{
  "schema": "phishdestroy.text-corpus.v1",
  "object_type": "Signed collection of page reading editions",
  "title": "The Steam Dossier — signed text corpus",
  "exported_at": "2026-09-29T00:23:51.082Z",
  "document_count": 342,
  "languages": [
    "ar",
    "de",
    "en",
    "es",
    "fr",
    "hi",
    "id",
    "it",
    "ja",
    "ko",
    "nl",
    "pl",
    "pt",
    "tr",
    "uk",
    "vi",
    "zh"
  ],
  "scope": "The signed object is this entire UTF-8 JSON file, including the complete exported content.text of every reading edition listed below, its source identity and its PDF SHA-256. Each document.scope identifies any editorial omissions or condensation. Pages absent from this list and external linked datasets or images are not included. This snapshot does not replace the separately signed rights statement.",
  "license": {
    "identifier": "CC0-1.0",
    "url": "https://creativecommons.org/publicdomain/zero/1.0/",
    "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
    "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
    "third_party_rights": "This is a public rights statement, not legal advice. Third-party materials, personal data, trademarks and quoted sources remain subject to their own rights and applicable law."
  },
  "integrity": {
    "signed_object": "dossier-text.json",
    "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
    "signature_file": "dossier-text.json.asc",
    "digest_file": "dossier-text.json.sha256",
    "format": "ASCII-armored detached OpenPGP",
    "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
    "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
    "verify": [
      "gpg --import pgp-key.txt",
      "gpg --verify dossier-text.json.asc dossier-text.json",
      "sha256sum -c dossier-text.json.sha256"
    ]
  },
  "documents": [
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "card_economy.html",
      "language": "en",
      "title": "The card economy — The Steam Dossier",
      "source_url": "https://phishdestroy.io/steam_dossier/card_economy",
      "source_html_sha256": "e6976efc6a8f740c1af31ca91f2082736b3a21a0ce1acc213fd3b192b0e33331",
      "exported_at": "2026-09-29T00:15:47.946Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "card_economy.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/en/card_economy.pdf?v=print-20260929-v5",
        "sha256": "53296542f2df0d03b6d31b9228e6767c2f27f34fa498205181f825f79929c301",
        "bytes": 239471,
        "pages": 22
      },
      "integrity": {
        "signed_object": "card_economy.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "card_economy.content.json.asc",
        "digest_file": "card_economy.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify card_economy.content.json.asc card_economy.content.json",
          "sha256sum -c card_economy.content.json.sha256"
        ]
      },
      "content": {
        "text": "EXHIBIT V — THE CARD ECONOMY\nThe Card Economy — Wholesaling, Drop Limits & Automated Farming\n\nA bot farm is not a leak in Valve's store. It is a customer.\n\nWHAT THIS SECTION PROVES\n\nThis chapter proves that automated Steam card farms operate as structural, revenue-generating wholesale customers rather than unauthorized exploiters. Every farming bot must clear Valve's $5.00 activation threshold, purchase game licenses, and generate guaranteed market transaction fees (floored at $0.02, extracting up to 66.7% fee rates on low-value assets). Despite explicit Terms of Service prohibitions against automated bot networks, 91 audited commercial bot networks openly maintain 694,673 complete card sets across Steam's ecosystem without enforcement interference.\n\n← Back to Executive briefing\n\nA Steam account cannot receive a single trading card until it has spent $5.00 in the store. It cannot farm a game it does not own, and it cannot farm one it was given free. So before an automated card farm produces anything at all, it has bought its way in — per account, at a price Valve publishes. Then Valve's automation clause names, line by line, exactly what that farm produces; its licence forbids every route by which a farmed card turns into money; and its market takes a cut when the card goes anyway — advertised at 15%, but floored at two cents a sale, which on a card priced in cents is most of the price. This exhibit measures how large that trade is, what the level at the top of a profile costs in sets, and what Valve's enforcement desk does with the same clause when the account belongs to an ordinary trader.\n\nWhat a farm has to buy firstWhat a level costs in setsBoth sides of the deskWho moderates the card economy\n$5.00Store spend before an account can receive any card — Valve's own support page\n13,876Games on Steam that issue trading cards, holding 99,971 distinct card types\n694,673Complete card sets held in stock right now by 91 publicly listed trading bots\n1,389,346Account-and-game card drop allowances that stock has already consumed, at minimum\n$9.99Median price of a card-bearing game — its finished set sells for a median of $0.74\n97,114Members of the card-trading group whose moderator list carries a Valve employee — § 08\n01 — The process\nWhat a farm actually is, step by step\n\nDescribed only from the tool's own documentation and Valve's own support pages. Nothing in this section is inferred, and nothing in it is disputed by either party.\n\nStep 1\nBuy in\n\nThe account must not be limited. Valve's support page bars limited accounts from \"Participating in the Steam Market\", from \"Trading Steam Community items (trading cards, booster packs, gems, etc.)\" and from \"Gaining Steam Profile Levels (Locked to level 0) and Trading Cards\". The gate is money: \"You will need to spend at least $5.00 USD within the Steam store.\"\n\nStep 2\nBuy games\n\nCards drop only from owned games. \"You need to own the game on your Steam account in order to be eligible for any card drops from it. Family sharing is not ownership and doesn't count.\" The free routes are closed too: \"Paid games that you've obtained for free during a promotion can't be farmed for card drops\", and \"You can't drop cards from F2P games without spending any money in them.\"\n\nStep 3\nIdle\n\nThe tool logs the account into the Steam network headlessly, \"parses your badges\", builds the list of farmable titles and starts \"playing eligible game and periodically checking if game is fully farmed already.\" Its maintainer's description of the mechanism: it \"does not do anything else than telling Steam we're playing given game.\"\n\nStep 4\nDrops run out\n\nEach title is finite. \"Every game has fixed number of card drops. Once you drop all of them (around a half of the full set), the game is not a candidate for farming anymore.\" A farm that wants to keep producing has to keep buying titles. Card supply is throttled by purchases — by design, and in Valve's favour.\n\nStep 5\nCash out\n\nThe card leaves by one of three doors: sold on the Community Market, traded away, or crushed into gems. Each is a Subscription Marketplace transaction or a trade, and § 3.D reserves the charge: \"Valve may charge a fee for transactions in a Subscription Marketplace.\" This is the step that makes the whole thing a breach — see 05.\n\nSources, read and quoted verbatim on 2026-09-22: Steam Support — Limited User Accounts ↗ · ArchiSteamFarm FAQ ↗ · Valve — Steam Trading Cards FAQ ↗ · Steam Subscriber Agreement ↗ archived 2026-09-24 ↗. ArchiSteamFarm is used throughout this page as a measuring instrument, not as a defendant; its own documentation states plainly that \"ASF is not authorized by Valve\".\n\n02 — The scale\nBefore a farm earns a cent, it has already paid Valve\n\nBecause a limited account cannot receive a card, every account in a farm must be bought out of limited status before it produces anything. The threshold is published, and it is charged per account.\n\nFarm size\tWhere the number comes from\tMinimum store spend to make them card-eligible\n10 accounts\tThe ceiling ASF recommends — \"based on internal Valve guidelines, as well as our own suggestions\"\t$50\n100–200 accounts\tTechnical ceiling in the same FAQ: \"you can run up to 100-200 bots with a single IP and a single ASF instance\"\t$500 – $1,000\n120 accounts\tEnforcement case 3 below — permanently banned\t$600\n170 accounts\tEnforcement case 2 below — permanently banned during the 2017 Winter Sale\t$850\n1,000 accounts\tEnforcement case 1 below — trade banned\t$5,000\n5,000 accounts unverified\tOperator scale reported to this investigation and not independently checked — see the note on sourcing\t$25,000\n10,000 accounts unverified\tOperator scale reported to this investigation and not independently checked — see the note on sourcing\t$50,000\n\nThe last two rows are the only figures on this page resting on an unverified report rather than a document — they are marked in the table, explained in the note on sourcing, and nothing else here depends on them. The right-hand column is arithmetic on Valve's published $5.00 USD threshold and nothing else. It is a floor, not an estimate of what a farm costs or of what Valve earned: it excludes the games, which must be owned and cannot have come free in a promotion, and it excludes the roughly 15% the Community Market takes when the cards are sold. No revenue figure is claimed on this page.\n\nAnd Valve has priced a card drop itself. Its Trading Cards FAQ sets the free-to-play conversion rate in plain dollars:\n\n\"Free to play games drop game cards based on your in-game purchasing. For every $9 USD spent (approximate) since the start of the Steam Trading Card Beta, you will earn one card drop.\"\n\n— Valve, Steam Trading Cards FAQ ↗ · verified verbatim 2026-09-22\n\nA trading card is not a giveaway the platform loses money on. It is something Valve sells, at a rate Valve published — and then charges a second time to sell onward. Which is why the honest description of a card farm is not parasite. It is wholesale buyer.\n\nHow large the thing being bought actually is\n\nEverything from here to the end of this section is measured, not reported. The card census is Steam Card Exchange's published badge pricelist; the prices of the games themselves come from Valve's own store API; the bot stock comes from a public bot directory that anyone can open. All three were read on 2026-09-22 and the arithmetic is given in full in section 08.\n\n13,876Games issuing cards\n99,971Distinct card types\n5 · 6 · 15Cards per set: min, median, max\n$0.74Median price of a finished set\n$23,586.57One of every set at market\nHow big a set is\n\n13,876 games by cards in the set. Valve drops about half of them to any one account.\n\n0\n1,250\n2,500\n3,750\n5,000\n5\n6\n7\n8\n9\n10\n11\n12\n13\n14\n15\nWhat the licence costs\n\nList price of the same games on Steam's store, in US dollars.\n\n0\n1,000\n2,000\n3,000\n4,000\n<$1\n$1-3\n$3-5\n$5-10\n$10-20\n$20-40\n$40+\nWhat the finished set returns\n\nMarket price of the completed set for the same games.\n\n0\n1,500\n3,000\n4,500\n6,000\n<$0.50\n$0.50-1\n$1-2\n$2-5\n$5-10\n$10+\n\nRead the second and third charts against each other and the shape of the trade is visible without arithmetic: the games cluster in the tens of dollars, the sets they yield cluster under one dollar. Both are counts of the same 13,876 games, on the same axis unit, so the comparison is between two heights and not between two scales.\n\nThat is the supply side. The demand side is the part Valve does not have to advertise, because it is already sitting in public: a single open directory of card-trading bots lists 91 bots holding 694,673 complete sets in stock at this moment. No login, no scraping of a marketplace, no private data — the stock figure is printed on the page next to each bot's name.\n\nTurn that stock into the only unit that matters here. Valve's own rule: \"Most games will drop a number of cards equal to about half the number of cards in that game's set of cards… You'll need to collect the other half of the set from other community members.\" One account can never finish a set by playing. Two, at the absolute minimum, each owning that game, each burning its once-per-game drop allowance. Drops do not regenerate.\n\n694,673Sets in stock, 91 public bots\n3,473,365Cards, at the 5-card minimum set\n1,389,346Drop allowances consumed, minimum\n2,602Accounts owning one single game, densest bot\nWhere the 694,673 sets are sitting\n\nThe twelve largest of the 91 publicly listed card bots, by complete sets in stock. The ten largest hold 248,115 sets between them — 35.7% of everything on the board.\n\n0\n11,250\n22,500\n33,750\n45,000\nCard Supply #4 (High)\nN!vq's Leveling (High)\nAlice [BOT] LEVEL-UP RARE SETS\nN!vq's Leveling (Low)\nDisco Lite Level Up\nN!vq's Leveling (Mid)\nbaty131store.net | Level Up\nKitten - Supreme\nArashirn | Level Up\nSH (Junior) Level Up\nDuobot.com - Overstock\nlvlupbot.com - godlike\n\nEvery one of those 1.39 million allowances belonged to an account that owned the game, was past the $5.00 gate, and can never produce those drops again. This is unsold inventory on ninety-one bots. It is not a measure of the market; it is a measure of what is left over after the market.\n\nThe last figure is a pigeonhole floor, not a headcount. One bot lists 14,310 sets drawn from only 11 games, so at least one of those games is represented by 1,301 sets, which is at least 2,602 distinct accounts that each bought that game. It is the smallest number the arithmetic permits, and it concerns one bot out of ninety-one.\n\nWhat this floor does and does not say\n\nThese bots buy cards from ordinary players as well as from farms — their published buy rates are the point of the directory. So the 1.39 million allowances are not a count of farm-owned accounts. They are a count of once-per-account, once-per-game drop allowances that have been spent somewhere on Steam and have ended up, unsold, in commercial stock. Whether the account behind each one was a farm or a teenager clearing their badges page does not change what Valve collected: the $5.00 unlock, the game licence, and a Market cut on every hop — not 15%, but 15% or the two one-cent minimums, whichever is larger, which on a card priced in cents is the larger by far. The arithmetic is in the fee ladder below. That is the point of this page, and it is not a complaint about farmers: the same conduct Valve charges a fee on is the conduct it cites, word for word, when it permanently bans an individual for \"commercial use\".\n\nThe figure is also a floor in a second sense. It counts only stock that is listed and unsold today on bots that choose to be in a public directory. Everything already sold, everything held privately, and every bot outside the directory is excluded.\n\nAnd farming does not pay for itself at Valve's prices\n\nThe obvious objection is that a farm buys cheap games to mint expensive cards. Steam's own store API says otherwise. Of the 13,876 card-bearing games, prices resolved for 13,713; 12,918 are paid titles with a median list price of $9.99. The median finished set sells for $0.74. Two licences are needed per set. So the median set costs roughly $19.98 of game licences to produce and returns $0.74.\n\nMeasured on 2026-09-22\tValue\tWhat it settles\nMedian list price, card-bearing game\t$9.99\tThe licence is the expensive half of the transaction, not the card\nGames priced at $4.99 or less\t3,665 (28.4%)\tEven the cheap tail is dearer than the set it yields\nCheapest card-bearing game on the store\t$0.99\tTwo licences, $1.98, for a set that typically sells under $1.30\nGames whose set sells for more than the game\t323 of 12,918 (2.5%)\tCard arbitrage against Steam's list prices exists in 1 game in 40\nFree-to-play titles in the census\t795\tAnd Valve prices each of their drops at $9 of in-game spend\n\nWhich closes the economic question in Valve's favour and against the usual story. At the prices Valve itself charges, card farming is a loss-making activity that only works on licences acquired below Steam's list price — bundles, regional pricing, key resale. The cards are the residue. The purchase is the event. And the purchase happened on Steam.\n\nWhat the farm actually props up\n\nPut the pieces together and the farm stops looking like something Valve tolerates and starts looking like something Valve needs. Every input a farm supplies is an output Valve reports or bills for. Follow one bot account outward:\n\nOne farmed accounta \"wholesale customer\", not a leak\nGame sales\n\nBuys the titles it farms — from the 13,876 card games to the $0.50 shovelware — because cards only drop from owned games.\n\n\"Online\" & playtime\n\nIdles them to drop cards, feeding the concurrent-player and hours-played figures Valve cites as engagement — the exact stat § 4.C calls \"faking playtime\".\n\nRegistrations\n\nMust clear the $5.00 limited-account gate before it can receive a card — a real store spend Valve books per account.\n\nWallet money & fees\n\nEvery card it sells routes back through the Market, where the fee reaches up to 66.7% on a low-value card and the proceeds stay locked in Steam Wallet.\n\nSteam-level PR\n\nThe badges and levels Valve showcases exist only because sets were crafted — and the top of that ladder is stocked by bots (see § 03).\n\nRemove the farm and every number above falls — the game sold fewer copies, the \"online\" was smaller, the account was never registered, the fee was never taken, and the level was never reached. That is why a rule that forbids automation coexists with millions of automated accounts: the prohibition is the option, and the activity is the revenue.\n\nAnd the cash-out itself is a value sink Valve taxes twice\n\nThe card is not the end of the loop. Valve's own mechanics let a card be crushed into gems, and gems be spent to craft booster packs — three more cards — which are sold or crushed again. Each hop is a Market transaction or a conversion, and each is taxed. The direction of that loop follows from the fee floor measured below and needs no outside model: every card sold inside it surrenders at least two cents, on cards that trade for three to five, so each turn of the crank returns less than went in. The loop destroys virtual value and forces fresh, fee-bearing transactions to replace it. No figure for the size of that loss is claimed here — the per-set return depends on gem rates and booster odds this investigation has not measured.\n\nTrading carddrops from owned game\n→\nGemscard crushed, fee taken\n→\nBooster packgems spent to craft\n→\n3 new cardssold on Market, fee taken\n↶\n\nOnly the mechanics are asserted here, and they are Valve's own — cards convert to gems, gems craft boosters, boosters yield cards — each documented in the Steam Trading Cards FAQ, and each hop a taxable Market event. Source of the loop mechanics: Valve, Steam Trading Cards FAQ ↗.\n\nThis is not a moment. It is an industry with a multi-year backbone.\n\nA single snapshot could be a fluke. So the public card-bot directory was read once per seasonal Steam sale, back through the Wayback Machine, from 2022 to 2026 — the set-stock the bots were carrying, and the same accounts, sale after sale. The economy does not appear and vanish; it persists, with a stable core of operators, and it peaked at over three million complete sets in stock during the Winter 2023 sale — on the order of a third of a million TF2 keys of value held at one moment, in one directory.\n\nComplete card sets held in the public bot directory, by Steam sale\n\nOne Wayback snapshot of steam.supply/CardBots per seasonal sale. Hover for the value in TF2 keys at that snapshot's rate.\n\n0.0M\n0.9M\n1.8M\n2.6M\n3.5M\nA’22\nS’23\nW’23\nS’24\nW’24\nS’25\nS’26\n401Distinct bot accounts seen across the sales\n59Present in 5 or more of 7 sales — the stable core\n16Present in every one of the 7 sales, 2022–2026\n3.22MPeak sets in stock (Winter 2023) ≈ $570k–790k in keys\nWhat one sale's badge ladder looks like from the top\n\nThe demand side matches the supply. On the public Summer Sale 2024 badge ladder archived 2026-07-16 ↗, the number one account had crafted the sale badge 1,740,645 times — 1.74 million ten-card sets, 17.4 million cards consumed into a single profile decoration. At the sale's own market price ($0.50 a set) that is ~$870,000 of card value; bought the way it is actually bought — TF2 keys traded to level-up bots at roughly 7.6 sets a key — it is ~229,000 keys, about $410,000–$570,000 in real terms. The number-two account: 552,000 sets, ~$130,000–181,000. No human plays for this. It is bought, and every leg of the buying is a transaction Valve clears.\n\nMethod and limits: set-stock is summed across the bots each snapshot lists; the number of bots per snapshot is not comparable across sales because some snapshots show only featured bots and some the full directory, so stock is read as a floor on what was visible, not a census. Key values use each snapshot's median advertised sets-per-key rate and a $1.79–$2.49 TF2 key. Persistence is by SteamID64 across snapshots. 2021 snapshots used an older page layout and are not included. Data: farm-economy-timeline.json; badge levels from SteamLadder; set prices from Steam Card Exchange (sale-time Wayback snapshots, $0.05 a card).\n\nAnd the same fleet is there when no sale is running\n\nThe two pictures above are not two populations. They are one fleet, photographed at different moments. The directory read at the top of this section was read on an ordinary day with no seasonal sale running — 2026-09-22 — and even at rest it held 91 bots and 694,673 complete sets: on the order of 186,000 TF2 keys, $334,000–$464,000 of card value, sitting idle between sales. That is the floor the operation carries when nothing is happening.\n\nAnd it is the same operation. Matched by SteamID64, 87 of those 91 resting bots — 96% — also appear in the seven sale snapshots above, sixteen of them in every single one. The directory is not a stall that opens for the sale and shuts afterward; it is a standing commercial inventory that this same fleet has swollen as high as 3.22 million sets at the Winter 2023 peak and never lets fall to zero. A sale is when it sells. It exists the rest of the year too.\n\nThe resting directory, bot by bot\n\nEach square is one bot in the directory on 2026-09-22, highlighted if it also appears in the seven sale snapshots. 91 is what the directory listed that day, not the size of the fleet — 401 distinct accounts appear across the sale snapshots, and the directory shows a different slice on different days.\n\nSeen in past sales (87) New since last snapshot (4)\n\nNon-sale baseline read 2026-09-22 from the same public directory, no login. Resting value uses each bot's own advertised sets-per-key rate and the $1.79–$2.49 key band above. Overlap is by SteamID64 against the seven sale snapshots. Because featured-vs-full listing differs by snapshot, this compares stock and identity, not headcount. Arithmetic in section 08.\n\n03 — The ladder\nThe other product is the number next to your name\n\nCards are the raw material. The finished good is a Steam Level, and Valve set its price in sets.\n\n100Steam Level\nTarget level — drag or use the arrow keys\nPrice of one complete set, USD\n\n$0.20 is the cheapest complete set in the census, $0.74 the median, $1.70 the mean. The figure covers the cards only — never the $5.00 unlocks or the game licences.\n\n55,000XP required\n550Complete sets consumed\n110Games to own, farming it yourself\n$407.00Cost of the cards at that price\n1,100Drop allowances burned, minimum\n$5,500.00$5.00 unlocks, if no account is reused\nComplete sets consumed, level 1 to 1,000\n\nOne badge craft = one complete set = 100 XP. Each level inside a block of ten costs 100 XP more than the block below it.\n\n0\n12,625\n25,250\n37,875\n50,500\n1\n250\n500\n750\n1000\n667\n550 sets\n\nA level is not decoration that Valve leaves alone. It is wired into the account. From Valve's own Trading Cards FAQ, on what crafting a badge gives you: \"100XP, which may increase your Steam Level. If your Steam Level increases, the limit on the size of your friends list will be increased by five, and potentially you'll unlock the ability to customize your profile with showcases.\" And on booster packs: \"your Steam Level increases your rate of receiving a booster pack drop: Level 10: +20%… Level 50: +100% increase in your drop rate (i.e. the rate has doubled).\"\n\nSo the level buys two things Valve controls: how many people you are allowed to be friends with, and how fast free cards fall into your inventory. The second one compounds — the more sets you have consumed, the faster the platform hands you more material. Valve built the reinvestment loop into the product.\n\nThe exchange rate is fixed and published. One badge craft consumes one complete set and yields 100 XP; \"You can craft a set for the same game at most five times.\" The XP a level costs rises every ten levels. That produces the following, and nothing here is an estimate:\n\nSteam Level\tComplete sets it consumes\tGames you must own to craft them yourself\tAt the cheapest set on record ($0.20)\tAt the median set ($0.74)\tScale\n10\t10\t2\t$2.00\t$7.40\t\n50\t150\t30\t$30.00\t$111.00\t\n100\t550\t110\t$110.00\t$407.00\t\n200\t2,100\t420\t$420.00\t$1,554.00\t\n500\t12,750\t2,550\t$2,550.00\t$9,435.00\t\n667\t22,579\t4,516\t$4,515.80\t$16,708.46\t\n\n667 is not a hypothetical. It is the highest level a single bot in the public directory advertises it can take a customer to, out of the 33,359 sets it holds across 6,117 games. The fourth column is the same ladder priced against the cheapest complete set anywhere in the census; the fifth against the median. Both are market prices for the cards alone and exclude the $5.00 unlock and the game licences entirely.\n\nHow the curve was checked, because Valve does not publish it\n\nValve states the badge rate (\"every 100 XP gives you an added Steam Level\") and then hedges it — \"(at least to start)\" — without publishing the escalation. The curve used above is the standard one, in which each level inside a block of ten costs 100 XP more than the block below it. It was verified against the directory rather than assumed: for every bot whose advertised maximum is limited by its stock rather than by the five-crafts-per-game cap, the level computed from this curve matches the level the bot advertises exactly — 541 against 541, 494 against 494, 464 against 464. Where the cap binds instead, the computed figure runs a few levels high, which is what a cap that also depends on per-game stock depth should do. No claim is made about the curve above level 667.\n\nRead the ladder next to section 02 and the shape of the business is visible. To put one account at level 500, somebody must assemble 12,750 complete sets. Each of those sets took at least two accounts' drop allowances, each of those accounts had crossed the $5.00 gate, and each owned the game. One vanity number at the top of one profile rests on at least 25,500 spent drop allowances underneath it. Valve is not losing that trade. Valve is the counterparty to every leg of it.\n\n04 — The statistics\nThe clause does not describe farming vaguely. It lists it.\n\n§ 4.C is not a general anti-bot sentence. Its enumerated examples name, one after another, the two things a card farm produces.\n\n\"You may not use any form of scripts, bots, macros, or other non-human-controlled systems ('Automation') to interact with Content and Services on Steam in any manner, including but not limited to:\n\nAutomating the Steam account creation process,\nFaking gameplay statistics (e.g., inflated wins or losses, XP, playtime),\nEarning rewards or progress without genuine user input,\nParticipating in adjudication systems (like peer reviews or 'overwatch') through automated means, including influencing outcomes or reporting users by scripted action rather than informed judgment.\"\n— Steam Subscriber Agreement § 4.C ↗ archived 2026-09-24 ↗ · retrieved and quoted verbatim 2026-09-22\n\"…playtime\"\n\nIdled hours are not phantom hours. The ASF FAQ answers the question head-on — \"Why playtime of games farmed through ASF doesn't increase?\" — with: \"It does, but not in real-time. Steam records your playtime in fixed intervals and schedules update for it… it's usually updated every 30 minutes or so.\"\n\nThose hours land in Valve's records, on Valve's store pages, and in the concurrent-player counts Valve publishes on its own Steam Charts ↗ archived 2026-09-23 ↗. In those figures an idling account is indistinguishable from a playing one. The engagement numbers the platform quotes outward are computed over a population that includes, by the platform's own rule, accounts that are not playing.\n\n\"…without genuine user input\"\n\nThat is a definition of an idled card drop, written by Valve. It is also a definition of the Steam Level, the badge, the booster-pack eligibility and the profile XP that come with it — the ASF FAQ confirms the tool \"preserves ability to receive booster packs\", because it logs in the same way the official client does.\n\nSo the reward system and the prohibited act are one mechanism seen from two sides. Valve built the reward to be produced by time rather than by skill, then wrote a clause forbidding the production of rewards by anything other than a person spending that time.\n\n05 — The commercial-use trap\nEvery exit from a farmed card is an exit the licence forbids — and Valve charges a fee at the door\n\nThis is the part that cannot be solved by farming \"responsibly\". The licence is for personal, non-commercial use, and a card only becomes worth farming at the moment it stops being personal.\n\n§ 2.A — the licence\n\n\"Valve hereby grants, and you accept, a non-exclusive license and right, to use the Content and Services for your personal, non-commercial use (except where commercial use is expressly allowed herein or in the applicable Subscription Terms).\"\n\n§ 2.G — the restriction\n\n\"you are not entitled to: … (iii) exploit the Content and Services or any of its parts for any commercial purpose, except as expressly permitted elsewhere in this Agreement (including any Subscription Terms or Rules of Use).\"\n\n§ 3.D — the fee\n\n\"Valve may charge a fee for transactions in a Subscription Marketplace. Any fees will be disclosed to you prior to the completion of the transaction.\"\n\nRead the three together and the position closes\n\nA card that is kept is worthless to a farm. A card that is sold, traded or crushed into gems has been used to produce value — and Valve has said in its own enforcement letter what it calls that: the operator of 170 bots was told the account \"was used to illegally collect collectible cards on Steam, as well as related and not only commercial activities.\" In that case the cards reached the market. The sales cleared. The fee was taken. The ban came afterwards.\n\nThe fee at that door is not 15%. On a farmed card it reaches two-thirds.\n\n§ 3.D reserves \"a fee\". On the cards a farm actually produces, that fee is nothing like the advertised ~15%. The Community Market takes a 5% Steam transaction fee and a 10% game fee, each with a floor of $0.01 (Valve's own Community Market FAQ). On a card listed for one cent those floors are the price: the buyer pays three cents, two of which are fees. The rounding floor turns the headline 15% into an effective levy that climbs to 66.7% exactly where the card market lives — a few cents a card.\n\nEffective fee on a Community Market sale, by the seller's asking price\n\n5% Steam + 10% game, each a minimum of $0.01. The shaded band is where trading cards actually trade — roughly $0.03–$0.05 a card.\n\n0%\n10%\n20%\n30%\n40%\n50%\n60%\n70%\ncards\n$0.01\n$0.10\n$0.20\n$0.30\n$0.40\n$0.50\n66.7%\nSeller wants\tSteam 5% (min $0.01)\tGame 10% (min $0.01)\tBuyer pays\tCombined fee\n$0.01\t$0.01\t$0.01\t$0.03\t66.7%\n$0.03\t$0.01\t$0.01\t$0.05\t40.0%\n$0.05\t$0.01\t$0.01\t$0.07\t28.6%\n$0.08\t$0.01\t$0.01\t$0.10\t20.0%\n$1.00\t$0.05\t$0.10\t$1.15\t13.0%\n\nThe 10% game fee goes to the app that issued the card; the 5% is Valve's own, and on Valve's own titles and base inventory items the whole fee is Valve's. Either way the money leaves the farmer — selling a three-cent card returns one cent and surrenders two. Multiply that by the hundreds of thousands of sub-five-cent card sales a farm generates and \"the fee Valve may charge\" is the business model, not a footnote. Source: Steam Community Market FAQ — Fees ↗ archived 2026-09-21 ↗, read 2026-09-22; the curve is arithmetic on those two published rates and their $0.01 floors.\n\nThere is no configuration of the tool that escapes this. It can be run by one person, on one account, with perfect restraint — and the moment that person sells a single farmed card for wallet funds, the same sentence in § 2.G reaches them as reaches the operator of ten thousand. Valve has therefore reserved a breach it could invoke against effectively every card seller on its own market, and has declined to invoke it against effectively all of them. A rule enforced at that rate is not a rule. It is an option. The question this exhibit puts is not why card farmers are tolerated; it is why the same option is exercised against a lone user who sells a card, while the commercial card economy those cards feed — the trading services, the level-up bots, the bulk sellers — runs on in the open, one of its largest groups moderated by a Valve employee (§ 08). The breach is reserved against the small holder and waived for the machine.\n\n06 — The enforcement record\nNo notice, in waves, and it travels down the phone number\n\nValve wrote the no-notice power into the agreement itself, one clause after the automation clause.\n\n\"Valve may restrict or terminate your Account(s) or a particular Subscription for any conduct or activity that is illegal, constitutes a Cheat or Automation or breaches the Steam Online Conduct Rules. You acknowledge that Valve is not required to provide you notice before terminating your Subscription(s) and/or Account.\"\n\n— Steam Subscriber Agreement § 4.D ↗ archived 2026-09-24 ↗ · verified verbatim 2026-09-22\n\n1,000+ bots · trade banned. \"It looks like this account was used to manage a network of bot accounts. Botting is a violation of the Steam Subscriber Agreement.\"\n\n170+ bots · permanently banned, 2017 Winter Sale. \"this account was used to illegally collect collectible cards on Steam, as well as related and not only commercial activities. The account has been permanently blocked and Steam Support can not provide additional support on this issue.\"\n\n120+ bots · permanently banned. \"This and other accounts were used for flooding our network infrastructure, which is a violation of Steam online conduct.\"\n\n— Steam Support messages reproduced in the ArchiSteamFarm FAQ, section \"Did anybody get banned for it?\". Source ↗ · verified verbatim 2026-09-22\nCase 4 — June 2025, VAC bans on idled CS2\n\nA later episode than the three above is recorded in the project's own tracker: accounts that had only idled Counter-Strike 2 through the tool received VAC bans — the anti-cheat kind, not the administrative kind. The maintainer's position is that idling cannot cause one, since it \"does not do anything else than telling Steam we're playing given game.\" The cause is disputed. That the accounts were banned is not.\n\n— ArchiSteamFarm discussion #3440, opened 26 June 2025 ↗ · read 2026-09-22\n\nHow a main account dies\n\nIn the same thread a project collaborator describes the propagation rule: accounts can be banned \"by chain\", if they are using same phone number — \"it may be just one VAC ban, propagated to 'clean' accounts connected to the banned one.\"\n\nSteam Guard requires a phone number. Farms are built on the operator's phone number. So enforcement does not stop at the disposable accounts: it walks up the shared identifier to the account holding the library, the friends list and the inventory. That is the mechanism one project collaborator describes for how a single action removes an operator's main account along with the farm — and it is why the loss in an enforcement wave is not measured in $5 accounts. (Described by a project contributor in ASF GitHub discussion #3440; there is no official Valve confirmation or formal precedent on record.)\n\nThe same paragraph, five years apart, from three different agents\n\nThe clause that makes farming a breach — commercial use of a personal, non-commercial licence — is not reserved for farms. It is the standing reason Steam gives when it closes an account over trading, and the reason arrives as a template. Below are three instances, published by the people who received them, five years apart, from three different named agents.\n\nMessage from Steam Support on Sep 29 @ 7:56pm\n\n\"The account you are writing in for has been locked for violating the terms of the Steam Subscriber Agreement. The account has been identified as being used for commercial purposes based on trading, community reports, and other factors.\n\nThis lock is permanent and Steam Support cannot help you further with this.\n\nBecause we have provided all the information we have I am closing this help request. Please note you will not receive further replies regarding this issue.\n\nRegards,\nHal\"\n\nThis help request has been closed.\n29 September 2020. Posted by the recipient with the comment \"RIP Trading.\" — @gergelyszabo94 ↗\nMensagem do Suporte Steam em 12 de jul. às 22:41\n\n\"The account you are writing in for has been locked for violating the terms of the Steam Subscriber Agreement. The account has been identified as being used for commercial purposes based on trading, community reports, and other factors.\n\nThis lock is permanent and Steam Support cannot help you further with this.\n\nBecause we have provided all the information we have I am closing this help request. Please note that future help requests submitted regarding the account lock may be closed without a reply.\n\nSteam Support\nVido\"\n\nEste pedido de ajuda foi encerrado.\n12 July 2024, Portuguese interface. The recipient is a professional CS2 player: \"already contacted steam support but only getting auto-responses… can't play faceit and also can't play professional matches.\" — @prcs25 ↗ archived 2024-07-15 ↗\nQuoted by the recipient, r/steamsupport\n\n\"Hello, The account you are writing in for has been locked for violating the terms of the Steam Subscriber Agreement. The account has been identified as being used for commercial purposes based on trading, community reports, and other factors.\n\nThis lock is permanent and Steam Support cannot help you further with this.\n\nBecause we have provided all the information we have I am closing this help request. Please note that future help requests submitted regarding the account lock may be closed without a reply.\n\nSteam Support\nSally\"\n\nReceived three times, on three separate requests.\n29 March 2025. The writer was not appealing the lock — their account had been stolen along with their email and they were asking for access: \"I'm not asking about the ban and I'm not disputing it I just want access to my steam account… Valve have given me this exact answer copy and pasted on every request and close the request.\" — r/steamsupport ↗, held in this investigation's own complaint corpus\n\nWord for word, comma for comma, across fifty-five months, three agents and two interface languages. The only edit anywhere in the body is the final sentence hardening between 2020 and 2024, from \"you will not receive further replies\" to \"future help requests… may be closed without a reply.\" Whatever process produced these decisions, the letter is not a record of it. The stated grounds are \"trading, community reports, and other factors\" — a category, a report of unknown origin, and an unnamed remainder.\n\nFive further cases, collected the same way. The first three are the same category and the same outcome; the last two are the same desk answering a different rule in the same words:\n\nDate\tWhat the account did\tWhat happened\tSource\n04.12.2021\tBuying and selling on Buff — \"I've done nothing else than some buying and selling on buff aka P2P trading\"\tCommunity ban: no market, no trading, expensive inventory frozen\tr/csgomarketforum ↗ archived 2025-03-27 ↗\n06.12.2021\tOne-way P2P trades through Buff and Bitskins for loadouts and trade-ups\tPermanent commercial-use lock plus community lock: \"stuck in a pseudo invisible mode… My profile is also stuck on private\"\tr/GlobalOffensiveTrade ↗ archived 2021-12-06 ↗\n20.12.2024\tAccount held since 2017, thousands of hours; trades on community marketplaces for themed loadouts and trade-ups\tPermanent lock with community lock, no prior warning or strike; support \"say their decision is final\", replies are automated\tr/csgomarketforum ↗ archived 2025-06-27 ↗\n23.12.2024\tReturning user adds wallet funds after a year away, over a VPN used \"only for general internet security\"\tPermanent community ban with no reason given at all: \"the ban is permanent and they cannot provide further information and that further tickets may be closed without response.\" 196 upvotes, 340 replies\tr/steamsupport ↗\n04.08.2026\tYears of purchases from Iran; the writer states they never posted, never used the Market, never used the forums\tCommunity access locked until 2038 over \"sanctioned regions\"; ticket closed by an agent named Azul. The same account's refund from the same Iranian IP had been approved a year earlier. The library and the money stay with Valve.\tr/pcgaming ↗\n\nThe last row is a different rule from the rest — sanctions compliance, not commercial use — and it is included because the shape of the answer is identical: a category, no evidence, no appeal, a closed ticket. It also raises a question the others do not. If the account was unlawful to serve, the years of payments were unlawful to accept. One of those two positions has to be wrong, and only one of them cost the customer anything.\n\nAll eight were read on 2026-09-22 — the 2021 and December-2024 threads through Internet Archive snapshots and the rest through a public Reddit front end, because Reddit refused direct requests from the collecting host. The two 2020 and 2024 letters are transcribed from the screenshots attached to the original posts, which are still live. None of these accounts is alleged by this investigation to be innocent or guilty of anything — that is precisely the point. No reader, and no regulator, can tell from the letter.\n\nNote on sourcing — operator-scale losses\n\nOperators canvassed by this investigation report losses on the order of five to ten thousand accounts each in single enforcement waves, with main accounts taken alongside the farm. That canvass is recorded here as first-party reporting, not as a finding. It has no published sample size, no fixed collection date and no per-account verification, and no other number on this page depends on it; the two rows in section 02 that rest on it are marked as such.\n\nIt is stated rather than dropped for two reasons. The chain-ban mechanism above is the documented explanation for exactly that pattern. And a regulator can compel from Valve the one record that would settle it: how many accounts were actioned for automation, in which waves, and how much each of those accounts had spent in the store before it was closed. Until that record exists, the figure stays where it is — reported, attributed and unproven.\n\n07 — The asymmetry\nBoth sides of the same desk\n\nSet that standard of proof against the one Valve applied to its own support operation. The right-hand column is this dossier's own incident register, reproduced with the hedges it carries there.\n\nA customer, for trading\n\nEight documented cases, 2020–2026\n\nConduct\nSelling or buying items on third-party marketplaces; in one case, no conduct at all — the account had been stolen.\nEvidence shown\nNone. \"Based on trading, community reports, and other factors.\"\nNotice\nNone. Valve reserved that in § 4.D: \"Valve is not required to provide you notice before terminating.\"\nAppeal\n\"This lock is permanent and Steam Support cannot help you further with this.\"\nTicket\nClosed on the first reply. Further requests \"may be closed without a reply.\"\nReach\nProfile, friends list, chat, Market, inventory, and every item bought with real money.\nDuration\nPermanent.\nAn automated bot fleet, for volume\n\n694,673 complete sets in public stock across 91 bots\n\nConduct\nRunning automated headless scripts across thousands of accounts simultaneously to idle cards, mass-craft badges and trade sets at industrial scale.\nEvidence shown\nOpenly published bot directories (steam.supply, SteamLvlUp) and public groups with millions of members.\nNotice\nZero intervention. 88.97% carry no ban of any kind; 99.8% of remaining bans are cosmetic.\nAppeal\nNot needed. Fleets operate continuously across multi-year lifecycles without disruption.\nTicket\n—\nReach\nUnrestricted inventory exchange, badge leveling and market liquidity.\nBenefit to Valve\n$26.8M+ in minimum store spend ($5.00 entry gate per account) plus 15% Community Market transaction cuts.\nThe question this leaves, put plainly\n\nAn individual customer who manually trades cards or items faces a permanent, unappealable ban under § 4.C (automation) or § 2.G (commercial use). An automated farming fleet running headless bots across thousands of accounts operates openly with an 88.97% untouched rate. Valve is the beneficiary of both.\n\nThe asymmetry is economic: individual traders take value out of the platform, while automated card fleets pump millions into Valve's store spend gate ($5.00 per account) and fuel transaction fees on every resale. Enforcement does not follow the written rulebook; it follows the revenue model.\n\n08 — Governance\nWho moderates the card economy\n\nThis dossier's recurring finding — that the third-party layer around Steam is staffed from inside Steam — holds in the card economy too, and it ends somewhere specific: nobody independent can count what Valve's enforcement actually does, because the party able to count sits inside that layer. Every fact below was read from Valve's own public group and profile pages on 2026-09-22 and can be reproduced by anyone in a browser.\n\nA Valve employee moderates the largest card-trading group Valve employee\n\nCardTrades ↗ describes itself in its own header as the \"Steam Card Exchange official group\" and carries 97,114 members. Its listed moderators — the accounts that hold the controls of that group — are Mickmane, SgtFopper and afarnsworth ↗.\n\nThat last profile is flagged by Valve's own site markup as a Valve employee — the page carries class=\"profile_header_valve_employee\" — gives its location as Bellevue, Washington, and belongs to the Valve, Steam and Steam Trading Cards Group groups. SteamID64 76561197960434622, member since 12 September 2003.\n\nThe observation is structural, not personal, and it is not an automation point — a moderator of a card-trading group is not running a bot, and nothing here suggests otherwise. The point is the clause in section 07. Steam Card Exchange is a third-party commercial card service; trading cards through third-party services is the exact conduct for which Valve permanently locks ordinary accounts under \"used for commercial purposes based on trading, community reports, and other factors.\" A Valve employee holds a listed moderator role in that service's official community group of ninety-seven thousand people.\n\nNo allegation of wrongdoing is made against any individual here, and no inference is drawn about what that role involves. The asymmetry is the finding: when an ordinary account touches a third-party card or skin service, the answer is a closed ticket and a permanent lock with no evidence shown; when the service is this one, a Valve employee is on the moderator list and the arrangement is visible on a page Valve itself publishes. What is asked is what is asked everywhere else in this dossier: produce the written authorisation, if one exists — and if none is needed, say so in writing, because eight people in section 06 were told the opposite.\n\nThe ban-list layer, and who administers it Volunteer moderatorThird-party service\n\nSteambans.com's group (archived) ↗ (live ↗ archived 2025-12-03 ↗) records its lineage in its preserved group description: \"The official Steambans.com Steam Community Group. SteamBans.com is a brand new service based on an old concept. Global ban lists have been active for years on the old WONID program from VALVe. When the change came to STEAMID it fell natural for us to develop a service specially minded to this new system. But we also wanted more. *. Archive page for Steambans which shut down in 2013.\" Its listed administrators include devicenull and killahinstinct_ ↗.\n\nThat administrator account is not a Valve employee — it carries no employee flag. It is a volunteer with unusually deep standing: a member of Community Moderators (414 members, described as a group \"created by Steam's Community Moderators\"), of Wiki Coordinators, of Steam Community Market, and of Valve programme and pre-release groups including Valve Pipeline, Steam Client Beta, Mobile Auth Beta, New Steam Community Beta, Steam Labs, Steamworks and Report ScamURLs. SteamID64 76561197960794555.\n\nAlso inside that circle and displaying Steambans directly in his public group roster: msart ↗ (groups roster ↗), SteamID64 76561197977933359, whose profile states in its own words \"I run steamid.uk and many other steam and non steam related sites\", and who operates a linked network of sixteen groups — SteamIDcouk (primary group \"Sid website\"), SidAdmins, SidBans, steamideu, Steam3ID, s-id and SArchive among them.\n\nsteamid.uk names the same number itself. Its FAQ: \"Who created SteamID? The SteamID website, network infrastructure, and security systems are all managed by 76561197977933359.\" Two answers further down it states where the data comes from: \"SteamID primarily utilizes the Steam Web API for data collection.\" The same page describes multiple dedicated servers across different hosts, off-site development, storage and text-search servers, and a separate backup facility.\n\nVerified through preserved Internet Archive records: the Steambans group snapshot of 3 Dec 2025 ↗, the operator profile snapshot of 14 Sep 2024 ↗, and the steamid.uk FAQ snapshot of 1 Apr 2026 ↗, matching data read directly on 2026-09-22.\n\nWhat this adds up to, and what it does not\n\nBan lists, SteamID resolution and card trading are the three services that decide who is trusted, who is identifiable, and what an item is worth. None of the three is operated by Valve. On each one, the people holding the controls came from inside Valve's orbit: a flagged Valve employee on the moderator list of the card service's official group; a long-serving Valve community moderator with pre-release programme access administering the ban-list group; the ID-resolution service run by one private individual who sits in the same circle. Three services, three control surfaces, three people Valve had already given standing to.\n\nGroup membership is not employment, and none of this is an accusation. It is a governance fact, and it is the reason the ordinary defence — those are third parties, we cannot control them — has to be tested rather than accepted. The people at the controls are not strangers to Valve. Valve is in a position to say what, if anything, it asked of them; nobody outside is in a position to find out.\n\nNobody counts. That is the finding.\n\nThe Steam ID space is a contiguous integer range. Walking it and reporting how many accounts are banned, how many are limited, and how much inventory sits behind a trade ban is not a research programme — it is a loop and an API key. Valve hands out that key itself, at steamcommunity.com/dev/apikey. And yet no independent party publishes that census. Not a regulator, not a journalist, not an academic, not a consumer body. The only public numbers about the scale of enforcement on Steam are the ones Valve chooses to mention.\n\nThe capability is not missing. It is held. The service that resolves and indexes the ID space at scale — steamid.uk — says in its own FAQ that it \"primarily utilizes the Steam Web API for data collection\" and runs it across multiple dedicated servers, off-site storage and text-search machines and a separate backup facility. It is operated by one private individual. His ban-list sibling group is co-administered by a long-serving Valve community moderator with access to Valve's pre-release programmes. The one party positioned to publish the count sits inside Valve's orbit, and does not publish it.\n\nThis is the same shape the dossier finds everywhere else. Every service that decides something load-bearing about the Steam economy — who is trusted, who is identifiable, what an item is worth, who is banned — is nominally third-party and practically adjacent to Valve. Steam Card Exchange is not an exception to that pattern; it is another instance of it. The defence that these are independent operators is available to Valve precisely because no one has ever been able to test it against a number.\n\nThe 10.88M Account Census: 88.97% Untouched\n\nThe ArchiSteamFarm install base was audited across Valve's GetPlayerBans endpoint (10,880,610 accounts, 55 minutes). The non-limited subset alone represents $26.8M+ in minimum store spend ($5.00 entry threshold). 9,680,599 accounts (88.97%) carry no ban of any kind, and 99.8% of the remainder carry only cosmetic community bans that leave automated trading active.\n\n5,360,499Non-limited ASF members (Steam's displayed count)\n10,880,610Total API entries scanned (limited + non-limited)\n9,680,599Never banned at all (88.97%)\n1,200,011Carry any Steam ban (11.0%) — 99.8% cosmetic\n55 minTo census the whole population, one key\nForensic Evidence & Deep Census\n\nThe detailed demographic breakdown — including ban-type distribution charts, account age at enforcement, creation-year clusters (2020–2026), and geographic self-reporting — is published in the dedicated census investigation.\n\nOpen the Full 10.88M Ban Census (Exhibit VI) →Section 4 — The Asset ID Blackout →\n\nSo the question to put, and it is answerable only by Valve: which identifier or capability was withdrawn, on what date, on whose decision, and what measurable effect did it have on the operators it was aimed at — set against its effect on everyone outside who was trying to count. A change that ends independent auditing does not become neutral because it was announced as a safety measure. It is the reason the census in the block above does not exist.\n\n09 — Method and limits\nWhat was read, and what is not claimed\n\nEvery quotation on this page was taken from the live source on 2026-09-22 and reproduced verbatim. Nothing here is drawn from a scrape, a marketplace credential or a private dataset.\n\nThe four datasets, and the arithmetic on them\n\nEach is a single public request, reproducible from a terminal. No account was used, no marketplace was logged into, and no endpoint requiring a credential was called.\n\nDataset\tWhere it came from\tWhat was computed from it\nCard census\n13,876 games\tSteam Card Exchange's published badge pricelist, the same feed that renders their public price page ↗ archived 2026-08-04 ↗\tGames issuing cards, cards per set, distinct card types, and the market price of each finished set. Medians and the $23,586.57 total are this investigation's arithmetic.\nGame prices\n13,713 resolved\tValve's own public store endpoint, store.steampowered.com/api/appdetails, cc=us, price field only, in batches\tMedian and distribution of the list price of a card-bearing game; the count of games whose finished set outsells the game itself.\nBot stock\n91 bots, 694,673 sets\tThe public card-bot directory at steam.supply/CardBots ↗, read as rendered, no login\tTotal sets in stock, the minimum card count, the drop-allowance floor, and the per-bot pigeonhole floor on distinct accounts.\nCross-check\n21 shared bots\tsteamlvlup.net/cardbots ↗ archived 2026-02-10 ↗, an independent directory of the same bots\tVerification only. On the 21 bots both list, aggregate stock agrees to 0.03%; the largest single-bot disagreement is 1.36%, consistent with two crawls of live inventory minutes apart.\n\nAttribution, as the second directory requires: data provided by SteamLvlUp, licensed under CC BY 4.0 archived 2026-09-23 ↗; used here only as an independent check on a third party's stock figures, and modified in that the per-bot rows were aggregated and compared rather than reproduced. Steam Card Exchange and steam.supply are credited above by link. Game prices are Valve's own. Card, game, and set names and images are Valve's or the publishers', reproduced under neither claim nor licence, as facts about a market.\n\nTwo intended measurements were not made and are not substituted for. Steam's own Community Market endpoints — priceoverview, search/render, pricehistory — return nothing to the collecting host, and Steam Community discussion pages return HTTP 403 to it, so no figure on this page is derived from live Market data. The sale-volume method that would have counted card drops at the daily reset requires a logged-in Steam session; this investigation's manifest states that no marketplace credential was used, and that statement was kept. The bot-stock floor is what can be measured without one.\n\nPrimary sources\n\nSteam Subscriber Agreement ↗ archived 2026-09-24 ↗ — § 2.A, § 2.G, § 3.D, § 4.C, § 4.D.\nSteam Support — Limited User Accounts ↗ — the $5.00 threshold and the restricted-feature list.\nValve — Steam Trading Cards FAQ ↗ — drop mechanics and the $9 free-to-play rate.\nArchiSteamFarm FAQ ↗ and discussion #3440 ↗.\nSteam Community group and profile pages, read directly, for section 08.\nsteamid.uk FAQ, Internet Archive snapshot 2026-04-01 ↗.\nEight Steam Support lock notices published by their recipients, 2020–2026, listed with their links in section 06.\n\nWhat is not claimed\n\nNo revenue figure is estimated for Valve from card farming. No active-account count is asserted for any tool, and the 1.39 million drop allowances are not a count of farm-owned accounts — see the note in section 02. No individual is accused of wrongdoing; where a person is named it is by their own public Steam handle, in their own public role, from a page Valve publishes. None of the eight locked accounts in section 06 is asserted to be innocent or guilty; the finding concerns the letter, not the account. The operator-loss figures in section 02 are first-party reporting and are labelled as such at the sourcing note. The steamid.uk FAQ is quoted from an Internet Archive snapshot because the live page is behind a bot challenge. No claim is made that any ban census has been attempted and suppressed — the finding is only that none is published. The Steam Level curve above 667 is not modelled.\n\nWhy the tool is not the subject\n\nArchiSteamFarm states that it \"is not authorized by Valve\" and it is not accused of anything on this page. It is used as a measuring instrument, because it is the only party in this economy that documents the mechanics in public and in writing. Valve can retire the whole exhibit in one paragraph: publish which commercial automation it authorises, and the per-operator record of what it did about the rest.\n\nRead next: how the Market itself is priced → · the price ladder and the listing cap → · the items Steam will not carry →",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "The Card Economy — Wholesaling, Drop Limits & Automated Farming"
          },
          {
            "level": 2,
            "id": null,
            "text": "What a farm actually is, step by step"
          },
          {
            "level": 3,
            "id": null,
            "text": "Buy in"
          },
          {
            "level": 3,
            "id": null,
            "text": "Buy games"
          },
          {
            "level": 3,
            "id": null,
            "text": "Idle\nThe tool logs the account into the Steam network headlessly, \"parses your badges\", builds the list of farmable titles and starts \"playing eligible game and periodically checking if game is fully farmed already.\" Its maintainer's description of the mechanism: it \"does not do anything else than telling Steam we're playing given game.\""
          },
          {
            "level": 3,
            "id": null,
            "text": "Drops run out\nEach title is finite. \"Every game has fixed number of card drops. Once you drop all of them (around a half of the full set), the game is not a candidate for farming anymore.\" A farm that wants to keep producing has to keep buying titles. Card supply is throttled by purchases — by design, and in Valve's favour."
          },
          {
            "level": 3,
            "id": null,
            "text": "Cash out\nThe card leaves by one of three doors: sold on the Community Market, traded away, or crushed into gems. Each is a Subscription Marketplace transaction or a trade, and § 3.D reserves the charge: \"Valve may charge a fee for transactions in a Subscription Marketplace.\" This is the step that makes the whole thing a breach — see 05."
          },
          {
            "level": 2,
            "id": null,
            "text": "Before a farm earns a cent, it has already paid Valve"
          },
          {
            "level": 3,
            "id": null,
            "text": "How large the thing being bought actually is"
          },
          {
            "level": 3,
            "id": null,
            "text": "How big a set is"
          },
          {
            "level": 3,
            "id": null,
            "text": "What the licence costs"
          },
          {
            "level": 3,
            "id": null,
            "text": "What the finished set returns"
          },
          {
            "level": 3,
            "id": null,
            "text": "Where the 694,673 sets are sitting"
          },
          {
            "level": 3,
            "id": null,
            "text": "What this floor does and does not say"
          },
          {
            "level": 3,
            "id": null,
            "text": "And farming does not pay for itself at Valve's prices"
          },
          {
            "level": 3,
            "id": null,
            "text": "What the farm actually props up"
          },
          {
            "level": 4,
            "id": null,
            "text": "Game sales"
          },
          {
            "level": 4,
            "id": null,
            "text": "\"Online\" & playtime"
          },
          {
            "level": 4,
            "id": null,
            "text": "Registrations"
          },
          {
            "level": 4,
            "id": null,
            "text": "Wallet money & fees"
          },
          {
            "level": 4,
            "id": null,
            "text": "Steam-level PR"
          },
          {
            "level": 3,
            "id": null,
            "text": "And the cash-out itself is a value sink Valve taxes twice"
          },
          {
            "level": 3,
            "id": null,
            "text": "This is not a moment. It is an industry with a multi-year backbone."
          },
          {
            "level": 3,
            "id": null,
            "text": "Complete card sets held in the public bot directory, by Steam sale"
          },
          {
            "level": 3,
            "id": null,
            "text": "What one sale's badge ladder looks like from the top"
          },
          {
            "level": 3,
            "id": null,
            "text": "And the same fleet is there when no sale is running"
          },
          {
            "level": 3,
            "id": null,
            "text": "The resting directory, bot by bot"
          },
          {
            "level": 2,
            "id": null,
            "text": "The other product is the number next to your name"
          },
          {
            "level": 3,
            "id": null,
            "text": "Complete sets consumed, level 1 to 1,000"
          },
          {
            "level": 3,
            "id": null,
            "text": "How the curve was checked, because Valve does not publish it"
          },
          {
            "level": 2,
            "id": null,
            "text": "The clause does not describe farming vaguely. It lists it."
          },
          {
            "level": 3,
            "id": null,
            "text": "\"…playtime\""
          },
          {
            "level": 3,
            "id": null,
            "text": "\"…without genuine user input\""
          },
          {
            "level": 2,
            "id": null,
            "text": "Every exit from a farmed card is an exit the licence forbids — and Valve charges a fee at the door"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 2.A — the licence"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 2.G — the restriction"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 3.D — the fee"
          },
          {
            "level": 3,
            "id": null,
            "text": "Read the three together and the position closes"
          },
          {
            "level": 3,
            "id": "fee-ladder",
            "text": "The fee at that door is not 15%. On a farmed card it reaches two-thirds."
          },
          {
            "level": 3,
            "id": null,
            "text": "Effective fee on a Community Market sale, by the seller's asking price"
          },
          {
            "level": 2,
            "id": null,
            "text": "No notice, in waves, and it travels down the phone number"
          },
          {
            "level": 3,
            "id": null,
            "text": "Case 4 — June 2025, VAC bans on idled CS2"
          },
          {
            "level": 3,
            "id": null,
            "text": "How a main account dies"
          },
          {
            "level": 3,
            "id": null,
            "text": "The same paragraph, five years apart, from three different agents"
          },
          {
            "level": 3,
            "id": null,
            "text": "Note on sourcing — operator-scale losses"
          },
          {
            "level": 2,
            "id": null,
            "text": "Both sides of the same desk"
          },
          {
            "level": 3,
            "id": null,
            "text": "A customer, for trading"
          },
          {
            "level": 3,
            "id": null,
            "text": "An automated bot fleet, for volume"
          },
          {
            "level": 3,
            "id": null,
            "text": "The question this leaves, put plainly"
          },
          {
            "level": 2,
            "id": null,
            "text": "Who moderates the card economy"
          },
          {
            "level": 3,
            "id": null,
            "text": "A Valve employee moderates the largest card-trading group Valve employee"
          },
          {
            "level": 3,
            "id": null,
            "text": "The ban-list layer, and who administers it Volunteer moderator Third-party service"
          },
          {
            "level": 3,
            "id": null,
            "text": "What this adds up to, and what it does not"
          },
          {
            "level": 3,
            "id": null,
            "text": "Nobody counts. That is the finding."
          },
          {
            "level": 3,
            "id": null,
            "text": "The 10.88M Account Census: 88.97% Untouched"
          },
          {
            "level": 3,
            "id": null,
            "text": "Forensic Evidence & Deep Census"
          },
          {
            "level": 2,
            "id": null,
            "text": "What was read, and what is not claimed"
          },
          {
            "level": 3,
            "id": null,
            "text": "The four datasets, and the arithmetic on them"
          },
          {
            "level": 3,
            "id": null,
            "text": "Primary sources"
          },
          {
            "level": 3,
            "id": null,
            "text": "What is not claimed"
          },
          {
            "level": 3,
            "id": null,
            "text": "Why the tool is not the subject"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/#briefing-heading",
          "https://help.steampowered.com/en/faqs/view/71D3-35C2-AD96-AA3A",
          "https://github.com/JustArchiNET/ArchiSteamFarm/wiki/FAQ",
          "https://steamcommunity.com/tradingcards/faq/",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260924114457/https://store.steampowered.com/subscriber_agreement/",
          "https://steamladder.com/ladder/badges/2861690/",
          "http://web.archive.org/web/20260716205303/https://steamladder.com/ladder/badges/2861690/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/farm-economy-timeline.json",
          "https://store.steampowered.com/charts/",
          "http://web.archive.org/web/20260923183013/https://store.steampowered.com/charts/",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://github.com/JustArchiNET/ArchiSteamFarm/discussions/3440",
          "https://x.com/gergelyszabo94/status/1311004678633795585",
          "https://x.com/prcs25/status/1811893857253982720",
          "http://web.archive.org/web/20240715122902/https://x.com/prcs25/status/1811893857253982720",
          "https://reddit.com/r/steamsupport/comments/1fjmgc5/what_to_do_when_your_steam_account_gets_hacked/mkelm2y/",
          "https://www.reddit.com/r/csgomarketforum/comments/r87owv/psa_my_steam_account_just_got_banned/",
          "http://web.archive.org/web/20250327203008/https://www.reddit.com/r/csgomarketforum/comments/r87owv/psa_my_steam_account_just_got_banned/",
          "https://www.reddit.com/r/GlobalOffensiveTrade/comments/r9xql9/d_recently_received_commercial_ban_for_what_seems/",
          "http://web.archive.org/web/20211206034804/https://www.reddit.com/r/GlobalOffensiveTrade/comments/r9xql9/d_recently_received_commercial_ban_for_what_seems/",
          "https://www.reddit.com/r/csgomarketforum/comments/1hhxx7m/d_permanently_locked_on_steam_for_commercial_use/",
          "http://web.archive.org/web/20250627014045/https://www.reddit.com/r/csgomarketforum/comments/1hhxx7m/d_permanently_locked_on_steam_for_commercial_use/",
          "https://www.reddit.com/r/steamsupport/comments/1hkctwt/permanent_ban_with_no_explanation/",
          "https://www.reddit.com/r/pcgaming/comments/1vf24lu/warning_to_all_gamersexpats_steam_took_my_money/",
          "https://steamcommunity.com/groups/card-trading-card-trades",
          "https://steamcommunity.com/id/afarnsworth",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/groups/steambans",
          "https://steamcommunity.com/groups/steambans",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/id/killahinstinct_",
          "https://web.archive.org/web/20240914124859/https://steamcommunity.com/id/msart",
          "https://steamcommunity.com/id/msart/groups/",
          "http://web.archive.org/web/20260401154714/https://steamid.uk/faq/",
          "https://phishdestroy.io/steam_dossier/enforcement_audit.html",
          "https://phishdestroy.io/steam_dossier/#evidence-blackout",
          "https://www.steamcardexchange.net/index.php?badgeprices",
          "http://web.archive.org/web/20260804200309/https://www.steamcardexchange.net/index.php?badgeprices",
          "https://steam.supply/CardBots",
          "https://steamlvlup.net/cardbots",
          "http://web.archive.org/web/20260210171205/https://steamlvlup.net/cardbots",
          "https://steamlvlup.net/",
          "https://creativecommons.org/licenses/by/4.0/",
          "http://web.archive.org/web/20260923221628/https://creativecommons.org/licenses/by/4.0/",
          "https://phishdestroy.io/steam_dossier/market_economics.html",
          "https://phishdestroy.io/steam_dossier/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/elite_skins.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/en/card_economy.content.json",
      "export_json_sha256": "4487a490a0d307dc5d587ddc13abd4c7654cf798fa7ab6ada0fbd3184f87d7e7"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "card_economy_de.html",
      "language": "de",
      "title": "Die Kartenwirtschaft – Das Steam-Dossier",
      "source_url": "https://phishdestroy.io/steam_dossier/card_economy_de",
      "source_html_sha256": "b21755f079483e1de5d3361e0027d258488f1ead3f8c9a7b9b53123f9c9b2f0b",
      "exported_at": "2026-09-29T00:15:47.943Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "card_economy_de.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/de/card_economy_de.pdf?v=print-20260929-v5",
        "sha256": "c75ca8de37e77b398b0de9a3d7c570eea76a20680b92420ae81364153b737048",
        "bytes": 269230,
        "pages": 25
      },
      "integrity": {
        "signed_object": "card_economy_de.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "card_economy_de.content.json.asc",
        "digest_file": "card_economy_de.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify card_economy_de.content.json.asc card_economy_de.content.json",
          "sha256sum -c card_economy_de.content.json.sha256"
        ]
      },
      "content": {
        "text": "ANHANG V – DIE KARTENWIRTSCHAFT\nEine Bot-Farm ist kein Leck in Valves Laden. Es ist ein Kunde.\n\nEin Steam-Konto kann erst dann eine einzelne Sammelkarte erhalten, wenn es einen Betrag ausgegeben hat $5.00 im Shop. Es kann kein Spiel farmen, das ihm nicht gehört, und es kann auch keines farmen, das es kostenlos erhalten hat. Bevor also ein automatisierter Karten-Farm-Dienst überhaupt etwas produziert, muss er sich den Zugang erkaufen – pro Konto, zu einem Preis, den Valve veröffentlicht. Dann legt die Automatisierungsklausel von Valve Zeile für Zeile genau fest, was dieser Farmbetrieb produziert; seine Lizenz verbietet jeden Weg, auf dem eine gefarmte Karte zu Geld wird; und sein Markt erhält einen Anteil, wenn die Karte dennoch verkauft wird – beworben bei 15%, aber mit einer Untergrenze von zwei Cent pro Verkauf, was bei einer Karte, deren Preis in Cent angegeben ist, den größten Teil des Preises ausmacht. Diese Darstellung zeigt, wie groß dieser Handel ist, was die oberste Stufe eines Profils in Sets kostet und wie die Durchsetzungsstelle von Valve mit derselben Klausel verfährt, wenn das Konto einem gewöhnlichen Händler gehört.\n\nWas ein landwirtschaftlicher Betrieb als Erstes kaufen mussWas ein Level in Sets kostetBeide Seiten des SchreibtischesWer regelt den Kartenumlauf?\n$5.00Ausgaben im Shop, bevor ein Konto eine Karte erhalten kann — Valves eigene Support-Seite\n13,876Spiele auf Steam, bei denen Sammelkarten ausgegeben werden und die 99,971 verschiedene Kartentypen enthalten\n694,673Komplette Kartensätze, die derzeit von 91 börsennotierten Trading-Bots auf Lager gehalten werden\n1,389,346Zumindest die Guthaben für Account- und Spielkarten, die bereits aufgebraucht wurden\n$9.99Medianpreis eines Kartenspiels – ein vollständiges Set wird zum Medianpreis von $0.74 verkauft\n97,114Mitglieder der Kartentauschgruppe, in deren Moderatorenliste ein Mitarbeiter mit der Nummer Valve aufgeführt ist — § 08\n01 — Der Ablauf\nWas ein Bauernhof eigentlich ist – Schritt für Schritt\n\nDie Angaben basieren ausschließlich auf der Dokumentation des Tools selbst und den Support-Seiten von Valve. Nichts in diesem Abschnitt ist eine Schlussfolgerung, und nichts darin wird von einer der beiden Parteien bestritten.\n\nSchritt 1\nEinstieg\n\nDas Konto darf nicht begrenzt. Auf der Support-Seite von Valve werden Konten mit Einschränkungen daran gehindert, „Teilnahme am Steam-Markt“, aus „Handel mit Steam Community-Artikeln (Sammelkarten, Booster-Packs, Edelsteine usw.)“ und aus „Erhalte Steam Profilstufen (auf Stufe 0 festgelegt) und Sammelkarten“. Das Tor ist Geld: „Sie müssen in diesem Geschäft mindestens $5.00 USD ausgeben.“\n\nSchritt 2\nSpiele kaufen\n\nKarten erhält man nur aus Spielen, die man besitzt. „Du musst das Spiel auf deinem Steam-Konto besitzen, um Anspruch auf die darin enthaltenen Karten zu haben. Die Familienfreigabe gilt nicht als Besitz und wird nicht berücksichtigt.“ Auch die freien Routen sind gesperrt: „Kostenpflichtige Spiele, die du im Rahmen einer Aktion kostenlos erhalten hast, können nicht zum Sammeln von Karten genutzt werden.“, und „Man kann keine Karten aus F2P-Spielen erhalten, ohne dort Geld auszugeben.“\n\nSchritt 3\nLeerlauf\n\nDas Tool meldet das Konto im Steam-Netzwerk im Headless-Modus an, „analysiert deine Abzeichen“, erstellt die Liste der Titel, die sich zum Farmen eignen, und startet „Ein geeignetes Spiel spielen und regelmäßig überprüfen, ob das Spiel bereits vollständig durchgespielt ist.“ Die Beschreibung des Mechanismus durch den Betreuer: Es „tut nichts anderes, als Steam mitzuteilen, dass wir ein bestimmtes Spiel spielen.“\n\nSchritt 4\nDie Tropfen gehen zur Neige\n\nJeder Titel ist endlich. „Jedes Spiel hat eine festgelegte Anzahl an Karten, die man erhalten kann. Sobald man alle davon erhalten hat (etwa die Hälfte des gesamten Sets), lohnt es sich nicht mehr, das Spiel weiter zu spielen.“ Ein Bauernhof, der weiterhin produzieren will, muss ständig Titel kaufen. Das Kartenangebot wird durch Käufe begrenzt – das ist beabsichtigt und spielt Valve in die Hände.\n\nSchritt 5\nAuszahlung\n\nDie Karte verlässt das Spiel auf eine von drei Arten: Sie wird auf dem Community-Markt verkauft, getauscht oder zu Edelsteinen zermahlen. In jedem Fall handelt es sich um eine Transaktion auf dem Abonnement-Marktplatz oder um einen Tausch, und § 3.D sieht folgende Gebühr vor: „Valve kann für Transaktionen auf einem Abonnement-Marktplatz eine Gebühr erheben.“ Dies ist der Schritt, der das Ganze zu einem Verstoß macht – siehe 05.\n\nQuellen, wörtlich zitiert auf 2026-09-22: Steam Support – Eingeschränkte Benutzerkonten ↗ · ArchiSteamFarm FAQ ↗ · Valve — Steam FAQ zu Sammelkarten ↗ · Steam Abonnentenvertrag ↗ archiviert 2026-09-24 ↗. ArchiSteamFarm wird auf dieser Seite durchgehend als Messinstrument verwendet, nicht als Angeklagter; in der dazugehörigen Dokumentation heißt es ausdrücklich, dass „ASF ist nicht durch Valve zugelassen“.\n\n02 — Die Skala\nBevor ein landwirtschaftlicher Betrieb auch nur einen Cent verdient, hat er bereits Valve gezahlt\n\nDa ein Konto mit eingeschränkten Rechten keine Karte erhalten kann, muss jedes Konto in einer Farm aus dem Status „eingeschränkt“ herausgelöst werden, bevor es Erträge abwirft. Der Schwellenwert wird veröffentlicht und pro Konto berechnet.\n\nBetriebsgröße\tWoher die Zahl stammt\tMindestumsatz im Geschäft, um die Berechtigung zum Erhalt der Karte zu erlangen\n10 Konten\tDie von der ASF empfohlene Obergrenze — „auf der Grundlage interner Valve-Richtlinien sowie unserer eigenen Vorschläge“\t$50\n100–200 Konten\tTechnische Obergrenze in denselben FAQ: „Mit einer einzigen IP-Adresse und einer einzigen ASF-Instanz können Sie bis zu 100–200 Bots betreiben.“\t$500 – $1,000\n120 Konten\tDurchsetzungsfall 3 unten – dauerhaft gesperrt\t$600\n170 Konten\tDurchsetzungsfall 2 unten – während des Winter-Ausverkaufs 2017 dauerhaft gesperrt\t$850\n1,000 Konten\tDurchsetzungsfall 1 unten – Handelsverbot\t$5,000\n5,000 Konten unbestätigt\tBedienerwaage im Rahmen dieser Untersuchung angegeben und nicht unabhängig überprüft — siehe den Hinweis zur Quellenangabe\t$25,000\n10,000 Konten unbestätigt\tBedienerwaage im Rahmen dieser Untersuchung gemeldet und nicht unabhängig überprüft — siehe den Hinweis zur Quellenangabe\t$50,000\n\nDie letzten beiden Zeilen sind die einzigen Angaben auf dieser Seite, die auf einem unbestätigten Bericht und nicht auf einem Dokument beruhen – sie sind in der Tabelle gekennzeichnet und werden in Hinweis zur Herkunft, und nichts anderes hier hängt davon ab. Die rechte Spalte bezieht sich ausschließlich auf die von Valve veröffentlichte Schwelle von $5.00 USD und auf nichts anderes. Es handelt sich um eine Boden, keine Schätzung der Kosten für einen Bauernhof oder der Einnahmen von Valve: Nicht berücksichtigt sind die Spiele, die im Besitz des Spielers sein müssen und nicht kostenlos im Rahmen einer Werbeaktion erworben worden sein dürfen, sowie die rund 15%, die der Community-Markt beim Verkauf der Karten einbehält. Auf dieser Seite werden keine Umsatzzahlen angegeben.\n\nUnd Valve hat selbst einen Kartendrop bepreist. In den FAQ zu den Sammelkarten wird die Konversionsrate des Free-to-Play-Modells in einfachen Dollar angegeben:\n\n„Bei Free-to-Play-Spielen erhältst du Spielkarten entsprechend deinen In-Game-Käufen. Pro ausgegebenem $9 USD (ungefähr) „Seit Beginn der Beta-Phase der Steam-Sammelkarten erhältst du eine Karte.“\n\n— Valve, Steam Häufig gestellte Fragen zu Sammelkarten ↗ · wortgetreu überprüft 2026-09-22\n\nEine Sammelkarte ist kein Werbegeschenk, mit dem die Plattform Geld verliert. Es handelt sich um etwas, das Valve verkauft, und zwar zu einem von Valve veröffentlichten Preis – und das dann ein zweites Mal in Rechnung stellt, um es weiterzuverkaufen. Deshalb lautet die ehrliche Beschreibung einer „Kartenfarm“ nicht Parasit. Es ist Großhandelskäufer.\n\nWie groß das Kaufobjekt tatsächlich ist\n\nAlles von hier bis zum Ende dieses Abschnitts wird gemessen, nicht angegeben. Die Kartenzählung basiert auf Steam, der veröffentlichten Preisliste von Card Exchange; die Preise der Spiele selbst stammen aus der eigenen Shop-API von Valve; der Bot-Bestand stammt aus einem öffentlichen Bot-Verzeichnis, auf das jeder Zugriff hat. Alle drei Daten wurden auf 2026-09-22 ausgelesen, und die Berechnungen sind vollständig aufgeführt in Abschnitt 08.\n\n13,876Kartenspiele\n99,971Unterschiedliche Kartentypen\n5 · 6 · 15Karten pro Satz: Min., Median, Max.\n$0.74Medianpreis eines fertigen Sets\n$23,586.57Je ein Exemplar pro Set auf dem Markt\nWie groß ist eine Menge?\n\n13,876 Spiele, die auf den Karten im Set abgebildet sind. Valve gibt etwa die Hälfte davon auf ein beliebiges Konto ab.\n\n0\n1,250\n2,500\n3,750\n5,000\n5\n6\n7\n8\n9\n10\n11\n12\n13\n14\n15\nWas die Lizenz kostet\n\nListenpreis derselben Spiele im Shop von Steam, in US-Dollar.\n\n0\n1,000\n2,000\n3,000\n4,000\n<$1\n$1-3\n$3-5\n$5-10\n$10-20\n$20-40\n$40+\nWas das fertige Set zurückgibt\n\nMarktpreis des kompletten Sets für dieselben Spiele.\n\n0\n1,500\n3,000\n4,500\n6,000\n<$0.50\n$0.50-1\n$1-2\n$2-5\n$5-10\n$10+\n\nVergleicht man die zweite und dritte Grafik miteinander, wird die Struktur des Handels auch ohne Rechenaufwand deutlich: Die Spiele gruppieren sich im Bereich von einigen Dutzend Dollar, die daraus resultierenden Sätze hingegen unter einem Dollar. Bei beiden handelt es sich um Zählungen derselben 13,876 Spiele auf derselben Achsen-Einheit, sodass der Vergleich zwischen zwei Höhen und nicht zwischen zwei Skalen stattfindet.\n\nDas ist die Angebotsseite. Die Nachfrageseite ist der Teil, für den Valve keine Werbung machen muss, da er bereits öffentlich zugänglich ist: Ein einziges offenes Verzeichnis von Bot-Programmen zum Kartentausch listet Derzeit sind 91 Bots mit 694,673 kompletten Sets auf Lager. Keine Anmeldung, kein Scraping eines Marktplatzes, keine privaten Daten – die Lagerbestandszahl ist auf der Seite neben dem Namen jedes Bots angegeben.\n\nMache diese Aktie zur einzigen Einheit, die hier zählt. Valves eigene Regel: „Bei den meisten Spielen werden etwa so viele Karten aus dem Kartensatz des jeweiligen Spiels entfernt, wie etwa die Hälfte der Karten in diesem Kartensatz ausmacht… Die andere Hälfte des Sets musst du von anderen Community-Mitgliedern sammeln.\" Ein Account allein kann eine Spielrunde niemals durch Spielen beenden. Es sind mindestens zwei Accounts erforderlich, die jeweils dieses Spiel besitzen und ihre einmal pro Spiel verfügbare „Drop“-Quote aufbrauchen. „Drops“ regenerieren sich nicht.\n\n694,673Sets auf Lager, 91 öffentliche Bots\n3,473,365Karten, bei einer festgelegten Mindestanzahl von 5 Karten\n1,389,346Verbrauchte Drop-Zuteilungen, Mindestwert\n2,602Konten, die nur ein einziges Spiel besitzen, mit der höchsten Bot-Dichte\nWo sich die 694,673-Sätze befinden\n\nDie zwölf größten der 91 börsennotierten „Card Bots“, gemessen an der Anzahl der vorrätigen Komplettsätze. Die zehn größten besitzen zusammen 248,115 Sätze – 35.7% von jedem Artikel auf der Liste.\n\n0\n11,250\n22,500\n33,750\n45,000\nCard Supply #4 (High)\nN!vq's Leveling (High)\nAlice [BOT] LEVEL-UP RARE SETS\nN!vq's Leveling (Low)\nDisco Lite Level Up\nN!vq's Leveling (Mid)\nbaty131store.net | Level Up\nKitten - Supreme\nArashirn | Level Up\nSH (Junior) Level Up\nDuobot.com - Overstock\nlvlupbot.com - godlike\n\nJede einzelne dieser 1,39 Millionen Zuteilungen gehörte zu einem Konto, das das Spiel besaß, die $5.00-Schwelle überschritten hatte und diese Drops nie wieder generieren kann. Das ist Lagerbestände, die nicht verkauft wurden auf einundneunzig Bots. Das ist kein Maßstab für den Markt, sondern ein Maßstab dafür, was nach dem Markt übrig bleibt.\n\nDie letzte Zahl bezieht sich auf die Anzahl der Kategorien, nicht auf die Anzahl der Nutzer. Ein Bot listet 14,310 Sets auf, die aus nur 11 Spielen stammen; daher ist mindestens eines dieser Spiele durch 1,301 Sets vertreten, was mindestens 2,602 verschiedene Konten bedeutet, die jeweils dieses Spiel gekauft haben. Das ist die kleinste Zahl, die die Rechnung zulässt, und sie betrifft einen von einundneunzig Bots.\n\nWas dieser Boden aussagt und was nicht\n\nDiese Bots kaufen Karten sowohl von normalen Spielern als auch von „Farms“ – ihre veröffentlichten Ankaufspreise sind der Kernpunkt des Verzeichnisses. Die 1,39 Millionen Zertifikate entsprechen also nicht der Anzahl der Konten, die sich im Besitz von landwirtschaftlichen Betrieben befinden. Es handelt sich um eine Aufstellung der einmal pro Konto und einmal pro Spiel gewährten Drop-Kontingente, die irgendwo auf Steam aufgebraucht wurden und unverkauft im Handelsbestand gelandet sind. Ob es sich bei dem jeweiligen Konto um einen Farm-Account oder um einen Teenager handelte, der seine Abzeichen-Seite abräumte, ändert nichts daran, was Valve eingenommen hat: die $5.00-Freischaltung, die Spielelizenz und eine Provision aus dem Markt bei jedem Verkauf — nicht 15%, sondern 15% oder die beiden Ein-Cent-Mindestbeträge, je nachdem, welcher davon größer ist, was bei einer Karte, deren Preis in Cent angegeben ist, bei weitem der höhere Betrag ist. Die Berechnung findet sich in die untenstehende Gebührenstaffel. Darum geht es auf dieser Seite, und es handelt sich dabei nicht um eine Beschwerde über Landwirte: Das gleiche Verhalten, für das Valve eine Gebühr erhebt, ist genau das Verhalten, das dort Wort für Wort angeführt wird, wenn eine Person wegen „kommerzieller Nutzung“ dauerhaft gesperrt wird.\n\nDie Zahl stellt auch in einem zweiten Sinne eine Untergrenze dar. Sie berücksichtigt nur Bestände, die heute im Angebot und noch nicht verkauft über Bots, die sich dafür entscheiden, in einem öffentlichen Verzeichnis zu sein. Alles, was bereits verkauft wurde, alles, was privat gehalten wird, und jeder Bot, der nicht im Verzeichnis aufgeführt ist, wird ausgeschlossen.\n\nUnd bei den Preisen von Valve rechnet sich die Landwirtschaft nicht aus.\n\nDer naheliegende Einwand lautet, dass ein Farm-Betreiber billige Spiele kauft, um teure Karten zu generieren. Die eigene Shop-API von Steam sagt jedoch etwas anderes. Von den 13,876 Spielen, die Karten enthalten, wurden die Preise für 13,713 ermittelt; 12,918 sind kostenpflichtige Titel mit einem mittleren Listenpreis von $9.99. Der Medianpreis für ein fertiges Set liegt bei $0.74. Pro Set werden zwei Lizenzen benötigt. Das Set kostet also im Median etwa $19.98 Spielelizenzen zur Herstellung und Rückgaben $0.74.\n\nGemessen bei 2026-09-22\tWert\tWas damit geregelt wird\nMedian des Listenpreises, Kartenspiel\t$9.99\tDie Lizenz ist der teure Teil der Transaktion, nicht die Karte.\nSpiele, die $4.99 oder weniger kosten\t3,665 (28.4%)\tSelbst der billigste Schwanz ist teurer als das, was man daraus gewinnt.\nDas günstigste Kartenspiel im Shop\t$0.99\tZwei Lizenzen, $1.98, für ein Set, das in der Regel für unter $1.30 verkauft wird\nSpiele, deren Set teurer ist als das Spiel selbst\t323 von 12,918 (2.5%)\tIn 1 von 40 Spielen gibt es Kartenarbitrage gegenüber den Listenpreisen von Steam.\nFree-to-Play-Titel in der Erhebung\t795\tUnd Valve legt den Preis für jeden seiner Drops auf $9 der Ausgaben im Spiel fest\n\nDamit ist die wirtschaftliche Frage zugunsten von Valve und gegen die gängige Darstellung geklärt. Zu den Preisen, die Valve selbst verlangt, Das „Card Farming“ ist ein verlustbringendes Geschäft, das nur bei Lizenzen funktioniert, die unter dem Listenpreis von Steam erworben wurden. — Bundles, regionale Preisgestaltung, Wiederverkauf von Schlüsseln. Die Karten sind nur Nebensache. Der Kauf ist das eigentliche Ereignis. Und der Kauf fand am Steam statt.\n\nWas der Betrieb tatsächlich am Leben erhält\n\nFührt man all diese Aspekte zusammen, erscheint der landwirtschaftliche Betrieb nicht mehr als etwas, das Valve toleriert, sondern als etwas, das Valve benötigt. Jeder Input, den ein landwirtschaftlicher Betrieb liefert, ist ein Output, den Valve ausweist oder in Rechnung stellt. Verfolgen Sie einmal den Weg eines Bot-Kontos nach außen:\n\nEin gefälschter Accountein „Großhandelskunde“, kein Informationsleck\nSpielverkäufe\n\nKauft die Titel, die es „farmt“ – von den 13,876-Kartenspielen bis hin zum $0.50-Shovelware –, da Karten nur aus Spielen fallen, die man besitzt.\n\n„Online“ & Spielzeit\n\nLässt sie Karten fallen, wodurch die Zahlen zu gleichzeitigen Spielern und gespielten Stunden aufgestockt werden, die Valve als Engagement bezeichnet – genau jene Statistik, die § 4.C als „Vortäuschen von Spielzeit“ bezeichnet.\n\nAnmeldungen\n\nDas Konto muss die $5.00-Grenze für das begrenzte Konto überschreiten, bevor es eine Karte erhalten kann – pro Konto werden Valve Ausgaben in einem realen Geschäft verbucht.\n\nGuthaben im Wallet & Gebühren\n\nJede verkaufte Karte wird über den Markt zurückgeleitet, wo die Gebühr bei einer Karte mit geringem Wert bis zu 66.7% beträgt und der Erlös in der Steam-Wallet gesperrt bleibt.\n\nSteam-Level-PR\n\nDie Abzeichen und Level-Ausstellungen „Valve“ gibt es nur, weil Sets erstellt wurden – und die Spitze dieser Rangliste wird von Bots besetzt (siehe § 03).\n\nEntferne die Farm, und alle oben genannten Zahlen fallen weg. — Das Spiel verkaufte sich weniger oft, der „Online“-Bereich war kleiner, das Konto wurde nie registriert, die Gebühr wurde nie erhoben und das Level wurde nie erreicht. Deshalb gibt es eine Regel, die Automatisierung verbietet, während gleichzeitig Millionen automatisierter Konten existieren: Das Verbot ist die Option, und die Aktivität ist der Umsatz.\n\nUnd die Auszahlung selbst ist ein Wertverlust Valve – doppelte Besteuerung\n\nDie Karte ist nicht das Ende der Schleife. Dank der Mechanik von Valve kann eine Karte zerkleinert werden in Edelsteine, und Edelsteine müssen für die Herstellung ausgegeben werden Booster-Packs — drei weitere Karten —, die verkauft oder erneut vernichtet werden. Jeder Schritt ist eine Markttransaktion oder eine Umwandlung, und jeder Schritt wird besteuert. Die Richtung dieser Schleife ergibt sich aus der unten gemessenen Gebührenuntergrenze und bedarf keines externen Modells: Jede darin verkaufte Karte gibt mindestens zwei Cent, bei Karten, die zu einem Kurs von drei bis fünf gehandelt werden, sodass bei jeder Umdrehung der Kurbel weniger zurückkommt, als hineingesteckt wurde. Dieser Kreislauf vernichtet den virtuellen Wert und zwingt dazu, ihn durch neue, gebührenpflichtige Transaktionen zu ersetzen. Hier wird keine Zahl für die Höhe dieses Verlusts genannt — Die Ausbeute pro Set hängt von den Edelsteinraten und den Booster-Gewinnchancen ab, die im Rahmen dieser Untersuchung nicht erfasst wurden.\n\nSammelkarteDrops aus dem eigenen Spiel\n→\nEdelsteineKarte zerknüllt, Gebühr eingezogen\n→\nBooster-Packfür die Herstellung verwendete Edelsteine\n→\n3 neue Kartenauf Market verkauft, Gebühr abgezogen\n↶\n\nHier werden lediglich die Spielmechaniken beschrieben, und zwar die von Valve – Karten werden in Edelsteine umgewandelt, aus Edelsteinen werden Booster-Packs hergestellt, Booster-Packs liefern Karten – allesamt in der Steam-FAQ zu Sammelkarten dokumentiert, und jeder Schritt ist ein steuerpflichtiges Marktereignis. Quelle der Schleifenmechanik: Valve, Steam FAQ zu Sammelkarten ↗.\n\nDas ist nicht nur ein Moment. Es handelt sich um eine Branche mit einer langjährigen Tradition.\n\nEine einzelne Momentaufnahme könnte ein Zufall sein. Daher wurde das öffentliche Verzeichnis der Card-Bots einmal pro saisonalem Steam-Ausverkauf zurück bis ins Jahr 2022 über die Wayback Machine abgefragt – der Bestand, den die Bots mit sich führten, und dieselben Konten, Ausverkauf für Ausverkauf. Die Wirtschaft taucht nicht einfach auf und verschwindet wieder; sie besteht fort, mit einem stabilen Kern von Betreibern, und erreichte ihren Höhepunkt bei über drei Millionen komplette Sets auf Lager während des Winter-Ausverkaufs 2023 – etwa eine Drittelmillion wertvolle TF2-Keys, die zu einem bestimmten Zeitpunkt in einem Verzeichnis gespeichert waren.\n\nVollständige Kartensätze im öffentlichen Bot-Verzeichnis, nach Steam Verkauf\n\nPro saisonalem Verkauf gibt es einen Wayback-Snapshot von „steam.supply/CardBots“. Fahre mit der Maus darüber, um den Wert der TF2-Schlüssel zum Kurs dieses Snapshots anzuzeigen.\n\n0.0M\n0.9M\n1.8M\n2.6M\n3.5M\nA’22\nS’23\nW’23\nS’24\nW’24\nS’25\nS’26\n401Im gesamten Vertrieb festgestellte einzelne Bot-Konten\n59In 5 oder mehr von 7 Verkäufen vertreten – der stabile Kern\n16An allen sieben Auktionen im Zeitraum 2022–2026 teilgenommen\n3,22 Mio.Peak-Sets auf Lager (Winter 2023) ≈ $570k–790k Schlüssel\nSo sieht die Rangliste der Verkaufsabzeichen von ganz oben aus\n\nDie Nachfrageseite entspricht dem Angebot. In der Öffentlichkeit Sommer-Sale 2024 – Abzeichen-Rangliste archiviert 2026-07-16 ↗, der Account auf Platz eins hatte das Verkaufsabzeichen erstellt 1,740,645 Mal — 1,74 Millionen Zehn-Karten-Sets, 17,4 Millionen Karten zu einem einzigen Profildekor zusammengefasst. Zum Marktpreis des Anbieters ($0.50 pro Set) beträgt das ~$870,000 des Kartenwerts; wenn man es so kauft, wie es tatsächlich gekauft wird – TF2-Schlüssel, die gegen Level-Up-Bots eingetauscht werden, zu etwa 7,6 Sets pro Schlüssel –, dann ist es ~229,000 Tasten, etwa $410,000–$570,000 real gesehen. Das Konto Nummer zwei: 552,000 Sätze, ~$130,000–181,000. Kein Mensch spielt um diesen Einsatz. Er wird gekauft, und jeder Schritt des Kaufs ist eine Transaktion, die Valve abwickelt.\n\nMethode und Grenzen: Der Set-Bestand wird über alle Bots hinweg summiert, die in den einzelnen Snapshots aufgeführt sind; die Zahl Die Anzahl der Bots pro Snapshot ist nicht über verschiedene Verkaufszeiträume hinweg vergleichbar, da manche Snapshots nur vorgestellte Bots und andere das gesamte Verzeichnis zeigen; daher wird der Bestand als Untergrenze dessen angesehen, was sichtbar war, und nicht als vollständige Bestandsaufnahme. Für Schlüsselwerte werden der Median der pro Schlüssel beworbenen Sets aus jedem Snapshot sowie ein TF2-Schlüssel von $1.79–$2.49 verwendet. Die Persistenz wird über die SteamID64 hinweg über alle Snapshots hinweg gewährleistet. Snapshots aus dem Jahr 2021 verwendeten ein älteres Seitenlayout und wurden nicht berücksichtigt. Daten: farm-economy-timeline.json; Abzeichen-Stufen von SteamLadder; festgelegte Preise aus dem Steam-Karten-Tausch (Wayback-Momentaufnahmen zum Zeitpunkt des Verkaufs, $0.05 pro Karte).\n\nUnd dieselbe Flotte ist auch dann vor Ort, wenn gerade kein Verkauf stattfindet\n\nDie beiden obigen Bilder zeigen nicht zwei Populationen. Es handelt sich um ein und dieselbe Flotte, die zu unterschiedlichen Zeitpunkten fotografiert wurde. Das Verzeichnis, das am Anfang dieses Abschnitts aufgeführt ist, wurde auf einem ein ganz normaler Tag, an dem kein Saisonausverkauf stattfindet — 2026-09-22 — und selbst im Ruhezustand hielt es 91 Bots und 694,673 vollständige Sets: in der Größenordnung von 186,000 TF2-Tasten, $334,000–$464,000 des Kartenwerts, im Leerlauf zwischen den Verkäufen. Das ist der Mindestbestand, den der Betrieb vorrätig hält, wenn nichts los ist.\n\nUnd es handelt sich um denselben Vorgang. Abgeglichen anhand der SteamID64, 87 dieser 91 inaktivierten Bots — 96% — tauchen ebenfalls in den sieben oben gezeigten Verkaufsübersichten auf, jeweils sechzehn davon. Das Verzeichnis ist kein Verkaufsstand, der zum Verkauf geöffnet und danach wieder geschlossen wird; es handelt sich um ein ständiges Handelsverzeichnis, das dieselbe Flotte auf bis zu 3,22 Millionen Sets auf dem Höchststand im Winter 2023 und fällt nie auf null. Ein Ausverkauf ist, wenn verkauft wird. Das gibt es auch den Rest des Jahres.\n\nDas Verzeichnis „resting“, Bot für Bot\n\nJedes Quadrat steht für einen Bot im Verzeichnis auf 2026-09-22; es ist hervorgehoben, wenn es auch in den sieben Verkaufs-Snapshots vorkommt. 91 war die Zahl, die an diesem Tag im Verzeichnis aufgeführt war, nicht die Größe der Flotte — In den Verkaufsübersichten tauchen 401 verschiedene Konten auf, und das Verzeichnis zeigt an verschiedenen Tagen jeweils einen anderen Ausschnitt.\n\nIn früheren Auktionen gesehen (87) Neu seit dem letzten Snapshot (4)\n\nDer Basiswert für Nicht-Verkaufsdaten wird als 2026-09-22 aus demselben öffentlichen Verzeichnis ausgelesen, ohne Anmeldung. Der Ruhewert basiert auf der von jedem Bot selbst angegebenen Rate an Sets pro Schlüssel und dem darüber liegenden Schlüsselbereich von $1.79 bis $2.49. Der Abgleich erfolgt anhand der SteamID64 mit den sieben Verkaufs-Snapshots. Da sich die Auflistung der vorgestellten gegenüber der vollständigen Liste je nach Snapshot unterscheidet, werden hier Bestand und Identität verglichen, nicht die Anzahl der Nutzer. Die Berechnung in Abschnitt 08.\n\n03 – Die Leiter\nDas andere Produkt ist die Zahl neben deinem Namen\n\nKarten sind der Rohstoff. Das Endprodukt hat die Stufe Steam, und Valve legt den Preis pro Set fest.\n\n100Steam Stufe\nZielwert – ziehen oder die Pfeiltasten verwenden\nPreis für ein komplettes Set, USD\n\n$0.20 ist das günstigste Komplettset in der Erhebung, $0.74 der Median, $1.70 der Mittelwert. Die Angabe bezieht sich ausschließlich auf die Karten – keinesfalls auf die $5.00 Freischaltungen oder die Spiellizenzen.\n\n55,000XP erforderlich\n550Verbrauchte Komplettsätze\n110Spiele zum Sammeln – selbst farmen\n$407.00Kosten der Karten zu diesem Preis\n1,100Abzug für verbrannte Zuteilungen, Mindestbetrag\n$5,500.00$5.00 wird freigeschaltet, wenn kein Konto wiederverwendet wird\nVerbrauchte Komplettsätze, Stufe 1 bis 1,000\n\nEin Abzeichen-Bastelprojekt = ein komplettes Set = 100 XP. Jede Stufe innerhalb einer Zehnergruppe kostet 100 XP mehr als die Stufe in der darunterliegenden Gruppe.\n\n0\n12,625\n25,250\n37,875\n50,500\n1\n250\n500\n750\n1000\n667\n550 sets\n\nEin Level ist keine Dekoration, die Valve einfach so stehen lässt. Er ist fest mit dem Account verknüpft. Aus Valves eigener FAQ zu Sammelkarten, in der erklärt wird, was man durch das Herstellen eines Abzeichens erhält: „100 XP, wodurch sich dein Level Steam erhöhen kann. Wenn sich dein Level Steam erhöht, wird die Obergrenze für die Anzahl der Einträge in deiner Freundesliste um fünf erhöht., und möglicherweise schaltest du damit die Möglichkeit frei, dein Profil mit Showcases individuell zu gestalten.\" Und zum Thema Booster-Packs: „Deine Stufe Steam erhöht die Wahrscheinlichkeit, ein Booster-Pack zu erhalten: Stufe 10: +20%… Stufe 50: +100% Erhöhung deiner Drop-Rate (d. h., die Wahrscheinlichkeit hat sich verdoppelt).“\n\nDas Level steuert also zwei Dinge Valve: wie viele Freunde man haben darf und wie schnell kostenlose Karten in das Inventar gelangen. Der zweite Faktor verstärkt sich – je mehr Sets du verbraucht hast, desto schneller stellt dir die Plattform weiteres Material zur Verfügung. Valve hat den Reinvestitionskreislauf in das Produkt integriert.\n\nDer Wechselkurs ist festgesetzt und wird veröffentlicht. Ein Abzeichen-Bastelvorgang verbraucht ein komplettes Set und bringt 100 XP ein; „Du kannst ein Set für dasselbe Spiel höchstens fünfmal zusammenstellen.“ Die Kosten für ein XP-Level steigen alle zehn Level. Daraus ergibt sich Folgendes, wobei es sich hierbei um keine Schätzwerte handelt:\n\nSteam Stufe\tKomplette Sätze, die er verbraucht\tSpiele, die du besitzen musst, um sie selbst herzustellen\tBei dem günstigsten jemals verzeichneten Kurs ($0.20)\tAm Medianpunkt ($0.74)\tMaßstab\n10\t10\t2\t$2.00\t$7.40\t\n50\t150\t30\t$30.00\t$111.00\t\n100\t550\t110\t$110.00\t$407.00\t\n200\t2,100\t420\t$420.00\t$1,554.00\t\n500\t12,750\t2,550\t$2,550.00\t$9,435.00\t\n667\t22,579\t4,516\t$4,515.80\t$16,708.46\t\n\n667 ist kein hypothetischer Wert. Es ist die höchste Stufe, auf die ein einzelner Bot im öffentlichen Verzeichnis angibt, einen Kunden bringen zu können – und zwar aus den 33,359 Sets, die er in 6,117 Spielen besitzt. Die vierte Spalte gibt den Preis dieser Rangliste im Vergleich zum günstigsten vollständigen Satz in der gesamten Erhebung an; die fünfte im Vergleich zum Median. Bei beiden handelt es sich um Marktpreise ausschließlich für die Karten, wobei die $5.00-Freischaltung und die Spielelizenzen vollständig unberücksichtigt bleiben.\n\nWie wurde die Kurve überprüft, da Valve sie nicht veröffentlicht?\n\nValve gibt die Abzeichenquote an („Für jeweils 100 XP erhältst du ein zusätzliches Steam Level.“) und sichert diese dann ab — „(zumindest am Anfang)“ — ohne die Eskalation zu veröffentlichen. Die oben verwendete Kurve ist die Standardkurve, bei der jede Stufe innerhalb eines Zehnerblocks 100 XP mehr kostet als der darunterliegende Block. Sie wurde anhand des Verzeichnisses überprüft und nicht einfach angenommen: Für jeden Bot, dessen angegebenes Maximum durch seinen Vorrat und nicht durch die Obergrenze von fünf Handwerken pro Spiel begrenzt ist, Der anhand dieser Kurve berechnete Wert stimmt exakt mit dem Wert überein, den der Bot angibt. — 541 zu 541, 494 zu 494, 464 zu 464. Dort, wo stattdessen die Obergrenze greift, liegt der berechnete Wert um einige Stufen höher, was bei einer Obergrenze, die auch von der Spieleranzahl pro Spiel abhängt, zu erwarten ist. Über Level 667 hinaus werden keine Aussagen zur Kurve getroffen.\n\nLies dir die Tabelle neben Abschnitt 02 durch, dann wird die Struktur des Geschäftsmodells deutlich. Um ein Konto auf Stufe 500 zu bringen, muss jemand 12,750 komplette Sets zusammenstellen. Für jedes dieser Sets wurden mindestens die Drop-Kontingente von zwei Konten benötigt, wobei jedes dieser Konten die $5.00-Schwelle überschritten hatte und jedes das Spiel besaß. Eine Prestigezahl oben in einem Profil basiert auf mindestens 25,500 darunter liegenden verbrauchten Drop-Kontingenten. Valve verliert dieses Geschäft nicht. Valve ist die Gegenpartei für jeden Teil dieses Geschäfts.\n\n04 – Die Statistiken\nIn dieser Klausel wird die Landwirtschaft nicht vage beschrieben, sondern konkret aufgezählt.\n\n§ 4.C ist keine allgemeine Anti-Bot-Klausel. In den dort aufgeführten Beispielen werden nacheinander die beiden Dinge genannt, die eine Kartenfarm produziert.\n\n„Es ist Ihnen untersagt, Skripte, Bots, Makros oder andere nicht von Menschen gesteuerte Systeme („Automatisierung“) jeglicher Art zu verwenden, um in irgendeiner Weise mit den Inhalten und Diensten auf Steam zu interagieren, einschließlich, aber nicht beschränkt auf:\n\nAutomatisierung des Steam-Kontoeröffnungsprozesses,\nFälschung von Spielstatistiken (z. B. überhöhte Sieg- oder Niederlagenzahlen, XP, Spielzeit),\nBelohnungen oder Fortschritte zu erzielen, ohne dass echte Nutzerbeiträge vorliegen,\n„Die Teilnahme an Bewertungssystemen (wie Peer-Reviews oder ‚Overwatch‘) durch automatisierte Mittel, einschließlich der Beeinflussung von Ergebnissen oder der Meldung von Nutzern durch skriptgesteuerte Aktionen anstelle einer fundierten Beurteilung.“\n— Steam Abonnentenvertrag § 4.C ↗ archiviert 2026-09-24 ↗ · wörtlich übernommen und zitiert 2026-09-22\n„…Spielzeit“\n\nLeerlaufstunden sind keine Phantomstunden. Die ASF-FAQ beantwortet diese Frage direkt — „Warum steigt die Spielzeit bei Spielen, die über ASF farmen, nicht an?“ — mit: „Das tut es zwar, aber nicht in Echtzeit. Steam zeichnet deine Spielzeit in festgelegten Intervallen auf und plant die Aktualisierung entsprechend … normalerweise erfolgt die Aktualisierung etwa alle 30 Minuten.“\n\nDiese Stunden werden in den Aufzeichnungen von Valve, auf den Shop-Seiten von Valve und in den Zahlen zu den gleichzeitigen Spielern erfasst, die Valve selbst veröffentlicht. Steam Diagramme ↗ archiviert 2026-09-23 ↗. In diesen Zahlen lassen sich inaktive Konten nicht von aktiven Konten unterscheiden. Die von der Plattform nach außen kommunizierten Nutzerzahlen werden auf der Grundlage einer Gesamtzahl berechnet, die nach den eigenen Regeln der Plattform auch Konten umfasst, die nicht aktiv sind.\n\n„…ohne echte Rückmeldungen der Nutzer“\n\nDas ist eine Definition des Begriffs „Idled Card Drop“, verfasst von Valve. Es handelt sich dabei auch um eine Definition der Stufe Steam, des Abzeichens, der Berechtigung zum Erhalt von Booster-Packs und der damit verbundenen Profil-XP – die ASF-FAQ bestätigt diese Definition. „sichert die Möglichkeit, Booster-Packs zu erhalten“, da es sich genauso anmeldet wie der offizielle Client.\n\nDas Belohnungssystem und die verbotene Handlung sind also ein und derselbe Mechanismus, betrachtet aus zwei verschiedenen Blickwinkeln. Valve legte fest, dass die Belohnung durch Zeit und nicht durch Können erzeugt werden sollte, und fügte dann eine Klausel hinzu, die die Erzeugung von Belohnungen durch alles andere als eine Person, die diese Zeit aufwendet, verbietet.\n\n05 – Die Falle der gewerblichen Nutzung\nJeder Ausgang von einer bewirtschafteten Karte ist ein Ausgang, den die Lizenz verbietet – und Valve erhebt am Eingang eine Gebühr.\n\nDas ist der Punkt, der sich nicht durch „verantwortungsbewusstes“ Farmen lösen lässt. Die Lizenz gilt für den persönlichen, nicht kommerziellen Gebrauch, und eine Karte lohnt sich erst dann zum Farmen, wenn sie nicht mehr nur für den persönlichen Gebrauch bestimmt ist.\n\n§ 2.A – die Lizenz\n\n„Valve gewährt Ihnen hiermit – und Sie nehmen diese an – eine nicht-exklusive Lizenz und das Recht, die Inhalte und Dienste für Ihre persönliche, nichtkommerzielle Nutzung (es sei denn, die kommerzielle Nutzung ist hierin oder in den geltenden Abonnementbedingungen ausdrücklich gestattet).“\n\n§ 2.G – Die Einschränkung\n\n„Sie sind nicht berechtigt: … (iii) die Inhalte und Dienste oder Teile davon für kommerzielle Zwecke zu nutzen, sofern in dieser Vereinbarung (einschließlich etwaiger Abonnementbedingungen oder Nutzungsbedingungen) nicht ausdrücklich etwas anderes gestattet ist.\"\n\n§ 3.D – Die Gebühr\n\n\"Valve kann für Transaktionen auf einem Abonnement-Marktplatz eine Gebühr erheben. Etwaige Gebühren werden Ihnen vor Abschluss der Transaktion mitgeteilt.\"\n\nLiest man die drei zusammen, wird die Position geschlossen.\n\nEine Karte, die behalten wird, ist für eine Farm wertlos. Eine Karte, die verkauft, getauscht oder zu Edelsteinen zermahlen wird, wurde zur Wertschöpfung genutzt – und Valve hat in seinem eigenen Mahnschreiben selbst erklärt, wie es das nennt: Dem Betreiber von 170 Bots wurde mitgeteilt, dass das Konto „wurde dazu genutzt, auf Steam illegal Sammelkarten zu sammeln sowie damit verbundene und nicht nur kommerzielle Aktivitäten durchzuführen.“ In diesem Fall kamen die Karten auf den Markt. Die Verkäufe wurden abgewickelt. Die Gebühr wurde eingezogen. Das Verbot folgte erst danach.\n\nDie Gebühr an dieser Tür beträgt nicht 15%. Bei einer „Farmed“-Karte beläuft sie sich auf zwei Drittel.\n\n§ 3.D Rücklagen „eine Gebühr“. Bei den Karten, die ein Bauernhof tatsächlich produziert, entspricht diese Gebühr bei weitem nicht dem beworbenen Wert von ~15%. Der Community-Markt nimmt eine 5% Steam Transaktionsgebühr und eine 10% Spielgebühr, jeweils mit einem Mindestbetrag von $0.01 (Valves eigene FAQ zum Community-Markt). Auf einer Karte, die für einen Cent angeboten wird, sind diese Etagen sind Der Preis: Der Käufer zahlt drei Cent, von denen zwei auf Gebühren entfallen. Durch die Abrundung nach unten wird der in der Überschrift angegebene Wert 15% zu einer effektiven Abgabe, die auf 66.7% genau dort, wo der Kartenmarkt spielt – ein paar Cent pro Karte.\n\nEffektive Gebühr bei einem Verkauf auf dem Community-Markt, basierend auf dem Angebotspreis des Verkäufers\n\n5% Steam + 10% Spiel, jeweils mindestens $0.01. Der schattierte Bereich zeigt an, wo Sammelkarten tatsächlich getauscht werden – etwa $0.03–$0.05 pro Karte.\n\n0%\n10%\n20%\n30%\n40%\n50%\n60%\n70%\ncards\n$0.01\n$0.10\n$0.20\n$0.30\n$0.40\n$0.50\n66.7%\nDer Verkäufer möchte\tSteam 5% (min. $0.01)\tSpiel 10% (Min. $0.01)\tDer Käufer trägt die Kosten\tGesamtgebühr\n$0.01\t$0.01\t$0.01\t$0.03\t66.7%\n$0.03\t$0.01\t$0.01\t$0.05\t40.0%\n$0.05\t$0.01\t$0.01\t$0.07\t28.6%\n$0.08\t$0.01\t$0.01\t$0.10\t20.0%\n$1.00\t$0.05\t$0.10\t$1.15\t13.0%\n\nDie Spielgebühr von 10% geht an die App, die die Karte ausgegeben hat; die 5% gehört Valve, und bei den eigenen Titeln und Basis-Inventargegenständen von Valve geht die gesamte Gebühr an Valve. So oder so geht das Geld dem „Farmer“ verloren – der Verkauf einer Drei-Cent-Karte bringt einen Cent ein und kostet zwei. Multipliziert man das mit den Hunderttausenden von Verkäufen von Karten unter fünf Cent, die ein „Farm“ generiert, und „die Gebühr, die Valve erheben darf“ ist das Geschäftsmodell, keine Fußnote. Quelle: Steam Community Market – Häufig gestellte Fragen (FAQ) – Gebühren ↗ archiviert 2026-09-21 ↗, lies 2026-09-22; die Kurve basiert auf diesen beiden veröffentlichten Zinssätzen und deren $0.01-Mindestzinssätzen.\n\nEs gibt keine Konfiguration des Tools, die dem entgeht. Es kann von einer einzigen Person auf einem einzigen Konto mit äußerster Zurückhaltung betrieben werden – und in dem Moment, in dem diese Person eine einzige „gefarmte“ Karte gegen Guthaben im Wallet verkauft, trifft sie derselbe Satz in § 2.G wie den Betreiber von zehntausend Karten. Valve hat sich somit einen Verstoß vorbehalten, den es gegen praktisch jeden Kartenverkäufer auf seinem eigenen Markt geltend machen könnte, und hat es abgelehnt, diesen gegen praktisch alle von ihnen geltend zu machen. Eine Regel, die in diesem Umfang durchgesetzt wird, ist keine Regel. Sie ist eine Option. Die Frage, die diese Ausstellung aufwirft, lautet nicht, warum „Card-Farmer“ toleriert werden; sondern warum genau diese Maßnahme gegen einen einzelnen Nutzer ergriffen wird, der eine Karte verkauft, während die kommerzielle Kartenwirtschaft, die von diesen Karten profitiert – die Handelsdienste, die Level-Up-Bots, die Großverkäufer – offen weiterläuft, wobei eine ihrer größten Gruppen von einem Valve-Mitarbeiter moderiert wird (§ 08). Der Verstoß wird dem Kleinbesitzer angelastet, während für die Maschine darauf verzichtet wird.\n\n06 — Die Vollstreckungsakte\nOhne Vorwarnung, in Wellen, und es breitet sich über die Telefonnummer aus\n\nValve hat die Befugnis zur Kündigung ohne Vorankündigung direkt in den Vertrag selbst aufgenommen, und zwar in der Klausel unmittelbar nach der Automatisierungsklausel.\n\n„Valve kann Ihr(e) Konto(s) oder ein bestimmtes Abonnement einschränken oder kündigen, wenn Sie sich rechtswidrig verhalten oder Aktivitäten ausüben, die einen Betrug oder den Einsatz von Automatisierung darstellen oder gegen die Steam-Regeln für das Online-Verhalten verstoßen. Sie erkennen an, dass Valve nicht verpflichtet ist, Sie vor der Kündigung Ihres Abonnements bzw. Ihrer Abonnements und/oder Ihres Kontos zu benachrichtigen.\"\n\n— Steam Abonnentenvertrag § 4.D ↗ archiviert 2026-09-24 ↗ · wortgetreu überprüft 2026-09-22\n\n1,000+ Bots · Handelsverbot. „Es sieht so aus, als wäre dieses Konto zur Verwaltung eines Netzwerks von Bot-Konten genutzt worden. Der Einsatz von Bots stellt einen Verstoß gegen die Steam-Nutzungsbedingungen dar.“\n\nÜber 170 Bots · dauerhaft gesperrt, Winter-Sale 2017. „Dieses Konto wurde dazu genutzt, auf Steam illegal Sammelkarten zu sammeln sowie damit verbundene und nicht ausschließlich kommerzielle Aktivitäten durchzuführen. Das Konto wurde dauerhaft gesperrt, und der Steam-Kundendienst kann zu diesem Thema keine weitere Unterstützung leisten.“\n\nÜber 120 Bots · dauerhaft gesperrt. „Dieses und andere Konten wurden dazu genutzt, unsere Netzwerkinfrastruktur zu überlasten, was einen Verstoß gegen die Online-Verhaltensregeln Steam darstellt.“\n\n— Steam Support-Nachrichten, die in den ArchiSteamFarm FAQ unter der Rubrik „Wurde jemand deswegen gesperrt?“ wiedergegeben sind. Quelle ↗ · wortgetreu überprüft 2026-09-22\nFall 4 – Juni 2025, VAC Verbote für inaktiviertes CS2\n\nEin Vorfall, der nach den drei oben genannten stattfand, ist im projektinternen Tracker verzeichnet: Accounts, die Counter-Strike 2 lediglich über das Tool im Leerlauf laufen ließen, erhielten VAC Sperren — im Sinne der Betrugsbekämpfung, nicht im administrativen Sinne. Der Betreuer vertritt die Auffassung, dass Leerlauf keinen solchen verursachen kann, da er „macht nichts anderes, als Steam mitzuteilen, dass wir das jeweilige Spiel spielen.“ Die Ursache ist umstritten. Dass die Konten gesperrt wurden, ist unbestritten.\n\n— ArchiSteamFarm Diskussion Nr. 3440, eröffnet am 26. Juni 2025 ↗ · lesen 2026-09-22\n\nWie ein Hauptkonto stirbt\n\nIm selben Thread beschreibt ein Projektmitarbeiter die Regel zur Weitergabe: Konten können gesperrt werden „nach Kette“, sofern sie dieselbe Telefonnummer verwenden — „Es könnte sich lediglich um eine VAC-Sperre handeln, die auf ‚saubere‘ Konten übertragen wurde, die mit dem gesperrten Konto in Verbindung stehen.“\n\nSteam Guard erfordert eine Telefonnummer. Die „Farms“ basieren auf der Telefonnummer des Betreibers. Die Durchsetzung beschränkt sich also nicht auf die Wegwerfkonten: Sie verfolgt die gemeinsame Kennung bis zu dem Konto, das die Bibliothek, die Freundesliste und das Inventar enthält. Das ist der Mechanismus, den ein Projektmitarbeiter beschreibt, wie eine einzige Aktion das Hauptkonto eines Betreibers zusammen mit der Farm entfernt – und das ist der Grund, warum der Verlust bei einer Durchsetzungswelle nicht in $5-Konten gemessen wird. (Beschrieben von einem Projektmitarbeiter in der ASF-GitHub-Diskussion Nr. 3440; es gibt keine offizielle Bestätigung von Valve oder einen formellen Präzedenzfall in den Unterlagen.)\n\nDerselbe Absatz, im Abstand von fünf Jahren, von drei verschiedenen Maklern\n\nDie Klausel, wonach landwirtschaftliche Nutzung einen Verstoß darstellt – nämlich die gewerbliche Nutzung einer privaten, nicht gewerblichen Lizenz –, gilt nicht nur für landwirtschaftliche Betriebe. Sie ist der Standardgrund, den Steam angibt, wenn ein Konto wegen gewerblicher Nutzung geschlossen wird, und dieser Grund wird als Vorlage bereitgestellt. Im Folgenden sind drei Beispiele aufgeführt, die von den Empfängern im Abstand von jeweils fünf Jahren von drei namentlich genannten Vertretern veröffentlicht wurden.\n\nNachricht vom Steam-Support am 29. September um 19:56 Uhr\n\n„Das Konto, von dem aus Sie schreiben, wurde wegen Verstoßes gegen die Bestimmungen der Steam-Nutzungsvereinbarung gesperrt. Anhand von Handelsaktivitäten, Meldungen aus der Community und weiteren Faktoren wurde festgestellt, dass das Konto für kommerzielle Zwecke genutzt wird.“\n\nDiese Sperre ist dauerhaft und Steam Der Support kann Ihnen in dieser Angelegenheit nicht weiterhelfen.\n\nDa wir alle uns zur Verfügung stehenden Informationen bereitgestellt haben, schließe ich diese Hilfeanfrage. Bitte beachten Sie, dass Sie zu diesem Thema keine weiteren Antworten mehr erhalten werden.\n\nMit freundlichen Grüßen,\n„Hal“\n\nDiese Hilfeanfrage wurde geschlossen.\n29. September 2020. Vom Empfänger gepostet mit dem Kommentar „RIP Trading.“ — @gergelyszabo94 ↗\nMitteilung vom Support Steam am 12. Juli um 22:41 Uhr\n\n„Das Konto, von dem aus Sie schreiben, wurde aufgrund eines Verstoßes gegen die Bestimmungen der Steam-Abonnentenvereinbarung gesperrt. Anhand von Handelsaktivitäten, Meldungen aus der Community und weiteren Faktoren wurde festgestellt, dass das Konto für kommerzielle Zwecke genutzt wird.“\n\nDiese Sperre ist dauerhaft und Steam Der Support kann Ihnen in dieser Angelegenheit nicht weiterhelfen.\n\nDa wir alle uns vorliegenden Informationen bereitgestellt haben, schließe ich diese Hilfeanfrage. Bitte beachten Sie, dass zukünftige Hilfeanfragen bezüglich der Kontosperrung möglicherweise ohne Antwort geschlossen werden.\n\nSteam Support\n„Vido“\n\nDieser Hilferuf wurde geschlossen.\n12. Juli 2024, portugiesische Benutzeroberfläche. Der Empfänger ist ein professioneller CS2-Spieler: „Ich habe mich bereits an den Steam-Support gewandt, erhalte aber nur automatische Antworten … Ich kann weder Faceit spielen noch an Profispielen teilnehmen.“ — @prcs25 ↗ archiviert 2024-07-15 ↗\nZitiert vom Empfänger, r/steamsupport\n\n„Hallo, das Konto, von dem aus Sie schreiben, wurde aufgrund eines Verstoßes gegen die Bestimmungen der Steam-Abonnentenvereinbarung gesperrt. Anhand von Handelsaktivitäten, Meldungen aus der Community und weiteren Faktoren wurde festgestellt, dass das Konto für kommerzielle Zwecke genutzt wird.\n\nDiese Sperre ist dauerhaft und Steam Der Support kann Ihnen in dieser Angelegenheit nicht weiterhelfen.\n\nDa wir alle uns vorliegenden Informationen bereitgestellt haben, schließe ich diese Hilfeanfrage. Bitte beachten Sie, dass zukünftige Hilfeanfragen bezüglich der Kontosperrung möglicherweise ohne Antwort geschlossen werden.\n\nSteam Support\n„Sally“\n\nDreimal erhalten, auf drei separate Anfragen hin.\n29. März 2025. Der Verfasser legte keine Beschwerde gegen die Sperrung ein – sein Konto war zusammen mit seiner E-Mail-Adresse gestohlen worden, und er bat um wiederhergestellten Zugriff: „Ich frage nicht nach der Sperre und ich stelle sie auch nicht in Frage. Ich möchte lediglich Zugriff auf mein Steam-Konto… Valve haben mir bei jeder Anfrage genau diese Antwort gegeben – kopiert und eingefügt – und die Anfrage dann geschlossen.“ — r/steamsupport ↗, die im Beschwerde-Korpus dieser Untersuchung enthalten sind\n\nWort für Wort, Komma für Komma, über fünfundfünfzig Monate hinweg, mit drei Agenten und zwei Schnittstellensprachen. Die einzige Änderung im gesamten Text ist die Präzisierung des letzten Satzes hinsichtlich der Jahre 2020 und 2024, von „Sie werden keine weiteren Antworten erhalten“ zu „Zukünftige Hilfeanfragen … werden möglicherweise ohne Antwort geschlossen.“ Unabhängig davon, welcher Prozess zu diesen Entscheidungen geführt hat, ist der Brief keine Aufzeichnung davon. Als Gründe werden „Handel, Meldungen aus der Bevölkerung und sonstige Faktoren“ genannt – eine Kategorie, ein Bericht unbekannter Herkunft und ein nicht näher bezeichneter Rest.\n\nFünf weitere Fälle, die auf dieselbe Weise zusammengetragen wurden. Die ersten drei gehören zur selben Kategorie und weisen dasselbe Ergebnis auf; die letzten beiden stammen von derselben Stelle und beziehen sich mit denselben Worten auf eine andere Vorschrift:\n\nDatum\tWas der Account getan hat\tWas ist passiert?\tQuelle\n04.12.2021\tKaufen und Verkaufen auf Buff — „Ich habe nichts anderes gemacht als ein bisschen auf Buff, auch bekannt als P2P-Handel, zu kaufen und zu verkaufen.“\tCommunity-Sperre: kein Markt, kein Handel, teure Lagerbestände gesperrt\tr/csgomarketforum ↗ archiviert 2025-03-27 ↗\n06.12.2021\tEinweg-P2P-Tauschgeschäfte über Buff und Bitskins für Ausrüstungen und Upgrades\tDauerschloss für gewerbliche Nutzung plus Gemeinschaftsschloss: „Ich stecke in einem quasi unsichtbaren Modus fest … Mein Profil ist außerdem weiterhin auf ‚privat‘ eingestellt.“\tr/GlobalOffensiveTrade ↗ archiviert 2021-12-06 ↗\n20.12.2024\tKonto seit 2017, Tausende von Stunden; Tauschgeschäfte auf Community-Marktplätzen für themenbezogene Ausrüstungen und Upgrades\tDauerhafte Sperre mit Gemeinschaftssperre, ohne vorherige Warnung oder Verwarnung; Unterstützung „sagen, ihre Entscheidung sei endgültig“, die Antworten erfolgen automatisch\tr/csgomarketforum ↗ archiviert 2025-06-27 ↗\n23.12.2024\tEin wiederkehrender Nutzer lädt nach einjähriger Abwesenheit über ein VPN Guthaben auf sein Wallet auf „nur für die allgemeine Internetsicherheit“\tDauerhafte Sperre aus der Community mit Es wurde überhaupt kein Grund angegeben: „Die Sperre ist dauerhaft, sie können keine weiteren Informationen bereitstellen, und weitere Tickets werden möglicherweise ohne Antwort geschlossen.“ 196 Likes, 340 Antworten\tr/steamsupport ↗\n04.08.2026\tJahrelange Einkäufe aus dem Iran; der Verfasser gibt an, dass er nie etwas gepostet, den Marktplatz nie genutzt und die Foren nie genutzt habe\tZugang zur Community gesperrt bis 2038 über „sanktionierte Regionen“; Das Ticket wurde von einem Mitarbeiter namens Azul geschlossen. Eine Rückerstattung für dasselbe Konto von derselben iranischen IP-Adresse war bereits ein Jahr zuvor genehmigt worden. Die Bibliothek und das Geld bleiben bei Valve.\tr/pcgaming ↗\n\nDie letzte Zeile weicht von den übrigen ab – es geht um die Einhaltung von Sanktionen, nicht um die kommerzielle Nutzung – und wurde aufgenommen, weil die Struktur der Antwort identisch ist: eine Kategorie, keine Beweise, kein Einspruch, ein geschlossenes Ticket. Außerdem wirft sie eine Frage auf, die die anderen nicht aufwerfen. Wenn die Betreuung des Kontos rechtswidrig war, war auch die Annahme der jahrelangen Zahlungen rechtswidrig. Eine dieser beiden Positionen muss falsch sein, und nur eine davon hat dem Kunden Kosten verursacht.\n\nAlle acht wurden am 2026-09-22 eingesehen – die Threads aus den Jahren 2021 und Dezember 2024 über Snapshots des Internet Archive und die übrigen über eine öffentliche Reddit-Benutzeroberfläche, da Reddit direkte Anfragen des sammelnden Hosts abgelehnt hatte. Die beiden Briefe aus den Jahren 2020 und 2024 wurden anhand der Screenshots transkribiert, die den Originalbeiträgen beigefügt waren, welche nach wie vor online sind. In dieser Untersuchung wird keinem dieser Konten Unschuld oder Schuld unterstellt – genau darum geht es. Weder der Leser noch die Aufsichtsbehörde kann dies dem Brief entnehmen.\n\nAnmerkung zur Datenherkunft – Verluste auf Betreiberebene\n\nDie im Rahmen dieser Untersuchung befragten Betreiber geben Verluste in der Größenordnung von jeweils fünf- bis zehntausend Konten in einzelnen Vollstreckungswellen, wobei die Hauptkonten zusammen mit dem landwirtschaftlichen Betrieb berücksichtigt wurden. Diese Umfrage wird hier als Bericht aus erster Hand erfasst, nicht als Ergebnis. Es gibt keine veröffentlichte Stichprobengröße, keinen festen Erhebungstermin und keine Überprüfung pro Konto, und keine andere Zahl auf dieser Seite hängt davon ab; die beiden Zeilen in Abschnitt 02, die darauf basieren, sind entsprechend gekennzeichnet.\n\nDies wird aus zwei Gründen ausdrücklich erwähnt und nicht einfach übergangen. Der oben beschriebene Mechanismus des Kettenverbots ist die dokumentierte Erklärung für genau dieses Muster. Und eine Aufsichtsbehörde kann von Valve die eine Aufzeichnung einfordern, die Klarheit schaffen würde: Wie viele Konten wurden im Rahmen der Automatisierung gesperrt, in welchen Phasen, und wie viel hatte jedes dieser Konten im Geschäft ausgegeben, bevor es geschlossen wurde? Solange diese Aufzeichnung nicht vorliegt, bleibt die Zahl, wie sie ist – gemeldet, zugeschrieben und unbewiesen.\n\n07 – Die Asymmetrie\nBeide Seiten desselben Schreibtisches\n\nVergleichen Sie diesen Beweisstandard mit dem Valve, der auf die eigene Unterstützungsoperation angewendet wurde. Die rechte Spalte ist das Vorfallregister dieses Dossiers, das mit den dort enthaltenen Vorbehalten wiedergegeben wurde.\n\nEin Kunde, für den Handel\n\nAcht dokumentierte Fälle, 2020–2026\n\nVerhalten\nVerkauf oder Kauf von Artikeln auf Marktplätzen von Drittanbietern; in einem Fall lag überhaupt kein Verhalten vor – das Konto war gestohlen worden.\nVorgelegte Beweise\nKeine. „Basierend auf Handelsdaten, Berichten aus der Community und weiteren Faktoren.“\nHinweis\nKeine. Valve hat in § 4.D Folgendes vorbehalten: „Valve ist nicht verpflichtet, Ihnen vor der Kündigung eine Mitteilung zu machen.“\nBerufung\n„Diese Sperre ist dauerhaft und Steam Der Support kann Ihnen in dieser Angelegenheit nicht weiterhelfen.“\nFahrkarte\nBei der ersten Antwort abgeschlossen. Weitere Anfragen „kann ohne Antwort geschlossen werden.“\nReichweite\nProfil, Freundesliste, Chat, Marktplatz, Inventar und alle mit echtem Geld gekauften Gegenstände.\nDauer\nDauerhaft.\nEine automatisierte Bot-Flotte für hohe Volumina\n\n694,673 vollständige Sets im öffentlichen Bestand über 91 Bots verteilt\n\nVerhalten\nAutomatisierte Headless-Skripte werden gleichzeitig auf Tausenden von Konten ausgeführt, um Karten in den Ruhezustand zu versetzen, Abzeichen in großem Umfang zu erstellen und Sets im industriellen Maßstab zu tauschen.\nVorgelegte Beweise\nÖffentlich zugängliche Bot-Verzeichnisse (steam.supply, SteamLvlUp) und öffentliche Gruppen mit Millionen von Mitgliedern.\nHinweis\nKeine Einmischung. 88.97% unterliegen keinerlei Verbot; 99.8% der verbleibenden Sperren sind rein kosmetischer Natur.\nBerufung\nNicht erforderlich. Die Flotten sind über ihren mehrjährigen Lebenszyklus hinweg ohne Unterbrechung im Einsatz.\nFahrkarte\n—\nReichweite\nUneingeschränkter Austausch von Inventar, Levelaufstieg durch Abzeichen und Marktliquidität.\nNutzen für Valve\n$26.8M+ Mindestumsatz im Shop ($5.00 Zugangstor pro Konto) plus 15% Kürzungen bei Transaktionen auf dem Community-Markt.\nDie Frage, die sich daraus ergibt, lässt sich ganz einfach so formulieren:\n\nEinzelkunden, die Karten oder Gegenstände manuell handeln, müssen mit einer dauerhaften, unanfechtbaren Sperre gemäß § 4.C (Automatisierung) oder § 2.G (kommerzielle Nutzung) rechnen. Eine automatisierte „Farming“-Flotte, die über Tausende von Konten hinweg „Headless“-Bots einsetzt, operiert offen mit einer „Unberührungsrate“ von 88.97%. Valve ist der Begünstigte beider.\n\nDie Asymmetrie ist wirtschaftlicher Natur: Einzelne Händler ziehen Wert aus der Plattform ab, während automatisierte Kartenflotten Millionen in das Shop-Ausgabetor von Valve ($5.00 pro Konto) pumpen und bei jedem Weiterverkauf Transaktionsgebühren generieren. Die Durchsetzung richtet sich nicht nach den schriftlichen Regeln, sondern nach dem Erlösmodell.\n\n08 — Unternehmensführung\nWer regelt den Kartenumlauf?\n\nDie sich in diesem Dossier wiederholende Erkenntnis – dass die Drittanbieter-Ebene um Steam aus dem Inneren von Steam besetzt wird – gilt auch für die Kartenwirtschaft und führt zu einer ganz konkreten Schlussfolgerung: Niemand, der unabhängig ist, kann nachverfolgen, was die Durchsetzungsmaßnahmen von Valve tatsächlich bewirken, da die Partei, die dies nachverfolgen könnte, innerhalb dieser Ebene angesiedelt ist. Alle nachstehenden Fakten wurden aus den eigenen öffentlichen Gruppen- und Profilseiten von Valve auf 2026-09-22 entnommen und können von jedem in einem Browser nachvollzogen werden.\n\nEin Valve-Mitarbeiter moderiert die größte Gruppe zum Kartentausch Valve Mitarbeiter\n\nCardTrades ↗ beschreibt sich in seiner eigenen Kopfzeile als die „Steam Offizielle Gruppe zum Kartentausch“ und trägt 97,114 Mitglieder. Die dort aufgeführten Moderatoren – also die Konten, die die Kontrolle über diese Gruppe haben – sind Mickmane, SgtFopper und afarnsworth ↗.\n\nDieses letzte Profil wird durch die Markierung auf der eigenen Website von Valve als Mitarbeiter von Valve gekennzeichnet – die Seite enthält class=\"profile_header_valve_employee\" — gibt seinen Standort an als Bellevue, Washington, und gehört zur Valve, Steam und Steam Sammelkarten-Gruppe Gruppen. SteamID64 76561197960434622, Mitglied seit dem 12. September 2003.\n\nDiese Feststellung ist struktureller Natur, nicht persönlicher, und sie ist nicht Ein wichtiger Punkt: Der Moderator einer Kartentauschgruppe betreibt keinen Bot, und nichts deutet hier auf das Gegenteil hin. Es geht um die Klausel in Abschnitt 07. Steam „Card Exchange“ ist ein kommerzieller Kartendienst eines Drittanbieters; der Handel mit Karten über Dienste von Drittanbietern ist genau das Verhalten, für das Valve normale Konten dauerhaft sperrt gemäß „für kommerzielle Zwecke genutzt, basierend auf Handelsaktivitäten, Community-Berichten und anderen Faktoren.“ Ein Mitarbeiter mit der Kennung „0“ hat eine offizielle Moderatorenrolle in der offiziellen Community-Gruppe dieses Dienstes, die 97.000 Mitglieder zählt.\n\nHier wird gegen keine Person der Vorwurf eines Fehlverhaltens erhoben., und es werden keine Rückschlüsse darauf gezogen, was diese Rolle beinhaltet. Die Asymmetrie ist die Feststellung: Wenn ein gewöhnliches Konto mit einem Kartendienst oder Skin-Dienst eines Drittanbieters in Berührung kommt, lautet die Antwort ein geschlossenes Ticket und eine dauerhafte Sperre ohne Vorlage von Beweisen; wenn es sich um diesen Dienst handelt, steht ein Mitarbeiter von Valve auf der Moderatorenliste und die Vereinbarung ist auf einer Seite sichtbar, die Valve selbst veröffentlicht. Die Frage lautet wie überall sonst in diesem Dossier: Legen Sie die schriftliche Genehmigung vor, falls es eine gibt – und falls keine erforderlich ist, teilen Sie dies schriftlich mit, denn acht Personen in Sektion 06 wurde das Gegenteil mitgeteilt.\n\nDie Sperrliste und wer sie verwaltet Ehrenamtlicher ModeratorDienst eines Drittanbieters\n\nDie Gruppe von Steambans.com (archiviert) ↗ (live ↗ archiviert 2025-12-03 ↗) hält seine Abstammung in der erhaltenen Gruppenbeschreibung fest: „Die offizielle Steambans.com Steam-Community-Gruppe. SteamBans.com ist ein brandneuer Dienst, der auf einem alten Konzept basiert. Globale Sperrlisten sind seit Jahren im alten WONID-Programm von VALVe aktiv. Als die Umstellung auf STEAMID erfolgte, lag es für uns nahe, einen Dienst zu entwickeln, der speziell auf dieses neue System zugeschnitten ist. Aber wir wollten noch mehr. *. Archivseite für Steambans, das 2013 eingestellt wurde.“ Zu den aufgeführten Verwaltern gehören devicenull und killahinstinct_ ↗.\n\nDieses Administratorkonto ist nicht ein Valve-Mitarbeiter – er ist nicht als Mitarbeiter gekennzeichnet. Es handelt sich um einen ehrenamtlichen Mitarbeiter mit ungewöhnlich hohem Ansehen: ein Mitglied von Community-Moderatoren (414 Mitglieder, als Gruppe bezeichnet „Erstellt von den Community-Moderatoren von Steam“), aus Wiki-Koordinatoren, von Steam Community-Markt, sowie der Valve-Programm- und Vorabveröffentlichungsgruppen, darunter Valve Pipeline, Steam Client-Beta, Mobile Auth Beta, Neue Steam Community-Beta-Version, Steam Labore, Steamworks und Betrügerische URLs melden. SteamID64 76561197960794555.\n\nEbenfalls innerhalb dieses Kreises und mit der direkten Anzeige von Steambans in seiner öffentlichen Gruppenliste: msart ↗ (Teilnehmerliste ↗), SteamID64 76561197977933359, in dessen Profil es mit eigenen Worten heißt „Ich betreibe steamid.uk und viele andere Websites, die sich mit Steam befassen oder auch nicht.“, und der ein vernetztes Netzwerk aus sechzehn Gruppen betreibt — SteamIDcouk (Hauptgruppe „Sid-Website“), SidAdmins, SidBans, steamideu, Steam3ID, s-id und SArchive darunter.\n\nsteamid.uk nennt diese Zahl selbst. In den FAQ heißt es: „Wer hat SteamID entwickelt? Die SteamID-Website, die Netzwerkinfrastruktur und die Sicherheitssysteme werden alle von 76561197977933359 verwaltet.“ Zwei Antworten weiter unten wird angegeben, woher die Daten stammen: „SteamID nutzt für die Datenerfassung in erster Linie die Steam-Web-API.“ Auf derselben Seite werden mehrere dedizierte Server bei verschiedenen Hosting-Anbietern, externe Entwicklungs-, Speicher- und Textsuchserver sowie eine separate Backup-Einrichtung beschrieben.\n\nBestätigt anhand von Aufzeichnungen aus dem Internet Archive: die Steambans-Gruppenübersicht vom 3. Dezember 2025 ↗, der Übersicht zum Betreiberprofil vom 14. September 2024 ↗, und die steamid.uk – FAQ-Übersicht vom 1. April 2026 ↗, wobei die Daten direkt auf 2026-09-22 ausgelesen werden.\n\nWas das alles bedeutet – und was nicht\n\nSperrlisten, die Auflösung von Steam-IDs und der Handel mit Karten sind die drei Dienste, die darüber entscheiden, wem vertraut wird, wer identifizierbar ist und welchen Wert ein Gegenstand hat. Keiner dieser drei Dienste wird von Valve betrieben. Bei jedem davon stammten die Personen, die die Kontrolle hatten, aus dem Umlaufbereich von Valve: ein mit einem Flag gekennzeichneter Valve-Mitarbeiter auf der Moderatorliste der offiziellen Gruppe des Kartendienstes; ein langjähriger Valve-Community-Moderator mit Zugriff auf das Pre-Release-Programm, der die Sperrlistengruppe verwaltet; der ID-Auflösungsdienst, der von einer Privatperson betrieben wird, die demselben Kreis angehört. Drei Dienste, drei Kontrollinstanzen, drei Personen Valve, denen bereits eine feste Stellung eingeräumt worden war.\n\nDie Mitgliedschaft in einer Gruppe ist kein Arbeitsverhältnis, und nichts davon ist als Vorwurf zu verstehen. Das ist eine Tatsache der Staatsführung, und genau das ist der Grund, warum das übliche Argument — Das sind Dritte, wir haben keinen Einfluss auf sie. — muss geprüft werden, anstatt einfach akzeptiert zu werden. Die Verantwortlichen sind mit Valve bestens vertraut. Valve ist in der Lage zu sagen, was es von ihnen verlangt hat, falls überhaupt etwas; niemand von außen ist in der Lage, dies herauszufinden.\n\nNiemand zählt. Das ist das Ergebnis.\n\nDer ID-Bereich Steam ist ein zusammenhängender Ganzzahlbereich. Diesen Bereich abzugehen und zu melden, wie viele Konten gesperrt sind, wie viele eingeschränkt sind und wie viel Bestand hinter einem Handelsverbot steckt, ist kein Forschungsprogramm – es ist eine Schleife und ein API-Schlüssel. Valve vergibt diesen Schlüssel selbst, unter steamcommunity.com/dev/apikey. Und doch Diese Volkszählung wird von keiner unabhängigen Stelle veröffentlicht. Weder eine Aufsichtsbehörde, noch ein Journalist, noch ein Wissenschaftler, noch eine Verbraucherorganisation. Die einzigen öffentlich zugänglichen Zahlen zum Umfang der Durchsetzungsmaßnahmen bei Steam sind diejenigen, die Valve erwähnt.\n\nDie Fähigkeit fehlt nicht. Sie wird zurückgehalten. Der Dienst, der den ID-Raum in großem Maßstab auflöst und indexiert – steamid.uk – erklärt in seinen eigenen FAQ, dass er „nutzt in erster Linie die Steam-Web-API zur Datenerfassung“ und betreibt sie auf mehreren dedizierten Servern, externen Speichersystemen, Text-Suchmaschinen und einer separaten Backup-Einrichtung. Es wird von einer Privatperson betrieben. Seine Schwestergruppe auf der Sperrliste wird gemeinsam von einem langjährigen Valve-Community-Moderator verwaltet, der Zugriff auf die Vorabversionen von Valve hat. Die einzige Partei, die in der Lage wäre, die Zahlen zu veröffentlichen, befindet sich im Einflussbereich von Valve und veröffentlicht sie nicht.\n\nDies entspricht genau dem Muster, das in dem Dossier überall sonst zu finden ist. Jeder Dienst, der eine tragende Entscheidung in Bezug auf die Steam-Wirtschaft trifft – wer vertrauenswürdig ist, wer identifizierbar ist, welchen Wert ein Gegenstand hat, wer gesperrt wird –, ist nominell ein Drittanbieter und steht praktisch in enger Verbindung zu Valve. Steam „Card Exchange“ bildet keine Ausnahme von diesem Muster; es ist ein weiteres Beispiel dafür. Das Argument, dass es sich um unabhängige Operatoren handelt, steht Valve gerade deshalb zur Verfügung, weil es noch niemandem gelungen ist, es anhand einer Zahl zu überprüfen.\n\nDie 10,88-Millionen-Konto-Erhebung: 88.97% Unberührt\n\nDie ArchiSteamFarm-Installationsbasis wurde bei Valve geprüft GetPlayerBans Endpunkt (10,880,610 Konten, 55 Minuten). Allein die unbegrenzte Teilmenge stellt dar $26.8M+ bei einem Mindestumsatz im Geschäft (Einstiegsschwelle $5.00). 9,680,599-Konten (88.97%) unterliegen keinerlei Sperre, und 99.8% der übrigen Fälle beinhalten lediglich kosmetische Community-Sperren, bei denen der automatisierte Handel weiterhin aktiv bleibt.\n\n5,360,499ASF-Mitglieder ohne Einschränkungen (angezeigte Anzahl von Steam)\n10,880,610Gesamtzahl der gescannten API-Einträge (begrenzt + unbegrenzt)\n9,680,599Wurde noch nie gesperrt (88.97%)\n1,200,011Jedes Steam-Verbot (11.0%) – 99.8% kosmetisch\n55 Min.Um die gesamte Bevölkerung zu erfassen, ist ein entscheidender Faktor\nForensische Beweise und umfassende Erhebung\n\nDie detaillierte demografische Aufschlüsselung – einschließlich Diagrammen zur Verteilung der Sperrarten, zum Alter der Konten zum Zeitpunkt der Durchsetzung, zu Clustern nach Erstellungsjahr (2020–2026) und zu den von den Nutzern selbst gemachten Angaben zum Wohnort – ist in der entsprechenden Erhebungsstudie veröffentlicht.\n\nDie vollständige Liste der 10,88 Millionen Sperren aufrufen (Anlage VI) →Abschnitt 4 – Die Sperrung der Asset-ID →\n\nDie Frage, die man also stellen muss – und die nur von Valve beantwortet werden kann: Welcher Identifikator oder welche Berechtigung wurde entzogen, an welchem Datum, auf wessen Beschluss hin und welche messbaren Auswirkungen hatte dies auf die Betreiber, an die sich die Maßnahme richtete? — im Gegensatz zu den Auswirkungen auf alle Außenstehenden, die versuchten, die Zahlen zu ermitteln. Eine Änderung, die unabhängige Prüfungen zunichte macht, wird nicht dadurch neutral, dass sie als Sicherheitsmaßnahme angekündigt wurde. Das ist der Grund, warum die Volkszählung im obigen Abschnitt nicht existiert.\n\n09 — Methode und Grenzen\nWas gelesen wurde und was nicht behauptet wird\n\nJedes Zitat auf dieser Seite wurde aus der Live-Quelle auf 2026-09-22 entnommen und wörtlich wiedergegeben. Nichts hier stammt aus einem Web-Scrape, einer Marktplatz-Quelle oder einem privaten Datensatz.\n\nDie vier Datensätze und die darauf durchgeführten Berechnungen\n\nJede davon ist eine einzelne öffentliche Anfrage, die über ein Terminal reproduzierbar ist. Es wurde kein Konto verwendet, es erfolgte keine Anmeldung bei einem Marktplatz und es wurde kein Endpunkt aufgerufen, für den Anmeldedaten erforderlich waren.\n\nDatensatz\tWoher es stammt\tWas wurde daraus berechnet?\nKartenverzeichnis\n13,876 Spiele\tSteam Die von Card Exchange veröffentlichte Preisliste für Badges – derselbe Feed, der auch deren Öffentliche Preisseite ↗ archiviert 2026-08-04 ↗\tSpiele, bei denen Karten ausgegeben werden, Karten pro Set, verschiedene Kartentypen und der Marktpreis jedes vollständigen Sets. Medianwerte und die Gesamtsumme $23,586.57 bilden die rechnerische Grundlage dieser Untersuchung.\nSpielpreise\n13,713 gelöst\tValves eigener öffentlicher Store-Endpunkt, store.steampowered.com/api/appdetails, cc=us, nur das Preisfeld, in Stapeln\tMedian und Verteilung des Listenpreises eines Kartenspiels; die Anzahl der Spiele, bei denen sich das komplette Set besser verkauft als das Spiel selbst.\nBot-Bestand\n91 Bots, 694,673 Sätze\tDas öffentliche Verzeichnis der Card-Bots unter steam.supply/CardBots ↗, wie angezeigt, keine Anmeldung\tGesamtzahl der vorrätigen Sets, Mindestanzahl an Karten, Mindestgrenze für Ausfälle und Mindestgrenze pro Bot für einzelne Konten.\nGegenprüfung\n21 gemeinsam genutzte Bots\tsteamlvlup.net/cardbots ↗ archiviert 2026-02-10 ↗, ein unabhängiges Verzeichnis derselben Bots\tNur zur Überprüfung. Bei den 21 Bots, die auf beiden Listen aufgeführt sind, erklärt sich Aggregate Stock damit einverstanden, 0.03%; die größte Abweichung zwischen zwei einzelnen Bots beträgt 1.36%, was mit zwei Abfragen des aktuellen Bestands im Abstand von wenigen Minuten übereinstimmt.\n\nQuellenangabe, wie im zweiten Verzeichnis vorgeschrieben: Daten bereitgestellt von SteamLvlUp, lizenziert unter CC BY 4.0 archiviert 2026-09-23 ↗; hier lediglich als unabhängige Überprüfung der Bestandszahlen eines Dritten verwendet und insofern angepasst, als die Zeilen pro Bot aggregiert und verglichen statt originalgetreu wiedergegeben wurden. Steam „Card Exchange“ und „steam.supply“ sind oben per Link angegeben. Die Spielpreise stammen von Valve. Karten-, Spiel- und Setnamen sowie Bilder stammen von Valve oder den Verlagen und werden ohne Anspruch oder Lizenz als Marktdaten wiedergegeben.\n\nZwei geplante Messungen wurden nicht durchgeführt und werden nicht ersetzt. Steams eigene Endpunkte für den Community Market — Preisübersicht, Suche/Darstellung, Preisentwicklung — geben dem abrufenden Host keine Daten zurück, und Steam Community-Diskussionsseiten senden ihm einen HTTP-403-Fehler zurück, sodass keine Zahlen auf dieser Seite aus Live-Marktdaten stammen. Die Methode zur Ermittlung des Verkaufsvolumens, mit der die Kartenausgaben beim täglichen Reset gezählt worden wären, erfordert eine angemeldete Steam-Sitzung; Im Manifest dieser Untersuchung heißt es, dass keine Marktplatz-Anmeldedaten verwendet wurden, und diese Aussage wurde beibehalten. Der „Bot-Stock“-Boden ist das, was sich ohne einen solchen messen lässt.\n\nPrimärquellen\n\nSteam Abonnentenvertrag ↗ archiviert 2026-09-24 ↗ — § 2.A, § 2.G, § 3.D, § 4.C, § 4.D.\nSteam Support – Eingeschränkte Benutzerkonten ↗ — der Schwellenwert $5.00 und die Liste der eingeschränkten Merkmale.\nValve — Steam FAQ zu Sammelkarten ↗ — die Drop-Mechanik und die $9-Free-to-Play-Rate.\nArchiSteamFarm FAQ ↗ und Diskussion Nr. 3440 ↗.\nSteam Community-Gruppen- und Profilseiten, direkt lesbar, für Abschnitt 08.\nsteamid.uk FAQ, Internet-Archiv-Momentbild 2026-04-01 ↗.\nAcht Steam von den Empfängern veröffentlichte Hinweise zur Sperrung der Unterstützung, 2020–2026, sind mit ihren Links in Abschnitt 06 aufgeführt.\n\nWas nicht beansprucht wird\n\nFür Valve werden keine Umsatzzahlen aus dem „Card Farming“ geschätzt. Für keines der Tools wird eine Anzahl aktiver Konten angegeben, und die 1,39 Millionen Drop-Zuteilungen sind nicht Eine Aufstellung der Konten im Besitz des Betriebs – siehe den Hinweis in Abschnitt 02. Es wird niemandem ein Fehlverhalten vorgeworfen; wenn eine Person namentlich genannt wird, geschieht dies unter ihrem eigenen öffentlichen Steam-Namen, in ihrer eigenen öffentlichen Rolle und auf einer Seite, die Valve veröffentlicht. Für keines der acht gesperrten Konten in Abschnitt 06 wird behauptet, es sei unschuldig oder schuldig; die Feststellung bezieht sich auf den Brief, nicht auf das Konto. Die Zahlen zu den Betreiberverlusten in Abschnitt 02 stammen aus Eigenangaben und sind als solche gekennzeichnet unter die Beschaffungsnotiz. Die FAQ von steamid.uk wird aus einem Snapshot des Internetarchivs zitiert, da die Live-Seite durch eine Bot-Sperre geschützt ist. Es wird nicht behauptet, dass versucht wurde, eine Bestandsaufnahme der Sperren durchzuführen, und diese unterdrückt wurde – die Feststellung lautet lediglich, dass keine veröffentlicht wurde. Die Steam-Level-Kurve oberhalb von 667 wurde nicht modelliert.\n\nWarum das Werkzeug nicht das Thema ist\n\nArchiSteamFarm besagt, dass es „ist nicht durch Valve genehmigt“ und auf dieser Seite wird ihr nichts vorgeworfen. Es wird als Messinstrument verwendet, da es der einzige Akteur in dieser Wirtschaft ist, der die Abläufe öffentlich und schriftlich dokumentiert. Valve kann die gesamte Darstellung in einem Absatz zusammenfassen: Veröffentlichung der von ihm genehmigten kommerziellen Automatisierung sowie der Aufzeichnung pro Bediener darüber, was er im Übrigen unternommen hat.\n\nWeiterlesen: wie der Markt selbst bewertet wird → · die Preisskala und die Obergrenze für die Notierung → · Die Artikel Steam werden nicht →",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Eine Bot-Farm ist kein Leck in Valves Laden. Es ist ein Kunde."
          },
          {
            "level": 2,
            "id": null,
            "text": "Was ein Bauernhof eigentlich ist – Schritt für Schritt"
          },
          {
            "level": 3,
            "id": null,
            "text": "Einstieg"
          },
          {
            "level": 3,
            "id": null,
            "text": "Spiele kaufen"
          },
          {
            "level": 3,
            "id": null,
            "text": "Leerlauf\nDas Tool meldet das Konto im Steam-Netzwerk im Headless-Modus an, „analysiert deine Abzeichen“, erstellt die Liste der Titel, die sich zum Farmen eignen, und startet „Ein geeignetes Spiel spielen und regelmäßig überprüfen, ob das Spiel bereits vollständig durchgespielt ist.“ Die Beschreibung des Mechanismus durch den Betreuer: Es „tut nichts anderes, als Steam mitzuteilen, dass wir ein bestimmtes Spiel spielen.“"
          },
          {
            "level": 3,
            "id": null,
            "text": "Die Tropfen gehen zur Neige\nJeder Titel ist endlich. „Jedes Spiel hat eine festgelegte Anzahl an Karten, die man erhalten kann. Sobald man alle davon erhalten hat (etwa die Hälfte des gesamten Sets), lohnt es sich nicht mehr, das Spiel weiter zu spielen.“ Ein Bauernhof, der weiterhin produzieren will, muss ständig Titel kaufen. Das Kartenangebot wird durch Käufe begrenzt – das ist beabsichtigt und spielt Valve in die Hände."
          },
          {
            "level": 3,
            "id": null,
            "text": "Auszahlung\nDie Karte verlässt das Spiel auf eine von drei Arten: Sie wird auf dem Community-Markt verkauft, getauscht oder zu Edelsteinen zermahlen. In jedem Fall handelt es sich um eine Transaktion auf dem Abonnement-Marktplatz oder um einen Tausch, und § 3.D sieht folgende Gebühr vor: „Valve kann für Transaktionen auf einem Abonnement-Marktplatz eine Gebühr erheben.“ Dies ist der Schritt, der das Ganze zu einem Verstoß macht – siehe 05."
          },
          {
            "level": 2,
            "id": null,
            "text": "Bevor ein landwirtschaftlicher Betrieb auch nur einen Cent verdient, hat er bereits Valve gezahlt"
          },
          {
            "level": 3,
            "id": null,
            "text": "Wie groß das Kaufobjekt tatsächlich ist"
          },
          {
            "level": 3,
            "id": null,
            "text": "Wie groß ist eine Menge?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Was die Lizenz kostet"
          },
          {
            "level": 3,
            "id": null,
            "text": "Was das fertige Set zurückgibt"
          },
          {
            "level": 3,
            "id": null,
            "text": "Wo sich die 694,673-Sätze befinden"
          },
          {
            "level": 3,
            "id": null,
            "text": "Was dieser Boden aussagt und was nicht"
          },
          {
            "level": 3,
            "id": null,
            "text": "Und bei den Preisen von Valve rechnet sich die Landwirtschaft nicht aus."
          },
          {
            "level": 3,
            "id": null,
            "text": "Was der Betrieb tatsächlich am Leben erhält"
          },
          {
            "level": 4,
            "id": null,
            "text": "Spielverkäufe"
          },
          {
            "level": 4,
            "id": null,
            "text": "„Online“ & Spielzeit"
          },
          {
            "level": 4,
            "id": null,
            "text": "Anmeldungen"
          },
          {
            "level": 4,
            "id": null,
            "text": "Guthaben im Wallet & Gebühren"
          },
          {
            "level": 4,
            "id": null,
            "text": "Steam-Level-PR"
          },
          {
            "level": 3,
            "id": null,
            "text": "Und die Auszahlung selbst ist ein Wertverlust Valve – doppelte Besteuerung"
          },
          {
            "level": 3,
            "id": null,
            "text": "Das ist nicht nur ein Moment. Es handelt sich um eine Branche mit einer langjährigen Tradition."
          },
          {
            "level": 3,
            "id": null,
            "text": "Vollständige Kartensätze im öffentlichen Bot-Verzeichnis, nach Steam Verkauf"
          },
          {
            "level": 3,
            "id": null,
            "text": "So sieht die Rangliste der Verkaufsabzeichen von ganz oben aus"
          },
          {
            "level": 3,
            "id": null,
            "text": "Und dieselbe Flotte ist auch dann vor Ort, wenn gerade kein Verkauf stattfindet"
          },
          {
            "level": 3,
            "id": null,
            "text": "Das Verzeichnis „resting“, Bot für Bot"
          },
          {
            "level": 2,
            "id": null,
            "text": "Das andere Produkt ist die Zahl neben deinem Namen"
          },
          {
            "level": 3,
            "id": null,
            "text": "Verbrauchte Komplettsätze, Stufe 1 bis 1,000"
          },
          {
            "level": 3,
            "id": null,
            "text": "Wie wurde die Kurve überprüft, da Valve sie nicht veröffentlicht?"
          },
          {
            "level": 2,
            "id": null,
            "text": "In dieser Klausel wird die Landwirtschaft nicht vage beschrieben, sondern konkret aufgezählt."
          },
          {
            "level": 3,
            "id": null,
            "text": "„…Spielzeit“"
          },
          {
            "level": 3,
            "id": null,
            "text": "„…ohne echte Rückmeldungen der Nutzer“"
          },
          {
            "level": 2,
            "id": null,
            "text": "Jeder Ausgang von einer bewirtschafteten Karte ist ein Ausgang, den die Lizenz verbietet – und Valve erhebt am Eingang eine Gebühr."
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 2.A – die Lizenz"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 2.G – Die Einschränkung"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 3.D – Die Gebühr"
          },
          {
            "level": 3,
            "id": null,
            "text": "Liest man die drei zusammen, wird die Position geschlossen."
          },
          {
            "level": 3,
            "id": "fee-ladder",
            "text": "Die Gebühr an dieser Tür beträgt nicht 15%. Bei einer „Farmed“-Karte beläuft sie sich auf zwei Drittel."
          },
          {
            "level": 3,
            "id": null,
            "text": "Effektive Gebühr bei einem Verkauf auf dem Community-Markt, basierend auf dem Angebotspreis des Verkäufers"
          },
          {
            "level": 2,
            "id": null,
            "text": "Ohne Vorwarnung, in Wellen, und es breitet sich über die Telefonnummer aus"
          },
          {
            "level": 3,
            "id": null,
            "text": "Fall 4 – Juni 2025, VAC Verbote für inaktiviertes CS2"
          },
          {
            "level": 3,
            "id": null,
            "text": "Wie ein Hauptkonto stirbt"
          },
          {
            "level": 3,
            "id": null,
            "text": "Derselbe Absatz, im Abstand von fünf Jahren, von drei verschiedenen Maklern"
          },
          {
            "level": 3,
            "id": null,
            "text": "Anmerkung zur Datenherkunft – Verluste auf Betreiberebene"
          },
          {
            "level": 2,
            "id": null,
            "text": "Beide Seiten desselben Schreibtisches"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ein Kunde, für den Handel"
          },
          {
            "level": 3,
            "id": null,
            "text": "Eine automatisierte Bot-Flotte für hohe Volumina"
          },
          {
            "level": 3,
            "id": null,
            "text": "Die Frage, die sich daraus ergibt, lässt sich ganz einfach so formulieren:"
          },
          {
            "level": 2,
            "id": null,
            "text": "Wer regelt den Kartenumlauf?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ein Valve-Mitarbeiter moderiert die größte Gruppe zum Kartentausch Valve Mitarbeiter"
          },
          {
            "level": 3,
            "id": null,
            "text": "Die Sperrliste und wer sie verwaltet Ehrenamtlicher Moderator Dienst eines Drittanbieters"
          },
          {
            "level": 3,
            "id": null,
            "text": "Was das alles bedeutet – und was nicht"
          },
          {
            "level": 3,
            "id": null,
            "text": "Niemand zählt. Das ist das Ergebnis."
          },
          {
            "level": 3,
            "id": null,
            "text": "Die 10,88-Millionen-Konto-Erhebung: 88.97% Unberührt"
          },
          {
            "level": 3,
            "id": null,
            "text": "Forensische Beweise und umfassende Erhebung"
          },
          {
            "level": 2,
            "id": null,
            "text": "Was gelesen wurde und was nicht behauptet wird"
          },
          {
            "level": 3,
            "id": null,
            "text": "Die vier Datensätze und die darauf durchgeführten Berechnungen"
          },
          {
            "level": 3,
            "id": null,
            "text": "Primärquellen"
          },
          {
            "level": 3,
            "id": null,
            "text": "Was nicht beansprucht wird"
          },
          {
            "level": 3,
            "id": null,
            "text": "Warum das Werkzeug nicht das Thema ist"
          }
        ],
        "links": [
          "https://help.steampowered.com/en/faqs/view/71D3-35C2-AD96-AA3A",
          "https://github.com/JustArchiNET/ArchiSteamFarm/wiki/FAQ",
          "https://steamcommunity.com/tradingcards/faq/",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260924114457/https://store.steampowered.com/subscriber_agreement/",
          "https://steamladder.com/ladder/badges/2861690/",
          "http://web.archive.org/web/20260716205303/https://steamladder.com/ladder/badges/2861690/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/farm-economy-timeline.json",
          "https://store.steampowered.com/charts/",
          "http://web.archive.org/web/20260923183013/https://store.steampowered.com/charts/",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://github.com/JustArchiNET/ArchiSteamFarm/discussions/3440",
          "https://x.com/gergelyszabo94/status/1311004678633795585",
          "https://x.com/prcs25/status/1811893857253982720",
          "http://web.archive.org/web/20240715122902/https://x.com/prcs25/status/1811893857253982720",
          "https://reddit.com/r/steamsupport/comments/1fjmgc5/what_to_do_when_your_steam_account_gets_hacked/mkelm2y/",
          "https://www.reddit.com/r/csgomarketforum/comments/r87owv/psa_my_steam_account_just_got_banned/",
          "http://web.archive.org/web/20250327203008/https://www.reddit.com/r/csgomarketforum/comments/r87owv/psa_my_steam_account_just_got_banned/",
          "https://www.reddit.com/r/GlobalOffensiveTrade/comments/r9xql9/d_recently_received_commercial_ban_for_what_seems/",
          "http://web.archive.org/web/20211206034804/https://www.reddit.com/r/GlobalOffensiveTrade/comments/r9xql9/d_recently_received_commercial_ban_for_what_seems/",
          "https://www.reddit.com/r/csgomarketforum/comments/1hhxx7m/d_permanently_locked_on_steam_for_commercial_use/",
          "http://web.archive.org/web/20250627014045/https://www.reddit.com/r/csgomarketforum/comments/1hhxx7m/d_permanently_locked_on_steam_for_commercial_use/",
          "https://www.reddit.com/r/steamsupport/comments/1hkctwt/permanent_ban_with_no_explanation/",
          "https://www.reddit.com/r/pcgaming/comments/1vf24lu/warning_to_all_gamersexpats_steam_took_my_money/",
          "https://steamcommunity.com/groups/card-trading-card-trades",
          "https://steamcommunity.com/id/afarnsworth",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/groups/steambans",
          "https://steamcommunity.com/groups/steambans",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/id/killahinstinct_",
          "https://web.archive.org/web/20240914124859/https://steamcommunity.com/id/msart",
          "https://steamcommunity.com/id/msart/groups/",
          "http://web.archive.org/web/20260401154714/https://steamid.uk/faq/",
          "https://phishdestroy.io/steam_dossier/de/enforcement_audit.html",
          "https://phishdestroy.io/steam_dossier/de/#evidence-blackout",
          "https://www.steamcardexchange.net/index.php?badgeprices",
          "http://web.archive.org/web/20260804200309/https://www.steamcardexchange.net/index.php?badgeprices",
          "https://steam.supply/CardBots",
          "https://steamlvlup.net/cardbots",
          "http://web.archive.org/web/20260210171205/https://steamlvlup.net/cardbots",
          "https://steamlvlup.net/",
          "https://creativecommons.org/licenses/by/4.0/",
          "http://web.archive.org/web/20260923221628/https://creativecommons.org/licenses/by/4.0/",
          "https://phishdestroy.io/steam_dossier/de/market_economics.html",
          "https://phishdestroy.io/steam_dossier/de/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/de/elite_skins.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/de/card_economy_de.content.json",
      "export_json_sha256": "3ae705b03a80bf2c3ff7cb65b3aee5e053d3db748466a2fcb03f843b51e38526"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "elite_skins.html",
      "language": "en",
      "title": "One item, two price systems — The Steam Dossier",
      "source_url": "https://phishdestroy.io/steam_dossier/elite_skins",
      "source_html_sha256": "5325f5d401d8206da62821caeca5987f21a51d05c3699d6ecd825968c364c0bb",
      "exported_at": "2026-09-29T00:15:48.936Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "register",
            "source": "https://phishdestroy.io/steam_dossier/elite_skins#register"
          },
          {
            "id": "",
            "source": "https://phishdestroy.io/steam_dossier/elite_skins#selected"
          }
        ],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "elite_skins.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/en/elite_skins.pdf?v=print-20260929-v5",
        "sha256": "52c97282d542d72a09e3fd3308f6b9bd455c16538503e0a14d00c7fd4282cecb",
        "bytes": 91548,
        "pages": 7
      },
      "integrity": {
        "signed_object": "elite_skins.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "elite_skins.content.json.asc",
        "digest_file": "elite_skins.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify elite_skins.content.json.asc elite_skins.content.json",
          "sha256sum -c elite_skins.content.json.sha256"
        ]
      },
      "content": {
        "text": "Dieses Material ist auf Englisch verfügbar.Zurück zum Dossier · Deutsch ↗\nEXHIBIT IV / MARKET ARCHITECTURE / 20 SEPTEMBER 2026\nElite Skins Register — The $1,800 Market Ceiling\n\nOne item. Two price systems.\n\nWHAT THIS SECTION PROVES\n\nThis register establishes an empirical census of all CS2 skin categories priced above Steam's $1,800 Community Market listing cap across five external exchanges. It proves that 248 corroborated high-tier categories—representing 18,394 active listings and $78.6 million in posted liquidity—are 100% absent from Valve's official marketplace. Sellers seeking true market prices are structurally forced onto external platforms while relying exclusively on Steam's underlying trade mechanics.\n\nWhat this means — the Community Market listing ceiling\n\nSteam’s own market refuses a listing above roughly $1,800. A seller may ask less, never more. Items whose market price sits above that line therefore cannot be sold at that price on Steam at all — which is the mechanism that moves those sales to third-party venues while the item itself never leaves Valve’s inventory system.\n\nSection 13 — the off-Steam price gap →\n\n← Back to Executive briefing\n\nSteam caps a Community Market listing at about $1,800. Across the five third-party marketplaces priced in this snapshot, 419 CS2 item categories carry a cheapest live ask above that limit — and 402 of them, 95.9%, have no Steam listing at all. Together they hold 18,641 listed copies worth at least $82.4 million. Requiring a second marketplace to agree before a price counts, 248 of those categories are corroborated — and every single one of them, 100%, is absent from Steam. The dearest is a Sticker | Titan (Holo) | Katowice 2014 at $66,285, quoted by four marketplaces within 5.2% of each other and carried by none of Valve's. The full ladder, the renders and the grading are in the price-ladder atlas.\n\nInspect all 419 entries ↓Open the atlas ↗Read the method\n248categories two or more marketplaces price above the cap\n18,394copies listed across five marketplaces\n$78.6Mfloor value of those listings\n100%of them absent from Steam entirely\n\nCorrection · this page previously led with an uncorroborated price\n\nAn earlier version of this page headlined a Souvenir AK-47 | Point Disarray asked at $148,954 on one marketplace while Steam priced it at $119. That row rests on a single shelf and a single copy with no second marketplace agreeing, so it is an asking price rather than a price, and it no longer carries the page. Every headline figure here is now restricted to the 248 categories that at least two marketplaces independently price above the cap. The row itself has not been removed — it is still in the register below, and the grading that demoted it is set out in full in the price-ladder atlas.\n\n01 / the money in active asks\nThe measurable dollar floor\n\nRecomputed from the licensed cs2.sh snapshot across five marketplaces. This is a minimum aggregate asking value in a defined subset, not sales turnover and not a valuation of the CS2 economy.\n\n248 CORROBORATED CATEGORIES · 18,394 LISTED COPIES · 5 MARKETPLACES$78.62M\n\nMinimum aggregate posted ask of every CS2 item that two or more marketplaces independently price above the limit Valve permits on its own market.\n\nWhy this is a floor, not an estimate\n\nFor each marketplace we multiply its lowest ask for an item by the number of copies that marketplace lists. Every other copy on that shelf is priced at or above the lowest ask, so the true posted value is higher — by construction, not by guesswork. It is not a sale, a cash flow or a market-wide valuation, and the same physical item may appear on more than one marketplace.\n\nCheck all 419 source rows ↗\n★ Sport Gloves | Hedge Maze (Field-Tested)\n$4.68M\nAWP | Gungnir (Factory New)\n$4.46M\nAWP | Dragon Lore (Factory New)\n$4.34M\n★ Butterfly Knife | Fade (Factory New)\n$4.17M\nAK-47 | Wild Lotus (Factory New)\n$4.16M\n★ Butterfly Knife | Doppler (Factory New)\n$3.64M\n\nBars show the six largest category-level contributions to the floor calculation, scaled against the largest. A high bar reflects both the cheapest ask and the number of copies listed. The same physical item can appear on more than one marketplace, so these figures must not be added to any other market total.\n\n02 / inspectable examples\nWhat the limit leaves out\n\nIllustrations correspond to exact item names where available. Prices are active asking prices from the dated catalogue, not transaction records.\n\n★ Butterfly Knife | Doppler (Factory New)\n\nSource: https://phishdestroy.io/steam_dossier/elite_skins#selected\n\nThe measurable gap: these offers cannot be matched by a Steam listing at the same USD figure. Valve’s own Community Market FAQ archived 2026-09-21 ↗ states an approximately $1,800 maximum listing price. A seller could still list below it; whether that would be acceptable is the seller’s choice. A separate CSMarketCap search for items above $1,800 ↗ shows Factory New Dragon Lore across 28 indexed markets with about 1.1K displayed offers; mirrored inventory can be counted more than once.\n\n03 / the structural dependency\nSteam's cap sends price discovery outside Steam\n\nThe comparison is structural. It neither assumes every asking price is fair nor treats unsold listings as revenue.\n\n01 · THE RULE\nSteam caps the listing\n\nValve says Community Market listings are capped at approximately $1,800. Wallet balances are also capped, and wallet funds cannot be withdrawn as cash.\n\n02 · THE OBSERVATION\nDragon Lore: $10,940.85\n\nThe 5-marketplace catalogue shows 389 live offers for AWP Dragon Lore (Factory New), starting at $10,940.85 (CSFloat floor). The wider register contains 248 corroborated categories above Steam's limit.\n\n03 · THE CONSEQUENCE\nPrice and transfer split\n\nA seller seeking that higher price cannot post it on Steam. External services can set the cash price, but delivery still uses Steam-controlled item ownership and transfer.\n\nThe policy contradiction: Valve's own Subscriber Agreement archived 2026-09-21 ↗ reserves commercial exploitation of Steam services unless expressly permitted, while its 2016 statement archived 2026-09-21 ↗ said gambling operators were already using Steam OpenID and automated accounts. That is direct evidence Valve knew of this class of outside operator in 2016. Yet the official marketplace cannot post the observed prices of these high-value items. That is architectural dependence on off-Steam price discovery and transactions; the contract status of each individual marketplace requires separate evidence. The two primary Western marketplaces capturing this over-cap transaction volume operate as formal corporate entities in major jurisdictions — CSFloat Inc. (incorporated in Delaware, USA) and Skinport GmbH (registered in Stuttgart, Germany, HRB 764879) — openly transacting hundreds of millions in peer-to-peer item sales relying directly on Steam Web APIs and trade infrastructure.\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\nThe four $100,000 rows sit at CSFloat’s own maximum listing price. They are marked in the register and must not be read as appraisals. The archived CSFloat listing crawl only reached approximately $6,999, so the public catalogue snapshot is used for the full >$1,800 register.\n\n04 / another Valve game\nThe ceiling also catches Dota 2\n\nThe same strict cheapest-offer test on Skinport finds 166 CS2 categories and 3 Dota 2 categories. They are a separate marketplace snapshot; do not add them to CSFloat’s 245.\n\nDOTA 2 · 1 OFFER\nHeroic Brutal Crescent\n\nCheapest Skinport ask: $14,622.25.\n\nDOTA 2 · 1 OFFER\nDark Artistry Cape\n\nCheapest Skinport ask: $8,255.16.\n\nDOTA 2 · 1 OFFER\nCorrupted Powered Star\n\nCheapest Skinport ask: $2,087.92.\n\nThese are three listed item categories, not every Dota 2 item in existence. Inspect the dated Skinport rows ↗ and API documentation ↗.\n\n05 / robustness\nThe finding does not depend on the exact cap\n\nValve sets the cap in the buyer's regional currency, so converted to USD it does not land on one clean figure. The census is therefore repeated at every plausible threshold. The share of these items missing from Steam never moves below 95%.\n\nThreshold tested\tItem categories\tCopies listed\tFloor value\tAbsent from Steam\n$1,800\t419\t18,641\t$82,449,526\t95.9%\n$2,000\t382\t15,159\t$75,541,325\t95.5%\n$2,070\t363\t12,336\t$69,560,305\t95.6%\n$2,300\t323\t11,644\t$67,984,432\t95.0%\n$2,500\t299\t10,950\t$66,203,929\t95.0%\n\nRead one row at a time; the rows are nested subsets of the same census, not separate populations. “Floor value” multiplies each marketplace's lowest ask by the number of copies it lists, so it understates the shelf by construction. Open the dataset ↗\n\n06 / scarcity you can count\nHow few of these actually exist for sale\n\nBUFF splits each item's shelf into float brackets and publishes how many copies sit in each. That turns “rare” from a word into a count — and prices the condition separately from the skin.\n\n298 COPIES LISTED\nAWP | Dragon Lore\n\n8 distinct variants priced. The dearest, Souvenir AWP | Dragon Lore (Factory New), asks $12,363 with 20 copies on the shelf.\n\nIn the best float bracket on the shelf (0–0.01) there are 2 copies, asking $17,875 — a +45% premium over the item's base ask for condition alone.\n\n607 COPIES LISTED\nM4A4 | Howl\n\n12 distinct variants priced. The dearest, Souvenir M4A4 | Howl (Factory New), asks $14,895 with 2 copies on the shelf.\n\n213 COPIES LISTED\nAK-47 | Wild Lotus\n\n7 distinct variants priced. The dearest, Souvenir AK-47 | Wild Lotus (Factory New), asks $14,895 with 2 copies on the shelf.\n\n310 COPIES LISTED\nAWP | Gungnir\n\n7 distinct variants priced. The dearest, Souvenir AWP | Gungnir (Minimal Wear), asks $14,895 with 2 copies on the shelf.\n\nWhy this matters to the rest of this dossier: these are not abstractions. A few hundred copies of each trophy exist on the open shelf worldwide, each tied to one Steam account and moved by one Steam trade. A market this thin is one where a single stolen inventory is a measurable event, and where the account-takeover techniques documented elsewhere in this investigation have a direct and quantifiable payoff.\n\nCounts are live listings on one marketplace at capture time, not the total number in existence. Copies held in private inventories are not counted anywhere here. Open the float dataset ↗\n\n07 / the ladder out of sight\nThe dearer the item, the further from any observable venue\n\nEach rung below is a different evidentiary class. They are deliberately not merged into one number.\n\nRung\tFigure\tWhat kind of fact this is\nCeiling on Valve's own market\t~$1,800\tPublished rule, stated in the Steam Community Market FAQ.\nDearest ask several marketplaces agree on\t$66,285\tMeasured by us in this snapshot. Sticker | Titan (Holo) | Katowice 2014, quoted by four marketplaces within 5.2% of one another. An ask, not a sale.\nDearest ask seen on any single shelf\t$148,954\tOne marketplace, one copy, no second marketplace agreeing — and equal to a round CNY 1,000,000 at the snapshot rate. Listed here as the outer edge of what sellers ask, and relied on for nothing.\nPublic marketplace sale\t$49,999\tSpecialist Gloves | Crimson Kimono (FN) on CSFloat, as reported by SteamAnalyst. Platform-recorded, third-party reported.\nReported private sale\t$400,000\tAK-47 | Case Hardened, reported by PC Gamer in April 2023. Journalism, not a record we hold.\nReported offer, declined\t$1,500,000\tBlue Gem Karambit, pattern #387. No sale took place and the figure has not been independently confirmed. Included to mark the ceiling of the claims, not to assert a value.\n\nThe structural point: Valve's market stops at about $1,800. Third-party marketplaces carry the trade to around $66,000 where several of them agree, and to roughly $150,000 where only one does. Above that there is no venue at all — the largest transfers of Valve-issued property happen privately, between individuals, with no listing, no platform record, no identity check and no reporting. The transfer itself still runs on Steam. The higher the value, the less anyone can see it, and the infrastructure carrying it is Valve's throughout.\n\nThe last two rungs are other people's reporting, cited as such. This project did not verify them and does not rely on them for any conclusion.\n\nAll 419 observed categories\n\nSource: https://phishdestroy.io/steam_dossier/elite_skins#register\n\n09 / provenance and limits\nCheck the calculation\n\nWe expose the local data and the public source. The numerical headline is scoped to CSFloat on the capture date.\n\nValve’s own ceiling and terms\n\nSteam Community Market FAQ ↗ archived 2026-09-21 ↗ states the approximate $1,800 listing maximum. The Subscriber Agreement ↗ archived 2026-09-21 ↗ sets the commercial-use restrictions.\n\nWhere the prices come from\n\nPrices, listing counts and float brackets are taken from the cs2.sh market data API under a paid commercial subscription, using a licensed key. No marketplace was scraped and no marketplace account or credential was used. The provider aggregates BUFF, Youpin, CSFloat, Skinport, C5Game and the Steam Community Market; all figures are USD as returned. Open the provenance manifest ↗ — it records the exact endpoints, capture times and SHA-256 hashes of the raw snapshots, so an independent reader with their own key can pull the same data and recompute every number on this page.\n\nWhat we could not obtain\n\nThe subscription purchased covers current snapshots only. Historical and archive endpoints were not available to us, and no claim about any trend, any past price or any change over time is made on this page. Everything here is a single moment, dated.\n\nThe earlier CSFloat register\n\nThe first version of this exhibit counted 245 categories from a single CSFloat catalogue snapshot dated 20 September 2026: that snapshot remains here ↗. The present register is wider because it spans five marketplaces rather than one. The two are separate captures and must not be added together.\n\nValve's specific enforcement statement\n\nValve's 2016 in-game item trading update ↗ archived 2026-09-21 ↗ addresses gambling operators using OpenID and automated Steam accounts. It is narrower than a ban on every outside marketplace.\n\nInterpretation boundary\n\nThese are offers, not sales. A market name can cover multiple physical items with different float, pattern or sticker details. This register does not measure total market value or Valve’s intent.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Elite Skins Register — The $1,800 Market Ceiling"
          },
          {
            "level": 2,
            "id": null,
            "text": "The measurable dollar floor"
          },
          {
            "level": 3,
            "id": null,
            "text": "Why this is a floor, not an estimate"
          },
          {
            "level": 2,
            "id": null,
            "text": "What the limit leaves out"
          },
          {
            "level": 3,
            "id": null,
            "text": "★ Butterfly Knife | Doppler (Factory New)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Steam's cap sends price discovery outside Steam"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam caps the listing"
          },
          {
            "level": 3,
            "id": null,
            "text": "Dragon Lore: $10,940.85"
          },
          {
            "level": 3,
            "id": null,
            "text": "Price and transfer split"
          },
          {
            "level": 2,
            "id": null,
            "text": "The ceiling also catches Dota 2"
          },
          {
            "level": 3,
            "id": null,
            "text": "Heroic Brutal Crescent"
          },
          {
            "level": 3,
            "id": null,
            "text": "Dark Artistry Cape"
          },
          {
            "level": 3,
            "id": null,
            "text": "Corrupted Powered Star"
          },
          {
            "level": 2,
            "id": null,
            "text": "The finding does not depend on the exact cap"
          },
          {
            "level": 2,
            "id": null,
            "text": "How few of these actually exist for sale"
          },
          {
            "level": 3,
            "id": null,
            "text": "AWP | Dragon Lore"
          },
          {
            "level": 3,
            "id": null,
            "text": "M4A4 | Howl"
          },
          {
            "level": 3,
            "id": null,
            "text": "AK-47 | Wild Lotus"
          },
          {
            "level": 3,
            "id": null,
            "text": "AWP | Gungnir"
          },
          {
            "level": 2,
            "id": null,
            "text": "The dearer the item, the further from any observable venue"
          },
          {
            "level": 2,
            "id": null,
            "text": "All 419 observed categories"
          },
          {
            "level": 2,
            "id": null,
            "text": "Check the calculation"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve’s own ceiling and terms"
          },
          {
            "level": 3,
            "id": null,
            "text": "Where the prices come from"
          },
          {
            "level": 3,
            "id": null,
            "text": "What we could not obtain"
          },
          {
            "level": 3,
            "id": null,
            "text": "The earlier CSFloat register"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve's specific enforcement statement"
          },
          {
            "level": 3,
            "id": null,
            "text": "Interpretation boundary"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/de/elite_skins.html",
          "https://phishdestroy.io/steam_dossier/de/#market-gap-section",
          "https://phishdestroy.io/steam_dossier/de/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/de/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/de/skin_atlas.html#grading",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-above-the-ceiling.json",
          "https://phishdestroy.io/steam_dossier/elite_skins#selected",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://csmarketcap.com/search?minPrice=1800&page=1",
          "https://store.steampowered.com/agreement/?l=english",
          "http://web.archive.org/web/20260921022032/https://store.steampowered.com/agreement/?l=english",
          "https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921021947/https://store.steampowered.com/oldnews/22883",
          "https://phishdestroy.io/steam_dossier/de/#proxy-bypass-explainer",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/skinport-floor-over-cap.json",
          "https://docs.skinport.com/items",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-float-scarcity.json",
          "https://phishdestroy.io/steam_dossier/elite_skins#register",
          "https://cs2.sh/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/csfloat-catalogue.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/en/elite_skins.content.json",
      "export_json_sha256": "fd689c51eee7fb22ea44f6388710d3458c21a9ee54db197fe9011f9e9ee4a2ba"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "enforcement_audit.html",
      "language": "en",
      "title": "The census Valve won't publish — The Steam Dossier",
      "source_url": "https://phishdestroy.io/steam_dossier/enforcement_audit",
      "source_html_sha256": "87e0765d22f3c432bced037023f0128abe682a83003d040530c2dcf6619e1a62",
      "exported_at": "2026-09-29T00:15:50.556Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "enforcement_audit.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/en/enforcement_audit.pdf?v=print-20260929-v5",
        "sha256": "45e43e7e4755e33092a3ff0af12f56ed9e9ed0b529e750c7c20d363c8216fc0d",
        "bytes": 139690,
        "pages": 11
      },
      "integrity": {
        "signed_object": "enforcement_audit.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "enforcement_audit.content.json.asc",
        "digest_file": "enforcement_audit.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify enforcement_audit.content.json.asc enforcement_audit.content.json",
          "sha256sum -c enforcement_audit.content.json.sha256"
        ]
      },
      "content": {
        "text": "Dieses Material ist auf Englisch verfügbar.Zurück zum Dossier · Deutsch ↗\nEXHIBIT VI — THE CENSUS VALVE WON'T PUBLISH\nEnforcement Audit — The 1,182,811 Ban Census\n\nWe didn't ask Valve how big the farm is. We counted it.\n\nWHAT THIS SECTION PROVES\n\nThis audit presents an empirical census of 1,182,811 banned accounts using Valve's official GetPlayerBans endpoint, cross-referencing commercial bot farming cohorts with documented fraud registries. It proves that over 63% of banned bots paid Valve's $5.00 store gating fee prior to enforcement, generating millions in initial revenue. Furthermore, among 51,732 convicted scammers documented in fraud registries, over 67% face zero community or trade bans—demonstrating that platform enforcement functions as commercial revenue extraction rather than victim restitution.\n\n← Back to Executive briefing\n\nThere is no published figure for how many automation accounts run on Steam. There is no need for one to be secret: the Steam ID space is a contiguous integer range and Valve hands out the Web API key that walks it. So we took the largest population that identifies itself — the ArchiSteamFarm community — and read every member once through Valve's own ban endpoint. It self-declares because ASF, on first launch, automatically joins the Steam group unless the user explicitly opts out or unchecks the group-join setting (AutoJoinSteamGroup / Statistics). Because this setting is active by default, group membership captures a broad population: active multi-account commercial bot networks, casual idling hobbyists, and ordinary players who ran the software on their personal account and never removed the default subscription. That makes its membership a working census of the software's cumulative reach: 10,880,610 total accounts (with 5,360,499 confirmed non-limited members past the $5.00 store gate). Then we asked the only question that matters — what has Valve actually done to them?\n\nWhat this page is not. It is not an argument that Valve should ban ten million people, and it is not a complaint about card farmers. Every number below is here for one reason: Valve does permanently ban individuals, and the reason it gives in writing is commercial use of Steam and automation. This measures how that same rule is applied to the same conduct at scale — by an operator whose $5.00 unlock, game licences and Market fees Valve collects on the way through. The finding is the asymmetry, not the farm.\n\nThe 10.88M countThe scammers who walk (53.5k)100k paid vs free audit\n10,880,610Total ASF group members read through Valve's own ban API (limited + non-limited combined)\n88.97%Have never been banned at all — 9,680,599 accounts still live\n63.06%Of banned accounts are paid ($5+ spend) — 100,000 SRSWOR slice (±0.39% MoE)\n67.77%Of 51,732 adjudicated scammers carry zero scam bans (full census)\n01 — The scale\nTen million accounts, and nine of ten untouched\n\nOne population that counts itself, read once through Valve's own endpoint.\n\nWHY IT SELF-COUNTS\nASF joins the group for you\n\nOn first run ArchiSteamFarm sets Statistics to true by default and joins the Archi's SC Farm Steam group. An operator has to actively opt out. So the membership is a floor on installs — not a ceiling. Operators who disabled Statistics are absent; the real install count is at least this large.\n\nWHAT WE READ\n10,880,610 total entries\n\nThe API member list returned 10,880,610 SteamID64s in total — both limited and non-limited. Steam's group page shows 5,360,499 (non-limited only). Every entry was passed once through ISteamUser/GetPlayerBans on 2026-09-23. Fifty-five minutes on one key.\n\nTHE ANSWER\n88.97% clean\n\n1,200,011 carry any Steam ban (11.03%). The other 9,680,599 have nothing on record at all — not a community ban, not VAC, nothing. The farm is not being cleared. It is being left running. The same clause, pointed at one person, is enough to remove them permanently.\n\nOf 10,880,610 accounts, how many Valve has touched\n\nThe whole scanned population, split by whether Valve has applied any ban at all. The red slice is everything Valve has ever done to this fleet.\n\n88.97%never banned\n11.03%\nNo ban of any kind — 9,680,599 (88.97%)Carries some Steam ban — 1,200,011 (11.03%)\n10,880,610ASF group members scanned\n9,680,599Never banned — 88.97%\n1,200,011Carry any ban — 11.03%\n55 minTo count all of it, on one API key\nWhat this fleet already paid Valve to exist\n\nNot an estimate of what the farm earns. A floor on what it has already spent in Valve's store — derived from Valve's own rule, applied to the count above.\n\nThe 10,880,610 count covers the full ASF group member list as returned by the API — this includes both limited and non-limited accounts. Steam's own Limited User Accounts page states that limited accounts do not count toward Steam group membership (they are excluded from the displayed group size), but they can still appear in the underlying member list. The non-limited subset — accounts that have spent at least $5.00 in the Steam store — is exactly 5,360,499 — the count Steam displays on the group page, which by Steam's own rule excludes limited accounts. The $5.00 floor calculation applies to that non-limited subset only.\n\n5,360,499non-limited members\n(Steam's displayed group count)\n×\n$5.00Valve's own minimum\nto stop being limited\n=\n$26,802,495floor on store spend\nby the non-limited subset\n\nThis is a lower bound on money already received by Valve from the non-limited fraction of the fleet — not a revenue estimate, not a profit claim. Actual spend per account is higher for most; the $5.00 figure is the minimum required threshold only.\n\nThe secondary harvest: up to 66.7% fee on farmed commodity volume. Beyond the $26.8M entrance fee, every card and commodity drop liquidating on the Community Market pays Valve a mandatory two-cent minimum fee floor ($0.01 Steam fee + $0.01 publisher fee). On typical 3-cent cards and junk items, Valve takes 2 cents out of 3 cents — an effective cut of 66.67% in Valve's favor, far exceeding the headline 15% marketing rate.\n\nCrucial population caveat: Group membership is not proof that every single account is a dedicated bot, nor does it capture every bot on Steam. ASF automatically subscribes accounts to its community group upon launch by default; unless the user explicitly unticks or disables that configuration flag (AutoJoinSteamGroup), regular players, one-time idlers, and community members remain on the roster alongside automated farming fleets. Furthermore, a Steam ban carries no public reason field. The finding is an empirical rate across this software-associated population, not an individual verdict on any single account. Aggregate, reproducible: asf-ban-census-2026-09-23.json.\n\n02 — Geography\nWhere the fleet lives\n\nOnly 8.5% of the banned accounts declare a country at all. Among the ones that do, the largest single share is the United States.\n\nA Steam profile carries an optional country field. 100,413 of the 1,182,811 banned accounts fill it in — 8.5%.† Among that minority the United States leads at 15.5%, then Ukraine, China and Russia, and the rest runs out into a long tail across Europe, Latin America and South-East Asia. Nobody verifies the field: Afghanistan sits in the top ten, which is roughly what it is worth. The other 91.5% are omitted rather than assigned, so what follows is the shape of a self-selected minority — not a map of the fleet, and not a basis for saying where it is run from.\n\nBanned accounts by declared country\n\nTop 15 countries among the 100,413 banned accounts that expose a public location. Share is of that located subset. Hover for counts.\n\n0%\n5%\n10%\n15%\n20%\nUnited States\nUkraine\nChina\nRussia\nCanada\nAustralia\nJapan\nBrazil\nGermany\nAfghanistan\nUnited Kingdom\nRomania\nFrance\nPhilippines\nIndia\n\nLocation read from GetPlayerSummaries for the banned subset. The field is set by the account holder and verified by nobody, so a VPN exit or a joke entry counts the same as a real one.\n\n03 — Freshness\nRecent accounts, not a legacy backlog\n\nDated by account-creation time, the banned population is recent, not a leftover from the trading-card era.\n\nIf this were an old mess being slowly cleaned up, the banned accounts would skew to the early trading-card years. They do the opposite. Of the 1,132,852 banned accounts that expose a creation date, 70% were created in 2020 or later, and nearly half since 2023. The count rises from 59,175 created in 2017 to a peak of 227,030 created in 2024 alone. Every one of them cleared the $5.00 store gate before it could receive a card, so the entry fee was collected on each.\n\nWhen the banned accounts were created\n\nAccount-creation year of the 1,132,852 banned members that expose a creation date. The mass is 2020–2026, not the 2013–2015 trading-card era. Peak: 2024. Hover for counts.\n\n0k\n63k\n125k\n188k\n250k\n'13\n'14\n'15\n'16\n'17\n'18\n'19\n'20\n'21\n'22\n'23\n'24\n'25\n'26\n70%Of banned accounts created in 2020 or later\n227,030Banned accounts created in 2024 — the peak year\n51,701The 2021 trough, between two peak years — unexplained\n2003→2026Range present, but the mass is the last six years\n\nCreation dates from GetPlayerSummaries for the banned subset, deduplicated by SteamID64. A creation date is when the account was made, not when it was banned or when it began farming; it is read here as evidence of how recent the population is, not of intent. Three things the chart does not show:\n\nA trend after 2024. An account made in 2025 or 2026 has had less time to collect a ban, and 2026 covers nine months — so 227,030 → 121,070 → 16,534 is censoring, not a decline.\nA ban rate. Creation years were read for banned accounts only, so there is no denominator. A growing install base alone would produce this shape.\nWhy 2021 collapsed. 51,701 sits between 105,821 and 104,641, under half of either neighbour. Nothing public explains it; it is left visible rather than smoothed.\n04 — Timing\nWhen Valve acts, it acts inside the first year\n\nThe obvious defence for 88.97% untouched is a backlog. The dated bans say otherwise.\n\nHow old the account was when the ban landed\n\nAccount age at the moment of the ban, for the 293,750 banned accounts that carry both a creation date and a dated last ban. Over half were caught inside the first year.\n\n0%\n10%\n20%\n30%\n40%\n<6 mo\n33.7%\n6–12 mo\n21.5%\n1–2 y\n20.6%\n2–5 y\n14.3%\n5 y+\n10.0%\n55.1% inside the first year\nBanned inside the first year — 55.1%Banned later — 44.9%\n0.80 yMedian age of the account when the ban arrived\n55.1%Banned inside the first year of the account\n33.7%Banned inside the first six months\n293,750Accounts where both dates are present\n\nThis is the answer to the obvious defence. If 88.97% of the fleet is untouched because enforcement is simply slow — a backlog working its way through — then the bans that do land would skew old. They do the opposite: the median banned account was nine and a half months old, and a third — 33.7% — were caught inside six months. When Valve acts on this population, it acts fast. The nine in ten still running are not waiting in a queue.\n\nAge at ban = creation date from GetPlayerSummaries subtracted from the ban date implied by DaysSinceLastBan, read on 2026-09-23. It is computed only where both values are present: 293,750 of the 1,200,011 banned accounts. The remaining accounts report no days-since value and are omitted, not assumed — so read this as the shape of the dated subset, not of every ban.\n\n05 — What the ban actually is\nWhen Valve does act, it doesn't stop the bot\n\nOf the 11% that carry any ban, look at which ban.\n\nA ban is not a ban. Of the 1,200,011 accounts Valve has flagged, 99.8% carry a community ban — a restriction on forums, profiles and groups that does nothing to a trading bot. The account can still receive cards, still trade, still move inventory. 22.2% carry at least one game ban and 3.9% a VAC ban; the categories overlap, so they do not sum. The one sanction that actually severs trading, the economy / trade ban, sits on 5,214 accounts. We are not resting the case on that number — trade bans are rare across Steam generally. The point of this chart is simpler: even the fraction Valve does touch keeps trading.\n\nWhat the 11% who are banned are actually banned for\n\nEach ban type as a share of all 10,880,610 scanned members. Accounts can carry more than one. Hover for counts.\n\n0%\n4%\n8%\n11%\n15%\nCommunity ban\nGame ban\nVAC ban\nEconomy / trade ban\n\nA Steam ban carries no reason field, so none of these bans is attributed to card farming specifically — this is the mix of ban types present, set beside what each type actually restricts. Community ban does not stop trading; the economy / trade ban does. Aggregate: asf-ban-census-2026-09-23.json.\n\n06 — The other population\nThe scammers Valve lets walk: The 51,732 Complete Census\n\nA second, independent list — community-confirmed fraud — measured against the same official API.\n\nThe automation population could be argued away as harmless idlers. The second population cannot. SteamRep is a long-running community reputation database; an account marked BANNED there has been adjudicated a scammer by that community, with documented victim proof and transaction chat logs. We completed a 100% census of all 51,732 profiles carrying that BANNED status against Steam's official Web API (ISteamUser/GetPlayerBans/v1) — and counted only the sanctions that address scamming. A VAC ban is for software cheating in a game (aimbots, wallhacks); it does nothing to a trader and is not evidence Valve acted on fraud, so it is not counted as fraud enforcement.\n\nAcross the entire 51,732-account census, 67.77% — 35,059 adjudicated scammers — carry ZERO scam-relevant bans from Valve: they can still trade, still send friend requests to new victims, still message. Only 32.23% were met with either a community or trade ban, and the trade ban — the one action that actually severs inventory transfers — sits on just 18.81% (9,731 accounts). An additional 12.81% (6,627 accounts) carry VAC or game bans purely for in-game cheating, while remaining completely unrestricted in Steam trading.\n\nConfirmed scammers, by whether Valve applied a scam-relevant ban (Full Census)\n\nAll 51,732 SteamRep-BANNED profiles, split by whether Valve applied a community or trade ban. VAC and game bans are excluded — they do not address fraud. Hover for counts.\n\n0%\n18%\n35%\n53%\n70%\nNo scam-relevant ban\nCommunity or trade ban\n0%\n6%\n13%\n19%\n25%\nCommunity ban\nTrade / economy ban\nVAC (not fraud)\nGame ban\n51,732SteamRep-BANNED profiles audited — 100% full census\n35,059Carry no scam-relevant ban (67.77%)\n18.81%Carry the trade ban that severs scams (9,731)\n32.23%The share Valve met with a community or trade ban (16,673)\n\nSteamRep is a third-party, community-adjudicated reputation database, not a Valve determination — which is the point: external evidence, measured against what Valve itself did. All 51,732 BANNED profiles from the canonical export were cross-referenced directly against ISteamUser/GetPlayerBans/v1. \"Scam-relevant\" means a community or economy/trade ban; VAC (12.81%) and game bans (3.86%) are counted separately because they address cheating, not fraud. Complete audit dataset: steamrep_steam_bans.csv.\n\nTwo populations, one finding\n\nThese are not the same people and not the same conduct. One is ten million automation accounts; the other is fifty-three thousand adjudicated scammers. What they share is the shape of the result: nine in ten farm accounts are never touched, and over two-thirds (67.77%) of confirmed scammers meet no sanction that addresses fraud. The community ban Valve does hand out freely restricts forums and profiles, not trading. The report button, the reputation database, the ban that stops a scam: all present, all under-used. Set that beside the archived refusals in the main dossier, where the same company permanently removes a single account and cites commercial use and automation as the reason — the clause is not dormant, it is pointed.\n\n07 — The $5.00 Account Gate & Account Hijacking\nThe 100,000-account empirical audit: botnets are not disposable free accounts\n\nStatistical sampling logic and mathematical proof: why taking any other 100,000 accounts yields the exact same result.\n\nValve's primary defense to regulators and consumer protection bodies has been that automated scams and farming are carried out by ephemeral, free \"throwaway\" accounts that are quickly banned. Under Valve's published rules, an account is Limited until it spends at least $5.00 USD in the Steam store, which locks it out of trading, friend requests, and API features. We audited this claim directly by testing the monetization status of a representative, mathematically rigorous sample of 100,000 banned Steam accounts drawn from our 1,182,811 profile metadata corpus.\n\nSAMPLING PROTOCOL (SRSWOR)\n100,000 Unbiased Slice\n\nDrawn from N = 1,182,811 unique banned Steam accounts using Simple Random Sampling Without Replacement via a cryptographically uniform PRNG. Every account had an identical inclusion probability of P = n / N ≈ 8.45%, completely eliminating survivorship and activity bias.\n\nMATHEMATICAL PROOF\nMargin of Error < ±0.4%\n\nApplying the Finite Population Correction (FPC) formula at a 99% Confidence Interval (Z = 2.576):\nMoE = Z × √[p(1-p)/n] × √[(N-n)/(N-1)] ≈ ±0.39%\n\nREPRODUCIBILITY\nWhy Any 100k Yields the Same\n\nBecause the margin of error is bounded under ±0.4% at 99% confidence, drawing any other independent 100,000-account sample is mathematically guaranteed to fall within 63.06% ± 0.39% (62.67% to 63.45%). The sample mirrors the entire 1.18 million banned population.\n\nThe audit results completely demolish the \"throwaway bot\" defense. Of the 100,000 accounts audited via Steam's legacy XML profile interface: 61,490 accounts (63.06% of classified accounts) are Non-Limited (Paid) accounts having spent at least $5.00 on Steam. Only 36,021 (36.94%) are limited free accounts, while 2,489 were unconfigured or private.\n\n100,000 Banned Accounts: Paid ($5+ Store Spend) vs Free Limited Status\n\nEmpirical audit of 100,000 randomly sampled banned accounts. Over 63% have cleared Valve's paid financial gate. Hover for counts.\n\n0%\n16%\n33%\n49%\n65%\nNon-limited (Paid ≥ $5.00)\nLimited (Free < $5.00)\n100,000Sampled population (SRSWOR, N=1.18M)\n63.06%Non-limited paid accounts (61,490 accounts)\n±0.39%Margin of error at 99% confidence interval\n~745,800Extrapolated paid accounts in 1.18M banned corpus\nThe Structural Reality: Industrial-Scale Account Liquidation\n\nWhy would 63% of the sampled banned accounts be paid accounts that spent real money in Valve's store? Botnet operators do not spend millions out of pocket on disposable accounts. This ratio highlights the volume of compromised and hijacked accounts circulating through the ecosystem.\n\nThis scale is directly observable on underground platforms: on marketplaces like FSB Market (an anonymized label; the original name is withheld here), over 550,000 Steam accounts (stealer logs, phishing captures, credential stuffing) are actively listed for sale at any given moment (phishdestroy.io/live-intel). The market authenticates buyers and sellers using Valve's own Steam OpenID, and neither FSB Market nor the associated forum is blocked by Valve's Link Filter.\n\nAs established in Section 06, Valve does not proactively eliminate this fraudulent activity: 67.77% of community-confirmed scammers carry zero scam bans on Steam, and 88.97% of the automation fleet remains completely untouched. The accounts circulate freely, authenticate through official APIs, and trade across the ecosystem with near-total impunity.\n\nForensic Evidence & Enforcement Architecture Diagram\nInteractive flow from 10.88M scanned accounts to 100k empirical slice and 53.5k confirmed scammers · Click links to inspect raw evidence\nTier 01 · 10.88M Automation Fleet Census\nThe largest self-identifying automation population on Steam, passed sequentially through Valve's official ban API. Proves that commercial bot fleets run with 88.97% impunity while paying tens of millions in entry fees.\n9,680,599 88.97% Active & Untouched\nAccounts running automated software that carry zero bans of any kind on record.\nRaw Census JSON (1.2 KB) ↗Inspect Section 01 ↗\n$26,802,495 Direct Store Revenue Floor\nCollected by Valve from 5,360,499 non-limited members past the minimum $5.00 entry threshold.\nCard Economy Audit ↗Valve $5 Rule FAQ ↗\n1,200,011 11.03% Flagged Subset\n99.8% carry cosmetic community bans only; trade remains open on 99.95% of accounts.\nBan Type Breakdown ↗Banned DB (60.4 MB) ↓\nTier 02 · 100,000-Account Empirical Sampling Audit (N = 1,182,811)\nRepresentative SRSWOR slice evaluated via legacy XML endpoints. Mathematically proven margin of error < ±0.4% at 99% confidence interval. Refutes the claim that banned bots are free throwaway accounts.\n61,490 (63.06%) Non-Limited Paid Accounts ($5+ Spend)\nOver 63% of banned accounts represent paid transactions. Extrapolates to ~745,800 paid accounts ($3.73M+ entry floor) in the banned pool.\nLimited Results CSV (2.1 MB) ↓100k Forensic Report ↗\n36,021 (36.94%) Limited Free Accounts (< $5.00)\nThe minority of banned profiles that fit Valve's \"disposable throwaway bot\" profile. 2,489 accounts were unconfigured/private.\n100k Sample Slice CSV (8.5 MB) ↓Spend Analysis MD ↗\n34.67% vs 63.93% Profile Sanitization Audit\nValve wiped nicknames to raw SteamID64 on 34,673 accounts, but left custom names & avatars completely untouched on 63,928 banned accounts.\nSanitization Section ↗Overview Roadmap ↗\n34.59% Legacy Aged Accounts (Created 2003–2019)\nOver a third of banned accounts were registered 5 to 20+ years ago, proving industrial-scale account hijacking of long-term Steam players.\nAge Chronology ↗Support Refusals ↗\nTier 03 · 51,732 SteamRep Confirmed Scammers Census\nFull 100% census of community-adjudicated fraudsters with victim chat logs and trade proof, cross-referenced against official Steam ban APIs. Proves systemic enforcement failure.\n35,059 (67.77%) Zero Scam Bans (Full Impunity)\nOver two-thirds of verified fraudsters carry neither Community nor Trade bans from Valve. Fully operational to trade and add victims.\nSteamRep API Bans (2.6 MB) ↓SteamRep Audit Report ↗\n9,731 (18.81%) Economy / Trade Bans\nThe only sanction that severs inventory liquidation. Present on less than a fifth of confirmed scammers.\nSteamRep Source (2.1 MB) ↓Inspect Section 06 ↗\n6,627 (12.81%) Irrelevant Cheating Bans (VAC Only)\nBanned for aimbots/wallhacks in games, while their Steam trade and phishing capabilities remain 100% active.\nVAC Irrelevance Analysis ↗Security Timeline ↗\nTier 04 · Wiki Defacement & August 2026 Infrastructure Breaches\nInternal developer documentation defacement, community editor suppression, and unsealed perimeter failures documented in the evidence pack.\n1,200+ Editors VDC Wiki Conflict Logs\nCommunity editors trying to fix phishing links and spam templates were systematically blocked by automated filters while Valve staff ignored warnings.\nRussian Conflicts Report (127 KB) ↗Classification Report (66 KB) ↗\n12 TB Unauthenticated August 2026 Asset Leak (CWE-284)\nValve hosted 12 Terabytes of internal code and prototype builds on an open public endpoint without authentication for weeks.\nValve Incompetence Dossier (43 KB) ↗Evidence Archive ↗\nCEVA Logistics Breach August 2026 Customer PII Leak\nNames, addresses, and phone numbers of European Steam Deck purchasers leaked from Valve's logistics partner, sparking phishing waves.\nIncident Record ↗Enforcement Record ↗\n\nSampling artifact: banned_100k_slice.csv (100,000 accounts). Audit outputs: slice_100k_limited_results.csv. Full analytical report: BANNED_100K_FORENSIC_ANALYSIS.md.\n\n08 — Method and limits\nHow this was read, and what it does not claim\n\nThree public populations, one public API, rigorous statistical sampling.\n\nEXECUTION & CREDENTIALS\n\nThe ASF census, the 100,000-account SRSWOR slice and the SteamRep cross-check were executed by PhishDestroy participants under their own Steam accounts and Web API keys, as part of the Coalition's public phishing and scam-banning work. The dossier author holds no Steam Web API key and performed no live scan personally. Aggregation, hashing, verification and publication were done from the participants' output.\n\nPopulation\tWhere it came from\tWhat was read\nASF members\n10,880,610\tThe public member list of the ArchiSteamFarm Steam Community group. Steam's group page shows 5,360,499 members (non-limited only); the API member list returned 10,880,610 total entries including limited accounts. The group is auto-joined on first run unless the user explicitly disables the default group-join setting in configuration (AutoJoinSteamGroup / Statistics), meaning the member list includes commercial bot clusters, individual card idlers, and regular gamers who left the default option enabled.\tGetPlayerBans for every member (ban flags); GetPlayerSummaries for creation dates and country. Batched at 100 IDs, deduplicated by SteamID64.\n100k Banned Accounts SRSWOR Slice\n100,000\tA representative sample drawn uniformly at random without replacement from the 1,182,811 banned accounts corpus ($P = 8.45\\%$). Finite Population Correction yields a margin of error of $\\pm 0.39\\%$ at a 99% confidence level ($Z = 2.576$).\tMonetization and limited account status (isLimitedAccount) audited via Steam's legacy XML profile interface (?xml=1) over distributed proxy pipelines. Confirms 63.06% paid status.\nSteamRep scammers\n51,732\tComplete 100% census of all profiles marked BANNED in the SteamRep community reputation database (51,732 total profiles). Zero sampling or filtering applied.\tISteamUser/GetPlayerBans/v1 for all 51,732 accounts, cross-tabulated against SteamRep status. Confirms 67.77% walk free of any scam bans.\nWhat is claimed\n\nOnly empirical rates and statistically bounded estimates. In the automation population, 88.97% carry no ban; the banned subset skews recent (70% since 2020). In the 100,000-account empirical audit, 63.06% of banned accounts are paid (non-limited), with a mathematically proven margin of error under ±0.4%. Among 51,732 confirmed scammers, 67.77% carry no scam-relevant ban. Every figure is reproducible from Valve's own Web API.\n\nWhat is not claimed\n\nA Steam ban carries no reason field, so no ban here is attributed to a specific cause. Group membership is not proof that an account is an automated bot: because ASF enables group-joining by default unless manually unticked, the population mixes commercial multi-account farms with personal accounts of ordinary players and hobbyists. Country is self-reported, and a SteamRep listing is a community adjudication, not a court finding. No individual is named.\n\nWhy it matters\n\nValve holds the same API, its own database behind it, and the ban reasons this scan cannot see. It can run this query across the whole ID space in seconds. The measurement that lets an outside party check an enforcement claim against a number has never been published by the one party that can produce it at full fidelity. This is the outside estimate, offered so the question can be put with a figure attached.\n\nRead next: the card economy this population runs → · support access and theft → · the full dossier →",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Enforcement Audit — The 1,182,811 Ban Census"
          },
          {
            "level": 2,
            "id": null,
            "text": "Ten million accounts, and nine of ten untouched"
          },
          {
            "level": 3,
            "id": null,
            "text": "ASF joins the group for you"
          },
          {
            "level": 3,
            "id": null,
            "text": "10,880,610 total entries"
          },
          {
            "level": 3,
            "id": null,
            "text": "88.97% clean"
          },
          {
            "level": 3,
            "id": null,
            "text": "Of 10,880,610 accounts, how many Valve has touched"
          },
          {
            "level": 3,
            "id": null,
            "text": "What this fleet already paid Valve to exist"
          },
          {
            "level": 2,
            "id": null,
            "text": "Where the fleet lives"
          },
          {
            "level": 3,
            "id": null,
            "text": "Banned accounts by declared country"
          },
          {
            "level": 2,
            "id": null,
            "text": "Recent accounts, not a legacy backlog"
          },
          {
            "level": 3,
            "id": null,
            "text": "When the banned accounts were created"
          },
          {
            "level": 2,
            "id": null,
            "text": "When Valve acts, it acts inside the first year"
          },
          {
            "level": 3,
            "id": null,
            "text": "How old the account was when the ban landed"
          },
          {
            "level": 2,
            "id": null,
            "text": "When Valve does act, it doesn't stop the bot"
          },
          {
            "level": 3,
            "id": null,
            "text": "What the 11% who are banned are actually banned for"
          },
          {
            "level": 2,
            "id": null,
            "text": "The scammers Valve lets walk: The 51,732 Complete Census"
          },
          {
            "level": 3,
            "id": null,
            "text": "Confirmed scammers, by whether Valve applied a scam-relevant ban (Full Census)"
          },
          {
            "level": 4,
            "id": null,
            "text": "Two populations, one finding"
          },
          {
            "level": 2,
            "id": null,
            "text": "The 100,000-account empirical audit: botnets are not disposable free accounts"
          },
          {
            "level": 3,
            "id": null,
            "text": "100,000 Unbiased Slice"
          },
          {
            "level": 3,
            "id": null,
            "text": "Margin of Error < ±0.4%"
          },
          {
            "level": 3,
            "id": null,
            "text": "Why Any 100k Yields the Same"
          },
          {
            "level": 3,
            "id": null,
            "text": "100,000 Banned Accounts: Paid ($5+ Store Spend) vs Free Limited Status"
          },
          {
            "level": 3,
            "id": null,
            "text": "The Structural Reality: Industrial-Scale Account Liquidation"
          },
          {
            "level": 2,
            "id": null,
            "text": "How this was read, and what it does not claim"
          },
          {
            "level": 3,
            "id": null,
            "text": "What is claimed"
          },
          {
            "level": 3,
            "id": null,
            "text": "What is not claimed"
          },
          {
            "level": 3,
            "id": null,
            "text": "Why it matters"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/de/enforcement_audit.html",
          "https://phishdestroy.io/steam_dossier/de/#briefing-heading",
          "https://help.steampowered.com/en/faqs/view/71D3-35C2-AD96-AA3A",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/asf-ban-census-2026-09-23.json",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/steamrep_steam_bans.csv",
          "https://phishdestroy.io/live-intel/?category=steam",
          "https://phishdestroy.io/steam_dossier/de/card_economy.html",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/banned_archiasf_massive.csv",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/slice_100k_limited_results.csv",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/reports/BANNED_100K_FORENSIC_ANALYSIS.md",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/banned_100k_slice.csv",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/reports/STEAM_BANNED_LIMIT_ANALYSIS.md",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/INVESTIGATION_OVERVIEW.md",
          "https://phishdestroy.io/steam_dossier/de/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/reports/STEAMREP_VS_STEAM_AUDIT.md",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/SteamRep_Profiles_BannedCaution_2024.csv",
          "https://phishdestroy.io/steam_dossier/de/security_timeline.html",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/reports/russian_conflicts_report.json",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/reports/classification_report.json",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/reports/VALVE_INCOMPETENCE_REPORT.md",
          "https://phishdestroy.io/steam_dossier/de/steam_evidence_archive.html",
          "https://phishdestroy.io/steam_dossier/de/steam_enforcement_evidence.html",
          "https://phishdestroy.io/steam_dossier/de/#insider-threat",
          "https://phishdestroy.io/steam_dossier/de/"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/en/enforcement_audit.content.json",
      "export_json_sha256": "d19ada61e47a553d40259b0f43009f9428275652b82591bcae5432460b06fa42"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "enforcement_audit_de.html",
      "language": "de",
      "title": "Die Zählung, die Valve nicht veröffentlicht — The Steam Dossier",
      "source_url": "https://phishdestroy.io/steam_dossier/enforcement_audit_de",
      "source_html_sha256": "ac037373145ea5451fff381449df421e91fda5f6199423db35d61e9ef19bc73b",
      "exported_at": "2026-09-29T00:15:50.554Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "enforcement_audit_de.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/de/enforcement_audit_de.pdf?v=print-20260929-v5",
        "sha256": "1105816fb9d81703a2e89c3b847d73dff9a99a98c76b8b6e66cb72ebeb0d6144",
        "bytes": 146601,
        "pages": 12
      },
      "integrity": {
        "signed_object": "enforcement_audit_de.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "enforcement_audit_de.content.json.asc",
        "digest_file": "enforcement_audit_de.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify enforcement_audit_de.content.json.asc enforcement_audit_de.content.json",
          "sha256sum -c enforcement_audit_de.content.json.sha256"
        ]
      },
      "content": {
        "text": "BEWEISSTÜCK VI — DIE ZÄHLUNG, DIE VALVE NICHT VERÖFFENTLICHT\nWir haben nicht bei Valve gefragt, wie groß die Farm ist. Wir zählten sie.\n\nEs gibt keine veröffentlichte Zahl darüber, wie viele Automatisierungs-Konten auf Steam laufen. Es gibt keinen Grund, warum dies geheim sein sollte: Der Steam-ID-Bereich ist ein kontinuierlicher Integer-Bereich und Valve verteilt den Web-API-Schlüssel, der diesen abwalkt. Daher haben wir die größte identifizierte Bevölkerung — die ArchiSteamFarm-Gemeinschaft — und haben jeden Mitglied einmal durch den eigenen Ban-Endpunkt von Valve gelesen. Dies geschieht durch Selbstdeklaration, da ASF, bei der ersten Ausführung, automatisch der Steam-Gruppe beitritt, es sei denn, der Benutzer wählt dies ausdrücklich aus oder deaktiviert die Einstellung zur Gruppenmitgliedschaft (AutoJoinSteamGroup / Statistiken). Da diese Einstellung standardmäßig aktiv ist, erfasst die Gruppenmitgliedschaft eine breite Bevölkerung: aktive Multi-Account-Commerical-Bot-Netzwerke, gemütliche faule Hobbyisten und gewöhnliche Spieler, die das Software auf ihrem persönlichen Konto ausgeführt haben und die Standardabonnement nicht entfernt haben. Dies macht die Mitgliedschaft zu einer arbeitsfähigen Zählung des kumulativen Erreichens des Software: 10.880.610 Gesamt-Konten (mit 5.360.499 bestätigten vollwertigen (nicht-eingeschränkten) Mitgliedern über der $5.00-Untergrenze). Dann haben wir die einzige Frage gestellt, die zählt — was hat Valve ihnen tatsächlich getan?\n\nWas diese Seite nicht ist. Es ist kein Argument dafür, dass Valve zehn Millionen Menschen sperren sollte, und es ist keine Beschwerde über Karten-Farmer. Jede Zahl hier hat einen Grund: Valve bannt Individuen dauerhaft, und der in schriftlicher Form angegebene Grund ist der kommerzielle Gebrauch von Steam und Automatisierung. Dies misst, wie dasselbe Regelwerk auf dasselbe Verhalten im großen Stil angewendet wird – durch einen Betreiber, der $5.00 Freischaltungen, Spielelizenzgebühren und Marktgebühren einsammelt, die Valve auf dem Weg durchzieht. Das Ergebnis ist die Asymmetrie, nicht die Farm.\n\nDie 10.88M-ZählungDie Betrüger, die gehen (53.5k)100.000 bezahlte versus kostenlose Überprüfung\n10,880,610Gesamtzahl der ASF-Gruppenmitglieder, die durch die eigene Ban-API von Valve (eingeschränkte und nicht-eingeschränkte Konten zusammengefasst) durchsucht haben.\n88.97%Nie gesperrt worden – 9.680.599 Konten sind weiterhin aktiv\n63.06%Von gesperrten Konten sind bezahlt ($5+ Ausgabe) — 100.000 SRSWOR-Stichprobe (±0,39 % MoE)\n68.63%Von 53.558 überführten Betrüger haben 0 Betrugsbanns (Vollzählung).\n01 — Das Maß\nZehn Millionen Konten, und neun von zehn unberührt\n\nEine Bevölkerung, die sich selbst zählt, einmal durch den eigenen Endpunkt von Valve gelesen.\n\nWarum es sich selbst zählt\nDas ASF tritt der Gruppe für Sie bei.\n\nBei der ersten Ausführung setzt ArchiSteamFarm Statistiken standardmäßig auf wahr und tritt der Archi's SC Farm Steam-Gruppe bei. Ein Betreiber muss aktiv aussteigen. Daher ist die Mitgliedschaft eine Untergrenze für Installationen – nicht eine Obergrenze. Betreiber, die Statistiken deaktiviert haben, fehlen; die tatsächliche Installationszahl ist mindestens so groß.\n\nWAS WIR GELESEN HABEN\n10.880.610 GesamtEinträge\n\nDie API-Mitgliederliste hat insgesamt 10.880.610 SteamID64s zurückgegeben – sowohl eingeschränkte als auch vollwertige Konten. Die Gruppenseite von Steam zeigt 5.360.499 (nur vollwertige Konten). Jeder Eintrag wurde am 23. September 2026 einmalig durch ISteamUser/GetPlayerBans geleitet. Fünfundsünfzig Minuten auf einem Schlüssel.\n\nDIE ANTWORT\n88,97 % sauber\n\n1.200.011 tragen einen Steam-Bann (11,03 %). Die anderen 9.680.599 haben überhaupt nichts im Verlauf – weder einen Community-Bann noch einen VAC-Bann, nichts. Die Farm wird nicht geräumt. Sie läuft weiter. Der gleiche Passus, gerichtet auf eine Person, reicht aus, um sie dauerhaft zu entfernen.\n\nVon 10.880.610 Konten wie viele hat die Valve berührt?\n\nDie gesamte durchgeführte Zählung, aufgeteilt nach dem Kriterium, ob die Valve irgendeinen Ban angeordnet hat. Der rote Bereich umfasst alles, was die Valve jemals mit dieser Flotte getan hat.\n\n88.97%never banned\n11.03%\nNo ban of any kind — 9,680,599 (88.97%)Carries some Steam ban — 1,200,011 (11.03%)\n10,880,610ASF-Mitglieder haben durchsucht\n9,680,599Nie gesperrt — 88,97 %\n1,200,011Jeglicher Bann — 11,03 %\n55 minUm alles zu zählen, auf einem API-Schlüssel\nWas diese Flotte bereits an Valve gezahlt hat, um zu existieren\n\nKeine Schätzung dessen, was die Farm einbringt. Eine Untergrenze dessen, was sie bereits in Valves Geschäft ausgegeben hat — abgeleitet aus Valves eigener Regel, angewendet auf die obige Anzahl.\n\nDie Anzahl von 10.880.610 umfasst die vollständige Liste der Mitglieder der ASF-Gruppe, wie sie vom API zurückgegeben wird — dies beinhaltet sowohl eingeschränkte als auch nicht-eingeschränkte Konten. Die eigene Seite der begrenzten Benutzerkonten von Steam stellt fest, dass eingeschränkte Konten nicht zu der Mitgliedschaft in der Steam-Gruppe zählen (sie werden von der angezeigten Gruppengröße ausgeschlossen), aber sie können dennoch in der zugrunde liegenden Mitgliederliste auftauchen. Der nicht-eingeschränkte Teil — Konten, die mindestens $5.00 im Steam-Shop ausgegeben haben — beträgt genau 5.360.499 — die Anzahl, die Steam auf der Gruppenseite anzeigt, die nach Steam's eigener Regel eingeschränkte Konten ausklammert. Die Berechnung der Untergrenze von $5.00 gilt nur für diesen nicht-eingeschränkten Teil.\n\n5,360,499nicht-eingeschränkte Mitglieder\n(Anzahl der angezeigten Gruppen in Steam)\n×\n$5.00Ventil's eigene Mindestausgabe-Schwelle\n, um nicht mehr eingeschränkt zu sein\n=\n$26,802,495Untergrenze für den Einkauf durch den nicht-eingeschränkten Teil\n\nDies ist eine Untergrenze für Geld, das Valve bereits von der nicht eingeschränkten Fraktion der Flotte erhalten hat — keine Einnahmeabschätzung, keine Gewinnforderung. Der tatsächliche Ausgabenbetrag pro Konto ist für die meisten höher; die Zahlungssumme von 5,00 USD ist nur die erforderliche Mindestausgabe-Schwelle.\n\nDie sekundäre Ernte: bis zu 66,7 % Gebühr auf dem geförderten Handelsvolumen. Über die 26,8 Mio. USD Eintrittsgebühr hinaus berechnet Valve für jeden auf dem Community Market liquidierten Karten- und Handelsabfall eine obligatorische Mindestgebühr von zwei Cent (0,01 USD Steam-Gebühr + 0,01 USD Verlagsgebühr). Bei typischen 3-Cent-Karten und Abfallprodukten entnimmt Valve 2 Cent aus 3 Cent – eine effektive Kürzung von 66,67 % zugunsten von Valve, weit über dem genannten 15-%-Marketingzuschlag hinaus.\n\nWichtiger Bevölkerungshinweis: Die Mitgliedschaft in einer Gruppe ist kein Beweis dafür, dass jeder einzelne Account ein dedizierter Bot ist, und erfasst auch nicht jeden Bot auf Steam. ASF schließt Accounts standardmäßig automatisch der Community-Gruppe bei der Einführung hinzu; es sei denn, der Benutzer deaktiviert diese Konfigurationsflagge ausdrücklich (AutoJoinSteamGroup), bleiben reguläre Spieler, Einmal-Zögerer und Community-Mitglieder im Roster zusammen mit automatisierten Farming-Flotten. Darüber hinaus enthält ein Steam-Bann kein öffentliches Gründenfeld. Die Feststellung ist eine empirische Rate über diese mit dem Software-Programm verbundenen Bevölkerung, nicht ein individueller Urteil über einen einzelnen Account. Aggregiert, wiedergabeehmend: asf-ban-census-2026-09-23.json.\n\n02 — Geographie\nWo die Flotte lebt\n\nNur 8,5 % der gesperrten Konten geben ein Land an. Unter denjenigen, die dies tun, hat die Vereinigten Staaten den größten Anteil.\n\nEin Steam-Profil verfügt über ein optionales Landfeld. 100.413 der 1.182.811 gesperrten Konten haben es ausgefüllt – 8,5%.† Unter dieser Minderheit führt die Vereinigten Staaten mit 15,5%, gefolgt von der Ukraine, China und Russland, und der Rest erstreckt sich in einer langen Kette über Europa, Lateinamerika und Südostasien. Niemand bestätigt dieses Feld: Afghanistan belegt in den Top Ten einen Platz, der annähernd seinem Wert entspricht. Die anderen 91,5% werden entweder nicht ausgefüllt oder nicht zugeordnet, sodass das Folgende das Bild einer selbstausgewählten Minderheit darstellt – nicht eine Karte der Flotte und nicht eine Grundlage für die Angabe, wo sie betrieben wird.\n\nGesperrte Konten durch angegebene Herkunftsländer\n\nTop 15 Länder unter den 100.413 gesperrten Konten, die eine öffentliche Lage offenlegen. Anteil dieses geografischen Unterbestands. Bewegen Sie den Mauszeiger, um die Zahlen anzuzeigen.\n\n0%\n5%\n10%\n15%\n20%\nUnited States\nUkraine\nChina\nRussia\nCanada\nAustralia\nJapan\nBrazil\nGermany\nAfghanistan\nUnited Kingdom\nRomania\nFrance\nPhilippines\nIndia\n\nOrt gelesen aus GetPlayerSummaries für den gesperrten Untergruppe. Das Feld wird vom Kontoinhaber festgelegt und von niemandem überprüft, daher zählt ein VPN-Ausgang oder eine Scherz-Eintragung so viel wie ein echter Eintrag.\n\n03 — Frische\nKürzlich angelegte Konten, kein legacy Backlog\n\nDatum der Kontoerstellung, ist die gesperrte Population aktuell, nicht ein Überbleibsel aus der ASF-Ära.\n\nWenn dies ein alter Haufen wäre, der langsam aufgeräumt wird, würden die gesperrten Konten in die frühen Jahre des Trading-Card-Handels fallen. Sie tun das Gegenteil. Von den 1.132.852 gesperrten Konten, die ein Erstellungsdatum aufweisen, 70% wurden in 2020 oder später erstellt, und fast die Hälfte seit 2023. Die Zahl steigt von 59.175 erstellt im Jahr 2017 auf einen Höchststand von 227.030 erstellt allein im Jahr 2024. Jedes dieser Konten hat die $5.00 Mindestausgabe-Schwelle vor dem Erhalt einer Karte passiert, sodass die Eintrittsgebühr bei jedem eingezogen wurde.\n\nWenn die gesperrten Konten erstellt wurden\n\nJahreszeitpunkt der Kontoerstellung der 1.132.852 gesperrten Mitglieder, die ein Erstellungsdatum aufweisen. Der Zeitraum erstreckt sich von 2020 bis 2026, nicht der Handelskartenära von 2013 bis 2015. Höchststand: 2024. Maus über die Zahlen halten.\n\n0k\n63k\n125k\n188k\n250k\n'13\n'14\n'15\n'16\n'17\n'18\n'19\n'20\n'21\n'22\n'23\n'24\n'25\n'26\n70%Von in 2020 oder später geschaffenen gesperrten Konten\n227,030Gesperrte Konten, die im Jahr 2024 erstellt wurden — dem Spitzenjahr\n51,701Der Tiefpunkt des Jahres 2021, zwischen zwei Spitzenjahren — unexplained\n2003→2026Der Bereich ist vorhanden, aber das Gewicht erstreckt sich über die letzten sechs Jahre.\n\nErstellungsdaten aus GetPlayerSummaries für den gesperrten Untergruppe, dedupliziert durch SteamID64. Ein Erstellungsdatum ist der Zeitpunkt, zu dem das Konto erstellt wurde, nicht der Zeitpunkt der Sperre oder des Beginns des Farmens; es wird hier als Beweis für die Neuestigkeit der Population gelesen, nicht für das Vorhaben. Drei Dinge, die der Chart nicht zeigt:\n\nEin Trend nach 2024. Ein Konto, das 2025 oder 2026 erstellt wurde, hat weniger Zeit gehabt, um einen Bann zu sammeln, und 2026 umfasst neun Monate – daher ist 227,030 → 121,070 → 16,534 Zensur, nicht ein Rückgang.\nEine Bannquote. Es wurden nur für gebannte Konten Erstellungsjahre gelesen, daher gibt es keinen Nenner. Eine wachsende Installationsbasis allein würde diese Form erzeugen.\nWarum 2021 zusammenbrach. 51.701 liegt zwischen 105.821 und 104.641, unter der Hälfte eines jeden Nachbarn. Es gibt nichts öffentliches, das es erklärt; es bleibt sichtbar, anstatt geglättet zu werden.\n04 — Zeitplanung\nWenn die Valve aktiv wird, tut sie dies innerhalb des ersten Jahres\n\nDie offensichtliche Verteidigung für 88,97 % unberührte Fälle ist ein Rückstand. Die datierten Bannungen sprechen dagegen.\n\nWie alt das Konto war, als der Bann eingesetzt wurde\n\nKontounterstand zum Zeitpunkt des Banns für die 293.750 gesperrten Konten, die sowohl ein Erstellungsdatum als auch ein datiertes letztes Banndatum aufweisen. Über die Hälfte wurden innerhalb des ersten Jahres erwischt.\n\n0%\n10%\n20%\n30%\n40%\n<6 mo\n33.7%\n6–12 mo\n21.5%\n1–2 y\n20.6%\n2–5 y\n14.3%\n5 y+\n10.0%\n55.1% inside the first year\nBanned inside the first year — 55.1%Banned later — 44.9%\n0.80 yMittlere Altersgruppe des Kontos zum Zeitpunkt des Banns\n55.1%Gebannt innerhalb des ersten Jahres des Kontos\n33.7%Gebannt innerhalb der ersten sechs Monate\n293,750Konten, auf denen beide Daten vorliegen\n\nDies ist die Antwort auf die offensichtliche Verteidigung. Wenn 88,97 % der Flotte unberührt bleiben, weil die Durchsetzung einfach langsam ist – ein Rückstand, der sich durcharbeitet – dann würden die Sanktionen, die durchgesetzt werden, veraltet. Sie tun das Gegenteil: Das mittlere gesperrte Konto war neun und ein halbes Monate alt, und ein Drittel – 33,7 % – wurden innerhalb von sechs Monaten erwischt. Wenn Valve auf diese Bevölkerung reagiert, tut er es schnell. Die neun von zehn, die noch laufen, warten nicht in einer Warteschlange.\n\nAlter bei Bann = Erstellungsdatum aus GetPlayerSummaries abzüglich des durch DaysSinceLastBan implizierten Bann-Datums, gelesen am 23. September 2026. Diese Berechnung wird nur vorgenommen, wo beide Werte vorhanden sind: 293.750 der 1.200.011 gesperrten Konten. Die verbleibenden Konten weisen keinen Wert für \"Tage seit letztem Bann\" auf und werden ausgeklammert, nicht angenommen – also lesen Sie dies als die Form des datierten Unterbestands, nicht als jeder Sperre.\n\n05 — Was der Bann tatsächlich ist\nWenn die Valve aktiv wird, stoppt sie den Bot nicht.\n\nVon den 11 %, die irgendeinen Bann tragen, betrachten Sie, welcher Bann.\n\nEin Bann ist kein Bann. Von den 1.200.011 Accounts, die Valve markiert hat, tragen 99,8% einen Community-Bann – eine Beschränkung auf Foren, Profile und Gruppen, die sich auf einen Trading-Bot nicht auswirkt. Das Konto kann weiterhin Karten erhalten, handeln und Inventar bewegen. 22,2% tragen mindestens einen Spielsperre-Bann und 3,9% einen VAC-Bann; die Kategorien überlappen sich, sodass sie sich nicht addieren. Der eine Sanktion, der tatsächlich den Handel unterbricht, der Wirtschaftsbann / Handelsbann, betrifft 5.214 Accounts. Wir stützen den Fall nicht auf diese Zahl – Handelsbanns sind auf Steam im Allgemeinen selten. Der Zweck dieses Diagramms ist einfacher: selbst der Bruchteil, den Valve berührt, bleibt handeln.\n\nWas die 11 %, die gesperrt sind, tatsächlich gesperrt sind für\n\nJeder Bann-Typ als Anteil an den insgesamt 10.880.610 durchsuchten Mitgliedern. Konten können mehr als einen Bann tragen. Maus überfahren, um die Anzahl zu sehen.\n\n0%\n4%\n8%\n11%\n15%\nCommunity ban\nGame ban\nVAC ban\nEconomy / trade ban\n\nEin Steam-Bann enthält kein Gründenfeld, daher werden none dieser Bannmaßnahmen spezifisch auf die Karten-Farming zurückgeführt — dies ist die Mischung der vorhandenen Bannarten, gesetzt nebeneinander zu dem, was jede Art tatsächlich einschränkt. Ein Community-Bann unterbricht den Handel nicht; dies tut der Wirtschafts-/Handelsbann. Zusammenfassung: asf-ban-census-2026-09-23.json.\n\n06 — Die andere Bevölkerungsgruppe\nDie Betrüger, die Valve gewähren lässt: Die 53.558-Vollzählung\n\nEine zweite, unabhängige Liste – bestätigte Gemeinschaftsbetrügereien – wurde mit dem gleichen offiziellen API gemessen.\n\nDie Automatisierungspopulation könnte als harmlose Träumer abgewehrt werden. Die zweite Population kann nicht. SteamRep ist eine lang laufende Community-Reputationsdatenbank; ein dort markiertes BANNED-Konto wurde von dieser Community als Betrüger eingestuft, mit dokumentiertem Opferbeweis und Transaktions-Chat-Protokollen. Wir haben eine 100%-Vollzählung aller 53.558 Profile durchgeführt, die diesen BANNED-Status gegen Steams offizielle Web-API (ISteamUser/GetPlayerBans/v1) — und nur die Sanktionen gezählt, die das Betrugsverhalten betreffen. Ein VAC-Bann ist für Softwarebetrug in einem Spiel (Aimbots, Wallhacks); er hat nichts mit einem Händler zu tun und ist kein Beweis dafür, dass Valve auf Betrug reagiert hat, daher wird er nicht als Betrugsbekämpfung gezählt.\n\nIm Rahmen der umfassenden Zählung über alle 53.558 Konten beträgt der Anteil von 68.63% – 36.757 überführte Betrüger –, die KEINE scam-relevanten Bannmaßnahmen von Valve tragen: sie können weiterhin handeln, Freunde neuer Opfer anfragen und Nachrichten senden. Nur 31.37% wurden mit einem Community-Bann oder Handelsbann konfrontiert, und der Handelsbann – die Maßnahme, die tatsächlich den Inventartransfer unterbindet – trifft lediglich 18.27% (9.783 Konten). Zusätzlich tragen 12.86% (6.888 Konten) VAC- oder Spielbannmaßnahmen rein aus Gründen des Ingame-Betrugs, bleiben aber im Steam-Handel vollständig unbegrenzt.\n\nBestätigte Betrüger, nach ob die Valve eine betrugsrelevante Sperre angelegt hat (Vollzählung)\n\nAlle 53.558 von SteamRep gesperrten Profile, aufgeteilt nach dem Vorhandensein eines Community-Bans oder Handelsbans durch Valve. VAC- und Spielbans sind ausgeschlossen – sie richten sich nicht gegen Betrug. Über die Mauszeigerposition erhalten Sie die Anzahl.\n\n0%\n18%\n35%\n53%\n70%\nNo scam-relevant ban\nCommunity or trade ban\n0%\n6%\n13%\n19%\n25%\nCommunity ban\nTrade / economy ban\nVAC (not fraud)\nGame ban\n53,558SteamRep-gesperrte Profile überprüft — 100% vollständige Zählung\n36,757Keinen betrugsrelevanten Bann tragen (68,63%)\n18.27%Den Handelsbann, der Betrügereien (9.783) unterbindet, durchführen.\n31.37%Der Anteil der Valve, der mit einem Community- oder Handelsbann (16.801) konfrontiert wurde,\n\nSteamRep ist eine von Dritten und durch die Gemeinschaft beurteilte Reputationsdatenbank, keine Entscheidung von Valve – was der Punkt ist: externes Beweismaterial, gemessen an dem, was Valve selbst getan hat. Alle 53.558 SPERRPROFILE aus dem kanonischen Export wurden direkt mit ISteamUser/GetPlayerBans/v1 abgeglichen. \"Betrüger-relevant\" bedeutet einen Community- oder Wirtschaft/Handelsbann; VAC (12,86%) und Spielbanns (3,86%) werden getrennt gezählt, da sie Betrug und nicht Betrug betreffen. Komplettes Audit-Datensatz: steamrep_steam_bans.csv.\n\nZwei Populationen, eine Entdeckung\n\nDiese sind nicht dieselben Personen und nicht dasselbe Verhalten. Eines sind zehn Millionen automatisierte Konten; das andere sind fünfzigtausend überführte Betrüger. Was sie gemeinsam haben, ist die Form des Ergebnisses: neun von zehn Farm-Konten werden niemals berührt, und über zwei Drittel (68,63%) der bestätigten Betrüger treffen keine Sanktion, die Betrug anspricht. Der von der Community-Bann Valve gewährte Bann beschränkt frei Forums- und Profilzugriffe, nicht den Handel. Der Berichtsknopf, die Reputationsdatenbank, der Bann, der einen Betrug stoppt: alles vorhanden, alles unterbenutzt. Dies setzen wir neben die archivierten Absagen im Hauptdossier, wo dasselbe Unternehmen ein einzelnes Konto dauerhaft löscht und den kommerziellen Gebrauch und die Automatisierung als Grund anführt — der Passus ist nicht ruhen, er ist scharf.\n\n07 — Die $5,00-Mindestausgabe-Schwelle und das Account-Hijacking\nDie 100.000-Konto-empirische Überprüfung: Botnetze sind keine Wegwerf-Konten.\n\nStatistische Stichprobengeschichte und mathematischer Beweis: Warum die Auswahl jeder anderen 100.000 Konten das gleiche Ergebnis führt.\n\nDie primäre Verteidigung von Valve gegenüber Regulierungsbehörden und Verbraucherschutzorganisationen bestand darin, dass automatisierte Betrugsversuche und Farming durch flüchtige, kostenlose \"Wegwerf-Accounts\" durchgeführt werden, die schnell gesperrt werden. Gemäß den veröffentlichten Regeln von Valve ist ein Konto eingeschränkt, bis es mindestens $5.00 USD im Steam-Shop ausgibt, was es von Handel, Freundschaftsanfragen und API-Funktionen ausschließt. Wir haben diese Behauptung direkt durch die Überprüfung des Monetarisierungsstatus einer repräsentativen, mathematisch strengen Stichprobe von 100.000 gesperrten Steam-Accounts überprüft, die aus unserem Korpus von 1.182.811 Profilmetadaten stammen.\n\nStichprobenerhebungsschema (SRSWOR)\n100.000 Repräsentative, unverzerrte Stichprobe\n\nAus N = 1.182.811 einzigartigen gesperrten Steam-Konten wurden durch einfaches Zufallsstichprobennahme ohne Wiederholung mittels eines kryptografisch gleichmäßigen PRNG gezogen. Jedes Konto hatte eine identische Einbeziehungswahrscheinlichkeit von P = n / N ≈ 8,45%, was vollständig Überlebenden- und Aktivitätsbias eliminierte.\n\nMathematischer Beweis\nFehlertoleranz < ±0,4 %\n\nDie Anwendung der Formel zur Korrektur der endlichen Population (FPC) im 99%-Konfidenzintervall (Z = 2,576):\nMitarbeiterrate = Z × √[p(1-p)/n] × √[(N-n)/(N-1)] ≈ ±0,39%\n\nErhaltbarkeit\nWarum jede 100k-Stichprobe das gleiche Ergebnis führt\n\nDa der Fehlerbereich unter ±0.4% bei 99% Konfidenz begrenzt ist, ist das Ziehen eines jeden anderen unabhängigen 100.000-Konto-Stichprobenmusters mathematisch gewährleistet, dass es innerhalb von 63.06% ± 0.39% (von 62.67% bis 63.45%) fällt. Die Stichprobe spiegelt die gesamte 1,18 Millionen betreffende gesperrte Bevölkerung wider.\n\nDie Prüfergebnisse zerstören vollständig die Verteidigung der „Wegwerf-Bot“. Bei den 100.000 überprüften Konten über die Steam-XML-Profil-Schnittstelle: 61.490 Konten (63,06 % der klassifizierten Konten) sind vollwertige (nicht-eingeschränkte) Paid-Konten, die mindestens $5,00 bei Steam ausgegeben haben. Nur 36.021 (36,94 %) sind eingeschränkte kostenlose Konten, während 2.489 nicht konfiguriert oder privat waren.\n\n100.000 gesperrte Konten: Bezahlte (Einkaufsverbrauch von $5+) gegenüber freiem eingeschränktem Status\n\nEmpirische Überprüfung von 100.000 zufällig ausgewählten gesperrten Konten. Über 63% haben die Mindestausgabe-Schwelle von Valve's bezahlten finanziellen Hürde passiert. Für die Anzahl blättern.\n\n0%\n16%\n33%\n49%\n65%\nNon-limited (Paid ≥ $5.00)\nLimited (Free < $5.00)\n100,000Stichprobe der Bevölkerung (SRSWOR, N=1,18M)\n63.06%Vollwertige bezahlte Konten (61.490 Konten)\n±0.39%Fehlertoleranz bei einem 99%-Konfidenzintervall\n~745,800Extrapolierte bezahlte Konten in einem 1.18M großen gesperrten Korpus\nDie schwerwiegende Ermittlungskonsequenz: Industriegrößenartige Account-Kapern\n\nWarum wären 63% der gesperrten Bot- und Betrugsaccounts bezahlte Konten, die echtes Geld in Valves Laden ausgegeben haben? Botnet-Betreiber geben nicht 3,7 Millionen Dollar aus eigener Tasche für Wegwerf-Konten aus. Dieses empirische Verhältnis beweist, dass legitime, alte Benutzerkonten auf industrieller Skala über Phishing, Malware und kompromittierte API-Schlüssel gehackt werden. Kriminelle Netzwerke stehlen echte Konten, um ihre Dauer zu übernehmen, Handelsbeschränkungen zu umgehen und sie als hochvertrauenswürdige \"Löffel\" zur Betrug von anderen Nutzern zu nutzen.\n\nWenn die automatische Moderation von Valve endlich die schädliche Aktivität erkennt, banniert Valve das Konto. Doch wie im Archiv des Support-Tickets dokumentiert, weigert sich der Steam-Support systematisch, gekaperte Konten an ihre rechtmäßigen Besitzer zurückzugeben, und sendet identische automatisierte Ablehnungsvorlagen. Valve erhebt die erste $5.00-Beitragsgebühr für den Laden, erhebt Gebühren für gestohlene Trades und sperrt dann den Opfer dauerhaft aus.\n\nForensic Evidence & Enforcement Architecture Diagram\nInteractive flow from 10.88M scanned accounts to 100k empirical slice and 53.5k confirmed scammers · Click links to inspect raw evidence\nTier 01 · 10.88M Automation Fleet Census\nThe largest self-identifying automation population on Steam, passed sequentially through Valve's official ban API. Proves that commercial bot fleets run with 88.97% impunity while paying tens of millions in entry fees.\n9,680,599 88.97% Active & Untouched\nAccounts running automated software that carry zero bans of any kind on record.\nRaw Census JSON (1.2 KB) ↗Inspect Section 01 ↗\n$26,802,495 Direct Store Revenue Floor\nCollected by Valve from 5,360,499 non-limited members past the minimum $5.00 entry threshold.\nCard Economy Audit ↗Valve $5 Rule FAQ ↗\n1,200,011 11.03% Flagged Subset\n99.8% carry cosmetic community bans only; trade remains open on 99.95% of accounts.\nBan Type Breakdown ↗Banned DB (60.4 MB) ↓\nTier 02 · 100,000-Account Empirical Sampling Audit (N = 1,182,811)\nRepresentative SRSWOR slice evaluated via legacy XML endpoints. Mathematically proven margin of error < ±0.4% at 99% confidence interval. Refutes the claim that banned bots are free throwaway accounts.\n61,490 (63.06%) Non-Limited Paid Accounts ($5+ Spend)\nOver 63% of banned accounts represent paid transactions. Extrapolates to ~745,800 paid accounts ($3.73M+ entry floor) in the banned pool.\nLimited Results CSV (2.1 MB) ↓100k Forensic Report ↗\n36,021 (36.94%) Limited Free Accounts (< $5.00)\nThe minority of banned profiles that fit Valve's \"disposable throwaway bot\" profile. 2,489 accounts were unconfigured/private.\n100k Sample Slice CSV (8.5 MB) ↓Spend Analysis MD ↗\n34.67% vs 63.93% Profile Sanitization Audit\nValve wiped nicknames to raw SteamID64 on 34,673 accounts, but left custom names & avatars completely untouched on 63,928 banned accounts.\nSanitization Section ↗Overview Roadmap ↗\n34.59% Legacy Aged Accounts (Created 2003–2019)\nOver a third of banned accounts were registered 5 to 20+ years ago, proving industrial-scale account hijacking of long-term Steam players.\nAge Chronology ↗Support Refusals ↗\nTier 03 · 53,558 SteamRep Confirmed Scammers Census\nFull 100% census of community-adjudicated fraudsters with victim chat logs and trade proof, cross-referenced against official Steam ban APIs. Proves systemic enforcement failure.\n36,757 (68.63%) Zero Scam Bans (Full Impunity)\nOver two-thirds of verified fraudsters carry neither Community nor Trade bans from Valve. Fully operational to trade and add victims.\nSteamRep API Bans (2.6 MB) ↓SteamRep Audit Report ↗\n9,783 (18.27%) Economy / Trade Bans\nThe only sanction that severs inventory liquidation. Present on less than a fifth of confirmed scammers.\nSteamRep Source (2.1 MB) ↓Inspect Section 06 ↗\n6,888 (12.86%) Irrelevant Cheating Bans (VAC Only)\nBanned for aimbots/wallhacks in games, while their Steam trade and phishing capabilities remain 100% active.\nVAC Irrelevance Analysis ↗Security Timeline ↗\nTier 04 · Wiki Defacement & August 2026 Infrastructure Breaches\nInternal developer documentation defacement, community editor suppression, and unsealed perimeter failures documented in the evidence pack.\n1,200+ Editors VDC Wiki Conflict Logs\nCommunity editors trying to fix phishing links and spam templates were systematically blocked by automated filters while Valve staff ignored warnings.\nRussian Conflicts Report (127 KB) ↗Classification Report (66 KB) ↗\n12 TB Unauthenticated August 2026 Asset Leak (CWE-284)\nValve hosted 12 Terabytes of internal code and prototype builds on an open public endpoint without authentication for weeks.\nValve Incompetence Dossier (43 KB) ↗Evidence Archive ↗\nCEVA Logistics Breach August 2026 Customer PII Leak\nNames, addresses, and phone numbers of European Steam Deck purchasers leaked from Valve's logistics partner, sparking phishing waves.\nIncident Record ↗Enforcement Record ↗\n\nStichprobenerzeugnis: banned_100k_slice.csv (100.000 Konten). Audit-Ausgaben: slice_100k_limited_results.csv. Vollständiges Analysergebnis: BANNED_100K_FORENSIC_ANALYSIS.md.\n\n08 — Methodik und Grenzen\nWie dies verstanden wurde und was es nicht behauptet\n\nDrei öffentliche Bevölkerungsgruppen, eine öffentliche API, rigorose statistische Stichprobe.\n\nBevölkerung\tWoher es kam\tWas wurde gelesen?\nASF-Mitglieder\n10.880.610\tDie öffentliche Mitgliederliste der ArchiSteamFarm Steam-Community-Gruppe. Die Gruppenseite von Steam zeigt 5.360.499 Mitglieder (nur vollwertige Konten); die API-Mitgliederliste gab 10.880.610 GesamtEinträge zurück, einschließlich eingeschränkter Konten. Die Gruppe wird automatisch beigetreten, wenn das Programm zum ersten Mal ausgeführt wird, es sei denn, der Benutzer deaktiviert ausdrücklich die Standardgruppe-Beitrittseinstellung in der Konfiguration (AutoJoinSteamGroup / Statistiken), was bedeutet, dass die Mitgliederliste kommerzielle Bot-Clustern, individuelle Kartenidler und reguläre Gamer umfasst, die die Standardoption aktiviert haben.\tDie GetPlayerBans für jeden Mitglied (Bann-Flags); GetPlayerSummaries für Erstellungsdaten und Land. In Batches von 100 IDs gruppiert, durch SteamID64 dedupliziert.\n100.000 gesperrte Konten SRSWOR-Stichprobe\n100.000\tEine repräsentative, unverzerrte Stichprobe, die ohne Ersatz und zufällig aus dem Korpus der 1.182.811 gesperrten Konten gezogen wurde ($P = 8.45\\%$). Die Finite-Bevölkerungs-Korrektur ergibt einen Fehlerbereich von $\\pm 0.39\\%$ bei einem 99%-Konfidenzniveau ($Z = 2.576$).\tMonetarisierung und Status eines eingeschränkten Kontos (isLimitedAccount) überprüft über das Steam-XML-Profil-Interface der alten Version (?xml=1) über verteilte Proxy-Pipelines. Bestätigt 63,06 % Zahlungsstatus.\nSteamRep-Betrüger\n53.558\tVollständige 100%-Zählung aller Profile, die im SteamRep-Gemeinschaftsreputationsverzeichnis als BANNED markiert sind (insgesamt 53.558 Profile). Keine Stichprobe oder Filterung angewendet.\tISteamUser/GetPlayerBans/v1 für alle 53.558 Konten, gegliedert nach dem Status von SteamRep. Bestätigt, dass 68,63 % der Konten von jeglichen Betrugsbannsstrafen unbeschadet geblieben sind.\nWas behauptet wird\n\nNur empirische Zuwachsraten und statistisch begrenzte Schätzungen. In der automatisierten Bevölkerung tragen 88,97 % keine Sperre; der gesperrte Untergruppe ist auf die jüngere Zeit (70 % seit 2020) verschoben. Bei der empirischen Prüfung von 100.000 Konten sind 63,06 % der gesperrten Konten bezahlt (nicht eingeschränkt), mit einem mathematisch nachgewiesenen Fehlerbereich unter ±0,4 %. Unter den 53.558 bestätigten Betrügern tragen 68,63 % keine betrugsrelevanten Sperren. Jede Zahl ist reproduzierbar über Valves eigenen Web-API.\n\nWas wird nicht beansprucht\n\nEin Steam-Bann enthält kein Gründenfeld, daher wird hier kein Bann auf eine spezifische Ursache zurückgeführt. Die Mitgliedschaft in einer Gruppe ist kein Beweis dafür, dass ein Konto ein automatisiertes Bot ist: Da ASF die Gruppenzugehörigkeit standardmäßig aktiviert, es sei denn, sie wird manuell abgewählt, mischt sich die Bevölkerung aus kommerziellen Multi-Account-Farms und persönlichen Konten von gewöhnlichen Spielern und Hobbyisten. Das Land wird selbst berichtet, und eine SteamRep-Listung ist eine Gemeinschaftsentscheidung, nicht ein Gerichtsurteil. Kein individueller Name wird genannt.\n\nWarum es wichtig ist\n\nDie Ventile besitzen die gleiche API, hinter denen ihre eigene Datenbank liegt, und die Banngründe, die dieser Scan nicht erkennen kann. Diese Abfrage kann innerhalb von Sekunden über den gesamten ID-Bereich durchgeführt werden. Die Messung, die es einer externen Partei ermöglicht, einen Durchsetzungsanspruch gegen eine Nummer zu überprüfen, wurde niemals von der Partei veröffentlicht, die es in voller Genauigkeit erstellen kann. Dies ist die externe Schätzung, die vorgeschlagen wird, damit die Frage mit einer Zahl verbunden werden kann.\n\nLesen Sie weiter: die von dieser Population betriebene Kartenökonomie → · Zugriff und Diebstahl unterstützen → · das vollständige Dossier →",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Wir haben nicht bei Valve gefragt, wie groß die Farm ist. Wir zählten sie."
          },
          {
            "level": 2,
            "id": null,
            "text": "Zehn Millionen Konten, und neun von zehn unberührt"
          },
          {
            "level": 3,
            "id": null,
            "text": "Das ASF tritt der Gruppe für Sie bei."
          },
          {
            "level": 3,
            "id": null,
            "text": "10.880.610 GesamtEinträge"
          },
          {
            "level": 3,
            "id": null,
            "text": "88,97 % sauber"
          },
          {
            "level": 3,
            "id": null,
            "text": "Von 10.880.610 Konten wie viele hat die Valve berührt?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Was diese Flotte bereits an Valve gezahlt hat, um zu existieren"
          },
          {
            "level": 2,
            "id": null,
            "text": "Wo die Flotte lebt"
          },
          {
            "level": 3,
            "id": null,
            "text": "Gesperrte Konten durch angegebene Herkunftsländer"
          },
          {
            "level": 2,
            "id": null,
            "text": "Kürzlich angelegte Konten, kein legacy Backlog"
          },
          {
            "level": 3,
            "id": null,
            "text": "Wenn die gesperrten Konten erstellt wurden"
          },
          {
            "level": 2,
            "id": null,
            "text": "Wenn die Valve aktiv wird, tut sie dies innerhalb des ersten Jahres"
          },
          {
            "level": 3,
            "id": null,
            "text": "Wie alt das Konto war, als der Bann eingesetzt wurde"
          },
          {
            "level": 2,
            "id": null,
            "text": "Wenn die Valve aktiv wird, stoppt sie den Bot nicht."
          },
          {
            "level": 3,
            "id": null,
            "text": "Was die 11 %, die gesperrt sind, tatsächlich gesperrt sind für"
          },
          {
            "level": 2,
            "id": null,
            "text": "Die Betrüger, die Valve gewähren lässt: Die 53.558-Vollzählung"
          },
          {
            "level": 3,
            "id": null,
            "text": "Bestätigte Betrüger, nach ob die Valve eine betrugsrelevante Sperre angelegt hat (Vollzählung)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Zwei Populationen, eine Entdeckung"
          },
          {
            "level": 2,
            "id": null,
            "text": "Die 100.000-Konto-empirische Überprüfung: Botnetze sind keine Wegwerf-Konten."
          },
          {
            "level": 3,
            "id": null,
            "text": "100.000 Repräsentative, unverzerrte Stichprobe"
          },
          {
            "level": 3,
            "id": null,
            "text": "Fehlertoleranz < ±0,4 %"
          },
          {
            "level": 3,
            "id": null,
            "text": "Warum jede 100k-Stichprobe das gleiche Ergebnis führt"
          },
          {
            "level": 3,
            "id": null,
            "text": "100.000 gesperrte Konten: Bezahlte (Einkaufsverbrauch von $5+) gegenüber freiem eingeschränktem Status"
          },
          {
            "level": 3,
            "id": null,
            "text": "Die schwerwiegende Ermittlungskonsequenz: Industriegrößenartige Account-Kapern"
          },
          {
            "level": 2,
            "id": null,
            "text": "Wie dies verstanden wurde und was es nicht behauptet"
          },
          {
            "level": 3,
            "id": null,
            "text": "Was behauptet wird"
          },
          {
            "level": 3,
            "id": null,
            "text": "Was wird nicht beansprucht"
          },
          {
            "level": 3,
            "id": null,
            "text": "Warum es wichtig ist"
          }
        ],
        "links": [
          "https://help.steampowered.com/en/faqs/view/71D3-35C2-AD96-AA3A",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/asf-ban-census-2026-09-23.json",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/steamrep_steam_bans.csv",
          "https://phishdestroy.io/steam_dossier/de/card_economy.html",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/banned_archiasf_massive.csv",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/slice_100k_limited_results.csv",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/reports/BANNED_100K_FORENSIC_ANALYSIS.md",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/banned_100k_slice.csv",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/reports/STEAM_BANNED_LIMIT_ANALYSIS.md",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/INVESTIGATION_OVERVIEW.md",
          "https://phishdestroy.io/steam_dossier/de/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/reports/STEAMREP_VS_STEAM_AUDIT.md",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/SteamRep_Profiles_BannedCaution_2024.csv",
          "https://phishdestroy.io/steam_dossier/de/security_timeline.html",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/reports/russian_conflicts_report.json",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/reports/classification_report.json",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/reports/VALVE_INCOMPETENCE_REPORT.md",
          "https://phishdestroy.io/steam_dossier/de/steam_evidence_archive.html",
          "https://phishdestroy.io/steam_dossier/de/steam_enforcement_evidence.html",
          "https://phishdestroy.io/steam_dossier/de/#insider-threat",
          "https://phishdestroy.io/steam_dossier/de/"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/de/enforcement_audit_de.content.json",
      "export_json_sha256": "2e9131636a58613b4a58342ceccde64db8fbcc597018dd50289c4d3615912e5a"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "index.html",
      "language": "en",
      "title": "The Steam Dossier: rules, routes and accountability",
      "source_url": "https://phishdestroy.io/steam_dossier/index",
      "source_html_sha256": "fe536ca0e41a575ed6cff54bd1a37590cfd1e84f48cbf884c692ab80ab6a559a",
      "exported_at": "2026-09-29T00:15:54.303Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "exhibit-gallery-section",
            "source": "https://phishdestroy.io/steam_dossier/index#exhibit-gallery-section"
          }
        ],
        "raster_images_replaced": 2
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "index.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/en/index.pdf?v=print-20260929-v5",
        "sha256": "2b92a6ef761d231329061f9394148ab5bc4ea536b41529c90df0c21afa47bb0b",
        "bytes": 914812,
        "pages": 98
      },
      "integrity": {
        "signed_object": "index.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "index.content.json.asc",
        "digest_file": "index.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify index.content.json.asc index.content.json",
          "sha256sum -c index.content.json.sha256"
        ]
      },
      "content": {
        "text": "Dieses Material ist auf Englisch verfügbar.Zurück zum Dossier · Deutsch ↗\nTL;DR — 5 VERIFIABLE CLAIMSAll 5 verifiable against Valve's own servers, documents and published dates\n44\n\nseparate auth-host domains found carrying Steam logins for third-party platforms — each a domain registered apart from the platform's main address.\n\nSection 3 →\n26\n\nfilter-split pairs: main domain shows a Steam Link Filter warning; the login host beside it does not.\n\nSection 3.2 →\n12y 6m\n\nis how long api.csgem.com has carried Steam logins while csgogem.com sits on the Link Filter. Registered March 2014.\n\nView table →\n10 days\n\nwas Valve's own 2016 deadline to gambling operators. No per-operator enforcement record has been published since.\n\nSection 2 →\n830 pp\n\nArt. 15 GDPR response from Valve's lawyers — 902,270 characters of extractable redactions, redaction bars left as selectable text.\n\nSection 18 →\nWHAT THIS MEANS — THE STEAM LINK FILTER\n\nValve maintains a link filter that blocks links to gambling and trading sites when posted in Steam chat or profile comments. When a user clicks a blocked link, Valve displays a full-screen warning: \"This link has been flagged as potentially malicious.\" However, Valve only checks the primary website domain. The separate domains used for Steam OpenID authentication are not on the blocklist — so the login flow succeeds even though the main site is blocked.\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\nSection 1 — Case briefing\nThe rule. The record. The unanswered questions.\nContext & source limits\n\nSix findings, each tied to a dated public record. The detailed sections follow the same order: technical record (Part A), rules and enforcement record (Part B), legal frameworks (Part C), then the appendices with the primary exhibits.\n\nSix findings. Each connects a written rule to a dated record and a question the evidence can test.\n\n1. Separate-domain auth hosts — 44 routes · 26 split pairs\n\nThe live register records 44 platforms authenticating through a separate registrable domain. Five further routes sit in pending verification awaiting an RDAP date; promoting them would take the total to 47. They are excluded from 44 and from the age chart. — 27 with a published per-route evidence file and 17 added from manual collection, listed apart. In 26 filter-split pairs the main domain is BLOCKED in the Steam Link Filter while the proxy carrying its login is not. These are not burner domains: csgogem.com is blocked while api.csgem.com, the host carrying its Steam login, has been registered since March 2014 — 12 years 6 months. Valve receives that hostname in every OpenID request, and renders it back to the user on its own login page. Full table, per-route ages and sourcing in Section 3.\n\nFollow the route →\n2. 2016: the mechanism was named, the deadline set\n\nOn 13 July 2016 Valve publicly described how gambling sites used Steam OpenID and automated trading accounts, and its counsel's notices of 20 July 2016 set a ten-day deadline. No per-operator enforcement record has been published since. Ten years after that deadline was issued, the same named mechanism is in use on separate-domain auth hosts that returned no Link Filter block on 2026-09-21.\n\nRead the open letter to the WSGC →\n3. Device correlation, on counsel's letterhead\n\nIn the correspondence reproduced here, Valve's counsel described device-level correlation linking one device to multiple accounts — a capability Steam Support had previously told users was not technically possible. The open question is which device-level records Valve holds and on what basis account holders are refused access to them.\n\nRead the memorandum →\n4. Two access responses. One withheld the data, one leaked it.\n\nOctober 2025: Valve's counsel answered an Art. 15 request with an 830-page appendix whose redactions are painted over the text instead of removing it — 902,270 characters come back out with a standard extraction tool, including the third-party identifiers the bars were there to withhold. Art. 15(4) is the reason those bars exist. September 2026: ticket HT-2YBP-F7JP-D4VB was closed after three days with a link to the self-service Account Data page — no data, no stated legal basis. The one-month period under Art. 12(3) had not expired at publication; the objection is to the substance.\n\nRead the redaction check →Read the ticket record →\n5. The market above Steam's ceiling\n\nSteam caps a Market listing at about $1,800. Across five marketplaces in a dated snapshot (23 Sep 2026), 248 CS2 item categories are priced above that cap by two or more of them independently, and all 248 are absent from Steam; a Factory New Dragon Lore starts at $10,941 across 389 copies listed on all five (the CSFloat-only figure in Section 13, from the 20 Sep snapshot, is $10,623.95 across 62 offers). Selling at those prices requires an outside venue, while item transfer still runs through Steam.\n\nFollow the price and transfer →\n6. The rule is explicit; the audit trail is not\n\nThe Subscriber Agreement reserves Steam for personal, non-commercial use, bars commercial exploitation except as expressly permitted, prohibits scripts and bots, and allows account termination. Valve applied that language to gambling operators in 2016. Separately, according to CSFloat's engineering account, Valve closed IEconItems_730/GetPlayerItems in 2017, removing public access to original item IDs (no Valve changelog located).\n\nPut the rule beside the network →\n2016 / Written demand 10 days\nDeadline in Valve counsel's July 2016 notices to gambling sites. Open letter to the WSGC: Section 2.\n2017 / Public audit trail ID access closed\nCSFloat records the loss of original item IDs.\nCounsel correspondence Device correlation\nOne device linked to dozens of stolen accounts.\nRoute register Blocked, and still logging in\nThe rule: Valve's 2016 statement prohibits running a gambling business on Steam OpenID. The record: 26 main domains sit on the Link Filter while the host carrying each one's Steam login runs on — csgogem.com's has run 12 years 6 months.\nSection 2 — Open letter\nOpen letter to the Washington State Gambling Commission\n\nTen days became ten years. The Commission's 2016 question to Valve has not been answered with an operator-by-operator record; this letter asks it to reopen the file.\n\nPUBLIC ADDRESS · WASHINGTON STATE GAMBLING COMMISSION\n\nTen days became ten years.Reopen the record.\n\nTo the Washington State Gambling Commission:\n\nIn 2016, Director David Trujillo asked Valve to show what it had done to stop the use of Steam skins for gambling. Then-Chair Chris Stearns and the Commission confronted an industry built on Valve-issued items and Steam transfers. Both men have since left their Commission roles. The question they put to Valve has not expired.\n\nValve's general counsel, Karl Quackenbush, gave gambling operators ten days to stop commercial use of Steam accounts. In its October response to your Commission, Valve denied facilitating gambling, said it had sent cease-and-desist letters to more than forty sites and said it had disabled associated accounts. It also defended preserving Steam trading and OpenID because those services benefited customers and game developers. That was an assertion of control. It deserves a test, not deference.\n\nIn our assessment, Valve's answer did not demonstrate that its chosen enforcement matched the scale of the network it described. A threatening letter to an operator is not the same thing as a durable block on the Steam accounts, trading infrastructure and authentication routes that make the business work. Reported estimates put CS:GO Lounge alone above $1 billion in betting handle during 2016; that is an outside estimate of wagers, not Valve revenue, and the site's original skin-betting operation later shut down. The scale made verifiable enforcement essential.\n\nToday, Valve's own Subscriber Agreement archived 2026-09-21 ↗ restricts commercial exploitation except where expressly permitted and separately prohibits specified forms of automation. Our dated route register records declared OpenID return hosts for outside services; openid.realm and openid.return_to are fields sent to Steam, not secrets hidden from it. Our Link Filter checks show cases where a main address was warned against but an associated login host was not. A filter result alone cannot prove that Valve allowed a login or that a particular bot evaded an account ban. It does prove that a homepage warning cannot be offered as a complete answer about access.\n\nNor can the existence of useful, lawful Steam trading and OpenID functions answer whether prohibited operators were actually excluded. Valve's own rules allow express exceptions. If Valve relies on that distinction, the Commission should ask it to identify the authorisation, account controls and enforcement criteria applicable to commercial skin businesses, and the specific non-gambling uses it invoked in 2016. The mere possibility of lawful use is no answer to documented prohibited use.\n\nWe ask the Commission to revisit its 2016 file and request an operator-by-operator account: which Steam accounts and trading bots were disabled after the ten-day notices; whether related accounts or return hosts were monitored; which operators later regained access; what exemptions were granted; and what records support Valve's statement to the Commission. Publish what law allows the public to inspect. Compare those records with current routes and with Valve's later interventions, including OPSkins in 2018 archived 2026-03-07 ↗.\n\nThe notice set a ten-day deadline in July 2016; ten years is long enough to establish whether it was carried out. The Commission should test Valve's 2016 account against the infrastructure that remains observable today.\n\nThe Steam Dossier investigation · Public statement, 20 September 2026\n\n2016 Commission notice ↗ archived 2026-05-20 ↗ · Valve's 2016 reply (document copy) ↗ · Valve's 2016 OpenID statement ↗ archived 2026-09-21 ↗ · Current Steam agreement ↗ archived 2026-09-21 ↗ · Timeline of the 2016 exchange: Section 11 →\n\nPart A — Technical record · Section 3\nThe site is blocked. The login route is not.\n\n26 blocked main domains. The authentication proxy behind each one, and how long it has been alive. These separate auth hosts are not incidental second addresses — each one is an authentication proxy for Steam, standing between the platform and Valve's OpenID endpoint and carrying the login the blocked domain can no longer carry in the open. Valve put the front door on the Link Filter. The sign-in kept running through the proxy: csgogem.com is blocked, and api.csgem.com has been registered since March 2014 — twelve and a half years. Every one of those days that host sent its own hostname to Valve's OpenID endpoint, and Steam rendered it straight back to the user on the login page. Valve is the trunk every one of these routes runs through; it does not have to find them. That is what this section measures: not whether a warning exists, but how many years the route behind the warning stays open. 44 separate-domain routes in the register, 27 of them with a published per-route evidence file — the table below. Follow one example, then measure all of them.\n\nFigure 3.1 — The two routes, drawn.\n\nOne platform, one player, two requests leaving the same browser. Valve's Link Filter stands on both. It stops the one that carries a link and passes the one that carries the login. Everything measured in this section is a count of how long the lower route stays open.\n\nThe player\none browser, one session\nrollbit.com\nthe platform's main domain\nrbsnin.com\nseparate authentication host\nLINK FILTER\n✕ BLOCKED\nLINK FILTER\n✓ CLEAN\nsteamcommunity.com\nOpenID endpoint · signs in\nno route\nLink posted in Steam — stoppedLogin request — passesSaved checks of 19 and 21 September 2026\n\nBoth requests are visible to Valve, and only one is acted on. The Link Filter is a Valve list, checked by a Valve service. The OpenID request carries the auth host's own name to Valve's endpoint, which prints it straight back on the login page. The hostname is in the request either way — what differs is whether anything is done with it.\n\nOne platform. Two different routes.ROLLBIT / SAVED OBSERVATIONS\nStep 5 / 5\n\nThe request reaches Steam. The observed route reached Steam's login form. The authors did not complete the login. Blocking the main-domain link did not block this observed route to the form.\n\n01 THE LINK FILTER CHECK\nDESTINATIONrollbit.comThe platform's main domain\nSTEAM LINK FILTERChecks the linkA separate destination-warning system\nSAVED RESULTLink blocked19 & 21 September 2026\n02 THE OBSERVED SIGN-IN ROUTE\nON THE PLATFORMSign in with SteamThe platform starts an OpenID request\nSEPARATE AUTH HOSTrbsnin.comNo Link Filter block in the saved check\nSTEAMLogin form servedThe requested host appears in Steam's notice\nInspect the original capture notes, registration date and protocol details\nWhat Valve's enforcement looks like\nMain domain: blocked\nUser\n→\nrollbit.com\n(main domain)\n↓\nSTEAM LINK FILTER — BLOCKED\n\"Link Blocked!\" — flagged as potentially malicious\nrollbit.com returned a Link Filter block on 2026-09-19 and 2026-09-21 (unauthenticated check; raw HTML and SHA-256 saved). A visible, auditable record.\nWhat actually happens — authentication\nAuth host: not blocked\nUser\n→\nrollbit.com\n\"Sign in with Steam\"\n↓\nRedirect via separate auth host:\nrbsnin.comLink Filter: CLEAN\nregistered 2026-09-18T09:34:52Z (Verisign RDAP)\n↓\nSteam login page notice (2026-09-20):\n\"Note that rbsnin.com is not affiliated with Steam or Valve\"\nSteam renders this notice from the openid.realm of the request it received.\n↓\nSteam login form served for the separate host\nThe login was not completed by the authors; the flow was observed up to the Steam form.\nValve receives the return_to / realm hostname on every such request. rbsnin.com returned no Link Filter block on 2026-09-21.\nPer request\nAs the OpenID provider, Steam receives the auth hostname with every authentication request: it arrives at Valve's own servers in the openid.return_to and openid.realm parameters.\nSent by the site\nThe auth host is not discovered by scanning — the platform sends it to Steam in each request. Under OpenID 2.0 §9.1 return_to is formally optional, but without it Steam cannot deliver the login result, so for a working Steam login it is effectively required. Steam even renders the hostname to the user (\"<host> is not affiliated with Steam or Valve\").\n14 yr\nis the age of the oldest auth host still carrying Steam logins at the 2026-09-21 check (dota2.net, registered 2011-10-29); the newest is three days old (rbsnin.com). Do not read the \"0 auth hosts blocked\" figure as the finding. A blocked auth host would break the platform's \"Sign in with Steam\" outright, so a register built from working logins can only contain hosts that were never blocked. The number that carries meaning is not the block count — it is how many years the main domain sat on the Link Filter while the login beside it kept running.\nSeparate-domain auth hosts: registration date vs. main domain (30 routes: the 25 resolved in the 2026-09-21 browser audit, plus 5 added on 2026-09-22)\nPlatform\tLink Filter: main\tAuth host\tLink Filter: auth host\tAuth host registered\tSource of observation\tEvidence file\nRollbit\nrollbit.com · reg. 2014-11-08\n\tBLOCKED\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\trbsnin.com\tCLEAN\n2026-09-21 · raw HTML (no Wayback snapshot)\n\t2026-09-18\n09:34:52Z, Verisign RDAP\n\tSteam login-page notice, 2026-09-20\trollbit.com.json\nSkin.Club\nskin.club · reg. 2017-09-04\n\tBLOCKED\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\tsc-auth.net\tCLEAN\n2026-09-21 · Wayback 2026-09-21\n\t2019-04-02\nRDAP\n\tSteam login-page notice\tskin.club.json\nHowl.GG\nhowl.gg · reg. 2017-03-16\n\tBLOCKED\n2026-09-18, 09-19, 09-21 · Wayback 2026-09-21\n\thowl.uno\tCLEAN\n2026-09-21 · Wayback 2026-09-21\n\t2026-08-11\nRDAP\n\tLive browser capture + supplied OpenID URL\thowl.gg.json\nDuelbits\nduelbits.com · reg. 2020-02-03\n\tBLOCKED\n2026-09-21 · Wayback 2026-09-21\n\tswitchflips.com\tCLEAN\n2026-09-21 · Wayback 2026-09-21\n\t2020-04-21\nRDAP\n\tSupplied OpenID URL\tduelbits.com.json\nCSGOFast\ncsgofast.com · reg. 2015-03-27\n\tBLOCKED\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\tsteam-login.authtofast.com\tCLEAN\nauthtofast.com, 2026-09-21 · Wayback 2026-09-21\n\t2026-06-30\nauthtofast.com, RDAP\n\tLive browser capture + supplied OpenID URL\tcsgofast.com.json\nFarmskins\nfarmskins.com · reg. 2016-03-23\n\tBLOCKED\n2026-09-19, 2026-09-21 · raw HTML\n\tsteam.kobal.cc\tCLEAN\n2026-09-19, 2026-09-21 · raw HTML\n\t2017-01-07\nkobal.cc, RDAP\n\tLive browser capture + supplied OpenID URL\tfarmskins.com.json\nCobaltLab\ncobaltlab.tech\n\tBLOCKED\n2026-09-21 · raw HTML\n\tcobaltauth.com\tCLEAN\n2026-09-21 · raw HTML\n\t2025-01-07\nRDAP\n\tSupplied OpenID URL\tcobaltlab.tech.json\nCSGO.NET\ncsgo.net · reg. 2012-07-22\n\tBLOCKED\n2026-09-21 · raw HTML\n\tcn2.easylot.net\tCLEAN\n2026-09-21 · raw HTML\n\t2016-09-03\neasylot.net, RDAP\n\tLive browser capture\tcsgo.net.json\nGGDrop\nggdrop.com\n\tBLOCKED\n2026-09-21 · raw HTML\n\tggauth.com\tCLEAN\n2026-09-21 · raw HTML\n\t2023-05-03\nRDAP\n\tSupplied OpenID URL\tggdrop.com.json\nRustChance\nrustchance.com\n\tBLOCKED\n2026-09-21 · raw HTML\n\thgfuihd.com\tCLEAN\n2026-09-21 · raw HTML\n\t2019-01-27\nRDAP\n\tSupplied OpenID URL\trustchance.com.json\nSkin.Fans\nskin.fans\n\tBLOCKED\n2026-09-21 · raw HTML\n\tauth.skinfans.com\tCLEAN\n2026-09-21 · raw HTML\n\t2018-07-16\nskinfans.com, RDAP\n\tSupplied OpenID URL\tskin.fans.json\nSkinport\nskinport.com · reg. 2018-09-05\n\tBLOCKED\n2026-09-21 · raw HTML\n\tskinport.app\tCLEAN\n2026-09-21 · raw HTML\n\t2020-06-20\nRDAP\n\tLive browser capture + supplied OpenID URL\tskinport.com.json\nSkins.Cash\nskins.cash\n\tBLOCKED\n2026-09-21 · raw HTML\n\tskinscash.live\tCLEAN\n2026-09-21 · raw HTML\n\t2019-12-05\nRDAP\n\tSupplied OpenID URL\tskins.cash.json\nTF2Hunt\ntf2hunt.com · reg. 2018-01-13\n\tBLOCKED\n2026-09-21 · raw HTML\n\trstspcl.com\tCLEAN\n2026-09-21 · raw HTML\n\t2020-08-08\nRDAP\n\tLive browser capture + supplied OpenID URL\ttf2hunt.com.json\nCSGOGem\ncsgogem.com · reg. 2016-10-16\n\tBLOCKED\n2026-09-22 · raw HTML\n\tapi.csgem.com\ncsgem.com — separate registrable domain\n\tCLEAN\n2026-09-22 · raw HTML\n\t2014-03-08\ncsgem.com, RDAP — oldest in register\n\tManual collection + Link Filter capture\tlinkfilter-2026-09-22.json\nGamdom\ngamdom.com · reg. 2016-07-29\n\tBLOCKED\n2026-09-22 · raw HTML\n\tlogin.gambldom.com\ngambldom.com — one letter off the brand\n\tCLEAN\n2026-09-22 · raw HTML\n\t2017-09-24\ngambldom.com, RDAP\n\tManual collection + Link Filter capture\tlinkfilter-2026-09-22.json\n12CS\n12cs.fail · reg. 2026-03-24\n\tBLOCKED\n2026-09-22 · raw HTML\n\tfail.games\tCLEAN\n2026-09-22 · raw HTML\n\t2021-08-24\nfail.games, RDAP\n\tManual collection + Link Filter capture\tlinkfilter-2026-09-22.json\nCSGOEmpire\ncsgoempire.com · reg. 2015-06-10\n\tCLEAN\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\tcsgoempirelogin4.com\none of ten numbered domains login1–10\n\tCLEAN\n2026-09-21 · Wayback 2026-09-21\n\t2020-07-20\n05:49:17Z, Verisign RDAP\n\tLive browser capture\tcsgoempire.com.json\nCS.MONEY\ncs.money\n\tCLEAN\n2026-09-21 · raw HTML\n\tauth.dota.trade\tCLEAN\n2026-09-21 · raw HTML\n\t2016-07-15\ndota.trade, RDAP\n\tSteam login-page notice\tcs.money.json\nCSFloat\ncsfloat.com · reg. 2021-07-11\n\tCLEAN\n2026-09-21 · raw HTML\n\tcsgofloat.com\noperator's former brand domain; separate registrable domain, not an evasion indicator\n\tCLEAN\n2026-09-21 · raw HTML\n\t2015-09-29\nRDAP\n\tLive browser capture\tcsfloat.com.json\nG4Skins\ng4skins.com\n\tCLEAN\n2026-09-21 · raw HTML\n\tauth.g4s.to\tCLEAN\n2026-09-21 · raw HTML\n\t2021-05-30\ng4s.to, RDAP\n\tSupplied OpenID URL\tg4skins.com.json\nJuice.GG\njuice.gg\n\tCLEAN\n2026-09-21 · raw HTML\n\tletmeinjuice.com\tCLEAN\n2026-09-21 · raw HTML\n\t2024-04-15\nRDAP\n\tSupplied OpenID URL\tjuice.gg.json\nMarket.CSGO\nmarket.csgo.com\n\tCLEAN\n2026-09-21 · raw HTML\n\tdota2.net\tCLEAN\n2026-09-21 · raw HTML\n\t2011-10-29\nRDAP\n\tLive browser capture + supplied OpenID URL\tmarket.csgo.com.json\nRust.TM\nrust.tm\n\tCLEAN\n2026-09-21 · raw HTML\n\tdota2.net\tCLEAN\n2026-09-21 · raw HTML\n\t2011-10-29\nRDAP\n\tSupplied OpenID URL\trust.tm.json\nCSGOLounge\ncsgolounge.com · reg. 2013-08-14\n\tCLEAN\n2026-09-22 · raw HTML\n\tdota2.net\nthird front-end on this auth host\n\tCLEAN\n2026-09-22 · raw HTML\n\t2011-10-29\ndota2.net, RDAP\n\tManual collection + Link Filter capture\tlinkfilter-2026-09-22.json\nDota2Lounge\ndota2lounge.com · reg. 2012-08-10\n\tCLEAN\n2026-09-22 · raw HTML\n\tdota2.net\nfourth front-end on this auth host\n\tCLEAN\n2026-09-22 · raw HTML\n\t2011-10-29\ndota2.net, RDAP\n\tManual collection + Link Filter capture\tlinkfilter-2026-09-22.json\nSkinBaron\nskinbaron.de\n\tCLEAN\n2026-09-21 · raw HTML\n\tskinbaron.com\nsame brand, different TLD\n\tCLEAN\n2026-09-21 · raw HTML\n\t2015-12-22\nRDAP\n\tSupplied OpenID URL\tskinbaron.de.json\nTF2Royal\ntf2royal.com · reg. 2022-08-17\n\tCLEAN\n2026-09-21 · raw HTML\n\ttf2auth.com\tCLEAN\n2026-09-21 · raw HTML\n\t2021-07-27\nRDAP\n\tLive browser capture + supplied OpenID URL\ttf2royal.com.json\nTradeit\ntradeit.gg\n\tCLEAN\n2026-09-21 · raw HTML\n\tconnect-tradeit.com\tCLEAN\n2026-09-21 · raw HTML\n\t2022-02-23\nRDAP\n\tSupplied OpenID URL\ttradeit.gg.json\nUpgrader\nupgrader.pro\n\tCLEAN\n2026-09-21 · raw HTML\n\tupgauth.space\tCLEAN\n2026-09-21 · raw HTML\n\t2026-08-14\nRDAP\n\tSupplied OpenID URL\tupgrader.pro.json\nSource: steamcommunity.com/linkfilter, unauthenticated GET, 2026-09-21, 53 hosts, 3 s spacing; steam_tos_assets/linkfilter-recheck-2026-09-21.json; raw HTML in steam_tos_assets/linkfilter-raw/. Registration dates: RDAP, steam_tos_assets/domain-registration.json. · Earlier check of 2026-09-19 in linkfilter-all-results.json · route records in auth-route-audit.json · Wayback Machine snapshots of the Link Filter pages, 2026-09-21, listed in wayback-snapshots.json (no snapshot exists for rbsnin.com; the local raw file is the only record).\n\nRegistration dates: RDAP (steam_tos_assets/domain-registry/). \"Supplied OpenID URL\" establishes the request parameters, not a completed login. No login was completed by the authors on any platform. A separate domain is not by itself proof of evasion. Nor is \"0 auth hosts blocked\" an independent finding: blocking one would break that platform's Steam login, so a register assembled from working logins cannot contain a blocked auth host. The observation that carries weight is the pairing and its duration — a main domain on the Link Filter beside a login domain that has run for years. This table carries 30 rows: 25 of the 27 routes with a per-route evidence file, plus five added on 2026-09-22 whose Link Filter split is captured in linkfilter-2026-09-22.json even though the realm itself was hand-collected — their rows say so in the source column. The two evidence-file routes not shown are skinsnipe.com (auth host pricing.tradeupspy.com, registered 2020-03-11) and csgobig.com (auth host letmeinbig.com, registered 2023-01-20); both returned BLOCKED main / CLEAN auth host in the check of 2026-09-22, recorded with SHA-256 in linkfilter-2026-09-22c.json, but the raw HTML for that batch is not in the published set, so they are named here rather than given a row that every other line in this table can evidence. The remaining 12 hand-collected routes in the register are identified as such in master_registry.json under realm_src: user.\n\nPrimary Empirical Audit · Multi-Year Date Range\nThe Big Picture Trap: Link Filter is Compliance Theater, Not a Shield\n\nOn desktop browsers, users are shielded by external defenses: Google Safe Browsing and Microsoft SmartScreen intercept known phishing with full-screen red warnings. Inside Steam's Big Picture mode, the in-game overlay (Shift+Tab), and the Steam Deck (SteamOS), those defenses do not exist. The embedded browser supports zero extensions, disables external Safe Browsing engines, and leaves the user with exactly one defensive barrier: Valve's linkfilter interstitial.\n\nSwipe to compare all four results →\n\n92.5%\n2025–2026 modern edge phishing passed clean (37/40)\n77.5%\n2023–2024 CS2 era phishing passed clean (31/40)\n70.0%\n2021–2022 legacy phishing passed clean (28/40)\n7 / 7\ngambling mains blocked (positive control)\nMulti-Year Longitudinal Audit: 120 Pure Steam Phishing Domains Tested Live (24 Sep 2026)\n\nTo test whether Valve's filter is simply slow to ingest new threats or fundamentally blind to them, we audited 120 confirmed Steam-specific phishing domains across three historical cohorts against steamcommunity.com/linkfilter:\n\nCohort 1: 2021–2022 (Classic Trade-Offer & Item Drops) — 70.0% Clean Pass (28/40). Even 4 to 5 years after being cataloged by community watchdogs, 7 out of 10 legacy phishing hosts still open without any block.\nCohort 2: 2023–2024 (CS2 Beta Hype & Fake Support Appeals) — 77.5% Clean Pass (31/40). Campaigns impersonating Counter-Strike 2 releases and fake community appeals (e.g. cs2-steam.com, appealsteamcommunity.help) pass straight through.\nCohort 3: 2025–2026 (Serverless Edge Deploys & Favicon Clones) — 92.5% Clean Pass (37/40). Modern phishing kits deploying on EdgeOne, Vercel, and Cloudflare Pages (e.g. steamgifter.online, steam-dp4lt5b8fnez.edgeone.dev) pass virtually unobstructed.\n\nTelemetry & Liability Shield, Not Protection. Why does the Link Filter exist if it passes 70% to 92.5% of pure Steam phishing? It functions as a corporate liability disclaimer and an outbound click telemetry sensor. By presenting a polite \"You are leaving Steam\" notice with a clickable green proceed button, Valve shifts legal blame onto the victim under the Steam Subscriber Agreement (*\"the user voluntarily navigated outside Steam\"*). Valve collects the telemetry of the click, but does not block the theft.\n\nThe Favicon Hash Proof: Zero Ingestion of Threat Feeds. Independent threat intelligence platforms (urlscan.io, Shodan, Censys) identify live Steam phishing kits using a simple search for Steam's official favicon hash (page.favicon.hash:9f890a9debcdfccc339149a7943be9aff9e4c9203c2fa37d5671a5b2c88503ad NOT domain:*.steampowered.com). This basic automated check surfaces active phishing clusters in seconds. Valve does not sync with external feeds, does not run hash-based threat hunting, and only manually intervenes when compelled by regulators (the 2016 WSGC gambling order) or to protect its trademarked domain strings.\n\nPrimary audit evidence artifacts: Longitudinal 120-domain multi-year audit: longitudinal-steam-phishing-audit.json · 100 dedicated Steam phishing sample: linkfilter-steam-phishing-100.json · Broad feed audit (n=250): linkfilter-coverage-2026-09-22.json.\n\nCSGOEmpire — batch registration of ten numbered auth domains\n\nOn 2020-07-20 ten numbered domains, csgoempirelogin1.com through csgoempirelogin10.com, were registered. Verisign RDAP timestamps are on file for all ten: login1 05:49:06Z, login5 05:49:08Z, login2 05:49:11Z, login3 05:49:14Z, login4 05:49:17Z, login6 05:49:20Z, login7 05:49:23Z, login8 05:49:26Z, login9 05:49:28Z — nine domains in 22 seconds — and login10 at 05:56:03Z, seven minutes later. The spacing is consistent with a single registrar bulk operation.\n\nThe pattern is consistent with pre-provisioned fallback hosts; only login4 has been observed in a live OpenID request. csgoempire.com and csgoempirelogin4.com both returned CLEAN in the Link Filter on 2026-09-21; CSGOEmpire was not among the sites named in press reports of the July 2016 notices.\n\n# DNS — all 10 active (September 2026)\nOK csgoempirelogin1.com 172.67.129.43\nOK csgoempirelogin2.com 172.67.175.168\nOK csgoempirelogin3.com 188.114.96.3\nOK csgoempirelogin4.com 188.114.96.11 ← in OpenID traffic\nOK csgoempirelogin5.com 172.67.160.194\nOK csgoempirelogin6–10.com Cloudflare IPs\nNXDOMAIN: csgoempirelogin11.com\nAll 10 registered 2020-07-20; all 10 RDAP-timestamped (steam_tos_assets/domain-registry/csgoempireloginN.com.rdap.json)\nConclusion for regulators\nA blocked main domain paired with an unblocked auth host leaves the login route open — and it stays open for years.\n\nThe Link Filter block on the main domain is a verifiable, public record. The auth host carries the \"Sign in with Steam\" traffic and appears in Valve's own OpenID request parameters. Across checks on 2026-09-21 and 2026-09-22, in 26 filter-split pairs the main domain returned a Link Filter block while the proxy carrying its login returned none. The register above measures the other half of that: these hosts are not short-lived burner domains. Several had been registered for more than a decade at the date of the check, and every one of those days is a day on which Valve received the hostname in its own request parameters. Valve has published no per-operator enforcement record, so whether any other measure was applied to these hosts cannot be established from public data.\n\n12 yr 6 mo\ncsgogem.com is blocked in the Link Filter.\nIts login host api.csgem.com has been\nregistered since 2014-03-08 and is not.\nPlain Language Summary — For Regulators & Courts (expand)\nPlain language summary — for regulators\nBackground: What Steam Is and Why It Matters Here\n\nSteam is a software platform operated by Valve Corporation (Bellevue, Washington, USA). Steam functions as a digital identity provider: gambling and gaming websites across the internet use a system called \"Sign in with Steam\" — a button that allows a website to verify that a visitor has a real Steam account. This is similar to \"Sign in with Google\" or a government-issued identity card check: the website sends the user to Steam's servers, Steam confirms who they are, and Steam sends them back to the website. Valve operates the authentication system. Every single login through \"Sign in with Steam\" passes through Valve's own servers.\n\nWhat Valve Did: The Domain Block\n\nIn July 2016, following media and legal pressure over skin gambling, Valve's counsel sent notices to approximately 23 named gambling sites (per press reports of 21 July 2016); in October 2016 Valve told the Washington State Gambling Commission it had contacted more than forty sites. Some gambling domains appear in the Steam Link Filter — a list that makes any link to them posted inside Steam (in chat, on a profile page, in the store) show a warning page: \"Link Blocked!\" The Link Filter is the only enforcement measure whose effect can be observed from outside Valve.\n\nExample: A link to rollbit.com inside Steam produces the Link Filter warning page (checked 2026-09-19 and 2026-09-21). On paper, the gambling site is blocked.\nWhat a Proxy Domain Is\n\nA separate-domain auth host is an authentication proxy: a second website address, on a different registrable domain, that the same operator puts between its users and Steam for the sole purpose of carrying the \"Sign in with Steam\" step. It proxies the login. The user believes they are signing in to the platform; the request that reaches Valve carries the proxy's hostname, not the platform's. It usually has no publicly visible connection to the gambling site, and it is the address that receives users back after Steam confirms their identity.\n\nExample: Rollbit operates under rollbit.com, which the Link Filter blocks. For Steam authentication, the flow observed on 2026-09-20 used a separate address: rbsnin.com, registered 2026-09-18. This address returned no Link Filter block on 2026-09-21. The gambling site continued to operate, and its Steam login flow ran through the unblocked host.\nThe Critical Point: The Auth Host Is Sent to Steam in Every Request\n\nValve does not need to scan or crawl to learn which auth hosts are in use. Steam is the OpenID identity provider for these sites, and every \"Sign in with Steam\" click sends a GET request to Valve's own servers containing the auth hostname in plaintext. Under OpenID 2.0 §9.1 the return_to field is formally optional, but without it Steam cannot deliver the login result, so for a working Steam login it is effectively required. Steam itself renders the hostname on the login page (\"<host> is not affiliated with Steam or Valve\").\n\n— Shape of the request Steam receives (host as observed for Rollbit on 2026-09-20): —\nGET steamcommunity.com/openid/login\n&openid.mode=checkid_setup\n&openid.return_to=https://rbsnin.com/… ← effectively required; arrives in Valve's log\n&openid.realm=https://rbsnin.com ← self-declared by the site; rendered on Steam's login page\nIf the site uses server-to-server verification (check_authentication), Valve's log also records the platform's server IP and hosting network.\n\nExtracting the hostname from this request is a standard operation. The enforcement record — which hosts were acted on, which were not, and under what criteria — exists only in Valve's infrastructure and has not been published.\n\nWhat This Proves\n\n1. The Link Filter block acts on links, not on logins. Blocking the main domain (for example rollbit.com) shows a warning to users who click links to it inside Steam. It does not stop the site from operating, or from using Valve's own OpenID service through a different address.\n\n2. The auth hosts tested were not blocked. The table above shows separate-domain auth hosts registered between 2011 and September 2026, several of them years after the July 2016 notices. In 26 pairs the main domain returned a Link Filter block and the proxy carrying its login did not (unauthenticated checks, 2026-09-21 and 2026-09-22; raw responses and SHA-256 saved). That proxy would stop working the day Valve refused it, which is why the measure here is how long it has run, not whether it is listed. Valve receives these hostnames in its own OpenID requests. Whether any measure other than the Link Filter was applied cannot be determined from public data, because Valve has published no per-operator enforcement record.\n\n3. The sites continued to authenticate through Valve's infrastructure. \"Sign in with Steam\" is Valve's service; every authentication through it is a request Valve receives and processes. Valve also earns revenue from case keys, and the Steam Community Market charges a combined fee of about 15% on transactions completed inside the Market (not on external trades). The Link Filter action created a public record; it did not interrupt the authentication relationship.\n\nWould Blocking Have Worked?\n\nBy analogy: when the free domain registrar Freenom wound down in 2023, phishing campaigns that depended on its domains were disrupted. Operational continuity depends on infrastructure stability.\n\nThe same logic applies here. If an auth host were refused in Steam's OpenID processing, the platform's \"Sign in with Steam\" function would break until a new host is registered, certificates issued and DNS propagated. During that window: downtime.\n\nRotation does not make blocking futile. It makes blocking an operational cost. Since new hosts appear in Valve's own request logs on first use, a response could run at the speed of that first use.\n\nBatch registration is itself a signal: CSGOEmpire's login1–login10 were registered on 2020-07-20, nine of them within 22 seconds (Verisign RDAP). A response does not need to be domain-by-domain; a sequential series from one registrar session can be identified as a series.\n\nThe public record does not show an attempt to block auth hosts that was defeated by rotation.\nIt shows main domains blocked while the proxy carrying each login kept running — 26 pairs as of 2026-09-22, the oldest auth host registered 12 years 6 months — and no published enforcement record for any operator.\nThe question for the regulator is therefore: what enforcement, if any, has Valve applied to the auth hosts it receives in its own OpenID requests?\nWhat Valve Did — and Why It Did Not Interrupt the Auth Path\n\nThe table below maps each publicly documented Valve action against whether it affected the OpenID authentication entry point. The finding is not \"Valve did nothing\" — it is that none of the publicly documented actions touched the point where gambling-platform logins pass through Valve's servers.\n\nDate\tValve Action\tAffected openid.return_to path?\nJuly 2016\tPublic statement of 13 July 2016; counsel's notices to ~23 named sites (press, 21 July 2016); >40 sites contacted per Valve's October 2016 letter to WSGC\tNo. Notices and the Link Filter act on operators and links; the OpenID request path was not changed.\n2017\tClosure of IEconItems_730/GetPlayerItems (according to CSFloat's engineering account; no Valve changelog located)\tNo. Affected public item-history visibility. OpenID authentication was not modified.\n2018-03-29\tCS:GO 7-day trade lock announced (blog.counter-strike.net)\tNo. Slowed item movement; the OpenID request path was not changed.\n2022-05-10\tTrade-cancellation endpoints removed from the public Web API (user-detected; no Valve changelog — node-steam-tradeoffer-manager #325)\tNo. Closed the offer-swap tooling; OpenID authentication was not modified.\n2023-12-04\tAPI-key creation now requires mobile confirmation (steamcommunity.com/dev/apikey; no changelog)\tNo. Protected the key endpoint; the auth hosts documented here were not affected.\n2026-09-19 / 09-21\tSteam Link Filter state as observed by the authors\tNo. 14 main domains returned a block in the saved 2026-09-21 recheck — 26 split pairs in the register by 2026-09-22 — while the proxy carrying each login kept running.\nSources: Valve statement of 13 July 2016 (store.steampowered.com/oldnews/22883, archived 2026-09-21) · CSFloat engineering account of the 2017 closure (blog.csfloat.com, archived 2026-09-21) · Link Filter state: linkfilter-recheck-2026-09-21.json.\nThis finding is falsifiable by a single published instance in which Valve refused an OpenID request because openid.return_to pointed to a gambling auth host. No such instance has been located in the public record.\nThe two most recent auth-host registrations\nhowl.unowas registered 2026-08-11 (RDAP), 41 days before 2026-09-21; howl.gg returned a Link Filter block on 2026-09-18, 2026-09-19 and 2026-09-21. Whether the block preceded the registration is not established.\nrbsnin.comwas registered 2026-09-18T09:34:52Z (Verisign RDAP) and was observed in Rollbit's Steam login flow on 2026-09-20 via Steam's own login-page notice; rollbit.com returned a Link Filter block on 2026-09-19 and 2026-09-21, rbsnin.com did not.\nEach host in the table above is sent to Valve's authentication servers as openid.realm on every login attempt.\nFull per-route data and Link Filter verdicts: the table in Section 3 above; raw results in linkfilter-recheck-2026-09-21.json and linkfilter-all-results.json.\nMethodology — How the Route and Link Filter Counts Were Established\n1. Domain resolution\nThe 2026-09-21 audit resolved 78 of 189 requested platforms: 33 authenticate on their own hostname and 20 on their own subdomain — direct authentication, and none of them are counted as separate-domain routes. The remaining 25 authenticate through a separate registrable domain, across 24 distinct hostnames (dota2.net is shared by market.csgo.com and rust.tm): 10 established by live browser capture, 3 by Steam's own login-page notice, 12 by a supplied OpenID URL. The live register (master_registry.json, 2026-09-22) extends that to 44 separate-domain routes: 26 filter-split pairs (main domain BLOCKED, auth host CLEAN) plus 18 further routes without a main-domain split. Of the 44, 27 carry a per-route evidence file; the other 17 were collected by hand and are marked realm_src: user in the register. Five of those seventeen — csgogem.com, gamdom.com, 12cs.fail, csgolounge.com and dota2lounge.com — were added on 2026-09-22 with a Link Filter capture of both hosts (raw HTML + SHA-256 in linkfilter-2026-09-22.json), so the split itself is evidenced even though the realm is hand-collected; they appear in the table above alongside the evidence-file routes. tfauth.com (tf2easy.com) was dropped from the register on 2026-09-22: like arena.fragnet.net, nothing verifiable links it to its origin site. The count is re-derivable from the published auth-route-audit.json (run of 2026-09-21) by one rule: a platform counts only when its observed Steam OpenID host sits on a different registrable domain than the platform itself.\n2. Steam Link Filter status\nTested via steamcommunity.com/linkfilter/?url=https://[domain], unauthenticated, on 2026-09-19 and 2026-09-21; raw HTML saved with SHA-256. Status recorded for main domain and auth host separately. A classifier distinguishes the generic \"You are leaving Steam\" notice (CLEAN) from the \"Link Blocked! ... flagged as potentially malicious\" page (BLOCKED); a google.com control confirms the two are not conflated. An earlier authenticated variant of this test was discarded after it returned \"blocked\" for every domain including that control — traced to an invalid session cookie in the probe script, not a real result.\n3. Observation of the auth host\nLive capture: a Playwright browser navigated to each platform's login flow and the openid.return_to hostname was read from the intercepted request. Login-page notice: the hostname was read from Steam's own \"<host> is not affiliated with Steam or Valve\" text, which Steam renders from openid.realm (rbsnin.com, sc-auth.net, auth.dota.trade). Supplied URL: a Steam loginform URL provided to the authors; this establishes the request parameters, not a completed login. No login was completed on any platform.\n4. Coverage — what was not resolved, and why that matters\nOf the 189 platforms, 110 produced no established route and one was not applicable (189 − 78 − 1). This dossier counts none of them. The breakdown of the 110, from the audit file: 22 bot challenges, 14 timeouts, 12 HTTP errors and 10 navigation errors — the observer could not reach the login flow, though most of these sites open normally in an ordinary browser; 20 showed no Steam login control on the landing page; 16 reached a login flow that could not be resolved to a host; 11 domains did not resolve in DNS; 5 stopped at a consent wall. The register below splits the same 110 differently: the 11 that did not resolve in DNS are listed separately as Removed · NXDOMAIN, and the one not-applicable entry joins the rest. 189 platforms audited, 11 removed on a definitive NXDOMAIN from both resolvers, 178 retained (platform-audit.json, platforms-removed.json). 137 auth domains that the ledger had guessed by naming pattern were deleted from the data on 2026-09-19 — never observed, therefore never evidence. Three of the guesses were contradicted by supplied OpenID URLs: buff.163.com, gamerpay.gg and csgoluck.com authenticate directly, against guesses of buffauthproxy.163.com, gamerpayredirect.io and lucklogin.app. The removals are listed in the published audit file.\nThe 25 is a floor, not a ceiling. Among the 78 platforms that did resolve, 25 used a separate domain and 53 did not. Nothing about the unresolved 110 is assumed from that ratio, and no projection from it appears anywhere in this dossier. Each one is resolvable by a person opening the site and pressing \"Sign in with Steam\": the auth hostname is in the URL of the Steam page that loads.\nThe point of this section: an independent observer needs a browser and a lot of patience to resolve 189 platforms, and got 78. Valve needs a database query. Every platform that uses \"Sign in with Steam\" — resolved and unresolved alike — sends openid.realm to Valve's authentication endpoint on every login. The gap in this table exists because the authors are outside the system. It does not exist for Valve.\nObserved proxy hostnames are in auth-route-audit.json. Domain registration dates from RDAP (Verisign) / IP2WHOIS. Link Filter results in linkfilter-all-results.json.\nAnalogy for clarity\n\nImagine a licensed taxi company is told by regulators that it may no longer operate from its registered Main Street address. The company removes the sign from Main Street. That sign removal is documented. However, the same company opens a Side Street address — registered under a different name — and continues operating from there. The regulators operate the central dispatch system that every taxi from both addresses uses. Every ride request shows \"pick up from Side Street.\" The regulators never revoke the Side Street licence. The removal of the Main Street sign is the only enforcement that occurred. The taxi company never stopped operating.\n\nPart A — Technical record · Section 3.1\nInside Steam, Valve's list is the only list.\n\nA link clicked in the Steam client, the in-game overlay or Big Picture mode does not open in the user's browser. It renders inside Steam's own embedded browser — where the warning layers a browser would apply are not present. The Link Filter is not one safeguard among several. It is the whole of it.\n\nIn a normal browserThree independent layers\nGoogle Safe BrowsingA full-page interstitial for hosts on Google's phishing and malware lists, updated continuously and independent of the site being visited.\nThe antivirus browser extensionMost consumer endpoint products ship a browser add-on that checks the destination against the vendor's own reputation list.\nEndpoint HTTPS inspectionWhere the product performs TLS inspection, page content is scanned before it reaches the user.\nIn the Steam client, overlay and Big PictureOne layer\nGoogle Safe BrowsingNot present. The check requires Google API keys that are not provisioned in embedded Chromium builds; where they are absent, Chromium's own design documentation records that the Safe Browsing handler is simply never added to the request chain.\nThe antivirus browser extensionNot present. Steam's renderer is not the user's browser and loads no extension from the user's browser profile, so no add-on runs against the page.\nEndpoint HTTPS inspectionProduct-dependent. The traffic terminates inside a code-signed Valve process rather than a recognised browser, and a number of endpoint products exempt signed applications from TLS inspection.\nThe Steam Link FilterValve's own blocklist, consulted when a link leaves the Steam ecosystem. This is the sole check that runs — and the table above records what it returns for the auth hosts documented in this section.\nA test any reader can run, and the finding falls if it fails\n\nOpen one of Google's published Safe Browsing test URLs (testsafebrowsing.appspot.com) in Chrome: a full-page red interstitial appears. Open the same URL from a Steam chat message, so that it renders in the Steam client or the overlay: no interstitial appears. The only warning Steam can produce is its own Link Filter page, and only for hosts on Valve's list.\n\nValve's own bug-bounty recordThe one layer has been got around before — on Valve's own record\n\nIf the Link Filter is the only check that runs inside the client, its own failure modes are not a side issue. Two reports on Valve's HackerOne programme, both accepted, both resolved, both since disclosed in full:\n\n#291750archived 2025-11-16 ↗Open Redirect · medium\nLink filter protection bypass\n\nReported 19 November 2017, resolved, disclosed 9 May 2018. The report's own proof of concept: substituting the ideographic full stop 。 (%E3%80%82) for the dot in a hostname — it is possible to bypass the blocking. The interstitial this section is about did not appear.\n\n#1079561archived 2026-09-24 ↗Information Disclosure · high\nBig Picture web browser leaks login cookies and discloses sensitive information (may lead to account takeover)\n\nReported 15 January 2021, resolved, disclosed 21 September 2021. Valve's own severity rating is high, and the title states the consequence. The disclosed record carries the title, rating and dates; the technical write-up is not in the published payload, so nothing further is quoted from it here.\n\nThe authors' reading, not a finding of either report: the two sit on either side of the same gate. One is the warning failing to appear before the destination opens; the other is the session leaving the client once a page is open inside it. The sequence that follows a stolen session — key registered without a prompt, the real trade cancelled, a duplicate sent to a clone — is the pattern set out in Section 5 to Section 8. Both reports are closed; neither is offered as a live vulnerability. What they establish is narrower and enough: the single remaining layer has a documented history of being got around, on Valve's own record.\n\nSource: the HackerOne disclosure record for each report, retrieved 2026-09-22 — number, title, team, weakness, severity, report and disclosure dates and state as published by HackerOne. Retrieval record: hackerone-reports.json. No bounty figure is stated here; none appears in the disclosed record retrieved.\n\nField observation · PhishDestroyDetections that normally end a campaign did not end these\n\nWe watched phishing hosts keep pulling traffic while carrying 20 or more vendor detections. Delivered by web or email, a campaign in that state dies in days — the browser and the antivirus both act on those verdicts. Inside Steam neither does. The verdicts existed the whole time. Nothing in the client ever asked.\n\nWhat this means for a minor with an antivirus installed\n\nHe ignores no warning and disables nothing. A message arrives inside Steam — a free knife, a vote for a friend's team — and the page opens inside Steam. He never opens a browser, so the browser never protects him. His antivirus is running and may already rate that domain malicious; it is never asked. Every warning that could have stopped him already exists. None of it reaches him. He believes he never left Steam, and he did not.\n\nThe giveaway is not the phisher's invention — free Valve items are how the skin and gambling sites advertise, which is exactly why the message reads as ordinary. Complaints: the enforcement archive. Age and children's data: Section 17.\n\nSources: Steam renders web content through the Chromium Embedded Framework in the steamwebhelper process — see DARKNAVY's technical analysis of 27 June 2024 ↗ and Valve's own Steam Client Beta forum ↗ archived 2025-08-04 ↗. No CEF version is relied on: embedded Chromium is not Chrome and ships none of Chrome's Google services. Safe Browsing without API keys: Chromium design document ↗ archived 2026-08-21 ↗, Chromium API keys ↗ archived 2026-08-30 ↗ (“Many of the Google APIs used by Chrome are specific to Google and not intended for use in derived products”), and the same effect in other unkeyed builds — Homebrew cask #193814 ↗. Test URLs: testsafebrowsing.appspot.com ↗.\n\nTwo different clocks\nThe domain’s age.The observation’s date.\n\nA registry creation date establishes when a domain was registered. A dated OpenID record establishes the return host in that record. The former cannot fill the years before the latter.\n\nThe complete register distinguishes a separate registrable domain, a site’s own subdomain and a direct route. Each row links to its source and DNS result.\n\nInspect the domain register →· Download registry dates ↗· Reproduce the observation ↗\n\nPart A — Technical record · Section 4\nAn endpoint closed. Public tracing lost a key.\nContext & source limits\n\nSteam shipped changes that removed public visibility of item Asset IDs and restricted API inventory access. The effect: tracing a specific item by its original Asset ID became impossible from public data. What follows is what was possible before, what stopped being possible after, and what that costs a victim trying to prove where their property went. The date is 2017 according to CSFloat's engineering account; no Valve changelog has been located. The sequence — roughly a year after the July 2016 gambling statement — is the investigative question, not a finding. The item records themselves remain inside Valve's systems; outside investigators lost access to the original-ID chain, while float, seed and paint identifiers allow only partial matching.\n\nThe rule Valve applies: Steam Support does not restore items that left your account, and the burden of showing what happened is yours. The record: in 2017 Valve closed the endpoint that carried original item IDs. Before it, anyone could follow a stolen skin from the victim's account into a marketplace bot. After it, nobody outside Valve can. The proof the victim is asked for is the proof that was switched off — and it still exists, inside Valve.\n\nThe Pre-Blackout Era\n\nHistorically, every virtual item generated on Steam possessed a globally unique, immutable Asset ID. Third-party OSINT databases could index these IDs. If a user had an item hijacked, investigators could trace the lineage of that specific asset as it moved from the hijacker's intermediate account into the storage accounts of a marketplace or gambling site.\n\nBEFORE: an item could be followed from the victim's account through intermediate accounts and into a marketplace or casino storage bot, by anyone, using public data.\nAfter the change\n\nAccording to CSFloat's engineering account, Valve closed the endpoint in 2017 and original item IDs stopped being available to outside parties. No Valve statement of the reason for the change has been located. In the same period, no published action against the commercial bot accounts that moved items at scale has been located either.\n\nWhatever the reason for it, the change severed the public chain of custody. A victim can no longer reproduce the original-ID chain from public data to show that a specific stolen item was liquidated through a specific marketplace or casino. The item records still exist inside Valve's systems; the public, researchers and law enforcement working from public data cannot reach them.\n\nAFTER: tracing a specific item by its original Asset ID is no longer possible from public data. The original-ID chain of custody for an item moved after 2017 exists only inside Valve's infrastructure; no such record has been produced publicly. Float, seed and paint identifiers allow only partial, probabilistic matching.\nIEconItems_730\nGET/IEconItems_730/GetPlayerItems/v1/\nTraceable Payload (Pre-Patch)\n\"id\": \"14892281934\",\n\"original_id\": \"11829910211\",\nStatus: Victim can track item lineage across bot accounts.\nObfuscated Payload (Post-Patch)\nCurrent\n\"id\": \"HIDDEN_BY_PRIVACY_SETTINGS\",\n\"original_id\": \"NULL\",\nStatus: outside parties can no longer trace item lineage by original Asset ID from public data.\nEffect on evidence: after the change, the public data needed to follow a specific item by its original Asset ID from a victim's account into a marketplace or casino bot was no longer available. The internal records still exist at Valve; a victim, researcher or investigator working from public data cannot reproduce the original-ID chain (float, seed and paint identifiers allow only partial matching).\n\nSource: CSFloat engineering account of the 2017 closure of IEconItems_730/GetPlayerItems — blog.csfloat.com/how-floatdb-tracks-items (archived 2026-09-21) · the payloads shown are an illustration of the field shape, not captured responses · no Valve changelog for the closure has been located.\n\nPart A — Technical record · Section 5\nOne session. More access than the user sees.\nContext & source limits\n\nValve's API-key architecture, as it stood before the 2023 changes, departed from baseline industry standards (OWASP ASVS, NIST SP 800-63B) and is the mechanism described in the automated inventory-theft complaints preserved in the evidence archive (Sections 6–8).\n\nThe rule Valve applied: the account holder created the key, accepted the terms, and bears the loss — that is the answer in the archived refusals. The record: until December 2023 a stolen session cookie alone could register that key. No password. No Steam Guard. No notification to the person whose account it was. The user did not create the key, could not see it, and was told he did. Mobile confirmation was added on 2023-12-04 — about seven years after the 2016 statement and roughly six after the scam panels the archive preserves. Those years were not paid by Valve. They were paid by the accounts emptied in the meantime, a share of them children's.\n\nOWASP ASVS 2.8 / NIST SP 800-63BSEVERITY: CRITICAL\n1. Insufficient Step-up Authentication\n\nSteam allowed the generation of highly privileged, long-lived API keys using only a session cookie. No 2FA (Steam Guard) or step-up authentication challenge was required when setting up or modifying a developer API key, so the Steam Guard mobile confirmation — the only second factor Steam offers — did not protect this step. (A hardware second factor was requested in Valve's own tracker in 2016 and the issue is still open: Appendix D, GH-01.)\n\nStatus: unpatched before 2023. Allowed a script holding a stolen cookie to register a key without any user interaction.\nOWASP A01:2021 / Least PrivilegeSEVERITY: CRITICAL\n2. Lack of Principle of Least Privilege\n\nThe Steam Web API lacked any role-based authorisation scopes. A developer API key issued for \"read-only\" inventory status possessed complete \"write\" permissions — including the ability to manipulate existing trades, initiate new ones, register webhooks and decline valid pending exchanges.\n\nStatus: systemic design defect. One key = full read/write control of the account's inventory and trades.\nOWASP A07:2021 / SessionsSEVERITY: HIGH\n3. Broken Session Management\n\nHijacked web sessions originating from server-hosting IP ranges were reported by users to persist. Standard practice is to terminate sessions on geographic anomalies and on password change; user reports collected in the archive describe sessions that remained active after a password change.\n\nStatus: reported behaviour (user complaints in the archive). Sessions could generate API keys without re-authentication.\nDomain-level blocking was technically feasibleENFORCEMENT FEASIBILITY\n4. Domain-Level Blocking of Auth Hosts Was Technically Feasible\n\nValve already operates a domain list (the Link Filter) and already receives every auth hostname in its own OpenID requests. The two mechanisms are not connected in any way visible from outside: as of 2026-09-22, in 26 pairs the main domain was on the filter while the proxy carrying its login was not.\n\nConnecting them is a small engineering task: read the openid.realm hostname from each incoming request, compare it against a list, and refuse or flag the request. The illustration on the right shows the shape of such a routine. Refusing the auth host — rather than only the public landing page — would interrupt the \"Sign in with Steam\" step that these platforms depend on.\n\nNo public evidence shows that Valve runs such a check. The Steam Community Market's combined fee of about 15% applies to sales completed inside the Market; it is not collected on these platforms' external trades.\n\nblock_auth_hosts.pyILLUSTRATION\n// Read the host Steam already receives — no scanning\ndef on_openid_request(request):\nhost = parse_openid_realm(request)\nif host in blocked_domains:\nrefuse(request)\nNote: pseudocode for illustration only. Both halves already exist at Valve — the auth hostname arrives in the request, and the domain list is the Link Filter. No public record explains why they are not connected.\nSection 5.1 — The standards were not unpublished\nValve builds against these rules every day. It did not build to them here.\n\nSteam ships on the App Store and Google Play, sells through the major card processors, and consumes third-party APIs like any other large platform. Each of those relationships carries a published, dated security requirement that Valve must satisfy to keep operating. Set the dates of those requirements against the dates on which Steam's own Web API acquired the same protections. Nothing below is a private standard, an internal memo or a trade secret: every row is a public document with a publication date.\n\nPublished external security requirements, with their dates, set against the date the Steam Web API acquired the equivalent control\nThe published standard, and the date it took effect\tThe Steam Web API on the same question\nScoped authorisationOAuth 2.0 — RFC 6749, October 2012. Section 3.3 defines scope so a client receives only the access it asks for. It has been the default of every major platform API since.\tGranular scopes arrived on 16 January 2026.Before that a single Steam Web API key carried full read and write over the account's trades regardless of why it was issued. Thirteen years and three months after the specification that defines the control.\nA key is not an authorisationGoogle's own Cloud documentation: A standard API key doesn't authenticate a principal, and for APIs that create or manage resources, don't use authorization keys in production.\tThe Steam Web API key was exactly that.A bearer string, issued to an account, sufficient on its own to read the inventory, cancel a pending trade and send a new one. No principal was authenticated at the point of use.\nMulti-factor authentication on privileged accessPCI DSS 3.2, requirement 8.3 — mandatory from 1 February 2018 for all non-console administrative and all remote access to the cardholder data environment. Apple then required two-factor authentication of every Developer Program account holder from 27 February 2019: developers with the Account Holder role in a developer program will need to enable two-factor authentication to sign in.\tA second factor was required to create an API key from 4 December 2023.Until then a stolen session cookie was enough, with no prompt on the account holder's phone and no notification afterwards. Four years and nine months after Apple made Valve itself use a second factor merely to sign in to a developer portal.\nCredential lifecycle and revocationTwitch requires of every third-party application: Your app must validate the OAuth token when it starts and on an hourly basis thereafter, and states that it audits for applications that do not. Its legacy v5 API was retired outright on 28 February 2022 on a published schedule.\tNo published key-lifecycle record.The 2023 change protected the creation endpoint. No Valve statement located with it addresses keys already registered, and no changelog accompanied the change at all. Whether keys created before it were invalidated cannot be established from public data — which is the question a data subject would need answered to know whether a key created on their account years earlier is still live.\nArchitectural Benchmark // Token Architecture\nGitHub Fine-Grained Scopes vs Valve Steam Web API\n\nValve developers manage open-source software on GitHub daily using granular least-privilege tokens. Compare that with the monolithic key issued to 130M Steam players.\n\nGitHub Fine-Grained Token\nUsed by Valve on GitHub\n\nFine-grained token with scoped isolation and mandatory lifecycle enforcement.\n\nRepository Access:Selected Repos only (1 repo)\nIssue Permissions:Read-only [✓]\nCode & Secrets:No access [✕]\nExpiration:30 Days (Mandatory TTL)\nAudit Logging:IP, User-Agent & Timestamp\nSecurity Posture: Least-privilege token limits damage to a single read-only resource.\n!Valve Steam Web API Key\nIssued to 130M Users\n\nSingle 32-character master string carrying all-or-nothing trade and inventory authority.\n\nAccount Access:FULL ACCOUNT (Monolithic)\nTrade Management:Read, Cancel, Decline [!]\nGranular Scopes:NONE (Arrived 2026, 13y late)\nExpiration:NEVER (Valid indefinitely)\nAudit Logging:NONE (Zero IP history for user)\nVulnerability: Stolen key allows silent interception of all outgoing trade offers.\nThe standard applied in one direction\n\nSuppose a vendor Valve depends on — a cloud provider, a payment processor, a CDN — left a credential endpoint without a second factor, and months later Valve's own corporate data left through a key minted at that endpoint. Would Valve accept that the fault lay with whoever clicked the link? The archived refusals preserved in this dossier answer the mirror-image question for the user: the position taken is that the account holder created the key and bears the loss. The same architecture is described as the vendor's failure in one direction and the user's responsibility in the other. Which it is, is not a technical question, and it is not one this investigation can settle — it is what a court or a supervisory authority decides.\n\nIllustration, not evidence — the standard read back the other way\nA payment processor that let a third-party script mint a full-privilege transaction credential from a browser cookie alone, with no prompt to the account holder.\nAn identity provider that closed the hole its tokens were minted through and published nothing about the tokens already minted.\nA bank that answered a disputed transfer by observing that the credential used was registered on the customer's own account, and closed the ticket.\n\nNone of these is offered as a finding about any named company. They are the same design decisions, moved to a setting where the supervisory response is well documented — which is the comparison a regulator is being asked to make.\n\nWhat the record establishes: the controls absent from the Steam Web API were public, dated and, in several cases, conditions Valve had to satisfy to keep shipping its own products. The interval between each standard and the equivalent Steam change is measurable and is set out above. What it does not establish is why. No Valve statement of reasons for any of these intervals has been located, and none is assumed here; that record exists inside Valve and has not been published.\n\nSources, each a public document: OAuth 2.0 — RFC 6749, October 2012 ↗ · Google Cloud — API keys documentation ↗ · PCI DSS 3.2 requirement 8.3 — PCI SSC resource guide ↗ · Apple — Upcoming Two-Factor Authentication Requirement for Account Holders, 20 February 2019 ↗ archived 2025-05-06 ↗ · Twitch — token validation requirement ↗ and the v5 shutdown notice ↗ archived 2025-01-27 ↗. Steam's own dates are those in the update record in this section; the 2023 and 2026 entries are the ones Valve shipped without a changelog. Retrieved 2026-09-22.\n\nValve's own update record — dated, from public sources\nDate\tValve change\tAnnounced?\tWhat it closed\tLag: mechanism public → fix\tSource\n2026-09-01\tAutomated Suspicious Chat Flagging\tYes\tDangerous links / patterns in group chats\t—\tnews ↗\n2026-01-16\tSteamworks Web API granular scopes\tYes\tLeast-privilege scopes for developer keys\t—\tannouncement ↗\n2025-07-15\tCS2 Trade Protection & reversal window\tYes\tNothing. Not a root-cause security fix. Support-side account recovery access remains untouched. Triggering reversal inflicts an automatic 30-day trade lockout (Skinvault ↗), while cash-trading shock caused a $104M (-25%) 24h market cap plunge (CSMarketCap ↗). In 2026, timers became per-item (Skin.land ↗).\t—\tFAQ ↗\n2025-05-14\tAccount Security Announcement\tYes\tStealer / session-hijack guidance\t—\tannouncement ↗\n2024-10-02\tCS2 'The Armory' 7-day hold\tYes\tHold on trade/market for Armory items\t—\tannouncement ↗\n2024-09-18\tNew-device login trade restriction\tYes\t2–7 day trade lock on new devices\t—\tFAQ ↗\n2024-02-14\tProfile name & avatar change hold\tYes\t2–4 h cooldown on trades after rename\t—\tpost ↗\n2023-12-04\tMobile confirmation for API keys\tNo changelog\tSilent cookie-only key registration\t≈6 years after the 2017-era panels\tdev page ↗\n2023-10-24\tSMS MFA for game build publications\tYes\tSteamworks build publishing\t—\tannouncement ↗\n2023-07-12\tCustom biography content warning\tYes\tPhishing links in bios\t—\tforum ↗\n2023-01-25\tProfile {LINK REMOVED} & cooldown\tYes\tLinks in profile text\t—\tFAQ ↗\n2022-10-24\tLogin overhaul & cookie truncation\tNo changelog\tInfinite stolen sessions\t— (IAuthenticationService token migration)\tnews ↗\n2022-10-12\tMobile App 3.0 QR login\tYes\tSession deauthorisation panel\t—\tnews ↗\n2022-05-10\tTrade-cancellation endpoints removed\tNo changelog\tOffer-swap (cancel & re-send)\t≈5 years after the 2017-era panels\tissue #325 ↗\n2020-05-25\tDota 2 7-day trade lock\tYes\tFast item flipping\t—\tblog ↗\n2018-03-29\tCS:GO 7-day trade lock\tYes\tInstant bot laundering\t≈20 months after the July 2016 statement\tblog ↗ archived 2025-02-26 ↗\nSources: the linked Valve posts, help pages and GitHub issues, as dated. Three decisive fixes shipped with no changelog (2022-05, 2022-10, 2023-12) and were detected by users, not announced by Valve — that asymmetry is part of the enforcement record. Lags are computed only where the dossier's own dating (July 2016 statement; 2017-era scam panels) supplies the start point; \"—\" means no such start point is established here.\nPart A — Technical record · Section 6\nInteractive Exploit & Hijack Simulator\nContext & source limits\n\nA reconstruction of the path from the phishing message to the server-side key registration and the trade swap. Before 2023, a Web API key registered on an account could read its inventory, cancel a pending trade offer and create a new one, and no trade-confirmation screen was shown to the account holder for any of those actions. That is the absence of least privilege (OWASP A01:2021). The timings in this simulation are illustrative and are not live measurements of the current platform.\n\nStep through the reconstructed hijack. Each phase shows what the account holder sees and, beside it, the call Steam receives at the same moment. Every one of those calls is correctly authenticated. Nothing in the sequence needs Steam's authentication to fail — it needs the key it issues to carry no scope (OWASP A01:2021).\n\nWhat the player sees. What changes behind it.WALKTHROUGH SIMULATOR\nStep 5 / 5\n\nThe Exploit Completed. Expecting a mobile prompt for their original trade, the victim approves the replacement trade. This is an integrated forensic walkthrough showing how the absence of Least Privilege (OWASP A01:2021) enables automated, sub-second asset hijacking.\n\n01 / THE CHAT LUREA friend asks to voteVictim receives a message with a link.\n02 / THE LOGINA lookalike portalVictim enters sign-in credentials.\n03 / THE ACCESSSilent Web API creationAttacker registers a developer key.\n04 / THE SWITCHLegitimate trade swappedClone bot duplicates target recipient.\n05 / CONFIRMATIONCounterfeit approvedWrong offer approved on mobile.\nThe same step, seen from the networkReconstruction of the pre-2023 pattern · illustrative call shapes\nVictimApproves the mobile prompt that was expected for the original trade.\nAttackerReceives the items at the clone account.\nSteam seesA transfer confirmed by the account holder on a registered device.\nConfirmation genuine — made by the account holder\nRecipient the clone bot, not the intended counterparty\nThe confirmation is authentic. The offer it confirms is not the one the user initiated.\n\nThe record left behind: a trade the user approved. That is the record Steam Support reads when the complaint arrives, and the reason the archived complaints were closed as user error. The complaints are in the enforcement archive.\n\nPart A — Technical record · Section 7\nThe endpoints behind the sequence.\nContext & source limits\n\nThese are the Steam Web API endpoints that the reported hijack scripts used to intercept trades without passing through the browser-side confirmation steps.\n\nFour documented endpoints do the whole job. None of them is a flaw, none needed exploiting — a valid key calls them and Steam answers. The key is the only thing the attacker had to steal.\n\nIEconService / GetTradeOffers / v1POLLING\n\nUsed to monitor the account's trade offers. Scripts poll this endpoint repeatedly with the compromised API key; it returns the details of newly created, pending or modified trade offers. Polling intervals are not measured here.\n\nThreat vector: Discloses pending trade offer IDs and the recipient's profile details.\nIEconService / CancelTradeOffer / v1INTERACTION\n\nUsed to programmatically invalidate the user's legitimate trade offer. Before 2023 no step-up authentication protected the key, so an automated server could cancel an offer as soon as it was detected, without any prompt to the account holder.\n\nThreat vector: Voids the trade before the account holder completes the mobile confirmation.\nISteamUser / GetPlayerSummaries / v2RECON\n\nQueried to retrieve the profile name, avatar image URL and level of the legitimate trade recipient. This lets the script dress a prepared clone account to match. No timing is measured here.\n\nThreat vector: Supplies the data needed to impersonate the intended recipient.\n/dev/ajaxregisterkeyCREATION\n\nSteam's registration endpoint for keys. Historically, any active browser cookie session (`steamLoginSecure`) could register a key without a Steam Guard confirmation on the mobile device, and without any notification to the account holder.\n\nThreat vector: A persistent credential created by a script, unseen by the account holder.\nPart A — Technical record · Section 8 · GDPR Article 7\nA checked box. Whose action?\nContext & source limits\n\nIn declining reimbursement, Steam Support replies preserved in the archive take the position that the account holder created the API key and, by checking the box, accepted the terms.\n\nThe support response attributes the key to the account holder. The question is whether the record establishes who actually created it.\n\nIn the observed API-key hijack pattern, however, the victim never saw or navigated to the API key creation page. The consent field is submitted by a script executing a headless POST with the stolen session cookie.\n\nUnder GDPR Article 7 and Article 4(11), consent must be a freely given, specific, informed and unambiguous indication of the data subject's wishes. The authors' position is that a terms-acceptance field submitted by a hostile script with a stolen cookie, with no page shown to the account holder, cannot meet that definition. Whether it does is for the supervisory authority.\n\nForensic Payload Analysis: Key Registration\nPOST https://steamcommunity.com/dev/ajaxregisterkey\n// Request Payload (Injected via hijacking script)\n{\n\"agreeToTerms\": \"agreed\", <-- machine-injected, no human interaction\n\"domain\": \"localhost\", ← not validated — any value accepted, including localhost\n\"sessionid\": \"8f0d8ef763ab2140bf89de2a\"\n}\nThe question for the supervisory authority: where the account holder never clicked the consent field, whether the terms-acceptance recorded against the account meets Article 7's requirement of a freely given, specific, informed and unambiguous indication of the data subject's wishes, and whether Steam Support may rely on it to decline a claim.\n\nSource: request shape of key registration as reconstructed from the public endpoint and from hijack reports preserved in the evidence archive (searchable build of 2026-09-17) · the session identifier shown is a placeholder, not a captured value.\n\nForensic Autopsy · The Trade Substitution Vector\nHow Valve Finally Neutralized \"Trade Substitution\" — And Why It Took 7 Years of Workarounds\n\nFor nearly a decade, the \"API Key Trade Substitution\" (or API MitM Scam) was the most lucrative account theft model on Steam, siphoning hundreds of millions of dollars in skins from unsuspecting players. Valve did not eradicate the exploit by fixing the vulnerable API architecture; instead, Valve spent seven years layering four platform-wide friction barriers that crippled community trade liquidity while leaving the root cause unaddressed.\n\n1. The Mimicry Death\nAvatar & Name Cooldown (Feb 2024)\n\nThe exploit required sub-second mimicry: the scam bot intercepted an outgoing trade, scraped the recipient's avatar/name via ISteamUser, and cloned the profile in 200ms. On 14 February 2024, Valve quietly implemented a mandatory 2-to-4 hour trade cooldown (Error 34) immediately following any profile name or avatar change. A bot can no longer clone a recipient on the fly without locking itself out of trading.\n\n2. The Economic Death\n7-Day CS2 Trade Reversal (Jul 2025)\n\nValve introduced unilateral Trade Reversals for Counter-Strike items. Any traded skin is tagged \"Trade Protected\" for seven days. If a victim discovers a substitution, they click \"Reverse Trade\" in Steam Support, and the skin is instantly returned to their inventory while freezing the recipient. Because the 7-day trade lock prevents scammers from moving the item to a cashout site, the theft is rendered unprofitable.\n\n3. The Silent Key Death\nMandatory Mobile Push for API (Dec 2023)\n\nHistorically, a stolen session cookie allowed malicious scripts to execute a headless background POST to /dev/ajaxregisterkey without notifying the victim. On 4 December 2023, Valve mandated an explicit push confirmation on the Steam Mobile App to generate a Web API key, eliminating silent background key provisioning.\n\n4. In-App Mobile Warnings\nAccount Age & Name Banners (2022–2024)\n\nValve revamped the mobile confirmation modal to display the trade partner's Steam account tenure (creation date), Steam level, and an explicit amber warning: \"This user has recently changed their profile name\", breaking the visual illusion for attentive victims.\n\nThe Three Flaws in Valve's Patchwork: Why Scammers Simply Shifted Targets\n1. The Game Exclusion Loophole (Dota 2 & TF2)\n\nTrade Reversals were deployed exclusively for Counter-Strike 2. Dota 2 and Team Fortress 2 items remain completely unprotected due to crafting and socketing complexities. High-tier items worth thousands of dollars (Dragonclaw Hooks, Golden Baby Roshans, Unusual TF2 burning flames) carry zero reversal window. Scammers simply redirected automated API interception onto Dota 2 and TF2 traders, where Steam Support strictly enforces its 2016 \"no item restoration\" policy.\n\n2. The \"Zombie Key\" Reservoir (Zero Expiration)\n\nWhile Valve added mobile push 2FA to generate new keys in December 2023, Valve never revoked, expired, or purged existing legacy API keys. Millions of active accounts that generated keys (or had keys silently created by phishing/malware prior to Dec 2023) still carry active credentials with zero expiration (no TTL) and zero inactivity timeout. Threat actors maintain massive historical databases of these persistent keys, continuing to poll IEconService undisturbed.\n\n3. The Victim Penalty: 30-Day Trading Lockdown\n\nEven in CS2, Valve penalizes the scammed player: clicking \"Reverse Trade\" in Steam Support automatically inflicts a mandatory 30-day trade and Community Market ban on the victim's account. Valve punishes the user with a month-long platform exile as a deterrent against \"frivolous\" reversals, discouraging victims from reversing trades on lower-value liquid items.\n\nThe Core Regulatory Scandal: Seven Years of Workarounds vs. One API Scope\n\nWhy did Valve spend seven years inventing trade holds, account cooldowns, and reversible trade locks—disrupting the entire gaming economy and wiping out $104M in market capitalization—instead of implementing the industry-standard fix?\n\nAs proven by Valve's official Steamworks release on 16 January 2026 (Announcement #493839547938902179 ↗), Valve already built Granular Permission Groups (General, Microtransactions, Economy, Sales Data) and IP Whitelisting for corporate Publisher Keys. Valve had the engineering solution in hand for years. A single user-facing checkbox—\"Prevent this Web API key from accessing IEconService (Trade Management)\" or a home IP whitelist—would have eradicated the trade substitution scam in 2018 with zero economic collateral damage. Valve refused to give regular players the protection it engineered for corporate partners.\n\nPart B — Rules and enforcement record · Section 9\nTheir rulebook. The recorded platforms.\nContext & source limits\n\nThis ledger maps explicit clauses from the Steam Subscriber Agreement (SSA) and Steam Online Conduct (SOC) guidelines directly against active, large-scale commercial entities.\n\nThe rule: no commercial use, no gambling, no bots — and Steam Support quotes those clauses when it refuses to return a victim's items. The record: the same clauses, on their face, cover the commercial platforms in this register, which run on Steam identities, Steam bots and Steam transfers. The clause is enforced against the person who lost the skins and not, on any published record, against the businesses moving them.\n\nIn the archived complaints, Steam Support cites the \"No Commercial Use\" and \"No Automation/Bots\" clauses when declining to restore items to victims of API-key fraud. The same clauses apply on their face to the commercial platforms recorded in this dossier, which authenticate through Steam OpenID and move items through automated Steam accounts. No market-wide revenue figure is estimated here (see the enforcement statistics below). What the record shows is the rule applied to individual accounts in the archived cases and no published per-operator enforcement record for the platforms. That asymmetry is what this section documents.\n\nThe central question / selective enforcementRules → Scale → Accountability\nOne rulebook. Unequal enforcement.\n\nThe register shows commercial services using Steam identities, inventories, bots and transfers as operating infrastructure. The SSA prohibits commercial exploitation and automation without permission. The archived complaints show that rule applied to individual accounts, while the public record does not show an equivalent operator-by-operator account for the platforms documented here. Publish the rule, the evidence and the enforcement decision for each one.\n\n189websites in audit scope\n44separate-domain routes in the live register — 27 with a published evidence file, 17 manually collected. The 189-website browser audit alone resolved 25 of them; the register adds the hand-collected routes.\n12 yr 6 mocsgogem.com blocked in the Link Filter; api.csgem.com registered 2014-03-08 and never blocked — one of 26 such pairs as of 2026-09-22\nNo verified totalmarket-wide revenue estimate excluded\nSteam Online Conduct\n\"…you shall not do, or attempt to do, any of the following on Steam: […] Engage in commercial activity. Examples of such prohibited behavior include: posting advertisements; running contests; gambling; buying or selling Steam accounts; selling content, gift cards, or other items; and begging.\"\n\nstore.steampowered.com/online_conduct ↗ archived 2026-09-21 ↗\n\nSSA § 2.G — Commercial use\n\"…[you may not] exploit the Content and Services or any of its parts for any commercial purpose, except as expressly permitted elsewhere in this Agreement…\"\n\nValve's 2016 notices, as reported, invoked the personal, non-commercial licence. No operator has produced a Valve authorisation on the record. store.steampowered.com/subscriber_agreement ↗ archived 2026-09-18 ↗\n\nSteam Web API Terms of Use\n\"You may not use the Steam Web API or Steam Data in any way that violates the Steam Subscriber Agreement.\"\n\nThird-party skin marketplaces operate through automated accounts consuming the Steam API. The rule text leaves no exception for commercial scale. steamcommunity.com/dev/apiterms ↗ archived 2026-09-21 ↗\n\nSSA § 4.C\nAutomation\n\nScripts, bots and non-human interaction are restricted. The ledger records bot trading, account farms and automated routing at commercial scale.\n\nInspect 153records tagged under this clause ↗\nWhat the record holds under this clause153 tagged platforms\nCase Opening15\nSkin Casino13\nCS2 Market9\nSkin Roulette8\ncsgoempire.com→csgoempirelogin4.comCasino\nrollbit.com→rbsnin.comCrypto Casino\n500.casino→fivezerozero.coLicenced Casino\n\nOf these, 153 are also tagged under SSA § 2.G and 2 are also tagged under SSA § 1.C — the same services fall under more than one clause, which is why the examples repeat.\n\n28 of the 153 were observed authenticating through a separate registrable domain. A tag records a dated observation that brings the platform within the clause on its face; it is not an adjudicated violation, and no Valve authorisation has been produced for any of them.\n\nSSA § 2.G\nCommercial use\n\nCommercial exploitation requires express permission. Compare the documented business models, their scale and any disclosed authorisation or enforcement.\n\nInspect 175records tagged under this clause ↗\nWhat the record holds under this clause175 tagged platforms\nCase Opening15\nSkin Casino13\nCS2 Market9\nSkin Roulette8\ncsgoempire.com→csgoempirelogin4.comCasino\nrollbit.com→rbsnin.comCrypto Casino\n500.casino→fivezerozero.coLicenced Casino\n\nOf these, 153 are also tagged under SSA § 4.C and 24 are also tagged under SSA § 1.C — the same services fall under more than one clause, which is why the examples repeat.\n\n28 of the 175 were observed authenticating through a separate registrable domain. A tag records a dated observation that brings the platform within the clause on its face; it is not an adjudicated violation, and no Valve authorisation has been produced for any of them.\n\nSSA § 3.A\nVPN & location disguise\n\nDisguising residence through IP proxying can lead to termination. Separate-domain auth hosts require a separate analysis: establish what is disguised and which rule applies.\n\nInspect the auth-host evidence ↗\nSteam Help / URL policy\nLink obfuscation\n\nSteam prohibits link shorteners and tools that obscure link destinations. A separate auth domain — rbsnin.com in Rollbit's login flow, auth.dota.trade in CS.MONEY's — raises the comparable question of whether the destination shown to Steam's OpenID verifier identifies the operating site.\n\nValve's URL policy ↗\n\nRule references: Steam Subscriber Agreement, revision 10 September 2026 archived 2026-09-18 ↗ · Steam Web API Terms of Use archived 2026-09-21 ↗ · Steam URL policy (link obfuscation). Counts describe this dossier's records and tags; they are not a count of adjudicated violations.\n\nThe trust deficit\nWho reviews the decision when support closes the case?\n\nThe preserved complaints describe permanent sanctions, unanswered challenges and refusals to restore stolen items. Test those accounts against the actual ticket history, available remedies and account-access logs. A generic phishing explanation cannot establish who initiated a reset or created an API key.\n\nRead the captured complaints ↗Request the underlying records →Moderator relationship graph →\nPart B — Rules and enforcement record · Section 10\nAn automation API. A rule against automation.\nContext & source limits\n\nThe question this section puts is how the two are reconciled: which uses of the API are authorised, by whom, and on what published criteria. No count of authorised commercial API users is estimated here, and none is implied by the absence of a published list — the absence is the finding, not a number behind it. The Steam Support messages quoted above are reproduced by the ArchiSteamFarm project in its own FAQ (verified verbatim 2026-09-22); they are not Valve publications, and the accounts they were sent to are not identified.\n\nThe rule (SSA § 4.C): no scripts, no bots, no non-human systems on Steam. The record: Valve ships a headless REST API whose entire purpose is server-to-server automation, and hands the key to any account. Users are banned for automation; the automation interface is Valve's own product. Which commercial uses are authorised has never been published.\n\nThe \"Game Developer\" Fallacy\nSteamworks SDK (Legitimate)\n\nUsed by legitimate game studios to integrate achievements, matchmaking, and leaderboards into their game clients. Requires complex C++ integration and official partner onboarding.\n\nSteam Web API (The Loophole)\n\nA headless JSON/REST architecture designed for external web servers. In the hijack pattern documented here it is used to read inventories and manipulate peer-to-peer trades from remote servers; its legitimate uses are not catalogued in this dossier.\n\nWho the key is forAn ordinary Steam user has no in-client need for a Web API key; the key page lives under a developer URL and its documented purpose is external, server-side access. The archived hijack complaints describe victims who did not know the page existed until a key had been registered on their account.\nThe Automation Contradiction\n\nSSA § 4.C provides: \"You may not use any form of scripts, bots, macros, or other non-human-controlled systems ('Automation') to interact with Content and Services on Steam in any manner.\" Yet the Web API endpoints (like CancelTradeOffer) require no human UI and no captcha and bypass the Steam client entirely. The API is designed for server-to-server automation; the rule prohibits automation by users; the boundary between the two is not published.\n\nA server-side position in the trade flow\n\nA Web API key lets a third-party server act on the account's trades without the Steam client. In the hijack pattern, that server sits between the account holder and the trade server.\n\n→No trade-confirmation screen is shown for the key's actions.\n→Allows background polling (GetTradeOffers).\n→Cancels and re-issues offers without user interaction.\nValve built the interface, prohibited user automation in its rules, and has published no criteria for which commercial uses are authorised.\nPart B — Rules and enforcement record · Section 11\nTen days demanded. Ten years to account for.\nContext & source limits\n\nOn 20 July 2016 Valve's general counsel gave gambling operators a 10-day deadline. Ten years later (as of the dossier snapshot, 2026-09-21) at least one platform named in press reports of that notice, CSGOFast, is still operational with a separate-domain auth host. The wording is reconstructed below from press reports of 21 July 2016; the reconstruction is not a scan. The enforcement record the notice implied has not been published. The open letter to the Commission is Section 2.\n\nRead the July 2016 notice beside the later observations. The outstanding demand is an operator-by-operator enforcement record.\n\nOne week earlier — 13 July 2016, in public\n\nOn 13 July 2016 archived 2026-09-21 ↗, Valve described how gambling sites used Steam: OpenID for account identification and automated accounts for trading. Valve stated that using those mechanisms to run a gambling business violated its API and user agreements. Both the description of the mechanism and the prohibition are in Valve's own dated statement. On 2026-09-21 the separate-domain auth hosts tested returned no Link Filter block, and Valve has published no per-operator enforcement record.\n\nEXHIBIT A / JUL 2016TYPESET RECONSTRUCTION\nVALVE CORPORATION\n\nBellevue, WA\n\nDATE:July 2016 (reported by press 21 July 2016)\nFROM:Karl Quackenbush, General Counsel\nRE:Cease and desist — commercial use of Steam accounts\nNOTE:Reconstruction of reported text; not a scan\n\n\"We are aware that you are operating one of the gambling sites listed below. You are using Steam accounts to conduct this business. Under the Steam Subscriber Agreement, Steam and Steam services are licensed for personal, non-commercial use only.\"\n\n\"You should immediately cease and desist further use of your Steam accounts for any commercial purposes. If you fail to do this within ten (10) days, Valve will pursue all available remedies including without limitation terminating your accounts.\"\n\nDossier reconstruction · consult the source record\nKarl Quackenbush\nGeneral Counsel, Valve Corp.\nIN THE MARGIN / EDITORIAL\nTen days.Then what?\n\nThe deadline was specific. The public follow-through should be, too.\n\nValve’s published 2016 position ↗\nA note to the deadline +\nSATIRE / NOT VALVE CORRESPONDENCE\n\nDear deadline,\n\nYou were given ten days. Somehow, the calendar was the only thing that kept working.\n\nPlease forward any reply to the public record.\n\nTimelineJuly 2016 – September 2026\nDeadline in the notice:\n10 Days\nJuly 2016\nElapsed since the notice:\n3,715 Days\nFixed count from 20 July 2016 to the dossier snapshot of 21 September 2026, not a live figure\nPublished enforcement record:\nNone\nNo per-operator account of terminations or blocks located\n\n◀ Days 0–10 — the deadline, to scaleDay 3715 — the snapshot ▶\n\n20 Jul 2016Ten-day demand issuedDay 0\n17 Feb 2024DSA obligations applyDay 2,768\n25 Feb 2026NY AG complaint announcedDay 3,507\n21 Sep 2026Dossier snapshotDay 3715\n\nTen years later, CSGOFast — named in press reports of the 2016 notices — is operational: csgofast.com returned a Link Filter block on 2026-09-19 and 2026-09-21, while its auth host steam-login.authtofast.com (registered 2026-06-30) did not.\n\nFull dated record of Valve's security changes: Security Timeline → · The Washington record and the enforcement standard: below\n\nWhat the record shows: the 2016 notice set a 10-day deadline; Valve already operated a domain list (the Link Filter) and received the auth hostnames in its own OpenID requests; no per-operator enforcement record has been published. Community reports describe a 2018 action against a marketplace (SkinJar), but those reports are unverified and are not relied on here.\nCSGOFAST / THE SAVED AUTHENTICATION ROUTE\nFollow the declared return host.\n\nThe saved route record links csgofast.com to steam-login.authtofast.com. The separate hostname is carried in the Steam OpenID request. It gives investigators a concrete address to compare with Valve's filtering and enforcement records.\n\nInspect the CSGOFast route and its source ↗ · Compare saved Steam Link Filter results ↗\n\nPUBLIC RECORD / WASHINGTON · 2016 → 2026\nTwo deadlines. One unanswered enforcement standard.\n20 JUL\nValve gives gambling sites 10 days\n\nIts counsel's demand warned that continued commercial use of Steam accounts could lead to termination.\n\n27 SEP\nWashington presses Valve\n\nThe state's Gambling Commission demanded evidence of steps to stop skin transfers for gambling and set a 14 October response deadline.\n\n17 OCT\nValve rejects the charge\n\nValve answered after the deadline, disputed that it facilitated gambling, said it had disabled associated accounts, and said it did not want to switch off trading and OpenID for everyone. At least one platform named in press reports of the July notices (CSGOFast) was operating a decade later. Both facts can hold only if the operator replaced the disabled accounts; the record that would show this has not been published. The WSGC should ask Valve to reconcile the two.\n\n2026\nThe routes observed in September 2026\n\nThe route register records 44 platforms authenticating through separate-domain auth hosts, including CSGOFast, using the OpenID and trading mechanisms Valve described in 2016. The enforcement record that would show which operators were cut off has not been produced.\n\nTHE COMMISSION'S OWN BRIEFING · 30 JANUARY 2018\nEighteen months after Valve replied, the regulator still called it an intent.\n\nBriefing its own legislature at the HB 2881 public hearing, the Commission described the July 2016 statement in its own words: Valve \"announced its intent to crack down on the use of its platform to facilitate skins gambling.\" The same page records what that announcement did to the industry forecast — \"as a result,\" the projected 2020 skin-gambling market was revised from $19.7 billion to $670 million, a cut of about 97 per cent, on the strength of the announcement alone. The forecast moved. The per-operator enforcement record that would justify it has still not been published.\n\nThe market figures are Narus Advisors / Eilers & Krejcik Gaming estimates reproduced in the Commission's briefing, not Commission findings; the same document puts 2016 skin wagering at about $5 billion, roughly $3 billion of it on casino-style sites. Retrieved 2026-09-22, SHA-256 c507c9025f93da0aadaf395c4d8882f25973211c318ee8e9b6f18a5b3755e050.\n\nValve's public 2016 position and today's observable infrastructure can be put side by side. The question is whether enforcement reached the accounts and routes used by prohibited operators. A ten-day notice is not evidence that the notice was carried out across the operators it named. The 2018 OPSkins action is the one documented intervention against a named operator; set against 189 platforms checked and no published per-operator record, one documented action does not show a pattern of enforcement.\n\nWashington Gambling Commission's 2016 notice ↗ archived 2026-05-20 ↗ · Valve's 17 October 2016 response (document copy) ↗ · WSGC briefing to the legislature, 30 January 2018 (local copy, 4 pp.) ↗ · the same file on wsgc.wa.gov ↗ · retrieval record & hash ↗ · Valve's 2018 OPSkins action ↗ archived 2026-03-07 ↗ · Current route audit ↗\n\nForensic Longitudinal Audit · 2016 Cease & Desist Targets\nThe 10-Day Notice Decade: Forensic Survival Audit of the 23 Named Sites\n\nOn 19–20 July 2016, Valve General Counsel Karl Quackenbush issued formal cease-and-desist notices to 23 skin gambling platforms, ordering them to cease commercial use of Steam accounts within 10 days under threat of account termination and legal action. Over 3,700 days later, an empirical audit reveals the true pattern of enforcement: multiple operators never ceased operations, others ran for up to six years after the deadline, and the multi-billion-dollar ecosystem continued to leverage Valve's OpenID architecture.\n\n5+ LIVE\nDefiantly operational in 2026 (CSGOBig, CSGO500, CSGOFast, etc.)\n6 YEARS\nLongest post-notice run before closure (CSGOatse active through 2022)\n$5.01B\n2016 skin wagering volume (Narus / Eilers & Krejcik)\n200+\nActive skin gambling sites operating at market peak\nThe Surviving Titans · 2024–2026 Financial & Traffic Blueprint\nFrom 10-Day Warnings to Offshore Conglomerates: The Multi-Billion-Dollar Turnover\n\nRather than eliminating skin gambling, Valve's 2016 notices catalyzed an industrial evolution. The surviving operators restructured as offshore corporate entities (Curaçao, Belize, Cyprus), pioneered Peer-to-Peer (P2P) trading to bypass bot bans, and now process over 10 million monthly web visits and billions of dollars in annual wagering handle while continuing to authenticate through Steam:\n\nPlatform / Domain\tJuly 2016 Notice\tEnforcement Outcome & Survival Status\tRecorded Verification / Primary Links\nCSGOBig\ncsgobig.com\t10-Day Notice (Jul 2016)\tSTILL LIVE IN 2026\nTemporarily paused, relaunched; authenticates via letmeinbig.com & csgobiglogin.com\tX: @csgobig ↗ · FB: csgobigofficial ↗\nCSGO500\ncsgo500.com / 500.casino\t10-Day Notice (Jul 2016)\tSTILL LIVE IN 2026\nRebranded into 500 Casino (Curaçao license #8048/JAZ2014-037), multi-million monthly turnover\tLive Platform (500.casino) ↗\nCSGOFast\ncsgofast.com\t10-Day Notice (Jul 2016)\tSTILL LIVE IN 2026\nActively operating roulette, crash, and jackpot via steam-login.authtofast.com\tDossier Auth Audit ↗\nCSGOLounge / Dota2Lounge\ncsgolounge.com / dota2lounge.com\t10-Day Notice (Jul 2016)\tSTILL LIVE IN 2026\nPivoted to esports coin wagering and crypto betting; maintained continuous operation\tLive Platform ↗\nCSGOCasino\ncsgocasino.net / csgocasino.gg\t10-Day Notice (Jul 2016)\tLIVE VIA SUCCESSOR (2026)\nDomain redirected; active successor portal operates under csgocasino.gg\tSuccessor Domain ↗\nCSGOatse\ncsgoatse.com\t10-Day Notice (Jul 2016)\tSURVIVED 6 YEARS (ACTIVE TO 2022)\nContinued full gambling operations for six years following Valve's 10-day ultimatum\tX: @CSGOatsecom (Active to 2022) ↗\nCSGOSweep\ncsgosweep.com\t10-Day Notice (Jul 2016)\tSURVIVED TO DEC 2017\nOperated publicly for 17 months after deadline\tX: CSGOSweep Status Dec 2017 ↗\nCSGOWild\ncsgowild.com\t10-Day Notice (Jul 2016)\tSURVIVED TO DEC 2017\nPromoted by major influencers; ran for 1.5 years post-C&D before crypto migration\tX: @Wild (Active Dec 2017) ↗\nCSGOPot\ncsgopot.com\t10-Day Notice (Jul 2016)\tSURVIVED TO SEPT 2017\nOperated high-stakes jackpot betting 14 months past notice\tX: @csgopot (Active Sep 2017) ↗\nCSGODiamonds\ncsgodiamonds.com\t10-Day Notice (Jul 2016)\tSURVIVED TO MID 2017\nRan through 2017 despite admitted outcome tampering for sponsored streamers\tX: @csgodiamondscom (2017) ↗\nCSGOLotto\ncsgolotto.com\t10-Day Notice (Jul 2016)\tCLOSED JULY 2016\nShut down under public scandal; target of federal FTC consent order\tFTC Consent Order (Docket C-4632) ↗\nCSGODouble\ncsgodouble.com\t10-Day Notice (Jul 2016)\tCLOSED JULY 2016\nShut down voluntarily immediately after C&D publication\tX: @CSGODouble (Closed Jul 2016) ↗\nCSGOMassive\ncsgomassive.com\t10-Day Notice (Jul 2016)\tCLOSED 2016\nCeased public operations in late 2016\tX: @csgo_massive ↗\nCSGOStrong\ncsgostrong.com\t10-Day Notice (Jul 2016)\tCLOSED 2016\nCeased public operations in 2016\tFB: csgostrongfree ↗\nSkins2\nskins2.com\t10-Day Notice (Jul 2016)\tCLOSED 2016\nCeased public operations in 2016\tFB: CSNCOM ↗\n\nPlatform\tMonthly Traffic (Visits)\tEstimated Turnover / Volume\tCorporate Entity & Jurisdiction\tKey Regulatory Actions & Model\nCSGOEmpire\ncsgoempire.com\t2.3M — 9.0M / mo\nAvg 6+ min duration; 80% direct\t$1.5B — $2.5B Annual Handle\n>1,000,000 P2P skin trades/mo; $6.4M active liquid order floor\tMoonrail Limited B.V. (Curaçao #148182)\nPayments: JHOLT LTD (Cyprus); Founder: \"Monarch\" (Ossi Ketola)\tPioneered 0% fee P2P item trading; licensed Curaçao OGL/2024/1183/0869\nCSGORoll\ncsgoroll.com\t2.74M — 3.5M / mo\nAvg 9m 23s duration; 16% bounce rate\t$1.0B — $2.0B Annual Handle\nEst. $100M–$200M annual corporate revenue from house edge\tFeral Holdings Limited\nHeadquartered in Belize City, Belize (Reg #171519)\tBanned by Australian ACMA (May 2023); sponsored tier-1 team G2 Esports with underage players\n500 Casino (CSGO500)\n500.casino / csgo500.com\t220K — 425K / mo\n~105k unique monthly visitors\t$100k / week ($5.2M/yr) in Royales\nHigh-roller wagering requirement: $400 wager per $1 rakeback\tPerfect Storm B.V. (Curaçao #150536)\nCuraçao Gaming Control Board license OGL/2024/1354/0882\tBanned by Swedish Spelinspektionen (Nov 2023) for unlicensed targeting of Swedish players\nCSGOBig\ncsgobig.com\t~169,600 / mo\nAvg duration 19m 12s; US primary\tMulti-Million Annual Volume\nMystery boxes, roulette, and case battles\tOperates via auxiliary proxy routing\nletmeinbig.com (reg 2023) & csgobiglogin.com\tTarget of July 2016 C&D; relaunched with proxy auth architecture\nCSGOFast\ncsgofast.com\t~150K — 250K / mo\nGlobal multi-language audience\tMulti-Million Annual Volume\nHigh-velocity roulette and crash games\tOffshore operational entities\nRoutes Steam auth via steam-login.authtofast.com\tTarget of July 2016 C&D; never discontinued operations; active in 2026\nCSGOPolygon\ncsgopolygon.com / plg.bet\t~300K — 500K / mo\nCIS and Eastern European dominance\tMulti-Million Annual Volume\nCrypto & skin roulette, match betting\tSecond-wave target (Oct 2016)\nPivoted to cryptocurrency with mirror domain plg.bet\tSurvived a full decade; continues skin liquidation via third-party APIs\nThe Second Wave: Why Valve's C&D Targeted 43+ Sites in Total\n\nOn 17 October 2016, Valve's legal counsel formally disclosed to the Washington State Gambling Commission that following the initial 23 notices on July 19, Valve had sent cease-and-desist letters to more than 20 additional skin gambling sites (bringing the official total above 43). This second wave was necessitated because the initial list inexplicably omitted the largest, most notorious gambling hubs in the world:\n\nCSGOJackpot.com: The historic originator of skin jackpots, which handled hundreds of millions in volume before shuttering under threat of federal indictment.\nCSGOShuffle.com: The site at the heart of the July 2016 streaming scandal, where Twitch streamer PhantomL0rd secretly owned 33% of the company and was exposed rigging odds with house funds.\nThe Macro Ecosystem (200+ Operators): According to industry research by Narus Advisors and Eilers & Krejcik Gaming, over 200 distinct skin gambling sites operated in 2016, generating $5.01 Billion in wagering volume from 3.03 million active players. Valve's 43 letters addressed less than 20% of the active market.\nOfficial Government & Regulatory Investigations on Steam Skin Gambling\n\nThe skin gambling phenomenon is documented across multiple formal statutory inquiries, enforcement actions, and government position papers:\n\n1. Washington State Gambling Commission (WSGC) (2016–2018)\n\nIssued formal Cease & Desist demand on 5 Oct 2016; published Legislative Briefing on 30 Jan 2018 documenting that skins are cash equivalents and reporting the $5.0B skin wagering volume.\n\nWSGC Legislative Report PDF (Local Copy) ↗\n2. U.S. Federal Trade Commission (FTC) (Sept 2017, Docket C-4632)\n\nFirst federal regulatory enforcement action involving skin gambling against CSGOLotto owners Trevor Martin and Thomas Cassell for deceptive practices and undisclosed platform control.\n\nFTC Decision & Consent Order ↗\n3. UK Gambling Commission (UKGC) Position Paper & Youth Audits\n\nFormally classified in-game skins as \"money or money's worth\" under Gambling Act 2005. Subsequent surveys found over 11% of children aged 11–16 had bet skins on video games.\n\nUKGC Research Repository ↗\n4. Australian Senate Environment & Communications Inquiry (2018)\n\nFederal Parliamentary report on \"Gaming micro-transactions for chance-based items\", evaluating Valve's loot box mechanics, secondary market cashouts, and regulatory circumvention.\n\nParliament of Australia Inquiry ↗\nThe outstanding demand\n\nPublish the enforcement record: which gambling accounts and bots were disabled, which return hosts were restricted, and which commercial services received permission. A public prohibition and a homepage warning do not establish that the underlying operation was stopped.\n\nPart B — Rules and enforcement record · Section 12\nThe hostname is already in the request.\nContext & source limits\n\nValve already maintains a domain list (the Link Filter) and already receives the auth hostname in every OpenID request. The pseudocode below shows the logical shape of connecting the two. No public evidence shows that Valve does so.\n\nValve already runs a domain blocklist. Valve already receives the login host in every OpenID request. Nothing needs building — the two have to be joined. That is a hostname lookup against a list Valve maintains itself. The pseudocode below is an illustration, not Valve's implementation.\n\nforensic_autoban.py\n# ILLUSTRATIVE PSEUDOCODE — Valve.block_domain() and flag_session_as_mitm() are not real API calls. This demonstrates the logical structure of a mitigation Valve could implement against proxy auth domains, not actual Valve internals.\n# Illustration: the logical shape of a check on the incoming OpenID request\ndef audit_openid_request(request):\nblocked_origins = database.get_blacklisted_platforms()\nproxy_domain = request.params.get('openid.realm')\ntarget_redirect = request.params.get('openid.return_to')\n\n# Logic: If the proxy routes back to a blocked site, ban the proxy.\nfor site in blocked_origins:\nif site in target_redirect:\nValve.block_domain(proxy_domain)\nValve.flag_session_as_mitm(request.session)\n# Result: the login request for that host is refused\n\nObservation:\nWhere a main domain is already on the Link Filter (e.g. howl.gg, blocked 2026-09-18/19/21) and its auth host (howl.uno) appears in the OpenID request from that site's login button, the association is observable to Valve from its own request data. The check is automatable; whether it is run is not.\nDocumented and reported precedents\n\nValve has intervened against a third-party operator at least once on the record: in 2018 it revoked OPSkins' access over the ExpressTrade system (Valve's announcement ↗ archived 2026-03-07 ↗). Community reports from 2018 also describe a marketplace (SkinJar) losing access; those reports are unverified and the mechanism is inferred from the outcome, not from a disclosed process.\n\nWhat the precedent establishes:\n\nValve can cut off a third-party operator's access when it decides to. CSGOFast, named in press reports of the July 2016 notices, was operating on 2026-09-21 with an auth host registered 2026-06-30 that returned no Link Filter block. Why one operator was cut off and others were not is not explained by any published criteria.\n\nWhat a registration date does and does not show\n\nThe registration date of an auth host is a lower bound on when the host could first have appeared in an OpenID request; it does not establish continuous use. sc-auth.net, for example, was registered 2019-04-02 (RDAP) and was observed in Skin.Club's Steam login flow in September 2026; what happened between those two dates is not in the public record.\n\nComparative Audit: API Compliance Standards\nEnforcement Dimension\tGitHub API Rules\tSteam Web API (Valve)\n1. Compliance Neutrality\tPublished, uniform rules. Documented rate limits (e.g. 5,000 calls/hr for authenticated users, 15,000/hr for GitHub Enterprise Cloud organisations) and published acceptable-use policies apply to every account.\tNo published criteria. Individual accounts are terminated under the automation and commercial-use clauses (archived complaints), while no per-operator enforcement record for commercial platforms has been published.\n2. OpenID / Auth Proxy Abuse\tGitHub's published policies allow OAuth apps and tokens to be suspended or revoked for abuse, and its documentation describes automatic revocation of exposed tokens (authors' summary of GitHub documentation).\tSeparate-domain auth hosts observed in Steam OpenID flows (e.g. rbsnin.com, howl.uno, sc-auth.net) returned no Link Filter block on 2026-09-21 while their main domains did.\n3. Monetization of Abuse\tGitHub takes no transaction fee on items moved by third-party automation; its revenue model is subscriptions and marketplace listings.\tValve sells the case keys that produce the items, and the Community Market charges a combined fee of about 15% on sales completed inside the Market. No figure for revenue attributable to third-party platforms is estimated here.\n4. Evasion Loop Lifespans\tSuspended OAuth client IDs stop working platform-wide at suspension; the documentation does not publish a time-to-action figure and none is assumed here.\tSeparate-domain auth hosts with registration dates from 2011 to September 2026 returned no Link Filter block in the checks of 2026-09-19 and 2026-09-21. Registration date is a lower bound on possible use, not proof of continuous use.\nSources: GitHub column — GitHub's published API rate-limit and platform-policy documentation (authors' summary, not quoted) · Steam column — Link Filter checks of 2026-09-19 and 2026-09-21 (linkfilter-recheck-2026-09-21.json), RDAP registry (domain-registration.json) and the archived support complaints (evidence archive).\nPart B — Rules and enforcement record · Section 13\nThe off-Steam price gap\n\nThe item sits in a Steam inventory; the sale happens elsewhere. A Factory New AWP Dragon Lore had 62 live offers on CSFloat; the cheapest asked $10,623.95. Steam's own market cannot display an asking price above approximately $1,800. To sell for the observed higher price, an owner needs an off-Steam buyer or marketplace. The item and its transfer still depend on Steam.\n\nWhat this means — the Community Market listing ceiling\n\nSteam’s own market refuses a listing above roughly $1,800. A seller may ask less, never more. Items whose market price sits above that line therefore cannot be sold at that price on Steam at all — which is the mechanism that moves those sales to third-party venues while the item itself never leaves Valve’s inventory system.\n\nSection 13 — the off-Steam price gap →\n\nContext & source limits\n\nThree different counts appear in this section and they are not interchangeable. 245 is the number of CS2 item-name categories whose cheapest active offer exceeded $1,800 on CSFloat alone, 20 September 2026. 241 is that same set minus the four categories pinned at CSFloat's $100,000 ceiling, which is the panel the $13.63M floor is calculated on. 248 is a different snapshot: categories priced above the cap by two or more of five marketplaces on 23 September 2026. The marketplaces overlap, so counts from different venues must never be added. Every figure here is an asking price, not a completed sale, and none of it is revenue, turnover or profit — for Valve or for anyone else. PriceEmpire's listed values are rounded estimates published by that site, and its Steam card covers items from other Steam games, so the scopes across the comparison are not identical.\n\nOne item. Two price systems.FOLLOW THE RECORD\nStep 3 / 3\n\nAt that ask, the seller needs an off-Steam venue or buyer. The item still depends on Steam's inventory and transfer system.\n\nSTEAMAbout $1,800Published Community Market listing cap\nSAVED CATALOGUE$10,623.95Factory New AWP Dragon Lore floor ask\nTHE DEPENDENCYStill a Steam itemThe inventory and transfer remain on Steam\n01 / ITEMValve game inventoryCS2 or Dota 2 item held in Steam\n02 / CEILINGAbout $1,800 on SteamMaximum price for one Market listing\n03 / OUTSIDE ASK$10,623.95 for Dragon LoreCheapest CSFloat offer in the dated snapshot\n04 / DELIVERYSteam remains in the chainOwnership and item transfer rely on its system\nMARKET ARCHITECTURE · DATED SNAPSHOT, 20 SEPTEMBER 2026\nThe price gap is measurable.\n\nWe counted item-name categories whose cheapest active offer was strictly above $1,800. CSFloat and Skinport are separate snapshots with overlapping CS2 inventories; their counts cannot be added. The outside offers show where higher asking prices are posted, while Steam still controls item ownership and transfer.\n\n245CS2 CATEGORIES · CSFLOAT\n166CS2 CATEGORIES · SKINPORT\n3DOTA 2 CATEGORIES · SKINPORT\n$10,623.95DRAGON LORE FLOOR ASK\n\nDragon Lore: 62 active CSFloat offers in the Factory New category; the displayed floor is an ask, not a confirmed sale. Steam permits listing the item for less, but cannot post the observed higher ask. Valve’s 2016 statement confirms its awareness of gambling operators using OpenID and Steam trade infrastructure. Whether a particular third-party marketplace breaches Valve’s rules must be established separately.\n\nInspect the full register →CSFloat JSON ↗Skinport JSON ↗Valve’s 2016 statement ↗\nDIRECT CSFLOAT API / DATED SNAPSHOT$13.63M\n\nMinimum aggregate asking value in 241 item categories and 3,395 active offers. Calculated as each category's cheapest ask × its offer count. Four categories pinned at CSFloat's $100,000 ceiling are excluded from this conservative panel.\n\nWhat the dollar figure shows\n\nThese offers represent at least $13,631,888.25 in posted asking prices for this limited CSFloat subset. Including the four ceiling-priced categories produces $14,231,888.25. This is a floor on active asks, not completed sales, cash turnover, profit or the entire CS2 market.\n\nRecalculate from the 245-row CSFloat snapshot ↗\nPRICEEMPIRE / LISTED VALUESteam: #15 of 39\nMany venues list more dollar value than Steam.\nUUSkins\n$133.8M\nYouPin898\n$127.5M\nBuff.163\n$104M\nMoon.Market\n$100.3M\nWhite.Market\n$89.6M\nBuff.Market\n$86.7M\nSteam\n$31M\n\nThe six largest displayed values and Steam. PriceEmpire rounds these figures; Steam shows $31M. Fourteen listed venues rank ahead of it by the displayed dollar values.\n\nPRICEEMPIRE / OFFER COUNTSteam: #1 of 39\nSteam still leads in number of offers.\nSteam\n32.2M\nYouPin898\n5.9M\nC5Game\n4.6M\nHaloSkins\n4.4M\nSkinport\n3.8M\n\nSteam shows 32.2M offers. Number of offers and total asking value answer different questions; many low-priced listings can dominate the count.\n\nSource: PriceEmpire's public comparison ↗ archived 2026-09-21 ↗, captured 2026-09-20 19:03 UTC; dated 39-row extraction ↗. Its figures are rounded estimates, and inventory can overlap across sites. Steam's card also describes items from other Steam games, so the scopes are not identical. Listed value measures asking prices, not sales or revenue.\n42\nANOTHER SOURCE / STEAMANALYST\nThe commercial ecosystem is in plain sight.\n\nSteamAnalyst's marketplace directory archived 2026-07-19 ↗ lists 42 third-party CS2 marketplaces alongside Steam, with recent price data for 32 of the 43 entries. PriceEmpire lists 39 marketplaces under its own inclusion criteria. Named businesses, public offers, visible prices: this economy is open to inspection.\n\nTHE CEILING IS THE MECHANISM: THE SALE LEAVES STEAM, THE ITEM DOES NOT.\n\nAcross five marketplaces captured in one licensed snapshot, 248 CS2 item categories are independently priced above Steam's approximately $1,800 listing ceiling by two or more of them — and every single one is absent from Steam. The same snapshot banded the whole catalogue by price: Valve's market carries 95.3% of the item categories below its cap and 1.9% of those above it. The collapse does not track falling demand; it lands exactly on the published rule. Selling at those prices requires an outside buyer or marketplace, while Steam still controls the inventory and the transfer — the business leaves Valve's checkout and the delivery stays on Valve's infrastructure.\n\nSteam Market FAQ ↗archived 2026-09-21 ↗Steam Subscriber Agreement ↗archived 2026-09-21 ↗Five-marketplace atlas dataset ↗Provenance manifest ↗Earlier CSFloat snapshot ↗Skinport snapshot ↗PriceEmpire ↗archived 2026-09-21 ↗SteamAnalyst ↗archived 2026-07-19 ↗Price-gap register ↗Price-ladder atlas ↗\n\nPart C — Legal frameworks\nPart C — Legal frameworks · Section 14 · Personnel access\nWho can reset the safeguards?\nContext & source limits\n\nAccount security also depends on the people who can recover an account, inspect private records or reset its safeguards. The investigation must follow those privileged actions as closely as it follows API abuse.\n\nAccount recovery hands a support agent the power to move an account away from its owner. Valve has confirmed in writing, twice — February 2023 and November 2025 — that this power was used to hand accounts to the wrong people. Thirty-three months apart, through the same channel. Below: what that access is worth, six sourced cases, and the log Valve holds for every one of them and has produced to nobody.\n\nPreserved testimony / 9 May 2025\nA recovery ticket that disabled the account's security, and a reported $10,000 loss\n\nA user in the collected support archive reports that Steam Support reset the password and disabled account protection after another person submitted a recovery ticket. The author says the account had been inactive for years, held items since 2016–2017 and had Steam Guard, a linked phone and stored recovery codes.\n\n\"Steam Support still gave someone else access to my account.\"\n\nFirst-person allegation, preserved in steam_support_tickets_MEGA.json, record 110. Read the complete captured post ↗\n\nThis is not one user's bad luck. The same door — a help request that moves an account to whoever supplies the older data — is the documented way in for every case in the ledger below, and Valve has twice put that in writing.\n\nThe owner cannot win that argument. Recovery asks for the first CD key, the first email, the first card, the first phone number. Those facts are in Valve's database, and support-side access reads them — reported as reaching back fifteen years. A person who has a copy of your file will always produce more of your history than you can. Targets were picked to fit: dormant for years, high-value, and often bought second-hand, so the holder never knew the original key. Afterwards the accounts were deleted outright, breaking the item-history trail the community uses to trace a skin — a deletion an ordinary user cannot perform without the standard waiting period.\n\nLeast privilege / OWASP A01\n\nRecovery privileges should be limited to the task, independently reviewed and logged. Audit who could reset credentials, remove Steam Guard, read billing records or export account data. OWASP access-control guidance ↗ archived 2026-09-20 ↗\n\nBroad support accessAccess-scope risk\nBeyond the inventory.\n\nIf broad support access is abused, private telemetry can become a tool for profiling, targeted phishing and surveillance. Potential victims include ordinary users, military personnel, public figures and their families. This is a threat model; the exact permissions require access-control records.\n\n01 IP history & location\nIP logs can expose network history and approximate location. They do not, by themselves, establish precise physical movements.\n02 Device fingerprinting\nDevice identifiers, where collected and accessible, can connect sessions and accounts.\n03 Activity telemetry\nLogin timestamps and session records can reveal routines, including activity invisible on a public profile.\n04 Communications & contacts\nAccess to retained messages or contact information would increase the scope for profiling and social engineering.\n05 Identity unmasking\nOriginal email, phone and payment records can connect a pseudonymous account to a person.\n06 Data resale & accountability\nExported target lists could support targeted scams. Establish the actor, access location, recipients and transfers; location alone establishes neither access nor legal immunity.\n\nValve describes IP logging, device information, payment records and third-party support providers in its Privacy Policy §§ 3, 5.2 archived 2026-09-21 ↗. The policy authorises third-party support access — the audit trail that would show which contractor accessed which category, when, and under what authorisation has not been disclosed.\n\nSection 14.1 · the register · June 2022 → November 2025 · every figure sourced\nValve admitted the door twice, thirty-three months apart. It never closed.\n\nSix reported cases in which accounts were taken through Steam's own help-request channel, or through the credentials that channel protects. Each amount is the figure the cited source published, and each source is named. Two of the six were made whole. The difference between them and the rest was not what happened — it was who was watching.\n\nValve, in writing — February 2023\"The items in question were removed from your account because they were received from an account that was compromised through a support help request, for which the CS:GO team takes responsibility. We have reversed the trades and removed them from any account which received them.\"Steam Support reply to a recipient of HFB's items, reproduced by Dexerto, 21 February 2023 ↗ archived 2025-08-18 ↗\nValve, in writing again — November 2025 · 33 months later\"A support technician that handled the help request failed to follow our process which resulted in your account restored to someone else. I apologize for this error.\"Steam Support reply to Hawkeye337, quoted in Dexerto, 14 November 2025 ↗\n21 Jun 2022\nHFB — the largest inventory in the game$2,000,000+ · raised to $3,000,000+ in the February 2023 follow-up\n\nSeven Souvenir AWP Dragon Lores and the #1 Blue Gem Karambit, that knife alone valued at about $1.26 million. The account had been dormant three years with the mobile authenticator still active; the email and password were changed anyway, through the support recovery route.\n\nThe money left before the items did. A reported $200,000+ of sale proceeds was already withdrawn through market.csgo.com — a marketplace that settles in cash and crypto. Reversing a trade returns a skin. It does not return the cash somebody already banked.\n\nAnd the fix broke. One buyer moved his Souvenir Dragon Lore into an in-game Storage Unit. Valve's rollback script could not see inside its own container, so it issued the owner a fresh copy and left the hidden one standing — Valve duplicated a $130,000 item while trying to undo a theft. It was caught by matching item IDs and community reporting, and deleted a month later, in July 2022. The buyer was refunded by BUFF, not by Valve. Emergency remediation this brittle is not a control; it is what a platform does when it has no control.\n\nDexerto, 21 Jun 2022 ↗ archived 2022-07-02 ↗ · Kaspersky ↗ · cash-out figure per Esportfire, 22 Jun 2022 ↗ archived 2026-05-15 ↗, attributed there to multiple Twitter sources · duplication and deletion per Esportsbetting, 14 Jul 2022 ↗\n\nRestoredTrades reversed. Items pulled back out of the inventories of people who had paid full price for them.\n14 Aug 2022\nCS.Money — the platform's own bots$6,300,000 · 19,000+ skins · first estimate $1.6M\n\nAttackers took the mobile-authenticator files of the marketplace's trading bots and emptied them, then sent part of the haul to well-known traders to blur the trail. Community researchers mapped 55 attacker accounts within hours and published them.\n\nValve reversed nothing. The reason given was that a third-party site sits outside Steam — the same Steam whose inventory, trade API and account system the theft ran on end to end.\n\nEsportfire, 14 Aug 2022 ↗ archived 2025-11-15 ↗\n\nRefusedNo reversal. Loss stayed with the platform and its users.\nReported\n21 Feb 2023\nQkss — same door, same actor$1,000,000+\n\nReported as taken the same way HFB was, by the same actor, through the same support help request. HFB was made whole eight months earlier. Qkss was not.\n\nOne route. Two answers. Nothing in the published record distinguishes the two cases except the size of the audience.\n\nDexerto, 21 Feb 2023 ↗ archived 2025-08-18 ↗\n\nRefusedNot restored.\nReported\nFeb 2023\nThe insider trade itself — a year of it≈ $320,000 · proceeds over roughly one year, not an inventory valuation\n\nSupport-side access reached account history up to 15 years old — the first CD key, the first email, the first card. That is exactly the evidence the recovery process asks for, which is why the person holding the database always wins the argument against the person holding the account.\n\nBlogger Mzkshow exposed how insider operator \"Steam Help\" and collaborator \"Alexander\" targeted dormant accounts holding over $100k in skins. One stolen M4A4 Howl carrying iBUYPOWER and Titan Katowice 2014 holos sold for $35,000 and ended up with NAVI's Valerii \"b1t\" Vakhovskyi, who had no way of knowing. After Valve intervened, the contractor dismissed its entire Steam support desk.\n\nVKPlay ↗ · Lis-Skins ↗ · Escorenews (RU) ↗ · Dexerto (EN) ↗\n\nNo registerValve has never published how many accounts this touched, or told the people it touched.\nReported\n2 Dec 2024\n\"Matvey\" — after the sackings$13,000\n\nRecovery was granted to someone who supplied account data the owner himself could not match. Two years after the contractor cleared out its Steam support desk, the same route produced the same result.\n\nPreserved post, 2 Dec 2024 ↗ archived 2025-08-05 ↗ · source rows & hashes ↓\n\nRefusedNot restored.\n13 Nov 2025\nHawkeye337 (Mark Spurlock) — and the second admission≈ $300,000–$500,000 · full Katowice 2014 holo collection\n\nThe attacker demanded 1 bitcoin and began scraping the collection onto Negevs to destroy it. Steam Support's written reply is the second admission above: a technician handled the help request, did not follow the process, and gave the account to someone else.\n\nWhat produced the fix was the feed. Hours after the posts tagging Valve went up on X, the account was taken back and every sticker restored. Qkss did not have that audience.\n\nSkin.club ↗ · Dexerto ↗ · Esportfire ↗ archived 2025-12-17 ↗\n\nRestoredReversed within hours of the story trending.\nWhat the ledger says that no single case does.\n\nThe route never closed. The first admission is dated February 2023 and the second November 2025 — thirty-three months apart, with the contractor's mass dismissal, a documented recurrence and a $6.3 million platform breach in between. Counting from the first theft in this ledger, the channel stayed open for three years and five months. Whatever was fixed in 2023, the help request still moved an account to the wrong person in November 2025 — Valve's own sentence.\n\nRestitution tracked attention, not harm. Restored: the biggest inventory in the game, and the collector whose thread trended. Refused: $1,000,000, $6,300,000, $13,000. Valve has never published the rule it applies, because a published rule would have to explain those three.\n\nNobody was told. Not the users whose account histories were read out of the database, not a supervisory authority, not the market that bought the items in good faith and had them clawed back. There is no breach notice, no incident report, no count of affected accounts — and the proceeds left as money, through marketplaces that pay in cash and crypto. A trade reversal cannot follow money out of Steam.\n\nValve holds the support audit trail, the recovery-ticket log and the transaction record for every line above. None of it has been produced. Ask for your own copy →\n\nThe NDA question\nConfidentiality must come with technical accountability.\n\nCompare confidentiality agreements with actual permissions, export controls, reset approvals and access logs. A canned response cannot resolve an allegation that the recovery process itself was abused.\n\nGDPR Articles 28, 32–34\n\nArt. 33 gives a controller 72 hours to notify the supervisory authority of a personal-data breach; Art. 34 requires telling the affected people when the risk to them is high. Valve has confirmed in writing, twice, that its support channel handed accounts to the wrong people — account history, billing records and all. No notification under either article has been published, and no affected user has reported receiving one. Read the regulation ↗ archived 2026-09-20 ↗\n\nInclude support access in your request →\nPart C — Legal frameworks · Section 15 · Commercial scale\nFollow the money. Separate the transactions.\nContext & source limits\n\nThe commercial-use question becomes sharper when the money flows are separated. Third-party item transfers, Valve's primary sales and external cash-outs are different transactions.\n\nThe item is Valve's. The inventory is Valve's. The transfer runs on Valve's servers. Only the payment happens somewhere else — which is the step that decides whether anyone is a money transmitter, and the one step Valve does not operate.\n\nThe revenue mechanism\nWhere the money actually moves.\nThree paths / one item economy\n01 / AccountUser inventory\n\nItems held on Steam\n\n02 / TransferP2P trade\n\nUser ↔ bot or user ↔ user\n\n03 / SettlementExternal platform\n\nSite balance or payment off Steam\n\nCirculationThe economic engine extends beyond a transfer fee\n\nSteam supplies the inventory and transfer infrastructure used by outside markets. The investigation's economic argument is that resale liquidity and repeated demand sustain spending on cases, keys and replacement items, with fees on subsequent Community Market sales. A direct P2P transfer carries no Community Market commission; that accounting fact does not settle the wider benefit. Valve retains control over account access and trading restrictions throughout.\n\n01 / Secondary demandLiquidity & resale value\n\nExternal trading and gambling demand\n\n02 / Primary spendingKeys, cases & capsules\n\nPurchases from Valve where offered\n\n03 / RevenuePrimary-sale income\n\nPlus fees on actual Market sales\n\n5% + 10%Steam + CS2 fee on Community Market sales\n\nThe investigation's economic inference: liquid resale markets can encourage spending on new items. The familiar 15% combines Market fee rates, subject to minimums and rounding; it is not a levy on every external trade.\n\nValve's Community Market fee schedule ↗ archived 2026-09-21 ↗. On 25 February 2026 the New York Attorney General filed an action archived 2026-09-01 ↗ alleging that paid loot boxes are connected to external cash resale and gambling harm — the same connection this dossier documents from the technical-infrastructure side. That complaint is an allegation, not a finding; it is cited here because a state law-enforcement agency has put to Valve a question adjacent to the one this dossier asks: where is the enforcement record that matches the public declarations?\n\n01 / EntryCrypto deposit\n\nExternal service and wallet records\n\n02 / ConversionBalance → skins\n\nItems delivered through Steam trades\n\n03 / ExitExternal fiat sale\n\nSeller, buyer and payout provider\n\nKYC?Identify the control at every handoff\n\nThis is the route to investigate, not a native Steam API cash-conversion service. Document identity checks, custody, transaction IDs and payout recipients at each external operator before asserting a no-KYC cash-out.\n\nUnited States / Bank Secrecy Act\nClassify the activity, then the obligation.\n\nFinCEN assesses money transmission by what a business does. Accepting and transmitting convertible virtual currency can trigger money-services obligations, subject to the applicable definitions and exceptions. Valve's Steam Wallet accepts funds and converts them to in-game items; those items are then liquidated through third-party operators for real currency. The item and its transfer run on Valve's infrastructure; the cash-out does not, and whether any part of that cycle meets the money-transmission definitions is a classification question for FinCEN, not a conclusion drawn here.\n\nFinCEN FIN-2019-G001, §§ 1–2, 5.1 ↗ archived 2025-07-11 ↗\n\nEuropean Union / money laundering\nTrace proceeds, knowledge and assistance.\n\nDirective (EU) 2018/1673 covers intentional laundering and participation involving criminal proceeds. The investigative question is what Valve knew about the operators using its trading and OpenID infrastructure after 13 July 2016, when it publicly described that use, and what it did about them. Valve has published no per-operator enforcement record; that record, not this dossier, would answer the question.\n\nEU criminal-law framework ↗\n\nAMLD6 terminology: the criminal-law directive above is distinct from Directive (EU) 2024/1640, also called AMLD6. The latter has a general transposition deadline of 10 July 2027, with specified exceptions. Article 78 ↗ archived 2026-08-30 ↗\n\nPart C — Legal frameworks · Section 16 · Notice, response, responsibility\nThe Digital Services Act: put knowledge on the record\nContext & source limits\n\nTwo elements of an Article 16 notice sit with the submitter rather than with this dossier: the submitter's own details and a statement of good faith that the information is accurate. Everything else the Article requires — the substantiated explanation and the exact electronic location — is set out in Section 3 and in the route register, with saved responses and hashes, so that any party can lodge it. Two further limits on the law itself: losing the hosting exemption does not by itself establish liability under any other law, and the 6% in Article 52(3) is a statutory ceiling, not an assessed penalty against Valve.\n\nUnder the DSA a hosting provider keeps its liability shield only until it has specific knowledge and fails to act. This dossier is that notice. It names the hosts, the dates, the saved responses and the hashes. From publication the question is no longer whether Valve knew — it is what Valve did next.\n\n01July 2016 / the dossier exhibit\nA ten-day demand.\n\nThe notice reconstructed above is the historical starting point for the investigation's enforcement comparison.\n\n0217 February 2024 / general application\nThe DSA time window.\n\nSeparate historical conduct from conduct during the period when the relevant DSA obligations apply.\n\n03Ten years / original dossier snapshot\nDuration needs a notice trail.\n\nThe elapsed time since July 2016 (see Section 11) is a dossier metric. It is not ten years of established DSA violations. Link each notice to a specific item, applicable law, delivery evidence and response.\n\nArticle 52(3) / statutory ceiling6%\nof annual worldwide turnover\n\nMaximum fine for a breach of DSA obligations, using the provider's preceding financial year. This is a legal ceiling, not an assessed penalty against Valve.\n\nArticles 6, 8 & 16 / the legal test\n\nFor relevant hosting services, specific knowledge and failure to act expeditiously can remove the hosting exemption. A sufficiently precise notice can establish knowledge of the particular content. The DSA imposes no general monitoring duty; loss of the exemption does not itself establish liability under another law.\n\nDSA: Articles 6, 8, 16, 52, 53, 93 and recital 17 ↗ archived 2026-09-20 ↗\n\nReview preserved complaints ↗Build the account timeline →Full legal & economic analysis →\nPart C — Legal frameworks · Section 17 · Identity, age, commercial access\nMinors: a Steam login is not an age check\nContext & source limits\n\nNo minor's data appears anywhere in this dossier and none was collected: the authors did not register on, deposit at, or complete a login to any platform named. Anyone building on this section should keep evidence involving a child private and redact identifying details from public exhibits. COPPA is cited here as a children's privacy law with its own scope conditions — audience, actual knowledge, personal data collected — and not as a general gambling-age rule; the 2026 New York complaint is an allegation by a state authority, not a finding.\n\n\"Sign in with Steam\" proves an account exists. It proves nothing about age — and on these sites it is the only gate between a child and a deposit. Read it with Section 3.1: inside the Steam client the warning a browser would show never fires, so the child never sees one.\n\nWhat Steam OpenID providesAccount identity\n\nA verified SteamID used to log in or link an account.\n\n≠\nWhat the operator must establishEligibility to participate\n\nAge, jurisdiction and any required identity checks.\n\nTechnical basis: Steamworks OpenID documentation ↗ archived 2026-09-21 ↗. The documented identity assertion is not a certification that the user may legally gamble.\n\nCOPPA / children under 13\nIdentify the operator and the data.\n\nCOPPA applies to covered child-directed services and services with actual knowledge that they collect personal information from children under 13. It is a children's privacy law, not a universal gambling-age rule. Establish the audience, personal data collected, knowledge and parental-consent process.\n\nFTC: COPPA requirements ↗ archived 2026-09-21 ↗\n\nThe evidence to preserve\nRecord the journey from login to deposit.\n\nPreserve the site's age gate, registration wording, eligibility terms, payment flow and complaint history. Assess each operator separately. Keep any evidence involving a child private and redact identifying details from public exhibits.\n\nA related public enforcement record is the 2026 New York complaint announcement archived 2026-09-01 ↗, which alleges harm to young users from paid loot boxes. It is not a COPPA finding.\n\nPart C — Legal frameworks · Section 18 · GDPR Article 15 request\nThe request. The reply. The missing comparison.\n\nHe asked for four things, one of them the log that would name whoever put an API key on his account. Three days later the ticket was closed with a link to a page that holds none of them — and the sentence used to close it is contradicted by Valve's own lawyers.\n\nWhose account this is · Provenance & Limits\n\nThese screenshots are not PhishDestroy's. They come from an ordinary Steam account holder — one respondent to a short survey run by this project, who filed the request himself and supplied the captures. The account is his, the ticket is his, and the correspondence is between him and Steam Support. This project did not submit the request, holds no account on the platform, and is not a party to this ticket.\n\nOn 16 September 2026 he filed a GDPR/CCPA Article 15 subject access request asking specifically for API-key registration logs, login history with IPs, device authorisation history and trade history. On 17 September agent \"Logen\" referred him to the self-service Account Data page. On 18 September he stated that the requested categories were not on that page and asked for escalation to the Privacy Team or DPO. On 19 September agent \"Kal\" closed the ticket with the same referral. Both screenshots are preserved below (requester e-mail redacted; SHA-256 in steam_tos_assets/screenshot-manifest.json).\n\nHe is a fitting requester for an ordinary reason: his account carries a Steam Web API key he did not create, registered to localhost. When it was created is not known — not to him, and not from anything Valve has made available to him, because the single record that would date it is the API-key registration log, which is exactly the category the closure withheld. The key is not new: it predates his awareness of it by an interval he cannot measure, for the same reason.\n\nOther account holders are filing the same request. Any reply that arrives will be added here on the same terms as these two — ticket number, capture date, SHA-256, requester redacted — whether it supplies the categories or refuses them.\n\nThis project takes no position on why the ticket was closed. No reason was stated in it, and none is inferred here.\n\nThe request. The response. The comparison.FOLLOW THE RECORD\nStep 3 / 3\n\nHe asked for four named categories. The Account Data page he was referred to is Valve's own self-service export, and this project cannot enumerate its contents for someone else's account — so no full category-by-category comparison is published here. What is on the record is his statement of 18 September that the categories were not there, and the closure of 19 September that repeated the referral without addressing them.\n\nTHE REQUESTSpecific categoriesAPI-key, login, device and trade records\nTHE RESPONSEAccount Data referenceInspect the support exchange\nTHE TESTWhat was supplied?Compare each requested category\nScreen 1/2 — Request (16 Sep) and first reply, agent \"Logen\" (17 Sep)\nGDPR ticket HT-2YBP-F7JP-D4VB — request and first response\nSource: help.steampowered.com, ticket HT-2YBP-F7JP-D4VB · captured 16–17 Sep 2026 · requester e-mail redacted 2026-09-21 · File: gdpr-ticket-1.png · SHA-256 da940c731ab9869d226e9d06ccc8a1b393738766b7b0c445a56662623e025a66 (screenshot-manifest.json).\nScreen 2/2 — Escalation request (18 Sep) and closure, agent \"Kal\" (19 Sep)\nGDPR ticket HT-2YBP-F7JP-D4VB — escalation request and closure\nSource: help.steampowered.com, ticket HT-2YBP-F7JP-D4VB · captured 18–19 Sep 2026 · File: gdpr-ticket-2.png · SHA-256 44844ea7b251f7fd7d79f87ee1578a846606a97b9659d3a53b322120c422219b (screenshot-manifest.json).\nClosing response, 19 Sep (verbatim):\n\"The data Steam retains can already be found in your Account Data page. As there's no further information Steam Support can offer, this request will be closed.\"\nNo data supplied · no legal basis for refusal stated · no escalation outcome shown\nThat sentence is false, and Valve's own lawyers prove it. Counsel's letter of 1 October 2025, paragraph 1.9, describes device-level correlation linking one device to dozens of accounts (Appendix A). The same response carried 830 pages of retained records (Appendix B). None of it is on the Account Data page.\nWhy this account asked for the API-key log\n\nHe did not pick those four categories at random. The localhost key on his account is the mark of a script, not of a person typing a real domain into the developer page (Section 5, Section 6). The one record that shows who created it and from where is the API-key registration log. That was the first thing he asked for. That is what the closure withheld.\n\nSource: the account holder, during this project's survey. The ticket screenshots above are hashed; the key page is not published.\n\nAssessment · PhishDestroy\n\nClosing a ticket with the question still open is not an accident here. It is the normal outcome. We hold 16,319 preserved complaint and support records and 354 de-duplicated support exchanges drawn from them. This ticket is one dated, fully captured example of the shape they take.\n\nSupport Ticket — PreservedHT-2YBP-F7JP-D4VB\nRequest typeGDPR Article 15 DSAR\nTicket statusCLOSED 19 SEP 2026 — NO DATA SUPPLIED\nAgents in the exchange\"Logen\" (17 Sep), \"Kal\" (19 Sep)\nFiled16 Sep 2026\nData requestedWho registered the Web API key linked to this account, and from which IP / device / timestamp\nLegal basis citedGDPR Art. 15 — right of access to personal data\nThe legal frame:Article 12(3) gives the controller one month from receipt (extendable with reasons). That period had not expired at publication, and this dossier does not assert a deadline breach. The objection is to the substance: the closing response links to a self-service page but does not show that the four named data categories were produced, and if the controller declines to act, Article 12(4) requires it to state the reasons and the complaint routes. Neither appears in the closing response.\nWhy this specific data matters\n\nThe Web API key event log is the record that shows whether a third party registered a key using a stolen session cookie — the mechanism described in the inventory-theft complaints preserved in this dossier's archive. Disclosing who registered an API key, from which IP, and at what timestamp, would:\n\nAllow the victim to compare the API creation IP against their own login history\nReveal data-centre IPs linked to known phishing / gambling bot infrastructure\nProduce evidence usable in civil or criminal proceedings against the actor\nShow whether the account holder was notified when the key was created\nWhat the record shows: Valve retains device-level and account-correlation records — its counsel's letter of 1 October 2025 describes them (see Appendix A, Evidence Memorandum — Source 1). In ticket HT-2YBP-F7JP-D4VB the same class of records was requested by the data subject and the ticket was closed with a referral to a self-service page that the data subject reported did not contain them. Whether that refusal is lawful is a question for the supervisory authority; the effect is that the person the data concerns does not get it.\nThe exchange — four messages, three days\n\nTwo Steam Support agents replied under first names shown on the ticket: \"Logen\" on 17 September and \"Kal\" on 19 September. Both referred the requester to the Account Data page. Nothing on the ticket shows whether the request reached Valve's Privacy Team or Data Protection Officer, and the dossier does not assert who the agents are, what their roles are, or how the ticket was routed.\n\n16 SEP\nArt. 15 request filed with four named data categories\n17–18 SEP\nReferral to Account Data; requester asks for DPO escalation\n19 SEP\nTicket closed with the same referral; no data, no stated basis\nWhat Article 15 GDPR explicitly entitles the subject to\nArt.15(1)(a)Processing purposes — why Valve holds the data\nArt.15(1)(b)Categories of data — what Valve holds\nArt.15(1)(c)Recipients or categories of recipients — who received the data (e.g., API key holder)\nArt.15(1)(d)Retention period or criteria for determining it\nArt.15(3)A copy of the personal data undergoing processing — i.e., the API-key log itself\nART.12(3)Response required within one month of receipt; an extension must be communicated within that month. The period had not expired at publication. Art. 12(4): if the controller does not act, it must state why and inform the subject of the complaint routes.\nRegulatory complaint pathway — for any user\n\nAny user who submitted an Article 15 GDPR request to Valve and received no compliant response (or a template refusal without data) may file a complaint with the supervisory authority in their EU/EEA member state. Valve's EU establishment is Valve GmbH in Hamburg, so the lead supervisory authority for cross-border complaints is the Hamburgische Beauftragte für Datenschutz und Informationsfreiheit (HmbBfDI). (Valve's Article 27 representative is also located in Hamburg; a representative's address does not by itself determine the competent authority.) A complaint may also be filed with the authority of the complainant's own member state under Article 77.\n\nHmbBfDI complaint form ↗ GDPR text (Art. 12, 15, 77) ↗ archived 2026-09-20 ↗EDPB guidelines ↗\n\nTicket reference for any complaint: HT-2YBP-F7JP-D4VB — preserved in this dossier as a documented instance.\n\nOne documented instance\nThe records exist; the data subject did not receive them.\n\nValve's counsel described device-level correlation records in a letter of 1 October 2025. On 19 September 2026 an Article 15 request for the same class of records was closed with a referral to a self-service page the requester reported did not contain them, without a stated legal basis. Ticket HT-2YBP-F7JP-D4VB is one documented instance; whether it reflects a wider practice is a question for the supervisory authority, which can ask Valve for its handling records.\n\nGDPR Articles 12, 15, 77 / Supervisory authority\n\nA complaint under Articles 12 and 15 can be lodged directly with the relevant supervisory authority without cost (Article 77). The authority may impose corrective measures including orders to comply with the access request, and fines under Article 83(5)(b) for infringements of data-subject rights. Preserving the original ticket reference and any Valve response (or its absence) strengthens a complaint.\n\nSee the DSAR template →\nPart C — Legal frameworks · Section 19 · Contract law\nThe Subscriber Agreement against the platform's own architecture\nContext & source limits\n\nThe authors are not lawyers and none of this is legal advice. The SSA is quoted from the revision of 10 September 2026; a different revision may read differently, and clause numbering has changed across revisions — check the clause against the version that governed the conduct in question. The Articles 25 and 32 arguments state what the regulation requires, not that a supervisory authority has found a breach. The figures in Argument 1 carry the scope limits set out in Section 13.\n\nThree of the SSA's central provisions sit awkwardly with how the platform is built: the commercial-use prohibition against a Market price ceiling that pushes high-value sales off-platform; the user-liability clause for API keys against a key endpoint that, before 2023, required no second factor; and the enforcement language against a public record that shows no per-operator enforcement. Whether these tensions affect enforceability is a question for a court; this section sets out the facts a court would have before it.\n\nArgument 1 / Market Cap Architecture\nThe Market ceiling and the commercial-use prohibition\n\nThe Steam Community Market has a listing ceiling of about $1,800. Across five marketplaces in a dated snapshot (23 Sep 2026), 248 CS2 item categories are independently priced above that ceiling by two or more of them; such items cannot be sold at those prices on Valve's own platform. Owners who want those prices use third-party markets, which run on Steam accounts and the Steam API — use that the SSA classes as commercial unless expressly permitted.\n\nItems exceed the Market ceiling → third-party markets fill the gap → those markets use Steam accounts and the Steam API → the SSA prohibits commercial use without permission → no register of permissions has been published. The Community Market's combined fee of about 15% applies only to sales completed inside the Market, not to these external trades.\nArgument 2 / API Key Security Architecture\nThe API-key vulnerability as a platform design question rather than user negligence\n\nBefore 2023, Steam's API key creation endpoint accepted a POST with a stolen sessionid and generated a high-privilege credential without e-mail confirmation, a second factor or device verification. The API hijack complaints collected in this investigation follow one pattern: attacker script, stolen session cookie, silent key creation, trade interception (the request payload is shown in Section 8).\n\nGDPR Article 25 (data protection by design) and Article 32 (security of processing) require technical measures appropriate to the risk. Issuing a credential capable of trade interception without a second factor or owner notification is a design question for the controller. Whether the SSA clause placing liability on the user can be relied on against that background is a question for a court and the supervisory authority.\n\nArgument 3 / Real-Time Visibility\nValve receives the auth hostname on every login\n\nThe auth hostname arrives at Valve's OpenID endpoint in plaintext in openid.return_to and openid.realm (the request shape is shown in Section 3). Extracting it is a standard operation. As of 2026-09-22, in 26 pairs the main domain was on the Link Filter while the host carrying its Steam login was not. Valve has published no per-operator enforcement record, so whether any measure other than the Link Filter has been applied to these hosts cannot be established from public data.\n\nWho bears the cost\nThe pattern in the archived complaints\n\nIn the reviewed complaints, Steam Support's response to an API-key hijack claim follows one form: decline restoration, cite the user's responsibility for the account and its API key, close the ticket. No aggregate figure for accounts affected or value lost is estimated in this dossier; no source for such a figure has been located.\n\nThe question is not whether individual users made mistakes. The question is who is responsible for an architecture that, until 2023, allowed a POST request with a stolen cookie to create a high-privilege trading credential with no notification and no second factor.\nThe SSA as a document vs the SSA as a contract\nA court evaluating this record would not read the SSA in isolation.\n\nIt would read it alongside counsel's October 2025 letter describing device-level correlation, the auth-host registration dates, the batch registration timestamps, the API-key request payload, and the ten years between the July 2016 notices and the platforms still operating in September 2026. That is the record Valve would have to address.\n\nSSA against the record / key points\n\"No commercial use\" — the Market ceiling pushes high-value sales to commercial third-party markets\n\"Users liable for API keys\" — no second factor on the key endpoint before 2023\n\"We enforce against violators\" — no per-operator enforcement record published since July 2016\n\"You agreed to terms\" — in the hijack pattern the acceptance is submitted by a script, not the account holder\nConclusion · What the record establishes and what we ask\nThe findings. The records we ask for.\nContext & source limits\n\nEach finding below is tied to a dated public record in the sections above. The requests are addressed to the authorities that can compel the one thing this investigation cannot reach: Valve's own enforcement, access and processing records.\n\nEach request follows a dated finding. The authorities can seek records that this public-source investigation cannot compel.\n\nWhat the public record establishes\n44 live platforms authenticate through a separate registrable domain — 27 with a published per-route evidence file, 17 from manual collection and listed apart. As of 2026-09-22, 26 pairs had the main domain blocked in the Steam Link Filter while the host carrying its login was not — csgogem.com blocked, api.csgem.com registered since March 2014. Steam receives that hostname in openid.realm and openid.return_to on every login. Section 3\nOn 13 July 2016 Valve publicly named the mechanism and prohibited it, and its counsel's notices of 20 July 2016 set a ten-day deadline. No per-operator enforcement record has been published in the ten years since that deadline. Section 11\nThe Steam Web API key endpoint issued a high-privilege, trade-capable credential from a session cookie alone, with no second factor before 2023. Section 5\nA GDPR Article 15 request (ticket HT-2YBP-F7JP-D4VB) was closed after three days with a link to self-service and no data. Section 18\nWhat we ask each authority\nWashington State Gambling Commission\nReopen the 2016 file. Request an operator-by-operator account of which accounts, bots and return hosts were disabled after the ten-day notices, and which operators later regained access. Section 2\nHmbBfDI (Hamburg; Valve GmbH)\nTest whether the Article 15 response met the controller's duty, and require disclosure of the API-key registration and access records relevant to identifying the actor. Section 18\nDSA digital-services coordinators\nPut the auth-host routing on the record as notice, then assess whether Valve's response meets its obligations once knowledge is documented. Section 16\nAny data subject\nUse the Article 15 template to request the same records for your own account; a retained record can test who initiated a reset or created a key. Appendix G\n\nThe single request behind all four is the same: publish the enforcement, access and processing records that only Valve holds. A homepage warning, a ten-day letter and a self-service page are assertions of control. Whether control was exercised is a question the public record cannot answer and a regulator can.\n\nAppendices — primary exhibits and working materials\nAppendix A — Counsel correspondence\nEvidence Memorandum — material provided by Source 1\n\nEvidence base and source status for the counsel correspondence relied on in Sections 1, 18 and 19.\n\nEvidence Base and Source Status — documents provided by Source 1\nThe user whose permanent ban triggered this audit is not the subject of it. Whether that ban was justified is not examined here, and this dossier neither defends nor disputes it. The account is not the point. What matters is the material: Source 1 — the banned account holder, who received the correspondence below from Valve's counsel as the data subject of their own GDPR request — passed on that correspondence and the accompanying case files, together with the right to examine them publicly. The name is withheld; the documents are described by date, producer metadata and hash.\n\nThat correspondence was sent in response to a GDPR/DSAR request. In the course of it, Valve's counsel put a statement on the record, under signature, describing a capability that Steam Support had previously told users was not technically possible. The paragraph quoted below is that statement.\n\nThe authors' further analysis of the produced log extract is withheld from this dossier pending independent review. It is not relied on by any other part of this investigation.\n\nThe admission on the record: persistent device-level telemetry\n\nIn paragraph 1.9 of the letter attributed to Valve's counsel, Valve's attorneys state: \"Between 2019 and 2023, this account was used primarily from a device that was also used to log into dozens of stolen Steam accounts.\"\n\nThe Fact: Valve's counsel here describes device-level correlation across accounts spanning four years. Steam Support has told theft victims that tracking stolen items or linking accounts to devices was not technically possible. Steam Guard device authorisation is publicly documented, so the existence of per-device records is not itself new; what is new is counsel's written confirmation that those records are retained and correlated across accounts over multi-year periods.\n\nWhy this matters: the correlation that can link one device to dozens of hijacked accounts over four years is the same class of record Support said it could not use for victims. Records of that class would be capable of identifying accounts and devices in a theft-and-resale chain. Which records exist, how long they are retained, and on what basis they are withheld from data subjects are the questions for the supervisory authority.\n\nSource: letter of Valve's counsel dated 1 October 2025, paragraph 1.9, and its 830-page PDF appendix · received by Source 1 in response to a GDPR Art. 15 request · SHA-256 of the appendix recorded in disclosure-audit.json · the letter itself is not reproduced; account names and third-party data are omitted.\n\nStatus: open\nSource materials are available through the evidence archive.\nAppendix B — The produced PDF · redaction check\nThe redaction in the produced PDF is cosmetic: the covered text remains extractable\n\nValve's counsel answered a GDPR access request with an 830-page appendix in which the redactions are painted over the text rather than removing it. 902,270 characters sit under the black bars and come straight out with a text-extraction tool — including the third-party identifiers the bars were there to withhold. Only aggregate counts are published here; no covered content is reproduced, and the appendix itself is not published.\n\n1. What the geometry check found\n\nThe GDPR Art. 15 response dated 1 October 2025 was accompanied by an 830-page PDF appendix (Aspose.PDF for .NET producer metadata, created and modified on the same date). The authors ran a page-level geometry check: for each page, opaque near-black rectangles painted after the text layer were located and the extractable characters lying beneath them were counted.\n\nMeasured on the produced file\n902,270\nCharacters still extractable from under the black bars\nCounted, not estimated. This is a count of covered characters — not of victims, re-identifications or incidents.\n830 / 830\nPages affected — every page\n986\nRectangles over extractable text\n1,329\nOpaque black rectangles in total\nThe black bars are drawn over the text layer; they do not remove it. Text under the bars can be extracted with standard PDF tools. Only aggregate counts are published; no covered content is reproduced here.\nForensic Demonstration: Layer Separation\nASPOSE.PDF FOR .NET VECTOR OVERLAY MOCKUP (APPENDIX P. 412)\n\nReport filed against account: [LOGIN: redacted_user_667]\n\nReason submitted by user: [TEXT: \"User reports duplicate items in inventory and abusive trade conduct...\"]\n\nForeground: <path fill=\"#000\" />Flaw: Underlying UTF-8 stream intact\nSource: PDF appendix to the counsel letter of 1 October 2025 (830 pages, Aspose.PDF for .NET producer metadata) · measured by the authors, method and per-page counts in disclosure-audit.json · SHA-256 of the appendix recorded in the same file · the appendix itself is not published.\n2. Why this matters for a data-subject response\n\nValve's counsel sent this file to a data subject in answer to a request for that person's own records. The bars on it are cosmetic: the text underneath was never removed, so the third-party identifiers the bars were applied to withhold went to the recipient along with the file. A redaction that lifts with a text-extraction tool withholds nothing, and it also leaves the recipient unable to establish what was disclosed and what was not.\n\nArticle 15(4) is the reason those bars exist at all: the right to obtain a copy must not adversely affect the rights and freedoms of others. That is the obligation this production did not meet. Whether it is characterised as a personal data breach under Art. 4(12) is for the supervisory authority to determine; the disclosure itself is measurable in the file, and reproducible by anyone holding the same bytes — the SHA-256 is published, the appendix is not.\n\nWhat was under the bars was not account numbers. It was the body of user reports filed against the requester, with their authors attached: Steam logins that, because a login is rarely used only on Steam, identify the person behind them — on the authors' count, over 60% of the users named in the document are fully identifiable — together with the raw, unredacted text of what they wrote. That text includes death wishes and abuse directed at the requester's nationality. Some of the people so identified are minors. The production handed a named list of reporters to the person they had reported, which is the precise harm Art. 15(4) is written to prevent.\n\nThe sequence around the file matters as much as its contents. The request was met first with a demand for further proof of identity, on the ground that the requester's alias email address did not contain his name; the account was permanently banned during the delay that followed. The letter that finally delivered the data, more than six weeks past the Art. 12(3) month, threatened the recipient with criminal prosecution and withheld the remainder of his own data until he explained his account activity to counsel. The disclosure also settles two questions Valve has not answered in public: the records produced show account-linking reaching back to 2019, and internal telemetry of a depth Valve has never described.\n\nScope of this section: the observation here is limited to the mechanics of the redaction, measured on the file as produced. The authors' further analysis of the produced logs is withheld pending independent review and is not relied on elsewhere in this dossier.\n\nEvidence: counsel letter of 1 October 2025 and its PDF appendix (SHA-256 recorded in the audit file); page-level PDF measurements and method ↗. The sequence of the request, the page-8 refusal and the characterisation of the exposed records are set out in full in PhishDestroy's account, “My Dog vs. Elite GDPR Lawyers”, 17 August 2026 ↗ archived 2026-08-21 ↗. Account names and third-party data are omitted here; nothing covered by the bars is reproduced.\n\nPage 8 of the covering letter refuses part of the request, and states the reason in writing: Eine genauere Auskunft ist aufgrund des Schutzes der personenbezogenen Daten anderer Nutzer der Steam-Plattform… nicht möglich. — a more detailed answer is not possible, because the personal data of other Steam users must be protected. The 830-page appendix was in the same package. What the bars covered was not account numbers: it was the reports filed against the requester, their authors named, with the raw unredacted messages attached. The account holder had asked Valve, through its counsel, for his own file; what he could extract from it was other people's. Nothing in this appendix turns on who drew the boxes. What it establishes is that the protection Valve invoked as its ground for withholding is the protection this same production failed, in the same envelope, on the same day.\nSupport and Legal Correspondence Exhibits\n\nSource: https://phishdestroy.io/steam_dossier/index#exhibit-gallery-section\n\nAppendix D — Source collection\nSelected primary records\n\nSix records from the archive — three GitHub issues in Valve's trackers and three Reddit accounts of disputed support outcomes. Each source stays attached to the claim, the saved text and the question it raises.\n\n1 / 6 selected records\nChoose a source record\nGH-01 / GITHUBOpen in saved build\nHardware keys, requested in 2016\n\nValveSoftware / steam-for-linux · #4521 · 2016-06-27\n\nA user asked Valve to support U2F hardware keys as an alternative second factor. The saved issue carries both Feature Request and reviewed labels, with its state recorded as open.\n\nI request U2F usb dongle support in steam as an alternative.\n\nExcerpt from the GitHub issue ↗\nDocumented record\nA dated request for an additional account safeguard, published in Valve's own issue tracker and labelled reviewed.\nAccountability demand\nPublish the product decision, the response date and the protection delivered after review.\nRead saved record →Open GitHub ↗\nIn the dossier: Account safeguards →Archive #484 · build 2026-09-17\nGH-02 / GITHUBOpen in saved build\nCrash reports without an effective opt-out\n\nValveSoftware / steam-for-linux · #6459 · 2019-08-18\n\nThe reporter describes a Steam client from 12 August 2019 on Ubuntu 16. They say disabling the crash-upload destination did not persist after a restart, and include the relevant configuration.\n\nIf I disable the `ServerURL`, it gets overwritten after every reboot.\n\nExcerpt from the GitHub issue ↗ archived 2026-04-19 ↗\nDocumented record\nA specific privacy complaint with a client date, operating system and configuration excerpt. The saved issue is open.\nAccountability demand\nIdentify the investigation, the affected builds and the change that made the opt-out effective.\nRead saved record →Open GitHub ↗archived 2026-04-19 ↗\nIn the dossier: Request the underlying records →Archive #467 · build 2026-09-17\nGH-03 / GITHUBOpen in saved build\nAuth-ticket abuse reported to Valve\n\nValveSoftware / Source-1-Games · #3857 · 2022-02-26\n\nThe author alleges that a server operation retained Steam authentication tickets after players disconnected and used misleading server listings. The post asks Valve to address the behavior.\n\nMaking their servers look packed.\n\nExcerpt from the GitHub issue ↗\nDocumented record\nA public abuse report lodged in Valve's tracker on 26 February 2022. Its saved state is open; the report includes links to screenshots.\nAccountability demand\nProduce the investigation result and the mitigation record for the reported authentication-ticket abuse.\nRead saved record →Open GitHub ↗\nIn the dossier: Dataset scope →Archive #768 · build 2026-09-17\nRD-01 / REDDITAuthor's account\n44 disputed Market purchases\n\nr/DotA2 · author handle withheld · 2022-07-07\n\nThe author reports 44 unauthorized Market purchases on 6 July 2022 and roughly $500+ in losses. They say two-factor authentication was enabled and describe repeated template replies from support.\n\n2nd ticket in and I have still yet to receive a non robotic copy paste template response from Steam.\n\nExcerpt from the Reddit post ↗ archived 2025-03-20 ↗\nDocumented record\nA dated account of disputed purchases, with links to transaction screenshots and a support response. The amounts and events are the author's report.\nAccountability demand\nReconcile the disputed purchases with transaction and session logs. Explain the evidence behind support's decision.\nRead saved record →Open Reddit ↗archived 2025-03-20 ↗\nIn the dossier: Support and enforcement →Archive #4,533 · build 2026-09-17\nRD-02 / REDDITAuthor's account\nA permanent ban and closed appeals\n\nr/ohnePixel · author handle withheld · 2024-12-09\n\nThe author disputes a permanent ban and says support cited suspected account transfer and community reports. They describe closed tickets and plans to request their personal data.\n\nI explained my situation and asked for more details, but they're sticking to their decision and closing my tickets.\n\nExcerpt from the Reddit post ↗\nDocumented record\nA preserved appeal account, including the reasons the author says support supplied and links to four images. The post date comes from the selected support export.\nAccountability demand\nIdentify the evidence supporting the permanent ban and the review available to challenge it. Closing an appeal does not explain the decision.\nRead saved record →Open Reddit ↗\nIn the dossier: Request the underlying records →Archive #4,766 · build 2026-09-17\nRD-03 / REDDITAuthor's account\nA recovery reset and a reported $10,000 loss\n\nr/legaladvice · author handle withheld · 2025-05-09\n\nThe author alleges that support reset credentials and disabled account protections after someone else submitted a recovery ticket. They report a loss of about US$10,000 from an inactive account.\n\nSteam Support reset my password and turned off all my account security.\n\nExcerpt from the Reddit post ↗\nDocumented record\nA preserved allegation about the recovery process overriding account safeguards. The saved post records what the author says support told them.\nAccountability demand\nIdentify who authorised the reset, the ownership evidence they accepted and the access log. Account recovery is part of the security system Valve controls.\nRead saved record →Open Reddit ↗\nIn the dossier: Request the underlying records →Archive #4,592 · build 2026-09-17\n\nSix selected records. GitHub states describe the saved build. Reddit posts preserve the authors' accounts.\n\nDownload the six records ↓\n\nThe searchable build contains 16,319 distinct records: 393 Trustpilot, 5,635 Reddit, 2,395 GitHub, 276 web and 7,620 wiki records. Multiple records can concern the same event. The separate 40,448-row master export has a different scope.\n\nSearch the full archive ↗ · Build manifest ↗ · Dataset scope and counts →\n\nAppendix E — Case study\nArchiSteamFarm and the automation clause\n\nAn open-source card-farming tool whose own FAQ states it runs on millions of accounts, set against the Subscriber Agreement clause (§ 4.C) that prohibits automation. The mechanics — what a farm has to buy from Valve before it can produce anything, why every way of cashing out a card breaches the licence, the enforcement record and who moderates the card economy — are set out in full in Exhibit V ↗.\n\nThe Steam Subscriber Agreement, § 4.C, states:\n\n\"You may not use any form of scripts, bots, macros, or other non-human-controlled systems ('Automation') to interact with Content and Services on Steam in any manner.\" — Steam Subscriber Agreement § 4.C (current) ↗ archived 2026-09-18 ↗\n\nValve enforces this clause. It is very good at it. The FAQ of ArchiSteamFarm (ASF) — an open-source tool its own documentation describes as running on more than a few million Steam accounts since a first release over 11 years ago — reproduces three Steam Support messages permanently banning users who ran bot networks. Valve found the networks, named them and killed them. The relevant question is therefore not whether Valve can detect automation at scale.\n\nThe project's official ArchiSteamFarm FAQ addresses the risk of a ban directly:\n\n\"This is extremely unlikely considering the fact that ASF is being used on more than a few million of Steam accounts, since its first release that happened over 11 years ago — but still a possibility, regardless of actual probability.\"\n\n\"Valve clearly acknowledges 'Steam idlers' existing, as stated here, so if you asked me, I'm pretty sure that if they weren't fine with them, they'd already do something instead of pointing out that they could cause problems VAC-wise. The key word here is Steam idlers, for example ASF, and not game idlers.\"\n\n— ArchiSteamFarm FAQ, JustArchiNET. Source: GitHub wiki ↗ · verified verbatim 2026-09-22\n\nThe same FAQ answers \"Did anybody get banned for it?\" with Yes, and reproduces what Steam Support wrote to three of them:\n\n1,000+ bots · trade banned\n\"It looks like this account was used to manage a network of bot accounts. Botting is a violation of the Steam Subscriber Agreement.\"\n\n170+ bots · permanently banned, 2017 Winter Sale\n\"this account was used to illegally collect collectible cards on Steam, as well as related and not only commercial activities. The account has been permanently blocked and Steam Support can not provide additional support on this issue.\"\n\n120+ bots · permanently banned\n\"This and other accounts were used for flooding our network infrastructure, which is a violation of Steam online conduct.\"\n\n— Steam Support messages reproduced in the ArchiSteamFarm FAQ, section \"Did anybody get banned for it?\". Source ↗ · verified verbatim 2026-09-22\n\nPut the two records side by side. A private user with 1,000 farming bots is identified, told that \"botting is a violation of the Steam Subscriber Agreement\", and permanently removed. The commercial platforms in this dossier run automated Steam accounts as their core business, at far greater scale, and authenticate through Valve's own OpenID on every login — and no per-operator enforcement record has been published for any of them. The clause works. The question is who it is pointed at.\n\nASF is not accused of anything here, and its reading of Valve's position is its own — its author states plainly that \"ASF is not authorized by Valve\". The tool is used here as a measuring instrument: it shows that Valve detects bot networks, names them in writing and bans them permanently. Valve can close the question in one sentence by publishing which commercial automation it authorises, and the per-operator record of what it did about the rest.\n\nWhere card farming touches Valve's revenue\n\nFarmed trading cards are sold on the Steam Community Market, which charges a combined fee of about 15% on each sale completed inside the Market; the account must have spent $5.00 USD on Steam before it can receive a card at all; and card drops require game ownership or in-game purchases. No aggregate revenue figure is estimated here — the operating scale is stated only as the ASF FAQ states it. The FAQ also records Valve distinguishing \"Steam idlers\" (card farming) from \"game idlers\"; see the ASF FAQ ↗. The mechanics are set out in full in Exhibit V — the scale and the commercial-use trap.\n\nSubjectArchiSteamFarm — automated card farming\nStated scaleMillions of accounts (per ASF FAQ — exact active count unverified)\nCounted, not quoted10,880,610 total API entries in ASF's own Steam group (5,360,499 non-limited, as Steam displays) — the FAQ's \"millions\" is not a story, it is a headcount. 88.97% carry no Steam ban of any kind. The full ban census ↗\nDisclosures in the tool's own documentation\nASF logs accounts in headlessly and idles games for card drops without launching the Steam client (per the project documentation).\nThe FAQ reasons that Valve is aware of \"Steam idlers\" and that \"if they weren't fine with them, they'd already do something\".\nNo targeted enforcement reported in over 11 years (per the FAQ); the resulting card sales inside the Community Market carry Steam's combined fee of about 15%.\nThe FAQ states a recommended ceiling of ten accounts per operator and attributes it to Valve: \"This recommendation is based on internal Valve guidelines, as well as our own suggestions.\" No such guideline is published by Valve.\nTechnical ceiling, per the same FAQ: \"you can run up to 100-200 bots with a single IP and a single ASF instance.\"\nFarmed playtime is recorded by Valve — \"it's usually updated every 30 minutes or so\" — and § 4.C lists \"Faking gameplay statistics (e.g., inflated wins or losses, XP, playtime)\" as a prohibited act.\nSources\nOfficial JustArchi ASF FAQ wiki ↗ ArchiSteamFarm repository ↗ archived 2026-09-24 ↗\nThe automation clause is explicit; the ASF FAQ has stated for years that the tool runs on millions of accounts; no targeted enforcement against it has been reported. The gap between the rule and its application is the record; the reason for it is not established here.\nFull exhibitThe card economy: the process, the scale, the licence and who moderates it ↗What a farm has to buy from Valve before it can produce a single card; the two lines of § 4.C that name card farming by its effects; why every way of cashing a card out breaches the licence Valve wrote while Valve charges a fee at the door; the enforcement record including the June 2025 VAC wave and chain-banning by shared phone number; and the Valve employee and community moderators found administering the card-trading and ban-list services around Steam.The ban censusWe didn't ask Valve how big the farm is. We counted it. ↗10,880,610 total accounts (limited and non-limited) read from ArchiSteamFarm's own Steam group, which the software auto-joins by default on first launch unless the user unchecks the group-join setting (capturing both commercial bot farms and regular players who left the default on). 88.97% carry no Steam ban of any kind; of the 11% that do, 99.8% are cosmetic community bans that never stop trading. Cross-checked against SteamRep, 67.77% of listed scammers walk free once anti-cheat bans are set aside. With registration-date, geography and survival breakdowns — the real scale, measured, not narrated.\n\nAppendix F — Working ledger\n\nRules ledger: clauses against recorded platforms\n\nChoose a rule; the register lists the recorded platforms tagged under it, with their main domain, declared auth host and saved Link Filter result. A blocked website, another domain for sign-in: follow the rule through to the route that remains.\n\n175records linked\nto this rule\n174 primary domains0 C&D mentions\nRULE EXCERPT / SSA § 2.G\nCommercial Use & Account Charging\n“…exploit the Content and Services or any of its parts for any commercial purpose, except as expressly permitted elsewhere in this Agreement (including any Subscription Terms or Rules of Use).”\nFOLLOW THE RECORDS\nPlatform register 175\nScale figures are source estimates\n\n175 of 175 records\n\nService / parent group\tMain domain / registry\tObserved auth domain / age\tScale / recorded response\n\nCasino\n\tcsgoempire.com\n11.3 yearsRegistered 2015-06-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgoempirelogin4.com\n6.2 yearsRegistered 2020-07-20\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustreaper.com\n23.2 yearsRegistered 2003-06-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustreaper.com\n23.2 yearsRegistered 2003-06-24\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustly.com\n12.4 yearsRegistered 2014-05-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustly.com\n12.4 yearsRegistered 2014-05-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette Casino\n\tcsgofast.com\n11.5 yearsRegistered 2015-03-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsteam-login.authtofast.com\n83 daysRegistered 2026-06-30\nRDAP ↗ · authtofast.com (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tduelbits.com\n6.6 yearsRegistered 2020-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nswitchflips.com\n6.4 yearsRegistered 2020-04-21\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opener\n\tfarmskins.com\n10.5 yearsRegistered 2016-03-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsteam.kobal.cc\n9.7 yearsRegistered 2017-01-07\nRDAP ↗ · kobal.cc (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgoluck.com\n9.3 yearsRegistered 2017-05-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgoluck.com\n9.3 yearsRegistered 2017-05-18\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tinsane.gg\n7.5 yearsRegistered 2019-04-02\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.insane.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcs2skin.com\n3.5 yearsRegistered 2023-03-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncs2skin.com\n3.5 yearsRegistered 2023-03-06\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tjuice.gg\n7.9 yearsRegistered 2018-10-19\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nletmeinjuice.com\n2.4 yearsRegistered 2024-04-15\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tggdrop.com\n8.6 yearsRegistered 2018-02-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nggauth.com\n3.4 yearsRegistered 2023-05-03\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Casino\n\thowl.gg\n9.5 yearsRegistered 2017-03-16\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhowl.uno\n41 daysRegistered 2026-08-11\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tchicken.gg\n5.7 yearsRegistered 2021-01-11\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nchicken.gg\n5.7 yearsRegistered 2021-01-11\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgocasino.gg\n2.6 yearsRegistered 2024-02-17\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.csgocasino.gg\n2.6 yearsRegistered 2024-02-17\nWHOISFREAKS ↗ · csgocasino.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Casino\n\thunt.gg\n6.9 yearsRegistered 2019-11-04\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.hunt.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Battles\n\tcsbattle.com\n9.8 yearsRegistered 2016-12-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsbattle.com\n9.8 yearsRegistered 2016-12-10\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskinrave.gg\n3.1 yearsRegistered 2023-08-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinrave.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsdouble.gg\n261 daysRegistered 2026-01-03\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsdouble.gg\n261 daysRegistered 2026-01-03\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustchance.com\n8.0 yearsRegistered 2018-10-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhgfuihd.com\n7.6 yearsRegistered 2019-01-27\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Automation\n\tcobaltlab.tech\n3.5 yearsRegistered 2023-03-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncobaltauth.com\n1.7 yearsRegistered 2025-01-07\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\traided.gg\n171 daysRegistered 2026-04-03\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.raided.gg\n171 daysRegistered 2026-04-03\nIP2WHOIS ↗ · raided.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustneo.gg\n1.3 yearsRegistered 2025-06-20\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustneo.gg\n1.3 yearsRegistered 2025-06-20\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tsplits.gg\n3.7 yearsRegistered 2023-01-23\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsplits.gg\n3.7 yearsRegistered 2023-01-23\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Upgrader\n\tupgrader.pro\n1.2 yearsRegistered 2025-07-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nupgauth.space\n38 daysRegistered 2026-08-14\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskin.fans\n8.2 yearsRegistered 2018-07-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skinfans.com\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\thotpizza.one\n1.8 yearsRegistered 2024-12-07\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhotpizza.one\n1.8 yearsRegistered 2024-12-07\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tg4skins.com\n10.1 yearsRegistered 2016-08-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.g4s.to\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2royal.com\n4.1 yearsRegistered 2022-08-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ntf2auth.com\n5.2 yearsRegistered 2021-07-27\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2hunt.com\n8.7 yearsRegistered 2018-01-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrstspcl.com\n6.1 yearsRegistered 2020-08-08\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2.bet/coinflip\n8.4 yearsRegistered 2018-05-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ntf2.bet\n8.4 yearsRegistered 2018-05-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\topenstars.gg\n131 daysRegistered 2026-05-13\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nopenstars.gg\n131 daysRegistered 2026-05-13\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tskins.com\n25.1 yearsRegistered 2001-08-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skins.com\n25.1 yearsRegistered 2001-08-08\nRDAP ↗ · skins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\twhite.market\n9.6 yearsRegistered 2017-03-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwhite.market\n9.6 yearsRegistered 2017-03-01\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tmoon.market\n7.6 yearsRegistered 2019-02-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmoon.market\n7.6 yearsRegistered 2019-02-27\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tcsfloat.com\n5.2 yearsRegistered 2021-07-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgofloat.com\n11.0 yearsRegistered 2015-09-29\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tskin.land\n4.7 yearsRegistered 2022-01-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skin.land\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\thaloskins.com\n2.8 yearsRegistered 2023-12-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhaloskins.com\n2.8 yearsRegistered 2023-12-10\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCorporate Market\n\tbuff.163.com\n29.0 yearsRegistered 1997-09-15\nRDAP ↗ · 163.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\nbuff.163.com\n29.0 yearsRegistered 1997-09-15\nRDAP ↗ · 163.com (parent)\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\tmarket.csgo.com\n26.6 yearsRegistered 2000-02-07\nRDAP ↗ · csgo.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\ndota2.net\n14.9 yearsRegistered 2011-10-29\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRegulated Market\n\tskinport.com\n8.0 yearsRegistered 2018-09-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinport.app\n6.3 yearsRegistered 2020-06-20\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMarketplace/Swap\n\tskinflow.gg\n3.8 yearsRegistered 2022-11-26\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinflow.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tskin.place\n6.0 yearsRegistered 2020-09-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skin.place\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tskinsmonkey.com\n5.7 yearsRegistered 2021-01-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinsmonkey.com\n5.7 yearsRegistered 2021-01-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCorporate Market\n\tskinbaron.de\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinbaron.com\n10.7 yearsRegistered 2015-12-22\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Market\n\trust.tm\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\ndota2.net\n14.9 yearsRegistered 2011-10-29\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tpirateswap.com\n6.0 yearsRegistered 2020-09-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nlogin.pirateswap.com\n6.0 yearsRegistered 2020-09-22\nRDAP ↗ · pirateswap.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Marketplace\n\tmannco.store\n8.6 yearsRegistered 2018-03-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmannco.store\n8.6 yearsRegistered 2018-03-02\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tskinswap.com\n9.9 yearsRegistered 2016-11-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinswap.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\texeskins.com\n2.1 yearsRegistered 2024-08-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nexeskins.com\n2.1 yearsRegistered 2024-08-14\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tbalticskins.com\n153 daysRegistered 2026-04-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nbalticskins.com\n153 daysRegistered 2026-04-21\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tcs.trade\n8.9 yearsRegistered 2017-11-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncs.trade\n8.9 yearsRegistered 2017-11-14\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\trapidskins.com\n4.5 yearsRegistered 2022-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.rapidskins.com\n4.5 yearsRegistered 2022-03-11\nRDAP ↗ · rapidskins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\ttradeit.gg\n9.1 yearsRegistered 2017-08-21\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nconnect-tradeit.com\n4.6 yearsRegistered 2022-02-23\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\t49skins.com\n3.4 yearsRegistered 2023-04-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.49skins.com\n3.4 yearsRegistered 2023-04-19\nRDAP ↗ · 49skins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tskinvault.gg\n3.4 yearsRegistered 2023-05-06\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinvault.gg\n3.4 yearsRegistered 2023-05-06\nIP2WHOIS ↗ · skinvault.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Trading\n\taim.market\n3.3 yearsRegistered 2023-05-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\naim.market\n3.3 yearsRegistered 2023-05-22\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Sell Portal\n\tskinout.gg\n5.6 yearsRegistered 2021-02-27\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skinout.gg\n5.6 yearsRegistered 2021-02-27\nIP2WHOIS ↗ · skinout.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Trading\n\tntskins.com\n230 daysRegistered 2026-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nntskins.com\n230 daysRegistered 2026-02-03\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Portal\n\tgamerpay.gg\n6.0 yearsRegistered 2020-10-02\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ngamerpay.gg\n6.0 yearsRegistered 2020-10-02\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Scrap Swap\n\tscrap.tf\n14.0 yearsRegistered 2012-09-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nscrap.tf\n14.0 yearsRegistered 2012-09-03\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Cashout\n\tmarketplace.tf\n14.0 yearsRegistered 2012-09-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmarketplace.tf\n14.0 yearsRegistered 2012-09-19\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Cashout\n\tskins.cash\n10.5 yearsRegistered 2016-03-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinscash.live\n6.8 yearsRegistered 2019-12-05\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgo.net\n14.2 yearsRegistered 2012-07-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncn2.easylot.net\n10.0 yearsRegistered 2016-09-03\nRDAP ↗ · easylot.net (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCommunity Hub\n\tcybershoke.net\n6.8 yearsRegistered 2019-11-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.cybershoke.net\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMatchmaker Hub\n\tfastcup.net\n14.6 yearsRegistered 2012-02-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.fastcup.net\n14.6 yearsRegistered 2012-02-16\nRDAP ↗ · fastcup.net (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Analytics\n\tleetify.com\n7.6 yearsRegistered 2019-03-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nleetify.com\n7.6 yearsRegistered 2019-03-01\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Analytics\n\tscope.gg\n7.8 yearsRegistered 2018-12-10\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nscope.gg\n7.8 yearsRegistered 2018-12-10\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tools\n\ttradeupspy.com\n6.5 yearsRegistered 2020-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.tradeupspy.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMarketplace\n\tcs.deals\n9.8 yearsRegistered 2016-12-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.cs.deals\n9.8 yearsRegistered 2016-12-03\nRDAP ↗ · cs.deals (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Price DB\n\tpricempire.com\n6.6 yearsRegistered 2020-01-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\npricempire.com\n6.6 yearsRegistered 2020-01-30\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Blackmarket\n\tFSB Market\n7.2 yearsRegistered 2019-07-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nFSB Market\n7.2 yearsRegistered 2019-07-27\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nReady-Account Hub\n\tz2u.com\n26.9 yearsRegistered 1999-11-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwww.z2u.com\n26.9 yearsRegistered 1999-11-10\nRDAP ↗ · z2u.com (parent)\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Gambling\n\tcsgoroll.com\n11.6 yearsRegistered 2015-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwww.csgoroll.com\nRegistry date unavailableRegistry date unavailable\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\trollbit.com\n11.9 yearsRegistered 2014-11-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrbsnin.com\n3 daysRegistered 2026-09-18\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nLicenced Casino\n\t500.casino\n5.9 yearsRegistered 2020-11-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette/Slots\n\tcsgobig.com\n11.4 yearsRegistered 2015-04-12\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcasedrop.com\n14.8 yearsRegistered 2011-12-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\tbanditcamp.com\n12.2 yearsRegistered 2014-06-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tskinbox.com\n18.8 yearsRegistered 2007-12-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\ttastydrop.com\n6.1 yearsRegistered 2020-08-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette Casino\n\tcsgopolygon.gg\n6.5 yearsRegistered 2020-03-28\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tmagicdrop.ru\n10.3 yearsRegistered 2016-05-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nDice Casino\n\tcsdice.com\n3.8 yearsRegistered 2022-11-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUpgrader Casino\n\tskinodds.com\n1.2 yearsRegistered 2025-06-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgowin.com\n12.0 yearsRegistered 2014-09-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrash Casino\n\tcsgorun.net\n7.3 yearsRegistered 2019-06-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\topenskins.com\n3.6 yearsRegistered 2023-02-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Gambling\n\trustbet.com\n7.6 yearsRegistered 2019-02-07\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgomagic.com\n9.4 yearsRegistered 2017-05-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUpgrader/Contract\n\tcsgobounty.com\n11.5 yearsRegistered 2015-03-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tezskins.com\n27.5 yearsRegistered 1999-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\trustcases.com\n7.2 yearsRegistered 2019-06-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgoreaper.com\n11.1 yearsRegistered 2015-08-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgocases.com\n12.3 yearsRegistered 2014-06-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Upgrader\n\tcsgo-skins.com\n11.2 yearsRegistered 2015-07-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgonet.com\n8.8 yearsRegistered 2017-12-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\twtfskins.com\n9.0 yearsRegistered 2017-10-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Casino\n\tflamecases.com\n10.0 yearsRegistered 2016-09-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tgamedom.com\n11.7 yearsRegistered 2015-01-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Battles\n\tskin.club\n9.0 yearsRegistered 2017-09-04\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsc-auth.net\n7.5 yearsRegistered 2019-04-02\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tdaddyskins.com\n9.9 yearsRegistered 2016-10-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Gambling\n\trustix.gg\n1.7 yearsRegistered 2025-01-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Upgrade\n\tskins.club\n4.2 yearsRegistered 2022-07-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgohouse.org\n146 daysRegistered 2026-04-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskinrave.net\n216 daysRegistered 2026-02-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tbloodycase.gg\n19 daysRegistered 2026-09-02\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nClicker/Upgrade\n\tcsgoclicker.com\n8.3 yearsRegistered 2018-05-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustbet.gg\n4.0 yearsRegistered 2022-09-30\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcs-drop.com\n262 daysRegistered 2026-01-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\thellstore.net\n11.7 yearsRegistered 2015-01-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustloot.com\n354 daysRegistered 2025-10-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgo-case.com\n10.3 yearsRegistered 2016-05-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgogem.com\n9.9 yearsRegistered 2016-10-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\trainbet.com\n8.8 yearsRegistered 2017-11-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nservices.rainbet.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustclash.com\n5.4 yearsRegistered 2021-05-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrash Casino\n\t12cs.fail\n181 daysRegistered 2026-03-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\twww.tf2easy.com\n6.3 yearsRegistered 2020-06-02\nRDAP ↗ · tf2easy.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2blaze.com\n7.6 yearsRegistered 2019-01-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tshuffle.com\n30.1 yearsRegistered 1996-07-31\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tbuff.market\n5.9 yearsRegistered 2020-10-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tavan.market\n8.3 yearsRegistered 2018-05-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Engine\n\tcs.money\n11.0 yearsRegistered 2015-09-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.dota.trade\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tuuskins.com\n2.6 yearsRegistered 2024-01-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Market\n\tyoupin898.com\n6.1 yearsRegistered 2020-08-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tc5game.com\n10.5 yearsRegistered 2016-03-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\twaxpeer.com\n7.3 yearsRegistered 2019-05-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwaxpeer.com\n7.3 yearsRegistered 2019-05-20\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBot Trading\n\tcs.money\n11.0 yearsRegistered 2015-09-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.dota.trade\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUS Marketplace\n\tdmarket.com\n30.2 yearsRegistered 1996-07-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nOfficial Market\n\tsteamcommunity.com/market\n20.3 yearsRegistered 2006-05-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNot an external login site2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Platform\n\tlootfarm.com\n11.9 yearsRegistered 2014-10-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Market\n\trustskins.com\n7.6 yearsRegistered 2019-01-31\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tkrakatoa.com\n26.4 yearsRegistered 2000-05-15\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\tshadowpay.com\n10.1 yearsRegistered 2016-08-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nChinese Powerhouse\n\tigxe.cn\n15.0 yearsRegistered 2011-09-06\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAutomated Swap\n\tswap.gg\n9.6 yearsRegistered 2017-01-29\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCash-out Portal\n\tbitskins.com\n11.2 yearsRegistered 2015-07-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Automation\n\ttf2mart.com\n1.1 yearsRegistered 2025-08-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Auctions\n\tskinbid.com\n10.2 yearsRegistered 2016-06-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Rental\n\tlootbear.com\n8.7 yearsRegistered 2018-01-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Valuation\n\tbackpack.tf\n14.4 yearsRegistered 2012-05-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Botnet\n\tstntrading.eu\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Cashout\n\tskinwallet.com\n18.0 yearsRegistered 2008-09-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nDota 2 Market\n\tdota2market.com\n12.2 yearsRegistered 2014-07-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nServer Network\n\txplay.gg\n5.3 yearsRegistered 2021-06-13\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMatchmaking Portal\n\tesportal.com\n26.8 yearsRegistered 1999-12-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nLATAM Hub\n\tgamersclub.com.br\n11.2 yearsRegistered 2015-06-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tools\n\tepidemic.gg\n4.9 yearsRegistered 2021-11-03\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tcs2stash.com\n3.5 yearsRegistered 2023-03-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tcsgoskins.gg\n6.8 yearsRegistered 2019-12-21\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tsteamanalyst.com\n12.6 yearsRegistered 2014-02-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Exchange\n\tsteamcardexchange.net\n13.3 yearsRegistered 2013-05-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tracker\n\tdotabuff.com\n14.2 yearsRegistered 2012-06-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tracker\n\ttracker.gg\n8.9 yearsRegistered 2017-10-12\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Exchange\n\tfunpay.com\n17.0 yearsRegistered 2009-09-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nGrey Market\n\tplayerauctions.com\n26.3 yearsRegistered 2000-06-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Portal\n\teldorado.gg\n8.0 yearsRegistered 2018-09-12\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Key Market\n\tg2a.com\n24.8 yearsRegistered 2001-12-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Key Market\n\tkinguin.net\n16.8 yearsRegistered 2009-12-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nVirtual Services\n\tg2g.com\n31.1 yearsRegistered 1995-08-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Broker\n\tplayerup.com\n19.3 yearsRegistered 2007-05-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfhub.net\n2.7 yearsRegistered 2023-12-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfaccounts.com\n5.3 yearsRegistered 2021-05-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Shop\n\tbuycsgorank.com\n6.2 yearsRegistered 2020-07-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tcsgosmurfkings.com\n9.3 yearsRegistered 2017-06-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfstore.co\n8.6 yearsRegistered 2018-03-03\nWHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlvlup.com\n9.9 yearsRegistered 2016-11-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlevels.com\n10.6 yearsRegistered 2016-02-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tlevelsteam.com\n79 daysRegistered 2026-07-04\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlevelu.com\n6.0 yearsRegistered 2020-09-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\teloking.com\n12.2 yearsRegistered 2014-07-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\tboosteria.org\n11.9 yearsRegistered 2014-10-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tovergear.com\n14.4 yearsRegistered 2012-04-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tblazingboost.com\n14.2 yearsRegistered 2012-06-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\tdota2boost.com\n2.9 yearsRegistered 2023-10-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tbuyboost.com\n22.4 yearsRegistered 2004-04-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\nThe investigation’s argumentSelected rule / analysis & commentary+\nBurden of proof\n\nThe investigation challenges the gap between restrictions on commercial use and the services recorded here. Classify each activity and establish any express permission before calling it a contractual violation. Community Market fees do not apply to every external trade.\n\nWhat a tagged record is, and is not\n\nA record is tagged when the dossier holds a dated observation that brings the platform within the clause on its face. A tag is not an adjudicated violation, and no express Valve permission has been produced on the record for any platform listed here. Where a platform holds an authorisation, publishing it resolves the entry.\n\nSources & methodologyEstimates, definitions & scope+\n\nCounts above refer to the selected rule. Record types group each platform once; full tags appear in the platform details. Search and filters apply within that rule. Registration dates come from the saved RDAP / WHOIS snapshot. Subdomains use the parent domain’s creation date. Age alone does not establish continuous operation or an authentication route. Current auth hostnames come from saved OpenID requests, with a UTC timestamp; unresolved checks do not reuse legacy labels. The observer stops before Steam login and does not test Steam Link Filter status. Download route observations ↗ Download registry results ↗\n\nExplore the source archive ↗\nAppendix G — From a template refusal to the underlying record\nDSAR playbook: request the evidence\n\nUse Article 15 GDPR to request personal data relating to API-key creation, account recovery and support access. A retained record can test who initiated an action and what the platform relied on.\n\n01\nPreserve your timeline.\n\nSave account notices, tickets, trade IDs and dates in UTC. Secure the account and review the recovery options applicable to the game and transaction.\n\nSteam Trade Protection information ↗\n02\nRequest your retained data.\n\nAsk for timestamps, source IPs, key lifecycle events, security confirmations and account-related recovery actions. Include support-access events and recipients where those data concern you.\n\n03\nKeep the delivery record.\n\nUse Valve's privacy contact route. The usual response period is one month; a necessary extension of up to two further months must be explained within that first month.\n\nValve privacy contact route ↗ archived 2026-09-21 ↗\n04\nCompare the response.\n\nReconcile logs with your timeline. Ask for reasons for omissions, then use the supervisory-authority complaint route if necessary. Preserve the response exactly as received.\n\nScope / Article 15\n\nAccess covers retained personal data, including data in logs. It does not guarantee every internal document, reconstructed records or unredacted data about others. Ask for an intelligible copy and the basis for any restriction.\n\nEDPB access guidelines, §§ 2, 4–6 ↗ · GDPR Articles 12, 15, 77 ↗ archived 2026-09-20 ↗\n\nData subject access requestGDPR / Article 15\nAccount security & access records\n\nReplace the bracketed fields before submitting.\n\nTo: Valve Privacy Team\nSubject: Article 15 GDPR request — account security records\n\nAccount / SteamID: [YOUR ACCOUNT IDENTIFIER]\nRelevant period (UTC): [START] to [END]\nRelated support tickets: [TICKET REFERENCES]\n\nI request a copy of the personal data concerning me that you retain for this period, including:\n\n1. API-key registration, confirmation, use and revocation events, with available timestamps, source IP addresses, registered domains, device or user-agent information and non-secret key identifiers.\n\n2. Recorded account-recovery actions, password/email/phone changes, Steam Guard removals or resets, confirmation events and the account-related evidence relied on to authorize those actions.\n\n3. Personal data in support-access and administrative-action logs concerning my account, including available dates, purposes, actions and the support entity involved, subject to applicable rights of others.\n\n4. Account-related records used to determine any sanction, and available records of my complaints, reviews and responses.\n\nPlease also provide the applicable processing purposes, categories, recipients, retention periods or criteria, and available information about sources where data were not obtained from me.\n\nWhere processing relies on my consent, please provide the retained record of the consent relied upon and the wording presented at that time.\n\nPlease provide an intelligible electronic copy with time zones and field definitions. Please do not include active credentials or secret tokens. If any requested data are not held, please say so. For any withheld data, please identify the scope and legal basis of the restriction and provide the remainder.\n\nPlease acknowledge receipt and respond within the applicable Article 12 period, explaining any necessary extension. I also ask you to preserve relevant existing records while this request is handled.\n\nName: [YOUR NAME]\nDate: [DATE]\nWhat a data-centre IP can establish\nA discrepancy is evidence to investigate.\n\nAn API-key request originating from a data-centre network, as in the hosting-provider example raised in this investigation, can be relevant when compared with login records, confirmations and the user's timeline. An IP alone does not identify the actor or automatically defeat every defence. Evidence that a hostile actor supplied the recorded consent could challenge reliance on that consent; other legal bases and liability issues require separate analysis.\n\nSee the preserved ban-and-GDPR complaint →\nAppendix H — Wayback Machine archive analysis · published support statistics\nSupport volume. Published response times.\nContext & source limits\n\nValve publishes daily support statistics at store.steampowered.com/stats/support. Wayback Machine archives preserve historical snapshots of this page from 2018 to 2026. The volume-to-headcount ratio implied by these figures is inconsistent with per-ticket human review at the published response times.\n\nCompare Valve's archived support figures across the saved snapshots. The methodology explains what those figures can and cannot measure.\n\nVolume against published response time (2018 → 2026)\nTwo queues at one support desk, read across 21 archived captures.\n\nValve publishes live support figures at store.steampowered.com/stats/support. Each point below is the lower bound Valve itself printed on that page on the day the Internet Archive captured it — not an estimate of ours. Both series are the same measure in the same unit, so they belong on one axis and can be read against each other directly.\n\nRefund requests — money Valve is holdingAccount security & recovery — the account you have lost\n0 h\n2 h\n4 h\n6 h\n8 h\n10 h\nno captures · 38 months\n2019\n2020\n2021\n2022\n2023\n2024\n2025\n2026\n8 h 44 m\naccount recovery\n52 m\nrefunds\n15 m — one capture only\n49–55 minThe refund lower bound in every capture from February 2018 to August 2026. Across eight and a half years it moves by under six minutes, while daily refund volume moves by a factor of nine.\n2.4 h → 8.7 hThe account-recovery lower bound sits near 2.4 hours in every capture through December 2022 but one. In the three 2026 captures Valve publishes 10.9 h, 5.8 h and 8.7 h.\n×2.8 → ×13How much slower recovery is than refunds, by Valve's own published figures. Steady for five years, then it widens — the queue that got slower is the one where the user, not Valve, is out of pocket.\n\nSource: 21 Wayback Machine captures of store.steampowered.com/stats/support, 2018-02-03 to 2026-08-10; extraction in VALVE_EVIDENCE_PACK/databases/steam_support_stats_history.json. Read the limits with the figures: the chart plots the lower bound of the range Valve prints. The published upper bound is worse on both lines — refunds ranged 1.5 hours to 1.5 days, recovery 7.0 hours to 3.6 days. Two captures were archived in a localised edition of the same Valve page — 2018-11-03 in Czech, 2020-03-25 in French — and are marked (cs) and (fr) in the table; their figures appear here with the unit words translated and the numbers as published, and the verbatim source strings are kept in the extraction file. Every capture published a response time for both queues, and no point on either line is interpolated. The single 15-minute recovery figure of 2020-10-21 is flagged on the chart and left in: it appears in one capture only and no other capture is within an order of magnitude of it. No capture exists between 2022-12-08 and 2026-02-01; that 38-month hole in the record is shaded, and nothing is drawn across it. These figures describe published response times. They do not show what happens inside a ticket, and Valve has published no headcount against which to read them.\n\nOpen every capture as a table\nEvery archived capture, as published\nCapture\tRefunds / day\tRefund response\tRecovery / day\tRecovery response\n2018-02-03\t98,788\t50.12 minutes to 1.52 hours\t25,662\t2.51 hours to 1.80 days\n2018-05-07\t60,494\t53.83 minutes to 1.47 days\t24,226\t2.45 hours to 2.22 days\n2018-08-02\t69,084\t50.27 minutes to 1.59 hours\t28,953\t2.44 hours to 22.17 hours\n2018-11-03 (cs)\t63,410\t49.28 minutes to 1.54 hours\t33,910\t2.42 hours to 1.31 days\n2019-02-01\t76,305\t50.13 minutes to 1.52 hours\t35,164\t2.44 hours to 2.04 days\n2019-05-18\t78,951\t51.03 minutes to 3.12 hours\t27,514\t2.46 hours to 20.39 hours\n2019-09-07\t78,941\t50.65 minutes to 1.66 hours\t28,812\t2.42 hours to 13.59 hours\n2019-12-13\t69,589\t50.77 minutes to 1.55 hours\t25,322\t2.45 hours to 1.13 days\n2020-03-25 (fr)\t139,278\t49.45 minutes to 1.53 hours\t32,302\t2.48 hours to 3.62 days\n2020-06-26\t278,504\t48.98 minutes to 2.29 hours\t20,343\t2.39 hours to 6.99 hours\n2020-10-21\t107,633\t50.80 minutes to 1.54 hours\t20,688\t15.33 minutes to 8.62 hours\n2021-03-20\t158,956\t50.80 minutes to 1.64 hours\t25,760\t2.34 hours to 11.62 hours\n2021-06-26\t547,907\t51.93 minutes to 6.73 hours\t29,728\t2.40 hours to 15.63 hours\n2021-10-10\t170,103\t51.88 minutes to 3.25 hours\t23,989\t2.39 hours to 13.05 hours\n2022-01-31\t354,386\t53.65 minutes to 8.09 hours\t24,391\t2.42 hours to 15.29 hours\n2022-05-09\t172,555\t51.83 minutes to 1.65 hours\t23,289\t2.41 hours to 16.90 hours\n2022-09-05\t153,453\t53.67 minutes to 4.15 hours\t23,594\t2.45 hours to 1.22 days\n2022-12-08\t181,075\t54.83 minutes to 6.67 hours\t27,111\t2.46 hours to 18.89 hours\n2026-02-01\t317,762\t50.30 minutes to 1.52 hours\t47,197\t10.91 hours to 21.30 hours\n2026-05-09\t246,776\t50.12 minutes to 1.52 hours\t35,264\t5.81 hours to 15.60 hours\n2026-08-10\t373,244\t52.05 minutes to 2.07 hours\t45,319\t8.73 hours to 16.52 hours\nKEY OBSERVATION:\nAcross 21 Wayback captures spanning 2018-02-03 to 2026-08-10, daily refund submissions ranged from 60,494 (May 2018) to 547,907 (June 2021) — a 9.1× spread. The 2026 figure is 373,244 (+278% vs the February 2018 capture).\nOver those same nine years the published lower bound for refund response time never left a 49–55 minute band: a total movement of under six minutes while the workload behind it moved by a factor of nine.\nIf a person read each ticket for even 5 seconds, processing 373,244 tickets per day (current) would occupy 22 agents working 24/7 just to open and close them; at peak (547,907, June 2021) that rises to 32.\nIf the published response time reflected per-ticket handling time (~52 min/ticket), the implied concurrent staffing would be on the order of 13,500 agents at current volume and ~20,000 at peak. No sourced figure for Valve's support headcount has been located; none is assumed here.\nWhat follows: the volume-to-headcount ratio is inconsistent with per-ticket human review at the published response times. The figures are consistent with a largely automated first pass; what proportion receives human review is not published.\nWhy this matters for GDPR compliance\n\nGDPR Article 22 prohibits solely automated individual decision-making that produces significant legal effects, without providing the right to human review on request. If Steam Support decisions (ticket closures, account actions, refusal of data requests) are made entirely by automated scripts, every such decision that \"significantly affects\" the user may violate Article 22.\n\nTicket HT-2YBP-F7JP-D4VB (Section 18) was closed after three days with a template referral and no engagement with the legal basis cited. Whether a person reviewed it cannot be determined from the ticket; that is a question the supervisory authority can put to Valve under Article 22 and Article 15(1)(h).\n\nSource: Wayback Machine snapshots of store.steampowered.com/stats/support (2018-02-03, 2021-06-26, 2026-08-10) — data extracted into VALVE_EVIDENCE_PACK/databases/steam_support_stats_history.json (21 snapshots, 2018–2026). Note: the \"~52 min\" response time is the refund-category lower bound; account security response was 2.4–16.5 hrs across the same snapshots. 2021-06-26 is the all-time peak (547,907 refund requests), not a monotone midpoint — volume surged ~6× in 2020–2021 then partially fell before recovering to 373K in 2026.\nAppendix I — Dataset scope · counts that can be reproduced\nCount the records. Check the scope.\nContext & source limits\n\nCount the records, then test the claims: every figure below is re-derivable from the published files.\n\nInspect the underlying datasets, reproduce the counts, and distinguish source rows from unique incidents.\n\nThe master CSV contains 40,448 rows. Of these, 36,516 come from the Discord-AntiScam phishing feed. The remaining 3,932 rows span GitHub, reviews, search results, forum material and other sources, providing a comprehensive index of reported community topics and security reports.\n\nWithin that CSV, 1,690 rows are categorised under the \"Unpatched Security Exploit\" collection label, representing historical user issues and vulnerability disclosures. Tracing these reports involves reviewing each thread's specific build timeline and public patch history.\n\nThe 16,319-record searchable archive is a separate, curated build with its own manifest, designed for precise local exploration of specific user claims and incident reports.\n\nTo build a reliable audit trail, every user-reported record must be verified against documented build timelines and historical patch logs.\n\nThe separate Part II collection records 231,829 unique listing IDs, including 33,509 in the automated registration category and 198,320 flagged as unverified transfers. The input file's SHA-256 matches the preserved measurement. These counts describe listing attempts and observed transfers rather than finalized transaction values or verified theft totals, highlighting the need for primary platform records to measure the exact economic impact. Listing measurements and hashes ↗\n\nMaster CSV ↗ · Searchable archive manifest ↗ · Inspect source records ↗\n\nAppendix J — About this investigation\nValve publishes no enforcement record. We built one.\n\nIndependent. Non-commercial. Built from public data only. Submitted to regulators.\n\n88.97%automation fleet untouched — no ban of any kind\n67.77%of 51,732 adjudicated scammers walk free\n$26.8M+floor on store spend by non-limited fleet\n3.6%gambling domains blocked by Valve's Link Filter\n8 yearsof security incidents documented\n\nWhat this is. A forensic dossier into Valve Corporation's Steam platform — its enforcement record, its card-farming economy, its legal framework, and the authentication infrastructure that gambling operators use through Steam's own OpenID relay. Every figure is reproducible from two sources: Valve's own public API and the datasets published alongside this investigation.\n\nWho it is for. Regulators with jurisdiction over Valve — the GDPR supervisory authority for the Netherlands, FinCEN, the SEC, the DSA Digital Services Coordinator, UOKiK, and any law enforcement agency examining Steam-linked financial flows. Also for journalists, researchers, and every user who received a permanent account ban, a refused refund, or a stolen inventory and was told there is no appeal.\n\nThe single demand. Valve holds this data at full fidelity — ban reasons attached, full ID space, real-time. It can run every query in this dossier in seconds and has chosen not to publish any of it. The question for any competent authority is simple: why not?\n\nWhat the authors do not claim. No login to Steam was completed on any third-party platform during this work. A supplied OpenID URL establishes the request parameters, not a completed login. A separate registrable domain is not by itself proof of evasion. Registration dates are lower bounds on when a host could first have appeared in an OpenID request; they do not establish continuous use. The authors do not assert what Valve knew or intended: every statement about Valve is tied to a dated public document or a dated observation. Where a claim could not be put behind a source document, it has been removed.\n\nWho we are\n\nPhishDestroy — independent investigators. No affiliation with Valve Corporation or any platform named here. One Steam account was used solely to document the GDPR request in Section 18.\n\nLegal disclaimer\n\nNon-commercial, decentralized public-interest investigation. All data provided \"as is\" with zero warranties. This publication is not a judicial finding.\n\nPUBLIC DOMAIN\nLicensing\n\nAll rights surrendered to humanity. Reproduce, adapt, publish — attribution not required. OFAC-region access: prohibited. Full licence & disclaimer →",
        "headings": [
          {
            "level": 2,
            "id": "briefing-heading",
            "text": "The rule. The record. The unanswered questions."
          },
          {
            "level": 2,
            "id": null,
            "text": "Open letter to the Washington State Gambling Commission"
          },
          {
            "level": 3,
            "id": "wsgc-public-address-title",
            "text": "Ten days became ten years.Reopen the record."
          },
          {
            "level": 2,
            "id": null,
            "text": "The site is blocked. The login route is not."
          },
          {
            "level": 3,
            "id": null,
            "text": "Figure 3.1 — The two routes, drawn."
          },
          {
            "level": 3,
            "id": null,
            "text": "The Big Picture Trap: Link Filter is Compliance Theater, Not a Shield"
          },
          {
            "level": 3,
            "id": null,
            "text": "A blocked main domain paired with an unblocked auth host leaves the login route open — and it stays open for years."
          },
          {
            "level": 3,
            "id": null,
            "text": "Background: What Steam Is and Why It Matters Here"
          },
          {
            "level": 3,
            "id": null,
            "text": "What Valve Did: The Domain Block"
          },
          {
            "level": 3,
            "id": null,
            "text": "What a Proxy Domain Is"
          },
          {
            "level": 3,
            "id": null,
            "text": "The Critical Point: The Auth Host Is Sent to Steam in Every Request"
          },
          {
            "level": 3,
            "id": null,
            "text": "What This Proves"
          },
          {
            "level": 3,
            "id": null,
            "text": "Inside Steam, Valve's list is the only list."
          },
          {
            "level": 3,
            "id": null,
            "text": "Link filter protection bypass"
          },
          {
            "level": 3,
            "id": null,
            "text": "Big Picture web browser leaks login cookies and discloses sensitive information (may lead to account takeover)"
          },
          {
            "level": 3,
            "id": null,
            "text": "What this means for a minor with an antivirus installed"
          },
          {
            "level": 3,
            "id": null,
            "text": "The domain’s age.The observation’s date."
          },
          {
            "level": 2,
            "id": null,
            "text": "An endpoint closed. Public tracing lost a key."
          },
          {
            "level": 3,
            "id": null,
            "text": "The Pre-Blackout Era"
          },
          {
            "level": 3,
            "id": null,
            "text": "After the change"
          },
          {
            "level": 2,
            "id": null,
            "text": "One session. More access than the user sees."
          },
          {
            "level": 3,
            "id": null,
            "text": "1. Insufficient Step-up Authentication"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. Lack of Principle of Least Privilege"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. Broken Session Management"
          },
          {
            "level": 3,
            "id": null,
            "text": "4. Domain-Level Blocking of Auth Hosts Was Technically Feasible"
          },
          {
            "level": 3,
            "id": "integration-paradox-title",
            "text": "Valve builds against these rules every day. It did not build to them here."
          },
          {
            "level": 4,
            "id": null,
            "text": "GitHub Fine-Grained Scopes vs Valve Steam Web API"
          },
          {
            "level": 2,
            "id": null,
            "text": "Interactive Exploit & Hijack Simulator"
          },
          {
            "level": 2,
            "id": null,
            "text": "The endpoints behind the sequence."
          },
          {
            "level": 2,
            "id": null,
            "text": "A checked box. Whose action?"
          },
          {
            "level": 3,
            "id": null,
            "text": "How Valve Finally Neutralized \"Trade Substitution\" — And Why It Took 7 Years of Workarounds"
          },
          {
            "level": 4,
            "id": null,
            "text": "Avatar & Name Cooldown (Feb 2024)"
          },
          {
            "level": 4,
            "id": null,
            "text": "7-Day CS2 Trade Reversal (Jul 2025)"
          },
          {
            "level": 4,
            "id": null,
            "text": "Mandatory Mobile Push for API (Dec 2023)"
          },
          {
            "level": 4,
            "id": null,
            "text": "Account Age & Name Banners (2022–2024)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Their rulebook. The recorded platforms."
          },
          {
            "level": 3,
            "id": "enforcement-focus-title",
            "text": "One rulebook. Unequal enforcement."
          },
          {
            "level": 4,
            "id": null,
            "text": "Automation"
          },
          {
            "level": 4,
            "id": null,
            "text": "Commercial use"
          },
          {
            "level": 4,
            "id": null,
            "text": "VPN & location disguise"
          },
          {
            "level": 4,
            "id": null,
            "text": "Link obfuscation"
          },
          {
            "level": 4,
            "id": null,
            "text": "Who reviews the decision when support closes the case?"
          },
          {
            "level": 2,
            "id": null,
            "text": "An automation API. A rule against automation."
          },
          {
            "level": 3,
            "id": null,
            "text": "The \"Game Developer\" Fallacy"
          },
          {
            "level": 4,
            "id": null,
            "text": "The Automation Contradiction"
          },
          {
            "level": 4,
            "id": null,
            "text": "A server-side position in the trade flow"
          },
          {
            "level": 2,
            "id": null,
            "text": "Ten days demanded. Ten years to account for."
          },
          {
            "level": 3,
            "id": "letter-company",
            "text": "VALVE CORPORATION"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ten days.Then what?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Follow the declared return host."
          },
          {
            "level": 3,
            "id": "washington-record-heading",
            "text": "Two deadlines. One unanswered enforcement standard."
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve gives gambling sites 10 days"
          },
          {
            "level": 4,
            "id": null,
            "text": "Washington presses Valve"
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve rejects the charge"
          },
          {
            "level": 4,
            "id": null,
            "text": "The routes observed in September 2026"
          },
          {
            "level": 4,
            "id": null,
            "text": "Eighteen months after Valve replied, the regulator still called it an intent."
          },
          {
            "level": 3,
            "id": null,
            "text": "The 10-Day Notice Decade: Forensic Survival Audit of the 23 Named Sites"
          },
          {
            "level": 4,
            "id": null,
            "text": "From 10-Day Warnings to Offshore Conglomerates: The Multi-Billion-Dollar Turnover"
          },
          {
            "level": 2,
            "id": null,
            "text": "The hostname is already in the request."
          },
          {
            "level": 3,
            "id": null,
            "text": "Documented and reported precedents"
          },
          {
            "level": 3,
            "id": null,
            "text": "What a registration date does and does not show"
          },
          {
            "level": 3,
            "id": null,
            "text": "Comparative Audit: API Compliance Standards"
          },
          {
            "level": 2,
            "id": "market-thesis-heading",
            "text": "The off-Steam price gap"
          },
          {
            "level": 2,
            "id": null,
            "text": "The price gap is measurable."
          },
          {
            "level": 3,
            "id": null,
            "text": "What the dollar figure shows"
          },
          {
            "level": 3,
            "id": null,
            "text": "Many venues list more dollar value than Steam."
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam still leads in number of offers."
          },
          {
            "level": 3,
            "id": null,
            "text": "The commercial ecosystem is in plain sight."
          },
          {
            "level": 2,
            "id": null,
            "text": "Who can reset the safeguards?"
          },
          {
            "level": 3,
            "id": null,
            "text": "A recovery ticket that disabled the account's security, and a reported $10,000 loss"
          },
          {
            "level": 3,
            "id": null,
            "text": "Beyond the inventory."
          },
          {
            "level": 3,
            "id": "theft-ledger-title",
            "text": "Valve admitted the door twice, thirty-three months apart. It never closed."
          },
          {
            "level": 4,
            "id": null,
            "text": "What the ledger says that no single case does."
          },
          {
            "level": 3,
            "id": null,
            "text": "Confidentiality must come with technical accountability."
          },
          {
            "level": 2,
            "id": null,
            "text": "Follow the money. Separate the transactions."
          },
          {
            "level": 3,
            "id": null,
            "text": "Where the money actually moves."
          },
          {
            "level": 3,
            "id": null,
            "text": "Classify the activity, then the obligation."
          },
          {
            "level": 3,
            "id": null,
            "text": "Trace proceeds, knowledge and assistance."
          },
          {
            "level": 2,
            "id": null,
            "text": "The Digital Services Act: put knowledge on the record"
          },
          {
            "level": 3,
            "id": null,
            "text": "A ten-day demand."
          },
          {
            "level": 3,
            "id": null,
            "text": "The DSA time window."
          },
          {
            "level": 3,
            "id": null,
            "text": "Duration needs a notice trail."
          },
          {
            "level": 3,
            "id": null,
            "text": "of annual worldwide turnover"
          },
          {
            "level": 2,
            "id": null,
            "text": "Minors: a Steam login is not an age check"
          },
          {
            "level": 3,
            "id": null,
            "text": "Identify the operator and the data."
          },
          {
            "level": 3,
            "id": null,
            "text": "Record the journey from login to deposit."
          },
          {
            "level": 2,
            "id": null,
            "text": "The request. The reply. The missing comparison."
          },
          {
            "level": 3,
            "id": null,
            "text": "The records exist; the data subject did not receive them."
          },
          {
            "level": 2,
            "id": null,
            "text": "The Subscriber Agreement against the platform's own architecture"
          },
          {
            "level": 3,
            "id": null,
            "text": "The Market ceiling and the commercial-use prohibition"
          },
          {
            "level": 3,
            "id": null,
            "text": "The API-key vulnerability as a platform design question rather than user negligence"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve receives the auth hostname on every login"
          },
          {
            "level": 3,
            "id": null,
            "text": "The pattern in the archived complaints"
          },
          {
            "level": 3,
            "id": null,
            "text": "A court evaluating this record would not read the SSA in isolation."
          },
          {
            "level": 2,
            "id": null,
            "text": "The findings. The records we ask for."
          },
          {
            "level": 2,
            "id": null,
            "text": "Evidence Memorandum — material provided by Source 1"
          },
          {
            "level": 2,
            "id": null,
            "text": "The redaction in the produced PDF is cosmetic: the covered text remains extractable"
          },
          {
            "level": 2,
            "id": null,
            "text": "Support and Legal Correspondence Exhibits"
          },
          {
            "level": 2,
            "id": null,
            "text": "Selected primary records"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-01",
            "text": "Hardware keys, requested in 2016"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-02",
            "text": "Crash reports without an effective opt-out"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-03",
            "text": "Auth-ticket abuse reported to Valve"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-01",
            "text": "44 disputed Market purchases"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-02",
            "text": "A permanent ban and closed appeals"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-03",
            "text": "A recovery reset and a reported $10,000 loss"
          },
          {
            "level": 2,
            "id": null,
            "text": "ArchiSteamFarm and the automation clause"
          },
          {
            "level": 2,
            "id": null,
            "text": "Rules ledger: clauses against recorded platforms"
          },
          {
            "level": 3,
            "id": "ledger-title",
            "text": "Commercial Use & Account Charging"
          },
          {
            "level": 3,
            "id": "lw-register-title",
            "text": "Platform register 175"
          },
          {
            "level": 4,
            "id": null,
            "text": "Burden of proof"
          },
          {
            "level": 4,
            "id": null,
            "text": "What a tagged record is, and is not"
          },
          {
            "level": 2,
            "id": null,
            "text": "DSAR playbook: request the evidence"
          },
          {
            "level": 3,
            "id": null,
            "text": "Preserve your timeline."
          },
          {
            "level": 3,
            "id": null,
            "text": "Request your retained data."
          },
          {
            "level": 3,
            "id": null,
            "text": "Keep the delivery record."
          },
          {
            "level": 3,
            "id": null,
            "text": "Compare the response."
          },
          {
            "level": 3,
            "id": null,
            "text": "Account security & access records"
          },
          {
            "level": 3,
            "id": null,
            "text": "A discrepancy is evidence to investigate."
          },
          {
            "level": 2,
            "id": null,
            "text": "Support volume. Published response times."
          },
          {
            "level": 3,
            "id": null,
            "text": "Two queues at one support desk, read across 21 archived captures."
          },
          {
            "level": 2,
            "id": null,
            "text": "Count the records. Check the scope."
          },
          {
            "level": 2,
            "id": null,
            "text": "Valve publishes no enforcement record.\nWe built one."
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/de/",
          "https://dotesports.com/counter-strike/news/csgo-lounge-billion-bets-3896",
          "https://store.steampowered.com/agreement/?l=english",
          "http://web.archive.org/web/20260921022032/https://store.steampowered.com/agreement/?l=english",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-all-results.json",
          "https://blog.counter-strike.net/expresstrade/",
          "http://web.archive.org/web/20260307161538/https://blog.counter-strike.net/expresstrade/",
          "https://wsgc.wa.gov/news/2016/washington-state-gambling-commission-orders-valve-stop-skins-gambling",
          "http://web.archive.org/web/20260520012601/https://wsgc.wa.gov/news/2016/washington-state-gambling-commission-orders-valve-stop-skins-gambling",
          "https://fr.scribd.com/document/328063293/Valve-s-Oct-18th-response-to-Washington-State-Gambling-Commission-s-cease-and-desist",
          "https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921021947/https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921022628/https://steamcommunity.com/linkfilter/?url=https:%2F%2Frollbit.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rbsnin.com.20260921T021120Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rollbit.com.json",
          "http://web.archive.org/web/20260921022740/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fskin.club",
          "http://web.archive.org/web/20260921022842/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fsc-auth.net",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skin.club.json",
          "http://web.archive.org/web/20260921022603/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fhowl.gg",
          "http://web.archive.org/web/20260921022636/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fhowl.uno",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/howl.gg.json",
          "http://web.archive.org/web/20260921022840/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fduelbits.com",
          "http://web.archive.org/web/20260921022901/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fswitchflips.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/duelbits.com.json",
          "http://web.archive.org/web/20260921022758/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgofast.com",
          "http://web.archive.org/web/20260921022847/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fauthtofast.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgofast.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/farmskins.com.20260921T025840Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/steam.kobal.cc.20260921T025844Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/farmskins.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cobaltlab.tech.20260921T041604Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cobaltauth.com.20260921T041608Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/cobaltlab.tech.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgo.net.20260921T041619Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cn2.easylot.net.20260921T041623Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgo.net.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/ggdrop.com.20260921T041637Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/ggauth.com.20260921T041641Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/ggdrop.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rustchance.com.20260921T041703Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/hgfuihd.com.20260921T041706Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rustchance.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skin.fans.20260921T041710Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.skinfans.com.20260921T041713Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skin.fans.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinport.com.20260921T041724Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinport.app.20260921T041728Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skinport.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skins.cash.20260921T041731Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinscash.live.20260921T041735Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skins.cash.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2hunt.com.20260921T041739Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rstspcl.com.20260921T041742Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tf2hunt.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgogem.com.20260922T192355Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/api.csgem.com.20260922T192358Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-2026-09-22.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/gamdom.com.20260922T192326Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/login.gambldom.com.20260922T192330Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/12cs.fail.20260922T192347Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/fail.games.20260922T192351Z.html",
          "http://web.archive.org/web/20260921022953/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgoempire.com",
          "http://web.archive.org/web/20260921022947/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgoempirelogin4.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgoempire.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cs.money.20260921T021131Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.dota.trade.20260921T021134Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/cs.money.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csfloat.com.20260921T041612Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgofloat.com.20260921T041615Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csfloat.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/g4skins.com.20260921T041630Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.g4s.to.20260921T041634Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/g4skins.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/juice.gg.20260921T041644Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/letmeinjuice.com.20260921T041648Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/juice.gg.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/market.csgo.com.20260921T041652Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2.net.20260921T041655Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/market.csgo.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rust.tm.20260921T041659Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rust.tm.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgolounge.com.20260922T192333Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2.net.20260922T192340Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2lounge.com.20260922T192337Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinbaron.de.20260921T041717Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinbaron.com.20260921T041721Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skinbaron.de.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2royal.com.20260921T041746Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2auth.com.20260921T041750Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tf2royal.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tradeit.gg.20260921T041753Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/connect-tradeit.com.20260921T041757Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tradeit.gg.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/upgrader.pro.20260921T041801Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/upgauth.space.20260921T041804Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/upgrader.pro.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-recheck-2026-09-21.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/domain-registration.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wayback-snapshots.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-2026-09-22c.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/master_registry.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/longitudinal-steam-phishing-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-steam-phishing-100.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-coverage-2026-09-22.json",
          "https://blog.csfloat.com/how-floatdb-tracks-items/",
          "http://web.archive.org/web/20260921022415/https://blog.csfloat.com/how-floatdb-tracks-items/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/platform-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/platforms-removed.json",
          "https://hackerone.com/reports/291750",
          "http://web.archive.org/web/20251116185046/https://hackerone.com/reports/291750",
          "https://hackerone.com/reports/1079561",
          "http://web.archive.org/web/20260924181830/https://hackerone.com/reports/1079561",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/hackerone-reports.json",
          "https://phishdestroy.io/steam_dossier/de/steam_enforcement_evidence.html#support-records",
          "https://www.darknavy.org/blog/exploiting_steam_usual_and_unusual_ways_in_the_cef_framework/",
          "https://steamcommunity.com/groups/SteamClientBeta/discussions/0/3365901765276206401/",
          "http://web.archive.org/web/20250804051514/https://steamcommunity.com/groups/SteamClientBeta/discussions/0/3365901765276206401/",
          "https://www.chromium.org/developers/design-documents/safebrowsing/",
          "http://web.archive.org/web/20260821101616/https://www.chromium.org/developers/design-documents/safebrowsing/",
          "https://www.chromium.org/developers/how-tos/api-keys/",
          "http://web.archive.org/web/20260830122831/https://www.chromium.org/developers/how-tos/api-keys/",
          "https://github.com/Homebrew/homebrew-cask/issues/193814",
          "https://testsafebrowsing.appspot.com/",
          "https://phishdestroy.io/steam_dossier/AUTH_AUDIT.md",
          "https://datatracker.ietf.org/doc/rfc6749/",
          "https://docs.cloud.google.com/docs/authentication/api-keys",
          "https://listings.pcisecuritystandards.org/pdfs/PCI_DSS_Resource_Guide_(003).pdf",
          "https://developer.apple.com/news/?id=02202019a",
          "http://web.archive.org/web/20250506070026/https://developer.apple.com/news/?id=02202019a",
          "https://dev.twitch.tv/docs/authentication/validate-tokens/",
          "https://discuss.dev.twitch.com/t/legacy-twitch-api-v5-i-e-kraken-shutdown-reminder-february-28-2022/36589",
          "http://web.archive.org/web/20250127085635/https://discuss.dev.twitch.com/t/legacy-twitch-api-v5-i-e-kraken-shutdown-reminder-february-28-2022/36589",
          "https://store.steampowered.com/news/posts/?enddate=1788390000",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/4123547285514022851",
          "https://skinvault.gg/blog/cs2-trade-protection-explained/",
          "https://csmarketcap.com/blog/market-insights/from-boom-to-bust-cs2s-trade-protection-impact",
          "https://skin.land/blog/steam-changes-cs2-trade-ban-logic-timing/",
          "https://help.steampowered.com/faqs/view/3041-A87A-E5F6-B6AC",
          "https://steamcommunity.com/ogg/593110/announcements/detail/533224478739530146",
          "https://steamcommunity.com/games/CSGO/announcements/detail/4447966961421256740",
          "https://steamcommunity.com/sharedfiles/filedetails/?id=2926756889",
          "https://steamcommunity.com/dev/apikey",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3734103130194459461",
          "https://steamcommunity.com/discussions/forum/1/3807266184852932971/",
          "https://help.steampowered.com/faqs/view/225C-C51E-B8F0-55B2",
          "https://store.steampowered.com/news/group/4/view/3314112260640237775",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/issues/325",
          "https://blog.dota2.com/2020/05/trading-cooldown/",
          "https://blog.counter-strike.net/index.php/2018/03/20308/",
          "http://web.archive.org/web/20250226114333/https://blog.counter-strike.net/index.php/2018/03/20308/",
          "https://phishdestroy.io/steam_dossier/de/steam_evidence_archive.html",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/493839547938902179",
          "https://store.steampowered.com/online_conduct",
          "http://web.archive.org/web/20260921022120/https://store.steampowered.com/online_conduct",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260918014700/https://store.steampowered.com/subscriber_agreement/",
          "https://steamcommunity.com/dev/apiterms",
          "http://web.archive.org/web/20260921022210/https://steamcommunity.com/dev/apiterms",
          "https://help.steampowered.com/en/faqs/view/628C-E332-BD8C-4D36",
          "https://phishdestroy.io/steam_dossier/de/social_graph.html",
          "https://phishdestroy.io/steam_dossier/de/security_timeline.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wsgc-skins-gambling-briefing-2018.pdf",
          "https://wsgc.wa.gov/sites/default/files/2023-10/Skins%20Gambling.pdf",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wsgc-briefing-manifest.json",
          "https://x.com/csgobig",
          "https://www.facebook.com/csgobigofficial/",
          "https://500.casino/",
          "https://csgolounge.com/",
          "https://csgocasino.gg/",
          "https://x.com/CSGOatsecom",
          "https://x.com/CSGOSweep/status/937420902538543106",
          "https://x.com/Wild",
          "https://x.com/csgopot",
          "https://x.com/csgodiamondscom",
          "https://www.ftc.gov/legal-library/browse/cases-proceedings/162-3184-csgo-lotto-matter",
          "https://x.com/CSGODouble",
          "https://x.com/csgo_massive",
          "https://www.facebook.com/csgostrongfree/",
          "https://www.facebook.com/CSNCOM/",
          "https://www.gamblingcommission.gov.uk/report/young-people-and-gambling",
          "https://www.aph.gov.au/Parliamentary_Business/Committees/Senate/Environment_and_Communications/Gamingmicro-transactions",
          "https://phishdestroy.io/steam_dossier/de/elite_skins.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/csfloat-catalogue.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/skinport-floor-over-cap.json",
          "https://pricempire.com/cs2-marketplaces",
          "http://web.archive.org/web/20260921022459/https://pricempire.com/cs2-marketplaces",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/priceempire-marketplaces.json",
          "https://www.steamanalyst.com/marketplace",
          "http://web.archive.org/web/20260719014552/https://www.steamanalyst.com/marketplace",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-atlas.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json",
          "https://phishdestroy.io/steam_dossier/de/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/de/steam_enforcement_evidence.html#case-support-recovery",
          "https://top10.owasp.org/2025/A01_2025-Broken_Access_Control/",
          "http://web.archive.org/web/20260920212535/https://top10.owasp.org/2025/A01_2025-Broken_Access_Control/",
          "https://store.steampowered.com/privacy_agreement/",
          "http://web.archive.org/web/20260921021648/https://store.steampowered.com/privacy_agreement/",
          "https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "http://web.archive.org/web/20250818113925/https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "https://www.dexerto.com/counter-strike-2/valve-saves-hacked-cs2-player-threatened-with-ransom-over-300000-of-rare-stickers-3283135/",
          "https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "http://web.archive.org/web/20220702042821/https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "https://www.kaspersky.com/blog/cs-go-two-million-usd-inventory-hack/44697/",
          "https://esportfire.com/article/the-2-million-usd-csgo-hack-22062022",
          "http://web.archive.org/web/20260515110250/https://esportfire.com/article/the-2-million-usd-csgo-hack-22062022",
          "https://esportsbetting.com/valve-deletes-130000-stolen-dragon-lore/",
          "https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "http://web.archive.org/web/20251115173120/https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "https://vkplay.ru/media/news/bloger-rasskazal-kak-podderzhka-steam-vorovala-akkaunty-igrokov/",
          "https://lis-skins.com/ru/blog/krupneisaia-mosenniceskaia-sxema-v-istorii-steam/",
          "https://escorenews.com/ru/csgo/news/44056-sotrudniki-podderjki-steam-zanimalis-krajey-skinov-s-akkauntov-za-god-oni-zarabotali-svyshe-300-tysyach-dollarov",
          "https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "http://web.archive.org/web/20250805141942/https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/outsourcing-archive-records.json",
          "https://community.skin.club/en/news/collector-has-steam-inventory-returned-after-bold-hack",
          "https://esportfire.com/article/300k-scam-full-katowice-2014-holo-collection-hacked",
          "http://web.archive.org/web/20251217072445/https://esportfire.com/article/300k-scam-full-katowice-2014-holo-collection-hacked",
          "https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng",
          "http://web.archive.org/web/20260920024236/https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng",
          "https://ag.ny.gov/press-release/2026/attorney-general-james-sues-game-developer-promoting-illegal-gambling-through",
          "http://web.archive.org/web/20260901015430/https://ag.ny.gov/press-release/2026/attorney-general-james-sues-game-developer-promoting-illegal-gambling-through",
          "https://www.fincen.gov/sites/default/files/2019-05/FinCEN%20CVC%20Guidance%20FINAL.pdf",
          "http://web.archive.org/web/20250711185007/https://www.fincen.gov/sites/default/files/2019-05/FinCEN%20CVC%20Guidance%20FINAL.pdf",
          "https://eur-lex.europa.eu/legal-content/EN/LSU/?uri=CELEX:32018L1673",
          "https://eur-lex.europa.eu/eli/dir/2024/1640/oj/eng",
          "http://web.archive.org/web/20260830153004/https://eur-lex.europa.eu/eli/dir/2024/1640/oj/eng",
          "https://eur-lex.europa.eu/eli/reg/2022/2065/oj/eng",
          "http://web.archive.org/web/20260920080125/https://eur-lex.europa.eu/eli/reg/2022/2065/oj/eng",
          "https://phishdestroy.io/steam_dossier/de/legal_analysis.html",
          "https://partner.steamgames.com/doc/features/auth#website",
          "http://web.archive.org/web/20260921022335/https://partner.steamgames.com/doc/features/auth",
          "https://www.ftc.gov/legal-library/browse/rules/childrens-online-privacy-protection-rule-coppa",
          "http://web.archive.org/web/20260921070051/https://www.ftc.gov/legal-library/browse/rules/childrens-online-privacy-protection-rule-coppa",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/gdpr-ticket-1.png",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/screenshot-manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/gdpr-ticket-2.png",
          "https://datenschutz.hamburg.de/beschwerde",
          "https://edpb.europa.eu/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/regulatory-review/disclosure-audit.json",
          "https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "http://web.archive.org/web/20260821155801/https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "https://phishdestroy.io/steam_dossier/index#exhibit-gallery-section",
          "https://github.com/ValveSoftware/steam-for-linux/issues/4521",
          "https://phishdestroy.io/steam_dossier/de/steam_evidence_archive.html?source=GitHub&record=484",
          "https://github.com/ValveSoftware/steam-for-linux/issues/6459",
          "http://web.archive.org/web/20260419051343/https://github.com/ValveSoftware/steam-for-linux/issues/6459",
          "https://phishdestroy.io/steam_dossier/de/steam_evidence_archive.html?source=GitHub&record=467",
          "https://github.com/ValveSoftware/Source-1-Games/issues/3857",
          "https://phishdestroy.io/steam_dossier/de/steam_evidence_archive.html?source=GitHub&record=768",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "http://web.archive.org/web/20250320082450/https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://phishdestroy.io/steam_dossier/de/steam_evidence_archive.html?source=Reddit&record=4533",
          "https://www.reddit.com/r/ohnePixel/comments/1hahqx2/permanently_banned_steam_account_without_a_clear/",
          "https://phishdestroy.io/steam_dossier/de/steam_evidence_archive.html?source=Reddit&record=4766",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://phishdestroy.io/steam_dossier/de/steam_evidence_archive.html?source=Reddit&record=4592",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/selected-evidence-records.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive_manifest.json",
          "https://phishdestroy.io/steam_dossier/de/card_economy.html",
          "https://github.com/JustArchiNET/ArchiSteamFarm/wiki/FAQ",
          "https://phishdestroy.io/steam_dossier/de/card_economy.html#scale",
          "https://phishdestroy.io/steam_dossier/de/card_economy.html#licence",
          "https://phishdestroy.io/steam_dossier/de/enforcement_audit.html",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "http://web.archive.org/web/20260924181709/https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://rdap.verisign.com/com/v1/domain/csgoempire.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoempire.com",
          "https://rdap.verisign.com/com/v1/domain/csgoempirelogin4.com",
          "https://rdap.verisign.com/com/v1/domain/rustreaper.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustreaper.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rustreaper.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustly.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustly.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rustly.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgofast.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgofast.com",
          "https://rdap.verisign.com/com/v1/domain/authtofast.com",
          "https://rdap.verisign.com/com/v1/domain/duelbits.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fduelbits.com",
          "https://rdap.verisign.com/com/v1/domain/switchflips.com",
          "https://rdap.verisign.com/com/v1/domain/farmskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffarmskins.com",
          "https://tld-rdap.verisign.com/cc/v1/domain/kobal.cc",
          "https://rdap.verisign.com/com/v1/domain/csgoluck.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoluck.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgoluck.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/domain-registry/insane.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Finsane.gg",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/insane.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs2skin.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs2skin.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/cs2skin.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/domain-registry/juice.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fjuice.gg",
          "https://rdap.verisign.com/com/v1/domain/letmeinjuice.com",
          "https://rdap.verisign.com/com/v1/domain/ggdrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fggdrop.com",
          "https://rdap.verisign.com/com/v1/domain/ggauth.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/domain-registry/howl.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhowl.gg",
          "https://rdap.radix.host/rdap/domain/howl.uno",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/domain-registry/chicken.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fchicken.gg",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/chicken.gg.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/domain-registry/csgocasino.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgocasino.gg",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgocasino.gg.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/domain-registry/hunt.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhunt.gg",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/hunt.gg.json",
          "https://rdap.verisign.com/com/v1/domain/csbattle.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsbattle.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csbattle.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/domain-registry/skinrave.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinrave.gg",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skinrave.gg.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/domain-registry/csdouble.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsdouble.gg",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csdouble.gg.json",
          "https://rdap.verisign.com/com/v1/domain/rustchance.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustchance.com",
          "https://rdap.verisign.com/com/v1/domain/hgfuihd.com",
          "https://rdap.radix.host/rdap/domain/cobaltlab.tech",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcobaltlab.tech",
          "https://rdap.verisign.com/com/v1/domain/cobaltauth.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/domain-registry/raided.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fraided.gg",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/raided.gg.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/domain-registry/rustneo.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustneo.gg",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rustneo.gg.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/domain-registry/splits.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsplits.gg",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/splits.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/upgrader.pro",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fupgrader.pro",
          "https://rdap.radix.host/rdap/domain/upgauth.space",
          "https://rdap.centralnic.com/fans/domain/skin.fans",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.fans",
          "https://rdap.nic.one/domain/hotpizza.one",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhotpizza.one",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/hotpizza.one.json",
          "https://rdap.verisign.com/com/v1/domain/g4skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg4skins.com",
          "https://rdap.verisign.com/com/v1/domain/tf2royal.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2royal.com",
          "https://rdap.verisign.com/com/v1/domain/tf2auth.com",
          "https://rdap.verisign.com/com/v1/domain/tf2hunt.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2hunt.com",
          "https://rdap.verisign.com/com/v1/domain/rstspcl.com",
          "https://rdap.identitydigital.services/rdap/domain/tf2.bet",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2.bet",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tf2.bet.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/domain-registry/openstars.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fopenstars.gg",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/openstars.gg.json",
          "https://rdap.verisign.com/com/v1/domain/skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skins.com.json",
          "https://rdap.identitydigital.services/rdap/domain/white.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwhite.market",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/white.market.json",
          "https://rdap.identitydigital.services/rdap/domain/moon.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmoon.market",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/moon.market.json",
          "https://rdap.verisign.com/com/v1/domain/csfloat.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsfloat.com",
          "https://rdap.verisign.com/com/v1/domain/csgofloat.com",
          "https://rdap.identitydigital.services/rdap/domain/skin.land",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.land",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skin.land.json",
          "https://rdap.verisign.com/com/v1/domain/haloskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhaloskins.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/haloskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/163.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuff.163.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/buff.163.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmarket.csgo.com",
          "https://rdap.verisign.com/net/v1/domain/dota2.net",
          "https://rdap.verisign.com/com/v1/domain/skinport.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinport.com",
          "https://pubapi.registry.google/rdap/domain/skinport.app",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/domain-registry/skinflow.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinflow.gg",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skinflow.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/skin.place",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.place",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skin.place.json",
          "https://rdap.verisign.com/com/v1/domain/skinsmonkey.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinsmonkey.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skinsmonkey.com.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbaron.de",
          "https://rdap.verisign.com/com/v1/domain/skinbaron.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frust.tm",
          "https://rdap.verisign.com/com/v1/domain/pirateswap.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fpirateswap.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/pirateswap.com.json",
          "https://rdap.radix.host/rdap/domain/mannco.store",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmannco.store",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/mannco.store.json",
          "https://rdap.verisign.com/com/v1/domain/skinswap.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinswap.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skinswap.com.json",
          "https://rdap.verisign.com/com/v1/domain/exeskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fexeskins.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/exeskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/balticskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbalticskins.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/balticskins.com.json",
          "https://rdap.nic.trade/domain/cs.trade",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.trade",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/cs.trade.json",
          "https://rdap.verisign.com/com/v1/domain/rapidskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frapidskins.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rapidskins.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/domain-registry/tradeit.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftradeit.gg",
          "https://rdap.verisign.com/com/v1/domain/connect-tradeit.com",
          "https://rdap.verisign.com/com/v1/domain/49skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F49skins.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/49skins.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/domain-registry/skinvault.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinvault.gg",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skinvault.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/aim.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Faim.market",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/aim.market.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/domain-registry/skinout.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinout.gg",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skinout.gg.json",
          "https://rdap.verisign.com/com/v1/domain/ntskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fntskins.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/ntskins.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/domain-registry/gamerpay.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamerpay.gg",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/gamerpay.gg.json",
          "https://rdap.nic.tf/domain/scrap.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fscrap.tf",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/scrap.tf.json",
          "https://rdap.nic.tf/domain/marketplace.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmarketplace.tf",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/marketplace.tf.json",
          "https://rdap.identitydigital.services/rdap/domain/skins.cash",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.cash",
          "https://rdap.identitydigital.services/rdap/domain/skinscash.live",
          "https://rdap.verisign.com/net/v1/domain/csgo.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo.net",
          "https://rdap.verisign.com/net/v1/domain/easylot.net",
          "https://rdap.verisign.com/net/v1/domain/cybershoke.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcybershoke.net",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/cybershoke.net.json",
          "https://rdap.verisign.com/net/v1/domain/fastcup.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffastcup.net",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/fastcup.net.json",
          "https://rdap.verisign.com/com/v1/domain/leetify.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fleetify.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/leetify.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/domain-registry/scope.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fscope.gg",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/scope.gg.json",
          "https://rdap.verisign.com/com/v1/domain/tradeupspy.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftradeupspy.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tradeupspy.com.json",
          "https://rdap.identitydigital.services/rdap/domain/cs.deals",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.deals",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/cs.deals.json",
          "https://rdap.verisign.com/com/v1/domain/pricempire.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fpricempire.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/pricempire.com.json",
          "https://rdap.identitydigital.services/rdap/domain/lzt.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flzt.market",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/lzt.market.json",
          "https://rdap.verisign.com/com/v1/domain/z2u.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fz2u.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/z2u.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoroll.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoroll.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgoroll.com.json",
          "https://rdap.verisign.com/com/v1/domain/rollbit.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frollbit.com",
          "https://rdap.verisign.com/com/v1/domain/rbsnin.com",
          "https://rdap.identitydigital.services/rdap/domain/500.casino",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F500.casino",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/500.casino.json",
          "https://rdap.verisign.com/com/v1/domain/csgobig.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgobig.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgobig.com.json",
          "https://rdap.verisign.com/com/v1/domain/casedrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcasedrop.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/casedrop.com.json",
          "https://rdap.verisign.com/com/v1/domain/banditcamp.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbanditcamp.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/banditcamp.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinbox.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbox.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skinbox.com.json",
          "https://rdap.verisign.com/com/v1/domain/tastydrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftastydrop.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tastydrop.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/domain-registry/csgopolygon.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgopolygon.gg",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgopolygon.gg.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/domain-registry/magicdrop.ru.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmagicdrop.ru",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/magicdrop.ru.json",
          "https://rdap.verisign.com/com/v1/domain/csdice.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsdice.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csdice.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinodds.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinodds.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skinodds.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgowin.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgowin.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgowin.com.json",
          "https://rdap.verisign.com/net/v1/domain/csgorun.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgorun.net",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgorun.net.json",
          "https://rdap.verisign.com/com/v1/domain/openskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fopenskins.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/openskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustbet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustbet.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rustbet.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgomagic.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgomagic.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgomagic.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgobounty.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgobounty.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgobounty.com.json",
          "https://rdap.verisign.com/com/v1/domain/ezskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fezskins.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/ezskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustcases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustcases.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rustcases.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoreaper.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoreaper.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgoreaper.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgocases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgocases.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgocases.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo-skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo-skins.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgo-skins.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgonet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgonet.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgonet.com.json",
          "https://rdap.verisign.com/com/v1/domain/wtfskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwtfskins.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/wtfskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/flamecases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fflamecases.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/flamecases.com.json",
          "https://rdap.verisign.com/com/v1/domain/gamedom.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamedom.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/gamedom.com.json",
          "https://rdap.nic.club/domain/skin.club",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.club",
          "https://rdap.verisign.com/net/v1/domain/sc-auth.net",
          "https://rdap.verisign.com/com/v1/domain/daddyskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdaddyskins.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/daddyskins.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/domain-registry/rustix.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustix.gg",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rustix.gg.json",
          "https://rdap.nic.club/domain/skins.club",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.club",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skins.club.json",
          "https://rdap.publicinterestregistry.org/rdap/domain/csgohouse.org",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgohouse.org",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgohouse.org.json",
          "https://rdap.verisign.com/net/v1/domain/skinrave.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinrave.net",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skinrave.net.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/domain-registry/bloodycase.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbloodycase.gg",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/bloodycase.gg.json",
          "https://rdap.verisign.com/com/v1/domain/csgoclicker.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoclicker.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgoclicker.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/domain-registry/rustbet.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustbet.gg",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rustbet.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs-drop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs-drop.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/cs-drop.com.json",
          "https://rdap.verisign.com/net/v1/domain/hellstore.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhellstore.net",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/hellstore.net.json",
          "https://rdap.verisign.com/com/v1/domain/rustloot.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustloot.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rustloot.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo-case.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo-case.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgo-case.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgogem.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgogem.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgogem.com.json",
          "https://rdap.verisign.com/com/v1/domain/rainbet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frainbet.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rainbet.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustclash.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustclash.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rustclash.com.json",
          "https://rdap.identitydigital.services/rdap/domain/12cs.fail",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F12cs.fail",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/12cs.fail.json",
          "https://rdap.verisign.com/com/v1/domain/tf2easy.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwww.tf2easy.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tf2easy.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2blaze.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2blaze.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tf2blaze.com.json",
          "https://rdap.verisign.com/com/v1/domain/shuffle.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fshuffle.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/shuffle.com.json",
          "https://rdap.identitydigital.services/rdap/domain/buff.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuff.market",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/buff.market.json",
          "https://rdap.identitydigital.services/rdap/domain/avan.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Favan.market",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/avan.market.json",
          "https://rdap.identitydigital.services/rdap/domain/cs.money",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.money",
          "https://rdap.verisign.com/com/v1/domain/uuskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fuuskins.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/uuskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/youpin898.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fyoupin898.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/youpin898.com.json",
          "https://rdap.verisign.com/com/v1/domain/c5game.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fc5game.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/c5game.com.json",
          "https://rdap.verisign.com/com/v1/domain/waxpeer.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwaxpeer.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/waxpeer.com.json",
          "https://rdap.verisign.com/com/v1/domain/dmarket.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdmarket.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/dmarket.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamcommunity.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamcommunity.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/steamcommunity.com.json",
          "https://rdap.verisign.com/com/v1/domain/lootfarm.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flootfarm.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/lootfarm.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustskins.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rustskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/krakatoa.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fkrakatoa.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/krakatoa.com.json",
          "https://rdap.verisign.com/com/v1/domain/shadowpay.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fshadowpay.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/shadowpay.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/domain-registry/igxe.cn.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Figxe.cn",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/igxe.cn.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/domain-registry/swap.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fswap.gg",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/swap.gg.json",
          "https://rdap.verisign.com/com/v1/domain/bitskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbitskins.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/bitskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2mart.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2mart.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tf2mart.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinbid.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbid.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skinbid.com.json",
          "https://rdap.verisign.com/com/v1/domain/lootbear.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flootbear.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/lootbear.com.json",
          "https://rdap.nic.tf/domain/backpack.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbackpack.tf",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/backpack.tf.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fstntrading.eu",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/stntrading.eu.json",
          "https://rdap.verisign.com/com/v1/domain/skinwallet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinwallet.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skinwallet.com.json",
          "https://rdap.verisign.com/com/v1/domain/dota2market.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdota2market.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/dota2market.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/domain-registry/xplay.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fxplay.gg",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/xplay.gg.json",
          "https://rdap.verisign.com/com/v1/domain/esportal.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fesportal.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/esportal.com.json",
          "https://rdap.registro.br/domain/gamersclub.com.br",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamersclub.com.br",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/gamersclub.com.br.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/domain-registry/epidemic.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fepidemic.gg",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/epidemic.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs2stash.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs2stash.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/cs2stash.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/domain-registry/csgoskins.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoskins.gg",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgoskins.gg.json",
          "https://rdap.verisign.com/com/v1/domain/steamanalyst.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamanalyst.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/steamanalyst.com.json",
          "https://rdap.verisign.com/net/v1/domain/steamcardexchange.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamcardexchange.net",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/steamcardexchange.net.json",
          "https://rdap.verisign.com/com/v1/domain/dotabuff.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdotabuff.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/dotabuff.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/domain-registry/tracker.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftracker.gg",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tracker.gg.json",
          "https://rdap.verisign.com/com/v1/domain/funpay.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffunpay.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/funpay.com.json",
          "https://rdap.verisign.com/com/v1/domain/playerauctions.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fplayerauctions.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/playerauctions.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/domain-registry/eldorado.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Feldorado.gg",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/eldorado.gg.json",
          "https://rdap.verisign.com/com/v1/domain/g2a.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg2a.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/g2a.com.json",
          "https://rdap.verisign.com/net/v1/domain/kinguin.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fkinguin.net",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/kinguin.net.json",
          "https://rdap.verisign.com/com/v1/domain/g2g.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg2g.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/g2g.com.json",
          "https://rdap.verisign.com/com/v1/domain/playerup.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fplayerup.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/playerup.com.json",
          "https://rdap.verisign.com/net/v1/domain/smurfhub.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfhub.net",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/smurfhub.net.json",
          "https://rdap.verisign.com/com/v1/domain/smurfaccounts.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfaccounts.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/smurfaccounts.com.json",
          "https://rdap.verisign.com/com/v1/domain/buycsgorank.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuycsgorank.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/buycsgorank.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgosmurfkings.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgosmurfkings.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgosmurfkings.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/domain-registry/smurfstore.co.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfstore.co",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/smurfstore.co.json",
          "https://rdap.verisign.com/com/v1/domain/steamlvlup.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlvlup.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/steamlvlup.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamlevels.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlevels.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/steamlevels.com.json",
          "https://rdap.verisign.com/com/v1/domain/levelsteam.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flevelsteam.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/levelsteam.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamlevelu.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlevelu.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/steamlevelu.com.json",
          "https://rdap.verisign.com/com/v1/domain/eloking.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Feloking.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/eloking.com.json",
          "https://rdap.publicinterestregistry.org/rdap/domain/boosteria.org",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fboosteria.org",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/boosteria.org.json",
          "https://rdap.verisign.com/com/v1/domain/overgear.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fovergear.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/overgear.com.json",
          "https://rdap.verisign.com/com/v1/domain/blazingboost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fblazingboost.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/blazingboost.com.json",
          "https://rdap.verisign.com/com/v1/domain/dota2boost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdota2boost.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/dota2boost.com.json",
          "https://rdap.verisign.com/com/v1/domain/buyboost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuyboost.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/buyboost.com.json",
          "https://help.steampowered.com/en/faqs/view/365F-4BEE-2AE2-7BDD",
          "https://store.steampowered.com/privacy_agreement/#8",
          "https://www.edpb.europa.eu/system/files/2023-04/edpb_guidelines_202201_data_subject_rights_access_v2_en.pdf",
          "https://web.archive.org/web/20260810154631/https://store.steampowered.com/stats/support",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/part2-measurements.json",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/TOTAL_VALVE_SCANDALS_MASTER_DB.csv",
          "https://phishdestroy.io/steam_dossier/de/license_disclaimer.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/en/index.content.json",
      "export_json_sha256": "8ff0a062e1fc652f2079ac4dba1757f5932b5a7288513895edacdaf752a2eb0e"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "investigation_part2.html",
      "language": "en",
      "title": "Account access & accountability — The Steam Dossier",
      "source_url": "https://phishdestroy.io/steam_dossier/investigation_part2",
      "source_html_sha256": "b3800f329d8b9826cda12272d0e758192e248cffb3a3f057618e664aac821a83",
      "exported_at": "2026-09-29T00:15:52.427Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "investigation_part2.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/en/investigation_part2.pdf?v=print-20260929-v5",
        "sha256": "45ce4c639daa81aab6f38789a870609c1f09482012f5b642595f57b9e9c77ab1",
        "bytes": 121418,
        "pages": 8
      },
      "integrity": {
        "signed_object": "investigation_part2.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "investigation_part2.content.json.asc",
        "digest_file": "investigation_part2.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify investigation_part2.content.json.asc investigation_part2.content.json",
          "sha256sum -c investigation_part2.content.json.sha256"
        ]
      },
      "content": {
        "text": "Dieses Material ist auf Englisch verfügbar.Zurück zum Dossier · Deutsch ↗\n\nTHE STEAM DOSSIER / II\n\nPart II — Account Access, Outsourced Support & Enforcement\n\nPublic automation. Outsourced support. The people left counting the cost.\n\nBegin this subsection ↓\nEXHIBIT 01 / LIVE SHADOW MARKET SURVEILLANCE550,000+\n\nSteam accounts actively on sale on FSB Market (an anonymized label; the original name is withheld here)\nat this very moment\n\n550,000+ LIVE INVENTORY · 231,829 IN HISTORICAL SCRAPED CORPUS (198,320 STEALER LOGS)\n\nThe primary underground clearinghouse for hijacked Steam accounts, FSB Market (associated names withheld), authenticates both buyers and sellers using Valve's official Steam OpenID (openid.realm = https://FSB Market). At any given minute, over half a million stolen and compromised accounts (stealer logs from RedLine/Lumma, phishing captures, credential stuffing) are actively listed for pennies ($0.50–$2.00). Neither FSB Market nor the associated forum is blocked by Valve's Link Filter. This is the industrial reservoir supplying the 63.06% paid bot accounts that Valve bans without assisting the victim.\n\nLive Intel: Shadow Market Monitoring (550k+ Live) ↗ · Open capture record ↗ · Open Link Filter trace ↗550K+ LIVE\n\n01 / AN ECOSYSTEM WITH AUTHORS\n\nAutomation hasa paper trail.\n\nNamed projects. Published capabilities. Trace a tool to its documentation, then inspect the collected developer relationships.\n\n252REPOSITORIES COLLECTED\n3,320GITHUB PROFILES\n4,214PROFILE–REPOSITORY PAIRS\nValve infrastructureCommunity librariesReusable applications\nLines show documented integrations or dependencies. Select a node to follow its evidence.\n\nMulti-account automation / JustArchiNET\n\nArchiSteamFarm\n\nThe project explicitly advertises simultaneous card farming across Steam accounts. Its project file declares a SteamKit2 dependency.\n\nRead the project’s own documentation ↗\n\nSteamKit → ArchiSteamFarm\ndeclared dependency ↗\n\nCOLLECTED RELATIONSHIPS\n\n40 contributor labels · 40 forker labels\n\nContributor sample below. These labels describe the repository relationship, not employment or approval.\n\n@JustArchi@renovate[bot]@JustArchi-ArchiBot@dependabot-preview[bot]@renovate-bot@actions-user@dependabot-support@Abrynos\nWhat the developer graph establishes\n\nThe graph maps published contributor and forker relationships between named projects and GitHub profiles. These are public records — repository forks, contribution lists, profile associations. The question is what the paper trail of published capabilities and developer relationships requires Valve to answer, not what this investigation invented. Source hashes are saved in the map provenance.\n\nExplore the full network ↗Repository source data ↓\n\n02 / DIFFERENT CREDENTIALS. DIFFERENT POWERS.\n\nWhich keyare we talking about?\n\nPlaying a game does not require the player to issue a personal Web API key. That is the distinction at the centre of this inquiry.\n\n01 / USER ACCOUNT\nPersonal Web API key\nsteamcommunity.com/dev/apikey\n\nIssued from a user account for permitted API calls. Key creation, visibility, revocation and abuse detection are account-security questions.\n\n02 / GAME BACKEND\nPublisher Web API key\n\nSteamworks partners use publisher credentials for supported backend operations, including game-related services. A player’s personal key is a different credential.\n\n03 / IDENTITY & SESSION\nOpenID / session tokens\n\nOpenID confirms identity to a website. A Steam session or refresh token has a different purpose. These mechanisms should not be presented as one interchangeable “API key”.\n\nValve documents both user and publisher Web API keys. The entire Web API is therefore not separate from Steamworks. API key documentation ↗ archived 2026-09-15 ↗ · Game-session authentication ↗ archived 2026-08-29 ↗\n\nDOCUMENTED BY THE TOOL’S AUTHOR / MARCH 2024\n\nAutomation can use more than an API key.\n\nTrade Offer Manager’s wiki describes using a session access token for parts of the Web API when no separate API key exists. It also records mobile confirmation for key creation from late 2023. The maintainer calls token use this way unsupported by Valve; this is a dated documentation claim, not a live bypass test.\n\nInspect the maintainer’s explanation ↗ archived 2026-09-24 ↗\n\nTHE HUMAN SIDE / AN ILLUSTRATIVE PHISHING PATH\n\nStill playing.Already exposed.\n\nA message from a friend. A request to vote. A “thank you” page. To the player, the task is finished. A compromised session can outlast that moment.\n\nON THE PLAYER’S SCREEN\n\nF\nA FRIEND’S ACCOUNT\n\n“Can you vote for our team?”\n\nThe request arrives through Steam chat from a familiar account. In this scenario, the linked page opens in the client’s browser.\n\nOUT OF SIGHT\n\nThe trust starts before the website.\n\nA hijacked friend’s account can lend credibility to a phishing link. The surrounding Steam interface does not certify the destination website.\n\nFAMILIAR SENDER / EXTERNAL DESTINATION\nAccount security is the issue before any item is sold.\n\nThe player did not set out to create an automation credential or delegate control. Returning to a game is not evidence that the account is safe. Valve holds the session logs, the API key creation record, and the device correlation data. The victim does not. That asymmetry is the accountability problem.\n\nSession access and credential types\n\nAn API key and a logged-in session are separate credentials with different capabilities. Revoking a key does not terminate an active session. Valve’s own documentation describes both; Valve holds the logs that would show which credential was active at the time of any disputed action. The demand is disclosure of that record — not an inference the investigation has invented. Maintainer documentation on token handling ↗ archived 2026-09-24 ↗ · Valve key documentation ↗ archived 2026-09-15 ↗\n\n03 / THE OFFICIAL MARKET HAS A CEILING\n\nThe item can be rare.The limit stays.\n\nA price above the listing cap cannot be realised through one Community Market listing at that full price.\n\nILLUSTRATIVE ASKING PRICE$5,000Change the item’s asking price\n$100$20,000\n\nAn illustration of the published limit, not a valuation or recommendation to trade.\n\nLISTING CAP≈ $1,800\nWALLET CAP≈ $2,000\n\nAbove the published listing cap.\n\nWallet funds cannot be withdrawn to a bank account. These constraints create the demand that third-party skin markets fill: a demand the listing and wallet caps produce, while Valve's own rules prohibit commercial operators from meeting it.\n\nSteam’s market limits ↗ archived 2026-09-21 ↗\n\n04 / INSIDE THE SUPPORT BOUNDARY\n\nEntrusted with data.Accountable for access.\n\nValve’s privacy policy expressly provides for sharing personal data with third-party support providers, as necessary for support.\n\nTHE PLAYERAccount & evidence\n→\nVALVERecovery process\n→\nSUPPORT PROVIDERDelegated access\n\nPrivacy Policy §5.2 ↗ · Valve's own policy authorises third-party support access. The open questions are: what permissions were granted, what audit trails exist, and what happened when access was allegedly abused.\n\n2015\nThe scale was public\n\nValve acknowledged widespread account theft and described protective measures.\n\nValve publication ↗archived 2026-08-09 ↗\n2015\nValve outsourced the desk — and said so\n\nValve keeps a small in-house Steam Support Leadership team and stated it \"hired a couple different companies\" to handle support (Erik Johnson, Valve, to Kotaku); its privacy policy § 5.2 authorises those third parties' access to user data. Which contractor holds account-recovery access, Valve has never disclosed — community discussion names vendors such as Concentrix, but none is Valve-confirmed. The outsourced desk was in place years before either admission below.\n\nKotaku: Valve on its support ↗archived 2025-07-11 ↗\n2023\nThe first admission\n\nValve's CS:GO team accepts responsibility in writing for an account compromised through its own help-request process, and reverses the trades.\n\nOpen the outsourcing case ↓\n2025\nThe second admission\n\n33 months later, Steam Support writes that a technician \"failed to follow our process which resulted in your account restored to someone else.\" Same channel. Same outcome.\n\nDexerto, 14 Nov 2025 ↗\n\nCASE FILE / HFB & THE OUTSOURCING ALLEGATIONS\n\nThe way in was Steam Support itself.Valve said so in writing.\n\nIn the support reply reproduced by Dexerto, Valve's CS:GO team accepts responsibility for an account compromised through the help-request process — its own channel, not a phishing page and not the user. The items were recovered and the trades reversed, which is the remedy Valve tells other victims does not exist. HFB's inventory was reported at $2,000,000+ on the day and $3,000,000+ in the follow-up; Qkss lost $1,000,000+ the same way and got nothing.\n\nSUPPORT REPLY / REPRODUCED BY DEXERTO · 21 FEB 2023\n“compromised through a support help request, for which the CS:GO team takes responsibility”\nRead the reporting and reproduced message ↗ archived 2025-08-18 ↗\n01 / WHAT VALVE ADMITTED\nIts own support channel was the way in\n\nThe reply covers the compromised account and the reversal of its trades. Valve reversed them — so the trades were reversible. The original authenticated ticket is not in this collection.\n\n02 / WHAT THE SACKINGS DID NOT FIX\nThe same door opened again in November 2025\n\nThe contractor dismissed its entire Steam-support staff — reported by Mzkshow via Dexerto, not a Valve personnel statement. Thirty-three months later Steam Support wrote to another collector that \"a support technician that handled the help request failed to follow our process which resulted in your account restored to someone else.\" Valve's own sentence, about the same channel.\n\nThe second admission, 14 Nov 2025 ↗\n03 / WHAT IS OPEN\nValve has never named the contractor\n\nNeither the contractor nor the location is established by these sources. That is not a hole in the reporting — it is a disclosure Valve has not made about who held access to user accounts.\n\nContemporary account of the case ↗\n\nThree questions Valve has not answered: who could override account recovery, what the access audit found, and what changed afterwards.\n\nLater allegations in the preserved support archive\n\nTwo 2024 Reddit posts relay further Mzkshow investigations — a July 2024 VAC-ban removal case and a December 2024 $13,000 inventory case. These are separately reported incidents. The accountability question in each is identical: who had override access, what did the audit find, and what changed.\n\n14 July 2024 · reported recovery / VAC-ban case ↗2 December 2024 · reported $13,000 inventory case ↗archived 2025-08-05 ↗Two preserved posts, source rows & hashes ↓\n\n05 / FOLLOW THE LOSS\n\nEvery amountneeds a case.\n\nTen cases, June 2022 to March 2026. Every amount is the figure its named source published — $6,300,000, $2,000,000+, $1,000,000+, ≈$320,000, ≈$300,000, and down to €288. Valve holds the transaction log, the session record and the support audit trail for each one, and has produced none of them.\n\nSUPPORT CHANNEL21 JUN 2022\n$2,000,000+\nHFB — the largest inventory in the game\n\nREPORTED INVENTORY VALUATION · RAISED TO $3M+ IN THE FEB 2023 FOLLOW-UP\n\nSeven Souvenir Dragon Lores and the #1 Blue Gem Karambit, that knife alone at about $1.26m. Dormant three years with the authenticator still on; email and password changed through the support recovery route. Valve reversed the trades — and put its responsibility in writing. Before the reversal a reported $200,000+ of proceeds had already been withdrawn through market.csgo.com, which settles in cash and crypto. A reversal returns a skin, not the money someone already banked. The rollback also broke: a buyer hid his Souvenir Dragon Lore in an in-game Storage Unit, the script could not see inside its own container, and Valve duplicated a $130,000 item while undoing a theft — caught by item IDs and community reporting, deleted in July 2022, buyer refunded by BUFF rather than Valve.\n\nDexerto, day of the theft ↗\nWALLET & PURCHASES07 JUL 2022\n>$500\n44 disputed Market purchases\n\nCLAIMED WALLET SPENDING · USD\n\nA user reports unauthorized purchases of low-value Dota 2 items and an unsatisfactory support response.\n\nRead the complaint & linked screenshots ↗\nPLATFORM BREACH14 AUG 2022\n$6,300,000\nCS.Money — 19,000+ skins out of the bots\n\nPRICED VALUATION · FIRST ESTIMATE $1.6M\n\nAttackers took the mobile-authenticator files of the marketplace’s trading bots and emptied them, seeding part of the haul to well-known traders to blur the trail. Community researchers mapped 55 attacker accounts within hours. Valve reversed nothing — a third-party site sits outside Steam, said the same Steam whose inventory, trade API and account system carried the theft end to end.\n\nRead the contemporary account ↗\nSUPPORT CHANNELREPORTED 21 FEB 2023\n$1,000,000+\nQkss — same door, same actor, opposite answer\n\nREPORTED INVENTORY VALUATION\n\nTaken the way HFB was taken, by the same actor, through the same support help request. HFB was made whole eight months earlier. Qkss was not. Nothing in the published record separates the two cases except the size of the audience.\n\nDexerto on the Mzkshow investigation ↗\nSUPPORT CHANNELREPORTED FEB 2023\n≈ $320,000\nThe insider trade itself — one year of it\n\nPROCEEDS OVER ROUGHLY ONE YEAR · NOT AN INVENTORY VALUATION\n\nSupport-side access reached account history up to 15 years old: the first CD key, the first email, the first card — exactly the evidence the recovery process asks for. Whoever holds the database always wins that argument against whoever holds the account. One stolen M4A4 Howl with iBUYPOWER and Titan Katowice 2014 holos sold for $35,000 and ended up with NAVI’s b1t, who had no way of knowing. The contractor’s answer was to dismiss every employee working Steam support.\n\nEscorenews on the same investigation ↗\nWALLET & PURCHASES09 DEC 2023\n€288\nWallet loss despite two-step protection\n\nTRUSTPILOT · SOURCE INDEX 16\n\nThe reviewer reports a hacked account and a refusal to help with Market spending. The export has no individual review URL.\n\nInspect the source provenance ↗\nACCOUNT RECOVERY02 DEC 2024\n$13,000\n“Matvey” — two years after the sackings\n\nAUTHOR’S INVENTORY ESTIMATE\n\nRecovery granted to someone who supplied account data the owner himself could not match. Same route, same result, after the contractor had cleared out its Steam support desk.\n\nRead the preserved allegation ↗\nACCOUNT RECOVERY09 MAY 2025\n≈ $10,000\nRecovery through someone else’s ticket\n\nCLAIMED ITEM LOSS · USD\n\nA Quebec user alleges support reset the password and removed account protection following another person’s request.\n\nRead the first-person complaint ↗\nSUPPORT CHANNEL13 NOV 2025\n≈ $300,000\nHawkeye337 — and Valve’s second written admission\n\nFULL KATOWICE 2014 HOLO COLLECTION\n\nThe attacker demanded 1 bitcoin and began scraping the collection onto Negevs to destroy it. Steam Support’s reply: “a support technician that handled the help request failed to follow our process which resulted in your account restored to someone else.” Thirty-three months after the first admission, the same door. Restored within hours of the thread trending on X. Qkss did not have that audience.\n\nDexerto, 14 Nov 2025 ↗\nWALLET & PURCHASES29 MAR 2026\n$50\nUnauthorized top-up and gifted games\n\nTRUSTPILOT · SOURCE INDEX 290\n\nThe reviewer alleges unauthorized spending and unsuccessful refund requests. The individual review URL is missing from the export.\n\nInspect the source provenance ↗\n\nAttribution and amounts remain as reported by each source. Valve holds the transaction logs, session records and support audit trail for every one of these cases. Produce them. A preserved Reddit post does not settle the question — Valve's own records do.\n\nTHE COLLECTION / AFTER CHECKING\n\n231,829 accounts on sale.Valve holds the logs for every one.\n354 → 201\nTrustpilot records\n\n153 duplicate rows removed. Individual review URLs were not preserved in the export.\n\n231,829\nSteam account listings\n\n33,509 classified as autoregistered; 198,320 under the collector’s stealer label. Listings are not completed sales.\n\nCollection audit ↓Search the source archive ↗",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Part II — Account Access, Outsourced Support & Enforcement"
          },
          {
            "level": 2,
            "id": null,
            "text": "Automation hasa paper trail."
          },
          {
            "level": 3,
            "id": null,
            "text": "ArchiSteamFarm"
          },
          {
            "level": 2,
            "id": null,
            "text": "Which keyare we talking about?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Personal Web API key"
          },
          {
            "level": 3,
            "id": null,
            "text": "Publisher Web API key"
          },
          {
            "level": 3,
            "id": null,
            "text": "OpenID / session tokens"
          },
          {
            "level": 3,
            "id": null,
            "text": "Automation can use more than an API key."
          },
          {
            "level": 2,
            "id": null,
            "text": "Still playing.Already exposed."
          },
          {
            "level": 3,
            "id": "session-hidden-title",
            "text": "The trust starts before the website."
          },
          {
            "level": 2,
            "id": null,
            "text": "The item can be rare.The limit stays."
          },
          {
            "level": 2,
            "id": null,
            "text": "Entrusted with data.Accountable for access."
          },
          {
            "level": 3,
            "id": null,
            "text": "The scale was public"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve outsourced the desk — and said so"
          },
          {
            "level": 3,
            "id": null,
            "text": "The first admission"
          },
          {
            "level": 3,
            "id": null,
            "text": "The second admission"
          },
          {
            "level": 3,
            "id": null,
            "text": "The way in was Steam Support itself.Valve said so in writing."
          },
          {
            "level": 4,
            "id": null,
            "text": "Its own support channel was the way in"
          },
          {
            "level": 4,
            "id": null,
            "text": "The same door opened again in November 2025"
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve has never named the contractor"
          },
          {
            "level": 2,
            "id": null,
            "text": "Every amountneeds a case."
          },
          {
            "level": 3,
            "id": null,
            "text": "HFB — the largest inventory in the game"
          },
          {
            "level": 3,
            "id": null,
            "text": "44 disputed Market purchases"
          },
          {
            "level": 3,
            "id": null,
            "text": "CS.Money — 19,000+ skins out of the bots"
          },
          {
            "level": 3,
            "id": null,
            "text": "Qkss — same door, same actor, opposite answer"
          },
          {
            "level": 3,
            "id": null,
            "text": "The insider trade itself — one year of it"
          },
          {
            "level": 3,
            "id": null,
            "text": "Wallet loss despite two-step protection"
          },
          {
            "level": 3,
            "id": null,
            "text": "“Matvey” — two years after the sackings"
          },
          {
            "level": 3,
            "id": null,
            "text": "Recovery through someone else’s ticket"
          },
          {
            "level": 3,
            "id": null,
            "text": "Hawkeye337 — and Valve’s second written admission"
          },
          {
            "level": 3,
            "id": null,
            "text": "Unauthorized top-up and gifted games"
          },
          {
            "level": 2,
            "id": null,
            "text": "231,829 accounts on sale.Valve holds the logs for every one."
          },
          {
            "level": 3,
            "id": null,
            "text": "Trustpilot records"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam account listings"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/de/investigation_part2.html",
          "https://phishdestroy.io/live-intel/?category=steam",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/lzt.market.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-evidence-lzt.json",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://github.com/JustArchiNET/ArchiSteamFarm/blob/main/ArchiSteamFarm/ArchiSteamFarm.csproj",
          "https://github.com/JustArchi",
          "https://github.com/renovate[bot]",
          "https://github.com/JustArchi-ArchiBot",
          "https://github.com/dependabot-preview[bot]",
          "https://github.com/renovate-bot",
          "https://github.com/actions-user",
          "https://github.com/dependabot-support",
          "https://github.com/Abrynos",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/automation-map.json",
          "https://phishdestroy.io/steam_dossier/de/output_steam_network/network.html",
          "https://phishdestroy.io/steam_dossier/output_steam_network/raw_data.json",
          "https://partner.steamgames.com/doc/webapi_overview/auth",
          "http://web.archive.org/web/20260915025812/https://partner.steamgames.com/doc/webapi_overview/auth",
          "https://partner.steamgames.com/doc/webapi/ISteamUserAuth",
          "http://web.archive.org/web/20260829124950/https://partner.steamgames.com/doc/webapi/ISteamUserAuth",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "http://web.archive.org/web/20260924181824/https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://store.steampowered.com/privacy_agreement/",
          "https://store.steampowered.com/oldnews/19618",
          "http://web.archive.org/web/20260809125516/https://store.steampowered.com/oldnews/19618",
          "https://kotaku.com/valve-explains-why-steam-customer-service-is-still-terr-1736988223",
          "http://web.archive.org/web/20250711004653/https://kotaku.com/valve-explains-why-steam-customer-service-is-still-terr-1736988223",
          "https://www.dexerto.com/counter-strike-2/valve-saves-hacked-cs2-player-threatened-with-ransom-over-300000-of-rare-stickers-3283135/",
          "https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "http://web.archive.org/web/20250818113925/https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "https://lis-skins.com/ru/blog/krupneisaia-mosenniceskaia-sxema-v-istorii-steam/",
          "https://www.reddit.com/r/cs2/comments/1e38jo4/stealing_accounts_and_removing_vac_bans_a_new/",
          "https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "http://web.archive.org/web/20250805141942/https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/outsourcing-archive-records.json",
          "https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "https://escorenews.com/en/csgo/news/44087-valve-steam-support-employee-accused-of-selling-inactive-accounts-inventories-worth-six-figures-b1t-has-one-of-these-skins",
          "https://phishdestroy.io/steam_dossier/PART2_RESEARCH.md",
          "https://www.reddit.com/r/GlobalOffensive/comments/1h56shi/steam_support_is_stealing_accounts/",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/part2-quality-review.json",
          "https://phishdestroy.io/steam_dossier/de/steam_evidence_archive.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/en/investigation_part2.content.json",
      "export_json_sha256": "26618de1892c9476d6467e1b42f44fd630d2d13d3dcc6f2e32e128ee62e388be"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "legal_analysis.html",
      "language": "en",
      "title": "Their terms, your rights — The Steam Dossier",
      "source_url": "https://phishdestroy.io/steam_dossier/legal_analysis",
      "source_html_sha256": "727caba15b9f9c17e88dfe03ae232fb5a6db2792450f503a06b6b4a49c3613f5",
      "exported_at": "2026-09-29T00:15:52.532Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "legal_analysis.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/en/legal_analysis.pdf?v=print-20260929-v5",
        "sha256": "d8522172848fd0b64e5379c75b5959a203066db1cdb63bc064f0d878f5ab4d3a",
        "bytes": 100706,
        "pages": 7
      },
      "integrity": {
        "signed_object": "legal_analysis.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "legal_analysis.content.json.asc",
        "digest_file": "legal_analysis.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify legal_analysis.content.json.asc legal_analysis.content.json",
          "sha256sum -c legal_analysis.content.json.sha256"
        ]
      },
      "content": {
        "text": "Dieses Material ist auf Englisch verfügbar.Zurück zum Dossier · Deutsch ↗\nLegal & economic report\nLegal Analysis — Terms of Service & Regulatory Compliance\n\nTheir terms. Your rights.\n\nWHAT THIS SECTION PROVES\n\nThis forensic legal audit assesses the contractual asymmetry between Valve Corporation and Steam users across key regulatory jurisdictions. It establishes how the revocable subscription license strips statutory consumer ownership, analyzes European Court jurisprudence on digital resale exhaustion, and examines compliance under the Digital Services Act (DSA) and GDPR Art. 15. The analysis demonstrates how automated enforcement mechanisms operate without meaningful appeals while platform market fees systematically extract economic value on every peer transaction.\n\n← Back to Executive briefing\n\nThis report presents a legal, economic and technical analysis of the gap between Steam's declared platform rules and the position of the consumer: automated enforcement with little recourse, and extensive corporate control over digital assets. Figures are stated with their source; where a figure could not be traced to a primary record it has been omitted.\n\nVector 1\n\nReplacing \"ownership\" with a revocable licence, so that digital assets can be withdrawn under the agreement.\n\nVector 2\n\nAutomated enforcement (VACNet) whose bans Steam Support states it cannot reverse.\n\nVector 3\n\nAccount and asset controls combined with a 15% CS2 market fee (5% Steam + 10% publisher fee) that removes value from the ecosystem on every resale.\n\nTerms asymmetry\nLiability waiver and the revocable licence\n2.1 The \"subscription\" model vs. property rights\n\nSection 2 of the Steam Subscriber Agreement grants users only a personal, non-exclusive, non-transferable and revocable licence. Under the agreement, Valve may terminate accounts at any time, and unused Steam Wallet balances may be forfeited.\n\n2.2 The refund illusion vs. the EU Consumer Rights Directive\nLegal framework\tRefund mechanism\tLimitation\nEU Consumer Rights Directive\tUnconditional 14-day right of withdrawal on digital content\tWaived if download begins with explicit consumer consent\nSteam SSA\t14 days / under 2 hours played\tValve may deny at its discretion for \"abuse\"\nAssessment\n\nValve conditions the EU's 14-day statutory withdrawal right on its own \"14 days / under 2 hours\" window, accepted at the moment of download before the product can be evaluated. That policy narrows — not extends — the statutory right; whether it lawfully does so is a question for the competent authority, not a conclusion asserted here.\n\nLitigation\nSecondary Market and Antitrust\nUFC Que Choisir v. Valve — France\n2019\nParis court: the exhaustion-of-rights doctrine applies to digital games — resale is lawful\nOct 2022\nParis Court of Appeal reverses the ruling\n23 Oct 2024\nCour de cassation (Supreme Court): video games are \"complex works\" under the InfoSoc Directive, not software. Digital resale prohibited. Valve prevails.\nWolfire Games antitrust — United States (In re Valve Antitrust Litigation, No. 2:21-cv-00563)\n\nValve's Platform Most-Favored-Nation (PMFN) clause prohibits developers from selling Steam keys more cheaply on any other platform. Competing stores — even those charging 12% commission against Valve's 30% — cannot pass the saving on to consumers.\n\n336total Valve employees (2021). Source: unsealed discovery.\n79employees managing the entire Steam platform. Source: unsealed discovery.\n$3.5Mnet income per employee. Source: unsealed discovery.\n\nUnsealed discovery records show $8.5B gross revenue in 2021 on 336 employees. The 79-person Steam team handled 373,000+ daily support tickets by routing them through outsourced, automated call centres.\n\nUNSEALED DOCKET EXHIBIT · W.D. WASH. CASE 2:21-CV-00563Internal Discovery Memo\n\nTim Sweeney (CEO, Epic Games) to Gabe Newell: \"Why is Steam still taking 30% of gross when payment processing is 2–5% and CDN bandwidth is $0.002/GB? If you subtract out the top 25 games on Steam, I bet Valve made more profit from most of the next 1,000 than the developers themselves made.\"\n\nScott Lynch (COO, Valve Corporation) internal forward to Gabe Newell: \"You mad bro?\"\n\nSworn Deposition Rebuttal (Bloomberg, 2026): Under Rule 30(b)(1) deposition, Gabe Newell testified that \"Valve does not have a policy or practice of dictating prices to third-party software developers on other platforms.\" Plaintiffs confronted Newell with internal Valve memos proving active price policing and delisting threats against developers pricing lower on competing stores. In late March 2026, the Federal Court denied Valve's summary judgment motion, sending the 32,000-developer class action to a jury trial.\nNovember 2024\n\nClass action certified for ~32,000 developers who paid commissions since January 2017, plus a parallel consumer class action.\n\nClaimed damages\n\n$3.1B\nTrebled under US antitrust law = $9.3B potential exposure.\n\nJune 2026: a new lawsuit alleges that Microsoft and Valve engaged in a cartel agreement suppressing competition in PC game distribution.\n\nFinancial Crime & AML Formal Admission\nValve Official Confession: Worldwide Fraud Liquidations (28 October 2019)\n\nOn 28 October 2019, Valve officially terminated the trading and marketplace re-sale of newly purchased Counter-Strike container keys. In its formal public announcement (blog.counter-strike.net/2019/10/26113), Valve Corporation conceded in writing that the virtual economy it architected had become an international money laundering clearinghouse:\n\n\"In the past, most key trades we observed were between legitimate customers. However, worldwide fraud networks have recently shifted to using CS:GO keys to liquidate their gains. At this point, nearly all key purchases that end up being traded or sold on the marketplace are believed to be fraud-sourced.\"\n\nRegulatory Context: This confession followed the Washington State Gambling Commission (WSGC) formal ultimatum to Valve and the July 2016 Cease & Desist orders issued by Valve General Counsel Karl Quackenbush to 23 skin-gambling domains (including CSGO Lotto, CSGOLounge, and OPSkins) only after criminal gambling scrutiny threatened platform operations.\n\nJurisdiction\nA rights-holder in Russia, unreachable to the user\n\nThe Subscriber Agreement presents Valve as a party that owes little and can be reached by no one: locks are permanent, appeals are declined, and access is withdrawn from whole territories on a single line about \"sanctioned regions.\" Set against that posture is what Valve does when its own commercial interests are the thing at stake in a jurisdiction it otherwise treats as difficult.\n\nValve v. Touch Skins — pre-trial IP claim, Russia\n1 Sep 2026\nValve, through the Russian law firm Melling, Voitishkin & Partners, sends a pre-trial demand letter to the operators of Touch Skins, a large CS2 skin-changer, by Russian Post and email.\nGrounds\nThree groups of alleged violations: exclusive rights to the software; rights to the appearance of weapon, knife and glove skins; and Valve's trademarks. The operators' conduct is characterised as deliberate and prolonged.\nDemand\nImmediately cease operation and delete all infrastructure — the software's source code, websites and social-media pages — failing which Valve reserves the right to sue in a Russian court for significant monetary compensation and to refer the matter to law-enforcement for a criminal assessment.\nOutcome\nAfter receiving the letter, the platform announced it was shutting down. Reported as Valve's first use of legal tooling against a skin-changer developer in Russia.\n\nReported by data-miner Maxim \"GabeFollower\" Poletaev (X, ~11 Sep 2026) and Russian gaming press. This is a pre-trial claim, not a filed suit; no docket number is public. Treated here as reported, not as a court record. Sources: dota2.ru archived 2026-09-24 ↗ · Shazoo.\n\nThe same jurisdiction, the other direction\n\nValve is not a stranger to the Russian legal and regulatory system. It complies with Roskomnadzor: on the regulator's demand it removed 260+ Steam community pages carrying prohibited material, and Roskomnadzor has publicly stated that Steam meets the legislation's requirements. Russia's \"landing\" law (Federal Law 236-FZ, in force from 2022) requires large foreign internet platforms serving Russian users to establish a local presence and a Roskomnadzor liaison account. Valve both answers that regulator's takedown orders and, now, wields Russian counsel and the threat of Russian courts to protect its skins as intellectual property.\n\nSo the platform is reachable, capable and rights-asserting exactly where its revenue is concerned. The contrast is with the user: a paying customer in a sanctioned region is told the relationship is over, the community access is locked until 2038, the ticket is closed, and no forum exists in which the decision can be tested — \"they were more than happy to take my money and process my transactions\", the same account's refund from the same Iranian IP having been approved a year earlier (r/pcgaming, 4 Aug 2026; more enforcement letters in the card-economy exhibit). Valve deploys the full apparatus of a national legal system to defend a skin; it affords the user who bought skins no process at all.\n\nValve treats the same jurisdiction as one it can act within, and comply within, whenever the interest at stake is Valve's — Russian counsel, the threat of Russian courts, Roskomnadzor takedown orders answered — while treating its obligations to the users of that market, and of every other, as beyond any process at all. It is a rights-holder where its revenue is concerned and an unreachable party where the user's rights would be.\n\nSources: TASS (RKN: Steam complies) · Federal Law 236-FZ.\n\nLegal opportunism\nThe Arbitration Clause Capitulation\n2023 — the attack\n\nLaw firms (Zaiger LLC, Mason LLP) recruited thousands of users via social media and filed tens of thousands of individual arbitration claims simultaneously.\n\nValve's exposure\n\n$225M+\nin non-refundable arbitration filing fees, before any case was heard on the merits. Calculated under American Arbitration Association (AAA) Consumer Arbitration Rules and Mass Arbitration Supplementary Schedules. Claimants represented by Zaiger LLC and Mason LLP filed ~75,000 individual arbitration demands against Valve Corp. (parallel to antitrust claims in Wolfire Games LLC et al. v. Valve Corp., Case No. 2:21-cv-00563-JCC, W.D. Wash.). Under AAA consumer fee schedules, the business respondent pays non-refundable administrative case fees and arbitrator appointment deposits of ~$3,000+ per individual case (75,000 filings × $3,000 = ~$225M in upfront procedural liabilities). See Bloomberg Law and Reuters legal reports on tech mass arbitration exposure (2023–2024).\n\nPeriod\tSSA dispute mechanism\tObserved effect\tResult\nBefore Sep 2024\tMandatory individual arbitration + class-action waiver\tIndividual litigation becomes economically irrational for users\tMass arbitration → $225M fee threat\nAfter Sep 2024\tDisputes in King County, WA courts only\tArbitration costs are avoided; cases consolidate in a single forum\tClass actions now possible\nConclusion\n\nFor over ten years the SSA required users to waive their right to a jury trial in favour of individual arbitration. After the mass-arbitration filings made that mechanism financially costly to Valve, the SSA was amended to route disputes to King County courts. The change was presented without a meaningful opt-out; the alternative to acceptance was losing access to purchased digital assets by deleting the account.\n\nAlgorithmic enforcement\nVACNet, Presumption of Guilt, and False Positives\nOctober 2023 — AMD Anti-Lag+\n\nAn AMD driver update (v23.10.1) activated Anti-Lag+ in CS2, which intercepted game DLL functions. VAC classified this as cheat-code injection and issued permanent bans to thousands of legitimate users before Valve intervened.\n\nDecember 2023 — high DPI\n\nPlayers with DPI above 10,000 rapidly turning the camera received permanent bans. VACNet could not distinguish physical mouse movement from a \"spinbot\" cheat.\n\nSupport category\tClaimed response time\tActual outcome\nRefund requests\t50 min – 1.5 hr\tAutomatic approval (<14 days, <2 hours played)\nAccount security / recovery\t3–12 hours\tDepends on documentation provided\nContesting a VAC ban\tForm response\tComplete refusal. Support cannot reverse VAC decisions. The ban is permanent.\nOfficial Valve policy\n\n\"VAC bans are permanent, non-negotiable, and cannot be removed by Steam Support.\"\n\nThe same support channel that carries the ban also carries the refusal of review: Steam Support states it cannot reverse a VAC decision. For the user, the algorithm's verdict is the operative outcome.\n\nEconomics of resale\nControl over virtual assets and the resale fee\nThe 15% CS2 market fee — value removed on each resale\nIteration\tBuyer's balance\tSeller receives\tBurned (15%)\n1\t$100.00\t$85.00\t$15.00\n2\t$85.00\t$72.25\t$12.75\n3\t$72.25\t$61.41\t$10.84\n10\t$23.16\t$19.68\t~$3.47\nTotal\t$100 → dust\tValve collects the 15% fee on each resale. Users must add new money to keep trading.\nCS2 trade-up rule change — October 2025\n\nWithout advance notice, Valve altered CS2 trade-up contract rules to allow guaranteed acquisition of rare knives and gloves in exchange for Covert-quality items. Knife prices fell, Covert item prices rose sharply, and panic selling followed across the market.\n\nValve's stated protection is Section 7 of the SSA — no liability for changing platform rules. Users bear the risk in an economy whose rules Valve can change without notice or compensation. The size of the reported market-wide loss is disputed and is not stated here without a primary source.\n\nEuropean regulatory response\nUOKiK, DSA, and the Digital Fairness Act\nUOKiK — Poland, May 2024\n\nPoland's antitrust authority (UOKiK) launched formal antimonopoly proceedings against Valve Corporation and five domestic game publishers/distributors regarding alleged price-fixing, restrictive price-parity clauses, and geo-blocking practices that caused Polish consumers to pay up to 20% more for digital games than neighboring EEA markets. As part of the antitrust inquiry, UOKiK inspectors and police conducted dawn raids and evidence inspections at the Polish premises of domestic partner publishers and distributors (not Valve subsidiary offices, as Valve maintains no Polish entity). Potential statutory fine: up to 10% of annual turnover. Source: UOKiK official announcement, \"Prezes UOKiK wszczął postępowanie przeciwko Valve i twórcom gier\", May 2024.\n\nDigital Services Act (DSA)\n\nRequires transparency in automated moderation. Steam publishes no false-positive/false-negative data for VACNet, and its support channel states that VAC decisions cannot be reversed.\n\nDigital Fairness Act — 2026\n\nExpected provisions: durable access to paid content, prohibition of dark patterns at the point of rights-waiver, recognition of property rights in digital assets, and protection from permanent inventory confiscation.\n\nConclusion\nDocumented gaps between the rules and the record\n1\n\nThe ownership gap. Users pay full price for a licence that the agreement allows Valve to revoke. The French Supreme Court (Oct 2024) held that digital resale is not protected, fixing that position in law.\n\n2\n\nAlgorithmic enforcement. VACNet issued false bans (AMD drivers, high-DPI incidents). Steam Support states it cannot reverse a VAC decision, so the algorithm is the operative final word.\n\n3\n\nEconomy of fees. The 15% CS2 market fee (5% Steam + 10% publisher fee) removes value on every resale, and platform rules can change without notice; Valve's liability for such changes is disclaimed under the SSA.\n\n4\n\nArbitration clause removed. The SSA dropped mandatory arbitration in September 2024, after mass filings exposed Valve to ~$225M in fees. Users received no meaningful opt-out from the change.\n\n5\n\nSelective jurisdiction. Valve engaged Russian counsel (Melling, Voitishkin & Partners) and threatened Russian court proceedings against Touch Skins, while simultaneously treating its obligations to users of that same market as beyond any adjudicative process. Valve acts as a rights-holder where its commercial interests are engaged, and as an unreachable party where the user's rights would be.\n\n← Part I: Proxy bypass & gamblingPart II: Access & accountability →\n\nLegal sources and case records are cited to their original publishers and repositories. No ownership of the underlying documents is claimed.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Legal Analysis — Terms of Service & Regulatory Compliance"
          },
          {
            "level": 2,
            "id": null,
            "text": "Liability waiver and the revocable licence"
          },
          {
            "level": 3,
            "id": null,
            "text": "2.1 The \"subscription\" model vs. property rights"
          },
          {
            "level": 3,
            "id": null,
            "text": "2.2 The refund illusion vs. the EU Consumer Rights Directive"
          },
          {
            "level": 2,
            "id": null,
            "text": "Secondary Market and Antitrust"
          },
          {
            "level": 3,
            "id": null,
            "text": "UFC Que Choisir v. Valve — France"
          },
          {
            "level": 3,
            "id": null,
            "text": "Wolfire Games antitrust — United States (In re Valve Antitrust Litigation, No. 2:21-cv-00563)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve Official Confession: Worldwide Fraud Liquidations (28 October 2019)"
          },
          {
            "level": 2,
            "id": null,
            "text": "A rights-holder in Russia, unreachable to the user"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve v. Touch Skins — pre-trial IP claim, Russia"
          },
          {
            "level": 3,
            "id": null,
            "text": "The same jurisdiction, the other direction"
          },
          {
            "level": 2,
            "id": null,
            "text": "The Arbitration Clause Capitulation"
          },
          {
            "level": 2,
            "id": null,
            "text": "VACNet, Presumption of Guilt, and False Positives"
          },
          {
            "level": 2,
            "id": null,
            "text": "Control over virtual assets and the resale fee"
          },
          {
            "level": 3,
            "id": null,
            "text": "The 15% CS2 market fee — value removed on each resale"
          },
          {
            "level": 3,
            "id": null,
            "text": "CS2 trade-up rule change — October 2025"
          },
          {
            "level": 2,
            "id": null,
            "text": "UOKiK, DSA, and the Digital Fairness Act"
          },
          {
            "level": 2,
            "id": null,
            "text": "Documented gaps between the rules and the record"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/de/legal_analysis.html",
          "https://phishdestroy.io/steam_dossier/de/#briefing-heading",
          "https://dota2.ru/news/67707-valve-cerez-uristov-napravila-krupnoj-rossijskoj-skincendzer-platforme-trebovanie-o-prekrasenii-deatelnosti/",
          "http://web.archive.org/web/20260924181657/https://dota2.ru/news/67707-valve-cerez-uristov-napravila-krupnoj-rossijskoj-skincendzer-platforme-trebovanie-o-prekrasenii-deatelnosti/",
          "https://shazoo.ru/2026/09/12/190508/valve-cerez-rossiiskix-iuristov-dobilas-zakrytiia-krupnogo-skinceindzera-dlia-cs2",
          "https://www.reddit.com/r/pcgaming/comments/1vf24lu/warning_to_all_gamersexpats_steam_took_my_money/",
          "https://phishdestroy.io/steam_dossier/de/card_economy.html#asymmetry",
          "https://tass.ru/obschestvo/23235387",
          "https://base.garant.ru/401414628/",
          "https://uokik.gov.pl/postepowanie-wyjasniajace-w-sprawie-valve-i-dystrybutorow-gier",
          "https://phishdestroy.io/steam_dossier/de/",
          "https://phishdestroy.io/steam_dossier/de/investigation_part2.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/en/legal_analysis.content.json",
      "export_json_sha256": "ca9c7569b13c95b88abfae90828ddcfa4637c78894a69fcf23f475139284d70a"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "license_disclaimer.html",
      "language": "en",
      "title": "License · Rights · Disclaimer — PhishDestroy",
      "source_url": "https://phishdestroy.io/steam_dossier/license_disclaimer",
      "source_html_sha256": "7958dcfb06d5757d2e0c89ecf286534a306a4b1fd2f4c1971a91f16bbce46003",
      "exported_at": "2026-09-29T00:15:54.407Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "license_disclaimer.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/en/license_disclaimer.pdf?v=print-20260929-v5",
        "sha256": "3a953864ee6de71c0c9da9b54732d93a523522b71f974a887f8b86e9bb9e6a73",
        "bytes": 112654,
        "pages": 10
      },
      "integrity": {
        "signed_object": "license_disclaimer.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "license_disclaimer.content.json.asc",
        "digest_file": "license_disclaimer.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify license_disclaimer.content.json.asc license_disclaimer.content.json",
          "sha256sum -c license_disclaimer.content.json.sha256"
        ]
      },
      "content": {
        "text": "Dieses Material ist auf Englisch verfügbar.Zurück zum Dossier · Deutsch ↗\nPHISHDESTROYForensic investigation · Valve / Steam\nLicense · Rights · Disclaimer\nLicense & Legal Disclaimer — Public Domain Dedication\n\nAll rights surrendered to humanity.\n\nWHAT THIS SECTION PROVES\n\nThis instrument establishes the unconditional public domain dedication (CC0 1.0 Universal) and MIT software licensing terms governing the PhishDestroy Steam Dossier. All forensic findings, evidentiary datasets, network graphs, and analytical methodologies are placed irrevocably in the public domain for unrestricted regulatory, legal, and academic use worldwide.\n\n← Back to Executive briefing\n\nPhishDestroy gives up every right to this material — reproduce it, sell it, put your name on it. What follows is two documents in one voice's clothing: an open letter to Valve, written the way we actually write, and a formal waiver written for the authority that will carry the substance forward.\n\nInvestigation · Valve Corporation / SteamPublic edition — no expiry, no take-backs\nWAIVED\nSection ILicense — the actual legal part, but human\n\nPhishDestroy gives up every right to this material. Zero. Gone. Done. You can reproduce it, sell it, put your name on it, tattoo it on your boss, whatever. No credit required, no DM needed, no thank-you card expected.\n\nOne actual rule (yes, just one)\n\nYOU do NOT get to decide whether you're a terrorist.\n\nIf you are a user from Russia or any OFAC-sanctioned country — this material is NOT for you. No loopholes. Enjoy your sanctions.\n\nAnd if you switched your Steam region to Turkey while sitting in Moscow — congratulations on your creative geography. You're still Russian. The sanctions still apply. That's literally the point.\n\nSection IIWhat this is and why it exists\n\nWe will publish more about Valve than an average Valve employee knows about themselves. That's not a brag. That's just where we ended up.\n\nHow did we get here? Funny story: Steam basically created us. It raised us on its scammers, its support tickets, its ban evasion ecosystem — and now here we are. No hard feelings. Poetic, actually.\n\nFor those who haven't read the origin story yet — we already met Valve's extremely expensive European lawyers (Taylor Wessing, since you asked):\n\nhttps://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d archived 2026-08-21 ↗\n\nCharming encounter. Especially given their hourly rate.\n\nDid Valve know? Yes. Did Taylor Wessing know? Almost certainly yes. But when you're that rich, laws are more of a vibe than a requirement, right?\n\nThat's kind of the whole answer, actually.\n\nSteam spent years farming scammers. Not always intentionally — sometimes scammers just got Valve's fingerprints on them by association. We're not trying to be dramatic about it. We're trying to be precise. That's harder for us than being dramatic, to be honest — this is just how we write.\n\nIs this a conflict?\n— No.\n\nCan it be resolved?\n— Yes. But we're not signing any NDA and we're not playing bug bounty for pennies.\n\nWe waited over 4 years for them to fix the spoofing issue before we could write about it publicly. Because if we had written about it earlier, Steam would've put on its little victim face and screamed \"active threat!\" and offered us pocket change to sign a document that would've made us their legal property forever. No thanks.\n\n(Also: Valve itself violates NDA. Their own employees do. The ones near the top. But sure, let's talk about ours.)\n\nSection IIIOpen letter to Valve — seriously, read this\n\nValve: if you want this domain taken down, email us. Outside counsel is not needed for that conversation.\n\nFor the uninitiated: Dr. Patrick holds a Master of Laws in International Commercial Law from the University of Aberdeen and — wait for it — literally finished his doctoral dissertation in IT law. He recently made partner at Taylor Wessing, which is a firm whose entire business model is billing companies like Valve obscene amounts of money to drag things out until the other side runs out of money or patience.\n\nWe don't blame him. Rich guilty clients who pay by the hour — solid career move. We just don't think you should be funding it.\n\nThe deal (open offer, no lawyers needed)\n\nThe domain is the only thing Valve can realistically reach. The investigation, the referrals, and the allied resources are already in motion — they continue with or without the domain.\n\nIf you want the domain:\n\nLet your IT law professionals set a fair price.\n\n50% goes to the SEAL Foundation.\n\nWe kill the domain. No drama. No court. Done.\n\nThis is not a threat. It is a straightforward offer for the one thing that is actually within reach. You won't get it any other way — that's just the architecture of the situation.\n\nWill we \"damage\" Valve directly? Probably not in a way they'll feel fiscally. We're not delusional. But we will do it honestly, openly, without chasing clout — because we don't need clout. We need the world to see what was always publicly visible if you spent enough time looking.\n\nWe have 5 years of archives. What Valve's lawyers showed in discovery — the data that support agents can see, the fingerprints, the paper trail they literally handed us — is enough. We don't need to leak it raw.\n\nWho gets what\n\nRegulators get the originals.\n\nResearchers and journalists get redacted versions (victim reports, children's logins and Valve's charming support commentary removed for obvious reasons).\n\nMinors were among the affected accounts and were not notified. That finding sits in the regulator package with the victim reports and credentials removed, because it belongs in front of a data-protection authority rather than in an article.\n\nAlso, Valve — we want to make something clear before you decide how to play this: PhishDestroy is a community, not a person. You learned that when you addressed legal correspondence to the community without bothering to speak with the community — just milked it for data and banned the accounts.\n\nThe community has no conflict with Valve. We didn't go looking for this. The scammers you grew found us. We blocked them. And here we are.\n\nSection III-BThe allied resources — a note to Steam specifically\n\nWe want to be upfront about the amplification structure, because pretending it doesn't exist would be dishonest.\n\nPhishDestroy, as we understand the community situation, has at least two allied resources that will pick up this material and run with it.\n\nWhat that means in practice:\n\nThey work their own angles on overlapping subject matter.\n\nThey are independent — they don't take our direction, we don't take theirs. Same general topic, different methodology.\n\nThey will NOT be activating on Part 1. They're watching.\n\nIf Valve chooses not to take down the site:\n\nExpect them to surface after Part 2 or Part 3.\n\nThey'll take what's useful from our work, supplement it with their own, and publish under their own authorship.\n\nThis is exactly the kind of thing the license in Section 1 is built for: the material goes where it needs to go, gets supplemented, gets amplified — and neither we nor they owe each other attribution.\n\n(PS for lawyers wondering about liability chains: there are none. These resources don't receive our direction, our funding, or our data. They read what's public and draw their own conclusions. Just like you could.)\n\nWe're not saying this to intimidate. We're saying it so that whoever is strategising on Valve's side has accurate information about what the information environment actually looks like.\n\nOne resource that pulls our material and supplements it would be a story. Two resources doing it independently and reaching similar conclusions is a pattern. Patterns are what regulators notice.\n\nSection IVThe money, the bans, the whole circus\n\nHere's the thing about Steam banning gambling sites and scammers: it's not enforcement. It's revenue capture. Valve pockets the money, cleans its hands, then goes on stage and tells everyone a wholesome story about Pokémon cards and baseball.\n\nWhere support-side compromises are documented — including Valve's written admission in February 2023 taking responsibility for high-value accounts compromised through help requests, and contractor staff dismissals reported by Dexerto and Escorenews following the $320k insider trade (Part II §04 · Main Dossier §14.1) — they rest on published admissions and investigative reporting. Unsubstantiated rumors of support staff operating gambling side hustles or taking percentages to lift bans are unestablished on the public record and are excluded here.\n\nMeanwhile Valve killed the ability to properly track skins in 2017. They even discussed it on their own forums. Called it \"anti-gambling measures\" — while the skin gambling ecosystem continued to route billions through Steam's infrastructure for years after. Great branding.\n\nWe're going to prove that:\n\nSkins are more anonymous than Monero\n\nA Peruvian Cartel allegedly used Dota 2 skins for money movement\n\nSteam is functionally a sanctions-bypass machine worth ~$7B in \"trading cards\" (yes, they actually said trading cards to a prosecutor)\n\nWe've got a video on the skins thing. You'll see it.\n\nWe also know:\n\nReddit moderation is influenced by Valve\n\nThird-party Steam data infrastructure (such as steamid.uk) is operated by a private individual (msart) whose linked sibling ban-list project (steambans.com archive) is co-administered by a confirmed Valve community moderator (killahinstinct_) — leaving independent auditing of platform bans entirely inside Valve's orbit (see Card Economy §08)\n\nWhat they can't control, they ban\n\nValve: if you keep playing dumb — that's fine. Your safe harbour is noted. Google Analytics anonymises your users' IPs anyway. We see what gets deleted. We just can't prove it cheaply enough for your lawyers to care. Yet.\n\nSection VThe malware thing — yes, we're mentioning it\n\nLet's be brutally clear about the sequence of events, because it exposes exactly who you are.\n\nWe are NOT disclosing the vulnerability in the game publicly. We are NOT reporting it to Steam. The programme requires an NDA, and signing one would bar us from telling the affected users what happened to their accounts. Disclosure to the people who lost those accounts, and to regulators, is the point of this work; a confidentiality agreement is incompatible with it.\n\nHere's what actually happened: This vulnerability is practically an open secret in the right circles. We know for a fact that independent security researchers have already shoved the full exploit directly into Steam Support's face. That part is done. You have been officially warned through your own sterile channels.\n\nAnd what did Valve do? Absolutely nothing. Because for Valve, security does not equal profit — in fact, it's the exact opposite. Security is a cost center. Until a threat reaches critical mass and causes a catastrophic public PR meltdown, Valve does not treat it as urgent.\n\nSo what are we doing? We're telling the public it exists, because \"Valve knows about a systemic malware threat and actively chooses to do nothing\" is a critical data point for the regulators currently reading this.\n\nThe game is massive. We're not naming it here. But understand this:\n\nThis is NOT the trivial CS:GO script-kiddie garbage where a server asks you to \"install a driver\". This is catastrophic.\n\nThis is an Unturned-level nightmare: zero-click RCE on server connect. You join a server. You click nothing. You download nothing. The connection itself is the attack surface, and your machine is fully compromised. Let's be real here: dropping an RCE and bypassing local antiviruses by piggybacking on Valve's trusted digital certificates isn't even a novelty on Steam anymore. It is practically a built-in feature of your ecosystem.\n\nValve already knows this exists. But they rely on their favorite, cowardly legal loophole: because the game is technically developed by a third party, Valve washes its hands. They distribute the game, they process the payments, they host the infrastructure, but when a zero-click RCE threatens millions of their users, their stance is: \"Not our game, not our liability.\"\n\nWhen this inevitably blows up, the third-party developer will take the bullet, and Valve will walk away pretending to be the responsible platform that \"assisted\" with the resolution. Classic Valve cowardice. We've seen the playbook.\n\nWe are putting this on the record so that regulators, prosecutors, and journalists understand exactly how Valve handles active malware: by hiding behind third-party developers, deploying NDA gag orders, and leaving the players as sitting ducks.\n\nEnd of the open letterFormal register begins\nFormal register · for the authority\nDeclarationAs to use and rights\n\nPhishDestroy Project & Cybersecurity Coalition\n\nThis declaration accompanies every submission and every exhibit in this referral set. It is addressed to any authority, court, regulator, prosecutor, researcher, journalist or affected person into whose hands the material comes.\n\n1. There are no conditions on use\n\n1.1 All material produced by the Coalition in this referral — the statements of fact, the analysis, the exhibits it has authored, the tooling, and the findings — is released WITHOUT RESERVATION OF ANY RIGHTS.\n\n1.2 Anyone may, without asking and without notifying us:\n\nreproduce it, in whole or in part;\n\nadapt, edit, rewrite, restructure or correct it;\n\ntranslate it;\n\nexcerpt it without indicating that it has been excerpted;\n\nincorporate it into official documents, findings, decisions, pleadings, reports or press material;\n\npresent it as the recipient's own work or the recipient's own findings;\n\nuse it as raw material and discard the rest;\n\nand pass it on to anyone else on the same terms.\n\n1.3 ATTRIBUTION IS NOT REQUIRED AND IS NOT SOUGHT. The Coalition need not be named, cited, credited, thanked, consulted or informed. If material from this referral assists an authority and the Coalition is never mentioned, THAT IS A COMPLETELY SATISFACTORY OUTCOME and the Coalition states so in advance so that the question need not be raised.\n\n1.4 If, on the other hand, an authority finds it more convenient to cite the Coalition as a source, it is free to do so. The choice is entirely the recipient's and neither course carries any consequence.\n\n1.5 This is a WAIVER, not a licence offer. It requires no acceptance, imposes no obligation, and cannot be breached. Software published by the Coalition is separately released under the MIT licence; the research and findings are released into the public domain to the fullest extent permitted, and where a jurisdiction does not permit waiver, the Coalition grants an irrevocable, worldwide, royalty-free licence to the same effect.\n\n2. Why this matters practically, and not only as a courtesy\n\n2.1 An authority may reasonably hesitate to rely on material supplied by an outside party, for fear of appearing to act at that party's instance or of acquiring some entanglement with it.\n\n2.2 THERE IS NOTHING HERE TO BE ENTANGLED WITH. The Coalition asks for nothing, is owed nothing, retains nothing, and has no expectation of any kind. It cannot later assert a right, claim credit, complain of misuse, or object to how the material is characterised, because it has retained no basis on which to do so.\n\n2.3 An authority using this material is therefore not acting for the Coalition. It is using public information that happens to have been assembled by someone else.\n\n3. Everything is open already\n\n3.1 The Coalition's work is public by default:\n\nthe investigations are published openly at https://phishdestroy.io and are freely readable;\n\nthe tooling is published as open source under the MIT licence at https://github.com/phishdestroy archived 2026-09-11 ↗;\n\nthe methodology is set out in the referral itself, at Annex A section A.16D, including the weight and limitations of each source type;\n\nthe Coalition accepts no donations and has published that position since 2018.\n\n3.2 The only material NOT published is that which cannot lawfully or safely be published: personal data of victims and of third parties, and information that would expose a source to retaliation. That material is supplied to authorities in confidence and is identified in the schedules of evidence.\n\n3.3 The Coalition invites scrutiny of its own conduct on the same terms it invites scrutiny of anyone else's, and has volunteered its own data handling to the authorities concerned, including a request for a direction on disposal.\n\n4. Integrity of the evidence bundle\n\n4.1 Exhibits are supplied with the submission or, where marked, on request through a secure channel. They are not published at a public address and no such address should be inferred: material of this kind is provided to authorities directly.\n\n4.2 Each delivery is accompanied by a file SHA256SUMS listing a SHA-256 digest for every file supplied, together with a detached OpenPGP signature SHA256SUMS.asc.\n\n4.3 The signing key is published at https://phishdestroy.io/.well-known/pgp-key.txt and on keys.openpgp.org. Its fingerprint appears in the letterhead of every submission in this set.\n\n4.4 Any recipient may verify at any time that a file in their possession is the file that was sent, unaltered:\n\ngpg --verify SHA256SUMS.asc SHA256SUMS\n\nsha256sum -c SHA256SUMS\n\n4.5 The purpose is not formality. It is so that, if the accuracy or integrity of any exhibit is disputed at a later date, the question can be settled by computation rather than by argument.\n\n5. On register — why the waiver is functional and not merely generous\n\n5.1 The authority may encounter the Coalition's published investigations and find them blunt, adversarial and at times satirical. That impression is correct. The Coalition writes that way deliberately and does not apologise for it.\n\n5.2 IT ALSO RECOGNISES THAT THIS IS THE WRONG REGISTER FOR A REGULATORY OR JUDICIAL PROCEEDING. A serious matter should not be carried in the voice of a campaign. Findings put before an authority should be stated flatly, with their limitations admitted, and should not require the reader to discount for tone before reaching the substance.\n\n5.3 THAT IS PRECISELY WHY THE COALITION WAIVES AUTHORSHIP. The waiver at section 1 is the mechanism by which the substance can be separated from the register: the authority may take what is useful, restate it in its own voice, and discard every word of the Coalition's manner along with the Coalition's name. Nothing is lost by doing so, and the Coalition would prefer it.\n\n5.4 THE COALITION ALSO ASKS THAT THE REGISTER NOT BE MISTAKEN FOR THE METHOD. The published tone is combative; the underlying practice is not careless. Throughout this referral, inference is separated from observation, testimony is identified as testimony, sources are weighted and their weaknesses stated, figures are presented with their limitations, and points the Coalition cannot prove are put as questions for the authority rather than as assertions. Where the evidence cut against the Coalition's own position it has said so — see Annex A, paragraph 7, and section B.0 of the parallel referral.\n\n5.5 THE COALITION EXPLAINS THE CONNECTION BETWEEN ITS MANNER AND ITS FINANCES BECAUSE THE TWO ARE NOT SEPARABLE. It takes no money from anyone — no donations, no bounties, no clients, no sponsors. That refusal is what makes the bluntness possible: an organisation with revenue to protect must moderate what it says about the parties it depends on. Having nothing to protect, the Coalition has nothing to moderate.\n\nIt is also the reason the Coalition continues to exist. There is no other engine. The work is done because it is done; it stops when the people doing it stop.\n\n5.6 The authority need accept none of this. It is stated so that the tone of the Coalition's public work is not read as a measure of the care taken with the material now before it.\n\n6. What the Coalition is providing, in its own words\n\nInformation, research and observation.\n\nNothing is asserted as a finding that the Coalition has no standing to make. Where something is inferred, the referral says so. Where something rests on testimony, the referral says whose and with what limitation. Where the Coalition cannot answer a question, it says that too, and identifies who can.\n\nThe Coalition seeks no remedy, no payment, no acknowledgement and no outcome for itself or for any individual. It asks only that the questions set out in the referral be put to Valve Corporation by a body with the power to compel an answer.\n\nClosing noteTo whoever is carrying this forward\n\nWe want to thank whoever gets this material to where it needs to go. It's probably not going to be a quick trip. Valve has deep pockets and Taylor Wessing charges by the hour — that combination is specifically designed to make people like you give up before they reach the finish line.\n\nWe know what we're doing. We know who we're writing about. Valve built us — how could we not understand them?\n\nPhishDestroy has no conflict with Valve. We blocked the only scammer ring of that scale we've come across — we didn't go looking for a fight with Valve. It just turned out that every road led back to them. Not a conflict. Just topology.\n\nValve cannot resolve the PhishDestroy situation because there is nothing to resolve. We have no relationship. The data about their enrichment schemes and overflow profits is largely public — you just had to spend enough time to see it. Think of it as a success encyclopedia: \"How to Not Follow Sanctions So That Russian Hackers Can't Pirate Our Free Games (The Paid Ones They Won't Pirate Anyway).\" You get the vibe.\n\nWe don't need authorship.\n\nWe don't need attribution.\n\nWe don't need a win.\n\nWe need someone with actual authority to ask Valve the questions that are already sitting in this referral, with the power to require an answer.\n\nThat's it. That's the whole ask.\n\nCases will live at:\n\nhttps://steamdestroy.eth/\n\nhttps://steamdestroy.eth.limo (currently broken — will fix when needed)\n\nWe'll be at:\n\nhttps://phishdestroy.eth.limo/ archived 2026-06-27 ↗\n\nhttps://phishdestroy.eth/\n\nTwo signed objects · rights and published text\nSigned releaseWhat is signed, and what it covers\n\nThe rights grant and research text are separately signed JSON objects below. Each detached OpenPGP signature authenticates the exact bytes of the JSON named beside it. The rights statement grants permissions; the text snapshot identifies and contains the material being published.\n\n1. Rights statement — license-rights.json\n\nSigned object: the complete license-rights.json file, containing the public rights grant dated 28 September 2026. It grants permission to copy, publish, edit, translate, combine and commercialise authored dossier materials without attribution, notification or approval. This signature authenticates the rights statement; it does not authenticate the text of every webpage or PDF.\n\nThe original signed release is preserved unchanged. Its existing grant cannot be withdrawn or narrowed by changing the website, publishing another file or taking the site offline. Third-party materials retain their own rights.\n\nRights statement JSON ↗ · Signature of license-rights.json ↗ · SHA-256 of license-rights.json ↗\n\ngpg --verify license-rights.json.asc license-rights.json\nsha256sum -c license-rights.json.sha256\n2. Published text — dossier-text.json\n\nSigned object: the complete dossier-text.json file. It contains the actual readable text of the exported pages in documents[].content.text, with each page’s title, language, source URL, source HTML hash, headings and references. The documents list is the exact inventory covered by this snapshot; the language variants are listed separately. It is a text publication, not just a list of hashes.\n\nEvery entry identifies its lightweight page PDF by filename and SHA-256 in documents[].pdf. The JSON also identifies the original rights statement by URL and SHA-256, so the published text, its PDF and the applicable rights release can be matched without guessing. Linked external databases, image originals and pages absent from the inventory are not embedded in this text snapshot.\n\nFull signed text JSON ↗ · Signature of dossier-text.json ↗ · SHA-256 of dossier-text.json ↗\n\ngpg --verify dossier-text.json.asc dossier-text.json\nsha256sum -c dossier-text.json.sha256\n\nOn the dossier home page, the PDF and JSON buttons export the research bundle. On an inner page, they export that page in its published language. Each page JSON also has its own detached signature and SHA-256 file, named explicitly in its integrity object. To verify the associated PDF, calculate its SHA-256 and compare it with the pdf.sha256 value in the verified JSON. The PDF is bound by that digest; it does not carry a PDF-format digital signature.\n\n3. Printable research bundle — steam-dossier-{language}.content.json\n\nSigned object: the complete language-specific JSON file, including the bundled chapter text in documents[].content.text, chapter page ranges, source languages, the excluded-source inventory and the exact PDF digest in pdf.sha256. The five supplementary evidence archives remain linked online and are not bundled. Authored research text is retained; visual catalogues are replaced with source links.\n\nEnglish JSON ↗ · Detached OpenPGP signature ↗ · SHA-256 digest ↗\n\nDeutsch JSON ↗ · Detached OpenPGP signature ↗ · SHA-256 digest ↗\n\ngpg --verify steam-dossier-en.content.json.asc steam-dossier-en.content.json\nsha256sum -c steam-dossier-en.content.json.sha256\n\nPublic verification key ↗\n\nSigning fingerprint: 129F C7F3 9C40 C69D 2EF3 C329 BFCF 9E8D D295 EE01\n\ngpg --import pgp-key.txt\ngpg --fingerprint 129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01\n\nCheck that the displayed fingerprint matches the one above, then verify the signature against the exact JSON filename. Editing a signed JSON changes the signed object and invalidates its original signature. A valid signature identifies the published bytes; it is not independent verification of the research findings.\n\nPhishDestroy — public investigation — all rights surrendered to humanity\n\nOFAC-region access: prohibited",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "License & Legal Disclaimer — Public Domain Dedication"
          },
          {
            "level": 2,
            "id": null,
            "text": "Section ILicense — the actual legal part, but human"
          },
          {
            "level": 3,
            "id": null,
            "text": "One actual rule (yes, just one)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Section IIWhat this is and why it exists"
          },
          {
            "level": 2,
            "id": null,
            "text": "Section IIIOpen letter to Valve — seriously, read this"
          },
          {
            "level": 3,
            "id": null,
            "text": "The deal (open offer, no lawyers needed)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Section III-BThe allied resources — a note to Steam specifically"
          },
          {
            "level": 2,
            "id": null,
            "text": "Section IVThe money, the bans, the whole circus"
          },
          {
            "level": 2,
            "id": null,
            "text": "Section VThe malware thing — yes, we're mentioning it"
          },
          {
            "level": 2,
            "id": null,
            "text": "DeclarationAs to use and rights"
          },
          {
            "level": 3,
            "id": null,
            "text": "1. There are no conditions on use"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. Why this matters practically, and not only as a courtesy"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. Everything is open already"
          },
          {
            "level": 3,
            "id": null,
            "text": "4. Integrity of the evidence bundle"
          },
          {
            "level": 3,
            "id": null,
            "text": "5. On register — why the waiver is functional and not merely generous"
          },
          {
            "level": 3,
            "id": null,
            "text": "6. What the Coalition is providing, in its own words"
          },
          {
            "level": 2,
            "id": null,
            "text": "Closing noteTo whoever is carrying this forward"
          },
          {
            "level": 2,
            "id": null,
            "text": "Signed releaseWhat is signed, and what it covers"
          },
          {
            "level": 3,
            "id": null,
            "text": "1. Rights statement — license-rights.json"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. Published text — dossier-text.json"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. Printable research bundle — steam-dossier-{language}.content.json"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/de/license_disclaimer.html",
          "https://phishdestroy.io/steam_dossier/de/#briefing-heading",
          "https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "http://web.archive.org/web/20260821155801/https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "https://phishdestroy.io/steam_dossier/de/investigation_part2.html#outsourcing-case",
          "https://phishdestroy.io/steam_dossier/de/#theft-ledger",
          "https://steamid.uk/",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/groups/steambans",
          "https://steamcommunity.com/id/killahinstinct_",
          "https://phishdestroy.io/steam_dossier/de/card_economy.html#governance",
          "https://phishdestroy.io/",
          "https://github.com/phishdestroy",
          "http://web.archive.org/web/20260911040557/https://github.com/PhishDestroy",
          "https://phishdestroy.io/.well-known/pgp-key.txt",
          "https://steamdestroy.eth/",
          "https://steamdestroy.eth.limo/",
          "https://phishdestroy.eth.limo/",
          "http://web.archive.org/web/20260627040219/https://phishdestroy.eth.limo/",
          "https://phishdestroy.eth/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json.asc",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json.sha256",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json.sha256?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json.sha256?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json.sha256?v=print-20260928-v3"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/en/license_disclaimer.content.json",
      "export_json_sha256": "bd5fdb1a7f32d3c39ba3b6556c1afa5cb5de196950ebc07c3910c6792f106131"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "market_economics.html",
      "language": "en",
      "title": "One infrastructure, two markets — The Steam Dossier",
      "source_url": "https://phishdestroy.io/steam_dossier/market_economics",
      "source_html_sha256": "e0d43cc331b4838c0dfb820094c9a247325abb1ff0c15ab7a046f6e9d06520b8",
      "exported_at": "2026-09-29T00:15:54.310Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "market_economics.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/en/market_economics.pdf?v=print-20260929-v5",
        "sha256": "cbf8f2abfd403f11b410b998f33a4f48888ac152970c58872cfab9b0144f81bb",
        "bytes": 96143,
        "pages": 7
      },
      "integrity": {
        "signed_object": "market_economics.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "market_economics.content.json.asc",
        "digest_file": "market_economics.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify market_economics.content.json.asc market_economics.content.json",
          "sha256sum -c market_economics.content.json.sha256"
        ]
      },
      "content": {
        "text": "Dieses Material ist auf Englisch verfügbar.Zurück zum Dossier · Deutsch ↗\nExhibit VII · Market Architecture · 20 September 2026\nMarket Economics — Two Economies & The Listing Ceiling\n\nTheir infrastructure. Two economies.\n\nWHAT THIS SECTION PROVES\n\nThis chapter analyzes the systemic market bifurcation created by Valve's $1,800 listing cap and non-withdrawable wallet balances. By surveying 38 active external skin exchanges holding approximately $1.28 billion in listed valuation, the investigation proves that high-tier trading necessarily migrates to external shadow platforms while relying on Steam's underlying trade and authentication infrastructure. While commercial use is formally prohibited in the Subscriber Agreement, Valve facilitates and monetizes this two-tier economy without published enforcement records.\n\n← Back to Executive briefing\n\n38 active third-party CS2 marketplaces, plus Steam's own. Every skin listed on any of them must move through Steam's inventory and trade API. Valve's rules prohibit commercial exploitation of that infrastructure. The roughly $1.28 billion third-party listed value exists while no public record of enforcing the rule has been located.\n\n$1.28B\nThird-party listed value · 38 platforms\n53.2M\nDisplayed offers · 38 third-party markets\n70.1K\nSteam items listed in the snapshot\n41×\nThird-party listed value vs Steam's $31M\nThe central finding\nOne infrastructure. Two economies.\n\nSteam controls the item, the inventory, and the trade. Every skin sold on any platform below must move through Steam's trade API — a structural dependence that is directly observable. Valve's own Community Market earns a fee on its sales; whether that fee funds, or is tied to, the third-party ecosystem is not established here.\n\nWhy this matters for the investigation\n1\nValve's Steam Subscriber Agreement prohibits commercial exploitation of Steam infrastructure without express permission. No such permission has been located in the public record for the platforms below.\n2\nSteam controls identity (OpenID), inventory state, and trade execution for the roughly $1.28B third-party listed value. No item transfer happens without Valve's infrastructure.\n3\nSteam's own marketplace has $31M listed — about 1/41 of the third-party listed value. The $1,800 price cap means sellers above it must go off-platform to sell at observed prices.\n4\n248 CS2 item categories, each priced above the cap by two or more marketplaces independently, cannot be sold at their observed market price on Steam — and none of them is listed there at all. The $1,800 cap creates the demand that third-party operators fill.\nSteam Community Market: $31MThird-party listed value: $1,276M\n$1,276M · third-party listed value — all dependent on Steam's trade API & OpenID\nSteam · $31M\n\nSource: PriceEmpire real-time catalogue, 20 September 2026. Listed value = sum of the rounded listed-value cards in the saved snapshot, Steam excluded. Not sales volume.\n\n38 active third-party markets · All depending on Steam infrastructure\nPlatform register\n\nThe platforms below route their logins through Steam OpenID and their trades through Steam's Web API. Each observed openid.realm passes through Steam's login flow; the register records the observed auth routes rather than asserting that any given operator lacks Valve's permission.\n\n#\tPlatform\tListed value\tActive offers\tItems\tScale\n1\tUUSkins\t$133.8M\t3.4M\t30.9K\t\n\n2\tYouPin898\t$127.5M\t5.9M\t29.2K\t\n\n3\tBuff.163\t$104M\t3.5M\t35K\t\n\n4\tMoon.Market\t$100.3M\t2.9M\t20.9K\t\n\n5\tWhite.Market\t$89.6M\t3M\t20.6K\t\n\n6\tBuff.Market\t$86.7M\t1.3M\t33.4K\t\n\n7\tEcosteam\t$82.1M\t3.3M\t30.1K\t\n\n8\tCSFloat\t$67.8M\t2.4M\t27.8K\t\n\n9\tSkin.Land\t$67.4M\t2.2M\t34.6K\t\n\n10\tLIS-SKINS\t$67.4M\t2.2M\t34.6K\t\n\n11\tC5Game\t$54.6M\t4.6M\t29.6K\t\n\n12\tHaloSkins\t$46.6M\t4.4M\t29.3K\t\n\n13\tAvan.Market\t$43.3M\t809.5K\t22.2K\t\n\n14\tWaxpeer\t$40.1M\t1M\t27.3K\t\n\n15\tSteam (official)\t$31M\t32.2M\t70.1K\t\n\n16\tCS.MONEY\t$29M\t748.9K\t28K\t\n\n17\tMarket.CSGO\t$26.3M\t1.3M\t27.6K\t\n\n18\tCS.MONEY Bot\t$25.7M\t614K\t23.8K\t\n\n19\tSkinport\t$16.3M\t3.8M\t31.1K\t\n\n20\tSkinFlow\t$14.1M\t481.8K\t23.6K\t\n\n21\tDMarket\t$12.6M\t948.2K\t35.6K\t\n\n22\tSkins.com\t$11.5M\t83.2K\t15.8K\t\n\n23\tSkin.place\t$6.9M\t380.8K\t11.4K\t\n\n24\tSkinsMonkey\t$6M\t109.4K\t11.6K\t\n\n25\tSkinBaron\t$5M\t2.1M\t21.5K\t\n\n26\tRustTM\t$3M\t33.1K\t4.9K\t\n\n27\tPirateSwap\t$2M\t859.3K\t10.5K\t\n\n28\tMannco.Store\t$1.2M\t223.7K\t11K\t\n\n29\tSkinSwap\t$1.1M\t11.4K\t4K\t\n\n30\tTradeIt\t$967.1K\t29.1K\t11.7K\t\n\n31\tLootFarm\t$896.1K\t162.5K\t28.6K\t\n\n32\tRustskins\t$714.8K\t312.5K\t6.1K\t\n\n33\tBalticSkins\t$599.2K\t28.2K\t4.5K\t\n\n34\tExeSkins\t$442.9K\t2.6K\t1.4K\t\n\n35\tRapidSkins\t$230.9K\t11.6K\t2.3K\t\n\n36\tCS.Trade\t$203K\t19K\t16.7K\t\n\n37\tKrakatoa\t$11.1K\t115\t53\t\n\n38\tShadowPay\t—\t—\t—\t—\n39\t49skins\t—\t—\t—\t—\nSteam's $1,800 price ceiling · five-marketplace snapshot · 23 September 2026\nThe price gap is measurable.\n\nSteam caps Community Market listings at approximately $1,800 (the finding is re-computed at $2,000, $2,070, $2,300 and $2,500 in cs2sh-atlas.json and holds at every threshold). Items observed above that price cannot be sold at their market price through Valve's own marketplace — but they still depend on Steam's inventory and transfer system wherever they are sold. Banding the whole catalogue by price shows where the wall stands: Valve's market carries 95.3% of the item categories priced below its cap and 1.9% of those above it.\n\nFive marketplaces: items above the Steam cap\n248\n\nItem categories whose cheapest ask clears $1,800 on two or more marketplaces independently, holding 18,394 listed copies worth at least $78.6M. Of those, 100.0% — every single one — have no Steam listing at all.\n\nFull exhibits: the register → · the price-ladder atlas →\n\nPrice distribution above cap\n$1,800–$5,000\n174\n$5,000–$10,000\n49\n$10,000–$25,000\n21\n$25,000–$50,000\n2\n$50,000+\n2\nTop items — cheapest corroborated ask across five marketplaces\n1Sticker | Titan (Holo) | Kat. '14$66,285\n2Sticker | iBUYPOWER (Holo) | Kat. '14$64,795\n3Sticker | Reason Gaming (Holo) | Kat. '14$42,899\n4★ Sport Gloves | Hedge Maze (FN)$26,812\n5Sticker | Team Dignitas (Holo) | Kat. '14$23,667\n6EMS Kat. '14 Legends$22,879\n7★ Sport Gloves | Pandora's Box (FN)$21,643\n8EMS Kat. '14 Challengers$21,010\n9Sticker | Vox Eminor (Holo) | Kat. '14$18,619\n10★ StatTrak™ Navaja Knife | Blue Steel (FN)$18,064\n\nAsking prices are not sale prices. Licensed cs2.sh snapshot, 23 September 2026. Every row is quoted above the cap by at least two marketplaces independently; single-shelf asks and quotes more than three times an item's cheapest ask are excluded. How the grading works →\n\nWhat Valve charges · licensed cs2.sh snapshot · 23 September 2026\nThe advertised fee is 15%. Most listings pay more.\n\nValve takes a 5% Steam fee and a 10% CS2 publisher fee from the seller's proceeds — the familiar 15%. Both fees carry a $0.01 minimum, so no sale can ever carry less than two cents in fees. On the cheap, high-volume items that make up the bulk of the market, that floor is the binding constraint, not the percentage. We solved the fee arithmetic for every one of the 29,635 item types carrying a live Steam ask.\n\n77.7%\nof live Steam listings sit on item types charged above 15%\n84.8%\nof item types do pay about the headline rate\n4,517\nitem types charged more than the advertised fee\n$0.02\nminimum fee on any sale, whatever the price\nThe two numbers point opposite ways, and both are true\n1\nCounted by item type, Valve's fee is broadly as advertised: 84.8% of the 29,635 priced types are charged at or near 15%.\n2\nCounted by actual listing, the picture inverts: 18,682,244 of 24,038,911 live listings are on item types charged more than 15%.\n3\nBoth are true because the overcharged types are the cheap, high-volume ones. 1,109 item types are charged more than double the headline rate, and those types alone carry 14,083,486 live listings.\n4\nThis is arithmetic, not an allegation. The minimum is disclosed in Valve's own fee documentation. What has not been published is how much of the market it actually applies to — which is what the figures above measure.\nFee charged, as a share of the headline 15%\n200%+\n14,083,486\n100-200%\n1,028,438\n50-100%\n700,804\n30-50%\n317,031\n20-30%\n2,258,254\n17.6-20%\n294,231\n\nBar length is the number of live listings in each band. A band of “200%+” means the fee taken is more than twice 15% of the seller's proceeds.\n\nA worked example\n67%\n\nOn a listing a buyer pays $0.03 for, the seller receives $0.01 and Valve takes $0.02 — the two one-cent minimums. As a share of what the buyer paid that is 67%; as a share of the seller's proceeds it is 200%.\n\nFull dataset: cs2sh-steam-fee-census.json →\n\nThe same item, inside the garden and outside it\nBuying on Steam costs more. Almost always.\n\nFor every item quoted both on Steam and on at least one third-party marketplace, we compared Steam's cheapest ask with the cheapest ask outside it. Across 28,700 items, Steam is the dearer venue 86.4% of the time, by a median of +35.7%.\n\nMedian Steam premium, by price band\nunder $0.50\n+48.3%\n$0.50-2\n+36.5%\n$2-10\n+29.6%\n$10-50\n+28.6%\n$50-250\n+36.3%\n$250-1k\n+51.1%\nover $1,000\n+67.9%\n\nThe curve is U-shaped. It is cheapest to buy on Steam in the $10–$50 band and dearest at the two ends.\n\nWhy the expensive end matters\n+67.9%\n\nAbove $1,000, the median Steam listing costs 67.9% more than the cheapest offer outside it — and only 1,040 such listings exist on Steam at all.\n\nPast roughly $1,800 the comparison stops being possible, because Valve's rule forbids the listing entirely. Steam's coverage of the items above its own cap is 1.9%. See the whole ladder →\n\nFull dataset: cs2sh-walled-garden-premium.json →\n\nA premium is not on its own a finding: Steam offers instant delivery and no counterparty risk, and buyers may reasonably pay for that. What is measurable is the size of the gap and the fact that the money crossing it cannot come back out — which is the next section.\n\nMoney in, no money out\n$128.1 million committed to orders that cannot be withdrawn.\n\nA Steam buy order is pre-funded: the money leaves the buyer's wallet the moment the order is placed. Steam wallet funds cannot be withdrawn — they can only be spent inside Steam. Summing every price level of every tracked item's buy book gives a census of committed, non-exitable money.\n\n$128.1M\ncommitted to standing Steam buy orders\n170.6M\nindividual funded buy orders standing\n$105.8M\nasking value of the listings facing them\n$15.9M\nValve's cut if every listing sold at its ask\nWhat this figure is, and what it is not\n1\nIt is real money already paid in. Every dollar counted has been debited from a wallet and is sitting against an open order across 31,253 item types.\n2\nIt is not revenue and not a claim about Valve's balance sheet. Where the float is held, and on whose books, is not established here.\n3\nIt is a snapshot, not a flow. Orders are cancellable by the buyer, which returns funds to the wallet — but still not out of Steam.\n4\nThe one-way door is the point. A marketplace whose currency cannot be cashed out is the reason a stolen inventory is converted off Steam rather than on it.\n\nMethod: every price level of every tracked buy book, multiplied by the orders standing at that level. Full dataset: cs2sh-steam-locked-capital.json →\n\nCompleted sales, not asking prices · one marketplace · trailing 90 days\n$30.9 million actually changed hands — on the smallest of the five shelves.\n\nA single high sale can be a rare craft or sticker-applied variant of a cheap base item (e.g. a $30 item with a one-off $9,772 completed sale). \"High\" = highest completed transaction, not the item's normal price.\n\nEvery other figure on this page measures what is listed. This one measures what was sold. Skinport publishes its own completed transactions, and over the trailing 90 days they came to 1,219,143 sales worth $30,927,032, at an average of $25.37 each.\n\n1.22M\ncompleted sales in 90 days, one marketplace\n$30.9M\nturnover over the same window\n$125M\nannualised run rate — a floor, not an estimate\n~2%\nSkinport's share of the above-cap shelf by listed value\nWhere the turnover came from\nunder $1\n0.5%\n$1-10\n5.8%\n$10-100\n22.2%\n$100-1k\n59.4%\n$1k-1.8k\n6.9%\nabove the Steam cap\n5.3%\n\nBar length is turnover; the figure is that tier's share of the total. 59.4% of the money moved in the $100–$1k tier, on 71,437 sales.\n\nAbove Valve's cap, sales still happen\n492\n\ncompleted sales of items priced above the Steam cap, worth $1,643,938, across 76 item types — on a marketplace that holds roughly 2% of that shelf. None of those sales could have taken place on Steam.\n\nFull dataset: cs2sh-offsteam-90d-dynamics.json → · the realised highs →\n\nSkinport is ONE of the third-party markets tracked here, and by listing value above the Steam cap it is the smallest of the five (about 2% of that shelf). Every total here is a floor on the off-Steam economy, not a measure of it. No Steam data is used.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Market Economics — Two Economies & The Listing Ceiling"
          },
          {
            "level": 2,
            "id": null,
            "text": "One infrastructure. Two economies."
          },
          {
            "level": 2,
            "id": null,
            "text": "Platform register"
          },
          {
            "level": 2,
            "id": null,
            "text": "The price gap is measurable."
          },
          {
            "level": 3,
            "id": null,
            "text": "Five marketplaces: items above the Steam cap"
          },
          {
            "level": 3,
            "id": null,
            "text": "Price distribution above cap"
          },
          {
            "level": 3,
            "id": null,
            "text": "Top items — cheapest corroborated ask across five marketplaces"
          },
          {
            "level": 2,
            "id": null,
            "text": "The advertised fee is 15%. Most listings pay more."
          },
          {
            "level": 3,
            "id": null,
            "text": "Fee charged, as a share of the headline 15%"
          },
          {
            "level": 3,
            "id": null,
            "text": "A worked example"
          },
          {
            "level": 2,
            "id": null,
            "text": "Buying on Steam costs more. Almost always."
          },
          {
            "level": 3,
            "id": null,
            "text": "Median Steam premium, by price band"
          },
          {
            "level": 3,
            "id": null,
            "text": "Why the expensive end matters"
          },
          {
            "level": 2,
            "id": null,
            "text": "$128.1 million committed to orders that cannot be withdrawn."
          },
          {
            "level": 2,
            "id": null,
            "text": "$30.9 million actually changed hands — on the smallest of the five shelves."
          },
          {
            "level": 3,
            "id": null,
            "text": "Where the turnover came from"
          },
          {
            "level": 3,
            "id": null,
            "text": "Above Valve's cap, sales still happen"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/de/market_economics.html",
          "https://phishdestroy.io/steam_dossier/de/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/de/elite_skins.html",
          "https://phishdestroy.io/steam_dossier/de/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/de/skin_atlas.html#grading",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-steam-fee-census.json",
          "https://phishdestroy.io/steam_dossier/de/skin_atlas.html#cliff",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-walled-garden-premium.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-steam-locked-capital.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-offsteam-90d-dynamics.json",
          "https://phishdestroy.io/steam_dossier/de/skin_atlas.html#highs"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/en/market_economics.content.json",
      "export_json_sha256": "0a4721d03b7372a707b05974fb31046cceb436bcaf5956525229ea9d0a6e021b"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "regulatory_act_print.html",
      "language": "en",
      "title": "FORENSIC AUDIT ACT: Valve Steam Web API Ecosystem & Commercial Exploitation (Ref: VAL-REG-2026-09)",
      "source_url": "https://phishdestroy.io/steam_dossier/regulatory_act_print",
      "source_html_sha256": "eb187c0cd41a7c65ee2d2a3578cb54fa5ba5744ac41444d2b70eb97f12452aed",
      "exported_at": "2026-09-29T00:15:55.773Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "regulatory_act_print.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/en/regulatory_act_print.pdf?v=print-20260929-v5",
        "sha256": "cb1d85edb711b92dfa3a4a541a5e9addc0e2aaa6c67a08dc83865f2117f67b7a",
        "bytes": 183662,
        "pages": 13
      },
      "integrity": {
        "signed_object": "regulatory_act_print.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "regulatory_act_print.content.json.asc",
        "digest_file": "regulatory_act_print.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify regulatory_act_print.content.json.asc regulatory_act_print.content.json",
          "sha256sum -c regulatory_act_print.content.json.sha256"
        ]
      },
      "content": {
        "text": "phishdestroy.io · Forensic Research Coalition · Universal Public Record\nDOCKET: VAL-REG-2026-09-EVID\nPROVENANCE: phishdestroy.io/steam_dossier/\nRIGHTS: ALL RIGHTS SURRENDERED TO HUMANITY\nForensic Audit Act & Regulatory Exhibit\nSystematic Third-Party API Provisioning, Automated Bypass Architecture & Contractual Non-Enforcement in the Valve Steam Ecosystem\nIssuing Domainphishdestroy.io\nTarget PlatformValve Steam / Steamworks\nPrimary Auth VectorSteam OpenID 2.0 / Web API\nLegal DedicationAll Rights to Humanity (CC0)\nSection I: Executive Memorandum & Factual FindingsREF: MEMO-SUMMARY-01\n\nThis document constitutes a formal forensic audit act examining the operational intersection between Valve Corporation's published commercial terms, its technical authentication endpoints, and observed third-party commercial platforms. The audit was conducted using passive, unauthenticated network observation, RDAP registration verification, and public Link Filter telemetry.\n\nFactual Core: Empirical observation establishes a systematic divergence between Valve's public contractual representations and its production infrastructure. While the Steam Subscriber Agreement (SSA) strictly prohibits unauthorized commercial exploitation (§ 2.G), automated bot/script interaction (§ 4.C), and account transfer (§ 1.C), Valve Corporation continues to provide live, programmatic OpenID authentication and inventory query infrastructure to at least 175 commercial entities generating multi-billion dollar secondary transaction volumes.\n\n175\nAudited Commercial Operators\n44\nSeparate-Domain Auth Hosts\n26\nFilter-Split Proxy Pairs\n100%\nUnenforced SSA § 2.G / § 4.C\n0\nEnforced Auth Revocations\nApplicable Contractual & Statutory Framework\nSSA § 2.G\nCommercial Use Prohibition: Expressly forbids exploiting Content and Services for commercial purposes without prior written authorization from Valve Corporation.\nSSA § 4.C\nAutomation Restriction: Strictly prohibits scripts, trading bots, macros, or non-human-controlled systems interacting with Steam services and markets.\nSSA § 1.C\nPersonal Use Mandate: Restricts accounts to personal use; expressly forbids selling, leasing, transferring, or trading Steam user accounts.\nEU DSA (2022/2065)\nSystemic Risk Assessment (Art. 34/35): Very Large Online Platforms (VLOPs) must actively detect, assess, and mitigate systemic risks stemming from automated misuse and unauthorized commercial exploitation.\nSection II: Exhibit Ledger A — Documented Link Filter Split Pairs (26 Routes)REF: EX-SPLIT-LEDGER\n\nForensic Analysis of Split-Domain Evasion: Under Valve's Steam Link Filter system (steamcommunity.com/linkfilter/?url=...), when an end-user clicks a link leading to a flagged gambling or black-market platform, Valve displays a prominent warning (\"Link Blocked! ... flagged as potentially malicious\"). However, forensic route tracing reveals 26 commercial platforms operating on a split-domain architecture: while the primary commercial domain is BLOCKED on the Link Filter, the secondary domain hosting Valve's OpenID return endpoint is marked CLEAN. Valve's OpenID servers accept authentication requests from these proxy hosts without interruption, neutralizing the consumer safety warning while continuing to process logins.\n\n#\tPrimary Commercial Domain\tMain Filter\tOpenID Auth Proxy Domain\tAuth Filter\tRDAP Registered\tCapture Basis\n01\trollbit.com\tBLOCKED\trbsnin.com\tCLEAN\t2026-09-18\tPASSIVE_CAPTURE\n02\tskin.club\tBLOCKED\tsc-auth.net\tCLEAN\t2019-04-02\tPASSIVE_CAPTURE\n03\thowl.gg\tBLOCKED\thowl.uno\tCLEAN\t2026-08-11\tPASSIVE_CAPTURE\n04\tduelbits.com\tBLOCKED\tswitchflips.com\tCLEAN\t2020-04-21\tPASSIVE_CAPTURE\n05\tcsgofast.com\tBLOCKED\tsteam-login.authtofast.com\tCLEAN\t2026-06-30\tPASSIVE_CAPTURE\n06\tfarmskins.com\tBLOCKED\tsteam.kobal.cc\tCLEAN\t2017-01-07\tPASSIVE_CAPTURE\n07\tcobaltlab.tech\tBLOCKED\tcobaltauth.com\tCLEAN\t2025-01-07\tPASSIVE_CAPTURE\n08\tcsgo.net\tBLOCKED\tcn2.easylot.net\tCLEAN\t2016-09-03\tPASSIVE_CAPTURE\n09\tggdrop.com\tBLOCKED\tggauth.com\tCLEAN\t2023-05-03\tPASSIVE_CAPTURE\n10\trustchance.com\tBLOCKED\thgfuihd.com\tCLEAN\t2019-01-27\tPASSIVE_CAPTURE\n11\tskin.fans\tBLOCKED\tauth.skinfans.com\tCLEAN\t2018-07-16\tPASSIVE_CAPTURE\n12\tskinport.com\tBLOCKED\tskinport.app\tCLEAN\t2020-06-20\tPASSIVE_CAPTURE\n13\tskins.cash\tBLOCKED\tskinscash.live\tCLEAN\t2019-12-05\tPASSIVE_CAPTURE\n14\ttf2hunt.com\tBLOCKED\trstspcl.com\tCLEAN\t2020-08-08\tPASSIVE_CAPTURE\n15\tdaddyskins.com\tBLOCKED\tgo-go-daddy.com\tCLEAN\t2019-01-26\tPASSIVE_CAPTURE\n16\tkey-drop.com\tBLOCKED\tkdauth.com\tCLEAN\t2026-05-13\tPASSIVE_CAPTURE\n17\tclash.gg\tBLOCKED\tclggauth.com\tCLEAN\t2024-09-16\tPASSIVE_CAPTURE\n18\tc5game.com\tBLOCKED\twww.imbastar.com\tCLEAN\t2016-02-27\tPASSIVE_CAPTURE\n19\tswap.gg\tBLOCKED\tswapauth.com\tCLEAN\t2018-10-06\tPASSIVE_CAPTURE\n20\tshadowpay.com\tBLOCKED\tthelogins.com\tCLEAN\t2018-01-22\tPASSIVE_CAPTURE\n21\tcsgocases.com\tBLOCKED\tlog-1n.com\tCLEAN\t2017-11-27\tPASSIVE_CAPTURE\n22\tcsgogem.com\tBLOCKED\tapi.csgem.com\tCLEAN\t2014-03-08\tPASSIVE_CAPTURE\n23\tgamdom.com\tBLOCKED\tlogin.gambldom.com\tCLEAN\t2017-09-24\tPASSIVE_CAPTURE\n24\t12cs.fail\tBLOCKED\tfail.games\tCLEAN\t2021-08-24\tPASSIVE_CAPTURE\n25\tskinsnipe.com\tBLOCKED\tpricing.tradeupspy.com\tCLEAN\t2020-03-11\tPASSIVE_CAPTURE\n26\tcsgobig.com\tBLOCKED\tletmeinbig.com\tCLEAN\t2023-01-20\tPASSIVE_CAPTURE\n\n* Note: Passive checks performed against unauthenticated Steam Link Filter endpoints on 2026-09-19 and 2026-09-21. Raw HTTP response bodies and SHA-256 digests preserved in repository dataset (steam_tos_assets/linkfilter-2026-09-22.json).\n\nSection III: Exhibit Ledger B — Comprehensive Census of 175 Audited Commercial EntitiesREF: EX-175-MASTER-CENSUS\n\nThe following register details all 175 third-party commercial platforms actively verified in the audit database. Each record indicates the entity name, primary commercial domain, observed Steam OpenID authentication route, activity classification, contractual breach mappings (SSA § 2.G, SSA § 4.C, SSA § 1.C), and the action field recorded in the source dataset. The label \"See dated evidence\" refers the reader to supporting records; it does not establish that Valve took no action. An absent action field is reported as not established.\n\nExhibit\tEntity Name & Main Domain\tObserved Auth Route / Proxy\tClassification\tContractual Breach\tValve Action\nEX-001\tCSGORoll\ncsgoroll.com\n\t\nwww.csgoroll.com\nDIRECT\n\tSkin Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-002\tCSGOEmpire\ncsgoempire.com\n\t\ncsgoempirelogin4.com\nSPLIT PROXY\n\tCasino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-003\tRollbit\nrollbit.com\n\t\nrbsnin.com\nSPLIT PROXY\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-004\t500 Casino\n500.casino\n\t\nfivezerozero.co\nSPLIT PROXY\n\tLicenced Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-005\tCSGOBig\ncsgobig.com\n\t\ncsgobig.com\nDIRECT\n\tRoulette/Slots\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-006\tCaseDrop\ncasedrop.com\n\t\ncasedrop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-007\tRustReaper\nrustreaper.com\n\t\nrustreaper.com\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-008\tBanditCamp\nbanditcamp.com\n\t\nbanditcamp.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-009\tSkinBox\nskinbox.com\n\t\nskinbox.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-010\tTastyDrop\ntastydrop.com\n\t\ntastydrop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-011\tCSGOPolygon\ncsgopolygon.gg\n\t\ncsgopolygon.gg\nDIRECT\n\tRoulette Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-012\tMagicDrop\nmagicdrop.ru\n\t\nmagicdrop.ru\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-013\tCSDice\ncsdice.com\n\t\ncsdice.com\nDIRECT\n\tDice Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-014\tRustly\nrustly.com\n\t\nrustly.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-015\tSkinOdds\nskinodds.com\n\t\nskinodds.com\nDIRECT\n\tUpgrader Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-016\tCSGOWin\ncsgowin.com\n\t\ncsgowin.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-017\tCSGORun\ncsgorun.net\n\t\ncsgorun.net\nDIRECT\n\tCrash Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-018\tOpenSkins\nopenskins.com\n\t\nopenskins.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-019\tRustBet\nrustbet.com\n\t\nrustbet.com\nDIRECT\n\tRust Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-020\tCSGOMagic\ncsgomagic.com\n\t\ncsgomagic.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-021\tCSGOBounty\ncsgobounty.com\n\t\ncsgobounty.com\nDIRECT\n\tUpgrader/Contract\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-022\tEZSkins\nezskins.com\n\t\nezskins.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-023\tRustCases\nrustcases.com\n\t\nrustcases.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-024\tCSGOReaper\ncsgoreaper.com\n\t\ncsgoreaper.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-025\tCSGOCases\ncsgocases.com\n\t\ncsgocases.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-026\tCSGO-Skins\ncsgo-skins.com\n\t\ncsgo-skins.com\nDIRECT\n\tCase Upgrader\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-027\tCSGONet\ncsgonet.com\n\t\ncsgonet.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-028\tWTFSkins\nwtfskins.com\n\t\nwtfskins.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-029\tCSGOFast\ncsgofast.com\n\t\nsteam-login.authtofast.com\nSPLIT PROXY\n\tRoulette Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-030\tDuelbits\nduelbits.com\n\t\nswitchflips.com\nSPLIT PROXY\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-031\tFlameCases\nflamecases.com\n\t\nflamecases.com\nDIRECT\n\tCase Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-032\tFarmskins\nfarmskins.com\n\t\nsteam.kobal.cc\nSPLIT PROXY\n\tCase Opener\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-033\tCSGOLuck\ncsgoluck.com\n\t\ncsgoluck.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-034\tGamedom\ngamedom.com\n\t\ngamedom.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-035\tSkin.Club\nskin.club\n\t\nsc-auth.net\nSPLIT PROXY\n\tCase Battles\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-036\tDaddySkins\ndaddyskins.com\n\t\ndaddyskins.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-037\tInsane.gg\ninsane.gg\n\t\napi.insane.gg\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-038\tRustix\nrustix.gg\n\t\nrustix.gg\nDIRECT\n\tRust Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-039\tSkins.Club\nskins.club\n\t\nskins.club\nDIRECT\n\tSkin Upgrade\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-040\tCSGOHouse\ncsgohouse.org\n\t\ncsgohouse.org\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-041\tSkinRave\nskinrave.net\n\t\nskinrave.net\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-042\tBloodyCase_GG\nbloodycase.gg\n\t\nbloodycase.gg\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-043\tCSGOClicker\ncsgoclicker.com\n\t\ncsgoclicker.com\nDIRECT\n\tClicker/Upgrade\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-044\tRustBet_GG\nrustbet.gg\n\t\nrustbet.gg\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-045\tCS_Drop\ncs-drop.com\n\t\ncs-drop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-046\tHellStore\nhellstore.net\n\t\nhellstore.net\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-047\tRustLoot\nrustloot.com\n\t\nrustloot.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-048\tCSGO_Case\ncsgo-case.com\n\t\ncsgo-case.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-049\tCS2Skin\ncs2skin.com\n\t\ncs2skin.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-050\tJuice_GG\njuice.gg\n\t\nletmeinjuice.com\nSPLIT PROXY\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-051\tGGDrop\nggdrop.com\n\t\nggauth.com\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-052\tCSGOGem\ncsgogem.com\n\t\ncsgogem.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-053\tRainbet\nrainbet.com\n\t\nservices.rainbet.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-054\tHowl_GG\nhowl.gg\n\t\nhowl.uno\nSPLIT PROXY\n\tSkins Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-055\tChicken_GG\nchicken.gg\n\t\nchicken.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-056\tCSGOCasino_GG\ncsgocasino.gg\n\t\napi.csgocasino.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-057\tHunt_GG\nhunt.gg\n\t\napi.hunt.gg\nDIRECT\n\tSkins Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-058\tCSBattle\ncsbattle.com\n\t\ncsbattle.com\nDIRECT\n\tCase Battles\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-059\tSkinRave_GG\nskinrave.gg\n\t\napi.skinrave.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-060\tCSDouble\ncsdouble.gg\n\t\ncsdouble.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-061\tRustChance\nrustchance.com\n\t\nhgfuihd.com\nSPLIT PROXY\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-062\tRustClash\nrustclash.com\n\t\nrustclash.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-063\tCobaltLab\ncobaltlab.tech\n\t\ncobaltauth.com\nSPLIT PROXY\n\tRust Automation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-064\tRaided_GG\nraided.gg\n\t\napi.raided.gg\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-065\tRustNeo\nrustneo.gg\n\t\nrustneo.gg\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-066\tSplits_GG\nsplits.gg\n\t\nsplits.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-067\tUpgrader_Pro\nupgrader.pro\n\t\nupgauth.space\nSPLIT PROXY\n\tSkin Upgrader\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-068\tSkinFans\nskin.fans\n\t\nauth.skinfans.com\nSPLIT PROXY\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-069\tHotPizza\nhotpizza.one\n\t\nhotpizza.one\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-070\tG4Skins\ng4skins.com\n\t\nauth.g4s.to\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-071\t12CS_Fail\n12cs.fail\n\t\n12cs.fail\nDIRECT\n\tCrash Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-072\tTF2Royal\ntf2royal.com\n\t\ntf2auth.com\nSPLIT PROXY\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-073\tTF2Easy\nwww.tf2easy.com\n\t\nwww.tf2easy.com\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-074\tTF2Hunt\ntf2hunt.com\n\t\nrstspcl.com\nSPLIT PROXY\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-075\tTF2Bet\ntf2.bet/coinflip\n\t\ntf2.bet\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-076\tTF2Blaze\ntf2blaze.com\n\t\ntf2blaze.com\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-077\tOpenStars_GG\nopenstars.gg\n\t\nopenstars.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-078\tShuffle_Com\nshuffle.com\n\t\nshuffle.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-079\tSkins.com\nskins.com\n\t\napi.skins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-080\tWhite.Market\nwhite.market\n\t\nwhite.market\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-081\tBuff.Market\nbuff.market\n\t\nbuff.market\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-082\tAvan.Market\navan.market\n\t\navan.market\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-083\tCS.MONEY\ncs.money\n\t\nauth.dota.trade\nSPLIT PROXY\n\tTrading Engine\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-084\tUUSkins\nuuskins.com\n\t\nuuskins.com\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-085\tYouPin898\nyoupin898.com\n\t\nyoupin898.com\nDIRECT\n\tMass Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-086\tMoon.Market\nmoon.market\n\t\nmoon.market\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-087\tCSFloat\ncsfloat.com\n\t\ncsgofloat.com\nSPLIT PROXY\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-088\tSkin.Land\nskin.land\n\t\nauth.skin.land\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-089\tC5Game\nc5game.com\n\t\nc5game.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-090\tHaloSkins\nhaloskins.com\n\t\nhaloskins.com\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-091\tBuff.163\nbuff.163.com\n\t\nbuff.163.com\nDIRECT\n\tCorporate Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-092\tWaxpeer\nwaxpeer.com\n\t\nwaxpeer.com\nDIRECT\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-093\tCS.MONEY Bot\ncs.money\n\t\nauth.dota.trade\nSPLIT PROXY\n\tBot Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-094\tMarket.CSGO\nmarket.csgo.com\n\t\ndota2.net\nSPLIT PROXY\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-095\tSkinport\nskinport.com\n\t\nskinport.app\nSPLIT PROXY\n\tRegulated Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-096\tSkinFlow\nskinflow.gg\n\t\napi.skinflow.gg\nDIRECT\n\tMarketplace/Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-097\tDMarket\ndmarket.com\n\t\ndmarket.com\nDIRECT\n\tUS Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-098\tSkin.place\nskin.place\n\t\napi.skin.place\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-099\tSkinsMonkey\nskinsmonkey.com\n\t\nskinsmonkey.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-100\tSkinBaron\nskinbaron.de\n\t\nskinbaron.com\nSPLIT PROXY\n\tCorporate Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-101\tSteam\nsteamcommunity.com/market\n\t\nsteamcommunity.com/market\nDIRECT\n\tOfficial Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-102\tRustTM\nrust.tm\n\t\ndota2.net\nSPLIT PROXY\n\tRust Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-103\tPirateSwap\npirateswap.com\n\t\nlogin.pirateswap.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-104\tMannco.Store\nmannco.store\n\t\nmannco.store\nDIRECT\n\tTF2 Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-105\tSkinSwap\nskinswap.com\n\t\napi.skinswap.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-106\tLootFarm\nlootfarm.com\n\t\nlootfarm.com\nDIRECT\n\tTrading Platform\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-107\tRustskins\nrustskins.com\n\t\nrustskins.com\nDIRECT\n\tRust Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-108\tExeSkins\nexeskins.com\n\t\nexeskins.com\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-109\tBalticSkins\nbalticskins.com\n\t\nbalticskins.com\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-110\tCS.Trade\ncs.trade\n\t\ncs.trade\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-111\tRapidSkins\nrapidskins.com\n\t\napi.rapidskins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-112\tTradeIt\ntradeit.gg\n\t\nconnect-tradeit.com\nSPLIT PROXY\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-113\tKrakatoa\nkrakatoa.com\n\t\nkrakatoa.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-114\tShadowPay\nshadowpay.com\n\t\nshadowpay.com\nDIRECT\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-115\t49skins\n49skins.com\n\t\napi.49skins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-116\tSkinVault\nskinvault.gg\n\t\napi.skinvault.gg\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-117\tAim Market\naim.market\n\t\naim.market\nDIRECT\n\tSkins Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-118\tSkinout\nskinout.gg\n\t\nauth.skinout.gg\nDIRECT\n\tInstant Sell Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-119\tNTSkins\nntskins.com\n\t\nntskins.com\nDIRECT\n\tSkins Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-120\tIGXE\nigxe.cn\n\t\nigxe.cn\nDIRECT\n\tChinese Powerhouse\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-121\tSwap.gg\nswap.gg\n\t\nswap.gg\nDIRECT\n\tAutomated Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-122\tBitskins\nbitskins.com\n\t\nbitskins.com\nDIRECT\n\tCash-out Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-123\tGamerPay\ngamerpay.gg\n\t\ngamerpay.gg\nDIRECT\n\tP2P Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-124\tTF2Mart\ntf2mart.com\n\t\ntf2mart.com\nDIRECT\n\tTF2 Automation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-125\tSkinBid\nskinbid.com\n\t\nskinbid.com\nDIRECT\n\tSkin Auctions\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-126\tLootBear\nlootbear.com\n\t\nlootbear.com\nDIRECT\n\tSkin Rental\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-127\tBackpack.tf\nbackpack.tf\n\t\nbackpack.tf\nDIRECT\n\tTF2 Valuation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-128\tScrap.tf\nscrap.tf\n\t\nscrap.tf\nDIRECT\n\tTF2 Scrap Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-129\tMarketplace.tf\nmarketplace.tf\n\t\nmarketplace.tf\nDIRECT\n\tTF2 Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-130\tSTNTrading\nstntrading.eu\n\t\nstntrading.eu\nDIRECT\n\tTF2 Botnet\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-131\tSkins.Cash\nskins.cash\n\t\nskinscash.live\nSPLIT PROXY\n\tInstant Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-132\tSkinWallet\nskinwallet.com\n\t\nskinwallet.com\nDIRECT\n\tInstant Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-133\tDota2Market\ndota2market.com\n\t\ndota2market.com\nDIRECT\n\tDota 2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-134\tCSGO.NET\ncsgo.net\n\t\ncn2.easylot.net\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-135\tCybershoke\ncybershoke.net\n\t\nauth.cybershoke.net\nDIRECT\n\tCommunity Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-136\tXPlay_GG\nxplay.gg\n\t\nxplay.gg\nDIRECT\n\tServer Network\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-137\tFastCup\nfastcup.net\n\t\napi.fastcup.net\nDIRECT\n\tMatchmaker Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-138\tEsportal\nesportal.com\n\t\nesportal.com\nDIRECT\n\tMatchmaking Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-139\tGamersClub\ngamersclub.com.br\n\t\ngamersclub.com.br\nDIRECT\n\tLATAM Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-140\tLeetify\nleetify.com\n\t\nleetify.com\nDIRECT\n\tSaaS Analytics\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-141\tScope_GG\nscope.gg\n\t\nscope.gg\nDIRECT\n\tSaaS Analytics\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-142\tTradeUpSpy\ntradeupspy.com\n\t\napi.tradeupspy.com\nDIRECT\n\tSaaS Tools\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-143\tEpidemic_GG\nepidemic.gg\n\t\nepidemic.gg\nDIRECT\n\tSaaS Tools\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-144\tCSDeals\ncs.deals\n\t\napi.cs.deals\nDIRECT\n\tMarketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-145\tPricempire\npricempire.com\n\t\npricempire.com\nDIRECT\n\tSaaS Price DB\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-146\tCS2Stash\ncs2stash.com\n\t\ncs2stash.com\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-147\tCSGOSkins\ncsgoskins.gg\n\t\ncsgoskins.gg\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-148\tSteamAnalyst\nsteamanalyst.com\n\t\nsteamanalyst.com\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-149\tSteamCardExchange\nsteamcardexchange.net\n\t\nsteamcardexchange.net\nDIRECT\n\tTrading Exchange\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-150\tDotaBuff\ndotabuff.com\n\t\ndotabuff.com\nDIRECT\n\tSaaS Tracker\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-151\tTracker_GG\ntracker.gg\n\t\ntracker.gg\nDIRECT\n\tSaaS Tracker\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-152\tFSB Market (an anonymized label; the original name is withheld here)\nFSB Market\n\t\nFSB Market\nDIRECT\n\tMass Blackmarket\tSSA § 2.G, SSA § 4.C, SSA § 1.C\tSee dated evidence\nEX-153\tFunPay\nfunpay.com\n\t\nfunpay.com\nDIRECT\n\tAccount Exchange\tSSA § 2.G, SSA § 4.C, SSA § 1.C\tSee dated evidence\nEX-154\tPlayerAuctions\nplayerauctions.com\n\t\nplayerauctions.com\nDIRECT\n\tGrey Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-155\tEldorado.gg\neldorado.gg\n\t\neldorado.gg\nDIRECT\n\tAccount Portal\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-156\tG2A\ng2a.com\n\t\ng2a.com\nDIRECT\n\tMass Key Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-157\tKinguin\nkinguin.net\n\t\nkinguin.net\nDIRECT\n\tMass Key Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-158\tG2G.com\ng2g.com\n\t\ng2g.com\nDIRECT\n\tVirtual Services\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-159\tPlayerup\nplayerup.com\n\t\nplayerup.com\nDIRECT\n\tAccount Broker\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-160\tZ2U.com\nz2u.com\n\t\nwww.z2u.com\nDIRECT\n\tReady-Account Hub\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-161\tSmurfHub\nsmurfhub.net\n\t\nsmurfhub.net\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-162\tSmurfAccounts\nsmurfaccounts.com\n\t\nsmurfaccounts.com\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-163\tBuyCSGORank\nbuycsgorank.com\n\t\nbuycsgorank.com\nDIRECT\n\tRank Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-164\tCSGOSmurfKings\ncsgosmurfkings.com\n\t\ncsgosmurfkings.com\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-165\tSmurfStore_Co\nsmurfstore.co\n\t\nsmurfstore.co\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-166\tSteamLvlUp\nsteamlvlup.com\n\t\nsteamlvlup.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-167\tSteamLevels\nsteamlevels.com\n\t\nsteamlevels.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-168\tLevelSteam\nlevelsteam.com\n\t\nlevelsteam.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-169\tSteamLevelU\nsteamlevelu.com\n\t\nsteamlevelu.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-170\tEloKing\neloking.com\n\t\neloking.com\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-171\tBoosteria\nboosteria.org\n\t\nboosteria.org\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-172\tOvergear\novergear.com\n\t\novergear.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-173\tBlazingBoost\nblazingboost.com\n\t\nblazingboost.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-174\tDota2Boost\ndota2boost.com\n\t\ndota2boost.com\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-175\tBuyBoost\nbuyboost.com\n\t\nbuyboost.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nSection IV: Technical Architecture & Authentication MechanicsREF: TECH-ANALYSIS-01\n\n1. Absence of Domain Ownership Validation in OpenID 2.0: Valve's implementation of the OpenID 2.0 protocol (https://steamcommunity.com/openid/login) evaluates the openid.return_to and openid.realm parameters without requiring prior developer registration, cryptographic challenge verification, or domain ownership validation. Any commercial operator can direct users to Valve's login screen and receive a cryptographically signed identity assertion (containing the 64-bit SteamID) redirected to arbitrary domains.\n\n2. Programmatic Inventory Querying & API Key Abuse: Once user authentication is confirmed via OpenID, operators query public and partner Web API endpoints (IEconItems_730/GetPlayerItems) to index inventory assets in real-time. Automated trading networks employ programmatic session tokens to submit, poll, and accept peer-to-peer (P2P) trade offers, directly contravening SSA § 4.C's prohibition on non-human interaction.\n\n3. Link Filter Asymmetry: The coexistence of consumer-facing domain warnings alongside fully functional authentication endpoints creates a regulatory contradiction: Valve's security telemetry classifies these operators as \"potentially malicious\", yet Valve's authentication infrastructure continues to authenticate their user base.\n\nEvidentiary Methodology & Chain of Custody Declaration\n\nThis document was generated from unauthenticated network captures, historical RDAP registry queries, and verified cryptographic hash manifests. No user login credentials were compromise-tested or processed. All findings reflect observable production network state as of September 2026. This act serves as a non-partisan technical exhibit prepared for judicial, regulatory, and public inquiries.\n\nDIGEST: SHA-256 VERIFIED\nc507c9025f93da0aadaf395c4d8882f25973211c318ee8e9b6f18a5b3755e050\nARCHIVE: OPEN LEGAL RECORD\nISSUED & SIGNED BY: phishdestroy.io · Forensic Research Coalition\nLEGAL STATUS: ALL RIGHTS SURRENDERED TO HUMANITY · CC0 UNIVERSAL PUBLIC DOMAIN",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Forensic Audit Act & Regulatory Exhibit"
          }
        ],
        "links": []
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/en/regulatory_act_print.content.json",
      "export_json_sha256": "d9686fe042ded21d08ade2416fbfb4853e661a7241d55d8ffdafb164ec62d1b0"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "security_timeline.html",
      "language": "en",
      "title": "Security Timeline — The Steam Dossier",
      "source_url": "https://phishdestroy.io/steam_dossier/security_timeline",
      "source_html_sha256": "74e91558539f91c84bc5958e5a12b7433b201d3abc5a76bade50787279c26322",
      "exported_at": "2026-09-29T00:15:56.060Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "security_timeline.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/en/security_timeline.pdf?v=print-20260929-v5",
        "sha256": "2be80efee545209070eecc8b98c4fa54b9840e6bdd0a8b525e640f9d13766fd6",
        "bytes": 91377,
        "pages": 6
      },
      "integrity": {
        "signed_object": "security_timeline.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "security_timeline.content.json.asc",
        "digest_file": "security_timeline.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify security_timeline.content.json.asc security_timeline.content.json",
          "sha256sum -c security_timeline.content.json.sha256"
        ]
      },
      "content": {
        "text": "Dieses Material ist auf Englisch verfügbar.Zurück zum Dossier · Deutsch ↗\nTHE SECURITY RECORDEXHIBIT / 16 ENTRIES\n\n2018 — 2026\n\nSecurity Timeline — 2018 to 2026\n\nSecurity changed. Follow the record.\n\nWHAT THIS SECTION PROVES\n\nThis chronological record reconstructs eight years of security modifications across Steam's trade and authentication stack. It tracks the 2018 7-day trade hold implementation, 2023 Web API key mobile confirmations, and the 2026 session token deprecations against documented bypass techniques. The timeline establishes that platform updates consistently lagged known exploit vectors while preserving structural advantages for commercial operators.\n\n← Back to Executive briefing\n\nTrade locks. Login controls. API restrictions. A dated record of what changed—and what the sources actually establish.\n\nExplore the timeline ↓\nEIGHT YEARS. ONE RECORD.16milestones to examine\n\nEvery entry keeps its submitted date and source. Verification is shown alongside it.\n\nREVIEWED / 24 SEP 2026\n10Verified event & date\n06Partly verified\n00Source mismatch\n00Source needed\nHow to read this record\n\nVerified event & date: both supported by a readable primary source. Partly verified: a related change is documented, but the date or scope remains unresolved. Source mismatch: the linked material does not support the submitted claim. Source needed: no matching dated source was verified in this review. An unresolved entry is not proof that an event did not happen.\n\nDates on unresolved entries are submitted dates, not verified release dates. The original investigation text has not been rewritten.\n\nThe chronology\n01 — 16\nSearch the recordTopicEvidenceOrder\n\n16 of 16 entries · newest first\n\n202609-01Submitted date\nCommunityPartly verified\nSuspicious-message warnings in group chats\n\nAn official beta notice confirms the feature on 31 August. The supplied 1 September stable-release date still needs its specific release note.\n\nSteam Client Beta — August 31st ↗archived 2026-03-13 ↗\nOriginal entry & submitted link\n\nAutomated Suspicious Chat Flagging\n\nInspect the submitted source ↗\n202601-16Verified date\nAPIVerified event & date\nGranular permissions & IP whitelisting for Publisher Keys (Valve announcement)\n\nOn 16 January 2026, Valve published an official Steamworks announcement (\"NEW: Better permissions and controls for Web API Keys\") confirming new granular permission tools allowing developers to segment Web API keys into discrete groups (General, Microtransactions, Economy, and Sales Data), restrict keys to specific App IDs, and enforce server IP whitelisting.\n\nThe Glaring Double Standard: This official announcement establishes that Valve has fully developed the technical infrastructure for granular API permissions and IP restrictions, but deliberately withholds them from regular user accounts (steamcommunity.com/dev/apikey). Regular user API keys remain monolithic, all-or-nothing credentials with no IP whitelisting—which is the exact technical omission enabling the multi-million-dollar API trade interception industry.\n\nValve Announcement — NEW: Better permissions and controls for Web API Keys (16 Jan 2026) ↗· Documentation: Steamworks Web API Authentication ↗\nOriginal entry & submitted link\n\nSteamworks Web API Granular Scopes\n\nInspect Valve's Official Steamworks Announcement (493839547938902179) ↗\n202507-15Verified date\nTradingVerified event & date\nCS2 trades gain a seven-day reversal window\n\nValve's dated announcement introduces reversal of Counter-Strike item trades from the preceding seven days. While designed to mitigate hijacking, third-party economic audits (CSMarketCap ↗) recorded a $104M (-25%) collapse in market capitalization within 24 hours due to cash-trading disruption. As analyzed by Skinvault ↗, triggering a reversal inflicts an automatic 30-day trade lockout on the account. In summer 2026, Valve shifted from global midnight UTC resets to individual per-item minute timers (Skin.land ↗).\n\nValve — 15 July 2025 announcement ↗· CSMarketCap Analysis ↗\nOriginal entry & submitted link\n\nCS2 Trade Protection / Reversal Window\n\nInspect the submitted source ↗\n202505-14Verified date\nAuthenticationVerified event & date\nValve publishes account security warning regarding SMS leaks\n\nValve's official announcement on May 14, 2025, addresses account security and SMS-based authenticators. While the notice focuses on SMS leaks and confirms no Steam systems were breached, it serves as an official security update on the submitted date.\n\nValve — A note about the security of your Steam account ↗\nOriginal entry & submitted link\n\nAccount Security Announcement\n\nInspect the submitted source ↗\n202410-02Verified date\nTradingVerified event & date\nSeven days before re-trading or re-marketing\n\nThe release notes cover items acquired through the in-game store, including the Armory, trade offers and the Community Market. The documented scope is wider than Armory items alone.\n\nValve — Release Notes for 10/2/2024 ↗\nOriginal entry & submitted link\n\nCS2 The Armory / 7-Day Hold\n\nInspect the submitted source ↗\n202409-18Submitted date\nTradingPartly verified\nNew-device restrictions verified on Help Pages\n\nSteam's official support documentation confirms a 7-day trading restriction when logging in from a new device that has not been authorized for at least 7 days. While the exact rollout date of September 18, 2024, is not recorded as a changelog milestone, the functionality is fully documented.\n\nSteam Support — Trading and Market Restrictions ↗\nOriginal entry & submitted link\n\nNew Device Login Trade Restriction\n\nInspect the submitted source ↗\n202402-14Submitted date\nCommunityPartly verified\nName-change trade cooldown implemented in 2024\n\nCommunity and developer records confirm that in early 2024, Valve introduced an unannounced 2-to-4 hour trade cooldown immediately following a profile name change to mitigate rapid impersonation scams. Because Valve published no official press release, client changelog, or support article for this restriction, the submitted February 14 date lacks formal verification; the Steam Workshop guide serves as indirect community corroboration rather than official Valve documentation.\n\nSteam Workshop Guide (indirect corroboration) — Name-change restriction detail ↗\nOriginal entry & submitted link\n\nProfile Name / Avatar Change Hold\n\nInspect the submitted source ↗\n202312-04Verified date\nAPIVerified event & date\nKey creation requires mobile confirmation\n\nThe introduction of mandatory Steam Guard mobile confirmation for Web API key creation is verified to have occurred in late 2023, as documented by third-party developer libraries. The exact date of December 4, 2023, represents the observed rollout period within the developer community.\n\nMaintainer documentation — March 2024 ↗archived 2026-09-24 ↗\nOriginal entry & submitted link\n\nMobile Confirmation for API Keys\n\nInspect the submitted source ↗\n202310-24Verified date\nDeveloperVerified event & date\nMandatory 2FA for setting game builds live goes effective\n\nValve's official Steamworks announcement on October 10, 2023, confirms that starting October 24, 2023, any account setting a build live on the default branch of a released application must authorize the change via SMS or the Steam Mobile App. This change directly updated the SetAppBuildLive Web API.\n\nSteamworks — Security improvements for managing builds and users ↗archived 2025-12-03 ↗\nOriginal entry & submitted link\n\nSMS MFA for Game Build Publications\n\nInspect the submitted source ↗\n202307-12Submitted date\nCommunityPartly verified\nCustom biography content warnings observed by community\n\nSteam community reports starting in July 2023 document that custom profile biographies containing external links or trigger words began displaying automated content warnings. The submitted date of July 12, 2023, matches the initial wave of user reports on Steam Community forums.\n\nSteam Community Forum — Bio Content Warning Reports ↗\nOriginal entry & submitted link\n\nCustom Biography Content Warning\n\nInspect the submitted source ↗\n202301-25Submitted date\nCommunityPartly verified\nProfile link filtering and editing cooldowns active\n\nSteam's official support documentation confirms that links in custom biographies are filtered, and abusive name or avatar changes can trigger editing bans. While the exact rollout of the 4-hour cooldown on January 25, 2023, represents the observed onset, the link-filtering mechanism itself is fully active on the submitted help page.\n\nSteam Support — Profile Name and Avatar Restrictions ↗\nOriginal entry & submitted link\n\nProfile LINK REMOVED / Cooldown\n\nInspect the submitted source ↗\n202210-24Verified date\nAuthenticationVerified event & date\nSteam Client transition to OAuth refresh and access tokens\n\nValve's major client and mobile app updates in October 2022 overhauled the Steam authentication system. The old session cookie structure was replaced with OAuth-based access and refresh tokens, and a list of active authorized devices was introduced to allow manual revocation of active sessions.\n\nValve — Steam Mobile App Update and Authentication Overhaul ↗\nOriginal entry & submitted link\n\nSteam Login Overhaul / Cookie Truncation\n\nInspect Valve Announcement ↗\n202210-12Verified date\nAuthenticationVerified event & date\nQR sign-in and authorized-device management\n\nValve's 12 October announcement describes QR sign-in, approval or denial of sign-ins, and a device list that can revoke account access.\n\nValve — The updated Steam Mobile App is now available ↗\nOriginal entry & submitted link\n\nSteam Mobile App 3.0 / QR Login\n\nInspect the submitted source ↗\n202205-10Submitted date\nAPIPartly verified\nTrade cancellation endpoints removed from public API list\n\nDeveloper records confirm that in May 2022, Valve silently removed trade management endpoints such as IEconService/CancelTradeOffer and DeclineTradeOffer from the Web API (documented in node-steam-tradeoffer-manager #325). While the methods remain functional in private client protocols, the date of May 10, 2022, represents their observed removal from public Web APIs to combat scam panels.\n\nDeveloper Discussion — Issue #325 (CancelTradeOffer removed) ↗· Steamworks Web API — IEconService Documentation ↗\nOriginal entry & submitted link\n\nRemoval of Trade Cancellation Endpoints\n\nInspect node-steam-tradeoffer-manager Issue #325 ↗\n202005-25Verified date\nTradingVerified event & date\nDota 2 items receive a seven-day trading cooldown\n\nOn May 25, 2020, alongside the International 10 Battle Pass release (blog.dota2.com/2020/05/the-international-10-battle-pass/), Valve implemented a 7-day trade lock on Dota 2 items, matching the 2018 Counter-Strike policy. This restriction applies to all traded items and Market purchases.\n\nDota 2 Community — Trade Lock and TI10 Client Update ↗\nOriginal entry & submitted link\n\nDota 2 / 7-Day Trade Lock\n\nInspect the submitted source ↗\n201803-29Verified date\nTradingVerified event & date\nTraded CS:GO items receive a seven-day cooldown\n\nThe official release notes confirm the date and restriction. The supplied URL redirected to a 2013 map update; the matching release-note URL ends in 20309.\n\nValve — Release Notes for 3/29/2018 ↗\nOriginal entry & submitted link\n\nCS:GO / 7-Day Trade Lock\n\nInspect the submitted source ↗ archived 2025-02-26 ↗\n\nFollow the evidence. Inspect the source.\n\nReturn to the investigation ↗",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Security Timeline — 2018 to 2026"
          },
          {
            "level": 2,
            "id": null,
            "text": "The chronology"
          },
          {
            "level": 2,
            "id": null,
            "text": "Suspicious-message warnings in group chats"
          },
          {
            "level": 2,
            "id": null,
            "text": "Granular permissions & IP whitelisting for Publisher Keys (Valve announcement)"
          },
          {
            "level": 2,
            "id": null,
            "text": "CS2 trades gain a seven-day reversal window"
          },
          {
            "level": 2,
            "id": null,
            "text": "Valve publishes account security warning regarding SMS leaks"
          },
          {
            "level": 2,
            "id": null,
            "text": "Seven days before re-trading or re-marketing"
          },
          {
            "level": 2,
            "id": null,
            "text": "New-device restrictions verified on Help Pages"
          },
          {
            "level": 2,
            "id": null,
            "text": "Name-change trade cooldown implemented in 2024"
          },
          {
            "level": 2,
            "id": null,
            "text": "Key creation requires mobile confirmation"
          },
          {
            "level": 2,
            "id": null,
            "text": "Mandatory 2FA for setting game builds live goes effective"
          },
          {
            "level": 2,
            "id": null,
            "text": "Custom biography content warnings observed by community"
          },
          {
            "level": 2,
            "id": null,
            "text": "Profile link filtering and editing cooldowns active"
          },
          {
            "level": 2,
            "id": null,
            "text": "Steam Client transition to OAuth refresh and access tokens"
          },
          {
            "level": 2,
            "id": null,
            "text": "QR sign-in and authorized-device management"
          },
          {
            "level": 2,
            "id": null,
            "text": "Trade cancellation endpoints removed from public API list"
          },
          {
            "level": 2,
            "id": null,
            "text": "Dota 2 items receive a seven-day trading cooldown"
          },
          {
            "level": 2,
            "id": null,
            "text": "Traded CS:GO items receive a seven-day cooldown"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/de/security_timeline.html",
          "https://phishdestroy.io/steam_dossier/de/#briefing-heading",
          "https://steamcommunity.com/groups/SteamClientBeta?l=english",
          "http://web.archive.org/web/20260313235409/https://steamcommunity.com/groups/SteamClientBeta?l=english",
          "https://store.steampowered.com/news/posts/?enddate=1788390000",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/493839547938902179",
          "https://partner.steamgames.com/doc/webapi_overview/auth",
          "https://csmarketcap.com/blog/market-insights/from-boom-to-bust-cs2s-trade-protection-impact",
          "https://skinvault.gg/blog/cs2-trade-protection-explained/",
          "https://skin.land/blog/steam-changes-cs2-trade-ban-logic-timing/",
          "https://store.steampowered.com/news/posts/?appids=730&enddate=1753924057&feed=steam_announce%2F1000",
          "https://help.steampowered.com/faqs/view/3041-A87A-E5F6-B6AC",
          "https://store.steampowered.com/news/posts/?enddate=1747349559",
          "https://steamcommunity.com/ogg/593110/announcements/detail/533224478739530146",
          "https://store.steampowered.com/news/posts/?appids=730&enddate=1728000977&feed=steam_community_announcements",
          "https://steamcommunity.com/games/CSGO/announcements/detail/4447966961421256740",
          "https://help.steampowered.com/faqs/view/7F77-9E92-31E0-6B8E",
          "https://steamcommunity.com/sharedfiles/filedetails/?id=2926756889",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "http://web.archive.org/web/20260924181824/https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "https://steamcommunity.com/dev/apikey",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3749866608167579206",
          "http://web.archive.org/web/20251203174259/https://steamcommunity.com/groups/steamworks/announcements/detail/3749866608167579206",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3734103130194459461",
          "https://steamcommunity.com/discussions/forum/1/3807266184852932971/",
          "https://help.steampowered.com/faqs/view/225C-C51E-B8F0-55B2",
          "https://store.steampowered.com/news/group/4/view/3314112260640237775",
          "https://store.steampowered.com/news/posts/?appgroupname=Keep+in+touch&enddate=1666122699&feed=steam_blog",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/issues/325",
          "https://partner.steamgames.com/doc/webapi/IEconService",
          "https://steamcommunity.com/app/570/announcements/",
          "https://blog.dota2.com/2020/05/trading-cooldown/",
          "https://blog.counter-strike.net/2018/03/20309/",
          "https://blog.counter-strike.net/index.php/2018/03/20308/",
          "http://web.archive.org/web/20250226114333/https://blog.counter-strike.net/index.php/2018/03/20308/",
          "https://phishdestroy.io/steam_dossier/de/#vulnerability-profile"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/en/security_timeline.content.json",
      "export_json_sha256": "986bf1d6b910c1f155b030f633e6ae9950aa38752552d0bd297239fa5c49dc89"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "skin_atlas.html",
      "language": "en",
      "title": "The atlas of what Steam cannot carry — The Steam Dossier",
      "source_url": "https://phishdestroy.io/steam_dossier/skin_atlas",
      "source_html_sha256": "3f79f54d23e7d980fba5b37d0e09c8a29560f2ef17762141d6abe776c75b19f9",
      "exported_at": "2026-09-29T00:15:59.698Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "gallery",
            "source": "https://phishdestroy.io/steam_dossier/skin_atlas#gallery"
          }
        ],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "skin_atlas.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/en/skin_atlas.pdf?v=print-20260929-v5",
        "sha256": "a0d290c19aa677bc1f961e33503febfbbf73ece6ee0ffb916d7bd50247b138ef",
        "bytes": 177014,
        "pages": 13
      },
      "integrity": {
        "signed_object": "skin_atlas.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "skin_atlas.content.json.asc",
        "digest_file": "skin_atlas.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify skin_atlas.content.json.asc skin_atlas.content.json",
          "sha256sum -c skin_atlas.content.json.sha256"
        ]
      },
      "content": {
        "text": "Dieses Material ist auf Englisch verfügbar.Zurück zum Dossier · Deutsch ↗\nEXHIBIT IV-B / THE PRICE LADDER / 2026-09-23\nSkin Price-Ladder Atlas — The Liquidity Cliff\n\nValve's market stops where the money starts.\n\nWHAT THIS SECTION PROVES\n\nThis visual atlas analyzes 30,266 item categories across five marketplace catalogues, measuring market coverage above and below Valve's listing threshold. Below the $1,800 cap, Steam hosts 95.3% of active categories; immediately above it, official coverage collapses to 1.9% (with 0.0% coverage across corroborated assets). This demonstrates an abrupt, structural liquidity cliff where Valve delegates high-value transaction discovery to outside platforms while retaining full control over underlying asset custody.\n\n← Back to Executive briefing\n\nEvery CS2 item with a live price on five marketplaces was placed in a price band by its cheapest ask, and each band was measured for one thing: what share of it Valve’s own Community Market still carries. Below Valve’s listing cap the answer is 95.3%. Above it, the answer is 1.9%. The drop is not gradual and it does not fall where demand falls — it falls exactly at the published rule. Of the 248 item categories that two or more marketplaces independently price above the cap, 100.0% have no Steam listing at all.\n\nSee the cliff ↓Open the gallery of 419 itemsMethod and limits\n30,266item categories measured\n95.3%of sub-cap items carried by Steam\n1.9%of above-cap items carried by Steam\n$78.6Mfloor value of the corroborated set\n01 / the measurement\nThe cliff lands on the rule, not on demand\n\nEach of the 30,266 item categories below is placed in a band by its cheapest live ask across BUFF163, CSFloat, Skinport, YouPin 898 and C5Game, and only items quoted on two or more of them are counted, so no single optimistic listing can invent a band member. The upper panel is the share of each band that Valve’s own market still carries.\n\nShare of each price band carried by the Steam Community Market\nupper: steam coverage · lower: items per band, log scale\n0%\n25%\n50%\n75%\n100%\n100%\n96.9%\n95.9%\n97.3%\n91.1%\n76.8%\n14.5%\n2.9%\n1.5%\n0%\n0%\n0%\n4,632\n1¢–10¢\n7,152\n10¢–$1\n8,568\n$1–10\n5,941\n$10–100\n2,329\n$100–300\n1,292\n$300–1k\n193\n$1k–1.8k\n70\n$1.8k–3k\n67\n$3k–10k\n18\n$10k–30k\n3\n$30k–100k\n1\n$100k+\nitems\nlog\nVALVE’S LISTING CAP\nat or below Valve’s listing capabove the cap — Valve’s rule forbids the listingitem categories in the band\n\nCoverage means a live Steam ask existed for that category at the moment of capture. The lower panel is logarithmic because the catalogue is overwhelmingly cheap: reading it linearly would flatten every band above $300 into the baseline.\n\nWhat the shape rules out\n\nIf expensive items were simply unpopular, coverage would sag gradually as price rose. It does not. It holds at 76.8% through the $300–$1k band, then collapses to 14.5% in the band immediately beneath the cap and 2.9% in the band immediately above it. A demand effect does not know where Valve set its ceiling. A rule does.\n\nPrice band\tItem categories\tWith a live Steam ask\tSteam coverage\tCopies listed off Steam\n1¢–10¢\t4,632\t4,632\t100%\t8,223,227\n10¢–$1\t7,152\t6,931\t96.9%\t5,488,315\n$1–10\t8,568\t8,213\t95.9%\t3,939,538\n$10–100\t5,941\t5,780\t97.3%\t1,328,255\n$100–300\t2,329\t2,121\t91.1%\t364,466\n$300–1k\t1,292\t992\t76.8%\t187,504\n$1k–1.8k\t193\t28\t14.5%\t40,281\n$1.8k–3k\t70\t2\t2.9%\t9,592\n$3k–10k\t67\t1\t1.5%\t6,706\n$10k–30k\t18\t0\t0%\t1,366\n$30k–100k\t3\t0\t0%\t21\n$100k+\t1\t0\t0%\t2\n\nPattern and phase variants are excluded from this ladder: Steam does not list a blue-gem tier or a Ruby phase as its own market entry, so counting them would understate Steam’s coverage. Measured without the two-marketplace requirement the same ladder reads 79.1% below the cap and 6.5% above it across 37,204 items — a starker gap, built on weaker evidence, which is why it is not the figure quoted.\n\n02 / evidential grading\nAn asking price is not a price\n\nAnyone can list a P2000 for a round ten million yuan. Before a figure on this page is used for anything, it is graded by how many marketplaces independently quote the item above the cap and how tightly the middle of those quotes clusters. Only grades A and B are quoted — here or anywhere else in this dossier.\n\nA  Three or more shelves agree\n\nThree or more marketplaces quote the item above the cap and their median sits within 25% of the cheapest. 197 categories, 18,218 copies, $76,585,587.\n\nAbsent from Steam: 100.0%.\n\nB  Two shelves agree\n\nTwo marketplaces agree above the cap, or three agree less tightly. 51 categories, 176 copies, $2,038,814.\n\nAbsent from Steam: 100.0%.\n\nC  One shelf — not used\n\nA single marketplace carries the only above-cap ask. 171 categories, 247 copies. Shown in the gallery for completeness and excluded from every total on this page.\n\nThese are requests for a price, not evidence of one.\n\nWhat this correction cost, and what it bought\n\nDropping grade C removes 171 categories and $3,825,125 from the headline. What is left is smaller and much harder to argue with: 248 categories, 18,394 listed copies, $78,624,401, and 100.0% of them — every single one — absent from Valve’s market. The grade-C rows are the reason the figure moved; they are listed, not hidden.\n\nListings set aside as artefacts\n\nAny quote more than three times the cheapest ask on the same item is set aside. Converted at the rate the data itself implies, most of them are round CNY figures — the signature of a placeholder or a platform ceiling rather than an offer. Because every total on this page uses the cheapest ask, none of these figures could ever have inflated a number; they are excluded so that none of them can be quoted as a headline either.\n\nItem\tCheapest live ask\tSet aside\nSouvenir P2000 | Wicked Sick (Minimal Wear)\t$148,954\t$1,489,543\n★ Specialist Gloves | Crimson Kimono (Minimal Wear) | Phase 1\t$37,239\t$119,163\nSouvenir USP-S | Printstream (Factory New)\t$2,000\t$59,582\n★ Bowie Knife | Crimson Web (Factory New)\t$2,957\t$43,030\n★ Karambit | Marble Fade (Factory New) | 1st\t$11,916\t$38,874\nSticker | Ninjas in Pyjamas (Holo) | Katowice 2014\t$5,000\t$31,748\nSouvenir AWP | Dragon Lore (Battle-Scarred)\t$4,225\t$29,157\n★ Karambit | Doppler (Minimal Wear) | Ruby\t$7,122\t$27,273\nAll 419 categories, with the object each price refers to\n\nSource: https://phishdestroy.io/steam_dossier/skin_atlas#gallery\n\n04 / where it went instead\nThe shelves that carry what Steam will not\n\nThe same listings, grouped by the marketplace holding them. This is a count of where copies are listed, which is not the same as where they are owned and is not read here as such.\n\nFloor value of above-cap listings, by marketplace\nlowest ask x copies listed on that shelf\nYouPin 898\n$22,720,252\nBUFF163\n$22,022,606\nC5Game\n$12,560,543\nCSFloat\n$10,871,845\nSkinport\n$1,385,060\n\nJurisdictions, in the order above: YouPin 898 — China · BUFF163 — China · C5Game — China · CSFloat — United States · Skinport — Germany / Malta. The same physical item can be listed on more than one of these shelves, so these figures must not be summed with any other market total.\n\nFloor value by price tier\nhow the money is distributed above the cap\n$1.8k-3k\n$9,842,391\n$3k-10k\n$36,787,269\n$10k-50k\n$20,038,749\nover $50k\n$2,891,897\n05 / scarcity you can count\nHow thin the supply actually is\n\nEach CS2 item carries a wear value, and the marketplaces publish how many copies sit in each band of it. That turns “rare” from an adjective into a number — and it is the number that explains why a single compromised account is worth the effort of a bespoke phishing kit.\n\nAWP | Dragon Lore\n150 listed · from $11,350\n0.00–0.01\n29 · $14,730\n0.01–0.02\n54 · $11,618\n0.02–0.03\n26 · $11,350\n0.03–0.04\n25 · $11,618\n0.04–0.07\n16 · $11,585\n\nAWP | Dragon Lore (Factory New)\n\nM4A4 | Howl\n105 listed · from $6,628\n0.00–0.01\n11 · $10,725\n0.01–0.02\n14 · $8,088\n0.02–0.03\n11 · $7,580\n0.03–0.04\n19 · $6,703\n0.04–0.07\n50 · $6,628\n\nM4A4 | Howl (Factory New)\n\nAK-47 | Wild Lotus\n113 listed · from $14,373\n0.00–0.01\n25 · $22,343\n0.01–0.02\n11 · $19,364\n0.02–0.03\n3 · $19,645\n0.03–0.04\n15 · $15,044\n0.04–0.07\n59 · $14,373\n\nAK-47 | Wild Lotus (Factory New)\n\nAWP | Gungnir\n173 listed · from $11,618\n0.00–0.01\n28 · $17,875\n0.01–0.02\n21 · $13,600\n0.02–0.03\n32 · $12,065\n0.03–0.04\n29 · $11,735\n0.04–0.07\n63 · $11,618\n\nAWP | Gungnir (Factory New)\n\nAK-47 | Fire Serpent\n278 listed · from $663\n0.15–0.18\n87 · $730\n0.18–0.21\n49 · $712\n0.21–0.24\n52 · $703\n0.24–0.27\n18 · $715\n0.27–0.38\n72 · $663\n\nAK-47 | Fire Serpent (Field-Tested)\n\nCase Hardened (all tiers / blue gem)\n76 listed · from $1,638\n0.07–0.08\n1 · $2,516\n0.08–0.09\n4 · $2,482\n0.09–0.10\n6 · $3,856\n0.10–0.11\n7 · $2,797\n0.11–0.15\n58 · $1,638\n\nAK-47 | Case Hardened (Minimal Wear) | Tier 1\n\nBands are the marketplaces’ own float buckets; only bands with at least one live listing are drawn. The price beside each bar is the cheapest live ask in that band, so the premium attached to a low float is directly readable rather than asserted.\n\n06 / movement, measured off Steam\nWhat the third-party shelves actually realised\n\nValve publishes no usable history at this tier, and this dossier claims none. Skinport does publish its own completed sales over the trailing 24 hours, 7, 30 and 90 days, and that is the whole of the time dimension available here: a median realised price per trailing window, indexed so the 90-day median is 100. No Steam data is involved in either chart.\n\nMedian realised price, trailing window\nindexed to the 90-day median · 6,758 items with 20+ sales\n85\n91\n97\n103\n100\n90d\n94\n30d\n90\n7d\n88\n24h\nCompleted sales per day\nsame items, same windows\n7,621\n9,653\n11,684\n13,716\n12,700\n90d\n11,894\n30d\n9,540\n7d\n8,637\n24h\n\nThese are two charts rather than one with two vertical scales: an index and a daily count share no unit, and drawing them on a common axis would invite a comparison that is not valid. The windows are nested and trailing — the 90-day figure contains the 24-hour figure — so this is not a daily series and must not be read as one. What it supports is narrow and stated plainly: over the trailing windows Skinport published, the median realised price sat below its own 90-day median and the daily sale count fell with it.\n\nSkinport realised sales. The windows are nested and trailing, so each point is the median realised price over the trailing window, indexed to the 90-day median. It is not a daily series and no Steam data is involved.\n\n07 / what it is made of\nSixteen-year-old stickers and a handful of gloves\n\nThe set above the cap is not a broad slice of the game. It concentrates in a few rarities and a few collections, several of which can no longer be obtained at all — which is exactly why the supply cannot respond to the price.\n\nCategories above the cap, by rarity\ncount of item categories\nCovert\n321\nClassified\n39\nRestricted\n24\nContraband\n12\nMil-Spec Grade\n9\nConsumer Grade\n9\nIndustrial Grade\n5\nCategories above the cap, by collection\ntop ten collections\nThe St. Marc Collection\n13\nThe Cobblestone Collection\n13\nThe Norse Collection\n12\nThe Arms Deal Collection\n9\nThe Canals Collection\n7\nThe Gods and Monsters Collection\n6\nThe Revolution Collection\n4\nThe 2021 Train Collection\n4\nThe Rising Sun Collection\n4\nThe Chop Shop Collection\n4\n\nBy category: skin 366, sticker 48, container 3, sticker_slab 2.\n\n08 / the most anyone actually paid\nHighs backed by a transaction, not by a listing\n\nEvery other price on this page is an ask — what a seller wants. These are sales: the highest completed transaction Skinport recorded for each item, over the trailing 90 days. It is the only figure in this dossier that somebody actually paid, and each row links to the marketplace so the number can be checked against its source rather than against us.\n\n21,216items with a completed sale in the window\n106sold at or above Valve’s listing cap\n$14,192highest single completed sale\n67/419above-cap categories with any recorded sale\nThe thirty highest completed sales in the window\nItem\tHighest sale\tMedian sale\tSales\tCheapest ask now\tSteam\tCheck it\nAWP | Gungnir (Factory New)\t$14,192\t$11,343\t5\t$11,490\tabsent\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Factory New)\t$12,387\t$12,387\t1\t$13,836\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Factory New)\t$11,779\t$11,063\t16\t$10,941\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Minimal Wear)\t$11,693\t$11,693\t1\t$9,946\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Minimal Wear)\t$10,437\t$10,437\t1\t$9,610\tabsent\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Blue Laminate (Minimal Wear)\t$9,772\t$37\t76\t$30\t$40\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Minimal Wear)\t$9,463\t$9,463\t1\t$9,500\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Minimal Wear)\t$9,104\t$9,026\t6\t$8,524\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Hedge Maze (Minimal Wear)\t$8,139\t$8,139\t1\t$6,819\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Field-Tested)\t$7,617\t$7,390\t4\t$7,194\tabsent\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Field-Tested)\t$7,615\t$7,615\t1\t$7,100\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Field-Tested)\t$7,149\t$7,006\t2\t$7,165\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Field-Tested)\t$6,711\t$6,194\t15\t$5,988\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Factory New)\t$6,679\t$6,613\t3\t$6,628\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Superconductor (Factory New)\t$6,084\t$6,084\t1\t$7,969\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Battle-Scarred)\t$5,750\t$5,413\t3\t$5,899\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Pandora's Box (Minimal Wear)\t$5,520\t$5,508\t3\t$4,998\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Vice (Factory New)\t$5,385\t$5,158\t2\t$5,700\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Minimal Wear)\t$5,342\t$4,989\t19\t$4,997\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Hedge Maze (Field-Tested)\t$5,334\t$4,862\t5\t$3,724\tabsent\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Vulcan (Factory New)\t$5,275\t$1,418\t12\t$1,280\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Well-Worn)\t$4,978\t$4,978\t1\t$4,942\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Well-Worn)\t$4,931\t$4,931\t1\t$5,445\tabsent\tSkinport CSFloat Steam\nAK-47 | Hydroponic (Factory New)\t$4,802\t$4,351\t2\t$3,648\tabsent\tSkinport CSFloat Steam\n★ Talon Knife | Case Hardened (Minimal Wear)\t$4,588\t$466\t16\t$442\t$630\tSkinport CSFloat Steam\nAWP | Medusa (Factory New)\t$4,484\t$4,484\t1\t$4,171\tabsent\tSkinport CSFloat Steam\n★ Specialist Gloves | Pillow Punchers (Factory New)\t$4,359\t$4,359\t1\t$4,302\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Pandora's Box (Field-Tested)\t$4,359\t$3,666\t11\t$3,245\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Field-Tested)\t$4,289\t$4,225\t8\t$4,022\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Battle-Scarred)\t$4,124\t$4,124\t1\t$4,279\tabsent\tSkinport CSFloat Steam\nSame item, same 90 days, wildly different price\n\nRestricted to items with a $100 median and at least five completed sales, because on a cheap skin one freak sale swamps the ratio. What is left is dominated by Case Hardened finishes, where the pattern decides the price and the marketplace files every pattern under one name — the same mechanism measured by float in section 05.\n\nItem\tHigh vs median\tHighest sale\tMedian sale\tSales\tCheck it\n★ Talon Knife | Case Hardened (Minimal Wear)\t+884%\t$4,588\t$466\t16\tSkinport CSFloat Steam\nDesert Eagle | Cobalt Disruption (Factory New)\t+859%\t$1,210\t$126\t115\tSkinport CSFloat Steam\nAWP | BOOM (Minimal Wear)\t+814%\t$1,232\t$135\t89\tSkinport CSFloat Steam\nAK-47 | Case Hardened (Well-Worn)\t+769%\t$1,720\t$198\t70\tSkinport CSFloat Steam\nAWP | Graphite (Factory New)\t+761%\t$1,469\t$171\t124\tSkinport CSFloat Steam\n★ Talon Knife | Case Hardened (Field-Tested)\t+509%\t$2,437\t$400\t48\tSkinport CSFloat Steam\n★ Kukri Knife | Case Hardened (Minimal Wear)\t+448%\t$723\t$132\t69\tSkinport CSFloat Steam\n★ Kukri Knife | Case Hardened (Field-Tested)\t+415%\t$549\t$106\t128\tSkinport CSFloat Steam\n★ Ursus Knife | Case Hardened (Minimal Wear)\t+371%\t$597\t$127\t12\tSkinport CSFloat Steam\nAK-47 | Case Hardened (Field-Tested)\t+369%\t$1,037\t$221\t125\tSkinport CSFloat Steam\nAK-47 | Red Laminate (Minimal Wear)\t+360%\t$552\t$120\t18\tSkinport CSFloat Steam\nAWP | Asiimov (Field-Tested)\t+351%\t$528\t$117\t439\tSkinport CSFloat Steam\nAK-47 | Vulcan (Field-Tested)\t+337%\t$865\t$198\t241\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Nightwish (Factory New)\t+322%\t$625\t$148\t31\tSkinport CSFloat Steam\nAWP | Lightning Strike (Factory New)\t+319%\t$2,065\t$493\t198\tSkinport CSFloat Steam\nStatTrak™ AWP | Redline (Minimal Wear)\t+312%\t$574\t$139\t24\tSkinport CSFloat Steam\nStatTrak™ AWP | Asiimov (Battle-Scarred)\t+287%\t$524\t$135\t37\tSkinport CSFloat Steam\nAK-47 | Redline (Minimal Wear)\t+277%\t$562\t$149\t112\tSkinport CSFloat Steam\nAWP | Crakow! (Factory New)\t+275%\t$379\t$101\t72\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Vulcan (Factory New)\t+272%\t$5,275\t$1,418\t12\tSkinport CSFloat Steam\n\nThis is a 90-day high, NOT an all-time high, and it covers ONE marketplace. No all-time figure is claimed anywhere in this dossier. An item with no Skinport sale in the window is absent from this exhibit entirely, which is why the set is smaller than the census.\n\nVerification links are built from the catalogue's own platform identifiers. They point at each marketplace's page for the item so a reader can check the figure against the source rather than against us. Outbound links carry rel=\"nofollow\": they are citations, not endorsements, and several of the destinations are marketplaces this investigation is critical of.\n\n09 / provenance and limits\nWhere this came from and what it cannot show\n\nEvery figure on this page is recomputed from two snapshot files whose hashes are published alongside them. Nothing here is transcribed from another site’s article.\n\nSource and access\n\ncs2.sh API, GET /v1/prices/latest and GET /v1/schema, single snapshot, captured 2026-09-23T00:44:27.871388581Z, priced in USD.\n\nThe data was obtained under a paid commercial subscription held by the GDPR requester documented in the archive, under the provider’s own terms. No marketplace was scraped and no credential of any marketplace was used. The requester’s key is held outside this repository and appears in no file here.\n\nHow an item qualifies\n\nEvery base item with at least one live ask on BUFF, CSFloat, Skinport, YouPin or C5Game is placed in a price band by its CHEAPEST such ask, so the band never depends on Steam. \"Steam coverage\" is the share of the items in that band carrying any live Steam ask at the moment of capture. Pattern and phase variants are excluded from the ladder because Steam does not list them separately; including them would understate Steam. Renders are the catalogue images for the same items, stored locally.\n\nRenders and image rights. Catalogue item renders are the provider's images served for the same market_hash_name as the price rows, stored locally for offline and IPFS display. The renders are not PhishDestroy's work: all item imagery, logos and screenshots remain the property of their respective owners (cs2.sh, CSFloat, Skinport, BUFF, YouPin, C5Game, Valve and others). They are reproduced solely for identification and public-interest reporting; no ownership or licence is claimed.\n\nWhat we could not obtain\n\nThe subscription tier used serves current snapshots only. Historical and archive endpoints were not available, and no historical series is claimed anywhere on this page beyond the trailing-window sales Skinport publishes itself in section 06.\n\nOne snapshot, not a time series. Absence of a Steam listing at the moment of capture is not proof an item may never appear there; it is the measured state of the shelf at that moment, and for prices above the cap it is also what Valve's published rule requires: Valve's Community Market explicitly caps listings at $1,800 per item (with a maximum Steam Wallet balance of $2,000; see Steam Community Market FAQ archived 2026-09-21 ↗ and Steam Subscriber Agreement § 3.C archived 2026-09-24 ↗).\n\nGrading\n\nAn item's price is always its cheapest live ask, so a high outlier can never inflate a total. Grading governs which rows may be quoted. Any quote more than three times the cheapest ask on the same item is set aside as not a live price. Grade A: three or more marketplaces still quote above the cap and their median sits within 25 per cent of the cheapest. Grade B: two marketplaces agree, or three agree less tightly. Grade C: a single shelf - an asking price, not a market price. Only grades A and B are quoted anywhere in this dossier.\n\nOutlier rule: quote > 3.0x the cheapest ask on the same item.\n\nWhy the totals are a floor\n\nFor each marketplace the item’s lowest ask is multiplied by the number of copies that shelf lists. Every other copy there is priced at or above that lowest ask, so the true posted value is higher by construction, not by estimate. It is not a sale, not a cash flow, and not a valuation of the CS2 economy.\n\nCheck it yourself\n\nThe derived datasets behind every chart on this page are published in full: the atlas dataset, the grading and artefact screen, the underlying census and the manifest with the SHA-256 of each raw snapshot.\n\nA correction recorded in the open\n\nAn earlier draft of the companion register led with a Souvenir AK-47 | Point Disarray asked at $148,954 on one Chinese marketplace while Steam priced it at $119. That row is grade C: a single shelf, a single copy, and no second marketplace agreeing. It is an asking price, not a price, and it has been demoted here and on that page. The corroborated leader is Sticker | Titan (Holo) | Katowice 2014 at $66,285, quoted by 4 marketplaces within 5.2% of each other — and absent from Steam entirely.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Skin Price-Ladder Atlas — The Liquidity Cliff"
          },
          {
            "level": 2,
            "id": null,
            "text": "The cliff lands on the rule, not on demand"
          },
          {
            "level": 3,
            "id": null,
            "text": "What the shape rules out"
          },
          {
            "level": 2,
            "id": null,
            "text": "An asking price is not a price"
          },
          {
            "level": 3,
            "id": null,
            "text": "A  Three or more shelves agree"
          },
          {
            "level": 3,
            "id": null,
            "text": "B  Two shelves agree"
          },
          {
            "level": 3,
            "id": null,
            "text": "C  One shelf — not used"
          },
          {
            "level": 3,
            "id": null,
            "text": "What this correction cost, and what it bought"
          },
          {
            "level": 3,
            "id": null,
            "text": "Listings set aside as artefacts"
          },
          {
            "level": 2,
            "id": null,
            "text": "All 419 categories, with the object each price refers to"
          },
          {
            "level": 2,
            "id": null,
            "text": "The shelves that carry what Steam will not"
          },
          {
            "level": 2,
            "id": null,
            "text": "How thin the supply actually is"
          },
          {
            "level": 2,
            "id": null,
            "text": "What the third-party shelves actually realised"
          },
          {
            "level": 2,
            "id": null,
            "text": "Sixteen-year-old stickers and a handful of gloves"
          },
          {
            "level": 2,
            "id": null,
            "text": "Highs backed by a transaction, not by a listing"
          },
          {
            "level": 3,
            "id": null,
            "text": "The thirty highest completed sales in the window"
          },
          {
            "level": 3,
            "id": null,
            "text": "Same item, same 90 days, wildly different price"
          },
          {
            "level": 2,
            "id": null,
            "text": "Where this came from and what it cannot show"
          },
          {
            "level": 3,
            "id": null,
            "text": "Source and access"
          },
          {
            "level": 3,
            "id": null,
            "text": "How an item qualifies"
          },
          {
            "level": 3,
            "id": null,
            "text": "What we could not obtain"
          },
          {
            "level": 3,
            "id": null,
            "text": "Grading"
          },
          {
            "level": 3,
            "id": null,
            "text": "Why the totals are a floor"
          },
          {
            "level": 3,
            "id": null,
            "text": "Check it yourself"
          },
          {
            "level": 3,
            "id": null,
            "text": "A correction recorded in the open"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/de/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/de/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/skin_atlas#gallery",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://skinport.com/market?search=AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260924114457/https://store.steampowered.com/subscriber_agreement/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-atlas.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-artefact-screen.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-above-the-ceiling.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/en/skin_atlas.content.json",
      "export_json_sha256": "c695d7e17d0c6cac357f6341317470f26079ec8410049f18ea9844f763fffa3f"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "social_graph.html",
      "language": "en",
      "title": "Follow the recorded connections — The Steam Dossier",
      "source_url": "https://phishdestroy.io/steam_dossier/social_graph",
      "source_html_sha256": "40cf1f075202fc3bc68d41a12c06d11357d148ea8c5b73f29bcaef91cda0c235",
      "exported_at": "2026-09-29T00:15:58.872Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "social_graph.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/en/social_graph.pdf?v=print-20260929-v5",
        "sha256": "731f9bf1cae683f67db3fdf3f0e888fd9ac9bde50b6b16bd30a6173a60cdca90",
        "bytes": 119843,
        "pages": 6
      },
      "integrity": {
        "signed_object": "social_graph.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "social_graph.content.json.asc",
        "digest_file": "social_graph.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify social_graph.content.json.asc social_graph.content.json",
          "sha256sum -c social_graph.content.json.sha256"
        ]
      },
      "content": {
        "text": "Dieses Material ist auf Englisch verfügbar.Zurück zum Dossier · Deutsch ↗\nFollow the connections.Inspect each relationship.\n\nSearch a profile. Choose a relationship type. Follow its direct neighbours in the captured records. Research tool: edges represent public relationships, not proof of direct contact, private coordination or misconduct between any two nodes. A 3,435-node layout is best read with filters.\n\nExplore one relationship at a time\n\n💡 Click & drag nodes to reorganize the graph. Hover to view detailed profiles. Teal solid lines = Friendships, Amber dashed lines = Mutual Comments.\n\nRelationship typeProfile and direct neighbours\n\n3,435 profiles · 4,551 recorded links\n\nSearch and choose a profile, or click a node. Only its direct recorded neighbours remain. An edge records a relationship; it does not establish private coordination.\n\nProfiles in the captured dataset\n\nFull source table: download all 3,435 rows (CSV). The table below initially shows the first 25 rows; search and pagination cover the complete dataset.\n\n1–25 / 3,435 rows\nPersona Name\tSteamID64\tPrivacy\tStatus\tGroup Memberships\tFrozen Inventory (USD)\tLocation\nMahatma Gandhi\t76561198333721623\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tPH\nGalley//갤리🌠🌙\t76561198043416832\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tKP\n$Schlächter\t76561198860277343\tPUBLIC\tClean\tsteambans\t$0.00\tUnknown\n❄r3dsn0w000™❄ [Cristi]🎮\t76561197986767957\tPUBLIC\tClean\tCommunityLegends\t$0.00\tRO\n(2a03) Wolfy\t76561197991671851\tPUBLIC\tCommunity\tsr_public\t$0.00\tUS\nZloy2288\t76561198038578334\tPUBLIC\tClean\tsteambans\t$0.00\tBY\njessy\t76561198039125237\tPUBLIC\tCommunity, VAC (1x)\tCommunityLegends\t$0.00\tJP\nJithraRufure\t76561198071896910\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\n| Níllerdínho |\t76561198003487438\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tDK\nJones is back\t76561198023013026\tPRIVATE\tVAC (1x)\tsteambans\t$0.00\tUnknown\nUNEX | ★✠☠ MoH3st ☠✠\t76561198050763123\tPUBLIC\tClean\tsteambans\t$0.00\tDE\nTrojan\t76561198048457084\tPUBLIC\tClean\tCommunityLegends\t$0.00\tDE\n𝗠𝗮𝘆𝘂 ❤\t76561199377967696\tPUBLIC\tClean\tsr_public\t$0.00\tIS\nbig fucking idiot\t76561198871206397\tPUBLIC\tVAC (1x)\tsteambans\t$0.00\tUnknown\nSOFF Games\t76561198227129276\tPUBLIC\tClean\tcommunitymoderators\t$0.00\tRU\nThijminecraft02\t76561198253895669\tPUBLIC\tClean\tSteamIDcouk SArchive\t$0.00\tNL\nStatic-sama\t76561198289329793\tPUBLIC\tClean\tsteambans\t$0.00\tJP\n𝙸mmortal 𝚂targazer\t76561198142116760\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\nCommander Keen\t76561197987773287\tPUBLIC\tClean\tsteambans\t$0.00\tBE\nS1mX\t76561199648509165\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\nmixwell\t76561199276547472\tPUBLIC\tClean\tsr_public\t$0.00\tJP\nP90_GOD_YyEs™\t76561198285821942\tPUBLIC\tClean\tsteambans\t$0.00\tHK\nhewwo?\t76561199133807546\tPUBLIC\tVAC (1x)\tsteambans\t$0.00\tCH\n♕Kamikaze Atze♕\t76561198002700103\tPUBLIC\tClean\tsteambans\t$0.00\tDE\nPastica\t76561198154655970\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tDZ\nRecorded friendship links\n\nFull source table: download all 4,299 rows (CSV). The table below initially shows the first 25 rows; search and pagination cover the complete dataset.\n\n1–25 / 4,299 rows\nUser A\tDirection\tUser B\tRelation Type\nMahatma Gandhi\n76561198333721623\t↔\tDeskjet\n76561198272738437\tMutual Friends\nGalley//갤리🌠🌙\n76561198043416832\t↔\tomega\n76561197960274529\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tFisty\n76561198057301486\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tFaalagorn\n76561198001116101\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tMURK\n76561198036995672\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tÅρøᴛʜℯᴛȋᴄÅʟȋℯη ♛👽♛\n76561197984615267\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tsilatrak\n76561197999629462\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tBlack Blade\n76561198083368493\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tAvenger\n76561197978249317\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tRemtar\n76561198124322650\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tCato\n76561197961345984\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t✪ G λ M Ξ ®\n76561197994308495\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tclees42\n76561198030936806\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t𝓜ε𝔰𝔥 | AusLevels\n76561198108828539\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tSgtFopper™\n76561198002555892\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t❥Miss Bee\n76561198046958996\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tTesTy\n76561198032370068\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tskl_andrey\n76561198136881436\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t\"Exekutor\"\n76561198009583947\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tAraripe\n76561198103754372\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tsteve6678\n76561198053200093\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\ttrinner\n76561197970359081\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tSteph S.\n76561198025653291\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tKirito\n76561198154545657\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tDoc. todt\n76561197984492467\tMutual Friends\nRecorded comment links\n\nFull source table: download all 252 rows (CSV). The table below initially shows the first 25 rows; search and pagination cover the complete dataset.\n\n1–25 / 252 rows\nAuthor\tDirection\tTarget Profile\tDate\tComment Text\nDeskjet\n76561198272738437\t→\tMahatma Gandhi\n76561198333721623\t16 September, 2021 @ 11:02:05 pm PDT\t\"𝑵𝒐𝒘 𝒊𝒇 𝑰 𝒇𝒖𝒄𝒌 𝒕𝒉𝒊𝒔 𝒎𝒐𝒅𝒆𝒍𝑨𝒏𝒅 𝒔𝒉𝒆 𝒋𝒖𝒔𝒕 𝒃𝒍𝒆𝒂𝒄𝒉𝒆𝒅 𝒉𝒆𝒓 𝒂𝒔𝒔𝒉𝒐𝒍𝒆𝑨𝒏𝒅 𝑰 𝒈𝒆𝒕 𝒃𝒍𝒆𝒂𝒄𝒉 𝒐𝒏 𝒎𝒚 𝑻-𝒔𝒉𝒊𝒓𝒕𝑰'𝒎𝒎𝒂 𝒇𝒆𝒆𝒍 𝒍𝒊𝒌𝒆 𝒂𝒏 𝒂𝒔𝒔𝒉𝒐𝒍𝒆\" - Nelson Mandela\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t22 November, 2021 @ 4:10:28 pm PDT\thttps://anige.horigiri.net/?cat=22\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t18 November, 2021 @ 12:45:26 am PDT\thttps://gamerch.com/umamusume/entry/250411\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t8 August, 2021 @ 4:13:25 am PDT\thttps://modoocode.com/304\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t6 February, 2021 @ 3:35:05 pm PDT\t▤ ∫︹- -ω⁾ ⁽︹▓▓︺\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t11 December, 2019 @ 1:50:53 am PDT\thttps://blog.naver.com/aksenwlddj12/221369410039\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t2 October, 2019 @ 7:11:59 am PDT\tǤαllєу║︎갤리..۩\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t9 April, 2019 @ 12:51:28 pm PDT\tExplosiveDamage(owner, from, maxrange, minrange, distmultiplier, dmgmultiplier, mindamage, typ, damagetype, ignore)\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 12:22:47 pm PDT\tinfo - sh_titles.lua\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 12:21:46 pm PDT\tlocal nibbas = 1344 init.lua\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 11:31:58 am PDT\thttp://foreign.aladin.co.kr/shop/wproduct.aspx?ItemId=123955531&start=slayer\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t3 April, 2019 @ 1:26:41 am PDT\tǤαllєу\nLei\n76561198982197954\t→\tJithraRufure\n76561198071896910\t29 December, 2024 @ 12:58:08 pm PDT\t+rep he knows how 2 rush B ￣ヘ￣\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t2 September, 2026 @ 5:16:55 am PDT\tlol\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t20 August, 2026 @ 6:11:03 am PDT\t?\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t25 July, 2026 @ 7:20:05 am PDT\thahahahaha\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t30 June, 2026 @ 12:52:42 pm PDT\twow\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t30 June, 2026 @ 12:41:32 pm PDT\txD\nvalorant enjoyer\n76561199112142402\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:26:30 pm PDT\toh no!!\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:26:11 pm PDT\toh no!!\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:22:22 pm PDT\tomg !!! they know my secret, omg!!!\nvalorant enjoyer\n76561199112142402\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:21:39 pm PDT\t+rep good ♥♥♥♥♥ player\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:20:50 pm PDT\tomg! u cant cheat on secure gaben servers, omg dont report me, they ban me for boosted omg\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 8:37:11 pm PDT\txD\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t28 June, 2026 @ 1:58:14 pm PDT\twow",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Follow the connections.Inspect each relationship."
          },
          {
            "level": 2,
            "id": null,
            "text": "Explore one relationship at a time"
          },
          {
            "level": 2,
            "id": null,
            "text": "Profiles in the captured dataset"
          },
          {
            "level": 2,
            "id": null,
            "text": "Recorded friendship links"
          },
          {
            "level": 2,
            "id": null,
            "text": "Recorded comment links"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/de/social_graph.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-profiles.csv",
          "https://steamcommunity.com/profiles/76561198333721623",
          "https://steamcommunity.com/profiles/76561198043416832",
          "https://steamcommunity.com/profiles/76561198860277343",
          "https://steamcommunity.com/profiles/76561197986767957",
          "https://steamcommunity.com/profiles/76561197991671851",
          "https://steamcommunity.com/profiles/76561198038578334",
          "https://steamcommunity.com/profiles/76561198039125237",
          "https://steamcommunity.com/profiles/76561198071896910",
          "https://steamcommunity.com/profiles/76561198003487438",
          "https://steamcommunity.com/profiles/76561198023013026",
          "https://steamcommunity.com/profiles/76561198050763123",
          "https://steamcommunity.com/profiles/76561198048457084",
          "https://steamcommunity.com/profiles/76561199377967696",
          "https://steamcommunity.com/profiles/76561198871206397",
          "https://steamcommunity.com/profiles/76561198227129276",
          "https://steamcommunity.com/profiles/76561198253895669",
          "https://steamcommunity.com/profiles/76561198289329793",
          "https://steamcommunity.com/profiles/76561198142116760",
          "https://steamcommunity.com/profiles/76561197987773287",
          "https://steamcommunity.com/profiles/76561199648509165",
          "https://steamcommunity.com/profiles/76561199276547472",
          "https://steamcommunity.com/profiles/76561198285821942",
          "https://steamcommunity.com/profiles/76561199133807546",
          "https://steamcommunity.com/profiles/76561198002700103",
          "https://steamcommunity.com/profiles/76561198154655970",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-connections.csv",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-comments.csv"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/en/social_graph.content.json",
      "export_json_sha256": "0d6c3475a54badceb2d439f41742148557c0e32ea923ded742103400cc070a19"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "steam_enforcement_evidence.html",
      "language": "en",
      "title": "Rules versus responses — The Steam Dossier",
      "source_url": "https://phishdestroy.io/steam_dossier/steam_enforcement_evidence",
      "source_html_sha256": "3581c2359ed25f6452b49674250c93c3249f70f143845a4cc64a0bb6a45b9011",
      "exported_at": "2026-09-29T00:15:58.460Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "steam_enforcement_evidence.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/en/steam_enforcement_evidence.pdf?v=print-20260929-v5",
        "sha256": "c69e9d7988a0a7f1e571bd6ce0742eb03c2ddb2041372fd2c2d9da0b77e9d1b9",
        "bytes": 377478,
        "pages": 36
      },
      "integrity": {
        "signed_object": "steam_enforcement_evidence.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "steam_enforcement_evidence.content.json.asc",
        "digest_file": "steam_enforcement_evidence.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify steam_enforcement_evidence.content.json.asc steam_enforcement_evidence.content.json",
          "sha256sum -c steam_enforcement_evidence.content.json.sha256"
        ]
      },
      "content": {
        "text": "Dieses Material ist auf Englisch verfügbar.Zurück zum Dossier · Deutsch ↗\nEvidence supplement / source-linked records\nSteam Enforcement Evidence — Support Records & Developer Network\n\nThe rule. The response.\n\nWHAT THIS SECTION PROVES\n\nThis evidence room compares Valve's official Subscriber Agreement against dated enforcement logs, support dispute resolutions, and developer network records across 252 repositories and 3,320 profiles. It demonstrates that ordinary account holders face non-rebuttable enforcement and support closures following session compromises, while high-volume commercial bot operations run continuously with public infrastructure access.\n\n← Back to Executive briefing\n\nRead the written restriction. Open the recorded response. Compare what the source shows with what remains unanswered.\n\nSupport & appeals ↓Public infrastructure ↓\n252repository records\n3,320public profiles\n4,214distinct profile–repository pairs\n98,902profile pairs with shared repos\n01 / Support, sanctions & restoration\nRead the complaint.Keep the source attached.\nSupport Refusals Gallery (981 Exhibits) ↗Download selected records ↓\nHFB / THE OUTSOURCING CASEThe acknowledged compromise.\nThe reported dismissals.\n\nFollow the reproduced support response and the source of the claim about contractor staff.\n\nOpen the case and its sources →\n\nBelow: five preserved public Reddit posts from the supplied support collection. Each record documents a reported interaction with Valve's support system — preserved with its original source link, capture position and complete text. These are victim accounts. The authenticated support logs that would confirm or contradict them are held by Valve and have not been disclosed.\n\n01\nBan & review2024-12-09\nPermanent sanction & closed appeals\n\nThe author reports a permanent account ban, repeated ticket closures and a planned GDPR access request.\n\nREDDIT / PUBLIC TESTIMONYr/ohnePixelCapture record 294\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 303 words\nPermanently banned Steam account without a clear explanation, need help!\n\nsteam_support_tickets_MEGA.json / record 294\n\nHey everyone,\n\nI’m in a really frustrating situation, and I’m hoping someone here can help me or offer advice. My Steam account was just permanently banned for allegedly violating the Steam Subscriber Agreement, and I have no idea why.\n\n# What Steam Support told me:\n\nThe support message said my account was banned due to:\n\n* Suspicious activities related to transferring or attempting to sell/trade the account.\n* Community reports and other unspecified factors.\n\nThey added that the ban is permanent and that they can't help me further. They also warned that future support requests regarding this ban might be ignored. 😞\n\n# Why I’m contesting this ban:\n\n* I have never sold, traded, or transferred my account. I’ve been the legitimate owner since the beginning.\n* On the day the ban occurred, I did nothing noteworthy that could have triggered such a sanction.\n* I received no prior warning, which feels incredibly unfair.\n\n# What I’ve tried so far:\n\n* Contacting Steam Support: I explained my situation and asked for more details, but they’re sticking to their decision and closing my tickets.\n* I’m preparing a request based on my Right of Access (GDPR) to get all the data related to my account.\n\n# Questions for the community:\n\n1. Has anyone successfully had a permanent ban lifted on Steam?\n2. Are there steps I can take to prove I’m the legitimate owner of the account?\n3. Any advice on how to word my request to convince support to reconsider my case?\n4. Would it be helpful to contact the CNIL (I’m based in France) to force Steam to provide more information?\n\nI’m really desperate at the thought of losing all my games, purchases, and years of playtime. Thanks in advance for any help and advice you can give!\n\nhttps://preview.redd.it/jk9qv0gmhv5e1.png?width=1289&amp;format=png&amp;auto=webp&amp;s=b3a333ebb08ea133e2c8747ba126f5a68283d9f7\n\nhttps://preview.redd.it/4sopt0gmhv5e1.png?width=1022&amp;format=png&amp;auto=webp&amp;s=56195d5336118faf9413f1514ead7e8d24c788c3\n\nhttps://preview.redd.it/eqrxw0gmhv5e1.png?width=996&amp;format=png&amp;auto=webp&amp;s=ff3539d28ab754e513ad471822c5de652920101d\n\nhttps://preview.redd.it/728xz0gmhv5e1.png?width=1034&amp;format=png&amp;auto=webp&amp;s=bc5335673509929669af785aa244bf8d2dc58da8\n\n02\nSupport access2025-05-09\nAccount recovery & a reported $10,000 loss\n\nThe author alleges that support reset credentials and removed account protection following another person’s recovery ticket.\n\nREDDIT / PUBLIC TESTIMONYr/legaladviceCapture record 110\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 193 words\nGot $10k stollen from steam inventory due to steam' support fault.\n\nsteam_support_tickets_MEGA.json / record 110\n\nLocation: Quebec, Canada.\n\nLast year, someone hacked my Steam account and stole items worth about $10,000 USD. I only noticed this last week. When I talked to Steam Support, they admitted that someone submitted a ticket to make changes on the account and Steam Support reset my password and turned off all my account security.\n\nI asked Steam Support about getting my items back, but they said there was nothing they could do. They told me I should follow their security recommendations.\n\nThe problem is, I did everything they \"suggested\" to protect an account:\n\n* I had two-factor authentication.\n* My phone number was connected to my account.\n* I used Steam Guard.\n* I printed recovery codes and kept them in a safe.\n\nEven though I did all these things, Steam Support still gave someone else access to my account. The stolen items had been in my account since around 2016-2017. Also, I had not logged in for a few years, so I didn’t accidentally give my information to a fake website.\n\nIs there anything I can do, or do I just have to accept losing $10,000 USD?\n\nThanks for your help.\n03\nRestoration2022-07-07\nA reported $500+ loss & template replies\n\nThe author describes an account compromise, disputed transactions and a support response that allegedly did not address the submitted evidence.\n\nREDDIT / PUBLIC TESTIMONYr/DotA2Capture record 45\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 410 words\nFunds stolen through steam market. Disappointed with Steam response.(or lackthereof)\n\nsteam_support_tickets_MEGA.json / record 45\n\nOn 6th July 2022, 44 unauthorized transactions were made on the steam market using my steam wallet funds totalling roughly $500+ USD to buy worthless 1 cent Dota 2 items. This happened during the wee hours in the morning and i contacted them first thing when i woke up. \n\nI have 2FA enabled all the time, and always thought this would not happen to me as I do not go on betting sites/click sketchy links. My account password + emails were not changed, nor did they take my inventory, just that my funds were used illicitly. Also when I went to disable other APIs, it says there are no other APIs to disable. Shows that it wasn't through me clicking sketchy links and leaving my account details there. Would have lost the whole account if i did so.\n\nWhat baffles me is how did they bypass my 2FA to login my account? Why doesn't steam market purchases go through 2FA as well? First time in 9 years that this happened to me. My acc was logged in 'BY' 'Vitebsk' during the illicit purchases but I'm based in Asia I gathered all the screenshots and provided in the ticket to steam support. \n\nAll i got was the standard copy paste template reply by Steam Support. Lost $500+ and was not even worthy of having a proper person to look into this. I dont think they even read or take a look at the screenshots cause if they did, they would have come to the realization that what happened was clearly fraud, and with a few clicks, reverse the unauthorized transactions, refund my wallet and ban the hijacker. \n\nOver the years, i've spent quite a fair bit on steam but really, this is the kind of recourse we get when our account is compromised? They just don’t care, sigh. I only expect the bare minimum from Steam and looks like even that is quite far-fetched.\n\nSS: https://imgur.com/a/67frcls \n\nHijacker: https://steamcommunity.com/profiles/76561199141246495\n\nSteam Response: https://imgur.com/a/V6v4maM\n\nI could think of a few ways on how to Improve:\n\n1) Add 2FA to market transactions. (even if its bulk posting or selling of items, just 1 2FA notif is required)\n\n2) Enable accounts to be region locked. (if you are migrating, then have to go through steam support etc)\n\n3) Additional Lock on Steam Wallet. (Another password perhaps?)\n\nEDIT: 2nd ticket in and I have still yet to receive a non robotic copy paste template response from Steam.\n04\nRestoration2021-11-29\nSteam Guard & an item-restoration refusal\n\nA preserved post includes the author’s account of item theft and a support response declining restoration.\n\nREDDIT / PUBLIC TESTIMONYr/DotA2Capture record 58\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 563 words\nMany people are losing item via clicking links where steam guard is enabled and steam support doesn't not restore items.\n\nsteam_support_tickets_MEGA.json / record 58\n\nAccounts are getting compromised and might be their pc as well where Steam market is targeted hence the malicious links . I am assuming these hackers are getting encouraged where steam support is not doing nothing and they are getting away with hacking items.  \nLiterally the guy who is supporting the game which he doesn't get any in game advantage just  cosmetics in game only for the sole purpose of supporting the game so that the game will prosper and become beautiful way  to enjoy weekend. But right now players are getting hacked left right and center and steam support  is copy pasting message where in short they are blaming the guy who clicked link. 1st this is happening because they are not targeting players but they are targeting market since they are selling those stuff for real cash via party website. Steam is a huge company and can eradicate the problem or at least can remove links temporarily  in chat since hackers are targeting .They made us install steam guard by saying we wont help if there is no steam guard now steam guard is not enough to save our inventory now they changed their policy  that they should not click any suspicious links. How would we know if the link is suspicious ? After clicking and getting our inventory stolen right !   \n\"we'd have to duplicate an item to restore it. Duplication lowers the value of all items by reducing their scarcity and inflating the economy, which affects everyone involved in trading and the Market. To maintain the value of everyone’s inventory, we do not restore items. For more information, please see the Steam Item Restoration Policy.\"  \nThey care for millions of people IN STEAM MARKET where as few  are losing items which is going to affect market where the rightful owner bought the items and hacker is going to sell the item via 3rd party website and enjoy ! HOW IRONIC !!  \nThis is the message from support where my frnd got his items stolen via clicking on link  \n   \nHi there,  \n\nThank you for the information and screenshots provided.  \n\nIt appears that the account was compromised, please take the following steps to secure your account and computer:  \n\nScan your computer for viruses, key loggers, spyware, and other malicious code using antivirus software with updated virus definitions.  \nChange the password for the email address that is associated with your Steam account.  \nRegularly reset your Steam account password.  \n\nPlease see our Security Recommendations article.  \n\nIn addition, I’m sorry to hear that your items were removed without your permission. Unfortunately, Steam Support does not restore scammed, lost, or stolen items for any reason.  \n\nSince Steam Support does not remove items from accounts, we'd have to duplicate an item to restore it. Duplication lowers the value of all items by reducing their scarcity and inflating the economy, which affects everyone involved in trading and the Market. To maintain the value of everyone’s inventory, we do not restore items. For more information, please see the Steam Item Restoration Policy.  \n\nTo make sure that a scammer is reported, please report them through the Steam Community. Reporting a scammer through the Steam Community is the best way to prevent them from committing future scams.  \n\nTo learn how to avoid scams or hijackings, please see our Trade Scam article.  \n\nIf you still need assistance, please let us know.\n05\nEnforcement2025-05-11\nSelective enforcement & an unexplained ban\n\nA community member describes a disputed ban and contrasts it with the visibility of commercial gambling promotion.\n\nREDDIT / PUBLIC TESTIMONYr/SteamUncensoredCapture record 107\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 1,208 words\n🚨 Steam Bans Without Reason and Ignores Its Community — What’s Going On?\n\nsteam_support_tickets_MEGA.json / record 107\n\nHey r/Steam,\n\nI’m writing this to share my thoughts and concerns about my friend [moneylead](https://steamcommunity.com/id/moneylead/) and Steam’s policies in general. I spoke with him yesterday about his situation, though I didn’t discuss writing this post with him—I asked last night, but he hasn’t responded yet. I want to highlight that this issue is broader than just his case, and while Steam might make changes in the future (though that’s unlikely), I feel the community needs to understand how far Steam has strayed from its original values. I’m not trying to put moneylead in a tough spot with this thread—all the info I’m sharing is public, nothing secretive. I hope he won’t be upset with me, but the community needs this case to see the bigger picture and how Steam feels completely unaccountable.\n\n**Why Does Steam Ignore Its Community?**  \nWhy does a platform like **Roblox** provide a detailed log of ban reasons, while Steam, which claims to be \"community-driven,\" ignores its community, bans whoever they want, for whatever they want, with no transparency? I looked into Roblox as a popular game—not a direct competitor to Steam—to see how their bans look, and you can check it out yourself: [Roblox Ban Reasons](https://www.google.com/search?q=Roblox+ban). Their bans are clear, detailed, and actually explain what you did wrong. I think most decent gaming communities operate like this—not with support agents named Olga, hired through outsourcing, who only know how to send canned auto-replies. Take cases like St4ck—or my friend **moneylead**. All these unbans, like **St4ck’s** or **Alexanddd’s**, happened behind closed doors with zero comments from Steam. Of course, it’s convenient for Steam to handle everything in secret, so no one knows or sees what’s going on—but this violates Steam’s own community rules and principles.\n\n**Who Is moneylead?**  \nI’ve known [moneylead ](https://steamcommunity.com/id/moneylead/)since around 2021. We played Dota 2 a couple of times, and then I just stayed on his friends list. He’s always been a legit player, bringing revenue to Steam through purchases. He never sold his skins, whether in **Dota or CS2—he wasn’t a trader**. All he did was:\n\n* Buy games and skins.\n* Collect badges to level up his profile.\n\nAccording to [SteamSets](https://steamsets.com/account/76561199080934614), he’s given out 324,000 Steam Points—I think he awarded profile rewards to all his friends in the list (though I’m not 100% sure). I do know he ran contests and gave gifts to friends, always supporting the community.\n\n**Steam’s Unfair Treatment**  \nI’ve seen Steam remove his showcases, avatar, description, and even his country multiple times—just because he’s from **Ukraine**. He has a ton of haters leaving toxic comments on his wall, and Steam seems to favor **Russian** users. Every time he tried to appeal the removal of his showcases or profile description—which didn’t break any rules, just had his Instagram link, and his avatar is the same as it is now—Steam moderators didn’t care. **They don’t care about top players who bring them massive revenue, nor about regular users.**\n\n>*Here’s the worst part: moneylead works in cybersecurity, specifically fighting account theft and phishing. He’s neutralized over 5,000 threats targeting Steam alone. And yet, Steam bans him for \"account hijacking\"?*\n\nIf you roughly calculate moneylead’s contribution to Steam and the community—his profile, level, badges (not skins, you can’t sell those)—is this normal, Steam? Banning people, closing tickets, and ignoring users with a spotless reputation who aren’t involved in any commercial activity, just bringing you profit without taking anything in return?\n\n**Steam’s Double Standards**  \nI’m honestly shocked:\n\n* YouTubers who promote casinos and skin gambling? Steam’s fine with that.\n* A cybersecurity expert who fights scams, doesn’t promote casinos, and openly talks about it on his profile? **Banned with no explanation, ignored, and denied an unban.**\n\nI wonder if Steam deliberately bans a high-level account once a year just because of their impunity—maybe for hype or something. Otherwise, this is just madness. It’s scary to think how many regular players have lost their accounts and skins—not because of scammers, but because of Steam’s desire to ignore, send auto-replies, and do whatever they want.\n\n**How Many Others Are Affected?**  \nHow many others are out there—maybe not as well-known—who just have a few games or skins, get banned for nothing, and receive zero explanation or response? **Is this even legal?** Every other platform provides a detailed log with specific violations, but Steam slaps on the same vague label and sends templated responses.\n\n* How safe is it to buy skins on Steam?\n* What’s the chance Steam will just ban your account for no reason, with no explanation?\n\n**A Message to Valve**  \nI wish moneylead the best in resolving this, but Valve, it’d be great if you remembered what \"community\" means and started following the law. Because right now, it looks like your 30% commission, impunity, and sense of being above the law in the U.S. have given you the idea that you can do whatever you want.\n\nI’m sure there are many others like moneylead and St4ck—people who aren’t public or don’t have the resources to fight back. Let’s unite these cases. **If you’re a U.S. resident who’s been banned by Steam without reason and wants to challenge it, please reach out to me.** I’m finishing my **Juris Doctor (J.D.) program at SMU Dedman School of Law** in Dallas, Texas, and I’m participating in a legal clinical practice under Rule 13 of the Texas Supreme Court.\n\nWhat Steam is doing is absolutely disgusting and illegal, and **I’d be happy to help any gamer (legitimate, with no real violations) who has games or skins with value. This will be beneficial for my practice, and it’s time to put Steam in its place and show them they can’t just dictate their own rules with arbitration**. Let’s take it all the way—not for punishment, but for the sake of the community. Maybe if Steam loses a case, they’ll change their policies and start explaining their actions like most popular gaming communities do. Many of us remember how Steam Support used to recover stolen accounts and ended up “stealing” skins themselves—banning without real reasons is basically the same thing, and that’s a serious accusation.\n\nSo, r/Steam, see you soon. I think you understand what you’re doing and how many people you’ve illegally deprived of their assets. I want to raise this issue—not just for the U.S., but for the entire world. You’ve banned class-action lawsuits? **Welcome to Texas.** I recommend starting to look for licensed attorneys in Texas, because I’d love to discuss your company’s policies, feedback, and support agents named Olga—a name that strongly associates with Russian users. Maybe it’d be easier to move your company to Moscow? But I’d be happy to discuss these critical issues on behalf of the global gaming community.\n\nAlso, I wouldn’t recommend ignoring the lawsuit request that will be sent to your physical address and email address, as the court will proceed without you, and that might upset you—especially since things aren’t going so well for a company with stocks like yours.\n\n**Thanks to everyone who took the time to read this. For those who need real help with an unjust Steam ban without any explanation, I’d be happy to assist. For users from Texas, we can easily file a collective lawsuit against Steam—let’s connect and make it happen.**\n02 / Steam development network\nPublic infrastructure.Recorded at scale.\nDownload all 252 records ↓\n\nThe supplied output_steam_network snapshot records repositories, public contributor/fork relationships and profile overlaps. These are published records — what was built, who contributed, what was forked. The paper trail of public capabilities is what Valve must account for.\n\nRepository / description\tContributors\tForkers\tRecorded profiles\nalliedmodders/amxmodx\n\nAMX Mod X - Half-Life 1 Scripting and Administration\n\n\t40\t40\t80\nalliedmodders/sourcemod\n\nSourceMod - Source Engine Scripting and Administration\n\n\t40\t40\t80\nDoctorMcKay/node-steam-user\n\nAllows interaction with the Steam network via the Steam client protocol\n\n\t40\t40\t80\nFacepunch/Facepunch.Steamworks\n\nAnother fucking c# Steamworks implementation\n\n\t40\t40\t80\nJustArchiNET/ArchiSteamFarm\n\nC# application with primary purpose of farming Steam cards from multiple accounts simultaneously.\n\n\t40\t40\t80\nodota/core\n\nOpenDota: Open source Dota 2 data platform with automated replay parsing\n\n\t40\t40\t80\nodota/dotaconstants\n\ndotaconstants: Static data for Dota applications\n\n\t40\t40\t80\nodota/web\n\nOpenDota: React web UI for Dota 2 statistics using the OpenDota platform\n\n\t40\t40\t80\nsplewis/get5\n\nCS:GO Sourcemod plugin for competitive matches/scrims\n\n\t40\t40\t80\nSteamDatabase/FileDetectionRuleSets\n\n🔎 Rules to detect game engines and other technologies based on Steam depot file lists\n\n\t40\t40\t80\nSteamRE/SteamKit\n\nSteamKit2 is a .NET library designed to interoperate with Valve's Steam network. It aims to provide a simple, yet extensible, interface to perform various actions on the network.\n\n\t40\t40\t80\nValveSoftware/dxvk\n\ndxvk tree containing branches used by Proton\n\n\t40\t40\t80\nValveSoftware/GameNetworkingSockets\n\nReliable & unreliable messages over UDP. Robust message fragmentation & reassembly. P2P networking / NAT traversal. Encryption.\n\n\t40\t40\t80\nValveSoftware/gamescope\n\nSteamOS session compositing window manager\n\n\t40\t40\t80\nValveSoftware/Proton\n\nCompatibility tool for Steam Play based on Wine and additional components\n\n\t40\t40\t80\nValveSoftware/source-sdk-2013\n\nThe 2013 edition of the Source SDK\n\n\t40\t40\t80\nValveSoftware/wine\n\nWine with a bit of extra spice\n\n\t40\t40\t80\nValveSoftware/steam-devices\n\nList of devices Steam and SteamVR will want read/write permissions on, to help downstream distributions create udev rules/etc\n\n\t39\t40\t79\nValveSoftware/steam-audio\n\nSteam Audio\n\n\t38\t40\t78\nalliedmodders/metamod-source\n\nMetamod:Source - C++ Plugin Environment and Detour Library for the Source Engine\n\n\t37\t40\t77\nalliedmodders/sourcepawn\n\nA small, statically typed scripting language.\n\n\t35\t40\t75\nValveSoftware/Fossilize\n\nA serialization format for various persistent Vulkan object types.\n\n\t31\t40\t71\nrlabrecque/Steamworks.NET\n\nSteamworks wrapper for Unity / C#\n\n\t27\t40\t67\nModDota/moddota.github.io\n\nModDota github pages project.\n\n\t26\t40\t66\nodota/parser\n\nReplay parse server generating JSON log events from Dota 2 replay files\n\n\t26\t40\t66\nValveSoftware/steam-for-linux\n\nIssue tracking for the Steam for Linux beta client\n\n\t26\t40\t66\nSteamRE/DepotDownloader\n\nSteam depot downloader utilizing the SteamKit2 library.\n\n\t24\t40\t64\nJustArchiNET/ASF-ui\n\nThe official web interface for ASF\n\n\t23\t40\t63\nadvancedfx/advancedfx\n\nHalf-Life Advanced Effects (HLAE) is a tool to enrich content creation mainly for the Counter-Strike series.\n\n\t22\t40\t62\nalliedmodders/ambuild\n\nAlliedModders C++ Build System\n\n\t23\t39\t62\nSteamDatabase/BrowserExtension\n\n💻 SteamDB's extension for Steam websites\n\n\t21\t40\t61\nodota/mobile\n\nReact Native apps for viewing Dota 2 data on Android/iOS\n\n\t19\t40\t59\nValvePython/steam\n\n☁️ Python package for interacting with Steam\n\n\t18\t40\t58\nskadistats/clarity\n\nComically fast Dota 2, CSGO, CS2 and Deadlock replay parser written in Java.\n\n\t13\t40\t53\nSteamRE/open-steamworks\n\nOpen Steamworks is a set of reverse engineered headers for the Valve's Steam Client. More or less abandoned now that the Steamworks SDK is publically available.\n\n\t13\t40\t53\nValveSoftware/Source-1-Games\n\nSource 1 based games such as TF2 and Counter-Strike: Source\n\n\t13\t40\t53\nalliedmodders/hl2sdk\n\nHalf-Life 2 SDK Mirrors\n\n\t11\t40\t51\nSteamDatabase/steamdb.info-issues\n\n🚱 Issue tracker for the SteamDB website\n\n\t11\t40\t51\nCSGOFloat/inspect\n\nSource Code that Powers the CSFloat Inspect Link API\n\n\t10\t40\t50\nValveSoftware/SteamOS\n\nSteamOS community tracker\n\n\t10\t40\t50\nalliedmodders/source2mod\n\nExperimental\n\n\t40\t9\t49\nsmiley/steamapi\n\nAn unofficial object-oriented Python library for accessing the Steam Web API.\n\n\t9\t40\t49\nSteamDatabase/GameTracking\n\n🛢 Dumping things, so you don't have to\n\n\t8\t40\t48\nValveSoftware/counter-strike_rules_and_regs\n\nCS:GO\n\n\t7\t40\t47\nValveSoftware/openvr\n\nOpenVR SDK\n\n\t6\t40\t46\nSteamDatabase/easy-markdown-editor\n\nEasyMDE: A simple, beautiful, and embeddable JavaScript Markdown editor. Delightful editing for beginners and experts alike. Features built-in autosaving and spell checking.\n\n\t40\t4\t44\nValveSoftware/Dota-2\n\nTracker for issues specific to Linux and Mac in the Reborn client. If you have a general issue or non-system-specific feature request please go to dev.dota2.com\n\n\t6\t38\t44\nValveSoftware/Dota2-Gameplay\n\nPublic Bug Tracker for Dota 2\n\n\t4\t40\t44\nJustArchiNET/ArchiBot\n\nNo description in the capture.\n\n\t16\t27\t43\nztizzlegaming/CSGOWinBig\n\nOpen-source Counter-Strike: Global Offensive jackpot betting website.\n\n\t1\t40\t41\nJustArchiNET/mantis.justarchi.net\n\nMantis Bug Tracker (MantisBT)\n\n\t40\t0\t40\nodota/node-steam-user\n\nAllows interaction with the Steam network via the Steam client protocol\n\n\t40\t0\t40\nModDota/TypeScriptAddonTemplate\n\nDota 2 addon template with TypeScript Panorama and VScripts.\n\n\t9\t29\t38\nValvePython/vdf\n\n📜 Package for working with Valve's text and binary KeyValue format\n\n\t6\t32\t38\nalliedmodders/amtl\n\nAlliedModders C++ Template Library\n\n\t17\t19\t36\nValvePython/dota2\n\n🐸 Python package for interacting with Dota 2 Game Coordinator\n\n\t5\t30\t35\nalliedmodders/stripper-source\n\nStripper:Source\n\n\t13\t21\t34\nAllyans3/steam-market-api-v2\n\nSteam Market API v2 package\n\n\t3\t31\t34\nModDota/dota-tutorial\n\nCustom game DOTA tutorial.\n\n\t11\t23\t34\nodota/blog\n\nNo description in the capture.\n\n\t29\t3\t32\nOpsecGuy/BetterGo\n\nExternal CS:GO cheat written in python.\n\n\t1\t27\t28\npxvr-official/1\n\n無許諾配信 企業理念剽窃 動物の森収益化 大神ミオ権利者削除 戌神権利侵害発言 常闇トワ炎上 夜空メルストーカー被害 建築王サポーター放置 赤十字マーク 魔乃アロエ卒業 一つの中國支持声明 大空昴3Dライブ 無限延期清掃員職業差別 日清コラボ楽曲 musedash非公開 rog案件取り消し 壁画ライブ 丁真 Ding Zhen 郑爽 Zheng Shuang 防护林 与朵小天使w 伊月猫凛 本主萌埋午休傻 汪峰 重生细胞 壁纸 比利海灵顿 香蕉君 van 田所浩二 抽象带篮子 抗压背锅吧 季子越 蒋明辉 傻逼…\n\n\t0\t28\t28\nRevadike/InternalSteamWebAPI\n\nDocumenting the unofficial and internal Steam Web API\n\n\t1\t27\t28\nJoeSzymkowiczFiveM/qb-lootcrate\n\nA CSGO-style case opening script\n\n\t2\t25\t27\nAbrarKL/MyRoulette.XYZ\n\nCSGO / Steam Roulette Site created with PHP and Node JS, using the Material Design front-end framework.\n\n\t1\t25\t26\nJustArchiNET/ASF-WebConfigGenerator\n\nNo description in the capture.\n\n\t10\t15\t25\nModDota/dota-data\n\nAuto-generated Dota 2 resource dumps\n\n\t11\t14\t25\nModDota/TypeScriptDeclarations\n\nTypeScript declarations for Dota 2.\n\n\t11\t14\t25\nModDota/API\n\nNo description in the capture.\n\n\t12\t12\t24\nalliedmodders/cssdm\n\nCounter-Strike:Source Deathmatch\n\n\t10\t13\t23\nSteamDatabase/steamstat.us\n\n✅ Front-end of Steam services status website\n\n\t4\t18\t22\nc0deina/csgojackpotV2\n\nCSGO Jackpot Source\n\n\t1\t20\t21\nValvePython/steamctl\n\n🤸 Take control of Steam from your terminal\n\n\t2\t19\t21\nValvePython/csgo\n\n🔫 Python package for interacting with CS:GO Game Coordinator\n\n\t3\t17\t20\nBeepIsla/csgo-crash-exploit\n\nAllows you to crash any Windows user\n\n\t3\t16\t19\nValvePython/vpk\n\n📦 Open, Search, Extract and Create VPKs in python\n\n\t4\t15\t19\nalliedmodders/SM-SteamWorks\n\nExposing SteamWorks functions to SourcePawn.\n\n\t14\t3\t17\nSteamRE/Steam4NET\n\nSteam4NET is a .NET wrapper around the Steamworks C++ interfaces\n\n\t2\t15\t17\nalliedmodders/hl2sdk-manifests\n\nInformation about HL2SDKs shared between Metamod:Source and SourceMod.\n\n\t6\t10\t16\nJustArchiNET/ASF-PluginTemplate\n\nTemplate repository that you can use for creating custom plugins for ArchiSteamFarm.\n\n\t8\t7\t15\nModDota/Dota2AIFramework\n\nGeneral Framework for Dota 2 AI Competitions\n\n\t1\t14\t15\nShkyyl/KeyChamp\n\nExtension for joining free case battle on key-drop automatically\n\n\t1\t14\t15\nSteamDatabase/SteamMonitor\n\n😤 Track Steam's connection manager servers status\n\n\t2\t12\t14\nBaterka/cslore.com\n\nCS:GO gambling site - csgo.style\n\n\t1\t12\t13\nSteamDatabase/SteamTokenDumper\n\n🔢 Submit users' PICS access tokens to SteamDB\n\n\t2\t11\t13\nmonoblocker/roulette\n\nRoulette CS:GO made in React and Typescript\n\n\t1\t11\t12\nzsith/launcher.user.js\n\n// ==UserScript== // @name AposLauncher // @namespace AposLauncher // @include http://agar.io/* // @version 3.062 // @grant none // @author http://www.twitch.tv/apostolique // ==/UserScript== var aposLauncherVersion = 3.062; Nu…\n\n\t1\t11\t12\nLincolnIT/CSGODouble-bot-automated\n\nCSGODouble Automated, auto Betting Bot.\n\n\t1\t10\t11\nvladpuz/steam-market\n\nSteam market API client\n\n\t4\t7\t11\nmcgrizzz/Cstrike.bet\n\nCSGO Roulette Website Angular frontend, nodejs backend, and steam trading bots\n\n\t1\t9\t10\nodota/underlords-web\n\nUI for OpenUnderlords\n\n\t5\t5\t10\nSteamDatabase/SteamToTwitter\n\n🕊 Tweets announcements from various Steam groups\n\n\t1\t9\t10\nModDota/AbilityLuaSpellLibrary\n\nThe successor to the Spell Library by Pizzalol\n\n\t4\t4\t8\nalvinl/bitskins\n\nUnofficial BitSkins API client\n\n\t2\t5\t7\nb1naryth1ef/steamy\n\nA Python Steam community and market API interface that will get you all hot and bothered\n\n\t2\t5\t7\nkratos1812/Case-Opening\n\nIn-game case opening system for CSGO servers.\n\n\t2\t5\t7\nodota/docs\n\nOpenDota API documentation\n\n\t4\t3\t7\nSteamDatabase/steam-advanced-access-fetch-players\n\n📈 Simple script to fetch Steam player count\n\n\t1\t6\t7\nTheRioMiner/CsgoBetterExternalRaytrace\n\nOverridden maps pack for better external raytrace\n\n\t1\t6\t7\nalliedmodders/hl2sdk-mock\n\nMock HL2SDK and Server\n\n\t5\t1\t6\nchristophersu/PySteamMarket\n\nPython API for getting prices from the Steam market.\n\n\t1\t5\t6\nExtremelyd1/Strat-Roulette\n\nCS:GO Sourcemod Plugin\n\n\t2\t4\t6\ngiovanni-orciuolo/double-sdk\n\nA simple way to write CS:GO cheats!\n\n\t2\t4\t6\nJustArchiNET/Madness\n\nMadness embraces your project by including compatibility layer for selected APIs normally not available on .NET Framework target.\n\n\t5\t1\t6\nModDota/TypescriptPanoramaDeclarations\n\nNo description in the capture.\n\n\t4\t2\t6\nodota/rapier\n\nA JavaScript Dota 2 (Source 2) replay parsing library\n\n\t1\t5\t6\nVozn1akHero/CSGOCaseOpeningSimulator\n\nCounter-Strike case opening simulator which resembles the good old CS:GO user interface\n\n\t3\t3\t6\nautarc/steam-store\n\nAPI client for the unofficial steam storefront/big picture resource\n\n\t2\t3\t5\nBETTING-CODE/awesome-esports-sites\n\nA curated list of awesome esport betting sites – live, statistics and other resources.\n\n\t1\t4\t5\njonteohr/Better-Warden\n\nAn improved and more advanced warden plugin with a custom menu for CS:GO jailbreak servers!\n\n\t2\t3\t5\nLudzikk/CSGO-Gambling-Site\n\nhttps://ludzikk.github.io/CSGO-Gambling-Site/\n\n\t1\t4\t5\nModDota/find-steam-app\n\nFind location of an installed Steam app\n\n\t3\t2\t5\nmprey/csgocact.us\n\nsource code for csgocact.us\n\n\t1\t4\t5\nnezu-cc/ServerCrasher\n\nCS:GO Server Crasher\n\n\t1\t4\t5\nodota/testfiles\n\nStores test replay files\n\n\t2\t3\t5\nodota/underlordsconstants\n\nConstant data for Dota Underlords\n\n\t3\t2\t5\nSnaBe/node-steam-market-fetcher\n\nA Node.js wrapper for the Steam Community Market API.\n\n\t2\t3\t5\nSteamDatabase/.github\n\n💗 Organization-wide community health files\n\n\t1\t4\t5\nwolfcon/RIP-HLTV-BET\n\nRIP BET AD (For Tampermonkey) https://greasyfork.org/en/scripts/423484-rip-hltv-bet\n\n\t2\t3\t5\nalliedmodders/blaster.net\n\nSource and GoldSrc Query Tool\n\n\t2\t2\t4\ncatears124/CS2-Price-API\n\nsimple python cs2 steam market price API\n\n\t1\t3\t4\nialakey/caseforge\n\nOpen-source CS2 case-opening platform: Steam auth, provably fair openings, RTP-balanced case builder, withdrawals bought on market.csgo.com and an admin CRM.\n\n\t1\t3\t4\nIlusion9/csgo-fix-mapchange-crash-sm\n\nFix players crash on map change.\n\n\t1\t3\t4\nismail0234/Benson-Map-Crash-Fixer\n\nCSGO Map Change Client Crash Fixer\n\n\t1\t3\t4\njaxwilko/steam-market-api\n\nPHP - Composer Compatible - Steam Market API\n\n\t2\t2\t4\nJustArchiNET/ArchiTag\n\nArchiTag is a very small utility based on Python 3 and Mutagen to provide missing functionality in opusenc of writing specific Opus metadata, such as total number of tracks or track number.\n\n\t1\t3\t4\nModDota/DotaUI\n\nNo description in the capture.\n\n\t2\t2\t4\nnode-steam/market-pricing\n\nWrapper for the unofficial Steam Market Pricing API\n\n\t1\t3\t4\nodota/media\n\nStores media files for Dota projects\n\n\t2\t2\t4\nSergeyIvanovDevelop/Crypto-Steam-Platform\n\nThe repository contains the code and configuration to run a platform for creating cryptocurrency stakes for arbitrary ERC20 tokens.\n\n\t1\t3\t4\nAareksio/csgodouble-floatchecker\n\nAdds context menu option to check item's float value\n\n\t1\t2\t3\nchinm4/CSGOdrop\n\nA online csgo gambling casino that includes a variety of mini games that allows you to win csgo skins\n\n\t2\t1\t3\nCruze03/CSGO-Case-Opening-Prank\n\nCommand:- !prank (Admin flag \"n\" required)\n\n\t1\t2\t3\nDhruva-Kapadia/CSGOTrollGG\n\nCSGO Case Opening Simulator\n\n\t2\t1\t3\nErhanCSGO/CSGOPolygon-prediction\n\nCSGOPolygon.com - prediction script, double your coins by using this tool\n\n\t1\t2\t3\nEv-Hoang/Bedrock-Chest-Case-Opening\n\nHypixel Skyblock Dungeon Mod - Bedrock Chest Opening Animation (CSGO Style)\n\n\t1\t2\t3\njmjp/csgo-roulette\n\nA csgo gambling roulette make with VueJS 3\n\n\t2\t1\t3\nJustArchiNET/ArchiCrowdin\n\nNo description in the capture.\n\n\t1\t2\t3\nLeonSK/WearMarketInspector\n\nRetrieve Wear Value (Float Value) and Pattern Index from Steam Community Market using http://csgo.exchange API\n\n\t1\t2\t3\nmaximgeerinck/csgo-gamble\n\nCSGO gambling website\n\n\t1\t2\t3\nModDota/BugTracker\n\nListing bugs for Dota 2 Custom Games\n\n\t2\t1\t3\nplwp/mma-betting\n\nUFC/MMA betting model with Pinnacle steam detection for AU book latency arb\n\n\t2\t1\t3\nSouthsideswag16/Csgo-Gambling-Site\n\nNo description in the capture.\n\n\t2\t1\t3\ntacyarg/csgofiesta-frontend-react\n\nRemastered version a the long time favorite csgo site\n\n\t2\t1\t3\nVelorasse/Mutah-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-csmoney-csgoskins\n\ngambling script for Mutah, Keydrop, csmoney, and csgoskins, featuring hacks, cheats, and predictors. Offers strategies to boost winning odds and optimize performance on these platforms.\n\n\t3\t0\t3\nalliedmodders/am-github-artifact-webhook\n\nNo description in the capture.\n\n\t2\t0\t2\ncharamza/roulette\n\nCSGO like roulette in JS\n\n\t1\t1\t2\nCruze03/CSGO-PugSetup-RoundRestore\n\nSometimes (player dropped/crashed) which would be disadvantage for a team. It would be very handy to restore the match to the previous round.\n\n\t1\t1\t2\ncsgorol/CSGO-ROLL-Crash-Predictor\n\nCSGO-ROLL-Crash-Predictor\n\n\t1\t1\t2\nFoxSerito/FOXWORLD_plugin_DoubleJump_CSGO\n\nПлагин SourceMod (CSGO). Двойной прыжок с эффектом.\n\n\t1\t1\t2\nhkehayovmoonbiz/CS2-Casino-Full-Source-Code\n\nCS2, CS2 betting platforms, Skin Roulette, Case Unboxing, Crash games, Jackpot, purchase CS2 casino source, crypto gambling\n\n\t1\t1\t2\nJustZakary/steamstoreapi\n\nThis NPM module is a API wrapper that makes the steam unofficial API easier to use.\n\n\t2\t0\t2\njzimr/steam-market-api\n\nA java library to easily get Steam Community Market data\n\n\t1\t1\t2\nMomohime/CSGO.Network-Jackpot-Coinflip\n\nNo description in the capture.\n\n\t1\t1\t2\nnnjjswat/moneybot\n\nautomated bots for bustabit (formerly known as moneypot), csgo crash, etc\n\n\t0\t2\t2\nodota/carry\n\nLegacy Application for donations to the OpenDota project\n\n\t1\t1\t2\nodota/PublicMatchDataBot\n\nA Discord bot to remind users to turn on Expose Public Match Data in the Dota 2 client\n\n\t1\t1\t2\nOrillio/CSGOBet.com\n\nCSGO roulette web app\n\n\t2\t0\t2\nripexz/csgo-bet-alert\n\nA Chrome extension to keep track of active CS:GO Lounge matches.\n\n\t1\t1\t2\nrrpvm/lumen_sense-beta-deprecated-\n\nthis is internal csgo cheat written by me(no paste, self reverse structures). start : ~6 August 2020, end : ~ 14 December 2020\n\n\t1\t1\t2\nRuthless222/csgoscore\n\nThis is a Counter Strike Global Offensive Betting Site. You chose the skins you want to bet and try to win jackpots\n\n\t2\t0\t2\ntfburns/CSGO-cases-PL\n\nExpected profit-loss of CS:GO case openings\n\n\t1\t1\t2\nTomDra/CSGO-Case-Data-Analysis\n\nWorks out the most profitable CS:GO case at that current time\n\n\t1\t1\t2\nValvePython/dota2-wrappers\n\nNo description in the capture.\n\n\t1\t1\t2\nValvePython/teamfortress2-closed-captions\n\nThis project aims to provide a set of closed captions for Team Fortress 2\n\n\t1\t1\t2\nVistaNetGTX/Cstrike.bet-\n\nCSGO Roulette Website Angular frontend, nodejs backend, and steam trading bots\n\n\t1\t1\t2\nwafflas/csgo-case-opening-simulator\n\nI created a cs go case opening simulator for a meme coin\n\n\t0\t2\t2\nAdmiral-Enigma/Le_Coinflip\n\nConflip game\n\n\t1\t0\t1\nadryeljuliao/roulette-csgo\n\nNo description in the capture.\n\n\t1\t0\t1\nAndreuTheG/csgo-coinflip-web\n\nCSGO Gambling Coinflip Website\n\n\t1\t0\t1\nasmilen/csgoDouble\n\na b c\n\n\t1\t0\t1\nb1naryth1ef/csgofort\n\nA CSGO portal for trading, betting, analytics, and more!\n\n\t1\t0\t1\nBaterka/PrivateSteamBettingWebsite2024\n\nPrivate Steam (Counter-Strike 2) betting/gambling website - Roulette, Jackpot\n\n\t1\t0\t1\nblackcaer/SteamTradeHandler\n\nAutomation of Steam trading. Helper project for bet automation.\n\n\t1\t0\t1\nBTheCoderr/theRounders\n\nThe Rounders - A professional-grade sports betting analytics platform combining real-time odds tracking, sharp movement detection, and advanced statistical analysis. Features include line shopping, steam move alerts, power rankings, and comprehensive bet t…\n\n\t1\t0\t1\nCallumHemsley/KazeBot\n\nA Twitch chat betting bot for CSGO, simply bet a certain amount of points, and double if you win, lose all if you lose. Simple.\n\n\t1\t0\t1\nchrisjpm/CSGOJackpotTemplate\n\nFront end for a jackpot site\n\n\t1\t0\t1\ncolinsenner/valve-bug-bounty\n\nFor many years CS:GO, Dota 2, and Team Fortress 2 servers had a bug that allowed malicious users to leak crucial server process memory or reliably crash any server.\n\n\t1\t0\t1\ncoryypeters/nrl-odds-intelligence-pipeline\n\nReal-time sports betting odds intelligence — streaming pipeline that detects line movement, steam, and arbitrage across bookmakers. Python · Redis Streams · FastAPI · React.\n\n\t1\t0\t1\ndeissh/dev-csgoduo\n\nCS:GO. Bot for receiving things on the site (Polygon, Duo, Double and etc).\n\n\t1\t0\t1\ndom1torii/even-better-font-manager\n\nSimply even better cross-platform tool for CS2 Font Management\n\n\t1\t0\t1\nDONnicov/CSGO-crash-black-screen-\n\nsolution csgo crash black screen and close csgo\n\n\t1\t0\t1\nDoubleBoters/CsgoDouble\n\nNo description in the capture.\n\n\t1\t0\t1\ndownarowiczd/DoubleBot\n\nAn old CSGO Double Bot written for my friend. - 07.05.2016\n\n\t1\t0\t1\nErayBahar/steammarketscraper\n\nSteam Market Scraper Python-based tool that tracks real-time CS2 skin prices using Steam's hidden API. It fetches the lowest sell and highest buy offers for any item, helping you monitor deals or snipe underpriced listings automatically.\n\n\t1\t0\t1\nfairydarkness/SteamwebmailAPI\n\nUnofficial Python API for steamwebmail.com Fast, lightweight, and browserless library for automating steamwebmail.com. Support for session management, proxy, folder navigation, and message retrieval\n\n\t1\t0\t1\nFAQU2/CSGO-Coinflip-MyJailShop\n\nSourcemod plugin which provides a Coinflip system for MyJailShop.\n\n\t1\t0\t1\nFlamesONE/csgo-case-opening\n\nNo description in the capture.\n\n\t1\t0\t1\nFunnyRain/csgorun-crash-watch\n\n🚀 CsgoRun dump crash. / 🚀 CsgoRun дамп крашей.\n\n\t1\t0\t1\ngeohdgio/Venatus-Autenticator\n\nეს არის Steam Autenticator ქართული Venatus Trade & Betting ისთვის და Valve News Georgia-სთვის.\n\n\t1\t0\t1\nhakanstarlord/steam-bot\n\nSports betting steam-move signal detection with ML pipeline (XGBoost stacking + isotonic calibration), backtesting engine, Flask dashboard, and Telegram alerts.\n\n\t1\t0\t1\nHvH-gg/CSGO-Item-CrashFix\n\nA plugin for Counter-Strike: Global Offensive that fixes an exploit where receiving CS2 Items will cause CS:GO clients to crash\n\n\t1\t0\t1\nHvH-gg/CSGO-NetMsg-CrashFix\n\nA plugin for Counter-Strike: Global Offensive that fixes an exploit where spamming NetMsg_StringCmd packets would result in a server crash.\n\n\t1\t0\t1\nisybycnsmam/SteamLibrary\n\nLegacy Steam Unofficial API\n\n\t1\t0\t1\nItsTangerine/SteamApis.Net\n\nUnofficial https://steamapis.com .NET library, supporting .NET 6.0+\n\n\t1\t0\t1\nJustArchiNET/JustArchi.net\n\nNo description in the capture.\n\n\t1\t0\t1\nkiri-osint/CS2-Info-Hub-Bot\n\nA Telegram bot that acts as a hub for CS2 players, providing real-time skin prices, server stats, and user profile/inventory inspection using official and unofficial Steam APIs.\n\n\t1\t0\t1\nKoshkaj/monte\n\nGamified csgo gambling platform implementation\n\n\t1\t0\t1\nmadsab/CaseOpening\n\nA school project using Java. Simulating the case opening from CSGO and more.\n\n\t1\t0\t1\nman90es/steamcardexchange-api\n\nSteamCardExchange.net unofficial REST API server (scraper).\n\n\t1\t0\t1\nMattPua/steam-unofficial-docs\n\nUnofficial docs for Steam APIs with fumadocs\n\n\t1\t0\t1\nMetallist1/Portfolio.CsgoWinGambleProject\n\nA website that was done in 2017 September. Websites focus was on gambling with Counter-Strike items. Project was largely completed however backups were not done correctly, this resulted in half a year of wasted improvements to the code. The website was test…\n\n\t1\t0\t1\nmikebobadilla/csgo-jackpot\n\nNo description in the capture.\n\n\t0\t1\t1\nmikebobadilla/meteor-csgojackpot\n\nCssgo Jackpot done in meteor\n\n\t1\t0\t1\nModDota/D2VDump\n\nDota 2 Server VScript API Dumper\n\n\t1\t0\t1\nModDota/DotaTracking\n\nNo description in the capture.\n\n\t1\t0\t1\nModDota/eslint-config\n\nESLint config by ark120202\n\n\t1\t0\t1\nmr-codinglv/Casino-script\n\nscript casino - script betting - exchange script - bc casino - casino csgo - script bet - betwin script\n\n\t1\t0\t1\nMrKeelik/MrKeel\n\nCSGO DOUBLE BOT\n\n\t1\t0\t1\nnoahlatzel/CSGORollHelper\n\nLeveraging positive expected value on triple green jackpots on CSGORoll!\n\n\t1\t0\t1\noddsgpt/oddsgpt-market-intelligence\n\nResearch on football betting markets, closing odds, CLV, market efficiency, steam moves, AI betting systems, and sports market intelligence.\n\n\t1\t0\t1\noEXU/csgo-server-crasher\n\nCSGO SERVER CRASHER\n\n\t1\t0\t1\nPrdTTony/CSGO-Roulette\n\n[CSGO] Roulette System. Bet on RED or Black and win x2 credits\n\n\t1\t0\t1\nr-adamski/csgo-jackpot\n\nNo description in the capture.\n\n\t1\t0\t1\nSahotallo/Turan-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-Skinbaron-hellcase\n\ngambling script for Turan, Keydrop, Skinbaron, and Hellcase, providing hacks, cheats, and predictors. Includes strategies to improve winning chances and enhance gameplay on these platforms.\n\n\t1\t0\t1\nsamuelcsouza/steam-marketplace-api\n\nAn unofficial API to get data from the Steam Marketplace.\n\n\t1\t0\t1\nSKINSTRACK/CS2-Price-API\n\nSkinstrack offers a free, limited API endpoint that returns Steam item prices. Paid plans additionally provide access to pricing data from multiple marketplaces, making it possible to compare prices across different markets through a single API.\n\n\t1\t0\t1\nsnmtriet/CSGO-Casino-Full-Source-Code\n\nCSGO, CSGOEmpire, Case Opening, Case Battles, Roulette, Coinflip, buy csgo gambling site, gambling\n\n\t1\t0\t1\nSteamRE/homebrew-tools\n\nRepository for installation of SteamRE tools via Homebrew (http://brew.sh)\n\n\t1\t0\t1\nSteamRE/opensteamworks.org\n\nNo description in the capture.\n\n\t1\t0\t1\nTheQuack45/CsgoCaseOpenProgram\n\nSimple program to parse an XML file with CS:GO case information and \"simulate\" case openings\n\n\t1\t0\t1\nTLClassless/StratRouletteCSGO\n\nA 'Strat Roulette' web app for CS:GO!\n\n\t1\t0\t1\ntomasoom/csgoCaseOpening\n\nNo description in the capture.\n\n\t1\t0\t1\nvitaliy-evsyukov/steamgifts-autobet-bookmarklet\n\nbookmarklet for automatic bets on steamgifts.com\n\n\t1\t0\t1\nXpravdaX/RouletteCSGO\n\nNo description in the capture.\n\n\t1\t0\t1\nYuiKasumii/steam_api_unofficial\n\nUnofficial Steam Game Information Database\n\n\t1\t0\t1\nZexuz/Steam-Betting\n\nA betting website build ontop of STEAM's ecosystem\n\n\t1\t0\t1\nANK-RULZZ/steam-jackpot-site\n\ngetting some errors and would like some one to help me with it thank you!!!\n\n\t0\t0\t0\nasmilen/CsgoDoubleVS\n\nNo description in the capture.\n\n\t0\t0\t0\nCORNOODOSADAS/CSGOWeed\n\nCsgo Jackpot and Coinflip\n\n\t0\t0\t0\nCSGOApple/csgoapple\n\nJackpot Site\n\n\t0\t0\t0\nCSGOFAST/csgofast-api\n\nNo description in the capture.\n\n\t0\t0\t0\nDonakall/csgoDoublebot\n\nAutomated bot for csgodouble\n\n\t0\t0\t0\nfedor-selivanov/csgo-fast-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nfoldageros/csgod\n\ndouble bot\n\n\t0\t0\t0\ngmod-gambling/gmod-gambling\n\nNo description in the capture.\n\n\t0\t0\t0\nierome/CSGOBoss-BackEnd\n\nBack end version of CSGOBoss. This was a CSGO Gambling site named CSGOBoss. Coded by an old friend of mine Dahquan Hinds (https://github.com/dahquan/) Thought I would release this to help out any one who would need it.\n\n\t0\t0\t0\njamienp1/CSGODOUBLE-BOT-AUTO\n\ni got a bot thats is betting on the last winning color except from green and if you lose it will double the coins you set it to bet, pretty good, so when there comes a loooong train you will be gaining a bit of money codepaste_net/ugmt92 remove all the _ an…\n\n\t0\t0\t0\nJEYONER/CSGOTOXIC\n\nPAGINA DE JACKPOT CSGO SKINS\n\n\t0\t0\t0\nkalrish/csgo-jackpot\n\nStressful but funny zombie-like Counter-Strike: Global Offensive game mode.\n\n\t0\t0\t0\nkrys12345/roulettee\n\n// ==UserScript== // @name CSGO Predict Bot // @namespace http://csgodouble.com // @version 1.0 // @description predicts what number its gonna be // @author Meee // @match http://www.csgodouble.com/ // @grant none // ==/…\n\n\t0\t0\t0\nLilDuggiMuffi/CSGODouble-Working-Bot\n\nFixed CSGO Double Bot\n\n\t0\t0\t0\nLyricLy/Steam2Proton\n\nCheck if all your Steam games will work with Proton! Uses the official Steam API and the unofficial Proton API.\n\n\t0\t0\t0\nM0NsTeR77/csgo-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nozanhalis/Hi\n\n// ==UserScript== // @name CS GO LOUNGE BOT-Ozan Halis // @namespace http://csgolounge.com/ // @version 0.6.6 // @description Cs Go Lounge Hızlı BOT // @match http://csgolounge.com/* // @match http://dota2lounge.com/* // @updateURL h…\n\n\t0\t0\t0\nscoobertus/CSGO-DoubleBot\n\nNo description in the capture.\n\n\t0\t0\t0\nTradeal/CSGO-Jackpot-Bot\n\nNo description in the capture.\n\n\t0\t0\t0\nValvePython/artifact\n\nNo description in the capture.\n\n\t0\t0\t0\nVampire/CSGO-Roulette-Bot\n\nNo description in the capture.\n\n\t0\t0\t0\nvdemans/csgo-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nVocoreVideo/CSGODungeon-\n\nCSGO Jackpot\n\n\t0\t0\t0\nwayz-dev/csgofloat\n\nNo description in the capture.\n\n\t0\t0\t0\n\nSnapshot: 17 September 2026, 11:19:11 as written in the source; timezone unspecified. Relationship collection is capped in the export (many categories stop at 40). Contributors and forkers sum to 4,554 role entries across 4,214 distinct profile–repository pairs; a profile can have both roles. Zero means no records captured in that category. Repository names may include aliases or case variants; totals retain the source’s counting conventions.\n\nSource provenance\nBuilt from your collected files.\nSupport testimony\n2323/reddit_scams_ultra/steam_support_tickets_MEGA.json · rows 45, 58, 107, 110, 294\nNetwork snapshot\nnetwork-repositories.csv · raw_data.json · overlaps.csv · summary.txt (historical source paths retained in manifest)\n\nThe manifest records source paths, byte sizes, SHA-256 hashes and selected record positions. Raw captures remain separate from the investigation’s interpretation.\n\nDownload source manifest ↓",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam Enforcement Evidence — Support Records & Developer Network"
          },
          {
            "level": 2,
            "id": null,
            "text": "Read the complaint.Keep the source attached."
          },
          {
            "level": 3,
            "id": null,
            "text": "Permanent sanction & closed appeals"
          },
          {
            "level": 4,
            "id": null,
            "text": "Permanently banned Steam account without a clear explanation, need help!"
          },
          {
            "level": 3,
            "id": null,
            "text": "Account recovery & a reported $10,000 loss"
          },
          {
            "level": 4,
            "id": null,
            "text": "Got $10k stollen from steam inventory due to steam' support fault."
          },
          {
            "level": 3,
            "id": null,
            "text": "A reported $500+ loss & template replies"
          },
          {
            "level": 4,
            "id": null,
            "text": "Funds stolen through steam market. Disappointed with Steam response.(or lackthereof)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam Guard & an item-restoration refusal"
          },
          {
            "level": 4,
            "id": null,
            "text": "Many people are losing item via clicking links where steam guard is enabled and steam support doesn't not restore items."
          },
          {
            "level": 3,
            "id": null,
            "text": "Selective enforcement & an unexplained ban"
          },
          {
            "level": 4,
            "id": null,
            "text": "🚨 Steam Bans Without Reason and Ignores Its Community — What’s Going On?"
          },
          {
            "level": 2,
            "id": null,
            "text": "Public infrastructure.Recorded at scale."
          },
          {
            "level": 2,
            "id": null,
            "text": "Built from your collected files."
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/de/steam_enforcement_evidence.html",
          "https://phishdestroy.io/steam_dossier/de/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/de/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/selected-support-records.json",
          "https://phishdestroy.io/steam_dossier/de/investigation_part2.html#outsourcing-case",
          "https://www.reddit.com/r/ohnePixel/comments/1hahqx2/permanently_banned_steam_account_without_a_clear/",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://www.reddit.com/r/DotA2/comments/r55bd7/many_people_are_losing_item_via_clicking_links/",
          "https://www.reddit.com/r/SteamUncensored/comments/1kjt2fa/steam_bans_without_reason_and_ignores_its/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/network-repositories.csv",
          "https://github.com/alliedmodders/amxmodx",
          "https://github.com/alliedmodders/sourcemod",
          "https://github.com/DoctorMcKay/node-steam-user",
          "https://github.com/Facepunch/Facepunch.Steamworks",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://github.com/odota/core",
          "https://github.com/odota/dotaconstants",
          "https://github.com/odota/web",
          "https://github.com/splewis/get5",
          "https://github.com/SteamDatabase/FileDetectionRuleSets",
          "https://github.com/SteamRE/SteamKit",
          "https://github.com/ValveSoftware/dxvk",
          "https://github.com/ValveSoftware/GameNetworkingSockets",
          "https://github.com/ValveSoftware/gamescope",
          "https://github.com/ValveSoftware/Proton",
          "https://github.com/ValveSoftware/source-sdk-2013",
          "https://github.com/ValveSoftware/wine",
          "https://github.com/ValveSoftware/steam-devices",
          "https://github.com/ValveSoftware/steam-audio",
          "https://github.com/alliedmodders/metamod-source",
          "https://github.com/alliedmodders/sourcepawn",
          "https://github.com/ValveSoftware/Fossilize",
          "https://github.com/rlabrecque/Steamworks.NET",
          "https://github.com/ModDota/moddota.github.io",
          "https://github.com/odota/parser",
          "https://github.com/ValveSoftware/steam-for-linux",
          "https://github.com/SteamRE/DepotDownloader",
          "https://github.com/JustArchiNET/ASF-ui",
          "https://github.com/advancedfx/advancedfx",
          "https://github.com/alliedmodders/ambuild",
          "https://github.com/SteamDatabase/BrowserExtension",
          "https://github.com/odota/mobile",
          "https://github.com/ValvePython/steam",
          "https://github.com/skadistats/clarity",
          "https://github.com/SteamRE/open-steamworks",
          "https://github.com/ValveSoftware/Source-1-Games",
          "https://github.com/alliedmodders/hl2sdk",
          "https://github.com/SteamDatabase/steamdb.info-issues",
          "https://github.com/CSGOFloat/inspect",
          "https://github.com/ValveSoftware/SteamOS",
          "https://github.com/alliedmodders/source2mod",
          "https://github.com/smiley/steamapi",
          "https://github.com/SteamDatabase/GameTracking",
          "https://github.com/ValveSoftware/counter-strike_rules_and_regs",
          "https://github.com/ValveSoftware/openvr",
          "https://github.com/SteamDatabase/easy-markdown-editor",
          "https://github.com/ValveSoftware/Dota-2",
          "https://github.com/ValveSoftware/Dota2-Gameplay",
          "https://github.com/JustArchiNET/ArchiBot",
          "https://github.com/ztizzlegaming/CSGOWinBig",
          "https://github.com/JustArchiNET/mantis.justarchi.net",
          "https://github.com/odota/node-steam-user",
          "https://github.com/ModDota/TypeScriptAddonTemplate",
          "https://github.com/ValvePython/vdf",
          "https://github.com/alliedmodders/amtl",
          "https://github.com/ValvePython/dota2",
          "https://github.com/alliedmodders/stripper-source",
          "https://github.com/Allyans3/steam-market-api-v2",
          "https://github.com/ModDota/dota-tutorial",
          "https://github.com/odota/blog",
          "https://github.com/OpsecGuy/BetterGo",
          "https://github.com/pxvr-official/1",
          "https://github.com/Revadike/InternalSteamWebAPI",
          "https://github.com/JoeSzymkowiczFiveM/qb-lootcrate",
          "https://github.com/AbrarKL/MyRoulette.XYZ",
          "https://github.com/JustArchiNET/ASF-WebConfigGenerator",
          "https://github.com/ModDota/dota-data",
          "https://github.com/ModDota/TypeScriptDeclarations",
          "https://github.com/ModDota/API",
          "https://github.com/alliedmodders/cssdm",
          "https://github.com/SteamDatabase/steamstat.us",
          "https://github.com/c0deina/csgojackpotV2",
          "https://github.com/ValvePython/steamctl",
          "https://github.com/ValvePython/csgo",
          "https://github.com/BeepIsla/csgo-crash-exploit",
          "https://github.com/ValvePython/vpk",
          "https://github.com/alliedmodders/SM-SteamWorks",
          "https://github.com/SteamRE/Steam4NET",
          "https://github.com/alliedmodders/hl2sdk-manifests",
          "https://github.com/JustArchiNET/ASF-PluginTemplate",
          "https://github.com/ModDota/Dota2AIFramework",
          "https://github.com/Shkyyl/KeyChamp",
          "https://github.com/SteamDatabase/SteamMonitor",
          "https://github.com/Baterka/cslore.com",
          "https://github.com/SteamDatabase/SteamTokenDumper",
          "https://github.com/monoblocker/roulette",
          "https://github.com/zsith/launcher.user.js",
          "https://github.com/LincolnIT/CSGODouble-bot-automated",
          "https://github.com/vladpuz/steam-market",
          "https://github.com/mcgrizzz/Cstrike.bet",
          "https://github.com/odota/underlords-web",
          "https://github.com/SteamDatabase/SteamToTwitter",
          "https://github.com/ModDota/AbilityLuaSpellLibrary",
          "https://github.com/alvinl/bitskins",
          "https://github.com/b1naryth1ef/steamy",
          "https://github.com/kratos1812/Case-Opening",
          "https://github.com/odota/docs",
          "https://github.com/SteamDatabase/steam-advanced-access-fetch-players",
          "https://github.com/TheRioMiner/CsgoBetterExternalRaytrace",
          "https://github.com/alliedmodders/hl2sdk-mock",
          "https://github.com/christophersu/PySteamMarket",
          "https://github.com/Extremelyd1/Strat-Roulette",
          "https://github.com/giovanni-orciuolo/double-sdk",
          "https://github.com/JustArchiNET/Madness",
          "https://github.com/ModDota/TypescriptPanoramaDeclarations",
          "https://github.com/odota/rapier",
          "https://github.com/Vozn1akHero/CSGOCaseOpeningSimulator",
          "https://github.com/autarc/steam-store",
          "https://github.com/BETTING-CODE/awesome-esports-sites",
          "https://github.com/jonteohr/Better-Warden",
          "https://github.com/Ludzikk/CSGO-Gambling-Site",
          "https://github.com/ModDota/find-steam-app",
          "https://github.com/mprey/csgocact.us",
          "https://github.com/nezu-cc/ServerCrasher",
          "https://github.com/odota/testfiles",
          "https://github.com/odota/underlordsconstants",
          "https://github.com/SnaBe/node-steam-market-fetcher",
          "https://github.com/SteamDatabase/.github",
          "https://github.com/wolfcon/RIP-HLTV-BET",
          "https://github.com/alliedmodders/blaster.net",
          "https://github.com/catears124/CS2-Price-API",
          "https://github.com/ialakey/caseforge",
          "https://github.com/Ilusion9/csgo-fix-mapchange-crash-sm",
          "https://github.com/ismail0234/Benson-Map-Crash-Fixer",
          "https://github.com/jaxwilko/steam-market-api",
          "https://github.com/JustArchiNET/ArchiTag",
          "https://github.com/ModDota/DotaUI",
          "https://github.com/node-steam/market-pricing",
          "https://github.com/odota/media",
          "https://github.com/SergeyIvanovDevelop/Crypto-Steam-Platform",
          "https://github.com/Aareksio/csgodouble-floatchecker",
          "https://github.com/chinm4/CSGOdrop",
          "https://github.com/Cruze03/CSGO-Case-Opening-Prank",
          "https://github.com/Dhruva-Kapadia/CSGOTrollGG",
          "https://github.com/ErhanCSGO/CSGOPolygon-prediction",
          "https://github.com/Ev-Hoang/Bedrock-Chest-Case-Opening",
          "https://github.com/jmjp/csgo-roulette",
          "https://github.com/JustArchiNET/ArchiCrowdin",
          "https://github.com/LeonSK/WearMarketInspector",
          "https://github.com/maximgeerinck/csgo-gamble",
          "https://github.com/ModDota/BugTracker",
          "https://github.com/plwp/mma-betting",
          "https://github.com/Southsideswag16/Csgo-Gambling-Site",
          "https://github.com/tacyarg/csgofiesta-frontend-react",
          "https://github.com/Velorasse/Mutah-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-csmoney-csgoskins",
          "https://github.com/alliedmodders/am-github-artifact-webhook",
          "https://github.com/charamza/roulette",
          "https://github.com/Cruze03/CSGO-PugSetup-RoundRestore",
          "https://github.com/csgorol/CSGO-ROLL-Crash-Predictor",
          "https://github.com/FoxSerito/FOXWORLD_plugin_DoubleJump_CSGO",
          "https://github.com/hkehayovmoonbiz/CS2-Casino-Full-Source-Code",
          "https://github.com/JustZakary/steamstoreapi",
          "https://github.com/jzimr/steam-market-api",
          "https://github.com/Momohime/CSGO.Network-Jackpot-Coinflip",
          "https://github.com/nnjjswat/moneybot",
          "https://github.com/odota/carry",
          "https://github.com/odota/PublicMatchDataBot",
          "https://github.com/Orillio/CSGOBet.com",
          "https://github.com/ripexz/csgo-bet-alert",
          "https://github.com/rrpvm/lumen_sense-beta-deprecated-",
          "https://github.com/Ruthless222/csgoscore",
          "https://github.com/tfburns/CSGO-cases-PL",
          "https://github.com/TomDra/CSGO-Case-Data-Analysis",
          "https://github.com/ValvePython/dota2-wrappers",
          "https://github.com/ValvePython/teamfortress2-closed-captions",
          "https://github.com/VistaNetGTX/Cstrike.bet-",
          "https://github.com/wafflas/csgo-case-opening-simulator",
          "https://github.com/Admiral-Enigma/Le_Coinflip",
          "https://github.com/adryeljuliao/roulette-csgo",
          "https://github.com/AndreuTheG/csgo-coinflip-web",
          "https://github.com/asmilen/csgoDouble",
          "https://github.com/b1naryth1ef/csgofort",
          "https://github.com/Baterka/PrivateSteamBettingWebsite2024",
          "https://github.com/blackcaer/SteamTradeHandler",
          "https://github.com/BTheCoderr/theRounders",
          "https://github.com/CallumHemsley/KazeBot",
          "https://github.com/chrisjpm/CSGOJackpotTemplate",
          "https://github.com/colinsenner/valve-bug-bounty",
          "https://github.com/coryypeters/nrl-odds-intelligence-pipeline",
          "https://github.com/deissh/dev-csgoduo",
          "https://github.com/dom1torii/even-better-font-manager",
          "https://github.com/DONnicov/CSGO-crash-black-screen-",
          "https://github.com/DoubleBoters/CsgoDouble",
          "https://github.com/downarowiczd/DoubleBot",
          "https://github.com/ErayBahar/steammarketscraper",
          "https://github.com/fairydarkness/SteamwebmailAPI",
          "https://github.com/FAQU2/CSGO-Coinflip-MyJailShop",
          "https://github.com/FlamesONE/csgo-case-opening",
          "https://github.com/FunnyRain/csgorun-crash-watch",
          "https://github.com/geohdgio/Venatus-Autenticator",
          "https://github.com/hakanstarlord/steam-bot",
          "https://github.com/HvH-gg/CSGO-Item-CrashFix",
          "https://github.com/HvH-gg/CSGO-NetMsg-CrashFix",
          "https://github.com/isybycnsmam/SteamLibrary",
          "https://github.com/ItsTangerine/SteamApis.Net",
          "https://github.com/JustArchiNET/JustArchi.net",
          "https://github.com/kiri-osint/CS2-Info-Hub-Bot",
          "https://github.com/Koshkaj/monte",
          "https://github.com/madsab/CaseOpening",
          "https://github.com/man90es/steamcardexchange-api",
          "https://github.com/MattPua/steam-unofficial-docs",
          "https://github.com/Metallist1/Portfolio.CsgoWinGambleProject",
          "https://github.com/mikebobadilla/csgo-jackpot",
          "https://github.com/mikebobadilla/meteor-csgojackpot",
          "https://github.com/ModDota/D2VDump",
          "https://github.com/ModDota/DotaTracking",
          "https://github.com/ModDota/eslint-config",
          "https://github.com/mr-codinglv/Casino-script",
          "https://github.com/MrKeelik/MrKeel",
          "https://github.com/noahlatzel/CSGORollHelper",
          "https://github.com/oddsgpt/oddsgpt-market-intelligence",
          "https://github.com/oEXU/csgo-server-crasher",
          "https://github.com/PrdTTony/CSGO-Roulette",
          "https://github.com/r-adamski/csgo-jackpot",
          "https://github.com/Sahotallo/Turan-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-Skinbaron-hellcase",
          "https://github.com/samuelcsouza/steam-marketplace-api",
          "https://github.com/SKINSTRACK/CS2-Price-API",
          "https://github.com/snmtriet/CSGO-Casino-Full-Source-Code",
          "https://github.com/SteamRE/homebrew-tools",
          "https://github.com/SteamRE/opensteamworks.org",
          "https://github.com/TheQuack45/CsgoCaseOpenProgram",
          "https://github.com/TLClassless/StratRouletteCSGO",
          "https://github.com/tomasoom/csgoCaseOpening",
          "https://github.com/vitaliy-evsyukov/steamgifts-autobet-bookmarklet",
          "https://github.com/XpravdaX/RouletteCSGO",
          "https://github.com/YuiKasumii/steam_api_unofficial",
          "https://github.com/Zexuz/Steam-Betting",
          "https://github.com/ANK-RULZZ/steam-jackpot-site",
          "https://github.com/asmilen/CsgoDoubleVS",
          "https://github.com/CORNOODOSADAS/CSGOWeed",
          "https://github.com/CSGOApple/csgoapple",
          "https://github.com/CSGOFAST/csgofast-api",
          "https://github.com/Donakall/csgoDoublebot",
          "https://github.com/fedor-selivanov/csgo-fast-roulette",
          "https://github.com/foldageros/csgod",
          "https://github.com/gmod-gambling/gmod-gambling",
          "https://github.com/ierome/CSGOBoss-BackEnd",
          "https://github.com/jamienp1/CSGODOUBLE-BOT-AUTO",
          "https://github.com/JEYONER/CSGOTOXIC",
          "https://github.com/kalrish/csgo-jackpot",
          "https://github.com/krys12345/roulettee",
          "https://github.com/LilDuggiMuffi/CSGODouble-Working-Bot",
          "https://github.com/LyricLy/Steam2Proton",
          "https://github.com/M0NsTeR77/csgo-roulette",
          "https://github.com/ozanhalis/Hi",
          "https://github.com/scoobertus/CSGO-DoubleBot",
          "https://github.com/Tradeal/CSGO-Jackpot-Bot",
          "https://github.com/ValvePython/artifact",
          "https://github.com/Vampire/CSGO-Roulette-Bot",
          "https://github.com/vdemans/csgo-roulette",
          "https://github.com/VocoreVideo/CSGODungeon-",
          "https://github.com/wayz-dev/csgofloat",
          "https://phishdestroy.io/steam_dossier/output_steam_network/raw_data.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/enforcement-source-manifest.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/en/steam_enforcement_evidence.content.json",
      "export_json_sha256": "9de6b7a6f3d9cc91f3a9236206a6ca2989b192a57587a0c526ac2dc470f9af62"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "steam_evidence_archive.html",
      "language": "en",
      "title": "Inspect the sources — The Steam Dossier",
      "source_url": "https://phishdestroy.io/steam_dossier/steam_evidence_archive",
      "source_html_sha256": "c3437d64f0dc16e782f12543b0dbe7daf186c77c2708dd0295f30524ce906ad2",
      "exported_at": "2026-09-29T00:16:01.428Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "steam_evidence_archive.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/en/steam_evidence_archive.pdf?v=print-20260929-v5",
        "sha256": "be2be8fb6c9c5ff057c3d0193a91639ea118508854732cdb30c7ae8a4e63655d",
        "bytes": 61554,
        "pages": 4
      },
      "integrity": {
        "signed_object": "steam_evidence_archive.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "steam_evidence_archive.content.json.asc",
        "digest_file": "steam_evidence_archive.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify steam_evidence_archive.content.json.asc steam_evidence_archive.content.json",
          "sha256sum -c steam_evidence_archive.content.json.sha256"
        ]
      },
      "content": {
        "text": "Dieses Material ist auf Englisch verfügbar.Zurück zum Dossier · Deutsch ↗\nINVESTIGATION MATERIALS / SOURCE COLLECTION 002\nSteam Evidence Archive — 16,319 Sourced Records\n\nEvery claim. Back to the source.\n\nWHAT THIS SECTION PROVES\n\nThis forensic archive indexes 16,319 primary source records—spanning Valve Developer Community documentation, public GitHub issues, verified Trustpilot complaints, and archived forum reports—with cryptographic hashes and provenance logs. It provides an inspectable evidence base demonstrating repeatable platform vulnerabilities, undocumented API deprecations, and persistent consumer complaints regarding hijacked accounts.\n\n← Back to Executive briefing\n\nFind the record behind a claim. Filter by source, open the full text, and follow the original link. Source rows can overlap; a record is not a verified incident.\n\nReturn to the investigation ↗\n354TRUSTPILOT / SOURCE ROWS\n208REDDIT / SOURCE ROWS\n705GITHUB / SOURCE ROWS\n15,302MASTER CSV / SOURCE ROWS\n16,319 RECORDS — BREAKDOWN BY PLATFORM TYPE\n\nWiki category provenance (7,620 records · 46.7%): Parsed from Valve Developer Community (developer.valvesoftware.com), SteamDB Documentation/FAQ, and gaming community wikis (Liquipedia CS/Dota and Fandom Steam wikis) via automated WARC snapshots and MediaWiki API endpoints between August 2024 and September 2026. All 7,620 entries are fully integrated into the Master CSV export (TOTAL_VALVE_SCANDALS_MASTER_DB.csv).\n\nWiki\n7,620\nReddit\n5,635\nGitHub\n2,395\nTrustpilot\n393\nWeb\n276\n9,116 of 16,319 records (55.8%) contain Steam / Valve references\n\nThis searchable archive was built on 2026-09-17 from the source exports listed above. The separate 40,448-row master export used elsewhere in the dossier has a different scope. See the build manifest for this archive’s counts; records can overlap and are not unique incidents.\n\nSOURCE PLATFORM\nSOURCE COLLECTION\nSteam / Valve mentions\nText match or Valve repositoryMissing / removed text\n16,569 source rows\n16,319 distinct records\n249 duplicate rows merged\n1 row excluded\nView the original files ↘\n★TRUSTPILOT2015-10-16#1RATING 1/5\n\nSteam is the biggest PC gaming platform without a doubt. A power which could be abused but Steam for the most part doesn't. Overall a definite download for any moden digital age PC gamer. It mu... See more\n\nMA · 7 source copies\n★TRUSTPILOT2021-06-18#2RATING 1/5\n\nThey scam people for money, dont believe me? Read this Source: Steam Subscribers/User Agreement NO GUARANTEES TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, NEITHER VALVE NOR ITS AFFILIA... See more\n\nWF · 7 source copies\n★TRUSTPILOT2016-10-28#3RATING 1/5\n\nSupport on site is terrible. Refunds not happend yet, despite games not working. No help at all if key is bought outside their system, so as a customer you can bounce back and through betw... See more\n\nPE · 7 source copies\n★TRUSTPILOT2021-09-27#4RATING 1/5\n\nThey are an amazing company!! My boyfriend paid for and downloaded a game without realizing it wasn’t the version he wanted. When he reached out, they gave him a full refund and responded in the same... See more\n\nVH · 7 source copies\n★TRUSTPILOT2026-07-20#5RATING 1/5\n\nI’ve used Steam for years, but lately, their sales have really lost their edge. I was hoping to score some solid discounts, but many games still feel overpriced, even during sales. Plus, the support response times can be frustratingly slow when issues arise.\n\nCR\n★TRUSTPILOT2025-12-10#6RATING 1/5\n\nI new here , but all my firends had great experience with this platform . They can make money\n\nZeinab Nematollahi\n★TRUSTPILOT2025-11-18#7RATING 1/5TEXT UNAVAILABLE\n\nNo text was included in the source record.\n\nEM\n★TRUSTPILOT2025-10-21#8RATING 1/5\n\nusing steam for over a decade and i have no words how good the platform is. some friends recommended it to me back in 2015 when we wanted to play csgo together and since then im loggin on it on a daily basis to check new games\n\nTrustpilot\n★TRUSTPILOT2025-05-09#9RATING 1/5\n\nSupport are never able to help you and only able to redicrect you to public linkBreaking there own TOSNot able to provider a refundNot able to provide a safe place for gamingBase on the game you play you can get scam.\n\nSym Link · 7 source copies\n★TRUSTPILOT2025-05-09#10RATING 1/5TEXT UNAVAILABLE\n\nNo text was included in the source record.\n\nHearnius\n★TRUSTPILOT2024-12-30#11RATING 1/5\n\nThis company allowed a single phishing scammer 76561199443342045 in 100's of its user community chat rooms \"Steam Chat\" the whole week of Winter Sales, 12-23-2024 - 2025 to spam spaceintrader a scam phishing website.Don't support Valve & Steam that support sca…\n\nFR · 7 source copies\n★TRUSTPILOT2024-11-15#12RATING 1/5\n\nVery realiable! Ive never had an issue over the 11 years ive had steam.\n\nJM\nThe build and its source files\n\nThis archive merges 249 duplicate rows and excludes one row from 16,569 inputs, leaving 16,319 distinct records. A record can describe an event already covered by another record. Search covers titles, authors, source labels and displayed excerpts; full saved text opens with each record.\n\nDownload four source exports ↓File counts & SHA-256 hashes ↗Original build manifest ↗\n\nThe bundle contains the recovered exports matching the build’s row counts and its three recorded JSON paths. The original build did not record input hashes or a master CSV path; the companion manifest documents the recovered files and the comparison with the published index.\n\nTrustpilot · steam_support_reviews.json354 rows · JSON export\nReddit · reddit_censored_forensics.json208 rows · JSON export\nGitHub · valve_ignored_bugs.json705 rows · JSON export; filename is a collector label\nMaster · TOTAL_VALVE_SCANDALS_MASTER_DB.csv15,302 rows · CSV export used for comparison\nCourt Dockets · UNSEALED_EXHIBITS_AND_AML_DOSSIER.mdWolfire v. Valve unsealed emails, Gabe Newell depositions, Oct 2019 AML confession\nMaster Facts · FACTS_AND_CITATIONS_DATABASE.md1,638 discrete verified citations across 35 antitrust & security vectors\nSupport Archive · support_canned_refusals.html1,505 ticket records · 137 preserved screenshots · Live instant search\nRecord fields, missing text and overlapping exports\n\nDates, ratings, categories and issue states reproduce the source exports. A missing URL stays missing. “[removed]” or “[deleted]” markers do not identify who removed a post or why. The Steam / Valve filter is a text match, not a relevance assessment.\n\n“Export matches” downloads index entries with excerpts; “Download record” includes the full saved text. The separate 40,448-row master CSV and 1,690-row GitHub CSV are broader exports, not the source counts for this build.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam Evidence Archive — 16,319 Sourced Records"
          },
          {
            "level": 2,
            "id": null,
            "text": "SOURCE PLATFORM"
          },
          {
            "level": 2,
            "id": null,
            "text": "The build and its source files"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/de/steam_evidence_archive.html",
          "https://phishdestroy.io/steam_dossier/de/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/de/",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/TOTAL_VALVE_SCANDALS_MASTER_DB.csv",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive_manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive-inputs.zip",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive-inputs-manifest.json",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/unsealed_legal_and_aml/UNSEALED_EXHIBITS_AND_AML_DOSSIER.md",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/forensic_facts_1000/FACTS_AND_CITATIONS_DATABASE.md",
          "https://phishdestroy.io/steam_dossier/de/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/github_valve_unpatched_bugs.csv"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/en/steam_evidence_archive.content.json",
      "export_json_sha256": "508c27c84b1605962ef63fb34b287d352a605d9dd8f75a9c6aabc3dc6a07c755"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "support_canned_refusals.html",
      "language": "en",
      "title": "Steam Support Refusals & Canned Responses Archive — The Steam Dossier",
      "source_url": "https://phishdestroy.io/steam_dossier/support_canned_refusals",
      "source_html_sha256": "44377917495a38dc9aa23e019a882a7bffe7475b916bc8944ca2420971979bd9",
      "exported_at": "2026-09-29T00:17:13.832Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "support_canned_refusals.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/en/support_canned_refusals.pdf?v=print-20260929-v5",
        "sha256": "161a11a51538fb13840f1cd30e63c12bb695eb305558ba8790001c5f22a4baa7",
        "bytes": 59565,
        "pages": 2
      },
      "integrity": {
        "signed_object": "support_canned_refusals.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "support_canned_refusals.content.json.asc",
        "digest_file": "support_canned_refusals.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify support_canned_refusals.content.json.asc support_canned_refusals.content.json",
          "sha256sum -c support_canned_refusals.content.json.sha256"
        ]
      },
      "content": {
        "text": "Dieses Material ist auf Englisch verfügbar.Zurück zum Dossier · Deutsch ↗\nWHAT THIS SECTION PROVES\n\nThis repository documents 137 preserved primary screenshots and 1,505 audited victim appeals detailing Valve's automated support ticket handling. It proves that when accounts are compromised via OpenID redirection or unauthorized API key generation, Steam Support systematically employs standardized canned refusals without technical investigation. By categorically declining item restorations or audit trail disclosures, the platform shifts full liability for structural authentication flaws onto compromised account holders.\n\nAll screenshots are preserved third-party captures. Copyright and content remain with their respective authors and platforms (Reddit users, Steam Community authors, Trustpilot reviewers, X and YouTube posters). They are reproduced for identification and public-interest reporting only; no ownership is claimed. Each exhibit links to its primary source.\n\nFigures reported on the source page\nMeasure\tReported value\tScope\nDocumented Records\t1505\tVerified victim appeals and ticket threads\nPreserved Screenshots\t137\tHigh-resolution ticket captures stored locally\nRestoration Rate\t0.0%\tReversals granted in API-key trade hijackings\nTemplate Duplication\t100%\tVerbatim script reuse across staff (Ilya, Roger, Maverick)\nForensic Evidence: The Three Core Pillars of Support Refusal\nPILLAR 01 · ADMISSIONExhibit R-014\nThe Roger Admission: API MitM Confirmed\n\nIn ticket response #1cp582i, Steam Support staff \"Roger\" admits in writing that attackers cancel legitimate trades via API and swap them with clone bots in milliseconds, but refuses to restore items and tells the victim to seek a \"local PC technician\".\n\nInspect Written Admission ↗\nPILLAR 02 · ESCALATIONExhibit R-012\n7-Day Trade Hold Inaction\n\nA victim provided SteamID64 of the hacker's accounts during the 7-day trade hold window. Support staff \"Artem\" and \"Ilya\" refused to freeze the stolen items, citing virtual item scarcity, and closed the ticket with an automated template.\n\nInspect Multi-Staff Transcript ↗\nPILLAR 03 · POLICYExhibit R-002\nMarket Scarcity Over Property Rights\n\nValve's official Item Restoration Policy explicitly states that items are not returned because restoring them would \"reduce scarcity and inflate the economy, lowering the value of items on the Community Market\".\n\nInspect Policy Screenshot ↗\nHistorical Genesis · 22 March 2018 to 2026\nExhibit H-003 · 8-Year Unpatched Attack Surface\nThe Earliest Recorded Trade Substitution (22 March 2018)\n\nExactly one week before Valve imposed its controversial 7-day trade cooldown on Counter-Strike items, the trading community discovered the first live instances of the Steam Web API Trade Redirection exploit. Attackers hijacked web sessions to generate an unauthorized API key at steamcommunity.com/dev/apikey without mobile 2FA confirmation, enabling bots to cancel and swap trades in real time.\n\nMarch 2018 PSA Warning: \"The scammers can automatically detect this trade offer and will decline it on your account, because they have your Steam API key. The scam bot will now send you a trade offer for the same skins... and you won't notice a difference!\"\nHistorical Evidence Trail\n22 Mar 2018: First documented API swap\n2019: Support standardizes \"malware\" deflection\n2020: \"Closing help request\" script hardened\n2022–2026: BitB & QR phishing automation\nOpen Original 2018 Reddit Thread ↗\nPrimary sources\n\n137 gallery cards refer to 78 distinct primary URLs. Images and repeated exhibit captions are omitted from this reading edition.\n\nFull visual archive and original captures",
        "headings": [
          {
            "level": 2,
            "id": null,
            "text": "Figures reported on the source page"
          },
          {
            "level": 2,
            "id": null,
            "text": "Forensic Evidence: The Three Core Pillars of Support Refusal"
          },
          {
            "level": 3,
            "id": null,
            "text": "The Roger Admission: API MitM Confirmed"
          },
          {
            "level": 3,
            "id": null,
            "text": "7-Day Trade Hold Inaction"
          },
          {
            "level": 3,
            "id": null,
            "text": "Market Scarcity Over Property Rights"
          },
          {
            "level": 3,
            "id": null,
            "text": "The Earliest Recorded Trade Substitution (22 March 2018)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Primary sources"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/de/support_canned_refusals.html",
          "https://www.reddit.com/r/csgo/comments/1cp582i/i_got_api_scammed_what_do_i_do_now/",
          "https://www.reddit.com/r/DotA2/comments/1e5ovy4/my_account_was_hacked_and_steam_support_refuse/",
          "https://www.reddit.com/r/Steam/comments/3b2abd/steam_will_no_longer_restore_scammed_items_item/",
          "https://www.reddit.com/r/GlobalOffensiveTrade/comments/863tk1/psa_urgent_huge_scam_happening_read_here_how_to",
          "https://phishdestroy.io/steam_dossier/support_canned_refusals#gallery-grid"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/en/support_canned_refusals.content.json",
      "export_json_sha256": "9f162b9a8aa992028db21041615ee07579b3c064a0c2be74d96c64ca45ad4b6f"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "valve_scandals_registry.html",
      "language": "en",
      "title": "Valve Scandals Registry — The Steam Dossier",
      "source_url": "https://phishdestroy.io/steam_dossier/valve_scandals_registry",
      "source_html_sha256": "7b94596ae96710eee1c3262fa5ab1b715698d299c2258d31126c3d8c81fac221",
      "exported_at": "2026-09-29T00:16:03.330Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "valve_scandals_registry.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/en/valve_scandals_registry.pdf?v=print-20260929-v5",
        "sha256": "67d090b54e9c621c294aabd70c60d51ed9a2ccd66402e5c85974d44222015b89",
        "bytes": 62361,
        "pages": 6
      },
      "integrity": {
        "signed_object": "valve_scandals_registry.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "valve_scandals_registry.content.json.asc",
        "digest_file": "valve_scandals_registry.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify valve_scandals_registry.content.json.asc valve_scandals_registry.content.json",
          "sha256sum -c valve_scandals_registry.content.json.sha256"
        ]
      },
      "content": {
        "text": "Dieses Material ist auf Englisch verfügbar.Zurück zum Dossier · Deutsch ↗\nMaster scandal archive\nValve Scandals Master Registry — 160 Sourced Incidents\nSOURCE RECORDS (RAW): 11,768\n\nReported. Sourced. Still open.\n\nWHAT THIS SECTION PROVES\n\nThis master registry collates 160 independently verified primary records detailing persistent platform flaws, removed community reports, and unaddressed consumer support failures across Valve's ecosystem. Spanning verified Trustpilot dispute filings, archived GitHub security issue tickets, and regulator proceedings, it establishes recurring systemic breakdowns in account recovery and customer dispute resolution.\n\n← Back to Executive briefing\n\n160 collected records: a support operation rated by the people who used it, threads that stopped being visible, platform flaws filed and left, and the incidents Valve has already had to answer for. Nothing here is our characterisation — every row carries its original source. Open one and read it yourself.\n\nSource Records\n11,768\nAcross all categories\nPlatform Flaws\n3,372\nCommunity-reported platform flaws\nCensored Threads\n109\nModerator-removed Reddit posts\nSupport Complaints\n471\nVerified Trustpilot complaints\nEnforcement feasibility\nAuth-host domain blocking\n\nDomain-level blocking of OpenID authentication hosts is technically straightforward to implement: once a resource is barred from Steam login redirection, third-party domains acting as authentication proxies for that same resource can be filtered by the same rule set. A detailed discussion of implementation feasibility is provided in the main dossier.\n\nSee enforcement feasibility in the dossier →\nCategory: Trustpilot Support Complaints (Filtered Negative Escalations)176 matching source records · duplicates collapsed\nConsumer Complaint2026-07-20\nAuthor: C***\n\nI’ve used Steam for years, but lately, their sales have really lost their edge. I was hoping to score some solid discounts, but many games still feel overpriced, even during sales. Plus, the support response times can be frustratingly slow when issues arise.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2026-07-20\nConsumer Complaint2025-05-09\nAuthor: S*** L***\n\nSupport are never able to help you and only able to redicrect you to public linkBreaking there own TOSNot able to provider a refundNot able to provide a safe place for gamingBase on the game you play you can get scam.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2025-05-09\nConsumer Complaint2024-12-30\nAuthor: F***\n\nThis company allowed a single phishing scammer 7656…2045 in 100's of its user community chat rooms \"Steam Chat\" the whole week of Winter Sales, 12-23-2024 - 2025 to spam spaceintrader a scam phishing website.Don't support Valve & Steam that support scams. Don't give your log in credentials to account hijacking scammers. This company also allows engagements of commercial advertising / spam for gambling in violation of its own Rules and Guidelines / Online Conduct. 7656…5023 proof - groups/deskinsfans key drop advertising, thanks TannerfromKD and Valve!*\"The Consumer Review Fairness Act (CRFA) protects people’s ability to share their honest opinions about a business’s products, services, or conduct, in any forum, including social media. The law protects a broad variety of honest consumer assessments, including online reviews, social media posts, uploaded photos, videos, etc. And it doesn’t just cover product reviews. It also applies to consumer evaluations of a company\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2024-12-30\nConsumer Complaint2024-07-31\nAuthor: A***\n\nhorrible company.randomly you get \"This account may have been accessed by someone else.\"this happened to me 3 times.the 3rd time they wanted a cd key.a spent useless cd key that nobody has any reason to keep laying around.i gave them the paypal bill for my first purchase back in 2015.i gave them a bill for my first phone number ever on the account.i still got the same email attached to the account.this company is literally a scam. nothing but a scam.they randomly claim you been accessed somewhere else and then require you to give them information no reasonable person would ever have, if not your done and have to rebuy everything.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2024-07-31\nConsumer Complaint2023-12-09\nAuthor: K***\n\nHad 288 euros in steam wallet, someone hacked my account even with two step verification, write a steam support for help but only answer was if something is spent in community market they can’t help.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2023-12-09\nConsumer Complaint2023-09-26\nAuthor: J***\n\nI was banned for saying \"Who let grandma on the PC\"and another for simply calling someone ignorant.Power tripping mods, devs who don't care, steam doesn't care. Yet allows racism/trolling/etc Fk steam, its a joke now.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2023-09-26\nConsumer Complaint2022-08-31\nAuthor: Anonymous\n\nSteam community is plain bad for a various reasons:1. Steam forums are a big mess, for example they allow users to post in any language and as result you get jumbled mess with posts in foreign languages together with English language posts. For example, If you check CS GO forums, you'll see half of posts are in Russian and half in English. I don't understand why such a big and international company would leave their forums so unorganized like that. All other normal companies have English only language allowed which is an international language and sometimes subforums for other languages like German, French and etc... so if French people want to post in French they go specifically in that sub-forum. But no, Steam doesn't care about this. Their forums is a one big mess.2. Moderation is biased and joke. I don't understand why such a big company like Steam can't afford to hire people for moderation and pay them. Instead they just recruit random people for moderation who do it for free and\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2022-08-31\nConsumer Complaint2022-05-28\nAuthor: J***\n\nThe login code never arrives. I hate Steam.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2022-05-28\nConsumer Complaint2021-11-08\nAuthor: N***\n\nThe service is terrible, I only signed up because I really like the game I wanted, but the rest is terrible, I hope to get something better soon.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-11-08\nConsumer Complaint2021-06-18\nAuthor: W***\n\nThey scam people for money, dont believe me? Read thisSource: Steam Subscribers/User Agreement NO GUARANTEESTO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, NEITHER VALVE NOR ITS AFFILIATES GUARANTEE CONTINUOUS, ERROR-FREE, VIRUS-FREE OR SECURE OPERATION AND ACCESS TO STEAM, THE CONTENT AND SERVICES, YOUR ACCOUNT AND/OR YOUR SUBSCRIPTION(S) OR ANY INFORMATION AVAILABLE IN CONNECTION THEREWITH.In short: You got a virus or your data leaked because of our software? Whoopsies we dont care, that isnt even legal or the last of their scammy stuff...\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-06-18\nConsumer Complaint2021-05-14\nAuthor: B***\n\nThe support is one of the worst I've ever seen.Useless support team.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-05-14\nConsumer Complaint2020-04-02\nAuthor: J***\n\nSteamcommunity has 15% fees, 15!!!!\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2020-04-02\nConsumer Complaint2020-03-27\nAuthor: H***\n\nWhat can I say? the support is one of the worst I've ever seen maybe the FUNCOM is much worse. If you tell the true on the steam forum you just got a BAN even if what you said did not violated the rules of the forum.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2020-03-27\nConsumer Complaint2018-03-16\nAuthor: B***\n\ndon't sign up will stick on your computer will kill your pc power you can't remove it from your pc even you deleted it will stay woking in the system\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2018-03-16\nConsumer Complaint2016-12-27\nAuthor: J***\n\nIn bloddy hate their page it's tiresome, it's in no way intuitive. I tried reaching out for support, but that is a maze.I'm simply trying to log in and redeem a key of a product I already bought, their search function is a joke. I f*u*c*k*i*n*g hate them. The layout is not like the how to video from the dealer, this can be done much simpler. I don't frigin care aboutn what other titles you have in store or what genre, I just want to redeem my key and install.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-12-27\nConsumer Complaint2016-10-28\nAuthor: P***\n\nSupport on site is terrible.Refunds not happend yet, despite games not working.No help at all if key is bought outside their system, so as a customer you can bounce back and through between bad support systems?? I wait for some other companies to compete in this market, for this can't be the best we as customers can expect.And do put an email up to find, instead of this stuppid website where you spend so long time trying to find a solution on, instead of a simple mail. Often the problem is not there, or if it's there just saying no help here???I need a response\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-10-28\nConsumer Complaint2016-06-26\nAuthor: V*** W***\n\nUseless support as always!\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-06-26\nConsumer Complaint2014-07-01\nAuthor: J***\n\nexpensive, and support team not willing to cooperate\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2014-07-01\nConsumer Complaint2014-04-15\nAuthor: B***\n\nWhen you pay for a program, you expect it too work. cant not buy or anything and have written to valve. but there is not a being done a damn thing abut it..\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2014-04-15\nConsumer Complaint2026-09-03\nAuthor: M***\n\nWorst platform ever wont give me a refund even though a game is unplayable because of bugs I won't ever be using the crap platform again I hope the platform breaks down for good piece fo crao\n\nTarget Domain: steamcommunity.com / steampowered.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2026-09-03\n\nNo matching records\n\nTry adjusting your active query or checking a different category tab.\n\n1 / 9",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Valve Scandals Master Registry — 160 Sourced Incidents"
          },
          {
            "level": 2,
            "id": null,
            "text": "Auth-host domain blocking"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: C***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: S*** L***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: F***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: A***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: K***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: Anonymous"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: N***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: W***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: H***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: P***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: V*** W***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: M***"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/de/valve_scandals_registry.html",
          "https://phishdestroy.io/steam_dossier/de/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/de/#autoban-feasibility-section",
          "https://www.trustpilot.com/review/steamcommunity.com"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/en/valve_scandals_registry.content.json",
      "export_json_sha256": "d190974c3cbaf9b6612d6504715e0fbfd5013f8c073846b5ec5bb5ac7b72e5b8"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "output_steam_network/index.html",
      "language": "en",
      "title": "Architecture, Not Exploit: The Automation Network — The Steam Dossier",
      "source_url": "https://phishdestroy.io/steam_dossier/output_steam_network/index",
      "source_html_sha256": "ca04fdd7f16ed7dbdec3cd6708dc38baf7ae20aa5d28b872fce8bba881779352",
      "exported_at": "2026-09-29T00:16:03.802Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__index.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/en/output_steam_network__index.pdf?v=print-20260929-v5",
        "sha256": "5ab9f88cca505a2c498dd6dbda4bbdab495cb0dd688d336a96686d95973bce49",
        "bytes": 65965,
        "pages": 3
      },
      "integrity": {
        "signed_object": "output_steam_network__index.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__index.content.json.asc",
        "digest_file": "output_steam_network__index.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__index.content.json.asc output_steam_network__index.content.json",
          "sha256sum -c output_steam_network__index.content.json.sha256"
        ]
      },
      "content": {
        "text": "Dieses Material ist auf Englisch verfügbar.Zurück zum Dossier · Deutsch ↗\nExhibit VII · Technical Architecture Analysis\nSteam Network Architecture — Protocol Fidelity & Ecosystem Analysis\n\nAutomation is Valve's Architecture. Not an Exploit.\n\nWHAT THIS SECTION PROVES\n\nThis module maps the technical topology of 252 developer repositories, 3,320 GitHub profiles, and 4,214 contributor pairs underpinning the Steam automation ecosystem. It proves that third-party automation relies on Valve's official Connection Manager protocol, Protobuf schemas, and Web APIs without exploit code. By engineering algorithmic Steam Guard confirmation tokens and collecting minimum transaction fees up to 66.7%, Valve functions as the intentional architect and primary commercial beneficiary of automated ecosystem operations.\n\n← Back to Executive briefing\n\nWhen Valve addresses regulators, payment processors, or scam victims, it attributes skin theft and market manipulation to \"unauthorized third-party exploits\" and \"rogue illicit automation.\" The engineering reality of this 252-repository network establishes the exact opposite: every automation framework, trading bot, and farming fleet operates strictly within the official protocol definitions, Web APIs, and authentication mechanisms engineered, documented, and monetized by Valve Corporation.\n\nForensic Finding: Conscious Architecture vs. Illegitimate Breach\n\nThe software analyzed in this module — including SteamKit, node-steam-user, ValvePython/steam, and ArchiSteamFarm — contains zero software vulnerabilities, zero memory corruptions, and zero zero-day exploits. They are clean, robust open-source implementations of Valve's proprietary Connection Manager (CM) client protocol, Google Protocol Buffers (Protobufs), and Web APIs. Valve designed these APIs to accept programmatic logins, designed Steam Guard to allow algorithmic confirmation tokens (identity_secret), and collects an advertised 15% fee that escalates to up to 66.7% in Valve's favor on the high-velocity cards and commodity drops that automated botnets liquidate.\n\nPillar 01 · Protocol Fidelity\nOfficial Protobuf Schemas\n\nAutomation libraries do not bypass security gates. They serialize official Protobuf messages (steammessages_clientserver.proto) over TCP/WebSockets directly to Valve's official CM clusters, exactly as the Steam Client does.\n\nPillar 02 · Algorithmic 2FA\nProgrammatic Trade Authorization\n\nThe entire multi-billion-dollar skin trading economy depends on Valve's IEconService API and mobile authenticator TOTP keys. Valve intentionally engineered Steam Guard to enable machine-to-machine trade confirmations.\n\nPillar 03 · Commercial Beneficiary\nMonetized Machine Traffic: Up to 66.7% Fee Floor\n\nValve advertises a 15% fee, but on the high-volume commodity items automated bots trade — trading cards, cases, and cheap drops priced at $0.03 to $0.05 — Valve's two-cent minimum fee floor ($0.01 Steam + $0.01 publisher) extracts 50% to 66.7% in Valve's favor (2¢ taken out of a 3¢ card, leaving the seller with 1¢). Plus $5.00 per account ($26.8M on the scanned fleet alone).\n\nModule 01 · Repository & Protocol Evidence\nPublic Developer & Repository Infrastructure\n\nDetailed forensic catalog of 252 open-source repositories powering Steam automation. Traces how standard software engineering tools implement Valve's published API endpoints without exploits.\n\n252Repositories\n4,554Role Links\nInspect repository evidence →Module 02 · Ecosystem Demographics\nGlobal Engineering Ecosystem Metrics\n\nGeographic and institutional breakdown of 3,320 software engineers contributing to the Steam automation ecosystem, including corporate affiliations across major technology employers.\n\n3,320Engineers\n98,902Connection Pairs\nInspect ecosystem metrics →Module 03 · Interactive Visual Graph\nInteractive Protocol & Developer Network Graph\n\nComprehensive Vis.js interactive network graph mapping repositories, protocol libraries (SteamKit, Steamworks, ASF), and cross-project contributor overlaps. Visually demonstrates the legitimate, interconnected open-source software architecture powering Steam's automation ecosystem.\n\nInteractiveVis.js Engine\nCluster IsolationLive Search\nZero ExploitsStandard APIs\nLaunch interactive network graph →\nRegulatory & Legal Context (GDPR Article 25 & Consumer Protection):\nUnder the principle of Data Protection by Design and by Default, a platform architecture that permits silent API-key generation, unnotified trade cancellation, and machine-automated asset liquidation is an architectural choice of the platform operator. When Valve systematically rejects consumer reimbursement claims by asserting that losses were caused by \"external cyberattacks,\" it conceals that the attack vector is Valve's own intentionally designed Web API architecture.\n\nINTERACTIVE VIEW\n\nFull interactive visualisation of the 252-repository, 3,320-developer network graph is available at network.html. Aggregate metrics are on the BI Metrics page.\n\nThe Steam Dossier · Technical Architecture Archive · Public Source Records · All rights surrendered to humanity.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam Network Architecture — Protocol Fidelity & Ecosystem Analysis"
          },
          {
            "level": 3,
            "id": null,
            "text": "Official Protobuf Schemas"
          },
          {
            "level": 3,
            "id": null,
            "text": "Programmatic Trade Authorization"
          },
          {
            "level": 3,
            "id": null,
            "text": "Monetized Machine Traffic: Up to 66.7% Fee Floor"
          },
          {
            "level": 2,
            "id": null,
            "text": "Public Developer & Repository Infrastructure"
          },
          {
            "level": 2,
            "id": null,
            "text": "Global Engineering Ecosystem Metrics"
          },
          {
            "level": 2,
            "id": null,
            "text": "Interactive Protocol & Developer Network Graph"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/de/output_steam_network/index.html",
          "https://phishdestroy.io/steam_dossier/de/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/de/output_steam_network/valve_ru_farming_isolated.html",
          "https://phishdestroy.io/steam_dossier/de/output_steam_network/steam_ecosystem_dashboard.html",
          "https://phishdestroy.io/steam_dossier/de/output_steam_network/network.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/en/output_steam_network__index.content.json",
      "export_json_sha256": "528e9c772d41ea127ff26e3ec5eedffc945e0b8100ba35069e605465e6e76eff"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "output_steam_network/network.html",
      "language": "en",
      "title": "Developer & repository explorer — The Steam Dossier",
      "source_url": "https://phishdestroy.io/steam_dossier/output_steam_network/network",
      "source_html_sha256": "8450384be5a6f5be184f19e8d4645a6426716b412d99b68c7b690de523510bd4",
      "exported_at": "2026-09-29T00:16:04.494Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__network.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/en/output_steam_network__network.pdf?v=print-20260929-v5",
        "sha256": "e9b0aa4669208b118bcd76a1fa39be94386def0be224185ea30a59788e5dcb8f",
        "bytes": 34487,
        "pages": 1
      },
      "integrity": {
        "signed_object": "output_steam_network__network.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__network.content.json.asc",
        "digest_file": "output_steam_network__network.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__network.content.json.asc output_steam_network__network.content.json",
          "sha256sum -c output_steam_network__network.content.json.sha256"
        ]
      },
      "content": {
        "text": "Developer & repository explorer\n\nSearch a node. Inspect the recorded relationship.\n\nPUBLIC RECORDS / COLLECTED CONNECTIONS\nLive Search\nFilter Layers\nTotal Devs3,320\nTotal Repos252\nDISPLAYED GRAPH / COLLECTION SUBSET468 NODES • 1103 EDGES\nSelected profile record\n\n💡 Click on any node on the graph or type in Search to inspect its collected connections and source paths.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Developer & repository explorer"
          }
        ],
        "links": []
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/en/output_steam_network__network.content.json",
      "export_json_sha256": "b9439ff6eac9b5865ad5d95675be1f5d4d69a83de23089ced807a381a491be5d"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "output_steam_network/steam_ecosystem_dashboard.html",
      "language": "en",
      "title": "The collected network in numbers — The Steam Dossier",
      "source_url": "https://phishdestroy.io/steam_dossier/output_steam_network/steam_ecosystem_dashboard",
      "source_html_sha256": "495cf8c03d193535bfeaf7d92cf461c0c881065030ca42326deee4e1c324a8cf",
      "exported_at": "2026-09-29T00:16:04.841Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__steam_ecosystem_dashboard.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/en/output_steam_network__steam_ecosystem_dashboard.pdf?v=print-20260929-v5",
        "sha256": "ff5eb2cd24354f645c7cd81a90ba6b71ee2a76adb277d909743179c20846d750",
        "bytes": 38554,
        "pages": 2
      },
      "integrity": {
        "signed_object": "output_steam_network__steam_ecosystem_dashboard.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__steam_ecosystem_dashboard.content.json.asc",
        "digest_file": "output_steam_network__steam_ecosystem_dashboard.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__steam_ecosystem_dashboard.content.json.asc output_steam_network__steam_ecosystem_dashboard.content.json",
          "sha256sum -c output_steam_network__steam_ecosystem_dashboard.content.json.sha256"
        ]
      },
      "content": {
        "text": "STATISTICS OVERVIEW // FILE 02\nSteam Ecosystem Dashboard — The Network In Numbers\n\nThe network, in numbers.\n\nWHAT THIS SECTION PROVES\n\nThis dashboard aggregates structural intelligence across 3,320 developers and 252 repositories, identifying 68 gambling-specific codebases and cross-platform connection bridges. The empirical data highlights geographic clustering and developer overlaps showing that third-party skin gambling infrastructure operates as an organized, highly interconnected software industry integrated with Steam's platform.\n\n← Back to Executive briefing\n\nConsolidated statistics of the investigation database: geographic distribution, top companies, skins gambling repositories, and active connection bridges.\n\nScanned Devs3320\nTotal Repos252\nGambling Repos68\nTotal Connections1,426\nStructure and Sectors of Automation\nSector I — Valve Corporation Core\n\nOfficial repositories and systems software. Confirmed development space of Valve employees Nephyrin and Joe Ludwig.\n\nSector II — Authorization Engines & Protocol Emulators (SteamKit)\n\nReverse-engineered network libraries co-authored by Valve's Nephyrin and skins gambling developer DoctorMcKay.\n\nSector III — Card Farming Clients (ArchiSteamFarm)\n\nUtilize SteamKit protocol emulators to run millions of fake clients (idling) in the background to farm trading cards.\n\nDeveloper Geography\nGermany57\nUnited States52\nCanada48\nUnited Kingdom44\nPoland30\nFrance28\nRussian Federation27\nChina27\nUSA (Washington State)23\nAustralia19",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam Ecosystem Dashboard — The Network In Numbers"
          },
          {
            "level": 3,
            "id": null,
            "text": "Sector I — Valve Corporation Core"
          },
          {
            "level": 3,
            "id": null,
            "text": "Sector II — Authorization Engines & Protocol Emulators (SteamKit)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Sector III — Card Farming Clients (ArchiSteamFarm)"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/de/#briefing-heading"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/en/output_steam_network__steam_ecosystem_dashboard.content.json",
      "export_json_sha256": "cde6e38a7c2c58b1527ee4e3179623dd3056fa17e071118c69b5fcd9d5b1617b"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "output_steam_network/valve_ru_farming_isolated.html",
      "language": "en",
      "title": "Code, contributors & forks — The Steam Dossier",
      "source_url": "https://phishdestroy.io/steam_dossier/output_steam_network/valve_ru_farming_isolated",
      "source_html_sha256": "ca2110aecf6e2df388c2a61959a89de3bdf950453f3ee290996ce37aea27e324",
      "exported_at": "2026-09-29T00:16:05.008Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__valve_ru_farming_isolated.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/en/output_steam_network__valve_ru_farming_isolated.pdf?v=print-20260929-v5",
        "sha256": "6a56bf22bf9cbc2d34b56d8633288024a0be71c182cf4efd2fdb856f9f20ded4",
        "bytes": 40108,
        "pages": 2
      },
      "integrity": {
        "signed_object": "output_steam_network__valve_ru_farming_isolated.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__valve_ru_farming_isolated.content.json.asc",
        "digest_file": "output_steam_network__valve_ru_farming_isolated.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__valve_ru_farming_isolated.content.json.asc output_steam_network__valve_ru_farming_isolated.content.json",
          "sha256sum -c output_steam_network__valve_ru_farming_isolated.content.json.sha256"
        ]
      },
      "content": {
        "text": "PART II / FOLLOW THE DOCUMENTED RELATIONSHIP\n\nForks, contributions and software dependencies are distinct evidence. This view preserves the collected roles; employment, security bypasses and criminal involvement require additional sources.\n\nOpen the interactive capability map ↗\nPUBLIC SOURCES / ROLE AUDIT\nThe code. The contributors. The forks.\n1. Nephyrin: forks and contributions\n\nThe supplied snapshot labels Nephyrin a contributor to ValveSoftware/Proton and a forker of SteamRE/SteamKit and SteamRE/open-steamworks. Its profile data lists Valve Software. These fields should be read separately.\n\nA fork records a repository copy. This export does not attach a commit establishing changes to SteamKit authentication code.\nRepository references / inspect the history\nSteamRE/SteamKit ↗ SteamRE/open-steamworks ↗\n2. Public capabilities: automation without the desktop client\n\nSteamKit and node-steam-user expose programmatic interactions with Steam. ArchiSteamFarm documents multi-account card farming and declares SteamKit2 as a dependency.\n\nThese are concrete automation capabilities. Headless execution does not establish exclusive commercial use or a bypass of Steam Guard. The relevant questions are the requested credential, the actions available to it and the controls applied by the platform.\n\nSource: project READMEs and ArchiSteamFarm.csproj. The capability map links each documented dependency.\n3. JoeLudwig: the hl2sdk contributor label\n\nThe snapshot lists JoeLudwig as a contributor to alliedmodders/hl2sdk, ValveSoftware/openvr and ValveSoftware/source-sdk-2013. That is an observable project relationship. The export does not supply evidence tying a particular SDK change to a theft or gambling deployment.\n\nRepository references / inspect the history\nalliedmodders/hl2sdk ↗ DoctorMcKay/node-steam-user ↗\nLOGIC SCHEMATIC // TRACES\nConnection Logic Flow-chart:\nPROFILE RELATIONSHIP\nNephyrin / collected profile\nContributor: Proton. Forker: SteamKit and open-steamworks.\n▼ Collected fork relationship\nCOMMUNITY LIBRARY\nSteamRE/SteamKit\nPublic Steam network library maintained in the SteamRE organization.\n▼ Declared SteamKit2 dependency\nDOCUMENTED AUTOMATION\nJustArchiNET/ArchiSteamFarm\nDocuments card farming across multiple accounts and a SteamKit2 dependency.\nEVIDENCE REVIEW / SOURCE SNAPSHOT\nRECORDED: distinct contributor and forker labels.\nDOCUMENTED: public libraries support programmatic Steam interactions.\nOPEN QUESTION: specific code authorship, platform approval and abuse attribution require separate evidence.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "The code. The contributors. The forks."
          },
          {
            "level": 2,
            "id": null,
            "text": "1. Nephyrin: forks and contributions"
          },
          {
            "level": 2,
            "id": null,
            "text": "2. Public capabilities: automation without the desktop client"
          },
          {
            "level": 2,
            "id": null,
            "text": "3. JoeLudwig: the hl2sdk contributor label"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/de/investigation_part2.html#automation-map",
          "https://github.com/SteamRE/SteamKit",
          "https://github.com/SteamRE/open-steamworks",
          "https://github.com/alliedmodders/hl2sdk",
          "https://github.com/DoctorMcKay/node-steam-user"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/en/output_steam_network__valve_ru_farming_isolated.content.json",
      "export_json_sha256": "9aebda2a748b92d7819d29cd0f036f25a17fbd9be9d436694a69b2d2b1f02e84"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "de/card_economy.html",
      "language": "de",
      "title": "The card economy — The Steam Dossier",
      "source_url": "https://phishdestroy.io/steam_dossier/de/card_economy",
      "source_html_sha256": "fc166547823839ab15664fc686d01d886b66c002377d4aae6be8982cb3c4cd41",
      "exported_at": "2026-09-29T00:16:06.361Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "card_economy.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/de/card_economy.pdf?v=print-20260929-v5",
        "sha256": "8a5f0fd0f0f3a0a609ab1a17c1a3cc8612b4ffdccb5e50bac8818564f0249fac",
        "bytes": 262444,
        "pages": 25
      },
      "integrity": {
        "signed_object": "card_economy.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "card_economy.content.json.asc",
        "digest_file": "card_economy.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify card_economy.content.json.asc card_economy.content.json",
          "sha256sum -c card_economy.content.json.sha256"
        ]
      },
      "content": {
        "text": "BEWEISSTÜCK V — DIE KARTENÖKONOMIE\nEine Bot-Farm ist kein Leck in Valves Laden. Es ist ein Kunde.\n\nEin Steam-Konto kann keine einzige Sammelkarte erhalten, bis es $5.00 im Laden ausgegeben hat. Es kann ein Spiel nicht farmen, das es nicht besitzt, und es kann auch nicht eines farmen, das es kostenlos erhalten hat. Daher hat ein automatisierter Karten-Farm vor der Produktion eines einzigen Gegenstands bereits seinen Weg bezahlt – pro Konto, zu einem Preis, den Valve veröffentlicht. Anschließend nennt Valve's Automatisierungsklausel Zeile für Zeile genau, was dieser Farm produziert; seine Lizenz verbietet jeden Weg, durch den ein gefarmtes Kartenstück in Geld umgewandelt wird; und sein Markt nimmt einen Anteil, wenn die Karte ohnehin verkauft wird – beworben mit 15%, aber auf zwei Cent pro Verkauf begrenzt, was bei einer Karte, die in Cent bewertet wird, den größten Teil des Preises ausmacht. Dieses Beweisstück misst die Größe dieses Handels, was der Preis für das höchste Level in einem Profil in Sets kostet, und was Valve's Durchsetzungsteam mit derselben Klausel macht, wenn das Konto einem gewöhnlichen Händler gehört.\n\nWas eine Farm zunächst kaufen mussWas ein Level in Sets kostetBeide Seiten des SchreibtischesWer moderiert die Kartenökonomie?\n$5.00Speichere Ausgaben, bevor ein Konto eine Karte erhalten kann — eigener Supportbereich von Valve\n13,876Spiele auf Steam, die Sammelkarten ausgeben, die 99.971 verschiedene Kartentypen umfassen\n694,673Gegenwärtig verfügbare vollständige Kartensätze, die von 91 börsennotierten Handelsbots gehalten werden\n1,389,346Konten- und Spielkartenabwurfgenehmigungen, die das Bestand bereits mindestens verbraucht hat\n$9.99Mittlerer Preis eines Sammelkarten-Spiels — sein fertiges Set wird für einen mittleren Preis von 0,74 US-Dollar verkauft.\n97,114Mitglieder der Sammelkarten-Handelsgruppe, deren Moderatorliste einen Valve-Mitarbeiter enthält — § 08\n01 — Der Prozess\nWas eine Farm tatsächlich ist, Schritt für Schritt\n\nBeschrieben ausschließlich aus der eigenen Dokumentation des Tools und den eigenen Supportseiten von Valve. Nichts in diesem Abschnitt wird aus der Ferne geschlossen und nichts wird von beiden Parteien angezweifelt.\n\nSchritt 1\nEinstieg\n\nDas Konto darf nicht eingeschränktsein. Valves Supportseite schließt eingeschränkte Konten von \"Teilnahme am Steam-Markt\", von \"Handel mit Steam-Community-Items (Sammelkarten, Booster-Packs, Edelsteine usw.)\" und von \"Erreichen von Steam-Profil-Leveln (Gesperrt auf Stufe 0) und Handel mit Sammelkarten\" aus. Die Mindestausgabe-Schwelle ist das Geld: \"Sie müssen mindestens 5,00 USD im Steam-Store ausgeben.\"\n\nSchritt 2\nSpiele kaufen\n\nKarten fallen nur aus besitzenen Spielen. \"Sie müssen das Spiel auf Ihrem Steam-Konto besitzen, um für jegliche Kartenabwürfe aus diesem berechtigt zu sein. Familienfreigabe ist kein Besitz und zählt nicht.\" Auch die kostenlosen Routen sind geschlossen: \"Bezahlte Spiele, die Sie während einer Promotion kostenlos erhalten haben, können nicht für Kartenabwürfe genutzt werden\", und \"Sie können keine Karten aus Free-to-Play-Spielen abwerfen, ohne darin Geld auszugeben.\"\n\nSchritt 3\nKarten farmen\n\nDas Tool meldet das Konto in das Steam-Netzwerk ohne Benutzeroberfläche an, \"parsing Ihre Abzeichen\", erstellt die Liste der anbaubaren Titel und beginnt, \"ein berechtigtes Spiel zu spielen und regelmäßig zu überprüfen, ob das Spiel bereits vollständig gefarmt ist.\" Die Beschreibung des Mechanismus durch seinen Betreiber: Es \"tut nichts anderes als Steam zu sagen, dass wir das angegebene Spiel spielen.\"\n\nSchritt 4\nDrops aufgebraucht\n\nJeder Titel ist begrenzt. \"Jedes Spiel hat eine festgelegte Anzahl an Kartenabwürfen. Sobald alle davon (etwa die Hälfte des vollen Sets) abgeworfen sind, ist das Spiel nicht mehr für die Farming geeignet.\" Ein Farm, der weiterhin produzieren möchte, muss Titel kaufen. Die Kartenversorgung wird durch Käufe gedrosselt – nach Design und zugunsten von Valve.\n\nSchritt 5\nAuszahlen\n\nDie Karte verlässt durch eine von drei Türen: sie wird auf dem Community-Markt verkauft, weiterverkauft oder in Edelsteine zerkleinert. Jedes Mal handelt es sich um eine Transaktion im Abo-Marktplatz oder einen Handel, und § 3.D behält die Gebühr bei: \"Valve kann eine Gebühr für Transaktionen im Abo-Marktplatz erheben.\" Dies ist der Schritt, der die gesamte Angelegenheit zu einem Verstoß macht — siehe 05.\n\nQuellen, gelesen und wörtlich zitiert am 22. September 2026: Steam Support — Begrenzte Benutzerkonten ↗ · ArchiSteamFarm FAQ ↗ · Valve — Steam Trading Cards FAQ ↗ · Steam-Nutzervereinbarung ↗ archiviert am 24. September 2026 ↗. ArchiSteamFarm wird auf dieser Seite als Messinstrument verwendet, nicht als Angeklagter; seine eigene Dokumentation stellt klar, dass \"ASF ist nicht durch Valve autorisiert\".\n\n02 — Die Skala\nBevor eine Farm einen Cent verdient, hat sie bereits Valve bezahlt\n\nWeil ein eingeschränktes Konto keine Karte empfangen kann, muss jedes Konto in einer Farm vor der Erzeugung von etwas aus dem eingeschränkten Status herausgekauft werden. Der Schwellenwert wird veröffentlicht und wird pro Konto berechnet.\n\nAnzahl der Farmen\tWoher die Nummer stammt\tMindesteinkaufssumme zur Erlangung der Kartenberechtigung\n10 Konten\tDie Obergrenze ASF empfiehlt — \"basierend auf internen Valve-Richtlinien sowie unseren eigenen Vorschlägen\"\t$50\n100–200 Konten\tTechnischer Schwellenwert im gleichen FAQ: \"Sie können bis zu 100-200 Bots mit einer einzigen IP-Adresse und einer einzigen ASF-Instanz betreiben\"\t500 – 1.000 US-Dollar\n120 Konten\tDurchsetzungsfall 3 unten – dauerhaft gesperrt\t$600\n170 Konten\tDurchsetzungsfall 2 unten – während des Winterverkaufs 2017 dauerhaft gesperrt\t$850\n1.000 Konten\tDurchsetzungsfall 1 unten — Handelsbann\t$5,000\n5.000 Konten nicht überprüft\tBetreiber skalierten gemeldet und nicht unabhängig überprüft — siehe Notiz zur Quellensuche\t$25,000\n10.000 Konten nicht überprüft\tBetreiber skalierten gemeldet und nicht unabhängig überprüft — siehe Notiz zur Quellensuche\t$50,000\n\nDie letzten beiden Zeilen sind die einzigen Zahlen auf dieser Seite, die auf einem nicht überprüften Bericht und nicht auf einem Dokument basieren — sie sind in der Tabelle markiert, in der Anmerkung zur Quellensucheerklärt und nichts anderes hier hängt von ihnen ab. Die rechte Spalte bezieht sich auf die arithmetischen Berechnungen anhand des von Valve veröffentlichten $5.00 USD-Schwellenwerts und nichts anderes. Es ist eine Untergrenze, keine Schätzung dessen, was eine Farm kostet oder was Valve erwirtschaftet: Es schließt die Spiele aus, die besessen werden müssen und die nicht kostenlos in einer Promotion gekommen sein können, und es schließt die etwa 15%, die der Community Market einbehält, wenn die Karten verkauft werden. Auf dieser Seite wird keine Einnahmezahl angegeben.\n\nUnd Valve hat selbst einen Kartenabwurf bewertet. Sein FAQ zu den Trading Cards gibt den Umtauschkurs für das Free-to-Play-Modell in klaren Dollar an:\n\n\"Kostenlose Spiele verteilen Sammelkarten basierend auf Ihren In-Game-Käufen. Für jeden ausgegebenen Betrag von 9 USD (ungefähre Angabe) seit dem Start der Steam Trading Card Beta, erhalten Sie eine Karte.\"\n\n— Valve, Steam Trading Cards FAQ ↗ · verified verbatim 2026-09-22\n\nEine Sammelkarte ist keine Aktion, auf der die Plattform Geld verliert. Es ist etwas, das Valve verkauft, zu einem von Valve veröffentlichten Preis – und verkauft sie dann zum zweiten Mal weiter. Deshalb ist die ehrliche Beschreibung einer Karten-Farm nicht Parasit. Es ist Großhändler.\n\nWie groß das tatsächlich gekaufte Objekt ist\n\nAlles von hier bis zum Ende dieses Abschnitts wird gemessen, nicht berichtet. Die Kartenzählung ist die veröffentlichte Abzeichenpreissliste von Steam Card Exchange; die Preise der Spiele selbst stammen aus dem eigenen Store-API von Valve; der Bot-Vorrat kommt aus einem öffentlichen Bot-Verzeichnis, das jeder öffnen kann. Alle drei wurden am 22. September 2026 gelesen, und die Arithmetik ist vollständig in Abschnitt 08 dargestellt.\n\n13,876Spiele, die Karten ausgeben\n99,971Unterschiedliche Kartentypen\nDie Berechnung der Multiplikation von 5, 6 und 15 ergibt: 5 · 6 · 15 = 450Karten pro Satz: min, median, max\n$0.74Mittlerer Preis eines fertigen Sets\n$23,586.57Eines von jedem Satz am Markt\nWie groß ein Set ist\n\n13.876 Spiele durch Karten im Satz. Valve gibt etwa die Hälfte davon auf ein jedwedes Konto.\n\n0\n1,250\n2,500\n3,750\n5,000\n5\n6\n7\n8\n9\n10\n11\n12\n13\n14\n15\nWas die Lizenz kostet\n\nListepreis der gleichen Spiele im Steam-Shop, in US-Dollar.\n\n0\n1,000\n2,000\n3,000\n4,000\n<$1\n$1-3\n$3-5\n$5-10\n$10-20\n$20-40\n$40+\nWas das fertige Set einbringt\n\nMarktpreis des abgeschlossenen Sets für die gleichen Spiele.\n\n0\n1,500\n3,000\n4,500\n6,000\n<$0.50\n$0.50-1\n$1-2\n$2-5\n$5-10\n$10+\n\nLesen Sie die zweiten und dritten Diagramme gegeneinander ab und die Form des Handels ist ohne Arithmetik erkennbar: Die Spiele konzentrieren sich im Bereich der Zehnerdollars, die durch die Spiele erzielten Sets konzentrieren sich unter einem Dollar. Beide sind Zählungen derselben 13.876 Spiele, auf der gleichen Achsen-Einheit, sodass die Vergleichsgrundlage zwei Höhen sind und nicht zwei Skalen.\n\nDas ist die Angebotsseite. Die Nachfrageseite ist der Teil, den Valve nicht bewerben muss, weil er bereits öffentlich vorhanden ist: Ein einzelnes offenes Verzeichnis von Kartenhandelsbots listet 91 Bots auf, die zu diesem Zeitpunkt 694.673 vollständige Sets im Lager haben. Keine Anmeldung, keine Auslesung eines Marktplatzes, keine privaten Daten – die Lagerzahl ist auf der Seite neben jedem Botnamen abgedruckt.\n\nDie Aktie in die einzige hier relevante Einheit umwandeln. Regeln von Valve selbst: \"Die meisten Spiele lassen eine Anzahl von Karten fallen, die der Hälfte der Karten im Kartensatz des Spiels entspricht… Sie müssen die andere Hälfte des Sets von anderen Mitgliedern der Community sammeln.\" Ein Konto kann niemals einen Satz durch Spielen vervollständigen. Zwei, mindestens, jedes besitzend, jedes seine einmal pro Spiel fallende Anzahl an Karten verbrauchend. Fallen werden nicht regeneriert.\n\n694,673Bestände, 91 öffentliche Bots\n3,473,365Karten, bei einer Mindestanzahl von 5 Karten\n1,389,346Abgenommene Freibeträge, Mindestausgabe-Schwelle\n2,602Konten, die ein einziges Spiel besitzen, dichteste Bot-Farm\nWo die 694.673 Sets liegen\n\nDie zwölf größten unter den 91 börsennotierten Kartenbetrügerbots, nach vollständigem Lagerbestand. Die zehn größten besitzen gemeinsam 248.115 Sets – das entspricht 35,7% des gesamten Bestands.\n\n0\n11,250\n22,500\n33,750\n45,000\nCard Supply #4 (High)\nN!vq's Leveling (High)\nAlice [BOT] LEVEL-UP RARE SETS\nN!vq's Leveling (Low)\nDisco Lite Level Up\nN!vq's Leveling (Mid)\nbaty131store.net | Level Up\nKitten - Supreme\nArashirn | Level Up\nSH (Junior) Level Up\nDuobot.com - Overstock\nlvlupbot.com - godlike\n\nJeder der 1.39 Millionen Lizenzen gehörte zu einem Konto, das das Spiel besaß, die $5.00-Mindestausgabe-Schwelle überschritt und niemals diese Drops mehr produzieren kann. Dies ist unverkaufter Bestand auf neunundneunzig Bots. Es ist kein Maß für den Markt; es ist ein Maß für das, was nach dem Markt übrig bleibt.\n\nDie letzte Zahl ist eine Untergrenze, nicht eine Kopfzahl. Ein Bot listet 14.310 Sets aus nur 11 Spielen auf, sodass mindestens eines dieser Spiele durch 1.301 Sets repräsentiert wird, was mindestens 2.602 verschiedene Konten bedeutet, die dieses Spiel gekauft haben. Es ist die kleinste Zahl, die die Arithmetik erlaubt, und es betrifft einen Bot aus neunundneunzig.\n\nWas diese Untergrenze aussagt und was nicht\n\nDiese Bots kaufen Karten sowohl von normalen Spielern als auch von Farmen – ihre veröffentlichten Kaufraten sind der Punkt des Verzeichnisses. Daher sind die 1,39 Millionen Lizenzen keine Zählung der von Farmen besitzenden Konten. Sie sind eine Zählung der einmal pro Konto, einmal pro Spiel fallenden Drop-Lizenzen, die irgendwo auf Steam ausgegeben wurden und unverkauft in kommerziellem Lager geblieben sind. Ob das hinter jedem Konto stehende Konto eine Farm oder ein Teenager war, der seine Abzeichen-Seite bereinigte, ändert nichts daran, was Valve einnahm: die $5,00 Freischaltung, die Spiel-Lizenz und eine Marktprovision bei jedem Schritt – nicht 15%, sondern 15% oder die beiden einzentigen Mindestbeträge, je nachdem, welcher Betrag höher ist, was bei einer Karte, die in Zentimen bewertet wird, weit überlegen ist. Die Mathematik ist in der Gebühren-Rangliste untendargestellt. Das ist der Punkt dieser Seite, und es ist keine Beschwerde über Farmer: dasselbe Verhalten, das Valve mit einer Gebühr belegt, wird wortwörtlich zitiert, wenn ein Individuum aufgrund des \"kommerziellen Gebrauchs\" dauerhaft gesperrt wird.\n\nDas Diagramm ist auch in einem zweiten Sinne eine Untergrenze. Es zählt nur Bestände, die heute noch nicht verkauft und auf Bots gelistet sind, die sich in einem öffentlichen Verzeichnis aufhalten . Alles, was bereits verkauft wurde, alles, das privat gehalten wird, und jeder Bot außerhalb des Verzeichnisses wird ausgeschlossen.\n\nUnd die Landwirtschaft bezahlt sich bei den Preisen von Valve nicht selbst aus.\n\nDie offensichtliche Einwendung lautet, dass eine Farm billige Spiele kauft, um teure Karten zu prägen. Steams eigener Store API spricht dagegen. Von den 13.876 Karten-Spielen wurden die Preise für 13.713 ermittelt; 12.918 sind bezahlte Titel mit einem mittleren Listenpreis von 9,99 USD. Der mittlere abgegebene Satz wird für 0,74 USD verkauft. Für jeden Satz sind zwei Lizenzen erforderlich. Daher kostet der mittlere Satz etwa 19,98 USD an Spiel-Lizenzen für die Produktion und bringt 0,74 USD ein.\n\nGemessen am 22. September 2026\tWert\tWas es klärt\nMittlere Listenpreis, Karten tragendes Spiel\t$9.99\tDie Lizenz ist der teure Teil der Transaktion, nicht die Karte\nSpiele, die mit $4,99 oder weniger bewertet sind\t3,665 (28.4%)\tSelbst das billige Leder ist teurer als das, das es liefert.\nAm billigsten erhältlichen Sammelkarten-Spiel im Laden\t$0.99\tZwei Lizenzen, 1,98 USD, für ein Set, das typischerweise unter 1,30 USD verkauft wird.\nSpiele, deren Sammlung für mehr als das Spiel verkauft wird\t323 von 12.918 (2,5%)\tKarten-Arbitrage gegen die Listenpreise von Steam besteht in 1 Spiel von 40.\nFreiespiel-Titel in der Zählung\t795\tUnd Valve bewertet jeden ihrer Drops mit einem Wert von 9 US-Dollar an In-Game-Ausgaben.\n\nWelches die wirtschaftliche Frage zugunsten von Valve und gegen die allgemeine Geschichte schließt. Bei den Preisen, die Valve selbst verlangt, ist Karten-Farming eine verlustbringende Aktivität, die nur auf Lizenzen funktioniert, die unter dem Listenpreis von Steam erworben wurden — Bündel, regionale Preise, Schlüssel-Wiederverkauf. Die Karten sind das Restprodukt. Der Kauf ist das Ereignis. Und der Kauf fand auf Steam statt.\n\nWas die Farm tatsächlich unterstützt\n\nDie Teile zusammenfügen und die Farm beginnt nicht mehr so auszusehen, als etwas, das Valve duldet, sondern wie etwas, das Valve benötigt. Jeder von einer Farm gelieferte Input ist ein Output, den Valve meldet oder abrechnet. Folgen Sie einem Bot-Account nach außen:\n\nOne farmed accounta \"wholesale customer\", not a leak\nGame sales\n\nKauft die Titel, die es anbaut — von den 13.876 Kartenspielen bis zum $0,50 Shovelware — weil Karten nur aus besitzenen Spielen fallen.\n\n\"Online\" & playtime\n\nIdles sie, um Karten fallen zu lassen, und versorgt die concurrent-player- und hours-played-Zahlen, die Valve als Engagement anführt – die genaue Statistik, die § 4.C als \"falsche Spielzeit\" bezeichnet.\n\nRegistrations\n\nMuss die $5.00-Mindestausgabe-Schwelle für ein eingeschränktes Konto vor dem Erhalt einer Karte klarstellen — ein echtes Ladengeschäft Valve-Buch pro Konto.\n\nWallet money & fees\n\nJede Karte, die es verkauft, wird zurückgeleitet durch den Markt, wo die Gebühr bis zu 66,7% auf einer Karte niedriger Werte beträgt und die Einnahmen im Steam Wallet gesperrt bleiben.\n\nSteam-level PR\n\nDie Abzeichen und Ebenen, die Valve präsentiert, existieren nur, weil Sets hergestellt wurden — und an der Spitze dieser Rangliste sind es Bots (vgl. § 03).\n\nDie Farm wird entfernt und jede Nummer darüber fällt — das Spiel wurde weniger Kopien verkauft, das \"Online\"-Spiel war kleiner, das Konto wurde nie registriert, die Gebühr wurde nie erhoben und das Level wurde nie erreicht. Daher coexistiert eine Regel, die die Automatisierung verbietet, mit Millionen automatisierter Konten: Das Verbot ist die Option, und die Aktivität ist der Gewinn.\n\nUnd der eigentliche Auszahlungsprozess ist ein Wertverlust, den Valve zweimal besteuert.\n\nDie Karte ist nicht das Ende des Zyklus. Die eigenen Mechanismen von Valve erlauben es, eine Karte in Edelsteine zu zerkleinern, und Edelsteine können ausgegeben werden, um Booster-Pakete zu craften – drei weitere Karten – die verkauft oder erneut zerkleinert werden. Jeder Schritt ist eine Markttransaktion oder eine Konvertierung, und jede wird besteuert. Die Richtung dieses Zyklus ergibt sich aus der unterhalb gemessenen Gebührenuntergrenze und erfordert keinen externen Modell: jede Karte, die darin verkauft wird, gibt zumindest zwei Zentimeab, bei Karten, die für drei bis fünf gehandelt werden, so dass jeder Umdrehung des Hebels weniger zurückkommt als hineingegangen ist. Der Zyklus zerstört virtuellen Wert und zwingt frische, gebührenpflichtige Transaktionen, ihn zu ersetzen. Hier wird keine Zahl für die Größe dieses Verlustes angegeben – der pro-Set-Gewinn hängt von den Edelsteinkursen und den Booster-Wahrscheinlichkeiten ab, die diese Untersuchung nicht gemessen hat.\n\nTrading carddrops from owned game\n→\nGemscard crushed, fee taken\n→\nBooster packgems spent to craft\n→\n3 new cardssold on Market, fee taken\n↶\n\nNur die Mechaniken werden hier behauptet, und sie sind Valve's eigene — Karten werden in Edelsteine umgewandelt, Edelsteine verzaubern Booster, Booster liefern Karten — alles dokumentiert im Steam Trading Cards FAQ, und jeder Schritt ist ein steuerpflichtiges Marktgeschehen. Quelle der Loop-Mechaniken: Valve, Steam Trading Cards FAQ ↗.\n\nDies ist kein Moment. Es handelt sich um eine Branche mit einem mehrjährigen Rückgrat.\n\nEin einzelnes Bild könnte ein Zufall sein. Daher wurde der öffentliche Card-Bot-Verzeichnis einmal pro saisonalem Steam-Verkauf, zurück bis 2022 bis 2026, mittels der Wayback Machine gelesen — die Menge der Sets, die die Bots führten, und die gleichen Konten, Verkauf nach Verkauf. Die Wirtschaft erscheint und verschwindet nicht; sie besteht fort, mit einem stabilen Kern von Betreibern, und sie erreichte ihren Höhepunkt bei über drei Millionen vollständigen Sets im Lager während des Winter 2023-Verkaufs — in der Größenordnung eines Drittels einer Million TF2-Schlüssel von Wert, die zu einem bestimmten Moment in einem Verzeichnis gehalten wurden.\n\nVollständige Kartensets im öffentlichen Bot-Verzeichnis, nach Steam-Sale\n\nEin Wayback-Snapshot von steam.supply/CardBots pro saisonalem Verkauf. Mit Mauszeiger über dem Bild verbleiben, um den Wert in TF2-Schlüsseln zu dem Zeitpunkt des Snapshots zu sehen.\n\n0.0M\n0.9M\n1.8M\n2.6M\n3.5M\nA’22\nS’23\nW’23\nS’24\nW’24\nS’25\nS’26\n401Unterschiedliche Bot-Konten, die bei den Verkäufen beobachtet wurden\n59Vorhanden in 5 oder mehr von 7 Verkäufen — das stabile Kernstück\n16In jedem der 7 Verkäufe präsent, 2022–2026\n3.22 MillionenSpitzenwerte im Aktienbestand (Winter 2023) ≈ 570.000–790.000 USD in Schlüsseln\nWie die Abzeichen-Rangliste eines Verkaufs von oben aussieht\n\nDie Nachfrage entspricht dem Angebot. Auf der öffentlichen Sommerverkauf 2024 Abzeichen-Rangliste am 16. Juli 2026 archiviert ↗, hatte das erste Konto den Verkaufabzeichen 1.740.645 Mal angefertigt — 1,74 Millionen Zehner-Sets, 17,4 Millionen Karten in eine einzige Profildekoration verbraucht. Bei dem eigenen Marktpreis des Verkaufs (0,50 USD pro Set) entspricht das ~$870.000 an Kartenwert; so gekauft, wie es tatsächlich gekauft wird — TF2-Schlüssel, die an Level-Up-Bots für etwa 7,6 Sets pro Schlüssel gehandelt werden — es sind ~229.000 Schlüssel, etwa $410.000–$570.000 in realen Werten. Das zweite Konto: 552.000 Sets, ~$130.000–181.000. Kein Mensch spielt dafür. Es wird gekauft, und jeder Schritt des Kaufs ist eine Transaktion, die Valve abwickelt.\n\nVerfahren und Grenzen: Der Bestand wird summiert, indem die auf jedem Schnappschuss aufgelisteten Bots zusammengefasst werden; die Anzahl der Bots pro Schnappschuss ist nicht vergleichbar zwischen den Verkäufen, da einige Schnappschüsse nur die gefeatureten Bots und einige den vollständigen Verzeichnis zeigen, sodass der Bestand als Untergrenze für das Sichtbare gelesen wird, nicht als Zählung. Schlüsselwerte nutzen die Medianwertrate der beworbenen Sets pro Schlüssel auf jedem Schnappschuss und einen TF2-Schlüssel im Preisbereich von $1,79–$2,49. Die Kontinuität wird durch SteamID64 über die Schnappschüsse hinweg gewährleistet. 2021-Schnappschüsse verwendeten ein älteres Seitendesign und sind nicht enthalten. Daten: farm-economy-timeline.json; Abzeichenstufen von SteamLadder; Setpreise von Steam Card Exchange (Wayback-Snapshots zum Verkaufzeitpunkt, $0,05 pro Karte).\n\nUnd die gleiche Flotte ist dort, wenn kein Verkauf läuft.\n\nDie beiden oben abgebildeten Bilder stellen nicht zwei Populationen dar. Es handelt sich um eine Flotte, die zu verschiedenen Zeitpunkten fotografiert wurde. Das Verzeichnis, das oben in diesem Abschnitt gelesen wurde, wurde an einem normalen Tag gelesen, an dem keine saisonale Verkaufsaktion lief — 2026-09-22 — und selbst im Ruhezustand hielt es 91 Bots und 694.673 vollständige Sets: auf dem Niveau von 186.000 TF2-Schlüsseln, einem Wert von $334.000–$464.000 an Sammelkarten, die zwischen Verkäufen untätig sitzten. Das ist die Untergrenze, die die Operation trägt, wenn nichts passiert.\n\nUnd es handelt sich um die gleiche Operation. Gerechnet nach SteamID64, 87 von diesen 91 ruhenden Bots – 96% – erscheinen in den sieben Verkaufsschnitten oben, davon sind sechzehn in jedem einzelnen. Das Verzeichnis ist nicht ein Schalter, der für den Verkauf geöffnet und danach wieder geschlossen wird; es ist ein stehendes kommerzielles Inventar, das diese gleiche Flotte so hoch geschwollen hat, wie 3.22 Millionen Sets am Winter 2023 Höchststand und nie auf Null fällt. Ein Verkauf ist, wenn er verkauft wird. Er existiert auch den Rest des Jahres.\n\nDas ruhende Verzeichnis, Bot für Bot\n\nJeder Quadrat ist ein Bot im Verzeichnis vom 22. September 2026, hervorgehoben, wenn er auch in den sieben Verkaufsschnitten vorkommt. 91 ist, was das Verzeichnis an diesem Tag aufgelistet hat, nicht die Größe der Flotte — 401 verschiedene Konten treten in den Verkaufsschnitten auf, und das Verzeichnis zeigt an verschiedenen Tagen unterschiedliche Stichproben dar.\n\nSeen in past sales (87) New since last snapshot (4)\n\nNicht-verkaufsbezogene Ausgangswerte vom 22. September 2026 aus demselben öffentlichen Verzeichnis gelesen, ohne Anmeldung. Der Ruhezustandswert nutzt die von jedem Bot beworbenen Sets-pro-Schlüssel-Geschwindigkeit und die Schlüsselbandbreite von $1,79–$2,49. Überschneidungen erfolgen durch SteamID64 gegen die sieben Verkaufs-Snapshots. Da das Verhältnis von Ausgabe-gegen-Vollanzeige von Snapshot zu Snapshot variiert, wird hier die Lagerbestands- und Identitätsübereinstimmung verglichen, nicht die Anzahl der Personen. Die Arithmetik im Abschnitt 08.\n\n03 — Die Rangliste\nDas andere Produkt ist die Nummer neben Ihrem Namen\n\nKarten sind das Rohmaterial. Das Fertigprodukt ist ein Steam-Level, und Valve hat seinen Preis in Sets festgelegt.\n\n100Steam Level\nTarget level — drag or use the arrow keys\nPrice of one complete set, USD\n\n0,20 US-Dollar ist das billigste vollständige Set in der Zählung, 0,74 US-Dollar der Median, 1,70 US-Dollar das Durchschnittswert. Das Diagramm bezieht sich nur auf die Karten — niemals auf die $5,00-Schwelle oder die Spiel-Lizenzen.\n\n55,000XP required\n550Complete sets consumed\n110Games to own, farming it yourself\n$407.00Cost of the cards at that price\n1,100Drop allowances burned, minimum\n$5,500.00$5.00 wird freigeschaltet, wenn kein Konto wiederverwendet wird\nVerbrauchte vollständige Sets, Level 1 bis 1.000\n\nEin Abzeichen herstellen = ein vollständiges Set = 100 XP. Jedes Level innerhalb eines Blocks von zehn kostet 100 XP mehr als der Block darunter.\n\n0\n12,625\n25,250\n37,875\n50,500\n1\n250\n500\n750\n1000\n667\n550 sets\n\nEin Level ist keine Dekoration, die Valve unberührt lässt. Es ist in das Konto integriert. Aus dem eigenen FAQ von Valve zu den Trading Cards, darüber, was man durch das Erstellen eines Abzeichens erhält: \"100XP, die möglicherweise Ihren Steam-Level erhöhen können. Wenn Ihr Steam-Level steigt, wird die Obergrenze der Größe Ihrer Freundesliste um fünf erhöht, und es besteht die Möglichkeit, die Fähigkeit zu entsperren, Ihr Profil mit Ausstellungen anzupassen.\" Und zu den Boost-Packs: \"Ihr Steam-Level erhöht Ihren Erfolgswahrscheinlichkeitsfaktor für das Erhalten eines Boost-Packs: Level 10: +20%… Level 50: +100% Erhöhung Ihrer Erfolgsrate (d.h. die Rate hat sich verdoppelt).\"\n\nSomit erwirbt das Level zwei Dinge, die Valve steuert: wie viele Freunde Sie haben dürfen, und wie schnell kostenlose Karten in Ihren Inventar fallen. Der zweite Faktor verstärkt sich – je mehr Sets Sie konsumiert haben, desto schneller gibt die Plattform Ihnen mehr Material. Valve hat den Wiedereinsatzzyklus in das Produkt integriert.\n\nDer Wechselkurs ist festgelegt und veröffentlicht. Ein Abzeichen-Rangliste erfordert einen vollständigen Satz und bringt 100 XP; \"Sie können für dasselbe Spiel höchstens fünfmal einen Satz herstellen.\" Der XP-Aufwand für ein Level steigt alle zehn Level. Das ergibt folgendes, und hierbei handelt es sich um keine Schätzung:\n\nStufe des Dampfes\tVollständige Sets, die es verbraucht\tSpiele, die Sie besitzen müssen, um sie selbst herzustellen.\tBei dem billigsten in der Aufzeichnung festgehaltenen Satz ($0.20)\tBei der Median-Einstellung ($0,74)\tSkala\n10\t10\t2\t$2.00\t$7.40\t\n50\t150\t30\t$30.00\t$111.00\t\n100\t550\t110\t$110.00\t$407.00\t\n200\t2,100\t420\t$420.00\t$1,554.00\t\n500\t12,750\t2,550\t$2,550.00\t$9,435.00\t\n667\t22,579\t4,516\t$4,515.80\t$16,708.46\t\n\n667 ist keine Hypothese. Es ist das höchste Niveau, das ein einzelner Bot im öffentlichen Verzeichnis für Kunden anpreisen kann, von den 33.359 Sets, die er über 6.117 Spiele hält. Die vierte Spalte zeigt dieselbe Rangliste, bewertet gegen das billigste vollständige Set überall in der Zählung; die fünfte Spalte gegen das Median. Beide sind Marktpreise für die Karten allein und schließen die $5.00 Freischaltung sowie die Spielelizenzen vollständig aus.\n\nWie die Kurve überprüft wurde, da Valve sie nicht veröffentlicht\n\nDie Valve gibt die Abzeichenquote an (bei \"jedes 100 XP gibt dir einen zusätzlichen Steam-Level\") und schränkt dies dann ein — \"(zumindest zu Anfang)\" — ohne die Eskalation zu veröffentlichen. Die obige Kurve ist die Standardkurve, in der jeder Level innerhalb eines Blocks von zehn 100 XP mehr kostet als der darunter liegende Block. Diese wurde gegen das Verzeichnis überprüft und nicht angenommen: Für jeden Bot, dessen angegebener Maximalwert durch seinen Vorrat begrenzt ist und nicht durch die Obergrenze von fünf Herstellungen pro Spiel, passt der Level, der aus dieser Kurve berechnet wird, genau zu dem Level, den der Bot anzeigt — 541 gegen 541, 494 gegen 494, 464 gegen 464. Wo die Obergrenze bindet, liegt die berechnete Zahl um einige Level höher, was eine Obergrenze tun sollte, die auch von der Tiefe des Vorrats pro Spiel abhängt. Es wird keine Behauptung über die Kurve über Level 667 hinaus gemacht.\n\nDen Lader neben dem Abschnitt 02 lesen und die Form des Unternehmens wird sichtbar. Um ein Konto auf Stufe 500 zu bringen, muss jemand 12.750 vollständige Sets zusammenstellen. Jedes dieser Sets hat mindestens zwei Konten Drop-Guthaben verwendet, jedes dieser Konten hat die $5,00-Schwelle überschritten und besaß das Spiel. Ein Eitelkeitsnummer an der Spitze eines Profils ruht auf mindestens 25.500 untergeordneten Drop-Guthaben. Valve verliert diesen Handel nicht. Valve ist Gegenpart jeder seiner Positionen.\n\n04 — Die Statistiken\nDer Satz beschreibt die Farming-Praxis nicht vage, sondern listet sie auf.\n\n§ 4.C ist kein allgemeines Anti-Bot-Satz. Seine aufgezählten Beispiele nennen nacheinander die zwei Dinge, die eine Karten-Farm produziert.\n\n\"Es ist Ihnen untersagt, jegliche Form von Skripten, Bots, Makros oder anderen nicht-menschgesteuerten Systemen ('Automatisierung') zur Interaktion mit Inhalten und Diensten auf Steam in irgendeiner Weise zu nutzen, einschließlich, aber nicht beschränkt auf:\n\nAutomating the Steam account creation process,\nFaking gameplay statistics (e.g., inflated wins or losses, XP, playtime),\nEarning rewards or progress without genuine user input,\nParticipating in adjudication systems (like peer reviews or 'overwatch') through automated means, including influencing outcomes or reporting users by scripted action rather than informed judgment.\"\n— Steam Subscriber Agreement § 4.C ↗ archiviert unter 2026-09-24 ↗ · retrieved and quoted verbatim 2026-09-22\nSpielzeit\n\nDie Leerstunden sind keine Phantomstunden. Die ASF FAQ beantwortet die Frage direkt – \"Warum erhöht sich die Spielzeit von durch ASF gefarmten Spielen nicht?\" – mit: \"Ja, aber nicht in Echtzeit. Steam protokolliert Ihre Spielzeit in festen Intervallen und plant Updates dafür… es wird in der Regel etwa alle 30 Minuten aktualisiert.\"\n\nDiese Stunden finden sich in den Aufzeichnungen von Valve, auf den Ladenseiten von Valve und in den gleichzeitig spielenden Spielerzahlen, die Valve auf seinen eigenen Steam Charts ↗ archiviert am 23. September 2026 ↗. In diesen Zahlen ist ein inaktives Konto nicht von einem spielenden unterscheidbar. Die Engagement-Zahlen, die die Plattform nach außen gibt, werden über eine Bevölkerung berechnet, die gemäß den eigenen Regeln der Plattform auch Konten umfasst, die nicht spielen.\n\n\"ohne echten Benutzerinput\"\n\nDies ist eine Definition eines stillgelegten Kartenabwurfs, erstellt von Valve. Es handelt sich ebenfalls um eine Definition des Steam-Niveaus, des Abzeichens, der Qualifikation für Booster-Packs und des damit verbundenen Profil-XP — das ASF FAQ bestätigt, dass das Tool \"die Fähigkeit, Booster-Packs zu erhalten, bewahrt\", da es sich auf die gleiche Weise anmeldet wie der offizielle Client.\n\nAuch das Belohnungssystem und das verbotene Verhalten stellen ein Mechanismus dar, der aus zwei Perspektiven betrachtet wird. Valve baute die Belohnung so, dass sie durch Zeit und nicht durch Fähigkeit erzeugt wird, und schrieb dann einen Passus, der die Erzeugung von Belohnungen durch etwas anderes als eine Person, die diese Zeit aufwendet, verbietet.\n\n05 — Die kommerzielle-Nutzung-Falle\nJeder Ausgang aus einer gefarmten Karte ist ein Ausgang, den die Lizenz verbietet – und Valve erhebt eine Gebühr an der Tür.\n\nDies ist der Teil, der nicht durch \"verantwortliches\" Farmen gelöst werden kann. Die Lizenz ist für persönliche, nicht-kommerzielle Nutzung bestimmt, und eine Karte wird erst dann wertvoll für das Farmen, wenn sie nicht mehr persönlich ist.\n\n§ 2.A — die Lizenz\n\n\"Die Ventil erteilt hiermit und Sie akzeptieren, eine nicht-exklusive Lizenz und das Recht, den Inhalt und die Dienstleistungen für Ihre persönliche, nicht-kommerzielle Nutzung zu verwenden (es sei denn, der kommerzielle Gebrauch ist hier oder in den anwendbaren Abonnementbedingungen ausdrücklich erlaubt).\"\n\n§ 2.G — die Einschränkung\n\n\"Sie sind nicht berechtigt: … (iii) den Inhalt und die Dienstleistungen oder deren Teile zu kommerziellen Zwecken auszubeuten, es sei denn, dies ist ausdrücklich in diesem Vertrag (einschließlich aller Abonnementbedingungen oder Nutzungsregeln) gestattet.\"\n\n§ 3.D — die Gebühr\n\n\"Valve ist berechtigt, eine Gebühr für Transaktionen in einem Abonnementmarkt zu erheben. Alle Gebühren werden Ihnen vor Abschluss der Transaktion mitgeteilt.\"\n\nLesen Sie die drei zusammen und die Position schließt sich.\n\nEine Karte, die behalten wird, ist für eine Farm wertlos. Eine Karte, die verkauft, gehandelt oder in Edelsteine zerkleinert wird, hat bereits Wert geschaffen – und Valve hat in seinem eigenen Durchsetzungsschreiben selbst gesagt, was es damit meint: Der Betreiber von 170 Bots wurde gesagt, dass das Konto \"illegal Sammelkarten auf Steam gesammelt hat, sowie damit zusammenhängende und nicht nur kommerzielle Aktivitäten.\" In diesem Fall gelangten die Karten auf den Markt. Die Verkäufe wurden abgewickelt. Die Gebühr wurde eingezogen. Der Bann kam danach.\n\nDie Gebühr an dieser Tür beträgt nicht 15 %. Auf einer gefarmten Karte erreicht sie zwei Drittel.\n\n§ 3.D sieht \"eine Gebühr\" vor. Auf den tatsächlich produzierten Karten einer Farm beträgt diese Gebühr in keiner Weise die beworbenen ~15 %. Der Community Market erhebt eine 5%-ige Steam-Transaktionsgebühr und eine 10%-ige Spielgebühr, jede mit einer Untergrenze von $0,01 (Valves eigener Community Market FAQ). Bei einer Karte, die für einen Cent gelistet ist, sind diese Untergrenzen daher der Preis: Der Käufer zahlt drei Cent, davon sind zwei Gebühren. Die Rundingrenze verwandelt die beworbene 15 % in eine effektive Abgabe, die bis zu 66,7% ansteigt, genau dort, wo der Kartenmarkt lebt – einige Cent pro Karte.\n\nEffektive Gebühr bei einem Verkauf auf dem Community-Markt, nach Verkaufspreis\n\n5% Dampf + 10% Spiel, jeder Betrag mindestens $0,01. Die schattierte Zone ist der Bereich, in dem Sammelkarten tatsächlich gehandelt werden – etwa $0,03–$0,05 pro Karte.\n\n0%\n10%\n20%\n30%\n40%\n50%\n60%\n70%\ncards\n$0.01\n$0.10\n$0.20\n$0.30\n$0.40\n$0.50\n66.7%\nVerkäufer möchte\tDampf 5% (min. 0,01 $)\tSpiel 10% (min. 0,01 $)\tKäufer zahlt\tKombinierte Gebühr\n$0.01\t$0.01\t$0.01\t$0.03\t66.7%\n$0.03\t$0.01\t$0.01\t$0.05\t40.0%\n$0.05\t$0.01\t$0.01\t$0.07\t28.6%\n$0.08\t$0.01\t$0.01\t$0.10\t20.0%\n$1.00\t$0.05\t$0.10\t$1.15\t13.0%\n\nDer 10-%-Spieleinsatz geht an die App, die die Karte ausgegeben hat; 5 % gehören Valve selbst, und bei eigenen Titeln und Basisinventargegenständen ist die gesamte Gebühr Valve. Auf jeden Fall verlässt das Geld den Farmer — der Verkauf einer dreizentstigen Karte bringt einen Cent ein und gibt zwei her. Das mal die Hunderttausende von Kartenverkäufen unter einem Cent, die eine Farm generiert, und \"die Gebühr, die Valve berechnen kann\" ist das Geschäftsmodell, nicht ein Fußnote. Quelle: Steam Community Market FAQ — Gebühren ↗ archiviert am 21. September 2026 ↗, gelesen am 22. September 2026; die Kurve ist arithmetisch bei diesen beiden veröffentlichten Gebühren und ihren $0,01-Untergrenzen.\n\nEs gibt keine Konfiguration des Tools, die dies umgeht. Es kann von einer Person auf einem Konto mit vollkommener Selbstbeherrschung ausgeführt werden — und im Moment, in dem diese Person eine einzige gefarmte Karte für Brieftaschengeld verkauft, trifft dieselbe Bestimmung in § 2.G auf sie, wie sie auf den Betreiber von zehntausend trifft. Valve hat daher eine Verletzung vorgesehen, die sie gegen effektiv jeden Kartenverkäufer auf ihrem eigenen Markt anwenden könnte, und hat es abgelehnt, sie gegen effektiv alle anzuwenden. Eine Regel, die in diesem Tempo durchgesetzt wird, ist keine Regel. Es ist eine Option. Die Frage, die dieses Beweisstück aufwirft, ist nicht, warum Kartenfärmer geduldet werden; es ist, warum dasselbe Recht gegen einen einzelnen Benutzer angewendet wird, der eine Karte verkauft, während die kommerzielle Kartenökonomie, die diese Karten ernährt — die Handelsdienste, die Level-Up-Bots, die Großhändler — offen weiterläuft, eine ihrer größten Gruppen wird von einem Valve-Mitarbeiter moderiert (§ 08). Die Verletzung ist gegen den kleinen Halter vorgesehen und für die Maschine aufgehoben.\n\n06 — Das Vollstreckungsprotokoll\nKeine Mitteilung, in Wellen und es reist sich entlang der Telefonnummer fort.\n\nDie Ventile haben die nicht-anzeigende Kraft in den Vertrag selbst eingefügt, eine Klausel nach der Automatisierungsklausel.\n\n\"Die Valve kann Ihr Konto oder eine bestimmte Abonnementkündigung aufgrund jeglicher illegalen Handlung oder Aktivität, die einen Betrug oder Automation darstellt oder die Steam Online-Verhaltensregeln verletzt, einschränken oder beenden. Sie erkennen an, dass die Valve nicht verpflichtet ist, Ihnen eine Kündigung vor der Beendigung Ihres Abonnements und/oder Kontos zu erteilen. \"\n\n— Steam Subscriber Agreement § 4.D ↗ archiviert unter 2026-09-24 ↗ · verified verbatim 2026-09-22\n\n1.000+ Bots · Handelsbann. „Es scheint, dass dieses Konto zur Verwaltung eines Bot-Account-Netzwerks verwendet wurde. Botting stellt eine Verletzung der Steam-Nutzervereinbarung dar.“\n\n170+ Bots · dauerhaft gesperrt, 2017 Winter Sale. „Dieses Konto wurde illegal zur Sammlung von Sammelkarten auf Steam sowie zu damit zusammenhängenden und nicht nur kommerziellen Aktivitäten verwendet. Das Konto wurde dauerhaft gesperrt, und der Steam-Support kann zu diesem Thema keine zusätzliche Unterstützung bieten.“\n\n120+ Bots · dauerhaft gesperrt. „Diese und andere Konten wurden zur Überflutung unserer Netzwerkinfrastruktur verwendet, was eine Verletzung des Steam-Online-Verhaltens darstellt.“\n\n— Steam Support messages reproduced in the ArchiSteamFarm FAQ, section \"Did anybody get banned for it?\". Source ↗ · verified verbatim 2026-09-22\nFall 4 — Juni 2025, VAC-Banns für stillgelegte CS2\n\nEin späteres Ereignis als die drei oben genannten ist im eigenen Tracker des Projekts dokumentiert: Konten, die nur durch das Tool Counter-Strike 2 gespielt haben, erhielten VAC-Banns — der Art der Anti-Cheat-Maßnahmen, nicht der administrativen Art. Die Position des Betreibers ist, dass das Leerlaufen nicht zu einem solchen führen kann, da es \"nur dazu dient, Steam zu informieren, dass wir das angegebene Spiel spielen.\" Die Ursache ist umstritten. Dass die Konten gesperrt wurden, ist nicht.\n\n— ArchiSteamFarm-Diskussion #3440, geöffnet am 26. Juni 2025 ↗ · gelesen am 22. September 2026\n\nWie ein Hauptkonto stirbt\n\nIn demselben Thread beschreibt ein Projektmitarbeiter die Propagationsregel: Konten können \"kettengerecht\" gesperrt werden, wenn sie denselben Telefonnummer — \"es kann sich dabei nur um einen VAC-Bann handeln, der auf 'saubere' Konten übertragen wird, die mit dem gesperrten Konto verbunden sind.\"\n\nSteam Guard erfordert eine Telefonnummer. Farmen werden auf der Telefonnummer des Betreibers aufgebaut. Daher endet die Durchsetzung nicht bei den Wegwerf-Accounts: Sie erstreckt sich bis zum gemeinsamen Identifizierer zum Konto, das die Bibliothek, die Freundeliste und das Inventar hält. Das ist das Mechanismus, den ein Projektzusammenarbeiter beschreibt, wie eine einzelne Aktion das Hauptkonto eines Betreibers zusammen mit der Farm löscht — und das ist der Grund, warum der Verlust in einer Durchsetzungswelle nicht in $5 Konten gemessen wird. (Beschrieben von einem Projektzusammenarbeiter in der ASF GitHub-Diskussion #3440; es gibt keine offizielle Valve-Bestätigung oder formelle Präzedenz auf dem Zettel.)\n\nDer gleiche Abschnitt, fünf Jahre auseinander, von drei verschiedenen Agenten\n\nDer Satz, der das Farmen als Verstoß klassifiziert — der kommerzielle Gebrauch einer persönlichen, nicht-kommerziellen Lizenz — ist nicht nur für Farmen reserviert. Es ist der ständige Grund, den Steam angibt, wenn er ein Konto aufgrund von Handel schließt, und der Grund tritt als Vorlage auf. Nachstehend sind drei Fälle, veröffentlicht von den Personen, die sie fünf Jahre auseinander von drei verschiedenen benannten Agenten erhalten haben.\n\nMessage from Steam Support on Sep 29 @ 7:56pm\n\n\"Das für Sie geschriebene Konto wurde aufgrund der Verletzung der Bedingungen des Steam-Abonnentenvertrags gesperrt. Das Konto wurde aufgrund von Handelsaktivitäten, Gemeinschaftsberichten und anderen Faktoren als für kommerzielle Zwecke verwendet identifiziert.\n\nDieser Schließmechanismus ist dauerhaft und der Steam-Support kann Ihnen hierbei keine weitere Hilfe leisten.\n\nDa wir alle verfügbaren Informationen bereitgestellt haben, schließe ich diesen Hilfsantrag. Bitte beachten Sie, dass Sie keine weiteren Antworten zu diesem Thema erhalten werden.\n\nGrüße,\nHal\"\n\nThis help request has been closed.\n29 September 2020. Posted by the recipient with the comment \"RIP Trading.\" — @gergelyszabo94 ↗\nMensagem do Suporte Steam em 12 de jul. às 22:41\n\n\"Das für Sie geschriebene Konto wurde aufgrund der Verletzung der Bedingungen des Steam-Abonnentenvertrags gesperrt. Das Konto wurde aufgrund von Handelsaktivitäten, Gemeinschaftsberichten und anderen Faktoren als für kommerzielle Zwecke verwendet identifiziert.\n\nDieser Schließmechanismus ist dauerhaft und der Steam-Support kann Ihnen hierbei keine weitere Hilfe leisten.\n\nDa wir alle verfügbaren Informationen bereitgestellt haben, schließe ich diesen Hilfsantrag. Bitte beachten Sie, dass zukünftige Hilfsanträge, die sich auf das Sperrung des Kontos beziehen, ohne Antwort geschlossen werden können.\n\nDampf-Support\nVido\"\n\nEste pedido de ajuda foi encerrado.\n12 July 2024, Portuguese interface. The recipient is a professional CS2 player: \"already contacted steam support but only getting auto-responses… can't play faceit and also can't play professional matches.\" — @prcs25 ↗ archived 2024-07-15 ↗\nQuoted by the recipient, r/steamsupport\n\nHallo, das für Sie verwendete Konto wurde aufgrund der Verletzung der Bedingungen des Steam-Abonnentenvertrags gesperrt. Das Konto wurde aufgrund von Handelsaktivitäten, Gemeinschaftsberichten und anderen Faktoren als für kommerzielle Zwecke verwendet identifiziert.\n\nDieser Schließmechanismus ist dauerhaft und der Steam-Support kann Ihnen hierbei keine weitere Hilfe leisten.\n\nDa wir alle verfügbaren Informationen bereitgestellt haben, schließe ich diesen Hilfsantrag. Bitte beachten Sie, dass zukünftige Hilfsanträge, die sich auf das Sperrung des Kontos beziehen, ohne Antwort geschlossen werden können.\n\nStromunterstützung\nSally\"\n\nReceived three times, on three separate requests.\n29 March 2025. The writer was not appealing the lock — their account had been stolen along with their email and they were asking for access: \"I'm not asking about the ban and I'm not disputing it I just want access to my steam account… Valve have given me this exact answer copy and pasted on every request and close the request.\" — r/steamsupport ↗, held in this investigation's own complaint corpus\n\nWort für Wort, Komma für Komma, über fünfundsünfzig Monate hinweg, drei Agenten und zwei Schnittstellen-Sprachen. Die einzige Änderung im Text ist die Festigung der letzten Zeile zwischen 2020 und 2024, von \"Sie werden keine weiteren Antworten erhalten\" bis zu \"zukünftige Hilfsanfragen… können ohne Antwort geschlossen werden.\" Egal welchen Prozess diese Entscheidungen hervorbrachten, das Schreiben ist keine Aufzeichnung davon. Die genannten Gründe sind \"Handel, Gemeinschaftsberichte und andere Faktoren\" — eine Kategorie, ein Bericht von unbekannter Herkunft und ein unbenannter Rest.\n\nFünf weitere Fälle, die auf die gleiche Weise gesammelt wurden. Die ersten drei gehören zur gleichen Kategorie und haben das gleiche Ergebnis; die letzten beiden werden von derselben Abteilung bearbeitet, die eine andere Regel in denselben Worten anwendet:\n\nDatum\tWas das Konto tat\tWas geschah?\tQuelltext\n04.12.2021\tEinkaufen und Verkaufen auf Buff — \"Ich habe nichts anderes getan als einige Einkäufe und Verkäufe auf Buff, auch bekannt als P2P-Handel\"\tCommunity-Bann: Kein Markt, kein Handel, teures Inventar eingefroren\tr/csgomarketforum ↗ archiviert am 27. März 2025 ↗\n06.12.2021\tEinseitige P2P-Geschäfte über Buff und Bitskins für Ausrüstungsaustausch und -aufrüstungen\tDauerhafter Sperrschlüssel für kommerzielle Nutzung plus Community-Sperre: \"steckt in einem pseudo unsichtbaren Modus… Mein Profil ist ebenfalls auf privat gesperrt\"\tr/GlobalOffensiveTrade ↗Reddit-Beitrag ↗ archiviert 2021-12-06 ↗Archivierte Quelle ↗\n20.12.2024\tKonto seit 2017 geführt, Tausende von Stunden; Handel auf Gemeinschafts-Marktplätzen für thematische Ausrüstungen und Aufwertungen\tDauerhaftes Sperren mit Community-Sperre, ohne vorherige Warnung oder Verwarnung; Unterstützung \"sagt, dass ihre Entscheidung endgültig ist\", Antworten werden automatisiert\tr/csgomarketforum ↗ archiviert am 27. Juni 2025 ↗\n23.12.2024\tRückkehrender Benutzer fügt nach einem Jahr der Abwesenheit Wallet-Guthaben hinzu, über einen VPN, der \"nur für die allgemeine Internet-Sicherheit\" verwendet wird.\tDauerhafter Community-Bann mit keinem angegebenen Grund: \"der Bann ist dauerhaft und sie können keine weiteren Informationen bereitstellen und es kann sein, dass weitere Tickets ohne Antwort geschlossen werden.\" 196 Likes, 340 Antworten\tr/steamsupport ↗\n04.08.2026\tJahre an Einkäufen aus dem Iran; der Verfasser behauptet, er habe niemals gepostet, niemals den Markt genutzt, niemals die Foren benutzt.\tCommunity-Zugriff gesperrt bis 2038 aufgrund von \"sanktionierten Regionen\"; Ticket durch einen Agenten namens Azul geschlossen. Eine Rückerstattung desselben Kontos von derselben iranischen IP wurde ein Jahr zuvor genehmigt. Die Bibliothek und das Geld bleiben bei Valve.\tr/pcgaming ↗\n\nDie letzte Zeile stellt eine andere Regel dar als die übrigen — es geht um die Einhaltung von Sanktionen, nicht um kommerzielle Nutzung — und sie ist enthalten, da die Form der Antwort identisch ist: eine Kategorie, kein Beweis, keine Berufung, ein geschlossenes Ticket. Sie erhebt auch eine Frage, die die anderen nicht aufwerfen. Wenn das Konto unrechtmäßig zu dienen war, waren die Jahre der Zahlungen unrechtmäßig anzunehmen. Eine dieser beiden Positionen muss falsch sein, und nur eine von ihnen hat dem Kunden etwas gekostet.\n\nAlle acht wurden am 22. September 2026 gelesen – die Threads aus dem Jahr 2021 und Dezember 2024 durch Internet Archive-Snapshots und der Rest über eine öffentliche Reddit-Oberfläche, da Reddit direkte Anfragen des Sammelrechners abgelehnt hat. Die beiden Briefe aus dem Jahr 2020 und 2024 sind aus den in den Originalbeiträgen beigefügten Screenshots transkribiert, die noch immer online sind. Keines dieser Konten wird von dieser Untersuchung als unschuldig oder schuldig von irgendetwas beschuldigt – das ist genau der Punkt. Kein Leser und kein Regulator kann aus dem Brief herausbekommen.\n\nHinweis zu den Quellen — Verluste auf Betreiberebene\n\nDie durch diese Untersuchungsbericht berichteten Betreiber haben in Einzelfallaktionen Verluste in der Größenordnung von fünf bis zehn Tausend Konten jedes erlitten, wobei Hauptkonten zusammen mit der Farm erfasst wurden. Diese Erhebung ist hier als erste Partei Berichtung aufgeführt, nicht als Feststellung. Es gibt keine veröffentlichte Stichprobengröße, kein festgelegtes Sammeldatum, keine pro-Konto-Verifizierung und keine andere Zahl auf dieser Seite hängt davon ab; die beiden Zeilen in Abschnitt 02, die darauf basieren, sind entsprechend gekennzeichnet.\n\nEs wird nicht einfach weggelassen, sondern aus zwei Gründen dargestellt. Das oben beschriebene Ketten-Bann-Mechanismus ist die dokumentierte Erklärung genau für dieses Muster. Und ein Regulator kann von Valve die eine Aufzeichnung erzwingen, die es klären würde: wie viele Konten wegen Automatisierung Maßnahmen ergriffen wurden, in welchen Wellen und wie viel jeder dieser Konten im Laden ausgegeben hatte, bevor er geschlossen wurde. Bis diese Aufzeichnung existiert, bleibt die Zahl dort, wo sie ist – berichtet, zugeordnet und unbestritten.\n\n07 — Die Asymmetrie\nBeide Seiten desselben Schreibtisches\n\nSetzen Sie diesen Beweisstandard gegen den abgestellten von Valve für seine eigene Supportoperation. Die rechte Spalte ist das eigene Vorfallsregister dieses Dossiers, wiedergegeben mit den Schranken, die es dort trägt.\n\nEin Kunde, für den Handel\n\nAcht dokumentierte Fälle, 2020–2026\n\nVerhalten\nVerkauf oder Kauf von Gegenständen auf Marktplätzen von Drittanbietern; in einem Fall überhaupt kein Verhalten — das Konto war gestohlen worden.\nVorgelegte Beweise\nKeine. \"Basierend auf Handel, Community-Meldungen und anderen Faktoren.\"\nBenachrichtigung\nKeine. Valve behielt sich dies in § 4.D vor: \"Valve ist nicht verpflichtet, Sie vor der Kündigung zu benachrichtigen.\"\nWiderspruch\n\"Diese Sperre ist dauerhaft und der Steam Support kann Ihnen hierbei nicht weiterhelfen.\"\nTicket\nGeschlossen bei der ersten Antwort. Weitere Anfragen \"können ohne Antwort geschlossen werden.\"\nReichweite\nProfil, Freundesliste, Chat, Markt, Inventar und jeder mit echtem Geld gekaufte Gegenstand.\nDauer\nDauerhaft.\nEine automatisierte Bot-Flotte, für das Volumen\n\n694.673 vollständige Sets im öffentlichen Bestand über 91 Bots\n\nVerhalten\nAusführung automatisierter Headless-Skripte über Tausende von Konten gleichzeitig, um Karten zu idlen, Abzeichen massenhaft herzustellen und Sets im industriellen Maßstab zu handeln.\nVorgelegte Beweise\nÖffentlich zugängliche Bot-Verzeichnisse (steam.supply, SteamLvlUp) und öffentliche Gruppen mit Millionen von Mitgliedern.\nBenachrichtigung\nNull Eingriffe. 88,97 % tragen keinerlei Bann; 99,8 % der verbleibenden Sperren sind rein kosmetisch.\nWiderspruch\nNicht erforderlich. Flotten operieren kontinuierlich über mehrjährige Lebenszyklen hinweg ohne Unterbrechung.\nTicket\n—\nReichweite\nUneingeschränkter Inventaraustausch, Abzeichen-Leveling und Marktliquidität.\nVorteil für Valve\n26,8 Mio. $+ an Mindestausgaben im Store ($5,00 Einstiegsschwelle pro Konto) plus 15 % Transaktionsgebühren auf dem Community-Markt.\nDie Frage, die dies aufwirft, gesagt einfach.\n\nEin einzelner Kunde, der manuell Sammelkarten oder Artikel handelt, sieht sich einem dauerhaften, nicht anfechtbaren Bann gemäß § 4.C (Automatisierung) oder § 2.G (kommerzielle Nutzung) ausgesetzt. Ein automatisiertes Farming-Flotten, das kopflose Bots über Tausende von Konten hinweg betreibt, operiert offenbar mit einer 88,97-%-igen unberührten Quote. Valve ist der Empfänger beider.\n\nDie Asymmetrie ist wirtschaftlicher Natur: Einzige Händler ziehen Wert aus der Plattform heraus, während automatisierte Kartenflotten Millionen in die Mindestausgabe-Schwelle von Valve's Store (5,00 USD pro Konto) pumpen und Transaktionsgebühren bei jeder Wiederverkauftransaktion erhöhen. Die Durchsetzung folgt nicht dem schriftlichen Regelwerk; sie folgt dem Einkommensmodell.\n\n08 – Governance\nWer moderiert die Kartenökonomie?\n\nDieses Dossier zeigt wiederholt, dass die dritte Schicht um Steam von innen aus Steam besetzt ist, und dies gilt auch für die Kartenökonomie, und es endet an einem spezifischen Ort: Kein unabhängiger Akteur kann zählen, was Valve tatsächlich durchsetzt, da die Partei, die das zählen kann, innerhalb dieser Schicht sitzt. Jeder nachfolgende Fakt wurde am 22. September 2026 von den eigenen öffentlichen Gruppen- und Profilseiten von Valve gelesen und kann von jedem in einem Browser nachvollzogen werden.\n\nEin Valve-Mitarbeiter moderiert die größte Sammelkarten-Handelsgruppe Valve-Mitarbeiter.\n\nCardTrades ↗ beschreibt sich selbst in seinem eigenen Header als die \"offizielle Steam Card Exchange-Gruppe\" und zählt 97.114 Mitglieder. Ihre aufgelisteten Moderatoren — die Konten, die die Kontrolle über diese Gruppe ausüben — sind Mickmane, SgtFopper und afarnsworth ↗.\n\nDieser letzte Profil ist durch die eigene Seitenauszeichnung von Valve als Valve-Mitarbeiter gekennzeichnet — die Seite trägt class=\"profile_header_valve_employee\" — gibt seinen Standort als Bellevue, Washington an und gehört zu den Gruppen Valve, Steam und Steam Trading Cards Group. SteamID64 76561197960434622, Mitglied seit dem 12. September 2003.\n\nDie Beobachtung ist strukturell, nicht persönlich, und sie ist keine Automatisierungspunkte — ein Moderator einer Sammelkarten-Gruppe führt keinen Bot, und nichts hier deutet darauf hin. Der Punkt ist der Satz in Abschnitt 07. Steam Card Exchange ist ein Drittanbieter- kommerzieller Karten-Service; der Handel mit Sammelkarten über Drittanbieter-Dienste ist genau das Verhalten, für das Valve gewöhnliche Konten dauerhaft sperren, unter \"zur kommerziellen Nutzung basierend auf dem Handel, Gemeinschaftsberichten und anderen Faktoren.\" Ein Valve-Mitarbeiter hat eine aufgelistete Moderatorrolle in der offiziellen Community-Gruppe dieses Dienstes, die neunundneunzigtausend Menschen umfasst.\n\nKeine Anschuldigung eines unrechtmäßigen Verhaltens wird hier gegen jedermann erhoben, und keine Schlussfolgerung wird gezogen über die Inhalte dieser Rolle. Das Auffällige ist das Ergebnis: Wenn ein gewöhnliches Konto eine Drittanbieterkarte oder ein Drittanbieter-Skin-Service berührt, ist die Antwort ein geschlossenes Ticket und eine dauerhafte Sperrung ohne dargestellte Beweise; wenn es sich um diesen Service handelt, ist ein Valve-Mitarbeiter in der Moderatorliste aufgeführt und die Vereinbarung ist auf einer Seite sichtbar, die Valve selbst veröffentlicht. Was gefragt wird, ist das gleiche wie überall sonst in diesem Dossier: Erstellen Sie die schriftliche Genehmigung, wenn eine vorliegt — und wenn keine erforderlich ist, teilen Sie dies schriftlich mit, da acht Personen in Abschnitt 06 das Gegenteil gesagt haben.\n\nDie Bannliste-Ebene und wer sie verwaltet Freiwilliger ModeratorDrittanbieter-Dienst\n\nSteambans.coms Gruppe (archiviert) ↗ (live ↗ archiviert 2025-12-03 ↗) führt ihre Abstammung in ihrer erhaltenen Gruppenbeschreibung auf: \"Die offizielle Steambans.com Steam Community Group. SteamBans.com ist ein brandneuer Service, der auf einem alten Konzept basiert. Globale Ban-Listen haben Jahre lang auf dem alten WONID-Programm von VALVe aktiv bestanden. Als der Wechsel zu STEAMID kam, war es für uns selbstverständlich, einen Service speziell für dieses neue System zu entwickeln. Aber wir wollten auch mehr. *. Archivseite für Steambans, die 2013 geschlossen wurde.\" Aufgeführt sind als Administratoren devicenull und killahinstinct_ ↗.\n\nDieser Administrator-Account ist kein Valve-Mitarbeiter — er trägt kein Mitarbeiter-Flagge. Es ist ein Freiwilliger mit außergewöhnlich tiefem Engagement: ein Mitglied der Community Moderatoren (414 Mitglieder, beschrieben als eine Gruppe \"von Steam's Community Moderatoren erstellt\"), der Wiki Koordinatoren, der Steam Community Market, und der Valve-Programm- und Vorveröffentlichungsgruppen einschließlich Valve Pipeline, Steam Client Beta, Mobile Auth Beta, New Steam Community Beta, Steam Labs, Steamworks und Report ScamURLs. SteamID64 76561197960794555.\n\nAuch innerhalb dieses Kreises und zeigt Steambans direkt in seinem öffentlichen Gruppenverzeichnis: msart ↗ (Gruppenverzeichnis ↗), SteamID64 76561197977933359, deren Profil in eigenen Worten angibt \"Ich betriebne steamid.uk und viele andere Steam- und nicht-Steam-bezogene Seiten\", und der einen verbundenen Netzwerk von sechzehn Gruppen führt — SteamIDcouk (Hauptgruppe \"Sid website\"), SidAdmins, SidBans, steamideu, Steam3ID, s-id und SArchive darunter.\n\nsteamid.uk nennt sich selbst. In seinen FAQs: \"Wer hat SteamID erstellt? Die SteamID-Website, die Netzwerkinfrastruktur und die Sicherheitssysteme werden alle von 76561197977933359 verwaltet.\" Zwei Antworten weiter unten wird angegeben, woher die Daten stammen: \"SteamID nutzt hauptsächlich die Steam Web API zur Datensammlung.\" Auf derselben Seite wird von mehreren dedizierten Servern auf verschiedenen Hosts, externen Entwicklungs-, Speicher- und Textsuchservern sowie einer separaten Backup-Anlage gesprochen.\n\nVerifiziert durch erhaltene Internet Archive-Aufzeichnungen: der Schnappschuss der Steambans-Gruppe vom 3. Dezember 2025 ↗, der Profil-Schnappschuss des Betreibers vom 14. September 2024 ↗, sowie der steamid.uk FAQ-Schnappschuss vom 1. April 2026 ↗, wobei die Daten direkt am 22. September 2026 gelesen wurden.\n\nWas dies ergibt und was es nicht ergibt\n\nBannlisten, SteamID-Resolution und Sammelkartenhandel sind die drei Dienstleistungen, die darüber entscheiden, wer vertrauenswürdig ist, wer identifizierbar und was ein Gegenstand wert ist. Keine dieser drei Dienstleistungen wird von Valve betrieben. Bei jedem dieser Dienstleistungen stammen die Personen, die die Kontrolle innehaben, aus dem Umfeld von Valve: ein markierter Valve-Mitarbeiter auf der Moderatorliste der offiziellen Gruppe des Sammelkarten-Dienstes; ein langjähriger Valve-Community-Moderator mit Zugang zum Vorveröffentlichungsprogramm, der die Bannlisten-Gruppe verwaltet; ein von einem privaten Einzelpersonen betriebener ID-Resolution-Dienst, der in derselben Gruppe sitzt. Drei Dienstleistungen, drei Kontrollflächen, drei Personen, denen Valve bereits eine Stellung gegeben hat.\n\nDie Mitgliedschaft in einer Gruppe ist keine Beschäftigung, und dies stellt keine Anklage dar. Es ist eine Governance-Tatsache, und dies ist der Grund, warum die allgemeine Verteidigung — denn das sind Dritte, die wir nicht kontrollieren können — überprüft werden muss, anstatt akzeptiert zu werden. Die Personen am Steuer sind nicht Unbekannte für Valve. Valve ist in der Lage zu sagen, was, wenn überhaupt, es von ihnen verlangt hat; niemand außerhalb kann dies herausfinden.\n\nNiemand zählt. Dies ist das Ergebnis.\n\nDer Steam-ID-Bereich ist ein kontinuierlicher Integer-Bereich. Ihn zu durchlaufen und zu berichten, wie viele Konten gesperrt sind, wie viele eingeschränkt sind und wie viel Inventar hinter einem Handelsbann liegt, ist kein Forschungsprogramm — es ist ein Loop und ein API-Schlüssel. Valve verteilt diesen Schlüssel selbst, unter steamcommunity.com/dev/apikey. Und dennoch veröffentlicht keine unabhängige Partei diese Zählung. Nicht ein Regulator, nicht ein Journalist, nicht ein Akademiker, nicht ein Verbraucherschutzverband. Die einzigen öffentlich verfügbaren Zahlen über den Umfang der Durchsetzung auf Steam sind diejenigen, die Valve selbst erwähnt.\n\nDie Fähigkeit fehlt nicht. Sie wird gehalten. Der Service, der den ID-Raum skalierbar auflöst und indexiert – steamid.uk – teilt in seinem eigenen FAQ mit, dass er \"primär die Steam Web API für die Datensammlung nutzt\" und sie auf mehreren dedizierten Servern, externen Speicheranlagen, Textsuchmaschinen und einer separaten Backup-Anlage ausführt. Er wird von einem privaten Einzelpersonen betrieben. Sein Bann-Liste-Schwester-Gruppe wird gemeinsam von einem langjährigen Valve-Community-Moderator verwaltet, der Zugang zu Valves Vorab-Programmen hat. Derjenige, der in der Lage ist, die Anzahl zu veröffentlichen, sitzt im Umfeld von Valve und veröffentlicht sie nicht.\n\nDies ist die gleiche Form, die das Dossier überall findet. Jeder Dienst, der etwas Tragendes über die Steam-Wirtschaft entscheidet — wer vertrauenswürdig ist, wer identifizierbar, was ein Artikel wert ist, wer gesperrt ist — ist nominell ein Drittanbieter und praktisch benachbart zu Valve. Der Steam Card Exchange ist keine Ausnahme von diesem Muster; es ist eine weitere Instanz davon. Die Verteidigung, dass es sich dabei um unabhängige Betreiber handelt, steht Valve genau deshalb zur Verfügung, weil niemand jemals in der Lage war, es an einer Zahl zu testen.\n\nDie 10.88M-Kontenzählung: 88,97 % unberührt\n\nDie Installationsbasis von ArchiSteamFarm wurde über den GetPlayerBans-Endpunkt von Valve überprüft (10.880.610 Konten, 55 Minuten). Allein der nicht-eingeschränkte Teil repräsentiert 26,8 Mio. USD an Mindestausgaben im Store ($5,00-Eintrittsschwelle). 9.680.599 Konten (88,97%) tragen keine Art von Ban, und 99,8% des Restes tragen nur kosmetische Community-Bans, die den automatisierten Handel aktiv lassen.\n\n5,360,499Nicht-eingeschränkte ASF-Mitglieder (angezeigte Anzahl bei Steam)\n10,880,610Gesamtzahl der durchsuchten API-Einträge (eingeschränkt + vollwertig)\n9,680,599Nie gesperrt (88,97%)\n1,200,011Jeglicher Steam-Bann (11,0%) — 99,8% kosmetischer\n55 minUm die gesamte Bevölkerung zu zählen, stellt sich ein Schlüsselproblem dar.\nForensische Beweise & Vertiefte Zählung\n\nDie detaillierte demografische Aufschlüsselung — einschließlich der Verteilungsdiagramme der Bannarten, des Alters der Konten bei der Durchsetzung, der Cluster der Gründungsjahre (2020–2026) und der geografischen Selbsteinschätzung — wird im dedizierten Zählungsdossier veröffentlicht.\n\nOpen the Full 10.88M Ban Census (Exhibit VI) →Section 4 — The Asset ID Blackout →\n\nSo die Frage zu stellen, die nur Valve beantworten kann: welcher Identifikator oder Fähigkeit wurde zurückgezogen, an welchem Datum, auf wessen Entscheidung und welche messbaren Auswirkungen hatte es auf die Betreiber, auf die es abzielte — im Vergleich zu seiner Auswirkung auf alle Außenstehenden, die versuchten, zu zählen. Eine Änderung, die die unabhängige Überprüfung beendet, wird nicht neutral, weil sie als Sicherheitsmaßnahme angekündigt wurde. Dies ist der Grund, warum die Zählung im Block darüber nicht existiert.\n\n09 — Methodik und Grenzen\nWas gelesen wurde und was nicht beansprucht wird\n\nJeder Zitat auf dieser Seite wurde aus der Live-Quelle vom 22. September 2026 entnommen und wortwörtlich wiedergegeben. Nichts hier wurde aus einem Scraping, einem Marktplatz-Zertifikat oder einem privaten Datensatz entnommen.\n\nDie vier Datensätze und die darauf durchgeführte Arithmetik\n\nJeder ist ein einzelner öffentlicher Antrag, der von einem Terminal aus wiedergegeben werden kann. Kein Konto wurde verwendet, kein Marktplatz wurde angemeldet, und kein Endpunkt, der eine Anmeldeinformation erfordert, wurde aufgerufen.\n\nDatenmenge\tWoher es kam\tAus ihm wurde berechnet.\nKarten-Zählung\n13.876 Spiele\tDie veröffentlichte Abzeichenpreissliste von Steam Card Exchange, dasselbe Feed, der ihre öffentliche Preisseite generiert ↗ archiviert am 04.08.2026 ↗\tSpiele, die Karten ausgeben, Karten pro Satz, verschiedene Kartentypen und der Marktpreis jedes fertigen Satzes. Medianwerte und das Gesamtbetrag von $23,586,57 sind die arithmetischen Ergebnisse dieser Untersuchung.\nSpielpreise\n13.713 gelöst\tVentils eigener öffentlicher Store-Endpunkt, store.steampowered.com/api/appdetails, cc=us, nur das Preisfeld, in Batches\tMittlere und Verteilung des Listenpreises eines Sammelkarten-Spiels; die Anzahl der Spiele, deren abgeschlossenes Set den Spiel selbst überschreitet.\nBot-Bestand\n91 Bots, 694.673 Sets\tDie öffentliche Karte-Bot-Verzeichnis bei steam.supply/CardBots ↗, wie dargestellt, ohne Anmeldung\tGesamtbestände, das Mindestkartenkontingent, die Mindestausgabe-Schwelle für die Drop-Genehmigung und die pro-Bot-Untergrenze für verschiedene Konten.\nKreuzkontrollen\n21 geteilte Bots\tsteamlvlup.net/cardbots ↗ archiviert am 10. Februar 2026 ↗, ein unabhängiges Verzeichnis derselben Bots\tDie Überprüfung betrifft nur. Auf beiden Listen der 21 Bots stimmt die aggregierte Bestandsmenge zu 0,03%; die größte Einzelfehlerquote eines Bots beträgt 1,36%, was mit zwei Crawl-Throughs des Live-Inventars, die Minuten voneinander entfernt durchgeführt wurden, übereinstimmt.\n\nZuordnung, wie es der zweite Verzeichnis erfordert: Daten bereitgestellt durch SteamLvlUp, lizenziert unter CC BY 4.0 archiviert am 23. September 2026 ↗; hier nur als unabhängige Überprüfung der Bestandszahlen eines Dritten verwendet und in dem Sinne verändert, dass die Zeilen pro Bot aggregiert und verglichen wurden, anstatt reproduziert. Steam Card Exchange und steam.supply werden oben durch Link erwähnt. Spielpreise sind Valve's eigene. Karten, Spiele und Setnamen sowie Bilder sind von Valve oder den Verlagen, reproduziert unter keiner Behauptung noch Lizenz, als Tatsachen über einen Markt.\n\nZwei geplante Messungen wurden nicht durchgeführt und sind nicht ersetzt worden. Die eigenen Community-Markt-Endpunkte von Steam — Preisübersicht, Suchen/Anzeigen, Preisgeschichte — liefern dem Sammelhost nichts zurück, und die Diskussionsseiten der Steam-Community geben HTTP 403 zurück, sodass keine Figur auf dieser Seite aus Live-Marktdaten abgeleitet wurde. Der Verkaufsvolumen-Method, die die Kartenabwürfe bei der täglichen Neustellung zählen würde, bedarf einer angemeldeten Steam-Sitzung; das Manifest dieser Untersuchung besagt, dass keine Marktplatzanmeldeinformationen verwendet wurden, und diese Aussage wurde beibehalten. Der Bot-Vorratsuntergrenze ist das, was ohne diese gemessen werden kann.\n\nHauptquellen\n\nSteam-Nutzervereinbarung ↗ archiviert am 24. September 2026 ↗ — § 2.A, § 2.G, § 3.D, § 4.C, § 4.D.\nSteam-Support — Eingeschränkte Benutzerkonten ↗ — die Mindestausgabe-Schwelle von $5.00 und die Liste der eingeschränkten Funktionen.\nValve — Häufig gestellte Fragen zu Steam Trading Cards ↗ — Drop-Mechanik und die $9 Free-to-Play-Rate.\nArchiSteamFarm Häufig gestellte Fragen ↗ und Diskussion #3440 ↗.\nSteam-Community-Gruppen und Profilseiten, direkt gelesen, für Abschnitt 08.\nsteamid.uk Häufig gestellte Fragen, Internet Archive Schnappschuss vom 1. April 2026 ↗.\nAcht von den Empfängern veröffentlichte Steam-Support-Sperrengaben, 2020–2026, aufgelistet mit ihren Links im Abschnitt 06.\n\nWas wird nicht beansprucht\n\nKeine Einnahmezahl wird für Valve aus der Karten-Farmung geschätzt. Keine Anzahl aktiver Konten wird für jedes Werkzeug behauptet, und die 1,39 Millionen Drop-Genehmigungen sind nicht eine Zählung der von der Farm besitzenden Konten — siehe die Anmerkung im Abschnitt 02. Kein Einzelperson wird der Übertretung beschuldigt; wenn eine Person genannt wird, ist es durch ihren eigenen öffentlichen Steam-Namen, in ihrer eigenen öffentlichen Rolle, von einer Seite, die Valve veröffentlicht. Keines der acht gesperrten Konten im Abschnitt 06 wird als unschuldig oder schuldig behauptet; die Feststellung betrifft das Schreiben, nicht das Konto. Die figures der Betreiber-Verluste im Abschnitt 02 sind erste Partei-Berichte und sind als solche im Quellungsnotiz gekennzeichnet. Der Steam-Level-Kurve über 667 wird nicht modelliert.\n\nWarum das Werkzeug nicht das Subjekt ist\n\nArchiSteamFarm gibt an, dass es \"nicht durch Valve autorisiert ist\" und auf dieser Seite nicht wegen irgendetwas angeklagt wird. Es wird als Messinstrument verwendet, da es die einzige Partei in dieser Wirtschaft ist, die die Mechanik öffentlich und schriftlich dokumentiert. Valve könnte das gesamte Beweisstück in einem Absatz abschaffen: welche kommerzielle Automatisierung es autorisiert und die Aufzeichnungen pro Betreiber darüber, was es mit dem Rest getan hat.\n\nLesen Sie weiter: wie der Markt selbst bewertet wird → · die Preisstufe und die Listenobergrenze → · die Artikel, die Steam nicht führen wird →",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Eine Bot-Farm ist kein Leck in Valves Laden. Es ist ein Kunde."
          },
          {
            "level": 2,
            "id": null,
            "text": "Was eine Farm tatsächlich ist, Schritt für Schritt"
          },
          {
            "level": 4,
            "id": null,
            "text": "Einstieg"
          },
          {
            "level": 4,
            "id": null,
            "text": "Spiele kaufen"
          },
          {
            "level": 4,
            "id": null,
            "text": "Karten farmen"
          },
          {
            "level": 4,
            "id": null,
            "text": "Drops aufgebraucht"
          },
          {
            "level": 4,
            "id": null,
            "text": "Auszahlen"
          },
          {
            "level": 2,
            "id": null,
            "text": "Bevor eine Farm einen Cent verdient, hat sie bereits Valve bezahlt"
          },
          {
            "level": 3,
            "id": null,
            "text": "Wie groß das tatsächlich gekaufte Objekt ist"
          },
          {
            "level": 4,
            "id": null,
            "text": "Wie groß ein Set ist"
          },
          {
            "level": 4,
            "id": null,
            "text": "Was die Lizenz kostet"
          },
          {
            "level": 4,
            "id": null,
            "text": "Was das fertige Set einbringt"
          },
          {
            "level": 4,
            "id": null,
            "text": "Wo die 694.673 Sets liegen"
          },
          {
            "level": 4,
            "id": null,
            "text": "Was diese Untergrenze aussagt und was nicht"
          },
          {
            "level": 3,
            "id": null,
            "text": "Und die Landwirtschaft bezahlt sich bei den Preisen von Valve nicht selbst aus."
          },
          {
            "level": 3,
            "id": null,
            "text": "Was die Farm tatsächlich unterstützt"
          },
          {
            "level": 3,
            "id": null,
            "text": "Und der eigentliche Auszahlungsprozess ist ein Wertverlust, den Valve zweimal besteuert."
          },
          {
            "level": 3,
            "id": null,
            "text": "Dies ist kein Moment. Es handelt sich um eine Branche mit einem mehrjährigen Rückgrat."
          },
          {
            "level": 4,
            "id": null,
            "text": "Vollständige Kartensets im öffentlichen Bot-Verzeichnis, nach Steam-Sale"
          },
          {
            "level": 3,
            "id": null,
            "text": "Wie die Abzeichen-Rangliste eines Verkaufs von oben aussieht"
          },
          {
            "level": 3,
            "id": null,
            "text": "Und die gleiche Flotte ist dort, wenn kein Verkauf läuft."
          },
          {
            "level": 4,
            "id": null,
            "text": "Das ruhende Verzeichnis, Bot für Bot"
          },
          {
            "level": 2,
            "id": null,
            "text": "Das andere Produkt ist die Nummer neben Ihrem Namen"
          },
          {
            "level": 4,
            "id": null,
            "text": "Verbrauchte vollständige Sets, Level 1 bis 1.000"
          },
          {
            "level": 4,
            "id": null,
            "text": "Wie die Kurve überprüft wurde, da Valve sie nicht veröffentlicht"
          },
          {
            "level": 2,
            "id": null,
            "text": "Der Satz beschreibt die Farming-Praxis nicht vage, sondern listet sie auf."
          },
          {
            "level": 3,
            "id": null,
            "text": "Spielzeit"
          },
          {
            "level": 3,
            "id": null,
            "text": "\"ohne echten Benutzerinput\""
          },
          {
            "level": 2,
            "id": null,
            "text": "Jeder Ausgang aus einer gefarmten Karte ist ein Ausgang, den die Lizenz verbietet – und Valve erhebt eine Gebühr an der Tür."
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 2.A — die Lizenz"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 2.G — die Einschränkung"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 3.D — die Gebühr"
          },
          {
            "level": 3,
            "id": null,
            "text": "Lesen Sie die drei zusammen und die Position schließt sich."
          },
          {
            "level": 3,
            "id": "fee-ladder",
            "text": "Die Gebühr an dieser Tür beträgt nicht 15 %. Auf einer gefarmten Karte erreicht sie zwei Drittel."
          },
          {
            "level": 4,
            "id": null,
            "text": "Effektive Gebühr bei einem Verkauf auf dem Community-Markt, nach Verkaufspreis"
          },
          {
            "level": 2,
            "id": null,
            "text": "Keine Mitteilung, in Wellen und es reist sich entlang der Telefonnummer fort."
          },
          {
            "level": 3,
            "id": null,
            "text": "Fall 4 — Juni 2025, VAC-Banns für stillgelegte CS2"
          },
          {
            "level": 3,
            "id": null,
            "text": "Wie ein Hauptkonto stirbt"
          },
          {
            "level": 3,
            "id": null,
            "text": "Der gleiche Abschnitt, fünf Jahre auseinander, von drei verschiedenen Agenten"
          },
          {
            "level": 4,
            "id": null,
            "text": "Hinweis zu den Quellen — Verluste auf Betreiberebene"
          },
          {
            "level": 2,
            "id": null,
            "text": "Beide Seiten desselben Schreibtisches"
          },
          {
            "level": 4,
            "id": null,
            "text": "Ein Kunde, für den Handel"
          },
          {
            "level": 4,
            "id": null,
            "text": "Eine automatisierte Bot-Flotte, für das Volumen"
          },
          {
            "level": 3,
            "id": null,
            "text": "Die Frage, die dies aufwirft, gesagt einfach."
          },
          {
            "level": 2,
            "id": null,
            "text": "Wer moderiert die Kartenökonomie?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ein Valve-Mitarbeiter moderiert die größte Sammelkarten-Handelsgruppe Valve-Mitarbeiter."
          },
          {
            "level": 3,
            "id": null,
            "text": "Die Bannliste-Ebene und wer sie verwaltet Freiwilliger Moderator Drittanbieter-Dienst"
          },
          {
            "level": 3,
            "id": null,
            "text": "Was dies ergibt und was es nicht ergibt"
          },
          {
            "level": 3,
            "id": null,
            "text": "Niemand zählt. Dies ist das Ergebnis."
          },
          {
            "level": 3,
            "id": null,
            "text": "Die 10.88M-Kontenzählung: 88,97 % unberührt"
          },
          {
            "level": 3,
            "id": null,
            "text": "Forensische Beweise & Vertiefte Zählung"
          },
          {
            "level": 2,
            "id": null,
            "text": "Was gelesen wurde und was nicht beansprucht wird"
          },
          {
            "level": 3,
            "id": null,
            "text": "Die vier Datensätze und die darauf durchgeführte Arithmetik"
          },
          {
            "level": 3,
            "id": null,
            "text": "Hauptquellen"
          },
          {
            "level": 3,
            "id": null,
            "text": "Was wird nicht beansprucht"
          },
          {
            "level": 3,
            "id": null,
            "text": "Warum das Werkzeug nicht das Subjekt ist"
          }
        ],
        "links": [
          "https://help.steampowered.com/en/faqs/view/71D3-35C2-AD96-AA3A",
          "https://github.com/JustArchiNET/ArchiSteamFarm/wiki/FAQ",
          "https://steamcommunity.com/tradingcards/faq/",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260924114457/https://store.steampowered.com/subscriber_agreement/",
          "https://steamladder.com/ladder/badges/2861690/",
          "http://web.archive.org/web/20260716205303/https://steamladder.com/ladder/badges/2861690/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/farm-economy-timeline.json",
          "https://store.steampowered.com/charts/",
          "http://web.archive.org/web/20260923183013/https://store.steampowered.com/charts/",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://github.com/JustArchiNET/ArchiSteamFarm/discussions/3440",
          "https://x.com/gergelyszabo94/status/1311004678633795585",
          "https://x.com/prcs25/status/1811893857253982720",
          "http://web.archive.org/web/20240715122902/https://x.com/prcs25/status/1811893857253982720",
          "https://reddit.com/r/steamsupport/comments/1fjmgc5/what_to_do_when_your_steam_account_gets_hacked/mkelm2y/",
          "https://www.reddit.com/r/csgomarketforum/comments/r87owv/psa_my_steam_account_just_got_banned/",
          "http://web.archive.org/web/20250327203008/https://www.reddit.com/r/csgomarketforum/comments/r87owv/psa_my_steam_account_just_got_banned/",
          "https://www.reddit.com/r/GlobalOffensiveTrade/comments/r9xql9/d_recently_received_commercial_ban_for_what_seems/",
          "http://web.archive.org/web/20211206034804/https://www.reddit.com/r/GlobalOffensiveTrade/comments/r9xql9/d_recently_received_commercial_ban_for_what_seems/",
          "https://www.reddit.com/r/csgomarketforum/comments/1hhxx7m/d_permanently_locked_on_steam_for_commercial_use/",
          "http://web.archive.org/web/20250627014045/https://www.reddit.com/r/csgomarketforum/comments/1hhxx7m/d_permanently_locked_on_steam_for_commercial_use/",
          "https://www.reddit.com/r/steamsupport/comments/1hkctwt/permanent_ban_with_no_explanation/",
          "https://www.reddit.com/r/pcgaming/comments/1vf24lu/warning_to_all_gamersexpats_steam_took_my_money/",
          "https://steamcommunity.com/groups/card-trading-card-trades",
          "https://steamcommunity.com/id/afarnsworth",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/groups/steambans",
          "https://steamcommunity.com/groups/steambans",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/id/killahinstinct_",
          "https://web.archive.org/web/20240914124859/https://steamcommunity.com/id/msart",
          "https://steamcommunity.com/id/msart/groups/",
          "http://web.archive.org/web/20260401154714/https://steamid.uk/faq/",
          "https://phishdestroy.io/steam_dossier/de/enforcement_audit.html",
          "https://phishdestroy.io/steam_dossier/de/#evidence-blackout",
          "https://www.steamcardexchange.net/index.php?badgeprices",
          "http://web.archive.org/web/20260804200309/https://www.steamcardexchange.net/index.php?badgeprices",
          "https://steam.supply/CardBots",
          "https://steamlvlup.net/cardbots",
          "http://web.archive.org/web/20260210171205/https://steamlvlup.net/cardbots",
          "https://steamlvlup.net/",
          "https://creativecommons.org/licenses/by/4.0/",
          "http://web.archive.org/web/20260923221628/https://creativecommons.org/licenses/by/4.0/",
          "https://phishdestroy.io/steam_dossier/de/market_economics.html",
          "https://phishdestroy.io/steam_dossier/de/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/de/elite_skins.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/de/card_economy.content.json",
      "export_json_sha256": "13ecb08452a52bdb3a8d85698bea3cdb1b528c4c92e90fb4ce6a37f987a50469"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "de/elite_skins.html",
      "language": "de",
      "title": "Ein Artikel, zwei Preissysteme – Das Dossier von „Steam“",
      "source_url": "https://phishdestroy.io/steam_dossier/de/elite_skins",
      "source_html_sha256": "ca7c55d0b5ae4660bb3e59157f7052f0ed06549702212dae92f878ca58110420",
      "exported_at": "2026-09-29T00:16:08.113Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "register",
            "source": "https://phishdestroy.io/steam_dossier/de/elite_skins#register"
          },
          {
            "id": "",
            "source": "https://phishdestroy.io/steam_dossier/de/elite_skins#selected"
          }
        ],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "elite_skins.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/de/elite_skins.pdf?v=print-20260929-v5",
        "sha256": "7d6c1c1625eb7cf0cb186835fe82f6857188e1897bf60f00e0ceee53410b4bcf",
        "bytes": 98410,
        "pages": 8
      },
      "integrity": {
        "signed_object": "elite_skins.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "elite_skins.content.json.asc",
        "digest_file": "elite_skins.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify elite_skins.content.json.asc elite_skins.content.json",
          "sha256sum -c elite_skins.content.json.sha256"
        ]
      },
      "content": {
        "text": "ANHANG IV / MARKTARCHITEKTUR / 20 SEPTEMBER 2026\nElite Skins-Registrierung – Die Obergrenze des „1,800“-Marktes\n\nEin Artikel. Zwei Preissysteme.\n\nWAS DIESER ABSCHNITT BELEGT\n\nDieses Verzeichnis erstellt eine empirische Bestandsaufnahme aller CS2-Skin-Kategorien, deren Preis über der von Steam festgelegten Obergrenze von $1,800 für Angebote auf dem Community-Markt liegt, und zwar über fünf externe Handelsplattformen hinweg. Es belegt, dass 248 bestätigte Kategorien der höchsten Preisklasse – die 18,394 aktive Angebote und eine ausgewiesene Liquidität von $78.6 Millionen repräsentieren – 100% auf dem offiziellen Marktplatz von Valve fehlen. Verkäufer, die echte Marktpreise anstreben, werden strukturell auf externe Plattformen gedrängt, während sie sich ausschließlich auf die zugrunde liegenden Handelsmechanismen von Steam verlassen.\n\nWhat this means — the Community Market listing ceiling\n\nSteam’s own market refuses a listing above roughly $1,800. A seller may ask less, never more. Items whose market price sits above that line therefore cannot be sold at that price on Steam at all — which is the mechanism that moves those sales to third-party venues while the item itself never leaves Valve’s inventory system.\n\nSection 13 — the off-Steam price gap →\n\n← Zurück zum Executive Briefing\n\nSteam begrenzt die Listung auf dem Community-Markt auf etwa $1,800. Auf den fünf in dieser Übersicht erfassten Drittanbieter-Marktplätzen 419 weisen die CS2-Artikelkategorien einen günstigsten aktuellen Verkaufspreis auf, der über dieser Grenze liegt – und bei 402 davon, 95.9%,, gibt es überhaupt kein Angebot auf Steam. Zusammen umfassen sie 18,641 gelistete Exemplare im Wert von mindestens $82.4 Millionen. Da die Zustimmung eines zweiten Marktplatzes erforderlich ist, bevor ein Preis berücksichtigt wird, 248 werden diese Kategorien bestätigt – und jede einzelne davon, 100%,, fehlt auf Steam. Das teuerste Exemplar ist ein Sticker | Titan (Holo) | Katowice 2014 mit einem $66,285, der von vier Marktplätzen innerhalb von 5.2% zueinander notiert wird und von keinem der Marktplätze von Valve geführt wird. Die vollständige Rangliste, die Renderings und die Bewertung finden sich im Preis-Ranglisten-Atlas.\n\nAlle „419“-Einträge anzeigen ↓Atlas öffnen ↗Lesen Sie die Methode\n248Kategorien mit zwei oder mehr Marktplätzen, deren Preis über der Obergrenze liegt\n18,394Exemplare, die auf fünf Marktplätzen gelistet sind\n$78.6MMindestwert dieser Angebote\n100%von diesen fehlen vollständig auf Steam\n\nKorrektur · Auf dieser Seite wurde zuvor ein unbestätigter Preis angegeben\n\nEine frühere Version dieser Seite enthielt die Überschrift „Souvenir AK-47 | Point Disarray“, für das auf einem Marktplatz ein Preis von $148,954 verlangt wurde, während Steam einen Preis von $119. angab. Diese Zeile bezieht sich auf ein einzelnes Exemplar in einem einzigen Regal, ohne dass ein zweiter Marktplatz diesen Preis bestätigt, sodass es sich eher um einen Angebotspreis als um einen tatsächlichen Preis handelt; sie ist daher nicht mehr auf der Seite enthalten. Jede hier aufgeführte Zahl beschränkt sich nun auf die Kategorien „248“, bei denen mindestens zwei Marktplätze unabhängig voneinander Preise über der Obergrenze angeben. Die Zeile selbst wurde nicht entfernt – sie ist weiterhin im Register unten zu finden, und die Einstufung, die zu ihrer Herabstufung geführt hat, ist vollständig in der Preis-Ranglisten-Atlas.\n\n01 / dem Geld in aktiven Verkaufsangeboten\nDie messbare Dollar-Untergrenze\n\nNeuberechnet anhand des lizenzierten „cs2.sh“-Snapshots über fünf Marktplätze hinweg. Hierbei handelt es sich um einen minimalen aggregierten Angebotwert in einer definierten Teilmenge, nicht um den Umsatz und auch nicht um eine Bewertung der CS2-Wirtschaft.\n\n248 BESTÄTIGTE KATEGORIEN · 18,394 EINGESTELLTE EXEMPLARE · 5 MARKTPLÄTZE$78.62M\n\nMindestgesamtsumme der angegebenen Angebotspreise für jeden CS2-Artikel, für den zwei oder mehr Marktplätze unabhängig voneinander einen Preis festlegen, der über dem von Valve auf seinem eigenen Markt zugelassenen Höchstwert liegt.\n\nWarum dies ein Mindestwert und keine Schätzung ist\n\nFür jeden Marktplatz multiplizieren wir dessen niedrigsten Angebotspreis für einen Artikel mit der Anzahl der Exemplare, die dieser Marktplatz listet. Jedes andere Exemplar in diesem Regal wird zum niedrigsten Angebotspreis oder darüber angeboten, sodass der tatsächliche angegebene Wert höher ist – aufgrund der Berechnungsweise, nicht aufgrund von Schätzungen. Es handelt sich nicht um einen Verkauf, einen Cashflow oder eine marktweite Bewertung, und derselbe physische Artikel kann auf mehr als einem Marktplatz erscheinen.\n\nAlle „419“-Quellzeilen prüfen ↗\n★ Sport-Handschuhe | Hedge Maze (praxiserprobt)\n$4.68M\nAWP | Gungnir (fabrikneu)\n$4.46M\nAWP | Dragon Lore (fabrikneu)\n$4.34M\n★ Butterfly-Messer | Fade (fabrikneu)\n$4.17M\nAK-47 | Wild Lotus (fabrikneu)\n$4.16M\n★ Butterfly-Messer | Doppler (fabrikneu)\n$3.64M\n\nDie Balken zeigen die sechs größten Beiträge auf Kategorieebene zur Preisuntergrenze, skaliert auf den größten Wert. Ein hoher Balken spiegelt sowohl den günstigsten Angebotspreis als auch die Anzahl der gelisteten Exemplare wider. Da derselbe physische Artikel auf mehr als einem Marktplatz erscheinen kann, dürfen diese Zahlen nicht zu anderen Marktsummen addiert werden.\n\n02 / einsehbare Beispiele\nWas die Obergrenze nicht berücksichtigt\n\nDie Abbildungen entsprechen, sofern verfügbar, den genauen Artikelnamen. Bei den Preisen handelt es sich um aktuelle Angebotspreise aus dem datierten Katalog, nicht um Transaktionsdaten.\n\n★ Butterfly Knife | Doppler (Factory New)\n\nQuelle: https://phishdestroy.io/steam_dossier/de/elite_skins#selected\n\nDie messbare Lücke: Diese Angebote lassen sich nicht mit einem „Steam“-Eintrag zum gleichen USD-Betrag abgleichen. Valves eigene Community-Markt-FAQ archiviert unter 2026-09-21 ↗ gibt einen maximalen Angebotspreis von ca. $1,800 an. Ein Verkäufer könnte dennoch einen niedrigeren Preis festlegen; ob dies akzeptabel wäre, liegt in der Entscheidung des Verkäufers. Eine separate CSMarketCap-Suche nach Artikeln über $1,800 ↗ zeigt „Factory New Dragon Lore“ in allen 28-indizierten Märkten mit etwa 1.1K angezeigten Angeboten; doppelte Bestände können mehrfach gezählt werden.\n\n03 / Die strukturelle Abhängigkeit\nDie Obergrenze von Steam verlagert die Preisbildung außerhalb von Steam\n\nDer Vergleich ist struktureller Natur. Er geht weder davon aus, dass jeder Angebotspreis fair ist, noch behandelt er unverkaufte Angebote als Umsatz.\n\n01 · DIE REGEL\nSteam begrenzt die Angebote\n\nValve besagt, dass Angebote auf dem Community-Markt auf etwa $1,800begrenzt. Auch die Guthaben in den Wallets sind begrenzt, und die Guthaben können nicht als Bargeld abgehoben werden.\n\n02 · DIE BEOBACHTUNG\nDragon Lore: $10,940.85\n\nDer Marktplatzkatalog von „5-“ zeigt 389 aktuelle Angebote für AWP „Dragon Lore“ (Factory New), beginnend bei $10,940.85 (Mindestpreis von CSFloat). Das erweiterte Register enthält 248 bestätigte Kategorien oberhalb des Limits von Steam.\n\n03 · DIE FOLGE\nPreis und Aufteilung der Provision\n\nEin Verkäufer, der diesen höheren Preis anstrebt , kann diesen nicht auf Steam veröffentlichenveröffentlichen. Externe Dienste können den Barpreis festlegen, doch für die Lieferung gelten weiterhin die von Steamkontrollierten Eigentumsverhältnisse und die Eigentumsübertragung.\n\nDer Widerspruch in den Richtlinien: Valves eigene Nutzungsvereinbarung archiviert unter 2026-09-21 ↗ behält sich die kommerzielle Nutzung der Dienste von Steam vor, sofern dies nicht ausdrücklich gestattet ist, während in der 2016 Aussage archiviert unter 2026-09-21 ↗ besagte, dass Glücksspielanbieter bereits Steam OpenID und automatisierte Konten nutzten. Das ist ein direkter Beweis dafür, dValve von dieser Art externer Anbieter auf 2016. wusste. Dennoch darf der offizielle Marktplatz die beobachteten Preise dieser hochwertigen Artikel nicht veröffentlichen. Dies stellt eine architektonische Abhängigkeit von der Preisfindung und den Transaktionen außerhalb vonSteam dar; der Vertragsstatus jedes einzelnen Marktplatzes erfordert gesonderte Nachweise. Die beiden wichtigsten westlichen Marktplätze, die dieses über das zulässige Limit hinausgehende Transaktionsvolumen verzeichnen, agieren als formelle Unternehmenseinheiten in bedeutenden Rechtsräumen — CSFloat Inc. (eingetragen in Delaware, USA) und Skinport GmbH (eingetragen in Stuttgart, Deutschland, HRB 764879) — und wickeln offen Peer-to-Peer-Verkäufe im Wert von Hunderten von Millionen ab, wobei sie sich direkt auf die Web-APIs und die Handelsinfrastruktur von Steam stützen.\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\nDie vier Zeilen mit dem Wert von $100,000 entsprechen dem von CSFloat festgelegten Höchstpreis für Einträge. Sie sind im Register gekennzeichnet und dürfen nicht als Schätzungen verstanden werden. Der archivierte Crawl der CSFloat-Einträge reichte nur bis etwa $6,999,, daher wird für das vollständige Register mit Werten über $1,800 die Momentaufnahme des öffentlichen Katalogs verwendet.\n\n04 / ein weiteres Spiel von „Valve“\nDie Obergrenze umfasst auch Dota 2\n\nDer gleiche strenge „Günstigstes-Angebot“-Test auf Skinport findet 166 CS2-Kategorien und 3 Dota-2-Kategorien. Es handelt sich um einen separaten Marktplatz-Snapshot; fügen Sie diese nicht zu CSFloat’s 245. hinzu\n\nDOTA 2 · 1 ANGEBOT\nHeroic Brutal Crescent\n\nGünstigster Angebotspreis für „Skinport“: $14,622.25.\n\nDOTA 2 · 1 ANGEBOT\nCape der dunklen Kunst\n\nGünstigster Angebotspreis für „Skinport“: $8,255.16.\n\nDOTA 2 · 1 ANGEBOT\n„Corrupted Powered Star“\n\nGünstigster Angebotspreis für „Skinport“: $2,087.92.\n\nDies sind drei aufgeführte Gegenstands-Kategorien, nicht alle existierenden Dota-2-Gegenstände. Sehen Sie sich die datierten „Skinport“-Zeilen an ↗ sowie API Dokumentation ↗.\n\n05 / Robustheit\nDas Ergebnis hängt nicht von der genauen Obergrenze ab\n\nValve legt den Höchstbetrag in der regionalen Währung des Käufers fest, sodass er bei der Umrechnung in USD nicht auf einen eindeutigen Wert fällt. Die Erhebung wird daher bei jedem plausiblen Schwellenwert wiederholt. Der Anteil dieser in „Steam“ fehlenden Artikel sinkt nie unter 95%.\n\nGetestete Schwellenwerte\tArtikelkategorien\tAufgelistete Exemplare\tMindestwert\tFehlen auf Steam\n$1,800\t419\t18,641\t$82,449,526\t95.9%\n$2,000\t382\t15,159\t$75,541,325\t95.5%\n$2,070\t363\t12,336\t$69,560,305\t95.6%\n$2,300\t323\t11,644\t$67,984,432\t95.0%\n$2,500\t299\t10,950\t$66,203,929\t95.0%\n\nLesen Sie jeweils eine Zeile; die Zeilen sind verschachtelte Teilmengen derselben Erhebung, keine separaten Grundgesamtheiten. Der „Mindestwert“ multipliziert die niedrigsten Angebotspreis mit der Anzahl der gelisteten Exemplare, sodass der Bestand naturgemäß zu niedrig angegeben wird. Datensatz öffnen ↗\n\n06 / Seltenheit, die man zählen kann\nWie wenige davon tatsächlich zum Verkauf stehen\n\nBUFF unterteilt das Angebot jedes Artikels in verschiedene Zustandsstufen und veröffentlicht, wie viele Exemplare in jeder Stufe vorhanden sind. Dadurch wird aus dem Begriff „selten“ eine konkrete Zahl – und der Zustand wird preislich getrennt vom Äußeren bewertet.\n\n298 AUFGEFÜHRTE EXEMPLARE\nAWP | Dragon Lore\n\n8 verschiedene Varianten mit Preisangaben. Die teuerste, Souvenir AWP | Dragon Lore (fabrikneu), fragt $12,363 mit 20 Exemplaren im Regal.\n\nIn der besten Preisklasse im Regal (0–0.01) gibt es 2 Exemplare, mit einem Angebotspreis von $17,875 — ein Aufschlag von +45% gegenüber dem Basisangebotspreis des Artikels allein aufgrund des Zustands.\n\n607 AUFGEFÜHRTE EXEMPLARE\nM4A4 | Howl\n\n12 verschiedene Varianten mit unterschiedlichen Preisen. Die teuerste, Souvenir M4A4 | Howl (fabrikneu), fragt $14,895 mit 2 Exemplaren auf Lager.\n\n213 AUFGEFÜHRTE EXEMPLARE\nAK-47 | Wild Lotus\n\n7 verschiedene Varianten mit Preisangaben. Die teuerste, Souvenir AK-47 | Wild Lotus (fabrikneu), fragt $14,895 mit 2 Exemplaren auf Lager.\n\n310 AUFGEFÜHRTE EXEMPLARE\nAWP | Gungnir\n\n7 verschiedene Varianten mit Preisangaben. Die teuerste, Souvenir AWP | Gungnir (minimale Gebrauchsspuren), fragt $14,895 mit 2 Exemplaren auf Lager.\n\nWarum dies für den Rest dieses Dossiers von Bedeutung ist: Es handelt sich hierbei nicht um abstrakte Zahlen. Weltweit befinden sich weltweit einige hundert Exemplare jeder Trophäe im freien Handel, von denen jedes mit einem „Steam“-Konto verknüpft ist und über einen „Steam“-Handel transferiert wurde. In einem so kleinen Markt ist bereits ein einziger gestohlener Bestand ein messbares Ereignis, und die an anderer Stelle in dieser Untersuchung dokumentierten Techniken zur Kontoübernahme bringen einen direkten und quantifizierbaren Gewinn.\n\nDie Zahlen beziehen sich auf aktuelle Angebote auf einem Marktplatz zum Zeitpunkt der Erfassung, nicht auf die Gesamtzahl der existierenden Exemplare. Exemplare, die sich in privaten Beständen befinden, werden hier nirgendwo gezählt. Öffnen Sie den „Float“-Datensatz ↗\n\n07 / die Rangliste ausblenden\nJe teurer der Artikel, desto weiter entfernt von jedem beobachtbaren Handelsplatz\n\nJede Sprosse darunter stellt eine andere Beweiskategorie dar. Sie werden bewusst nicht zu einer einzigen Zahl zusammengefasst.\n\nSprosse\tAbbildung\tUm welche Art von Tatsache handelt es sich\nCeiling on Valve's own market\t~$1,800\tPublished rule, stated in the Steam Community Market FAQ.\nDearest ask several marketplaces agree on\t$66,285\tMeasured by us in this snapshot. Sticker | Titan (Holo) | Katowice 2014, quoted by four marketplaces within 5.2% of one another. An ask, not a sale.\nDearest ask seen on any single shelf\t$148,954\tOne marketplace, one copy, no second marketplace agreeing — and equal to a round CNY 1,000,000 at the snapshot rate. Listed here as the outer edge of what sellers ask, and relied on for nothing.\nPublic marketplace sale\t$49,999\tSpecialist Gloves | Crimson Kimono (FN) on CSFloat, as reported by SteamAnalyst. Platform-recorded, third-party reported.\nReported private sale\t$400,000\tAK-47 | Case Hardened, reported by PC Gamer in April 2023. Journalism, not a record we hold.\nReported offer, declined\t$1,500,000\tBlue Gem Karambit, pattern #387. No sale took place and the figure has not been independently confirmed. Included to mark the ceiling of the claims, not to assert a value.\n\nDer strukturelle Aspekt: Valves Marktpreis liegt bei etwa $1,800. Auf Marktplätzen von Drittanbietern liegt der Preis bei etwa $66,000 – hier stimmen mehrere Anbieter überein – und bei etwa $150,000, wo nur ein Anbieter diesen Preis angibt. Darüber hinaus gibt es überhaupt keinen Handelsplatz mehr – die größten Transfers von durch „Valve“ ausgegebenen Vermögenswerten finden privat zwischen Einzelpersonen statt, ohne Notierung, ohne Plattformaufzeichnung, ohne Identitätsprüfung und ohne Meldepflicht. Die Übertragung selbst läuft weiterhin über „Steam“. Je höher der Wert, desto weniger ist er für andere sichtbar, und die Infrastruktur, auf der er basiert, gehört durchweg der „Valve“.\n\nDie letzten beiden Stufen basieren auf Berichten anderer Personen, die als solche gekennzeichnet sind. Dieses Projekt hat diese nicht überprüft und stützt sich bei seinen Schlussfolgerungen nicht auf sie.\n\nAlle von 419 beobachteten Kategorien\n\nQuelle: https://phishdestroy.io/steam_dossier/de/elite_skins#register\n\n09 / Herkunft und Beschränkungen\nÜberprüfen Sie die Berechnung\n\nWir legen die lokalen Daten und die öffentliche Quelle offen. Die numerische Angabe bezieht sich auf CSFloat zum Erfassungsdatum.\n\nValves eigene Obergrenze und Bedingungen\n\nSteam Community-Markt-FAQ ↗ archiviert unter 2026-09-21 ↗ gibt den ungefähren Höchstwert für1,800-Angebote an. Die Nutzungsvertrag ↗ archiviert unter 2026-09-21 ↗ legt die Einschränkungen für die gewerbliche Nutzung fest.\n\nWoher die Preise stammen\n\nPreise, Anzahl der Notierungen und Kursspannen stammen aus den cs2.sh Marktdaten von API im Rahmen eines kostenpflichtigen gewerblichen Abonnements unter Verwendung eines Lizenzschlüssels. Es wurden keine Marktplätze gecrawlt und keine Marktplatzkonten oder Zugangsdaten verwendet. Der Anbieter aggregiert Daten von BUFF, Youpin, CSFloat, Skinport, C5Game und dem Steam Community Market; alle Zahlen sind in USD angegeben, wie sie zurückgegeben wurden. Öffnen Sie das Herkunftsmanifest ↗ — es enthält die genauen Endpunkte, Erfassungszeitpunkte und SHA-256-Hashes der Rohdaten-Snapshots, sodass ein unabhängiger Leser mit eigenem Schlüssel dieselben Daten abrufen und jede Zahl auf dieser Seite neu berechnen kann.\n\nWas wir nicht erhalten konnten\n\nDas erworbene Abonnement deckt nur aktuelle Snapshots ab. Historische und archivierte Endpunkte standen uns nicht zur Verfügung, und auf dieser Seite werden keine Aussagen zu Trends, vergangenen Preisen oder Veränderungen im Zeitverlauf getroffen. Alles hier bezieht sich auf einen einzelnen, datierten Zeitpunkt.\n\nDas frühere „CSFloat“-Register\n\nDie erste Version dieser Ausstellung zählte „245“-Kategorien aus einer einzelnen Momentaufnahme des „CSFloat“-Katalogs vom 20. September 2026: Dieser Schnappschuss ist hier weiterhin verfügbar ↗. Das vorliegende Verzeichnis ist umfangreicher, da es fünf Marktplätze statt nur eines umfasst. Es handelt sich um zwei separate Erfassungen, die nicht miteinander addiert werden dürfen.\n\nDie spezifische Durchsetzungserklärung von Valve\n\nValves Update zum Handel mit In-Game-Gegenständen unter dem Titel „2016“ ↗ archiviert unter 2026-09-21 ↗ bezieht sich auf Glücksspielanbieter, die OpenID und automatisierte Steam-Konten nutzen. Sie ist enger gefasst als ein Verbot aller externen Marktplätze.\n\nAuslegungsgrenze\n\nEs handelt sich um Angebote, nicht um Verkäufe. Ein Marktname kann mehrere physische Gegenstände mit unterschiedlichen Details hinsichtlich Auflage, Muster oder Aufkleber umfassen. Dieses Verzeichnis erfasst weder den Gesamtmarktwert noch die Absicht von Valve.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Elite Skins-Registrierung – Die Obergrenze des „1,800“-Marktes"
          },
          {
            "level": 2,
            "id": null,
            "text": "Die messbare Dollar-Untergrenze"
          },
          {
            "level": 3,
            "id": null,
            "text": "Warum dies ein Mindestwert und keine Schätzung ist"
          },
          {
            "level": 2,
            "id": null,
            "text": "Was die Obergrenze nicht berücksichtigt"
          },
          {
            "level": 3,
            "id": null,
            "text": "★ Butterfly Knife | Doppler (Factory New)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Die Obergrenze von Steam verlagert die Preisbildung außerhalb von Steam"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam begrenzt die Angebote"
          },
          {
            "level": 3,
            "id": null,
            "text": "Dragon Lore: $10,940.85"
          },
          {
            "level": 3,
            "id": null,
            "text": "Preis und Aufteilung der Provision"
          },
          {
            "level": 2,
            "id": null,
            "text": "Die Obergrenze umfasst auch Dota 2"
          },
          {
            "level": 3,
            "id": null,
            "text": "Heroic Brutal Crescent"
          },
          {
            "level": 3,
            "id": null,
            "text": "Cape der dunklen Kunst"
          },
          {
            "level": 3,
            "id": null,
            "text": "„Corrupted Powered Star“"
          },
          {
            "level": 2,
            "id": null,
            "text": "Das Ergebnis hängt nicht von der genauen Obergrenze ab"
          },
          {
            "level": 2,
            "id": null,
            "text": "Wie wenige davon tatsächlich zum Verkauf stehen"
          },
          {
            "level": 3,
            "id": null,
            "text": "AWP | Dragon Lore"
          },
          {
            "level": 3,
            "id": null,
            "text": "M4A4 | Howl"
          },
          {
            "level": 3,
            "id": null,
            "text": "AK-47 | Wild Lotus"
          },
          {
            "level": 3,
            "id": null,
            "text": "AWP | Gungnir"
          },
          {
            "level": 2,
            "id": null,
            "text": "Je teurer der Artikel, desto weiter entfernt von jedem beobachtbaren Handelsplatz"
          },
          {
            "level": 2,
            "id": null,
            "text": "Alle von 419 beobachteten Kategorien"
          },
          {
            "level": 2,
            "id": null,
            "text": "Überprüfen Sie die Berechnung"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valves eigene Obergrenze und Bedingungen"
          },
          {
            "level": 3,
            "id": null,
            "text": "Woher die Preise stammen"
          },
          {
            "level": 3,
            "id": null,
            "text": "Was wir nicht erhalten konnten"
          },
          {
            "level": 3,
            "id": null,
            "text": "Das frühere „CSFloat“-Register"
          },
          {
            "level": 3,
            "id": null,
            "text": "Die spezifische Durchsetzungserklärung von Valve"
          },
          {
            "level": 3,
            "id": null,
            "text": "Auslegungsgrenze"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/de/#market-gap-section",
          "https://phishdestroy.io/steam_dossier/de/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/de/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/de/skin_atlas.html#grading",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-above-the-ceiling.json",
          "https://phishdestroy.io/steam_dossier/de/elite_skins#selected",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://csmarketcap.com/search?minPrice=1800&amp;page=1",
          "https://store.steampowered.com/agreement/?l=english",
          "http://web.archive.org/web/20260921022032/https://store.steampowered.com/agreement/?l=english",
          "https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921021947/https://store.steampowered.com/oldnews/22883",
          "https://phishdestroy.io/steam_dossier/de/#proxy-bypass-explainer",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/skinport-floor-over-cap.json",
          "https://docs.skinport.com/items",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-float-scarcity.json",
          "https://phishdestroy.io/steam_dossier/de/elite_skins#register",
          "https://cs2.sh/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/csfloat-catalogue.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/de/elite_skins.content.json",
      "export_json_sha256": "51bb99ade38fb21959a02b13dd02cd9c9f5efc68df8ad65a3b00a2c39b593352"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "de/enforcement_audit.html",
      "language": "de",
      "title": "Die Volkszählung Valve wird nicht veröffentlicht – Das Steam-Dossier",
      "source_url": "https://phishdestroy.io/steam_dossier/de/enforcement_audit",
      "source_html_sha256": "77cf9d2cc3e6f51d4e8b6b1d2d26cef808250db97ee67565fd32701aa5fe61c5",
      "exported_at": "2026-09-29T00:16:06.861Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "enforcement_audit.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/de/enforcement_audit.pdf?v=print-20260929-v5",
        "sha256": "7a8afbfc83403018e980dde66f46f4d3ccdd18d4b302beeb8148cdd400e256fb",
        "bytes": 153606,
        "pages": 13
      },
      "integrity": {
        "signed_object": "enforcement_audit.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "enforcement_audit.content.json.asc",
        "digest_file": "enforcement_audit.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify enforcement_audit.content.json.asc enforcement_audit.content.json",
          "sha256sum -c enforcement_audit.content.json.sha256"
        ]
      },
      "content": {
        "text": "ANLAGE VI – DIE VOLKSZÄHLUNG VALVE WIRD NICHT VERÖFFENTLICHT\nWie groß ist die Steam-Farm? Wir haben selbst nachgezählt.\n\nEs gibt keine veröffentlichten Zahlen darüber, wie viele Automatisierungskonten auf Steam laufen. Es besteht auch kein Grund, dies geheim zu halten: Der Steam-ID-Raum ist ein zusammenhängender Ganzzahlbereich, und Valve vergibt den Web-API-Schlüssel, der diesen Bereich abdeckt. Also haben wir die größte Gruppe herangezogen, die sich selbst identifiziert – die ArchiSteamFarm-Community – und jedes Mitglied einmal über den eigenen Sperr-Endpunkt von Valve abgefragt. Die Zugehörigkeit erfolgt automatisch, da ASF beim ersten Start automatisch der Gruppe Steam beitritt, sofern der Nutzer sich nicht ausdrücklich abmeldet oder die Einstellung zum Beitritt zur Gruppe deaktiviert (AutoJoinSteamGroup / Statistik). Da diese Einstellung standardmäßig aktiviert ist, umfasst die Gruppenmitgliedschaft eine breite Bevölkerungsgruppe: aktive kommerzielle Bot-Netzwerke mit mehreren Konten, gelegentlich aktive Hobby-Nutzer sowie gewöhnliche Spieler, die die Software auf ihrem persönlichen Konto ausgeführt und das Standardabonnement nie deaktiviert haben. Damit stellt die Mitgliederzahl eine aussagekräftige Bestandsaufnahme der kumulativen Reichweite der Software dar: 10,880,610 Konten insgesamt (davon 5,360,499 bestätigte Mitglieder ohne Nutzungsbeschränkung, die das $5.00-Eingangsportal passiert haben). Dann stellten wir die einzige Frage, die wirklich zählt – was hat Valve ihnen eigentlich angetan?\n\nWas diese Seite nicht ist. Es geht hier nicht darum, dass Valve zehn Millionen Menschen sperren sollte, und es ist auch keine Beschwerde über „Card-Farmer“. Jede der folgenden Zahlen ist aus einem einzigen Grund hier aufgeführt: Valve tut Personen dauerhaft zu sperren, wobei als schriftlicher Grund die kommerzielle Nutzung von Steam und die Automatisierung angegeben wird. Hier wird gemessen, wie dieselbe Regel in großem Maßstab auf dasselbe Verhalten angewendet wird – durch einen Betreiber, der dabei $5.00 für die Freischaltung, Spiellizenzen und Marktgebühren Valve einnimmt. Das Ergebnis ist die Asymmetrie, nicht die Farm.\n\nDie Zahl von 10,88 MillionenDie Betrüger, die zu Fuß unterwegs sind (53,5k)Bezahlte Prüfung (100.000) vs. kostenlose Prüfung\n10,880,610Gesamtzahl der Mitglieder der ASF-Gruppe, die die eigene Ban-API von Valve durchgelesen haben (begrenzt + unbegrenzt zusammen)\n88.97%Wurde noch nie gesperrt – 9,680,599 Konten sind noch aktiv\n63.06%Von den gesperrten Konten sind bezahlte ($5+ Ausgaben) — 100,000 SRSWOR Anteil (±0.39% MoE)\n67.77%Von den 51,732 verurteilten Betrügern unterliegt keiner einem Betrugsverbot (vollständige Erhebung)\n01 — Die Skala\nZehn Millionen Konten, von denen neun von zehn unberührt sind\n\nEine Population, die sich selbst zählt, gelesen einmal durch den eigenen Endpunkt von Valve.\n\nWARUM ES SICH SELBST ZÄHLT\nASF schließt sich der Gruppe für dich an\n\nBeim ersten Durchlauf ArchiSteamFarm Sätze Statistiken ist standardmäßig auf „true“ gesetzt und fügt die Gruppe „Archi's SC Farm Steam“ hinzu. Ein Betreiber muss sich aktiv abmelden. Die Mitgliedschaft stellt somit eine Untergrenze für die Installationen dar – keine Obergrenze. Betreiber, die die Statistik deaktiviert haben, sind nicht erfasst; die tatsächliche Anzahl der Installationen ist mindestens so groß.\n\nWAS WIR LESEN\n10,880,610 Einträge insgesamt\n\nDie API-Mitgliederliste lieferte insgesamt 10,880,610 SteamID64s zurück – sowohl eingeschränkte als auch uneingeschränkte. Auf der Gruppenseite von Steam werden 5,360,499 (nur uneingeschränkte) angezeigt. Jeder Eintrag wurde einmal durch ISteamUser/GetPlayerBans am 2026-09-23. Fünfundfünfzig Minuten auf einer Taste.\n\nDIE ANTWORT\n88.97% sauber\n\n1,200,011 unterliegt keinem Steam Verbot (11.03%). Die anderen 9,680,599 Es liegen überhaupt keine Einträge vor. — keine Sperre aus der Community, kein VAC, gar nichts. Der Account wird nicht gelöscht. Er bleibt weiterhin aktiv. Dieselbe Klausel, wenn sie auf eine einzelne Person angewendet wird, reicht aus, um diese dauerhaft zu entfernen.\n\nVon den 10,880,610 Konten: Wie viele Valve wurden berührt?\n\nDie gesamte gescannte Population, unterteilt danach, ob Valve überhaupt ein Verbot verhängt hat. Der rote Ausschnitt umfasst alles, was Valve jemals in Bezug auf diese Flotte unternommen hat.\n\n88.97%nie gesperrt\n11.03%\nKein Verbot jeglicher Art — 9,680,599 (88.97%)Mit einem Steam-Verbot — 1,200,011 (11.03%)\n10,880,610Mitglieder der ASF-Gruppe wurden gescannt\n9,680,599Nie gesperrt — 88.97%\n1,200,011Jedes Verbot durchsetzen — 11.03%\n55 Min.Um alles zusammenzuzählen, mit einem API-Schlüssel\nWas diese Flotte bereits für ihre Existenz bezahlt hat: Valve\n\nKeine Schätzung der Einnahmen des Betriebs. Eine Untergrenze für die Ausgaben, die der Betrieb bereits in Valves Laden getätigt hat – abgeleitet aus Valves eigener Regel, angewandt auf die obige Zählung.\n\nDie Anzahl 10,880,610 umfasst die vollständige Liste der ASF-Gruppenmitglieder, wie sie von der API zurückgegeben wird – dies schließt sowohl eingeschränkte als auch uneingeschränkte Konten ein. Steams eigene Benutzerkonten mit eingeschränkten Rechten Auf der Seite heißt es, dass eingeschränkte Konten nicht anrechnen Steam Gruppenmitgliedschaft (sie werden bei der Anzeige der Gruppengröße nicht berücksichtigt), können aber dennoch in der zugrunde liegenden Mitgliederliste erscheinen. Die nicht eingeschränkte Teilmenge – Konten, die mindestens $5.00 im Steam-Shop ausgegeben haben – ist genau 5,360,499 — Die Anzahl Steam wird auf der Gruppenseite angezeigt, wobei gemäß der von Steam selbst festgelegten Regel eingeschränkte Konten ausgeschlossen sind. Die Berechnung der Untergrenze $5.00 gilt nur für diese nicht eingeschränkte Teilmenge.\n\n5,360,499Mitglieder ohne Beschränkungen\n(Die angezeigte Gruppenanzahl von Steam)\n×\n$5.00Valves eigenes Minimum\num nicht mehr eingeschränkt zu sein\n=\n$26,802,495Mindestausgaben im Geschäft\ndurch die nicht beschränkte Teilmenge\n\nDies ist eine Untergrenze für die Beträge, die Valve bereits vom nicht begrenzten Teil der Flotte erhalten hat – es handelt sich weder um eine Umsatzschätzung noch um eine Gewinnangabe. Die tatsächlichen Ausgaben pro Konto liegen bei den meisten höher; die Zahl $5.00 stellt lediglich die erforderliche Mindestschwelle dar.\n\nDie Sekundärobernte: bis zu 66.7% Gebühr auf das Volumen der angebauten Erzeugnisse. Zusätzlich zum Eintrittsgeld von $26.8M wird für jede Karte und jeden Artikel, der auf dem Community-Markt verkauft wird, eine obligatorische Mindestgebühr von Valve ($0.01 Steam Gebühr + $0.01 Herausgebergebühr) erhoben. Bei typischen 3-Cent-Karten und Ramschartikeln, Valve nimmt 2 Cent von 3 Cent – eine effektive Kürzung um 66.67% zugunsten von Valve, was weit über dem angegebenen 15%-Marketingzinssatz liegt.\n\nWichtiger Hinweis zur Bevölkerungszahl: Die Zugehörigkeit zu einer Gruppe ist kein Beweis dafür, dass es sich bei jedem einzelnen Konto um einen reinen Bot handelt, und sie erfasst auch nicht jeden Bot auf Steam. ASF fügt Konten standardmäßig beim Start automatisch seiner Community-Gruppe hinzu, es sei denn, der Nutzer deaktiviert dieses Konfigurationsflag ausdrücklich (AutoJoinSteamGroup), regelmäßige Spieler, gelegentliche Spieler und Community-Mitglieder bleiben neben automatisierten Farming-Flotten auf der Spielerliste. Darüber hinaus wird bei einer Steam-Sperre kein öffentlicher Grund angegeben. Die Feststellung bezieht sich auf eine empirisch ermittelte Quote innerhalb dieser mit der Software verbundenen Population und stellt kein individuelles Urteil über einen einzelnen Account dar. Aggregiert, reproduzierbar: asf-ban-census-2026-09-23.json.\n\n02 – Geografie\nWo die Flotte beheimatet ist\n\nNur 8.5% der gesperrten Konten geben überhaupt ein Land an. Unter denjenigen, die dies tun, entfallen die meisten auf die Vereinigten Staaten.\n\nEin Steam-Profil enthält ein optionales Länderfeld. 100,413 der 1,182,811 gesperrten Konten geben dies an — 8.5%.† Unter dieser Minderheit liegen die Vereinigten Staaten mit 15.5% an der Spitze, gefolgt von der Ukraine, China und Russland, während sich der Rest in einem langen Schweif über Europa, Lateinamerika und Südostasien erstreckt. Niemand überprüft diese Angaben: Afghanistan rangiert unter den Top Ten, was in etwa seinem tatsächlichen Wert entspricht. Die übrigen 91.5% werden eher weggelassen als zugeordnet, sodass das, was folgt, das Bild einer selbst ausgewählten Minderheit ergibt – keine Karte der Flotte und keine Grundlage für die Aussage, von wo aus sie betrieben wird.\n\nGesperrte Konten nach angegebenem Land\n\nDie 15 Länder mit den meisten der 100,413 gesperrten Konten, die einen öffentlichen Standort preisgeben. Der Anteil bezieht sich auf diese Teilmenge. Bewegen Sie den Mauszeiger darüber, um die Zahlen anzuzeigen.\n\n0%\n5%\n10%\n15%\n20%\nUnited States\nUkraine\nChina\nRussia\nCanada\nAustralia\nJapan\nBrazil\nGermany\nAfghanistan\nUnited Kingdom\nRomania\nFrance\nPhilippines\nIndia\n\nStandort gelesen aus GetPlayerSummaries für die gesperrte Teilmenge. Das Feld wird vom Kontoinhaber festgelegt und von niemandem überprüft, sodass ein VPN-Ausgang oder ein Scherzeintrag genauso zählt wie ein echter Eintrag.\n\n03 — Frische\nAktuelle Aufträge, kein Altbestand\n\nGemessen an dem Zeitpunkt der Kontoeröffnung handelt es sich bei den gesperrten Nutzern um eine neue Gruppe und nicht um einen Überrest aus der Sammelkarten-Ära.\n\nWäre dies ein altes Chaos, das nach und nach beseitigt wird, würden die gesperrten Konten vor allem aus den frühen Jahren des Sammelkartengeschäfts stammen. Das Gegenteil ist jedoch der Fall. Von den 1,132,852 gesperrten Konten, deren Erstellungsdatum bekannt ist, 70% wurden im Jahr 2020 oder später gegründet, und fast die Hälfte davon seit 2023. Die Zahl stieg von 59,175 im Jahr 2017 auf einen Höchststand von 227,030 allein im Jahr 2024 geschaffen. Jeder von ihnen passierte das $5.00-Ladentor, bevor dort eine Karte entgegengenommen werden konnte, sodass für jeden Einzelnen der Eintrittspreis erhoben wurde.\n\nAls die gesperrten Konten angelegt wurden\n\nJahr der Kontoeröffnung der 1,132,852 gesperrten Mitglieder, deren Erstellungsdatum bekannt ist. Der Zeitraum umfasst die Jahre 2020–2026, nicht die Sammelkarten-Ära von 2013–2015. Höchststand: 2024. Für Zahlenangaben mit der Maus darüberfahren.\n\n0k\n63k\n125k\n188k\n250k\n'13\n'14\n'15\n'16\n'17\n'18\n'19\n'20\n'21\n'22\n'23\n'24\n'25\n'26\n70%Von gesperrten Konten, die im Jahr 2020 oder später erstellt wurden\n227,030Gesperrte Konten, die im Jahr 2024 erstellt wurden – dem Jahr mit den meisten Sperrungen\n51,701Der Tiefpunkt im Jahr 2021 zwischen zwei Spitzenjahren – ungeklärt\n2003→2026Der Bereich ist vorhanden, aber die Daten beziehen sich auf die letzten sechs Jahre\n\nDas Werk stammt aus dem Jahr GetPlayerSummaries für die gesperrte Teilmenge, dedupliziert nach SteamID64. Als Erstellungsdatum gilt der Zeitpunkt, zu dem das Konto angelegt wurde, nicht der Zeitpunkt, zu dem es gesperrt wurde oder mit dem „Farming“ begann; dieser Wert dient hier als Hinweis darauf, wie aktuell die Daten sind, nicht als Hinweis auf die Absicht. Drei Dinge, die die Grafik nicht zeigt:\n\nEin Trend nach 2024. Ein Konto, das 2025 oder 2026 eröffnet wurde, hatte weniger Zeit, eine Sperre zu erhalten, und das Jahr 2026 umfasst neun Monate – daher ist 227,030 → 121,070 → 16,534 eine Zensur und kein Rückgang.\nEine Verbotsquote. Die Erstellungsjahre wurden nur für gesperrte Konten erfasst, daher gibt es keinen Nenner. Allein eine wachsende Nutzerbasis würde diesen Verlauf ergeben.\nWarum das Jahr 2021 scheiterte. 51,701 liegt zwischen 105,821 und 104,641, jeweils unter der Hälfte eines der beiden Nachbarn. Es gibt keine öffentliche Erklärung dafür; es bleibt sichtbar, anstatt geglättet zu werden.\n04 — Zeitplanung\nWenn Valve wirkt, wirkt es innerhalb des ersten Jahres\n\nDie naheliegende Rechtfertigung dafür, dass 88.97% unangetastet bleibt, ist ein Rückstand. Die datierten Verbote sprechen jedoch eine andere Sprache.\n\nWie alt war der Account, als die Sperre verhängt wurde?\n\nAlter des Kontos zum Zeitpunkt der Sperrung für die 293,750 gesperrten Konten, für die sowohl ein Erstellungsdatum als auch ein Datum der letzten Sperrung vorliegen. Mehr als die Hälfte wurde innerhalb des ersten Jahres entdeckt.\n\n0%\n10%\n20%\n30%\n40%\n<6 mo\n33.7%\n6–12 mo\n21.5%\n1–2 y\n20.6%\n2–5 y\n14.3%\n5 y+\n10.0%\n55.1% inside the first year\nIm ersten Jahr gesperrt — 55.1%Später gesperrt — 44.9%\n0,80 yDurchschnittsalter des Kontos zum Zeitpunkt der Sperrung\n55.1%Sperre innerhalb des ersten Jahres nach der Kontoeröffnung\n33.7%In den ersten sechs Monaten gesperrt\n293,750Konten, bei denen beide Daten vorhanden sind\n\nDies ist die Antwort auf das naheliegende Einwand. Wenn 88.97% der Flotte unberührt bleibt, weil die Durchsetzung einfach langsam ist – ein Rückstau, der nach und nach abgebaut wird –, dann sind die Verbote, die tun Die Daten würden ein verzerrtes Bild der Altersstruktur vermitteln. Das Gegenteil ist der Fall: Der Medianwert der gesperrten Konten lag bei neuneinhalb Monate alt, und ein dritter – 33.7% – wurde innerhalb von sechs Monaten gefangen. Wenn Valve auf diese Population einwirkt, geschieht dies schnell. Die neun von zehn, die noch auf freiem Fuß sind, warten nicht in einer Warteschlange.\n\nAlter zum Zeitpunkt des Verbots = Erstellungsdatum ab GetPlayerSummaries abgezogen von dem Datum des Verbots, das sich aus TageSeitDerLetztenSperre, weiterlesen 2026-09-23. Der Wert wird nur berechnet, wenn beide Werte vorhanden sind: 293,750 der 1,200,011 gesperrten Konten. Die übrigen Konten weisen keinen Wert für die Anzahl der Tage seit der Sperre auf und werden weggelassen, nicht angenommen – betrachten Sie dies also als die Struktur der datierten Teilmenge, nicht als die jeder einzelnen Sperre.\n\n05 – Was das Verbot eigentlich beinhaltet\nWenn Valve aktiv wird, stoppt es den Bot nicht\n\nVon den 11%, für die ein Verbot gilt, schau dir an, um welches Verbot es sich handelt.\n\nEin Sperrbefehl ist kein Sperrbefehl. Von den 1,200,011 Konten, die Valve gemeldet hat, 99.8% tragen ein Gemeinschaft Verbot — eine Einschränkung für Foren, Profile und Gruppen, die einem Handelsbot nichts anhaben kann. Das Konto kann weiterhin Karten erhalten, weiterhin handeln und weiterhin Bestände verschieben. 22.2% mindestens eine Spielsperre und 3.9% eine VAC-Sperre; die Kategorien überschneiden sich, daher addieren sie sich nicht. Die einzige Sanktion, die den Handel tatsächlich unterbindet – die Wirtschafts-/Handelssperre –, betrifft 5,214 Konten. Wir stützen unsere Argumentation nicht auf diese Zahl – Handelssperren sind im Allgemeinen bei Steam selten. Der Kern dieser Grafik ist einfacher: Selbst der Anteil von Valve tut touch handelt weiter.\n\nWofür genau die 11%, die gesperrt wurden, eigentlich gesperrt wurden\n\nDer Anteil der einzelnen Sperrarten an allen 10,880,610 gescannten Mitgliedern. Ein Konto kann mehr als eine Sperrart aufweisen. Bewegen Sie den Mauszeiger darüber, um die Zahlen anzuzeigen.\n\n0%\n4%\n8%\n11%\n15%\nCommunity ban\nGame ban\nVAC ban\nEconomy / trade ban\n\nEin „0“-Sperrvermerk enthält kein Feld für die Begründung, daher wird keine dieser Sperren speziell dem „Card Farming“ zugeschrieben – dies ist eine Aufschlüsselung der vorhandenen Sperrarten, nebeneinander gestellt mit den jeweiligen Einschränkungen der einzelnen Arten. Eine Community-Sperre verhindert den Handel nicht; eine Wirtschafts- bzw. Handelssperre hingegen schon. Zusammenfassung: asf-ban-census-2026-09-23.json.\n\n06 – Die andere Bevölkerungsgruppe\nDie Betrüger Valve lassen uns gehen: Die 51,732 vollständige Volkszählung\n\nEine zweite, unabhängige Liste – von der Community bestätigte Betrugsfälle –, die anhand derselben offiziellen API ermittelt wurde.\n\nDie Gruppe der Automatisierer ließe sich noch als harmlose Müßiggänger abtun. Die zweite Gruppe hingegen nicht. SteamRep ist eine seit Langem bestehende Datenbank zur Bewertung der Reputation von Community-Mitgliedern; ein Konto, das als GESPERRT Von dieser Community wurde eine Person als Betrüger eingestuft, wobei Nachweise der Opfer und Chat-Protokolle der Transaktionen vorliegen. Wir haben eine 100%-Erhebung aller 51,732 Profile mit dem Status „GESPERRT“ gegen die offizielle Web-API von Steam (ISteamUser/GetPlayerBans/v1) – und dabei wurden nur die Sanktionen berücksichtigt, die sich auf Betrug beziehen. Eine VAC-Sperre gilt für Software-Betrug in einem Spiel (Aimbots, Wallhacks); sie hat keine Auswirkungen auf einen Händler und ist kein Beweis Valve für betrügerisches Handeln, daher wird sie nicht als Maßnahme zur Betrugsbekämpfung gewertet.\n\nÜber die gesamte 51,732-Kontoerhebung hinweg haben 67.77% — 35,059 nachweislich betrügerische Nutzer — NULL betrugsbezogene Sperren von Valve: Sie können weiterhin handeln, neuen Opfern Freundschaftsanfragen senden und Nachrichten verschicken. Nur 32.23% wurden entweder mit einer Community- oder einer Handelssperre belegt, und die Handelssperre – die einzige Maßnahme, die den Transfer von Inventar tatsächlich unterbindet – betrifft lediglich 18.81% (9,731 Konten). Weitere 12.81% (6,627 Konten) sind mit VAC Spielverboten allein wegen Betrugs im Spiel belegt, während sie beim Handel in Steam Fällen keinerlei Einschränkungen unterliegen.\n\nBestätigte Betrüger, je nachdem, ob Valve eine betrugsbezogene Sperre verhängt hat (vollständige Erfassung)\n\nAlle 51,732 SteamRep-gesperrten Profile, aufgeschlüsselt danach, ob Valve eine Community- oder Handelssperre verhängt hat. VAC- und Spielsperren sind ausgeschlossen – sie beziehen sich nicht auf Betrug. Bewegen Sie den Mauszeiger darüber, um die Zahlen anzuzeigen.\n\n0%\n18%\n35%\n53%\n70%\nNo scam-relevant ban\nCommunity or trade ban\n0%\n6%\n13%\n19%\n25%\nCommunity ban\nTrade / economy ban\nVAC (not fraud)\nGame ban\n51,732SteamRep gesperrte Profile geprüft — 100% vollständige Erhebung\n35,059Keine Sperre aufgrund von Betrug (67.77%)\n18.81%Setzen Sie das Handelsverbot durch, das Betrugsmaschen unterbindet (9,731)\n32.23%Der Beitrag Valve wurde mit einem Community- oder Handelsverbot (16,673) belegt.\n\nSteamRep ist eine von einer Community bewertete Reputationsdatenbank eines Drittanbieters und keine Valve-Entscheidung – und genau darum geht es: um externe Beweise, gemessen an dem, was Valve selbst getan hat. Alle 51,732 gesperrten Profile aus dem kanonischen Export wurden direkt mit ISteamUser/GetPlayerBans/v1. „Betrugsrelevant“ bedeutet eine Sperre für die Community oder den Handel; VAC (12.81%) und Spielsperren (3.86%) werden separat gezählt, da sie sich auf Cheating und nicht auf Betrug beziehen. Vollständiger Prüfungsdatensatz: steamrep_steam_bans.csv.\n\nZwei Populationen, ein Befund\n\nEs handelt sich nicht um dieselben Personen und nicht um dasselbe Verhalten. Bei dem einen Fall geht es um zehn Millionen automatisierte Konten, bei dem anderen um dreiundfünfzigtausend rechtskräftig verurteilte Betrüger. Was sie gemeinsam haben, ist die Form des Ergebnisses: Neun von zehn landwirtschaftlichen Konten werden nie angerührt, und mehr als zwei Drittel (67.77%) der nachweislich betrügerisch handelnden Personen müssen keine Sanktionen wegen Betrugs befürchten. Die Community-Sperre Valve schränkt Foren und Profile frei ein, nicht den Handel. Die Melden-Funktion, die Reputationsdatenbank, die Sperre, die einen Betrug verhindert: alles vorhanden, alles zu wenig genutzt. Vergleichen Sie dies mit den archivierten Ablehnungen im Hauptdossier, in denen dasselbe Unternehmen ein einzelnes Konto dauerhaft löscht und als Grund kommerzielle Nutzung sowie Automatisierung angibt – die Klausel ist nicht nur auf dem Papier, sie wird gezielt angewendet.\n\n07 — Der „$5.00“-Account-Skandal und Account-Hijacking\nDie empirische Untersuchung zu 100,000-Konten: Botnetze sind keine kostenlosen Einwegkonten\n\nStatistische Stichprobenlogik und mathematischer Beweis: Warum die Verwendung beliebiger anderer 100,000-Werte genau dasselbe Ergebnis liefert.\n\nValve hat gegenüber Aufsichtsbehörden und Verbraucherschutzorganisationen vor allem damit argumentiert, dass automatisierte Betrugsversuche und „Farming“ über kurzlebige, kostenlose „Wegwerf“-Konten durchgeführt werden, die schnell gesperrt werden. Gemäß den von Valve veröffentlichten Regeln gilt ein Konto als Begrenzt bis es mindestens 5.00 USD im Steam-Store, wodurch der Zugriff auf Handel, Freundschaftsanfragen und API-Funktionen gesperrt ist. Wir haben diese Behauptung direkt überprüft, indem wir den Monetarisierungsstatus einer repräsentativen, mathematisch fundierten Stichprobe von 100,000 gesperrte Steam Konten entnommen aus unserem 1,182,811-Profil-Metadatenkorpus.\n\nPROBENENTNAHMEPROTOKOLL (SRSWOR)\n100,000 Unvoreingenommener Ausschnitt\n\nEntnommen aus N = 1,182,811 eindeutige gesperrte Steam Konten, die mittels einfacher Zufallsauswahl ohne Zurücklegen unter Verwendung eines kryptografisch gleichverteilten PRNG ausgewählt wurden. Jedes Konto hatte eine identische Einbeziehungswahrscheinlichkeit von P = n / N ≈ 8.45%, wodurch Überlebens- und Aktivitätsverzerrungen vollständig beseitigt werden.\n\nMATHEMATISCHER BEWEIS\nFehlergrenze < ±0.4%\n\nAnwendung der Formel zur Korrektur für endliche Grundgesamtheiten (FPC) bei einem 99% Konfidenzintervall (Z = 2,576):\nMoE = Z × √[p(1-p)/n] × √[(N-n)/(N-1)] ≈ ±0.39%\n\nREPRODUZIERBARKEIT\nWarum jede 100.000 immer dasselbe ergibt\n\nDa die Fehlergrenze bei einem Konfidenzniveau von 99% auf ±0.4% begrenzt ist, Es ist mathematisch garantiert, dass jede andere unabhängige Stichprobe aus dem 100,000-Konto in den Bereich von 63.06% ± 0.39% fällt. (62.67% bis 63.45%). Die Stichprobe spiegelt die gesamte Gruppe der 1,18 Millionen gesperrten Personen wider.\n\nDie Prüfungsergebnisse widerlegen die Behauptung, es handele sich um „Wegwerf-Bots“, vollständig. Von den 100,000 Konten, die über die veraltete XML-Profil-Schnittstelle von Steam geprüft wurden: 61,490 Konten (63.06% der klassifizierten Konten) sind uneingeschränkte (bezahlte) Konten, auf denen mindestens $5.00 für Steam ausgegeben wurden. Nur 36,021 (36.94%) sind eingeschränkte kostenlose Konten, während 2,489 nicht konfiguriert oder privat waren.\n\n100,000 Gesperrte Konten: Bezahlte Konten ($5+ Ausgaben im Store) vs. kostenlose Konten mit eingeschränktem Status\n\nEmpirische Überprüfung von 100,000 zufällig ausgewählten gesperrten Konten. Über 63% haben die bezahlte Finanzsperre von Valve überwunden. Bewegen Sie den Mauszeiger darüber, um die Zahlen anzuzeigen.\n\n0%\n16%\n33%\n49%\n65%\nNon-limited (Paid ≥ $5.00)\nLimited (Free < $5.00)\n100,000Stichprobenpopulation (SRSWOR, N = 1,18 Mio.)\n63.06%Unbegrenzte kostenpflichtige Konten (61,490-Konten)\n±0.39%Fehlermarge bei einem Konfidenzintervall von 99%\n~745,800Extrapolierte bezahlte Konten in einem Korpus von 1,18 Mio. gesperrten Konten\nDie strukturelle Realität: Kontoschließungen im industriellen Maßstab\n\nWarum sollten 63% der untersuchten gesperrten Konten kostenpflichtige Konten sein, bei denen im Shop von Valve echtes Geld ausgegeben wurde? Botnetzbetreiber geben nicht Millionen aus eigener Tasche für Wegwerfkonten aus. Dieses Verhältnis verdeutlicht das Ausmaß von kompromittierte und gekaperte Konten die im Ökosystem zirkulieren.\n\nDieses Ausmaß lässt sich auf Untergrundplattformen direkt beobachten: auf Marktplätzen wie dem FSB Market (anonymisierte Bezeichnung; der Originalname wird hier nicht genannt), über 550,000 Steam Konten (Stealer-Protokolle, Phishing-Erfassungen, Credential Stuffing) werden zu jedem beliebigen Zeitpunkt aktiv zum Verkauf angeboten (phishdestroy.io/live-intel). Der Marktplatz authentifiziert Käufer und Verkäufer mithilfe der eigenen Steam-OpenID von Valve, und weder FSB Market noch das zugehörige Forum wird durch den Link-Filter von Valve blockiert.\n\nWie in Abschnitt 06 dargelegt, unterbindet Valve diese betrügerische Aktivität nicht proaktiv: 67.77% der von der Community bestätigten Betrüger haben auf Steam keinerlei Sperren wegen Betrugs, und 88.97% der Automatisierungsflotte bleibt völlig unberührt. Die Konten bewegen sich frei, authentifizieren sich über offizielle APIs und handeln im gesamten Ökosystem nahezu ungestraft.\n\nDiagramm zur Architektur für forensische Beweismittel und Strafverfolgung\nInteraktiver Überblick über 10,88 Millionen gescannte Konten, 100.000 empirisch ermittelte Fälle und 53.500 bestätigte Betrüger · Klicken Sie auf die Links, um die Rohdaten einzusehen\nStufe 01 · 10,88 Mio. Automatisierungsflotte – Bestandsaufnahme\nDie größte Gruppe von Nutzern, die sich selbst als Automatisierungsnutzer bezeichnet, auf Steam durchlief nacheinander die offizielle Sperr-API von Valve. Dies beweist, dass kommerzielle Bot-Flotten auf 88.97% ungestraft operieren, während sie gleichzeitig Eintrittsgebühren in Höhe von mehreren zehn Millionen zahlen.\n9,680,599 88.97% Aktiv & unberührt\nKonten, auf denen automatisierte Software ausgeführt wird und für die keinerlei Sperren verzeichnet sind.\nJSON-Datei mit den Rohdaten der Volkszählung (1,2 KB) ↗Abschnitt 01 prüfen ↗\n$26,802,495 Mindestumsatz in den Filialen\nVon Valve von 5,360,499 Mitgliedern ohne Beschränkungen gesammelt, die die Mindestteilnahmeschwelle von $5.00 überschritten haben.\nPrüfung der Kartenwirtschaft ↗Valve $5 FAQ zu den Regeln ↗\n1,200,011 11.03% Markierte Teilmenge\n99.8% betrifft ausschließlich kosmetische Community-Sperren; der Handel bleibt auf 99.95% Konten weiterhin möglich.\nAufschlüsselung nach Sperrart ↗Gesperrte Datenbank (60,4 MB) ↓\nStufe 02 · 100,000-Konto: Empirische Stichprobenprüfung (N = 1,182,811)\nRepräsentative Stichprobe von SRSWOR, ausgewertet über veraltete XML-Endpunkte. Mathematisch nachgewiesene Fehlerquote < ±0.4% bei einem Konfidenzintervall von 99%. Widerlegt die Behauptung, dass gesperrte Bots kostenlose Wegwerfkonten seien.\n61,490 (63.06%) Unbegrenzte kostenpflichtige Konten (Ausgaben ab 0)\nÜber 63% der gesperrten Konten entfallen auf bezahlte Transaktionen. Dies lässt sich auf etwa 745,800 bezahlte Konten (Mindestschwelle von $3.73M+) im Pool der gesperrten Konten hochrechnen.\nAusgewählte Ergebnisse als CSV-Datei (2,1 MB) ↓100k-Forensikbericht ↗\n36,021 (36.94%) Kostenlose Konten mit eingeschränkten Funktionen (< $5.00)\nDie Minderheit der gesperrten Profile, die dem von Valve beschriebenen Profil eines „Wegwerf-Bots“ entsprechen. Die 2,489-Konten waren nicht konfiguriert bzw. privat.\nCSV-Datei mit 100.000 Beispieldatensätzen (8,5 MB) ↓Ausgabenanalyse MD ↗\n34.67% gegen 63.93% Prüfung der Profilsanierung\nValve Spitznamen wurden auf 34,673 Konten durch die reine SteamID64 ersetzt, während benutzerdefinierte Namen und Avatare auf 63,928 gesperrten Konten vollständig unverändert blieben.\nAbschnitt „Desinfektion“ ↗Übersicht Roadmap ↗\n34.59% Vermächtnis Altkonten (angelegt 2003–2019)\nÜber ein Drittel der gesperrten Konten wurde vor 5 bis über 20 Jahren registriert, was auf eine im industriellen Maßstab erfolgende Kontoübernahme bei langjährigen Steam-Spielern hindeutet.\nChronologie der Epochen ↗Ablehnungen von Unterstützungsanträgen ↗\nStufe 03 · 51,732 SteamRep Erhebung zu bestätigten Betrügern\nVollständige 100%-Erhebung zu von der Community gemeldeten Betrügern mit Chat-Protokollen der Opfer und Handelsnachweisen, abgeglichen mit offiziellen Steam-Sperr-APIs. Belegt ein systemisches Versagen bei der Durchsetzung.\n35,059 (67.77%) Keine Sperren wegen Betrugs (vollständige Straffreiheit)\nÜber zwei Drittel der identifizierten Betrüger unterliegen weder einem Community- noch einem Handelsverbot von Valve. Sie sind voll einsatzfähig, um Handel zu betreiben und neue Opfer zu gewinnen.\nSteamRep API-Sperren (2,6 MB) ↓SteamRep Prüfungsbericht ↗\n9,731 (18.81%) Wirtschaft / Handelsembargos\nDie einzige Sanktion, die die Bestandsliquidation unterbindet. Tritt bei weniger als einem Fünftel der bestätigten Betrüger auf.\nSteamRep Quelle (2,1 MB) ↓Siehe Abschnitt 06 ↗\n6,627 (12.81%) Irrelevante Sperren wegen Betrugs (nur VAC)\nWegen Aimbots/Wallhacks in Spielen gesperrt, während ihre Steam Handels- und Phishing-Fähigkeiten weiterhin 100% aktiv sind.\nVAC Irrelevanzanalyse ↗Sicherheitszeitleiste ↗\nStufe 04 · Wiki-Verunstaltungen und Infrastrukturangriffe im August 2026\nManipulationen an der internen Entwicklerdokumentation, die Unterdrückung von Community-Redakteuren und Fehler im ungesicherten Perimeter, die im Beweismaterialpaket dokumentiert sind.\n1,200+ Redaktion VDC-Wiki-Konfliktprotokolle\nCommunity-Redakteure, die versuchten, Phishing-Links und Spam-Vorlagen zu korrigieren, wurden systematisch von automatisierten Filtern blockiert, während Valve Mitarbeiter die Warnungen ignorierten.\nBericht über Konflikte in Russland (127 KB) ↗Klassifizierungsbericht (66 KB) ↗\n12 TB, nicht authentifiziert August 2026 – Asset Leak (CWE-284)\nValve hat wochenlang 12 Terabyte an internem Code und Prototyp-Builds auf einem öffentlich zugänglichen Endpunkt ohne Authentifizierung bereitgestellt.\nValve Dossier zur Inkompetenz (43 KB) ↗Beweisarchiv ↗\nSicherheitsvorfall bei CEVA Logistics August 2026: Datenpanne mit personenbezogenen Kundendaten\nNamen, Adressen und Telefonnummern von Käufern des „European Steam Deck“ sind vom Logistikpartner von Valve durchgesickert und haben eine Welle von Phishing-Angriffen ausgelöst.\nEreignisprotokoll ↗Vollstreckungsprotokoll ↗\n\nAbtastartefakt: banned_100k_slice.csv (100,000 Konten). Ergebnisse der Prüfung: slice_100k_limited_results.csv. Vollständiger Analysebericht: BANNED_100K_FORENSIC_ANALYSIS.md.\n\n08 — Methode und Grenzen\nWie dies interpretiert wurde und was damit nicht behauptet wird\n\nDrei öffentliche Populationen, eine öffentliche API, strenge statistische Stichprobenahme.\n\nAUSFÜHRUNG & BEFUGNISSE\n\nDie ASF-Erhebung, das 100,000-Konto SRSWOR-Ausschnitt und die SteamRep-Gegenprüfung wurden von PhishDestroy Teilnehmern unter Verwendung ihrer eigenen Steam-Konten und Web-API-Schlüsseln im Rahmen der öffentlichen Arbeit der Koalition zur Bekämpfung von Phishing und Betrug durchgeführt. Der Verfasser dieses Dossiers verfügt über keinen Steam Web-API-Schlüssel und hat persönlich keinen Live-Scan durchgeführt. Die Aggregation, das Hashing, die Verifizierung und die Veröffentlichung erfolgten auf der Grundlage der Ergebnisse der Teilnehmer.\n\nBevölkerung\tWoher es stammt\tWas vorgelesen wurde\nASF-Mitglieder\n10,880,610\tDie öffentliche Mitgliederliste der Community-Gruppe ArchiSteamFarm Steam. Auf der Gruppenseite von Steam werden 5,360,499 Mitglieder angezeigt (nur nicht eingeschränkte); die API-Mitgliederliste lieferte insgesamt 10,880,610 Einträge, einschließlich eingeschränkter Konten. Die Gruppe wird beim ersten Start automatisch beitreten, es sei denn, der Benutzer deaktiviert die Standardeinstellung für den Gruppenbeitritt in der Konfiguration ausdrücklich (AutoJoinSteamGroup / Statistik), was bedeutet, dass die Mitgliederliste kommerzielle Bot-Cluster, einzelne „Card-Idler“ und reguläre Spieler umfasst, die die Standardoption aktiviert gelassen haben.\tGetPlayerBans für jedes Mitglied (Sperrmarkierungen); GetPlayerSummaries nach Erstellungsdatum und Land. In Chargen zu je 100 IDs zusammengefasst, anhand der SteamID64 dedupliziert.\n100.000 gesperrte Konten SRSWOR Slice\n100,000\tEine repräsentative Stichprobe, die gleichmäßig nach dem Zufallsprinzip ohne Zurücklegen aus dem Korpus der 1,182,811 gesperrten Konten gezogen wurde ($P = 8,45\\%$). Die Korrektur für endliche Grundgesamtheiten ergibt eine Fehlermarge von $\\pm 0,39\\%$ bei einem Konfidenzniveau von 99% ($Z = 2,576$).\tMonetarisierung und Status „Eingeschränktes Konto“ (isLimitedAccount) geprüft über die veraltete XML-Profil-Schnittstelle von Steam (?xml=1) über verteilte Proxy-Pipelines. Bestätigt den Status „63.06% bezahlt“.\nSteamRep Betrüger\n51,732\tVollständige 100% Erfassung aller Profile, die in der SteamRep Community-Reputationsdatenbank als „BANNED“ gekennzeichnet sind (insgesamt 51,732 Profile). Es wurde keine Stichprobenauswahl oder Filterung vorgenommen.\tISteamUser/GetPlayerBans/v1 für alle 51,732-Konten, in einer Kreuztabelle mit dem Status SteamRep. Bestätigt, dass 67.77% frei von jeglichen Sperren wegen Betrugs ist.\nWas beansprucht wird\n\nAusschließlich empirische Werte und statistisch begrenzte Schätzungen. In der Automatisierungsgruppe unterliegen 88.97% keiner Sperre; die gesperrte Teilmenge konzentriert sich auf die jüngere Vergangenheit (70% seit 2020). Bei der empirischen Überprüfung der 100,000-Konten sind 63.06% der gesperrten Konten kostenpflichtig (nicht beschränkt), wobei die mathematisch nachgewiesene Fehlerquote unter ±0.4% liegt. Unter den 51,732 bestätigten Betrügern unterliegen 67.77% keiner betrugsrelevanten Sperre. Jede Zahl lässt sich über die eigene Web-API von Valve reproduzieren.\n\nWas nicht beansprucht wird\n\nEine Steam-Sperre enthält kein Feld für die Angabe eines Grundes, daher wird hier keine Sperre einem bestimmten Grund zugeordnet. Die Gruppenzugehörigkeit ist kein Beweis dafür, dass es sich bei einem Konto um einen automatisierten Bot handelt: Da ASF standardmäßig den Beitritt zu Gruppen ermöglicht, sofern diese Option nicht manuell deaktiviert wird, vermischt sich die Nutzerbasis aus kommerziellen Multi-Account-Farmen mit privaten Konten gewöhnlicher Spieler und Hobby-Spieler. Die Angabe zum Land erfolgt auf eigene Angabe, und eine „0“-Eintragung ist eine Entscheidung der Community, kein gerichtliches Urteil. Es werden keine Namen genannt.\n\nWarum das wichtig ist\n\nValve verfügt über dieselbe API, eine eigene Datenbank im Hintergrund sowie die Sperrgründe, die dieser Scan nicht erkennen kann. Es kann diese Abfrage innerhalb von Sekunden über den gesamten ID-Bereich ausführen. Die Messgröße, mit der eine externe Partei eine Durchsetzungsbehauptung in Bezug auf eine Nummer überprüfen kann, wurde von der einzigen Partei, die sie in voller Genauigkeit liefern kann, nie veröffentlicht. Dies ist eine externe Schätzung, die angegeben wird, damit die Frage mit einer Zahl untermauert werden kann.\n\nWeiterlesen: die Kartenwirtschaft, die diese Bevölkerungsgruppe betreibt → · Zugriff und Diebstahl → · das vollständige Dossier →",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Wie groß ist die Steam-Farm? Wir haben selbst nachgezählt."
          },
          {
            "level": 2,
            "id": null,
            "text": "Zehn Millionen Konten, von denen neun von zehn unberührt sind"
          },
          {
            "level": 3,
            "id": null,
            "text": "ASF schließt sich der Gruppe für dich an"
          },
          {
            "level": 3,
            "id": null,
            "text": "10,880,610 Einträge insgesamt"
          },
          {
            "level": 3,
            "id": null,
            "text": "88.97% sauber"
          },
          {
            "level": 3,
            "id": null,
            "text": "Von den 10,880,610 Konten: Wie viele Valve wurden berührt?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Was diese Flotte bereits für ihre Existenz bezahlt hat: Valve"
          },
          {
            "level": 2,
            "id": null,
            "text": "Wo die Flotte beheimatet ist"
          },
          {
            "level": 3,
            "id": null,
            "text": "Gesperrte Konten nach angegebenem Land"
          },
          {
            "level": 2,
            "id": null,
            "text": "Aktuelle Aufträge, kein Altbestand"
          },
          {
            "level": 3,
            "id": null,
            "text": "Als die gesperrten Konten angelegt wurden"
          },
          {
            "level": 2,
            "id": null,
            "text": "Wenn Valve wirkt, wirkt es innerhalb des ersten Jahres"
          },
          {
            "level": 3,
            "id": null,
            "text": "Wie alt war der Account, als die Sperre verhängt wurde?"
          },
          {
            "level": 2,
            "id": null,
            "text": "Wenn Valve aktiv wird, stoppt es den Bot nicht"
          },
          {
            "level": 3,
            "id": null,
            "text": "Wofür genau die 11%, die gesperrt wurden, eigentlich gesperrt wurden"
          },
          {
            "level": 2,
            "id": null,
            "text": "Die Betrüger Valve lassen uns gehen: Die 51,732 vollständige Volkszählung"
          },
          {
            "level": 3,
            "id": null,
            "text": "Bestätigte Betrüger, je nachdem, ob Valve eine betrugsbezogene Sperre verhängt hat (vollständige Erfassung)"
          },
          {
            "level": 4,
            "id": null,
            "text": "Zwei Populationen, ein Befund"
          },
          {
            "level": 2,
            "id": null,
            "text": "Die empirische Untersuchung zu 100,000-Konten: Botnetze sind keine kostenlosen Einwegkonten"
          },
          {
            "level": 3,
            "id": null,
            "text": "100,000 Unvoreingenommener Ausschnitt"
          },
          {
            "level": 3,
            "id": null,
            "text": "Fehlergrenze < ±0.4%"
          },
          {
            "level": 3,
            "id": null,
            "text": "Warum jede 100.000 immer dasselbe ergibt"
          },
          {
            "level": 3,
            "id": null,
            "text": "100,000 Gesperrte Konten: Bezahlte Konten ($5+ Ausgaben im Store) vs. kostenlose Konten mit eingeschränktem Status"
          },
          {
            "level": 3,
            "id": null,
            "text": "Die strukturelle Realität: Kontoschließungen im industriellen Maßstab"
          },
          {
            "level": 2,
            "id": null,
            "text": "Wie dies interpretiert wurde und was damit nicht behauptet wird"
          },
          {
            "level": 3,
            "id": null,
            "text": "Was beansprucht wird"
          },
          {
            "level": 3,
            "id": null,
            "text": "Was nicht beansprucht wird"
          },
          {
            "level": 3,
            "id": null,
            "text": "Warum das wichtig ist"
          }
        ],
        "links": [
          "https://help.steampowered.com/en/faqs/view/71D3-35C2-AD96-AA3A",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/asf-ban-census-2026-09-23.json",
          "https://phishdestroy.io/steam_dossier/de/VALVE_EVIDENCE_PACK/databases/steamrep_steam_bans.csv",
          "https://phishdestroy.io/live-intel/?category=steam",
          "https://phishdestroy.io/steam_dossier/de/card_economy.html",
          "https://phishdestroy.io/steam_dossier/de/VALVE_EVIDENCE_PACK/databases/banned_archiasf_massive.csv",
          "https://phishdestroy.io/steam_dossier/de/VALVE_EVIDENCE_PACK/databases/slice_100k_limited_results.csv",
          "https://phishdestroy.io/steam_dossier/de/VALVE_EVIDENCE_PACK/reports/BANNED_100K_FORENSIC_ANALYSIS.md",
          "https://phishdestroy.io/steam_dossier/de/VALVE_EVIDENCE_PACK/databases/banned_100k_slice.csv",
          "https://phishdestroy.io/steam_dossier/de/VALVE_EVIDENCE_PACK/reports/STEAM_BANNED_LIMIT_ANALYSIS.md",
          "https://phishdestroy.io/steam_dossier/de/VALVE_EVIDENCE_PACK/INVESTIGATION_OVERVIEW.md",
          "https://phishdestroy.io/steam_dossier/de/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/de/VALVE_EVIDENCE_PACK/reports/STEAMREP_VS_STEAM_AUDIT.md",
          "https://phishdestroy.io/steam_dossier/de/VALVE_EVIDENCE_PACK/databases/SteamRep_Profiles_BannedCaution_2024.csv",
          "https://phishdestroy.io/steam_dossier/de/security_timeline.html",
          "https://phishdestroy.io/steam_dossier/de/VALVE_EVIDENCE_PACK/reports/russian_conflicts_report.json",
          "https://phishdestroy.io/steam_dossier/de/VALVE_EVIDENCE_PACK/reports/classification_report.json",
          "https://phishdestroy.io/steam_dossier/de/VALVE_EVIDENCE_PACK/reports/VALVE_INCOMPETENCE_REPORT.md",
          "https://phishdestroy.io/steam_dossier/de/steam_evidence_archive.html",
          "https://phishdestroy.io/steam_dossier/de/steam_enforcement_evidence.html",
          "https://phishdestroy.io/steam_dossier/de/#insider-threat",
          "https://phishdestroy.io/steam_dossier/de/"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/de/enforcement_audit.content.json",
      "export_json_sha256": "3abd114072a8a3242c47a5e8d548f63b76665cf0a9cd2803614641a1c686d08b"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "de/index.html",
      "language": "de",
      "title": "Das Steam-Dossier: Regeln, Wege und Verantwortlichkeit",
      "source_url": "https://phishdestroy.io/steam_dossier/de/index",
      "source_html_sha256": "83d7971d006387a55887dd1931173f11b003cfbac5f0cb88daf624a816e642e3",
      "exported_at": "2026-09-29T00:16:11.305Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "exhibit-gallery-section",
            "source": "https://phishdestroy.io/steam_dossier/de/index#exhibit-gallery-section"
          }
        ],
        "raster_images_replaced": 2
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "index.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/de/index.pdf?v=print-20260929-v5",
        "sha256": "a048010fc328411569f7df0970241e3bf791cebfa7e73371a91ed86f199a95b4",
        "bytes": 1004092,
        "pages": 112
      },
      "integrity": {
        "signed_object": "index.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "index.content.json.asc",
        "digest_file": "index.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify index.content.json.asc index.content.json",
          "sha256sum -c index.content.json.sha256"
        ]
      },
      "content": {
        "text": "Abschnitt 1 – Fallzusammenfassung\nDie Regel. Der Rekord. Die offenen Fragen.\nKontext und Quellenbeschränkungen\n\nSechs Feststellungen, die jeweils mit einem datierten öffentlichen Dokument verknüpft sind. Die einzelnen Abschnitte folgen derselben Reihenfolge: Technische Unterlagen (Teil A), Vorschriften und Durchsetzungsmaßnahmen (Teil B), rechtliche Rahmenbedingungen (Teil C) sowie die Anhänge mit den wichtigsten Anlagen.\n\nSechs Erkenntnisse. Jede davon verknüpft eine schriftliche Regel mit einer datierten Aufzeichnung und einer Frage, die anhand der Beweislage überprüft werden kann.\n\n1. Authentifizierungshosts mit separaten Domänen – 44 Routen · 26 geteilte Paare\n\nDie Aufzeichnungen im Live-Register 44 Plattformen, die sich über eine separate, registrierbare Domain authentifizieren. Fünf weitere Routen befinden sich in der ausstehenden Überprüfung und warten auf einen RDAP-Termin; würden diese hinzugefügt, würde sich die Gesamtzahl auf 47 erhöhen. Sie sind in der Zahl 44 und in der Altersübersicht nicht enthalten. — 27 mit einer veröffentlichten Nachweisdatei pro Route sowie 17 aus der manuellen Erfassung hinzugefügte, die separat aufgeführt sind. In 26 Filter-Split-Paare Die Hauptdomain lautet GESPERRT im Steam-Linkfilter, während der Proxy, der diese Anmeldedaten überträgt, nicht blockiert ist. Es handelt sich hierbei nicht um Wegwerf-Domains: csgogem.com ist blockiert, während api.csgem.com, der Host mit der Kennung Steam, ist seit März 2014 registriert — 12 Jahre und 6 Monate. Valve empfängt diesen Hostnamen bei jeder OpenID-Anfrage und zeigt ihn dem Nutzer auf seiner eigenen Anmeldeseite an. Die vollständige Tabelle mit den Altersangaben pro Route und den Herkunftsangaben findet sich in Abschnitt 3.\n\nDer Route folgen →\n2. 2016: Der Mechanismus wurde benannt, die Frist festgelegt\n\nAm 13. Juli 2016 beschrieb Valve öffentlich, wie Glücksspielseiten Steam OpenID und automatisierte Handelskonten nutzten, und in den Mitteilungen seines Rechtsbeistands vom 20. Juli 2016 wurde eine Frist von zehn Tagen gesetzt. Seitdem wurde keine Aufstellung der Durchsetzungsmaßnahmen nach Betreibern veröffentlicht. Zehn Jahre nach Ablauf dieser Frist wird derselbe benannte Mechanismus auf Authentifizierungs-Hosts mit separaten Domains verwendet, die am 2026-09-21 keine Blockierung durch den Link-Filter zurückgaben.\n\nLesen Sie den offenen Brief an die WSGC →\n3. Geräteabgleich, auf Briefpapier der Kanzlei\n\nIn dem hier wiedergegebenen Schriftwechsel beschrieb der Rechtsbeistand von Valve eine Korrelation auf Geräteebene, bei der ein Gerät mit mehreren Konten verknüpft wird – eine Funktion, von der der Steam-Support den Nutzern zuvor mitgeteilt hatte, dass sie technisch nicht möglich sei. Die offene Frage ist, welche Daten auf Geräteebene Valve besitzt und auf welcher Grundlage den Kontoinhabern der Zugriff darauf verweigert wird.\n\nLesen Sie das Memorandum →\n4. Zwei Reaktionen auf die Zugangsanfrage. In einem Fall wurden die Daten zurückgehalten, im anderen wurden sie weitergegeben.\n\nOktober 2025: Der Anwalt von Valve antwortete auf ein Ersuchen gemäß § 15 mit einem 830-seitigen Anhang, in dem die Schwärzungen über den Text gemalt wurden, anstatt ihn zu entfernen — 902,270 Zeichen mit einem Standard-Extraktionswerkzeug wiederherzustellen, einschließlich der Identifikatoren von Drittanbietern, die durch die Sperrstriche verborgen werden sollten. Art. 15 Abs. 4 ist der Grund für das Vorhandensein dieser Sperrstriche. September 2026: Das Ticket HT-2YBP-F7JP-D4VB wurde nach drei Tagen mit einem Link zur Self-Service-Seite „Kontodaten“ geschlossen – ohne Angaben zu den Daten und ohne Angabe einer Rechtsgrundlage. Die einmonatige Frist gemäß Art. 12 Abs. 3 war zum Zeitpunkt der Veröffentlichung noch nicht abgelaufen; der Einspruch bezieht sich auf den Sachverhalt.\n\nLesen Sie die Überprüfung der Redaktion →Ticket-Eintrag lesen →\n5. Der Markt oberhalb der Obergrenze von Steam\n\nSteam begrenzt die Marktkapitalisierung auf etwa $1,800. Auf fünf Marktplätzen in einer veralteten Momentaufnahme (23. September 2026), 248 CS2-Artikelkategorien von zwei oder mehr von ihnen unabhängig voneinander über dieser Obergrenze angeboten werden, und Alle 248 fehlen in Steam; ein fabrikneues „Dragon Lore“-Exemplar kostet ab $10,941 über 389 Exemplare, die in allen fünf Listen aufgeführt sind (die Zahl für „CSFloat“ allein in Abschnitt 13, basierend auf dem Snapshot vom 20. September, beträgt $10,623.95 bei 62 Angeboten). Der Verkauf zu diesen Preisen erfordert eine externe Handelsplattform, während die Artikelübertragung weiterhin über Steam läuft.\n\nPreisentwicklung verfolgen und Überweisung vornehmen →\n6. Die Regel ist eindeutig; der Prüfpfad ist es nicht.\n\nDie Nutzungsvereinbarung behält Steam für den persönlichen, nichtkommerziellen Gebrauch vor, untersagt die kommerzielle Nutzung, sofern dies nicht ausdrücklich gestattet ist, verbietet Skripte und Bots und erlaubt die Kündigung des Kontos. Valve hat diese Bestimmungen im Jahr 2016 auf Glücksspielanbieter angewendet. Unabhängig davon wurde laut dem Entwickler-Account von CSFloat Valve geschlossen IEconItems_730/GetPlayerItems im Jahr 2017, wodurch der öffentliche Zugriff auf die IDs der Originalelemente aufgehoben wurde (kein Valve-Änderungsprotokoll gefunden).\n\nLege die Regel neben das Netzwerk →\n2016 / Schriftliche Aufforderung 10 Tage\nFrist gemäß den Mitteilungen der Valve-Anwälte an Glücksspielseiten vom Juli 2016. Offener Brief an die WSGC: Abschnitt 2.\n2017 / Öffentlicher Prüfpfad Zugang per Ausweis gesperrt\nCSFloat protokolliert den Verlust von ursprünglichen Artikel-IDs.\nKorrespondenz mit dem Rechtsbeistand Gerätekorrelation\nEin Gerät, das mit Dutzenden gestohlener Konten in Verbindung steht.\nStreckenverzeichnis Gesperrt, aber weiterhin beim Einloggen\nDie Regel: Die Erklärung von Valve aus dem Jahr 2016 verbietet den Betrieb eines Glücksspielunternehmens auf Steam OpenID. Die Bilanz: Im Link-Filter sind 26 Hauptdomains hinterlegt, während der Host, auf dem jeweils die Steam-Anmeldung läuft, bereits seit — im Fall von csgogem.com seit 12 Jahren und 6 Monaten – in Betrieb ist.\nAbschnitt 2 – Offener Brief\nOffener Brief an die Glücksspielkommission des Bundesstaates Washington\n\nAus zehn Tagen wurden zehn Jahre. Die Anfrage der Kommission aus dem Jahr 2016 an Valve wurde nicht mit einer Aufstellung nach einzelnen Betreibern beantwortet; in diesem Schreiben wird die Kommission gebeten, die Akte wieder aufzunehmen.\n\nÖFFENTLICHE MITTEILUNG · GLÜCKSSPIELKOMMISSION DES BUNDESSTAATES WASHINGTON\n\nAus zehn Tagen wurden zehn Jahre.Öffnen Sie den Datensatz erneut.\n\nAn die Glücksspielkommission des Bundesstaates Washington:\n\nIm Jahr 2016 forderte Direktor David Trujillo Valve auf, darzulegen, welche Maßnahmen das Unternehmen ergriffen hatte, um die Nutzung von Steam-Skins für Glücksspiele zu unterbinden. Der damalige Vorsitzende Chris Stearns und die Kommission sahen sich einer Branche gegenüber, die auf von Valve ausgegebenen Gegenständen und Steam-Transfers basierte. Beide Männer haben inzwischen ihre Ämter in der Kommission niedergelegt. Die Frage, die sie an Valve gerichtet hatten, ist noch nicht hinfällig.\n\nDer Justiziar von Valve, Karl Quackenbush, räumte den Glücksspielanbietern eine Frist von zehn Tagen ein, um die kommerzielle Nutzung von Steam-Konten einzustellen. In seiner Antwort an Ihre Kommission vom Oktober bestritt Valve, Glücksspiele zu ermöglichen, gab an, Unterlassungsaufforderungen an mehr als vierzig Websites verschickt zu haben, und erklärte, die damit verbundenen Konten deaktiviert zu haben. Das Unternehmen verteidigte zudem die Beibehaltung von Steam-Handel und OpenID, da diese Dienste Kunden und Spieleentwicklern zugutekämen. Das war ein Machtbeweis. Das verdient eine Überprüfung, keine Unterwürfigkeit.\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\nUnserer Einschätzung nach hat die Antwort von Valve nicht gezeigt, dass die gewählten Durchsetzungsmaßnahmen dem Umfang des beschriebenen Netzwerks angemessen waren. Ein Drohbrief an einen Betreiber ist nicht dasselbe wie eine dauerhafte Sperrung der Steam-Konten, der Handelsinfrastruktur und der Authentifizierungswege, die das Geschäft erst möglich machen. Gemäß den gemeldeten Schätzungen belaufen sich Allein die CS:GO Lounge verzeichnete im Jahr 2016 ein Wettvolumen von über $1 Milliarden; dabei handelt es sich um eine externe Schätzung der Einsätze, nicht um Einnahmen in Höhe von Valve, und der ursprüngliche „Skin-Betting“-Betrieb der Website wurde später eingestellt. Das Ausmaß machte eine nachprüfbare Durchsetzung unerlässlich.\n\nHeute, Valves eigene Abonnentenvertrag archiviert 2026-09-21 ↗ schränkt die kommerzielle Nutzung ein, sofern dies nicht ausdrücklich gestattet ist, und verbietet darüber hinaus ausdrücklich bestimmte Formen der Automatisierung. Unsere veraltetes Streckenverzeichnis Einträge, die OpenID-Return-Hosts für externe Dienste angeben; openid.realm und openid.return_to sind Felder, die an Steam gesendet werden, und keine Geheimnisse, die vor ihm verborgen bleiben. Unsere Link-Filter-Prüfungen zeigt Fälle, in denen vor einer Hauptadresse gewarnt wurde, ein zugehöriger Anmeldehost jedoch nicht. Ein Filterergebnis allein kann nicht beweisen, dass Valve eine Anmeldung zugelassen hat oder dass ein bestimmter Bot eine Kontosperre umgangen hat. Dies beweist, dass eine Warnung auf der Startseite nicht als vollständige Antwort in Bezug auf den Zugang herangezogen werden kann.\n\nAuch die Existenz nützlicher, rechtmäßiger Steam-Handels- und OpenID-Funktionen gibt keinen Aufschluss darüber, ob verbotene Betreiber tatsächlich ausgeschlossen wurden. Die eigenen Regeln von Valve lassen ausdrückliche Ausnahmen zu. Sollte sich Valve auf diese Unterscheidung stützen, sollte die Kommission das Unternehmen auffordern, die für kommerzielle Skin-Unternehmen geltenden Genehmigungs-, Kontokontroll- und Durchsetzungskriterien sowie die spezifischen, nicht dem Glücksspiel dienenden Verwendungszwecke anzugeben, auf die es sich im Jahr 2016 berufen hat. Die bloße Möglichkeit einer rechtmäßigen Nutzung ist keine Antwort auf nachgewiesene verbotene Nutzung.\n\nWir bitten die Kommission, ihre Akte aus dem Jahr 2016 erneut zu prüfen und eine Aufstellung nach einzelnen Betreibern anzufordern: Welche Steam-Konten und Trading-Bots wurden nach den zehntägigen Fristsetzungen deaktiviert; ob verbundene Konten oder Return-Hosts überwacht wurden; welche Betreiber später wieder Zugang erhielten; welche Ausnahmegenehmigungen erteilt wurden; und welche Unterlagen die Aussage von Valve gegenüber der Kommission stützen. Veröffentlichen Sie alles, was nach geltendem Recht der Öffentlichkeit zur Einsichtnahme zusteht. Vergleichen Sie diese Unterlagen mit den aktuellen Routen und mit den späteren Eingriffen von Valve, einschließlich OPSkins im Jahr 2018 archiviert 2026-03-07 ↗.\n\nIn der Mitteilung wurde im Juli 2016 eine Frist von zehn Tagen gesetzt; zehn Jahre sind lang genug, um festzustellen, ob dies umgesetzt wurde. Die Kommission sollte den Bericht von Valve aus dem Jahr 2016 anhand der Infrastruktur überprüfen, die heute noch nachweisbar ist.\n\nDie Steam-Dossier-Untersuchung · Öffentliche Erklärung, 20. September 2026\n\nBekanntmachung der Kommission von 2016 ↗ archiviert 2026-05-20 ↗ · Antwort von Valve aus dem Jahr 2016 (Kopie des Dokuments) ↗ · Valves OpenID-Erklärung aus dem Jahr 2016 ↗ archiviert 2026-09-21 ↗ · Aktuelle Steam Vereinbarung ↗ archiviert 2026-09-21 ↗ · Zeitachse des Austauschs im Jahr 2016: Abschnitt 11 →\n\nTeil A – Technische Unterlagen · Abschnitt 3\nDie Website ist gesperrt. Die Anmeldeseite ist es nicht.\n\n26 gesperrte Hauptdomains. Der Authentifizierungs-Proxy hinter jeder einzelnen Domain und wie lange dieser bereits aktiv ist. Diese separaten Auth-Hosts sind keine zufälligen Zweitadressen – jeder einzelne ist ein Authentifizierungs-Proxy für Steam, der zwischen dem Plattform-Endpunkt und dem OpenID-Endpunkt von Valve steht und die Anmeldung übernimmt, die die gesperrte Domain nicht mehr offen durchführen kann. Valve hat den Link-Filter als „Haustür“ eingerichtet. Die Anmeldung lief weiterhin über den Proxy: csgogem.com ist gesperrt, und api.csgem.com ist seit März 2014 registriert — zwölfeinhalb Jahre. An jedem dieser Tage sendete der jeweilige Host seinen eigenen Hostnamen an den OpenID-Endpunkt von Valve, und Steam zeigte ihn dem Nutzer auf der Anmeldeseite direkt wieder an. Valve ist der Stamm, durch den jede dieser Routen verläuft; er muss sie nicht finden. Genau das wird in diesem Abschnitt gemessen: nicht, ob eine Warnung vorliegt, sondern wie viele Jahre die Strecke hinter der Warnung befahrbar bleibt. Im Register sind 44 Strecken mit getrennten Domänen verzeichnet, von denen für 27 eine nach Strecken aufgeschlüsselte Belegdatei veröffentlicht wurde – siehe die Tabelle unten. Schauen Sie sich zunächst ein Beispiel an und messen Sie dann alle.\n\nAbbildung 3.1 – Die beiden Routen, grafisch dargestellt.\n\nEine Plattform, ein Nutzer, zwei Anfragen, die denselben Browser verlassen. Der Link-Filter von Valve greift bei beiden an. Er blockiert die Anfrage, die einen Link enthält, und lässt die Anfrage durch, die die Anmeldedaten enthält. Alle in diesem Abschnitt gemessenen Werte geben an, wie lange die untere Route offen bleibt.\n\nThe player\none browser, one session\nrollbit.com\nthe platform's main domain\nrbsnin.com\nseparate authentication host\nLINK FILTER\n✕ BLOCKED\nLINK FILTER\n✓ CLEAN\nsteamcommunity.com\nOpenID endpoint · signs in\nno route\nLink gepostet am Steam — beendetAnmeldeanfrage – PässeAufbewahrte Schecks vom 19. und 21. September 2026\n\nBeide Anfragen sind für Valve sichtbar, und es wird nur eine davon bearbeitet. Der Link-Filter ist eine Valve-Liste, die von einem Valve-Dienst überprüft wird. Die OpenID-Anfrage übermittelt den eigenen Namen des Authentifizierungshosts an den Endpunkt von Valve, der ihn direkt auf der Anmeldeseite anzeigt. Der Hostname ist in jedem Fall in der Anfrage enthalten – der Unterschied besteht darin, ob damit etwas unternommen wird.\n\nEin Bahnsteig. Zwei verschiedene Strecken.ROLLBIT / GESPEICHERTE BEOBACHTUNGEN\nSchritt 5 / 5\n\nDie Anfrage erreicht Steam. Der beobachtete Pfad führte zum Anmeldeformular von Steam. Die Autoren haben die Anmeldung nicht abgeschlossen. Das Blockieren des Links zur Hauptdomain hat diesen beobachteten Pfad zum Formular nicht blockiert.\n\n01 DIE PRÜFUNG DES LINKFILTERS\nREISEZIELrollbit.comDie Hauptdomain der Plattform\nDAMPF-VERBINDUNGSFILTERÜberprüft den LinkEin eigenständiges Zielwarnsystem\nGESPEICHERTES ERGEBNISLink gesperrt19. und 21. September 2026\n02 DER BEOBACHTETE ANMELDEABLAUF\nAUF DEM PERRONMit Steam anmeldenDie Plattform initiiert eine OpenID-Anfrage\nSEPARATER AUTH-HOSTrbsnin.comKein „Link-Filter“-Block in der gespeicherten Prüfung\nSTEAMAnmeldeformular wurde bereitgestelltDer angeforderte Host erscheint in der Meldung von Steam\nÜberprüfen Sie die ursprünglichen Erfassungsnotizen, das Registrierungsdatum und die Protokolldaten\nSo sieht die Durchsetzung von Valve aus\nHauptdomain: gesperrt\nBenutzer\n→\nrollbit.com\n(Hauptdomain)\n↓\nSTEAM-LINK-FILTER – GESPERRT\n„Link gesperrt!“ – als potenziell schädlich gekennzeichnet\nrollbit.com hat bei 2026-09-19 und 2026-09-21 eine Blockierung durch den Link-Filter zurückgegeben (Prüfung ohne Authentifizierung; Roh-HTML und SHA-256 gespeichert). Ein sichtbarer, nachvollziehbarer Datensatz.\nWas tatsächlich passiert – Authentifizierung\nAuth-Host: nicht gesperrt\nBenutzer\n→\nrollbit.com\n„Mit Steam anmelden“\n↓\nWeiterleitung über einen separaten Authentifizierungshost:\nrbsnin.comLink-Filter: CLEAN\nregistriert 2026-09-18T09:34:52Z (Verisign RDAP)\n↓\nSteam Hinweis auf der Anmeldeseite (2026-09-20):\n\"Note that rbsnin.com is not affiliated with Steam or Valve\"\nSteam gibt diesen Hinweis aus dem „openid.realm“ der empfangenen Anfrage aus.\n↓\nSteam Anmeldeformular, das für den separaten Host bereitgestellt wird\nDie Autoren haben die Anmeldung nicht abgeschlossen; der Ablauf wurde bis zum Formular „Steam“ beobachtet.\nValve erhält bei jeder solchen Anfrage den Hostnamen „return_to / realm“. rbsnin.com hat bei 2026-09-21 keine Sperre durch den Link-Filter zurückgegeben.\nAuf Anfrage\nAls OpenID-Anbieter erhält Steam bei jeder Authentifizierungsanfrage den Auth-Hostnamen: Dieser trifft auf den eigenen Servern von Valve in der openid.return_to und openid.realm Parameter.\nVon der Website gesendet\nDer Authentifizierungshost wird beim Scan nicht ermittelt – die Plattform übermittelt ihn in jeder Anfrage an Steam. Gemäß OpenID 2.0 §9.1 return_to ist formal optional, aber ohne diese Angabe kann Steam das Anmeldeergebnis nicht ausgeben; für eine funktionierende Steam-Anmeldung ist sie daher faktisch erforderlich. Steam zeigt dem Benutzer sogar den Hostnamen an („<host> steht in keiner Verbindung zu Steam oder Valve\").\n14 Jahre\nist das Alter des ältesten Auth-Hosts, der bei der 2026-09-21-Prüfung noch Steam Anmeldungen aufweist (dota2.net, registriert am 2011-10-29); der jüngste ist drei Tage alt (rbsnin.com). Die Zahl „0 gesperrte Authentifizierungshosts“ sollte nicht als Ergebnis gewertet werden. Ein gesperrter Authentifizierungshost würde die Funktion „Anmelden mit Steam“ der Plattform vollständig lahmlegen, daher kann ein aus funktionierenden Anmeldungen erstelltes Verzeichnis nur Hosts enthalten, die nie gesperrt wurden. Die aussagekräftige Zahl ist nicht die Anzahl der Sperrungen – es geht darum, wie viele Jahre die Hauptdomain im Link-Filter verbleibt, während die daneben liegende Anmeldung weiterhin funktioniert.\nAuthentifizierungshosts mit separaten Domänen: Registrierungsdatum im Vergleich zur Hauptdomäne (30 Routen: die 25, die im Browser-Audit 2026-09-21 aufgelöst wurden, sowie 5, die am 2026-09-22 hinzugefügt wurden)\nPlattform\tLink-Filter: Hauptseite\tAuth-Host\tLink-Filter: Authentifizierungshost\tAuth-Host registriert\tBeobachtungsquelle\tBeweismittelakte\nRollbit\nrollbit.com · Reg. 2014-11-08\n\tGESPERRT\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\trbsnin.com\tSAUBER\n2026-09-21 · reines HTML (kein Wayback-Snapshot)\n\t2026-09-18\n09:34:52Z, Verisign RDAP\n\tSteam Hinweis auf der Anmeldeseite, 2026-09-20\trollbit.com.json\nSkin.Club\nskin.club · Registrieren 2017-09-04\n\tGESPERRT\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\tsc-auth.net\tSAUBER\n2026-09-21 · Wayback 2026-09-21\n\t2019-04-02\nRDAP\n\tSteam Hinweis auf der Anmeldeseite\tskin.club.json\nHowl.GG\nhowl.gg · Registrieren 2017-03-16\n\tGESPERRT\n2026-09-18, 19.09., 21.09. · Wayback 2026-09-21\n\thowl.uno\tSAUBER\n2026-09-21 · Wayback 2026-09-21\n\t2026-08-11\nRDAP\n\tLive-Browser-Aufzeichnung + bereitgestellte OpenID-URL\thowl.gg.json\nDuelbits\nduelbits.com · registriert 2020-02-03\n\tGESPERRT\n2026-09-21 · Wayback 2026-09-21\n\tswitchflips.com\tSAUBER\n2026-09-21 · Wayback 2026-09-21\n\t2020-04-21\nRDAP\n\tAngegebene OpenID-URL\tduelbits.com.json\nCSGOFast\ncsgofast.com · registriert 2015-03-27\n\tGESPERRT\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\tsteam-login.authtofast.com\tSAUBER\nauthtofast.com, 2026-09-21 · Wayback 2026-09-21\n\t2026-06-30\nauthtofast.com, RDAP\n\tLive-Browser-Aufzeichnung + bereitgestellte OpenID-URL\tcsgofast.com.json\nFarmskins\nfarmskins.com · Reg. 2016-03-23\n\tGESPERRT\n2026-09-19, 2026-09-21 · reines HTML\n\tsteam.kobal.cc\tSAUBER\n2026-09-19, 2026-09-21 · reines HTML\n\t2017-01-07\nkobal.cc, RDAP\n\tLive-Browser-Aufzeichnung + bereitgestellte OpenID-URL\tfarmskins.com.json\nCobaltLab\ncobaltlab.tech\n\tGESPERRT\n2026-09-21 · reines HTML\n\tcobaltauth.com\tSAUBER\n2026-09-21 · reines HTML\n\t2025-01-07\nRDAP\n\tAngegebene OpenID-URL\tcobaltlab.tech.json\nCSGO.NET\ncsgo.net · registriert 2012-07-22\n\tGESPERRT\n2026-09-21 · reines HTML\n\tcn2.easylot.net\tSAUBER\n2026-09-21 · reines HTML\n\t2016-09-03\neasylot.net, RDAP\n\tLive-Aufzeichnung im Browser\tcsgo.net.json\nGGDrop\nggdrop.com\n\tGESPERRT\n2026-09-21 · reines HTML\n\tggauth.com\tSAUBER\n2026-09-21 · reines HTML\n\t2023-05-03\nRDAP\n\tAngegebene OpenID-URL\tggdrop.com.json\nRustChance\nrustchance.com\n\tGESPERRT\n2026-09-21 · reines HTML\n\thgfuihd.com\tSAUBER\n2026-09-21 · reines HTML\n\t2019-01-27\nRDAP\n\tAngegebene OpenID-URL\trustchance.com.json\nSkin.Fans\nskin.fans\n\tGESPERRT\n2026-09-21 · reines HTML\n\tauth.skinfans.com\tSAUBER\n2026-09-21 · reines HTML\n\t2018-07-16\nskinfans.com, RDAP\n\tAngegebene OpenID-URL\tskin.fans.json\nSkinport\nskinport.com · Registrieren 2018-09-05\n\tGESPERRT\n2026-09-21 · reines HTML\n\tskinport.app\tSAUBER\n2026-09-21 · reines HTML\n\t2020-06-20\nRDAP\n\tLive-Browser-Aufzeichnung + bereitgestellte OpenID-URL\tskinport.com.json\nSkins.Cash\nskins.cash\n\tGESPERRT\n2026-09-21 · reines HTML\n\tskinscash.live\tSAUBER\n2026-09-21 · reines HTML\n\t2019-12-05\nRDAP\n\tAngegebene OpenID-URL\tskins.cash.json\nTF2Hunt\ntf2hunt.com · Registriert 2018-01-13\n\tGESPERRT\n2026-09-21 · reines HTML\n\trstspcl.com\tSAUBER\n2026-09-21 · reines HTML\n\t2020-08-08\nRDAP\n\tLive-Browser-Aufzeichnung + bereitgestellte OpenID-URL\ttf2hunt.com.json\nCSGOGem\ncsgogem.com · registriert 2016-10-16\n\tGESPERRT\n2026-09-22 · reines HTML\n\tapi.csgem.com\ncsgem.com – separate, registrierbare Domain\n\tSAUBER\n2026-09-22 · reines HTML\n\t2014-03-08\ncsgem.com, RDAP – ältester Eintrag im Register\n\tManuelle Erfassung + Erfassung über den Link-Filter\tlinkfilter-2026-09-22.json\nGamdom\ngamdom.com · Registrieren 2016-07-29\n\tGESPERRT\n2026-09-22 · reines HTML\n\tlogin.gambldom.com\ngambldom.com – nur ein Buchstabe anders als die Marke\n\tSAUBER\n2026-09-22 · reines HTML\n\t2017-09-24\ngambldom.com, RDAP\n\tManuelle Erfassung + Erfassung über den Link-Filter\tlinkfilter-2026-09-22.json\n12CS\n12cs.fail · reg. 2026-03-24\n\tGESPERRT\n2026-09-22 · reines HTML\n\tfail.games\tSAUBER\n2026-09-22 · reines HTML\n\t2021-08-24\nfail.games, RDAP\n\tManuelle Erfassung + Erfassung über den Link-Filter\tlinkfilter-2026-09-22.json\nCSGOEmpire\ncsgoempire.com · registriert 2015-06-10\n\tSAUBER\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\tcsgoempirelogin4.com\neine von zehn nummerierten Domänen login1–10\n\tSAUBER\n2026-09-21 · Wayback 2026-09-21\n\t2020-07-20\n05:49:17Z, Verisign RDAP\n\tLive-Aufzeichnung im Browser\tcsgoempire.com.json\nCS.MONEY\ncs.money\n\tSAUBER\n2026-09-21 · reines HTML\n\tauth.dota.trade\tSAUBER\n2026-09-21 · reines HTML\n\t2016-07-15\ndota.trade, RDAP\n\tSteam Hinweis auf der Anmeldeseite\tcs.money.json\nCSFloat\ncsfloat.com · Reg. 2021-07-11\n\tSAUBER\n2026-09-21 · reines HTML\n\tcsgofloat.com\nEhemalige Markendomain des Betreibers; eigenständige, registrierbare Domain, kein Hinweis auf eine Umgehung\n\tSAUBER\n2026-09-21 · reines HTML\n\t2015-09-29\nRDAP\n\tLive-Aufzeichnung im Browser\tcsfloat.com.json\nG4Skins\ng4skins.com\n\tSAUBER\n2026-09-21 · reines HTML\n\tauth.g4s.to\tSAUBER\n2026-09-21 · reines HTML\n\t2021-05-30\ng4s.to, RDAP\n\tAngegebene OpenID-URL\tg4skins.com.json\nJuice.GG\njuice.gg\n\tSAUBER\n2026-09-21 · reines HTML\n\tletmeinjuice.com\tSAUBER\n2026-09-21 · reines HTML\n\t2024-04-15\nRDAP\n\tAngegebene OpenID-URL\tjuice.gg.json\nMarkt.CSGO\nmarket.csgo.com\n\tSAUBER\n2026-09-21 · reines HTML\n\tdota2.net\tSAUBER\n2026-09-21 · reines HTML\n\t2011-10-29\nRDAP\n\tLive-Browser-Aufzeichnung + bereitgestellte OpenID-URL\tmarket.csgo.com.json\nRust.TM\nrust.tm\n\tSAUBER\n2026-09-21 · reines HTML\n\tdota2.net\tSAUBER\n2026-09-21 · reines HTML\n\t2011-10-29\nRDAP\n\tAngegebene OpenID-URL\trust.tm.json\nCSGOLounge\ncsgolounge.com · Registriert 2013-08-14\n\tSAUBER\n2026-09-22 · reines HTML\n\tdota2.net\ndrittes Frontend auf diesem Authentifizierungshost\n\tSAUBER\n2026-09-22 · reines HTML\n\t2011-10-29\ndota2.net, RDAP\n\tManuelle Erfassung + Erfassung über den Link-Filter\tlinkfilter-2026-09-22.json\nDota2Lounge\ndota2lounge.com · Registriert 2012-08-10\n\tSAUBER\n2026-09-22 · reines HTML\n\tdota2.net\nviertes Frontend auf diesem Authentifizierungshost\n\tSAUBER\n2026-09-22 · reines HTML\n\t2011-10-29\ndota2.net, RDAP\n\tManuelle Erfassung + Erfassung über den Link-Filter\tlinkfilter-2026-09-22.json\nSkinBaron\nskinbaron.de\n\tSAUBER\n2026-09-21 · reines HTML\n\tskinbaron.com\ngleiche Marke, andere TLD\n\tSAUBER\n2026-09-21 · reines HTML\n\t2015-12-22\nRDAP\n\tAngegebene OpenID-URL\tskinbaron.de.json\nTF2Royal\ntf2royal.com · Registriert 2022-08-17\n\tSAUBER\n2026-09-21 · reines HTML\n\ttf2auth.com\tSAUBER\n2026-09-21 · reines HTML\n\t2021-07-27\nRDAP\n\tLive-Browser-Aufzeichnung + bereitgestellte OpenID-URL\ttf2royal.com.json\nTradeit\ntradeit.gg\n\tSAUBER\n2026-09-21 · reines HTML\n\tconnect-tradeit.com\tSAUBER\n2026-09-21 · reines HTML\n\t2022-02-23\nRDAP\n\tAngegebene OpenID-URL\ttradeit.gg.json\nUpgrader\nupgrader.pro\n\tSAUBER\n2026-09-21 · reines HTML\n\tupgauth.space\tSAUBER\n2026-09-21 · reines HTML\n\t2026-08-14\nRDAP\n\tAngegebene OpenID-URL\tupgrader.pro.json\nQuelle: steamcommunity.com/linkfilter, GET ohne Authentifizierung, 2026-09-21, 53 Hosts, 3 s Abstand; steam_tos_assets/linkfilter-recheck-2026-09-21.json; reines HTML in steam_tos_assets/linkfilter-raw/. Anmeldefristen: RDAP, steam_tos_assets/domain-registration.json. · Frühere Überprüfung von 2026-09-19 in linkfilter-all-results.json · Routendaten in auth-route-audit.json · Wayback-Machine-Momentaufnahmen der Link-Filter-Seiten, 2026-09-21, aufgeführt unter wayback-snapshots.json (Für rbsnin.com liegt kein Snapshot vor; die lokale Raw-Datei ist der einzige Datensatz).\n\nAnmeldefristen: RDAP (steam_tos_assets/domain-registry/). Die „bereitgestellte OpenID-URL“ legt lediglich die Anfrageparameter fest, stellt jedoch keine abgeschlossene Anmeldung dar. Die Autoren haben auf keiner Plattform eine Anmeldung abgeschlossen. Eine separate Domain ist für sich genommen kein Beweis für eine Umgehung. Auch „0 gesperrte Authentifizierungshosts“ ist kein eigenständiger Befund: Das Sperren eines solchen Hosts würde die Anmeldung auf dieser Plattform unterbrechen, sodass ein aus funktionierenden Anmeldungen zusammengestelltes Verzeichnis keinen gesperrten Authentifizierungshost enthalten kann. Aussagekräftig ist die Paarung und deren Dauer – eine Hauptdomain im Link-Filter neben einer Anmeldedomain, die seit Jahren besteht. Diese Tabelle umfasst 30 Zeilen: 25 der 27 Routen mit einer nach Routen geordneten Beweisdatei sowie fünf, die unter 2026-09-22 hinzugefügt wurden, deren Aufteilung im Link-Filter in linkfilter-2026-09-22.json obwohl die Daten selbst manuell erfasst wurden – das geht aus den Einträgen in der Spalte „Quelle“ hervor. Die beiden nicht dargestellten Pfade der Evidenzdateien sind skinsnipe.com (Authentifizierungshost pricing.tradeupspy.com, registriert unter 2020-03-11) und csgobig.com (Auth-Host letmeinbig.com, registriert 2023-01-20); beide lieferten bei der Überprüfung von 2026-09-22 das Ergebnis „BLOCKED main / CLEAN auth host“, aufgezeichnet mit SHA-256 in linkfilter-2026-09-22c.json, doch der Roh-HTML-Code für diesen Stapel ist nicht im veröffentlichten Datensatz enthalten, weshalb sie hier namentlich aufgeführt werden, anstatt eine Zeile zu erhalten, wie es bei jeder anderen Zeile in dieser Tabelle der Fall ist. Die verbleibenden 12 manuell erfassten Routen im Register sind als solche gekennzeichnet in master_registry.json unter realm_src: user.\n\nPrimäre empirische Prüfung · Mehrjähriger Zeitraum\nDie „Big Picture“-Falle: Der Link-Filter ist bloßes Compliance-Theater, kein Schutzschild\n\nIn Desktop-Browsern werden Nutzer durch externe Schutzmaßnahmen geschützt: Google Safe Browsing und Microsoft SmartScreen wehren bekannte Phishing-Angriffe mit roten Vollbild-Warnungen ab. Im „Big Picture“-Modus von Steam, im Overlay im Spiel (Umschalt+Tab) und im Steam-Deck (SteamOS) gibt es diese Schutzmaßnahmen nicht. Der integrierte Browser unterstützt keinerlei Erweiterungen, deaktiviert externe „Safe Browsing“-Engines und lässt dem Nutzer genau eine Schutzbarriere: die von Valve. linkfilter Zwischenraum.\n\nWischen, um alle vier Ergebnisse zu vergleichen →\n\n92.5%\n2025–2026: Modernes Edge-Phishing ohne Beanstandungen bestanden (37/40)\n77.5%\nPhishing in der CS2-Ära 2023–2024 ohne Beanstandungen bestanden (31/40)\n70.0%\nPhishing-Angriffe aus den Jahren 2021–2022 ohne Beanstandungen bestanden (28/40)\n7 / 7\nGlücksspiel-Hauptleitungen gesperrt (Positivkontrolle)\nMehrjährige Langzeituntersuchung: 120 reine Steam-Phishing-Domains live getestet (24. September 2026)\n\nUm zu prüfen, ob der Filter von Valve neue Bedrohungen lediglich langsam erfasst oder ihnen grundsätzlich blind gegenüber ist, haben wir eine Überprüfung durchgeführt 120 bestätigte Steam-spezifische Phishing-Domains über drei historische Kohorten hinweg im Vergleich zu steamcommunity.com/linkfilter:\n\nKohorte 1: 2021–2022 (Klassisches Tauschangebot & Item-Drops) — 70.0% Clean Pass (28/40). Selbst 4 bis 5 Jahre, nachdem sie von Community-Überwachungsinitiativen erfasst wurden, lassen sich 7 von 10 älteren Phishing-Hosts immer noch ungehindert aufrufen.\nKohorte 2: 2023–2024 (CS2-Beta-Hype & gefälschte Support-Anfragen) — 77.5% Clean Pass (31/40). Kampagnen, die sich als Veröffentlichungen von „Counter-Strike 2“ ausgeben, sowie gefälschte Aufrufe der Community (z. B. cs2-steam.com, appealsteamcommunity.help) gehen direkt hindurch.\nKohorte 3: 2025–2026 (Serverlose Edge-Bereitstellungen & Favicon-Klone) — 92.5% Voller Erfolg (37/40). Moderne Phishing-Kits, die auf EdgeOne, Vercel und Cloudflare Pages bereitgestellt werden (z. B. steamgifter.online, steam-dp4lt5b8fnez.edgeone.dev) praktisch ungehindert passieren.\n\nTelemetrie und Haftungsschutz – kein Schutz. Warum gibt es den Link-Filter, wenn er von 70% bis 92.5% reines Steam-Phishing durchlässt? Er dient als Haftungsausschluss für Unternehmen und als Sensor zur Erfassung ausgehender Klicks. Durch die höfliche Darstellung „Du verlässt Steam“ Hinweis mit einer anklickbaren grünen Schaltfläche „Weiter“; Valve verlagert die rechtliche Verantwortung gemäß dem Steam Abonnentenvertrag auf das Opfer (*„Der Nutzer hat Steam freiwillig verlassen“*). Valve erfasst die Telemetriedaten des Klicks, verhindert den Diebstahl jedoch nicht.\n\nDer Favicon-Hash-Nachweis: Keine Erfassung von Bedrohungs-Feeds. Unabhängige Plattformen für Bedrohungsinformationen (urlscan.io, Shodan, Censys) identifizieren aktive Steam-Phishing-Kits durch eine einfache Suche nach dem offiziellen Favicon-Hash von Steam (page.favicon.hash:9f890a9debcdfccc339149a7943be9aff9e4c9203c2fa37d5671a5b2c88503ad NOT domain:*.steampowered.com). Diese automatisierte Grundprüfung deckt aktive Phishing-Cluster innerhalb von Sekunden auf. Valve synchronisiert sich nicht mit externen Feeds, führt keine hashbasierte Bedrohungssuche durch und greift nur dann manuell ein, wenn dies von Aufsichtsbehörden vorgeschrieben wird (die WSGC-Verfügung zum Glücksspiel aus dem Jahr 2016) oder um seine markenrechtlich geschützten Domain-Strings zu schützen.\n\nPrimäre Prüfungsnachweise: Mehrjährige Längsschnittstudie mit 120 Domänen: longitudinal-steam-phishing-audit.json · 100 spezifische Steam-Phishing-Beispiele: linkfilter-steam-phishing-100.json · Umfassende Futtermittelprüfung (n = 250): linkfilter-coverage-2026-09-22.json.\n\nCSGOEmpire – Sammelregistrierung von zehn nummerierten Auth-Domains\n\nAm 2020-07-20 zehn nummerierte Domänen, csgoempirelogin1.com durch csgoempirelogin10.com, wurden registriert. Für alle zehn liegen Verisign-RDAP-Zeitstempel vor: login1 05:49:06Z, login5 05:49:08Z, login2 05:49:11Z, login3 05:49:14Z, login4 05:49:17Z, login6 05:49:20Z, login7 05:49:23Z, login8 05:49:26Z, login9 05:49:28Z — neun Domains in 22 Sekunden — und „login10“ um 05:56:03Z, sieben Minuten später. Der zeitliche Abstand passt zu einem einzigen Massenvorgang eines Registrars.\n\nDas Muster stimmt mit vorab bereitgestellten Fallback-Hosts überein; nur login4 Dies wurde bei einer Live-OpenID-Anfrage festgestellt. Sowohl csgoempire.com als auch csgoempirelogin4.com lieferten im Link-Filter den Status „CLEAN“ bei 2026-09-21; CSGOEmpire gehörte nicht zu den Websites, die in den Presseberichten zu den Mitteilungen vom Juli 2016 genannt wurden.\n\n# DNS – alle 10 aktiv (September 2026)\nOK csgoempirelogin1.com 172,67,129,43\nOK csgoempirelogin2.com 172,67,175,168\nOK csgoempirelogin3.com 188.114.96.3\nOK csgoempirelogin4.com 188.114.96.11 ← im OpenID-Datenverkehr\nOK csgoempirelogin5.com 172,67,160,194\nOK csgoempirelogin6–10.com Cloudflare-IP-Adressen\nNXDOMAIN: csgoempirelogin11.com\nAlle 10 registriert 2020-07-20; alle 10 mit RDAP-Zeitstempel versehen (steam_tos_assets/domain-registry/csgoempireloginN.com.rdap.json)\nSchlussfolgerung für die Regulierungsbehörden\nEine gesperrte Hauptdomain in Verbindung mit einem nicht gesperrten Auth-Host lässt die Anmelderoute offen – und diese bleibt über Jahre hinweg offen.\n\nDer Link-Filter-Block auf der Hauptdomäne ist ein überprüfbarer, öffentlicher Datensatz. Der Auth-Host überträgt den Datenverkehr „Anmelden mit Steam“ und erscheint in den OpenID-Anfrageparametern von Valve. Bei Überprüfungen von 2026-09-21 und 2026-09-22 gab die Hauptdomain in 26 Filter-Split-Paaren eine „Link Filter“-Sperre zurück, während der Proxy, der die Anmeldung übertrug, keine zurückgab. Die obige Auflistung erfasst die andere Hälfte davon: Bei diesen Hosts handelt es sich nicht um kurzlebige Wegwerf-Domains. Einige waren zum Zeitpunkt der Überprüfung bereits seit mehr als einem Jahrzehnt registriert, und jeder dieser Tage ist ein Tag, an dem Valve den Hostnamen in seinen eigenen Anfrageparametern erhalten hat. Valve hat keine Aufzeichnungen über die Durchsetzung pro Betreiber veröffentlicht, sodass anhand öffentlicher Daten nicht festgestellt werden kann, ob gegenüber diesen Hosts weitere Maßnahmen ergriffen wurden.\n\nWhat this means — the Steam Link Filter\n\nValve’s own blocklist for links leaving Steam. Click a listed address inside the client and an interstitial appears instead of the page. It acts on the link that is posted, not on the login a site performs, and it is the only such check that runs inside the Steam client.\n\nSection 3.1 — why it is the only layer →\n\n12 Jahre und 6 Monate\ncsgogem.com wird im Linkfilter blockiert.\nSein Anmeldehost api.csgem.com war\nist seit 2014-03-08 registriert und ist es nicht.\nZusammenfassung in einfacher Sprache – Für Aufsichtsbehörden und Gerichte (erweitern)\nZusammenfassung in einfacher Sprache – für Aufsichtsbehörden\nHintergrund: Was Steam ist und warum es hier von Bedeutung ist\n\nSteam ist eine Softwareplattform, die von der Valve Corporation (Bellevue, Washington, USA) betrieben wird. Steam fungiert als Anbieter digitaler Identitäten: Glücksspiel- und Gaming-Websites im Internet nutzen ein System namens „Anmelden mit Steam“ – eine Schaltfläche, über die eine Website überprüfen kann, ob ein Besucher über ein echtes Steam-Konto verfügt. Dies ähnelt der Funktion „Mit Google anmelden“ oder einer Überprüfung anhand eines amtlichen Ausweises: Die Website leitet den Nutzer zu den Servern von Steam weiter, Steam bestätigt dessen Identität und Steam leitet ihn zurück zur Website. Valve betreibt das Authentifizierungssystem. Jede einzelne Anmeldung über „Mit Steam anmelden“ läuft über die eigenen Server von Valve.\n\nWas Valve getan hat: Die Domain-Sperre\n\nIm Juli 2016 sandte der Rechtsbeistand von Valve infolge des medialen und rechtlichen Drucks im Zusammenhang mit „Skin-Glücksspielen“ Mahnungen an etwa 23 namentlich genannte Glücksspiel-Websites (laut Presseberichten vom 21. Juli 2016); im Oktober 2016 teilte Valve der Glücksspielkommission des Staates Washington mit, dass es mehr als vierzig Seiten kontaktiert habe. Einige Glücksspiel-Domains tauchen in der Steam Linkfilter — eine Liste, die bewirkt, dass bei jedem Link zu diesen Seiten, der innerhalb von Steam gepostet wird (im Chat, auf einer Profilseite, im Shop), eine Warnseite angezeigt wird: „Link gesperrt!“ Der Link-Filter ist die einzige Durchsetzungsmaßnahme, deren Wirkung von außerhalb von Valve beobachtet werden kann.\n\nBeispiel: Ein Link zu rollbit.com Im Bereich Steam wird die Warnseite des Link-Filters angezeigt (2026-09-19 und 2026-09-21 sind markiert). Theoretisch ist die Glücksspiel-Website gesperrt.\nWas ist eine Proxy-Domain?\n\nA Ein Auth-Host mit separater Domäne ist ein Authentifizierungsproxy.: eine zweite Website-Adresse auf einer anderen registrierbaren Domain, die derselbe Betreiber zwischen seine Nutzer und Steam schaltet, ausschließlich zu dem Zweck, den Schritt „Mit Steam anmelden“ durchzuführen. Sie fungiert als Proxy für die Anmeldung. Der Nutzer glaubt, sich bei der Plattform anzumelden; die Anfrage, die bei Valve eintrifft, enthält jedoch den Hostnamen des Proxys und nicht den der Plattform. In der Regel besteht keine öffentlich sichtbare Verbindung zur Glücksspiel-Website, und es ist diese Adresse, an die die Nutzer zurückgeleitet werden, nachdem Steam ihre Identität bestätigt hat.\n\nBeispiel: Rollbit wird betrieben unter rollbit.com, die vom Link-Filter blockiert wird. Bei der Authentifizierung auf Steam verwendete der auf 2026-09-20 beobachtete Datenfluss eine separate Adresse: rbsnin.com, registriert unter 2026-09-18. Diese Adresse wurde zurückgegeben kein Link-Filter-Block am 2026-09-21. Die Glücksspiel-Website war weiterhin in Betrieb, und ihr Steam-Anmeldeprozess lief über den nicht gesperrten Host.\nDer kritische Punkt: Der Auth-Host wird bei jeder Anfrage an Steam gesendet\n\nValve muss weder scannen noch crawlen, um zu ermitteln, welche Authentifizierungshosts verwendet werden. Steam ist der OpenID-Identitätsanbieter für diese Websites, und jeder Klick auf „Mit Steam anmelden“ sendet eine GET-Anfrage an die eigenen Server von Valve, die den Authentifizierungs-Hostnamen im Klartext enthält. Gemäß OpenID 2.0 §9.1 gilt die return_to Das Feld ist formal optional, aber ohne dieses Feld kann Steam das Anmeldeergebnis nicht ausgeben; für eine funktionierende Steam-Anmeldung ist es daher praktisch erforderlich. Steam selbst zeigt den Hostnamen auf der Anmeldeseite an („<host> steht in keiner Verbindung zu Steam oder Valve\").\n\n— Form der Anfrage, die Steam empfängt (Host, wie bei Rollbit unter 2026-09-20 beobachtet): —\nGET steamcommunity.com/openid/login\n&openid.mode=checkid_setup\n&openid.return_to=https://rbsnin.com/… ← wird praktisch benötigt; erscheint im Logbuch von Valve\n&openid.realm=https://rbsnin.com ← von der Website selbst angegeben; wird auf der Anmeldeseite von Steam angezeigt\nWenn die Website eine Server-zu-Server-Überprüfung (check_authentication) verwendet, werden im Protokoll von Valve auch die Server-IP-Adresse der Plattform und das Hosting-Netzwerk erfasst.\n\nDas Extrahieren des Hostnamens aus dieser Anfrage ist ein Standardvorgang. Die Aufzeichnung der Durchsetzungsmaßnahmen – welche Hosts betroffen waren, welche nicht und nach welchen Kriterien – existiert ausschließlich in der Infrastruktur von Valve und wurde nicht veröffentlicht.\n\nWas dies beweist\n\n1. Der Block „Link-Filter“ wirkt sich auf Links aus, nicht auf Anmeldungen. Die Hauptdomain sperren (zum Beispiel rollbit.com) zeigt Nutzern, die innerhalb von Steam auf Links dazu klicken, eine Warnung an. Dies beeinträchtigt weder den Betrieb der Website noch die Nutzung des eigenen OpenID-Dienstes von Valve über eine andere Adresse.\n\n2. Die getesteten Authentifizierungshosts wurden nicht blockiert. Die obige Tabelle zeigt Authentifizierungshosts mit separaten Domänen, die zwischen 2011 und September 2026 registriert wurden, einige davon noch Jahre nach den Benachrichtigungen vom Juli 2016. Bei 26 Paaren gab die Hauptdomain eine „Link Filter“-Sperre zurück, der Proxy, der die Anmeldung übertrug, jedoch nicht (nicht authentifizierte Prüfungen, 2026-09-21 und 2026-09-22; Rohantworten und SHA-256 gespeichert). Dieser Proxy würde an dem Tag nicht mehr funktionieren, an dem Valve ihn ablehnte; daher ist das Kriterium hier, wie lange er gelaufen ist, und nicht, ob er aufgeführt ist. Valve erhält diese Hostnamen in seinen eigenen OpenID-Anfragen. Ob neben dem Link-Filter noch andere Maßnahmen angewendet wurden, lässt sich anhand öffentlicher Daten nicht feststellen, da Valve keine Aufzeichnungen über die Durchsetzung pro Betreiber veröffentlicht hat.\n\n3. Die Websites führten die Authentifizierung weiterhin über die Infrastruktur von Valve durch. „Mit Steam anmelden“ ist ein Dienst von Valve; jede Authentifizierung über diesen Dienst ist eine Anfrage, die Valve empfängt und verarbeitet. Valve erzielt ebenfalls Einnahmen aus Case-Keys, und der Steam Community Market erhebt eine kombinierte Gebühr von etwa 15% auf Transaktionen, die innerhalb des Marktes abgeschlossen werden (nicht auf externe Handelsgeschäfte). Die Aktion „Link Filter“ hat einen öffentlichen Datensatz erstellt; sie hat die Authentifizierungsbeziehung nicht unterbrochen.\n\nHätte eine Blockade funktioniert?\n\nAnalog dazu: Als der kostenlose Domain-Registrar Freenom im Jahr 2023 seinen Betrieb einstellte, wurden Phishing-Kampagnen, die auf dessen Domains basierten, unterbrochen. Die Betriebskontinuität hängt von der Stabilität der Infrastruktur ab.\n\nHier gilt dieselbe Logik. Würde ein Authentifizierungshost bei der OpenID-Verarbeitung von Steam abgelehnt, würde die Funktion „Mit Steam anmelden“ der Plattform so lange nicht funktionieren, bis ein neuer Host registriert, Zertifikate ausgestellt und die DNS-Änderungen übernommen sind. Während dieses Zeitraums käme es zu Ausfallzeiten.\n\nDurch die Rotation wird das Blocken nicht sinnlos. Dadurch wird das Blockieren zu einem Betriebskostenfaktor. Da neue Hosts bei ihrer ersten Nutzung in den eigenen Anfrageprotokollen von Valve erscheinen, könnte eine Antwort mit der Geschwindigkeit dieser ersten Nutzung erfolgen.\n\nDie Sammelregistrierung ist an sich schon ein Signal: Die Einträge „login1–login10“ von CSGOEmpire wurden am 2020-07-20 registriert, neun davon innerhalb von 22 Sekunden (Verisign RDAP). Eine Antwort muss nicht domänenweise erfolgen; eine fortlaufende Reihe aus einer Registrarsitzung kann als Serie identifiziert werden.\n\nAus den öffentlich zugänglichen Aufzeichnungen geht kein Versuch hervor, authentifizierte Hosts zu blockieren, der durch die Rotation vereitelt wurde.\nEs zeigt die gesperrten Hauptdomains, während der Proxy, über den die jeweilige Anmeldung erfolgte, weiterlief – 26 Paare (Stand: 2026-09-22), wobei der älteste Authentifizierungshost vor 12 Jahren und 6 Monaten registriert wurde – und es gibt für keinen Betreiber einen veröffentlichten Durchsetzungsnachweis.\nDie Frage an die Regulierungsbehörde lautet daher: Welche Durchsetzungsmaßnahmen hat Valve gegebenenfalls auf die Authentifizierungshosts angewendet, die sie in ihren eigenen OpenID-Anfragen erhält?\nWas Valve tat – und warum es den Auth-Pfad nicht unterbrach\n\nDie folgende Tabelle ordnet jede öffentlich dokumentierte Valve-Maßnahme dem Kriterium zu, ob sie den OpenID-Authentifizierungszugangspunkt betraf. Das Ergebnis lautet nicht „Valve hat nichts unternommen“ – vielmehr hat keine der öffentlich dokumentierten Maßnahmen den Punkt berührt, an dem Anmeldungen bei Glücksspielplattformen über die Server von Valve laufen.\n\nDatum\tValve Aktion\tBetroffen openid.return_to Pfad?\nJuli 2016\tÖffentliche Erklärung vom 13. Juli 2016; Mitteilungen des Anwalts an ~23 namentlich genannte Standorte (Presse, 21. Juli 2016); >40 Standorte wurden gemäß dem Schreiben von Valve vom Oktober 2016 an die WSGC kontaktiert\tNein. Benachrichtigungen und der Link-Filter wirken sich auf Operatoren und Links aus; der OpenID-Anforderungspfad wurde nicht geändert.\n2017\tSchließung von IEconItems_730/GetPlayerItems (laut dem Entwicklerkonto von CSFloat; es wurde kein Valve-Changelog gefunden)\tNein. Betroffen war die Sichtbarkeit des Verlaufs öffentlicher Einträge. Die OpenID-Authentifizierung wurde nicht geändert.\n2018-03-29\tCS:GO: 7-tägige Handelssperre angekündigt (blog.counter-strike.net)\tNein. Die Datenübertragung wurde verlangsamt; der OpenID-Anforderungspfad wurde nicht geändert.\n2022-05-10\tEndpunkte für die Stornierung von Handelsvorgängen wurden aus der öffentlichen Web-API entfernt (vom Benutzer entdeckt; kein Valve-Changelog – node-steam-tradeoffer-manager #325)\tNein. Das Tool für den Angebotsaustausch wurde geschlossen; die OpenID-Authentifizierung wurde nicht geändert.\n2023-12-04\tFür die Erstellung eines API-Schlüssels ist nun eine Bestätigung per Handy erforderlich (steamcommunity.com/dev/apikey; kein Changelog)\tNein. Der wichtige Endpunkt wurde geschützt; die hier dokumentierten Authentifizierungshosts waren nicht betroffen.\n2026-09-19 / 21.09.\tSteam Link: Filterzustand, wie er von den Autoren beobachtet wurde\tNr. 14 der Hauptdomänen lieferte bei der gespeicherten 2026-09-21-Nachprüfung einen Block zurück – 26 geteilte Paare im Register durch 2026-09-22 –, während der Proxy, der die jeweilige Anmeldung übertrug, weiterlief.\nQuellen: Valve Erklärung vom 13. Juli 2016 (store.steampowered.com/oldnews/22883, archiviert 2026-09-21) · Technischer Bericht von CSFloat zur Schließung im Jahr 2017 (blog.csfloat.com, archiviert 2026-09-21) · Status des Linkfilters: linkfilter-recheck-2026-09-21.json.\nDiese Erkenntnis lässt sich durch einen einzigen veröffentlichten Fall widerlegen, in dem Valve eine OpenID-Anfrage abgelehnt hat, weil openid.return_to verwies auf einen Host mit Glücksspiel-Zulassung. In den öffentlich zugänglichen Unterlagen konnte keine solche Instanz gefunden werden.\nDie beiden zuletzt vorgenommenen Registrierungen von Auth-Hosts\nhowl.unowurde am 2026-08-11 (RDAP) registriert, 41 Tage vor 2026-09-21; howl.gg gab am 2026-09-18, 2026-09-19 und 2026-09-21 eine Sperre durch den Link-Filter zurück. Ob die Sperre vor der Registrierung erfolgte, ist nicht geklärt.\nrbsnin.comwurde unter 2026-09-18T09:34:52Z (Verisign RDAP) registriert und wurde am 2026-09-20 im Anmeldeablauf von Rollbit unter Steam über einen Hinweis auf der eigenen Anmeldeseite von Steam festgestellt; rollbit.com gab am 2026-09-19 und 2026-09-21 eine Blockierung durch den Link-Filter zurück, rbsnin.com hingegen nicht.\nJeder Host in der obigen Tabelle wird an die Authentifizierungsserver von Valve gesendet als openid.realm bei jedem Anmeldeversuch.\nVollständige Daten pro Route und Ergebnisse des Link-Filters: die Tabelle in Abschnitt 3 oben; Rohdaten in linkfilter-recheck-2026-09-21.json und linkfilter-all-results.json.\nMethodik – Wie die Zahlen für Routen- und Verbindungsfilter ermittelt wurden\n1. Domain-Auflösung\nIm Rahmen des 2026-09-21-Audits wurden 78 der 189 angeforderten Plattformen abgearbeitet: 33 authentifizieren sich über ihren eigenen Hostnamen und 20 über ihre eigene Subdomain – direkte Authentifizierung, und keine davon wird als Route einer separaten Domäne gezählt. Die übrigen 25 Authentifizierung über eine separate, registrierbare Domain, verteilt auf 24 verschiedene Hostnamen (dota2.net wird von market.csgo.com und rust.tm gemeinsam genutzt): 10 wurden durch Live-Browser-Erfassung ermittelt, 3 durch einen Hinweis auf der Anmeldeseite von Steam und 12 durch eine bereitgestellte OpenID-URL. Das Live-Register (master_registry.json, 2026-09-22) erweitert dies auf 44 Routen mit separaten Domänen: 26 Filter-Split-Paare (Hauptdomain BLOCKED, Authentifizierungshost CLEAN) sowie 18 weitere Routen ohne Aufteilung nach Hauptdomain. Von den 44, 27. Eine Nachweisdatei pro Route führen; die übrigen 17 wurden von Hand gesammelt und sind gekennzeichnet realm_src: user im Register. Fünf dieser siebzehn – csgogem.com, gamdom.com, 12cs.fail, csgolounge.com und dota2lounge.com – wurden am 2026-09-22 hinzugefügt, wobei für beide Hosts eine Link-Filter-Erfassung vorlag (Raw-HTML + SHA-256 in linkfilter-2026-09-22.json), sodass die Aufteilung selbst belegt ist, obwohl der Bereich manuell erfasst wurde; sie erscheinen in der obigen Tabelle neben den Routen aus den Belegdateien. tfauth.com (tf2easy.com) wurde um 2026-09-22 aus dem Register gestrichen: Wie bei arena.fragnet.net gibt es keine nachprüfbaren Hinweise auf eine Verbindung zur Ursprungsseite. Die Zahl lässt sich aus den veröffentlichten Daten erneut ableiten. auth-route-audit.json (Lauf von 2026-09-21) nach einer Regel: Eine Plattform zählt nur dann, wenn ihr beobachteter Steam OpenID-Host auf einer anderen registrierbaren Domain liegt als die Plattform selbst.\n2. Steam Status des Linkfilters\nGetestet über steamcommunity.com/linkfilter/?url=https://[domain], nicht authentifiziert, auf 2026-09-19 und 2026-09-21; Roh-HTML mit SHA-256 gespeichert. Der Status wird für die Hauptdomain und den Authentifizierungshost separat erfasst. Ein Klassifikator unterscheidet den allgemeinen Hinweis „Sie verlassen Steam“ (CLEAN) von der Seite „Link gesperrt! … als potenziell bösartig markiert“ (BLOCKED); eine google.com-Kontrollseite bestätigt, dass die beiden nicht verwechselt werden. Eine frühere, authentifizierte Variante dieses Tests wurde verworfen, nachdem sie für jede Domain – einschließlich dieser Kontrollinstanz – den Status „blockiert“ zurückgab; dies wurde auf ein ungültiges Sitzungs-Cookie im Testskript zurückgeführt und stellte kein echtes Ergebnis dar.\n3. Überprüfung des Authentifizierungshosts\nLive-Aufzeichnung: Ein Playwright-Browser rief den Anmeldeprozess der jeweiligen Plattform auf und der openid.return_to Der Hostname wurde aus der abgefangenen Anfrage ausgelesen. Hinweis zur Anmeldeseite: Der Hostname wurde aus Steams eigener „<host> steht in keiner Verbindung zu Steam oder Valve\" Text, der Steam aus openid.realm (rbsnin.com, sc-auth.net, auth.dota.trade). Übermittelte URL: a Steam – den Autoren wurde eine Login-Formular-URL bereitgestellt; diese legt die Anfrageparameter fest, stellt jedoch keinen abgeschlossenen Anmeldevorgang dar. Auf keiner Plattform wurde eine Anmeldung abgeschlossen.\n4. Berichterstattung – Was wurde nicht geklärt, und warum ist das von Bedeutung?\nVon den 189 Plattformen, 110 ergab keine festgelegte Route und einer war nicht zutreffend (189 − 78 − 1). In diesem Dossier wurde keiner davon berücksichtigt. Die Aufschlüsselung der 110 Fälle aus der Prüfungsdatei: 22 Bot-Prüfungen, 14 Timeouts, 12 HTTP-Fehler und 10 Navigationsfehler – der Beobachter konnte den Anmeldeablauf nicht erreichen, obwohl sich die meisten dieser Websites in einem normalen Browser wie gewohnt öffnen lassen; 20 wiesen auf der Landingpage keine Steam-Anmeldekontrolle auf; 16 gelangten zu einem Anmeldeablauf, der nicht auf einen Host aufgelöst werden konnte; 11 Domains konnten im DNS nicht aufgelöst werden; 5 blieben an einer Einwilligungsabfrage hängen. Die nachstehende Tabelle unterteilt dieselben 110 Fälle anders: Die 11, die im DNS nicht aufgelöst werden konnten, sind separat aufgeführt als Entfernt · NXDOMAIN, und der eine Eintrag, auf den dies nicht zutrifft, reiht sich in die übrigen ein. 189 Plattformen wurden geprüft, 11 wurden aufgrund eines endgültigen NXDOMAIN-Ergebnisses von beiden Resolvern entfernt, 178 beibehalten (platform-audit.json, platforms-removed.json). 137 Authentifizierungsdomänen, die das Ledger anhand des Namensmusters erraten hatte, wurden aus den Daten auf 2026-09-19 gelöscht – sie wurden nie beobachtet und stellten daher auch keinen Beweis dar. Drei der Vermutungen wurden durch die angegebenen OpenID-URLs widerlegt: buff.163.com, gamerpay.gg und csgoluck.com führen die Authentifizierung direkt durch, während die Vermutungen auf buffauthproxy.163.com, gamerpayredirect.io und lucklogin.app lauteten. Die entfernten Einträge sind in der veröffentlichten Audit-Datei aufgeführt.\nDie Zahl 25 ist ein Mindestwert, keine Obergrenze. Von den 78 Plattformen, bei denen eine Authentifizierung erfolgreich war, nutzten 25 eine separate Domain und 53 nicht. Aus diesem Verhältnis lassen sich keine Rückschlüsse auf die 110 nicht authentifizierten Plattformen ziehen, und an keiner Stelle dieses Dossiers findet sich eine Hochrechnung auf deren Grundlage. Jede einzelne lässt sich auflösen, indem man die Seite öffnet und auf „Mit Steam anmelden“ klickt: Der Hostname für die Authentifizierung befindet sich in der URL der Steam-Seite, die geladen wird.\nDer Kernpunkt dieses Abschnitts: Ein unabhängiger Beobachter benötigt einen Browser und viel Geduld, um 189 Plattformen zu ermitteln, und hat 78 gefunden. Valve erfordert eine Datenbankabfrage. Jede Plattform, die „Mit Steam anmelden“ verwendet – sowohl ermittelte als auch nicht ermittelte –, sendet openid.realm bei jeder Anmeldung an den Authentifizierungsendpunkt von Valve. Die Lücke in dieser Tabelle ist darauf zurückzuführen, dass sich die Autoren außerhalb des Systems befinden. Bei Valve besteht diese Lücke nicht.\nDie beobachteten Proxy-Hostnamen befinden sich in auth-route-audit.json. Domain-Registrierungsdaten von RDAP (Verisign) / IP2WHOIS. Die Ergebnisse des Link-Filters lauten linkfilter-all-results.json.\nEine Analogie zur Verdeutlichung\n\nStellen Sie sich vor, ein zugelassenes Taxiunternehmen erhält von den Aufsichtsbehörden die Anweisung, dass es seinen Betrieb nicht mehr von seiner registrierten Adresse in der Main Street aus führen darf. Das Unternehmen entfernt das Schild an der Main Street. Diese Entfernung des Schildes wird dokumentiert. Das gleiche Unternehmen eröffnet jedoch eine Niederlassung in der Side Street – registriert unter einem anderen Namen – und setzt seinen Betrieb von dort aus fort. Die Aufsichtsbehörden betreiben das zentrale Dispatch-System, das jedes Taxi von beiden Adressen aus nutzt. Bei jeder Fahrtanfrage wird „Abholung in der Side Street“ angezeigt. Die Aufsichtsbehörden entziehen die Lizenz für die Side Street zu keinem Zeitpunkt. Die Entfernung des „Main Street“-Schilds war die einzige Durchsetzungsmaßnahme, die ergriffen wurde. Das Taxiunternehmen hat seinen Betrieb nie eingestellt.\n\nTeil A – Technische Unterlagen · Abschnitt 3.1\nIn Steam ist die Liste von Valve die einzige Liste.\n\nEin Link, auf den im Steam-Client, im In-Game-Overlay oder im Big-Picture-Modus geklickt wird, wird nicht im Browser des Benutzers geöffnet. Er wird im eigenen, eingebetteten Browser von Steam gerendert – wo die Warnebenen, die ein Browser anzeigen würde, nicht vorhanden sind. Der Link-Filter ist nicht nur eine von mehreren Sicherheitsvorkehrungen. Er ist die einzige.\n\nIn einem normalen BrowserDrei unabhängige Schichten\nGoogle Safe BrowsingEine ganzseitige Zwischenseite für Hosts, die auf den Phishing- und Malware-Listen von Google aufgeführt sind; diese wird kontinuierlich aktualisiert und ist unabhängig von der besuchten Website.\nDie Antiviren-BrowsererweiterungDie meisten Endpunktprodukte für Privatanwender enthalten ein Browser-Add-on, das die Zieladresse anhand der herstellereigenen Reputationsliste überprüft.\nHTTPS-Prüfung an EndgerätenWenn das Produkt eine TLS-Prüfung durchführt, wird der Seiteninhalt gescannt, bevor er den Nutzer erreicht.\nIm Steam-Client: Overlay und Big PictureEine Schicht\nGoogle Safe BrowsingNicht vorhanden. Für die Überprüfung sind Google-API-Schlüssel erforderlich, die in eingebetteten Chromium-Builds nicht bereitgestellt werden; falls diese fehlen, wird laut der Chromium-Entwicklungsdokumentation der „Safe Browsing“-Handler schlichtweg nie in die Anforderungskette aufgenommen.\nDie Antiviren-BrowsererweiterungNicht vorhanden. Der Renderer von Steam ist nicht der Browser des Benutzers und lädt keine Erweiterung aus dem Browserprofil des Benutzers, sodass auf der Seite kein Add-on ausgeführt wird.\nHTTPS-Prüfung an EndpunktenProduktabhängig. Der Datenverkehr endet innerhalb eines codesignierten Valve-Prozesses und nicht in einem erkannten Browser, und eine Reihe von Endpunktprodukten nimmt signierte Anwendungen von der TLS-Prüfung aus.\nDer Steam-Link-FilterDie eigene Blockliste von Valve, die abgefragt wird, wenn ein Link das Steam-Ökosystem verlässt. Dies ist die einzige Überprüfung, die durchgeführt wird – und die obige Tabelle zeigt, welche Ergebnisse sie für die in diesem Abschnitt dokumentierten Authentifizierungshosts liefert.\nEin Test, den jeder Leser durchführen kann, und wenn er fehlschlägt, ist das Ergebnis hinfällig\n\nÖffnen Sie eine der von Google veröffentlichten Test-URLs für „Safe Browsing“ (testsafebrowsing.appspot.com) in Chrome: Es erscheint eine ganzseitige rote Zwischenseite. Öffnen Sie dieselbe URL über eine Steam-Chatnachricht, sodass sie im Steam-Client oder im Overlay dargestellt wird: Es erscheint keine Zwischenseite. Die einzige Warnung, die Steam ausgeben kann, ist die eigene Link-Filter-Seite, und zwar nur für Hosts auf der Liste von Valve.\n\nValves eigene Bug-Bounty-BilanzDiese eine Ebene wurde bereits zuvor umgangen – auf Valves eigener Platte\n\nWenn der Link-Filter die einzige Überprüfung ist, die auf dem Client ausgeführt wird, sind seine eigenen Fehlerquellen kein Nebenaspekt. Zwei Meldungen im Rahmen des HackerOne-Programms von Valve, die beide angenommen, behoben und inzwischen vollständig offengelegt wurden:\n\n#291750archiviert 2025-11-16 ↗Open Redirect · medium\nUmgehung des Link-Filterschutzes\n\nGemeldet am 19. November 2017, behoben, veröffentlicht am 9. Mai 2018. Der im Bericht enthaltene Proof-of-Concept: Ersetzen des ideografischen Punktes 。 (%E3%80%82) für den Punkt in einem Hostnamen — Es ist möglich, die Sperre zu umgehen. Der Zwischentext, um den es in diesem Abschnitt geht, wurde nicht angezeigt.\n\n#1079561archiviert 2026-09-24 ↗Offenlegung von Informationen · hoch\nDer Webbrowser „Big Picture“ gibt Login-Cookies preis und legt sensible Informationen offen (kann zur Übernahme des Kontos führen)\n\nGemeldet am 15. Januar 2021, behoben, veröffentlicht am 21. September 2021. Die von Valve selbst festgelegte Schweregrad-Einstufung ist hoch, und der Titel gibt die Auswirkung an. Der veröffentlichte Datensatz enthält den Titel, die Einstufung und die Daten; die technische Beschreibung ist nicht Teil der veröffentlichten Daten, daher wird hier nichts Weiteres daraus zitiert.\n\nDie Interpretation der Autoren, nicht eine Feststellung aus einem der beiden Berichte: Beide liegen auf beiden Seiten desselben Tors. Das eine ist die Warnung, die nicht erscheint, bevor sich das Ziel öffnet; das andere ist die Sitzung, die den Client verlässt, sobald eine Seite darin geöffnet ist. Die Abfolge, die auf eine gestohlene Sitzung folgt – Schlüsselregistrierung ohne Aufforderung, Stornierung des eigentlichen Handels, Versand eines Duplikats an einen Klon – ist das Muster, das in Abschnitt 5 zu Abschnitt 8. Beide Berichte sind abgeschlossen; keiner der beiden wird als aktuelle Sicherheitslücke aufgeführt. Was sie belegen, ist zwar enger gefasst, reicht aber aus: Die einzige verbleibende Schutzebene wurde nachweislich bereits umgangen, wie aus den eigenen Aufzeichnungen von Valve hervorgeht.\n\nQuelle: Der HackerOne-Offenlegungsdatensatz für jeden Bericht, abgerufen am 2026-09-22 – Nummer, Titel, Team, Schwachstelle, Schweregrad, Datum der Meldung und der Offenlegung sowie Status, wie von HackerOne veröffentlicht. Abrufdatensatz: hackerone-reports.json. Hier wird kein Kopfgeldbetrag genannt; in den abgerufenen, veröffentlichten Unterlagen taucht auch keiner auf.\n\nFeldbeobachtung · PhishDestroyErkennungen, die normalerweise eine Kampagne beenden, haben diese nicht beendet\n\nWir haben beobachtet, wie Phishing-Hosts weiterhin Datenverkehr generierten, während sie 20 oder mehr Erkennungen von Anbietern. Wird eine Kampagne in diesem Zustand über das Web oder per E-Mail versendet, ist sie innerhalb weniger Tage zum Scheitern verurteilt – sowohl der Browser als auch das Antivirenprogramm reagieren auf diese Bewertungen. Innerhalb von Steam ist dies jedoch nicht der Fall. Die Bewertungen waren die ganze Zeit über vorhanden. Auf dem Client wurde nie danach gefragt.\n\nWas das für einen Minderjährigen bedeutet, auf dessen Computer ein Antivirenprogramm installiert ist\n\nEr ignoriert keine Warnung und deaktiviert nichts. In Steam geht eine Nachricht ein – ein kostenloses Messer, eine Stimme für das Team eines Freundes – und die Seite öffnet sich in Steam. Er öffnet nie einen Browser, daher schützt ihn der Browser auch nie. Sein Antivirenprogramm läuft und stuft diese Domain möglicherweise bereits als bösartig ein; es wird jedoch nie dazu aufgefordert. Jede Warnung, die ihn hätte aufhalten können, gibt es bereits. Keine davon dringt zu ihm durch. Er glaubt, dass er Steam nie verlassen hat, und das hat er auch nicht.\n\nDas Werbegeschenk ist keine Erfindung des Phishers – mit kostenlosen Valve-Artikeln werben Skin- und Glücksspiel-Websites, und genau deshalb wirkt die Nachricht ganz normal. Beschwerden: das Vollstreckungsarchiv. Angaben zu Alter und Kindern: § 17.\n\nQuellen: Steam stellt Webinhalte über das Chromium Embedded Framework im steamwebhelper Prozess — siehe Die technische Analyse von DARKNAVY vom 27. Juni 2024 ↗ und Valves eigenes Steam Client-Beta-Forum ↗ archiviert 2025-08-04 ↗. Es wird keine CEF-Version verwendet: Das eingebettete Chromium ist nicht Chrome und enthält keine der Google-Dienste von Chrome. „Safe Browsing“ ohne API-Schlüssel: Chromium-Design-Dokument ↗ archiviert 2026-08-21 ↗, Chromium-API-Schlüssel ↗ archiviert 2026-08-30 ↗ („Viele der von Chrome verwendeten Google-APIs sind Google-spezifisch und nicht für die Verwendung in abgeleiteten Produkten vorgesehen“), und derselbe Effekt tritt auch in anderen Builds ohne Schlüssel auf — Homebrew-Fass Nr. 193814 ↗. Test-URLs: testsafebrowsing.appspot.com ↗.\n\nZwei verschiedene Uhren\nDas Alter der Domain.Das Datum der Beobachtung.\n\nDas Erstellungsdatum der Registrierung gibt an, wann eine Domain registriert wurde. Ein datierter OpenID-Eintrag gibt den Rückgabehost in diesem Eintrag an. Ersteres kann die Jahre vor Letzterem nicht abdecken.\n\nDas vollständige Verzeichnis unterscheidet zwischen einer separaten registrierbaren Domain, einer eigenen Subdomain einer Website und einem direkten Pfad. Jede Zeile enthält einen Link zur Quelle und zum Ergebnis unter DNS.\n\nDomain-Register prüfen →· Anmeldetermine herunterladen ↗· Die Beobachtung wiederholen ↗\n\nTeil A – Technische Unterlagen · Abschnitt 4\nEin Endpunkt wurde geschlossen. Bei der öffentlichen Rückverfolgung ging ein Schlüssel verloren.\nKontext und Quellenbeschränkungen\n\nSteam wurden Änderungen eingeführt, durch die die öffentliche Sichtbarkeit von Asset-IDs entfernt und der API-Zugriff auf den Bestand eingeschränkt wurde. Die Folge: Es wurde unmöglich, einen bestimmten Artikel anhand seiner ursprünglichen Asset-ID anhand öffentlicher Daten zurückzuverfolgen. Im Folgenden wird dargelegt, was zuvor möglich war, was danach nicht mehr möglich war und welche Kosten einem Opfer entstehen, das nachweisen möchte, wohin sein Eigentum gelangt ist. Laut dem Entwicklerkonto von CSFloat ist das Datum 2017; ein Valve-Changelog wurde nicht gefunden. Der zeitliche Ablauf – etwa ein Jahr nach der Erklärung zum Glücksspiel vom Juli 2016 – ist Gegenstand der Untersuchung, keine Feststellung. Die Gegenstanddatensätze selbst verbleiben in den Systemen von Valve; externe Ermittler haben den Zugriff auf die ursprüngliche ID-Kette verloren, während Float-, Seed- und Paint-Identifikatoren nur einen teilweisen Abgleich ermöglichen.\n\nEs gilt die Regel Valve: Steam Der Support stellt keine Elemente wieder her, die Ihr Konto verlassen haben, und die Beweislast dafür, was geschehen ist, liegt bei Ihnen. Die Bilanz: Im Jahr 2017 schloss Valve den Endpunkt, über den die ursprünglichen Artikel-IDs übertragen wurden. Vorher konnte jeder einen gestohlenen Skin vom Konto des Opfers bis zu einem Marktplatz-Bot zurückverfolgen. Seitdem ist dies niemandem außerhalb von Valve mehr möglich. Der Nachweis, um den das Opfer gebeten wird, ist der Nachweis, der ausgetauscht wurde. — und es existiert immer noch, innerhalb von Valve.\n\nDie Zeit vor dem Stromausfall\n\nIn der Vergangenheit verfügte jeder auf Steam generierte virtuelle Gegenstand über eine global eindeutige, unveränderliche Asset-ID. OSINT-Datenbanken von Drittanbietern könnten diese IDs indexieren. Wenn einem Nutzer ein Gegenstand entwendet wurde, könnten Ermittler den Weg dieses bestimmten Gegenstands nachverfolgen, während er vom Zwischenkonto des Entführers in die Lagerkonten einer Handelsplattform oder einer Glücksspielseite gelangt.\n\nVORHER: Jeder konnte anhand öffentlich zugänglicher Daten den Weg eines Gegenstands vom Konto des Opfers über Zwischenkonten bis hin zu einem Marktplatz oder einem Casino-Speicherbot verfolgen.\nNach der Änderung\n\nLaut dem technischen Bericht von CSFloat hat Valve den Endpunkt im Jahr 2017 geschlossen, und die ursprünglichen Artikel-IDs standen externen Parteien nicht mehr zur Verfügung. Es wurde keine Erklärung von Valve zum Grund für diese Änderung gefunden. Im gleichen Zeitraum wurden auch keine veröffentlichten Maßnahmen gegen die kommerziellen Bot-Konten gefunden, die Artikel in großem Umfang verschoben haben.\n\nWas auch immer der Grund dafür sein mag, diese Änderung hat die öffentliche Nachverfolgungskette unterbrochen. Ein Geschädigter kann die ursprüngliche ID-Kette nicht mehr anhand öffentlicher Daten rekonstruieren, um nachzuweisen, dass ein bestimmter gestohlener Gegenstand über einen bestimmten Marktplatz oder ein bestimmtes Casino veräußert wurde. Die Datensätze zu den Gegenständen existieren zwar weiterhin in den Systemen von Valve, doch die Öffentlichkeit, Forscher und Strafverfolgungsbehörden, die mit öffentlichen Daten arbeiten, haben keinen Zugriff darauf.\n\nNACHHER: Die Rückverfolgung eines bestimmten Objekts anhand seiner ursprünglichen Asset-ID ist anhand öffentlicher Daten nicht mehr möglich. Die ursprüngliche ID-Nachverfolgungskette für ein nach 2017 verlegtes Objekt existiert nur innerhalb der Infrastruktur von Valve; öffentlich wurden keine entsprechenden Aufzeichnungen veröffentlicht. Float-, Seed- und Paint-Identifikatoren ermöglichen nur einen teilweisen, probabilistischen Abgleich.\nIEconItems_730\nGET/IEconItems_730/GetPlayerItems/v1/\nNachverfolgbare Nutzlast (vor dem Patch)\n\"id\": \"14892281934\",\n\"original_id\": \"11829910211\",\nStatus: Das Opfer kann die Herkunft des Gegenstands über verschiedene Bot-Konten hinweg nachverfolgen.\nVerschleierte Nutzlast (nach dem Patch)\nAktuell\n\"id\": \"HIDDEN_BY_PRIVACY_SETTINGS\",\n\"original_id\": \"NULL\",\nStatus: Externe Parteien können die Herkunft eines Artikels anhand der ursprünglichen Asset-ID nicht mehr aus öffentlich zugänglichen Daten zurückverfolgen.\nAuswirkungen auf die Beweisführung: Nach der Änderung standen die öffentlichen Daten, die erforderlich waren, um einen bestimmten Gegenstand anhand seiner ursprünglichen Asset-ID vom Konto eines Opfers bis hin zu einem Marktplatz oder Casino-Bot zu verfolgen, nicht mehr zur Verfügung. Die internen Aufzeichnungen existieren weiterhin unter Valve; ein Opfer, Forscher oder Ermittler, der auf der Grundlage öffentlicher Daten arbeitet, kann die ursprüngliche ID-Kette nicht rekonstruieren (Float-, Seed- und Paint-Identifikatoren ermöglichen nur einen teilweisen Abgleich).\n\nQuelle: Bericht von CSFloat Engineering über die Schließung im Jahr 2017 von IEconItems_730/GetPlayerItems — blog.csfloat.com/how-floatdb-tracks-items (archiviert 2026-09-21) · Die dargestellten Payloads dienen lediglich zur Veranschaulichung der Feldstruktur und stellen keine erfassten Antworten dar. · Es wurde kein Änderungsprotokoll (Valve) für die Closure gefunden.\n\nTeil A – Technische Unterlagen · Abschnitt 5\nEine Sitzung. Mehr Zugriff, als der Benutzer sieht.\nKontext und Quellenbeschränkungen\n\nDie API-Schlüssel-Architektur von Valve, wie sie vor den Änderungen im Jahr 2023 bestand, wich von den grundlegenden Branchenstandards ab (OWASP ASVS, NIST SP 800-63B) und entspricht dem Mechanismus, der in den automatisierten Beschwerden über Inventardiebstahl beschrieben wird, die im Beweisarchiv aufbewahrt sind (Abschnitte 6–8).\n\nEs galt die Regel Valve: Der Kontoinhaber hat den Schlüssel erstellt, die Bedingungen akzeptiert und trägt den Verlust – so lautet die Antwort in den archivierten Ablehnungen. Die Aufzeichnung: Bis Dezember 2023 reichte ein gestohlenes Session-Cookie allein aus, um diesen Schlüssel zu registrieren. Kein Passwort. Kein Steam Guard. Keine Benachrichtigung an den Inhaber des Kontos. Der Benutzer hat den Schlüssel nicht erstellt, konnte ihn nicht sehen und erhielt die Auskunft, er habe dies getan. Die mobile Bestätigung wurde am 2023-12-04 hinzugefügt – etwa sieben Jahre nach der Erklärung von 2016 und rund sechs Jahre nach den Betrugsfällen, die im Archiv dokumentiert sind. Diese Jahre wurden nicht von Valve bezahlt. Sie wurden durch die Konten finanziert, die in der Zwischenzeit leergeräumt worden waren, darunter auch einige Kinderkonten.\n\nOWASP ASVS 2.8 / NIST SP 800-63BSCHWERIGKEITSGRAD: KRITISCH\n1. Unzureichende mehrstufige Authentifizierung\n\nSteam ermöglichte die Generierung von API-Schlüsseln mit weitreichenden Berechtigungen und langer Gültigkeitsdauer, wobei lediglich ein Sitzungscookie verwendet wurde. Bei der Einrichtung oder Änderung eines Entwickler-API-Schlüssels war weder eine 2FA (Steam Guard) noch eine Step-up-Authentifizierung erforderlich, sodass die mobile Bestätigung Steam Guard – der einzige zweite Faktor, den Steam anbietet – diesen Schritt nicht schützte. (Ein zweiter Faktor in Form einer Hardware wurde 2016 im eigenen Tracker von Valve gefordert, und das Problem ist nach wie vor offen: Anhang D, GH-01.)\n\nStatus: Vor 2023 nicht behoben. Ein Skript, das ein gestohlenes Cookie enthielt, konnte ohne jegliche Benutzerinteraktion einen Schlüssel registrieren.\nOWASP A01:2021 / Prinzip der geringsten BerechtigungenSCHWERWIEGENDKEIT: KRITISCH\n2. Fehlen des Prinzips der geringsten Berechtigungen\n\nDer Steam-Web-API fehlten jegliche rollenbasierten Autorisierungsbereiche. Ein für den „schreibgeschützten“ Bestandsstatus ausgestellter Entwickler-API-Schlüssel verfügte über vollständige „Schreib“-Berechtigungen – einschließlich der Möglichkeit, bestehende Transaktionen zu bearbeiten, neue zu initiieren, Webhooks zu registrieren und gültige, ausstehende Umtauschvorgänge abzulehnen.\n\nStatus: Systemweiter Konstruktionsfehler. Ein Schlüssel = vollständige Lese- und Schreibrechte über den Bestand und die Transaktionen des Kontos.\nOWASP A07:2021 / VorträgeSCHWERWIEGENDKEIT: HOCH\n3. Fehlerhafte Sitzungsverwaltung\n\nNutzer berichteten, dass entführte Web-Sitzungen, die von IP-Bereichen von Server-Hosting-Anbietern ausgingen, weiterhin bestanden. Üblicherweise werden Sitzungen bei geografischen Anomalien und bei einer Passwortänderung beendet; die im Archiv gesammelten Nutzerberichte beschreiben jedoch Sitzungen, die auch nach einer Passwortänderung weiterhin aktiv blieben.\n\nStatus: Gemeldetes Verhalten (Benutzerbeschwerden im Archiv). In bestimmten Sitzungen konnten API-Schlüssel ohne erneute Authentifizierung generiert werden.\nEine Sperrung auf Domain-Ebene war technisch machbarDURCHSETZBARKEIT\n4. Eine Sperrung von Auth-Hosts auf Domain-Ebene war technisch machbar\n\nValve betreibt bereits eine Domänenliste (den Link-Filter) und erhält bereits jeden Auth-Hostnamen in seinen eigenen OpenID-Anfragen. Die beiden Mechanismen sind in keiner von außen sichtbaren Weise miteinander verbunden: Stand 2026-09-22 befand sich in 26 Fällen die Hauptdomain im Filter, während der Proxy, der die Anmeldung übermittelte, nicht darin enthalten war.\n\nSie miteinander zu verbinden, ist eine kleine technische Herausforderung: Lesen Sie die openid.realm Den Hostnamen jeder eingehenden Anfrage ermitteln, ihn mit einer Liste abgleichen und die Anfrage ablehnen oder markieren. Die Abbildung rechts veranschaulicht den Ablauf einer solchen Routine. Die Ablehnung des Authentifizierungshosts – und nicht nur der öffentlichen Startseite – würde den Schritt „Anmelden mit Steam“ unterbrechen, auf den diese Plattformen angewiesen sind.\n\nEs gibt keine öffentlich zugänglichen Belege dafür, dass Valve eine solche Überprüfung durchführt. Die kombinierte Gebühr des Steam Community Market in Höhe von etwa 15% gilt für Verkäufe, die innerhalb des Marktes abgeschlossen werden; sie wird nicht auf externe Transaktionen dieser Plattformen erhoben.\n\nblock_auth_hosts.pyABBILDUNG\n// Den Host Steam auslesen, der bereits Signale empfängt – kein Scannen\ndef on_openid_request(request):\nhost = parse_openid_realm(request)\nfalls Gastgeber in blockierte_Domains:\nablehnen (Antrag)\nHinweis: Pseudocode dient nur zur Veranschaulichung. Beide Teile sind bereits bei Valve vorhanden – der Hostname des Authentifizierers ist in der Anfrage enthalten, und die Domänenliste ist der Link-Filter. Es gibt keinen öffentlichen Eintrag, der erklärt, warum sie nicht miteinander verbunden sind.\nAbschnitt 5.1 – Die Normen wurden nicht veröffentlicht\nValve wird jeden Tag nach diesen Regeln kompiliert. Hier ist die Kompilierung nach diesen Regeln jedoch fehlgeschlagen.\n\nSteam ist im App Store und bei Google Play erhältlich, wickelt Zahlungen über die großen Zahlungsdienstleister ab und nutzt wie jede andere große Plattform APIs von Drittanbietern. Für jede dieser Beziehungen gelten veröffentlichte, datierte Sicherheitsanforderungen, die Valve erfüllen muss, um den Betrieb aufrechtzuerhalten. Vergleichen Sie die Daten dieser Anforderungen mit den Daten, an denen die eigene Web-API von Steam die gleichen Schutzmaßnahmen erhalten hat. Bei den folgenden Angaben handelt es sich weder um einen internen Standard, noch um ein internes Memo oder ein Geschäftsgeheimnis: Jede Zeile ist ein öffentliches Dokument mit einem Veröffentlichungsdatum.\n\nVeröffentlichte externe Sicherheitsanforderungen mit ihren jeweiligen Daten im Vergleich zu dem Zeitpunkt, zu dem die Steam-Web-API die entsprechende Kontrollmaßnahme eingeführt hat\nDie veröffentlichte Norm und das Datum ihres Inkrafttretens\tDie Steam-Web-API zur gleichen Frage\nBereichsbezogene BerechtigungOAuth 2.0 – RFC 6749, Oktober 2012. In Abschnitt 3.3 wird definiert scope So erhält ein Client nur die Zugriffsrechte, um die er bittet. Dies ist seitdem die Standardeinstellung jeder wichtigen Plattform-API.\tGranulare Gültigkeitsbereiche wurden eingeführt am 16. Januar 2026.Zuvor gewährte ein einziger Steam-Web-API-Schlüssel uneingeschränkte Lese- und Schreibrechte für alle Transaktionen des Kontos, unabhängig davon, zu welchem Zweck er ausgestellt worden war. Dreizehn Jahre und drei Monate nach der Spezifikation, die das Steuerelement definiert.\nEin Schlüssel ist keine Berechtigung.Googles eigene Cloud-Dokumentation: Ein Standard-API-Schlüssel dient nicht zur Authentifizierung eines Prinzipals., und für APIs, die Ressourcen erstellen oder verwalten, Verwenden Sie in der Produktionsumgebung keine Autorisierungsschlüssel.\tDer Web-API-Schlüssel „Steam“ war genau das.Eine Inhaberstring, die für ein Konto ausgestellt wurde und für sich allein ausreicht, um den Bestand abzurufen, einen ausstehenden Handel zu stornieren und einen neuen zu senden. Zum Zeitpunkt der Nutzung wurde kein Auftraggeber authentifiziert.\nMehrfaktor-Authentifizierung bei privilegiertem ZugriffPCI DSS 3.2, Anforderung 8.3 – verbindlich ab 1. Februar 2018 für alle nicht über die Konsole erfolgenden administrativen Zugriffe sowie für alle Fernzugriffe auf die Umgebung mit Karteninhaberdaten. Apple schrieb daraufhin eine Zwei-Faktor-Authentifizierung für jeden Inhaber eines Entwicklerprogramm-Kontos ab 27. Februar 2019: Entwickler mit der Rolle „Kontoinhaber“ in einem Entwicklerprogramm müssen die Zwei-Faktor-Authentifizierung aktivieren, um sich anzumelden.\tEs war ein zweiter Faktor erforderlich, um einen API-Schlüssel aus 4. Dezember 2023.Bis dahin reichte ein gestohlenes Sitzungs-Cookie aus, ohne dass auf dem Smartphone des Kontoinhabers eine Abfrage erschien und ohne dass anschließend eine Benachrichtigung erfolgte. Vier Jahre und neun Monate Nachdem Apple selbst Valve dazu veranlasst hatte, einen zweiten Authentifizierungsfaktor zu verwenden, nur um sich bei einem Entwicklerportal anzumelden.\nLebenszyklus und Sperrung von BerechtigungsnachweisenTwitch stellt an jede Drittanbieter-Anwendung folgende Anforderungen: Ihre App muss das OAuth-Token beim Start und danach stündlich überprüfen., und gibt an, dass es Anwendungen überprüft, bei denen dies nicht der Fall ist. Seine veraltete v5-API wurde am 28. Februar 2022 gemäß einem veröffentlichten Fahrplan.\tEs gibt keine veröffentlichten Aufzeichnungen zum Schlüssel-Lebenszyklus.Die Änderung im Jahr 2023 sicherte den Endpunkt für die Erstellung. Es wurde keine Valve-Anweisung gefunden, die sich auf bereits registrierte Schlüssel bezieht, und der Änderung lag überhaupt kein Änderungsprotokoll bei. Ob zuvor erstellte Schlüssel ungültig wurden, lässt sich anhand öffentlicher Daten nicht feststellen – und genau diese Frage müsste eine betroffene Person beantwortet bekommen, um zu wissen, ob ein vor Jahren auf ihrem Konto erstellter Schlüssel noch aktiv ist.\nArchitektur-Benchmark // Token Architecture\nFein abgestufte Gültigkeitsbereiche bei GitHub im Vergleich zur Web-API Valve Steam\n\nValve Entwickler verwalten täglich Open-Source-Software auf GitHub mithilfe von detaillierten Tokens mit minimalen Berechtigungen. Vergleichen Sie das mit dem monolithischen Schlüssel, der an 130 Millionen Steam Spieler ausgegeben wurde.\n\nGitHub-Token mit hoher Granularität\nWird von Valve auf GitHub verwendet\n\nFeinkörniges Token mit bereichsbezogener Isolation und zwingender Durchsetzung des Lebenszyklus.\n\nZugriff auf das Repository:Nur ausgewählte Repos (1 Repo)\nBerechtigungen erteilen:Nur-Lese-Zugriff [✓]\nCode & Geheimnisse:Kein Zugriff [✕]\nGültigkeitsdauer:30 Tage (vorgeschriebene TTL)\nProtokollierung von Prüfungen:IP, User-Agent und Zeitstempel\nSicherheitslage: Ein Token mit minimalen Berechtigungen begrenzt den Schaden auf eine einzige schreibgeschützte Ressource.\n!Valve Steam Web-API-Schlüssel\nAn 130 Millionen Nutzer ausgegeben\n\nEine einzige, 32 Zeichen lange Master-Zeichenkette, die die Handels- und Lagerbestandsbefugnisse nach dem „Alles-oder-nichts“-Prinzip enthält.\n\nZugriff auf das Konto:VOLLSTÄNDIGES KONTO (monolithisch)\nHandelsmanagement:Lesen, Stornieren, Ablehnen [!]\nGranulare Geltungsbereiche:KEINE (Ankunft 2026, 13 Jahre zu spät)\nGültigkeitsende:NIEMALS (unbefristet gültig)\nProtokollierung von Prüfvorgängen:KEINE (Der Nutzer hat noch keine IP-Historie)\nSicherheitslücke: Ein gestohlener Schlüssel ermöglicht das unbemerkte Abfangen aller ausgehenden Handelsangebote.\nDer in einer Richtung angewandte Standard\n\nAngenommen, ein Anbieter Valve – sei es ein Cloud-Anbieter, ein Zahlungsdienstleister oder ein CDN – hat einen Endpunkt für Anmeldedaten ohne zweite Authentifizierungsstufe offen gelassen, und Monate später gelangten die Unternehmensdaten von Valve über einen an diesem Endpunkt generierten Schlüssel nach außen. Würde Valve akzeptieren, dass die Schuld bei demjenigen liegt, der auf den Link geklickt hat? Die in diesem Dossier archivierten Ablehnungen beantworten die spiegelbildliche Frage für den Nutzer: Man vertritt den Standpunkt, dass der Kontoinhaber den Schlüssel erstellt hat und den Verlust zu tragen hat. Diese Architektur wird so beschrieben, dass in der einen Richtung der Anbieter versagt und in der anderen Richtung der Nutzer die Verantwortung trägt. Ob dies der Fall ist, ist keine technische Frage, und es ist auch keine Frage, die im Rahmen dieser Untersuchung geklärt werden kann – darüber entscheidet ein Gericht oder eine Aufsichtsbehörde.\n\nVeranschaulichung, kein Beweis – der Standard, umgekehrt gelesen\nEin Zahlungsabwickler, der es einem Skript eines Drittanbieters ermöglichte, allein anhand eines Browser-Cookies eine Transaktionsberechtigung mit uneingeschränkten Rechten zu generieren, ohne dass der Kontoinhaber dazu aufgefordert wurde.\nEin Identitätsanbieter, der die Sicherheitslücke geschlossen hat, über die seine Token generiert wurden, und keine Informationen über die bereits generierten Token veröffentlicht hat.\nEine Bank, die auf eine beanstandete Überweisung mit dem Hinweis reagierte, dass die verwendeten Zugangsdaten auf dem eigenen Konto des Kunden registriert seien, und den Vorgang abschloss.\n\nKeine dieser Feststellungen bezieht sich auf ein konkret genanntes Unternehmen. Es handelt sich um dieselben gestalterischen Entscheidungen, übertragen auf einen Kontext, in dem die Reaktion der Aufsichtsbehörde gut dokumentiert ist – und genau diesen Vergleich soll eine Aufsichtsbehörde anstellen.\n\nWas aus den Akten hervorgeht: Die in der Steam-Web-API fehlenden Kontrollen waren öffentlich, veraltet und stellten in mehreren Fällen Bedingungen dar, Valve die erfüllt werden mussten, damit das Unternehmen seine eigenen Produkte weiterhin ausliefern konnte. Der Zeitraum zwischen den einzelnen Standards und der entsprechenden Steam-Änderung ist messbar und wurde oben dargelegt. Was damit jedoch nicht geklärt wird, ist der Grund dafür. Es wurde keine Begründung für eines dieser Intervalle gefunden, und es wird hier auch keine angenommen; diese Aufzeichnung befindet sich in Valve und wurde nicht veröffentlicht.\n\nQuellen, jeweils ein öffentlich zugängliches Dokument: OAuth 2.0 — RFC 6749, Oktober 2012 ↗ · Google Cloud — Dokumentation zu API-Schlüsseln ↗ · PCI DSS 3.2, Anforderung 8.3 — PCI SSC-Leitfaden ↗ · Apple — Bevorstehende Verpflichtung zur Zwei-Faktor-Authentifizierung für Kontoinhaber, 20. Februar 2019 ↗ archiviert 2025-05-06 ↗ · Twitch — Anforderung zur Token-Validierung ↗ und die Hinweis zur Einstellung von v5 ↗ archiviert 2025-01-27 ↗. Die Daten von Steam entsprechen denen im Aktualisierungsdatensatz in diesem Abschnitt; die Einträge für 2023 und 2026 sind diejenigen, die Valve ohne Änderungsprotokoll veröffentlicht hat. Abgerufen am 2026-09-22.\n\nValves eigene Aktualisierungsaufzeichnung – datiert, aus öffentlichen Quellen\nDatum\tValve ändern\tAngekündigt?\tWas wurde geschlossen?\tVerzögerung: Mechanismus öffentlich → behoben\tQuelle\n2026-09-01\tAutomatische Kennzeichnung verdächtiger Chats\tJa\tGefährliche Links / Muster in Gruppenchats\t—\tNachrichten ↗\n2026-01-16\tDetaillierte Geltungsbereiche der Steamworks-Web-API\tJa\tBereiche mit minimalen Berechtigungen für Entwicklerschlüssel\t—\tAnkündigung ↗\n2025-07-15\tCS2-Handelsschutz und Rückabwicklungsfenster\tJa\tNichts. Dies ist keine Sicherheitsmaßnahme, die das Grundproblem behebt. Der Zugriff auf die Kontowiederherstellung durch den Support bleibt davon unberührt. Das Auslösen einer Rückabwicklung führt zu einer automatischen 30-tägigen Handelssperre (Skinvault ↗), während ein Schock im Kassahandel zu einem Einbruch der Marktkapitalisierung um $104M (-25%) innerhalb von 24 Stunden führte (CSMarketCap ↗). Im Jahr 2026 wurden die Zeitmesser auf Einzelartikel umgestellt (Skin.land ↗).\t—\tFAQ ↗\n2025-05-14\tMitteilung zur Kontosicherheit\tJa\tLeitfaden zu Stealer / Session-Hijacking\t—\tAnkündigung ↗\n2024-10-02\tCS2 „The Armory“ – 7-tägige Sperre\tJa\tHandel/Markt für Rüstungsgegenstände vorübergehend ausgesetzt\t—\tAnkündigung ↗\n2024-09-18\tHandelsbeschränkung bei der Anmeldung auf einem neuen Gerät\tJa\t2–7-tägige Handelssperre bei neuen Geräten\t—\tFAQ ↗\n2024-02-14\tÄnderung des Profilnamens und des Avatars zurückgestellt\tJa\t2–4 Stunden Wartezeit für Trades nach einer Umbenennung\t—\tBeitrag ↗\n2023-12-04\tBestätigung per Handy für API-Schlüssel\tKein Änderungsprotokoll\tStille Schlüsselregistrierung ausschließlich über Cookies\t≈6 Jahre nach den Panels aus der Zeit um 2017\tEntwicklerseite ↗\n2023-10-24\tSMS-MFA für die Veröffentlichung von Spiel-Builds\tJa\tVeröffentlichung von Builds über Steamworks\t—\tAnkündigung ↗\n2023-07-12\tWarnhinweis zu benutzerdefinierten Biografieinhalten\tJa\tPhishing-Links in Biografien\t—\tForum ↗\n2023-01-25\tProfil {LINK ENTFERNT} & Abklingzeit\tJa\tLinks im Profiltext\t—\tFAQ ↗\n2022-10-24\tÜberarbeitung des Anmeldeprozesses und Kürzung von Cookies\tKein Änderungsprotokoll\tUnbegrenzte Anzahl gestohlener Sitzungen\t— (Token-Migration des IAuthenticationService)\tNachrichten ↗\n2022-10-12\tMobile App 3.0 – Anmeldung per QR-Code\tJa\tFenster zur Aufhebung der Sitzungsautorisierung\t—\tNachrichten ↗\n2022-05-10\tEndpunkte für die Stornierung von Transaktionen entfernt\tKein Änderungsprotokoll\tAngebotsaustausch (stornieren und erneut senden)\t≈5 Jahre nach den Panels aus der Zeit um 2017\tAusgabe Nr. 325 ↗\n2020-05-25\tDota 2: 7-tägige Handelssperre\tJa\tSchnelles Weiterverkaufen von Artikeln\t—\tBlog ↗\n2018-03-29\tCS:GO – 7-tägige Handelssperre\tJa\tSofortige Bot-Geldwäsche\t≈20 Monate nach der Erklärung vom Juli 2016\tBlog ↗ archiviert 2025-02-26 ↗\nQuellen: die verlinkten Valve-Beiträge, Hilfeseiten und GitHub-Issues, jeweils mit Datumsangabe. Drei entscheidende Korrekturen wurden ohne Changelog veröffentlicht (Mai 2022, Oktober 2022, Dezember 2023) und von Nutzern entdeckt, nicht von Valve angekündigt – diese Asymmetrie ist Teil der Durchsetzungshistorie. Verzögerungen werden nur dort berechnet, wo die datierungsbezogenen Angaben des Dossiers selbst (Erklärung vom Juli 2016; Betrugsforen aus dem Jahr 2017) den Ausgangspunkt liefern; „—“ bedeutet, dass hier kein solcher Ausgangspunkt festgelegt ist.\nTeil A – Technische Unterlagen · Abschnitt 6\nInteraktiver Exploit- und Hijack-Simulator\nKontext und Quellenbeschränkungen\n\nEine Rekonstruktion des Ablaufs von der Phishing-Nachricht bis zur serverseitigen Schlüsselregistrierung und dem Handelstausch. Vor 2023 konnte ein auf einem Konto registrierter Web-API-Schlüssel den Bestand des Kontos einsehen, ein ausstehendes Handelsangebot stornieren und ein neues erstellen, ohne dass dem Kontoinhaber bei einer dieser Aktionen ein Bestätigungsbildschirm angezeigt wurde. Dies stellt einen Verstoß gegen das Prinzip der geringsten Berechtigungen dar (OWASP A01:2021). Die Zeitangaben in dieser Simulation dienen lediglich der Veranschaulichung und sind keine Echtzeitmessungen der aktuellen Plattform.\n\nGehen Sie die rekonstruierte Entführung Schritt für Schritt durch. In jeder Phase wird gezeigt, was der Kontoinhaber sieht, und daneben der Anruf, den Steam im selben Moment erhält. Jeder einzelne dieser Anrufe wird ordnungsgemäß authentifiziert. Nichts in diesem Ablauf erfordert, dass die Authentifizierung von Steam fehlschlägt – vielmehr darf der von Steam ausgestellte Schlüssel keinen Geltungsbereich haben (OWASP A01:2021).\n\nWas der Spieler sieht. Was sich dahinter verändert.WALKTHROUGH-SIMULATOR\nSchritt 5 / 5\n\nDer Exploit wurde erfolgreich ausgeführt. Da das Opfer eine Benachrichtigung auf seinem Mobilgerät bezüglich seines ursprünglichen Handelsgeschäfts erwartet, genehmigt es das Ersatzgeschäft. Dies ist eine integrierte forensische Schritt-für-Schritt-Anleitung, die zeigt, wie das Fehlen des Prinzips der geringsten Berechtigungen (OWASP A01:2021) eine automatisierte, in Bruchteilen von Sekunden erfolgende Übernahme von Vermögenswerten ermöglicht.\n\n01 / DER CHAT-KÖDEREin Freund bittet mich, meine Stimme abzugebenDas Opfer erhält eine Nachricht mit einem Link.\n02 / DIE ANMELDUNGEin Portal für DoppelgängerDas Opfer gibt seine Anmeldedaten ein.\n03 / DER ZUGANGErstellung einer „Silent Web“-APIDer Angreifer registriert einen Entwicklerschlüssel.\n04 / DER WECHSELLegitimer Handel ausgetauschtDer „Clone Bot“ dupliziert den Zielempfänger.\n05 / BESTÄTIGUNGFälschung genehmigtFalsches Angebot auf dem Handy genehmigt.\nDerselbe Schritt, aus der Perspektive des Netzwerks betrachtetRekonstruktion des Musters vor 2023 · veranschaulichende Anrufmuster\nOpferBestätigt die mobile Benachrichtigung, die für das ursprüngliche Geschäft erwartet wurde.\nAngreiferNimmt die Artikel auf dem Klonkonto entgegen.\nSteam siehtEine Überweisung, die vom Kontoinhaber auf einem registrierten Gerät bestätigt wurde.\nConfirmation genuine — made by the account holder\nRecipient the clone bot, not the intended counterparty\nThe confirmation is authentic. The offer it confirms is not the one the user initiated.\n\nDie hinterlassenen Spuren: ein Handel, den der Nutzer genehmigt hat. Das ist der Datensatz, den der Support bei Eingang der Beschwerde ausliest (Steam), und der Grund, warum die archivierten Beschwerden als „Benutzerfehler“ abgeschlossen wurden. Die Beschwerden befinden sich in das Vollstreckungsarchiv.\n\nTeil A – Technische Unterlagen · Abschnitt 7\nDie Endpunkte, die hinter der Sequenz stehen.\nKontext und Quellenbeschränkungen\n\nDies sind die Steam Web-API-Endpunkte, über die die gemeldeten Hijack-Skripte Transaktionen abgefangen haben, ohne die bestätigungsschritte auf der Browserseite zu durchlaufen.\n\nVier dokumentierte Endpunkte erledigen die gesamte Aufgabe. Keiner davon weist einen Fehler auf, keiner musste ausgenutzt werden – ein gültiger Schlüssel ruft sie auf, und Steam antwortet. Der Schlüssel ist das Einzige, was der Angreifer stehlen musste.\n\nIEconService / GetTradeOffers / v1UMFRAGE\n\nDient zur Überwachung der Handelsangebote des Kontos. Skripte fragen diesen Endpunkt wiederholt mit dem kompromittierten API-Schlüssel ab; er gibt die Details neu erstellter, ausstehender oder geänderter Handelsangebote zurück. Die Abfrageintervalle werden hier nicht gemessen.\n\nAngriffsvektor: Zeigt die IDs ausstehender Handelsangebote sowie die Profildetails des Empfängers an.\nIEconService / CancelTradeOffer / v1INTERAKTION\n\nWurde verwendet, um das rechtmäßige Handelsangebot des Nutzers programmgesteuert für ungültig zu erklären. Vor 2023 war der Schlüssel nicht durch eine mehrstufige Authentifizierung geschützt, sodass ein automatisierter Server ein Angebot sofort nach dessen Erkennung stornieren konnte, ohne dass der Kontoinhaber dazu aufgefordert wurde.\n\nAngriffsvektor: Der Handel wird storniert, bevor der Kontoinhaber die Bestätigung per Handy abgeschlossen hat.\nISteamUser / GetPlayerSummaries / v2RECON\n\nAbfrage zum Abrufen des Profilnamens, der URL des Avatar-Bildes und der Stufe des legitimen Handelsempfängers. Dadurch kann das Skript ein vorbereitetes Klonkonto entsprechend anpassen. Hier wird keine Zeit gemessen.\n\nAngriffsvektor: Stellt die Daten bereit, die erforderlich sind, um sich als der beabsichtigte Empfänger auszugeben.\n/dev/ajaxregisterkeyENTSTEHUNG\n\nDer Registrierungsendpunkt von Steam für Schlüssel. In der Vergangenheit konnte jede aktive Browser-Cookie-Sitzung (`steamLoginSecure`) einen Schlüssel registrieren, ohne dass eine Bestätigung durch Steam Guard auf dem Mobilgerät erforderlich war und ohne dass der Kontoinhaber darüber benachrichtigt wurde.\n\nAngriffsvektor: Eine dauerhafte Zugangsberechtigung, die von einem Skript erstellt wurde, ohne dass der Kontoinhaber davon Kenntnis hat.\nTeil A – Technische Dokumentation · Abschnitt 8 · Artikel 7 der DSGVO\nEin angekreuztes Kästchen. Wessen Handlung?\nKontext und Quellenbeschränkungen\n\nBei der Ablehnung der Erstattung vertreten die im Archiv gespeicherten Support-Antworten die Auffassung, dass der Kontoinhaber den API-Schlüssel erstellt und durch Anklicken des Kästchens die Bedingungen akzeptiert hat.\n\nIn der Antwort des Supports wird der Schlüssel dem Kontoinhaber zugeordnet. Die Frage ist, ob aus dem Datensatz hervorgeht, wer ihn tatsächlich angelegt hat.\n\nBei dem beobachteten Muster des API-Schlüssel-Missbrauchs hat das Opfer jedoch die Seite zur Erstellung des API-Schlüssels weder gesehen noch aufgerufen. Das Einwilligungsfeld wird von einem Skript übermittelt, das mit dem gestohlenen Sitzungs-Cookie einen „Headless“-POST-Aufruf ausführt.\n\nGemäß Artikel 7 und Artikel 4 Absatz 11 der DSGVO muss die Einwilligung eine freiwillige, spezifische, informierte und eindeutige Willensbekundung der betroffenen Person sein. Die Autoren vertreten die Auffassung, dass ein Feld zur Zustimmung zu den Nutzungsbedingungen, das von einem bösartigen Skript unter Verwendung eines gestohlenen Cookies übermittelt wird, ohne dass dem Kontoinhaber eine Seite angezeigt wird, dieser Definition nicht entsprechen kann. Ob dies der Fall ist, muss die Aufsichtsbehörde entscheiden.\n\nForensische Payload-Analyse: Schlüsselregistrierung\nBEITRAG https://steamcommunity.com/dev/ajaxregisterkey\n// Anfrage-Payload (über ein Hijacking-Skript eingefügt)\n{\n\"agreeToTerms\": „einverstanden“, <-- maschinell eingegeben, ohne menschliches Zutun\n\"domain\": „localhost“, ← nicht validiert – jeder Wert wird akzeptiert, einschließlich „localhost“\n„sessionid“: \"8f0d8ef763ab2140bf89de2a\"\n}\nDie Frage an die Aufsichtsbehörde: Wenn der Kontoinhaber das Zustimmungsfeld nie angeklickt hat, stellt sich die Frage, ob die für das Konto erfasste Zustimmung zu den Nutzungsbedingungen die Anforderungen von Artikel 7 an eine freiwillige, konkrete, informierte und eindeutige Willensbekundung der betroffenen Person erfüllt und ob sich der Kundendienst Steam darauf berufen kann, um einen Anspruch abzulehnen.\n\nQuelle: Abfrage der Form der Schlüsselregistrierung, wie sie anhand des öffentlichen Endpunkts und der im Beweismittelarchiv gespeicherten Hijack-Meldungen rekonstruiert wurde (durchsuchbare Version von 2026-09-17) · Die angezeigte Sitzungskennung ist ein Platzhalter und kein erfasster Wert.\n\nForensische Autopsie · Der Handelssubstitutionsvektor\nWie Valve schließlich die „Handelssubstitution“ neutralisierte – und warum es sieben Jahre voller Umgehungslösungen dauerte\n\nSeit fast einem Jahrzehnt ist die „API-Schlüssel-Substitution“ (oder API-MitM-Betrug) war das lukrativste Modell für Kontodiebstahl auf Steam, bei dem Skins im Wert von Hunderten Millionen Dollar von ahnungslosen Spielern abgezweigt wurden. Valve hat den Exploit nicht durch eine Korrektur der anfälligen API-Architektur beseitigt; stattdessen hat Valve sieben Jahre damit verbracht, vier plattformweite Reibungsbarrieren zu errichten, die die Liquidität des Handels innerhalb der Community stark beeinträchtigten, während die eigentliche Ursache ungelöst blieb.\n\n1. Der Tod durch Mimikry\nAbklingzeit für Avatar und Namen (Februar 2024)\n\nDer Angriff erforderte eine Nachahmung im Bruchteil einer Sekunde: Der Betrugsbot fing eine ausgehende Transaktion ab und extrahierte den Avatar bzw. den Namen des Empfängers über ISteamUser, und klonte das Profil in 200 ms. Am 14. Februar 2024 führte Valve stillschweigend eine verbindliche 2- bis 4-stündige Abklingzeit für den Handel (Fehler 34) unmittelbar nach jeder Änderung des Profilnamens oder des Avatars. Ein Bot kann einen Empfänger nicht mehr spontan klonen, ohne sich selbst vom Handel auszuschließen.\n\n2. Der wirtschaftliche Niedergang\n7-Tage-CS2-Handelsumkehr (Juli 2025)\n\nValve einseitig eingeführt Handelsumkehrungen für Counter-Strike-Gegenstände. Jeder getauschte Skin wird sieben Tage lang als „Tauschgeschützt“ gekennzeichnet. Entdeckt ein Opfer einen Austausch, klickt es im Steam-Support auf „Tausch rückgängig machen“, woraufhin der Skin sofort in sein Inventar zurückgeführt und der Empfänger gesperrt wird. Da die 7-tägige Tausch-Sperre Betrüger daran hindert, den Gegenstand auf eine Auszahlungsseite zu übertragen, wird der Diebstahl unrentabel.\n\n3. Der Tod des „Silent Key“\nObligatorischer mobiler Push für die API (Dezember 2023)\n\nIn der Vergangenheit ermöglichte ein gestohlenes Session-Cookie bösartigen Skripten, einen „Headless“-POST-Aufruf im Hintergrund an /dev/ajaxregisterkey ohne das Opfer darüber zu informieren. Am 4. Dezember 2023 schrieb Valve eine ausdrückliche Push-Bestätigung in der Steam-App vor, um einen Web-API-Schlüssel zu generieren, wodurch die stillschweigende Schlüsselvergabe im Hintergrund unterbunden wurde.\n\n4. Mobile Warnmeldungen in der App\nBanner mit Kontodauer und Namen (2022–2024)\n\nValve hat das Bestätigungsfenster für Mobilgeräte überarbeitet, um die Daten des Handelspartners anzuzeigen Steam Kontoalter (Erstellungsdatum), Stufe Steam und eine ausdrückliche gelbe Warnung: „Dieser Nutzer hat kürzlich seinen Profilnamen geändert.“, wodurch die optische Täuschung für aufmerksame Opfer durchbrochen wird.\n\nDie drei Schwachstellen in Valves Patchwork: Warum Betrüger einfach ihre Ziele gewechselt haben\n1. Die Lücke beim Ausschluss von Spielen (Dota 2 & TF2)\n\n„Trade Reversals“ wurden ausschließlich für Counter-Strike 2 eingesetzt. Gegenstände in „Dota 2“ und „Team Fortress 2“ sind nach wie vor völlig ungeschützt aufgrund der Komplexität beim Herstellen und Besetzen. Hochwertige Gegenstände im Wert von Tausenden von Dollar (Drachenklauenhaken, Goldene Baby-Roshans, ungewöhnliche TF2-Brennflammen) unterliegen keinerlei Rückgaberecht. Betrüger haben die automatisierte API-Abfangtechnik einfach auf „Dota 2“- und „TF2“-Händler umgeleitet, wo der Steam-Support seine Richtlinie aus dem Jahr 2016, wonach keine Gegenstände wiederhergestellt werden, strikt durchsetzt.\n\n2. Der „Zombie-Key“-Speicher (ohne Ablaufdatum)\n\nWährend Valve die mobile Push-2FA hinzugefügt hat, um neu Schlüssel im Dezember 2023, Valve Bestehende API-Schlüssel aus früheren Versionen wurden nie widerrufen, sind nie abgelaufen und wurden nie gelöscht.. Millionen aktiver Konten, die Schlüssel generiert haben (oder bei denen vor Dezember 2023 durch Phishing oder Malware unbemerkt Schlüssel erstellt wurden), verfügen nach wie vor über aktive Anmeldedaten mit keine Ablaufzeit (keine TTL) und kein Zeitlimit für Inaktivität. Angreifer unterhalten riesige historische Datenbanken mit diesen persistenten Schlüsseln und fragen diese weiterhin ab IEconService ungestört.\n\n3. Die Strafe für das Opfer: 30-tägiges Handelsverbot\n\nSelbst in CS2 wird der betrogene Spieler in Valve bestraft: Ein Klick auf „Reverse Trade“ im Steam-Support führt automatisch zu einer zwingendes 30-tägiges Handels- und Community-Markt-Verbot für das Konto des Opfers. Valve bestraft den Nutzer mit einem einmonatigen Plattformverbot, um von „unbegründeten“ Rückabwicklungen abzuschrecken und Opfer davon abzuhalten, Transaktionen mit liquiden Artikeln von geringem Wert rückgängig zu machen.\n\nDer zentrale Regulierungsskandal: Sieben Jahre Umgehungsmaßnahmen gegen einen einzigen API-Gültigkeitsbereich\n\nWarum hat Valve sieben Jahre damit verbracht, Handelssperren, Konto-Abklingzeiten und reversible Handelssperren zu entwickeln – wodurch die gesamte Spielwirtschaft durcheinandergebracht und eine Marktkapitalisierung von $104M zunichte gemacht wurde –, anstatt die branchenübliche Lösung umzusetzen?\n\nWie die offizielle Steamworks-Veröffentlichung von Valve am 16. Januar 2026 belegt (Ankündigung #493839547938902179 ↗), Valve bereits gebaut Detaillierte Berechtigungsgruppen (Allgemein, Mikrotransaktionen, Wirtschaft, Verkaufsdaten) und IP-Whitelisting für Publisher-Schlüssel von Unternehmen. Valve verfügte bereits seit Jahren über die technische Lösung. Ein einziges Kontrollkästchen für den Benutzer –„Verhindern Sie, dass dieser Web-API-Schlüssel auf IEconService (Trade Management) zugreift.“ oder eine Whitelist für private IP-Adressen – hätte den Betrug mit Handelssubstitutionen im Jahr 2018 ohne jegliche wirtschaftlichen Kollateralschäden beseitigt. Valve weigerte sich, regulären Spielern denselben Schutz zu gewähren, den es für seine Unternehmenspartner entwickelt hatte.\n\nTeil B – Vorschriften und Durchsetzungsbilanz · § 9\nIhr Regelwerk. Die aufgezeichneten Plattformen.\nKontext und Quellenbeschränkungen\n\nDieses Hauptbuch ordnet explizite Klauseln aus dem Steam Abonnentenvertrag (SSA) und Steam Online-Verhalten (SOC) Richtlinien, die sich direkt gegen aktive, groß angelegte kommerzielle Unternehmen richten.\n\nDie Regel: Keine kommerzielle Nutzung, kein Glücksspiel, keine Bots – und Steam Der Kundendienst beruft sich auf diese Klauseln, wenn er sich weigert, die Gegenstände eines Opfers zurückzugeben. Die Bilanz: Diese Bestimmungen gelten auf den ersten Blick für die kommerziellen Plattformen in diesem Register, die auf Steam Identitäten, Steam Bots und Steam Übertragungen basieren. Die Klausel wird gegenüber der Person durchgesetzt, die die Häute verloren hat, und nicht – soweit aus den veröffentlichten Unterlagen hervorgeht – gegenüber den Unternehmen, die sie transportiert haben.\n\nIn den archivierten Beschwerden führt Steam Support Folgendes an: „Keine kommerzielle Nutzung“ und „Keine Automatisierung/Bots“ Klauseln bei der Verweigerung der Rückgabe von Gegenständen an Opfer von API-Key-Betrug. Dieselben Klauseln gelten dem Wortlaut nach auch für die in diesem Dossier aufgeführten kommerziellen Plattformen, die sich über Steam OpenID authentifizieren und Gegenstände über automatisierte Steam-Konten bewegen. Es wird hier keine marktweite Umsatzschätzung vorgenommen (siehe die Durchsetzungsstatistiken weiter unten). Die Aufzeichnungen zeigen lediglich die Anwendung der Regelung auf einzelne Konten in den archivierten Fällen, jedoch keine veröffentlichten Durchsetzungsdaten pro Betreiber für die Plattformen. Diese Asymmetrie wird in diesem Abschnitt dokumentiert.\n\nDie zentrale Frage / selektive DurchsetzungRegeln → Umfang → Rechenschaftspflicht\nEin Regelwerk. Ungleiche Durchsetzung.\n\nDas Register listet kommerzielle Dienste auf, die Steam-Identitäten, Bestände, Bots und Übertragungen als Betriebsinfrastruktur nutzen. Die SSA verbietet die kommerzielle Nutzung und Automatisierung ohne Genehmigung. Aus den archivierten Beschwerden geht hervor, dass diese Regel auf einzelne Konten angewendet wurde, während die öffentlichen Aufzeichnungen keine entsprechenden, nach Betreibern gegliederten Angaben für die hier dokumentierten Plattformen enthalten. Veröffentlichen Sie die Vorschrift, die Beweise und die Durchsetzungsentscheidung für jeden einzelnen Fall.\n\n189Websites, die in den Prüfungsumfang fallen\n44Routen mit separaten Domains im Live-Register – 27 mit einer veröffentlichten Nachweisdatei, 17 manuell erfasst. Allein durch das Browser-Audit der 189 Websites konnten 25 davon behoben werden; das Register ergänzt diese um die manuell erfassten Routen.\n12 Jahre und 6 Monatecsgogem.com wurde im Link-Filter blockiert; api.csgem.com registriert am 2014-03-08 und nie gesperrt – eines von 26 solchen Paaren (Stand: 2026-09-22)\nKeine verifizierte GesamtsummeSchätzung des marktweiten Umsatzes nicht berücksichtigt\nSteam Verhalten im Internet\n„…Sie dürfen auf Steam keine der folgenden Handlungen vornehmen oder versuchen, diese vorzunehmen: […] Kommerzielle Aktivitäten ausüben. Beispiele für solche verbotenen Verhaltensweisen sind unter anderem: das Veröffentlichen von Anzeigen; das Durchführen von Gewinnspielen; Glücksspiel; der Kauf oder Verkauf von Steam-Konten; der Verkauf von Inhalten, Geschenkkarten oder anderen Artikeln; sowie Betteln.\"\n\nstore.steampowered.com/online_conduct ↗ archiviert 2026-09-21 ↗\n\nSSA § 2.G – Kommerzielle Nutzung\n„…[Sie dürfen] die Inhalte und Dienste oder Teile davon nicht für kommerzielle Zwecke nutzen, es sei denn, dies ist an anderer Stelle in dieser Vereinbarung ausdrücklich gestattet…“\n\nWie berichtet, wurde in den Bescheiden von Valve aus dem Jahr 2016 die persönliche, nichtkommerzielle Lizenz geltend gemacht. Bislang hat kein Betreiber eine Valve-Genehmigung vorgelegt. store.steampowered.com/subscriber_agreement ↗ archiviert 2026-09-18 ↗\n\nSteam Nutzungsbedingungen für die Web-API\n„Sie dürfen die Steam Web-API oder die Steam Daten nicht in einer Weise nutzen, die gegen die Steam Abonnentenvereinbarung verstößt.“\n\nSkin-Marktplätze von Drittanbietern werden über automatisierte Konten betrieben, die die Steam-API nutzen. Der Regeltext sieht keine Ausnahme für den gewerblichen Betrieb vor. steamcommunity.com/dev/apiterms ↗ archiviert 2026-09-21 ↗\n\nSSA § 4.C\nAutomatisierung\n\nSkripte, Bots und nicht-menschliche Interaktionen sind eingeschränkt. Das Ledger erfasst Bot-Handel, Account-Farmen und automatisierte Weiterleitungen im kommerziellen Maßstab.\n\nPrüfen 153Datensätze, die unter dieser Klausel gekennzeichnet sind ↗\nWas unter dieser Klausel in den Unterlagen vermerkt ist153 mit Tags versehene Plattformen\nEröffnung des Verfahrens15\nSkin Casino13\nCS2-Markt9\nHaut-Roulette8\ncsgoempire.com→csgoempirelogin4.comCasino\nrollbit.com→rbsnin.comKrypto-Casino\n500.casino→fivezerozero.coLizenziertes Casino\n\nDavon 153 sind außerdem unter SSA § 2.G und 2 sind außerdem unter SSA § 1.C aufgeführt – dieselben Dienstleistungen fallen unter mehr als eine Klausel, weshalb sich die Beispiele wiederholen.\n\n28 Es wurden Fälle festgestellt, in denen die „153“ sich über eine separate, registrierbare Domain authentifiziert haben. Ein Tag dokumentiert eine datierte Feststellung, die die Plattform dem Wortlaut der Klausel nach erfasst; es handelt sich dabei nicht um einen gerichtlich festgestellten Verstoß, und für keinen der Fälle wurde eine Genehmigung der „Valve“ vorgelegt.\n\nSSA § 2.G\nKommerzielle Nutzung\n\nDie kommerzielle Nutzung bedarf einer ausdrücklichen Genehmigung. Vergleichen Sie die dokumentierten Geschäftsmodelle, deren Umfang sowie etwaige offengelegte Genehmigungen oder Durchsetzungsmaßnahmen.\n\nPrüfen 175Datensätze, die unter dieser Klausel gekennzeichnet sind ↗\nWas unter dieser Klausel in den Unterlagen vermerkt ist175 mit Tags versehene Plattformen\nEröffnung des Verfahrens15\nSkin Casino13\nCS2-Markt9\nHaut-Roulette8\ncsgoempire.com→csgoempirelogin4.comCasino\nrollbit.com→rbsnin.comKrypto-Casino\n500.casino→fivezerozero.coLizenziertes Casino\n\nDavon 153 sind außerdem unter SSA § 4.C und 24 sind außerdem unter SSA § 1.C aufgeführt – dieselben Dienstleistungen fallen unter mehr als eine Klausel, weshalb sich die Beispiele wiederholen.\n\n28 Es wurden Fälle festgestellt, in denen die „175“ sich über eine separate, registrierbare Domain authentifiziert haben. Ein Tag dokumentiert eine datierte Feststellung, die die Plattform dem Wortlaut der Klausel entsprechend erfasst; es handelt sich dabei nicht um einen gerichtlich festgestellten Verstoß, und für keinen dieser Fälle wurde eine Genehmigung der „Valve“ vorgelegt.\n\nSSA § 3.A\nVPN & Standortverschleierung\n\nDie Verschleierung des Standorts durch IP-Proxying kann zur Kündigung führen. Authentifizierungshosts mit separaten Domänen erfordern eine gesonderte Analyse: Es muss festgestellt werden, was verschleiert wird und welche Regel gilt.\n\nÜberprüfen Sie die Nachweise für den Auth-Host ↗\nSteam Hilfe / URL-Richtlinie\nLink-Verschleierung\n\nSteam verbietet Linkverkürzer und Tools, die das Ziel von Links verschleiern. Eine separate Authentifizierungsdomäne — rbsnin.com im Anmeldeablauf von Rollbit, auth.dota.trade in CS.MONEY – wirft die vergleichbare Frage auf, ob die dem OpenID-Verifizierer von Steam angezeigte Zieladresse die Betriebsstätte identifiziert.\n\nDie URL-Richtlinie von Valve ↗\n\nVerweise auf Vorschriften: Steam Abonnentenvertrag, Fassung vom 10. September 2026 archiviert 2026-09-18 ↗ · Steam Nutzungsbedingungen für die Web-API archiviert 2026-09-21 ↗ · Steam URL-Richtlinie (Verschleierung von Links). Die Zahlen beziehen sich auf die Einträge und Tags in diesem Dossier; es handelt sich nicht um die Anzahl der rechtskräftig festgestellten Verstöße.\n\nDas Vertrauensdefizit\nWer überprüft die Entscheidung, wenn die Fälligkeitsstelle den Fall abschließt?\n\nDie aufbewahrten Beschwerden beschreiben dauerhafte Sanktionen, unbeantwortete Einsprüche und die Weigerung, gestohlene Gegenstände zurückzugeben. Vergleichen Sie diese Berichte mit dem tatsächlichen Ticketverlauf, den verfügbaren Abhilfemaßnahmen und den Zugriffsprotokollen für die Konten. Eine allgemeine Erklärung im Zusammenhang mit Phishing reicht nicht aus, um festzustellen, wer eine Zurücksetzung veranlasst oder einen API-Schlüssel erstellt hat.\n\nLesen Sie die erfassten Beschwerden ↗Die zugrunde liegenden Unterlagen anfordern →Beziehungsdiagramm des Moderators →\nTeil B – Vorschriften und Durchsetzungsbilanz · § 10\nEine API zur Automatisierung. Eine Regel gegen Automatisierung.\nKontext und Quellenbeschränkungen\n\nDie Frage, die in diesem Abschnitt gestellt wird, lautet, wie sich beides miteinander vereinbaren lässt: Welche Nutzungen der API sind zulässig, durch wen und nach welchen veröffentlichten Kriterien? Eine Schätzung der Anzahl der autorisierten kommerziellen API-Nutzer wird hier nicht vorgenommen, und das Fehlen einer veröffentlichten Liste lässt auch keine solche Zahl vermuten – das Fehlen selbst ist die Feststellung, nicht eine dahinterstehende Zahl. Die oben zitierten Steam Support-Nachrichten werden vom ArchiSteamFarm-Projekt in seinen eigenen FAQ wiedergegeben (wortgetreu überprüft 2026-09-22); es handelt sich dabei nicht um Valve Veröffentlichungen, und die Konten, an die sie gesendet wurden, sind nicht identifiziert.\n\nDie Vorschrift (SSA § 4.C): Keine Skripte, keine Bots, keine nicht-menschlichen Systeme auf Steam. Die Bilanz: Valve stellt eine Headless-REST-API bereit, deren einziger Zweck die Server-zu-Server-Automatisierung ist, und übergibt den Schlüssel an jedes beliebige Konto. Nutzer werden wegen Automatisierung gesperrt; die Automatisierungsschnittstelle ist ein eigenes Produkt von Valve. Welche kommerziellen Verwendungszwecke zulässig sind, wurde nie veröffentlicht.\n\nDer Irrtum des „Spieleentwicklers“\nSteamworks SDK (Original)\n\nWird von seriösen Spielestudios genutzt, um Erfolge, Matchmaking und Bestenlisten in ihre Spiel-Clients zu integrieren. Erfordert eine komplexe C++-Integration und die Aufnahme als offizieller Partner.\n\nSteam Web-API (Die Lücke)\n\nEine „headless“ JSON/REST-Architektur, die für externe Webserver konzipiert ist. Im hier dokumentierten „Hijack“-Muster wird sie zum Auslesen von Bestandslisten und zur Manipulation von Peer-to-Peer-Transaktionen von Remote-Servern verwendet; ihre legitimen Anwendungsfälle werden in diesem Dossier nicht aufgeführt.\n\nFür wen der Schlüssel bestimmt istEin gewöhnlicher Steam-Nutzer benötigt innerhalb der App keinen Web-API-Schlüssel; die Schlüsselseite ist unter einer Entwickler-URL zu finden und dient laut Dokumentation dem externen, serverseitigen Zugriff. Die archivierten Beschwerden über Kontoübernahmen beschreiben Opfer, die nichts von der Existenz dieser Seite wussten, bis ein Schlüssel für ihr Konto registriert worden war.\nDer Widerspruch der Automatisierung\n\nSSA § 4.C sieht vor: „Es ist Ihnen untersagt, in irgendeiner Weise Skripte, Bots, Makros oder andere nicht von Menschen gesteuerte Systeme („Automatisierung“) zu verwenden, um mit den Inhalten und Diensten auf Steam zu interagieren.“ Allerdings sind die Web-API-Endpunkte (wie CancelTradeOffer) erfordern weder eine Benutzeroberfläche noch ein Captcha und umgehen den Steam-Client vollständig. Die API ist für die Server-zu-Server-Automatisierung konzipiert; die Regel verbietet die Automatisierung durch Benutzer; die Grenze zwischen beiden ist nicht veröffentlicht.\n\nEine serverseitige Position im Handelsablauf\n\nMit einem Web-API-Schlüssel kann ein Server eines Drittanbieters ohne den Steam-Client Transaktionen auf dem Konto ausführen. Beim „Hijack“-Muster befindet sich dieser Server zwischen dem Kontoinhaber und dem Handelsserver.\n\n→Für die Aktionen der Taste wird kein Bestätigungsbildschirm angezeigt.\n→Ermöglicht die Abfrage im Hintergrund (GetTradeOffers).\n→Storniert Angebote und gibt sie erneut aus, ohne dass ein Eingreifen des Benutzers erforderlich ist.\nValve hat die Benutzeroberfläche entwickelt, in seinen Regeln die Automatisierung durch Nutzer untersagt und keine Kriterien veröffentlicht, nach denen kommerzielle Nutzungen zulässig sind.\nTeil B – Vorschriften und Durchsetzungsbilanz · § 11\nZehn Tage wurden gefordert. Zehn Jahre müssen abgerechnet werden.\nKontext und Quellenbeschränkungen\n\nAm 20. Juli 2016 setzte der Leiter der Rechtsabteilung von Valve den Glücksspielanbietern eine Frist von 10 Tagen. Zehn Jahre später (Stand der Dossier-Momentaufnahme, 2026-09-21) ist mindestens eine Plattform, die in Presseberichten zu dieser Mitteilung namentlich genannt wurde – CSGOFast –, weiterhin mit einem Auth-Host unter einer separaten Domain in Betrieb. Der Wortlaut wurde im Folgenden anhand von Presseberichten vom 21. Juli 2016 rekonstruiert; es handelt sich nicht um einen Scan. Das in der Mitteilung angedeutete Durchsetzungsprotokoll wurde nicht veröffentlicht. Der offene Brief an die Kommission lautet Abschnitt 2.\n\nLesen Sie die Mitteilung vom Juli 2016 neben den späteren Bemerkungen. Was noch aussteht, ist eine Aufstellung der Durchsetzungsmaßnahmen nach einzelnen Betreibern.\n\nEine Woche zuvor – am 13. Juli 2016, in der Öffentlichkeit\n\nAm 13. Juli 2016 archiviert 2026-09-21 ↗, Valve beschrieb, wie Glücksspielseiten Steam nutzten: OpenID zur Kontoidentifizierung und automatisierte Konten für den Handel. Valve erklärte, dass die Nutzung dieser Mechanismen zum Betreiben eines Glücksspielunternehmens gegen die API- und Nutzungsbedingungen verstoße. Sowohl die Beschreibung des Mechanismus als auch das Verbot sind in der datierten Erklärung von Valve selbst enthalten. Am 2026-09-21 haben die getesteten Auth-Hosts mit separaten Domänen keine Blockierung durch den Link-Filter zurückgegeben, und Valve hat keinen betreiberspezifischen Durchsetzungsdatensatz veröffentlicht.\n\nANLAGE A / JULI 2016REKONSTRUKTION DER SCHRIFTZUSAMMENSETZUNG\nVALVE CORPORATION\n\nBellevue, WA\n\nDATUM:Juli 2016 (Pressemeldung vom 21. Juli 2016)\nVON:Karl Quackenbush, Leiter der Rechtsabteilung\nBetreff:Unterlassungsaufforderung – kommerzielle Nutzung von Steam-Konten\nHINWEIS:Rekonstruktion des gemeldeten Textes; kein Scan\n\n„Uns ist bekannt, dass Sie eine der unten aufgeführten Glücksspiel-Websites betreiben. Sie nutzen Steam Konten, um dieses Geschäft zu betreiben. Gemäß der Steam Nutzungsvereinbarung sind die Dienste Steam und Steam ausschließlich für den persönlichen, nicht kommerziellen Gebrauch lizenziert.“\n\n„Sie sollten die weitere Nutzung Ihrer Steam-Konten für kommerzielle Zwecke unverzüglich einstellen. Sollten Sie dies nicht tun, innerhalb von zehn (10) Tagen, Valve wird alle verfügbaren Rechtsmittel ausschöpfen, einschließlich, aber nicht beschränkt auf die Kündigung Ihrer Konten.\"\n\nRekonstruktion der Akte · Quelldokument einsehen\nKarl Quackenbush\nLeiter der Rechtsabteilung, Valve Corp.\nAM RAND / LEITARTIKEL\nZehn Tage.Und was dann?\n\nDie Frist war klar festgelegt. Das sollte auch bei der Umsetzung durch die Öffentlichkeit der Fall sein.\n\nValves veröffentlichte Stellungnahme zu „2016“ ↗\nEin Hinweis zur Frist +\nSATIRE / KEINE ENTSPRECHUNG ZU „VALVE“\n\nLiebe Frist,\n\nDir wurden zehn Tage gegeben. Aus irgendeinem Grund war der Kalender das Einzige, was noch funktionierte.\n\nBitte leiten Sie jede Antwort an das öffentliche Register weiter.\n\nZeitleisteJuli 2016 – September 2026\nFrist in der Bekanntmachung:\n10 Tage\nJuli 2016\nSeit der Mitteilung verstrichene Zeit:\n3,715 Tage\nFeste Zahl vom 20. Juli 2016 bis zur Momentaufnahme der Akte vom 21. September 2026, keine Echtzeitzahl\nVeröffentlichte Vollstreckungsakte:\nKeine\nEs wurde keine nach Betreibern aufgeschlüsselte Aufstellung der Kündigungen oder Sperrungen gefunden\n\n◀ Tage 0–10 — die Frist, skalierbarTag 3715 — der Schnappschuss ▶\n\n20. Juli 2016Zehntägige Aufforderung erlassenTag 0\n17. Februar 2024Es gelten die DSA-VerpflichtungenTag 2,768\n25. Februar 2026Klage des Generalstaatsanwalts von New York angekündigtTag 3,507\n21. September 2026Übersicht über das DossierTag 3715\n\nZehn Jahre später, CSGOFast — das in Presseberichten zu den Meldungen aus dem Jahr 2016 genannt wurde — ist in Betrieb: csgofast.com löste bei 2026-09-19 und 2026-09-21 eine Blockierung durch den Link-Filter aus, während sein Auth-Host steam-login.authtofast.com (registriert 2026-06-30) tat dies nicht.\n\nVollständige, datierte Aufzeichnung der Sicherheitsänderungen von Valve: Sicherheitszeitleiste → · Die Rechtsprechung in Washington und der Maßstab für die Durchsetzung: unten\n\nWas aus den Akten hervorgeht: In der Mitteilung von 2016 wurde eine Frist von 10 Tagen festgelegt; Valve betrieb bereits eine Domain-Liste (den „Link Filter“) und erhielt die autorisierten Hostnamen in seinen eigenen OpenID-Anfragen; es wurde kein Durchsetzungsbericht pro Betreiber veröffentlicht. Berichte aus der Community beschreiben eine Maßnahme aus dem Jahr 2018 gegen einen Marktplatz (SkinJar), doch diese Berichte sind unbestätigt und werden hier nicht herangezogen.\nCSGOFAST / DER SPEICHERTE AUTHENTIFIZIERUNGSPROZESS\nFolgen Sie dem angegebenen Rückgaberechner.\n\nDie Links zu den gespeicherten Routenaufzeichnungen csgofast.com zu steam-login.authtofast.com. Der separate Hostname wird in der OpenID-Anfrage Steam übermittelt. Er liefert den Ermittlern eine konkrete Adresse, die sie mit den Filter- und Durchsetzungsaufzeichnungen von Valve abgleichen können.\n\nSehen Sie sich die CSGOFast-Route und deren Quelle an ↗ · Gespeicherte Ergebnisse vergleichen Steam Linkfilter-Ergebnisse ↗\n\nÖFFENTLICHES REGISTER / WASHINGTON · 2016 → 2026\nZwei Fristen. Ein ungeklärter Durchsetzungsmaßstab.\n20. Juli\nValve räumt Glücksspielseiten eine Frist von 10 Tagen ein\n\nIn der Aufforderung des Anwalts des Unternehmens wurde darauf hingewiesen, dass eine fortgesetzte gewerbliche Nutzung von Steam-Konten zur Kündigung führen könnte.\n\n27. SEP\nWashington drängt Valve\n\nDie staatliche Glücksspielkommission forderte Nachweise für Maßnahmen zur Unterbindung von Skin-Transfers für Glücksspielzwecke und setzte eine Antwortfrist bis zum 14. Oktober fest.\n\n17. OKT.\nValve weist den Vorwurf zurück\n\nValve antwortete nach Ablauf der Frist, bestritt, Glücksspiele zu ermöglichen, gab an, die betreffenden Konten deaktiviert zu haben, und erklärte, man wolle den Handel und OpenID nicht für alle Nutzer deaktivieren. Mindestens eine Plattform, die in Presseberichten über die Mitteilungen vom Juli genannt wurde (CSGOFast), war ein Jahrzehnt später noch in Betrieb. Beide Tatsachen können nur zutreffen, wenn der Betreiber die deaktivierten Konten ersetzt hat; die Aufzeichnungen, die dies belegen würden, wurden nicht veröffentlicht. Die WSGC sollte Valve auffordern, diese beiden Sachverhalte in Einklang zu bringen.\n\n2026\nDie im September 2026 beobachteten Routen\n\nDas Routenregister verzeichnet 44 Plattformen, die sich über Authentifizierungsserver in separaten Domänen, darunter CSGOFast, authentifizieren und dabei die 2016 beschriebenen OpenID- und Handelsmechanismen Valve nutzen. Der Durchsetzungsbericht, aus dem hervorgehen würde, welche Betreiber gesperrt wurden, wurde nicht vorgelegt.\n\nEIGENE INFORMATION DER KOMMISSION · 30. JANUAR 2018\nAchtzehn Monate nach der Antwort von Valve bezeichnete die Aufsichtsbehörde dies immer noch als Absichtserklärung.\n\nBei der öffentlichen Anhörung zu HB 2881 beschrieb die Kommission vor dem eigenen Landtag die Erklärung vom Juli 2016 mit eigenen Worten: Valve „kündigte an, entschlossen gegen die Nutzung seiner Plattform zur Ermöglichung von Glücksspielen mit Skins vorzugehen.“ Auf derselben Seite wird beschrieben, wie sich diese Ankündigung auf die Branchenprognose ausgewirkt hat — „infolgedessen“, Die Prognose für den Skin-Gambling-Markt im Jahr 2020 wurde von $19.7 Milliarden zu $670 Millionen, ein Rückgang um etwa 97 Prozent, allein aufgrund der Ankündigung. Die Prognose wurde angepasst. Der Durchschnittswert pro Betreiber, der dies rechtfertigen würde, wurde noch immer nicht veröffentlicht.\n\nBei den Marktzahlen handelt es sich um Schätzungen von Narus Advisors / Eilers & Krejcik Gaming, die im Briefing der Kommission wiedergegeben wurden, nicht um Erkenntnisse der Kommission; demselben Dokument zufolge beliefen sich die Einsätze bei „Skin-Wetten“ im Jahr 2016 auf etwa $5 Milliarden, davon etwa $3 Milliarden auf Websites im Casino-Stil. Abgerufen am 2026-09-22, SHA-256 c507c9025f93da0aadaf395c4d8882f25973211c318ee8e9b6f18a5b3755e050.\n\nDie öffentliche Stellungnahme von Valve aus dem Jahr 2016 lässt sich mit der heute sichtbaren Infrastruktur vergleichen. Die Frage ist, ob die Durchsetzungsmaßnahmen auch die Konten und Routen der verbotenen Betreiber erfasst haben. Eine zehntägige Frist ist kein Beweis dafür, dass die Benachrichtigung bei allen darin genannten Betreibern erfolgt ist. Die OPSkins-Maßnahme aus dem Jahr 2018 ist die einzige dokumentierte Intervention gegen einen namentlich genannten Betreiber; vor dem Hintergrund von 189 überprüften Plattformen und keiner veröffentlichten Aufschlüsselung nach Betreibern lässt eine einzige dokumentierte Maßnahme kein Muster der Durchsetzung erkennen.\n\nBekanntmachung der Glücksspielkommission von Washington aus dem Jahr 2016 ↗ archiviert 2026-05-20 ↗ · Antwort von Valve vom 17. Oktober 2016 (Kopie des Dokuments) ↗ · WSGC-Informationsveranstaltung vor dem Landtag, 30. Januar 2018 (lokale Kopie, 4 Seiten) ↗ · die gleiche Datei auf wsgc.wa.gov ↗ · Abrufdatensatz & Hash ↗ · Valves OPSkins-Aktion 2018 ↗ archiviert 2026-03-07 ↗ · Aktuelle Routenprüfung ↗\n\nForensische Längsschnittprüfung · Adressaten der Unterlassungsaufforderungen aus dem Jahr 2016\nDas Jahrzehnt der 10-Tage-Frist: Forensische Überlebensprüfung der 23 genannten Standorte\n\nAm 19. und 20. Juli 2016 erließ Valve General Counsel Karl Quackenbush formelle Unterlassungsaufforderungen an 23 Skin-Glücksspielplattformen und wies diese an, die kommerzielle Nutzung von Steam-Konten innerhalb von 10 Tage unter Androhung der Kontosperrung und rechtlicher Schritte. Mehr als 3,700 Tage später deckt eine empirische Überprüfung das tatsächliche Durchsetzungsmuster auf: Zahlreiche Betreiber haben ihren Betrieb nie eingestellt, andere waren auch nach Ablauf der Frist noch bis zu sechs Jahre lang aktiv, und das milliardenschwere Ökosystem nutzte weiterhin die OpenID-Architektur von Valve.\n\n5+ LIVE\nWird 2026 definitiv in Betrieb sein (CSGOBig, CSGO500, CSGOFast usw.)\n6 JAHRE\nLängster Betrieb nach Bekanntgabe vor der Schließung (CSGOatse war bis 2022 aktiv)\n$5.01B\nWettvolumen im Bereich „Skin“ im Jahr 2016 (Narus / Eilers & Krejcik)\n200+\nAktive Glücksspiel-Websites, die auf dem Höhepunkt des Marktes tätig sind\nDie „Surviving Titans“ · Finanz- und Besucherzahlenplan 2024–2026\nVon 10-Tage-Warnungen bis hin zu Offshore-Konzernen: Der Umsatz in Milliardenhöhe\n\nAnstatt das „Skin-Glücksspiel“ zu unterbinden, haben die Bekanntmachungen von Valve aus dem Jahr 2016 eine industrielle Entwicklung vorangetrieben. Die überlebenden Betreiber strukturierten sich als Offshore-Unternehmen (Curaçao, Belize, Zypern) um, leisteten Pionierarbeit beim Peer-to-Peer-Handel (P2P), um Bot-Verbote zu umgehen, und wickeln mittlerweile über 10 Millionen Webbesuche pro Monat und Milliarden Dollar an jährlichem Wettumsatz wobei die Authentifizierung weiterhin über Steam erfolgt:\n\nPlattform / Domain\tMitteilung vom Juli 2016\tErgebnis der Vollstreckung und Überlebensstatus\tProtokollierte Überprüfung / Primäre Links\nCSGOBig\ncsgobig.com\t10-Tage-Frist (Juli 2016)\tIM JAHR 2026 NOCH IMMER AM LEBEN\nVorübergehend ausgesetzt, wieder aufgenommen; Authentifizierung über letmeinbig.com und csgobiglogin.com\tX: @csgobig ↗ · FB: csgobigofficial ↗\nCSGO500\ncsgo500.com / 500.casino\t10-Tage-Frist (Juli 2016)\tIM JAHR 2026 NOCH IMMER AM LEBEN\nUmbenannt in 500 Casino (Curaçao-Lizenz Nr. 8048/JAZ2014-037), monatlicher Umsatz in Millionenhöhe\tLive-Plattform (500.casino) ↗\nCSGOFast\ncsgofast.com\t10-Tage-Frist (Juli 2016)\tIM JAHR 2026 NOCH IMMER AM LEBEN\nAktiver Betrieb von Roulette, Crash und Jackpot über steam-login.authtofast.com\tDossier-Authentifizierungsprüfung ↗\nCSGOLounge / Dota2Lounge\ncsgolounge.com / dota2lounge.com\t10-Tage-Frist (Juli 2016)\tIM JAHR 2026 NOCH IMMER AM LEBEN\nFokus auf Wetten mit E-Sport-Coins und Krypto-Wetten; Aufrechterhaltung des kontinuierlichen Betriebs\tLive-Plattform ↗\nCSGOCasino\ncsgocasino.net / csgocasino.gg\t10-Tage-Frist (Juli 2016)\tLIVE VIA SUCCESSOR (2026)\nDie Domain wurde umgeleitet; das aktive Nachfolgeportal ist unter csgocasino.gg erreichbar.\tNachfolgende Domäne ↗\nCSGOatse\ncsgoatse.com\t10-Tage-Frist (Juli 2016)\t6 JAHRE ÜBERLEBT (AKTIV BIS 2022)\nDer Glücksspielbetrieb wurde nach dem 10-tägigen Ultimatum von Valve sechs Jahre lang uneingeschränkt fortgeführt\tX: @CSGOatsecom (aktiv bis 2022) ↗\nCSGOSweep\ncsgosweep.com\t10-Tage-Frist (Juli 2016)\tBIS DEZEMBER 2017 ÜBERLEBT\nWurde nach Ablauf der Frist noch 17 Monate lang öffentlich betrieben\tX: CSGOSweep-Status Dez. 2017 ↗\nCSGOWild\ncsgowild.com\t10-Tage-Frist (Juli 2016)\tBIS DEZEMBER 2017 ÜBERLEBT\nVon bedeutenden Influencern beworben; lief nach der Unterlassungsaufforderung noch 1,5 Jahre weiter, bevor die Umstellung auf Kryptowährung erfolgte\tX: @Wild (aktiv seit Dez. 2017) ↗\nCSGOPot\ncsgopot.com\t10-Tage-Frist (Juli 2016)\tBIS SEPTEMBER 2017 ÜBERLEBT\n14 Monate nach der Bekanntgabe wurden weiterhin Jackpot-Wetten mit hohen Einsätzen angeboten\tX: @csgopot (aktiv im September 2017) ↗\nCSGODiamonds\ncsgodiamonds.com\t10-Tage-Frist (Juli 2016)\tHAT BIS MITTE 2017 ÜBERLEBT\nLief bis 2017 weiter, obwohl zugegeben wurde, dass die Ergebnisse für gesponserte Streamer manipuliert wurden\tX: @csgodiamondscom (2017) ↗\nCSGOLotto\ncsgolotto.com\t10-Tage-Frist (Juli 2016)\tGESCHLOSSEN IM JULI 2016\nWegen eines öffentlichen Skandals geschlossen; Gegenstand einer Einverständniserklärung der US-Kartellbehörde FTC\tEinverständniserklärung der FTC (Aktenzeichen C-4632) ↗\nCSGODouble\ncsgodouble.com\t10-Tage-Frist (Juli 2016)\tGESCHLOSSEN IM JULI 2016\nSofortige freiwillige Einstellung des Betriebs nach Veröffentlichung der Unterlassungsaufforderung\tX: @CSGODouble (im Juli 2016 geschlossen) ↗\nCSGOMassive\ncsgomassive.com\t10-Tage-Frist (Juli 2016)\tGESCHLOSSEN 2016\nDer öffentliche Betrieb wurde Ende 2016 eingestellt\tX: @csgo_massive ↗\nCSGOStrong\ncsgostrong.com\t10-Tage-Frist (Juli 2016)\tGESCHLOSSEN 2016\nHat den öffentlichen Betrieb im Jahr 2016 eingestellt\tFB: csgostrongfree ↗\nSkins2\nskins2.com\t10-Tage-Frist (Juli 2016)\tGESCHLOSSEN 2016\nHat den öffentlichen Betrieb im Jahr 2016 eingestellt\tFB: CSNCOM ↗\n\nPlattform\tMonatliche Besucherzahlen (Besuche)\tGeschätzter Umsatz / Volumen\tRechtsform und Gerichtsbarkeit\tWichtige regulatorische Maßnahmen und Modell\nCSGOEmpire\ncsgoempire.com\t2,3 Mio. – 9,0 Mio. / Monat\nDurchschnittliche Dauer: 6+ Minuten; 80% direkt\t$1.5B — $2.5B Jährlicher Umsatz\n>1,000,000 P2P-Skin-Trades pro Monat; $6.4M aktiver Liquiditätspool\tMoonrail Limited B.V. (Curaçao Nr. 148182)\nZahlungen: JHOLT LTD (Zypern); Gründer: „Monarch“ (Ossi Ketola)\tPionier des gebührenfreien P2P-Handels mit Gegenständen; lizenziert in Curaçao unter der Nummer OGL/2024/1183/0869\nCSGORoll\ncsgoroll.com\t2,74 Mio. – 3,5 Mio. / Monat\nDurchschnittliche Dauer: 9 Minuten 23 Sekunden; Absprungrate: 16%\t$1.0B — $2.0B Jährlicher Umsatz\nGeschätzter Jahresumsatz des Unternehmens aus dem Hausvorteil: $100M–$200M\tFeral Holdings Limited\nMit Hauptsitz in Belize City, Belize (Reg.-Nr. 171519)\tVon der australischen ACMA gesperrt (Mai 2023); sponserte das Tier-1-Team G2 Esports mit minderjährigen Spielern\n500 Casino (CSGO500)\n500.casino / csgo500.com\t220.000 – 425.000 / Monat\n~105.000 einzelne Besucher pro Monat\t$100k / Woche ($5.2M/Jahr) in Royales\nUmsatzanforderung für High-Roller: $400 Einsatz pro $1 Rakeback\tPerfect Storm B.V. (Curaçao Nr. 150536)\nLizenz der Glücksspielaufsichtsbehörde von Curaçao OGL/2024/1354/0882\tVon der schwedischen Spelinspektionen (Nov. 2023) wegen nicht genehmigter Werbung für schwedische Spieler gesperrt\nCSGOBig\ncsgobig.com\t~169,600 / Monat\nDurchschnittliche Dauer: 19 Min. 12 Sek.; US-Vorwahlen\tJährliches Umsatzvolumen in Millionenhöhe\nÜberraschungskisten, Roulette und Kistenkämpfe\tFunktioniert über zusätzliches Proxy-Routing\nletmeinbig.com (registriert 2023) & csgobiglogin.com\tZiel des C&D vom Juli 2016; mit Proxy-Authentifizierungsarchitektur neu gestartet\nCSGOFast\ncsgofast.com\tca. 150.000 – 250.000 / Monat\nEin weltweites, mehrsprachiges Publikum\tJährliches Umsatzvolumen in Millionenhöhe\nHochgeschwindigkeits-Roulette und Crash-Spiele\tOffshore-Betriebsgesellschaften\nRouten Steam Authentifizierung über steam-login.authtofast.com\tZielobjekt der Unterlassungsklage vom Juli 2016; Betrieb wurde nie eingestellt; im Jahr 2026 noch aktiv\nCSGOPolygon\ncsgopolygon.com / plg.bet\t~300.000 – 500.000 / Monat\nDie Vorherrschaft der GUS-Staaten und Osteuropas\tJährliches Umsatzvolumen in Höhe von mehreren Millionen\nKrypto- und Skin-Roulette, Match-Wetten\tZiel der zweiten Welle (Okt. 2016)\nUmstellung auf Kryptowährung mit der Spiegeldomain plg.bet\tHat ein ganzes Jahrzehnt überstanden; setzt die Skin-Liquidation über APIs von Drittanbietern fort\nDie zweite Welle: Warum die Unterlassungsaufforderungen von Valve insgesamt mehr als 43 Websites betrafen\n\nAm 17. Oktober 2016 teilte der Rechtsbeistand von Valve der Glücksspielkommission des Bundesstaates Washington offiziell mit, dass Valve nach den ersten 23 Mitteilungen vom 19. Juli Unterlassungsaufforderungen an mehr als 20 weitere Skin-Glücksspielseiten (wodurch die offizielle Gesamtzahl auf über 43 stieg). Diese zweite Runde war notwendig geworden, da in der ursprünglichen Liste aus unerklärlichen Gründen die größten und berüchtigtsten Glücksspielzentren der Welt nicht aufgeführt waren:\n\nCSGOJackpot.com: Der historische Pionier der „Skin-Jackpots“, der ein Volumen von mehreren hundert Millionen abwickelte, bevor er unter Androhung einer Anklage durch die Bundesbehörden den Betrieb einstellte.\nCSGOShuffle.com: Die Plattform, die im Mittelpunkt des Streaming-Skandals vom Juli 2016 stand, bei dem der Twitch-Streamer PhantomL0rd heimlich 33% des Unternehmens besaß und dabei überführt wurde, mit firmeneigenen Mitteln die Gewinnchancen manipuliert zu haben.\nDas Makro-Ökosystem (über 200 Betreiber): Laut einer Branchenstudie von Narus Advisors und Eilers & Krejcik Gaming waren im Jahr 2016 über 200 verschiedene Skin-Glücksspielseiten in Betrieb, die mit 3,03 Millionen aktiven Spielern ein Wettvolumen von $5.01 Milliarden erzielten. Die 43 Schreiben von Valve richteten sich an weniger als 20% des aktiven Marktes.\nOffizielle behördliche und aufsichtsrechtliche Ermittlungen zu Steam Skin Gambling\n\nDas Phänomen des „Skin Gambling“ ist in zahlreichen offiziellen behördlichen Untersuchungen, Durchsetzungsmaßnahmen und Stellungnahmen der Regierung dokumentiert:\n\n1. Glücksspielkommission des Bundesstaates Washington (WSGC) (2016–2018)\n\nAm 5. Oktober 2016 wurde eine formelle Unterlassungsaufforderung erlassen; am 30. Januar 2018 wurde ein Gesetzgebungsbericht veröffentlicht, in dem dokumentiert wird, dass „Skins“ als Zahlungsmitteläquivalente gelten, und in dem das Wettvolumen von $5.0B „Skins“ ausgewiesen wird.\n\nWSGC-Gesetzgebungsbericht als PDF (lokale Kopie) ↗\n2. US-Bundeswettbewerbsbehörde (Federal Trade Commission, FTC) (Sept. 2017, Aktenzeichen C-4632)\n\nErste behördliche Durchsetzungsmaßnahme auf Bundesebene im Zusammenhang mit „Skin Gambling“ gegen die CSGOLotto-Eigentümer Trevor Martin und Thomas Cassell wegen irreführender Praktiken und nicht offengelegter Kontrolle über die Plattform.\n\nEntscheidung und Vergleichsvereinbarung der FTC ↗\n3. Positionspapier der britischen Glücksspielkommission (UKGC) und Jugendprüfungen\n\nIm Spiel wurden Skins gemäß dem Glücksspielgesetz von 2005 offiziell als „Geld oder Geldwert“ eingestuft. Nachfolgende Umfragen ergaben, dass über 11% der Kinder im Alter von 11 bis 16 Jahren Skins in Videospielen eingesetzt hatten.\n\nUKGC-Forschungsarchiv ↗\n4. Untersuchung des australischen Senats zu Umwelt und Kommunikation (2018)\n\nBericht des Bundesparlaments über „Mikrotransaktionen in Spielen für zufällig generierte Gegenstände“, wobei die Loot-Box-Mechanismen von Valve, Auszahlungen auf dem Sekundärmarkt und die Umgehung von Vorschriften untersucht werden.\n\nUntersuchung des australischen Parlaments ↗\nDie ausstehende Forderung\n\nVeröffentlichung des Durchsetzungsberichts: Welche Glücksspielkonten und Bots wurden gesperrt, welche Return-Hosts wurden eingeschränkt und welche kommerziellen Dienste erhielten eine Genehmigung? Ein öffentliches Verbot und ein Warnhinweis auf der Startseite bedeuten nicht, dass der zugrunde liegende Betrieb eingestellt wurde.\n\nTeil B – Vorschriften und Durchsetzungsbilanz · § 12\nDer Hostname ist bereits in der Anfrage enthalten.\nKontext und Quellenbeschränkungen\n\nValve verfügt bereits über eine Domänenliste (den Link-Filter) und erhält bei jeder OpenID-Anfrage den Auth-Hostnamen. Der folgende Pseudocode veranschaulicht den logischen Aufbau der Verknüpfung beider Elemente. Es gibt keine öffentlichen Hinweise darauf, dass Valve dies tut.\n\nValve betreibt bereits eine Domain-Blockliste. Valve erhält bereits bei jeder OpenID-Anfrage den Anmelde-Host. Es muss nichts gebaut werden – die beiden müssen nur miteinander verbunden werden. Das ist eine Hostnamenabfrage anhand einer Liste, die Valve selbst verwaltet. Der folgende Pseudocode dient lediglich zur Veranschaulichung und stellt nicht die Implementierung von Valve dar.\n\nforensic_autoban.py\n# VERANSCHAULICHENDER PSEUDOCODE — Valve.block_domain() und flag_session_as_mitm() sind keine echten API-Aufrufe. Dies veranschaulicht die logische Struktur einer Schutzmaßnahme, die Valve gegen Proxy-Authentifizierungsdomänen implementieren könnte, und nicht die tatsächlichen Valve-Interna.\n# Abbildung: Der logische Aufbau einer Überprüfung der eingehenden OpenID-Anfrage\ndef audit_openid_request(Anfrage):\nblocked_origins = database.get_blacklisted_platforms()\nproxy_domain = request.params.erhalten(„openid.realm“)\ntarget_redirect = request.params.erhalten('openid.return_to')\n\n# Logik: Wenn der Proxy zu einer gesperrten Website weiterleitet, wird der Proxy gesperrt.\nfür Website in blocked_origins:\nfalls Website in target_redirect:\nValve.block_domain(proxy_domain)\nValve.flag_session_as_mitm(request.session)\n# Ergebnis: Die Anmeldeanfrage für diesen Host wird abgelehnt.\n\nAnmerkung:\nWenn eine Hauptdomain bereits im Link-Filter enthalten ist (z. B. howl.gg, gesperrt 2026-09-18/19/21) und ihr Authentifizierungshost (howl.uno) in der OpenID-Anfrage über den Anmeldebutton dieser Website erscheint, ist die Zuordnung für Valve anhand der eigenen Anfragedaten erkennbar. Die Überprüfung lässt sich automatisieren; ob sie durchgeführt wird, ist jedoch nicht automatisierbar.\nDokumentierte und gemeldete Präzedenzfälle\n\nValve ist nachweislich mindestens einmal gegen einen Drittanbieter vorgegangen: Im Jahr 2018 entzog es OPSkins den Zugang zum ExpressTrade-System (Valves Ankündigung ↗ archiviert 2026-03-07 ↗). In Community-Berichten aus dem Jahr 2018 wird ebenfalls beschrieben, dass ein Marktplatz (SkinJar) den Zugriff verloren hat; diese Berichte sind unbestätigt, und der Mechanismus wird aus dem Ergebnis abgeleitet, nicht aus einem offengelegten Ablauf.\n\nWas dieser Präzedenzfall festlegt:\n\nValve kann den Zugang eines Drittanbieters nach eigenem Ermessen sperren. CSGOFast, das in Presseberichten zu den Mitteilungen vom Juli 2016 genannt wurde, war auf 2026-09-21 aktiv und verfügte über einen unter 2026-06-30 registrierten Auth-Host, der keine Sperre durch den Link-Filter auslöste. Warum ein Betreiber gesperrt wurde und andere nicht, wird durch keine veröffentlichten Kriterien erklärt.\n\nWas ein Eintragungsdatum aussagt und was nicht\n\nDas Registrierungsdatum eines Auth-Hosts stellt eine Untergrenze dafür dar, wann der Host erstmals in einer OpenID-Anfrage aufgetaucht sein könnte; es belegt jedoch keine kontinuierliche Nutzung. sc-auth.net… wurde beispielsweise unter der Kennung 2019-04-02 (RDAP) registriert und im September 2026 im Anmeldeablauf Steam von Skin.Club beobachtet; was zwischen diesen beiden Zeitpunkten geschah, ist nicht öffentlich bekannt.\n\nVergleichsprüfung: API-Konformitätsstandards\nDurchsetzungsaspekt\tRegeln für die GitHub-API\tSteam Web-API (Valve)\n1. Compliance-Neutralität\tVeröffentlichte, einheitliche Regeln. Dokumentierte Ratenbeschränkungen (z. B. 5,000 Aufrufe/Stunde für authentifizierte Benutzer, 15,000/Stunde für GitHub Enterprise Cloud-Organisationen) und veröffentlichte Richtlinien zur zulässigen Nutzung gelten für jedes Konto.\tEs wurden keine Kriterien veröffentlicht. Einzelne Konten werden aufgrund der Klauseln zur Automatisierung und zur kommerziellen Nutzung (archivierte Beschwerden) gekündigt, während keine Aufzeichnungen über die Durchsetzungsmaßnahmen pro Betreiber für kommerzielle Plattformen veröffentlicht wurden.\n2. Missbrauch von OpenID / Auth-Proxy\tDie von GitHub veröffentlichten Richtlinien sehen vor, dass OAuth-Apps und -Token bei Missbrauch gesperrt oder widerrufen werden können, und in der Dokumentation wird der automatische Widerruf offengelegter Token beschrieben (Zusammenfassung der GitHub-Dokumentation durch die Autoren).\tBei Authentifizierungs-Hosts mit separaten Domänen, die in Steam OpenID-Abläufen beobachtet wurden (z. B. rbsnin.com, howl.uno, sc-auth.net), wurde bei 2026-09-21 kein Block durch den Link-Filter ausgelöst, während dies bei ihren Hauptdomänen der Fall war.\n3. Monetarisierung von Missbrauch\tGitHub erhebt keine Transaktionsgebühren für Artikel, die über Automatisierungslösungen von Drittanbietern verkauft werden; sein Erlösmodell basiert auf Abonnements und Marktplatzangeboten.\tValve verkauft die Kisten-Schlüssel, mit denen die Gegenstände hergestellt werden, und der Community-Markt erhebt eine Gesamtgebühr von etwa 15% auf Verkäufe, die innerhalb des Marktes getätigt werden. Hier werden keine Schätzungen zu den Einnahmen aus Drittplattformen vorgenommen.\n4. Lebensdauer von Ausweichschleifen\tGesperrte OAuth-Client-IDs funktionieren ab dem Zeitpunkt der Sperrung plattformweit nicht mehr; in der Dokumentation wird kein Zeitraum für die Umsetzung genannt, und auch hier wird kein solcher angenommen.\tBei den Authentifizierungshosts mit separaten Domänen und Registrierungsdaten zwischen 2011 und September 2026 wurde bei den Prüfungen von 2026-09-19 und 2026-09-21 keine Sperrung durch den Link-Filter festgestellt. Das Registrierungsdatum stellt eine Untergrenze für die mögliche Nutzung dar, ist jedoch kein Nachweis für eine kontinuierliche Nutzung.\nQuellen: GitHub-Kolumne – Von GitHub veröffentlichte Dokumentation zu API-Ratenbeschränkungen und Plattformrichtlinien (Zusammenfassung der Autoren, nicht wörtlich zitiert) · Steam-Kolumne – Linkfilter-Prüfungen von 2026-09-19 und 2026-09-21 (linkfilter-recheck-2026-09-21.json), RDAP-Register (domain-registration.json) und die archivierten Support-Anfragen (Beweisarchiv).\nTeil B – Vorschriften und Durchsetzungshistorie · § 13\nDie Preisdifferenz zwischen „Off-0“ und „0“\n\nDer Artikel befindet sich in einem Steam-Inventar; der Verkauf findet an anderer Stelle statt. Ein fabrikneues AWP Dragon Lore hatte 62 aktuelle Angebote bei CSFloat; der günstigste Preis $10,623.95. Auf dem eigenen Markt von Steam kann kein Angebotspreis über etwa $1,800 angezeigt werden. Um zu dem beobachteten höheren Preis zu verkaufen, benötigt ein Eigentümer einen Käufer oder Marktplatz außerhalb von Steam. Der Artikel und seine Übertragung hängen weiterhin von Steam ab.\n\nWhat this means — the Community Market listing ceiling\n\nSteam’s own market refuses a listing above roughly $1,800. A seller may ask less, never more. Items whose market price sits above that line therefore cannot be sold at that price on Steam at all — which is the mechanism that moves those sales to third-party venues while the item itself never leaves Valve’s inventory system.\n\nSection 13 — the off-Steam price gap →\n\nKontext und Quellenbeschränkungen\n\nIn diesem Abschnitt werden drei verschiedene Zählweisen aufgeführt, die nicht miteinander austauschbar sind. 245 ist die Anzahl der CS2-Artikelkategorien, deren günstigstes aktives Angebot allein auf CSFloat am 20. September 2026 den Wert $1,800 überschritten hat. 241 Das ist dieselbe Menge abzüglich der vier Kategorien, die an der Obergrenze $100,000 von CSFloat fixiert sind – das ist das Feld, auf dessen Grundlage die Untergrenze $13.63M berechnet wird. 248 ist eine andere Momentaufnahme: Kategorien, deren Preis am 23. September 2026 auf zwei oder mehr von fünf Marktplätzen über der Obergrenze lag. Da sich die Marktplätze überschneiden, dürfen die Zahlen verschiedener Plattformen keinesfalls addiert werden. Jede hier angegebene Zahl ist ein Angebotspreis, kein abgeschlossener Verkauf, und nichts davon stellt Umsatz, Erlös oder Gewinn dar – weder für Valve noch für irgendjemanden sonst. Die von PriceEmpire aufgeführten Werte sind gerundete Schätzungen, die von dieser Website veröffentlicht wurden, und die Steam-Karte umfasst Gegenstände aus anderen Steam-Spielen, sodass die Vergleichsgrundlagen nicht identisch sind.\n\nEin Artikel. Zwei Preissysteme.FOLGEN SIE DER ENTWICKLUNG\nSchritt 3 / 3\n\nBei diesem Angebot benötigt der Verkäufer eine alternative Plattform oder einen Käufer. Der Artikel hängt weiterhin vom Lagerbestand und vom Transfersystem von Steam ab.\n\nSTEAMÜber $1,800Veröffentlichte Obergrenze für Notierungen am Community-Markt\nGESPEICHERTER KATALOG$10,623.95AWP „Dragon Lore“ – brandneu, Preis auf Anfrage\nDIE ABHÄNGIGKEITImmer noch ein Steam-ArtikelDer Bestand und die Übertragung bleiben bei Steam\n01 / ARTIKELValve SpielbestandCS2- oder Dota 2-Gegenstand, der in Steam aufbewahrt wird\n02 / DECKEÜber $1,800 am SteamHöchstpreis für einen Markt-Eintrag\n03 / EXTERNE ANFRAGE$10,623.95 für „Dragon Lore“Das günstigste CSFloat-Angebot in der Momentaufnahme vom [Datum]\n04 / LIEFERUNGSteam bleibt in der Kette erhaltenEigentumsverhältnisse und die Übertragung von Gegenständen basieren auf diesem System\nMARKTSTRUKTUR · MOMENTAUFNAHME VOM 20 SEPTEMBER 2026\nDie Preisdifferenz ist messbar.\n\nWir haben die Kategorien von Artikelnamen gezählt, deren günstigstes aktives Angebot deutlich über1,800. lag. CSFloat und Skinport sind separate Momentaufnahmen mit sich überschneidenden CS2-Beständen; ihre Zahlen lassen sich nicht addieren. Die externen Angebote zeigen, wo höhere Angebotspreise angegeben sind, während Steam weiterhin den Besitz und die Übertragung der Artikel verwaltet.\n\n245CS2-KATEGORIEN · CSFLOAT\n166CS2-KATEGORIEN · SKINPORT\n3DOTA-2-KATEGORIEN · SKINPORT\n$10,623.95DRAGON LORE – BODEN – FRAGE\n\nDragon Lore: 62 bietet in der Kategorie „Factory New“ CSFloat an; der angezeigte Mindestpreis ist ein Angebot und kein bestätigter Verkauf. Steam erlaubt es, den Artikel zu einem niedrigeren Preis einzustellen, verbietet jedoch die Veröffentlichung des beobachteten höheren Angebots. Die Erklärung von Valve unter 2016 bestätigt, dass dem Unternehmen bekannt ist, dass Glücksspielanbieter die Handelsinfrastruktur von OpenID und Steam nutzen. Ob ein bestimmter Drittanbieter-Marktplatz gegen die Regeln von Valve verstößt, muss separat festgestellt werden.\n\nDas vollständige Register einsehen →CSFloat JSON ↗Skinport JSON ↗Valves Stellungnahme zu „2016“ ↗\nDIRECT CSFLOAT API / DATUMSBEZOGENE MOMENTAUFNAHME$13.63M\n\nMindestgesamtschlusspreis in 241 Artikelkategorien und 3,395 aktive Angebote. Berechnet als das günstigste Verkaufsangebot jeder Kategorie multipliziert mit der Anzahl der Angebote. Vier Kategorien, die an die Obergrenze von CSFloat $100,000 gebunden sind, werden aus dieser konservativen Auswertung ausgeschlossen.\n\nWas die Dollarbeträge aussagen\n\nDiese Angebote entsprechen mindestens $13,631,888.25 in den angegebenen Angebotspreisen für diese begrenzte CSFloat-Teilmenge. Bezieht man die vier Kategorien mit Höchstpreisen mit ein, ergibt sich $14,231,888.25. Dies ist ein Mindestpreis bei aktiven Kaufaufträgen, nicht der abgeschlossene Umsatz, der Barumsatz, der Gewinn oder der gesamte CS2-Markt.\n\nNeuberechnung anhand des CSFloat-Snapshots mit 245 Zeilen ↗\nPRICEEMPIRE / ANGEGEBENER WERTSteam: Nr. 15 von 39\nViele Veranstaltungsorte geben einen höheren Dollarwert als Steam an.\nUUSkins\n$133.8M\nYouPin898\n$127.5M\nBuff.163\n$104M\nMoon.Market\n$100.3M\nWhite.Market\n$89.6M\nBuff.Market\n$86.7M\nSteam\n$31M\n\nDie sechs größten angezeigten Werte und Steam. PriceEmpire rundet diese Zahlen; Steam zeigt $31M. Vierzehn der aufgeführten Veranstaltungsorte liegen gemessen an den angegebenen Dollarbeträgen vor diesem.\n\nPRICEEMPIRE / ANZAHL DER ANGEBOTESteam: Platz 1 von 39\nSteam liegt bei der Anzahl der Angebote weiterhin an der Spitze.\nSteam\n32,2 Mio.\nYouPin898\n5,9 Mio.\nC5Game\n4,6 Mio.\nHaloSkins\n4,4 Mio.\nSkinport\n3,8 Mio.\n\nSteam zeigt 32,2 Mio. Angebote. Die Anzahl der Angebote und der Gesamtverkaufspreis geben Aufschluss über unterschiedliche Aspekte; viele preisgünstige Angebote können die Gesamtzahl dominieren.\n\nQuelle: Öffentlicher Vergleich von PriceEmpire ↗ archiviert 2026-09-21 ↗, erfasst am 2026-09-20 um 19:03 UTC; veraltete 39-zeilige Extraktion ↗. Bei den Zahlen handelt es sich um gerundete Schätzwerte, und Bestände können sich standortübergreifend überschneiden. Auf der Karte von Steam sind auch Gegenstände aus anderen Steam-Spielen aufgeführt, sodass die Umfangsangaben nicht identisch sind. Die angegebenen Werte beziehen sich auf die Angebotspreise, nicht auf Verkäufe oder Umsätze.\n42\nEINE WEITERE QUELLE / STEAMANALYST\nDas kommerzielle Ökosystem liegt auf der Hand.\n\nDas Marktplatzverzeichnis von SteamAnalyst archiviert 2026-07-19 ↗ listet 42 CS2-Marktplätze von Drittanbietern neben Steam auf, wobei für 32 der 43 Einträge aktuelle Preisdaten vorliegen. PriceEmpire listet 39 Marktplätze nach seinen eigenen Aufnahmekriterien auf. Namentlich genannte Unternehmen, öffentliche Angebote, sichtbare Preise: Diese Wirtschaft ist für jedermann einsehbar.\n\nDIE OBERGRENZE IST DER MECHANISMUS: DER VERKAUF VERLOR AN DYNAMIK, DER ARTIKEL JEDOCH NICHT.\n\nÜber fünf Marktplätze hinweg, die in einer lizenzierten Momentaufnahme erfasst wurden, 248 Artikelkategorien der CS2 liegen preislich unabhängig voneinander um zwei oder mehr über der von Steam festgelegten Obergrenze von etwa $1,800 – und jede einzelne davon fehlt bei Steam. Derselbe Momentaufnahme unterteilte den gesamten Katalog nach Preis: Der Markt von Valve führt 95.3% der Artikelkategorien unterhalb seiner Obergrenze und 1.9% derjenigen oberhalb davon. Der Einbruch ist nicht auf eine sinkende Nachfrage zurückzuführen; er entspricht genau der veröffentlichten Regel. Der Verkauf zu diesen Preisen erfordert einen externen Käufer oder Marktplatz, während Steam weiterhin die Kontrolle über den Lagerbestand und den Transfer behält – der Geschäftsvorgang verlässt die Kasse von Valve und die Lieferung erfolgt weiterhin über die Infrastruktur von Valve.\n\nSteam Häufig gestellte Fragen zum Markt ↗archiviert 2026-09-21 ↗Steam Abonnentenvertrag ↗archiviert 2026-09-21 ↗Datensatz „Five-Marketplace-Atlas“ ↗Herkunftsnachweis ↗Früherer CSFloat-Snapshot ↗Skinport-Übersicht ↗PriceEmpire ↗archiviert 2026-09-21 ↗SteamAnalyst ↗archiviert 2026-07-19 ↗Preisunterschiedsregister ↗Preisleiter-Atlas ↗\n\nTeil C – Rechtliche Rahmenbedingungen\nTeil C – Rechtliche Rahmenbedingungen · Abschnitt 14 · Zugang für Mitarbeiter\nWer kann die Sicherheitsvorkehrungen zurücksetzen?\nKontext und Quellenbeschränkungen\n\nDie Kontosicherheit hängt auch von den Personen ab, die ein Konto wiederherstellen, private Daten einsehen oder dessen Sicherheitsmaßnahmen zurücksetzen können. Die Untersuchung muss diese privilegierten Aktionen ebenso genau verfolgen wie den Missbrauch der API.\n\nDie Kontowiederherstellung gibt einem Support-Mitarbeiter die Befugnis, ein Konto seinem Inhaber zu entziehen. Valve hat zweimal – im Februar 2023 und im November 2025 – schriftlich bestätigt, dass diese Befugnis dazu genutzt wurde, Konten an die falschen Personen zu übertragen. Im Abstand von dreiunddreißig Monaten, über denselben Kanal. Nachstehend: Was dieser Zugang wert ist, sechs belegte Fälle und das Protokoll Valve, das für jeden einzelnen davon gilt und das niemandem zur Verfügung gestellt wurde.\n\nGespeicherte Zeugenaussage / 9. Mai 2025\nEin Wiederherstellungsticket, durch das die Sicherheit des Kontos außer Kraft gesetzt wurde, sowie ein gemeldeter Verlust in Höhe von $10,000\n\nEin Nutzer im Support-Archiv berichtet, dass Steam der Support das Passwort zurückgesetzt und den Kontoschutz deaktiviert habe, nachdem eine andere Person ein Ticket zur Kontowiederherstellung eingereicht hatte. Der Verfasser gibt an, dass das Konto seit Jahren inaktiv war, Elemente aus den Jahren 2016–2017 enthielt und über Steam Guard, eine verknüpfte Telefonnummer sowie gespeicherte Wiederherstellungscodes verfügte.\n\n\"Steam Der Support hat dennoch einer anderen Person Zugriff auf mein Konto gewährt.\"\n\nAussage aus erster Hand, überliefert in steam_support_tickets_MEGA.json, Eintrag 110. Den vollständigen Beitrag lesen ↗\n\nDas ist nicht das Pech eines einzelnen Nutzers. Dieselbe Vorgehensweise – eine Hilfeanfrage, durch die ein Konto an denjenigen übertragen wird, der die älteren Daten bereitstellt – ist in allen Fällen in der untenstehenden Aufstellung als dokumentierter Weg festgehalten, und Valve hat dies zweimal schriftlich festgehalten.\n\nDer Eigentümer kann diese Auseinandersetzung nicht gewinnen. Die Wiederherstellung fragt nach dem ersten CD-Key, der ersten E-Mail-Adresse, der ersten Kreditkarte und der ersten Telefonnummer. Diese Angaben befinden sich in der Datenbank von Valve, und der Support-Zugang liest sie aus – angeblich reichen sie bis zu fünfzehn Jahre zurück. Eine Person, die eine Kopie Ihrer Datei besitzt, kann immer mehr Details aus Ihrer Vergangenheit vorweisen, als Sie selbst. Die Ziele wurden passend ausgewählt: seit Jahren inaktiv, von hohem Wert und oft aus zweiter Hand erworben, sodass der Besitzer den ursprünglichen Schlüssel nie kannte. Anschließend wurden die Konten vollständig gelöscht, wodurch die Spur der Artikelhistorie unterbrochen wurde, die die Community nutzt, um einen Skin zurückzuverfolgen – eine Löschung, die ein gewöhnlicher Nutzer ohne die übliche Wartezeit nicht vornehmen kann.\n\nPrinzip der geringsten Berechtigungen / OWASP A01\n\nDie Berechtigungen zur Datenwiederherstellung sollten auf die jeweilige Aufgabe beschränkt, unabhängig überprüft und protokolliert werden. Überprüfen Sie, wer Anmeldedaten zurücksetzen, Steam Guard entfernen, Abrechnungsunterlagen einsehen oder Kontodaten exportieren darf. OWASP-Leitfaden zur Zugriffskontrolle ↗ archiviert 2026-09-20 ↗\n\nUmfassender Support-ZugangRisiko im Zusammenhang mit Zugriffsrechten\nÜber das Inventar hinaus.\n\nWird der umfassende Zugriff missbraucht, kann private Telemetrie zu einem Instrument für Profiling, gezieltes Phishing und Überwachung werden. Zu den potenziellen Opfern zählen normale Nutzer, Militärangehörige, Personen des öffentlichen Lebens und deren Familien. Hierbei handelt es sich um ein Bedrohungsmodell; die genauen Berechtigungen erfordern Zugriffskontrollprotokolle.\n\n01 IP-Verlauf und Standort\nIP-Protokolle können Aufschluss über den Netzwerkverlauf und den ungefähren Standort geben. Sie lassen jedoch für sich genommen keine genauen physischen Bewegungen erkennen.\n02 Geräte-Fingerprinting\nGerätekennungen können, sofern sie erfasst wurden und zugänglich sind, Sitzungen und Konten miteinander verknüpfen.\n03 Aktivitäts-Telemetrie\nAnmeldezeitstempel und Sitzungsprotokolle können Gewohnheiten offenbaren, darunter auch Aktivitäten, die in einem öffentlichen Profil nicht sichtbar sind.\n04 Kommunikation und Kontakte\nDer Zugriff auf gespeicherte Nachrichten oder Kontaktdaten würde die Möglichkeiten für Profiling und Social Engineering erweitern.\n05 Enttarnung der Identität\nAnhand der ursprünglichen E-Mail-, Telefon- und Zahlungsdaten lässt sich ein pseudonymes Konto einer bestimmten Person zuordnen.\n06 Weiterverkauf von Daten und Rechenschaftspflicht\nExportierte Ziellisten könnten gezielte Betrugsversuche begünstigen. Ermitteln Sie den Akteur, den Zugriffsort, die Empfänger und die Überweisungen; der Standort allein begründet weder einen Zugriff noch rechtliche Immunität.\n\nValve beschreibt in seinem Bericht die Protokollierung von IP-Adressen, Geräteinformationen, Zahlungsdaten und externe Support-Anbieter Datenschutzerklärung §§ 3, 5.2 archiviert 2026-09-21 ↗. Die Richtlinie gestattet den Zugriff durch Dritte – der Prüfpfad, aus dem hervorgeht, welcher Auftragnehmer wann und mit welcher Berechtigung auf welche Kategorie zugegriffen hat, wurde jedoch nicht offengelegt.\n\nAbschnitt 14.1 · Das Register · Juni 2022 → November 2025 · Alle Zahlen mit Quellenangabe\nValve öffnete die Tür zweimal im Abstand von dreiunddreißig Monaten. Sie schloss sich nie.\n\nSechs gemeldete Fälle, in denen Konten über den eigenen Hilfeanfrage-Kanal von Steam oder über die von diesem Kanal geschützten Zugangsdaten kompromittiert wurden. Die jeweiligen Beträge entsprechen den von den genannten Quellen veröffentlichten Zahlen, und jede Quelle wird namentlich genannt. Zwei der sechs Fälle konnten vollständig wiederhergestellt werden. Der Unterschied zwischen diesen Fällen und den übrigen lag nicht darin, was passiert war – sondern darin, wer zuschaute.\n\nValve, schriftlich – Februar 2023„Die betreffenden Gegenstände wurden aus deinem Konto entfernt, da sie von einem Konto stammten, das im Zuge einer Support-Anfrage kompromittiert wurde – wofür das CS:GO-Team die Verantwortung übernimmt. Wir haben die Tauschgeschäfte rückgängig gemacht und die Gegenstände aus allen Konten entfernt, auf denen sie eingegangen sind.“Steam Antwort an einen Empfänger von HFB-Artikeln, wiedergegeben von Dexerto, 21. Februar 2023 ↗ archiviert 2025-08-18 ↗\nValve, wieder schriftlich – November 2025 · 33 Monate später„Ein Support-Mitarbeiter, der die Supportanfrage bearbeitet hat, hat unseren Prozess nicht eingehalten, was dazu führte, dass Ihr Konto einer anderen Person zugewiesen wurde. Ich entschuldige mich für diesen Fehler.“Steam Antwort des Supports an Hawkeye337, zitiert in Dexerto, 14. November 2025 ↗\n21. Juni 2022\nHFB – das größte Sortiment im Spiel$2,000,000+ · wurde im Follow-up vom Februar 2023 auf $3,000,000+ angehoben\n\nSieben „AWP Dragon Lores“-Souvenirs und das „#1 Blue Gem Karambit“ – allein dieses Messer hat einen Wert von etwa $1.26 Millionen. Das Konto war seit drei Jahren inaktiv, wobei der mobile Authentifikator weiterhin aktiv war; E-Mail-Adresse und Passwort wurden dennoch über den Support-Wiederherstellungsweg geändert.\n\nDas Geld war schon weg, bevor die Sachen weg waren. Ein gemeldeter $200,000+ Ein Teil des Verkaufserlöses wurde bereits über market.csgo.com abgehoben – einen Marktplatz, auf dem Transaktionen in Bargeld und Kryptowährung abgewickelt werden. Bei der Rückabwicklung eines Handels wird die Skin zurückgegeben. Das bereits auf das Konto eingezahlte Bargeld wird jedoch nicht zurückerstattet.\n\nUnd die Korrektur hat nicht funktioniert. Ein Käufer hat seinen „Souvenir Dragon Lore“ in einen Lagerraum im Spiel verschoben. Das Rollback-Skript von Valve konnte nicht in den eigenen Container hineinsehen, daher stellte es dem Besitzer eine neue Kopie aus und ließ die versteckte Kopie bestehen – Valve duplizierte einen $130,000 Artikel, als versucht wurde, einen Diebstahl rückgängig zu machen. Der Vorfall wurde durch den Abgleich von Artikel-IDs und Meldungen aus der Community aufgedeckt und der Artikel wurde einen Monat später, im Juli 2022, gelöscht. Der Käufer erhielt eine Rückerstattung von BUFF, nicht von Valve. Eine so kurzfristige Notfallmaßnahme ist keine Kontrolle; es ist das, was eine Plattform tut, wenn sie keine Kontrolle hat.\n\nDexerto, 21. Juni 2022 ↗ archiviert 2022-07-02 ↗ · Kaspersky ↗ · Auszahlungsbetrag pro Esportfire, 22. Juni 2022 ↗ archiviert 2026-05-15 ↗, dort mehreren Twitter-Quellen zugeschrieben · Duplikate und Löschungen gemäß Esportsbetting, 14. Juli 2022 ↗\n\nRestauriertDie Geschäfte wurden rückgängig gemacht. Die Artikel wurden aus den Beständen derjenigen zurückgezogen, die den vollen Preis dafür bezahlt hatten.\n14. August 2022\nCS.Money – die plattformeigenen Bots$6,300,000 · 19,000+ Skins · erste Schätzung $1.6M\n\nDie Angreifer erbeuteten die Dateien des mobilen Authentifikators der Handelsbots des Marktplatzes und leerten diese; anschließend schickten sie einen Teil der Beute an bekannte Händler, um die Spuren zu verwischen. Forscher aus der Community haben dies nachverfolgt 55 Angreifer-Konten innerhalb weniger Stunden und veröffentlichte sie.\n\nValve hat nichts rückgängig gemacht. Als Grund wurde angegeben, dass sich eine Website eines Drittanbieters außerhalb von Steam befindet – desselben Steam, dessen Bestandsdaten, Handels-API und Kontensystem durch den Diebstahl durchgängig betroffen waren.\n\nEsportfire, 14. August 2022 ↗ archiviert 2025-11-15 ↗\n\nAbgelehntKeine Rückabwicklung. Der Verlust blieb bei der Plattform und ihren Nutzern.\nGemeldet\n21. Februar 2023\nQkss – dieselbe Tür, derselbe Schauspieler$1,000,000+\n\nEs wurde berichtet, dass dies auf dieselbe Weise wie bei HFB erfolgte – durch denselben Schauspieler und über dieselbe Support-Anfrage. HFB wurde bereits acht Monate zuvor vollständig behoben. Bei Qkss war dies nicht der Fall.\n\nEin Weg. Zwei Antworten. In den veröffentlichten Unterlagen gibt es keinen Unterschied zwischen den beiden Fällen, abgesehen von der Größe des Publikums.\n\nDexerto, 21. Februar 2023 ↗ archiviert 2025-08-18 ↗\n\nAbgelehntNicht restauriert.\nGemeldet\nFebruar 2023\nDer Insiderhandel an sich – ein Jahr lang≈ $320,000 · Erlöse über einen Zeitraum von etwa einem Jahr, keine Bestandsbewertung\n\nDer Zugriff über den Support ermöglichte den Zugriff auf den Kontoverlauf bis zum 15 Jahre alt — der erste CD-Key, die erste E-Mail, die erste Karte. Genau das sind die Nachweise, die im Wiederherstellungsprozess verlangt werden, weshalb derjenige, der die Datenbank besitzt, im Streit mit dem Kontoinhaber immer die Oberhand behält.\n\nDer Blogger Mzkshow deckte auf, wie der Insider-Betreiber „Steam Help“ und sein Komplize „Alexander“ inaktive Konten ins Visier nahmen, auf denen Skins im Wert von über $100k lagen. Eine gestohlene M4A4 Howl mit den Holos „iBUYPOWER“ und „Titan Katowice 2014“ wurde für $35,000 und landete schließlich bei Valerii „b1t“ Vakhovskyi von NAVI, der davon nichts ahnen konnte. Nachdem Valve eingeschritten war, entließ der Auftragnehmer sein gesamtes Steam-Supportteam.\n\nVKPlay ↗ · Lis-Skins ↗ · Escorenews (RU) ↗ · Dexerto (EN) ↗\n\nKein RegisterValve hat nie veröffentlicht, wie viele Konten davon betroffen waren, und hat auch die Betroffenen nicht darüber informiert.\nGemeldet\n2. Dezember 2024\n„Matvey“ – nach den Entlassungen$13,000\n\nDie Wiederherstellung wurde jemandem gewährt, der Kontodaten vorlegte, die der Eigentümer selbst nicht zuordnen konnte. Zwei Jahre, nachdem der Auftragnehmer seinen Steam-Support-Desk aufgelöst hatte, führte derselbe Weg zum gleichen Ergebnis.\n\nArchivierter Beitrag, 2. Dezember 2024 ↗ archiviert 2025-08-05 ↗ · Quellzeilen und Hashes ↓\n\nAbgelehntNicht restauriert.\n13. November 2025\nHawkeye337 (Mark Spurlock) – und das zweite Geständnis≈ $300,000–$500,000 · Die komplette Holo-Kollektion „Katowice 2014“\n\nDer Angreifer forderte 1 Bitcoin und begann, die Sammlung auf Negevs zu kopieren, um sie zu vernichten. Steam Die schriftliche Antwort des Supports ist das zweite Eingeständnis oben: Ein Techniker hat die Supportanfrage bearbeitet, sich nicht an den vorgegebenen Ablauf gehalten und das Konto an jemand anderen weitergegeben.\n\nDer Grund für die Korrektur war der Feed. Nur wenige Stunden, nachdem die Beiträge mit dem Tag Valve auf X veröffentlicht worden waren, wurde der Account wieder freigeschaltet und alle Sticker wiederhergestellt. Qkss hatte nicht so viele Follower.\n\nSkin.club ↗ · Dexerto ↗ · Esportfire ↗ archiviert 2025-12-17 ↗\n\nRestauriertInnerhalb weniger Stunden, nachdem die Meldung zum Trend geworden war, wurde sie zurückgenommen.\nWas die Bilanz aussagt, was kein Einzelfall tut.\n\nDie Strecke wurde nie gesperrt. Die erste Aufnahme erfolgte im Februar 2023, die zweite im November 2025 — im Abstand von dreiunddreißig Monaten, dazwischen kam es zu einer Massenentlassung bei dem Auftragnehmer, einem dokumentierten erneuten Vorfall und einem Plattformverstoß in Höhe von $6.3 Millionen. Gerechnet ab dem ersten Diebstahl in diesem Verzeichnis blieb der Kanal offen für drei Jahre und fünf Monate. Was auch immer im Jahr 2023 behoben wurde, im November 2025 wurde die Hilfeanfrage dennoch an die falsche Person weitergeleitet – so der eigene Satz von Valve.\n\nBei der Wiedergutmachung ging es um die Aufmerksamkeit, nicht um den Schaden. Wiederhergestellt: das größte Inventar im Spiel und der Sammler, dessen Thread zum Trend wurde. Abgelehnt: $1,000,000, $6,300,000, $13,000. Valve hat die zugrunde liegende Regel nie veröffentlicht, da eine veröffentlichte Regel diese drei erklären müsste.\n\nNiemand wurde darüber informiert. Weder die Nutzer, deren Kontodaten aus der Datenbank ausgelesen wurden, noch eine Aufsichtsbehörde, noch der Markt, der die Artikel in gutem Glauben gekauft hatte und sie zurückfordern musste. Es gibt keine Benachrichtigung über eine Datenschutzverletzung, keinen Vorfallbericht, keine Aufstellung der betroffenen Konten — und die Erlöse, die als Geld übrig blieben, über Marktplätze, die in Bargeld und Kryptowährung auszahlen. Eine Handelsumkehr kann nicht dem Geldfluss aus Steam folgen.\n\nValve enthält den Support-Prüfpfad, das Protokoll der Wiederherstellungstickets und die Transaktionsaufzeichnungen für jede der oben genannten Zeilen. Nichts davon wurde vorgelegt. Fordern Sie Ihr eigenes Exemplar an →\n\nDie Frage zur Geheimhaltungsvereinbarung\nVertraulichkeit muss mit technischer Rechenschaftspflicht einhergehen.\n\nVergleichen Sie Vertraulichkeitsvereinbarungen mit den tatsächlichen Berechtigungen, Exportkontrollen, Genehmigungen für das Zurücksetzen und Zugriffsprotokollen. Eine vorgefertigte Antwort reicht nicht aus, um den Vorwurf auszuräumen, dass der Wiederherstellungsprozess selbst missbraucht wurde.\n\nArtikel 28, 32–34 der DSGVO\n\nGemäß Art. 33 hat ein Verantwortlicher 72 Stunden Zeit, um die Aufsichtsbehörde über eine Verletzung des Schutzes personenbezogener Daten zu informieren; Art. 34 schreibt vor, die betroffenen Personen zu benachrichtigen, wenn das Risiko für sie hoch ist. Valve hat zweimal schriftlich bestätigt, dass sein Support-Kanal Konten – einschließlich Kontoverlauf, Abrechnungsunterlagen und allem anderen – an die falschen Personen weitergegeben hat. Es wurde keine Mitteilung gemäß einem der beiden Artikel veröffentlicht, und kein betroffener Nutzer hat berichtet, eine solche erhalten zu haben. Lesen Sie die Verordnung ↗ archiviert 2026-09-20 ↗\n\nFügen Sie Ihrer Anfrage den Support-Zugang hinzu →\nTeil C – Rechtliche Rahmenbedingungen · Abschnitt 15 · Kommerzieller Maßstab\nFolgen Sie dem Geld. Trennen Sie die Transaktionen.\nKontext und Quellenbeschränkungen\n\nDie Frage nach der gewerblichen Nutzung stellt sich umso deutlicher, wenn die Geldströme voneinander getrennt werden. Die Übertragung von Gegenständen an Dritte, die Hauptverkäufe von Valve und externe Auszahlungen sind unterschiedliche Transaktionen.\n\nDer Artikel gehört Valve. Der Bestand beträgt Valve. Die Übertragung läuft auf den Servern von Valve. Nur die Zahlung erfolgt an einem anderen Ort — das ist der Schritt, der darüber entscheidet, ob jemand als Geldtransferdienstleister gilt, und genau diesen Schritt Valve führt das Unternehmen nicht durch.\n\nDer Einnahmemechanismus\nWo das Geld tatsächlich fließt.\nDrei Pfade / Ein-Gegenstand-Wirtschaft\n01 / KontoBenutzerverzeichnis\n\nArtikel im Bestand: Steam\n\n02 / TransferP2P-Handel\n\nBenutzer ↔ Bot oder Benutzer ↔ Benutzer\n\n03 / AbrechnungExterne Plattform\n\nSaldo oder Restzahlung Steam\n\nAuflageDer wirtschaftliche Motor geht über die Ablösesumme hinaus\n\nSteam stellt die von externen Märkten genutzte Infrastruktur für Bestandsführung und Transfers bereit. Das wirtschaftliche Argument der Untersuchung lautet, dass die Liquidität beim Weiterverkauf und die wiederkehrende Nachfrage die Ausgaben für Koffer, Schlüssel und Ersatzartikel aufrechterhalten, wobei Gebühren auf nachfolgende Verkäufe auf dem Community-Markt anfallen. Bei einem direkten P2P-Transfer fällt keine Provision des Community-Marktes an; diese buchhalterische Tatsache sagt jedoch nichts über den umfassenderen Nutzen aus. Valve behält durchgehend die Kontrolle über den Kontozugang und die Handelsbeschränkungen.\n\n01 / SekundärnachfrageLiquidität und Wiederverkaufswert\n\nNachfrage im Außenhandel und im Glücksspielbereich\n\n02 / Primäre AusgabenSchlüssel, Etuis und Kapseln\n\nEinkäufe bei Valve, sofern angeboten\n\n03 / UmsatzErlöse aus Erstverkäufen\n\nZuzüglich Gebühren auf tatsächliche Marktverkäufe\n\n5% + 10%Steam + CS2-Gebühr auf Verkäufe im Community-Markt\n\nDie wirtschaftliche Schlussfolgerung der Untersuchung: Flüssige Wiederverkaufsmärkte können den Kauf neuer Artikel fördern. Das bekannte 15% umfasst Marktgebühren, die Mindestbeträgen und Rundungen unterliegen; es handelt sich nicht um eine Abgabe auf jeden Außenhandel.\n\nGebührenordnung des Community Market von Valve ↗ archiviert 2026-09-21 ↗. Am 25. Februar 2026 Der Generalstaatsanwalt von New York hat Klage eingereicht archiviert 2026-09-01 ↗ mit der Behauptung, dass kostenpflichtige Lootboxen mit dem Weiterverkauf gegen Bargeld und Glücksspielschäden in Verbindung stehen – genau dieser Zusammenhang wird in diesem Dossier aus Sicht der technischen Infrastruktur dokumentiert. Diese Beschwerde ist eine Behauptung, keine Feststellung; sie wird hier angeführt, weil eine staatliche Strafverfolgungsbehörde eine Frage aufgeworfen hat, die eng mit der in diesem Dossier gestellten zusammenhängt: Wo sind die Durchsetzungsergebnisse, die den öffentlichen Erklärungen entsprechen?\n\n01 / EintragKrypto-Einzahlung\n\nExterne Dienst- und Wallet-Datensätze\n\n02 / UmwandlungBalance → Skins\n\nArtikel, die über Steam-Transaktionen geliefert wurden\n\n03 / AusgangExterner Fiat-Verkauf\n\nVerkäufer, Käufer und Auszahlungsdienstleister\n\nKYC?Bei jeder Übergabe die Kontrollinstanz ermitteln\n\nDies ist der Weg, den es zu prüfen gilt, und nicht ein nativer Steam-API-Dienst zur Bargeldumwandlung. Dokumentieren Sie Identitätsprüfungen, Verwahrung, Transaktions-IDs und Auszahlungsempfänger bei jedem externen Betreiber, bevor Sie eine Auszahlung ohne KYC-Prüfung genehmigen.\n\nVereinigte Staaten / Bankgeheimnisgesetz\nOrdnen Sie zunächst die Tätigkeit und anschließend die Verpflichtung zu.\n\nFinCEN bewertet den Geldtransfer anhand der Geschäftstätigkeit eines Unternehmens. Die Annahme und der Transfer konvertierbarer virtueller Währungen können Verpflichtungen im Rahmen des Gelddienstleistungsgesetzes auslösen, vorbehaltlich der geltenden Definitionen und Ausnahmen. Die Steam-Wallet von Valve nimmt Gelder entgegen und wandelt sie in Gegenstände im Spiel um; diese Gegenstände werden anschließend über Drittanbieter gegen echte Währung veräußert. Der Gegenstand und dessen Übertragung laufen über die Infrastruktur von Valve; die Auszahlung erfolgt jedoch nicht darüber, und ob ein Teil dieses Zyklus den Definitionen für Geldtransfers entspricht, ist eine Einstufungsfrage für FinCEN und wird hier nicht abschließend beurteilt.\n\nFinCEN FIN-2019-G001, §§ 1–2, 5.1 ↗ archiviert 2025-07-11 ↗\n\nEuropäische Union / Geldwäsche\nErlöse, Wissen und Unterstützung nachverfolgen.\n\nDie Richtlinie (EU) 2018/1673 betrifft vorsätzliche Geldwäsche und die Beteiligung an Straftaten im Zusammenhang mit Erträgen aus Straftaten. Die ermittlungsrelevante Frage lautet, was Valve über die Betreiber wusste, die seine Handels- und OpenID-Infrastruktur nach dem 13. Juli 2016 nutzten – als das Unternehmen diese Nutzung öffentlich beschrieb –, und welche Maßnahmen es in diesem Zusammenhang ergriffen hat. Valve hat keine Aufzeichnungen über die Durchsetzungsmaßnahmen pro Betreiber veröffentlicht; diese Aufzeichnungen, nicht das vorliegende Dossier, würden die Frage beantworten.\n\nStrafrechtlicher Rahmen der EU ↗\n\nBegriffe der AMLD6: Die oben genannte strafrechtliche Richtlinie unterscheidet sich von der Richtlinie (EU) 2024/1640, auch bekannt als AMLD6. Für Letztere gilt eine allgemeine Umsetzungsfrist bis zum 10. Juli 2027, wobei bestimmte Ausnahmen vorgesehen sind. Artikel 78 ↗ archiviert 2026-08-30 ↗\n\nTeil C – Rechtliche Rahmenbedingungen · § 16 · Mitteilung, Antwort, Haftung\nDas Gesetz über digitale Dienste: Wissen dokumentieren\nKontext und Quellenbeschränkungen\n\nZwei Elemente einer Mitteilung gemäß Artikel 16 liegen beim Einreicher und nicht in diesem Dossier vor: die Angaben des Einreichers selbst und eine Erklärung in gutem Glauben, dass die Informationen korrekt sind. Alles andere, was der Artikel vorschreibt – die begründete Erklärung und der genaue elektronische Speicherort –, ist in Abschnitt 3 und im Routenregister mit gespeicherten Antworten und Hashwerten festgelegt, sodass jede Partei die Meldung einreichen kann. Zwei weitere Einschränkungen des Gesetzes selbst: Der Verlust der Hosting-Ausnahme begründet für sich genommen keine Haftung nach anderen Gesetzen, und der Betrag „0“ in Artikel 52 Absatz 3 ist eine gesetzliche Obergrenze, keine festgesetzte Strafe in Höhe von „1“.\n\nGemäß dem DSA genießt ein Hosting-Anbieter nur so lange Haftungsschutz, bis er konkrete Kenntnis erlangt und es versäumt, entsprechend zu handeln. Dieses Dossier stellt diese Mitteilung dar. Darin werden die Hosts, die Daten, die gespeicherten Antworten und die Hashes genannt. Seit der Veröffentlichung stellt sich nicht mehr die Frage, ob Valve davon wusste – sondern vielmehr, was Valve als Nächstes tat.\n\n01Juli 2016 / die Dossier-Ausstellung\nEine zehntägige Frist.\n\nDie oben wiedergegebene Bekanntmachung bildet den historischen Ausgangspunkt für den Vergleich der Durchsetzungsmaßnahmen im Rahmen der Untersuchung.\n\n0217. Februar 2024 / Allgemeine Bewerbung\nDas DSA-Zeitfenster.\n\nTrennen Sie das Verhalten in der Vergangenheit von dem Verhalten während des Zeitraums, in dem die einschlägigen DSA-Verpflichtungen gelten.\n\n03Zehn Jahre / Momentaufnahme der ursprünglichen Akte\nFür die Dauer ist ein Nachverfolgungspfad erforderlich.\n\nDie seit Juli 2016 verstrichene Zeit (siehe Abschnitt 11) ist eine Kennzahl aus den Akten. Es handelt sich nicht um zehn Jahre nachgewiesener Verstöße gegen das DSA. Verknüpfen Sie jede Mitteilung mit einem konkreten Sachverhalt, dem anwendbaren Recht, dem Zustellnachweis und der Antwort.\n\nArtikel 52 Absatz 3 / gesetzliche Obergrenze6%\ndes weltweiten Jahresumsatzes\n\nHöchststrafe bei Verstößen gegen die Verpflichtungen gemäß dem DSA, bezogen auf das vorangegangene Geschäftsjahr des Anbieters. Hierbei handelt es sich um eine gesetzliche Obergrenze, nicht um eine gegen Valve verhängte Strafe.\n\nArtikel 6, 8 und 16 / die rechtliche Prüfung\n\nBei den betreffenden Hosting-Diensten können spezifische Kenntnisse und das Versäumnis, unverzüglich zu handeln, zum Verlust der Hosting-Ausnahme führen. Eine hinreichend präzise Mitteilung kann die Kenntnis des konkreten Inhalts begründen. Das DSA sieht keine allgemeine Überwachungspflicht vor; der Verlust der Ausnahme begründet für sich genommen keine Haftung nach einem anderen Gesetz.\n\nDSA: Artikel 6, 8, 16, 52, 53, 93 und Erwägungsgrund 17 ↗ archiviert 2026-09-20 ↗\n\nGespeicherte Beschwerden anzeigen ↗Die Zeitleiste des Kontos erstellen →Umfassende rechtliche und wirtschaftliche Analyse →\nTeil C – Rechtliche Rahmenbedingungen · Abschnitt 17 · Identität, Alter, Zugang zu kommerziellen Diensten\nMinderjährige: Eine Anmeldung mit „0“ gilt nicht als Altersüberprüfung.\nKontext und Quellenbeschränkungen\n\nIn dieser Akte tauchen an keiner Stelle Daten von Minderjährigen auf, und es wurden auch keine erhoben: Die Autoren haben sich auf keiner der genannten Plattformen registriert, dort Daten hinterlegt oder sich dort angemeldet. Wer auf diesem Abschnitt aufbaut, sollte Beweismittel, die ein Kind betreffen, vertraulich behandeln und identifizierende Angaben aus öffentlichen Unterlagen schwärzen. COPPA wird hier als Datenschutzgesetz für Kinder mit eigenen Anwendungsbedingungen – Zielgruppe, tatsächliche Kenntnis, erhobene personenbezogene Daten – zitiert und nicht als allgemeine Regel zum Mindestalter für Glücksspiele; die Klage aus New York aus dem Jahr 2026 ist eine Behauptung einer staatlichen Behörde, keine festgestellte Tatsache.\n\n„Mit Steam anmelden“ bestätigt, dass ein Konto vorhanden ist. Das sagt nichts über das Alter aus — und auf diesen Seiten ist es das einzige Hindernis zwischen einem Kind und einer Einzahlung. Lies es mit Abschnitt 3.1: Innerhalb des Steam-Clients wird die Warnung, die ein Browser anzeigen würde, niemals ausgelöst, sodass das Kind sie nie zu sehen bekommt.\n\nWas Steam OpenID bietetKontoidentität\n\nEine verifizierte Steam-ID, die zum Einloggen oder zum Verknüpfen eines Kontos verwendet wird.\n\n≠\nWas der Betreiber nachweisen mussTeilnahmeberechtigung\n\nAlter, zuständiges Gericht und etwaige erforderliche Identitätsprüfungen.\n\nTechnische Grundlagen: Steamworks OpenID-Dokumentation ↗ archiviert 2026-09-21 ↗. Die dokumentierte Identitätsbestätigung stellt keine Bescheinigung dar, dass der Nutzer rechtmäßig Glücksspiele betreiben darf.\n\nCOPPA / Kinder unter 13 Jahren\nBestimmen Sie den Operator und die Daten.\n\nCOPPA gilt für betroffene, an Kinder gerichtete Dienste sowie für Dienste, denen tatsächlich bekannt ist, dass sie personenbezogene Daten von Kindern unter 13 Jahren erheben. Es handelt sich um ein Datenschutzgesetz für Kinder und nicht um eine allgemeine Regelung zum Mindestalter für Glücksspiele. Legen Sie die Zielgruppe, die erhobenen personenbezogenen Daten, die Kenntnislage sowie das Verfahren zur Einholung der elterlichen Einwilligung fest.\n\nFTC: COPPA-Vorschriften ↗ archiviert 2026-09-21 ↗\n\nDie zu sichernden Beweismittel\nErfassen Sie den Ablauf vom Einloggen bis zur Einzahlung.\n\nBehalten Sie die Altersbeschränkung der Website, den Wortlaut der Registrierungsbedingungen, die Teilnahmebedingungen, den Zahlungsablauf und die Beschwerdehistorie bei. Bewerten Sie jeden Betreiber separat. Behandeln Sie alle Beweismittel, die ein Kind betreffen, vertraulich und schwärzen Sie identifizierende Angaben in öffentlichen Unterlagen.\n\nEin damit zusammenhängender öffentlicher Vollstreckungsbescheid ist der Bekanntmachung zur Klage in New York 2026 archiviert 2026-09-01 ↗, in der behauptet wird, dass kostenpflichtige Lootboxen jungen Nutzern Schaden zufügen. Es handelt sich dabei nicht um eine Feststellung im Rahmen des COPPA.\n\nTeil C – Rechtliche Rahmenbedingungen · Abschnitt 18 · Antrag gemäß Artikel 15 der DSGVO\nDie Anfrage. Die Antwort. Der fehlende Vergleich.\n\nEr bat um vier Dinge, darunter das Protokoll, aus dem hervorgehen würde, wer einen API-Schlüssel in seinem Konto hinterlegt hatte. Drei Tage später wurde das Ticket mit einem Link zu einer Seite geschlossen, auf der keine davon zu finden ist. — und der Satz, mit dem der Text abgeschlossen wird, wird von Valves eigenen Anwälten widerlegt.\n\nWem dieser Bericht gehört · Herkunft und Einschränkungen\n\nDiese Screenshots stammen nicht von PhishDestroy. Sie stammen von einem gewöhnlichen Steam-Kontoinhaber – einem Teilnehmer einer kurzen Umfrage im Rahmen dieses Projekts, der die Anfrage selbst gestellt und die Screenshots bereitgestellt hat. Das Konto gehört ihm, das Ticket gehört ihm, und der Schriftverkehr findet zwischen ihm und dem Steam-Support statt. Dieses Projekt hat den Antrag nicht gestellt, unterhält kein Konto auf der Plattform und ist nicht Partei dieses Tickets.\n\nAm 16. September 2026 reichte er einen Antrag auf Auskunft gemäß Artikel 15 der DSGVO/des CCPA ein, in dem er ausdrücklich um die Bereitstellung von Protokollen zur Registrierung von API-Schlüsseln, den Anmeldeverlauf mit IP-Adressen, den Verlauf der Geräteautorisierungen und den Handelsverlauf bat. Am 17. September verwies ihn der Mitarbeiter „Logen“ auf die Self-Service-Seite „Kontodaten“. Am 18. September wies er darauf hin, dass die angeforderten Kategorien auf dieser Seite nicht zu finden seien, und bat um Weiterleitung an das Datenschutzteam oder den Datenschutzbeauftragten. Am 19. September schloss der Mitarbeiter „Kal“ das Ticket mit demselben Verweis. Beide Screenshots sind unten zu sehen (E-Mail-Adresse des Antragstellers unkenntlich gemacht; SHA-256 in steam_tos_assets/screenshot-manifest.json).\n\nEr ist aus einem ganz gewöhnlichen Grund der richtige Anfragende: Sein Konto verfügt über einen Steam Web-API-Schlüssel, den er nicht erstellt hat und der registriert ist unter localhost. Wann es entstanden ist, ist nicht bekannt — nicht für ihn und auch nicht aus irgendetwas, das Valve ihm zur Verfügung gestellt hat, denn die einzige Aufzeichnung, die eine Datierung ermöglichen würde, ist das Registrierungsprotokoll für den API-Schlüssel, und genau diese Kategorie hat die Schließung zurückgehalten. Der Schlüssel ist nicht neu: Er existierte bereits vor dem Zeitpunkt, zu dem er davon Kenntnis erlangte, und zwar um einen Zeitraum, den er aus demselben Grund nicht beziffern kann.\n\nAndere Kontoinhaber reichen denselben Antrag ein. Jede eingehende Antwort wird hier unter denselben Bedingungen wie bei diesen beiden hinzugefügt – Ticketnummer, Erfassungsdatum, SHA-256, Antragsteller unkenntlich gemacht –, unabhängig davon, ob darin die Kategorien genehmigt oder abgelehnt werden.\n\nDieses Projekt nimmt keine Stellung dazu, warum das Ticket geschlossen wurde. Es wurde kein Grund dafür angegeben, und auch hier wird kein Grund vermutet.\n\nDie Anfrage. Die Antwort. Der Vergleich.FOLGE DEM VERLAUF\nSchritt 3 / 3\n\nEr fragte nach vier namentlich genannten Kategorien. Die Seite „Kontodaten“, auf die er verwiesen wurde, ist der Selbstbedienungs-Export von Valve selbst, und dieses Projekt kann deren Inhalt für das Konto einer anderen Person nicht auflisten – daher wird hier kein vollständiger Vergleich nach einzelnen Kategorien veröffentlicht. Dokumentiert sind lediglich seine Aussage vom 18. September, dass die Kategorien nicht vorhanden waren, sowie der Abschluss vom 19. September, in dem der Verweis wiederholt wurde, ohne auf diese einzugehen.\n\nDIE ANFRAGEBestimmte KategorienAPI-Schlüssel, Anmeldedaten, Geräte- und Handelsdaten\nDIE ANTWORTVerweis auf KontodatenDen Austausch der Halterung überprüfen\nDER TESTWas wurde geliefert?Vergleiche die einzelnen angeforderten Kategorien\nBildschirm 1/2 – Anfrage (16. September) und erste Antwort, Mitarbeiter „Logen“ (17. September)\nGDPR ticket HT-2YBP-F7JP-D4VB — request and first response\nQuelle: help.steampowered.com, Ticket HT-2YBP-F7JP-D4VB · erfasst am 16.–17. September 2026 · E-Mail-Adresse des Anfragenden unkenntlich gemacht 2026-09-21 · Datei: gdpr-ticket-1.png · SHA-256 da940c731ab9869d226e9d06ccc8a1b393738766b7b0c445a56662623e025a66 (screenshot-manifest.json).\nBildschirm 2/2 – Eskalationsanfrage (18. September) und Abschluss, Mitarbeiter „Kal“ (19. September)\nGDPR ticket HT-2YBP-F7JP-D4VB — escalation request and closure\nQuelle: help.steampowered.com, Ticket HT-2YBP-F7JP-D4VB · erfasst am 18.–19. September 2026 · Datei: gdpr-ticket-2.png · SHA-256 44844ea7b251f7fd7d79f87ee1578a846606a97b9659d3a53b322120c422219b (screenshot-manifest.json).\nAbschließende Stellungnahme, 19. September (wörtliches Zitat):\n„Die von Steam gespeicherten Daten finden Sie bereits auf der Seite ‚Kontodaten‘. Da der Support keine weiteren Informationen Steam bereitstellen kann, Diese Anfrage wird geschlossen.\"\nKeine Daten angegeben · keine Rechtsgrundlage für die Ablehnung angegeben · kein Ergebnis der Eskalation angegeben\nDieser Satz ist falsch, und die Anwälte von Valve selbst beweisen dies. Im Schreiben des Rechtsbeistands vom 1. Oktober 2025 wird in Absatz 1.9 eine Korrelation auf Geräteebene beschrieben, die ein Gerät mit Dutzenden von Konten verknüpft (Anhang A). Diese Antwort umfasste 830 Seiten an aufbewahrten Unterlagen (Anhang B). Auf der Seite „Kontodaten“ ist davon nichts zu finden.\nWarum hat dieses Konto das API-Schlüssel-Protokoll angefordert?\n\nEr hat diese vier Kategorien nicht zufällig ausgewählt. Die localhost Der Schlüssel zu seinem Konto ist ein Hinweis auf ein Skript, nicht auf eine Person, die eine echte Domain auf der Entwicklerseite eingibt (Abschnitt 5, Abschnitt 6). Der einzige Eintrag, aus dem hervorgeht, wer ihn erstellt hat und woher er stammt, ist das Protokoll zur Registrierung des API-Schlüssels. Das war das Erste, wonach er gefragt hatte. Genau das hat die geschlossene Gesellschaft zurückgehalten.\n\nQuelle: Der Kontoinhaber im Rahmen der Umfrage zu diesem Projekt. Die oben gezeigten Screenshots der Tickets sind mit einem Hash versehen; die Schlüsselseite wurde nicht veröffentlicht.\n\nBewertung · PhishDestroy\n\nEin Ticket zu schließen, obwohl die Frage noch offen ist, ist hier kein Zufall. Es ist das normale Ergebnis. Wir halten 16,319 aufbewahrte Beschwerde- und Unterstützungsunterlagen und 354 deduplizierte Support-Anfragen die daraus entnommen wurden. Diese Fahrkarte ist ein datiertes, vollständig dokumentiertes Beispiel für ihre Form.\n\nSupport-Ticket – AufbewahrtHT-2YBP-F7JP-D4VB\nAnfragetypDSGVO Artikel 15 – Recht auf Auskunft (DSAR)\nTicketstatusGESCHLOSSEN AM 19. SEPT. 2026 — KEINE DATEN VERFÜGBAR\nHandelsvertreter an der Börse„Logen“ (17. September), „Kal“ (19. September)\nAbgelegt16. September 2026\nAngeforderte DatenWer hat den mit diesem Konto verknüpften Web-API-Schlüssel registriert, und von welcher IP-Adresse / welchem Gerät / zu welchem Zeitpunkt?\nAngeführte RechtsgrundlageDSGVO Art. 15 – Recht auf Auskunft über personenbezogene Daten\nDer rechtliche Rahmen:Artikel 12 Absatz 3 räumt dem für die Verarbeitung Verantwortlichen eine Frist von einem Monat ab Erhalt ein (die unter Angabe von Gründen verlängert werden kann). Diese Frist war zum Zeitpunkt der Veröffentlichung noch nicht abgelaufen, und in dieser Akte wird kein Verstoß gegen die Frist geltend gemacht. Der Einwand bezieht sich auf den Inhalt: Die abschließende Antwort verweist auf eine Selbstbedienungsseite, zeigt jedoch nicht, dass die vier genannten Datenkategorien bereitgestellt wurden, und sollte der Verantwortliche ein Tätigwerden ablehnen, ist er gemäß Artikel 12 Absatz 4 verpflichtet, die Gründe dafür anzugeben und die Beschwerdewege darzulegen. Beides ist in der abschließenden Antwort nicht enthalten.\nWarum gerade diese Daten wichtig sind\n\nDas Ereignisprotokoll der Web-API-Schlüssel ist die Aufzeichnung, aus der hervorgeht, ob ein Dritter einen Schlüssel unter Verwendung eines gestohlenen Sitzungs-Cookies registriert hat – der Mechanismus, der in den Beschwerden über Inventardiebstahl beschrieben wird, die im Archiv dieses Dossiers aufbewahrt werden. Die Offenlegung, wer einen API-Schlüssel registriert hat, von welcher IP-Adresse aus und zu welchem Zeitpunkt, würde:\n\nGeben Sie dem Opfer die Möglichkeit, die IP-Adresse, von der aus die API erstellt wurde, mit seinem eigenen Anmeldeverlauf zu vergleichen.\nAufdeckung von IP-Adressen von Rechenzentren, die mit bekannter Phishing- bzw. Glücksspiel-Bot-Infrastruktur in Verbindung stehen\nBeweismittel vorlegen, die in Zivil- oder Strafverfahren gegen den Täter verwertbar sind\nAnzeigen, ob der Kontoinhaber bei der Erstellung des Schlüssels benachrichtigt wurde\nWas aus den Unterlagen hervorgeht: Valve bewahrt Datensätze auf Geräteebene sowie zur Kontenverknüpfung auf – diese werden im Schreiben des Rechtsbeistands vom 1. Oktober 2025 beschrieben (siehe Anhang A, Beweisverzeichnis – Quelle 1). Im Ticket HT-2YBP-F7JP-D4VB wurden dieselbe Art von Datensätzen von der betroffenen Person angefordert, und das Ticket wurde mit einem Verweis auf eine Selbstbedienungsseite geschlossen, die nach Angaben der betroffenen Person diese Datensätze nicht enthielt. Ob diese Verweigerung rechtmäßig ist, ist eine Frage für die Aufsichtsbehörde; die Folge ist, dass die betroffene Person die Daten nicht erhält.\nDer Austausch – vier Nachrichten, drei Tage\n\nZwei Support-Mitarbeiter von Steam antworteten unter den im Ticket angegebenen Vornamen: „Logen“ am 17. September und „Kal“ am 19. September. Beide verwiesen den Anfragenden auf die Seite „Kontodaten“. Aus dem Ticket geht nicht hervor, ob die Anfrage das Datenschutzteam oder den Datenschutzbeauftragten von Valve erreicht hat, und aus den Unterlagen geht nicht hervor, wer die Mitarbeiter sind, welche Funktionen sie ausüben oder wie das Ticket weitergeleitet wurde.\n\n16. SEP\nArt. 15: Antrag mit Angabe von vier Datenkategorien\n17.–18. SEP\nVerweis auf Kontodaten; der Antragsteller bittet um Eskalation an den Datenschutzbeauftragten\n19. SEP\nDer Fall wurde mit demselben Verweis abgeschlossen; keine Daten, keine angegebene Begründung\nWozu ist die betroffene Person gemäß Artikel 15 DSGVO ausdrücklich berechtigt?\nArt. 15 Abs. 1 Buchstabe aVerarbeitungszwecke – warum Valve die Daten speichert\nArt. 15 Abs. 1 Buchstabe bDatenkategorien – was Valve beinhaltet\nArt. 15 Abs. 1 Buchstabe cEmpfänger oder Empfängergruppen — wer die Daten erhalten hat (z. B. der Inhaber des API-Schlüssels)\nArt. 15 Abs. 1 Buchstabe dAufbewahrungsfrist bzw. Kriterien für deren Festlegung\nArt. 15 Abs. 3Eine Kopie der personenbezogenen Daten, die verarbeitet werden – d. h. das API-Schlüssel-Protokoll selbst\nArt. 12 Abs. 3Antwort bitte bis zum ein Monat ab Erhalt; eine Verlängerung muss innerhalb dieses Monats mitgeteilt werden. Die Frist war zum Zeitpunkt der Veröffentlichung noch nicht abgelaufen. § 12 Abs. 4: Wenn der Verantwortliche keine Maßnahmen ergreift, muss er die Gründe dafür darlegen und die betroffene Person über die Beschwerdemöglichkeiten informieren.\nVerfahren zur Einreichung von Beschwerden bei der Aufsichtsbehörde – für alle Nutzer\n\nJeder Nutzer, der einen Antrag gemäß Artikel 15 DSGVO an Valve gestellt und keine konforme Antwort (oder eine vorformulierte Ablehnung ohne Datenangaben) erhalten hat, kann eine Beschwerde bei der Aufsichtsbehörde seines EU-/EWR-Mitgliedstaats einreichen. Die EU-Niederlassung von Valve ist die Valve GmbH in Hamburg, daher ist die federführende Aufsichtsbehörde für grenzüberschreitende Beschwerden die Hamburgische Beauftragte für Datenschutz und Informationsfreiheit (HmbBfDI). (Der gemäß Artikel 27 benannte Vertreter von Valve hat seinen Sitz ebenfalls in Hamburg; die Anschrift eines Vertreters ist für sich genommen nicht ausschlaggebend für die Bestimmung der zuständigen Behörde.) Eine Beschwerde kann gemäß Artikel 77 auch bei der Behörde des Mitgliedstaats des Beschwerdeführers eingereicht werden.\n\nHmbBfDI-Beschwerdeformular ↗ Text der DSGVO (Art. 12, 15, 77) ↗ archiviert 2026-09-20 ↗Leitlinien des EDPB ↗\n\nTicket-Nummer für jede Reklamation: HT-2YBP-F7JP-D4VB — in dieser Akte als dokumentierter Fall festgehalten.\n\nEin dokumentierter Fall\nDie Unterlagen sind vorhanden; die betroffene Person hat sie nicht erhalten.\n\nDer Rechtsbeistand von Valve beschrieb in einem Schreiben vom 1. Oktober 2025 Korrelationsdatensätze auf Geräteebene. Am 19. September 2026 wurde ein Antrag gemäß Artikel 15 auf dieselbe Art von Aufzeichnungen mit einem Verweis auf eine Selbstbedienungsseite abgeschlossen, die nach Angaben des Antragstellers diese Aufzeichnungen nicht enthielt, ohne dass eine Rechtsgrundlage angegeben wurde. Das Ticket HT-2YBP-F7JP-D4VB ist ein dokumentierter Einzelfall; ob dies eine weit verbreitete Praxis widerspiegelt, ist eine Frage an die Aufsichtsbehörde, die Valve um Einsicht in dessen Bearbeitungsunterlagen ersuchen kann.\n\nArtikel 12, 15 und 77 der DSGVO / Aufsichtsbehörde\n\nEine Beschwerde gemäß den Artikeln 12 und 15 kann kostenlos direkt bei der zuständigen Aufsichtsbehörde eingereicht werden (Artikel 77). Die Behörde kann Abhilfemaßnahmen verhängen, darunter Anordnungen zur Erfüllung des Auskunftsersuchens, sowie Geldbußen gemäß Artikel 83 Absatz 5 Buchstabe b bei Verstößen gegen die Rechte der betroffenen Person. Die Aufbewahrung der ursprünglichen Ticket-Referenznummer und einer etwaigen Valve-Antwort (oder deren Ausbleiben) stärkt die Beschwerde.\n\nZur DSAR-Vorlage →\nTeil C – Rechtliche Rahmenbedingungen · Abschnitt 19 · Vertragsrecht\nDie Nutzungsvereinbarung im Widerspruch zur eigenen Architektur der Plattform\nKontext und Quellenbeschränkungen\n\nDie Autoren sind keine Juristen, und der vorliegende Text stellt keine Rechtsberatung dar. Die SSA wird in der Fassung vom 10. September 2026 zitiert; eine andere Fassung kann abweichende Formulierungen enthalten, und die Nummerierung der Paragraphen hat sich im Laufe der verschiedenen Fassungen geändert – vergleichen Sie den betreffenden Paragrafen mit der Fassung, die für das fragliche Verhalten maßgeblich war. Die Argumente zu den Artikeln 25 und 32 legen dar, was die Verordnung vorschreibt, und nicht, dass eine Aufsichtsbehörde einen Verstoß festgestellt hat. Die Zahlen in Argument 1 enthalten die in Abschnitt 13 festgelegten Anwendungsgrenzen.\n\nDrei der zentralen Bestimmungen der SSA stehen in einem Widerspruch zur Art und Weise, wie die Plattform aufgebaut ist: das Verbot der kommerziellen Nutzung in Verbindung mit einer Preisobergrenze auf dem Marktplatz, die hochpreisige Verkäufe von der Plattform verdrängt; die Haftungsklausel für Nutzer in Bezug auf API-Schlüssel im Gegensatz zu einem Schlüssel-Endpunkt, für den vor 2023 keine Zwei-Faktor-Authentifizierung erforderlich war; und die Formulierungen zur Durchsetzung im Gegensatz zu einem öffentlichen Verzeichnis, aus dem hervorgeht, dass keine betreiberspezifische Durchsetzung erfolgt. Ob diese Widersprüche die Durchsetzbarkeit beeinträchtigen, ist eine Frage für ein Gericht; in diesem Abschnitt werden die Sachverhalte dargelegt, die einem Gericht vorliegen würden.\n\nArgument 1 / Architektur der Marktkapitalisierung\nDie Markt-Obergrenze und das Verbot der gewerblichen Nutzung\n\nDer Steam Community Market hat eine Preisobergrenze von etwa $1,800. In einer veralteten Momentaufnahme (23. September 2026) liegen die Preise für 248 CS2-Artikelkategorien auf fünf Marktplätzen bei zwei oder mehr dieser Marktplätze unabhängig voneinander über dieser Obergrenze; solche Artikel können auf der eigenen Plattform von Valve nicht zu diesen Preisen verkauft werden. Eigentümer, die diese Preise nutzen möchten, greifen auf Drittanbieter-Marktplätze zurück, die über Steam-Konten und die Steam-API betrieben werden – die SSA stuft diese als kommerziell ein, sofern nicht ausdrücklich anders genehmigt.\n\nArtikel überschreiten die Obergrenze des Marktes → Drittanbieter-Märkte füllen die Lücke → diese Märkte nutzen Steam-Konten und die Steam-API → die SSA verbietet die kommerzielle Nutzung ohne Genehmigung → es wurde kein Verzeichnis der Genehmigungen veröffentlicht. Die kombinierte Gebühr des Community-Marktes in Höhe von etwa 15% gilt nur für Verkäufe, die innerhalb des Marktes abgeschlossen werden, nicht für diese externen Transaktionen.\nArgument 2 / Sicherheitsarchitektur für API-Schlüssel\nDie Sicherheitslücke beim API-Schlüssel ist eher ein Problem des Plattformdesigns als auf Nachlässigkeit der Nutzer zurückzuführen\n\nVor 2023 akzeptierte der Endpunkt zur Erstellung von API-Schlüsseln bei Steam einen POST-Aufruf mit einer gestohlenen Session-ID und generierte Zugangsdaten mit hohen Berechtigungen. ohne E-Mail-Bestätigung, ohne zweistufige Authentifizierung oder Geräteüberprüfung. Die im Rahmen dieser Untersuchung gesammelten Beschwerden über API-Hijacking folgen einem einheitlichen Muster: Angreiferskript, gestohlenes Sitzungs-Cookie, heimliche Schlüsselgenerierung, Abfangen von Transaktionen (die Nutzdaten der Anfrage sind in Abschnitt 8 dargestellt).\n\nArtikel 25 (Datenschutz durch Technikgestaltung) und Artikel 32 (Sicherheit der Verarbeitung) der DSGVO verlangen risikogerechte technische Maßnahmen. Die Ausstellung eines Zugangsnachweises, der ohne einen zweiten Authentifizierungsfaktor oder eine Benachrichtigung des Inhabers abgefangen werden kann, ist eine Frage der Konzeption seitens des Verantwortlichen. Ob vor diesem Hintergrund auf die SSA-Klausel, die die Haftung dem Nutzer auferlegt, zurückgegriffen werden kann, ist eine Frage, die von einem Gericht und der Aufsichtsbehörde zu klären ist.\n\nArgument 3 / Echtzeit-Transparenz\nValve erhält bei jeder Anmeldung den Authentifizierungs-Hostnamen\n\nDer Authentifizierungs-Hostname wird im Klartext an den OpenID-Endpunkt von Valve gesendet in openid.return_to und openid.realm (Die Form der Anfrage ist in Abschnitt 3 dargestellt). Das Extrahieren dieser Informationen ist ein Standardvorgang. Zum Zeitpunkt von 2026-09-22 befand sich bei 26 Paaren die Hauptdomain im Link-Filter, während der Host, der die Steam-Anmeldung trug, nicht darin enthalten war. Valve hat keine Aufzeichnungen über die Durchsetzung pro Betreiber veröffentlicht, sodass anhand öffentlicher Daten nicht festgestellt werden kann, ob auf diese Hosts andere Maßnahmen als der Link-Filter angewendet wurden.\n\nWer trägt die Kosten?\nDas Muster in den archivierten Beschwerden\n\nIn den untersuchten Beschwerden folgt die Antwort des Steam-Supports auf die Behauptung einer API-Schlüssel-Entwendung stets einem festen Muster: Ablehnung der Wiederherstellung, Hinweis auf die Verantwortung des Nutzers für das Konto und dessen API-Schlüssel sowie Schließung des Tickets. In dieser Akte wird keine Gesamtzahl der betroffenen Konten oder des entstandenen Schadens geschätzt; eine Quelle für eine solche Zahl wurde nicht gefunden.\n\nDie Frage ist nicht, ob einzelne Nutzer Fehler gemacht haben. Die Frage ist, wer für eine Architektur verantwortlich ist, die es bis 2023 ermöglichte, dass eine POST-Anfrage mit einem gestohlenen Cookie ohne Benachrichtigung und ohne Zwei-Faktor-Authentifizierung Zugangsdaten mit hohen Berechtigungen für den Handel erstellte.\nDie SSA als Dokument im Vergleich zur SSA als Vertrag\nEin Gericht, das diese Aktenlage prüft, würde die SSA nicht isoliert betrachten.\n\nEs würde dies im Zusammenhang mit dem Schreiben des Rechtsbeistands vom Oktober 2025 betrachten, in dem die Korrelation auf Geräteebene, die Registrierungsdaten der Authentifizierungshosts, die Zeitstempel der Batch-Registrierung, die Nutzdaten der API-Schlüsselanforderung sowie die zehn Jahre zwischen den Mitteilungen vom Juli 2016 und den im September 2026 noch in Betrieb befindlichen Plattformen beschrieben werden. Das ist der Sachverhalt, auf den sich Valve beziehen müsste.\n\nSSA im Vergleich zur Aktenlage / Kernpunkte\n„Keine kommerzielle Nutzung“ – die Obergrenze des Marktplatzes verlagert hochpreisige Verkäufe auf kommerzielle Drittmärkte\n„Nutzer haften für API-Schlüssel“ – vor 2023 keine Zwei-Faktor-Authentifizierung am Schlüssel-Endpunkt\n„Wir gehen gegen Verstöße vor“ – seit Juli 2016 wurden keine Aufzeichnungen über die Ahndungsmaßnahmen pro Betreiber veröffentlicht\n„Sie haben den Bedingungen zugestimmt“ – beim Hijack-Muster wird die Zustimmung von einem Skript übermittelt, nicht vom Kontoinhaber\nFazit · Was aus den Akten hervorgeht und was wir beantragen\nDie Ergebnisse. Die Unterlagen, um die wir bitten.\nKontext und Quellenbeschränkungen\n\nJede der nachstehenden Feststellungen bezieht sich auf eine datierte öffentliche Aufzeichnung in den vorangegangenen Abschnitten. Die Anfragen richten sich an die Behörden, die das erzwingen können, was diese Untersuchung nicht erreichen kann: die eigenen Aufzeichnungen von Valve über die Durchsetzung, den Zugriff und die Verarbeitung.\n\nJeder Antrag folgt auf eine datierte Feststellung. Die Behörden können Unterlagen anfordern, zu deren Herausgabe diese Untersuchung auf der Grundlage öffentlich zugänglicher Quellen nicht zwingen kann.\n\nWas aus den öffentlich zugänglichen Unterlagen hervorgeht\n44 Live-Plattformen authentifizieren sich über eine separate, registrierbare Domain – 27 davon mit einer veröffentlichten Nachweisdatei pro Route, 17 stammen aus manueller Erfassung und werden separat aufgeführt. Stand 2026-09-22 war bei 26 Paaren die Hauptdomain im Steam-Linkfilter gesperrt, während der Host, auf dem sich die Anmeldung befand, nicht gesperrt war – csgogem.com gesperrt, api.csgem.com seit März 2014 registriert. Steam erhält diesen Hostnamen in openid.realm und openid.return_to bei jeder Anmeldung. Abschnitt 3\nAm 13. Juli 2016 Valve benannte die Behörde den Mechanismus öffentlich und verbot ihn; in den Mitteilungen ihres Rechtsbeistands vom 20. Juli 2016 wurde eine Frist von zehn Tagen gesetzt. In den zehn Jahren seit Ablauf dieser Frist wurden keine Durchsetzungsdaten pro Betreiber veröffentlicht. Abschnitt 11\nDer Endpunkt „Steam“ für Web-API-Schlüssel stellte bis 2023 allein anhand eines Sitzungs-Cookies Zugangsdaten mit hohen Berechtigungen und Handelsberechtigung aus, ohne dass eine zweite Authentifizierungsstufe erforderlich war. Abschnitt 5\nEin Antrag gemäß Artikel 15 der DSGVO (Ticket HT-2YBP-F7JP-D4VB) wurde nach drei Tagen mit einem Link zum Self-Service und ohne Daten geschlossen. § 18\nWas wir von jeder Behörde verlangen\nGlücksspielkommission des Bundesstaates Washington\nÖffnen Sie die Datei aus dem Jahr 2016 erneut. Fordern Sie eine Aufstellung nach einzelnen Betreibern an, aus der hervorgeht, welche Konten, Bots und Return-Hosts nach den zehntägigen Benachrichtigungen deaktiviert wurden und welche Betreiber später wieder Zugriff erhielten. Abschnitt 2\nHmbBfDI (Hamburg; Valve GmbH)\nPrüfen Sie, ob die Antwort gemäß Artikel 15 der Pflicht des für die Verarbeitung Verantwortlichen entsprach, und verlangen Sie die Offenlegung der API-Schlüssel-Registrierungs- und Zugriffsprotokolle, die für die Identifizierung des Handelnden relevant sind. § 18\nDSA-Koordinatoren für digitale Dienste\nFügen Sie das „auth-host“-Routing als Hinweis in den Datensatz ein und prüfen Sie anschließend, ob die Antwort von Valve den Anforderungen entspricht, sobald die Informationen dokumentiert sind. § 16\nJede betroffene Person\nVerwenden Sie die Vorlage gemäß Artikel 15, um dieselben Aufzeichnungen für Ihr eigenes Konto anzufordern; anhand einer aufbewahrten Aufzeichnung lässt sich feststellen, wer eine Zurücksetzung veranlasst oder einen Schlüssel erstellt hat. Anhang G\n\nDie einzige Forderung, die hinter allen vier Fällen steht, ist dieselbe: die Veröffentlichung der Aufzeichnungen über Durchsetzungsmaßnahmen, Datenzugriffe und Datenverarbeitungen, über die ausschließlich Valve verfügt. Ein Warnhinweis auf der Startseite, ein zehntägiges Schreiben und eine Selbstbedienungsseite sind Ausdruck von Kontrolle. Ob diese Kontrolle tatsächlich ausgeübt wurde, ist eine Frage, die anhand der öffentlich zugänglichen Unterlagen nicht beantwortet werden kann, wohl aber von einer Aufsichtsbehörde.\n\nAnhänge – Primärdokumente und Arbeitsunterlagen\nAnhang A – Korrespondenz mit den Rechtsbeiständen\nBeweismemorandum – von Quelle 1 bereitgestelltes Material\n\nEvidenzgrundlage und Quellenangaben für die in den Abschnitten 1, 18 und 19 herangezogene Korrespondenz mit den Rechtsbeiständen.\n\nEvidenzbasis und Status der Quelle — von Quelle 1 bereitgestellte Dokumente\nDer Nutzer, dessen dauerhafte Sperre diese Überprüfung ausgelöst hat, ist nicht Gegenstand dieser Untersuchung. Ob diese Sperre gerechtfertigt war, wird hier nicht geprüft, und diese Akte verteidigt sie weder noch stellt sie sie in Frage. Es geht nicht um das Konto. Was zählt, ist das Material: Quelle 1 — Der Inhaber des gesperrten Kontos, der als betroffene Person im Rahmen seines eigenen DSGVO-Antrags die nachstehende Korrespondenz vom Rechtsbeistand von Valve erhalten hatte, hat diese Korrespondenz und die dazugehörigen Akten weitergeleitet, zusammen mit dem Recht auf öffentliche Einsichtnahme. Der Name wird zurückgehalten; die Dokumente sind nach Datum, Metadaten des Erstellers und Hash-Wert beschrieben.\n\nDiese Korrespondenz wurde als Antwort auf eine Anfrage gemäß DSGVO/DSAR versandt. Im Rahmen dieser Korrespondenz gab der Rechtsbeistand von Valve eine unterschriebene Erklärung zu Protokoll, in der eine Funktion beschrieben wurde, von der der Steam-Support den Nutzern zuvor mitgeteilt hatte, dass sie technisch nicht möglich sei. Der unten zitierte Absatz ist diese Erklärung.\n\nDie weitere Analyse des erstellten Protokollauszugs durch die Autoren lautet wie folgt: in diesem Dossier nicht enthalten vorbehaltlich einer unabhängigen Überprüfung. In keinem anderen Teil dieser Untersuchung wird darauf Bezug genommen.\n\nDas zu Protokoll genommene Eingeständnis: fortlaufende Telemetrie auf Geräteebene\n\nIn Absatz 1.9 des Schreibens, das dem Rechtsbeistand von Valve zugeschrieben wird, führen die Anwälte von Valve aus: „Zwischen 2019 und 2023 wurde dieses Konto hauptsächlich von einem Gerät aus genutzt, das auch dazu diente, sich bei Dutzenden gestohlener Steam-Konten anzumelden.“\n\nDie Tatsache: Der Anwalt von Valve beschreibt hier eine gerätebezogene Korrelation über verschiedene Konten hinweg, die sich über vier Jahre erstreckt. Der Support von Steam hat Diebstahlopfern mitgeteilt, dass die Nachverfolgung gestohlener Gegenstände oder die Verknüpfung von Konten mit Geräten technisch nicht möglich sei. Steam Guard Die Geräteautorisierung ist öffentlich dokumentiert, sodass die Existenz von Aufzeichnungen auf Geräteebene an sich nichts Neues ist; neu ist jedoch die schriftliche Bestätigung des Anwalts, dass diese Aufzeichnungen über mehrere Jahre hinweg aufbewahrt und kontoübergreifend miteinander verknüpft werden.\n\nWarum das wichtig ist: Die Korrelation, die ein Gerät über einen Zeitraum von vier Jahren mit Dutzenden von gekaperten Konten in Verbindung bringen kann, gehört zu derselben Kategorie von Aufzeichnungen, die der Support nach eigenen Angaben nicht zugunsten der Betroffenen nutzen konnte. Datensätze dieser Art würden es ermöglichen, Konten und Geräte in einer Kette von Diebstahl und Weiterverkauf zu identifizieren. Welche Datensätze existieren, wie lange sie aufbewahrt werden und auf welcher Grundlage sie den betroffenen Personen vorenthalten werden, sind Fragen, die an die Aufsichtsbehörde zu richten sind.\n\nQuelle: Schreiben des Rechtsbeistands von Valve vom 1. Oktober 2025, Absatz 1.9, sowie dessen 830-seitiger PDF-Anhang · eingegangen bei Quelle 1 als Antwort auf ein Ersuchen gemäß Art. 15 DSGVO · SHA-256 des Anhangs gespeichert in disclosure-audit.json · Der Brief selbst wird nicht wiedergegeben; Kontonamen und Daten Dritter wurden weggelassen.\n\nStatus: öffnen\nDie Quellenmaterialien sind über das Evidenzarchiv verfügbar.\nAnhang B – Die erstellte PDF-Datei · Redaktionsprüfung\nDie Schwärzung in der bereitgestellten PDF-Datei ist rein kosmetischer Natur: Der verdeckte Text lässt sich weiterhin extrahieren.\n\nDer Anwalt von Valve beantwortete einen Auskunftsantrag gemäß DSGVO mit einem 830-seitigen Anhang, in dem die Schwärzungen über den Text gemalt wurden, anstatt ihn zu entfernen. 902,270 Zeichen befinden sich unter den schwarzen Balken und werden mit einem Text-Extraktions-Tool direkt angezeigt — einschließlich der Identifikatoren von Drittanbietern, die durch die Balken verborgen werden sollten. Hier werden lediglich aggregierte Zahlen veröffentlicht; es werden keine geschützten Inhalte wiedergegeben, und der Anhang selbst wird nicht veröffentlicht.\n\n1. Was die Geometrieprüfung ergeben hat\n\nDie Antwort gemäß Art. 15 der DSGVO vom 1. Oktober 2025 Es lag ein 830-seitiger PDF-Anhang bei (Metadaten des Erstellers: Aspose.PDF für .NET, erstellt und geändert am selben Tag). Die Autoren führten eine Geometrieprüfung auf Seitenebene durch: Für jede Seite wurden undurchsichtige, fast schwarze Rechtecke, die über die Textebene gelegt worden waren, lokalisiert und die darunter liegenden extrahierbaren Zeichen gezählt.\n\nGemessen anhand der erstellten Datei\n902,270\nZeichen, die noch unter den schwarzen Balken hervorgeholt werden können\nZählen, nicht schätzen. Hierbei handelt es sich um eine Zählung der erfassten Personen – nicht der Opfer, der erneuten Identifizierungen oder der Vorfälle.\n830 / 830\nBetroffene Seiten – jede Seite\n986\nRechtecke über extrahierbarem Text\n1,329\nGesamtzahl der undurchsichtigen schwarzen Rechtecke\nDie schwarzen Balken werden über die Textebene gelegt; sie entfernen den Text nicht. Der unter den Balken liegende Text kann mit gängigen PDF-Tools extrahiert werden. Es werden lediglich Gesamtzahlen veröffentlicht; der verdeckte Inhalt wird hier nicht wiedergegeben.\nForensische Demonstration: Schichttrennung\nASPOSE.PDF FÜR .NET – VEKTOR-OVERLAY-MOCKUP (ANHANG, S. 412)\n\nMeldung zu diesem Konto: [LOGIN: redacted_user_667]\n\nVom Nutzer angegebener Grund: [TEXT: „Nutzer meldet doppelte Gegenstände im Inventar und missbräuchliches Handelsverhalten...“]\n\nVordergrund: <path fill=\"#000\" />Fehler: Der zugrunde liegende UTF-8-Stream bleibt unverändert\nQuelle: PDF-Anhang zum Anwaltsschreiben vom 1. Oktober 2025 (830 Seiten, Metadaten des Erstellers gemäß Aspose.PDF für .NET) · von den Autoren ermittelt, Methode und Seitenanzahl in disclosure-audit.json · SHA-256 des im selben Dateianhang enthaltenen Anhangs · Der Anhang selbst wird nicht veröffentlicht.\n2. Warum dies für die Reaktion einer betroffenen Person von Bedeutung ist\n\nDer Anwalt von Valve hat diese Akte als Antwort auf einen Antrag einer betroffenen Person auf Einsicht in ihre eigenen Unterlagen an diese gesendet. Die Schwärzungen dienen lediglich der optischen Maskierung: Der darunterliegende Text wurde nie entfernt, sodass die Identifikationsmerkmale Dritter, die durch die Schwärzungen verborgen werden sollten, zusammen mit der Datei an den Empfänger gelangten. Eine Schwärzung, die sich mit einem Text-Extraktions-Tool entfernen lässt, verbergen nichts und macht es dem Empfänger zudem unmöglich festzustellen, welche Informationen offengelegt wurden und welche nicht.\n\nArtikel 15 Absatz 4 ist der Grund, warum diese Sperren überhaupt bestehen: Das Recht auf Erhalt einer Kopie darf die Rechte und Freiheiten anderer nicht beeinträchtigen. Diese Verpflichtung hat diese Produktion nicht erfüllt. Ob dies als Verletzung des Schutzes personenbezogener Daten im Sinne von Art. 4 Abs. 12 einzustufen ist, obliegt der Aufsichtsbehörde; die Offenlegung selbst ist in der Datei messbar und von jedem reproduzierbar, der über dieselben Bytes verfügt – der SHA-256-Hash ist veröffentlicht, der Anhang hingegen nicht.\n\nWas sich unter den Strichen befand, waren keine Kontonummern. Es handelte sich um die Sammlung der gegen den Antragsteller eingereichten Nutzerberichte, zusammen mit den Namen ihrer Verfasser: Steam Anmeldungen, die – da eine Anmeldung selten nur auf Steam verwendet wird – die dahinter stehende Person identifizieren — Nach Angaben der Autoren sind über 60% der in dem Dokument genannten Nutzer vollständig identifizierbar — zusammen mit dem unbearbeiteten, ungeschwärzten Wortlaut ihrer Beiträge. Dieser Text enthält Todeswünsche und Beleidigungen, die sich gegen die Nationalität des Anfragenden richten. Einige der so identifizierten Personen sind minderjährig. Die Produktion übergab der Person, über die sie berichtet hatten, eine namentliche Liste von Reportern., was genau der Schaden ist, den Art. 15 Abs. 4 verhindern soll.\n\nDie Reihenfolge der Zeichen in der Datei ist genauso wichtig wie ihr Inhalt. Auf die Anfrage hin wurde zunächst ein weiterer Identitätsnachweis verlangt, mit der Begründung, dass die Alias-E-Mail-Adresse des Anfragenden nicht seinen Namen enthielt; während der darauf folgenden Verzögerung wurde das Konto dauerhaft gesperrt. In dem Schreiben, mit dem die Daten schließlich über sechs Wochen nach Ablauf der in Art. 12 Abs. 3 festgelegten Frist übermittelt wurden, wurde dem Empfänger mit strafrechtlicher Verfolgung gedroht und die Herausgabe der restlichen Daten zurückgehalten, bis er seine Kontoaktivitäten gegenüber dem Rechtsbeistand erläutert hatte. Die Offenlegung klärt zudem zwei Fragen, die Valve öffentlich nicht beantwortet hat: Die vorgelegten Unterlagen zeigen, dass die Verknüpfung von Konten bis ins Jahr 2019 zurückreicht, und es gibt interne Telemetriedaten in einem Umfang, den Valve noch nie beschrieben hat.\n\nGeltungsbereich dieses Abschnitts: Die hier vorgebrachte Feststellung beschränkt sich auf die technischen Aspekte der Bearbeitung, die anhand der vorgelegten Datei ermittelt wurden. Die weitere Analyse der vorgelegten Protokolle durch die Autoren wird bis zum Vorliegen einer unabhängigen Überprüfung zurückgehalten und an keiner anderen Stelle dieses Dossiers herangezogen.\n\nBeweismittel: Schreiben des Rechtsbeistands vom 1. Oktober 2025 und dessen PDF-Anhang (SHA-256 in der Prüfungsdatei gespeichert); PDF-Messungen auf Seitenebene und Methode ↗. Der Ablauf der Anfrage, die Ablehnung auf Seite 8 und die Beschreibung der offengelegten Datensätze sind in der Schilderung von PhishDestroy ausführlich dargelegt, „Mein Hund gegen Elite-DSG-Anwälte“, 17. August 2026 ↗ archiviert 2026-08-21 ↗. Kontonamen und Daten von Dritten wurden hier weggelassen; nichts, was von den Balken verdeckt wird, wird wiedergegeben.\n\nAuf Seite 8 des Begleitschreibens wird ein Teil des Antrags abgelehnt und der Grund dafür schriftlich dargelegt: Eine genauere Auskunft ist aufgrund des Schutzes der personenbezogenen Daten anderer Nutzer der Steam-Plattform… nicht möglich. — Eine detailliertere Antwort ist nicht möglich, da die personenbezogenen Daten anderer Steam-Nutzer geschützt werden müssen. Der 830-seitige Anhang befand sich im selben Paket. Was die Schwärzungen verdeckten, waren keine Kontonummern: Es handelte sich um die gegen den Antragsteller eingereichten Berichte, in denen die Verfasser namentlich genannt wurden und denen die unbearbeiteten, ungeschwärzten Nachrichten beigefügt waren. Der Kontoinhaber hatte über seinen Anwalt Valve um seine eigene Akte gebeten; was er daraus entnehmen konnte, betraf jedoch andere Personen. Nichts in diesem Anhang hängt davon ab, wer die Markierungen gesetzt hat. Es wird lediglich festgestellt, dass der Schutz Valve, der als Begründung für die Zurückhaltung angeführt wurde, genau der Schutz ist, den diese gleiche Herausgabe – im selben Umschlag, am selben Tag – nicht gewährleistet hat.\nUnterlagen zu Unterhaltsangelegenheiten und Rechtskorrespondenz\n\nQuelle: https://phishdestroy.io/steam_dossier/de/index#exhibit-gallery-section\n\nAnhang D – Quellenerhebung\nAusgewählte Primärquellen\n\nSechs Einträge aus dem Archiv – drei GitHub-Issues in den Trackern von Valve und drei Reddit-Beiträge zu umstrittenen Support-Ergebnissen. Jede Quelle bleibt mit der Behauptung, dem gespeicherten Text und der damit verbundenen Frage verknüpft.\n\n1 / 6 ausgewählte Datensätze\nWählen Sie einen Quelldatensatz aus\nGH-01 / GITHUBIn gespeicherter Version öffnen\nHardware-Schlüssel, angefordert im Jahr 2016\n\nValveSoftware / steam-for-linux · #4521 · 2016-06-27\n\nEin Nutzer hat Valve gebeten, U2F-Hardware-Schlüssel als alternative zweite Authentifizierungsstufe zu unterstützen. Das gespeicherte Ticket trägt sowohl das Label „Feature Request“ als auch das Label „reviewed“, und sein Status ist als „offen“ vermerkt.\n\nIch bitte darum, dass U2F-USB-Dongles in Steam als Alternative unterstützt werden.\n\nAuszug aus dem GitHub-Issue ↗\nDokumentierte Aufzeichnung\nEine veraltete Anfrage bezüglich einer zusätzlichen Kontosicherung, die im eigenen Issue-Tracker von Valve veröffentlicht und als „geprüft“ gekennzeichnet wurde.\nForderung nach Rechenschaftspflicht\nVeröffentlichen Sie die Produktentscheidung, das Antwortdatum und den nach der Prüfung gewährten Schutz.\nGespeicherten Datensatz lesen →GitHub öffnen ↗\nIm Dossier: Kontosicherheitsmaßnahmen →Archiv Nr. 484 · Build 2026-09-17\nGH-02 / GITHUBIn gespeicherter Version öffnen\nAbsturzberichte ohne wirksame Opt-out-Möglichkeit\n\nValveSoftware / steam-for-linux · #6459 · 2019-08-18\n\nDer Verfasser beschreibt einen Steam-Client vom 12. August 2019 unter Ubuntu 16. Er berichtet, dass die Deaktivierung des „crash-upload“-Ziels nach einem Neustart nicht beibehalten wurde, und fügt die entsprechende Konfiguration bei.\n\nWenn ich die `ServerURL` deaktiviere, wird sie nach jedem Neustart überschrieben.\n\nAuszug aus dem GitHub-Issue ↗ archiviert 2026-04-19 ↗\nDokumentierte Aufzeichnung\nEine konkrete Datenschutzbeschwerde mit Angabe des Kundendatums, des Betriebssystems und eines Auszugs aus der Konfiguration. Das gespeicherte Problem ist noch offen.\nForderung nach Rechenschaftspflicht\nErmitteln Sie die Untersuchung, die betroffenen Builds und die Änderung, durch die das Opt-out wirksam wurde.\nGespeicherten Datensatz lesen →GitHub öffnen ↗archiviert 2026-04-19 ↗\nIm Dossier: Die zugrunde liegenden Unterlagen anfordern →Archiv Nr. 467 · Build 2026-09-17\nGH-03 / GITHUBIn gespeicherter Version öffnen\nMissbrauch von Auth-Tickets an Valve gemeldet\n\nValveSoftware / Source-1-Games · #3857 · 2022-02-26\n\nDer Autor behauptet, dass ein Serverbetreiber Steam Authentifizierungstickets beibehalten habe, nachdem Spieler die Verbindung getrennt hatten, und irreführende Serverlisten verwendet habe. In dem Beitrag wird Valve gebeten, sich mit diesem Verhalten auseinanderzusetzen.\n\nSo sieht es aus, als wären ihre Server voll ausgelastet.\n\nAuszug aus dem GitHub-Issue ↗\nDokumentierte Aufzeichnung\nEine Meldung wegen Missbrauchs, die am 26. Februar 2022 im Tracker von Valve eingereicht wurde. Der gespeicherte Status lautet „offen“; die Meldung enthält Links zu Screenshots.\nForderung nach Rechenschaftspflicht\nLegen Sie das Untersuchungsergebnis und die Aufzeichnungen zu den Abhilfemaßnahmen für den gemeldeten Missbrauch von Authentifizierungstickets vor.\nGespeicherten Datensatz lesen →GitHub öffnen ↗\nIm Dossier: Umfang des Datensatzes →Archiv Nr. 768 · Build 2026-09-17\nRD-01 / REDDITAngaben zum Autor\n44 umstrittene Marktkäufe\n\nr/DotA2 · Name des Autors nicht angegeben · 2022-07-07\n\nDer Autor berichtet von 44 unbefugten Käufen im Market am 6. Juli 2022 und Verlusten in Höhe von etwa $500+. Er gibt an, dass die Zwei-Faktor-Authentifizierung aktiviert war, und beschreibt wiederholte Standardantworten des Supports.\n\nDas ist nun schon mein zweites Ticket, und ich habe immer noch keine Antwort von Steam erhalten, die nicht wie eine automatische Kopier-Einfüge-Vorlage wirkt.\n\nAuszug aus dem Reddit-Beitrag ↗ archiviert 2025-03-20 ↗\nDokumentierte Aufzeichnung\nEine zeitlich geordnete Aufstellung umstrittener Käufe mit Links zu Screenshots der Transaktionen und einer Antwort des Kundendienstes. Die Beträge und Ereignisse stammen aus dem Bericht des Autors.\nForderung nach Rechenschaftspflicht\nStimmen Sie die strittigen Käufe anhand der Transaktions- und Sitzungsprotokolle ab. Erläutern Sie die Gründe für die Entscheidung des Supports.\nGespeicherten Datensatz lesen →Reddit öffnen ↗archiviert 2025-03-20 ↗\nIm Dossier: Unterstützung und Durchsetzung →Archiv Nr. 4,533 · Build 2026-09-17\nRD-02 / REDDITAngaben zum Autor\nEine dauerhafte Sperre und ausgeschöpfte Rechtsmittel\n\nr/ohnePixel · Name des Autors nicht angegeben · 2024-12-09\n\nDer Autor bestreitet, dass es sich um eine dauerhafte Sperre handelt, und erklärt, dass sich die Begründung auf den Verdacht einer Kontoübertragung sowie auf Meldungen aus der Community stütze. Er berichtet von abgeschlossenen Support-Anfragen und plant, seine persönlichen Daten anzufordern.\n\nIch habe meine Situation geschildert und um weitere Informationen gebeten, aber sie bleiben bei ihrer Entscheidung und schließen meine Tickets.\n\nAuszug aus dem Reddit-Beitrag ↗\nDokumentierte Aufzeichnung\nEin gespeicherter Appell-Bericht, einschließlich der Gründe, die laut Autor die bereitgestellten Belege stützen, sowie Links zu vier Bildern. Das Datum der Veröffentlichung stammt aus dem ausgewählten Beleg-Export.\nForderung nach Rechenschaftspflicht\nErmitteln Sie die Gründe, die für die dauerhafte Sperre sprechen, sowie die Rechtsmittel, mit denen diese angefochten werden kann. Die Ablehnung eines Einspruchs stellt keine Begründung für die Entscheidung dar.\nGespeicherten Datensatz lesen →Reddit öffnen ↗\nIm Dossier: Die zugrunde liegenden Unterlagen anfordern →Archiv Nr. 4,766 · Build 2026-09-17\nRD-03 / REDDITAngaben zum Autor\nEin Neustart der Erholung und ein gemeldeter Verlust von $10,000\n\nr/legaladvice · Autor anonym · 2025-05-09\n\nDer Autor behauptet, dass der Support die Anmeldedaten zurückgesetzt und die Kontoschutzmaßnahmen deaktiviert habe, nachdem eine andere Person eine Wiederherstellungsanfrage gestellt hatte. Er berichtet von einem Verlust in Höhe von etwa US$10,000 von einem inaktiven Konto.\n\nSteam Der Support hat mein Passwort zurückgesetzt und alle Sicherheitsfunktionen meines Kontos deaktiviert.\n\nAuszug aus dem Reddit-Beitrag ↗\nDokumentierte Aufzeichnung\nEine gespeicherte Behauptung darüber, dass der Wiederherstellungsprozess die Kontosicherheitsmaßnahmen außer Kraft setzt. Der gespeicherte Beitrag gibt wieder, was der Autor laut eigenen Angaben vom Support erfahren hat.\nForderung nach Rechenschaftspflicht\nErmitteln Sie, wer die Zurücksetzung genehmigt hat, welche Nachweise zur Identitätsfeststellung akzeptiert wurden und wie das Zugriffsprotokoll aussieht. Die Kontowiederherstellung ist Teil der Sicherheitsmaßnahmen Valve.\nGespeicherten Datensatz lesen →Reddit öffnen ↗\nIm Dossier: Die zugrunde liegenden Unterlagen anfordern →Archiv Nr. 4,592 · Build 2026-09-17\n\nSechs ausgewählte Datensätze. GitHub-Beschreibungen geben Auskunft über den gespeicherten Build. Reddit-Beiträge enthalten die Berichte der Autoren.\n\nLade die sechs Datensätze herunter ↓\n\nDie durchsuchbare Version enthält 16,319 eindeutige Datensätze: 393 Trustpilot, 5,635 Reddit, 2,395 GitHub, 276 Web- und 7,620 Wiki-Einträge. Mehrere Einträge können sich auf dasselbe Ereignis beziehen. Der separate Master-Export mit 40,448 Zeilen hat einen anderen Umfang.\n\nDas gesamte Archiv durchsuchen ↗ · Manifest erstellen ↗ · Umfang und Anzahl der Datensätze →\n\nAnhang E – Fallstudie\nArchiSteamFarm und die Automatisierungsklausel\n\nEin Open-Source-Tool zum Sammeln von Karten, das laut eigener FAQ auf Millionen von Konten läuft – im Widerspruch zur Klausel (§ 4.C) der Nutzungsvereinbarung, die Automatisierung verbietet. Die Funktionsweise – was eine Farm bei Valve kaufen muss, bevor sie etwas produzieren kann, warum jede Art der Auszahlung einer Karte gegen die Lizenz verstößt, die Durchsetzungsbilanz und wer die Kartenwirtschaft moderiert – wird ausführlich beschrieben in Anlage V ↗.\n\nIn § 4.C des Steam-Abonnentenvertrags heißt es:\n\n„Es ist Ihnen untersagt, in irgendeiner Weise Skripte, Bots, Makros oder andere nicht von Menschen gesteuerte Systeme („Automatisierung“) zu verwenden, um mit den Inhalten und Diensten auf Steam zu interagieren.“ — Steam Abonnentenvertrag § 4.C (aktuell) ↗ archiviert 2026-09-18 ↗\n\nValve setzt diese Klausel durch. Das macht es sehr gut. Die FAQ zu ArchiSteamFarm (ASF) — ein Open-Source-Tool, das laut seiner eigenen Dokumentation auf mehr als ein paar Millionen Steam-Konten Seit der ersten Veröffentlichung vor über 11 Jahren – gibt es drei Steam Support-Meldungen, in denen Nutzer, die Bot-Netzwerke betrieben haben, dauerhaft gesperrt wurden. Valve hat die Netzwerke aufgedeckt, benannt und zerschlagen. Die relevante Frage ist daher nicht, ob Valve Automatisierung in großem Maßstab erkennen kann.\n\nDie offizielle Website des Projekts ArchiSteamFarm Häufig gestellte Fragen geht direkt auf das Risiko eines Verbots ein:\n\n„Angesichts der Tatsache, dass ASF seit seiner ersten Veröffentlichung vor über elf Jahren auf mehr als ein paar Millionen Steam-Konten eingesetzt wird, ist dies äußerst unwahrscheinlich – aber unabhängig von der tatsächlichen Wahrscheinlichkeit dennoch eine Möglichkeit.“\n\n„Valve räumt, wie hier dargelegt, eindeutig ein, dass es ‚Steam Faulenzer‘ gibt. Wenn du mich also fragst, bin ich mir ziemlich sicher: Wenn sie damit nicht einverstanden wären, hätten sie längst etwas unternommen, anstatt nur darauf hinzuweisen, dass diese VAC-mäßig Probleme verursachen könnten.“ Das Schlüsselwort lautet hier „Steam-Idler“, zum Beispiel ASF, und nicht „Game-Idler“.\"\n\n— ArchiSteamFarm FAQ, JustArchiNET. Quelle: GitHub-Wiki ↗ · wortgetreu überprüft 2026-09-22\n\nIn denselben FAQ wird die Frage „Wurde jemand deswegen gesperrt?“ wie folgt beantwortet: Ja, und gibt wieder, was Steam Support an drei von ihnen geschrieben hat:\n\n1,000+ Bots · Handelssperre\n„Es sieht so aus, als wäre dieses Konto zur Verwaltung eines Netzwerks von Bot-Konten genutzt worden. Der Einsatz von Bots stellt einen Verstoß gegen die Steam-Nutzungsbedingungen dar.“\n\nÜber 170 Bots · dauerhaft gesperrt, Winter-Sale 2017\n„Dieses Konto wurde dazu genutzt, auf Steam illegal Sammelkarten zu sammeln sowie damit verbundene und nicht ausschließlich kommerzielle Aktivitäten durchzuführen. Das Konto wurde dauerhaft gesperrt, und der Steam-Support kann zu diesem Thema keine weitere Unterstützung leisten.“\n\nÜber 120 Bots · dauerhaft gesperrt\n„Dieses und andere Konten wurden dazu genutzt, unsere Netzwerkinfrastruktur zu überlasten, was einen Verstoß gegen die Online-Verhaltensregeln Steam darstellt.“\n\n— Steam Support-Nachrichten, die in den ArchiSteamFarm FAQ unter der Rubrik „Wurde jemand deswegen gesperrt?“ wiedergegeben sind. Quelle ↗ · wortgetreu überprüft 2026-09-22\n\nLegen Sie die beiden Datensätze nebeneinander. Ein privater Nutzer mit 1,000 Farming-Bots wird identifiziert, darauf hingewiesen, dass „das Einsatz von Bots einen Verstoß gegen die Steam Nutzungsbedingungen darstellt“, und dauerhaft gesperrt. Die kommerziellen Plattformen in diesem Dossier betreiben automatisierte Steam-Konten als ihr Kerngeschäft in weitaus größerem Umfang und authentifizieren sich bei jeder Anmeldung über die eigene OpenID von Valve – und für keine von ihnen wurde bisher ein Durchsetzungsbericht pro Betreiber veröffentlicht. Die Klausel funktioniert. Die Frage ist nur, gegen wen sie sich richtet.\n\nDer ASF wird hier nichts vorgeworfen, und ihre Interpretation der Position von Valve ist ihre eigene – der Autor stellt klar, dass „der ASF nicht von Valve bevollmächtigt ist“. Das Tool wird hier als Messinstrument verwendet: Es zeigt, dass Valve Bot-Netzwerke aufspürt, sie namentlich nennt und dauerhaft sperrt. Valve könnte die Frage mit einem einzigen Satz klären, indem es veröffentlicht, welche kommerzielle Automatisierung es zulässt, und für jeden Betreiber dokumentiert, wie es mit dem Rest verfahren ist.\n\nWo sich das „Card Farming“ auf die Einnahmen von Valve auswirkt\n\nDie im Spiel gesammelten Sammelkarten werden auf dem Steam Community-Markt verkauft, der für jeden auf dem Markt abgeschlossenen Verkauf eine Gesamtgebühr von etwa 15% erhebt; Das Konto muss $5.00 USD für Steam ausgegeben haben, bevor es überhaupt eine Karte erhalten kann; und für das Erhalten von Karten ist der Besitz des Spiels oder der Kauf von In-Game-Inhalten erforderlich. Es wird hier keine geschätzte Gesamtumsatzzahl angegeben – der Betriebsumfang wird lediglich so angegeben, wie es in den ASF-FAQ steht. Die FAQ verzeichnen außerdem Valve Unterscheidungsmerkmale \"Steam Müßiggänger\" (Kartenfarmen) aus „Spiel-Faulenzer“; siehe die ASF – Häufig gestellte Fragen ↗. Die Einzelheiten sind ausführlich dargelegt in Anlage V – die Skala und die Falle der gewerblichen Nutzung.\n\nBetreffArchiSteamFarm — automatisiertes Sammeln von Karten\nAngegebener MaßstabMillionen von Konten (laut ASF-FAQ – genaue Anzahl der aktiven Konten nicht bestätigt)\nGezählt, nicht zitiert10,880,610 API-Einträge insgesamt in der ASF-eigenen Steam-Gruppe (5,360,499 uneingeschränkt, wie Steam zeigt) – die „Millionen“ in den FAQs sind keine Erfindung, sondern eine Zählung. 88.97% unterliegen keinerlei Steam Sperre. Die vollständige Übersicht über die Verbote ↗\nAngaben in der Dokumentation des Tools selbst\nASF meldet Konten im Headless-Modus an und hält Spiele im Leerlauf, um Karten zu erhalten, ohne den Steam-Client zu starten (gemäß der Projektdokumentation).\nIn den FAQ wird argumentiert, dass Valve sich der „Steam-Faulenzer“ bewusst sei und dass „sie bereits etwas unternommen hätten, wenn sie damit nicht einverstanden wären“.\nSeit über 11 Jahren wurden keine gezielten Durchsetzungsmaßnahmen gemeldet (laut FAQ); die daraus resultierenden Kartenumsätze im Community Market sind mit einer Gesamtgebühr von etwa 15% für Steam verbunden.\nIn den FAQ wird eine empfohlene Obergrenze von zehn Konten pro Betreiber genannt und auf Valve zurückgeführt: „Diese Empfehlung basiert auf internen Valve-Richtlinien sowie auf unseren eigenen Vorschlägen.“ Eine solche Richtlinie wurde von Valve nicht veröffentlicht.\nTechnische Obergrenze laut derselben FAQ: „Mit einer einzigen IP-Adresse und einer einzigen ASF-Instanz können Sie bis zu 100–200 Bots betreiben.“\nDie Spielzeit aus dem „Farming“ wird von Valve erfasst – „sie wird in der Regel etwa alle 30 Minuten aktualisiert“ – und in § 4.C wird das „Fälschen von Spielstatistiken (z. B. überhöhte Siege oder Niederlagen, XP, Spielzeit)“ als verbotene Handlung aufgeführt.\nQuellen\nOffizielles JustArchi ASF-FAQ-Wiki ↗ ArchiSteamFarm Repository ↗ archiviert 2026-09-24 ↗\nDie Automatisierungsklausel ist eindeutig formuliert; in den ASF-FAQ wird seit Jahren darauf hingewiesen, dass das Tool auf Millionen von Konten läuft; es wurden keine gezielten Durchsetzungsmaßnahmen dagegen gemeldet. Die Diskrepanz zwischen der Regel und ihrer Anwendung ist aktenkundig; der Grund dafür wird hier nicht näher erläutert.\nGesamte AusstellungDie Kartenwirtschaft: der Ablauf, der Umfang, die Lizenz und wer sie überwacht ↗Was ein Betrieb bei Valve kaufen muss, bevor er eine einzige Karte produzieren kann; die beiden Zeilen in § 4.C, die das „Card Farming“ anhand seiner Auswirkungen benennen; warum jede Art der Einlösung einer Karte gegen die Lizenz verstößt, die Valve verfasst hat, während Valve eine Gebühr am Eingang erhebt; die Durchsetzungsakte, einschließlich der VAC-Welle im Juni 2025 und der Ketten-Sperrung anhand gemeinsamer Telefonnummern; sowie die Valve-Mitarbeiter und Community-Moderatoren, die rund um Steam für die Verwaltung des Kartentauschs und der Sperrlisten zuständig waren.Die Erhebung zum VerbotWir haben Valve nicht gefragt, wie groß der Hof ist. Wir haben ihn gezählt. ↗10,880,610 Konten insgesamt (mit und ohne Beschränkung), die aus der eigenen Steam-Gruppe von ArchiSteamFarm ausgelesen werden, der die Software beim ersten Start standardmäßig automatisch beitritt, sofern der Benutzer die Einstellung zum Beitritt zur Gruppe nicht deaktiviert (wobei sowohl kommerzielle Bot-Farmen als auch reguläre Spieler erfasst werden, die die Standardeinstellung beibehalten haben). 88.97% unterliegen keinerlei Steam-Sperre; von den 11%, bei denen dies der Fall ist, handelt es sich bei 99.8% um rein kosmetische Community-Sperren, die den Handel in keiner Weise behindern. Nach einem Abgleich mit SteamRep bleiben 67.77% der aufgeführten Betrüger straffrei, sobald Anti-Cheat-Sperren aufgehoben werden. Mit Aufschlüsselungen nach Registrierungsdatum, geografischer Herkunft und Überlebensrate – das tatsächliche Ausmaß, gemessen, nicht nur beschrieben.\n\nAppendix F — Working ledger\n\nRules ledger: clauses against recorded platforms\n\nWählen Sie eine Regel aus; im Register werden die darunter zugeordneten Plattformen mit ihrer Hauptdomain, dem angegebenen Authentifizierungshost und dem gespeicherten Ergebnis des Linkfilters aufgelistet. Eine gesperrte Website, eine andere Domain für die Anmeldung: Folgen Sie der Regel bis zu der verbleibenden Route.\n\n175verknüpfte Datensätze\nzu dieser Regel\n174 Primärdomänen0 C&D-Erwähnungen\nAUSZUG AUS DER VERORDNUNG / SSA § 2.G\nKommerzielle Nutzung und Abrechnung über das Konto\n“…exploit the Content and Services or any of its parts for any commercial purpose, except as expressly permitted elsewhere in this Agreement (including any Subscription Terms or Rules of Use).”\nFOLGE DEN AUFZEICHNUNGEN\nPlattformregister 175\nDie Zahlen in der Skala sind Schätzungen der Quelle.\n\n175 aus den Aufzeichnungen von „175“\n\nDienstleistung / Muttergesellschaft\tHauptdomain / Registrierungsstelle\tBeobachtete Authentifizierungsdomäne / Alter\tSkala / aufgezeichnete Reaktion\n\nCasino\n\tcsgoempire.com\n11.3 yearsRegistered 2015-06-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgoempirelogin4.com\n6.2 yearsRegistered 2020-07-20\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustreaper.com\n23.2 yearsRegistered 2003-06-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustreaper.com\n23.2 yearsRegistered 2003-06-24\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustly.com\n12.4 yearsRegistered 2014-05-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustly.com\n12.4 yearsRegistered 2014-05-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette Casino\n\tcsgofast.com\n11.5 yearsRegistered 2015-03-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsteam-login.authtofast.com\n83 daysRegistered 2026-06-30\nRDAP ↗ · authtofast.com (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tduelbits.com\n6.6 yearsRegistered 2020-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nswitchflips.com\n6.4 yearsRegistered 2020-04-21\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opener\n\tfarmskins.com\n10.5 yearsRegistered 2016-03-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsteam.kobal.cc\n9.7 yearsRegistered 2017-01-07\nRDAP ↗ · kobal.cc (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgoluck.com\n9.3 yearsRegistered 2017-05-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgoluck.com\n9.3 yearsRegistered 2017-05-18\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tinsane.gg\n7.5 yearsRegistered 2019-04-02\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.insane.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcs2skin.com\n3.5 yearsRegistered 2023-03-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncs2skin.com\n3.5 yearsRegistered 2023-03-06\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tjuice.gg\n7.9 yearsRegistered 2018-10-19\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nletmeinjuice.com\n2.4 yearsRegistered 2024-04-15\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tggdrop.com\n8.6 yearsRegistered 2018-02-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nggauth.com\n3.4 yearsRegistered 2023-05-03\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Casino\n\thowl.gg\n9.5 yearsRegistered 2017-03-16\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhowl.uno\n41 daysRegistered 2026-08-11\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tchicken.gg\n5.7 yearsRegistered 2021-01-11\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nchicken.gg\n5.7 yearsRegistered 2021-01-11\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgocasino.gg\n2.6 yearsRegistered 2024-02-17\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.csgocasino.gg\n2.6 yearsRegistered 2024-02-17\nWHOISFREAKS ↗ · csgocasino.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Casino\n\thunt.gg\n6.9 yearsRegistered 2019-11-04\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.hunt.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Battles\n\tcsbattle.com\n9.8 yearsRegistered 2016-12-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsbattle.com\n9.8 yearsRegistered 2016-12-10\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskinrave.gg\n3.1 yearsRegistered 2023-08-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinrave.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsdouble.gg\n261 daysRegistered 2026-01-03\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsdouble.gg\n261 daysRegistered 2026-01-03\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustchance.com\n8.0 yearsRegistered 2018-10-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhgfuihd.com\n7.6 yearsRegistered 2019-01-27\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Automation\n\tcobaltlab.tech\n3.5 yearsRegistered 2023-03-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncobaltauth.com\n1.7 yearsRegistered 2025-01-07\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\traided.gg\n171 daysRegistered 2026-04-03\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.raided.gg\n171 daysRegistered 2026-04-03\nIP2WHOIS ↗ · raided.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustneo.gg\n1.3 yearsRegistered 2025-06-20\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustneo.gg\n1.3 yearsRegistered 2025-06-20\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tsplits.gg\n3.7 yearsRegistered 2023-01-23\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsplits.gg\n3.7 yearsRegistered 2023-01-23\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Upgrader\n\tupgrader.pro\n1.2 yearsRegistered 2025-07-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nupgauth.space\n38 daysRegistered 2026-08-14\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskin.fans\n8.2 yearsRegistered 2018-07-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skinfans.com\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\thotpizza.one\n1.8 yearsRegistered 2024-12-07\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhotpizza.one\n1.8 yearsRegistered 2024-12-07\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tg4skins.com\n10.1 yearsRegistered 2016-08-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.g4s.to\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2royal.com\n4.1 yearsRegistered 2022-08-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ntf2auth.com\n5.2 yearsRegistered 2021-07-27\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2hunt.com\n8.7 yearsRegistered 2018-01-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrstspcl.com\n6.1 yearsRegistered 2020-08-08\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2.bet/coinflip\n8.4 yearsRegistered 2018-05-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ntf2.bet\n8.4 yearsRegistered 2018-05-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\topenstars.gg\n131 daysRegistered 2026-05-13\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nopenstars.gg\n131 daysRegistered 2026-05-13\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tskins.com\n25.1 yearsRegistered 2001-08-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skins.com\n25.1 yearsRegistered 2001-08-08\nRDAP ↗ · skins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\twhite.market\n9.6 yearsRegistered 2017-03-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwhite.market\n9.6 yearsRegistered 2017-03-01\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tmoon.market\n7.6 yearsRegistered 2019-02-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmoon.market\n7.6 yearsRegistered 2019-02-27\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tcsfloat.com\n5.2 yearsRegistered 2021-07-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgofloat.com\n11.0 yearsRegistered 2015-09-29\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tskin.land\n4.7 yearsRegistered 2022-01-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skin.land\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\thaloskins.com\n2.8 yearsRegistered 2023-12-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhaloskins.com\n2.8 yearsRegistered 2023-12-10\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCorporate Market\n\tbuff.163.com\n29.0 yearsRegistered 1997-09-15\nRDAP ↗ · 163.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\nbuff.163.com\n29.0 yearsRegistered 1997-09-15\nRDAP ↗ · 163.com (parent)\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\tmarket.csgo.com\n26.6 yearsRegistered 2000-02-07\nRDAP ↗ · csgo.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\ndota2.net\n14.9 yearsRegistered 2011-10-29\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRegulated Market\n\tskinport.com\n8.0 yearsRegistered 2018-09-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinport.app\n6.3 yearsRegistered 2020-06-20\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMarketplace/Swap\n\tskinflow.gg\n3.8 yearsRegistered 2022-11-26\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinflow.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tskin.place\n6.0 yearsRegistered 2020-09-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skin.place\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tskinsmonkey.com\n5.7 yearsRegistered 2021-01-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinsmonkey.com\n5.7 yearsRegistered 2021-01-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCorporate Market\n\tskinbaron.de\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinbaron.com\n10.7 yearsRegistered 2015-12-22\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Market\n\trust.tm\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\ndota2.net\n14.9 yearsRegistered 2011-10-29\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tpirateswap.com\n6.0 yearsRegistered 2020-09-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nlogin.pirateswap.com\n6.0 yearsRegistered 2020-09-22\nRDAP ↗ · pirateswap.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Marketplace\n\tmannco.store\n8.6 yearsRegistered 2018-03-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmannco.store\n8.6 yearsRegistered 2018-03-02\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tskinswap.com\n9.9 yearsRegistered 2016-11-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinswap.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\texeskins.com\n2.1 yearsRegistered 2024-08-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nexeskins.com\n2.1 yearsRegistered 2024-08-14\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tbalticskins.com\n153 daysRegistered 2026-04-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nbalticskins.com\n153 daysRegistered 2026-04-21\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tcs.trade\n8.9 yearsRegistered 2017-11-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncs.trade\n8.9 yearsRegistered 2017-11-14\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\trapidskins.com\n4.5 yearsRegistered 2022-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.rapidskins.com\n4.5 yearsRegistered 2022-03-11\nRDAP ↗ · rapidskins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\ttradeit.gg\n9.1 yearsRegistered 2017-08-21\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nconnect-tradeit.com\n4.6 yearsRegistered 2022-02-23\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\t49skins.com\n3.4 yearsRegistered 2023-04-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.49skins.com\n3.4 yearsRegistered 2023-04-19\nRDAP ↗ · 49skins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tskinvault.gg\n3.4 yearsRegistered 2023-05-06\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinvault.gg\n3.4 yearsRegistered 2023-05-06\nIP2WHOIS ↗ · skinvault.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Trading\n\taim.market\n3.3 yearsRegistered 2023-05-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\naim.market\n3.3 yearsRegistered 2023-05-22\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Sell Portal\n\tskinout.gg\n5.6 yearsRegistered 2021-02-27\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skinout.gg\n5.6 yearsRegistered 2021-02-27\nIP2WHOIS ↗ · skinout.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Trading\n\tntskins.com\n230 daysRegistered 2026-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nntskins.com\n230 daysRegistered 2026-02-03\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Portal\n\tgamerpay.gg\n6.0 yearsRegistered 2020-10-02\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ngamerpay.gg\n6.0 yearsRegistered 2020-10-02\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Scrap Swap\n\tscrap.tf\n14.0 yearsRegistered 2012-09-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nscrap.tf\n14.0 yearsRegistered 2012-09-03\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Cashout\n\tmarketplace.tf\n14.0 yearsRegistered 2012-09-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmarketplace.tf\n14.0 yearsRegistered 2012-09-19\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Cashout\n\tskins.cash\n10.5 yearsRegistered 2016-03-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinscash.live\n6.8 yearsRegistered 2019-12-05\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgo.net\n14.2 yearsRegistered 2012-07-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncn2.easylot.net\n10.0 yearsRegistered 2016-09-03\nRDAP ↗ · easylot.net (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCommunity Hub\n\tcybershoke.net\n6.8 yearsRegistered 2019-11-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.cybershoke.net\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMatchmaker Hub\n\tfastcup.net\n14.6 yearsRegistered 2012-02-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.fastcup.net\n14.6 yearsRegistered 2012-02-16\nRDAP ↗ · fastcup.net (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Analytics\n\tleetify.com\n7.6 yearsRegistered 2019-03-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nleetify.com\n7.6 yearsRegistered 2019-03-01\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Analytics\n\tscope.gg\n7.8 yearsRegistered 2018-12-10\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nscope.gg\n7.8 yearsRegistered 2018-12-10\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tools\n\ttradeupspy.com\n6.5 yearsRegistered 2020-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.tradeupspy.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMarketplace\n\tcs.deals\n9.8 yearsRegistered 2016-12-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.cs.deals\n9.8 yearsRegistered 2016-12-03\nRDAP ↗ · cs.deals (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Price DB\n\tpricempire.com\n6.6 yearsRegistered 2020-01-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\npricempire.com\n6.6 yearsRegistered 2020-01-30\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Blackmarket\n\tFSB Market\n7.2 yearsRegistered 2019-07-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nFSB Market\n7.2 yearsRegistered 2019-07-27\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nReady-Account Hub\n\tz2u.com\n26.9 yearsRegistered 1999-11-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwww.z2u.com\n26.9 yearsRegistered 1999-11-10\nRDAP ↗ · z2u.com (parent)\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Gambling\n\tcsgoroll.com\n11.6 yearsRegistered 2015-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwww.csgoroll.com\nRegistry date unavailableRegistry date unavailable\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\trollbit.com\n11.9 yearsRegistered 2014-11-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrbsnin.com\n3 daysRegistered 2026-09-18\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nLicenced Casino\n\t500.casino\n5.9 yearsRegistered 2020-11-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette/Slots\n\tcsgobig.com\n11.4 yearsRegistered 2015-04-12\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcasedrop.com\n14.8 yearsRegistered 2011-12-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\tbanditcamp.com\n12.2 yearsRegistered 2014-06-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tskinbox.com\n18.8 yearsRegistered 2007-12-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\ttastydrop.com\n6.1 yearsRegistered 2020-08-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette Casino\n\tcsgopolygon.gg\n6.5 yearsRegistered 2020-03-28\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tmagicdrop.ru\n10.3 yearsRegistered 2016-05-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nDice Casino\n\tcsdice.com\n3.8 yearsRegistered 2022-11-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUpgrader Casino\n\tskinodds.com\n1.2 yearsRegistered 2025-06-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgowin.com\n12.0 yearsRegistered 2014-09-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrash Casino\n\tcsgorun.net\n7.3 yearsRegistered 2019-06-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\topenskins.com\n3.6 yearsRegistered 2023-02-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Gambling\n\trustbet.com\n7.6 yearsRegistered 2019-02-07\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgomagic.com\n9.4 yearsRegistered 2017-05-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUpgrader/Contract\n\tcsgobounty.com\n11.5 yearsRegistered 2015-03-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tezskins.com\n27.5 yearsRegistered 1999-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\trustcases.com\n7.2 yearsRegistered 2019-06-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgoreaper.com\n11.1 yearsRegistered 2015-08-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgocases.com\n12.3 yearsRegistered 2014-06-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Upgrader\n\tcsgo-skins.com\n11.2 yearsRegistered 2015-07-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgonet.com\n8.8 yearsRegistered 2017-12-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\twtfskins.com\n9.0 yearsRegistered 2017-10-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Casino\n\tflamecases.com\n10.0 yearsRegistered 2016-09-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tgamedom.com\n11.7 yearsRegistered 2015-01-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Battles\n\tskin.club\n9.0 yearsRegistered 2017-09-04\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsc-auth.net\n7.5 yearsRegistered 2019-04-02\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tdaddyskins.com\n9.9 yearsRegistered 2016-10-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Gambling\n\trustix.gg\n1.7 yearsRegistered 2025-01-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Upgrade\n\tskins.club\n4.2 yearsRegistered 2022-07-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgohouse.org\n146 daysRegistered 2026-04-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskinrave.net\n216 daysRegistered 2026-02-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tbloodycase.gg\n19 daysRegistered 2026-09-02\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nClicker/Upgrade\n\tcsgoclicker.com\n8.3 yearsRegistered 2018-05-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustbet.gg\n4.0 yearsRegistered 2022-09-30\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcs-drop.com\n262 daysRegistered 2026-01-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\thellstore.net\n11.7 yearsRegistered 2015-01-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustloot.com\n354 daysRegistered 2025-10-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgo-case.com\n10.3 yearsRegistered 2016-05-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgogem.com\n9.9 yearsRegistered 2016-10-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\trainbet.com\n8.8 yearsRegistered 2017-11-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nservices.rainbet.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustclash.com\n5.4 yearsRegistered 2021-05-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrash Casino\n\t12cs.fail\n181 daysRegistered 2026-03-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\twww.tf2easy.com\n6.3 yearsRegistered 2020-06-02\nRDAP ↗ · tf2easy.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2blaze.com\n7.6 yearsRegistered 2019-01-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tshuffle.com\n30.1 yearsRegistered 1996-07-31\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tbuff.market\n5.9 yearsRegistered 2020-10-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tavan.market\n8.3 yearsRegistered 2018-05-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Engine\n\tcs.money\n11.0 yearsRegistered 2015-09-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.dota.trade\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tuuskins.com\n2.6 yearsRegistered 2024-01-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Market\n\tyoupin898.com\n6.1 yearsRegistered 2020-08-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tc5game.com\n10.5 yearsRegistered 2016-03-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\twaxpeer.com\n7.3 yearsRegistered 2019-05-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwaxpeer.com\n7.3 yearsRegistered 2019-05-20\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBot Trading\n\tcs.money\n11.0 yearsRegistered 2015-09-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.dota.trade\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUS Marketplace\n\tdmarket.com\n30.2 yearsRegistered 1996-07-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nOfficial Market\n\tsteamcommunity.com/market\n20.3 yearsRegistered 2006-05-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNot an external login site2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Platform\n\tlootfarm.com\n11.9 yearsRegistered 2014-10-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Market\n\trustskins.com\n7.6 yearsRegistered 2019-01-31\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tkrakatoa.com\n26.4 yearsRegistered 2000-05-15\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\tshadowpay.com\n10.1 yearsRegistered 2016-08-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nChinese Powerhouse\n\tigxe.cn\n15.0 yearsRegistered 2011-09-06\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAutomated Swap\n\tswap.gg\n9.6 yearsRegistered 2017-01-29\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCash-out Portal\n\tbitskins.com\n11.2 yearsRegistered 2015-07-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Automation\n\ttf2mart.com\n1.1 yearsRegistered 2025-08-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Auctions\n\tskinbid.com\n10.2 yearsRegistered 2016-06-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Rental\n\tlootbear.com\n8.7 yearsRegistered 2018-01-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Valuation\n\tbackpack.tf\n14.4 yearsRegistered 2012-05-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Botnet\n\tstntrading.eu\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Cashout\n\tskinwallet.com\n18.0 yearsRegistered 2008-09-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nDota 2 Market\n\tdota2market.com\n12.2 yearsRegistered 2014-07-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nServer Network\n\txplay.gg\n5.3 yearsRegistered 2021-06-13\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMatchmaking Portal\n\tesportal.com\n26.8 yearsRegistered 1999-12-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nLATAM Hub\n\tgamersclub.com.br\n11.2 yearsRegistered 2015-06-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tools\n\tepidemic.gg\n4.9 yearsRegistered 2021-11-03\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tcs2stash.com\n3.5 yearsRegistered 2023-03-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tcsgoskins.gg\n6.8 yearsRegistered 2019-12-21\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tsteamanalyst.com\n12.6 yearsRegistered 2014-02-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Exchange\n\tsteamcardexchange.net\n13.3 yearsRegistered 2013-05-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tracker\n\tdotabuff.com\n14.2 yearsRegistered 2012-06-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tracker\n\ttracker.gg\n8.9 yearsRegistered 2017-10-12\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Exchange\n\tfunpay.com\n17.0 yearsRegistered 2009-09-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nGrey Market\n\tplayerauctions.com\n26.3 yearsRegistered 2000-06-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Portal\n\teldorado.gg\n8.0 yearsRegistered 2018-09-12\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Key Market\n\tg2a.com\n24.8 yearsRegistered 2001-12-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Key Market\n\tkinguin.net\n16.8 yearsRegistered 2009-12-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nVirtual Services\n\tg2g.com\n31.1 yearsRegistered 1995-08-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Broker\n\tplayerup.com\n19.3 yearsRegistered 2007-05-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfhub.net\n2.7 yearsRegistered 2023-12-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfaccounts.com\n5.3 yearsRegistered 2021-05-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Shop\n\tbuycsgorank.com\n6.2 yearsRegistered 2020-07-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tcsgosmurfkings.com\n9.3 yearsRegistered 2017-06-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfstore.co\n8.6 yearsRegistered 2018-03-03\nWHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlvlup.com\n9.9 yearsRegistered 2016-11-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlevels.com\n10.6 yearsRegistered 2016-02-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tlevelsteam.com\n79 daysRegistered 2026-07-04\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlevelu.com\n6.0 yearsRegistered 2020-09-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\teloking.com\n12.2 yearsRegistered 2014-07-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\tboosteria.org\n11.9 yearsRegistered 2014-10-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tovergear.com\n14.4 yearsRegistered 2012-04-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tblazingboost.com\n14.2 yearsRegistered 2012-06-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\tdota2boost.com\n2.9 yearsRegistered 2023-10-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tbuyboost.com\n22.4 yearsRegistered 2004-04-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\nDie Argumentation der UntersuchungAusgewählte Vorschrift / Analyse und Kommentar+\nBeweislast\n\nDie Untersuchung hinterfragt die Diskrepanz zwischen den Beschränkungen der gewerblichen Nutzung und den hier aufgeführten Dienstleistungen. Klassifizieren Sie jede Aktivität und stellen Sie fest, ob eine ausdrückliche Genehmigung vorliegt, bevor Sie von einem Vertragsverstoß sprechen. Die Gebühren für den Community Market gelten nicht für jeden externen Handel.\n\nWas ein „tagged record“ ist und was nicht\n\nEin Eintrag wird markiert, wenn die Akte eine datierte Feststellung enthält, durch die die Plattform dem Wortlaut der Klausel entspricht. Eine Markierung stellt keinen festgestellten Verstoß dar, und für keine der hier aufgeführten Plattformen wurde eine ausdrückliche Genehmigung gemäß Valve in den Unterlagen erteilt. Verfügt eine Plattform über eine Genehmigung, wird der Eintrag durch deren Veröffentlichung aufgehoben.\n\nQuellen und MethodikSchätzungen, Definitionen und Geltungsbereich+\n\nDie oben genannten Zahlen beziehen sich auf die ausgewählte Regel. Datensatztypen werden pro Plattform jeweils einmal zusammengefasst; vollständige Tags werden in den Plattformdetails angezeigt. Die Suche und Filter gelten innerhalb dieser Regel. Die Registrierungsdaten stammen aus dem gespeicherten Snapshot unter RDAP / WHOIS. Subdomains verwenden das Erstellungsdatum der übergeordneten Domain. Das Alter allein ist kein Hinweis auf einen kontinuierlichen Betrieb oder einen Authentifizierungsweg. Aktuelle Authentifizierungs-Hostnamen stammen aus gespeicherten OpenID-Anfragen mit einem UTC-Zeitstempel; bei nicht aufgelösten Prüfungen werden keine alten Bezeichnungen wiederverwendet. Der Beobachter stoppt vor der Anmeldung unter Steam und testet den Status des Steam-Linkfilters nicht. Streckenbeobachtungen herunterladen ↗ Registrierungsergebnisse herunterladen ↗\n\nDas Quellarchiv erkunden ↗\nAnhang G – Von einer Standardablehnung zum zugrunde liegenden Datensatz\nDSAR-Leitfaden: Anforderung der Nachweise\n\nNutzen Sie Artikel 15 DSGVO, um personenbezogene Daten im Zusammenhang mit der Erstellung von API-Schlüsseln, der Kontowiederherstellung und dem Supportzugang anzufordern. Anhand einer gespeicherten Aufzeichnung lässt sich nachprüfen, wer eine Aktion ausgelöst hat und worauf sich die Plattform dabei gestützt hat.\n\n01\nBewahre deine Zeitleiste auf.\n\nSpeichern Sie Kontobenachrichtigungen, Tickets, Transaktions-IDs und Datumsangaben in UTC. Sichern Sie das Konto und prüfen Sie die für das Spiel und die Transaktion geltenden Wiederherstellungsoptionen.\n\nSteam Informationen zum Handelsschutz ↗\n02\nFordern Sie Ihre gespeicherten Daten an.\n\nFragen Sie nach Zeitstempeln, Quell-IP-Adressen, wichtigen Ereignissen im Lebenszyklus von Schlüsseln, Sicherheitsbestätigungen und Maßnahmen zur Kontowiederherstellung. Beziehen Sie Ereignisse im Zusammenhang mit dem Support-Zugriff sowie die Empfänger mit ein, sofern diese Daten für Sie relevant sind.\n\n03\nBewahren Sie den Lieferschein auf.\n\nNutzen Sie den Datenschutz-Kontaktweg von Valve. Die übliche Bearbeitungsfrist beträgt einen Monat; eine erforderliche Verlängerung um bis zu zwei weitere Monate muss innerhalb dieses ersten Monats begründet werden.\n\nValve Datenschutz – Kontakt – Wegbeschreibung ↗ archiviert 2026-09-21 ↗\n04\nVergleiche die Antwort.\n\nGleichen Sie die Protokolle mit Ihrem Zeitablauf ab. Fragen Sie nach den Gründen für Auslassungen und nutzen Sie gegebenenfalls den Beschwerdeweg bei der Aufsichtsbehörde. Bewahren Sie die Antwort genau so auf, wie Sie sie erhalten haben.\n\nGeltungsbereich / Artikel 15\n\nDas Auskunftsrecht erstreckt sich auf gespeicherte personenbezogene Daten, einschließlich Daten in Protokollen. Es garantiert jedoch keinen Zugang zu allen internen Dokumenten, rekonstruierten Aufzeichnungen oder ungeschwärzten Daten über andere Personen. Fordern Sie eine verständliche Kopie sowie die Begründung für etwaige Einschränkungen an.\n\nZugangsrichtlinien des EDPB, §§ 2, 4–6 ↗ · Artikel 12, 15 und 77 der DSGVO ↗ archiviert 2026-09-20 ↗\n\nAuskunftsersuchen der betroffenen PersonDSGVO / Artikel 15\nKontosicherheit und Zugriffsprotokolle\n\nErsetzen Sie die Felder in Klammern, bevor Sie das Formular absenden.\n\nTo: Valve Privacy Team\nSubject: Article 15 GDPR request — account security records\n\nAccount / SteamID: [YOUR ACCOUNT IDENTIFIER]\nRelevant period (UTC): [START] to [END]\nRelated support tickets: [TICKET REFERENCES]\n\nI request a copy of the personal data concerning me that you retain for this period, including:\n\n1. API-key registration, confirmation, use and revocation events, with available timestamps, source IP addresses, registered domains, device or user-agent information and non-secret key identifiers.\n\n2. Recorded account-recovery actions, password/email/phone changes, Steam Guard removals or resets, confirmation events and the account-related evidence relied on to authorize those actions.\n\n3. Personal data in support-access and administrative-action logs concerning my account, including available dates, purposes, actions and the support entity involved, subject to applicable rights of others.\n\n4. Account-related records used to determine any sanction, and available records of my complaints, reviews and responses.\n\nPlease also provide the applicable processing purposes, categories, recipients, retention periods or criteria, and available information about sources where data were not obtained from me.\n\nWhere processing relies on my consent, please provide the retained record of the consent relied upon and the wording presented at that time.\n\nPlease provide an intelligible electronic copy with time zones and field definitions. Please do not include active credentials or secret tokens. If any requested data are not held, please say so. For any withheld data, please identify the scope and legal basis of the restriction and provide the remainder.\n\nPlease acknowledge receipt and respond within the applicable Article 12 period, explaining any necessary extension. I also ask you to preserve relevant existing records while this request is handled.\n\nName: [YOUR NAME]\nDate: [DATE]\nWas eine IP-Adresse im Rechenzentrum leisten kann\nEine Unstimmigkeit ist ein Anhaltspunkt für weitere Untersuchungen.\n\nEine API-Schlüsselanfrage, die aus einem Rechenzentrumsnetzwerk stammt, wie im Rahmen dieser Untersuchung angeführten Beispiel des Hosting-Anbieters, kann im Zusammenhang mit Anmeldedaten, Bestätigungen und der Zeitleiste des Nutzers von Bedeutung sein. Eine IP-Adresse allein identifiziert den Akteur nicht und umgeht nicht automatisch alle Schutzmaßnahmen. Der Nachweis, dass ein böswilliger Akteur die aufgezeichnete Einwilligung bereitgestellt hat, könnte die Verlässlichkeit dieser Einwilligung in Frage stellen; andere Rechtsgrundlagen und Haftungsfragen erfordern eine gesonderte Analyse.\n\nSiehe die archivierte Beschwerde bezüglich des Verbots und der DSGVO →\nAnhang H – Analyse des Wayback-Machine-Archivs · Veröffentlichte Support-Statistiken\nSupport-Umfang. Veröffentlichte Reaktionszeiten.\nKontext und Quellenbeschränkungen\n\nValve veröffentlicht täglich Support-Statistiken unter store.steampowered.com/stats/support. Die Archive der Wayback Machine bewahren historische Momentaufnahmen dieser Seite aus den Jahren 2018 bis 2026 auf. Das aus diesen Zahlen abgeleitete Verhältnis von Fallvolumen zu Personalbestand steht im Widerspruch zu einer manuellen Überprüfung jedes einzelnen Tickets innerhalb der angegebenen Bearbeitungszeiten.\n\nVergleichen Sie die archivierten Unterstützungswerte von Valve in den gespeicherten Momentaufnahmen. In der Methodik wird erläutert, was diese Werte messen können und was nicht.\n\nAufkommen im Vergleich zur veröffentlichten Reaktionszeit (2018 → 2026)\nZwei Warteschlangen an einem Support-Schalter, wie aus 21 archivierten Screenshots hervorgeht.\n\nValve veröffentlicht Zahlen zum Live-Support unter store.steampowered.com/stats/support. Jeder der unten aufgeführten Punkte entspricht dem unteren Grenzwert Valve, der an dem Tag, an dem das Internet Archive die Seite erfasst hat, dort tatsächlich angegeben war – es handelt sich nicht um eine Schätzung unsererseits. Da beide Reihen dieselbe Größe in derselben Einheit darstellen, gehören sie auf eine Achse und lassen sich direkt miteinander vergleichen.\n\nRückerstattungsanträge — Geld Valve ist im Besitz vonKontosicherheit und Wiederherstellung — das Konto, das Sie verloren haben\n0 h\n2 h\n4 h\n6 h\n8 h\n10 h\nno captures · 38 months\n2019\n2020\n2021\n2022\n2023\n2024\n2025\n2026\n8 h 44 m\naccount recovery\n52 m\nrefunds\n15 m — one capture only\n49–55 Min.Die Untergrenze der Rückvergütung in jedem Erfassungszeitraum von Februar 2018 bis August 2026. Über einen Zeitraum von achteinhalb Jahren verschiebt sie sich um weniger als sechs Minuten, während sich das tägliche Rückvergütungsvolumen um den Faktor neun verändert.\n2,4 h → 8,7 hDie Untergrenze für die Kontowiederherstellung liegt in allen Erhebungen bis einschließlich Dezember 2022 mit einer Ausnahme bei etwa 2,4 Stunden. In den drei Erhebungen für das Jahr 2026 gibt Valve Werte von 10,9 h, 5,8 h und 8,7 h an.\n×2,8 → ×13Um wie viel langsamer die Rückerstattung im Vergleich zu Rückzahlungen ist – laut den von Valve selbst veröffentlichten Zahlen. Fünf Jahre lang bleibt der Abstand konstant, dann vergrößert er sich – die Warteschlange, in der es langsamer vorangeht, ist die, bei der der Nutzer – und nicht Valve – aus eigener Tasche zahlen muss.\n\nQuelle: 21 Wayback-Machine-Speicherabbilder von store.steampowered.com/stats/support, 2018-02-03 bis 2026-08-10; Extraktion in VALVE_EVIDENCE_PACK/databases/steam_support_stats_history.json. Lesen Sie die Grenzwerte anhand der Zahlen ab: Das Diagramm stellt die niedriger Obergrenze des Bereichs Valve Drucke. Die veröffentlichte Obergrenze ist in beiden Fällen schlechter – die Rückerstattungszeiten lagen zwischen 1,5 Stunden und 1,5 Tagen, die Wiederherstellungszeiten zwischen 7,0 Stunden und 3,6 Tagen. Zwei Erfassungen wurden in einer lokalisierten Ausgabe derselben Valve-Seite archiviert – 2018-11-03 auf Tschechisch, 2020-03-25 auf Französisch – und sind in der Tabelle mit (cs) und (fr) gekennzeichnet; ihre Zahlen erscheinen hier mit übersetzten Einheitenbezeichnungen und den Zahlen in der veröffentlichten Form, während die wörtlichen Quellzeichenfolgen in der Extraktionsdatei beibehalten werden. Jeder Datensatz enthält eine Antwortzeit für beide Warteschlangen, und kein Punkt auf einer der beiden Linien wurde interpoliert. Der einzelne 15-Minuten-Wiederherstellungswert von 2020-10-21 ist im Diagramm markiert und wurde beibehalten: Er erscheint nur in einem Datensatz, und kein anderer Datensatz liegt auch nur annähernd in derselben Größenordnung. Zwischen 2022-12-08 und 2026-02-01 gibt es keine Erfassung; diese 38-monatige Lücke in den Aufzeichnungen ist schattiert, und es wird keine Linie darüber gezogen. Diese Zahlen beschreiben veröffentlichte Antwortzeiten. Sie zeigen nicht, was innerhalb eines Tickets geschieht, und Valve hat keine Mitarbeiterzahlen veröffentlicht, anhand derer man sie einordnen könnte.\n\nJede Aufnahme als Tabelle öffnen\nJede archivierte Aufnahme, wie veröffentlicht\nErfassen\tRückerstattungen / Tag\tAntwort zur Rückerstattung\tErholung / Tag\tMaßnahmen zur Wiederherstellung\n2018-02-03\t98,788\t50,12 Minuten bis 1,52 Stunden\t25,662\t2,51 Stunden bis 1,80 Tage\n2018-05-07\t60,494\t53,83 Minuten bis 1,47 Tage\t24,226\t2,45 Stunden bis 2,22 Tage\n2018-08-02\t69,084\t50,27 Minuten bis 1,59 Stunden\t28,953\t2,44 Stunden bis 22,17 Stunden\n2018-11-03 (cs)\t63,410\t49,28 Minuten bis 1,54 Stunden\t33,910\t2,42 Stunden bis 1,31 Tage\n2019-02-01\t76,305\t50,13 Minuten bis 1,52 Stunden\t35,164\t2,44 Stunden bis 2,04 Tage\n2019-05-18\t78,951\t51,03 Minuten bis 3,12 Stunden\t27,514\t2,46 Stunden bis 20,39 Stunden\n2019-09-07\t78,941\t50,65 Minuten bis 1,66 Stunden\t28,812\t2,42 Stunden bis 13,59 Stunden\n2019-12-13\t69,589\t50,77 Minuten bis 1,55 Stunden\t25,322\t2,45 Stunden bis 1,13 Tage\n2020-03-25 (fr)\t139,278\t49,45 Minuten bis 1,53 Stunden\t32,302\t2,48 Stunden bis 3,62 Tage\n2020-06-26\t278,504\t48,98 Minuten bis 2,29 Stunden\t20,343\t2,39 Stunden bis 6,99 Stunden\n2020-10-21\t107,633\t50,80 Minuten bis 1,54 Stunden\t20,688\t15,33 Minuten bis 8,62 Stunden\n2021-03-20\t158,956\t50,80 Minuten bis 1,64 Stunden\t25,760\t2,34 Stunden bis 11,62 Stunden\n2021-06-26\t547,907\t51,93 Minuten bis 6,73 Stunden\t29,728\t2,40 Stunden bis 15,63 Stunden\n2021-10-10\t170,103\t51,88 Minuten bis 3,25 Stunden\t23,989\t2,39 Stunden bis 13,05 Stunden\n2022-01-31\t354,386\t53,65 Minuten bis 8,09 Stunden\t24,391\t2,42 Stunden bis 15,29 Stunden\n2022-05-09\t172,555\t51,83 Minuten bis 1,65 Stunden\t23,289\t2,41 Stunden bis 16,90 Stunden\n2022-09-05\t153,453\t53,67 Minuten bis 4,15 Stunden\t23,594\t2,45 Stunden bis 1,22 Tage\n2022-12-08\t181,075\t54,83 Minuten bis 6,67 Stunden\t27,111\t2,46 Stunden bis 18,89 Stunden\n2026-02-01\t317,762\t50,30 Minuten bis 1,52 Stunden\t47,197\t10:91 Uhr bis 21:30 Uhr\n2026-05-09\t246,776\t50,12 Minuten bis 1,52 Stunden\t35,264\t5,81 Stunden bis 15,60 Stunden\n2026-08-10\t373,244\t52,05 Minuten bis 2,07 Stunden\t45,319\t8,73 Stunden bis 16,52 Stunden\nWICHTIGSTE BEMERKUNG:\nQuer durch 21 Wayback-Archivierungen Im Zeitraum von 2018-02-03 bis 2026-08-10 lagen die täglichen Rückerstattungsanträge zwischen 60,494 (Mai 2018) bis 547,907 (Juni 2021) — a 9,1× Spread. Der Wert für 2026 beträgt 373,244 (+278% im Vergleich zur Erhebung vom Februar 2018).\nIn diesen neun Jahren lag die veröffentlichte Untergrenze für die Bearbeitungszeit von Erstattungsanträgen stets bei 49–55 Minuten Band: Eine Gesamtbewegung von weniger als sechs Minuten, während sich die dahinterliegende Arbeitslast um den Faktor neun veränderte.\nWenn eine Person jedes Ticket auch nur 5 Sekunden lang lesen würde, würde die Bearbeitung von 373,244 Tickets pro Tag (derzeit) 22 Mitarbeiter, die rund um die Uhr im Einsatz sind allein schon, um sie zu öffnen und zu schließen; in der Hochsaison (547,907, Juni 2021) steigt dieser Wert auf 32.\nWenn die veröffentlichte Bearbeitungszeit die Bearbeitungszeit pro Ticket widerspiegeln würde (~52 Min./Ticket), läge der daraus abgeleitete Personalbedarf in der Größenordnung von 13,500 Agenten bei der aktuellen Menge und ~20,000 bei Spitzenwerten. Es konnte keine Quelle für die Anzahl der Mitarbeiter von Valve gefunden werden; hier wird keine angenommen.\nWas daraus folgt: Das Verhältnis von Bearbeitungsvolumen zu Mitarbeiterzahl lässt sich bei den veröffentlichten Bearbeitungszeiten nicht mit einer manuellen Überprüfung jedes einzelnen Tickets vereinbaren. Die Zahlen deuten auf einen weitgehend automatisierten ersten Durchlauf hin; welcher Anteil einer manuellen Überprüfung unterzogen wird, wird nicht veröffentlicht.\nWarum dies für die Einhaltung der DSGVO wichtig ist\n\nArtikel 22 der DSGVO verbietet eine ausschließlich automatisierte Einzelentscheidung, die erhebliche rechtliche Auswirkungen hat, ohne dass auf Antrag das Recht auf eine Überprüfung durch einen Menschen gewährt wird. Wenn Steam Support-Entscheidungen (Schließung von Tickets, Maßnahmen in Bezug auf Konten, Ablehnung von Datenanfragen) vollständig durch automatisierte Skripte getroffen werden, kann jede solche Entscheidung, die den Nutzer „erheblich betrifft“, gegen Artikel 22 verstoßen.\n\nFahrkarte HT-2YBP-F7JP-D4VB (Abschnitt 18) wurde nach drei Tagen mit einer Standardverweisung abgeschlossen, ohne dass auf die angeführte Rechtsgrundlage eingegangen wurde. Ob eine Person den Fall geprüft hat, lässt sich aus dem Ticket nicht feststellen; diese Frage kann die Aufsichtsbehörde gemäß Artikel 22 und Artikel 15 Absatz 1 Buchstabe h an Valve richten.\n\nQuelle: Wayback-Machine-Snapshots von store.steampowered.com/stats/support (2018-02-03, 2021-06-26, 2026-08-10) – Daten extrahiert in VALVE_EVIDENCE_PACK/databases/steam_support_stats_history.json (21 Snapshots, 2018–2026). Hinweis: Die Reaktionszeit von „~52 min“ ist die Untergrenze für die Kategorie „Rückerstattung“; die Reaktionszeit bei der Kontosicherheit lag in denselben Snapshots zwischen 2,4 und 16,5 Stunden. 2021-06-26 ist der historische Höchstwert (547,907 Rückerstattungsanträge), kein monotoner Mittelwert – das Volumen stieg 2020–2021 um das ~6-Fache an, ging dann teilweise zurück, bevor es sich 2026 auf 373.000 erholte.\nAnhang I – Umfang des Datensatzes · reproduzierbare Zählwerte\nZähle die Datensätze. Überprüfe den Umfang.\nKontext und Quellenbeschränkungen\n\nZählen Sie die Datensätze und überprüfen Sie anschließend die Angaben: Jede der folgenden Zahlen lässt sich aus den veröffentlichten Dateien erneut ableiten.\n\nÜberprüfen Sie die zugrunde liegenden Datensätze, reproduzieren Sie die Zählwerte und unterscheiden Sie Quellzeilen von einzelnen Vorfällen.\n\nDie CSV-Stammdatei enthält 40,448 Zeilen. Davon 36,516 stammen aus dem Discord-AntiScam-Phishing-Feed. Die übrigen 3,932 Die Einträge umfassen GitHub, Reviews, Suchergebnisse, Forenbeiträge und andere Quellen und bieten so einen umfassenden Überblick über gemeldete Community-Themen und Sicherheitsberichte.\n\nIn dieser CSV-Datei sind 1,690 Zeilen unter der Sammelbezeichnung „Unpatched Security Exploit“ zusammengefasst, die historische Benutzerprobleme und Offenlegungen von Sicherheitslücken darstellen. Um diese Meldungen nachzuverfolgen, müssen die spezifische Build-Zeitleiste und die öffentliche Patch-Historie jedes Threads überprüft werden.\n\nDas durchsuchbare Archiv mit 16,319 Datensätzen ist eine eigenständige, kuratierte Version mit einem eigenen Manifest, die für die gezielte lokale Untersuchung bestimmter Nutzerbeanstandungen und Vorfallmeldungen konzipiert ist.\n\nUm einen zuverlässigen Prüfpfad zu erstellen, muss jeder vom Benutzer gemeldete Datensatz anhand dokumentierter Build-Zeitpläne und historischer Patch-Protokolle überprüft werden.\n\nDie separaten Bestandsdatensätze von Teil II 231,829 eindeutige Angebots-IDs, darunter 33,509 in der Kategorie „automatische Registrierung“ und 198,320, die als nicht verifizierte Übertragungen gekennzeichnet sind. Der SHA-256-Hash der Eingabedatei stimmt mit dem gespeicherten Messwert überein. Diese Zahlen beschreiben Einstellversuche und beobachtete Transfers und nicht die endgültigen Transaktionswerte oder verifizierten Diebstahlsummen, was die Notwendigkeit von Primärdaten der Plattformen zur Ermittlung der genauen wirtschaftlichen Auswirkungen unterstreicht. Auflistung von Maßen und Hashwerten ↗\n\nCSV beherrschen ↗ · Durchsuchbares Archivverzeichnis ↗ · Quelldatensätze prüfen ↗\n\nAnhang J – Über diese Untersuchung\nValve veröffentlicht keine Vollstreckungsunterlagen. Wir haben eins gebaut.\n\nUnabhängig. Nicht kommerziell. Ausschließlich auf der Grundlage öffentlicher Daten erstellt. Den Aufsichtsbehörden vorgelegt.\n\n88.97%Automatisierungsflotte bleibt unberührt – keinerlei Verbot\n67.77%von 51,732 verurteilten Betrügern kommen ungestraft davon\n$26.8M+Mindestausgaben im Geschäft durch die nicht-begrenzte Flotte\n3.6%Glücksspiel-Domains, die vom Linkfilter von Valve blockiert wurden\n8 Jahreder dokumentierten Sicherheitsvorfälle\n\nWas das ist. Ein forensisches Dossier zur Steam-Plattform der Valve Corporation – ihre Durchsetzungsbilanz, ihre „Card-Farming“-Ökonomie, ihr rechtlicher Rahmen sowie die Authentifizierungsinfrastruktur, die Glücksspielanbieter über das eigene OpenID-Relay von Steam nutzen. Jede Zahl lässt sich anhand von zwei Quellen nachvollziehen: der eigenen öffentlichen API von Valve und den im Rahmen dieser Untersuchung veröffentlichten Datensätzen.\n\nFür wen ist es gedacht? Zuständige Aufsichtsbehörden für Valve – die DSGVO-Aufsichtsbehörde der Niederlande, FinCEN, die SEC, der DSA-Koordinator für digitale Dienste, UOKiK sowie alle Strafverfolgungsbehörden, die mit Steam verbundene Finanzströme untersuchen. Ebenso für Journalisten, Forscher und alle Nutzer, denen eine dauerhafte Kontosperrung auferlegt, eine Rückerstattung verweigert oder Inventar gestohlen wurde und denen mitgeteilt wurde, dass kein Rechtsmittel eingelegt werden kann.\n\nDie einzige Forderung. Valve speichert diese Daten in voller Genauigkeit – einschließlich der Sperrgründe, des vollständigen ID-Raums und in Echtzeit. Es kann jede Abfrage in dieser Akte innerhalb von Sekunden ausführen und hat sich entschieden, nichts davon zu veröffentlichen. Die Frage für jede zuständige Behörde ist einfach: Warum nicht?\n\nWas die Autoren nicht behaupten. Während dieser Arbeit wurde auf keiner Drittanbieter-Plattform eine Anmeldung bei Steam abgeschlossen. Eine bereitgestellte OpenID-URL legt die Anforderungsparameter fest, nicht jedoch eine abgeschlossene Anmeldung. Eine separate registrierbare Domain ist für sich genommen kein Beweis für eine Umgehung. Registrierungsdaten stellen Untergrenzen dafür dar, wann ein Host erstmals in einer OpenID-Anfrage aufgetaucht sein könnte; sie belegen keine kontinuierliche Nutzung. Die Autoren machen keine Aussagen darüber, was Valve wusste oder beabsichtigte: Jede Aussage über Valve ist an ein datiertes öffentliches Dokument oder eine datierte Beobachtung gebunden. Wo eine Behauptung nicht durch ein Quelldokument belegt werden konnte, wurde sie entfernt.\n\nWer wir sind\n\nPhishDestroy — unabhängige Ermittler. Keine Verbindung zur Valve Corporation oder zu einer der hier genannten Plattformen. Ein Steam-Konto wurde ausschließlich dazu verwendet, den DSGVO-Antrag in Abschnitt 18 zu dokumentieren.\n\nRechtlicher Hinweis\n\nNichtkommerzielle, dezentrale Recherche im öffentlichen Interesse. Alle Daten werden „wie besehen“ und ohne jegliche Gewähr bereitgestellt. Diese Veröffentlichung stellt keine gerichtliche Feststellung dar.\n\nGEMEINWARE\nLizenzierung\n\nAlle Rechte werden der Menschheit übertragen. Vervielfältigung, Bearbeitung, Veröffentlichung – keine Nennung der Quelle erforderlich. Zugriff aus OFAC-Regionen: untersagt. Vollständige Lizenz und Haftungsausschluss →",
        "headings": [
          {
            "level": 2,
            "id": "briefing-heading",
            "text": "Die Regel. Der Rekord. Die offenen Fragen."
          },
          {
            "level": 2,
            "id": null,
            "text": "Offener Brief an die Glücksspielkommission des Bundesstaates Washington"
          },
          {
            "level": 3,
            "id": "wsgc-public-address-title",
            "text": "Aus zehn Tagen wurden zehn Jahre.Öffnen Sie den Datensatz erneut."
          },
          {
            "level": 2,
            "id": null,
            "text": "Die Website ist gesperrt. Die Anmeldeseite ist es nicht."
          },
          {
            "level": 3,
            "id": null,
            "text": "Abbildung 3.1 – Die beiden Routen, grafisch dargestellt."
          },
          {
            "level": 3,
            "id": null,
            "text": "Die „Big Picture“-Falle: Der Link-Filter ist bloßes Compliance-Theater, kein Schutzschild"
          },
          {
            "level": 3,
            "id": null,
            "text": "Eine gesperrte Hauptdomain in Verbindung mit einem nicht gesperrten Auth-Host lässt die Anmelderoute offen – und diese bleibt über Jahre hinweg offen."
          },
          {
            "level": 3,
            "id": null,
            "text": "Hintergrund: Was Steam ist und warum es hier von Bedeutung ist"
          },
          {
            "level": 3,
            "id": null,
            "text": "Was Valve getan hat: Die Domain-Sperre"
          },
          {
            "level": 3,
            "id": null,
            "text": "Was ist eine Proxy-Domain?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Der kritische Punkt: Der Auth-Host wird bei jeder Anfrage an Steam gesendet"
          },
          {
            "level": 3,
            "id": null,
            "text": "Was dies beweist"
          },
          {
            "level": 3,
            "id": null,
            "text": "In Steam ist die Liste von Valve die einzige Liste."
          },
          {
            "level": 3,
            "id": null,
            "text": "Umgehung des Link-Filterschutzes"
          },
          {
            "level": 3,
            "id": null,
            "text": "Der Webbrowser „Big Picture“ gibt Login-Cookies preis und legt sensible Informationen offen (kann zur Übernahme des Kontos führen)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Was das für einen Minderjährigen bedeutet, auf dessen Computer ein Antivirenprogramm installiert ist"
          },
          {
            "level": 3,
            "id": null,
            "text": "Das Alter der Domain.Das Datum der Beobachtung."
          },
          {
            "level": 2,
            "id": null,
            "text": "Ein Endpunkt wurde geschlossen. Bei der öffentlichen Rückverfolgung ging ein Schlüssel verloren."
          },
          {
            "level": 3,
            "id": null,
            "text": "Die Zeit vor dem Stromausfall"
          },
          {
            "level": 3,
            "id": null,
            "text": "Nach der Änderung"
          },
          {
            "level": 2,
            "id": null,
            "text": "Eine Sitzung. Mehr Zugriff, als der Benutzer sieht."
          },
          {
            "level": 3,
            "id": null,
            "text": "1. Unzureichende mehrstufige Authentifizierung"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. Fehlen des Prinzips der geringsten Berechtigungen"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. Fehlerhafte Sitzungsverwaltung"
          },
          {
            "level": 3,
            "id": null,
            "text": "4. Eine Sperrung von Auth-Hosts auf Domain-Ebene war technisch machbar"
          },
          {
            "level": 3,
            "id": "integration-paradox-title",
            "text": "Valve wird jeden Tag nach diesen Regeln kompiliert. Hier ist die Kompilierung nach diesen Regeln jedoch fehlgeschlagen."
          },
          {
            "level": 4,
            "id": null,
            "text": "Fein abgestufte Gültigkeitsbereiche bei GitHub im Vergleich zur Web-API Valve Steam"
          },
          {
            "level": 2,
            "id": null,
            "text": "Interaktiver Exploit- und Hijack-Simulator"
          },
          {
            "level": 2,
            "id": null,
            "text": "Die Endpunkte, die hinter der Sequenz stehen."
          },
          {
            "level": 2,
            "id": null,
            "text": "Ein angekreuztes Kästchen. Wessen Handlung?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Wie Valve schließlich die „Handelssubstitution“ neutralisierte – und warum es sieben Jahre voller Umgehungslösungen dauerte"
          },
          {
            "level": 4,
            "id": null,
            "text": "Abklingzeit für Avatar und Namen (Februar 2024)"
          },
          {
            "level": 4,
            "id": null,
            "text": "7-Tage-CS2-Handelsumkehr (Juli 2025)"
          },
          {
            "level": 4,
            "id": null,
            "text": "Obligatorischer mobiler Push für die API (Dezember 2023)"
          },
          {
            "level": 4,
            "id": null,
            "text": "Banner mit Kontodauer und Namen (2022–2024)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Ihr Regelwerk. Die aufgezeichneten Plattformen."
          },
          {
            "level": 3,
            "id": "enforcement-focus-title",
            "text": "Ein Regelwerk. Ungleiche Durchsetzung."
          },
          {
            "level": 4,
            "id": null,
            "text": "Automatisierung"
          },
          {
            "level": 4,
            "id": null,
            "text": "Kommerzielle Nutzung"
          },
          {
            "level": 4,
            "id": null,
            "text": "VPN & Standortverschleierung"
          },
          {
            "level": 4,
            "id": null,
            "text": "Link-Verschleierung"
          },
          {
            "level": 4,
            "id": null,
            "text": "Wer überprüft die Entscheidung, wenn die Fälligkeitsstelle den Fall abschließt?"
          },
          {
            "level": 2,
            "id": null,
            "text": "Eine API zur Automatisierung. Eine Regel gegen Automatisierung."
          },
          {
            "level": 3,
            "id": null,
            "text": "Der Irrtum des „Spieleentwicklers“"
          },
          {
            "level": 4,
            "id": null,
            "text": "Der Widerspruch der Automatisierung"
          },
          {
            "level": 4,
            "id": null,
            "text": "Eine serverseitige Position im Handelsablauf"
          },
          {
            "level": 2,
            "id": null,
            "text": "Zehn Tage wurden gefordert. Zehn Jahre müssen abgerechnet werden."
          },
          {
            "level": 3,
            "id": "letter-company",
            "text": "VALVE CORPORATION"
          },
          {
            "level": 3,
            "id": null,
            "text": "Zehn Tage.Und was dann?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Folgen Sie dem angegebenen Rückgaberechner."
          },
          {
            "level": 3,
            "id": "washington-record-heading",
            "text": "Zwei Fristen. Ein ungeklärter Durchsetzungsmaßstab."
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve räumt Glücksspielseiten eine Frist von 10 Tagen ein"
          },
          {
            "level": 4,
            "id": null,
            "text": "Washington drängt Valve"
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve weist den Vorwurf zurück"
          },
          {
            "level": 4,
            "id": null,
            "text": "Die im September 2026 beobachteten Routen"
          },
          {
            "level": 4,
            "id": null,
            "text": "Achtzehn Monate nach der Antwort von Valve bezeichnete die Aufsichtsbehörde dies immer noch als Absichtserklärung."
          },
          {
            "level": 3,
            "id": null,
            "text": "Das Jahrzehnt der 10-Tage-Frist: Forensische Überlebensprüfung der 23 genannten Standorte"
          },
          {
            "level": 4,
            "id": null,
            "text": "Von 10-Tage-Warnungen bis hin zu Offshore-Konzernen: Der Umsatz in Milliardenhöhe"
          },
          {
            "level": 2,
            "id": null,
            "text": "Der Hostname ist bereits in der Anfrage enthalten."
          },
          {
            "level": 3,
            "id": null,
            "text": "Dokumentierte und gemeldete Präzedenzfälle"
          },
          {
            "level": 3,
            "id": null,
            "text": "Was ein Eintragungsdatum aussagt und was nicht"
          },
          {
            "level": 3,
            "id": null,
            "text": "Vergleichsprüfung: API-Konformitätsstandards"
          },
          {
            "level": 2,
            "id": "market-thesis-heading",
            "text": "Die Preisdifferenz zwischen „Off-0“ und „0“"
          },
          {
            "level": 2,
            "id": null,
            "text": "Die Preisdifferenz ist messbar."
          },
          {
            "level": 3,
            "id": null,
            "text": "Was die Dollarbeträge aussagen"
          },
          {
            "level": 3,
            "id": null,
            "text": "Viele Veranstaltungsorte geben einen höheren Dollarwert als Steam an."
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam liegt bei der Anzahl der Angebote weiterhin an der Spitze."
          },
          {
            "level": 3,
            "id": null,
            "text": "Das kommerzielle Ökosystem liegt auf der Hand."
          },
          {
            "level": 2,
            "id": null,
            "text": "Wer kann die Sicherheitsvorkehrungen zurücksetzen?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ein Wiederherstellungsticket, durch das die Sicherheit des Kontos außer Kraft gesetzt wurde, sowie ein gemeldeter Verlust in Höhe von $10,000"
          },
          {
            "level": 3,
            "id": null,
            "text": "Über das Inventar hinaus."
          },
          {
            "level": 3,
            "id": "theft-ledger-title",
            "text": "Valve öffnete die Tür zweimal im Abstand von dreiunddreißig Monaten. Sie schloss sich nie."
          },
          {
            "level": 4,
            "id": null,
            "text": "Was die Bilanz aussagt, was kein Einzelfall tut."
          },
          {
            "level": 3,
            "id": null,
            "text": "Vertraulichkeit muss mit technischer Rechenschaftspflicht einhergehen."
          },
          {
            "level": 2,
            "id": null,
            "text": "Folgen Sie dem Geld. Trennen Sie die Transaktionen."
          },
          {
            "level": 3,
            "id": null,
            "text": "Wo das Geld tatsächlich fließt."
          },
          {
            "level": 3,
            "id": null,
            "text": "Ordnen Sie zunächst die Tätigkeit und anschließend die Verpflichtung zu."
          },
          {
            "level": 3,
            "id": null,
            "text": "Erlöse, Wissen und Unterstützung nachverfolgen."
          },
          {
            "level": 2,
            "id": null,
            "text": "Das Gesetz über digitale Dienste: Wissen dokumentieren"
          },
          {
            "level": 3,
            "id": null,
            "text": "Eine zehntägige Frist."
          },
          {
            "level": 3,
            "id": null,
            "text": "Das DSA-Zeitfenster."
          },
          {
            "level": 3,
            "id": null,
            "text": "Für die Dauer ist ein Nachverfolgungspfad erforderlich."
          },
          {
            "level": 3,
            "id": null,
            "text": "des weltweiten Jahresumsatzes"
          },
          {
            "level": 2,
            "id": null,
            "text": "Minderjährige: Eine Anmeldung mit „0“ gilt nicht als Altersüberprüfung."
          },
          {
            "level": 3,
            "id": null,
            "text": "Bestimmen Sie den Operator und die Daten."
          },
          {
            "level": 3,
            "id": null,
            "text": "Erfassen Sie den Ablauf vom Einloggen bis zur Einzahlung."
          },
          {
            "level": 2,
            "id": null,
            "text": "Die Anfrage. Die Antwort. Der fehlende Vergleich."
          },
          {
            "level": 3,
            "id": null,
            "text": "Die Unterlagen sind vorhanden; die betroffene Person hat sie nicht erhalten."
          },
          {
            "level": 2,
            "id": null,
            "text": "Die Nutzungsvereinbarung im Widerspruch zur eigenen Architektur der Plattform"
          },
          {
            "level": 3,
            "id": null,
            "text": "Die Markt-Obergrenze und das Verbot der gewerblichen Nutzung"
          },
          {
            "level": 3,
            "id": null,
            "text": "Die Sicherheitslücke beim API-Schlüssel ist eher ein Problem des Plattformdesigns als auf Nachlässigkeit der Nutzer zurückzuführen"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve erhält bei jeder Anmeldung den Authentifizierungs-Hostnamen"
          },
          {
            "level": 3,
            "id": null,
            "text": "Das Muster in den archivierten Beschwerden"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ein Gericht, das diese Aktenlage prüft, würde die SSA nicht isoliert betrachten."
          },
          {
            "level": 2,
            "id": null,
            "text": "Die Ergebnisse. Die Unterlagen, um die wir bitten."
          },
          {
            "level": 2,
            "id": null,
            "text": "Beweismemorandum – von Quelle 1 bereitgestelltes Material"
          },
          {
            "level": 2,
            "id": null,
            "text": "Die Schwärzung in der bereitgestellten PDF-Datei ist rein kosmetischer Natur: Der verdeckte Text lässt sich weiterhin extrahieren."
          },
          {
            "level": 2,
            "id": null,
            "text": "Unterlagen zu Unterhaltsangelegenheiten und Rechtskorrespondenz"
          },
          {
            "level": 2,
            "id": null,
            "text": "Ausgewählte Primärquellen"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-01",
            "text": "Hardware-Schlüssel, angefordert im Jahr 2016"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-02",
            "text": "Absturzberichte ohne wirksame Opt-out-Möglichkeit"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-03",
            "text": "Missbrauch von Auth-Tickets an Valve gemeldet"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-01",
            "text": "44 umstrittene Marktkäufe"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-02",
            "text": "Eine dauerhafte Sperre und ausgeschöpfte Rechtsmittel"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-03",
            "text": "Ein Neustart der Erholung und ein gemeldeter Verlust von $10,000"
          },
          {
            "level": 2,
            "id": null,
            "text": "ArchiSteamFarm und die Automatisierungsklausel"
          },
          {
            "level": 2,
            "id": null,
            "text": "Rules ledger: clauses against recorded platforms"
          },
          {
            "level": 3,
            "id": "ledger-title",
            "text": "Kommerzielle Nutzung und Abrechnung über das Konto"
          },
          {
            "level": 3,
            "id": "lw-register-title",
            "text": "Plattformregister 175"
          },
          {
            "level": 4,
            "id": null,
            "text": "Beweislast"
          },
          {
            "level": 4,
            "id": null,
            "text": "Was ein „tagged record“ ist und was nicht"
          },
          {
            "level": 2,
            "id": null,
            "text": "DSAR-Leitfaden: Anforderung der Nachweise"
          },
          {
            "level": 3,
            "id": null,
            "text": "Bewahre deine Zeitleiste auf."
          },
          {
            "level": 3,
            "id": null,
            "text": "Fordern Sie Ihre gespeicherten Daten an."
          },
          {
            "level": 3,
            "id": null,
            "text": "Bewahren Sie den Lieferschein auf."
          },
          {
            "level": 3,
            "id": null,
            "text": "Vergleiche die Antwort."
          },
          {
            "level": 3,
            "id": null,
            "text": "Kontosicherheit und Zugriffsprotokolle"
          },
          {
            "level": 3,
            "id": null,
            "text": "Eine Unstimmigkeit ist ein Anhaltspunkt für weitere Untersuchungen."
          },
          {
            "level": 2,
            "id": null,
            "text": "Support-Umfang. Veröffentlichte Reaktionszeiten."
          },
          {
            "level": 3,
            "id": null,
            "text": "Zwei Warteschlangen an einem Support-Schalter, wie aus 21 archivierten Screenshots hervorgeht."
          },
          {
            "level": 2,
            "id": null,
            "text": "Zähle die Datensätze. Überprüfe den Umfang."
          },
          {
            "level": 2,
            "id": null,
            "text": "Valve veröffentlicht keine Vollstreckungsunterlagen.\nWir haben eins gebaut."
          }
        ],
        "links": [
          "https://dotesports.com/counter-strike/news/csgo-lounge-billion-bets-3896",
          "https://store.steampowered.com/agreement/?l=english",
          "http://web.archive.org/web/20260921022032/https://store.steampowered.com/agreement/?l=english",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-all-results.json",
          "https://blog.counter-strike.net/expresstrade/",
          "http://web.archive.org/web/20260307161538/https://blog.counter-strike.net/expresstrade/",
          "https://wsgc.wa.gov/news/2016/washington-state-gambling-commission-orders-valve-stop-skins-gambling",
          "http://web.archive.org/web/20260520012601/https://wsgc.wa.gov/news/2016/washington-state-gambling-commission-orders-valve-stop-skins-gambling",
          "https://fr.scribd.com/document/328063293/Valve-s-Oct-18th-response-to-Washington-State-Gambling-Commission-s-cease-and-desist",
          "https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921021947/https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921022628/https://steamcommunity.com/linkfilter/?url=https:%2F%2Frollbit.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rbsnin.com.20260921T021120Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rollbit.com.json",
          "http://web.archive.org/web/20260921022740/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fskin.club",
          "http://web.archive.org/web/20260921022842/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fsc-auth.net",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skin.club.json",
          "http://web.archive.org/web/20260921022603/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fhowl.gg",
          "http://web.archive.org/web/20260921022636/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fhowl.uno",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/howl.gg.json",
          "http://web.archive.org/web/20260921022840/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fduelbits.com",
          "http://web.archive.org/web/20260921022901/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fswitchflips.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/duelbits.com.json",
          "http://web.archive.org/web/20260921022758/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgofast.com",
          "http://web.archive.org/web/20260921022847/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fauthtofast.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgofast.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/farmskins.com.20260921T025840Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/steam.kobal.cc.20260921T025844Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/farmskins.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cobaltlab.tech.20260921T041604Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cobaltauth.com.20260921T041608Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/cobaltlab.tech.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgo.net.20260921T041619Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cn2.easylot.net.20260921T041623Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgo.net.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/ggdrop.com.20260921T041637Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/ggauth.com.20260921T041641Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/ggdrop.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rustchance.com.20260921T041703Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/hgfuihd.com.20260921T041706Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rustchance.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skin.fans.20260921T041710Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.skinfans.com.20260921T041713Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skin.fans.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinport.com.20260921T041724Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinport.app.20260921T041728Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skinport.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skins.cash.20260921T041731Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinscash.live.20260921T041735Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skins.cash.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2hunt.com.20260921T041739Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rstspcl.com.20260921T041742Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tf2hunt.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgogem.com.20260922T192355Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/api.csgem.com.20260922T192358Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-2026-09-22.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/gamdom.com.20260922T192326Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/login.gambldom.com.20260922T192330Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/12cs.fail.20260922T192347Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/fail.games.20260922T192351Z.html",
          "http://web.archive.org/web/20260921022953/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgoempire.com",
          "http://web.archive.org/web/20260921022947/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgoempirelogin4.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgoempire.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cs.money.20260921T021131Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.dota.trade.20260921T021134Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/cs.money.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csfloat.com.20260921T041612Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgofloat.com.20260921T041615Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csfloat.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/g4skins.com.20260921T041630Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.g4s.to.20260921T041634Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/g4skins.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/juice.gg.20260921T041644Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/letmeinjuice.com.20260921T041648Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/juice.gg.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/market.csgo.com.20260921T041652Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2.net.20260921T041655Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/market.csgo.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rust.tm.20260921T041659Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rust.tm.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgolounge.com.20260922T192333Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2.net.20260922T192340Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2lounge.com.20260922T192337Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinbaron.de.20260921T041717Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinbaron.com.20260921T041721Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skinbaron.de.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2royal.com.20260921T041746Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2auth.com.20260921T041750Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tf2royal.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tradeit.gg.20260921T041753Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/connect-tradeit.com.20260921T041757Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tradeit.gg.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/upgrader.pro.20260921T041801Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/upgauth.space.20260921T041804Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/upgrader.pro.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-recheck-2026-09-21.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/domain-registration.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wayback-snapshots.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-2026-09-22c.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/master_registry.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/longitudinal-steam-phishing-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-steam-phishing-100.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-coverage-2026-09-22.json",
          "https://blog.csfloat.com/how-floatdb-tracks-items/",
          "http://web.archive.org/web/20260921022415/https://blog.csfloat.com/how-floatdb-tracks-items/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/platform-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/platforms-removed.json",
          "https://hackerone.com/reports/291750",
          "http://web.archive.org/web/20251116185046/https://hackerone.com/reports/291750",
          "https://hackerone.com/reports/1079561",
          "http://web.archive.org/web/20260924181830/https://hackerone.com/reports/1079561",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/hackerone-reports.json",
          "https://phishdestroy.io/steam_dossier/de/steam_enforcement_evidence.html#support-records",
          "https://www.darknavy.org/blog/exploiting_steam_usual_and_unusual_ways_in_the_cef_framework/",
          "https://steamcommunity.com/groups/SteamClientBeta/discussions/0/3365901765276206401/",
          "http://web.archive.org/web/20250804051514/https://steamcommunity.com/groups/SteamClientBeta/discussions/0/3365901765276206401/",
          "https://www.chromium.org/developers/design-documents/safebrowsing/",
          "http://web.archive.org/web/20260821101616/https://www.chromium.org/developers/design-documents/safebrowsing/",
          "https://www.chromium.org/developers/how-tos/api-keys/",
          "http://web.archive.org/web/20260830122831/https://www.chromium.org/developers/how-tos/api-keys/",
          "https://github.com/Homebrew/homebrew-cask/issues/193814",
          "https://testsafebrowsing.appspot.com/",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/domain-registration.json",
          "https://phishdestroy.io/steam_dossier/de/AUTH_AUDIT.md",
          "https://datatracker.ietf.org/doc/rfc6749/",
          "https://docs.cloud.google.com/docs/authentication/api-keys",
          "https://listings.pcisecuritystandards.org/pdfs/PCI_DSS_Resource_Guide_(003).pdf",
          "https://developer.apple.com/news/?id=02202019a",
          "http://web.archive.org/web/20250506070026/https://developer.apple.com/news/?id=02202019a",
          "https://dev.twitch.tv/docs/authentication/validate-tokens/",
          "https://discuss.dev.twitch.com/t/legacy-twitch-api-v5-i-e-kraken-shutdown-reminder-february-28-2022/36589",
          "http://web.archive.org/web/20250127085635/https://discuss.dev.twitch.com/t/legacy-twitch-api-v5-i-e-kraken-shutdown-reminder-february-28-2022/36589",
          "https://store.steampowered.com/news/posts/?enddate=1788390000",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/4123547285514022851",
          "https://skinvault.gg/blog/cs2-trade-protection-explained/",
          "https://csmarketcap.com/blog/market-insights/from-boom-to-bust-cs2s-trade-protection-impact",
          "https://skin.land/blog/steam-changes-cs2-trade-ban-logic-timing/",
          "https://help.steampowered.com/faqs/view/3041-A87A-E5F6-B6AC",
          "https://steamcommunity.com/ogg/593110/announcements/detail/533224478739530146",
          "https://steamcommunity.com/games/CSGO/announcements/detail/4447966961421256740",
          "https://steamcommunity.com/sharedfiles/filedetails/?id=2926756889",
          "https://steamcommunity.com/dev/apikey",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3734103130194459461",
          "https://steamcommunity.com/discussions/forum/1/3807266184852932971/",
          "https://help.steampowered.com/faqs/view/225C-C51E-B8F0-55B2",
          "https://store.steampowered.com/news/group/4/view/3314112260640237775",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/issues/325",
          "https://blog.dota2.com/2020/05/trading-cooldown/",
          "https://blog.counter-strike.net/index.php/2018/03/20308/",
          "http://web.archive.org/web/20250226114333/https://blog.counter-strike.net/index.php/2018/03/20308/",
          "https://phishdestroy.io/steam_dossier/de/steam_evidence_archive.html",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/493839547938902179",
          "https://store.steampowered.com/online_conduct",
          "http://web.archive.org/web/20260921022120/https://store.steampowered.com/online_conduct",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260918014700/https://store.steampowered.com/subscriber_agreement/",
          "https://steamcommunity.com/dev/apiterms",
          "http://web.archive.org/web/20260921022210/https://steamcommunity.com/dev/apiterms",
          "https://help.steampowered.com/en/faqs/view/628C-E332-BD8C-4D36",
          "https://phishdestroy.io/steam_dossier/de/social_graph.html",
          "https://phishdestroy.io/steam_dossier/de/security_timeline.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wsgc-skins-gambling-briefing-2018.pdf",
          "https://wsgc.wa.gov/sites/default/files/2023-10/Skins%20Gambling.pdf",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wsgc-briefing-manifest.json",
          "https://x.com/csgobig",
          "https://www.facebook.com/csgobigofficial/",
          "https://500.casino/",
          "https://csgolounge.com/",
          "https://csgocasino.gg/",
          "https://x.com/CSGOatsecom",
          "https://x.com/CSGOSweep/status/937420902538543106",
          "https://x.com/Wild",
          "https://x.com/csgopot",
          "https://x.com/csgodiamondscom",
          "https://www.ftc.gov/legal-library/browse/cases-proceedings/162-3184-csgo-lotto-matter",
          "https://x.com/CSGODouble",
          "https://x.com/csgo_massive",
          "https://www.facebook.com/csgostrongfree/",
          "https://www.facebook.com/CSNCOM/",
          "https://www.gamblingcommission.gov.uk/report/young-people-and-gambling",
          "https://www.aph.gov.au/Parliamentary_Business/Committees/Senate/Environment_and_Communications/Gamingmicro-transactions",
          "https://phishdestroy.io/steam_dossier/de/elite_skins.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/csfloat-catalogue.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/skinport-floor-over-cap.json",
          "https://pricempire.com/cs2-marketplaces",
          "http://web.archive.org/web/20260921022459/https://pricempire.com/cs2-marketplaces",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/priceempire-marketplaces.json",
          "https://www.steamanalyst.com/marketplace",
          "http://web.archive.org/web/20260719014552/https://www.steamanalyst.com/marketplace",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-atlas.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json",
          "https://phishdestroy.io/steam_dossier/de/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/de/steam_enforcement_evidence.html#case-support-recovery",
          "https://top10.owasp.org/2025/A01_2025-Broken_Access_Control/",
          "http://web.archive.org/web/20260920212535/https://top10.owasp.org/2025/A01_2025-Broken_Access_Control/",
          "https://store.steampowered.com/privacy_agreement/",
          "http://web.archive.org/web/20260921021648/https://store.steampowered.com/privacy_agreement/",
          "https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "http://web.archive.org/web/20250818113925/https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "https://www.dexerto.com/counter-strike-2/valve-saves-hacked-cs2-player-threatened-with-ransom-over-300000-of-rare-stickers-3283135/",
          "https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "http://web.archive.org/web/20220702042821/https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "https://www.kaspersky.com/blog/cs-go-two-million-usd-inventory-hack/44697/",
          "https://esportfire.com/article/the-2-million-usd-csgo-hack-22062022",
          "http://web.archive.org/web/20260515110250/https://esportfire.com/article/the-2-million-usd-csgo-hack-22062022",
          "https://esportsbetting.com/valve-deletes-130000-stolen-dragon-lore/",
          "https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "http://web.archive.org/web/20251115173120/https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "https://vkplay.ru/media/news/bloger-rasskazal-kak-podderzhka-steam-vorovala-akkaunty-igrokov/",
          "https://lis-skins.com/ru/blog/krupneisaia-mosenniceskaia-sxema-v-istorii-steam/",
          "https://escorenews.com/ru/csgo/news/44056-sotrudniki-podderjki-steam-zanimalis-krajey-skinov-s-akkauntov-za-god-oni-zarabotali-svyshe-300-tysyach-dollarov",
          "https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "http://web.archive.org/web/20250805141942/https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/outsourcing-archive-records.json",
          "https://community.skin.club/en/news/collector-has-steam-inventory-returned-after-bold-hack",
          "https://esportfire.com/article/300k-scam-full-katowice-2014-holo-collection-hacked",
          "http://web.archive.org/web/20251217072445/https://esportfire.com/article/300k-scam-full-katowice-2014-holo-collection-hacked",
          "https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng",
          "http://web.archive.org/web/20260920024236/https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng",
          "https://ag.ny.gov/press-release/2026/attorney-general-james-sues-game-developer-promoting-illegal-gambling-through",
          "http://web.archive.org/web/20260901015430/https://ag.ny.gov/press-release/2026/attorney-general-james-sues-game-developer-promoting-illegal-gambling-through",
          "https://www.fincen.gov/sites/default/files/2019-05/FinCEN%20CVC%20Guidance%20FINAL.pdf",
          "http://web.archive.org/web/20250711185007/https://www.fincen.gov/sites/default/files/2019-05/FinCEN%20CVC%20Guidance%20FINAL.pdf",
          "https://eur-lex.europa.eu/legal-content/EN/LSU/?uri=CELEX:32018L1673",
          "https://eur-lex.europa.eu/eli/dir/2024/1640/oj/eng",
          "http://web.archive.org/web/20260830153004/https://eur-lex.europa.eu/eli/dir/2024/1640/oj/eng",
          "https://eur-lex.europa.eu/eli/reg/2022/2065/oj/eng",
          "http://web.archive.org/web/20260920080125/https://eur-lex.europa.eu/eli/reg/2022/2065/oj/eng",
          "https://phishdestroy.io/steam_dossier/de/legal_analysis.html",
          "https://partner.steamgames.com/doc/features/auth#website",
          "http://web.archive.org/web/20260921022335/https://partner.steamgames.com/doc/features/auth",
          "https://www.ftc.gov/legal-library/browse/rules/childrens-online-privacy-protection-rule-coppa",
          "http://web.archive.org/web/20260921070051/https://www.ftc.gov/legal-library/browse/rules/childrens-online-privacy-protection-rule-coppa",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/gdpr-ticket-1.png",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/screenshot-manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/gdpr-ticket-2.png",
          "https://datenschutz.hamburg.de/beschwerde",
          "https://edpb.europa.eu/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/regulatory-review/disclosure-audit.json",
          "https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "http://web.archive.org/web/20260821155801/https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "https://phishdestroy.io/steam_dossier/de/index#exhibit-gallery-section",
          "https://github.com/ValveSoftware/steam-for-linux/issues/4521",
          "https://phishdestroy.io/steam_dossier/de/steam_evidence_archive.html?source=GitHub&record=484",
          "https://github.com/ValveSoftware/steam-for-linux/issues/6459",
          "http://web.archive.org/web/20260419051343/https://github.com/ValveSoftware/steam-for-linux/issues/6459",
          "https://phishdestroy.io/steam_dossier/de/steam_evidence_archive.html?source=GitHub&record=467",
          "https://github.com/ValveSoftware/Source-1-Games/issues/3857",
          "https://phishdestroy.io/steam_dossier/de/steam_evidence_archive.html?source=GitHub&record=768",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "http://web.archive.org/web/20250320082450/https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://phishdestroy.io/steam_dossier/de/steam_evidence_archive.html?source=Reddit&record=4533",
          "https://www.reddit.com/r/ohnePixel/comments/1hahqx2/permanently_banned_steam_account_without_a_clear/",
          "https://phishdestroy.io/steam_dossier/de/steam_evidence_archive.html?source=Reddit&record=4766",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://phishdestroy.io/steam_dossier/de/steam_evidence_archive.html?source=Reddit&record=4592",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/selected-evidence-records.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive_manifest.json",
          "https://phishdestroy.io/steam_dossier/de/card_economy.html",
          "https://github.com/JustArchiNET/ArchiSteamFarm/wiki/FAQ",
          "https://phishdestroy.io/steam_dossier/de/card_economy.html#scale",
          "https://phishdestroy.io/steam_dossier/de/card_economy.html#licence",
          "https://phishdestroy.io/steam_dossier/de/enforcement_audit.html",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "http://web.archive.org/web/20260924181709/https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://rdap.verisign.com/com/v1/domain/csgoempire.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoempire.com",
          "https://rdap.verisign.com/com/v1/domain/csgoempirelogin4.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/csgoempire.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustreaper.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustreaper.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/rustreaper.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustly.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustly.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/rustly.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgofast.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgofast.com",
          "https://rdap.verisign.com/com/v1/domain/authtofast.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/csgofast.com.json",
          "https://rdap.verisign.com/com/v1/domain/duelbits.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fduelbits.com",
          "https://rdap.verisign.com/com/v1/domain/switchflips.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/duelbits.com.json",
          "https://rdap.verisign.com/com/v1/domain/farmskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffarmskins.com",
          "https://tld-rdap.verisign.com/cc/v1/domain/kobal.cc",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/farmskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoluck.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoluck.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/csgoluck.com.json",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/domain-registry/insane.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Finsane.gg",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/insane.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs2skin.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs2skin.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/cs2skin.com.json",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/domain-registry/juice.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fjuice.gg",
          "https://rdap.verisign.com/com/v1/domain/letmeinjuice.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/juice.gg.json",
          "https://rdap.verisign.com/com/v1/domain/ggdrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fggdrop.com",
          "https://rdap.verisign.com/com/v1/domain/ggauth.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/ggdrop.com.json",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/domain-registry/howl.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhowl.gg",
          "https://rdap.radix.host/rdap/domain/howl.uno",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/howl.gg.json",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/domain-registry/chicken.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fchicken.gg",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/chicken.gg.json",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/domain-registry/csgocasino.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgocasino.gg",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/csgocasino.gg.json",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/domain-registry/hunt.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhunt.gg",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/hunt.gg.json",
          "https://rdap.verisign.com/com/v1/domain/csbattle.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsbattle.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/csbattle.com.json",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/domain-registry/skinrave.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinrave.gg",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/skinrave.gg.json",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/domain-registry/csdouble.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsdouble.gg",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/csdouble.gg.json",
          "https://rdap.verisign.com/com/v1/domain/rustchance.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustchance.com",
          "https://rdap.verisign.com/com/v1/domain/hgfuihd.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/rustchance.com.json",
          "https://rdap.radix.host/rdap/domain/cobaltlab.tech",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcobaltlab.tech",
          "https://rdap.verisign.com/com/v1/domain/cobaltauth.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/cobaltlab.tech.json",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/domain-registry/raided.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fraided.gg",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/raided.gg.json",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/domain-registry/rustneo.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustneo.gg",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/rustneo.gg.json",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/domain-registry/splits.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsplits.gg",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/splits.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/upgrader.pro",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fupgrader.pro",
          "https://rdap.radix.host/rdap/domain/upgauth.space",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/upgrader.pro.json",
          "https://rdap.centralnic.com/fans/domain/skin.fans",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.fans",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/skin.fans.json",
          "https://rdap.nic.one/domain/hotpizza.one",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhotpizza.one",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/hotpizza.one.json",
          "https://rdap.verisign.com/com/v1/domain/g4skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg4skins.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/g4skins.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2royal.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2royal.com",
          "https://rdap.verisign.com/com/v1/domain/tf2auth.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/tf2royal.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2hunt.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2hunt.com",
          "https://rdap.verisign.com/com/v1/domain/rstspcl.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/tf2hunt.com.json",
          "https://rdap.identitydigital.services/rdap/domain/tf2.bet",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2.bet",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/tf2.bet.json",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/domain-registry/openstars.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fopenstars.gg",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/openstars.gg.json",
          "https://rdap.verisign.com/com/v1/domain/skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/skins.com.json",
          "https://rdap.identitydigital.services/rdap/domain/white.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwhite.market",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/white.market.json",
          "https://rdap.identitydigital.services/rdap/domain/moon.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmoon.market",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/moon.market.json",
          "https://rdap.verisign.com/com/v1/domain/csfloat.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsfloat.com",
          "https://rdap.verisign.com/com/v1/domain/csgofloat.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/csfloat.com.json",
          "https://rdap.identitydigital.services/rdap/domain/skin.land",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.land",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/skin.land.json",
          "https://rdap.verisign.com/com/v1/domain/haloskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhaloskins.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/haloskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/163.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuff.163.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/buff.163.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmarket.csgo.com",
          "https://rdap.verisign.com/net/v1/domain/dota2.net",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/market.csgo.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinport.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinport.com",
          "https://pubapi.registry.google/rdap/domain/skinport.app",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/skinport.com.json",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/domain-registry/skinflow.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinflow.gg",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/skinflow.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/skin.place",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.place",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/skin.place.json",
          "https://rdap.verisign.com/com/v1/domain/skinsmonkey.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinsmonkey.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/skinsmonkey.com.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbaron.de",
          "https://rdap.verisign.com/com/v1/domain/skinbaron.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/skinbaron.de.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frust.tm",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/rust.tm.json",
          "https://rdap.verisign.com/com/v1/domain/pirateswap.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fpirateswap.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/pirateswap.com.json",
          "https://rdap.radix.host/rdap/domain/mannco.store",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmannco.store",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/mannco.store.json",
          "https://rdap.verisign.com/com/v1/domain/skinswap.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinswap.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/skinswap.com.json",
          "https://rdap.verisign.com/com/v1/domain/exeskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fexeskins.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/exeskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/balticskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbalticskins.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/balticskins.com.json",
          "https://rdap.nic.trade/domain/cs.trade",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.trade",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/cs.trade.json",
          "https://rdap.verisign.com/com/v1/domain/rapidskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frapidskins.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/rapidskins.com.json",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/domain-registry/tradeit.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftradeit.gg",
          "https://rdap.verisign.com/com/v1/domain/connect-tradeit.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/tradeit.gg.json",
          "https://rdap.verisign.com/com/v1/domain/49skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F49skins.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/49skins.com.json",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/domain-registry/skinvault.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinvault.gg",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/skinvault.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/aim.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Faim.market",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/aim.market.json",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/domain-registry/skinout.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinout.gg",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/skinout.gg.json",
          "https://rdap.verisign.com/com/v1/domain/ntskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fntskins.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/ntskins.com.json",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/domain-registry/gamerpay.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamerpay.gg",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/gamerpay.gg.json",
          "https://rdap.nic.tf/domain/scrap.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fscrap.tf",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/scrap.tf.json",
          "https://rdap.nic.tf/domain/marketplace.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmarketplace.tf",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/marketplace.tf.json",
          "https://rdap.identitydigital.services/rdap/domain/skins.cash",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.cash",
          "https://rdap.identitydigital.services/rdap/domain/skinscash.live",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/skins.cash.json",
          "https://rdap.verisign.com/net/v1/domain/csgo.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo.net",
          "https://rdap.verisign.com/net/v1/domain/easylot.net",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/csgo.net.json",
          "https://rdap.verisign.com/net/v1/domain/cybershoke.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcybershoke.net",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/cybershoke.net.json",
          "https://rdap.verisign.com/net/v1/domain/fastcup.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffastcup.net",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/fastcup.net.json",
          "https://rdap.verisign.com/com/v1/domain/leetify.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fleetify.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/leetify.com.json",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/domain-registry/scope.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fscope.gg",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/scope.gg.json",
          "https://rdap.verisign.com/com/v1/domain/tradeupspy.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftradeupspy.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/tradeupspy.com.json",
          "https://rdap.identitydigital.services/rdap/domain/cs.deals",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.deals",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/cs.deals.json",
          "https://rdap.verisign.com/com/v1/domain/pricempire.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fpricempire.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/pricempire.com.json",
          "https://rdap.identitydigital.services/rdap/domain/lzt.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flzt.market",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/lzt.market.json",
          "https://rdap.verisign.com/com/v1/domain/z2u.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fz2u.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/z2u.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoroll.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoroll.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/csgoroll.com.json",
          "https://rdap.verisign.com/com/v1/domain/rollbit.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frollbit.com",
          "https://rdap.verisign.com/com/v1/domain/rbsnin.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/rollbit.com.json",
          "https://rdap.identitydigital.services/rdap/domain/500.casino",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F500.casino",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/500.casino.json",
          "https://rdap.verisign.com/com/v1/domain/csgobig.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgobig.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/csgobig.com.json",
          "https://rdap.verisign.com/com/v1/domain/casedrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcasedrop.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/casedrop.com.json",
          "https://rdap.verisign.com/com/v1/domain/banditcamp.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbanditcamp.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/banditcamp.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinbox.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbox.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/skinbox.com.json",
          "https://rdap.verisign.com/com/v1/domain/tastydrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftastydrop.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/tastydrop.com.json",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/domain-registry/csgopolygon.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgopolygon.gg",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/csgopolygon.gg.json",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/domain-registry/magicdrop.ru.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmagicdrop.ru",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/magicdrop.ru.json",
          "https://rdap.verisign.com/com/v1/domain/csdice.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsdice.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/csdice.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinodds.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinodds.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/skinodds.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgowin.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgowin.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/csgowin.com.json",
          "https://rdap.verisign.com/net/v1/domain/csgorun.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgorun.net",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/csgorun.net.json",
          "https://rdap.verisign.com/com/v1/domain/openskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fopenskins.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/openskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustbet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustbet.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/rustbet.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgomagic.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgomagic.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/csgomagic.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgobounty.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgobounty.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/csgobounty.com.json",
          "https://rdap.verisign.com/com/v1/domain/ezskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fezskins.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/ezskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustcases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustcases.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/rustcases.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoreaper.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoreaper.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/csgoreaper.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgocases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgocases.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/csgocases.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo-skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo-skins.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/csgo-skins.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgonet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgonet.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/csgonet.com.json",
          "https://rdap.verisign.com/com/v1/domain/wtfskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwtfskins.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/wtfskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/flamecases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fflamecases.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/flamecases.com.json",
          "https://rdap.verisign.com/com/v1/domain/gamedom.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamedom.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/gamedom.com.json",
          "https://rdap.nic.club/domain/skin.club",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.club",
          "https://rdap.verisign.com/net/v1/domain/sc-auth.net",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/skin.club.json",
          "https://rdap.verisign.com/com/v1/domain/daddyskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdaddyskins.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/daddyskins.com.json",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/domain-registry/rustix.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustix.gg",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/rustix.gg.json",
          "https://rdap.nic.club/domain/skins.club",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.club",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/skins.club.json",
          "https://rdap.publicinterestregistry.org/rdap/domain/csgohouse.org",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgohouse.org",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/csgohouse.org.json",
          "https://rdap.verisign.com/net/v1/domain/skinrave.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinrave.net",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/skinrave.net.json",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/domain-registry/bloodycase.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbloodycase.gg",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/bloodycase.gg.json",
          "https://rdap.verisign.com/com/v1/domain/csgoclicker.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoclicker.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/csgoclicker.com.json",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/domain-registry/rustbet.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustbet.gg",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/rustbet.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs-drop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs-drop.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/cs-drop.com.json",
          "https://rdap.verisign.com/net/v1/domain/hellstore.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhellstore.net",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/hellstore.net.json",
          "https://rdap.verisign.com/com/v1/domain/rustloot.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustloot.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/rustloot.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo-case.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo-case.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/csgo-case.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgogem.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgogem.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/csgogem.com.json",
          "https://rdap.verisign.com/com/v1/domain/rainbet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frainbet.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/rainbet.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustclash.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustclash.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/rustclash.com.json",
          "https://rdap.identitydigital.services/rdap/domain/12cs.fail",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F12cs.fail",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/12cs.fail.json",
          "https://rdap.verisign.com/com/v1/domain/tf2easy.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwww.tf2easy.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/tf2easy.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2blaze.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2blaze.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/tf2blaze.com.json",
          "https://rdap.verisign.com/com/v1/domain/shuffle.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fshuffle.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/shuffle.com.json",
          "https://rdap.identitydigital.services/rdap/domain/buff.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuff.market",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/buff.market.json",
          "https://rdap.identitydigital.services/rdap/domain/avan.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Favan.market",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/avan.market.json",
          "https://rdap.identitydigital.services/rdap/domain/cs.money",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.money",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/cs.money.json",
          "https://rdap.verisign.com/com/v1/domain/uuskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fuuskins.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/uuskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/youpin898.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fyoupin898.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/youpin898.com.json",
          "https://rdap.verisign.com/com/v1/domain/c5game.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fc5game.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/c5game.com.json",
          "https://rdap.verisign.com/com/v1/domain/waxpeer.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwaxpeer.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/waxpeer.com.json",
          "https://rdap.verisign.com/com/v1/domain/dmarket.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdmarket.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/dmarket.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamcommunity.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamcommunity.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/steamcommunity.com.json",
          "https://rdap.verisign.com/com/v1/domain/lootfarm.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flootfarm.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/lootfarm.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustskins.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/rustskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/krakatoa.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fkrakatoa.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/krakatoa.com.json",
          "https://rdap.verisign.com/com/v1/domain/shadowpay.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fshadowpay.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/shadowpay.com.json",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/domain-registry/igxe.cn.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Figxe.cn",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/igxe.cn.json",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/domain-registry/swap.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fswap.gg",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/swap.gg.json",
          "https://rdap.verisign.com/com/v1/domain/bitskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbitskins.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/bitskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2mart.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2mart.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/tf2mart.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinbid.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbid.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/skinbid.com.json",
          "https://rdap.verisign.com/com/v1/domain/lootbear.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flootbear.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/lootbear.com.json",
          "https://rdap.nic.tf/domain/backpack.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbackpack.tf",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/backpack.tf.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fstntrading.eu",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/stntrading.eu.json",
          "https://rdap.verisign.com/com/v1/domain/skinwallet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinwallet.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/skinwallet.com.json",
          "https://rdap.verisign.com/com/v1/domain/dota2market.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdota2market.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/dota2market.com.json",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/domain-registry/xplay.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fxplay.gg",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/xplay.gg.json",
          "https://rdap.verisign.com/com/v1/domain/esportal.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fesportal.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/esportal.com.json",
          "https://rdap.registro.br/domain/gamersclub.com.br",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamersclub.com.br",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/gamersclub.com.br.json",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/domain-registry/epidemic.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fepidemic.gg",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/epidemic.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs2stash.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs2stash.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/cs2stash.com.json",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/domain-registry/csgoskins.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoskins.gg",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/csgoskins.gg.json",
          "https://rdap.verisign.com/com/v1/domain/steamanalyst.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamanalyst.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/steamanalyst.com.json",
          "https://rdap.verisign.com/net/v1/domain/steamcardexchange.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamcardexchange.net",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/steamcardexchange.net.json",
          "https://rdap.verisign.com/com/v1/domain/dotabuff.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdotabuff.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/dotabuff.com.json",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/domain-registry/tracker.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftracker.gg",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/tracker.gg.json",
          "https://rdap.verisign.com/com/v1/domain/funpay.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffunpay.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/funpay.com.json",
          "https://rdap.verisign.com/com/v1/domain/playerauctions.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fplayerauctions.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/playerauctions.com.json",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/domain-registry/eldorado.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Feldorado.gg",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/eldorado.gg.json",
          "https://rdap.verisign.com/com/v1/domain/g2a.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg2a.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/g2a.com.json",
          "https://rdap.verisign.com/net/v1/domain/kinguin.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fkinguin.net",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/kinguin.net.json",
          "https://rdap.verisign.com/com/v1/domain/g2g.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg2g.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/g2g.com.json",
          "https://rdap.verisign.com/com/v1/domain/playerup.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fplayerup.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/playerup.com.json",
          "https://rdap.verisign.com/net/v1/domain/smurfhub.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfhub.net",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/smurfhub.net.json",
          "https://rdap.verisign.com/com/v1/domain/smurfaccounts.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfaccounts.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/smurfaccounts.com.json",
          "https://rdap.verisign.com/com/v1/domain/buycsgorank.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuycsgorank.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/buycsgorank.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgosmurfkings.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgosmurfkings.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/csgosmurfkings.com.json",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/domain-registry/smurfstore.co.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfstore.co",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/smurfstore.co.json",
          "https://rdap.verisign.com/com/v1/domain/steamlvlup.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlvlup.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/steamlvlup.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamlevels.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlevels.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/steamlevels.com.json",
          "https://rdap.verisign.com/com/v1/domain/levelsteam.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flevelsteam.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/levelsteam.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamlevelu.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlevelu.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/steamlevelu.com.json",
          "https://rdap.verisign.com/com/v1/domain/eloking.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Feloking.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/eloking.com.json",
          "https://rdap.publicinterestregistry.org/rdap/domain/boosteria.org",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fboosteria.org",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/boosteria.org.json",
          "https://rdap.verisign.com/com/v1/domain/overgear.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fovergear.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/overgear.com.json",
          "https://rdap.verisign.com/com/v1/domain/blazingboost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fblazingboost.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/blazingboost.com.json",
          "https://rdap.verisign.com/com/v1/domain/dota2boost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdota2boost.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/dota2boost.com.json",
          "https://rdap.verisign.com/com/v1/domain/buyboost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuyboost.com",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit/buyboost.com.json",
          "https://phishdestroy.io/steam_dossier/de/steam_tos_assets/auth-route-audit.json",
          "https://help.steampowered.com/en/faqs/view/365F-4BEE-2AE2-7BDD",
          "https://store.steampowered.com/privacy_agreement/#8",
          "https://www.edpb.europa.eu/system/files/2023-04/edpb_guidelines_202201_data_subject_rights_access_v2_en.pdf",
          "https://web.archive.org/web/20260810154631/https://store.steampowered.com/stats/support",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/design-review/part2/measurements.json",
          "https://phishdestroy.io/steam_dossier/de/VALVE_EVIDENCE_PACK/databases/TOTAL_VALVE_SCANDALS_MASTER_DB.csv",
          "https://phishdestroy.io/steam_dossier/de/license_disclaimer.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/de/index.content.json",
      "export_json_sha256": "b2f4cb942beea0d9e5448766c9d2868e447fe446d83537d9f835e6107b682261"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "de/investigation_part2.html",
      "language": "de",
      "title": "Zugriff auf Konten und Rechenschaftspflicht – Das Steam-Dossier",
      "source_url": "https://phishdestroy.io/steam_dossier/de/investigation_part2",
      "source_html_sha256": "f36d8cd2b339ca94e1018a6d26f62c2e72eec85c2d6c82fd54eefe91e4423d80",
      "exported_at": "2026-09-29T00:16:08.480Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "investigation_part2.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/de/investigation_part2.pdf?v=print-20260929-v5",
        "sha256": "e04fabe330091ff9d988b7ac29d45eb43c80fba889a1271980ce74bf182bf16b",
        "bytes": 131002,
        "pages": 9
      },
      "integrity": {
        "signed_object": "investigation_part2.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "investigation_part2.content.json.asc",
        "digest_file": "investigation_part2.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify investigation_part2.content.json.asc investigation_part2.content.json",
          "sha256sum -c investigation_part2.content.json.sha256"
        ]
      },
      "content": {
        "text": "DAS STEAM-DOSSIER / II\n\nIhr Konto.Ihr Zugang.Wer geht ran?\n\nÖffentliche Automatisierung. Ausgelagerter Support. Die Menschen, die am Ende die Zeche zahlen müssen.\n\nVerfolgen Sie die Infrastruktur, die gemeldeten Schäden und die Unterlagen, auf denen die Forderungen basieren.\n\nDie Infrastruktur nachverfolgen ↘\nANLAGE 01 / ÜBERWACHUNG DES LIVE-SCHATTENMARKTES550,000+\n\nSteam Konten, die derzeit aktiv auf dem FSB Market (anonymisierte Bezeichnung; der Originalname wird hier nicht genannt) zum Verkauf stehen\ngerade in diesem Moment\n\n550,000+ AKTUELLER BESTAND · 231,829 IM HISTORISCHEN SCRAPED-KORPUS (198,320 STEALER-LOGS)\n\nDie wichtigste unterirdische Clearingstelle für gekaperte Steam-Konten, FSB Market (zugehörige Namen nicht genannt) authentifiziert sowohl Käufer als auch Verkäufer mithilfe der offiziellen OpenID Steam von Valve (openid.realm = https://FSB Market). Zu jedem beliebigen Zeitpunkt werden über eine halbe Million gestohlene und kompromittierte Konten (Stealer-Logs von RedLine/Lumma, Phishing-Beute, Credential Stuffing) aktiv für wenige Cent angeboten ($0.50–$2.00). Weder FSB Market noch das zugehörige Forum wird durch den Link-Filter von Valve blockiert. Dabei handelt es sich um den industriellen Pool, aus dem die 63.06% bezahlten Bot-Konten gespeist werden, die Valve sperrt, ohne dem Opfer zu helfen.\n\nLive-Daten: Überwachung des Schattenmarktes (über 550.000 Live-Daten) ↗ · Aufzeichnungsdatensatz öffnen ↗ · Link-Filter-Trace öffnen ↗Über 550.000 LIVE\n\n01 / EIN ÖKOSYSTEM MIT AUTOREN\n\nDie Automatisierung hateine Papierspur.\n\nBenannte Projekte. Veröffentlichte Funktionen. Verfolgen Sie ein Tool bis zu seiner Dokumentation zurück und untersuchen Sie anschließend die erfassten Entwicklerbeziehungen.\n\n252ERFASSTE REPOSITORIES\n3,320GITHUB-PROFILE\n4,214PROFIL–REPOSITORY-PAARE\nValve InfrastrukturÖffentliche BibliothekenWiederverwendbare Anwendungen\nDie Linien zeigen dokumentierte Integrationen oder Abhängigkeiten an. Wählen Sie einen Knoten aus, um dessen Belegung zu verfolgen.\n\nAutomatisierung für mehrere Konten / JustArchiNET\n\nArchiSteamFarm\n\nDas Projekt wirbt ausdrücklich mit dem gleichzeitigen Sammeln von Karten über verschiedene „Steam“-Konten hinweg. In der Projektdatei ist eine Abhängigkeit von SteamKit2 angegeben.\n\nLies die Dokumentation des Projekts ↗\n\nSteamKit → ArchiSteamFarm\ndeklarierte Abhängigkeit ↗\n\nGESAMMELTE BEZIEHUNGEN\n\n40 Beitrags-Labels · 40 Forker-Etiketten\n\nBeispiel eines Mitwirkenden siehe unten. Diese Bezeichnungen beschreiben die Beziehung zum Repository, nicht ein Arbeitsverhältnis oder eine Genehmigung.\n\n@JustArchi@renovate[Bot]@JustArchi-ArchiBot@dependabot-preview[bot]@renovate-bot@actions-user@dependabot-support@Abrynos\nWas die Entwicklergrafik verdeutlicht\n\nDie Grafik stellt die veröffentlichten Beziehungen zwischen Mitwirkenden und Forkern bei namentlich genannten Projekten und GitHub-Profilen dar. Dabei handelt es sich um öffentlich zugängliche Daten – Repository-Forks, Mitwirkungslisten, Profilverknüpfungen. Die Frage ist, welche Schlussfolgerungen aus den veröffentlichten Informationen zu Fähigkeiten und Entwicklerbeziehungen gezogen werden müssen Valve, nicht, was diese Untersuchung erfunden hat. Quellcode-Hashes werden in der Herkunft der Karte.\n\nEntdecken Sie das gesamte Netzwerk ↗Quelldaten des Repositorys ↓\n\n02 / UNTERSCHIEDLICHE BEFUGNISSE. UNTERSCHIEDLICHE BEFÄHIGUNGEN.\n\nWelche TasteWovon reden wir hier eigentlich?\n\nUm ein Spiel zu spielen, muss der Spieler keinen persönlichen Web-API-Schlüssel angeben. Das ist der entscheidende Unterschied, um den es bei dieser Untersuchung geht.\n\n01 / BENUTZERKONTO\nPersönlicher Web-API-Schlüssel\nsteamcommunity.com/dev/apikey\n\nWird von einem Benutzerkonto für zulässige API-Aufrufe ausgestellt. Die Erstellung, Sichtbarkeit und Sperrung von Schlüsseln sowie die Erkennung von Missbrauch sind Fragen der Kontosicherheit.\n\n02 / SPIEL-BACKEND\nWeb-API-Schlüssel des Herausgebers\n\nSteamworks-Partner verwenden die Anmeldedaten des Herausgebers für unterstützte Backend-Vorgänge, einschließlich spielbezogener Dienste. Der persönliche Schlüssel eines Spielers ist ein separates Zugangsdatum.\n\n03 / IDENTITÄT & SITZUNG\nOpenID / Sitzungstoken\n\nOpenID dient der Identitätsbestätigung gegenüber einer Website. Ein Steam-Sitzungs- oder Aktualisierungstoken erfüllt einen anderen Zweck. Diese Mechanismen sollten nicht als ein einziger, austauschbarer „API-Schlüssel“ dargestellt werden.\n\nValve dokumentiert sowohl die Web-API-Schlüssel der Nutzer als auch die der Herausgeber. Die gesamte Web-API ist daher nicht von Steamworks getrennt. Dokumentation zum API-Schlüssel ↗ archiviert 2026-09-15 ↗ · Authentifizierung während der Spielsitzung ↗ archiviert 2026-08-29 ↗\n\nDOKUMENTIERT VOM AUTOR DES TOOLS / MÄRZ 2024\n\nFür die Automatisierung kann mehr als nur ein API-Schlüssel verwendet werden.\n\nIm Wiki des Trade Offer Managers wird beschrieben, wie ein Session-Zugriffstoken für Teile der Web-API verwendet werden kann, wenn kein separater API-Schlüssel vorhanden ist. Außerdem wird dort die mobile Bestätigung für die Schlüsselerstellung ab Ende 2023 dokumentiert. Der Betreuer bezeichnet die Verwendung von Tokens auf diese Weise als von Valve nicht unterstützt; hierbei handelt es sich um eine veraltete Angabe in der Dokumentation und nicht um einen aktuellen Umgehungstest.\n\nDie Erklärung des Betreibers einsehen ↗ archiviert 2026-09-24 ↗\n\nDIE MENSCHLICHE SEITE / EIN ANHAND EINES BEISPIELS DARGESTELLTER PHISHING-VERLAUF\n\nEs läuft noch.Bereits offengelegt.\n\nEine Nachricht von einem Freund. Eine Aufforderung zur Stimmabgabe. Eine „Danke“-Seite. Für den Spieler ist die Aufgabe erledigt. Eine kompromittierte Sitzung kann jedoch über diesen Moment hinaus andauern.\n\nAUF DEM BILDSCHIRM DES SPIELERS\n\nF\nDER BERICHT EINES FREUNDES\n\n„Kannst du für unser Team stimmen?“\n\nDie Anfrage geht über den Chat auf Steam von einem bekannten Konto ein. In diesem Fall wird die verlinkte Seite im Browser des Kunden geöffnet.\n\nAUS DEN AUGEN\n\nDas Vertrauen entsteht schon vor der Website.\n\nEin gehacktes Konto eines Bekannten kann einem Phishing-Link Glaubwürdigkeit verleihen. Die umgebende Steam-Oberfläche bietet keine Zertifizierung für die Zielwebsite.\n\nBEKANNTER ABSENDER / EXTERNES ZIEL\nDie Sicherheit des Kontos hat Vorrang vor jedem Verkauf.\n\nDer Spieler hatte nicht die Absicht, Zugangsdaten für die Automatisierung zu erstellen oder die Kontrolle zu übertragen. Die Rückkehr zu einem Spiel ist kein Beweis dafür, dass das Konto sicher ist. Valve verfügt über die Sitzungsprotokolle, die Aufzeichnungen zur Erstellung des API-Schlüssels und die Daten zur Gerätekorrelation. Das Opfer hingegen nicht. Diese Asymmetrie ist das Problem der Rechenschaftspflicht.\n\nZugriff auf Sitzungen und Arten von Anmeldedaten\n\nEin API-Schlüssel und eine angemeldete Sitzung sind getrennte Zugangsdaten mit unterschiedlichen Berechtigungen. Das Widerrufen eines Schlüssels beendet keine aktive Sitzung. In der Dokumentation von Valve werden beide beschrieben; Valve verfügt über die Protokolle, aus denen hervorgeht, welche Zugangsdaten zum Zeitpunkt einer strittigen Aktion aktiv waren. Gefordert wird die Offenlegung dieses Datensatzes – nicht eine Schlussfolgerung, die die Ermittlungsbehörde erfunden hat. Dokumentation des Betreuers zur Token-Verarbeitung ↗ archiviert 2026-09-24 ↗ · Valve Wichtige Dokumentation ↗ archiviert 2026-09-15 ↗\n\n03 / DER OFFIZIELLE MARKT HAT EINE OBERGRENZE\n\nDer Gegenstand kann selten sein.Die Beschränkung bleibt bestehen.\n\nEin Preis, der über der Obergrenze für die Notierung liegt, kann nicht durch eine einzige Notierung auf dem Community-Markt zu diesem vollen Preis erzielt werden.\n\nORIENTIERUNGSPREIS$5,000Den Angebotspreis des Artikels ändern\n$100$20,000\n\nEine Veranschaulichung des veröffentlichten Kurslimits, keine Kursbewertung und keine Handelsempfehlung.\n\nLISTING-OBERGRENZE≈ $1,800\nGELDBEUTELKAPPE≈ $2,000\n\nÜber der veröffentlichten Obergrenze für Notierungen.\n\nGuthaben aus dem Wallet können nicht auf ein Bankkonto ausgezahlt werden. Diese Einschränkungen führen zu einer Nachfrage, die von Skin-Marktplätzen von Drittanbietern gedeckt wird: eine Nachfrage, die durch die Obergrenzen für Listings und Wallet-Guthaben entsteht, während die eigenen Regeln von Valve kommerziellen Anbietern verbieten, diese Nachfrage zu bedienen.\n\nSteams Marktgrenzen ↗ archiviert 2026-09-21 ↗\n\n04 / INNERHALB DER UNTERSTÜTZUNGSGRENZE\n\nMit Daten betraut.Verantwortlich für den Zugang.\n\nDie Datenschutzerklärung von Valve sieht ausdrücklich vor, dass personenbezogene Daten an externe Support-Anbieter weitergegeben werden dürfen, sofern dies für den Support erforderlich ist.\n\nDER SPIELERKonto & Belege\n→\nVENTILWiederherstellungsprozess\n→\nDIENSTLEISTERDelegierter Zugriff\n\nDatenschutzerklärung § 5.2 ↗ · Die Richtlinien von Valve selbst gestatten den Zugriff durch Dritte zu Supportzwecken. Die offenen Fragen lauten: Welche Berechtigungen wurden erteilt, welche Protokollaufzeichnungen liegen vor und was geschah, als der Zugriff angeblich missbraucht wurde?\n\n2015\nDie Waage war öffentlich zugänglich\n\nValve räumte den groß angelegten Diebstahl von Konten ein und erläuterte Schutzmaßnahmen.\n\nValve Veröffentlichung ↗archiviert 2026-08-09 ↗\n2015\nValve hat den Schalter ausgelagert – und das auch so gesagt\n\nValve unterhält ein kleines internes Steam Support-Führungsteam und erklärte dies „hat ein paar verschiedene Firmen beauftragt“ zur Abwicklung des Supports (Erik Johnson, Valve, an Kotaku); gemäß § 5.2 der Datenschutzerklärung ist diesen Dritten der Zugriff auf Nutzerdaten gestattet. Welcher Auftragnehmer über Zugriffsrechte zur Kontowiederherstellung verfügt, hat Valve nie bekannt gegeben — In der Community-Diskussion werden Anbieter wie Concentrix genannt, doch keiner davon ist Valve-bestätigt. Der ausgelagerte Helpdesk war bereits Jahre vor den beiden unten genannten Eingeständnissen eingerichtet worden.\n\nKotaku: Valve zu seinem Support ↗archiviert 2025-07-11 ↗\n2023\nDas erste Bekenntnis\n\nDas CS:GO-Team von Valve übernimmt schriftlich die Verantwortung für einen Account, der über den eigenen Hilfeanfrageprozess kompromittiert wurde, und macht die Transaktionen rückgängig.\n\nDen Outsourcing-Fall öffnen ↓\n2025\nDas zweite Geständnis\n\n33 Monate später schreibt der Steam-Support, dass ein Techniker „unseren Prozess nicht befolgt hat, was dazu führte, dass Ihr Konto einer anderen Person zugewiesen wurde“. Gleicher Kanal. Gleiches Ergebnis.\n\nDexerto, 14. November 2025 ↗\n\nAKTE / HFB UND DIE VORWÜRFE ZUM OUTSOURCING\n\nDer Weg dorthin war Steam Support selbst.Valve hat dies schriftlich erklärt.\n\nIn der von Dexerto veröffentlichten Antwort des Kundendienstes übernimmt das CS:GO-Team von Valve die Verantwortung für die Kompromittierung eines Kontos im Rahmen des Hilfeanfrageprozesses — über einen eigenen Kanal, nicht über eine Phishing-Seite und nicht über den Nutzer. Die Gegenstände wurden wiederbeschafft und die Transaktionen rückgängig gemacht – eine Abhilfe, von der Valve anderen Opfern sagt, dass es sie nicht gibt. Der Bestand von HFB wurde mit $2,000,000+ an diesem Tag und $3,000,000+ im weiteren Verlauf; Qkss verlor $1,000,000+ auf dieselbe Weise und ging leer aus.\n\nANTWORT DES SUPPORTS / WIEDERGEBEN VON DEXERTO · 21. FEB 2023\n„durch eine Support-Anfrage kompromittiert, wofür das CS:GO-Team die Verantwortung übernimmt“\nLesen Sie den Bericht und die wiedergegebene Nachricht ↗ archiviert 2025-08-18 ↗\n01 / WAS DAS VENTIL DURCHLÄSST\nDer eigene Support-Kanal war der Einstieg\n\nDie Antwort bezieht sich auf das kompromittierte Konto und die Stornierung der damit getätigten Transaktionen. Valve hat diese storniert – die Transaktionen waren also stornierbar. Das ursprüngliche, authentifizierte Ticket ist in dieser Sammlung nicht enthalten.\n\n02 / WAS DIE ENTLASSUNGEN NICHT BEHOBEN HABEN\nIm November 2025 öffnete sich dieselbe Tür erneut\n\nDer Auftragnehmer entließ sein gesamtes Steam-Support-Personal – dies berichtete Mzkshow über Dexerto, nicht in einer Valve-Personalmitteilung. Dreiunddreißig Monate später schrieb Steam Support an einen anderen Inkassobeauftragten, dass „ein Support-Techniker, der die Hilfeanfrage bearbeitet hat, unseren Prozess nicht befolgt hat, was dazu führte, dass Ihr Konto auf eine andere Person zurückgesetzt wurde“. Ein Zitat von Valve selbst, über denselben Kanal.\n\nDie zweite Aufnahme, 14. November 2025 ↗\n03 / WAS IST „OPEN“?\nValve hat den Auftragnehmer nie namentlich genannt\n\nWeder der Auftragnehmer noch der Standort lassen sich aus diesen Quellen ermitteln. Das ist keine Lücke in der Berichterstattung – es handelt sich um eine Information, die Valve nicht preisgegeben hat, nämlich wer Zugriff auf die Benutzerkonten hatte.\n\nZeitgenössischer Bericht über den Fall ↗\n\nDrei Fragen, die Valve nicht beantwortet hat: Wer könnte die Kontowiederherstellung außer Kraft setzen, was hat die Zugriffsprüfung ergeben und was hat sich danach geändert?\n\nSpätere Vorwürfe im archivierten Support-Archiv\n\nZwei Reddit-Beiträge aus dem Jahr 2024 berichten über weitere Untersuchungen von Mzkshow – einen Fall zur Aufhebung einer Sperre vom Juli 2024 (VAC) und einen Fall zur Bestandsaufnahme vom Dezember 2024 ($13,000). Dabei handelt es sich um separat gemeldete Vorfälle. Die Frage nach der Verantwortlichkeit ist in beiden Fällen identisch: Wer hatte Zugriffsrechte zur Außerkraftsetzung, was ergab die Prüfung und was hat sich geändert?\n\n14. Juli 2024 · gemeldete Wiederherstellung / VAC-Sperrfall ↗2. Dezember 2024 · gemeldet $13,000 Bestandsfall ↗archiviert 2025-08-05 ↗Zwei gespeicherte Pfosten, Quellzeilen und Hash-Werte ↓\n\n05 / DEM VERLUST FOLGEN\n\nJeder Betragbraucht eine Hülle.\n\nZehn Fälle, Juni 2022 bis März 2026. Jeder Betrag entspricht dem Wert, den die jeweilige Quelle veröffentlicht hat — $6,300,000, $2,000,000+, $1,000,000+, ≈$320,000, ≈$300,000, und zwar auf 288 €. Valve verwaltet das Transaktionsprotokoll, die Sitzungsaufzeichnung und den Support-Prüfpfad für jeden einzelnen Fall, hat jedoch keines dieser Dokumente vorgelegt.\n\nSUPPORT-KANAL21 JUN 2022\n$2,000,000+\nHFB — the largest inventory in the game\n\nBERICHTETE LAGERBESTANDSBEWERTUNG · IM FEBRUAR AUF ÜBER $3M ANGEHOBEN2023-FOLGEMELDUNG\n\nSieben „Souvenir Dragon Lores“ und das „1 Blue Gem Karambit“ mit der Nummer # – allein dieses Messer hat einen Wert von etwa $1.26. Das Konto war drei Jahre lang inaktiv, wobei der Authentifikator noch aktiv war; E-Mail-Adresse und Passwort wurden über den Support-Wiederherstellungsweg geändert. Valve hat die Transaktionen rückgängig gemacht – und seine Verantwortung schriftlich bestätigt. Vor der Rückabwicklung waren Berichten zufolge bereits $200,000+ an Erlösen über market.csgo.com abgehoben worden, eine Plattform, die Zahlungen in Bargeld und Kryptowährung abwickelt. Eine Rückabwicklung führt zur Rückgabe eines Skins, nicht des Geldes, das jemand bereits auf sein Konto überwiesen hat. Bei der Rückabwicklung kam es zudem zu einem Fehler: Ein Käufer versteckte sein „Souvenir Dragon Lore“ in einem Lagerraum im Spiel; das Skript konnte nicht in den Inhalt des Containers einsehen, und Valve duplizierte einen $130,000-Gegenstand beim Rückgängigmachen eines Diebstahls – entdeckt durch Gegenstands-IDs und Meldungen der Community, im Juli gelöscht 2022,; der Käufer erhielt eine Rückerstattung von BUFF statt von Valve.\n\nDexerto, Tag des Diebstahls ↗\nGELDBEUTEL & EINKAUFE07 JULI 2022\n>$500\n44 disputed Market purchases\n\nANGEGEBENE AUSGABEN AUS DEM PORTEMONNAIE · USD\n\nEin Nutzer berichtet von unbefugten Käufen von Dota-2-Gegenständen mit geringem Wert und einer unbefriedigenden Reaktion des Kundendienstes.\n\nLesen Sie die Beschwerde und sehen Sie sich die verlinkten Screenshots an ↗\nPLATTFORM-HACK14 2022. August\n$6,300,000\nCS.Money — 19,000+ Skins aus den Bots\n\nPREISBEWERTUNG · ERSTE SCHÄTZUNG $1.6M\n\nDie Angreifer erbeuteten die Dateien des mobilen Authentifikators der Handels-Bots des Marktplatzes und leerten diese; einen Teil der Beute verteilten sie an bekannte Händler, um die Spuren zu verwischen. Forscher aus der Community konnten die Angreiferkonten unter 55 innerhalb weniger Stunden identifizieren. Valve hat nichts rückgängig gemacht – eine Website eines Drittanbieters befindet sich außerhalb von Steam, so Steam, dessen Bestand, Handels-API und Kontensystem den Diebstahl von Anfang bis Ende ermöglichten.\n\nLies den zeitgenössischen Bericht ↗\nSUPPORT-KANALBERICHT21. Februar 2023\n$1,000,000+\nQkss – dieselbe Tür, derselbe Schauspieler, gegensätzliche Antwort\n\nAUSGEWIESENE BESTANDSBEWERTUNG\n\nGenauso wie im Fall von HFB, durch denselben Schauspieler und über dieselbe Supportanfrage. HFB wurde bereits acht Monate zuvor vollständig entschädigt. Qkss hingegen nicht. In den veröffentlichten Unterlagen gibt es keinen Unterschied zwischen den beiden Fällen, abgesehen von der Größe des Publikums.\n\nDexerto über die Ermittlungen im Fall „Mzkshow“ ↗\nSUPPORT-KANALBERICHT VOM 2023\n≈ $320,000\nDer Insiderhandel an sich – ein Jahr lang\n\nEINNAHMEN ÜBER EINEN ZEITRAUM VON ETWA EINEM JAHR · KEINE BESTANDSBEWERTUNG\n\nDer Support-Zugriff ermöglichte den Zugriff auf den Kontoverlauf bis zu 15 Jahre zurück: der erste CD-Key, die erste E-Mail, die erste Karte – genau die Nachweise, die für den Wiederherstellungsprozess benötigt werden. Wer auch immer die Datenbank besitzt, gewinnt diesen Streit immer gegen den Kontoinhaber. Ein gestohlener M4A4 Howl mit iBUYPOWER- und Titan Katowice-2014-Holos wurde für $35,000 verkauft und landete schließlich bei NAVIs b1t, der davon nichts ahnen konnte. Die Reaktion des Auftraggebers bestand darin, jeden Mitarbeiter zu entlassen, der im Support vSteamtätig war.\n\nEscorenews zu derselben Untersuchung ↗\nGELDBEUTEL & EINKAUFE09 DEC 2023\n€288\nVerlust der Wallet trotz zweistufiger Sicherung\n\nTRUSTPILOT · QUELLENVERZEICHNIS 16\n\nDer Rezensent berichtet von einem gehackten Konto und einer Weigerung, bei den Market-Ausgaben zu helfen. Der Export enthält keine individuelle URL für die Rezension.\n\nHerkunft der Quelle überprüfen ↗\nKONTOWIEDERHERSTELLUNG02 DEC-2024\n$13,000\n„Matvey“ – zwei Jahre nach den Entlassungen\n\nSCHÄTZUNG DES BESTANDS DURCH DEN AUTOR\n\nDie Wiederherstellung wurde einer Person gewährt, die Kontodaten vorgelegt hatte, die der Kontoinhaber selbst nicht zuordnen konnte. Gleicher Weg, gleiches Ergebnis, nachdem der Auftragnehmer seinen Support-Desk unter Steam aufgelöst hatte.\n\nLesen Sie den archivierten Vorwurf ↗\nKONTOWIEDERHERSTELLUNG09 MAI-2025\n≈ $10,000\nErstattung über das Ticket einer anderen Person\n\nGEMELDETER VERLUST EINES GEGENSTANDS · USD\n\nEin Nutzer aus Quebec behauptet, der Kundendienst habe auf Anfrage einer anderen Person das Passwort zurückgesetzt und den Kontoschutz aufgehoben.\n\nLesen Sie die Beschwerde aus erster Hand ↗\nSUPPORT-KANAL13 NOV 2025\n≈ $300,000\nHawkeye337 – und das zweite schriftliche Geständnis vValve\n\nDIE KOMPLETTE HOLO-KOLLEKTION VON KATOWICE 2014\n\nDer Angreifer forderte 1 Bitcoin und begann, die Sammlung auf Negevs zu kopieren, um sie zu vernichten. Steam Antwort des Supports: „Ein Support-Mitarbeiter, der die Supportanfrage bearbeitet hat, hat sich nicht an unseren Prozess gehalten, was dazu führte, dass Ihr Konto auf eine andere Person zurückgesetzt wurde.“ Dreiunddreißig Monate nach dem ersten Eingeständnis – dieselbe Geschichte. Das Konto wurde innerhalb weniger Stunden wiederhergestellt, nachdem der Thread auf X zum Trend geworden war. Qkss hatte diese Reichweite nicht.\n\nDexerto, 14 Nov 2025 ↗\nGELDBEUTEL & EINKAUFE29 MÄRZ 2026\n$50\nUnbefugte Aufladungen und verschenkte Spiele\n\nTRUSTPILOT · QUELLENVERZEICHNIS 290\n\nDer Rezensent wirft unbefugte Ausgaben und erfolglose Rückerstattungsanträge vor. Die URL der einzelnen Rezension fehlt im Export.\n\nHerkunft der Quelle überprüfen ↗\n\nDie Zuordnung und die Beträge entsprechen den Angaben der jeweiligen Quellen. Valve verfügt über die Transaktionsprotokolle, Sitzungsaufzeichnungen und Support-Prüfpfade für jeden einzelnen dieser Fälle. Legen Sie diese vor. Ein gespeicherter Reddit-Beitrag klärt die Frage nicht – die eigenen Aufzeichnungen von Valve tun dies.\n\nDIE KOLLEKTION / NACH DER PRÜFUNG\n\n231,829 Konten im Angebot.Valve enthält die Protokolle für jeden einzelnen.\n354 → 201\nTrustpilot-Bewertungen\n\n153 doppelte Zeilen wurden entfernt. Die URLs der einzelnen Bewertungen wurden beim Export nicht beibehalten.\n\n231,829\nSteam Kontoeinträge\n\n33,509 als selbst registriert eingestuft; 198,320 unter dem Label „Collector’s Stealer“. Die Angebote stellen keine abgeschlossenen Verkäufe dar.\n\nPrüfung der Inkassoforderungen ↓Das Quellarchiv durchsuchen ↗",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Ihr Konto.Ihr Zugang.Wer geht ran?"
          },
          {
            "level": 2,
            "id": null,
            "text": "Die Automatisierung hateine Papierspur."
          },
          {
            "level": 3,
            "id": null,
            "text": "ArchiSteamFarm"
          },
          {
            "level": 2,
            "id": null,
            "text": "Welche TasteWovon reden wir hier eigentlich?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Persönlicher Web-API-Schlüssel"
          },
          {
            "level": 3,
            "id": null,
            "text": "Web-API-Schlüssel des Herausgebers"
          },
          {
            "level": 3,
            "id": null,
            "text": "OpenID / Sitzungstoken"
          },
          {
            "level": 3,
            "id": null,
            "text": "Für die Automatisierung kann mehr als nur ein API-Schlüssel verwendet werden."
          },
          {
            "level": 2,
            "id": null,
            "text": "Es läuft noch.Bereits offengelegt."
          },
          {
            "level": 3,
            "id": "session-hidden-title",
            "text": "Das Vertrauen entsteht schon vor der Website."
          },
          {
            "level": 2,
            "id": null,
            "text": "Der Gegenstand kann selten sein.Die Beschränkung bleibt bestehen."
          },
          {
            "level": 2,
            "id": null,
            "text": "Mit Daten betraut.Verantwortlich für den Zugang."
          },
          {
            "level": 3,
            "id": null,
            "text": "Die Waage war öffentlich zugänglich"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve hat den Schalter ausgelagert – und das auch so gesagt"
          },
          {
            "level": 3,
            "id": null,
            "text": "Das erste Bekenntnis"
          },
          {
            "level": 3,
            "id": null,
            "text": "Das zweite Geständnis"
          },
          {
            "level": 3,
            "id": null,
            "text": "Der Weg dorthin war Steam Support selbst.Valve hat dies schriftlich erklärt."
          },
          {
            "level": 4,
            "id": null,
            "text": "Der eigene Support-Kanal war der Einstieg"
          },
          {
            "level": 4,
            "id": null,
            "text": "Im November 2025 öffnete sich dieselbe Tür erneut"
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve hat den Auftragnehmer nie namentlich genannt"
          },
          {
            "level": 2,
            "id": null,
            "text": "Jeder Betragbraucht eine Hülle."
          },
          {
            "level": 3,
            "id": null,
            "text": "HFB — the largest inventory in the game"
          },
          {
            "level": 3,
            "id": null,
            "text": "44 disputed Market purchases"
          },
          {
            "level": 3,
            "id": null,
            "text": "CS.Money — 19,000+ Skins aus den Bots"
          },
          {
            "level": 3,
            "id": null,
            "text": "Qkss – dieselbe Tür, derselbe Schauspieler, gegensätzliche Antwort"
          },
          {
            "level": 3,
            "id": null,
            "text": "Der Insiderhandel an sich – ein Jahr lang"
          },
          {
            "level": 3,
            "id": null,
            "text": "Verlust der Wallet trotz zweistufiger Sicherung"
          },
          {
            "level": 3,
            "id": null,
            "text": "„Matvey“ – zwei Jahre nach den Entlassungen"
          },
          {
            "level": 3,
            "id": null,
            "text": "Erstattung über das Ticket einer anderen Person"
          },
          {
            "level": 3,
            "id": null,
            "text": "Hawkeye337 – und das zweite schriftliche Geständnis vValve"
          },
          {
            "level": 3,
            "id": null,
            "text": "Unbefugte Aufladungen und verschenkte Spiele"
          },
          {
            "level": 2,
            "id": null,
            "text": "231,829 Konten im Angebot.Valve enthält die Protokolle für jeden einzelnen."
          },
          {
            "level": 3,
            "id": null,
            "text": "Trustpilot-Bewertungen"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam Kontoeinträge"
          }
        ],
        "links": [
          "https://phishdestroy.io/live-intel/?category=steam",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/lzt.market.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-evidence-lzt.json",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://github.com/JustArchiNET/ArchiSteamFarm/blob/main/ArchiSteamFarm/ArchiSteamFarm.csproj",
          "https://github.com/JustArchi",
          "https://github.com/renovate[bot]",
          "https://github.com/JustArchi-ArchiBot",
          "https://github.com/dependabot-preview[bot]",
          "https://github.com/renovate-bot",
          "https://github.com/actions-user",
          "https://github.com/dependabot-support",
          "https://github.com/Abrynos",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/automation-map.json",
          "https://phishdestroy.io/steam_dossier/de/output_steam_network/network.html",
          "https://phishdestroy.io/steam_dossier/de/output_steam_network/raw_data.json",
          "https://partner.steamgames.com/doc/webapi_overview/auth",
          "http://web.archive.org/web/20260915025812/https://partner.steamgames.com/doc/webapi_overview/auth",
          "https://partner.steamgames.com/doc/webapi/ISteamUserAuth",
          "http://web.archive.org/web/20260829124950/https://partner.steamgames.com/doc/webapi/ISteamUserAuth",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "http://web.archive.org/web/20260924181824/https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://store.steampowered.com/privacy_agreement/",
          "https://store.steampowered.com/oldnews/19618",
          "http://web.archive.org/web/20260809125516/https://store.steampowered.com/oldnews/19618",
          "https://kotaku.com/valve-explains-why-steam-customer-service-is-still-terr-1736988223",
          "http://web.archive.org/web/20250711004653/https://kotaku.com/valve-explains-why-steam-customer-service-is-still-terr-1736988223",
          "https://www.dexerto.com/counter-strike-2/valve-saves-hacked-cs2-player-threatened-with-ransom-over-300000-of-rare-stickers-3283135/",
          "https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "http://web.archive.org/web/20250818113925/https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "https://lis-skins.com/ru/blog/krupneisaia-mosenniceskaia-sxema-v-istorii-steam/",
          "https://www.reddit.com/r/cs2/comments/1e38jo4/stealing_accounts_and_removing_vac_bans_a_new/",
          "https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "http://web.archive.org/web/20250805141942/https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/outsourcing-archive-records.json",
          "https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "https://escorenews.com/en/csgo/news/44087-valve-steam-support-employee-accused-of-selling-inactive-accounts-inventories-worth-six-figures-b1t-has-one-of-these-skins",
          "https://phishdestroy.io/steam_dossier/de/PART2_RESEARCH.md",
          "https://www.reddit.com/r/GlobalOffensive/comments/1h56shi/steam_support_is_stealing_accounts/",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/design-review/part2/quality-review.json",
          "https://phishdestroy.io/steam_dossier/de/steam_evidence_archive.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/de/investigation_part2.content.json",
      "export_json_sha256": "02194ec3fee00d634bd4c25c5e4c1e24bd3cea5b6f87c10a38ddcff86490fa5b"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "de/legal_analysis.html",
      "language": "de",
      "title": "Ihre Bedingungen, Ihre Rechte – Das „Steam“-Dossier",
      "source_url": "https://phishdestroy.io/steam_dossier/de/legal_analysis",
      "source_html_sha256": "462e303ea53bd557b9f3ec0e8596eef6d3553daf99a269a5b5a315f02ab681d5",
      "exported_at": "2026-09-29T00:16:09.810Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "legal_analysis.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/de/legal_analysis.pdf?v=print-20260929-v5",
        "sha256": "37055676575fb603c57ed8c0c3a71ef62accee09cba9e0bc52c4287a22907ec9",
        "bytes": 109194,
        "pages": 8
      },
      "integrity": {
        "signed_object": "legal_analysis.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "legal_analysis.content.json.asc",
        "digest_file": "legal_analysis.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify legal_analysis.content.json.asc legal_analysis.content.json",
          "sha256sum -c legal_analysis.content.json.sha256"
        ]
      },
      "content": {
        "text": "Rechtlicher und wirtschaftlicher Bericht\nRechtliche Analyse – Nutzungsbedingungen und Einhaltung gesetzlicher Vorschriften\n\nIhre Bedingungen. Ihre Rechte.\n\nWAS DIESER ABSCHNITT BELEGT\n\nDiese forensische rechtliche Prüfung bewertet die vertragliche Asymmetrie zwischen der „Valve“ Corporation und den Nutzern von Steam in wichtigen Rechtsordnungen. Sie stellt fest, inwiefern die widerrufbare Abonnementlizenz den gesetzlich verankerten Eigentumsanspruch des Verbrauchers aufhebt, analysiert die Rechtsprechung des Europäischen Gerichtshofs zur Erschöpfung digitaler Weiterverkaufsrechte und prüft die Einhaltung des Digital Services Act (DSA) sowie des Artikels 15. des Gesetzes über den Schutz von Verbrauchern bei Online-Geschäften (GDPR). Die Analyse zeigt auf, wie automatisierte Durchsetzungsmechanismen ohne sinnvolle Einspruchsmöglichkeiten funktionieren, während Plattformgebühren systematisch wirtschaftlichen Wert aus jeder Peer-to-Peer-Transaktion abschöpfen.\n\n← Zurück zum Executive Briefing\n\nDieser Bericht enthält eine rechtliche, wirtschaftliche und technische Analyse der Diskrepanz zwischen den von „Steam“ erklärten Plattformregeln und der Situation der Verbraucher: automatisierte Durchsetzung mit geringen Rechtsbehelfen und umfassende Kontrolle des Unternehmens über digitale Vermögenswerte. Zahlenangaben sind mit ihrer Quelle versehen; sofern eine Zahl nicht auf eine Primärquelle zurückgeführt werden konnte, wurde sie weggelassen.\n\nVector 1\n\nErsetzung des „Eigentums“ durch eine widerrufbare Lizenz, sodass digitale Vermögenswerte im Rahmen der Vereinbarung entzogen werden können.\n\nVektor2\n\nAutomatisierte Durchsetzung (VACNet), deren Sperren laut „Steam Support“ nicht rückgängig gemacht werden können.\n\nVector 3\n\nKonto- und Vermögenskontrollen in Kombination mit einer 15% CS2-Marktgebühr (5% Steam + 10% Publisher-Gebühr), die bei jedem Weiterverkauf Wert aus dem Ökosystem entzieht.\n\nAsymmetrie der Vertragsbedingungen\nHaftungsausschluss und die widerrufbare Lizenz\n2.1 Das „Abonnement“-Modell im Vergleich zu Eigentumsrechten\n\nAbschnitt 2 der Steam-Abonnentenvereinbarung gewährt den Nutzern lediglich eine persönliche, nicht ausschließliche, nicht übertragbare und widerrufbare Lizenz. Gemäß der Vereinbarung kann Valve Konten jederzeit kündigen, und nicht genutzte Guthaben im Steam-Wallet können verfallen.\n\n2.2 Die Illusion der Rückerstattung vs. die EU-Verbraucherrechtsrichtlinie\nRechtlicher Rahmen\tRückerstattungsmechanismus\tEinschränkung\nEU Consumer Rights Directive\tUnconditional 14-day right of withdrawal on digital content\tWaived if download begins with explicit consumer consent\nSteam SSA\t14 days / under 2 hours played\tValve may deny at its discretion for \"abuse\"\nBeurteilung\n\nValve Die EU-14--Tage-Widerrufsfrist unterliegt einer eigenen Frist von „14-Tage / unter 2 Stunden“, die zum Zeitpunkt des Downloads akzeptiert werden muss, bevor das Produkt geprüft werden kann. Diese Regelung schränkt das gesetzliche Recht ein – sie erweitert es nicht; ob dies rechtmäßig geschieht, ist eine Frage für die zuständige Behörde und wird hier nicht als Schlussfolgerung behauptet.\n\nRechtsstreitigkeiten\nSekundärmarkt und Kartellrecht\nUFC Que Choisir gegen „Valve“ – Frankreich\n2019\nPariser Gericht: Die Rechtserschöpfungsdoktrin gilt für digitale Spiele – der Weiterverkauf ist rechtmäßig\nOkt. 2022\nDas Pariser Berufungsgericht hebt das Urteil auf\n23 Okt. 2024\nCour de cassation (Oberster Gerichtshof): Videospiele sind „komplexe Werke“ im Sinne der InfoSoc-Richtlinie und keine Software. Der digitale Weiterverkauf verboten. Valve setzt sich durch.\nWolfire Games-Kartellverfahren – Vereinigte Staaten (In re Valve Antitrust Litigation, Nr. 2:21-cv-00563)\n\nDie „Platform Most-Favored-Nation“-Klausel (PMFN) von Valve verbietet es Entwicklern, „Steam“-Schlüssel auf einer anderen Plattform günstiger zu verkaufen. Konkurrierende Shops – selbst solche, die im Gegensatz zu Valves „30%“ eine Provision von 12% erheben – dürfen die Einsparungen nicht an die Verbraucher weitergeben.\n\n336Gesamtzahl der Mitarbeiter von Valve (2021). Quelle: freigegebene Ermittlungsunterlagen.\n79Mitarbeiter, die die gesamte „Steam“-Plattform verwalten. Quelle: freigegebene Ermittlungsunterlagen.\n$3.5MNettoeinkommen pro Mitarbeiter. Quelle: freigegebene Ermittlungsunterlagen.\n\nAus den freigegebenen Ermittlungsunterlagen geht hervor, $8.5B Bruttoeinnahmen in 2021 336-Mitarbeiter. Das 79-Steam-Team bearbeitete die täglichen Support-Tickets von 373,000+, indem sie diese an ausgelagerte, automatisierte Callcenter weiterleitete.\n\nOFFENGELEGTE AKTENANLAGE · W.D. WASH. FALL 2:21-CV-00563Internes Memo zur Beweisaufnahme\n\nTim Sweeney (CEO, Epic Games) an Gabe Newell: „Warum behält Steam immer noch 30% des Bruttoumsatzes ein, obwohl die Zahlungsabwicklung 2–5% erfolgt und die Bandbreite CDN bei $0.002/GB liegt? Wenn man die Top-25-Spiele auf Steam abzieht, wette ich, dass Valve mit den meisten der folgenden 1,000 mehr Gewinn gemacht hat als die Entwickler selbst.“\n\nScott Lynch (COO, Valve Corporation) in einer internen Weiterleitung an Gabe Newell: „Bist du sauer, Alter?“\n\nWiderlegung der eidesstattlichen Aussage (Bloomberg, 2026): Gemäß der eidesstattlichen Aussage gemäß Regel 30(b) (1) sagte Gabe Newell aus, dass „Valve keine Richtlinie oder Praxis verfolgt, Drittanbietern von Software auf anderen Plattformen Preise vorzuschreiben.“ Die Kläger konfrontierten Newell mit internen Memos von Valve, die eine aktive Preiskontrolle sowie Drohungen mit der Streichung aus dem Angebot gegen Entwickler belegten, die in konkurrierenden Shops niedrigere Preise verlangten. Ende März 2026, wies das Bundesgericht den Antrag von „Valve“ auf ein summarisches Urteil zurück und verwies die Sammelklage der Entwickler von „32,000-“ an ein Geschworenenverfahren.\nNovember 2024\n\nSammelklage zugelassen für ~32,000 Entwickler die seit Januar 2017, Provisionen gezahlt haben sowie eine parallele Verbraucher-Sammelklage.\n\nGeltend gemachte Schadensersatzansprüche\n\n$3.1B\nDreifach nach US-Kartellrecht = $9.3B potenzielles Haftungsrisiko.\n\nIm Juni 2026: In einer neuen Klage wird behauptet, dass Microsoft und Valve eine Kartellvereinbarung getroffen hätten, um den Wettbewerb im Vertrieb von PC-Spielen zu unterbinden.\n\nFinanzkriminalität & Geldwäschebekämpfung – Offizielles Eingeständnis\nValve Offizielles Geständnis: Weltweite Liquidationen aufgrund von Betrug (28. Oktober 2019)\n\nAm 28. Oktober 2019, Valve stellte der Handel und der Weiterverkauf neu erworbener „Counter-Strike“-Container-Keys auf dem Marktplatz offiziell ein. In seiner offiziellen öffentlichen Bekanntmachung (blog.counter-strike.net/2019/10/26113) räumte die Valve Corporation schriftlich ein, dass die von ihr geschaffene virtuelle Wirtschaft zu einer internationalen Clearingstelle für Geldwäsche geworden sei:\n\n„In der Vergangenheit fanden die meisten von uns beobachteten Schlüsseltransaktionen zwischen legitimen Kunden statt. In jüngster Zeit nutzen jedoch weltweite Betrugsnetzwerke CS:GO-Schlüssel, um ihre Gewinne zu liquidieren. Derzeit wird davon ausgegangen, dass nahezu alle Schlüsselkäufe, die letztendlich auf dem Marktplatz gehandelt oder verkauft werden, aus betrügerischen Quellen stammen.“\n\nRegulatorischer Kontext: Dieses Eingeständnis folgte auf das formelle Ultimatum der Washington State Gambling Commission (WSGC) an „Valve“ sowie auf die im Juli 2016 erlassenen Unterlassungsanordnungen durch Karl Quackenbush, General Counsel der „Valve“, an die Skin-Glücksspiel-Domains von „23“ (einschließlich CSGO Lotto, CSGOLounge und OPSkins) – erst nachdem strafrechtliche Ermittlungen wegen Glücksspiels den Betrieb der Plattformen bedrohten.\n\nGerichtsbarkeit\nEin Rechteinhaber in Russland, der für den Nutzer unerreichbar ist\n\nDer Nutzungsvertrag stellt Valve als eine Partei dar, die kaum Verpflichtungen hat und von niemandem erreicht werden kann: Sperren sind dauerhaft, Einsprüche werden abgelehnt und der Zugang wird für ganze Gebiete mit einem einzigen Satz über „sanktionierte Regionen“ entzogen. Im Gegensatz zu dieser Haltung steht das Vorgehen von Valve, wenn die eigenen wirtschaftlichen Interessen in einer Rechtsordnung auf dem Spiel stehen, die das Unternehmen ansonsten als schwierig einstuft.\n\nValve v. Touch Skins – vorgerichtliche IP-Klage, Russland\n1 Sep. 2026\nValve über die russische Anwaltskanzlei Melling, Voitishkin & Partnersein vorgerichtliches Mahnschreiben an die Betreiber von Touch Skins, einem großen CS2-Skin-Tauschdienst, per russischer Post und per E-Mail ein vorgerichtliches Mahnschreiben.\nGründe\nDrei Gruppen mutmaßlicher Verstöße: Exklusivrechte an der Software; Rechte am Erscheinungsbild von Waffen-, Messer- und Handschuh-Skins; sowie die Marken von „Valve“. Das Verhalten der Betreiber wird als vorsätzlich und andauernd charakterisiert.\nForderung\nSofortige Einstellung des Betriebs und Löschung der gesamten Infrastruktur – des Quellcode, Websites und Social-Media-Seiten — andernfalls behält sich „Valve“ das Recht vor, vor einem russischen Gericht auf erheblichen Schadenersatz zu klagen und die Angelegenheit an die Strafverfolgungsbehörden zur strafrechtlichen Prüfung.\nErgebnis\nNach Erhalt des Schreibens kündigte die Plattform an, den Betrieb einzustellen. Dies gilt als erster Fall, in dem Valve in Russland rechtliche Schritte gegen einen Entwickler von Skin-Changern eingeleitet hat.\n\nBerichtet von dem Data-Miner Maxim „GabeFollower“ Poletaev (X, ~11, 2026. September) sowie der russischen Gaming-Presse. Es handelt sich hierbei um eine vorgerichtliche Forderung, nicht um eine eingereichte Klage; eine Aktenzeichen ist nicht öffentlich bekannt. Wird hier gemäß den Berichten behandelt, nicht als Gerichtsakte. Quellen: dota2.ru archiviert unter 2026-09-24 ↗ · Shazoo.\n\nDieselbe Gerichtsbarkeit, die andere Richtung\n\nValve ist dem russischen Rechts- und Regulierungssystem nicht fremd. Es hält sich an die Vorgaben von Roskomnadzor: Auf Verlangen der Aufsichtsbehörde wurden die Community-Seiten 260und Steam, die verbotene Inhalte enthielten, entfernt, und Roskomnadzor hat öffentlich erklärt, dass Steam die gesetzlichen Anforderungen erfüllt. Das russische „Landing“-Gesetz (Föderales Gesetz 236-FZ, in Kraft seit 2022) verlangt von großen ausländischen Internetplattformen, die russische Nutzer bedienen, eine lokale Präsenz sowie die Einrichtung eines Roskomnadzor-Ansprechpartners. Valve kommt sowohl den Löschanordnungen der Regulierungsbehörde nach als auch greift nun auf russische Rechtsberater zurück und droht mit russischen Gerichten, um seine Skins als geistiges Eigentum zu schützen.\n\nDie Plattform ist also erreichbar, handlungsfähig und setzt ihre Rechte genau dort durch, wo es um ihre Einnahmen geht. Der Kontrast besteht gegenüber den Nutzern: Ein zahlender Kunde in einer sanktionierten Region erfährt, dass die Beziehung beendet ist, der Zugang zur Community ist gesperrt, bis 2038, das Ticket geschlossen ist, und es gibt kein Forum, in dem die Entscheidung angefochten werden kann – „Sie waren mehr als glücklich, mein Geld anzunehmen und meine Transaktionen abzuwickeln“, wobei die Rückerstattung für dasselbe Konto von derselben iranischen IP-Adresse bereits ein Jahr zuvor genehmigt worden war (r/pcgaming, 4 Aug. 2026; weitere Mahnschreiben in der „Card-Economy“-Anlage). Valve setzt den gesamten Apparat eines nationalen Rechtssystems ein, um einen Skin zu verteidigen; dem Nutzer, der Skins gekauft hat, gewährt es keinerlei Rechtsweg.\n\nValve betrachtet dieselbe Gerichtsbarkeit als eine, in der es handeln und deren Vorschriften es einhalten kann, wann immer die Interessen von Valve auf dem Spiel stehen – russische Rechtsberater, die Androhung russischer Gerichte, die Befolgung von Löschanordnungen durch Roskomnadzor –, während es seine Verpflichtungen gegenüber den Nutzern dieses Marktes und aller anderen Märkte so behandelt, als lägen sie völlig außerhalb jeglicher Rechtsverfahren. Es ist ein Rechteinhaber, wenn es um seine Einnahmen geht, und eine unerreichbare Partei, wenn es um die Rechte der Nutzer geht.\n\nQuellen: TASS (RKN: „Steam“ hält sich an die Vorschriften) · Bundesgesetz „236-“ FZ.\n\nRechtlicher Opportunismus\nDie Kapitulation vor der Schiedsklausel\n2023 – der Angriff\n\nAnwaltskanzleien (Zaiger LLC, Mason LLP) warben über soziale Medien Tausende von Nutzern an und reichten gleichzeitig Zehntausende von individuellen Schlichtungsklagen ein.\n\nValves Belastung\n\n$225M+\nin nicht erstattungsfähigen Schiedsgerichtsgebühren, noch bevor ein Fall in der Sache verhandelt wurde. Berechnet gemäß den Verbraucher-Schiedsgerichtsregeln der American Arbitration Association (AAA) und den ergänzenden Anhängen für Massenschiedsverfahren. Die von Zaiger LLC und Mason LLP vertretenen Kläger reichten ~75,000 Einzelschlichtungsanträge gegen die Valve Corp. ein (parallel zu kartellrechtlichen Klagen in Wolfire Games LLC u. a. gegen Valve Corp., Aktenzeichen 2:21-cv-00563-JCC, W.D. Wash.). Gemäß den AAA-Gebührenordnungen für Verbraucher zahlt der beklagte Unternehmer nicht erstattungsfähige Verwaltungsgebühren und Kautionen für die Ernennung von Schiedsrichtern in Höhe von ca.3,000+ pro Einzelfall (75,000 Einreichungen × $3,000 = ca. $225Mio. an im Voraus zu entrichtenden Verfahrenskosten). Siehe die Rechtsberichte von Bloomberg Law und Reuters zum Risiko von Massen-Schiedsverfahren in der Tech-Branche (2023–2024).\n\nZeitraum\tSSA-Streitbeilegungsmechanismus\tBeobachtete Auswirkung\tErgebnis\nBefore Sep 2024\tMandatory individual arbitration + class-action waiver\tIndividual litigation becomes economically irrational for users\tMass arbitration → $225M fee threat\nAfter Sep 2024\tDisputes in King County, WA courts only\tArbitration costs are avoided; cases consolidate in a single forum\tClass actions now possible\nSchlussfolgerung\n\nÜber zehn Jahre lang verlangte die SSA von den Nutzern, auf ihr Recht auf ein Schwurgerichtsverfahren zugunsten eines individuellen Schiedsverfahrens zu verzichten. Nachdem die massenhaften Schlichtungsanträge diesen Mechanismus für „Valve“ finanziell unerschwinglich gemacht hatten, wurde die SSA dahingehend geändert, dass Streitigkeiten nun an die Gerichte von King County weitergeleitet werden. Die Änderung wurde ohne eine sinnvolle Opt-out-Möglichkeit eingeführt; die Alternative zur Zustimmung bestand darin, durch die Löschung des Kontos den Zugriff auf erworbene digitale Inhalte zu verlieren.\n\nAlgorithmische Durchsetzung\nVACNet, Schuldvermutung und Fehlalarme\nOktober 2023 – AMD Anti-Lag+\n\nEin AMD-Treiber-Update (v23.10.1) aktivierte „Anti-Lag+“ in CS2, wodurch DLL-Funktionen des Spiels abgefangen wurden. VAC stufte dies als Einfügen von Cheat-Code ein und verhängte dauerhafte Sperren gegen Tausende legitimer Nutzer, bevor Valve eingriff.\n\nDezember 2023 – hohe DPI\n\nSpieler mit einer DPI-Einstellung über 10,000, die die Kamera blitzschnell drehten, erhielten eine dauerhafte Sperre. VACNet konnte physische Mausbewegungen nicht von einem „Spinbot“-Cheat unterscheiden.\n\nSupport-Kategorie\tAngegebene Reaktionszeit\tTatsächliches Ergebnis\nRefund requests\t50 min – 1.5 hr\tAutomatic approval (<14 days, <2 hours played)\nAccount security / recovery\t3–12 hours\tDepends on documentation provided\nContesting a VAC ban\tForm response\tComplete refusal. Support cannot reverse VAC decisions. The ban is permanent.\nOffizielle Richtlinie von Valve\n\n„VAC-Sperren sind dauerhaft, nicht verhandelbar und können vom Steam-Support nicht aufgehoben werden.“\n\nDer gleiche Supportkanal, der die Sperre verhängt, lehnt auch eine Überprüfung ab: Der Steam-Support erklärt, dass er eine VAC-Entscheidung nicht rückgängig machen kann. Für den Nutzer ist das Urteil des Algorithmus das maßgebliche Ergebnis.\n\nÖkonomie des Weiterverkaufs\nKontrolle über virtuelle Vermögenswerte und die Wiederverkaufsgebühr\nDie 15%-CS2-Marktgebühr – Wert, der bei jedem Weiterverkauf abgezogen wird\nIteration\tGuthaben des Käufers\tDer Verkäufer erhält\tVerbrannt (15%)\n1\t$100.00\t$85.00\t$15.00\n2\t$85.00\t$72.25\t$12.75\n3\t$72.25\t$61.41\t$10.84\n10\t$23.16\t$19.68\t~$3.47\nTotal\t$100 → dust\tValve collects the 15% fee on each resale. Users must add new money to keep trading.\nÄnderung der CS2-Trade-up-Regeln – Oktober 2025\n\nOhne Vorankündigung änderte Valve die Regeln für CS2-Trade-Up-Verträge, um den garantierten Erwerb seltener Messer und Handschuhe im Tausch gegen Gegenstände der Covert-Qualität zu ermöglichen. Die Messerpreise fielen, die Preise für Covert-Gegenstände stiegen stark an, und es kam zu Panikverkäufen auf dem gesamten Markt.\n\nValve beruft sich auf Abschnitt 7 der SSA – keine Haftung für Änderungen der Plattformregeln. Die Nutzer tragen das Risiko in einer Wirtschaft, deren Regeln Valve sich ohne Vorankündigung oder Entschädigung ändern können. Die Höhe des gemeldeten marktweiten Verlusts ist umstritten und wird hier ohne Angabe einer Primärquelle nicht genannt.\n\nReaktion der europäischen Regulierungsbehörden\nUOKiK, DSA und das Gesetz zur digitalen Fairness\nUOKiK – Polen, Mai 2024\n\nDie polnische Kartellbehörde (UOKiK) leitete ein formelles Kartellverfahren gegen die Valve Corporation und fünf inländische Spielehersteller/-vertreiber wegen angeblicher Preisabsprachen, wettbewerbsbeschränkender Preisparitätsklauseln und Geoblocking-Praktiken ein, die dazu führten, dass polnische Verbraucher bis zu 20% mehr für digitale Spiele zahlten als Verbraucher in benachbarten EWR-Märkten. Im Rahmen der kartellrechtlichen Untersuchung führten Inspektoren der UOKiK und Polizeibeamte Razzien und Beweissicherungen in den polnischen Niederlassungen einheimischer Partnerverlage und -vertriebe durch (nicht in Zweigstellen vValve, da „Valve“ keine polnische Niederlassung unterhält). Mögliche gesetzliche Geldbuße: bis zu 10% des Jahresumsatzes. Quelle: Offizielle Mitteilung der UOKiK, „Prezes UOKiK wszczął postępowanie przeciwko Valve i twórcom gier“, 2024.\n\nDigital Services Act (DSA)\n\nVerlangt Transparenz bei der automatisierten Moderation. Steam veröffentlicht keine Daten zu „False Positives“ und „False Negatives“ für VACNet, und im Support-Kanal heißt es, dass VAC-Entscheidungen nicht rückgängig gemacht werden können.\n\nDigital Fairness Act – 2026\n\nErwartete Bestimmungen: dauerhafter Zugang zu kostenpflichtigen Inhalten, Verbot von „Dark Patterns“ bei der Verzichtserklärung, Anerkennung von Eigentumsrechten an digitalen Vermögenswerten und Schutz vor dauerhafter Beschlagnahmung von Beständen.\n\nSchlussfolgerung\nDokumentierte Diskrepanzen zwischen den Vorschriften und der Praxis\n1\n\nDie Eigentumslücke. Nutzer zahlen den vollen Preis für eine Lizenz, die Valve laut Vereinbarung widerrufen darf. Der französische Oberste Gerichtshof (Okt. 2024) entschied, dass der digitale Weiterverkauf nicht geschützt ist, und verankerte diese Position gesetzlich.\n\n2\n\nAlgorithmische Durchsetzung. VACNet hat ungerechtfertigte Sperren verhängt (AMD-Treiber, Vorfälle mit hoher DPI). Der „Steam“-Support erklärt, dass er eine VAC-Entscheidung nicht rückgängig machen kann, sodass der Algorithmus das maßgebliche letzte Wort hat.\n\n3\n\nGebührenpolitik. Die Marktgebühr von 15% für CS2 (5% Steam + 10% Publisher-Gebühr) mindert den Wert bei jedem Weiterverkauf, und die Plattformregeln können ohne Vorankündigung geändert werden; Valve lehnt gemäß der SSA jegliche Haftung für solche Änderungen ab.\n\n4\n\nSchlichtungsklausel gestrichen. Die SSA hat im September 2024, die obligatorische Schlichtung abgeschafft, nachdem Massenklagen Valve Gebühren in Höhe von ca. $225M auferlegt hatten. Den Nutzern wurde keine sinnvolle Möglichkeit geboten, sich von dieser Änderung abzumelden.\n\n5\n\nSelektive Gerichtsbarkeit. Valve Valve beauftragte einen russischen Anwalt (Melling, Voitishkin & Partners) und drohte mit russischen Gerichtsverfahren gegen Touch Skins, während es gleichzeitig seine Verpflichtungen gegenüber Nutzern desselben Marktes als außerhalb jeglichen gerichtlichen Verfahrens stehend behandelte. agiert als Rechteinhaber, wenn seine kommerziellen Interessen betroffen sind, und als unerreichbare Partei, wenn es um die Rechte der Nutzer geht.\n\n← Teil I: Proxy-Umgehung & GlücksspielTeil II: Zugang & Rechenschaftspflicht →\n\nRechtsquellen und Fallakten werden unter Angabe ihrer ursprünglichen Herausgeber und Aufbewahrungsorte zitiert. Es wird kein Anspruch auf das Eigentum an den zugrunde liegenden Dokumenten erhoben.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Rechtliche Analyse – Nutzungsbedingungen und Einhaltung gesetzlicher Vorschriften"
          },
          {
            "level": 2,
            "id": null,
            "text": "Haftungsausschluss und die widerrufbare Lizenz"
          },
          {
            "level": 3,
            "id": null,
            "text": "2.1 Das „Abonnement“-Modell im Vergleich zu Eigentumsrechten"
          },
          {
            "level": 3,
            "id": null,
            "text": "2.2 Die Illusion der Rückerstattung vs. die EU-Verbraucherrechtsrichtlinie"
          },
          {
            "level": 2,
            "id": null,
            "text": "Sekundärmarkt und Kartellrecht"
          },
          {
            "level": 3,
            "id": null,
            "text": "UFC Que Choisir gegen „Valve“ – Frankreich"
          },
          {
            "level": 3,
            "id": null,
            "text": "Wolfire Games-Kartellverfahren – Vereinigte Staaten (In re Valve Antitrust Litigation, Nr. 2:21-cv-00563)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve Offizielles Geständnis: Weltweite Liquidationen aufgrund von Betrug (28. Oktober 2019)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Ein Rechteinhaber in Russland, der für den Nutzer unerreichbar ist"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve v. Touch Skins – vorgerichtliche IP-Klage, Russland"
          },
          {
            "level": 3,
            "id": null,
            "text": "Dieselbe Gerichtsbarkeit, die andere Richtung"
          },
          {
            "level": 2,
            "id": null,
            "text": "Die Kapitulation vor der Schiedsklausel"
          },
          {
            "level": 2,
            "id": null,
            "text": "VACNet, Schuldvermutung und Fehlalarme"
          },
          {
            "level": 2,
            "id": null,
            "text": "Kontrolle über virtuelle Vermögenswerte und die Wiederverkaufsgebühr"
          },
          {
            "level": 3,
            "id": null,
            "text": "Die 15%-CS2-Marktgebühr – Wert, der bei jedem Weiterverkauf abgezogen wird"
          },
          {
            "level": 3,
            "id": null,
            "text": "Änderung der CS2-Trade-up-Regeln – Oktober 2025"
          },
          {
            "level": 2,
            "id": null,
            "text": "UOKiK, DSA und das Gesetz zur digitalen Fairness"
          },
          {
            "level": 2,
            "id": null,
            "text": "Dokumentierte Diskrepanzen zwischen den Vorschriften und der Praxis"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/de/#briefing-heading",
          "https://dota2.ru/news/67707-valve-cerez-uristov-napravila-krupnoj-rossijskoj-skincendzer-platforme-trebovanie-o-prekrasenii-deatelnosti/",
          "http://web.archive.org/web/20260924181657/https://dota2.ru/news/67707-valve-cerez-uristov-napravila-krupnoj-rossijskoj-skincendzer-platforme-trebovanie-o-prekrasenii-deatelnosti/",
          "https://shazoo.ru/2026/09/12/190508/valve-cerez-rossiiskix-iuristov-dobilas-zakrytiia-krupnogo-skinceindzera-dlia-cs2",
          "https://www.reddit.com/r/pcgaming/comments/1vf24lu/warning_to_all_gamersexpats_steam_took_my_money/",
          "https://phishdestroy.io/steam_dossier/de/card_economy.html#asymmetry",
          "https://tass.ru/obschestvo/23235387",
          "https://base.garant.ru/401414628/",
          "https://uokik.gov.pl/postepowanie-wyjasniajace-w-sprawie-valve-i-dystrybutorow-gier",
          "https://phishdestroy.io/steam_dossier/de/",
          "https://phishdestroy.io/steam_dossier/de/investigation_part2.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/de/legal_analysis.content.json",
      "export_json_sha256": "095d4532d626a360fbee7e31c63b02cdcd3f374ba4027345f629c7bac51ad522"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "de/license_disclaimer.html",
      "language": "de",
      "title": "Lizenz · Rechte · Haftungsausschluss — PhishDestroy",
      "source_url": "https://phishdestroy.io/steam_dossier/de/license_disclaimer",
      "source_html_sha256": "9a2232e48d3105c47027554a747077a5a770e12d43727596bba24fe8cfbcd8bc",
      "exported_at": "2026-09-29T00:16:10.163Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "license_disclaimer.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/de/license_disclaimer.pdf?v=print-20260929-v5",
        "sha256": "bce3856711784ac196f222ee4e738dad1be50f1d2e20089f27965712c432a68e",
        "bytes": 123885,
        "pages": 11
      },
      "integrity": {
        "signed_object": "license_disclaimer.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "license_disclaimer.content.json.asc",
        "digest_file": "license_disclaimer.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify license_disclaimer.content.json.asc license_disclaimer.content.json",
          "sha256sum -c license_disclaimer.content.json.sha256"
        ]
      },
      "content": {
        "text": "PHISHDESTROYForensische Untersuchung · Valve / Steam\nLizenz · Rechte · Haftungsausschluss\nLizenz & Rechtlicher Hinweis – Widmung als Public Domain\n\nAlle Rechte werden der Menschheit überlassen.\n\nWAS DIESER ABSCHNITT BELEGT\n\nDieses Dokument legt die bedingungslose Widmung zur Gemeingut-Nutzung (CC0 1.0 Universal) sowie die MIT-Softwarelizenzbedingungen fest, die für das Dossier „PhishDestroy“ (Steam) gelten. Alle forensischen Befunde, Beweisdatensätze, Netzwerkgraphen und Analysemethoden werden unwiderruflich der Gemeingut-Nutzung zugeführt und stehen weltweit für uneingeschränkte regulatorische, rechtliche und akademische Zwecke zur Verfügung.\n\n← Zurück zum Executive Briefing\n\nPhishDestroy Wir verzichten auf jegliche Rechte an diesem Material – Sie dürfen es reproduzieren, verkaufen und mit Ihrem Namen versehen. Was folgt, sind zwei Dokumente, die in einer Stimme verfasst sind: ein offener Brief an Valve, geschrieben in unserer üblichen Sprache, und eine formelle Verzichtserklärung, die für die Behörde verfasst wurde, die den Inhalt weiterverfolgen wird.\n\nUntersuchung · Valve Corporation / SteamÖffentliche Fassung – keine Gültigkeitsdauer, kein Widerruf\nVERZICHTET\nAbschnitt ILizenz — der eigentliche rechtliche Teil, aber menschlich ausgedrückt\n\nPhishDestroy verzichte auf jegliches Recht an diesem Material. Null. Weg. Erledigt. Du kannst es vervielfältigen, verkaufen, deinen Namen darauf setzen, es deinem Chef tätowieren – was auch immer. Keine Nennung erforderlich, keine DM nötig, keine Dankeskarte erwartet.\n\nEine einzige Regel (ja, wirklich nur eine)\n\nDU darfst NICHT entscheiden, ob du ein Terrorist bist.\n\nWenn du ein Nutzer aus Russland oder einem anderen von der OFAC sanktionierten Land bist – dieses Material ist NICHT für dich bestimmt. Keine Schlupflöcher. Viel Spaß mit deinen Sanktionen.\n\nUnd falls du deine „Steam“-Region auf die Türkei umgestellt hast, während du in Moskau sitzt – herzlichen Glückwunsch zu deiner kreativen Geografie. Du bist immer noch Russe. Die Sanktionen gelten weiterhin. Genau darum geht es.\n\nAbschnitt IIWas das ist und warum es existiert\n\nWir werden mehr über „Valve“ veröffentlichen, als ein durchschnittlicher „Valve“-Mitarbeiter über sich selbst weiß. Das ist keine Prahlerei. Das ist einfach das Ergebnis unserer Arbeit.\n\nWie sind wir hierhergekommen? Eine lustige Geschichte: „Steam“ hat uns im Grunde genommen erschaffen. Es hat uns mit seinen Betrügern, seinen Support-Tickets und seinem Ökosystem zur Umgehung von Sperren großgezogen – und nun sind wir hier. Nichts für ungut. Eigentlich sogar poetisch.\n\nFür alle, die die Entstehungsgeschichte noch nicht gelesen haben – wir haben bereits die extrem teuren europäischen Anwälte von Valve kennengelernt (Taylor Wessing, da ihr gefragt habt):\n\nhttps://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d 2026-08-21 im Archiv ↗\n\nEine reizende Begegnung. Vor allem angesichts ihres Stundensatzes.\n\nWusste „Valve“ davon? Ja. Wusste Taylor Wessing davon? Mit ziemlicher Sicherheit ja. Aber wenn man so reich ist, sind Gesetze eher eine Stimmungssache als eine Verpflichtung, oder?\n\nDas ist eigentlich schon die ganze Antwort.\n\nSteam Wir haben jahrelang Betrüger „gepflegt“. Nicht immer absichtlich – manchmal gerieten Betrüger einfach durch ihre Verbindungen in den Einflussbereich vValve. Wir wollen das nicht dramatisieren. Wir wollen präzise sein. Das fällt uns ehrlich gesagt schwerer als zu dramatisieren – so schreiben wir nun einmal.\n\nIst das ein Konflikt?\n— Nein.\n\nLässt er sich lösen?\n— Ja. Aber wir unterzeichnen keine Geheimhaltungsvereinbarung und machen kein Bug-Bounty-Programm für ein paar Cent mit.\n\nWir haben über 4 Jahre darauf gewartet, dass sie das Spoofing-Problem beheben, bevor wir öffentlich darüber schreiben konnten. Denn hätten wir früher darüber geschrieben, hätte Steam seine kleine Opfermaske aufgesetzt, „aktive Bedrohung!“ geschrien und uns Kleingeld angeboten, damit wir ein Dokument unterschreiben, das uns für immer zu ihrem rechtlichen Eigentum gemacht hätte. Nein, danke.\n\n(Außerdem: Valve verstößt selbst gegen die Geheimhaltungsvereinbarung. Ihre eigenen Mitarbeiter tun das. Die ganz oben. Aber klar, reden wir lieber über unsere.)\n\nAbschnitt IIIOffener Brief an Valve – im Ernst, lies das hier\n\nValve: Wenn ihr wollt, dass diese Domain abgeschaltet wird, schickt uns eine E-Mail. Für dieses Gespräch ist kein externer Rechtsbeistand erforderlich.\n\nFür Uneingeweihte: Dr. Patrick hat einen Master of Laws in internationalem Handelsrecht von der University of Aberdeen und – haltet euch fest – hat seine Doktorarbeit buchstäblich im IT-Recht abgeschlossen. Er wurde kürzlich zum Partner bei Taylor Wessing ernannt, einer Kanzlei, deren gesamtes Geschäftsmodell darin besteht, Unternehmen wie Valve unverschämt hohe Summen in Rechnung zu stellen, um die Dinge so lange hinauszuzögern, bis der Gegenseite das Geld oder die Geduld ausgeht.\n\nWir nehmen es ihm nicht übel. Reiche, schuldige Mandanten, die nach Stunden bezahlen – ein solider Karriereschritt. Wir finden nur, dass Sie das nicht finanzieren sollten.\n\nDas Angebot (offenes Angebot, keine Anwälte erforderlich)\n\nDie Domain ist das Einzige, was „Valve“ realistisch erreichen kann. Die Ermittlungen, die Hinweise und die damit verbundenen Ressourcen sind bereits in Gang – sie laufen mit oder ohne die Domain weiter.\n\nWenn Sie die Domain haben möchten:\n\nLassen Sie Ihre IT-Rechtsexperten einen fairen Preis festlegen.\n\n50% geht an die „SEAL“-Stiftung.\n\nWir löschen die Domain. Kein Drama. Kein Gericht. Erledigt.\n\nDas ist keine Drohung. Es ist ein klares Angebot für das Einzige, was tatsächlich in Reichweite ist. Auf andere Weise werden Sie es nicht bekommen – so ist nun einmal die Situation.\n\nWerden wir Valve direkt „schaden“? Wahrscheinlich nicht in einer Weise, die sie finanziell spüren werden. Wir machen uns keine Illusionen. Aber wir werden es ehrlich und offen tun, ohne nach Einfluss zu streben – denn wir brauchen keinen Einfluss. Wir wollen, dass die Welt sieht, was schon immer öffentlich sichtbar war, wenn man nur lange genug hinschaute.\n\nWir verfügen über ein5e Jahre an Archivmaterial. Was die Anwälte von „Valve“ im Rahmen der Beweisaufnahme vorgelegt haben – die Daten, die die Ermittler einsehen können, die Fingerabdrücke, die Papierspuren, die sie uns buchstäblich ausgehändigt haben –, reicht aus. Wir müssen das Material nicht unbearbeitet veröffentlichen.\n\nWer bekommt was\n\nDie Aufsichtsbehörden erhalten die Originale.\n\nForscher und Journalisten erhalten geschwärzte Versionen (Opferberichte, Anmeldedaten von Kindern und die charmanten Kommentare des „Valve“-Supports wurden aus offensichtlichen Gründen entfernt).\n\nUnter den betroffenen Konten befanden sich auch Minderjährige, die nicht benachrichtigt wurden. Diese Erkenntnis ist im Paket für die Aufsichtsbehörden enthalten, wobei die Opferberichte und Zugangsdaten entfernt wurden, da sie eher vor eine Datenschutzbehörde als in einen Artikel gehören.\n\nAußerdem, „Valve“ – wir möchten eines klarstellen, bevor ihr entscheidet, wie ihr damit umgeht: „PhishDestroy“ ist eine Community, keine Person. Das habt ihr gelernt, als ihr rechtliche Korrespondenz an die Community gerichtet habt, ohne euch die Mühe zu machen, mit der Community zu sprechen – ihr habt sie einfach nur für Daten ausgenutzt und die Konten gesperrt.\n\nDie Community hat keinen Konflikt mit Valve. Wir haben das nicht gesucht. Die Betrüger, die ihr großgezogen habt, haben uns gefunden. Wir haben sie gesperrt. Und hier sind wir nun.\n\nAbschnitt III-BDie verbündeten Ressourcen – ein Hinweis speziell an Steam\n\nWir möchten offen über die Verbreitungsstruktur sprechen, denn so zu tun, als gäbe es sie nicht, wäre unehrlich.\n\nPhishDestroy verfügt nach unserem Verständnis der Situation in der Community über mindestens zwei verbündete Ressourcen, die dieses Material aufgreifen und weiterverbreiten werden.\n\nWas das in der Praxis bedeutet:\n\nSie beleuchten überlappende Themen aus ihren eigenen Blickwinkeln.\n\nSie sind unabhängig – sie lassen sich nicht von uns leiten, und wir lassen uns nicht von ihnen leiten. Gleiches allgemeines Thema, unterschiedliche Methodik.\n\nSie werden NICHT auf Part 1. aktiv werden. Sie beobachten die Lage.\n\nFalls Valve beschließt, die Website nicht zu schließen:\n\nist damit zu rechnen, dass sie nach Teil 2 oder Teil 3. in Erscheinung treten\n\nSie werden das Nützliche aus unserer Arbeit übernehmen, es mit ihren eigenen Beiträgen ergänzen und unter ihrem eigenen Namen veröffentlichen.\n\nGenau für solche Fälle ist die Lizenz in Abschnitt 1 gedacht: Das Material gelangt dorthin, wo es gebraucht wird, wird ergänzt, wird erweitert – und weder wir noch sie sind einander eine Namensnennung schuldig.\n\n(PS für Juristen, die sich über Haftungsketten Gedanken machen: Es gibt keine. Diese Quellen erhalten weder unsere Anweisungen noch unsere Finanzierung oder unsere Daten. Sie lesen, was öffentlich zugänglich ist, und ziehen ihre eigenen Schlussfolgerungen. Genau wie Sie es tun könnten.)\n\nWir sagen das nicht, um einzuschüchtern. Wir sagen es, damit derjenige, der auf Seiten von „Valve“ die Strategie festlegt, genaue Informationen darüber hat, wie die Informationslandschaft tatsächlich aussieht.\n\nEine Quelle, die unser Material aufgreift und ergänzt, wäre ein Artikel. Zwei Quellen, die dies unabhängig voneinander tun und zu ähnlichen Schlussfolgerungen gelangen, bilden ein Muster. Muster sind es, die den Regulierungsbehörden auffallen.\n\nAbschnitt IVDas Geld, die Verbote, der ganze Zirkus\n\nDie Sache mit dem Verbot von Glücksspielseiten und Betrügern durch „Steam“ ist folgende: Es geht nicht um Durchsetzung. Es geht um die Erzielung von Einnahmen. „Valve“ steckt das Geld ein, wäscht sich die Hände rein, betritt dann die Bühne und erzählt allen eine heilsame Geschichte über Pokémon-Karten und Baseball.\n\nWo Kompromisse auf Seiten des Supports dokumentiert sind – einschließlich des schriftlichen Eingeständnisses von Valve im Februar, dass 2023 die Verantwortung für kompromittierte Hochwertkonten durch Hilfeanfragen übernimmt, sowie der Entlassungen von Mitarbeitern von Auftragnehmern, über die Dexerto und Escorenews im Anschluss an den Insiderhandel in Höhe von320k berichteten (Teil II §04 · Hauptdossier §14.1) – stützen sich auf veröffentlichte Eingeständnisse und investigative Berichterstattung. Unbegründete Gerüchte, wonach Support-Mitarbeiter nebenbei Glücksspiele betreiben oder Provisionen für die Aufhebung von Sperren kassieren, sind öffentlich nicht belegt und werden hier nicht berücksichtigt.\n\nUnterdessen hat Valve die Möglichkeit zunichte gemacht, Skins ordnungsgemäß zu verfolgen: 2017.. Sie haben das sogar in ihren eigenen Foren diskutiert. Sie nannten es „Maßnahmen gegen Glücksspiel“ – während das Ökosystem des Skin-Glücksspiels noch Jahre danach Milliarden über die Infrastruktur von Steam weiterleitete. Tolles Branding.\n\nWir werden beweisen, dass:\n\nSkins sind anonymer als Monero\n\nEin peruanisches Kartell soll Dota-2-Skins für Geldtransfers genutzt haben\n\nSteam ist praktisch eine Maschine zur Umgehung von Sanktionen im Wert von ~7B in „Sammelkarten“ (ja, sie haben gegenüber einem Staatsanwalt tatsächlich von Sammelkarten gesprochen)\n\nWir haben ein Video zu dieser Skin-Sache. Ihr werdet es sehen.\n\nAußerdem wissen wir:\n\nDie Moderation auf Reddit wird von „Valve“ beeinflusst\n\nDie Dateninfrastruktur von Drittanbietern von „Steam“ (wie z. B. steamid.uk) wird von einer Privatperson betrieben (msart), deren verbundenes Schwesterprojekt mit einer Sperrliste (steambans.com Archiv) von einem bestätigten Moderator der „Valve“-Community (killahinstinct_) – wodurch die unabhängige Überprüfung von Plattform-Sperren vollständig im Einflussbereich von „Valve“ verbleibt (siehe Kartenwirtschaft §08)\n\nWas sie nicht kontrollieren können, sperren sie\n\nValve: Wenn du dich weiterhin dumm stellst – ist das in Ordnung. Dein sicherer Hafen ist vermerkt. Google Analytics anonymisiert die IP-Adressen deiner Nutzer ohnehin. Wir sehen, was gelöscht wird. Wir können es nur nicht kostengünstig genug beweisen, damit es deine Anwälte interessiert. Noch nicht.\n\nAbschnitt VDie Malware-Sache – ja, wir erwähnen es\n\nLassen Sie uns den Ablauf der Ereignisse ganz unverblümt darlegen, denn er enthüllt genau, wer Sie sind.\n\nWir geben die Sicherheitslücke im Spiel NICHT öffentlich bekannt. Wir melden sie NICHT an „Steam“. Das Programm verlangt eine Vertraulichkeitsvereinbarung, und deren Unterzeichnung würde uns daran hindern, den betroffenen Nutzern mitzuteilen, was mit ihren Konten passiert ist. Die Offenlegung gegenüber den Betroffenen, deren Konten verloren gingen, sowie gegenüber den Aufsichtsbehörden ist der Sinn dieser Arbeit; eine Vertraulichkeitsvereinbarung ist damit unvereinbar.\n\nFolgendes ist tatsächlich passiert: Diese Sicherheitslücke ist in den richtigen Kreisen praktisch ein offenes Geheimnis. Wir wissen mit Sicherheit, dass unabhängige Sicherheitsforscher den vollständigen Exploit dem „Steam“-Support bereits direkt unter die Nase gerieben haben. Dieser Teil ist erledigt. Ihr wurdet über eure eigenen sterilen Kanäle offiziell gewarnt.\n\nUnd was hat „Valve“ getan? Absolut nichts. Denn für „Valve“ ist Sicherheit nicht gleichbedeutend mit Gewinn – im Gegenteil, es ist genau das Gegenteil. Sicherheit ist ein Kostenfaktor. Solange eine Bedrohung nicht eine kritische Masse erreicht und einen katastrophalen PR-Zusammenbruch in der Öffentlichkeit verursacht, behandelt „Valve“ sie nicht als dringlich.\n\nWas tun wir also? Wir machen die Öffentlichkeit darauf aufmerksam, denn „Valve weiß von einer systemischen Malware-Bedrohung und entscheidet sich bewusst dafür, nichts zu unternehmen“ ist ein entscheidender Hinweis für die Aufsichtsbehörden, die dies gerade lesen.\n\nDas Spiel ist riesig. Wir nennen es hier nicht beim Namen. Aber man muss Folgendes verstehen:\n\nDas ist NICHT der belanglose CS:GO-Script-Kiddie-Mist, bei dem ein Server euch auffordert, „einen Treiber zu installieren“. Das hier ist katastrophal.\n\nDas ist ein Albtraum auf „Unturned“-Niveau: Zero-Click-RCE bei der Serververbindung. Du trittst einem Server bei. Du klickst auf gar nichts. Du lädst nichts herunter. Die Verbindung selbst ist die Angriffsfläche, und dein Rechner ist vollständig kompromittiert. Seien wir mal ehrlich: Ein RCE zu platzieren und lokale Antivirenprogramme zu umgehen, indem man sich auf die vertrauenswürdigen digitalen Zertifikate von Valve aufschwingt, ist auf Steam nicht einmal mehr eine Neuheit. Es ist praktisch eine integrierte Funktion deines Ökosystems.\n\nValve weiß bereits, dass es das gibt. Aber sie verlassen sich auf ihre bevorzugte, feige rechtliche Lücke: Da das Spiel technisch gesehen von einem Drittanbieter entwickelt wurde, wäscht Valve seine Hände in Unschuld. Sie vertreiben das Spiel, wickeln die Zahlungen ab, hosten die Infrastruktur – doch wenn ein Zero-Click-RCE Millionen ihrer Nutzer bedroht, lautet ihre Haltung: „Nicht unser Spiel, nicht unsere Haftung.“\n\nWenn dies unweigerlich eskaliert, wird der Drittentwickler den Kopf hinhalten müssen, und Valve wird sich aus der Affäre ziehen und so tun, als sei es die verantwortungsbewusste Plattform, die bei der Lösung des Problems „mitgeholfen“ hat. Klassische Valve-Feigheit. Wir kennen das Drehbuch.\n\nWir halten dies offiziell fest, damit Aufsichtsbehörden, Staatsanwälte und Journalisten genau verstehen, wie Valve mit aktiver Malware umgeht: indem es sich hinter Drittentwicklern versteckt, Geheimhaltungsvereinbarungen (NDAs) einsetzt und die Spieler schutzlos zurücklässt.\n\nEnde des offenen BriefesBeginn des formellen Protokolls\nFormelles Protokoll · für die Behörde\nErklärungIn Bezug auf Nutzung und Rechte\n\nPhishDestroy Projekt & Cybersicherheitskoalition\n\nDiese Erklärung liegt jeder Einreichung und jedem Anlagenstück in diesem Unterlagenpaket bei. Sie richtet sich an alle Behörden, Gerichte, Aufsichtsbehörden, Staatsanwälte, Forscher, Journalisten oder betroffenen Personen, in deren Hände das Material gelangt.\n\n1. Es bestehen keine Nutzungsbedingungen\n\n1.1 Das gesamte von der Koalition im Rahmen dieser Vorlage erstellte Material – die Sachverhaltsdarstellungen, die Analysen, die von ihr verfassten Anlagen, die Tools und die Ergebnisse – wird OHNE VORBEHALT IRGENDER RECHTE freigegeben.\n\n1.2 Jeder darf, ohne uns zu fragen und ohne uns zu benachrichtigen:\n\nes ganz oder teilweise vervielfältigen;\n\nes anpassen, bearbeiten, umschreiben, umstrukturieren oder korrigieren;\n\nes übersetzen;\n\nAuszüge daraus verwenden, ohne darauf hinzuweisen, dass es sich um Auszüge handelt;\n\nes in amtliche Dokumente, Feststellungen, Entscheidungen, Schriftsätze, Berichte oder Pressematerial einarbeiten;\n\nes als eigenes Werk oder eigene Erkenntnisse des Empfängers darzustellen;\n\nes als Ausgangsmaterial verwenden und den Rest verwerfen;\n\nund es unter denselben Bedingungen an Dritte weitergeben.\n\n1.3 EINE QUELLENANGABE IST NICHT ERFORDERLICH UND WIRD AUCH NICHT VERLANGT. Die Koalition muss weder namentlich genannt, zitiert, gewürdigt, gedankt, konsultiert noch informiert werden. Wenn Material aus dieser Empfehlung einer Behörde hilft und die Koalition dabei nie erwähnt wird, IST DAS EIN VÖLLIG ZUFRIEDENSTELLENDES ERGEBNIS, und die Koalition erklärt dies im Voraus, damit die Frage gar nicht erst aufgeworfen werden muss.\n\n1.4 Sollte eine Behörde es hingegen für zweckmäßiger erachten, die Koalition als Quelle anzugeben, steht es ihr frei, dies zu tun. Die Entscheidung liegt ganz beim Empfänger, und keine der beiden Vorgehensweisen hat irgendwelche Konsequenzen.\n\n1.5 Dies ist ein VERZICHT, kein Lizenzangebot. Er bedarf keiner Annahme, begründet keine Verpflichtung und kann nicht verletzt werden. Von der Koalition veröffentlichte Software wird separat unter der MIT-Lizenz freigegeben; die Forschungsergebnisse und Erkenntnisse werden im größtmöglichen zulässigen Umfang der Öffentlichkeit zugänglich gemacht, und sofern eine Rechtsordnung keinen Verzicht zulässt, gewährt die Koalition eine unwiderrufliche, weltweite, gebührenfreie Lizenz mit gleicher Wirkung.\n\n2. Warum dies in der Praxis von Bedeutung ist – und nicht nur aus Höflichkeit\n\n2.1 Eine Behörde könnte aus gutem Grund zögern, sich auf von einer externen Partei bereitgestelltes Material zu stützen, aus Angst, den Anschein zu erwecken, auf Veranlassung dieser Partei zu handeln, oder sich in irgendeiner Weise mit ihr zu verstricken.\n\n2.2 HIER GIBT ES NICHTS, MIT DEM MAN VERFLOCHTEN SEIN KÖNNTE. Die Koalition verlangt nichts, hat keinen Anspruch auf etwas, behält nichts für sich und hegt keinerlei Erwartungen. Sie kann später kein Recht geltend machen, keine Anerkennung einfordern, sich nicht über Missbrauch beschweren oder Einwände gegen die Darstellung des Materials erheben, da sie sich keine Grundlage dafür vorbehalten hat.\n\n2.3 Eine Behörde, die dieses Material nutzt, handelt daher nicht im Auftrag der Koalition. Sie nutzt öffentliche Informationen, die zufällig von jemand anderem zusammengestellt wurden.\n\n3. Alles ist bereits offen zugänglich\n\n3.1 Die Arbeit der Koalition ist standardmäßig öffentlich:\n\nDie Recherchen werden offen unter https://phishdestroy.io und sind frei einsehbar;\n\ndie Tools werden als Open Source unter der MIT-Lizenz unter https://github.com/phishdestroy archiviert unter 2026-09-11 ↗;\n\nDie Methodik ist in der Vorlage selbst dargelegt, und zwar in Anhang A Abschnitt A.16D, einschließlich der Gewichtung und Einschränkungen der einzelnen Quelltypen;\n\nDie Koalition nimmt keine Spenden entgegen und hat diesen Standpunkt seit 2018. veröffentlicht\n\n3.2 Das einzige Material, das NICHT veröffentlicht wurde, ist das, das rechtlich oder aus Sicherheitsgründen nicht veröffentlicht werden darf: personenbezogene Daten von Opfern und Dritten sowie Informationen, die eine Quelle der Vergeltung aussetzen würden. Dieses Material wird den Behörden vertraulich zur Verfügung gestellt und ist in den Beweisverzeichnissen aufgeführt.\n\n3.3 Die Koalition lädt dazu ein, ihr eigenes Verhalten unter denselben Bedingungen zu überprüfen, unter denen sie auch die Überprüfung des Verhaltens anderer fordert, und hat den zuständigen Behörden freiwillig Einblick in ihre eigenen Datenverarbeitungsprozesse gewährt, einschließlich der Bitte um eine Anweisung zur Datenlöschung.\n\n4. Integrität des Beweismaterials\n\n4.1 Die Beweisstücke werden mit der Einreichung bereitgestellt oder, sofern gekennzeichnet, auf Anfrage über einen sicheren Kanal übermittelt. Sie werden nicht unter einer öffentlichen Adresse veröffentlicht, und eine solche Adresse sollte auch nicht abgeleitet werden: Material dieser Art wird den Behörden direkt zur Verfügung gestellt.\n\n4.2 Jeder Übermittlung liegt eine Datei „SHA256SUMS“ bei, die für jede bereitgestellte Datei einen SHA-256-Digest sowie eine separate „OpenPGP“-Signatur SHA256SUMS.asc enthält.\n\n4.3 Der Signaturschlüssel ist veröffentlicht unter https://phishdestroy.io/.well-known/pgp-key.txt und auf keys.openpgp.org veröffentlicht. Sein Fingerabdruck erscheint im Briefkopf jeder Einreichung in diesem Satz.\n\n4.4 Jeder Empfänger kann jederzeit überprüfen, ob eine in seinem Besitz befindliche Datei tatsächlich die gesendete Datei ist und nicht verändert wurde:\n\ngpg --verify SHA256SUMS.asc SHA256SUMS\n\nsha256sum -c SHA256SUMS\n\n4.5 Dabei geht es nicht um reine Formalität. Vielmehr soll sichergestellt werden, dass, falls die Richtigkeit oder Integrität eines Belegs zu einem späteren Zeitpunkt angefochten wird, die Frage durch Berechnung und nicht durch Argumente geklärt werden kann.\n\n5. Zur Klarstellung – warum der Verzicht zweckmäßig und nicht nur großzügig ist\n\n5.1 Die Behörde könnte auf die veröffentlichten Untersuchungen der Koalition stoßen und diese als unverblümt, konfrontativ und bisweilen satirisch empfinden. Dieser Eindruck ist zutreffend. Die Koalition schreibt bewusst in diesem Stil und entschuldigt sich nicht dafür.\n\n5.2 SIE ERKENNT AUCH AN, DASS DIES DER FALSCHE STIL FÜR EIN VERWALTUNGS- ODER GERICHTSVERFAHREN IST. Eine ernste Angelegenheit sollte nicht im Ton einer Kampagne behandelt werden. Eine Behörde vorgelegte Erkenntnisse sollten nüchtern dargelegt werden, wobei ihre Grenzen eingeräumt werden, und sie sollten den Leser nicht dazu zwingen, den Tonfall zu berücksichtigen, bevor er zum Kern der Sache vordringt.\n\n5.3 GENAU DESHALB VERZICHTET DIE KOALITION AUF DIE NENNUNG DER URHEBERSCHAFT. Der Verzicht unter 1 ist der Mechanismus, durch den der Inhalt vom Stil getrennt werden kann: Die Behörde kann das Nützliche übernehmen, es in ihren eigenen Worten wiedergeben und jedes Wort, das den Stil der Koalition widerspiegelt, zusammen mit dem Namen der Koalition verwerfen. Dadurch geht nichts verloren, und die Koalition würde dies sogar bevorzugen.\n\n5.4 DIE KOALITION BITTET AUCH DARUM, DAS VERZEICHNIS NICHT MIT DER METHODE ZU VERWECHSELN. Der veröffentlichte Ton ist kämpferisch; die zugrunde liegende Vorgehensweise ist jedoch nicht nachlässig. In dieser Stellungnahme werden Schlussfolgerungen von Beobachtungen getrennt, Aussagen werden als solche gekennzeichnet, Quellen werden abgewogen und ihre Schwächen dargelegt, Zahlen werden mit ihren Einschränkungen präsentiert, und Punkte, die die Koalition nicht beweisen kann, werden als Fragen an die Behörde formuliert und nicht als Behauptungen. Wo die Beweislage der Position der Koalition widersprach, hat sie dies auch so angegeben – siehe Anhang A, Absatz 7, und Abschnitt B.0 der parallelen Vorlage.\n\n5.5 DIE KOALITION ERKLÄRT DEN ZUSAMMENHANG ZWISCHEN IHRER VORGEHENSWEISE UND IHRER FINANZIERUNG, DA BEIDES UNTRENNBAR IST. Sie nimmt von niemandem Geld an – keine Spenden, keine Prämien, keine Auftraggeber, keine Sponsoren. Diese Weigerung ist es, die die Unverblümtheit ermöglicht: Eine Organisation, die Einnahmen zu schützen hat, muss ihre Äußerungen über die Parteien, von denen sie abhängt, mäßigen. Da die Koalition nichts zu schützen hat, muss sie sich in nichts mäßigen.\n\nDas ist auch der Grund, warum die Koalition weiterhin existiert. Es gibt keinen anderen Antrieb. Die Arbeit wird geleistet, weil sie geleistet wird; sie hört auf, wenn die Menschen, die sie leisten, aufhören.\n\n5.6 Die Behörde muss nichts davon akzeptieren. Dies wird nur dargelegt, damit der Ton der öffentlichen Arbeit der Koalition nicht als Maßstab für die Sorgfalt gewertet wird, mit der sie das ihr nun vorliegende Material behandelt.\n\n6. Was die Koalition nach eigenen Angaben bereitstellt\n\nInformationen, Forschung und Beobachtung.\n\nNichts wird als Ergebnis behauptet, zu dem die Koalition nicht befugt ist. Wo etwas abgeleitet wird, wird dies in der Vorlage angegeben. Wo etwas auf Zeugenaussagen beruht, wird in der Vorlage angegeben, von wem diese stammen und mit welchen Einschränkungen. Wo die Koalition eine Frage nicht beantworten kann, gibt sie dies ebenfalls an und nennt, wer dies kann.\n\nDie Koalition strebt weder Rechtsbehelf noch Zahlung, noch Anerkennung noch ein Ergebnis für sich selbst oder für eine einzelne Person an. Sie fordert lediglich, dass die in der Vorlage dargelegten Fragen von einer Stelle, die befugt ist, eine Antwort zu erzwingen, an die „Valve“ Corporation gerichtet werden.\n\nSchlussbemerkungAn denjenigen, der dies weiterverfolgt\n\nWir möchten uns bei allen bedanken, die dieses Material dorthin bringen, wo es hingehört. Es wird wahrscheinlich kein schneller Weg sein. „Valve“ verfügt über tiefe Taschen, und Taylor Wessing berechnet Stundenhonorare – diese Kombination ist speziell darauf ausgelegt, dass Menschen wie Sie aufgeben, bevor sie die Ziellinie erreichen.\n\nWir wissen, was wir tun. Wir wissen, über wen wir schreiben. „Valve“ hat uns groß gemacht – wie könnten wir sie da nicht verstehen?\n\nPhishDestroy Es gibt keinen Konflikt mit Valve. Wir haben den einzigen Betrügerring dieser Größenordnung blockiert, auf den wir gestoßen sind – wir haben keinen Streit mit Valve gesucht. Es hat sich einfach so ergeben, dass jeder Weg zu ihnen zurückführte. Kein Konflikt. Nur Topologie.\n\nValve Die Situation mit PhishDestroy lässt sich nicht lösen, weil es nichts zu lösen gibt. Wir haben keine Beziehung zu ihnen. Die Daten über ihre Bereicherungsmaschen und übermäßigen Gewinne sind größtenteils öffentlich – man musste nur genug Zeit aufwenden, um sie zu sehen. Stell dir das als eine Art Erfolgs-Enzyklopädie vor: „Wie man Sanktionen umgeht, damit russische Hacker unsere kostenlosen Spiele nicht raubkopieren können (die kostenpflichtigen würden sie sowieso nicht raubkopieren).“ Du verstehst, worauf ich hinauswill.\n\nWir brauchen keine Urheberschaft.\n\nWir brauchen keine Urheberschaft.\n\nWir brauchen keinen Sieg.\n\nWir brauchen jemanden mit tatsächlicher Autorität, der Valve die Fragen stellt, die bereits in dieser Meldung enthalten sind, und der die Macht hat, eine Antwort einzufordern.\n\nDas ist alles. Das ist die gesamte Forderung.\n\nDie Fälle werden hier zu finden sein:\n\nhttps://steamdestroy.eth/\n\nhttps://steamdestroy.eth.limo (derzeit nicht funktionsfähig – wird bei Bedarf behoben)\n\nWir sind zu finden unter:\n\nhttps://phishdestroy.eth.limo/ archiviert unter 2026-06-27 ↗\n\nhttps://phishdestroy.eth/\n\nZwei signierte Objekte · Rechte und veröffentlichter Text\nSignierte VeröffentlichungWas ist signiert und was umfasst es?\n\nDie Rechteübertragung und der Forschungstext sind unten als separat signierte JSON-Objekte aufgeführt. Jede eigenständige „OpenPGP“-Signatur authentifiziert die exakten Bytes des daneben genannten JSON-Objekts. Die Rechteerklärung gewährt Berechtigungen; der Textsnapshot identifiziert das veröffentlichte Material und enthält es.\n\n1. Rechteerklärung — license-rights.json\n\nSigniertes Objekt: die vollständige license-rights.json Datei, die die öffentliche Rechteübertragung vom 28 September 2026. enthält. Sie gewährt die Erlaubnis, verfasste Dossier-Materialien ohne Namensnennung, Benachrichtigung oder Genehmigung zu kopieren, zu veröffentlichen, zu bearbeiten, zu übersetzen, zu kombinieren und zu vermarkten. Diese Signatur beglaubigt die Rechteerklärung; sie beglaubigt nicht den Text jeder einzelnen Webseite oder jedes PDFs.\n\nDie ursprünglich signierte Freigabe bleibt unverändert erhalten. Die darin enthaltene Einwilligung kann nicht durch Änderungen an der Website, die Veröffentlichung einer anderen Datei oder die Abschaltung der Website widerrufen oder eingeschränkt werden. Materialien von Dritten unterliegen weiterhin ihren eigenen Rechten.\n\nRechteerklärung JSON ↗ · Signatur von license-rights.json ↗ · SHA-256 von license-rights.json ↗\n\ngpg --verify license-rights.json.asc license-rights.json\nsha256sum -c license-rights.json.sha256\n2. Veröffentlichter Text — dossier-text.json\n\nSigniertes Objekt: die vollständige dossier-text.json Datei. Sie enthält den tatsächlich lesbaren Text der exportierten Seiten in documents[].content.text, zusammen mit dem Titel, der Sprache, der Quell-URL, dem Quell-HTML-Hash, den Überschriften und den Verweisen jeder Seite. Die documents Liste ist das genaue Inventar, das dieser Snapshot abdeckt; die Sprachvarianten sind separat aufgeführt. Es handelt sich um eine Textveröffentlichung, nicht nur um eine Liste von Hashes.\n\nJeder Eintrag identifiziert seine Lightweight-Seite-PDF anhand von Dateinamen und SHA-256 in documents[].pdf. Das JSON identifiziert zudem die ursprüngliche Rechteerklärung anhand der URL und des SHA-256,, sodass der veröffentlichte Text, sein PDF und die entsprechende Rechtefreigabe ohne Spekulationen einander zugeordnet werden können. Verlinkte externe Datenbanken, Bildvorlagen und Seiten, die nicht im Bestand enthalten sind, sind in diesem Text-Snapshot nicht eingebettet.\n\nVollständiger signierter Text (JSON) ↗ · Signatur von dossier-text.json ↗ · SHA-256 von dossier-text.json ↗\n\ngpg --verify dossier-text.json.asc dossier-text.json\nsha256sum -c dossier-text.json.sha256\n\nAuf der Startseite des Dossiers exportieren die Schaltflächen „PDF“ und „JSON“ das Recherchepaket. Auf einer Unterseite exportieren sie diese Seite in der Sprache, in der sie veröffentlicht wurde. Jede Seite im JSON-Format verfügt zudem über eine eigene, separate Signatur und eine SHA-256-Datei, die in ihrem integrity Objekt explizit benannt ist. Um die zugehörige PDF-Datei zu verifizieren, berechnen Sie deren SHA-256 und vergleichen Sie diesen mit dem pdf.sha256 Wert in der verifizierten JSON-Datei. Die PDF-Datei ist an diesen Digest gebunden; sie enthält keine digitale Signatur im PDF-Format.\n\n3. Druckbares Forschungspaket – steam-dossier-{language}.content.json\n\nSigniertes Objekt: die vollständige sprachspezifische JSON-Datei, einschließlich der gebündelten Kapiteltexte in documents[].content.text, die Seitenbereiche der Kapitel, die Quellsprachen, das Verzeichnis der ausgeschlossenen Quellen und den exakten PDF-Digest in pdf.sha256. Die fünf ergänzenden Quellenarchive bleiben online miteinander verknüpft und werden nicht gebündelt. Die verfassten Forschungstexte bleiben erhalten; Bildkataloge werden durch Links zu den Quellen ersetzt.\n\nEnglisch JSON ↗ · Freistehendes Haus „OpenPGP“ ↗ · SHA-256-Digest ↗\n\nDeutsch JSON ↗ · Freistehendes Haus „OpenPGP“ ↗ · SHA-256-Digest ↗\n\ngpg --verify steam-dossier-en.content.json.asc steam-dossier-en.content.json\nsha256sum -c steam-dossier-en.content.json.sha256\n\nÖffentlicher Verifizierungsschlüssel ↗\n\nSignatur-Fingerabdruck: 129F C7F3 9C40 C69D 2EF3 C329 BFCF 9E8D D295 EE01\n\ngpg --import pgp-key.txt\ngpg --fingerprint 129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01\n\nÜberprüfen Sie, ob der angezeigte Fingerabdruck mit dem oben angegebenen übereinstimmt, und vergleichen Sie anschließend die Signatur mit dem genauen JSON-Dateinamen. Das Bearbeiten einer signierten JSON-Datei verändert das signierte Objekt und macht dessen ursprüngliche Signatur ungültig. Eine gültige Signatur identifiziert die veröffentlichten Bytes; sie stellt keine unabhängige Überprüfung der Forschungsergebnisse dar.\n\nPhishDestroy — öffentliche Untersuchung — alle Rechte an die Menschheit abgetreten\n\nZugang zur OFAC-Region: verboten",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Lizenz & Rechtlicher Hinweis – Widmung als Public Domain"
          },
          {
            "level": 2,
            "id": null,
            "text": "Abschnitt ILizenz — der eigentliche rechtliche Teil, aber menschlich ausgedrückt"
          },
          {
            "level": 3,
            "id": null,
            "text": "Eine einzige Regel (ja, wirklich nur eine)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Abschnitt IIWas das ist und warum es existiert"
          },
          {
            "level": 2,
            "id": null,
            "text": "Abschnitt IIIOffener Brief an Valve – im Ernst, lies das hier"
          },
          {
            "level": 3,
            "id": null,
            "text": "Das Angebot (offenes Angebot, keine Anwälte erforderlich)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Abschnitt III-BDie verbündeten Ressourcen – ein Hinweis speziell an Steam"
          },
          {
            "level": 2,
            "id": null,
            "text": "Abschnitt IVDas Geld, die Verbote, der ganze Zirkus"
          },
          {
            "level": 2,
            "id": null,
            "text": "Abschnitt VDie Malware-Sache – ja, wir erwähnen es"
          },
          {
            "level": 2,
            "id": null,
            "text": "ErklärungIn Bezug auf Nutzung und Rechte"
          },
          {
            "level": 3,
            "id": null,
            "text": "1. Es bestehen keine Nutzungsbedingungen"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. Warum dies in der Praxis von Bedeutung ist – und nicht nur aus Höflichkeit"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. Alles ist bereits offen zugänglich"
          },
          {
            "level": 3,
            "id": null,
            "text": "4. Integrität des Beweismaterials"
          },
          {
            "level": 3,
            "id": null,
            "text": "5. Zur Klarstellung – warum der Verzicht zweckmäßig und nicht nur großzügig ist"
          },
          {
            "level": 3,
            "id": null,
            "text": "6. Was die Koalition nach eigenen Angaben bereitstellt"
          },
          {
            "level": 2,
            "id": null,
            "text": "SchlussbemerkungAn denjenigen, der dies weiterverfolgt"
          },
          {
            "level": 2,
            "id": null,
            "text": "Signierte VeröffentlichungWas ist signiert und was umfasst es?"
          },
          {
            "level": 3,
            "id": null,
            "text": "1. Rechteerklärung — license-rights.json"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. Veröffentlichter Text — dossier-text.json"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. Druckbares Forschungspaket – steam-dossier-{language}.content.json"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/de/#briefing-heading",
          "https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "http://web.archive.org/web/20260821155801/https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "https://phishdestroy.io/steam_dossier/de/investigation_part2.html#outsourcing-case",
          "https://phishdestroy.io/steam_dossier/de/#theft-ledger",
          "https://steamid.uk/",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/groups/steambans",
          "https://steamcommunity.com/id/killahinstinct_",
          "https://phishdestroy.io/steam_dossier/de/card_economy.html#governance",
          "https://phishdestroy.io/steam_dossier/de/license_disclaimer.html",
          "https://github.com/phishdestroy",
          "http://web.archive.org/web/20260911040557/https://github.com/PhishDestroy",
          "https://phishdestroy.io/.well-known/pgp-key.txt",
          "https://steamdestroy.eth/",
          "https://steamdestroy.eth.limo/",
          "https://phishdestroy.eth.limo/",
          "http://web.archive.org/web/20260627040219/https://phishdestroy.eth.limo/",
          "https://phishdestroy.eth/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json.asc",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json.sha256",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json.sha256?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json.sha256?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json.sha256?v=print-20260928-v3"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/de/license_disclaimer.content.json",
      "export_json_sha256": "d65416074b8e5b575dca0591d47eb84a2cfb8e93d82bbbc41b5167385e6ac58f"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "de/market_economics.html",
      "language": "de",
      "title": "Eine Infrastruktur, zwei Märkte – Das Dossier „Steam“",
      "source_url": "https://phishdestroy.io/steam_dossier/de/market_economics",
      "source_html_sha256": "dd225bff546af1939cb2e6de9fd84410b6d9b90c87e4c18772c31227d75bb4c2",
      "exported_at": "2026-09-29T00:16:11.302Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "market_economics.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/de/market_economics.pdf?v=print-20260929-v5",
        "sha256": "9a2bb90420d4564d73507ea24a07d322f4ff1c8212025d2640816d04b5fa0a7e",
        "bytes": 103688,
        "pages": 8
      },
      "integrity": {
        "signed_object": "market_economics.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "market_economics.content.json.asc",
        "digest_file": "market_economics.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify market_economics.content.json.asc market_economics.content.json",
          "sha256sum -c market_economics.content.json.sha256"
        ]
      },
      "content": {
        "text": "Anhang VII · Marktarchitektur · 20 September 2026\nMarktwirtschaft – Zwei Wirtschaftssysteme und die Obergrenze für Börsennotierungen\n\nIhre Infrastruktur. Zwei Volkswirtschaften.\n\nWAS DIESER ABSCHNITT BELEGT\n\nIn diesem Kapitel wird die systemische Marktpolarisierung analysiert, die durch die Obergrenze von $1,800 für die Notierung bei Valve und die nicht abhebbaren Wallet-Guthaben entsteht. Durch die Untersuchung von 38 aktiven externen Skin-Börsen mit einer gelisteten Marktkapitalisierung von etwa $1.28 Milliarden belegt die Untersuchung, dass der Handel im hohen Volumen zwangsläufig auf externe Schattenplattformen ausweicht, während er sich gleichzeitig auf die zugrunde liegende Handels- und Authentifizierungsinfrastruktur von Steam stützt. Obwohl die kommerzielle Nutzung in der Nutzungsvereinbarung formell untersagt ist, ermöglicht Valve diese zweigeteilte Wirtschaft und monetarisiert sie, ohne dass es veröffentlichte Aufzeichnungen über Durchsetzungsmaßnahmen gibt.\n\n← Zurück zum Executive Briefing\n\n38 aktive CS2-Marktplätze von Drittanbietern sowie den eigenen Marktplatz von „Steam“. Jeder auf einer dieser Plattformen gelistete Skin muss über das Inventar von „Steam“ und die Handelsplattform „API“ abgewickelt werden. Die Regeln von „Valve“ verbieten die kommerzielle Nutzung dieser Infrastruktur. Der von Dritten geschätzte Wert von rund $1.28 Milliarden besteht, obwohl keine öffentlichen Aufzeichnungen über die Durchsetzung dieser Regel gefunden wurden.\n\n$1.28B\nVon Dritten angegebene Werte · Plattformen der Art „38“\n53.2M\nAngezeigte Angebote · 38 Märkte von Drittanbietern\n70.1K\nSteam im Snapshot aufgeführte Elemente\n41×\nVon Dritten angegebener Wert im Vergleich zu den $31M von „Steam“\nDas zentrale Ergebnis\nEine Infrastruktur. Zwei Volkswirtschaften.\n\nSteam kontrolliert den Artikel, den Bestand und den Handel. Jeder Skin, der auf einer der unten aufgeführten Plattformen verkauft wird, muss über die HandelsAPI von Steam abgewickelt werden – eine strukturelle Abhängigkeit, die direkt beobachtbar ist. — eine strukturelle Abhängigkeit, die direkt beobachtbar ist. Der eigene Community Market von Valve erzielt eine Provision auf seine Verkäufe; ob diese Provision das Ökosystem von Drittanbietern finanziert oder daran gekoppelt ist, wird hier nicht näher erläutert.\n\nWarum dies für die Ermittlungen von Bedeutung ist\n1\nValve – Nutzungsvereinbarung für „Steam“ verbietet die kommerzielle Verwertung der Infrastruktur von „Steam“ ohne ausdrückliche Genehmigung. In den öffentlich zugänglichen Unterlagen wurde für die unten aufgeführten Plattformen keine derartige Genehmigung gefunden.\n2\nSteam steuert die Identitätsprüfung (OpenID), den Bestandsstatus und die Handelsausführung für den Wert von rund $1.28B, der von Dritten gelistet ist. Ohne die Infrastruktur von „Valve“ findet keine Übertragung von Gegenständen statt.\n3\nDer eigene Marktplatz von Steam verfügt über $31M notiert – etwa 1/41 des von Drittanbietern notierten Wertes. Die Preisobergrenze von $1,800 bedeutet, dass Verkäufer, die diesen Wert überschreiten, außerhalb der Plattform verkaufen müssen, um zu den beobachteten Preisen zu verkaufen.\n4\n248 CS2-Artikelkategorien, deren Preis von zwei oder mehr Marktplätzen unabhängig voneinander über der Obergrenze liegt, können auf Steam nicht zu ihrem beobachteten Marktpreis verkauft werden – und keines dieser Produkte ist dort überhaupt gelistet. Die Obergrenze von $1,800 schafft die Nachfrage, die von Drittanbietern gedeckt wird.\nSteam Community-Markt: $31MVon Dritten angegebener Wert: $1,276M\n1,276Mio. $ · von Dritten angegebener Wert — alles abhängig von Steams HandelsAPIen und OpenID\nSteam · $31M\n\nQuelle: PriceEmpire-Echtzeitkatalog, 20 September 2026. Listenpreis = Summe der gerundeten Listenpreise in der gespeicherten Momentaufnahme, Steam ausgenommen. Kein Absatzvolumen.\n\n38 aktive Drittmärkte · Alles hängt von der Infrastruktur von „Steam“ ab\nPlattformregister\n\nDie unten aufgeführten Plattformen leiten ihre Anmeldungen über die OpenID von Steam und ihre Handelsgeschäfte über den Web-API von Steam weiter. Jede beobachtete openid.realm durchläuft den Anmeldeprozess von Steam; das Register erfasst die beobachteten Authentifizierungsrouten, anstatt zu behaupten, dass einem bestimmten Operator die Berechtigung von Valve fehlt.\n\n#\tPlattform\tBörsenkurs\tAktuelle Angebote\tArtikel\tMaßstab\n1\tUUSkins\t$133.8M\t3.4M\t30.9K\t\n\n2\tYouPin898\t$127.5M\t5.9M\t29.2K\t\n\n3\tBuff.163\t$104M\t3.5M\t35K\t\n\n4\tMoon.Market\t$100.3M\t2.9M\t20.9K\t\n\n5\tWhite.Market\t$89.6M\t3M\t20.6K\t\n\n6\tBuff.Market\t$86.7M\t1.3M\t33.4K\t\n\n7\tEcosteam\t$82.1M\t3.3M\t30.1K\t\n\n8\tCSFloat\t$67.8M\t2.4M\t27.8K\t\n\n9\tSkin.Land\t$67.4M\t2.2M\t34.6K\t\n\n10\tLIS-SKINS\t$67.4M\t2.2M\t34.6K\t\n\n11\tC5Game\t$54.6M\t4.6M\t29.6K\t\n\n12\tHaloSkins\t$46.6M\t4.4M\t29.3K\t\n\n13\tAvan.Market\t$43.3M\t809.5K\t22.2K\t\n\n14\tWaxpeer\t$40.1M\t1M\t27.3K\t\n\n15\tSteam (official)\t$31M\t32.2M\t70.1K\t\n\n16\tCS.MONEY\t$29M\t748.9K\t28K\t\n\n17\tMarket.CSGO\t$26.3M\t1.3M\t27.6K\t\n\n18\tCS.MONEY Bot\t$25.7M\t614K\t23.8K\t\n\n19\tSkinport\t$16.3M\t3.8M\t31.1K\t\n\n20\tSkinFlow\t$14.1M\t481.8K\t23.6K\t\n\n21\tDMarket\t$12.6M\t948.2K\t35.6K\t\n\n22\tSkins.com\t$11.5M\t83.2K\t15.8K\t\n\n23\tSkin.place\t$6.9M\t380.8K\t11.4K\t\n\n24\tSkinsMonkey\t$6M\t109.4K\t11.6K\t\n\n25\tSkinBaron\t$5M\t2.1M\t21.5K\t\n\n26\tRustTM\t$3M\t33.1K\t4.9K\t\n\n27\tPirateSwap\t$2M\t859.3K\t10.5K\t\n\n28\tMannco.Store\t$1.2M\t223.7K\t11K\t\n\n29\tSkinSwap\t$1.1M\t11.4K\t4K\t\n\n30\tTradeIt\t$967.1K\t29.1K\t11.7K\t\n\n31\tLootFarm\t$896.1K\t162.5K\t28.6K\t\n\n32\tRustskins\t$714.8K\t312.5K\t6.1K\t\n\n33\tBalticSkins\t$599.2K\t28.2K\t4.5K\t\n\n34\tExeSkins\t$442.9K\t2.6K\t1.4K\t\n\n35\tRapidSkins\t$230.9K\t11.6K\t2.3K\t\n\n36\tCS.Trade\t$203K\t19K\t16.7K\t\n\n37\tKrakatoa\t$11.1K\t115\t53\t\n\n38\tShadowPay\t—\t—\t—\t—\n39\t49skins\t—\t—\t—\t—\nSteams Preisobergrenze von1,800 $ · Überblick über fünf Marktplätze · 23 September 2026\nDie Preisdifferenz ist messbar.\n\nSteam begrenzt die Angebote auf dem Community Market auf etwa $1,800 (das Ergebnis wird neu berechnet auf $2,000, $2,070, $2,300und $2,500 in cs2sh-atlas.json und hält an jeder Schwelle stand). Artikel, deren Preis über diesem Wert liegt können nicht zum Marktpreis über den eigenen Marktplatz von „Valve“ verkauft werden — aber sie sind nach wie vor vom Lager- und Versandsystem von „Steam“ abhängig, unabhängig davon, wo sie verkauft werden. Eine Einteilung des gesamten Sortiments nach Preis zeigt, wo die Grenze liegt: Der Markt von „Valve“ umfasst 95.3% der Artikelkategorien, deren Preise unter der Preisobergrenze liegen, und 1.9% der darüber liegenden.\n\nFünf Marktplätze: Artikel, die die Obergrenze von „Steam“ überschreiten\n248\n\nArtikelkategorien, bei denen der günstigste Angebotspreis1,800 übersteigt, am zwei oder mehrere Marktplätze unabhängig voneinander, mit einem Bestand an börsennotierten Anteilen der „18,394“ im Wert von mindestens $78.6M. Davon 100.0% — jede einzelne davon — ist überhaupt nicht bei „ Steam“ gelistet.\n\nVollständige Anlagen: das Register → · Der Preisleiter-Atlas →\n\nPreisverteilung oberhalb der Obergrenze\n$1,800–$5,000\n174\n$5,000–$10,000\n49\n$10,000–$25,000\n21\n$25,000–$50,000\n2\n$50,000+\n2\nTop-Artikel – günstigster bestätigter Angebotspreis auf fünf Marktplätzen\n1Aufkleber | Titan (Holo) | Kat. „14“$66,285\n2Aufkleber | iBUYPOWER (Holo) | Kat. „14“$64,795\n3Aufkleber | Reason Gaming (Holo) | Kat. „14“$42,899\n4★ Sport-Handschuhe | Heckenlabyrinth (FN)$26,812\n5Aufkleber | Team Dignitas (Holo) | Kat. „14“$23,667\n6EMS Kat. „14-Legenden“$22,879\n7★ Sport-Handschuhe | Pandoras Büchse (FN)$21,643\n8EMS-Kat. „14-Herausforderer“$21,010\n9Aufkleber | Vox Eminor (Holo) | Kat. „14“$18,619\n10★ StatTrak™ Navaja-Messer | Blue Steel (FN)$18,064\n\nAngebotspreise sind keine Verkaufspreise. Auszug aus „cs2.sh“, 23, Stand: September 2026.. Jede Zeile wird von mindestens zwei unabhängigen Marktplätzen über der Obergrenze notiert; Einzelangebots- und -nachfragepreise, die mehr als das Dreifache des günstigsten Angebotspreises eines Artikels betragen, werden ausgeschlossen. So funktioniert die Benotung →\n\nWas Valve kostet · lizenziert cs2.sh Momentaufnahme · 23 September 2026\nDie angegebene Vergütung beträgt 15%.. Bei den meisten Angeboten wird mehr gezahlt.\n\nValve behält eine Gebühr für „5%“ (Steam) sowie eine „10%“-CS2-Verlegergebühr vom Erlös des Verkäufers ein – die bekannte „15%.“. Beide Gebühren beinhalten eine Mindestens0.01, sodass bei keinem Verkauf die Gebühren jemals weniger als zwei Cent betragen können. Bei den günstigen Artikeln mit hohem Absatz, die den Großteil des Marktes ausmachen, stellt diese Untergrenze die entscheidende Einschränkung dar, nicht der Prozentsatz. Wir haben die Gebührenberechnung für jeden einzelnen der 29,635 Artikelarten, für die eine Anfrage mit Live-Steamen vorliegt.\n\n77.7%\nAktuelle Angebote auf Steam werden nach den oben genannten Artikelkategorien berechnet: 15%\n84.8%\ndes Artikels Typen zahlen tatsächlich in etwa den in der Überschrift genannten Satz\n4,517\nFür bestimmte Artikelarten wurde eine höhere Gebühr als die angegebene berechnet\n$0.02\nMindestgebühr bei jedem Verkauf, unabhängig vom Preis\nDie beiden Zahlen weisen in entgegengesetzte Richtungen, und beide sind richtig.\n1\nZählte nach Art des Artikels, Die Gebühren von „Valve“ entsprechen im Großen und Ganzen den Angaben: 84.8% der unter 29,635 aufgeführten Preisklassen werden zu den dort angegebenen Preisen oder zu ähnlichen Preisen berechnet: 15%.\n2\nZählte nach tatsächlicher Auflistung, kehrt sich das Bild um: 18,682,244 von „24,038,911“ Aktuelle Angebote beziehen sich auf Artikelarten, für die höhere Gebühren anfallen als unter 15%.\n3\nBeides trifft zu, denn die überladenen Typen sind die günstig, in großen Mengen diese. 1,109 Bestandsarten werden teurer berechnet als doppelt der Spitzenpreis, und allein diese Arten sind in den aktuellen Angeboten auf 14,083,486 zu finden.\n4\nDas ist reine Mathematik, keine Behauptung. Der Mindestbetrag ist in den eigenen Gebührenunterlagen von „Valve“ angegeben. Was nicht veröffentlicht wurde, ist wie groß der Marktanteil tatsächlich ist — und genau das wird anhand der obigen Zahlen gemessen.\nBerechnete Gebühr als Anteil am Netto-15%\n200%+\n14,083,486\n100-200%\n1,028,438\n50-100%\n700,804\n30-50%\n317,031\n20-30%\n2,258,254\n17.6-20%\n294,231\n\nDie „Bar-Länge“ bezeichnet die Anzahl der aktiven Angebote in jedem Bereich. Ein Bereich mit der Bezeichnung „200%+“ bedeutet, dass die erhobene Gebühr mehr als das Doppelte von 15% des Verkaufserlöses des Verkäufers beträgt.\n\nEin Beispiel mit Lösung\n67%\n\nBei einem Inserat zahlt der Käufer $0.03 denn der Verkäufer erhält $0.01 und „Valve“ dauert $0.02 — die beiden Mindestbeträge von jeweils einem Cent. Bezogen auf den vom Käufer gezahlten Preis beträgt dies 67%; bezogen auf den Erlös des Verkäufers beträgt dies 200%.\n\nVollständiger Datensatz: cs2sh-steam-fee-census.json →\n\nDerselbe Gegenstand, im Garten und außerhalb des Gartens\nEinkäufe auf Steam sind teurer. Fast immer.\n\nFür jeden Artikel, der sowohl auf Steam als auch auf mindestens einem Marktplatz eines Drittanbieters angeboten wurde, haben wir den günstigsten Angebotspreis auf Steam mit dem günstigsten Angebotspreis außerhalb dieser Plattform verglichen. Über 28,700 Was die Artikel angeht, ist Steam die teurere Plattform. 86.4% in den meisten Fällen um einen Medianwert von +35.7%.\n\nMedian der Prämien für „Steam“, nach Preisklassen\nunter0.50 Dollar\n+48.3%\n$0.50-2\n+36.5%\n$2-10\n+29.6%\n$10-50\n+28.6%\n$50-250\n+36.3%\n$250-1k\n+51.1%\nüber1,000 Dollar\n+67.9%\n\nDie Kurve verläuft U-förmig. Am günstigsten ist der Kauf auf Steam im $10–$50 Band und „Liebste“ an den beiden Enden.\n\nWarum das teure Segment wichtig ist\n+67.9%\n\nOben $1,000, die mittleren Angebotskosten auf Steam 67.9% sind höher als das günstigste Angebot außerhalb dieser Seite – und es gibt überhaupt nur 1,040 solche Angebote auf Steam.\n\nAb etwa1,800 ist ein Vergleich nicht mehr möglich, da die Regelung von Valve die Auflistung gänzlich untersagt. Die Berichterstattung von Steam über Artikel, deren Preis über der eigenen Obergrenze liegt, ist 1.9%. Die gesamte Rangliste anzeigen →\n\nVollständiger Datensatz: cs2sh-walled-garden-premium.json →\n\nEin Aufschlag ist für sich genommen noch keine Erkenntnis: Steam bietet sofortige Lieferung und kein Gegenparteirisiko, und Käufer sind durchaus bereit, dafür zu zahlen. Messbar sind hingegen die Höhe der Differenz und die Tatsache, dass das Geld, das diese Differenz überbrückt, nicht wieder zurückfließen kann – worauf im nächsten Abschnitt eingegangen wird.\n\nGeld rein, kein Geld raus\n128.1-Millionen-Dollar-Betrag für Aufträge, die nicht widerrufen werden können.\n\nEine Kauforder bei „Steam“ ist im Voraus finanziert: Das Geld wird in dem Moment von der Wallet des Käufers abgebucht, in dem die Order aufgegeben wird. Steam wallet funds kann nicht zurückgezogen werden — sie können ausschließlich innerhalb von „ Steam“ ausgegeben werden. Addiert man alle Preisstufen des Kaufbuchs jedes erfassten Artikels, erhält man eine Übersicht über das gebundene, nicht abziehbare Geld.\n\n$128.1M\nverpflichtet, Kaufaufträge vSteam-Konto auszuführen\n170.6M\noffene, individuell finanzierte Kaufaufträge\n$105.8M\nAngebotspreis der ihnen gegenüberliegenden Objekte\n$15.9M\nDie Provision von Valve, wenn jede Immobilie zum Angebotspreis verkauft würde\nWas diese Zahl ist und was sie nicht ist\n1\nEs ist bereits eingezahltes echtes Geld. Jeder erfasste Dollar wurde von einem Wallet abgebucht und ist mit einer offenen Order für verschiedene Artikelkategorien v31,253 verknüpft.\n2\nEs ist nicht Umsatz und keine Aussage über die Bilanz von „Valve“. Wo der Umlaufbestand gehalten wird und in wessen Büchern er verbucht ist, wird hier nicht näher erläutert.\n3\nEs ist ein Momentaufnahme, kein Ablauf. Bestellungen können vom Käufer storniert werden, woraufhin der Betrag wieder auf das Wallet zurücküberwiesen wird – jedoch noch nicht aus Steam.\n4\nDer springende Punkt ist die Einwegtür. Ein Marktplatz, dessen Währung nicht ausgezahlt werden kann, ist der Grund dafür, dass gestohlene Waren umgewandelt werden. aus Steam statt darauf.\n\nMethode: Jedes Preisniveau jedes erfassten Kaufbuchs, multipliziert mit den Aufträgen, die auf diesem Niveau vorliegen. Vollständiger Datensatz: cs2sh-steam-locked-capital.json →\n\nTatsächliche Verkaufspreise, keine Angebotspreise · eine Plattform · 90-Tage-Trend\nTatsächlich wurden30.9-Millionen-Dollar umgesetzt – auf dem kleinsten der fünf Regale.\n\nEin einzelner Verkauf zu einem hohen Preis kann sich um ein seltenes Unikat oder eine mit Aufklebern versehene Variante eines günstigen Basisartikels handeln (z. B. e.g: ein Artikel im Wert von $30, der einmalig für $9,772 verkauft wurde). „Hoch“ = höchste abgeschlossene Transaktion, nicht der normale Preis des Artikels.\n\nJede andere Abbildung auf dieser Seite misst das, was aufgeführt. Dieses hier misst, was verkauft. Skinport veröffentlicht seine eigenen abgeschlossenen Transaktionen, und in den letzten 90 Tagen beliefen sich diese auf 1,219,143 Umsatz Wert $30,927,032, zu einem Durchschnittspreis von jeweils25.37 Dollar.\n\n1.22M\nAbgeschlossene Verkäufe in „90“ Tagen, ein Marktplatz\n$30.9M\nUmsatz im gleichen Zeitraum\n$125M\nannualisierte Run Rate – eine Untergrenze, keine Schätzung\n~2%\nDer Anteil von Skinport am „Above-Cap-Shelf“ nach Börsenwert\nWoher der Umsatz stammte\nunter1 Dollar\n0.5%\n$1-10\n5.8%\n$10-100\n22.2%\n$100-1k\n59.4%\n$1k-1.8k\n6.9%\nüber der Obergrenze für den „Steam“\n5.3%\n\nDie Balkenlänge entspricht dem Umsatz; die Zahl gibt den Anteil dieser Ebene am Gesamtumsatz an. 59.4% des Geldes, das im $100–$1k-Segment bei 71,437-Verkäufen umgesetzt wurde.\n\nAuch über „Valves“ Kappe hinaus werden weiterhin Verkäufe getätigt\n492\n\nabgeschlossene Verkäufe von Artikeln, deren Preis über der Obergrenze von Steam lag, im Wert von $1,643,938, über 76 verschiedene Artikelkategorien hinweg – auf einem Marktplatz, der etwa 2% dieses Regals einnimmt. Keiner dieser Verkäufe hätte auf Steam stattfinden können.\n\nVollständiger Datensatz: cs2sh-offsteam-90d-dynamics.json → · die erreichten Höchststände →\n\nSkinport ist EINER der hier erfassten Drittmärkte und stellt aufgrund seines Börsenwerts, der über der Obergrenze von Steam liegt, den kleinsten der fünf dar (etwa 2% dieses Segments). Jede hier angegebene Gesamtsumme stellt eine Untergrenze für die Off-Steam-Wirtschaft dar, nicht deren Umfang. Es werden keine Daten von Steam verwendet.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Marktwirtschaft – Zwei Wirtschaftssysteme und die Obergrenze für Börsennotierungen"
          },
          {
            "level": 2,
            "id": null,
            "text": "Eine Infrastruktur. Zwei Volkswirtschaften."
          },
          {
            "level": 2,
            "id": null,
            "text": "Plattformregister"
          },
          {
            "level": 2,
            "id": null,
            "text": "Die Preisdifferenz ist messbar."
          },
          {
            "level": 3,
            "id": null,
            "text": "Fünf Marktplätze: Artikel, die die Obergrenze von „Steam“ überschreiten"
          },
          {
            "level": 3,
            "id": null,
            "text": "Preisverteilung oberhalb der Obergrenze"
          },
          {
            "level": 3,
            "id": null,
            "text": "Top-Artikel – günstigster bestätigter Angebotspreis auf fünf Marktplätzen"
          },
          {
            "level": 2,
            "id": null,
            "text": "Die angegebene Vergütung beträgt 15%.. Bei den meisten Angeboten wird mehr gezahlt."
          },
          {
            "level": 3,
            "id": null,
            "text": "Berechnete Gebühr als Anteil am Netto-15%"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ein Beispiel mit Lösung"
          },
          {
            "level": 2,
            "id": null,
            "text": "Einkäufe auf Steam sind teurer. Fast immer."
          },
          {
            "level": 3,
            "id": null,
            "text": "Median der Prämien für „Steam“, nach Preisklassen"
          },
          {
            "level": 3,
            "id": null,
            "text": "Warum das teure Segment wichtig ist"
          },
          {
            "level": 2,
            "id": null,
            "text": "128.1-Millionen-Dollar-Betrag für Aufträge, die nicht widerrufen werden können."
          },
          {
            "level": 2,
            "id": null,
            "text": "Tatsächlich wurden30.9-Millionen-Dollar umgesetzt – auf dem kleinsten der fünf Regale."
          },
          {
            "level": 3,
            "id": null,
            "text": "Woher der Umsatz stammte"
          },
          {
            "level": 3,
            "id": null,
            "text": "Auch über „Valves“ Kappe hinaus werden weiterhin Verkäufe getätigt"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/de/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/de/elite_skins.html",
          "https://phishdestroy.io/steam_dossier/de/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/de/skin_atlas.html#grading",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-steam-fee-census.json",
          "https://phishdestroy.io/steam_dossier/de/skin_atlas.html#cliff",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-walled-garden-premium.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-steam-locked-capital.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-offsteam-90d-dynamics.json",
          "https://phishdestroy.io/steam_dossier/de/skin_atlas.html#highs"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/de/market_economics.content.json",
      "export_json_sha256": "946a8643739bd05d55107f9077f5e57d49597cf657b505d7ddeef26b31c7f0a4"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "de/regulatory_act_print.html",
      "language": "de",
      "title": "GESETZ ÜBER DIE FORENSISCHE PRÜFUNG: Valve Steam Web-API-Ökosystem und kommerzielle Nutzung (Ref.: VAL-REG-2026-09)",
      "source_url": "https://phishdestroy.io/steam_dossier/de/regulatory_act_print",
      "source_html_sha256": "53e83d37ab6363b16d70224bd200646ecffe505a0f45da48e11d8e9ba947cde4",
      "exported_at": "2026-09-29T00:16:11.456Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "regulatory_act_print.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/de/regulatory_act_print.pdf?v=print-20260929-v5",
        "sha256": "f35cdc76603554777fc913acbccddb8bf659e747c2b9b86b84c882826d7bdfce",
        "bytes": 187676,
        "pages": 14
      },
      "integrity": {
        "signed_object": "regulatory_act_print.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "regulatory_act_print.content.json.asc",
        "digest_file": "regulatory_act_print.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify regulatory_act_print.content.json.asc regulatory_act_print.content.json",
          "sha256sum -c regulatory_act_print.content.json.sha256"
        ]
      },
      "content": {
        "text": "phishdestroy.io · Koalition für forensische Forschung · Universelles öffentliches Register\nAKTENZEICHEN: VAL-REG-2026-09-EVID\nHERKUNFT: phishdestroy.io/steam_dossier/\nRECHTE: ALLE RECHTE AN DIE MENSCHHEIT ABGETRETEN\nGesetz über die forensische Wirtschaftsprüfung und aufsichtsrechtlicher Anhang\nSystematische Bereitstellung von „Third-Party-API“, automatisierte Bypass-Architektur und vertragliche Nichtdurchsetzung im „Valve“-Steam-Ökosystem\nAusstellende Domänephishdestroy.io\nZielplattformValve Steam / Steamworks\nPrimärer AuthentifizierungsvektorSteam OpenID 2.0 / Web API\nRechtlicher HinweisAll Rights to Humanity (CC0)\nAbschnitt I: Memorandum der Geschäftsleitung und Feststellungen zum SachverhaltREF: MEMO-SUMMARY-01\n\nDas vorliegende Dokument stellt einen formellen forensischen Prüfbericht dar, in dem die operativen Schnittstellen zwischen den veröffentlichten Geschäftsbedingungen der „Valve“ Corporation, ihren technischen Authentifizierungsendpunkten und beobachteten kommerziellen Plattformen von Drittanbietern untersucht werden. Die Prüfung erfolgte anhand passiver, nicht authentifizierter Netzwerkbeobachtung, der Überprüfung von Registrierungen bei RDAP sowie öffentlicher Link-Filter-Telemetriedaten.\n\nSachlicher Kern: Empirische Beobachtungen belegen eine systematische Diskrepanz zwischen den öffentlichen vertraglichen Zusicherungen von „Valve“ und seiner Produktionsinfrastruktur. Während der „Steam Subscriber Agreement“ (SSA) die unbefugte kommerzielle Nutzung (§ 2.G), automatisierte Bot-/Skript-Interaktionen (§ 4.C) und die Übertragung von Konten (§ 1.C) strengstens untersagt, stellt die „Valve Corporation“ weiterhin eine Infrastruktur für die programmatische OpenID-Authentifizierung und Bestandsabfragen in Echtzeit bereit – und zwar für mindestens 175 kommerzielle Unternehmen, die Sekundärtransaktionsvolumina in Höhe von mehreren Milliarden Dollar generieren.\n\n175\nGeprüfte gewerbliche Betreiber\n44\nAuthentifizierungshosts mit separaten Domänen\n26\nFilter-Split-Proxy-Paare\n100%\nNicht in Kraft getretene SSA § 2.G / § 4.C\n0\nErzwungene Authentifizierungswiderrufe\nAnwendbare vertragliche und gesetzliche Rahmenbedingungen\nSSA § 2.G\nVerbot der kommerziellen Nutzung: Die Nutzung von Inhalten und Diensten zu kommerziellen Zwecken ohne vorherige schriftliche Genehmigung der Valve Corporation ist ausdrücklich untersagt.\nSSA § 4.C\nEinschränkung der Automatisierung: Skripte, Trading-Bots, Makros oder nicht von Menschen gesteuerte Systeme, die mit den Diensten und Märkten von Steam interagieren, sind strengstens untersagt.\nSSA § 1.C\nVorschrift zur privaten Nutzung: Beschränkt die Nutzung der Konten auf den privaten Gebrauch; der Verkauf, die Vermietung, die Übertragung oder der Handel mit „Steam“-Benutzerkonten ist ausdrücklich untersagt.\nEU-DSA (2022/2065)\nSystemische Risikobewertung (Art. 34/35): Sehr große Online-Plattformen (VLOPs) müssen systemische Risiken, die sich aus automatisiertem Missbrauch und unbefugter kommerzieller Nutzung ergeben, aktiv erkennen, bewerten und mindern.\nAbschnitt II: Anhang A – Dokumentierte Link-Filter-Split-Paare (Routen nach 26)REF: EX-SPLIT-LEDGER\n\nForensische Analyse von Split-Domain-Umgehungstechniken: Im Rahmen des Link-Filter-Systems von „ Valve “ unter Steam (steamcommunity.com/linkfilter/?url=...), wenn ein Endnutzer auf einen Link klickt, der zu einer als problematisch gekennzeichneten Glücksspiel- oder Schwarzmarktplattform führt, zeigt Valve eine deutlich sichtbare Warnung an („Link gesperrt! … als potenziell schädlich markiert“). Die forensische Rückverfolgung der Datenwege zeigt jedoch, dass kommerzielle Plattformen von „26“ auf einer Architektur mit geteilten Domänen: Während die primäre kommerzielle Domain im Link-Filter als „BLOCKED“ gekennzeichnet ist, wird die sekundäre Domain, auf der der OpenID-Rückgabe-Endpunkt von Valve gehostet wird, als „CLEAN“ markiert. Die OpenID-Server von Valve akzeptieren Authentifizierungsanfragen von diesen Proxy-Hosts ohne Unterbrechung, wodurch die Sicherheitswarnung für Verbraucher außer Kraft gesetzt wird und die Anmeldung weiterhin verarbeitet wird.\n\n#\tPrimäre kommerzielle Domain\tHauptfilter\tOpenID-Authentifizierungs-Proxy-Domäne\tAuth-Filter\tRDAP Registriert\tErfassungsgrundlage\n01\trollbit.com\tBLOCKED\trbsnin.com\tCLEAN\t2026-09-18\tPASSIVE_CAPTURE\n02\tskin.club\tBLOCKED\tsc-auth.net\tCLEAN\t2019-04-02\tPASSIVE_CAPTURE\n03\thowl.gg\tBLOCKED\thowl.uno\tCLEAN\t2026-08-11\tPASSIVE_CAPTURE\n04\tduelbits.com\tBLOCKED\tswitchflips.com\tCLEAN\t2020-04-21\tPASSIVE_CAPTURE\n05\tcsgofast.com\tBLOCKED\tsteam-login.authtofast.com\tCLEAN\t2026-06-30\tPASSIVE_CAPTURE\n06\tfarmskins.com\tBLOCKED\tsteam.kobal.cc\tCLEAN\t2017-01-07\tPASSIVE_CAPTURE\n07\tcobaltlab.tech\tBLOCKED\tcobaltauth.com\tCLEAN\t2025-01-07\tPASSIVE_CAPTURE\n08\tcsgo.net\tBLOCKED\tcn2.easylot.net\tCLEAN\t2016-09-03\tPASSIVE_CAPTURE\n09\tggdrop.com\tBLOCKED\tggauth.com\tCLEAN\t2023-05-03\tPASSIVE_CAPTURE\n10\trustchance.com\tBLOCKED\thgfuihd.com\tCLEAN\t2019-01-27\tPASSIVE_CAPTURE\n11\tskin.fans\tBLOCKED\tauth.skinfans.com\tCLEAN\t2018-07-16\tPASSIVE_CAPTURE\n12\tskinport.com\tBLOCKED\tskinport.app\tCLEAN\t2020-06-20\tPASSIVE_CAPTURE\n13\tskins.cash\tBLOCKED\tskinscash.live\tCLEAN\t2019-12-05\tPASSIVE_CAPTURE\n14\ttf2hunt.com\tBLOCKED\trstspcl.com\tCLEAN\t2020-08-08\tPASSIVE_CAPTURE\n15\tdaddyskins.com\tBLOCKED\tgo-go-daddy.com\tCLEAN\t2019-01-26\tPASSIVE_CAPTURE\n16\tkey-drop.com\tBLOCKED\tkdauth.com\tCLEAN\t2026-05-13\tPASSIVE_CAPTURE\n17\tclash.gg\tBLOCKED\tclggauth.com\tCLEAN\t2024-09-16\tPASSIVE_CAPTURE\n18\tc5game.com\tBLOCKED\twww.imbastar.com\tCLEAN\t2016-02-27\tPASSIVE_CAPTURE\n19\tswap.gg\tBLOCKED\tswapauth.com\tCLEAN\t2018-10-06\tPASSIVE_CAPTURE\n20\tshadowpay.com\tBLOCKED\tthelogins.com\tCLEAN\t2018-01-22\tPASSIVE_CAPTURE\n21\tcsgocases.com\tBLOCKED\tlog-1n.com\tCLEAN\t2017-11-27\tPASSIVE_CAPTURE\n22\tcsgogem.com\tBLOCKED\tapi.csgem.com\tCLEAN\t2014-03-08\tPASSIVE_CAPTURE\n23\tgamdom.com\tBLOCKED\tlogin.gambldom.com\tCLEAN\t2017-09-24\tPASSIVE_CAPTURE\n24\t12cs.fail\tBLOCKED\tfail.games\tCLEAN\t2021-08-24\tPASSIVE_CAPTURE\n25\tskinsnipe.com\tBLOCKED\tpricing.tradeupspy.com\tCLEAN\t2020-03-11\tPASSIVE_CAPTURE\n26\tcsgobig.com\tBLOCKED\tletmeinbig.com\tCLEAN\t2023-01-20\tPASSIVE_CAPTURE\n\n* Hinweis: Passive Überprüfungen, die an nicht authentifizierten Endpunkten des „Steam Link Filter“ unter 2026-09-19 und 2026-09-21. durchgeführt wurden. Die Rohdaten der HTTP-Antworten sowie die SHA-256-Hashes werden im Repository-Datensatz (steam_tos_assets/linkfilter-2026-09-22.json) gespeichert.\n\nAbschnitt III: Anhang B – Umfassende Erhebung der geprüften Wirtschaftsunternehmen von „175“REF: EX-175-MASTER-CENSUS\n\nDas folgende Verzeichnis enthält alle kommerziellen Drittanbieterplattformen unter 175, die in der Audit-Datenbank aktiv verifiziert wurden. Jeder Datensatz enthält den Namen der Organisation, die primäre kommerzielle Domain, den beobachteten OpenID-Authentifizierungsweg Steam, die Aktivitätsklassifizierung, Zuordnungen zu Vertragsverletzungen (SSA § 2.G, SSA § 4.C, SSA § 1.C) sowie das im Quelldatensatz erfasste Aktionsfeld. Die Kennzeichnung „Siehe datierten Nachweis“ verweist den Leser auf belegende Unterlagen; sie bedeutet nicht, dass Valve keine Maßnahmen ergriffen hat. Ein fehlendes Aktionsfeld wird als „nicht festgestellt“ gemeldet.\n\nAusstellung\tName der Organisation und Hauptdomain\tBeobachtete Auth-Route / Proxy\tKlassifizierung\tVertragsverletzung\tValve Aktion\nEX-001\tCSGORoll\ncsgoroll.com\n\t\nwww.csgoroll.com\nDIRECT\n\tSkin Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-002\tCSGOEmpire\ncsgoempire.com\n\t\ncsgoempirelogin4.com\nSPLIT PROXY\n\tCasino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-003\tRollbit\nrollbit.com\n\t\nrbsnin.com\nSPLIT PROXY\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-004\t500 Casino\n500.casino\n\t\nfivezerozero.co\nSPLIT PROXY\n\tLicenced Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-005\tCSGOBig\ncsgobig.com\n\t\ncsgobig.com\nDIRECT\n\tRoulette/Slots\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-006\tCaseDrop\ncasedrop.com\n\t\ncasedrop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-007\tRustReaper\nrustreaper.com\n\t\nrustreaper.com\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-008\tBanditCamp\nbanditcamp.com\n\t\nbanditcamp.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-009\tSkinBox\nskinbox.com\n\t\nskinbox.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-010\tTastyDrop\ntastydrop.com\n\t\ntastydrop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-011\tCSGOPolygon\ncsgopolygon.gg\n\t\ncsgopolygon.gg\nDIRECT\n\tRoulette Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-012\tMagicDrop\nmagicdrop.ru\n\t\nmagicdrop.ru\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-013\tCSDice\ncsdice.com\n\t\ncsdice.com\nDIRECT\n\tDice Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-014\tRustly\nrustly.com\n\t\nrustly.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-015\tSkinOdds\nskinodds.com\n\t\nskinodds.com\nDIRECT\n\tUpgrader Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-016\tCSGOWin\ncsgowin.com\n\t\ncsgowin.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-017\tCSGORun\ncsgorun.net\n\t\ncsgorun.net\nDIRECT\n\tCrash Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-018\tOpenSkins\nopenskins.com\n\t\nopenskins.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-019\tRustBet\nrustbet.com\n\t\nrustbet.com\nDIRECT\n\tRust Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-020\tCSGOMagic\ncsgomagic.com\n\t\ncsgomagic.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-021\tCSGOBounty\ncsgobounty.com\n\t\ncsgobounty.com\nDIRECT\n\tUpgrader/Contract\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-022\tEZSkins\nezskins.com\n\t\nezskins.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-023\tRustCases\nrustcases.com\n\t\nrustcases.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-024\tCSGOReaper\ncsgoreaper.com\n\t\ncsgoreaper.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-025\tCSGOCases\ncsgocases.com\n\t\ncsgocases.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-026\tCSGO-Skins\ncsgo-skins.com\n\t\ncsgo-skins.com\nDIRECT\n\tCase Upgrader\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-027\tCSGONet\ncsgonet.com\n\t\ncsgonet.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-028\tWTFSkins\nwtfskins.com\n\t\nwtfskins.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-029\tCSGOFast\ncsgofast.com\n\t\nsteam-login.authtofast.com\nSPLIT PROXY\n\tRoulette Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-030\tDuelbits\nduelbits.com\n\t\nswitchflips.com\nSPLIT PROXY\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-031\tFlameCases\nflamecases.com\n\t\nflamecases.com\nDIRECT\n\tCase Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-032\tFarmskins\nfarmskins.com\n\t\nsteam.kobal.cc\nSPLIT PROXY\n\tCase Opener\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-033\tCSGOLuck\ncsgoluck.com\n\t\ncsgoluck.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-034\tGamedom\ngamedom.com\n\t\ngamedom.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-035\tSkin.Club\nskin.club\n\t\nsc-auth.net\nSPLIT PROXY\n\tCase Battles\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-036\tDaddySkins\ndaddyskins.com\n\t\ndaddyskins.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-037\tInsane.gg\ninsane.gg\n\t\napi.insane.gg\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-038\tRustix\nrustix.gg\n\t\nrustix.gg\nDIRECT\n\tRust Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-039\tSkins.Club\nskins.club\n\t\nskins.club\nDIRECT\n\tSkin Upgrade\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-040\tCSGOHouse\ncsgohouse.org\n\t\ncsgohouse.org\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-041\tSkinRave\nskinrave.net\n\t\nskinrave.net\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-042\tBloodyCase_GG\nbloodycase.gg\n\t\nbloodycase.gg\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-043\tCSGOClicker\ncsgoclicker.com\n\t\ncsgoclicker.com\nDIRECT\n\tClicker/Upgrade\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-044\tRustBet_GG\nrustbet.gg\n\t\nrustbet.gg\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-045\tCS_Drop\ncs-drop.com\n\t\ncs-drop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-046\tHellStore\nhellstore.net\n\t\nhellstore.net\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-047\tRustLoot\nrustloot.com\n\t\nrustloot.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-048\tCSGO_Case\ncsgo-case.com\n\t\ncsgo-case.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-049\tCS2Skin\ncs2skin.com\n\t\ncs2skin.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-050\tJuice_GG\njuice.gg\n\t\nletmeinjuice.com\nSPLIT PROXY\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-051\tGGDrop\nggdrop.com\n\t\nggauth.com\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-052\tCSGOGem\ncsgogem.com\n\t\ncsgogem.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-053\tRainbet\nrainbet.com\n\t\nservices.rainbet.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-054\tHowl_GG\nhowl.gg\n\t\nhowl.uno\nSPLIT PROXY\n\tSkins Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-055\tChicken_GG\nchicken.gg\n\t\nchicken.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-056\tCSGOCasino_GG\ncsgocasino.gg\n\t\napi.csgocasino.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-057\tHunt_GG\nhunt.gg\n\t\napi.hunt.gg\nDIRECT\n\tSkins Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-058\tCSBattle\ncsbattle.com\n\t\ncsbattle.com\nDIRECT\n\tCase Battles\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-059\tSkinRave_GG\nskinrave.gg\n\t\napi.skinrave.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-060\tCSDouble\ncsdouble.gg\n\t\ncsdouble.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-061\tRustChance\nrustchance.com\n\t\nhgfuihd.com\nSPLIT PROXY\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-062\tRustClash\nrustclash.com\n\t\nrustclash.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-063\tCobaltLab\ncobaltlab.tech\n\t\ncobaltauth.com\nSPLIT PROXY\n\tRust Automation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-064\tRaided_GG\nraided.gg\n\t\napi.raided.gg\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-065\tRustNeo\nrustneo.gg\n\t\nrustneo.gg\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-066\tSplits_GG\nsplits.gg\n\t\nsplits.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-067\tUpgrader_Pro\nupgrader.pro\n\t\nupgauth.space\nSPLIT PROXY\n\tSkin Upgrader\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-068\tSkinFans\nskin.fans\n\t\nauth.skinfans.com\nSPLIT PROXY\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-069\tHotPizza\nhotpizza.one\n\t\nhotpizza.one\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-070\tG4Skins\ng4skins.com\n\t\nauth.g4s.to\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-071\t12CS_Fail\n12cs.fail\n\t\n12cs.fail\nDIRECT\n\tCrash Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-072\tTF2Royal\ntf2royal.com\n\t\ntf2auth.com\nSPLIT PROXY\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-073\tTF2Easy\nwww.tf2easy.com\n\t\nwww.tf2easy.com\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-074\tTF2Hunt\ntf2hunt.com\n\t\nrstspcl.com\nSPLIT PROXY\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-075\tTF2Bet\ntf2.bet/coinflip\n\t\ntf2.bet\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-076\tTF2Blaze\ntf2blaze.com\n\t\ntf2blaze.com\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-077\tOpenStars_GG\nopenstars.gg\n\t\nopenstars.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-078\tShuffle_Com\nshuffle.com\n\t\nshuffle.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-079\tSkins.com\nskins.com\n\t\napi.skins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-080\tWhite.Market\nwhite.market\n\t\nwhite.market\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-081\tBuff.Market\nbuff.market\n\t\nbuff.market\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-082\tAvan.Market\navan.market\n\t\navan.market\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-083\tCS.MONEY\ncs.money\n\t\nauth.dota.trade\nSPLIT PROXY\n\tTrading Engine\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-084\tUUSkins\nuuskins.com\n\t\nuuskins.com\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-085\tYouPin898\nyoupin898.com\n\t\nyoupin898.com\nDIRECT\n\tMass Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-086\tMoon.Market\nmoon.market\n\t\nmoon.market\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-087\tCSFloat\ncsfloat.com\n\t\ncsgofloat.com\nSPLIT PROXY\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-088\tSkin.Land\nskin.land\n\t\nauth.skin.land\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-089\tC5Game\nc5game.com\n\t\nc5game.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-090\tHaloSkins\nhaloskins.com\n\t\nhaloskins.com\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-091\tBuff.163\nbuff.163.com\n\t\nbuff.163.com\nDIRECT\n\tCorporate Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-092\tWaxpeer\nwaxpeer.com\n\t\nwaxpeer.com\nDIRECT\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-093\tCS.MONEY Bot\ncs.money\n\t\nauth.dota.trade\nSPLIT PROXY\n\tBot Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-094\tMarket.CSGO\nmarket.csgo.com\n\t\ndota2.net\nSPLIT PROXY\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-095\tSkinport\nskinport.com\n\t\nskinport.app\nSPLIT PROXY\n\tRegulated Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-096\tSkinFlow\nskinflow.gg\n\t\napi.skinflow.gg\nDIRECT\n\tMarketplace/Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-097\tDMarket\ndmarket.com\n\t\ndmarket.com\nDIRECT\n\tUS Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-098\tSkin.place\nskin.place\n\t\napi.skin.place\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-099\tSkinsMonkey\nskinsmonkey.com\n\t\nskinsmonkey.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-100\tSkinBaron\nskinbaron.de\n\t\nskinbaron.com\nSPLIT PROXY\n\tCorporate Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-101\tSteam\nsteamcommunity.com/market\n\t\nsteamcommunity.com/market\nDIRECT\n\tOfficial Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-102\tRustTM\nrust.tm\n\t\ndota2.net\nSPLIT PROXY\n\tRust Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-103\tPirateSwap\npirateswap.com\n\t\nlogin.pirateswap.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-104\tMannco.Store\nmannco.store\n\t\nmannco.store\nDIRECT\n\tTF2 Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-105\tSkinSwap\nskinswap.com\n\t\napi.skinswap.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-106\tLootFarm\nlootfarm.com\n\t\nlootfarm.com\nDIRECT\n\tTrading Platform\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-107\tRustskins\nrustskins.com\n\t\nrustskins.com\nDIRECT\n\tRust Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-108\tExeSkins\nexeskins.com\n\t\nexeskins.com\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-109\tBalticSkins\nbalticskins.com\n\t\nbalticskins.com\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-110\tCS.Trade\ncs.trade\n\t\ncs.trade\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-111\tRapidSkins\nrapidskins.com\n\t\napi.rapidskins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-112\tTradeIt\ntradeit.gg\n\t\nconnect-tradeit.com\nSPLIT PROXY\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-113\tKrakatoa\nkrakatoa.com\n\t\nkrakatoa.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-114\tShadowPay\nshadowpay.com\n\t\nshadowpay.com\nDIRECT\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-115\t49skins\n49skins.com\n\t\napi.49skins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-116\tSkinVault\nskinvault.gg\n\t\napi.skinvault.gg\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-117\tAim Market\naim.market\n\t\naim.market\nDIRECT\n\tSkins Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-118\tSkinout\nskinout.gg\n\t\nauth.skinout.gg\nDIRECT\n\tInstant Sell Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-119\tNTSkins\nntskins.com\n\t\nntskins.com\nDIRECT\n\tSkins Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-120\tIGXE\nigxe.cn\n\t\nigxe.cn\nDIRECT\n\tChinese Powerhouse\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-121\tSwap.gg\nswap.gg\n\t\nswap.gg\nDIRECT\n\tAutomated Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-122\tBitskins\nbitskins.com\n\t\nbitskins.com\nDIRECT\n\tCash-out Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-123\tGamerPay\ngamerpay.gg\n\t\ngamerpay.gg\nDIRECT\n\tP2P Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-124\tTF2Mart\ntf2mart.com\n\t\ntf2mart.com\nDIRECT\n\tTF2 Automation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-125\tSkinBid\nskinbid.com\n\t\nskinbid.com\nDIRECT\n\tSkin Auctions\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-126\tLootBear\nlootbear.com\n\t\nlootbear.com\nDIRECT\n\tSkin Rental\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-127\tBackpack.tf\nbackpack.tf\n\t\nbackpack.tf\nDIRECT\n\tTF2 Valuation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-128\tScrap.tf\nscrap.tf\n\t\nscrap.tf\nDIRECT\n\tTF2 Scrap Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-129\tMarketplace.tf\nmarketplace.tf\n\t\nmarketplace.tf\nDIRECT\n\tTF2 Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-130\tSTNTrading\nstntrading.eu\n\t\nstntrading.eu\nDIRECT\n\tTF2 Botnet\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-131\tSkins.Cash\nskins.cash\n\t\nskinscash.live\nSPLIT PROXY\n\tInstant Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-132\tSkinWallet\nskinwallet.com\n\t\nskinwallet.com\nDIRECT\n\tInstant Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-133\tDota2Market\ndota2market.com\n\t\ndota2market.com\nDIRECT\n\tDota 2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-134\tCSGO.NET\ncsgo.net\n\t\ncn2.easylot.net\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-135\tCybershoke\ncybershoke.net\n\t\nauth.cybershoke.net\nDIRECT\n\tCommunity Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-136\tXPlay_GG\nxplay.gg\n\t\nxplay.gg\nDIRECT\n\tServer Network\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-137\tFastCup\nfastcup.net\n\t\napi.fastcup.net\nDIRECT\n\tMatchmaker Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-138\tEsportal\nesportal.com\n\t\nesportal.com\nDIRECT\n\tMatchmaking Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-139\tGamersClub\ngamersclub.com.br\n\t\ngamersclub.com.br\nDIRECT\n\tLATAM Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-140\tLeetify\nleetify.com\n\t\nleetify.com\nDIRECT\n\tSaaS Analytics\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-141\tScope_GG\nscope.gg\n\t\nscope.gg\nDIRECT\n\tSaaS Analytics\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-142\tTradeUpSpy\ntradeupspy.com\n\t\napi.tradeupspy.com\nDIRECT\n\tSaaS Tools\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-143\tEpidemic_GG\nepidemic.gg\n\t\nepidemic.gg\nDIRECT\n\tSaaS Tools\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-144\tCSDeals\ncs.deals\n\t\napi.cs.deals\nDIRECT\n\tMarketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-145\tPricempire\npricempire.com\n\t\npricempire.com\nDIRECT\n\tSaaS Price DB\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-146\tCS2Stash\ncs2stash.com\n\t\ncs2stash.com\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-147\tCSGOSkins\ncsgoskins.gg\n\t\ncsgoskins.gg\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-148\tSteamAnalyst\nsteamanalyst.com\n\t\nsteamanalyst.com\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-149\tSteamCardExchange\nsteamcardexchange.net\n\t\nsteamcardexchange.net\nDIRECT\n\tTrading Exchange\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-150\tDotaBuff\ndotabuff.com\n\t\ndotabuff.com\nDIRECT\n\tSaaS Tracker\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-151\tTracker_GG\ntracker.gg\n\t\ntracker.gg\nDIRECT\n\tSaaS Tracker\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-152\tFSB Market (an anonymized label; the original name is withheld here)\nFSB Market\n\t\nFSB Market\nDIRECT\n\tMass Blackmarket\tSSA § 2.G, SSA § 4.C, SSA § 1.C\tSee dated evidence\nEX-153\tFunPay\nfunpay.com\n\t\nfunpay.com\nDIRECT\n\tAccount Exchange\tSSA § 2.G, SSA § 4.C, SSA § 1.C\tSee dated evidence\nEX-154\tPlayerAuctions\nplayerauctions.com\n\t\nplayerauctions.com\nDIRECT\n\tGrey Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-155\tEldorado.gg\neldorado.gg\n\t\neldorado.gg\nDIRECT\n\tAccount Portal\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-156\tG2A\ng2a.com\n\t\ng2a.com\nDIRECT\n\tMass Key Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-157\tKinguin\nkinguin.net\n\t\nkinguin.net\nDIRECT\n\tMass Key Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-158\tG2G.com\ng2g.com\n\t\ng2g.com\nDIRECT\n\tVirtual Services\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-159\tPlayerup\nplayerup.com\n\t\nplayerup.com\nDIRECT\n\tAccount Broker\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-160\tZ2U.com\nz2u.com\n\t\nwww.z2u.com\nDIRECT\n\tReady-Account Hub\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-161\tSmurfHub\nsmurfhub.net\n\t\nsmurfhub.net\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-162\tSmurfAccounts\nsmurfaccounts.com\n\t\nsmurfaccounts.com\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-163\tBuyCSGORank\nbuycsgorank.com\n\t\nbuycsgorank.com\nDIRECT\n\tRank Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-164\tCSGOSmurfKings\ncsgosmurfkings.com\n\t\ncsgosmurfkings.com\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-165\tSmurfStore_Co\nsmurfstore.co\n\t\nsmurfstore.co\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-166\tSteamLvlUp\nsteamlvlup.com\n\t\nsteamlvlup.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-167\tSteamLevels\nsteamlevels.com\n\t\nsteamlevels.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-168\tLevelSteam\nlevelsteam.com\n\t\nlevelsteam.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-169\tSteamLevelU\nsteamlevelu.com\n\t\nsteamlevelu.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-170\tEloKing\neloking.com\n\t\neloking.com\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-171\tBoosteria\nboosteria.org\n\t\nboosteria.org\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-172\tOvergear\novergear.com\n\t\novergear.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-173\tBlazingBoost\nblazingboost.com\n\t\nblazingboost.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-174\tDota2Boost\ndota2boost.com\n\t\ndota2boost.com\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-175\tBuyBoost\nbuyboost.com\n\t\nbuyboost.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nAbschnitt IV: Technische Architektur und AuthentifizierungsmechanismenREF: TECH-ANALYSIS-01\n\n1. Fehlende Überprüfung der Domain-Inhaberschaft in OpenID-2.0: Die von Valve entwickelte Implementierung des OpenID-2.0-Protokolls (https://steamcommunity.com/openid/login) bewertet die openid.return_to sowie openid.realm Parameter, ohne dass eine vorherige Registrierung als Entwickler, eine kryptografische Überprüfung oder eine Validierung des Domain-Eigentums erforderlich ist. Jeder kommerzielle Betreiber kann Nutzer auf den Anmeldebildschirm von Valve weiterleiten und eine kryptografisch signierte Identitätsbescheinigung (die die Steam-ID „64-“ enthält) erhalten, die auf beliebige Domains umgeleitet wird.\n\n2. Programmatische Abfrage des Inventars und Missbrauch von „API“-Schlüsseln: Sobald die Benutzerauthentifizierung über OpenID bestätigt ist, fragen die Betreiber Endpunkte öffentlicher und Partner-WebAPI-Endpunkte ab (IEconItems_730/GetPlayerItems), um Bestandswerte in Echtzeit zu indexieren. Automatisierte Handelsnetzwerke nutzen programmatische Sitzungstoken, um Peer-to-Peer-Handelsangebote (P2P) einzureichen, abzufragen und anzunehmen, was in direktem Widerspruch zum Verbot nicht-menschlicher Interaktion gemäß SSA §4.C steht.\n\n3. Asymmetrie bei Link-Filtern: Das Nebeneinanderbestehen von Warnmeldungen zu Domainnamen für Endnutzer und voll funktionsfähigen Authentifizierungsendpunkten führt zu einem regulatorischen Widerspruch: Die Sicherheitstelemetrie von Valve stuft diese Betreiber als „potenziell bösartig“ ein, während die Authentifizierungsinfrastruktur von Valve deren Nutzer weiterhin authentifiziert.\n\nBeweismethodik und Erklärung zur Beweiskette\n\nDieses Dokument wurde auf der Grundlage von nicht authentifizierten Netzwerkaufzeichnungen, historischen Abfragen der Registrierungsdatenbank „RDAP“ sowie verifizierten kryptografischen Hash-Manifesten erstellt. Es wurden keine Anmeldedaten von Benutzern auf Sicherheitslücken geprüft oder verarbeitet. Alle Ergebnisse spiegeln den beobachtbaren Zustand des Produktionsnetzwerks zum Stand vom September 2026. wider. Dieses Dokument dient als überparteiliche technische Anlage, die für gerichtliche, behördliche und öffentliche Anfragen erstellt wurde.\n\nZUSAMMENFASSUNG: SHA-256-VERIFIZIERT\nc507c9025f93da0aadaf395c4d8882f25973211c318ee8e9b6f18a5b3755e050\nARCHIV: ÖFFENTLICHE RECHTSAKTE\nAUSGESTELLT UND UNTERZEICHNET VON: phishdestroy.io · Koalition für forensische Forschung\nRECHTLICHER STATUS: ALLE RECHTE AN DIE MENSCHHEIT ABGETRETEN · CC0 UNIVERSAL PUBLIC DOMAIN",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Gesetz über die forensische Wirtschaftsprüfung und aufsichtsrechtlicher Anhang"
          }
        ],
        "links": []
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/de/regulatory_act_print.content.json",
      "export_json_sha256": "764f645f2d4f2f1ab80be70036c4ce02792214a64a0d8588b31c2a65a156c04d"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "de/security_timeline.html",
      "language": "de",
      "title": "Chronologie der Sicherheitsvorfälle – Das Dossier „Steam“",
      "source_url": "https://phishdestroy.io/steam_dossier/de/security_timeline",
      "source_html_sha256": "b9747970ca988b63d3c7897943a81840b5d15eeeca686f30edef00f9797bfe20",
      "exported_at": "2026-09-29T00:16:12.868Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "security_timeline.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/de/security_timeline.pdf?v=print-20260929-v5",
        "sha256": "ff8f43c5aedcc3306212f1c0bfea276722295b8d4253f878550a63c98c39d8e7",
        "bytes": 99220,
        "pages": 7
      },
      "integrity": {
        "signed_object": "security_timeline.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "security_timeline.content.json.asc",
        "digest_file": "security_timeline.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify security_timeline.content.json.asc security_timeline.content.json",
          "sha256sum -c security_timeline.content.json.sha256"
        ]
      },
      "content": {
        "text": "DIE SICHERHEITSBILANZAUSSTELLUNG / BEITRÄGE ZU „16“\n\n2018 — 2026\n\nSicherheits-Zeitleiste – Von „2018“ zu „2026“\n\nDie Sicherheitsvorkehrungen wurden geändert. Folgen Sie dem Protokoll.\n\nWAS DIESER ABSCHNITT BELEGT\n\nDiese chronologische Aufzeichnung rekonstruiert acht Jahre Sicherheitsanpassungen im Handels- und Authentifizierungsstack von Steam. Sie verfolgt die 2018 7-Implementierung der Tageshandelssperre, 2023 Web-API die Bestätigung per Mobilschlüssel sowie die 2026 Abschaffung von Sitzungstoken im Zusammenhang mit dokumentierten Umgehungstechniken. Die Zeitleiste belegt, dass Plattform-Updates stets hinter bekannten Exploit-Vektoren zurückblieben, während strukturelle Vorteile für kommerzielle Betreiber erhalten blieben.\n\n← Zurück zum Executive Briefing\n\nHandelsbeschränkungen. Zugangskontrollen. Beschränkungen der „API“. Eine chronologische Aufstellung dessen, was sich geändert hat – und was die Quellen tatsächlich belegen.\n\nEntdecken Sie die Zeitleiste ↓\nACHT JAHRE. EIN ALBUM.16zu untersuchende Meilensteine\n\nJeder Eintrag behält sein Eingabedatum und seine Quelle bei. Die Überprüfung wird daneben angezeigt.\n\nREZENSION / 24 SEP 2026\n10Bestätigte Veranstaltung und Datum\n06Teilweise überprüft\n00Quelleninkongruenz\n00Quelle erforderlich\nSo lesen Sie diesen Datensatz\n\nBestätigte Veranstaltung und Datum: beides durch eine aussagekräftige Primärquelle belegt. Teilweise überprüft: Eine damit zusammenhängende Änderung ist dokumentiert, doch das Datum oder der Umfang sind noch nicht geklärt. Quellenkonflikt: Das verlinkte Material stützt die vorgebrachte Behauptung nicht. Quelle erforderlich: Im Rahmen dieser Überprüfung konnte keine übereinstimmende datierte Quelle verifiziert werden. Ein ungeklärter Eintrag ist kein Beweis dafür, dass ein Ereignis nicht stattgefunden hat.\n\nDie Datumsangaben bei ungeklärten Einträgen beziehen sich auf das Datum der Einreichung und nicht auf das verifizierte Veröffentlichungsdatum. Der ursprüngliche Untersuchungstext wurde nicht umgeschrieben.\n\nDie Chronologie\n01 — 16\nDen Datensatz durchsuchenThemaBeweiseBestellung\n\n16 16-Einträge · neueste zuerst\n\n202609-01Eingereicht am\nGemeinschaftTeilweise überprüft\nWarnungen vor verdächtigen Nachrichten in Gruppenchats\n\nEine offizielle Beta-Mitteilung bestätigt die Funktion am 31. August. Für das angegebene Veröffentlichungsdatum der stabilen Version am 1. September fehlt noch die entsprechende Release-Note.\n\nSteam Client-Beta – 31. August ↗archiviert unter 2026-03-13 ↗\nUrsprünglicher Eintrag & eingereichter Link\n\nAutomatische Kennzeichnung verdächtiger Chats\n\nDen eingereichten Quellcode prüfen ↗\n202601-16Datum der Überprüfung\nAPIBestätigte Veranstaltung und Datum\nDetaillierte Berechtigungen und IP-Whitelisting für Publisher-Schlüssel (Ankündigung auf Valve)\n\nAm 16. Januar 2026, veröffentlichte Valve eine offizielle Steamworks-Mitteilung („NEU: Bessere Berechtigungen und Steuerungsmöglichkeiten für Web-API-Schlüssel“), in dem neue Tools für detaillierte Berechtigungen vorgestellt werden, mit denen Entwickler Web-API-Schlüssel in einzelne Gruppen unterteilen können (Allgemeines, Mikrotransaktionen, Wirtschaft und Umsatzdaten), Schlüssel auf bestimmte App-IDs beschränken und eine Whitelist für Server-IP-Adressen durchsetzen.\n\nDie eklatante Doppelmoral: Mit dieser offiziellen Bekanntmachung wird bestätigt, dass Valve die technische Infrastruktur für detaillierte Berechtigungen für „API“ und IP-Beschränkungen vollständig entwickelt hat, jedoch sie bewusst vor normalen Benutzerkonten zurückhält (steamcommunity.com/dev/apikey). Die üblichen Benutzer-API-Schlüssel sind nach wie vor monolithische „Alles-oder-nichts“-Zugangsdaten ohne IP-Whitelisting – und genau diese technische Lücke ermöglicht die millionenschwere Branche der Handelsüberwachung unter API.\n\nValve Ankündigung – NEU: Bessere Berechtigungen und Kontrollmöglichkeiten für Web-API-Schlüssel (16 Jan 2026) ↗· Dokumentation: Steamworks-Web-API-Authentifizierung ↗\nUrsprünglicher Eintrag & eingereichter Link\n\nSteamworks-WebAPI-Granular-Scopes\n\nSeht euch die offizielle Steamworks-Ankündigung zu „Valve“ an (493839547938902179) ↗\n202507-15Datum der Überprüfung\nHandelBestätigte Veranstaltung und Datum\nCS2-Trades erhalten ein siebentägiges Umkehrfenster\n\nIn der Ankündigung von Valve vom [Datum] wird die Rückabwicklung von Counter-Strike-Gegenstandstransaktionen der letzten sieben Tage eingeführt. Diese Maßnahme soll zwar Hijacking eindämmen, jedoch können wirtschaftliche Prüfungen durch Dritte (CSMarketCap ↗) verzeichnete einen $104M (-25%) zusammenbrechen bei der Marktkapitalisierung innerhalb von 24 Stunden aufgrund einer Störung im Kassahandel. Wie aus der Analyse von Skinvault ↗, die Auslösung einer Umkehr führt zu einer automatischen 30--Tageshandelssperre für das Konto. Im Sommer 2026, Valve wurde von globalen Resets um Mitternacht UTC auf individuelle, pro Artikel festgelegte Minutentimer umgestellt (Skin.land ↗).\n\nValve — 15 Ankündigung vom 2025 ↗· CSMarketCap-Analyse ↗\nUrsprünglicher Eintrag & eingereichter Link\n\nCS2-Handelschutz / Rücktrittsfrist\n\nDen eingereichten Quellcode prüfen ↗\n202505-14Datum der Überprüfung\nAuthentifizierungBestätigte Veranstaltung und Datum\nValve veröffentlicht eine Sicherheitswarnung bezüglich SMS-Lecks\n\nDie offizielle Mitteilung von Valve vom Mai 14, 2025, befasst sich mit der Kontosicherheit und SMS-basierten Authentifizierungsverfahren. Die Mitteilung konzentriert sich zwar auf SMS-Lecks und bestätigt, dass keine Systeme von Steam kompromittiert wurden, dient jedoch als offizielles Sicherheitsupdate zum angegebenen Datum.\n\nValve — Ein Hinweis zur Sicherheit Ihres „Steam“-Kontos ↗\nUrsprünglicher Eintrag & eingereichter Link\n\nMitteilung zur Kontosicherheit\n\nDen eingereichten Quellcode prüfen ↗\n202410-02Datum der Überprüfung\nHandelBestätigte Veranstaltung und Datum\nSieben Tage vor dem erneuten Handel oder der erneuten Vermarktung\n\nDie Versionshinweise beziehen sich auf Gegenstände, die über den Ingame-Shop erworben wurden, darunter die Rüstkammer, Tauschangebote und den Community-Markt. Der dokumentierte Umfang geht über die Gegenstände der Rüstkammer hinaus.\n\nValve — Versionshinweise zu „10/2/2024“ ↗\nUrsprünglicher Eintrag & eingereichter Link\n\nCS2 „The Armory“ / „7-“ – Tages-Hold\n\nDen eingereichten Quellcode prüfen ↗\n202409-18Eingereicht am\nHandelTeilweise überprüft\nEinschränkungen für neue Geräte auf den Hilfeseiten überprüft\n\nDie offizielle Support-Dokumentation von Steam bestätigt eine Beschränkung des Tageshandels unter 7-bei der Anmeldung von einem neuen Gerät aus, das seit mindestens 7 Tagen nicht autorisiert wurde. Obwohl das genaue Einführungsdatum vom 18, 2024, nicht als Meilenstein im Changelog vermerkt ist, ist die Funktionalität vollständig dokumentiert.\n\nSteam Support – Handels- und Marktbeschränkungen ↗\nUrsprünglicher Eintrag & eingereichter Link\n\nAnmeldung auf einem neuen Gerät – Handelsbeschränkung\n\nDen eingereichten Quellcode prüfen ↗\n202402-14Eingereicht am\nGemeinschaftTeilweise überprüft\nIn „2024“ wurde eine Wartezeit für Namensänderungen bei Tauschgeschäften eingeführt\n\nCommunity- und Entwickleraufzeichnungen bestätigen, dass „2024,“ (Valve) Anfang Februar 2-eine unangekündigte Abklingzeit von4 Stunden unmittelbar nach einer Änderung des Profilnamens eingeführt hat, um Betrugsversuche durch schnelle Identitätswechsel einzudämmen. Da Valve zu dieser Einschränkung keine offizielle Pressemitteilung, kein Client-Changelog und keinen Support-Artikel veröffentlicht hat, fehlt für das angegebene Datum im Februar 14 eine formelle Bestätigung; der Leitfaden im Steam Workshop dient eher als indirekte Bestätigung durch die Community denn als offizielle Valve Dokumentation.\n\nSteam Workshop-Leitfaden (indirekte Bestätigung) – Einzelheiten zur Beschränkung der Namensänderung ↗\nUrsprünglicher Eintrag & eingereichter Link\n\nProfilname / Avatar-Änderung zurückgestellt\n\nDen eingereichten Quellcode prüfen ↗\n202312-04Datum der Überprüfung\nAPIBestätigte Veranstaltung und Datum\nZur Schlüsselerstellung ist eine Bestätigung per Handy erforderlich\n\nDie Einführung der obligatorischen mobilen Bestätigung per „Steam Guard“ für die Schlüsselerstellung im Web unter API erfolgte nachweislich Ende 2023,, wie aus Bibliotheken von Drittanbietern hervorgeht. Das genaue Datum vom Dezember 4, 2023, entspricht dem in der Entwickler-Community beobachteten Rollout-Zeitraum.\n\nDokumentation für Betreuer – März 2024 ↗archiviert unter 2026-09-24 ↗\nUrsprünglicher Eintrag & eingereichter Link\n\nBestätigung per Handy für „API“-Schlüssel\n\nDen eingereichten Quellcode prüfen ↗\n202310-24Datum der Überprüfung\nEntwicklerBestätigte Veranstaltung und Datum\nDie obligatorische „2“-FA für die Freischaltung von Spiel-Builds tritt in Kraft\n\nDie offizielle Steamworks-Ankündigung von Valve vom Oktober 10, 2023, bestätigt, dass ab dem Oktober 24, 2023, jedes Konto, das einen Build auf dem Standardzweig einer veröffentlichten Anwendung live schaltet, die Änderung per SMS oder über die Steam-App autorisieren muss. Diese Änderung führte zu einer direkten Aktualisierung der SetAppBuildLive-Webseite API.\n\nSteamworks – Sicherheitsverbesserungen bei der Verwaltung von Builds und Benutzern ↗archiviert unter 2025-12-03 ↗\nUrsprünglicher Eintrag & eingereichter Link\n\nSMS-MFA für die Veröffentlichung von Spiel-Builds\n\nDen eingereichten Quellcode prüfen ↗\n202307-12Eingereicht am\nGemeinschaftTeilweise überprüft\nVon der Community festgestellte Inhaltswarnungen in benutzerdefinierten Biografien\n\nSteam Community-Meldungen ab Juli unter 2023 belegen, dass benutzerdefinierte Profilbeschreibungen, die externe Links oder Auslösewörter enthielten, plötzlich automatische Inhaltswarnungen anzeigten. Das Datum der Meldung vom Juli unter 12, 2023, stimmt mit der ersten Welle von Nutzerberichten in den Community-Foren unter Steam überein.\n\nSteam Community-Forum – Meldungen zu Bio-Inhalten ↗\nUrsprünglicher Eintrag & eingereichter Link\n\nWarnhinweis zu benutzerdefinierten Biografieinhalten\n\nDen eingereichten Quellcode prüfen ↗\n202301-25Eingereicht am\nGemeinschaftTeilweise überprüft\nFilterung von Profil-Links und Wartezeiten für Bearbeitungen sind aktiv\n\nDie offizielle Support-Dokumentation von Steam bestätigt, dass Links in benutzerdefinierten Biografien gefiltert werden und missbräuchliche Änderungen des Namens oder des Avatars zu Bearbeitungssperren führen können. Während die genaue Einführung der einstündigen Wartezeit 4-am 1. Januar 25, 2023, den beobachteten Beginn darstellt, ist der Mechanismus zur Linkfilterung selbst laut der bereitgestellten Hilfeseite bereits voll funktionsfähig.\n\nSteam Support – Einschränkungen bezüglich Profilname und Avatar ↗\nUrsprünglicher Eintrag & eingereichter Link\n\nProfil-LINK ENTFERNT / Abklingzeit\n\nDen eingereichten Quellcode prüfen ↗\n202210-24Datum der Überprüfung\nAuthentifizierungBestätigte Veranstaltung und Datum\nSteam Umstellung der Clients auf OAuth-Aktualisierungs- und Zugriffstoken\n\nDie wichtigsten Kunden- und App-Updates von Valve im Oktober 2022 hat das Authentifizierungssystem von Steam grundlegend überarbeitet. Die alte Struktur mit Sitzungs-Cookies wurde durch OAuth-basierte Zugriffs- und Aktualisierungstoken ersetzt, und es wurde eine Liste der aktiven, autorisierten Geräte eingeführt, um die manuelle Aufhebung aktiver Sitzungen zu ermöglichen.\n\nValve — Aktualisierung der „Steam“-App und Überarbeitung des Authentifizierungsverfahrens ↗\nUrsprünglicher Eintrag & eingereichter Link\n\nSteam Überarbeitung des Anmeldeprozesses / Kürzung von Cookies\n\nAnkündigung zu „Valve“ ansehen ↗\n202210-12Datum der Überprüfung\nAuthentifizierungBestätigte Veranstaltung und Datum\nQR-Code-Anmeldung und Verwaltung autorisierter Geräte\n\nIn der Ankündigung von Valve vom 12. Oktober werden die Anmeldung per QR-Code, die Genehmigung oder Ablehnung von Anmeldungen sowie eine Geräteliste beschrieben, über die der Zugriff auf das Konto widerrufen werden kann.\n\nValve — Die aktualisierte „Steam“-App ist ab sofort verfügbar ↗\nUrsprünglicher Eintrag & eingereichter Link\n\nSteam 3.0en zur mobilen App / QR-Anmeldung\n\nDen eingereichten Quellcode prüfen ↗\n202205-10Eingereicht am\nAPITeilweise überprüft\nEndpunkte für die Stornierung von Transaktionen wurden aus der öffentlichen Liste „API“ entfernt\n\nEntwickleraufzeichnungen bestätigen, dass im Mai 2022, Valve stillschweigend Endpunkte für die Handelsverwaltung wie IEconService/CancelTradeOffer und DeclineTradeOffer aus dem Web-API entfernt wurden (dokumentiert in node-steam-tradeoffer-manager #325). Zwar funktionieren die Methoden in privaten Client-Protokollen weiterhin, doch das Datum vom 10, 2022, markiert ihre beobachtete Entfernung aus öffentlichen Web-APIs zur Bekämpfung von Betrugs-Panels.\n\nEntwicklerdiskussion – Issue Nr.325 (CancelTradeOffer entfernt) ↗· Steamworks-WebAPI – IEconService-Dokumentation ↗\nUrsprünglicher Eintrag & eingereichter Link\n\nEntfernung von Endpunkten für die Stornierung von Handelsgeschäften\n\nKnoten „node-steam-tradeoffer-manager“ prüfen – Issue Nr.325 ↗\n202005-25Datum der Überprüfung\nHandelBestätigte Veranstaltung und Datum\nDota-2-Gegenstände unterliegen einer siebentägigen Handelssperre\n\nAm 25, 2020, wurde zeitgleich mit der Veröffentlichung des Battle Passes für das „10“ (blog.dota2.com/2020/05/the-international-10-battle-pass/) Valve eine eintägige Handelssperre (7-) für Dota-2-Gegenstände eingeführt, die der 2018 Counter-Strike-Richtlinie entspricht. Diese Einschränkung gilt für alle getauschten Gegenstände und Marktkäufe.\n\nDota-2-Community – Trade Lock und TI10-Client-Update ↗\nUrsprünglicher Eintrag & eingereichter Link\n\nDota 2 / 7-Day-Trade-Sperre\n\nDen eingereichten Quellcode prüfen ↗\n201803-29Datum der Überprüfung\nHandelBestätigte Veranstaltung und Datum\nFür getauschte CS:GO-Gegenstände gilt eine siebentägige Wartezeit\n\nDie offiziellen Versionshinweise bestätigen das Datum und die Einschränkung. Die angegebene URL leitete zu einem Karten-Update unter 2013 weiter; die entsprechende URL in den Versionshinweisen endet auf 20309.\n\nValve — Versionshinweise zu „3/29/2018“ ↗\nUrsprünglicher Eintrag & eingereichter Link\n\nCS:GO / „7-“ – Day-Trade-Sperre\n\nDen eingereichten Quellcode prüfen ↗ archiviert unter 2025-02-26 ↗\n\nFolgen Sie den Beweisen. Prüfen Sie die Quelle.\n\nZurück zur Untersuchung ↗",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Sicherheits-Zeitleiste – Von „2018“ zu „2026“"
          },
          {
            "level": 2,
            "id": null,
            "text": "Die Chronologie"
          },
          {
            "level": 2,
            "id": null,
            "text": "Warnungen vor verdächtigen Nachrichten in Gruppenchats"
          },
          {
            "level": 2,
            "id": null,
            "text": "Detaillierte Berechtigungen und IP-Whitelisting für Publisher-Schlüssel (Ankündigung auf Valve)"
          },
          {
            "level": 2,
            "id": null,
            "text": "CS2-Trades erhalten ein siebentägiges Umkehrfenster"
          },
          {
            "level": 2,
            "id": null,
            "text": "Valve veröffentlicht eine Sicherheitswarnung bezüglich SMS-Lecks"
          },
          {
            "level": 2,
            "id": null,
            "text": "Sieben Tage vor dem erneuten Handel oder der erneuten Vermarktung"
          },
          {
            "level": 2,
            "id": null,
            "text": "Einschränkungen für neue Geräte auf den Hilfeseiten überprüft"
          },
          {
            "level": 2,
            "id": null,
            "text": "In „2024“ wurde eine Wartezeit für Namensänderungen bei Tauschgeschäften eingeführt"
          },
          {
            "level": 2,
            "id": null,
            "text": "Zur Schlüsselerstellung ist eine Bestätigung per Handy erforderlich"
          },
          {
            "level": 2,
            "id": null,
            "text": "Die obligatorische „2“-FA für die Freischaltung von Spiel-Builds tritt in Kraft"
          },
          {
            "level": 2,
            "id": null,
            "text": "Von der Community festgestellte Inhaltswarnungen in benutzerdefinierten Biografien"
          },
          {
            "level": 2,
            "id": null,
            "text": "Filterung von Profil-Links und Wartezeiten für Bearbeitungen sind aktiv"
          },
          {
            "level": 2,
            "id": null,
            "text": "Steam Umstellung der Clients auf OAuth-Aktualisierungs- und Zugriffstoken"
          },
          {
            "level": 2,
            "id": null,
            "text": "QR-Code-Anmeldung und Verwaltung autorisierter Geräte"
          },
          {
            "level": 2,
            "id": null,
            "text": "Endpunkte für die Stornierung von Transaktionen wurden aus der öffentlichen Liste „API“ entfernt"
          },
          {
            "level": 2,
            "id": null,
            "text": "Dota-2-Gegenstände unterliegen einer siebentägigen Handelssperre"
          },
          {
            "level": 2,
            "id": null,
            "text": "Für getauschte CS:GO-Gegenstände gilt eine siebentägige Wartezeit"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/de/#briefing-heading",
          "https://steamcommunity.com/groups/SteamClientBeta?l=english",
          "http://web.archive.org/web/20260313235409/https://steamcommunity.com/groups/SteamClientBeta?l=english",
          "https://store.steampowered.com/news/posts/?enddate=1788390000",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/493839547938902179",
          "https://partner.steamgames.com/doc/webapi_overview/auth",
          "https://csmarketcap.com/blog/market-insights/from-boom-to-bust-cs2s-trade-protection-impact",
          "https://skinvault.gg/blog/cs2-trade-protection-explained/",
          "https://skin.land/blog/steam-changes-cs2-trade-ban-logic-timing/",
          "https://store.steampowered.com/news/posts/?appids=730&amp;enddate=1753924057&amp;feed=steam_announce%2F1000",
          "https://help.steampowered.com/faqs/view/3041-A87A-E5F6-B6AC",
          "https://store.steampowered.com/news/posts/?enddate=1747349559",
          "https://steamcommunity.com/ogg/593110/announcements/detail/533224478739530146",
          "https://store.steampowered.com/news/posts/?appids=730&amp;enddate=1728000977&amp;feed=steam_community_announcements",
          "https://steamcommunity.com/games/CSGO/announcements/detail/4447966961421256740",
          "https://help.steampowered.com/faqs/view/7F77-9E92-31E0-6B8E",
          "https://steamcommunity.com/sharedfiles/filedetails/?id=2926756889",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "http://web.archive.org/web/20260924181824/https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "https://steamcommunity.com/dev/apikey",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3749866608167579206",
          "http://web.archive.org/web/20251203174259/https://steamcommunity.com/groups/steamworks/announcements/detail/3749866608167579206",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3734103130194459461",
          "https://steamcommunity.com/discussions/forum/1/3807266184852932971/",
          "https://help.steampowered.com/faqs/view/225C-C51E-B8F0-55B2",
          "https://store.steampowered.com/news/group/4/view/3314112260640237775",
          "https://store.steampowered.com/news/posts/?appgroupname=Keep+in+touch&amp;enddate=1666122699&amp;feed=steam_blog",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/issues/325",
          "https://partner.steamgames.com/doc/webapi/IEconService",
          "https://steamcommunity.com/app/570/announcements/",
          "https://blog.dota2.com/2020/05/trading-cooldown/",
          "https://blog.counter-strike.net/2018/03/20309/",
          "https://blog.counter-strike.net/index.php/2018/03/20308/",
          "http://web.archive.org/web/20250226114333/https://blog.counter-strike.net/index.php/2018/03/20308/",
          "https://phishdestroy.io/steam_dossier/de/#vulnerability-profile"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/de/security_timeline.content.json",
      "export_json_sha256": "2c630b8a70369ccc384f744b89f2cf1699f9741736c65a3c724543e22200c1a4"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "de/skin_atlas.html",
      "language": "de",
      "title": "Der Atlas dessen, was „Steam“ nicht zeigen darf – Das Dossier „Steam“",
      "source_url": "https://phishdestroy.io/steam_dossier/de/skin_atlas",
      "source_html_sha256": "c4c770011d11a6c07972ad87105bf55727a89e8dd0c12d1ca478322d3561fc00",
      "exported_at": "2026-09-29T00:16:14.665Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "gallery",
            "source": "https://phishdestroy.io/steam_dossier/de/skin_atlas#gallery"
          }
        ],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "skin_atlas.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/de/skin_atlas.pdf?v=print-20260929-v5",
        "sha256": "dd536618eff0d2b9e60cfc98d589d42abcadc99476fbeff08c653e1120e86065",
        "bytes": 187587,
        "pages": 14
      },
      "integrity": {
        "signed_object": "skin_atlas.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "skin_atlas.content.json.asc",
        "digest_file": "skin_atlas.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify skin_atlas.content.json.asc skin_atlas.content.json",
          "sha256sum -c skin_atlas.content.json.sha256"
        ]
      },
      "content": {
        "text": "ANLAGE IV-B / DIE PREISSTUFEN / 2026-09-23\nSkin-Preis-Leiter-Atlas – Die Liquiditätsklippe\n\nValves Marktauftritte Wo das Geld herkommt.\n\nWAS DIESER ABSCHNITT BELEGT\n\nDieser visuelle Atlas analysiert die Artikelkategorien von „30,266“ in fünf Marktplatzkatalogen und ermittelt dabei die Marktabdeckung oberhalb und unterhalb der Einstellschwelle von „Valve“. Unterhalb der Obergrenze von $1,800 beherbergt Steam 95.3% aktive Kategorien; unmittelbar darüber bricht die offizielle Abdeckung auf 1.9% ein (wobei 0.0% die Abdeckung über bestätigte Vermögenswerte hinweg gewährleistet). Dies verdeutlicht eine abrupte, strukturelle Liquiditätsklippe, bei der Valve die Erkennung hochwertiger Transaktionen an externe Plattformen delegiert, während es die volle Kontrolle über die Verwahrung der zugrunde liegenden Vermögenswerte behält.\n\n← Zurück zum Executive Briefing\n\nJeder CS2-Artikel, für den auf fünf Marktplätzen ein aktueller Preis vorlag, wurde anhand seines günstigsten Angebotspreises einer Preisspanne zugeordnet, und jede Spanne wurde hinsichtlich eines einzigen Kriteriums bewertet: Welchen Anteil davon macht der Community-Markt vValve noch aus? Unterhalb der Obergrenze für Angebote vValve lautet die Antwort 95.3%. Darüber lautet die Antwort 1.9%. Der Rückgang erfolgt nicht schrittweise und entspricht auch nicht dem Rückgang der Nachfrage – er erfolgt genau gemäß der veröffentlichten Regelung. Von den 248 Artikelkategorien, bei denen zwei oder mehr Marktplätze unabhängig voneinander Preise über der Obergrenze festlegen, 100.0% haben überhaupt keinen Eintrag auf Steam.\n\nSiehe die Klippe ↓Öffne die Galerie mit Artikeln von „419“Methode und Grenzen\n30,266gemessene Artikelkategorien\n95.3%der von Steam geführten Sub-Cap-Titel\n1.9%der von Steam geführten Artikel, die die Obergrenze überschreiten\n$78.6MUntergrenze der bestätigten Menge\n01 / die Messung\nDie Klippe fällt nach der Regel, nicht auf Verlangen\n\nJede der unten aufgeführten Artikelkategorien von „30,266“ wird entsprechend ihrer am günstigsten Live-Abfrage über BUFF163, CSFloat, Skinport, YouPin 898 und C5Game; dabei werden nur Artikel gezählt, die auf mindestens zwei dieser Plattformen aufgeführt sind, sodass kein einzelner optimistischer Eintrag ein Bandmitglied erfinden kann. Der obere Abschnitt zeigt den Anteil, den der eigene Markt von „Valve“ noch an den jeweiligen Bands ausmacht.\n\nAnteil der einzelnen Preisklassen, die auf dem „Steam Community Market“ angeboten werden\noben: Dampfabdeckung · unten: Anzahl der Elemente pro Band, logarithmische Skala\n0%\n25%\n50%\n75%\n100%\n100%\n96.9%\n95.9%\n97.3%\n91.1%\n76.8%\n14.5%\n2.9%\n1.5%\n0%\n0%\n0%\n4,632\n1¢–10¢\n7,152\n10¢–$1\n8,568\n$1–10\n5,941\n$10–100\n2,329\n$100–300\n1,292\n$300–1k\n193\n$1k–1.8k\n70\n$1.8k–3k\n67\n$3k–10k\n18\n$10k–30k\n3\n$30k–100k\n1\n$100k+\nitems\nlog\nVALVE’S LISTING CAP\nbei oder unterhalb der Obergrenze für die Notierung von „Valve“über der Obergrenze – die Vorschriften der „Valve“ verbieten die NotierungArtikelkategorien in der Bandbreite\n\n„Abdeckung“ bedeutet, dass zum Zeitpunkt der Erfassung ein Live-Steam-Ask für diese Kategorie vorlag. Das untere Diagramm ist logarithmisch skaliert, da der Katalog überwiegend aus günstigen Titeln besteht: Bei einer linearen Darstellung würden alle Bereiche oberhalb von $300 auf das Grundniveau abgeflacht werden.\n\nWas die Form ausschließt\n\nWären teure Güter einfach nur unbeliebt, würde die Nachfrage mit steigendem Preis allmählich nachlassen. Das ist jedoch nicht der Fall. Sie bleibt im Bereich von 76.8% über den Preisbereichen von $300–$1k stabil und bricht dann im Bereich unmittelbar unterhalb der Obergrenze auf 14.5% und im Bereich unmittelbar darüber auf 2.9% ein. Ein Nachfrageeffekt weiß nicht, wo Valve seine Obergrenze festlegt. Eine Regel hingegen schon.\n\nPreisspanne\tArtikelkategorien\tMit einer Live-Steam-Anfrage\tSteam Reichweite\tExemplare, die auf Steam aufgeführt sind\n1¢–10¢\t4,632\t4,632\t100%\t8,223,227\n10¢–$1\t7,152\t6,931\t96.9%\t5,488,315\n$1–10\t8,568\t8,213\t95.9%\t3,939,538\n$10–100\t5,941\t5,780\t97.3%\t1,328,255\n$100–300\t2,329\t2,121\t91.1%\t364,466\n$300–1k\t1,292\t992\t76.8%\t187,504\n$1k–1.8k\t193\t28\t14.5%\t40,281\n$1.8k–3k\t70\t2\t2.9%\t9,592\n$3k–10k\t67\t1\t1.5%\t6,706\n$10k–30k\t18\t0\t0%\t1,366\n$30k–100k\t3\t0\t0%\t21\n$100k+\t1\t0\t0%\t2\n\nMuster- und Phasenvarianten sind in dieser Rangliste nicht berücksichtigt: Auf Steam werden weder die „Blue-Gem“-Stufe noch die „Ruby“-Phase als eigenständige Markteintritte aufgeführt, sodass ihre Berücksichtigung die Reichweite von Steam unterschätzen würde. Ohne die Anforderung der zwei Marktplätze ergibt dieselbe Rangliste folgende Werte: „79.1%“ unterhalb der Obergrenze und „6.5%“ oberhalb derselben für alle Artikel auf 37,204 – eine deutlichere Lücke, die auf schwächeren Belegen basiert, weshalb diese Zahl nicht angegeben wird.\n\n02 / Beweisbewertung\nEin Angebotspreis ist kein Preis\n\nJeder kann eine P2000 für rund zehn Millionen Yuan anbieten. Bevor eine Zahl auf dieser Seite für irgendetwas herangezogen wird, wird sie danach bewertet, wie viele Marktplätze den Artikel unabhängig voneinander über dem Höchstpreis notieren und wie eng der Mittelwert dieser Notierungen beieinander liegt. Es werden nur die Bewertungsstufen A und B angegeben – hier wie auch an jeder anderen Stelle in diesem Dossier.\n\nA  Drei oder mehr Regale stimmen überein\n\nDrei oder mehr Marktplätze bieten den Artikel zu einem Preis über der Obergrenze an, und ihr Medianpreis liegt innerhalb von 25% des günstigsten Preises. 197 Kategorien, 18,218 Exemplare, $76,585,587.\n\nNicht in „Steam“ enthalten: 100.0%.\n\nB  Zwei Regale passen zusammen\n\nZwei Märkte liegen über der Obergrenze, drei liegen etwas darunter. 51 Kategorien, 176 Exemplare, $2,038,814.\n\nNicht in „Steam“ enthalten: 100.0%.\n\nC  Ein Regal – ungenutzt\n\nNur ein einziger Handelsplatz weist das einzige Angebot über der Obergrenze auf. 171 Kategorien, 247 Exemplare. Wird der Vollständigkeit halber in der Galerie angezeigt, ist jedoch aus allen Summen auf dieser Seite ausgeschlossen.\n\nDas sind Preisanfragen, keine Preisnachweise.\n\nWas diese Korrektur gekostet hat und was sie gebracht hat\n\nDurch das Weglassen der Note C fallen die Kategorien „171“ sowie „$3,825,125“ aus der Überschrift weg. Was übrig bleibt, ist kürzer und viel schwerer zu widerlegen: 248 Kategorien, 18,394 aufgeführte Exemplare, $78,624,401, und 100.0% – jedes einzelne davon fehlt auf dem Markt von Valve. Die Zeilen der Klasse C sind der Grund dafür, dass sich die Zahl verändert hat; sie sind aufgeführt und nicht ausgeblendet.\n\nAls Artefakte ausgewiesene Einträge\n\nJedes Angebot, das mehr als das Dreifache des günstigsten Angebotspreises für denselben Artikel beträgt, wird aussortiert. Umgerechnet zu dem Kurs, den die Daten selbst nahelegen, handelt es sich bei den meisten um runde CNY-Beträge – ein typisches Merkmal für einen Platzhalter oder eine Obergrenze der Plattform und nicht für ein tatsächliches Angebot. Denn jeder Gesamtbetrag auf dieser Seite basiert auf dem am günstigsten Man muss sich klar machen, dass keine dieser Persönlichkeiten jemals eine Zahl aufgebläht haben könnte; sie wurden ausgeschlossen, damit auch keine von ihnen als Schlagzeile zitiert werden kann.\n\nArtikel\tGünstigstes Live-Angebot\tBeiseite stellen\nSouvenir P2000 | Wicked Sick (Minimal Wear)\t$148,954\t$1,489,543\n★ Specialist Gloves | Crimson Kimono (Minimal Wear) | Phase 1\t$37,239\t$119,163\nSouvenir USP-S | Printstream (Factory New)\t$2,000\t$59,582\n★ Bowie Knife | Crimson Web (Factory New)\t$2,957\t$43,030\n★ Karambit | Marble Fade (Factory New) | 1st\t$11,916\t$38,874\nSticker | Ninjas in Pyjamas (Holo) | Katowice 2014\t$5,000\t$31,748\nSouvenir AWP | Dragon Lore (Battle-Scarred)\t$4,225\t$29,157\n★ Karambit | Doppler (Minimal Wear) | Ruby\t$7,122\t$27,273\nAlle Kategorien unter „419“, mit Angabe des Objekts, auf das sich der jeweilige Preis bezieht\n\nQuelle: https://phishdestroy.io/steam_dossier/de/skin_atlas#gallery\n\n04 / wohin es stattdessen ging\nDie Regale, in denen das steht, was Steam nicht anbietet\n\nDieselben Angebote, gruppiert nach dem jeweiligen Marktplatz, auf dem sie zu finden sind. Hier wird aufgeführt, wo sich Exemplare befinden. aufgeführt, was nicht dasselbe ist wie der Ort, an dem sie sich befinden, und hier auch nicht als solcher verstanden wird.\n\nMindestwert von Angeboten über der Obergrenze, nach Marktplatz\nniedrigster Angebotspreis × Anzahl der Exemplare in diesem Regal\nYouPin 898\n$22,720,252\nBUFF163\n$22,022,606\nC5Game\n$12,560,543\nCSFloat\n$10,871,845\nSkinport\n$1,385,060\n\nLänder, in der oben genannten Reihenfolge: YouPin 898 — China · BUFF163 — China · C5Game — China · CSFloat — Vereinigte Staaten · Skinport — Deutschland / Malta. Ein und derselbe Artikel kann in mehr als einem dieser Regale gelistet sein, daher dürfen diese Zahlen nicht mit den Gesamtzahlen anderer Märkte addiert werden.\n\nMindestwert nach Preisklasse\nwie das Geld oberhalb der Obergrenze verteilt wird\n$1.8k-3k\n$9,842,391\n$3k-10k\n$36,787,269\n$10k-50k\n$20,038,749\nover $50k\n$2,891,897\n05 / Knappheit, die man zählen kann\nWie knapp das Angebot tatsächlich ist\n\nJeder CS2-Artikel hat einen Seltenheitswert, und die Marktplätze veröffentlichen, wie viele Exemplare sich in den einzelnen Seltenheitsstufen befinden. Dadurch wird „selten“ von einem Adjektiv zu einer Zahl – und genau diese Zahl erklärt, warum ein einzelnes gehacktes Konto den Aufwand für ein maßgeschneidertes Phishing-Kit rechtfertigt.\n\nAWP | Dragon Lore\n150 im Angebot · ab11,350\n0.00–0.01\n29 · $14,730\n0.01–0.02\n54 · $11,618\n0.02–0.03\n26 · $11,350\n0.03–0.04\n25 · $11,618\n0.04–0.07\n16 · $11,585\n\nAWP | Dragon Lore (fabrikneu)\n\nM4A4 | Howl\n105 im Angebot · ab6,628\n0.00–0.01\n11 · $10,725\n0.01–0.02\n14 · $8,088\n0.02–0.03\n11 · $7,580\n0.03–0.04\n19 · $6,703\n0.04–0.07\n50 · $6,628\n\nM4A4 | Howl (fabrikneu)\n\nAK-47 | Wild Lotus\n113 im Angebot · ab14,373\n0.00–0.01\n25 · $22,343\n0.01–0.02\n11 · $19,364\n0.02–0.03\n3 · $19,645\n0.03–0.04\n15 · $15,044\n0.04–0.07\n59 · $14,373\n\nAK-47 | Wild Lotus (fabrikneu)\n\nAWP | Gungnir\n173 im Angebot · ab11,618\n0.00–0.01\n28 · $17,875\n0.01–0.02\n21 · $13,600\n0.02–0.03\n32 · $12,065\n0.03–0.04\n29 · $11,735\n0.04–0.07\n63 · $11,618\n\nAWP | Gungnir (fabrikneu)\n\nAK-47 | Feuerschlange\n278 im Angebot · ab663\n0.15–0.18\n87 · $730\n0.18–0.21\n49 · $712\n0.21–0.24\n52 · $703\n0.24–0.27\n18 · $715\n0.27–0.38\n72 · $663\n\nAK-47 | Feuerschlange (praxiserprobt)\n\nEinsatzgehärtet (alle Stufen / blauer Edelstein)\n76 im Angebot · ab1,638\n0.07–0.08\n1 · $2,516\n0.08–0.09\n4 · $2,482\n0.09–0.10\n6 · $3,856\n0.10–0.11\n7 · $2,797\n0.11–0.15\n58 · $1,638\n\nAK-47 | Einsatzgehärtet (minimale Abnutzung) | Stufe 1\n\nBänder sind die marktplatzspezifischen Liquiditätsbereiche; es werden nur Bänder mit mindestens einem aktuellen Kurs gezogen. Der Preis neben jedem Balken entspricht dem günstigsten aktuellen Briefkurs in diesem Band, sodass der Aufschlag bei geringem Liquiditätsvolumen direkt ersichtlich ist und nicht extra angegeben werden muss.\n\n06 / Bewegung, gemessen auf Steam\nWas die Regale von Drittanbietern tatsächlich erzielten\n\nValve veröffentlicht auf dieser Ebene keine verwertbaren historischen Daten, und auch dieses Dossier erhebt keinen Anspruch darauf. Skinport veröffentlicht zwar seine eigenen abgeschlossenen Verkäufe der letzten 24 Stunden, 7, 30 und 90 Tage, und das ist auch schon die gesamte hier verfügbare Zeitdimension: ein Median des realisierten Preises pro Zeitfenster, indexiert, sodass der 90-Tagesmedian 100. beträgt. In keiner der beiden Grafiken sind Daten von „Steam“ enthalten.\n\nMedian des realisierten Preises, gleitendes Zeitfenster\nindexiert auf den Medianwert von 90-pro Tag · 6,758 Artikel mit 20+ Umsatz\n85\n91\n97\n103\n100\n90d\n94\n30d\n90\n7d\n88\n24h\nAbgeschlossene Verkäufe pro Tag\ngleiche Artikel, gleiche Fenster\n7,621\n9,653\n11,684\n13,716\n12,700\n90d\n11,894\n30d\n9,540\n7d\n8,637\n24h\n\nEs handelt sich hier um zwei Diagramme und nicht um ein einziges mit zwei vertikalen Skalen: Ein Index und eine tägliche Zählung haben keine gemeinsame Einheit, und ihre Darstellung auf einer gemeinsamen Achse würde zu einem Vergleich verleiten, der nicht zulässig ist. Die Zeitfenster sind verschachtelt und gleitend – der Tageswert „90-“ enthält den Stundenwert „24-“ –, daher handelt es sich nicht um eine tägliche Reihe und sie darf auch nicht als solche interpretiert werden. Was die Grafik belegt, ist eng gefasst und klar formuliert: Über die von Skinport veröffentlichten gleitenden Zeitfenster lag der Median des realisierten Preises unter seinem eigenen 90-Tagesmedian, und die tägliche Verkaufszahl sank mit ihm.\n\nSkinport Realisierte Umsätze. Die Zeitfenster sind verschachtelt und gleitend, sodass jeder Punkt dem Median des realisierten Kurses über das gleitende Zeitfenster entspricht, indexiert auf den Median des „90-“-Tages. Es handelt sich nicht um eine tägliche Reihe, und es werden keine Daten aus dem „Steam“ herangezogen.\n\n07 / woraus es besteht\nSechzehn Jahre alte Aufkleber und eine Handvoll Handschuhe\n\nDas oben genannte Segment deckt nicht den Großteil des Marktes ab. Es konzentriert sich auf einige wenige Raritäten und Sammlungen, von denen einige gar nicht mehr erhältlich sind – und genau deshalb kann das Angebot nicht auf den Preis reagieren.\n\nKategorien oberhalb der Obergrenze, nach Seltenheit\nAnzahl der Artikelkategorien\nCovert\n321\nClassified\n39\nRestricted\n24\nContraband\n12\nMil-Spec Grade\n9\nConsumer Grade\n9\nIndustrial Grade\n5\nKategorien oberhalb der Leiste, nach Kollektion\nDie zehn besten Kollektionen\nThe St. Marc Collection\n13\nThe Cobblestone Collection\n13\nThe Norse Collection\n12\nThe Arms Deal Collection\n9\nThe Canals Collection\n7\nThe Gods and Monsters Collection\n6\nThe Revolution Collection\n4\nThe 2021 Train Collection\n4\nThe Rising Sun Collection\n4\nThe Chop Shop Collection\n4\n\nNach Kategorie: skin 366, sticker 48, container 3, sticker_slab 2.\n\n08 / der höchste Betrag, den tatsächlich jemand gezahlt hat\nHöchststände, die durch eine Transaktion und nicht durch eine Börsennotierung gestützt werden\n\nJeder andere Preis auf dieser Seite ist ein verlangen — was ein Verkäufer will. Das sind Umsatz: der höchste verzeichnete AbschlussSkinport für jeden Artikel in den letzten 90 Tagen. Es handelt sich um den einzigen Wert in dieser Übersicht, den tatsächlich jemand bezahlt hat, und jede Zeile enthält einen Link zum Marktplatz, sodass der Wert direkt an der Quelle und nicht bei uns überprüft werden kann.\n\n21,216Artikel, deren Verkauf bereits abgeschlossen ist, im Schaufenster\n106zu einem Preis verkauft, der der Obergrenze von „Valve“ entspricht oder darüber liegt\n$14,192höchster einzelner abgeschlossener Verkauf\n67/419Kategorien oberhalb der Obergrenze mit mindestens einem verzeichneten Verkauf\nDie dreißig höchsten abgeschlossenen Verkäufe in diesem Zeitraum\nArtikel\tHöchster Umsatz\tMedianverkaufspreis\tUmsatz\tJetzt zum günstigsten Preis anfragen\tSteam\tSchau es dir an\nAWP | Gungnir (Factory New)\t$14,192\t$11,343\t5\t$11,490\tabsent\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Factory New)\t$12,387\t$12,387\t1\t$13,836\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Factory New)\t$11,779\t$11,063\t16\t$10,941\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Minimal Wear)\t$11,693\t$11,693\t1\t$9,946\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Minimal Wear)\t$10,437\t$10,437\t1\t$9,610\tabsent\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Blue Laminate (Minimal Wear)\t$9,772\t$37\t76\t$30\t$40\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Minimal Wear)\t$9,463\t$9,463\t1\t$9,500\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Minimal Wear)\t$9,104\t$9,026\t6\t$8,524\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Hedge Maze (Minimal Wear)\t$8,139\t$8,139\t1\t$6,819\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Field-Tested)\t$7,617\t$7,390\t4\t$7,194\tabsent\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Field-Tested)\t$7,615\t$7,615\t1\t$7,100\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Field-Tested)\t$7,149\t$7,006\t2\t$7,165\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Field-Tested)\t$6,711\t$6,194\t15\t$5,988\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Factory New)\t$6,679\t$6,613\t3\t$6,628\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Superconductor (Factory New)\t$6,084\t$6,084\t1\t$7,969\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Battle-Scarred)\t$5,750\t$5,413\t3\t$5,899\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Pandora's Box (Minimal Wear)\t$5,520\t$5,508\t3\t$4,998\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Vice (Factory New)\t$5,385\t$5,158\t2\t$5,700\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Minimal Wear)\t$5,342\t$4,989\t19\t$4,997\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Hedge Maze (Field-Tested)\t$5,334\t$4,862\t5\t$3,724\tabsent\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Vulcan (Factory New)\t$5,275\t$1,418\t12\t$1,280\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Well-Worn)\t$4,978\t$4,978\t1\t$4,942\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Well-Worn)\t$4,931\t$4,931\t1\t$5,445\tabsent\tSkinport CSFloat Steam\nAK-47 | Hydroponic (Factory New)\t$4,802\t$4,351\t2\t$3,648\tabsent\tSkinport CSFloat Steam\n★ Talon Knife | Case Hardened (Minimal Wear)\t$4,588\t$466\t16\t$442\t$630\tSkinport CSFloat Steam\nAWP | Medusa (Factory New)\t$4,484\t$4,484\t1\t$4,171\tabsent\tSkinport CSFloat Steam\n★ Specialist Gloves | Pillow Punchers (Factory New)\t$4,359\t$4,359\t1\t$4,302\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Pandora's Box (Field-Tested)\t$4,359\t$3,666\t11\t$3,245\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Field-Tested)\t$4,289\t$4,225\t8\t$4,022\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Battle-Scarred)\t$4,124\t$4,124\t1\t$4,279\tabsent\tSkinport CSFloat Steam\nDerselbe Artikel, derselbe „90“-Tag, aber ein himmelweiter Preisunterschied\n\nBeschränkt auf Artikel mit einem Medianwert von $100 und mindestens fünf abgeschlossenen Verkäufen, da bei einem günstigen Skin ein einziger Ausreißer das Verhältnis stark verzerrt. Was übrig bleibt, wird dominiert von Einsatzgehärtet Ausführungen, bei denen das Muster den Preis bestimmt und der Marktplatz jedes Muster unter einem Namen erfasst – derselbe Mechanismus, der im Abschnitt „05.“ anhand des Float-Werts gemessen wird.\n\nArtikel\tHöchstwert vs. Median\tHöchster Umsatz\tMedianverkaufspreis\tUmsatz\tSchau es dir an\n★ Talon Knife | Case Hardened (Minimal Wear)\t+884%\t$4,588\t$466\t16\tSkinport CSFloat Steam\nDesert Eagle | Cobalt Disruption (Factory New)\t+859%\t$1,210\t$126\t115\tSkinport CSFloat Steam\nAWP | BOOM (Minimal Wear)\t+814%\t$1,232\t$135\t89\tSkinport CSFloat Steam\nAK-47 | Case Hardened (Well-Worn)\t+769%\t$1,720\t$198\t70\tSkinport CSFloat Steam\nAWP | Graphite (Factory New)\t+761%\t$1,469\t$171\t124\tSkinport CSFloat Steam\n★ Talon Knife | Case Hardened (Field-Tested)\t+509%\t$2,437\t$400\t48\tSkinport CSFloat Steam\n★ Kukri Knife | Case Hardened (Minimal Wear)\t+448%\t$723\t$132\t69\tSkinport CSFloat Steam\n★ Kukri Knife | Case Hardened (Field-Tested)\t+415%\t$549\t$106\t128\tSkinport CSFloat Steam\n★ Ursus Knife | Case Hardened (Minimal Wear)\t+371%\t$597\t$127\t12\tSkinport CSFloat Steam\nAK-47 | Case Hardened (Field-Tested)\t+369%\t$1,037\t$221\t125\tSkinport CSFloat Steam\nAK-47 | Red Laminate (Minimal Wear)\t+360%\t$552\t$120\t18\tSkinport CSFloat Steam\nAWP | Asiimov (Field-Tested)\t+351%\t$528\t$117\t439\tSkinport CSFloat Steam\nAK-47 | Vulcan (Field-Tested)\t+337%\t$865\t$198\t241\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Nightwish (Factory New)\t+322%\t$625\t$148\t31\tSkinport CSFloat Steam\nAWP | Lightning Strike (Factory New)\t+319%\t$2,065\t$493\t198\tSkinport CSFloat Steam\nStatTrak™ AWP | Redline (Minimal Wear)\t+312%\t$574\t$139\t24\tSkinport CSFloat Steam\nStatTrak™ AWP | Asiimov (Battle-Scarred)\t+287%\t$524\t$135\t37\tSkinport CSFloat Steam\nAK-47 | Redline (Minimal Wear)\t+277%\t$562\t$149\t112\tSkinport CSFloat Steam\nAWP | Crakow! (Factory New)\t+275%\t$379\t$101\t72\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Vulcan (Factory New)\t+272%\t$5,275\t$1,418\t12\tSkinport CSFloat Steam\n\nEs handelt sich hierbei um ein Tageshoch für „90-“, NICHT um ein Allzeithoch, und es bezieht sich auf EINEN Marktplatz. In dieser Dokumentation wird an keiner Stelle ein Allzeithoch angegeben. Ein Artikel, für den im Fenster kein Verkauf bei „Skinport“ angezeigt wird, fehlt vollständig in dieser Aufstellung, weshalb der Umfang kleiner ist als der der Erhebung.\n\nVerifizierungslinks werden anhand der Plattform-IDs des Katalogs erstellt. Sie verweisen auf die Seite des jeweiligen Marktplatzes für den Artikel, sodass der Leser die Angaben direkt an der Quelle und nicht bei uns überprüfen kann. Ausgehende Links führen rel=\"nofollow\": Es handelt sich um Verweise, nicht um Empfehlungen, und bei einigen der genannten Ziele handelt es sich um Marktplätze, die in dieser Untersuchung kritisch beleuchtet werden.\n\n09 / Herkunft und Beschränkungen\nWoher das stammt und was es nicht zeigen kann\n\nJede Zahl auf dieser Seite wurde anhand von zwei Snapshot-Dateien neu berechnet, deren Hashes neben den Zahlen veröffentlicht sind. Nichts hier wurde aus einem Artikel einer anderen Website übernommen.\n\nQuelle und Zugriff\n\ncs2.sh API, GET /v1/prices/latest und GET /v1/schema, Einzel-Snapshot, erfasst am 2026-09-23T00:44:27.871388581Z, Preise in USD.\n\nDie Daten wurden im Rahmen eines kostenpflichtigen kommerziellen Abonnements bezogen, das der im Archiv dokumentierte Antragsteller „GDPR“ gemäß den Bedingungen des Anbieters abgeschlossen hatte. Es wurde kein Marktplatz abgefragt, und es wurden keine Zugangsdaten eines Marktplatzes verwendet. Der Schlüssel des Anfragenden wird außerhalb dieses Repositorys gespeichert und taucht hier in keiner Datei auf.\n\nWie ein Artikel die Voraussetzungen erfüllt\n\nJeder Basisartikel mit mindestens einem aktiven Verkaufsangebot auf BUFF, CSFloat, Skinport, YouPin oder C5Game wird anhand seines GÜNSTIGSTEN solchen Angebots in eine Preisspanne eingeordnet, sodass die Spanne niemals von Steam abhängt. „Steam-Abdeckung“ ist der Anteil der Artikel in dieser Spanne, für die zum Zeitpunkt der Erfassung ein aktives Steam-Verkaufsangebot vorliegt. Muster- und Phasenvarianten werden aus der Rangliste ausgeschlossen, da Steam diese nicht separat auflistet; ihre Einbeziehung würde Steam zu niedrig ausfallen lassen. „Renders“ sind die lokal gespeicherten Katalogbilder für dieselben Artikel.\n\nRenderings und Bildrechte. Bei den Renderings der Katalogartikel handelt es sich um Bilder des Anbieters, die für denselben „market_hash_name“ wie die Preiszeilen bereitgestellt und lokal für die Offline- und IPFS-Anzeige gespeichert werden. Die Darstellungen stammen nicht von PhishDestroy: Alle Artikelbilder, Logos und Screenshots bleiben Eigentum ihrer jeweiligen Inhaber (cs2.sh, CSFloat, Skinport, BUFF, YouPin, C5Game, Valve und andere). Sie werden ausschließlich zu Identifikationszwecken und im öffentlichen Interesse wiedergegeben; es werden keine Eigentums- oder Lizenzansprüche geltend gemacht.\n\nWas wir nicht erhalten konnten\n\nDie genutzte Abonnementstufe umfasst ausschließlich aktuelle Snapshots. Endpunkte für historische Daten und Archivdaten standen nicht zur Verfügung, und Auf dieser Seite wird an keiner Stelle behauptet, dass es sich um eine historische Reihe handelt. Weitere Informationen zum UmsatzSkinports auf Basis eines gleitenden Zeitfensters finden Sie im Abschnitt „06.“\n\nEine Momentaufnahme, keine Zeitreihe. Das Fehlen eines Eintrags auf Steam zum Zeitpunkt der Erfassung ist kein Beweis dafür, dass ein Artikel dort niemals erscheinen wird; es handelt sich um den gemessenen Zustand des Regals zu diesem Zeitpunkt, und bei Preisen über der Obergrenze entspricht dies zudem der von Valve veröffentlichten Regel: Der Community-Markt von Valve begrenzt Einträge ausdrücklich auf $1,800 pro Artikel (bei einem maximalen Steam-Wallet-Guthaben von $2,000; siehe Steam Häufig gestellte Fragen zum Community-Markt archiviert unter 2026-09-21 ↗ sowie Steam Abonnentenvertrag § 3.C archiviert unter 2026-09-24 ↗).\n\nBenotung\n\nDer Preis eines Artikels entspricht immer dem günstigsten aktuellen Briefkurs, sodass ein hoher Ausreißer den Gesamtwert niemals in die Höhe treiben kann. Die Einstufung bestimmt, welche Zeilen aufgeführt werden dürfen. Jedes Angebot, das mehr als das Dreifache des günstigsten Briefkurses für denselben Artikel beträgt, wird als kein aktueller Preis aussortiert. Bewertungsstufe A: Drei oder mehr Marktplätze notieren weiterhin über der Obergrenze, und ihr Median liegt innerhalb von 25 Prozent des günstigsten Preises. Bewertungsstufe B: Zwei Marktplätze stimmen überein, oder drei stimmen weniger eng überein. Bewertungsstufe C: Ein einzelner Preis – ein Angebotspreis, kein Marktpreis. In diesem Dossier werden ausschließlich die Bewertungsstufen A und B angegeben.\n\nAusreißerregel: Kurs > 3.0x der günstigste Briefkurs für denselben Titel.\n\nWarum die Summen einen Mindestwert darstellen\n\nFür jeden Marktplatz gilt für den Artikel, dass niedrigsten Der Angebotspreis wird mit der Anzahl der Exemplare multipliziert, die in der Regalliste aufgeführt sind. Jedes zweite Exemplar dort hat einen Preis, der diesem niedrigsten Angebotspreis entspricht oder darüber liegt, sodass der tatsächlich angegebene Wert naturgemäß höher ist – nicht aufgrund einer Schätzung. Es handelt sich weder um einen Verkauf noch um einen Cashflow noch um eine Bewertung der CS2-Wirtschaft.\n\nÜberzeugen Sie sich selbst\n\nDie jedem Diagramm auf dieser Seite zugrunde liegenden Datensätze werden vollständig veröffentlicht: der Atlas-Datensatz, der Bildschirm für die Einstufung und die Artefakte, die zugrunde liegende Volkszählung sowie das Manifest mit dem SHA-256-Wert jedes Raw-Snapshots.\n\nEine Korrektur, die öffentlich verzeichnet wurde\n\nEin früherer Entwurf des Begleitregisters führte mit einem Souvenir-AK-47 | Point Disarray, das auf einem chinesischen Marktplatz zu $148,954 angeboten wurde, während Steam den Preis mit $119. angab. Diese Zeile entspricht der Klasse C: ein einziges Regal, ein einziges Exemplar und kein zweiter Marktplatz, der diesen Preis bestätigt. Es handelt sich um einen Angebotspreis, nicht um einen tatsächlichen Preis, und er wurde hier sowie auf jener Seite herabgestuft. Der bestätigte Spitzenreiter ist „Sticker | Titan (Holo) | Katowice“ 2014 zu $66,285, zitiert von 4: Marktplätze, die innerhalb von 5.2% voneinander getrennt sind – und auf Steam überhaupt nicht vertreten sind.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Skin-Preis-Leiter-Atlas – Die Liquiditätsklippe"
          },
          {
            "level": 2,
            "id": null,
            "text": "Die Klippe fällt nach der Regel, nicht auf Verlangen"
          },
          {
            "level": 3,
            "id": null,
            "text": "Was die Form ausschließt"
          },
          {
            "level": 2,
            "id": null,
            "text": "Ein Angebotspreis ist kein Preis"
          },
          {
            "level": 3,
            "id": null,
            "text": "A  Drei oder mehr Regale stimmen überein"
          },
          {
            "level": 3,
            "id": null,
            "text": "B  Zwei Regale passen zusammen"
          },
          {
            "level": 3,
            "id": null,
            "text": "C  Ein Regal – ungenutzt"
          },
          {
            "level": 3,
            "id": null,
            "text": "Was diese Korrektur gekostet hat und was sie gebracht hat"
          },
          {
            "level": 3,
            "id": null,
            "text": "Als Artefakte ausgewiesene Einträge"
          },
          {
            "level": 2,
            "id": null,
            "text": "Alle Kategorien unter „419“, mit Angabe des Objekts, auf das sich der jeweilige Preis bezieht"
          },
          {
            "level": 2,
            "id": null,
            "text": "Die Regale, in denen das steht, was Steam nicht anbietet"
          },
          {
            "level": 2,
            "id": null,
            "text": "Wie knapp das Angebot tatsächlich ist"
          },
          {
            "level": 2,
            "id": null,
            "text": "Was die Regale von Drittanbietern tatsächlich erzielten"
          },
          {
            "level": 2,
            "id": null,
            "text": "Sechzehn Jahre alte Aufkleber und eine Handvoll Handschuhe"
          },
          {
            "level": 2,
            "id": null,
            "text": "Höchststände, die durch eine Transaktion und nicht durch eine Börsennotierung gestützt werden"
          },
          {
            "level": 3,
            "id": null,
            "text": "Die dreißig höchsten abgeschlossenen Verkäufe in diesem Zeitraum"
          },
          {
            "level": 3,
            "id": null,
            "text": "Derselbe Artikel, derselbe „90“-Tag, aber ein himmelweiter Preisunterschied"
          },
          {
            "level": 2,
            "id": null,
            "text": "Woher das stammt und was es nicht zeigen kann"
          },
          {
            "level": 3,
            "id": null,
            "text": "Quelle und Zugriff"
          },
          {
            "level": 3,
            "id": null,
            "text": "Wie ein Artikel die Voraussetzungen erfüllt"
          },
          {
            "level": 3,
            "id": null,
            "text": "Was wir nicht erhalten konnten"
          },
          {
            "level": 3,
            "id": null,
            "text": "Benotung"
          },
          {
            "level": 3,
            "id": null,
            "text": "Warum die Summen einen Mindestwert darstellen"
          },
          {
            "level": 3,
            "id": null,
            "text": "Überzeugen Sie sich selbst"
          },
          {
            "level": 3,
            "id": null,
            "text": "Eine Korrektur, die öffentlich verzeichnet wurde"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/de/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/de/skin_atlas#gallery",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://skinport.com/market?search=AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260924114457/https://store.steampowered.com/subscriber_agreement/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-atlas.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-artefact-screen.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-above-the-ceiling.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/de/skin_atlas.content.json",
      "export_json_sha256": "9ad71eeb14f395d35e4f758c6fb06224749c0968971a32c0eef593c60d6ccae4"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "de/social_graph.html",
      "language": "de",
      "title": "Verfolgen Sie die nachgewiesenen Verbindungen – Das Dossier „Steam“",
      "source_url": "https://phishdestroy.io/steam_dossier/de/social_graph",
      "source_html_sha256": "d13f7137f10c570b513985d2a439bfb32d2373bba22b1158330d8a50aea01968",
      "exported_at": "2026-09-29T00:16:14.852Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "social_graph.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/de/social_graph.pdf?v=print-20260929-v5",
        "sha256": "267c1f623456d2822b4e6a39a59451e9f96f524b8899902bdd4cdd6fa1d6ba5f",
        "bytes": 120797,
        "pages": 6
      },
      "integrity": {
        "signed_object": "social_graph.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "social_graph.content.json.asc",
        "digest_file": "social_graph.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify social_graph.content.json.asc social_graph.content.json",
          "sha256sum -c social_graph.content.json.sha256"
        ]
      },
      "content": {
        "text": "Folgen Sie den Verbindungen.Überprüfen Sie jede Beziehung.\n\nSuchen Sie nach einem Profil. Wählen Sie eine Beziehungsart aus. Verfolgen Sie die direkten Nachbarn in den erfassten Datensätzen. Recherchetool: Kanten stehen für öffentliche Beziehungen und sind kein Beweis für direkten Kontakt, private Absprachen oder Fehlverhalten zwischen zwei beliebigen Knoten. Ein „3,435-“-Knotenlayout lässt sich am besten mithilfe von Filtern interpretieren.\n\nEntdecke jeweils eine Beziehung nach der anderen\n\n💡 Klicken und ziehen Sie die Knoten, um das Diagramm neu anzuordnen. Bewegen Sie den Mauszeiger darüber, um detaillierte Profile anzuzeigen. Türkisfarbene durchgezogene Linien = Freundschaften, bernsteinfarbene gestrichelte Linien = Gemeinsame Kommentare.\n\nBeziehungstypProfil und direkte Nachbarn\n\n3,435 Profile · 4,551 gespeicherte Links\n\nSuchen und wählen Sie ein Profil aus oder klicken Sie auf einen Knoten. Es bleiben nur dessen direkt verzeichnete Nachbarn übrig. Eine Kante dokumentiert eine Beziehung; sie begründet keine private Koordination.\n\nProfile im erfassten Datensatz\n\nVollständige Quelltabelle: Alle „3,435“-Zeilen herunterladen (CSV). Die folgende Tabelle zeigt zunächst die ersten 25 Zeilen; über die Suchfunktion und die Paginierung lässt sich der gesamte Datensatz einsehen.\n\n1–25 / 3,435 Zeilen\nName der Persona\tSteamID64\tDatenschutz\tStatus\tGruppenmitgliedschaften\tGebundene Lagerbestände (USD)\tStandort\nMahatma Gandhi\t76561198333721623\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tPH\nGalley//갤리🌠🌙\t76561198043416832\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tKP\n$Schlächter\t76561198860277343\tPUBLIC\tClean\tsteambans\t$0.00\tUnknown\n❄r3dsn0w000™❄ [Cristi]🎮\t76561197986767957\tPUBLIC\tClean\tCommunityLegends\t$0.00\tRO\n(2a03) Wolfy\t76561197991671851\tPUBLIC\tCommunity\tsr_public\t$0.00\tUS\nZloy2288\t76561198038578334\tPUBLIC\tClean\tsteambans\t$0.00\tBY\njessy\t76561198039125237\tPUBLIC\tCommunity, VAC (1x)\tCommunityLegends\t$0.00\tJP\nJithraRufure\t76561198071896910\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\n| Níllerdínho |\t76561198003487438\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tDK\nJones is back\t76561198023013026\tPRIVATE\tVAC (1x)\tsteambans\t$0.00\tUnknown\nUNEX | ★✠☠ MoH3st ☠✠\t76561198050763123\tPUBLIC\tClean\tsteambans\t$0.00\tDE\nTrojan\t76561198048457084\tPUBLIC\tClean\tCommunityLegends\t$0.00\tDE\n𝗠𝗮𝘆𝘂 ❤\t76561199377967696\tPUBLIC\tClean\tsr_public\t$0.00\tIS\nbig fucking idiot\t76561198871206397\tPUBLIC\tVAC (1x)\tsteambans\t$0.00\tUnknown\nSOFF Games\t76561198227129276\tPUBLIC\tClean\tcommunitymoderators\t$0.00\tRU\nThijminecraft02\t76561198253895669\tPUBLIC\tClean\tSteamIDcouk SArchive\t$0.00\tNL\nStatic-sama\t76561198289329793\tPUBLIC\tClean\tsteambans\t$0.00\tJP\n𝙸mmortal 𝚂targazer\t76561198142116760\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\nCommander Keen\t76561197987773287\tPUBLIC\tClean\tsteambans\t$0.00\tBE\nS1mX\t76561199648509165\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\nmixwell\t76561199276547472\tPUBLIC\tClean\tsr_public\t$0.00\tJP\nP90_GOD_YyEs™\t76561198285821942\tPUBLIC\tClean\tsteambans\t$0.00\tHK\nhewwo?\t76561199133807546\tPUBLIC\tVAC (1x)\tsteambans\t$0.00\tCH\n♕Kamikaze Atze♕\t76561198002700103\tPUBLIC\tClean\tsteambans\t$0.00\tDE\nPastica\t76561198154655970\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tDZ\nErfasste Freundschaftsverbindungen\n\nVollständige Quelltabelle: Alle „4,299“-Zeilen herunterladen (CSV). Die folgende Tabelle zeigt zunächst die ersten 25 Zeilen; über die Suchfunktion und die Paginierung lässt sich der gesamte Datensatz einsehen.\n\n1–25 / 4,299 Zeilen\nBenutzer A\tRichtung\tBenutzer B\tBeziehungstyp\nMahatma Gandhi\n76561198333721623\t↔\tDeskjet\n76561198272738437\tMutual Friends\nGalley//갤리🌠🌙\n76561198043416832\t↔\tomega\n76561197960274529\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tFisty\n76561198057301486\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tFaalagorn\n76561198001116101\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tMURK\n76561198036995672\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tÅρøᴛʜℯᴛȋᴄÅʟȋℯη ♛👽♛\n76561197984615267\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tsilatrak\n76561197999629462\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tBlack Blade\n76561198083368493\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tAvenger\n76561197978249317\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tRemtar\n76561198124322650\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tCato\n76561197961345984\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t✪ G λ M Ξ ®\n76561197994308495\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tclees42\n76561198030936806\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t𝓜ε𝔰𝔥 | AusLevels\n76561198108828539\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tSgtFopper™\n76561198002555892\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t❥Miss Bee\n76561198046958996\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tTesTy\n76561198032370068\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tskl_andrey\n76561198136881436\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t\"Exekutor\"\n76561198009583947\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tAraripe\n76561198103754372\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tsteve6678\n76561198053200093\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\ttrinner\n76561197970359081\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tSteph S.\n76561198025653291\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tKirito\n76561198154545657\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tDoc. todt\n76561197984492467\tMutual Friends\nLinks zu aufgezeichneten Kommentaren\n\nVollständige Quelltabelle: Alle „252“-Zeilen herunterladen (CSV). Die folgende Tabelle zeigt zunächst die ersten 25 Zeilen; über die Suchfunktion und die Paginierung lässt sich der gesamte Datensatz einsehen.\n\n1–25 / 252 Zeilen\nAutor\tRichtung\tZielgruppenprofil\tDatum\tKommentartext\nDeskjet\n76561198272738437\t→\tMahatma Gandhi\n76561198333721623\t16 September, 2021 @ 11:02:05 pm PDT\t\"𝑵𝒐𝒘 𝒊𝒇 𝑰 𝒇𝒖𝒄𝒌 𝒕𝒉𝒊𝒔 𝒎𝒐𝒅𝒆𝒍𝑨𝒏𝒅 𝒔𝒉𝒆 𝒋𝒖𝒔𝒕 𝒃𝒍𝒆𝒂𝒄𝒉𝒆𝒅 𝒉𝒆𝒓 𝒂𝒔𝒔𝒉𝒐𝒍𝒆𝑨𝒏𝒅 𝑰 𝒈𝒆𝒕 𝒃𝒍𝒆𝒂𝒄𝒉 𝒐𝒏 𝒎𝒚 𝑻-𝒔𝒉𝒊𝒓𝒕𝑰'𝒎𝒎𝒂 𝒇𝒆𝒆𝒍 𝒍𝒊𝒌𝒆 𝒂𝒏 𝒂𝒔𝒔𝒉𝒐𝒍𝒆\" - Nelson Mandela\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t22 November, 2021 @ 4:10:28 pm PDT\thttps://anige.horigiri.net/?cat=22\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t18 November, 2021 @ 12:45:26 am PDT\thttps://gamerch.com/umamusume/entry/250411\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t8 August, 2021 @ 4:13:25 am PDT\thttps://modoocode.com/304\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t6 February, 2021 @ 3:35:05 pm PDT\t▤ ∫︹- -ω⁾ ⁽︹▓▓︺\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t11 December, 2019 @ 1:50:53 am PDT\thttps://blog.naver.com/aksenwlddj12/221369410039\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t2 October, 2019 @ 7:11:59 am PDT\tǤαllєу║︎갤리..۩\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t9 April, 2019 @ 12:51:28 pm PDT\tExplosiveDamage(owner, from, maxrange, minrange, distmultiplier, dmgmultiplier, mindamage, typ, damagetype, ignore)\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 12:22:47 pm PDT\tinfo - sh_titles.lua\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 12:21:46 pm PDT\tlocal nibbas = 1344 init.lua\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 11:31:58 am PDT\thttp://foreign.aladin.co.kr/shop/wproduct.aspx?ItemId=123955531&start=slayer\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t3 April, 2019 @ 1:26:41 am PDT\tǤαllєу\nLei\n76561198982197954\t→\tJithraRufure\n76561198071896910\t29 December, 2024 @ 12:58:08 pm PDT\t+rep he knows how 2 rush B ￣ヘ￣\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t2 September, 2026 @ 5:16:55 am PDT\tlol\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t20 August, 2026 @ 6:11:03 am PDT\t?\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t25 July, 2026 @ 7:20:05 am PDT\thahahahaha\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t30 June, 2026 @ 12:52:42 pm PDT\twow\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t30 June, 2026 @ 12:41:32 pm PDT\txD\nvalorant enjoyer\n76561199112142402\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:26:30 pm PDT\toh no!!\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:26:11 pm PDT\toh no!!\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:22:22 pm PDT\tomg !!! they know my secret, omg!!!\nvalorant enjoyer\n76561199112142402\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:21:39 pm PDT\t+rep good ♥♥♥♥♥ player\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:20:50 pm PDT\tomg! u cant cheat on secure gaben servers, omg dont report me, they ban me for boosted omg\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 8:37:11 pm PDT\txD\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t28 June, 2026 @ 1:58:14 pm PDT\twow",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Folgen Sie den Verbindungen.Überprüfen Sie jede Beziehung."
          },
          {
            "level": 2,
            "id": null,
            "text": "Entdecke jeweils eine Beziehung nach der anderen"
          },
          {
            "level": 2,
            "id": null,
            "text": "Profile im erfassten Datensatz"
          },
          {
            "level": 2,
            "id": null,
            "text": "Erfasste Freundschaftsverbindungen"
          },
          {
            "level": 2,
            "id": null,
            "text": "Links zu aufgezeichneten Kommentaren"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-profiles.csv",
          "https://steamcommunity.com/profiles/76561198333721623",
          "https://steamcommunity.com/profiles/76561198043416832",
          "https://steamcommunity.com/profiles/76561198860277343",
          "https://steamcommunity.com/profiles/76561197986767957",
          "https://steamcommunity.com/profiles/76561197991671851",
          "https://steamcommunity.com/profiles/76561198038578334",
          "https://steamcommunity.com/profiles/76561198039125237",
          "https://steamcommunity.com/profiles/76561198071896910",
          "https://steamcommunity.com/profiles/76561198003487438",
          "https://steamcommunity.com/profiles/76561198023013026",
          "https://steamcommunity.com/profiles/76561198050763123",
          "https://steamcommunity.com/profiles/76561198048457084",
          "https://steamcommunity.com/profiles/76561199377967696",
          "https://steamcommunity.com/profiles/76561198871206397",
          "https://steamcommunity.com/profiles/76561198227129276",
          "https://steamcommunity.com/profiles/76561198253895669",
          "https://steamcommunity.com/profiles/76561198289329793",
          "https://steamcommunity.com/profiles/76561198142116760",
          "https://steamcommunity.com/profiles/76561197987773287",
          "https://steamcommunity.com/profiles/76561199648509165",
          "https://steamcommunity.com/profiles/76561199276547472",
          "https://steamcommunity.com/profiles/76561198285821942",
          "https://steamcommunity.com/profiles/76561199133807546",
          "https://steamcommunity.com/profiles/76561198002700103",
          "https://steamcommunity.com/profiles/76561198154655970",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-connections.csv",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-comments.csv"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/de/social_graph.content.json",
      "export_json_sha256": "4a627397035dd49f0e2e1e2f4f79541d1f735d43341ba1a5c0e98b8636f0e177"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "de/steam_enforcement_evidence.html",
      "language": "de",
      "title": "Regeln versus Reaktionen – Das Dossier „Steam“",
      "source_url": "https://phishdestroy.io/steam_dossier/de/steam_enforcement_evidence",
      "source_html_sha256": "eee12d4c46bef88e55dcdb7c0290ad917f9ee68a40566a0b8dd7203d877d15ec",
      "exported_at": "2026-09-29T00:16:15.341Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "steam_enforcement_evidence.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/de/steam_enforcement_evidence.pdf?v=print-20260929-v5",
        "sha256": "7410268cb86e44f94e872df7f097440dfdac18f9db4afa0aa115c87ce9bad3e8",
        "bytes": 381262,
        "pages": 36
      },
      "integrity": {
        "signed_object": "steam_enforcement_evidence.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "steam_enforcement_evidence.content.json.asc",
        "digest_file": "steam_enforcement_evidence.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify steam_enforcement_evidence.content.json.asc steam_enforcement_evidence.content.json",
          "sha256sum -c steam_enforcement_evidence.content.json.sha256"
        ]
      },
      "content": {
        "text": "Ergänzende Nachweise / quellenverknüpfte Datensätze\nSteam Nachweise zur Durchsetzung – Belege und Entwicklernetzwerk\n\nDie Regel. Die Antwort.\n\nWAS DIESER ABSCHNITT BELEGT\n\nDieser Beweisraum vergleicht die offizielle Abonnentenvereinbarung von „Valve“ mit datierten Durchsetzungsprotokollen, Lösungen von Support-Streitfällen und Aufzeichnungen des Entwicklernetzwerks in den Repositorys unter 252 und den Profilen unter 3,320. Er zeigt, dass gewöhnliche Kontoinhaber nach Kompromittierungen ihrer Sitzungen mit unwiderlegbaren Durchsetzungsmaßnahmen und der Schließung von Support-Fällen konfrontiert sind, während kommerzielle Bot-Operationen mit hohem Volumen dank des Zugangs zur öffentlichen Infrastruktur kontinuierlich weiterlaufen.\n\n← Zurück zum Executive Briefing\n\nLesen Sie die schriftliche Einschränkung. Öffnen Sie die aufgezeichnete Antwort. Vergleichen Sie die Angaben in der Quelle mit den noch unbeantworteten Fragen.\n\nUnterstützung & Einsprüche ↓Öffentliche Infrastruktur ↓\n252Bestandsdaten\n3,320öffentliche Profile\n4,214eindeutige Profil-Repository-Paare\n98,902Profilpaare mit gemeinsamen Repos\n01 / Unterstützung, Sanktionen und Wiederaufbau\nLesen Sie die Beschwerde.Fügen Sie die Quelle bitte bei.\nGalerie „Ablehnungen“ (Ausstellungen der 981) ↗Ausgewählte Datensätze herunterladen ↓\nHFB / DER OUTSOURCING-FALLDer anerkannte Kompromiss.\nDie gemeldeten Entlassungen.\n\nBeachten Sie die wiedergegebene Antwort des Supports und die Quelle der Behauptung bezüglich der Mitarbeiter von Auftragnehmern.\n\nDen Fall und seine Quellen öffnen →\n\nUnten: fünf erhaltene öffentliche Reddit-Beiträge aus der bereitgestellten Support-Sammlung. Jeder Eintrag dokumentiert eine gemeldete Interaktion mit dem Support-System von Valve – einschließlich des ursprünglichen Quelllinks, der Erfassungsposition und des vollständigen Textes. Es handelt sich hierbei um Schilderungen von Betroffenen. Die authentifizierten Support-Protokolle, die diese Schilderungen bestätigen oder widerlegen würden, befinden sich im Besitz von Valve und wurden nicht offengelegt.\n\n01\nBan & review2024-12-09\nPermanent sanction & closed appeals\n\nThe author reports a permanent account ban, repeated ticket closures and a planned GDPR access request.\n\nREDDIT / PUBLIC TESTIMONYr/ohnePixelCapture record 294\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 303 words\nPermanently banned Steam account without a clear explanation, need help!\n\nsteam_support_tickets_MEGA.json / record 294\n\nHey everyone,\n\nI’m in a really frustrating situation, and I’m hoping someone here can help me or offer advice. My Steam account was just permanently banned for allegedly violating the Steam Subscriber Agreement, and I have no idea why.\n\n# What Steam Support told me:\n\nThe support message said my account was banned due to:\n\n* Suspicious activities related to transferring or attempting to sell/trade the account.\n* Community reports and other unspecified factors.\n\nThey added that the ban is permanent and that they can't help me further. They also warned that future support requests regarding this ban might be ignored. 😞\n\n# Why I’m contesting this ban:\n\n* I have never sold, traded, or transferred my account. I’ve been the legitimate owner since the beginning.\n* On the day the ban occurred, I did nothing noteworthy that could have triggered such a sanction.\n* I received no prior warning, which feels incredibly unfair.\n\n# What I’ve tried so far:\n\n* Contacting Steam Support: I explained my situation and asked for more details, but they’re sticking to their decision and closing my tickets.\n* I’m preparing a request based on my Right of Access (GDPR) to get all the data related to my account.\n\n# Questions for the community:\n\n1. Has anyone successfully had a permanent ban lifted on Steam?\n2. Are there steps I can take to prove I’m the legitimate owner of the account?\n3. Any advice on how to word my request to convince support to reconsider my case?\n4. Would it be helpful to contact the CNIL (I’m based in France) to force Steam to provide more information?\n\nI’m really desperate at the thought of losing all my games, purchases, and years of playtime. Thanks in advance for any help and advice you can give!\n\nhttps://preview.redd.it/jk9qv0gmhv5e1.png?width=1289&amp;format=png&amp;auto=webp&amp;s=b3a333ebb08ea133e2c8747ba126f5a68283d9f7\n\nhttps://preview.redd.it/4sopt0gmhv5e1.png?width=1022&amp;format=png&amp;auto=webp&amp;s=56195d5336118faf9413f1514ead7e8d24c788c3\n\nhttps://preview.redd.it/eqrxw0gmhv5e1.png?width=996&amp;format=png&amp;auto=webp&amp;s=ff3539d28ab754e513ad471822c5de652920101d\n\nhttps://preview.redd.it/728xz0gmhv5e1.png?width=1034&amp;format=png&amp;auto=webp&amp;s=bc5335673509929669af785aa244bf8d2dc58da8\n\n02\nSupport access2025-05-09\nAccount recovery & a reported $10,000 loss\n\nThe author alleges that support reset credentials and removed account protection following another person’s recovery ticket.\n\nREDDIT / PUBLIC TESTIMONYr/legaladviceCapture record 110\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 193 words\nGot $10k stollen from steam inventory due to steam' support fault.\n\nsteam_support_tickets_MEGA.json / record 110\n\nLocation: Quebec, Canada.\n\nLast year, someone hacked my Steam account and stole items worth about $10,000 USD. I only noticed this last week. When I talked to Steam Support, they admitted that someone submitted a ticket to make changes on the account and Steam Support reset my password and turned off all my account security.\n\nI asked Steam Support about getting my items back, but they said there was nothing they could do. They told me I should follow their security recommendations.\n\nThe problem is, I did everything they \"suggested\" to protect an account:\n\n* I had two-factor authentication.\n* My phone number was connected to my account.\n* I used Steam Guard.\n* I printed recovery codes and kept them in a safe.\n\nEven though I did all these things, Steam Support still gave someone else access to my account. The stolen items had been in my account since around 2016-2017. Also, I had not logged in for a few years, so I didn’t accidentally give my information to a fake website.\n\nIs there anything I can do, or do I just have to accept losing $10,000 USD?\n\nThanks for your help.\n03\nRestoration2022-07-07\nA reported $500+ loss & template replies\n\nThe author describes an account compromise, disputed transactions and a support response that allegedly did not address the submitted evidence.\n\nREDDIT / PUBLIC TESTIMONYr/DotA2Capture record 45\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 410 words\nFunds stolen through steam market. Disappointed with Steam response.(or lackthereof)\n\nsteam_support_tickets_MEGA.json / record 45\n\nOn 6th July 2022, 44 unauthorized transactions were made on the steam market using my steam wallet funds totalling roughly $500+ USD to buy worthless 1 cent Dota 2 items. This happened during the wee hours in the morning and i contacted them first thing when i woke up. \n\nI have 2FA enabled all the time, and always thought this would not happen to me as I do not go on betting sites/click sketchy links. My account password + emails were not changed, nor did they take my inventory, just that my funds were used illicitly. Also when I went to disable other APIs, it says there are no other APIs to disable. Shows that it wasn't through me clicking sketchy links and leaving my account details there. Would have lost the whole account if i did so.\n\nWhat baffles me is how did they bypass my 2FA to login my account? Why doesn't steam market purchases go through 2FA as well? First time in 9 years that this happened to me. My acc was logged in 'BY' 'Vitebsk' during the illicit purchases but I'm based in Asia I gathered all the screenshots and provided in the ticket to steam support. \n\nAll i got was the standard copy paste template reply by Steam Support. Lost $500+ and was not even worthy of having a proper person to look into this. I dont think they even read or take a look at the screenshots cause if they did, they would have come to the realization that what happened was clearly fraud, and with a few clicks, reverse the unauthorized transactions, refund my wallet and ban the hijacker. \n\nOver the years, i've spent quite a fair bit on steam but really, this is the kind of recourse we get when our account is compromised? They just don’t care, sigh. I only expect the bare minimum from Steam and looks like even that is quite far-fetched.\n\nSS: https://imgur.com/a/67frcls \n\nHijacker: https://steamcommunity.com/profiles/76561199141246495\n\nSteam Response: https://imgur.com/a/V6v4maM\n\nI could think of a few ways on how to Improve:\n\n1) Add 2FA to market transactions. (even if its bulk posting or selling of items, just 1 2FA notif is required)\n\n2) Enable accounts to be region locked. (if you are migrating, then have to go through steam support etc)\n\n3) Additional Lock on Steam Wallet. (Another password perhaps?)\n\nEDIT: 2nd ticket in and I have still yet to receive a non robotic copy paste template response from Steam.\n04\nRestoration2021-11-29\nSteam Guard & an item-restoration refusal\n\nA preserved post includes the author’s account of item theft and a support response declining restoration.\n\nREDDIT / PUBLIC TESTIMONYr/DotA2Capture record 58\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 563 words\nMany people are losing item via clicking links where steam guard is enabled and steam support doesn't not restore items.\n\nsteam_support_tickets_MEGA.json / record 58\n\nAccounts are getting compromised and might be their pc as well where Steam market is targeted hence the malicious links . I am assuming these hackers are getting encouraged where steam support is not doing nothing and they are getting away with hacking items.  \nLiterally the guy who is supporting the game which he doesn't get any in game advantage just  cosmetics in game only for the sole purpose of supporting the game so that the game will prosper and become beautiful way  to enjoy weekend. But right now players are getting hacked left right and center and steam support  is copy pasting message where in short they are blaming the guy who clicked link. 1st this is happening because they are not targeting players but they are targeting market since they are selling those stuff for real cash via party website. Steam is a huge company and can eradicate the problem or at least can remove links temporarily  in chat since hackers are targeting .They made us install steam guard by saying we wont help if there is no steam guard now steam guard is not enough to save our inventory now they changed their policy  that they should not click any suspicious links. How would we know if the link is suspicious ? After clicking and getting our inventory stolen right !   \n\"we'd have to duplicate an item to restore it. Duplication lowers the value of all items by reducing their scarcity and inflating the economy, which affects everyone involved in trading and the Market. To maintain the value of everyone’s inventory, we do not restore items. For more information, please see the Steam Item Restoration Policy.\"  \nThey care for millions of people IN STEAM MARKET where as few  are losing items which is going to affect market where the rightful owner bought the items and hacker is going to sell the item via 3rd party website and enjoy ! HOW IRONIC !!  \nThis is the message from support where my frnd got his items stolen via clicking on link  \n   \nHi there,  \n\nThank you for the information and screenshots provided.  \n\nIt appears that the account was compromised, please take the following steps to secure your account and computer:  \n\nScan your computer for viruses, key loggers, spyware, and other malicious code using antivirus software with updated virus definitions.  \nChange the password for the email address that is associated with your Steam account.  \nRegularly reset your Steam account password.  \n\nPlease see our Security Recommendations article.  \n\nIn addition, I’m sorry to hear that your items were removed without your permission. Unfortunately, Steam Support does not restore scammed, lost, or stolen items for any reason.  \n\nSince Steam Support does not remove items from accounts, we'd have to duplicate an item to restore it. Duplication lowers the value of all items by reducing their scarcity and inflating the economy, which affects everyone involved in trading and the Market. To maintain the value of everyone’s inventory, we do not restore items. For more information, please see the Steam Item Restoration Policy.  \n\nTo make sure that a scammer is reported, please report them through the Steam Community. Reporting a scammer through the Steam Community is the best way to prevent them from committing future scams.  \n\nTo learn how to avoid scams or hijackings, please see our Trade Scam article.  \n\nIf you still need assistance, please let us know.\n05\nEnforcement2025-05-11\nSelective enforcement & an unexplained ban\n\nA community member describes a disputed ban and contrasts it with the visibility of commercial gambling promotion.\n\nREDDIT / PUBLIC TESTIMONYr/SteamUncensoredCapture record 107\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 1,208 words\n🚨 Steam Bans Without Reason and Ignores Its Community — What’s Going On?\n\nsteam_support_tickets_MEGA.json / record 107\n\nHey r/Steam,\n\nI’m writing this to share my thoughts and concerns about my friend [moneylead](https://steamcommunity.com/id/moneylead/) and Steam’s policies in general. I spoke with him yesterday about his situation, though I didn’t discuss writing this post with him—I asked last night, but he hasn’t responded yet. I want to highlight that this issue is broader than just his case, and while Steam might make changes in the future (though that’s unlikely), I feel the community needs to understand how far Steam has strayed from its original values. I’m not trying to put moneylead in a tough spot with this thread—all the info I’m sharing is public, nothing secretive. I hope he won’t be upset with me, but the community needs this case to see the bigger picture and how Steam feels completely unaccountable.\n\n**Why Does Steam Ignore Its Community?**  \nWhy does a platform like **Roblox** provide a detailed log of ban reasons, while Steam, which claims to be \"community-driven,\" ignores its community, bans whoever they want, for whatever they want, with no transparency? I looked into Roblox as a popular game—not a direct competitor to Steam—to see how their bans look, and you can check it out yourself: [Roblox Ban Reasons](https://www.google.com/search?q=Roblox+ban). Their bans are clear, detailed, and actually explain what you did wrong. I think most decent gaming communities operate like this—not with support agents named Olga, hired through outsourcing, who only know how to send canned auto-replies. Take cases like St4ck—or my friend **moneylead**. All these unbans, like **St4ck’s** or **Alexanddd’s**, happened behind closed doors with zero comments from Steam. Of course, it’s convenient for Steam to handle everything in secret, so no one knows or sees what’s going on—but this violates Steam’s own community rules and principles.\n\n**Who Is moneylead?**  \nI’ve known [moneylead ](https://steamcommunity.com/id/moneylead/)since around 2021. We played Dota 2 a couple of times, and then I just stayed on his friends list. He’s always been a legit player, bringing revenue to Steam through purchases. He never sold his skins, whether in **Dota or CS2—he wasn’t a trader**. All he did was:\n\n* Buy games and skins.\n* Collect badges to level up his profile.\n\nAccording to [SteamSets](https://steamsets.com/account/76561199080934614), he’s given out 324,000 Steam Points—I think he awarded profile rewards to all his friends in the list (though I’m not 100% sure). I do know he ran contests and gave gifts to friends, always supporting the community.\n\n**Steam’s Unfair Treatment**  \nI’ve seen Steam remove his showcases, avatar, description, and even his country multiple times—just because he’s from **Ukraine**. He has a ton of haters leaving toxic comments on his wall, and Steam seems to favor **Russian** users. Every time he tried to appeal the removal of his showcases or profile description—which didn’t break any rules, just had his Instagram link, and his avatar is the same as it is now—Steam moderators didn’t care. **They don’t care about top players who bring them massive revenue, nor about regular users.**\n\n>*Here’s the worst part: moneylead works in cybersecurity, specifically fighting account theft and phishing. He’s neutralized over 5,000 threats targeting Steam alone. And yet, Steam bans him for \"account hijacking\"?*\n\nIf you roughly calculate moneylead’s contribution to Steam and the community—his profile, level, badges (not skins, you can’t sell those)—is this normal, Steam? Banning people, closing tickets, and ignoring users with a spotless reputation who aren’t involved in any commercial activity, just bringing you profit without taking anything in return?\n\n**Steam’s Double Standards**  \nI’m honestly shocked:\n\n* YouTubers who promote casinos and skin gambling? Steam’s fine with that.\n* A cybersecurity expert who fights scams, doesn’t promote casinos, and openly talks about it on his profile? **Banned with no explanation, ignored, and denied an unban.**\n\nI wonder if Steam deliberately bans a high-level account once a year just because of their impunity—maybe for hype or something. Otherwise, this is just madness. It’s scary to think how many regular players have lost their accounts and skins—not because of scammers, but because of Steam’s desire to ignore, send auto-replies, and do whatever they want.\n\n**How Many Others Are Affected?**  \nHow many others are out there—maybe not as well-known—who just have a few games or skins, get banned for nothing, and receive zero explanation or response? **Is this even legal?** Every other platform provides a detailed log with specific violations, but Steam slaps on the same vague label and sends templated responses.\n\n* How safe is it to buy skins on Steam?\n* What’s the chance Steam will just ban your account for no reason, with no explanation?\n\n**A Message to Valve**  \nI wish moneylead the best in resolving this, but Valve, it’d be great if you remembered what \"community\" means and started following the law. Because right now, it looks like your 30% commission, impunity, and sense of being above the law in the U.S. have given you the idea that you can do whatever you want.\n\nI’m sure there are many others like moneylead and St4ck—people who aren’t public or don’t have the resources to fight back. Let’s unite these cases. **If you’re a U.S. resident who’s been banned by Steam without reason and wants to challenge it, please reach out to me.** I’m finishing my **Juris Doctor (J.D.) program at SMU Dedman School of Law** in Dallas, Texas, and I’m participating in a legal clinical practice under Rule 13 of the Texas Supreme Court.\n\nWhat Steam is doing is absolutely disgusting and illegal, and **I’d be happy to help any gamer (legitimate, with no real violations) who has games or skins with value. This will be beneficial for my practice, and it’s time to put Steam in its place and show them they can’t just dictate their own rules with arbitration**. Let’s take it all the way—not for punishment, but for the sake of the community. Maybe if Steam loses a case, they’ll change their policies and start explaining their actions like most popular gaming communities do. Many of us remember how Steam Support used to recover stolen accounts and ended up “stealing” skins themselves—banning without real reasons is basically the same thing, and that’s a serious accusation.\n\nSo, r/Steam, see you soon. I think you understand what you’re doing and how many people you’ve illegally deprived of their assets. I want to raise this issue—not just for the U.S., but for the entire world. You’ve banned class-action lawsuits? **Welcome to Texas.** I recommend starting to look for licensed attorneys in Texas, because I’d love to discuss your company’s policies, feedback, and support agents named Olga—a name that strongly associates with Russian users. Maybe it’d be easier to move your company to Moscow? But I’d be happy to discuss these critical issues on behalf of the global gaming community.\n\nAlso, I wouldn’t recommend ignoring the lawsuit request that will be sent to your physical address and email address, as the court will proceed without you, and that might upset you—especially since things aren’t going so well for a company with stocks like yours.\n\n**Thanks to everyone who took the time to read this. For those who need real help with an unjust Steam ban without any explanation, I’d be happy to assist. For users from Texas, we can easily file a collective lawsuit against Steam—let’s connect and make it happen.**\n02 / Entwicklungsnetzwerk „Steam“\nÖffentliche Infrastruktur.In großem Maßstab aufgezeichnet.\nAlle „252“-Aufnahmen herunterladen ↓\n\nDas mitgelieferte output_steam_network Snapshots erfassen Repositorien, öffentliche Beziehungen zwischen Mitwirkenden und Forks sowie Profilüberschneidungen. Dabei handelt es sich um veröffentlichte Aufzeichnungen – was erstellt wurde, wer dazu beigetragen hat, was geforkt wurde. Diese dokumentierten Nachweise öffentlicher Fähigkeiten müssen von „Valve“ berücksichtigt werden.\n\nRepository / Beschreibung\tMitwirkende\tGabelhalter\tGespeicherte Profile\nalliedmodders/amxmodx\n\nAMX Mod X - Half-Life 1 Scripting and Administration\n\n\t40\t40\t80\nalliedmodders/sourcemod\n\nSourceMod - Source Engine Scripting and Administration\n\n\t40\t40\t80\nDoctorMcKay/node-steam-user\n\nAllows interaction with the Steam network via the Steam client protocol\n\n\t40\t40\t80\nFacepunch/Facepunch.Steamworks\n\nAnother fucking c# Steamworks implementation\n\n\t40\t40\t80\nJustArchiNET/ArchiSteamFarm\n\nC# application with primary purpose of farming Steam cards from multiple accounts simultaneously.\n\n\t40\t40\t80\nodota/core\n\nOpenDota: Open source Dota 2 data platform with automated replay parsing\n\n\t40\t40\t80\nodota/dotaconstants\n\ndotaconstants: Static data for Dota applications\n\n\t40\t40\t80\nodota/web\n\nOpenDota: React web UI for Dota 2 statistics using the OpenDota platform\n\n\t40\t40\t80\nsplewis/get5\n\nCS:GO Sourcemod plugin for competitive matches/scrims\n\n\t40\t40\t80\nSteamDatabase/FileDetectionRuleSets\n\n🔎 Rules to detect game engines and other technologies based on Steam depot file lists\n\n\t40\t40\t80\nSteamRE/SteamKit\n\nSteamKit2 is a .NET library designed to interoperate with Valve's Steam network. It aims to provide a simple, yet extensible, interface to perform various actions on the network.\n\n\t40\t40\t80\nValveSoftware/dxvk\n\ndxvk tree containing branches used by Proton\n\n\t40\t40\t80\nValveSoftware/GameNetworkingSockets\n\nReliable & unreliable messages over UDP. Robust message fragmentation & reassembly. P2P networking / NAT traversal. Encryption.\n\n\t40\t40\t80\nValveSoftware/gamescope\n\nSteamOS session compositing window manager\n\n\t40\t40\t80\nValveSoftware/Proton\n\nCompatibility tool for Steam Play based on Wine and additional components\n\n\t40\t40\t80\nValveSoftware/source-sdk-2013\n\nThe 2013 edition of the Source SDK\n\n\t40\t40\t80\nValveSoftware/wine\n\nWine with a bit of extra spice\n\n\t40\t40\t80\nValveSoftware/steam-devices\n\nList of devices Steam and SteamVR will want read/write permissions on, to help downstream distributions create udev rules/etc\n\n\t39\t40\t79\nValveSoftware/steam-audio\n\nSteam Audio\n\n\t38\t40\t78\nalliedmodders/metamod-source\n\nMetamod:Source - C++ Plugin Environment and Detour Library for the Source Engine\n\n\t37\t40\t77\nalliedmodders/sourcepawn\n\nA small, statically typed scripting language.\n\n\t35\t40\t75\nValveSoftware/Fossilize\n\nA serialization format for various persistent Vulkan object types.\n\n\t31\t40\t71\nrlabrecque/Steamworks.NET\n\nSteamworks wrapper for Unity / C#\n\n\t27\t40\t67\nModDota/moddota.github.io\n\nModDota github pages project.\n\n\t26\t40\t66\nodota/parser\n\nReplay parse server generating JSON log events from Dota 2 replay files\n\n\t26\t40\t66\nValveSoftware/steam-for-linux\n\nIssue tracking for the Steam for Linux beta client\n\n\t26\t40\t66\nSteamRE/DepotDownloader\n\nSteam depot downloader utilizing the SteamKit2 library.\n\n\t24\t40\t64\nJustArchiNET/ASF-ui\n\nThe official web interface for ASF\n\n\t23\t40\t63\nadvancedfx/advancedfx\n\nHalf-Life Advanced Effects (HLAE) is a tool to enrich content creation mainly for the Counter-Strike series.\n\n\t22\t40\t62\nalliedmodders/ambuild\n\nAlliedModders C++ Build System\n\n\t23\t39\t62\nSteamDatabase/BrowserExtension\n\n💻 SteamDB's extension for Steam websites\n\n\t21\t40\t61\nodota/mobile\n\nReact Native apps for viewing Dota 2 data on Android/iOS\n\n\t19\t40\t59\nValvePython/steam\n\n☁️ Python package for interacting with Steam\n\n\t18\t40\t58\nskadistats/clarity\n\nComically fast Dota 2, CSGO, CS2 and Deadlock replay parser written in Java.\n\n\t13\t40\t53\nSteamRE/open-steamworks\n\nOpen Steamworks is a set of reverse engineered headers for the Valve's Steam Client. More or less abandoned now that the Steamworks SDK is publically available.\n\n\t13\t40\t53\nValveSoftware/Source-1-Games\n\nSource 1 based games such as TF2 and Counter-Strike: Source\n\n\t13\t40\t53\nalliedmodders/hl2sdk\n\nHalf-Life 2 SDK Mirrors\n\n\t11\t40\t51\nSteamDatabase/steamdb.info-issues\n\n🚱 Issue tracker for the SteamDB website\n\n\t11\t40\t51\nCSGOFloat/inspect\n\nSource Code that Powers the CSFloat Inspect Link API\n\n\t10\t40\t50\nValveSoftware/SteamOS\n\nSteamOS community tracker\n\n\t10\t40\t50\nalliedmodders/source2mod\n\nExperimental\n\n\t40\t9\t49\nsmiley/steamapi\n\nAn unofficial object-oriented Python library for accessing the Steam Web API.\n\n\t9\t40\t49\nSteamDatabase/GameTracking\n\n🛢 Dumping things, so you don't have to\n\n\t8\t40\t48\nValveSoftware/counter-strike_rules_and_regs\n\nCS:GO\n\n\t7\t40\t47\nValveSoftware/openvr\n\nOpenVR SDK\n\n\t6\t40\t46\nSteamDatabase/easy-markdown-editor\n\nEasyMDE: A simple, beautiful, and embeddable JavaScript Markdown editor. Delightful editing for beginners and experts alike. Features built-in autosaving and spell checking.\n\n\t40\t4\t44\nValveSoftware/Dota-2\n\nTracker for issues specific to Linux and Mac in the Reborn client. If you have a general issue or non-system-specific feature request please go to dev.dota2.com\n\n\t6\t38\t44\nValveSoftware/Dota2-Gameplay\n\nPublic Bug Tracker for Dota 2\n\n\t4\t40\t44\nJustArchiNET/ArchiBot\n\nNo description in the capture.\n\n\t16\t27\t43\nztizzlegaming/CSGOWinBig\n\nOpen-source Counter-Strike: Global Offensive jackpot betting website.\n\n\t1\t40\t41\nJustArchiNET/mantis.justarchi.net\n\nMantis Bug Tracker (MantisBT)\n\n\t40\t0\t40\nodota/node-steam-user\n\nAllows interaction with the Steam network via the Steam client protocol\n\n\t40\t0\t40\nModDota/TypeScriptAddonTemplate\n\nDota 2 addon template with TypeScript Panorama and VScripts.\n\n\t9\t29\t38\nValvePython/vdf\n\n📜 Package for working with Valve's text and binary KeyValue format\n\n\t6\t32\t38\nalliedmodders/amtl\n\nAlliedModders C++ Template Library\n\n\t17\t19\t36\nValvePython/dota2\n\n🐸 Python package for interacting with Dota 2 Game Coordinator\n\n\t5\t30\t35\nalliedmodders/stripper-source\n\nStripper:Source\n\n\t13\t21\t34\nAllyans3/steam-market-api-v2\n\nSteam Market API v2 package\n\n\t3\t31\t34\nModDota/dota-tutorial\n\nCustom game DOTA tutorial.\n\n\t11\t23\t34\nodota/blog\n\nNo description in the capture.\n\n\t29\t3\t32\nOpsecGuy/BetterGo\n\nExternal CS:GO cheat written in python.\n\n\t1\t27\t28\npxvr-official/1\n\n無許諾配信 企業理念剽窃 動物の森収益化 大神ミオ権利者削除 戌神権利侵害発言 常闇トワ炎上 夜空メルストーカー被害 建築王サポーター放置 赤十字マーク 魔乃アロエ卒業 一つの中國支持声明 大空昴3Dライブ 無限延期清掃員職業差別 日清コラボ楽曲 musedash非公開 rog案件取り消し 壁画ライブ 丁真 Ding Zhen 郑爽 Zheng Shuang 防护林 与朵小天使w 伊月猫凛 本主萌埋午休傻 汪峰 重生细胞 壁纸 比利海灵顿 香蕉君 van 田所浩二 抽象带篮子 抗压背锅吧 季子越 蒋明辉 傻逼…\n\n\t0\t28\t28\nRevadike/InternalSteamWebAPI\n\nDocumenting the unofficial and internal Steam Web API\n\n\t1\t27\t28\nJoeSzymkowiczFiveM/qb-lootcrate\n\nA CSGO-style case opening script\n\n\t2\t25\t27\nAbrarKL/MyRoulette.XYZ\n\nCSGO / Steam Roulette Site created with PHP and Node JS, using the Material Design front-end framework.\n\n\t1\t25\t26\nJustArchiNET/ASF-WebConfigGenerator\n\nNo description in the capture.\n\n\t10\t15\t25\nModDota/dota-data\n\nAuto-generated Dota 2 resource dumps\n\n\t11\t14\t25\nModDota/TypeScriptDeclarations\n\nTypeScript declarations for Dota 2.\n\n\t11\t14\t25\nModDota/API\n\nNo description in the capture.\n\n\t12\t12\t24\nalliedmodders/cssdm\n\nCounter-Strike:Source Deathmatch\n\n\t10\t13\t23\nSteamDatabase/steamstat.us\n\n✅ Front-end of Steam services status website\n\n\t4\t18\t22\nc0deina/csgojackpotV2\n\nCSGO Jackpot Source\n\n\t1\t20\t21\nValvePython/steamctl\n\n🤸 Take control of Steam from your terminal\n\n\t2\t19\t21\nValvePython/csgo\n\n🔫 Python package for interacting with CS:GO Game Coordinator\n\n\t3\t17\t20\nBeepIsla/csgo-crash-exploit\n\nAllows you to crash any Windows user\n\n\t3\t16\t19\nValvePython/vpk\n\n📦 Open, Search, Extract and Create VPKs in python\n\n\t4\t15\t19\nalliedmodders/SM-SteamWorks\n\nExposing SteamWorks functions to SourcePawn.\n\n\t14\t3\t17\nSteamRE/Steam4NET\n\nSteam4NET is a .NET wrapper around the Steamworks C++ interfaces\n\n\t2\t15\t17\nalliedmodders/hl2sdk-manifests\n\nInformation about HL2SDKs shared between Metamod:Source and SourceMod.\n\n\t6\t10\t16\nJustArchiNET/ASF-PluginTemplate\n\nTemplate repository that you can use for creating custom plugins for ArchiSteamFarm.\n\n\t8\t7\t15\nModDota/Dota2AIFramework\n\nGeneral Framework for Dota 2 AI Competitions\n\n\t1\t14\t15\nShkyyl/KeyChamp\n\nExtension for joining free case battle on key-drop automatically\n\n\t1\t14\t15\nSteamDatabase/SteamMonitor\n\n😤 Track Steam's connection manager servers status\n\n\t2\t12\t14\nBaterka/cslore.com\n\nCS:GO gambling site - csgo.style\n\n\t1\t12\t13\nSteamDatabase/SteamTokenDumper\n\n🔢 Submit users' PICS access tokens to SteamDB\n\n\t2\t11\t13\nmonoblocker/roulette\n\nRoulette CS:GO made in React and Typescript\n\n\t1\t11\t12\nzsith/launcher.user.js\n\n// ==UserScript== // @name AposLauncher // @namespace AposLauncher // @include http://agar.io/* // @version 3.062 // @grant none // @author http://www.twitch.tv/apostolique // ==/UserScript== var aposLauncherVersion = 3.062; Nu…\n\n\t1\t11\t12\nLincolnIT/CSGODouble-bot-automated\n\nCSGODouble Automated, auto Betting Bot.\n\n\t1\t10\t11\nvladpuz/steam-market\n\nSteam market API client\n\n\t4\t7\t11\nmcgrizzz/Cstrike.bet\n\nCSGO Roulette Website Angular frontend, nodejs backend, and steam trading bots\n\n\t1\t9\t10\nodota/underlords-web\n\nUI for OpenUnderlords\n\n\t5\t5\t10\nSteamDatabase/SteamToTwitter\n\n🕊 Tweets announcements from various Steam groups\n\n\t1\t9\t10\nModDota/AbilityLuaSpellLibrary\n\nThe successor to the Spell Library by Pizzalol\n\n\t4\t4\t8\nalvinl/bitskins\n\nUnofficial BitSkins API client\n\n\t2\t5\t7\nb1naryth1ef/steamy\n\nA Python Steam community and market API interface that will get you all hot and bothered\n\n\t2\t5\t7\nkratos1812/Case-Opening\n\nIn-game case opening system for CSGO servers.\n\n\t2\t5\t7\nodota/docs\n\nOpenDota API documentation\n\n\t4\t3\t7\nSteamDatabase/steam-advanced-access-fetch-players\n\n📈 Simple script to fetch Steam player count\n\n\t1\t6\t7\nTheRioMiner/CsgoBetterExternalRaytrace\n\nOverridden maps pack for better external raytrace\n\n\t1\t6\t7\nalliedmodders/hl2sdk-mock\n\nMock HL2SDK and Server\n\n\t5\t1\t6\nchristophersu/PySteamMarket\n\nPython API for getting prices from the Steam market.\n\n\t1\t5\t6\nExtremelyd1/Strat-Roulette\n\nCS:GO Sourcemod Plugin\n\n\t2\t4\t6\ngiovanni-orciuolo/double-sdk\n\nA simple way to write CS:GO cheats!\n\n\t2\t4\t6\nJustArchiNET/Madness\n\nMadness embraces your project by including compatibility layer for selected APIs normally not available on .NET Framework target.\n\n\t5\t1\t6\nModDota/TypescriptPanoramaDeclarations\n\nNo description in the capture.\n\n\t4\t2\t6\nodota/rapier\n\nA JavaScript Dota 2 (Source 2) replay parsing library\n\n\t1\t5\t6\nVozn1akHero/CSGOCaseOpeningSimulator\n\nCounter-Strike case opening simulator which resembles the good old CS:GO user interface\n\n\t3\t3\t6\nautarc/steam-store\n\nAPI client for the unofficial steam storefront/big picture resource\n\n\t2\t3\t5\nBETTING-CODE/awesome-esports-sites\n\nA curated list of awesome esport betting sites – live, statistics and other resources.\n\n\t1\t4\t5\njonteohr/Better-Warden\n\nAn improved and more advanced warden plugin with a custom menu for CS:GO jailbreak servers!\n\n\t2\t3\t5\nLudzikk/CSGO-Gambling-Site\n\nhttps://ludzikk.github.io/CSGO-Gambling-Site/\n\n\t1\t4\t5\nModDota/find-steam-app\n\nFind location of an installed Steam app\n\n\t3\t2\t5\nmprey/csgocact.us\n\nsource code for csgocact.us\n\n\t1\t4\t5\nnezu-cc/ServerCrasher\n\nCS:GO Server Crasher\n\n\t1\t4\t5\nodota/testfiles\n\nStores test replay files\n\n\t2\t3\t5\nodota/underlordsconstants\n\nConstant data for Dota Underlords\n\n\t3\t2\t5\nSnaBe/node-steam-market-fetcher\n\nA Node.js wrapper for the Steam Community Market API.\n\n\t2\t3\t5\nSteamDatabase/.github\n\n💗 Organization-wide community health files\n\n\t1\t4\t5\nwolfcon/RIP-HLTV-BET\n\nRIP BET AD (For Tampermonkey) https://greasyfork.org/en/scripts/423484-rip-hltv-bet\n\n\t2\t3\t5\nalliedmodders/blaster.net\n\nSource and GoldSrc Query Tool\n\n\t2\t2\t4\ncatears124/CS2-Price-API\n\nsimple python cs2 steam market price API\n\n\t1\t3\t4\nialakey/caseforge\n\nOpen-source CS2 case-opening platform: Steam auth, provably fair openings, RTP-balanced case builder, withdrawals bought on market.csgo.com and an admin CRM.\n\n\t1\t3\t4\nIlusion9/csgo-fix-mapchange-crash-sm\n\nFix players crash on map change.\n\n\t1\t3\t4\nismail0234/Benson-Map-Crash-Fixer\n\nCSGO Map Change Client Crash Fixer\n\n\t1\t3\t4\njaxwilko/steam-market-api\n\nPHP - Composer Compatible - Steam Market API\n\n\t2\t2\t4\nJustArchiNET/ArchiTag\n\nArchiTag is a very small utility based on Python 3 and Mutagen to provide missing functionality in opusenc of writing specific Opus metadata, such as total number of tracks or track number.\n\n\t1\t3\t4\nModDota/DotaUI\n\nNo description in the capture.\n\n\t2\t2\t4\nnode-steam/market-pricing\n\nWrapper for the unofficial Steam Market Pricing API\n\n\t1\t3\t4\nodota/media\n\nStores media files for Dota projects\n\n\t2\t2\t4\nSergeyIvanovDevelop/Crypto-Steam-Platform\n\nThe repository contains the code and configuration to run a platform for creating cryptocurrency stakes for arbitrary ERC20 tokens.\n\n\t1\t3\t4\nAareksio/csgodouble-floatchecker\n\nAdds context menu option to check item's float value\n\n\t1\t2\t3\nchinm4/CSGOdrop\n\nA online csgo gambling casino that includes a variety of mini games that allows you to win csgo skins\n\n\t2\t1\t3\nCruze03/CSGO-Case-Opening-Prank\n\nCommand:- !prank (Admin flag \"n\" required)\n\n\t1\t2\t3\nDhruva-Kapadia/CSGOTrollGG\n\nCSGO Case Opening Simulator\n\n\t2\t1\t3\nErhanCSGO/CSGOPolygon-prediction\n\nCSGOPolygon.com - prediction script, double your coins by using this tool\n\n\t1\t2\t3\nEv-Hoang/Bedrock-Chest-Case-Opening\n\nHypixel Skyblock Dungeon Mod - Bedrock Chest Opening Animation (CSGO Style)\n\n\t1\t2\t3\njmjp/csgo-roulette\n\nA csgo gambling roulette make with VueJS 3\n\n\t2\t1\t3\nJustArchiNET/ArchiCrowdin\n\nNo description in the capture.\n\n\t1\t2\t3\nLeonSK/WearMarketInspector\n\nRetrieve Wear Value (Float Value) and Pattern Index from Steam Community Market using http://csgo.exchange API\n\n\t1\t2\t3\nmaximgeerinck/csgo-gamble\n\nCSGO gambling website\n\n\t1\t2\t3\nModDota/BugTracker\n\nListing bugs for Dota 2 Custom Games\n\n\t2\t1\t3\nplwp/mma-betting\n\nUFC/MMA betting model with Pinnacle steam detection for AU book latency arb\n\n\t2\t1\t3\nSouthsideswag16/Csgo-Gambling-Site\n\nNo description in the capture.\n\n\t2\t1\t3\ntacyarg/csgofiesta-frontend-react\n\nRemastered version a the long time favorite csgo site\n\n\t2\t1\t3\nVelorasse/Mutah-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-csmoney-csgoskins\n\ngambling script for Mutah, Keydrop, csmoney, and csgoskins, featuring hacks, cheats, and predictors. Offers strategies to boost winning odds and optimize performance on these platforms.\n\n\t3\t0\t3\nalliedmodders/am-github-artifact-webhook\n\nNo description in the capture.\n\n\t2\t0\t2\ncharamza/roulette\n\nCSGO like roulette in JS\n\n\t1\t1\t2\nCruze03/CSGO-PugSetup-RoundRestore\n\nSometimes (player dropped/crashed) which would be disadvantage for a team. It would be very handy to restore the match to the previous round.\n\n\t1\t1\t2\ncsgorol/CSGO-ROLL-Crash-Predictor\n\nCSGO-ROLL-Crash-Predictor\n\n\t1\t1\t2\nFoxSerito/FOXWORLD_plugin_DoubleJump_CSGO\n\nПлагин SourceMod (CSGO). Двойной прыжок с эффектом.\n\n\t1\t1\t2\nhkehayovmoonbiz/CS2-Casino-Full-Source-Code\n\nCS2, CS2 betting platforms, Skin Roulette, Case Unboxing, Crash games, Jackpot, purchase CS2 casino source, crypto gambling\n\n\t1\t1\t2\nJustZakary/steamstoreapi\n\nThis NPM module is a API wrapper that makes the steam unofficial API easier to use.\n\n\t2\t0\t2\njzimr/steam-market-api\n\nA java library to easily get Steam Community Market data\n\n\t1\t1\t2\nMomohime/CSGO.Network-Jackpot-Coinflip\n\nNo description in the capture.\n\n\t1\t1\t2\nnnjjswat/moneybot\n\nautomated bots for bustabit (formerly known as moneypot), csgo crash, etc\n\n\t0\t2\t2\nodota/carry\n\nLegacy Application for donations to the OpenDota project\n\n\t1\t1\t2\nodota/PublicMatchDataBot\n\nA Discord bot to remind users to turn on Expose Public Match Data in the Dota 2 client\n\n\t1\t1\t2\nOrillio/CSGOBet.com\n\nCSGO roulette web app\n\n\t2\t0\t2\nripexz/csgo-bet-alert\n\nA Chrome extension to keep track of active CS:GO Lounge matches.\n\n\t1\t1\t2\nrrpvm/lumen_sense-beta-deprecated-\n\nthis is internal csgo cheat written by me(no paste, self reverse structures). start : ~6 August 2020, end : ~ 14 December 2020\n\n\t1\t1\t2\nRuthless222/csgoscore\n\nThis is a Counter Strike Global Offensive Betting Site. You chose the skins you want to bet and try to win jackpots\n\n\t2\t0\t2\ntfburns/CSGO-cases-PL\n\nExpected profit-loss of CS:GO case openings\n\n\t1\t1\t2\nTomDra/CSGO-Case-Data-Analysis\n\nWorks out the most profitable CS:GO case at that current time\n\n\t1\t1\t2\nValvePython/dota2-wrappers\n\nNo description in the capture.\n\n\t1\t1\t2\nValvePython/teamfortress2-closed-captions\n\nThis project aims to provide a set of closed captions for Team Fortress 2\n\n\t1\t1\t2\nVistaNetGTX/Cstrike.bet-\n\nCSGO Roulette Website Angular frontend, nodejs backend, and steam trading bots\n\n\t1\t1\t2\nwafflas/csgo-case-opening-simulator\n\nI created a cs go case opening simulator for a meme coin\n\n\t0\t2\t2\nAdmiral-Enigma/Le_Coinflip\n\nConflip game\n\n\t1\t0\t1\nadryeljuliao/roulette-csgo\n\nNo description in the capture.\n\n\t1\t0\t1\nAndreuTheG/csgo-coinflip-web\n\nCSGO Gambling Coinflip Website\n\n\t1\t0\t1\nasmilen/csgoDouble\n\na b c\n\n\t1\t0\t1\nb1naryth1ef/csgofort\n\nA CSGO portal for trading, betting, analytics, and more!\n\n\t1\t0\t1\nBaterka/PrivateSteamBettingWebsite2024\n\nPrivate Steam (Counter-Strike 2) betting/gambling website - Roulette, Jackpot\n\n\t1\t0\t1\nblackcaer/SteamTradeHandler\n\nAutomation of Steam trading. Helper project for bet automation.\n\n\t1\t0\t1\nBTheCoderr/theRounders\n\nThe Rounders - A professional-grade sports betting analytics platform combining real-time odds tracking, sharp movement detection, and advanced statistical analysis. Features include line shopping, steam move alerts, power rankings, and comprehensive bet t…\n\n\t1\t0\t1\nCallumHemsley/KazeBot\n\nA Twitch chat betting bot for CSGO, simply bet a certain amount of points, and double if you win, lose all if you lose. Simple.\n\n\t1\t0\t1\nchrisjpm/CSGOJackpotTemplate\n\nFront end for a jackpot site\n\n\t1\t0\t1\ncolinsenner/valve-bug-bounty\n\nFor many years CS:GO, Dota 2, and Team Fortress 2 servers had a bug that allowed malicious users to leak crucial server process memory or reliably crash any server.\n\n\t1\t0\t1\ncoryypeters/nrl-odds-intelligence-pipeline\n\nReal-time sports betting odds intelligence — streaming pipeline that detects line movement, steam, and arbitrage across bookmakers. Python · Redis Streams · FastAPI · React.\n\n\t1\t0\t1\ndeissh/dev-csgoduo\n\nCS:GO. Bot for receiving things on the site (Polygon, Duo, Double and etc).\n\n\t1\t0\t1\ndom1torii/even-better-font-manager\n\nSimply even better cross-platform tool for CS2 Font Management\n\n\t1\t0\t1\nDONnicov/CSGO-crash-black-screen-\n\nsolution csgo crash black screen and close csgo\n\n\t1\t0\t1\nDoubleBoters/CsgoDouble\n\nNo description in the capture.\n\n\t1\t0\t1\ndownarowiczd/DoubleBot\n\nAn old CSGO Double Bot written for my friend. - 07.05.2016\n\n\t1\t0\t1\nErayBahar/steammarketscraper\n\nSteam Market Scraper Python-based tool that tracks real-time CS2 skin prices using Steam's hidden API. It fetches the lowest sell and highest buy offers for any item, helping you monitor deals or snipe underpriced listings automatically.\n\n\t1\t0\t1\nfairydarkness/SteamwebmailAPI\n\nUnofficial Python API for steamwebmail.com Fast, lightweight, and browserless library for automating steamwebmail.com. Support for session management, proxy, folder navigation, and message retrieval\n\n\t1\t0\t1\nFAQU2/CSGO-Coinflip-MyJailShop\n\nSourcemod plugin which provides a Coinflip system for MyJailShop.\n\n\t1\t0\t1\nFlamesONE/csgo-case-opening\n\nNo description in the capture.\n\n\t1\t0\t1\nFunnyRain/csgorun-crash-watch\n\n🚀 CsgoRun dump crash. / 🚀 CsgoRun дамп крашей.\n\n\t1\t0\t1\ngeohdgio/Venatus-Autenticator\n\nეს არის Steam Autenticator ქართული Venatus Trade & Betting ისთვის და Valve News Georgia-სთვის.\n\n\t1\t0\t1\nhakanstarlord/steam-bot\n\nSports betting steam-move signal detection with ML pipeline (XGBoost stacking + isotonic calibration), backtesting engine, Flask dashboard, and Telegram alerts.\n\n\t1\t0\t1\nHvH-gg/CSGO-Item-CrashFix\n\nA plugin for Counter-Strike: Global Offensive that fixes an exploit where receiving CS2 Items will cause CS:GO clients to crash\n\n\t1\t0\t1\nHvH-gg/CSGO-NetMsg-CrashFix\n\nA plugin for Counter-Strike: Global Offensive that fixes an exploit where spamming NetMsg_StringCmd packets would result in a server crash.\n\n\t1\t0\t1\nisybycnsmam/SteamLibrary\n\nLegacy Steam Unofficial API\n\n\t1\t0\t1\nItsTangerine/SteamApis.Net\n\nUnofficial https://steamapis.com .NET library, supporting .NET 6.0+\n\n\t1\t0\t1\nJustArchiNET/JustArchi.net\n\nNo description in the capture.\n\n\t1\t0\t1\nkiri-osint/CS2-Info-Hub-Bot\n\nA Telegram bot that acts as a hub for CS2 players, providing real-time skin prices, server stats, and user profile/inventory inspection using official and unofficial Steam APIs.\n\n\t1\t0\t1\nKoshkaj/monte\n\nGamified csgo gambling platform implementation\n\n\t1\t0\t1\nmadsab/CaseOpening\n\nA school project using Java. Simulating the case opening from CSGO and more.\n\n\t1\t0\t1\nman90es/steamcardexchange-api\n\nSteamCardExchange.net unofficial REST API server (scraper).\n\n\t1\t0\t1\nMattPua/steam-unofficial-docs\n\nUnofficial docs for Steam APIs with fumadocs\n\n\t1\t0\t1\nMetallist1/Portfolio.CsgoWinGambleProject\n\nA website that was done in 2017 September. Websites focus was on gambling with Counter-Strike items. Project was largely completed however backups were not done correctly, this resulted in half a year of wasted improvements to the code. The website was test…\n\n\t1\t0\t1\nmikebobadilla/csgo-jackpot\n\nNo description in the capture.\n\n\t0\t1\t1\nmikebobadilla/meteor-csgojackpot\n\nCssgo Jackpot done in meteor\n\n\t1\t0\t1\nModDota/D2VDump\n\nDota 2 Server VScript API Dumper\n\n\t1\t0\t1\nModDota/DotaTracking\n\nNo description in the capture.\n\n\t1\t0\t1\nModDota/eslint-config\n\nESLint config by ark120202\n\n\t1\t0\t1\nmr-codinglv/Casino-script\n\nscript casino - script betting - exchange script - bc casino - casino csgo - script bet - betwin script\n\n\t1\t0\t1\nMrKeelik/MrKeel\n\nCSGO DOUBLE BOT\n\n\t1\t0\t1\nnoahlatzel/CSGORollHelper\n\nLeveraging positive expected value on triple green jackpots on CSGORoll!\n\n\t1\t0\t1\noddsgpt/oddsgpt-market-intelligence\n\nResearch on football betting markets, closing odds, CLV, market efficiency, steam moves, AI betting systems, and sports market intelligence.\n\n\t1\t0\t1\noEXU/csgo-server-crasher\n\nCSGO SERVER CRASHER\n\n\t1\t0\t1\nPrdTTony/CSGO-Roulette\n\n[CSGO] Roulette System. Bet on RED or Black and win x2 credits\n\n\t1\t0\t1\nr-adamski/csgo-jackpot\n\nNo description in the capture.\n\n\t1\t0\t1\nSahotallo/Turan-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-Skinbaron-hellcase\n\ngambling script for Turan, Keydrop, Skinbaron, and Hellcase, providing hacks, cheats, and predictors. Includes strategies to improve winning chances and enhance gameplay on these platforms.\n\n\t1\t0\t1\nsamuelcsouza/steam-marketplace-api\n\nAn unofficial API to get data from the Steam Marketplace.\n\n\t1\t0\t1\nSKINSTRACK/CS2-Price-API\n\nSkinstrack offers a free, limited API endpoint that returns Steam item prices. Paid plans additionally provide access to pricing data from multiple marketplaces, making it possible to compare prices across different markets through a single API.\n\n\t1\t0\t1\nsnmtriet/CSGO-Casino-Full-Source-Code\n\nCSGO, CSGOEmpire, Case Opening, Case Battles, Roulette, Coinflip, buy csgo gambling site, gambling\n\n\t1\t0\t1\nSteamRE/homebrew-tools\n\nRepository for installation of SteamRE tools via Homebrew (http://brew.sh)\n\n\t1\t0\t1\nSteamRE/opensteamworks.org\n\nNo description in the capture.\n\n\t1\t0\t1\nTheQuack45/CsgoCaseOpenProgram\n\nSimple program to parse an XML file with CS:GO case information and \"simulate\" case openings\n\n\t1\t0\t1\nTLClassless/StratRouletteCSGO\n\nA 'Strat Roulette' web app for CS:GO!\n\n\t1\t0\t1\ntomasoom/csgoCaseOpening\n\nNo description in the capture.\n\n\t1\t0\t1\nvitaliy-evsyukov/steamgifts-autobet-bookmarklet\n\nbookmarklet for automatic bets on steamgifts.com\n\n\t1\t0\t1\nXpravdaX/RouletteCSGO\n\nNo description in the capture.\n\n\t1\t0\t1\nYuiKasumii/steam_api_unofficial\n\nUnofficial Steam Game Information Database\n\n\t1\t0\t1\nZexuz/Steam-Betting\n\nA betting website build ontop of STEAM's ecosystem\n\n\t1\t0\t1\nANK-RULZZ/steam-jackpot-site\n\ngetting some errors and would like some one to help me with it thank you!!!\n\n\t0\t0\t0\nasmilen/CsgoDoubleVS\n\nNo description in the capture.\n\n\t0\t0\t0\nCORNOODOSADAS/CSGOWeed\n\nCsgo Jackpot and Coinflip\n\n\t0\t0\t0\nCSGOApple/csgoapple\n\nJackpot Site\n\n\t0\t0\t0\nCSGOFAST/csgofast-api\n\nNo description in the capture.\n\n\t0\t0\t0\nDonakall/csgoDoublebot\n\nAutomated bot for csgodouble\n\n\t0\t0\t0\nfedor-selivanov/csgo-fast-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nfoldageros/csgod\n\ndouble bot\n\n\t0\t0\t0\ngmod-gambling/gmod-gambling\n\nNo description in the capture.\n\n\t0\t0\t0\nierome/CSGOBoss-BackEnd\n\nBack end version of CSGOBoss. This was a CSGO Gambling site named CSGOBoss. Coded by an old friend of mine Dahquan Hinds (https://github.com/dahquan/) Thought I would release this to help out any one who would need it.\n\n\t0\t0\t0\njamienp1/CSGODOUBLE-BOT-AUTO\n\ni got a bot thats is betting on the last winning color except from green and if you lose it will double the coins you set it to bet, pretty good, so when there comes a loooong train you will be gaining a bit of money codepaste_net/ugmt92 remove all the _ an…\n\n\t0\t0\t0\nJEYONER/CSGOTOXIC\n\nPAGINA DE JACKPOT CSGO SKINS\n\n\t0\t0\t0\nkalrish/csgo-jackpot\n\nStressful but funny zombie-like Counter-Strike: Global Offensive game mode.\n\n\t0\t0\t0\nkrys12345/roulettee\n\n// ==UserScript== // @name CSGO Predict Bot // @namespace http://csgodouble.com // @version 1.0 // @description predicts what number its gonna be // @author Meee // @match http://www.csgodouble.com/ // @grant none // ==/…\n\n\t0\t0\t0\nLilDuggiMuffi/CSGODouble-Working-Bot\n\nFixed CSGO Double Bot\n\n\t0\t0\t0\nLyricLy/Steam2Proton\n\nCheck if all your Steam games will work with Proton! Uses the official Steam API and the unofficial Proton API.\n\n\t0\t0\t0\nM0NsTeR77/csgo-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nozanhalis/Hi\n\n// ==UserScript== // @name CS GO LOUNGE BOT-Ozan Halis // @namespace http://csgolounge.com/ // @version 0.6.6 // @description Cs Go Lounge Hızlı BOT // @match http://csgolounge.com/* // @match http://dota2lounge.com/* // @updateURL h…\n\n\t0\t0\t0\nscoobertus/CSGO-DoubleBot\n\nNo description in the capture.\n\n\t0\t0\t0\nTradeal/CSGO-Jackpot-Bot\n\nNo description in the capture.\n\n\t0\t0\t0\nValvePython/artifact\n\nNo description in the capture.\n\n\t0\t0\t0\nVampire/CSGO-Roulette-Bot\n\nNo description in the capture.\n\n\t0\t0\t0\nvdemans/csgo-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nVocoreVideo/CSGODungeon-\n\nCSGO Jackpot\n\n\t0\t0\t0\nwayz-dev/csgofloat\n\nNo description in the capture.\n\n\t0\t0\t0\n\nSnapshot: 17 September 2026, 11:19:11 wie in der Quelle angegeben; Zeitzone nicht angegeben. Die Sammlung der Beziehungen ist im Export begrenzt (viele Kategorien enden bei „40“). Die Summe der Mitwirkenden und Forker ergibt 4,554 Rolleneinträge über 4,214 verschiedene Profil-Repository-Paare; ein Profil kann beide Rollen innehaben. Null bedeutet, dass in dieser Kategorie keine Datensätze erfasst wurden. Repository-Namen können Aliase oder Varianten in der Groß- und Kleinschreibung enthalten; bei den Gesamtzahlen werden die Zählkonventionen der Quelle beibehalten.\n\nHerkunft der Quelle\nAus Ihren gesammelten Dateien erstellt.\nUnterstützungsaussage\n2323/reddit_scams_ultra/steam_support_tickets_MEGA.json · Zeilen 45, 58, 107, 110, 294\nNetzwerk-Snapshot\nnetwork-repositories.csv · raw_data.json · overlaps.csv · summary.txt (historische Quellpfade im Manifest beibehalten)\n\nDas Manifest enthält Quellpfade, Bytegrößen, SHA-256-Hashes und ausgewählte Datensatzpositionen. Die Rohdaten werden getrennt von den Auswertungsergebnissen der Untersuchung aufbewahrt.\n\nQuellmanifest herunterladen ↓",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam Nachweise zur Durchsetzung – Belege und Entwicklernetzwerk"
          },
          {
            "level": 2,
            "id": null,
            "text": "Lesen Sie die Beschwerde.Fügen Sie die Quelle bitte bei."
          },
          {
            "level": 3,
            "id": null,
            "text": "Permanent sanction & closed appeals"
          },
          {
            "level": 4,
            "id": null,
            "text": "Permanently banned Steam account without a clear explanation, need help!"
          },
          {
            "level": 3,
            "id": null,
            "text": "Account recovery & a reported $10,000 loss"
          },
          {
            "level": 4,
            "id": null,
            "text": "Got $10k stollen from steam inventory due to steam' support fault."
          },
          {
            "level": 3,
            "id": null,
            "text": "A reported $500+ loss & template replies"
          },
          {
            "level": 4,
            "id": null,
            "text": "Funds stolen through steam market. Disappointed with Steam response.(or lackthereof)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam Guard & an item-restoration refusal"
          },
          {
            "level": 4,
            "id": null,
            "text": "Many people are losing item via clicking links where steam guard is enabled and steam support doesn't not restore items."
          },
          {
            "level": 3,
            "id": null,
            "text": "Selective enforcement & an unexplained ban"
          },
          {
            "level": 4,
            "id": null,
            "text": "🚨 Steam Bans Without Reason and Ignores Its Community — What’s Going On?"
          },
          {
            "level": 2,
            "id": null,
            "text": "Öffentliche Infrastruktur.In großem Maßstab aufgezeichnet."
          },
          {
            "level": 2,
            "id": null,
            "text": "Aus Ihren gesammelten Dateien erstellt."
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/de/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/de/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/selected-support-records.json",
          "https://phishdestroy.io/steam_dossier/de/investigation_part2.html#outsourcing-case",
          "https://www.reddit.com/r/ohnePixel/comments/1hahqx2/permanently_banned_steam_account_without_a_clear/",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://www.reddit.com/r/DotA2/comments/r55bd7/many_people_are_losing_item_via_clicking_links/",
          "https://www.reddit.com/r/SteamUncensored/comments/1kjt2fa/steam_bans_without_reason_and_ignores_its/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/network-repositories.csv",
          "https://github.com/alliedmodders/amxmodx",
          "https://github.com/alliedmodders/sourcemod",
          "https://github.com/DoctorMcKay/node-steam-user",
          "https://github.com/Facepunch/Facepunch.Steamworks",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://github.com/odota/core",
          "https://github.com/odota/dotaconstants",
          "https://github.com/odota/web",
          "https://github.com/splewis/get5",
          "https://github.com/SteamDatabase/FileDetectionRuleSets",
          "https://github.com/SteamRE/SteamKit",
          "https://github.com/ValveSoftware/dxvk",
          "https://github.com/ValveSoftware/GameNetworkingSockets",
          "https://github.com/ValveSoftware/gamescope",
          "https://github.com/ValveSoftware/Proton",
          "https://github.com/ValveSoftware/source-sdk-2013",
          "https://github.com/ValveSoftware/wine",
          "https://github.com/ValveSoftware/steam-devices",
          "https://github.com/ValveSoftware/steam-audio",
          "https://github.com/alliedmodders/metamod-source",
          "https://github.com/alliedmodders/sourcepawn",
          "https://github.com/ValveSoftware/Fossilize",
          "https://github.com/rlabrecque/Steamworks.NET",
          "https://github.com/ModDota/moddota.github.io",
          "https://github.com/odota/parser",
          "https://github.com/ValveSoftware/steam-for-linux",
          "https://github.com/SteamRE/DepotDownloader",
          "https://github.com/JustArchiNET/ASF-ui",
          "https://github.com/advancedfx/advancedfx",
          "https://github.com/alliedmodders/ambuild",
          "https://github.com/SteamDatabase/BrowserExtension",
          "https://github.com/odota/mobile",
          "https://github.com/ValvePython/steam",
          "https://github.com/skadistats/clarity",
          "https://github.com/SteamRE/open-steamworks",
          "https://github.com/ValveSoftware/Source-1-Games",
          "https://github.com/alliedmodders/hl2sdk",
          "https://github.com/SteamDatabase/steamdb.info-issues",
          "https://github.com/CSGOFloat/inspect",
          "https://github.com/ValveSoftware/SteamOS",
          "https://github.com/alliedmodders/source2mod",
          "https://github.com/smiley/steamapi",
          "https://github.com/SteamDatabase/GameTracking",
          "https://github.com/ValveSoftware/counter-strike_rules_and_regs",
          "https://github.com/ValveSoftware/openvr",
          "https://github.com/SteamDatabase/easy-markdown-editor",
          "https://github.com/ValveSoftware/Dota-2",
          "https://github.com/ValveSoftware/Dota2-Gameplay",
          "https://github.com/JustArchiNET/ArchiBot",
          "https://github.com/ztizzlegaming/CSGOWinBig",
          "https://github.com/JustArchiNET/mantis.justarchi.net",
          "https://github.com/odota/node-steam-user",
          "https://github.com/ModDota/TypeScriptAddonTemplate",
          "https://github.com/ValvePython/vdf",
          "https://github.com/alliedmodders/amtl",
          "https://github.com/ValvePython/dota2",
          "https://github.com/alliedmodders/stripper-source",
          "https://github.com/Allyans3/steam-market-api-v2",
          "https://github.com/ModDota/dota-tutorial",
          "https://github.com/odota/blog",
          "https://github.com/OpsecGuy/BetterGo",
          "https://github.com/pxvr-official/1",
          "https://github.com/Revadike/InternalSteamWebAPI",
          "https://github.com/JoeSzymkowiczFiveM/qb-lootcrate",
          "https://github.com/AbrarKL/MyRoulette.XYZ",
          "https://github.com/JustArchiNET/ASF-WebConfigGenerator",
          "https://github.com/ModDota/dota-data",
          "https://github.com/ModDota/TypeScriptDeclarations",
          "https://github.com/ModDota/API",
          "https://github.com/alliedmodders/cssdm",
          "https://github.com/SteamDatabase/steamstat.us",
          "https://github.com/c0deina/csgojackpotV2",
          "https://github.com/ValvePython/steamctl",
          "https://github.com/ValvePython/csgo",
          "https://github.com/BeepIsla/csgo-crash-exploit",
          "https://github.com/ValvePython/vpk",
          "https://github.com/alliedmodders/SM-SteamWorks",
          "https://github.com/SteamRE/Steam4NET",
          "https://github.com/alliedmodders/hl2sdk-manifests",
          "https://github.com/JustArchiNET/ASF-PluginTemplate",
          "https://github.com/ModDota/Dota2AIFramework",
          "https://github.com/Shkyyl/KeyChamp",
          "https://github.com/SteamDatabase/SteamMonitor",
          "https://github.com/Baterka/cslore.com",
          "https://github.com/SteamDatabase/SteamTokenDumper",
          "https://github.com/monoblocker/roulette",
          "https://github.com/zsith/launcher.user.js",
          "https://github.com/LincolnIT/CSGODouble-bot-automated",
          "https://github.com/vladpuz/steam-market",
          "https://github.com/mcgrizzz/Cstrike.bet",
          "https://github.com/odota/underlords-web",
          "https://github.com/SteamDatabase/SteamToTwitter",
          "https://github.com/ModDota/AbilityLuaSpellLibrary",
          "https://github.com/alvinl/bitskins",
          "https://github.com/b1naryth1ef/steamy",
          "https://github.com/kratos1812/Case-Opening",
          "https://github.com/odota/docs",
          "https://github.com/SteamDatabase/steam-advanced-access-fetch-players",
          "https://github.com/TheRioMiner/CsgoBetterExternalRaytrace",
          "https://github.com/alliedmodders/hl2sdk-mock",
          "https://github.com/christophersu/PySteamMarket",
          "https://github.com/Extremelyd1/Strat-Roulette",
          "https://github.com/giovanni-orciuolo/double-sdk",
          "https://github.com/JustArchiNET/Madness",
          "https://github.com/ModDota/TypescriptPanoramaDeclarations",
          "https://github.com/odota/rapier",
          "https://github.com/Vozn1akHero/CSGOCaseOpeningSimulator",
          "https://github.com/autarc/steam-store",
          "https://github.com/BETTING-CODE/awesome-esports-sites",
          "https://github.com/jonteohr/Better-Warden",
          "https://github.com/Ludzikk/CSGO-Gambling-Site",
          "https://github.com/ModDota/find-steam-app",
          "https://github.com/mprey/csgocact.us",
          "https://github.com/nezu-cc/ServerCrasher",
          "https://github.com/odota/testfiles",
          "https://github.com/odota/underlordsconstants",
          "https://github.com/SnaBe/node-steam-market-fetcher",
          "https://github.com/SteamDatabase/.github",
          "https://github.com/wolfcon/RIP-HLTV-BET",
          "https://github.com/alliedmodders/blaster.net",
          "https://github.com/catears124/CS2-Price-API",
          "https://github.com/ialakey/caseforge",
          "https://github.com/Ilusion9/csgo-fix-mapchange-crash-sm",
          "https://github.com/ismail0234/Benson-Map-Crash-Fixer",
          "https://github.com/jaxwilko/steam-market-api",
          "https://github.com/JustArchiNET/ArchiTag",
          "https://github.com/ModDota/DotaUI",
          "https://github.com/node-steam/market-pricing",
          "https://github.com/odota/media",
          "https://github.com/SergeyIvanovDevelop/Crypto-Steam-Platform",
          "https://github.com/Aareksio/csgodouble-floatchecker",
          "https://github.com/chinm4/CSGOdrop",
          "https://github.com/Cruze03/CSGO-Case-Opening-Prank",
          "https://github.com/Dhruva-Kapadia/CSGOTrollGG",
          "https://github.com/ErhanCSGO/CSGOPolygon-prediction",
          "https://github.com/Ev-Hoang/Bedrock-Chest-Case-Opening",
          "https://github.com/jmjp/csgo-roulette",
          "https://github.com/JustArchiNET/ArchiCrowdin",
          "https://github.com/LeonSK/WearMarketInspector",
          "https://github.com/maximgeerinck/csgo-gamble",
          "https://github.com/ModDota/BugTracker",
          "https://github.com/plwp/mma-betting",
          "https://github.com/Southsideswag16/Csgo-Gambling-Site",
          "https://github.com/tacyarg/csgofiesta-frontend-react",
          "https://github.com/Velorasse/Mutah-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-csmoney-csgoskins",
          "https://github.com/alliedmodders/am-github-artifact-webhook",
          "https://github.com/charamza/roulette",
          "https://github.com/Cruze03/CSGO-PugSetup-RoundRestore",
          "https://github.com/csgorol/CSGO-ROLL-Crash-Predictor",
          "https://github.com/FoxSerito/FOXWORLD_plugin_DoubleJump_CSGO",
          "https://github.com/hkehayovmoonbiz/CS2-Casino-Full-Source-Code",
          "https://github.com/JustZakary/steamstoreapi",
          "https://github.com/jzimr/steam-market-api",
          "https://github.com/Momohime/CSGO.Network-Jackpot-Coinflip",
          "https://github.com/nnjjswat/moneybot",
          "https://github.com/odota/carry",
          "https://github.com/odota/PublicMatchDataBot",
          "https://github.com/Orillio/CSGOBet.com",
          "https://github.com/ripexz/csgo-bet-alert",
          "https://github.com/rrpvm/lumen_sense-beta-deprecated-",
          "https://github.com/Ruthless222/csgoscore",
          "https://github.com/tfburns/CSGO-cases-PL",
          "https://github.com/TomDra/CSGO-Case-Data-Analysis",
          "https://github.com/ValvePython/dota2-wrappers",
          "https://github.com/ValvePython/teamfortress2-closed-captions",
          "https://github.com/VistaNetGTX/Cstrike.bet-",
          "https://github.com/wafflas/csgo-case-opening-simulator",
          "https://github.com/Admiral-Enigma/Le_Coinflip",
          "https://github.com/adryeljuliao/roulette-csgo",
          "https://github.com/AndreuTheG/csgo-coinflip-web",
          "https://github.com/asmilen/csgoDouble",
          "https://github.com/b1naryth1ef/csgofort",
          "https://github.com/Baterka/PrivateSteamBettingWebsite2024",
          "https://github.com/blackcaer/SteamTradeHandler",
          "https://github.com/BTheCoderr/theRounders",
          "https://github.com/CallumHemsley/KazeBot",
          "https://github.com/chrisjpm/CSGOJackpotTemplate",
          "https://github.com/colinsenner/valve-bug-bounty",
          "https://github.com/coryypeters/nrl-odds-intelligence-pipeline",
          "https://github.com/deissh/dev-csgoduo",
          "https://github.com/dom1torii/even-better-font-manager",
          "https://github.com/DONnicov/CSGO-crash-black-screen-",
          "https://github.com/DoubleBoters/CsgoDouble",
          "https://github.com/downarowiczd/DoubleBot",
          "https://github.com/ErayBahar/steammarketscraper",
          "https://github.com/fairydarkness/SteamwebmailAPI",
          "https://github.com/FAQU2/CSGO-Coinflip-MyJailShop",
          "https://github.com/FlamesONE/csgo-case-opening",
          "https://github.com/FunnyRain/csgorun-crash-watch",
          "https://github.com/geohdgio/Venatus-Autenticator",
          "https://github.com/hakanstarlord/steam-bot",
          "https://github.com/HvH-gg/CSGO-Item-CrashFix",
          "https://github.com/HvH-gg/CSGO-NetMsg-CrashFix",
          "https://github.com/isybycnsmam/SteamLibrary",
          "https://github.com/ItsTangerine/SteamApis.Net",
          "https://github.com/JustArchiNET/JustArchi.net",
          "https://github.com/kiri-osint/CS2-Info-Hub-Bot",
          "https://github.com/Koshkaj/monte",
          "https://github.com/madsab/CaseOpening",
          "https://github.com/man90es/steamcardexchange-api",
          "https://github.com/MattPua/steam-unofficial-docs",
          "https://github.com/Metallist1/Portfolio.CsgoWinGambleProject",
          "https://github.com/mikebobadilla/csgo-jackpot",
          "https://github.com/mikebobadilla/meteor-csgojackpot",
          "https://github.com/ModDota/D2VDump",
          "https://github.com/ModDota/DotaTracking",
          "https://github.com/ModDota/eslint-config",
          "https://github.com/mr-codinglv/Casino-script",
          "https://github.com/MrKeelik/MrKeel",
          "https://github.com/noahlatzel/CSGORollHelper",
          "https://github.com/oddsgpt/oddsgpt-market-intelligence",
          "https://github.com/oEXU/csgo-server-crasher",
          "https://github.com/PrdTTony/CSGO-Roulette",
          "https://github.com/r-adamski/csgo-jackpot",
          "https://github.com/Sahotallo/Turan-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-Skinbaron-hellcase",
          "https://github.com/samuelcsouza/steam-marketplace-api",
          "https://github.com/SKINSTRACK/CS2-Price-API",
          "https://github.com/snmtriet/CSGO-Casino-Full-Source-Code",
          "https://github.com/SteamRE/homebrew-tools",
          "https://github.com/SteamRE/opensteamworks.org",
          "https://github.com/TheQuack45/CsgoCaseOpenProgram",
          "https://github.com/TLClassless/StratRouletteCSGO",
          "https://github.com/tomasoom/csgoCaseOpening",
          "https://github.com/vitaliy-evsyukov/steamgifts-autobet-bookmarklet",
          "https://github.com/XpravdaX/RouletteCSGO",
          "https://github.com/YuiKasumii/steam_api_unofficial",
          "https://github.com/Zexuz/Steam-Betting",
          "https://github.com/ANK-RULZZ/steam-jackpot-site",
          "https://github.com/asmilen/CsgoDoubleVS",
          "https://github.com/CORNOODOSADAS/CSGOWeed",
          "https://github.com/CSGOApple/csgoapple",
          "https://github.com/CSGOFAST/csgofast-api",
          "https://github.com/Donakall/csgoDoublebot",
          "https://github.com/fedor-selivanov/csgo-fast-roulette",
          "https://github.com/foldageros/csgod",
          "https://github.com/gmod-gambling/gmod-gambling",
          "https://github.com/ierome/CSGOBoss-BackEnd",
          "https://github.com/jamienp1/CSGODOUBLE-BOT-AUTO",
          "https://github.com/JEYONER/CSGOTOXIC",
          "https://github.com/kalrish/csgo-jackpot",
          "https://github.com/krys12345/roulettee",
          "https://github.com/LilDuggiMuffi/CSGODouble-Working-Bot",
          "https://github.com/LyricLy/Steam2Proton",
          "https://github.com/M0NsTeR77/csgo-roulette",
          "https://github.com/ozanhalis/Hi",
          "https://github.com/scoobertus/CSGO-DoubleBot",
          "https://github.com/Tradeal/CSGO-Jackpot-Bot",
          "https://github.com/ValvePython/artifact",
          "https://github.com/Vampire/CSGO-Roulette-Bot",
          "https://github.com/vdemans/csgo-roulette",
          "https://github.com/VocoreVideo/CSGODungeon-",
          "https://github.com/wayz-dev/csgofloat",
          "https://phishdestroy.io/steam_dossier/output_steam_network/raw_data.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/enforcement-source-manifest.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/de/steam_enforcement_evidence.content.json",
      "export_json_sha256": "7d8ec2be8b0f14c689a844f06db12431bac11fee21010db81f5d78d24a17d694"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "de/steam_evidence_archive.html",
      "language": "de",
      "title": "Quellen prüfen – Das Dossier „Steam“",
      "source_url": "https://phishdestroy.io/steam_dossier/de/steam_evidence_archive",
      "source_html_sha256": "9e079f1654cffb9d948e5fb728ec4afad607fb1788a943c8daea899fc5139efb",
      "exported_at": "2026-09-29T00:16:16.760Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "steam_evidence_archive.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/de/steam_evidence_archive.pdf?v=print-20260929-v5",
        "sha256": "67dd7fa51226bd59f4da1e3532ed3a52410e492cb03ce0652f9d651237f2cb0d",
        "bytes": 63927,
        "pages": 4
      },
      "integrity": {
        "signed_object": "steam_evidence_archive.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "steam_evidence_archive.content.json.asc",
        "digest_file": "steam_evidence_archive.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify steam_evidence_archive.content.json.asc steam_evidence_archive.content.json",
          "sha256sum -c steam_evidence_archive.content.json.sha256"
        ]
      },
      "content": {
        "text": "UNTERSUCHUNGSMATERIALIEN / QUELLENSAMMLUNG 002\nSteam Beweisarchiv – 16,319 – Originaldokumente\n\nJeder Anspruch. Zurück zum Ursprung.\n\nWAS DIESER ABSCHNITT BELEGT\n\nDieses forensische Archiv indexiert 16,319 Primärquellen-Datensätze – darunter Dokumentation der Valve Developer Community, öffentliche GitHub-Tickets, verifizierte Trustpilot-Beschwerden und archivierte Forenberichte – mit kryptografischen Hashes und Herkunftsprotokollen. Es bietet eine überprüfbare Beweisgrundlage, die wiederholbare Plattformschwachstellen, undokumentierte API-Abkündigungen und anhaltende Verbraucherbeschwerden bezüglich gekaperter Konten belegt.\n\n← Zurück zum Executive Briefing\n\nFinden Sie den Datensatz, der hinter einer Behauptung steht. Filtern Sie nach Quelle, öffnen Sie den Volltext und folgen Sie dem Original-Link. Quellzeilen können sich überschneiden; ein Datensatz ist kein bestätigter Vorfall.\n\nZurück zur Untersuchung ↗\n354TRUSTPILOT / QUELLZEILEN\n208REDDIT / QUELLZEILEN\n705GITHUB / QUELLCODEZEILEN\n15,302MASTER-CSV / QUELLZEILEN\n16,319 DATENSATZE — AUFGLIEDERUNG NACH PLATTFORMART\n\nWiki-Kategorie „Provenienz“ (7,620 records · 46.7%): Die Daten wurden aus der „Valve“-Entwickler-Community (developer.valvesoftware.com), der SteamDB-Dokumentation/FAQ sowie aus Wikis der Gaming-Community (Liquipedia CS/Dota und Fandom-Steam-Wikis) mittels automatisierter WARC-Snapshots und MediaWiki-Endpunkten (API) zwischen dem 2024 und dem 2026. extrahiert. Alle Einträge unter 7,620 sind vollständig in den Master-CSV-Export integriert (TOTAL_VALVE_SCANDALS_MASTER_DB.csv).\n\nWiki\n7,620\nReddit\n5,635\nGitHub\n2,395\nTrustpilot\n393\nWeb\n276\n9,116 von den Einträgen unter 16,319 (55.8%) enthalten Verweise auf Steam / Valve\n\nDieses durchsuchbare Archiv wurde auf der Grundlage von 2026-09-17 aus den oben aufgeführten Quell-Exporten. Der separate Master-Export „40,448-“, der an anderer Stelle in der Dokumentation verwendet wird, hat einen anderen Umfang. Siehe den Manifest erstellen für die Zahlenangaben dieses Archivs; Datensätze können sich überschneiden und stellen keine einzelnen Vorfälle dar.\n\nQUELLPLATTFORM\nQUELLENSAMMLUNG\nSteam / Valve-Erwähnungen\nTextabgleich oder „Valve“-RepositoryFehlender / entfernter Text\n16,569 Quellzeilen\n16,319 eindeutige Datensätze\n249 Doppelte Zeilen wurden zusammengeführt\n1 Zeile ausgeschlossen\nDie Originaldateien anzeigen ↘\n★TRUSTPILOT2015-10-16#1RATING 1/5\n\nSteam is the biggest PC gaming platform without a doubt. A power which could be abused but Steam for the most part doesn't. Overall a definite download for any moden digital age PC gamer. It mu... See more\n\nMA · 7 source copies\n★TRUSTPILOT2021-06-18#2RATING 1/5\n\nThey scam people for money, dont believe me? Read this Source: Steam Subscribers/User Agreement NO GUARANTEES TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, NEITHER VALVE NOR ITS AFFILIA... See more\n\nWF · 7 source copies\n★TRUSTPILOT2016-10-28#3RATING 1/5\n\nSupport on site is terrible. Refunds not happend yet, despite games not working. No help at all if key is bought outside their system, so as a customer you can bounce back and through betw... See more\n\nPE · 7 source copies\n★TRUSTPILOT2021-09-27#4RATING 1/5\n\nThey are an amazing company!! My boyfriend paid for and downloaded a game without realizing it wasn’t the version he wanted. When he reached out, they gave him a full refund and responded in the same... See more\n\nVH · 7 source copies\n★TRUSTPILOT2026-07-20#5RATING 1/5\n\nI’ve used Steam for years, but lately, their sales have really lost their edge. I was hoping to score some solid discounts, but many games still feel overpriced, even during sales. Plus, the support response times can be frustratingly slow when issues arise.\n\nCR\n★TRUSTPILOT2025-12-10#6RATING 1/5\n\nI new here , but all my firends had great experience with this platform . They can make money\n\nZeinab Nematollahi\n★TRUSTPILOT2025-11-18#7RATING 1/5TEXT UNAVAILABLE\n\nNo text was included in the source record.\n\nEM\n★TRUSTPILOT2025-10-21#8RATING 1/5\n\nusing steam for over a decade and i have no words how good the platform is. some friends recommended it to me back in 2015 when we wanted to play csgo together and since then im loggin on it on a daily basis to check new games\n\nTrustpilot\n★TRUSTPILOT2025-05-09#9RATING 1/5\n\nSupport are never able to help you and only able to redicrect you to public linkBreaking there own TOSNot able to provider a refundNot able to provide a safe place for gamingBase on the game you play you can get scam.\n\nSym Link · 7 source copies\n★TRUSTPILOT2025-05-09#10RATING 1/5TEXT UNAVAILABLE\n\nNo text was included in the source record.\n\nHearnius\n★TRUSTPILOT2024-12-30#11RATING 1/5\n\nThis company allowed a single phishing scammer 76561199443342045 in 100's of its user community chat rooms \"Steam Chat\" the whole week of Winter Sales, 12-23-2024 - 2025 to spam spaceintrader a scam phishing website.Don't support Valve & Steam that support sca…\n\nFR · 7 source copies\n★TRUSTPILOT2024-11-15#12RATING 1/5\n\nVery realiable! Ive never had an issue over the 11 years ive had steam.\n\nJM\nDer Build und seine Quelldateien\n\nDieses Archiv führt die doppelten Zeilen aus 249 zusammen und schließt eine Zeile aus den Eingaben unter 16,569 aus, sodass 16,319 eindeutige Datensätze verbleiben. Ein Datensatz kann ein Ereignis beschreiben, das bereits durch einen anderen Datensatz abgedeckt ist. Die Suche umfasst Titel, Autoren, Quellenangaben und angezeigte Auszüge; der vollständige gespeicherte Text wird bei jedem Datensatz geöffnet.\n\nVier Quelldateien herunterladen ↓Dateianzahl und SHA-256-Hashes ↗Ursprüngliches Build-Manifest ↗\n\nDas Paket enthält die wiederhergestellten Exporte, die mit der Zeilenanzahl des Builds und den drei aufgezeichneten JSON-Pfaden übereinstimmen. Beim ursprünglichen Build wurden weder Eingabe-Hashes noch ein Master-CSV-Pfad aufgezeichnet; das zugehörige Manifest dokumentiert die wiederhergestellten Dateien und den Vergleich mit dem veröffentlichten Index.\n\nTrustpilot · steam_support_reviews.json354 Zeilen · JSON-Export\nReddit · reddit_censored_forensics.json208 Zeilen · JSON-Export\nGitHub · valve_ignored_bugs.json705 Zeilen · JSON-Export; der Dateiname ist eine Sammlerbezeichnung\nMaster · TOTAL_VALVE_SCANDALS_MASTER_DB.csv15,302 Zeilen · CSV-Export zum Vergleich\nGerichtsakten · UNSEALED_EXHIBITS_AND_AML_DOSSIER.mdWolfire gegen „Valve“ – freigegebene E-Mails, Aussagen von Gabe Newell, „Oct2019“-AML-Geständnis\nMaster Facts · FACTS_AND_CITATIONS_DATABASE.md1,638 Einzelne, verifizierte Zitate aus den Bereichen Kartellrecht und Sicherheit auf 35\nSupport-Archiv · support_canned_refusals.html1,505 Ticket-Datensätze · 137 – gespeicherte Screenshots · Live-Sofortsuche\nDatensatzfelder, fehlender Text und sich überschneidende Exporte\n\nDaten, Bewertungen, Kategorien und Statusangaben entsprechen den Exportdaten der Quelle. Eine fehlende URL bleibt weiterhin fehlend. Die Kennzeichnungen „[entfernt]“ oder „[gelöscht]“ geben keinen Aufschluss darüber, wer einen Beitrag entfernt hat oder warum. Der Filter Steam / Valve basiert auf einer Textübereinstimmung und nicht auf einer Relevanzbewertung.\n\n„Exportieren“ gleicht Indexeinträge mit Auszügen ab; „Datensatz herunterladen“ enthält den vollständigen gespeicherten Text. Die separate 40,448-Zeilen-Master-CSV sowie 1,690-Zeile „GitHub“ im CSV-Format Entscheidend für diesen Build sind die Exporte insgesamt, nicht die Anzahl der Quellen.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam Beweisarchiv – 16,319 – Originaldokumente"
          },
          {
            "level": 2,
            "id": null,
            "text": "QUELLPLATTFORM"
          },
          {
            "level": 2,
            "id": null,
            "text": "Der Build und seine Quelldateien"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/de/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/de/",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/TOTAL_VALVE_SCANDALS_MASTER_DB.csv",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive_manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive-inputs.zip",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive-inputs-manifest.json",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/unsealed_legal_and_aml/UNSEALED_EXHIBITS_AND_AML_DOSSIER.md",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/forensic_facts_1000/FACTS_AND_CITATIONS_DATABASE.md",
          "https://phishdestroy.io/steam_dossier/de/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/github_valve_unpatched_bugs.csv"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/de/steam_evidence_archive.content.json",
      "export_json_sha256": "1766ed3886ccbc6708b452c0708e1557ad0754a421fe0fa7bf3049131b7d7d4c"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "de/support_canned_refusals.html",
      "language": "de",
      "title": "Steam Archiv für abgelehnte Unterstützungsanträge und Standardantworten – Das Dossier „Steam“",
      "source_url": "https://phishdestroy.io/steam_dossier/de/support_canned_refusals",
      "source_html_sha256": "237b924fc20c72645d910309814c94d1d0d997b9a1164a2e288d32df734abbdf",
      "exported_at": "2026-09-29T00:17:13.815Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "support_canned_refusals.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/de/support_canned_refusals.pdf?v=print-20260929-v5",
        "sha256": "ec2c825250eee5d0edcc156019e3c4c60b9bbda642c137e40afc18da5245ab37",
        "bytes": 61979,
        "pages": 2
      },
      "integrity": {
        "signed_object": "support_canned_refusals.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "support_canned_refusals.content.json.asc",
        "digest_file": "support_canned_refusals.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify support_canned_refusals.content.json.asc support_canned_refusals.content.json",
          "sha256sum -c support_canned_refusals.content.json.sha256"
        ]
      },
      "content": {
        "text": "WAS DIESER ABSCHNITT BELEGT\n\nDieses Repository dokumentiert unter 137 aufbewahrte Screenshots sowie unter 1,505 geprüfte Einsprüche von Betroffenen, in denen die automatisierte Bearbeitung von Support-Tickets durch Valve detailliert beschrieben wird. Es belegt, dass der Support von Steam bei Konten, die durch OpenID-Weiterleitung oder die unbefugte Generierung von API-Schlüsseln kompromittiert wurden, systematisch standardisierte Standardablehnungen ohne technische Untersuchung verwendet. Indem die Plattform die Wiederherstellung von Gegenständen oder die Offenlegung von Prüfpfaden kategorisch ablehnt, wälzt sie die volle Haftung für strukturelle Authentifizierungsmängel auf die Inhaber der kompromittierten Konten ab.\n\nAlle Screenshots sind von Dritten erstellte Aufnahmen. Das Urheberrecht und die Inhalte verbleiben bei den jeweiligen Autoren und Plattformen (Reddit-Nutzer, Autoren der „Steam“-Community, Trustpilot-Rezensenten, X und YouTube-Nutzer). Sie werden ausschließlich zu Identifikationszwecken und im Rahmen der Berichterstattung im öffentlichen Interesse wiedergegeben; es wird kein Eigentumsanspruch geltend gemacht. Jeder Screenshot enthält einen Link zur jeweiligen Originalquelle.\n\nFigures reported on the source page\nMeasure\tReported value\tScope\nDokumentierte Aufzeichnungen\t1505\tÜberprüfte Opferbeschwerden und Threads zu Strafzetteln\nGespeicherte Screenshots\t137\tHochauflösende Ticket-Scans werden lokal gespeichert\nWiederherstellungsrate\t0.0%\tIm Fall der Entführungen von Flugzeugen der „API“ wurde eine Wiederaufnahme des Verfahrens gewährt\nVorlagen duplizieren\t100%\tWiederverwendung von Skripten durch verschiedene Mitarbeiter (Ilya, Roger, Maverick)\nForensische Beweise: Die drei Grundpfeiler der Verweigerung der Unterstützung\nSÄULE 01 · ZULASSUNGAnlage R –014\nDas Roger-Geständnis: „API“-MitM-Angriff bestätigt\n\nIn der Ticket-Antwort Nr.1cp582i räumt der Steam-Supportmitarbeiter „Roger“ schriftlich ein, dass Angreifer legitime Transaktionen über API stornieren und diese innerhalb von Millisekunden durch Klon-Bots ersetzen, weigert sich jedoch, die Gegenstände wiederherzustellen, und rät dem Opfer, sich an einen „lokalen PC-Techniker“ zu wenden.\n\nSchriftliche Zulassung prüfen ↗\nSÄULE 02 · EskalationAnlage R –012\n7-Day-Trading: Halten – Untätigkeit\n\nEin Opfer gab während des „7-“-Fensters für den Handel die SteamID64 der Hacker-Konten an. Die Support-Mitarbeiter „Artem“ und „Ilya“ weigerten sich unter Berufung auf die Knappheit virtueller Gegenstände, die gestohlenen Gegenstände zu sperren, und schlossen das Ticket mit einer automatisierten Standardantwort ab.\n\nTranskript mit mehreren Mitarbeitern prüfen ↗\nSÄULE 03 · POLITIKAnlage R –002\nMarktknappheit im Zusammenhang mit Eigentumsrechten\n\nIn den offiziellen Richtlinien zur Wiederherstellung von Gegenständen von Valve heißt es ausdrücklich, dass Gegenstände nicht zurückgegeben werden, da ihre Wiederherstellung „die Knappheit verringern und die Wirtschaft aufblähen würde, was den Wert der Gegenstände auf dem Community-Markt mindern würde“.\n\nScreenshot der Richtlinie „Prüfen“ ↗\nHistorische Entstehung · 22 März 2018 an 2026\nAnhang H –003 · 8-Jahr ohne Patches – Angriffsfläche\nDie früheste dokumentierte Handelssubstitution (22 März 2018)\n\nGenau eine Woche, bevor „Valve“ seine umstrittene „7-“-Abkühlphase für den Tageshandel mit „Counter-Strike“-Gegenständen einführte, entdeckte die Handelsgemeinschaft die ersten Live-Fälle des Steam Web-API-Exploit zur Umleitung von Transaktionen. Angreifer haben Web-Sitzungen gekapert, um einen nicht autorisierten „API“-Schlüssel unter steamcommunity.com/dev/apikey ohne Bestätigung durch die FA per Mobil2, wodurch Bots in der Lage sind, Trades in Echtzeit zu stornieren und auszutauschen.\n\nWarnung der PSA vom März „2018“: „Die Betrüger können dieses Tauschangebot automatisch erkennen und werden es auf deinem Konto ablehnen, da sie deinen Schlüssel Steam API haben. Der Betrugsbot wird dir nun ein Tauschangebot für dieselben Skins senden … und du wirst keinen Unterschied bemerken!“\nHistorischer Lehrpfad\n22 März 2018: Erster dokumentierter Austausch vAPI\n2019: Der Support standardisiert die Abwehr von „Malware“\n2020: Skript „Hilfeanfrage schließen“ gesichert\n2022–2026: Automatisierung von BitB- und QR-Phishing\nDen ursprünglichen Reddit-Thread „2018“ öffnen ↗\nPrimary sources\n\n137 gallery cards refer to 78 distinct primary URLs. Images and repeated exhibit captions are omitted from this reading edition.\n\nFull visual archive and original captures",
        "headings": [
          {
            "level": 2,
            "id": null,
            "text": "Figures reported on the source page"
          },
          {
            "level": 2,
            "id": null,
            "text": "Forensische Beweise: Die drei Grundpfeiler der Verweigerung der Unterstützung"
          },
          {
            "level": 3,
            "id": null,
            "text": "Das Roger-Geständnis: „API“-MitM-Angriff bestätigt"
          },
          {
            "level": 3,
            "id": null,
            "text": "7-Day-Trading: Halten – Untätigkeit"
          },
          {
            "level": 3,
            "id": null,
            "text": "Marktknappheit im Zusammenhang mit Eigentumsrechten"
          },
          {
            "level": 3,
            "id": null,
            "text": "Die früheste dokumentierte Handelssubstitution (22 März 2018)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Primary sources"
          }
        ],
        "links": [
          "https://www.reddit.com/r/csgo/comments/1cp582i/i_got_api_scammed_what_do_i_do_now/",
          "https://www.reddit.com/r/DotA2/comments/1e5ovy4/my_account_was_hacked_and_steam_support_refuse/",
          "https://www.reddit.com/r/Steam/comments/3b2abd/steam_will_no_longer_restore_scammed_items_item/",
          "https://www.reddit.com/r/GlobalOffensiveTrade/comments/863tk1/psa_urgent_huge_scam_happening_read_here_how_to",
          "https://phishdestroy.io/steam_dossier/de/support_canned_refusals#gallery-grid"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/de/support_canned_refusals.content.json",
      "export_json_sha256": "a1228bc747773629254057f7140ba998c0794a361944569638cb684e652010c2"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "de/valve_scandals_registry.html",
      "language": "de",
      "title": "Valve Skandalregister – Das Dossier „Steam“",
      "source_url": "https://phishdestroy.io/steam_dossier/de/valve_scandals_registry",
      "source_html_sha256": "98a7348c6c16336b215dea0a5428633e9c6be81ca12f5c2f6f0eb30f21b76176",
      "exported_at": "2026-09-29T00:17:13.238Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "valve_scandals_registry.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/de/valve_scandals_registry.pdf?v=print-20260929-v5",
        "sha256": "d412e76abff0bcbe0334a748caf179cebf7a1e731ffea21495863eaf636bc009",
        "bytes": 63425,
        "pages": 6
      },
      "integrity": {
        "signed_object": "valve_scandals_registry.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "valve_scandals_registry.content.json.asc",
        "digest_file": "valve_scandals_registry.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify valve_scandals_registry.content.json.asc valve_scandals_registry.content.json",
          "sha256sum -c valve_scandals_registry.content.json.sha256"
        ]
      },
      "content": {
        "text": "Hauptarchiv für Skandale\nValve Skandal-Stammregister – 160 – Aus den Quellen stammende Vorfälle\nQUELLDATEN (ROHDATEN): 11,768\n\nGemeldet. Quelle angegeben. Noch offen.\n\nWAS DIESER ABSCHNITT BELEGT\n\nDiese Master-Datenbank fasst von „160“ unabhängig überprüfte Primärdaten zusammen, die detaillierte Angaben zu anhaltenden Plattformmängeln, gelöschten Community-Meldungen und ungelösten Problemen im Kundensupport im gesamten Ökosystem von „Valve“ enthalten. Anhand von verifizierten Streitfallmeldungen auf Trustpilot, archivierten Tickets zu Sicherheitsproblemen auf GitHub sowie behördlichen Verfahren werden wiederkehrende systemische Mängel bei der Kontowiederherstellung und der Beilegung von Kundenstreitigkeiten aufgezeigt.\n\n← Zurück zum Executive Briefing\n\n160 Gesammelte Einträge: eine Support-Maßnahme, die von den Nutzern bewertet wurde, Threads, die nicht mehr sichtbar sind, gemeldete und unbeachtete Plattformfehler sowie die Vorfälle, für die sich Valve bereits verantworten musste. Nichts davon ist unsere eigene Einschätzung – jede Zeile enthält den Verweis auf die ursprüngliche Quelle. Öffnen Sie einen Eintrag und lesen Sie ihn selbst.\n\nQuelldatensätze\n11,768\nIn allen Kategorien\nMängel der Plattform\n3,372\nVon der Community gemeldete Plattformfehler\nZensierte Threads\n109\nVon Moderatoren gelöschte Reddit-Beiträge\nSupport-Beschwerden\n471\nVerifizierte Trustpilot-Beschwerden\nDurchsetzbarkeit\nSperrung von Auth-Host-Domains\n\nDie Sperrung von OpenID-Authentifizierungshosts auf Domain-Ebene ist technisch einfach umzusetzen: Sobald eine Ressource von der Weiterleitung bei der Anmeldung unter Steam ausgeschlossen ist, können Drittanbieter-Domains, die als Authentifizierungsproxys für dieselbe Ressource fungieren, anhand desselben Regelsatzes gefiltert werden. Eine ausführliche Erörterung der Umsetzbarkeit findet sich im Hauptdossier.\n\nSiehe Durchsetzbarkeit im Dossier →\nKategorie: Trustpilot-Support-Beschwerden (gefilterte negative Eskalationen)176 übereinstimmende Quelldatensätze · Duplikate ausgeblendet\nConsumer Complaint2026-07-20\nAuthor: C***\n\nI’ve used Steam for years, but lately, their sales have really lost their edge. I was hoping to score some solid discounts, but many games still feel overpriced, even during sales. Plus, the support response times can be frustratingly slow when issues arise.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2026-07-20\nConsumer Complaint2025-05-09\nAuthor: S*** L***\n\nSupport are never able to help you and only able to redicrect you to public linkBreaking there own TOSNot able to provider a refundNot able to provide a safe place for gamingBase on the game you play you can get scam.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2025-05-09\nConsumer Complaint2024-12-30\nAuthor: F***\n\nThis company allowed a single phishing scammer 7656…2045 in 100's of its user community chat rooms \"Steam Chat\" the whole week of Winter Sales, 12-23-2024 - 2025 to spam spaceintrader a scam phishing website.Don't support Valve & Steam that support scams. Don't give your log in credentials to account hijacking scammers. This company also allows engagements of commercial advertising / spam for gambling in violation of its own Rules and Guidelines / Online Conduct. 7656…5023 proof - groups/deskinsfans key drop advertising, thanks TannerfromKD and Valve!*\"The Consumer Review Fairness Act (CRFA) protects people’s ability to share their honest opinions about a business’s products, services, or conduct, in any forum, including social media. The law protects a broad variety of honest consumer assessments, including online reviews, social media posts, uploaded photos, videos, etc. And it doesn’t just cover product reviews. It also applies to consumer evaluations of a company\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2024-12-30\nConsumer Complaint2024-07-31\nAuthor: A***\n\nhorrible company.randomly you get \"This account may have been accessed by someone else.\"this happened to me 3 times.the 3rd time they wanted a cd key.a spent useless cd key that nobody has any reason to keep laying around.i gave them the paypal bill for my first purchase back in 2015.i gave them a bill for my first phone number ever on the account.i still got the same email attached to the account.this company is literally a scam. nothing but a scam.they randomly claim you been accessed somewhere else and then require you to give them information no reasonable person would ever have, if not your done and have to rebuy everything.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2024-07-31\nConsumer Complaint2023-12-09\nAuthor: K***\n\nHad 288 euros in steam wallet, someone hacked my account even with two step verification, write a steam support for help but only answer was if something is spent in community market they can’t help.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2023-12-09\nConsumer Complaint2023-09-26\nAuthor: J***\n\nI was banned for saying \"Who let grandma on the PC\"and another for simply calling someone ignorant.Power tripping mods, devs who don't care, steam doesn't care. Yet allows racism/trolling/etc Fk steam, its a joke now.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2023-09-26\nConsumer Complaint2022-08-31\nAuthor: Anonymous\n\nSteam community is plain bad for a various reasons:1. Steam forums are a big mess, for example they allow users to post in any language and as result you get jumbled mess with posts in foreign languages together with English language posts. For example, If you check CS GO forums, you'll see half of posts are in Russian and half in English. I don't understand why such a big and international company would leave their forums so unorganized like that. All other normal companies have English only language allowed which is an international language and sometimes subforums for other languages like German, French and etc... so if French people want to post in French they go specifically in that sub-forum. But no, Steam doesn't care about this. Their forums is a one big mess.2. Moderation is biased and joke. I don't understand why such a big company like Steam can't afford to hire people for moderation and pay them. Instead they just recruit random people for moderation who do it for free and\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2022-08-31\nConsumer Complaint2022-05-28\nAuthor: J***\n\nThe login code never arrives. I hate Steam.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2022-05-28\nConsumer Complaint2021-11-08\nAuthor: N***\n\nThe service is terrible, I only signed up because I really like the game I wanted, but the rest is terrible, I hope to get something better soon.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-11-08\nConsumer Complaint2021-06-18\nAuthor: W***\n\nThey scam people for money, dont believe me? Read thisSource: Steam Subscribers/User Agreement NO GUARANTEESTO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, NEITHER VALVE NOR ITS AFFILIATES GUARANTEE CONTINUOUS, ERROR-FREE, VIRUS-FREE OR SECURE OPERATION AND ACCESS TO STEAM, THE CONTENT AND SERVICES, YOUR ACCOUNT AND/OR YOUR SUBSCRIPTION(S) OR ANY INFORMATION AVAILABLE IN CONNECTION THEREWITH.In short: You got a virus or your data leaked because of our software? Whoopsies we dont care, that isnt even legal or the last of their scammy stuff...\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-06-18\nConsumer Complaint2021-05-14\nAuthor: B***\n\nThe support is one of the worst I've ever seen.Useless support team.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-05-14\nConsumer Complaint2020-04-02\nAuthor: J***\n\nSteamcommunity has 15% fees, 15!!!!\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2020-04-02\nConsumer Complaint2020-03-27\nAuthor: H***\n\nWhat can I say? the support is one of the worst I've ever seen maybe the FUNCOM is much worse. If you tell the true on the steam forum you just got a BAN even if what you said did not violated the rules of the forum.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2020-03-27\nConsumer Complaint2018-03-16\nAuthor: B***\n\ndon't sign up will stick on your computer will kill your pc power you can't remove it from your pc even you deleted it will stay woking in the system\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2018-03-16\nConsumer Complaint2016-12-27\nAuthor: J***\n\nIn bloddy hate their page it's tiresome, it's in no way intuitive. I tried reaching out for support, but that is a maze.I'm simply trying to log in and redeem a key of a product I already bought, their search function is a joke. I f*u*c*k*i*n*g hate them. The layout is not like the how to video from the dealer, this can be done much simpler. I don't frigin care aboutn what other titles you have in store or what genre, I just want to redeem my key and install.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-12-27\nConsumer Complaint2016-10-28\nAuthor: P***\n\nSupport on site is terrible.Refunds not happend yet, despite games not working.No help at all if key is bought outside their system, so as a customer you can bounce back and through between bad support systems?? I wait for some other companies to compete in this market, for this can't be the best we as customers can expect.And do put an email up to find, instead of this stuppid website where you spend so long time trying to find a solution on, instead of a simple mail. Often the problem is not there, or if it's there just saying no help here???I need a response\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-10-28\nConsumer Complaint2016-06-26\nAuthor: V*** W***\n\nUseless support as always!\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-06-26\nConsumer Complaint2014-07-01\nAuthor: J***\n\nexpensive, and support team not willing to cooperate\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2014-07-01\nConsumer Complaint2014-04-15\nAuthor: B***\n\nWhen you pay for a program, you expect it too work. cant not buy or anything and have written to valve. but there is not a being done a damn thing abut it..\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2014-04-15\nConsumer Complaint2026-09-03\nAuthor: M***\n\nWorst platform ever wont give me a refund even though a game is unplayable because of bugs I won't ever be using the crap platform again I hope the platform breaks down for good piece fo crao\n\nTarget Domain: steamcommunity.com / steampowered.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2026-09-03\n\nKeine passenden Einträge\n\nVersuchen Sie, Ihre aktuelle Suchanfrage anzupassen oder eine andere Kategorie-Registerkarte auszuwählen.\n\n1 / 9",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Valve Skandal-Stammregister – 160 – Aus den Quellen stammende Vorfälle"
          },
          {
            "level": 2,
            "id": null,
            "text": "Sperrung von Auth-Host-Domains"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: C***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: S*** L***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: F***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: A***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: K***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: Anonymous"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: N***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: W***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: H***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: P***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: V*** W***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: M***"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/de/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/de/#autoban-feasibility-section",
          "https://www.trustpilot.com/review/steamcommunity.com"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/de/valve_scandals_registry.content.json",
      "export_json_sha256": "f90bf60ea792bbdc652b2b0c41aa32973d15ded348018f312dc4825049ec6d84"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "de/output_steam_network/index.html",
      "language": "de",
      "title": "Architektur statt Exploit: Das Automation Network – Das Dossier „Steam“",
      "source_url": "https://phishdestroy.io/steam_dossier/de/output_steam_network/index",
      "source_html_sha256": "f20de2a303bbfea489047e96dfdec9bcda81c3dbb9832e778322d79c1701cf14",
      "exported_at": "2026-09-29T00:17:16.035Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__index.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/de/output_steam_network__index.pdf?v=print-20260929-v5",
        "sha256": "3137b730e14048dbc70dcd86c12f7a25e38aec01b0cdcecb3c4350225f0462d5",
        "bytes": 68191,
        "pages": 3
      },
      "integrity": {
        "signed_object": "output_steam_network__index.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__index.content.json.asc",
        "digest_file": "output_steam_network__index.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__index.content.json.asc output_steam_network__index.content.json",
          "sha256sum -c output_steam_network__index.content.json.sha256"
        ]
      },
      "content": {
        "text": "Anhang VII · Analyse der technischen Architektur\nSteam Netzwerkarchitektur – Protokolltreue und Ökosystemanalyse\n\nAutomatisierung ist das Fundament vValve. Kein Exploit.\n\nWAS DIESER ABSCHNITT BELEGT\n\nDieses Modul bildet die technische Topologie der Entwickler-Repositorys unter 252, der Profile unter 3,320 und GitHub sowie der Mitwirkendenpaare unter 4,214 ab, die das Automatisierungsökosystem von Steam bilden. Es belegt, dass die Automatisierung durch Drittanbieter auf dem offiziellen Connection-Manager-Protokoll von Valve, Protobuf-Schemas und Web-APIs ohne Exploit-Code basiert. Durch die Entwicklung algorithmischer Steam-Guard-Bestätigungstoken und die Erhebung minimaler Transaktionsgebühren von bis zu 66.7%, Valve fungiert das Unternehmen als bewusster Architekt und Hauptnutznießer der automatisierten Ökosystembetriebe.\n\n← Zurück zum Executive Briefing\n\nWenn sich Valve an Aufsichtsbehörden, Zahlungsabwickler oder Betrugsopfer wendet, führt es den Diebstahl von Skin-Daten und Marktmanipulationen auf „unbefugte Angriffe durch Dritte“ und „illegale Automatisierung durch Kriminelle“ zurück. Die technische Realität dieses Repository-Netzwerks unter 252-belegt jedoch genau das Gegenteil: Jedes Automatisierungs-Framework, jeder Trading-Bot und jede Farming-Flotte arbeitet streng im Rahmen der offiziellen Protokolldefinitionen, Web-APIs und Authentifizierungsmechanismen, die von der Valve Corporation entwickelt, dokumentiert und kommerzialisiert wurden.\n\nForensischer Befund: Bewusste Architektur vs. unrechtmäßiger Zugriff\n\nDie in diesem Modul analysierte Software – darunter SteamKit, node-steam-user, ValvePython/steam, und ArchiSteamFarm — enthält keine Software-Sicherheitslücken, keine Speicherbeschädigungen und keine Zero-Day-Exploits. Es handelt sich um saubere, robuste Open-Source-Implementierungen des proprietären Connection-Manager-Client-Protokolls (CM) von „Valve“, von Google Protocol Buffers (Protobufs) sowie von Web-APIs. „Valve“ hat diese APIs für die programmatische Anmeldung entwickelt und „Steam Guard“ so konzipiert, dass algorithmische Bestätigungstoken (identity_secret) und erhebt eine in der Werbung angegebene Gebühr von 15%, die sich auf bis zu 66.7% zugunsten von Valve bei den Hochgeschwindigkeitskarten und den Massenwaren, die von automatisierten Botnetzen verwertet werden.\n\nSäule 01 · Protokolltreue\nOffizielle Protobuf-Schemas\n\nAutomatisierungsbibliotheken umgehen keine Sicherheitskontrollen. Sie serialisieren offizielle Protobuf-Nachrichten (steammessages_clientserver.proto) über TCP/WebSockets direkt an die offiziellen CM-Cluster von „Valve“, genau wie es der „Steam“-Client tut.\n\nPillar 02 · Algorithmic 2FA\nGenehmigung für den programmatischen Handel\n\nDie gesamte, mehrere Milliarden Dollar schwere Wirtschaft rund um den Handel mit Skins hängt von „Valve“ ab. IEconService API sowie TOTP-Schlüssel für mobile Authentifikatoren. Valve hat „Steam Guard“ gezielt entwickelt, um Handelsbestätigungen von Maschine zu Maschine zu ermöglichen.\n\nSäule 03 · Gewerbliche Begünstigte\nMonetarisierter Maschinen-Traffic: Bis zu 66.7% Mindestgebühr\n\nValve Es wird eine Gebühr von 15% beworben, doch bei den umsatzstarken Massenartikeln, mit denen automatisierte Bots handeln – Sammelkarten, Kartons und günstige Drops zu Preisen zwischen $0.03 und $0.05 – wird die Mindestgebühr von Valve in Höhe von zwei Cent ($0.01Steam + $0.01 publisher) erhoben. 50% an 66.7% zugunsten von Valve (2¢ werden von einer 3¢-Karte abgebucht, sodass dem Verkäufer 1¢ verbleiben). Hinzu kommen $5.00 pro Konto ($26.8M allein für die gescannte Flotte).\n\nModul „01“ · Nachweise zu Repositorien und Protokollen\nÖffentliche Entwickler- und Repository-Infrastruktur\n\nAusführlicher forensischer Katalog der Open-Source-Repositorys von „252“, die die Automatisierung von „Steam“ unterstützen. Veranschaulicht, wie gängige Software-Engineering-Tools die von „Valve“ veröffentlichten Endpunkte unter API ohne Exploits implementieren.\n\n252Repositorien\n4,554Links zu Rollen\nBeweismaterial im Archiv prüfen →Modul „02“ · Demografie von Ökosystemen\nKennzahlen zum globalen Engineering-Ökosystem\n\nGeografische und institutionelle Aufschlüsselung der Softwareentwickler aus dem Bereich „3,320“, die zum Automatisierungsökosystem „Steam“ beitragen, einschließlich der Zugehörigkeit zu den wichtigsten Arbeitgebern der Technologiebranche.\n\n3,320Ingenieure\n98,902Verbindungspaare\nÖkosystemkennzahlen prüfen →Modul „03“ · Interaktive visuelle Darstellung\nInteraktives Protokoll und Netzwerkdiagramm für Entwickler\n\nUmfassende interaktive Netzwerkdiagramme auf Vis.js, die Repositorys, Protokollbibliotheken (SteamKit, Steamworks, ASF) und projektübergreifende Überschneidungen bei den Mitwirkenden abbilden. Veranschaulicht anschaulich die legitime, vernetzte Open-Source-Softwarearchitektur, die das Automatisierungsökosystem von Steam antreibt.\n\nInteraktivVis.js Motor\nCluster-IsolierungLive-Suche\nKeine SicherheitslückenStandard-APIs\nInteraktives Netzwerkdiagramm öffnen →\nRegulatorischer und rechtlicher Kontext (Artikel von GDPR 25 sowie Verbraucherschutz):\nNach dem Grundsatz des „Data Protection by Design and by Default“ ist eine Plattformarchitektur, die die stillschweigende Generierung von „API“-Schlüsseln, die unangekündigte Stornierung von Handelsgeschäften und die maschinell automatisierte Liquidation von Vermögenswerten ermöglicht, eine architektonische Entscheidung des Plattformbetreibers. Wenn „Valve“ Verbraucher-Erstattungsansprüche systematisch mit der Begründung ablehnt, dass Verluste durch „externe Cyberangriffe“ verursacht wurden, verschleiert das Unternehmen, dass der Angriffsvektor in der eigValve von „“ bewusst konzipierten Web-API-Architektur liegt.\n\nINTERAKTIVE ANSICHT\n\nEine vollständig interaktive Visualisierung des Repositorys „252-“ sowie des Entwicklernetzwerkdiagramms „3,320-“ finden Sie unter network.html. Die aggregierten Kennzahlen finden Sie auf der BI-Kennzahlen Seite.\n\nDas „Steam“-Dossier · Archiv zur technischen Architektur · Öffentliche Quellenangaben · Alle Rechte wurden der Menschheit abgetreten.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam Netzwerkarchitektur – Protokolltreue und Ökosystemanalyse"
          },
          {
            "level": 3,
            "id": null,
            "text": "Offizielle Protobuf-Schemas"
          },
          {
            "level": 3,
            "id": null,
            "text": "Genehmigung für den programmatischen Handel"
          },
          {
            "level": 3,
            "id": null,
            "text": "Monetarisierter Maschinen-Traffic: Bis zu 66.7% Mindestgebühr"
          },
          {
            "level": 2,
            "id": null,
            "text": "Öffentliche Entwickler- und Repository-Infrastruktur"
          },
          {
            "level": 2,
            "id": null,
            "text": "Kennzahlen zum globalen Engineering-Ökosystem"
          },
          {
            "level": 2,
            "id": null,
            "text": "Interaktives Protokoll und Netzwerkdiagramm für Entwickler"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/de/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/de/output_steam_network/valve_ru_farming_isolated.html",
          "https://phishdestroy.io/steam_dossier/de/output_steam_network/steam_ecosystem_dashboard.html",
          "https://phishdestroy.io/steam_dossier/de/output_steam_network/network.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/de/output_steam_network__index.content.json",
      "export_json_sha256": "45ea7e172125437b11471d0a6aa3c37997d6cd80ab39a0a5931f9e39250cad8e"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "de/output_steam_network/network.html",
      "language": "de",
      "title": "Entwickler- und Repository-Explorer – Das Dossier zu „Steam“",
      "source_url": "https://phishdestroy.io/steam_dossier/de/output_steam_network/network",
      "source_html_sha256": "dd80795b28757053d726e8364587b5c3f0ad831912f3dadc28a545c4e50bb5de",
      "exported_at": "2026-09-29T00:17:16.949Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__network.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/de/output_steam_network__network.pdf?v=print-20260929-v5",
        "sha256": "bbdb8072a13afce90edcc201b2dd623448dd18e019ef5f1bb89545c9ba02204c",
        "bytes": 37114,
        "pages": 1
      },
      "integrity": {
        "signed_object": "output_steam_network__network.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__network.content.json.asc",
        "digest_file": "output_steam_network__network.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__network.content.json.asc output_steam_network__network.content.json",
          "sha256sum -c output_steam_network__network.content.json.sha256"
        ]
      },
      "content": {
        "text": "Entwickler- und Repository-Explorer\n\nEinen Knoten suchen. Die gespeicherte Beziehung überprüfen.\n\nÖFFENTLICHE UNTERLAGEN / GESAMMELTE VERBINDUNGEN\nLive-Suche\nFilterschichten\nEntwickler insgesamt3,320\nRepos insgesamt252\nANGEZEIGTE GRAFIK / TEILMENGE DER SAMMLUNG468 KNOTEN • 1103 KANTEN\nAusgewählter Profildatensatz\n\n💡 Klicken Sie auf einen beliebigen Knoten im Diagramm oder geben Sie einen Suchbegriff ein, um die erfassten Verbindungen und Quellpfade dieses Knotens anzuzeigen.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Entwickler- und Repository-Explorer"
          }
        ],
        "links": []
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/de/output_steam_network__network.content.json",
      "export_json_sha256": "9c63b718ce4976ae2b7f036fca60c3aeb581d532f2a218ad57245bf768bfa406"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "de/output_steam_network/steam_ecosystem_dashboard.html",
      "language": "de",
      "title": "Das „Collected Network“ in Zahlen – Das Dossier „Steam“",
      "source_url": "https://phishdestroy.io/steam_dossier/de/output_steam_network/steam_ecosystem_dashboard",
      "source_html_sha256": "8dec7d91197eee546e724daa51dae0782070d3fba2db8892a5b2de9f9c0b5422",
      "exported_at": "2026-09-29T00:17:16.823Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__steam_ecosystem_dashboard.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/de/output_steam_network__steam_ecosystem_dashboard.pdf?v=print-20260929-v5",
        "sha256": "0372c0edec19dfb0fdcfee4d5d84ab98c3adc2f58fd588e7dbeeec79258655ef",
        "bytes": 40532,
        "pages": 2
      },
      "integrity": {
        "signed_object": "output_steam_network__steam_ecosystem_dashboard.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__steam_ecosystem_dashboard.content.json.asc",
        "digest_file": "output_steam_network__steam_ecosystem_dashboard.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__steam_ecosystem_dashboard.content.json.asc output_steam_network__steam_ecosystem_dashboard.content.json",
          "sha256sum -c output_steam_network__steam_ecosystem_dashboard.content.json.sha256"
        ]
      },
      "content": {
        "text": "STATISTIKÜBERSICHT // DATEI-02\nSteam Ökosystem-Dashboard – Das Netzwerk in Zahlen\n\nDas Netzwerk in Zahlen.\n\nWAS DIESER ABSCHNITT BELEGT\n\nDieses Dashboard fasst Strukturdaten aus den Entwicklerteams von 3,320 und den Repositorys von 252 zusammen und identifiziert 68 glücksspielspezifische Codebasen sowie plattformübergreifende Verbindungsbrücken. Die empirischen Daten verdeutlichen geografische Clusterbildungen und Überschneidungen bei den Entwicklern und zeigen, dass die Glücksspielinfrastruktur von Drittanbietern als organisierte, stark vernetzte Softwarebranche fungiert, die in die Plattform von Steam integriert ist.\n\n← Zurück zum Executive Briefing\n\nZusammengefasste Statistiken aus der Ermittlungsdatenbank: geografische Verteilung, führende Unternehmen, Skins-Glücksspiel-Repositorien und aktive Verbindungsbrücken.\n\nScanned Devs3320\nRepos insgesamt252\nGlücksspiel-Repos68\nGesamtzahl der Verbindungen1,426\nStruktur und Branchen der Automatisierung\nSektor I – Kern der „Valve“-Gesellschaft\n\nOffizielle Repositories und Systemsoftware. Bestätigter Entwicklungsbereich der „Valve“-Mitarbeiter Nephyrin und Joe Ludwig.\n\nSektor II – Autorisierungs-Engines und Protokoll-Emulatoren (SteamKit)\n\nDurch Reverse Engineering erstellte Netzwerkbibliotheken, die gemeinsam von Nephyrin von „Valve“ und dem Entwickler von Glücksspiel-Skins DoctorMcKay verfasst wurden.\n\nSektor III – Kunden im Bereich Grafikkarten-Farming (ArchiSteamFarm)\n\nNutze SteamKit-Protokoll-Emulatoren, um im Hintergrund Millionen von gefälschten Clients (im Leerlauf) laufen zu lassen und so Sammelkarten zu farmen.\n\nEntwickler nach Region\nDeutschland57\nVereinigte Staaten52\nKanada48\nVereinigtes Königreich44\nPolen30\nFrankreich28\nRussische Föderation27\nChina27\nUSA (Bundesstaat Washington)23\nAustralien19",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam Ökosystem-Dashboard – Das Netzwerk in Zahlen"
          },
          {
            "level": 3,
            "id": null,
            "text": "Sektor I – Kern der „Valve“-Gesellschaft"
          },
          {
            "level": 3,
            "id": null,
            "text": "Sektor II – Autorisierungs-Engines und Protokoll-Emulatoren (SteamKit)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Sektor III – Kunden im Bereich Grafikkarten-Farming (ArchiSteamFarm)"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/de/#briefing-heading"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/de/output_steam_network__steam_ecosystem_dashboard.content.json",
      "export_json_sha256": "4a56e110b0ab2eb0344446fbd039b5c2463da1951e2ec753cbc972bb1716e473"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "de/output_steam_network/valve_ru_farming_isolated.html",
      "language": "de",
      "title": "Code, Mitwirkende und Forks – Das Dossier zu „Steam“",
      "source_url": "https://phishdestroy.io/steam_dossier/de/output_steam_network/valve_ru_farming_isolated",
      "source_html_sha256": "204b1e97c85cd799675b82dd625b9029ddc400a6de86c36745e6419d27e8b2af",
      "exported_at": "2026-09-29T00:17:17.256Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__valve_ru_farming_isolated.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/de/output_steam_network__valve_ru_farming_isolated.pdf?v=print-20260929-v5",
        "sha256": "626f029c16b21025fa2147915a76c8f6c0dad0dd9fcce3795b29a20676c71e5d",
        "bytes": 42353,
        "pages": 2
      },
      "integrity": {
        "signed_object": "output_steam_network__valve_ru_farming_isolated.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__valve_ru_farming_isolated.content.json.asc",
        "digest_file": "output_steam_network__valve_ru_farming_isolated.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__valve_ru_farming_isolated.content.json.asc output_steam_network__valve_ru_farming_isolated.content.json",
          "sha256sum -c output_steam_network__valve_ru_farming_isolated.content.json.sha256"
        ]
      },
      "content": {
        "text": "TEIL II / DER DOKUMENTIERTEN BEZIEHUNG FOLGEN\n\nForks, Beiträge und Software-Abhängigkeiten sind eindeutige Belege. Diese Sichtweise berücksichtigt die erfassten Rollen; Angaben zu Beschäftigung, Sicherheitsumgehungen und kriminellen Verwicklungen erfordern zusätzliche Quellen.\n\nÖffnen Sie die interaktive Kompetenzkarte ↗\nÖFFENTLICHE QUELLEN / ROLLENPRÜFUNG\nDer Code. Die Mitwirkenden. Die Forks.\n1. Nephyrin: Forks und Beiträge\n\nDer bereitgestellte Snapshot bezeichnet Nephyrin als Mitwirkenden bei ValveSoftware/Proton und als Forker von SteamRE/SteamKit und SteamRE/open-steamworks. In seinen Profildaten ist „ValveSoftware“ angegeben. Diese Felder sollten getrennt voneinander betrachtet werden.\n\nEin Fork erstellt eine Kopie eines Repositorys. Bei diesem Export wird kein Commit angehängt, der Änderungen am SteamKit-Authentifizierungscode festhält.\nRepository-Verweise / Verlauf anzeigen\nSteamRE/SteamKit ↗ SteamRE/open-steamworks ↗\n2. Öffentliche Funktionen: Automatisierung ohne Desktop-Client\n\nSteamKit und node-steam-user ermöglichen die programmgesteuerte Interaktion mit Steam. ArchiSteamFarm dokumentiert das „Card Farming“ mit mehreren Konten und gibt SteamKit2 als Abhängigkeit an.\n\nDies sind konkrete Automatisierungsfunktionen. Die „Headless“-Ausführung bedeutet weder eine ausschließliche kommerzielle Nutzung noch eine Umgehung von „Steam Guard“. Entscheidend sind die angeforderten Anmeldedaten, die damit möglichen Aktionen und die von der Plattform angewandten Kontrollen.\n\nQuelle: README-Dateien der Projekte und ArchiSteamFarm.csproj. Die Funktionsübersicht enthält Verweise auf alle dokumentierten Abhängigkeiten.\n3. JoeLudwig: das „hl2sdk-Mitwirkender“-Label\n\nDer Snapshot führt JoeLudwig als Mitwirkenden bei alliedmodders/hl2sdk, ValveSoftware/openvr und ValveSoftware/source-sdk-2013. auf. Dies ist eine nachweisbare Projektbeziehung. Der Export liefert keine Belege dafür, dass eine bestimmte SDK-Änderung mit Diebstahl oder dem Einsatz für Glücksspiele in Verbindung steht.\n\nRepository-Verweise / Verlauf anzeigen\nalliedmodders/hl2sdk ↗ DoctorMcKay/node-steam-user ↗\nLOGIKSCHALTPLAN // LEITUNGEN\nFlussdiagramm zur Verbindungslogik:\nPROFIL BEZIEHUNG\nNephyrin / zusammengestelltes Profil\nBeitragender: Proton. Forker: SteamKit und open-steamworks.\n▼ Zusammenfassung der Fork-Beziehungen\nGEMEINSCHAFTSBIBLIOTHEK\nSteamRE/SteamKit\nÖffentliche Netzwerk-Steam-Bibliothek, die von der Organisation „SteamRE“ gepflegt wird.\n▼ Angegebene SteamKit2-Abhängigkeit\nDOKUMENTIERTE AUTOMATISIERUNG\nJustArchiNET/ArchiSteamFarm\nEs wird das Sammeln von Karten über mehrere Konten hinweg sowie eine Abhängigkeit von SteamKit2 dokumentiert.\nÜBERBLICK ÜBER DIE BELEGE / QUELLENÜBERSICHT\nERFASST: Eindeutige Bezeichnungen für Mitwirkende und Forker.\nBELEGT: Öffentliche Bibliotheken fördern programmatische „Steam“-Interaktionen.\nOFFENE FRAGE: Für die Feststellung der konkreten Urheberschaft des Codes, die Genehmigung durch die Plattform und die Zuordnung des Missbrauchs sind separate Beweise erforderlich.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Der Code. Die Mitwirkenden. Die Forks."
          },
          {
            "level": 2,
            "id": null,
            "text": "1. Nephyrin: Forks und Beiträge"
          },
          {
            "level": 2,
            "id": null,
            "text": "2. Öffentliche Funktionen: Automatisierung ohne Desktop-Client"
          },
          {
            "level": 2,
            "id": null,
            "text": "3. JoeLudwig: das „hl2sdk-Mitwirkender“-Label"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/de/investigation_part2.html#automation-map",
          "https://github.com/SteamRE/SteamKit",
          "https://github.com/SteamRE/open-steamworks",
          "https://github.com/alliedmodders/hl2sdk",
          "https://github.com/DoctorMcKay/node-steam-user"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/de/output_steam_network__valve_ru_farming_isolated.content.json",
      "export_json_sha256": "873c7caa7d8fee329e1f87b16801bcbf1317a01c8f6f8d5c18e2ef61ca41793e"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "es/card_economy.html",
      "language": "es",
      "title": "La economía de las tarjetas — El Dossier Steam",
      "source_url": "https://phishdestroy.io/steam_dossier/es/card_economy",
      "source_html_sha256": "37349e99101f9f4ebd3fae7b38133a7a642fa37abd7fe3431a96ca514974b476",
      "exported_at": "2026-09-29T00:17:19.078Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "card_economy.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/es/card_economy.pdf?v=print-20260929-v5",
        "sha256": "15b174416a9e661c102042dd293edcd9ccaf69d27a270367441137823dfd659c",
        "bytes": 251716,
        "pages": 25
      },
      "integrity": {
        "signed_object": "card_economy.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "card_economy.content.json.asc",
        "digest_file": "card_economy.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify card_economy.content.json.asc card_economy.content.json",
          "sha256sum -c card_economy.content.json.sha256"
        ]
      },
      "content": {
        "text": "ANEXO V — LA ECONOMÍA DE LAS TARJETAS\nUna granja de bots no es una fuga en la tienda de Valve. Es una cliente.\n\nUna cuenta Steam no puede recibir ni una sola tarjeta de juego hasta que haya gastado $5.00 en la tienda. No puede «farmear» un juego que no le pertenece, ni tampoco uno que le hayan regalado. Así que, antes de que un sistema automatizado de «farming» de cartas produzca nada en absoluto, tiene que haber pagado por el acceso —por cuenta—, al precio que publica Valve. A continuación, la cláusula de automatización de Valve enumera, punto por punto, exactamente lo que produce ese sistema de obtención; su licencia prohíbe todas las vías por las que una carta obtenida mediante el «farming» se convierte en dinero; y su mercado se lleva una comisión cuando la carta se vende de todos modos —anunciada en 15%, pero con un mínimo de dos céntimos por venta, lo que en una carta cuyo precio está fijado en céntimos supone la mayor parte del precio—. Este ejemplo mide la magnitud de ese comercio, cuánto cuesta en sets el nivel más alto de un perfil y qué hace el departamento de cumplimiento de Valve con la misma cláusula cuando la cuenta pertenece a un comerciante corriente.\n\nLo primero que debe comprar una granjaCuánto cuesta un nivel en juegosA ambos lados del escritorio¿Quién regula el mercado de las cartas?\n$5.00Realizar un gasto en la tienda antes de que una cuenta pueda recibir cualquier tarjeta — Página de asistencia de Valve\n13,876Juegos en Steam que emiten cromos y cuentan con 99,971 tipos distintos de cromos\n694,673Conjuntos completos de cartas de los que disponen actualmente en stock 91 bots de trading que cotizan en bolsa\n1,389,346Las asignaciones de tarjetas de cuenta y de juego que el stock ya ha consumido, como mínimo\n$9.99Precio mediano de un juego de cartas: el juego completo se vende por un precio mediano de $0.74\n97,114Miembros del grupo de intercambio de cromos cuya lista de moderadores incluye a un empleado con el código Valve — § 08\n01 — El proceso\nQué es realmente una granja, paso a paso\n\nSe describe únicamente a partir de la propia documentación de la herramienta y de las páginas de asistencia de Valve. Nada de lo que figura en esta sección es una deducción, y ninguna de las partes lo cuestiona.\n\nPaso 1\nComprar en\n\nLa cuenta no debe ser limitado. La página de asistencia de Valve impide que las cuentas con restricciones «Participar en el mercado Steam», de «Intercambio de artículos de la comunidad Steam (cromos, sobres de cartas, gemas, etc.)» y de «Consigue Steam niveles de perfil (bloqueado en el nivel 0) y cromos». La entrada cuesta dinero: «Tendrás que gastar al menos $5.00 USD en la tienda Steam».\n\nPaso 2\nComprar juegos\n\nLas cartas solo se obtienen en los juegos que ya tienes. «Tienes que ser el propietario del juego en tu cuenta Steam para poder optar a las cartas que se obtengan en él. El uso compartido familiar no equivale a la propiedad y no cuenta». Las rutas gratuitas también están cerradas: «Los juegos de pago que hayas conseguido gratis durante una promoción no se pueden utilizar para conseguir cartas»., y «No puedes conseguir cartas de los juegos F2P sin gastar dinero en ellos».\n\nPaso 3\nInactivo\n\nLa herramienta inicia sesión en la red Steam de forma automática, «analiza tus insignias», crea la lista de títulos que se pueden cultivar y comienza «Jugar a los juegos que cumplen los requisitos y comprobar periódicamente si ya se ha completado la partida». Descripción del mecanismo por parte de su responsable: es «No hace más que indicar a Steam que estamos jugando a un juego determinado».\n\nPaso 4\nSe acaban las gotas\n\nCada título es finito. «Cada juego tiene un número fijo de cartas que se pueden obtener. Una vez que las hayas conseguido todas (aproximadamente la mitad del conjunto completo), el juego ya no es una opción para seguir farmando». Una granja que quiera seguir produciendo tiene que seguir comprando títulos. El suministro de cartas se ve limitado por las compras —por diseño, y en beneficio de Valve.\n\nPaso 5\nRetirar dinero\n\nLa tarjeta sale por una de estas tres vías: se vende en el Mercado de la Comunidad, se intercambia o se tritura para convertirla en gemas. Cada una de ellas constituye una transacción en el Mercado de Suscripciones o un intercambio, y el apartado § 3.D reserva el cobro: «Valve podrá cobrar una comisión por las transacciones realizadas en un mercado de suscripciones». Este es el paso que hace que todo ello constituya una infracción; véase 05.\n\nFuentes, leídas y citadas textualmente en 2026-09-22: Steam Asistencia técnica — Cuentas de usuario limitadas ↗ · ArchiSteamFarm Preguntas frecuentes ↗ · Valve — Steam Preguntas frecuentes sobre las cartas coleccionables ↗ · Steam Contrato de suscripción ↗ archivado 2026-09-24 ↗. ArchiSteamFarm se utiliza a lo largo de esta página como instrumento de medición, no como acusado; su propia documentación afirma claramente que «La ASF no está autorizada por Valve».\n\n02 — La balanza\nAntes de que una explotación agrícola gane un céntimo, ya ha pagado Valve\n\nDado que una cuenta con restricciones no puede recibir una tarjeta, todas las cuentas de una granja deben dejar de tener ese estatus antes de que puedan producir nada. El umbral está publicado y se cobra por cuenta.\n\nTamaño de la explotación agrícola\tDe dónde sale esa cifra\tImporte mínimo de compra en la tienda para poder solicitar la tarjeta\n10 cuentas\tEl límite máximo que recomienda la ASF — «basándonos en las directrices internas Valve, así como en nuestras propias sugerencias»\t$50\nEntre 100 y 200 cuentas\tLímite técnico en la misma sección de preguntas frecuentes: «Puedes ejecutar entre 100 y 200 bots con una sola dirección IP y una sola instancia de ASF».\t$500 – $1,000\n120 cuentas\tCaso de sanción n.º 3 que figura a continuación: inhabilitación permanente\t$600\n170 cuentas\tCaso de sanción n.º 2 que figura a continuación: expulsión definitiva durante las rebajas de invierno de 2017\t$850\n1,000 cuentas\tExemplo de caso de aplicación de la normativa n.º 1 que figura a continuación: prohibición de comercio\t$5,000\n5,000 cuentas sin verificar\tBáscula de operador comunicados a esta investigación y no verificados de forma independiente — véase la nota sobre la procedencia\t$25,000\n10,000 cuentas sin verificar\tBáscula de operador comunicados a esta investigación y no verificados de forma independiente — véase la nota sobre la procedencia\t$50,000\n\nLas dos últimas filas son las únicas cifras de esta página que se basan en un informe no verificado en lugar de en un documento; están señaladas en la tabla y se explican en Nota sobre el origen de los productos, y nada más aquí depende de ellos. La columna de la derecha se basa únicamente en el umbral de $5.00 USD publicado por Valve y en nada más. Es un piso, no es una estimación del coste de una granja ni de lo que Valve ha ganado: excluye los juegos, que deben ser de tu propiedad y no pueden haberse obtenido gratis en una promoción, y excluye los aproximadamente 15% que se lleva el Mercado de la Comunidad cuando se venden las cartas. En esta página no se indica ninguna cifra de ingresos.\n\nY Valve ha fijado el precio de una entrega de cartas por su cuenta. En su sección de preguntas frecuentes sobre las tarjetas coleccionables se indica la tasa de conversión del modelo «free-to-play» en dólares:\n\n«Los juegos gratuitos reparten tarjetas de juego en función de las compras que realices dentro del juego». Por cada $9 USD gastados (aproximadamente) «Desde el inicio de la beta de las cartas coleccionables Steam, obtendrás una carta al azar».\n\n— Valve, Steam Preguntas frecuentes sobre las cartas coleccionables ↗ · verificado palabra por palabra 2026-09-22\n\nUna tarjeta coleccionable no es un obsequio con el que la plataforma pierda dinero. Es algo que Valve vende, al precio Valve publicado, y por lo que luego cobra una segunda vez al revenderla. Por eso, la descripción honesta de una «granja de tarjetas» no es parásito. Es comprador mayorista.\n\nEl tamaño real del artículo que se va a comprar\n\nTodo lo que hay desde aquí hasta el final de esta sección se ha medido, no se ha extraído de informes. El censo de tarjetas procede de Steam, la lista de precios de insignias publicada por Card Exchange; los precios de los propios juegos proceden de la API de la propia tienda de Valve; y el inventario de bots procede de un directorio público de bots al que cualquiera puede acceder. Los tres datos se obtuvieron en 2026-09-22 y el cálculo se detalla íntegramente en sección 08.\n\n13,876Juegos en los que se reparten cartas\n99,971Diferentes tipos de tarjetas\n5 · 6 · 15Cartas por juego: mínimo, mediana, máximo\n$0.74Precio medio de un conjunto completo\n$23,586.57Uno de cada juego en el mercado\n¿Qué tamaño tiene un conjunto?\n\n13,876 juegos según las cartas del mazo. Valve asigna aproximadamente la mitad de ellos a una cuenta cualquiera.\n\n0\n1,250\n2,500\n3,750\n5,000\n5\n6\n7\n8\n9\n10\n11\n12\n13\n14\n15\nCuánto cuesta la licencia\n\nPrecio de catálogo de los mismos videojuegos en la tienda de Steam, en dólares estadounidenses.\n\n0\n1,000\n2,000\n3,000\n4,000\n<$1\n$1-3\n$3-5\n$5-10\n$10-20\n$20-40\n$40+\nLo que devuelve el conjunto final\n\nPrecio de mercado del pack completo de esos mismos juegos.\n\n0\n1,500\n3,000\n4,500\n6,000\n<$0.50\n$0.50-1\n$1-2\n$2-5\n$5-10\n$10+\n\nSi se comparan el segundo y el tercer gráfico, la estructura de la operación se hace evidente sin necesidad de hacer cálculos: los juegos se agrupan en la franja de las decenas de dólares, mientras que los conjuntos que generan se agrupan por debajo de un dólar. Ambos son recuentos de los mismos 13,876 juegos, en la misma unidad del eje, por lo que la comparación se realiza entre dos alturas y no entre dos escalas.\n\nEsa es la parte de la oferta. La parte de la demanda es aquella en la que Valve no tiene que hacer publicidad, porque ya está a la vista de todos: un único directorio abierto de bots de intercambio de tarjetas enumera En este momento hay 91 robots con 694,673 juegos completos en stock. Sin necesidad de iniciar sesión, sin extraer datos de un mercado online, sin datos privados: la cifra de existencias aparece impresa en la página junto al nombre de cada bot.\n\nConvierte esa acción en la única unidad que importa aquí. La propia regla de Valve: «En la mayoría de los juegos se reparten tantas cartas como aproximadamente la mitad del número de cartas que hay en el mazo de ese juego… Tendrás que conseguir la otra mitad del conjunto de otros miembros de la comunidad.\" Una sola cuenta nunca puede completar una serie jugando. Se necesitan, como mínimo, dos, cada una de las cuales debe poseer ese juego y agotar su cupo de descartes, que solo se puede utilizar una vez por partida. Los descartes no se regeneran.\n\n694,673Conjuntos en stock, 91 bots públicos\n3,473,365Cartas, con un mínimo de 5 cartas\n1,389,346Deducciones por caídas consumidas, mínimo\n2,602Cuentas que solo tienen un juego, la mayor concentración de bots\nDónde se encuentran los conjuntos 694,673\n\nLos doce mayores de los 91 «card bots» que cotizan en bolsa, según el número de juegos completos en stock. Los diez mayores cuentan con 248,115 juegos entre todos ellos, lo que supone 35.7% de todo lo que hay en el tablero.\n\n0\n11,250\n22,500\n33,750\n45,000\nCard Supply #4 (High)\nN!vq's Leveling (High)\nAlice [BOT] LEVEL-UP RARE SETS\nN!vq's Leveling (Low)\nDisco Lite Level Up\nN!vq's Leveling (Mid)\nbaty131store.net | Level Up\nKitten - Supreme\nArashirn | Level Up\nSH (Junior) Level Up\nDuobot.com - Overstock\nlvlupbot.com - godlike\n\nCada una de esas 1,39 millones de asignaciones pertenecía a una cuenta que poseía el juego, había superado la barrera de $5.00 y nunca podrá volver a generar esos botines. Esto es existencias sin vender en noventa y un bots. No es un indicador del mercado; es un indicador de lo que queda después del mercado.\n\nLa última cifra corresponde a una clasificación por categorías, no a un recuento total. Un bot indica 14,310 conjuntos extraídos de solo 11 juegos, por lo que al menos uno de esos juegos está representado por 1,301 conjuntos, lo que supone al menos 2,602 cuentas distintas que compraron cada una ese juego. Es el número más pequeño que permite el cálculo aritmético, y se refiere a un bot de entre noventa y uno.\n\nLo que dice y lo que no dice este suelo\n\nEstos bots compran cartas tanto a jugadores normales como a «granjas»; sus precios de compra publicados son el objetivo del directorio. Por lo tanto, los 1,39 millones de derechos de emisión no corresponden al número de cuentas a nombre de explotaciones agrícolas. Se trata de un recuento de los objetos que se pueden obtener una vez por cuenta y una vez por partida, que se han gastado en algún lugar de Steam y han acabado, sin venderse, en el stock comercial. Da igual si la cuenta detrás de cada una era una cuenta de farming o la de un adolescente que estaba completando su página de insignias: eso no cambia lo que Valve recaudó: el desbloqueo de $5.00, la licencia del juego y una comisión del Mercado en cada transacción — no 15%, sino 15% o los dos mínimos de un céntimo, el que sea mayor, que en una tarjeta cuyo precio se expresa en céntimos es, con diferencia, la mayor. El cálculo está en la tabla de tarifas que figura a continuación. Ese es el objetivo de esta página, y no se trata de una queja contra los agricultores: la misma conducta por la que Valve cobra una tarifa es la que cita, palabra por palabra, cuando expulsa de forma definitiva a una persona por «uso comercial».\n\nLa cifra también constituye un mínimo en un segundo sentido. Solo tiene en cuenta las acciones que son en venta y sin vender hoy sobre los bots que elegir aparecer en un directorio público. Se excluyen todos los artículos ya vendidos, todos los que se venden de forma privada y todos los bots que no figuran en el directorio.\n\nY la agricultura no es rentable con los precios de Valve.\n\nLa objeción obvia es que una granja compra juegos baratos para acuñar cartas caras. La propia API de la tienda de Steam dice lo contrario. De los 13,876 juegos que contienen cartas, los precios se fijaron en 13,713; 12,918 son títulos de pago con un precio de venta medio de $9.99. El precio medio de venta de un conjunto terminado es de $0.74. Se necesitan dos licencias por conjunto. Por lo tanto, el coste medio de un conjunto es de aproximadamente $19.98 de licencias de juego para la producción y devoluciones $0.74.\n\nMedido en 2026-09-22\tValor\tQué regula\nPrecio medio de catálogo, juego con cartas\t$9.99\tLa licencia es la parte más cara de la transacción, no la tarjeta.\nJuegos cuyo precio sea de $4.99 o menos\t3,665 (28.4%)\tIncluso la cola más barata sale más cara que el conjunto que produce\nEl juego de cartas más barato de la tienda\t$0.99\tDos licencias, $1.98, por un lote que suele venderse por menos de $1.30\nJuegos cuyo estuche se vende por más dinero que el propio juego\t323 de 12,918 (2.5%)\tEl arbitraje con tarjetas respecto a los precios de catálogo de Steam se da en 1 de cada 40 partidos.\nTítulos de acceso gratuito incluidos en el censo\t795\tY Valve fija el precio de cada uno de sus lanzamientos en $9 de gasto dentro del juego\n\nLo cual zanja la cuestión económica a favor de Valve y en contra de la versión habitual. A los precios que cobra la propia Valve, La «cría de tarjetas» es una actividad deficitaria que solo resulta rentable con licencias adquiridas por debajo del precio de catálogo de Steam. — paquetes, precios regionales, reventa clave. Las tarjetas son lo que queda. La compra es el acontecimiento. Y la compra tuvo lugar el Steam.\n\nLo que realmente sustenta la granja\n\nSi unimos todas las piezas, la granja deja de parecer algo que Valve tolera y empieza a parecer algo que Valve necesita. Cada insumo que suministra una granja es un producto que Valve contabiliza o factura. Sigue el recorrido de una cuenta de bot hacia fuera:\n\nUna cuenta creada artificialmenteun «cliente mayorista», no una filtración\nVentas de videojuegos\n\nCompra los títulos que cultiva —desde los juegos de cartas 13,876 hasta los shovelware $0.50— porque las cartas solo se obtienen de los juegos que ya posee.\n\n«En línea» y tiempo de juego\n\nHace que los jugadores inactivos suelten cartas, lo que alimenta las cifras de jugadores simultáneos y horas jugadas que Valve cita como «compromiso», la estadística exacta que el § 4.C denomina «tiempo de juego falso».\n\nInscripciones\n\nDebe superar el control de la cuenta limitada $5.00 antes de poder recibir una tarjeta: un gasto real en tienda de Valve libros por cuenta.\n\nDinero en el monedero y comisiones\n\nCada tarjeta que vende pasa por el Mercado, donde la comisión alcanza hasta 66.7% en el caso de una tarjeta de bajo valor y los ingresos permanecen bloqueados en la Cartera Steam.\n\nRelaciones públicas de nivel Steam\n\nLas insignias y los niveles Valve solo existen porque se crearon conjuntos, y los primeros puestos de esa clasificación están ocupados por bots (véase el apartado 03).\n\nSi eliminas la granja, todos los números anteriores disminuyen. — El juego vendió menos copias, la parte «online» era más reducida, la cuenta nunca se registró, nunca se cobró la cuota y nunca se alcanzó el nivel. Por eso, una norma que prohíbe la automatización coexiste con millones de cuentas automatizadas: la prohibición es la opción, y la actividad es la fuente de ingresos.\n\nY el propio cobro supone una pérdida de valor: Valve impuestos por partida doble\n\nLa carta no es el final del ciclo. La mecánica propia de Valve permite que una carta sea aplastada hasta convertirse en joyas, y se deben gastar gemas para fabricar paquetes de cartas — tres cartas más — que se venden o se destruyen de nuevo. Cada paso corresponde a una transacción en el mercado o a una conversión, y cada una de ellas está sujeta a impuestos. La dirección de ese bucle se deriva del umbral mínimo de comisión que se calcula a continuación y no requiere ningún modelo externo: cada carta vendida dentro de él cede al menos dos céntimos, en tarjetas que se intercambian por un valor de tres a cinco, de modo que cada vuelta de la manivela reporta menos de lo que se invirtió. Este círculo vicioso destruye el valor virtual y obliga a realizar nuevas transacciones, sujetas a comisiones, para sustituirlo. En este texto no se indica ninguna cifra sobre la cuantía de dicha pérdida. — La recompensa por conjunto depende de las tasas de gemas y de las probabilidades de los sobres, que no se han medido en este estudio.\n\nTarjeta coleccionableobjetos que se obtienen en el juego\n→\nGemasTarjeta destrozada, cuota cobrada\n→\nPaquete de refuerzogemas gastadas en la fabricación\n→\n3 cartas nuevasVendido en Market, comisión cobrada\n↶\n\nAquí solo se exponen las mecánicas, que son propias de Valve: las cartas se convierten en gemas, con las gemas se crean sobres y los sobres proporcionan cartas; todo ello está documentado en las Preguntas frecuentes sobre cartas coleccionables de Steam, y cada paso constituye un evento de mercado sujeto a impuestos. Origen de las mecánicas del bucle: Valve, Steam Preguntas frecuentes sobre las cartas coleccionables ↗.\n\nNo se trata de un momento puntual. Es un sector con una trayectoria de varios años.\n\nUna sola instantánea podría ser una casualidad. Por eso, se consultó el directorio público de bots de tarjetas una vez por cada rebaja de temporada Steam, a través de Wayback Machine, desde 2022 hasta 2026: el stock fijo que llevaban los bots y las mismas cuentas, rebaja tras rebaja. La economía no aparece y desaparece; persiste, con un núcleo estable de operadores, y alcanzó su punto álgido con más de Tres millones de juegos completos en stock durante la venta de invierno de 2023: alrededor de un tercio de millón de claves de TF2 de valor almacenadas en un momento dado, en un único directorio.\n\nConjuntos completos de cartas almacenados en el directorio público de bots, por Steam venta\n\nUna instantánea de Wayback de steam.supply/CardBots por cada venta de temporada. Pasa el cursor por encima para ver el valor en claves de TF2 según el tipo de cambio de esa instantánea.\n\n0.0M\n0.9M\n1.8M\n2.6M\n3.5M\nA’22\nS’23\nW’23\nS’24\nW’24\nS’25\nS’26\n401Cuentas de bots distintas detectadas en las ventas\n59Presente en 5 o más de las 7 ventas: el núcleo estable\n16Ha estado presente en todas y cada una de las 7 subastas, entre 2022 y 2026\n3,22 millonesConjuntos Peak en stock (invierno de 2023) ≈ $570k–790k en llaves\nAsí es como se ve la escala de insignias de ventas desde lo más alto\n\nLa demanda se ajusta a la oferta. En el ámbito público Escalera de insignias de las rebajas de verano de 2024 archivado 2026-07-16 ↗, la cuenta número uno había creado la insignia de venta 1,740,645 veces — 1,74 millones de juegos de diez cartas, 17,4 millones de tarjetas integrados en un único perfil decorativo. Al precio de mercado de la propia tienda ($0.50 el juego), eso supone ~$870,000 del valor de la tarjeta; si se compra tal y como se compra en realidad —llaves de TF2 intercambiadas para subir de nivel a los bots a razón de unos 7,6 conjuntos por llave—, resulta que es ~229,000 teclas, aproximadamente $410,000–$570,000 en términos reales. La cuenta número dos: 552,000 conjuntos, ~$130,000–181,000. Ningún humano juega por esto. Se compra, y cada tramo de la compra es una transacción que Valve liquida.\n\nMétodo y límites: el stock total se suma entre todos los bots que aparecen en cada instantánea; el número El número de bots por instantánea no es comparable entre las distintas ventas, ya que algunas instantáneas solo muestran los bots destacados y otras el directorio completo; por lo tanto, el stock se interpreta como un mínimo de lo que estaba visible, no como un censo. Los valores de las claves utilizan la mediana de la tasa de conjuntos anunciados por clave de cada instantánea y una clave TF2 de $1.79–$2.49. La persistencia se mide mediante el SteamID64 a lo largo de las instantáneas. Las instantáneas de 2021 utilizaban un diseño de página más antiguo y no se han incluido. Datos: cronología-de-la-economía-agrícola.json; niveles de insignias de SteamLadder; precios fijados en Steam Card Exchange (instantáneas de Wayback en el momento de la venta, $0.05 por carta).\n\nY esa misma flota sigue ahí cuando no hay ninguna oferta en marcha\n\nLas dos imágenes de arriba no corresponden a dos poblaciones distintas. Se trata de una misma flota, fotografiada en momentos diferentes. El directorio que aparece en la parte superior de esta sección se leyó en un un día cualquiera en el que no hay ninguna oferta de temporada — 2026-09-22 — e incluso en reposo se mantenía 91 bots y 694,673 conjuntos completos: del orden de 186,000 teclas de TF2, $334,000–$464,000 del valor de la carta, inactivas entre ventas. Ese es el nivel mínimo que mantiene la operación cuando no hay actividad.\n\nY se trata de la misma operación. Identificada por el SteamID64, 87 de esos 91 bots inactivos — 96% — también aparecen en las siete instantáneas de ventas anteriores, dieciséis de ellos en cada uno. El directorio no es un puesto que se abre para la venta y se cierra después; es un inventario comercial permanente que esta misma flota ha ampliado hasta alcanzar 3,22 millones de unidades en el pico del invierno de 2023 y nunca baja a cero. Una rebaja es cuando se vende. También existe el resto del año.\n\nEl directorio de reposo, bot por bot\n\nCada cuadrado representa un bot del directorio en 2026-09-22, que aparece resaltado si también figura en las siete instantáneas de ventas. 91 es la cifra que figuraba en el directorio ese día, no el tamaño de la flota — En las instantáneas de ventas aparecen 401 cuentas distintas, y el directorio muestra una selección diferente cada día.\n\nVisto en subastas anteriores (87) Novedades desde la última instantánea (4)\n\nLa lectura de referencia sin rebajas es 2026-09-22 desde el mismo directorio público, sin necesidad de iniciar sesión. El valor en reposo utiliza la tasa de conjuntos por clave anunciada por cada bot y el intervalo de claves $1.79–$2.49 anterior. La superposición se realiza mediante SteamID64 con respecto a las siete instantáneas de rebajas. Dado que el listado destacado difiere del completo según la instantánea, aquí se comparan las existencias y la identidad, no el número de usuarios. Cálculos en sección 08.\n\n03 — La escalera\nEl otro producto es el número que aparece junto a tu nombre\n\nLas cartas son la materia prima. El producto final es de nivel Steam, y Valve establece su precio por lotes.\n\n100Steam Nivel\nNivel objetivo: arrastra o utiliza las teclas de flecha\nPrecio de un juego completo, en dólares estadounidenses\n\n$0.20 es el juego completo más barato del censo, $0.74 la mediana y $1.70 la media. La cifra se refiere únicamente a las cartas, nunca a los desbloqueos $5.00 ni a las licencias del juego.\n\n55,000Se requiere XP\n550Conjuntos completos consumidos\n110Juegos para tener en tu colección, que te ganas tú mismo\n$407.00Precio de las tarjetas a ese precio\n1,100Indemnizaciones por despido, mínimo\n$5,500.00$5.00 se desbloquea, si no se reutiliza ninguna cuenta\nConjuntos completos consumidos, del nivel 1 al 1,000\n\nUna manualidad de insignias = un conjunto completo = 100 XP. Cada nivel dentro de un bloque de diez cuesta 100 XP más que el bloque inferior.\n\n0\n12,625\n25,250\n37,875\n50,500\n1\n250\n500\n750\n1000\n667\n550 sets\n\nUn nivel no es un adorno que Valve pueda ignorar. Está vinculado a la cuenta. Según las propias preguntas frecuentes sobre las cartas de juego de Valve, esto es lo que se obtiene al crear una insignia: «100 XP, que pueden aumentar tu nivel Steam. Si tu nivel Steam aumenta, el límite del tamaño de tu lista de amigos se ampliará en cinco personas., y es posible que puedas desbloquear la opción de personalizar tu perfil con galerías». Y sobre los sobres de cartas: «Tu nivel Steam aumenta la probabilidad de obtener un sobre de cartas: Nivel 10: +20%… Nivel 50: +100% de aumento en tu probabilidad de obtención (es decir, la probabilidad se ha duplicado)».\n\nAsí pues, el nivel determina dos cosas: Valve controla cuántas personas puedes tener como amigos y la rapidez con la que las cartas gratuitas se añaden a tu inventario. Esto último se acumula: cuantos más conjuntos hayas consumido, más rápido te proporcionará la plataforma más material. Valve incorporó el ciclo de reinversión al producto.\n\nEl tipo de cambio es fijo y se publica. Cada creación de insignia consume un conjunto completo y otorga 100 XP; «Puedes crear un conjunto para el mismo juego un máximo de cinco veces». El coste en XP por nivel aumenta cada diez niveles. Esto da lugar a lo siguiente, y ninguna de estas cifras es aproximada:\n\nSteam Nivel\tConjuntos completos que consume\tJuegos que debes tener para poder crearlos tú mismo\tAl nivel más bajo registrado ($0.20)\tEn el conjunto mediano ($0.74)\tEscala\n10\t10\t2\t$2.00\t$7.40\t\n50\t150\t30\t$30.00\t$111.00\t\n100\t550\t110\t$110.00\t$407.00\t\n200\t2,100\t420\t$420.00\t$1,554.00\t\n500\t12,750\t2,550\t$2,550.00\t$9,435.00\t\n667\t22,579\t4,516\t$4,515.80\t$16,708.46\t\n\n667 no es una cifra hipotética. Es el nivel más alto al que un único bot del directorio público anuncia que puede llevar a un cliente, de entre los 33,359 conjuntos que posee en 6,117 juegos. La cuarta columna muestra el mismo precio en la escalera comparado con el conjunto completo más barato de todo el censo; la quinta, comparado con la mediana. Ambos son precios de mercado solo para las cartas y excluyen por completo el desbloqueo $5.00 y las licencias de los juegos.\n\n¿Cómo se comprobó la curva, ya que Valve no la publica?\n\nValve indica la tasa de insignias («Por cada 100 XP, obtienes un nivel adicional de Steam».) y luego lo cubre — «(al menos al principio)» — sin publicar la escalada. La curva utilizada anteriormente es la estándar, en la que cada nivel dentro de un bloque de diez cuesta 100 XP más que el bloque inferior. Se verificó con el directorio en lugar de darlo por supuesto: para cada bot cuyo máximo anunciado esté limitado por su stock en lugar de por el límite de cinco creaciones por partida, el nivel calculado a partir de esta curva coincide exactamente con el nivel que indica el bot — 541 contra 541, 494 contra 494, 464 contra 464. En los casos en los que el límite máximo se aplica, la cifra calculada es ligeramente superior, que es precisamente lo que debería ocurrir con un límite máximo que también depende de la profundidad de la plantilla por partido. No se hace ninguna afirmación sobre la curva por encima del nivel 667.\n\nLee la tabla que hay junto a la sección 02 y verás cómo funciona el negocio. Para situar una cuenta en el nivel 500, alguien debe reunir 12,750 conjuntos completos. Cada uno de esos conjuntos requirió al menos las asignaciones de botín de dos cuentas, cada una de las cuales había superado la puerta $5.00 y poseía el juego. Cada número de vanidad que aparece en la parte superior de un perfil se sustenta en al menos 25,500 asignaciones de gotas gastadas situadas debajo de él. Valve no va a perder esa operación. Valve es la contraparte en cada tramo de la misma.\n\n04 — Las estadísticas\nLa cláusula no se refiere a la agricultura de forma vaga. La enumera.\n\nEl apartado § 4.C no es una frase general contra los bots. Los ejemplos que enumera mencionan, uno tras otro, las dos cosas que produce una «card farm».\n\n«No está permitido utilizar ningún tipo de script, bot, macro u otros sistemas no controlados por personas («automatización») para interactuar con el Contenido y los Servicios de Steam de ninguna manera, incluyendo, entre otros:\n\nAutomatizar el proceso de creación de cuentas Steam,\nFalsificar estadísticas de juego (por ejemplo, inflar el número de victorias o derrotas, la XP o el tiempo de juego),\nObtener recompensas o avanzar sin una participación real por parte de los usuarios,\n«Participar en sistemas de evaluación (como las revisiones por pares o el «overwatch») mediante medios automatizados, lo que incluye influir en los resultados o denunciar a usuarios mediante acciones programadas en lugar de un juicio fundamentado».\n— Steam Contrato de suscripción, artículo 4.C ↗ archivado 2026-09-24 ↗ · extraído y citado textualmente 2026-09-22\n«…la hora de jugar»\n\nLas horas de inactividad no son horas fantasma. La sección de preguntas frecuentes de la ASF responde a esta pregunta sin rodeos: — «¿Por qué no aumenta el tiempo de juego de los juegos obtenidos a través de ASF?» — con: «Sí, pero no en tiempo real. Steam registra el tiempo de juego en intervalos fijos y programa una actualización al respecto… Normalmente se actualiza cada 30 minutos más o menos».\n\nEsas horas se registran en los registros de Valve, en las páginas de la tienda de Valve y en los recuentos de jugadores simultáneos que Valve publica por su cuenta. Steam Gráficos ↗ archivado 2026-09-23 ↗. En esas cifras, una cuenta inactiva es indistinguible de una activa. Las cifras de interacción que la plataforma facilita al exterior se calculan sobre una población que incluye, según las propias normas de la plataforma, cuentas que no están activas.\n\n«…sin una aportación real por parte de los usuarios»\n\nEsa es una definición de «sorteo de cartas inactivas», redactada por Valve. También es una definición del nivel Steam, la insignia, los requisitos para obtener sobres de expansión y los XP de perfil que conlleva; la sección de preguntas frecuentes de la ASF confirma esta herramienta. «mantiene la posibilidad de recibir sobres de cartas», ya que se conecta igual que el cliente oficial.\n\nAsí pues, el sistema de recompensas y el acto prohibido son un mismo mecanismo visto desde dos perspectivas diferentes. Valve estableció que la recompensa se generara en función del tiempo y no de la habilidad, y luego redactó una cláusula que prohibía la generación de recompensas por cualquier medio que no fuera el tiempo dedicado por una persona.\n\n05 — La trampa del uso comercial\nCada salida desde una sala de juego es una salida que la licencia prohíbe, y Valve cobra una tarifa en la puerta.\n\nEsta es la parte que no se puede resolver practicando el «farming» de forma «responsable». La licencia es para uso personal y no comercial, y una tarjeta solo merece la pena «farmearla» en el momento en que deja de ser de uso personal.\n\n§ 2.A — la licencia\n\n«Valve concede por la presente, y tú aceptas, una licencia y un derecho no exclusivos para utilizar el Contenido y los Servicios con fines de» uso personal y no comercial (salvo en los casos en que el uso comercial esté expresamente permitido en el presente documento o en las Condiciones de suscripción aplicables).»\n\n§ 2.G — la restricción\n\n«No tienes derecho a: … (iii) aprovechar el Contenido y los Servicios, o cualquiera de sus partes, con fines comerciales, salvo en los casos expresamente permitidos en otras disposiciones del presente Acuerdo (incluidas las Condiciones de suscripción o las Normas de uso).»\n\n§ 3.D — la tasa\n\n\"Valve puede cobrar una comisión por las transacciones realizadas en un mercado de suscripciones. «Se le informará de cualquier comisión antes de que se complete la transacción».\n\nSi se leen los tres juntos, la posición se cierra.\n\nUna carta que se conserva no tiene ningún valor para una granja. Una carta que se vende, se intercambia o se transforma en gemas se ha utilizado para generar valor —y Valve ha explicado en su propia carta de medidas disciplinarias cómo denomina esto: al operador de 170 bots se le comunicó que la cuenta «se utilizaba para obtener de forma ilegal cromos coleccionables en Steam, así como para actividades relacionadas, no solo de carácter comercial». En ese caso, las tarjetas llegaron al mercado. Las ventas se completaron. Se cobró la comisión. La prohibición se produjo después.\n\nLa tarifa en esa puerta no es de 15%. En una tarjeta de cultivo alcanza dos tercios.\n\n§ 3.D: reservas «una tarifa». En las tarjetas que produce realmente una granja, esa comisión no se parece en nada al ~15% anunciado. El Mercado Comunitario cobra un 5% Steam de comisión por transacción y una 10% de comisión por partida, cada una con un mínimo de $0.01 (Preguntas frecuentes del Community Market de Valve). En una tarjeta que cuesta un céntimo, esos niveles son El precio: el comprador paga tres céntimos, dos de los cuales son comisiones. El redondeo a la baja convierte el titular «15%» en un gravamen efectivo que asciende a 66.7% exactamente dónde se mueve el mercado de las tarjetas: unos pocos céntimos por tarjeta.\n\nComisión efectiva en una venta en el mercado comunitario, según el precio de venta solicitado por el vendedor\n\n5% Steam + 10% de juego, cada uno con un mínimo de $0.01. La franja sombreada es donde realmente se intercambian las cartas coleccionables: aproximadamente entre $0.03 y $0.05 por carta.\n\n0%\n10%\n20%\n30%\n40%\n50%\n60%\n70%\ncards\n$0.01\n$0.10\n$0.20\n$0.30\n$0.40\n$0.50\n66.7%\nEl vendedor quiere\tSteam 5% (mín. $0.01)\tPartido 10% (min $0.01)\tLos gastos corren a cargo del comprador\tCuota combinada\n$0.01\t$0.01\t$0.01\t$0.03\t66.7%\n$0.03\t$0.01\t$0.01\t$0.05\t40.0%\n$0.05\t$0.01\t$0.01\t$0.07\t28.6%\n$0.08\t$0.01\t$0.01\t$0.10\t20.0%\n$1.00\t$0.05\t$0.10\t$1.15\t13.0%\n\nLa comisión de 10% por partida se destina a la aplicación que ha emitido la tarjeta; el 5% es para Valve, y en los títulos propios de Valve y en los artículos del inventario básico, la comisión íntegra es para Valve. En cualquier caso, el dinero sale del bolsillo del «farmer»: vender una tarjeta de tres céntimos le reporta un céntimo y le hace perder dos. Multiplica eso por los cientos de miles de ventas de tarjetas de menos de cinco céntimos que genera una granja y «la tarifa que Valve puede cobrar» es el modelo de negocio, no una nota al pie. Fuente: Steam Preguntas frecuentes sobre el mercado comunitario — Tarifas ↗ archivado 2026-09-21 ↗, léase 2026-09-22; la curva es aritmética sobre esos dos tipos publicados y sus límites mínimos $0.01.\n\nNo hay ninguna configuración de la herramienta que permita eludir esto. Puede ser utilizada por una sola persona, en una sola cuenta, con la máxima moderación; y en el momento en que esa persona venda una sola tarjeta obtenida de forma fraudulenta a cambio de fondos de monedero, la misma sanción prevista en el apartado § 2.G se le aplicará a ella, al igual que al operador de diez mil. Por lo tanto, Valve se ha reservado el derecho a invocar un incumplimiento contra prácticamente cualquier vendedor de cartas en su propio mercado, y ha decidido no invocarlo contra prácticamente ninguno de ellos. Una norma que se aplica con esa frecuencia no es una norma. Es una opción. La pregunta que plantea esta exposición no es por qué se tolera a los «card farmers»; sino por qué se aplica esa misma medida contra un usuario aislado que vende una tarjeta, mientras que la economía comercial de tarjetas a la que estas alimentan —los servicios de intercambio, los bots para subir de nivel, los vendedores al por mayor— sigue funcionando a la vista de todos, con uno de sus grupos más grandes moderado por un empleado Valve (§ 08). La infracción se reserva para el pequeño poseedor y se pasa por alto en el caso de la máquina.\n\n06 — El historial de cumplimiento\nSin previo aviso, por oleadas, y se propaga a través del número de teléfono\n\nValve incluyó la facultad de rescisión sin preaviso en el propio acuerdo, en una cláusula situada justo después de la cláusula de automatización.\n\n«Valve podrá restringir o cancelar tu(s) cuenta(s) o una suscripción concreta por cualquier conducta o actividad que sea ilegal, constituya un truco o una automatización, o incumpla las Normas de conducta en línea Steam. Reconoces que Valve no está obligado a notificarte antes de rescindir tu(s) suscripción(es) y/o tu cuenta.\"\n\n— Steam Contrato de suscripción, artículo 4.D ↗ archivado 2026-09-24 ↗ · verificado palabra por palabra 2026-09-22\n\n1,000+ bots · prohibidas las transacciones. «Parece que esta cuenta se utilizó para gestionar una red de cuentas de bots. El uso de bots constituye una infracción del Acuerdo de suscriptor Steam».\n\nMás de 170 bots · bloqueados de forma permanente, rebajas de invierno de 2017. «Esta cuenta se utilizó para coleccionar ilegalmente cromos en Steam, así como para actividades relacionadas, no solo de carácter comercial. La cuenta ha sido bloqueada de forma permanente y el servicio de atención al cliente de Steam no puede ofrecer asistencia adicional sobre este asunto».\n\nMás de 120 bots · bloqueados de forma permanente. «Esta y otras cuentas se utilizaron para saturar nuestra infraestructura de red, lo que constituye una infracción de las normas de conducta en línea Steam».\n\n— Steam Mensajes de asistencia reproducidos en la ArchiSteamFarm sección de preguntas frecuentes, apartado «¿Han expulsado a alguien por eso?». Fuente ↗ · verificado palabra por palabra 2026-09-22\nCaso 4 — Junio de 2025, VAC prohibiciones sobre el CS2 inactivo\n\nEn el propio sistema de seguimiento del proyecto se ha registrado un episodio posterior a los tres anteriores: las cuentas que solo habían dejado inactivo Counter-Strike 2 a través de la herramienta recibieron VAC prohibiciones — del tipo «antitrampas», no del tipo «administrativo». La postura del responsable del mantenimiento es que el tiempo de inactividad no puede provocar uno, ya que «No hace más que indicar Steam que estamos jugando a un juego determinado». La causa es objeto de controversia. Que se bloquearan las cuentas, en cambio, no lo es.\n\n— ArchiSteamFarm debate n.º 3440, iniciado el 26 de junio de 2025 ↗ · leer 2026-09-22\n\nCómo se cierra una cuenta principal\n\nEn el mismo hilo, un colaborador del proyecto describe la norma de propagación: se pueden bloquear cuentas «por cadena», si utilizan el mismo número de teléfono — «Puede que se trate simplemente de una suspensión VAC, que se haya extendido a cuentas \"limpias\" vinculadas a la cuenta suspendida».\n\nSteam Guard requiere un número de teléfono. Las «granjas» se crean a partir del número de teléfono del operador. Por lo tanto, las medidas de control no se limitan a las cuentas desechables: siguen la pista del identificador compartido hasta la cuenta que contiene la biblioteca, la lista de amigos y el inventario. Ese es el mecanismo que describe un colaborador del proyecto para explicar cómo una sola acción elimina la cuenta principal de un operador junto con la granja, y es la razón por la que la pérdida en una oleada de medidas coercitivas no se mide en $5 cuentas. (Descrito por un colaborador del proyecto en la discusión n.º 3440 de GitHub de la ASF; no hay ninguna confirmación oficial Valve ni ningún precedente formal registrado).\n\nEl mismo párrafo, con cinco años de diferencia, de tres agentes distintos\n\nLa cláusula que considera la actividad agrícola como un incumplimiento —el uso comercial de una licencia personal y no comercial— no se limita a las explotaciones agrícolas. Es el motivo habitual que Steam alega cuando cierra una cuenta por motivos comerciales, y dicho motivo se presenta en forma de plantilla. A continuación se muestran tres ejemplos, publicados por las personas que los recibieron, con cinco años de diferencia, procedentes de tres agentes diferentes identificados.\n\nMensaje del servicio de atención al cliente Steam el 29 de septiembre a las 19:56 h\n\n«La cuenta desde la que estás escribiendo ha sido bloqueada por infringir las condiciones del Acuerdo de suscriptor Steam. Se ha determinado que la cuenta se utiliza con fines comerciales, basándose en operaciones bursátiles, denuncias de la comunidad y otros factores.»\n\nEste bloqueo es permanente y Steam El servicio de asistencia no puede ayudarte más con este asunto.\n\nDado que ya te hemos facilitado toda la información de la que disponemos, voy a cerrar esta solicitud de ayuda. Ten en cuenta que no recibirás más respuestas sobre este asunto.\n\nSaludos,\n«Hal»\n\nEsta solicitud de ayuda se ha cerrado.\n29 de septiembre de 2020. Publicado por el destinatario con el siguiente comentario: «Adiós, RIP Trading». — @gergelyszabo94 ↗\nMensaje del servicio de asistencia Steam el 12 de julio a las 22:41\n\n«La cuenta desde la que estás escribiendo ha sido bloqueada por infringir los términos del Acuerdo de suscripción Steam. Se ha determinado que la cuenta se utiliza con fines comerciales, basándose en operaciones, denuncias de la comunidad y otros factores.»\n\nEste bloqueo es permanente y Steam El servicio de asistencia no puede ayudarte más con este asunto.\n\nDado que ya te hemos facilitado toda la información de la que disponemos, voy a cerrar esta solicitud de ayuda. Ten en cuenta que las futuras solicitudes de ayuda que se envíen en relación con el bloqueo de la cuenta podrían cerrarse sin respuesta.\n\nSteam Asistencia\n«Vido»\n\nEsta solicitud de ayuda se ha cerrado.\n12 de julio de 2024, interfaz en portugués. El destinatario es un jugador profesional de CS2: «Ya me he puesto en contacto con el servicio de asistencia de Steam, pero solo recibo respuestas automáticas… No puedo jugar a Faceit ni participar en partidas profesionales». — @prcs25 ↗ archivado 2024-07-15 ↗\nCitado por el destinatario, r/steamsupport\n\n«Hola, la cuenta desde la que estás escribiendo ha sido bloqueada por infringir las condiciones del Acuerdo de suscriptor Steam. Se ha determinado que la cuenta se utiliza con fines comerciales a partir de las operaciones realizadas, las denuncias de la comunidad y otros factores.»\n\nEste bloqueo es permanente y Steam El servicio de asistencia no puede ayudarte más con esto.\n\nDado que ya te hemos facilitado toda la información de la que disponemos, voy a cerrar esta solicitud de ayuda. Ten en cuenta que las futuras solicitudes de ayuda que se envíen en relación con el bloqueo de la cuenta podrían cerrarse sin respuesta.\n\nSteam Asistencia\n«Sally»\n\nSe ha recibido en tres ocasiones, en respuesta a tres solicitudes distintas.\n29 de marzo de 2025. El autor no estaba recurriendo el bloqueo: le habían robado la cuenta junto con su correo electrónico y solicitaba acceso: «No estoy preguntando por la suspensión ni la estoy cuestionando; solo quiero acceder a mi cuenta de Steam… Valve me han dado exactamente esta misma respuesta, copiada y pegada en todas las solicitudes, y cierran la solicitud». — r/steamsupport ↗, recogidos en el propio corpus de denuncias de esta investigación\n\nPalabra por palabra, coma por coma, a lo largo de cincuenta y cinco meses, con tres agentes y dos idiomas de interfaz. La única modificación en todo el texto es la precisión en la última frase, que pasa de 2020 a 2024, de «No recibirás más respuestas» a «Las futuras solicitudes de ayuda… podrían cerrarse sin respuesta.» Sea cual sea el proceso que haya dado lugar a estas decisiones, la carta no constituye un registro del mismo. Los motivos alegados son «actividades comerciales, informes de la comunidad y otros factores»: una categoría, un informe de origen desconocido y un resto sin especificar.\n\nOtros cinco casos, recopilados de la misma forma. Los tres primeros pertenecen a la misma categoría y tienen el mismo resultado; los dos últimos corresponden a la misma oficina y responden a una norma diferente expresada con las mismas palabras:\n\nFecha\tQué hizo la cuenta\t¿Qué pasó?\tFuente\n4 de diciembre de 2021\tComprar y vender en Buff — «No he hecho más que algunas operaciones de compra y venta en Buff, también conocido como comercio P2P».\tSanción de la comunidad: sin mercado, sin intercambios, existencias costosas congeladas\tr/csgomarketforum ↗ archivado 2025-03-27 ↗\n6 de diciembre de 2021\tIntercambios P2P unidireccionales a través de Buff y Bitskins para equipamientos y mejoras\tCerradura permanente para uso comercial más cerradura comunitaria: «Atrapado en un modo pseudoinvisible… Mi perfil también sigue en modo privado».\tr/GlobalOffensiveTrade ↗ archivado 2021-12-06 ↗\n20 de diciembre de 2024\tCuenta desde 2017, miles de horas; intercambios en mercados comunitarios para conseguir equipamientos temáticos y mejoras.\tBloqueo permanente con bloqueo comunitario, sin aviso previo ni penalización; apoyo «afirman que su decisión es definitiva», las respuestas son automáticas\tr/csgomarketforum ↗ archivado 2025-06-27 ↗\n23 de diciembre de 2024\tUn usuario que vuelve al servicio recarga su monedero tras un año de ausencia, utilizando una VPN «solo para la seguridad general en Internet»\tExpulsión permanente de la comunidad con no se ha dado ninguna razón: «La prohibición es permanente y no pueden facilitar más información; además, es posible que se cierren otras incidencias sin dar respuesta». 196 votos positivos, 340 respuestas\tr/steamsupport ↗\n4 de agosto de 2026\tAños de compras en Irán; el autor afirma que nunca publicó nada, nunca utilizó el Market ni los foros.\tAcceso a la comunidad bloqueado hasta el año 2038 más allá de «regiones sujetas a sanciones»; ticket cerrado por un agente llamado Azul. Un año antes se había aprobado un reembolso de la misma cuenta desde la misma dirección IP iraní. La biblioteca y el dinero se quedan con Valve.\tr/pcgaming ↗\n\nLa última fila se rige por una norma diferente al resto —cumplimiento de sanciones, no uso comercial— y se incluye porque la estructura de la respuesta es idéntica: una categoría, sin pruebas, sin recurso, un ticket cerrado. Además, plantea una cuestión que las demás no plantean. Si era ilegal prestar servicio a la cuenta, también era ilegal aceptar los pagos realizados durante esos años. Una de esas dos posturas tiene que ser errónea, y solo una de ellas le ha supuesto algún coste al cliente.\n\nLas ocho se leyeron en 2026-09-22: los hilos de 2021 y diciembre de 2024 a través de instantáneas de Internet Archive y el resto a través de una interfaz pública de Reddit, ya que Reddit rechazó las solicitudes directas del servidor encargado de la recopilación. Las dos cartas de 2020 y 2024 se han transcrito a partir de las capturas de pantalla adjuntas a las publicaciones originales, que siguen activas. Esta investigación no atribuye a ninguna de estas cuentas la inocencia ni la culpabilidad de nada; ese es precisamente el quid de la cuestión. Ni el lector ni el regulador pueden deducirlo por la carta.\n\nNota sobre el abastecimiento: pérdidas a escala de operador\n\nLos operadores encuestados en el marco de esta investigación declaran pérdidas del orden de entre cinco mil y diez mil cuentas cada una en campañas de control puntuales, en las que se inspeccionan las cuentas principales junto con la explotación agrícola. Esa encuesta se recoge aquí como información de primera mano, no como una conclusión. No se ha publicado el tamaño de la muestra, no hay una fecha de recopilación fija ni una verificación por cuenta, y ninguna otra cifra de esta página depende de ella; las dos filas de la sección 02 que se basan en ella están marcadas como tales.\n\nSe afirma, en lugar de dejarse de lado, por dos razones. El mecanismo de prohibición en cadena mencionado anteriormente es la explicación documentada de precisamente ese patrón. Y un regulador puede exigir a Valve el único dato que lo aclararía: cuántas cuentas se procesaron por automatización, en qué oleadas y cuánto había gastado cada una de esas cuentas en la tienda antes de que se cerrara. Hasta que ese dato exista, la cifra se mantiene tal y como está: comunicada, atribuida y sin demostrar.\n\n07 — La asimetría\nLos dos lados del mismo escritorio\n\nCompara ese nivel de prueba con el Valve aplicado a su propia operación de apoyo. La columna de la derecha es el registro de incidentes de este expediente, reproducido tal y como aparece allí, con las salvedades que incluye.\n\nUn cliente, para operaciones bursátiles\n\nOcho casos documentados, 2020-2026\n\nConducta\nVender o comprar artículos en plataformas de terceros; en un caso, no hubo conducta alguna: la cuenta había sido pirateada.\nPruebas presentadas\nNinguna. «Teniendo en cuenta las operaciones bursátiles, los informes de la comunidad y otros factores».\nAviso\nNinguna. Valve se reserva lo dispuesto en el apartado 4.D: «Valve no está obligada a notificártelo antes de rescindir el contrato».\nRecurso\n«Este bloqueo es permanente y Steam El servicio de asistencia no puede ayudarte más con este asunto».\nEntrada\nCerrado tras la primera respuesta. Solicitudes adicionales «puede cerrarse sin respuesta».\nAlcance\nPerfil, lista de amigos, chat, Market, inventario y todos los artículos comprados con dinero real.\nDuración\nPermanente.\nUna flota de bots automatizados, para gestionar grandes volúmenes\n\n694,673 conjuntos completos disponibles en stock público repartidos entre 91 bots\n\nConducta\nEjecutar scripts automatizados sin interfaz de usuario en miles de cuentas al mismo tiempo para inactivar tarjetas, crear insignias en masa e intercambiar colecciones a escala industrial.\nPruebas presentadas\nDirectorios de bots publicados abiertamente (steam.supply, SteamLvlUp) y grupos públicos con millones de miembros.\nAviso\nSin intervención alguna. 88.97% no están sujetos a ningún tipo de prohibición; 99.8% de las prohibiciones restantes son de carácter meramente estético.\nRecurso\nNo es necesario. Las flotas operan de forma ininterrumpida a lo largo de ciclos de vida de varios años sin interrupciones.\nEntrada\n—\nAlcance\nIntercambio de inventario sin restricciones, subida de nivel de insignias y liquidez del mercado.\nBeneficio de Valve\n$26.8M+ en el gasto mínimo en la tienda ($5.00 de acceso por cuenta) más 15% de descuentos por transacciones en el Mercado Comunitario.\nLa pregunta que esto plantea, dicho sin rodeos\n\nUn cliente particular que intercambie tarjetas u objetos de forma manual se enfrenta a una suspensión permanente e inapelable en virtud del artículo 4.C (automatización) o del artículo 2.G (uso comercial). Una red automatizada de «farming» que utiliza bots sin interfaz de usuario en miles de cuentas opera abiertamente con una tasa de cuentas intactas del 88.97%. Valve es el beneficiario de ambos.\n\nLa asimetría es de carácter económico: los comerciantes individuales obtienen beneficios de la plataforma, mientras que las flotas de tarjetas automatizadas inyectan millones en la pasarela de pago de Valve ($5.00 por cuenta) y alimentan las comisiones por transacción en cada reventa. La aplicación de las normas no se rige por el reglamento escrito, sino por el modelo de ingresos.\n\n08 — Gobernanza\n¿Quién regula el mercado de las cartas?\n\nLa conclusión recurrente de este informe —que la capa de terceros que rodea a Steam está formada por personal procedente del interior de Steam— también se cumple en la economía de las tarjetas, y conduce a una conclusión concreta: nadie independiente puede evaluar qué efectos tiene realmente la aplicación de las normas por parte de Valve, ya que la parte capaz de evaluarlo se encuentra dentro de esa capa. Todos los datos que se exponen a continuación se han extraído del propio grupo público y de las páginas de perfil de Valve en 2026-09-22, y cualquiera puede reproducirlos en un navegador.\n\nUn empleado de Valve modera el grupo más grande dedicado al intercambio de cromos Valve empleado\n\nCardTrades ↗ Se describe a sí mismo en su propia cabecera como el «Steam Grupo oficial de intercambio de tarjetas» y lleva 97,114 miembros. Sus moderadores registrados —las cuentas que controlan dicho grupo— son Mickmane, SgtFopper y afarnsworth ↗.\n\nEse último perfil aparece marcado, según el propio código de la web de Valve, como un empleado Valve; la página incluye class=\"profile_header_valve_employee\" — indica que su ubicación es Bellevue, Washington, y pertenece a la Valve, Steam y Steam Grupo de cromos grupos. SteamID64 76561197960434622, miembro desde el 12 de septiembre de 2003.\n\nSe trata de una observación de carácter estructural, no personal, y es no Un aspecto a tener en cuenta: el moderador de un grupo de intercambio de cartas no está utilizando un bot, y nada aquí sugiere lo contrario. La cuestión es la cláusula que figura en sección 07. Steam Card Exchange es un servicio de tarjetas comerciales de terceros; el intercambio de tarjetas a través de servicios de terceros es precisamente la conducta por la que Valve bloquea de forma permanente las cuentas ordinarias en virtud de «utilizados con fines comerciales en función de las operaciones bursátiles, los informes de la comunidad y otros factores». Un empleado Valve ocupa un puesto de moderador oficial en el grupo comunitario oficial de ese servicio, que cuenta con noventa y siete mil miembros.\n\nEn este contexto no se formula ninguna acusación de conducta indebida contra ninguna persona., y no se extrae ninguna conclusión sobre en qué consiste esa función. La asimetría es la conclusión: cuando una cuenta ordinaria recurre a un servicio de tarjetas o de «skins» de terceros, la respuesta es un ticket cerrado y un bloqueo permanente sin que se muestre ninguna prueba; cuando el servicio es este, un empleado Valve figura en la lista de moderadores y el acuerdo es visible en una página Valve que el propio servicio publica. Lo que se pide es lo mismo que se pide en el resto de este expediente: que se presente la autorización por escrito, si existe; y si no se necesita ninguna, que se indique por escrito, ya que a ocho personas de la sección 06 se les dijo lo contrario.\n\nLa capa de la lista de prohibiciones y quién la gestiona Moderador voluntarioServicio de terceros\n\nGrupo de Steambans.com (archivado) ↗ (en directo ↗ archivado 2025-12-03 ↗) recoge su linaje en la descripción del grupo que se conserva: «El grupo oficial de la comunidad de Steambans.com Steam. SteamBans.com es un servicio totalmente nuevo basado en un concepto ya conocido. Las listas de bloqueos globales llevan años activas en el antiguo programa WONID de VALVe. Cuando se produjo el cambio a STEAMID, nos pareció natural desarrollar un servicio especialmente pensado para este nuevo sistema. Pero también queríamos más. *. Página de archivo de Steambans, que cerró en 2013.» Entre sus administradores figuran: devicenull y killahinstinct_ ↗.\n\nEsa cuenta de administrador es no un empleado «a Valve» —no figura como empleado—. Se trata de un voluntario con una posición excepcionalmente destacada: un miembro de Moderadores de la comunidad (414 miembros, descrito como un grupo «Creado por los moderadores de la comunidad de Steam»), de Coordinadores de la wiki, de Steam Mercado comunitario, y de los grupos del programa Valve y de prelanzamiento, entre los que se incluyen Valve Cartera de proyectos, Steam Versión beta para clientes, Autenticación móvil (versión beta), Nueva versión beta comunitaria Steam, Steam Laboratorios, Steamworks y Denunciar direcciones URL fraudulentas. SteamID64 76561197960794555.\n\nTambién dentro de ese círculo y mostrando a Steambans directamente en la lista de miembros de su grupo público: msart ↗ (Lista de grupos ↗), SteamID64 76561197977933359, cuyo perfil dice, en sus propias palabras: «Dirijo steamid.uk y muchas otras páginas web relacionadas o no con Steam»., y que gestiona una red interconectada de dieciséis grupos — SteamIDcouk (grupo principal «Página web de Sid»), SidAdmins, SidBans, steamideu, Steam3ID, s-id y SArchive entre ellos.\n\nLa propia página web steamid.uk indica esa misma cifra. En su sección de preguntas frecuentes: «¿Quién creó SteamID? La página web de SteamID, la infraestructura de red y los sistemas de seguridad están gestionados por 76561197977933359». Dos respuestas más abajo se indica de dónde proceden los datos: «SteamID utiliza principalmente la API web Steam para la recopilación de datos». En esa misma página se describen varios servidores dedicados en diferentes proveedores de alojamiento, servidores de desarrollo, almacenamiento y búsqueda de texto externos, así como una instalación independiente para copias de seguridad.\n\nVerificado a través de registros conservados en el Internet Archive: el Resumen del grupo Steambans a 3 de diciembre de 2025 ↗, el Resumen del perfil del operador a fecha de 14 de septiembre de 2024 ↗, y el Resumen de las preguntas frecuentes de steamid.uk a 1 de abril de 2026 ↗, datos coincidentes leídos directamente en 2026-09-22.\n\nEn resumen, esto es lo que significa y lo que no\n\nLas listas de bloqueo, la resolución de SteamID y el intercambio de tarjetas son los tres servicios que determinan en quién se confía, quién es identificable y cuál es el valor de un artículo. Ninguno de los tres está gestionado por Valve. En cada uno de ellos, las personas que manejaban los mandos procedían del interior de la órbita de Valve: un empleado marcado con Valve en la lista de moderadores del grupo oficial del servicio de tarjetas; un moderador de la comunidad con amplia experiencia Valve, con acceso al programa previo al lanzamiento, que administra el grupo de la lista de bloqueados; el servicio de resolución de identidades gestionado por un particular que forma parte del mismo círculo. Tres servicios, tres niveles de control, tres personas Valve a las que ya se les había otorgado autoridad.\n\nPertenecer al grupo no equivale a tener una relación laboral, y nada de esto constituye una acusación. Es un hecho de gobernanza, y es la razón por la que la defensa habitual — Se trata de terceros, no podemos controlarlos — debe someterse a prueba en lugar de aceptarse sin más. Las personas que están a los mandos no son ajenas a Valve. Valve está en condiciones de decir qué les pidió, si es que les pidió algo; nadie de fuera está en condiciones de averiguarlo.\n\nNadie cuenta. Esa es la conclusión.\n\nEl espacio de identificación Steam es un rango contiguo de números enteros. Recorrerlo e informar de cuántas cuentas están bloqueadas, cuántas tienen restricciones y cuánto inventario hay sujeto a una prohibición de intercambio no es un programa de investigación: es un bucle y una clave API. Valve proporciona esa clave directamente, en steamcommunity.com/dev/apikey. Y, sin embargo, Ninguna entidad independiente publica ese censo. Ni un organismo regulador, ni un periodista, ni un académico, ni una organización de consumidores. Las únicas cifras públicas sobre el alcance de las medidas de control en Steam son las que Valve decide mencionar.\n\nLa capacidad no falta. Se mantiene. El servicio que resuelve e indexa el espacio de identificadores a gran escala —steamid.uk— indica en su propia sección de preguntas frecuentes que «utiliza principalmente la API web Steam para la recopilación de datos» y lo ejecuta en varios servidores dedicados, almacenamiento externo, máquinas de búsqueda de texto y una instalación de copias de seguridad independiente. Lo gestiona un particular. Su grupo hermano de la lista de bloqueados está coadministrado por un moderador de la comunidad Valve con amplia experiencia, que tiene acceso a los programas de prelanzamiento de Valve. La única parte que está en condiciones de publicar el recuento se encuentra dentro de la órbita de Valve, y no lo publica.\n\nEsta es la misma estructura que el informe detecta en todos los demás ámbitos. Todos los servicios que toman decisiones fundamentales sobre la economía Steam —en quién se confía, quién es identificable, cuál es el valor de un artículo, a quién se excluye— son, en teoría, de terceros y, en la práctica, están muy próximos a Valve. Steam El intercambio de tarjetas no es una excepción a ese patrón; es otro ejemplo del mismo. El argumento de que se trata de operadores independientes puede esgrimirse en el caso de Valve precisamente porque nadie ha podido comprobarlo nunca con ningún número.\n\nCenso de cuentas de 10,88 millones: 88.97% Sin modificar\n\nSe auditó la base instalada de ArchiSteamFarm en Valve GetPlayerBans punto final (10,880,610 cuentas, 55 minutos). Solo el subconjunto no limitado representa $26.8M+ en el gasto mínimo en la tienda (umbral de entrada de $5.00). Las cuentas 9,680,599 (88.97%) no tienen ningún tipo de restricción., y 99.8% del resto solo imponen sanciones comunitarias meramente simbólicas que permiten que el trading automatizado siga activo.\n\n5,360,499Miembros de ASF sin restricciones (número mostrado de Steam)\n10,880,610Total de entradas de API analizadas (con y sin restricciones)\n9,680,599Nunca ha sido bloqueado (88.97%)\n1,200,011Llevar cualquier prohibición Steam (11.0%) — 99.8% cosmético\n55 minPara realizar un censo de toda la población, un factor clave\nPruebas forenses y censo exhaustivo\n\nEl desglose demográfico detallado —que incluye gráficos de distribución por tipo de suspensión, antigüedad de las cuentas en el momento de la aplicación de la medida, grupos por año de creación (2020-2026) y datos geográficos facilitados por los propios usuarios— se publica en el estudio censal específico.\n\nAbrir el censo completo de las prohibiciones (10,88 M) (Anexo VI) →Sección 4 — El apagón del identificador de activos →\n\nAsí pues, la pregunta que hay que plantearse, y a la que solo Valve puede responder, es: qué identificador o capacidad se retiró, en qué fecha, por decisión de quién y qué efecto cuantificable tuvo en los operadores a los que iba dirigido — frente a su repercusión en todas las personas que, desde fuera, intentaban realizar el recuento. Un cambio que pone fin a la auditoría independiente no deja de ser controvertido por el mero hecho de que se haya anunciado como una medida de seguridad. Esa es la razón por la que el censo del bloque anterior no existe.\n\n09 — Método y límites\nLo que se leyó y lo que no se alega\n\nTodas las citas de esta página se han extraído de la fuente en tiempo real de 2026-09-22 y se han reproducido textualmente. Nada de lo que aquí aparece procede de un rastreo, de credenciales de un mercado o de un conjunto de datos privado.\n\nLos cuatro conjuntos de datos y los cálculos realizados con ellos\n\nCada una de ellas es una única solicitud pública, reproducible desde un terminal. No se utilizó ninguna cuenta, no se inició sesión en ningún mercado y no se llamó a ningún punto final que requiriera credenciales.\n\nConjunto de datos\tDe dónde viene\t¿Qué se calculó a partir de ello?\nCenso de tarjetas\n13,876 partidos\tSteam La lista de precios de insignias publicada por Card Exchange, la misma fuente de datos que genera su página de precios para el público ↗ archivado 2026-08-04 ↗\tJuegos que emiten cartas, cartas por colección, tipos distintos de cartas y el precio de mercado de cada colección completa. Las medianas y el total $23,586.57 constituyen los datos aritméticos de este estudio.\nPrecios de los videojuegos\n13,713 resuelto\tEl punto final de la tienda pública de Valve, store.steampowered.com/api/appdetails, cc=us, solo el campo de precio, por lotes\tMediana y distribución del precio de catálogo de un juego de cartas; número de juegos en los que las expansiones se venden más que el juego en sí.\nExistencias de robots\n91 bots, 694,673 conjuntos\tEl directorio público de bots de cartas en steam.supply/CardBots ↗, tal y como aparece, sin necesidad de iniciar sesión\tTotal de conjuntos en stock, el número mínimo de tarjetas, el límite mínimo de bajas y el límite mínimo de asignación por bot en cuentas distintas.\nVerificación cruzada\n21 bots compartidos\tsteamlvlup.net/cardbots ↗ archivado 2026-02-10 ↗, un directorio independiente de esos mismos bots\tSolo a efectos de verificación. En los 21 bots que figuran en ambas listas, Aggregate Stock se compromete a 0.03%; la mayor discrepancia entre un único bot es 1.36%, lo que concuerda con dos recopilaciones de inventario en tiempo real realizadas con unos minutos de diferencia.\n\nAtribución, tal y como exige el segundo directorio: datos facilitados por SteamLvlUp, bajo licencia CC BY 4.0 archivado 2026-09-23 ↗; se utiliza aquí únicamente como verificación independiente de las cifras de existencias de un tercero, y se ha modificado en el sentido de que las filas por robot se han agregado y comparado, en lugar de reproducirse. Steam Card Exchange y steam.supply se citan más arriba mediante un enlace. Los precios de los juegos son propios de Valve. Los nombres e imágenes de las cartas, los juegos y las colecciones pertenecen a Valve o a los editores, y se reproducen sin reclamación ni licencia alguna, a título de datos sobre el mercado.\n\nNo se realizaron dos mediciones previstas y no se han sustituido por otras. Los propios criterios de valoración del «Community Market» de Steam — resumen de precios, buscar/mostrar, historial de precios — no devuelve ningún dato al servidor que los recopila, y Steam las páginas de debate de la comunidad le devuelven un código HTTP 403, por lo que ninguna cifra de esta página procede de datos en tiempo real del Mercado. El método de volumen de ventas, que habría contabilizado las apariciones de cartas en el reinicio diario, requiere una sesión Steam con inicio de sesión; El manifiesto de esta investigación indica que no se utilizó ninguna credencial del mercado, y esa afirmación se mantuvo. El nivel mínimo de existencias de bot es aquel que se puede medir sin necesidad de uno.\n\nFuentes primarias\n\nSteam Contrato de suscripción ↗ archivado 2026-09-24 ↗ — § 2.A, § 2.G, § 3.D, § 4.C, § 4.D.\nSteam Asistencia técnica — Cuentas de usuario limitadas ↗ — el umbral $5.00 y la lista de características restringidas.\nValve — Steam Preguntas frecuentes sobre las cartas coleccionables ↗ — la mecánica de los botines y la tarifa de juego gratuito $9.\nArchiSteamFarm Preguntas frecuentes ↗ y debate n.º 3440 ↗.\nSteam Páginas de grupos y perfiles de la comunidad, de lectura directa, para la sección 08.\nPreguntas frecuentes de steamid.uk, instantánea de Internet Archive 2026-04-01 ↗.\nOcho Steam Avisos sobre el bloqueo de la asistencia publicados por sus destinatarios, 2020-2026, que figuran con sus enlaces en la sección 06.\n\nLo que no se reivindica\n\nNo se ha estimado ninguna cifra de ingresos para Valve procedente del «card farming». No se ha facilitado ningún recuento de cuentas activas para ninguna herramienta, y las 1,39 millones de asignaciones de «drop» son no un recuento de las cuentas propiedad de granjas —véase la nota de la sección 02—. No se acusa a ninguna persona de haber cometido ninguna irregularidad; cuando se menciona a alguien, se hace utilizando su propio nombre de usuario público Steam, en su propia función pública, a partir de una página que Valve publica. No se afirma que ninguna de las ocho cuentas bloqueadas de la sección 06 sea inocente o culpable; la conclusión se refiere a la carta, no a la cuenta. Las cifras de pérdidas de los operadores de la sección 02 proceden de informes propios y se indican como tales en la nota de origen. La sección de preguntas frecuentes (FAQ) de steamid.uk se ha extraído de una instantánea del Internet Archive, ya que la página activa está protegida por un sistema de verificación contra bots. No se afirma que se haya intentado realizar ningún censo de bloqueos y que este haya sido ocultado; la conclusión es únicamente que no se ha publicado ninguno. La curva de nivel Steam por encima de 667 no está modelizada.\n\nPor qué la herramienta no es el tema\n\nArchiSteamFarm afirma que «no está autorizado por Valve» y no se le acusa de nada en esta página. Se utiliza como instrumento de medición, porque es la única parte de esta economía que documenta los mecanismos de forma pública y por escrito. Valve puede resumir todo el asunto en un solo párrafo: publicar qué automatización comercial autoriza y el registro por operador de lo que hizo con respecto al resto.\n\nSiguiente: cómo se valora el propio mercado → · la escala de precios y el límite máximo de cotización → · los artículos Steam no se transportarán →",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Una granja de bots no es una fuga en la tienda de Valve. Es una cliente."
          },
          {
            "level": 2,
            "id": null,
            "text": "Qué es realmente una granja, paso a paso"
          },
          {
            "level": 3,
            "id": null,
            "text": "Comprar en"
          },
          {
            "level": 3,
            "id": null,
            "text": "Comprar juegos"
          },
          {
            "level": 3,
            "id": null,
            "text": "Inactivo\nLa herramienta inicia sesión en la red Steam de forma automática, «analiza tus insignias», crea la lista de títulos que se pueden cultivar y comienza «Jugar a los juegos que cumplen los requisitos y comprobar periódicamente si ya se ha completado la partida». Descripción del mecanismo por parte de su responsable: es «No hace más que indicar a Steam que estamos jugando a un juego determinado»."
          },
          {
            "level": 3,
            "id": null,
            "text": "Se acaban las gotas\nCada título es finito. «Cada juego tiene un número fijo de cartas que se pueden obtener. Una vez que las hayas conseguido todas (aproximadamente la mitad del conjunto completo), el juego ya no es una opción para seguir farmando». Una granja que quiera seguir produciendo tiene que seguir comprando títulos. El suministro de cartas se ve limitado por las compras —por diseño, y en beneficio de Valve."
          },
          {
            "level": 3,
            "id": null,
            "text": "Retirar dinero\nLa tarjeta sale por una de estas tres vías: se vende en el Mercado de la Comunidad, se intercambia o se tritura para convertirla en gemas. Cada una de ellas constituye una transacción en el Mercado de Suscripciones o un intercambio, y el apartado § 3.D reserva el cobro: «Valve podrá cobrar una comisión por las transacciones realizadas en un mercado de suscripciones». Este es el paso que hace que todo ello constituya una infracción; véase 05."
          },
          {
            "level": 2,
            "id": null,
            "text": "Antes de que una explotación agrícola gane un céntimo, ya ha pagado Valve"
          },
          {
            "level": 3,
            "id": null,
            "text": "El tamaño real del artículo que se va a comprar"
          },
          {
            "level": 3,
            "id": null,
            "text": "¿Qué tamaño tiene un conjunto?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Cuánto cuesta la licencia"
          },
          {
            "level": 3,
            "id": null,
            "text": "Lo que devuelve el conjunto final"
          },
          {
            "level": 3,
            "id": null,
            "text": "Dónde se encuentran los conjuntos 694,673"
          },
          {
            "level": 3,
            "id": null,
            "text": "Lo que dice y lo que no dice este suelo"
          },
          {
            "level": 3,
            "id": null,
            "text": "Y la agricultura no es rentable con los precios de Valve."
          },
          {
            "level": 3,
            "id": null,
            "text": "Lo que realmente sustenta la granja"
          },
          {
            "level": 4,
            "id": null,
            "text": "Ventas de videojuegos"
          },
          {
            "level": 4,
            "id": null,
            "text": "«En línea» y tiempo de juego"
          },
          {
            "level": 4,
            "id": null,
            "text": "Inscripciones"
          },
          {
            "level": 4,
            "id": null,
            "text": "Dinero en el monedero y comisiones"
          },
          {
            "level": 4,
            "id": null,
            "text": "Relaciones públicas de nivel Steam"
          },
          {
            "level": 3,
            "id": null,
            "text": "Y el propio cobro supone una pérdida de valor: Valve impuestos por partida doble"
          },
          {
            "level": 3,
            "id": null,
            "text": "No se trata de un momento puntual. Es un sector con una trayectoria de varios años."
          },
          {
            "level": 3,
            "id": null,
            "text": "Conjuntos completos de cartas almacenados en el directorio público de bots, por Steam venta"
          },
          {
            "level": 3,
            "id": null,
            "text": "Así es como se ve la escala de insignias de ventas desde lo más alto"
          },
          {
            "level": 3,
            "id": null,
            "text": "Y esa misma flota sigue ahí cuando no hay ninguna oferta en marcha"
          },
          {
            "level": 3,
            "id": null,
            "text": "El directorio de reposo, bot por bot"
          },
          {
            "level": 2,
            "id": null,
            "text": "El otro producto es el número que aparece junto a tu nombre"
          },
          {
            "level": 3,
            "id": null,
            "text": "Conjuntos completos consumidos, del nivel 1 al 1,000"
          },
          {
            "level": 3,
            "id": null,
            "text": "¿Cómo se comprobó la curva, ya que Valve no la publica?"
          },
          {
            "level": 2,
            "id": null,
            "text": "La cláusula no se refiere a la agricultura de forma vaga. La enumera."
          },
          {
            "level": 3,
            "id": null,
            "text": "«…la hora de jugar»"
          },
          {
            "level": 3,
            "id": null,
            "text": "«…sin una aportación real por parte de los usuarios»"
          },
          {
            "level": 2,
            "id": null,
            "text": "Cada salida desde una sala de juego es una salida que la licencia prohíbe, y Valve cobra una tarifa en la puerta."
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 2.A — la licencia"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 2.G — la restricción"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 3.D — la tasa"
          },
          {
            "level": 3,
            "id": null,
            "text": "Si se leen los tres juntos, la posición se cierra."
          },
          {
            "level": 3,
            "id": "fee-ladder",
            "text": "La tarifa en esa puerta no es de 15%. En una tarjeta de cultivo alcanza dos tercios."
          },
          {
            "level": 3,
            "id": null,
            "text": "Comisión efectiva en una venta en el mercado comunitario, según el precio de venta solicitado por el vendedor"
          },
          {
            "level": 2,
            "id": null,
            "text": "Sin previo aviso, por oleadas, y se propaga a través del número de teléfono"
          },
          {
            "level": 3,
            "id": null,
            "text": "Caso 4 — Junio de 2025, VAC prohibiciones sobre el CS2 inactivo"
          },
          {
            "level": 3,
            "id": null,
            "text": "Cómo se cierra una cuenta principal"
          },
          {
            "level": 3,
            "id": null,
            "text": "El mismo párrafo, con cinco años de diferencia, de tres agentes distintos"
          },
          {
            "level": 3,
            "id": null,
            "text": "Nota sobre el abastecimiento: pérdidas a escala de operador"
          },
          {
            "level": 2,
            "id": null,
            "text": "Los dos lados del mismo escritorio"
          },
          {
            "level": 3,
            "id": null,
            "text": "Un cliente, para operaciones bursátiles"
          },
          {
            "level": 3,
            "id": null,
            "text": "Una flota de bots automatizados, para gestionar grandes volúmenes"
          },
          {
            "level": 3,
            "id": null,
            "text": "La pregunta que esto plantea, dicho sin rodeos"
          },
          {
            "level": 2,
            "id": null,
            "text": "¿Quién regula el mercado de las cartas?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Un empleado de Valve modera el grupo más grande dedicado al intercambio de cromos Valve empleado"
          },
          {
            "level": 3,
            "id": null,
            "text": "La capa de la lista de prohibiciones y quién la gestiona Moderador voluntario Servicio de terceros"
          },
          {
            "level": 3,
            "id": null,
            "text": "En resumen, esto es lo que significa y lo que no"
          },
          {
            "level": 3,
            "id": null,
            "text": "Nadie cuenta. Esa es la conclusión."
          },
          {
            "level": 3,
            "id": null,
            "text": "Censo de cuentas de 10,88 millones: 88.97% Sin modificar"
          },
          {
            "level": 3,
            "id": null,
            "text": "Pruebas forenses y censo exhaustivo"
          },
          {
            "level": 2,
            "id": null,
            "text": "Lo que se leyó y lo que no se alega"
          },
          {
            "level": 3,
            "id": null,
            "text": "Los cuatro conjuntos de datos y los cálculos realizados con ellos"
          },
          {
            "level": 3,
            "id": null,
            "text": "Fuentes primarias"
          },
          {
            "level": 3,
            "id": null,
            "text": "Lo que no se reivindica"
          },
          {
            "level": 3,
            "id": null,
            "text": "Por qué la herramienta no es el tema"
          }
        ],
        "links": [
          "https://help.steampowered.com/en/faqs/view/71D3-35C2-AD96-AA3A",
          "https://github.com/JustArchiNET/ArchiSteamFarm/wiki/FAQ",
          "https://steamcommunity.com/tradingcards/faq/",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260924114457/https://store.steampowered.com/subscriber_agreement/",
          "https://steamladder.com/ladder/badges/2861690/",
          "http://web.archive.org/web/20260716205303/https://steamladder.com/ladder/badges/2861690/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/farm-economy-timeline.json",
          "https://store.steampowered.com/charts/",
          "http://web.archive.org/web/20260923183013/https://store.steampowered.com/charts/",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://github.com/JustArchiNET/ArchiSteamFarm/discussions/3440",
          "https://x.com/gergelyszabo94/status/1311004678633795585",
          "https://x.com/prcs25/status/1811893857253982720",
          "http://web.archive.org/web/20240715122902/https://x.com/prcs25/status/1811893857253982720",
          "https://reddit.com/r/steamsupport/comments/1fjmgc5/what_to_do_when_your_steam_account_gets_hacked/mkelm2y/",
          "https://www.reddit.com/r/csgomarketforum/comments/r87owv/psa_my_steam_account_just_got_banned/",
          "http://web.archive.org/web/20250327203008/https://www.reddit.com/r/csgomarketforum/comments/r87owv/psa_my_steam_account_just_got_banned/",
          "https://www.reddit.com/r/GlobalOffensiveTrade/comments/r9xql9/d_recently_received_commercial_ban_for_what_seems/",
          "http://web.archive.org/web/20211206034804/https://www.reddit.com/r/GlobalOffensiveTrade/comments/r9xql9/d_recently_received_commercial_ban_for_what_seems/",
          "https://www.reddit.com/r/csgomarketforum/comments/1hhxx7m/d_permanently_locked_on_steam_for_commercial_use/",
          "http://web.archive.org/web/20250627014045/https://www.reddit.com/r/csgomarketforum/comments/1hhxx7m/d_permanently_locked_on_steam_for_commercial_use/",
          "https://www.reddit.com/r/steamsupport/comments/1hkctwt/permanent_ban_with_no_explanation/",
          "https://www.reddit.com/r/pcgaming/comments/1vf24lu/warning_to_all_gamersexpats_steam_took_my_money/",
          "https://steamcommunity.com/groups/card-trading-card-trades",
          "https://steamcommunity.com/id/afarnsworth",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/groups/steambans",
          "https://steamcommunity.com/groups/steambans",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/id/killahinstinct_",
          "https://web.archive.org/web/20240914124859/https://steamcommunity.com/id/msart",
          "https://steamcommunity.com/id/msart/groups/",
          "http://web.archive.org/web/20260401154714/https://steamid.uk/faq/",
          "https://phishdestroy.io/steam_dossier/es/enforcement_audit.html",
          "https://phishdestroy.io/steam_dossier/es/#evidence-blackout",
          "https://www.steamcardexchange.net/index.php?badgeprices",
          "http://web.archive.org/web/20260804200309/https://www.steamcardexchange.net/index.php?badgeprices",
          "https://steam.supply/CardBots",
          "https://steamlvlup.net/cardbots",
          "http://web.archive.org/web/20260210171205/https://steamlvlup.net/cardbots",
          "https://steamlvlup.net/",
          "https://creativecommons.org/licenses/by/4.0/",
          "http://web.archive.org/web/20260923221628/https://creativecommons.org/licenses/by/4.0/",
          "https://phishdestroy.io/steam_dossier/es/market_economics.html",
          "https://phishdestroy.io/steam_dossier/es/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/es/elite_skins.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/es/card_economy.content.json",
      "export_json_sha256": "dcd3d24cfe6649b59026854d1094e45264d2bf6ac292109e18edfd0c9fd062bd"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "es/elite_skins.html",
      "language": "es",
      "title": "Un producto, dos sistemas de precios — El dossier «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/es/elite_skins",
      "source_html_sha256": "265c985aae47e9bfe28a76ae449ade9246176c9b964f473790ac967a85fe3c58",
      "exported_at": "2026-09-29T00:17:19.964Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "register",
            "source": "https://phishdestroy.io/steam_dossier/es/elite_skins#register"
          },
          {
            "id": "",
            "source": "https://phishdestroy.io/steam_dossier/es/elite_skins#selected"
          }
        ],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "elite_skins.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/es/elite_skins.pdf?v=print-20260929-v5",
        "sha256": "ebfbd790645110c5525cdfee04b9289711fce92ce550fff007971e81aaff0712",
        "bytes": 95482,
        "pages": 7
      },
      "integrity": {
        "signed_object": "elite_skins.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "elite_skins.content.json.asc",
        "digest_file": "elite_skins.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify elite_skins.content.json.asc elite_skins.content.json",
          "sha256sum -c elite_skins.content.json.sha256"
        ]
      },
      "content": {
        "text": "ANEXO IV / ARQUITECTURA DEL MERCADO / 20 SEPTIEMBRE DE 2026\nRegistro en Elite Skins — El techo del mercado de $1,800\n\nUn artículo. Dos sistemas de precios.\n\nLO QUE DEMUESTRA ESTA SECCIÓN\n\nEste registro establece un censo empírico de todas las categorías de skins de CS2 cuyo precio supera el límite máximo de puja de $1,800 del Mercado Comunitario de Steam en cinco plataformas externas. Demuestra que 248 las categorías de alto nivel —que representan 18,394 anuncios activos y $78.6 millones en liquidez publicada— están 100% ausentes del mercado oficial de Valve. Los vendedores que buscan precios reales de mercado se ven estructuralmente obligados a recurrir a plataformas externas, al tiempo que dependen exclusivamente de Steam de los mecanismos comerciales subyacentes.\n\nWhat this means — the Community Market listing ceiling\n\nSteam’s own market refuses a listing above roughly $1,800. A seller may ask less, never more. Items whose market price sits above that line therefore cannot be sold at that price on Steam at all — which is the mechanism that moves those sales to third-party venues while the item itself never leaves Valve’s inventory system.\n\nSection 13 — the off-Steam price gap →\n\n← Volver al informe ejecutivo\n\nSteam fija el precio máximo de un anuncio en Community Market en unos $1,800.. En los cinco mercados de terceros cuyos precios se recogen en este resumen, 419 Las categorías de artículos de CS2 tienen un precio de venta más barato en tiempo real por encima de ese límite, y 402 de ellas, 95.9%,, no tienen ningún anuncio en Steam. Entre todos poseen ejemplares que figuran en la lista de 18,641 y cuyo valor asciende al menos a $82.4 millones. Para que un precio sea válido, es necesario que un segundo mercado lo apruebe, 248 De esas categorías, todas ellas —y en cada una de ellas, «100%,»— no aparece en «Steam». «The dearest» es una pegatina | Titan (Holo) | Katowice 2014 en $66,285, cotizada por cuatro mercados situados a una distancia de 5.2% entre sí y que no figura en ninguno de los de Valve. La tabla completa, las representaciones y la clasificación se encuentran en el atlas de escalera de precios.\n\nRevisa todas las entradas de «419» ↓Abrir el atlas ↗Lee el método\n248categorías en las que el precio en dos o más mercados supera el límite máximo\n18,394ejemplares disponibles en cinco plataformas de venta\n$78.6Mvalor mínimo de esos anuncios\n100%de los cuales no aparecen en absoluto en Steam\n\nCorrección: en esta página aparecía anteriormente un precio sin confirmar.\n\nUna versión anterior de esta página incluía un artículo titulado «Souvenir AK-47» | «Point Disarray», cuyo precio de venta era de $148,954 en un mercado, mientras que Steam lo ofrecía a $119. Esa entrada se refiere a un único ejemplar en una sola estantería, sin que ningún otro mercado coincida con el precio, por lo que se trata de un precio de venta y no de un precio de mercado, y ya no aparece en la página. Todas las cifras destacadas aquí se limitan ahora a las categorías 248 en las que al menos dos mercados fijan de forma independiente un precio superior al límite máximo. La entrada en sí no se ha eliminado —sigue figurando en el registro más abajo— y la clasificación que la ha rebajado se detalla íntegramente en el atlas de escalera de precios.\n\n01 / el dinero de las órdenes de compra activas\nEl umbral mínimo cuantificable en dólares\n\nRecalculado a partir de la instantánea autorizada de cs2.sh en cinco mercados. Se trata de un valor mínimo agregado de venta en un subconjunto definido, no del volumen de ventas ni de una valoración de la economía de CS2.\n\n248 CATEGORÍAS VERIFICADAS · 18,394 COPIAS A LA VENTA · 5 MERCADOS$78.62M\n\nPrecio mínimo agregado de venta publicado de cada artículo CS2 para el que dos o más mercados fijen de forma independiente un precio superior al límite que Valve permite en su propio mercado.\n\nPor qué se trata de un mínimo y no de una estimación\n\nPara cada mercado, multiplicamos su más bajo Solicita un artículo por el número de ejemplares que aparece en la plataforma de venta. Todos los demás ejemplares de esa estantería tienen un precio igual o superior al precio de venta más bajo, por lo que el valor real anunciado es más alto —por definición, no por conjeturas—. No se trata de una venta, ni de un flujo de caja, ni de una valoración de todo el mercado, y el mismo artículo físico puede aparecer en más de una plataforma de venta.\n\nComprobar todas las filas de origen de «419» ↗\n★ Guantes deportivos | Hedge Maze (probados en la práctica)\n$4.68M\nAWP | Gungnir (nuevo de fábrica)\n$4.46M\nAWP | Dragon Lore (nuevo de fábrica)\n$4.34M\n★ Cuchillo mariposa | Fade (nuevo de fábrica)\n$4.17M\nAK-47| Wild Lotus (nuevo de fábrica)\n$4.16M\n★ Cuchillo mariposa | Doppler (nuevo de fábrica)\n$3.64M\n\nLas barras muestran las seis mayores aportaciones a nivel de categoría al cálculo del precio mínimo, en proporción a la mayor de ellas. Una barra alta refleja tanto el precio de venta más barato como el número de ejemplares disponibles. Un mismo artículo físico puede aparecer en más de un mercado, por lo que estas cifras no deben sumarse al total de ningún otro mercado.\n\n02 / ejemplos que se pueden examinar\nLo que el límite no tiene en cuenta\n\nLas ilustraciones corresponden a los nombres exactos de los artículos, siempre que estén disponibles. Los precios son los precios de venta vigentes que figuran en el catálogo de la fecha indicada, no registros de transacciones.\n\n★ Butterfly Knife | Doppler (Factory New)\n\nFuente: https://phishdestroy.io/steam_dossier/es/elite_skins#selected\n\nLa brecha cuantificable: Estas ofertas no pueden igualarse con un anuncio de Steam por el mismo importe en dólares estadounidenses. El propio Valve… Preguntas frecuentes sobre el mercado comunitario archivado en 2026-09-21 ↗ establece un precio máximo de venta de aproximadamente $1,800. Un vendedor podría seguir fijando un precio inferior a ese; que eso resulte aceptable o no es decisión del vendedor. Otro Búsqueda en CSMarketCap de artículos por encima de $1,800 ↗ Muestra los productos «Factory New Dragon Lore» en los mercados indexados por 28, con unas 1.1K ofertas publicadas; el inventario duplicado puede contabilizarse más de una vez.\n\n03 / la dependencia estructural\nEl límite de Steam hace que la determinación de precios se desvíe de Steam\n\nLa comparación es de carácter estructural. No da por sentado que todos los precios de venta sean justos ni considera los anuncios sin vender como ingresos.\n\n01 · LA NORMA\nSteam cierra la lista\n\nValve afirma que los anuncios de Community Market tienen un límite máximo de aproximadamente $1,800. Además, los saldos de los monederos tienen un límite máximo y los fondos de los monederos no se pueden retirar en efectivo.\n\n02 · LA OBSERVACIÓN\nDragon Lore:10,940.85 dólares\n\nEl catálogo del mercado «5-» muestra 389 ofertas en directo para AWP Dragon Lore (nuevo de fábrica), a partir de10,940.85 dólares (piso de CSFloat). El registro más amplio contiene 248 categorías corroboradas por encima del límite de Steam.\n\n03 · LA CONSECUENCIA\nDesglose del precio y de la transferencia\n\nUn vendedor que busca obtener ese precio más alto No puedo publicarlo en Steam. Los servicios externos pueden fijar el precio al contado, pero la entrega sigue basándose en la titularidad y la transferencia de artículos controladas pSteam.\n\nLa contradicción política: De Valve Contrato de suscripción archivado en 2026-09-21 ↗ se reserva el derecho a la explotación comercial de los servicios de Steam, salvo que se autorice expresamente, mientras que su 2016 declaración archivado en 2026-09-21 ↗ Dichos operadores de juegos de azar ya estaban utilizando un OpenID de Steam y cuentas automatizadas. Esto constituye una prueba directa de que Valve tenía conocimiento de este tipo de operadores externos en 2016.. Sin embargo, el mercado oficial no puede publicar los precios observados de estos artículos de gran valor. Se trata de la dependencia estructural respecto a la determinación de precios y las transacciones en el mercado «off-Steam»; El estado contractual de cada mercado concreto requiere pruebas independientes. Los dos principales mercados occidentales que registran este volumen de transacciones superior a su capacidad operan como entidades corporativas formales en las principales jurisdicciones — CSFloat S.A. (constituida en Delaware, EE. UU.) y Skinport GmbH (inscrita en Stuttgart, Alemania, HRB 764879) — realiza abiertamente transacciones por valor de cientos de millones en ventas de artículos entre particulares, basándose directamente en las API web y la infraestructura comercial de Steam.\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\nLas cuatro filas de $100,000 corresponden al precio máximo de cotización de CSFloat. Están marcadas en el registro y no deben interpretarse como tasaciones. El rastreo de cotizaciones archivadas de CSFloat solo alcanzó aproximadamente $6,999,, por lo que se utiliza la instantánea del catálogo público para el registro completo >$1,800.\n\n04 / otro juego de «Valve»\nEl techo también afecta a Dota 2\n\nLa misma prueba rigurosa de «la oferta más barata» en Skinport muestra las categorías de CS2 en 166 y las de Dota en 3 2. Se trata de una instantánea independiente del mercado; no las añadas a la lista de CSFloat en 245.\n\nDOTA 2 · OFERTA DE 1\nMedia luna heroica y brutal\n\n¿Cuál es el precio más barato de «Skinport»? Pregunta: $14,622.25.\n\nDOTA 2 · OFERTA DE 1\nCapa «Dark Artistry»\n\n¿Cuál es el precio más barato de «Skinport»? Pregunta: $8,255.16.\n\nDOTA 2 · OFERTA DE 1\nEstrella de energía corrompida\n\n¿Cuál es el precio más barato de «Skinport»? Pregunta: $2,087.92.\n\nEstas son tres categorías de objetos que aparecen en la lista, no todos los objetos de Dota 2 que existen. Revisa las filas con fecha «Skinport» ↗ y API documentación ↗.\n\n05 / robustez\nEl resultado no depende del límite exacto\n\nValve establece el límite máximo en la moneda regional del comprador, por lo que, al convertirlo a dólares estadounidenses, no se obtiene una cifra redonda. Por lo tanto, el recuento se repite en cada umbral plausible. El porcentaje de estos artículos que faltan en Steam nunca desciende por debajo de 95%.\n\nSe ha comprobado el umbral\tCategorías de artículos\tEjemplares disponibles\tValor mínimo\tAusente de Steam\n$1,800\t419\t18,641\t$82,449,526\t95.9%\n$2,000\t382\t15,159\t$75,541,325\t95.5%\n$2,070\t363\t12,336\t$69,560,305\t95.6%\n$2,300\t323\t11,644\t$67,984,432\t95.0%\n$2,500\t299\t10,950\t$66,203,929\t95.0%\n\nLee una fila cada vez; las filas son subconjuntos anidados del mismo censo, no poblaciones independientes. El «valor mínimo» multiplica el valor de cada mercado más bajo se calcula en función del número de ejemplares que figura en la lista, por lo que, por su propia naturaleza, subestima el número de ejemplares disponibles en las estanterías. Abrir el conjunto de datos ↗\n\n06 / escasez que se puede cuantificar\nQué pocos de estos hay realmente a la venta\n\nBUFF divide la estantería de cada artículo en rangos de valor y publica cuántos ejemplares hay en cada uno. De este modo, «raro» deja de ser una simple palabra para convertirse en una cifra, y el precio del estado se calcula por separado del del diseño.\n\n298 LISTA DE EJEMPLARES\nAWP | La leyenda del dragón\n\n8 diferentes variantes con sus respectivos precios. La más cara, AWP de recuerdo | Dragon Lore (nuevo de fábrica), pregunta $12,363 con 20 ejemplares en las estanterías.\n\nEn la sección de flotadores de mejor calidad de la tienda (0–0.01) hay 2 copias, preguntando $17,875 — una prima de «45%» sobre el precio de venta base del artículo, basada únicamente en su estado.\n\n607 LISTA DE EJEMPLARES\nM4A4 | Howl\n\n12 diferentes variantes con sus respectivos precios. La más cara, M4A4 de recuerdo | Howl (nuevo de fábrica), pregunta $14,895 con 2 ejemplares en las estanterías.\n\n213 LISTA DE EJEMPLARES\nAK-47 | Wild Lotus\n\n7 diferentes variantes con sus respectivos precios. La más cara, AK-47, de recuerdo | Wild Lotus (nuevo de fábrica), pregunta $14,895 con 2 ejemplares en las estanterías.\n\n310 LISTA DE EJEMPLARES\nAWP | Gungnir\n\n7 diferentes variantes con sus respectivos precios. La más cara, AWP de recuerdo | Gungnir (desgaste mínimo), pregunta $14,895 con 2 ejemplares en las estanterías.\n\nPor qué es importante para el resto de este dossier: No se trata de abstracciones. En todo el mundo hay unos pocos cientos de ejemplares de cada trofeo disponibles en el mercado abierto, cada uno vinculado a una cuenta de Steam y transferido mediante una transacción de Steam. En un mercado tan reducido, el robo de un solo artículo del inventario constituye un hecho cuantificable, y las técnicas de apropiación de cuentas documentadas en otras partes de esta investigación tienen una recompensa directa y cuantificable.\n\nLas cifras corresponden a los anuncios activos en un mercado en el momento de la recopilación, no al número total existente. Las unidades que se encuentran en inventarios privados no se contabilizan aquí en ningún caso. Abrir el conjunto de datos «float» ↗\n\n07 / la escalera, fuera de la vista\nCuanto más caro es el artículo, más lejos se encuentra de cualquier lugar visible\n\nCada nivel que aparece a continuación corresponde a una categoría probatoria diferente. Se ha optado deliberadamente por no agruparlas en una sola cifra.\n\nPeldaño\tFigura\t¿De qué tipo de hecho se trata?\nCeiling on Valve's own market\t~$1,800\tPublished rule, stated in the Steam Community Market FAQ.\nDearest ask several marketplaces agree on\t$66,285\tMeasured by us in this snapshot. Sticker | Titan (Holo) | Katowice 2014, quoted by four marketplaces within 5.2% of one another. An ask, not a sale.\nDearest ask seen on any single shelf\t$148,954\tOne marketplace, one copy, no second marketplace agreeing — and equal to a round CNY 1,000,000 at the snapshot rate. Listed here as the outer edge of what sellers ask, and relied on for nothing.\nPublic marketplace sale\t$49,999\tSpecialist Gloves | Crimson Kimono (FN) on CSFloat, as reported by SteamAnalyst. Platform-recorded, third-party reported.\nReported private sale\t$400,000\tAK-47 | Case Hardened, reported by PC Gamer in April 2023. Journalism, not a record we hold.\nReported offer, declined\t$1,500,000\tBlue Gem Karambit, pattern #387. No sale took place and the figure has not been independently confirmed. Included to mark the ceiling of the claims, not to assert a value.\n\nEl aspecto estructural: El mercado de Valve se sitúa en torno a los $1,800.. Las plataformas de terceros elevan la cotización hasta unos $66,000, donde coinciden varias de ellas, y hasta aproximadamente $150,000, donde solo coincide una. Por encima de ese nivel no existe ningún mercado: las mayores transferencias de activos emitidos por Valvese realizan de forma privada, entre particulares, sin cotización, sin registro en ninguna plataforma, sin verificación de identidad y sin notificación. La transferencia en sí misma sigue realizándose en Steam. Cuanto mayor sea el valor, menos visible será para los demás, y la infraestructura que lo soporta es íntegrValve.\n\nLos dos últimos puntos se basan en informaciones de terceros, citadas como tales. Este proyecto no las ha verificado y no se basa en ellas para llegar a ninguna conclusión.\n\nTodas las categorías observadas en «419»\n\nFuente: https://phishdestroy.io/steam_dossier/es/elite_skins#register\n\n09 / procedencia y límites\nComprueba el cálculo\n\nMostramos los datos locales y la fuente pública. El dato numérico se refiere a CSFloat en la fecha de captura.\n\nLos límites y condiciones de Valve\n\nSteam Preguntas frecuentes sobre el mercado comunitario ↗ archivado en 2026-09-21 ↗ indica el máximo aproximado de $1,800. El Acuerdo de suscripción ↗ archivado en 2026-09-21 ↗ establece las restricciones de uso comercial.\n\nDe dónde proceden los precios\n\nLos precios, el número de cotizaciones y los rangos de capitalización bursátil se han extraído de la cs2.sh Datos de mercado API mediante una suscripción comercial de pago, utilizando una clave de licencia. No se ha extraído información de ninguna plataforma de comercio electrónico ni se ha utilizado ninguna cuenta o credencial de ninguna de ellas. El proveedor agrupa BUFF, Youpin, CSFloat, Skinport, C5Game y el mercado de la comunidad Steam; todas las cifras se expresan en dólares estadounidenses tal y como se han facilitado. Abrir el manifiesto de procedencia ↗ — registra los puntos finales exactos, las horas de captura y los hash SHA-256 de las instantáneas sin procesar, por lo que un lector independiente que disponga de su propia clave puede obtener los mismos datos y volver a calcular todas las cifras que aparecen en esta página.\n\nLo que no pudimos conseguir\n\nLa suscripción adquirida solo cubre las instantáneas actuales. No hemos tenido acceso a los puntos finales históricos ni a los archivados, y En esta página no se hace ninguna afirmación sobre ninguna tendencia, ningún precio anterior ni ningún cambio a lo largo del tiempo. Aquí todo es un único instante, con fecha.\n\nEl registro anterior de «CSFloat»\n\nLa primera versión de esta exposición incluía 245 categorías procedentes de una única instantánea del catálogo de CSFloat con fecha del 20 de septiembre de 2026: esa instantánea sigue aquí ↗. El presente registro es más amplio, ya que abarca cinco mercados en lugar de uno solo. Se trata de dos recuentos distintos y no deben sumarse.\n\nDeclaración de cumplimiento específico de Valve\n\nActualización de Valve sobre el intercambio de objetos en el juego de «2016» ↗ archivado en 2026-09-21 ↗ se refiere a los operadores de juegos de azar que utilizan OpenID y cuentas automatizadas de Steam. Se trata de una medida más limitada que una prohibición de todos los mercados externos.\n\nLímite de interpretación\n\nSe trata de ofertas, no de ventas. Un nombre de mercado puede abarcar varios artículos físicos con diferentes detalles en cuanto a flotación, diseño o pegatinas. Este registro no mide el valor total de mercado ni la intención de Valve.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Registro en Elite Skins — El techo del mercado de $1,800"
          },
          {
            "level": 2,
            "id": null,
            "text": "El umbral mínimo cuantificable en dólares"
          },
          {
            "level": 3,
            "id": null,
            "text": "Por qué se trata de un mínimo y no de una estimación"
          },
          {
            "level": 2,
            "id": null,
            "text": "Lo que el límite no tiene en cuenta"
          },
          {
            "level": 3,
            "id": null,
            "text": "★ Butterfly Knife | Doppler (Factory New)"
          },
          {
            "level": 2,
            "id": null,
            "text": "El límite de Steam hace que la determinación de precios se desvíe de Steam"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam cierra la lista"
          },
          {
            "level": 3,
            "id": null,
            "text": "Dragon Lore:10,940.85 dólares"
          },
          {
            "level": 3,
            "id": null,
            "text": "Desglose del precio y de la transferencia"
          },
          {
            "level": 2,
            "id": null,
            "text": "El techo también afecta a Dota 2"
          },
          {
            "level": 3,
            "id": null,
            "text": "Media luna heroica y brutal"
          },
          {
            "level": 3,
            "id": null,
            "text": "Capa «Dark Artistry»"
          },
          {
            "level": 3,
            "id": null,
            "text": "Estrella de energía corrompida"
          },
          {
            "level": 2,
            "id": null,
            "text": "El resultado no depende del límite exacto"
          },
          {
            "level": 2,
            "id": null,
            "text": "Qué pocos de estos hay realmente a la venta"
          },
          {
            "level": 3,
            "id": null,
            "text": "AWP | La leyenda del dragón"
          },
          {
            "level": 3,
            "id": null,
            "text": "M4A4 | Howl"
          },
          {
            "level": 3,
            "id": null,
            "text": "AK-47 | Wild Lotus"
          },
          {
            "level": 3,
            "id": null,
            "text": "AWP | Gungnir"
          },
          {
            "level": 2,
            "id": null,
            "text": "Cuanto más caro es el artículo, más lejos se encuentra de cualquier lugar visible"
          },
          {
            "level": 2,
            "id": null,
            "text": "Todas las categorías observadas en «419»"
          },
          {
            "level": 2,
            "id": null,
            "text": "Comprueba el cálculo"
          },
          {
            "level": 3,
            "id": null,
            "text": "Los límites y condiciones de Valve"
          },
          {
            "level": 3,
            "id": null,
            "text": "De dónde proceden los precios"
          },
          {
            "level": 3,
            "id": null,
            "text": "Lo que no pudimos conseguir"
          },
          {
            "level": 3,
            "id": null,
            "text": "El registro anterior de «CSFloat»"
          },
          {
            "level": 3,
            "id": null,
            "text": "Declaración de cumplimiento específico de Valve"
          },
          {
            "level": 3,
            "id": null,
            "text": "Límite de interpretación"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/es/#market-gap-section",
          "https://phishdestroy.io/steam_dossier/es/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/es/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/es/skin_atlas.html#grading",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-above-the-ceiling.json",
          "https://phishdestroy.io/steam_dossier/es/elite_skins#selected",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://csmarketcap.com/search?minPrice=1800&amp;page=1",
          "https://store.steampowered.com/agreement/?l=english",
          "http://web.archive.org/web/20260921022032/https://store.steampowered.com/agreement/?l=english",
          "https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921021947/https://store.steampowered.com/oldnews/22883",
          "https://phishdestroy.io/steam_dossier/es/#proxy-bypass-explainer",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/skinport-floor-over-cap.json",
          "https://docs.skinport.com/items",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-float-scarcity.json",
          "https://phishdestroy.io/steam_dossier/es/elite_skins#register",
          "https://cs2.sh/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/csfloat-catalogue.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/es/elite_skins.content.json",
      "export_json_sha256": "67c7cbbba2e07420fb536f0cd6c73f2acc84590252233393816c6184fb374d23"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "es/enforcement_audit.html",
      "language": "es",
      "title": "El censo Valve no se publicará — El Dossier Steam",
      "source_url": "https://phishdestroy.io/steam_dossier/es/enforcement_audit",
      "source_html_sha256": "3aae0b6e070bf1481bf157d5c080f38a409283f252ff772363f6b0bd6ebbf404",
      "exported_at": "2026-09-29T00:17:19.079Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "enforcement_audit.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/es/enforcement_audit.pdf?v=print-20260929-v5",
        "sha256": "c473e6b54957f158a4bfc739beb3e07707843b4912e533e4742a87ef83c8f104",
        "bytes": 146069,
        "pages": 13
      },
      "integrity": {
        "signed_object": "enforcement_audit.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "enforcement_audit.content.json.asc",
        "digest_file": "enforcement_audit.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify enforcement_audit.content.json.asc enforcement_audit.content.json",
          "sha256sum -c enforcement_audit.content.json.sha256"
        ]
      },
      "content": {
        "text": "ANEXO VI — EL CENSO VALVE NO SE PUBLICARÁ\n¿Qué tamaño tiene la granja de Steam? La contamos nosotros.\n\nNo hay ninguna cifra publicada sobre cuántas cuentas de automatización se ejecutan en Steam. No hay necesidad de que sea un secreto: el espacio de identificadores Steam es un rango contiguo de números enteros y Valve proporciona la clave de la API web que lo recorre. Así que tomamos la población más numerosa que se identifica a sí misma —la comunidad ArchiSteamFarm— y consultamos a cada miembro una vez a través del propio punto final de bloqueo de Valve. Se autodeclara porque ASF, al iniciarse por primera vez, se une automáticamente al grupo Steam, a menos que el usuario opte explícitamente por no participar o desmarque la configuración de unión al grupo (AutoJoinSteamGroup / Estadísticas). Dado que esta configuración está activa por defecto, los miembros del grupo abarcan una amplia población: redes comerciales activas de bots con múltiples cuentas, aficionados ocasionales que dejan sus cuentas inactivas y jugadores normales que ejecutaron el software en su cuenta personal y nunca desactivaron la suscripción predeterminada. Esto hace que sus miembros constituyan un censo operativo del alcance acumulado del software: 10,880,610 cuentas en total (con 5,360,499 miembros confirmados sin restricciones que han superado la $5.00 puerta de la tienda). Entonces planteamos la única pregunta que importa: ¿qué les ha hecho realmente Valve?\n\nQué no es esta página. No se trata de argumentar que Valve debería expulsar a diez millones de personas, ni es una queja contra los «card farmers». Todas las cifras que aparecen a continuación están aquí por una sola razón: Valve ¿hace? expulsar de forma permanente a determinados usuarios, y la razón que expone por escrito es el uso comercial de Steam y la automatización. Esto mide cómo se aplica esa misma norma a la misma conducta a gran escala —por parte de un operador que, de paso, recauda el desbloqueo $5.00, las licencias de los juegos y las comisiones del Market Valve—. La conclusión es la asimetría, no la granja.\n\nLos 10,88 millonesLos estafadores que se pasean (53,5 mil)Auditoría de 100 000 frente a auditoría gratuita\n10,880,610El número total de miembros del grupo ASF que han consultado la API de bloqueo propia de Valve (combinando los casos con y sin limitación)\n88.97%Nunca me han bloqueado — 9,680,599 cuentas siguen activas\n63.06%De las cuentas bloqueadas, las de pago ($5+ gasto) — 100,000 SRSWOR porcentaje (±0.39% margen de error)\n67.77%De los 51,732 estafadores condenados, ninguno tiene ninguna prohibición por estafa (censo completo)\n01 — La escala\nDiez millones de cuentas, y nueve de cada diez sin tocar\n\nUna población que se cuenta a sí misma, leída una vez a través del propio punto final de Valve.\n\nPOR QUÉ SE AUTOCONTARÍA\nASF se une al grupo por ti\n\nEn la primera ejecución, se establecen ArchiSteamFarm conjuntos Estadísticas se establece en «true» de forma predeterminada y se une al grupo «SC Farm Steam» de Archi. Un operador tiene que optar activamente por no participar. Por lo tanto, el número de miembros supone un mínimo de instalaciones, no un máximo. Los operadores que han desactivado las estadísticas no aparecen; el recuento real de instalaciones es, como mínimo, este.\n\nLO QUE LEEMOS\n10,880,610 entradas en total\n\nLa lista de miembros de la API devolvió 10,880,610 SteamID64 en total —tanto limitados como no limitados—. La página del grupo de Steam muestra 5,360,499 (solo no limitados). Cada entrada se procesó una vez a través de ISteamUser/GetPlayerBans en 2026-09-23. Cincuenta y cinco minutos con una sola tecla.\n\nLA RESPUESTA\n88.97% limpio\n\n1,200,011 no está sujeto a ninguna Steam prohibición (11.03%). El otro 9,680,599 no hay ningún dato registrado — Ni una expulsión de la comunidad, ni VAC, nada. La granja no se está desmantelando. Se está dejando en funcionamiento. Esa misma cláusula, aplicada a una sola persona, basta para expulsarla de forma permanente.\n\nDe las cuentas 10,880,610, ¿cuántas Valve se han utilizado?\n\nEl conjunto de la población escaneada, dividida según si Valve ha aplicado alguna prohibición. La sección roja representa todo lo que Valve ha hecho jamás con esta flota.\n\n88.97%nunca ha sido suspendido\n11.03%\nNo existe prohibición de ningún tipo — 9,680,599 (88.97%)Lleva una prohibición de Steam — 1,200,011 (11.03%)\n10,880,610Los miembros del grupo ASF escanearon\n9,680,599Nunca ha sido expulsado — 88.97%\n1,200,011Aplicar cualquier prohibición — 11.03%\n55 minPara contabilizarlo todo con una sola clave de API\nLo que esta flota ya ha pagado Valve para existir\n\nNo es una estimación de lo que gana la granja. Es un límite mínimo de lo que ya ha gastado en la tienda de Valve, calculado a partir de la propia regla de Valve, aplicada al recuento anterior.\n\nEl recuento 10,880,610 abarca la lista completa de miembros del grupo ASF tal y como la devuelve la API; esto incluye tanto las cuentas con restricciones como las que no las tienen. La propia Steam Cuentas de usuario con funciones limitadas En la página se indica que las cuentas limitadas no contar para Steam pertenecen al grupo (no se tienen en cuenta a la hora de calcular el tamaño del grupo que se muestra), pero pueden aparecer en la lista de miembros subyacente. El subconjunto sin restricciones —las cuentas que han gastado al menos $5.00 en la tienda Steam— es exactamente 5,360,499 — El recuento Steam aparece en la página del grupo, que, según la propia regla de Steam, excluye las cuentas con restricciones. El cálculo del mínimo $5.00 se aplica únicamente a ese subconjunto sin restricciones.\n\n5,360,499miembros sin restricciones\n(Número de grupos mostrados por Steam)\n×\n$5.00El mínimo propio de Valve\npara dejar de estar limitado\n=\n$26,802,495límite mínimo de gasto en la tienda\npor el subconjunto no limitado\n\nSe trata de un límite inferior de la cantidad de dinero que ya ha recibido Valve de la parte no limitada de la flota; no es una estimación de ingresos ni una declaración de beneficios. El gasto real por cuenta es superior en la mayoría de los casos; la cifra $5.00 es únicamente el umbral mínimo requerido.\n\nLa cosecha secundaria: comisión de hasta 66.7% sobre el volumen de productos cultivados. Además de la cuota de entrada de $26.8M, cada tarjeta y artículo que se venda en el Mercado de la Comunidad paga Valve, que corresponde a una cuota mínima obligatoria de dos céntimos ($0.01 Steam de comisión + $0.01 de comisión del editor). En el caso de las tarjetas típicas de 3 céntimos y los artículos sin valor, Valve se queda con 2 céntimos de cada 3 céntimos, lo que supone una reducción efectiva de 66.67% a favor de Valve, superando con creces la tasa de marketing oficial de 15%.\n\nAdvertencia fundamental sobre la población: El hecho de pertenecer al grupo no prueba que todas y cada una de las cuentas sean bots dedicados, ni garantiza que se incluyan todos los bots de Steam. Por defecto, ASF suscribe automáticamente las cuentas a su grupo comunitario al iniciarse; a menos que el usuario desmarque explícitamente o desactive esa opción de configuración (AutoJoinSteamGroup), los jugadores habituales, los usuarios ocasionales y los miembros de la comunidad siguen figurando en la lista junto a las flotas de farming automatizadas. Además, una suspensión de Steam no incluye ningún campo de justificación pública. El resultado es una tasa empírica en toda esta población asociada al software, no un veredicto individual sobre una cuenta concreta. Agregado, reproducible: asf-ban-census-2026-09-23.json.\n\n02 — Geografía\nDónde se encuentra la flota\n\nSolo 8.5% de las cuentas bloqueadas indican algún país. De las que sí lo hacen, la mayor proporción corresponde a Estados Unidos.\n\nUn perfil Steam incluye un campo opcional de país. 100,413 de las 1,182,811 cuentas bloqueadas lo rellenan: 8.5%.† Entre esa minoría, Estados Unidos ocupa el primer puesto con 15.5%, seguido de Ucrania, China y Rusia, mientras que el resto se distribuye en una larga cola que abarca Europa, América Latina y el sudeste asiático. Nadie verifica los datos sobre el terreno: Afganistán figura entre los diez primeros, lo que más o menos se ajusta a su importancia. Los otros 91.5% se omiten en lugar de asignarse, por lo que lo que sigue es el perfil de una minoría autoseleccionada, no un mapa de la flota, ni una base para afirmar desde dónde se dirige.\n\nCuentas bloqueadas por país declarado\n\nLos 15 países con mayor número de cuentas bloqueadas 100,413 que revelan una ubicación pública. El porcentaje corresponde a ese subconjunto concreto. Pasa el cursor por encima para ver las cifras.\n\n0%\n5%\n10%\n15%\n20%\nUnited States\nUkraine\nChina\nRussia\nCanada\nAustralia\nJapan\nBrazil\nGermany\nAfghanistan\nUnited Kingdom\nRomania\nFrance\nPhilippines\nIndia\n\nUbicación leída desde GetPlayerSummaries para el subconjunto de direcciones prohibidas. El campo lo configura el titular de la cuenta y nadie lo verifica, por lo que una salida de VPN o una entrada falsa cuentan igual que una real.\n\n03 — Frescura\nCuentas recientes, no un volumen de trabajo atrasado heredado\n\nA juzgar por la fecha de creación de las cuentas, la población de usuarios bloqueados es reciente, no un vestigio de la era de las cartas coleccionables.\n\nSi se tratara de un antiguo lío que se estuviera resolviendo poco a poco, las cuentas bloqueadas se concentrarían en los primeros años de las cartas coleccionables. Sin embargo, ocurre justo lo contrario. De las 1,132,852 cuentas bloqueadas que muestran una fecha de creación, 70% se crearon en 2020 o posteriormente, y casi la mitad desde 2023. La cifra ha pasado de 59,175, registrada en 2017, a un máximo de 227,030 creados solo en 2024. Todos ellos cruzaron la puerta de la tienda $5.00 antes de que esta pudiera leer su tarjeta, por lo que se les cobró la cuota de entrada a cada uno.\n\nCuándo se crearon las cuentas bloqueadas\n\nAño de creación de las cuentas de los 1,132,852 miembros expulsados cuya fecha de creación se conoce. El periodo abarca de 2020 a 2026, no la era de las tarjetas coleccionables de 2013 a 2015. Pico: 2024. Pasa el cursor por encima para ver las cifras.\n\n0k\n63k\n125k\n188k\n250k\n'13\n'14\n'15\n'16\n'17\n'18\n'19\n'20\n'21\n'22\n'23\n'24\n'25\n'26\n70%De las cuentas bloqueadas creadas en 2020 o posteriormente\n227,030Cuentas bloqueadas creadas en 2024 — el año en que se alcanzó el máximo—\n51,701El mínimo de 2021, entre dos años de máximos: sin explicación\n2003→2026Se muestra el rango, pero los datos corresponden a los últimos seis años\n\nLa creación data de GetPlayerSummaries para el subconjunto de cuentas bloqueadas, sin duplicados según el SteamID64. La fecha de creación es la fecha en la que se creó la cuenta, no la fecha en la que fue bloqueada ni la fecha en la que comenzó a generar cuentas; aquí se utiliza como indicio de lo reciente que es la población, no de la intención. Hay tres cosas que el gráfico no muestra:\n\nUna tendencia a partir de 2024. Una cuenta creada en 2025 o 2026 ha tenido menos tiempo para acumular una suspensión, y 2026 abarca nueve meses, por lo que 227,030 → 121,070 → 16,534 supone una censura, no un descenso.\nUna tasa de prohibición. Los años de creación se han consultado únicamente para las cuentas bloqueadas, por lo que no hay denominador. El mero hecho de que la base de usuarios esté creciendo ya daría lugar a esta tendencia.\nPor qué se vino abajo el año 2021. 51,701 se sitúa entre 105,821 y 104,641, por debajo de la mitad de cualquiera de sus vecinos. No hay ninguna explicación pública al respecto; se deja a la vista en lugar de suavizarse.\n04 — Sincronización\nCuando Valve entra en vigor, lo hace dentro del primer año\n\nLa justificación obvia para que 88.97% no se haya modificado es la acumulación de trabajo pendiente. Las prohibiciones anteriores indican lo contrario.\n\n¿Cuánto tiempo llevaba abierta la cuenta cuando se le impuso la suspensión?\n\nAntigüedad de la cuenta en el momento de la suspensión, en el caso de las 293,750 cuentas suspendidas que cuentan tanto con una fecha de creación como con una fecha de última suspensión. Más de la mitad fueron detectadas durante el primer año.\n\n0%\n10%\n20%\n30%\n40%\n<6 mo\n33.7%\n6–12 mo\n21.5%\n1–2 y\n20.6%\n2–5 y\n14.3%\n5 y+\n10.0%\n55.1% inside the first year\nProhibido durante el primer año — 55.1%Bloqueado más tarde — 44.9%\n0,80 yEdad media de la cuenta en el momento en que se produjo la suspensión\n55.1%Bloqueado durante el primer año de la cuenta\n33.7%Prohibido durante los primeros seis meses\n293,750Cuentas en las que figuran ambas fechas\n\nEsta es la respuesta a la objeción obvia. Si el 88.97% de la flota no se ve afectado porque la aplicación de la normativa es simplemente lenta —hay un retraso que se va resolviendo poco a poco—, entonces las prohibiciones que hacer Los datos podrían dar una imagen sesgada. Sin embargo, ocurre justo lo contrario: la mediana de las cuentas bloqueadas era nueve meses y medio, y un tercero — 33.7% — fue capturado en un plazo de seis meses. Cuando Valve actúa sobre esta población, lo hace con rapidez. Los nueve de cada diez que siguen en libertad no están esperando en una cola.\n\nEdad en el momento de la prohibición = fecha de creación a partir del GetPlayerSummaries restada de la fecha de prohibición que se desprende de Días desde la última suspensión, sigue leyendo 2026-09-23. Se calcula únicamente cuando ambos valores están presentes: 293,750 de las 1,200,011 cuentas bloqueadas. Las cuentas restantes no indican ningún valor de «días desde» y se omiten, no se estiman; por lo tanto, interpreta esto como la forma del subconjunto con fecha, no de cada suspensión.\n\n05 — En qué consiste realmente la prohibición\nCuando Valve se activa, no detiene al bot\n\nDe los 11% que tienen alguna prohibición, fíjate en cuál es.\n\nUna suspensión no es una suspensión. De las 1,200,011 cuentas que Valve ha marcado, 99.8% llevar un comunidad prohibición — una restricción en foros, perfiles y grupos que no afecta en absoluto a un bot de intercambio. La cuenta sigue pudiendo recibir cartas, seguir intercambiando y seguir moviendo inventario. 22.2% tener al menos una suspensión de juego y 3.9% una suspensión de VAC; las categorías se solapan, por lo que no se suman. La única sanción que realmente impide el intercambio, la suspensión económica o comercial, se aplica a 5,214 cuentas. No basamos nuestro argumento en esa cifra: las prohibiciones de comercio son poco frecuentes en Steam en general. La idea de este gráfico es más sencilla: incluso la fracción Valve ¿hace que...? Touch sigue operando.\n\nPor qué motivo se ha expulsado realmente a los 11% que están expulsados\n\nCada tipo de bloqueo representa un porcentaje del total de miembros analizados 10,880,610. Las cuentas pueden tener más de uno. Pasa el cursor por encima para ver las cifras.\n\n0%\n4%\n8%\n11%\n15%\nCommunity ban\nGame ban\nVAC ban\nEconomy / trade ban\n\nUna prohibición Steam no incluye un campo de motivo, por lo que ninguna de estas prohibiciones se atribuye específicamente a la acumulación de cartas; se trata de una combinación de los tipos de prohibición existentes, junto con lo que cada tipo restringe realmente. La prohibición comunitaria no impide el intercambio; la prohibición económica o comercial sí lo hace. Resumen: asf-ban-census-2026-09-23.json.\n\n06 — La otra población\nLos estafadores Valve, vamos allá: el censo completo 51,732\n\nUna segunda lista independiente —casos de fraude confirmados por la comunidad— comparada con la misma API oficial.\n\nSe podría argumentar que el grupo de los automatizados no son más que holgazanes inofensivos. No se puede decir lo mismo del segundo grupo. SteamRep es una base de datos de reputación comunitaria que lleva mucho tiempo en funcionamiento; una cuenta marcada como PROHIBIDO esa comunidad ha declarado a una persona como estafadora, con pruebas documentadas de las víctimas y registros de chat de las transacciones. Hemos realizado un censo 100% de todos los 51,732 perfiles con el estado «PROHIBIDO» frente a la API web oficial de Steam (ISteamUser/GetPlayerBans/v1) — y solo se han contabilizado las sanciones relacionadas con las estafas. Una sanción de VAC se aplica al uso de software para hacer trampa en un juego (aimbots, wallhacks); no afecta en modo alguno a un operador y no constituye una prueba Valve de que se haya cometido un fraude, por lo que no se contabiliza como medida contra el fraude.\n\nEn el censo completo de cuentas 51,732, 67.77% — 35,059 estafadores condenados — no tienen NINGUNA suspensión relacionada con estafas por parte de Valve: Aún pueden realizar intercambios, enviar solicitudes de amistad a nuevas víctimas y enviar mensajes. Solo a 32.23% se les ha impuesto una suspensión de la comunidad o una prohibición de intercambios, y la prohibición de intercambios —la única medida que realmente impide las transferencias de inventario— se aplica únicamente a 18.81% (9,731 cuentas). Otras 12.81% (6,627 cuentas) tienen VAC prohibiciones de juego o de acceso al juego exclusivamente por hacer trampas en el juego, mientras que no tienen ninguna restricción en Steam en lo que respecta a las transacciones.\n\nEstafadores confirmados, según si Valve les ha impuesto una suspensión relacionada con la estafa (Censo completo)\n\nTodos los perfiles 51,732 SteamRep-BLOQUEADOS, desglosados según si Valve se aplicó una suspensión por motivos comunitarios o comerciales. Se excluyen las suspensiones VAC y las relacionadas con el juego, ya que no se refieren al fraude. Pasa el cursor por encima para ver las cifras.\n\n0%\n18%\n35%\n53%\n70%\nNo scam-relevant ban\nCommunity or trade ban\n0%\n6%\n13%\n19%\n25%\nCommunity ban\nTrade / economy ban\nVAC (not fraud)\nGame ban\n51,732SteamRep perfiles bloqueados auditados — 100% censo completo\n35,059No tiene ninguna suspensión relacionada con estafas (67.77%)\n18.81%Aplicar la prohibición comercial que pone fin a las estafas (9,731)\n32.23%La acción Valve se vio afectada por una prohibición comunitaria o comercial (16,673)\n\nSteamRep es una base de datos de reputación de terceros, evaluada por la comunidad, y no una determinación Valve —y ahí está la clave: se trata de pruebas externas, comparadas con lo que hizo Valve en sí mismo. Todos los perfiles 51,732 BLOQUEADOS de la exportación canónica se cotejaron directamente con ISteamUser/GetPlayerBans/v1. «Relacionado con el fraude» se refiere a una suspensión de la comunidad o de la economía/comercio; VAC (12.81%) y las suspensiones del juego (3.86%) se contabilizan por separado, ya que se refieren a las trampas, no al fraude. Conjunto de datos completo de la auditoría: steamrep_steam_bans.csv.\n\nDos poblaciones, un hallazgo\n\nNo se trata de las mismas personas ni de la misma conducta. En un caso, son diez millones de cuentas automatizadas; en el otro, cincuenta y tres mil estafadores condenados. Lo que tienen en común es la forma que adopta el resultado: Nueve de cada diez cuentas agrícolas nunca se utilizan, y más de dos tercios (67.77%) de los estafadores confirmados no reciben ninguna sanción por fraude. La expulsión de la comunidad Valve sí que se aplica libremente para restringir foros y perfiles, pero no el comercio. El botón de denuncia, la base de datos de reputación, la expulsión que frena una estafa: todo está ahí, pero se utiliza muy poco. Compárese esto con los rechazos archivados en el expediente principal, donde la misma empresa elimina definitivamente una única cuenta y alega como motivo el uso comercial y la automatización: la cláusula no está inactiva, sino que se aplica de forma específica.\n\n07 — El caso «$5.00» y el secuestro de cuentas\nLa auditoría empírica de las cuentas «100,000»: las redes de bots no son cuentas gratuitas desechables\n\nLógica del muestreo estadístico y demostración matemática: por qué tomar cualquier otro valor de 100,000 da exactamente el mismo resultado.\n\nLa principal defensa de Valve ante los organismos reguladores y de protección del consumidor ha sido que las estafas automatizadas y el «farming» se llevan a cabo mediante cuentas efímeras y gratuitas, «desechables», que se bloquean rápidamente. Según las normas publicadas por Valve, una cuenta es Limitado hasta que gaste al menos 5.00s de dólares estadounidenses en la tienda Steam, lo que le impide realizar transacciones, enviar solicitudes de amistad y acceder a las funciones de la API. Hemos comprobado esta afirmación directamente, analizando el estado de monetización de una muestra representativa y matemáticamente rigurosa de 100,000 cuentas bloqueadas Steam extraídos de nuestro corpus de metadatos de perfiles 1,182,811.\n\nPROTOCOLO DE MUESTREO (SRSWOR)\n100,000 Corte imparcial\n\nExtraído de N = 1,182,811 cuentas únicas bloqueadas Steam mediante un muestreo aleatorio simple sin reposición a través de un generador de números aleatorios pseudoaleatorios (PRNG) criptográficamente uniforme. Cada cuenta tenía una probabilidad de inclusión idéntica de P = n / N ≈ 8.45%, lo que elimina por completo los sesgos de supervivencia y de actividad.\n\nDEMOSTRACIÓN MATEMÁTICA\nMargen de error < ±0.4%\n\nAplicando la fórmula de la corrección de población finita (FPC) a un 99% Intervalo de confianza (Z = 2,576):\nMoE = Z × √[p(1-p)/n] × √[(N-n)/(N-1)] ≈ ±0.39%\n\nREPRODUCIBILIDAD\nPor qué cualquier 100k da el mismo resultado\n\nDado que el margen de error está acotado entre ±0.4% con un nivel de confianza de 99%, Está matemáticamente garantizado que cualquier otra muestra independiente de la cuenta 100,000 se situará dentro de 63.06% ± 0.39% (de 62.67% a 63.45%). La muestra es representativa del conjunto de la población de 1,18 millones de personas excluidas.\n\nLos resultados de la auditoría desmontan por completo la defensa basada en los «bots desechables». De las 100,000 cuentas auditadas a través de la interfaz de perfiles XML heredada de Steam: Las cuentas 61,490 (63.06% de las cuentas clasificadas) son cuentas sin límite (de pago) que han gastado al menos $5.00 en Steam. Solo 36,021 (36.94%) son cuentas gratuitas limitadas, mientras que 2,489 no estaban configuradas o eran privadas.\n\n100,000 Cuentas bloqueadas: de pago ($5+ gasto en la tienda) frente a cuentas gratuitas con estado limitado\n\nAuditoría empírica de 100,000 cuentas bloqueadas seleccionadas al azar. Más de 63% han superado el filtro financiero de pago de Valve. Pasa el cursor por encima para ver las cifras.\n\n0%\n16%\n33%\n49%\n65%\nNon-limited (Paid ≥ $5.00)\nLimited (Free < $5.00)\n100,000Población muestreada (SRSWOR, N = 1,18 millones)\n63.06%Cuentas de pago sin restricciones (cuentas 61,490)\n±0.39%Margen de error en un intervalo de confianza de 99%\n~745,800Cuentas de pago extrapoladas en un conjunto de datos de 1,18 millones de cuentas bloqueadas\nLa realidad estructural: la liquidación de cuentas a escala industrial\n\n¿Por qué 63% de las cuentas bloqueadas incluidas en la muestra serían cuentas de pago que gastaron dinero real en la tienda de Valve? Los operadores de botnets no gastan millones de su propio bolsillo en cuentas desechables. Esta proporción pone de relieve el volumen de cuentas comprometidas y pirateadas que circulan por el ecosistema.\n\nEsta escala se puede observar directamente en las plataformas clandestinas: en mercados como FSB Market (nombre anonimizado; aquí no se divulga el nombre original), a través de 550,000 Steam cuentas (registros de robo de datos, capturas de phishing, relleno de credenciales) se anuncian activamente a la venta en todo momento (phishdestroy.io/live-intel). El mercado verifica la identidad de compradores y vendedores mediante el OpenID Steam propio de Valve, y ni FSB Market ni el foro asociado está bloqueado por el filtro de enlaces de Valve.\n\nTal y como se establece en la sección 06, Valve no elimina de forma proactiva esta actividad fraudulenta: 67.77% de los estafadores confirmados por la comunidad no tienen ninguna suspensión por estafa en Steam, y el 88.97% de la flota de automatización permanece totalmente intacto. Las cuentas circulan libremente, se autentican a través de API oficiales y realizan operaciones en todo el ecosistema con una impunidad casi total.\n\nDiagrama de la arquitectura de pruebas forenses y aplicación de la ley\nFlujo interactivo desde 10,88 millones de cuentas analizadas hasta una muestra empírica de 100 000 y 53 500 estafadores confirmados · Haz clic en los enlaces para examinar las pruebas sin procesar\nNivel 01 · 10,88 millones: censo de la flota de automatización\nLa mayor población de bots que se autodefine como «de automatización» en Steam pasó sucesivamente por la API de bloqueo oficial de Valve. Esto demuestra que las flotas de bots comerciales operan con total impunidad en 88.97%, a pesar de pagar decenas de millones en cuotas de acceso.\n9,680,599 88.97% Activo y sin modificar\nCuentas que utilizan software automatizado y que no tienen registrado ningún tipo de bloqueo.\nDatos del censo en formato JSON sin procesar (1,2 KB) ↗Consulte la sección 01 ↗\n$26,802,495 Límite mínimo de ingresos directos de las tiendas\nRecogidos por Valve de entre 5,360,499 miembros sin restricciones que superan el umbral mínimo de participación de $5.00.\nAuditoría de la economía de las tarjetas ↗Valve $5 Preguntas frecuentes sobre las reglas ↗\n1,200,011 11.03% Subconjunto marcado\n99.8% solo aplica restricciones de carácter cosmético a la comunidad; el comercio sigue abierto en 99.95% de las cuentas.\nDesglose por tipo de suspensión ↗Base de datos bloqueada (60,4 MB) ↓\nNivel 02 · 100,000-Auditoría de muestreo empírico de cuentas (N = 1,182,811)\nMuestra representativa de SRSWOR evaluada a través de puntos de conexión XML heredados. Margen de error demostrado matemáticamente < ±0.4% con un intervalo de confianza de 99%. Refuta la afirmación de que los bots bloqueados son cuentas desechables gratuitas.\n61,490 (63.06%) Cuentas de pago sin límites ($5+ de gasto)\nMás de 63% de las cuentas bloqueadas corresponden a transacciones de pago. Esto se extrapola a ~745,800 cuentas de pago (con un umbral mínimo de $3.73M+) en el conjunto de cuentas bloqueadas.\nResultados limitados en formato CSV (2,1 MB) ↓Informe forense de 100 000 ↗\n36,021 (36.94%) Cuentas gratuitas con funciones limitadas (< $5.00)\nLa minoría de perfiles bloqueados que se ajustan al perfil de «bot desechable» descrito por Valve. Las cuentas 2,489 no estaban configuradas o eran privadas.\nMuestra de 100 000 registros en formato CSV (8,5 MB) ↓Análisis de gastos MD ↗\n34.67% contra 63.93% Auditoría de saneamiento de perfiles\nValve ha borrado los apodos y los ha sustituido por el SteamID64 sin formato en 34,673 cuentas, pero ha dejado los nombres personalizados y los avatares tal y como estaban en 63,928 cuentas bloqueadas.\nSección de desinfección ↗Hoja de ruta general ↗\n34.59% Legado Cuentas antiguas (creadas entre 2003 y 2019)\nMás de un tercio de las cuentas bloqueadas se registraron hace entre 5 y más de 20 años, lo que demuestra que se ha producido un secuestro a escala industrial de cuentas de jugadores veteranos (Steam).\nCronología por épocas ↗Denegaciones de ayuda ↗\nNivel 03 · 51,732 SteamRep Censo de estafadores confirmados\nCenso completo 100% de estafadores sancionados por la comunidad, con registros de chat de las víctimas y pruebas de transacciones, cotejados con las API oficiales Steam de expulsión. Demuestra un fallo sistémico en la aplicación de las normas.\n35,059 (67.77%) Cero sanciones por estafa (impunidad total)\nMás de dos tercios de los estafadores verificados no tienen ninguna restricción comunitaria ni comercial impuesta por Valve. Están plenamente operativos para realizar transacciones y añadir víctimas.\nSteamRep Restricciones de la API (2,6 MB) ↓SteamRep Informe de auditoría ↗\n9,731 (18.81%) Economía / Prohibiciones comerciales\nLa única sanción que pone fin a la liquidación de existencias. Se aplica a menos de una quinta parte de los estafadores confirmados.\nSteamRep Fuente (2,1 MB) ↓Consulte la sección 06 ↗\n6,627 (12.81%) Sanciones por trampas irrelevantes (solo VAC)\nSe les ha prohibido el uso de aimbots y wallhacks en los juegos, mientras que sus capacidades de comercio y phishing siguen activas.\nVAC Análisis de irrelevancia ↗Cronología de seguridad ↗\nNivel 04 · Alteración de páginas wiki y brechas de seguridad en la infraestructura de agosto de 2026\nLa alteración de la documentación interna para desarrolladores, la supresión del editor de la comunidad y los fallos en el perímetro no protegido, tal y como se recogen en el paquete de pruebas.\n1,200+ Redacción Registros de conflictos de VDC Wiki\nLos editores de la comunidad que intentaban corregir enlaces de phishing y plantillas de spam eran bloqueados sistemáticamente por filtros automáticos, mientras que el personal Valve ignoraba las advertencias.\nInforme sobre los conflictos en Rusia (127 KB) ↗Informe de clasificación (66 KB) ↗\n12 TB sin autenticación Agosto de 2026: Fuga de activos (CWE-284)\nValve mantuvo durante semanas 12 terabytes de código interno y versiones prototipo en un punto de acceso público abierto sin autenticación.\nValve Expediente de incompetencia (43 KB) ↗Archivo de pruebas ↗\nIncidente de seguridad en CEVA Logistics Agosto de 2026: Fuga de datos personales de clientes\nSe han filtrado los nombres, direcciones y números de teléfono de los compradores europeos de Steam Deck a través del socio logístico de Valve, lo que ha desencadenado una oleada de intentos de suplantación de identidad.\nRegistro de incidentes ↗Historial de medidas coercitivas ↗\n\nArtefacto de muestreo: banned_100k_slice.csv (100,000 cuentas). Resultados de la auditoría: slice_100k_limited_results.csv. Informe analítico completo: BANNED_100K_FORENSIC_ANALYSIS.md.\n\n08 — Método y límites\nCómo se ha interpretado esto y qué es lo que no afirma\n\nTres poblaciones públicas, una API pública y un muestreo estadístico riguroso.\n\nEJECUCIÓN Y CREDENCIALES\n\nEl censo de la ASF, la 100,000-cuenta SRSWOR y la SteamRep verificación cruzada fueron llevadas a cabo por PhishDestroy participantes utilizando sus propias Steam cuentas y claves de API web, como parte del trabajo público de la Coalición para la lucha contra el phishing y la prohibición de las estafas. El autor del informe no posee ninguna Steam clave de API web y no realizó personalmente ningún escaneo en tiempo real. La agregación, el hash, la verificación y la publicación se llevaron a cabo a partir de los resultados de los participantes.\n\nPoblación\tDe dónde viene\tLo que se leyó\nMiembros de la ASF\n10,880,610\tLa lista pública de miembros del grupo de la comunidad ArchiSteamFarm Steam. La página del grupo de Steam muestra 5,360,499 miembros (solo los que no tienen restricciones); la lista de miembros de la API devolvió un total de 10,880,610 entradas, incluidas las cuentas con restricciones. El usuario se une automáticamente al grupo la primera vez que ejecuta la aplicación, a menos que desactive explícitamente la configuración predeterminada de unión al grupo en la configuración (AutoJoinSteamGroup / Estadísticas), lo que significa que la lista de miembros incluye grupos de bots comerciales, usuarios individuales que mantienen sus tarjetas inactivas y jugadores habituales que dejaron activada la opción predeterminada.\tGetPlayerBans para cada miembro (indicadores de bloqueo); GetPlayerSummaries por fecha de creación y país. Agrupados en lotes de 100 ID, con las duplicadas eliminadas según el SteamID64.\n100 000 cuentas bloqueadas SRSWOR Porción\n100,000\tUna muestra representativa extraída al azar de forma uniforme y sin reposición del corpus de 1,182,811 cuentas bloqueadas ($P = 8,45\\%$). La corrección por población finita arroja un margen de error de $\\pm 0,39\\%$ con un nivel de confianza de 99% ($Z = 2,576$).\tMonetización y estado de cuenta limitada (isLimitedAccount) auditado a través de la interfaz de perfiles XML heredada de Steam (?xml=1) a través de canales de proxy distribuidos. Confirma el estado de pago 63.06%.\nSteamRep estafadores\n51,732\tSe ha realizado un recuento completo 100% de todos los perfiles marcados como «BLOQUEADOS» en la base de datos de reputación de la comunidad SteamRep (51,732 perfiles en total). No se ha aplicado ningún muestreo ni filtrado.\tISteamUser/GetPlayerBans/v1 para todas las cuentas 51,732, en una tabla cruzada con el estado SteamRep. Confirma que 67.77% queda libre de cualquier prohibición por estafa.\nObjeto de la reivindicación\n\nSolo tasas empíricas y estimaciones con límites estadísticos. En la población de automatización, 88.97% no tienen ninguna restricción; el subconjunto restringido se concentra en los últimos años (70% desde 2020). En la auditoría empírica de las cuentas 100,000, 63.06% de las cuentas bloqueadas son de pago (sin límite), con un margen de error matemáticamente demostrado inferior a ±0.4%. Entre los 51,732 estafadores confirmados, 67.77% no tienen ninguna suspensión relacionada con la estafa. Todas las cifras se pueden reproducir a partir de la propia API web de Valve.\n\nLo que no se reivindica\n\nUna suspensión de tipo Steam no incluye un campo de motivo, por lo que ninguna suspensión de este tipo se atribuye a una causa específica. La pertenencia a un grupo no es prueba de que una cuenta sea un bot automatizado: dado que ASF permite la incorporación a grupos de forma predeterminada, a menos que se desmarque manualmente, el conjunto de cuentas mezcla granjas comerciales de cuentas múltiples con cuentas personales de jugadores habituales y aficionados. El país se indica por el propio usuario, y una entrada SteamRep es una resolución de la comunidad, no una sentencia judicial. No se menciona el nombre de ninguna persona.\n\nPor qué es importante\n\nValve cuenta con la misma API, su propia base de datos y los motivos de bloqueo que este análisis no puede ver. Puede ejecutar esta consulta en todo el espacio de identificadores en cuestión de segundos. La medida que permite a un tercero comprobar una alegación de aplicación de la normativa respecto a un número nunca ha sido publicada por la única parte capaz de generarla con total fiabilidad. Se trata de una estimación externa, ofrecida para que la pregunta pueda plantearse acompañada de una cifra.\n\nSiguiente: la economía de las tarjetas que gestiona esta población → · asistencia técnica y robo → · el expediente completo →",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "¿Qué tamaño tiene la granja de Steam? La contamos nosotros."
          },
          {
            "level": 2,
            "id": null,
            "text": "Diez millones de cuentas, y nueve de cada diez sin tocar"
          },
          {
            "level": 3,
            "id": null,
            "text": "ASF se une al grupo por ti"
          },
          {
            "level": 3,
            "id": null,
            "text": "10,880,610 entradas en total"
          },
          {
            "level": 3,
            "id": null,
            "text": "88.97% limpio"
          },
          {
            "level": 3,
            "id": null,
            "text": "De las cuentas 10,880,610, ¿cuántas Valve se han utilizado?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Lo que esta flota ya ha pagado Valve para existir"
          },
          {
            "level": 2,
            "id": null,
            "text": "Dónde se encuentra la flota"
          },
          {
            "level": 3,
            "id": null,
            "text": "Cuentas bloqueadas por país declarado"
          },
          {
            "level": 2,
            "id": null,
            "text": "Cuentas recientes, no un volumen de trabajo atrasado heredado"
          },
          {
            "level": 3,
            "id": null,
            "text": "Cuándo se crearon las cuentas bloqueadas"
          },
          {
            "level": 2,
            "id": null,
            "text": "Cuando Valve entra en vigor, lo hace dentro del primer año"
          },
          {
            "level": 3,
            "id": null,
            "text": "¿Cuánto tiempo llevaba abierta la cuenta cuando se le impuso la suspensión?"
          },
          {
            "level": 2,
            "id": null,
            "text": "Cuando Valve se activa, no detiene al bot"
          },
          {
            "level": 3,
            "id": null,
            "text": "Por qué motivo se ha expulsado realmente a los 11% que están expulsados"
          },
          {
            "level": 2,
            "id": null,
            "text": "Los estafadores Valve, vamos allá: el censo completo 51,732"
          },
          {
            "level": 3,
            "id": null,
            "text": "Estafadores confirmados, según si Valve les ha impuesto una suspensión relacionada con la estafa (Censo completo)"
          },
          {
            "level": 4,
            "id": null,
            "text": "Dos poblaciones, un hallazgo"
          },
          {
            "level": 2,
            "id": null,
            "text": "La auditoría empírica de las cuentas «100,000»: las redes de bots no son cuentas gratuitas desechables"
          },
          {
            "level": 3,
            "id": null,
            "text": "100,000 Corte imparcial"
          },
          {
            "level": 3,
            "id": null,
            "text": "Margen de error < ±0.4%"
          },
          {
            "level": 3,
            "id": null,
            "text": "Por qué cualquier 100k da el mismo resultado"
          },
          {
            "level": 3,
            "id": null,
            "text": "100,000 Cuentas bloqueadas: de pago ($5+ gasto en la tienda) frente a cuentas gratuitas con estado limitado"
          },
          {
            "level": 3,
            "id": null,
            "text": "La realidad estructural: la liquidación de cuentas a escala industrial"
          },
          {
            "level": 2,
            "id": null,
            "text": "Cómo se ha interpretado esto y qué es lo que no afirma"
          },
          {
            "level": 3,
            "id": null,
            "text": "Objeto de la reivindicación"
          },
          {
            "level": 3,
            "id": null,
            "text": "Lo que no se reivindica"
          },
          {
            "level": 3,
            "id": null,
            "text": "Por qué es importante"
          }
        ],
        "links": [
          "https://help.steampowered.com/en/faqs/view/71D3-35C2-AD96-AA3A",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/asf-ban-census-2026-09-23.json",
          "https://phishdestroy.io/steam_dossier/es/VALVE_EVIDENCE_PACK/databases/steamrep_steam_bans.csv",
          "https://phishdestroy.io/live-intel/?category=steam",
          "https://phishdestroy.io/steam_dossier/es/card_economy.html",
          "https://phishdestroy.io/steam_dossier/es/VALVE_EVIDENCE_PACK/databases/banned_archiasf_massive.csv",
          "https://phishdestroy.io/steam_dossier/es/VALVE_EVIDENCE_PACK/databases/slice_100k_limited_results.csv",
          "https://phishdestroy.io/steam_dossier/es/VALVE_EVIDENCE_PACK/reports/BANNED_100K_FORENSIC_ANALYSIS.md",
          "https://phishdestroy.io/steam_dossier/es/VALVE_EVIDENCE_PACK/databases/banned_100k_slice.csv",
          "https://phishdestroy.io/steam_dossier/es/VALVE_EVIDENCE_PACK/reports/STEAM_BANNED_LIMIT_ANALYSIS.md",
          "https://phishdestroy.io/steam_dossier/es/VALVE_EVIDENCE_PACK/INVESTIGATION_OVERVIEW.md",
          "https://phishdestroy.io/steam_dossier/es/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/es/VALVE_EVIDENCE_PACK/reports/STEAMREP_VS_STEAM_AUDIT.md",
          "https://phishdestroy.io/steam_dossier/es/VALVE_EVIDENCE_PACK/databases/SteamRep_Profiles_BannedCaution_2024.csv",
          "https://phishdestroy.io/steam_dossier/es/security_timeline.html",
          "https://phishdestroy.io/steam_dossier/es/VALVE_EVIDENCE_PACK/reports/russian_conflicts_report.json",
          "https://phishdestroy.io/steam_dossier/es/VALVE_EVIDENCE_PACK/reports/classification_report.json",
          "https://phishdestroy.io/steam_dossier/es/VALVE_EVIDENCE_PACK/reports/VALVE_INCOMPETENCE_REPORT.md",
          "https://phishdestroy.io/steam_dossier/es/steam_evidence_archive.html",
          "https://phishdestroy.io/steam_dossier/es/steam_enforcement_evidence.html",
          "https://phishdestroy.io/steam_dossier/es/#insider-threat",
          "https://phishdestroy.io/steam_dossier/es/"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/es/enforcement_audit.content.json",
      "export_json_sha256": "56e79d7a9805d5590ba9fb5db3e32f555556768831c5bb1e501ba3bb2515a187"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "es/index.html",
      "language": "es",
      "title": "El dossier «Steam»: normas, itinerarios y rendición de cuentas",
      "source_url": "https://phishdestroy.io/steam_dossier/es/index",
      "source_html_sha256": "5550df66679b0b90eb1cb8b17cc22d925283ccc3678ae271449808d216a5eb6a",
      "exported_at": "2026-09-29T00:17:24.594Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "exhibit-gallery-section",
            "source": "https://phishdestroy.io/steam_dossier/es/index#exhibit-gallery-section"
          }
        ],
        "raster_images_replaced": 2
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "index.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/es/index.pdf?v=print-20260929-v5",
        "sha256": "36a941e2d7f12e450e8a164140e9c23c8ecb8b1981cbf3eb61bab7966cc6ac77",
        "bytes": 964002,
        "pages": 111
      },
      "integrity": {
        "signed_object": "index.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "index.content.json.asc",
        "digest_file": "index.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify index.content.json.asc index.content.json",
          "sha256sum -c index.content.json.sha256"
        ]
      },
      "content": {
        "text": "Sección 1 — Resumen del caso\nLa norma. El récord. Las preguntas sin respuesta.\nContexto y límites de la fuente\n\nSeis conclusiones, cada una de ellas vinculada a un documento público con fecha. Las secciones detalladas siguen el mismo orden: expediente técnico (Parte A), normativa y expediente de cumplimiento (Parte B), marcos jurídicos (Parte C) y, a continuación, los anexos con las pruebas documentales principales.\n\nSeis conclusiones. Cada una de ellas relaciona una norma escrita con un registro fechado y una hipótesis que puede contrastarse con las pruebas.\n\n1. Hosts de autenticación de dominios independientes: 44 rutas · 26 pares divididos\n\nLos registros de personas en situación de desempleo 44 plataformas que se autentifican a través de un dominio independiente registrable. Hay otras cinco rutas pendientes de verificación que esperan una fecha de RDAP; si se incluyeran, el total ascendería a 47. Quedan excluidas de la cifra de 44 y de la tabla de antigüedad. — 27 con un archivo de pruebas publicado por ruta y 17 añadidos a partir de una recopilación manual, que se enumeran por separado. En 26 pares de filtros divididos El dominio principal es BLOQUEADO en el filtro de enlaces Steam, mientras que el proxy que utiliza sus datos de inicio de sesión no lo está. No se trata de dominios temporales: csgogem.com está bloqueado, mientras que api.csgem.com, el servidor con el nombre de usuario Steam, está registrado desde marzo de 2014 — 12 años y 6 meses. Valve recibe ese nombre de host en cada solicitud de OpenID y se lo muestra al usuario en su propia página de inicio de sesión. En la sección 3 se incluyen la tabla completa, las edades por ruta y el origen.\n\nSigue la ruta →\n2. 2016: se dio nombre al mecanismo y se fijó el plazo\n\nEl 13 de julio de 2016, Valve describió públicamente cómo los sitios de apuestas utilizaban Steam OpenID y cuentas de trading automatizadas, y las notificaciones de su abogado, de fecha 20 de julio de 2016, fijaron un plazo de diez días. Desde entonces no se ha publicado ningún registro de medidas coercitivas por operador. Diez años después de que se fijara dicho plazo, el mismo mecanismo mencionado se sigue utilizando en servidores de autenticación de dominios independientes que no devolvieron ningún bloqueo de Link Filter en 2026-09-21.\n\nLee la carta abierta dirigida al WSGC →\n3. Correlación de dispositivos, en papel con membrete del bufete\n\nEn la correspondencia que aquí se reproduce, el abogado de Valve describió una correlación a nivel de dispositivo que vincula un dispositivo con varias cuentas, una función que el servicio de asistencia de Steam había indicado previamente a los usuarios que no era técnicamente posible. La cuestión que queda pendiente es qué registros a nivel de dispositivo conserva Valve y en qué se basa para denegar el acceso a los titulares de las cuentas.\n\nLee el memorándum →\n4. Dos respuestas respecto al acceso. Una denegó el acceso a los datos y la otra los filtró.\n\nOctubre de 2025: El abogado de Valve respondió a una solicitud en virtud del artículo 15 con un anexo de 830 páginas en el que las partes censuradas se han tachado sobre el texto en lugar de eliminarlas — 902,270 caracteres volver a mostrar los datos con una herramienta de extracción estándar, incluidos los identificadores de terceros que esas barras tenían por objeto ocultar. El apartado 4 del artículo 15 es la razón por la que existen esas barras. Septiembre de 2026: El ticket HT-2YBP-F7JP-D4VB se cerró al cabo de tres días con un enlace a la página de autoservicio «Datos de la cuenta»: sin datos y sin indicar el fundamento jurídico. El plazo de un mes previsto en el artículo 12, apartado 3, aún no había vencido en el momento de la publicación; la objeción se refiere al fondo del asunto.\n\nLee la revisión del texto →Leer el registro del ticket →\n5. El mercado por encima del techo de Steam\n\nSteam limita la cotización en bolsa a unos $1,800. En cinco mercados, según una instantánea de fecha pasada (23 de septiembre de 2026), 248 categorías de artículos CS2 dos o más de ellos, de forma independiente, fijen un precio superior a ese límite máximo, y los 248 están ausentes de Steam; un «Dragon Lore» nuevo de fábrica cuesta a partir de $10,941 en 389 copias que figuran en las cinco listas (la cifra correspondiente únicamente a CSFloat de la sección 13, procedente de la instantánea del 20 de septiembre, es de $10,623.95 en 62 ofertas). Vender a esos precios requiere una plataforma externa, mientras que la transferencia de artículos sigue realizándose a Steam.\n\nSigue el precio y realiza la transferencia →\n6. La norma es explícita; el registro de auditoría no lo es.\n\nEl Acuerdo de suscripción reserva Steam para uso personal y no comercial, prohíbe la explotación comercial salvo en los casos expresamente permitidos, prohíbe el uso de scripts y bots, y permite la cancelación de la cuenta. Valve aplicó esa cláusula a los operadores de juegos de azar en 2016. Por otra parte, según la cuenta de ingeniería de CSFloat, Valve cerró IEconItems_730/GetPlayerItems En 2017, se eliminó el acceso público a los identificadores originales de los elementos (no se ha encontrado ningún registro de cambios Valve).\n\nColoca la regla junto a la red →\n2016 / Reclamación por escrito 10 días\nPlazo establecido en las notificaciones enviadas por el abogado en julio de 2016 a los sitios web de apuestas. Carta abierta a la WSGC: Sección 2.\n2017 / Registro público de auditoría Acceso con identificación cerrado\nCSFloat registra la pérdida de los ID originales de los elementos.\nCorrespondencia con los abogados Correlación de dispositivos\nUn dispositivo vinculado a decenas de cuentas robadas.\nRegistro de rutas Bloqueado, pero sigo iniciando sesión\nLa norma: La declaración de Valve de 2016 prohíbe gestionar un negocio de apuestas en Steam OpenID. El historial: El filtro de enlaces contiene 26 dominios principales, mientras que el servidor que aloja el inicio de sesión Steam de cada uno de ellos lleva funcionando… el de csgogem.com lleva 12 años y 6 meses en funcionamiento.\nSección 2 — Carta abierta\nCarta abierta a la Comisión de Juegos de Azar del Estado de Washington\n\nDiez días se convirtieron en diez años. La Comisión no ha recibido una respuesta con un registro operador por operador a la pregunta que formuló en 2016 a Valve; en esta carta se le solicita que reabra el expediente.\n\nCOMUNICADO PÚBLICO · COMISIÓN DE JUEGOS DE AZAR DEL ESTADO DE WASHINGTON\n\nDiez días se convirtieron en diez años.Vuelve a abrir el expediente.\n\nA la Comisión de Juegos de Azar del Estado de Washington:\n\nEn 2016, el director David Trujillo pidió a Valve que explicara qué medidas había tomado para impedir el uso de skins Steam con fines de juego. El entonces presidente, Chris Stearns, y la Comisión se enfrentaron a un sector basado en artículos emitidos por Valve y transferencias de Steam. Desde entonces, ambos han dejado sus cargos en la Comisión. La pregunta que plantearon a Valve sigue sin respuesta.\n\nEl consejero general de Valve, Karl Quackenbush, concedió a los operadores de juegos de azar un plazo de diez días para poner fin al uso comercial de las cuentas de Steam. En su respuesta de octubre a su Comisión, Valve negó haber facilitado el juego, afirmó que había enviado cartas de cese y desistimiento a más de cuarenta sitios web y señaló que había desactivado las cuentas asociadas. Asimismo, defendió el mantenimiento de Steam Trading y OpenID, ya que dichos servicios beneficiaban a los clientes y a los desarrolladores de juegos. Eso fue una demostración de control. Merece ser puesta a prueba, no ser aceptada sin más.\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\nEn nuestra evaluación, la respuesta de Valve no demostró que las medidas coercitivas elegidas se ajustaran a la magnitud de la red que describía. Una carta amenazante dirigida a un operador no es lo mismo que un bloqueo permanente de las cuentas Steam, la infraestructura comercial y las rutas de autenticación que hacen funcionar el negocio. Según las estimaciones publicadas, Solo CS:GO Lounge superó los $1 mil millones en volumen de apuestas durante 2016; se trata de una estimación externa de las apuestas, no de los ingresos Valve, y la actividad original de apuestas con «skin» del sitio web se cerró posteriormente. La magnitud del fenómeno hizo imprescindible una aplicación de la ley verificable.\n\nHoy, el propio Valve Contrato de suscripción archivado 2026-09-21 ↗ restringe la explotación comercial, salvo en los casos en que se permita expresamente, y prohíbe por separado determinadas formas de automatización. Nuestra registro de rutas con fecha registros que indican los hosts de respuesta de OpenID para servicios externos; openid.realm y openid.return_to son campos que se envían a Steam, no secretos que se le ocultan. Nuestros Comprobaciones del filtro de enlaces muestra casos en los que se emitió una advertencia sobre una dirección principal, pero no sobre un servidor de inicio de sesión asociado. Un resultado del filtro por sí solo no puede demostrar que Valve permitiera un inicio de sesión o que un bot concreto eludiera el bloqueo de una cuenta. Esto demuestra que una advertencia en la página de inicio no puede considerarse una respuesta exhaustiva en materia de acceso.\n\nTampoco la existencia de funciones útiles y lícitas de comercio Steam y de OpenID permite determinar si los operadores prohibidos quedaron realmente excluidos. Las propias normas de Valve admiten excepciones expresas. Si Valve se basa en esa distinción, la Comisión debería pedirle que identifique la autorización, los controles de cuentas y los criterios de aplicación aplicables a las empresas comerciales de «skins», así como los usos específicos no relacionados con el juego a los que invocó en 2016. La mera posibilidad de un uso lícito no es respuesta a un uso prohibido documentado.\n\nSolicitamos a la Comisión que revise su expediente de 2016 y pida un informe por operador: qué cuentas Steam y bots de negociación se desactivaron tras los avisos de diez días; si se supervisaron las cuentas relacionadas o los servidores de retorno; qué operadores recuperaron posteriormente el acceso; qué exenciones se concedieron; y qué registros respaldan la declaración de Valve ante la Comisión. Publique todo lo que la ley permita al público examinar. Compare esos registros con las rutas actuales y con las intervenciones posteriores de Valve, incluidas OPSkins en 2018 archivado 2026-03-07 ↗.\n\nLa notificación fijaba un plazo de diez días en julio de 2016; diez años son tiempo suficiente para determinar si se llevó a cabo. La Comisión debería contrastar el informe de 2016 de Valve con las infraestructuras que aún se pueden observar en la actualidad.\n\nLa investigación del Dossier Steam · Comunicado público, 20 de septiembre de 2026\n\nComunicación de la Comisión de 2016 ↗ archivado 2026-05-20 ↗ · Respuesta de Valve de 2016 (copia del documento) ↗ · Declaración de OpenID de Valve de 2016 ↗ archivado 2026-09-21 ↗ · Acuerdo actual Steam ↗ archivado 2026-09-21 ↗ · Cronología del intercambio de 2016: Sección 11 →\n\nParte A — Ficha técnica · Sección 3\nEl sitio está bloqueado. La ruta de inicio de sesión no lo está.\n\n26 dominios principales bloqueados. El proxy de autenticación que hay detrás de cada uno de ellos y el tiempo que lleva activo. Estos servidores de autenticación independientes no son direcciones secundarias accidentales: cada uno de ellos es un proxy de autenticación para Steam, situándose entre la plataforma y el punto final OpenID de Valve y gestionando el inicio de sesión que el dominio bloqueado ya no puede realizar de forma abierta. Valve colocó la «puerta principal» en el Link Filter. El inicio de sesión siguió realizándose a través del proxy: csgogem.com está bloqueado, y api.csgem.com está registrado desde marzo de 2014 — doce años y medio. Cada uno de esos días, ese servidor enviaba su propio nombre de host al punto final de OpenID de Valve, y Steam se lo mostraba directamente al usuario en la página de inicio de sesión. Valve es el tronco por el que discurren todas estas rutas; no tiene que buscarlas. Eso es lo que mide esta sección: no si existe una advertencia, sino cuántos años permanece abierta la ruta situada tras la advertencia. En el registro figuran 44 rutas de dominio independiente, 27 de ellas con un archivo de pruebas publicado para cada ruta —véase la tabla siguiente—. Analiza un ejemplo y, a continuación, evalúalas todas.\n\nFigura 3.1 — Las dos rutas, representadas gráficamente.\n\nUna plataforma, un usuario, dos solicitudes que salen del mismo navegador. El filtro de enlaces de Valve se aplica a ambas. Bloquea la que contiene un enlace y deja pasar la que contiene los datos de inicio de sesión. Todo lo que se mide en esta sección es el tiempo que permanece abierta la ruta inferior.\n\nThe player\none browser, one session\nrollbit.com\nthe platform's main domain\nrbsnin.com\nseparate authentication host\nLINK FILTER\n✕ BLOCKED\nLINK FILTER\n✓ CLEAN\nsteamcommunity.com\nOpenID endpoint · signs in\nno route\nEnlace publicado el Steam — suspendidoSolicitud de inicio de sesión — pasesCheques guardados de los días 19 y 21 de septiembre de 2026\n\nAmbas solicitudes son visibles para Valve, y solo se procesa una de ellas. El filtro de enlaces es una lista Valve, que comprueba un servicio Valve. La solicitud OpenID envía el nombre del propio servidor de autenticación al punto final de Valve, que lo muestra directamente en la página de inicio de sesión. El nombre de host aparece en la solicitud en cualquier caso; lo que varía es si se realiza alguna acción con él.\n\nUna plataforma. Dos rutas diferentes.ROLLBIT / OBSERVACIONES GUARDADAS\nPaso 5 / 5\n\nLa solicitud llega a Steam. La ruta observada llegó al formulario de inicio de sesión de Steam. Los autores no completaron el inicio de sesión. El bloqueo del enlace del dominio principal no impidió esta ruta observada hacia el formulario.\n\n01 COMPROBACIÓN DEL FILTRO DE ENLACES\nDESTINOrollbit.comEl dominio principal de la plataforma\nFILTRO DE CONEXIÓN DE VAPORComprueba el enlaceUn sistema independiente de aviso de destino\nRESULTADO GUARDADOEnlace bloqueado19 y 21 de septiembre de 2026\n02 LA RUTA DE INICIO DE SESIÓN OBSERVADA\nEN EL ANDÉNIniciar sesión con SteamLa plataforma inicia una solicitud de OpenID\nHOST DE AUTENTIFICACIÓN INDEPENDIENTErbsnin.comNo hay ningún bloque «Filtro de enlaces» en la comprobación guardada\nSTEAMSe ha mostrado el formulario de inicio de sesiónEl servidor solicitado aparece en el aviso de Steam\nComprueba las notas originales de la captura, la fecha de registro y los datos del protocolo.\nCómo se aplica la norma Valve\nDominio principal: bloqueado\nUsuario\n→\nrollbit.com\n(dominio principal)\n↓\nFILTRO DE STEAM LINK — BLOQUEADO\n«¡Enlace bloqueado!» — marcado como potencialmente malicioso\nrollbit.com devolvió un bloqueo del filtro de enlaces en 2026-09-19 y 2026-09-21 (comprobación sin autenticación; se guardaron el HTML sin procesar y el SHA-256). Un registro visible y auditable.\nQué ocurre realmente: la autenticación\nServidor de autenticación: no bloqueado\nUsuario\n→\nrollbit.com\n«Iniciar sesión con Steam»\n↓\nRedirigir a través de un servidor de autenticación independiente:\nrbsnin.comFiltro de enlaces: LIMPIO\nregistrado 2026-09-18T09:34:52Z (Verisign RDAP)\n↓\nSteam Aviso en la página de inicio de sesión (2026-09-20):\n\"Note that rbsnin.com is not affiliated with Steam or Valve\"\nSteam muestra este aviso procedente del openid.realm de la solicitud que ha recibido.\n↓\nSteam Formulario de inicio de sesión servido desde un servidor independiente\nLos autores no completaron el proceso de inicio de sesión; se observó el proceso hasta el formulario «Steam».\nValve recibe el nombre de host «return_to / realm» en cada una de esas solicitudes. rbsnin.com no devolvió ningún bloqueo del filtro de enlaces en 2026-09-21.\nA petición\nComo proveedor de OpenID, Steam recibe el nombre de host de autenticación con cada solicitud de autenticación: este llega a los propios servidores de Valve en el openid.return_to y openid.realm parámetros.\nEnviado por la página web\nEl servidor de autenticación no se detecta mediante el escaneo; la plataforma lo envía a Steam en cada solicitud. Según OpenID 2.0, apartado 9.1 return_to Es opcional desde el punto de vista técnico, pero sin él Steam no puede proporcionar el resultado del inicio de sesión, por lo que, para que el inicio de sesión con Steam funcione, es prácticamente obligatorio. Steam incluso muestra el nombre de host al usuario («<host> no está vinculado a Steam ni a Valve\").\n14 años\nes la antigüedad del servidor de autenticación más antiguo que aún mantiene Steam inicios de sesión en la comprobación 2026-09-21 (dota2.net, registrado hace 2011-10-29); el más reciente tiene tres días de antigüedad (rbsnin.com). No interpretes la cifra «0 hosts de autenticación bloqueados» como el resultado. Un host de autenticación bloqueado inutilizaría por completo la función «Iniciar sesión con Steam» de la plataforma, por lo que un registro creado a partir de inicios de sesión válidos solo puede contener hosts que nunca hayan sido bloqueados. La cifra que tiene importancia no es el recuento de bloqueos, sino el número de años que el dominio principal permaneció en el filtro de enlaces mientras que el inicio de sesión asociado a él siguió funcionando.\nServidores de autenticación de dominios independientes: fecha de registro frente al dominio principal (30 rutas: las 25 resueltas en la auditoría del navegador 2026-09-21, más 5 añadidas en 2026-09-22)\nPlataforma\tFiltro de enlaces: principal\tServidor de autenticación\tFiltro de enlaces: host de autenticación\tSe ha registrado el servidor de autenticación\tFuente de la observación\tExpediente de pruebas\nRollbit\nrollbit.com · reg. 2014-11-08\n\tBLOQUEADO\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\trbsnin.com\tLIMPIO\n2026-09-21 · HTML sin formato (no hay copia de Wayback)\n\t2026-09-18\n09:34:52Z, Verisign RDAP\n\tSteam Aviso en la página de inicio de sesión, 2026-09-20\trollbit.com.json\nSkin.Club\nskin.club · reg. 2017-09-04\n\tBLOQUEADO\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\tsc-auth.net\tLIMPIO\n2026-09-21 · Wayback 2026-09-21\n\t2019-04-02\nRDAP\n\tSteam Aviso de la página de inicio de sesión\tskin.club.json\nHowl.GG\nhowl.gg · reg. 2017-03-16\n\tBLOQUEADO\n2026-09-18, 19 de septiembre, 21 de septiembre · Wayback 2026-09-21\n\thowl.uno\tLIMPIAR\n2026-09-21 · Wayback 2026-09-21\n\t2026-08-11\nRDAP\n\tCaptura en directo del navegador + URL de OpenID facilitada\thowl.gg.json\nDuelbits\nduelbits.com · reg. 2020-02-03\n\tBLOQUEADO\n2026-09-21 · Wayback 2026-09-21\n\tswitchflips.com\tLIMPIO\n2026-09-21 · Wayback 2026-09-21\n\t2020-04-21\nRDAP\n\tURL de OpenID facilitada\tduelbits.com.json\nCSGOFast\ncsgofast.com · reg. 2015-03-27\n\tBLOQUEADO\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\tsteam-login.authtofast.com\tLIMPIO\nauthtofast.com, 2026-09-21 · Wayback 2026-09-21\n\t2026-06-30\nauthtofast.com, RDAP\n\tCaptura en directo del navegador + URL de OpenID facilitada\tcsgofast.com.json\nFarmskins\nfarmskins.com · reg. 2016-03-23\n\tBLOQUEADO\n2026-09-19, 2026-09-21 · HTML sin formato\n\tsteam.kobal.cc\tLIMPIO\n2026-09-19, 2026-09-21 · HTML sin formato\n\t2017-01-07\nkobal.cc, RDAP\n\tCaptura en directo del navegador + URL de OpenID facilitada\tfarmskins.com.json\nCobaltLab\ncobaltlab.tech\n\tBLOQUEADO\n2026-09-21 · HTML sin formato\n\tcobaltauth.com\tLIMPIO\n2026-09-21 · HTML sin formato\n\t2025-01-07\nRDAP\n\tURL de OpenID facilitada\tcobaltlab.tech.json\nCSGO.NET\ncsgo.net · reg. 2012-07-22\n\tBLOQUEADO\n2026-09-21 · HTML sin formato\n\tcn2.easylot.net\tLIMPIO\n2026-09-21 · HTML sin formato\n\t2016-09-03\neasylot.net, RDAP\n\tCaptura en directo del navegador\tcsgo.net.json\nGGDrop\nggdrop.com\n\tBLOQUEADO\n2026-09-21 · HTML sin formato\n\tggauth.com\tLIMPIO\n2026-09-21 · HTML sin formato\n\t2023-05-03\nRDAP\n\tURL de OpenID facilitada\tggdrop.com.json\nRustChance\nrustchance.com\n\tBLOQUEADO\n2026-09-21 · HTML sin formato\n\thgfuihd.com\tLIMPIO\n2026-09-21 · HTML sin formato\n\t2019-01-27\nRDAP\n\tURL de OpenID facilitada\trustchance.com.json\nSkin.Fans\nskin.fans\n\tBLOQUEADO\n2026-09-21 · HTML sin formato\n\tauth.skinfans.com\tLIMPIO\n2026-09-21 · HTML sin formato\n\t2018-07-16\nskinfans.com, RDAP\n\tURL de OpenID facilitada\tskin.fans.json\nSkinport\nskinport.com · reg. 2018-09-05\n\tBLOQUEADO\n2026-09-21 · HTML sin formato\n\tskinport.app\tLIMPIO\n2026-09-21 · HTML sin formato\n\t2020-06-20\nRDAP\n\tCaptura en directo del navegador + URL de OpenID facilitada\tskinport.com.json\nSkins.Cash\nskins.cash\n\tBLOQUEADO\n2026-09-21 · HTML sin formato\n\tskinscash.live\tLIMPIO\n2026-09-21 · HTML sin formato\n\t2019-12-05\nRDAP\n\tURL de OpenID facilitada\tskins.cash.json\nTF2Hunt\ntf2hunt.com · reg. 2018-01-13\n\tBLOQUEADO\n2026-09-21 · HTML sin formato\n\trstspcl.com\tLIMPIO\n2026-09-21 · HTML sin formato\n\t2020-08-08\nRDAP\n\tCaptura en directo del navegador + URL de OpenID facilitada\ttf2hunt.com.json\nCSGOGem\ncsgogem.com · reg. 2016-10-16\n\tBLOQUEADO\n2026-09-22 · HTML sin formato\n\tapi.csgem.com\ncsgem.com — dominio independiente que se puede registrar\n\tLIMPIO\n2026-09-22 · HTML sin formato\n\t2014-03-08\ncsgem.com, RDAP — el más antiguo del registro\n\tRecopilación manual + Captura mediante el filtro de enlaces\tlinkfilter-2026-09-22.json\nGamdom\ngamdom.com · reg. 2016-07-29\n\tBLOQUEADO\n2026-09-22 · HTML sin formato\n\tlogin.gambldom.com\ngambldom.com — solo una letra diferente de la marca\n\tLIMPIO\n2026-09-22 · HTML sin formato\n\t2017-09-24\ngambldom.com, RDAP\n\tRecopilación manual + Captura mediante el filtro de enlaces\tlinkfilter-2026-09-22.json\n12CS\n12cs.fail · reg. 2026-03-24\n\tBLOQUEADO\n2026-09-22 · HTML sin formato\n\tfail.games\tLIMPIO\n2026-09-22 · HTML sin formato\n\t2021-08-24\nfail.games, RDAP\n\tRecopilación manual + Captura mediante el filtro de enlaces\tlinkfilter-2026-09-22.json\nCSGOEmpire\ncsgoempire.com · reg. 2015-06-10\n\tLIMPIO\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\tcsgoempirelogin4.com\nuno de los diez dominios numerados login1–10\n\tLIMPIO\n2026-09-21 · Wayback 2026-09-21\n\t2020-07-20\n05:49:17Z, Verisign RDAP\n\tCaptura en directo del navegador\tcsgoempire.com.json\nCS.MONEY\ncs.money\n\tLIMPIO\n2026-09-21 · HTML sin formato\n\tauth.dota.trade\tLIMPIO\n2026-09-21 · HTML sin formato\n\t2016-07-15\ndota.trade, RDAP\n\tSteam Aviso en la página de inicio de sesión\tcs.money.json\nCSFloat\ncsfloat.com · reg. 2021-07-11\n\tLIMPIO\n2026-09-21 · HTML sin formato\n\tcsgofloat.com\nantiguo dominio de marca del operador; dominio registrable independiente, no constituye un indicador de evasión\n\tLIMPIO\n2026-09-21 · HTML sin formato\n\t2015-09-29\nRDAP\n\tCaptura en directo del navegador\tcsfloat.com.json\nG4Skins\ng4skins.com\n\tLIMPIO\n2026-09-21 · HTML sin formato\n\tauth.g4s.to\tLIMPIO\n2026-09-21 · HTML sin formato\n\t2021-05-30\ng4s.to, RDAP\n\tURL de OpenID facilitada\tg4skins.com.json\nJuice.GG\njuice.gg\n\tLIMPIO\n2026-09-21 · HTML sin formato\n\tletmeinjuice.com\tLIMPIO\n2026-09-21 · HTML sin formato\n\t2024-04-15\nRDAP\n\tURL de OpenID facilitada\tjuice.gg.json\nMarket.CSGO\nmarket.csgo.com\n\tLIMPIO\n2026-09-21 · HTML sin formato\n\tdota2.net\tLIMPIO\n2026-09-21 · HTML sin formato\n\t2011-10-29\nRDAP\n\tCaptura en directo del navegador + URL de OpenID facilitada\tmarket.csgo.com.json\nRust.TM\nrust.tm\n\tLIMPIO\n2026-09-21 · HTML sin formato\n\tdota2.net\tLIMPIO\n2026-09-21 · HTML sin formato\n\t2011-10-29\nRDAP\n\tURL de OpenID facilitada\trust.tm.json\nCSGOLounge\ncsgolounge.com · reg. 2013-08-14\n\tLIMPIO\n2026-09-22 · HTML sin formato\n\tdota2.net\ntercer front-end en este servidor de autenticación\n\tLIMPIO\n2026-09-22 · HTML sin formato\n\t2011-10-29\ndota2.net, RDAP\n\tRecopilación manual + Captura mediante el filtro de enlaces\tlinkfilter-2026-09-22.json\nDota2Lounge\ndota2lounge.com · reg. 2012-08-10\n\tLIMPIO\n2026-09-22 · HTML sin formato\n\tdota2.net\ncuarto front-end en este servidor de autenticación\n\tLIMPIO\n2026-09-22 · HTML sin formato\n\t2011-10-29\ndota2.net, RDAP\n\tRecopilación manual + Captura mediante el filtro de enlaces\tlinkfilter-2026-09-22.json\nSkinBaron\nskinbaron.de\n\tLIMPIO\n2026-09-21 · HTML sin formato\n\tskinbaron.com\nmisma marca, dominio de nivel superior diferente\n\tLIMPIO\n2026-09-21 · HTML sin formato\n\t2015-12-22\nRDAP\n\tURL de OpenID facilitada\tskinbaron.de.json\nTF2Royal\ntf2royal.com · reg. 2022-08-17\n\tLIMPIO\n2026-09-21 · HTML sin formato\n\ttf2auth.com\tLIMPIO\n2026-09-21 · HTML sin formato\n\t2021-07-27\nRDAP\n\tCaptura en directo del navegador + URL de OpenID facilitada\ttf2royal.com.json\nTradeit\ntradeit.gg\n\tLIMPIO\n2026-09-21 · HTML sin formato\n\tconnect-tradeit.com\tLIMPIO\n2026-09-21 · HTML sin formato\n\t2022-02-23\nRDAP\n\tURL de OpenID facilitada\ttradeit.gg.json\nActualizador\nupgrader.pro\n\tLIMPIO\n2026-09-21 · HTML sin formato\n\tupgauth.space\tLIMPIO\n2026-09-21 · HTML sin formato\n\t2026-08-14\nRDAP\n\tURL de OpenID facilitada\tupgrader.pro.json\nFuente: steamcommunity.com/linkfilter, GET sin autenticación, 2026-09-21, 53 hosts, intervalo de 3 s; steam_tos_assets/linkfilter-recheck-2026-09-21.json; código HTML sin formato en steam_tos_assets/linkfilter-raw/. Fechas de inscripción: RDAP, steam_tos_assets/domain-registration.json. · Comprobación previa de 2026-09-19 en linkfilter-all-results.json · registros de rutas en auth-route-audit.json · Instantáneas de Wayback Machine de las páginas de Link Filter, 2026-09-21, que figuran en wayback-snapshots.json (No existe ninguna instantánea de rbsnin.com; el archivo sin procesar local es el único registro).\n\nFechas de inscripción: RDAP (steam_tos_assets/domain-registry/). La «URL de OpenID facilitada» establece los parámetros de la solicitud, no un inicio de sesión completado. Los autores no completaron ningún inicio de sesión en ninguna plataforma. Un dominio independiente no es, por sí solo, prueba de evasión. Tampoco es «0 hosts de autenticación bloqueados» un hallazgo independiente: bloquear uno interrumpiría el inicio de sesión Steam de esa plataforma, por lo que un registro elaborado a partir de inicios de sesión válidos no puede contener un host de autenticación bloqueado. La observación que tiene peso es la asociación y su duración: un dominio principal en el filtro de enlaces junto a un dominio de inicio de sesión que lleva años en funcionamiento. Esta tabla contiene 30 filas: 25 de las 27 rutas con un archivo de pruebas por ruta, más cinco añadidas en 2026-09-22 cuya división en el filtro de enlaces se recoge en linkfilter-2026-09-22.json aunque el dominio en sí se recopiló manualmente — así lo indican sus filas en la columna «fuente». Las dos rutas de los archivos de evidencia que no se muestran son skinsnipe.com (host de autenticación pricing.tradeupspy.com, registrado 2020-03-11) y csgobig.com (host de autenticación letmeinbig.com, registrado 2023-01-20); ambos devolvieron «BLOQUEADO» (main) / «LÍPIDO» (auth host) en la comprobación de 2026-09-22, registrado con SHA-256 en linkfilter-2026-09-22c.json, pero el código HTML sin formato de ese lote no se incluye en el conjunto publicado, por lo que aquí se mencionan por su nombre en lugar de asignárseles una fila, como se puede comprobar en todas las demás líneas de esta tabla. Las 12 rutas restantes del registro, recopiladas manualmente, se identifican como tales en master_registry.json debajo de realm_src: user.\n\nAuditoría empírica primaria · Intervalo de fechas plurianual\nLa trampa del panorama general: el filtro de enlaces es una farsa de cumplimiento normativo, no un escudo\n\nEn los navegadores de ordenador, los usuarios están protegidos por defensas externas: Google Safe Browsing y Microsoft SmartScreen interceptan los intentos de phishing conocidos y muestran avisos rojos a pantalla completa. En el modo «Big Picture» de Steam, en la superposición del juego (Shift+Tab) y en el Deck Steam (SteamOS), esas defensas no existen. El navegador integrado no admite ninguna extensión, desactiva los motores externos de «Navegación segura» y deja al usuario con una única barrera de protección: la de Valve. linkfilter intersticial.\n\nDesliza para comparar los cuatro resultados →\n\n92.5%\n2025-2026: phishing de última generación aprobado sin problemas (37/40)\n77.5%\nPhishing de la era CS2 (2023-2024) aprobado sin objeciones (31/40)\n70.0%\nCaso de phishing heredado de 2021-2022 aprobado sin problemas (28/40)\n7 / 7\nlíneas principales de juego bloqueadas (control positivo)\nAuditoría longitudinal plurianual: 120 dominios de phishing «puros» Steam sometidos a pruebas en tiempo real (24 de septiembre de 2026)\n\nPara comprobar si el filtro de Valve simplemente tarda en detectar nuevas amenazas o si, por el contrario, es incapaz de detectarlas, hemos realizado una auditoría de 120 dominios de phishing confirmados específicos de Steam en tres cohortes históricas, en comparación con steamcommunity.com/linkfilter:\n\nPromoción 1: 2021-2022 (Oferta de intercambio clásica y objetos que se obtienen al completar misiones) — 70.0% Superado sin fallos (28/40). Incluso entre cuatro y cinco años después de haber sido catalogados por los organismos de control comunitarios, siete de cada diez servidores de phishing heredados siguen activos sin ningún tipo de bloqueo.\nPromoción 2: 2023-2024 (CS2 Beta: expectación y apelaciones de soporte falsas) — 77.5% Aprobado sin fallos (31/40). Campañas que se hacen pasar por lanzamientos de Counter-Strike 2 y peticiones falsas de la comunidad (p. ej., cs2-steam.com, appealsteamcommunity.help) pasan directamente.\nCohorte 3: 2025-2026 (Implementaciones en el borde sin servidor y clones de favicons) — 92.5% Aprobado sin fallos (37/40). Kits modernos de phishing que se implementan en EdgeOne, Vercel y Cloudflare Pages (p. ej., steamgifter.online, steam-dp4lt5b8fnez.edgeone.dev) pasan prácticamente sin obstáculos.\n\nTelemetría y exención de responsabilidad, no protección. ¿Por qué existe el filtro de enlaces si deja pasar 70% a 92.5% de un caso claro de phishing Steam? Sirve como exención de responsabilidad para la empresa y como sensor de telemetría de clics salientes. Al presentar un mensaje cortés «Estás saliendo de Steam» Aviso con un botón verde «Continuar» en el que se puede hacer clic; Valve atribuye la responsabilidad legal a la víctima en virtud del Steam Acuerdo de suscripción (*«el usuario ha navegado voluntariamente fuera de Steam»*). Valve recopila los datos de telemetría del clic, pero no impide el robo.\n\nLa prueba del hash del favicon: cero captación de fuentes de amenazas. Las plataformas independientes de inteligencia sobre amenazas (urlscan.io, Shodan, Censys) identifican kits de phishing activos Steam mediante una simple búsqueda del hash del favicon oficial de Steam (page.favicon.hash:9f890a9debcdfccc339149a7943be9aff9e4c9203c2fa37d5671a5b2c88503ad NOT domain:*.steampowered.com). Esta comprobación automática básica detecta grupos activos de phishing en cuestión de segundos. Valve no se sincroniza con fuentes externas, no realiza búsquedas de amenazas basadas en hash y solo interviene manualmente cuando así lo exigen las autoridades reguladoras (la orden sobre juegos de azar de la WSGC de 2016) o para proteger sus cadenas de dominio registradas como marcas comerciales.\n\nElementos de prueba de auditoría primarios: Auditoría longitudinal de 120 dominios a lo largo de varios años: auditoría-longitudinal-de-phishing-por-vapor.json · 100 muestras específicas de phishing Steam: linkfilter-steam-phishing-100.json · Auditoría general de la alimentación (n = 250): linkfilter-coverage-2026-09-22.json.\n\nCSGOEmpire — registro por lotes de diez dominios de autenticación numerados\n\nEl 2020-07-20 diez dominios numerados, csgoempirelogin1.com a través de csgoempirelogin10.com, quedaron registrados. Se conservan las marcas de tiempo RDAP de Verisign para los diez: login1 05:49:06Z, login5 05:49:08Z, login2 05:49:11Z, login3 05:49:14Z, login4 05:49:17Z, login6 05:49:20Z, login7 05:49:23Z, login8 05:49:26Z, login9 05:49:28Z — nueve dominios en 22 segundos — y login10 a las 05:56:03Z, siete minutos después. El intervalo entre ambos registros concuerda con una única operación masiva realizada por un registrador.\n\nEl patrón concuerda con los hosts de reserva preconfigurados; solo login4 Se ha observado en una solicitud de OpenID en tiempo real. Tanto csgoempire.com como csgoempirelogin4.com devolvieron el resultado «CLEAN» en el filtro de enlaces en 2026-09-21; CSGOEmpire no figuraba entre los sitios mencionados en las noticias de prensa sobre los avisos de julio de 2016.\n\n# DNS: los 10 están activos (septiembre de 2026)\nVale csgoempirelogin1.com 172.67.129.43\nVale csgoempirelogin2.com 172.67.175.168\nVale csgoempirelogin3.com 188.114.96.3\nVale csgoempirelogin4.com 188.114.96.11 ← en el tráfico de OpenID\nVale csgoempirelogin5.com 172.67.160.194\nVale csgoempirelogin6–10.com Direcciones IP de Cloudflare\nNXDOMAIN: csgoempirelogin11.com\nLos 10 están registrados 2020-07-20; los 10 tienen marca de tiempo RDAP (steam_tos_assets/domain-registry/csgoempireloginN.com.rdap.json)\nConclusión para las autoridades reguladoras\nSi se bloquea el dominio principal y no se bloquea el host de autenticación, la ruta de inicio de sesión queda abierta, y así permanece durante años.\n\nEl bloque «Link Filter» del dominio principal es un registro público y verificable. El servidor de autenticación transporta el tráfico de «Iniciar sesión con Steam» y aparece en los propios parámetros de solicitud OpenID de Valve. En las comprobaciones realizadas en 2026-09-21 y 2026-09-22, en 26 pares divididos por el filtro, el dominio principal devolvió un bloqueo del filtro de enlaces, mientras que el proxy que transportaba su inicio de sesión no devolvió ninguno. El registro anterior mide la otra mitad de eso: estos hosts no son dominios desechables de corta duración. Varios llevaban registrados más de una década en la fecha de la comprobación, y cada uno de esos días es un día en el que Valve recibió el nombre de host en sus propios parámetros de solicitud. Valve no ha publicado ningún registro de medidas coercitivas por operador, por lo que no se puede determinar a partir de los datos públicos si se aplicó alguna otra medida a estos hosts.\n\n12 años y 6 meses\ncsgogem.com está bloqueado en el filtro de enlaces.\nSu servidor de inicio de sesión api.csgem.com ha sido\nestá registrado desde 2014-03-08 y no lo está.\nResumen en lenguaje sencillo — Para organismos reguladores y tribunales (ampliar)\nResumen en lenguaje sencillo — para las autoridades reguladoras\nAntecedentes: qué es Steam y por qué es importante en este contexto\n\nSteam es una plataforma de software gestionada por Valve Corporation (Bellevue, Washington, EE. UU.). Steam actúa como proveedor de identidad digital: los sitios web de apuestas y juegos de azar en Internet utilizan un sistema denominado «Iniciar sesión con Steam», un botón que permite a un sitio web verificar que un visitante dispone de una cuenta Steam real. Esto es similar a «Iniciar sesión con Google» o a la comprobación de un documento de identidad oficial: el sitio web redirige al usuario a los servidores de Steam, Steam confirma su identidad y Steam lo devuelve al sitio web. Valve gestiona el sistema de autenticación. Cada inicio de sesión a través de «Iniciar sesión con Steam» pasa por los propios servidores de Valve.\n\nLo que hizo Valve: el bloqueo de dominios\n\nEn julio de 2016, tras la presión mediática y jurídica en torno a las apuestas con «skins», el abogado de Valve envió notificaciones a aproximadamente 23 sitios web de apuestas identificados (según informes de prensa del 21 de julio de 2016); en octubre de 2016, Valve comunicó a la Comisión de Juego del Estado de Washington que se había puesto en contacto con más de cuarenta sitios web. Algunos dominios de juego aparecen en el Steam Filtro de enlaces — una lista que hace que cualquier enlace a ellos publicado dentro de Steam (en el chat, en una página de perfil, en la tienda) muestre una página de advertencia: «¡Enlace bloqueado!» El filtro de enlaces es la única medida de control cuyo efecto puede observarse desde fuera de Valve.\n\nEjemplo: Un enlace a rollbit.com Al pulsar Steam se muestra la página de advertencia de Link Filter (se han marcado 2026-09-19 y 2026-09-21). En teoría, el sitio web de apuestas está bloqueado.\nQué es un dominio proxy\n\nA El servidor de autenticación de dominio independiente es un proxy de autenticación: una segunda dirección web, en un dominio registrable diferente, que el mismo operador interpone entre sus usuarios y Steam con el único fin de llevar a cabo el paso «Iniciar sesión con Steam». Actúa como proxy para el inicio de sesión. El usuario cree que está iniciando sesión en la plataforma; la solicitud que llega a Valve lleva el nombre de host del servidor proxy, no el de la plataforma. Por lo general, no tiene ninguna conexión visible públicamente con el sitio de apuestas, y es la dirección a la que vuelven los usuarios después de que Steam confirme su identidad.\n\nEjemplo: Rollbit opera bajo rollbit.com, que el filtro de enlaces bloquea. En el caso de la autenticación Steam, el flujo observado en 2026-09-20 utilizaba una dirección diferente: rbsnin.com, registrado como 2026-09-18. Esta dirección devolvió No hay ningún bloque de filtro de enlaces en 2026-09-21. La página web de apuestas siguió funcionando, y su proceso de inicio de sesión Steam se realizó a través del servidor desbloqueado.\nEl punto crítico: el servidor de autenticación se envía a Steam en cada solicitud\n\nValve no necesita realizar un escaneo ni un rastreo para saber qué servidores de autenticación están en uso. Steam es el Proveedor de identidad OpenID para estos sitios web, y cada vez que se hace clic en «Iniciar sesión con Steam», se envía una solicitud GET a los propios servidores de Valve que contiene el nombre de host de autenticación en texto sin cifrar. Según el apartado 9.1 de OpenID 2.0, el return_to El campo es técnicamente opcional, pero sin él Steam no puede proporcionar el resultado del inicio de sesión, por lo que, para que el inicio de sesión Steam funcione, es, en la práctica, obligatorio. El propio Steam muestra el nombre de host en la página de inicio de sesión («<host> no está afiliado a Steam ni a Valve\").\n\n— Formato de la solicitud Steam recibida (host tal y como se observa para Rollbit en 2026-09-20): —\nOBTENER steamcommunity.com/openid/login\n&openid.mode=checkid_setup\n&openid.return_to=https://rbsnin.com/… ← se requiere efectivamente; aparece en el registro de Valve\n&openid.realm=https://rbsnin.com ← información facilitada por la propia web; mostrada en la página de inicio de sesión de Steam\nSi el sitio web utiliza la verificación de servidor a servidor (check_authentication), el registro de Valve también recoge la dirección IP del servidor de la plataforma y la red de alojamiento.\n\nExtraer el nombre de host de esta solicitud es una operación habitual. El registro de aplicación —qué servidores se han visto afectados, cuáles no y con qué criterios— solo existe en la infraestructura de Valve y no se ha publicado.\n\nLo que esto demuestra\n\n1. El bloque «Link Filter» actúa sobre los enlaces, no sobre los inicios de sesión. Bloquear el dominio principal (por ejemplo, rollbit.com) muestra un aviso a los usuarios que hacen clic en los enlaces que conducen a ella dentro de Steam. Esto no impide que el sitio web siga funcionando, ni que utilice el propio servicio OpenID de Valve a través de una dirección diferente.\n\n2. Los servidores de autenticación sometidos a prueba no estaban bloqueados. La tabla anterior muestra los hosts de autenticación de dominio independiente registrados entre 2011 y septiembre de 2026, varios de ellos años después de los avisos de julio de 2016. En 26 pares, el dominio principal devolvió un bloqueo de Link Filter y el proxy que gestionaba su inicio de sesión no lo hizo (comprobaciones sin autenticar, 2026-09-21 y 2026-09-22; respuestas sin procesar y SHA-256 guardadas). Ese proxy dejaría de funcionar el día en que Valve lo rechazara, por lo que la medida que se tiene en cuenta aquí es el tiempo que ha estado en funcionamiento, y no si figura en la lista. Valve recibe estos nombres de host en sus propias solicitudes de OpenID. A partir de los datos públicos no se puede determinar si se aplicó alguna medida distinta del filtro de enlaces, ya que Valve no ha publicado ningún registro de aplicación por operador.\n\n3. Los sitios web siguieron realizando el proceso de autenticación a través de la infraestructura de Valve. «Iniciar sesión con Steam» es un servicio de Valve; cada autenticación que se realiza a través de él es una solicitud que Valve recibe y procesa. Valve también obtiene ingresos de las claves de caso, y el Mercado Comunitario Steam cobra una comisión combinada de aproximadamente 15% por las transacciones realizadas dentro del Mercado (no por las operaciones externas). La acción «Filtro de enlaces» creó un registro público; no interrumpió la relación de autenticación.\n\n¿Habría funcionado el bloqueo?\n\nPor analogía: cuando el registrador de dominios gratuito Freenom cerró en 2023, las campañas de phishing que dependían de sus dominios se vieron interrumpidas. La continuidad operativa depende de la estabilidad de la infraestructura.\n\nAquí se aplica la misma lógica. Si se rechazara un servidor de autenticación durante el procesamiento de OpenID de Steam, la función «Iniciar sesión con Steam» de la plataforma dejaría de funcionar hasta que se registrara un nuevo servidor, se emitieran los certificados y se propagara el DNS. Durante ese periodo: tiempo de inactividad.\n\nLa rotación no hace que el bloqueo resulte inútil. Esto convierte el bloqueo en un coste operativo. Dado que los nuevos servidores aparecen en los propios registros de solicitudes de Valve la primera vez que se utilizan, una respuesta podría tardar lo mismo que ese primer uso.\n\nEl registro por lotes es, en sí mismo, una señal: Las consultas «login1» a «login10» de CSGOEmpire se registraron el 2020-07-20, nueve de ellas en un plazo de 22 segundos (Verisign RDAP). No es necesario que una respuesta se refiera a cada dominio por separado; una serie secuencial procedente de una misma sesión del registrador puede identificarse como una serie.\n\nLos registros públicos no indican que se haya producido ningún intento de bloquear hosts de autenticación que haya sido frustrado por la rotación.\nMuestra los dominios principales bloqueados mientras el proxy que gestionaba cada inicio de sesión seguía en funcionamiento —26 pares a fecha de 2026-09-22, siendo el servidor de autenticación más antiguo el que llevaba registrado 12 años y 6 meses— y no hay ningún registro publicado de medidas coercitivas por parte de ningún operador.\nPor lo tanto, la pregunta que se plantea el regulador es: ¿qué medidas coercitivas, si las hay, ha aplicado Valve a los servidores de autenticación que recibe en sus propias solicitudes de OpenID?\n¿Qué hizo Valve y por qué no interrumpió la ruta de autenticación?\n\nLa tabla siguiente relaciona cada acción Valve documentada públicamente con el hecho de si afectó o no al punto de entrada de autenticación de OpenID. La conclusión no es que «Valve no hiciera nada», sino que ninguna de las acciones documentadas públicamente afectó al punto por el que pasan los inicios de sesión en las plataformas de juego a través de los servidores de Valve.\n\nFecha\tValve Acción\tAfectados openid.return_to ¿ruta?\nJulio de 2016\tDeclaración pública del 13 de julio de 2016; notificaciones de los abogados a unas 23 entidades concretas (prensa, 21 de julio de 2016); se contactó con más de 40 entidades según la carta de Valve de octubre de 2016 dirigida a WSGC\tNo. Las notificaciones y el filtro de enlaces actúan sobre los operadores y los enlaces; la ruta de solicitud de OpenID no se ha modificado.\n2017\tCierre de IEconItems_730/GetPlayerItems (según la cuenta de ingeniería de CSFloat; no se ha encontrado ningún registro de cambios Valve)\tNo. Se ha visto afectada la visibilidad del historial de los elementos públicos. La autenticación OpenID no se ha modificado.\n2018-03-29\tSe anuncia un bloqueo de intercambios de 7 días en CS:GO (blog.counter-strike.net)\tNo. Se ha ralentizado el movimiento de elementos; la ruta de solicitud de OpenID no se ha modificado.\n2022-05-10\tSe han eliminado los puntos finales de cancelación de intercambios de la API web pública (detectado por un usuario; sin registro de cambios Valve — node-steam-tradeoffer-manager #325)\tNo. Se ha desactivado la herramienta de intercambio de ofertas; la autenticación OpenID no se ha modificado.\n2023-12-04\tLa creación de claves API ahora requiere una confirmación a través del móvil (steamcommunity.com/dev/apikey; sin registro de cambios)\tNo. Se protegió el punto final clave; los servidores de autenticación que se mencionan aquí no se vieron afectados.\n2026-09-19 / 21-09\tSteam Estado del filtro de enlaces según la observación de los autores\tLos 14 dominios principales devolvieron un bloqueo en la nueva comprobación guardada 2026-09-21 —26 pares divididos en el registro por 2026-09-22—, mientras que el proxy que gestionaba cada inicio de sesión siguió funcionando.\nFuentes: Valve comunicado del 13 de julio de 2016 (store.steampowered.com/oldnews/22883, archivado 2026-09-21) · Informe técnico de CSFloat sobre el cierre de 2017 (blog.csfloat.com, archivado 2026-09-21) · Estado del filtro de enlaces: linkfilter-recheck-2026-09-21.json.\nEsta conclusión puede refutarse con un solo caso publicado en el que Valve haya rechazado una solicitud de OpenID porque openid.return_to apuntaba a un servidor de autorización de juegos de azar. No se ha encontrado ninguna instancia de este tipo en los registros públicos.\nLos dos registros de «auth-host» más recientes\nhowl.unoSe registró 2026-08-11 (RDAP), 41 días antes de 2026-09-21; howl.gg devolvió un bloqueo del filtro de enlaces en 2026-09-18, 2026-09-19 y 2026-09-21. No se ha determinado si el bloqueo fue anterior al registro.\nrbsnin.comse registró como 2026-09-18T09:34:52Z (Verisign RDAP) y se observó en el flujo de inicio de sesión de Rollbit Steam en 2026-09-20 a través del aviso de la propia página de inicio de sesión de Steam; rollbit.com devolvió un bloqueo del filtro de enlaces en 2026-09-19 y 2026-09-21, mientras que rbsnin.com no lo hizo.\nCada host de la tabla anterior se envía a los servidores de autenticación de Valve como openid.realm en cada intento de inicio de sesión.\nDatos completos por ruta y resultados del filtro de enlaces: la tabla de la sección 3 anterior; resultados sin procesar en linkfilter-recheck-2026-09-21.json y linkfilter-all-results.json.\nMetodología: cómo se establecieron los recuentos de rutas y filtros de enlace\n1. Resolución de dominios\nLa auditoría 2026-09-21 resolvió 78 de las 189 plataformas solicitadas: 33 se autentican con su propio nombre de host y 20 con su propio subdominio —autenticación directa—, y ninguna de ellas se contabiliza como ruta de dominio independiente. El resto 25. Autenticarse a través de un dominio independiente que se pueda registrar, repartidos entre 24 nombres de host distintos (dota2.net es compartido por market.csgo.com y rust.tm): 10 identificados mediante captura en tiempo real del navegador, 3 a través del aviso de la propia página de inicio de sesión de Steam y 12 mediante una URL de OpenID facilitada. El registro en tiempo real (master_registry.json, 2026-09-22) amplía eso a 44 rutas de dominios independientes: 26 pares con división de filtro (dominio principal BLOQUEADO, host de autenticación LIMPIO), más otras 18 rutas sin división del dominio principal. De las 44, 27. Llevar un expediente de pruebas por cada ruta; los otros 17 se recogieron a mano y están marcados realm_src: user en el registro. Cinco de esos diecisiete —csgogem.com, gamdom.com, 12cs.fail, csgolounge.com y dota2lounge.com— se añadieron el 2026-09-22 con una captura de Link Filter de ambos hosts (HTML sin procesar + SHA-256 en linkfilter-2026-09-22.json), por lo que la división en sí misma queda constatada aunque el dominio se haya recopilado manualmente; aparecen en la tabla anterior junto a las rutas del archivo de pruebas. tfauth.com (tf2easy.com) fue eliminado del registro a las 2026-09-22: al igual que arena.fragnet.net, no hay ningún enlace verificable que lo relacione con su sitio de origen. El recuento se puede volver a calcular a partir de los datos publicados auth-route-audit.json (serie de 2026-09-21) según una única regla: una plataforma solo cuenta cuando su host OpenID Steam observado se encuentra en un dominio registrable distinto al de la propia plataforma.\n2. Steam Estado del filtro de enlaces\nProbado mediante steamcommunity.com/linkfilter/?url=https://[domain], sin autenticar, en 2026-09-19 y 2026-09-21; HTML sin procesar guardado con SHA-256. El estado se registra por separado para el dominio principal y el host de autenticación. Un clasificador distingue el aviso genérico «Estás saliendo de Steam» (CLEAN) de la página «¡Enlace bloqueado! ... marcado como potencialmente malicioso» (BLOCKED); un control de google.com confirma que ambos no se confunden. Se descartó una variante anterior autenticada de esta prueba después de que devolviera «bloqueado» para todos los dominios, incluido ese control; se determinó que se debía a una cookie de sesión no válida en el script de prueba, y no a un resultado real.\n3. Observación del host de autenticación\nCaptura en directo: un navegador Playwright accedió al proceso de inicio de sesión de cada plataforma y el openid.return_to El nombre de host se ha obtenido de la solicitud interceptada. Aviso de la página de inicio de sesión: el nombre de host se ha obtenido de la propia «» de Steam'<host> no está vinculado a Steam ni a Valve\" texto, que Steam se representa a partir de openid.realm (rbsnin.com, sc-auth.net, auth.dota.trade). URL facilitada: una URL de inicio de sesión «a Steam» facilitada a los autores; esta establece los parámetros de la solicitud, no un inicio de sesión completado. No se completó ningún inicio de sesión en ninguna plataforma.\n4. Cobertura: lo que no se ha resuelto y por qué es importante\nDe las 189 plataformas, El 110 no estableció ninguna ruta y uno no era aplicable (189 − 78 − 1). Este expediente no tiene en cuenta ninguno de ellos. El desglose de los 110, según el archivo de auditoría: 22 retos de bot, 14 tiempos de espera agotados, 12 errores HTTP y 10 errores de navegación —el observador no pudo acceder al flujo de inicio de sesión, aunque la mayoría de estos sitios se abren con normalidad en un navegador habitual—; 20 no mostraban ningún control de inicio de sesión Steam en la página de destino; 16 llegaban a un flujo de inicio de sesión que no se podía resolver en un servidor; 11 dominios no se resolvían en el DNS; 5 se detenían en una pantalla de consentimiento. El registro que figura a continuación desglosa esos mismos 110 de forma diferente: los 11 que no se resolvieron en el DNS se enumeran por separado como Eliminado · NXDOMAIN, y la única entrada no aplicable se suma al resto. Se han auditado 189 plataformas y se han eliminado 11 tras recibir un NXDOMAIN definitivo de ambos resolutores, 178 conservados (platform-audit.json, platforms-removed.json). Se eliminaron de los datos de 2026-09-19 137 dominios de autenticación que el libro mayor había adivinado a partir del patrón de nomenclatura —nunca se observaron, por lo que nunca constituyeron una prueba—. Tres de las suposiciones se contradecían con las URL de OpenID facilitadas: buff.163.com, gamerpay.gg y csgoluck.com realizan la autenticación directamente, frente a las suposiciones de buffauthproxy.163.com, gamerpayredirect.io y lucklogin.app. Las eliminaciones figuran en el archivo de auditoría publicado.\nEl 25 es un mínimo, no un máximo. De las 78 plataformas que se resolvieron, 25 utilizaban un dominio independiente y 53 no. De esa proporción no se deduce nada sobre las 110 no resueltas, y en ningún lugar de este informe aparece ninguna proyección basada en ella. Cada una de ellas puede resolverse si una persona abre la página y pulsa «Iniciar sesión con Steam»: el nombre de host de autenticación aparece en la URL de la página Steam que se carga.\nEl objetivo de esta sección: Un observador independiente necesita un navegador y mucha paciencia para identificar 189 plataformas, y ha conseguido identificar 78. Valve requiere una consulta a la base de datos. Todas las plataformas que utilizan «Iniciar sesión con Steam» —tanto las identificadas como las no identificadas— envían openid.realm al punto final de autenticación de Valve en cada inicio de sesión. La laguna que aparece en esta tabla se debe a que los autores se encuentran fuera del sistema. No existe en el caso de Valve.\nLos nombres de host proxy observados se encuentran en auth-route-audit.json. Fechas de registro del dominio según RDAP (Verisign) / IP2WHOIS. Resultados del filtro de enlaces en linkfilter-all-results.json.\nUna analogía para que quede más claro\n\nImagina que las autoridades reguladoras comunican a una empresa de taxis con licencia que ya no puede operar desde su dirección registrada en Main Street. La empresa retira el letrero de Main Street. Se documenta la retirada de dicho letrero. Sin embargo, la misma empresa abre una sede en Side Street —registrada bajo un nombre diferente— y continúa operando desde allí. Las autoridades reguladoras gestionan el sistema central de despacho que utilizan todos los taxis de ambas direcciones. Cada solicitud de viaje indica «recogida en Side Street». Las autoridades reguladoras nunca revocan la licencia de Side Street. La retirada del letrero de «Main Street» fue la única medida coercitiva que se llevó a cabo. La empresa de taxis nunca dejó de prestar servicio.\n\nParte A — Ficha técnica · Apartado 3.1\nDentro de Steam, la lista de Valve es la única lista.\n\nSi se hace clic en un enlace en el cliente Steam, la superposición del juego o el modo Big Picture no se abren en el navegador del usuario. Se muestran en el propio navegador integrado de Steam, donde no están presentes las capas de advertencia que aplicaría un navegador. El filtro de enlaces no es una medida de seguridad más entre otras muchas. Es la única medida de seguridad.\n\nEn un navegador normalTres capas independientes\nNavegación segura de GoogleUn intersticial a página completa para los servidores incluidos en las listas de phishing y malware de Google, que se actualiza continuamente y es independiente del sitio web que se esté visitando.\nLa extensión antivirus para el navegadorLa mayoría de los productos para dispositivos finales de consumo incluyen un complemento para el navegador que comprueba si el destino figura en la lista de reputación del propio proveedor.\nInspección HTTPS en los terminalesCuando el producto realiza una inspección TLS, el contenido de la página se analiza antes de que llegue al usuario.\nEn el cliente Steam, superposición y «Big Picture»Una capa\nNavegación segura de GoogleNo está presente. La comprobación requiere claves API de Google que no se proporcionan en las compilaciones de Chromium integradas; cuando no están presentes, la propia documentación de diseño de Chromium indica que el controlador de Navegación segura simplemente nunca se añade a la cadena de solicitudes.\nLa extensión antivirus para el navegadorNo está presente. El motor de renderizado de Steam no es el navegador del usuario y no carga ninguna extensión del perfil del navegador del usuario, por lo que no se ejecuta ningún complemento en la página.\nInspección HTTPS en los terminalesDepende del producto. El tráfico termina dentro de un proceso Valve firmado con código, en lugar de en un navegador reconocido, y varios productos de punto final excluyen las aplicaciones firmadas de la inspección TLS.\nEl filtro de enlaces SteamLa lista de bloqueados propia de Valve, a la que se recurre cuando un enlace sale del ecosistema Steam. Esta es la única comprobación que se lleva a cabo, y la tabla anterior recoge los resultados que devuelve para los hosts de autenticación descritos en esta sección.\nUna prueba que cualquier lector puede realizar, y si falla, la conclusión deja de ser válida.\n\nAbre una de las URL de prueba de «Navegación segura» publicadas por Google (testsafebrowsing.appspot.com) en Chrome: aparece una página intersticial roja a pantalla completa. Abre la misma URL desde un mensaje de chat Steam, de modo que se muestre en el cliente Steam o en la superposición: no aparece ninguna página intersticial. La única advertencia que Steam puede generar es su propia página de filtro de enlaces, y solo para los hosts que figuran en la lista de Valve.\n\nEl historial de recompensas por errores de ValveEsa sola capa ya se había utilizado antes, en el propio disco de Valve\n\nSi el filtro de enlaces es la única comprobación que se ejecuta en el cliente, sus propios modos de fallo no son una cuestión secundaria. Dos informes en el programa HackerOne de Valve, ambos aceptados, ambos resueltos y ambos divulgados íntegramente desde entonces:\n\n#291750archivado 2025-11-16 ↗Open Redirect · Medium\nDesactivación de la protección del filtro de enlaces\n\nNotificado el 19 de noviembre de 2017, resuelto y divulgado el 9 de mayo de 2018. Prueba de concepto del propio informe: sustitución del punto ideográfico 。 (%E3%80%82) para el punto en un nombre de host — Es posible eludir el bloqueo. El contenido intersticial al que se refiere esta sección no ha aparecido.\n\n#1079561archivado 2026-09-24 ↗Divulgación de información · alta\nEl navegador web Big Picture filtra cookies de inicio de sesión y revela información confidencial (lo que podría dar lugar a la apropiación de cuentas)\n\nNotificada el 15 de enero de 2021, resuelta y divulgada el 21 de septiembre de 2021. La propia clasificación de gravedad de Valve es alta, y el título indica la consecuencia. El registro publicado incluye el título, la clasificación y las fechas; la descripción técnica no figura en el contenido publicado, por lo que no se cita nada más de ella aquí.\n\nEs una interpretación de los autores, no una conclusión de ninguno de los dos informes: Ambos se sitúan a ambos lados de la misma puerta. Uno es la advertencia que no aparece antes de que se abra el destino; el otro es la sesión que abandona el cliente una vez que se abre una página en su interior. La secuencia que sigue a una sesión robada —clave registrada sin solicitud previa, operación real cancelada, duplicado enviado a un clon— es el patrón establecido en Sección 5 a Sección 8. Ambos informes están cerrados; ninguno de ellos se presenta como una vulnerabilidad activa. Lo que demuestran es más limitado, pero suficiente: la única capa que queda tiene un historial documentado de haber sido eludida, según los propios registros de Valve.\n\nFuente: el registro de divulgación de HackerOne correspondiente a cada informe, consultado el 2026-09-22 — número, título, equipo, vulnerabilidad, gravedad, fechas de informe y divulgación, y estado tal y como lo publica HackerOne. Registro de consulta: hackerone-reports.json. Aquí no se indica ninguna cuantía de la recompensa; tampoco aparece ninguna en el expediente consultado.\n\nObservación de campo · PhishDestroyLas detecciones que normalmente ponen fin a una campaña no lograron detener estas\n\nObservamos cómo los servidores de phishing seguían captando tráfico mientras transportaban 20 o más detecciones de proveedores. Si se envía a través de la web o por correo electrónico, una campaña en ese estado se frustra en cuestión de días: tanto el navegador como el antivirus actúan en función de esos veredictos. En Steam, sin embargo, no ocurre así. Los veredictos existían desde el principio. El cliente nunca solicitó nada.\n\nQué significa esto para un menor que tiene instalado un antivirus\n\nNo ignora ninguna advertencia ni desactiva nada. Llega un mensaje en Steam —un cuchillo gratis, un voto para el equipo de un amigo— y la página se abre en Steam. Nunca abre un navegador, por lo que el navegador nunca le protege. Su antivirus está en funcionamiento y puede que ya haya clasificado ese dominio como malicioso; pero nunca se le consulta. Ya existen todas las advertencias que podrían haberlo detenido. Ninguna de ellas le llega. Él cree que nunca se marchó de Steam, y así fue.\n\nLa oferta gratuita no es una invención del estafador: los artículos «gratis Valve» son la forma en que se anuncian las páginas web de skins y de apuestas, y precisamente por eso el mensaje parece tan normal. Quejas: el archivo de ejecución. Datos sobre la edad y los hijos: Artículo 17.\n\nFuentes: Steam muestra el contenido web a través del Chromium Embedded Framework en el steamwebhelper proceso — véase Análisis técnico de DARKNAVY del 27 de junio de 2024 ↗ y el propio de Valve Steam Foro de la versión beta para clientes ↗ archivado 2025-08-04 ↗. No se utiliza ninguna versión de CEF: el Chromium integrado no es Chrome y no incluye ninguno de los servicios de Google de Chrome. Navegación segura sin claves API: Documento de diseño de Chromium ↗ archivado 2026-08-21 ↗, Claves de la API de Chromium ↗ archivado 2026-08-30 ↗ («Muchas de las API de Google que utiliza Chrome son específicas de Google y no están pensadas para su uso en productos derivados»), y el mismo efecto en otras versiones sin clave — Barril de cerveza artesanal n.º 193814 ↗. URL de prueba: testsafebrowsing.appspot.com ↗.\n\nDos relojes distintos\nLa antigüedad del dominio.Fecha de la observación.\n\nLa fecha de creación del registro indica cuándo se registró un dominio. Un registro OpenID con fecha establece el servidor de origen de dicho registro. La primera no puede cubrir los años anteriores a la segunda.\n\nEl registro completo distingue entre un dominio registrable independiente, el subdominio propio de un sitio web y una ruta directa. Cada fila incluye un enlace a su origen y al resultado de DNS.\n\nConsultar el registro de dominios →· Descargar fechas de inscripción ↗· Repetir la observación ↗\n\nParte A — Ficha técnica · Sección 4\nSe ha cerrado un punto final. El seguimiento público ha perdido una clave.\nContexto y límites de la fuente\n\nSteam introdujo cambios que eliminaron la visibilidad pública de los ID de activos de los artículos y restringieron el acceso al inventario a través de la API. El resultado: se hizo imposible rastrear un artículo concreto mediante su ID de activo original a partir de datos públicos. A continuación se detalla lo que era posible antes, lo que dejó de serlo después y lo que eso supone para una víctima que intenta demostrar adónde ha ido a parar su propiedad. La fecha es 2017, según la cuenta de ingeniería de CSFloat; no se ha localizado ningún registro de cambios de Valve. La secuencia —aproximadamente un año después de la declaración sobre el juego de julio de 2016— es la pregunta de la investigación, no una conclusión. Los registros de los artículos en sí permanecen dentro de los sistemas de Valve; los investigadores externos perdieron el acceso a la cadena de identificadores originales, mientras que los identificadores «float», «seed» y «paint» solo permiten una coincidencia parcial.\n\nSe aplica la regla Valve: Steam El servicio de atención al cliente no recupera los artículos que hayan salido de tu cuenta, y la responsabilidad de demostrar lo que ha ocurrido recae en ti. El historial: En 2017, Valve cerró el punto final que contenía los ID originales de los artículos. Antes de eso, cualquiera podía rastrear un skin robado desde la cuenta de la víctima hasta un bot de un mercado. Desde entonces, nadie ajeno a Valve puede hacerlo. El documento de identidad que se le pide a la víctima es el que fue sustraído. — y sigue existiendo, dentro de Valve.\n\nLa era anterior al apagón\n\nHistóricamente, cada objeto virtual generado en Steam poseía un identificador único a nivel global e inmutable ID del activo. Las bases de datos OSINT de terceros podrían indexar estos identificadores. Si a un usuario le robaran un artículo, los investigadores podrían rastrear el recorrido de ese activo concreto a medida que pasara de la cuenta intermedia del ladrón a las cuentas de almacenamiento de un mercado o un sitio web de apuestas.\n\nANTES: cualquiera podía rastrear un artículo desde la cuenta de la víctima, pasando por cuentas intermedias, hasta llegar a un bot de almacenamiento de un mercado o un casino, utilizando datos públicos.\nTras el cambio\n\nSegún la cuenta de ingeniería de CSFloat, Valve cerró el punto final en 2017 y los ID originales de los artículos dejaron de estar disponibles para terceros. No se ha encontrado ninguna declaración Valve que explique el motivo del cambio. Tampoco se ha encontrado, en ese mismo periodo, ninguna medida publicada contra las cuentas de bots comerciales que movían artículos a gran escala.\n\nSea cual sea el motivo, el cambio rompió la cadena de custodia pública. Una víctima ya no puede reconstruir la cadena de identificación original a partir de datos públicos para demostrar que un artículo robado concreto se vendió a través de un mercado o casino específico. Los registros de los artículos siguen existiendo en los sistemas de Valve; el público, los investigadores y las fuerzas del orden que trabajan con datos públicos no pueden acceder a ellos.\n\nA PARTIR DE AHORA: ya no es posible rastrear un artículo concreto mediante su ID de activo original a partir de datos públicos. La cadena de custodia del ID original de un artículo trasladado después de 2017 solo existe dentro de la infraestructura de Valve; no se ha hecho público ningún registro de este tipo. Los identificadores «float», «seed» y «paint» solo permiten una correspondencia parcial y probabilística.\nIEconItems_730\nOBTENER/IEconItems_730/GetPlayerItems/v1/\nCarga útil rastreable (antes del parche)\n\"id\": \"14892281934\",\n\"original_id\": \"11829910211\",\nEstado: La víctima puede rastrear el historial del objeto a través de las cuentas de los bots.\nCarga útil ofuscada (tras la aplicación del parche)\nActual\n\"id\": \"HIDDEN_BY_PRIVACY_SETTINGS\",\n\"original_id\": \"NULL\",\nEstado: las partes externas ya no pueden rastrear el historial de un artículo a partir de su ID de activo original utilizando datos públicos.\nRepercusión en las pruebas: Tras el cambio, ya no se disponía de los datos públicos necesarios para rastrear un artículo concreto mediante su ID de activo original desde la cuenta de una víctima hasta un bot de un mercado o un casino. Los registros internos siguen existiendo en Valve; una víctima, un investigador o un analista que trabaje a partir de datos públicos no puede reproducir la cadena del ID original (los identificadores «float», «seed» y «paint» solo permiten una coincidencia parcial).\n\nFuente: Informe técnico de CSFloat sobre el cierre en 2017 de IEconItems_730/GetPlayerItems — blog.csfloat.com/how-floatdb-tracks-items (archivado 2026-09-21) · Las cargas útiles que se muestran son una ilustración de la forma del campo, no respuestas capturadas · No se ha encontrado ningún registro de cambios Valve para el cierre.\n\nParte A — Ficha técnica · Sección 5\nUna sesión. Más acceso del que el usuario percibe.\nLímites del contexto y de la fuente\n\nLa arquitectura de claves API de Valve, tal y como era antes de los cambios de 2023, se apartaba de los estándares básicos del sector (OWASP ASVS, NIST SP 800-63B) y es el mecanismo descrito en las denuncias automatizadas por robo de inventario conservadas en el archivo de pruebas (secciones 6-8).\n\nSe aplicó la regla Valve: El titular de la cuenta creó la clave, aceptó las condiciones y asume la pérdida: esa es la respuesta que figura en los rechazos archivados. El historial: Hasta diciembre de 2023, bastaba con una cookie de sesión robada para registrar esa clave. Sin contraseña. Sin Steam Guard. Sin notificación alguna a la persona a la que pertenecía la cuenta. El usuario no creó la clave, no podía verla y, sin embargo, le dijeron que sí lo había hecho. La confirmación móvil se añadió el 2023-12-04, unos siete años después de la declaración de 2016 y aproximadamente seis años después de los paneles sobre estafas que conserva el archivo. Esos años no los pagó Valve. Los pagaron las cuentas que se habían vaciado entretanto, algunas de ellas de menores.\n\nOWASP ASVS 2.8 / NIST SP 800-63BGRAVEDAD: CRÍTICA\n1. Autenticación de nivel superior insuficiente\n\nSteam permitía la generación de claves API con privilegios elevados y de larga duración utilizando únicamente una cookie de sesión. No se exigía la autenticación de dos factores (Steam Guard) ni ningún desafío de autenticación reforzada al configurar o modificar una clave API de desarrollador, por lo que la confirmación móvil Steam Guard —el único segundo factor que ofrece Steam— no protegía este paso. (En 2016 se solicitó un segundo factor de hardware en el propio sistema de seguimiento de 2 y el problema sigue abierto: Apéndice D, GH-01.)\n\nEstado: sin parchear antes de 2023. Permitía que un script que contuviera una cookie robada registrara una clave sin ninguna interacción por parte del usuario.\nOWASP A01:2021 / Principio del privilegio mínimoGRAVEDAD: CRÍTICA\n2. Ausencia del principio del mínimo privilegio\n\nLa API web Steam carecía de ámbitos de autorización basados en roles. Una clave de API para desarrolladores emitida para consultar el estado del inventario en «solo lectura» poseía permisos completos de «escritura», incluida la capacidad de modificar operaciones existentes, iniciar otras nuevas, registrar webhooks y rechazar intercambios pendientes válidos.\n\nEstado: defecto de diseño sistémico. Una clave = control total de lectura y escritura sobre el inventario y las operaciones de la cuenta.\nOWASP A07:2021 / SesionesGRAVEDAD: ALTA\n3. Fallos en la gestión de sesiones\n\nLos usuarios han informado de que las sesiones web secuestradas procedentes de rangos de direcciones IP de servidores de alojamiento siguen activas. La práctica habitual consiste en cerrar las sesiones ante anomalías geográficas y tras un cambio de contraseña; los informes de los usuarios recopilados en el archivo describen sesiones que permanecieron activas tras un cambio de contraseña.\n\nEstado: comportamiento notificado (quejas de usuarios en el archivo). Las sesiones podían generar claves API sin necesidad de volver a autenticarse.\nEl bloqueo a nivel de dominio era técnicamente viableVIABILIDAD DE LA APLICACIÓN\n4. El bloqueo a nivel de dominio de los servidores de autenticación era técnicamente viable\n\nValve ya gestiona una lista de dominios (el «Link Filter») y ya recibe todos los nombres de host de autenticación en sus propias solicitudes de OpenID. Ambos mecanismos no están conectados de ninguna forma visible desde el exterior: a fecha de 2026-09-22, en 26 pares el dominio principal figuraba en el filtro, mientras que el proxy que gestionaba su inicio de sesión no lo hacía.\n\nConectarlas es una tarea de ingeniería sencilla: lee el openid.realm el nombre de host de cada solicitud entrante, compararlo con una lista y rechazar o marcar la solicitud. La ilustración de la derecha muestra el esquema de dicha rutina. Rechazar el host de autenticación —en lugar de limitarse a la página de inicio pública— interrumpiría el paso «Iniciar sesión con Steam», del que dependen estas plataformas.\n\nNo hay pruebas públicas que demuestren que Valve realice dicha comprobación. La comisión combinada del Steam Community Market, de aproximadamente 15%, se aplica a las ventas realizadas dentro del mercado; no se cobra en las transacciones externas de estas plataformas.\n\nblock_auth_hosts.pyILUSTRACIÓN\n// Leer el host Steam que ya se ha recibido — no realizar escaneo\ndef on_openid_request(solicitud):\nhost = parse_openid_realm(request)\nsi anfitrión en dominios_bloqueados:\nrechazar (una solicitud)\nNota: Pseudocódigo a título meramente ilustrativo. Ambas partes ya existen en Valve: el nombre de host del autor se incluye en la solicitud y la lista de dominios es el filtro de enlaces. No hay ningún registro público que explique por qué no están conectadas.\nApartado 5.1 — Las normas no se retiraron de la publicación\nValve se compila siguiendo estas reglas todos los días. En este caso, no se ha compilado según ellas.\n\nSteam está disponible en la App Store y en Google Play, realiza ventas a través de los principales procesadores de tarjetas y utiliza API de terceros como cualquier otra gran plataforma. Cada una de esas relaciones conlleva un requisito de seguridad publicado y con fecha concreta que Valve debe cumplir para seguir operando. Compara las fechas de dichos requisitos con las fechas en las que la propia API web de Steam incorporó las mismas medidas de protección. Nada de lo que figura a continuación es una norma privada, un memorándum interno ni un secreto comercial: cada fila es un documento público con una fecha de publicación.\n\nRequisitos de seguridad externos publicados, con sus fechas, comparados con la fecha en la que la API web Steam incorporó el control equivalente\nLa norma publicada y la fecha en que entró en vigor\tLa API web Steam sobre la misma pregunta\nAutorización limitadaOAuth 2.0 — RFC 6749, Octubre de 2012. En el apartado 3.3 se define scope De este modo, un cliente solo recibe el acceso que solicita. Desde entonces, ha sido la configuración por defecto de todas las API de las principales plataformas.\tLos ámbitos granulares llegaron el 16 de enero de 2026.Antes de eso, una sola clave de la API web Steam permitía acceso completo de lectura y escritura sobre las operaciones de la cuenta, independientemente del motivo por el que se hubiera emitido. Trece años y tres meses tras la especificación que define el control.\nUna clave no es una autorizaciónLa propia documentación de Google Cloud: Una clave API estándar no autentica a un sujeto, y en el caso de las API que crean o gestionan recursos, No utilices claves de autorización en el entorno de producción.\tLa clave de la API web Steam era exactamente eso.Una cadena de portador, emitida para una cuenta, que por sí sola basta para consultar el inventario, cancelar una operación pendiente y enviar una nueva. No se autenticó a ningún ordenante en el momento de su uso.\nAutenticación multifactorial para el acceso privilegiadoPCI DSS 3.2, requisito 8.3 — obligatorio a partir del 1 de febrero de 2018 para todos los accesos administrativos que no se realicen a través de la consola y para todos los accesos remotos al entorno de datos de los titulares de tarjetas. Posteriormente, Apple exigió la autenticación de dos factores a todos los titulares de cuentas del Programa para Desarrolladores a partir de 27 de febrero de 2019: Los desarrolladores que tengan el rol de «Titular de la cuenta» en un programa para desarrolladores deberán activar la autenticación de dos factores para iniciar sesión.\tSe necesitaba un segundo factor para crear una clave API a partir de 4 de diciembre de 2023.Hasta entonces, bastaba con una cookie de sesión robada, sin que apareciera ningún aviso en el teléfono del titular de la cuenta ni se enviara ninguna notificación posterior. Cuatro años y nueve meses después de que Apple obligara a Valve a utilizar un segundo factor de autenticación simplemente para iniciar sesión en un portal para desarrolladores.\nCiclo de vida y revocación de las credencialesTwitch exige a todas las aplicaciones de terceros: Tu aplicación debe validar el token de OAuth al iniciarse y, a partir de entonces, cada hora., y afirma que realiza auditorías para detectar aquellas aplicaciones que no lo hacen. Su API heredada v5 se retiró definitivamente el 28 de febrero de 2022 según un horario publicado.\tNo hay ningún registro publicado sobre el ciclo de vida de la clave.El cambio de 2023 protegió el punto final de creación. No se ha encontrado ninguna declaración Valve relacionada con este cambio que haga referencia a las claves ya registradas, y el cambio no vino acompañado de ningún registro de cambios. A partir de los datos públicos no se puede determinar si las claves creadas antes de dicho cambio quedaron invalidadas, y esa es precisamente la pregunta que un interesado necesitaría que se le respondiera para saber si una clave creada en su cuenta años atrás sigue activa.\nReferencia arquitectónica // Token Architecture\nÁmbitos detallados de GitHub frente a Valve Steam API web\n\nValve desarrolladores gestionan a diario software de código abierto en GitHub utilizando tokens granulares con el mínimo privilegio. Compárese esto con la clave monolítica emitida a 130 millones de Steam jugadores.\n\nToken de GitHub de alto nivel de detalle\nUtilizado por Valve en GitHub\n\nToken de alto nivel de detalle con aislamiento por ámbito y aplicación obligatoria del ciclo de vida.\n\nAcceso al repositorio:Solo repositorios seleccionados (1 repositorio)\nConceder permisos:Solo lectura [✓]\nCódigo y secretos:Sin acceso [✕]\nFecha de caducidad:30 días (TTL obligatorio)\nRegistro de auditoría:Dirección IP, agente de usuario y marca de tiempo\nSituación de seguridad: El token de privilegios mínimos limita los daños a un único recurso de solo lectura.\n!Valve Steam Clave de la API web\nDistribuido a 130 millones de usuarios\n\nUna única cadena maestra de 32 caracteres que otorga una autorización de «todo o nada» en materia de operaciones e inventario.\n\nAcceso a la cuenta:CUENTA COMPLETA (monolítica)\nGestión de operaciones:Leer, Cancelar, Rechazar [!]\nÁmbitos granulares:NINGUNO (Llegó en 2026, con 13 años de retraso)\nFecha de caducidad:NUNCA (Válido indefinidamente)\nRegistro de auditoría:NINGUNA (El usuario no tiene historial de direcciones IP)\nVulnerabilidad: Una clave robada permite interceptar de forma silenciosa todas las ofertas comerciales salientes.\nLa norma se aplica en una sola dirección\n\nSupongamos que un proveedor Valve —ya sea un proveedor de servicios en la nube, un procesador de pagos o una red de distribución de contenidos (CDN)— dejó un punto final de credenciales sin un segundo factor de autenticación y, meses más tarde, los propios datos corporativos de Valve se filtraron a través de una clave generada en ese punto final. ¿Aceptaría Valve que la culpa recayera en quienquiera que hiciera clic en el enlace? Las denegaciones archivadas que se conservan en este expediente responden a la pregunta inversa para el usuario: la postura adoptada es que el titular de la cuenta creó la clave y debe asumir la pérdida. Esta misma arquitectura se describe como un fallo del proveedor por un lado y una responsabilidad del usuario por el otro. Que sea así no es una cuestión técnica, y tampoco es algo que esta investigación pueda zanjar: es algo que debe decidir un tribunal o una autoridad supervisora.\n\nUna ilustración, no una prueba: la norma interpretada al revés\nUn procesador de pagos que permitía que un script de terceros generara una credencial de transacción con privilegios totales a partir únicamente de una cookie del navegador, sin que se le pidiera confirmación al titular de la cuenta.\nUn proveedor de identidad que cerró la brecha a través de la cual se acuñaron sus tokens y no publicó nada sobre los tokens ya acuñados.\nUn banco que respondió a una transferencia impugnada señalando que la credencial utilizada estaba registrada en la propia cuenta del cliente y cerró el expediente.\n\nNinguna de estas observaciones pretende constituir una conclusión sobre ninguna empresa concreta. Se trata de las mismas decisiones de diseño, trasladadas a un contexto en el que la respuesta de las autoridades de supervisión está bien documentada; y esa es precisamente la comparación que se pide al regulador que realice.\n\nLo que se desprende del expediente: Los controles que no figuraban en la API web Steam eran públicos, obsoletos y, en varios casos, condiciones Valve que la empresa tenía que cumplir para poder seguir distribuyendo sus propios productos. El intervalo entre cada norma y el cambio equivalente Steam es cuantificable y se detalla más arriba. Lo que no aclara es el motivo. No se ha encontrado ninguna Valve explicación sobre los motivos de ninguno de estos intervalos, y aquí no se da ninguna por sentada; dicho registro se encuentra en Valve y no se ha publicado.\n\nFuentes, todas ellas documentos públicos: OAuth 2.0 — RFC 6749, octubre de 2012 ↗ · Google Cloud — Documentación sobre claves API ↗ · Requisito 8.3 de la norma PCI DSS 3.2 — Guía de recursos del PCI SSC ↗ · Apple — Próximo requisito de autenticación de dos factores para los titulares de cuentas, 20 de febrero de 2019 ↗ archivado 2025-05-06 ↗ · Twitch — Requisito de validación de el token ↗ y el Aviso de cierre de la versión 5 ↗ archivado 2025-01-27 ↗. Las fechas de Steam son las que figuran en el registro de actualizaciones de esta sección; las entradas de 2023 y 2026 corresponden a las versiones que Valve lanzó sin un registro de cambios. Consultado el 2026-09-22.\n\nRegistro de actualizaciones de Valve — con fecha, procedente de fuentes públicas\nFecha\tValve cambio\t¿Se ha anunciado?\tLo que cerró\tRetraso: mecanismo público → solucionado\tFuente\n2026-09-01\tDetección automática de chats sospechosos\tSí\tEnlaces o patrones peligrosos en los chats de grupo\t—\tnoticias ↗\n2026-01-16\tÁmbitos granulares de la API web de Steamworks\tSí\tÁmbitos de privilegios mínimos para las claves de desarrollador\t—\tanuncio ↗\n2025-07-15\tProtección comercial y ventana de reversión de CS2\tSí\tNada. No se trata de una solución de seguridad que aborde la causa raíz. El acceso para la recuperación de cuentas por parte del servicio de asistencia no se ve afectado. Al activar la anulación, se aplica automáticamente un bloqueo de operaciones de 30 días (Skinvault ↗), mientras que la crisis en el mercado al contado provocó una caída de $104M (-25%) en la capitalización bursátil en las últimas 24 horas (CSMarketCap ↗). En 2026, los temporizadores pasaron a ser por artículo (Skin.land ↗).\t—\tPreguntas frecuentes ↗\n2025-05-14\tAnuncio sobre la seguridad de la cuenta\tSí\tGuía sobre Stealer y el secuestro de sesiones\t—\tanuncio ↗\n2024-10-02\tCS2 «The Armory»: retención de 7 días\tSí\tMercado de intercambio de artículos de la Armería\t—\tanuncio ↗\n2024-09-18\tRestricción comercial para el inicio de sesión en un dispositivo nuevo\tSí\tBloqueo de transferencias de 2 a 7 días en dispositivos nuevos\t—\tPreguntas frecuentes ↗\n2024-02-14\tSuspensión del cambio de nombre y avatar del perfil\tSí\tPeriodo de espera de 2 a 4 horas para realizar intercambios tras cambiar el nombre\t—\tpublicación ↗\n2023-12-04\tConfirmación a través del móvil para las claves API\tSin historial de cambios\tRegistro silencioso de claves solo mediante cookies\t≈6 años después de los paneles de la época de 2017\tpágina de desarrollo ↗\n2023-10-24\tAutenticación multifactorial (MFA) mediante SMS para la publicación de versiones de videojuegos\tSí\tPublicación de compilaciones en Steamworks\t—\tanuncio ↗\n2023-07-12\tAdvertencia sobre el contenido de la biografía personalizada\tSí\tEnlaces de phishing en las biografías\t—\tforo ↗\n2023-01-25\tPerfil {ENLACE ELIMINADO} y tiempo de recarga\tSí\tEnlaces en el texto del perfil\t—\tPreguntas frecuentes ↗\n2022-10-24\tRevisión del proceso de inicio de sesión y truncamiento de cookies\tSin historial de cambios\tSesiones robadas ilimitadas\t— (Migración de tokens de IAuthenticationService)\tnoticias ↗\n2022-10-12\tInicio de sesión mediante código QR en la aplicación móvil 3.0\tSí\tPanel de desautorización de sesión\t—\tnoticias ↗\n2022-05-10\tSe han eliminado los puntos finales de cancelación de operaciones\tSin historial de cambios\tIntercambio de ofertas (cancelar y reenviar)\t≈5 años después de los paneles de la época de 2017\tnúmero 325 ↗\n2020-05-25\tBloqueo de intercambios de 7 días en Dota 2\tSí\tReventa rápida de artículos\t—\tblog ↗\n2018-03-29\tBloqueo de intercambio de 7 días en CS:GO\tSí\tBlanqueo instantáneo de bots\t≈20 meses después de la declaración de julio de 2016\tblog ↗ archivado 2025-02-26 ↗\nFuentes: las entradas Valve enlazadas, las páginas de ayuda y los incidencias de GitHub, según la fecha indicada. Se implementaron tres correcciones decisivas sin registro de cambios (mayo de 2022, octubre de 2022 y diciembre de 2023) que fueron detectadas por los usuarios, sin que Valve las anunciara; esa asimetría forma parte del historial de aplicación. Los retrasos solo se calculan cuando la propia datación del expediente (declaración de julio de 2016; paneles de estafas de la época de 2017) proporciona el punto de partida; «—» significa que aquí no se ha establecido dicho punto de partida.\nParte A — Ficha técnica · Sección 6\nSimulador interactivo de vulnerabilidades y secuestros de sistemas\nContexto y límites de la fuente\n\nUna reconstrucción del proceso desde el mensaje de phishing hasta el registro de la clave en el servidor y la operación de intercambio. Antes de 2023, una clave de API web registrada en una cuenta podía consultar su inventario, cancelar una oferta de intercambio pendiente y crear una nueva, sin que se mostrara al titular de la cuenta ninguna pantalla de confirmación de la operación para ninguna de esas acciones. Esto supone una falta del principio del privilegio mínimo (OWASP A01:2021). Los tiempos que aparecen en esta simulación son ilustrativos y no constituyen mediciones en tiempo real de la plataforma actual.\n\nRepasa paso a paso el secuestro reconstruido. En cada fase se muestra lo que ve el titular de la cuenta y, junto a ello, la llamada Steam que recibe en ese mismo momento. Todas y cada una de esas llamadas se autentican correctamente. Ningún paso de la secuencia requiere que la autenticación de Steam falle; lo que se necesita es que la clave que emite no tenga ámbito (OWASP A01:2021).\n\nLo que ve el jugador. Lo que cambia detrás.SIMULADOR DE RECORRIDO\nPaso 5 / 5\n\nLa explotación se ha completado. Al esperar recibir una notificación en el móvil sobre su operación original, la víctima aprueba la operación sustitutiva. Se trata de un análisis forense integrado que muestra cómo la ausencia del principio del «privilegio mínimo» (OWASP A01:2021) permite el secuestro automatizado de activos en menos de un segundo.\n\n01 / EL SEÑUELO PARA CHATUn amigo me pide que voteLa víctima recibe un mensaje con un enlace.\n02 / EL INICIO DE SESIÓNUn portal de doblesLa víctima introduce sus datos de acceso.\n03 / EL ACCESOCreación de la API de Silent WebEl atacante registra una clave de desarrollador.\n04 / EL CAMBIOIntercambio comercial legítimoEl bot «Clone» duplica al destinatario seleccionado.\n05 / CONFIRMACIÓNFalsificación autorizadaSe ha aprobado una oferta errónea desde el móvil.\nEl mismo paso, visto desde la redReconstrucción del patrón anterior a 2023 · formas ilustrativas de las llamadas\nVíctimaAprueba el aviso en el móvil que se esperaba para la operación original.\nDelanteroRecibe los artículos en la cuenta clonada.\nSteam veUna transferencia confirmada por el titular de la cuenta en un dispositivo registrado.\nConfirmation genuine — made by the account holder\nRecipient the clone bot, not the intended counterparty\nThe confirmation is authentic. The offer it confirms is not the one the user initiated.\n\nEl legado que dejó: una transacción que el usuario aprobó. Ese es el registro que Steam Support consulta cuando se recibe la reclamación, y el motivo por el que las reclamaciones archivadas se cerraron como «error del usuario». Las reclamaciones se encuentran en el archivo de ejecución.\n\nParte A — Expediente técnico · Sección 7\nLos puntos finales que hay detrás de la secuencia.\nContexto y límites de la fuente\n\nEstos son los Steam puntos finales de la API web que los scripts de secuestro detectados utilizaban para interceptar operaciones sin pasar por los pasos de confirmación del navegador.\n\nCuatro puntos finales documentados se encargan de todo. Ninguno de ellos presenta fallos, ni es necesario aprovecharlos: una clave válida los invoca y Steam responde. La clave es lo único que el atacante tuvo que robar.\n\nIEconService / GetTradeOffers / v1ENCUESTA\n\nSe utiliza para supervisar las ofertas de negociación de la cuenta. Los scripts consultan este punto final repetidamente con la clave API comprometida; este devuelve los detalles de las ofertas de negociación recién creadas, pendientes o modificadas. En este caso no se miden los intervalos de consulta.\n\nVector de amenaza: Muestra los ID de las ofertas comerciales pendientes y los datos del perfil del destinatario.\nIEconService / CancelTradeOffer / v1INTERACCIÓN\n\nSe utilizaba para invalidar de forma automática la oferta de intercambio legítima del usuario. Antes de 2023, la clave no estaba protegida por ninguna autenticación de dos factores, por lo que un servidor automatizado podía cancelar una oferta tan pronto como se detectara, sin avisar al titular de la cuenta.\n\nVector de amenaza: Anula la operación antes de que el titular de la cuenta complete la confirmación a través del móvil.\nISteamUser / GetPlayerSummaries / v2RECON\n\nSe ha realizado una consulta para obtener el nombre del perfil, la URL de la imagen de avatar y el nivel del destinatario legítimo de la transacción. Esto permite que el script adapte una cuenta clonada previamente preparada para que coincida con los datos. Aquí no se mide el tiempo.\n\nVector de amenaza: Proporciona los datos necesarios para hacerse pasar por el destinatario previsto.\n/dev/ajaxregisterkeyCREACIÓN\n\nEl punto final de registro de Steam para las claves. Históricamente, cualquier sesión activa de cookies del navegador (`steamLoginSecure`) podía registrar una clave sin una confirmación Steam Guard en el dispositivo móvil y sin notificarlo al titular de la cuenta.\n\nVector de amenaza: Una credencial persistente creada por un script, sin que el titular de la cuenta se dé cuenta.\nParte A — Expediente técnico · Sección 8 · Artículo 7 del RGPD\nUna casilla marcada. ¿De quién es esa acción?\nContexto y límites de la fuente\n\nAl denegar el reembolso, Steam Las respuestas del servicio de atención al cliente conservadas en el archivo sostienen que el titular de la cuenta creó la clave API y que, al marcar la casilla, aceptó las condiciones.\n\nLa respuesta del servicio de asistencia atribuye la clave al titular de la cuenta. La cuestión es si el registro permite determinar quién lo creó realmente.\n\nSin embargo, en el patrón de secuestro de claves API observado, la víctima nunca vio ni accedió a la página de creación de claves API. El campo de consentimiento se envía mediante un script que ejecuta una solicitud POST «headless» con la cookie de sesión robada.\n\nDe conformidad con el artículo 7 y el artículo 4, apartado 11, del RGPD, el consentimiento debe ser una manifestación de voluntad libre, específica, informada e inequívoca del interesado. La postura de los autores es que un campo de aceptación de condiciones enviado por un script malicioso con una cookie robada, sin que se muestre ninguna página al titular de la cuenta, no puede ajustarse a esa definición. Corresponde a la autoridad de control determinar si así es.\n\nAnálisis forense de cargas útiles: registro de claves\nPUBLICAR https://steamcommunity.com/dev/ajaxregisterkey\n// Carga útil de la solicitud (inyectada mediante un script de secuestro)\n{\n\"agreeToTerms\": «de acuerdo», <-- generado automáticamente, sin intervención humana\n«dominio»: «localhost», ← no validado: se acepta cualquier valor, incluido «localhost»\n\"sessionid\": \"8f0d8ef763ab2140bf89de2a\"\n}\nLa pregunta para la autoridad de control: en los casos en que el titular de la cuenta nunca haya marcado la casilla de consentimiento, si la aceptación de las condiciones registrada en la cuenta cumple el requisito del artículo 7 de que constituya una manifestación de voluntad libre, específica, informada e inequívoca de los deseos del interesado, y si Steam el servicio de atención al cliente puede basarse en ello para desestimar una reclamación.\n\nFuente: forma de solicitud de registro de claves, tal y como se ha reconstruido a partir del punto de acceso público y de los informes de secuestro conservados en el archivo de pruebas (versión con función de búsqueda de 2026-09-17) · El identificador de sesión que se muestra es un marcador de posición, no un valor capturado.\n\nAutopsia forense · El vector de sustitución comercial\nCómo Valve logró finalmente neutralizar la «sustitución comercial» — y por qué se necesitaron siete años de soluciones provisionales\n\nDurante casi una década, el «Sustitución de claves API» (o estafa MitM de API) fue el modelo de robo de cuentas más lucrativo en Steam, con el que se sustrajeron cientos de millones de dólares en skins a jugadores desprevenidos. Valve no erradicó el exploit corrigiendo la arquitectura vulnerable de la API; en su lugar, Valve dedicó siete años a superponer cuatro barreras de fricción en toda la plataforma que paralizaron la liquidez del comercio de la comunidad, sin abordar la causa raíz.\n\n1. La muerte por mimetismo\nTiempo de espera para cambiar de avatar y nombre (febrero de 2024)\n\nLa vulnerabilidad requería una imitación en menos de un segundo: el bot fraudulento interceptaba una transacción saliente y extraía el avatar y el nombre del destinatario a través de ISteamUser, y clonó el perfil en 200 ms. El 14 de febrero de 2024, Valve implementó discretamente una medida obligatoria Tiempo de espera de 2 a 4 horas para realizar una transacción (Error 34) inmediatamente después de cualquier cambio en el nombre de perfil o en el avatar. Un bot ya no puede clonar a un destinatario sobre la marcha sin quedar bloqueado para realizar operaciones.\n\n2. La muerte económica\nInversión de tendencia de 7 días en CS2 (julio de 2025)\n\nValve introdujo medidas unilaterales Inversiones en las operaciones para objetos de Counter-Strike. Cualquier skin intercambiada se marca como «Protegida contra intercambios» durante siete días. Si una víctima descubre una sustitución, hace clic en «Reversar intercambio» en Steam Soporte, y el skin se devuelve al instante a su inventario, al tiempo que se bloquea al destinatario. Dado que el bloqueo de intercambio de 7 días impide que los estafadores trasladen el objeto a un sitio de cambio por dinero, el robo deja de ser rentable.\n\n3. La muerte de «Silent Key»\nNotificación push obligatoria para la API (diciembre de 2023)\n\nHistóricamente, una cookie de sesión robada permitía que los scripts maliciosos ejecutaran una solicitud POST en segundo plano y sin interfaz gráfica hacia /dev/ajaxregisterkey sin avisar a la víctima. El 4 de diciembre de 2023, Valve exigió una confirmación explícita mediante notificación push en la aplicación móvil Steam para generar una clave de API web, con lo que se eliminó la asignación silenciosa de claves en segundo plano.\n\n4. Avisos móviles dentro de la aplicación\nBanners con la antigüedad y el nombre de la cuenta (2022-2024)\n\nValve se ha rediseñado la ventana modal de confirmación para dispositivos móviles con el fin de mostrar el Steam antigüedad de la cuenta (fecha de creación), nivel Steam y una advertencia explícita de color ámbar: «Este usuario ha cambiado recientemente el nombre de su perfil», lo que rompe la ilusión óptica para las víctimas que prestan atención.\n\nLos tres fallos del «mosaico» de Valve: por qué los estafadores simplemente cambiaron de objetivo\n1. La laguna jurídica de la exclusión de juegos (Dota 2 y TF2)\n\nLas «Trade Reversals» se implementaron exclusivamente para Counter-Strike 2. Los objetos de Dota 2 y Team Fortress 2 siguen sin estar protegidos en absoluto debido a las complejidades de la creación y el engaste. Los objetos de alto nivel que valen miles de dólares (ganchos de garra de dragón, Baby Roshans dorados, llamas ardientes inusuales de TF2) no tienen ningún plazo de reversión. Los estafadores simplemente redirigieron la interceptación automatizada de la API hacia los comerciantes de Dota 2 y TF2, donde el servicio de atención al cliente de Steam aplica estrictamente su política de 2016 de «no restitución de objetos».\n\n2. El depósito «Zombie Key» (sin caducidad)\n\nMientras que Valve incorporó la autenticación de dos factores (2FA) mediante notificaciones push en el móvil para generar nuevo llaves en diciembre de 2023, Valve nunca se han revocado, caducado ni eliminado las claves de API heredadas existentes. Millones de cuentas activas que generaron claves (o en las que se crearon claves de forma silenciosa mediante phishing o malware antes de diciembre de 2023) siguen teniendo credenciales activas con caducidad nula (sin TTL) y tiempo de espera por inactividad nulo. Los autores de amenazas mantienen enormes bases de datos históricas con estas claves persistentes y siguen realizando consultas IEconService sin alteraciones.\n\n3. La sanción impuesta a la víctima: suspensión de operaciones durante 30 días\n\nIncluso en CS2, Valve penaliza al jugador estafado: al hacer clic en «Anular intercambio» en Steam Soporte, se inflige automáticamente un prohibición obligatoria de realizar operaciones y de acceder al Mercado Comunitario durante 30 días en la cuenta de la víctima. Valve sanciona al usuario con un mes de suspensión de la plataforma como medida disuasoria frente a las anulaciones «frívolas», lo que desalienta a las víctimas a anular operaciones con artículos líquidos de menor valor.\n\nEl escándalo regulatorio fundamental: siete años de soluciones provisionales frente a un único ámbito de aplicación de la API\n\n¿Por qué Valve dedicó siete años a inventar restricciones comerciales, tiempos de espera en las cuentas y bloqueos comerciales reversibles —lo que trastocó toda la economía del juego y provocó una pérdida de $104M en capitalización bursátil— en lugar de aplicar la solución estándar del sector?\n\nTal y como demuestra el lanzamiento oficial de Valve en Steamworks el 16 de enero de 2026 (Anuncio #493839547938902179 ↗), Valve ya construido Grupos de permisos detallados (General, Microtransacciones, Economía, Datos de ventas) y Lista blanca de direcciones IP para las claves de editor corporativas. Valve llevaba años disponiendo de la solución técnica. Una simple casilla de selección visible para el usuario—«Impedir que esta clave de la API web acceda a IEconService (Gestión de operaciones)» o una lista blanca de direcciones IP domésticas —habría erradicado la estafa de la sustitución comercial en 2018 sin causar ningún daño colateral económico. Valve se negó a ofrecer a los jugadores habituales la protección que había diseñado para sus socios corporativos.\n\nParte B — Normativa y historial de cumplimiento · Artículo 9\nSu reglamento. Las plataformas registradas.\nContexto y límites de la fuente\n\nEste libro mayor asocia las cláusulas explícitas del Steam Contrato de suscripción (SSA) y Steam Conducta en línea (SOC) directrices dirigidas directamente contra entidades comerciales activas y de gran envergadura.\n\nLa regla: Prohibido el uso comercial, los juegos de azar y los bots — y Steam El servicio de atención al cliente se acoge a esas cláusulas cuando se niega a devolver los artículos a una víctima. El historial: A primera vista, esas mismas cláusulas se aplican a las plataformas comerciales de este registro, que operan con Steam identidades, Steam bots y Steam transferencias. La cláusula se aplica a la persona que perdió las pieles y no, según consta en ningún registro público, a las empresas que las transportaban.\n\nEn las reclamaciones archivadas, Steam Support menciona el «Prohibido el uso comercial» y «Sin automatización ni bots» cláusulas que se invocan al negarse a restituir los artículos a las víctimas de fraude con claves API. A primera vista, esas mismas cláusulas se aplican a las plataformas comerciales recogidas en este expediente, que se autentican mediante Steam OpenID y transfieren los artículos a través de cuentas automatizadas Steam. Aquí no se estima ninguna cifra de ingresos para todo el mercado (véanse las estadísticas de aplicación de la ley más abajo). Lo que muestran los registros es la norma aplicada a cuentas individuales en los casos archivados y no existe ningún registro publicado de aplicación de la ley por operador para las plataformas. Esa asimetría es lo que documenta esta sección.\n\nLa cuestión central / aplicación selectiva de la leyNormas → Alcance → Rendición de cuentas\nUnas mismas normas. Una aplicación desigual.\n\nEl registro muestra que los servicios comerciales utilizan identidades Steam, inventarios, bots y transferencias como infraestructura operativa. La SSA prohíbe la explotación comercial y la automatización sin autorización. Las reclamaciones archivadas muestran que dicha norma se aplicó a cuentas individuales, mientras que el registro público no muestra un registro equivalente, operador por operador, para las plataformas aquí documentadas. Publique la norma, las pruebas y la resolución de ejecución correspondiente a cada una de ellas.\n\n189sitios web incluidos en el alcance de la auditoría\n44rutas de dominios independientes en el registro activo: 27 con un archivo de pruebas publicado y 17 recopiladas manualmente. Solo la auditoría de 189 sitios web resolvió 25 de ellas; el registro añade las rutas recopiladas manualmente.\n12 años y 6 mesescsgogem.com bloqueado en el filtro de enlaces; api.csgem.com registrado el 2014-03-08 y nunca bloqueado — uno de los 26 pares de este tipo a fecha del 2026-09-22\nTotal no verificadoSe ha excluido la estimación de ingresos para todo el mercado\nSteam Conducta en línea\n«…no deberás realizar ni intentar realizar ninguna de las siguientes acciones en Steam: […] Llevar a cabo actividades comerciales. Entre los ejemplos de este tipo de conductas prohibidas se incluyen: publicar anuncios; organizar concursos; juego; comprar o vender cuentas Steam; vender contenidos, tarjetas regalo u otros artículos; y mendigar».\n\nstore.steampowered.com/online_conduct ↗ archivado 2026-09-21 ↗\n\nSSA, artículo 2.G — Uso comercial\n«…[no podrá] explotar el Contenido y los Servicios ni ninguna de sus partes con fines comerciales, salvo en los casos expresamente permitidos en otras disposiciones del presente Acuerdo…»\n\nLas notificaciones de Valve de 2016, tal y como se ha informado, invocaban la licencia personal y no comercial. Ningún operador ha presentado una autorización Valve que conste en el expediente. store.steampowered.com/subscriber_agreement ↗ archivado 2026-09-18 ↗\n\nSteam Condiciones de uso de la API web\n«No está permitido utilizar la API web Steam ni los datos Steam de forma alguna que incumpla el Steam Contrato de suscriptor».\n\nLas plataformas de venta de skins de terceros operan mediante cuentas automatizadas que utilizan la API Steam. El texto de la norma no contempla ninguna excepción para la actividad a escala comercial. steamcommunity.com/dev/apiterms ↗ archivado 2026-09-21 ↗\n\nSSA, artículo 4.C\nAutomatización\n\nSe restringen los scripts, los bots y las interacciones no humanas. El libro mayor registra las operaciones realizadas por bots, las redes de cuentas y el enrutamiento automatizado a escala comercial.\n\nInspeccionar 153registros etiquetados con esta cláusula ↗\nLo que consta en el expediente en virtud de esta cláusula153 plataformas etiquetadas\nApertura del expediente15\nSkin Casino13\nMercado CS29\nRuleta de la piel8\ncsgoempire.com→csgoempirelogin4.comCasino\nrollbit.com→rbsnin.comCasino de criptomonedas\n500.casino→fivezerozero.coCasino con licencia\n\nDe ellos, 153 también están clasificadas en el artículo 2.G de la SSA y 2 también están clasificados en virtud del artículo 1.C de la SSA; estos mismos servicios se incluyen en más de una cláusula, por lo que los ejemplos se repiten.\n\n28 Se observaron casos de la «153» que se autenticaban a través de un dominio independiente susceptible de registro. Una etiqueta registra una observación fechada que hace que la plataforma entre, a primera vista, en el ámbito de aplicación de la cláusula; no se trata de una infracción sancionada, y no se ha presentado ninguna autorización de Valve para ninguno de ellos.\n\nSSA, artículo 2.G\nUso comercial\n\nLa explotación comercial requiere una autorización expresa. Compara los modelos de negocio documentados, su alcance y cualquier autorización o medida de cumplimiento que se haya hecho pública.\n\nInspeccionar 175registros etiquetados con esta cláusula ↗\nLo que consta en el expediente en virtud de esta cláusula175 plataformas etiquetadas\nApertura del expediente15\nSkin Casino13\nMercado CS29\nRuleta de la piel8\ncsgoempire.com→csgoempirelogin4.comCasino\nrollbit.com→rbsnin.comCasino de criptomonedas\n500.casino→fivezerozero.coCasino con licencia\n\nDe ellos, 153 también están clasificadas en el artículo 4.C de la SSA y 24 también están clasificados en virtud del artículo 1.C de la SSA; estos mismos servicios se incluyen en más de una cláusula, por lo que los ejemplos se repiten.\n\n28 Se observaron casos de la «175» que se autenticaban a través de un dominio independiente susceptible de registro. Una etiqueta registra una observación fechada que hace que la plataforma entre en el ámbito de aplicación de la cláusula tal y como está redactada; no se trata de una infracción sancionada, y no se ha presentado ninguna autorización de Valve para ninguno de ellos.\n\nSSA, artículo 3.A\nVPN y ocultación de la ubicación\n\nOcultar la dirección IP mediante un proxy puede dar lugar a la rescisión del contrato. Los servidores de autenticación con dominios independientes requieren un análisis por separado: hay que determinar qué se está ocultando y qué norma se aplica.\n\nRevisa la información sobre el servidor de autenticación ↗\nSteam Ayuda / Política de URL\nOcultación de enlaces\n\nSteam prohíbe los acortadores de enlaces y las herramientas que ocultan el destino de los enlaces. Un dominio de autenticación independiente — rbsnin.com En el proceso de inicio de sesión de Rollbit, auth.dota.trade en CS.MONEY — plantea la misma cuestión de si el destino que se muestra al verificador OpenID de Steam identifica el sitio operativo.\n\nPolítica de URL de Valve ↗\n\nReferencias normativas: Steam Contrato de suscripción, revisión del 10 de septiembre de 2026 archivado 2026-09-18 ↗ · Steam Condiciones de uso de la API web archivado 2026-09-21 ↗ · Steam Política de URL (ocultación de enlaces). Las cifras se refieren a los registros y las etiquetas de este expediente; no se trata de un recuento de infracciones sancionadas.\n\nEl déficit de confianza\n¿Quién revisa la decisión cuando el servicio de asistencia cierra el caso?\n\nLas reclamaciones conservadas describen sanciones permanentes, reclamaciones sin respuesta y negativas a restituir los artículos sustraídos. Contrasta esos relatos con el historial real de las entradas, las soluciones disponibles y los registros de acceso a la cuenta. Una explicación genérica basada en el phishing no puede determinar quién inició un restablecimiento o creó una clave API.\n\nLee las quejas registradas ↗Solicitar los registros correspondientes →Gráfico de relaciones de los moderadores →\nParte B — Normativa y historial de cumplimiento · Artículo 10\nUna API de automatización. Una norma contra la automatización.\nContexto y límites de la fuente\n\nLa cuestión que plantea esta sección es cómo se concilian ambos aspectos: qué usos de la API están autorizados, quién los autoriza y según qué criterios publicados. Aquí no se estima el número de usuarios comerciales autorizados de la API, y la ausencia de una lista publicada no implica tal cifra; la ausencia es la conclusión, no una cifra que haya detrás. Los mensajes de asistencia Steam citados anteriormente han sido reproducidos por el proyecto ArchiSteamFarm en su propia sección de preguntas frecuentes (verificados textualmente 2026-09-22); no se trata de Valve publicaciones, y no se identifican las cuentas a las que se enviaron.\n\nLa norma (SSA, artículo 4.C): No se admiten scripts, bots ni sistemas no humanos en Steam. El historial: Valve ofrece una API REST sin interfaz de usuario cuyo único objetivo es la automatización de servidor a servidor, y proporciona la clave a cualquier cuenta. Se bloquea a los usuarios que utilicen herramientas de automatización; la interfaz de automatización es un producto propio de Valve. Nunca se ha publicado qué usos comerciales están autorizados.\n\nLa falacia del «desarrollador de videojuegos»\nSDK de Steamworks (original)\n\nLo utilizan los estudios de videojuegos legítimos para integrar logros, emparejamiento y tablas de clasificación en los clientes de sus juegos. Requiere una integración compleja en C++ y la incorporación como socio oficial.\n\nSteam API web (La laguna jurídica)\n\nUna arquitectura JSON/REST sin encabezado diseñada para servidores web externos. En el patrón de secuestro que aquí se documenta, se utiliza para leer inventarios y manipular intercambios entre pares desde servidores remotos; sus usos legítimos no se recogen en este informe.\n\nPara quién es la llaveUn usuario normal Steam no necesita una clave de API web dentro de la aplicación; la página de claves se encuentra en una URL para desarrolladores y su finalidad, según la documentación, es el acceso externo desde el lado del servidor. Las denuncias archivadas por suplantación de identidad describen casos de víctimas que no sabían que esa página existía hasta que se había registrado una clave en su cuenta.\nLa contradicción de la automatización\n\nEl artículo 4.C de la SSA establece lo siguiente: «No está permitido utilizar ningún tipo de scripts, bots, macros u otros sistemas no controlados por personas («automatización») para interactuar de ninguna manera con el Contenido y los Servicios de Steam». Sin embargo, los puntos finales de la API web (como CancelTradeOffer) no requieren interfaz de usuario ni captcha y eluden por completo el cliente Steam. La API está diseñada para la automatización de servidor a servidor; la norma prohíbe la automatización por parte de los usuarios; la línea divisoria entre ambas no se ha hecho pública.\n\nUn puesto del lado del servidor en el flujo comercial\n\nUna clave de API web permite que un servidor externo realice operaciones en la cuenta sin necesidad del cliente Steam. En el patrón de secuestro, dicho servidor se interpone entre el titular de la cuenta y el servidor de operaciones.\n\n→No aparece ninguna pantalla de confirmación de operación para las acciones realizadas con la tecla.\n→Permite la consulta en segundo plano (GetTradeOffers).\n→Cancela y vuelve a emitir ofertas sin necesidad de que el usuario intervenga.\nValve ha creado la interfaz, ha prohibido la automatización por parte de los usuarios en sus normas y no ha publicado ningún criterio sobre qué usos comerciales están autorizados.\nParte B — Normativa y historial de cumplimiento · Artículo 11\nSe exigían diez días. Había que rendir cuentas de diez años.\nContexto y límites de la fuente\n\nEl 20 de julio de 2016, el consejero jurídico de Valve fijó un plazo de 10 días a los operadores de juegos de azar. Diez años después (a fecha de la captura de pantalla del expediente, 2026-09-21), al menos una de las plataformas mencionadas en las noticias de prensa sobre dicho aviso, CSGOFast, sigue operativa con un servidor de autenticación en un dominio independiente. A continuación se reconstruye el texto a partir de las noticias de prensa del 21 de julio de 2016; la reconstrucción no es un escaneo. El expediente de ejecución al que aludía el aviso no se ha publicado. La carta abierta a la Comisión es Sección 2.\n\nLee el aviso de julio de 2016 que figura junto a las observaciones posteriores. Lo que aún falta es un registro de cumplimiento por cada operador.\n\nUna semana antes — 13 de julio de 2016, en público\n\nEl 13 de julio de 2016 archivado 2026-09-21 ↗, Valve describió cómo los sitios web de apuestas utilizaban Steam: OpenID para la identificación de cuentas y cuentas automatizadas para las operaciones. Valve afirmó que el uso de esos mecanismos para gestionar un negocio de apuestas infringía su API y sus acuerdos de usuario. Tanto la descripción del mecanismo como la prohibición figuran en la propia declaración fechada de Valve. En 2026-09-21, los servidores de autenticación de dominios independientes sometidos a prueba no devolvieron ningún bloqueo de filtro de enlaces, y Valve no ha publicado ningún registro de aplicación específico por operador.\n\nANEXO A / JULIO DE 2016RECONSTRUCCIÓN TIPOGRÁFICA\nVALVE CORPORATION\n\nBellevue, WA\n\nFECHA:Julio de 2016 (según informó la prensa el 21 de julio de 2016)\nDE:Karl Quackenbush, consejero jurídico general\nAsunto:Cese y desistimiento — uso comercial de cuentas Steam\nNOTA:Reconstrucción del texto facilitado; no es un escaneo\n\n«Sabemos que gestionas uno de los sitios web de apuestas que se enumeran a continuación. Está utilizando Steam cuentas para llevar a cabo esta actividad. Según el Steam Contrato de Suscripción, los servicios Steam y Steam están autorizados únicamente para uso personal y no comercial».\n\n«Debes cesar y abstenerte de inmediato de seguir utilizando tus cuentas Steam con fines comerciales. Si no lo haces, en un plazo de diez (10) días, «Valve emprenderá todas las acciones legales a su alcance, incluida, entre otras, la cancelación de tus cuentas».\n\nReconstrucción del expediente · consultar el registro original\nKarl Quackenbush\nConsejero jurídico general, Valve Corp.\nAL MARGEN / EDITORIAL\nDiez días.¿Y luego qué?\n\nEl plazo era concreto. El seguimiento por parte de la ciudadanía también debería serlo.\n\nLa postura de Valve sobre «2016» ↗\nNota sobre el plazo límite +\nSÁTIRA / NO ES CORRESPONDENCIA DE VALVE\n\nEstimada fecha límite:\n\nTe dieron diez días. Por alguna razón, el calendario fue lo único que siguió funcionando.\n\nPor favor, remita cualquier respuesta al registro público.\n\nCronologíaJulio de 2016 – septiembre de 2026\nPlazo indicado en el anuncio:\n10 días\nJulio de 2016\nTiempo transcurrido desde la notificación:\n3,715 días\nCifra fija desde el 20 de julio de 2016 hasta la instantánea del expediente del 21 de septiembre de 2026; no se trata de una cifra en tiempo real.\nExpediente de ejecución publicado:\nNinguno\nNo se ha encontrado ningún registro por operador de cortes o bloqueos\n\n◀ Días 0-10 — el plazo, a escalaDía 3715 — la instantánea ▶\n\n20 de julio de 2016Se ha emitido un requerimiento de diez díasDía 0\n17 de febrero de 2024Se aplican las obligaciones de la DSADía 2,768\n25 de febrero de 2026Se ha anunciado la denuncia de la Fiscalía General de Nueva YorkDía 3,507\n21 de septiembre de 2026Resumen del expedienteDía 3715\n\nDiez años después, CSGOFast —mencionado en las noticias de prensa sobre los avisos de 2016— está operativo: csgofast.com devolvió un bloqueo de Link Filter en 2026-09-19 y 2026-09-21, mientras que su servidor de autenticación steam-login.authtofast.com (registrado 2026-06-30) no lo hizo.\n\nRegistro completo y con fecha de los cambios de seguridad de Valve: Cronología de la seguridad → · El historial de Washington y el criterio de aplicación: a continuación\n\nLo que consta en el expediente: La notificación de 2016 establecía un plazo de 10 días; Valve ya gestionaba una lista de dominios (el «Link Filter») y recibía los nombres de host de autenticación en sus propias solicitudes de OpenID; no se ha publicado ningún registro de medidas coercitivas por operador. Los informes de la comunidad describen una medida tomada en 2018 contra un mercado (SkinJar), pero dichos informes no han sido verificados y no se tienen en cuenta en este documento.\nCSGOFAST / LA RUTA DE AUTENTIFICACIÓN GUARDADA\nSigue al servidor de retorno indicado.\n\nLos enlaces de los registros de rutas guardados csgofast.com a steam-login.authtofast.com. El nombre de host independiente se incluye en la solicitud OpenID Steam. Esto proporciona a los investigadores una dirección concreta que pueden comparar con los registros de filtrado y aplicación de Valve.\n\nConsulta la ruta de CSGOFast y su origen ↗ · Comparar resultados guardados Steam Filtro de enlaces ↗\n\nARCHIVO PÚBLICO / WASHINGTON · 2016 → 2026\nDos plazos. Una norma de aplicación sin respuesta.\n20 de julio\nValve concede a los sitios web de apuestas un plazo de 10 días\n\nEn la notificación de su abogado se advertía de que el uso comercial continuado de las cuentas Steam podría dar lugar a la rescisión del contrato.\n\n27 de septiembre\nWashington presiona Valve\n\nLa Comisión de Juegos de Azar del estado exigió pruebas de las medidas adoptadas para impedir las transferencias de «skins» con fines de juego y fijó el 14 de octubre como fecha límite para responder.\n\n17 de octubre\nValve rechaza la acusación\n\nValve respondió tras el plazo establecido, negó que facilitara las apuestas, afirmó que había desactivado las cuentas relacionadas y señaló que no quería desactivar el comercio ni OpenID para todos los usuarios. Al menos una de las plataformas mencionadas en las noticias de prensa sobre las notificaciones de julio (CSGOFast) seguía en funcionamiento una década después. Ambos hechos solo pueden ser ciertos si el operador sustituyó las cuentas desactivadas; el registro que lo demostraría no se ha publicado. La WSGC debería pedir a Valve que aclare esta contradicción.\n\n2026\nLas rutas observadas en septiembre de 2026\n\nEl registro de rutas recoge 44 plataformas que se autentican a través de servidores de autenticación de dominios independientes, entre ellas CSGOFast, utilizando los mecanismos OpenID y de intercambio Valve descritos en 2016. No se ha presentado el registro de medidas coercitivas que indicaría qué operadores fueron bloqueados.\n\nINFORME DE LA PROPIA COMISIÓN · 30 DE ENERO DE 2018\nDieciocho meses después de que Valve respondiera, el organismo regulador seguía considerándolo una intención.\n\nEn la sesión informativa celebrada ante su propia asamblea legislativa durante la audiencia pública sobre el proyecto de ley HB 2881, la Comisión describió la declaración de julio de 2016 con sus propias palabras: Valve «anunció su intención de tomar medidas enérgicas contra el uso de su plataforma para facilitar las apuestas con skins». En esa misma página se recoge el impacto que tuvo ese anuncio en las previsiones del sector — «como consecuencia de ello», La previsión para el mercado de las apuestas con «skin» en 2020 se revisó de $19.7 mil millones a $670 millones, una caída de alrededor del 97 por ciento, solo a raíz del anuncio. La previsión se modificó. El informe de cumplimiento por operador que lo justificaría aún no se ha publicado.\n\nLas cifras de mercado son estimaciones de Narus Advisors / Eilers & Krejcik Gaming reproducidas en el informe de la Comisión, no conclusiones de la propia Comisión; el mismo documento sitúa las apuestas con «skins» en 2016 en unos $5 mil millones, de los cuales aproximadamente $3 mil millones correspondieron a sitios web tipo casino. Recuperado el 2026-09-22, SHA-256 c507c9025f93da0aadaf395c4d8882f25973211c318ee8e9b6f18a5b3755e050.\n\nLa postura pública de Valve en 2016 y la infraestructura observable en la actualidad pueden compararse. La cuestión es si las medidas de control llegaron a las cuentas y rutas utilizadas por los operadores prohibidos. Un plazo de preaviso de diez días no constituye prueba de que se haya notificado a todos los operadores mencionados en el mismo. La medida tomada por OPSkins en 2018 es la única intervención documentada contra un operador concreto; teniendo en cuenta que se revisaron 189 plataformas y que no se ha publicado ningún registro por operador, una única medida documentada no pone de manifiesto un patrón de aplicación de la normativa.\n\nComunicado de 2016 de la Comisión del Juego de Washington ↗ archivado 2026-05-20 ↗ · Respuesta de Valve del 17 de octubre de 2016 (copia del documento) ↗ · Sesión informativa del WSGC ante la Asamblea Legislativa, 30 de enero de 2018 (copia local, 4 págs.) ↗ · el mismo archivo en wsgc.wa.gov ↗ · registro de recuperación y hash ↗ · La acción de Valve en OPSkins en 2018 ↗ archivado 2026-03-07 ↗ · Auditoría de la ruta actual ↗\n\nAuditoría forense longitudinal · Objetivos de las órdenes de cese y desistimiento de 2016\nLa década del preaviso de 10 días: auditoría forense de supervivencia de los 23 emplazamientos señalados\n\nLos días 19 y 20 de julio de 2016, Valve el consejero jurídico Karl Quackenbush emitió notificaciones formales de cese y desistimiento a 23 plataformas de apuestas con «skins», ordenándoles que cesaran el uso comercial de Steam cuentas dentro de 10 días bajo la amenaza de la cancelación de la cuenta y de acciones legales. Más de 3,700 días después, una auditoría empírica revela el verdadero patrón de aplicación de la normativa: numerosos operadores nunca cesaron su actividad, otros siguieron operando hasta seis años después de la fecha límite, y el ecosistema, valorado en miles de millones de dólares, siguió aprovechando la arquitectura OpenID de Valve.\n\n5+ EN DIRECTO\nDefinitivamente en funcionamiento en 2026 (CSGOBig, CSGO500, CSGOFast, etc.)\n6 AÑOS\nPeriodo más largo de actividad tras el aviso previo al cierre (CSGOatse estuvo activo hasta 2022)\n$5.01B\nVolumen de apuestas «skin» en 2016 (Narus / Eilers & Krejcik)\nMás de 200\nSitios web de apuestas en línea activos que operan en el momento álgido del mercado\nLos «Surviving Titans» · Plan financiero y de tráfico para 2024-2026\nDesde avisos con 10 días de antelación hasta conglomerados con sede en el extranjero: un volumen de negocio de varios miles de millones de dólares\n\nEn lugar de acabar con las apuestas con «skin», los avisos de Valve de 2016 impulsaron una evolución del sector. Los operadores que sobrevivieron se reestructuraron como entidades corporativas extraterritoriales (Curazao, Belice, Chipre), fueron pioneros en el comercio entre pares (P2P) para eludir las prohibiciones de los bots y ahora procesan más de 10 millones de visitas mensuales a la web y miles de millones de dólares en volumen anual de apuestas sin dejar de autenticarse a través de Steam:\n\nPlataforma / Dominio\tAviso de julio de 2016\tResultado de la ejecución y situación de supervivencia\tVerificación registrada / Enlaces principales\nCSGOBig\ncsgobig.com\tAviso con 10 días de antelación (julio de 2016)\tSIGO VIVIENDO EN 2026\nSe ha suspendido temporalmente y se ha relanzado; la autenticación se realiza a través de letmeinbig.com y csgobiglogin.com\tX: @csgobig ↗ · FB: csgobigofficial ↗\nCSGO500\ncsgo500.com / 500.casino\tAviso con 10 días de antelación (julio de 2016)\tSEGUIRÉ VIVIENDO EN 2026\nRenombrado como 500 Casino (licencia de Curazao n.º 8048/JAZ2014-037), con una facturación mensual de varios millones\tPlataforma en directo (500.casino) ↗\nCSGOFast\ncsgofast.com\tAviso con 10 días de antelación (julio de 2016)\tSEGUIRÉ VIVIENDO EN 2026\nOferta activa de ruleta, Crash y Jackpot a través de steam-login.authtofast.com\tExpediente de auditoría de autenticación ↗\nCSGOLounge / Dota2Lounge\ncsgolounge.com / dota2lounge.com\tAviso con 10 días de antelación (julio de 2016)\tSEGUIRÉ VIVIENDO EN 2026\nSe ha reorientado hacia las apuestas con monedas de los esports y las apuestas con criptomonedas; ha mantenido su funcionamiento ininterrumpido\tPlataforma en directo ↗\nCSGOCasino\ncsgocasino.net / csgocasino.gg\tAviso con 10 días de antelación (julio de 2016)\tEN DIRECTO A TRAVÉS DE SUCCESSOR (2026)\nEl dominio ha sido redirigido; el portal sucesor, ya operativo, funciona en csgocasino.gg\tDominio sucesor ↗\nCSGOatse\ncsgoatse.com\tAviso con 10 días de antelación (julio de 2016)\tHA PERDURADO 6 AÑOS (EN ACTIVO HASTA 2022)\nLas operaciones de juego continuaron sin interrupción durante seis años tras el ultimátum de 10 días de Valve\tX: @CSGOatsecom (Activo hasta 2022) ↗\nCSGOSweep\ncsgosweep.com\tAviso con 10 días de antelación (julio de 2016)\tVIVIÓ HASTA DICIEMBRE DE 2017\nPermaneció en funcionamiento público durante 17 meses tras la fecha límite\tX: Estado de CSGOSweep, diciembre de 2017 ↗\nCSGOWild\ncsgowild.com\tAviso con 10 días de antelación (julio de 2016)\tVIVIÓ HASTA DICIEMBRE DE 2017\nPromocionado por influyentes de gran alcance; estuvo en funcionamiento durante un año y medio tras la carta de cese y desistimiento, antes de la migración a las criptomonedas.\tX: @Wild (Activo en diciembre de 2017) ↗\nCSGOPot\ncsgopot.com\tAviso con 10 días de antelación (julio de 2016)\tVIVIÓ HASTA SEPTIEMBRE DE 2017\nLlevaba 14 meses operando apuestas con botes de alto riesgo tras haber recibido la notificación\tX: @csgopot (Activo en septiembre de 2017) ↗\nCSGODiamonds\ncsgodiamonds.com\tAviso con 10 días de antelación (julio de 2016)\tSUPERÓ LA METAD DE 2017\nSe mantuvo en marcha durante 2017 a pesar de que se admitió que se habían manipulado los resultados de los streamers patrocinados\tX: @csgodiamondscom (2017) ↗\nCSGOLotto\ncsgolotto.com\tAviso con 10 días de antelación (julio de 2016)\tCERRADO EN JULIO DE 2016\nCerró tras un escándalo público; objeto de una orden de consentimiento de la FTC federal\tOrden de consentimiento de la FTC (expediente C-4632) ↗\nCSGODouble\ncsgodouble.com\tAviso con 10 días de antelación (julio de 2016)\tCERRADO EN JULIO DE 2016\nCierre voluntario inmediatamente después de la publicación de la orden de cese y desistimiento\tX: @CSGODouble (Cerrado en julio de 2016) ↗\nCSGOMassive\ncsgomassive.com\tAviso con 10 días de antelación (julio de 2016)\tCERRADO EN 2016\nCessó su actividad pública a finales de 2016\tX: @csgo_massive ↗\nCSGOStrong\ncsgostrong.com\tAviso con 10 días de antelación (julio de 2016)\tCERRADO EN 2016\nCessó su actividad pública en 2016\tFB: csgostrongfree ↗\nSkins2\nskins2.com\tAviso con 10 días de antelación (julio de 2016)\tCERRADO EN 2016\nCessó su actividad pública en 2016\tFB: CSNCOM ↗\n\nPlataforma\tTráfico mensual (visitas)\tVolumen de negocio estimado\tEntidad jurídica y jurisdicción\tPrincipales medidas normativas y modelo\nCSGOEmpire\ncsgoempire.com\t2,3 millones — 9,0 millones al mes\nDuración media: más de 6 minutos; 80% directo\t$1.5B — $2.5B Volumen de negocio anual\n>1,000,000 operaciones de intercambio de skins P2P al mes; $6.4M de volumen de órdenes activas y líquidas\tMoonrail Limited B.V. (Curazao n.º 148182)\nPagos: JHOLT LTD (Chipre); Fundador: «Monarch» (Ossi Ketola)\tPioneros en el intercambio de artículos P2P sin comisiones; con licencia de Curazao OGL/2024/1183/0869\nCSGORoll\ncsgoroll.com\t2,74 millones — 3,5 millones al mes\nDuración media: 9 min 23 s; tasa de rebote: 16%\t$1.0B — $2.0B Volumen de negocio anual\nIngresos corporativos anuales estimados de entre $100M y $200M procedentes de la ventaja de la casa\tFeral Holdings Limited\nCon sede en la ciudad de Belice, Belice (n.º de registro 171519)\tProhibido por la ACMA australiana (mayo de 2023); patrocinaba al equipo de primera división G2 Esports, que contaba con jugadores menores de edad\n500 Casino (CSGO500)\n500.casino / csgo500.com\t220 000 — 425 000 al mes\n~105 000 visitantes únicos al mes\t$100k / semana ($5.2M/año) en Royales\nRequisito de apuesta para grandes apostadores: $400 de apuesta por cada $1 de rakeback\tPerfect Storm B.V. (Curazao n.º 150536)\nLicencia de la Junta de Control del Juego de Curazao OGL/2024/1354/0882\tProhibida por la Spelinspektionen sueca (noviembre de 2023) por dirigirse a jugadores suecos sin licencia\nCSGOBig\ncsgobig.com\t~169,600 / mes\nDuración media: 19 min 12 s; primarias de EE. UU.\tVolumen anual multimillonario\nCajas misteriosas, ruleta y batallas por cajas\tFunciona mediante enrutamiento por proxy auxiliar\nletmeinbig.com (registrado en 2023) y csgobiglogin.com\tTarget de julio de 2016 C&D; relanzado con arquitectura de autenticación por proxy\nCSGOFast\ncsgofast.com\t~150 000 — 250 000 al mes\nPúblico internacional multilingüe\tVolumen anual multimillonario\nJuegos de ruleta y «crash» de alta velocidad\tEntidades operativas extraterritoriales\nRutas Steam autenticación a través de steam-login.authtofast.com\tObjeto de la orden de cese y desalojo de julio de 2016; nunca cesó su actividad; en funcionamiento en 2026\nCSGOPolygon\ncsgopolygon.com / plg.bet\t~300 000 — 500 000 al mes\nEl dominio de la CEI y Europa del Este\tVolumen anual multimillonario\nCriptomonedas y ruleta de skins, apuestas en partidos\tObjetivo de la segunda fase (octubre de 2016)\nSe ha reorientado hacia las criptomonedas con el dominio espejo plg.bet\tHa sobrevivido una década completa; sigue liquidando skins a través de API de terceros\nLa segunda oleada: por qué la notificación de cese y desistimiento de Valve se dirigió a más de 43 sitios web en total\n\nEl 17 de octubre de 2016, el asesor jurídico de Valve comunicó oficialmente a la Comisión de Juegos de Azar del Estado de Washington que, tras las 23 notificaciones iniciales del 19 de julio, Valve había enviado cartas de cese y desistimiento a más de 20 sitios web adicionales de apuestas con «skins» (con lo que el total oficial supera los 43). Esta segunda ronda se hizo necesaria porque la lista inicial omitía, inexplicablemente, los centros de juego más grandes y famosos del mundo:\n\nCSGOJackpot.com: La empresa pionera en el sector de las apuestas clandestinas, que gestionó un volumen de cientos de millones antes de cerrar ante la amenaza de una acusación federal.\nCSGOShuffle.com: La plataforma que se vio envuelta en el escándalo de las retransmisiones de julio de 2016, en la que el streamer de Twitch PhantomL0rd era propietario en secreto del 33% de la empresa y se descubrió que manipulaba las cuotas con fondos de la propia plataforma.\nEl macroecosistema (más de 200 operadores): Según un estudio del sector realizado por Narus Advisors y Eilers & Krejcik Gaming, en 2016 operaban más de 200 sitios web distintos de apuestas con «skins», que generaron $5.01 mil millones en volumen de apuestas procedentes de 3,03 millones de jugadores activos. Las 43 cartas de Valve se dirigían a menos de 20% del mercado activo.\nInvestigaciones oficiales gubernamentales y reguladoras sobre el juego «Steam Skin Gambling»\n\nEl fenómeno de las apuestas con «skin» está documentado en múltiples investigaciones oficiales, medidas coercitivas y documentos de posición del Gobierno:\n\n1. Comisión de Juegos de Azar del Estado de Washington (WSGC) (2016-2018)\n\nEl 5 de octubre de 2016 se emitió una requerimiento formal de cese y desistimiento; el 30 de enero de 2018 se publicó un informe legislativo en el que se documentaba que los «skins» son equivalentes al efectivo y se daba a conocer el volumen de apuestas con «skins» de $5.0B.\n\nInforme legislativo del WSGC en formato PDF (copia local) ↗\n2. Comisión Federal de Comercio de EE. UU. (FTC) (septiembre de 2017, expediente C-4632)\n\nPrimera medida coercitiva reguladora federal relacionada con las apuestas con «skins» contra los propietarios de CSGOLotto, Trevor Martin y Thomas Cassell, por prácticas engañosas y control no revelado de la plataforma.\n\nResolución y orden de consentimiento de la FTC ↗\n3. Documento de posición de la Comisión del Juego del Reino Unido (UKGC) y auditorías sobre los jóvenes\n\nLas skins del juego se clasificaron oficialmente como «dinero o algo equivalente al dinero» en virtud de la Ley de Juegos de Azar de 2005. Encuestas posteriores revelaron que más del 11% de los niños de entre 11 y 16 años habían apostado skins en videojuegos.\n\nRepositorio de investigación de la UKGC ↗\n4. Investigación del Senado australiano sobre Medio Ambiente y Comunicaciones (2018)\n\nInforme del Parlamento Federal sobre «Microtransacciones en videojuegos para obtener objetos aleatorios», en la que se analizan la mecánica de las cajas de botín de Valve, las retiradas de dinero en el mercado secundario y la elusión de la normativa.\n\nInvestigación del Parlamento de Australia ↗\nLa demanda pendiente\n\nPublicar el informe de medidas coercitivas: qué cuentas de juego y bots se han desactivado, a qué servidores de respuesta se ha restringido el acceso y a qué servicios comerciales se les ha concedido permiso. Una prohibición pública y una advertencia en la página de inicio no demuestran que se haya detenido la operación subyacente.\n\nParte B — Normativa y historial de cumplimiento · Artículo 12\nEl nombre de host ya figura en la solicitud.\nLímites del contexto y de la fuente\n\nValve ya dispone de una lista de dominios (el «Link Filter») y ya recibe el nombre de host de autenticación en cada solicitud de OpenID. El pseudocódigo que aparece a continuación muestra la estructura lógica para conectar ambos elementos. No hay pruebas públicas que indiquen que Valve lo haga.\n\nValve ya mantiene una lista negra de dominios. Valve ya recibe el host de inicio de sesión en cada solicitud de OpenID. No hay que construir nada: solo hay que unir las dos cosas. Se trata de una consulta de nombre de host en una lista que Valve mantiene por sí misma. El pseudocódigo que aparece a continuación es un ejemplo ilustrativo, no la implementación de Valve.\n\nforensic_autoban.py\n# PSEUDOCÓDIGO ILUSTRATIVO — Valve.block_domain() y flag_session_as_mitm() no son llamadas reales a la API. Esto ilustra la estructura lógica de una medida de mitigación que Valve podría implementar frente a dominios de autenticación por proxy, no el funcionamiento interno real de Valve.\n# Ilustración: el esquema lógico de una comprobación de la solicitud de OpenID recibida\ndef audit_openid_request(solicitud):\nblocked_origins = base de datos.obtener_plataformas_en_la_lista_negra()\nproxy_domain = request.params.obtener(«openid.realm»)\ntarget_redirect = request.params.obtener('openid.return_to')\n\n# Lógica: Si el proxy redirige a un sitio bloqueado, bloquear el proxy.\npara sitio web en blocked_origins:\nsi sitio web en target_redirect:\nValve.bloquear_dominio(proxy_domain)\nValve.marcar_sesión_como_MITM(request.session)\n# Resultado: Se rechaza la solicitud de inicio de sesión para ese host\n\nObservación:\nCuando un dominio principal ya figura en el filtro de enlaces (por ejemplo, howl.gg, bloqueado 2026-09-18/19/21) y su host de autenticación (howl.uno) aparece en la solicitud OpenID procedente del botón de inicio de sesión de ese sitio, la asociación es observable para Valve a partir de sus propios datos de solicitud. La comprobación se puede automatizar; sin embargo, no se puede determinar si se lleva a cabo.\nPrecedentes documentados y comunicados\n\nValve ha intervenido contra un operador externo al menos una vez, según consta: en 2018 revocó el acceso de OPSkins al sistema ExpressTrade (El anuncio de Valve ↗ archivado 2026-03-07 ↗). Los informes de la comunidad de 2018 también describen cómo una plataforma de comercio (SkinJar) perdió el acceso; dichos informes no han sido verificados y el mecanismo se deduce a partir del resultado, no de un proceso revelado.\n\nLo que establece el precedente:\n\nValve puede bloquear el acceso de un operador externo cuando lo considere oportuno. CSGOFast, mencionado en las noticias de prensa sobre las notificaciones de julio de 2016, operaba en 2026-09-21 con un servidor de autenticación registrado en 2026-06-30 que no devolvía ningún bloqueo de Link Filter. No hay ningún criterio publicado que explique por qué se bloqueó a un operador y a otros no.\n\nLo que indica y lo que no indica una fecha de inscripción\n\nLa fecha de registro de un host de autenticación constituye el límite inferior de cuándo podría haber aparecido por primera vez dicho host en una solicitud OpenID; no implica un uso continuado. sc-auth.net, por ejemplo, se registró como 2019-04-02 (RDAP) y se observó en el flujo de inicio de sesión Steam de Skin.Club en septiembre de 2026; lo que ocurrió entre esas dos fechas no figura en los registros públicos.\n\nAuditoría comparativa: Normas de cumplimiento de la API\nDimensión de la aplicación de la ley\tNormas de la API de GitHub\tSteam API web (Valve)\n1. Neutralidad en materia de cumplimiento\tSe aplican a todas las cuentas normas publicadas y uniformes, así como límites de frecuencia documentados (por ejemplo, 5,000 llamadas/hora para usuarios autenticados, 15,000/hora para organizaciones de GitHub Enterprise Cloud) y políticas de uso aceptable publicadas.\tNo hay criterios publicados. Las cuentas individuales se cierran en virtud de las cláusulas de automatización y uso comercial (quejas archivadas), mientras que no se ha publicado ningún historial de medidas coercitivas por operador para las plataformas comerciales.\n2. Uso indebido de OpenID / proxy de autenticación\tLas políticas publicadas por GitHub permiten suspender o revocar las aplicaciones y los tokens de OAuth en caso de uso indebido, y su documentación describe la revocación automática de los tokens expuestos (resumen de la documentación de GitHub elaborado por los autores).\tLos servidores de autenticación de dominios independientes observados en Steam flujos de OpenID (por ejemplo, rbsnin.com, howl.uno, sc-auth.net) no provocaron ningún bloqueo del filtro de enlaces en 2026-09-21, mientras que sus dominios principales sí lo hicieron.\n3. Monetización del abuso\tGitHub no cobra comisión por las transacciones de artículos gestionadas mediante automatización de terceros; su modelo de ingresos se basa en las suscripciones y los anuncios en su mercado.\tValve vende las llaves de las cajas que permiten obtener los objetos, y el Mercado de la Comunidad cobra una comisión conjunta de aproximadamente 15% sobre las ventas realizadas en el propio Mercado. En este informe no se estima ninguna cifra correspondiente a los ingresos atribuibles a plataformas de terceros.\n4. Duración de los bucles de evasión\tLos ID de cliente de OAuth suspendidos dejan de funcionar en toda la plataforma en el momento de la suspensión; la documentación no indica un plazo para la aplicación de la medida y aquí no se asume ninguno.\tLos servidores de autenticación de dominios independientes con fechas de registro comprendidas entre 2011 y septiembre de 2026 no mostraron ningún bloqueo por parte del filtro de enlaces en las comprobaciones de 2026-09-19 y 2026-09-21. La fecha de registro constituye un límite inferior del posible uso, no una prueba de uso continuado.\nFuentes: Columna de GitHub — Documentación publicada por GitHub sobre los límites de tasa de la API y la política de la plataforma (resumen de los autores, sin citas) · Columna Steam — Comprobaciones del filtro de enlaces de 2026-09-19 y 2026-09-21 (linkfilter-recheck-2026-09-21.json), registro RDAP (registro-de-dominios.json) y las reclamaciones de asistencia archivadas (archivo de pruebas).\nParte B — Normativa y historial de cumplimiento · Artículo 13\nLa diferencia de precio «off-Steam»\n\nEl artículo se encuentra en un inventario Steam; la venta se realiza en otro lugar. Un AWP Dragon Lore «Factory New» tenía 62 ofertas activas en CSFloat; el precio más bajo que se pide $10,623.95. En el propio mercado de Steam no se puede fijar un precio de venta superior a aproximadamente $1,800. Para vender al precio más alto observado, el propietario necesita un comprador o un mercado ajeno a Steam. El artículo y su transferencia siguen dependiendo de Steam.\n\nWhat this means — the Community Market listing ceiling\n\nSteam’s own market refuses a listing above roughly $1,800. A seller may ask less, never more. Items whose market price sits above that line therefore cannot be sold at that price on Steam at all — which is the mechanism that moves those sales to third-party venues while the item itself never leaves Valve’s inventory system.\n\nSection 13 — the off-Steam price gap →\n\nContexto y límites de la fuente\n\nEn esta sección aparecen tres conceptos distintos que no son intercambiables. 245 es el número de categorías de nombres de artículos de CS2 cuya oferta activa más barata superó el valor $1,800 únicamente en CSFloat, el 20 de septiembre de 2026. 241 es ese mismo conjunto menos las cuatro categorías fijadas en el límite superior $100,000 de CSFloat, que es el panel sobre el que se calcula el límite inferior $13.63M. 248 Se trata de una visión general diferente: categorías cuyo precio superaba el límite máximo en dos o más de los cinco mercados el 23 de septiembre de 2026. Los mercados se solapan, por lo que nunca deben sumarse las cifras de las distintas plataformas. Todas las cifras aquí indicadas son precios de venta, no ventas realizadas, y ninguna de ellas corresponde a ingresos, volumen de negocio o beneficio —ni para Valve ni para nadie más—. Los valores que figuran en PriceEmpire son estimaciones redondeadas publicadas por dicho sitio web, y su carta Steam incluye artículos de otros Steam juegos, por lo que los ámbitos de la comparación no son idénticos.\n\nUn artículo. Dos sistemas de precios.SIGUE EL REGISTRO\nPaso 3 / 3\n\nEn ese caso, el vendedor necesita un canal alternativo o un comprador. El artículo sigue dependiendo del inventario y del sistema de transferencia de Steam.\n\nSTEAMAcerca de $1,800Límite máximo de anuncios publicados en el mercado comunitario\nCATÁLOGO GUARDADO$10,623.95AWP Dragon Lore, nueva de fábrica, precio a consultar\nLA DEPENDENCIASigue siendo un artículo SteamEl inventario y la transferencia siguen en Steam\n01 / ARTÍCULOValve inventario del juegoObjeto de CS2 o Dota 2 guardado en Steam\n02 / TECHOAcerca de $1,800 en SteamPrecio máximo por un anuncio en el mercado\n03 / PREGUNTAS EXTERNAS$10,623.95 para «Dragon Lore»La oferta más barata de CSFloat en la instantánea de esa fecha\n04 / ENTREGASteam permanece en la cadenaLa titularidad y la transferencia de artículos dependen de su sistema\nARQUITECTURA DEL MERCADO · INSTANTÁNEA DE FECHA, 20 SEPTIEMBRE 2026\nLa diferencia de precios es cuantificable.\n\nHemos contabilizado las categorías de nombres de artículos cuya oferta activa más barata se situaba estrictamente por encima de $1,800. CSFloat y Skinport son instantáneas independientes con inventarios de CS2 que se solapan; sus recuentos no se pueden sumar. Las ofertas externas muestran dónde se publican precios de venta más elevados, mientras que Steam sigue controlando la propiedad y la transferencia de los artículos.\n\n245CATEGORÍAS DE CS2 · CSFLOAT\n166CATEGORÍAS DE CS2 · SKINPORT\n3DOTA2CATEGORÍAS · SKINPORT\n$10,623.95PREGUNTAS SOBRE EL PISO DE DRAGON LORE\n\nDragon Lore: 62 ofrece CSFloat en la categoría «Factory New»; el precio mínimo mostrado es una petición, no una venta confirmada. Steam permite publicar el artículo por un precio inferior, pero no permite publicar el precio de venta más alto observado. La declaración de Valve en 2016 confirma que es consciente de que hay operadores de juegos de azar que utilizan OpenID y la infraestructura comercial de Steam. La cuestión de si un mercado de terceros concreto incumple las normas de Valve debe determinarse por separado.\n\nConsultar el registro completo →CSFloat JSON ↗Skinport JSON ↗Declaración de Valve sobre «2016» ↗\nAPI DIRECTA DE CSFLOAT / INSTANTÁNEA CON FECHA$13.63M\n\nValor mínimo total de venta en 241 categorías de artículos y 3,395 ofertas activas. Se calcula multiplicando el precio de venta más barato de cada categoría por el número de ofertas correspondientes. Se excluyen de este panel conservador las cuatro categorías fijadas en el límite máximo de $100,000 de CSFloat.\n\nLo que refleja la cifra en dólares\n\nEstas ofertas representan, como mínimo, $13,631,888.25 en los precios de venta anunciados para este subconjunto limitado de CSFloat. Si se incluyen las cuatro categorías con precio máximo, el resultado es $14,231,888.25. Esto es un límite mínimo para las órdenes de compra activas, y no las ventas realizadas, el volumen de caja, los beneficios ni el mercado CS2 en su conjunto.\n\nVolver a calcular a partir de la instantánea de CSFloat de 245 filas ↗\nPRICEEMPIRE / VALOR DE CATÁLOGOSteam: n.º 15 de 39\nMuchos locales indican un valor en dólares superior a Steam.\nUUSkins\n$133.8M\nYouPin898\n$127.5M\nBuff.163\n$104M\nMoon.Market\n$100.3M\nWhite.Market\n$89.6M\nBuff.Market\n$86.7M\nSteam\n$31M\n\nLos seis valores más altos mostrados y Steam. PriceEmpire redondea estas cifras; Steam muestra $31M. Catorce recintos de la lista lo superan según los valores en dólares que se muestran.\n\nPRICEEMPIRE / NÚMERO DE OFERTASSteam: n.º 1 de 39\nSteam sigue a la cabeza en cuanto al número de ofertas.\nSteam\n32,2 millones\nYouPin898\n5,9 millones\nC5Game\n4,6 millones\nHaloSkins\n4,4 millones\nSkinport\n3,8 millones\n\nSteam muestra 32,2 millones Ofertas. El número de ofertas y el valor total de venta responden a cuestiones diferentes; es posible que haya muchas propiedades a la venta a bajo precio que dominen el recuento.\n\nFuente: Comparativa pública de PriceEmpire ↗ archivado 2026-09-21 ↗, capturado el 2026-09-20 a las 19:03 UTC; extracción de 39 filas con fecha ↗. Las cifras son estimaciones aproximadas y el inventario puede solaparse entre las distintas sedes. La ficha de Steam también describe objetos de otros juegos de Steam, por lo que los ámbitos no son idénticos. Los valores indicados corresponden a los precios de venta, no a las ventas ni a los ingresos.\n42\nOTRA FUENTE / STEAMANALYST\nEl ecosistema comercial está a la vista de todos.\n\nDirectorio de tiendas de SteamAnalyst archivado 2026-07-19 ↗ Enumera 42 plataformas de venta de CS2 de terceros, además de Steam, con datos recientes sobre los precios de 32 de las 43 entradas. PriceEmpire recoge 39 plataformas de venta según sus propios criterios de inclusión. Empresas identificadas, ofertas públicas, precios visibles: esta economía está abierta a la inspección.\n\nEL LÍMITE ES EL MECANISMO: LA OFERTA PIERDE IMPULSO, PERO EL ARTÍCULO NO.\n\nEn cinco mercados recogidos en una instantánea autorizada, Las 248 categorías de artículos de CS2 tienen un precio fijado de forma independiente que supera en dos o más unidades el límite máximo de cotización de Steam, que es de aproximadamente $1,800, y ninguna de ellas aparece en Steam. Esa misma instantánea agrupaba todo el catálogo por precios: el mercado de Valve ofrece 95.3% de las categorías de artículos por debajo de su límite máximo y 1.9% de las que están por encima. La caída no se debe a una disminución de la demanda, sino que se ajusta exactamente a la norma publicada. Vender a esos precios requiere un comprador externo o un mercado, mientras que Steam sigue controlando el inventario y la transferencia: la transacción sale de la caja de Valve y la entrega se realiza a través de la infraestructura de Valve.\n\nSteam Preguntas frecuentes sobre el mercado ↗archivado 2026-09-21 ↗Steam Contrato de suscripción ↗archivado 2026-09-21 ↗Conjunto de datos del atlas de cinco mercados ↗Manifiesto de procedencia ↗Instantánea anterior de CSFloat ↗Resumen de Skinport ↗PriceEmpire ↗archivado 2026-09-21 ↗SteamAnalyst ↗archivado 2026-07-19 ↗Registro de diferencias de precios ↗Atlas de la escala de precios ↗\n\nParte C — Marcos jurídicos\nParte C — Marcos jurídicos · Sección 14 · Acceso del personal\n¿Quién puede restablecer las medidas de seguridad?\nContexto y límites de la fuente\n\nLa seguridad de una cuenta también depende de las personas que pueden recuperarla, consultar sus datos privados o restablecer sus medidas de seguridad. La investigación debe supervisar esas acciones privilegiadas con el mismo rigor con el que supervisa el uso indebido de las API.\n\nLa recuperación de cuentas otorga a un agente de atención al cliente la facultad de retirar la cuenta a su titular. Valve ha confirmado por escrito, en dos ocasiones —en febrero de 2023 y en noviembre de 2025— que esta facultad se utilizó para ceder cuentas a personas equivocadas. Con treinta y tres meses de diferencia, a través del mismo canal. A continuación: lo que vale ese acceso, seis casos documentados y el registro Valve que se aplica a cada uno de ellos y que no se ha facilitado a nadie.\n\nTestimonio conservado / 9 de mayo de 2025\nUn ticket de recuperación que desactivó la seguridad de la cuenta y una pérdida declarada de $10,000\n\nUn usuario del archivo de asistencia recopilado informa de que Steam el servicio de asistencia restableció la contraseña y desactivó la protección de la cuenta después de que otra persona enviara una solicitud de recuperación. El autor afirma que la cuenta llevaba años inactiva, contenía elementos desde 2016-2017 y tenía Steam Guard, un teléfono vinculado y códigos de recuperación almacenados.\n\n«Steam El servicio de asistencia le ha dado acceso a mi cuenta a otra persona».\n\nDeclaración en primera persona, conservada en steam_support_tickets_MEGA.json, registro n.º 110. Lee la publicación completa capturada ↗\n\nNo se trata de la mala suerte de un solo usuario. Esa misma vía —una solicitud de ayuda que transfiere la cuenta a quien facilite los datos más antiguos— es el procedimiento documentado para todos los casos que figuran en el registro que se muestra a continuación, y Valve lo ha dejado por escrito en dos ocasiones.\n\nEl propietario no puede ganar esa discusión. La recuperación solicita la primera clave de CD, el primer correo electrónico, la primera tarjeta y el primer número de teléfono. Esos datos se encuentran en la base de datos de Valve, y el servicio de asistencia técnica los consulta —según se informa, se remontan hasta quince años atrás—. Una persona que tenga una copia de tu expediente siempre podrá proporcionar más datos de tu historial de los que tú mismo puedas aportar. Los objetivos se seleccionaban para que encajaran en el perfil: inactivos durante años, de gran valor y, a menudo, comprados de segunda mano, de modo que el titular nunca conociera la clave original. Posteriormente, las cuentas se eliminaban por completo, rompiendo así el rastro del historial de artículos que la comunidad utiliza para rastrear un skin —una eliminación que un usuario normal no puede realizar sin el periodo de espera estándar.\n\nPrivilegio mínimo / OWASP A01\n\nLos privilegios de recuperación deben limitarse a la tarea en cuestión, someterse a una revisión independiente y registrarse. Se debe auditar quién puede restablecer credenciales, eliminar Steam Guard, consultar registros de facturación o exportar datos de cuentas. Directrices de OWASP sobre el control de acceso ↗ archivado 2026-09-20 ↗\n\nAmplio acceso a la asistencia técnicaRiesgo relacionado con el ámbito de acceso\nMás allá del inventario.\n\nSi se abusa del acceso general, la telemetría privada puede convertirse en una herramienta para la elaboración de perfiles, el phishing dirigido y la vigilancia. Entre las posibles víctimas se encuentran los usuarios comunes, el personal militar, las figuras públicas y sus familias. Se trata de un modelo de amenaza; los permisos exactos requieren registros de control de acceso.\n\n01 Historial y ubicación de la IP\nLos registros de IP pueden revelar el historial de navegación y la ubicación aproximada. Por sí solos, no permiten determinar con precisión los desplazamientos físicos.\n02 Identificación de dispositivos\nLos identificadores de dispositivos, cuando se recopilan y son accesibles, permiten vincular sesiones y cuentas.\n03 Telemetría de actividad\nLas marcas de tiempo de inicio de sesión y los registros de sesión pueden revelar hábitos, incluida la actividad que no se ve en un perfil público.\n04 Comunicaciones y contactos\nEl acceso a los mensajes almacenados o a la información de contacto aumentaría las posibilidades de elaboración de perfiles y de ingeniería social.\n05 Desenmascaramiento de la identidad\nLos registros originales de correo electrónico, teléfono y pagos pueden vincular una cuenta seudónima a una persona.\n06 Reventa de datos y responsabilidad\nLas listas de destinatarios exportadas podrían servir para cometer estafas selectivas. Identifica al autor, la ubicación de acceso, los destinatarios y las transferencias; la ubicación por sí sola no determina ni el acceso ni la inmunidad jurídica.\n\nValve describe el registro de direcciones IP, la información de los dispositivos, los registros de pago y los proveedores de asistencia externos en su Política de privacidad, apartados 3 y 5.2 archivado 2026-09-21 ↗. La política autoriza el acceso de terceros para prestar apoyo; sin embargo, no se ha revelado el registro de auditoría que indicaría qué contratista accedió a qué categoría, cuándo y con qué autorización.\n\nSección 14.1 · el registro · junio de 2022 → noviembre de 2025 · todas las cifras tienen su fuente\nValve abrió la puerta dos veces, con treinta y tres meses de diferencia. Nunca se cerró.\n\nSe han registrado seis casos en los que se sustrajeron cuentas a través del propio canal de solicitud de ayuda de Steam, o mediante las credenciales que protege dicho canal. Cada importe corresponde a la cifra publicada por la fuente citada, y se indica el nombre de cada fuente. Dos de los seis casos se han resuelto con la recuperación íntegra de los fondos. La diferencia entre estos casos y el resto no radicaba en lo que ocurrió, sino en quién estaba al tanto de ello.\n\nValve, por escrito — febrero de 2023«Los artículos en cuestión se han eliminado de tu cuenta porque procedían de una cuenta que fue vulnerada a través de una solicitud de asistencia, responsabilidad de la que se hace cargo el equipo de CS:GO. Hemos anulado los intercambios y los hemos eliminado de todas las cuentas que los recibieron».Steam Respuesta de asistencia a un destinatario de los artículos de HFB, reproducida por Dexerto, 21 de febrero de 2023 ↗ archivado 2025-08-18 ↗\nValve, de nuevo por escrito — noviembre de 2025 · 33 meses después«Un técnico de asistencia que se encargó de la solicitud de ayuda no siguió nuestro procedimiento, lo que provocó que tu cuenta se restableciera a nombre de otra persona. Te pido disculpas por este error».Steam Respuesta del servicio de asistencia a Hawkeye337, citada en Dexerto, 14 de noviembre de 2025 ↗\n21 de junio de 2022\nHFB: el mayor surtido del juego$2,000,000+ · se elevó a $3,000,000+ en el seguimiento de febrero de 2023\n\nSiete «Dragon Lores» de AWP de recuerdo y el karambit «Blue Gem» n.º 1, cuyo valor solo ese cuchillo asciende a unos $1.26 millones. La cuenta llevaba tres años inactiva, aunque la aplicación de autenticación móvil seguía activa; aun así, se cambiaron el correo electrónico y la contraseña a través del proceso de recuperación del servicio de asistencia.\n\nEl dinero se acabó antes que los artículos. Según se ha informado, $200,000+ Parte de los ingresos de la venta ya se había retirado a través de market.csgo.com, un mercado en el que las transacciones se liquidan en efectivo y criptomonedas. Al anular una transacción, se recupera el skin, pero no el dinero que ya se haya ingresado en la cuenta.\n\nY la solución dejó de funcionar. Un comprador trasladó su «Souvenir Dragon Lore» a una unidad de almacenamiento del juego. El script de reversión de Valve no podía ver el interior de su propio contenedor, por lo que le proporcionó al propietario una copia nueva y dejó la oculta tal cual — Valve duplicó un $130,000 artículo al intentar revertir un robo. Se detectó gracias a la comparación de los identificadores de los artículos y a las denuncias de la comunidad, y se eliminó un mes después, en julio de 2022. BUFF reembolsó al comprador, no Valve. Una solución de emergencia tan precaria como esta no es un control; es lo que hace una plataforma cuando carece de control.\n\nDexerto, 21 de junio de 2022 ↗ archivado 2022-07-02 ↗ · Kaspersky ↗ · importe del retiro por Esportfire, 22 de junio de 2022 ↗ archivado 2026-05-15 ↗, atribuido allí a varias fuentes de Twitter · duplicación y eliminación según Esportsbetting, 14 de julio de 2022 ↗\n\nRestauradoSe anularon las transacciones. Se retiraron los artículos de los inventarios de quienes los habían pagado a precio completo.\n14 de agosto de 2022\nCS.Money: los bots propios de la plataforma$6,300,000 · 19,000+ skins · primera estimación $1.6M\n\nLos atacantes se hicieron con los archivos del autenticador móvil de los bots de negociación de la plataforma y los vaciaron; a continuación, enviaron parte del botín a operadores conocidos para despistar. Los investigadores de la comunidad identificaron 55 cuentas de atacantes en cuestión de horas y los publicó.\n\nValve no modificó nada. La razón aducida fue que un sitio web de terceros se encuentra fuera de Steam —el mismo Steam en cuyo inventario, API comercial y sistema de cuentas se llevó a cabo el robo de principio a fin—.\n\nEsportfire, 14 de agosto de 2022 ↗ archivado 2025-11-15 ↗\n\nRechazadoNo hubo reversión. La pérdida recayó sobre la plataforma y sus usuarios.\nNotificado\n21 de febrero de 2023\nQkss — la misma puerta, el mismo actor$1,000,000+\n\nSegún se ha informado, se tramitó de la misma forma que el HFB, por parte del mismo actor y a través de la misma solicitud de asistencia técnica. El HFB se resolvió por completo ocho meses antes. El Qkss no.\n\nUn camino. Dos respuestas. No hay nada en el expediente publicado que distinga ambos casos, salvo el número de asistentes.\n\nDexerto, 21 de febrero de 2023 ↗ archivado 2025-08-18 ↗\n\nRechazadoNo se ha restaurado.\nNotificado\nFebrero de 2023\nEl uso de información privilegiada en sí mismo: un año de ello≈ $320,000 · se refiere a un periodo de aproximadamente un año, no a una valoración de existencias\n\nEl acceso desde el servicio de asistencia permitió consultar el historial de la cuenta hasta 15 años — la primera clave de CD, el primer correo electrónico, la primera tarjeta. Esas son, precisamente, las pruebas que exige el proceso de recuperación, y por eso quien tiene la base de datos siempre sale ganando en la discusión frente a quien tiene la cuenta.\n\nEl bloguero Mzkshow reveló cómo el operador interno «Steam Help» y su colaborador «Alexander» se centraron en cuentas inactivas que contenían más de $100k en skins. Un M4A4 Howl robado, con los hologramas de iBUYPOWER y Titan Katowice 2014, se vendió por $35,000 y acabó recayendo en Valerii «b1t» Vakhovskyi, de NAVI, quien no tenía forma de saberlo. Tras la intervención de Valve, la empresa contratista despidió a todo el personal del servicio de asistencia técnica Steam.\n\nVKPlay ↗ · Lis-Skins ↗ · Escorenews (RU) ↗ · Dexerto (EN) ↗\n\nSin registroValve nunca ha revelado a cuántas cuentas afectó esto, ni se lo ha comunicado a las personas afectadas.\nNotificado\n2 de diciembre de 2024\n«Matvey» — tras los despidos$13,000\n\nSe concedió la recuperación a una persona que facilitó datos de la cuenta que ni el propio titular pudo corroborar. Dos años después de que la empresa contratista desmantelara su servicio de asistencia Steam, seguir el mismo procedimiento dio el mismo resultado.\n\nPublicación archivada, 2 de diciembre de 2024 ↗ archivado 2025-08-05 ↗ · filas de origen y hash ↓\n\nRechazadoNo se ha restaurado.\n13 de noviembre de 2025\nHawkeye337 (Mark Spurlock) — y la segunda confesión≈ $300,000–$500,000 · Colección completa de hologramas de Katowice 2014\n\nEl agresor exigió 1 bitcoin y empezaron a transferir la colección a cuentas de Negev para destruirla. Steam La respuesta por escrito del servicio de asistencia es la segunda admisión mencionada anteriormente: un técnico se encargó de la solicitud de ayuda, no siguió el procedimiento y cedió la cuenta a otra persona.\n\nLo que provocó el fallo fue la señal. Pocas horas después de que se publicaran en X las entradas en las que se etiquetaba a Valve, se recuperó la cuenta y se restablecieron todas las pegatinas. Qkss no contaba con esa audiencia.\n\nSkin.club ↗ · Dexerto ↗ · Esportfire ↗ archivado 2025-12-17 ↗\n\nRestauradoLa noticia se desmintió a las pocas horas de que se convirtiera en tendencia.\nLo que refleja el libro mayor y que ningún caso concreto muestra por sí solo.\n\nLa ruta nunca se cerró. La primera admisión data de febrero de 2023 y la segunda, de noviembre de 2025 — con treinta y tres meses de diferencia, tras el despido masivo por parte del contratista, un nuevo incidente documentado y una brecha de seguridad en la plataforma de $6.3 millones entre ambos. Contando desde el primer robo registrado en este libro de cuentas, el canal permaneció abierto durante tres años y cinco meses. Independientemente de lo que se corrigiera en 2023, la solicitud de ayuda siguió asignándose a la persona equivocada en noviembre de 2025 — según las propias palabras de Valve.\n\nLa restitución se centraba en la atención, no en el daño. Restablecido: el inventario más grande del juego y el coleccionista cuyo hilo se hizo viral. Rechazado: $1,000,000, $6,300,000, $13,000. Valve nunca ha publicado la regla que aplica, ya que una regla publicada tendría que explicar esas tres.\n\nNo se lo dijeron a nadie. Ni los usuarios cuyos historiales de cuenta fueron extraídos de la base de datos, ni una autoridad supervisora, ni el mercado que compró los artículos de buena fe y se los tuvieron que recuperar. No hay ningún aviso de violación de seguridad, ningún informe de incidente, ningún recuento de las cuentas afectadas — y los ingresos que quedan en forma de dinero, a través de plataformas que pagan en efectivo y en criptomonedas. Una reversión de la operación no puede seguir el dinero que sale de Steam.\n\nValve contiene el registro de auditoría de asistencia, el registro de tickets de recuperación y el registro de transacciones de cada una de las líneas anteriores. No se ha presentado ninguno de ellos. Solicita tu propio ejemplar →\n\nLa cuestión del NDA\nLa confidencialidad debe ir acompañada de la responsabilidad técnica.\n\nCompara los acuerdos de confidencialidad con los permisos reales, los controles de exportación, las autorizaciones de restablecimiento y los registros de acceso. Una respuesta predefinida no puede resolver una acusación de que se haya abusado del propio proceso de recuperación.\n\nArtículos 28 y 32 a 34 del RGPD\n\nEl artículo 33 concede al responsable del tratamiento un plazo de 72 horas para notificar a la autoridad de control una violación de la seguridad de los datos personales; el artículo 34 exige informar a las personas afectadas cuando el riesgo para ellas sea elevado. Valve ha confirmado por escrito, en dos ocasiones, que su canal de asistencia entregó cuentas a personas equivocadas —incluidos el historial de la cuenta, los registros de facturación y todo lo demás—. No se ha publicado ninguna notificación en virtud de ninguno de los dos artículos, y ningún usuario afectado ha informado de haber recibido ninguna. Lee el reglamento ↗ archivado 2026-09-20 ↗\n\nIncluye el acceso al servicio de asistencia en tu solicitud →\nParte C — Marcos jurídicos · Sección 15 · A escala comercial\nSigue el rastro del dinero. Separa las transacciones.\nContexto y límites de la fuente\n\nLa cuestión del uso comercial se agudiza cuando se separan los flujos de dinero. Las transferencias de artículos a terceros, las ventas principales de Valve y las retiradas de efectivo externas son transacciones diferentes.\n\nEl artículo es de Valve. El stock es de Valve. La transferencia se realiza en los servidores de Valve. Lo único es que el pago se realiza en otro sitio — que es el paso que determina si alguien es un operador de transferencia de fondos, y el único paso Valve que no lleva a cabo.\n\nEl mecanismo de ingresos\nDonde realmente circula el dinero.\nTres caminos / una economía de un solo artículo\n01 / CuentaInventario de usuarios\n\nArtículos en reserva: Steam\n\n02 / TraspasoComercio entre particulares\n\nUsuario ↔ bot o usuario ↔ usuario\n\n03 / LiquidaciónPlataforma externa\n\nSaldo de la obra o pago de Steam\n\nCirculaciónEl motor económico va más allá del coste de traspaso\n\nSteam proporciona la infraestructura de inventario y transferencia que utilizan los mercados externos. El argumento económico de la investigación es que la liquidez de la reventa y la demanda recurrente sostienen el gasto en estuches, llaves y artículos de recambio, con comisiones sobre las ventas posteriores en el Mercado Comunitario. Una transferencia directa entre particulares (P2P) no conlleva comisión del Mercado Comunitario; ese dato contable no resuelve la cuestión del beneficio general. Valve mantiene el control sobre el acceso a las cuentas y las restricciones de negociación en todo momento.\n\n01 / Demanda secundariaLiquidez y valor de reventa\n\nDemanda externa relacionada con el comercio y los juegos de azar\n\n02 / Gasto primarioLlaves, estuches y cápsulas\n\nCompras a partir de Valve, cuando estén disponibles\n\n03 / IngresosIngresos por venta directa\n\nMás comisiones sobre las ventas reales en el mercado\n\n5% + 10%Steam + comisión de CS2 sobre las ventas en el Mercado de la Comunidad\n\nConclusión económica de la investigación: los mercados de reventa de activos líquidos pueden fomentar el gasto en artículos nuevos. El conocido 15% combina las tasas de comisión del mercado, sujetas a mínimos y redondeos; no se trata de un gravamen que se aplique a todas las transacciones con el exterior.\n\nLista de tarifas del Community Market de Valve ↗ archivado 2026-09-21 ↗. El 25 de febrero de 2026 El fiscal general de Nueva York interpuso una demanda archivado 2026-09-01 ↗ en la que se alega que las cajas de botín de pago están relacionadas con la reventa externa por dinero en efectivo y los daños derivados del juego —la misma relación que este informe documenta desde el punto de vista de la infraestructura técnica—. Esa denuncia es una alegación, no una conclusión; se cita aquí porque un organismo estatal encargado de hacer cumplir la ley ha planteado una cuestión relacionada con la que plantea este informe: ¿dónde está el historial de aplicación de la ley que se corresponda con las declaraciones públicas?\n\n01 / EntradaIngreso en criptomonedas\n\nRegistros de servicios externos y monederos\n\n02 / ConversiónEquilibrio → aspectos\n\nArtículos entregados a través de Steam transacciones\n\n03 / SalidaVenta externa de moneda fiduciaria\n\nVendedor, comprador y proveedor de pagos\n\n¿KYC?Identificar el control en cada traspaso\n\nEsta es la vía que hay que investigar, no un servicio de conversión de efectivo mediante la API nativa Steam. Documenta las comprobaciones de identidad, la custodia, los identificadores de transacción y los destinatarios de los pagos en cada operador externo antes de afirmar que se trata de un retiro de efectivo sin KYC.\n\nEstados Unidos / Ley de Secreto Bancario\nClasifica primero la actividad y, a continuación, la obligación.\n\nLa FinCEN evalúa la transmisión de fondos en función de la actividad que realiza una empresa. Aceptar y transferir moneda virtual convertible puede dar lugar a obligaciones en materia de servicios monetarios, con sujeción a las definiciones y excepciones aplicables. La cartera Steam de Valve acepta fondos y los convierte en artículos del juego; a continuación, dichos artículos se liquidan a través de operadores externos a cambio de moneda real. El objeto y su transferencia se gestionan en la infraestructura de Valve; el cobro en efectivo no, y el hecho de que alguna parte de ese ciclo se ajuste a las definiciones de transferencia de fondos es una cuestión de clasificación que corresponde a la FinCEN, no una conclusión que se extraiga aquí.\n\nFinCEN FIN-2019-G001, §§ 1–2, 5.1 ↗ archivado 2025-07-11 ↗\n\nUnión Europea / blanqueo de capitales\nRealizar un seguimiento de los ingresos, la información y la asistencia.\n\nLa Directiva (UE) 2018/1673 regula el blanqueo intencional y la participación en actividades relacionadas con productos del delito. La cuestión que se plantea en la investigación es qué sabía Valve sobre los operadores que utilizaban su infraestructura de negociación y OpenID después del 13 de julio de 2016, cuando describió públicamente dicho uso, y qué medidas tomó al respecto. Valve no ha publicado ningún registro de medidas coercitivas por operador; ese registro, y no este expediente, respondería a la pregunta.\n\nMarco penal de la UE ↗\n\nTerminología de la AMLD6: La directiva en materia de derecho penal mencionada anteriormente es distinta de la Directiva (UE) 2024/1640, también conocida como AMLD6. Esta última tiene un plazo general de transposición que vence el 10 de julio de 2027, con algunas excepciones específicas. Artículo 78 ↗ archivado 2026-08-30 ↗\n\nParte C — Marcos jurídicos · Artículo 16 · Notificación, respuesta, responsabilidad\nLa Ley de Servicios Digitales: dejar constancia de los conocimientos\nContexto y límites de la fuente\n\nHay dos elementos de una notificación conforme al artículo 16 que corresponden al remitente y no a este expediente: los datos del propio remitente y una declaración de buena fe de que la información es exacta. Todo lo demás que exige el artículo —la explicación fundamentada y la ubicación electrónica exacta— se recoge en la sección 3 y en el registro de rutas, junto con las respuestas guardadas y los hash, de modo que cualquier parte pueda presentarla. Hay otras dos limitaciones en la propia ley: la pérdida de la exención de responsabilidad del proveedor de alojamiento no implica por sí misma responsabilidad alguna en virtud de ninguna otra ley, y el 6% del artículo 52, apartado 3, es un límite máximo legal, no una sanción impuesta contra Valve.\n\nEn virtud de la DSA, un proveedor de servicios de alojamiento solo goza de exención de responsabilidad hasta el momento en que tenga conocimiento concreto de los hechos y no actúe en consecuencia. Este expediente constituye dicha notificación. En él se indican los servidores, las fechas, las respuestas guardadas y los hash. Desde su publicación, la cuestión ya no es si Valve lo sabía, sino qué hizo Valve a continuación.\n\n01Julio de 2016 / la exposición «The Dossier»\nUn plazo de diez días.\n\nLa notificación reconstruida anteriormente constituye el punto de partida histórico para la comparación de las medidas de ejecución de la investigación.\n\n0217 de febrero de 2024 / solicitud general\nLa ventana temporal del DSA.\n\nDistingue entre la conducta histórica y la conducta durante el período en el que se aplican las obligaciones pertinentes de la DSA.\n\n03Diez años / instantánea del expediente original\nLa duración requiere un historial de notificaciones.\n\nEl tiempo transcurrido desde julio de 2016 (véase la sección 11) es un indicador del expediente. No se trata de diez años de infracciones constatadas de la DSA. Vincula cada notificación a un elemento concreto, a la legislación aplicable, a las pruebas de entrega y a la respuesta correspondiente.\n\nArtículo 52, apartado 3 / límite máximo legal6%\nde la facturación anual a nivel mundial\n\nMulta máxima por incumplimiento de las obligaciones derivadas de la DSA, calculada sobre la base del ejercicio financiero anterior del proveedor. Se trata de un límite máximo legal, no de una sanción impuesta a Valve.\n\nArtículos 6, 8 y 16 / el criterio jurídico\n\nEn el caso de los servicios de alojamiento web pertinentes, el conocimiento específico y la falta de actuación con la debida diligencia pueden dar lugar a la pérdida de la exención de responsabilidad por alojamiento. Una notificación suficientemente precisa puede demostrar el conocimiento del contenido concreto. La DSA no impone ninguna obligación general de supervisión; la pérdida de la exención no implica por sí misma la responsabilidad en virtud de otra ley.\n\nDSA: artículos 6, 8, 16, 52, 53 y 93, y considerando 17 ↗ archivado 2026-09-20 ↗\n\nRevisar las reclamaciones archivadas ↗Crear la cronología de la cuenta →Análisis jurídico y económico completo →\nParte C — Marcos jurídicos · Sección 17 · Identidad, edad y acceso comercial\nMenores de edad: un inicio de sesión con «Steam» no constituye una verificación de edad\nContexto y límites de la fuente\n\nEn este expediente no aparece ningún dato de menores en ninguna parte y no se recopiló ninguno: los autores no se registraron, no depositaron información ni iniciaron sesión en ninguna de las plataformas mencionadas. Cualquiera que se base en esta sección debe mantener la confidencialidad de las pruebas relacionadas con menores y ocultar los datos identificativos en los documentos públicos. La COPPA se cita aquí como una ley de protección de la privacidad de los menores con sus propias condiciones de aplicación —público destinatario, conocimiento efectivo, datos personales recopilados— y no como una norma general sobre la edad mínima para apostar; la denuncia presentada en Nueva York en 2026 es una alegación de una autoridad estatal, no una resolución judicial.\n\n«Iniciar sesión con Steam» demuestra que existe una cuenta. Eso no demuestra nada sobre la edad — y en estas páginas es la única barrera entre un niño y un depósito. Léelo con Apartado 3.1: dentro del cliente Steam, la advertencia que mostraría un navegador nunca se activa, por lo que el niño nunca la ve.\n\n¿Qué ofrece OpenID?Identidad de la cuenta\n\nUn SteamID verificado que se utiliza para iniciar sesión o vincular una cuenta.\n\n≠\nLo que debe determinar el operadorRequisitos para participar\n\nEdad, jurisdicción y cualquier verificación de identidad necesaria.\n\nFundamento técnico: Documentación de Steamworks OpenID ↗ archivado 2026-09-21 ↗. La verificación de identidad documentada no constituye una certificación de que el usuario pueda apostar legalmente.\n\nCOPPA / menores de 13 años\nIdentifica el operador y los datos.\n\nLa COPPA se aplica a los servicios dirigidos a menores que entran en su ámbito de aplicación y a aquellos que tienen conocimiento efectivo de que recogen datos personales de menores de 13 años. Se trata de una ley sobre la privacidad de los menores, no de una norma universal sobre la edad mínima para participar en juegos de azar. Se debe determinar el público destinatario, los datos personales que se recogen, el conocimiento de dichos datos y el proceso de consentimiento parental.\n\nFTC: Requisitos de la COPPA ↗ archivado 2026-09-21 ↗\n\nLas pruebas que hay que conservar\nRegistra el proceso desde el inicio de sesión hasta el ingreso.\n\nMantén el control de edad del sitio web, el texto del registro, las condiciones de acceso, el proceso de pago y el historial de reclamaciones. Evalúa a cada operador por separado. Mantén la confidencialidad de cualquier prueba relacionada con un menor y oculta los datos identificativos en los documentos públicos.\n\nUn registro relacionado con la aplicación de la ley es el Anuncio de la demanda de Nueva York de 2026 archivado 2026-09-01 ↗, en la que se alega que las cajas de botín de pago causan perjuicios a los usuarios jóvenes. No se trata de una conclusión de la COPPA.\n\nParte C — Marcos jurídicos · Sección 18 · Solicitud en virtud del artículo 15 del RGPD\nLa solicitud. La respuesta. La comparación que falta.\n\nPidió cuatro cosas, una de ellas el registro que revelaría quién había introducido una clave API en su cuenta. Tres días después, el ticket se cerró con un enlace a una página en la que no aparece ninguno de ellos. — y la frase con la que se concluye la contradicen los propios abogados de Valve.\n\nDe quién es esta cuenta · Procedencia y límites\n\nEstas capturas de pantalla no son de PhishDestroy. Provienen de un titular de una cuenta Steam cualquiera —uno de los participantes en una breve encuesta realizada por este proyecto—, que presentó la solicitud él mismo y facilitó las capturas de pantalla. La cuenta es suya, el ticket es suyo y la correspondencia es entre él y el servicio de atención al cliente Steam. Este proyecto no presentó la solicitud, no tiene ninguna cuenta en la plataforma y no es parte en este ticket.\n\nEl 16 de septiembre de 2026 presentó una solicitud de acceso de datos del interesado, en virtud del artículo 15 del RGPD y la CCPA, en la que solicitaba específicamente los registros de registro de claves API, el historial de inicio de sesión con direcciones IP, el historial de autorización de dispositivos y el historial de operaciones. El 17 de septiembre, el agente «Logen» le remitió a la página de autoservicio «Datos de la cuenta». El 18 de septiembre, declaró que las categorías solicitadas no figuraban en dicha página y pidió que se remitiera el asunto al equipo de privacidad o al delegado de protección de datos (DPO). El 19 de septiembre, el agente «Kal» cerró el ticket con la misma remisión. A continuación se conservan ambas capturas de pantalla (se ha ocultado el correo electrónico del solicitante; SHA-256 en steam_tos_assets/screenshot-manifest.json).\n\nEs el solicitante ideal por una razón muy sencilla: Su cuenta tiene una clave de API web Steam que él no ha creado, registrada a nombre de localhost. Se desconoce cuándo se creó — ni a él, ni a partir de nada que Valve haya puesto a su disposición, ya que el único registro que permitiría datarlo es el registro de inscripción de la clave API, que es precisamente la categoría que el cierre ocultó. La clave no es nueva: es anterior a que él tuviera conocimiento de ella en un intervalo que no puede cuantificar, por la misma razón.\n\nOtros titulares de cuentas están presentando la misma solicitud. Cualquier respuesta que se reciba se añadirá aquí en las mismas condiciones que estas dos —número de ticket, fecha de captura, SHA-256, identidad del solicitante ocultada—, tanto si acepta las categorías como si las rechaza.\n\nEste proyecto no se pronuncia sobre los motivos por los que se cerró el ticket. En él no se indicaba ningún motivo, y aquí tampoco se deduce ninguno.\n\nLa solicitud. La respuesta. La comparación.SIGUE EL REGISTRO\nPaso 3 / 3\n\nPidió cuatro categorías concretas. La página de «Datos de la cuenta» a la que se le remitió es la propia función de exportación de autoservicio de Valve, y este proyecto no puede detallar su contenido para la cuenta de otra persona; por lo tanto, aquí no se publica ninguna comparación completa categoría por categoría. Lo que consta en el expediente es su declaración del 18 de septiembre en la que afirmaba que las categorías no estaban ahí, y el cierre del 19 de septiembre, en el que se repetía la remisión sin abordar el tema.\n\nLA SOLICITUDCategorías específicasRegistros de claves API, inicio de sesión, dispositivos y operaciones\nLA RESPUESTAReferencia de datos de la cuentaRevisa el intercambio de soporte\nLA PRUEBA¿Qué se suministró?Compara cada categoría solicitada\nPantalla 1/2 — Solicitud (16 de septiembre) y primera respuesta, agente «Logen» (17 de septiembre)\nGDPR ticket HT-2YBP-F7JP-D4VB — request and first response\nFuente: help.steampowered.com, ticket HT-2YBP-F7JP-D4VB · capturado del 16 al 17 de septiembre de 2026 · correo electrónico del solicitante ocultado 2026-09-21 · Archivo: gdpr-ticket-1.png · SHA-256 da940c731ab9869d226e9d06ccc8a1b393738766b7b0c445a56662623e025a66 (captura-de-pantalla-manifest.json).\nPantalla 2/2 — Solicitud de escalado (18 de septiembre) y cierre, agente «Kal» (19 de septiembre)\nGDPR ticket HT-2YBP-F7JP-D4VB — escalation request and closure\nFuente: help.steampowered.com, ticket HT-2YBP-F7JP-D4VB · capturado del 18 al 19 de septiembre de 2026 · Archivo: gdpr-ticket-2.png · SHA-256 44844ea7b251f7fd7d79f87ee1578a846606a97b9659d3a53b322120c422219b (captura-de-pantalla-manifest.json).\nRespuesta final, 19 de septiembre (textual):\n«Los datos Steam que se conservan ya se pueden consultar en la página «Datos de la cuenta». Dado que el servicio de atención al cliente Steam no puede ofrecer más información, Esta solicitud se cerrará.\"\nNo se han facilitado datos · no se ha indicado ningún fundamento jurídico para la denegación · no se muestra el resultado de la escalación\nEsa afirmación es falsa, y los propios abogados de Valve lo demuestran. En el apartado 1.9 de la carta del abogado de 1 de octubre de 2025 se describe una correlación a nivel de dispositivo que vincula un dispositivo con docenas de cuentas (Apéndice A). Esa misma respuesta incluía 830 páginas de documentos conservados (Apéndice B). No aparece nada de eso en la página «Datos de la cuenta».\n¿Por qué esta cuenta solicitó el registro de la clave API?\n\nNo eligió esas cuatro categorías al azar. El localhost La clave de su cuenta es la marca de un script, no de una persona que introduce un dominio real en la página de desarrolladores (Sección 5, Sección 6). El único registro que indica quién lo creó y desde dónde es el registro de registro de claves API. Eso fue lo primero que pidió. Y eso es lo que la empresa se negó a facilitar.\n\nFuente: el titular de la cuenta, durante la encuesta de este proyecto. Las capturas de pantalla de los tickets que aparecen arriba están cifradas; la página clave no se ha publicado.\n\nEvaluación · PhishDestroy\n\nCerrar un ticket sin haber resuelto la cuestión no es algo fortuito en este caso. Es lo habitual. Nos atenemos a 16,319 registros conservados de reclamaciones y asistencia y 354 intercambios de asistencia técnica sin duplicados extraídos de ellos. Este billete es un ejemplo concreto y completo de la forma que adoptan.\n\nTicket de asistencia — ConservadoHT-2YBP-F7JP-D4VB\nTipo de solicitudArtículo 15 del RGPD (Solicitud de acceso a los datos)\nEstado del billeteCERRADO EL 19 DE SEPTIEMBRE DE 2026 — NO SE HAN FACILITADO DATOS\nAgentes de la bolsa«Logen» (17 de septiembre), «Kal» (19 de septiembre)\nArchivado16 de septiembre de 2026\nDatos solicitados¿Quién registró la clave de la API web vinculada a esta cuenta, y desde qué dirección IP, dispositivo y marca de tiempo?\nFundamento jurídico invocadoArtículo 15 del RGPD: derecho de acceso a los datos personales\nEl marco jurídico:El artículo 12, apartado 3, concede al responsable del tratamiento un plazo de un mes a partir de la recepción (prorrogable previa justificación). Dicho plazo no había vencido en el momento de la publicación, y este expediente no alega ningún incumplimiento del plazo. La objeción se refiere al fondo del asunto: la respuesta final incluye un enlace a una página de autoservicio, pero no demuestra que se hayan facilitado las cuatro categorías de datos mencionadas; además, si el responsable del tratamiento se niega a actuar, el artículo 12, apartado 4, le obliga a exponer los motivos y las vías de reclamación. Ninguno de estos elementos figura en la respuesta final.\nPor qué son importantes estos datos concretos\n\nEl registro de eventos de claves de la API web es el registro que muestra si un tercero ha registrado una clave utilizando una cookie de sesión robada — el mecanismo descrito en las denuncias por robo de inventario conservadas en el archivo de este expediente—. Revelar quién registró una clave de API, desde qué dirección IP y en qué momento:\n\nPermitir a la víctima comparar la dirección IP de creación de la API con su propio historial de inicio de sesión\nRevelar las direcciones IP de centros de datos vinculadas a infraestructuras conocidas de phishing o de bots de apuestas\nAportar pruebas que puedan utilizarse en procedimientos civiles o penales contra el autor\nIndica si se notificó al titular de la cuenta cuando se creó la clave\nLo que consta en el expediente: Valve conserva registros a nivel de dispositivo y de correlación de cuentas; la carta de su asesor jurídico, de 1 de octubre de 2025, los describe (véase el Apéndice A, Memorándum de pruebas — Fuente 1). En el ticket HT-2YBP-F7JP-D4VB, el interesado solicitó el mismo tipo de registros y el ticket se cerró remitiéndole a una página de autoservicio que, según informó el interesado, no los contenía. La legalidad de dicha denegación es una cuestión que compete a la autoridad de control; el resultado es que el interesado no recibe los datos.\nEl intercambio: cuatro mensajes, tres días\n\nDos agentes de atención al cliente de Steam respondieron utilizando los nombres de pila que figuraban en el ticket: «Logen» el 17 de septiembre y «Kal» el 19 de septiembre. Ambos remitieron al solicitante a la página de datos de la cuenta. En el ticket no hay nada que indique si la solicitud llegó al equipo de privacidad o al responsable de protección de datos de Valve, y el expediente no especifica quiénes son los agentes, cuáles son sus funciones ni cómo se tramitó el ticket.\n\n16 de septiembre\nSolicitud en virtud del artículo 15 presentada con cuatro categorías de datos especificadas\n17-18 de septiembre\nConsulta sobre los datos de la cuenta; el solicitante pide que se remita el asunto al responsable de protección de datos\n19 de septiembre\nIncidencia cerrada con la misma referencia; sin datos, sin fundamento indicado.\n¿A qué derechos da derecho explícitamente al interesado el artículo 15 del RGPD?\nArt. 15, apartado 1, letra a)Finalidades del tratamiento: por qué Valve conserva los datos\nArt. 15, apartado 1, letra b)Categorías de datos: qué contiene Valve\nArt. 15, apartado 1, letra c)Destinatarios o categorías de destinatarios — quién recibió los datos (p. ej., el titular de la clave API)\nArt. 15, apartado 1, letra d)Plazo de conservación o criterios para determinarlo\nArt. 15, apartado 3Una copia de los datos personales objeto de tratamiento, es decir, el propio registro de claves API\nART. 12, apartado 3Se requiere una respuesta en un plazo de un mes a partir de la fecha de recepción; cualquier prórroga deberá comunicarse en el plazo de ese mes. El plazo aún no había vencido en el momento de la publicación. Art. 12, apartado 4: Si el responsable del tratamiento no toma medidas, deberá explicar los motivos e informar al interesado de las vías de reclamación.\nProcedimiento de reclamación ante las autoridades reguladoras — para cualquier usuario\n\nCualquier usuario que haya presentado una solicitud en virtud del artículo 15 del RGPD a Valve y no haya recibido una respuesta conforme (o una respuesta de denegación con un texto predefinido sin datos) podrá presentar una reclamación ante la autoridad de control de su Estado miembro de la UE o del EEE. El establecimiento de Valve en la UE es Valve GmbH, con sede en Hamburgo, por lo que la autoridad de control principal para las reclamaciones transfronterizas es la Delegado de Hamburgo para la Protección de Datos y la Libertad de Información (HmbBfDI). (El representante a que se refiere el artículo 27 de Valve también tiene su sede en Hamburgo; la dirección de un representante no determina por sí sola cuál es la autoridad competente.) También se puede presentar una reclamación ante la autoridad del propio Estado miembro del reclamante, con arreglo al artículo 77.\n\nFormulario de reclamaciones de HmbBfDI ↗ Texto del RGPD (artículos 12, 15 y 77) ↗ archivado 2026-09-20 ↗Directrices del CEPD ↗\n\nNúmero de referencia del ticket para cualquier reclamación: HT-2YBP-F7JP-D4VB — que se recoge en este expediente como un caso documentado.\n\nUn caso documentado\nLos registros existen; el interesado no los ha recibido.\n\nEl abogado de Valve describió los registros de correlación a nivel de dispositivo en una carta de 1 de octubre de 2025. El 19 de septiembre de 2026 se archivó una solicitud en virtud del artículo 15 relativa a la misma clase de registros, remitiéndose al solicitante a una página de autoservicio que, según este, no contenía dichos registros, sin que se indicara el fundamento jurídico correspondiente. El ticket HT-2YBP-F7JP-D4VB es un caso documentado; si esto refleja una práctica más generalizada es una cuestión que debe resolver la autoridad de control, que puede solicitar a Valve sus registros de tramitación.\n\nArtículos 12, 15 y 77 del RGPD / Autoridad de control\n\nSe puede presentar una reclamación en virtud de los artículos 12 y 15 directamente ante la autoridad de control competente sin coste alguno (artículo 77). La autoridad podrá imponer medidas correctoras, incluidas órdenes de cumplimiento de la solicitud de acceso, y multas con arreglo al artículo 83, apartado 5, letra b), por vulneraciones de los derechos de los interesados. Conservar la referencia original del billete y cualquier respuesta Valve (o la ausencia de la misma) refuerza la reclamación.\n\nConsulta la plantilla del DSAR →\nParte C — Marcos jurídicos · Artículo 19 · Derecho contractual\nEl acuerdo de suscripción frente a la propia arquitectura de la plataforma\nContexto y límites de la fuente\n\nLos autores no son abogados y nada de lo aquí expuesto constituye asesoramiento jurídico. La cita de la SSA procede de la revisión del 10 de septiembre de 2026; una revisión diferente puede tener un texto distinto, y la numeración de las cláusulas ha cambiado a lo largo de las distintas revisiones; comprueba la cláusula con la versión que regulaba la conducta en cuestión. Los argumentos de los artículos 25 y 32 exponen lo que exige el reglamento, no que una autoridad de control haya constatado una infracción. Las cifras del argumento 1 recogen los límites de ámbito de aplicación establecidos en la sección 13.\n\nTres de las disposiciones fundamentales de la SSA chocan con la forma en que está diseñada la plataforma: la prohibición del uso comercial frente a un límite máximo de precios en el «Mercado» que empuja las ventas de alto valor fuera de la plataforma; la cláusula de responsabilidad del usuario por las claves API, frente a un punto final de claves que, antes de 2023, no exigía un segundo factor de autenticación; y la redacción relativa a la aplicación de la normativa, frente a un registro público que no muestra ninguna medida de aplicación por parte de los operadores. Que estas contradicciones afecten a la aplicabilidad es una cuestión que debe resolver un tribunal; en esta sección se exponen los hechos que se presentarían ante un tribunal.\n\nArgumento 1 / Arquitectura de la capitalización bursátil\nEl límite máximo del mercado y la prohibición de uso comercial\n\nEl mercado comunitario Steam tiene un límite máximo de cotización de aproximadamente $1,800. En cinco mercados, según una instantánea obsoleta (23 de septiembre de 2026), 248 categorías de artículos CS2 tienen precios fijos en dos o más de esos mercados que superan dicho límite máximo; dichos artículos no se pueden vender a esos precios en la propia plataforma de Valve. Los propietarios que deseen esos precios recurren a mercados de terceros, que funcionan con cuentas Steam y la API Steam —la SSA las considera de carácter comercial, salvo que se autorice expresamente lo contrario—.\n\nLos artículos superan el límite máximo del Mercado → los mercados de terceros cubren esa diferencia → dichos mercados utilizan cuentas Steam y la API Steam → la SSA prohíbe el uso comercial sin autorización → no se ha publicado ningún registro de autorizaciones. La comisión combinada del Mercado Comunitario, de aproximadamente 15%, se aplica únicamente a las ventas realizadas dentro del Mercado, no a estas transacciones externas.\nArgumento 2 / Arquitectura de seguridad de las claves API\nLa vulnerabilidad de la clave API como un problema de diseño de la plataforma, más que como una negligencia por parte del usuario\n\nAntes de 2023, el punto final de creación de claves API de Steam aceptaba una solicitud POST con un «sessionid» sustraído y generaba una credencial con privilegios elevados. sin confirmación por correo electrónico, sin autenticación de dos factores ni verificación mediante dispositivo. Las denuncias de secuestro de API recopiladas en esta investigación siguen un patrón común: script del atacante, cookie de sesión robada, creación silenciosa de claves e interceptación de transacciones (la carga útil de la solicitud se muestra en la sección 8).\n\nEl artículo 25 del RGPD (protección de datos desde el diseño) y el artículo 32 (seguridad del tratamiento) exigen la adopción de medidas técnicas adecuadas al riesgo. La emisión de una credencial susceptible de ser interceptada en el tráfico de datos sin un segundo factor de autenticación ni notificación al titular es una cuestión de diseño que incumbe al responsable del tratamiento. La cuestión de si, en ese contexto, puede invocarse la cláusula del SSA que atribuye la responsabilidad al usuario es competencia de los tribunales y de la autoridad de control.\n\nArgumento 3 / Visibilidad en tiempo real\nValve recibe el nombre de host de autenticación en cada inicio de sesión\n\nEl nombre de host de autenticación llega al punto final OpenID de Valve en texto sin cifrar en openid.return_to y openid.realm (la estructura de la solicitud se muestra en la sección 3). Su extracción es una operación estándar. A fecha de 2026-09-22, en 26 pares, el dominio principal figuraba en el filtro de enlaces, mientras que el host que albergaba su inicio de sesión Steam no lo hacía. Valve no ha publicado ningún registro de aplicación por operador, por lo que, a partir de los datos públicos, no se puede determinar si se ha aplicado alguna medida distinta del filtro de enlaces a estos hosts.\n\n¿Quién corre con los gastos?\nLa tendencia observada en las reclamaciones archivadas\n\nEn las reclamaciones analizadas, la respuesta del servicio de atención al cliente de Steam ante una denuncia de suplantación de una clave API sigue siempre el mismo patrón: rechazar la restauración, hacer hincapié en la responsabilidad del usuario respecto a la cuenta y su clave API, y cerrar el ticket. En este informe no se estima ninguna cifra global sobre el número de cuentas afectadas ni sobre el valor perdido; tampoco se ha localizado ninguna fuente que proporcione dicha cifra.\n\nLa cuestión no es si los usuarios individuales cometieron errores. La cuestión es quién es responsable de una arquitectura que, hasta 2023, permitía que una solicitud POST con una cookie robada creara una credencial de negociación con privilegios elevados sin notificación alguna y sin autenticación de dos factores.\nEl SSA como documento frente al SSA como contrato\nUn tribunal que evaluara este expediente no interpretaría la SSA de forma aislada.\n\nLo leería junto con la carta del abogado de octubre de 2025 en la que se describen la correlación a nivel de dispositivo, las fechas de registro del host de autenticación, las marcas de tiempo de registro por lotes, la carga útil de la solicitud de la clave API y los diez años transcurridos entre las notificaciones de julio de 2016 y las plataformas que seguían operando en septiembre de 2026. Ese es el expediente que Valve tendría que abordar.\n\nSSA en relación con el expediente / puntos clave\n«Sin uso comercial»: el límite máximo del mercado empuja las ventas de alto valor hacia mercados comerciales de terceros\n«Los usuarios son responsables de las claves API»: no habrá autenticación de dos factores en el punto final de las claves hasta 2023\n«Tomamos medidas contra los infractores»: no se ha publicado ningún registro de sanciones por operador desde julio de 2016\n«Has aceptado las condiciones»: en el patrón de secuestro, la aceptación la envía un script, no el titular de la cuenta.\nConclusión · Lo que se desprende del expediente y lo que solicitamos\nLas conclusiones. Los documentos que solicitamos.\nContexto y límites de la fuente\n\nCada una de las conclusiones que figuran a continuación está vinculada a un registro público con fecha concreta que aparece en las secciones anteriores. Las solicitudes se dirigen a las autoridades que pueden obtener lo único a lo que esta investigación no tiene acceso: los propios registros de aplicación, acceso y tratamiento de Valve.\n\nCada solicitud se basa en una conclusión fechada. Las autoridades pueden solicitar documentos que esta investigación basada en fuentes públicas no puede exigir.\n\nLo que se desprende de los registros públicos\n44 plataformas activas se autentican a través de un dominio independiente registrable: 27 con un archivo de pruebas publicado por ruta y 17 procedentes de una recopilación manual y que figuran por separado. A fecha de 2026-09-22, 26 pares tenían el dominio principal bloqueado en el filtro de enlaces Steam, mientras que el servidor que alojaba su página de inicio de sesión no lo estaba: csgogem.com bloqueado, api.csgem.com registrado desde marzo de 2014. Steam recibe ese nombre de host en openid.realm y openid.return_to cada vez que se inicie sesión. Sección 3\nEl 13 de julio de 2016, Valve dio a conocer públicamente dicho mecanismo y lo prohibió, y las notificaciones de su abogado, de fecha 20 de julio de 2016, fijaron un plazo de diez días. En los diez años transcurridos desde que venció dicho plazo, no se ha publicado ningún registro de medidas coercitivas por operador. Artículo 11\nEl punto final de la clave de la API web Steam emitía una credencial con privilegios elevados y apta para operaciones bursátiles basándose únicamente en una cookie de sesión, sin ningún factor de autenticación adicional antes de 2023. Sección 5\nUna solicitud en virtud del artículo 15 del RGPD (ticket HT-2YBP-F7JP-D4VB) se cerró al cabo de tres días con un enlace al autoservicio y sin datos. Artículo 18\nLo que pedimos a cada autoridad\nComisión de Juegos de Azar del Estado de Washington\nVuelve a abrir el expediente de 2016. Solicita un informe detallado, operador por operador, sobre qué cuentas, bots y hosts de retorno se desactivaron tras los avisos de diez días, y qué operadores recuperaron posteriormente el acceso. Sección 2\nHmbBfDI (Hamburgo; Valve GmbH)\nComprobar si la respuesta prevista en el artículo 15 cumplió con la obligación del responsable del tratamiento y exigir la divulgación de los registros de registro y acceso de la clave API pertinentes para identificar al autor. Artículo 18\nCoordinadores de servicios digitales de la DSA\nIncluye la ruta de auth-host en el registro como aviso y, una vez documentada la información, evalúa si la respuesta de Valve cumple con sus obligaciones. Artículo 16\nCualquier interesado\nUtiliza la plantilla del artículo 15 para solicitar los mismos registros para tu propia cuenta; un registro conservado puede servir para determinar quién inició un restablecimiento o quién creó una clave. Apéndice G\n\nLa única petición que subyace a las cuatro es la misma: publicar los registros relativos a la aplicación de la normativa, el acceso y el tratamiento de datos que solo Valve conserva. Una advertencia en la página de inicio, una carta con un plazo de diez días y una página de autoservicio son manifestaciones de control. Si se ejerció o no dicho control es una pregunta que el registro público no puede responder, pero que sí puede responder un organismo regulador.\n\nAnexos: pruebas documentales principales y materiales de trabajo\nApéndice A — Correspondencia con los abogados\nMemorándum probatorio — material facilitado por la Fuente 1\n\nBase probatoria y estado de las fuentes de la correspondencia con el abogado en la que se basa lo expuesto en los artículos 1, 18 y 19.\n\nBase empírica y estado de la fuente: documentos facilitados por la Fuente 1\nEl usuario cuya expulsión definitiva dio lugar a esta auditoría no es el objeto de la misma. En este informe no se examina si dicha expulsión estuvo justificada, y este expediente no la defiende ni la cuestiona. La cuenta no es lo importante. Lo que importa es el material: Fuente 1 — El titular de la cuenta bloqueada, que recibió la correspondencia que figura a continuación del abogado de Valve en su calidad de interesado de su propia solicitud en virtud del RGPD — facilitó dicha correspondencia y los expedientes adjuntos, junto con el derecho a consultarlos públicamente. Se omite el nombre; los documentos se describen por fecha, metadatos del autor y hash.\n\nDicha correspondencia se envió en respuesta a una solicitud en virtud del RGPD/DSAR. En el transcurso de la misma, el abogado de Valve hizo constar en el expediente, mediante firma, una declaración en la que describía una funcionalidad que el servicio de asistencia de Steam había indicado previamente a los usuarios que no era técnicamente posible. El párrafo que se cita a continuación es dicha declaración.\n\nEl análisis adicional que han realizado los autores del extracto de registro obtenido es omitido en este expediente a la espera de una revisión independiente. Ninguna otra parte de esta investigación se basa en ello.\n\nLa admisión que consta en el expediente: telemetría persistente a nivel de dispositivo\n\nEn el apartado 1.9 de la carta atribuida al abogado de Valve, los abogados de Valve afirman: «Entre 2019 y 2023, esta cuenta se utilizó principalmente desde un dispositivo que también se empleó para iniciar sesión en docenas de cuentas Steam robadas».\n\nEl hecho: El abogado de Valve describe aquí la correlación a nivel de dispositivo entre cuentas a lo largo de cuatro años. El servicio de asistencia de Steam ha comunicado a las víctimas de robos que el seguimiento de los artículos robados o la vinculación de cuentas a dispositivos no era técnicamente posible. Steam Guard La autorización de dispositivos está documentada públicamente, por lo que la existencia de registros por dispositivo no es en sí misma una novedad; lo que sí es nuevo es la confirmación por escrito del abogado de que dichos registros se conservan y se correlacionan entre cuentas a lo largo de períodos de varios años.\n\nPor qué es importante: La correlación que puede vincular un dispositivo con docenas de cuentas pirateadas a lo largo de cuatro años corresponde al mismo tipo de registro que, según el Servicio de Asistencia, no podía facilitar a las víctimas. Los registros de ese tipo permitirían identificar cuentas y dispositivos en una cadena de robo y reventa. Qué registros existen, cuánto tiempo se conservan y en qué se basa la decisión de no facilitárselos a los interesados son cuestiones que debe abordar la autoridad de control.\n\nFuente: carta del abogado de Valve, con fecha del 1 de octubre de 2025, apartado 1.9, y su anexo en formato PDF de 830 páginas · recibida por la Fuente 1 en respuesta a una solicitud en virtud del artículo 15 del RGPD · SHA-256 del anexo registrado en disclosure-audit.json · No se reproduce el texto de la carta; se omiten los nombres de las cuentas y los datos de terceros.\n\nEstado: abrir\nLos materiales originales están disponibles en el archivo de pruebas.\nApéndice B — El PDF generado · comprobación de la censura\nLa censura que aparece en el PDF generado es meramente estética: el texto ocultado sigue pudiendo extraerse.\n\nEl abogado de Valve respondió a una solicitud de acceso en virtud del RGPD con un anexo de 830 páginas en el que los datos ocultados se han tachado sobre el texto en lugar de eliminarlos. 902,270 caracteres aparecen debajo de las barras negras y se extraen directamente con una herramienta de extracción de texto — incluidos los identificadores de terceros que las barras debían ocultar. Aquí solo se publican las cifras agregadas; no se reproduce ningún contenido protegido y el propio apéndice no se publica.\n\n1. Resultados de la comprobación geométrica\n\nRespuesta en virtud del artículo 15 del RGPD, con fecha del 1 de octubre de 2025 Iba acompañado de un apéndice en formato PDF de 830 páginas (metadatos del creador de Aspose.PDF para .NET, creados y modificados en la misma fecha). Los autores realizaron una comprobación de la geometría a nivel de página: para cada página, se localizaron los rectángulos opacos, casi negros, superpuestos a la capa de texto y se contaron los caracteres extraíbles que se encontraban debajo de ellos.\n\nMedido en el archivo generado\n902,270\nCaracteres que aún se pueden extraer de debajo de las barras negras\nContados, no estimados. Se trata de un recuento de los personajes incluidos, no de víctimas, reidentificaciones o incidentes.\n830 / 830\nPáginas afectadas: todas las páginas\n986\nRectángulos sobre texto extraíble\n1,329\nRectángulos negros opacos en total\nLas barras negras se superponen a la capa de texto; no la eliminan. El texto que se encuentra debajo de las barras puede extraerse con herramientas estándar de PDF. Solo se publican las cifras globales; aquí no se reproduce ningún contenido oculto.\nDemostración forense: separación de capas\nMAQUETA DE SUPERPOSICIÓN VECTORIAL DE ASPOSE.PDF PARA .NET (APÉNDICE, PÁG. 412)\n\nDenuncia presentada contra la cuenta: [INICIO DE SESIÓN: redacted_user_667]\n\nMotivo indicado por el usuario: [TEXTO: «Un usuario denuncia la presencia de artículos duplicados en el inventario y conductas comerciales abusivas...»]\n\nPrimer plano: <path fill=\"#000\" />Vulnerabilidad: El flujo UTF-8 subyacente permanece intacto\nFuente: Apéndice en formato PDF de la carta del abogado del 1 de octubre de 2025 (830 páginas, metadatos del creador de Aspose.PDF para .NET) · calculado por los autores, método y recuento por página en disclosure-audit.json · El SHA-256 del apéndice se incluye en el mismo archivo · El apéndice en sí no se publica.\n2. Por qué esto es importante para la respuesta del interesado\n\nEl abogado de Valve envió este expediente a un interesado en respuesta a una solicitud de acceso a sus propios datos. Las barras que aparecen son meramente estéticas: el texto que hay debajo nunca se eliminó, por lo que los identificadores de terceros que se pretendía ocultar con esas barras llegaron al destinatario junto con el archivo. Una censura que se elimina con una herramienta de extracción de texto no oculta nada y, además, impide que el destinatario pueda determinar qué información se reveló y cuál no.\n\nEl artículo 15, apartado 4, es la razón por la que existen esas restricciones: el derecho a obtener una copia no debe afectar negativamente a los derechos y libertades de terceros. Esa es la obligación que esta producción no cumplió. Corresponde a la autoridad de control determinar si se trata de una violación de datos personales con arreglo al artículo 4, apartado 12; la divulgación en sí misma es cuantificable en el archivo y reproducible por cualquier persona que disponga de los mismos bytes: el SHA-256 está publicado, pero el anexo no.\n\nLo que había debajo de las barras no eran números de cuenta. Se trataba del conjunto de denuncias presentadas por los usuarios contra el solicitante, con los nombres de sus autores adjuntos: Steam inicios de sesión que, dado que rara vez se utiliza un inicio de sesión únicamente en Steam, identifican a la persona que hay detrás de ellos — Según el recuento de los autores, más de 60% de los usuarios mencionados en el documento son totalmente identificables — junto con el texto original, sin censurar, de lo que escribieron. Dicho texto incluye amenazas de muerte e insultos dirigidos a la nacionalidad del solicitante. Algunas de las personas así identificadas son menores de edad. La producción entregó una lista con los nombres de los periodistas a la persona a la que habían denunciado., que es precisamente el perjuicio que el artículo 15, apartado 4, pretende evitar.\n\nEl orden de los caracteres del archivo es tan importante como su contenido. La solicitud se respondió en un primer momento con la exigencia de aportar más pruebas de identidad, alegando que la dirección de correo electrónico con seudónimo del solicitante no incluía su nombre; la cuenta fue bloqueada de forma permanente durante el retraso que se produjo a continuación. La carta que finalmente facilitó los datos, más de seis semanas después del plazo de un mes establecido en el artículo 12, apartado 3, amenazaba al destinatario con un proceso penal y retenía el resto de sus propios datos hasta que explicara la actividad de su cuenta al abogado. La divulgación también aclara dos cuestiones que Valve no había respondido públicamente: los registros presentados muestran que la vinculación de cuentas se remonta a 2019, y una telemetría interna de una profundidad que Valve nunca ha descrito.\n\nÁmbito de aplicación de esta sección: La observación que aquí se presenta se limita a los aspectos técnicos de la redacción, tal y como se aprecian en el expediente tal y como se ha presentado. El análisis más detallado que han realizado los autores de los registros presentados queda en suspenso a la espera de una revisión independiente y no se tiene en cuenta en ninguna otra parte de este expediente.\n\nPrueba: carta del abogado de 1 de octubre de 2025 y su anexo en formato PDF (SHA-256 registrado en el archivo de auditoría); Medidas y método en PDF a nivel de página ↗. La secuencia de la solicitud, la denegación de la página 8 y la descripción de los registros divulgados se exponen en detalle en el relato de PhishDestroy, «Mi perro contra los abogados expertos en el RGPD», 17 de agosto de 2026 ↗ archivado 2026-08-21 ↗. En este caso se han omitido los nombres de las cuentas y los datos de terceros; no se reproduce nada de lo que quedan ocultos tras las barras.\n\nEn la página 8 de la carta de presentación se deniega parte de la solicitud y se expone el motivo por escrito: No es posible facilitar información más detallada debido a la protección de los datos personales de otros usuarios de la plataforma Steam… — No es posible dar una respuesta más detallada, ya que hay que proteger los datos personales de otros Steam usuarios. El anexo de 830 páginas se encontraba en el mismo paquete. Lo que ocultaban las barras no eran números de cuenta: se trataba de las denuncias presentadas contra el solicitante, con los nombres de sus autores y los mensajes originales sin censurar adjuntos. El titular de la cuenta había solicitado a Valve, a través de su abogado, su propio expediente; lo que pudo extraer de él eran datos de otras personas. Nada de lo que figura en este anexo tiene que ver con quién dibujó los recuadros. Lo que queda claro es que la protección Valve invocada como motivo para la retención es precisamente la protección que esta misma entrega no respetó, en el mismo sobre, el mismo día.\nDocumentación de apoyo y correspondencia jurídica\n\nFuente: https://phishdestroy.io/steam_dossier/es/index#exhibit-gallery-section\n\nApéndice D — Recogida de muestras\nDocumentos primarios seleccionados\n\nSeis registros del archivo: tres incidencias de GitHub en los sistemas de seguimiento de Valve y tres cuentas de Reddit con resultados controvertidos de la asistencia técnica. Cada fuente se mantiene vinculada a la reclamación, al texto guardado y a la cuestión que plantea.\n\n1 / 6 registros seleccionados\nElige un registro de origen\nGH-01 / GITHUBAbrir en la compilación guardada\nClaves de hardware, solicitadas en 2016\n\nValveSoftware / steam-for-linux · n.º 4521 · 2016-06-27\n\nUn usuario solicitó a Valve que admitiera las llaves de hardware U2F como segundo factor de autenticación alternativo. La incidencia guardada lleva las etiquetas «Solicitud de función» y «Revisada», y su estado figura como «abierta».\n\nSolicito que Steam admita los llaveros USB U2F como alternativa.\n\nExtracto de la incidencia de GitHub ↗\nExpediente documentado\nUna solicitud antigua para una medida de seguridad adicional en la cuenta, publicada en el propio sistema de seguimiento de incidencias de Valve y marcada como «revisada».\nExigencia de rendición de cuentas\nPublica la decisión sobre el producto, la fecha de respuesta y la protección concedida tras la revisión.\nLeer el registro guardado →Abrir GitHub ↗\nEn el dossier: Medidas de seguridad de la cuenta →Archivo n.º 484 · compilación 2026-09-17\nGH-02 / GITHUBAbrir en la compilación guardada\nInformes de fallos sin una opción de exclusión efectiva\n\nValveSoftware / steam-for-linux · n.º 6459 · 2019-08-18\n\nEl autor del informe describe un problema con el cliente Steam, detectado el 12 de agosto de 2019 en Ubuntu 16. Afirma que la desactivación del destino de «crash-upload» no se mantuvo tras reiniciar el sistema, e incluye la configuración correspondiente.\n\nSi desactivo la `ServerURL`, se sobrescribe cada vez que se reinicia el sistema.\n\nExtracto de la incidencia de GitHub ↗ archivado 2026-04-19 ↗\nExpediente documentado\nUna reclamación específica sobre privacidad que incluye la fecha del cliente, el sistema operativo y un extracto de la configuración. El incidente guardado está abierto.\nExigencia de rendición de cuentas\nIdentifica la investigación, las versiones afectadas y el cambio que hizo efectiva la exclusión voluntaria.\nLeer el registro guardado →Abrir GitHub ↗archivado 2026-04-19 ↗\nEn el expediente: Solicitar los documentos correspondientes →Archivo n.º 467 · compilación 2026-09-17\nGH-03 / GITHUBAbrir en la compilación guardada\nSe ha notificado un uso indebido de un ticket de autenticación a Valve\n\nValveSoftware / Source-1-Games · n.º 3857 · 2022-02-26\n\nEl autor alega que el equipo de administración del servidor conservó Steam tickets de autenticación después de que los jugadores se desconectaran y utilizó listados de servidores engañosos. En la publicación se pide a Valve que se pronuncie sobre este comportamiento.\n\nHacer que parezca que sus servidores están a rebosar.\n\nExtracto de la incidencia de GitHub ↗\nExpediente documentado\nUna denuncia por abuso público presentada en el sistema de seguimiento de Valve el 26 de febrero de 2022. Su estado guardado es «abierto»; la denuncia incluye enlaces a capturas de pantalla.\nExigencia de rendición de cuentas\nElabora el informe de la investigación y el registro de medidas correctivas relativos al uso indebido del ticket de autenticación que se ha denunciado.\nLeer el registro guardado →Abrir GitHub ↗\nEn el dossier: Alcance del conjunto de datos →Archivo n.º 768 · compilación 2026-09-17\nRD-01 / REDDITPerfil del autor\n44 compras en el mercado objeto de litigio\n\nr/DotA2 · nombre de usuario oculto · 2022-07-07\n\nEl autor informa de 44 compras no autorizadas en Market el 6 de julio de 2022 y de unas pérdidas de aproximadamente $500+. Afirma que la autenticación de dos factores estaba activada y describe las repetidas respuestas tipo que recibió del servicio de atención al cliente.\n\nYa es el segundo ticket que envío y todavía no he recibido ninguna respuesta de Steam que no sea una plantilla copiada y pegada automáticamente.\n\nFragmento de la publicación de Reddit ↗ archivado 2025-03-20 ↗\nExpediente documentado\nUn relato detallado de unas compras objeto de disputa, con enlaces a capturas de pantalla de las transacciones y una respuesta del servicio de atención al cliente. Las cantidades y los hechos son según lo relatado por el autor.\nExigencia de rendición de cuentas\nConciliar las compras objeto de disputa con los registros de transacciones y de sesiones. Explicar los fundamentos en los que se basa la decisión del servicio de atención al cliente.\nLeer el registro guardado →Abrir Reddit ↗archivado 2025-03-20 ↗\nEn el dossier: Apoyo y cumplimiento →Archivo n.º 4,533 · compilación 2026-09-17\nRD-02 / REDDITPerfil del autor\nUna suspensión definitiva y la imposibilidad de recurrir\n\nr/ohnePixel · nombre de usuario oculto · 2024-12-09\n\nEl autor cuestiona la suspensión permanente y afirma que el servicio de asistencia se basó en una supuesta transferencia de cuenta y en denuncias de la comunidad. Describe los tickets cerrados y sus planes de solicitar sus datos personales.\n\nLes expliqué mi situación y les pedí más detalles, pero se mantienen firmes en su decisión y van a cerrar mis incidencias.\n\nFragmento de la publicación de Reddit ↗\nExpediente documentado\nUna descripción de la apelación conservada, que incluye los motivos que, según el autor, respaldan la ayuda prestada y enlaces a cuatro imágenes. La fecha de la publicación procede de la exportación de la ayuda seleccionada.\nExigencia de rendición de cuentas\nIdentifica las pruebas en las que se basa la prohibición permanente y los recursos disponibles para impugnarla. El hecho de desestimar un recurso no explica la decisión.\nLeer el registro guardado →Abrir Reddit ↗\nEn el expediente: Solicitar los documentos correspondientes →Archivo n.º 4,766 · compilación n.º 2026-09-17\nRD-03 / REDDITPerfil del autor\nUn reinicio de la recuperación y una pérdida declarada de $10,000\n\nr/legaladvice · nombre de usuario oculto · 2025-05-09\n\nEl autor alega que el servicio de atención al cliente restableció las credenciales y desactivó las medidas de protección de la cuenta después de que otra persona presentara una solicitud de recuperación. Denuncia una pérdida de aproximadamente US$10,000 de una cuenta inactiva.\n\nSteam El servicio de asistencia me ha restablecido la contraseña y ha desactivado todas las medidas de seguridad de mi cuenta.\n\nFragmento de la publicación de Reddit ↗\nExpediente documentado\nUna denuncia conservada sobre cómo el proceso de recuperación anula las medidas de seguridad de la cuenta. La publicación guardada recoge lo que, según el autor, le comunicó el servicio de atención al cliente.\nExigencia de rendición de cuentas\nIdentifica quién autorizó el restablecimiento, las pruebas de titularidad que se aceptaron y el registro de acceso. La recuperación de la cuenta forma parte de los controles del sistema de seguridad Valve.\nLeer el registro guardado →Abrir Reddit ↗\nEn el expediente: Solicitar los documentos correspondientes →Archivo n.º 4,592 · compilación 2026-09-17\n\nSeis registros seleccionados. Las descripciones de GitHub recogen la compilación guardada. Las publicaciones de Reddit conservan los relatos de los autores.\n\nDescarga los seis discos ↓\n\nLa versión con función de búsqueda contiene 16,319 registros distintos: 393 en Trustpilot, 5,635 en Reddit, 2,395 en GitHub, 276 entradas en la web y 7,620 en la wiki. Varias entradas pueden referirse al mismo evento. La exportación principal, de 40,448 filas, tiene un alcance diferente.\n\nBuscar en todo el archivo ↗ · Generar manifiesto ↗ · Ámbito y recuentos del conjunto de datos →\n\nApéndice E — Estudio de caso\nArchiSteamFarm y la cláusula de automatización\n\nUna herramienta de código abierto para la «farming» de tarjetas que, según su propia sección de preguntas frecuentes, funciona en millones de cuentas, lo que contraviene la cláusula del Acuerdo de Suscripción (§ 4.C) que prohíbe la automatización. Los mecanismos —lo que una granja tiene que comprar a Valve antes de poder producir nada, por qué todas las formas de cobrar una tarjeta incumplen la licencia, el historial de aplicación de la normativa y quién modera la economía de las tarjetas— se describen detalladamente en Anexo V ↗.\n\nEl Contrato de Suscripción Steam, en su apartado 4.C, establece lo siguiente:\n\n«No está permitido utilizar ningún tipo de script, bot, macro u otros sistemas no controlados por personas («automatización») para interactuar de ninguna manera con el Contenido y los Servicios de Steam». — Steam Contrato de suscripción, artículo 4.C (vigente) ↗ archivado 2026-09-18 ↗\n\nValve se encarga de hacer cumplir esta cláusula. Lo hace muy bien. Las preguntas frecuentes de ArchiSteamFarm (ASF) — una herramienta de código abierto que, según su propia documentación, se ejecuta en más de unos cuantos millones de cuentas Steam Desde su primer lanzamiento, hace más de 11 años, reproduce tres Steam mensajes del servicio de asistencia en los que se expulsaba de forma permanente a los usuarios que gestionaban redes de bots. Valve detectó las redes, las identificó y las desmanteló. Por lo tanto, la cuestión relevante no es si Valve es capaz de detectar la automatización a gran escala.\n\nLa página web oficial del proyecto ArchiSteamFarm Preguntas frecuentes aborda directamente el riesgo de una prohibición:\n\n«Esto es muy poco probable, teniendo en cuenta que ASF se utiliza en más de unos cuantos millones de cuentas Steam desde su lanzamiento, hace ya más de 11 años; pero sigue siendo una posibilidad, independientemente de la probabilidad real».\n\n«Valve reconoce claramente que existen los «Steam holgazanes», tal y como se afirma aquí, así que, si me preguntas, estoy bastante seguro de que, si no les parecieran bien, ya habrían hecho algo al respecto en lugar de señalar que podrían causar problemas en lo que respecta a VAC. La palabra clave aquí es «juegos de inactividad» (por ejemplo, ASF), y no «juegos de inactividad».\"\n\n— ArchiSteamFarm Preguntas frecuentes, JustArchiNET. Fuente: Wiki de GitHub ↗ · verificado palabra por palabra 2026-09-22\n\nEn la misma sección de preguntas frecuentes, a la pregunta «¿Han expulsado a alguien por eso?» se responde con Sí, y reproduce lo que Steam Support escribió a tres de ellos:\n\n1,000+ bots · prohibido comerciar\n«Parece que esta cuenta se utilizó para gestionar una red de cuentas de bots. El uso de bots constituye una infracción del Acuerdo de suscriptor Steam».\n\nMás de 170 bots · bloqueados de forma permanente, rebajas de invierno de 2017\n«Esta cuenta se utilizó para coleccionar ilegalmente tarjetas coleccionables en Steam, así como para actividades relacionadas, no solo de carácter comercial. La cuenta ha sido bloqueada de forma permanente y el servicio de atención al cliente de Steam no puede ofrecer asistencia adicional sobre este asunto».\n\nMás de 120 bots · bloqueados de forma permanente\n«Esta y otras cuentas se utilizaron para saturar nuestra infraestructura de red, lo que constituye una infracción de las normas de conducta en línea Steam».\n\n— Steam Mensajes de asistencia reproducidos en la ArchiSteamFarm sección de preguntas frecuentes, apartado «¿Han expulsado a alguien por eso?». Fuente ↗ · verificado palabra por palabra 2026-09-22\n\nColoca los dos discos uno al lado del otro. Se identifica a un usuario particular que utiliza 1,000 bots de farming, se le informa de que «el uso de bots constituye una infracción del Steam Acuerdo de Suscriptor» y se le expulsa de forma permanente. Las plataformas comerciales incluidas en este informe gestionan cuentas automatizadas Steam como actividad principal, a una escala mucho mayor, y se autentican a través del propio OpenID de Valve en cada inicio de sesión; sin embargo, no se ha publicado ningún registro de medidas disciplinarias por operador para ninguna de ellas. La cláusula es válida. La cuestión es a quién va dirigida.\n\nAquí no se acusa a la ASF de nada, y su interpretación de la postura de Valve es propia: su autor afirma claramente que «la ASF no está autorizada por Valve». La herramienta se utiliza aquí como instrumento de medición: muestra que Valve detecta redes de bots, las identifica por escrito y las bloquea de forma permanente. Valve puede zanjar la cuestión con una sola frase publicando qué automatización comercial autoriza y el registro, por operador, de las medidas que tomó con respecto al resto.\n\nCómo afecta la «farming» de tarjetas a los ingresos de Valve\n\nLas cartas coleccionables obtenidas en el juego se venden en el Mercado de la Comunidad Steam, que cobra una comisión total de aproximadamente 15% por cada venta realizada en el Mercado; la cuenta debe haber gastado $5.00 USD en Steam antes de poder recibir una tarjeta; y para obtener tarjetas es necesario poseer el juego o realizar compras dentro del mismo. Aquí no se estima ninguna cifra de ingresos totales: la escala operativa se indica únicamente tal y como la describe la sección de preguntas frecuentes de ASF. La sección de preguntas frecuentes también recoge Valve características distintivas \"Steam ociosos\" (obtención de cartas) de «jugadores que no hacen nada»; véase el Preguntas frecuentes sobre la peste porcina africana ↗. Las normas se describen detalladamente en Anexo V — la escala y la trampa del uso comercial.\n\nAsuntoArchiSteamFarm — obtención automática de tarjetas\nEscala indicadaMillones de cuentas (según las preguntas frecuentes de la ASF; no se ha verificado el número exacto de cuentas activas)\nContados, no citados10,880,610 entradas API en total en el propio grupo Steam de la ASF (5,360,499 sin límite, tal y como muestra Steam): los «millones» de las preguntas frecuentes no son una cifra aproximada, sino un recuento. 88.97% no conllevan Steam prohibición de ningún tipo. Censo completo de las prohibiciones ↗\nInformación que figura en la propia documentación de la herramienta\nASF inicia sesión en las cuentas en modo sin interfaz gráfica y mantiene los juegos en espera para obtener cartas sin iniciar el cliente Steam (según la documentación del proyecto).\nEn la sección de preguntas frecuentes se argumenta que Valve es consciente de la existencia de los «Steam holgazanes» y que «si no les parecieran bien, ya habrían hecho algo al respecto».\nNo se ha informado de ninguna medida coercitiva específica en más de 11 años (según las preguntas frecuentes); las ventas de tarjetas resultantes dentro del Community Market conllevan una comisión combinada de Steam, que asciende a unos 15%.\nEn la sección de preguntas frecuentes se establece un límite máximo recomendado de diez cuentas por operador y se atribuye a Valve: «Esta recomendación se basa en directrices internas de Valve, así como en nuestras propias sugerencias». Valve no ha publicado ninguna directriz de este tipo.\nLímite técnico, según la misma sección de preguntas frecuentes: «Se pueden ejecutar entre 100 y 200 bots con una sola dirección IP y una sola instancia de ASF».\nEl tiempo de juego «farmado» lo registra Valve —«suele actualizarse cada 30 minutos aproximadamente»— y el apartado § 4.C incluye «Falsificar estadísticas de juego (por ejemplo, inflar el número de victorias o derrotas, la XP o el tiempo de juego)» como una acción prohibida.\nFuentes\nWiki oficial de preguntas frecuentes de JustArchi ASF ↗ ArchiSteamFarm repositorio ↗ archivado 2026-09-24 ↗\nLa cláusula sobre automatización es explícita; en las preguntas frecuentes de la ASF se afirma desde hace años que la herramienta se utiliza en millones de cuentas; no se ha informado de ninguna medida coercitiva específica contra ella. La discrepancia entre la norma y su aplicación queda reflejada en los registros; aquí no se establece la razón de dicha discrepancia.\nExposición completaLa economía de las tarjetas: el proceso, la escala, la licencia y quién la regula ↗Lo que una granja tiene que comprar a Valve antes de poder producir una sola tarjeta; las dos líneas del § 4.C que definen la «granja de tarjetas» por sus efectos; por qué cualquier forma de canjear una tarjeta incumple la licencia Valve, mientras que Valve cobra una tarifa en la entrada; el historial de cumplimiento, incluida la oleada de VAC de junio de 2025 y la prohibición en cadena por número de teléfono compartido; y los empleados de Valve y moderadores de la comunidad que se encargaban de gestionar los servicios de intercambio de tarjetas y la lista de prohibidos en torno a Steam.El censo de las prohibicionesNo le preguntamos a Valve qué tamaño tiene la granja. La medimos. ↗10,880,610 cuentas en total (limitadas y no limitadas) leídas del grupo Steam propio de ArchiSteamFarm, al que el software se une automáticamente por defecto al iniciarse por primera vez, a menos que el usuario desmarque la opción de unirse al grupo (lo que incluye tanto a las granjas de bots comerciales como a los jugadores habituales que mantuvieron la configuración predeterminada). 88.97% no tiene ninguna Steam suspensión de ningún tipo; de los 11% que sí la tienen, 99.8% son suspensiones comunitarias meramente simbólicas que nunca impiden seguir operando. Tras cotejarlo con SteamRep, 67.77% de los estafadores de la lista quedan en libertad una vez que se dejan de lado las sanciones del sistema antitrampas. Con desgloses por fecha de registro, ubicación geográfica y permanencia: la escala real, medida, no narrada.\n\nAppendix F — Working ledger\n\nRules ledger: clauses against recorded platforms\n\nElige una regla; el registro muestra las plataformas registradas etiquetadas bajo ella, junto con su dominio principal, el servidor de autenticación declarado y el resultado guardado del filtro de enlaces. Si se trata de una página web bloqueada o de otro dominio para iniciar sesión, sigue la regla hasta llegar a la ruta que queda.\n\n175registros vinculados\na esta norma\n174 dominios principales0 Menciones de C&D\nEXTRACTO DE LA NORMA / SSA § 2.G\nUso comercial y facturación de la cuenta\n“…exploit the Content and Services or any of its parts for any commercial purpose, except as expressly permitted elsewhere in this Agreement (including any Subscription Terms or Rules of Use).”\nSIGUE LOS RESULTADOS\nRegistro de la plataforma 175\nLas cifras a escala son estimaciones de las fuentes.\n\n175 de los discos de «175»\n\nServicio / grupo matriz\tDominio principal / registro\tDominio de autenticación observado / antigüedad\tEscala / respuesta registrada\n\nCasino\n\tcsgoempire.com\n11.3 yearsRegistered 2015-06-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgoempirelogin4.com\n6.2 yearsRegistered 2020-07-20\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustreaper.com\n23.2 yearsRegistered 2003-06-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustreaper.com\n23.2 yearsRegistered 2003-06-24\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustly.com\n12.4 yearsRegistered 2014-05-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustly.com\n12.4 yearsRegistered 2014-05-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette Casino\n\tcsgofast.com\n11.5 yearsRegistered 2015-03-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsteam-login.authtofast.com\n83 daysRegistered 2026-06-30\nRDAP ↗ · authtofast.com (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tduelbits.com\n6.6 yearsRegistered 2020-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nswitchflips.com\n6.4 yearsRegistered 2020-04-21\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opener\n\tfarmskins.com\n10.5 yearsRegistered 2016-03-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsteam.kobal.cc\n9.7 yearsRegistered 2017-01-07\nRDAP ↗ · kobal.cc (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgoluck.com\n9.3 yearsRegistered 2017-05-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgoluck.com\n9.3 yearsRegistered 2017-05-18\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tinsane.gg\n7.5 yearsRegistered 2019-04-02\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.insane.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcs2skin.com\n3.5 yearsRegistered 2023-03-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncs2skin.com\n3.5 yearsRegistered 2023-03-06\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tjuice.gg\n7.9 yearsRegistered 2018-10-19\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nletmeinjuice.com\n2.4 yearsRegistered 2024-04-15\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tggdrop.com\n8.6 yearsRegistered 2018-02-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nggauth.com\n3.4 yearsRegistered 2023-05-03\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Casino\n\thowl.gg\n9.5 yearsRegistered 2017-03-16\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhowl.uno\n41 daysRegistered 2026-08-11\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tchicken.gg\n5.7 yearsRegistered 2021-01-11\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nchicken.gg\n5.7 yearsRegistered 2021-01-11\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgocasino.gg\n2.6 yearsRegistered 2024-02-17\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.csgocasino.gg\n2.6 yearsRegistered 2024-02-17\nWHOISFREAKS ↗ · csgocasino.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Casino\n\thunt.gg\n6.9 yearsRegistered 2019-11-04\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.hunt.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Battles\n\tcsbattle.com\n9.8 yearsRegistered 2016-12-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsbattle.com\n9.8 yearsRegistered 2016-12-10\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskinrave.gg\n3.1 yearsRegistered 2023-08-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinrave.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsdouble.gg\n261 daysRegistered 2026-01-03\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsdouble.gg\n261 daysRegistered 2026-01-03\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustchance.com\n8.0 yearsRegistered 2018-10-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhgfuihd.com\n7.6 yearsRegistered 2019-01-27\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Automation\n\tcobaltlab.tech\n3.5 yearsRegistered 2023-03-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncobaltauth.com\n1.7 yearsRegistered 2025-01-07\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\traided.gg\n171 daysRegistered 2026-04-03\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.raided.gg\n171 daysRegistered 2026-04-03\nIP2WHOIS ↗ · raided.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustneo.gg\n1.3 yearsRegistered 2025-06-20\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustneo.gg\n1.3 yearsRegistered 2025-06-20\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tsplits.gg\n3.7 yearsRegistered 2023-01-23\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsplits.gg\n3.7 yearsRegistered 2023-01-23\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Upgrader\n\tupgrader.pro\n1.2 yearsRegistered 2025-07-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nupgauth.space\n38 daysRegistered 2026-08-14\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskin.fans\n8.2 yearsRegistered 2018-07-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skinfans.com\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\thotpizza.one\n1.8 yearsRegistered 2024-12-07\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhotpizza.one\n1.8 yearsRegistered 2024-12-07\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tg4skins.com\n10.1 yearsRegistered 2016-08-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.g4s.to\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2royal.com\n4.1 yearsRegistered 2022-08-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ntf2auth.com\n5.2 yearsRegistered 2021-07-27\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2hunt.com\n8.7 yearsRegistered 2018-01-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrstspcl.com\n6.1 yearsRegistered 2020-08-08\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2.bet/coinflip\n8.4 yearsRegistered 2018-05-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ntf2.bet\n8.4 yearsRegistered 2018-05-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\topenstars.gg\n131 daysRegistered 2026-05-13\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nopenstars.gg\n131 daysRegistered 2026-05-13\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tskins.com\n25.1 yearsRegistered 2001-08-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skins.com\n25.1 yearsRegistered 2001-08-08\nRDAP ↗ · skins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\twhite.market\n9.6 yearsRegistered 2017-03-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwhite.market\n9.6 yearsRegistered 2017-03-01\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tmoon.market\n7.6 yearsRegistered 2019-02-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmoon.market\n7.6 yearsRegistered 2019-02-27\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tcsfloat.com\n5.2 yearsRegistered 2021-07-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgofloat.com\n11.0 yearsRegistered 2015-09-29\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tskin.land\n4.7 yearsRegistered 2022-01-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skin.land\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\thaloskins.com\n2.8 yearsRegistered 2023-12-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhaloskins.com\n2.8 yearsRegistered 2023-12-10\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCorporate Market\n\tbuff.163.com\n29.0 yearsRegistered 1997-09-15\nRDAP ↗ · 163.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\nbuff.163.com\n29.0 yearsRegistered 1997-09-15\nRDAP ↗ · 163.com (parent)\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\tmarket.csgo.com\n26.6 yearsRegistered 2000-02-07\nRDAP ↗ · csgo.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\ndota2.net\n14.9 yearsRegistered 2011-10-29\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRegulated Market\n\tskinport.com\n8.0 yearsRegistered 2018-09-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinport.app\n6.3 yearsRegistered 2020-06-20\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMarketplace/Swap\n\tskinflow.gg\n3.8 yearsRegistered 2022-11-26\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinflow.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tskin.place\n6.0 yearsRegistered 2020-09-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skin.place\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tskinsmonkey.com\n5.7 yearsRegistered 2021-01-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinsmonkey.com\n5.7 yearsRegistered 2021-01-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCorporate Market\n\tskinbaron.de\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinbaron.com\n10.7 yearsRegistered 2015-12-22\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Market\n\trust.tm\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\ndota2.net\n14.9 yearsRegistered 2011-10-29\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tpirateswap.com\n6.0 yearsRegistered 2020-09-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nlogin.pirateswap.com\n6.0 yearsRegistered 2020-09-22\nRDAP ↗ · pirateswap.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Marketplace\n\tmannco.store\n8.6 yearsRegistered 2018-03-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmannco.store\n8.6 yearsRegistered 2018-03-02\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tskinswap.com\n9.9 yearsRegistered 2016-11-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinswap.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\texeskins.com\n2.1 yearsRegistered 2024-08-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nexeskins.com\n2.1 yearsRegistered 2024-08-14\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tbalticskins.com\n153 daysRegistered 2026-04-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nbalticskins.com\n153 daysRegistered 2026-04-21\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tcs.trade\n8.9 yearsRegistered 2017-11-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncs.trade\n8.9 yearsRegistered 2017-11-14\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\trapidskins.com\n4.5 yearsRegistered 2022-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.rapidskins.com\n4.5 yearsRegistered 2022-03-11\nRDAP ↗ · rapidskins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\ttradeit.gg\n9.1 yearsRegistered 2017-08-21\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nconnect-tradeit.com\n4.6 yearsRegistered 2022-02-23\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\t49skins.com\n3.4 yearsRegistered 2023-04-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.49skins.com\n3.4 yearsRegistered 2023-04-19\nRDAP ↗ · 49skins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tskinvault.gg\n3.4 yearsRegistered 2023-05-06\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinvault.gg\n3.4 yearsRegistered 2023-05-06\nIP2WHOIS ↗ · skinvault.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Trading\n\taim.market\n3.3 yearsRegistered 2023-05-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\naim.market\n3.3 yearsRegistered 2023-05-22\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Sell Portal\n\tskinout.gg\n5.6 yearsRegistered 2021-02-27\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skinout.gg\n5.6 yearsRegistered 2021-02-27\nIP2WHOIS ↗ · skinout.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Trading\n\tntskins.com\n230 daysRegistered 2026-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nntskins.com\n230 daysRegistered 2026-02-03\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Portal\n\tgamerpay.gg\n6.0 yearsRegistered 2020-10-02\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ngamerpay.gg\n6.0 yearsRegistered 2020-10-02\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Scrap Swap\n\tscrap.tf\n14.0 yearsRegistered 2012-09-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nscrap.tf\n14.0 yearsRegistered 2012-09-03\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Cashout\n\tmarketplace.tf\n14.0 yearsRegistered 2012-09-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmarketplace.tf\n14.0 yearsRegistered 2012-09-19\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Cashout\n\tskins.cash\n10.5 yearsRegistered 2016-03-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinscash.live\n6.8 yearsRegistered 2019-12-05\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgo.net\n14.2 yearsRegistered 2012-07-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncn2.easylot.net\n10.0 yearsRegistered 2016-09-03\nRDAP ↗ · easylot.net (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCommunity Hub\n\tcybershoke.net\n6.8 yearsRegistered 2019-11-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.cybershoke.net\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMatchmaker Hub\n\tfastcup.net\n14.6 yearsRegistered 2012-02-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.fastcup.net\n14.6 yearsRegistered 2012-02-16\nRDAP ↗ · fastcup.net (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Analytics\n\tleetify.com\n7.6 yearsRegistered 2019-03-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nleetify.com\n7.6 yearsRegistered 2019-03-01\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Analytics\n\tscope.gg\n7.8 yearsRegistered 2018-12-10\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nscope.gg\n7.8 yearsRegistered 2018-12-10\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tools\n\ttradeupspy.com\n6.5 yearsRegistered 2020-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.tradeupspy.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMarketplace\n\tcs.deals\n9.8 yearsRegistered 2016-12-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.cs.deals\n9.8 yearsRegistered 2016-12-03\nRDAP ↗ · cs.deals (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Price DB\n\tpricempire.com\n6.6 yearsRegistered 2020-01-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\npricempire.com\n6.6 yearsRegistered 2020-01-30\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Blackmarket\n\tFSB Market\n7.2 yearsRegistered 2019-07-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nFSB Market\n7.2 yearsRegistered 2019-07-27\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nReady-Account Hub\n\tz2u.com\n26.9 yearsRegistered 1999-11-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwww.z2u.com\n26.9 yearsRegistered 1999-11-10\nRDAP ↗ · z2u.com (parent)\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Gambling\n\tcsgoroll.com\n11.6 yearsRegistered 2015-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwww.csgoroll.com\nRegistry date unavailableRegistry date unavailable\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\trollbit.com\n11.9 yearsRegistered 2014-11-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrbsnin.com\n3 daysRegistered 2026-09-18\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nLicenced Casino\n\t500.casino\n5.9 yearsRegistered 2020-11-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette/Slots\n\tcsgobig.com\n11.4 yearsRegistered 2015-04-12\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcasedrop.com\n14.8 yearsRegistered 2011-12-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\tbanditcamp.com\n12.2 yearsRegistered 2014-06-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tskinbox.com\n18.8 yearsRegistered 2007-12-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\ttastydrop.com\n6.1 yearsRegistered 2020-08-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette Casino\n\tcsgopolygon.gg\n6.5 yearsRegistered 2020-03-28\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tmagicdrop.ru\n10.3 yearsRegistered 2016-05-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nDice Casino\n\tcsdice.com\n3.8 yearsRegistered 2022-11-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUpgrader Casino\n\tskinodds.com\n1.2 yearsRegistered 2025-06-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgowin.com\n12.0 yearsRegistered 2014-09-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrash Casino\n\tcsgorun.net\n7.3 yearsRegistered 2019-06-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\topenskins.com\n3.6 yearsRegistered 2023-02-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Gambling\n\trustbet.com\n7.6 yearsRegistered 2019-02-07\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgomagic.com\n9.4 yearsRegistered 2017-05-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUpgrader/Contract\n\tcsgobounty.com\n11.5 yearsRegistered 2015-03-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tezskins.com\n27.5 yearsRegistered 1999-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\trustcases.com\n7.2 yearsRegistered 2019-06-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgoreaper.com\n11.1 yearsRegistered 2015-08-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgocases.com\n12.3 yearsRegistered 2014-06-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Upgrader\n\tcsgo-skins.com\n11.2 yearsRegistered 2015-07-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgonet.com\n8.8 yearsRegistered 2017-12-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\twtfskins.com\n9.0 yearsRegistered 2017-10-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Casino\n\tflamecases.com\n10.0 yearsRegistered 2016-09-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tgamedom.com\n11.7 yearsRegistered 2015-01-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Battles\n\tskin.club\n9.0 yearsRegistered 2017-09-04\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsc-auth.net\n7.5 yearsRegistered 2019-04-02\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tdaddyskins.com\n9.9 yearsRegistered 2016-10-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Gambling\n\trustix.gg\n1.7 yearsRegistered 2025-01-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Upgrade\n\tskins.club\n4.2 yearsRegistered 2022-07-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgohouse.org\n146 daysRegistered 2026-04-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskinrave.net\n216 daysRegistered 2026-02-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tbloodycase.gg\n19 daysRegistered 2026-09-02\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nClicker/Upgrade\n\tcsgoclicker.com\n8.3 yearsRegistered 2018-05-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustbet.gg\n4.0 yearsRegistered 2022-09-30\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcs-drop.com\n262 daysRegistered 2026-01-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\thellstore.net\n11.7 yearsRegistered 2015-01-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustloot.com\n354 daysRegistered 2025-10-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgo-case.com\n10.3 yearsRegistered 2016-05-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgogem.com\n9.9 yearsRegistered 2016-10-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\trainbet.com\n8.8 yearsRegistered 2017-11-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nservices.rainbet.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustclash.com\n5.4 yearsRegistered 2021-05-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrash Casino\n\t12cs.fail\n181 daysRegistered 2026-03-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\twww.tf2easy.com\n6.3 yearsRegistered 2020-06-02\nRDAP ↗ · tf2easy.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2blaze.com\n7.6 yearsRegistered 2019-01-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tshuffle.com\n30.1 yearsRegistered 1996-07-31\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tbuff.market\n5.9 yearsRegistered 2020-10-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tavan.market\n8.3 yearsRegistered 2018-05-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Engine\n\tcs.money\n11.0 yearsRegistered 2015-09-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.dota.trade\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tuuskins.com\n2.6 yearsRegistered 2024-01-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Market\n\tyoupin898.com\n6.1 yearsRegistered 2020-08-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tc5game.com\n10.5 yearsRegistered 2016-03-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\twaxpeer.com\n7.3 yearsRegistered 2019-05-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwaxpeer.com\n7.3 yearsRegistered 2019-05-20\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBot Trading\n\tcs.money\n11.0 yearsRegistered 2015-09-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.dota.trade\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUS Marketplace\n\tdmarket.com\n30.2 yearsRegistered 1996-07-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nOfficial Market\n\tsteamcommunity.com/market\n20.3 yearsRegistered 2006-05-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNot an external login site2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Platform\n\tlootfarm.com\n11.9 yearsRegistered 2014-10-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Market\n\trustskins.com\n7.6 yearsRegistered 2019-01-31\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tkrakatoa.com\n26.4 yearsRegistered 2000-05-15\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\tshadowpay.com\n10.1 yearsRegistered 2016-08-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nChinese Powerhouse\n\tigxe.cn\n15.0 yearsRegistered 2011-09-06\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAutomated Swap\n\tswap.gg\n9.6 yearsRegistered 2017-01-29\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCash-out Portal\n\tbitskins.com\n11.2 yearsRegistered 2015-07-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Automation\n\ttf2mart.com\n1.1 yearsRegistered 2025-08-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Auctions\n\tskinbid.com\n10.2 yearsRegistered 2016-06-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Rental\n\tlootbear.com\n8.7 yearsRegistered 2018-01-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Valuation\n\tbackpack.tf\n14.4 yearsRegistered 2012-05-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Botnet\n\tstntrading.eu\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Cashout\n\tskinwallet.com\n18.0 yearsRegistered 2008-09-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nDota 2 Market\n\tdota2market.com\n12.2 yearsRegistered 2014-07-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nServer Network\n\txplay.gg\n5.3 yearsRegistered 2021-06-13\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMatchmaking Portal\n\tesportal.com\n26.8 yearsRegistered 1999-12-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nLATAM Hub\n\tgamersclub.com.br\n11.2 yearsRegistered 2015-06-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tools\n\tepidemic.gg\n4.9 yearsRegistered 2021-11-03\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tcs2stash.com\n3.5 yearsRegistered 2023-03-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tcsgoskins.gg\n6.8 yearsRegistered 2019-12-21\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tsteamanalyst.com\n12.6 yearsRegistered 2014-02-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Exchange\n\tsteamcardexchange.net\n13.3 yearsRegistered 2013-05-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tracker\n\tdotabuff.com\n14.2 yearsRegistered 2012-06-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tracker\n\ttracker.gg\n8.9 yearsRegistered 2017-10-12\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Exchange\n\tfunpay.com\n17.0 yearsRegistered 2009-09-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nGrey Market\n\tplayerauctions.com\n26.3 yearsRegistered 2000-06-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Portal\n\teldorado.gg\n8.0 yearsRegistered 2018-09-12\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Key Market\n\tg2a.com\n24.8 yearsRegistered 2001-12-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Key Market\n\tkinguin.net\n16.8 yearsRegistered 2009-12-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nVirtual Services\n\tg2g.com\n31.1 yearsRegistered 1995-08-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Broker\n\tplayerup.com\n19.3 yearsRegistered 2007-05-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfhub.net\n2.7 yearsRegistered 2023-12-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfaccounts.com\n5.3 yearsRegistered 2021-05-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Shop\n\tbuycsgorank.com\n6.2 yearsRegistered 2020-07-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tcsgosmurfkings.com\n9.3 yearsRegistered 2017-06-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfstore.co\n8.6 yearsRegistered 2018-03-03\nWHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlvlup.com\n9.9 yearsRegistered 2016-11-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlevels.com\n10.6 yearsRegistered 2016-02-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tlevelsteam.com\n79 daysRegistered 2026-07-04\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlevelu.com\n6.0 yearsRegistered 2020-09-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\teloking.com\n12.2 yearsRegistered 2014-07-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\tboosteria.org\n11.9 yearsRegistered 2014-10-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tovergear.com\n14.4 yearsRegistered 2012-04-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tblazingboost.com\n14.2 yearsRegistered 2012-06-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\tdota2boost.com\n2.9 yearsRegistered 2023-10-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tbuyboost.com\n22.4 yearsRegistered 2004-04-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\nEl argumento de la investigaciónNorma seleccionada / análisis y comentarios+\nCarga de la prueba\n\nLa investigación pone de relieve la discrepancia entre las restricciones al uso comercial y los servicios aquí registrados. Clasifica cada actividad y comprueba si existe algún permiso expreso antes de considerarla un incumplimiento contractual. Las tarifas del Mercado Comunitario no se aplican a todas las transacciones comerciales externas.\n\nQué es y qué no es un registro etiquetado\n\nUn registro se marca cuando el expediente contiene una observación fechada que hace que la plataforma entre en el ámbito de aplicación de la cláusula tal y como está redactada. Una marca no equivale a una infracción confirmada, y no se ha presentado en el registro ningún permiso expreso Valve para ninguna de las plataformas aquí enumeradas. Cuando una plataforma cuenta con una autorización, su publicación resuelve la entrada.\n\nFuentes y metodologíaEstimaciones, definiciones y ámbito de aplicación+\n\nLas cifras anteriores se refieren a la regla seleccionada. Los tipos de registros agrupan cada plataforma una sola vez; las etiquetas completas aparecen en los detalles de la plataforma. La búsqueda y los filtros se aplican dentro de esa regla. Las fechas de registro proceden de la instantánea guardada de RDAP / WHOIS. Los subdominios utilizan la fecha de creación del dominio principal. La antigüedad por sí sola no establece un funcionamiento continuo ni una ruta de autenticación. Los nombres de host de autenticación actuales proceden de solicitudes OpenID guardadas, con una marca de tiempo UTC; las comprobaciones sin resolver no reutilizan etiquetas heredadas. El observador se detiene antes del inicio de sesión en Steam y no comprueba el estado del filtro de enlaces de Steam. Descargar observaciones de la ruta ↗ Descargar los resultados del registro ↗\n\nExplora el archivo fuente ↗\nApéndice G — De un modelo de denegación al expediente correspondiente\nManual de actuación DSAR: solicitar las pruebas\n\nRecurre al artículo 15 del RGPD para solicitar los datos personales relacionados con la creación de claves API, la recuperación de cuentas y el acceso al servicio de asistencia. Un registro conservado permite comprobar quién inició una acción y en qué se basó la plataforma.\n\n01\nConserva tu cronología.\n\nGuarda los avisos de la cuenta, los tickets, los identificadores de las transacciones y las fechas en UTC. Protege la cuenta y revisa las opciones de recuperación aplicables al juego y a la transacción.\n\nSteam Información sobre protección comercial ↗\n02\nSolicita los datos que se han conservado.\n\nSolicita las marcas de tiempo, las direcciones IP de origen, los eventos clave del ciclo de vida, las confirmaciones de seguridad y las acciones de recuperación relacionadas con la cuenta. Incluye los eventos de acceso al servicio de asistencia y los destinatarios cuando esos datos te conciernan.\n\n03\nGuarda el albarán de entrega.\n\nUtiliza el canal de contacto de privacidad de Valve. El plazo de respuesta habitual es de un mes; si fuera necesario prorrogarlo hasta dos meses más, deberá justificarse dicha prórroga en el plazo de ese primer mes.\n\nValve vía de contacto sobre privacidad ↗ archivado 2026-09-21 ↗\n04\nCompara la respuesta.\n\nCompara los registros con tu cronología. Pregunta por los motivos de las omisiones y, si es necesario, recurre a la vía de reclamación ante la autoridad supervisora. Conserva la respuesta tal y como la hayas recibido.\n\nÁmbito de aplicación / Artículo 15\n\nEl derecho de acceso abarca los datos personales conservados, incluidos los que figuran en los registros. No garantiza el acceso a todos los documentos internos, registros reconstruidos ni datos sin censurar sobre terceras personas. Solicita una copia legible y que te expliquen los motivos de cualquier restricción.\n\nDirectrices del EDPB sobre el acceso, apartados 2 y 4 a 6 ↗ · Artículos 12, 15 y 77 del RGPD ↗ archivado 2026-09-20 ↗\n\nSolicitud de acceso del interesadoRGPD / Artículo 15\nSeguridad de la cuenta y registros de acceso\n\nSustituye los campos entre corchetes antes de enviar el formulario.\n\nTo: Valve Privacy Team\nSubject: Article 15 GDPR request — account security records\n\nAccount / SteamID: [YOUR ACCOUNT IDENTIFIER]\nRelevant period (UTC): [START] to [END]\nRelated support tickets: [TICKET REFERENCES]\n\nI request a copy of the personal data concerning me that you retain for this period, including:\n\n1. API-key registration, confirmation, use and revocation events, with available timestamps, source IP addresses, registered domains, device or user-agent information and non-secret key identifiers.\n\n2. Recorded account-recovery actions, password/email/phone changes, Steam Guard removals or resets, confirmation events and the account-related evidence relied on to authorize those actions.\n\n3. Personal data in support-access and administrative-action logs concerning my account, including available dates, purposes, actions and the support entity involved, subject to applicable rights of others.\n\n4. Account-related records used to determine any sanction, and available records of my complaints, reviews and responses.\n\nPlease also provide the applicable processing purposes, categories, recipients, retention periods or criteria, and available information about sources where data were not obtained from me.\n\nWhere processing relies on my consent, please provide the retained record of the consent relied upon and the wording presented at that time.\n\nPlease provide an intelligible electronic copy with time zones and field definitions. Please do not include active credentials or secret tokens. If any requested data are not held, please say so. For any withheld data, please identify the scope and legal basis of the restriction and provide the remainder.\n\nPlease acknowledge receipt and respond within the applicable Article 12 period, explaining any necessary extension. I also ask you to preserve relevant existing records while this request is handled.\n\nName: [YOUR NAME]\nDate: [DATE]\nQué puede ofrecer una dirección IP de un centro de datos\nUna discrepancia es un indicio que hay que investigar.\n\nUna solicitud de clave API procedente de la red de un centro de datos, como en el ejemplo del proveedor de alojamiento web planteado en esta investigación, puede resultar relevante si se compara con los registros de inicio de sesión, las confirmaciones y la cronología del usuario. Una dirección IP por sí sola no identifica al autor ni anula automáticamente todas las defensas. La prueba de que un autor malintencionado haya facilitado el consentimiento registrado podría poner en duda la validez de dicho consentimiento; otras bases jurídicas y cuestiones de responsabilidad requieren un análisis por separado.\n\nConsulta la denuncia archivada sobre la prohibición y el RGPD →\nApéndice H — Análisis del archivo de Wayback Machine · Estadísticas de asistencia publicadas\nVolumen de asistencia técnica. Tiempos de respuesta publicados.\nContexto y límites de la fuente\n\nValve publica estadísticas diarias de asistencia en store.steampowered.com/stats/support. Los archivos de Wayback Machine conservan instantáneas históricas de esta página desde 2018 hasta 2026. La relación entre el volumen y el número de empleados que se desprende de estas cifras no es compatible con una revisión humana de cada ticket en los tiempos de respuesta publicados.\n\nCompara las cifras de apoyo archivadas de Valve en las instantáneas guardadas. La metodología explica qué es lo que esas cifras pueden y no pueden medir.\n\nVolumen frente al tiempo de respuesta publicado (2018 → 2026)\nDos colas en un servicio de atención al cliente, según se desprende de 21 capturas archivadas.\n\nValve publica las cifras de asistencia en directo en store.steampowered.com/stats/support. Cada punto que aparece a continuación corresponde al límite inferior Valve tal y como figuraba en esa página el día en que Internet Archive la capturó, y no es una estimación nuestra. Ambas series representan la misma medida en la misma unidad, por lo que deben situarse en un mismo eje y pueden compararse directamente entre sí.\n\nSolicitudes de reembolso — dinero Valve disponibleSeguridad y recuperación de la cuenta — la cuenta que has perdido\n0 h\n2 h\n4 h\n6 h\n8 h\n10 h\nno captures · 38 months\n2019\n2020\n2021\n2022\n2023\n2024\n2025\n2026\n8 h 44 m\naccount recovery\n52 m\nrefunds\n15 m — one capture only\n49-55 minEl límite inferior del reembolso en cada captura desde febrero de 2018 hasta agosto de 2026. A lo largo de ocho años y medio, varía en menos de seis minutos, mientras que el volumen diario de reembolsos varía en un factor de nueve.\n2,4 h → 8,7 hEl límite inferior de la recuperación de cuentas se sitúa en torno a las 2,4 horas en todos los registros hasta diciembre de 2022, salvo en uno. En los tres registros de 2026, Valve publica 10,9 h, 5,8 h y 8,7 h.\n×2,8 → ×13Cuánto más lenta es la recuperación que los reembolsos, según las propias cifras publicadas por Valve. Se mantiene estable durante cinco años y luego la diferencia aumenta: la cola que se ha ralentizado es aquella en la que es el usuario, y no Valve, quien corre con los gastos.\n\nFuente: 21 capturas de Wayback Machine de store.steampowered.com/stats/support, de 2018-02-03 a 2026-08-10; extracción en VALVE_EVIDENCE_PACK/databases/steam_support_stats_history.json. Lee los límites junto con las cifras: el gráfico representa el inferior límite del rango de Valve impresiones. El límite superior publicado es peor en ambos casos: los reembolsos oscilaron entre 1,5 horas y 1,5 días, y la recuperación, entre 7,0 horas y 3,6 días. Se archivaron dos capturas en una edición localizada de la misma página Valve — 2018-11-03 en checo, 2020-03-25 en francés — y están marcadas como (cs) y (fr) en la tabla; sus cifras aparecen aquí con las palabras de las unidades traducidas y los números tal y como se publicaron, y las cadenas de texto originales se conservan en el archivo de extracción. Cada captura publicó un tiempo de respuesta para ambas colas, y ningún punto de ninguna de las líneas está interpolado. La única cifra de recuperación de 15 minutos, 2020-10-21, está señalada en el gráfico y se ha dejado tal cual: aparece solo en una captura y ninguna otra captura se encuentra dentro de un orden de magnitud de ella. No existe ningún registro entre 2022-12-08 y 2026-02-01; ese vacío de 38 meses en el registro aparece sombreado y no se traza ninguna línea a través de él. Estas cifras describen los tiempos de respuesta publicados. No muestran lo que ocurre en el interior de un ticket, y Valve no ha publicado ninguna cifra de personal con la que compararlas.\n\nAbrir cada captura como una tabla\nTodas las capturas archivadas, tal y como se publicaron\nCaptura\tReembolsos / día\tRespuesta sobre el reembolso\tRecuperación / día\tRespuesta de recuperación\n2018-02-03\t98,788\tDe 50,12 minutos a 1,52 horas\t25,662\tDe 2,51 horas a 1,80 días\n2018-05-07\t60,494\tDe 53,83 minutos a 1,47 días\t24,226\tDe 2,45 horas a 2,22 días\n2018-08-02\t69,084\tDe 50,27 minutos a 1,59 horas\t28,953\tDe 2,44 horas a 22,17 horas\n2018-11-03 (cs)\t63,410\tDe 49,28 minutos a 1,54 horas\t33,910\tDe 2,42 horas a 1,31 días\n2019-02-01\t76,305\tDe 50,13 minutos a 1,52 horas\t35,164\tDe 2,44 horas a 2,04 días\n2019-05-18\t78,951\tDe 51,03 minutos a 3,12 horas\t27,514\tDe 2,46 horas a 20,39 horas\n2019-09-07\t78,941\tDe 50,65 minutos a 1,66 horas\t28,812\tDe 2,42 horas a 13,59 horas\n2019-12-13\t69,589\tDe 50,77 minutos a 1,55 horas\t25,322\tDe 2,45 horas a 1,13 días\n2020-03-25 (fr)\t139,278\tDe 49,45 minutos a 1,53 horas\t32,302\tDe 2,48 horas a 3,62 días\n2020-06-26\t278,504\tDe 48,98 minutos a 2,29 horas\t20,343\tDe 2,39 horas a 6,99 horas\n2020-10-21\t107,633\tDe 50,80 minutos a 1,54 horas\t20,688\tDe 15,33 minutos a 8,62 horas\n2021-03-20\t158,956\tDe 50,80 minutos a 1,64 horas\t25,760\tDe 2,34 horas a 11,62 horas\n2021-06-26\t547,907\tDe 51,93 minutos a 6,73 horas\t29,728\tDe 2,40 horas a 15,63 horas\n2021-10-10\t170,103\tDe 51,88 minutos a 3,25 horas\t23,989\tDe las 2,39 horas a las 13,05 horas\n2022-01-31\t354,386\tDe 53,65 minutos a 8,09 horas\t24,391\tDe 2,42 horas a 15,29 horas\n2022-05-09\t172,555\tDe 51,83 minutos a 1,65 horas\t23,289\tDe 2,41 horas a 16,90 horas\n2022-09-05\t153,453\tDe 53,67 minutos a 4,15 horas\t23,594\tDe 2,45 horas a 1,22 días\n2022-12-08\t181,075\tDe 54,83 minutos a 6,67 horas\t27,111\tDe 2,46 horas a 18,89 horas\n2026-02-01\t317,762\tDe 50,30 minutos a 1,52 horas\t47,197\tDe las 10.91 horas a las 21.30 horas\n2026-05-09\t246,776\tDe 50,12 minutos a 1,52 horas\t35,264\tDe 5,81 horas a 15,60 horas\n2026-08-10\t373,244\tDe 52,05 minutos a 2,07 horas\t45,319\tDe 8,73 horas a 16,52 horas\nOBSERVACIÓN CLAVE:\nA lo largo de 21 capturas de Wayback En el intervalo comprendido entre 2018-02-03 y 2026-08-10, las solicitudes diarias de reembolso oscilaron entre 60,494 (mayo de 2018) hasta 547,907 (Junio de 2021) — un 9,1× de diferencial. La cifra de 2026 es 373,244 (+278% respecto a la de febrero de 2018).\nA lo largo de esos mismos nueve años, el límite inferior publicado para el tiempo de respuesta de las devoluciones nunca se alejó de un 49–55 minutos banda: un movimiento total de menos de seis minutos, mientras que la carga de trabajo subyacente se multiplicó por nueve.\nSi una persona dedicara tan solo 5 segundos a leer cada ticket, procesar 373,244 tickets al día (cifra actual) le llevaría 22 agentes que trabajan las 24 horas del día, los 7 días de la semana solo para abrirlas y cerrarlas; en su momento álgido (547,907, junio de 2021) esa cifra asciende a 32.\nSi el tiempo de respuesta publicado reflejara el tiempo de tramitación por ticket (aprox. 52 min/ticket), la plantilla simultánea necesaria sería del orden de 13,500 agentes al volumen actual y ~20,000 en el pico. No se ha encontrado ninguna cifra contrastada sobre el número de empleados de Valve; por lo tanto, aquí no se ha tenido en cuenta.\nA continuación: la relación entre volumen y número de empleados no es compatible con una revisión humana de cada ticket en los tiempos de respuesta publicados. Las cifras concuerdan con una primera revisión en gran medida automatizada; no se ha publicado qué proporción se somete a revisión humana.\nPor qué es importante para el cumplimiento del RGPD\n\nEl artículo 22 del RGPD prohíbe la toma de decisiones individuales exclusivamente automatizadas que tengan efectos jurídicos significativos, sin que se conceda el derecho a una revisión humana previa solicitud. Si las decisiones de asistencia (cierre de tickets, acciones en la cuenta, denegación de solicitudes de datos) se toman íntegramente mediante scripts automatizados, cada una de esas decisiones que «afecte de manera significativa» al usuario podría infringir el artículo 22.\n\nEntrada HT-2YBP-F7JP-D4VB (Apartado 18) se cerró al cabo de tres días con una remisión tipo y sin que se abordara el fundamento jurídico citado. A partir del expediente no se puede determinar si alguien lo revisó; esa es una cuestión que la autoridad de control puede plantear a Valve en virtud del artículo 22 y del artículo 15, apartado 1, letra h).\n\nFuente: instantáneas de Wayback Machine de store.steampowered.com/stats/support (2018-02-03, 2021-06-26, 2026-08-10) — datos extraídos a VALVE_EVIDENCE_PACK/databases/steam_support_stats_history.json (21 instantáneas, 2018-2026). Nota: el tiempo de respuesta de «~52 min» es el límite inferior de la categoría de reembolsos; la respuesta en materia de seguridad de la cuenta osciló entre 2,4 y 16,5 horas en las mismas instantáneas. 2021-06-26 es el máximo histórico (547,907 solicitudes de reembolso), no un punto medio monótono: el volumen se multiplicó por ~6 entre 2020 y 2021, luego descendió parcialmente antes de recuperarse hasta alcanzar las 373 000 en 2026.\nApéndice I — Alcance del conjunto de datos · recuentos que pueden reproducirse\nCuenta los registros. Comprueba el ámbito.\nContexto y límites de la fuente\n\nCuenta los registros y, a continuación, comprueba las afirmaciones: todas las cifras que aparecen a continuación pueden volver a calcularse a partir de los archivos publicados.\n\nExamina los conjuntos de datos subyacentes, reproduce los recuentos y distingue las filas de origen de los incidentes únicos.\n\nEl archivo CSV principal contiene 40,448 filas. De ellos, 36,516 proceden del canal de phishing «Discord-AntiScam». El resto 3,932 Las filas abarcan GitHub, revisiones, resultados de búsqueda, contenido de foros y otras fuentes, lo que ofrece un índice exhaustivo de los temas planteados por la comunidad y los informes de seguridad.\n\nEn ese archivo CSV, 1,690 filas están clasificadas bajo la etiqueta de colección «Vulnerabilidades de seguridad sin parchear», que recoge incidencias históricas de los usuarios y divulgaciones de vulnerabilidades. El seguimiento de estos informes implica revisar la cronología específica de cada versión y el historial público de parches de cada hilo.\n\nEl archivo de búsqueda de registros 16,319 es una versión independiente y seleccionada, con su propio manifiesto, diseñada para la exploración local precisa de reclamaciones de usuarios e informes de incidentes específicos.\n\nPara crear un registro de auditoría fiable, cada registro comunicado por los usuarios debe verificarse cotejándolo con los plazos de compilación documentados y los registros históricos de parches.\n\nLos registros de la colección de la Parte II, por separado 231,829 identificadores únicos de anuncios, incluyendo 33,509 en la categoría de registro automatizado y 198,320 marcado como transferencias no verificadas. El SHA-256 del archivo de entrada coincide con la medición conservada. Estas cifras describen los intentos de publicación y las transferencias observadas, más que los valores de las transacciones finalizadas o los totales de robos verificados, lo que pone de relieve la necesidad de disponer de registros primarios de la plataforma para medir el impacto económico exacto. Lista de medidas y hash ↗\n\nCSV avanzado ↗ · Índice del archivo con función de búsqueda ↗ · Revisar los registros originales ↗\n\nApéndice J — Acerca de esta investigación\nValve no publica ningún historial de medidas coercitivas. Hemos construido uno.\n\nIndependiente. Sin ánimo de lucro. Elaborado exclusivamente a partir de datos públicos. Presentado a las autoridades reguladoras.\n\n88.97%La flota de vehículos autónomos no se ve afectada: no hay prohibición de ningún tipo\n67.77%de los 51,732 estafadores condenados que quedan en libertad\n$26.8M+Límite mínimo de gasto en tienda para la flota no limitada\n3.6%dominios de juegos de azar bloqueados por el filtro de enlaces de Valve\n8 añosde incidentes de seguridad registrados\n\nDe qué se trata. Un informe forense sobre la plataforma Steam de Valve Corporation: su historial de cumplimiento normativo, su economía basada en la acumulación de tarjetas, su marco jurídico y la infraestructura de autenticación que utilizan los operadores de juegos de azar a través del relé OpenID propio de Steam. Todas las cifras pueden verificarse a partir de dos fuentes: la propia API pública de Valve y los conjuntos de datos publicados junto con esta investigación.\n\nA quién va dirigido. Las autoridades reguladoras con competencia sobre Valve —la autoridad de control del RGPD en los Países Bajos, la FinCEN, la SEC, el coordinador de servicios digitales de la DSA, la UOKiK y cualquier organismo encargado de hacer cumplir la ley que investigue los flujos financieros vinculados a Steam—. También para periodistas, investigadores y cualquier usuario al que se le haya bloqueado la cuenta de forma permanente, se le haya denegado un reembolso o se le haya sustraído el inventario, y al que se le haya comunicado que no existe posibilidad de recurso.\n\nLa única exigencia. Valve conserva estos datos con total fidelidad —incluidos los motivos de la prohibición, el espacio de identificación completo y en tiempo real—. Es capaz de ejecutar cualquier consulta de este expediente en cuestión de segundos y ha decidido no publicar nada de ello. La pregunta para cualquier autoridad competente es sencilla: ¿Por qué no?\n\nLo que los autores no afirman. Durante este trabajo no se completó ningún inicio de sesión en Steam en ninguna plataforma de terceros. Una URL de OpenID facilitada establece los parámetros de la solicitud, no un inicio de sesión completado. El hecho de que exista un dominio registrable independiente no constituye, por sí solo, prueba de evasión. Las fechas de registro son límites mínimos respecto a cuándo podría haber aparecido por primera vez un host en una solicitud de OpenID; no demuestran un uso continuado. Los autores no afirman lo que Valve sabía o pretendía: cada afirmación sobre Valve está vinculada a un documento público con fecha o a una observación con fecha. Cuando no ha sido posible respaldar una afirmación con un documento fuente, se ha eliminado.\n\nQuiénes somos\n\nPhishDestroy — Investigadores independientes. Sin afiliación alguna con Valve Corporation ni con ninguna de las plataformas aquí mencionadas. Se utilizó una cuenta Steam con el único fin de documentar la solicitud en virtud del RGPD a la que se hace referencia en la sección 18.\n\nAviso legal\n\nInvestigación de interés público, sin ánimo de lucro y descentralizada. Todos los datos se facilitan «tal cual», sin garantía alguna. Esta publicación no constituye una resolución judicial.\n\nDE DOMINIO PÚBLICO\nLicencias\n\nTodos los derechos cedidos a la humanidad. Se permite reproducir, adaptar y publicar sin necesidad de citar la fuente. Acceso desde la región de la OFAC: prohibido. Licencia completa y aviso legal →",
        "headings": [
          {
            "level": 2,
            "id": "briefing-heading",
            "text": "La norma. El récord. Las preguntas sin respuesta."
          },
          {
            "level": 2,
            "id": null,
            "text": "Carta abierta a la Comisión de Juegos de Azar del Estado de Washington"
          },
          {
            "level": 3,
            "id": "wsgc-public-address-title",
            "text": "Diez días se convirtieron en diez años.Vuelve a abrir el expediente."
          },
          {
            "level": 2,
            "id": null,
            "text": "El sitio está bloqueado. La ruta de inicio de sesión no lo está."
          },
          {
            "level": 3,
            "id": null,
            "text": "Figura 3.1 — Las dos rutas, representadas gráficamente."
          },
          {
            "level": 3,
            "id": null,
            "text": "La trampa del panorama general: el filtro de enlaces es una farsa de cumplimiento normativo, no un escudo"
          },
          {
            "level": 3,
            "id": null,
            "text": "Si se bloquea el dominio principal y no se bloquea el host de autenticación, la ruta de inicio de sesión queda abierta, y así permanece durante años."
          },
          {
            "level": 3,
            "id": null,
            "text": "Antecedentes: qué es Steam y por qué es importante en este contexto"
          },
          {
            "level": 3,
            "id": null,
            "text": "Lo que hizo Valve: el bloqueo de dominios"
          },
          {
            "level": 3,
            "id": null,
            "text": "Qué es un dominio proxy"
          },
          {
            "level": 3,
            "id": null,
            "text": "El punto crítico: el servidor de autenticación se envía a Steam en cada solicitud"
          },
          {
            "level": 3,
            "id": null,
            "text": "Lo que esto demuestra"
          },
          {
            "level": 3,
            "id": null,
            "text": "Dentro de Steam, la lista de Valve es la única lista."
          },
          {
            "level": 3,
            "id": null,
            "text": "Desactivación de la protección del filtro de enlaces"
          },
          {
            "level": 3,
            "id": null,
            "text": "El navegador web Big Picture filtra cookies de inicio de sesión y revela información confidencial (lo que podría dar lugar a la apropiación de cuentas)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Qué significa esto para un menor que tiene instalado un antivirus"
          },
          {
            "level": 3,
            "id": null,
            "text": "La antigüedad del dominio.Fecha de la observación."
          },
          {
            "level": 2,
            "id": null,
            "text": "Se ha cerrado un punto final. El seguimiento público ha perdido una clave."
          },
          {
            "level": 3,
            "id": null,
            "text": "La era anterior al apagón"
          },
          {
            "level": 3,
            "id": null,
            "text": "Tras el cambio"
          },
          {
            "level": 2,
            "id": null,
            "text": "Una sesión. Más acceso del que el usuario percibe."
          },
          {
            "level": 3,
            "id": null,
            "text": "1. Autenticación de nivel superior insuficiente"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. Ausencia del principio del mínimo privilegio"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. Fallos en la gestión de sesiones"
          },
          {
            "level": 3,
            "id": null,
            "text": "4. El bloqueo a nivel de dominio de los servidores de autenticación era técnicamente viable"
          },
          {
            "level": 3,
            "id": "integration-paradox-title",
            "text": "Valve se compila siguiendo estas reglas todos los días. En este caso, no se ha compilado según ellas."
          },
          {
            "level": 4,
            "id": null,
            "text": "Ámbitos detallados de GitHub frente a Valve Steam API web"
          },
          {
            "level": 2,
            "id": null,
            "text": "Simulador interactivo de vulnerabilidades y secuestros de sistemas"
          },
          {
            "level": 2,
            "id": null,
            "text": "Los puntos finales que hay detrás de la secuencia."
          },
          {
            "level": 2,
            "id": null,
            "text": "Una casilla marcada. ¿De quién es esa acción?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Cómo Valve logró finalmente neutralizar la «sustitución comercial» — y por qué se necesitaron siete años de soluciones provisionales"
          },
          {
            "level": 4,
            "id": null,
            "text": "Tiempo de espera para cambiar de avatar y nombre (febrero de 2024)"
          },
          {
            "level": 4,
            "id": null,
            "text": "Inversión de tendencia de 7 días en CS2 (julio de 2025)"
          },
          {
            "level": 4,
            "id": null,
            "text": "Notificación push obligatoria para la API (diciembre de 2023)"
          },
          {
            "level": 4,
            "id": null,
            "text": "Banners con la antigüedad y el nombre de la cuenta (2022-2024)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Su reglamento. Las plataformas registradas."
          },
          {
            "level": 3,
            "id": "enforcement-focus-title",
            "text": "Unas mismas normas. Una aplicación desigual."
          },
          {
            "level": 4,
            "id": null,
            "text": "Automatización"
          },
          {
            "level": 4,
            "id": null,
            "text": "Uso comercial"
          },
          {
            "level": 4,
            "id": null,
            "text": "VPN y ocultación de la ubicación"
          },
          {
            "level": 4,
            "id": null,
            "text": "Ocultación de enlaces"
          },
          {
            "level": 4,
            "id": null,
            "text": "¿Quién revisa la decisión cuando el servicio de asistencia cierra el caso?"
          },
          {
            "level": 2,
            "id": null,
            "text": "Una API de automatización. Una norma contra la automatización."
          },
          {
            "level": 3,
            "id": null,
            "text": "La falacia del «desarrollador de videojuegos»"
          },
          {
            "level": 4,
            "id": null,
            "text": "La contradicción de la automatización"
          },
          {
            "level": 4,
            "id": null,
            "text": "Un puesto del lado del servidor en el flujo comercial"
          },
          {
            "level": 2,
            "id": null,
            "text": "Se exigían diez días. Había que rendir cuentas de diez años."
          },
          {
            "level": 3,
            "id": "letter-company",
            "text": "VALVE CORPORATION"
          },
          {
            "level": 3,
            "id": null,
            "text": "Diez días.¿Y luego qué?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Sigue al servidor de retorno indicado."
          },
          {
            "level": 3,
            "id": "washington-record-heading",
            "text": "Dos plazos. Una norma de aplicación sin respuesta."
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve concede a los sitios web de apuestas un plazo de 10 días"
          },
          {
            "level": 4,
            "id": null,
            "text": "Washington presiona Valve"
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve rechaza la acusación"
          },
          {
            "level": 4,
            "id": null,
            "text": "Las rutas observadas en septiembre de 2026"
          },
          {
            "level": 4,
            "id": null,
            "text": "Dieciocho meses después de que Valve respondiera, el organismo regulador seguía considerándolo una intención."
          },
          {
            "level": 3,
            "id": null,
            "text": "La década del preaviso de 10 días: auditoría forense de supervivencia de los 23 emplazamientos señalados"
          },
          {
            "level": 4,
            "id": null,
            "text": "Desde avisos con 10 días de antelación hasta conglomerados con sede en el extranjero: un volumen de negocio de varios miles de millones de dólares"
          },
          {
            "level": 2,
            "id": null,
            "text": "El nombre de host ya figura en la solicitud."
          },
          {
            "level": 3,
            "id": null,
            "text": "Precedentes documentados y comunicados"
          },
          {
            "level": 3,
            "id": null,
            "text": "Lo que indica y lo que no indica una fecha de inscripción"
          },
          {
            "level": 3,
            "id": null,
            "text": "Auditoría comparativa: Normas de cumplimiento de la API"
          },
          {
            "level": 2,
            "id": "market-thesis-heading",
            "text": "La diferencia de precio «off-Steam»"
          },
          {
            "level": 2,
            "id": null,
            "text": "La diferencia de precios es cuantificable."
          },
          {
            "level": 3,
            "id": null,
            "text": "Lo que refleja la cifra en dólares"
          },
          {
            "level": 3,
            "id": null,
            "text": "Muchos locales indican un valor en dólares superior a Steam."
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam sigue a la cabeza en cuanto al número de ofertas."
          },
          {
            "level": 3,
            "id": null,
            "text": "El ecosistema comercial está a la vista de todos."
          },
          {
            "level": 2,
            "id": null,
            "text": "¿Quién puede restablecer las medidas de seguridad?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Un ticket de recuperación que desactivó la seguridad de la cuenta y una pérdida declarada de $10,000"
          },
          {
            "level": 3,
            "id": null,
            "text": "Más allá del inventario."
          },
          {
            "level": 3,
            "id": "theft-ledger-title",
            "text": "Valve abrió la puerta dos veces, con treinta y tres meses de diferencia. Nunca se cerró."
          },
          {
            "level": 4,
            "id": null,
            "text": "Lo que refleja el libro mayor y que ningún caso concreto muestra por sí solo."
          },
          {
            "level": 3,
            "id": null,
            "text": "La confidencialidad debe ir acompañada de la responsabilidad técnica."
          },
          {
            "level": 2,
            "id": null,
            "text": "Sigue el rastro del dinero. Separa las transacciones."
          },
          {
            "level": 3,
            "id": null,
            "text": "Donde realmente circula el dinero."
          },
          {
            "level": 3,
            "id": null,
            "text": "Clasifica primero la actividad y, a continuación, la obligación."
          },
          {
            "level": 3,
            "id": null,
            "text": "Realizar un seguimiento de los ingresos, la información y la asistencia."
          },
          {
            "level": 2,
            "id": null,
            "text": "La Ley de Servicios Digitales: dejar constancia de los conocimientos"
          },
          {
            "level": 3,
            "id": null,
            "text": "Un plazo de diez días."
          },
          {
            "level": 3,
            "id": null,
            "text": "La ventana temporal del DSA."
          },
          {
            "level": 3,
            "id": null,
            "text": "La duración requiere un historial de notificaciones."
          },
          {
            "level": 3,
            "id": null,
            "text": "de la facturación anual a nivel mundial"
          },
          {
            "level": 2,
            "id": null,
            "text": "Menores de edad: un inicio de sesión con «Steam» no constituye una verificación de edad"
          },
          {
            "level": 3,
            "id": null,
            "text": "Identifica el operador y los datos."
          },
          {
            "level": 3,
            "id": null,
            "text": "Registra el proceso desde el inicio de sesión hasta el ingreso."
          },
          {
            "level": 2,
            "id": null,
            "text": "La solicitud. La respuesta. La comparación que falta."
          },
          {
            "level": 3,
            "id": null,
            "text": "Los registros existen; el interesado no los ha recibido."
          },
          {
            "level": 2,
            "id": null,
            "text": "El acuerdo de suscripción frente a la propia arquitectura de la plataforma"
          },
          {
            "level": 3,
            "id": null,
            "text": "El límite máximo del mercado y la prohibición de uso comercial"
          },
          {
            "level": 3,
            "id": null,
            "text": "La vulnerabilidad de la clave API como un problema de diseño de la plataforma, más que como una negligencia por parte del usuario"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve recibe el nombre de host de autenticación en cada inicio de sesión"
          },
          {
            "level": 3,
            "id": null,
            "text": "La tendencia observada en las reclamaciones archivadas"
          },
          {
            "level": 3,
            "id": null,
            "text": "Un tribunal que evaluara este expediente no interpretaría la SSA de forma aislada."
          },
          {
            "level": 2,
            "id": null,
            "text": "Las conclusiones. Los documentos que solicitamos."
          },
          {
            "level": 2,
            "id": null,
            "text": "Memorándum probatorio — material facilitado por la Fuente 1"
          },
          {
            "level": 2,
            "id": null,
            "text": "La censura que aparece en el PDF generado es meramente estética: el texto ocultado sigue pudiendo extraerse."
          },
          {
            "level": 2,
            "id": null,
            "text": "Documentación de apoyo y correspondencia jurídica"
          },
          {
            "level": 2,
            "id": null,
            "text": "Documentos primarios seleccionados"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-01",
            "text": "Claves de hardware, solicitadas en 2016"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-02",
            "text": "Informes de fallos sin una opción de exclusión efectiva"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-03",
            "text": "Se ha notificado un uso indebido de un ticket de autenticación a Valve"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-01",
            "text": "44 compras en el mercado objeto de litigio"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-02",
            "text": "Una suspensión definitiva y la imposibilidad de recurrir"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-03",
            "text": "Un reinicio de la recuperación y una pérdida declarada de $10,000"
          },
          {
            "level": 2,
            "id": null,
            "text": "ArchiSteamFarm y la cláusula de automatización"
          },
          {
            "level": 2,
            "id": null,
            "text": "Rules ledger: clauses against recorded platforms"
          },
          {
            "level": 3,
            "id": "ledger-title",
            "text": "Uso comercial y facturación de la cuenta"
          },
          {
            "level": 3,
            "id": "lw-register-title",
            "text": "Registro de la plataforma 175"
          },
          {
            "level": 4,
            "id": null,
            "text": "Carga de la prueba"
          },
          {
            "level": 4,
            "id": null,
            "text": "Qué es y qué no es un registro etiquetado"
          },
          {
            "level": 2,
            "id": null,
            "text": "Manual de actuación DSAR: solicitar las pruebas"
          },
          {
            "level": 3,
            "id": null,
            "text": "Conserva tu cronología."
          },
          {
            "level": 3,
            "id": null,
            "text": "Solicita los datos que se han conservado."
          },
          {
            "level": 3,
            "id": null,
            "text": "Guarda el albarán de entrega."
          },
          {
            "level": 3,
            "id": null,
            "text": "Compara la respuesta."
          },
          {
            "level": 3,
            "id": null,
            "text": "Seguridad de la cuenta y registros de acceso"
          },
          {
            "level": 3,
            "id": null,
            "text": "Una discrepancia es un indicio que hay que investigar."
          },
          {
            "level": 2,
            "id": null,
            "text": "Volumen de asistencia técnica. Tiempos de respuesta publicados."
          },
          {
            "level": 3,
            "id": null,
            "text": "Dos colas en un servicio de atención al cliente, según se desprende de 21 capturas archivadas."
          },
          {
            "level": 2,
            "id": null,
            "text": "Cuenta los registros. Comprueba el ámbito."
          },
          {
            "level": 2,
            "id": null,
            "text": "Valve no publica ningún historial de medidas coercitivas.\nHemos construido uno."
          }
        ],
        "links": [
          "https://dotesports.com/counter-strike/news/csgo-lounge-billion-bets-3896",
          "https://store.steampowered.com/agreement/?l=english",
          "http://web.archive.org/web/20260921022032/https://store.steampowered.com/agreement/?l=english",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-all-results.json",
          "https://blog.counter-strike.net/expresstrade/",
          "http://web.archive.org/web/20260307161538/https://blog.counter-strike.net/expresstrade/",
          "https://wsgc.wa.gov/news/2016/washington-state-gambling-commission-orders-valve-stop-skins-gambling",
          "http://web.archive.org/web/20260520012601/https://wsgc.wa.gov/news/2016/washington-state-gambling-commission-orders-valve-stop-skins-gambling",
          "https://fr.scribd.com/document/328063293/Valve-s-Oct-18th-response-to-Washington-State-Gambling-Commission-s-cease-and-desist",
          "https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921021947/https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921022628/https://steamcommunity.com/linkfilter/?url=https:%2F%2Frollbit.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rbsnin.com.20260921T021120Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rollbit.com.json",
          "http://web.archive.org/web/20260921022740/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fskin.club",
          "http://web.archive.org/web/20260921022842/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fsc-auth.net",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skin.club.json",
          "http://web.archive.org/web/20260921022603/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fhowl.gg",
          "http://web.archive.org/web/20260921022636/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fhowl.uno",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/howl.gg.json",
          "http://web.archive.org/web/20260921022840/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fduelbits.com",
          "http://web.archive.org/web/20260921022901/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fswitchflips.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/duelbits.com.json",
          "http://web.archive.org/web/20260921022758/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgofast.com",
          "http://web.archive.org/web/20260921022847/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fauthtofast.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgofast.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/farmskins.com.20260921T025840Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/steam.kobal.cc.20260921T025844Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/farmskins.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cobaltlab.tech.20260921T041604Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cobaltauth.com.20260921T041608Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/cobaltlab.tech.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgo.net.20260921T041619Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cn2.easylot.net.20260921T041623Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgo.net.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/ggdrop.com.20260921T041637Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/ggauth.com.20260921T041641Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/ggdrop.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rustchance.com.20260921T041703Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/hgfuihd.com.20260921T041706Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rustchance.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skin.fans.20260921T041710Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.skinfans.com.20260921T041713Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skin.fans.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinport.com.20260921T041724Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinport.app.20260921T041728Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skinport.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skins.cash.20260921T041731Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinscash.live.20260921T041735Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skins.cash.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2hunt.com.20260921T041739Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rstspcl.com.20260921T041742Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tf2hunt.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgogem.com.20260922T192355Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/api.csgem.com.20260922T192358Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-2026-09-22.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/gamdom.com.20260922T192326Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/login.gambldom.com.20260922T192330Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/12cs.fail.20260922T192347Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/fail.games.20260922T192351Z.html",
          "http://web.archive.org/web/20260921022953/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgoempire.com",
          "http://web.archive.org/web/20260921022947/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgoempirelogin4.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgoempire.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cs.money.20260921T021131Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.dota.trade.20260921T021134Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/cs.money.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csfloat.com.20260921T041612Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgofloat.com.20260921T041615Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csfloat.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/g4skins.com.20260921T041630Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.g4s.to.20260921T041634Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/g4skins.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/juice.gg.20260921T041644Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/letmeinjuice.com.20260921T041648Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/juice.gg.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/market.csgo.com.20260921T041652Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2.net.20260921T041655Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/market.csgo.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rust.tm.20260921T041659Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rust.tm.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgolounge.com.20260922T192333Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2.net.20260922T192340Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2lounge.com.20260922T192337Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinbaron.de.20260921T041717Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinbaron.com.20260921T041721Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skinbaron.de.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2royal.com.20260921T041746Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2auth.com.20260921T041750Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tf2royal.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tradeit.gg.20260921T041753Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/connect-tradeit.com.20260921T041757Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tradeit.gg.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/upgrader.pro.20260921T041801Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/upgauth.space.20260921T041804Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/upgrader.pro.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-recheck-2026-09-21.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/domain-registration.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wayback-snapshots.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-2026-09-22c.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/master_registry.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/longitudinal-steam-phishing-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-steam-phishing-100.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-coverage-2026-09-22.json",
          "https://blog.csfloat.com/how-floatdb-tracks-items/",
          "http://web.archive.org/web/20260921022415/https://blog.csfloat.com/how-floatdb-tracks-items/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/platform-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/platforms-removed.json",
          "https://hackerone.com/reports/291750",
          "http://web.archive.org/web/20251116185046/https://hackerone.com/reports/291750",
          "https://hackerone.com/reports/1079561",
          "http://web.archive.org/web/20260924181830/https://hackerone.com/reports/1079561",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/hackerone-reports.json",
          "https://phishdestroy.io/steam_dossier/es/steam_enforcement_evidence.html#support-records",
          "https://www.darknavy.org/blog/exploiting_steam_usual_and_unusual_ways_in_the_cef_framework/",
          "https://steamcommunity.com/groups/SteamClientBeta/discussions/0/3365901765276206401/",
          "http://web.archive.org/web/20250804051514/https://steamcommunity.com/groups/SteamClientBeta/discussions/0/3365901765276206401/",
          "https://www.chromium.org/developers/design-documents/safebrowsing/",
          "http://web.archive.org/web/20260821101616/https://www.chromium.org/developers/design-documents/safebrowsing/",
          "https://www.chromium.org/developers/how-tos/api-keys/",
          "http://web.archive.org/web/20260830122831/https://www.chromium.org/developers/how-tos/api-keys/",
          "https://github.com/Homebrew/homebrew-cask/issues/193814",
          "https://testsafebrowsing.appspot.com/",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/domain-registration.json",
          "https://phishdestroy.io/steam_dossier/es/AUTH_AUDIT.md",
          "https://datatracker.ietf.org/doc/rfc6749/",
          "https://docs.cloud.google.com/docs/authentication/api-keys",
          "https://listings.pcisecuritystandards.org/pdfs/PCI_DSS_Resource_Guide_(003).pdf",
          "https://developer.apple.com/news/?id=02202019a",
          "http://web.archive.org/web/20250506070026/https://developer.apple.com/news/?id=02202019a",
          "https://dev.twitch.tv/docs/authentication/validate-tokens/",
          "https://discuss.dev.twitch.com/t/legacy-twitch-api-v5-i-e-kraken-shutdown-reminder-february-28-2022/36589",
          "http://web.archive.org/web/20250127085635/https://discuss.dev.twitch.com/t/legacy-twitch-api-v5-i-e-kraken-shutdown-reminder-february-28-2022/36589",
          "https://store.steampowered.com/news/posts/?enddate=1788390000",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/4123547285514022851",
          "https://skinvault.gg/blog/cs2-trade-protection-explained/",
          "https://csmarketcap.com/blog/market-insights/from-boom-to-bust-cs2s-trade-protection-impact",
          "https://skin.land/blog/steam-changes-cs2-trade-ban-logic-timing/",
          "https://help.steampowered.com/faqs/view/3041-A87A-E5F6-B6AC",
          "https://steamcommunity.com/ogg/593110/announcements/detail/533224478739530146",
          "https://steamcommunity.com/games/CSGO/announcements/detail/4447966961421256740",
          "https://steamcommunity.com/sharedfiles/filedetails/?id=2926756889",
          "https://steamcommunity.com/dev/apikey",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3734103130194459461",
          "https://steamcommunity.com/discussions/forum/1/3807266184852932971/",
          "https://help.steampowered.com/faqs/view/225C-C51E-B8F0-55B2",
          "https://store.steampowered.com/news/group/4/view/3314112260640237775",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/issues/325",
          "https://blog.dota2.com/2020/05/trading-cooldown/",
          "https://blog.counter-strike.net/index.php/2018/03/20308/",
          "http://web.archive.org/web/20250226114333/https://blog.counter-strike.net/index.php/2018/03/20308/",
          "https://phishdestroy.io/steam_dossier/es/steam_evidence_archive.html",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/493839547938902179",
          "https://store.steampowered.com/online_conduct",
          "http://web.archive.org/web/20260921022120/https://store.steampowered.com/online_conduct",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260918014700/https://store.steampowered.com/subscriber_agreement/",
          "https://steamcommunity.com/dev/apiterms",
          "http://web.archive.org/web/20260921022210/https://steamcommunity.com/dev/apiterms",
          "https://help.steampowered.com/en/faqs/view/628C-E332-BD8C-4D36",
          "https://phishdestroy.io/steam_dossier/es/social_graph.html",
          "https://phishdestroy.io/steam_dossier/es/security_timeline.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wsgc-skins-gambling-briefing-2018.pdf",
          "https://wsgc.wa.gov/sites/default/files/2023-10/Skins%20Gambling.pdf",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wsgc-briefing-manifest.json",
          "https://x.com/csgobig",
          "https://www.facebook.com/csgobigofficial/",
          "https://500.casino/",
          "https://csgolounge.com/",
          "https://csgocasino.gg/",
          "https://x.com/CSGOatsecom",
          "https://x.com/CSGOSweep/status/937420902538543106",
          "https://x.com/Wild",
          "https://x.com/csgopot",
          "https://x.com/csgodiamondscom",
          "https://www.ftc.gov/legal-library/browse/cases-proceedings/162-3184-csgo-lotto-matter",
          "https://x.com/CSGODouble",
          "https://x.com/csgo_massive",
          "https://www.facebook.com/csgostrongfree/",
          "https://www.facebook.com/CSNCOM/",
          "https://www.gamblingcommission.gov.uk/report/young-people-and-gambling",
          "https://www.aph.gov.au/Parliamentary_Business/Committees/Senate/Environment_and_Communications/Gamingmicro-transactions",
          "https://phishdestroy.io/steam_dossier/es/elite_skins.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/csfloat-catalogue.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/skinport-floor-over-cap.json",
          "https://pricempire.com/cs2-marketplaces",
          "http://web.archive.org/web/20260921022459/https://pricempire.com/cs2-marketplaces",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/priceempire-marketplaces.json",
          "https://www.steamanalyst.com/marketplace",
          "http://web.archive.org/web/20260719014552/https://www.steamanalyst.com/marketplace",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-atlas.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json",
          "https://phishdestroy.io/steam_dossier/es/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/es/steam_enforcement_evidence.html#case-support-recovery",
          "https://top10.owasp.org/2025/A01_2025-Broken_Access_Control/",
          "http://web.archive.org/web/20260920212535/https://top10.owasp.org/2025/A01_2025-Broken_Access_Control/",
          "https://store.steampowered.com/privacy_agreement/",
          "http://web.archive.org/web/20260921021648/https://store.steampowered.com/privacy_agreement/",
          "https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "http://web.archive.org/web/20250818113925/https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "https://www.dexerto.com/counter-strike-2/valve-saves-hacked-cs2-player-threatened-with-ransom-over-300000-of-rare-stickers-3283135/",
          "https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "http://web.archive.org/web/20220702042821/https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "https://www.kaspersky.com/blog/cs-go-two-million-usd-inventory-hack/44697/",
          "https://esportfire.com/article/the-2-million-usd-csgo-hack-22062022",
          "http://web.archive.org/web/20260515110250/https://esportfire.com/article/the-2-million-usd-csgo-hack-22062022",
          "https://esportsbetting.com/valve-deletes-130000-stolen-dragon-lore/",
          "https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "http://web.archive.org/web/20251115173120/https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "https://vkplay.ru/media/news/bloger-rasskazal-kak-podderzhka-steam-vorovala-akkaunty-igrokov/",
          "https://lis-skins.com/ru/blog/krupneisaia-mosenniceskaia-sxema-v-istorii-steam/",
          "https://escorenews.com/ru/csgo/news/44056-sotrudniki-podderjki-steam-zanimalis-krajey-skinov-s-akkauntov-za-god-oni-zarabotali-svyshe-300-tysyach-dollarov",
          "https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "http://web.archive.org/web/20250805141942/https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/outsourcing-archive-records.json",
          "https://community.skin.club/en/news/collector-has-steam-inventory-returned-after-bold-hack",
          "https://esportfire.com/article/300k-scam-full-katowice-2014-holo-collection-hacked",
          "http://web.archive.org/web/20251217072445/https://esportfire.com/article/300k-scam-full-katowice-2014-holo-collection-hacked",
          "https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng",
          "http://web.archive.org/web/20260920024236/https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng",
          "https://ag.ny.gov/press-release/2026/attorney-general-james-sues-game-developer-promoting-illegal-gambling-through",
          "http://web.archive.org/web/20260901015430/https://ag.ny.gov/press-release/2026/attorney-general-james-sues-game-developer-promoting-illegal-gambling-through",
          "https://www.fincen.gov/sites/default/files/2019-05/FinCEN%20CVC%20Guidance%20FINAL.pdf",
          "http://web.archive.org/web/20250711185007/https://www.fincen.gov/sites/default/files/2019-05/FinCEN%20CVC%20Guidance%20FINAL.pdf",
          "https://eur-lex.europa.eu/legal-content/EN/LSU/?uri=CELEX:32018L1673",
          "https://eur-lex.europa.eu/eli/dir/2024/1640/oj/eng",
          "http://web.archive.org/web/20260830153004/https://eur-lex.europa.eu/eli/dir/2024/1640/oj/eng",
          "https://eur-lex.europa.eu/eli/reg/2022/2065/oj/eng",
          "http://web.archive.org/web/20260920080125/https://eur-lex.europa.eu/eli/reg/2022/2065/oj/eng",
          "https://phishdestroy.io/steam_dossier/es/legal_analysis.html",
          "https://partner.steamgames.com/doc/features/auth#website",
          "http://web.archive.org/web/20260921022335/https://partner.steamgames.com/doc/features/auth",
          "https://www.ftc.gov/legal-library/browse/rules/childrens-online-privacy-protection-rule-coppa",
          "http://web.archive.org/web/20260921070051/https://www.ftc.gov/legal-library/browse/rules/childrens-online-privacy-protection-rule-coppa",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/gdpr-ticket-1.png",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/screenshot-manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/gdpr-ticket-2.png",
          "https://datenschutz.hamburg.de/beschwerde",
          "https://edpb.europa.eu/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/regulatory-review/disclosure-audit.json",
          "https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "http://web.archive.org/web/20260821155801/https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "https://phishdestroy.io/steam_dossier/es/index#exhibit-gallery-section",
          "https://github.com/ValveSoftware/steam-for-linux/issues/4521",
          "https://phishdestroy.io/steam_dossier/es/steam_evidence_archive.html?source=GitHub&record=484",
          "https://github.com/ValveSoftware/steam-for-linux/issues/6459",
          "http://web.archive.org/web/20260419051343/https://github.com/ValveSoftware/steam-for-linux/issues/6459",
          "https://phishdestroy.io/steam_dossier/es/steam_evidence_archive.html?source=GitHub&record=467",
          "https://github.com/ValveSoftware/Source-1-Games/issues/3857",
          "https://phishdestroy.io/steam_dossier/es/steam_evidence_archive.html?source=GitHub&record=768",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "http://web.archive.org/web/20250320082450/https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://phishdestroy.io/steam_dossier/es/steam_evidence_archive.html?source=Reddit&record=4533",
          "https://www.reddit.com/r/ohnePixel/comments/1hahqx2/permanently_banned_steam_account_without_a_clear/",
          "https://phishdestroy.io/steam_dossier/es/steam_evidence_archive.html?source=Reddit&record=4766",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://phishdestroy.io/steam_dossier/es/steam_evidence_archive.html?source=Reddit&record=4592",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/selected-evidence-records.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive_manifest.json",
          "https://phishdestroy.io/steam_dossier/es/card_economy.html",
          "https://github.com/JustArchiNET/ArchiSteamFarm/wiki/FAQ",
          "https://phishdestroy.io/steam_dossier/es/card_economy.html#scale",
          "https://phishdestroy.io/steam_dossier/es/card_economy.html#licence",
          "https://phishdestroy.io/steam_dossier/es/enforcement_audit.html",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "http://web.archive.org/web/20260924181709/https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://rdap.verisign.com/com/v1/domain/csgoempire.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoempire.com",
          "https://rdap.verisign.com/com/v1/domain/csgoempirelogin4.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/csgoempire.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustreaper.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustreaper.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/rustreaper.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustly.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustly.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/rustly.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgofast.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgofast.com",
          "https://rdap.verisign.com/com/v1/domain/authtofast.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/csgofast.com.json",
          "https://rdap.verisign.com/com/v1/domain/duelbits.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fduelbits.com",
          "https://rdap.verisign.com/com/v1/domain/switchflips.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/duelbits.com.json",
          "https://rdap.verisign.com/com/v1/domain/farmskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffarmskins.com",
          "https://tld-rdap.verisign.com/cc/v1/domain/kobal.cc",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/farmskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoluck.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoluck.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/csgoluck.com.json",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/domain-registry/insane.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Finsane.gg",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/insane.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs2skin.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs2skin.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/cs2skin.com.json",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/domain-registry/juice.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fjuice.gg",
          "https://rdap.verisign.com/com/v1/domain/letmeinjuice.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/juice.gg.json",
          "https://rdap.verisign.com/com/v1/domain/ggdrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fggdrop.com",
          "https://rdap.verisign.com/com/v1/domain/ggauth.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/ggdrop.com.json",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/domain-registry/howl.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhowl.gg",
          "https://rdap.radix.host/rdap/domain/howl.uno",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/howl.gg.json",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/domain-registry/chicken.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fchicken.gg",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/chicken.gg.json",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/domain-registry/csgocasino.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgocasino.gg",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/csgocasino.gg.json",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/domain-registry/hunt.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhunt.gg",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/hunt.gg.json",
          "https://rdap.verisign.com/com/v1/domain/csbattle.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsbattle.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/csbattle.com.json",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/domain-registry/skinrave.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinrave.gg",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/skinrave.gg.json",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/domain-registry/csdouble.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsdouble.gg",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/csdouble.gg.json",
          "https://rdap.verisign.com/com/v1/domain/rustchance.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustchance.com",
          "https://rdap.verisign.com/com/v1/domain/hgfuihd.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/rustchance.com.json",
          "https://rdap.radix.host/rdap/domain/cobaltlab.tech",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcobaltlab.tech",
          "https://rdap.verisign.com/com/v1/domain/cobaltauth.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/cobaltlab.tech.json",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/domain-registry/raided.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fraided.gg",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/raided.gg.json",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/domain-registry/rustneo.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustneo.gg",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/rustneo.gg.json",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/domain-registry/splits.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsplits.gg",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/splits.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/upgrader.pro",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fupgrader.pro",
          "https://rdap.radix.host/rdap/domain/upgauth.space",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/upgrader.pro.json",
          "https://rdap.centralnic.com/fans/domain/skin.fans",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.fans",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/skin.fans.json",
          "https://rdap.nic.one/domain/hotpizza.one",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhotpizza.one",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/hotpizza.one.json",
          "https://rdap.verisign.com/com/v1/domain/g4skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg4skins.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/g4skins.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2royal.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2royal.com",
          "https://rdap.verisign.com/com/v1/domain/tf2auth.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/tf2royal.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2hunt.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2hunt.com",
          "https://rdap.verisign.com/com/v1/domain/rstspcl.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/tf2hunt.com.json",
          "https://rdap.identitydigital.services/rdap/domain/tf2.bet",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2.bet",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/tf2.bet.json",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/domain-registry/openstars.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fopenstars.gg",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/openstars.gg.json",
          "https://rdap.verisign.com/com/v1/domain/skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/skins.com.json",
          "https://rdap.identitydigital.services/rdap/domain/white.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwhite.market",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/white.market.json",
          "https://rdap.identitydigital.services/rdap/domain/moon.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmoon.market",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/moon.market.json",
          "https://rdap.verisign.com/com/v1/domain/csfloat.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsfloat.com",
          "https://rdap.verisign.com/com/v1/domain/csgofloat.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/csfloat.com.json",
          "https://rdap.identitydigital.services/rdap/domain/skin.land",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.land",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/skin.land.json",
          "https://rdap.verisign.com/com/v1/domain/haloskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhaloskins.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/haloskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/163.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuff.163.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/buff.163.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmarket.csgo.com",
          "https://rdap.verisign.com/net/v1/domain/dota2.net",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/market.csgo.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinport.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinport.com",
          "https://pubapi.registry.google/rdap/domain/skinport.app",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/skinport.com.json",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/domain-registry/skinflow.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinflow.gg",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/skinflow.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/skin.place",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.place",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/skin.place.json",
          "https://rdap.verisign.com/com/v1/domain/skinsmonkey.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinsmonkey.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/skinsmonkey.com.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbaron.de",
          "https://rdap.verisign.com/com/v1/domain/skinbaron.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/skinbaron.de.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frust.tm",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/rust.tm.json",
          "https://rdap.verisign.com/com/v1/domain/pirateswap.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fpirateswap.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/pirateswap.com.json",
          "https://rdap.radix.host/rdap/domain/mannco.store",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmannco.store",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/mannco.store.json",
          "https://rdap.verisign.com/com/v1/domain/skinswap.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinswap.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/skinswap.com.json",
          "https://rdap.verisign.com/com/v1/domain/exeskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fexeskins.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/exeskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/balticskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbalticskins.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/balticskins.com.json",
          "https://rdap.nic.trade/domain/cs.trade",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.trade",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/cs.trade.json",
          "https://rdap.verisign.com/com/v1/domain/rapidskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frapidskins.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/rapidskins.com.json",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/domain-registry/tradeit.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftradeit.gg",
          "https://rdap.verisign.com/com/v1/domain/connect-tradeit.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/tradeit.gg.json",
          "https://rdap.verisign.com/com/v1/domain/49skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F49skins.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/49skins.com.json",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/domain-registry/skinvault.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinvault.gg",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/skinvault.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/aim.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Faim.market",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/aim.market.json",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/domain-registry/skinout.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinout.gg",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/skinout.gg.json",
          "https://rdap.verisign.com/com/v1/domain/ntskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fntskins.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/ntskins.com.json",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/domain-registry/gamerpay.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamerpay.gg",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/gamerpay.gg.json",
          "https://rdap.nic.tf/domain/scrap.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fscrap.tf",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/scrap.tf.json",
          "https://rdap.nic.tf/domain/marketplace.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmarketplace.tf",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/marketplace.tf.json",
          "https://rdap.identitydigital.services/rdap/domain/skins.cash",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.cash",
          "https://rdap.identitydigital.services/rdap/domain/skinscash.live",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/skins.cash.json",
          "https://rdap.verisign.com/net/v1/domain/csgo.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo.net",
          "https://rdap.verisign.com/net/v1/domain/easylot.net",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/csgo.net.json",
          "https://rdap.verisign.com/net/v1/domain/cybershoke.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcybershoke.net",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/cybershoke.net.json",
          "https://rdap.verisign.com/net/v1/domain/fastcup.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffastcup.net",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/fastcup.net.json",
          "https://rdap.verisign.com/com/v1/domain/leetify.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fleetify.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/leetify.com.json",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/domain-registry/scope.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fscope.gg",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/scope.gg.json",
          "https://rdap.verisign.com/com/v1/domain/tradeupspy.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftradeupspy.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/tradeupspy.com.json",
          "https://rdap.identitydigital.services/rdap/domain/cs.deals",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.deals",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/cs.deals.json",
          "https://rdap.verisign.com/com/v1/domain/pricempire.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fpricempire.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/pricempire.com.json",
          "https://rdap.identitydigital.services/rdap/domain/lzt.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flzt.market",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/lzt.market.json",
          "https://rdap.verisign.com/com/v1/domain/z2u.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fz2u.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/z2u.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoroll.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoroll.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/csgoroll.com.json",
          "https://rdap.verisign.com/com/v1/domain/rollbit.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frollbit.com",
          "https://rdap.verisign.com/com/v1/domain/rbsnin.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/rollbit.com.json",
          "https://rdap.identitydigital.services/rdap/domain/500.casino",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F500.casino",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/500.casino.json",
          "https://rdap.verisign.com/com/v1/domain/csgobig.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgobig.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/csgobig.com.json",
          "https://rdap.verisign.com/com/v1/domain/casedrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcasedrop.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/casedrop.com.json",
          "https://rdap.verisign.com/com/v1/domain/banditcamp.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbanditcamp.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/banditcamp.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinbox.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbox.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/skinbox.com.json",
          "https://rdap.verisign.com/com/v1/domain/tastydrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftastydrop.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/tastydrop.com.json",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/domain-registry/csgopolygon.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgopolygon.gg",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/csgopolygon.gg.json",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/domain-registry/magicdrop.ru.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmagicdrop.ru",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/magicdrop.ru.json",
          "https://rdap.verisign.com/com/v1/domain/csdice.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsdice.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/csdice.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinodds.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinodds.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/skinodds.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgowin.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgowin.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/csgowin.com.json",
          "https://rdap.verisign.com/net/v1/domain/csgorun.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgorun.net",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/csgorun.net.json",
          "https://rdap.verisign.com/com/v1/domain/openskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fopenskins.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/openskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustbet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustbet.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/rustbet.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgomagic.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgomagic.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/csgomagic.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgobounty.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgobounty.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/csgobounty.com.json",
          "https://rdap.verisign.com/com/v1/domain/ezskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fezskins.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/ezskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustcases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustcases.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/rustcases.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoreaper.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoreaper.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/csgoreaper.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgocases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgocases.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/csgocases.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo-skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo-skins.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/csgo-skins.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgonet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgonet.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/csgonet.com.json",
          "https://rdap.verisign.com/com/v1/domain/wtfskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwtfskins.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/wtfskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/flamecases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fflamecases.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/flamecases.com.json",
          "https://rdap.verisign.com/com/v1/domain/gamedom.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamedom.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/gamedom.com.json",
          "https://rdap.nic.club/domain/skin.club",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.club",
          "https://rdap.verisign.com/net/v1/domain/sc-auth.net",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/skin.club.json",
          "https://rdap.verisign.com/com/v1/domain/daddyskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdaddyskins.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/daddyskins.com.json",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/domain-registry/rustix.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustix.gg",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/rustix.gg.json",
          "https://rdap.nic.club/domain/skins.club",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.club",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/skins.club.json",
          "https://rdap.publicinterestregistry.org/rdap/domain/csgohouse.org",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgohouse.org",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/csgohouse.org.json",
          "https://rdap.verisign.com/net/v1/domain/skinrave.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinrave.net",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/skinrave.net.json",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/domain-registry/bloodycase.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbloodycase.gg",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/bloodycase.gg.json",
          "https://rdap.verisign.com/com/v1/domain/csgoclicker.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoclicker.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/csgoclicker.com.json",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/domain-registry/rustbet.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustbet.gg",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/rustbet.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs-drop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs-drop.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/cs-drop.com.json",
          "https://rdap.verisign.com/net/v1/domain/hellstore.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhellstore.net",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/hellstore.net.json",
          "https://rdap.verisign.com/com/v1/domain/rustloot.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustloot.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/rustloot.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo-case.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo-case.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/csgo-case.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgogem.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgogem.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/csgogem.com.json",
          "https://rdap.verisign.com/com/v1/domain/rainbet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frainbet.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/rainbet.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustclash.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustclash.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/rustclash.com.json",
          "https://rdap.identitydigital.services/rdap/domain/12cs.fail",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F12cs.fail",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/12cs.fail.json",
          "https://rdap.verisign.com/com/v1/domain/tf2easy.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwww.tf2easy.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/tf2easy.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2blaze.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2blaze.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/tf2blaze.com.json",
          "https://rdap.verisign.com/com/v1/domain/shuffle.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fshuffle.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/shuffle.com.json",
          "https://rdap.identitydigital.services/rdap/domain/buff.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuff.market",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/buff.market.json",
          "https://rdap.identitydigital.services/rdap/domain/avan.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Favan.market",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/avan.market.json",
          "https://rdap.identitydigital.services/rdap/domain/cs.money",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.money",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/cs.money.json",
          "https://rdap.verisign.com/com/v1/domain/uuskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fuuskins.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/uuskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/youpin898.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fyoupin898.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/youpin898.com.json",
          "https://rdap.verisign.com/com/v1/domain/c5game.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fc5game.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/c5game.com.json",
          "https://rdap.verisign.com/com/v1/domain/waxpeer.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwaxpeer.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/waxpeer.com.json",
          "https://rdap.verisign.com/com/v1/domain/dmarket.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdmarket.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/dmarket.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamcommunity.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamcommunity.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/steamcommunity.com.json",
          "https://rdap.verisign.com/com/v1/domain/lootfarm.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flootfarm.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/lootfarm.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustskins.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/rustskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/krakatoa.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fkrakatoa.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/krakatoa.com.json",
          "https://rdap.verisign.com/com/v1/domain/shadowpay.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fshadowpay.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/shadowpay.com.json",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/domain-registry/igxe.cn.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Figxe.cn",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/igxe.cn.json",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/domain-registry/swap.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fswap.gg",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/swap.gg.json",
          "https://rdap.verisign.com/com/v1/domain/bitskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbitskins.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/bitskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2mart.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2mart.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/tf2mart.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinbid.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbid.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/skinbid.com.json",
          "https://rdap.verisign.com/com/v1/domain/lootbear.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flootbear.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/lootbear.com.json",
          "https://rdap.nic.tf/domain/backpack.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbackpack.tf",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/backpack.tf.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fstntrading.eu",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/stntrading.eu.json",
          "https://rdap.verisign.com/com/v1/domain/skinwallet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinwallet.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/skinwallet.com.json",
          "https://rdap.verisign.com/com/v1/domain/dota2market.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdota2market.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/dota2market.com.json",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/domain-registry/xplay.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fxplay.gg",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/xplay.gg.json",
          "https://rdap.verisign.com/com/v1/domain/esportal.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fesportal.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/esportal.com.json",
          "https://rdap.registro.br/domain/gamersclub.com.br",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamersclub.com.br",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/gamersclub.com.br.json",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/domain-registry/epidemic.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fepidemic.gg",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/epidemic.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs2stash.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs2stash.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/cs2stash.com.json",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/domain-registry/csgoskins.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoskins.gg",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/csgoskins.gg.json",
          "https://rdap.verisign.com/com/v1/domain/steamanalyst.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamanalyst.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/steamanalyst.com.json",
          "https://rdap.verisign.com/net/v1/domain/steamcardexchange.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamcardexchange.net",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/steamcardexchange.net.json",
          "https://rdap.verisign.com/com/v1/domain/dotabuff.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdotabuff.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/dotabuff.com.json",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/domain-registry/tracker.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftracker.gg",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/tracker.gg.json",
          "https://rdap.verisign.com/com/v1/domain/funpay.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffunpay.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/funpay.com.json",
          "https://rdap.verisign.com/com/v1/domain/playerauctions.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fplayerauctions.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/playerauctions.com.json",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/domain-registry/eldorado.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Feldorado.gg",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/eldorado.gg.json",
          "https://rdap.verisign.com/com/v1/domain/g2a.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg2a.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/g2a.com.json",
          "https://rdap.verisign.com/net/v1/domain/kinguin.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fkinguin.net",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/kinguin.net.json",
          "https://rdap.verisign.com/com/v1/domain/g2g.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg2g.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/g2g.com.json",
          "https://rdap.verisign.com/com/v1/domain/playerup.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fplayerup.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/playerup.com.json",
          "https://rdap.verisign.com/net/v1/domain/smurfhub.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfhub.net",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/smurfhub.net.json",
          "https://rdap.verisign.com/com/v1/domain/smurfaccounts.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfaccounts.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/smurfaccounts.com.json",
          "https://rdap.verisign.com/com/v1/domain/buycsgorank.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuycsgorank.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/buycsgorank.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgosmurfkings.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgosmurfkings.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/csgosmurfkings.com.json",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/domain-registry/smurfstore.co.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfstore.co",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/smurfstore.co.json",
          "https://rdap.verisign.com/com/v1/domain/steamlvlup.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlvlup.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/steamlvlup.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamlevels.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlevels.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/steamlevels.com.json",
          "https://rdap.verisign.com/com/v1/domain/levelsteam.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flevelsteam.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/levelsteam.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamlevelu.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlevelu.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/steamlevelu.com.json",
          "https://rdap.verisign.com/com/v1/domain/eloking.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Feloking.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/eloking.com.json",
          "https://rdap.publicinterestregistry.org/rdap/domain/boosteria.org",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fboosteria.org",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/boosteria.org.json",
          "https://rdap.verisign.com/com/v1/domain/overgear.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fovergear.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/overgear.com.json",
          "https://rdap.verisign.com/com/v1/domain/blazingboost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fblazingboost.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/blazingboost.com.json",
          "https://rdap.verisign.com/com/v1/domain/dota2boost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdota2boost.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/dota2boost.com.json",
          "https://rdap.verisign.com/com/v1/domain/buyboost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuyboost.com",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit/buyboost.com.json",
          "https://phishdestroy.io/steam_dossier/es/steam_tos_assets/auth-route-audit.json",
          "https://help.steampowered.com/en/faqs/view/365F-4BEE-2AE2-7BDD",
          "https://store.steampowered.com/privacy_agreement/#8",
          "https://www.edpb.europa.eu/system/files/2023-04/edpb_guidelines_202201_data_subject_rights_access_v2_en.pdf",
          "https://web.archive.org/web/20260810154631/https://store.steampowered.com/stats/support",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/design-review/part2/measurements.json",
          "https://phishdestroy.io/steam_dossier/es/VALVE_EVIDENCE_PACK/databases/TOTAL_VALVE_SCANDALS_MASTER_DB.csv",
          "https://phishdestroy.io/steam_dossier/es/license_disclaimer.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/es/index.content.json",
      "export_json_sha256": "d44e42daec25f99c0904ff9f8f7761793bff39218113c3b21066d49aa02494c5"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "es/investigation_part2.html",
      "language": "es",
      "title": "Acceso a las cuentas y rendición de cuentas — El Dossier Steam",
      "source_url": "https://phishdestroy.io/steam_dossier/es/investigation_part2",
      "source_html_sha256": "fcfea9a84e7b5e965e8720fe6b76f578d5d1e2a0d9168a9e00579ca3d20fbae0",
      "exported_at": "2026-09-29T00:17:21.410Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "investigation_part2.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/es/investigation_part2.pdf?v=print-20260929-v5",
        "sha256": "6e18793accc166149ac1dcea0ff951fc0bdcfe2a5a5b7843333e125f1c872877",
        "bytes": 125055,
        "pages": 9
      },
      "integrity": {
        "signed_object": "investigation_part2.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "investigation_part2.content.json.asc",
        "digest_file": "investigation_part2.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify investigation_part2.content.json.asc investigation_part2.content.json",
          "sha256sum -c investigation_part2.content.json.sha256"
        ]
      },
      "content": {
        "text": "EL DOSSIER DE STEAM / II\n\nTu cuenta.Su acceso.¿Quién contesta?\n\nAutomatización de los servicios públicos. Asistencia externalizada. Y son los ciudadanos quienes acaban pagando las consecuencias.\n\nSigue de cerca las infraestructuras, las pérdidas comunicadas y los documentos en los que se basan las reclamaciones.\n\nAnalizar la infraestructura ↘\nANEXO 01 / VIGILANCIA DEL MERCADO NEGRO EN DIRECTO550,000+\n\nSteam cuentas a la venta actualmente en FSB Market (nombre anonimizado; aquí no se divulga el nombre original)\nen este preciso momento\n\n550,000+ INVENTARIO EN TIEMPO REAL · 231,829 EN EL CORPUS HISTÓRICO EXTRAÍDO (198,320 REGISTROS DE STEALER)\n\nEl principal centro de intercambio clandestino de cuentas Steam secuestradas, FSB Market (otros nombres asociados no divulgados) verifica la identidad tanto de los compradores como de los vendedores mediante el OpenID oficial Steam de Valve (openid.realm = https://FSB Market). En cualquier momento dado, más de medio millón de cuentas robadas y comprometidas (registros de programas de robo de datos de RedLine/Lumma, capturas de phishing, «credential stuffing») se ponen a la venta activamente por céntimos ($0.50–$2.00). Ni FSB Market ni el foro asociado está bloqueado por el filtro de enlaces de Valve. Se trata del «depósito industrial» que abastece a las cuentas de bots de pago 63.06% que Valve bloquea sin prestar asistencia a la víctima.\n\nDatos en tiempo real de Intel: Seguimiento del mercado negro (más de 550 000 usuarios activos) ↗ · Abrir registro de captura ↗ · Abrir el seguimiento del filtro de enlaces ↗Más de 550 000 EN DIRECTO\n\n01 / UN ECOSISTEMA CON AUTORES\n\nLa automatización haun registro documental.\n\nProyectos con nombre. Funcionalidades publicadas. Localiza la documentación de una herramienta y, a continuación, analiza las relaciones entre desarrolladores recopiladas.\n\n252REPOSITORIOS RECOPILADOS\n3,320PERFILES DE GITHUB\n4,214PERFIL – PARES DE REPOSITORIOS\nValve infraestructuraBibliotecas municipalesAplicaciones reutilizables\nLas líneas indican integraciones o dependencias documentadas. Selecciona un nodo para ver la información correspondiente.\n\nAutomatización de varias cuentas / JustArchiNET\n\nArchiSteamFarm\n\nEl proyecto anuncia explícitamente la obtención simultánea de cartas en cuentas de Steam. Su archivo de proyecto declara una dependencia de SteamKit2.\n\nLee la documentación del propio proyecto ↗\n\nSteamKit → ArchiSteamFarm\ndependencia declarada ↗\n\nRELACIONES RECOPILADAS\n\n40 etiquetas de colaboradores · 40 etiquetas de Forker\n\nA continuación se muestra una muestra de colaboradores. Estas etiquetas describen la relación con el repositorio, no una relación laboral ni de aprobación.\n\n@JustArchi@renovate[bot]@JustArchi-ArchiBot@dependabot-preview[bot]@renovate-bot@actions-user@dependabot-support@Abrynos\nLo que muestra el gráfico del desarrollador\n\nEl gráfico muestra las relaciones publicadas entre colaboradores y bifurcadores de proyectos concretos y perfiles de GitHub. Se trata de registros públicos: bifurcaciones de repositorios, listas de contribuciones y asociaciones de perfiles. La cuestión es qué debe responder Valve a partir del rastro documental de las capacidades publicadas y las relaciones entre desarrolladores, no qué ha inventado esta investigación. Los hash de los códigos fuente se guardan en el procedencia del mapa.\n\nExplora toda la red ↗Datos de origen del repositorio ↓\n\n02 / DIFERENTES CREDENCIALES. DIFERENTES PODERES.\n\n¿Qué tecla?¿De qué estamos hablando?\n\nPara jugar a un juego no es necesario que el jugador facilite una clave personal de API web. Esa es la diferencia fundamental que se aborda en esta investigación.\n\n01 / CUENTA DE USUARIO\nClave personal de la API web\nsteamcommunity.com/dev/apikey\n\nSe emite desde una cuenta de usuario para las llamadas a la API autorizadas. La creación, la visibilidad y la revocación de claves, así como la detección de abusos, son cuestiones relacionadas con la seguridad de la cuenta.\n\n02 / BACKEND DEL JUEGO\nClave de la API web del editor\n\nLos socios de Steamworks utilizan las credenciales del editor para las operaciones de backend compatibles, incluidos los servicios relacionados con los juegos. La clave personal de un jugador es una credencial diferente.\n\n03 / IDENTIDAD Y SESIÓN\nOpenID / tokens de sesión\n\nOpenID confirma la identidad ante un sitio web. Un token de sesión o de actualización Steam tiene una finalidad diferente. Estos mecanismos no deben presentarse como una única «clave API» intercambiable.\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\nValve registra tanto las claves de la API web del usuario como las del editor. Por lo tanto, la API web en su conjunto no está separada de Steamworks. Documentación sobre claves API ↗ archivado 2026-09-15 ↗ · Autenticación durante la sesión de juego ↗ archivado 2026-08-29 ↗\n\nDOCUMENTADO POR EL AUTOR DE LA HERRAMIENTA / MARZO DE 2024\n\nLa automatización puede utilizar más de una clave API.\n\nLa wiki del Trade Offer Manager describe cómo utilizar un token de acceso de sesión para algunas partes de la API web cuando no existe una clave de API independiente. También recoge la confirmación a través del móvil para la creación de claves a partir de finales de 2023. El responsable del mantenimiento afirma que Valve no admite el uso del token de esta forma; se trata de una afirmación de la documentación obsoleta, no de una prueba de elusión en tiempo real.\n\nConsulta la explicación del responsable del mantenimiento ↗ archivado 2026-09-24 ↗\n\nEL LADO HUMANO / UN RECORRIDO ILUSTRATIVO POR EL PHISHING\n\nSigo jugando.Ya se ha revelado.\n\nUn mensaje de un amigo. Una petición para votar. Una página de agradecimiento. Para el jugador, la tarea ha terminado. Una sesión comprometida puede prolongarse más allá de ese momento.\n\nEN LA PANTALLA DEL REPRODUCTOR\n\nF\nEL RELATO DE UN AMIGO\n\n«¿Puedes votar por nuestro equipo?»\n\nLa solicitud llega a través del chat deSteam, procedente de una cuenta conocida. En este caso, la página enlazada se abre en el navegador del cliente.\n\nFUERA DE LA VISTA\n\nLa confianza viene antes que la página web.\n\nLa cuenta de un amigo que haya sido pirateada puede dar credibilidad a un enlace de phishing. La interfaz Steam que lo rodea no certifica la página web de destino.\n\nREEMITENTE CONOCIDO / DESTINO EXTERNO\nLa seguridad de la cuenta es lo primero que hay que tener en cuenta antes de vender cualquier artículo.\n\nEl jugador no tenía la intención de crear una credencial de automatización ni de delegar el control. Volver a entrar en un juego no es prueba de que la cuenta sea segura. Valve conserva los registros de sesión, el historial de creación de claves API y los datos de correlación de dispositivos. La víctima, en cambio, no. Esa asimetría es el problema de la responsabilidad.\n\nAcceso a la sesión y tipos de credenciales\n\nUna clave API y una sesión de inicio de sesión son credenciales independientes con capacidades diferentes. La revocación de una clave no pone fin a una sesión activa. La propia documentación de Valve describe ambas; Valve conserva los registros que mostrarían qué credencial estaba activa en el momento de cualquier acción objeto de controversia. Lo que se exige es la divulgación de ese registro, no una deducción inventada por la investigación. Documentación del responsable sobre la gestión de tokens ↗ archivado 2026-09-24 ↗ · Valve documentación clave ↗ archivado 2026-09-15 ↗\n\n03 / EL MERCADO OFICIAL TIENE UN LÍMITE MÁXIMO\n\nEl artículo puede ser poco común.El límite se mantiene.\n\nNo es posible obtener un precio superior al límite máximo de cotización mediante una única cotización en el Mercado Comunitario a ese precio íntegro.\n\nPRECIO DE VENTA ORIENTATIVO$5,000Modificar el precio de venta del artículo\n$100$20,000\n\nSe trata de una ilustración del límite publicado, no de una valoración ni de una recomendación de negociación.\n\nLÍMITE DE COTIZACIÓN≈ $1,800\nTAPA DE LA CARTERA≈ $2,000\n\nPor encima del límite máximo de cotización publicado.\n\nLos fondos del monedero no se pueden retirar a una cuenta bancaria. Estas restricciones generan una demanda que satisfacen los mercados de skins de terceros: una demanda que se deriva de los límites de cotización y de saldo del monedero, mientras que las propias normas de Valve prohíben a los operadores comerciales satisfacerla.\n\nLímites de mercado de Steam ↗ archivado 2026-09-21 ↗\n\n04 / DENTRO DEL LÍMITE DE APOYO\n\nNos confían sus datos.Responsable del acceso.\n\nLa política de privacidad de Valve prevé expresamente el intercambio de datos personales con terceros proveedores de asistencia, en la medida en que sea necesario para prestar dicha asistencia.\n\nEL JUGADORCuenta y pruebas\n→\nVÁLVULAProceso de recuperación\n→\nPROVEEDOR DE ASISTENCIAAcceso delegado\n\nPolítica de privacidad, apartado 5.2 ↗ · La propia política de Valve autoriza el acceso de terceros con fines de asistencia técnica. Las cuestiones pendientes son: qué permisos se concedieron, qué registros de auditoría existen y qué ocurrió cuando, supuestamente, se hizo un uso indebido de dicho acceso.\n\n2015\nLa balanza era de uso público\n\nValve reconoció que se habían producido numerosos robos de cuentas y describió las medidas de protección.\n\nValve publicación ↗archivado 2026-08-09 ↗\n2015\nValve subcontrató el servicio — y así lo dijo\n\nValve cuenta con un pequeño equipo interno de Steam de liderazgo en materia de asistencia y así lo ha declarado «contratamos a un par de empresas diferentes» para gestionar el servicio de asistencia (Erik Johnson, Valve, a Kotaku); el artículo 5.2 de su política de privacidad autoriza el acceso de dichos terceros a los datos de los usuarios. ¿Qué contratista tiene acceso a la recuperación de cuentas? Valve nunca lo ha revelado. — En los debates de la comunidad se mencionan empresas como Concentrix, pero ninguna de ellas ha sido Valve-confirmada. El servicio externalizado ya estaba en funcionamiento años antes de cualquiera de las dos admisiones que se mencionan a continuación.\n\nKotaku: Valve en su sección de ayuda ↗archivado 2025-07-11 ↗\n2023\nLa primera admisión\n\nEl equipo de CS:GO de Valve asume por escrito la responsabilidad por el hecho de que una cuenta haya sido comprometida a través de su propio proceso de solicitud de ayuda, y anula los intercambios.\n\nAbrir el caso de externalización ↓\n2025\nLa segunda admisión\n\n33 meses después, Steam El servicio de atención al cliente explica que un técnico «no siguió nuestro procedimiento, lo que provocó que tu cuenta se restableciera a nombre de otra persona». El mismo canal. El mismo resultado.\n\nDexerto, 14 de noviembre de 2025 ↗\n\nEXPEDIENTE / HFB Y LAS ACUSACIONES DE EXTERNALIZACIÓN\n\nLa forma de entrar era Steam el propio «Support».Valve así lo afirmó por escrito.\n\nEn la respuesta del servicio de atención al cliente reproducida por Dexerto, el equipo de CS:GO de Valve asume la responsabilidad por el robo de una cuenta. a través del proceso de solicitud de ayuda — su propio canal, no una página de phishing ni el usuario. Los artículos se recuperaron y las transacciones se anularon, lo que, según Valve, es una solución que no existe para otras víctimas. El inventario de HFB se situaba en $2,000,000+ ese mismo día y $3,000,000+ en el seguimiento; Qkss perdió $1,000,000+ de la misma manera y no se llevó nada.\n\nRESPUESTA DEL SERVICIO DE ASISTENCIA / REPRODUCIDO POR DEXERTO · 21 DE FEBRERO DE 2023\n«se vio comprometida a raíz de una solicitud de asistencia, de lo cual se hace responsable el equipo de CS:GO»\nLee la noticia y el mensaje reproducido ↗ archivado 2025-08-18 ↗\n01 / QUÉ VÁLVULA SE ADMITÍA\nSu propio canal de asistencia fue la vía de acceso\n\nLa respuesta se refiere a la cuenta comprometida y a la anulación de sus operaciones. Valve las anuló, por lo que las operaciones eran reversibles. El ticket original autenticado no se encuentra en esta recopilación.\n\n02 / LO QUE LOS DESPIDOS NO SOLUCIONARON\nEsa misma puerta se volvió a abrir en noviembre de 2025\n\nLa empresa contratista despidió a todo su personal de asistencia técnica Steam —según informó Mzkshow a través de Dexerto, y no mediante un comunicado oficial de la empresa Valve—. Treinta y tres meses después, Steam Support escribió a otro cobrador que «un técnico de soporte que gestionó la solicitud de ayuda no siguió nuestro proceso, lo que provocó que su cuenta se restableciera a nombre de otra persona». Frase del propio Valve, sobre el mismo canal.\n\nSegunda admisión, 14 de noviembre de 2025 ↗\n03 / ¿QUÉ ES «OPEN»?\nValve nunca ha revelado el nombre del contratista\n\nNinguna de estas fuentes indica quién fue el contratista ni dónde se produjo el hecho. Esto no es una laguna en la información, sino un dato que Valve no ha revelado sobre quién tenía acceso a las cuentas de los usuarios.\n\nRelato contemporáneo del caso ↗\n\nTres preguntas que Valve no ha respondido: quién podría anular la recuperación de la cuenta, qué se descubrió en la auditoría de acceso y qué cambió a raíz de ello.\n\nDenuncias posteriores recogidas en el archivo de pruebas conservado\n\nDos publicaciones de Reddit de 2024 recogen nuevas investigaciones de Mzkshow: un caso de levantamiento de una suspensión VAC de julio de 2024 y un caso de inventario $13,000 de diciembre de 2024. Se trata de incidentes notificados por separado. La cuestión de la responsabilidad en cada uno de ellos es idéntica: quién tenía acceso de anulación, qué reveló la auditoría y qué cambió.\n\n14 de julio de 2024 · recuperación notificada / caso de prohibición VAC ↗2 de diciembre de 2024 · se ha notificado $13,000 caso de inventario ↗archivado 2025-08-05 ↗Dos postes conservados, filas de origen y hash ↓\n\n05 / SIGUE LA PÉRDIDA\n\nCada importeNecesita una funda.\n\nDiez casos, de junio de 2022 a marzo de 2026. Cada importe corresponde a la cifra publicada por la fuente a la que hace referencia — $6,300,000, $2,000,000+, $1,000,000+, ≈$320,000, ≈$300,000, y ha bajado hasta los 288 €. Valve conserva el registro de transacciones, el registro de la sesión y el registro de auditoría de asistencia técnica de cada una de ellas, y no ha facilitado ninguno de ellos.\n\nCANAL DE ASISTENCIA21 2022 de junio\n$2,000,000+\nHFB — the largest inventory in the game\n\nVALORACIÓN DEL STOCK COMUNICADA · AUMENTADA A MÁS DE $3M EN EL SEGUIMIENTO DEL 2023 DE FEBRERO\n\nSiete «Dragon Lores» de recuerdo y el karambit «Blue Gem» n.º1, que solo ese cuchillo cuesta unos1.26m. Inactivo durante tres años con el autenticador aún activado; el correo electrónico y la contraseña se cambiaron a través del proceso de recuperación de la asistencia técnica. Valve anuló las transacciones y asumió su responsabilidad por escrito. Antes de la anulación, ya se habían retirado, según se informó, unos200,000dólares de los ingresos a través de market.csgo.com, que realiza los pagos en efectivo y criptomonedas. Una anulación devuelve un skin, no el dinero que alguien ya se había ingresado. La anulación también provocó un fallo: un comprador ocultó su «Souvenir Dragon Lore» en una unidad de almacenamiento del juego; el script no podía ver el interior de su propio contenedor, y Valve duplicó un objeto de $130,000 al revertir un robo —detectado gracias a los ID de los objetos y a las denuncias de la comunidad, eliminado en julio 2022,; el comprador recibió el reembolso a través de BUFF en lugar de Valve.\n\nDexerto, el día del robo ↗\nCARTERA Y COMPRAS07 2022 de julio\n>$500\n44 disputed Market purchases\n\nGASTOS DECLARADOS DE LA CARTERA · USD\n\nUn usuario denuncia compras no autorizadas de artículos de bajo valor de Dota 2 y una respuesta insatisfactoria por parte del servicio de atención al cliente.\n\nLee la denuncia y las capturas de pantalla adjuntas ↗\nINFRACCIÓN DE LA PLATAFORMA14 2022 de agosto\n$6,300,000\nCS.Money — 19,000+ skins de los bots\n\nVALORACIÓN · PRIMERA ESTIMACIÓN: $1.6M\n\nLos atacantes se hicieron con los archivos del autenticador móvil de los bots de trading de la plataforma y los vaciaron, transfiriendo parte del botín a traders conocidos para despistar. Los investigadores de la comunidad identificaron 55 cuentas de los atacantes en cuestión de horas. Valve no revirtió nada: un sitio de terceros se encuentra fuera de Steam, según la misma Steam cuyo inventario, sistema de operaciones API y sistema de cuentas se encargaron del robo de principio a fin.\n\nLee el relato de la época ↗\nCANAL DE ASISTENCIAPUBLICADO EN 21 1 de febrero de 2023\n$1,000,000+\nQkss: misma puerta, mismo actor, respuesta opuesta\n\nVALORACIÓN DEL STOCK DECLARADO\n\nSe tramitó de la misma forma que el caso de HFB, por el mismo actor y a través de la misma solicitud de asistencia técnica. El caso de HFB se resolvió por completo ocho meses antes. El de Qkss, no. No hay nada en el expediente publicado que distinga ambos casos, salvo el tamaño de la audiencia.\n\nDexerto sobre la investigación de Mzkshow ↗\nCANAL DE ASISTENCIAPUBLICADO EL 2023 DE FEBRERO\n≈ $320,000\nEl propio uso de información privilegiada: un año de ello\n\nINGRESOS DE APROXIMADAMENTE UN AÑO · NO SE TRATA DE UNA VALORACIÓN DE EXISTENCIAS\n\nEl acceso a través del servicio de asistencia permitió consultar el historial de la cuenta de hasta 15 años de antigüedad: la primera clave de CD, el primer correo electrónico, la primera tarjeta… exactamente las pruebas que requiere el proceso de recuperación. Quien controla la base de datos siempre sale ganando en esa discusión frente a quien controla la cuenta. Un M4A4 Howl robado con hologramas de iBUYPOWER y Titan Katowice 2014 se vendió por35,000 y acabó en manos de b1t, de NAVI, quien no tenía forma de saberlo. La respuesta del contratista fue despedir a todos los empleados que trabajaban en el servicio de asistenciSteam.\n\nNoticias de Escorenews sobre la misma investigación ↗\nCARTERA Y COMPRAS09 2023 de diciembre\n€288\nPérdida del monedero a pesar de la protección en dos pasos\n\nTRUSTPILOT · ÍNDICE DE FUENTES 16\n\nEl usuario denuncia que le han pirateado la cuenta y que se han negado a ayudarle con los gastos en Market. La exportación no incluye ninguna URL de valoración individual.\n\nComprobar la procedencia de la fuente ↗\nRECUPERACIÓN DE CUENTAS02 2024 de diciembre\n$13,000\n«Matvey»: dos años después de los despidos\n\nESTIMACIÓN DEL INVENTARIO DEL AUTOR\n\nSe concedió la recuperación a una persona que facilitó datos de la cuenta que el propio titular no pudo corroborar. El mismo procedimiento, el mismo resultado, después de que el contratista hubiera cerrado su servicio de asistencia de Steam.\n\nLee la denuncia archivada ↗\nRECUPERACIÓN DE CUENTAS09 2025 DE MAYO\n≈ $10,000\nRecuperación a través del billete de otra persona\n\nPÉRDIDA DE UN ARTÍCULO RECLAMADO · USD\n\nUn usuario de Quebec afirma que el servicio de atención al cliente restableció la contraseña y eliminó la protección de la cuenta a petición de otra persona.\n\nLee la denuncia en primera persona ↗\nCANAL DE ASISTENCIA13 2025 de noviembre\n≈ $300,000\nHawkeye337 — y la segunda confesión por escrito deValve\n\nCOLECCIÓN COMPLETA DE HOLOGRAMAS «2014» DE KATOWICE\n\nEl atacante exigió un bitcoin de 1 y empezó a transferir la colección a cuentas de Negevs para destruirla. Steam Respuesta del servicio de asistencia: «Un técnico de asistencia que gestionó la solicitud de ayuda no siguió nuestro procedimiento, lo que provocó que tu cuenta fuera restaurada a nombre de otra persona». Treinta y tres meses después de la primera admisión, la misma historia. Restaurada a las pocas horas de que el hilo se convirtiera en tendencia en X. Qkss no contaba con esa audiencia.\n\nDexerto, 14 Nov 2025 ↗\nCARTERA Y COMPRAS29 MAR2026\n$50\nRecargas no autorizadas y juegos regalados\n\nTRUSTPILOT · ÍNDICE DE FUENTES 290\n\nEl autor de la reseña alega gastos no autorizados y solicitudes de reembolso denegadas. En la exportación falta la URL de la reseña concreta.\n\nComprobar la procedencia de la fuente ↗\n\nLas atribuciones y los importes se mantienen tal y como los ha comunicado cada fuente. Valve conserva los registros de transacciones, los registros de sesión y el historial de auditoría de asistencia técnica de cada uno de estos casos. Preséntalos. Una publicación de Reddit que se haya conservado no resuelve la cuestión; lo que cuenta son los propios registros de Valve.\n\nLA COLECCIÓN / TRAS LA COMPROBACIÓN\n\n231,829 cuentas en oferta.Valve contiene los registros de todos ellos.\n354 → 201\nValoraciones en Trustpilot\n\nSe han eliminado 153 filas duplicadas. Las URL de las reseñas individuales no se han conservado en la exportación.\n\n231,829\nSteam listados de cuentas\n\n33,509 clasificado como «autoregistrado»; 198,320 bajo la etiqueta «ladrón» del coleccionista. Los anuncios no constituyen ventas formalizadas.\n\nAuditoría de cobros ↓Buscar en el archivo fuente ↗",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Tu cuenta.Su acceso.¿Quién contesta?"
          },
          {
            "level": 2,
            "id": null,
            "text": "La automatización haun registro documental."
          },
          {
            "level": 3,
            "id": null,
            "text": "ArchiSteamFarm"
          },
          {
            "level": 2,
            "id": null,
            "text": "¿Qué tecla?¿De qué estamos hablando?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Clave personal de la API web"
          },
          {
            "level": 3,
            "id": null,
            "text": "Clave de la API web del editor"
          },
          {
            "level": 3,
            "id": null,
            "text": "OpenID / tokens de sesión"
          },
          {
            "level": 3,
            "id": null,
            "text": "La automatización puede utilizar más de una clave API."
          },
          {
            "level": 2,
            "id": null,
            "text": "Sigo jugando.Ya se ha revelado."
          },
          {
            "level": 3,
            "id": "session-hidden-title",
            "text": "La confianza viene antes que la página web."
          },
          {
            "level": 2,
            "id": null,
            "text": "El artículo puede ser poco común.El límite se mantiene."
          },
          {
            "level": 2,
            "id": null,
            "text": "Nos confían sus datos.Responsable del acceso."
          },
          {
            "level": 3,
            "id": null,
            "text": "La balanza era de uso público"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve subcontrató el servicio — y así lo dijo"
          },
          {
            "level": 3,
            "id": null,
            "text": "La primera admisión"
          },
          {
            "level": 3,
            "id": null,
            "text": "La segunda admisión"
          },
          {
            "level": 3,
            "id": null,
            "text": "La forma de entrar era Steam el propio «Support».Valve así lo afirmó por escrito."
          },
          {
            "level": 4,
            "id": null,
            "text": "Su propio canal de asistencia fue la vía de acceso"
          },
          {
            "level": 4,
            "id": null,
            "text": "Esa misma puerta se volvió a abrir en noviembre de 2025"
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve nunca ha revelado el nombre del contratista"
          },
          {
            "level": 2,
            "id": null,
            "text": "Cada importeNecesita una funda."
          },
          {
            "level": 3,
            "id": null,
            "text": "HFB — the largest inventory in the game"
          },
          {
            "level": 3,
            "id": null,
            "text": "44 disputed Market purchases"
          },
          {
            "level": 3,
            "id": null,
            "text": "CS.Money — 19,000+ skins de los bots"
          },
          {
            "level": 3,
            "id": null,
            "text": "Qkss: misma puerta, mismo actor, respuesta opuesta"
          },
          {
            "level": 3,
            "id": null,
            "text": "El propio uso de información privilegiada: un año de ello"
          },
          {
            "level": 3,
            "id": null,
            "text": "Pérdida del monedero a pesar de la protección en dos pasos"
          },
          {
            "level": 3,
            "id": null,
            "text": "«Matvey»: dos años después de los despidos"
          },
          {
            "level": 3,
            "id": null,
            "text": "Recuperación a través del billete de otra persona"
          },
          {
            "level": 3,
            "id": null,
            "text": "Hawkeye337 — y la segunda confesión por escrito deValve"
          },
          {
            "level": 3,
            "id": null,
            "text": "Recargas no autorizadas y juegos regalados"
          },
          {
            "level": 2,
            "id": null,
            "text": "231,829 cuentas en oferta.Valve contiene los registros de todos ellos."
          },
          {
            "level": 3,
            "id": null,
            "text": "Valoraciones en Trustpilot"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam listados de cuentas"
          }
        ],
        "links": [
          "https://phishdestroy.io/live-intel/?category=steam",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/lzt.market.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-evidence-lzt.json",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://github.com/JustArchiNET/ArchiSteamFarm/blob/main/ArchiSteamFarm/ArchiSteamFarm.csproj",
          "https://github.com/JustArchi",
          "https://github.com/renovate[bot]",
          "https://github.com/JustArchi-ArchiBot",
          "https://github.com/dependabot-preview[bot]",
          "https://github.com/renovate-bot",
          "https://github.com/actions-user",
          "https://github.com/dependabot-support",
          "https://github.com/Abrynos",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/automation-map.json",
          "https://phishdestroy.io/steam_dossier/es/output_steam_network/network.html",
          "https://phishdestroy.io/steam_dossier/es/output_steam_network/raw_data.json",
          "https://phishdestroy.io/steam_dossier/es/#proxy-bypass-explainer",
          "https://partner.steamgames.com/doc/webapi_overview/auth",
          "http://web.archive.org/web/20260915025812/https://partner.steamgames.com/doc/webapi_overview/auth",
          "https://partner.steamgames.com/doc/webapi/ISteamUserAuth",
          "http://web.archive.org/web/20260829124950/https://partner.steamgames.com/doc/webapi/ISteamUserAuth",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "http://web.archive.org/web/20260924181824/https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://store.steampowered.com/privacy_agreement/",
          "https://store.steampowered.com/oldnews/19618",
          "http://web.archive.org/web/20260809125516/https://store.steampowered.com/oldnews/19618",
          "https://kotaku.com/valve-explains-why-steam-customer-service-is-still-terr-1736988223",
          "http://web.archive.org/web/20250711004653/https://kotaku.com/valve-explains-why-steam-customer-service-is-still-terr-1736988223",
          "https://www.dexerto.com/counter-strike-2/valve-saves-hacked-cs2-player-threatened-with-ransom-over-300000-of-rare-stickers-3283135/",
          "https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "http://web.archive.org/web/20250818113925/https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "https://lis-skins.com/ru/blog/krupneisaia-mosenniceskaia-sxema-v-istorii-steam/",
          "https://www.reddit.com/r/cs2/comments/1e38jo4/stealing_accounts_and_removing_vac_bans_a_new/",
          "https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "http://web.archive.org/web/20250805141942/https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/outsourcing-archive-records.json",
          "https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "https://escorenews.com/en/csgo/news/44087-valve-steam-support-employee-accused-of-selling-inactive-accounts-inventories-worth-six-figures-b1t-has-one-of-these-skins",
          "https://phishdestroy.io/steam_dossier/es/PART2_RESEARCH.md",
          "https://www.reddit.com/r/GlobalOffensive/comments/1h56shi/steam_support_is_stealing_accounts/",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/design-review/part2/quality-review.json",
          "https://phishdestroy.io/steam_dossier/es/steam_evidence_archive.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/es/investigation_part2.content.json",
      "export_json_sha256": "d9a7db8c95be724aba5cd94efffc14f5fb2c1ad9d3b217aa1b715dc3ada4baa3"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "es/legal_analysis.html",
      "language": "es",
      "title": "Sus condiciones, tus derechos — El dossier «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/es/legal_analysis",
      "source_html_sha256": "c8c01cb3d28e50fe6257652cc005d96556bdd68027ea630e0156f499cc6d1869",
      "exported_at": "2026-09-29T00:17:21.988Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "legal_analysis.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/es/legal_analysis.pdf?v=print-20260929-v5",
        "sha256": "98e80c250778599ab3fc4e45ee3270ebf9ba9fc4c4f680e270674acd346171b8",
        "bytes": 105343,
        "pages": 8
      },
      "integrity": {
        "signed_object": "legal_analysis.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "legal_analysis.content.json.asc",
        "digest_file": "legal_analysis.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify legal_analysis.content.json.asc legal_analysis.content.json",
          "sha256sum -c legal_analysis.content.json.sha256"
        ]
      },
      "content": {
        "text": "Informe jurídico y económico\nAnálisis jurídico: condiciones de uso y cumplimiento normativo\n\nSus condiciones. Tus derechos.\n\nLO QUE DEMUESTRA ESTA SECCIÓN\n\nEsta auditoría jurídica forense evalúa la asimetría contractual entre Valve Corporation y los usuarios de Steam en las principales jurisdicciones reguladoras. Establece cómo la licencia de suscripción revocable priva al consumidor de la propiedad legal, analiza la jurisprudencia del Tribunal de Justicia de la Unión Europea sobre el agotamiento del derecho de reventa digital y examina el cumplimiento de la Ley de Servicios Digitales (DSA) y del artículo GDPR 15.. El análisis demuestra cómo los mecanismos de aplicación automatizados funcionan sin que existan vías de recurso significativas, mientras que las comisiones de mercado de las plataformas extraen sistemáticamente valor económico de cada transacción entre pares.\n\n← Volver al informe ejecutivo\n\nEl presente informe ofrece un análisis jurídico, económico y técnico de la discrepancia existente entre las normas declaradas de la plataforma «Steam» y la situación del consumidor: una aplicación automatizada de las normas con escasas vías de recurso y un amplio control corporativo sobre los activos digitales. Las cifras se indican junto con su fuente; cuando no ha sido posible rastrear una cifra hasta un registro primario, se ha omitido.\n\nVector 1\n\nSustituir la «propiedad» por una licencia revocable, de modo que los activos digitales puedan retirarse en virtud del acuerdo.\n\nVector 2\n\nSistema de control automatizado (VACNet), cuyas sanciones, según se indica en Steam Support, no pueden revocarse.\n\nVector3\n\nLos controles sobre cuentas y activos, combinados con una comisión de mercado de CS2 de 15% (5%, Steam y 10%, comisión del editor), que resta valor al ecosistema en cada reventa.\n\nAsimetría de los términos\nExención de responsabilidad y licencia revocable\n2.1 El modelo de «suscripción» frente a los derechos de propiedad\n\nEl artículo 2 del Acuerdo de suscripción de Steam otorga a los usuarios únicamente un licencia personal, no exclusiva, intransferible y revocable. Según lo establecido en el acuerdo, Valve podrá cancelar cuentas en cualquier momento, y los saldos no utilizados de Steam Wallet podrán perderse.\n\n2.2 La ilusión del reembolso frente a la Directiva de la UE sobre los derechos de los consumidores\nMarco jurídico\tMecanismo de reembolso\tLimitación\nEU Consumer Rights Directive\tUnconditional 14-day right of withdrawal on digital content\tWaived if download begins with explicit consumer consent\nSteam SSA\t14 days / under 2 hours played\tValve may deny at its discretion for \"abuse\"\nEvaluación\n\nValve condiciona el derecho legal de desistimiento de la UE, de «14-días», a su propio plazo de «14 días / 2 horas», que debe aceptarse en el momento de la descarga antes de que se pueda evaluar el producto. Esa política restringe —y no amplía— el derecho legal; si lo hace de forma lícita es una cuestión que compete a la autoridad competente, y no una conclusión que se afirme aquí.\n\nLitigios\nMercado secundario y defensa de la competencia\nUFC Que Choisir contra «Valve» — Francia\n2019\nTribunal de París: la doctrina del agotamiento de los derechos se aplica a los videojuegos — la reventa es lícita\n2022 de octubre\nEl Tribunal de Apelación de París revoca la sentencia\n23 2024 de octubre\nTribunal de Casación (Tribunal Supremo): los videojuegos son «obras complejas» a efectos de la Directiva sobre la sociedad de la información, y no programas informáticos. Reventa digital prohibido. Prevalece «Valve».\nCaso antimonopolio de Wolfire Games — Estados Unidos (En el asunto «Valve», n.º 2:21-cv-00563)\n\nLa cláusula de «nación más favorecida» (PMFN) de la plataforma Valve prohíbe a los desarrolladores vender claves de «Steam» a un precio más bajo en cualquier otra plataforma. Las tiendas de la competencia —incluso aquellas que cobran una comisión de 12% frente a la de Valve, que es de 30%— no pueden trasladar ese ahorro a los consumidores.\n\nWhat this means — PMFN — platform most-favoured-nation\n\nA contract term that stops a seller offering better terms anywhere else than on the platform it signed with. Applied to game keys it means a studio cannot undercut its Steam price on a storefront that takes a smaller cut. It is the clause at the centre of the antitrust claims against Valve.\n\n336Número total de empleados de Valve (2021). Fuente: pruebas documentales desclasificadas.\n79empleados que gestionan toda la plataforma Steam. Fuente: pruebas documentales desclasificadas.\n$3.5Mbeneficio neto por empleado. Fuente: pruebas presentadas en el proceso de revelación de pruebas.\n\nLos expedientes de la fase de presentación de pruebas, ya desclasificados, revelan que 8.5.000 dólares de ingresos brutos en 2021 sobre los empleados de «336». El 79-equipo «Steam» gestionó 373,000+ las solicitudes de asistencia diarias, derivándolas a centros de atención telefónica automatizados y subcontratados.\n\nANEXO DEL EXPEDIENTE PÚBLICO · W.D. WASH. ASUNTO2:21-CV-00563Nota interna de investigación\n\nTim Sweeney (director ejecutivo de Epic Games) a Gabe Newell: «¿Por qué Steam sigue quedándose con 30% de los ingresos brutos cuando el procesamiento de pagos cuesta 2–5% y el ancho de banda CDN cuesta $0.002/GB? Si restas los juegos más populares de 25 en Steam, apuesto a que Valve obtuvo más beneficios de la mayoría de los siguientes 1,000 que los propios desarrolladores».\n\nScott Lynch (director de operaciones de Valve Corporation), en un reenvío interno dirigido a Gabe Newell: «¿Estás enfadado, tío?»\n\nRéplica a la declaración jurada (Bloomberg, 2026): En el marco de la declaración jurada prevista en el artículo 30 (b) (1), Gabe Newell declaró que «Valve no tiene ninguna política ni práctica consistente en imponer precios a los desarrolladores de software de terceros en otras plataformas». Los demandantes confrontaron a Newell con memorandos internos de Valve que demostraban una política activa de control de precios y amenazas de exclusión de la lista a aquellos desarrolladores que fijaban precios más bajos en tiendas de la competencia. A finales de marzo 2026,, el Tribunal Federal denegó la solicitud de sentencia sumaria de Valve, remitiendo la demanda colectiva de los desarrolladores de 32,000-a un juicio con jurado.\n2024 de noviembre\n\nSe ha admitido a trámite la demanda colectiva relativa a ~ Los desarrolladores de «32,000» que pagó comisiones desde enero de 2017,, además de una demanda colectiva paralela de consumidores.\n\nIndemnización reclamada\n\n$3.1B\nTriplicado según la legislación antimonopolio de EE. UU. = $9.3B posible exposición.\n\n2026: de junio Una nueva demanda alega que Microsoft y Valve participaron en un acuerdo de cártel para restringir la competencia en la distribución de videojuegos para PC.\n\nAdmisión oficial en el programa de Delitos Financieros y Prevención del Blanqueo de Capitales\nValve Confesión oficial: Liquidaciones por fraude a nivel mundial (28, octubre de 2019)\n\nEl 28 de octubre de 2019, Valve puso fin oficialmente al intercambio y la reventa en el mercado de claves de contenedores de Counter-Strike recién adquiridas. En su comunicado público oficial (blog.counter-strike.net/2019/10/26113), la empresa «Valve» reconoció por escrito que la economía virtual que había creado se había convertido en un centro internacional de blanqueo de capitales:\n\n«En el pasado, la mayoría de las transacciones de claves que observábamos se realizaban entre clientes legítimos. Sin embargo, recientemente las redes de fraude internacionales han empezado a utilizar claves de CS:GO para liquidar sus ganancias. En este momento, se cree que casi todas las compras de claves que acaban siendo intercambiadas o vendidas en el mercado proceden de actividades fraudulentas».\n\nContexto normativo: Esta confesión se produjo tras el ultimátum formal de la Comisión de Juego del Estado de Washington (WSGC) a Valve y las órdenes de cese y desistimiento de julio de 2016 emitidas por el consejero general de Valve, Karl Quackenbush, a los dominios de apuestas con skins de 23 (entre los que se incluyen CSGO Lotto, CSGOLounge y OPSkins), solo después de que una investigación penal sobre apuestas pusiera en peligro las operaciones de la plataforma.\n\nCompetencia\nUn titular de derechos en Rusia, con el que el usuario no puede ponerse en contacto\n\nEl Acuerdo de suscripción presenta a Valve como una parte que debe muy poco y a la que nadie puede llegar: los bloqueos son permanentes, las apelaciones se rechazan y se retira el acceso a territorios enteros con una sola línea sobre las «regiones sancionadas». Frente a esa postura, está lo que hace Valve cuando son sus propios intereses comerciales los que están en juego en una jurisdicción a la que, por lo demás, trata como difícil.\n\nValve v. Touch Skins — reclamación de propiedad intelectual previa al juicio, Rusia\n1 2026 de septiembre\nValve., a través del bufete de abogados ruso Melling, Voitishkin & Partners, envía una carta de requerimiento previo al juicio a los operadores de Fundas táctiles, un gran cambiador de skins para CS2, enviado por correo postal ruso y por correo electrónico.\nMotivos\nTres grupos de presuntas infracciones: los derechos exclusivos sobre el software; los derechos sobre el aspecto de los «skins» de armas, cuchillos y guantes; y las marcas registradas de «Valve». La conducta de los operadores se califica de deliberada y prolongada.\nDemanda\nDetén inmediatamente el funcionamiento y elimina toda la infraestructura: el software… código fuente, sitios web y páginas en redes sociales; de no ser así, Valve se reserva el derecho a interponer una demanda ante un tribunal ruso por una indemnización económica considerable y remitir el asunto a las fuerzas del orden para una evaluación penal.\nResultado\nTras recibir la carta, la plataforma anunció que iba a cerrar. Se trata, según se ha informado, de la primera vez quValve recurre a vías legales contra un desarrollador de «skin-changers» en Rusia.\n\nSegún ha informado el investigador de datos Maxim «GabeFollower» Poletaev (X, ~11 de septiembre de 2026) y la prensa rusa especializada en videojuegos. Se trata de una reclamación previa al juicio, no de una demanda presentada; no se ha hecho público ningún número de expediente. Se trata aquí tal y como se ha informado, no como un expediente judicial. Fuentes: dota2.ru archivado en 2026-09-24 ↗ · Shazoo.\n\nLa misma jurisdicción, pero en sentido contrario\n\nValve no es ajeno al sistema jurídico y normativo ruso. Es cumple con los requisitos de Roskomnadzor: a petición del organismo regulador, se eliminaron las páginas de la comunidad 260+ Steam que contenían material prohibido, y Roskomnadzor ha declarado públicamente que Steam cumple con los requisitos de la legislación. La ley rusa de «páginas de destino» (Ley Federal 236-FZ, en vigor desde 2022), exige a las grandes plataformas de Internet extranjeras que prestan servicio a usuarios rusos que establezcan una presencia local y una cuenta de enlace con Roskomnadzor. Valve no solo cumple las órdenes de retirada de dicho organismo regulador, sino que, ahora, recurre a asesores jurídicos rusos y a la amenaza de los tribunales rusos para proteger sus «skins» como propiedad intelectual.\n\nAsí pues, la plataforma es accesible, eficaz y defiende sus derechos precisamente en lo que respecta a sus ingresos. El contraste radica en el usuario: a un cliente de pago de una región sancionada se le comunica que la relación ha terminado, se le bloquea el acceso a la comunidad hasta que 2038, se cierre el ticket, y no existe ningún foro en el que se pueda cuestionar la decisión — «Estaban más que encantados de cobrarme y tramitar mis transacciones», habiéndose aprobado un año antes el reembolso de esa misma cuenta desde la misma dirección IP iraní (r/pcgaming, 4 2026 de agosto de ; más cartas de requerimiento en la exposición sobre la economía de las tarjetas). «Valve» recurre a todo el aparato de un sistema jurídico nacional para defender un «skin»; en cambio, no ofrece ningún tipo de procedimiento al usuario que haya comprado los «skins».\n\nValve Considera que esa misma jurisdicción es aquella en la que puede actuar y cumplir con la normativa siempre que el interés en juego sea el de «Valve» —asesores jurídicos rusos, la amenaza de los tribunales rusos, el cumplimiento de las órdenes de retirada de Roskomnadzor—, mientras que considera que sus obligaciones para con los usuarios de ese mercado, y de cualquier otro, quedan fuera de cualquier proceso. Es un titular de derechos cuando se trata de sus ingresos y una parte inalcanzable cuando se trata de los derechos de los usuarios.\n\nFuentes: TASS (RKN: cumple con la normativa «Steam») · Ley federal «236-» FZ.\n\nOportunismo jurídico\nLa capitulación de la cláusula de arbitraje\n2023 — el ataque\n\nVarios bufetes de abogados (Zaiger LLC, Mason LLP) captaron a miles de usuarios a través de las redes sociales y presentaron simultáneamente decenas de miles de demandas de arbitraje individuales.\n\nLa exposición de Valve\n\n$225M+\nen concepto de tasas de tramitación de arbitraje no reembolsables, antes de que se examinara el fondo del asunto. Calculado con arreglo al Reglamento de Arbitraje para Consumidores de la Asociación Americana de Arbitraje (AAA) y a los Anexos Complementarios sobre Arbitraje Masivo. Los demandantes, representados por Zaiger LLC y Mason LLP, presentaron unas ~75,000s demandas de arbitraje individuales contra Valve Corp. (en paralelo a las demandas antimonopolio en Wolfire Games LLC y otros contra Valve Corp., Expediente n.º 2:21-cv-00563-JCC, W.D. Wash.). Según las tarifas para consumidores de la AAA, la empresa demandada abona tasas administrativas no reembolsables por el caso y depósitos para el nombramiento de árbitros de aproximadamente $3,000+ por cada caso individual (75,000 presentaciones × $3,000 = aproximadamente $225M en gastos procesales iniciales). Véanse los informes jurídicos de Bloomberg Law y Reuters sobre la exposición al arbitraje masivo en el sector tecnológico (2023–2024).\n\nPeríodo\tMecanismo de resolución de litigios de la SSA\tEfecto observado\tResultado\nBefore Sep 2024\tMandatory individual arbitration + class-action waiver\tIndividual litigation becomes economically irrational for users\tMass arbitration → $225M fee threat\nAfter Sep 2024\tDisputes in King County, WA courts only\tArbitration costs are avoided; cases consolidate in a single forum\tClass actions now possible\nConclusión\n\nDurante más de diez años, la SSA exigió a los usuarios que renunciaran a su derecho a un juicio con jurado a favor del arbitraje individual. Después de que las demandas masivas de arbitraje hicieran que ese mecanismo resultara económicamente oneroso para Valve, se modificó la SSA para remitir los litigios a los tribunales del condado de King. El cambio se presentó sin una opción de exclusión significativa; la alternativa a su aceptación era perder el acceso a los activos digitales adquiridos mediante la eliminación de la cuenta.\n\nAplicación algorítmica\nVACNet, la presunción de culpabilidad y los falsos positivos\n2023, octubre — AMD Anti-Lag+\n\nUna actualización del controlador de AMD (v23.10.1) activó la función Anti-Lag+ en CS2, lo que provocó la interceptación de funciones DLL del juego. VAC clasificó esto como inyección de código de trampa e impuso sanciones permanentes a miles de usuarios legítimos antes de que interviniera Valve.\n\n2023, diciembre — alta resolución (DPI)\n\nLos jugadores con un DPI superior a 10,000 que giraban la cámara rápidamente recibieron sanciones permanentes. VACNet no podía distinguir entre el movimiento físico del ratón y un truco de tipo «spinbot».\n\nCategoría de asistencia\tTiempo de respuesta declarado\tResultado real\nRefund requests\t50 min – 1.5 hr\tAutomatic approval (<14 days, <2 hours played)\nAccount security / recovery\t3–12 hours\tDepends on documentation provided\nContesting a VAC ban\tForm response\tComplete refusal. Support cannot reverse VAC decisions. The ban is permanent.\nPolítica oficial de «Valve»\n\n«Las exclusiones de VAC son permanentes, no negociables y el servicio de asistenciSteam no puede anularlas».\n\nEl mismo canal de asistencia que comunica la suspensión también comunica la denegación de la revisión: Steam. El servicio de asistencia afirma que no puede revocar una decisión del VAC. Para el usuario, el veredicto del algoritmo es el resultado definitivo.\n\nAspectos económicos de la reventa\nControl sobre los activos virtuales y la comisión por reventa\nLa comisión de mercado de «15%» CS2: el valor se deduce en cada reventa.\nIteración\tSaldo del comprador\tEl vendedor recibe\t«Burned» (15%)\n1\t$100.00\t$85.00\t$15.00\n2\t$85.00\t$72.25\t$12.75\n3\t$72.25\t$61.41\t$10.84\n10\t$23.16\t$19.68\t~$3.47\nTotal\t$100 → dust\tValve collects the 15% fee on each resale. Users must add new money to keep trading.\nCambio en la normativa de canje de CS2 — 2025 de octubre\n\nSin previo aviso, Valve modificó las normas del contrato de canje de CS2 para permitir la adquisición garantizada de cuchillos y guantes raros a cambio de objetos de calidad «Covert». Los precios de los cuchillos cayeron, los de los objetos «Covert» se dispararon y se produjo una ola de ventas motivadas por el pánico en todo el mercado.\n\nLa protección a la que se refiere Valve es la Sección 7 de la SSA: no se asume responsabilidad alguna por los cambios en las normas de la plataforma. Los usuarios asumen el riesgo en una economía cuyas normas Valve pueden cambiar sin previo aviso ni compensación. La cuantía de la pérdida estimada para todo el mercado es objeto de controversia y no se indica aquí a falta de una fuente primaria.\n\nRespuesta normativa europea\nLa UOKiK, la DSA y la Ley de Equidad Digital\nUOKiK — Polonia, 2024 de mayo\n\nLa autoridad de competencia de Polonia (UOKiK) ha iniciado un procedimiento formal antimonopolio contra Valve Corporation y cinco editoriales y distribuidoras de videojuegos nacionales en relación con una supuesta fijación de precios, cláusulas restrictivas de paridad de precios y prácticas de bloqueo geográfico que han provocado que los consumidores polacos paguen hasta un 20% más por los videojuegos digitales que en los mercados vecinos del EEE. Como parte de la investigación antimonopolio, los inspectores de la UOKiK y la policía llevaron a cabo redadas al amanecer e inspecciones de pruebas en las sedes polacas de los editores y distribuidores nacionales asociados (no en las oficinas filiales deValve, ya que Valve no cuenta con ninguna entidad en Polonia). Multa legal potencial: hasta el 10% de la facturación anual. Fuente: Comunicado oficial de la UOKiK: «El presidente de la UOKiK ha iniciado un procedimiento contra Valve y los creadores de los juegos», 2024 de mayo.\n\nLey de Servicios Digitales (DSA)\n\nExige transparencia en la moderación automatizada. Steam no publica datos sobre falsos positivos ni falsos negativos de VACNet, y en su canal de asistencia se indica que las decisiones de VAC no pueden revocarse.\n\nLey de Equidad Digital — 2026\n\nDisposiciones previstas: acceso duradero a contenidos de pago, prohibición de las prácticas engañosas en el momento de la renuncia a derechos, reconocimiento de los derechos de propiedad sobre los activos digitales y protección frente a la confiscación permanente de existencias.\n\nConclusión\nDiscrepancias documentadas entre las normas y los datos registrados\n1\n\nLa brecha en la propiedad. Los usuarios pagan el precio íntegro por una licencia que el contrato permite a Valve revocar. El Tribunal Supremo francés (octubre de 2024) dictaminó que la reventa digital no está protegida, consolidando así esa posición en la legislación.\n\n2\n\nAplicación algorítmica. VACNet ha impuesto sanciones injustificadas (controladores de AMD, incidentes relacionados con un DPI elevado). El servicio de asistencia de Steam afirma que no puede revocar una decisión de VAC, por lo que el algoritmo es la última palabra.\n\n3\n\nAhorro en las tasas. La comisión de mercado de «15%» CS2 (5%, Steam y 10%, comisión del editor) reduce el valor en cada reventa, y las normas de la plataforma pueden cambiar sin previo aviso; Valve se exime de toda responsabilidad por dichos cambios en virtud del SSA.\n\n4\n\nSe ha eliminado la cláusula de arbitraje. La SSA eliminó el arbitraje obligatorio en septiembre de 2024, después de que una avalancha de reclamaciones expusiera a Valve a unos225M en concepto de comisiones. Los usuarios no dispusieron de ninguna opción significativa para excluirse de este cambio.\n\n5\n\nCompetencia selectiva. Valve contrató a un bufete de abogados ruso (Melling, Voitishkin & Partners) y amenazó con iniciar procedimientos judiciales en Rusia contra Touch Skins, al tiempo que consideraba que sus obligaciones para con los usuarios de ese mismo mercado quedaban al margen de cualquier proceso judicial. Valve actúa como titular de los derechos cuando están en juego sus intereses comerciales, y como parte inalcanzable cuando se trata de los derechos de los usuarios.\n\n← Parte I: Cómo eludir los servidores proxy y los juegos de azarParte II: Acceso y rendición de cuentas →\n\nLas fuentes jurídicas y los expedientes judiciales se citan haciendo referencia a sus editores y repositorios originales. No se reivindica la titularidad de los documentos originales.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Análisis jurídico: condiciones de uso y cumplimiento normativo"
          },
          {
            "level": 2,
            "id": null,
            "text": "Exención de responsabilidad y licencia revocable"
          },
          {
            "level": 3,
            "id": null,
            "text": "2.1 El modelo de «suscripción» frente a los derechos de propiedad"
          },
          {
            "level": 3,
            "id": null,
            "text": "2.2 La ilusión del reembolso frente a la Directiva de la UE sobre los derechos de los consumidores"
          },
          {
            "level": 2,
            "id": null,
            "text": "Mercado secundario y defensa de la competencia"
          },
          {
            "level": 3,
            "id": null,
            "text": "UFC Que Choisir contra «Valve» — Francia"
          },
          {
            "level": 3,
            "id": null,
            "text": "Caso antimonopolio de Wolfire Games — Estados Unidos (En el asunto «Valve», n.º 2:21-cv-00563)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve Confesión oficial: Liquidaciones por fraude a nivel mundial (28, octubre de 2019)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Un titular de derechos en Rusia, con el que el usuario no puede ponerse en contacto"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve v. Touch Skins — reclamación de propiedad intelectual previa al juicio, Rusia"
          },
          {
            "level": 3,
            "id": null,
            "text": "La misma jurisdicción, pero en sentido contrario"
          },
          {
            "level": 2,
            "id": null,
            "text": "La capitulación de la cláusula de arbitraje"
          },
          {
            "level": 2,
            "id": null,
            "text": "VACNet, la presunción de culpabilidad y los falsos positivos"
          },
          {
            "level": 2,
            "id": null,
            "text": "Control sobre los activos virtuales y la comisión por reventa"
          },
          {
            "level": 3,
            "id": null,
            "text": "La comisión de mercado de «15%» CS2: el valor se deduce en cada reventa."
          },
          {
            "level": 3,
            "id": null,
            "text": "Cambio en la normativa de canje de CS2 — 2025 de octubre"
          },
          {
            "level": 2,
            "id": null,
            "text": "La UOKiK, la DSA y la Ley de Equidad Digital"
          },
          {
            "level": 2,
            "id": null,
            "text": "Discrepancias documentadas entre las normas y los datos registrados"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/es/#briefing-heading",
          "https://dota2.ru/news/67707-valve-cerez-uristov-napravila-krupnoj-rossijskoj-skincendzer-platforme-trebovanie-o-prekrasenii-deatelnosti/",
          "http://web.archive.org/web/20260924181657/https://dota2.ru/news/67707-valve-cerez-uristov-napravila-krupnoj-rossijskoj-skincendzer-platforme-trebovanie-o-prekrasenii-deatelnosti/",
          "https://shazoo.ru/2026/09/12/190508/valve-cerez-rossiiskix-iuristov-dobilas-zakrytiia-krupnogo-skinceindzera-dlia-cs2",
          "https://www.reddit.com/r/pcgaming/comments/1vf24lu/warning_to_all_gamersexpats_steam_took_my_money/",
          "https://phishdestroy.io/steam_dossier/es/card_economy.html#asymmetry",
          "https://tass.ru/obschestvo/23235387",
          "https://base.garant.ru/401414628/",
          "https://uokik.gov.pl/postepowanie-wyjasniajace-w-sprawie-valve-i-dystrybutorow-gier",
          "https://phishdestroy.io/steam_dossier/es/",
          "https://phishdestroy.io/steam_dossier/es/investigation_part2.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/es/legal_analysis.content.json",
      "export_json_sha256": "2c2a391b4e14bc1a4c83f807c3c4ad310b15ac0805459aac80b531902e1e65c0"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "es/license_disclaimer.html",
      "language": "es",
      "title": "Licencia · Derechos · Descargo de responsabilidad — PhishDestroy",
      "source_url": "https://phishdestroy.io/steam_dossier/es/license_disclaimer",
      "source_html_sha256": "f41e74dc31215dac73bae20148c1d3ec0a6f1d39abe2ba868cb0879d58d85e26",
      "exported_at": "2026-09-29T00:17:23.182Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "license_disclaimer.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/es/license_disclaimer.pdf?v=print-20260929-v5",
        "sha256": "d16c93fed96f885af567e3bc457966bf76a046adf1b616b3f077ff25bbe7713a",
        "bytes": 117143,
        "pages": 11
      },
      "integrity": {
        "signed_object": "license_disclaimer.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "license_disclaimer.content.json.asc",
        "digest_file": "license_disclaimer.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify license_disclaimer.content.json.asc license_disclaimer.content.json",
          "sha256sum -c license_disclaimer.content.json.sha256"
        ]
      },
      "content": {
        "text": "PHISHDESTROYInvestigación forense · Valve / Steam\nLicencia · Derechos · Exención de responsabilidad\nLicencia y aviso legal — Dedicación al dominio público\n\nTodos los derechos se rindió ante la humanidad.\n\nLO QUE DEMUESTRA ESTA SECCIÓN\n\nEl presente documento establece la cesión incondicional al dominio público (CC0 1.0 Universal) y las condiciones de licencia de software del MIT que rigen el PhishDestroy Steam Dossier. Todos los hallazgos forenses, conjuntos de datos probatorios, gráficos de red y metodologías analíticas se ceden de forma irrevocable al dominio público para su uso sin restricciones con fines normativos, jurídicos y académicos en todo el mundo.\n\n← Volver al informe ejecutivo\n\nPhishDestroy renuncia a cualquier derecho sobre este material: reproducirlo, venderlo o poner tu nombre en él. A continuación se incluyen dos documentos que adoptan un mismo tono: una carta abierta dirigida a Valve, redactada tal y como solemos escribir, y una renuncia formal redactada para la autoridad que se encargará de llevar adelante el proyecto.\n\nInvestigación · Valve Corporation / SteamEdición pública: sin fecha de caducidad, sin posibilidad de devolución\nEXENTADO\nSección ILicencia — la parte propiamente jurídica, pero desde un punto de vista humano\n\nPhishDestroy Renuncia a cualquier derecho sobre este material. Cero. Se acabó. Ya está. Puedes reproducirlo, venderlo, poner tu nombre en él, tatuárselo a tu jefe, lo que sea. No hace falta que me des crédito, ni que me envíes un mensaje directo, ni que me mandes una tarjeta de agradecimiento.\n\nUna regla de verdad (sí, solo una)\n\nNO te corresponde a TI decidir si eres un terrorista.\n\nSi eres un usuario de Rusia o de cualquier país sujeto a sanciones de la OFAC, este material NO es para ti. No hay escapatorias. Disfruta de tus sanciones.\n\nY si has cambiado la región de tu Steam a Turquía mientras estabas en Moscú… enhorabuena por tu creatividad geográfica. Sigues siendo ruso. Las sanciones siguen vigentes. Esa es, literalmente, la cuestión.\n\nSección IIQué es esto y por qué existe\n\nPublicaremos más información sobre Valve de la que conoce un empleado medio de Valve sobre sí mismo. No es por presumir. Simplemente es lo que ha acabado pasando.\n\n¿Cómo hemos llegado hasta aquí? Es una historia curiosa: Steam, básicamente, nos creó. Nos crió a base de sus estafadores, sus tickets de asistencia y su ecosistema de elusión de bloqueos… y ahora aquí estamos. Sin rencor. De hecho, resulta poético.\n\nPara aquellos que aún no hayan leído la historia de cómo empezó todo, ya hemos conocido a los carísimos abogados europeos de «Valve» (Taylor Wessing, ya que lo preguntas):\n\nhttps://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d archivado en 2026-08-21 ↗\n\nUn encuentro encantador. Sobre todo teniendo en cuenta su tarifa por hora.\n\n¿Lo sabía «Valve»? Sí. ¿Lo sabía «Taylor Wessing»? Es casi seguro que sí. Pero cuando se es tan rico, las leyes son más una cuestión de actitud que una obligación, ¿no?\n\nEn realidad, eso es más o menos toda la respuesta.\n\nSteam Llevamos años dedicándonos a los estafadores. No siempre de forma intencionada: a veces, los estafadores simplemente acababan teniendo la huella de «Valve» por asociación. No pretendemos ser dramáticos al respecto. Intentamos ser precisos. Para ser sinceros, eso nos resulta más difícil que ser dramáticos: simplemente, así es como escribimos.\n\n¿Se trata de un conflicto?\n— No.\n\n¿Se puede resolver?\n— Sí. Pero no vamos a firmar ningún acuerdo de confidencialidad ni vamos a participar en programas de recompensa por errores a cambio de cuatro duros.\n\nEsperamos más de 4 años a que solucionaran el problema de la suplantación de identidad antes de poder escribir sobre ello públicamente. Porque si hubiéramos escrito sobre ello antes, Steam habría puesto su carita de víctima y habría gritado «¡amenaza activa!», y nos habría ofrecido unas migajas a cambio de que firmáramos un documento que nos habría convertido en su propiedad legal para siempre. No, gracias.\n\n(Además: la propia «Valve» incumple el acuerdo de confidencialidad. Lo hacen sus propios empleados. Los que están en los puestos más altos. Pero claro, hablemos de los nuestros.)\n\nSección IIICarta abierta a «Valve» — En serio, lee esto\n\nValve: si quieres que se elimine este dominio, envíanos un correo electrónico. No es necesario recurrir a un asesor jurídico externo para esa conversación.\n\nPara los que no lo sepan: el Dr. Patrick tiene un máster en Derecho Mercantil Internacional por la Universidad de Aberdeen y —atención— terminó, literalmente, su tesis doctoral en Derecho de las Tecnologías de la Información. Recientemente se ha convertido en socio de Taylor Wessing, un bufete cuyo modelo de negocio consiste en cobrar a empresas como Valve cantidades exorbitantes de dinero para alargar los procesos hasta que la otra parte se quede sin dinero o se agote su paciencia.\n\nNo le echamos la culpa. Clientes ricos y culpables que pagan por horas: una jugada profesional muy acertada. Simplemente creemos que tú no deberías financiarlo.\n\nEl trato (oferta abierta, sin necesidad de abogados)\n\nEl dominio es lo único a lo que Valve puede aspirar de forma realista. La investigación, las remisiones y los recursos asociados ya están en marcha; seguirán adelante con o sin el dominio.\n\nSi quieres el dominio:\n\nDeja que tus expertos en derecho de las tecnologías de la información fijen un precio justo.\n\n50% se destina a la Fundación «SEAL».\n\nEliminamos el dominio. Sin dramas. Sin tribunales. Listo.\n\nEsto no es una amenaza. Es una oferta clara por lo único que realmente está a tu alcance. No lo conseguirás de ninguna otra forma; así es como están las cosas.\n\n¿Vamos a «perjudicar» directamente a Valve? Probablemente no de una forma que les afecte económicamente. No nos hacemos ilusiones. Pero lo haremos con honestidad, abiertamente, sin buscar influencia, porque no la necesitamos. Necesitamos que el mundo vea lo que siempre ha estado a la vista de todos si uno se tomaba el tiempo suficiente para fijarse.\n\nDisponemos de un5es años de archivos. Lo que los abogados de Valve presentaron durante la fase de presentación de pruebas —los datos a los que tienen acceso los agentes de apoyo, las huellas dactilares, el rastro documental que, literalmente, nos entregaron— es suficiente. No necesitamos filtrarlo sin procesar.\n\n¿Quién se queda con qué?\n\nLas autoridades reguladoras reciben los originales.\n\nLos investigadores y periodistas reciben versiones censuradas (en las que se han eliminado, por razones obvias, las denuncias de las víctimas, los datos de acceso de los menores y los encantadores comentarios de apoyo de Valve).\n\nEntre las cuentas afectadas había menores, a los que no se les notificó nada. Esta conclusión figura en el expediente del regulador, del que se han eliminado los informes de las víctimas y los datos de identificación, ya que es un asunto que debe tratarse ante una autoridad de protección de datos y no en un artículo.\n\nAdemás, Valve: queremos dejar algo claro antes de que decidas cómo actuar al respecto: PhishDestroy es una comunidad, no una persona. Ya lo supiste cuando enviaste correspondencia legal a la comunidad sin molestarte en hablar con ella; simplemente la aprovechaste para obtener datos y bloqueaste las cuentas.\n\nLa comunidad no tiene ningún conflicto con Valve. No fuimos nosotros quienes buscamos esto. Los estafadores que vosotros habéis fomentado nos encontraron a nosotros. Los hemos bloqueado. Y aquí estamos.\n\nSección III-BLos recursos aliados — una nota dirigida específicamente a Steam\n\nQueremos ser sinceros en cuanto a la estructura de amplificación, porque fingir que no existe sería deshonesto.\n\nSegún tenemos entendido, PhishDestroy cuenta con al menos dos recursos aliados que se harán cargo de este material y le darán continuidad.\n\nLo que eso significa en la práctica:\n\nCada uno aborda desde su propio punto de vista los temas que se solapan.\n\nSon independientes: no siguen nuestras indicaciones, ni nosotros las suyas. El tema general es el mismo, pero la metodología es diferente.\n\nNO van a actuar en la Parte 1.. Están al tanto.\n\nSi Valve decide no retirar la página web:\n\nEs de esperar que aparezcan tras la «Parte2» o la «Parte3.».\n\nTomarán lo que les resulte útil de nuestro trabajo, lo complementarán con el suyo propio y lo publicarán bajo su propia autoría.\n\nEsto es precisamente para lo que está pensada la licencia de la sección 1: el material llega a donde tiene que llegar, se complementa, se amplía… y ni nosotros ni ellos nos debemos mutuamente ninguna atribución.\n\n(P. D. para los abogados que se pregunten por las cadenas de responsabilidad: no hay ninguna. Estos recursos no reciben instrucciones, financiación ni datos nuestros. Leen lo que es de dominio público y sacan sus propias conclusiones. Igual que haríais vosotros.)\n\nNo decimos esto para intimidar. Lo decimos para que quienquiera que esté elaborando estrategias por parte de «Valve» disponga de información precisa sobre cómo es realmente el entorno informativo.\n\nUn recurso que recopile nuestra información y la complemente sería un reportaje. Dos recursos que lo hagan de forma independiente y lleguen a conclusiones similares constituyen un patrón. Los patrones son lo que llaman la atención de las autoridades reguladoras.\n\nSección IVEl dinero, las prohibiciones, todo este circo\n\nLo que pasa con la prohibición de los sitios web de apuestas y los estafadores por parte de la «Steam» es que no se trata de hacer cumplir la ley, sino de recaudar ingresos. Valve se embolsa el dinero, se lava las manos y luego sale a escena para contar a todo el mundo una historia edulcorada sobre las cartas de Pokémon y el béisbol.\n\nEn los casos en los que se han documentado casos de vulnerabilidades en el servicio de asistencia —incluida la admisión por escrito de «Valve» en febrero 2023, en la que asumía la responsabilidad por la filtración de cuentas de alto valor a través de solicitudes de ayuda, y los despidos de personal subcontratado de los que informaron Dexerto y Escorenews tras el caso de uso de información privilegiada por valor de320k (Parte II, §04 · Dossier principal §14.1) — se basan en declaraciones públicas y en reportajes de investigación. Los rumores sin fundamento sobre miembros del personal de apoyo que se dedican a actividades de juego paralelas o que cobran un porcentaje a cambio de levantar prohibiciones no están respaldados por datos públicos y, por lo tanto, no se incluyen aquí.\n\nMientras tanto, Valve eliminó la posibilidad de realizar un seguimiento adecuado de los skins en 2017.. Incluso lo debatieron en sus propios foros. Lo denominaron «medidas contra las apuestas», aunque el ecosistema de apuestas con skins siguió canalizando miles de millones a través de la infraestructura de Steam durante años después de eso. Una estrategia de marca estupenda.\n\nVamos a demostrar que:\n\nLas «skins» son más anónimas que Monero\n\nAl parecer, un cártel peruano utilizó skins de Dota 2 para mover dinero\n\nSteam es, en la práctica, una máquina para eludir sanciones valorada en unos ~7B en «cromos» (sí, de verdad le dijeron «cromos» a un fiscal)\n\nTenemos un vídeo sobre lo de las skins. Ya lo verás.\n\nTambién sabemos que:\n\nLa moderación de Reddit se rige por Valve\n\nInfraestructura de datos de terceros de Steam (como steamid.uk) está gestionado por un particular (msart) cuyo proyecto asociado sobre la lista de prohibiciones (steambans.com archivo) está coadministrado por un moderador confirmado de la comunidad Valve (killahinstinct_) — lo que deja la auditoría independiente de las expulsiones de la plataforma totalmente en manos de «Valve» (Véase «Economía de las cartas», apartado «08»)\n\nLo que no pueden controlar, lo prohíben\n\nValve: si sigues haciéndote el tonto, no pasa nada. Ya sabemos cuál es tu refugio seguro. De todos modos, Google Analytics oculta las direcciones IP de tus usuarios. Vemos lo que se borra. Simplemente no podemos demostrarlo de forma lo suficientemente barata como para que a tus abogados les importe. De momento.\n\nSección VEl tema del malware — Sí, lo vamos a mencionar\n\nSeamos brutalmente claros sobre la secuencia de los hechos, porque eso pone de manifiesto exactamente quién eres.\n\nNO vamos a hacer pública la vulnerabilidad del juego. NO la vamos a comunicar a Steam. El programa exige un acuerdo de confidencialidad, y firmarlo nos impediría informar a los usuarios afectados de lo que ha ocurrido con sus cuentas. El objetivo de este trabajo es informar a las personas que han perdido esas cuentas y a las autoridades reguladoras; un acuerdo de confidencialidad es incompatible con ello.\n\nEsto es lo que ocurrió realmente: esta vulnerabilidad es prácticamente un secreto a voces en los círculos adecuados. Sabemos a ciencia cierta que investigadores de seguridad independientes ya le han restregado el exploit completo directamente a la cara al servicio de soporSteam. Esa parte ya está hecha. Se os ha advertido oficialmente a través de vuestros propios canales formales.\n\n¿Y qué hizo «Valve»? Absolutamente nada. Porque para «Valve», la seguridad no es sinónimo de beneficios; de hecho, es justo lo contrario. La seguridad es una fuente de gastos. Hasta que una amenaza alcanza una magnitud crítica y provoca una crisis catastrófica de relaciones públicas, «Valve» no la considera urgente.\n\nEntonces, ¿qué estamos haciendo? Estamos informando al público de que existe, porque el hecho de que «Valve» sea consciente de una amenaza sistémica de malware y opte activamente por no hacer nada es un dato fundamental para los reguladores que estén leyendo esto en estos momentos.\n\nEl juego es enorme. No vamos a decir cuál es aquí. Pero tened en cuenta lo siguiente:\n\nEsto NO es esa basura trivial de los «script-kiddies» de CS:GO en la que un servidor te pide que «instales un controlador». Esto es catastrófico.\n\nEsto es una pesadilla al estilo de Unturned: ejecución de código remoto (RCE) sin necesidad de hacer clic al conectarse al servidor. Te unes a un servidor. No haces clic en nada. No descargas nada. La propia conexión es la superficie de ataque, y tu equipo queda totalmente comprometido. Seamos realistas: lanzar un RCE y eludir los antivirus locales aprovechándose de los certificados digitales de confianza de Valve ya ni siquiera es una novedad en Steam. Es prácticamente una característica integrada en tu ecosistema.\n\nValve ya sabe que esto existe. Pero se amparan en su coartada legal favorita y cobarde: dado que, técnicamente, el juego lo ha desarrollado un tercero, Valve se lava las manos. Distribuyen el juego, gestionan los pagos y alojan la infraestructura, pero cuando un RCE de «cero clics» amenaza a millones de sus usuarios, su postura es: «No es nuestro juego, no es nuestra responsabilidad».\n\nCuando esto, inevitablemente, salga a la luz, el desarrollador externo será el que cargue con la culpa, y Valve se librará fingiendo ser la plataforma responsable que «colaboró» en la resolución del problema. La clásica cobardía de Valve. Ya conocemos el guion.\n\nDejamos constancia de esto para que las autoridades reguladoras, los fiscales y los periodistas comprendan exactamente cómo gestiona Valve el malware activo: escondiéndose tras desarrolladores externos, imponiendo acuerdos de confidencialidad que impiden hablar del tema y dejando a los jugadores en una situación de total indefensión.\n\nFin de la carta abiertaComienza el plazo de inscripción\nEstilo formal · para las autoridades\nDeclaraciónEn cuanto al uso y los derechos\n\nPhishDestroy Coalición para los Proyectos y la Ciberseguridad\n\nEsta declaración acompaña a cada documento presentado y a cada prueba adjunta en este expediente. Va dirigida a cualquier autoridad, tribunal, organismo regulador, fiscal, investigador, periodista o persona afectada a quien llegue este material.\n\n1. No hay condiciones de uso\n\n1.1 Todo el material elaborado por la Coalición en el marco de este expediente —las exposiciones de los hechos, el análisis, las pruebas documentales que ha elaborado, las herramientas y las conclusiones— se publica SIN RESERVA ALGUNA DE DERECHOS.\n\n1.2 Cualquier persona puede, sin pedir permiso y sin avisarnos:\n\nreproducirlo, total o parcialmente;\n\nadaptarlo, editarlo, reescribirlo, reestructurarlo o corregirlo;\n\ntradúcelo;\n\nextraerlo sin indicar que se trata de un extracto;\n\nincorporarla en documentos oficiales, conclusiones, resoluciones, escritos procesales, informes o material de prensa;\n\npresentarlo como si fuera obra propia del destinatario o como si fueran conclusiones propias del destinatario;\n\nutilizarlo como materia prima y desechar el resto;\n\ny transmitirlo a cualquier otra persona en las mismas condiciones.\n\n1.3 NO SE EXIGE NI SE SOLICITA NINGÚN TIPO DE ATRIBUCIÓN. No es necesario nombrar, citar, mencionar, dar las gracias, consultar ni informar a la Coalición. Si el material de esta referencia resulta de ayuda a una autoridad y nunca se menciona a la Coalición, ESE RESULTA UN RESULTADO TOTALMENTE SATISFACTORIO, y la Coalición lo declara por adelantado para que no sea necesario plantear la cuestión.\n\n1.4 Si, por el contrario, una autoridad considera más conveniente citar a la Coalición como fuente, es libre de hacerlo. La elección depende exclusivamente del destinatario y ninguna de las dos opciones conlleva consecuencia alguna.\n\n1.5 El presente documento es una RENUNCIA, no una oferta de licencia. No requiere aceptación, no impone ninguna obligación y no puede ser incumplido. El software publicado por la Coalición se distribuye por separado bajo la licencia MIT; la investigación y los resultados se ceden al dominio público en la medida máxima permitida y, en aquellos casos en que una jurisdicción no permita la renuncia, la Coalición concede una licencia irrevocable, mundial y libre de derechos de autor con el mismo efecto.\n\n2. Por qué esto es importante en la práctica, y no solo por una cuestión de cortesía\n\n2.1 Una autoridad puede tener dudas fundadas a la hora de basarse en información facilitada por un tercero, por temor a que parezca que actúa a instancias de dicho tercero o a verse implicada de alguna manera con él.\n\n2.2 AQUÍ NO HAY NADA CON LO QUE ENREDARSE. La Coalición no pide nada, no se le debe nada, no retiene nada y no tiene expectativa alguna. No podrá posteriormente hacer valer ningún derecho, atribuirse el mérito, quejarse de un uso indebido ni oponerse a cómo se caracterice el material, ya que no ha conservado ningún fundamento sobre el que basarse para hacerlo.\n\n2.3 Por lo tanto, una autoridad que utilice este material no está actuando en nombre de la Coalición. Simplemente está utilizando información pública que, casualmente, ha sido recopilada por otra persona.\n\n3. Ya está todo abierto\n\n3.1 El trabajo de la Coalición es público por defecto:\n\nLas investigaciones se publican abiertamente en https://phishdestroy.io y se pueden leer libremente;\n\nLas herramientas se publican como código abierto bajo la licencia MIT en https://github.com/phishdestroy archivado en 2026-09-11 ↗;\n\nLa metodología se detalla en la propia remisión, en el anexo A, sección A.16D, incluyendo la ponderación y las limitaciones de cada tipo de fuente;\n\nLa Coalición no acepta donaciones y ha hecho pública esta postura desde el 2018.\n\n3.2 El único material que NO se publica es aquel que no puede publicarse de forma legal o segura: los datos personales de las víctimas y de terceros, así como la información que podría exponer a una fuente a represalias. Dicho material se facilita a las autoridades de forma confidencial y se identifica en los anexos de pruebas.\n\n3.3 La Coalición invita a que se examine su propia conducta en las mismas condiciones en que invita a examinar la de cualquier otra persona, y ha puesto a disposición de las autoridades competentes, de forma voluntaria, la información relativa a su gestión de datos, incluida una solicitud de instrucciones sobre su eliminación.\n\n4. Integridad del conjunto de pruebas\n\n4.1 Los anexos se adjuntan a la solicitud o, cuando así se indique, se facilitan previa solicitud a través de un canal seguro. No se publican en ninguna dirección pública y no debe deducirse ninguna dirección de este tipo: este tipo de material se facilita directamente a las autoridades.\n\n4.2 Cada entrega va acompañada de un archivo SHA256SUMS que recoge un resumen SHA-256 de cada archivo suministrado, junto con una firma independiente de OpenPGP SHA256SUMS.asc.\n\n4.3 La clave de firma se encuentra publicada en https://phishdestroy.io/.well-known/pgp-key.txt y en keys.openpgp.org. Su marca distintiva aparece en el membrete de cada documento de este conjunto.\n\n4.4 Cualquier destinatario puede comprobar en cualquier momento que el archivo que tiene en su poder es el mismo que se le envió, sin modificaciones:\n\ngpg --verify SHA256SUMS.asc SHA256SUMS\n\nsha256sum -c SHA256SUMS\n\n4.5 El objetivo no es una mera formalidad. Se hace para que, si en el futuro se cuestiona la exactitud o la integridad de alguna prueba documental, la cuestión pueda resolverse mediante un cálculo y no mediante una discusión.\n\n5. A propósito de la inscripción: por qué la exención es funcional y no solo un gesto de generosidad\n\n5.1 Es posible que las autoridades se topen con las investigaciones publicadas por la Coalición y las consideren directas, polémicas y, en ocasiones, satíricas. Esa impresión es acertada. La Coalición escribe así de forma deliberada y no se disculpa por ello.\n\n5.2 ASIMISMO, RECONOCE QUE ESTE NO ES EL TONO ADECUADO PARA UN PROCEDIMIENTO REGULATORIO O JUDICIAL. Un asunto grave no debe tratarse en el tono de una campaña. Las conclusiones presentadas ante una autoridad deben exponerse de forma directa, admitiendo sus limitaciones, y no deben obligar al lector a hacer caso omiso del tono para poder llegar al fondo del asunto.\n\n5.3 ESA ES PRECISAMENTE LA RAZÓN POR LA QUE LA COALICIÓN RENUNCIA A LA AUTORÍA. La renuncia que figura en la sección 1 es el mecanismo mediante el cual se puede separar el contenido del registro: la autoridad puede tomar lo que le resulte útil, reformularlo con sus propias palabras y descartar cada palabra del estilo de la Coalición, junto con el nombre de esta. Al hacerlo no se pierde nada, y la Coalición lo prefiere así.\n\n5.4 LA COALICIÓN TAMBIÉN PIDE QUE NO SE CONFUNDA EL REGISTRO CON EL MÉTODO. El tono utilizado es combativo; la práctica subyacente no es descuidada. A lo largo de esta remisión, se separa la inferencia de la observación, se identifica el testimonio como tal, se evalúan las fuentes y se señalan sus puntos débiles, se presentan las cifras con sus limitaciones, y los puntos que la Coalición no puede demostrar se plantean como preguntas dirigidas a la autoridad, en lugar de como afirmaciones. Cuando las pruebas iban en contra de la propia posición de la Coalición, esta así lo ha señalado; véase el anexo A, párrafo 7, y sección B.0 de la remisión paralela.\n\n5.5 LA COALICIÓN EXPLICA LA RELACIÓN ENTRE SU FORMA DE ACTUAR Y SUS FINANZAS, YA QUE AMBAS SON INSEPARABLES. No acepta dinero de nadie: ni donaciones, ni recompensas, ni clientes, ni patrocinadores. Esa negativa es lo que hace posible su franqueza: una organización con ingresos que proteger debe moderar lo que dice sobre los partidos de los que depende. Al no tener nada que proteger, la Coalición no tiene nada que moderar.\n\nEsa es también la razón por la que la Coalición sigue existiendo. No hay ningún otro motor. El trabajo se lleva a cabo porque se lleva a cabo; se detiene cuando las personas que lo realizan dejan de hacerlo.\n\n5.6 La autoridad no tiene por qué aceptar nada de esto. Se señala esto para que el tono de la labor pública de la Coalición no se interprete como un indicador del cuidado que se ha puesto en el material que ahora tiene ante sí.\n\n6. Lo que ofrece la Coalición, según sus propias palabras\n\nInformación, investigación y observación.\n\nNo se afirma nada como una conclusión sobre la que la Coalición no tenga legitimación para pronunciarse. Cuando se deduce algo, el informe así lo indica. Cuando algo se basa en un testimonio, el informe señala de quién es y con qué limitaciones. Cuando la Coalición no puede responder a una pregunta, también lo indica e identifica quién puede hacerlo.\n\nLa Coalición no busca ninguna reparación, ningún pago, ningún reconocimiento ni ningún resultado para sí misma ni para ninguna persona en particular. Solo pide que las preguntas formuladas en la remisión sean planteadas a la corporacióValve por un organismo con facultades para exigir una respuesta.\n\nNota finalA quienquiera que se encargue de esto\n\nQueremos dar las gracias a quienquiera que se encargue de hacer llegar este material a su destino. Probablemente no será un proceso rápido. «Valve» tiene mucho dinero y Taylor Wessing cobra por horas; esa combinación está diseñada específicamente para que personas como tú se rindan antes de llegar a la meta.\n\nSabemos lo que hacemos. Sabemos sobre quiénes escribimos. «Valve» nos ha forjado; ¿cómo no íbamos a entenderlos?\n\nPhishDestroy No hay ningún conflicto con Valve. Hemos bloqueado la única red de estafadores de esa envergadura con la que nos hemos topado; no hemos ido a buscar pelea con Valve. Simplemente resultó que todos los caminos conducían hasta ellos. No es un conflicto. Solo es una cuestión de topología.\n\nValve No se puede resolver la situación de «PhishDestroy» porque no hay nada que resolver. No tenemos ninguna relación. Los datos sobre sus esquemas de enriquecimiento y sus beneficios desmesurados son, en gran medida, públicos; solo hay que dedicar el tiempo suficiente a buscarlos. Piensa en ello como una enciclopedia del éxito: «Cómo no cumplir las sanciones para que los hackers rusos no puedan piratear nuestros juegos gratuitos (los de pago, que de todos modos no piratearían)». Ya te haces una idea.\n\nNo necesitamos la autoría.\n\nNo necesitamos que se cite la fuente.\n\nNo necesitamos ganar.\n\nNecesitamos a alguien con autoridad real para plantear a Valve las preguntas que ya figuran en esta remisión, y que tenga la facultad de exigir una respuesta.\n\nEso es todo. Eso es todo lo que pedimos.\n\nLos casos se publicarán en:\n\nhttps://steamdestroy.eth/\n\nhttps://steamdestroy.eth.limo (ahora mismo no funciona; lo arreglaré cuando sea necesario)\n\nEstaremos en:\n\nhttps://phishdestroy.eth.limo/ archivado en 2026-06-27 ↗\n\nhttps://phishdestroy.eth/\n\nDos objetos firmados · derechos y texto publicado\nAutorización firmadaQué se ha firmado y qué abarca\n\nA continuación se muestran, por separado, los objetos JSON de la concesión de derechos y el texto de investigación. Cada firma independiente OpenPGP autentifica los bytes exactos del JSON que figura junto a ella. La declaración de derechos concede permisos; la instantánea del texto identifica y contiene el material que se publica.\n\n1. Declaración de derechos — license-rights.json\n\nObjeto firmado: el completo license-rights.json Archivo que contiene la concesión de derechos de uso público con fecha del 28 de septiembre de 2026.. En ella se concede permiso para copiar, publicar, editar, traducir, combinar y comercializar los materiales del dossier sin necesidad de atribución, notificación ni autorización. Esta firma autentifica la declaración de derechos; no autentifica el texto de cada página web o PDF.\n\nLa autorización original firmada se mantiene sin modificaciones. La concesión de derechos que en ella se establece no puede revocarse ni restringirse mediante cambios en el sitio web, la publicación de otro archivo o la retirada del sitio de la red. Los materiales de terceros conservan sus propios derechos.\n\nDeclaración de derechos en formato JSON ↗ · Firma de license-rights.json ↗ · SHA-256, de license-rights.json ↗\n\ngpg --verify license-rights.json.asc license-rights.json\nsha256sum -c license-rights.json.sha256\n2. Texto publicado — dossier-text.json\n\nObjeto firmado: el completo dossier-text.json archivo. Contiene el texto legible de las páginas exportadas en documents[].content.text, con el título de cada página, el idioma, la URL de origen, el hash del código HTML de origen, los encabezados y las referencias. El documents La lista recoge el inventario exacto que abarca esta instantánea; las variantes lingüísticas se enumeran por separado. Se trata de una publicación de texto, no solo de una lista de hash.\n\nCada entrada identifica su PDF de página ligera mediante el nombre de archivo y el SHA-256o en documents[].pdf. El archivo JSON también identifica la declaración de derechos original mediante la URL y el SHA-256,, de modo que el texto publicado, su PDF y la autorización de derechos correspondiente puedan relacionarse sin necesidad de conjeturas. Las bases de datos externas vinculadas, las imágenes originales y las páginas que no figuran en el inventario no están incluidas en esta instantánea del texto.\n\nTexto completo en formato JSON firmado ↗ · Firma de dossier-text.json ↗ · SHA-256, de dossier-text.json ↗\n\ngpg --verify dossier-text.json.asc dossier-text.json\nsha256sum -c dossier-text.json.sha256\n\nEn la página de inicio del dossier, los botones «PDF» y «JSON» permiten exportar el conjunto de documentos de investigación. En una página interior, permiten exportar esa página en el idioma en el que se ha publicado. Además, cada archivo JSON de página cuenta con su propia firma independiente y su propio archivo SHA-256, cuyo nombre se indica explícitamente en su integrity objeto. Para verificar el PDF asociado, calcula su SHA-256 y compáralo con el pdf.sha256 valor en el JSON verificado. El PDF está vinculado a ese resumen; no incluye una firma digital en formato PDF.\n\n3. Paquete de investigación imprimible — steam-dossier-{language}.content.json\n\nObjeto firmado: el archivo JSON completo específico para cada idioma, que incluye el texto del capítulo incluido en documents[].content.text, los rangos de páginas de los capítulos, los idiomas de origen, el inventario de fuentes excluidas y el resumen exacto del PDF en pdf.sha256. Los cinco archivos de material complementario siguen estando vinculados en línea y no se agrupan. Se conserva el texto de la investigación original; los catálogos visuales se sustituyen por enlaces a las fuentes.\n\nJSON en inglés ↗ · Firma de «OpenPGP» en un documento independiente ↗ · Resumen de SHA-256 ↗\n\nAlemán JSON ↗ · Firma de «OpenPGP» en un documento independiente ↗ · Resumen de SHA-256 ↗\n\ngpg --verify steam-dossier-en.content.json.asc steam-dossier-en.content.json\nsha256sum -c steam-dossier-en.content.json.sha256\n\nClave pública de verificación ↗\n\nHuella digital de la firma: 129F C7F3 9C40 C69D 2EF3 C329 BFCF 9E8D D295 EE01\n\ngpg --import pgp-key.txt\ngpg --fingerprint 129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01\n\nComprueba que la huella digital que se muestra coincida con la de arriba y, a continuación, verifica la firma con el nombre exacto del archivo JSON. La edición de un archivo JSON firmado modifica el objeto firmado e invalida su firma original. Una firma válida identifica los bytes publicados; no constituye una verificación independiente de los resultados de la investigación.\n\nPhishDestroy — investigación pública — todos los derechos cedidos a la humanidad\n\nAcceso a la región de la OFAC: prohibido",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Licencia y aviso legal — Dedicación al dominio público"
          },
          {
            "level": 2,
            "id": null,
            "text": "Sección ILicencia — la parte propiamente jurídica, pero desde un punto de vista humano"
          },
          {
            "level": 3,
            "id": null,
            "text": "Una regla de verdad (sí, solo una)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Sección IIQué es esto y por qué existe"
          },
          {
            "level": 2,
            "id": null,
            "text": "Sección IIICarta abierta a «Valve» — En serio, lee esto"
          },
          {
            "level": 3,
            "id": null,
            "text": "El trato (oferta abierta, sin necesidad de abogados)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Sección III-BLos recursos aliados — una nota dirigida específicamente a Steam"
          },
          {
            "level": 2,
            "id": null,
            "text": "Sección IVEl dinero, las prohibiciones, todo este circo"
          },
          {
            "level": 2,
            "id": null,
            "text": "Sección VEl tema del malware — Sí, lo vamos a mencionar"
          },
          {
            "level": 2,
            "id": null,
            "text": "DeclaraciónEn cuanto al uso y los derechos"
          },
          {
            "level": 3,
            "id": null,
            "text": "1. No hay condiciones de uso"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. Por qué esto es importante en la práctica, y no solo por una cuestión de cortesía"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. Ya está todo abierto"
          },
          {
            "level": 3,
            "id": null,
            "text": "4. Integridad del conjunto de pruebas"
          },
          {
            "level": 3,
            "id": null,
            "text": "5. A propósito de la inscripción: por qué la exención es funcional y no solo un gesto de generosidad"
          },
          {
            "level": 3,
            "id": null,
            "text": "6. Lo que ofrece la Coalición, según sus propias palabras"
          },
          {
            "level": 2,
            "id": null,
            "text": "Nota finalA quienquiera que se encargue de esto"
          },
          {
            "level": 2,
            "id": null,
            "text": "Autorización firmadaQué se ha firmado y qué abarca"
          },
          {
            "level": 3,
            "id": null,
            "text": "1. Declaración de derechos — license-rights.json"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. Texto publicado — dossier-text.json"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. Paquete de investigación imprimible — steam-dossier-{language}.content.json"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/es/#briefing-heading",
          "https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "http://web.archive.org/web/20260821155801/https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "https://phishdestroy.io/steam_dossier/es/investigation_part2.html#outsourcing-case",
          "https://phishdestroy.io/steam_dossier/es/#theft-ledger",
          "https://steamid.uk/",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/groups/steambans",
          "https://steamcommunity.com/id/killahinstinct_",
          "https://phishdestroy.io/steam_dossier/es/card_economy.html#governance",
          "https://phishdestroy.io/steam_dossier/es/license_disclaimer.html",
          "https://github.com/phishdestroy",
          "http://web.archive.org/web/20260911040557/https://github.com/PhishDestroy",
          "https://phishdestroy.io/.well-known/pgp-key.txt",
          "https://steamdestroy.eth/",
          "https://steamdestroy.eth.limo/",
          "https://phishdestroy.eth.limo/",
          "http://web.archive.org/web/20260627040219/https://phishdestroy.eth.limo/",
          "https://phishdestroy.eth/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json.asc",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json.sha256",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json.sha256?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json.sha256?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json.sha256?v=print-20260928-v3"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/es/license_disclaimer.content.json",
      "export_json_sha256": "a941d095ed8efdc1479f8cae0dd8fd54730515da0e20708603293c3850d5d052"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "es/market_economics.html",
      "language": "es",
      "title": "Una infraestructura, dos mercados: el dossier «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/es/market_economics",
      "source_html_sha256": "14f91a6ac48c313195879ca4137274bcf0e41ce54a3fe2393f61976f5b721734",
      "exported_at": "2026-09-29T00:17:23.526Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "market_economics.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/es/market_economics.pdf?v=print-20260929-v5",
        "sha256": "00e131e779cd681958ddc74510fd57f20ee1a4949b8e4b295d225f3d04e080cf",
        "bytes": 97646,
        "pages": 8
      },
      "integrity": {
        "signed_object": "market_economics.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "market_economics.content.json.asc",
        "digest_file": "market_economics.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify market_economics.content.json.asc market_economics.content.json",
          "sha256sum -c market_economics.content.json.sha256"
        ]
      },
      "content": {
        "text": "Anexo VII · Arquitectura del mercado · 20 2026 de septiembre\nEconomía de mercado: dos economías y el límite máximo de cotización\n\nSu infraestructura. Dos economías.\n\nLO QUE DEMUESTRA ESTA SECCIÓN\n\nEn este capítulo se analiza la bifurcación sistémica del mercado provocada por el límite de cotización de Valve, fijado en $1,800, y los saldos de monedero no retirables. Tras examinar 38 las plataformas externas activas de intercambio de skins que cuentan con una valoración cotizada de aproximadamente1.28 mil millones de dólares, la investigación demuestra que las operaciones de alto nivel migran necesariamente a plataformas paralelas externas, al tiempo que dependen de la infraestructura subyacente de transacciones y autenticación de Steam. Aunque el uso comercial está formalmente prohibido en el Acuerdo de Suscriptor, Valve facilita y monetiza esta economía de dos niveles sin que existan registros públicos de su aplicación.\n\n← Volver al informe ejecutivo\n\n38 mercados de CS2 de terceros activos, además del propio de Steam. Todas las skins que figuran en cualquiera de ellas deben pasar por el inventario de Steam y comercializarse en API. Las normas de Valve prohíben la explotación comercial de dicha infraestructura. El valor estimado en unos $1.28 mil millones, según fuentes externas, sigue existiendo, aunque no se ha encontrado ningún registro público que demuestre que se haya aplicado dicha norma.\n\n$1.28B\nValor de cotización de terceros · Plataformas de «38»\n53.2M\nOfertas mostradas · 38 mercados de terceros\n70.1K\nSteam elementos que figuran en la instantánea\n41×\nValor cotizado por terceros frente a los $31M de Steam\nLa conclusión principal\nUna infraestructura. Dos economías.\n\nSteam controla el artículo, el inventario y el comercio. Cada skin que se venda en cualquiera de las plataformas que figuran a continuación debe pasar por la plataforma de intercambio de Steam API —una dependencia estructural que se puede observar directamente. El «Community Market» de Valve obtiene una comisión por sus ventas; en este documento no se aclara si dicha comisión financia el ecosistema de terceros ni si está vinculada a él.\n\nPor qué esto es importante para la investigación\n1\nAcuerdo de suscripción a «Steam» de Valve prohíbe la explotación comercial de la infraestructura de «Steam» sin autorización expresa. No se ha encontrado dicha autorización en los registros públicos para las plataformas que se indican a continuación.\n2\nSteam controla la identidad (OpenID), el estado de las existencias y la ejecución de las operaciones de los aproximadamente1.28mil millones de dólares en activos cotizados de terceros. No se produce ninguna transferencia de artículos sin la infraestructura de Valve.\n3\nEl mercado propio de Steam cuenta con $31M cotizados: aproximadamente un1/41e del valor de cotización de terceros. El límite máximo de precio de $1,800 significa que los vendedores que lo superen deben salir de la plataforma para vender a los precios observados.\n4\n248 Categorías de artículos de CS2, cuyos precios han sido fijados por dos o más mercados de forma independiente por encima del límite máximo, no pueden venderse a su precio de mercado observado en Steam — y ninguno de ellos figura en dicha plataforma. El límite máximo de $1,800 genera la demanda que satisfacen los operadores externos.\nSteam Mercado comunitario: $31MValor de cotización de terceros: $1,276M\n1,276M $ · valor publicado por terceros — todo ello depende de la transacción de Steam API y OpenID\nSteam · $31M\n\nFuente: Catálogo en tiempo real de PriceEmpire, 20 septiembre de 2026.. Valor de catálogo = suma de las fichas de valor de catálogo redondeadas en la instantánea guardada, Steam excluido. No se trata del volumen de ventas.\n\n38 mercados de terceros activos · Todo ello depende de la infraestructura de Steam\nRegistro de la plataforma\n\nLas plataformas que se indican a continuación canalizan sus inicios de sesión a través de OpenID de Steam y sus operaciones a través de la «API» web de Steam. Cada una de las observadas openid.realm pasa por el flujo de inicio de sesión de Steam; el registro recoge las rutas de autenticación observadas, en lugar de afirmar que un operador concreto carece de permiso de Valve.\n\n#\tPlataforma\tValor cotizado\tOfertas vigentes\tArtículos\tEscala\n1\tUUSkins\t$133.8M\t3.4M\t30.9K\t\n\n2\tYouPin898\t$127.5M\t5.9M\t29.2K\t\n\n3\tBuff.163\t$104M\t3.5M\t35K\t\n\n4\tMoon.Market\t$100.3M\t2.9M\t20.9K\t\n\n5\tWhite.Market\t$89.6M\t3M\t20.6K\t\n\n6\tBuff.Market\t$86.7M\t1.3M\t33.4K\t\n\n7\tEcosteam\t$82.1M\t3.3M\t30.1K\t\n\n8\tCSFloat\t$67.8M\t2.4M\t27.8K\t\n\n9\tSkin.Land\t$67.4M\t2.2M\t34.6K\t\n\n10\tLIS-SKINS\t$67.4M\t2.2M\t34.6K\t\n\n11\tC5Game\t$54.6M\t4.6M\t29.6K\t\n\n12\tHaloSkins\t$46.6M\t4.4M\t29.3K\t\n\n13\tAvan.Market\t$43.3M\t809.5K\t22.2K\t\n\n14\tWaxpeer\t$40.1M\t1M\t27.3K\t\n\n15\tSteam (official)\t$31M\t32.2M\t70.1K\t\n\n16\tCS.MONEY\t$29M\t748.9K\t28K\t\n\n17\tMarket.CSGO\t$26.3M\t1.3M\t27.6K\t\n\n18\tCS.MONEY Bot\t$25.7M\t614K\t23.8K\t\n\n19\tSkinport\t$16.3M\t3.8M\t31.1K\t\n\n20\tSkinFlow\t$14.1M\t481.8K\t23.6K\t\n\n21\tDMarket\t$12.6M\t948.2K\t35.6K\t\n\n22\tSkins.com\t$11.5M\t83.2K\t15.8K\t\n\n23\tSkin.place\t$6.9M\t380.8K\t11.4K\t\n\n24\tSkinsMonkey\t$6M\t109.4K\t11.6K\t\n\n25\tSkinBaron\t$5M\t2.1M\t21.5K\t\n\n26\tRustTM\t$3M\t33.1K\t4.9K\t\n\n27\tPirateSwap\t$2M\t859.3K\t10.5K\t\n\n28\tMannco.Store\t$1.2M\t223.7K\t11K\t\n\n29\tSkinSwap\t$1.1M\t11.4K\t4K\t\n\n30\tTradeIt\t$967.1K\t29.1K\t11.7K\t\n\n31\tLootFarm\t$896.1K\t162.5K\t28.6K\t\n\n32\tRustskins\t$714.8K\t312.5K\t6.1K\t\n\n33\tBalticSkins\t$599.2K\t28.2K\t4.5K\t\n\n34\tExeSkins\t$442.9K\t2.6K\t1.4K\t\n\n35\tRapidSkins\t$230.9K\t11.6K\t2.3K\t\n\n36\tCS.Trade\t$203K\t19K\t16.7K\t\n\n37\tKrakatoa\t$11.1K\t115\t53\t\n\n38\tShadowPay\t—\t—\t—\t—\n39\t49skins\t—\t—\t—\t—\nEl precio máximo de Steam, fijado en $1,800 · Resumen de cinco mercados · 23 septiembre 2026\nLa diferencia de precios es cuantificable.\n\nSteam limita los precios de los anuncios del «Community Market» a aproximadamente $1,800 (el resultado se vuelve a calcular en $2,000, $, 2,070, $, 2,300 y $2,500 en cs2sh-atlas.json y se mantiene en cada umbral). Los artículos cuyo precio supera ese precio no pueden venderse a su precio de mercado a través de la propia plataforma de Valve — pero siguen dependiendo del inventario y del sistema de distribución de Steam, independientemente de dónde se vendan. Clasificar todo el catálogo por precios pone de manifiesto dónde está el límite: el mercado de Valve ofrece 95.3% de las categorías de artículos cuyo precio sea inferior a su límite máximo y 1.9% de los que están por encima de él.\n\nCinco mercados: artículos que superan el límite de «Steam»\n248\n\nCategorías de artículos cuyo precio de venta más bajo supera los $1,800 en dos o más mercados de forma independiente, con un valor de al menos las copias que figuran en la lista de «18,394» $78.6M. De ellos, 100.0% — todas y cada una de ellas — no aparecen en absoluto en Steam.\n\nAnexos completos: el registro → · el atlas de la escala de precios →\n\nDistribución de precios por encima del límite máximo\n$1,800–$5,000\n174\n$5,000–$10,000\n49\n$10,000–$25,000\n21\n$25,000–$50,000\n2\n$50,000+\n2\nProductos más vendidos: el precio de venta más barato confirmado en cinco plataformas de venta\n1Pegatina | Titan (Holo) | Cat. «14»$66,285\n2Pegatina | iBUYPOWER (Holo) | Cat. «14»$64,795\n3Pegatina | Reason Gaming (Holo) | Cat. «14»$42,899\n4★ Guantes deportivos | Laberinto de setos (FN)$26,812\n5Pegatina | Team Dignitas (Holo) | Kat. «14»$23,667\n6EMS Cat. «14: Legends»$22,879\n7★ Guantes deportivos | La caja de Pandora (FN)$21,643\n8EMS Cat. «14» Challengers$21,010\n9Pegatina | Vox Eminor (Holo) | Cat. «14»$18,619\n10★ Cuchillo StatTrak™ Navaja | Blue Steel (FN)$18,064\n\nLos precios de venta solicitados no son precios de venta. Instantánea de cs2.sh con licencia, 23 septiembre de 2026.. Cada fila ha sido cotizada por encima del límite máximo por al menos dos mercados de forma independiente; se excluyen las ofertas de venta de un solo lote y las cotizaciones que superen en más de tres veces la oferta de venta más barata de un artículo. Cómo funciona la calificación →\n\nLo que cobra Valve · con licencia cs2.sh instantánea · 23 septiembre 2026\nLa tarifa anunciada es de 15%.. La mayoría de los anuncios pagan más.\n\nValve deduce una comisión de 5% Steam y una comisión de 10% CS2 Publisher de los ingresos del vendedor —la conocida 15%. Ambas comisiones conllevan un Mínimo de $0.01, por lo que ninguna venta puede suponer nunca menos de dos céntimos en comisiones. En el caso de los artículos baratos y de gran volumen que constituyen la mayor parte del mercado, ese mínimo es la restricción determinante, no el porcentaje. Hemos resuelto el cálculo de las comisiones para cada uno de los 29,635 tipos de artículos que tienen una cotización en tiempo real en Steam.\n\n77.7%\nLos anuncios activos de Steam corresponden a tipos de artículos que se cobran según lo indicado en 15%\n84.8%\ndel artículo tipos pagan más o menos el salario base\n4,517\ntipos de artículos a los que se les aplica una tarifa superior a la anunciada\n$0.02\ncomisión mínima por cualquier venta, sea cual sea el precio\nLas dos cifras apuntan en direcciones opuestas, y ambas son ciertas.\n1\nContados por tipo de artículo, Las tarifas de Valve se ajustan, en líneas generales, a lo anunciado: 84.8% de los tipos de precios que figuran en 29,635 se cobran a un precio igual o similar al de 15%.\n2\nContados por lista real, la situación se invierte: 18,682,244 de 24,038,911 Los listados en tiempo real se aplican a los tipos de artículos que tienen un precio superior a 15%.\n3\nAmbas afirmaciones son ciertas porque los tipos sobrecarionados son los barato, de gran volumen esos. 1,109 Los tipos de artículos se cobran más que doble la tarifa principal, y solo esos tipos cuentan con anuncios activos en 14,083,486.\n4\nEsto es aritmética, no una acusación. El mínimo figura en la propia documentación sobre honorarios de «Valve». Lo que no se ha publicado es a qué parte del mercado se aplica realmente — que es precisamente lo que miden las cifras anteriores.\nComisión cobrada, como porcentaje del valor nominal 15%\n200%+\n14,083,486\n100-200%\n1,028,438\n50-100%\n700,804\n30-50%\n317,031\n20-30%\n2,258,254\n17.6-20%\n294,231\n\nLa «longitud de la barra» es el número de anuncios activos en cada franja. Una franja de «200%+» significa que la comisión que se cobra es más del doble de 15% de los ingresos del vendedor.\n\nUn ejemplo resuelto\n67%\n\nEn una venta, el comprador paga $0.03 pues el vendedor recibe $0.01 y «Valve» lleva $0.02 — los dos mínimos de un céntimo. Como porcentaje de lo que pagó el comprador, es 67%; como porcentaje de los ingresos del vendedor, es 200%.\n\nConjunto de datos completo: cs2sh-steam-fee-census.json →\n\nEl mismo objeto, dentro y fuera del jardín\nComprar en Steam sale más caro. Casi siempre.\n\nPara cada artículo cuyo precio apareciera tanto en Steam como en al menos un mercado de terceros, comparamos el precio de venta más barato de Steam con el precio de venta más barato fuera de esta plataforma. En 28,700 En cuanto a los artículos, Steam es la tienda más cara. 86.4% la mayor parte del tiempo, con una mediana de +35.7%.\n\nPrima media de «Steam», por tramo de precios\nmenos de $0.50\n+48.3%\n$0.50-2\n+36.5%\n$2-10\n+29.6%\n$10-50\n+28.6%\n$50-250\n+36.3%\n$250-1k\n+51.1%\nmás de $1,000\n+67.9%\n\nLa curva tiene forma de U. Lo más barato es comprar en Steam en el $10–$50 la banda y lo más querido en ambos extremos.\n\nPor qué es importante el segmento de gama alta\n+67.9%\n\nArriba $1,000, el precio medio de los anuncios de «Steam» 67.9% es superior al de la oferta más barata fuera de esta zona, y solo 1,040 existen anuncios de este tipo en Steam.\n\nA partir de unos $1,800, la comparación deja de ser posible, ya que la normativa de Valve prohíbe por completo su inclusión en la lista. La cobertura de Steam para los artículos que superan su propio límite máximo es 1.9%. Ver la clasificación completa →\n\nConjunto de datos completo: cs2sh-walled-garden-premium.json →\n\nUna prima no constituye por sí sola una conclusión: Steam ofrece entrega inmediata y ausencia de riesgo de contraparte, y es razonable que los compradores paguen por ello. Lo que sí es cuantificable es la magnitud de la brecha y el hecho de que el dinero que la atraviesa no pueda recuperarse, lo cual se aborda en la siguiente sección.\n\nEntra dinero, no sale dinero\n128.1 millones de dólares destinados a pedidos que no se pueden cancelar.\n\nUna orden de compra de «Steam» está prefinanciada: el dinero sale del monedero del comprador en el momento en que se realiza la orden. Steam fondos del monedero no se puede retirar — solo se pueden gastar dentro de Steam. La suma de todos los niveles de precio del libro de órdenes de compra de cada artículo registrado ofrece un recuento del dinero comprometido, del que no se puede salir.\n\n$128.1M\ncomprometidos a mantener las órdenes de comprSteam\n170.6M\nórdenes de compra financiadas de forma individual pendientes\n$105.8M\nprecio de venta de los inmuebles que tienen delante\n$15.9M\nLa comisión de Valve si todos los inmuebles se vendieran al precio de venta solicitado\nQué es esta cifra y qué no es\n1\nEs dinero real ya ingresado. Cada dólar contabilizado se ha cargado en una cartera y está asignado a una orden abierta en cualquiera de los tipos de artíc31,253.\n2\nEs no son ingresos y no se trata de una afirmación sobre el balance de «Valve». En este texto no se aclara dónde se mantiene el capital circulante ni en qué libros figura.\n3\nEs un una instantánea, no un flujo. El comprador puede cancelar los pedidos, lo que hace que el importe se devuelva al monedero, aunque sin salir de Steam.\n4\nLa clave está en la puerta de sentido único. Un mercado cuya moneda no se puede canjear por dinero es la razón por la que se convierte el inventario robado apagado Steam en lugar de sobre él.\n\nMétodo: cada nivel de precio de cada libro de compra analizado, multiplicado por las órdenes existentes en ese nivel. Conjunto de datos completo: cs2sh-steam-locked-capital.json →\n\nVentas realizadas, no precios de venta solicitados · un único mercado · los últimos 90 días\nDe hecho, se intercambiaron $30.9 millones, en la estantería más pequeña de las cinco.\n\nUna sola venta por un importe elevado puede corresponder a una pieza de artesanía poco común o a una variante con pegatina de un artículo básico barato (por ejemploe.g un artículo de30 con una venta completada única de9,772). «Elevado» = la transacción completada de mayor importe, no el precio habitual del artículo.\n\nTodas las demás cifras de esta página indican lo que es enumerados. Este mide lo que era vendido. Skinport publica sus propias operaciones realizadas y, en los últimos 90 días, estas ascendieron a 1,219,143 ventas valor $30,927,032, a un precio medio de $25.37 cada una.\n\n1.22M\nventas realizadas en 90 días, en un único mercado\n$30.9M\nvolumen de negocio durante el mismo periodo\n$125M\ntasa de ejecución anualizada: un mínimo, no una estimación\n~2%\nParticipación de Skinport en el mercado de valores no cotizados por encima del límite máximo, según el valor de cotización\nDe dónde procedía el volumen de negocio\nmenos de $1\n0.5%\n$1-10\n5.8%\n$10-100\n22.2%\n$100-1k\n59.4%\n$1k-1.8k\n6.9%\npor encima del límite de «Steam»\n5.3%\n\nLa longitud de la barra representa el volumen de negocio; la cifra indica la proporción de ese nivel respecto al total. 59.4% del dinero movido en el nivel de $100–$1k, en ventas de 71,437.\n\nPor encima del límite de «Valve», las ventas siguen produciéndose\n492\n\nventas realizadas de artículos cuyo precio superaba el límite establecido en Steam, por un valor de $1,643,938, en un 76s de tipos de productos, en un mercado que ocupa aproximadamente un2% de ese espacio en las estanterías. Ninguna de esas ventas habría podido realizarse en Steam.\n\nConjunto de datos completo: cs2sh-offsteam-90d-dynamics.json → · los máximos alcanzados →\n\nSkinport Es UNO de los mercados de terceros que se analizan aquí y, al tener un valor de cotización superior al límite de Steam, es el más pequeño de los cinco (aproximadamente 2% de esa sección). Todas las cifras totales que aparecen aquí representan un mínimo de la economía paralelaSteam, no una medida de la misma. No se utilizan datos de Steam.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Economía de mercado: dos economías y el límite máximo de cotización"
          },
          {
            "level": 2,
            "id": null,
            "text": "Una infraestructura. Dos economías."
          },
          {
            "level": 2,
            "id": null,
            "text": "Registro de la plataforma"
          },
          {
            "level": 2,
            "id": null,
            "text": "La diferencia de precios es cuantificable."
          },
          {
            "level": 3,
            "id": null,
            "text": "Cinco mercados: artículos que superan el límite de «Steam»"
          },
          {
            "level": 3,
            "id": null,
            "text": "Distribución de precios por encima del límite máximo"
          },
          {
            "level": 3,
            "id": null,
            "text": "Productos más vendidos: el precio de venta más barato confirmado en cinco plataformas de venta"
          },
          {
            "level": 2,
            "id": null,
            "text": "La tarifa anunciada es de 15%.. La mayoría de los anuncios pagan más."
          },
          {
            "level": 3,
            "id": null,
            "text": "Comisión cobrada, como porcentaje del valor nominal 15%"
          },
          {
            "level": 3,
            "id": null,
            "text": "Un ejemplo resuelto"
          },
          {
            "level": 2,
            "id": null,
            "text": "Comprar en Steam sale más caro. Casi siempre."
          },
          {
            "level": 3,
            "id": null,
            "text": "Prima media de «Steam», por tramo de precios"
          },
          {
            "level": 3,
            "id": null,
            "text": "Por qué es importante el segmento de gama alta"
          },
          {
            "level": 2,
            "id": null,
            "text": "128.1 millones de dólares destinados a pedidos que no se pueden cancelar."
          },
          {
            "level": 2,
            "id": null,
            "text": "De hecho, se intercambiaron $30.9 millones, en la estantería más pequeña de las cinco."
          },
          {
            "level": 3,
            "id": null,
            "text": "De dónde procedía el volumen de negocio"
          },
          {
            "level": 3,
            "id": null,
            "text": "Por encima del límite de «Valve», las ventas siguen produciéndose"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/es/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/es/elite_skins.html",
          "https://phishdestroy.io/steam_dossier/es/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/es/skin_atlas.html#grading",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-steam-fee-census.json",
          "https://phishdestroy.io/steam_dossier/es/skin_atlas.html#cliff",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-walled-garden-premium.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-steam-locked-capital.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-offsteam-90d-dynamics.json",
          "https://phishdestroy.io/steam_dossier/es/skin_atlas.html#highs"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/es/market_economics.content.json",
      "export_json_sha256": "1fe147861015cfa2e6b8fb83fe950fa4d847f56886ec93823ae926a478eb9e40"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "es/regulatory_act_print.html",
      "language": "es",
      "title": "LEY DE AUDITORÍA FORENSE: Valve Steam Web API Ecosistema y explotación comercial (Ref.: VAL-REG-2026-09)",
      "source_url": "https://phishdestroy.io/steam_dossier/es/regulatory_act_print",
      "source_html_sha256": "935c68ea9d87f398187c212509c39ca89578828bd58265229dcda8fffe3d894c",
      "exported_at": "2026-09-29T00:17:24.589Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "regulatory_act_print.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/es/regulatory_act_print.pdf?v=print-20260929-v5",
        "sha256": "00acf738fa13012168274c0938710a9d9d86b37a8b50999f0c7147085f47f141",
        "bytes": 183979,
        "pages": 14
      },
      "integrity": {
        "signed_object": "regulatory_act_print.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "regulatory_act_print.content.json.asc",
        "digest_file": "regulatory_act_print.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify regulatory_act_print.content.json.asc regulatory_act_print.content.json",
          "sha256sum -c regulatory_act_print.content.json.sha256"
        ]
      },
      "content": {
        "text": "phishdestroy.io · Coalición para la Investigación Forense · Registro Público Universal\nEXPEDIENTE: VAL-REG-2026-09-EVID\nPROCEDENCIA: phishdestroy.io/steam_dossier/\nDERECHOS: TODOS LOS DERECHOS CEDIDOS A LA HUMANIDAD\nLey de Auditoría Forense y Anexo Normativo\nAprovisionamiento sistemático de «API» por parte de terceros, arquitectura de derivación automatizada e incumplimiento contractual en el ecosistema de «Valve» Steam\nDominio emisorphishdestroy.io\nPlataforma de destinoValve Steam / Steamworks\nVector de autenticación principalSteam OpenID 2.0 / Web API\nDedicatoria legalAll Rights to Humanity (CC0)\nSección I: Memorándum ejecutivo y conclusiones fácticasREF: MEMORÁNDUM-RESUMEN-01\n\nEl presente documento constituye un informe formal de auditoría forense en el que se analiza la interrelación operativa entre las condiciones comerciales publicadas por Valve Corporation, sus puntos finales de autenticación técnica y las plataformas comerciales de terceros observadas. La auditoría se llevó a cabo mediante la observación pasiva y sin autenticación de la red, la verificación de registros en RDAP y la telemetría pública de Link Filter.\n\nNúcleo factual: La observación empírica pone de manifiesto una divergencia sistemática entre las declaraciones contractuales públicas de Valve y su infraestructura de producción. Aunque el Acuerdo de Suscriptor de Steam (SSA) prohíbe estrictamente la explotación comercial no autorizada (§ 2.G), la interacción automatizada mediante bots o scripts (§ 4.C) y la transferencia de cuentas (§ 1.C), Valve Corporation sigue proporcionando, en tiempo real, una infraestructura programática de autenticación OpenID y consulta de inventario a, al menos, 175 entidades comerciales que generan volúmenes de transacciones secundarias de miles de millones de dólares.\n\n175\nOperadores comerciales auditados\n44\nServidores de autenticación con dominios independientes\n26\nPares de proxies con filtrado dividido\n100%\nArtículos no aplicados de la SSA: § 2.G / § 4.C\n0\nRevocaciones de autenticación forzadas\nMarco contractual y normativo aplicable\nSSA, art.2.G\nProhibición de uso comercial: Queda expresamente prohibido utilizar los Contenidos y Servicios con fines comerciales sin la autorización previa por escrito de Valve Corporation.\nSSA, art.4.C\nRestricción de automatización: Queda terminantemente prohibido el uso de scripts, bots de negociación, macros o sistemas no controlados por personas que interactúen con los servicios y mercados de Steam.\nSSA, art.1.C\nObligación de uso personal: Limita el uso de las cuentas al ámbito personal; prohíbe expresamente la venta, el alquiler, la cesión o el intercambio de cuentas de usuario de Steam.\nLa Ley de Seguridad de los Datos de la UE (DSA, 2022/2065)\nEvaluación del riesgo sistémico (art. 34/35): Las plataformas en línea de gran envergadura (VLOP) deben detectar, evaluar y mitigar de forma activa los riesgos sistémicos derivados del uso indebido automatizado y la explotación comercial no autorizada.\nSección II: Libro mayor de anexos A — Pares divididos con filtro de enlaces documentados (rutas 26)REF: EX-SPLIT-LEDGER\n\nAnálisis forense de la evasión mediante dominios divididos: En el marco del sistema de filtrado de enlaces «Steam» de Valve (steamcommunity.com/linkfilter/?url=...), cuando un usuario final hace clic en un enlace que conduce a una plataforma de apuestas o del mercado negro señalada, Valve muestra una advertencia destacada («¡Enlace bloqueado! ... marcado como potencialmente malicioso»). Sin embargo, el rastreo forense de rutas revela que existen 26 plataformas comerciales que operan en un arquitectura de dominios separados: aunque el dominio comercial principal aparece como BLOQUEADO en el filtro de enlaces, el dominio secundario que aloja el punto final de respuesta de OpenID de Valve aparece marcado como LIMPIO. Los servidores OpenID de Valve aceptan sin interrupción las solicitudes de autenticación procedentes de estos servidores proxy, lo que neutraliza la advertencia de seguridad para el usuario y permite seguir procesando los inicios de sesión.\n\n#\tDominio comercial principal\tFiltro principal\tDominio del proxy de autenticación OpenID\tFiltro de autenticación\tRDAP Registrado\tBase de captura\n01\trollbit.com\tBLOCKED\trbsnin.com\tCLEAN\t2026-09-18\tPASSIVE_CAPTURE\n02\tskin.club\tBLOCKED\tsc-auth.net\tCLEAN\t2019-04-02\tPASSIVE_CAPTURE\n03\thowl.gg\tBLOCKED\thowl.uno\tCLEAN\t2026-08-11\tPASSIVE_CAPTURE\n04\tduelbits.com\tBLOCKED\tswitchflips.com\tCLEAN\t2020-04-21\tPASSIVE_CAPTURE\n05\tcsgofast.com\tBLOCKED\tsteam-login.authtofast.com\tCLEAN\t2026-06-30\tPASSIVE_CAPTURE\n06\tfarmskins.com\tBLOCKED\tsteam.kobal.cc\tCLEAN\t2017-01-07\tPASSIVE_CAPTURE\n07\tcobaltlab.tech\tBLOCKED\tcobaltauth.com\tCLEAN\t2025-01-07\tPASSIVE_CAPTURE\n08\tcsgo.net\tBLOCKED\tcn2.easylot.net\tCLEAN\t2016-09-03\tPASSIVE_CAPTURE\n09\tggdrop.com\tBLOCKED\tggauth.com\tCLEAN\t2023-05-03\tPASSIVE_CAPTURE\n10\trustchance.com\tBLOCKED\thgfuihd.com\tCLEAN\t2019-01-27\tPASSIVE_CAPTURE\n11\tskin.fans\tBLOCKED\tauth.skinfans.com\tCLEAN\t2018-07-16\tPASSIVE_CAPTURE\n12\tskinport.com\tBLOCKED\tskinport.app\tCLEAN\t2020-06-20\tPASSIVE_CAPTURE\n13\tskins.cash\tBLOCKED\tskinscash.live\tCLEAN\t2019-12-05\tPASSIVE_CAPTURE\n14\ttf2hunt.com\tBLOCKED\trstspcl.com\tCLEAN\t2020-08-08\tPASSIVE_CAPTURE\n15\tdaddyskins.com\tBLOCKED\tgo-go-daddy.com\tCLEAN\t2019-01-26\tPASSIVE_CAPTURE\n16\tkey-drop.com\tBLOCKED\tkdauth.com\tCLEAN\t2026-05-13\tPASSIVE_CAPTURE\n17\tclash.gg\tBLOCKED\tclggauth.com\tCLEAN\t2024-09-16\tPASSIVE_CAPTURE\n18\tc5game.com\tBLOCKED\twww.imbastar.com\tCLEAN\t2016-02-27\tPASSIVE_CAPTURE\n19\tswap.gg\tBLOCKED\tswapauth.com\tCLEAN\t2018-10-06\tPASSIVE_CAPTURE\n20\tshadowpay.com\tBLOCKED\tthelogins.com\tCLEAN\t2018-01-22\tPASSIVE_CAPTURE\n21\tcsgocases.com\tBLOCKED\tlog-1n.com\tCLEAN\t2017-11-27\tPASSIVE_CAPTURE\n22\tcsgogem.com\tBLOCKED\tapi.csgem.com\tCLEAN\t2014-03-08\tPASSIVE_CAPTURE\n23\tgamdom.com\tBLOCKED\tlogin.gambldom.com\tCLEAN\t2017-09-24\tPASSIVE_CAPTURE\n24\t12cs.fail\tBLOCKED\tfail.games\tCLEAN\t2021-08-24\tPASSIVE_CAPTURE\n25\tskinsnipe.com\tBLOCKED\tpricing.tradeupspy.com\tCLEAN\t2020-03-11\tPASSIVE_CAPTURE\n26\tcsgobig.com\tBLOCKED\tletmeinbig.com\tCLEAN\t2023-01-20\tPASSIVE_CAPTURE\n\n* Nota: Se han realizado comprobaciones pasivas en los puntos finales no autenticados del filtro de enlaces «Steam» en 2026-09-19 y 2026-09-21.. Los cuerpos de las respuestas HTTP sin procesar y los resúmenes SHA-256 se conservan en el conjunto de datos del repositorio (steam_tos_assets/linkfilter-2026-09-22.json).\n\nSección III: Libro de registro de anexos B — Censo exhaustivo de las entidades comerciales auditadas de 175REF: EX-175-, CENSO GENERAL\n\nEl siguiente registro detalla todas las plataformas comerciales de terceros 175 verificadas activamente en la base de datos de auditoría. Cada registro indica el nombre de la entidad, el dominio comercial principal, la ruta de autenticación OpenID observada Steam, la clasificación de la actividad, las correspondencias de incumplimiento contractual (SSA § 2.G, SSA § 4.C, SSA § 1.C) y el campo de acción registrado en el conjunto de datos de origen. La etiqueta «Véase la prueba fechada» remite al lector a los registros justificativos; no establece que Valve no tomara ninguna medida. La ausencia de un campo de acción se indica como «no establecido».\n\nAnexo\tNombre de la entidad y dominio principal\tRuta de autenticación observada / Proxy\tClasificación\tIncumplimiento contractual\tValve Acción\nEX-001\tCSGORoll\ncsgoroll.com\n\t\nwww.csgoroll.com\nDIRECT\n\tSkin Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-002\tCSGOEmpire\ncsgoempire.com\n\t\ncsgoempirelogin4.com\nSPLIT PROXY\n\tCasino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-003\tRollbit\nrollbit.com\n\t\nrbsnin.com\nSPLIT PROXY\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-004\t500 Casino\n500.casino\n\t\nfivezerozero.co\nSPLIT PROXY\n\tLicenced Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-005\tCSGOBig\ncsgobig.com\n\t\ncsgobig.com\nDIRECT\n\tRoulette/Slots\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-006\tCaseDrop\ncasedrop.com\n\t\ncasedrop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-007\tRustReaper\nrustreaper.com\n\t\nrustreaper.com\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-008\tBanditCamp\nbanditcamp.com\n\t\nbanditcamp.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-009\tSkinBox\nskinbox.com\n\t\nskinbox.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-010\tTastyDrop\ntastydrop.com\n\t\ntastydrop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-011\tCSGOPolygon\ncsgopolygon.gg\n\t\ncsgopolygon.gg\nDIRECT\n\tRoulette Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-012\tMagicDrop\nmagicdrop.ru\n\t\nmagicdrop.ru\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-013\tCSDice\ncsdice.com\n\t\ncsdice.com\nDIRECT\n\tDice Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-014\tRustly\nrustly.com\n\t\nrustly.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-015\tSkinOdds\nskinodds.com\n\t\nskinodds.com\nDIRECT\n\tUpgrader Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-016\tCSGOWin\ncsgowin.com\n\t\ncsgowin.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-017\tCSGORun\ncsgorun.net\n\t\ncsgorun.net\nDIRECT\n\tCrash Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-018\tOpenSkins\nopenskins.com\n\t\nopenskins.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-019\tRustBet\nrustbet.com\n\t\nrustbet.com\nDIRECT\n\tRust Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-020\tCSGOMagic\ncsgomagic.com\n\t\ncsgomagic.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-021\tCSGOBounty\ncsgobounty.com\n\t\ncsgobounty.com\nDIRECT\n\tUpgrader/Contract\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-022\tEZSkins\nezskins.com\n\t\nezskins.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-023\tRustCases\nrustcases.com\n\t\nrustcases.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-024\tCSGOReaper\ncsgoreaper.com\n\t\ncsgoreaper.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-025\tCSGOCases\ncsgocases.com\n\t\ncsgocases.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-026\tCSGO-Skins\ncsgo-skins.com\n\t\ncsgo-skins.com\nDIRECT\n\tCase Upgrader\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-027\tCSGONet\ncsgonet.com\n\t\ncsgonet.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-028\tWTFSkins\nwtfskins.com\n\t\nwtfskins.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-029\tCSGOFast\ncsgofast.com\n\t\nsteam-login.authtofast.com\nSPLIT PROXY\n\tRoulette Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-030\tDuelbits\nduelbits.com\n\t\nswitchflips.com\nSPLIT PROXY\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-031\tFlameCases\nflamecases.com\n\t\nflamecases.com\nDIRECT\n\tCase Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-032\tFarmskins\nfarmskins.com\n\t\nsteam.kobal.cc\nSPLIT PROXY\n\tCase Opener\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-033\tCSGOLuck\ncsgoluck.com\n\t\ncsgoluck.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-034\tGamedom\ngamedom.com\n\t\ngamedom.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-035\tSkin.Club\nskin.club\n\t\nsc-auth.net\nSPLIT PROXY\n\tCase Battles\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-036\tDaddySkins\ndaddyskins.com\n\t\ndaddyskins.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-037\tInsane.gg\ninsane.gg\n\t\napi.insane.gg\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-038\tRustix\nrustix.gg\n\t\nrustix.gg\nDIRECT\n\tRust Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-039\tSkins.Club\nskins.club\n\t\nskins.club\nDIRECT\n\tSkin Upgrade\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-040\tCSGOHouse\ncsgohouse.org\n\t\ncsgohouse.org\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-041\tSkinRave\nskinrave.net\n\t\nskinrave.net\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-042\tBloodyCase_GG\nbloodycase.gg\n\t\nbloodycase.gg\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-043\tCSGOClicker\ncsgoclicker.com\n\t\ncsgoclicker.com\nDIRECT\n\tClicker/Upgrade\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-044\tRustBet_GG\nrustbet.gg\n\t\nrustbet.gg\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-045\tCS_Drop\ncs-drop.com\n\t\ncs-drop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-046\tHellStore\nhellstore.net\n\t\nhellstore.net\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-047\tRustLoot\nrustloot.com\n\t\nrustloot.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-048\tCSGO_Case\ncsgo-case.com\n\t\ncsgo-case.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-049\tCS2Skin\ncs2skin.com\n\t\ncs2skin.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-050\tJuice_GG\njuice.gg\n\t\nletmeinjuice.com\nSPLIT PROXY\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-051\tGGDrop\nggdrop.com\n\t\nggauth.com\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-052\tCSGOGem\ncsgogem.com\n\t\ncsgogem.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-053\tRainbet\nrainbet.com\n\t\nservices.rainbet.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-054\tHowl_GG\nhowl.gg\n\t\nhowl.uno\nSPLIT PROXY\n\tSkins Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-055\tChicken_GG\nchicken.gg\n\t\nchicken.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-056\tCSGOCasino_GG\ncsgocasino.gg\n\t\napi.csgocasino.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-057\tHunt_GG\nhunt.gg\n\t\napi.hunt.gg\nDIRECT\n\tSkins Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-058\tCSBattle\ncsbattle.com\n\t\ncsbattle.com\nDIRECT\n\tCase Battles\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-059\tSkinRave_GG\nskinrave.gg\n\t\napi.skinrave.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-060\tCSDouble\ncsdouble.gg\n\t\ncsdouble.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-061\tRustChance\nrustchance.com\n\t\nhgfuihd.com\nSPLIT PROXY\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-062\tRustClash\nrustclash.com\n\t\nrustclash.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-063\tCobaltLab\ncobaltlab.tech\n\t\ncobaltauth.com\nSPLIT PROXY\n\tRust Automation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-064\tRaided_GG\nraided.gg\n\t\napi.raided.gg\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-065\tRustNeo\nrustneo.gg\n\t\nrustneo.gg\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-066\tSplits_GG\nsplits.gg\n\t\nsplits.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-067\tUpgrader_Pro\nupgrader.pro\n\t\nupgauth.space\nSPLIT PROXY\n\tSkin Upgrader\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-068\tSkinFans\nskin.fans\n\t\nauth.skinfans.com\nSPLIT PROXY\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-069\tHotPizza\nhotpizza.one\n\t\nhotpizza.one\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-070\tG4Skins\ng4skins.com\n\t\nauth.g4s.to\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-071\t12CS_Fail\n12cs.fail\n\t\n12cs.fail\nDIRECT\n\tCrash Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-072\tTF2Royal\ntf2royal.com\n\t\ntf2auth.com\nSPLIT PROXY\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-073\tTF2Easy\nwww.tf2easy.com\n\t\nwww.tf2easy.com\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-074\tTF2Hunt\ntf2hunt.com\n\t\nrstspcl.com\nSPLIT PROXY\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-075\tTF2Bet\ntf2.bet/coinflip\n\t\ntf2.bet\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-076\tTF2Blaze\ntf2blaze.com\n\t\ntf2blaze.com\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-077\tOpenStars_GG\nopenstars.gg\n\t\nopenstars.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-078\tShuffle_Com\nshuffle.com\n\t\nshuffle.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-079\tSkins.com\nskins.com\n\t\napi.skins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-080\tWhite.Market\nwhite.market\n\t\nwhite.market\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-081\tBuff.Market\nbuff.market\n\t\nbuff.market\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-082\tAvan.Market\navan.market\n\t\navan.market\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-083\tCS.MONEY\ncs.money\n\t\nauth.dota.trade\nSPLIT PROXY\n\tTrading Engine\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-084\tUUSkins\nuuskins.com\n\t\nuuskins.com\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-085\tYouPin898\nyoupin898.com\n\t\nyoupin898.com\nDIRECT\n\tMass Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-086\tMoon.Market\nmoon.market\n\t\nmoon.market\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-087\tCSFloat\ncsfloat.com\n\t\ncsgofloat.com\nSPLIT PROXY\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-088\tSkin.Land\nskin.land\n\t\nauth.skin.land\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-089\tC5Game\nc5game.com\n\t\nc5game.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-090\tHaloSkins\nhaloskins.com\n\t\nhaloskins.com\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-091\tBuff.163\nbuff.163.com\n\t\nbuff.163.com\nDIRECT\n\tCorporate Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-092\tWaxpeer\nwaxpeer.com\n\t\nwaxpeer.com\nDIRECT\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-093\tCS.MONEY Bot\ncs.money\n\t\nauth.dota.trade\nSPLIT PROXY\n\tBot Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-094\tMarket.CSGO\nmarket.csgo.com\n\t\ndota2.net\nSPLIT PROXY\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-095\tSkinport\nskinport.com\n\t\nskinport.app\nSPLIT PROXY\n\tRegulated Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-096\tSkinFlow\nskinflow.gg\n\t\napi.skinflow.gg\nDIRECT\n\tMarketplace/Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-097\tDMarket\ndmarket.com\n\t\ndmarket.com\nDIRECT\n\tUS Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-098\tSkin.place\nskin.place\n\t\napi.skin.place\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-099\tSkinsMonkey\nskinsmonkey.com\n\t\nskinsmonkey.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-100\tSkinBaron\nskinbaron.de\n\t\nskinbaron.com\nSPLIT PROXY\n\tCorporate Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-101\tSteam\nsteamcommunity.com/market\n\t\nsteamcommunity.com/market\nDIRECT\n\tOfficial Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-102\tRustTM\nrust.tm\n\t\ndota2.net\nSPLIT PROXY\n\tRust Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-103\tPirateSwap\npirateswap.com\n\t\nlogin.pirateswap.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-104\tMannco.Store\nmannco.store\n\t\nmannco.store\nDIRECT\n\tTF2 Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-105\tSkinSwap\nskinswap.com\n\t\napi.skinswap.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-106\tLootFarm\nlootfarm.com\n\t\nlootfarm.com\nDIRECT\n\tTrading Platform\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-107\tRustskins\nrustskins.com\n\t\nrustskins.com\nDIRECT\n\tRust Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-108\tExeSkins\nexeskins.com\n\t\nexeskins.com\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-109\tBalticSkins\nbalticskins.com\n\t\nbalticskins.com\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-110\tCS.Trade\ncs.trade\n\t\ncs.trade\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-111\tRapidSkins\nrapidskins.com\n\t\napi.rapidskins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-112\tTradeIt\ntradeit.gg\n\t\nconnect-tradeit.com\nSPLIT PROXY\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-113\tKrakatoa\nkrakatoa.com\n\t\nkrakatoa.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-114\tShadowPay\nshadowpay.com\n\t\nshadowpay.com\nDIRECT\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-115\t49skins\n49skins.com\n\t\napi.49skins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-116\tSkinVault\nskinvault.gg\n\t\napi.skinvault.gg\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-117\tAim Market\naim.market\n\t\naim.market\nDIRECT\n\tSkins Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-118\tSkinout\nskinout.gg\n\t\nauth.skinout.gg\nDIRECT\n\tInstant Sell Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-119\tNTSkins\nntskins.com\n\t\nntskins.com\nDIRECT\n\tSkins Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-120\tIGXE\nigxe.cn\n\t\nigxe.cn\nDIRECT\n\tChinese Powerhouse\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-121\tSwap.gg\nswap.gg\n\t\nswap.gg\nDIRECT\n\tAutomated Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-122\tBitskins\nbitskins.com\n\t\nbitskins.com\nDIRECT\n\tCash-out Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-123\tGamerPay\ngamerpay.gg\n\t\ngamerpay.gg\nDIRECT\n\tP2P Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-124\tTF2Mart\ntf2mart.com\n\t\ntf2mart.com\nDIRECT\n\tTF2 Automation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-125\tSkinBid\nskinbid.com\n\t\nskinbid.com\nDIRECT\n\tSkin Auctions\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-126\tLootBear\nlootbear.com\n\t\nlootbear.com\nDIRECT\n\tSkin Rental\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-127\tBackpack.tf\nbackpack.tf\n\t\nbackpack.tf\nDIRECT\n\tTF2 Valuation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-128\tScrap.tf\nscrap.tf\n\t\nscrap.tf\nDIRECT\n\tTF2 Scrap Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-129\tMarketplace.tf\nmarketplace.tf\n\t\nmarketplace.tf\nDIRECT\n\tTF2 Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-130\tSTNTrading\nstntrading.eu\n\t\nstntrading.eu\nDIRECT\n\tTF2 Botnet\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-131\tSkins.Cash\nskins.cash\n\t\nskinscash.live\nSPLIT PROXY\n\tInstant Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-132\tSkinWallet\nskinwallet.com\n\t\nskinwallet.com\nDIRECT\n\tInstant Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-133\tDota2Market\ndota2market.com\n\t\ndota2market.com\nDIRECT\n\tDota 2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-134\tCSGO.NET\ncsgo.net\n\t\ncn2.easylot.net\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-135\tCybershoke\ncybershoke.net\n\t\nauth.cybershoke.net\nDIRECT\n\tCommunity Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-136\tXPlay_GG\nxplay.gg\n\t\nxplay.gg\nDIRECT\n\tServer Network\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-137\tFastCup\nfastcup.net\n\t\napi.fastcup.net\nDIRECT\n\tMatchmaker Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-138\tEsportal\nesportal.com\n\t\nesportal.com\nDIRECT\n\tMatchmaking Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-139\tGamersClub\ngamersclub.com.br\n\t\ngamersclub.com.br\nDIRECT\n\tLATAM Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-140\tLeetify\nleetify.com\n\t\nleetify.com\nDIRECT\n\tSaaS Analytics\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-141\tScope_GG\nscope.gg\n\t\nscope.gg\nDIRECT\n\tSaaS Analytics\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-142\tTradeUpSpy\ntradeupspy.com\n\t\napi.tradeupspy.com\nDIRECT\n\tSaaS Tools\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-143\tEpidemic_GG\nepidemic.gg\n\t\nepidemic.gg\nDIRECT\n\tSaaS Tools\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-144\tCSDeals\ncs.deals\n\t\napi.cs.deals\nDIRECT\n\tMarketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-145\tPricempire\npricempire.com\n\t\npricempire.com\nDIRECT\n\tSaaS Price DB\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-146\tCS2Stash\ncs2stash.com\n\t\ncs2stash.com\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-147\tCSGOSkins\ncsgoskins.gg\n\t\ncsgoskins.gg\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-148\tSteamAnalyst\nsteamanalyst.com\n\t\nsteamanalyst.com\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-149\tSteamCardExchange\nsteamcardexchange.net\n\t\nsteamcardexchange.net\nDIRECT\n\tTrading Exchange\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-150\tDotaBuff\ndotabuff.com\n\t\ndotabuff.com\nDIRECT\n\tSaaS Tracker\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-151\tTracker_GG\ntracker.gg\n\t\ntracker.gg\nDIRECT\n\tSaaS Tracker\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-152\tFSB Market (an anonymized label; the original name is withheld here)\nFSB Market\n\t\nFSB Market\nDIRECT\n\tMass Blackmarket\tSSA § 2.G, SSA § 4.C, SSA § 1.C\tSee dated evidence\nEX-153\tFunPay\nfunpay.com\n\t\nfunpay.com\nDIRECT\n\tAccount Exchange\tSSA § 2.G, SSA § 4.C, SSA § 1.C\tSee dated evidence\nEX-154\tPlayerAuctions\nplayerauctions.com\n\t\nplayerauctions.com\nDIRECT\n\tGrey Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-155\tEldorado.gg\neldorado.gg\n\t\neldorado.gg\nDIRECT\n\tAccount Portal\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-156\tG2A\ng2a.com\n\t\ng2a.com\nDIRECT\n\tMass Key Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-157\tKinguin\nkinguin.net\n\t\nkinguin.net\nDIRECT\n\tMass Key Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-158\tG2G.com\ng2g.com\n\t\ng2g.com\nDIRECT\n\tVirtual Services\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-159\tPlayerup\nplayerup.com\n\t\nplayerup.com\nDIRECT\n\tAccount Broker\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-160\tZ2U.com\nz2u.com\n\t\nwww.z2u.com\nDIRECT\n\tReady-Account Hub\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-161\tSmurfHub\nsmurfhub.net\n\t\nsmurfhub.net\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-162\tSmurfAccounts\nsmurfaccounts.com\n\t\nsmurfaccounts.com\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-163\tBuyCSGORank\nbuycsgorank.com\n\t\nbuycsgorank.com\nDIRECT\n\tRank Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-164\tCSGOSmurfKings\ncsgosmurfkings.com\n\t\ncsgosmurfkings.com\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-165\tSmurfStore_Co\nsmurfstore.co\n\t\nsmurfstore.co\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-166\tSteamLvlUp\nsteamlvlup.com\n\t\nsteamlvlup.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-167\tSteamLevels\nsteamlevels.com\n\t\nsteamlevels.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-168\tLevelSteam\nlevelsteam.com\n\t\nlevelsteam.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-169\tSteamLevelU\nsteamlevelu.com\n\t\nsteamlevelu.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-170\tEloKing\neloking.com\n\t\neloking.com\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-171\tBoosteria\nboosteria.org\n\t\nboosteria.org\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-172\tOvergear\novergear.com\n\t\novergear.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-173\tBlazingBoost\nblazingboost.com\n\t\nblazingboost.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-174\tDota2Boost\ndota2boost.com\n\t\ndota2boost.com\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-175\tBuyBoost\nbuyboost.com\n\t\nbuyboost.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nSección IV: Arquitectura técnica y mecanismos de autenticaciónREF: ANÁLISIS TÉCNICO -01\n\n1. Ausencia de validación de la titularidad del dominio en OpenID 2.0: La implementación de Valve del protocolo OpenID 2.0 (https://steamcommunity.com/openid/login) evalúa el openid.return_to y openid.realm parámetros sin necesidad de que el desarrollador se haya registrado previamente, de realizar una verificación mediante desafío criptográfico ni de validar la titularidad del dominio. Cualquier operador comercial puede redirigir a los usuarios a la pantalla de inicio de sesión de Valve y recibir una afirmación de identidad firmada criptográficamente (que contiene el SteamID de 64-bits) redirigida a dominios arbitrarios.\n\n2. Consultas programáticas de inventario y uso indebido de claves de «API»: Una vez confirmada la autenticación del usuario a través de OpenID, los operadores consultan los puntos finales de las webAPIes públicas y de socios (IEconItems_730/GetPlayerItems) para indexar los activos de inventario en tiempo real. Las redes de negociación automatizadas utilizan tokens de sesión programáticos para enviar, solicitar y aceptar ofertas de negociación entre pares (P2P), lo que contraviene directamente la prohibición de la interacción no humana establecida en el artículo 4.C de la SSA.\n\n3. Asimetría del filtro de enlaces: La coexistencia de advertencias sobre dominios dirigidas a los consumidores junto con puntos finales de autenticación plenamente funcionales genera una contradicción normativa: la telemetría de seguridad de Valve clasifica a estos operadores como «potencialmente maliciosos», mientras que la infraestructura de autenticación de Valve sigue autenticando a su base de usuarios.\n\nMetodología probatoria y declaración sobre la cadena de custodia\n\nEste documento se ha elaborado a partir de capturas de red no autenticadas, consultas históricas al registro RDAP y manifiestos de hash criptográficos verificados. No se han sometido a pruebas de compromiso ni se han procesado credenciales de inicio de sesión de ningún usuario. Todos los hallazgos reflejan el estado observable de la red de producción a fecha de septiembre de 2026.. El presente documento constituye un anexo técnico imparcial elaborado para consultas judiciales, reguladoras y públicas.\n\nRESUMEN: SHA-256: VERIFICADO\nc507c9025f93da0aadaf395c4d8882f25973211c318ee8e9b6f18a5b3755e050\nARCHIVO: EXPEDIENTE JUDICIAL PÚBLICO\nEMITIDO Y FIRMADO POR: phishdestroy.io · Coalición para la Investigación Forense\nSITUACIÓN JURÍDICA: TODOS LOS DERECHOS CEDIDOS A LA HUMANIDAD · CC0 DOMINIO PÚBLICO UNIVERSAL",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Ley de Auditoría Forense y Anexo Normativo"
          }
        ],
        "links": []
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/es/regulatory_act_print.content.json",
      "export_json_sha256": "7cdd7c2cf4c49122230df5b61d0a850368ae237fdd2823fb53f81f36e174891d"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "es/security_timeline.html",
      "language": "es",
      "title": "Cronología de la seguridad — El expediente «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/es/security_timeline",
      "source_html_sha256": "c899da35caa97148a1c2da1829689a82eb7dbb3a60280fbf57bd4f0a26fb7301",
      "exported_at": "2026-09-29T00:17:24.972Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "security_timeline.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/es/security_timeline.pdf?v=print-20260929-v5",
        "sha256": "fb14ee50b3078ab024246ddbe289e6452889337a11550dcffda6c537f9b6a047",
        "bytes": 96211,
        "pages": 7
      },
      "integrity": {
        "signed_object": "security_timeline.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "security_timeline.content.json.asc",
        "digest_file": "security_timeline.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify security_timeline.content.json.asc security_timeline.content.json",
          "sha256sum -c security_timeline.content.json.sha256"
        ]
      },
      "content": {
        "text": "EL HISTORIAL DE SEGURIDADEXPOSICIÓN / PARTICIPACIONES EN EL «16»\n\n2018 — 2026\n\nCronología de seguridad: de «2018» a «2026»\n\nSe han producido cambios en la seguridad. Sigue el historial.\n\nLO QUE DEMUESTRA ESTA SECCIÓN\n\nEste registro cronológico reconstruye ocho años de modificaciones de seguridad en la pila de operaciones y autenticación de Steam. En él se recogen la implementación de la retención de operaciones de un día 2018 7-, las confirmaciones móviles con clave 2023 Web API y la retirada de los tokens de sesión 2026 frente a técnicas de elusión documentadas. La línea temporal pone de manifiesto que las actualizaciones de la plataforma siempre iban por detrás de los vectores de explotación conocidos, al tiempo que se preservaban las ventajas estructurales para los operadores comerciales.\n\n← Volver al informe ejecutivo\n\nBloqueos comerciales. Controles de acceso. Restricciones de «API». Un registro cronológico de lo que cambió y de lo que realmente demuestran las fuentes.\n\nExplora la línea temporal ↓\nOCHO AÑOS. UN RÉCORD.16hitos que hay que analizar\n\nCada entrada conserva la fecha de envío y la fuente. La verificación aparece junto a ella.\n\nREVISADO / 24 SEP 2026\n10Evento y fecha confirmados\n06Verificado parcialmente\n00Incompatibilidad de fuentes\n00Se necesita fuente\nCómo interpretar este registro\n\nEvento y fecha confirmados: ambas respaldadas por una fuente primaria fiable. Verificado parcialmente: Se ha documentado un cambio relacionado, pero la fecha o el alcance siguen sin estar claros. Discrepancia entre fuentes: El material al que se hace referencia no respalda la afirmación presentada. Se necesita fuente: En esta revisión no se ha verificado ninguna fuente con fecha que coincida. El hecho de que una entrada no se haya resuelto no prueba que el suceso no haya tenido lugar.\n\nLas fechas que figuran en las entradas sin resolver corresponden a las fechas de presentación, no a las fechas de publicación verificadas. El texto original de la investigación no se ha modificado.\n\nLa cronología\n01 — 16\nBuscar en el registroTemaPruebasPedido\n\n16 de las entradas de «16» · las más recientes primero\n\n202609-01Fecha de presentación\nComunidadVerificado parcialmente\nAvisos sobre mensajes sospechosos en los chats de grupo\n\nUn comunicado oficial sobre la versión beta confirma esta función el 31 de agosto. La fecha de lanzamiento de la versión estable, indicada en 1 de septiembre, aún no cuenta con sus notas de lanzamiento específicas.\n\nSteam Versión beta para clientes — 31de agosto ↗archivado en 2026-03-13 ↗\nEntrada original y enlace enviado\n\nDetección automática de chats sospechosos\n\nRevisa el código fuente enviado ↗\n202601-16Fecha de verificación\nAPIEvento y fecha confirmados\nPermisos detallados y listas blancas de direcciones IP para las claves de editor (anuncio sobre Valve)\n\nEl 16 de enero de 2026, Valve publicó un comunicado oficial de Steamworks («NOVEDAD: Mejores permisos y controles para las claves de «API» en la web») en la que se confirman nuevas herramientas de permisos detallados que permiten a los desarrolladores dividir las claves de «API» de la web en grupos independientes (Datos generales, sobre microtransacciones, economía y ventas), restringir las claves a ID de aplicación específicos y aplicar una lista blanca de direcciones IP de servidor.\n\nEl flagrante doble rasero: Este comunicado oficial establece que Valve ha desarrollado por completo la infraestructura técnica necesaria para la gestión detallada de permisos (API) y restricciones de IP, pero las oculta deliberadamente a las cuentas de usuario normales (steamcommunity.com/dev/apikey). Las claves de los usuarios habituales de API siguen siendo credenciales monolíticas, del tipo «todo o nada», sin listas blancas de direcciones IP, lo que constituye precisamente la omisión técnica que permite la existencia de una industria de interceptación de transacciones de API valorada en varios millones de dólares.\n\nValve Anuncio — NOVEDAD: Mejores permisos y controles para las claves de «API» en la web (16, 2026 de enero) ↗· Documentación: Autenticación web de Steamworks API ↗\nEntrada original y enlace enviado\n\nSteamworks Web API Alcances granulares\n\nEcha un vistazo al anuncio oficial de «Valve» en Steamworks (493839547938902179) ↗\n202507-15Fecha de verificación\nOperaciones bursátilesEvento y fecha confirmados\nLas operaciones con CS2 cuentan con un plazo de reversión de siete días\n\nEl comunicado publicado por Valve anuncia la anulación de los intercambios de objetos de Counter-Strike realizados durante los siete días anteriores. Aunque está pensado para mitigar el secuestro de cuentas, las auditorías económicas realizadas por terceros (CSMarketCap ↗) registró un 104millones de dólares (-25%) colapso en capitalización bursátil en unas hor24es debido a una interrupción en la negociación al contado. Según el análisis realizado por Skinvault ↗, al activar una reversión, se aplica automáticamente un bloqueo de operaciones intradía 30-en la cuenta. En verano, 2026, Valve pasó de los reinicios globales a medianoche (UTC) a temporizadores individuales por artículo, con una duración de un minuto (Skin.land ↗).\n\nValve — 15, 2025, anuncio de julio ↗· Análisis de CSMarketCap ↗\nEntrada original y enlace enviado\n\nProtección comercial de CS2 / Ventana de reversión\n\nRevisa el código fuente enviado ↗\n202505-14Fecha de verificación\nAutenticaciónEvento y fecha confirmados\nValve publica una advertencia sobre la seguridad de las cuentas en relación con las filtraciones de SMS\n\nEl comunicado oficial de Valve del 14, 2025, aborda la seguridad de las cuentas y los autenticadores basados en SMS. Aunque el comunicado se centra en las filtraciones de SMS y confirma que no se ha producido ninguna brecha en los sistemas de Steam, sirve como actualización oficial de seguridad en la fecha de publicación.\n\nValve — Una nota sobre la seguridad de tu cuenta de Steam ↗\nEntrada original y enlace enviado\n\nAnuncio sobre la seguridad de la cuenta\n\nRevisa el código fuente enviado ↗\n202410-02Fecha de verificación\nOperaciones bursátilesEvento y fecha confirmados\nSiete días antes de volver a poner a la venta o volver a comercializar\n\nLas notas de la actualización abarcan los artículos adquiridos a través de la tienda del juego, incluyendo la Armería, las ofertas de intercambio y el Mercado de la Comunidad. El alcance descrito es más amplio que el de los artículos de la Armería por sí solos.\n\nValve — Notas de la versión de «10/2/2024» ↗\nEntrada original y enlace enviado\n\nCS2: The Armory / 7-Día de retención\n\nRevisa el código fuente enviado ↗\n202409-18Fecha de presentación\nOperaciones bursátilesVerificado parcialmente\nRestricciones para nuevos dispositivos verificadas en las páginas de ayuda\n\nLa documentación oficial de soporte de Steam confirma una restricción de operaciones intradía 7-al iniciar sesión desde un nuevo dispositivo que no haya sido autorizado durante al menos 7 días. Aunque la fecha exacta de implementación de septiembre 18, 2024, no figura como hito en el registro de cambios, la funcionalidad está plenamente documentada.\n\nSteam Asistencia — Restricciones comerciales y de mercado ↗\nEntrada original y enlace enviado\n\nRestricción comercial para el inicio de sesión en un nuevo dispositivo\n\nRevisa el código fuente enviado ↗\n202402-14Fecha de presentación\nComunidadVerificado parcialmente\nSe ha implementado el tiempo de espera para el cambio de nombre en 2024\n\nLos registros de la comunidad y de los desarrolladores confirman que, a principios de 2024,, Valve introdujo, sin previo aviso, 2-un tiempo de espera de4 horas inmediatamente después de un cambio de nombre de perfil, con el fin de mitigar las estafas por suplantación de identidad. Dado que Valve no publicó ningún comunicado de prensa oficial, registro de cambios del cliente ni artículo de soporte técnico sobre esta restricción, la fecha de febrero 14 que se ha facilitado carece de verificación formal; la guía de Steam Workshop sirve como corroboración indirecta de la comunidad, más que como documentación oficial Valve.\n\nSteam Guía del taller (corroboración indirecta) — Detalles sobre la restricción al cambio de nombre ↗\nEntrada original y enlace enviado\n\nSuspensión del cambio de nombre de perfil o avatar\n\nRevisa el código fuente enviado ↗\n202312-04Fecha de verificación\nAPIEvento y fecha confirmados\nLa creación de la clave requiere una confirmación a través del móvil\n\nSe ha comprobado que la introducción de la confirmación móvil obligatoria de Steam Guard para la creación de claves en la web API tuvo lugar a finales de 2023,, tal y como lo documentan las bibliotecas de desarrolladores de terceros. La fecha exacta de diciembre 4, 2023, corresponde al periodo de implantación observado en la comunidad de desarrolladores.\n\nDocumentación para administradores — 2024 de marzo ↗archivado en 2026-09-24 ↗\nEntrada original y enlace enviado\n\nConfirmación a través del móvil para las claves de API\n\nRevisa el código fuente enviado ↗\n202310-24Fecha de verificación\nDesarrolladorEvento y fecha confirmados\nEntra en vigor la solicitud de autorización (FA) obligatoria de 2para la publicación de las versiones del juego\n\nEl anuncio oficial de Valve sobre Steamworks, publicado el 10, de octubre en 2023,, confirma que, a partir del 24, de octubre en 2023,, cualquier cuenta que publique una versión en la rama predeterminada de una aplicación ya lanzada deberá autorizar el cambio mediante SMS o a través de la aplicación móvil Steam. Este cambio se ha reflejado directamente en la página web SetAppBuildLive API.\n\nSteamworks: mejoras de seguridad para la gestión de compilaciones y usuarios ↗archivado en 2025-12-03 ↗\nEntrada original y enlace enviado\n\nAutenticación multifactorial (MFA) por SMS para la publicación de versiones de videojuegos\n\nRevisa el código fuente enviado ↗\n202307-12Fecha de presentación\nComunidadVerificado parcialmente\nAdvertencias sobre el contenido de las biografías personalizadas señaladas por la comunidad\n\nSteam Los informes de la comunidad, que se remontan a julio 2023, indican que las biografías de los perfiles personalizados que contenían enlaces externos o palabras clave comenzaron a mostrar advertencias automáticas sobre el contenido. La fecha de envío, 12, 2023,, coincide con la primera oleada de informes de los usuarios en los foros de la comunidad de Steam.\n\nSteam Foro de la comunidad — Informes sobre advertencias de contenido biográfico ↗\nEntrada original y enlace enviado\n\nAdvertencia sobre el contenido de la biografía personalizada\n\nRevisa el código fuente enviado ↗\n202301-25Fecha de presentación\nComunidadVerificado parcialmente\nFiltrado de enlaces de perfil y tiempos de espera para la edición activos\n\nLa documentación oficial de soporte de Steam confirma que los enlaces de las biografías personalizadas se filtran y que los cambios abusivos de nombre o avatar pueden dar lugar a prohibiciones de edición. Si bien la implementación exacta del periodo de espera de una hora 4-el 1 de enero 25, 2023, marca el inicio observado, el mecanismo de filtrado de enlaces en sí mismo está plenamente activo, tal y como se indica en la página de ayuda facilitada.\n\nSteam Asistencia técnica — Restricciones sobre el nombre de perfil y el avatar ↗\nEntrada original y enlace enviado\n\nPerfil ENLACE ELIMINADO / Tiempo de espera\n\nRevisa el código fuente enviado ↗\n202210-24Fecha de verificación\nAutenticaciónEvento y fecha confirmados\nSteam Transición de los clientes a los tokens de actualización y de acceso de OAuth\n\nPrincipales actualizaciones de Valve para clientes y aplicaciones móviles en octubre 2022 ha renovado por completo el sistema de autenticación de Steam. La antigua estructura de cookies de sesión se ha sustituido por tokens de acceso y de actualización basados en OAuth, y se ha introducido una lista de dispositivos autorizados activos para permitir la revocación manual de las sesiones activas.\n\nValve — Actualización de la aplicación móvil «Steam» y renovación del sistema de autenticación ↗\nEntrada original y enlace enviado\n\nSteam Revisión del proceso de inicio de sesión / Truncamiento de cookies\n\nConsulta el anuncio de «Valve» ↗\n202210-12Fecha de verificación\nAutenticaciónEvento y fecha confirmados\nInicio de sesión mediante código QR y gestión de dispositivos autorizados\n\nEn el anuncio de Valve sobre «12» del mes de octubre se describen el inicio de sesión mediante código QR, la aprobación o denegación de inicios de sesión y una lista de dispositivos que pueden revocar el acceso a la cuenta.\n\nValve — Ya está disponible la versión actualizada de la aplicación móvil «Steam» ↗\nEntrada original y enlace enviado\n\nSteam Aplicación móvil 3.0 / Inicio de sesión mediante código QR\n\nRevisa el código fuente enviado ↗\n202205-10Fecha de presentación\nAPIVerificado parcialmente\nSe han eliminado los puntos finales de cancelación de operaciones de la lista pública API\n\nLos registros de los desarrolladores confirman que, en mayo de 2022, Valve, se eliminaron de forma silenciosa los puntos finales de gestión de intercambios, como IEconService/CancelTradeOffer y DeclineTradeOffer, del sitio web API (documentado en node-steam-tradeoffer-manager #325). Aunque los métodos siguen funcionando en los protocolos de cliente privados, la fecha del 10, 2022, marca su retirada efectiva de las API web públicas para combatir los paneles fraudulentos.\n\nDebate de desarrolladores — Tema n.º325 (se ha eliminado «CancelTradeOffer») ↗· Sitio web de Steamworks API — Documentación de IEconService ↗\nEntrada original y enlace enviado\n\nEliminación de los puntos finales de cancelación de operaciones\n\nConsultar el problema n.º325 de node-steam-tradeoffer-manager ↗\n202005-25Fecha de verificación\nOperaciones bursátilesEvento y fecha confirmados\nLos objetos de «2» de Dota tienen un tiempo de espera de siete días para su intercambio\n\nEl 25, de mayo, 2020,, coincidiendo con el lanzamiento del Pase de Batalla de The International 10 (blog.dota2.com/2020/05/the-international-10-battle-pass/), Valve implementó un bloqueo de intercambio de un día 7-para los objetos de Dota 2, en consonancia con la política de 2018 para Counter-Strike. Esta restricción se aplica a todos los objetos intercambiados y a las compras realizadas en el Mercado.\n\nComunidad de Dota 2: bloqueo de intercambios y actualización del cliente de TI10 ↗\nEntrada original y enlace enviado\n\nDota 2 / 7-Bloqueo de operaciones intradía\n\nRevisa el código fuente enviado ↗\n201803-29Fecha de verificación\nOperaciones bursátilesEvento y fecha confirmados\nLos objetos de CS:GO intercambiados tienen un periodo de espera de siete días.\n\nLas notas oficiales de la versión confirman la fecha y la restricción. La URL facilitada redirigía a una actualización de mapas de 2013; la URL correspondiente a las notas de la versión termina en 20309.\n\nValve — Notas de la versión de «3/29/2018» ↗\nEntrada original y enlace enviado\n\nCS:GO / Bloqueo de operaciones intradía de «7-»\n\nRevisa el código fuente enviado ↗ archivado en 2025-02-26 ↗\n\nSigue las pistas. Comprueba la fuente.\n\nVolver a la investigación ↗",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Cronología de seguridad: de «2018» a «2026»"
          },
          {
            "level": 2,
            "id": null,
            "text": "La cronología"
          },
          {
            "level": 2,
            "id": null,
            "text": "Avisos sobre mensajes sospechosos en los chats de grupo"
          },
          {
            "level": 2,
            "id": null,
            "text": "Permisos detallados y listas blancas de direcciones IP para las claves de editor (anuncio sobre Valve)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Las operaciones con CS2 cuentan con un plazo de reversión de siete días"
          },
          {
            "level": 2,
            "id": null,
            "text": "Valve publica una advertencia sobre la seguridad de las cuentas en relación con las filtraciones de SMS"
          },
          {
            "level": 2,
            "id": null,
            "text": "Siete días antes de volver a poner a la venta o volver a comercializar"
          },
          {
            "level": 2,
            "id": null,
            "text": "Restricciones para nuevos dispositivos verificadas en las páginas de ayuda"
          },
          {
            "level": 2,
            "id": null,
            "text": "Se ha implementado el tiempo de espera para el cambio de nombre en 2024"
          },
          {
            "level": 2,
            "id": null,
            "text": "La creación de la clave requiere una confirmación a través del móvil"
          },
          {
            "level": 2,
            "id": null,
            "text": "Entra en vigor la solicitud de autorización (FA) obligatoria de 2para la publicación de las versiones del juego"
          },
          {
            "level": 2,
            "id": null,
            "text": "Advertencias sobre el contenido de las biografías personalizadas señaladas por la comunidad"
          },
          {
            "level": 2,
            "id": null,
            "text": "Filtrado de enlaces de perfil y tiempos de espera para la edición activos"
          },
          {
            "level": 2,
            "id": null,
            "text": "Steam Transición de los clientes a los tokens de actualización y de acceso de OAuth"
          },
          {
            "level": 2,
            "id": null,
            "text": "Inicio de sesión mediante código QR y gestión de dispositivos autorizados"
          },
          {
            "level": 2,
            "id": null,
            "text": "Se han eliminado los puntos finales de cancelación de operaciones de la lista pública API"
          },
          {
            "level": 2,
            "id": null,
            "text": "Los objetos de «2» de Dota tienen un tiempo de espera de siete días para su intercambio"
          },
          {
            "level": 2,
            "id": null,
            "text": "Los objetos de CS:GO intercambiados tienen un periodo de espera de siete días."
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/es/#briefing-heading",
          "https://steamcommunity.com/groups/SteamClientBeta?l=english",
          "http://web.archive.org/web/20260313235409/https://steamcommunity.com/groups/SteamClientBeta?l=english",
          "https://store.steampowered.com/news/posts/?enddate=1788390000",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/493839547938902179",
          "https://partner.steamgames.com/doc/webapi_overview/auth",
          "https://csmarketcap.com/blog/market-insights/from-boom-to-bust-cs2s-trade-protection-impact",
          "https://skinvault.gg/blog/cs2-trade-protection-explained/",
          "https://skin.land/blog/steam-changes-cs2-trade-ban-logic-timing/",
          "https://store.steampowered.com/news/posts/?appids=730&amp;enddate=1753924057&amp;feed=steam_announce%2F1000",
          "https://help.steampowered.com/faqs/view/3041-A87A-E5F6-B6AC",
          "https://store.steampowered.com/news/posts/?enddate=1747349559",
          "https://steamcommunity.com/ogg/593110/announcements/detail/533224478739530146",
          "https://store.steampowered.com/news/posts/?appids=730&amp;enddate=1728000977&amp;feed=steam_community_announcements",
          "https://steamcommunity.com/games/CSGO/announcements/detail/4447966961421256740",
          "https://help.steampowered.com/faqs/view/7F77-9E92-31E0-6B8E",
          "https://steamcommunity.com/sharedfiles/filedetails/?id=2926756889",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "http://web.archive.org/web/20260924181824/https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "https://steamcommunity.com/dev/apikey",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3749866608167579206",
          "http://web.archive.org/web/20251203174259/https://steamcommunity.com/groups/steamworks/announcements/detail/3749866608167579206",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3734103130194459461",
          "https://steamcommunity.com/discussions/forum/1/3807266184852932971/",
          "https://help.steampowered.com/faqs/view/225C-C51E-B8F0-55B2",
          "https://store.steampowered.com/news/group/4/view/3314112260640237775",
          "https://store.steampowered.com/news/posts/?appgroupname=Keep+in+touch&amp;enddate=1666122699&amp;feed=steam_blog",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/issues/325",
          "https://partner.steamgames.com/doc/webapi/IEconService",
          "https://steamcommunity.com/app/570/announcements/",
          "https://blog.dota2.com/2020/05/trading-cooldown/",
          "https://blog.counter-strike.net/2018/03/20309/",
          "https://blog.counter-strike.net/index.php/2018/03/20308/",
          "http://web.archive.org/web/20250226114333/https://blog.counter-strike.net/index.php/2018/03/20308/",
          "https://phishdestroy.io/steam_dossier/es/#vulnerability-profile"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/es/security_timeline.content.json",
      "export_json_sha256": "61a40ebe8233ac5b95668a3eaa0fddf47aad6c1dba00fe81dd7b004334e97fd6"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "es/skin_atlas.html",
      "language": "es",
      "title": "El atlas de lo que «Steam» no puede transportar — El dossier de «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/es/skin_atlas",
      "source_html_sha256": "98f795e2fc6b166cc03686d8bc35c8b68b07ef0248d7b6b06e6fd51616167f81",
      "exported_at": "2026-09-29T00:17:28.223Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "gallery",
            "source": "https://phishdestroy.io/steam_dossier/es/skin_atlas#gallery"
          }
        ],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "skin_atlas.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/es/skin_atlas.pdf?v=print-20260929-v5",
        "sha256": "7132d79f923e048fc578b382c149728a1889fe0f3ce22cb4c582b69ad9127a64",
        "bytes": 181161,
        "pages": 14
      },
      "integrity": {
        "signed_object": "skin_atlas.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "skin_atlas.content.json.asc",
        "digest_file": "skin_atlas.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify skin_atlas.content.json.asc skin_atlas.content.json",
          "sha256sum -c skin_atlas.content.json.sha256"
        ]
      },
      "content": {
        "text": "ANEXO IV-B / LA ESCALA DE PRECIOS / 2026-09-23\nAtlas de la escala de precios de Skin — El precipicio de la liquidez\n\nLas paradas de Valve en el mercado de dónde viene el dinero.\n\nLO QUE DEMUESTRA ESTA SECCIÓN\n\nEste atlas visual analiza las categorías de artículos de 30,266 en cinco catálogos de marketplaces, midiendo la cobertura del mercado por encima y por debajo del umbral de inclusión de Valve. Por debajo del límite de $1,800, Steam alberga 95.3% de categorías activas; inmediatamente por encima de este, la cobertura oficial se reduce a 1.9% (con una cobertura de 0.0% en activos corroborados). Esto pone de manifiesto un precipicio de liquidez abrupto y estructural en el que Valve delega la búsqueda de transacciones de alto valor a plataformas externas, al tiempo que mantiene el control total sobre la custodia de los activos subyacentes.\n\n← Volver al informe ejecutivo\n\nCada artículo de CS2 con un precio actual en cinco mercados se clasificó en una franja de precios según su precio de venta más bajo, y cada franja se evaluó en función de un único criterio: qué porcentaje de ella sigue estando disponible en el propio Mercado de la Comunidad de Valve. Por debajo del límite de anuncios de Valve, la respuesta es 95.3%. Encima de eso, la respuesta es 1.9%. La caída no es gradual y no se produce allí donde disminuye la demanda, sino que se produce exactamente según la norma publicada. De los 248 Las categorías de artículos en las que dos o más plataformas de venta fijan de forma independiente un precio superior al límite máximo, 100.0%, no tienen ningún anuncio Steam.\n\nMira el acantilado ↓Abrir la galería de artículos de «419»Método y límites\n30,266categorías de artículos analizadas\n95.3%de partidas fuera del capital social que figuran en el balance de Steam\n1.9%de los artículos que superan el límite máximo que ofrece Steam\n$78.6Mvalor mínimo del conjunto corroborado\n01 / la medición\nEl precipicio se produce según la norma, no a petición\n\nCada una de las categorías de artículos de 30,266 que se indican a continuación se clasifica en un nivel según su más barato Consulta en directo en BUFF163, CSFloat, Skinport, YouPin 898 y C5Game; solo se tienen en cuenta los artículos que aparecen en al menos dos de estas plataformas, por lo que ninguna publicación optimista por sí sola puede inventarse a un miembro del grupo. El panel superior muestra la cuota de mercado que el propio Valve sigue representando para cada grupo.\n\nPorcentaje de cada franja de precios que ofrece el mercado comunitario «Steam»\nparte superior: cobertura de vapor · parte inferior: elementos por banda, escala logarítmica\n0%\n25%\n50%\n75%\n100%\n100%\n96.9%\n95.9%\n97.3%\n91.1%\n76.8%\n14.5%\n2.9%\n1.5%\n0%\n0%\n0%\n4,632\n1¢–10¢\n7,152\n10¢–$1\n8,568\n$1–10\n5,941\n$10–100\n2,329\n$100–300\n1,292\n$300–1k\n193\n$1k–1.8k\n70\n$1.8k–3k\n67\n$3k–10k\n18\n$10k–30k\n3\n$30k–100k\n1\n$100k+\nitems\nlog\nVALVE’S LISTING CAP\nigual o inferior al límite de cotización de «Valve»por encima del límite: la normativa de «Valve» prohíbe su cotizacióncategorías de artículos del grupo\n\nPor «cobertura» se entiende que, en el momento de la captura, existía una cotización en tiempo real Steam para esa categoría. El gráfico inferior es logarítmico porque el catálogo está compuesto en su gran mayoría por valores muy baratos: si se leyera de forma lineal, todas las franjas por encima de $300 se aplanarían hasta la línea de base.\n\nLo que descarta la forma\n\nSi los artículos caros simplemente no tuvieran demanda, la cobertura se reduciría gradualmente a medida que subiera el precio. Pero no es así. Se mantiene en 76.8% en el rango de $300–$1k, para luego desplomarse hasta 14.5% en el rango inmediatamente inferior al límite máximo y 2.9% en el rango inmediatamente superior a este. Un efecto de la demanda no tiene en cuenta dónde Valve ha fijado su límite máximo. Una norma, sí.\n\nRango de precios\tCategorías de artículos\tCon una pregunta en directo en Steam\tSteam cobertura\tEjemplares que aparecen en Steam\n1¢–10¢\t4,632\t4,632\t100%\t8,223,227\n10¢–$1\t7,152\t6,931\t96.9%\t5,488,315\n$1–10\t8,568\t8,213\t95.9%\t3,939,538\n$10–100\t5,941\t5,780\t97.3%\t1,328,255\n$100–300\t2,329\t2,121\t91.1%\t364,466\n$300–1k\t1,292\t992\t76.8%\t187,504\n$1k–1.8k\t193\t28\t14.5%\t40,281\n$1.8k–3k\t70\t2\t2.9%\t9,592\n$3k–10k\t67\t1\t1.5%\t6,706\n$10k–30k\t18\t0\t0%\t1,366\n$30k–100k\t3\t0\t0%\t21\n$100k+\t1\t0\t0%\t2\n\nLas variantes de patrón y fase quedan excluidas de esta clasificación: Steam no incluye un nivel «blue-gem» ni una fase «Ruby» como entradas independientes en el mercado, por lo que contabilizarlas subestimaría la cobertura de Steam. Si se calcula sin el requisito de los dos mercados, la misma escala muestra 79.1% por debajo del límite y 6.5% por encima de él en los artículos de 37,204 —una diferencia más marcada, basada en pruebas menos sólidas—, razón por la cual no es la cifra citada.\n\n02 / calificación basada en pruebas\nEl precio de venta no es un precio\n\nCualquiera puede poner a la venta una P2000 por unos diez millones de yuanes. Antes de que una cifra de esta página se utilice para cualquier fin, se clasifica en función del número de mercados que cotizan el artículo de forma independiente por encima del límite máximo y de lo ajustada que sea la dispersión de las cotizaciones en torno a ese valor medio. Solo se incluyen las clasificaciones A y B, tanto aquí como en cualquier otra parte de este informe.\n\nA  Tres o más estantes coinciden\n\nTres o más plataformas de venta ofrecen el artículo a un precio superior al límite máximo y su mediana se sitúa en un25%o del precio más barato. 197 categorías, 18,218 ejemplares, $76,585,587.\n\nAusentes en «Steam»: 100.0%.\n\nB  Las dos estanterías coinciden\n\nDos mercados se ponen de acuerdo por encima del límite máximo, o tres lo hacen con un margen menor. 51 categorías, 176 ejemplares, $2,038,814.\n\nAusentes en «Steam»: 100.0%.\n\nC  Un estante — sin usar\n\nSolo hay un mercado en el que se registra una oferta por encima del límite máximo. 171 categorías, 247 copias. Se muestra en la galería para completar la información y se excluye de todos los totales de esta página.\n\nSe trata de solicitudes de presupuesto, no de pruebas de un precio.\n\nCuánto costó esta corrección y qué se consiguió con ella\n\nAl eliminar la calificación «C», se suprimen las categorías «171» y la cifra «$3,825,125» del titular. Lo que queda es más breve y mucho más difícil de rebatir: 248 categorías, 18,394 ejemplares disponibles, $78,624,401, y 100.0% de ellos —todos y cada uno— no están disponibles en el mercado de Valve. Las filas de grado C son la razón por la que ha variado la cifra; aparecen en la lista, no están ocultas.\n\nEntradas reservadas como objetos\n\nCualquier presupuesto que supere en más de tres veces el precio de venta más barato del mismo artículo se descarta. Al convertirlos al tipo de cambio que se desprende de los propios datos, la mayoría de ellos son cifras redondas en CNY, lo que indica que se trata de un valor provisional o del límite máximo de la plataforma, más que de una oferta real. Dado que todos los totales de esta página utilizan el más barato Hay que tener en cuenta que ninguna de estas cifras podría haber exagerado nunca un dato; se han excluido para que tampoco se pueda citar ninguna de ellas como titular.\n\nArtículo\tLa pregunta en directo más barata\tDeja a un lado\nSouvenir P2000 | Wicked Sick (Minimal Wear)\t$148,954\t$1,489,543\n★ Specialist Gloves | Crimson Kimono (Minimal Wear) | Phase 1\t$37,239\t$119,163\nSouvenir USP-S | Printstream (Factory New)\t$2,000\t$59,582\n★ Bowie Knife | Crimson Web (Factory New)\t$2,957\t$43,030\n★ Karambit | Marble Fade (Factory New) | 1st\t$11,916\t$38,874\nSticker | Ninjas in Pyjamas (Holo) | Katowice 2014\t$5,000\t$31,748\nSouvenir AWP | Dragon Lore (Battle-Scarred)\t$4,225\t$29,157\n★ Karambit | Doppler (Minimal Wear) | Ruby\t$7,122\t$27,273\nTodas las categorías de 419, con el objeto al que se refiere cada precio\n\nFuente: https://phishdestroy.io/steam_dossier/es/skin_atlas#gallery\n\n04 / adónde fue en realidad\nLas estanterías que contienen lo que Steam no ofrece\n\nLos mismos anuncios, agrupados según la plataforma en la que se encuentran. Este es un recuento de dónde se encuentran las copias enumerados, lo cual no es lo mismo que el lugar donde se encuentran y aquí no se interpreta como tal.\n\nValor mínimo de los anuncios que superan el límite máximo, por mercado\nel precio de venta más bajo por cada una de las copias que figuran en esa estantería\nYouPin 898\n$22,720,252\nBUFF163\n$22,022,606\nC5Game\n$12,560,543\nCSFloat\n$10,871,845\nSkinport\n$1,385,060\n\nJurisdicciones, en el orden indicado anteriormente: YouPin 898 — China · BUFF163 — China · C5Game — China · CSFloat — Estados Unidos · Skinport — Alemania / Malta. Un mismo artículo físico puede aparecer en más de una de estas secciones, por lo que estas cifras no deben sumarse a ningún otro total de mercado.\n\nValor mínimo por nivel de precio\ncómo se distribuye el dinero por encima del límite máximo\n$1.8k-3k\n$9,842,391\n$3k-10k\n$36,787,269\n$10k-50k\n$20,038,749\nover $50k\n$2,891,897\n05 / escasez que puedas contar\nLo escaso que es realmente el suministro\n\nCada artículo de CS2 tiene un valor de desgaste, y las plataformas de venta publican cuántas copias hay en cada rango de dicho valor. Esto convierte a «raro» de un adjetivo en un número, y es precisamente ese número el que explica por qué una sola cuenta comprometida merece la pena el esfuerzo de crear un kit de phishing a medida.\n\nAWP | La leyenda del dragón\n150 en venta · desde11,350 dólares\n0.00–0.01\n29 · $14,730\n0.01–0.02\n54 · $11,618\n0.02–0.03\n26 · $11,350\n0.03–0.04\n25 · $11,618\n0.04–0.07\n16 · $11,585\n\nAWP | Dragon Lore (nuevo de fábrica)\n\nM4A4 | Howl\n105 en venta · desde6,628 dólares\n0.00–0.01\n11 · $10,725\n0.01–0.02\n14 · $8,088\n0.02–0.03\n11 · $7,580\n0.03–0.04\n19 · $6,703\n0.04–0.07\n50 · $6,628\n\nM4A4 | Howl (nuevo de fábrica)\n\nAK-47 | Wild Lotus\n113 en venta · desde14,373 dólares\n0.00–0.01\n25 · $22,343\n0.01–0.02\n11 · $19,364\n0.02–0.03\n3 · $19,645\n0.03–0.04\n15 · $15,044\n0.04–0.07\n59 · $14,373\n\nAK-47| Wild Lotus (nuevo de fábrica)\n\nAWP | Gungnir\n173 en venta · desde11,618 dólares\n0.00–0.01\n28 · $17,875\n0.01–0.02\n21 · $13,600\n0.02–0.03\n32 · $12,065\n0.03–0.04\n29 · $11,735\n0.04–0.07\n63 · $11,618\n\nAWP | Gungnir (nuevo de fábrica)\n\nAK-47 | Serpiente de fuego\n278 en venta · desde663 dólares\n0.15–0.18\n87 · $730\n0.18–0.21\n49 · $712\n0.21–0.24\n52 · $703\n0.24–0.27\n18 · $715\n0.27–0.38\n72 · $663\n\nAK-47 | Serpiente de fuego (probada en el campo)\n\nCementado (todos los niveles / gema azul)\n76 en venta · desde1,638 dólares\n0.07–0.08\n1 · $2,516\n0.08–0.09\n4 · $2,482\n0.09–0.10\n6 · $3,856\n0.10–0.11\n7 · $2,797\n0.11–0.15\n58 · $1,638\n\nAK-47 | Cementado (desgaste mínimo) | Nivel1\n\nLas bandas son los rangos de liquidez propios de los mercados; solo se tienen en cuenta las bandas que cuenten con al menos una cotización en tiempo real. El precio que aparece junto a cada barra es la oferta más baja en tiempo real dentro de esa banda, por lo que la prima asociada a una liquidez reducida se puede leer directamente, en lugar de tener que deducirse.\n\n06 / movimiento, según datos de Steam\nLo que realmente se vendió en las estanterías de otros distribuidores\n\nValve No publica datos históricos útiles en este nivel, y este informe tampoco los incluye. Skinport sí publica sus propias ventas completadas en las últimas 24 horas, 7, 30 y 90 días, y esa es toda la dimensión temporal disponible aquí: un precio medio realizado por ventana de tiempo, indexado de modo que la mediana 90-del día sea 100. En ninguno de los dos gráficos se incluyen datos de «Steam».\n\nPrecio medio realizado, ventana móvil\nindexado a la mediana diaria de 90-· elementos de 6,758 con 20+ ventas\n85\n91\n97\n103\n100\n90d\n94\n30d\n90\n7d\n88\n24h\nVentas realizadas al día\nlos mismos artículos, las mismas ventanas\n7,621\n9,653\n11,684\n13,716\n12,700\n90d\n11,894\n30d\n9,540\n7d\n8,637\n24h\n\nSe trata de dos gráficos, y no de uno solo con dos escalas verticales: un índice y un recuento diario no comparten unidad, y representarlos en un eje común daría lugar a una comparación que no es válida. Las ventanas están anidadas y son de tipo «trailing» —la cifra diaria de 90-contiene la cifra horaria de 24-—, por lo que no se trata de una serie diaria y no debe interpretarse como tal. Lo que muestra es limitado y se expresa con claridad: a lo largo de las ventanas de seguimiento Skinport publicadas, el precio medio realizado se situó por debajo de su propia mediana de 90-días y el recuento diario de ventas descendió con él.\n\nSkinport ventas realizadas. Las ventanas están anidadas y son móviles, por lo que cada punto representa la mediana del precio realizado en la ventana móvil, indexada a la mediana del día 90-. No se trata de una serie diaria y no se incluyen datos de Steam.\n\n07 / de qué está hecho\nPegatinas de hace dieciséis años y un puñado de guantes\n\nEl segmento por encima del límite máximo no representa una amplia parte del mercado. Se centra en unas pocas piezas raras y unas pocas colecciones, varias de las cuales ya no se pueden conseguir en absoluto, y esa es precisamente la razón por la que la oferta no puede ajustarse al precio.\n\nCategorías por encima del límite, ordenadas por rareza\nnúmero de categorías de artículos\nCovert\n321\nClassified\n39\nRestricted\n24\nContraband\n12\nMil-Spec Grade\n9\nConsumer Grade\n9\nIndustrial Grade\n5\nCategorías por encima de la barra superior, por colección\nLas diez mejores colecciones\nThe St. Marc Collection\n13\nThe Cobblestone Collection\n13\nThe Norse Collection\n12\nThe Arms Deal Collection\n9\nThe Canals Collection\n7\nThe Gods and Monsters Collection\n6\nThe Revolution Collection\n4\nThe 2021 Train Collection\n4\nThe Rising Sun Collection\n4\nThe Chop Shop Collection\n4\n\nPor categoría: skin 366, sticker 48, container 3, sticker_slab 2.\n\n08 / la cantidad máxima que pagó realmente alguien\nMáximos respaldados por una operación, no por una cotización\n\nTodos los demás precios que aparecen en esta página son un preguntar — lo que quiere un vendedor. Estos son ventas: la transacción más alta completada Skinport registrada para cada artículo, en los últimos 90 días. Es la única cifra de este informe que alguien ha pagado realmente, y cada fila incluye un enlace a la plataforma de venta para que la cifra se pueda comprobar en su fuente original, en lugar de con nosotros.\n\n21,216artículos cuya venta se ha completado en el escaparate\n106vendidos a un precio igual o superior al límite máximo de cotización de «Valve»\n$14,192la venta individual más elevada realizada\n67/419categorías por encima del límite máximo con alguna venta registrada\nLas treinta ventas más elevadas cerradas durante el periodo\nArtículo\tVenta más alta\tPrecio medio de venta\tVentas\tPregunta ahora por la oferta más barata\tSteam\tÉchale un vistazo\nAWP | Gungnir (Factory New)\t$14,192\t$11,343\t5\t$11,490\tabsent\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Factory New)\t$12,387\t$12,387\t1\t$13,836\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Factory New)\t$11,779\t$11,063\t16\t$10,941\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Minimal Wear)\t$11,693\t$11,693\t1\t$9,946\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Minimal Wear)\t$10,437\t$10,437\t1\t$9,610\tabsent\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Blue Laminate (Minimal Wear)\t$9,772\t$37\t76\t$30\t$40\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Minimal Wear)\t$9,463\t$9,463\t1\t$9,500\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Minimal Wear)\t$9,104\t$9,026\t6\t$8,524\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Hedge Maze (Minimal Wear)\t$8,139\t$8,139\t1\t$6,819\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Field-Tested)\t$7,617\t$7,390\t4\t$7,194\tabsent\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Field-Tested)\t$7,615\t$7,615\t1\t$7,100\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Field-Tested)\t$7,149\t$7,006\t2\t$7,165\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Field-Tested)\t$6,711\t$6,194\t15\t$5,988\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Factory New)\t$6,679\t$6,613\t3\t$6,628\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Superconductor (Factory New)\t$6,084\t$6,084\t1\t$7,969\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Battle-Scarred)\t$5,750\t$5,413\t3\t$5,899\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Pandora's Box (Minimal Wear)\t$5,520\t$5,508\t3\t$4,998\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Vice (Factory New)\t$5,385\t$5,158\t2\t$5,700\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Minimal Wear)\t$5,342\t$4,989\t19\t$4,997\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Hedge Maze (Field-Tested)\t$5,334\t$4,862\t5\t$3,724\tabsent\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Vulcan (Factory New)\t$5,275\t$1,418\t12\t$1,280\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Well-Worn)\t$4,978\t$4,978\t1\t$4,942\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Well-Worn)\t$4,931\t$4,931\t1\t$5,445\tabsent\tSkinport CSFloat Steam\nAK-47 | Hydroponic (Factory New)\t$4,802\t$4,351\t2\t$3,648\tabsent\tSkinport CSFloat Steam\n★ Talon Knife | Case Hardened (Minimal Wear)\t$4,588\t$466\t16\t$442\t$630\tSkinport CSFloat Steam\nAWP | Medusa (Factory New)\t$4,484\t$4,484\t1\t$4,171\tabsent\tSkinport CSFloat Steam\n★ Specialist Gloves | Pillow Punchers (Factory New)\t$4,359\t$4,359\t1\t$4,302\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Pandora's Box (Field-Tested)\t$4,359\t$3,666\t11\t$3,245\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Field-Tested)\t$4,289\t$4,225\t8\t$4,022\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Battle-Scarred)\t$4,124\t$4,124\t1\t$4,279\tabsent\tSkinport CSFloat Steam\nEl mismo artículo, el mismo «90» días, un precio totalmente diferente\n\nSe limita a artículos con una mediana de $100 y al menos cinco ventas completadas, ya que, en el caso de un skin barato, una sola venta atípica distorsiona la proporción. Lo que queda está dominado por Cementado acabados, donde el diseño determina el precio y el mercado clasifica todos los diseños bajo un mismo nombre —el mismo mecanismo que se mide mediante «float» en la sección 05.\n\nArtículo\tMáximo frente a mediana\tVenta más alta\tPrecio medio de venta\tVentas\tÉchale un vistazo\n★ Talon Knife | Case Hardened (Minimal Wear)\t+884%\t$4,588\t$466\t16\tSkinport CSFloat Steam\nDesert Eagle | Cobalt Disruption (Factory New)\t+859%\t$1,210\t$126\t115\tSkinport CSFloat Steam\nAWP | BOOM (Minimal Wear)\t+814%\t$1,232\t$135\t89\tSkinport CSFloat Steam\nAK-47 | Case Hardened (Well-Worn)\t+769%\t$1,720\t$198\t70\tSkinport CSFloat Steam\nAWP | Graphite (Factory New)\t+761%\t$1,469\t$171\t124\tSkinport CSFloat Steam\n★ Talon Knife | Case Hardened (Field-Tested)\t+509%\t$2,437\t$400\t48\tSkinport CSFloat Steam\n★ Kukri Knife | Case Hardened (Minimal Wear)\t+448%\t$723\t$132\t69\tSkinport CSFloat Steam\n★ Kukri Knife | Case Hardened (Field-Tested)\t+415%\t$549\t$106\t128\tSkinport CSFloat Steam\n★ Ursus Knife | Case Hardened (Minimal Wear)\t+371%\t$597\t$127\t12\tSkinport CSFloat Steam\nAK-47 | Case Hardened (Field-Tested)\t+369%\t$1,037\t$221\t125\tSkinport CSFloat Steam\nAK-47 | Red Laminate (Minimal Wear)\t+360%\t$552\t$120\t18\tSkinport CSFloat Steam\nAWP | Asiimov (Field-Tested)\t+351%\t$528\t$117\t439\tSkinport CSFloat Steam\nAK-47 | Vulcan (Field-Tested)\t+337%\t$865\t$198\t241\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Nightwish (Factory New)\t+322%\t$625\t$148\t31\tSkinport CSFloat Steam\nAWP | Lightning Strike (Factory New)\t+319%\t$2,065\t$493\t198\tSkinport CSFloat Steam\nStatTrak™ AWP | Redline (Minimal Wear)\t+312%\t$574\t$139\t24\tSkinport CSFloat Steam\nStatTrak™ AWP | Asiimov (Battle-Scarred)\t+287%\t$524\t$135\t37\tSkinport CSFloat Steam\nAK-47 | Redline (Minimal Wear)\t+277%\t$562\t$149\t112\tSkinport CSFloat Steam\nAWP | Crakow! (Factory New)\t+275%\t$379\t$101\t72\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Vulcan (Factory New)\t+272%\t$5,275\t$1,418\t12\tSkinport CSFloat Steam\n\nSe trata de un máximo diario de 90-, NO de un máximo histórico, y abarca UN SOLO mercado. En ningún lugar de este informe se menciona ninguna cifra histórica. Los artículos que no cuentan con una venta en Skinport en el escaparate no aparecen en absoluto en esta exposición, razón por la cual el conjunto es más reducido que el censo.\n\nLos enlaces de verificación se crean a partir de los identificadores de la propia plataforma del catálogo. Apuntan a la página de cada tienda online correspondiente al artículo, de modo que el lector pueda contrastar la información con la fuente original en lugar de con nosotros. Los enlaces externos contienen rel=\"nofollow\": se trata de referencias, no de recomendaciones, y varios de los destinos son plataformas de venta online a las que esta investigación critica.\n\n09 / procedencia y límites\nDe dónde procede esto y qué es lo que no puede mostrar\n\nTodas las cifras que aparecen en esta página se han vuelto a calcular a partir de dos archivos de instantáneas cuyos hash se publican junto a ellas. Nada de lo que aquí aparece se ha copiado de un artículo de otra web.\n\nFuente y acceso\n\ncs2.sh API, GET /v1/prices/latest y GET /v1/schema, instantánea única, capturada en 2026-09-23T00:44:27.871388581Z, con precios en USD.\n\nLos datos se obtuvieron mediante una suscripción comercial de pago contratada por el solicitante de la solicitud de acceso a la información (GDPR), tal y como consta en el archivo, de acuerdo con las condiciones establecidas por el propio proveedor. No se ha extraído información de ningún mercado ni se ha utilizado ninguna credencial de ningún mercado. La clave del solicitante se almacena fuera de este repositorio y no aparece en ningún archivo de este.\n\nCómo se determina si un artículo cumple los requisitos\n\nCada artículo básico con al menos una oferta activa en BUFF, CSFloat, Skinport, YouPin o C5Game se clasifica en un rango de precios según su oferta MÁS BARATA, por lo que el rango nunca depende de Steam. La «Steam» es la proporción de artículos de ese rango que cuentan con alguna oferta activa Steam en el momento de la captura. Las variantes de patrón y fase se excluyen de la clasificación porque Steam no las muestra por separado; incluirlas subestimaría Steam. Las imágenes de render son las imágenes de catálogo de los mismos artículos, almacenadas localmente.\n\nImágenes renderizadas y derechos de imagen. Las imágenes renderizadas de los artículos del catálogo son imágenes del proveedor asociadas al mismo «market_hash_name» que las líneas de precios, almacenadas localmente para su visualización sin conexión y a través de IPFS. Las representaciones no son obra de PhishDestroy: todas las imágenes de los artículos, logotipos y capturas de pantalla siguen siendo propiedad de sus respectivos titulares (cs2.sh, CSFloat, Skinport, BUFF, YouPin, C5Game, Valve y otros). Se reproducen únicamente con fines de identificación y de información de interés público; no se reivindica ningún derecho de propiedad ni licencia.\n\nLo que no pudimos conseguir\n\nEl nivel de suscripción utilizado solo admite instantáneas actuales. Los puntos finales históricos y de archivo no estaban disponibles, y En ninguna parte de esta página se afirma que exista ninguna serie histórica. Más allá de las ventas con ventana móvil: Skinport se publica en la sección 06.\n\nUna instantánea, no una serie temporal. La ausencia de un anuncio en Steam en el momento de la captura no prueba que un artículo no vaya a aparecer nunca allí; se trata del estado registrado de la estantería en ese momento y, en el caso de los precios superiores al límite máximo, es también lo que exige la norma publicada por Valve: el Mercado Comunitario de Valve limita explícitamente los anuncios a $1,800 por artículo (con un saldo máximo en el monedero de Steam de $2,000; véase Steam Preguntas frecuentes sobre el mercado comunitario archivado en 2026-09-21 ↗ y Steam Contrato de suscripción, artículo 3.C archivado en 2026-09-24 ↗).\n\nCalificación\n\nEl precio de un artículo es siempre su cotización de venta más barata en tiempo real, por lo que un valor atípico elevado nunca puede inflar el total. La clasificación determina qué filas pueden incluirse en la cotización. Cualquier cotización que supere en más de tres veces la cotización de venta más barata del mismo artículo se descarta por no ser un precio en tiempo real. Calificación A: tres o más mercados siguen cotizando por encima del límite máximo y su mediana se sitúa dentro de un25 % del precio de venta más barato. Calificación B: dos mercados coinciden, o tres coinciden de forma menos ajustada. Calificación C: un único precio de venta, que no es un precio de mercado. En este informe solo se citan las calificaciones A y B.\n\nRegla de valores atípicos: cotización > 3.0multiplicada por el precio de venta más barato del mismo artículo.\n\nPor qué los totales son un mínimo\n\nPara cada tienda online, el artículo… más bajo El precio de venta se multiplica por el número de ejemplares que figuran en la lista de existencias. Todos los demás ejemplares tienen un precio igual o superior a ese precio de venta más bajo, por lo que el valor real publicado es más alto por definición, no por estimación. No se trata de una venta, ni de un flujo de caja, ni de una valoración de la economía de CS2.\n\nCompruébalo tú mismo\n\nLos conjuntos de datos derivados en los que se basan todos los gráficos de esta página se publican íntegramente: el conjunto de datos «atlas», la pantalla de clasificación y detección de artefactos, el censo en el que se basa y el manifiesto con el SHA-256o de cada instantánea sin procesar.\n\nUna corrección registrada en la apertura\n\nEn un borrador anterior del registro complementario, el primer artículo era un AK-47 de recuerdo | Point Disarray, cuyo precio de venta era de $148,954 en una plataforma de comercio electrónico china, mientras que Steam lo ofrecía a $119. Esa entrada es de categoría C: un solo estante, un solo ejemplar y ninguna otra plataforma que coincida. Se trata de un precio de venta, no de un precio de mercado, y se ha rebajado aquí y en esa página. El líder corroborado es Sticker | Titan (Holo) | Katowice 2014 a $66,285, según 4, en mercados situados a 5.2% de distancia entre sí — y que no aparecen en absoluto en Steam.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Atlas de la escala de precios de Skin — El precipicio de la liquidez"
          },
          {
            "level": 2,
            "id": null,
            "text": "El precipicio se produce según la norma, no a petición"
          },
          {
            "level": 3,
            "id": null,
            "text": "Lo que descarta la forma"
          },
          {
            "level": 2,
            "id": null,
            "text": "El precio de venta no es un precio"
          },
          {
            "level": 3,
            "id": null,
            "text": "A  Tres o más estantes coinciden"
          },
          {
            "level": 3,
            "id": null,
            "text": "B  Las dos estanterías coinciden"
          },
          {
            "level": 3,
            "id": null,
            "text": "C  Un estante — sin usar"
          },
          {
            "level": 3,
            "id": null,
            "text": "Cuánto costó esta corrección y qué se consiguió con ella"
          },
          {
            "level": 3,
            "id": null,
            "text": "Entradas reservadas como objetos"
          },
          {
            "level": 2,
            "id": null,
            "text": "Todas las categorías de 419, con el objeto al que se refiere cada precio"
          },
          {
            "level": 2,
            "id": null,
            "text": "Las estanterías que contienen lo que Steam no ofrece"
          },
          {
            "level": 2,
            "id": null,
            "text": "Lo escaso que es realmente el suministro"
          },
          {
            "level": 2,
            "id": null,
            "text": "Lo que realmente se vendió en las estanterías de otros distribuidores"
          },
          {
            "level": 2,
            "id": null,
            "text": "Pegatinas de hace dieciséis años y un puñado de guantes"
          },
          {
            "level": 2,
            "id": null,
            "text": "Máximos respaldados por una operación, no por una cotización"
          },
          {
            "level": 3,
            "id": null,
            "text": "Las treinta ventas más elevadas cerradas durante el periodo"
          },
          {
            "level": 3,
            "id": null,
            "text": "El mismo artículo, el mismo «90» días, un precio totalmente diferente"
          },
          {
            "level": 2,
            "id": null,
            "text": "De dónde procede esto y qué es lo que no puede mostrar"
          },
          {
            "level": 3,
            "id": null,
            "text": "Fuente y acceso"
          },
          {
            "level": 3,
            "id": null,
            "text": "Cómo se determina si un artículo cumple los requisitos"
          },
          {
            "level": 3,
            "id": null,
            "text": "Lo que no pudimos conseguir"
          },
          {
            "level": 3,
            "id": null,
            "text": "Calificación"
          },
          {
            "level": 3,
            "id": null,
            "text": "Por qué los totales son un mínimo"
          },
          {
            "level": 3,
            "id": null,
            "text": "Compruébalo tú mismo"
          },
          {
            "level": 3,
            "id": null,
            "text": "Una corrección registrada en la apertura"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/es/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/es/skin_atlas#gallery",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://skinport.com/market?search=AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260924114457/https://store.steampowered.com/subscriber_agreement/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-atlas.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-artefact-screen.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-above-the-ceiling.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/es/skin_atlas.content.json",
      "export_json_sha256": "a963993ec8139714d737fd37de7bc419c8b8ca2edb16a7bc0dcfea0d1cb495f0"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "es/social_graph.html",
      "language": "es",
      "title": "Sigue las conexiones registradas — El dossier «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/es/social_graph",
      "source_html_sha256": "d2bb98759904904c719bd04f02fb9b083ce1b54ee3278df757889c9dd25fcd32",
      "exported_at": "2026-09-29T00:17:27.223Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "social_graph.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/es/social_graph.pdf?v=print-20260929-v5",
        "sha256": "9499efa2ed633123fff5b56c1f4aad3c026bd176b68f3b95efe5e65f33184360",
        "bytes": 119765,
        "pages": 6
      },
      "integrity": {
        "signed_object": "social_graph.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "social_graph.content.json.asc",
        "digest_file": "social_graph.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify social_graph.content.json.asc social_graph.content.json",
          "sha256sum -c social_graph.content.json.sha256"
        ]
      },
      "content": {
        "text": "Sigue las conexiones.Revisa cada relación.\n\nBusca un perfil. Elige un tipo de relación. Sigue a sus vecinos directos en los registros capturados. Herramienta de investigación: Las aristas representan relaciones públicas, no son prueba de contacto directo, coordinación privada ni conducta indebida entre dos nodos cualesquiera. La mejor forma de interpretar una disposición de nodos de tipo «3,435-» es utilizando filtros.\n\nExplora una relación cada vez\n\n💡 Haz clic y arrastra los nodos para reorganizar el gráfico. Pasa el cursor por encima para ver los perfiles detallados. Líneas continuas de color verde azulado = amistades; líneas discontinuas de color ámbar = comentarios mutuos.\n\nTipo de relaciónPerfil y vecinos más cercanos\n\n3,435 perfiles · enlaces grabados de 4,551\n\nBusca y elige un perfil, o haz clic en un nodo. Solo se mantendrán sus vecinos directos registrados. Una arista registra una relación; no establece una coordinación privada.\n\nPerfiles del conjunto de datos capturado\n\nTabla completa de fuentes: Descargar todas las filas de «3,435» (CSV). La tabla siguiente muestra inicialmente las primeras 25 filas; la función de búsqueda y la paginación permiten consultar el conjunto de datos completo.\n\n1–25 /3,435 filas\nNombre del personaje\tSteamID64\tPrivacidad\tEstado\tAfiliaciones a grupos\tExistencias inmovilizadas (USD)\tUbicación\nMahatma Gandhi\t76561198333721623\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tPH\nGalley//갤리🌠🌙\t76561198043416832\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tKP\n$Schlächter\t76561198860277343\tPUBLIC\tClean\tsteambans\t$0.00\tUnknown\n❄r3dsn0w000™❄ [Cristi]🎮\t76561197986767957\tPUBLIC\tClean\tCommunityLegends\t$0.00\tRO\n(2a03) Wolfy\t76561197991671851\tPUBLIC\tCommunity\tsr_public\t$0.00\tUS\nZloy2288\t76561198038578334\tPUBLIC\tClean\tsteambans\t$0.00\tBY\njessy\t76561198039125237\tPUBLIC\tCommunity, VAC (1x)\tCommunityLegends\t$0.00\tJP\nJithraRufure\t76561198071896910\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\n| Níllerdínho |\t76561198003487438\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tDK\nJones is back\t76561198023013026\tPRIVATE\tVAC (1x)\tsteambans\t$0.00\tUnknown\nUNEX | ★✠☠ MoH3st ☠✠\t76561198050763123\tPUBLIC\tClean\tsteambans\t$0.00\tDE\nTrojan\t76561198048457084\tPUBLIC\tClean\tCommunityLegends\t$0.00\tDE\n𝗠𝗮𝘆𝘂 ❤\t76561199377967696\tPUBLIC\tClean\tsr_public\t$0.00\tIS\nbig fucking idiot\t76561198871206397\tPUBLIC\tVAC (1x)\tsteambans\t$0.00\tUnknown\nSOFF Games\t76561198227129276\tPUBLIC\tClean\tcommunitymoderators\t$0.00\tRU\nThijminecraft02\t76561198253895669\tPUBLIC\tClean\tSteamIDcouk SArchive\t$0.00\tNL\nStatic-sama\t76561198289329793\tPUBLIC\tClean\tsteambans\t$0.00\tJP\n𝙸mmortal 𝚂targazer\t76561198142116760\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\nCommander Keen\t76561197987773287\tPUBLIC\tClean\tsteambans\t$0.00\tBE\nS1mX\t76561199648509165\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\nmixwell\t76561199276547472\tPUBLIC\tClean\tsr_public\t$0.00\tJP\nP90_GOD_YyEs™\t76561198285821942\tPUBLIC\tClean\tsteambans\t$0.00\tHK\nhewwo?\t76561199133807546\tPUBLIC\tVAC (1x)\tsteambans\t$0.00\tCH\n♕Kamikaze Atze♕\t76561198002700103\tPUBLIC\tClean\tsteambans\t$0.00\tDE\nPastica\t76561198154655970\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tDZ\nVínculos de amistad registrados\n\nTabla completa de fuentes: Descargar todas las filas de 4,299 (CSV). La tabla siguiente muestra inicialmente las primeras 25 filas; la función de búsqueda y la paginación permiten consultar el conjunto de datos completo.\n\n1–25 /4,299 filas\nUsuario A\tDirección\tUsuario B\tTipo de relación\nMahatma Gandhi\n76561198333721623\t↔\tDeskjet\n76561198272738437\tMutual Friends\nGalley//갤리🌠🌙\n76561198043416832\t↔\tomega\n76561197960274529\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tFisty\n76561198057301486\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tFaalagorn\n76561198001116101\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tMURK\n76561198036995672\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tÅρøᴛʜℯᴛȋᴄÅʟȋℯη ♛👽♛\n76561197984615267\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tsilatrak\n76561197999629462\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tBlack Blade\n76561198083368493\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tAvenger\n76561197978249317\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tRemtar\n76561198124322650\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tCato\n76561197961345984\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t✪ G λ M Ξ ®\n76561197994308495\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tclees42\n76561198030936806\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t𝓜ε𝔰𝔥 | AusLevels\n76561198108828539\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tSgtFopper™\n76561198002555892\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t❥Miss Bee\n76561198046958996\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tTesTy\n76561198032370068\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tskl_andrey\n76561198136881436\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t\"Exekutor\"\n76561198009583947\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tAraripe\n76561198103754372\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tsteve6678\n76561198053200093\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\ttrinner\n76561197970359081\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tSteph S.\n76561198025653291\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tKirito\n76561198154545657\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tDoc. todt\n76561197984492467\tMutual Friends\nEnlaces a comentarios grabados\n\nTabla completa de fuentes: Descargar todas las filas de «252» (CSV). La tabla siguiente muestra inicialmente las primeras 25 filas; la función de búsqueda y la paginación permiten consultar el conjunto de datos completo.\n\n1–25 /252 filas\nAutor\tDirección\tPerfil del público objetivo\tFecha\tTexto del comentario\nDeskjet\n76561198272738437\t→\tMahatma Gandhi\n76561198333721623\t16 September, 2021 @ 11:02:05 pm PDT\t\"𝑵𝒐𝒘 𝒊𝒇 𝑰 𝒇𝒖𝒄𝒌 𝒕𝒉𝒊𝒔 𝒎𝒐𝒅𝒆𝒍𝑨𝒏𝒅 𝒔𝒉𝒆 𝒋𝒖𝒔𝒕 𝒃𝒍𝒆𝒂𝒄𝒉𝒆𝒅 𝒉𝒆𝒓 𝒂𝒔𝒔𝒉𝒐𝒍𝒆𝑨𝒏𝒅 𝑰 𝒈𝒆𝒕 𝒃𝒍𝒆𝒂𝒄𝒉 𝒐𝒏 𝒎𝒚 𝑻-𝒔𝒉𝒊𝒓𝒕𝑰'𝒎𝒎𝒂 𝒇𝒆𝒆𝒍 𝒍𝒊𝒌𝒆 𝒂𝒏 𝒂𝒔𝒔𝒉𝒐𝒍𝒆\" - Nelson Mandela\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t22 November, 2021 @ 4:10:28 pm PDT\thttps://anige.horigiri.net/?cat=22\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t18 November, 2021 @ 12:45:26 am PDT\thttps://gamerch.com/umamusume/entry/250411\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t8 August, 2021 @ 4:13:25 am PDT\thttps://modoocode.com/304\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t6 February, 2021 @ 3:35:05 pm PDT\t▤ ∫︹- -ω⁾ ⁽︹▓▓︺\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t11 December, 2019 @ 1:50:53 am PDT\thttps://blog.naver.com/aksenwlddj12/221369410039\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t2 October, 2019 @ 7:11:59 am PDT\tǤαllєу║︎갤리..۩\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t9 April, 2019 @ 12:51:28 pm PDT\tExplosiveDamage(owner, from, maxrange, minrange, distmultiplier, dmgmultiplier, mindamage, typ, damagetype, ignore)\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 12:22:47 pm PDT\tinfo - sh_titles.lua\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 12:21:46 pm PDT\tlocal nibbas = 1344 init.lua\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 11:31:58 am PDT\thttp://foreign.aladin.co.kr/shop/wproduct.aspx?ItemId=123955531&start=slayer\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t3 April, 2019 @ 1:26:41 am PDT\tǤαllєу\nLei\n76561198982197954\t→\tJithraRufure\n76561198071896910\t29 December, 2024 @ 12:58:08 pm PDT\t+rep he knows how 2 rush B ￣ヘ￣\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t2 September, 2026 @ 5:16:55 am PDT\tlol\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t20 August, 2026 @ 6:11:03 am PDT\t?\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t25 July, 2026 @ 7:20:05 am PDT\thahahahaha\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t30 June, 2026 @ 12:52:42 pm PDT\twow\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t30 June, 2026 @ 12:41:32 pm PDT\txD\nvalorant enjoyer\n76561199112142402\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:26:30 pm PDT\toh no!!\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:26:11 pm PDT\toh no!!\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:22:22 pm PDT\tomg !!! they know my secret, omg!!!\nvalorant enjoyer\n76561199112142402\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:21:39 pm PDT\t+rep good ♥♥♥♥♥ player\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:20:50 pm PDT\tomg! u cant cheat on secure gaben servers, omg dont report me, they ban me for boosted omg\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 8:37:11 pm PDT\txD\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t28 June, 2026 @ 1:58:14 pm PDT\twow",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Sigue las conexiones.Revisa cada relación."
          },
          {
            "level": 2,
            "id": null,
            "text": "Explora una relación cada vez"
          },
          {
            "level": 2,
            "id": null,
            "text": "Perfiles del conjunto de datos capturado"
          },
          {
            "level": 2,
            "id": null,
            "text": "Vínculos de amistad registrados"
          },
          {
            "level": 2,
            "id": null,
            "text": "Enlaces a comentarios grabados"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-profiles.csv",
          "https://steamcommunity.com/profiles/76561198333721623",
          "https://steamcommunity.com/profiles/76561198043416832",
          "https://steamcommunity.com/profiles/76561198860277343",
          "https://steamcommunity.com/profiles/76561197986767957",
          "https://steamcommunity.com/profiles/76561197991671851",
          "https://steamcommunity.com/profiles/76561198038578334",
          "https://steamcommunity.com/profiles/76561198039125237",
          "https://steamcommunity.com/profiles/76561198071896910",
          "https://steamcommunity.com/profiles/76561198003487438",
          "https://steamcommunity.com/profiles/76561198023013026",
          "https://steamcommunity.com/profiles/76561198050763123",
          "https://steamcommunity.com/profiles/76561198048457084",
          "https://steamcommunity.com/profiles/76561199377967696",
          "https://steamcommunity.com/profiles/76561198871206397",
          "https://steamcommunity.com/profiles/76561198227129276",
          "https://steamcommunity.com/profiles/76561198253895669",
          "https://steamcommunity.com/profiles/76561198289329793",
          "https://steamcommunity.com/profiles/76561198142116760",
          "https://steamcommunity.com/profiles/76561197987773287",
          "https://steamcommunity.com/profiles/76561199648509165",
          "https://steamcommunity.com/profiles/76561199276547472",
          "https://steamcommunity.com/profiles/76561198285821942",
          "https://steamcommunity.com/profiles/76561199133807546",
          "https://steamcommunity.com/profiles/76561198002700103",
          "https://steamcommunity.com/profiles/76561198154655970",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-connections.csv",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-comments.csv"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/es/social_graph.content.json",
      "export_json_sha256": "27f42cba4580fc54a38239db4037e3208a3c1d1fe11bd8c491753ccf82b4fbd1"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "es/steam_enforcement_evidence.html",
      "language": "es",
      "title": "Normas frente a respuestas — El dossier «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/es/steam_enforcement_evidence",
      "source_html_sha256": "aa46055bf26d490f0a82297e2db60c670d9058aa8662232f1aff612c5c0073fb",
      "exported_at": "2026-09-29T00:17:28.680Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "steam_enforcement_evidence.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/es/steam_enforcement_evidence.pdf?v=print-20260929-v5",
        "sha256": "d7852d505d27a1af154df73eb87d3a73c825a4a81b47e99f34bd6f3c29307de1",
        "bytes": 377318,
        "pages": 36
      },
      "integrity": {
        "signed_object": "steam_enforcement_evidence.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "steam_enforcement_evidence.content.json.asc",
        "digest_file": "steam_enforcement_evidence.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify steam_enforcement_evidence.content.json.asc steam_enforcement_evidence.content.json",
          "sha256sum -c steam_enforcement_evidence.content.json.sha256"
        ]
      },
      "content": {
        "text": "Suplemento de pruebas / registros vinculados a fuentes\nSteam Pruebas de cumplimiento: registros de apoyo y red de desarrolladores\n\nLa norma. La respuesta.\n\nLO QUE DEMUESTRA ESTA SECCIÓN\n\nEsta sala de pruebas compara el Acuerdo de Suscripción oficial de Valve con registros de medidas coercitivas fechados, resoluciones de disputas de asistencia técnica y registros de la red de desarrolladores en los repositorios de 252 y los perfiles de 3,320. Demuestra que los titulares de cuentas normales se enfrentan a medidas coercitivas irrefutables y al cierre de los servicios de asistencia tras la compromisión de sus sesiones, mientras que las operaciones comerciales de bots de gran volumen funcionan de forma continua con acceso a la infraestructura pública.\n\n← Volver al informe ejecutivo\n\nLee la restricción por escrito. Abre la respuesta grabada. Compara lo que muestra la fuente con lo que queda sin respuesta.\n\nAsistencia y recursos ↓Infraestructuras públicas ↓\n252registros del repositorio\n3,320perfiles públicos\n4,214pares distintos de perfil y repositorio\n98,902pares de perfiles con repositorios compartidos\n01 / Apoyo, sanciones y restauración\nLee la denuncia.Adjunta el archivo original.\nGalería de denegaciones de ayudas (Exposiciones de 981) ↗Descargar los registros seleccionados ↓\nHFB / EL CASO DE LA EXTERNALIZACIÓNEl compromiso reconocido.\nLos despidos de los que se ha informado.\n\nConsulta la respuesta del servicio de asistencia que se reproduce a continuación y la fuente de la afirmación relativa al personal de los contratistas.\n\nAbrir el caso y sus fuentes →\n\nA continuación: cinco conservados publicaciones públicas en Reddit de la recopilación de asistencia técnica facilitada. Cada registro documenta una interacción notificada con el sistema de asistencia técnica de Valve, conservada con su enlace de origen original, la posición de la captura y el texto completo. Se trata de testimonios de las víctimas. Los registros de asistencia técnica autenticados que podrían confirmarlos o contradecirlos están en poder de Valve y no se han hecho públicos.\n\n01\nBan & review2024-12-09\nPermanent sanction & closed appeals\n\nThe author reports a permanent account ban, repeated ticket closures and a planned GDPR access request.\n\nREDDIT / PUBLIC TESTIMONYr/ohnePixelCapture record 294\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 303 words\nPermanently banned Steam account without a clear explanation, need help!\n\nsteam_support_tickets_MEGA.json / record 294\n\nHey everyone,\n\nI’m in a really frustrating situation, and I’m hoping someone here can help me or offer advice. My Steam account was just permanently banned for allegedly violating the Steam Subscriber Agreement, and I have no idea why.\n\n# What Steam Support told me:\n\nThe support message said my account was banned due to:\n\n* Suspicious activities related to transferring or attempting to sell/trade the account.\n* Community reports and other unspecified factors.\n\nThey added that the ban is permanent and that they can't help me further. They also warned that future support requests regarding this ban might be ignored. 😞\n\n# Why I’m contesting this ban:\n\n* I have never sold, traded, or transferred my account. I’ve been the legitimate owner since the beginning.\n* On the day the ban occurred, I did nothing noteworthy that could have triggered such a sanction.\n* I received no prior warning, which feels incredibly unfair.\n\n# What I’ve tried so far:\n\n* Contacting Steam Support: I explained my situation and asked for more details, but they’re sticking to their decision and closing my tickets.\n* I’m preparing a request based on my Right of Access (GDPR) to get all the data related to my account.\n\n# Questions for the community:\n\n1. Has anyone successfully had a permanent ban lifted on Steam?\n2. Are there steps I can take to prove I’m the legitimate owner of the account?\n3. Any advice on how to word my request to convince support to reconsider my case?\n4. Would it be helpful to contact the CNIL (I’m based in France) to force Steam to provide more information?\n\nI’m really desperate at the thought of losing all my games, purchases, and years of playtime. Thanks in advance for any help and advice you can give!\n\nhttps://preview.redd.it/jk9qv0gmhv5e1.png?width=1289&amp;format=png&amp;auto=webp&amp;s=b3a333ebb08ea133e2c8747ba126f5a68283d9f7\n\nhttps://preview.redd.it/4sopt0gmhv5e1.png?width=1022&amp;format=png&amp;auto=webp&amp;s=56195d5336118faf9413f1514ead7e8d24c788c3\n\nhttps://preview.redd.it/eqrxw0gmhv5e1.png?width=996&amp;format=png&amp;auto=webp&amp;s=ff3539d28ab754e513ad471822c5de652920101d\n\nhttps://preview.redd.it/728xz0gmhv5e1.png?width=1034&amp;format=png&amp;auto=webp&amp;s=bc5335673509929669af785aa244bf8d2dc58da8\n\n02\nSupport access2025-05-09\nAccount recovery & a reported $10,000 loss\n\nThe author alleges that support reset credentials and removed account protection following another person’s recovery ticket.\n\nREDDIT / PUBLIC TESTIMONYr/legaladviceCapture record 110\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 193 words\nGot $10k stollen from steam inventory due to steam' support fault.\n\nsteam_support_tickets_MEGA.json / record 110\n\nLocation: Quebec, Canada.\n\nLast year, someone hacked my Steam account and stole items worth about $10,000 USD. I only noticed this last week. When I talked to Steam Support, they admitted that someone submitted a ticket to make changes on the account and Steam Support reset my password and turned off all my account security.\n\nI asked Steam Support about getting my items back, but they said there was nothing they could do. They told me I should follow their security recommendations.\n\nThe problem is, I did everything they \"suggested\" to protect an account:\n\n* I had two-factor authentication.\n* My phone number was connected to my account.\n* I used Steam Guard.\n* I printed recovery codes and kept them in a safe.\n\nEven though I did all these things, Steam Support still gave someone else access to my account. The stolen items had been in my account since around 2016-2017. Also, I had not logged in for a few years, so I didn’t accidentally give my information to a fake website.\n\nIs there anything I can do, or do I just have to accept losing $10,000 USD?\n\nThanks for your help.\n03\nRestoration2022-07-07\nA reported $500+ loss & template replies\n\nThe author describes an account compromise, disputed transactions and a support response that allegedly did not address the submitted evidence.\n\nREDDIT / PUBLIC TESTIMONYr/DotA2Capture record 45\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 410 words\nFunds stolen through steam market. Disappointed with Steam response.(or lackthereof)\n\nsteam_support_tickets_MEGA.json / record 45\n\nOn 6th July 2022, 44 unauthorized transactions were made on the steam market using my steam wallet funds totalling roughly $500+ USD to buy worthless 1 cent Dota 2 items. This happened during the wee hours in the morning and i contacted them first thing when i woke up. \n\nI have 2FA enabled all the time, and always thought this would not happen to me as I do not go on betting sites/click sketchy links. My account password + emails were not changed, nor did they take my inventory, just that my funds were used illicitly. Also when I went to disable other APIs, it says there are no other APIs to disable. Shows that it wasn't through me clicking sketchy links and leaving my account details there. Would have lost the whole account if i did so.\n\nWhat baffles me is how did they bypass my 2FA to login my account? Why doesn't steam market purchases go through 2FA as well? First time in 9 years that this happened to me. My acc was logged in 'BY' 'Vitebsk' during the illicit purchases but I'm based in Asia I gathered all the screenshots and provided in the ticket to steam support. \n\nAll i got was the standard copy paste template reply by Steam Support. Lost $500+ and was not even worthy of having a proper person to look into this. I dont think they even read or take a look at the screenshots cause if they did, they would have come to the realization that what happened was clearly fraud, and with a few clicks, reverse the unauthorized transactions, refund my wallet and ban the hijacker. \n\nOver the years, i've spent quite a fair bit on steam but really, this is the kind of recourse we get when our account is compromised? They just don’t care, sigh. I only expect the bare minimum from Steam and looks like even that is quite far-fetched.\n\nSS: https://imgur.com/a/67frcls \n\nHijacker: https://steamcommunity.com/profiles/76561199141246495\n\nSteam Response: https://imgur.com/a/V6v4maM\n\nI could think of a few ways on how to Improve:\n\n1) Add 2FA to market transactions. (even if its bulk posting or selling of items, just 1 2FA notif is required)\n\n2) Enable accounts to be region locked. (if you are migrating, then have to go through steam support etc)\n\n3) Additional Lock on Steam Wallet. (Another password perhaps?)\n\nEDIT: 2nd ticket in and I have still yet to receive a non robotic copy paste template response from Steam.\n04\nRestoration2021-11-29\nSteam Guard & an item-restoration refusal\n\nA preserved post includes the author’s account of item theft and a support response declining restoration.\n\nREDDIT / PUBLIC TESTIMONYr/DotA2Capture record 58\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 563 words\nMany people are losing item via clicking links where steam guard is enabled and steam support doesn't not restore items.\n\nsteam_support_tickets_MEGA.json / record 58\n\nAccounts are getting compromised and might be their pc as well where Steam market is targeted hence the malicious links . I am assuming these hackers are getting encouraged where steam support is not doing nothing and they are getting away with hacking items.  \nLiterally the guy who is supporting the game which he doesn't get any in game advantage just  cosmetics in game only for the sole purpose of supporting the game so that the game will prosper and become beautiful way  to enjoy weekend. But right now players are getting hacked left right and center and steam support  is copy pasting message where in short they are blaming the guy who clicked link. 1st this is happening because they are not targeting players but they are targeting market since they are selling those stuff for real cash via party website. Steam is a huge company and can eradicate the problem or at least can remove links temporarily  in chat since hackers are targeting .They made us install steam guard by saying we wont help if there is no steam guard now steam guard is not enough to save our inventory now they changed their policy  that they should not click any suspicious links. How would we know if the link is suspicious ? After clicking and getting our inventory stolen right !   \n\"we'd have to duplicate an item to restore it. Duplication lowers the value of all items by reducing their scarcity and inflating the economy, which affects everyone involved in trading and the Market. To maintain the value of everyone’s inventory, we do not restore items. For more information, please see the Steam Item Restoration Policy.\"  \nThey care for millions of people IN STEAM MARKET where as few  are losing items which is going to affect market where the rightful owner bought the items and hacker is going to sell the item via 3rd party website and enjoy ! HOW IRONIC !!  \nThis is the message from support where my frnd got his items stolen via clicking on link  \n   \nHi there,  \n\nThank you for the information and screenshots provided.  \n\nIt appears that the account was compromised, please take the following steps to secure your account and computer:  \n\nScan your computer for viruses, key loggers, spyware, and other malicious code using antivirus software with updated virus definitions.  \nChange the password for the email address that is associated with your Steam account.  \nRegularly reset your Steam account password.  \n\nPlease see our Security Recommendations article.  \n\nIn addition, I’m sorry to hear that your items were removed without your permission. Unfortunately, Steam Support does not restore scammed, lost, or stolen items for any reason.  \n\nSince Steam Support does not remove items from accounts, we'd have to duplicate an item to restore it. Duplication lowers the value of all items by reducing their scarcity and inflating the economy, which affects everyone involved in trading and the Market. To maintain the value of everyone’s inventory, we do not restore items. For more information, please see the Steam Item Restoration Policy.  \n\nTo make sure that a scammer is reported, please report them through the Steam Community. Reporting a scammer through the Steam Community is the best way to prevent them from committing future scams.  \n\nTo learn how to avoid scams or hijackings, please see our Trade Scam article.  \n\nIf you still need assistance, please let us know.\n05\nEnforcement2025-05-11\nSelective enforcement & an unexplained ban\n\nA community member describes a disputed ban and contrasts it with the visibility of commercial gambling promotion.\n\nREDDIT / PUBLIC TESTIMONYr/SteamUncensoredCapture record 107\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 1,208 words\n🚨 Steam Bans Without Reason and Ignores Its Community — What’s Going On?\n\nsteam_support_tickets_MEGA.json / record 107\n\nHey r/Steam,\n\nI’m writing this to share my thoughts and concerns about my friend [moneylead](https://steamcommunity.com/id/moneylead/) and Steam’s policies in general. I spoke with him yesterday about his situation, though I didn’t discuss writing this post with him—I asked last night, but he hasn’t responded yet. I want to highlight that this issue is broader than just his case, and while Steam might make changes in the future (though that’s unlikely), I feel the community needs to understand how far Steam has strayed from its original values. I’m not trying to put moneylead in a tough spot with this thread—all the info I’m sharing is public, nothing secretive. I hope he won’t be upset with me, but the community needs this case to see the bigger picture and how Steam feels completely unaccountable.\n\n**Why Does Steam Ignore Its Community?**  \nWhy does a platform like **Roblox** provide a detailed log of ban reasons, while Steam, which claims to be \"community-driven,\" ignores its community, bans whoever they want, for whatever they want, with no transparency? I looked into Roblox as a popular game—not a direct competitor to Steam—to see how their bans look, and you can check it out yourself: [Roblox Ban Reasons](https://www.google.com/search?q=Roblox+ban). Their bans are clear, detailed, and actually explain what you did wrong. I think most decent gaming communities operate like this—not with support agents named Olga, hired through outsourcing, who only know how to send canned auto-replies. Take cases like St4ck—or my friend **moneylead**. All these unbans, like **St4ck’s** or **Alexanddd’s**, happened behind closed doors with zero comments from Steam. Of course, it’s convenient for Steam to handle everything in secret, so no one knows or sees what’s going on—but this violates Steam’s own community rules and principles.\n\n**Who Is moneylead?**  \nI’ve known [moneylead ](https://steamcommunity.com/id/moneylead/)since around 2021. We played Dota 2 a couple of times, and then I just stayed on his friends list. He’s always been a legit player, bringing revenue to Steam through purchases. He never sold his skins, whether in **Dota or CS2—he wasn’t a trader**. All he did was:\n\n* Buy games and skins.\n* Collect badges to level up his profile.\n\nAccording to [SteamSets](https://steamsets.com/account/76561199080934614), he’s given out 324,000 Steam Points—I think he awarded profile rewards to all his friends in the list (though I’m not 100% sure). I do know he ran contests and gave gifts to friends, always supporting the community.\n\n**Steam’s Unfair Treatment**  \nI’ve seen Steam remove his showcases, avatar, description, and even his country multiple times—just because he’s from **Ukraine**. He has a ton of haters leaving toxic comments on his wall, and Steam seems to favor **Russian** users. Every time he tried to appeal the removal of his showcases or profile description—which didn’t break any rules, just had his Instagram link, and his avatar is the same as it is now—Steam moderators didn’t care. **They don’t care about top players who bring them massive revenue, nor about regular users.**\n\n>*Here’s the worst part: moneylead works in cybersecurity, specifically fighting account theft and phishing. He’s neutralized over 5,000 threats targeting Steam alone. And yet, Steam bans him for \"account hijacking\"?*\n\nIf you roughly calculate moneylead’s contribution to Steam and the community—his profile, level, badges (not skins, you can’t sell those)—is this normal, Steam? Banning people, closing tickets, and ignoring users with a spotless reputation who aren’t involved in any commercial activity, just bringing you profit without taking anything in return?\n\n**Steam’s Double Standards**  \nI’m honestly shocked:\n\n* YouTubers who promote casinos and skin gambling? Steam’s fine with that.\n* A cybersecurity expert who fights scams, doesn’t promote casinos, and openly talks about it on his profile? **Banned with no explanation, ignored, and denied an unban.**\n\nI wonder if Steam deliberately bans a high-level account once a year just because of their impunity—maybe for hype or something. Otherwise, this is just madness. It’s scary to think how many regular players have lost their accounts and skins—not because of scammers, but because of Steam’s desire to ignore, send auto-replies, and do whatever they want.\n\n**How Many Others Are Affected?**  \nHow many others are out there—maybe not as well-known—who just have a few games or skins, get banned for nothing, and receive zero explanation or response? **Is this even legal?** Every other platform provides a detailed log with specific violations, but Steam slaps on the same vague label and sends templated responses.\n\n* How safe is it to buy skins on Steam?\n* What’s the chance Steam will just ban your account for no reason, with no explanation?\n\n**A Message to Valve**  \nI wish moneylead the best in resolving this, but Valve, it’d be great if you remembered what \"community\" means and started following the law. Because right now, it looks like your 30% commission, impunity, and sense of being above the law in the U.S. have given you the idea that you can do whatever you want.\n\nI’m sure there are many others like moneylead and St4ck—people who aren’t public or don’t have the resources to fight back. Let’s unite these cases. **If you’re a U.S. resident who’s been banned by Steam without reason and wants to challenge it, please reach out to me.** I’m finishing my **Juris Doctor (J.D.) program at SMU Dedman School of Law** in Dallas, Texas, and I’m participating in a legal clinical practice under Rule 13 of the Texas Supreme Court.\n\nWhat Steam is doing is absolutely disgusting and illegal, and **I’d be happy to help any gamer (legitimate, with no real violations) who has games or skins with value. This will be beneficial for my practice, and it’s time to put Steam in its place and show them they can’t just dictate their own rules with arbitration**. Let’s take it all the way—not for punishment, but for the sake of the community. Maybe if Steam loses a case, they’ll change their policies and start explaining their actions like most popular gaming communities do. Many of us remember how Steam Support used to recover stolen accounts and ended up “stealing” skins themselves—banning without real reasons is basically the same thing, and that’s a serious accusation.\n\nSo, r/Steam, see you soon. I think you understand what you’re doing and how many people you’ve illegally deprived of their assets. I want to raise this issue—not just for the U.S., but for the entire world. You’ve banned class-action lawsuits? **Welcome to Texas.** I recommend starting to look for licensed attorneys in Texas, because I’d love to discuss your company’s policies, feedback, and support agents named Olga—a name that strongly associates with Russian users. Maybe it’d be easier to move your company to Moscow? But I’d be happy to discuss these critical issues on behalf of the global gaming community.\n\nAlso, I wouldn’t recommend ignoring the lawsuit request that will be sent to your physical address and email address, as the court will proceed without you, and that might upset you—especially since things aren’t going so well for a company with stocks like yours.\n\n**Thanks to everyone who took the time to read this. For those who need real help with an unjust Steam ban without any explanation, I’d be happy to assist. For users from Texas, we can easily file a collective lawsuit against Steam—let’s connect and make it happen.**\n02 / Red de desarrollo «Steam»\nInfraestructuras públicas.Grabado a gran escala.\nDescargar todos los discos de «252» ↓\n\nEl incluido output_steam_network Snapshot registra los repositorios, las relaciones públicas entre colaboradores y bifurcaciones, y los solapamientos de perfiles. Se trata de registros públicos: qué se ha creado, quién ha colaborado y qué se ha bifurcado. El historial documentado de las capacidades públicas es lo que debe tener en cuenta Valve.\n\nRepositorio / descripción\tColaboradores\tForkers\tPerfiles guardados\nalliedmodders/amxmodx\n\nAMX Mod X - Half-Life 1 Scripting and Administration\n\n\t40\t40\t80\nalliedmodders/sourcemod\n\nSourceMod - Source Engine Scripting and Administration\n\n\t40\t40\t80\nDoctorMcKay/node-steam-user\n\nAllows interaction with the Steam network via the Steam client protocol\n\n\t40\t40\t80\nFacepunch/Facepunch.Steamworks\n\nAnother fucking c# Steamworks implementation\n\n\t40\t40\t80\nJustArchiNET/ArchiSteamFarm\n\nC# application with primary purpose of farming Steam cards from multiple accounts simultaneously.\n\n\t40\t40\t80\nodota/core\n\nOpenDota: Open source Dota 2 data platform with automated replay parsing\n\n\t40\t40\t80\nodota/dotaconstants\n\ndotaconstants: Static data for Dota applications\n\n\t40\t40\t80\nodota/web\n\nOpenDota: React web UI for Dota 2 statistics using the OpenDota platform\n\n\t40\t40\t80\nsplewis/get5\n\nCS:GO Sourcemod plugin for competitive matches/scrims\n\n\t40\t40\t80\nSteamDatabase/FileDetectionRuleSets\n\n🔎 Rules to detect game engines and other technologies based on Steam depot file lists\n\n\t40\t40\t80\nSteamRE/SteamKit\n\nSteamKit2 is a .NET library designed to interoperate with Valve's Steam network. It aims to provide a simple, yet extensible, interface to perform various actions on the network.\n\n\t40\t40\t80\nValveSoftware/dxvk\n\ndxvk tree containing branches used by Proton\n\n\t40\t40\t80\nValveSoftware/GameNetworkingSockets\n\nReliable & unreliable messages over UDP. Robust message fragmentation & reassembly. P2P networking / NAT traversal. Encryption.\n\n\t40\t40\t80\nValveSoftware/gamescope\n\nSteamOS session compositing window manager\n\n\t40\t40\t80\nValveSoftware/Proton\n\nCompatibility tool for Steam Play based on Wine and additional components\n\n\t40\t40\t80\nValveSoftware/source-sdk-2013\n\nThe 2013 edition of the Source SDK\n\n\t40\t40\t80\nValveSoftware/wine\n\nWine with a bit of extra spice\n\n\t40\t40\t80\nValveSoftware/steam-devices\n\nList of devices Steam and SteamVR will want read/write permissions on, to help downstream distributions create udev rules/etc\n\n\t39\t40\t79\nValveSoftware/steam-audio\n\nSteam Audio\n\n\t38\t40\t78\nalliedmodders/metamod-source\n\nMetamod:Source - C++ Plugin Environment and Detour Library for the Source Engine\n\n\t37\t40\t77\nalliedmodders/sourcepawn\n\nA small, statically typed scripting language.\n\n\t35\t40\t75\nValveSoftware/Fossilize\n\nA serialization format for various persistent Vulkan object types.\n\n\t31\t40\t71\nrlabrecque/Steamworks.NET\n\nSteamworks wrapper for Unity / C#\n\n\t27\t40\t67\nModDota/moddota.github.io\n\nModDota github pages project.\n\n\t26\t40\t66\nodota/parser\n\nReplay parse server generating JSON log events from Dota 2 replay files\n\n\t26\t40\t66\nValveSoftware/steam-for-linux\n\nIssue tracking for the Steam for Linux beta client\n\n\t26\t40\t66\nSteamRE/DepotDownloader\n\nSteam depot downloader utilizing the SteamKit2 library.\n\n\t24\t40\t64\nJustArchiNET/ASF-ui\n\nThe official web interface for ASF\n\n\t23\t40\t63\nadvancedfx/advancedfx\n\nHalf-Life Advanced Effects (HLAE) is a tool to enrich content creation mainly for the Counter-Strike series.\n\n\t22\t40\t62\nalliedmodders/ambuild\n\nAlliedModders C++ Build System\n\n\t23\t39\t62\nSteamDatabase/BrowserExtension\n\n💻 SteamDB's extension for Steam websites\n\n\t21\t40\t61\nodota/mobile\n\nReact Native apps for viewing Dota 2 data on Android/iOS\n\n\t19\t40\t59\nValvePython/steam\n\n☁️ Python package for interacting with Steam\n\n\t18\t40\t58\nskadistats/clarity\n\nComically fast Dota 2, CSGO, CS2 and Deadlock replay parser written in Java.\n\n\t13\t40\t53\nSteamRE/open-steamworks\n\nOpen Steamworks is a set of reverse engineered headers for the Valve's Steam Client. More or less abandoned now that the Steamworks SDK is publically available.\n\n\t13\t40\t53\nValveSoftware/Source-1-Games\n\nSource 1 based games such as TF2 and Counter-Strike: Source\n\n\t13\t40\t53\nalliedmodders/hl2sdk\n\nHalf-Life 2 SDK Mirrors\n\n\t11\t40\t51\nSteamDatabase/steamdb.info-issues\n\n🚱 Issue tracker for the SteamDB website\n\n\t11\t40\t51\nCSGOFloat/inspect\n\nSource Code that Powers the CSFloat Inspect Link API\n\n\t10\t40\t50\nValveSoftware/SteamOS\n\nSteamOS community tracker\n\n\t10\t40\t50\nalliedmodders/source2mod\n\nExperimental\n\n\t40\t9\t49\nsmiley/steamapi\n\nAn unofficial object-oriented Python library for accessing the Steam Web API.\n\n\t9\t40\t49\nSteamDatabase/GameTracking\n\n🛢 Dumping things, so you don't have to\n\n\t8\t40\t48\nValveSoftware/counter-strike_rules_and_regs\n\nCS:GO\n\n\t7\t40\t47\nValveSoftware/openvr\n\nOpenVR SDK\n\n\t6\t40\t46\nSteamDatabase/easy-markdown-editor\n\nEasyMDE: A simple, beautiful, and embeddable JavaScript Markdown editor. Delightful editing for beginners and experts alike. Features built-in autosaving and spell checking.\n\n\t40\t4\t44\nValveSoftware/Dota-2\n\nTracker for issues specific to Linux and Mac in the Reborn client. If you have a general issue or non-system-specific feature request please go to dev.dota2.com\n\n\t6\t38\t44\nValveSoftware/Dota2-Gameplay\n\nPublic Bug Tracker for Dota 2\n\n\t4\t40\t44\nJustArchiNET/ArchiBot\n\nNo description in the capture.\n\n\t16\t27\t43\nztizzlegaming/CSGOWinBig\n\nOpen-source Counter-Strike: Global Offensive jackpot betting website.\n\n\t1\t40\t41\nJustArchiNET/mantis.justarchi.net\n\nMantis Bug Tracker (MantisBT)\n\n\t40\t0\t40\nodota/node-steam-user\n\nAllows interaction with the Steam network via the Steam client protocol\n\n\t40\t0\t40\nModDota/TypeScriptAddonTemplate\n\nDota 2 addon template with TypeScript Panorama and VScripts.\n\n\t9\t29\t38\nValvePython/vdf\n\n📜 Package for working with Valve's text and binary KeyValue format\n\n\t6\t32\t38\nalliedmodders/amtl\n\nAlliedModders C++ Template Library\n\n\t17\t19\t36\nValvePython/dota2\n\n🐸 Python package for interacting with Dota 2 Game Coordinator\n\n\t5\t30\t35\nalliedmodders/stripper-source\n\nStripper:Source\n\n\t13\t21\t34\nAllyans3/steam-market-api-v2\n\nSteam Market API v2 package\n\n\t3\t31\t34\nModDota/dota-tutorial\n\nCustom game DOTA tutorial.\n\n\t11\t23\t34\nodota/blog\n\nNo description in the capture.\n\n\t29\t3\t32\nOpsecGuy/BetterGo\n\nExternal CS:GO cheat written in python.\n\n\t1\t27\t28\npxvr-official/1\n\n無許諾配信 企業理念剽窃 動物の森収益化 大神ミオ権利者削除 戌神権利侵害発言 常闇トワ炎上 夜空メルストーカー被害 建築王サポーター放置 赤十字マーク 魔乃アロエ卒業 一つの中國支持声明 大空昴3Dライブ 無限延期清掃員職業差別 日清コラボ楽曲 musedash非公開 rog案件取り消し 壁画ライブ 丁真 Ding Zhen 郑爽 Zheng Shuang 防护林 与朵小天使w 伊月猫凛 本主萌埋午休傻 汪峰 重生细胞 壁纸 比利海灵顿 香蕉君 van 田所浩二 抽象带篮子 抗压背锅吧 季子越 蒋明辉 傻逼…\n\n\t0\t28\t28\nRevadike/InternalSteamWebAPI\n\nDocumenting the unofficial and internal Steam Web API\n\n\t1\t27\t28\nJoeSzymkowiczFiveM/qb-lootcrate\n\nA CSGO-style case opening script\n\n\t2\t25\t27\nAbrarKL/MyRoulette.XYZ\n\nCSGO / Steam Roulette Site created with PHP and Node JS, using the Material Design front-end framework.\n\n\t1\t25\t26\nJustArchiNET/ASF-WebConfigGenerator\n\nNo description in the capture.\n\n\t10\t15\t25\nModDota/dota-data\n\nAuto-generated Dota 2 resource dumps\n\n\t11\t14\t25\nModDota/TypeScriptDeclarations\n\nTypeScript declarations for Dota 2.\n\n\t11\t14\t25\nModDota/API\n\nNo description in the capture.\n\n\t12\t12\t24\nalliedmodders/cssdm\n\nCounter-Strike:Source Deathmatch\n\n\t10\t13\t23\nSteamDatabase/steamstat.us\n\n✅ Front-end of Steam services status website\n\n\t4\t18\t22\nc0deina/csgojackpotV2\n\nCSGO Jackpot Source\n\n\t1\t20\t21\nValvePython/steamctl\n\n🤸 Take control of Steam from your terminal\n\n\t2\t19\t21\nValvePython/csgo\n\n🔫 Python package for interacting with CS:GO Game Coordinator\n\n\t3\t17\t20\nBeepIsla/csgo-crash-exploit\n\nAllows you to crash any Windows user\n\n\t3\t16\t19\nValvePython/vpk\n\n📦 Open, Search, Extract and Create VPKs in python\n\n\t4\t15\t19\nalliedmodders/SM-SteamWorks\n\nExposing SteamWorks functions to SourcePawn.\n\n\t14\t3\t17\nSteamRE/Steam4NET\n\nSteam4NET is a .NET wrapper around the Steamworks C++ interfaces\n\n\t2\t15\t17\nalliedmodders/hl2sdk-manifests\n\nInformation about HL2SDKs shared between Metamod:Source and SourceMod.\n\n\t6\t10\t16\nJustArchiNET/ASF-PluginTemplate\n\nTemplate repository that you can use for creating custom plugins for ArchiSteamFarm.\n\n\t8\t7\t15\nModDota/Dota2AIFramework\n\nGeneral Framework for Dota 2 AI Competitions\n\n\t1\t14\t15\nShkyyl/KeyChamp\n\nExtension for joining free case battle on key-drop automatically\n\n\t1\t14\t15\nSteamDatabase/SteamMonitor\n\n😤 Track Steam's connection manager servers status\n\n\t2\t12\t14\nBaterka/cslore.com\n\nCS:GO gambling site - csgo.style\n\n\t1\t12\t13\nSteamDatabase/SteamTokenDumper\n\n🔢 Submit users' PICS access tokens to SteamDB\n\n\t2\t11\t13\nmonoblocker/roulette\n\nRoulette CS:GO made in React and Typescript\n\n\t1\t11\t12\nzsith/launcher.user.js\n\n// ==UserScript== // @name AposLauncher // @namespace AposLauncher // @include http://agar.io/* // @version 3.062 // @grant none // @author http://www.twitch.tv/apostolique // ==/UserScript== var aposLauncherVersion = 3.062; Nu…\n\n\t1\t11\t12\nLincolnIT/CSGODouble-bot-automated\n\nCSGODouble Automated, auto Betting Bot.\n\n\t1\t10\t11\nvladpuz/steam-market\n\nSteam market API client\n\n\t4\t7\t11\nmcgrizzz/Cstrike.bet\n\nCSGO Roulette Website Angular frontend, nodejs backend, and steam trading bots\n\n\t1\t9\t10\nodota/underlords-web\n\nUI for OpenUnderlords\n\n\t5\t5\t10\nSteamDatabase/SteamToTwitter\n\n🕊 Tweets announcements from various Steam groups\n\n\t1\t9\t10\nModDota/AbilityLuaSpellLibrary\n\nThe successor to the Spell Library by Pizzalol\n\n\t4\t4\t8\nalvinl/bitskins\n\nUnofficial BitSkins API client\n\n\t2\t5\t7\nb1naryth1ef/steamy\n\nA Python Steam community and market API interface that will get you all hot and bothered\n\n\t2\t5\t7\nkratos1812/Case-Opening\n\nIn-game case opening system for CSGO servers.\n\n\t2\t5\t7\nodota/docs\n\nOpenDota API documentation\n\n\t4\t3\t7\nSteamDatabase/steam-advanced-access-fetch-players\n\n📈 Simple script to fetch Steam player count\n\n\t1\t6\t7\nTheRioMiner/CsgoBetterExternalRaytrace\n\nOverridden maps pack for better external raytrace\n\n\t1\t6\t7\nalliedmodders/hl2sdk-mock\n\nMock HL2SDK and Server\n\n\t5\t1\t6\nchristophersu/PySteamMarket\n\nPython API for getting prices from the Steam market.\n\n\t1\t5\t6\nExtremelyd1/Strat-Roulette\n\nCS:GO Sourcemod Plugin\n\n\t2\t4\t6\ngiovanni-orciuolo/double-sdk\n\nA simple way to write CS:GO cheats!\n\n\t2\t4\t6\nJustArchiNET/Madness\n\nMadness embraces your project by including compatibility layer for selected APIs normally not available on .NET Framework target.\n\n\t5\t1\t6\nModDota/TypescriptPanoramaDeclarations\n\nNo description in the capture.\n\n\t4\t2\t6\nodota/rapier\n\nA JavaScript Dota 2 (Source 2) replay parsing library\n\n\t1\t5\t6\nVozn1akHero/CSGOCaseOpeningSimulator\n\nCounter-Strike case opening simulator which resembles the good old CS:GO user interface\n\n\t3\t3\t6\nautarc/steam-store\n\nAPI client for the unofficial steam storefront/big picture resource\n\n\t2\t3\t5\nBETTING-CODE/awesome-esports-sites\n\nA curated list of awesome esport betting sites – live, statistics and other resources.\n\n\t1\t4\t5\njonteohr/Better-Warden\n\nAn improved and more advanced warden plugin with a custom menu for CS:GO jailbreak servers!\n\n\t2\t3\t5\nLudzikk/CSGO-Gambling-Site\n\nhttps://ludzikk.github.io/CSGO-Gambling-Site/\n\n\t1\t4\t5\nModDota/find-steam-app\n\nFind location of an installed Steam app\n\n\t3\t2\t5\nmprey/csgocact.us\n\nsource code for csgocact.us\n\n\t1\t4\t5\nnezu-cc/ServerCrasher\n\nCS:GO Server Crasher\n\n\t1\t4\t5\nodota/testfiles\n\nStores test replay files\n\n\t2\t3\t5\nodota/underlordsconstants\n\nConstant data for Dota Underlords\n\n\t3\t2\t5\nSnaBe/node-steam-market-fetcher\n\nA Node.js wrapper for the Steam Community Market API.\n\n\t2\t3\t5\nSteamDatabase/.github\n\n💗 Organization-wide community health files\n\n\t1\t4\t5\nwolfcon/RIP-HLTV-BET\n\nRIP BET AD (For Tampermonkey) https://greasyfork.org/en/scripts/423484-rip-hltv-bet\n\n\t2\t3\t5\nalliedmodders/blaster.net\n\nSource and GoldSrc Query Tool\n\n\t2\t2\t4\ncatears124/CS2-Price-API\n\nsimple python cs2 steam market price API\n\n\t1\t3\t4\nialakey/caseforge\n\nOpen-source CS2 case-opening platform: Steam auth, provably fair openings, RTP-balanced case builder, withdrawals bought on market.csgo.com and an admin CRM.\n\n\t1\t3\t4\nIlusion9/csgo-fix-mapchange-crash-sm\n\nFix players crash on map change.\n\n\t1\t3\t4\nismail0234/Benson-Map-Crash-Fixer\n\nCSGO Map Change Client Crash Fixer\n\n\t1\t3\t4\njaxwilko/steam-market-api\n\nPHP - Composer Compatible - Steam Market API\n\n\t2\t2\t4\nJustArchiNET/ArchiTag\n\nArchiTag is a very small utility based on Python 3 and Mutagen to provide missing functionality in opusenc of writing specific Opus metadata, such as total number of tracks or track number.\n\n\t1\t3\t4\nModDota/DotaUI\n\nNo description in the capture.\n\n\t2\t2\t4\nnode-steam/market-pricing\n\nWrapper for the unofficial Steam Market Pricing API\n\n\t1\t3\t4\nodota/media\n\nStores media files for Dota projects\n\n\t2\t2\t4\nSergeyIvanovDevelop/Crypto-Steam-Platform\n\nThe repository contains the code and configuration to run a platform for creating cryptocurrency stakes for arbitrary ERC20 tokens.\n\n\t1\t3\t4\nAareksio/csgodouble-floatchecker\n\nAdds context menu option to check item's float value\n\n\t1\t2\t3\nchinm4/CSGOdrop\n\nA online csgo gambling casino that includes a variety of mini games that allows you to win csgo skins\n\n\t2\t1\t3\nCruze03/CSGO-Case-Opening-Prank\n\nCommand:- !prank (Admin flag \"n\" required)\n\n\t1\t2\t3\nDhruva-Kapadia/CSGOTrollGG\n\nCSGO Case Opening Simulator\n\n\t2\t1\t3\nErhanCSGO/CSGOPolygon-prediction\n\nCSGOPolygon.com - prediction script, double your coins by using this tool\n\n\t1\t2\t3\nEv-Hoang/Bedrock-Chest-Case-Opening\n\nHypixel Skyblock Dungeon Mod - Bedrock Chest Opening Animation (CSGO Style)\n\n\t1\t2\t3\njmjp/csgo-roulette\n\nA csgo gambling roulette make with VueJS 3\n\n\t2\t1\t3\nJustArchiNET/ArchiCrowdin\n\nNo description in the capture.\n\n\t1\t2\t3\nLeonSK/WearMarketInspector\n\nRetrieve Wear Value (Float Value) and Pattern Index from Steam Community Market using http://csgo.exchange API\n\n\t1\t2\t3\nmaximgeerinck/csgo-gamble\n\nCSGO gambling website\n\n\t1\t2\t3\nModDota/BugTracker\n\nListing bugs for Dota 2 Custom Games\n\n\t2\t1\t3\nplwp/mma-betting\n\nUFC/MMA betting model with Pinnacle steam detection for AU book latency arb\n\n\t2\t1\t3\nSouthsideswag16/Csgo-Gambling-Site\n\nNo description in the capture.\n\n\t2\t1\t3\ntacyarg/csgofiesta-frontend-react\n\nRemastered version a the long time favorite csgo site\n\n\t2\t1\t3\nVelorasse/Mutah-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-csmoney-csgoskins\n\ngambling script for Mutah, Keydrop, csmoney, and csgoskins, featuring hacks, cheats, and predictors. Offers strategies to boost winning odds and optimize performance on these platforms.\n\n\t3\t0\t3\nalliedmodders/am-github-artifact-webhook\n\nNo description in the capture.\n\n\t2\t0\t2\ncharamza/roulette\n\nCSGO like roulette in JS\n\n\t1\t1\t2\nCruze03/CSGO-PugSetup-RoundRestore\n\nSometimes (player dropped/crashed) which would be disadvantage for a team. It would be very handy to restore the match to the previous round.\n\n\t1\t1\t2\ncsgorol/CSGO-ROLL-Crash-Predictor\n\nCSGO-ROLL-Crash-Predictor\n\n\t1\t1\t2\nFoxSerito/FOXWORLD_plugin_DoubleJump_CSGO\n\nПлагин SourceMod (CSGO). Двойной прыжок с эффектом.\n\n\t1\t1\t2\nhkehayovmoonbiz/CS2-Casino-Full-Source-Code\n\nCS2, CS2 betting platforms, Skin Roulette, Case Unboxing, Crash games, Jackpot, purchase CS2 casino source, crypto gambling\n\n\t1\t1\t2\nJustZakary/steamstoreapi\n\nThis NPM module is a API wrapper that makes the steam unofficial API easier to use.\n\n\t2\t0\t2\njzimr/steam-market-api\n\nA java library to easily get Steam Community Market data\n\n\t1\t1\t2\nMomohime/CSGO.Network-Jackpot-Coinflip\n\nNo description in the capture.\n\n\t1\t1\t2\nnnjjswat/moneybot\n\nautomated bots for bustabit (formerly known as moneypot), csgo crash, etc\n\n\t0\t2\t2\nodota/carry\n\nLegacy Application for donations to the OpenDota project\n\n\t1\t1\t2\nodota/PublicMatchDataBot\n\nA Discord bot to remind users to turn on Expose Public Match Data in the Dota 2 client\n\n\t1\t1\t2\nOrillio/CSGOBet.com\n\nCSGO roulette web app\n\n\t2\t0\t2\nripexz/csgo-bet-alert\n\nA Chrome extension to keep track of active CS:GO Lounge matches.\n\n\t1\t1\t2\nrrpvm/lumen_sense-beta-deprecated-\n\nthis is internal csgo cheat written by me(no paste, self reverse structures). start : ~6 August 2020, end : ~ 14 December 2020\n\n\t1\t1\t2\nRuthless222/csgoscore\n\nThis is a Counter Strike Global Offensive Betting Site. You chose the skins you want to bet and try to win jackpots\n\n\t2\t0\t2\ntfburns/CSGO-cases-PL\n\nExpected profit-loss of CS:GO case openings\n\n\t1\t1\t2\nTomDra/CSGO-Case-Data-Analysis\n\nWorks out the most profitable CS:GO case at that current time\n\n\t1\t1\t2\nValvePython/dota2-wrappers\n\nNo description in the capture.\n\n\t1\t1\t2\nValvePython/teamfortress2-closed-captions\n\nThis project aims to provide a set of closed captions for Team Fortress 2\n\n\t1\t1\t2\nVistaNetGTX/Cstrike.bet-\n\nCSGO Roulette Website Angular frontend, nodejs backend, and steam trading bots\n\n\t1\t1\t2\nwafflas/csgo-case-opening-simulator\n\nI created a cs go case opening simulator for a meme coin\n\n\t0\t2\t2\nAdmiral-Enigma/Le_Coinflip\n\nConflip game\n\n\t1\t0\t1\nadryeljuliao/roulette-csgo\n\nNo description in the capture.\n\n\t1\t0\t1\nAndreuTheG/csgo-coinflip-web\n\nCSGO Gambling Coinflip Website\n\n\t1\t0\t1\nasmilen/csgoDouble\n\na b c\n\n\t1\t0\t1\nb1naryth1ef/csgofort\n\nA CSGO portal for trading, betting, analytics, and more!\n\n\t1\t0\t1\nBaterka/PrivateSteamBettingWebsite2024\n\nPrivate Steam (Counter-Strike 2) betting/gambling website - Roulette, Jackpot\n\n\t1\t0\t1\nblackcaer/SteamTradeHandler\n\nAutomation of Steam trading. Helper project for bet automation.\n\n\t1\t0\t1\nBTheCoderr/theRounders\n\nThe Rounders - A professional-grade sports betting analytics platform combining real-time odds tracking, sharp movement detection, and advanced statistical analysis. Features include line shopping, steam move alerts, power rankings, and comprehensive bet t…\n\n\t1\t0\t1\nCallumHemsley/KazeBot\n\nA Twitch chat betting bot for CSGO, simply bet a certain amount of points, and double if you win, lose all if you lose. Simple.\n\n\t1\t0\t1\nchrisjpm/CSGOJackpotTemplate\n\nFront end for a jackpot site\n\n\t1\t0\t1\ncolinsenner/valve-bug-bounty\n\nFor many years CS:GO, Dota 2, and Team Fortress 2 servers had a bug that allowed malicious users to leak crucial server process memory or reliably crash any server.\n\n\t1\t0\t1\ncoryypeters/nrl-odds-intelligence-pipeline\n\nReal-time sports betting odds intelligence — streaming pipeline that detects line movement, steam, and arbitrage across bookmakers. Python · Redis Streams · FastAPI · React.\n\n\t1\t0\t1\ndeissh/dev-csgoduo\n\nCS:GO. Bot for receiving things on the site (Polygon, Duo, Double and etc).\n\n\t1\t0\t1\ndom1torii/even-better-font-manager\n\nSimply even better cross-platform tool for CS2 Font Management\n\n\t1\t0\t1\nDONnicov/CSGO-crash-black-screen-\n\nsolution csgo crash black screen and close csgo\n\n\t1\t0\t1\nDoubleBoters/CsgoDouble\n\nNo description in the capture.\n\n\t1\t0\t1\ndownarowiczd/DoubleBot\n\nAn old CSGO Double Bot written for my friend. - 07.05.2016\n\n\t1\t0\t1\nErayBahar/steammarketscraper\n\nSteam Market Scraper Python-based tool that tracks real-time CS2 skin prices using Steam's hidden API. It fetches the lowest sell and highest buy offers for any item, helping you monitor deals or snipe underpriced listings automatically.\n\n\t1\t0\t1\nfairydarkness/SteamwebmailAPI\n\nUnofficial Python API for steamwebmail.com Fast, lightweight, and browserless library for automating steamwebmail.com. Support for session management, proxy, folder navigation, and message retrieval\n\n\t1\t0\t1\nFAQU2/CSGO-Coinflip-MyJailShop\n\nSourcemod plugin which provides a Coinflip system for MyJailShop.\n\n\t1\t0\t1\nFlamesONE/csgo-case-opening\n\nNo description in the capture.\n\n\t1\t0\t1\nFunnyRain/csgorun-crash-watch\n\n🚀 CsgoRun dump crash. / 🚀 CsgoRun дамп крашей.\n\n\t1\t0\t1\ngeohdgio/Venatus-Autenticator\n\nეს არის Steam Autenticator ქართული Venatus Trade & Betting ისთვის და Valve News Georgia-სთვის.\n\n\t1\t0\t1\nhakanstarlord/steam-bot\n\nSports betting steam-move signal detection with ML pipeline (XGBoost stacking + isotonic calibration), backtesting engine, Flask dashboard, and Telegram alerts.\n\n\t1\t0\t1\nHvH-gg/CSGO-Item-CrashFix\n\nA plugin for Counter-Strike: Global Offensive that fixes an exploit where receiving CS2 Items will cause CS:GO clients to crash\n\n\t1\t0\t1\nHvH-gg/CSGO-NetMsg-CrashFix\n\nA plugin for Counter-Strike: Global Offensive that fixes an exploit where spamming NetMsg_StringCmd packets would result in a server crash.\n\n\t1\t0\t1\nisybycnsmam/SteamLibrary\n\nLegacy Steam Unofficial API\n\n\t1\t0\t1\nItsTangerine/SteamApis.Net\n\nUnofficial https://steamapis.com .NET library, supporting .NET 6.0+\n\n\t1\t0\t1\nJustArchiNET/JustArchi.net\n\nNo description in the capture.\n\n\t1\t0\t1\nkiri-osint/CS2-Info-Hub-Bot\n\nA Telegram bot that acts as a hub for CS2 players, providing real-time skin prices, server stats, and user profile/inventory inspection using official and unofficial Steam APIs.\n\n\t1\t0\t1\nKoshkaj/monte\n\nGamified csgo gambling platform implementation\n\n\t1\t0\t1\nmadsab/CaseOpening\n\nA school project using Java. Simulating the case opening from CSGO and more.\n\n\t1\t0\t1\nman90es/steamcardexchange-api\n\nSteamCardExchange.net unofficial REST API server (scraper).\n\n\t1\t0\t1\nMattPua/steam-unofficial-docs\n\nUnofficial docs for Steam APIs with fumadocs\n\n\t1\t0\t1\nMetallist1/Portfolio.CsgoWinGambleProject\n\nA website that was done in 2017 September. Websites focus was on gambling with Counter-Strike items. Project was largely completed however backups were not done correctly, this resulted in half a year of wasted improvements to the code. The website was test…\n\n\t1\t0\t1\nmikebobadilla/csgo-jackpot\n\nNo description in the capture.\n\n\t0\t1\t1\nmikebobadilla/meteor-csgojackpot\n\nCssgo Jackpot done in meteor\n\n\t1\t0\t1\nModDota/D2VDump\n\nDota 2 Server VScript API Dumper\n\n\t1\t0\t1\nModDota/DotaTracking\n\nNo description in the capture.\n\n\t1\t0\t1\nModDota/eslint-config\n\nESLint config by ark120202\n\n\t1\t0\t1\nmr-codinglv/Casino-script\n\nscript casino - script betting - exchange script - bc casino - casino csgo - script bet - betwin script\n\n\t1\t0\t1\nMrKeelik/MrKeel\n\nCSGO DOUBLE BOT\n\n\t1\t0\t1\nnoahlatzel/CSGORollHelper\n\nLeveraging positive expected value on triple green jackpots on CSGORoll!\n\n\t1\t0\t1\noddsgpt/oddsgpt-market-intelligence\n\nResearch on football betting markets, closing odds, CLV, market efficiency, steam moves, AI betting systems, and sports market intelligence.\n\n\t1\t0\t1\noEXU/csgo-server-crasher\n\nCSGO SERVER CRASHER\n\n\t1\t0\t1\nPrdTTony/CSGO-Roulette\n\n[CSGO] Roulette System. Bet on RED or Black and win x2 credits\n\n\t1\t0\t1\nr-adamski/csgo-jackpot\n\nNo description in the capture.\n\n\t1\t0\t1\nSahotallo/Turan-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-Skinbaron-hellcase\n\ngambling script for Turan, Keydrop, Skinbaron, and Hellcase, providing hacks, cheats, and predictors. Includes strategies to improve winning chances and enhance gameplay on these platforms.\n\n\t1\t0\t1\nsamuelcsouza/steam-marketplace-api\n\nAn unofficial API to get data from the Steam Marketplace.\n\n\t1\t0\t1\nSKINSTRACK/CS2-Price-API\n\nSkinstrack offers a free, limited API endpoint that returns Steam item prices. Paid plans additionally provide access to pricing data from multiple marketplaces, making it possible to compare prices across different markets through a single API.\n\n\t1\t0\t1\nsnmtriet/CSGO-Casino-Full-Source-Code\n\nCSGO, CSGOEmpire, Case Opening, Case Battles, Roulette, Coinflip, buy csgo gambling site, gambling\n\n\t1\t0\t1\nSteamRE/homebrew-tools\n\nRepository for installation of SteamRE tools via Homebrew (http://brew.sh)\n\n\t1\t0\t1\nSteamRE/opensteamworks.org\n\nNo description in the capture.\n\n\t1\t0\t1\nTheQuack45/CsgoCaseOpenProgram\n\nSimple program to parse an XML file with CS:GO case information and \"simulate\" case openings\n\n\t1\t0\t1\nTLClassless/StratRouletteCSGO\n\nA 'Strat Roulette' web app for CS:GO!\n\n\t1\t0\t1\ntomasoom/csgoCaseOpening\n\nNo description in the capture.\n\n\t1\t0\t1\nvitaliy-evsyukov/steamgifts-autobet-bookmarklet\n\nbookmarklet for automatic bets on steamgifts.com\n\n\t1\t0\t1\nXpravdaX/RouletteCSGO\n\nNo description in the capture.\n\n\t1\t0\t1\nYuiKasumii/steam_api_unofficial\n\nUnofficial Steam Game Information Database\n\n\t1\t0\t1\nZexuz/Steam-Betting\n\nA betting website build ontop of STEAM's ecosystem\n\n\t1\t0\t1\nANK-RULZZ/steam-jackpot-site\n\ngetting some errors and would like some one to help me with it thank you!!!\n\n\t0\t0\t0\nasmilen/CsgoDoubleVS\n\nNo description in the capture.\n\n\t0\t0\t0\nCORNOODOSADAS/CSGOWeed\n\nCsgo Jackpot and Coinflip\n\n\t0\t0\t0\nCSGOApple/csgoapple\n\nJackpot Site\n\n\t0\t0\t0\nCSGOFAST/csgofast-api\n\nNo description in the capture.\n\n\t0\t0\t0\nDonakall/csgoDoublebot\n\nAutomated bot for csgodouble\n\n\t0\t0\t0\nfedor-selivanov/csgo-fast-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nfoldageros/csgod\n\ndouble bot\n\n\t0\t0\t0\ngmod-gambling/gmod-gambling\n\nNo description in the capture.\n\n\t0\t0\t0\nierome/CSGOBoss-BackEnd\n\nBack end version of CSGOBoss. This was a CSGO Gambling site named CSGOBoss. Coded by an old friend of mine Dahquan Hinds (https://github.com/dahquan/) Thought I would release this to help out any one who would need it.\n\n\t0\t0\t0\njamienp1/CSGODOUBLE-BOT-AUTO\n\ni got a bot thats is betting on the last winning color except from green and if you lose it will double the coins you set it to bet, pretty good, so when there comes a loooong train you will be gaining a bit of money codepaste_net/ugmt92 remove all the _ an…\n\n\t0\t0\t0\nJEYONER/CSGOTOXIC\n\nPAGINA DE JACKPOT CSGO SKINS\n\n\t0\t0\t0\nkalrish/csgo-jackpot\n\nStressful but funny zombie-like Counter-Strike: Global Offensive game mode.\n\n\t0\t0\t0\nkrys12345/roulettee\n\n// ==UserScript== // @name CSGO Predict Bot // @namespace http://csgodouble.com // @version 1.0 // @description predicts what number its gonna be // @author Meee // @match http://www.csgodouble.com/ // @grant none // ==/…\n\n\t0\t0\t0\nLilDuggiMuffi/CSGODouble-Working-Bot\n\nFixed CSGO Double Bot\n\n\t0\t0\t0\nLyricLy/Steam2Proton\n\nCheck if all your Steam games will work with Proton! Uses the official Steam API and the unofficial Proton API.\n\n\t0\t0\t0\nM0NsTeR77/csgo-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nozanhalis/Hi\n\n// ==UserScript== // @name CS GO LOUNGE BOT-Ozan Halis // @namespace http://csgolounge.com/ // @version 0.6.6 // @description Cs Go Lounge Hızlı BOT // @match http://csgolounge.com/* // @match http://dota2lounge.com/* // @updateURL h…\n\n\t0\t0\t0\nscoobertus/CSGO-DoubleBot\n\nNo description in the capture.\n\n\t0\t0\t0\nTradeal/CSGO-Jackpot-Bot\n\nNo description in the capture.\n\n\t0\t0\t0\nValvePython/artifact\n\nNo description in the capture.\n\n\t0\t0\t0\nVampire/CSGO-Roulette-Bot\n\nNo description in the capture.\n\n\t0\t0\t0\nvdemans/csgo-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nVocoreVideo/CSGODungeon-\n\nCSGO Jackpot\n\n\t0\t0\t0\nwayz-dev/csgofloat\n\nNo description in the capture.\n\n\t0\t0\t0\n\nResumen: 17 septiembre 2026, 11:19:11 tal y como figura en la fuente; zona horaria sin especificar. La recopilación de relaciones está limitada en la exportación (muchas categorías se detienen en 40). Los colaboradores y los que han creado bifurcaciones suman 4,554 entradas de rol en 4,214 pares distintos de perfil-repositorio; un perfil puede tener ambos roles. El valor cero significa que no se han registrado datos en esa categoría. Los nombres de los repositorios pueden incluir alias o variantes de mayúsculas y minúsculas; los totales se ajustan a las convenciones de recuento de la fuente.\n\nProcedencia de la fuente\nCreado a partir de los archivos que has recopilado.\nTestimonio de apoyo\n2323/reddit_scams_ultra/steam_support_tickets_MEGA.json · filas 45, 58, 107, 110, 294\nInstantánea de la red\nnetwork-repositories.csv · raw_data.json · overlaps.csv · summary.txt (las rutas de origen históricas se conservan en el manifiesto)\n\nEl manifiesto recoge las rutas de origen, los tamaños en bytes, los hash SHA-256 y las posiciones de los registros seleccionados. Las capturas sin procesar se mantienen separadas de la interpretación de la investigación.\n\nDescargar el manifiesto de origen ↓",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam Pruebas de cumplimiento: registros de apoyo y red de desarrolladores"
          },
          {
            "level": 2,
            "id": null,
            "text": "Lee la denuncia.Adjunta el archivo original."
          },
          {
            "level": 3,
            "id": null,
            "text": "Permanent sanction & closed appeals"
          },
          {
            "level": 4,
            "id": null,
            "text": "Permanently banned Steam account without a clear explanation, need help!"
          },
          {
            "level": 3,
            "id": null,
            "text": "Account recovery & a reported $10,000 loss"
          },
          {
            "level": 4,
            "id": null,
            "text": "Got $10k stollen from steam inventory due to steam' support fault."
          },
          {
            "level": 3,
            "id": null,
            "text": "A reported $500+ loss & template replies"
          },
          {
            "level": 4,
            "id": null,
            "text": "Funds stolen through steam market. Disappointed with Steam response.(or lackthereof)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam Guard & an item-restoration refusal"
          },
          {
            "level": 4,
            "id": null,
            "text": "Many people are losing item via clicking links where steam guard is enabled and steam support doesn't not restore items."
          },
          {
            "level": 3,
            "id": null,
            "text": "Selective enforcement & an unexplained ban"
          },
          {
            "level": 4,
            "id": null,
            "text": "🚨 Steam Bans Without Reason and Ignores Its Community — What’s Going On?"
          },
          {
            "level": 2,
            "id": null,
            "text": "Infraestructuras públicas.Grabado a gran escala."
          },
          {
            "level": 2,
            "id": null,
            "text": "Creado a partir de los archivos que has recopilado."
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/es/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/es/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/selected-support-records.json",
          "https://phishdestroy.io/steam_dossier/es/investigation_part2.html#outsourcing-case",
          "https://www.reddit.com/r/ohnePixel/comments/1hahqx2/permanently_banned_steam_account_without_a_clear/",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://www.reddit.com/r/DotA2/comments/r55bd7/many_people_are_losing_item_via_clicking_links/",
          "https://www.reddit.com/r/SteamUncensored/comments/1kjt2fa/steam_bans_without_reason_and_ignores_its/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/network-repositories.csv",
          "https://github.com/alliedmodders/amxmodx",
          "https://github.com/alliedmodders/sourcemod",
          "https://github.com/DoctorMcKay/node-steam-user",
          "https://github.com/Facepunch/Facepunch.Steamworks",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://github.com/odota/core",
          "https://github.com/odota/dotaconstants",
          "https://github.com/odota/web",
          "https://github.com/splewis/get5",
          "https://github.com/SteamDatabase/FileDetectionRuleSets",
          "https://github.com/SteamRE/SteamKit",
          "https://github.com/ValveSoftware/dxvk",
          "https://github.com/ValveSoftware/GameNetworkingSockets",
          "https://github.com/ValveSoftware/gamescope",
          "https://github.com/ValveSoftware/Proton",
          "https://github.com/ValveSoftware/source-sdk-2013",
          "https://github.com/ValveSoftware/wine",
          "https://github.com/ValveSoftware/steam-devices",
          "https://github.com/ValveSoftware/steam-audio",
          "https://github.com/alliedmodders/metamod-source",
          "https://github.com/alliedmodders/sourcepawn",
          "https://github.com/ValveSoftware/Fossilize",
          "https://github.com/rlabrecque/Steamworks.NET",
          "https://github.com/ModDota/moddota.github.io",
          "https://github.com/odota/parser",
          "https://github.com/ValveSoftware/steam-for-linux",
          "https://github.com/SteamRE/DepotDownloader",
          "https://github.com/JustArchiNET/ASF-ui",
          "https://github.com/advancedfx/advancedfx",
          "https://github.com/alliedmodders/ambuild",
          "https://github.com/SteamDatabase/BrowserExtension",
          "https://github.com/odota/mobile",
          "https://github.com/ValvePython/steam",
          "https://github.com/skadistats/clarity",
          "https://github.com/SteamRE/open-steamworks",
          "https://github.com/ValveSoftware/Source-1-Games",
          "https://github.com/alliedmodders/hl2sdk",
          "https://github.com/SteamDatabase/steamdb.info-issues",
          "https://github.com/CSGOFloat/inspect",
          "https://github.com/ValveSoftware/SteamOS",
          "https://github.com/alliedmodders/source2mod",
          "https://github.com/smiley/steamapi",
          "https://github.com/SteamDatabase/GameTracking",
          "https://github.com/ValveSoftware/counter-strike_rules_and_regs",
          "https://github.com/ValveSoftware/openvr",
          "https://github.com/SteamDatabase/easy-markdown-editor",
          "https://github.com/ValveSoftware/Dota-2",
          "https://github.com/ValveSoftware/Dota2-Gameplay",
          "https://github.com/JustArchiNET/ArchiBot",
          "https://github.com/ztizzlegaming/CSGOWinBig",
          "https://github.com/JustArchiNET/mantis.justarchi.net",
          "https://github.com/odota/node-steam-user",
          "https://github.com/ModDota/TypeScriptAddonTemplate",
          "https://github.com/ValvePython/vdf",
          "https://github.com/alliedmodders/amtl",
          "https://github.com/ValvePython/dota2",
          "https://github.com/alliedmodders/stripper-source",
          "https://github.com/Allyans3/steam-market-api-v2",
          "https://github.com/ModDota/dota-tutorial",
          "https://github.com/odota/blog",
          "https://github.com/OpsecGuy/BetterGo",
          "https://github.com/pxvr-official/1",
          "https://github.com/Revadike/InternalSteamWebAPI",
          "https://github.com/JoeSzymkowiczFiveM/qb-lootcrate",
          "https://github.com/AbrarKL/MyRoulette.XYZ",
          "https://github.com/JustArchiNET/ASF-WebConfigGenerator",
          "https://github.com/ModDota/dota-data",
          "https://github.com/ModDota/TypeScriptDeclarations",
          "https://github.com/ModDota/API",
          "https://github.com/alliedmodders/cssdm",
          "https://github.com/SteamDatabase/steamstat.us",
          "https://github.com/c0deina/csgojackpotV2",
          "https://github.com/ValvePython/steamctl",
          "https://github.com/ValvePython/csgo",
          "https://github.com/BeepIsla/csgo-crash-exploit",
          "https://github.com/ValvePython/vpk",
          "https://github.com/alliedmodders/SM-SteamWorks",
          "https://github.com/SteamRE/Steam4NET",
          "https://github.com/alliedmodders/hl2sdk-manifests",
          "https://github.com/JustArchiNET/ASF-PluginTemplate",
          "https://github.com/ModDota/Dota2AIFramework",
          "https://github.com/Shkyyl/KeyChamp",
          "https://github.com/SteamDatabase/SteamMonitor",
          "https://github.com/Baterka/cslore.com",
          "https://github.com/SteamDatabase/SteamTokenDumper",
          "https://github.com/monoblocker/roulette",
          "https://github.com/zsith/launcher.user.js",
          "https://github.com/LincolnIT/CSGODouble-bot-automated",
          "https://github.com/vladpuz/steam-market",
          "https://github.com/mcgrizzz/Cstrike.bet",
          "https://github.com/odota/underlords-web",
          "https://github.com/SteamDatabase/SteamToTwitter",
          "https://github.com/ModDota/AbilityLuaSpellLibrary",
          "https://github.com/alvinl/bitskins",
          "https://github.com/b1naryth1ef/steamy",
          "https://github.com/kratos1812/Case-Opening",
          "https://github.com/odota/docs",
          "https://github.com/SteamDatabase/steam-advanced-access-fetch-players",
          "https://github.com/TheRioMiner/CsgoBetterExternalRaytrace",
          "https://github.com/alliedmodders/hl2sdk-mock",
          "https://github.com/christophersu/PySteamMarket",
          "https://github.com/Extremelyd1/Strat-Roulette",
          "https://github.com/giovanni-orciuolo/double-sdk",
          "https://github.com/JustArchiNET/Madness",
          "https://github.com/ModDota/TypescriptPanoramaDeclarations",
          "https://github.com/odota/rapier",
          "https://github.com/Vozn1akHero/CSGOCaseOpeningSimulator",
          "https://github.com/autarc/steam-store",
          "https://github.com/BETTING-CODE/awesome-esports-sites",
          "https://github.com/jonteohr/Better-Warden",
          "https://github.com/Ludzikk/CSGO-Gambling-Site",
          "https://github.com/ModDota/find-steam-app",
          "https://github.com/mprey/csgocact.us",
          "https://github.com/nezu-cc/ServerCrasher",
          "https://github.com/odota/testfiles",
          "https://github.com/odota/underlordsconstants",
          "https://github.com/SnaBe/node-steam-market-fetcher",
          "https://github.com/SteamDatabase/.github",
          "https://github.com/wolfcon/RIP-HLTV-BET",
          "https://github.com/alliedmodders/blaster.net",
          "https://github.com/catears124/CS2-Price-API",
          "https://github.com/ialakey/caseforge",
          "https://github.com/Ilusion9/csgo-fix-mapchange-crash-sm",
          "https://github.com/ismail0234/Benson-Map-Crash-Fixer",
          "https://github.com/jaxwilko/steam-market-api",
          "https://github.com/JustArchiNET/ArchiTag",
          "https://github.com/ModDota/DotaUI",
          "https://github.com/node-steam/market-pricing",
          "https://github.com/odota/media",
          "https://github.com/SergeyIvanovDevelop/Crypto-Steam-Platform",
          "https://github.com/Aareksio/csgodouble-floatchecker",
          "https://github.com/chinm4/CSGOdrop",
          "https://github.com/Cruze03/CSGO-Case-Opening-Prank",
          "https://github.com/Dhruva-Kapadia/CSGOTrollGG",
          "https://github.com/ErhanCSGO/CSGOPolygon-prediction",
          "https://github.com/Ev-Hoang/Bedrock-Chest-Case-Opening",
          "https://github.com/jmjp/csgo-roulette",
          "https://github.com/JustArchiNET/ArchiCrowdin",
          "https://github.com/LeonSK/WearMarketInspector",
          "https://github.com/maximgeerinck/csgo-gamble",
          "https://github.com/ModDota/BugTracker",
          "https://github.com/plwp/mma-betting",
          "https://github.com/Southsideswag16/Csgo-Gambling-Site",
          "https://github.com/tacyarg/csgofiesta-frontend-react",
          "https://github.com/Velorasse/Mutah-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-csmoney-csgoskins",
          "https://github.com/alliedmodders/am-github-artifact-webhook",
          "https://github.com/charamza/roulette",
          "https://github.com/Cruze03/CSGO-PugSetup-RoundRestore",
          "https://github.com/csgorol/CSGO-ROLL-Crash-Predictor",
          "https://github.com/FoxSerito/FOXWORLD_plugin_DoubleJump_CSGO",
          "https://github.com/hkehayovmoonbiz/CS2-Casino-Full-Source-Code",
          "https://github.com/JustZakary/steamstoreapi",
          "https://github.com/jzimr/steam-market-api",
          "https://github.com/Momohime/CSGO.Network-Jackpot-Coinflip",
          "https://github.com/nnjjswat/moneybot",
          "https://github.com/odota/carry",
          "https://github.com/odota/PublicMatchDataBot",
          "https://github.com/Orillio/CSGOBet.com",
          "https://github.com/ripexz/csgo-bet-alert",
          "https://github.com/rrpvm/lumen_sense-beta-deprecated-",
          "https://github.com/Ruthless222/csgoscore",
          "https://github.com/tfburns/CSGO-cases-PL",
          "https://github.com/TomDra/CSGO-Case-Data-Analysis",
          "https://github.com/ValvePython/dota2-wrappers",
          "https://github.com/ValvePython/teamfortress2-closed-captions",
          "https://github.com/VistaNetGTX/Cstrike.bet-",
          "https://github.com/wafflas/csgo-case-opening-simulator",
          "https://github.com/Admiral-Enigma/Le_Coinflip",
          "https://github.com/adryeljuliao/roulette-csgo",
          "https://github.com/AndreuTheG/csgo-coinflip-web",
          "https://github.com/asmilen/csgoDouble",
          "https://github.com/b1naryth1ef/csgofort",
          "https://github.com/Baterka/PrivateSteamBettingWebsite2024",
          "https://github.com/blackcaer/SteamTradeHandler",
          "https://github.com/BTheCoderr/theRounders",
          "https://github.com/CallumHemsley/KazeBot",
          "https://github.com/chrisjpm/CSGOJackpotTemplate",
          "https://github.com/colinsenner/valve-bug-bounty",
          "https://github.com/coryypeters/nrl-odds-intelligence-pipeline",
          "https://github.com/deissh/dev-csgoduo",
          "https://github.com/dom1torii/even-better-font-manager",
          "https://github.com/DONnicov/CSGO-crash-black-screen-",
          "https://github.com/DoubleBoters/CsgoDouble",
          "https://github.com/downarowiczd/DoubleBot",
          "https://github.com/ErayBahar/steammarketscraper",
          "https://github.com/fairydarkness/SteamwebmailAPI",
          "https://github.com/FAQU2/CSGO-Coinflip-MyJailShop",
          "https://github.com/FlamesONE/csgo-case-opening",
          "https://github.com/FunnyRain/csgorun-crash-watch",
          "https://github.com/geohdgio/Venatus-Autenticator",
          "https://github.com/hakanstarlord/steam-bot",
          "https://github.com/HvH-gg/CSGO-Item-CrashFix",
          "https://github.com/HvH-gg/CSGO-NetMsg-CrashFix",
          "https://github.com/isybycnsmam/SteamLibrary",
          "https://github.com/ItsTangerine/SteamApis.Net",
          "https://github.com/JustArchiNET/JustArchi.net",
          "https://github.com/kiri-osint/CS2-Info-Hub-Bot",
          "https://github.com/Koshkaj/monte",
          "https://github.com/madsab/CaseOpening",
          "https://github.com/man90es/steamcardexchange-api",
          "https://github.com/MattPua/steam-unofficial-docs",
          "https://github.com/Metallist1/Portfolio.CsgoWinGambleProject",
          "https://github.com/mikebobadilla/csgo-jackpot",
          "https://github.com/mikebobadilla/meteor-csgojackpot",
          "https://github.com/ModDota/D2VDump",
          "https://github.com/ModDota/DotaTracking",
          "https://github.com/ModDota/eslint-config",
          "https://github.com/mr-codinglv/Casino-script",
          "https://github.com/MrKeelik/MrKeel",
          "https://github.com/noahlatzel/CSGORollHelper",
          "https://github.com/oddsgpt/oddsgpt-market-intelligence",
          "https://github.com/oEXU/csgo-server-crasher",
          "https://github.com/PrdTTony/CSGO-Roulette",
          "https://github.com/r-adamski/csgo-jackpot",
          "https://github.com/Sahotallo/Turan-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-Skinbaron-hellcase",
          "https://github.com/samuelcsouza/steam-marketplace-api",
          "https://github.com/SKINSTRACK/CS2-Price-API",
          "https://github.com/snmtriet/CSGO-Casino-Full-Source-Code",
          "https://github.com/SteamRE/homebrew-tools",
          "https://github.com/SteamRE/opensteamworks.org",
          "https://github.com/TheQuack45/CsgoCaseOpenProgram",
          "https://github.com/TLClassless/StratRouletteCSGO",
          "https://github.com/tomasoom/csgoCaseOpening",
          "https://github.com/vitaliy-evsyukov/steamgifts-autobet-bookmarklet",
          "https://github.com/XpravdaX/RouletteCSGO",
          "https://github.com/YuiKasumii/steam_api_unofficial",
          "https://github.com/Zexuz/Steam-Betting",
          "https://github.com/ANK-RULZZ/steam-jackpot-site",
          "https://github.com/asmilen/CsgoDoubleVS",
          "https://github.com/CORNOODOSADAS/CSGOWeed",
          "https://github.com/CSGOApple/csgoapple",
          "https://github.com/CSGOFAST/csgofast-api",
          "https://github.com/Donakall/csgoDoublebot",
          "https://github.com/fedor-selivanov/csgo-fast-roulette",
          "https://github.com/foldageros/csgod",
          "https://github.com/gmod-gambling/gmod-gambling",
          "https://github.com/ierome/CSGOBoss-BackEnd",
          "https://github.com/jamienp1/CSGODOUBLE-BOT-AUTO",
          "https://github.com/JEYONER/CSGOTOXIC",
          "https://github.com/kalrish/csgo-jackpot",
          "https://github.com/krys12345/roulettee",
          "https://github.com/LilDuggiMuffi/CSGODouble-Working-Bot",
          "https://github.com/LyricLy/Steam2Proton",
          "https://github.com/M0NsTeR77/csgo-roulette",
          "https://github.com/ozanhalis/Hi",
          "https://github.com/scoobertus/CSGO-DoubleBot",
          "https://github.com/Tradeal/CSGO-Jackpot-Bot",
          "https://github.com/ValvePython/artifact",
          "https://github.com/Vampire/CSGO-Roulette-Bot",
          "https://github.com/vdemans/csgo-roulette",
          "https://github.com/VocoreVideo/CSGODungeon-",
          "https://github.com/wayz-dev/csgofloat",
          "https://phishdestroy.io/steam_dossier/output_steam_network/raw_data.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/enforcement-source-manifest.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/es/steam_enforcement_evidence.content.json",
      "export_json_sha256": "d63f13f15ae9573f18d1fb13326f70e0946db073893ba172565b40be969b83eb"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "es/steam_evidence_archive.html",
      "language": "es",
      "title": "Analiza las fuentes: el informe «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/es/steam_evidence_archive",
      "source_html_sha256": "13948e1d3a6613e8b91d1c543204af4f0d2824fea4d379a192fd55fc2de5b35a",
      "exported_at": "2026-09-29T00:17:29.065Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "steam_evidence_archive.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/es/steam_evidence_archive.pdf?v=print-20260929-v5",
        "sha256": "2bfa44a67aa0fc84ca3e53bfa941a59df09f326ff3e6e782f032b2348eab5859",
        "bytes": 63346,
        "pages": 4
      },
      "integrity": {
        "signed_object": "steam_evidence_archive.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "steam_evidence_archive.content.json.asc",
        "digest_file": "steam_evidence_archive.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify steam_evidence_archive.content.json.asc steam_evidence_archive.content.json",
          "sha256sum -c steam_evidence_archive.content.json.sha256"
        ]
      },
      "content": {
        "text": "MATERIALES DE INVESTIGACIÓN / RECOPILACIÓN DE FUENTES 002\nSteam Archivo de pruebas — Documentos procedentes de «16,319»\n\nTodas las reclamaciones. De vuelta al origen.\n\nLO QUE DEMUESTRA ESTA SECCIÓN\n\nEste archivo forense indexa 16,319 registros de fuentes primarias —que abarcan documentación de la comunidad de desarrolladores de Valve, incidencias públicas de GitHub, reclamaciones verificadas en Trustpilot e informes archivados de foros— mediante hash criptográficos y registros de procedencia. Proporciona una base de pruebas verificable que demuestra vulnerabilidades repetibles de la plataforma, funciones obsoletas no documentadas de API y reclamaciones persistentes de los consumidores relativas a cuentas suplantadas.\n\n← Volver al informe ejecutivo\n\nBusca el registro en el que se basa una afirmación. Filtra por fuente, abre el texto completo y sigue el enlace original. Las entradas de las fuentes pueden solaparse; un registro no equivale a un incidente verificado.\n\nVolver a la investigación ↗\n354TRUSTPILOT / FILAS DE ORIGEN\n208REDDIT / FILAS DE ORIGEN\n705GITHUB / LÍNEAS DE CÓDIGO\n15,302MASTER CSV / FILAS DE ORIGEN\n16,319 REGISTROS — DESGLOSE POR TIPO DE PLATAFORMA\n\nCategoría de la wiki «procedencia» (registros de 7,620 · 46.7%): Datos extraídos de la comunidad de desarrolladores deValve (developer.valvesoftware.com), la documentación y las preguntas frecuentes de SteamDB, y las wikis de la comunidad de videojuegos (Liquipedia CS/Dota y las wikis de Fandom Steam) mediante instantáneas automatizadas de WARC y puntos de acceso de MediaWiki API entre el 2024 de agosto y el 2026. de septiembre. Todas las entradas de 7,620 están totalmente integradas en la exportación CSV maestra (TOTAL_VALVE_SCANDALS_MASTER_DB.csv).\n\nWiki\n7,620\nReddit\n5,635\nGitHub\n2,395\nTrustpilot\n393\nWeb\n276\n9,116 de los registros de 16,319 (55.8%) contienen referencias a Steam / Valve\n\nEste archivo con función de búsqueda se creó a partir de 2026-09-17 de las exportaciones de origen enumeradas anteriormente. La exportación maestra de filas independiente de «40,448-», utilizada en otras partes del expediente, tiene un ámbito diferente. Véase el crear un manifiesto en las cifras de este archivo; los registros pueden solaparse y no corresponden a incidentes únicos.\n\nPLATAFORMA DE ORIGEN\nRECOPILACIÓN DE FUENTES\nSteam / Valve menciones\nCoincidencia de texto o repositorio «Valve»Texto que falta o se ha eliminado\n16,569 filas de origen\n16,319 registros distintos\n249 Se han fusionado las filas duplicadas\n1 fila excluida\nVer los archivos originales ↘\n★TRUSTPILOT2015-10-16#1RATING 1/5\n\nSteam is the biggest PC gaming platform without a doubt. A power which could be abused but Steam for the most part doesn't. Overall a definite download for any moden digital age PC gamer. It mu... See more\n\nMA · 7 source copies\n★TRUSTPILOT2021-06-18#2RATING 1/5\n\nThey scam people for money, dont believe me? Read this Source: Steam Subscribers/User Agreement NO GUARANTEES TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, NEITHER VALVE NOR ITS AFFILIA... See more\n\nWF · 7 source copies\n★TRUSTPILOT2016-10-28#3RATING 1/5\n\nSupport on site is terrible. Refunds not happend yet, despite games not working. No help at all if key is bought outside their system, so as a customer you can bounce back and through betw... See more\n\nPE · 7 source copies\n★TRUSTPILOT2021-09-27#4RATING 1/5\n\nThey are an amazing company!! My boyfriend paid for and downloaded a game without realizing it wasn’t the version he wanted. When he reached out, they gave him a full refund and responded in the same... See more\n\nVH · 7 source copies\n★TRUSTPILOT2026-07-20#5RATING 1/5\n\nI’ve used Steam for years, but lately, their sales have really lost their edge. I was hoping to score some solid discounts, but many games still feel overpriced, even during sales. Plus, the support response times can be frustratingly slow when issues arise.\n\nCR\n★TRUSTPILOT2025-12-10#6RATING 1/5\n\nI new here , but all my firends had great experience with this platform . They can make money\n\nZeinab Nematollahi\n★TRUSTPILOT2025-11-18#7RATING 1/5TEXT UNAVAILABLE\n\nNo text was included in the source record.\n\nEM\n★TRUSTPILOT2025-10-21#8RATING 1/5\n\nusing steam for over a decade and i have no words how good the platform is. some friends recommended it to me back in 2015 when we wanted to play csgo together and since then im loggin on it on a daily basis to check new games\n\nTrustpilot\n★TRUSTPILOT2025-05-09#9RATING 1/5\n\nSupport are never able to help you and only able to redicrect you to public linkBreaking there own TOSNot able to provider a refundNot able to provide a safe place for gamingBase on the game you play you can get scam.\n\nSym Link · 7 source copies\n★TRUSTPILOT2025-05-09#10RATING 1/5TEXT UNAVAILABLE\n\nNo text was included in the source record.\n\nHearnius\n★TRUSTPILOT2024-12-30#11RATING 1/5\n\nThis company allowed a single phishing scammer 76561199443342045 in 100's of its user community chat rooms \"Steam Chat\" the whole week of Winter Sales, 12-23-2024 - 2025 to spam spaceintrader a scam phishing website.Don't support Valve & Steam that support sca…\n\nFR · 7 source copies\n★TRUSTPILOT2024-11-15#12RATING 1/5\n\nVery realiable! Ive never had an issue over the 11 years ive had steam.\n\nJM\nLa compilación y sus archivos fuente\n\nEste archivo fusiona 249 las entradas duplicadas y excluye una entrada de 16,569, lo que deja 16,319 registros distintos. Un registro puede describir un evento que ya figure en otro registro. La búsqueda abarca títulos, autores, sellos discográficos y extractos mostrados; el texto completo guardado se abre con cada registro.\n\nDescargar cuatro archivos de exportación de código fuente ↓Número de archivos y hash SHA-256 ↗Manifiesto de compilación original ↗\n\nEl paquete contiene las exportaciones recuperadas que coinciden con el recuento de filas de la compilación y sus tres rutas JSON registradas. La compilación original no registró los hash de entrada ni una ruta CSV principal; el manifiesto adjunto documenta los archivos recuperados y la comparación con el índice publicado.\n\nTrustpilot · steam_support_reviews.json354 filas · Exportación a JSON\nReddit · reddit_censored_forensics.json208 filas · Exportación a JSON\nGitHub · valve_ignored_bugs.json705 filas · Exportación a JSON; el nombre del archivo es una etiqueta del colector\nMaster · TOTAL_VALVE_SCANDALS_MASTER_DB.csv15,302 filas · Exportación a CSV utilizada para la comparación\nExpedientes judiciales · UNSEALED_EXHIBITS_AND_AML_DOSSIER.mdWolfire contra «Valve», correos electrónicos desclasificados, declaraciones de Gabe Newell, octubre de 2019, confesión sobre el blanqueo de capitales\nDatos clave · FACTS_AND_CITATIONS_DATABASE.md1,638 citas verificadas y específicas en los ámbitos de la competencia y la seguridad de 35\nArchivo de asistencia · support_canned_refusals.html1,505 Historial de tickets · Capturas de pantalla archivadas de 137 · Búsqueda instantánea en tiempo real\nCampos de registro, texto que falta y exportaciones superpuestas\n\nLas fechas, valoraciones, categorías y estados de las entradas se reproducen tal y como aparecen en las exportaciones originales. Una URL que falte seguirá sin aparecer. Las marcas «[eliminado]» o «[borrado]» no indican quién ha eliminado una entrada ni por qué. El filtro Steam / Valve se basa en la coincidencia de texto, no en una evaluación de relevancia.\n\n«Exportar coincidencias» descarga las entradas del índice con extractos; «Descargar registro» incluye el texto completo guardado. El archivo independiente 40,448-fila principal CSV y 1,690-fila «GitHub» CSV Lo que cuenta en esta versión son las exportaciones generales, no el número de fuentes.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam Archivo de pruebas — Documentos procedentes de «16,319»"
          },
          {
            "level": 2,
            "id": null,
            "text": "PLATAFORMA DE ORIGEN"
          },
          {
            "level": 2,
            "id": null,
            "text": "La compilación y sus archivos fuente"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/es/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/es/",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/TOTAL_VALVE_SCANDALS_MASTER_DB.csv",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive_manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive-inputs.zip",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive-inputs-manifest.json",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/unsealed_legal_and_aml/UNSEALED_EXHIBITS_AND_AML_DOSSIER.md",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/forensic_facts_1000/FACTS_AND_CITATIONS_DATABASE.md",
          "https://phishdestroy.io/steam_dossier/es/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/github_valve_unpatched_bugs.csv"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/es/steam_evidence_archive.content.json",
      "export_json_sha256": "8780dbaa5b2bfd0f55a364af6830e0f217c68150c2a238c2d656bf9b8457af89"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "es/support_canned_refusals.html",
      "language": "es",
      "title": "Steam Archivo de denegaciones de ayuda y respuestas predefinidas — El expediente «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/es/support_canned_refusals",
      "source_html_sha256": "56b5f863f5281ec70991a3ffac3fa3bf46567d01b9e9c8800cb5cccb4b11e004",
      "exported_at": "2026-09-29T00:17:30.732Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "support_canned_refusals.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/es/support_canned_refusals.pdf?v=print-20260929-v5",
        "sha256": "ad558fc0db7fa60882e2a869e9c8e1a36c4785a1b821b26c5b287e88381778ab",
        "bytes": 58845,
        "pages": 2
      },
      "integrity": {
        "signed_object": "support_canned_refusals.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "support_canned_refusals.content.json.asc",
        "digest_file": "support_canned_refusals.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify support_canned_refusals.content.json.asc support_canned_refusals.content.json",
          "sha256sum -c support_canned_refusals.content.json.sha256"
        ]
      },
      "content": {
        "text": "LO QUE DEMUESTRA ESTA SECCIÓN\n\nEste repositorio recoge capturas de pantalla originales conservadas en 137 y recursos de las víctimas auditados en 1,505, en los que se detalla la gestión automatizada de los tickets de asistencia de Valve. Demuestra que, cuando las cuentas se ven comprometidas mediante la redirección de OpenID o la generación no autorizada de claves API, el servicio de asistencia de Steam recurre sistemáticamente a respuestas estándar de denegación sin realizar ninguna investigación técnica. Al rechazar categóricamente la restauración de artículos o la divulgación de los registros de auditoría, la plataforma traslada toda la responsabilidad por los fallos estructurales de autenticación a los titulares de las cuentas comprometidas.\n\nTodas las capturas de pantalla son capturas realizadas por terceros. Los derechos de autor y el contenido pertenecen a sus respectivos autores y plataformas (usuarios de Reddit, autores de la comunidad Steam, reseñadores de Trustpilot, X y usuarios de YouTube). Se reproducen únicamente con fines de identificación y de información de interés público; no se reclama ningún derecho de propiedad sobre ellas. Cada imagen incluye un enlace a su fuente original.\n\nFigures reported on the source page\nMeasure\tReported value\tScope\nRegistros documentados\t1505\tReclamaciones de víctimas verificadas y hilos sobre multas\nCapturas de pantalla guardadas\t137\tCapturas de tickets en alta resolución almacenadas localmente\nTasa de recuperación\t0.0%\tSe conceden revisiones en los casos de secuestro de trenes de la línea «API»\nDuplicación de plantillas\t100%\tReutilización de guiones literales entre el personal (Ilya, Roger, Maverick)\nPruebas forenses: los tres pilares fundamentales de la denegación de asistencia\nPILLAR 01 · ADMISIÓNAnexo R:014\nConfirmada la participación de Roger en la MitM: API\n\nEn la respuesta al ticket n.º1cp582i, Steam, el miembro del equipo de asistencia «Roger» admite por escrito que los atacantes cancelan transacciones legítimas a través de API y las sustituyen por bots clonados en milisegundos, pero se niega a restaurar los artículos y le dice a la víctima que acuda a un «técnico informático local».\n\nRevisar la admisión por escrito ↗\nPILLAR 02 · ESCALACIÓNAnexo R-012\n7-Operaciones intradía: mantener la posición sin actuar\n\nUna víctima facilitó el SteamID64 de las cuentas del hacker durante el plazo de retención de las transacciones diarias de 7-. Los miembros del equipo de asistencia «Artem» e «Ilya» se negaron a bloquear los artículos robados, alegando la escasez de artículos virtuales, y cerraron el ticket con una plantilla automática.\n\nConsultar el expediente académico de varios empleados ↗\nPILAR 03 · POLÍTICAAnexo R-002\nLa escasez en el mercado frente a los derechos de propiedad\n\nLa política oficial de restauración de objetos de Valve establece explícitamente que los objetos no se devuelven porque su restauración «reduciría su escasez e inflaría la economía, lo que disminuiría el valor de los objetos en el Mercado de la Comunidad».\n\nCaptura de pantalla de la política de inspección ↗\nOrígenes históricos · 22 1 de marzo de 2018 a 2026\nAnexo H -003 · 8-Superficie de ataque sin parches anual\nLa primera sustitución comercial de la que se tiene constancia (22 de marzo de 2018)\n\nExactamente una semana antes de que Valve impusiera su polémico periodo de espera de 7-para el intercambio de objetos de Counter-Strike, la comunidad de intercambiadores descubrió los primeros casos reales de la Steam Vulnerabilidad de redireccionamiento en el servicio «API». Los atacantes secuestraron sesiones web para generar una clave no autorizada de «API» en steamcommunity.com/dev/apikey sin la confirmación de «2» (FA) de Mobile, lo que permite a los bots cancelar e intercambiar operaciones en tiempo real.\n\nAdvertencia del anuncio de servicio público «2018» de marzo: «Los estafadores pueden detectar automáticamente esta oferta de intercambio y la rechazarán en tu cuenta, ya que disponen de tu clave de Steam API. El bot de estafa te enviará ahora una oferta de intercambio por los mismos skins... ¡y tú no notarás la diferencia!»\nRuta de las pruebas históricas\n22 2018: de marzo Primer cambio de «API» del que se tiene constancia\n2019: El servicio de asistencia estandariza la defensa contra el «malware»\n2020: Se ha reforzado la seguridad del script «Cerrar solicitud de ayuda»\n2022–2026: Automatización del phishing con BitB y códigos QR\nAbrir el hilo original de Reddit sobre «2018» ↗\nPrimary sources\n\n137 gallery cards refer to 78 distinct primary URLs. Images and repeated exhibit captions are omitted from this reading edition.\n\nFull visual archive and original captures",
        "headings": [
          {
            "level": 2,
            "id": null,
            "text": "Figures reported on the source page"
          },
          {
            "level": 2,
            "id": null,
            "text": "Pruebas forenses: los tres pilares fundamentales de la denegación de asistencia"
          },
          {
            "level": 3,
            "id": null,
            "text": "Confirmada la participación de Roger en la MitM: API"
          },
          {
            "level": 3,
            "id": null,
            "text": "7-Operaciones intradía: mantener la posición sin actuar"
          },
          {
            "level": 3,
            "id": null,
            "text": "La escasez en el mercado frente a los derechos de propiedad"
          },
          {
            "level": 3,
            "id": null,
            "text": "La primera sustitución comercial de la que se tiene constancia (22 de marzo de 2018)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Primary sources"
          }
        ],
        "links": [
          "https://www.reddit.com/r/csgo/comments/1cp582i/i_got_api_scammed_what_do_i_do_now/",
          "https://www.reddit.com/r/DotA2/comments/1e5ovy4/my_account_was_hacked_and_steam_support_refuse/",
          "https://www.reddit.com/r/Steam/comments/3b2abd/steam_will_no_longer_restore_scammed_items_item/",
          "https://www.reddit.com/r/GlobalOffensiveTrade/comments/863tk1/psa_urgent_huge_scam_happening_read_here_how_to",
          "https://phishdestroy.io/steam_dossier/es/support_canned_refusals#gallery-grid"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/es/support_canned_refusals.content.json",
      "export_json_sha256": "d62304a90ee840622778b61baceb189f530131f0cfe0c40a842024e855af2130"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "es/valve_scandals_registry.html",
      "language": "es",
      "title": "Valve Registro de escándalos — El expediente de «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/es/valve_scandals_registry",
      "source_html_sha256": "8ca0bec684d8c48b6669d888d1abf8301e5ddf55beb9df16fada15b1e32e6d0e",
      "exported_at": "2026-09-29T00:17:30.846Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "valve_scandals_registry.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/es/valve_scandals_registry.pdf?v=print-20260929-v5",
        "sha256": "e0a4ec9e2ae331f1e4aff89ef4b945985e02b939ffe83f855e785cb8b901335e",
        "bytes": 63900,
        "pages": 6
      },
      "integrity": {
        "signed_object": "valve_scandals_registry.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "valve_scandals_registry.content.json.asc",
        "digest_file": "valve_scandals_registry.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify valve_scandals_registry.content.json.asc valve_scandals_registry.content.json",
          "sha256sum -c valve_scandals_registry.content.json.sha256"
        ]
      },
      "content": {
        "text": "Archivo de escándalos principales\nValve Registro central de escándalos — 160 Incidentes recopilados\nDATOS DE ORIGEN (SIN PROCESAR): 11,768\n\nNotificado. Con fuente. Aún pendiente.\n\nLO QUE DEMUESTRA ESTA SECCIÓN\n\nEste registro maestro recopila 160 registros primarios verificados de forma independiente que detallan fallos persistentes de la plataforma, informes de la comunidad eliminados y fallos no resueltos en la atención al cliente en todo el ecosistema de Valve. Abarca reclamaciones verificadas presentadas en Trustpilot, tickets archivados sobre problemas de seguridad en GitHub y procedimientos de las autoridades reguladoras, y pone de manifiesto fallos sistémicos recurrentes en la recuperación de cuentas y la resolución de reclamaciones de los clientes.\n\n← Volver al informe ejecutivo\n\n160 registros recopilados: una operación de asistencia valorada por quienes la utilizaron, hilos que dejaron de estar visibles, fallos de la plataforma notificados y sin resolver, y los incidentes de los que Valve ya ha tenido que dar cuenta. Nada de lo que aquí aparece es una interpretación nuestra: cada entrada incluye su fuente original. Abre una y léela tú mismo.\n\nRegistros de origen\n11,768\nEn todas las categorías\nDeficiencias de la plataforma\n3,372\nFallos en la plataforma señalados por la comunidad\nHilos censurados\n109\nPublicaciones de Reddit eliminadas por el moderador\nQuejas sobre la asistencia técnica\n471\nQuejas verificadas en Trustpilot\nViabilidad de la aplicación\nBloqueo de dominios de Auth-host\n\nEl bloqueo a nivel de dominio de los servidores de autenticación OpenID es técnicamente sencillo de implementar: una vez que se impide que un recurso sea redirigido a un inicio de sesiSteam, los dominios de terceros que actúan como proxies de autenticación para ese mismo recurso pueden filtrarse mediante el mismo conjunto de reglas. En el informe principal se ofrece un análisis detallado de la viabilidad de la implementación.\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\nConsulta la viabilidad de la aplicación en el expediente →\nCategoría: Reclamaciones al servicio de atención al cliente de Trustpilot (escaladas negativas filtradas)176 registros de origen coincidentes · duplicados ocultos\nConsumer Complaint2026-07-20\nAuthor: C***\n\nI’ve used Steam for years, but lately, their sales have really lost their edge. I was hoping to score some solid discounts, but many games still feel overpriced, even during sales. Plus, the support response times can be frustratingly slow when issues arise.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2026-07-20\nConsumer Complaint2025-05-09\nAuthor: S*** L***\n\nSupport are never able to help you and only able to redicrect you to public linkBreaking there own TOSNot able to provider a refundNot able to provide a safe place for gamingBase on the game you play you can get scam.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2025-05-09\nConsumer Complaint2024-12-30\nAuthor: F***\n\nThis company allowed a single phishing scammer 7656…2045 in 100's of its user community chat rooms \"Steam Chat\" the whole week of Winter Sales, 12-23-2024 - 2025 to spam spaceintrader a scam phishing website.Don't support Valve & Steam that support scams. Don't give your log in credentials to account hijacking scammers. This company also allows engagements of commercial advertising / spam for gambling in violation of its own Rules and Guidelines / Online Conduct. 7656…5023 proof - groups/deskinsfans key drop advertising, thanks TannerfromKD and Valve!*\"The Consumer Review Fairness Act (CRFA) protects people’s ability to share their honest opinions about a business’s products, services, or conduct, in any forum, including social media. The law protects a broad variety of honest consumer assessments, including online reviews, social media posts, uploaded photos, videos, etc. And it doesn’t just cover product reviews. It also applies to consumer evaluations of a company\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2024-12-30\nConsumer Complaint2024-07-31\nAuthor: A***\n\nhorrible company.randomly you get \"This account may have been accessed by someone else.\"this happened to me 3 times.the 3rd time they wanted a cd key.a spent useless cd key that nobody has any reason to keep laying around.i gave them the paypal bill for my first purchase back in 2015.i gave them a bill for my first phone number ever on the account.i still got the same email attached to the account.this company is literally a scam. nothing but a scam.they randomly claim you been accessed somewhere else and then require you to give them information no reasonable person would ever have, if not your done and have to rebuy everything.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2024-07-31\nConsumer Complaint2023-12-09\nAuthor: K***\n\nHad 288 euros in steam wallet, someone hacked my account even with two step verification, write a steam support for help but only answer was if something is spent in community market they can’t help.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2023-12-09\nConsumer Complaint2023-09-26\nAuthor: J***\n\nI was banned for saying \"Who let grandma on the PC\"and another for simply calling someone ignorant.Power tripping mods, devs who don't care, steam doesn't care. Yet allows racism/trolling/etc Fk steam, its a joke now.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2023-09-26\nConsumer Complaint2022-08-31\nAuthor: Anonymous\n\nSteam community is plain bad for a various reasons:1. Steam forums are a big mess, for example they allow users to post in any language and as result you get jumbled mess with posts in foreign languages together with English language posts. For example, If you check CS GO forums, you'll see half of posts are in Russian and half in English. I don't understand why such a big and international company would leave their forums so unorganized like that. All other normal companies have English only language allowed which is an international language and sometimes subforums for other languages like German, French and etc... so if French people want to post in French they go specifically in that sub-forum. But no, Steam doesn't care about this. Their forums is a one big mess.2. Moderation is biased and joke. I don't understand why such a big company like Steam can't afford to hire people for moderation and pay them. Instead they just recruit random people for moderation who do it for free and\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2022-08-31\nConsumer Complaint2022-05-28\nAuthor: J***\n\nThe login code never arrives. I hate Steam.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2022-05-28\nConsumer Complaint2021-11-08\nAuthor: N***\n\nThe service is terrible, I only signed up because I really like the game I wanted, but the rest is terrible, I hope to get something better soon.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-11-08\nConsumer Complaint2021-06-18\nAuthor: W***\n\nThey scam people for money, dont believe me? Read thisSource: Steam Subscribers/User Agreement NO GUARANTEESTO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, NEITHER VALVE NOR ITS AFFILIATES GUARANTEE CONTINUOUS, ERROR-FREE, VIRUS-FREE OR SECURE OPERATION AND ACCESS TO STEAM, THE CONTENT AND SERVICES, YOUR ACCOUNT AND/OR YOUR SUBSCRIPTION(S) OR ANY INFORMATION AVAILABLE IN CONNECTION THEREWITH.In short: You got a virus or your data leaked because of our software? Whoopsies we dont care, that isnt even legal or the last of their scammy stuff...\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-06-18\nConsumer Complaint2021-05-14\nAuthor: B***\n\nThe support is one of the worst I've ever seen.Useless support team.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-05-14\nConsumer Complaint2020-04-02\nAuthor: J***\n\nSteamcommunity has 15% fees, 15!!!!\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2020-04-02\nConsumer Complaint2020-03-27\nAuthor: H***\n\nWhat can I say? the support is one of the worst I've ever seen maybe the FUNCOM is much worse. If you tell the true on the steam forum you just got a BAN even if what you said did not violated the rules of the forum.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2020-03-27\nConsumer Complaint2018-03-16\nAuthor: B***\n\ndon't sign up will stick on your computer will kill your pc power you can't remove it from your pc even you deleted it will stay woking in the system\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2018-03-16\nConsumer Complaint2016-12-27\nAuthor: J***\n\nIn bloddy hate their page it's tiresome, it's in no way intuitive. I tried reaching out for support, but that is a maze.I'm simply trying to log in and redeem a key of a product I already bought, their search function is a joke. I f*u*c*k*i*n*g hate them. The layout is not like the how to video from the dealer, this can be done much simpler. I don't frigin care aboutn what other titles you have in store or what genre, I just want to redeem my key and install.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-12-27\nConsumer Complaint2016-10-28\nAuthor: P***\n\nSupport on site is terrible.Refunds not happend yet, despite games not working.No help at all if key is bought outside their system, so as a customer you can bounce back and through between bad support systems?? I wait for some other companies to compete in this market, for this can't be the best we as customers can expect.And do put an email up to find, instead of this stuppid website where you spend so long time trying to find a solution on, instead of a simple mail. Often the problem is not there, or if it's there just saying no help here???I need a response\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-10-28\nConsumer Complaint2016-06-26\nAuthor: V*** W***\n\nUseless support as always!\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-06-26\nConsumer Complaint2014-07-01\nAuthor: J***\n\nexpensive, and support team not willing to cooperate\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2014-07-01\nConsumer Complaint2014-04-15\nAuthor: B***\n\nWhen you pay for a program, you expect it too work. cant not buy or anything and have written to valve. but there is not a being done a damn thing abut it..\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2014-04-15\nConsumer Complaint2026-09-03\nAuthor: M***\n\nWorst platform ever wont give me a refund even though a game is unplayable because of bugs I won't ever be using the crap platform again I hope the platform breaks down for good piece fo crao\n\nTarget Domain: steamcommunity.com / steampowered.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2026-09-03\n\nNo se han encontrado registros coincidentes\n\nIntenta modificar la consulta que tienes abierta o consulta otra pestaña de categoría.\n\n1 / 9",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Valve Registro central de escándalos — 160 Incidentes recopilados"
          },
          {
            "level": 2,
            "id": null,
            "text": "Bloqueo de dominios de Auth-host"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: C***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: S*** L***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: F***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: A***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: K***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: Anonymous"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: N***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: W***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: H***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: P***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: V*** W***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: M***"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/es/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/es/#proxy-bypass-explainer",
          "https://phishdestroy.io/steam_dossier/es/#autoban-feasibility-section",
          "https://www.trustpilot.com/review/steamcommunity.com"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/es/valve_scandals_registry.content.json",
      "export_json_sha256": "5af19e749fe5d9e1cdb509b9dbba1f44a753492f4437c92f6eef3e7ce8ca9f4a"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "es/output_steam_network/index.html",
      "language": "es",
      "title": "Arquitectura, no vulnerabilidad: The Automation Network — El dossier de «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/es/output_steam_network/index",
      "source_html_sha256": "947ba46b039e198e426e13df57b9f53cb479f836bd0501e6f28c812930c93c0a",
      "exported_at": "2026-09-29T00:17:30.948Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__index.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/es/output_steam_network__index.pdf?v=print-20260929-v5",
        "sha256": "8486c5c3ac428263997c4c38112dfc42c6c44321f20a2df6e78cacc7713f911d",
        "bytes": 65851,
        "pages": 3
      },
      "integrity": {
        "signed_object": "output_steam_network__index.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__index.content.json.asc",
        "digest_file": "output_steam_network__index.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__index.content.json.asc output_steam_network__index.content.json",
          "sha256sum -c output_steam_network__index.content.json.sha256"
        ]
      },
      "content": {
        "text": "Anexo VII · Análisis de la arquitectura técnica\nSteam Arquitectura de red: fidelidad de protocolos y análisis del ecosistema\n\nLa automatización es la arquitectura de «Valve». No es un exploit.\n\nLO QUE DEMUESTRA ESTA SECCIÓN\n\nEste módulo describe la topología técnica de los repositorios de desarrolladores de 252, 3,320, los perfiles de GitHub y los pares de colaboradores de 4,214 que sustentan el ecosistema de automatización de Steam. Demuestra que la automatización de terceros se basa en el protocolo oficial Connection Manager de Valve, los esquemas Protobuf y las API web, sin código de explotación. Mediante el diseño algorítmico de Steam de los tokens de confirmación de Guard y el cobro de comisiones mínimas por transacción de hasta 66.7%, Valve, actúa como artífice intencional y principal beneficiario comercial de las operaciones automatizadas del ecosistema.\n\n← Volver al informe ejecutivo\n\nCuando Valve se dirige a los organismos reguladores, a las entidades de procesamiento de pagos o a las víctimas de estafas, atribuye el robo de identidades y la manipulación del mercado a «vulnerabilidades explotadas por terceros no autorizados» y a «automatización ilícita y fraudulenta». La realidad técnica de esta red de repositorios 252-demuestra exactamente lo contrario: Todos los marcos de automatización, bots de trading y flotas de «farming» operan estrictamente dentro de las definiciones oficiales del protocolo, las API web y los mecanismos de autenticación diseñados, documentados y monetizados por la empresa «Valve».\n\nConclusión forense: Arquitectura consciente frente a violación ilegítima\n\nEl software analizado en este módulo —entre los que se incluyen— SteamKit, node-steam-user, ValvePython/steam, y ArchiSteamFarm — contiene cero vulnerabilidades de software, cero daños en la memoria y cero exploits de día cero. Se trata de implementaciones de código abierto, limpias y robustas del protocolo propietario «Connection Manager» (CM) de Valve, de Google Protocol Buffers (Protobufs) y de las API web. Valve diseñó estas API para admitir inicios de sesión programáticos, y diseñó Steam Guard para permitir el uso de tokens de confirmación algorítmicos (identity_secret), y cobra una tarifa anunciada de 15% que se incrementa hasta hasta 66.7% a favor de Valve en las operaciones de alta velocidad y las ventas masivas de productos básicos que liquidan las redes de bots automatizadas.\n\nPilar 01 · Protocol Fidelity\nEsquemas oficiales de Protobuf\n\nLas bibliotecas de automatización no eluden los controles de seguridad. Serializan los mensajes Protobuf oficiales (steammessages_clientserver.proto) a través de TCP/WebSockets directamente a los clústeres oficiales de CM de Valve, exactamente igual que lo hace el cliente de Steam.\n\nPilar 02 · Algorítmica 2FA\nAutorización para el comercio programático\n\nToda la economía del comercio de skins, valorada en miles de millones de dólares, depende de Valve's IEconService API y claves de autenticación TOTP para dispositivos móviles. Valve ha diseñado específicamente Steam Guard para permitir las confirmaciones de operaciones entre máquinas.\n\nPilar 03 · Beneficiario comercial\nTráfico de la máquina monetizado: hasta un mínimo de66.7%\n\nValve Anuncia una comisión de 15%, pero en el caso de los artículos de gran volumen con los que operan los bots automatizados —cromos, estuches y artículos de bajo coste con precios que oscilan entre los $0.03 y los $0.05— la comisión mínima de dos céntimos de Valve ($0.01 Steam + $0.01 publisher) supone 50% a 66.7% a favor de Valve (2¢ deducidos de una tarjeta 3¢, lo que deja al vendedor con 1¢). Además, $5.00 por cuenta ($26.8M solo en la flota escaneada).\n\nMódulo «01» · Evidencia sobre repositorios y protocolos\nInfraestructura pública de desarrolladores y repositorios\n\nCatálogo forense detallado de los repositorios de código abierto de 252 que sustentan la automatización de Steam. Analiza cómo las herramientas estándar de ingeniería de software implementan los puntos finales publicados por Valve en API sin recurrir a exploits.\n\n252Repositorios\n4,554Enlaces relacionados con el puesto\nRevisar las pruebas del depósito →Módulo «02» · Demografía de los ecosistemas\nMétricas del ecosistema global de ingeniería\n\nDesglose geográfico e institucional de los ingenieros de software de 3,320 que contribuyen al ecosistema de automatización de Steam, incluidas las afiliaciones corporativas a las principales empresas del sector tecnológico.\n\n3,320Ingenieros\n98,902Pares de conexiones\nConsultar los indicadores del ecosistema →Módulo «03» · Gráfico visual interactivo\nGráfico interactivo del protocolo y la red de desarrolladores\n\nMapeo exhaustivo en forma de gráfico de red interactivo de Vis.js que recoge repositorios, bibliotecas de protocolos (SteamKit, Steamworks, ASF) y solapamientos entre colaboradores de distintos proyectos. Muestra de forma visual la arquitectura de software de código abierto, legítima e interconectada, que sustenta el ecosistema de automatización de Steam.\n\nInteractivoVis.js Motor\nAislamiento de clústeresBúsqueda en directo\nSin vulnerabilidadesAPI estándar\nAbrir el gráfico de red interactivo →\nContexto normativo y jurídico (artículo de GDPR 25 y protección del consumidor):\nEn virtud del principio de «protección de datos desde el diseño y por defecto», una arquitectura de plataforma que permita la generación silenciosa de claves de «API», la cancelación de operaciones sin previo aviso y la liquidación de activos automatizada por máquinas constituye una elección arquitectónica del operador de la plataforma. Cuando Valve rechaza sistemáticamente las reclamaciones de reembolso de los consumidores alegando que las pérdidas se debieron a «ciberataques externos», oculta que el vector de ataque es la propia arquitectura web API de Valve, diseñada intencionadamente.\n\nVISTA INTERACTIVA\n\nLa visualización interactiva completa del repositorio «252-», 3,320-, el gráfico de la red de desarrolladores, está disponible en network.html. Las métricas agregadas se encuentran en la Métricas de BI página.\n\nEl dossier «Steam» · Archivo de arquitectura técnica · Registros de código abierto · Todos los derechos cedidos a la humanidad.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam Arquitectura de red: fidelidad de protocolos y análisis del ecosistema"
          },
          {
            "level": 3,
            "id": null,
            "text": "Esquemas oficiales de Protobuf"
          },
          {
            "level": 3,
            "id": null,
            "text": "Autorización para el comercio programático"
          },
          {
            "level": 3,
            "id": null,
            "text": "Tráfico de la máquina monetizado: hasta un mínimo de66.7%"
          },
          {
            "level": 2,
            "id": null,
            "text": "Infraestructura pública de desarrolladores y repositorios"
          },
          {
            "level": 2,
            "id": null,
            "text": "Métricas del ecosistema global de ingeniería"
          },
          {
            "level": 2,
            "id": null,
            "text": "Gráfico interactivo del protocolo y la red de desarrolladores"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/es/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/es/output_steam_network/valve_ru_farming_isolated.html",
          "https://phishdestroy.io/steam_dossier/es/output_steam_network/steam_ecosystem_dashboard.html",
          "https://phishdestroy.io/steam_dossier/es/output_steam_network/network.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/es/output_steam_network__index.content.json",
      "export_json_sha256": "bbaf2e626309dbdb7b12d69e8844c4f78522df15a374b6247cf296cf8bb08886"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "es/output_steam_network/network.html",
      "language": "es",
      "title": "Explorador de desarrolladores y repositorios — El dossier de «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/es/output_steam_network/network",
      "source_html_sha256": "56d7506e7bdfde752f8ed87ad72a88f8b6b6fcfe5b13450b15aab8b6ade36a3b",
      "exported_at": "2026-09-29T00:17:32.575Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__network.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/es/output_steam_network__network.pdf?v=print-20260929-v5",
        "sha256": "e68d8339d313f3627d1189a042be971421a9b0883d5769eca1024b7da4fee653",
        "bytes": 35869,
        "pages": 1
      },
      "integrity": {
        "signed_object": "output_steam_network__network.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__network.content.json.asc",
        "digest_file": "output_steam_network__network.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__network.content.json.asc output_steam_network__network.content.json",
          "sha256sum -c output_steam_network__network.content.json.sha256"
        ]
      },
      "content": {
        "text": "Explorador de desarrolladores y repositorios\n\nBuscar un nodo. Examinar la relación registrada.\n\nREGISTROS PÚBLICOS / CONEXIONES RECOPILADAS\nBúsqueda en directo\nCapas de filtro\nTotal de desarrolladores3,320\nTotal de repos252\nGRÁFICO MOSTRADO / SUBCONJUNTO DE LA COLECCIÓN468 NODOS • 1103 ARISTAS\nRegistro de perfil seleccionado\n\n💡 Haz clic en cualquier nodo del gráfico o escribe en el campo «Buscar» para examinar las conexiones recopiladas y las rutas de origen correspondientes.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Explorador de desarrolladores y repositorios"
          }
        ],
        "links": []
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/es/output_steam_network__network.content.json",
      "export_json_sha256": "f9dd66a977e850671d5126c6716bf8dfffb761c15a7fcc7c0d86bb2556af8e7f"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "es/output_steam_network/steam_ecosystem_dashboard.html",
      "language": "es",
      "title": "La red «The Collected» en cifras — El dossier de «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/es/output_steam_network/steam_ecosystem_dashboard",
      "source_html_sha256": "9f81dee105a03e24e6104378cd2aa7af3667df2382b640f229cd4649a7826d72",
      "exported_at": "2026-09-29T00:17:32.246Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__steam_ecosystem_dashboard.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/es/output_steam_network__steam_ecosystem_dashboard.pdf?v=print-20260929-v5",
        "sha256": "a2d38a29db527859f432f24bb0b1d9f40dae35d01613f5e303f60436ec83c128",
        "bytes": 39031,
        "pages": 2
      },
      "integrity": {
        "signed_object": "output_steam_network__steam_ecosystem_dashboard.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__steam_ecosystem_dashboard.content.json.asc",
        "digest_file": "output_steam_network__steam_ecosystem_dashboard.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__steam_ecosystem_dashboard.content.json.asc output_steam_network__steam_ecosystem_dashboard.content.json",
          "sha256sum -c output_steam_network__steam_ecosystem_dashboard.content.json.sha256"
        ]
      },
      "content": {
        "text": "RESUMEN DE ESTADÍSTICAS // ARCHIVO02\nSteam Cuadro de mando del ecosistema — La red en cifras\n\nLa red, en cifras.\n\nLO QUE DEMUESTRA ESTA SECCIÓN\n\nEste panel de control recopila información estructural de los desarrolladores de 3,320 y los repositorios de 252, identificando 68 bases de código específicas del sector del juego y puentes de conexión entre plataformas. Los datos empíricos ponen de relieve la concentración geográfica y los solapamientos entre desarrolladores, lo que demuestra que la infraestructura de juego de terceros funciona como una industria de software organizada y altamente interconectada, integrada en la plataforma de Steam.\n\n← Volver al informe ejecutivo\n\nEstadísticas consolidadas de la base de datos de la investigación: distribución geográfica, principales empresas, repositorios de apuestas con «skins» y puentes de conexión activos.\n\nScanned Devs3320\nTotal de repos252\nRepos relacionados con el juego68\nTotal de conexiones1,426\nEstructura y sectores de la automatización\nSector I — Núcleo de la Corporación «Valve»\n\nRepositorios oficiales y software del sistema. Espacio de desarrollo confirmado de los empleados deValve, Nephyrin y Joe Ludwig.\n\nSector II — Motores de autorización y emuladores de protocolos (SteamKit)\n\nBibliotecas de red creadas mediante ingeniería inversa, de la que son coautores Nephyrin, de «Valve», y DoctorMcKay, desarrollador de juegos de azar de «skins».\n\nSector III — Clientes de «card farming» (ArchiSteamFarm)\n\nUtiliza emuladores del protocolo SteamKit para ejecutar millones de clientes falsos (en modo inactivo) en segundo plano con el fin de conseguir cromos.\n\nGeografía de los desarrolladores\nAlemania57\nEstados Unidos52\nCanadá48\nReino Unido44\nPolonia30\nFrancia28\nFederación Rusa27\nChina27\nEE. UU. (estado de Washington)23\nAustralia19",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam Cuadro de mando del ecosistema — La red en cifras"
          },
          {
            "level": 3,
            "id": null,
            "text": "Sector I — Núcleo de la Corporación «Valve»"
          },
          {
            "level": 3,
            "id": null,
            "text": "Sector II — Motores de autorización y emuladores de protocolos (SteamKit)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Sector III — Clientes de «card farming» (ArchiSteamFarm)"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/es/#briefing-heading"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/es/output_steam_network__steam_ecosystem_dashboard.content.json",
      "export_json_sha256": "15ff7488aa9ba7d2f021c2ca0bff4f0933b67aed2dbd8ff79eb07753792b1502"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "es/output_steam_network/valve_ru_farming_isolated.html",
      "language": "es",
      "title": "Código, colaboradores y bifurcaciones — El dossier de «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/es/output_steam_network/valve_ru_farming_isolated",
      "source_html_sha256": "1dd9224374adcb83937a2edc29459e7f69ce91195a3d31edf18f376d92c8cc0f",
      "exported_at": "2026-09-29T00:17:32.833Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__valve_ru_farming_isolated.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/es/output_steam_network__valve_ru_farming_isolated.pdf?v=print-20260929-v5",
        "sha256": "fe960ff765186ef541a5cfab1b417bb85db14aadfb9ded50c4fbdf34e30b9042",
        "bytes": 41323,
        "pages": 2
      },
      "integrity": {
        "signed_object": "output_steam_network__valve_ru_farming_isolated.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__valve_ru_farming_isolated.content.json.asc",
        "digest_file": "output_steam_network__valve_ru_farming_isolated.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__valve_ru_farming_isolated.content.json.asc output_steam_network__valve_ru_farming_isolated.content.json",
          "sha256sum -c output_steam_network__valve_ru_farming_isolated.content.json.sha256"
        ]
      },
      "content": {
        "text": "PARTE II / SIGUE LA RELACIÓN DOCUMENTADA\n\nLas bifurcaciones, las contribuciones y las dependencias de software constituyen pruebas claras. Esta visión mantiene los roles recopilados; el empleo, las vulnerabilidades de seguridad y la implicación en actividades delictivas requieren fuentes adicionales.\n\nAbrir el mapa interactivo de capacidades ↗\nFUENTES PÚBLICAS / AUDITORÍA DE FUNCIONES\nEl código. Los colaboradores. Las bifurcaciones.\n1. Nephyrin: bifurcaciones y contribuciones\n\nLa instantánea proporcionada identifica a Nephyrin como colaborador de ValveSoftware/Proton y como creador de las ramas SteamRE/SteamKit y SteamRE/open-steamworks. En los datos de su perfil figura «Valve Software». Estos campos deben interpretarse por separado.\n\nUna bifurcación registra una copia del repositorio. Esta exportación no incluye una confirmación que refleje los cambios en el código de autenticación de SteamKit.\nReferencias del repositorio / consultar el historial\nSteamRE/SteamKit ↗ SteamRE/open-steamworks ↗\n2. Funcionalidades públicas: automatización sin cliente de escritorio\n\nSteamKit y node-steam-user permiten interactuar mediante programación con Steam. ArchiSteamFarm documenta la gestión de cuentas múltiples para la obtención de tarjetas y declara a SteamKit2 como dependencia.\n\nSe trata de capacidades concretas de automatización. La ejecución sin interfaz no implica un uso comercial exclusivo ni eludir la protección de «Steam». Las cuestiones relevantes son las credenciales solicitadas, las acciones a las que tienen acceso y los controles aplicados por la plataforma.\n\nFuente: archivos README de los proyectos y ArchiSteamFarm.csproj. El mapa de capacidades incluye enlaces a cada una de las dependencias documentadas.\n3. JoeLudwig: la etiqueta de colaborador del hl2sdk\n\nLa captura de pantalla muestra a JoeLudwig como colaborador de alliedmodders/hl2sdk, ValveSoftware/openvr y ValveSoftware/source-sdk-2013.. Se trata de una relación entre proyectos observable. La exportación no aporta pruebas que vinculen un cambio concreto en el SDK con un robo o con una implementación relacionada con el juego.\n\nReferencias del repositorio / consultar el historial\nalliedmodders/hl2sdk ↗ DoctorMcKay/node-steam-user ↗\nESQUEMA LÓGICO // PISTAS\nDiagrama de flujo de la lógica de conexión:\nPERFIL DE RELACIÓN\nNephyrin / perfil recopilado\nColaborador: Proton. Autores de la bifurcación: SteamKit y open-steamworks.\n▼ Relación de bifurcaciones recopiladas\nBIBLIOTECA COMUNITARIA\nSteamRE/SteamKit\nBiblioteca de la red pública «Steam» gestionada por la organización SteamRE.\n▼ Dependencia declarada de SteamKit2\nAUTOMATIZACIÓN DOCUMENTADA\nJustArchiNET/ArchiSteamFarm\nSe documenta la obtención de tarjetas a través de varias cuentas y una dependencia de SteamKit2.\nREVISIÓN DE LA EVIDENCIA / RESUMEN DE LA FUENTE\nREGISTRO: etiquetas distintas para colaboradores y bifurcadores.\nDOCUMENTADO: las bibliotecas públicas favorecen las interacciones programáticas Steam.\nPREGUNTA ABIERTA: la autoría concreta del código, la aprobación de la plataforma y la atribución del uso indebido requieren pruebas independientes.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "El código. Los colaboradores. Las bifurcaciones."
          },
          {
            "level": 2,
            "id": null,
            "text": "1. Nephyrin: bifurcaciones y contribuciones"
          },
          {
            "level": 2,
            "id": null,
            "text": "2. Funcionalidades públicas: automatización sin cliente de escritorio"
          },
          {
            "level": 2,
            "id": null,
            "text": "3. JoeLudwig: la etiqueta de colaborador del hl2sdk"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/es/investigation_part2.html#automation-map",
          "https://github.com/SteamRE/SteamKit",
          "https://github.com/SteamRE/open-steamworks",
          "https://github.com/alliedmodders/hl2sdk",
          "https://github.com/DoctorMcKay/node-steam-user"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/es/output_steam_network__valve_ru_farming_isolated.content.json",
      "export_json_sha256": "5116e70d72765686d2053e1f8f037cf4bf754ace67202bfb74e0338109100454"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "fr/card_economy.html",
      "language": "fr",
      "title": "L'économie des cartes — Le dossier Steam",
      "source_url": "https://phishdestroy.io/steam_dossier/fr/card_economy",
      "source_html_sha256": "aebf1383e9f681afe9c77d789e0ae9dd7949bd912e02d50d9505aa3ae2ce4e32",
      "exported_at": "2026-09-29T00:17:33.799Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "card_economy.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/fr/card_economy.pdf?v=print-20260929-v5",
        "sha256": "7e5074a4fbb7fd746f6302075d464f22cf3ca6db970da2ab8ffd619457f3d7bb",
        "bytes": 260838,
        "pages": 25
      },
      "integrity": {
        "signed_object": "card_economy.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "card_economy.content.json.asc",
        "digest_file": "card_economy.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify card_economy.content.json.asc card_economy.content.json",
          "sha256sum -c card_economy.content.json.sha256"
        ]
      },
      "content": {
        "text": "ANNEXE V — L'ÉCONOMIE DES CARTES\nUne ferme de bots n'est pas une fuite dans la boutique de Valve. C'est une client.\n\nUn compte Steam ne peut recevoir aucune carte à collectionner tant qu'il n'a pas dépensé $5.00 dans la boutique. Il ne peut pas « farmer » un jeu dont il n’est pas propriétaire, ni un jeu qui lui a été offert gratuitement. Ainsi, avant qu’un système automatisé de « farming » de cartes ne produise quoi que ce soit, il a dû payer pour y avoir accès — par compte, au prix publié par Valve. Ensuite, la clause d’automatisation de Valve énonce, ligne par ligne, exactement ce que ce système de farming produit ; sa licence interdit toute voie permettant de transformer une carte récoltée en argent ; et son marché prélève une commission lorsque la carte est vendue — annoncée à 15%, mais plafonnée à deux centimes par vente, ce qui, pour une carte dont le prix est exprimé en centimes, représente la majeure partie du prix. Cette illustration mesure l’ampleur de ce commerce, ce que coûte en sets le niveau le plus élevé d’un profil, et ce que le service de contrôle de Valve fait de cette même clause lorsque le compte appartient à un trader ordinaire.\n\nCe qu'une exploitation agricole doit acheter en prioritéCombien coûte un niveau en lots ?Des deux côtés du bureauQui régit le système économique des cartes ?\n$5.00Effectuer des achats en magasin avant qu'un compte puisse recevoir une carte — Page d'aide de Valve\n13,876Jeux classés Steam qui proposent des cartes à collectionner et comportent 99,971 types de cartes différents\n694,673Séries complètes de cartes actuellement en stock chez 91 robots de trading cotés en bourse\n1,389,346Les quotas de cartes de compte et de jeu que le stock a déjà utilisés, au minimum\n$9.99Prix médian d'un jeu de cartes — une fois complet, ce jeu se vend à un prix médian de $0.74\n97,114Les membres du groupe d'échange de cartes dont la liste des modérateurs comprend un employé Valve — § 08\n01 — Le processus\nQu'est-ce qu'une ferme, en détail ?\n\nCes informations proviennent exclusivement de la documentation de l'outil lui-même et des pages d'assistance de Valve. Aucune des informations contenues dans cette section n'est déduite, et aucune n'est contestée par l'une ou l'autre des parties.\n\nÉtape 1\nAcheter à\n\nLe compte ne doit pas être limité. La page d'assistance de Valve interdit aux comptes à accès limité de « Participer au marché Steam », tiré de « Échange d'objets de la communauté Steam (cartes à collectionner, boosters, gemmes, etc.) » et de « Gagner Steam niveaux de profil (bloqué au niveau 0) et des cartes à collectionner ». L'entrée, c'est l'argent : « Vous devrez dépenser au moins $5.00 USD dans le magasin Steam. »\n\nÉtape 2\nAcheter des jeux\n\nLes cartes ne s'obtiennent qu'en jouant à des jeux que vous possédez. « Vous devez être propriétaire du jeu sur votre compte Steam pour pouvoir recevoir les cartes qui y sont associées. Le partage familial ne vaut pas comme propriété et n'est pas pris en compte. » Les itinéraires gratuits sont également fermés : « Les jeux payants que vous avez obtenus gratuitement dans le cadre d'une promotion ne peuvent pas être utilisés pour obtenir des cartes. », et « On ne peut pas obtenir de cartes dans les jeux F2P sans y dépenser d'argent. »\n\nÉtape 3\nInactif\n\nL'outil connecte le compte au réseau Steam en mode sans interface graphique, « analyse vos badges », génère la liste des titres pouvant faire l'objet d'une exploitation et lance « Jouer à un jeu éligible et vérifier régulièrement si le jeu a déjà été entièrement « farmé ». » Description du mécanisme par son responsable : il « ne fait rien d'autre que d'indiquer à Steam que nous jouons à tel ou tel jeu. »\n\nÉtape 4\nLes gouttes s'épuisent\n\nChaque titre est fini. « Chaque jeu comporte un nombre fixe de cartes à obtenir. Une fois que vous les avez toutes obtenues (environ la moitié du set complet), le jeu ne vaut plus la peine d'être farmé. » Une exploitation agricole qui souhaite continuer à produire doit continuer à acheter des cartes. L'approvisionnement en cartes est limité par les achats — c'est voulu, et cela joue en faveur de Valve.\n\nÉtape 5\nRetrait\n\nLa carte quitte le jeu par l'une des trois voies suivantes : elle est vendue sur le Marché communautaire, échangée ou transformée en gemmes. Chacune de ces opérations correspond à une transaction sur la Place de marché des abonnés ou à un échange, et le § 3.D prévoit les frais suivants : « Valve peut facturer des frais pour les transactions effectuées sur une place de marché d'abonnements. » C'est cette étape qui fait de tout cela une violation — voir 05.\n\nSources, lues et citées mot pour mot sur 2026-09-22 : Steam Assistance — Comptes utilisateur limités ↗ · ArchiSteamFarm FAQ ↗ · Valve — Steam FAQ sur les cartes à collectionner ↗ · Steam Contrat d'abonnement ↗ archivé 2026-09-24 ↗. ArchiSteamFarm est utilisé tout au long de cette page en tant qu'instrument de mesure, et non en tant que défendeur ; sa propre documentation indique clairement que « L'ASF n'est pas agréée par Valve ».\n\n02 — L'échelle\nAvant même qu'une exploitation agricole ne gagne un centime, elle a déjà dépensé Valve\n\nÉtant donné qu'un compte « limité » ne peut pas recevoir de carte, chaque compte d'une ferme doit être libéré de son statut « limité » avant de pouvoir produire quoi que ce soit. Le seuil est publié et les frais sont facturés par compte.\n\nSuperficie de l'exploitation agricole\tD'où vient ce chiffre ?\tMontant minimum d'achat en magasin pour pouvoir bénéficier de la carte\n10 comptes\tLe plafond recommandé par l'ASF — « sur la base des directives internes Valve, ainsi que de nos propres suggestions »\t$50\n100 à 200 comptes\tLimite technique mentionnée dans cette même FAQ : « Vous pouvez faire fonctionner jusqu’à 100 à 200 bots avec une seule adresse IP et une seule instance ASF. »\t$500 – $1,000\n120 comptes\tCas n° 3 ci-dessous — exclusion définitive\t$600\n170 comptes\tCas de sanction n° 2 ci-dessous — exclusion définitive lors des soldes d'hiver 2017\t$850\n1,000 comptes\tAffaire n° 1 ci-dessous — interdiction des échanges\t$5,000\n5,000 comptes non vérifié\tBalance de l'opérateur communiquées dans le cadre de cette enquête et non vérifiées de manière indépendante — voir la note sur l'origine des données\t$25,000\n10,000 comptes non vérifié\tBalance de l'opérateur communiquées dans le cadre de cette enquête et non vérifiées de manière indépendante — voir la note sur l'origine des données\t$50,000\n\nLes deux dernières lignes sont les seuls chiffres de cette page qui reposent sur un rapport non vérifié plutôt que sur un document — elles sont signalées dans le tableau et expliquées dans la note sur l'approvisionnement, et rien d'autre ici ne dépend d'eux. La colonne de droite repose uniquement sur le calcul arithmétique du seuil de $5.00 USD publié par Valve, et rien d'autre. Il s'agit d'un étage, il ne s'agit pas d'une estimation du coût d'une ferme ni des gains générés par Valve : ce chiffre exclut les jeux, qui doivent être achetés et ne peuvent pas avoir été obtenus gratuitement dans le cadre d'une promotion, ainsi que les quelque 15% prélevés par le Marché communautaire lors de la vente des cartes. Aucun chiffre d'affaires n'est indiqué sur cette page.\n\nEt Valve a lui-même fixé le prix d'une distribution de cartes. Sa FAQ sur les cartes à collectionner présente le taux de conversion du modèle « free-to-play » en dollars :\n\n« Les jeux gratuits distribuent des cartes de jeu en fonction de vos achats effectués dans le jeu. » Pour chaque $9 USD dépensé (environ) « Depuis le lancement de la version bêta des cartes à collectionner Steam, vous gagnerez une carte. »\n\n— Valve, Steam FAQ sur les cartes à collectionner ↗ · vérifié mot pour mot 2026-09-22\n\nUne carte à collectionner n’est pas un cadeau promotionnel qui fait perdre de l’argent à la plateforme. C’est un produit que Valve vend, au prix Valve annoncé, puis pour lequel elle facture une deuxième fois lors de la revente. C’est pourquoi la description honnête d’une « ferme à cartes » n’est pas parasite. C'est acheteur en gros.\n\nQuelle est la taille réelle de l'objet acheté ?\n\nTout ce qui suit jusqu’à la fin de cette section est mesuré, et non pas simplement rapporté. Le recensement des cartes provient de Steam, la liste de prix des badges publiée par Card Exchange ; les prix des jeux eux-mêmes proviennent de l’API de la boutique de Valve ; quant au stock de bots, il provient d’un annuaire public de bots accessible à tous. Ces trois sources ont été consultées sur 2026-09-22 et les calculs sont présentés dans leur intégralité dans section 08.\n\n13,876Jeux de cartes\n99,971Différents types de cartes\n5 · 6 · 15Nombre de cartes par jeu : min., médiane, max.\n$0.74Prix médian d'un ensemble complet\n$23,586.57Un exemplaire de chaque lot sur le marché\nQuelle est la taille d'un ensemble ?\n\n13,876 jeux de cartes dans le lot. Valve en attribue environ la moitié à un seul compte.\n\n0\n1,250\n2,500\n3,750\n5,000\n5\n6\n7\n8\n9\n10\n11\n12\n13\n14\n15\nCombien coûte la licence ?\n\nPrix catalogue de ces mêmes jeux sur la boutique de Steam, en dollars américains.\n\n0\n1,000\n2,000\n3,000\n4,000\n<$1\n$1-3\n$3-5\n$5-10\n$10-20\n$20-40\n$40+\nCe que renvoie l'ensemble final\n\nPrix du marché de la collection complète de ces mêmes jeux.\n\n0\n1,500\n3,000\n4,500\n6,000\n<$0.50\n$0.50-1\n$1-2\n$2-5\n$5-10\n$10+\n\nEn comparant le deuxième et le troisième graphique, la structure des transactions apparaît clairement sans qu'il soit nécessaire de faire des calculs : les jeux se regroupent autour de la dizaine de dollars, tandis que les lots qu'ils rapportent se situent en dessous d'un dollar. Dans les deux cas, il s'agit du nombre de jeux 13,876, sur la même unité d'échelle ; la comparaison porte donc sur deux hauteurs et non sur deux échelles différentes.\n\nVoilà pour le côté de l'offre. Quant au côté de la demande, Valve n'a pas besoin d'en faire la publicité, car tout est déjà accessible au public : un seul répertoire public de bots d'échange de cartes répertorie 91 robots disposant actuellement de 694,673 ensembles complets en stock. Pas besoin de se connecter, pas d'extraction de données d'une place de marché, pas de données privées : le nombre d'exemplaires disponibles est indiqué sur la page, à côté du nom de chaque bot.\n\nFaites de ce titre la seule valeur qui compte ici. La règle de Valve : « La plupart des jeux distribuent un nombre de cartes correspondant à environ la moitié du nombre total de cartes du jeu… » Tu devras récupérer l'autre moitié de l'ensemble auprès d'autres membres de la communauté.« Un seul compte ne peut jamais terminer une série en jouant. Il en faut au moins deux, chacun possédant ce jeu et utilisant son quota de « drop » (une fois par partie). Les « drops » ne se régénèrent pas.\n\n694,673Ensembles en stock, 91 bots publics\n3,473,365Cartes, avec un minimum de 5 cartes\n1,389,346Allocations de perte consommées, minimum\n2,602Comptes ne possédant qu’un seul jeu, bot le plus actif\nOù se trouvent les ensembles 694,673\n\nLes douze plus grands des 91 « card bots » cotés en bourse, classés selon le nombre de séries complètes en stock. Les dix plus grands détiennent à eux tous 248,115 séries, soit 35.7% de chaque élément présent sur le tableau.\n\n0\n11,250\n22,500\n33,750\n45,000\nCard Supply #4 (High)\nN!vq's Leveling (High)\nAlice [BOT] LEVEL-UP RARE SETS\nN!vq's Leveling (Low)\nDisco Lite Level Up\nN!vq's Leveling (Mid)\nbaty131store.net | Level Up\nKitten - Supreme\nArashirn | Level Up\nSH (Junior) Level Up\nDuobot.com - Overstock\nlvlupbot.com - godlike\n\nChacune de ces 1,39 million d'unités appartenait à un compte qui possédait le jeu, avait franchi le seuil de $5.00 et ne pourra plus jamais générer ces gains. C'est stocks invendus sur quatre-vingt-onze bots. Ce n'est pas un indicateur du marché ; c'est un indicateur de ce qui reste une fois le marché écarté.\n\nCe dernier chiffre correspond à une répartition par catégorie, et non à un décompte des utilisateurs. Un bot recense 14,310 ensembles tirés de seulement 11 jeux ; par conséquent, au moins l’un de ces jeux est représenté par 1,301 ensembles, ce qui correspond à au moins 2,602 comptes distincts ayant chacun acheté ce jeu. C'est le plus petit nombre que l'arithmétique autorise, et cela concerne un bot sur quatre-vingt-onze.\n\nCe que ce sol dit et ne dit pas\n\nCes bots achètent des cartes aussi bien auprès de joueurs lambda qu’auprès de « fermes » : leurs tarifs d’achat publiés constituent l’intérêt de cet annuaire. Les 1,39 million de quotas ne correspondent donc pas au nombre de comptes détenus par des exploitations agricoles. Il s’agit d’un décompte des récompenses pouvant être obtenues une fois par compte et une fois par jeu, qui ont été utilisées quelque part sur Steam et qui se sont retrouvées, invendues, dans le stock commercial. Que le compte associé à chacun d’entre eux ait été un compte de farm ou celui d’un adolescent souhaitant vider sa page de badges, cela ne change rien à ce que Valve a récolté : le déblocage de $5.00, la licence du jeu et une commission sur chaque transaction sur le Marché — non pas 15%, mais 15% ou les deux montants minimaux d'un cent, selon celui qui est le plus élevé, ce qui, sur une carte dont le prix est indiqué en cents, représente de loin le montant le plus élevé. Le calcul figure dans le barème des frais ci-dessous. C'est là l'objet de cette page, et il ne s'agit pas d'une critique à l'encontre des agriculteurs : le comportement Valve pour lequel des frais sont facturés est précisément celui qu'il invoque, mot pour mot, lorsqu'il exclut définitivement un utilisateur pour « usage commercial ».\n\nCe chiffre constitue également un seuil dans un second sens. Il ne prend en compte que les actions qui sont mis en vente et non vendus aujourd’hui sur les bots qui choisir d'apparaître dans un annuaire public. Tout ce qui a déjà été vendu, tout ce qui est détenu à titre privé et tous les bots ne figurant pas dans le répertoire sont exclus.\n\nEt l'agriculture n'est pas rentable aux prix pratiqués par Valve\n\nL'objection qui vient immédiatement à l'esprit est qu'une « ferme » achète des jeux bon marché pour y créer des cartes coûteuses. L'API de la boutique de Steam indique pourtant le contraire. Sur les 13,876 jeux comportant des cartes, les prix ont été fixés pour 13,713 ; 12,918 sont des titres payants dont le prix catalogue médian est de $9.99. Le prix de vente médian d'un ensemble fini s'élève à $0.74. Il faut deux licences par ensemble. Le coût médian d'un ensemble s'élève donc à environ $19.98 des licences de jeux pour la production et les retours $0.74.\n\nMesuré à 2026-09-22\tValeur\tCe que cela règle\nPrix moyen affiché, jeu de cartes\t$9.99\tC'est la licence qui représente la partie la plus coûteuse de la transaction, et non la carte.\nJeux dont le prix est de $4.99 ou moins\t3,665 (28.4%)\tMême la queue la moins chère coûte plus cher que l'ensemble qu'elle permet d'obtenir\nLe jeu de cartes le moins cher de la boutique\t$0.99\tDeux licences, $1.98, pour un ensemble qui se vend généralement à moins de $1.30\nLes jeux dont le coffret coûte plus cher que le jeu lui-même\t323 sur 12,918 (2.5%)\tL'arbitrage sur les cartes par rapport aux prix catalogue de Steam existe dans 1 jeu sur 40\nLes jeux « free-to-play » recensés\t795\tEt Valve fixe le prix de chacune de ses offres à $9 de dépenses dans le jeu\n\nCe qui tranche la question économique en faveur de Valve et va à l'encontre de la thèse habituelle. Aux prix pratiqués par Valve lui-même, La « culture de cartes » est une activité déficitaire qui ne fonctionne qu’avec des licences acquises à un prix inférieur au prix catalogue de Steam. — offres groupées, tarification régionale, revente de produits phares. Les cartes ne sont qu’un détail. C’est l’achat qui compte. Et cet achat a eu lieu le Steam.\n\nCe que la ferme soutient réellement\n\nSi l’on rassemble tous ces éléments, la ferme cesse d’apparaître comme quelque chose que Valve tolère pour devenir quelque chose dont Valve a besoin. Chaque apport fourni par une ferme correspond à une prestation que Valve déclare ou facture. Suivons le parcours d’un compte de bot vers l’extérieur :\n\nUn compte « farmé »un « client grossiste », et non une fuite\nVentes de jeux vidéo\n\nIl achète les titres qu’il « farm » — des jeux de cartes « 13,876 » aux jeux de mauvaise qualité « $0.50 » — car les cartes ne s’obtiennent qu’à partir des jeux que l’on possède.\n\n« En ligne » et temps de jeu\n\nCela les incite à lâcher des cartes, ce qui alimente les chiffres relatifs au nombre de joueurs simultanés et d’heures jouées que Valve présente comme un indicateur d’engagement — la statistique précise que le § 4.C qualifie de « temps de jeu fictif ».\n\nInscriptions\n\nIl faut franchir le seuil de $5.00 du compte à limite avant de pouvoir recevoir une carte — les dépenses réelles en magasin sont comptabilisées à raison de Valve par compte.\n\nArgent sur le portefeuille et frais\n\nChaque carte vendue transite par le Marché, où les frais peuvent atteindre 66.7% pour une carte de faible valeur et où le produit de la vente reste bloqué dans le portefeuille Steam.\n\nRelations publiques de niveau 0\n\nLes vitrines des badges et des niveaux Valve n'existent que parce que des ensembles ont été créés — et le sommet de ce classement est occupé par des bots (voir § 03).\n\nSi l'on retire la ferme, tous les chiffres ci-dessus diminuent. — le jeu s'est moins bien vendu, la communauté « en ligne » était plus restreinte, le compte n'a jamais été créé, les frais n'ont jamais été prélevés et le niveau n'a jamais été atteint. C'est pourquoi une règle interdisant l'automatisation coexiste avec des millions de comptes automatisés : l'interdiction est une option, et l'activité est source de revenus.\n\nEt le retrait lui-même entraîne une perte de valeur : Valve, car il est imposé deux fois\n\nLa carte n'est pas la fin de la boucle. Les mécanismes propres à Valve permettent à une carte d'être écrasée en pierres précieuses, et les gemmes doivent être utilisées pour fabriquer paquets de cartes — trois cartes supplémentaires — qui sont à nouveau vendues ou détruites. Chaque étape correspond à une transaction sur le marché ou à une conversion, et chacune est soumise à une taxe. Le sens de cette boucle découle du seuil minimal des frais mesuré ci-dessous et ne nécessite aucun modèle externe : chaque carte vendue à l'intérieur de celle-ci cède au moins deux centimes, sur des cartes dont le cours oscille entre trois et cinq, de sorte que chaque tour de manivelle rapporte moins que ce qui a été investi. Ce cercle vicieux détruit la valeur virtuelle et oblige à effectuer de nouvelles transactions, soumises à des frais, pour la remplacer. Aucun chiffre n'est avancé ici concernant l'ampleur de cette perte — le rendement par lot dépend des taux d’obtention des gemmes et des chances de gain dans les boosters, que cette étude n’a pas mesurés.\n\nCarte à collectionnerobjets obtenus dans un jeu dont on est propriétaire\n→\nPierres précieusescarte détruite, frais prélevés\n→\nPaquet de cartesgemmes utilisées pour la fabrication\n→\n3 nouvelles cartesvendu sur Market, frais prélevés\n↶\n\nSeuls les mécanismes sont présentés ici, et ce sont ceux propres à Valve : les cartes se transforment en gemmes, les gemmes permettent de fabriquer des boosters, les boosters donnent des cartes — chacun d’entre eux étant décrit dans la FAQ des cartes à collectionner Steam, et chaque étape constituant un événement de Marché imposable. Source des mécanismes de la boucle : Valve, Steam FAQ sur les cartes à collectionner ↗.\n\nCe n'est pas un simple phénomène passager. Il s'agit d'un secteur qui repose sur des fondements solides depuis plusieurs années.\n\nUn simple instantané pourrait n'être qu'un hasard. C'est pourquoi le répertoire public des « card-bots » a été consulté une fois par période de soldes saisonniers Steam, en remontant dans le temps grâce à Wayback Machine, de 2022 à 2026 — le stock que les bots proposaient, ainsi que les mêmes comptes, soldes après soldes. Cette économie n’apparaît pas pour disparaître aussitôt ; elle persiste, avec un noyau stable d’opérateurs, et a atteint un pic à plus de trois millions de lots complets en stock lors de la vente d'hiver 2023 — soit environ un tiers de million de clés TF2 de valeur conservées à un moment donné, dans un seul répertoire.\n\nSéries complètes de cartes disponibles dans le répertoire public des bots, en vente à Steam\n\nUn instantané Wayback de steam.supply/CardBots par vente saisonnière. Passez la souris dessus pour connaître la valeur en clés TF2 au taux de cet instantané.\n\n0.0M\n0.9M\n1.8M\n2.6M\n3.5M\nA’22\nS’23\nW’23\nS’24\nW’24\nS’25\nS’26\n401Nombre de comptes de bots distincts recensés dans l'ensemble des ventes\n59Présent dans au moins 5 des 7 ventes — le noyau stable\n16Présent à chacune des 7 ventes, de 2022 à 2026\n3,22 millionsNombre maximal d'ensembles en stock (hiver 2023) ≈ $570k–790k clés\nÀ quoi ressemble l'échelle des insignes de vente vue du haut ?\n\nLa demande correspond à l'offre. Du côté du public Échelle des badges des soldes d'été 2024 archivé 2026-07-16 ↗, le compte numéro un avait créé le badge de vente 1,740,645 fois — 1,74 million de jeux de dix cartes, 17,4 millions de cartes intégrés dans un seul motif décoratif. Au prix du marché pratiqué par le vendeur ($0.50 l'ensemble), cela représente ~$870,000 en termes de valeur des cartes ; si on les achète comme on le fait réellement — en échangeant des clés TF2 contre des bots pour monter de niveau, à raison d'environ 7,6 lots par clé —, cela revient à ~229,000 touches, environ $410,000–$570,000 en termes réels. Le compte numéro deux : 552,000 ensembles, ~$130,000–181,000. Personne ne joue pour cela. On l'achète, et chaque étape de l'achat correspond à une transaction que Valve compense.\n\nMéthode et limites : le stock total est calculé en additionnant les stocks de chaque bot répertorié dans chaque instantané ; le nombre Le nombre de bots par instantané n'est pas comparable d'une vente à l'autre, car certains instantanés ne montrent que les bots mis en avant tandis que d'autres affichent l'intégralité du répertoire ; le stock est donc considéré comme un seuil minimal de ce qui était visible, et non comme un recensement complet. Les valeurs des clés utilisent le taux médian de « sets » par clé annoncé pour chaque instantané et une clé TF2 comprise entre $1.79 et $2.49. La persistance est assurée par le SteamID64 d’un instantané à l’autre. Les instantanés de 2021 utilisaient une mise en page plus ancienne et ne sont pas inclus. Données : chronologie-de-l'économie-agricole.json; niveaux de badges issus de SteamLadder ; prix fixés par Steam Card Exchange (captures d'écran Wayback au moment de la vente, $0.05 par carte).\n\nEt cette même flotte est présente même lorsqu'il n'y a pas de promotion en cours\n\nLes deux photos ci-dessus ne représentent pas deux populations distinctes. Il s’agit d’une seule et même flotte, photographiée à différents moments. Le répertoire mentionné en haut de cette section a été lu sur un une journée ordinaire où aucune promotion saisonnière n'est en cours — 2026-09-22 — et même au repos, il restait 91 robots et 694,673 ensembles complets: de l'ordre de 186,000 touches TF2, $334,000–$464,000 de la valeur de la carte, inactives entre deux ventes. C'est le niveau minimum que l'activité maintient lorsqu'il ne se passe rien.\n\nEt il s'agit bien de la même opération. Identifiée par le SteamID64, 87 de ces 91 bots inactifs — 96% — apparaissent également dans les sept instantanés de vente ci-dessus, seize dans chacune d’entre elles. L’annuaire n’est pas un stand qui s’ouvre pour la vente et se referme ensuite ; il s’agit d’un inventaire commercial permanent que cette même flotte a fait grimper jusqu’à 3,22 millions d'unités au plus haut de l'hiver 2023 et ne descend jamais à zéro. Une promotion, c'est quand ça se vend. Ça existe aussi le reste de l'année.\n\nLe répertoire de stockage, bot par bot\n\nChaque carré représente un bot figurant dans le répertoire sur 2026-09-22 ; il est mis en évidence s'il apparaît également dans les sept instantanés de vente. Le chiffre 91 correspond à ce qui figurait dans l'annuaire ce jour-là, et non à la taille de la flotte. — 401 comptes distincts apparaissent dans les aperçus des ventes, et le répertoire présente un échantillon différent selon les jours.\n\nVu lors de ventes précédentes (87) Nouveautés depuis le dernier instantané (4)\n\nLa valeur de référence hors promotion est de 2026-09-22, extraite du même répertoire public, sans connexion. La valeur par défaut utilise le taux de « sets par clé » annoncé par chaque bot et la bande de clés $1.79–$2.49 ci-dessus. Le recoupement s’effectue par SteamID64 par rapport aux sept instantanés de soldes. Étant donné que la liste des produits en promotion diffère de la liste complète selon l’instantané, cette comparaison porte sur les stocks et l’identité, et non sur le nombre d’utilisateurs. Calculs dans section 08.\n\n03 — L'échelle\nL'autre élément est le numéro qui figure à côté de votre nom\n\nLes cartes constituent la matière première. Le produit fini correspond au niveau Steam, et Valve en fixe le prix par lot.\n\n100Steam Niveau\nNiveau cible — faites glisser ou utilisez les touches fléchées\nPrix d'un ensemble complet, en dollars américains\n\n$0.20 correspond à la collection complète la moins chère du recensement, $0.74 à la médiane et $1.70 à la moyenne. Ce chiffre ne concerne que les cartes — en aucun cas les déblocages $5.00 ni les licences de jeu.\n\n55,000XP requis\n550Ensembles complets consommés\n110Des jeux à posséder, à cultiver soi-même\n$407.00Prix des cartes à ce tarif\n1,100Allocations de réduction utilisées, minimum\n$5,500.00$5.00 se débloque si aucun compte n'est réutilisé\nEnsembles complets utilisés, niveau 1 à 1,000\n\nUne création de badge = un ensemble complet = 100 XP. Chaque niveau au sein d'une tranche de dix coûte 100 XP de plus que la tranche inférieure.\n\n0\n12,625\n25,250\n37,875\n50,500\n1\n250\n500\n750\n1000\n667\n550 sets\n\nUn niveau n'est pas une décoration que Valve laisse de côté. Il est intégré au compte. D'après la FAQ sur les cartes à collectionner de Valve, voici ce que vous apporte la création d'un badge : « 100 XP, ce qui pourrait faire passer votre niveau à Steam. » Si votre niveau Steam augmente, la limite du nombre de contacts dans votre liste d'amis sera augmentée de cinq., et vous pourrez peut-être débloquer la possibilité de personnaliser votre profil avec des vitrines. » Et à propos des paquets de cartes : « Votre niveau Steam augmente votre taux d'obtention de paquets de cartes : niveau 10 : +20%… niveau 50 : +100% d'augmentation de votre taux d'obtention (c'est-à-dire que le taux a doublé). »\n\nCe niveau détermine donc deux éléments Valve : le nombre d’amis que vous pouvez avoir et la vitesse à laquelle les cartes gratuites apparaissent dans votre inventaire. Ce deuxième paramètre est cumulatif : plus vous avez consommé de séries, plus la plateforme vous fournit rapidement du contenu. Valve a intégré cette boucle de réinvestissement au produit.\n\nLe taux de change est fixe et publié. La fabrication d'un insigne nécessite un ensemble complet et rapporte 100 XP ; « Vous pouvez créer un ensemble pour un même jeu cinq fois au maximum. » Le coût en XP par niveau augmente tous les dix niveaux. Il en résulte les chiffres suivants, qui ne sont en aucun cas des estimations :\n\nSteam Niveau\tEnsembles complets qu'il utilise\tLes jeux que vous devez posséder pour pouvoir les créer vous-même\tAu niveau le plus bas jamais enregistré ($0.20)\tAu niveau de la médiane ($0.74)\tÉchelle\n10\t10\t2\t$2.00\t$7.40\t\n50\t150\t30\t$30.00\t$111.00\t\n100\t550\t110\t$110.00\t$407.00\t\n200\t2,100\t420\t$420.00\t$1,554.00\t\n500\t12,750\t2,550\t$2,550.00\t$9,435.00\t\n667\t22,579\t4,516\t$4,515.80\t$16,708.46\t\n\n667 n'est pas une valeur hypothétique. Il s'agit du niveau le plus élevé qu'un bot figurant dans l'annuaire public indique pouvoir faire atteindre à un client, parmi les 33,359 ensembles qu'il détient dans 6,117 jeux. La quatrième colonne correspond au même barème de prix par rapport à l’ensemble complet le moins cher recensé ; la cinquième, par rapport à la médiane. Dans les deux cas, il s’agit des prix du marché pour les cartes seules, qui excluent totalement le déblocage $5.00 et les licences de jeu.\n\nComment la courbe a-t-elle été vérifiée, puisque Valve ne la publie pas ?\n\nValve indique le taux de badges (« Chaque tranche de 100 XP te fait gagner un niveau supplémentaire Steam ») puis il s'en couvre — « (du moins au début) » — sans publier l'augmentation. La courbe utilisée ci-dessus est la courbe standard, dans laquelle chaque niveau au sein d’un bloc de dix coûte 100 XP de plus que le bloc inférieur. Elle a été vérifiée par rapport au répertoire plutôt que supposée : pour chaque bot dont le maximum annoncé est limité par son stock plutôt que par le plafond de cinq objets par partie, le niveau calculé à partir de cette courbe correspond exactement au niveau annoncé par le bot — 541 contre 541, 494 contre 494, 464 contre 464. Lorsque le plafond s'applique, le chiffre calculé est légèrement supérieur de quelques niveaux, ce qui est normal pour un plafond qui dépend également de l'effectif disponible par match. Aucune affirmation n’est faite concernant la courbe au-delà du niveau 667.\n\nIl suffit de consulter l'échelle à côté de la section 02 pour se faire une idée de la structure de l'activité. Pour placer un compte au niveau 500, il faut assembler 12,750 ensembles complets. Chacun de ces ensembles a nécessité au moins deux quotas de drop de comptes, chacun de ces comptes ayant franchi la barre des $5.00 et chacun possédant le jeu. Un chiffre fantaisiste figurant en haut d'un profil repose sur au moins 25,500 allocations de gouttes dépensées situées en dessous. Valve ne perdra pas cette transaction. Valve est la contrepartie de chacune de ses composantes.\n\n04 — Les statistiques\nCette clause ne se contente pas de décrire l'agriculture de manière vague. Elle l'énumère.\n\nLe § 4.C n'est pas une disposition générale visant à lutter contre les bots. Les exemples qu'il énumère citent, l'un après l'autre, les deux éléments produits par une « carte farm ».\n\n« Vous ne devez en aucun cas utiliser des scripts, des bots, des macros ou tout autre système non contrôlé par un être humain (« automatisation ») pour interagir avec le Contenu et les Services sur Steam, de quelque manière que ce soit, y compris, mais sans s’y limiter :\n\nAutomatisation du processus de création de compte Steam,\nFalsification des statistiques de jeu (par exemple, gonflement du nombre de victoires ou de défaites, des points d’expérience ou du temps de jeu),\nObtenir des récompenses ou progresser sans contribution réelle de la part des utilisateurs,\n« Participer à des systèmes d'évaluation (tels que les évaluations par les pairs ou l'« Overwatch ») par des moyens automatisés, notamment en influençant les résultats ou en signalant des utilisateurs au moyen d'actions programmées plutôt que sur la base d'un jugement éclairé. »\n— Steam Contrat d'abonnement § 4.C ↗ archivé 2026-09-24 ↗ · extrait et cité mot pour mot 2026-09-22\n« …la récréation »\n\nLes heures d'inactivité ne sont pas des heures fantômes. La FAQ de l'ASF répond sans détour à cette question — « Pourquoi le temps de jeu des jeux obtenus via ASF n'augmente-t-il pas ? » — avec : « C'est vrai, mais pas en temps réel. Steam enregistre la durée de jeu à intervalles réguliers et programme la mise à jour en conséquence… En général, la mise à jour a lieu toutes les 30 minutes environ. »\n\nCes heures apparaissent dans les statistiques de Valve, sur les pages de la boutique de Valve et dans les chiffres relatifs au nombre de joueurs simultanés que Valve publie lui-même Steam Graphiques ↗ archivé 2026-09-23 ↗. Dans ces chiffres, un compte inactif est impossible à distinguer d'un compte actif. Les chiffres d'engagement communiqués par la plateforme sont calculés sur une population qui inclut, selon ses propres règles, des comptes qui ne sont pas actifs.\n\n« … sans véritable contribution des utilisateurs »\n\nIl s'agit d'une définition du « lâcher de carte inactive », rédigée par Valve. Elle définit également le niveau Steam, le badge, les conditions d'éligibilité aux boosters et les XP de profil qui y sont associés — la FAQ de l'ASF confirme cette interprétation. « permet de continuer à recevoir des boosters », car il se connecte de la même manière que le client officiel.\n\nAinsi, le système de récompense et l'acte interdit constituent un même mécanisme vu sous deux angles différents. Valve a conçu la récompense de manière à ce qu'elle soit générée par le temps plutôt que par la compétence, puis a rédigé une clause interdisant la production de récompenses par tout autre moyen que le temps passé par une personne.\n\n05 — Le piège de l'utilisation commerciale\nChaque sortie d'une carte « farmed » est une sortie interdite par la licence — et Valve perçoit un droit d'entrée à la sortie\n\nC'est là le problème que l'« exploitation responsable » ne permet pas de résoudre. La licence est destinée à un usage personnel et non commercial, et une carte ne devient intéressante à exploiter qu'à partir du moment où elle cesse d'être à usage personnel.\n\n§ 2.A — la licence\n\n« Valve vous accorde par la présente, et vous acceptez, une licence et un droit non exclusifs vous permettant d’utiliser le Contenu et les Services pour votre usage personnel et non commercial (sauf lorsque l'utilisation commerciale est expressément autorisée dans les présentes ou dans les Conditions d'abonnement applicables). »\n\n§ 2.G — la restriction\n\n« Vous n'avez pas le droit de : … (iii) exploiter le Contenu et les Services, ou l'une de leurs parties, à des fins commerciales, sauf autorisation expresse prévue ailleurs dans le présent Contrat (y compris dans les Conditions d'abonnement ou les Conditions d'utilisation). »\n\n§ 3.D — les frais\n\n«Valve peut prélever des frais sur les transactions effectuées sur une place de marché d’abonnements. « Les éventuels frais vous seront communiqués avant la finalisation de la transaction. »\n\nSi on lit ces trois éléments ensemble, le poste est pourvu.\n\nUne carte conservée n'a aucune valeur pour une ferme. Une carte vendue, échangée ou transformée en gemmes a servi à générer de la valeur — et Valve a précisé dans sa propre lettre de mise en demeure comment elle qualifie cette pratique : l'exploitant de 170 bots s'est vu signifier que son compte « a été utilisé pour collecter illégalement des cartes de collection sur Steam, ainsi que pour des activités connexes, et pas uniquement commerciales. » Dans ce cas-là, les cartes ont été mises sur le marché. Les ventes ont été conclues. La commission a été prélevée. L'interdiction est intervenue par la suite.\n\nLe prix d'entrée à cette porte n'est pas de 15%. Sur une carte « farmed », il atteint les deux tiers.\n\n§ 3.D Réserves « des frais ». Sur les cartes qu'une ferme produit réellement, ces frais sont bien loin des ~15% annoncés. Le Marché communautaire prélève un 5% Steam de frais de transaction et 10% de frais de jeu, chacun avec un seuil minimum de $0.01 (FAQ du Marché communautaire de Valve). Sur une carte proposée à un cent, ces étages sont le prix : l'acheteur paie trois centimes, dont deux correspondent à des frais. L'arrondi à l'unité inférieure transforme le chiffre affiché 15% en une taxe effective qui grimpe jusqu'à 66.7% c'est exactement là où se situe le marché des cartes : quelques centimes par carte.\n\nFrais effectifs sur une vente sur Community Market, calculés sur la base du prix demandé par le vendeur\n\n5% Steam + 10%, chacune valant au minimum $0.01. La bande ombrée correspond à la fourchette de prix réelle des échanges de cartes à collectionner — environ $0.03 à $0.05 par carte.\n\n0%\n10%\n20%\n30%\n40%\n50%\n60%\n70%\ncards\n$0.01\n$0.10\n$0.20\n$0.30\n$0.40\n$0.50\n66.7%\nLe vendeur souhaite\tSteam 5% (min $0.01)\tMatch 10% (min $0.01)\tFrais à la charge de l'acheteur\tFrais globaux\n$0.01\t$0.01\t$0.01\t$0.03\t66.7%\n$0.03\t$0.01\t$0.01\t$0.05\t40.0%\n$0.05\t$0.01\t$0.01\t$0.07\t28.6%\n$0.08\t$0.01\t$0.01\t$0.10\t20.0%\n$1.00\t$0.05\t$0.10\t$1.15\t13.0%\n\nLes frais de jeu de 10% reviennent à l’application qui a émis la carte ; le 5% revient à Valve, et sur les titres et les objets d’inventaire de base de Valve, la totalité des frais revient à Valve. Dans tous les cas, l’argent quitte le « farmer » : la vente d’une carte à trois centimes rapporte un centime et lui fait perdre deux. Multipliez cela par les centaines de milliers de ventes de cartes à moins de cinq centimes générées par un « farm » et « les frais que Valve peut facturer » C'est le modèle économique, pas une note de bas de page. Source : Steam FAQ sur le Marché communautaire — Frais ↗ archivé 2026-09-21 ↗, lire 2026-09-22 ; la courbe est arithmétique sur ces deux taux publiés et leurs planchers $0.01.\n\nAucune configuration de l’outil ne permet d’y échapper. Il peut être utilisé par une seule personne, sur un seul compte, avec une retenue parfaite — et dès l’instant où cette personne vend une seule carte obtenue par farming contre des fonds de portefeuille, la même sanction prévue au § 2.G s’applique à elle qu’à l’exploitant d’un compte de dix mille cartes. Valve s’est donc réservé le droit d’invoquer une violation à l’encontre de pratiquement tous les vendeurs de cartes sur son propre marché, mais a choisi de ne pas l’invoquer à leur encontre. Une règle appliquée à ce rythme n'est pas une règle. C'est une option. La question que soulève cette exposition n’est pas de savoir pourquoi les « card farmers » sont tolérés ; mais pourquoi cette même mesure est appliquée à un utilisateur isolé qui vend une carte, alors que l’économie commerciale des cartes que ces cartes alimentent — les services d’échange, les bots de progression, les vendeurs en gros — continue de fonctionner au grand jour, l’un de ses plus grands groupes étant modéré par un employé Valve (§ 08). La sanction est réservée au petit détenteur et ne s’applique pas à la machine.\n\n06 — Le bilan des mesures coercitives\nSans préavis, par vagues, et ça se propage le long de la liste des numéros de téléphone\n\nValve a inscrit cette faculté de résiliation sans préavis dans le contrat lui-même, juste après la clause relative à l'automatisation.\n\n« Valve peut restreindre ou résilier votre ou vos comptes ou un abonnement particulier en cas de comportement ou d’activité illégale, constituant une triche ou une automatisation, ou enfreignant les Steam règles de conduite en ligne. » Vous reconnaissez que Valve n'est pas tenu de vous adresser un préavis avant de résilier votre ou vos abonnements et/ou votre compte.«\n\n— Steam Contrat d'abonnement, § 4.D ↗ archivé 2026-09-24 ↗ · vérifié mot pour mot 2026-09-22\n\n1,000+ bots · interdiction de trading. « Il semblerait que ce compte ait été utilisé pour gérer un réseau de comptes de bots. L'utilisation de bots constitue une violation du Contrat d'abonnement Steam. »\n\nPlus de 170 bots · bannis définitivement, soldes d'hiver 2017. « Ce compte a été utilisé pour collecter illégalement des cartes à collectionner sur Steam, ainsi que pour mener des activités connexes, qui ne se limitaient pas au domaine commercial. Le compte a été définitivement bloqué et le service d'assistance Steam ne peut pas fournir d'aide supplémentaire à ce sujet. »\n\nPlus de 120 bots · bannis définitivement. « Ce compte, ainsi que d’autres, ont été utilisés pour saturer notre infrastructure réseau, ce qui constitue une violation des règles de conduite en ligne Steam. »\n\n— Steam Messages d'assistance reproduits dans la ArchiSteamFarm FAQ, section « Est-ce que quelqu'un s'est fait bannir pour ça ? ». Source ↗ · vérifié mot pour mot 2026-09-22\nCas n° 4 — Juin 2025, VAC interdictions concernant le CS2 mis hors service\n\nUn incident postérieur aux trois mentionnés ci-dessus a été consigné dans le système de suivi du projet : les comptes qui avaient simplement laissé Counter-Strike 2 en veille via cet outil ont reçu VAC interdictions — du type « anti-triche », et non du type « administratif ». Le responsable estime que le fait de rester inactif ne peut pas en provoquer un, puisque cela « ne fait rien d'autre que d'indiquer à Steam que nous jouons à tel ou tel jeu. » La cause de cette décision fait l'objet d'une controverse. En revanche, le fait que ces comptes aient été supprimés ne fait aucun doute.\n\n— ArchiSteamFarm discussion n° 3440, ouverte le 26 juin 2025 ↗ · lire 2026-09-22\n\nComment un compte principal disparaît\n\nDans le même fil de discussion, un collaborateur du projet décrit la règle de propagation : les comptes peuvent être bannis « par chaîne », s'ils utilisent le même numéro de téléphone — « Il pourrait s'agir simplement d'une interdiction VAC, étendue aux comptes « propres » liés à celui qui a été banni. »\n\nSteam Guard nécessite un numéro de téléphone. Les « fermes » sont créées à partir du numéro de téléphone de l’opérateur. Ainsi, la répression ne s’arrête pas aux comptes jetables : elle remonte la piste de l’identifiant partagé jusqu’au compte contenant la bibliothèque, la liste d’amis et l’inventaire. C’est le mécanisme décrit par un collaborateur du projet pour expliquer comment une seule action permet de supprimer le compte principal d’un opérateur ainsi que la ferme — et c’est pourquoi les pertes subies lors d’une vague de mesures de répression ne se mesurent pas en nombre de comptes $5. (Décrit par un contributeur du projet dans la discussion GitHub de l’ASF n° 3440 ; il n’existe aucune confirmation officielle Valve ni aucun précédent formel consigné.)\n\nLe même paragraphe, à cinq ans d'intervalle, rédigé par trois agents différents\n\nLa clause selon laquelle l'agriculture constitue une violation — à savoir l'utilisation commerciale d'une licence personnelle et non commerciale — ne s'applique pas uniquement aux exploitations agricoles. C'est le motif systématiquement invoqué par Steam lorsqu'il ferme un compte pour cause de commerce, et ce motif est fourni sous forme de modèle. Vous trouverez ci-dessous trois exemples, publiés par les personnes qui les ont reçus, à cinq ans d’intervalle, de la part de trois agents différents dont les noms sont mentionnés.\n\nMessage du service d'assistance Steam le 29 septembre à 19 h 56\n\n« Le compte sur lequel vous écrivez a été bloqué pour violation des conditions générales du contrat d'abonnement Steam. Il a été constaté que ce compte était utilisé à des fins commerciales, sur la base d'activités de trading, de signalements de la communauté et d'autres facteurs. »\n\nCe verrouillage est définitif et Steam Le service d'assistance ne peut pas vous aider davantage à ce sujet.\n\nComme nous vous avons fourni toutes les informations dont nous disposons, je clos cette demande d'aide. Veuillez noter que vous ne recevrez plus de réponses concernant ce problème.\n\nCordialement,\n« Hal »\n\nCette demande d'aide a été clôturée.\n29 septembre 2020. Publié par le destinataire avec le commentaire suivant : « Adieu, RIP Trading. » — @gergelyszabo94 ↗\nMessage du service d'assistance Steam le 12 juillet à 22 h 41\n\n« Le compte sur lequel vous écrivez a été verrouillé pour avoir enfreint les conditions du contrat d'abonnement Steam. Il a été établi que ce compte était utilisé à des fins commerciales, sur la base d'activités de trading, de signalements de la communauté et d'autres facteurs. »\n\nCe verrouillage est définitif et Steam Le service d'assistance ne peut pas vous aider davantage à ce sujet.\n\nComme nous vous avons fourni toutes les informations dont nous disposons, je clos cette demande d'aide. Veuillez noter que toute future demande d'aide concernant le verrouillage du compte pourra être clôturée sans réponse.\n\nSteam Assistance\n« Vido »\n\nCette demande d'aide a été clôturée.\n12 juillet 2024, interface en portugais. Le destinataire est un joueur professionnel de CS2 : « J'ai déjà contacté le service d'assistance de Steam, mais je ne reçois que des réponses automatiques… Je ne peux pas jouer à Faceit ni participer à des matchs professionnels. » — @prcs25 ↗ archivé 2024-07-15 ↗\nCité par le destinataire, r/steamsupport\n\n« Bonjour, le compte à partir duquel vous écrivez a été bloqué pour avoir enfreint les conditions du contrat d'abonnement Steam. Il a été établi que ce compte était utilisé à des fins commerciales, sur la base d'activités de trading, de signalements de la communauté et d'autres facteurs. »\n\nCe verrouillage est définitif et Steam Le service d'assistance ne peut pas vous aider davantage à ce sujet.\n\nComme nous vous avons fourni toutes les informations dont nous disposons, je clos cette demande d'aide. Veuillez noter que les futures demandes d'aide concernant le verrouillage du compte pourraient être clôturées sans réponse.\n\nSteam Assistance\n« Sally »\n\nReçu à trois reprises, suite à trois demandes distinctes.\n29 mars 2025. L'auteur ne contestait pas le verrouillage : son compte avait été piraté, tout comme son adresse e-mail, et il demandait à y avoir à nouveau accès : « Je ne pose pas de questions sur la suspension et je ne la conteste pas ; je veux simplement pouvoir accéder à mon compte Steam… Valve m'ont donné exactement cette réponse, copiée-collée à chaque demande, puis ont clôturé la demande. » — r/steamsupport ↗, figurant dans le corpus de plaintes propre à cette enquête\n\nMot pour mot, virgule pour virgule, sur cinquante-cinq mois, avec trois agents et deux langues d'interface. La seule modification apportée au corps du texte concerne la dernière phrase, où la période s'est précisée entre 2020 et 2024, passant de « Vous ne recevrez plus de réponses » à « Les futures demandes d'aide… pourraient être clôturées sans réponse. » Quel que soit le processus qui a conduit à ces décisions, la lettre n'en rend pas compte. Les motifs invoqués sont « les transactions, les signalements de la communauté et d'autres facteurs » : une catégorie, un rapport d'origine inconnue et un ensemble de facteurs non précisés.\n\nCinq autres cas, recueillis de la même manière. Les trois premiers relèvent de la même catégorie et aboutissent au même résultat ; les deux derniers concernent le même service, mais répondent à une règle différente, formulée dans les mêmes termes :\n\nDate\tCe qu'a fait ce compte\tQue s'est-il passé ?\tSource\n4 décembre 2021\tAcheter et vendre sur Buff — « Je n'ai rien fait d'autre que quelques achats et ventes sur Buff, c'est-à-dire des échanges entre particuliers. »\tInterdiction au sein de la communauté : pas de marché, pas d'échanges, stocks coûteux gelés\tr/csgomarketforum ↗ archivé 2025-03-27 ↗\n6 décembre 2021\tÉchanges P2P unidirectionnels via Buff et Bitskins pour des équipements et des échanges de matériel\tSerrure permanente à usage commercial et serrure collective : « Je suis bloqué en mode pseudo-invisible… Mon profil est également bloqué en mode privé »\tr/GlobalOffensiveTrade ↗ archivé 2021-12-06 ↗\n20 décembre 2024\tCompte détenu depuis 2017, des milliers d'heures de jeu ; échanges sur les places de marché communautaires pour obtenir des équipements thématiques et des améliorations\tVerrouillage définitif avec verrouillage communautaire, sans avertissement préalable ni avertissement écrit ; soutien « affirment que leur décision est définitive », les réponses sont automatisées\tr/csgomarketforum ↗ archivé 2025-06-27 ↗\n23 décembre 2024\tUn utilisateur qui revient sur le site recharge son portefeuille après une année d'absence, via un VPN « uniquement pour la sécurité générale sur Internet »\tExclusion définitive de la communauté avec aucune raison n'a été donnée: « L'interdiction est définitive et ils ne peuvent pas fournir d'autres informations ; de plus, d'autres tickets pourraient être clôturés sans réponse. » 196 votes positifs, 340 réponses\tr/steamsupport ↗\n4 août 2026\tDes années d'achats en Iran ; l'auteur affirme n'avoir jamais publié de message, n'avoir jamais utilisé la boutique ni les forums\tAccès à la communauté bloqué jusqu'en 2038 plus de « régions soumises à des sanctions »; dossier clôturé par un agent nommé Azul. Le remboursement de ce même compte, provenant de la même adresse IP iranienne, avait été approuvé un an plus tôt. La bibliothèque et l'argent restent à Valve.\tr/pcgaming ↗\n\nLa dernière ligne obéit à une règle différente des autres — il s'agit de conformité aux sanctions, et non d'utilisation commerciale — et elle est incluse car la structure de la réponse est identique : une catégorie, aucune preuve, aucun recours, un dossier clos. Elle soulève également une question que les autres ne posent pas. Si la gestion de ce compte était illégale, l'acceptation de ces années de paiements était elle aussi illégale. L’une de ces deux positions doit être erronée, et une seule d’entre elles a entraîné un coût pour le client.\n\nLes huit messages ont été consultés sur 2026-09-22 : les fils de discussion de 2021 et de décembre 2024 via des captures d’écran d’Internet Archive, et les autres via une interface publique de Reddit, car Reddit a refusé les demandes directes de l’hébergeur chargé de la collecte. Les deux messages de 2020 et 2024 ont été transcrits à partir des captures d’écran jointes aux publications originales, qui sont toujours en ligne. Aucun de ces comptes n’est présumé innocent ou coupable de quoi que ce soit dans le cadre de cette enquête — c’est précisément là où réside tout l’intérêt. Ni le lecteur, ni l'autorité de régulation ne peuvent en déduire quoi que ce soit à la lecture de cette lettre.\n\nRemarque concernant l'approvisionnement — pertes au niveau des opérateurs\n\nLes opérateurs interrogés dans le cadre de cette enquête font état de pertes de l'ordre de entre cinq mille et dix mille comptes chacun dans le cadre d'opérations ponctuelles de contrôle, les principaux comptes étant vérifiés en même temps que l'exploitation agricole. Cette enquête est consignée ici à titre de compte rendu de première main, et non comme une conclusion. Aucune taille d'échantillon n'est publiée, aucune date de collecte n'est fixée et aucune vérification par compte n'est effectuée ; aucun autre chiffre de cette page n'en dépend ; les deux lignes de la section 02 qui s'appuient sur ce chiffre sont signalées comme telles.\n\nCette affirmation est clairement énoncée, et non pas simplement évoquée, pour deux raisons. Le mécanisme d’interdiction en cascade décrit ci-dessus constitue l’explication documentée de ce phénomène précis. Et une autorité de régulation peut exiger de Valve le seul élément qui permettrait de trancher : combien de comptes ont fait l’objet d’une automatisation, au cours de quelles vagues, et combien chacun de ces comptes avait dépensé dans le magasin avant sa fermeture. Tant que cet élément n’existe pas, le chiffre reste tel quel — rapporté, attribué et non prouvé.\n\n07 — L'asymétrie\nLes deux côtés du même bureau\n\nComparez ce niveau de preuve à celui Valve appliqué à sa propre opération de soutien. La colonne de droite correspond au registre des incidents de ce dossier, reproduit tel quel, avec les réserves qui y figurent.\n\nUn client, à des fins de trading\n\nHuit cas recensés, 2020-2026\n\nComportement\nVente ou achat d'articles sur des plateformes tierces ; dans un cas précis, il ne s'agissait d'aucun acte délictueux : le compte avait été piraté.\nÉléments de preuve présentés\nAucun. « Sur la base des transactions, des signalements de la communauté et d'autres facteurs. »\nAvis\nAucune. Valve a précisé au § 4.D : « Valve n’est pas tenu de vous adresser un préavis avant de mettre fin au contrat. »\nAppel\n« Ce verrouillage est définitif et Steam Le service d'assistance ne peut pas vous aider davantage à ce sujet. »\nBillet\nAffaire classée après la première réponse. Demandes supplémentaires « peut être clôturé sans réponse. »\nPortée\nProfil, liste d'amis, chat, Market, inventaire et tous les objets achetés avec de l'argent réel.\nDurée\nPermanent.\nUne flotte de bots automatisés, pour le volume\n\n694,673 ensembles complets disponibles en stock public répartis sur 91 robots\n\nComportement\nExécuter simultanément des scripts automatisés en mode « headless » sur des milliers de comptes afin de mettre des cartes en attente, de créer en masse des badges et d'échanger des séries à une échelle industrielle.\nÉléments de preuve présentés\nDes répertoires de bots accessibles à tous (steam.supply, SteamLvlUp) et des groupes publics comptant des millions de membres.\nAvis\nAucune intervention. 88.97% ne font l'objet d'aucune interdiction d'aucune sorte; 99.8% des interdictions restantes sont purement esthétiques.\nAppel\nCe n'est pas nécessaire. Les flottes fonctionnent en continu tout au long de leur cycle de vie, qui s'étend sur plusieurs années, sans aucune interruption.\nBillet\n—\nPortée\nÉchange d'inventaire sans restriction, progression des badges et liquidité du marché.\nAvantage de Valve\n$26.8M+ en montant minimum d'achats en magasin ($5.00 seuil d'accès par compte) plus 15% réduction sur les transactions effectuées sur le Marché communautaire.\nLa question qui se pose alors, pour le dire simplement\n\nTout client qui effectue manuellement des échanges de cartes ou d’objets s’expose à une exclusion définitive et sans possibilité de recours en vertu de l’article 4.C (automatisation) ou de l’article 2.G (utilisation commerciale). Un réseau automatisé de farming utilisant des bots sans interface utilisateur sur des milliers de comptes opère ouvertement avec un taux d’intégrité de 88.97%. Valve en bénéficie à la fois.\n\nL'asymétrie est d'ordre économique : les traders individuels tirent profit de la plateforme, tandis que les flottes de cartes automatisées injectent des millions dans le système de paiement de Valve ($5.00 par compte) et alimentent les frais de transaction à chaque revente. L'application des règles ne suit pas le règlement écrit ; elle suit le modèle économique.\n\n08 — Gouvernance\nQui régit le système économique des cartes ?\n\nLa conclusion récurrente de ce dossier — à savoir que la couche tierce entourant Steam est constituée de personnel issu de Steam — vaut également pour l’économie des cartes, et elle aboutit à une conclusion précise : personne d’indépendant ne peut évaluer l’impact réel des mesures coercitives de Valve, car la partie en mesure de le faire se trouve au sein même de cette couche. Tous les faits présentés ci-dessous ont été extraits du groupe public et des pages de profil de Valve sur 2026-09-22 et peuvent être reproduits par n’importe qui dans un navigateur.\n\nUn employé Valve anime le plus grand groupe dédié à l'échange de cartes Valve employé\n\nCardTrades ↗ se présente, dans son en-tête, comme le « Steam Groupe officiel d'échange de cartes » et comporte 97,114 membres. Ses modérateurs répertoriés — les comptes qui gèrent ce groupe — sont Mickmane, SgtFopper et afarnsworth ↗.\n\nCe dernier profil est identifié par le balisage du site de Valve comme étant celui d'un employé Valve — la page indique class=\"profile_header_valve_employee\" — indique que son emplacement est le suivant : Bellevue, dans l'État de Washington, et appartient à la Valve, Steam et Steam Groupe « Cartes à collectionner » groupes. SteamID64 76561197960434622, membre depuis le 12 septembre 2003.\n\nCette remarque est d'ordre structurel, et non personnel, et elle est pas Un point concernant l'automatisation : le modérateur d'un groupe dédié à l'échange de cartes n'utilise pas de bot, et rien ici ne laisse penser le contraire. Le problème réside dans la clause figurant dans section 07. Steam Card Exchange est un service tiers de cartes commerciales ; l'échange de cartes via des services tiers constitue précisément le comportement pour lequel Valve procède au verrouillage définitif des comptes ordinaires en vertu de « utilisées à des fins commerciales sur la base des transactions, des rapports de la communauté et d'autres facteurs. » Un employé Valve occupe un poste de modérateur officiel au sein du groupe communautaire officiel de ce service, qui compte 97 000 membres.\n\nAucune allégation d'acte répréhensible n'est formulée à l'encontre d'une quelconque personne dans le présent document, et aucune conclusion n'est tirée quant à la nature de ce rôle. C'est cette asymétrie qui constitue le constat : lorsqu’un compte ordinaire fait appel à un service tiers de carte ou de « skin », la réponse se traduit par la clôture du ticket et un blocage définitif sans qu’aucune preuve ne soit fournie ; lorsque le service en question est celui-ci, un employé Valve figure sur la liste des modérateurs et cet arrangement est visible sur une page Valve publiée par le service lui-même. Ce qui est demandé, c’est ce qui est demandé partout ailleurs dans ce dossier : produire l’autorisation écrite, si elle existe — et si aucune n’est nécessaire, le dire par écrit, car huit personnes de la section 06 se sont vu dire le contraire.\n\nLa liste des comptes bannis et la personne qui la gère Modérateur bénévoleService tiers\n\nLe groupe Steambans.com (archivé) ↗ (en direct ↗ archivé 2025-12-03 ↗) retrace son histoire dans la description de son groupe qui a été conservée : « Le groupe communautaire officiel de Steambans.com Steam. SteamBans.com est un tout nouveau service reposant sur un concept bien connu. Les listes d’exclusion mondiales existent depuis des années sur l’ancien programme WONID de VALVe. Lorsque le passage à STEAMID s’est imposé, il nous a semblé naturel de développer un service spécialement adapté à ce nouveau système. Mais nous voulions aller plus loin. *. Page d’archives pour Steambans, qui a fermé ses portes en 2013. » Parmi ses administrateurs figurent notamment devicenull et killahinstinct_ ↗.\n\nCe compte administrateur est pas un Valve employé — il n'est pas identifié comme tel. Il s'agit d'un bénévole jouissant d'un statut particulièrement élevé : un membre de Modérateurs de la communauté (414 membres, décrit comme un groupe « créé par les modérateurs de la communauté de Steam »), de Coordinateurs du wiki, de Steam Marché communautaire, ainsi que des groupes liés au programme Valve et aux avant-premières, notamment Valve Pipeline, Steam Version bêta pour les clients, Auth Mobile (version bêta), Nouvelle version bêta communautaire Steam, Steam Laboratoires, Steamworks et Signaler des URL frauduleuses. SteamID64 76561197960794555.\n\nÉgalement à l'intérieur de ce cercle et affichant les Steambans directement dans la liste des membres de son groupe public : msart ↗ (liste des groupes ↗), SteamID64 76561197977933359, dont le profil indique, selon ses propres termes : « Je gère steamid.uk ainsi que de nombreux autres sites liés ou non à Steam. », et qui gère un réseau regroupant seize groupes — SteamIDcouk (groupe principal « Site web de Sid »), SidAdmins, SidBans, steamideu, Steam3ID, s-id et SArchive parmi eux.\n\nsteamid.uk indique lui-même ce chiffre. Voici ce qu'on peut lire dans sa FAQ : « Qui a créé SteamID ? Le site web SteamID, l'infrastructure réseau et les systèmes de sécurité sont tous gérés par 76561197977933359. » Deux réponses plus bas, on précise d'où proviennent ces données : « SteamID utilise principalement l'API Web Steam pour la collecte de données. » Cette même page décrit plusieurs serveurs dédiés hébergés chez différents fournisseurs, des serveurs de développement, de stockage et de recherche de texte hébergés hors site, ainsi qu'une infrastructure de sauvegarde distincte.\n\nVérifié grâce aux archives conservées par Internet Archive : le Aperçu du groupe Steambans au 3 décembre 2025 ↗, le Aperçu du profil de l'opérateur au 14 septembre 2024 ↗, et le Aperçu de la FAQ de steamid.uk au 1er avril 2026 ↗, données correspondantes lues directement sur 2026-09-22.\n\nCe que cela signifie, et ce que cela ne signifie pas\n\nLes listes d'exclusion, la résolution des SteamID et l'échange de cartes sont les trois services qui déterminent qui est digne de confiance, qui est identifiable et quelle est la valeur d'un objet. Aucun de ces trois services n'est géré par Valve. Dans chacun d'entre eux, les personnes aux commandes provenaient de l'orbite de Valve : un employé signalé Valve figurant sur la liste des modérateurs du groupe officiel du service de cartes ; un modérateur de communauté de longue date Valve, disposant d’un accès au programme en avant-première et gérant le groupe de la liste des comptes bannis ; le service de résolution d’identité géré par un particulier faisant partie du même cercle. Trois services, trois interfaces de contrôle, trois personnes Valve auxquelles on avait déjà accordé un statut officiel.\n\nL'appartenance à un groupe ne constitue pas un emploi, et rien de tout cela ne constitue une accusation. C'est un fait de gouvernance, et c'est la raison pour laquelle l'argument habituel — Ce sont des tiers, nous n'avons aucun contrôle sur eux — doit être vérifié plutôt qu’accepté. Les personnes aux commandes connaissent bien Valve. Valve est le seul à pouvoir dire ce qu’il leur a demandé, le cas échéant ; personne à l’extérieur n’est en mesure de le savoir.\n\nPersonne ne compte. Telle est la conclusion.\n\nL’espace d’identification Steam correspond à une plage d’entiers contigus. Parcourir cette plage et recenser le nombre de comptes bannis, le nombre de comptes restreints et le volume de stock concerné par une interdiction de transaction ne constitue pas un programme de recherche : il s’agit simplement d’une boucle et d’une clé API. Valve fournit lui-même cette clé, à l’adresse steamcommunity.com/dev/apikey. Et pourtant Aucun organisme indépendant ne publie ce recensement. Ni autorité de régulation, ni journaliste, ni universitaire, ni association de consommateurs. Les seuls chiffres publics concernant l'ampleur des mesures de contrôle sur Steam sont ceux que Valve choisit de mentionner.\n\nCette fonctionnalité n'est pas absente. Elle est simplement mise en attente. Le service qui gère et indexe l'espace d'identifiants à grande échelle — steamid.uk — indique dans sa propre FAQ qu'il « utilise principalement l'API Web Steam pour la collecte de données » et l'exploite sur plusieurs serveurs dédiés, des systèmes de stockage hors site, des machines de recherche textuelle et un centre de sauvegarde distinct. Il est géré par un particulier. Le groupe de frères et sœurs de sa liste d’exclusion est co-administré par un modérateur de longue date de la communauté Valve ayant accès aux programmes en préversion de Valve. La seule partie en mesure de publier le décompte se trouve dans l'orbite de Valve, mais ne le publie pas.\n\nC'est exactement la même configuration que l'on retrouve partout ailleurs dans ce dossier. Chaque service chargé de prendre des décisions déterminantes concernant l'économie Steam — qui est digne de confiance, qui est identifiable, quelle est la valeur d'un bien, qui est banni — est, en théorie, un tiers, mais, dans la pratique, il est étroitement lié à Valve. Steam « Card Exchange » ne fait pas exception à cette règle ; il s'agit d'un autre exemple de ce phénomène. L'argument selon lequel il s'agit d'opérateurs indépendants peut être avancé pour Valve précisément parce que personne n'a jamais pu le vérifier à l'aide d'un nombre.\n\nRecensement des 10,88 millions de comptes : 88.97% Non modifié\n\nLe parc d'installations ArchiSteamFarm a fait l'objet d'un audit sur l'ensemble des Valve GetPlayerBans point final (10,880,610 comptes, 55 minutes). Le sous-ensemble non limité représente à lui seul $26.8M+ en montant minimum d'achat en magasin (seuil d'entrée de $5.00). Les comptes « 9,680,599 » (88.97%) ne font l'objet d'aucune restriction d'aucune sorte, et 99.8% des autres ne prévoient que des interdictions communautaires purement symboliques qui laissent le trading automatisé en place.\n\n5,360,499Membres ASF sans restriction (nombre affiché de Steam)\n10,880,610Nombre total d'entrées API analysées (limitées + non limitées)\n9,680,599Jamais banni (88.97%)\n1,200,011Appliquer une interdiction de Steam (11.0%) — 99.8% cosmétique\n55 minPour recenser l'ensemble de la population, un élément clé\nPreuves médico-légales et recensement approfondi\n\nLa répartition démographique détaillée — comprenant notamment des graphiques illustrant la répartition par type d'interdiction, l'ancienneté des comptes au moment de l'application de la mesure, les tranches d'années de création (2020-2026) et les données géographiques fournies par les utilisateurs eux-mêmes — est publiée dans l'étude consacrée au recensement.\n\nOuvrir le recensement complet des interdictions (10,88 Mo) (pièce VI) →Section 4 — Le black-out de l'identifiant d'actif →\n\nLa question qu'il faut donc poser, et à laquelle seul Valve peut répondre, est la suivante : quel identifiant ou quelle capacité a été retiré(e), à quelle date, sur décision de qui, et quel effet mesurable cela a-t-il eu sur les opérateurs concernés ? — par rapport à ses répercussions sur toutes les personnes à l'extérieur qui tentaient de compter. Une modification mettant fin à l'audit indépendant ne devient pas neutre sous prétexte qu'elle a été annoncée comme une mesure de sécurité. C'est la raison pour laquelle le recensement mentionné dans le paragraphe ci-dessus n'existe pas.\n\n09 — Méthode et limites\nCe qui a été lu, et ce qui n'est pas revendiqué\n\nToutes les citations figurant sur cette page ont été extraites de la source en ligne sur 2026-09-22 et reproduites mot pour mot. Aucune d'entre elles ne provient d'un scraping, d'identifiants de marché ou d'un ensemble de données privé.\n\nLes quatre ensembles de données et les calculs effectués sur ceux-ci\n\nChacune correspond à une requête publique unique, reproductible depuis un terminal. Aucun compte n'a été utilisé, aucune connexion à une place de marché n'a été établie et aucun point de terminaison nécessitant des identifiants n'a été appelé.\n\nEnsemble de données\tD'où cela vient-il ?\tQu'est-ce qui en a été déduit ?\nRecensement des cartes\n13,876 matchs\tSteam La liste des prix des badges publiée par Card Exchange, le même flux qui permet d'afficher leurs page des prix publique ↗ archivé 2026-08-04 ↗\tJeux émettant des cartes, nombre de cartes par série, types de cartes distincts et prix du marché de chaque série complète. Les médianes et le total $23,586.57 constituent les données arithmétiques de cette étude.\nPrix des jeux\n13,713 résolu\tle point de terminaison de la boutique publique de Valve, store.steampowered.com/api/appdetails, cc=us, champ « prix » uniquement, par lots\tMédiane et répartition du prix catalogue d'un jeu de cartes ; nombre de jeux dont la vente de la collection complète dépasse celle du jeu lui-même.\nStock de bots\n91 bots, 694,673 ensembles\tLe répertoire public des « card-bot » disponible à l'adresse steam.supply/CardBots ↗, tel qu'affiché, sans connexion\tNombre total de sets en stock, nombre minimum de cartes, seuil minimal de perte autorisé et seuil minimal de répartition par bot sur des comptes distincts.\nVérification croisée\n21 bots partagés\tsteamlvlup.net/cardbots ↗ archivé 2026-02-10 ↗, un annuaire indépendant regroupant ces mêmes bots\tÀ titre de vérification uniquement. Sur les 21 bots figurant dans les deux listes, Aggregate Stock accepte de 0.03%; l'écart le plus important entre deux robots est de 1.36%, ce qui correspond à deux collectes de données d'inventaire en temps réel effectuées à quelques minutes d'intervalle.\n\nMention obligatoire, comme l'exige le deuxième répertoire : données fournies par SteamLvlUp, sous licence CC BY 4.0 archivé 2026-09-23 ↗; utilisées ici uniquement à titre de vérification indépendante des chiffres de stock fournis par un tiers, et modifiées en ce sens que les lignes par robot ont été agrégées et comparées plutôt que reproduites. Steam Card Exchange et steam.supply sont mentionnés ci-dessus par un lien. Les prix des jeux sont ceux de Valve. Les noms et images des cartes, des jeux et des coffrets appartiennent à Valve ou aux éditeurs ; ils sont reproduits sans revendication ni licence, à titre d’informations factuelles sur le marché.\n\nDeux mesures prévues n'ont pas été effectuées et n'ont pas été remplacées. Les critères d'évaluation propres au « Community Market » de Steam — aperçu des prix, recherche/affichage, historique des prix — ne renvoient aucune information à l'hôte collecteur, tandis que Steam les pages de discussion de la communauté lui renvoient un code HTTP 403 ; par conséquent, aucun chiffre figurant sur cette page n'est issu des données en temps réel du Marché. La méthode de calcul du volume de ventes, qui aurait permis de comptabiliser les cartes obtenues lors de la réinitialisation quotidienne, nécessite une session Steam connectée ; Le rapport d'enquête indique qu'aucun identifiant de la place de marché n'a été utilisé, et cette affirmation a été retenue. Le plancher « bot-stock » correspond à ce qui peut être mesuré sans bot.\n\nSources primaires\n\nSteam Contrat d'abonnement ↗ archivé 2026-09-24 ↗ — § 2.A, § 2.G, § 3.D, § 4.C, § 4.D.\nSteam Assistance — Comptes utilisateur limités ↗ — le seuil $5.00 et la liste des fonctionnalités restreintes.\nValve — Steam FAQ sur les cartes à collectionner ↗ — les mécanismes de « drop » et le modèle free-to-play $9.\nArchiSteamFarm FAQ ↗ et discussion n° 3440 ↗.\nSteam Pages des groupes et des profils communautaires, à consulter directement, pour la section 08.\nFAQ de steamid.uk, instantané d'Internet Archive 2026-04-01 ↗.\nHuit Steam avis de blocage de l'assistance publiés par leurs destinataires, 2020-2026, répertoriés avec leurs liens dans la section 06.\n\nCe qui n'est pas revendiqué\n\nAucun chiffre d'affaires n'est estimé pour Valve issu de la « card farming ». Aucun nombre de comptes actifs n'est avancé pour aucun outil, et les 1,39 million d'allocations de drop sont pas un décompte des comptes appartenant à des exploitations agricoles — voir la note de la section 02. Aucune personne n’est accusée d’actes répréhensibles ; lorsqu’une personne est citée, c’est sous son pseudonyme public Steam, dans le cadre de sa fonction publique, à partir d’une page publiée par Valve. Aucun des huit comptes verrouillés mentionnés dans la section 06 n’est déclaré innocent ou coupable ; la conclusion porte sur la lettre, et non sur le compte. Les chiffres relatifs aux pertes subies par les opérateurs, figurant dans la section 02, proviennent de déclarations des parties concernées et sont indiqués comme tels à la note d'approvisionnement. La FAQ de steamid.uk est tirée d'un instantané d'Internet Archive, car la page en ligne est protégée par un test anti-bot. Nous n'affirmons en aucun cas qu'un recensement des bannissements a été tenté puis supprimé — nous constatons simplement qu'aucun n'a été publié. La courbe de niveau Steam au-delà de 667 n'est pas modélisée.\n\nPourquoi l'outil n'est pas le sujet\n\nArchiSteamFarm précise que « n'est pas autorisé par Valve » et rien ne lui est reproché sur cette page. Elle sert d’instrument de mesure, car c’est la seule entité de cette économie qui documente publiquement et par écrit les mécanismes en jeu. Valve peut résumer l’ensemble de la présentation en un seul paragraphe : publier quelles automatisations commerciales elle autorise, ainsi que le relevé par opérateur de ce qu’elle a fait concernant le reste.\n\nÀ lire ensuite : comment le marché lui-même est évalué → · l'échelle des prix et le plafond des annonces → · les articles Steam ne seront pas livrés →",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Une ferme de bots n'est pas une fuite dans la boutique de Valve. C'est une client."
          },
          {
            "level": 2,
            "id": null,
            "text": "Qu'est-ce qu'une ferme, en détail ?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Acheter à"
          },
          {
            "level": 3,
            "id": null,
            "text": "Acheter des jeux"
          },
          {
            "level": 3,
            "id": null,
            "text": "Inactif\nL'outil connecte le compte au réseau Steam en mode sans interface graphique, « analyse vos badges », génère la liste des titres pouvant faire l'objet d'une exploitation et lance « Jouer à un jeu éligible et vérifier régulièrement si le jeu a déjà été entièrement « farmé ». » Description du mécanisme par son responsable : il « ne fait rien d'autre que d'indiquer à Steam que nous jouons à tel ou tel jeu. »"
          },
          {
            "level": 3,
            "id": null,
            "text": "Les gouttes s'épuisent\nChaque titre est fini. « Chaque jeu comporte un nombre fixe de cartes à obtenir. Une fois que vous les avez toutes obtenues (environ la moitié du set complet), le jeu ne vaut plus la peine d'être farmé. » Une exploitation agricole qui souhaite continuer à produire doit continuer à acheter des cartes. L'approvisionnement en cartes est limité par les achats — c'est voulu, et cela joue en faveur de Valve."
          },
          {
            "level": 3,
            "id": null,
            "text": "Retrait\nLa carte quitte le jeu par l'une des trois voies suivantes : elle est vendue sur le Marché communautaire, échangée ou transformée en gemmes. Chacune de ces opérations correspond à une transaction sur la Place de marché des abonnés ou à un échange, et le § 3.D prévoit les frais suivants : « Valve peut facturer des frais pour les transactions effectuées sur une place de marché d'abonnements. » C'est cette étape qui fait de tout cela une violation — voir 05."
          },
          {
            "level": 2,
            "id": null,
            "text": "Avant même qu'une exploitation agricole ne gagne un centime, elle a déjà dépensé Valve"
          },
          {
            "level": 3,
            "id": null,
            "text": "Quelle est la taille réelle de l'objet acheté ?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Quelle est la taille d'un ensemble ?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Combien coûte la licence ?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ce que renvoie l'ensemble final"
          },
          {
            "level": 3,
            "id": null,
            "text": "Où se trouvent les ensembles 694,673"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ce que ce sol dit et ne dit pas"
          },
          {
            "level": 3,
            "id": null,
            "text": "Et l'agriculture n'est pas rentable aux prix pratiqués par Valve"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ce que la ferme soutient réellement"
          },
          {
            "level": 4,
            "id": null,
            "text": "Ventes de jeux vidéo"
          },
          {
            "level": 4,
            "id": null,
            "text": "« En ligne » et temps de jeu"
          },
          {
            "level": 4,
            "id": null,
            "text": "Inscriptions"
          },
          {
            "level": 4,
            "id": null,
            "text": "Argent sur le portefeuille et frais"
          },
          {
            "level": 4,
            "id": null,
            "text": "Relations publiques de niveau 0"
          },
          {
            "level": 3,
            "id": null,
            "text": "Et le retrait lui-même entraîne une perte de valeur : Valve, car il est imposé deux fois"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ce n'est pas un simple phénomène passager. Il s'agit d'un secteur qui repose sur des fondements solides depuis plusieurs années."
          },
          {
            "level": 3,
            "id": null,
            "text": "Séries complètes de cartes disponibles dans le répertoire public des bots, en vente à Steam"
          },
          {
            "level": 3,
            "id": null,
            "text": "À quoi ressemble l'échelle des insignes de vente vue du haut ?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Et cette même flotte est présente même lorsqu'il n'y a pas de promotion en cours"
          },
          {
            "level": 3,
            "id": null,
            "text": "Le répertoire de stockage, bot par bot"
          },
          {
            "level": 2,
            "id": null,
            "text": "L'autre élément est le numéro qui figure à côté de votre nom"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ensembles complets utilisés, niveau 1 à 1,000"
          },
          {
            "level": 3,
            "id": null,
            "text": "Comment la courbe a-t-elle été vérifiée, puisque Valve ne la publie pas ?"
          },
          {
            "level": 2,
            "id": null,
            "text": "Cette clause ne se contente pas de décrire l'agriculture de manière vague. Elle l'énumère."
          },
          {
            "level": 3,
            "id": null,
            "text": "« …la récréation »"
          },
          {
            "level": 3,
            "id": null,
            "text": "« … sans véritable contribution des utilisateurs »"
          },
          {
            "level": 2,
            "id": null,
            "text": "Chaque sortie d'une carte « farmed » est une sortie interdite par la licence — et Valve perçoit un droit d'entrée à la sortie"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 2.A — la licence"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 2.G — la restriction"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 3.D — les frais"
          },
          {
            "level": 3,
            "id": null,
            "text": "Si on lit ces trois éléments ensemble, le poste est pourvu."
          },
          {
            "level": 3,
            "id": "fee-ladder",
            "text": "Le prix d'entrée à cette porte n'est pas de 15%. Sur une carte « farmed », il atteint les deux tiers."
          },
          {
            "level": 3,
            "id": null,
            "text": "Frais effectifs sur une vente sur Community Market, calculés sur la base du prix demandé par le vendeur"
          },
          {
            "level": 2,
            "id": null,
            "text": "Sans préavis, par vagues, et ça se propage le long de la liste des numéros de téléphone"
          },
          {
            "level": 3,
            "id": null,
            "text": "Cas n° 4 — Juin 2025, VAC interdictions concernant le CS2 mis hors service"
          },
          {
            "level": 3,
            "id": null,
            "text": "Comment un compte principal disparaît"
          },
          {
            "level": 3,
            "id": null,
            "text": "Le même paragraphe, à cinq ans d'intervalle, rédigé par trois agents différents"
          },
          {
            "level": 3,
            "id": null,
            "text": "Remarque concernant l'approvisionnement — pertes au niveau des opérateurs"
          },
          {
            "level": 2,
            "id": null,
            "text": "Les deux côtés du même bureau"
          },
          {
            "level": 3,
            "id": null,
            "text": "Un client, à des fins de trading"
          },
          {
            "level": 3,
            "id": null,
            "text": "Une flotte de bots automatisés, pour le volume"
          },
          {
            "level": 3,
            "id": null,
            "text": "La question qui se pose alors, pour le dire simplement"
          },
          {
            "level": 2,
            "id": null,
            "text": "Qui régit le système économique des cartes ?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Un employé Valve anime le plus grand groupe dédié à l'échange de cartes Valve employé"
          },
          {
            "level": 3,
            "id": null,
            "text": "La liste des comptes bannis et la personne qui la gère Modérateur bénévole Service tiers"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ce que cela signifie, et ce que cela ne signifie pas"
          },
          {
            "level": 3,
            "id": null,
            "text": "Personne ne compte. Telle est la conclusion."
          },
          {
            "level": 3,
            "id": null,
            "text": "Recensement des 10,88 millions de comptes : 88.97% Non modifié"
          },
          {
            "level": 3,
            "id": null,
            "text": "Preuves médico-légales et recensement approfondi"
          },
          {
            "level": 2,
            "id": null,
            "text": "Ce qui a été lu, et ce qui n'est pas revendiqué"
          },
          {
            "level": 3,
            "id": null,
            "text": "Les quatre ensembles de données et les calculs effectués sur ceux-ci"
          },
          {
            "level": 3,
            "id": null,
            "text": "Sources primaires"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ce qui n'est pas revendiqué"
          },
          {
            "level": 3,
            "id": null,
            "text": "Pourquoi l'outil n'est pas le sujet"
          }
        ],
        "links": [
          "https://help.steampowered.com/en/faqs/view/71D3-35C2-AD96-AA3A",
          "https://github.com/JustArchiNET/ArchiSteamFarm/wiki/FAQ",
          "https://steamcommunity.com/tradingcards/faq/",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260924114457/https://store.steampowered.com/subscriber_agreement/",
          "https://steamladder.com/ladder/badges/2861690/",
          "http://web.archive.org/web/20260716205303/https://steamladder.com/ladder/badges/2861690/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/farm-economy-timeline.json",
          "https://store.steampowered.com/charts/",
          "http://web.archive.org/web/20260923183013/https://store.steampowered.com/charts/",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://github.com/JustArchiNET/ArchiSteamFarm/discussions/3440",
          "https://x.com/gergelyszabo94/status/1311004678633795585",
          "https://x.com/prcs25/status/1811893857253982720",
          "http://web.archive.org/web/20240715122902/https://x.com/prcs25/status/1811893857253982720",
          "https://reddit.com/r/steamsupport/comments/1fjmgc5/what_to_do_when_your_steam_account_gets_hacked/mkelm2y/",
          "https://www.reddit.com/r/csgomarketforum/comments/r87owv/psa_my_steam_account_just_got_banned/",
          "http://web.archive.org/web/20250327203008/https://www.reddit.com/r/csgomarketforum/comments/r87owv/psa_my_steam_account_just_got_banned/",
          "https://www.reddit.com/r/GlobalOffensiveTrade/comments/r9xql9/d_recently_received_commercial_ban_for_what_seems/",
          "http://web.archive.org/web/20211206034804/https://www.reddit.com/r/GlobalOffensiveTrade/comments/r9xql9/d_recently_received_commercial_ban_for_what_seems/",
          "https://www.reddit.com/r/csgomarketforum/comments/1hhxx7m/d_permanently_locked_on_steam_for_commercial_use/",
          "http://web.archive.org/web/20250627014045/https://www.reddit.com/r/csgomarketforum/comments/1hhxx7m/d_permanently_locked_on_steam_for_commercial_use/",
          "https://www.reddit.com/r/steamsupport/comments/1hkctwt/permanent_ban_with_no_explanation/",
          "https://www.reddit.com/r/pcgaming/comments/1vf24lu/warning_to_all_gamersexpats_steam_took_my_money/",
          "https://steamcommunity.com/groups/card-trading-card-trades",
          "https://steamcommunity.com/id/afarnsworth",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/groups/steambans",
          "https://steamcommunity.com/groups/steambans",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/id/killahinstinct_",
          "https://web.archive.org/web/20240914124859/https://steamcommunity.com/id/msart",
          "https://steamcommunity.com/id/msart/groups/",
          "http://web.archive.org/web/20260401154714/https://steamid.uk/faq/",
          "https://phishdestroy.io/steam_dossier/fr/enforcement_audit.html",
          "https://phishdestroy.io/steam_dossier/fr/#evidence-blackout",
          "https://www.steamcardexchange.net/index.php?badgeprices",
          "http://web.archive.org/web/20260804200309/https://www.steamcardexchange.net/index.php?badgeprices",
          "https://steam.supply/CardBots",
          "https://steamlvlup.net/cardbots",
          "http://web.archive.org/web/20260210171205/https://steamlvlup.net/cardbots",
          "https://steamlvlup.net/",
          "https://creativecommons.org/licenses/by/4.0/",
          "http://web.archive.org/web/20260923221628/https://creativecommons.org/licenses/by/4.0/",
          "https://phishdestroy.io/steam_dossier/fr/market_economics.html",
          "https://phishdestroy.io/steam_dossier/fr/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/fr/elite_skins.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/fr/card_economy.content.json",
      "export_json_sha256": "8a387639e93c10acd133d5e4e066509432a6a722217253ada1f18fbbb0e3bb94"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "fr/elite_skins.html",
      "language": "fr",
      "title": "Un même produit, deux systèmes de prix — Le dossier «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/fr/elite_skins",
      "source_html_sha256": "fd8207139368496416b244578d439fa33dfeed469713295c2fc5cd099022ac4c",
      "exported_at": "2026-09-29T00:17:35.108Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "register",
            "source": "https://phishdestroy.io/steam_dossier/fr/elite_skins#register"
          },
          {
            "id": "",
            "source": "https://phishdestroy.io/steam_dossier/fr/elite_skins#selected"
          }
        ],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "elite_skins.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/fr/elite_skins.pdf?v=print-20260929-v5",
        "sha256": "b1bcdfc16423a5458d9a26f5cf7f63581884412d2085ccc80d6d283ed5efac41",
        "bytes": 99853,
        "pages": 8
      },
      "integrity": {
        "signed_object": "elite_skins.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "elite_skins.content.json.asc",
        "digest_file": "elite_skins.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify elite_skins.content.json.asc elite_skins.content.json",
          "sha256sum -c elite_skins.content.json.sha256"
        ]
      },
      "content": {
        "text": "ANNEXE IV / ARCHITECTURE DU MARCHÉ / 20 SEPTEMBRE 2026\nInscription à Elite Skins — Le plafond du marché « $1,800 »\n\nUn article. Deux systèmes de tarification.\n\nCE QUE CETTE SECTION DÉMONTRERA\n\nCe registre établit un recensement empirique de toutes les catégories de skins CS2 dont le prix dépasse le plafond de mise en vente de Steam sur le « Community Market » (1,800), sur cinq plateformes externes. Il démontre que 248 les catégories haut de gamme — représentant 18,394 annonces actives et78.6 millions de dollars de liquidités affichées — sont 100% absentes de la place de marché officielle de Valve. Les vendeurs à la recherche de véritables prix de marché sont structurellement contraints de se tourner vers des plateformes externes tout en s’appuyant exclusivement sur les mécanismes de transaction sous-jacents d’Steam.\n\n← Retour au dossier de synthèse destiné aux dirigeants\n\nSteam limite le prix d'une annonce sur Community Market à environ1,800. Sur les cinq places de marché tierces dont les prix sont indiqués dans cet aperçu, 419 Les catégories d'objets CS2 affichent un prix de vente en temps réel le plus bas supérieur à cette limite — et 402 d'entre elles, 95.9%,, ne comportent aucune Steam annonce. À eux deux, ils détiennent des titres cotés sur 18,641 d’une valeur d’au moins $82.4 million. Il faut qu’une deuxième place de marché donne son accord pour que le cours soit pris en compte, 248 Parmi ces catégories, toutes sont confirmées — et dans chacune d’entre elles, 100%, est absent de Steam. « The dearest » est un autocollant | Titan (Holo) | Katowice 2014 à l'adresse $66,285, coté par quatre places de marché situées à 5.2% les unes des autres et non répertorié sur aucune des places de marché de Valve. Le classement complet, les rendus et les notes figurent dans le atlas des échelles de prix.\n\nConsulter toutes les entrées d'419s ↓Ouvrir l'atlas ↗Lire la méthode\n248catégories pour lesquelles le prix est supérieur au plafond sur au moins deux places de marché\n18,394exemplaires référencés sur cinq places de marché\n$78.6Mvaleur minimale de ces annonces\n100%dont certains sont totalement absents de Steam\n\nCorrection · cette page indiquait auparavant un prix non vérifié\n\nUne version antérieure de cette page présentait un « Souvenir AK-47 | Point Disarray » proposé à148,954 $ sur une plateforme de vente en ligne, tandis que Steam l'évaluait à119. $. Cette entrée ne concerne qu’un seul exemplaire disponible sur une seule plateforme, aucune autre plateforme ne proposant le même prix ; il s’agit donc d’un prix demandé et non d’un prix de vente, et elle n’apparaît plus sur la page. Chaque chiffre indiqué ici est désormais limité aux catégories «248» pour lesquelles au moins deux plateformes fixent indépendamment un prix supérieur au plafond. La ligne elle-même n’a pas été supprimée — elle figure toujours dans le registre ci-dessous, et la notation qui a entraîné son déclassement est présentée dans son intégralité dans le atlas des échelles de prix.\n\n01 / les fonds disponibles dans les ordres d'achat actifs\nLe seuil minimal mesurable en dollars\n\nChiffre recalculé à partir de l'instantané sous licence « cs2.sh » sur cinq places de marché. Il s'agit d'une valeur minimale agrégée des prix demandés au sein d'un sous-ensemble défini ; il ne s'agit ni du chiffre d'affaires ni d'une évaluation de l'économie CS2.\n\n248 CATÉGORIES VÉRIFIÉES · 18,394 EXEMPLAIRES RÉFÉRENCÉS · 5 PLATEFORMES DE VENTE$78.62M\n\nCours vendeur global minimal affiché pour chaque produit CS2 dont le prix est fixé, de manière indépendante, par au moins deux places de marché au-delà de la limite autorisée par Valve sur sa propre place de marché.\n\nPourquoi s'agit-il d'un seuil et non d'une estimation ?\n\nPour chaque place de marché, nous multiplions son le plus bas Demandez un article en indiquant le nombre d'exemplaires proposé par la plateforme. Tous les autres exemplaires présents sur cette étagère sont proposés à un prix égal ou supérieur au prix le plus bas demandé ; la valeur réelle affichée est donc plus élevée — par nature, et non par simple supposition. Il ne s'agit ni d'une vente, ni d'une trésorerie, ni d'une évaluation à l'échelle du marché, et un même article physique peut apparaître sur plusieurs plateformes.\n\nVérifier toutes les lignes de source d'419s ↗\n★ Gants de sport | Hedge Maze (testés sur le terrain)\n$4.68M\nAWP | Gungnir (neuf d'usine)\n$4.46M\nAWP | Dragon Lore (neuf, sorti d'usine)\n$4.34M\n★ Couteau papillon | Fade (neuf, sorti d'usine)\n$4.17M\nAK-47 | Wild Lotus (Neuf d'usine)\n$4.16M\n★ Couteau papillon | Doppler (neuf, sorti d'usine)\n$3.64M\n\nLes barres indiquent les six contributions les plus importantes, au niveau des catégories, au calcul du cours plancher, mises à l'échelle par rapport à la plus importante. Une barre haute reflète à la fois le prix vendeur le plus bas et le nombre d'exemplaires proposés. Un même article physique pouvant apparaître sur plusieurs places de marché, ces chiffres ne doivent en aucun cas être ajoutés au total d'une autre place de marché.\n\n02 / exemples vérifiables\nCe que cette limite ne prend pas en compte\n\nLes illustrations correspondent aux noms exacts des articles, lorsqu'ils sont indiqués. Les prix indiqués sont les prix de vente en vigueur figurant dans le catalogue daté, et non des prix de vente réels.\n\n★ Butterfly Knife | Doppler (Factory New)\n\nSource: https://phishdestroy.io/steam_dossier/fr/elite_skins#selected\n\nL'écart mesurable : Ces offres ne peuvent pas être égalées par une annonce publiée sur Steam au même prix en dollars américains. Celles proposées par Valve lui-même FAQ sur le marché communautaire archivé 2026-09-21 ↗ indique un prix de mise en vente maximal d'environ1,800. Un vendeur peut toutefois proposer un prix inférieur ; c'est à lui de décider si cela est acceptable. Une autre Recherche sur CSMarketCap pour les titres dont le cours est supérieur à1,800 $ ↗ présente les produits « Factory New Dragon Lore » sur les marchés référencés par 28, avec environ 1.1K d'offres affichées ; les stocks en double peuvent être comptabilisés plusieurs fois.\n\n03 / la dépendance structurelle\nLe plafond imposé par la Steam fait sortir la découverte des prix du cadre de l'Steam\n\nCette comparaison est de nature structurelle. Elle ne part pas du principe que tous les prix demandés sont justes et ne considère pas non plus les annonces invendues comme des recettes.\n\n01 · LA RÈGLE\nSteam conclut la liste\n\nValve précise que le nombre d'annonces sur Community Market est plafonné à environ $1,800. Les soldes des portefeuilles sont également plafonnés, et les fonds qu'ils contiennent ne peuvent pas être retirés en espèces.\n\nWhat this means — the Community Market listing ceiling\n\nSteam’s own market refuses a listing above roughly $1,800. A seller may ask less, never more. Items whose market price sits above that line therefore cannot be sold at that price on Steam at all — which is the mechanism that moves those sales to third-party venues while the item itself never leaves Valve’s inventory system.\n\nSection 13 — the off-Steam price gap →\n\n02 · L'OBSERVATION\nDragon Lore :10,940.85 $\n\nLe catalogue de la plateforme « 5-» présente 389 offres en direct pour l'AWP Dragon Lore (neuf d'usine), à partir de10,940.85 $ (étage CSFloat). Le registre plus large contient 248 des catégories vérifiées dépassant la limite de Steam.\n\n03 · LA CONSÉQUENCE\nRépartition du prix et du transfert\n\nUn vendeur qui cherche à obtenir ce prix plus élevé Je ne peux pas le publier sur Steam. Les prestataires externes peuvent fixer le prix au comptant, mais la livraison s'effectue toujours selon les modalités de propriété et de transfert des articles définies par l'Steam.\n\nLa contradiction politique : Une création de Valve Contrat d'abonnement archivé 2026-09-21 ↗ se réserve le droit d'interdire l'exploitation commerciale des services Steam, sauf autorisation expresse, tandis que son 2016 déclaration archivé 2026-09-21 ↗ Ces opérateurs de jeux d’argent utilisaient déjà l’OpenID d’Steam ainsi que des comptes automatisés. Il s’agit là d’une preuve directe qu’Valve avait connaissance de l’existence de cette catégorie d’opérateurs tiers sur 2016.. Pourtant, la place de marché officielle ne peut pas publier les prix observés pour ces articles de grande valeur. Il s’agit là d’une dépendance structurelle vis-à-vis des mécanismes de formation des prix et des transactions horsSteam ; Le statut contractuel de chaque place de marché nécessite des justificatifs distincts. Les deux principales places de marché occidentales qui enregistrent ce volume de transactions excédentaire opèrent en tant qu’entités juridiques à part entière dans des juridictions majeures — CSFloat Inc. (société constituée dans le Delaware, aux États-Unis) et Skinport GmbH (enregistrée à Stuttgart, en Allemagne, sous le numéro HRB 764879) — réalise ouvertement des centaines de millions dans le cadre de ventes entre particuliers, en s'appuyant directement sur les API Web et l'infrastructure commerciale d'Steam.\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\nLes quatre lignes à100,000 $ correspondent au prix de vente maximal fixé par CSFloat. Elles sont indiquées dans le registre et ne doivent pas être considérées comme des estimations. Le relevé archivé des annonces de CSFloat n'a couvert que les prix allant jusqu'à environ6,999, $ ; c'est pourquoi on utilise l'instantané du catalogue public pour le registre complet >1,800 $.\n\n04 / un autre jeu «Valve »\nLe plafond retient également les «2 » de Dota\n\nLe même test rigoureux de recherche de l’offre la moins chère sur Skinport permet de trouver les catégories CS2 sur 166 et les catégories Dota 2 sur 3. Il s’agit d’un aperçu distinct du marché ; ne les ajoutez pas à la liste 245. de CSFloat.\n\n2 DOTA · OFFRE 1\nCroissant héroïque et brutal\n\nPrix le plus bas pour « Skinport » : $14,622.25.\n\n2 DOTA · OFFRE 1\nCape « Dark Artistry »\n\nPrix le plus bas pour « Skinport » : $8,255.16.\n\n2 DOTA · OFFRE 1\nÉtoile alimentée corrompue\n\nPrix le plus bas pour « Skinport » : $2,087.92.\n\nIl s'agit là de trois catégories d'objets répertoriés, et non de l'ensemble des objets de Dota2. Consultez les lignes datées de l'Skinport ↗ et API documentation ↗.\n\n05 / robustesse\nCe résultat ne dépend pas de la valeur exacte du plafond\n\nValve définit le plafond dans la devise régionale de l'acheteur ; ainsi, une fois converti en dollars américains, le montant ne correspond pas à un chiffre rond. Le recensement est donc répété à chaque seuil plausible. La part de ces articles manquants sur Steam ne descend jamais en dessous de 95%.\n\nSeuil testé\tCatégories d'articles\tExemplaires répertoriés\tValeur plancher\tAbsent de Steam\n$1,800\t419\t18,641\t$82,449,526\t95.9%\n$2,000\t382\t15,159\t$75,541,325\t95.5%\n$2,070\t363\t12,336\t$69,560,305\t95.6%\n$2,300\t323\t11,644\t$67,984,432\t95.0%\n$2,500\t299\t10,950\t$66,203,929\t95.0%\n\nLisez une ligne à la fois ; les lignes constituent des sous-ensembles imbriqués d'un même recensement, et non des populations distinctes. La « valeur plancher » multiplie le le plus bas Il se base sur le nombre d'exemplaires qu'il recense, ce qui fait que, par nature, il sous-estime le nombre d'ouvrages en rayon. Ouvrir le jeu de données ↗\n\n06 / une pénurie sur laquelle on peut compter\nCombien peu d'entre eux sont réellement proposés à la vente ?\n\nBUFF divise la gamme de prix de chaque article en fourchettes et indique le nombre d'exemplaires disponibles dans chacune d'elles. Ainsi, le terme « rare » n'est plus qu'une simple indication chiffrée, et le prix de l'état de l'article est fixé indépendamment de celui de la peau.\n\n298 EXEMPLAIRES RÉFÉRENCÉS\nAWP | L'histoire du dragon\n\n8 différentes versions au prix. La plus chère, AWP de collection | Dragon Lore (neuf d'usine), demande $12,363 avec 20 exemplaires en rayon.\n\nDans la rubrique « Meilleurs flotteurs » de la boutique en ligne (0–0.01), on trouve 2 exemplaires, en demandant $17,875 — une prime de « +45% » par rapport au prix de base demandé pour cet article, uniquement en fonction de son état.\n\n607 EXEMPLAIRES RÉFÉRENCÉS\nM4A4 | Howl\n\n12 différentes versions au prix indiqué. La plus chère, Souvenir M4A4 | Howl (neuf d'usine), demande $14,895 avec des exemplaires d’2s en rayon.\n\n213 EXEMPLAIRES DÉCRITS\nAK-47 | Wild Lotus\n\n7 différentes versions au prix. La plus chère, AK-47 de collection | Wild Lotus (neuf d'usine), demande $14,895 avec des exemplaires d’2s en rayon.\n\n310 EXEMPLAIRES RÉFÉRENCÉS\nAWP | Gungnir\n\n7 différentes versions au prix. La plus chère, AWP de collection | Gungnir (très peu d'usure), demande $14,895 avec des exemplaires d’2s en rayon.\n\nEn quoi cela est-il pertinent pour la suite de ce dossier : Il ne s’agit pas là d’abstractions. Il existe dans le monde entier quelques centaines d’exemplaires de chaque trophée disponibles librement, chacun étant lié à un compte Steam et ayant fait l’objet d’une transaction sur Steam. Sur un marché aussi restreint, le vol d’un seul objet d’inventaire constitue un événement mesurable, et les techniques de piratage de compte décrites ailleurs dans cette enquête ont un impact direct et quantifiable.\n\nLes chiffres correspondent au nombre d'annonces actives sur une place de marché au moment de la collecte des données, et non au nombre total d'exemplaires existants. Les exemplaires conservés dans des stocks privés ne sont pas pris en compte ici. Ouvrir l'ensemble de données « float » ↗\n\n07 / l'échelle hors de vue\nPlus l'article est cher, plus il est éloigné de tout lieu de vente visible\n\nChaque échelon ci-dessous correspond à une catégorie de preuves distincte. Elles n’ont délibérément pas été regroupées en un seul chiffre.\n\nÉchelon\tFigure\tDe quel type de fait s'agit-il ?\nCeiling on Valve's own market\t~$1,800\tPublished rule, stated in the Steam Community Market FAQ.\nDearest ask several marketplaces agree on\t$66,285\tMeasured by us in this snapshot. Sticker | Titan (Holo) | Katowice 2014, quoted by four marketplaces within 5.2% of one another. An ask, not a sale.\nDearest ask seen on any single shelf\t$148,954\tOne marketplace, one copy, no second marketplace agreeing — and equal to a round CNY 1,000,000 at the snapshot rate. Listed here as the outer edge of what sellers ask, and relied on for nothing.\nPublic marketplace sale\t$49,999\tSpecialist Gloves | Crimson Kimono (FN) on CSFloat, as reported by SteamAnalyst. Platform-recorded, third-party reported.\nReported private sale\t$400,000\tAK-47 | Case Hardened, reported by PC Gamer in April 2023. Journalism, not a record we hold.\nReported offer, declined\t$1,500,000\tBlue Gem Karambit, pattern #387. No sale took place and the figure has not been independently confirmed. Included to mark the ceiling of the claims, not to assert a value.\n\nLe point structurel : Le marché de Valve s'arrête à environ1,800.. Les places de marché tierces font grimper le prix à environ66,000, niveau auquel plusieurs d'entre elles s'accordent, et à environ150,000, niveau auquel une seule d'entre elles s'aligne. Au-delà de ce seuil, il n’existe aucune plateforme : les transferts les plus importants d’actifs émis par Valves’effectuent de gré à gré, entre particuliers, sans cotation, sans trace sur une plateforme, sans vérification d’identité et sans déclaration. Le transfert lui-même s’effectue toujours via Steam. Plus la valeur est élevée, moins elle est visible, et l'infrastructure qui la prend en charge est entièrement celle d'Valve.\n\nLes deux derniers éléments proviennent de rapports rédigés par des tiers, cités comme tels. Ce projet ne les a pas vérifiés et ne s'appuie pas sur eux pour tirer la moindre conclusion.\n\nToutes les catégories observées dans «419»\n\nSource: https://phishdestroy.io/steam_dossier/fr/elite_skins#register\n\n09 / provenance et limites\nVérifiez le calcul\n\nNous mettons à disposition les données locales et la source publique. La valeur numérique indiquée correspond à CSFloat à la date de capture.\n\nLes limites et les conditions propres à Valve\n\nSteam FAQ sur le Marché communautaire ↗ archivé 2026-09-21 ↗ indique le montant maximal approximatif de l'annonce, soit1,800. Le Contrat d'abonnement ↗ archivé 2026-09-21 ↗ définit les restrictions relatives à l'utilisation commerciale.\n\nD'où viennent les prix ?\n\nLes cours, le nombre de titres cotés et les fourchettes de flottant sont tirés du cs2.sh API des données de marché dans le cadre d'un abonnement commercial payant, à l'aide d'une clé de licence. Aucune plateforme de vente en ligne n'a fait l'objet d'un scraping et aucun compte ni identifiant de ces plateformes n'a été utilisé. Le fournisseur regroupe BUFF, Youpin, CSFloat, Skinport, C5Game et la place de marché communautaire Steam ; tous les montants sont exprimés en dollars américains tels qu'ils ont été communiqués. Ouvrir le manifeste de provenance ↗ — il enregistre les points de fin exacts, les heures de capture et les hachages SHA-256 des instantanés bruts ; ainsi, un lecteur indépendant disposant de sa propre clé peut extraire les mêmes données et recalculer chaque chiffre figurant sur cette page.\n\nCe que nous n'avons pas pu obtenir\n\nL'abonnement souscrit ne couvre que les instantanés actuels. Nous n'avons pas eu accès aux points de terminaison historiques et archivés, et Cette page ne contient aucune affirmation concernant une tendance quelconque, un cours passé ou une évolution dans le temps. Ici, tout n'est qu'un instant, daté.\n\nL'ancien registre « CSFloat »\n\nLa première version de cette exposition comptait 245 catégories issues d'un seul instantané du catalogue CSFloat daté du 20 septembre 2026: cet instantané reste ici ↗. Le présent registre est plus large, car il couvre cinq places de marché au lieu d'une seule. Il s'agit de deux relevés distincts qui ne doivent pas être additionnés.\n\nDéclaration de Valve relative à l'exécution forcée\n\nMise à jour de Valve concernant l'échange d'objets en jeu dans « 2016 » ↗ archivé 2026-09-21 ↗ vise les opérateurs de jeux d'argent utilisant OpenID et des comptes automatisés de type «Steam ». Cette mesure a une portée plus restreinte qu'une interdiction de toutes les plateformes tierces.\n\nLimite d'interprétation\n\nIl s'agit d'offres, et non de ventes. Un nom de référence peut désigner plusieurs articles physiques présentant des différences au niveau de la finition, du motif ou des autocollants. Ce registre ne rend pas compte de la valeur marchande totale ni de l'intention d'Valve.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Inscription à Elite Skins — Le plafond du marché « $1,800 »"
          },
          {
            "level": 2,
            "id": null,
            "text": "Le seuil minimal mesurable en dollars"
          },
          {
            "level": 3,
            "id": null,
            "text": "Pourquoi s'agit-il d'un seuil et non d'une estimation ?"
          },
          {
            "level": 2,
            "id": null,
            "text": "Ce que cette limite ne prend pas en compte"
          },
          {
            "level": 3,
            "id": null,
            "text": "★ Butterfly Knife | Doppler (Factory New)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Le plafond imposé par la Steam fait sortir la découverte des prix du cadre de l'Steam"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam conclut la liste"
          },
          {
            "level": 3,
            "id": null,
            "text": "Dragon Lore :10,940.85 $"
          },
          {
            "level": 3,
            "id": null,
            "text": "Répartition du prix et du transfert"
          },
          {
            "level": 2,
            "id": null,
            "text": "Le plafond retient également les «2 » de Dota"
          },
          {
            "level": 3,
            "id": null,
            "text": "Croissant héroïque et brutal"
          },
          {
            "level": 3,
            "id": null,
            "text": "Cape « Dark Artistry »"
          },
          {
            "level": 3,
            "id": null,
            "text": "Étoile alimentée corrompue"
          },
          {
            "level": 2,
            "id": null,
            "text": "Ce résultat ne dépend pas de la valeur exacte du plafond"
          },
          {
            "level": 2,
            "id": null,
            "text": "Combien peu d'entre eux sont réellement proposés à la vente ?"
          },
          {
            "level": 3,
            "id": null,
            "text": "AWP | L'histoire du dragon"
          },
          {
            "level": 3,
            "id": null,
            "text": "M4A4 | Howl"
          },
          {
            "level": 3,
            "id": null,
            "text": "AK-47 | Wild Lotus"
          },
          {
            "level": 3,
            "id": null,
            "text": "AWP | Gungnir"
          },
          {
            "level": 2,
            "id": null,
            "text": "Plus l'article est cher, plus il est éloigné de tout lieu de vente visible"
          },
          {
            "level": 2,
            "id": null,
            "text": "Toutes les catégories observées dans «419»"
          },
          {
            "level": 2,
            "id": null,
            "text": "Vérifiez le calcul"
          },
          {
            "level": 3,
            "id": null,
            "text": "Les limites et les conditions propres à Valve"
          },
          {
            "level": 3,
            "id": null,
            "text": "D'où viennent les prix ?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ce que nous n'avons pas pu obtenir"
          },
          {
            "level": 3,
            "id": null,
            "text": "L'ancien registre « CSFloat »"
          },
          {
            "level": 3,
            "id": null,
            "text": "Déclaration de Valve relative à l'exécution forcée"
          },
          {
            "level": 3,
            "id": null,
            "text": "Limite d'interprétation"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/fr/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/fr/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/fr/skin_atlas.html#grading",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-above-the-ceiling.json",
          "https://phishdestroy.io/steam_dossier/fr/elite_skins#selected",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://csmarketcap.com/search?minPrice=1800&amp;page=1",
          "https://phishdestroy.io/steam_dossier/fr/#market-gap-section",
          "https://store.steampowered.com/agreement/?l=english",
          "http://web.archive.org/web/20260921022032/https://store.steampowered.com/agreement/?l=english",
          "https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921021947/https://store.steampowered.com/oldnews/22883",
          "https://phishdestroy.io/steam_dossier/fr/#proxy-bypass-explainer",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/skinport-floor-over-cap.json",
          "https://docs.skinport.com/items",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-float-scarcity.json",
          "https://phishdestroy.io/steam_dossier/fr/elite_skins#register",
          "https://cs2.sh/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/csfloat-catalogue.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/fr/elite_skins.content.json",
      "export_json_sha256": "6609d152b0cfce571d4f283c961f6326b674bf5eae262041968c6069af1a7c43"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "fr/enforcement_audit.html",
      "language": "fr",
      "title": "Le recensement Valve ne sera pas publié — Le dossier Steam",
      "source_url": "https://phishdestroy.io/steam_dossier/fr/enforcement_audit",
      "source_html_sha256": "8c85ed6effa76788a245dab5ecc0629b670904809969767c12f1d2c5841b2c46",
      "exported_at": "2026-09-29T00:17:34.222Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "enforcement_audit.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/fr/enforcement_audit.pdf?v=print-20260929-v5",
        "sha256": "e1616b1edf47ee8256fdc4b13232171008de5612eb67e71b089782c6013b6cd0",
        "bytes": 151971,
        "pages": 13
      },
      "integrity": {
        "signed_object": "enforcement_audit.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "enforcement_audit.content.json.asc",
        "digest_file": "enforcement_audit.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify enforcement_audit.content.json.asc enforcement_audit.content.json",
          "sha256sum -c enforcement_audit.content.json.sha256"
        ]
      },
      "content": {
        "text": "PIÈCE VI — LE RECENSEMENT VALVE NE SERA PAS PUBLIÉ\nQuelle est l’ampleur de cette ferme Steam ? Nous l’avons comptée.\n\nIl n'existe aucun chiffre publié concernant le nombre de comptes d'automatisation fonctionnant sur Steam. Il n'y a d'ailleurs aucune raison que ce chiffre soit tenu secret : l'espace d'identifiants Steam correspond à une plage d'entiers contigus et Valve distribue la clé d'API Web qui permet de parcourir cette plage. Nous avons donc pris la plus grande population qui s'identifie elle-même — la communauté ArchiSteamFarm — et avons interrogé chaque membre une fois via le point de terminaison de blocage propre à Valve. Elle s’autodéclare car ASF, lors de son premier lancement, rejoint automatiquement le groupe Steam, à moins que l’utilisateur ne se désinscrive explicitement ou ne désactive le paramètre d’adhésion au groupe (AutoJoinSteamGroup / Statistiques). Ce paramètre étant activé par défaut, les membres du groupe représentent un large éventail d’utilisateurs : des réseaux commerciaux de bots gérant plusieurs comptes, des amateurs occasionnels laissant leurs comptes inactifs, ainsi que des joueurs lambda ayant utilisé le logiciel sur leur compte personnel sans jamais désactiver l’abonnement par défaut. Les membres du groupe constituent ainsi un recensement représentatif de l’audience cumulée du logiciel : 10,880,610 compte au total (dont 5,360,499 membres confirmés sans restriction ayant franchi la porte du magasin $5.00). Nous avons alors posé la seule question qui compte : qu'est-ce que Valve leur a réellement fait ?\n\nCe que cette page n'est pas. Il ne s'agit pas d'un argument en faveur de l'exclusion de dix millions de personnes par Valve, ni d'une critique à l'encontre des « card farmers ». Chaque chiffre ci-dessous est mentionné pour une seule raison : Valve fait exclure définitivement des utilisateurs, et la raison invoquée par écrit est l’utilisation commerciale de Steam et l’automatisation. Cela permet de mesurer la manière dont cette même règle est appliquée à un même comportement à grande échelle — par un opérateur dont le déblocage $5.00, les licences de jeu et les frais de la Boutique Valve sont prélevés au fur et à mesure. Ce qui ressort, c’est l’asymétrie, et non le « farming ».\n\nLe nombre de 10,88 millionsLes escrocs qui se promènent (53 500)Audit payant à 100 000 vs audit gratuit\n10,880,610Nombre total de membres du groupe ASF ayant consulté l'API de suspension de Valve (limitées et non limitées confondues)\n88.97%Je n'ai jamais été banni — 9,680,599 comptes toujours actifs\n63.06%Parmi les comptes suspendus, ceux qui sont payants ($5+ dépenses) — 100,000 SRSWOR tranche (±0.39% MoE)\n67.77%Parmi les 51,732 escrocs condamnés, aucun ne fait l'objet d'une interdiction pour escroquerie (recensement complet)\n01 — L'échelle\nDix millions de comptes, dont neuf sur dix n'ont pas été utilisés\n\nUne population qui s'auto-recense, lue une fois à travers le point final propre à Valve.\n\nPOURQUOI IL SE COMPTE LUI-MÊME\nASF rejoint le groupe pour vous\n\nLors de la première exécution, ArchiSteamFarm ensembles Statistiques est défini sur « true » par défaut et intègre le groupe « SC Farm Steam » d'Archi. Un opérateur doit expressément choisir de ne pas y adhérer. L'appartenance à ce groupe correspond donc à un seuil minimal pour les installations, et non à un plafond. Les opérateurs ayant désactivé les statistiques ne sont pas pris en compte ; le nombre réel d'installations est au moins aussi élevé.\n\nCE QUE NOUS LISONS\n10,880,610 nombre total d'entrées\n\nLa liste des membres de l'API a renvoyé 10,880,610 SteamID64 au total — qu'ils soient limités ou non. La page du groupe de Steam en affiche 5,360,499 (uniquement les identifiants non limités). Chaque entrée a été traitée une fois via ISteamUser/GetPlayerBans sur 2026-09-23. Cinquante-cinq minutes sur une seule touche.\n\nLA RÉPONSE\n88.97% propre\n\n1,200,011 ne fait l’objet d’aucune Steam interdiction (11.03%). L’autre 9,680,599 n'a absolument rien dans son dossier — ni exclusion de la communauté, ni VAC, rien. La ferme n'est pas supprimée. Elle continue de fonctionner. Cette même clause, appliquée à une seule personne, suffit à l'exclure définitivement.\n\nSur 10,880,610 comptes, combien ont atteint Valve ?\n\nL'ensemble de la population scannée, répartie selon que Valve a appliqué ou non une interdiction. La partie en rouge correspond à tout ce que Valve a jamais fait à cette flotte.\n\n88.97%jamais banni\n11.03%\nAucune interdiction d'aucune sorte — 9,680,599 (88.97%)Comporte une interdiction de Steam — 1,200,011 (11.03%)\n10,880,610Les membres du groupe ASF ont été scannés\n9,680,599Jamais banni — 88.97%\n1,200,011Appliquer toute interdiction — 11.03%\n55 minPour tout comptabiliser, avec une seule clé API\nCe que cette flotte a déjà coûté Valve pour voir le jour\n\nIl ne s'agit pas d'une estimation des revenus de la ferme, mais d'un seuil minimum correspondant à ce qu'elle a déjà dépensé dans le magasin de Valve — calculé à partir de la règle de Valve, appliquée au décompte ci-dessus.\n\nLe nombre 10,880,610 correspond à la liste complète des membres du groupe ASF telle qu'elle est renvoyée par l'API — cela inclut à la fois les comptes soumis à des restrictions et ceux qui ne le sont pas. Steam lui-même Comptes d'utilisateurs à fonctionnalités limitées La page précise que les comptes à fonctionnalités limitées ne compter pour Steam appartenance à un groupe (ils ne sont pas pris en compte dans le nombre de membres du groupe affiché), mais ils peuvent tout de même figurer dans la liste des membres sous-jacente. Le sous-ensemble non limité — les comptes ayant dépensé au moins $5.00 dans le magasin Steam — est exactement 5,360,499 — le nombre Steam s'affiche sur la page du groupe, qui, selon la règle définie par Steam, exclut les comptes soumis à des restrictions. Le calcul du seuil $5.00 ne s'applique qu'à ce sous-ensemble non soumis à des restrictions.\n\n5,360,499membres sans restriction\n(Nombre de groupes affichés par Steam)\n×\n$5.00Le minimum propre à Valve\npour ne plus être limité\n=\n$26,802,495seuil de dépenses en magasin\npar le sous-ensemble non limité\n\nIl s'agit d'une limite inférieure correspondant aux sommes déjà perçues par Valve auprès de la partie non soumise à restriction de la flotte — et non d'une estimation des recettes, ni d'une déclaration de bénéfices. Les dépenses réelles par compte sont supérieures pour la plupart ; le chiffre $5.00 correspond uniquement au seuil minimum requis.\n\nLa récolte secondaire : jusqu’à 66.7% de frais sur le volume des produits cultivés. Au-delà des frais d’entrée de $26.8M, chaque carte et chaque objet mis en vente sur le Marché communautaire est soumis à des frais minimums obligatoires de deux centimes ($0.01 Steam de frais + $0.01 de frais d’éditeur). Pour les cartes et les objets sans valeur typiques à 3 centimes, Valve prélève 2 centimes sur 3 centimes — ce qui revient à une réduction effective de 66.67% en faveur de Valve, dépassant de loin le taux de commercialisation annoncé de 15%.\n\nRemarque importante concernant la population : L'appartenance à un groupe ne prouve pas que chaque compte soit un bot dédié, et ne recense pas non plus tous les bots présents sur Steam. Par défaut, ASF inscrit automatiquement les comptes à son groupe communautaire dès leur création ; à moins que l'utilisateur ne désactive explicitement cette option (AutoJoinSteamGroup), les joueurs réguliers, les joueurs occasionnels et les membres de la communauté figurent toujours sur la liste aux côtés des flottes de farming automatisées. De plus, une suspension Steam n'est accompagnée d'aucune justification publique. Ce constat correspond à un taux empirique observé au sein de cette population liée au logiciel, et non à un verdict individuel concernant un compte en particulier. Agrégé, reproductible : asf-ban-census-2026-09-23.json.\n\n02 — Géographie\nOù se trouve la flotte\n\nSeuls 8.5% des comptes bannis indiquent un pays. Parmi ceux qui le font, les États-Unis représentent la plus grande part.\n\nUn profil Steam comporte un champ « Pays » facultatif. 100,413 des 1,182,811 comptes suspendus l'ont renseigné — 8.5%.† Au sein de cette minorité, les États-Unis arrivent en tête avec 15.5%, suivis de l’Ukraine, de la Chine et de la Russie, tandis que les autres se répartissent en une longue traîne à travers l’Europe, l’Amérique latine et l’Asie du Sud-Est. Personne ne vérifie ces données sur le terrain : l’Afghanistan figure dans le top 10, ce qui correspond à peu près à sa valeur réelle. Les 91.5% autres pays sont omis plutôt qu’attribués ; ce qui suit reflète donc la composition d’une minorité auto-sélectionnée — et non une carte de la flotte, ni une base permettant de déterminer d’où elle est dirigée.\n\nComptes bannis par pays déclaré\n\nLes 15 premiers pays parmi les 100,413 comptes suspendus qui divulguent un lieu public. La part correspond à ce sous-ensemble. Passez la souris pour afficher les chiffres.\n\n0%\n5%\n10%\n15%\n20%\nUnited States\nUkraine\nChina\nRussia\nCanada\nAustralia\nJapan\nBrazil\nGermany\nAfghanistan\nUnited Kingdom\nRomania\nFrance\nPhilippines\nIndia\n\nEmplacement lu à partir de GetPlayerSummaries pour le sous-ensemble banni. Ce champ est défini par le titulaire du compte et n'est vérifié par personne ; ainsi, une adresse de sortie VPN ou une entrée fantaisiste a la même valeur qu'une entrée réelle.\n\n03 — Fraîcheur\nDes comptes récents, et non un arriéré historique\n\nSi l'on se base sur la date de création des comptes, cette population bannie est récente ; il ne s'agit pas d'un vestige de l'époque des cartes à collectionner.\n\nS'il s'agissait d'un vieux problème en train d'être progressivement réglé, les comptes bannis concerneraient principalement les premières années des cartes à collectionner. Or, c'est tout le contraire. Sur les 1,132,852 comptes bannis dont la date de création est connue, 70% ont été créés en 2020 ou après, et près de la moitié depuis 2023. Le nombre passe de 59,175, créé en 2017, à un pic de 227,030 créés rien qu'en 2024. Chacun d’entre eux a franchi la barrière du magasin $5.00 avant que celle-ci n’ait pu enregistrer leur carte, de sorte que les frais d’entrée ont été prélevés pour chacun d’entre eux.\n\nÀ quel moment les comptes bannis ont-ils été créés ?\n\nAnnée de création des comptes des 1,132,852 membres bannis dont la date de création est visible. La période concernée s'étend de 2020 à 2026, et non pas à l'époque des cartes à collectionner (2013-2015). Pic : 2024. Passez la souris pour afficher les chiffres.\n\n0k\n63k\n125k\n188k\n250k\n'13\n'14\n'15\n'16\n'17\n'18\n'19\n'20\n'21\n'22\n'23\n'24\n'25\n'26\n70%Parmi les comptes suspendus créés en 2020 ou après\n227,030Comptes bannis créés en 2024 — l'année où leur nombre a atteint son pic\n51,701Le creux de 2021, entre deux années de pic — inexpliqué\n2003→2026La fourchette est indiquée, mais les données portent sur les six dernières années\n\nLa création remonte à GetPlayerSummaries pour le sous-ensemble des comptes bannis, après déduplication par SteamID64. La date de création correspond à la date à laquelle le compte a été créé, et non à celle à laquelle il a été banni ou à celle où il a commencé à « farmer » ; elle est ici considérée comme un indicateur de la fraîcheur de la population, et non comme une preuve d'intention. Trois éléments ne figurent pas dans le graphique :\n\nUne tendance qui se dessinera après 2024. Un compte créé en 2025 ou en 2026 a eu moins de temps pour se voir infliger une suspension, et l'année 2026 couvre neuf mois — donc 227,030 → 121,070 → 16,534 correspond à une censure, et non à une baisse.\nUn taux d'interdiction. Les années de création n'ont été prises en compte que pour les comptes suspendus ; il n'y a donc pas de dénominateur. La simple croissance du nombre d'utilisateurs suffirait à expliquer cette courbe.\nPourquoi l'année 2021 a été un échec. 51,701 se situe entre 105,821 et 104,641, à moins de la moitié de la distance de chacun de ses voisins. Aucune explication officielle n'est fournie ; il est laissé tel quel plutôt que d'être lissé.\n04 — Calendrier\nLorsque Valve intervient, c'est au cours de la première année\n\nL'argument évident en faveur du maintien du 88.97% tel quel est l'accumulation des dossiers en attente. Les interdictions datées indiquent le contraire.\n\nDepuis combien de temps le compte existait-il au moment où la suspension a été prononcée ?\n\nAncienneté des comptes au moment de la suspension, pour les 293,750 comptes suspendus pour lesquels on dispose à la fois d'une date de création et d'une date de dernière suspension. Plus de la moitié ont été suspendus au cours de leur première année d'existence.\n\n0%\n10%\n20%\n30%\n40%\n<6 mo\n33.7%\n6–12 mo\n21.5%\n1–2 y\n20.6%\n2–5 y\n14.3%\n5 y+\n10.0%\n55.1% inside the first year\nInterdit au cours de la première année — 55.1%Banni par la suite — 44.9%\n0,80 anÂge médian du compte au moment de l'application de la suspension\n55.1%Banni au cours de la première année d'existence du compte\n33.7%Interdit au cours des six premiers mois\n293,750Comptes pour lesquels les deux dates sont présentes\n\nVoici la réponse à cet argument de défense évident. Si 88.97% de la flotte n'est pas concernée parce que l'application de la loi est tout simplement lente — un arriéré qui se résorbe progressivement —, alors les interdictions qui faire on pourrait s'attendre à ce que les données soient biaisées vers les comptes anciens. Or, c'est tout le contraire : l'âge médian des comptes suspendus était de âgé de neuf mois et demi, et un troisième — 33.7% — a été capturé en moins de six mois. Lorsque Valve agit sur cette population, il agit rapidement. Les neuf sur dix qui sont toujours en liberté n’attendent pas leur tour.\n\nÂge au moment de l'interdiction = date de création à partir de GetPlayerSummaries déduit de la date d'interdiction découlant de JoursDepuisLaDernièreInterdiction, lire la suite 2026-09-23. Ce chiffre n'est calculé que lorsque les deux valeurs sont présentes : 293,750 des 1,200,011 comptes bannis. Les comptes restants ne fournissent aucune valeur de « nombre de jours écoulés » et sont omis, et non supposés — il faut donc considérer cela comme la structure du sous-ensemble daté, et non comme celle de chaque suspension.\n\n05 — En quoi consiste réellement cette interdiction ?\nLorsque Valve s'active, cela n'arrête pas le bot\n\nParmi les 11% qui font l'objet d'une interdiction, vérifiez de quelle interdiction il s'agit.\n\nUne suspension n'est pas une suspension. Sur les 1,200,011 comptes signalés par Valve, 99.8% porter un communauté interdiction — une restriction applicable aux forums, profils et groupes qui n’a aucun effet sur un bot d’échange. Le compte peut toujours recevoir des cartes, effectuer des échanges et gérer son inventaire. 22.2% avoir fait l’objet d’au moins une exclusion du jeu et 3.9% d’une exclusion de VAC ; ces catégories se recoupent, elles ne s’additionnent donc pas. La seule sanction qui empêche réellement les échanges, à savoir l’exclusion économique / commerciale, concerne 5,214 comptes. Nous ne fondons pas notre argumentation sur ce chiffre — les interdictions d’échanges sont rares, avec Steam en général. Le message de ce graphique est plus simple : même la fraction Valve fait touch poursuit ses activités de trading.\n\nPour quoi sont réellement bannis les 11% qui ont été bannis ?\n\nChaque type d'interdiction représente une part de l'ensemble des membres 10,880,610 analysés. Un compte peut en comporter plusieurs. Passez la souris dessus pour afficher les chiffres.\n\n0%\n4%\n8%\n11%\n15%\nCommunity ban\nGame ban\nVAC ban\nEconomy / trade ban\n\nUne interdiction de type « Steam » ne comporte pas de champ « motif » ; par conséquent, aucune de ces interdictions n'est spécifiquement attribuée à la « collecte de cartes » — il s'agit ici d'un mélange des différents types d'interdictions existants, mis en parallèle avec ce que chaque type restreint concrètement. L'interdiction communautaire n'empêche pas les échanges ; en revanche, l'interdiction économique / commerciale, elle, les empêche. Résumé : asf-ban-census-2026-09-23.json.\n\n06 — L'autre population\nLes escrocs Valve, passons à autre chose : le recensement complet 51,732\n\nUne deuxième liste, indépendante — regroupant les fraudes signalées par la communauté —, comparée à la même API officielle.\n\nOn pourrait faire valoir que la population des automatiseurs n’est composée que de fainéants inoffensifs. Ce n’est pas le cas de la deuxième population. SteamRep est une base de données de réputation communautaire qui existe depuis longtemps ; un compte marqué INTERDIT Cette communauté a désigné un escroc, sur la base de preuves fournies par les victimes et d'historiques de discussion relatifs aux transactions. Nous avons réalisé un recensement 100% de tous les 51,732 profils portant le statut « INTERDIT » par rapport à l'API Web officielle de Steam (ISteamUser/GetPlayerBans/v1) — et n'a pris en compte que les sanctions visant spécifiquement la fraude. Une suspension de VAC concerne l'utilisation de logiciels de triche dans un jeu (aimbots, wallhacks) ; elle n'a aucune incidence sur un trader et ne constitue pas une preuve Valve de fraude, elle n'est donc pas comptabilisée comme une mesure de lutte contre la fraude.\n\nSur l'ensemble du recensement des comptes 51,732, 67.77% — 35,059 escrocs condamnés — n'ont fait l'objet d'AUCUNE suspension liée à l'escroquerie de la part de Valve : Ils peuvent toujours effectuer des échanges, envoyer des demandes d’amitié à de nouvelles victimes et envoyer des messages. Seuls 32.23% ont fait l’objet d’une exclusion de la communauté ou d’une interdiction d’échange, et cette dernière — la seule mesure qui empêche réellement les transferts d’inventaire — ne concerne que 18.81% (9,731 comptes). En outre, 12.81% (6,627 compte) ont reçu VAC interdictions de jeu uniquement pour triche en jeu, tout en restant totalement libres d’effectuer des Steam échanges.\n\nEscrocs confirmés, selon que Valve a appliqué ou non une suspension liée à une arnaque (recensement complet)\n\nTous les profils 51,732 SteamRep-BANNIS, classés selon que Valve a appliqué une exclusion de la communauté ou une exclusion commerciale. Les exclusions VAC et les exclusions liées au jeu sont exclues — elles ne concernent pas la fraude. Passez la souris dessus pour voir les chiffres.\n\n0%\n18%\n35%\n53%\n70%\nNo scam-relevant ban\nCommunity or trade ban\n0%\n6%\n13%\n19%\n25%\nCommunity ban\nTrade / economy ban\nVAC (not fraud)\nGame ban\n51,732SteamRep - Profils « BANNED » vérifiés — 100% recensement complet\n35,059N'a fait l'objet d'aucune exclusion liée à une arnaque (67.77%)\n18.81%Appliquer l'interdiction commerciale qui met fin aux escroqueries (9,731)\n32.23%La part Valve a fait l'objet d'une interdiction communautaire ou commerciale (16,673)\n\nSteamRep est une base de données de réputation tierce, évaluée par la communauté, et non une décision Valve — c’est justement là le point essentiel : il s’agit de preuves externes, mises en regard de ce qu’Valve a lui-même fait. Tous les profils 51,732 INTERDITS issus de l’exportation canonique ont fait l’objet d’un recoupement direct avec ISteamUser/GetPlayerBans/v1. L'expression « lié à la fraude » désigne une exclusion de la communauté ou une interdiction d'accès à l'économie/au commerce ; VAC (12.81%) et les interdictions de jeu (3.86%) sont comptabilisées séparément, car elles concernent la triche et non la fraude. Ensemble complet de données d'audit : steamrep_steam_bans.csv.\n\nDeux populations, une seule découverte\n\nIl ne s’agit ni des mêmes personnes, ni des mêmes agissements. D’un côté, on compte dix millions de comptes automatisés ; de l’autre, cinquante-trois mille escrocs condamnés par la justice. Ce qu’ils ont en commun, c’est la nature du résultat : Neuf comptes agricoles sur dix ne sont jamais utilisés, et plus des deux tiers (67.77%) des fraudeurs avérés ne font l'objet d'aucune sanction liée à la fraude. La mesure d’exclusion de la communauté Valve permet de restreindre librement l’accès aux forums et aux profils, mais pas les échanges commerciaux. Le bouton de signalement, la base de données de réputation, la mesure d’exclusion qui met fin à une arnaque : tout est là, mais tout est sous-utilisé. Comparez cela aux refus archivés dans le dossier principal, où la même entreprise supprime définitivement un seul compte en invoquant comme motif l’utilisation commerciale et l’automatisation — cette clause n’est pas lettre morte, elle est bien ciblée.\n\n07 — La faille de sécurité « $5.00 » et le piratage de comptes\nL'audit empirique des comptes « 100,000 » : les botnets ne sont pas des comptes gratuits jetables\n\nLogique de l'échantillonnage statistique et démonstration mathématique : pourquoi le fait de prendre n'importe quelle autre valeur de 100,000 donne exactement le même résultat.\n\nL'argument principal avancé par Valve auprès des autorités de régulation et des organismes de protection des consommateurs est que les escroqueries automatisées et le « farming » sont le fait de comptes « jetables », éphémères et gratuits, qui sont rapidement bannis. Selon les règles publiées par Valve, un compte est Limité jusqu'à ce qu'il dépense au moins 5.00s de dollars américains dans la boutique Steam, ce qui l'empêche d'accéder aux échanges, aux demandes d'amitié et aux fonctionnalités de l'API. Nous avons vérifié cette affirmation directement en testant le statut de monétisation d'un échantillon représentatif et mathématiquement rigoureux de 100,000 comptes Steam bannis issues de notre corpus de métadonnées de profils 1,182,811.\n\nPROTOCOLE D'ÉCHANTILLONNAGE (SRSWOR)\n100,000 Tranche impartiale\n\nTiré de N = 1,182,811 comptes uniques bannis Steam à l'aide d'un échantillonnage aléatoire simple sans replacement via un générateur de nombres aléatoires pseudo-aléatoires (PRNG) cryptographiquement uniforme. Chaque compte avait une probabilité d'inclusion identique de P = n / N ≈ 8.45%, ce qui élimine totalement les biais de survie et d'activité.\n\nPREUVE MATHÉMATIQUE\nMarge d'erreur < ±0.4%\n\nEn appliquant la formule de correction pour population finie (FPC) à un 99% Intervalle de confiance (Z = 2,576) :\nMoE = Z × √[p(1-p)/n] × √[(N-n)/(N-1)] ≈ ±0.39%\n\nREPRODUCTIBILITÉ\nPourquoi n'importe quel 100k donne le même résultat\n\nÉtant donné que la marge d'erreur est bornée à ±0.4% avec un niveau de confiance de 99%, il est mathématiquement garanti que tout autre échantillon indépendant tiré du compte 100,000 se situera dans l'intervalle 63.06% ± 0.39% (62.67% à 63.45%). L'échantillon est représentatif de l'ensemble de la population concernée par l'interdiction, soit 1,18 million de personnes.\n\nLes résultats de l'audit réfutent totalement l'argument du « bot jetable ». Parmi les 100,000 comptes audités via l'interface XML héritée de Steam : Les comptes 61,490 (63.06% des comptes classés) sont des comptes « non limités » (payants) ayant dépensé au moins $5.00 sur Steam. Seulement 36,021 (36.94%) sont des comptes gratuits limités, tandis que 2,489 n'étaient pas configurés ou étaient privés.\n\n100,000 Comptes bannis : comptes payants ($5+ dépenses en boutique) vs comptes gratuits à accès limité\n\nAudit empirique portant sur 100,000 comptes bannis sélectionnés au hasard. Plus de 63% d'entre eux ont franchi le seuil financier payant de Valve. Passez la souris dessus pour voir les chiffres.\n\n0%\n16%\n33%\n49%\n65%\nNon-limited (Paid ≥ $5.00)\nLimited (Free < $5.00)\n100,000Population échantillonnée (SRSWOR, N = 1,18 million)\n63.06%Comptes payants sans restriction (comptes « 61,490 »)\n±0.39%Marge d'erreur de l'intervalle de confiance à 99%\n~745,800Nombre extrapolé de comptes payants dans un ensemble de données comprenant 1,18 million de comptes bannis\nLa réalité structurelle : la liquidation de comptes à l'échelle industrielle\n\nPourquoi 63% des comptes bannis inclus dans l'échantillon seraient-ils des comptes payants ayant dépensé de l'argent réel dans la boutique de Valve ? Les opérateurs de botnets ne dépensent pas des millions de leur poche pour des comptes jetables. Ce ratio met en évidence le volume de comptes piratés et détournés circulant dans l'écosystème.\n\nCette échelle est directement observable sur les plateformes souterraines : sur des marchés tels que FSB Market (nom anonymisé ; le nom d’origine n’est pas indiqué ici), sur 550,000 Steam comptes (logs de vol de données, captures de hameçonnage, attaques par « credential stuffing ») sont activement proposés à la vente à tout moment (phishdestroy.io/live-intel). La place de marché authentifie les acheteurs et les vendeurs à l'aide de l'OpenID Steam propre à Valve, et ni FSB Market ni le forum associé est bloqué par le filtre de liens de Valve.\n\nComme le précise la section 06, Valve ne permet pas d'éliminer de manière proactive cette activité frauduleuse : 67.77% des escrocs signalés par la communauté n'ont fait l'objet d'aucune suspension pour escroquerie sur Steam, et 88.97% de la flotte automatisée reste totalement intacte. Les comptes circulent librement, s’authentifient via des API officielles et effectuent des transactions au sein de l’écosystème en toute impunité, ou presque.\n\nSchéma de l'architecture des preuves judiciaires et de l'application de la loi\nFlux interactif issu de 10,88 millions de comptes analysés, permettant d'identifier 100 000 cas empiriques et 53 500 escrocs confirmés · Cliquez sur les liens pour consulter les preuves brutes\nNiveau 01 · Recensement de 10,88 millions de véhicules automatisés\nLa plus grande population de robots d'automatisation autodéclarés sur Steam a franchi successivement l'API d'interdiction officielle de Valve. Cela prouve que les flottes de bots commerciaux opèrent en toute impunité sur 88.97% tout en versant des dizaines de millions en frais d'adhésion.\n9,680,599 88.97% Actif et intact\nComptes utilisant des logiciels automatisés et ne présentant aucun antécédent d'interdiction, quelle qu'en soit la nature.\nFichier JSON brut du recensement (1,2 Ko) ↗Consultez la section 01 ↗\n$26,802,495 Seuil minimal des recettes en magasin\nCollecté par Valve auprès de 5,360,499 membres sans restriction ayant dépassé le seuil minimum d'entrée de $5.00.\nAudit de la gestion des cartes ↗Valve $5 FAQ sur les règles ↗\n1,200,011 11.03% Sous-ensemble marqué\n99.8% ne fait l'objet que d'interdictions de nature purement symbolique au sein de la communauté ; les opérations restent autorisées sur 99.95% des comptes.\nRépartition par type de suspension ↗Base de données bannie (60,4 Mo) ↓\nNiveau 02 · 100,000 - Audit par échantillonnage empirique des comptes (N = 1,182,811)\nÉchantillon représentatif de SRSWOR évalué via des points de terminaison XML hérités. Marge d'erreur prouvée mathématiquement inférieure à ±0.4% avec un intervalle de confiance de 99%. Cela réfute l'affirmation selon laquelle les bots bannis seraient des comptes jetables gratuits.\n61,490 (63.06%) Comptes payants sans limite (dépenses $5+)\nPlus de 63% des comptes bannis correspondent à des transactions payantes. Cela permet d’estimer à environ 745,800 le nombre de comptes payants (seuil d’entrée de $3.73M+) dans le groupe des comptes bannis.\nRésultats limités au format CSV (2,1 Mo) ↓Rapport d'expertise 100k ↗\n36,021 (36.94%) Comptes gratuits avec fonctionnalités limitées (< $5.00)\nLa minorité de profils bannis qui correspondent au profil de « bot jetable » défini par Valve. Les comptes 2,489 n'étaient pas configurés ou étaient privés.\nExtrait de 100 000 échantillons au format CSV (8,5 Mo) ↓Analyse des dépenses MD ↗\n34.67% contre 63.93% Audit de nettoyage des profils\nValve ont remplacé les pseudonymes par des SteamID64 bruts sur 34,673 comptes, mais ont laissé les noms personnalisés et les avatars tels quels sur 63,928 compte banni.\nSection « Désinfection » ↗Aperçu de la feuille de route ↗\n34.59% Héritage Comptes anciens (créés entre 2003 et 2019)\nPlus d'un tiers des comptes suspendus avaient été créés il y a entre 5 et plus de 20 ans, ce qui prouve l'existence d'un détournement à grande échelle des comptes de joueurs de longue date de Steam.\nChronologie des époques ↗Refus d'assistance ↗\nNiveau 03 · 51,732 SteamRep Recensement des escrocs confirmés\nRecensement complet 100% des fraudeurs sanctionnés par la communauté, accompagné des historiques de discussion des victimes et des preuves de transactions, recoupé avec les API officielles Steam de suspension. Prouve l'échec systémique de l'application des règles.\n35,059 (67.77%) Aucune exclusion pour arnaque (impunité totale)\nPlus des deux tiers des fraudeurs identifiés ne font l'objet d'aucune interdiction de participation à la communauté ni d'aucune restriction commerciale de la part de Valve. Ils sont donc pleinement opérationnels pour mener leurs activités frauduleuses et ajouter de nouvelles victimes.\nSteamRep Interdictions d'API (2,6 Mo) ↓SteamRep Rapport d'audit ↗\n9,731 (18.81%) Économie / Embargos commerciaux\nLa seule sanction qui met fin à la liquidation des stocks. Elle concerne moins d'un cinquième des escrocs confirmés.\nSteamRep Source (2,1 Mo) ↓Consultez la section 06 ↗\n6,627 (12.81%) Exclusions pour tricherie non pertinentes (VAC uniquement)\nIls ont été bannis pour avoir utilisé des aimbots ou des wallhacks dans les jeux, alors que leurs activités de trafic et de hameçonnage restent toujours actives.\nVAC Analyse de la non-pertinence ↗Chronologie des mesures de sécurité ↗\nNiveau 04 · Défacement de sites wiki et failles d'infrastructure d'août 2026\nLa falsification de la documentation interne destinée aux développeurs, la suppression d'un éditeur communautaire et les failles de sécurité au niveau du périmètre non sécurisé sont documentées dans le dossier de preuves.\n1,200+ Rédacteurs Journaux des conflits du wiki VDC\nLes modérateurs de la communauté qui tentaient de corriger les liens de hameçonnage et les modèles de spam ont été systématiquement bloqués par des filtres automatisés, tandis que le personnel Valve ignorait les avertissements.\nRapport sur les conflits en Russie (127 Ko) ↗Rapport de classification (66 Ko) ↗\n12 To sans authentification Août 2026 : fuite d'actifs (CWE-284)\nValve a hébergé pendant plusieurs semaines 12 téraoctets de code interne et de versions prototypes sur un point de terminaison public ouvert, sans aucune authentification.\nValve Dossier sur l'incompétence (43 Ko) ↗Archives des preuves ↗\nFaille de sécurité chez CEVA Logistics Août 2026 : fuite de données à caractère personnel des clients\nLes noms, adresses et numéros de téléphone des acheteurs européens de Steam Deck ont fait l'objet d'une fuite provenant du partenaire logistique de Valve, déclenchant une vague d'attaques par hameçonnage.\nRapport d'incident ↗Historique des mesures coercitives ↗\n\nArtéfact d'échantillonnage : banned_100k_slice.csv (100,000 comptes). Résultats de l'audit : slice_100k_limited_results.csv. Rapport d'analyse complet : BANNED_100K_FORENSIC_ANALYSIS.md.\n\n08 — Méthode et limites\nComment ce texte a été interprété, et ce qu'il ne prétend pas\n\nTrois populations publiques, une API publique, un échantillonnage statistique rigoureux.\n\nEXÉCUTION ET INFORMATIONS D'IDENTIFICATION\n\nLe recensement ASF, le 100,000-compte SRSWOR et la SteamRep vérification croisée ont été réalisés par PhishDestroy participants à l’aide de leurs propres Steam comptes et clés API Web, dans le cadre du travail de la Coalition visant à lutter publiquement contre le hameçonnage et à interdire les escroqueries. L'auteur de ce dossier ne détient aucune clé d'API Web Steam et n'a personnellement effectué aucun scan en direct. L'agrégation, le hachage, la vérification et la publication ont été réalisés à partir des résultats fournis par les participants.\n\nPopulation\tD'où cela vient-il ?\tCe qui a été lu\nMembres de l'ASF\n10,880,610\tLa liste publique des membres du groupe communautaire ArchiSteamFarm Steam. La page du groupe de Steam affiche 5,360,499 membres (comptes non restreints uniquement) ; la liste des membres fournie par l'API a renvoyé 10,880,610 entrée au total, comptes restreints compris. L'utilisateur est automatiquement ajouté au groupe lors de la première exécution, à moins qu'il ne désactive explicitement le paramètre par défaut d'adhésion au groupe dans la configuration (AutoJoinSteamGroup / Statistiques), ce qui signifie que la liste des membres comprend des réseaux de bots commerciaux, des utilisateurs individuels qui laissent leur carte inactive, ainsi que des joueurs réguliers qui ont laissé l'option par défaut activée.\tGetPlayerBans pour chaque membre (signaux d'interdiction) ; GetPlayerSummaries pour les dates de création et le pays. Regroupés par lots de 100 identifiants, dédupliqués par SteamID64.\n100 000 comptes bannis SRSWOR Tranche\n100,000\tUn échantillon représentatif tiré au hasard de manière uniforme sans replacement à partir du corpus des 1,182,811 comptes bannis ($P = 8,45\\%$). La correction pour population finie donne une marge d’erreur de $\\pm 0,39\\%$ à un niveau de confiance de 99% ($Z = 2,576$).\tMonétisation et statut de compte limité (isLimitedAccount) vérifié via l'interface de profil XML héritée de Steam (?xml=1) via des pipelines de proxy distribués. Confirme le statut « 63.06% » (payé).\nSteamRep escrocs\n51,732\tRecensement complet 100% de tous les profils marqués comme « BANNIS » dans la base de données de réputation de la communauté SteamRep (51,732 profils au total). Aucun échantillonnage ni filtrage n'a été appliqué.\tISteamUser/GetPlayerBans/v1 pour tous les comptes 51,732, croisés avec le statut SteamRep. Confirme que 67.77% est exempt de toute interdiction liée à une arnaque.\nObjet de la revendication\n\nUniquement des taux empiriques et des estimations statistiquement bornées. Dans la population concernée par l’automatisation, 88.97% ne font l’objet d’aucune interdiction ; le sous-ensemble des comptes interdits est concentré sur la période récente (70% depuis 2020). Dans l’audit empirique des comptes 100,000, 63.06% des comptes bannis sont payants (non limités), avec une marge d’erreur mathématiquement prouvée inférieure à ±0.4%. Parmi les 51,732 escrocs confirmés, 67.77% ne font l’objet d’aucune suspension liée à l’escroquerie. Chaque chiffre est reproductible à partir de l’API Web de Valve.\n\nCe qui n'est pas revendiqué\n\nUne exclusion « Steam » ne comporte pas de champ « motif » ; aucune exclusion ne peut donc être attribuée ici à une cause spécifique. L'appartenance à un groupe ne prouve pas qu'un compte soit un bot automatisé : comme ASF autorise par défaut l'adhésion à un groupe à moins que cette option ne soit désactivée manuellement, la population mélange des fermes de comptes multiples à but commercial avec des comptes personnels de joueurs lambda et d'amateurs. Le pays est déclaré par les utilisateurs eux-mêmes, et une mention « SteamRep » correspond à une décision de la communauté, et non à un jugement rendu par un tribunal. Aucun individu n'est nommé.\n\nPourquoi est-ce important ?\n\nValve dispose de la même API, de sa propre base de données en arrière-plan et des motifs d’exclusion que cette analyse ne peut pas détecter. Il peut exécuter cette requête sur l’ensemble de l’espace d’identifiants en quelques secondes. La mesure permettant à un tiers de vérifier une allégation d’application de la règle concernant un numéro n’a jamais été publiée par la seule partie capable de la produire avec une fidélité totale. Il s’agit ici d’une estimation externe, proposée afin que la question puisse être posée en s’appuyant sur un chiffre.\n\nÀ lire ensuite : l'économie des cartes pratiquée par cette population → · assistance, accès et vol → · le dossier complet →",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Quelle est l’ampleur de cette ferme Steam ? Nous l’avons comptée."
          },
          {
            "level": 2,
            "id": null,
            "text": "Dix millions de comptes, dont neuf sur dix n'ont pas été utilisés"
          },
          {
            "level": 3,
            "id": null,
            "text": "ASF rejoint le groupe pour vous"
          },
          {
            "level": 3,
            "id": null,
            "text": "10,880,610 nombre total d'entrées"
          },
          {
            "level": 3,
            "id": null,
            "text": "88.97% propre"
          },
          {
            "level": 3,
            "id": null,
            "text": "Sur 10,880,610 comptes, combien ont atteint Valve ?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ce que cette flotte a déjà coûté Valve pour voir le jour"
          },
          {
            "level": 2,
            "id": null,
            "text": "Où se trouve la flotte"
          },
          {
            "level": 3,
            "id": null,
            "text": "Comptes bannis par pays déclaré"
          },
          {
            "level": 2,
            "id": null,
            "text": "Des comptes récents, et non un arriéré historique"
          },
          {
            "level": 3,
            "id": null,
            "text": "À quel moment les comptes bannis ont-ils été créés ?"
          },
          {
            "level": 2,
            "id": null,
            "text": "Lorsque Valve intervient, c'est au cours de la première année"
          },
          {
            "level": 3,
            "id": null,
            "text": "Depuis combien de temps le compte existait-il au moment où la suspension a été prononcée ?"
          },
          {
            "level": 2,
            "id": null,
            "text": "Lorsque Valve s'active, cela n'arrête pas le bot"
          },
          {
            "level": 3,
            "id": null,
            "text": "Pour quoi sont réellement bannis les 11% qui ont été bannis ?"
          },
          {
            "level": 2,
            "id": null,
            "text": "Les escrocs Valve, passons à autre chose : le recensement complet 51,732"
          },
          {
            "level": 3,
            "id": null,
            "text": "Escrocs confirmés, selon que Valve a appliqué ou non une suspension liée à une arnaque (recensement complet)"
          },
          {
            "level": 4,
            "id": null,
            "text": "Deux populations, une seule découverte"
          },
          {
            "level": 2,
            "id": null,
            "text": "L'audit empirique des comptes « 100,000 » : les botnets ne sont pas des comptes gratuits jetables"
          },
          {
            "level": 3,
            "id": null,
            "text": "100,000 Tranche impartiale"
          },
          {
            "level": 3,
            "id": null,
            "text": "Marge d'erreur < ±0.4%"
          },
          {
            "level": 3,
            "id": null,
            "text": "Pourquoi n'importe quel 100k donne le même résultat"
          },
          {
            "level": 3,
            "id": null,
            "text": "100,000 Comptes bannis : comptes payants ($5+ dépenses en boutique) vs comptes gratuits à accès limité"
          },
          {
            "level": 3,
            "id": null,
            "text": "La réalité structurelle : la liquidation de comptes à l'échelle industrielle"
          },
          {
            "level": 2,
            "id": null,
            "text": "Comment ce texte a été interprété, et ce qu'il ne prétend pas"
          },
          {
            "level": 3,
            "id": null,
            "text": "Objet de la revendication"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ce qui n'est pas revendiqué"
          },
          {
            "level": 3,
            "id": null,
            "text": "Pourquoi est-ce important ?"
          }
        ],
        "links": [
          "https://help.steampowered.com/en/faqs/view/71D3-35C2-AD96-AA3A",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/asf-ban-census-2026-09-23.json",
          "https://phishdestroy.io/steam_dossier/fr/VALVE_EVIDENCE_PACK/databases/steamrep_steam_bans.csv",
          "https://phishdestroy.io/live-intel/?category=steam",
          "https://phishdestroy.io/steam_dossier/fr/card_economy.html",
          "https://phishdestroy.io/steam_dossier/fr/VALVE_EVIDENCE_PACK/databases/banned_archiasf_massive.csv",
          "https://phishdestroy.io/steam_dossier/fr/VALVE_EVIDENCE_PACK/databases/slice_100k_limited_results.csv",
          "https://phishdestroy.io/steam_dossier/fr/VALVE_EVIDENCE_PACK/reports/BANNED_100K_FORENSIC_ANALYSIS.md",
          "https://phishdestroy.io/steam_dossier/fr/VALVE_EVIDENCE_PACK/databases/banned_100k_slice.csv",
          "https://phishdestroy.io/steam_dossier/fr/VALVE_EVIDENCE_PACK/reports/STEAM_BANNED_LIMIT_ANALYSIS.md",
          "https://phishdestroy.io/steam_dossier/fr/VALVE_EVIDENCE_PACK/INVESTIGATION_OVERVIEW.md",
          "https://phishdestroy.io/steam_dossier/fr/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/fr/VALVE_EVIDENCE_PACK/reports/STEAMREP_VS_STEAM_AUDIT.md",
          "https://phishdestroy.io/steam_dossier/fr/VALVE_EVIDENCE_PACK/databases/SteamRep_Profiles_BannedCaution_2024.csv",
          "https://phishdestroy.io/steam_dossier/fr/security_timeline.html",
          "https://phishdestroy.io/steam_dossier/fr/VALVE_EVIDENCE_PACK/reports/russian_conflicts_report.json",
          "https://phishdestroy.io/steam_dossier/fr/VALVE_EVIDENCE_PACK/reports/classification_report.json",
          "https://phishdestroy.io/steam_dossier/fr/VALVE_EVIDENCE_PACK/reports/VALVE_INCOMPETENCE_REPORT.md",
          "https://phishdestroy.io/steam_dossier/fr/steam_evidence_archive.html",
          "https://phishdestroy.io/steam_dossier/fr/steam_enforcement_evidence.html",
          "https://phishdestroy.io/steam_dossier/fr/#insider-threat",
          "https://phishdestroy.io/steam_dossier/fr/"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/fr/enforcement_audit.content.json",
      "export_json_sha256": "2040fb96497f40174666402696beb0abd59c1a1e7b7bad9a184059e032dff66c"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "fr/index.html",
      "language": "fr",
      "title": "Le dossier « Steam » : règles, itinéraires et responsabilité",
      "source_url": "https://phishdestroy.io/steam_dossier/fr/index",
      "source_html_sha256": "72f33cad6d95d8bb9f4d587699b27b5cbdbe1b3580bb78f3de98c166f8a546b0",
      "exported_at": "2026-09-29T00:17:38.163Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "exhibit-gallery-section",
            "source": "https://phishdestroy.io/steam_dossier/fr/index#exhibit-gallery-section"
          }
        ],
        "raster_images_replaced": 2
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "index.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/fr/index.pdf?v=print-20260929-v5",
        "sha256": "8b1a9112f19405ee54c67fe4dcadab29eebacb1ffbb5d33c6020d9e826fdb44f",
        "bytes": 980361,
        "pages": 110
      },
      "integrity": {
        "signed_object": "index.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "index.content.json.asc",
        "digest_file": "index.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify index.content.json.asc index.content.json",
          "sha256sum -c index.content.json.sha256"
        ]
      },
      "content": {
        "text": "Section 1 — Résumé de l'affaire\nLe record. L'histoire. Les questions sans réponse.\nContexte et limites de la source\n\nSix conclusions, chacune étant liée à un document public daté. Les sections détaillées suivent le même ordre : dossier technique (partie A), règlement et mesures d'application (partie B), cadres juridiques (partie C), puis les annexes contenant les pièces à conviction principales.\n\nSix conclusions. Chacune établit un lien entre une règle écrite, un document daté et une hypothèse que les éléments de preuve permettent de vérifier.\n\n1. Hôtes d'authentification à domaine distinct — 44 routes · 26 paires divisées\n\nLes registres des personnes inscrites 44 plateformes s'authentifiant via un domaine distinct pouvant faire l'objet d'un enregistrement. Cinq autres itinéraires sont en attente de vérification et d'une date RDAP ; leur validation porterait le total à 47. Ils ne sont pas pris en compte dans le chiffre de 44 ni dans le tableau des âges. — 27, avec un dossier de justification publié pour chaque itinéraire et 17 autres issus d'une collecte manuelle, répertoriés séparément. Dans 26 paires de filtres séparés le domaine principal est BLOQUÉ dans le filtre de liens Steam, alors que le proxy utilisant ses identifiants ne l'est pas. Il ne s'agit pas de domaines jetables : csgogem.com est bloqué tandis que api.csgem.com, l'hôte portant l'identifiant Steam, est enregistré depuis mars 2014 — 12 ans et 6 mois. Valve reçoit ce nom d'hôte dans chaque requête OpenID et le affiche à l'utilisateur sur sa propre page de connexion. Le tableau complet, les durées de validité par route et les sources sont présentés à la section 3.\n\nSuivez l'itinéraire →\n2. 2016 : le mécanisme a été baptisé et la date limite a été fixée\n\nLe 13 juillet 2016, Valve a décrit publiquement comment les sites de jeux d’argent utilisaient Steam OpenID et des comptes de trading automatisés, et les mises en demeure de son avocat, datées du 20 juillet 2016, ont fixé un délai de dix jours. Aucun rapport d’application de la réglementation par opérateur n’a été publié depuis. Dix ans après l’expiration de ce délai, le même mécanisme est utilisé sur des serveurs d’authentification de domaines distincts qui n’ont renvoyé aucun blocage par le filtre de liens sur 2026-09-21.\n\nLire la lettre ouverte adressée au WSGC →\n3. Corrélation des appareils, sur papier à en-tête de l'avocat\n\nDans la correspondance reproduite ici, l'avocat de Valve a décrit une corrélation au niveau des appareils reliant un appareil à plusieurs comptes — une fonctionnalité que le service d'assistance de Steam avait auparavant déclaré aux utilisateurs comme étant techniquement impossible. La question qui reste en suspens est de savoir quels enregistrements au niveau des appareils Valve détient et sur quelle base l’accès à ces enregistrements est refusé aux titulaires de comptes.\n\nLire la note →\n4. Deux réponses concernant l'accès aux données. L'une a refusé de les communiquer, l'autre les a divulguées.\n\nOctobre 2025 : L'avocat de Valve a répondu à une demande au titre de l'article 15 en joignant une annexe de 830 pages dans laquelle les passages caviardés ont été masqués par des marques sur le texte au lieu d'être supprimés — 902,270 caractères révèlent des informations à l'aide d'un outil d'extraction standard, y compris les identifiants tiers que ces barres étaient censées masquer. C'est l'article 15, paragraphe 4, qui justifie l'existence de ces barres. Septembre 2026 : Le dossier HT-2YBP-F7JP-D4VB a été classé au bout de trois jours, accompagné d'un lien vers la page « Données du compte » en libre-service — aucune donnée n'y figurait et aucune base juridique n'était mentionnée. Le délai d'un mois prévu à l'article 12, paragraphe 3, n'était pas encore écoulé au moment de la publication ; l'objection porte sur le fond.\n\nConsultez la vérification de la rédaction →Consulter la fiche du ticket →\n5. Le marché au-dessus du plafond de Steam\n\nSteam limite la capitalisation boursière à environ $1,800. Sur cinq places de marché, selon un instantané daté du 23 septembre 2026, 248 catégories d'articles CS2 dont le prix dépasse ce plafond, et ce de manière indépendante, par au moins deux d'entre eux, et les 248 sont absents de Steam; un Dragon Lore neuf d’usine est proposé à partir de $10,941 sur 389 exemplaires répertoriés sur les cinq plateformes (le chiffre concernant uniquement CSFloat à la section 13, issu de l'instantané du 20 septembre, est de $10,623.95 sur 62 offres). La vente à ces prix nécessite une plateforme externe, tandis que le transfert d’objets s’effectue toujours à Steam.\n\nSuivre le cours et effectuer le virement →\n6. La règle est explicite ; la piste d'audit ne l'est pas\n\nLe contrat d’abonnement réserve Steam à un usage personnel et non commercial, interdit toute exploitation commerciale sauf autorisation expresse, interdit l’utilisation de scripts et de bots, et autorise la résiliation du compte. Valve a étendu cette disposition aux opérateurs de jeux d’argent en 2016. Par ailleurs, selon le compte d’ingénierie de CSFloat, Valve a fermé IEconItems_730/GetPlayerItems en 2017, suppression de l'accès public aux identifiants d'éléments d'origine (aucun journal des modifications Valve trouvé).\n\nPlacez la règle à côté du réseau →\n2016 / Demande écrite 10 jours\nDate limite mentionnée dans les avis envoyés en juillet 2016 par l’avocat aux sites de jeux d’argent. Lettre ouverte à la WSGC : section 2.\n2017 / Journal d'audit public Accès par identifiant fermé\nCSFloat enregistre la perte des identifiants d'origine des éléments.\nCorrespondance avec les avocats Corrélation entre appareils\nUn appareil lié à des dizaines de comptes piratés.\nRegistre des itinéraires Bloqué, mais je continue à me connecter\nLa règle : La déclaration de Valve de 2016 interdit l'exploitation d'une activité de jeux d'argent sur Steam OpenID. Le bilan : Le « Link Filter » héberge 26 domaines principaux, tandis que l'hébergeur gérant la connexion « Steam » de chacun d'entre eux est en service depuis — celui de csgogem.com fonctionne depuis 12 ans et 6 mois.\nSection 2 — Lettre ouverte\nLettre ouverte à la Commission des jeux de l'État de Washington\n\nCes dix jours se sont transformés en dix ans. La Commission n'a pas reçu de réponse à la question qu'elle avait posée en 2016 à Valve sous la forme d'un relevé détaillé par opérateur ; cette lettre lui demande de rouvrir le dossier.\n\nCOMMUNIQUÉ PUBLIC · COMMISSION DES JEUX DE L'ÉTAT DE WASHINGTON\n\nDix jours se sont transformés en dix ans.Rouvrez la fiche.\n\nÀ la Commission des jeux de l'État de Washington :\n\nEn 2016, le directeur David Trujillo a demandé à Valve de présenter les mesures qu’elle avait prises pour mettre fin à l’utilisation des « skins » Steam à des fins de jeux d’argent. Chris Stearns, alors président, et la Commission se sont heurtés à un secteur reposant sur des objets émis par Valve et des transferts Steam. Depuis, les deux hommes ont quitté leurs fonctions au sein de la Commission. La question qu’ils ont posée à Valve reste d’actualité.\n\nLe directeur juridique de Valve, Karl Quackenbush, a donné dix jours aux opérateurs de jeux d’argent pour mettre fin à l’utilisation commerciale des comptes Steam. Dans sa réponse adressée à votre Commission en octobre, Valve a nié avoir facilité les jeux d’argent, a indiqué avoir envoyé des lettres de mise en demeure à plus de quarante sites et a déclaré avoir désactivé les comptes associés. Elle a également défendu le maintien des services de trading Steam et d’OpenID, au motif que ces services profitaient aux clients et aux développeurs de jeux. C'était une démonstration de pouvoir. Cela mérite d'être mis à l'épreuve, et non d'être accepté sans discussion.\n\nSelon notre analyse, la réponse de Valve n’a pas démontré que les mesures coercitives choisies étaient à la hauteur de l’ampleur du réseau qu’elle décrivait. Une lettre de menace adressée à un opérateur n’équivaut pas à un blocage durable des comptes Steam, de l’infrastructure de trading et des voies d’authentification qui permettent à l’activité de fonctionner. Selon les estimations rapportées, À lui seul, le CS:GO Lounge a enregistré plus de $1 milliards de volume de paris en 2016; il s’agit là d’une estimation externe des mises, et non d’un chiffre d’affaires de Valve, et l’activité initiale du site, qui consistait à parier des « skins », a par la suite été interrompue. L’ampleur du phénomène a rendu indispensable la mise en place de mesures de contrôle vérifiables.\n\nAujourd'hui, celui de Valve Contrat d'abonnement archivé 2026-09-21 ↗ limite l'exploitation commerciale, sauf dans les cas expressément autorisés, et interdit par ailleurs certaines formes d'automatisation. Notre registre des itinéraires obsolète les enregistrements déclarés OpenID renvoient les hôtes des services externes ; openid.realm et openid.return_to sont des champs transmis à Steam, et non des secrets qui lui sont cachés. Notre Vérifications du filtre de liens présente des cas où une adresse principale a fait l'objet d'un avertissement, mais pas l'hôte de connexion associé. Un résultat de filtrage ne suffit pas à lui seul à prouver que Valve a autorisé une connexion ou qu'un bot particulier a contourné une suspension de compte. Cela prouve bien qu'un avertissement figurant sur la page d'accueil ne saurait constituer une réponse exhaustive en matière d'accessibilité.\n\nL'existence de fonctions commerciales et OpenID utiles et licites Steam ne permet pas non plus de déterminer si les opérateurs interdits ont effectivement été exclus. Les propres règles de Valve prévoient des exceptions expresses. Si Valve s’appuie sur cette distinction, la Commission devrait lui demander d’identifier l’autorisation, les contrôles des comptes et les critères d’application applicables aux entreprises commerciales de « skins », ainsi que les utilisations spécifiques non liées aux jeux d’argent qu’elle a invoquées en 2016. La simple possibilité d’une utilisation licite ne constitue pas une réponse face à une utilisation interdite documentée.\n\nNous demandons à la Commission de réexaminer son dossier de 2016 et de demander un compte rendu opérateur par opérateur : quels comptes Steam et robots de trading ont été désactivés après les préavis de dix jours ; si les comptes associés ou les serveurs de retour ont fait l’objet d’une surveillance ; quels opérateurs ont par la suite recouvré leur accès ; quelles dérogations ont été accordées ; et quels documents étayent la déclaration de Valve devant la Commission. Publiez tout ce que la loi autorise le public à consulter. Comparez ces documents avec les itinéraires actuels et avec les interventions ultérieures de Valve, notamment OPSkins en 2018 archivé 2026-03-07 ↗.\n\nL'avis fixait un délai de dix jours en juillet 2016 ; dix ans, c'est suffisamment long pour déterminer si cette mesure a été mise en œuvre. La Commission devrait vérifier la cohérence du rapport de Valve de 2016 avec les infrastructures encore visibles aujourd’hui.\n\nEnquête « Dossier Steam » · Déclaration publique, 20 septembre 2026\n\nCommunication de la Commission de 2016 ↗ archivé 2026-05-20 ↗ · Réponse de Valve datée de 2016 (copie du document) ↗ · Déclaration d'OpenID de Valve pour 2016 ↗ archivé 2026-09-21 ↗ · Accord actuel Steam ↗ archivé 2026-09-21 ↗ · Chronologie de l'échange de 2016 : Section 11 →\n\nPartie A — Dossier technique · Section 3\nLe site est bloqué. La page de connexion, elle, ne l'est pas.\n\n26 domaines principaux bloqués. Le proxy d'authentification associé à chacun d'entre eux, ainsi que sa durée de fonctionnement. Ces serveurs d'authentification distincts ne sont pas de simples adresses secondaires : chacun d'entre eux est un proxy d'authentification pour Steam, situé entre la plateforme et le point de terminaison OpenID de Valve et prenant en charge la connexion que le domaine bloqué ne peut plus effectuer ouvertement. Valve a configuré le Link Filter comme point d’accès principal. La connexion a continué à passer par le proxy : csgogem.com est bloqué, et api.csgem.com est enregistrée depuis mars 2014 — douze ans et demi. Chaque jour, cet hébergeur envoyait son propre nom d'hôte au point de terminaison OpenID de Valve, et Steam le renvoyait directement à l'utilisateur sur la page de connexion. Valve est la ligne principale par laquelle passent tous ces itinéraires ; il n'a pas besoin de les rechercher. C’est ce que mesure cette section : non pas l’existence d’un avertissement, mais le nombre d’années pendant lesquelles le tracé situé en aval de l’avertissement reste ouvert. Le registre recense 44 tracés de domaines distincts, dont 27 sont accompagnés d’un dossier justificatif publié pour chaque tracé — voir le tableau ci-dessous. Prenez un exemple, puis évaluez-les tous.\n\nFigure 3.1 — Les deux itinéraires, représentés graphiquement.\n\nUne plateforme, un utilisateur, deux requêtes provenant du même navigateur. Le filtre de liens de Valve s'applique aux deux. Il bloque celle qui contient un lien et laisse passer celle qui contient les identifiants de connexion. Toutes les mesures présentées dans cette section correspondent à la durée pendant laquelle la route inférieure reste ouverte.\n\nThe player\none browser, one session\nrollbit.com\nthe platform's main domain\nrbsnin.com\nseparate authentication host\nLINK FILTER\n✕ BLOCKED\nLINK FILTER\n✓ CLEAN\nsteamcommunity.com\nOpenID endpoint · signs in\nno route\nLien publié le Steam — interrompuDemande de connexion — mots de passeChèques conservés datés des 19 et 21 septembre 2026\n\nLes deux requêtes sont visibles par Valve, mais une seule fait l'objet d'une action. Le filtre de liens est une liste Valve, vérifiée par un service Valve. La requête OpenID transmet le nom de l’hôte d’authentification au point de terminaison de Valve, qui l’affiche directement sur la page de connexion. Le nom d’hôte figure de toute façon dans la requête ; ce qui change, c’est si une action est effectuée avec celui-ci.\n\nUne seule plateforme. Deux itinéraires différents.ROLLBIT / OBSERVATIONS ENREGISTRÉES\nÉtape 5 / 5\n\nLa requête atteint Steam. Le parcours observé a abouti au formulaire de connexion de Steam. Les auteurs n'ont pas finalisé la connexion. Le blocage du lien vers le domaine principal n'a pas empêché ce parcours d'aboutir au formulaire.\n\n01 VÉRIFICATION DU FILTRE DE LIENS\nDESTINATIONrollbit.comLe domaine principal de la plateforme\nFILTRE STEAM LINKVérifie le lienUn système d'alerte de destination distinct\nRÉSULTAT ENREGISTRÉLien bloquéLes 19 et 21 septembre 2026\n02 LE PARCOURS D'ACCÈS OBSERVÉ\nSUR LE QUAISe connecter avec SteamLa plateforme lance une requête OpenID\nHÔTE D'AUTHENTIFICATION DISTINCTrbsnin.comAucun bloc « Filtre de liens » dans la vérification enregistrée\nSTEAMFormulaire de connexion affichéL'hôte demandé apparaît dans l'avis de Steam\nVérifiez les notes de capture d'origine, la date d'enregistrement et les détails du protocole\nÀ quoi ressemble la mise en œuvre de la mesure Valve ?\nDomaine principal : bloqué\nUtilisateur\n→\nrollbit.com\n(domaine principal)\n↓\nFILTRE STEAM LINK — BLOQUÉ\n« Lien bloqué ! » — signalé comme potentiellement malveillant\nrollbit.com a renvoyé un blocage par le filtre de liens pour 2026-09-19 et 2026-09-21 (vérification sans authentification ; HTML brut et SHA-256 enregistrés). Une trace visible et vérifiable.\nCe qui se passe réellement — l'authentification\nHôte d'authentification : non bloqué\nUtilisateur\n→\nrollbit.com\n« Se connecter avec Steam »\n↓\nRediriger via un serveur d'authentification distinct :\nrbsnin.comFiltre de liens : CLEAN\nenregistré 2026-09-18T09:34:52Z (Verisign RDAP)\n↓\nSteam Avis sur la page de connexion (2026-09-20) :\n\"Note that rbsnin.com is not affiliated with Steam or Valve\"\nSteam affiche cet avis à partir du domaine OpenID (openid.realm) de la requête qu'il a reçue.\n↓\nSteam formulaire de connexion hébergé sur un serveur distinct\nLes auteurs n'ont pas mené la procédure de connexion jusqu'au bout ; le processus a été observé jusqu'au formulaire « Steam ».\nValve reçoit le nom d'hôte « return_to / realm » à chaque requête de ce type. rbsnin.com n'a renvoyé aucun blocage du filtre de liens sur 2026-09-21.\nSur demande\nEn tant que fournisseur OpenID, Steam reçoit le nom d'hôte d'authentification à chaque demande d'authentification : celui-ci parvient aux serveurs de Valve dans le openid.return_to et openid.realm paramètres.\nEnvoyé par le site\nL'hôte d'authentification n'est pas détecté lors de l'analyse — la plateforme l'envoie à Steam dans chaque requête. Conformément à la section 9.1 de la spécification OpenID 2.0 return_to est techniquement facultatif, mais sans lui, Steam ne peut pas fournir le résultat de la connexion ; il est donc de fait obligatoire pour que la connexion Steam fonctionne. Steam affiche même le nom d'hôte à l'utilisateur («<host> n'est affilié ni à Steam ni à Valve« »).\n14 ans\nIl s'agit de l'âge de l'hôte d'authentification le plus ancien qui comporte encore Steam connexions lors de la vérification 2026-09-21 (dota2.net, enregistré depuis 2011-10-29) ; le plus récent date de trois jours (rbsnin.com). Ne considérez pas le chiffre « 0 hôtes d'authentification bloqués » comme une conclusion. Un hôte d'authentification bloqué rendrait purement et simplement inopérante la fonctionnalité « Se connecter avec Steam » de la plateforme ; par conséquent, un registre constitué à partir de connexions réussies ne peut contenir que des hôtes qui n'ont jamais été bloqués. Ce n’est pas le nombre de blocages qui est significatif, mais le nombre d’années pendant lesquelles le domaine principal est resté dans le filtre de liens alors que l’identifiant associé continuait de fonctionner.\nHôtes d'authentification à domaine distinct : date d'enregistrement par rapport au domaine principal (30 routes : les 25 identifiées lors de l'audit du navigateur 2026-09-21, plus 5 ajoutées le 2026-09-22)\nPlateforme\tFiltre de liens : principal\tHôte d'authentification\tFiltre de liens : hôte d'authentification\tHôte d'authentification enregistré\tSource de l'observation\tDossier de preuves\nRollbit\nrollbit.com · inscrit 2014-11-08\n\tBLOQUÉ\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\trbsnin.com\tNET\n2026-09-21 · HTML brut (pas d'archive Wayback)\n\t2026-09-18\n09:34:52Z, Verisign RDAP\n\tSteam message d'avertissement sur la page de connexion, 2026-09-20\trollbit.com.json\nSkin.Club\nskin.club · inscription 2017-09-04\n\tBLOQUÉ\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\tsc-auth.net\tNET\n2026-09-21 · Wayback 2026-09-21\n\t2019-04-02\nRDAP\n\tSteam Avis sur la page de connexion\tskin.club.json\nHowl.GG\nhowl.gg · inscription 2017-03-16\n\tBLOQUÉ\n2026-09-18, 19/09, 21/09 · Wayback 2026-09-21\n\thowl.uno\tNET\n2026-09-21 · Wayback 2026-09-21\n\t2026-08-11\nRDAP\n\tCapture en direct du navigateur + URL OpenID fournie\thowl.gg.json\nDuelbits\nduelbits.com · enregistrement 2020-02-03\n\tBLOQUÉ\n2026-09-21 · Wayback 2026-09-21\n\tswitchflips.com\tNET\n2026-09-21 · Wayback 2026-09-21\n\t2020-04-21\nRDAP\n\tURL OpenID fournie\tduelbits.com.json\nCSGOFast\ncsgofast.com · inscrit depuis 2015-03-27\n\tBLOQUÉ\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\tsteam-login.authtofast.com\tNET\nauthtofast.com, 2026-09-21 · Wayback 2026-09-21\n\t2026-06-30\nauthtofast.com, RDAP\n\tCapture en direct du navigateur + URL OpenID fournie\tcsgofast.com.json\nFarmskins\nfarmskins.com · reg. 2016-03-23\n\tBLOQUÉ\n2026-09-19, 2026-09-21 · HTML brut\n\tsteam.kobal.cc\tNET\n2026-09-19, 2026-09-21 · HTML brut\n\t2017-01-07\nkobal.cc, RDAP\n\tCapture en direct du navigateur + URL OpenID fournie\tfarmskins.com.json\nCobaltLab\ncobaltlab.tech\n\tBLOQUÉ\n2026-09-21 · HTML brut\n\tcobaltauth.com\tNET\n2026-09-21 · HTML brut\n\t2025-01-07\nRDAP\n\tURL OpenID fournie\tcobaltlab.tech.json\nCSGO.NET\ncsgo.net · inscrit 2012-07-22\n\tBLOQUÉ\n2026-09-21 · HTML brut\n\tcn2.easylot.net\tNET\n2026-09-21 · HTML brut\n\t2016-09-03\neasylot.net, RDAP\n\tCapture en direct depuis le navigateur\tcsgo.net.json\nGGDrop\nggdrop.com\n\tBLOQUÉ\n2026-09-21 · HTML brut\n\tggauth.com\tNET\n2026-09-21 · HTML brut\n\t2023-05-03\nRDAP\n\tURL OpenID fournie\tggdrop.com.json\nRustChance\nrustchance.com\n\tBLOQUÉ\n2026-09-21 · HTML brut\n\thgfuihd.com\tNET\n2026-09-21 · HTML brut\n\t2019-01-27\nRDAP\n\tURL OpenID fournie\trustchance.com.json\nSkin.Fans\nskin.fans\n\tBLOQUÉ\n2026-09-21 · HTML brut\n\tauth.skinfans.com\tNET\n2026-09-21 · HTML brut\n\t2018-07-16\nskinfans.com, RDAP\n\tURL OpenID fournie\tskin.fans.json\nSkinport\nskinport.com · inscription 2018-09-05\n\tBLOQUÉ\n2026-09-21 · HTML brut\n\tskinport.app\tNET\n2026-09-21 · HTML brut\n\t2020-06-20\nRDAP\n\tCapture en direct du navigateur + URL OpenID fournie\tskinport.com.json\nSkins.Cash\nskins.cash\n\tBLOQUÉ\n2026-09-21 · HTML brut\n\tskinscash.live\tNET\n2026-09-21 · HTML brut\n\t2019-12-05\nRDAP\n\tURL OpenID fournie\tskins.cash.json\nTF2Hunt\ntf2hunt.com · inscrit 2018-01-13\n\tBLOQUÉ\n2026-09-21 · HTML brut\n\trstspcl.com\tNET\n2026-09-21 · HTML brut\n\t2020-08-08\nRDAP\n\tCapture en direct du navigateur + URL OpenID fournie\ttf2hunt.com.json\nCSGOGem\ncsgogem.com · reg. 2016-10-16\n\tBLOQUÉ\n2026-09-22 · HTML brut\n\tapi.csgem.com\ncsgem.com — nom de domaine distinct pouvant faire l'objet d'un enregistrement\n\tNET\n2026-09-22 · HTML brut\n\t2014-03-08\ncsgem.com, RDAP — le plus ancien du registre\n\tCollecte manuelle + Capture via le filtre de liens\tlinkfilter-2026-09-22.json\nGamdom\ngamdom.com · inscription 2016-07-29\n\tBLOQUÉ\n2026-09-22 · HTML brut\n\tlogin.gambldom.com\ngambldom.com — une lettre de différence par rapport à la marque\n\tNET\n2026-09-22 · HTML brut\n\t2017-09-24\ngambldom.com, RDAP\n\tCollecte manuelle + Capture via le filtre de liens\tlinkfilter-2026-09-22.json\n12CS\n12cs.fail · reg. 2026-03-24\n\tBLOQUÉ\n2026-09-22 · HTML brut\n\tfail.games\tNET\n2026-09-22 · HTML brut\n\t2021-08-24\nfail.games, RDAP\n\tCollecte manuelle + Capture via le filtre de liens\tlinkfilter-2026-09-22.json\nCSGOEmpire\ncsgoempire.com · inscrit 2015-06-10\n\tNET\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\tcsgoempirelogin4.com\nl'un des dix domaines numérotés de login1 à login10\n\tNET\n2026-09-21 · Wayback 2026-09-21\n\t2020-07-20\n05:49:17Z, Verisign RDAP\n\tCapture en direct depuis le navigateur\tcsgoempire.com.json\nCS.MONEY\ncs.money\n\tNET\n2026-09-21 · HTML brut\n\tauth.dota.trade\tNET\n2026-09-21 · HTML brut\n\t2016-07-15\ndota.trade, RDAP\n\tSteam Avis sur la page de connexion\tcs.money.json\nCSFloat\ncsfloat.com · reg. 2021-07-11\n\tNET\n2026-09-21 · HTML brut\n\tcsgofloat.com\nancien nom de domaine de la marque de l'opérateur ; nom de domaine distinct pouvant faire l'objet d'un enregistrement, ne constituant pas un indicateur de manœuvre frauduleuse\n\tNET\n2026-09-21 · HTML brut\n\t2015-09-29\nRDAP\n\tCapture en direct depuis le navigateur\tcsfloat.com.json\nG4Skins\ng4skins.com\n\tNET\n2026-09-21 · HTML brut\n\tauth.g4s.to\tNET\n2026-09-21 · HTML brut\n\t2021-05-30\ng4s.to, RDAP\n\tURL OpenID fournie\tg4skins.com.json\nJuice.GG\njuice.gg\n\tNET\n2026-09-21 · HTML brut\n\tletmeinjuice.com\tNET\n2026-09-21 · HTML brut\n\t2024-04-15\nRDAP\n\tURL OpenID fournie\tjuice.gg.json\nMarket.CSGO\nmarket.csgo.com\n\tNET\n2026-09-21 · HTML brut\n\tdota2.net\tNET\n2026-09-21 · HTML brut\n\t2011-10-29\nRDAP\n\tCapture en direct dans le navigateur + URL OpenID fournie\tmarket.csgo.com.json\nRust.TM\nrust.tm\n\tNET\n2026-09-21 · HTML brut\n\tdota2.net\tNET\n2026-09-21 · HTML brut\n\t2011-10-29\nRDAP\n\tURL OpenID fournie\trust.tm.json\nCSGOLounge\ncsgolounge.com · inscrit 2013-08-14\n\tNET\n2026-09-22 · HTML brut\n\tdota2.net\ntroisième interface utilisateur sur cet hôte d'authentification\n\tNET\n2026-09-22 · HTML brut\n\t2011-10-29\ndota2.net, RDAP\n\tCollecte manuelle + Capture via le filtre de liens\tlinkfilter-2026-09-22.json\nDota2Lounge\ndota2lounge.com · inscrit 2012-08-10\n\tNET\n2026-09-22 · HTML brut\n\tdota2.net\nquatrième interface utilisateur sur cet hôte d'authentification\n\tNET\n2026-09-22 · HTML brut\n\t2011-10-29\ndota2.net, RDAP\n\tCollecte manuelle + Capture via le filtre de liens\tlinkfilter-2026-09-22.json\nSkinBaron\nskinbaron.de\n\tNET\n2026-09-21 · HTML brut\n\tskinbaron.com\nmême marque, TLD différent\n\tNET\n2026-09-21 · HTML brut\n\t2015-12-22\nRDAP\n\tURL OpenID fournie\tskinbaron.de.json\nTF2Royal\ntf2royal.com · inscrit 2022-08-17\n\tNET\n2026-09-21 · HTML brut\n\ttf2auth.com\tNET\n2026-09-21 · HTML brut\n\t2021-07-27\nRDAP\n\tCapture en direct depuis le navigateur + URL OpenID fournie\ttf2royal.com.json\nTradeit\ntradeit.gg\n\tNET\n2026-09-21 · HTML brut\n\tconnect-tradeit.com\tNET\n2026-09-21 · HTML brut\n\t2022-02-23\nRDAP\n\tURL OpenID fournie\ttradeit.gg.json\nMise à niveau\nupgrader.pro\n\tNET\n2026-09-21 · HTML brut\n\tupgauth.space\tNET\n2026-09-21 · HTML brut\n\t2026-08-14\nRDAP\n\tURL OpenID fournie\tupgrader.pro.json\nSource : steamcommunity.com/linkfilter, requête GET non authentifiée, 2026-09-21, 53 hôtes, intervalle de 3 s ; steam_tos_assets/linkfilter-recheck-2026-09-21.json; code HTML brut dans steam_tos_assets/linkfilter-raw/. Dates d'inscription : RDAP, steam_tos_assets/domain-registration.json. · Vérification préalable de 2026-09-19 dans linkfilter-all-results.json · enregistrement des itinéraires dans auth-route-audit.json · Instantanés Wayback Machine des pages « Link Filter », 2026-09-21, répertoriées dans wayback-snapshots.json (il n'existe aucun instantané pour rbsnin.com ; le fichier brut local est la seule trace disponible).\n\nDates d'inscription : RDAP (steam_tos_assets/domain-registry/). L’« URL OpenID fournie » définit les paramètres de la requête, et non une connexion aboutie. Les auteurs n’ont effectué aucune connexion sur aucune plateforme. Un domaine distinct ne constitue pas en soi une preuve de contournement. De même, le fait qu’« aucun hôte d’authentification n’ait été bloqué » n’est pas une constatation indépendante : en bloquer un interrompt la connexion Steam de cette plateforme ; par conséquent, un registre constitué à partir de connexions fonctionnelles ne peut contenir d’hôte d’authentification bloqué. L’observation qui a du poids est le couplage et sa durée : un domaine principal dans le filtre de liens à côté d’un domaine de connexion qui fonctionne depuis des années. Ce tableau comporte 30 lignes : 25 des 27 routes disposant d’un fichier de preuves par route, plus cinq ajoutées sur 2026-09-22 dont la répartition dans le filtre de liens est capturée dans linkfilter-2026-09-22.json même si le domaine lui-même a été sélectionné manuellement — c’est ce qu’indiquent les lignes correspondantes dans la colonne « source ». Les deux chemins d’accès aux fichiers de preuve qui ne sont pas affichés sont skinsnipe.com (hôte d’authentification pricing.tradeupspy.com, enregistré 2020-03-11) et csgobig.com (hôte d'authentification letmeinbig.com, enregistré 2023-01-20) ; les deux ont renvoyé « BLOCKED main / CLEAN auth host » lors de la vérification de 2026-09-22, enregistré avec SHA-256 dans linkfilter-2026-09-22c.json, mais le code HTML brut correspondant à ce lot ne figure pas dans l'ensemble publié ; c'est pourquoi elles sont simplement mentionnées ici, au lieu de faire l'objet d'une ligne distincte, comme c'est le cas pour toutes les autres lignes de ce tableau. Les 12 itinéraires restants, recueillis manuellement et figurant dans le registre, sont identifiés comme tels dans master_registry.json sous realm_src: user.\n\nAudit empirique primaire · Période pluriannuelle\nLe piège de la vision d'ensemble : le filtre de liens n'est qu'une mise en scène de conformité, pas un véritable bouclier\n\nSur les navigateurs de bureau, les utilisateurs sont protégés par des dispositifs de sécurité externes : Google Safe Browsing et Microsoft SmartScreen bloquent les tentatives de hameçonnage connues en affichant des avertissements rouges en plein écran. Dans le mode « Big Picture » de Steam, dans la superposition en jeu (Maj+Tab) et dans le Deck Steam (SteamOS), ces défenses n'existent pas. Le navigateur intégré ne prend en charge aucune extension, désactive les moteurs externes de « navigation sécurisée » et ne laisse à l'utilisateur qu'une seule barrière de protection : celle de Valve. linkfilter interstitiel.\n\nFaites défiler pour comparer les quatre résultats →\n\n92.5%\n2025-2026 : le phishing de nouvelle génération a été validé sans problème (37/40)\n77.5%\nHameçonnage de l'ère CS2 (2023-2024) a été validé sans problème (31/40)\n70.0%\nHameçonnage de type « legacy » en 2021-2022 a été validé sans problème (28/40)\n7 / 7\nréseaux de jeux d'argent bloqués (témoin positif)\nAudit longitudinal pluriannuel : 120 domaines de phishing « purs » Steam testés en temps réel (24 septembre 2026)\n\nPour vérifier si le filtre de Valve est simplement lent à détecter les nouvelles menaces ou s'il en est fondamentalement incapable, nous avons procédé à un audit 120 domaines de hameçonnage confirmés spécifiques à Steam sur trois cohortes historiques par rapport à steamcommunity.com/linkfilter:\n\nPromotion 1 : 2021-2022 (Offres d'échange classiques et objets à gagner) — 70.0% Sans faute (28/40). Même 4 à 5 ans après avoir été répertoriés par les organismes de surveillance communautaires, 7 hébergeurs de hameçonnage historiques sur 10 restent accessibles sans aucun blocage.\nPromotion 2 : 2023-2024 (CS2 Beta : engouement et faux appels à l'aide) — 77.5% Réussite sans faute (31/40). Campagnes se faisant passer pour des annonces concernant la sortie de Counter-Strike 2 et de faux appels à la communauté (par exemple : cs2-steam.com, appealsteamcommunity.help) passent tout droit.\nCohorte 3 : 2025-2026 (Déploiements en périphérie sans serveur et clones de favicons) — 92.5% Réussite haute (37/40). Kits de phishing modernes déployés sur EdgeOne, Vercel et Cloudflare Pages (par exemple : steamgifter.online, steam-dp4lt5b8fnez.edgeone.dev) passent pratiquement sans encombre.\n\nTélémétrie et couverture de responsabilité civile, pas de protection. Pourquoi le « Link Filter » existe-t-il s’il laisse passer 70% à 92.5% des tentatives de hameçonnage pures de type Steam ? Il sert à la fois de clause de non-responsabilité pour l’entreprise et de capteur de télémétrie des clics sortants. En affichant un message poli « Vous quittez Steam » Une notification comportant un bouton vert cliquable « Continuer » ; Valve fait porter la responsabilité juridique sur la victime en vertu du Steam Contrat d’abonnement (*« l’utilisateur a volontairement quitté le site Steam »*). Valve recueille les données télémétriques relatives au clic, mais n’empêche pas le vol.\n\nLa preuve « Favicon Hash » : aucune intégration de flux de menaces. Des plateformes indépendantes de renseignements sur les menaces (urlscan.io, Shodan, Censys) identifient les kits de phishing actifs Steam grâce à une simple recherche du hachage de la favicon officielle de Steam (page.favicon.hash:9f890a9debcdfccc339149a7943be9aff9e4c9203c2fa37d5671a5b2c88503ad NOT domain:*.steampowered.com). Ce contrôle automatisé de base permet de détecter en quelques secondes les clusters de phishing actifs. Valve ne se synchronise pas avec des flux externes, n’effectue pas de recherche de menaces basée sur les hachages et n’intervient manuellement que lorsqu’il y est contraint par les autorités de régulation (décision de 2016 du WSGC concernant les jeux d’argent) ou pour protéger ses chaînes de domaine déposées.\n\nÉléments probants primaires : Audit longitudinal pluriannuel portant sur 120 domaines : audit-longitudinal-sur-les-attaques-de-hameçonnage-via-Steam.json · 100 échantillons de hameçonnage Steam spécifiques : linkfilter-steam-phishing-100.json · Audit général des aliments pour animaux (n = 250) : linkfilter-coverage-2026-09-22.json.\n\nCSGOEmpire — enregistrement groupé de dix domaines d'authentification numérotés\n\nLe 2020-07-20 dix domaines numérotés, csgoempirelogin1.com par le biais de csgoempirelogin10.com, ont été enregistrés. Les horodatages RDAP de Verisign sont consignés pour les dix : login1 05:49:06Z, login5 05:49:08Z, login2 05:49:11Z, login3 05:49:14Z, login4 05:49:17Z, login6 05:49:20Z, login7 05:49:23Z, login8 05:49:26Z, login9 05:49:28Z — neuf domaines en 22 secondes — et login10 à 05:56:03Z, sept minutes plus tard. L'intervalle correspond à une opération groupée effectuée par un seul registraire.\n\nCe schéma correspond à celui des hôtes de secours préconfigurés ; seuls login4 Cela a été observé lors d'une requête OpenID en temps réel. Les sites csgoempire.com et csgoempirelogin4.com ont tous deux renvoyé la mention « CLEAN » dans le filtre de liens sur 2026-09-21 ; CSGOEmpire ne figurait pas parmi les sites cités dans les articles de presse relatifs aux notifications de juillet 2016.\n\n# DNS — les 10 sont actifs (septembre 2026)\nOK csgoempirelogin1.com 172.67.129.43\nOK csgoempirelogin2.com 172.67.175.168\nOK csgoempirelogin3.com 188.114.96.3\nOK csgoempirelogin4.com 188.114.96.11 ← dans le trafic OpenID\nOK csgoempirelogin5.com 172.67.160.194\nOK csgoempirelogin6–10.com Adresses IP de Cloudflare\nNXDOMAIN : csgoempirelogin11.com\nLes 10 sont enregistrés 2020-07-20 ; les 10 sont horodatés par le RDAP (steam_tos_assets/domain-registry/csgoempireloginN.com.rdap.json)\nConclusion à l'intention des autorités de régulation\nUn domaine principal bloqué associé à un hôte d'authentification non bloqué laisse la route d'accès ouverte — et celle-ci reste ouverte pendant des années.\n\nLe bloc « Link Filter » du domaine principal est une entrée publique et vérifiable. L’hôte d’authentification achemine le trafic « Se connecter avec Steam » et apparaît dans les paramètres de requête OpenID propres à Valve. Lors de vérifications effectuées sur 2026-09-21 et 2026-09-22, sur 26 paires de filtres distincts, le domaine principal a renvoyé un bloc « Link Filter » tandis que le proxy acheminant sa connexion n’en a renvoyé aucun. Le registre ci-dessus mesure l’autre moitié de ce phénomène : ces hôtes ne sont pas des domaines jetables à courte durée de vie. Plusieurs étaient enregistrés depuis plus d’une décennie à la date de la vérification, et chacun de ces jours correspond à un jour où Valve a reçu le nom d’hôte dans ses propres paramètres de requête. Valve n’a publié aucun rapport sur les mesures coercitives par opérateur ; il est donc impossible de déterminer, à partir des données publiques, si d’autres mesures ont été appliquées à ces hôtes.\n\n12 ans et 6 mois\nLe site csgogem.com est bloqué dans le filtre de liens.\nSon serveur de connexion api.csgem.com a été\nest inscrit depuis 2014-03-08 et ne l'est pas.\nRésumé en langage clair — À l'intention des autorités de régulation et des tribunaux (déplier)\nRésumé en langage clair — à l'intention des autorités de régulation\nContexte : Qu'est-ce que Steam et pourquoi est-ce important dans ce contexte ?\n\nSteam est une plateforme logicielle exploitée par la société Valve (Bellevue, Washington, États-Unis). Steam fait office de fournisseur d’identité numérique : les sites de jeux d’argent et de jeux vidéo sur Internet utilisent un système appelé « Se connecter avec Steam » — un bouton qui permet à un site web de vérifier qu’un visiteur dispose d’un véritable compte Steam. Ce processus est similaire à « Se connecter avec Google » ou à la vérification d’une carte d’identité délivrée par les autorités : le site web redirige l’utilisateur vers les serveurs de Steam, Steam confirme son identité, puis Steam le renvoie vers le site web. Valve gère le système d'authentification. Chaque connexion effectuée via « Se connecter avec Steam » passe par les serveurs de Valve.\n\nCe qu’a fait Valve : le bloc de domaines\n\nEn juillet 2016, suite aux pressions médiatiques et juridiques concernant les jeux d’argent « skin gambling », l’avocat de Valve a envoyé des mises en demeure à environ 23 sites de jeux d’argent identifiés (selon des articles de presse du 21 juillet 2016) ; en octobre 2016, Valve a déclaré à la Commission des jeux de l'État de Washington qu'elle avait contacté plus de quarante sites. Certains domaines de jeux d'argent figurent dans le Steam Filtre de liens — une liste qui fait en sorte que tout lien vers ces éléments publié dans Steam (dans le chat, sur une page de profil, dans la boutique) affiche une page d'avertissement : « Lien bloqué ! » Le filtre de liaison est la seule mesure coercitive dont l'effet peut être observé depuis l'extérieur de Valve.\n\nExemple : Un lien vers rollbit.com La valeur Steam affiche la page d'avertissement « Link Filter » (options 2026-09-19 et 2026-09-21 cochées). En théorie, le site de jeux d'argent est bloqué.\nQu'est-ce qu'un domaine proxy ?\n\nA L'hôte d'authentification à domaine distinct est un proxy d'authentification: une deuxième adresse de site web, sur un domaine enregistrable différent, que le même opérateur interpose entre ses utilisateurs et Steam dans le seul but de gérer l'étape « Se connecter avec Steam ». Elle sert de proxy pour la connexion. L’utilisateur croit qu’il se connecte à la plateforme ; la requête qui parvient à Valve porte le nom d’hôte du proxy, et non celui de la plateforme. Il n’a généralement aucun lien visible publiquement avec le site de jeux d’argent, et c’est cette adresse qui redirige les utilisateurs une fois que Steam a confirmé leur identité.\n\nExemple : Rollbit opère sous rollbit.com, que le filtre de liens bloque. Pour l'authentification Steam, le flux observé sur 2026-09-20 utilisait une adresse distincte : rbsnin.com, enregistrée sous le numéro 2026-09-18. Cette adresse a renvoyé Pas de bloc « Link Filter » le 2026-09-21. Le site de jeux d'argent a continué à fonctionner, et son processus de connexion Steam passait par l'hôte débloqué.\nLe point critique : l'hôte d'authentification est envoyé à Steam dans chaque requête\n\nValve n'a pas besoin d'effectuer de scan ou d'exploration pour déterminer quels hôtes d'authentification sont utilisés. Steam est le Fournisseur d'identité OpenID pour ces sites, et chaque clic sur « Se connecter avec Steam » envoie une requête GET aux serveurs de Valve contenant le nom d'hôte d'authentification en clair. Conformément à la section 9.1 de la spécification OpenID 2.0, le return_to Ce champ est techniquement facultatif, mais sans lui, Steam ne peut pas fournir le résultat de la connexion ; il est donc de fait obligatoire pour que la connexion Steam fonctionne. Steam affiche lui-même le nom d'hôte sur la page de connexion («<host> n'est affilié ni à Steam ni à Valve« »).\n\n— Format de la requête Steam reçue (hôte tel qu’observé pour Rollbit sur 2026-09-20) : —\nOBTENIR steamcommunity.com/openid/login\n&openid.mode=checkid_setup\n&openid.return_to=https://rbsnin.com/… ← effectivement requis ; apparaît dans le journal de Valve\n&openid.realm=https://rbsnin.com ← informations fournies par le site lui-même ; affichées sur la page de connexion de Steam\nSi le site utilise une vérification de serveur à serveur (check_authentication), le journal de Valve enregistre également l'adresse IP du serveur de la plateforme et le réseau d'hébergement.\n\nL'extraction du nom d'hôte à partir de cette requête est une opération courante. Le registre des mesures appliquées — indiquant quels hôtes ont fait l'objet d'une intervention, lesquels n'en ont pas fait l'objet, et selon quels critères — n'existe que dans l'infrastructure de Valve et n'a pas été rendu public.\n\nCe que cela prouve\n\n1. Le bloc « Link Filter » agit sur les liens, et non sur les identifiants de connexion. Bloquer le domaine principal (par exemple rollbit.com) affiche un message d'avertissement aux utilisateurs qui cliquent sur des liens y menant à l'intérieur de Steam. Cela n'empêche pas le site de fonctionner, ni d'utiliser le service OpenID de Valve via une autre adresse.\n\n2. Les serveurs d'authentification testés n'étaient pas bloqués. Le tableau ci-dessus présente les hôtes d’authentification à domaine distinct enregistrés entre 2011 et septembre 2026, dont plusieurs l’ont été plusieurs années après les avis de juillet 2016. Dans 26 paires, le domaine principal a renvoyé un blocage par filtre de liens, contrairement au proxy transmettant ses identifiants (vérifications non authentifiées, 2026-09-21 et 2026-09-22 ; réponses brutes et SHA-256 enregistrées). Ce proxy cessait de fonctionner le jour où Valve le refusait ; c’est pourquoi la mesure prise ici porte sur la durée de son fonctionnement, et non sur le fait qu’il figure ou non dans la liste. Valve reçoit ces noms d’hôtes dans ses propres requêtes OpenID. Il est impossible de déterminer à partir des données publiques si une mesure autre que le filtre de liens a été appliquée, car Valve n’a publié aucun relevé d’application par opérateur.\n\n3. Les sites ont continué à s'authentifier via l'infrastructure de Valve. « Se connecter avec Steam » est un service proposé par Valve ; chaque authentification effectuée via ce service correspond à une requête que Valve reçoit et traite. Valve tire également des revenus des clés de cas, et le Marché communautaire Steam prélève des frais combinés d’environ 15% sur les transactions effectuées au sein du Marché (mais pas sur les échanges externes). L’action « Link Filter » a créé un enregistrement public ; elle n’a pas interrompu la relation d’authentification.\n\nLe blocage aurait-il fonctionné ?\n\nÀ titre d'analogie : lorsque le registraire de noms de domaine gratuit Freenom a cessé ses activités en 2023, les campagnes de hameçonnage qui reposaient sur ses noms de domaine ont été interrompues. La continuité opérationnelle dépend de la stabilité de l'infrastructure.\n\nLa même logique s'applique ici. Si un hôte d'authentification était refusé lors du traitement OpenID de Steam, la fonction « Se connecter avec Steam » de la plateforme cesserait de fonctionner jusqu'à ce qu'un nouvel hôte soit enregistré, que les certificats soient émis et que la propagation DNS soit effective. Pendant cette période : interruption de service.\n\nLa rotation ne rend pas le blocage inutile. Cela fait du blocage un coût opérationnel. Étant donné que les nouveaux hôtes apparaissent dans les journaux de requêtes de Valve lors de leur première utilisation, une réponse pourrait s'exécuter à la vitesse de cette première utilisation.\n\nL'enregistrement par lots est en soi un signal : Les requêtes « login1 » à « login10 » de CSGOEmpire ont été enregistrées le 2020-07-20, dont neuf en l'espace de 22 secondes (Verisign RDAP). Une réponse ne doit pas nécessairement concerner chaque domaine individuellement ; une série séquentielle issue d'une même session chez un registraire peut être considérée comme une série.\n\nLes archives publiques ne font état d'aucune tentative de blocage des hôtes d'authentification qui aurait été contrecarrée par la rotation.\nIl indique les principaux domaines bloqués alors que le proxy gérant chaque connexion continuait de fonctionner — 26 paires au 2026-09-22, l’hôte d’authentification le plus ancien ayant été enregistré il y a 12 ans et 6 mois — et aucune trace de mesure coercitive publiée pour aucun opérateur.\nLa question qui se pose donc à l'autorité de régulation est la suivante : quelles mesures coercitives, le cas échéant, Valve a-t-elle appliquées aux serveurs d'authentification qu'elle reçoit dans ses propres requêtes OpenID ?\nCe qu’a fait Valve — et pourquoi cela n’a pas interrompu le chemin d’authentification\n\nLe tableau ci-dessous recense chaque action Valve rendue publique et indique si elle a eu une incidence sur le point d’entrée d’authentification OpenID. La conclusion n'est pas que « Valve n'a rien fait », mais qu'aucune des actions rendues publiques n'a touché le point par lequel les connexions aux plateformes de jeux d'argent transitent par les serveurs de Valve.\n\nDate\tValve Action\tConcerné openid.return_to chemin ?\nJuillet 2016\tCommuniqué de presse du 13 juillet 2016 ; notifications de l'avocat adressées à environ 23 sites cités (presse, 21 juillet 2016) ; plus de 40 sites contactés suite à la lettre adressée par Valve au WSGC en octobre 2016\tNon. Les notifications et le filtre de liens agissent sur les opérateurs et les liens ; le chemin de requête OpenID n'a pas été modifié.\n2017\tFermeture de IEconItems_730/GetPlayerItems (d'après le compte d'ingénierie de CSFloat ; aucun journal des modifications Valve n'a été trouvé)\tNon. Cela a eu un impact sur la visibilité de l'historique des éléments publics. L'authentification OpenID n'a pas été modifiée.\n2018-03-29\tAnnonce d'un délai de blocage de 7 jours pour les échanges dans CS:GO (blog.counter-strike.net)\tNon. Ralentissement du transfert des éléments ; le chemin de requête OpenID n'a pas été modifié.\n2022-05-10\tSuppression des points de fin d'annulation de transaction de l'API Web publique (détectée par un utilisateur ; pas de mention dans le journal des modifications Valve — node-steam-tradeoffer-manager #325)\tNon. L'outil d'échange d'offres a été désactivé ; l'authentification OpenID n'a pas été modifiée.\n2023-12-04\tLa création d'une clé API nécessite désormais une confirmation via mobile (steamcommunity.com/dev/apikey ; pas de journal des modifications)\tNon. Le point de terminaison clé a été protégé ; les hôtes d'authentification mentionnés ici n'ont pas été affectés.\n2026-09-19 / 21 septembre\tSteam État du filtre de liens tel qu'observé par les auteurs\tLes 14 domaines principaux ont renvoyé un bloc lors de la nouvelle vérification enregistrée 2026-09-21 — 26 paires fractionnées dans le registre par 2026-09-22 — tandis que le proxy gérant chaque connexion continuait de fonctionner.\nSources : Valve communiqué du 13 juillet 2016 (store.steampowered.com/oldnews/22883, archivé 2026-09-21) · Compte rendu technique de CSFloat sur la fermeture de 2017 (blog.csfloat.com, archivé 2026-09-21) · État du filtre de liens : linkfilter-recheck-2026-09-21.json.\nCette conclusion peut être réfutée par un seul cas publié dans lequel Valve aurait refusé une demande OpenID parce que openid.return_to indiquait un serveur d'autorisation de jeux d'argent. Aucune instance de ce type n'a été identifiée dans les registres publics.\nLes deux derniers enregistrements d'hôtes d'authentification\nhowl.unoa été enregistré 2026-08-11 (RDAP), 41 jours avant 2026-09-21 ; howl.gg a renvoyé un blocage par le filtre de liens sur 2026-09-18, 2026-09-19 et 2026-09-21. Il n’est pas établi si le blocage a précédé l’enregistrement.\nrbsnin.coma été enregistré sous le code 2026-09-18T09:34:52Z (Verisign RDAP) et a été détecté dans le processus de connexion de Rollbit (Steam) le 2026-09-20 via l'avis affiché sur la page de connexion de Steam ; rollbit.com a renvoyé un blocage du filtre de liens les 2026-09-19 et 2026-09-21, contrairement à rbsnin.com.\nChaque hôte figurant dans le tableau ci-dessus est envoyé aux serveurs d'authentification de Valve sous la forme openid.realm à chaque tentative de connexion.\nDonnées complètes par itinéraire et résultats du filtre de liens : voir le tableau de la section 3 ci-dessus ; résultats bruts dans linkfilter-recheck-2026-09-21.json et linkfilter-all-results.json.\nMéthodologie — Comment ont été établis les chiffres relatifs aux itinéraires et aux filtres de liaisons ?\n1. Résolution de nom de domaine\nL'audit « 2026-09-21 » a permis de résoudre 78 des 189 plateformes concernées : 33 s'authentifient sur leur propre nom d'hôte et 20 sur leur propre sous-domaine — authentification directe — et aucune d'entre elles n'est comptabilisée comme une route de domaine distinct. Les autres 25 : authentification via un domaine distinct pouvant faire l'objet d'un enregistrement, répartis sur 24 noms d’hôte distincts (dota2.net est partagé par market.csgo.com et rust.tm) : 10 identifiés grâce à une capture en direct du navigateur, 3 grâce à la notification affichée sur la page de connexion de Steam, et 12 grâce à une URL OpenID fournie. Le registre en temps réel (master_registry.json, 2026-09-22) étend cela à 44 routes de domaines distincts: 26 paires de filtres séparés (domaine principal BLOCKED, hôte d'authentification CLEAN) plus 18 autres routes sans séparation du domaine principal. Sur ces 44, 27 tenir un dossier de preuves par itinéraire; les 17 autres ont été ramassés à la main et sont marqués realm_src: user dans le registre. Cinq de ces dix-sept sites — csgogem.com, gamdom.com, 12cs.fail, csgolounge.com et dota2lounge.com — ont été ajoutés le 2026-09-22 avec une capture Link Filter des deux hôtes (HTML brut + SHA-256 dans linkfilter-2026-09-22.json), de sorte que la division elle-même est mise en évidence même si le domaine est collecté manuellement ; elles apparaissent dans le tableau ci-dessus aux côtés des itinéraires du dossier de preuves. tfauth.com (tf2easy.com) a été supprimé du registre à 2026-09-22 : tout comme arena.fragnet.net, aucun lien vérifiable ne le relie à son site d'origine. Le nombre peut être recalculé à partir des données publiées auth-route-audit.json (série de 2026-09-21) selon une seule règle : une plateforme n'est prise en compte que si son hôte OpenID Steam observé se trouve sur un domaine enregistrable différent de celui de la plateforme elle-même.\n2. Steam État du filtre de liens\nTesté via steamcommunity.com/linkfilter/?url=https://[domain], non authentifié, sur 2026-09-19 et 2026-09-21 ; code HTML brut enregistré avec SHA-256. Statut enregistré séparément pour le domaine principal et l'hôte d'authentification. Un classificateur distingue le message générique « Vous quittez Steam » (CLEAN) de la page « Lien bloqué ! ... signalé comme potentiellement malveillant » (BLOCKED) ; un test de contrôle sur google.com confirme que les deux ne sont pas confondus. Une variante antérieure authentifiée de ce test a été écartée après avoir renvoyé « bloqué » pour chaque domaine, y compris ce contrôle — ce qui s’est avéré être dû à un cookie de session invalide dans le script de test, et non à un résultat réel.\n3. Observation de l'hôte d'authentification\nCapture en direct : un navigateur Playwright a accédé à la procédure de connexion de chaque plateforme et le openid.return_to Le nom d'hôte a été extrait de la requête interceptée. Avis concernant la page de connexion : le nom d'hôte a été extrait du propre « » de Steam<host> n'est affilié ni à Steam ni à Valve\" texte, que Steam affiche à partir de openid.realm (rbsnin.com, sc-auth.net, auth.dota.trade). URL fournie : une URL de connexion de type « a Steam » transmise aux auteurs ; celle-ci définit les paramètres de la requête, mais ne correspond pas à une connexion effective. Aucune connexion n'a été effectuée sur aucune plateforme.\n4. Portée — ce qui n’a pas été résolu, et pourquoi cela est important\nSur les 189 plateformes, La ligne 110 n'a pas de parcours défini et l'un d'entre eux n'était pas applicable (189 − 78 − 1). Ce dossier n'en tient compte d'aucun. La répartition des 110 cas, d’après le fichier d’audit : 22 défis anti-bot, 14 délais d’expiration, 12 erreurs HTTP et 10 erreurs de navigation — l’observateur n’a pas pu accéder au flux de connexion, bien que la plupart de ces sites s’ouvrent normalement dans un navigateur classique ; 20 ne présentaient aucun contrôle de connexion Steam sur la page d’accueil ; 16 ont abouti à un processus de connexion qui n’a pas pu être résolu vers un hôte ; 11 domaines n’ont pas été résolus via le DNS ; 5 se sont heurtés à une page de consentement. Le tableau ci-dessous présente ces mêmes 110 sites sous un angle différent : les 11 qui n’ont pas pu être résolus via le DNS sont répertoriés séparément comme Supprimé · NXDOMAIN, et l'entrée non conforme rejoint les autres. 189 plateformes auditées, 11 supprimées suite à un NXDOMAIN définitif de la part des deux résolveurs, 178 conservés (platform-audit.json, platforms-removed.json). 137 domaines d'authentification que le registre avait devinés en se basant sur un modèle de nommage ont été supprimés des données de 2026-09-19 — jamais observés, donc jamais considérés comme des preuves. Trois de ces hypothèses ont été contredites par les URL OpenID fournies : buff.163.com, gamerpay.gg et csgoluck.com effectuent l'authentification directement, contrairement aux hypothèses concernant buffauthproxy.163.com, gamerpayredirect.io et lucklogin.app. Les suppressions sont répertoriées dans le fichier d'audit publié.\nLe chiffre 25 correspond à un seuil minimal, et non à un plafond. Parmi les 78 plateformes pour lesquelles la connexion a abouti, 25 utilisaient un domaine distinct et 53 n’en utilisaient pas. Ce ratio ne permet de tirer aucune conclusion concernant les 110 cas non résolus, et aucune projection à partir de celui-ci n’apparaît nulle part dans ce dossier. Chacune d’entre elles peut être résolue par une personne qui ouvre le site et clique sur « Se connecter avec Steam » : le nom d’hôte d’authentification se trouve dans l’URL de la page Steam qui se charge.\nL'objectif de cette section : Un observateur indépendant a besoin d’un navigateur et de beaucoup de patience pour identifier 189 plateformes, et en a identifié 78. Valve nécessite une requête dans la base de données. Chaque plateforme qui utilise « Se connecter avec Steam » — qu’elle soit identifiée ou non — envoie openid.realm vers le point de terminaison d'authentification de Valve à chaque connexion. L'absence de données dans ce tableau s'explique par le fait que les auteurs ne font pas partie du système. Elle n'existe pas pour Valve.\nLes noms d'hôtes proxy observés se trouvent dans auth-route-audit.json. Dates d'enregistrement du nom de domaine provenant de RDAP (Verisign) / IP2WHOIS. Résultats du filtre de liens dans linkfilter-all-results.json.\nUne analogie pour plus de clarté\n\nImaginons qu’une société de taxis agréée se voie notifier par les autorités de régulation qu’elle ne peut plus exercer son activité à partir de son adresse enregistrée sur Main Street. La société retire son enseigne de Main Street. Ce retrait est consigné. Cependant, cette même société ouvre une adresse sur Side Street — enregistrée sous un autre nom — et poursuit son activité à partir de là. Les autorités de régulation gèrent le système central de répartition utilisé par tous les taxis, quelle que soit leur adresse d'enregistrement. Chaque demande de course indique « prise en charge depuis Side Street ». Les autorités de régulation ne révoquent jamais la licence de Side Street. Le retrait du panneau « Main Street » est la seule mesure coercitive qui ait été prise. La compagnie de taxis n'a jamais cessé ses activités.\n\nPartie A — Dossier technique · Section 3.1\nDans Steam, la liste de Valve est la seule liste.\n\nUn lien sur lequel l'utilisateur clique dans le client Steam, dans la superposition en jeu ou en mode Big Picture ne s'ouvre pas dans son navigateur. Il s'affiche dans le navigateur intégré à Steam, où les couches d'avertissement qu'un navigateur appliquerait ne sont pas présentes. Le filtre de liens n'est pas l'une des mesures de sécurité parmi d'autres. C'est la seule et unique mesure de sécurité.\n\nDans un navigateur classiqueTrois couches indépendantes\nNavigation sécurisée de GoogleUne page interstitielle pleine page pour les serveurs figurant sur les listes de Google relatives au phishing et aux logiciels malveillants, mise à jour en continu et indépendamment du site visité.\nL'extension antivirus pour navigateurLa plupart des produits destinés aux particuliers sont fournis avec une extension de navigateur qui vérifie la destination par rapport à la liste de réputation propre au fournisseur.\nInspection HTTPS au niveau des terminauxLorsque le produit effectue une inspection TLS, le contenu de la page est analysé avant d'être transmis à l'utilisateur.\nDans le client Steam, les modes « Overlay » et « Big Picture »Une couche\nNavigation sécurisée de GoogleAbsent. La vérification nécessite des clés API Google qui ne sont pas fournies dans les versions intégrées de Chromium ; en leur absence, la documentation technique de Chromium indique que le gestionnaire « Safe Browsing » n'est tout simplement jamais ajouté à la chaîne de requêtes.\nL'extension antivirus pour navigateurAbsent. Le moteur de rendu de Steam n'est pas le navigateur de l'utilisateur et ne charge aucune extension à partir du profil de navigation de ce dernier ; par conséquent, aucun module complémentaire ne s'exécute sur cette page.\nInspection HTTPS au niveau des terminauxCela dépend du produit. Le trafic aboutit au sein d’un processus signé (Valve) plutôt que dans un navigateur reconnu, et certains produits côté terminal exemptent les applications signées de l’inspection TLS.\nLe filtre de liens SteamLa liste noire propre à Valve, consultée lorsqu'un lien quitte l'écosystème Steam. Il s'agit de la seule vérification effectuée — et le tableau ci-dessus indique les résultats obtenus pour les hôtes d'authentification mentionnés dans cette section.\nUn test que tout lecteur peut effectuer, et dont les résultats sont invalides en cas d'échec\n\nOuvrez l'une des URL de test de la fonctionnalité « Navigation sécurisée » publiées par Google (testsafebrowsing.appspot.com) dans Chrome : une page interstitielle rouge en plein écran s'affiche. Ouvrez la même URL à partir d'un message de chat Steam, de manière à ce qu'elle s'affiche dans le client Steam ou dans la superposition : aucune page interstitielle n'apparaît. Le seul avertissement que Steam peut générer est sa propre page « Link Filter », et uniquement pour les hôtes figurant sur la liste de Valve.\n\nLe palmarès de Valve en matière de programme de récompenses pour la découverte de faillesCe morceau a déjà été repris auparavant — sur l'album de Valve lui-même\n\nSi le filtre de liens est le seul contrôle effectué au sein du client, ses propres modes de défaillance ne sont pas une question secondaire. Deux rapports soumis dans le cadre du programme HackerOne de Valve, tous deux acceptés, tous deux résolus, et tous deux rendus publics dans leur intégralité depuis :\n\n#291750archivé 2025-11-16 ↗Open Redirect · medium\nContournement de la protection par filtre de liaison\n\nSignalé le 19 novembre 2017, résolu, rendu public le 9 mai 2018. Preuve de concept fournie par le rapport lui-même : remplacement du point idéographique 。 (%E3%80%82) pour le point dans un nom d'hôte — Il est possible de contourner ce blocage. L'élément interstitiel dont traite cette section n'est pas apparu.\n\n#1079561archivé 2026-09-24 ↗Divulgation d'informations · élevé\nLe navigateur Web Big Picture divulgue des cookies de connexion et expose des informations sensibles (ce qui peut entraîner le piratage de comptes)\n\nSignalé le 15 janvier 2021, résolu, rendu public le 21 septembre 2021. Le niveau de gravité attribué par Valve est élevé, et le titre indique la conséquence. La fiche publiée comporte le titre, le niveau de gravité et les dates ; la description technique ne figure pas dans le contenu publié, c'est pourquoi aucun autre extrait n'en est cité ici.\n\nIl s'agit là de l'interprétation des auteurs, et non d'une conclusion tirée de l'un ou l'autre de ces rapports : Les deux se situent de part et d’autre d’une même barrière. L’une correspond à l’avertissement qui ne s’affiche pas avant l’ouverture de la page de destination ; l’autre correspond à la session qui quitte le client dès qu’une page est ouverte dans celle-ci. La séquence qui suit le vol d’une session — clé enregistrée sans demande de confirmation, transaction réelle annulée, doublon envoyé à un clone — correspond au schéma décrit dans Section 5 à Section 8. Ces deux rapports sont classés ; aucune de ces vulnérabilités n'est considérée comme active. Ce qu'ils démontrent est plus restreint, mais suffisant : la seule couche restante a déjà fait l'objet de contournements avérés, comme l'indique le propre historique de Valve.\n\nSource : fiche de divulgation HackerOne pour chaque rapport, extraite le 2026-09-22 — numéro, titre, équipe, vulnérabilité, gravité, dates de signalement et de divulgation, ainsi que le statut, tels que publiés par HackerOne. Fiche d’extraction : hackerone-reports.json. Aucun montant de prime n'est mentionné ici ; aucun ne figure dans le dossier consulté.\n\nObservation sur le terrain · PhishDestroyLes détections qui mettent habituellement fin à une campagne n'ont pas mis fin à celles-ci\n\nNous avons observé que les serveurs de hameçonnage continuaient à générer du trafic tout en hébergeant 20 détections de fournisseurs ou plus. Diffusée via le Web ou par e-mail, une campagne dans cet état est neutralisée en quelques jours : le navigateur et l’antivirus réagissent tous deux à ces verdicts. Dans Steam, ce n’est pas le cas. Les verdicts existaient depuis le début. Rien dans le client n’a jamais demandé quoi que ce soit.\n\nQuelles sont les conséquences pour un mineur qui a installé un antivirus ?\n\nIl ne néglige aucun avertissement et ne désactive rien. Un message arrive dans Steam — un couteau gratuit, un vote pour l'équipe d'un ami — et la page s'ouvre dans Steam. Il n'ouvre jamais de navigateur, donc le navigateur ne le protège jamais. Son antivirus est en marche et considère peut-être déjà ce domaine comme malveillant ; on ne lui demande jamais son avis. Toutes les mises en garde qui auraient pu l'en empêcher existent déjà. Aucune d'entre elles ne lui parvient. Il pense n'avoir jamais quitté Steam, et c'est effectivement le cas.\n\nCette offre n'est pas une invention du hameçonneur : les sites de skins et de jeux d'argent font leur publicité en proposant des articles gratuits Valve, ce qui explique précisément pourquoi le message semble tout à fait normal. Plaintes : les archives des mesures d'exécution. Données relatives à l'âge et aux enfants : Article 17.\n\nSources : Steam affiche le contenu Web via le Chromium Embedded Framework dans le steamwebhelper processus — voir Analyse technique de DARKNAVY du 27 juin 2024 ↗ et celui de Valve lui-même Steam Forum bêta des clients ↗ archivé 2025-08-04 ↗. Aucune version CEF n'est utilisée : Chromium intégré n'est pas Chrome et ne comprend aucun des services Google de Chrome. Navigation sécurisée sans clés API : Document de conception de Chromium ↗ archivé 2026-08-21 ↗, Clés API Chromium ↗ archivé 2026-08-30 ↗ (« Bon nombre des API Google utilisées par Chrome sont spécifiques à Google et ne sont pas destinées à être utilisées dans des produits dérivés »), et le même effet dans d'autres versions sans clé — Fût de bière artisanale n° 193814 ↗. URL de test : testsafebrowsing.appspot.com ↗.\n\nDeux horloges différentes\nL'ancienneté du domaine.Date de l'observation.\n\nLa date de création du registre indique à quel moment un domaine a été enregistré. Un enregistrement OpenID daté précise l'hôte de retour associé à cet enregistrement. La première ne peut pas couvrir les années antérieures à la seconde.\n\nLe registre complet distingue un domaine enregistrable distinct, le sous-domaine propre à un site et un chemin d'accès direct. Chaque ligne renvoie vers sa source et le résultat de l'DNS.\n\nConsulter le registre des noms de domaine →· Télécharger les dates d'enregistrement ↗· Reproduire l'observation ↗\n\nPartie A — Dossier technique · Section 4\nUn point de terminaison a été fermé. Le traçage public a perdu une clé.\nContexte et limites de la source\n\nSteam a mis en place des modifications qui ont supprimé la visibilité publique des identifiants d’actifs (Asset ID) et restreint l’accès à l’inventaire via l’API. Conséquence : il est devenu impossible de retracer un article spécifique à partir de son identifiant d’actif d’origine à partir des données publiques. Ce qui suit présente ce qui était possible auparavant, ce qui ne l’est plus depuis lors, et ce que cela coûte à une victime qui tente de prouver où sont passés ses biens. La date est 2017 selon le compte d’ingénierie de CSFloat ; aucun journal des modifications de Valve n’a été retrouvé. Cette chronologie — qui intervient environ un an après la déclaration de juillet 2016 concernant les jeux d’argent — constitue l’objet de l’enquête, et non une conclusion. Les enregistrements des objets eux-mêmes restent dans les systèmes de Valve ; les enquêteurs externes ont perdu l’accès à la chaîne d’identifiants d’origine, tandis que les identifiants « float », « seed » et « paint » ne permettent qu’une correspondance partielle.\n\nLa règle Valve s'applique : Steam Le service d'assistance ne rétablit pas les éléments qui ont quitté votre compte, et c'est à vous qu'il incombe de prouver ce qui s'est passé. Le bilan : En 2017, Valve a fermé le point de terminaison qui transmettait les identifiants d'origine des objets. Avant cela, n'importe qui pouvait suivre le parcours d'un skin volé depuis le compte de la victime jusqu'à un bot sur une place de marché. Depuis, personne en dehors de Valve ne peut plus le faire. Le justificatif demandé à la victime est celui qui a été retiré. — et elle existe toujours, à l’intérieur de Valve.\n\nL'époque d'avant la panne d'électricité\n\nHistoriquement, chaque objet virtuel généré sur Steam possédait un identifiant unique au niveau mondial et immuable Identifiant de l'élément. Des bases de données OSINT tierces pourraient indexer ces identifiants. Si un utilisateur se faisait détourner un bien, les enquêteurs pourraient retracer le parcours de cet actif spécifique, depuis le compte intermédiaire du pirate jusqu’aux comptes de stockage d’une place de marché ou d’un site de jeux d’argent.\n\nAVANT : n'importe qui pouvait, à l'aide de données publiques, retracer le parcours d'un objet depuis le compte de la victime, en passant par des comptes intermédiaires, jusqu'à un bot de stockage sur une place de marché ou un casino.\nAprès le changement\n\nSelon le compte d'ingénierie de CSFloat, Valve a fermé le point de terminaison en 2017 et les identifiants d'éléments d'origine ont cessé d'être accessibles aux tiers. Aucune déclaration Valve expliquant la raison de ce changement n’a été trouvée. Au cours de la même période, aucune mesure publiée à l’encontre des comptes de bots commerciaux qui transféraient des objets à grande échelle n’a non plus été identifiée.\n\nQuelle qu'en soit la raison, ce changement a rompu la chaîne de traçabilité publique. Une victime ne peut plus reconstituer la chaîne d'identification d'origine à partir des données publiques pour démontrer qu'un objet volé spécifique a été écoulé via une plateforme de vente ou un casino en particulier. Les enregistrements relatifs à ces objets existent toujours dans les systèmes de Valve ; le grand public, les chercheurs et les forces de l'ordre qui travaillent à partir des données publiques n'y ont toutefois pas accès.\n\nDÉSORMAIS : il n'est plus possible de retracer un objet spécifique à partir de son identifiant d'actif (Asset ID) d'origine à partir des données publiques. La chaîne de traçabilité de l'identifiant d'origine d'un objet déplacé après 2017 n'existe qu'au sein de l'infrastructure de Valve ; aucun enregistrement de ce type n'a été rendu public. Les identifiants « float », « seed » et « paint » ne permettent qu'une correspondance partielle et probabiliste.\nIEconItems_730\nOBTENIR/IEconItems_730/GetPlayerItems/v1/\nCharge utile traçable (avant le correctif)\n\"id\": \"14892281934\",\n\"original_id\": \"11829910211\",\nStatut : la victime peut retracer le parcours d'un objet à travers les différents comptes de bots.\nCharge utile obscurcie (après application du correctif)\nActuel\n\"id\": \"HIDDEN_BY_PRIVACY_SETTINGS\",\n\"original_id\": \"NULL\",\nStatut : les tiers ne peuvent plus retracer l'historique d'un élément à partir de son identifiant d'actif d'origine à partir des données publiques.\nIncidence sur les éléments de preuve : Après cette modification, les données publiques nécessaires pour suivre un élément spécifique à partir de son identifiant d'actif (Asset ID) d'origine, depuis le compte d'une victime jusqu'à une plateforme de marché ou un bot de casino, n'étaient plus disponibles. Les enregistrements internes existent toujours à l'adresse Valve ; une victime, un chercheur ou un enquêteur travaillant à partir de données publiques ne peut pas reconstituer la chaîne d'identifiants d'origine (les identifiants « float », « seed » et « paint » ne permettent qu'une correspondance partielle).\n\nSource : Compte rendu technique de CSFloat concernant la fermeture en 2017 de IEconItems_730/GetPlayerItems — blog.csfloat.com/how-floatdb-tracks-items (archivé 2026-09-21) · Les données présentées servent à illustrer la forme du champ et ne constituent pas des réponses enregistrées · Aucun journal des modifications Valve n'a été trouvé pour cette fermeture.\n\nPartie A — Dossier technique · Section 5\nUne seule session. Un accès plus étendu que ce que l'utilisateur perçoit.\nContexte et limites de la source\n\nL'architecture des clés API de Valve, telle qu'elle existait avant les modifications de 2023, s'écartait des normes de référence du secteur (OWASP ASVS, NIST SP 800-63B) et correspond au mécanisme décrit dans les plaintes automatisées pour vol de stock conservées dans les archives de preuves (sections 6 à 8).\n\nLa règle Valve s'applique : « Le titulaire du compte a créé la clé, a accepté les conditions générales et assume la perte » : telle est la réponse figurant dans les refus archivés. Le bilan : Jusqu’en décembre 2023, un simple cookie de session volé suffisait à enregistrer cette clé. Sans mot de passe. Sans Steam Guard. Sans notification à la personne à qui appartenait le compte. L'utilisateur n'a pas créé la clé, ne pouvait pas la voir, mais on lui a dit que c'était le cas. La confirmation mobile a été ajoutée le 2023-12-04 — environ sept ans après la déclaration de 2016 et environ six ans après les forums consacrés aux arnaques conservés dans les archives. Ces années n’ont pas été financées par Valve. Elles ont été financées par les comptes vidés entre-temps, dont une partie appartenait à des enfants.\n\nOWASP ASVS 2.8 / NIST SP 800-63BNIVEAU DE GRAVITÉ : CRITIQUE\n1. Authentification renforcée insuffisante\n\nSteam permettait la génération de clés API dotées de privilèges élevés et d’une longue durée de vie en utilisant uniquement un cookie de session. Aucune authentification à deux facteurs (Steam Guard) ni aucun défi d’authentification renforcée n’étaient requis lors de la configuration ou de la modification d’une clé API de développeur ; par conséquent, la confirmation mobile Steam Guard — le seul deuxième facteur proposé par Steam — ne protégeait pas cette étape. (Un deuxième facteur matériel avait été demandé dans le système de suivi de Valve en 2016 et le ticket est toujours ouvert : Annexe D, GH-01.)\n\nStatut : non corrigé avant 2023. Permettait à un script contenant un cookie volé d'enregistrer une clé sans aucune intervention de l'utilisateur.\nOWASP A01:2021 / Principe du privilège minimalNIVEAU DE GRAVITÉ : CRITIQUE\n2. Absence du principe du droit d'accès minimal\n\nL'API Web Steam ne disposait d'aucun périmètre d'autorisation basé sur les rôles. Une clé API de développeur délivrée pour consulter l'état des stocks en « lecture seule » disposait de tous les droits d'« écriture », notamment la possibilité de modifier des transactions existantes, d'en initier de nouvelles, d'enregistrer des webhooks et de refuser des échanges en attente valides.\n\nStatut : faille de conception systémique. Une seule clé suffit pour obtenir un contrôle total (lecture/écriture) sur l'inventaire et les transactions du compte.\nOWASP A07:2021 / SessionsNIVEAU DE GRAVITÉ : ÉLEVÉ\n3. Problèmes de gestion des sessions\n\nDes utilisateurs ont signalé que des sessions Web détournées provenant de plages d'adresses IP d'hébergement de serveurs persistaient. La pratique courante consiste à mettre fin aux sessions en cas d'anomalies géographiques ou de changement de mot de passe ; les rapports d'utilisateurs recueillis dans les archives font état de sessions restées actives après un changement de mot de passe.\n\nStatut : comportement signalé (plaintes d'utilisateurs dans les archives). Certaines sessions pouvaient générer des clés API sans nouvelle authentification.\nLe blocage au niveau du domaine était techniquement possibleFAISABILITÉ DE LA MISE EN ŒUVRE\n4. Le blocage au niveau du domaine des hôtes d'authentification était techniquement réalisable\n\nValve gère déjà une liste de domaines (le « Link Filter ») et reçoit déjà tous les noms d’hôte d’authentification dans ses propres requêtes OpenID. Ces deux mécanismes ne sont en aucun cas reliés de manière visible de l'extérieur : à la date de 2026-09-22, dans 26 cas, le domaine principal figurait dans le filtre alors que le proxy assurant sa connexion n'y figurait pas.\n\nLes relier est une petite opération technique : lisez le openid.realm extraire le nom d’hôte de chaque requête entrante, le comparer à une liste, puis refuser ou signaler la requête. L’illustration de droite montre la structure d’une telle routine. Le fait de refuser l’hôte d’authentification — plutôt que la simple page d’accueil publique — interromprait l’étape « Se connecter avec Steam » dont dépendent ces plateformes.\n\nAucun élément public ne permet d'affirmer que Valve procède à une telle vérification. Les frais combinés du « Community Market » Steam, d'un montant d'environ 15%, s'appliquent aux ventes réalisées au sein de cette place de marché ; ils ne sont pas prélevés sur les transactions effectuées en dehors de ces plateformes.\n\nblock_auth_hosts.pyILLUSTRATION\n// Lire l'hôte Steam qui reçoit déjà — pas de balayage\ndef on_openid_request(request) :\nhost = parse_openid_realm(request)\nsi hôte dans domaines bloqués :\nrefuser (une demande)\nRemarque : Pseudo-code fourni à titre indicatif uniquement. Les deux parties existent déjà à Valve : le nom d’hôte de l’auteur figure dans la requête, et la liste de domaines correspond au filtre de liens. Aucune documentation publique n’explique pourquoi elles ne sont pas reliées.\nSection 5.1 — Les normes n'étaient pas non publiées\nValve est compilé quotidiennement selon ces règles. Ce n'est pas le cas ici.\n\nSteam est disponible sur l’App Store et Google Play, effectue ses ventes via les principaux prestataires de paiement par carte et utilise des API tierces comme n’importe quelle autre grande plateforme. Chacune de ces relations s’accompagne d’une exigence de sécurité publiée et datée à laquelle Valve doit se conformer pour pouvoir continuer à fonctionner. Comparez les dates de ces exigences avec celles auxquelles l’API Web de Steam a bénéficié des mêmes mesures de protection. Aucun des éléments ci-dessous ne relève d'une norme privée, d'une note interne ou d'un secret d'affaires : chaque ligne correspond à un document public assorti d'une date de publication.\n\nExigences de sécurité externes publiées, avec leurs dates, mises en regard de la date à laquelle l'API Web Steam a mis en place le contrôle équivalent\nLa norme publiée et sa date d'entrée en vigueur\tL'API Web Steam sur la même question\nAutorisation limitée à un domaineOAuth 2.0 — RFC 6749, Octobre 2012. La section 3.3 définit scope Ainsi, un client ne reçoit que les droits d'accès qu'il demande. C'est depuis lors le comportement par défaut de toutes les API des principales plateformes.\tLes portées granulaires ont fait leur apparition le 16 janvier 2026.Auparavant, une seule clé API Web Steam donnait des droits complets de lecture et d'écriture sur toutes les transactions du compte, quelle que soit la raison pour laquelle elle avait été émise. Treize ans et trois mois après la spécification qui définit le contrôle.\nUne clé n'est pas une autorisationDocumentation officielle de Google Cloud : Une clé API standard ne permet pas d'authentifier un utilisateur., et pour les API qui créent ou gèrent des ressources, N'utilisez pas de clés d'autorisation en environnement de production.\tLa clé API Web Steam correspondait exactement à cela.Une chaîne de caractères au porteur, attribuée à un compte, suffisante à elle seule pour consulter l'inventaire, annuler une transaction en attente et en envoyer une nouvelle. Aucun mandant n'a été authentifié au moment de l'utilisation.\nAuthentification multifactorielle pour les accès privilégiésPCI DSS 3.2, exigence 8.3 — obligatoire à compter du 1er février 2018 pour tous les accès administratifs hors console et tous les accès à distance à l’environnement contenant les données des titulaires de carte. Apple a ensuite imposé l’authentification à deux facteurs pour tous les titulaires de compte du Programme pour développeurs à partir de 27 février 2019: Les développeurs disposant du rôle « Titulaire du compte » dans un programme pour développeurs devront activer l'authentification à deux facteurs pour se connecter.\tUn deuxième élément était nécessaire pour créer une clé API à partir de 4 décembre 2023.Jusqu'alors, un cookie de session volé suffisait, sans aucune invite sur le téléphone du titulaire du compte ni aucune notification par la suite. Quatre ans et neuf mois après qu'Apple a imposé l'utilisation d'une authentification à deux facteurs simplement pour se connecter à un portail destiné aux développeurs.\nCycle de vie et révocation des identifiantsTwitch impose les conditions suivantes à toute application tierce : Votre application doit valider le jeton OAuth au démarrage, puis toutes les heures par la suite., et précise qu’elle procède à des audits pour les applications qui ne s’y conforment pas. Son ancienne API v5 a été définitivement supprimée le 28 février 2022 selon un calendrier publié.\tAucun enregistrement relatif au cycle de vie des clés n'a été publié.La modification de 2023 a protégé le point de terminaison de création. Aucune instruction « Valve » associée à cette modification ne concerne les clés déjà enregistrées, et aucune note de mise à jour n’accompagnait cette modification. Les données publiques ne permettent pas de déterminer si les clés créées avant cette modification ont été invalidées — or, c’est précisément la question à laquelle une personne concernée aurait besoin d’une réponse pour savoir si une clé créée sur son compte il y a plusieurs années est toujours valide.\nRéférence architecturale // Token Architecture\nPortées granulaires de GitHub vs Valve Steam API Web\n\nValve développeurs gèrent quotidiennement des logiciels open source sur GitHub à l'aide de jetons granulaires basés sur le principe du « privilège minimal ». Comparez cela à la clé monolithique délivrée à 130 millions de Steam joueurs.\n\nJeton à granularité fine GitHub\nUtilisé par Valve sur GitHub\n\nJeton à granularité fine avec isolation par périmètre et application obligatoire du cycle de vie.\n\nAccès au référentiel :Uniquement les dépôts sélectionnés (1 dépôt)\nAutorisations d'émission :Lecture seule [✓]\nCode et secrets :Accès refusé [✕]\nDate d'expiration :30 jours (durée de validité obligatoire)\nJournalisation des audits :Adresse IP, agent utilisateur et horodatage\nSituation en matière de sécurité : Le principe du « privilège minimal » limite les dommages à une seule ressource en lecture seule.\n!Valve Steam Clé API Web\nDistribué à 130 millions d'utilisateurs\n\nChaîne principale unique de 32 caractères conférant des autorisations de transaction et de gestion des stocks de type « tout ou rien ».\n\nAccès au compte :COMPTE COMPLET (monolithique)\nGestion des transactions :Lire, Annuler, Refuser [!]\nPortées granulaires :AUCUN (Arrivé en 2026, avec 13 ans de retard)\nDate d'expiration :JAMAIS (Valable indéfiniment)\nJournalisation des audits :AUCUN (Historique IP nul pour l'utilisateur)\nVulnérabilité : Une clé volée permet d'intercepter discrètement toutes les offres commerciales sortantes.\nLa norme appliquée dans un sens\n\nSupposons qu’un fournisseur Valve — un prestataire de services cloud, un prestataire de paiement, un CDN — ait laissé un point de terminaison d’authentification sans authentification à deux facteurs, et que, quelques mois plus tard, les données d’entreprise de Valve aient été divulguées via une clé générée à partir de ce point de terminaison. Valve accepterait-il que la faute incombe à celui qui a cliqué sur le lien ? Les refus archivés et conservés dans ce dossier répondent à la question inverse posée à l’utilisateur : la position adoptée est que le titulaire du compte a créé la clé et doit assumer la perte. Cette même architecture est décrite comme une défaillance du fournisseur d'un côté et une responsabilité de l'utilisateur de l'autre. Il ne s'agit pas là d'une question technique, et ce n'est pas une question que cette enquête peut trancher : c'est à un tribunal ou à une autorité de contrôle qu'il appartient de se prononcer.\n\nUne illustration, pas une preuve — la norme appliquée à l'envers\nUn prestataire de services de paiement qui permettait à un script tiers de générer des identifiants de transaction dotés de tous les privilèges à partir d'un simple cookie de navigateur, sans que le titulaire du compte ne soit averti.\nUn fournisseur d'identité qui a comblé la faille par laquelle ses jetons avaient été créés et qui n'a publié aucune information concernant les jetons déjà créés.\nUne banque qui, face à un virement contesté, a répondu en indiquant que les identifiants utilisés étaient enregistrés sur le compte du client lui-même, et a classé le dossier.\n\nAucune de ces observations ne vise à tirer des conclusions concernant une entreprise en particulier. Il s’agit des mêmes choix de conception, transposés dans un contexte où la réponse des autorités de surveillance est bien documentée — et c’est précisément la comparaison qu’on demande à l’autorité de régulation d’effectuer.\n\nCe qui ressort du dossier : Les contrôles qui faisaient défaut dans l'API Web Steam étaient publics, obsolètes et, dans plusieurs cas, constituaient des conditions Valve que l'entreprise devait remplir pour pouvoir continuer à expédier ses propres produits. L'intervalle entre chaque norme et la modification équivalente Steam est mesurable et est précisé ci-dessus. Ce que cela ne précise pas, c'est pourquoi. Aucune Valve justification n’a été trouvée pour aucun de ces intervalles, et aucune n’est supposée ici ; ce document figure dans Valve et n’a pas été publié.\n\nSources, toutes issues de documents publics : OAuth 2.0 — RFC 6749, octobre 2012 ↗ · Google Cloud — Documentation sur les clés API ↗ · Exigence 8.3 de la norme PCI DSS 3.2 — Guide des ressources du PCI SSC ↗ · Apple — Obligation prochaine d'authentification à deux facteurs pour les titulaires de compte, 20 février 2019 ↗ archivé 2025-05-06 ↗ · Twitch — exigence de validation du jeton ↗ et le Avis de fermeture de la version 5 ↗ archivé 2025-01-27 ↗. Les dates propres à Steam sont celles figurant dans l'enregistrement de mise à jour de cette section ; les entrées de 2023 et 2026 correspondent à celles que Valve a publiées sans journal des modifications. Consulté le 2026-09-22.\n\nValve : son propre historique de mises à jour — daté, issu de sources publiques\nDate\tValve modifier\tAnnoncé ?\tCe qui a fermé\tLag : mécanisme public → correction\tSource\n2026-09-01\tSignalement automatisé des conversations suspectes\tOui\tLiens / schémas dangereux dans les discussions de groupe\t—\tactualités ↗\n2026-01-16\tChamps d'application granulaires de l'API Web Steamworks\tOui\tChamps d'application du principe du « privilège minimal » pour les clés de développeur\t—\tannonce ↗\n2025-07-15\tCS2 : Protection des transactions et délai de rétractation\tOui\tRien. Il ne s'agit pas d'une correction de sécurité visant la cause profonde. L'accès à la récupération de compte par le service d'assistance reste inchangé. Le déclenchement d'une annulation entraîne automatiquement un blocage des opérations pendant 30 jours (Skinvault ↗), tandis qu'un choc sur le marché au comptant a entraîné une chute de $104M (-25%) de la capitalisation boursière en 24 heures (CSMarketCap ↗). En 2026, les délais ont été fixés par article (Skin.land ↗).\t—\tFAQ ↗\n2025-05-14\tAnnonce concernant la sécurité des comptes\tOui\tGuide sur le vol d’identité et le détournement de session\t—\tannonce ↗\n2024-10-02\tCS2 « The Armory » : délai de 7 jours\tOui\tSuspension des échanges/du marché pour les objets d'armurerie\t—\tannonce ↗\n2024-09-18\tRestriction relative à la connexion sur un nouvel appareil\tOui\tBlocage des transactions pendant 2 à 7 jours sur les nouveaux appareils\t—\tFAQ ↗\n2024-02-14\tSuspension de la modification du nom de profil et de l'avatar\tOui\tDélai d'attente de 2 à 4 heures pour les échanges après un changement de nom\t—\tpublication ↗\n2023-12-04\tConfirmation sur mobile pour les clés API\tPas de journal des modifications\tEnregistrement silencieux d'une clé via un cookie uniquement\tEnviron 6 ans après les panneaux de l'époque de 2017\tpage de développement ↗\n2023-10-24\tAuthentification multifactorielle par SMS pour la publication des versions de jeux\tOui\tPublication d'une version via Steamworks\t—\tannonce ↗\n2023-07-12\tAvertissement concernant le contenu de la biographie personnalisée\tOui\tLiens de hameçonnage dans les biographies\t—\tforum ↗\n2023-01-25\tProfil {LIEN SUPPRIMÉ} et temps de recharge\tOui\tLiens dans le texte du profil\t—\tFAQ ↗\n2022-10-24\tRefonte de la procédure de connexion et tronquage des cookies\tPas de journal des modifications\tUn nombre illimité de sessions volées\t— (Migration des jetons IAuthenticationService)\tactualités ↗\n2022-10-12\tApplication mobile 3.0 : connexion via QR code\tOui\tPanneau de désauthentification de session\t—\tactualités ↗\n2022-05-10\tSuppression des points de fin de transaction\tPas de journal des modifications\tÉchange d'offres (annulation et nouvel envoi)\tEnviron 5 ans après les panels de l'époque de 2017\tnuméro n° 325 ↗\n2020-05-25\tBlocage des échanges de 7 jours dans Dota 2\tOui\tRevente rapide d'objets\t—\tblog ↗\n2018-03-29\tBlocage des échanges de 7 jours dans CS:GO\tOui\tBlanchiment instantané de bots\tEnviron 20 mois après la déclaration de juillet 2016\tblog ↗ archivé 2025-02-26 ↗\nSources : les publications Valve liées, les pages d'aide et les tickets GitHub, aux dates indiquées. Trois corrections décisives ont été déployées sans journal des modifications (mai 2022, octobre 2022, décembre 2023) et ont été détectées par les utilisateurs, sans avoir été annoncées par Valve — cette asymétrie fait partie du bilan des mesures prises. Les retards ne sont calculés que lorsque la chronologie du dossier lui-même (déclaration de juillet 2016 ; forums de signalement d’arnaques datant de 2017) fournit le point de départ ; « — » signifie qu’aucun point de départ n’est établi ici.\nPartie A — Dossier technique · Section 6\nSimulateur interactif d'exploitation et de détournement\nContexte et limites de la source\n\nReconstitution du parcours, depuis le message de hameçonnage jusqu’à l’enregistrement de la clé côté serveur et à l’échange. Avant 2023, une clé d’API Web enregistrée sur un compte permettait de consulter son inventaire, d’annuler une offre d’échange en attente et d’en créer une nouvelle, sans qu’aucun écran de confirmation d’échange ne s’affiche pour le titulaire du compte lors de ces actions. Il s’agit là d’une violation du principe du privilège minimal (OWASP A01:2021). Les durées indiquées dans cette simulation sont données à titre indicatif et ne correspondent pas à des mesures en temps réel de la plateforme actuelle.\n\nParcourez étape par étape la reconstitution du piratage. Chaque phase montre ce que voit le titulaire du compte et, à côté, l'appel Steam qu'il reçoit au même moment. Chacun de ces appels est correctement authentifié. Aucune étape de la séquence ne nécessite que l'authentification de Steam échoue — il suffit que la clé qu'elle génère n'ait aucune portée (OWASP A01:2021).\n\nCe que voit le joueur. Ce qui change en coulisses.SIMULATEUR DE PARCOURS\nÉtape 5 / 5\n\nL'exploitation est terminée. S'attendant à recevoir une notification sur son mobile concernant sa transaction initiale, la victime valide la transaction de remplacement. Il s'agit d'une démonstration forensic intégrée montrant comment l'absence du principe du « privilège minimal » (OWASP A01:2021) permet un détournement automatisé d'actifs en moins d'une seconde.\n\n01 / L'APPÂT À CHATUn ami me demande de voterLa victime reçoit un message contenant un lien.\n02 / LA CONNEXIONUn portail dédié aux sosiesLa victime saisit ses identifiants de connexion.\n03 / L'ACCÈSCréation d'une API « Silent Web »L'attaquant enregistre une clé de développeur.\n04 / LE CHANGEMENTÉchange commercial légitimeLe bot « Clone » crée une copie du destinataire ciblé.\n05 / CONFIRMATIONContrefaçon autoriséeUne offre erronée a été validée sur mobile.\nLa même étape, vue du point de vue du réseauReconstitution de la tendance antérieure à 2023 · exemples de formes d'appels\nVictimeValide la notification mobile attendue pour la transaction initiale.\nAttaquantReçoit les articles sur le compte clone.\nSteam voitUn virement validé par le titulaire du compte sur un appareil enregistré.\nConfirmation genuine — made by the account holder\nRecipient the clone bot, not the intended counterparty\nThe confirmation is authentic. The offer it confirms is not the one the user initiated.\n\nLes traces laissées : une transaction approuvée par l'utilisateur. C'est l'enregistrement que le service d'assistance Steam consulte lorsque la réclamation est reçue, et la raison pour laquelle les réclamations archivées ont été classées comme « erreur de l'utilisateur ». Les réclamations se trouvent dans les archives des mesures d'exécution.\n\nPartie A — Dossier technique · Section 7\nLes points d'extrémité associés à la séquence.\nContexte et limites de la source\n\nIl s'agit des points de terminaison de l'API Web Steam que les scripts de détournement signalés ont utilisés pour intercepter des transactions sans passer par les étapes de confirmation côté navigateur.\n\nQuatre points de terminaison documentés suffisent à tout faire. Aucun d'entre eux ne présente de faille, aucun n'a besoin d'être exploité : une clé valide les appelle et Steam répond. La clé est la seule chose que l'attaquant a dû voler.\n\nIEconService / GetTradeOffers / v1SONDAGE\n\nPermet de suivre les offres de transaction du compte. Des scripts interrogent régulièrement ce point de terminaison à l'aide de la clé API piratée ; celui-ci renvoie les détails des offres de transaction nouvellement créées, en attente ou modifiées. Les intervalles d'interrogation ne sont pas mesurés ici.\n\nVecteur de menace : Affiche les références des offres commerciales en cours ainsi que les informations du profil du destinataire.\nIEconService / Annuler une offre commerciale / v1INTERACTION\n\nUtilisé pour invalider par programmation l'offre d'échange légitime de l'utilisateur. Avant 2023, aucune authentification renforcée ne protégeait la clé ; ainsi, un serveur automatisé pouvait annuler une offre dès qu'elle était détectée, sans que le titulaire du compte ne soit averti.\n\nVecteur de menace : Annule la transaction avant que le titulaire du compte n'ait validé la confirmation sur son mobile.\nISteamUser / GetPlayerSummaries / v2RECON\n\nRequête visant à récupérer le nom du profil, l'URL de l'avatar et le niveau du destinataire légitime de la transaction. Cela permet au script d'adapter un compte clone pré-configuré en conséquence. Aucun temps n'est mesuré ici.\n\nVecteur de menace : Fournit les données nécessaires pour se faire passer pour le destinataire visé.\n/dev/ajaxregisterkeyCRÉATION\n\nLe point de terminaison d'enregistrement des clés de Steam. Auparavant, toute session de cookie de navigateur active (`steamLoginSecure`) pouvait enregistrer une clé sans confirmation Steam Guard sur l'appareil mobile et sans aucune notification au titulaire du compte.\n\nVecteur de menace : Identifiants persistants créés par un script, à l'insu du titulaire du compte.\nPartie A — Dossier technique · Section 8 · Article 7 du RGPD\nUne case cochée. Qui a coché cette case ?\nContexte et limites de la source\n\nEn cas de refus de remboursement, Steam Les réponses du service d'assistance conservées dans les archives indiquent que le titulaire du compte a créé la clé API et qu'en cochant la case, il a accepté les conditions générales.\n\nLa réponse du service d'assistance attribue la clé au titulaire du compte. La question est de savoir si le dossier permet d'établir qui l'a réellement créé.\n\nDans le schéma de détournement de clé API observé, cependant, la victime n'a jamais vu ni accédé à la page de création de clé API. Le champ de consentement est soumis par un script exécutant une requête POST « headless » à l'aide du cookie de session volé.\n\nEn vertu de l'article 7 et de l'article 4, paragraphe 11, du RGPD, le consentement doit constituer une manifestation de volonté libre, spécifique, éclairée et sans ambiguïté de la part de la personne concernée. Les auteurs estiment qu’un champ d’acceptation des conditions soumis par un script malveillant à l’aide d’un cookie volé, sans qu’aucune page ne soit affichée au titulaire du compte, ne peut répondre à cette définition. Il appartient à l’autorité de contrôle de déterminer si tel est le cas.\n\nAnalyse des charges utiles à des fins judiciaires : enregistrement des clés\nPUBLICATION https://steamcommunity.com/dev/ajaxregisterkey\n// Contenu de la requête (injecté via un script de détournement)\n{\n« agreeToTerms » : « d'accord », <-- généré automatiquement, sans intervention humaine\n« domaine » : « localhost », ← non validé — toute valeur est acceptée, y compris « localhost »\n« sessionid » : « 8f0d8ef763ab2140bf89de2a »\n}\nLa question posée à l'autorité de contrôle : lorsque le titulaire du compte n'a jamais coché la case de consentement, la question est de savoir si l'acceptation des conditions enregistrée pour ce compte répond à l'exigence de l'article 7, à savoir une manifestation de volonté libre, spécifique, éclairée et non équivoque de la part de la personne concernée, et si le service client Steam peut s'appuyer sur cet élément pour rejeter une réclamation.\n\nSource : forme de la requête d'enregistrement de clé telle qu'elle a été reconstituée à partir du point de terminaison public et des rapports de détournement conservés dans les archives des preuves (version consultable de 2026-09-17) · L'identifiant de session affiché est un espace réservé, et non une valeur enregistrée.\n\nAutopsie médico-légale · Le vecteur de substitution des produits\nComment Valve a finalement mis fin à la « substitution commerciale » — et pourquoi il a fallu sept ans de solutions de contournement\n\nDepuis près d'une décennie, le « Substitution de clé API » (ou arnaque de type « MitM » via l'API) était le modèle de vol de comptes le plus lucratif sur Steam, permettant de détourner des centaines de millions de dollars en skins au détriment de joueurs qui ne se doutaient de rien. Valve n’a pas éliminé cette faille en corrigeant l’architecture API vulnérable ; au lieu de cela, Valve a passé sept ans à mettre en place quatre barrières à l’échelle de la plateforme qui ont paralysé la liquidité des échanges au sein de la communauté, sans pour autant s’attaquer à la cause profonde du problème.\n\n1. La mort par mimétisme\nDélai de recharge de l'avatar et du nom (février 2024)\n\nCette faille nécessitait une imitation en moins d'une seconde : le bot malveillant interceptait une transaction sortante, récupérait l'avatar et le nom du destinataire via ISteamUser, et a cloné le profil en 200 ms. Le 14 février 2024, Valve a discrètement mis en place une mesure obligatoire Délai de recharge de 2 à 4 heures pour les échanges (Erreur 34) immédiatement après tout changement de nom de profil ou d'avatar. Un bot ne peut plus cloner un destinataire à la volée sans se priver lui-même de la possibilité d'effectuer des transactions.\n\n2. La mort économique\nInversion de tendance sur le CS2 sur 7 jours (juillet 2025)\n\nValve a mis en place, de manière unilatérale, Inversions de tendance pour les objets de Counter-Strike. Tout skin échangé est marqué comme « Protégé contre les échanges » pendant sept jours. Si une victime constate une substitution, elle clique sur « Annuler l’échange » dans l’assistance Steam, et le skin est immédiatement restitué dans son inventaire tandis que le destinataire est bloqué. Comme le verrouillage des échanges de 7 jours empêche les escrocs de transférer l’objet vers un site de revente, le vol n’est plus rentable.\n\n3. La mort d’un « Silent Key »\nMise à jour obligatoire des notifications push mobiles pour l'API (décembre 2023)\n\nPar le passé, un cookie de session volé permettait à des scripts malveillants d'exécuter une requête POST en arrière-plan et sans interface graphique vers /dev/ajaxregisterkey sans en informer la victime. Le 4 décembre 2023, Valve a imposé une confirmation explicite par notification push sur l’application mobile Steam pour générer une clé API Web, mettant ainsi fin à l’attribution silencieuse de clés en arrière-plan.\n\n4. Alertes mobiles intégrées à l'application\nBannières « Âge et nom du compte » (2022-2024)\n\nValve a repensé la fenêtre contextuelle de confirmation sur mobile afin d'afficher les informations relatives au partenaire commercial Steam ancienneté du compte (date de création), niveau Steam, et une alerte orange explicite : « Cet utilisateur a récemment modifié le nom de son profil », brisant ainsi l'illusion d'optique pour les victimes attentives.\n\nLes trois failles du « patchwork » de Valve : pourquoi les escrocs se sont simplement tournés vers d'autres cibles\n1. La faille liée à l'exclusion des jeux (Dota 2 et TF2)\n\nLes « Trade Reversals » ont été utilisés exclusivement pour Counter-Strike 2. Les objets de Dota 2 et Team Fortress 2 ne bénéficient toujours d'aucune protection en raison de la complexité de la fabrication et de l'encastrement. Les objets haut de gamme valant des milliers de dollars (Dragonclaw Hooks, Golden Baby Roshans, flammes ardentes TF2 « Unusual ») ne bénéficient d’aucun délai de rétractation. Les escrocs ont simplement redirigé l'interception automatisée via API vers les traders de Dota 2 et TF2, où le service d'assistance Steam applique strictement sa politique de 2016 interdisant la « restauration d'objets ».\n\n2. Le réservoir « Zombie Key » (sans date d'expiration)\n\nAlors que Valve a ajouté l'authentification à deux facteurs (2FA) par notification push mobile pour générer nouveau en décembre 2023, Valve les clés API héritées existantes n'ont jamais été révoquées, n'ont jamais expiré et n'ont jamais été supprimées. Des millions de comptes actifs ayant généré des clés (ou pour lesquels des clés avaient été créées à leur insu par hameçonnage ou des logiciels malveillants avant décembre 2023) contiennent toujours des identifiants actifs avec expiration nulle (pas de TTL) et délai d'inactivité nul. Les acteurs malveillants disposent d’énormes bases de données historiques contenant ces clés persistantes et continuent d’interroger IEconService en toute tranquillité.\n\n3. La sanction infligée à la victime : suspension des opérations de trading pendant 30 jours\n\nMême dans CS2, Valve pénalise le joueur victime d'une arnaque : cliquer sur « Annuler l'échange » dans Steam Support inflige automatiquement une suspension obligatoire de 30 jours des opérations de trading et d'accès au marché communautaire sur le compte de la victime. Valve sanctionne l'utilisateur par une exclusion de la plateforme d'un mois afin de dissuader les annulations « futiles » et d'empêcher les victimes d'annuler des transactions portant sur des articles liquides de faible valeur.\n\nLe scandale au cœur de la réglementation : sept ans de solutions de contournement contre un seul champ d'application de l'API\n\nPourquoi Valve a-t-il passé sept ans à mettre au point des blocages de transactions, des délais de recharge des comptes et des verrouillages de transactions réversibles — bouleversant ainsi l'ensemble de l'économie du jeu et faisant perdre $104M de capitalisation boursière — au lieu d'appliquer la solution standard du secteur ?\n\nComme l'atteste la sortie officielle de Valve sur Steamworks le 16 janvier 2026 (Annonce #493839547938902179 ↗), Valve déjà construits Groupes d'autorisations granulaires (Général, Microtransactions, Économie, Données de vente) et Liste blanche d'adresses IP pour les clés d'éditeur d'entreprise. Valve disposait de la solution technique depuis des années. Une simple case à cocher accessible à l'utilisateur —« Empêcher cette clé d'API Web d'accéder à IEconService (Gestion des transactions) » ou une liste blanche d’adresses IP résidentielles — aurait permis d’éradiquer l’arnaque à la substitution commerciale en 2018 sans aucun préjudice économique collatéral. Valve a refusé d’accorder aux joueurs réguliers la protection qu’elle avait mise au point pour ses partenaires commerciaux.\n\nPartie B — Règles et bilan de leur application · Article 9\nLeur règlement. Les plateformes enregistrées.\nContexte et limites de la source\n\nCe registre met en correspondance les clauses explicites issues du Steam Contrat d'abonnement (SSA) et Steam Comportement en ligne (SOC) des directives visant directement les grandes entreprises commerciales en activité.\n\nLa règle : pas d'utilisation commerciale, pas de jeux d'argent, pas de bots — et Steam Le service client invoque ces clauses lorsqu'il refuse de restituer les articles d'une victime. Le bilan : ces mêmes clauses, à première vue, s'appliquent aux plateformes commerciales figurant dans ce registre, qui fonctionnent selon les principes suivants : Steam identités, Steam bots et Steam transferts. Cette clause s'applique à la personne qui a perdu les peaux et non, d'après les registres publics, aux entreprises qui les ont transportées.\n\nDans les réclamations archivées, Steam Support mentionne le « Aucune utilisation commerciale » et « Pas d'automatisation ni de bots » clauses invoquées pour refuser de restituer des biens aux victimes de fraudes liées aux clés API. Ces mêmes clauses s'appliquent, à première vue, aux plateformes commerciales répertoriées dans ce dossier, qui s'authentifient via Steam OpenID et transfèrent des biens par le biais de comptes automatisés Steam. Aucun chiffre d’affaires global du marché n’est estimé ici (voir les statistiques d’application ci-dessous). Les données disponibles montrent la règle appliquée aux comptes individuels dans les cas archivés, mais aucun bilan d’application par opérateur n’a été publié pour ces plateformes. C’est cette asymétrie que la présente section met en évidence.\n\nLa question centrale / l'application sélective de la loiRègles → Échelle → Responsabilité\nUn seul règlement. Une application inégale.\n\nLe registre fait état de services commerciaux utilisant des identités Steam, des inventaires, des bots et des transferts comme infrastructure opérationnelle. La SSA interdit l’exploitation commerciale et l’automatisation sans autorisation. Les plaintes archivées montrent que cette règle s’appliquait aux comptes individuels, tandis que le registre public ne présente pas de relevé équivalent, opérateur par opérateur, pour les plateformes mentionnées ici. Publiez la règle, les éléments de preuve et la décision d’application pour chacune d’entre elles.\n\n189sites web concernés par l'audit\n44itinéraires de domaines distincts figurant dans le registre actif — 27 accompagnés d’un dossier de preuves publié, 17 recueillis manuellement. L’audit des navigateurs portant sur 189 sites web a permis à lui seul d’en résoudre 25 ; le registre ajoute les itinéraires recueillis manuellement.\n12 ans et 6 moiscsgogem.com bloqué dans le filtre de liens ; api.csgem.com enregistrée le 2014-03-08 et jamais bloquée — l'une des 26 paires de ce type au 2026-09-22\nTotal non vérifiéestimation du chiffre d'affaires à l'échelle du marché non incluse\nSteam Comportement en ligne\n« …vous ne devez pas commettre ni tenter de commettre l’un des actes suivants sur Steam : […] Se livrer à une activité commerciale. Voici quelques exemples de comportements interdits : publier des publicités ; organiser des jeux-concours ; jeux d'argent; l'achat ou la vente de comptes « Steam » ; la vente de contenus, de cartes-cadeaux ou d'autres articles ; et la mendicité. »\n\nstore.steampowered.com/online_conduct ↗ archivé 2026-09-21 ↗\n\nSSA § 2.G — Utilisation commerciale\n« …[vous ne pouvez pas] exploiter le Contenu et les Services, ni aucune partie de ceux-ci, à des fins commerciales, sauf autorisation expresse prévue ailleurs dans le présent Contrat… »\n\nLes notifications de Valve pour 2016, comme indiqué, invoquaient la licence personnelle et non commerciale. Aucun opérateur n'a présenté d'autorisation Valve dans le dossier. store.steampowered.com/subscriber_agreement ↗ archivé 2026-09-18 ↗\n\nSteam Conditions d'utilisation de l'API Web\n« Vous ne devez pas utiliser l’API Web Steam ni les données Steam d’une manière qui enfreigne le contrat d’abonnement Steam. »\n\nLes plateformes tierces de vente de skins fonctionnent grâce à des comptes automatisés qui utilisent l'API Steam. Le texte de la règle ne prévoit aucune exception pour une utilisation à des fins commerciales. steamcommunity.com/dev/apiterms ↗ archivé 2026-09-21 ↗\n\nSSA § 4.C\nAutomatisation\n\nLes scripts, les bots et les interactions non humaines sont interdits. Le registre recense les opérations de trading effectuées par des bots, les réseaux de comptes automatisés et le routage automatisé à l'échelle commerciale.\n\nInspecter 153enregistrements classés sous cette clause ↗\nCe que prévoit le texte en vertu de cette clause153 plateformes taguées\nOuverture du dossier15\nSkin Casino13\nMarché CS29\nRoulette de la peau8\ncsgoempire.com→csgoempirelogin4.comCasino\nrollbit.com→rbsnin.comCasino crypto\n500.casino→fivezerozero.coCasino agréé\n\nParmi ceux-ci, 153 sont également classés sous les articles 2.G du SSA et 2 sont également répertoriés sous le §1.C du SSA — les mêmes services relevant de plusieurs clauses, ce qui explique pourquoi les exemples se répètent.\n\n28 de l’153, ont été observés en train d’effectuer une authentification via un domaine distinct pouvant faire l’objet d’un enregistrement. Une balise consigne une observation datée qui fait entrer la plateforme dans le champ d’application de la clause telle qu’elle est libellée ; il ne s’agit pas d’une infraction constatée, et aucune autorisation de l’Valve n’a été présentée pour aucun d’entre eux.\n\nSSA § 2.G\nUsage commercial\n\nToute exploitation commerciale nécessite une autorisation expresse. Comparez les modèles économiques documentés, leur ampleur ainsi que toute autorisation ou mesure d'application rendue publique.\n\nInspecter 175enregistrements classés sous cette clause ↗\nCe que prévoit le texte en vertu de cette clause175 plateformes taguées\nOuverture du dossier15\nSkin Casino13\nMarché CS29\nRoulette de la peau8\ncsgoempire.com→csgoempirelogin4.comCasino\nrollbit.com→rbsnin.comCasino crypto\n500.casino→fivezerozero.coCasino agréé\n\nParmi ceux-ci, 153 sont également classés sous les articles 4.C du SSA et 24 sont également répertoriés sous le §1.C du SSA — les mêmes services relevant de plusieurs clauses, ce qui explique pourquoi les exemples se répètent.\n\n28 de l’175, ont été constatées lors d’une authentification via un domaine enregistrable distinct. Une balise consigne une observation datée qui fait entrer la plateforme dans le champ d’application de la clause telle qu’elle est libellée ; il ne s’agit pas d’une infraction constatée par une décision judiciaire, et aucune autorisation de l’Valve n’a été présentée pour aucune d’entre elles.\n\nSSA § 3.A\nVPN et dissimulation de l'emplacement\n\nLe fait de masquer son adresse IP à l'aide d'un proxy peut entraîner la résiliation du contrat. Les serveurs d'authentification sur des domaines distincts nécessitent une analyse spécifique : il convient de déterminer ce qui est masqué et quelle règle s'applique.\n\nVérifier les informations relatives à l'hôte d'authentification ↗\nSteam Aide / Politique relative aux URL\nMasquage des liens\n\nSteam interdit les services de raccourcissement de liens et les outils qui masquent la destination des liens. Un domaine d'authentification distinct — rbsnin.com dans le processus de connexion à Rollbit, auth.dota.trade dans CS.MONEY — soulève la question similaire de savoir si la destination indiquée au vérificateur OpenID de Steam identifie le site opérationnel.\n\nPolitique relative aux URL de Valve ↗\n\nRéférences réglementaires : Steam Contrat d'abonnement, version du 10 septembre 2026 archivé 2026-09-18 ↗ · Steam Conditions d'utilisation de l'API Web archivé 2026-09-21 ↗ · Steam Politique relative aux URL (masquage des liens). Les chiffres indiqués correspondent aux enregistrements et aux balises contenus dans ce dossier ; il ne s'agit pas d'un décompte des infractions ayant fait l'objet d'une décision judiciaire.\n\nLe déficit de confiance\nQui examine la décision lorsque le service d'assistance clôt le dossier ?\n\nLes réclamations conservées font état de sanctions définitives, de contestations restées sans réponse et de refus de restituer les éléments volés. Vérifiez ces déclarations en les comparant à l'historique réel des tickets, aux recours disponibles et aux journaux d'accès aux comptes. Une explication générique invoquant une tentative d'hameçonnage ne permet pas d'établir qui a lancé une réinitialisation ou créé une clé API.\n\nLire les réclamations enregistrées ↗Demander les documents correspondants →Graphique des relations entre modérateurs →\nPartie B — Règles et bilan de leur application · Article 10\nUne API d'automatisation. Une règle interdisant l'automatisation.\nContexte et limites de la source\n\nLa question soulevée dans cette section est de savoir comment concilier ces deux aspects : quelles utilisations de l’API sont autorisées, par qui et selon quels critères publiés ? Aucun chiffre concernant le nombre d’utilisateurs commerciaux autorisés de l’API n’est estimé ici, et l’absence de liste publiée n’implique aucun chiffre — c’est l’absence elle-même qui constitue le constat, et non un chiffre sous-jacent. Les messages d’assistance Steam cités ci-dessus sont reproduits par le projet ArchiSteamFarm dans sa propre FAQ (vérifiés mot pour mot 2026-09-22) ; il ne s’agit pas de Valve publications, et les comptes auxquels ils ont été envoyés ne sont pas identifiés.\n\nLa règle (SSA § 4.C) : Pas de scripts, pas de bots, pas de systèmes non humains sur Steam. Le bilan : Valve propose une API REST « headless » dont l'unique objectif est l'automatisation de serveur à serveur, et fournit la clé à n'importe quel compte. Les utilisateurs sont bannis pour utilisation d'outils d'automatisation ; l'interface d'automatisation est un produit développé par Valve. La liste des utilisations commerciales autorisées n'a jamais été publiée.\n\nLe mythe du « développeur de jeux vidéo »\nSDK Steamworks (version officielle)\n\nUtilisé par des studios de jeux vidéo reconnus pour intégrer des succès, un système de mise en relation entre joueurs et des classements dans leurs clients de jeu. Nécessite une intégration complexe en C++ et une procédure officielle d'intégration en tant que partenaire.\n\nSteam API Web (The Loophole)\n\nUne architecture JSON/REST « headless » conçue pour les serveurs web externes. Dans le modèle de détournement décrit ici, elle est utilisée pour lire des inventaires et manipuler des échanges peer-to-peer à partir de serveurs distants ; ses utilisations légitimes ne sont pas répertoriées dans ce dossier.\n\nÀ qui est destinée cette clé ?Un utilisateur ordinaire Steam n'a pas besoin d'une clé d'API Web au sein du client ; la page dédiée aux clés se trouve sous une URL réservée aux développeurs et son objectif, tel qu'il est documenté, est l'accès externe côté serveur. Les plaintes archivées pour détournement de compte font état de victimes qui ignoraient l'existence de cette page jusqu'à ce qu'une clé ait été enregistrée sur leur compte.\nLa contradiction de l'automatisation\n\nL'article 4.C du SSA dispose : « Il est interdit d'utiliser, de quelque manière que ce soit, des scripts, des bots, des macros ou tout autre système non contrôlé par un être humain (« automatisation ») pour interagir avec le Contenu et les Services sur Steam. » Pourtant, les points de terminaison de l'API Web (tels que CancelTradeOffer) ne nécessitent ni interface utilisateur ni captcha et contournent entièrement le client Steam. L'API est conçue pour l'automatisation de serveur à serveur ; la règle interdit l'automatisation par les utilisateurs ; la frontière entre les deux n'est pas publiée.\n\nUn rôle côté serveur dans le flux commercial\n\nUne clé API Web permet à un serveur tiers d'intervenir sur les transactions du compte sans passer par le client Steam. Dans le scénario de détournement, ce serveur se place entre le titulaire du compte et le serveur de transactions.\n\n→Aucun écran de confirmation de transaction ne s'affiche pour les actions effectuées à l'aide de cette touche.\n→Permet l'interrogation en arrière-plan (GetTradeOffers).\n→Annule et réémet les offres sans intervention de l'utilisateur.\nValve a développé l'interface, a interdit l'automatisation par les utilisateurs dans ses règles et n'a publié aucun critère précisant quelles utilisations commerciales sont autorisées.\nPartie B — Règles et bilan des mesures coercitives · Article 11\nDix jours exigés. Dix ans à justifier.\nContexte et limites de la source\n\nLe 20 juillet 2016, le directeur juridique de Valve a fixé un délai de 10 jours aux opérateurs de jeux d'argent. Dix ans plus tard (à la date de la capture d’écran du dossier, 2026-09-21), au moins une plateforme citée dans les articles de presse relatifs à cet avis, CSGOFast, est toujours opérationnelle avec un hôte d’authentification sur un domaine distinct. Le texte est reconstitué ci-dessous à partir d’articles de presse du 21 juillet 2016 ; cette reconstitution n’est pas un scan. Le dossier d’application de la loi auquel l’avis faisait allusion n’a pas été publié. La lettre ouverte adressée à la Commission est Section 2.\n\nVeuillez consulter l'avis de juillet 2016 figurant à côté des observations ultérieures. Il reste à établir un bilan de la mise en application par opérateur.\n\nUne semaine auparavant — le 13 juillet 2016, en public\n\nLe 13 juillet 2016 archivé 2026-09-21 ↗, Valve a expliqué comment les sites de jeux d'argent utilisaient Steam : OpenID pour l'identification des comptes et des comptes automatisés pour les transactions. Valve a déclaré que l'utilisation de ces mécanismes pour exploiter une activité de jeux d'argent constituait une violation de son API et de ses conditions d'utilisation. La description du mécanisme et l'interdiction figurent toutes deux dans la déclaration datée de Valve lui-même. Le 2026-09-21, les hôtes d'authentification à domaine distinct testés n'ont renvoyé aucun blocage de filtre de lien, et le Valve n'a publié aucun enregistrement d'application par opérateur.\n\nANNEXE A / JUILLET 2016RECONSTITUTION DE LA COMPOSITION TYPOGRAPHIQUE\nVALVE CORPORATION\n\nBellevue, État de Washington\n\nDATE :Juillet 2016 (selon la presse du 21 juillet 2016)\nDE :Karl Quackenbush, directeur juridique\nRE :Mise en demeure — utilisation commerciale des comptes Steam\nREMARQUE :Reconstitution du texte tel qu'il a été rapporté ; il ne s'agit pas d'une numérisation\n\n« Nous savons que vous exploitez l'un des sites de jeux d'argent énumérés ci-dessous. Vous utilisez Steam comptes pour exercer cette activité. Conformément au Steam Contrat d'abonnement, les services Steam et Steam sont autorisés uniquement à des fins personnelles et non commerciales. »\n\n« Vous devez cesser immédiatement toute utilisation de vos comptes Steam à des fins commerciales. Si vous ne vous conformez pas à cette exigence, dans un délai de dix (10) jours, Valve fera valoir tous les recours à sa disposition, y compris, sans s'y limiter, la résiliation de vos comptes. »\n\nReconstitution du dossier · consulter le document source\nKarl Quackenbush\nDirecteur juridique, Valve Corp.\nEN MARGE / ÉDITORIAL\nDix jours.Et ensuite ?\n\nLa date limite était clairement fixée. Il devrait en être de même pour les mesures concrètes prises par les pouvoirs publics.\n\nLa position officielle de Valve sur « 2016 » ↗\nRemarque concernant la date limite +\nSATIRE / CORRESPONDANCE NON OFFICIELLE\n\nChère date limite,\n\nOn t'avait accordé dix jours. Bizarrement, le calendrier était la seule chose qui continuait de fonctionner.\n\nMerci de bien vouloir transmettre toute réponse au dossier public.\n\nChronologieJuillet 2016 – septembre 2026\nDate limite indiquée dans l'avis :\n10 jours\nJuillet 2016\nDélai écoulé depuis l'avis :\n3,715 jours\nChiffre fixe correspondant à la période allant du 20 juillet 2016 à la date de l'instantané du dossier du 21 septembre 2026 ; il ne s'agit pas d'un chiffre en temps réel.\nHistorique des mesures coercitives rendues publiques :\nAucun\nAucun relevé par opérateur concernant les résiliations ou les blocages n'a été trouvé\n\n◀ Jours 0 à 10 — la date limite, à adapterJour 3715 — l'instantané ▶\n\n20 juillet 2016Délai de dix jours accordéJour 0\n17 février 2024Les obligations prévues par la DSA s'appliquentJour 2,768\n25 février 2026Annonce d'une plainte déposée par le procureur général de New YorkJour 3,507\n21 septembre 2026Aperçu du dossierJour 3715\n\nDix ans plus tard, CSGOFast — cité dans les articles de presse relatifs aux notifications de 2016 — est opérationnel : csgofast.com a renvoyé un blocage « Link Filter » pour 2026-09-19 et 2026-09-21, tandis que son hôte d'authentification steam-login.authtofast.com (enregistré 2026-06-30) ne l'a pas fait.\n\nHistorique complet et daté des modifications apportées à la sécurité par Valve : Chronologie de la sécurité → · La jurisprudence de Washington et le critère d'application : ci-dessous\n\nCe que révèlent les éléments du dossier : L'avis de 2016 fixait un délai de 10 jours ; Valve gérait déjà une liste de domaines (le « Link Filter ») et recevait les noms d'hôtes d'authentification dans ses propres requêtes OpenID ; aucun rapport sur les mesures d'application par opérateur n'a été publié. Des rapports de la communauté font état d’une action menée en 2018 contre une place de marché (SkinJar), mais ces rapports n’ont pas été vérifiés et ne sont pas pris en compte ici.\nCSGOFAST / LA VOIE D'AUTHENTIFICATION ENREGISTRÉE\nSuivez l'hôte de retour indiqué.\n\nLes liens vers les itinéraires enregistrés csgofast.com à steam-login.authtofast.com. Le nom d'hôte distinct est transmis dans la requête OpenID Steam. Il fournit aux enquêteurs une adresse concrète à comparer avec les registres de filtrage et d'application de la règle Valve.\n\nConsultez le parcours de CSGOFast et sa source ↗ · Comparer les résultats enregistrés Steam Filtrer les liens ↗\n\nARCHIVES PUBLIQUES / WASHINGTON · 2016 → 2026\nDeux délais. Une norme d'application qui reste sans réponse.\n20 JUILLET\nValve accorde 10 jours aux sites de jeux d'argent\n\nDans sa mise en demeure, son avocat a averti que la poursuite de l'utilisation commerciale des comptes Steam pourrait entraîner la résiliation du contrat.\n\n27 septembre\nWashington fait pression Valve\n\nLa Commission des jeux de l'État a exigé des preuves des mesures prises pour mettre fin aux transferts de « skins » à des fins de jeu et a fixé au 14 octobre la date limite de réponse.\n\n17 OCT\nValve rejette l'accusation\n\nValve a répondu après l'expiration du délai, a contesté avoir facilité les jeux d'argent, a déclaré avoir désactivé les comptes associés et a indiqué ne pas vouloir désactiver les transactions et OpenID pour tous les utilisateurs. Au moins une plateforme citée dans les articles de presse relatifs aux avis de juillet (CSGOFast) était toujours en activité dix ans plus tard. Ces deux faits ne peuvent être conciliés que si l'opérateur a remplacé les comptes désactivés ; le document qui permettrait de le prouver n'a pas été publié. La WSGC devrait demander à Valve de concilier ces deux éléments.\n\n2026\nLes itinéraires observés en septembre 2026\n\nLe registre des itinéraires recense 44 plateformes s'authentifiant via des serveurs d'authentification de domaines distincts, dont CSGOFast, en utilisant les mécanismes OpenID et d'échange Valve décrits en 2016. Le rapport d'application qui permettrait de savoir quels opérateurs ont été coupés n'a pas été produit.\n\nCOMMUNIQUÉ DE LA COMMISSION · 30 JANVIER 2018\nDix-huit mois après la réponse de Valve, l'autorité de régulation continuait de qualifier cela d'« intention ».\n\nLors de l'audition publique relative au projet de loi HB 2881, la Commission a présenté un exposé devant son propre organe législatif et a décrit, dans ses propres termes, la déclaration de juillet 2016 : Valve « a annoncé son intention de sévir contre l'utilisation de sa plateforme pour faciliter les paris sur les skins. » Cette même page indique l'impact de cette annonce sur les prévisions du secteur — « par conséquent, » les prévisions concernant le marché des jeux d'argent « skin » pour 2020 ont été révisées, passant de $19.7 milliards à 670 millions de dollars, soit une baisse d'environ 97 %, uniquement sur la base de cette annonce. Les prévisions ont évolué. Le bilan des contrôles par opérateur qui permettrait de justifier cette mesure n'a toujours pas été publié.\n\nLes chiffres du marché sont des estimations de Narus Advisors / Eilers & Krejcik Gaming reprises dans la note d'information de la Commission, et non des conclusions de cette dernière ; ce même document estime le montant des paris « skin » en 2016 à environ $5 milliard, dont environ $3 milliards sur des sites de type casino. Récupéré le 2026-09-22, SHA-256 c507c9025f93da0aadaf395c4d8882f25973211c318ee8e9b6f18a5b3755e050.\n\nOn peut comparer la position officielle exprimée par Valve en 2016 et l'infrastructure observable aujourd'hui. La question est de savoir si les mesures de contrôle ont concerné les comptes et les itinéraires utilisés par les opérateurs interdits. Un préavis de dix jours ne constitue pas une preuve que la notification a bien été transmise à l'ensemble des opérateurs qu'il désignait. L'action menée par OPSkins en 2018 est la seule intervention avérée à l'encontre d'un opérateur identifié ; compte tenu des 189 plateformes contrôlées et de l'absence de données publiées par opérateur, une seule action avérée ne permet pas de mettre en évidence une tendance en matière d'application de la réglementation.\n\nAvis de 2016 de la Commission des jeux de Washington ↗ archivé 2026-05-20 ↗ · Réponse de Valve du 17 octobre 2016 (copie du document) ↗ · Exposé du WSGC devant l'Assemblée législative, 30 janvier 2018 (copie locale, 4 pages) ↗ · le même fichier sur wsgc.wa.gov ↗ · enregistrement de récupération et hachage ↗ · L'action OPSkins de Valve en 2018 ↗ archivé 2026-03-07 ↗ · Audit de l'itinéraire actuel ↗\n\nAudit longitudinal judiciaire · Cibles des mises en demeure de 2016\nLa « Décennie du préavis de 10 jours » : audit de survie médico-légal des 23 sites désignés\n\nLes 19 et 20 juillet 2016, Valve Karl Quackenbush, directeur juridique, a adressé des mises en demeure officielles à 23 plateformes de jeux d’argent basées sur des « skins », leur ordonnant de cesser l’utilisation commerciale des comptes Steam au sein de 10 jours sous peine de fermeture de compte et de poursuites judiciaires. Plus de 3,700 jours plus tard, un audit empirique révèle la véritable réalité de l'application de ces mesures : de nombreux opérateurs n'ont jamais cessé leurs activités, d'autres ont continué à fonctionner jusqu'à six ans après la date butoir, et cet écosystème de plusieurs milliards de dollars a continué à s'appuyer sur l'architecture OpenID de Valve.\n\n5+ EN DIRECT\nDéfinitivement opérationnels en 2026 (CSGOBig, CSGO500, CSGOFast, etc.)\n6 ANS\nDurée maximale entre la publication de l'avis et la fermeture (CSGOatse restera actif jusqu'en 2022)\n$5.01B\nVolume des paris « skin » en 2016 (Narus / Eilers & Krejcik)\nPlus de 200\nSites de jeux d'argent en ligne très actifs, opérant au plus fort du marché\nLes Titans survivants · Plan stratégique financier et d’audience 2024-2026\nDes alertes de 10 jours aux conglomérats offshore : un chiffre d'affaires de plusieurs milliards de dollars\n\nPlutôt que de mettre fin aux paris « skin », les avis publiés par Valve en 2016 ont catalysé une évolution du secteur. Les opérateurs qui ont survécu se sont restructurés en sociétés offshore (Curaçao, Belize, Chypre), ont été les pionniers du trading entre particuliers (P2P) pour contourner les interdictions des bots, et traitent désormais plus de 10 millions de visites mensuelles sur le site et des milliards de dollars de mises annuelles tout en continuant à s'authentifier via Steam :\n\nPlateforme / Domaine\tAvis de juillet 2016\tRésultats de l'application de la loi et statut de survie\tVérification enregistrée / Liens principaux\nCSGOBig\ncsgobig.com\tAvis de 10 jours (juillet 2016)\tTOUJOURS EN VIE EN 2026\nTemporairement suspendu, puis relancé ; authentification via letmeinbig.com et csgobiglogin.com\tX : @csgobig ↗ · FB : csgobigofficial ↗\nCSGO500\ncsgo500.com / 500.casino\tAvis de 10 jours (juillet 2016)\tTOUJOURS EN VIE EN 2026\nRebaptisé « 500 Casino » (licence de Curaçao n° 8048/JAZ2014-037), chiffre d'affaires mensuel de plusieurs millions\tPlateforme en direct (500.casino) ↗\nCSGOFast\ncsgofast.com\tAvis de 10 jours (juillet 2016)\tTOUJOURS EN VIE EN 2026\nExploitation active des jeux de roulette, crash et jackpot via steam-login.authtofast.com\tDossier d'audit d'authentification ↗\nCSGOLounge / Dota2Lounge\ncsgolounge.com / dota2lounge.com\tAvis de 10 jours (juillet 2016)\tTOUJOURS EN VIE EN 2026\nS'est recentré sur les paris liés aux cryptomonnaies dans le domaine de l'e-sport ; a maintenu une activité ininterrompue\tPlateforme en direct ↗\nCSGOCasino\ncsgocasino.net / csgocasino.gg\tAvis de 10 jours (juillet 2016)\tEN DIRECT VIA SUCCESSOR (2026)\nLe domaine a été redirigé ; le portail successeur, désormais opérationnel, est accessible à l'adresse csgocasino.gg\tDomaine successeur ↗\nCSGOatse\ncsgoatse.com\tAvis de 10 jours (juillet 2016)\tA EXISTÉ PENDANT 6 ANS (EN ACTIVITÉ JUSQU'EN 2022)\nPoursuite des activités de jeux d'argent à plein régime pendant six ans après l'ultimatum de 10 jours lancé par Valve\tX : @CSGOatsecom (Actif jusqu'en 2022) ↗\nCSGOSweep\ncsgosweep.com\tAvis de 10 jours (juillet 2016)\tA SURVÉCU JUSQU'EN DÉCEMBRE 2017\nA continué à fonctionner au public pendant 17 mois après la date limite\tX : État d'avancement de CSGOSweep, décembre 2017 ↗\nCSGOWild\ncsgowild.com\tAvis de 10 jours (juillet 2016)\tA SURVÉCU JUSQU'EN DÉCEMBRE 2017\nPromue par des influenceurs de premier plan ; a fonctionné pendant un an et demi après la mise en demeure, avant la migration vers la cryptomonnaie\tX : @Wild (Actif en décembre 2017) ↗\nCSGOPot\ncsgopot.com\tAvis de 10 jours (juillet 2016)\tA VÉCU JUSQU'EN SEPTEMBRE 2017\nA continué à proposer des paris à gros enjeux avec jackpot pendant 14 mois après la notification\tX : @csgopot (Actif en septembre 2017) ↗\nCSGODiamonds\ncsgodiamonds.com\tAvis de 10 jours (juillet 2016)\tA SURVÉCU JUSQU'AU MILIEU DE L'ANNÉE 2017\nA continué jusqu'en 2017 malgré des manipulations avouées des résultats au profit de streamers sponsorisés\tX : @csgodiamondscom (2017) ↗\nCSGOLotto\ncsgolotto.com\tAvis de 10 jours (juillet 2016)\tFERMÉ EN JUILLET 2016\nA fermé ses portes à la suite d’un scandale public ; a fait l’objet d’une ordonnance de consentement de la FTC fédérale\tOrdonnance par consentement de la FTC (dossier C-4632) ↗\nCSGODouble\ncsgodouble.com\tAvis de 10 jours (juillet 2016)\tFERMÉ EN JUILLET 2016\nFermeture volontaire immédiatement après la publication de la mise en demeure\tX : @CSGODouble (Fermé en juillet 2016) ↗\nCSGOMassive\ncsgomassive.com\tAvis de 10 jours (juillet 2016)\tFERMÉ EN 2016\nA cessé ses activités publiques fin 2016\tX : @csgo_massive ↗\nCSGOStrong\ncsgostrong.com\tAvis de 10 jours (juillet 2016)\tFERMÉ EN 2016\nA cessé ses activités publiques en 2016\tFB : csgostrongfree ↗\nSkins2\nskins2.com\tAvis de 10 jours (juillet 2016)\tFERMÉ EN 2016\nA cessé ses activités publiques en 2016\tFB : CSNCOM ↗\n\nPlateforme\tTrafic mensuel (visites)\tChiffre d'affaires / Volume estimé\tEntité juridique et juridiction\tPrincipales mesures réglementaires et modèle\nCSGOEmpire\ncsgoempire.com\t2,3 millions — 9,0 millions / mois\nDurée moyenne : 6 minutes ou plus ; 80% direct\t$1.5B — $2.5B Chiffre d'affaires annuel\n>1,000,000 transaction P2P de skins par mois ; $6.4M de volume d'ordres actifs et liquides\tMoonrail Limited B.V. (Curaçao n° 148182)\nPaiements : JHOLT LTD (Chypre) ; Fondateur : « Monarch » (Ossi Ketola)\tPionnier du commerce d'objets P2P sans frais ; titulaire de la licence OGL/2024/1183/0869 délivrée par Curaçao\nCSGORoll\ncsgoroll.com\t2,74 millions — 3,5 millions / mois\nDurée moyenne : 9 min 23 s ; taux de rebond : 16%\t$1.0B — $2.0B Chiffre d'affaires annuel\nChiffre d'affaires annuel estimé de l'entreprise, provenant de l'avantage de la maison : entre $100M et $200M\tFeral Holdings Limited\nSiège social à Belize City, au Belize (n° d'enregistrement 171519)\tInterdit par l'ACMA australienne (mai 2023) ; sponsorisait l'équipe de niveau 1 G2 Esports, qui comptait des joueurs mineurs dans ses rangs\n500 Casino (CSGO500)\n500.casino / csgo500.com\t220 000 — 425 000 / mois\nenviron 105 000 visiteurs uniques par mois\t$100k / semaine ($5.2M/an) à Royales\nCondition de mise pour les gros parieurs : $400 de mise pour chaque $1 de rakeback\tPerfect Storm B.V. (Curaçao n° 150536)\nLicence OGL/2024/1354/0882 délivrée par la Commission de contrôle des jeux de Curaçao\tInterdit par la Spelinspektionen suédoise (novembre 2023) pour avoir ciblé des joueurs suédois sans licence\nCSGOBig\ncsgobig.com\t~169,600 / mois\nDurée moyenne : 19 min 12 s ; primaires américaines\tUn chiffre d'affaires annuel de plusieurs millions\nBoîtes mystères, roulette et combats de caisses\tFonctionne via un routage par proxy auxiliaire\nletmeinbig.com (enregistré en 2023) & csgobiglogin.com\tCible de juillet 2016 pour C&D ; relancé avec une architecture d'authentification par proxy\nCSGOFast\ncsgofast.com\tenviron 150 000 — 250 000 / mois\nUn public international multilingue\tUn chiffre d'affaires annuel de plusieurs millions\nJeux de roulette et de « crash » à rythme effréné\tEntités opérationnelles offshore\nItinéraires Steam authentification via steam-login.authtofast.com\tCible de la mise en demeure de juillet 2016 ; n'a jamais cessé ses activités ; toujours en activité en 2026\nCSGOPolygon\ncsgopolygon.com / plg.bet\tenviron 300 000 — 500 000 / mois\nLa prédominance de la CEI et de l'Europe de l'Est\tUn chiffre d'affaires annuel de plusieurs millions\nRoulette crypto et skin, paris sur les matchs\tObjectif de la deuxième vague (octobre 2016)\nRéorientation vers les cryptomonnaies avec le domaine miroir plg.bet\tA tenu le coup pendant une décennie entière ; poursuit la liquidation des skins via des API tierces\nLa deuxième vague : pourquoi la mise en demeure de Valve visait au total plus de 43 sites\n\nLe 17 octobre 2016, le conseiller juridique de Valve a officiellement informé la Commission des jeux de l'État de Washington qu'à la suite des 23 premières notifications envoyées le 19 juillet, Valve avait adressé des lettres de mise en demeure à plus de 20 sites supplémentaires de jeux d'argent en « skins » (ce qui porte le total officiel à plus de 43). Cette deuxième vague s'est avérée nécessaire car la liste initiale omettait, sans raison apparente, les centres de jeux d'argent les plus importants et les plus tristement célèbres au monde :\n\nCSGOJackpot.com : Le pionnier historique des « jackpots de peau », qui a géré des centaines de millions avant de mettre la clé sous la porte sous la menace d’une mise en accusation fédérale.\nCSGOShuffle.com : Le site au cœur du scandale de streaming de juillet 2016, où le streamer Twitch PhantomL0rd détenait secrètement 33% de la société et a été dénoncé pour avoir truqué les cotes avec les fonds de la maison.\nL'écosystème macro (plus de 200 opérateurs) : Selon une étude sectorielle menée par Narus Advisors et Eilers & Krejcik Gaming, plus de 200 sites distincts de jeux d’argent « skin » étaient en activité en 2016, générant $5.01 milliards de volume de paris auprès de 3,03 millions de joueurs actifs. Les 43 lettres de Valve ne couvraient que moins de 20% du marché actif.\nEnquêtes officielles menées par les pouvoirs publics et les autorités de régulation sur les jeux d’argent « Steam Skin Gambling »\n\nLe phénomène des paris « skin gambling » est documenté dans le cadre de nombreuses enquêtes officielles, mesures coercitives et prises de position gouvernementales :\n\n1. Commission des jeux de l'État de Washington (WSGC) (2016-2018)\n\nEnvoi d'une mise en demeure officielle le 5 octobre 2016 ; publication d'une note d'information législative le 30 janvier 2018 établissant que les « skins » constituent des équivalents de trésorerie et faisant état d'un volume de paris sur les « skins » de $5.0B.\n\nRapport législatif du WSGC au format PDF (copie locale) ↗\n2. Commission fédérale du commerce des États-Unis (FTC) (septembre 2017, dossier n° C-4632)\n\nPremière mesure coercitive fédérale visant les propriétaires de CSGOLotto, Trevor Martin et Thomas Cassell, dans le cadre des jeux d'argent « skin gambling », pour pratiques trompeuses et contrôle non divulgué de la plateforme.\n\nDécision et ordonnance par consentement de la FTC ↗\n3. Document de prise de position de la Commission britannique des jeux d'argent (UKGC) et audits consacrés aux jeunes\n\nLes skins utilisés dans les jeux vidéo ont été officiellement classés comme « de l'argent ou ayant la valeur de l'argent » au titre de la loi de 2005 sur les jeux d'argent. Des enquêtes menées par la suite ont révélé que plus de 11% des enfants âgés de 11 à 16 ans avaient parié des skins dans des jeux vidéo.\n\nRépertoire de recherches de l'UKGC ↗\n4. Enquête du Sénat australien sur l’environnement et les communications (2018)\n\nRapport du Parlement fédéral sur « Microtransactions dans les jeux vidéo pour l'obtention d'objets aléatoires », en analysant les mécanismes des « loot boxes » de Valve, les retraits d'argent sur le marché secondaire et le contournement de la réglementation.\n\nEnquête du Parlement australien ↗\nLa demande en cours\n\nPublier le rapport d'application : quels comptes de jeux d'argent et quels bots ont été désactivés, quels serveurs de redirection ont été bloqués et quels services commerciaux ont reçu une autorisation. Une interdiction publique et un avertissement sur la page d'accueil ne suffisent pas à prouver que l'activité sous-jacente a été interrompue.\n\nPartie B — Règles et bilan de leur application · Article 12\nLe nom d'hôte figure déjà dans la requête.\nContexte et limites de la source\n\nValve dispose déjà d’une liste de domaines (le « Link Filter ») et reçoit déjà le nom d’hôte d’authentification dans chaque requête OpenID. Le pseudocode ci-dessous illustre la structure logique permettant de relier ces deux éléments. Aucune preuve publique n’indique que Valve procède de la sorte.\n\nValve gère déjà une liste noire de domaines. Valve reçoit déjà l'hôte de connexion dans chaque requête OpenID. Il n'y a rien à construire : il suffit de les assembler. Il s'agit d'une recherche de nom d'hôte effectuée à partir d'une liste que Valve gère lui-même. Le pseudocode ci-dessous est donné à titre d'illustration et ne correspond pas à l'implémentation de Valve.\n\nforensic_autoban.py\n# PSEUDOCODE À TITRE D'ILLUSTRATION — Valve.block_domain() et flag_session_as_mitm() ne sont pas de véritables appels d'API. Ceci illustre la structure logique d’une mesure d’atténuation Valve pouvant être mise en œuvre contre les domaines d’authentification par proxy, et non le fonctionnement interne réel de Valve.\n# Illustration : schéma logique d'une vérification de la requête OpenID entrante\ndef audit_openid_request(demande) :\nblocked_origins = base de données.get_blacklisted_platforms()\nproxy_domain = request.params.obtenir(« openid.realm »)\ntarget_redirect = request.params.obtenir(« openid.return_to »)\n\n# Logique : si le proxy redirige vers un site bloqué, bloquer le proxy.\npour site dans blocked_origins :\nsi site dans target_redirect :\nValve.block_domain(proxy_domain)\nValve.flag_session_as_mitm(request.session)\n# Résultat : la demande de connexion pour cet hôte a été refusée\n\nRemarque :\nLorsqu’un domaine principal figure déjà dans le filtre de liens (par exemple, howl.gg, bloqué 2026-09-18/19/21) et que son hôte d’authentification (howl.uno) apparaît dans la requête OpenID provenant du bouton de connexion de ce site, l’association est observable par Valve à partir de ses propres données de requête. La vérification peut être automatisée ; son exécution, en revanche, ne l’est pas.\nPrécédents documentés et signalés\n\nValve est intervenu au moins une fois, d'après les informations disponibles, à l'encontre d'un opérateur tiers : en 2018, il a révoqué l'accès d'OPSkins au système ExpressTrade (Annonce de Valve ↗ archivé 2026-03-07 ↗). Des rapports de la communauté datant de 2018 font également état d'une plateforme (SkinJar) ayant perdu son accès ; ces rapports n'ont pas été vérifiés et le mécanisme est déduit du résultat, et non d'un processus rendu public.\n\nCe qu'établit ce précédent :\n\nValve peut bloquer l'accès d'un opérateur tiers quand bon lui semble. CSGOFast, cité dans les articles de presse relatifs aux notifications de juillet 2016, fonctionnait sur 2026-09-21 avec un hôte d'authentification enregistré sous 2026-06-30 qui ne renvoyait aucun blocage via Link Filter. Aucun critère publié n’explique pourquoi un opérateur a été coupé et d’autres non.\n\nCe qu'une date d'immatriculation indique et ce qu'elle n'indique pas\n\nLa date d'enregistrement d'un hôte d'authentification correspond à la date la plus ancienne à laquelle cet hôte aurait pu apparaître pour la première fois dans une requête OpenID ; elle ne prouve pas pour autant une utilisation continue. sc-auth.net, par exemple, a été enregistré sous le numéro 2019-04-02 (RDAP) et a été observé dans le processus de connexion Steam de Skin.Club en septembre 2026 ; ce qui s'est passé entre ces deux dates ne figure pas dans les archives publiques.\n\nAudit comparatif : normes de conformité aux API\nDimension relative à l'application de la loi\tRègles relatives à l'API GitHub\tSteam API Web (Valve)\n1. Neutralité en matière de conformité\tDes règles publiées et uniformes. Des limites de débit documentées (par exemple, 5,000 appels/heure pour les utilisateurs authentifiés, 15,000/heure pour les organisations GitHub Enterprise Cloud) et des politiques d'utilisation acceptable publiées s'appliquent à chaque compte.\tAucun critère n'a été publié. Les comptes individuels sont résiliés en vertu des clauses relatives à l'automatisation et à l'utilisation commerciale (plaintes archivées), tandis qu'aucun relevé des mesures prises par opérateur n'a été publié pour les plateformes commerciales.\n2. Utilisation abusive d'OpenID / du proxy d'authentification\tLes politiques publiées par GitHub permettent de suspendre ou de révoquer les applications et les jetons OAuth en cas d'abus, et sa documentation décrit la révocation automatique des jetons exposés (résumé de la documentation GitHub par les auteurs).\tLes serveurs d'authentification de domaines distincts observés dans Steam flux OpenID (par exemple rbsnin.com, howl.uno, sc-auth.net) n'ont pas été bloqués par le filtre de liens sur 2026-09-21, contrairement à leurs domaines principaux.\n3. Monétisation des abus\tGitHub ne prélève aucun frais de transaction sur les articles transférés via des outils d'automatisation tiers ; son modèle économique repose sur les abonnements et les annonces publiées sur sa place de marché.\tValve vend les clés de coffrets permettant d'obtenir ces objets, et le Marché communautaire prélève des frais combinés d'environ 15% sur les ventes réalisées au sein du Marché. Aucune estimation des revenus attribuables aux plateformes tierces n'est fournie ici.\n4. Durée de vie des boucles d'évasion\tLes identifiants de client OAuth suspendus cessent de fonctionner sur l'ensemble de la plateforme dès leur suspension ; la documentation ne précise pas de délai d'intervention et aucun n'est supposé ici.\tLes hôtes d'authentification de domaines distincts dont les dates d'enregistrement s'étendent de 2011 à septembre 2026 n'ont donné lieu à aucun blocage par le filtre de liens lors des vérifications 2026-09-19 et 2026-09-21. La date d'enregistrement constitue une limite inférieure quant à l'utilisation possible, et non une preuve d'utilisation continue.\nSources : rubrique GitHub — Documentation publiée par GitHub concernant les limites de débit de l'API et la politique de la plateforme (résumé des auteurs, non cité) · rubrique Steam — Vérifications du filtre de liens pour 2026-09-19 et 2026-09-21 (linkfilter-recheck-2026-09-21.json), registre RDAP (domain-registration.json) et les demandes d'assistance archivées (archives des preuves).\nPartie B — Règles et bilan de leur application · Article 13\nL'écart de prix « off-Steam »\n\nL'objet se trouve dans un inventaire « Steam » ; la vente a lieu ailleurs. Un AWP Dragon Lore « Factory New » avait 62 offres en cours sur CSFloat; le prix le plus bas demandé $10,623.95. Sur le marché de Steam, le prix demandé ne peut pas dépasser environ $1,800. Pour vendre à un prix plus élevé que celui observé, un propriétaire doit trouver un acheteur ou une place de marché hors Steam. L'article et son transfert dépendent toujours de Steam.\n\nContexte et limites de la source\n\nCette section présente trois types de comptage différents, qui ne sont pas interchangeables. 245 correspond au nombre de catégories de noms d'articles CS2 dont l'offre active la moins chère dépassait $1,800 sur CSFloat uniquement, le 20 septembre 2026. 241 Il s'agit de cet ensemble, dont on a retiré les quatre catégories épinglées au plafond $100,000 de CSFloat, qui correspond au panneau sur lequel est calculé le plancher $13.63M. 248 Voici un autre aperçu : les catégories dont le prix dépassait le plafond sur au moins deux des cinq places de marché au 23 septembre 2026. Les places de marché se recoupent ; il ne faut donc en aucun cas additionner les chiffres provenant de différentes places de marché. Tous les chiffres présentés ici correspondent à des prix demandés, et non à des ventes conclues ; aucun d’entre eux ne représente de chiffre d’affaires, de volume d’affaires ou de bénéfice — ni pour Valve ni pour quiconque d’autre. Les valeurs indiquées par PriceEmpire sont des estimations arrondies publiées par ce site, et sa carte « Steam » couvre des objets issus d’autres jeux « Steam » ; les périmètres de comparaison ne sont donc pas identiques.\n\nUn article. Deux systèmes de prix.SUIVEZ L'ACTUALITÉ\nÉtape 3 / 3\n\nDans ce cas, le vendeur doit trouver une plateforme ou un acheteur hors Steam. L'article dépend toujours du stock et du système de transfert de Steam.\n\nSTEAMÀ propos de $1,800Plafond publié pour les annonces sur le Marché communautaire\nCATALOGUE ENREGISTRÉ$10,623.95AWP Dragon Lore neuf d'usine : demande de prix\nLA DÉPENDANCEToujours un article SteamLe stock et le transfert restent à Steam\n01 / ARTICLEValve inventaire du jeuObjet de CS2 ou Dota 2 détenu dans Steam\n02 / PLAFONDÀ propos de $1,800 sur SteamPrix maximal pour une annonce sur le Marché\n03 / DEMANDE EXTÉRIEURE$10,623.95 pour « Dragon Lore »L'offre CSFloat la moins chère dans l'instantané daté\n04 / LIVRAISONSteam reste dans la chaîneLa propriété et le transfert des objets dépendent de ce système\nARCHITECTURE DU MARCHÉ · INSTANTANÉ DATÉ, 20 SEPTEMBRE 2026\nL'écart de prix est quantifiable.\n\nNous avons recensé les catégories d'articles dont l'offre active la moins chère était strictement supérieure à1,800.. Les pages CSFloat et Skinport correspondent à des instantanés distincts dont les inventaires CS2 se recoupent ; leurs chiffres ne peuvent donc pas être additionnés. Les offres externes indiquent les sites où des prix de vente plus élevés sont proposés, tandis que Steam continue de gérer la propriété et le transfert des articles.\n\n245CATÉGORIES CS2 · CSFLOAT\n166CATÉGORIES CS2 · SKINPORT\n3CATÉGORIES D'2S SUR DOTA · SKINPORT\n$10,623.95QUESTIONS SUR L'ÉTAGE « DRAGON LORE »\n\nDragon Lore : 62 propose actuellement CSFloat offres dans la catégorie « Factory New » ; le prix affiché correspond à une demande de vente et non à une vente confirmée. Steam autorise la mise en vente de l’article à un prix inférieur, mais ne permet pas de publier une demande de vente supérieure à celle observée. La déclaration de Valve, disponible à l’adresse 2016, confirme que la société a connaissance du fait que des opérateurs de jeux d’argent utilisent OpenID et l’infrastructure commerciale de Steam. Il convient de déterminer séparément si une place de marché tierce spécifique enfreint les règles de Valve.\n\nConsulter le registre complet →CSFloat JSON ↗Skinport JSON ↗Déclaration de Valve sur « 2016 » ↗\nAPI DIRECTE CSFLOAT / INSTANTANÉ DATÉ$13.63M\n\nValeur totale minimale demandée en 241 catégories d'articles et 3,395 offres en cours. Calculé en multipliant le prix de vente le plus bas de chaque catégorie par le nombre d'offres correspondantes. Les quatre catégories plafonnées à $100,000 par CSFloat sont exclues de ce panel prudent.\n\nCe que révèle ce chiffre en dollars\n\nCes offres représentent au moins $13,631,888.25 dans les prix demandés publiés pour ce sous-ensemble limité de CSFloat. En incluant les quatre catégories dont le prix est plafonné, on obtient $14,231,888.25. Il s'agit d'un seuil pour les ordres d'achat actifs, et non pas le chiffre d'affaires réalisé, la trésorerie, les bénéfices ou l'ensemble du marché CS2.\n\nRecalculer à partir de l'instantané CSFloat de 245 lignes ↗\nPRICEEMPIRE / VALEUR INSCRITESteam : n° 15 sur 39\nDe nombreuses salles indiquent une valeur en dollars supérieure à Steam.\nUUSkins\n$133.8M\nYouPin898\n$127.5M\nBuff.163\n$104M\nMoon.Market\n$100.3M\nWhite.Market\n$89.6M\nBuff.Market\n$86.7M\nSteam\n$31M\n\nLes six valeurs les plus élevées affichées et Steam. PriceEmpire arrondit ces chiffres ; Steam indique $31M. Quatorze lieux répertoriés le devancent selon les montants en dollars affichés.\n\nPRICEEMPIRE / NOMBRE D'OFFRESSteam : n° 1 sur 39\nSteam reste en tête en termes de nombre d'offres.\nSteam\n32,2 millions\nYouPin898\n5,9 millions\nC5Game\n4,6 millions\nHaloSkins\n4,4 millions\nSkinport\n3,8 millions\n\nSteam affiche 32,2 millions offres. Le nombre d'offres et la valeur totale des demandes ne répondent pas aux mêmes questions ; de nombreuses annonces à bas prix peuvent faire grimper ce chiffre.\n\nSource : Comparatif public de PriceEmpire ↗ archivé 2026-09-21 ↗, enregistré le 2026-09-20 à 19 h 03 UTC ; extraction datée de 39 lignes ↗. Les chiffres indiqués sont des estimations arrondies, et les stocks peuvent se recouper d'un site à l'autre. La fiche de Steam mentionne également des éléments issus d'autres jeux Steam ; les périmètres ne sont donc pas identiques. Les valeurs indiquées correspondent aux prix demandés, et non aux ventes ou au chiffre d'affaires.\n42\nAUTRE SOURCE / STEAMANALYST\nL'écosystème commercial est sous les yeux de tous.\n\nRépertoire des boutiques de SteamAnalyst archivé 2026-07-19 ↗ répertorie 42 places de marché CS2 tierces aux côtés de Steam, avec des données récentes sur les prix pour 32 des 43 entrées. PriceEmpire répertorie 39 places de marché selon ses propres critères de sélection. Entreprises nommées, offres publiques, prix visibles : cette économie est transparente.\n\nLE PLAFOND EST LE MÉCANISME : LA PROMOTION PREND FIN, MAIS L'ARTICLE RESTE.\n\nSur cinq places de marché représentées dans un instantané sous licence, 248 catégories d'articles CS2 ont un prix fixé indépendamment supérieur au plafond de mise en vente d'environ $1,800 fixé par Steam pour au moins deux d'entre elles — et chacune d'entre elles est absente de Steam. Ce même instantané a classé l’ensemble du catalogue par prix : le marché de Valve propose 95.3% des catégories d’articles situées en dessous de son plafond et 1.9% de celles situées au-dessus. Cette chute ne reflète pas une baisse de la demande ; elle correspond exactement à la règle publiée. La vente à ces prix nécessite un acheteur ou une place de marché externe, tandis que Steam contrôle toujours le stock et le transfert : la transaction quitte la caisse de Valve et la livraison reste sur l’infrastructure de Valve.\n\nSteam FAQ sur le marché ↗archivé 2026-09-21 ↗Steam Contrat d'abonnement ↗archivé 2026-09-21 ↗Ensemble de données « Atlas » portant sur cinq marchés ↗Manifeste de provenance ↗Instantané précédent de CSFloat ↗Aperçu de Skinport ↗PriceEmpire ↗archivé 2026-09-21 ↗SteamAnalyst ↗archivé 2026-07-19 ↗Registre des écarts de prix ↗Atlas des échelles de prix ↗\n\nPartie C — Cadres juridiques\nPartie C — Cadres juridiques · Section 14 · Accès du personnel\nQui peut réinitialiser les mesures de sécurité ?\nContexte et limites de la source\n\nLa sécurité d'un compte dépend également des personnes qui sont en mesure de le récupérer, de consulter ses données privées ou de réinitialiser ses mesures de sécurité. L'enquête doit surveiller ces actions privilégiées avec autant d'attention que les abus d'API.\n\nLa procédure de récupération de compte permet à un agent du service d'assistance de retirer la propriété d'un compte à son titulaire. Valve a confirmé par écrit, à deux reprises — en février 2023 et en novembre 2025 — que ce pouvoir avait été utilisé pour confier des comptes à des personnes non autorisées. À trente-trois mois d'intervalle, par le même canal. Ci-dessous : ce que vaut cet accès, six cas documentés, et le journal Valve qui contient des informations sur chacun d'entre eux et n'a été communiqué à personne.\n\nTémoignage conservé / 9 mai 2025\nUn ticket de récupération qui a désactivé la sécurité du compte, et une perte déclarée de $10,000\n\nUn utilisateur, dans les archives de l'assistance, signale que Steam l'assistance a réinitialisé le mot de passe et désactivé la protection du compte après qu'une autre personne eut soumis une demande de récupération. L'auteur précise que le compte était inactif depuis des années, qu'il contenait des éléments datant de 2016-2017 et qu'il comportait Steam Guard, un numéro de téléphone associé et des codes de récupération enregistrés.\n\n« Steam Le service d'assistance a tout de même permis à quelqu'un d'autre d'accéder à mon compte. »\n\nAllégation à la première personne, conservée dans steam_support_tickets_MEGA.json, enregistrement n° 110. Lire l'intégralité de la publication enregistrée ↗\n\nIl ne s'agit pas d'un simple coup de malchance pour un utilisateur. Cette même procédure — une demande d'aide visant à transférer un compte à la personne qui fournit les données les plus anciennes — est la méthode officielle appliquée dans tous les cas répertoriés dans le registre ci-dessous, et Valve l'a confirmée par écrit à deux reprises.\n\nLe propriétaire n'a aucune chance de gagner ce débat. La procédure de récupération demande la première clé CD, la première adresse e-mail, la première carte bancaire, le premier numéro de téléphone. Ces informations se trouvent dans la base de données de Valve, et le service d’assistance y a accès — on dit que ces données remontent à quinze ans. Une personne qui possède une copie de votre dossier pourra toujours retracer davantage de votre historique que vous ne le pourriez vous-même. Les cibles ont été choisies en fonction de critères précis : inactives depuis des années, de grande valeur, et souvent achetées d’occasion, de sorte que le détenteur n’ait jamais connu la clé d’origine. Par la suite, les comptes ont été purement et simplement supprimés, coupant ainsi la piste de l’historique des objets que la communauté utilise pour retracer l’origine d’un skin — une suppression qu’un utilisateur lambda ne peut effectuer sans respecter la période d’attente standard.\n\nPrincipe du privilège minimal / OWASP A01\n\nLes droits de récupération doivent être limités à la tâche concernée, faire l'objet d'un contrôle indépendant et être consignés. Vérifiez qui est habilité à réinitialiser les identifiants, à supprimer Steam Guard, à consulter les relevés de facturation ou à exporter les données des comptes. Recommandations de l'OWASP en matière de contrôle d'accès ↗ archivé 2026-09-20 ↗\n\nAccès étendu aux services d'assistanceRisque lié à l'étendue des droits d'accès\nAu-delà de l'inventaire.\n\nSi l'accès généralisé est utilisé à mauvais escient, la télémétrie privée peut devenir un outil de profilage, d'hameçonnage ciblé et de surveillance. Parmi les victimes potentielles figurent les utilisateurs lambda, le personnel militaire, les personnalités publiques et leurs familles. Il s'agit là d'un modèle de menace ; les autorisations exactes nécessitent des registres de contrôle d'accès.\n\n01 Historique et localisation de l'adresse IP\nLes journaux d'adresses IP peuvent révéler l'historique de navigation et la localisation approximative. À eux seuls, ils ne permettent pas de déterminer avec précision les déplacements physiques.\n02 Identification par empreinte numérique des appareils\nLes identifiants d'appareil, lorsqu'ils sont collectés et accessibles, permettent d'établir un lien entre les sessions et les comptes.\n03 Télémétrie d'activité\nLes horodatages de connexion et les historiques de session peuvent révéler des habitudes, y compris des activités qui n'apparaissent pas sur un profil public.\n04 Communication et contacts\nL'accès aux messages conservés ou aux coordonnées élargirait les possibilités de profilage et d'ingénierie sociale.\n05 Dévoilement de l'identité\nLes données originales relatives aux e-mails, aux numéros de téléphone et aux paiements permettent d'associer un compte pseudonyme à une personne.\n06 Revente de données et responsabilité\nLes listes de cibles exportées pourraient servir à mener des escroqueries ciblées. Il convient d’identifier l’auteur, le lieu d’accès, les destinataires et les transferts ; le lieu à lui seul ne suffit pas à établir ni l’accès ni l’immunité juridique.\n\nValve décrit la consignation des adresses IP, les informations sur les appareils, les relevés de paiement et les prestataires de services d'assistance tiers dans son Politique de confidentialité, articles 3 et 5.2 archivé 2026-09-21 ↗. Cette politique autorise l'accès de tiers à l'assistance ; toutefois, la piste d'audit qui permettrait de déterminer quel prestataire a accédé à quelle catégorie, à quel moment et en vertu de quelle autorisation n'a pas été divulguée.\n\nSection 14.1 · le registre · juin 2022 → novembre 2025 · toutes les données sont référencées\nValve a ouvert la porte à deux reprises, à trente-trois mois d'intervalle. Elle ne s'est jamais refermée.\n\nSix cas ont été signalés dans lesquels des comptes ont été récupérés via le canal d’aide de Steam lui-même, ou grâce aux identifiants protégés par ce canal. Chaque montant correspond au chiffre publié par la source citée, et chaque source est nommée. Deux des six victimes ont été dédommagées. Ce qui les distinguait des autres, ce n'était pas ce qui s'était passé, mais qui observait la situation.\n\nValve, par écrit — février 2023« Les objets en question ont été retirés de votre compte car ils provenaient d'un compte qui avait été piraté à la suite d'une demande d'assistance, dont l'équipe CS:GO assume l'entière responsabilité. Nous avons annulé les échanges et supprimé ces objets de tous les comptes qui les avaient reçus. »Steam Réponse du service d'assistance à un destinataire des articles de HFB, reproduite par Dexerto, 21 février 2023 ↗ archivé 2025-08-18 ↗\nValve, de nouveau par écrit — novembre 2025 · 33 mois plus tard« Un technicien du service d'assistance chargé de traiter votre demande d'aide n'a pas respecté notre procédure, ce qui a entraîné la réactivation de votre compte au nom d'une autre personne. Je vous présente mes excuses pour cette erreur. »Steam Réponse du service d'assistance à Hawkeye337, citée dans Dexerto, 14 novembre 2025 ↗\n21 juin 2022\nHFB — le plus grand choix de produits du jeu$2,000,000+ · relevé à $3,000,000+ lors du suivi de février 2023\n\nSept objets de collection « Dragon Lores » de l’AWP et le karambit « Blue Gem » n° 1, ce couteau à lui seul étant estimé à environ 1.26 millions de dollars. Le compte était inactif depuis trois ans, mais l'application d'authentification mobile était toujours active ; l'adresse e-mail et le mot de passe ont tout de même été modifiés, via la procédure de récupération proposée par le service d'assistance.\n\nL'argent a disparu avant les objets. Selon certaines informations, $200,000+ Une partie du produit de la vente avait déjà été retirée via market.csgo.com — une place de marché qui effectue les règlements en espèces et en cryptomonnaies. L'annulation d'une transaction permet de récupérer un skin, mais ne restitue pas l'argent déjà encaissé par l'autre partie.\n\nEt la solution a cessé de fonctionner. Un acheteur a déplacé son « Souvenir Dragon Lore » dans un espace de stockage du jeu. Le script de restauration de Valve ne pouvait pas accéder au contenu de son propre conteneur ; il a donc fourni une nouvelle copie au propriétaire tout en laissant l'objet caché en place — Valve a dupliqué un $130,000 objet alors qu’il tentait de faire annuler un vol. Il a été repéré grâce à la comparaison des identifiants d’objets et aux signalements de la communauté, puis supprimé un mois plus tard, en juillet 2022. L’acheteur a été remboursé par BUFF, et non par Valve. Une intervention d’urgence aussi précaire ne constitue pas un mécanisme de contrôle ; c’est ce que fait une plateforme lorsqu’elle n’a aucun contrôle.\n\nDexerto, 21 juin 2022 ↗ archivé 2022-07-02 ↗ · Kaspersky ↗ · montant du retrait par Esportfire, 22 juin 2022 ↗ archivé 2026-05-15 ↗, attribué là-bas à plusieurs sources Twitter · duplication et suppression conformément à Esportsbetting, 14 juillet 2022 ↗\n\nRestauréLes transactions ont été annulées. Les articles ont été retirés des stocks de ceux qui les avaient payés au prix fort.\n14 août 2022\nCS.Money — les bots propres à la plateforme$6,300,000 · 19,000+ skins · première estimation $1.6M\n\nLes pirates ont mis la main sur les fichiers de l'authentificateur mobile des bots de trading de la plateforme et les ont vidés, puis ont envoyé une partie du butin à des traders connus afin de brouiller les pistes. Des chercheurs de la communauté ont retracé 55 comptes d'attaquants en quelques heures et les a publiés.\n\nValve n'a rien changé. La raison invoquée était qu'un site tiers se situait en dehors de Steam — ce même Steam sur lequel le vol s'était déroulé de bout en bout, en exploitant son inventaire, son API commerciale et son système de comptes.\n\nEsportfire, 14 août 2022 ↗ archivé 2025-11-15 ↗\n\nRefuséPas de réversion. La perte est restée à la charge de la plateforme et de ses utilisateurs.\nSignalé\n21 février 2023\nQkss — même porte, même acteur$1,000,000+\n\nIl a été signalé que cette mesure a été prise de la même manière que pour HFB, par le même intervenant, via la même demande d'assistance. HFB avait été entièrement réglé huit mois plus tôt. Ce n'était pas le cas pour Qkss.\n\nUn parcours. Deux réponses. D'après les documents rendus publics, rien ne permet de distinguer ces deux affaires, si ce n'est la taille de l'auditoire.\n\nDexerto, 21 février 2023 ↗ archivé 2025-08-18 ↗\n\nRefuséNon restauré.\nSignalé\nFévrier 2023\nLe délit d'initié en soi — une année de délit d'initié≈ $320,000 · porte sur une période d'environ un an ; il ne s'agit pas d'une évaluation des stocks\n\nL'accès via le service d'assistance a permis de consulter l'historique du compte jusqu'au 15 ans — la première clé CD, le premier e-mail, la première carte. Ce sont précisément les justificatifs exigés dans le cadre de la procédure de récupération, et c’est pourquoi la personne qui détient la base de données l’emporte toujours face à celle qui détient le compte.\n\nLe blogueur Mzkshow a révélé comment l'opérateur « Steam Help » et son complice « Alexander » s'en sont pris à des comptes inactifs contenant plus de $100k de skins. Un M4A4 Howl volé, orné des hologrammes « iBUYPOWER » et « Titan Katowice 2014 », s'est vendu pour $35,000 et s'est retrouvé face à Valerii « b1t » Vakhovskyi, de NAVI, qui n'avait aucun moyen de le savoir. Après l'intervention de Valve, le prestataire a licencié l'ensemble de son service d'assistance Steam.\n\nVKPlay ↗ · Lis-Skins ↗ · Escorenews (RU) ↗ · Dexerto (EN) ↗\n\nPas de registreValve n'a jamais révélé le nombre de comptes concernés, ni informé les personnes concernées.\nSignalé\n2 décembre 2024\n« Matvey » — après les licenciements$13,000\n\nLa récupération a été accordée à une personne qui a fourni des données de compte que le titulaire lui-même n'arrivait pas à faire correspondre. Deux ans après que le prestataire eut fermé son service d'assistance Steam, la même démarche a abouti au même résultat.\n\nMessage archivé, 2 décembre 2024 ↗ archivé 2025-08-05 ↗ · lignes source et hachages ↓\n\nRefuséNon restauré.\n13 novembre 2025\nHawkeye337 (Mark Spurlock) — et la deuxième confession≈ $300,000–$500,000 · Collection complète d'hologrammes de Katowice 2014\n\nL'agresseur a exigé 1 bitcoin et a commencé à transférer la collection sur des disques Negev afin de la détruire. Steam La réponse écrite du service d'assistance correspond à la deuxième reconnaissance mentionnée ci-dessus : un technicien a traité la demande d'assistance, n'a pas respecté la procédure et a confié le compte à quelqu'un d'autre.\n\nC'est le flux qui a permis de résoudre le problème. Quelques heures après la publication sur X des messages taguant Valve, le compte a été réactivé et tous les stickers ont été rétablis. Qkss n'avait pas une telle audience.\n\nSkin.club ↗ · Dexerto ↗ · Esportfire ↗ archivé 2025-12-17 ↗\n\nRestauréLa décision a été annulée quelques heures après que l'article soit devenu viral.\nCe que le registre révèle, contrairement à chaque cas pris individuellement.\n\nLa ligne n'a jamais été fermée. La première admission remonte à février 2023 et la seconde à novembre 2025 — à trente-trois mois d'intervalle, avec le licenciement massif des sous-traitants, une récidive avérée et une faille de sécurité de la plateforme ayant entraîné une perte de $6.3 millions entre-temps. En comptant à partir du premier vol consigné dans ce registre, le canal est resté ouvert pendant trois ans et cinq mois. Quelles qu’aient été les mesures prises en 2023, la demande d’aide a tout de même été transmise à la mauvaise personne en novembre 2025 — selon les propres mots de Valve.\n\nLa restitution tenait compte de l'attention, et non du préjudice. Réintégré : le plus grand inventaire du jeu, et le collectionneur dont le fil de discussion a fait le buzz. Refusé : $1,000,000, $6,300,000, $13,000. Valve n'a jamais publié la règle qu'il applique, car une règle publiée devrait expliquer ces trois-là.\n\nPersonne n'en a été informé. Ni les utilisateurs dont l'historique des comptes a été extrait de la base de données, ni une autorité de contrôle, ni le marché qui a acheté les articles de bonne foi et s'est vu les retirer. Il n'y a pas de notification de violation, pas de rapport d'incident, pas de décompte des comptes concernés — et les recettes conservées sous forme d'argent, par le biais de places de marché qui effectuent des paiements en espèces et en cryptomonnaies. Une annulation de transaction ne peut pas suivre les fonds sortant de Steam.\n\nValve contient la piste d'audit de l'assistance, le journal des tickets de dépannage et l'historique des transactions correspondant à chaque ligne ci-dessus. Aucun de ces éléments n'a été fourni. Demandez votre exemplaire →\n\nLa question de l'accord de confidentialité (NDA)\nLa confidentialité doit aller de pair avec la responsabilité technique.\n\nComparez les accords de confidentialité avec les autorisations effectives, les contrôles à l'exportation, les autorisations de réinitialisation et les journaux d'accès. Une réponse type ne permet pas de réfuter une allégation selon laquelle le processus de récupération lui-même aurait fait l'objet d'un abus.\n\nArticles 28, 32 à 34 du RGPD\n\nL'article 33 accorde au responsable du traitement un délai de 72 heures pour notifier à l'autorité de contrôle toute violation de données à caractère personnel ; l'article 34 impose d'informer les personnes concernées lorsque le risque qu'elles encourent est élevé. Valve a confirmé par écrit, à deux reprises, que son service d’assistance avait transmis des comptes à des personnes non autorisées — historique des comptes, relevés de facturation et tout le reste. Aucune notification au titre de l'un ou l'autre de ces articles n'a été publiée, et aucun utilisateur concerné n'a signalé en avoir reçu une. Consultez le règlement ↗ archivé 2026-09-20 ↗\n\nAjoutez « accès à l'assistance » à votre demande →\nPartie C — Cadres juridiques · Section 15 · Échelle commerciale\nSuivez la trace de l'argent. Séparez les transactions.\nContexte et limites de la source\n\nLa question de l'utilisation à des fins commerciales se pose avec plus d'acuité lorsque les flux financiers sont dissociés. Les transferts de biens à des tiers, les ventes principales de Valve et les retraits de fonds externes constituent des transactions distinctes.\n\nL'article appartient à Valve. Le stock est de Valve. Le transfert s'effectue sur les serveurs de Valve. Seul le paiement s'effectue ailleurs — c'est-à-dire l'étape qui détermine si une personne est considérée comme un opérateur de transfert de fonds, et la seule étape que Valve ne réalise pas.\n\nLe mécanisme de recettes\nLà où l'argent circule réellement.\nTrois voies / une économie fondée sur un seul bien\n01 / CompteInventaire des utilisateurs\n\nArticles en stock : Steam\n\n02 / TransfertCommerce P2P\n\nUtilisateur ↔ bot ou utilisateur ↔ utilisateur\n\n03 / RèglementPlateforme externe\n\nSolde du site ou paiement de Steam\n\nDiffusionLe moteur économique ne se limite pas aux frais de transfert\n\nSteam fournit l’infrastructure de gestion des stocks et de transfert utilisée par les marchés externes. L’argument économique avancé dans le cadre de l’enquête est que la liquidité de la revente et la demande répétée soutiennent les dépenses liées aux coffrets, aux clés et aux articles de remplacement, ainsi que les commissions sur les ventes ultérieures sur le Marché communautaire. Un transfert direct entre particuliers (P2P) n’entraîne aucune commission du Marché communautaire ; ce fait comptable ne permet toutefois pas de trancher la question de l’intérêt général. Valve conserve à tout moment le contrôle de l’accès aux comptes et des restrictions de négociation.\n\n01 / Demande secondaireLiquidité et valeur de revente\n\nDemande extérieure liée au commerce et aux jeux d'argent\n\n02 / Dépenses primairesClés, étuis et capsules\n\nAchats à partir de Valve lorsque cette option est proposée\n\n03 / Chiffre d'affairesRevenus de la vente en première main\n\nPlus les frais liés aux ventes réelles sur le marché\n\n5% + 10%Steam + frais CS2 sur les ventes sur le Marché communautaire\n\nConclusion économique de cette étude : l'existence de marchés de revente liquides peut encourager les dépenses pour l'achat de produits neufs. Le symbole bien connu 15% regroupe les taux des frais de marché, soumis à des montants minimaux et à des arrondis ; il ne s'agit pas d'une taxe prélevée sur chaque transaction commerciale avec l'étranger.\n\nBarème des frais du marché communautaire de Valve ↗ archivé 2026-09-21 ↗. Le 25 février 2026 Le procureur général de New York a intenté une action en justice archivé 2026-09-01 ↗ alléguant que les « loot boxes » payantes sont liées à la revente en argent réel et aux méfaits du jeu — ce même lien que ce dossier met en évidence du point de vue de l’infrastructure technique. Cette plainte est une allégation, et non une conclusion ; elle est citée ici parce qu’un organisme d’application de la loi de l’État a soulevé une question étroitement liée à celle posée par ce dossier : où sont les résultats concrets en matière d’application de la loi qui correspondent aux déclarations publiques ?\n\n01 / EntréeDépôt en cryptomonnaie\n\nEnregistrements relatifs aux services externes et aux portefeuilles\n\n02 / ConversionÉquilibre → apparences\n\nArticles livrés via Steam transactions\n\n03 / SortieVente externe de monnaie fiduciaire\n\nVendeur, acheteur et prestataire de paiement\n\nKYC ?Identifier le responsable à chaque transfert de responsabilité\n\nC'est cette piste qu'il convient d'explorer, et non un service de conversion d'argent via l'API native Steam. Vérifiez les contrôles d'identité, la conservation des fonds, les identifiants de transaction et les destinataires des versements auprès de chaque opérateur externe avant de valider un retrait sans vérification d'identité (no-KYC).\n\nÉtats-Unis / Loi sur le secret bancaire\nClassez d'abord l'activité, puis l'obligation.\n\nLe FinCEN évalue les activités de transfert de fonds en fonction des activités exercées par l’entreprise. L'acceptation et le transfert de monnaie virtuelle convertible peuvent entraîner des obligations en matière de services monétaires, sous réserve des définitions et exceptions applicables. Le portefeuille Steam de Valve accepte des fonds et les convertit en objets de jeu ; ces objets sont ensuite monnayés par des opérateurs tiers contre de la monnaie réelle. L’objet et son transfert s’effectuent sur l’infrastructure de Valve ; ce n’est pas le cas du retrait d’argent, et la question de savoir si une partie quelconque de ce cycle répond aux définitions du transfert de fonds relève d’une classification qui incombe au FinCEN, et non d’une conclusion tirée ici.\n\nFinCEN FIN-2019-G001, §§ 1–2, 5.1 ↗ archivé 2025-07-11 ↗\n\nUnion européenne / blanchiment d'argent\nSuivi des recettes, des connaissances et de l'assistance.\n\nLa directive (UE) 2018/1673 porte sur le blanchiment intentionnel et la participation impliquant des produits du crime. La question qui se pose dans le cadre de l’enquête est de savoir ce que Valve savait au sujet des opérateurs utilisant son infrastructure de trading et OpenID après le 13 juillet 2016, date à laquelle elle a publiquement décrit cette utilisation, et quelles mesures elle a prises à leur égard. Valve n’a publié aucun registre des mesures coercitives par opérateur ; c’est ce registre, et non le présent dossier, qui permettrait de répondre à cette question.\n\nCadre pénal de l'UE ↗\n\nTerminologie de la 6e directive anti-blanchiment (AMLD6) : La directive pénale susmentionnée est distincte de la directive (UE) 2024/1640, également appelée AMLD6. Pour cette dernière, la date limite générale de transposition est fixée au 10 juillet 2027, sous réserve de certaines exceptions. Article 78 ↗ archivé 2026-08-30 ↗\n\nPartie C — Cadres juridiques · Section 16 · Notification, réponse, responsabilité\nLa loi sur les services numériques : consigner les connaissances\nContexte et limites de la source\n\nDeux éléments d'une notification au titre de l'article 16 relèvent de la responsabilité du déclarant plutôt que de ce dossier : les coordonnées du déclarant et une déclaration de bonne foi attestant que les informations sont exactes. Tout ce que l’article exige par ailleurs — l’explication étayée et l’emplacement électronique exact — est précisé dans la section 3 et dans le registre des itinéraires, avec les réponses enregistrées et les hachages, de sorte que n’importe quelle partie puisse le déposer. Deux autres limites s’appliquent à la loi elle-même : la perte de l’exemption relative à l’hébergement n’entraîne pas en soi de responsabilité au titre d’une autre loi, et le montant de 6% prévu à l’article 52, paragraphe 3, constitue un plafond légal, et non une amende fixée à Valve.\n\nEn vertu de la DSA, un hébergeur ne bénéficie de l'immunité de responsabilité que jusqu'à ce qu'il ait connaissance de faits précis et qu'il omette d'agir. Ce dossier constitue cette notification. Il mentionne les hôtes, les dates, les réponses enregistrées et les hachages. Depuis la publication, la question n’est plus de savoir si Valve était au courant, mais ce que Valve a fait ensuite.\n\n01Juillet 2016 / l'exposition « Le dossier »\nUn délai de dix jours.\n\nL'avis reproduit ci-dessus constitue le point de départ historique de la comparaison des mesures d'application menée dans le cadre de l'enquête.\n\n0217 février 2024 / candidature générale\nLa fenêtre temporelle DSA.\n\nIl convient de distinguer les comportements antérieurs de ceux adoptés pendant la période au cours de laquelle les obligations prévues par la DSA s'appliquent.\n\n03Dix ans / instantané du dossier d'origine\nLa durée doit être accompagnée d'un historique des notifications.\n\nLe délai écoulé depuis juillet 2016 (voir section 11) est un indicateur issu du dossier. Il ne s'agit pas de dix années de violations avérées de la DSA. Associez chaque notification à un élément spécifique, à la législation applicable, à une preuve de transmission et à une réponse.\n\nArticle 52, paragraphe 3 / plafond légal6%\ndu chiffre d'affaires annuel mondial\n\nAmende maximale en cas de manquement aux obligations prévues par la DSA, calculée sur la base de l'exercice financier précédent du prestataire. Il s'agit d'un plafond légal et non d'une sanction effectivement infligée à Valve.\n\nArticles 6, 8 et 16 / le critère juridique\n\nEn ce qui concerne les services d'hébergement concernés, la connaissance spécifique du contenu et l'absence d'action rapide peuvent entraîner la perte de l'exonération relative à l'hébergement. Une notification suffisamment précise peut établir la connaissance du contenu en question. La DSA n'impose aucune obligation générale de surveillance ; la perte de l'exonération n'entraîne pas en soi une responsabilité au titre d'une autre loi.\n\nDSA : articles 6, 8, 16, 52, 53, 93 et considérant 17 ↗ archivé 2026-09-20 ↗\n\nConsulter les réclamations archivées ↗Créer la chronologie du compte →Analyse juridique et économique complète →\nPartie C — Cadres juridiques · Section 17 · Identité, âge, accès aux services commerciaux\nMineurs : une connexion avec « Steam » ne constitue pas une vérification de l'âge\nContexte et limites de la source\n\nAucune donnée relative à un mineur n'apparaît dans ce dossier et aucune n'a été collectée : les auteurs ne se sont pas inscrits, n'ont rien déposé ni effectué de connexion sur aucune des plateformes citées. Toute personne s'appuyant sur cette section doit préserver la confidentialité des éléments de preuve concernant un enfant et expurger les détails permettant de l'identifier des pièces à conviction rendues publiques. La loi COPPA est citée ici en tant que loi sur la protection de la vie privée des enfants, avec ses propres conditions d’application — public visé, connaissance effective, données à caractère personnel collectées — et non comme une règle générale relative à l’âge légal pour les jeux d’argent ; la plainte déposée à New York en 2026 est une allégation émanant d’une autorité publique, et non une conclusion.\n\n« Se connecter avec Steam » permet de vérifier l'existence d'un compte. Cela ne prouve rien quant à l'âge — et sur ces sites, c’est le seul obstacle entre un enfant et un dépôt. Lisez-le avec Section 3.1: au sein du client Steam, l'avertissement qu'un navigateur afficherait ne s'affiche jamais, de sorte que l'enfant ne le voit jamais.\n\nCe qu'offre OpenID SteamIdentité du compte\n\nUn SteamID vérifié, utilisé pour se connecter ou associer un compte.\n\n≠\nCe que l'opérateur doit établirConditions d'éligibilité pour participer\n\nÂge, juridiction compétente et vérifications d'identité éventuellement requises.\n\nFondements techniques : Documentation Steamworks OpenID ↗ archivé 2026-09-21 ↗. La vérification d'identité consignée ne constitue pas une attestation selon laquelle l'utilisateur est légalement autorisé à jouer.\n\nCOPPA / enfants de moins de 13 ans\nIdentifiez l'opérateur et les données.\n\nLa loi COPPA s'applique aux services destinés aux enfants qui relèvent de son champ d'application, ainsi qu'aux services ayant la connaissance effective qu'ils collectent des données à caractère personnel auprès d'enfants de moins de 13 ans. Il s'agit d'une loi relative à la protection de la vie privée des enfants, et non d'une règle générale concernant l'âge légal pour jouer à des jeux d'argent. Il convient de définir le public cible, les données à caractère personnel collectées, la connaissance de ces faits et la procédure d'obtention du consentement parental.\n\nFTC : Exigences de la loi COPPA ↗ archivé 2026-09-21 ↗\n\nLes éléments de preuve à conserver\nEnregistrez le parcours, de la connexion au versement.\n\nConserver les critères d'âge d'accès au site, le libellé des conditions d'inscription, les conditions d'éligibilité, le processus de paiement et l'historique des plaintes. Évaluer chaque opérateur séparément. Préserver la confidentialité de tout élément de preuve concernant un enfant et masquer les informations permettant de l'identifier dans les pièces versées au dossier public.\n\nUn autre registre public relatif à l'application de la loi est celui de Annonce d'une plainte à New York en 2026 archivé 2026-09-01 ↗, qui fait état de préjudices subis par de jeunes utilisateurs du fait des « loot boxes » payantes. Il ne s’agit pas d’une conclusion au titre de la COPPA.\n\nPartie C — Cadres juridiques · Section 18 · Demande au titre de l'article 15 du RGPD\nLa demande. La réponse. La comparaison qui manque.\n\nIl a demandé quatre choses, dont le fichier journal permettant d'identifier la personne qui avait ajouté une clé API à son compte. Trois jours plus tard, le ticket a été clôturé avec un lien vers une page qui ne contient aucune de ces informations. — et la phrase qui conclut ce texte est contredite par les propres avocats de Valve.\n\nÀ qui appartient ce compte ? · Provenance et limites\n\nCes captures d'écran ne sont pas celles de PhishDestroy. Ces informations proviennent d’un simple titulaire de compte Steam — un participant à une brève enquête menée dans le cadre de ce projet — qui a lui-même déposé la demande et fourni les captures d’écran. Le compte est le sien, le ticket est le sien, et la correspondance s'est déroulée entre lui et le service d'assistance Steam. Ce projet n'a pas soumis la demande, ne détient aucun compte sur la plateforme et n'est pas partie prenante dans ce ticket.\n\nLe 16 septembre 2026, il a déposé une demande d’accès aux données personnelles en vertu de l’article 15 du RGPD/CCPA, demandant spécifiquement les journaux d’enregistrement des clés API, l’historique des connexions avec les adresses IP, l’historique des autorisations des appareils et l’historique des transactions. Le 17 septembre, l’agent « Logen » l’a redirigé vers la page en libre-service « Données du compte ». Le 18 septembre, il a indiqué que les catégories demandées ne figuraient pas sur cette page et a demandé que sa demande soit transmise à l’équipe chargée de la protection de la vie privée ou au délégué à la protection des données (DPO). Le 19 septembre, l’agent « Kal » a clôturé le ticket en lui fournissant la même réponse. Les deux captures d’écran sont conservées ci-dessous (l’adresse e-mail du demandeur a été masquée ; SHA-256 dans steam_tos_assets/screenshot-manifest.json).\n\nC'est une personne tout à fait indiquée pour formuler cette demande, et ce pour une raison toute simple : Son compte est associé à une clé API Web Steam qu'il n'a pas créée, enregistrée auprès de localhost. On ignore quand elle a été créée. — ni pour lui, ni à partir de quoi que ce soit que Valve ait mis à sa disposition, car le seul document permettant de la dater est le journal d’enregistrement des clés API, qui correspond précisément à la catégorie que la société a refusé de divulguer. Cette clé n’est pas récente : elle est antérieure au moment où il en a pris connaissance, d’une durée qu’il ne peut pas évaluer, pour la même raison.\n\nD'autres titulaires de compte ont déposé la même demande. Toute réponse reçue sera ajoutée ici selon les mêmes modalités que pour ces deux demandes — numéro de ticket, date de capture, SHA-256, identité du demandeur masquée —, qu'elle accorde ou refuse l'accès aux catégories demandées.\n\nCe projet ne se prononce pas sur les raisons pour lesquelles le ticket a été clôturé. Aucune raison n'y était mentionnée, et aucune n'est supposée ici.\n\nLa demande. La réponse. La comparaison.SUIVEZ L'ACTUALITÉ\nÉtape 3 / 3\n\nIl a demandé quatre catégories précises. La page « Données du compte » vers laquelle il a été redirigé correspond à l’exportation en libre-service de Valve lui-même, et ce projet ne peut pas énumérer son contenu pour le compte d’une autre personne — c’est pourquoi aucune comparaison complète, catégorie par catégorie, n’est publiée ici. Ce qui figure dans le dossier, c’est sa déclaration du 18 septembre indiquant que les catégories n’y figuraient pas, ainsi que la clôture du dossier du 19 septembre qui réitérait le renvoi sans aborder ces catégories.\n\nLA DEMANDECatégories spécifiquesClé API, identifiants de connexion, appareils et enregistrements de transactions\nLA RÉPONSERéférence des données du compteVérifier l'échange de support\nLE TESTQu'est-ce qui a été fourni ?Comparer chaque catégorie demandée\nÉcran 1/2 — Demande (16 septembre) et première réponse de l'agent « Logen » (17 septembre)\nGDPR ticket HT-2YBP-F7JP-D4VB — request and first response\nSource : help.steampowered.com, ticket HT-2YBP-F7JP-D4VB · capturé les 16 et 17 septembre 2026 · adresse e-mail du demandeur masquée 2026-09-21 · Fichier : gdpr-ticket-1.png · SHA-256 da940c731ab9869d226e9d06ccc8a1b393738766b7b0c445a56662623e025a66 (screenshot-manifest.json).\nÉcran 2/2 — Demande de recourir à un niveau supérieur (18 septembre) et clôture, agent « Kal » (19 septembre)\nGDPR ticket HT-2YBP-F7JP-D4VB — escalation request and closure\nSource : help.steampowered.com, ticket HT-2YBP-F7JP-D4VB · capturé les 18 et 19 septembre 2026 · Fichier : gdpr-ticket-2.png · SHA-256 44844ea7b251f7fd7d79f87ee1578a846606a97b9659d3a53b322120c422219b (screenshot-manifest.json).\nRéponse finale, 19 septembre (transcription intégrale) :\n« Les données Steam conservées sont déjà disponibles sur la page « Données de votre compte ». Le service d'assistance ne pouvant vous fournir aucune autre information Steam, Cette demande sera classée.«\nAucune donnée fournie · aucune base juridique justifiant le refus n'a été indiquée · aucun résultat de l'escalade n'est indiqué\nCette affirmation est fausse, et ce sont les propres avocats de Valve qui le prouvent. La lettre de l'avocat du 1er octobre 2025, au paragraphe 1.9, décrit une corrélation au niveau des appareils reliant un appareil à des dizaines de comptes (Annexe A). Cette même réponse comprenait 830 pages de documents conservés (Annexe B). Aucune de ces informations ne figure sur la page « Données du compte ».\nPourquoi ce compte a-t-il demandé le journal des clés API ?\n\nIl n'a pas choisi ces quatre catégories au hasard. Le localhost La clé de son compte est la marque d'un script, et non celle d'une personne saisissant un véritable nom de domaine dans la page de développement (Section 5, Section 6). Le seul document indiquant qui l'a créé et d'où il provient est le journal d'enregistrement des clés API. C'est la première chose qu'il a demandée. C'est ce que la partie défenderesse a refusé de communiquer.\n\nSource : le titulaire du compte, lors de l'enquête menée dans le cadre de ce projet. Les captures d'écran des tickets ci-dessus ont été hachées ; la page contenant la clé n'est pas publiée.\n\nÉvaluation · PhishDestroy\n\nLe fait de clore un ticket alors que la question reste en suspens n'est pas un hasard dans ce contexte. C'est le dénouement normal. Nous considérons que 16,319 dossiers de réclamations et de prise en charge conservés et 354 échanges d'assistance après déduplication tirés de ces sources. Ce billet en est un exemple daté et très complet illustrant la forme qu’ils prennent.\n\nTicket d'assistance — ConservéHT-2YBP-F7JP-D4VB\nType de demandeArticle 15 du RGPD (demande d'accès aux données)\nStatut du billetFERMÉ LE 19 SEPT. 2026 — AUCUNE DONNÉE FOURNIE\nAgents de la bourse« Logen » (17 septembre), « Kal » (19 septembre)\nClassé16 septembre 2026\nDonnées demandéesQui a enregistré la clé API Web associée à ce compte, et depuis quelle adresse IP / quel appareil / à quelle date et heure ?\nBase juridique invoquéeArticle 15 du RGPD — droit d'accès aux données à caractère personnel\nLe cadre juridique :L'article 12, paragraphe 3, accorde au responsable du traitement un délai d'un mois à compter de la réception (prolongeable sur motivation). Ce délai n'était pas encore écoulé au moment de la publication, et le présent dossier ne fait pas état d'un dépassement de délai. L’objection porte sur le fond : la réponse finale renvoie à une page en libre-service, mais ne démontre pas que les quatre catégories de données mentionnées ont été fournies ; or, si le responsable du traitement refuse de donner suite, l’article 12, paragraphe 4, lui impose d’en exposer les motifs et d’indiquer les voies de recours. Aucun de ces éléments ne figure dans la réponse finale.\nPourquoi ces données précises sont-elles importantes ?\n\nLe journal des événements liés aux clés API Web est le registre qui indique si un tiers a enregistré une clé à l'aide d'un cookie de session volé — le mécanisme décrit dans les plaintes pour vol d'inventaire conservées dans les archives de ce dossier. Révéler l'identité de la personne ayant enregistré une clé API, l'adresse IP d'où provient l'enregistrement et l'horodatage de celui-ci permettrait :\n\nPermettre à la victime de comparer l'adresse IP utilisée pour la création de l'API avec son propre historique de connexion\nRévéler les adresses IP des centres de données liées à des infrastructures connues de hameçonnage ou de bots de jeux d'argent\nFournir des éléments de preuve pouvant être utilisés dans le cadre d'une procédure civile ou pénale à l'encontre de l'auteur des faits\nIndiquer si le titulaire du compte a été informé lors de la création de la clé\nCe qui ressort du dossier : Valve conserve des enregistrements relatifs aux appareils et aux corrélations entre comptes — la lettre de son avocat du 1er octobre 2025 les décrit (voir annexe A, Mémoire de preuve — Source 1). Dans le dossier HT-2YBP-F7JP-D4VB, la même catégorie de données a été demandée par la personne concernée et le dossier a été clôturé par un renvoi vers une page en libre-service qui, selon la personne concernée, ne contenait pas ces données. La légalité de ce refus relève de la compétence de l’autorité de contrôle ; en l’occurrence, la personne concernée n’obtient pas les informations demandées.\nL'échange — quatre messages en trois jours\n\nDeux agents du service d'assistance Steam ont répondu en utilisant les prénoms indiqués sur le ticket : « Logen » le 17 septembre et « Kal » le 19 septembre. Tous deux ont renvoyé le demandeur vers la page « Données du compte ». Rien dans le ticket n’indique si la demande a été transmise à l’équipe chargée de la confidentialité ou au délégué à la protection des données de Valve, et le dossier ne précise pas qui sont ces agents, quels sont leurs rôles ni comment le ticket a été acheminé.\n\n16 septembre\nDemande au titre de l'article 15 portant sur quatre catégories de données désignées\n17-18 septembre\nRéférence aux données du compte ; le demandeur sollicite une intervention du délégué à la protection des données\n19 SEPT.\nDossier clôturé avec la même référence ; aucune donnée, aucun fondement indiqué\nQuels sont les droits que l'article 15 du RGPD reconnaît explicitement à la personne concernée ?\nArt. 15, paragraphe 1, point a)Finalités du traitement — pourquoi Valve conserve ces données\nArt. 15, paragraphe 1, point b)Catégories de données — ce que contient Valve\nArt. 15, paragraphe 1, point c)Destinataires ou catégories de destinataires — qui a reçu les données (par exemple, le détenteur de la clé API)\nArt. 15, paragraphe 1, point d)Durée de conservation ou critères permettant de la déterminer\nArt. 15, paragraphe 3Une copie des données à caractère personnel faisant l'objet du traitement — c'est-à-dire le journal des clés API lui-même\nART. 12, paragraphe 3Réponse attendue dans un délai de un mois à compter de la réception ; toute prolongation doit être notifiée au cours de ce mois. Le délai n’était pas encore écoulé au moment de la publication. Art. 12, paragraphe 4 : Si le responsable du traitement ne donne pas suite, il doit en indiquer les raisons et informer la personne concernée des voies de recours.\nProcédure de réclamation auprès des autorités de régulation — pour tout utilisateur\n\nTout utilisateur ayant adressé une demande au titre de l’article 15 du RGPD à Valve et n’ayant reçu aucune réponse conforme (ou un refus type ne contenant aucune donnée) peut déposer une réclamation auprès de l’autorité de contrôle de son État membre de l’UE/EEE. L'établissement européen de Valve est Valve GmbH à Hambourg ; l'autorité de contrôle chef de file pour les plaintes transfrontalières est donc la Commissaire à la protection des données et à la liberté d'information de Hambourg (HmbBfDI). (Le représentant désigné au titre de l'article 27 de Valve est également établi à Hambourg ; l'adresse d'un représentant ne détermine pas à elle seule l'autorité compétente.) Une plainte peut également être déposée auprès de l'autorité de l'État membre dont relève le plaignant, en vertu de l'article 77.\n\nFormulaire de réclamation HmbBfDI ↗ Texte du RGPD (articles 12, 15 et 77) ↗ archivé 2026-09-20 ↗Lignes directrices du CEPD ↗\n\nRéférence du dossier pour toute réclamation : HT-2YBP-F7JP-D4VB — conservé dans ce dossier à titre d'exemple documenté.\n\nUn cas avéré\nCes documents existent ; la personne concernée ne les a pas reçus.\n\nL'avocat de Valve a décrit les enregistrements de corrélation au niveau des appareils dans une lettre datée du 1er octobre 2025. Le 19 septembre 2026, une demande au titre de l’article 15 portant sur la même catégorie de documents a été classée sans suite par renvoi vers une page en libre-service qui, selon le demandeur, ne contenait pas les informations demandées, et ce sans fondement juridique précisé. Le ticket HT-2YBP-F7JP-D4VB constitue un exemple documenté ; la question de savoir s’il reflète une pratique plus générale relève de l’autorité de contrôle, qui peut demander à Valve ses registres de traitement.\n\nArticles 12, 15 et 77 du RGPD / Autorité de contrôle\n\nUne réclamation au titre des articles 12 et 15 peut être déposée directement auprès de l'autorité de contrôle compétente, sans frais (article 77). L'autorité peut imposer des mesures correctives, notamment des injonctions de se conformer à la demande d'accès, ainsi que des amendes en vertu de l'article 83, paragraphe 5, point b), en cas de violation des droits des personnes concernées. La conservation de la référence du billet d'origine et de toute réponse Valve (ou de son absence) renforce le bien-fondé d'une réclamation.\n\nConsultez le modèle de DSAR →\nPartie C — Cadres juridiques · Section 19 · Droit des contrats\nLe contrat d'abonnement par rapport à l'architecture propre à la plateforme\nContexte et limites de la source\n\nLes auteurs ne sont pas juristes et le présent texte ne constitue en aucun cas un avis juridique. La SSA est citée dans sa version révisée du 10 septembre 2026 ; une autre version peut présenter des différences, et la numérotation des articles a évolué d'une version à l'autre — il convient de vérifier l'article en se référant à la version qui régissait le comportement en question. Les arguments relatifs aux articles 25 et 32 énoncent ce qu’exige la réglementation, et non le fait qu’une autorité de contrôle ait constaté une infraction. Les chiffres mentionnés dans l’argument n° 1 reprennent les limites de champ d’application définies à l’article 13.\n\nTrois des dispositions centrales de la SSA sont en contradiction avec la conception même de la plateforme : l’interdiction d’utilisation commerciale associée à un plafond de prix sur le « Market », qui pousse les ventes de grande valeur hors de la plateforme ; la clause de responsabilité de l’utilisateur relative aux clés API, qui s’oppose à un point de terminaison de clé n’exigeant, avant 2023, aucune authentification à deux facteurs ; et les dispositions relatives à l’application de la loi, qui s’opposent à un registre public ne faisant état d’aucune mesure coercitive par opérateur. Il appartiendra à un tribunal de déterminer si ces tensions affectent l’applicabilité de la loi ; la présente section expose les faits qui seraient soumis à l’appréciation d’un tribunal.\n\nArgument n° 1 / Architecture de la capitalisation boursière\nLe plafond du marché et l'interdiction d'utilisation à des fins commerciales\n\nLe marché communautaire Steam a un plafond de mise en vente d'environ $1,800. Sur cinq places de marché, selon un instantané daté du 23 septembre 2026, 248 catégories d'articles CS2 affichent, sur au moins deux de ces places de marché, un prix supérieur à ce plafond ; ces articles ne peuvent pas être vendus à ces prix sur la propre plateforme de Valve. Les propriétaires qui souhaitent bénéficier de ces tarifs ont recours à des marchés tiers, qui fonctionnent avec des comptes « Steam » et l’API « Steam » — une utilisation que la SSA considère comme commerciale, sauf autorisation expresse.\n\nLes articles dépassent le plafond du Marché → des marchés tiers comblent ce manque → ces marchés utilisent des comptes Steam et l’API Steam → la SSA interdit toute utilisation commerciale sans autorisation → aucun registre des autorisations n’a été publié. Les frais combinés du Marché communautaire, d’environ 15%, s’appliquent uniquement aux ventes réalisées au sein du Marché, et non à ces transactions externes.\nArgument n° 2 / Architecture de sécurité des clés API\nLa vulnérabilité liée à la clé API relève davantage d'un problème de conception de la plateforme que d'une négligence de la part des utilisateurs\n\nAvant 2023, le point de terminaison de création de clés API de Steam acceptait une requête POST contenant un identifiant de session volé et générait des identifiants dotés de privilèges élevés. sans confirmation par e-mail, sans authentification à deux facteurs ni vérification par appareil. Les signalements de détournement d'API recueillis dans le cadre de cette enquête suivent tous le même schéma : script de l'attaquant, cookie de session volé, création silencieuse d'une clé, interception d'une transaction (le contenu de la requête est présenté à la section 8).\n\nL’article 25 du RGPD (protection des données dès la conception) et l’article 32 (sécurité du traitement) exigent la mise en œuvre de mesures techniques adaptées au risque. La délivrance d’un identifiant susceptible d’être intercepté lors d’une transaction sans authentification à deux facteurs ni notification au titulaire relève d’un choix de conception incombant au responsable du traitement. La question de savoir si la clause du SSA attribuant la responsabilité à l’utilisateur peut être invoquée dans ce contexte relève de la compétence d’un tribunal et de l’autorité de contrôle.\n\nArgument n° 3 / Visibilité en temps réel\nValve reçoit le nom d'hôte d'authentification à chaque connexion\n\nLe nom d'hôte d'authentification parvient au point de terminaison OpenID de Valve en texte clair dans openid.return_to et openid.realm (la structure de la requête est présentée à la section 3). Son extraction est une opération standard. À la date de 2026-09-22, sur 26 paires, le domaine principal figurait dans le filtre de liens (Link Filter), contrairement à l’hôte hébergeant son identifiant Steam. Valve n’ayant publié aucun rapport sur les mesures d’application par opérateur, il n’est pas possible, à partir des données publiques, de déterminer si une mesure autre que le filtre de liaison a été appliquée à ces hôtes.\n\nQui prend en charge les frais ?\nLa tendance qui se dégage des plaintes archivées\n\nDans les plaintes examinées, la réponse du service d'assistance Steam à une plainte concernant le détournement d'une clé API suit toujours le même schéma : refus de la restauration, mise en avant de la responsabilité de l'utilisateur vis-à-vis de son compte et de sa clé API, puis clôture du ticket. Ce dossier ne contient aucune estimation du nombre total de comptes concernés ni du montant des pertes subies ; aucune source permettant d'établir ces chiffres n'a pu être identifiée.\n\nLa question n'est pas de savoir si certains utilisateurs ont commis des erreurs. La question est de savoir qui est responsable d'une architecture qui, jusqu'en 2023, permettait à une requête POST utilisant un cookie volé de créer un identifiant de trading doté de privilèges élevés, sans notification ni authentification à deux facteurs.\nLa SSA en tant que document vs la SSA en tant que contrat\nUn tribunal chargé d'examiner ce dossier ne se contenterait pas d'interpréter la SSA de manière isolée.\n\nIl faudrait le lire en parallèle de la lettre de l'avocat datée d'octobre 2025, qui décrit la corrélation au niveau des appareils, les dates d'enregistrement des hôtes d'authentification, les horodatages d'enregistrement des lots, le contenu de la requête de clé API, ainsi que les dix années écoulées entre les notifications de juillet 2016 et les plateformes encore en service en septembre 2026. C'est sur ce dossier que Valve devrait se pencher.\n\nSSA par rapport au dossier / points clés\n« Aucune utilisation commerciale » — le plafond fixé par le Marché pousse les ventes de grande valeur vers des marchés commerciaux tiers\n« Les utilisateurs sont responsables de leurs clés API » — pas d'authentification à deux facteurs sur le point de terminaison des clés avant 2023\n« Nous prenons des mesures à l'encontre des contrevenants » — aucun relevé des sanctions par opérateur n'a été publié depuis juillet 2016\n« Vous avez accepté les conditions » — dans le scénario de détournement, l'acceptation est envoyée par un script, et non par le titulaire du compte\nConclusion · Ce que le dossier établit et ce que nous demandons\nLes conclusions. Les documents que nous demandons.\nContexte et limites de la source\n\nChacune des conclusions ci-dessous est liée à un document public daté figurant dans les sections précédentes. Les demandes sont adressées aux autorités habilitées à obtenir ce que cette enquête ne peut pas obtenir : les propres registres de Valve concernant l'application de la loi, l'accès aux données et leur traitement.\n\nChaque demande fait suite à une conclusion datée. Les autorités peuvent demander des documents que cette enquête menée à partir de sources publiques ne peut pas exiger.\n\nCe que les documents publics établissent\n44 plateformes actives s'authentifient via un domaine distinct pouvant faire l'objet d'un enregistrement — 27 d'entre elles disposent d'un fichier de preuves publié pour chaque route, tandis que les 17 autres proviennent d'une collecte manuelle et sont répertoriées séparément. Au 2026-09-22, 26 paires avaient leur domaine principal bloqué dans le filtre de liens Steam, alors que l’hébergeur hébergeant leur page de connexion ne l’était pas — csgogem.com bloqué, api.csgem.com enregistré depuis mars 2014. Steam reçoit ce nom d'hôte dans openid.realm et openid.return_to à chaque connexion. Section 3\nLe 13 juillet 2016, Valve a officiellement désigné ce mécanisme et l'a interdit, et les notifications de son avocat du 20 juillet 2016 ont fixé un délai de dix jours. Aucun relevé des mesures coercitives par opérateur n'a été publié au cours des dix années qui ont suivi l'expiration de ce délai. Article 11\nLe point de terminaison de la clé API Web Steam délivrait, avant 2023, un identifiant doté de privilèges élevés et permettant d'effectuer des transactions à partir d'un simple cookie de session, sans authentification à deux facteurs. Section 5\nUne demande au titre de l'article 15 du RGPD (dossier HT-2YBP-F7JP-D4VB) a été clôturée au bout de trois jours avec un lien vers le portail en libre-service, sans aucune donnée fournie. Article 18\nCe que nous demandons à chaque autorité\nCommission des jeux de l'État de Washington\nRouvrez le dossier de 2016. Demandez un relevé, opérateur par opérateur, indiquant quels comptes, bots et hôtes de retour ont été désactivés à l'issue des préavis de dix jours, et quels opérateurs ont par la suite récupéré leur accès. Section 2\nHmbBfDI (Hambourg ; Valve GmbH)\nVérifier si la réponse fournie au titre de l'article 15 a respecté l'obligation qui incombe au responsable du traitement, et exiger la communication des registres d'enregistrement et d'accès à la clé API permettant d'identifier l'auteur de l'infraction. Article 18\nCoordinateurs des services numériques (DSA)\nIndiquez le routage « auth-host » dans l’enregistrement en tant que remarque, puis vérifiez si la réponse de Valve répond à ses obligations une fois les informations consignées. Article 16\nToute personne concernée\nUtilisez le modèle prévu à l'article 15 pour demander ces mêmes données pour votre propre compte ; les données conservées permettent de déterminer qui a lancé une réinitialisation ou créé une clé. Annexe G\n\nLa seule demande qui sous-tend ces quatre cas est la même : publier les registres relatifs à l’application de la loi, à l’accès et au traitement des données, dont seul Valve dispose. Un avertissement sur la page d’accueil, une lettre de mise en demeure de dix jours et une page en libre-service constituent autant de manifestations de contrôle. La question de savoir si ce contrôle a été exercé ne trouve pas de réponse dans les documents publics, mais peut être tranchée par une autorité de régulation.\n\nAnnexes — pièces à conviction principales et documents de travail\nAnnexe A — Correspondance avec les avocats\nNote relative aux éléments de preuve — documents fournis par la source n° 1\n\nFondement factuel et nature des sources des correspondances avec l'avocat invoquées aux sections 1, 18 et 19.\n\nFondement factuel et statut de la source — documents fournis par la source n° 1\nL'utilisateur dont l'exclusion définitive a déclenché cet audit n'en fait pas l'objet. La question de savoir si cette exclusion était justifiée n'est pas examinée ici, et ce dossier ne la défend ni ne la conteste. Le compte n'est pas le sujet. Ce qui importe, ce sont les éléments suivants : Source 1 — Le titulaire du compte suspendu, qui a reçu la correspondance ci-dessous de la part de l’avocat de Valve en tant que personne concernée par sa propre demande au titre du RGPD, a transmis cette correspondance et les dossiers y afférents, en accordant le droit de les consulter publiquement. Son nom n’est pas divulgué ; les documents sont répertoriés par date, métadonnées de l’auteur et hachage.\n\nCette correspondance a été envoyée en réponse à une demande au titre du RGPD/DSAR. Dans ce cadre, l'avocat de Valve a versé au dossier une déclaration signée décrivant une fonctionnalité que le service d'assistance de Steam avait auparavant présentée aux utilisateurs comme techniquement impossible. Le paragraphe cité ci-dessous correspond à cette déclaration.\n\nL'analyse plus approfondie par les auteurs de l'extrait de journal généré est la suivante : omise dans ce dossier dans l'attente d'un examen indépendant. Aucun autre élément de cette enquête ne s'appuie sur cet élément.\n\nLa reconnaissance officielle : la télémétrie persistante au niveau des appareils\n\nAu paragraphe 1.9 de la lettre attribuée à l'avocat de Valve, les avocats de Valve indiquent : « Entre 2019 et 2023, ce compte a principalement été utilisé depuis un appareil qui a également servi à se connecter à des dizaines de comptes Steam piratés. »\n\nLa réalité : Valve L'avocat décrit ici une corrélation au niveau des appareils entre différents comptes sur une période de quatre ans. Steam Le service d'assistance a indiqué aux victimes de vol qu'il n'était techniquement pas possible de localiser les objets volés ni d'associer des comptes à des appareils. Steam Guard L’autorisation des appareils est documentée publiquement ; l’existence d’enregistrements par appareil n’est donc pas en soi une nouveauté ; ce qui est nouveau, c’est la confirmation écrite de l’avocat selon laquelle ces enregistrements sont conservés et mis en corrélation entre les comptes sur des périodes de plusieurs années.\n\nPourquoi est-ce important ? : La corrélation permettant de relier un appareil à des dizaines de comptes piratés sur une période de quatre ans relève de la même catégorie de données que celle que le service d’assistance a déclaré ne pas pouvoir mettre à la disposition des victimes. Les données de cette catégorie permettraient d’identifier les comptes et les appareils impliqués dans une chaîne de vol et de revente. Quelles sont les données existantes, pendant combien de temps elles sont conservées et sur quelle base elles sont soustraites à la connaissance des personnes concernées : telles sont les questions qui s’adressent à l’autorité de contrôle.\n\nSource : lettre de l'avocat de Valve datée du 1er octobre 2025, paragraphe 1.9, et son annexe au format PDF de 830 pages · reçue par la Source 1 en réponse à une demande au titre de l'article 15 du RGPD · la valeur SHA-256 de l'annexe enregistrée dans disclosure-audit.json · La lettre elle-même n'est pas reproduite ; les noms des comptes et les données provenant de tiers ont été omis.\n\nStatut : ouvrir\nLes documents sources sont disponibles dans les archives des données probantes.\nAnnexe B — Le fichier PDF généré · vérification de la caviardage\nLa caviardage dans le fichier PDF fourni est purement esthétique : le texte masqué reste extractible\n\nL'avocat de Valve a répondu à une demande d'accès au titre du RGPD en joignant une annexe de 830 pages dans laquelle les passages caviardés sont masqués par une couche de peinture plutôt que supprimés. 902,270 caractères se trouvent sous les barres noires et apparaissent directement grâce à un outil d'extraction de texte — y compris les identifiants tiers que les barres étaient censées masquer. Seuls les chiffres agrégés sont publiés ici ; aucun contenu protégé n'est reproduit, et l'annexe elle-même n'est pas publiée.\n\n1. Résultats de la vérification géométrique\n\nRéponse au titre de l'article 15 du RGPD en date du 1er octobre 2025 était accompagné d'une annexe au format PDF de 830 pages (métadonnées du créateur Aspose.PDF pour .NET, créées et modifiées à la même date). Les auteurs ont effectué une vérification géométrique au niveau de chaque page : pour chaque page, ils ont repéré les rectangles opaques, presque noirs, superposés au calque de texte, puis ont compté les caractères extractibles situés en dessous.\n\nMesuré sur le fichier généré\n902,270\nDes caractères peuvent encore être extraits de sous les barres noires\nChiffre compté, et non estimé. Il s’agit du nombre de personnages concernés — et non du nombre de victimes, de cas de réidentification ou d’incidents.\n830 / 830\nPages concernées — toutes les pages\n986\nDes rectangles recouvrant du texte extractible\n1,329\nNombre total de rectangles noirs opaques\nLes barres noires sont superposées au calque de texte ; elles ne le suppriment pas. Le texte situé sous les barres peut être extrait à l'aide d'outils PDF courants. Seuls les chiffres globaux sont publiés ; aucun contenu masqué n'est reproduit ici.\nDémonstration médico-légale : séparation des couches\nMAQUETTE DE SUPERPOSITION VECTORIELLE D'ASPOSE.PDF POUR .NET (ANNEXE, p. 412)\n\nPlainte déposée à l'encontre du compte : [IDENTIFIANT : redacted_user_667]\n\nMotif fourni par l'utilisateur : [TEXTE : « Un utilisateur signale la présence d'articles en double dans son inventaire et des pratiques commerciales abusives... »]\n\nPremier plan : <path fill=\"#000\" />Vulnérabilité : le flux UTF-8 sous-jacent reste intact\nSource : annexe au format PDF de la lettre de l'avocat du 1er octobre 2025 (830 pages, métadonnées du créateur fournies par Aspose.PDF pour .NET) · calcul effectué par les auteurs, méthode et nombre de pages dans disclosure-audit.json · La valeur SHA-256 de l'annexe est enregistrée dans le même fichier · L'annexe elle-même n'est pas publiée.\n2. En quoi cela est-il important pour la réponse apportée à une personne concernée ?\n\nL'avocat de Valve a transmis ce dossier à une personne concernée en réponse à une demande visant à obtenir ses propres données. Ces barres sont purement esthétiques : le texte situé en dessous n'a jamais été supprimé ; par conséquent, les identifiants tiers que ces barres étaient censées masquer ont été transmis au destinataire en même temps que le fichier. Une caviardage qui peut être supprimé à l'aide d'un outil d'extraction de texte ne masque rien et empêche en outre le destinataire de déterminer ce qui a été divulgué et ce qui ne l'a pas été.\n\nC’est l’article 15, paragraphe 4, qui justifie l’existence même de ces caviates : le droit d’obtenir une copie ne doit pas porter atteinte aux droits et libertés d’autrui. C’est à cette obligation que cette production n’a pas satisfait. C’est à l’autorité de contrôle qu’il appartient de déterminer s’il s’agit d’une violation de données à caractère personnel au sens de l’article 4, paragraphe 12 ; la divulgation elle-même est mesurable dans le fichier et reproductible par toute personne disposant des mêmes octets — la valeur SHA-256 est publiée, contrairement à l’annexe.\n\nCe qui se trouvait sous les barres n'était pas des numéros de compte. Il s'agissait de l'ensemble des signalements d'utilisateurs déposés à l'encontre du demandeur, accompagnés du nom de leurs auteurs : Steam identifiants qui, comme un identifiant est rarement utilisé uniquement sur Steam, permettent d'identifier la personne qui se cache derrière eux — Selon les auteurs, plus de 60% des utilisateurs cités dans le document sont parfaitement identifiables — ainsi que le texte brut, non expurgé, de ce qu’ils ont écrit. Ce texte contient des menaces de mort et des propos injurieux à l’encontre de la nationalité du demandeur. Certaines des personnes ainsi identifiées sont mineures. La production a remis une liste nominative de journalistes à la personne qu'elle avait dénoncée., ce qui correspond précisément au préjudice que l'article 15, paragraphe 4, vise à prévenir.\n\nL'ordre des caractères dans le fichier est tout aussi important que son contenu. La demande a d’abord donné lieu à une exigence de preuves d’identité supplémentaires, au motif que l’adresse e-mail d’alias du demandeur ne contenait pas son nom ; le compte a été définitivement suspendu pendant le délai qui a suivi. La lettre qui a finalement permis de transmettre les données, plus de six semaines après l’expiration du délai d’un mois prévu à l’article 12, paragraphe 3, menaçait le destinataire de poursuites pénales et retenait le reste de ses propres données jusqu’à ce qu’il explique l’activité de son compte à son avocat. Cette divulgation apporte également une réponse à deux questions auxquelles Valve n’avait pas répondu publiquement : les documents fournis montrent que les liens entre comptes remontent à 2019, et la télémétrie interne atteint un niveau de détail que Valve n’a jamais décrit.\n\nChamp d'application de cette section : La présente analyse se limite aux aspects techniques de la rédaction, tels qu’ils ressortent du dossier tel qu’il a été produit. L’analyse plus approfondie des journaux de bord fournis, réalisée par les auteurs, n’est pas divulguée dans l’attente d’un examen indépendant et n’est pas prise en compte ailleurs dans ce dossier.\n\nPièce à conviction : lettre de l'avocat du 1er octobre 2025 et son annexe au format PDF (SHA-256 enregistré dans le dossier d'audit) ; Mesures et méthode au niveau de la page dans un fichier PDF ↗. Le déroulement de la demande, le refus mentionné à la page 8 et la description des documents divulgués sont exposés en détail dans le récit de PhishDestroy, « Mon chien contre les avocats d'élite spécialisés dans le RGPD », 17 août 2026 ↗ archivé 2026-08-21 ↗. Les noms de comptes et les données provenant de tiers ont été omis ici ; aucune information masquée par les barres n'est reproduite.\n\nÀ la page 8 de la lettre d'accompagnement, une partie de la demande est rejetée, et le motif est exposé par écrit : Il n'est pas possible de fournir des informations plus précises en raison de la protection des données à caractère personnel des autres utilisateurs de la plateforme Steam… — Il n’est pas possible de donner une réponse plus détaillée, car les données à caractère personnel des autres utilisateurs Steam doivent être protégées. L’annexe de 830 pages figurait dans le même dossier. Ce que masquaient les barres n’était pas des numéros de compte : il s’agissait des signalements déposés à l’encontre du demandeur, avec le nom de leurs auteurs et les messages bruts non expurgés en pièce jointe. Le titulaire du compte avait demandé à Valve, par l’intermédiaire de son avocat, son propre dossier ; ce qu’il a pu en extraire concernait d’autres personnes. Rien dans cette annexe ne porte sur l’identité de la personne ayant tracé ces encadrés. Ce qu’elle établit, c’est que la protection Valve invoquée pour justifier la non-divulgation est précisément celle que cette même communication n’a pas respectée, dans la même enveloppe, le même jour.\nPièces relatives à l'assistance et à la correspondance juridique\n\nSource: https://phishdestroy.io/steam_dossier/fr/index#exhibit-gallery-section\n\nAnnexe D — Collecte des sources\nDocuments sources sélectionnés\n\nSix éléments issus des archives : trois tickets GitHub dans les trackers de Valve et trois comptes Reddit relatant des cas de support controversés. Chaque source est associée à l'allégation, au texte enregistré et à la question qu'elle soulève.\n\n1 / 6 enregistrements sélectionnés\nChoisissez un enregistrement source\nGH-01 / GITHUBOuvrir dans la version enregistrée\nClés matérielles, demandées en 2016\n\nValveSoftware / steam-for-linux · n° 4521 · 2016-06-27\n\nUn utilisateur a demandé à Valve de prendre en charge les clés matérielles U2F comme deuxième facteur d'authentification alternatif. Le ticket enregistré porte à la fois les étiquettes « Demande de fonctionnalité » et « Révisé », et son statut est indiqué comme « ouvert ».\n\nJe demande que Steam prenne en charge les clés USB U2F comme alternative.\n\nExtrait de la ticket GitHub ↗\nDossier documenté\nUne demande datée visant à mettre en place une mesure de sécurité supplémentaire pour le compte, publiée dans le système de suivi des incidents de Valve et marquée comme « examinée ».\nExigence de responsabilité\nPublier la décision relative au produit, la date de réponse et la protection accordée à l'issue de l'examen.\nLire l'enregistrement sauvegardé →Ouvrir GitHub ↗\nDans le dossier : Mesures de sécurité du compte →Archive n° 484 · version 2026-09-17\nGH-02 / GITHUBOuvrir dans la version enregistrée\nRapports d'erreurs sans possibilité effective de se désinscrire\n\nValveSoftware / steam-for-linux · n° 6459 · 2019-08-18\n\nLe contributeur décrit un problème rencontré par un client « Steam » le 12 août 2019 sous Ubuntu 16. Il indique que la désactivation de la destination « crash-upload » n'a pas été conservée après un redémarrage, et fournit la configuration correspondante.\n\nSi je désactive le paramètre `ServerURL`, celui-ci est réinitialisé à chaque redémarrage.\n\nExtrait de la ticket GitHub ↗ archivé 2026-04-19 ↗\nDossier documenté\nUne plainte spécifique relative à la confidentialité, accompagnée de la date de connexion du client, du système d'exploitation et d'un extrait de la configuration. Le ticket enregistré est en cours de traitement.\nExigence de responsabilité\nIdentifiez l'enquête, les versions concernées et la modification qui a rendu l'option de désinscription effective.\nLire l'enregistrement sauvegardé →Ouvrir GitHub ↗archivé 2026-04-19 ↗\nDans le dossier : Demander les documents sources →Archive n° 467 · version 2026-09-17\nGH-03 / GITHUBOuvrir dans la version enregistrée\nAbus de tickets d'authentification signalé à Valve\n\nValveSoftware / Source-1-Games · n° 3857 · 2022-02-26\n\nL'auteur affirme qu'un opérateur de serveur a conservé Steam tickets d'authentification après la déconnexion des joueurs et a utilisé des listes de serveurs trompeuses. Le message demande à Valve de réagir face à ce comportement.\n\nDonner l'impression que leurs serveurs sont pleins à craquer.\n\nExtrait de la ticket GitHub ↗\nDossier documenté\nUn signalement d'abus public a été déposé dans le tracker de Valve le 26 février 2022. Son état enregistré est « ouvert » ; le signalement comprend des liens vers des captures d'écran.\nExigence de responsabilité\nFournir les conclusions de l'enquête et le compte rendu des mesures correctives mises en œuvre concernant l'utilisation abusive du ticket d'authentification qui a été signalée.\nLire l'enregistrement sauvegardé →Ouvrir GitHub ↗\nDans le dossier : Portée de l'ensemble de données →Archive n° 768 · version 2026-09-17\nRD-01 / REDDITProfil de l'auteur\n44 achats contestés sur le marché\n\nr/DotA2 · pseudonyme de l'auteur non divulgué · 2022-07-07\n\nL'auteur fait état de 44 achats non autorisés effectués sur le Market le 6 juillet 2022 et de pertes s'élevant à environ $500+. Il précise que l'authentification à deux facteurs était activée et décrit les réponses types répétées envoyées par le service d'assistance.\n\nC'est déjà mon deuxième ticket, et je n'ai toujours pas reçu de réponse de Steam qui ne soit pas un simple copier-coller standardisé.\n\nExtrait du message publié sur Reddit ↗ archivé 2025-03-20 ↗\nDossier documenté\nUn compte rendu daté d'achats contestés, accompagné de liens vers des captures d'écran des transactions et d'une réponse du service client. Les montants et les faits sont rapportés par l'auteur.\nExigence de responsabilité\nVérifiez les achats contestés à l'aide des journaux de transactions et de session. Expliquez les éléments qui ont motivé la décision du service d'assistance.\nLire l'enregistrement sauvegardé →Ouvrir Reddit ↗archivé 2025-03-20 ↗\nDans le dossier : Aide et application de la loi →Archive n° 4,533 · version 2026-09-17\nRD-02 / REDDITProfil de l'auteur\nUne exclusion définitive et des recours irrecevables\n\nr/ohnePixel · pseudonyme de l'auteur non divulgué · 2024-12-09\n\nL'auteur conteste cette exclusion définitive et affirme que la modération s'est appuyée sur des soupçons de transfert de compte et des signalements de la communauté. Il évoque des tickets fermés et son intention de demander l'accès à ses données personnelles.\n\nJ'ai expliqué ma situation et demandé plus de précisions, mais ils campent sur leur décision et clôturent mes tickets.\n\nExtrait du message publié sur Reddit ↗\nDossier documenté\nUn compte rendu d'appel conservé, comprenant les motifs invoqués par l'auteur à l'appui de sa demande ainsi que des liens vers quatre images. La date de publication provient de l'exportation des pièces justificatives sélectionnées.\nExigence de responsabilité\nIdentifiez les éléments justifiant la suspension définitive ainsi que les voies de recours disponibles pour la contester. Le fait de classer un recours sans suite ne constitue pas une explication de la décision.\nLire l'enregistrement sauvegardé →Ouvrir Reddit ↗\nDans le dossier : Demander les documents sources →Archive n° 1 · version 0\nRD-03 / REDDITProfil de l'auteur\nUne remise à zéro de la reprise et une perte déclarée de $10,000\n\nr/legaladvice · pseudonyme de l'auteur non divulgué · 2025-05-09\n\nL'auteur affirme que le service d'assistance a réinitialisé ses identifiants et désactivé les mesures de protection de son compte après qu'une autre personne eut envoyé une demande de récupération. Il signale une perte d'environ 0,01 dollar américain provenant d'un compte inactif.\n\nSteam Le service d'assistance a réinitialisé mon mot de passe et désactivé toutes les mesures de sécurité de mon compte.\n\nExtrait du message publié sur Reddit ↗\nDossier documenté\nUne allégation conservée selon laquelle le processus de récupération aurait contourné les mesures de sécurité du compte. Le message enregistré rapporte ce que, selon l'auteur, le service d'assistance lui aurait dit.\nExigence de responsabilité\nIdentifiez la personne qui a autorisé la réinitialisation, les justificatifs de propriété qu'elle a acceptés et le journal d'accès. La récupération de compte fait partie des contrôles Valve du système de sécurité.\nLire l'enregistrement sauvegardé →Ouvrir Reddit ↗\nDans le dossier : Demander les documents sources →Archive n° 4,592 · version 2026-09-17\n\nSix enregistrements sélectionnés. Les descriptions GitHub détaillent la version enregistrée. Les publications Reddit conservent les témoignages des auteurs.\n\nTéléchargez les six morceaux ↓\n\nLa version consultable contient 16,319 enregistrements distincts: 393 entrées sur Trustpilot, 5,635 sur Reddit, 2,395 sur GitHub, 276 entrées sur le Web et 7,620 sur le wiki. Plusieurs entrées peuvent concerner un même événement. Le fichier d'exportation principal, composé de 40,448 lignes distinctes, a une portée différente.\n\nRechercher dans l'intégralité des archives ↗ · Créer un manifeste ↗ · Portée et nombre d'enregistrements →\n\nAnnexe E — Étude de cas\nArchiSteamFarm et la clause d'automatisation\n\nUn outil open source de « farming » de cartes dont la FAQ indique qu'il fonctionne sur des millions de comptes, ce qui va à l'encontre de la clause du contrat d'abonnement (§ 4.C) interdisant l'automatisation. Les mécanismes — ce qu’une ferme doit acheter auprès de Valve avant de pouvoir produire quoi que ce soit, pourquoi chaque méthode de retrait d’argent d’une carte constitue une violation de la licence, le bilan des mesures prises et qui modère l’économie des cartes — sont exposés en détail dans Annexe V ↗.\n\nLe contrat d’abonnement Steam, § 4.C, stipule :\n\n« Il est interdit d'utiliser, de quelque manière que ce soit, des scripts, des bots, des macros ou tout autre système non contrôlé par un être humain (« automatisation ») pour interagir avec le Contenu et les Services sur Steam. » — Steam Contrat d'abonnement, § 4.C (version en vigueur) ↗ archivé 2026-09-18 ↗\n\nValve veille au respect de cette clause. Il s'en acquitte très bien. La FAQ de ArchiSteamFarm (ASF) — un outil open source dont la documentation indique qu’il fonctionne sur plus de quelques millions de comptes Steam depuis sa première version il y a plus de 11 ans — reproduit trois Steam messages du service d'assistance annonçant l'exclusion définitive d'utilisateurs qui exploitaient des réseaux de bots. Valve a identifié ces réseaux, les a nommés et les a démantelés. La question qui se pose n'est donc pas de savoir si Valve est capable de détecter l'automatisation à grande échelle.\n\nLe site officiel du projet ArchiSteamFarm FAQ aborde directement le risque d'une interdiction :\n\n« Cela semble extrêmement improbable, étant donné que l’ASF est utilisé sur plusieurs millions de comptes Steam depuis sa première version, sortie il y a plus de 11 ans — mais cela reste une possibilité, quelle que soit la probabilité réelle. »\n\n« Valve reconnaît clairement l’existence des « Steam fainéants », comme indiqué ici ; donc, si tu me demandes mon avis, je suis presque sûr que s’ils ne les acceptaient pas, ils auraient déjà pris des mesures au lieu de simplement souligner qu’ils pourraient poser des problèmes du point de vue VAC. » Le mot-clé ici, ce sont les « idlers » Steam, comme ASF par exemple, et non les « game idlers ».«\n\n— ArchiSteamFarm FAQ, JustArchiNET. Source : wiki GitHub ↗ · vérifié mot pour mot 2026-09-22\n\nDans cette même FAQ, la question « Est-ce que quelqu’un s’est fait bannir pour ça ? » reçoit la réponse suivante : Oui, et reproduit ce que Steam Support a écrit à trois d'entre eux :\n\n1,000+ bots · interdiction de transaction\n« Il semblerait que ce compte ait été utilisé pour gérer un réseau de comptes de bots. L'utilisation de bots constitue une violation du Contrat d'abonnement Steam. »\n\nPlus de 170 bots · bannis définitivement, soldes d'hiver 2017\n« Ce compte a été utilisé pour collecter illégalement des cartes à collectionner sur Steam, ainsi que pour mener des activités connexes, qui ne se limitaient pas au domaine commercial. Le compte a été définitivement bloqué et le service d'assistance Steam ne peut pas fournir d'aide supplémentaire à ce sujet. »\n\nPlus de 120 bots · bannis définitivement\n« Ce compte, ainsi que d’autres, ont été utilisés pour saturer notre infrastructure réseau, ce qui constitue une violation des règles de conduite en ligne Steam. »\n\n— Steam Messages d'assistance reproduits dans la ArchiSteamFarm FAQ, section « Quelqu'un s'est-il déjà fait bannir pour ça ? ». Source ↗ · vérifié mot pour mot 2026-09-22\n\nPlacez les deux disques côte à côte. Un utilisateur privé disposant de 1,000 bots d’exploitation est identifié, informé que « l’utilisation de bots constitue une violation du Steam Contrat d’abonnement », puis banni définitivement. Les plateformes commerciales mentionnées dans ce dossier ont pour activité principale la gestion de comptes automatisés Steam, à une échelle bien plus grande, et s’authentifient via l’OpenID propre à Valve à chaque connexion — or, aucun rapport sur les mesures de contrôle par opérateur n’a été publié pour aucune d’entre elles. Cette clause est valable. La question est de savoir à qui elle s'adresse.\n\nL'ASF n'est ici accusée de rien, et son interprétation de la position de Valve n'engage qu'elle-même — son auteur affirme clairement que « l'ASF n'est pas autorisée par Valve ». Cet outil est utilisé ici comme un instrument de mesure : il montre que Valve détecte les réseaux de bots, les identifie par écrit et les bannit définitivement. Valve pourrait clore le débat en une seule phrase en publiant la liste des automatisations commerciales qu’il autorise, ainsi que le relevé, opérateur par opérateur, des mesures qu’il a prises concernant les autres.\n\nL'impact du « card farming » sur le chiffre d'affaires de Valve\n\nLes cartes à collectionner obtenues en jeu sont vendues sur le Marché communautaire Steam, qui prélève des frais combinés d'environ 15% sur chaque vente conclue au sein du Marché ; le compte doit avoir dépensé $5.00 USD sur Steam avant de pouvoir recevoir la moindre carte ; et l’obtention de cartes nécessite de posséder le jeu ou d’effectuer des achats dans le jeu. Aucun chiffre global de chiffre d’affaires n’est estimé ici — l’ampleur des activités est indiquée uniquement telle qu’elle est présentée dans la FAQ de l’ASF. La FAQ mentionne également Valve éléments distinctifs « Steam roues folles » (collecte de cartes) à partir de « les joueurs qui ne font rien »; voir le FAQ sur la PPA ↗. Les modalités sont décrites en détail dans Annexe V — le barème et le piège de l'utilisation commerciale.\n\nObjetArchiSteamFarm — obtention automatisée de cartes\nÉchelle indiquéeDes millions de comptes (selon la FAQ de l'ASF — le nombre exact de comptes actifs n'a pas été vérifié)\nComptés, et non cités10,880,610 entrées API au total dans le Steam groupe propre à l'ASF (5,360,499 sans restriction, comme l'indique Steam) — le chiffre de « millions » mentionné dans la FAQ ne correspond pas à un récit, mais à un décompte. 88.97% ne comportent aucune Steam interdiction d’aucune sorte. Le recensement complet des interdictions ↗\nInformations figurant dans la documentation de l'outil lui-même\nASF se connecte en mode sans interface graphique et laisse les jeux en veille pour obtenir des cartes sans lancer le client Steam (conformément à la documentation du projet).\nLa FAQ explique que Valve est au courant de l'existence des « Steam fainéants » et que « s'ils ne les acceptaient pas, ils auraient déjà réagi ».\nAucune mesure de contrôle ciblée n'a été signalée depuis plus de 11 ans (selon la FAQ) ; les ventes de cartes qui en résultent au sein du Community Market génèrent des frais cumulés d'environ 15% pour Steam.\nLa FAQ indique un plafond recommandé de dix comptes par opérateur et l'attribue à Valve : « Cette recommandation repose sur des directives internes Valve, ainsi que sur nos propres suggestions. » Aucune directive de ce type n'est publiée par Valve.\nLimite technique, selon cette même FAQ : « Vous pouvez faire fonctionner jusqu'à 100 à 200 bots avec une seule adresse IP et une seule instance ASF. »\nLe temps de jeu « farmé » est enregistré par Valve — « il est généralement mis à jour toutes les 30 minutes environ » — et le § 4.C mentionne la « falsification des statistiques de jeu (par exemple, gonflement du nombre de victoires ou de défaites, des points d'expérience ou du temps de jeu) » comme un acte interdit.\nSources\nWiki officiel des questions fréquentes (FAQ) de JustArchi ASF ↗ ArchiSteamFarm dépôt ↗ archivé 2026-09-24 ↗\nLa clause relative à l'automatisation est explicite ; la FAQ de l'ASF précise depuis des années que l'outil est utilisé sur des millions de comptes ; aucune mesure coercitive ciblée à son encontre n'a été signalée. L'écart entre la règle et son application est avéré ; la raison de cet écart n'est pas établie ici.\nExposition complèteL'économie des cartes : le fonctionnement, l'ampleur, la licence et qui la réglemente ↗Ce qu'une ferme doit acheter auprès de Valve avant de pouvoir produire une seule carte ; les deux lignes du § 4.C qui définissent la « culture de cartes » par ses effets ; pourquoi toute méthode d’encaissement d’une carte constitue une violation de la licence Valve, alors que Valve prélève des frais à l’entrée ; le bilan des mesures de contrôle, y compris la vague de juin 2025 VAC et l’interdiction en chaîne par numéro de téléphone partagé ; et les employés Valve et modérateurs communautaires chargés de gérer les services d’échange de cartes et de liste noire autour de Steam.Le recensement des interdictionsNous n'avons pas demandé à Valve quelle était la superficie de la ferme. Nous l'avons mesurée. ↗10,880,610 comptes au total (limités et non limités) lus à partir du groupe Steam propre à ArchiSteamFarm, auquel le logiciel adhère automatiquement par défaut lors du premier lancement, à moins que l'utilisateur ne désactive le paramètre d'adhésion au groupe (ce qui inclut à la fois les fermes de bots commerciales et les joueurs réguliers ayant conservé le paramètre par défaut). 88.97% ne font l’objet d’aucune Steam interdiction d’aucune sorte ; parmi les 11% qui en font l’objet, 99.8% sont des interdictions communautaires purement symboliques qui n’empêchent en rien la poursuite des échanges. Après recoupement avec les données de SteamRep, 67.77% des escrocs répertoriés sont remis en liberté une fois les interdictions anti-triche levées. Avec des ventilations par date d’inscription, zone géographique et durée de survie — l’ampleur réelle, mesurée, et non pas simplement décrite.\n\nAppendix F — Working ledger\n\nRules ledger: clauses against recorded platforms\n\nChoisissez une règle ; le registre affiche la liste des plateformes enregistrées associées à cette règle, avec leur domaine principal, l'hôte d'authentification déclaré et le résultat du filtre de liens enregistré. Un site web bloqué, un autre domaine pour la connexion : suivez la règle jusqu'à la route restante.\n\n175enregistrements liés\nà cette règle\n174 domaines principaux0 Mentions « C&D »\nEXTRAIT DE LA RÈGLE / SSA § 2.G\nUtilisation commerciale et facturation du compte\n“…exploit the Content and Services or any of its parts for any commercial purpose, except as expressly permitted elsewhere in this Agreement (including any Subscription Terms or Rules of Use).”\nSUIVEZ LES RÉSULTATS\nRegistre de la plateforme 175\nLes chiffres indiqués sont des estimations provenant de sources diverses.\n\n175 des dossiers d'175\n\nService / groupe parent\tDomaine principal / registre\tDomaine d'authentification observé / âge\tÉchelle / réponse enregistrée\n\nCasino\n\tcsgoempire.com\n11.3 yearsRegistered 2015-06-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgoempirelogin4.com\n6.2 yearsRegistered 2020-07-20\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustreaper.com\n23.2 yearsRegistered 2003-06-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustreaper.com\n23.2 yearsRegistered 2003-06-24\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustly.com\n12.4 yearsRegistered 2014-05-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustly.com\n12.4 yearsRegistered 2014-05-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette Casino\n\tcsgofast.com\n11.5 yearsRegistered 2015-03-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsteam-login.authtofast.com\n83 daysRegistered 2026-06-30\nRDAP ↗ · authtofast.com (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tduelbits.com\n6.6 yearsRegistered 2020-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nswitchflips.com\n6.4 yearsRegistered 2020-04-21\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opener\n\tfarmskins.com\n10.5 yearsRegistered 2016-03-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsteam.kobal.cc\n9.7 yearsRegistered 2017-01-07\nRDAP ↗ · kobal.cc (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgoluck.com\n9.3 yearsRegistered 2017-05-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgoluck.com\n9.3 yearsRegistered 2017-05-18\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tinsane.gg\n7.5 yearsRegistered 2019-04-02\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.insane.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcs2skin.com\n3.5 yearsRegistered 2023-03-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncs2skin.com\n3.5 yearsRegistered 2023-03-06\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tjuice.gg\n7.9 yearsRegistered 2018-10-19\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nletmeinjuice.com\n2.4 yearsRegistered 2024-04-15\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tggdrop.com\n8.6 yearsRegistered 2018-02-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nggauth.com\n3.4 yearsRegistered 2023-05-03\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Casino\n\thowl.gg\n9.5 yearsRegistered 2017-03-16\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhowl.uno\n41 daysRegistered 2026-08-11\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tchicken.gg\n5.7 yearsRegistered 2021-01-11\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nchicken.gg\n5.7 yearsRegistered 2021-01-11\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgocasino.gg\n2.6 yearsRegistered 2024-02-17\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.csgocasino.gg\n2.6 yearsRegistered 2024-02-17\nWHOISFREAKS ↗ · csgocasino.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Casino\n\thunt.gg\n6.9 yearsRegistered 2019-11-04\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.hunt.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Battles\n\tcsbattle.com\n9.8 yearsRegistered 2016-12-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsbattle.com\n9.8 yearsRegistered 2016-12-10\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskinrave.gg\n3.1 yearsRegistered 2023-08-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinrave.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsdouble.gg\n261 daysRegistered 2026-01-03\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsdouble.gg\n261 daysRegistered 2026-01-03\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustchance.com\n8.0 yearsRegistered 2018-10-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhgfuihd.com\n7.6 yearsRegistered 2019-01-27\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Automation\n\tcobaltlab.tech\n3.5 yearsRegistered 2023-03-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncobaltauth.com\n1.7 yearsRegistered 2025-01-07\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\traided.gg\n171 daysRegistered 2026-04-03\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.raided.gg\n171 daysRegistered 2026-04-03\nIP2WHOIS ↗ · raided.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustneo.gg\n1.3 yearsRegistered 2025-06-20\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustneo.gg\n1.3 yearsRegistered 2025-06-20\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tsplits.gg\n3.7 yearsRegistered 2023-01-23\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsplits.gg\n3.7 yearsRegistered 2023-01-23\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Upgrader\n\tupgrader.pro\n1.2 yearsRegistered 2025-07-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nupgauth.space\n38 daysRegistered 2026-08-14\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskin.fans\n8.2 yearsRegistered 2018-07-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skinfans.com\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\thotpizza.one\n1.8 yearsRegistered 2024-12-07\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhotpizza.one\n1.8 yearsRegistered 2024-12-07\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tg4skins.com\n10.1 yearsRegistered 2016-08-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.g4s.to\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2royal.com\n4.1 yearsRegistered 2022-08-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ntf2auth.com\n5.2 yearsRegistered 2021-07-27\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2hunt.com\n8.7 yearsRegistered 2018-01-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrstspcl.com\n6.1 yearsRegistered 2020-08-08\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2.bet/coinflip\n8.4 yearsRegistered 2018-05-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ntf2.bet\n8.4 yearsRegistered 2018-05-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\topenstars.gg\n131 daysRegistered 2026-05-13\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nopenstars.gg\n131 daysRegistered 2026-05-13\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tskins.com\n25.1 yearsRegistered 2001-08-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skins.com\n25.1 yearsRegistered 2001-08-08\nRDAP ↗ · skins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\twhite.market\n9.6 yearsRegistered 2017-03-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwhite.market\n9.6 yearsRegistered 2017-03-01\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tmoon.market\n7.6 yearsRegistered 2019-02-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmoon.market\n7.6 yearsRegistered 2019-02-27\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tcsfloat.com\n5.2 yearsRegistered 2021-07-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgofloat.com\n11.0 yearsRegistered 2015-09-29\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tskin.land\n4.7 yearsRegistered 2022-01-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skin.land\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\thaloskins.com\n2.8 yearsRegistered 2023-12-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhaloskins.com\n2.8 yearsRegistered 2023-12-10\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCorporate Market\n\tbuff.163.com\n29.0 yearsRegistered 1997-09-15\nRDAP ↗ · 163.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\nbuff.163.com\n29.0 yearsRegistered 1997-09-15\nRDAP ↗ · 163.com (parent)\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\tmarket.csgo.com\n26.6 yearsRegistered 2000-02-07\nRDAP ↗ · csgo.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\ndota2.net\n14.9 yearsRegistered 2011-10-29\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRegulated Market\n\tskinport.com\n8.0 yearsRegistered 2018-09-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinport.app\n6.3 yearsRegistered 2020-06-20\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMarketplace/Swap\n\tskinflow.gg\n3.8 yearsRegistered 2022-11-26\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinflow.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tskin.place\n6.0 yearsRegistered 2020-09-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skin.place\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tskinsmonkey.com\n5.7 yearsRegistered 2021-01-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinsmonkey.com\n5.7 yearsRegistered 2021-01-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCorporate Market\n\tskinbaron.de\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinbaron.com\n10.7 yearsRegistered 2015-12-22\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Market\n\trust.tm\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\ndota2.net\n14.9 yearsRegistered 2011-10-29\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tpirateswap.com\n6.0 yearsRegistered 2020-09-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nlogin.pirateswap.com\n6.0 yearsRegistered 2020-09-22\nRDAP ↗ · pirateswap.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Marketplace\n\tmannco.store\n8.6 yearsRegistered 2018-03-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmannco.store\n8.6 yearsRegistered 2018-03-02\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tskinswap.com\n9.9 yearsRegistered 2016-11-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinswap.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\texeskins.com\n2.1 yearsRegistered 2024-08-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nexeskins.com\n2.1 yearsRegistered 2024-08-14\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tbalticskins.com\n153 daysRegistered 2026-04-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nbalticskins.com\n153 daysRegistered 2026-04-21\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tcs.trade\n8.9 yearsRegistered 2017-11-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncs.trade\n8.9 yearsRegistered 2017-11-14\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\trapidskins.com\n4.5 yearsRegistered 2022-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.rapidskins.com\n4.5 yearsRegistered 2022-03-11\nRDAP ↗ · rapidskins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\ttradeit.gg\n9.1 yearsRegistered 2017-08-21\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nconnect-tradeit.com\n4.6 yearsRegistered 2022-02-23\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\t49skins.com\n3.4 yearsRegistered 2023-04-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.49skins.com\n3.4 yearsRegistered 2023-04-19\nRDAP ↗ · 49skins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tskinvault.gg\n3.4 yearsRegistered 2023-05-06\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinvault.gg\n3.4 yearsRegistered 2023-05-06\nIP2WHOIS ↗ · skinvault.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Trading\n\taim.market\n3.3 yearsRegistered 2023-05-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\naim.market\n3.3 yearsRegistered 2023-05-22\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Sell Portal\n\tskinout.gg\n5.6 yearsRegistered 2021-02-27\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skinout.gg\n5.6 yearsRegistered 2021-02-27\nIP2WHOIS ↗ · skinout.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Trading\n\tntskins.com\n230 daysRegistered 2026-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nntskins.com\n230 daysRegistered 2026-02-03\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Portal\n\tgamerpay.gg\n6.0 yearsRegistered 2020-10-02\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ngamerpay.gg\n6.0 yearsRegistered 2020-10-02\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Scrap Swap\n\tscrap.tf\n14.0 yearsRegistered 2012-09-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nscrap.tf\n14.0 yearsRegistered 2012-09-03\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Cashout\n\tmarketplace.tf\n14.0 yearsRegistered 2012-09-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmarketplace.tf\n14.0 yearsRegistered 2012-09-19\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Cashout\n\tskins.cash\n10.5 yearsRegistered 2016-03-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinscash.live\n6.8 yearsRegistered 2019-12-05\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgo.net\n14.2 yearsRegistered 2012-07-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncn2.easylot.net\n10.0 yearsRegistered 2016-09-03\nRDAP ↗ · easylot.net (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCommunity Hub\n\tcybershoke.net\n6.8 yearsRegistered 2019-11-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.cybershoke.net\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMatchmaker Hub\n\tfastcup.net\n14.6 yearsRegistered 2012-02-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.fastcup.net\n14.6 yearsRegistered 2012-02-16\nRDAP ↗ · fastcup.net (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Analytics\n\tleetify.com\n7.6 yearsRegistered 2019-03-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nleetify.com\n7.6 yearsRegistered 2019-03-01\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Analytics\n\tscope.gg\n7.8 yearsRegistered 2018-12-10\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nscope.gg\n7.8 yearsRegistered 2018-12-10\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tools\n\ttradeupspy.com\n6.5 yearsRegistered 2020-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.tradeupspy.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMarketplace\n\tcs.deals\n9.8 yearsRegistered 2016-12-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.cs.deals\n9.8 yearsRegistered 2016-12-03\nRDAP ↗ · cs.deals (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Price DB\n\tpricempire.com\n6.6 yearsRegistered 2020-01-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\npricempire.com\n6.6 yearsRegistered 2020-01-30\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Blackmarket\n\tFSB Market\n7.2 yearsRegistered 2019-07-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nFSB Market\n7.2 yearsRegistered 2019-07-27\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nReady-Account Hub\n\tz2u.com\n26.9 yearsRegistered 1999-11-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwww.z2u.com\n26.9 yearsRegistered 1999-11-10\nRDAP ↗ · z2u.com (parent)\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Gambling\n\tcsgoroll.com\n11.6 yearsRegistered 2015-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwww.csgoroll.com\nRegistry date unavailableRegistry date unavailable\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\trollbit.com\n11.9 yearsRegistered 2014-11-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrbsnin.com\n3 daysRegistered 2026-09-18\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nLicenced Casino\n\t500.casino\n5.9 yearsRegistered 2020-11-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette/Slots\n\tcsgobig.com\n11.4 yearsRegistered 2015-04-12\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcasedrop.com\n14.8 yearsRegistered 2011-12-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\tbanditcamp.com\n12.2 yearsRegistered 2014-06-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tskinbox.com\n18.8 yearsRegistered 2007-12-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\ttastydrop.com\n6.1 yearsRegistered 2020-08-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette Casino\n\tcsgopolygon.gg\n6.5 yearsRegistered 2020-03-28\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tmagicdrop.ru\n10.3 yearsRegistered 2016-05-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nDice Casino\n\tcsdice.com\n3.8 yearsRegistered 2022-11-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUpgrader Casino\n\tskinodds.com\n1.2 yearsRegistered 2025-06-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgowin.com\n12.0 yearsRegistered 2014-09-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrash Casino\n\tcsgorun.net\n7.3 yearsRegistered 2019-06-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\topenskins.com\n3.6 yearsRegistered 2023-02-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Gambling\n\trustbet.com\n7.6 yearsRegistered 2019-02-07\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgomagic.com\n9.4 yearsRegistered 2017-05-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUpgrader/Contract\n\tcsgobounty.com\n11.5 yearsRegistered 2015-03-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tezskins.com\n27.5 yearsRegistered 1999-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\trustcases.com\n7.2 yearsRegistered 2019-06-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgoreaper.com\n11.1 yearsRegistered 2015-08-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgocases.com\n12.3 yearsRegistered 2014-06-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Upgrader\n\tcsgo-skins.com\n11.2 yearsRegistered 2015-07-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgonet.com\n8.8 yearsRegistered 2017-12-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\twtfskins.com\n9.0 yearsRegistered 2017-10-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Casino\n\tflamecases.com\n10.0 yearsRegistered 2016-09-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tgamedom.com\n11.7 yearsRegistered 2015-01-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Battles\n\tskin.club\n9.0 yearsRegistered 2017-09-04\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsc-auth.net\n7.5 yearsRegistered 2019-04-02\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tdaddyskins.com\n9.9 yearsRegistered 2016-10-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Gambling\n\trustix.gg\n1.7 yearsRegistered 2025-01-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Upgrade\n\tskins.club\n4.2 yearsRegistered 2022-07-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgohouse.org\n146 daysRegistered 2026-04-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskinrave.net\n216 daysRegistered 2026-02-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tbloodycase.gg\n19 daysRegistered 2026-09-02\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nClicker/Upgrade\n\tcsgoclicker.com\n8.3 yearsRegistered 2018-05-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustbet.gg\n4.0 yearsRegistered 2022-09-30\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcs-drop.com\n262 daysRegistered 2026-01-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\thellstore.net\n11.7 yearsRegistered 2015-01-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustloot.com\n354 daysRegistered 2025-10-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgo-case.com\n10.3 yearsRegistered 2016-05-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgogem.com\n9.9 yearsRegistered 2016-10-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\trainbet.com\n8.8 yearsRegistered 2017-11-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nservices.rainbet.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustclash.com\n5.4 yearsRegistered 2021-05-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrash Casino\n\t12cs.fail\n181 daysRegistered 2026-03-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\twww.tf2easy.com\n6.3 yearsRegistered 2020-06-02\nRDAP ↗ · tf2easy.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2blaze.com\n7.6 yearsRegistered 2019-01-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tshuffle.com\n30.1 yearsRegistered 1996-07-31\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tbuff.market\n5.9 yearsRegistered 2020-10-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tavan.market\n8.3 yearsRegistered 2018-05-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Engine\n\tcs.money\n11.0 yearsRegistered 2015-09-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.dota.trade\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tuuskins.com\n2.6 yearsRegistered 2024-01-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Market\n\tyoupin898.com\n6.1 yearsRegistered 2020-08-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tc5game.com\n10.5 yearsRegistered 2016-03-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\twaxpeer.com\n7.3 yearsRegistered 2019-05-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwaxpeer.com\n7.3 yearsRegistered 2019-05-20\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBot Trading\n\tcs.money\n11.0 yearsRegistered 2015-09-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.dota.trade\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUS Marketplace\n\tdmarket.com\n30.2 yearsRegistered 1996-07-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nOfficial Market\n\tsteamcommunity.com/market\n20.3 yearsRegistered 2006-05-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNot an external login site2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Platform\n\tlootfarm.com\n11.9 yearsRegistered 2014-10-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Market\n\trustskins.com\n7.6 yearsRegistered 2019-01-31\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tkrakatoa.com\n26.4 yearsRegistered 2000-05-15\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\tshadowpay.com\n10.1 yearsRegistered 2016-08-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nChinese Powerhouse\n\tigxe.cn\n15.0 yearsRegistered 2011-09-06\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAutomated Swap\n\tswap.gg\n9.6 yearsRegistered 2017-01-29\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCash-out Portal\n\tbitskins.com\n11.2 yearsRegistered 2015-07-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Automation\n\ttf2mart.com\n1.1 yearsRegistered 2025-08-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Auctions\n\tskinbid.com\n10.2 yearsRegistered 2016-06-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Rental\n\tlootbear.com\n8.7 yearsRegistered 2018-01-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Valuation\n\tbackpack.tf\n14.4 yearsRegistered 2012-05-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Botnet\n\tstntrading.eu\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Cashout\n\tskinwallet.com\n18.0 yearsRegistered 2008-09-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nDota 2 Market\n\tdota2market.com\n12.2 yearsRegistered 2014-07-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nServer Network\n\txplay.gg\n5.3 yearsRegistered 2021-06-13\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMatchmaking Portal\n\tesportal.com\n26.8 yearsRegistered 1999-12-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nLATAM Hub\n\tgamersclub.com.br\n11.2 yearsRegistered 2015-06-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tools\n\tepidemic.gg\n4.9 yearsRegistered 2021-11-03\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tcs2stash.com\n3.5 yearsRegistered 2023-03-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tcsgoskins.gg\n6.8 yearsRegistered 2019-12-21\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tsteamanalyst.com\n12.6 yearsRegistered 2014-02-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Exchange\n\tsteamcardexchange.net\n13.3 yearsRegistered 2013-05-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tracker\n\tdotabuff.com\n14.2 yearsRegistered 2012-06-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tracker\n\ttracker.gg\n8.9 yearsRegistered 2017-10-12\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Exchange\n\tfunpay.com\n17.0 yearsRegistered 2009-09-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nGrey Market\n\tplayerauctions.com\n26.3 yearsRegistered 2000-06-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Portal\n\teldorado.gg\n8.0 yearsRegistered 2018-09-12\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Key Market\n\tg2a.com\n24.8 yearsRegistered 2001-12-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Key Market\n\tkinguin.net\n16.8 yearsRegistered 2009-12-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nVirtual Services\n\tg2g.com\n31.1 yearsRegistered 1995-08-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Broker\n\tplayerup.com\n19.3 yearsRegistered 2007-05-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfhub.net\n2.7 yearsRegistered 2023-12-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfaccounts.com\n5.3 yearsRegistered 2021-05-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Shop\n\tbuycsgorank.com\n6.2 yearsRegistered 2020-07-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tcsgosmurfkings.com\n9.3 yearsRegistered 2017-06-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfstore.co\n8.6 yearsRegistered 2018-03-03\nWHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlvlup.com\n9.9 yearsRegistered 2016-11-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlevels.com\n10.6 yearsRegistered 2016-02-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tlevelsteam.com\n79 daysRegistered 2026-07-04\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlevelu.com\n6.0 yearsRegistered 2020-09-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\teloking.com\n12.2 yearsRegistered 2014-07-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\tboosteria.org\n11.9 yearsRegistered 2014-10-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tovergear.com\n14.4 yearsRegistered 2012-04-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tblazingboost.com\n14.2 yearsRegistered 2012-06-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\tdota2boost.com\n2.9 yearsRegistered 2023-10-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tbuyboost.com\n22.4 yearsRegistered 2004-04-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\nL'argumentation de l'enquêteRègle sélectionnée / analyse et commentaire+\nCharge de la preuve\n\nL'enquête met en évidence le décalage entre les restrictions relatives à l'usage commercial et les services répertoriés ici. Il convient de classer chaque activité et de vérifier l'existence d'une autorisation expresse avant de conclure à une violation du contrat. Les frais liés au Marché communautaire ne s'appliquent pas à toutes les transactions commerciales externes.\n\nCe qu'est — et ce que n'est pas — un enregistrement balisé\n\nUn dossier est signalé lorsqu’il contient une observation datée qui fait entrer la plateforme, à première vue, dans le champ d’application de la clause. Un signalement ne constitue pas une infraction avérée, et aucune autorisation expresse de l’Valve n’a été mentionnée dans le dossier pour aucune des plateformes répertoriées ici. Lorsqu’une plateforme dispose d’une autorisation, la publication de celle-ci entraîne la suppression de l’entrée.\n\nSources et méthodologieEstimations, définitions et champ d'application+\n\nLes chiffres ci-dessus se rapportent à la règle sélectionnée. Les types d'enregistrements regroupent chaque plateforme une seule fois ; les balises complètes apparaissent dans les détails de la plateforme. La recherche et les filtres s'appliquent au sein de cette règle. Les dates d’enregistrement proviennent de l’instantané enregistré sur RDAP / WHOIS. Les sous-domaines utilisent la date de création du domaine parent. L’ancienneté ne suffit pas à elle seule à établir un fonctionnement continu ou une voie d’authentification. Les noms d’hôte d’authentification actuels proviennent de requêtes OpenID enregistrées, accompagnées d’un horodatage UTC ; les vérifications non résolues ne réutilisent pas les étiquettes héritées. L’observateur s’arrête avant la connexion à Steam et ne teste pas l’état du filtre de liens Steam. Télécharger les observations d'itinéraire ↗ Télécharger les résultats du registre ↗\n\nExplorer les archives sources ↗\nAnnexe G — D’un modèle de refus au dossier correspondant\nGuide pratique DSAR : demander les éléments de preuve\n\nInvoquez l'article 15 du RGPD pour demander les données à caractère personnel relatives à la création d'une clé API, à la récupération d'un compte et à l'accès au service d'assistance. Un enregistrement conservé permet de vérifier qui a lancé une action et sur quoi la plateforme s'est appuyée.\n\n01\nConservez votre chronologie.\n\nEnregistrez les notifications relatives au compte, les tickets, les identifiants de transaction et les dates en UTC. Sécurisez le compte et passez en revue les options de récupération applicables au jeu et à la transaction.\n\nSteam Informations sur la protection commerciale ↗\n02\nDemandez à consulter vos données conservées.\n\nDemandez les horodatages, les adresses IP sources, les événements clés du cycle de vie, les confirmations de sécurité et les actions de récupération liées au compte. Précisez les événements d'accès au service d'assistance et les destinataires lorsque ces données vous concernent.\n\n03\nConservez le bon de livraison.\n\nUtilisez le canal de contact dédié à la protection de la vie privée de Valve. Le délai de réponse habituel est d'un mois ; toute prolongation nécessaire pouvant aller jusqu'à deux mois supplémentaires doit être justifiée au cours de ce premier mois.\n\nValve contact relatif à la confidentialité ↗ archivé 2026-09-21 ↗\n04\nComparez les réponses.\n\nComparez les registres avec votre chronologie. Demandez les raisons des omissions, puis, si nécessaire, engagez une procédure de réclamation auprès de l'autorité de tutelle. Conservez la réponse telle que vous l'avez reçue.\n\nChamp d'application / Article 15\n\nLe droit d'accès porte sur les données à caractère personnel conservées, y compris celles figurant dans les fichiers journaux. Il ne garantit pas l'accès à tous les documents internes, aux enregistrements reconstitués ou aux données non expurgées concernant des tiers. Demandez une copie lisible et les motifs justifiant toute restriction.\n\nLignes directrices du CEPD relatives à l'accès, §§ 2, 4 à 6 ↗ · Articles 12, 15 et 77 du RGPD ↗ archivé 2026-09-20 ↗\n\nDemande d'accès aux données personnellesRGPD / Article 15\nSécurité du compte et historique des accès\n\nRemplacez les champs entre crochets avant de valider.\n\nTo: Valve Privacy Team\nSubject: Article 15 GDPR request — account security records\n\nAccount / SteamID: [YOUR ACCOUNT IDENTIFIER]\nRelevant period (UTC): [START] to [END]\nRelated support tickets: [TICKET REFERENCES]\n\nI request a copy of the personal data concerning me that you retain for this period, including:\n\n1. API-key registration, confirmation, use and revocation events, with available timestamps, source IP addresses, registered domains, device or user-agent information and non-secret key identifiers.\n\n2. Recorded account-recovery actions, password/email/phone changes, Steam Guard removals or resets, confirmation events and the account-related evidence relied on to authorize those actions.\n\n3. Personal data in support-access and administrative-action logs concerning my account, including available dates, purposes, actions and the support entity involved, subject to applicable rights of others.\n\n4. Account-related records used to determine any sanction, and available records of my complaints, reviews and responses.\n\nPlease also provide the applicable processing purposes, categories, recipients, retention periods or criteria, and available information about sources where data were not obtained from me.\n\nWhere processing relies on my consent, please provide the retained record of the consent relied upon and the wording presented at that time.\n\nPlease provide an intelligible electronic copy with time zones and field definitions. Please do not include active credentials or secret tokens. If any requested data are not held, please say so. For any withheld data, please identify the scope and legal basis of the restriction and provide the remainder.\n\nPlease acknowledge receipt and respond within the applicable Article 12 period, explaining any necessary extension. I also ask you to preserve relevant existing records while this request is handled.\n\nName: [YOUR NAME]\nDate: [DATE]\nCe qu'une adresse IP de centre de données permet de mettre en place\nUne anomalie constitue un élément justifiant l'ouverture d'une enquête.\n\nUne demande de clé API provenant du réseau d'un centre de données, comme dans l'exemple du fournisseur d'hébergement évoqué dans le cadre de cette enquête, peut s'avérer pertinente lorsqu'elle est recoupée avec les historiques de connexion, les confirmations et l'historique de l'utilisateur. Une adresse IP à elle seule ne permet pas d’identifier l’acteur ni de contourner automatiquement toutes les mesures de protection. La preuve qu’un acteur malveillant a fourni le consentement enregistré pourrait remettre en cause le caractère valable de ce consentement ; d’autres fondements juridiques et questions de responsabilité nécessitent une analyse distincte.\n\nConsultez la plainte relative à l'interdiction et au RGPD conservée →\nAnnexe H — Analyse des archives de Wayback Machine · Statistiques de prise en charge publiées\nVolume d'assistance. Délais de réponse publiés.\nContexte et limites de la source\n\nValve publie quotidiennement des statistiques relatives à l'assistance sur store.steampowered.com/stats/support. Les archives de Wayback Machine conservent des instantanés historiques de cette page de 2018 à 2026. Le rapport volume/effectifs que laissent entrevoir ces chiffres n'est pas compatible avec une vérification humaine de chaque ticket dans les délais de réponse publiés.\n\nComparez les chiffres d'audience archivés de Valve dans les instantanés enregistrés. La méthodologie explique ce que ces chiffres permettent et ne permettent pas de mesurer.\n\nVolume en fonction du délai de réponse publié (2018 → 2026)\nDeux files d'attente à un même guichet d'assistance, d'après 21 captures d'écran archivées.\n\nValve publie les chiffres relatifs à l'assistance en direct sur store.steampowered.com/stats/support. Chaque point ci-dessous correspond à la borne inférieure Valve telle qu’elle figurait sur cette page le jour où Internet Archive l’a archivée — et non à une estimation de notre part. Les deux séries représentent la même mesure dans la même unité ; elles doivent donc figurer sur un même axe et peuvent être comparées directement l’une à l’autre.\n\nDemandes de remboursement — argent Valve en possession deSécurité et récupération du compte — le compte que vous avez perdu\n0 h\n2 h\n4 h\n6 h\n8 h\n10 h\nno captures · 38 months\n2019\n2020\n2021\n2022\n2023\n2024\n2025\n2026\n8 h 44 m\naccount recovery\n52 m\nrefunds\n15 m — one capture only\n49 à 55 minLa limite inférieure du remboursement pour chaque capture, de février 2018 à août 2026. Sur une période de huit ans et demi, elle varie de moins de six minutes, tandis que le volume quotidien des remboursements est multiplié par neuf.\n2,4 h → 8,7 hLa borne inférieure du temps de récupération de compte se situe à environ 2,4 heures dans toutes les mesures jusqu'en décembre 2022, à l'exception d'une seule. Dans les trois mesures de 2026, Valve publie respectivement 10,9 h, 5,8 h et 8,7 h.\n×2,8 → ×13À quel point le remboursement est-il plus lent que les remboursements, d'après les chiffres publiés par Valve lui-même ? La situation reste stable pendant cinq ans, puis l'écart se creuse : la file d'attente qui a ralenti est celle où c'est l'utilisateur, et non Valve, qui doit avancer les frais.\n\nSource : 21 captures d'écran de Wayback Machine de store.steampowered.com/stats/support, de 2018-02-03 à 2026-08-10 ; extraction dans VALVE_EVIDENCE_PACK/databases/steam_support_stats_history.json. Lisez les limites indiquées par les chiffres : le graphique représente la inférieur limite de l'intervalle Valve impressions. La limite supérieure publiée est moins favorable sur les deux lignes : les remboursements ont varié entre 1,5 heure et 1,5 jour, et les récupérations entre 7,0 heures et 3,6 jours. Deux captures ont été archivées dans une édition localisée de la même Valve page — 2018-11-03 en tchèque, 2020-03-25 en français — et sont marquées (cs) et (fr) dans le tableau ; leurs chiffres apparaissent ici avec les noms d’unités traduits et les nombres tels que publiés, tandis que les chaînes source mot pour mot sont conservées dans le fichier d’extraction. Chaque capture a publié un temps de réponse pour les deux files d’attente, et aucun point sur l’une ou l’autre courbe n’est interpolé. La seule valeur de temps de récupération de 2020-10-21 en 15 minutes est signalée sur le graphique et conservée : elle n’apparaît que dans une seule capture et aucune autre capture ne se situe à un ordre de grandeur proche de celle-ci. Il n’existe aucune capture entre 2022-12-08 et 2026-02-01 ; cette lacune de 38 mois dans l’historique est ombrée, et rien n’est tracé par-dessus. Ces chiffres décrivent les délais de réponse publiés. Ils ne montrent pas ce qui se passe au sein d’un ticket, et Valve n’a publié aucun effectif permettant de les mettre en perspective.\n\nOuvrir chaque capture sous forme de tableau\nChaque capture archivée, telle qu'elle a été publiée\nCapture\tRemboursements / jour\tRéponse concernant le remboursement\tRécupération / jour\tMesures de reprise\n2018-02-03\t98,788\t50,12 minutes à 1 h 52\t25,662\t2,51 heures à 1,80 jour\n2018-05-07\t60,494\tDe 53,83 minutes à 1,47 jour\t24,226\tDe 2 h 45 à 2,22 jours\n2018-08-02\t69,084\t50,27 minutes à 1 h 59\t28,953\tDe 2 h 44 à 22 h 17\n2018-11-03 (cs)\t63,410\t49,28 minutes à 1 h 54\t33,910\tDe 2,42 heures à 1,31 jour\n2019-02-01\t76,305\t50,13 minutes à 1 h 52\t35,164\tDe 2,44 heures à 2,04 jours\n2019-05-18\t78,951\t51,03 minutes à 3 h 12\t27,514\tDe 2 h 46 à 20 h 39\n2019-09-07\t78,941\t50,65 minutes à 1,66 heure\t28,812\tDe 2 h 42 à 13 h 59\n2019-12-13\t69,589\t50,77 minutes à 1 h 55\t25,322\tDe 2 h 45 à 1,13 jour\n2020-03-25 (fr)\t139,278\t49,45 minutes à 1 h 53\t32,302\tDe 2,48 heures à 3,62 jours\n2020-06-26\t278,504\t48,98 minutes à 2 h 29\t20,343\tDe 2,39 heures à 6,99 heures\n2020-10-21\t107,633\t50,80 minutes à 1 h 54\t20,688\t15,33 minutes à 8,62 heures\n2021-03-20\t158,956\t50,80 minutes à 1,64 heure\t25,760\tDe 2,34 heures à 11,62 heures\n2021-06-26\t547,907\t51,93 minutes à 6,73 heures\t29,728\tDe 2 h 40 à 15 h 63\n2021-10-10\t170,103\t51,88 minutes à 3 h 25\t23,989\tDe 2 h 39 à 13 h 05\n2022-01-31\t354,386\t53,65 minutes à 8 h 09\t24,391\tDe 2 h 42 à 15 h 29\n2022-05-09\t172,555\t51,83 minutes à 1,65 heure\t23,289\tDe 2 h 41 à 16 h 90\n2022-09-05\t153,453\t53,67 minutes à 4 h 15\t23,594\tDe 2 h 45 à 1,22 jour\n2022-12-08\t181,075\t54,83 minutes à 6,67 heures\t27,111\tDe 2,46 heures à 18,89 heures\n2026-02-01\t317,762\t50,30 minutes à 1 h 52\t47,197\tDe 10 h 91 à 21 h 30\n2026-05-09\t246,776\t50,12 minutes à 1 h 52\t35,264\tDe 5,81 heures à 15,60 heures\n2026-08-10\t373,244\t52,05 minutes à 2 h 07\t45,319\tDe 8 h 73 à 16 h 52\nOBSERVATION CLÉ :\nDe l'autre côté 21 captures Wayback entre 2018-02-03 et 2026-08-10, les demandes de remboursement quotidiennes variaient entre 60,494 (mai 2018) à 547,907 (juin 2021) — un 9,1 × écart. Le chiffre pour 2026 est de 373,244 (+278% par rapport aux données de février 2018).\nAu cours de ces neuf mêmes années, la limite inférieure publiée concernant le délai de traitement des demandes de remboursement n’a jamais dépassé 49 à 55 minutes bande : un mouvement total de moins de six minutes, alors que la charge de travail sous-jacente a été multipliée par neuf.\nSi une personne consacrait ne serait-que 5 secondes à la lecture de chaque ticket, le traitement de 373,244 tickets par jour (chiffre actuel) prendrait 22 agents travaillant 24 heures sur 24, 7 jours sur 7 simplement pour les ouvrir et les fermer ; ce chiffre atteint 32 lors du pic (547,907, juin 2021).\nSi le temps de réponse publié reflétait le temps de traitement par ticket (~52 min/ticket), les effectifs simultanés nécessaires seraient de l'ordre de 13,500 agents au volume actuel et ~20,000 au pic. Aucune donnée provenant d'une source fiable concernant les effectifs de soutien de Valve n'a pu être trouvée ; on ne tient pas compte de ce chiffre ici.\nCe qui suit : le rapport volume/effectifs n'est pas compatible avec un examen humain de chaque ticket dans les délais de réponse publiés. Les chiffres correspondent à un premier traitement largement automatisé ; la proportion de tickets faisant l'objet d'un examen humain n'est pas communiquée.\nPourquoi est-ce important pour la conformité au RGPD ?\n\nL'article 22 du RGPD interdit toute prise de décision individuelle entièrement automatisée qui produit des effets juridiques significatifs, sans prévoir le droit à un contrôle humain sur demande. Si les décisions de support (clôture de tickets, actions sur les comptes, refus de demandes de données) sont prises entièrement par des scripts automatisés, chacune de ces décisions qui « affecte de manière significative » l’utilisateur peut constituer une violation de l’article 22.\n\nBillet HT-2YBP-F7JP-D4VB (Section 18) a été classée après trois jours avec un renvoi type et sans examen approfondi du fondement juridique invoqué. Le ticket ne permet pas de déterminer si une personne l’a examiné ; il s’agit là d’une question que l’autorité de contrôle peut poser à Valve en vertu de l’article 22 et de l’article 15, paragraphe 1, point h).\n\nSource : instantanés de Wayback Machine de store.steampowered.com/stats/support (2018-02-03, 2021-06-26, 2026-08-10) — données extraites dans VALVE_EVIDENCE_PACK/databases/steam_support_stats_history.json (21 captures, 2018–2026). Remarque : le délai de réponse de « ~52 min » correspond à la limite inférieure pour la catégorie des remboursements ; le délai de réponse concernant la sécurité des comptes variait entre 2,4 et 16,5 heures sur l’ensemble de ces captures. 2021-06-26 correspond au pic historique (547,907 demandes de remboursement), et non à un point médian monotone — le volume a été multiplié par environ 6 entre 2020 et 2021, puis a partiellement baissé avant de remonter à 373 000 en 2026.\nAnnexe I — Portée de l'ensemble de données · chiffres pouvant être reproduits\nComptez les enregistrements. Vérifiez la portée.\nContexte et limites de la source\n\nComptez les enregistrements, puis vérifiez les affirmations : chaque chiffre ci-dessous peut être recalculé à partir des fichiers publiés.\n\nExaminez les ensembles de données sous-jacents, reproduisez les décomptes et distinguez les lignes sources des incidents uniques.\n\nLe fichier CSV principal contient 40,448 lignes. Parmi ceux-ci, 36,516 proviennent du fil d'actualités « Discord-AntiScam » consacré au phishing. Les autres 3,932 Ces lignes couvrent GitHub, les revues de code, les résultats de recherche, les contributions aux forums et d'autres sources, offrant ainsi un index complet des sujets abordés par la communauté et des rapports de sécurité.\n\nDans ce fichier CSV, 1,690 lignes sont classées sous l'étiquette « Unpatched Security Exploit » (Faille de sécurité non corrigée), qui regroupe les problèmes signalés par les utilisateurs et les divulgations de vulnérabilités par le passé. Pour retracer ces signalements, il faut examiner la chronologie de compilation spécifique à chaque fil de discussion ainsi que l'historique public des correctifs.\n\nL'archive consultable « 16,319-record » est une version distincte et organisée, dotée de son propre manifeste, conçue pour permettre une exploration locale précise des réclamations d'utilisateurs et des rapports d'incident spécifiques.\n\nPour établir une piste d'audit fiable, chaque enregistrement signalé par un utilisateur doit être vérifié par rapport aux calendriers de compilation documentés et aux journaux historiques des correctifs.\n\nLes notices de la collection « Partie II » (distincte) 231,829 identifiants d'annonce uniques, dont 33,509 dans la catégorie des inscriptions automatisées et 198,320 signalé comme transfert non vérifié. La valeur SHA-256 du fichier d’entrée correspond à celle conservée dans la mesure. Ces chiffres décrivent les tentatives de mise en vente et les transferts observés plutôt que les montants des transactions finalisées ou les totaux vérifiés des vols, ce qui souligne la nécessité de disposer des registres primaires de la plateforme pour mesurer l’impact économique exact. Liste des mesures et des hachages ↗\n\nMaîtriser le format CSV ↗ · Liste des archives consultables ↗ · Consulter les documents sources ↗\n\nAnnexe J — À propos de cette enquête\nValve ne publie aucun rapport sur les mesures coercitives. Nous en avons construit un.\n\nIndépendant. À but non commercial. Élaboré exclusivement à partir de données publiques. Soumis aux autorités de régulation.\n\n88.97%flotte de véhicules autonomes : aucune restriction d'aucune sorte\n67.77%parmi les 51,732 escrocs condamnés, certains sont en liberté\n$26.8M+seuil minimal des dépenses en magasin pour les flottes non limitées\n3.6%domaines liés aux jeux d'argent bloqués par le filtre de liens de Valve\n8 ansd'incidents de sécurité recensés\n\nDe quoi s'agit-il ? Un dossier d'analyse approfondie de la plateforme Steam de la société Valve : son historique en matière d'application des règles, son économie basée sur le « card-farming », son cadre juridique et l'infrastructure d'authentification utilisée par les opérateurs de jeux d'argent via le relais OpenID propre à Steam. Chaque chiffre est vérifiable à partir de deux sources : l’API publique de Valve et les ensembles de données publiés parallèlement à cette enquête.\n\nÀ qui s'adresse-t-il ? Les autorités de régulation compétentes en matière de Valve — l’autorité de contrôle du RGPD aux Pays-Bas, le FinCEN, la SEC, le coordinateur des services numériques (DSA), l’UOKiK, ainsi que tout organisme chargé de l’application de la loi enquêtant sur les flux financiers liés à Steam. Également pour les journalistes, les chercheurs et tous les utilisateurs ayant fait l'objet d'une suspension définitive de leur compte, d'un refus de remboursement ou d'un vol de leurs biens, et à qui l'on a indiqué qu'il n'existait aucun recours.\n\nLa seule exigence. Valve conserve ces données dans leur intégralité — motifs d’interdiction joints, espace d’identification complet, en temps réel. Il est capable d’exécuter n’importe quelle requête contenue dans ce dossier en quelques secondes et a choisi de n’en publier aucune partie. La question qui se pose à toute autorité compétente est simple : Pourquoi pas ?\n\nCe que les auteurs ne prétendent pas. Aucune connexion à Steam n’a été effectuée sur une plateforme tierce au cours de ces travaux. Une URL OpenID fournie définit les paramètres de la requête, et non une connexion effective. Le fait qu’un domaine distinct soit enregistrable ne constitue pas en soi une preuve de contournement. Les dates d’enregistrement constituent des limites inférieures quant au moment où un hôte aurait pu apparaître pour la première fois dans une requête OpenID ; elles ne prouvent pas une utilisation continue. Les auteurs ne se prononcent pas sur ce que Valve savait ou avait l’intention de faire : chaque affirmation concernant Valve est étayée par un document public daté ou une observation datée. Lorsqu’une affirmation ne pouvait s’appuyer sur un document source, elle a été supprimée.\n\nQui sommes-nous ?\n\nPhishDestroy — enquêteurs indépendants. Aucun lien avec la société Valve ni avec aucune des plateformes mentionnées ici. Un compte Steam a été utilisé uniquement pour consigner la demande relative au RGPD mentionnée à la section 18.\n\nMentions légales\n\nEnquête d'intérêt public, non commerciale et décentralisée. Toutes les données sont fournies « en l'état », sans aucune garantie. Cette publication ne constitue pas une décision judiciaire.\n\nDOMAINE PUBLIC\nLicences\n\nTous les droits sont cédés à l'humanité. Reproduction, adaptation, publication autorisées — mention de la source non requise. Accès interdit aux personnes résidant dans les pays soumis aux sanctions de l'OFAC. Licence complète et clause de non-responsabilité →",
        "headings": [
          {
            "level": 2,
            "id": "briefing-heading",
            "text": "Le record. L'histoire. Les questions sans réponse."
          },
          {
            "level": 2,
            "id": null,
            "text": "Lettre ouverte à la Commission des jeux de l'État de Washington"
          },
          {
            "level": 3,
            "id": "wsgc-public-address-title",
            "text": "Dix jours se sont transformés en dix ans.Rouvrez la fiche."
          },
          {
            "level": 2,
            "id": null,
            "text": "Le site est bloqué. La page de connexion, elle, ne l'est pas."
          },
          {
            "level": 3,
            "id": null,
            "text": "Figure 3.1 — Les deux itinéraires, représentés graphiquement."
          },
          {
            "level": 3,
            "id": null,
            "text": "Le piège de la vision d'ensemble : le filtre de liens n'est qu'une mise en scène de conformité, pas un véritable bouclier"
          },
          {
            "level": 3,
            "id": null,
            "text": "Un domaine principal bloqué associé à un hôte d'authentification non bloqué laisse la route d'accès ouverte — et celle-ci reste ouverte pendant des années."
          },
          {
            "level": 3,
            "id": null,
            "text": "Contexte : Qu'est-ce que Steam et pourquoi est-ce important dans ce contexte ?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ce qu’a fait Valve : le bloc de domaines"
          },
          {
            "level": 3,
            "id": null,
            "text": "Qu'est-ce qu'un domaine proxy ?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Le point critique : l'hôte d'authentification est envoyé à Steam dans chaque requête"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ce que cela prouve"
          },
          {
            "level": 3,
            "id": null,
            "text": "Dans Steam, la liste de Valve est la seule liste."
          },
          {
            "level": 3,
            "id": null,
            "text": "Contournement de la protection par filtre de liaison"
          },
          {
            "level": 3,
            "id": null,
            "text": "Le navigateur Web Big Picture divulgue des cookies de connexion et expose des informations sensibles (ce qui peut entraîner le piratage de comptes)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Quelles sont les conséquences pour un mineur qui a installé un antivirus ?"
          },
          {
            "level": 3,
            "id": null,
            "text": "L'ancienneté du domaine.Date de l'observation."
          },
          {
            "level": 2,
            "id": null,
            "text": "Un point de terminaison a été fermé. Le traçage public a perdu une clé."
          },
          {
            "level": 3,
            "id": null,
            "text": "L'époque d'avant la panne d'électricité"
          },
          {
            "level": 3,
            "id": null,
            "text": "Après le changement"
          },
          {
            "level": 2,
            "id": null,
            "text": "Une seule session. Un accès plus étendu que ce que l'utilisateur perçoit."
          },
          {
            "level": 3,
            "id": null,
            "text": "1. Authentification renforcée insuffisante"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. Absence du principe du droit d'accès minimal"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. Problèmes de gestion des sessions"
          },
          {
            "level": 3,
            "id": null,
            "text": "4. Le blocage au niveau du domaine des hôtes d'authentification était techniquement réalisable"
          },
          {
            "level": 3,
            "id": "integration-paradox-title",
            "text": "Valve est compilé quotidiennement selon ces règles. Ce n'est pas le cas ici."
          },
          {
            "level": 4,
            "id": null,
            "text": "Portées granulaires de GitHub vs Valve Steam API Web"
          },
          {
            "level": 2,
            "id": null,
            "text": "Simulateur interactif d'exploitation et de détournement"
          },
          {
            "level": 2,
            "id": null,
            "text": "Les points d'extrémité associés à la séquence."
          },
          {
            "level": 2,
            "id": null,
            "text": "Une case cochée. Qui a coché cette case ?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Comment Valve a finalement mis fin à la « substitution commerciale » — et pourquoi il a fallu sept ans de solutions de contournement"
          },
          {
            "level": 4,
            "id": null,
            "text": "Délai de recharge de l'avatar et du nom (février 2024)"
          },
          {
            "level": 4,
            "id": null,
            "text": "Inversion de tendance sur le CS2 sur 7 jours (juillet 2025)"
          },
          {
            "level": 4,
            "id": null,
            "text": "Mise à jour obligatoire des notifications push mobiles pour l'API (décembre 2023)"
          },
          {
            "level": 4,
            "id": null,
            "text": "Bannières « Âge et nom du compte » (2022-2024)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Leur règlement. Les plateformes enregistrées."
          },
          {
            "level": 3,
            "id": "enforcement-focus-title",
            "text": "Un seul règlement. Une application inégale."
          },
          {
            "level": 4,
            "id": null,
            "text": "Automatisation"
          },
          {
            "level": 4,
            "id": null,
            "text": "Usage commercial"
          },
          {
            "level": 4,
            "id": null,
            "text": "VPN et dissimulation de l'emplacement"
          },
          {
            "level": 4,
            "id": null,
            "text": "Masquage des liens"
          },
          {
            "level": 4,
            "id": null,
            "text": "Qui examine la décision lorsque le service d'assistance clôt le dossier ?"
          },
          {
            "level": 2,
            "id": null,
            "text": "Une API d'automatisation. Une règle interdisant l'automatisation."
          },
          {
            "level": 3,
            "id": null,
            "text": "Le mythe du « développeur de jeux vidéo »"
          },
          {
            "level": 4,
            "id": null,
            "text": "La contradiction de l'automatisation"
          },
          {
            "level": 4,
            "id": null,
            "text": "Un rôle côté serveur dans le flux commercial"
          },
          {
            "level": 2,
            "id": null,
            "text": "Dix jours exigés. Dix ans à justifier."
          },
          {
            "level": 3,
            "id": "letter-company",
            "text": "VALVE CORPORATION"
          },
          {
            "level": 3,
            "id": null,
            "text": "Dix jours.Et ensuite ?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Suivez l'hôte de retour indiqué."
          },
          {
            "level": 3,
            "id": "washington-record-heading",
            "text": "Deux délais. Une norme d'application qui reste sans réponse."
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve accorde 10 jours aux sites de jeux d'argent"
          },
          {
            "level": 4,
            "id": null,
            "text": "Washington fait pression Valve"
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve rejette l'accusation"
          },
          {
            "level": 4,
            "id": null,
            "text": "Les itinéraires observés en septembre 2026"
          },
          {
            "level": 4,
            "id": null,
            "text": "Dix-huit mois après la réponse de Valve, l'autorité de régulation continuait de qualifier cela d'« intention »."
          },
          {
            "level": 3,
            "id": null,
            "text": "La « Décennie du préavis de 10 jours » : audit de survie médico-légal des 23 sites désignés"
          },
          {
            "level": 4,
            "id": null,
            "text": "Des alertes de 10 jours aux conglomérats offshore : un chiffre d'affaires de plusieurs milliards de dollars"
          },
          {
            "level": 2,
            "id": null,
            "text": "Le nom d'hôte figure déjà dans la requête."
          },
          {
            "level": 3,
            "id": null,
            "text": "Précédents documentés et signalés"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ce qu'une date d'immatriculation indique et ce qu'elle n'indique pas"
          },
          {
            "level": 3,
            "id": null,
            "text": "Audit comparatif : normes de conformité aux API"
          },
          {
            "level": 2,
            "id": "market-thesis-heading",
            "text": "L'écart de prix « off-Steam »"
          },
          {
            "level": 2,
            "id": null,
            "text": "L'écart de prix est quantifiable."
          },
          {
            "level": 3,
            "id": null,
            "text": "Ce que révèle ce chiffre en dollars"
          },
          {
            "level": 3,
            "id": null,
            "text": "De nombreuses salles indiquent une valeur en dollars supérieure à Steam."
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam reste en tête en termes de nombre d'offres."
          },
          {
            "level": 3,
            "id": null,
            "text": "L'écosystème commercial est sous les yeux de tous."
          },
          {
            "level": 2,
            "id": null,
            "text": "Qui peut réinitialiser les mesures de sécurité ?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Un ticket de récupération qui a désactivé la sécurité du compte, et une perte déclarée de $10,000"
          },
          {
            "level": 3,
            "id": null,
            "text": "Au-delà de l'inventaire."
          },
          {
            "level": 3,
            "id": "theft-ledger-title",
            "text": "Valve a ouvert la porte à deux reprises, à trente-trois mois d'intervalle. Elle ne s'est jamais refermée."
          },
          {
            "level": 4,
            "id": null,
            "text": "Ce que le registre révèle, contrairement à chaque cas pris individuellement."
          },
          {
            "level": 3,
            "id": null,
            "text": "La confidentialité doit aller de pair avec la responsabilité technique."
          },
          {
            "level": 2,
            "id": null,
            "text": "Suivez la trace de l'argent. Séparez les transactions."
          },
          {
            "level": 3,
            "id": null,
            "text": "Là où l'argent circule réellement."
          },
          {
            "level": 3,
            "id": null,
            "text": "Classez d'abord l'activité, puis l'obligation."
          },
          {
            "level": 3,
            "id": null,
            "text": "Suivi des recettes, des connaissances et de l'assistance."
          },
          {
            "level": 2,
            "id": null,
            "text": "La loi sur les services numériques : consigner les connaissances"
          },
          {
            "level": 3,
            "id": null,
            "text": "Un délai de dix jours."
          },
          {
            "level": 3,
            "id": null,
            "text": "La fenêtre temporelle DSA."
          },
          {
            "level": 3,
            "id": null,
            "text": "La durée doit être accompagnée d'un historique des notifications."
          },
          {
            "level": 3,
            "id": null,
            "text": "du chiffre d'affaires annuel mondial"
          },
          {
            "level": 2,
            "id": null,
            "text": "Mineurs : une connexion avec « Steam » ne constitue pas une vérification de l'âge"
          },
          {
            "level": 3,
            "id": null,
            "text": "Identifiez l'opérateur et les données."
          },
          {
            "level": 3,
            "id": null,
            "text": "Enregistrez le parcours, de la connexion au versement."
          },
          {
            "level": 2,
            "id": null,
            "text": "La demande. La réponse. La comparaison qui manque."
          },
          {
            "level": 3,
            "id": null,
            "text": "Ces documents existent ; la personne concernée ne les a pas reçus."
          },
          {
            "level": 2,
            "id": null,
            "text": "Le contrat d'abonnement par rapport à l'architecture propre à la plateforme"
          },
          {
            "level": 3,
            "id": null,
            "text": "Le plafond du marché et l'interdiction d'utilisation à des fins commerciales"
          },
          {
            "level": 3,
            "id": null,
            "text": "La vulnérabilité liée à la clé API relève davantage d'un problème de conception de la plateforme que d'une négligence de la part des utilisateurs"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve reçoit le nom d'hôte d'authentification à chaque connexion"
          },
          {
            "level": 3,
            "id": null,
            "text": "La tendance qui se dégage des plaintes archivées"
          },
          {
            "level": 3,
            "id": null,
            "text": "Un tribunal chargé d'examiner ce dossier ne se contenterait pas d'interpréter la SSA de manière isolée."
          },
          {
            "level": 2,
            "id": null,
            "text": "Les conclusions. Les documents que nous demandons."
          },
          {
            "level": 2,
            "id": null,
            "text": "Note relative aux éléments de preuve — documents fournis par la source n° 1"
          },
          {
            "level": 2,
            "id": null,
            "text": "La caviardage dans le fichier PDF fourni est purement esthétique : le texte masqué reste extractible"
          },
          {
            "level": 2,
            "id": null,
            "text": "Pièces relatives à l'assistance et à la correspondance juridique"
          },
          {
            "level": 2,
            "id": null,
            "text": "Documents sources sélectionnés"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-01",
            "text": "Clés matérielles, demandées en 2016"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-02",
            "text": "Rapports d'erreurs sans possibilité effective de se désinscrire"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-03",
            "text": "Abus de tickets d'authentification signalé à Valve"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-01",
            "text": "44 achats contestés sur le marché"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-02",
            "text": "Une exclusion définitive et des recours irrecevables"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-03",
            "text": "Une remise à zéro de la reprise et une perte déclarée de $10,000"
          },
          {
            "level": 2,
            "id": null,
            "text": "ArchiSteamFarm et la clause d'automatisation"
          },
          {
            "level": 2,
            "id": null,
            "text": "Rules ledger: clauses against recorded platforms"
          },
          {
            "level": 3,
            "id": "ledger-title",
            "text": "Utilisation commerciale et facturation du compte"
          },
          {
            "level": 3,
            "id": "lw-register-title",
            "text": "Registre de la plateforme 175"
          },
          {
            "level": 4,
            "id": null,
            "text": "Charge de la preuve"
          },
          {
            "level": 4,
            "id": null,
            "text": "Ce qu'est — et ce que n'est pas — un enregistrement balisé"
          },
          {
            "level": 2,
            "id": null,
            "text": "Guide pratique DSAR : demander les éléments de preuve"
          },
          {
            "level": 3,
            "id": null,
            "text": "Conservez votre chronologie."
          },
          {
            "level": 3,
            "id": null,
            "text": "Demandez à consulter vos données conservées."
          },
          {
            "level": 3,
            "id": null,
            "text": "Conservez le bon de livraison."
          },
          {
            "level": 3,
            "id": null,
            "text": "Comparez les réponses."
          },
          {
            "level": 3,
            "id": null,
            "text": "Sécurité du compte et historique des accès"
          },
          {
            "level": 3,
            "id": null,
            "text": "Une anomalie constitue un élément justifiant l'ouverture d'une enquête."
          },
          {
            "level": 2,
            "id": null,
            "text": "Volume d'assistance. Délais de réponse publiés."
          },
          {
            "level": 3,
            "id": null,
            "text": "Deux files d'attente à un même guichet d'assistance, d'après 21 captures d'écran archivées."
          },
          {
            "level": 2,
            "id": null,
            "text": "Comptez les enregistrements. Vérifiez la portée."
          },
          {
            "level": 2,
            "id": null,
            "text": "Valve ne publie aucun rapport sur les mesures coercitives.\nNous en avons construit un."
          }
        ],
        "links": [
          "https://dotesports.com/counter-strike/news/csgo-lounge-billion-bets-3896",
          "https://store.steampowered.com/agreement/?l=english",
          "http://web.archive.org/web/20260921022032/https://store.steampowered.com/agreement/?l=english",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-all-results.json",
          "https://blog.counter-strike.net/expresstrade/",
          "http://web.archive.org/web/20260307161538/https://blog.counter-strike.net/expresstrade/",
          "https://wsgc.wa.gov/news/2016/washington-state-gambling-commission-orders-valve-stop-skins-gambling",
          "http://web.archive.org/web/20260520012601/https://wsgc.wa.gov/news/2016/washington-state-gambling-commission-orders-valve-stop-skins-gambling",
          "https://fr.scribd.com/document/328063293/Valve-s-Oct-18th-response-to-Washington-State-Gambling-Commission-s-cease-and-desist",
          "https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921021947/https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921022628/https://steamcommunity.com/linkfilter/?url=https:%2F%2Frollbit.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rbsnin.com.20260921T021120Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rollbit.com.json",
          "http://web.archive.org/web/20260921022740/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fskin.club",
          "http://web.archive.org/web/20260921022842/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fsc-auth.net",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skin.club.json",
          "http://web.archive.org/web/20260921022603/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fhowl.gg",
          "http://web.archive.org/web/20260921022636/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fhowl.uno",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/howl.gg.json",
          "http://web.archive.org/web/20260921022840/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fduelbits.com",
          "http://web.archive.org/web/20260921022901/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fswitchflips.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/duelbits.com.json",
          "http://web.archive.org/web/20260921022758/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgofast.com",
          "http://web.archive.org/web/20260921022847/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fauthtofast.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgofast.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/farmskins.com.20260921T025840Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/steam.kobal.cc.20260921T025844Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/farmskins.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cobaltlab.tech.20260921T041604Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cobaltauth.com.20260921T041608Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/cobaltlab.tech.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgo.net.20260921T041619Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cn2.easylot.net.20260921T041623Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgo.net.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/ggdrop.com.20260921T041637Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/ggauth.com.20260921T041641Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/ggdrop.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rustchance.com.20260921T041703Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/hgfuihd.com.20260921T041706Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rustchance.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skin.fans.20260921T041710Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.skinfans.com.20260921T041713Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skin.fans.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinport.com.20260921T041724Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinport.app.20260921T041728Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skinport.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skins.cash.20260921T041731Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinscash.live.20260921T041735Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skins.cash.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2hunt.com.20260921T041739Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rstspcl.com.20260921T041742Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tf2hunt.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgogem.com.20260922T192355Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/api.csgem.com.20260922T192358Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-2026-09-22.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/gamdom.com.20260922T192326Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/login.gambldom.com.20260922T192330Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/12cs.fail.20260922T192347Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/fail.games.20260922T192351Z.html",
          "http://web.archive.org/web/20260921022953/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgoempire.com",
          "http://web.archive.org/web/20260921022947/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgoempirelogin4.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgoempire.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cs.money.20260921T021131Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.dota.trade.20260921T021134Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/cs.money.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csfloat.com.20260921T041612Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgofloat.com.20260921T041615Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csfloat.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/g4skins.com.20260921T041630Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.g4s.to.20260921T041634Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/g4skins.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/juice.gg.20260921T041644Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/letmeinjuice.com.20260921T041648Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/juice.gg.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/market.csgo.com.20260921T041652Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2.net.20260921T041655Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/market.csgo.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rust.tm.20260921T041659Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rust.tm.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgolounge.com.20260922T192333Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2.net.20260922T192340Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2lounge.com.20260922T192337Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinbaron.de.20260921T041717Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinbaron.com.20260921T041721Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skinbaron.de.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2royal.com.20260921T041746Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2auth.com.20260921T041750Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tf2royal.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tradeit.gg.20260921T041753Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/connect-tradeit.com.20260921T041757Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tradeit.gg.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/upgrader.pro.20260921T041801Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/upgauth.space.20260921T041804Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/upgrader.pro.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-recheck-2026-09-21.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/domain-registration.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wayback-snapshots.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-2026-09-22c.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/master_registry.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/longitudinal-steam-phishing-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-steam-phishing-100.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-coverage-2026-09-22.json",
          "https://blog.csfloat.com/how-floatdb-tracks-items/",
          "http://web.archive.org/web/20260921022415/https://blog.csfloat.com/how-floatdb-tracks-items/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/platform-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/platforms-removed.json",
          "https://hackerone.com/reports/291750",
          "http://web.archive.org/web/20251116185046/https://hackerone.com/reports/291750",
          "https://hackerone.com/reports/1079561",
          "http://web.archive.org/web/20260924181830/https://hackerone.com/reports/1079561",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/hackerone-reports.json",
          "https://phishdestroy.io/steam_dossier/fr/steam_enforcement_evidence.html#support-records",
          "https://www.darknavy.org/blog/exploiting_steam_usual_and_unusual_ways_in_the_cef_framework/",
          "https://steamcommunity.com/groups/SteamClientBeta/discussions/0/3365901765276206401/",
          "http://web.archive.org/web/20250804051514/https://steamcommunity.com/groups/SteamClientBeta/discussions/0/3365901765276206401/",
          "https://www.chromium.org/developers/design-documents/safebrowsing/",
          "http://web.archive.org/web/20260821101616/https://www.chromium.org/developers/design-documents/safebrowsing/",
          "https://www.chromium.org/developers/how-tos/api-keys/",
          "http://web.archive.org/web/20260830122831/https://www.chromium.org/developers/how-tos/api-keys/",
          "https://github.com/Homebrew/homebrew-cask/issues/193814",
          "https://testsafebrowsing.appspot.com/",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/domain-registration.json",
          "https://phishdestroy.io/steam_dossier/fr/AUTH_AUDIT.md",
          "https://datatracker.ietf.org/doc/rfc6749/",
          "https://docs.cloud.google.com/docs/authentication/api-keys",
          "https://listings.pcisecuritystandards.org/pdfs/PCI_DSS_Resource_Guide_(003).pdf",
          "https://developer.apple.com/news/?id=02202019a",
          "http://web.archive.org/web/20250506070026/https://developer.apple.com/news/?id=02202019a",
          "https://dev.twitch.tv/docs/authentication/validate-tokens/",
          "https://discuss.dev.twitch.com/t/legacy-twitch-api-v5-i-e-kraken-shutdown-reminder-february-28-2022/36589",
          "http://web.archive.org/web/20250127085635/https://discuss.dev.twitch.com/t/legacy-twitch-api-v5-i-e-kraken-shutdown-reminder-february-28-2022/36589",
          "https://store.steampowered.com/news/posts/?enddate=1788390000",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/4123547285514022851",
          "https://skinvault.gg/blog/cs2-trade-protection-explained/",
          "https://csmarketcap.com/blog/market-insights/from-boom-to-bust-cs2s-trade-protection-impact",
          "https://skin.land/blog/steam-changes-cs2-trade-ban-logic-timing/",
          "https://help.steampowered.com/faqs/view/3041-A87A-E5F6-B6AC",
          "https://steamcommunity.com/ogg/593110/announcements/detail/533224478739530146",
          "https://steamcommunity.com/games/CSGO/announcements/detail/4447966961421256740",
          "https://steamcommunity.com/sharedfiles/filedetails/?id=2926756889",
          "https://steamcommunity.com/dev/apikey",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3734103130194459461",
          "https://steamcommunity.com/discussions/forum/1/3807266184852932971/",
          "https://help.steampowered.com/faqs/view/225C-C51E-B8F0-55B2",
          "https://store.steampowered.com/news/group/4/view/3314112260640237775",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/issues/325",
          "https://blog.dota2.com/2020/05/trading-cooldown/",
          "https://blog.counter-strike.net/index.php/2018/03/20308/",
          "http://web.archive.org/web/20250226114333/https://blog.counter-strike.net/index.php/2018/03/20308/",
          "https://phishdestroy.io/steam_dossier/fr/steam_evidence_archive.html",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/493839547938902179",
          "https://store.steampowered.com/online_conduct",
          "http://web.archive.org/web/20260921022120/https://store.steampowered.com/online_conduct",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260918014700/https://store.steampowered.com/subscriber_agreement/",
          "https://steamcommunity.com/dev/apiterms",
          "http://web.archive.org/web/20260921022210/https://steamcommunity.com/dev/apiterms",
          "https://help.steampowered.com/en/faqs/view/628C-E332-BD8C-4D36",
          "https://phishdestroy.io/steam_dossier/fr/social_graph.html",
          "https://phishdestroy.io/steam_dossier/fr/security_timeline.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wsgc-skins-gambling-briefing-2018.pdf",
          "https://wsgc.wa.gov/sites/default/files/2023-10/Skins%20Gambling.pdf",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wsgc-briefing-manifest.json",
          "https://x.com/csgobig",
          "https://www.facebook.com/csgobigofficial/",
          "https://500.casino/",
          "https://csgolounge.com/",
          "https://csgocasino.gg/",
          "https://x.com/CSGOatsecom",
          "https://x.com/CSGOSweep/status/937420902538543106",
          "https://x.com/Wild",
          "https://x.com/csgopot",
          "https://x.com/csgodiamondscom",
          "https://www.ftc.gov/legal-library/browse/cases-proceedings/162-3184-csgo-lotto-matter",
          "https://x.com/CSGODouble",
          "https://x.com/csgo_massive",
          "https://www.facebook.com/csgostrongfree/",
          "https://www.facebook.com/CSNCOM/",
          "https://www.gamblingcommission.gov.uk/report/young-people-and-gambling",
          "https://www.aph.gov.au/Parliamentary_Business/Committees/Senate/Environment_and_Communications/Gamingmicro-transactions",
          "https://phishdestroy.io/steam_dossier/fr/elite_skins.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/csfloat-catalogue.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/skinport-floor-over-cap.json",
          "https://pricempire.com/cs2-marketplaces",
          "http://web.archive.org/web/20260921022459/https://pricempire.com/cs2-marketplaces",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/priceempire-marketplaces.json",
          "https://www.steamanalyst.com/marketplace",
          "http://web.archive.org/web/20260719014552/https://www.steamanalyst.com/marketplace",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-atlas.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json",
          "https://phishdestroy.io/steam_dossier/fr/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/fr/steam_enforcement_evidence.html#case-support-recovery",
          "https://top10.owasp.org/2025/A01_2025-Broken_Access_Control/",
          "http://web.archive.org/web/20260920212535/https://top10.owasp.org/2025/A01_2025-Broken_Access_Control/",
          "https://store.steampowered.com/privacy_agreement/",
          "http://web.archive.org/web/20260921021648/https://store.steampowered.com/privacy_agreement/",
          "https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "http://web.archive.org/web/20250818113925/https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "https://www.dexerto.com/counter-strike-2/valve-saves-hacked-cs2-player-threatened-with-ransom-over-300000-of-rare-stickers-3283135/",
          "https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "http://web.archive.org/web/20220702042821/https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "https://www.kaspersky.com/blog/cs-go-two-million-usd-inventory-hack/44697/",
          "https://esportfire.com/article/the-2-million-usd-csgo-hack-22062022",
          "http://web.archive.org/web/20260515110250/https://esportfire.com/article/the-2-million-usd-csgo-hack-22062022",
          "https://esportsbetting.com/valve-deletes-130000-stolen-dragon-lore/",
          "https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "http://web.archive.org/web/20251115173120/https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "https://vkplay.ru/media/news/bloger-rasskazal-kak-podderzhka-steam-vorovala-akkaunty-igrokov/",
          "https://lis-skins.com/ru/blog/krupneisaia-mosenniceskaia-sxema-v-istorii-steam/",
          "https://escorenews.com/ru/csgo/news/44056-sotrudniki-podderjki-steam-zanimalis-krajey-skinov-s-akkauntov-za-god-oni-zarabotali-svyshe-300-tysyach-dollarov",
          "https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "http://web.archive.org/web/20250805141942/https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/outsourcing-archive-records.json",
          "https://community.skin.club/en/news/collector-has-steam-inventory-returned-after-bold-hack",
          "https://esportfire.com/article/300k-scam-full-katowice-2014-holo-collection-hacked",
          "http://web.archive.org/web/20251217072445/https://esportfire.com/article/300k-scam-full-katowice-2014-holo-collection-hacked",
          "https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng",
          "http://web.archive.org/web/20260920024236/https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng",
          "https://ag.ny.gov/press-release/2026/attorney-general-james-sues-game-developer-promoting-illegal-gambling-through",
          "http://web.archive.org/web/20260901015430/https://ag.ny.gov/press-release/2026/attorney-general-james-sues-game-developer-promoting-illegal-gambling-through",
          "https://www.fincen.gov/sites/default/files/2019-05/FinCEN%20CVC%20Guidance%20FINAL.pdf",
          "http://web.archive.org/web/20250711185007/https://www.fincen.gov/sites/default/files/2019-05/FinCEN%20CVC%20Guidance%20FINAL.pdf",
          "https://eur-lex.europa.eu/legal-content/EN/LSU/?uri=CELEX:32018L1673",
          "https://eur-lex.europa.eu/eli/dir/2024/1640/oj/eng",
          "http://web.archive.org/web/20260830153004/https://eur-lex.europa.eu/eli/dir/2024/1640/oj/eng",
          "https://eur-lex.europa.eu/eli/reg/2022/2065/oj/eng",
          "http://web.archive.org/web/20260920080125/https://eur-lex.europa.eu/eli/reg/2022/2065/oj/eng",
          "https://phishdestroy.io/steam_dossier/fr/legal_analysis.html",
          "https://partner.steamgames.com/doc/features/auth#website",
          "http://web.archive.org/web/20260921022335/https://partner.steamgames.com/doc/features/auth",
          "https://www.ftc.gov/legal-library/browse/rules/childrens-online-privacy-protection-rule-coppa",
          "http://web.archive.org/web/20260921070051/https://www.ftc.gov/legal-library/browse/rules/childrens-online-privacy-protection-rule-coppa",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/gdpr-ticket-1.png",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/screenshot-manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/gdpr-ticket-2.png",
          "https://datenschutz.hamburg.de/beschwerde",
          "https://edpb.europa.eu/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/regulatory-review/disclosure-audit.json",
          "https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "http://web.archive.org/web/20260821155801/https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "https://phishdestroy.io/steam_dossier/fr/index#exhibit-gallery-section",
          "https://github.com/ValveSoftware/steam-for-linux/issues/4521",
          "https://phishdestroy.io/steam_dossier/fr/steam_evidence_archive.html?source=GitHub&record=484",
          "https://github.com/ValveSoftware/steam-for-linux/issues/6459",
          "http://web.archive.org/web/20260419051343/https://github.com/ValveSoftware/steam-for-linux/issues/6459",
          "https://phishdestroy.io/steam_dossier/fr/steam_evidence_archive.html?source=GitHub&record=467",
          "https://github.com/ValveSoftware/Source-1-Games/issues/3857",
          "https://phishdestroy.io/steam_dossier/fr/steam_evidence_archive.html?source=GitHub&record=768",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "http://web.archive.org/web/20250320082450/https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://phishdestroy.io/steam_dossier/fr/steam_evidence_archive.html?source=Reddit&record=4533",
          "https://www.reddit.com/r/ohnePixel/comments/1hahqx2/permanently_banned_steam_account_without_a_clear/",
          "https://phishdestroy.io/steam_dossier/fr/steam_evidence_archive.html?source=Reddit&record=4766",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://phishdestroy.io/steam_dossier/fr/steam_evidence_archive.html?source=Reddit&record=4592",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/selected-evidence-records.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive_manifest.json",
          "https://phishdestroy.io/steam_dossier/fr/card_economy.html",
          "https://github.com/JustArchiNET/ArchiSteamFarm/wiki/FAQ",
          "https://phishdestroy.io/steam_dossier/fr/card_economy.html#scale",
          "https://phishdestroy.io/steam_dossier/fr/card_economy.html#licence",
          "https://phishdestroy.io/steam_dossier/fr/enforcement_audit.html",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "http://web.archive.org/web/20260924181709/https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://rdap.verisign.com/com/v1/domain/csgoempire.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoempire.com",
          "https://rdap.verisign.com/com/v1/domain/csgoempirelogin4.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/csgoempire.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustreaper.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustreaper.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/rustreaper.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustly.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustly.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/rustly.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgofast.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgofast.com",
          "https://rdap.verisign.com/com/v1/domain/authtofast.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/csgofast.com.json",
          "https://rdap.verisign.com/com/v1/domain/duelbits.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fduelbits.com",
          "https://rdap.verisign.com/com/v1/domain/switchflips.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/duelbits.com.json",
          "https://rdap.verisign.com/com/v1/domain/farmskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffarmskins.com",
          "https://tld-rdap.verisign.com/cc/v1/domain/kobal.cc",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/farmskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoluck.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoluck.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/csgoluck.com.json",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/domain-registry/insane.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Finsane.gg",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/insane.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs2skin.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs2skin.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/cs2skin.com.json",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/domain-registry/juice.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fjuice.gg",
          "https://rdap.verisign.com/com/v1/domain/letmeinjuice.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/juice.gg.json",
          "https://rdap.verisign.com/com/v1/domain/ggdrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fggdrop.com",
          "https://rdap.verisign.com/com/v1/domain/ggauth.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/ggdrop.com.json",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/domain-registry/howl.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhowl.gg",
          "https://rdap.radix.host/rdap/domain/howl.uno",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/howl.gg.json",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/domain-registry/chicken.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fchicken.gg",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/chicken.gg.json",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/domain-registry/csgocasino.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgocasino.gg",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/csgocasino.gg.json",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/domain-registry/hunt.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhunt.gg",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/hunt.gg.json",
          "https://rdap.verisign.com/com/v1/domain/csbattle.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsbattle.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/csbattle.com.json",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/domain-registry/skinrave.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinrave.gg",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/skinrave.gg.json",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/domain-registry/csdouble.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsdouble.gg",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/csdouble.gg.json",
          "https://rdap.verisign.com/com/v1/domain/rustchance.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustchance.com",
          "https://rdap.verisign.com/com/v1/domain/hgfuihd.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/rustchance.com.json",
          "https://rdap.radix.host/rdap/domain/cobaltlab.tech",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcobaltlab.tech",
          "https://rdap.verisign.com/com/v1/domain/cobaltauth.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/cobaltlab.tech.json",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/domain-registry/raided.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fraided.gg",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/raided.gg.json",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/domain-registry/rustneo.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustneo.gg",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/rustneo.gg.json",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/domain-registry/splits.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsplits.gg",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/splits.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/upgrader.pro",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fupgrader.pro",
          "https://rdap.radix.host/rdap/domain/upgauth.space",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/upgrader.pro.json",
          "https://rdap.centralnic.com/fans/domain/skin.fans",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.fans",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/skin.fans.json",
          "https://rdap.nic.one/domain/hotpizza.one",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhotpizza.one",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/hotpizza.one.json",
          "https://rdap.verisign.com/com/v1/domain/g4skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg4skins.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/g4skins.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2royal.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2royal.com",
          "https://rdap.verisign.com/com/v1/domain/tf2auth.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/tf2royal.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2hunt.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2hunt.com",
          "https://rdap.verisign.com/com/v1/domain/rstspcl.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/tf2hunt.com.json",
          "https://rdap.identitydigital.services/rdap/domain/tf2.bet",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2.bet",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/tf2.bet.json",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/domain-registry/openstars.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fopenstars.gg",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/openstars.gg.json",
          "https://rdap.verisign.com/com/v1/domain/skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/skins.com.json",
          "https://rdap.identitydigital.services/rdap/domain/white.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwhite.market",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/white.market.json",
          "https://rdap.identitydigital.services/rdap/domain/moon.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmoon.market",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/moon.market.json",
          "https://rdap.verisign.com/com/v1/domain/csfloat.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsfloat.com",
          "https://rdap.verisign.com/com/v1/domain/csgofloat.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/csfloat.com.json",
          "https://rdap.identitydigital.services/rdap/domain/skin.land",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.land",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/skin.land.json",
          "https://rdap.verisign.com/com/v1/domain/haloskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhaloskins.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/haloskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/163.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuff.163.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/buff.163.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmarket.csgo.com",
          "https://rdap.verisign.com/net/v1/domain/dota2.net",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/market.csgo.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinport.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinport.com",
          "https://pubapi.registry.google/rdap/domain/skinport.app",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/skinport.com.json",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/domain-registry/skinflow.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinflow.gg",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/skinflow.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/skin.place",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.place",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/skin.place.json",
          "https://rdap.verisign.com/com/v1/domain/skinsmonkey.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinsmonkey.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/skinsmonkey.com.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbaron.de",
          "https://rdap.verisign.com/com/v1/domain/skinbaron.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/skinbaron.de.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frust.tm",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/rust.tm.json",
          "https://rdap.verisign.com/com/v1/domain/pirateswap.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fpirateswap.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/pirateswap.com.json",
          "https://rdap.radix.host/rdap/domain/mannco.store",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmannco.store",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/mannco.store.json",
          "https://rdap.verisign.com/com/v1/domain/skinswap.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinswap.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/skinswap.com.json",
          "https://rdap.verisign.com/com/v1/domain/exeskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fexeskins.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/exeskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/balticskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbalticskins.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/balticskins.com.json",
          "https://rdap.nic.trade/domain/cs.trade",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.trade",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/cs.trade.json",
          "https://rdap.verisign.com/com/v1/domain/rapidskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frapidskins.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/rapidskins.com.json",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/domain-registry/tradeit.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftradeit.gg",
          "https://rdap.verisign.com/com/v1/domain/connect-tradeit.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/tradeit.gg.json",
          "https://rdap.verisign.com/com/v1/domain/49skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F49skins.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/49skins.com.json",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/domain-registry/skinvault.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinvault.gg",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/skinvault.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/aim.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Faim.market",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/aim.market.json",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/domain-registry/skinout.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinout.gg",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/skinout.gg.json",
          "https://rdap.verisign.com/com/v1/domain/ntskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fntskins.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/ntskins.com.json",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/domain-registry/gamerpay.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamerpay.gg",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/gamerpay.gg.json",
          "https://rdap.nic.tf/domain/scrap.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fscrap.tf",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/scrap.tf.json",
          "https://rdap.nic.tf/domain/marketplace.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmarketplace.tf",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/marketplace.tf.json",
          "https://rdap.identitydigital.services/rdap/domain/skins.cash",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.cash",
          "https://rdap.identitydigital.services/rdap/domain/skinscash.live",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/skins.cash.json",
          "https://rdap.verisign.com/net/v1/domain/csgo.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo.net",
          "https://rdap.verisign.com/net/v1/domain/easylot.net",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/csgo.net.json",
          "https://rdap.verisign.com/net/v1/domain/cybershoke.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcybershoke.net",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/cybershoke.net.json",
          "https://rdap.verisign.com/net/v1/domain/fastcup.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffastcup.net",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/fastcup.net.json",
          "https://rdap.verisign.com/com/v1/domain/leetify.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fleetify.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/leetify.com.json",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/domain-registry/scope.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fscope.gg",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/scope.gg.json",
          "https://rdap.verisign.com/com/v1/domain/tradeupspy.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftradeupspy.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/tradeupspy.com.json",
          "https://rdap.identitydigital.services/rdap/domain/cs.deals",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.deals",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/cs.deals.json",
          "https://rdap.verisign.com/com/v1/domain/pricempire.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fpricempire.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/pricempire.com.json",
          "https://rdap.identitydigital.services/rdap/domain/lzt.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flzt.market",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/lzt.market.json",
          "https://rdap.verisign.com/com/v1/domain/z2u.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fz2u.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/z2u.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoroll.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoroll.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/csgoroll.com.json",
          "https://rdap.verisign.com/com/v1/domain/rollbit.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frollbit.com",
          "https://rdap.verisign.com/com/v1/domain/rbsnin.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/rollbit.com.json",
          "https://rdap.identitydigital.services/rdap/domain/500.casino",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F500.casino",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/500.casino.json",
          "https://rdap.verisign.com/com/v1/domain/csgobig.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgobig.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/csgobig.com.json",
          "https://rdap.verisign.com/com/v1/domain/casedrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcasedrop.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/casedrop.com.json",
          "https://rdap.verisign.com/com/v1/domain/banditcamp.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbanditcamp.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/banditcamp.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinbox.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbox.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/skinbox.com.json",
          "https://rdap.verisign.com/com/v1/domain/tastydrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftastydrop.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/tastydrop.com.json",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/domain-registry/csgopolygon.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgopolygon.gg",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/csgopolygon.gg.json",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/domain-registry/magicdrop.ru.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmagicdrop.ru",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/magicdrop.ru.json",
          "https://rdap.verisign.com/com/v1/domain/csdice.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsdice.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/csdice.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinodds.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinodds.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/skinodds.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgowin.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgowin.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/csgowin.com.json",
          "https://rdap.verisign.com/net/v1/domain/csgorun.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgorun.net",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/csgorun.net.json",
          "https://rdap.verisign.com/com/v1/domain/openskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fopenskins.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/openskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustbet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustbet.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/rustbet.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgomagic.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgomagic.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/csgomagic.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgobounty.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgobounty.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/csgobounty.com.json",
          "https://rdap.verisign.com/com/v1/domain/ezskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fezskins.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/ezskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustcases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustcases.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/rustcases.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoreaper.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoreaper.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/csgoreaper.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgocases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgocases.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/csgocases.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo-skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo-skins.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/csgo-skins.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgonet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgonet.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/csgonet.com.json",
          "https://rdap.verisign.com/com/v1/domain/wtfskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwtfskins.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/wtfskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/flamecases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fflamecases.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/flamecases.com.json",
          "https://rdap.verisign.com/com/v1/domain/gamedom.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamedom.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/gamedom.com.json",
          "https://rdap.nic.club/domain/skin.club",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.club",
          "https://rdap.verisign.com/net/v1/domain/sc-auth.net",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/skin.club.json",
          "https://rdap.verisign.com/com/v1/domain/daddyskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdaddyskins.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/daddyskins.com.json",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/domain-registry/rustix.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustix.gg",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/rustix.gg.json",
          "https://rdap.nic.club/domain/skins.club",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.club",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/skins.club.json",
          "https://rdap.publicinterestregistry.org/rdap/domain/csgohouse.org",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgohouse.org",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/csgohouse.org.json",
          "https://rdap.verisign.com/net/v1/domain/skinrave.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinrave.net",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/skinrave.net.json",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/domain-registry/bloodycase.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbloodycase.gg",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/bloodycase.gg.json",
          "https://rdap.verisign.com/com/v1/domain/csgoclicker.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoclicker.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/csgoclicker.com.json",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/domain-registry/rustbet.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustbet.gg",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/rustbet.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs-drop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs-drop.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/cs-drop.com.json",
          "https://rdap.verisign.com/net/v1/domain/hellstore.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhellstore.net",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/hellstore.net.json",
          "https://rdap.verisign.com/com/v1/domain/rustloot.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustloot.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/rustloot.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo-case.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo-case.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/csgo-case.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgogem.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgogem.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/csgogem.com.json",
          "https://rdap.verisign.com/com/v1/domain/rainbet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frainbet.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/rainbet.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustclash.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustclash.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/rustclash.com.json",
          "https://rdap.identitydigital.services/rdap/domain/12cs.fail",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F12cs.fail",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/12cs.fail.json",
          "https://rdap.verisign.com/com/v1/domain/tf2easy.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwww.tf2easy.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/tf2easy.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2blaze.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2blaze.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/tf2blaze.com.json",
          "https://rdap.verisign.com/com/v1/domain/shuffle.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fshuffle.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/shuffle.com.json",
          "https://rdap.identitydigital.services/rdap/domain/buff.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuff.market",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/buff.market.json",
          "https://rdap.identitydigital.services/rdap/domain/avan.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Favan.market",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/avan.market.json",
          "https://rdap.identitydigital.services/rdap/domain/cs.money",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.money",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/cs.money.json",
          "https://rdap.verisign.com/com/v1/domain/uuskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fuuskins.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/uuskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/youpin898.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fyoupin898.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/youpin898.com.json",
          "https://rdap.verisign.com/com/v1/domain/c5game.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fc5game.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/c5game.com.json",
          "https://rdap.verisign.com/com/v1/domain/waxpeer.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwaxpeer.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/waxpeer.com.json",
          "https://rdap.verisign.com/com/v1/domain/dmarket.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdmarket.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/dmarket.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamcommunity.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamcommunity.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/steamcommunity.com.json",
          "https://rdap.verisign.com/com/v1/domain/lootfarm.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flootfarm.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/lootfarm.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustskins.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/rustskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/krakatoa.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fkrakatoa.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/krakatoa.com.json",
          "https://rdap.verisign.com/com/v1/domain/shadowpay.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fshadowpay.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/shadowpay.com.json",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/domain-registry/igxe.cn.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Figxe.cn",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/igxe.cn.json",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/domain-registry/swap.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fswap.gg",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/swap.gg.json",
          "https://rdap.verisign.com/com/v1/domain/bitskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbitskins.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/bitskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2mart.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2mart.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/tf2mart.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinbid.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbid.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/skinbid.com.json",
          "https://rdap.verisign.com/com/v1/domain/lootbear.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flootbear.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/lootbear.com.json",
          "https://rdap.nic.tf/domain/backpack.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbackpack.tf",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/backpack.tf.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fstntrading.eu",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/stntrading.eu.json",
          "https://rdap.verisign.com/com/v1/domain/skinwallet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinwallet.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/skinwallet.com.json",
          "https://rdap.verisign.com/com/v1/domain/dota2market.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdota2market.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/dota2market.com.json",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/domain-registry/xplay.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fxplay.gg",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/xplay.gg.json",
          "https://rdap.verisign.com/com/v1/domain/esportal.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fesportal.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/esportal.com.json",
          "https://rdap.registro.br/domain/gamersclub.com.br",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamersclub.com.br",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/gamersclub.com.br.json",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/domain-registry/epidemic.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fepidemic.gg",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/epidemic.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs2stash.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs2stash.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/cs2stash.com.json",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/domain-registry/csgoskins.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoskins.gg",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/csgoskins.gg.json",
          "https://rdap.verisign.com/com/v1/domain/steamanalyst.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamanalyst.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/steamanalyst.com.json",
          "https://rdap.verisign.com/net/v1/domain/steamcardexchange.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamcardexchange.net",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/steamcardexchange.net.json",
          "https://rdap.verisign.com/com/v1/domain/dotabuff.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdotabuff.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/dotabuff.com.json",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/domain-registry/tracker.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftracker.gg",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/tracker.gg.json",
          "https://rdap.verisign.com/com/v1/domain/funpay.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffunpay.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/funpay.com.json",
          "https://rdap.verisign.com/com/v1/domain/playerauctions.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fplayerauctions.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/playerauctions.com.json",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/domain-registry/eldorado.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Feldorado.gg",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/eldorado.gg.json",
          "https://rdap.verisign.com/com/v1/domain/g2a.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg2a.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/g2a.com.json",
          "https://rdap.verisign.com/net/v1/domain/kinguin.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fkinguin.net",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/kinguin.net.json",
          "https://rdap.verisign.com/com/v1/domain/g2g.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg2g.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/g2g.com.json",
          "https://rdap.verisign.com/com/v1/domain/playerup.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fplayerup.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/playerup.com.json",
          "https://rdap.verisign.com/net/v1/domain/smurfhub.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfhub.net",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/smurfhub.net.json",
          "https://rdap.verisign.com/com/v1/domain/smurfaccounts.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfaccounts.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/smurfaccounts.com.json",
          "https://rdap.verisign.com/com/v1/domain/buycsgorank.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuycsgorank.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/buycsgorank.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgosmurfkings.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgosmurfkings.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/csgosmurfkings.com.json",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/domain-registry/smurfstore.co.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfstore.co",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/smurfstore.co.json",
          "https://rdap.verisign.com/com/v1/domain/steamlvlup.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlvlup.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/steamlvlup.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamlevels.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlevels.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/steamlevels.com.json",
          "https://rdap.verisign.com/com/v1/domain/levelsteam.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flevelsteam.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/levelsteam.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamlevelu.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlevelu.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/steamlevelu.com.json",
          "https://rdap.verisign.com/com/v1/domain/eloking.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Feloking.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/eloking.com.json",
          "https://rdap.publicinterestregistry.org/rdap/domain/boosteria.org",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fboosteria.org",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/boosteria.org.json",
          "https://rdap.verisign.com/com/v1/domain/overgear.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fovergear.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/overgear.com.json",
          "https://rdap.verisign.com/com/v1/domain/blazingboost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fblazingboost.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/blazingboost.com.json",
          "https://rdap.verisign.com/com/v1/domain/dota2boost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdota2boost.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/dota2boost.com.json",
          "https://rdap.verisign.com/com/v1/domain/buyboost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuyboost.com",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit/buyboost.com.json",
          "https://phishdestroy.io/steam_dossier/fr/steam_tos_assets/auth-route-audit.json",
          "https://help.steampowered.com/en/faqs/view/365F-4BEE-2AE2-7BDD",
          "https://store.steampowered.com/privacy_agreement/#8",
          "https://www.edpb.europa.eu/system/files/2023-04/edpb_guidelines_202201_data_subject_rights_access_v2_en.pdf",
          "https://web.archive.org/web/20260810154631/https://store.steampowered.com/stats/support",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/design-review/part2/measurements.json",
          "https://phishdestroy.io/steam_dossier/fr/VALVE_EVIDENCE_PACK/databases/TOTAL_VALVE_SCANDALS_MASTER_DB.csv",
          "https://phishdestroy.io/steam_dossier/fr/license_disclaimer.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/fr/index.content.json",
      "export_json_sha256": "4274eb8ab5b2067817d250b28b9ccaa6e9933d2597f1df6ad41dbaeaf5a0ea72"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "fr/investigation_part2.html",
      "language": "fr",
      "title": "Accès aux comptes et responsabilité — Le dossier Steam",
      "source_url": "https://phishdestroy.io/steam_dossier/fr/investigation_part2",
      "source_html_sha256": "203be1af496b27a021c2f614ce9177336b93950dfd35ad68b5f4dfd0384c5b3f",
      "exported_at": "2026-09-29T00:17:35.822Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "investigation_part2.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/fr/investigation_part2.pdf?v=print-20260929-v5",
        "sha256": "45f823615cab8f81bb38b12045035d31c076af542edb60466dc759f063b29656",
        "bytes": 126565,
        "pages": 9
      },
      "integrity": {
        "signed_object": "investigation_part2.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "investigation_part2.content.json.asc",
        "digest_file": "investigation_part2.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify investigation_part2.content.json.asc investigation_part2.content.json",
          "sha256sum -c investigation_part2.content.json.sha256"
        ]
      },
      "content": {
        "text": "LE DOSSIER STEAM / II\n\nVotre compte.Leur accès.Qui répond ?\n\nAutomatisation des services publics. Externalisation de l'assistance. Et ce sont les citoyens qui en font les frais.\n\nSuivez l'évolution des infrastructures, les pertes signalées et les documents à l'origine des réclamations.\n\nCartographier l'infrastructure ↘\nANNEXE 01 / SURVEILLANCE EN TEMPS RÉEL DU MARCHÉ PARALLÈLE550,000+\n\nSteam comptes actuellement en vente sur FSB Market (nom anonymisé ; le nom d’origine n’est pas indiqué ici)\nen ce moment même\n\n550,000+ STOCK EN TEMPS RÉEL · 231,829 DANS LE CORPUS HISTORIQUE EXTRAIT (198,320 JOURNAUX DE STEALER)\n\nLa principale plateforme souterraine de recueil des comptes Steam piratés, FSB Market (autres noms associés non divulgués) authentifie à la fois les acheteurs et les vendeurs à l'aide de l'OpenID officiel Valve de Steam (openid.realm = https://FSB Market). À chaque instant, plus d’un demi-million de comptes volés ou compromis (journaux de vol provenant de RedLine/Lumma, captures issues d’hameçonnage, « credential stuffing ») sont activement mis en vente pour quelques centimes ($0.50–$2.00). Ni FSB Market ni le forum associé est bloqué par le filtre de liens de Valve. Il s’agit du réservoir industriel alimentant les 63.06% comptes de bots payants que Valve bannit sans venir en aide à la victime.\n\nDonnées en temps réel : surveillance du marché noir (plus de 550 000 utilisateurs en ligne) ↗ · Ouvrir la fiche de saisie ↗ · Ouvrir la trace du filtre de liens ↗Plus de 550 000 en direct\n\n01 / UN ÉCOSYSTÈME AVEC DES AUTEURS\n\nL'automatisation aune trace écrite.\n\nProjets nommés. Fonctionnalités publiées. Retracez l'origine d'un outil jusqu'à sa documentation, puis examinez les relations entre développeurs ainsi recensées.\n\n252RÉPERTOIRES RECUEILLIS\n3,320PROFILS GITHUB\n4,214PAIRES PROFIL-RÉFÉRENTIEL\nValve infrastructuresBibliothèques municipalesApplications réutilisables\nLes lignes indiquent les intégrations ou les dépendances documentées. Sélectionnez un nœud pour suivre sa traçabilité.\n\nAutomatisation multi-comptes / JustArchiNET\n\nArchiSteamFarm\n\nLe projet vante explicitement la possibilité de « farmer » des cartes simultanément sur plusieurs comptes Steam. Son fichier de projet mentionne une dépendance à SteamKit2.\n\nConsultez la documentation du projet ↗\n\nSteamKit → ArchiSteamFarm\ndépendance déclarée ↗\n\nRELATIONS RASSEMBLÉES\n\n40 étiquettes des contributeurs · 40 étiquettes « forker »\n\nExemple de contributeur ci-dessous. Ces mentions décrivent la relation avec le dépôt, et non une relation de travail ou d’approbation.\n\n@JustArchi@renovate[bot]@JustArchi-ArchiBot@dependabot-preview[bot]@renovate-bot@actions-user@dependabot-support@Abrynos\nCe que montre le graphique des développeurs\n\nLe graphique met en évidence les relations entre les contributeurs et les auteurs de forks publiés, d’une part, et les projets cités ainsi que les profils GitHub, d’autre part. Il s’agit de données publiques : forks de dépôts, listes de contributions, associations de profils. La question porte sur ce que la trace écrite des capacités publiées et des relations entre développeurs exige que Valve réponde, et non sur ce que cette enquête a inventé. Les hachages des sources sont enregistrés dans le provenance de la carte.\n\nDécouvrez l'ensemble du réseau ↗Données source du référentiel ↓\n\n02 / DES QUALIFICATIONS DIFFÉRENTES. DES POUVOIRS DIFFÉRENTS.\n\nQuelle touche ?De quoi parlons-nous ?\n\nPour jouer à un jeu, le joueur n'a pas besoin de fournir une clé API Web personnelle. C'est là le point central de cette enquête.\n\n01 / COMPTE UTILISATEUR\nClé API Web personnelle\nsteamcommunity.com/dev/apikey\n\nÉmises à partir d'un compte utilisateur pour les appels API autorisés. La création, la visibilité, la révocation et la détection des abus liés aux clés relèvent de la sécurité du compte.\n\n02 / BACKEND DU JEU\nClé API Web de l'éditeur\n\nLes partenaires de Steamworks utilisent les identifiants de l'éditeur pour les opérations de gestion en arrière-plan prises en charge, y compris les services liés aux jeux. La clé personnelle d'un joueur constitue un identifiant distinct.\n\n03 / IDENTITÉ ET SESSION\nOpenID / jetons de session\n\nOpenID permet de confirmer l'identité auprès d'un site web. Un jeton de session ou d'actualisation Steam a une finalité différente. Ces mécanismes ne doivent pas être présentés comme une seule et même « clé API » interchangeable.\n\nValve répertorie à la fois les clés API Web des utilisateurs et celles des éditeurs. L'API Web dans son ensemble n'est donc pas distincte de Steamworks. Documentation sur les clés API ↗ archivé 2026-09-15 ↗ · Authentification pendant une session de jeu ↗ archivé 2026-08-29 ↗\n\nDOCUMENTÉ PAR L'AUTEUR DE L'OUTIL / MARS 2024\n\nL'automatisation peut utiliser autre chose qu'une clé API.\n\nLe wiki du Trade Offer Manager décrit l'utilisation d'un jeton d'accès de session pour certaines parties de l'API Web lorsqu'il n'existe pas de clé API distincte. Il mentionne également la confirmation par mobile pour la création de clés à partir de fin 2023. Le responsable de la maintenance précise que cette utilisation du jeton n'est pas prise en charge par Valve ; il s'agit d'une affirmation obsolète figurant dans la documentation, et non d'un test de contournement en conditions réelles.\n\nConsultez les explications du responsable de la maintenance ↗ archivé 2026-09-24 ↗\n\nL'ASPECT HUMAIN / UN EXEMPLE ILLUSTRATIF DE PARCOURS DE PHISHING\n\nJe joue toujours.Déjà révélé.\n\nUn message d'un ami. Une invitation à voter. Une page de remerciement. Pour le joueur, la tâche est terminée. Une session piratée peut toutefois se prolonger au-delà de ce moment.\n\nSUR L'ÉCRAN DU JOUEUR\n\nF\nLE RÉCIT D’UN AMI\n\n« Pouvez-vous voter pour notre équipe ? »\n\nLa demande est envoyée via le chat d'Steampar un compte connu. Dans ce cas de figure, la page associée s'ouvre dans le navigateur du client.\n\nHORS DE VUE\n\nLa confiance vient avant le site web.\n\nLe compte piraté d’un ami peut renforcer la crédibilité d’un lien de hameçonnage. L’interface Steam qui l’entoure ne certifie pas le site Web de destination.\n\nEXPÉDITEUR CONNU / DESTINATION EXTERNE\nLa sécurité du compte est la priorité absolue avant toute vente.\n\nLe joueur n'avait pas l'intention de créer un identifiant d'automatisation ni de déléguer le contrôle. Le fait de se reconnecter à un jeu ne prouve pas que le compte est sécurisé. Valve conserve les journaux de session, l'historique de création des clés API et les données de corrélation des appareils. Ce n'est pas le cas de la victime. C'est cette asymétrie qui pose le problème de la responsabilité.\n\nAccès aux sessions et types d'identifiants\n\nUne clé API et une session connectée sont des identifiants distincts dotés de capacités différentes. La révocation d’une clé ne met pas fin à une session active. La documentation de Valve décrit ces deux éléments ; Valve conserve les journaux qui permettraient de déterminer quel identifiant était actif au moment de toute action contestée. Ce qui est demandé, c’est la divulgation de cet enregistrement — et non une déduction inventée par l’enquête. Documentation du responsable concernant la gestion des jetons ↗ archivé 2026-09-24 ↗ · Valve documentation clé ↗ archivé 2026-09-15 ↗\n\n03 / LE MARCHÉ OFFICIEL EST SOUMIS À UN PLAFOND\n\nCet objet peut être rare.La limite reste en vigueur.\n\nUn prix supérieur au plafond de cotation ne peut être obtenu par le biais d'une seule cotation sur le Marché communautaire à ce prix plein.\n\nPRIX DEMANDÉ À TITRE INDICATIF$5,000Modifier le prix demandé pour l'article\n$100$20,000\n\nIl s'agit d'une illustration de la limite publiée, et non d'une évaluation ni d'une recommandation d'opération.\n\nPLAFOND D'INSCRIPTION≈ $1,800\nCASQUETTE DE PORTEFEUILLE≈ $2,000\n\nAu-delà du plafond de cotation publié.\n\nLes fonds du portefeuille ne peuvent pas être retirés vers un compte bancaire. Ces contraintes génèrent une demande à laquelle répondent les marchés de skins tiers : une demande créée par les limites d'inscription et de portefeuille, alors que les règles propres à Valve interdisent aux opérateurs commerciaux d'y répondre.\n\nLimites du marché de Steam ↗ archivé 2026-09-21 ↗\n\n04 / À L'INTÉRIEUR DE LA ZONE D'ASSISTANCE\n\nChargés de la gestion des données.Responsable de l'accès.\n\nLa politique de confidentialité de Valve prévoit expressément le partage de données à caractère personnel avec des prestataires de services d'assistance tiers, dans la mesure où cela est nécessaire à la fourniture de ces services.\n\nLE JOUEURCompte et justificatifs\n→\nSOUPAPEProcessus de rétablissement\n→\nPRESTATAIRE DE SOUTIENAccès délégué\n\nPolitique de confidentialité §5.2 ↗ · La politique interne de Valve autorise l'accès de tiers à des fins d'assistance. Les questions qui restent en suspens sont les suivantes : quelles autorisations ont été accordées, quelles pistes d'audit existent et que s'est-il passé lorsque cet accès aurait fait l'objet d'un abus ?\n\n2015\nLa balance était accessible au public\n\nValve a reconnu que des vols de comptes avaient eu lieu à grande échelle et a présenté les mesures de protection mises en place.\n\nValve publication ↗archivé 2026-08-09 ↗\n2015\nValve a externalisé ce service — et l'a dit clairement\n\nValve dispose d'une petite équipe interne Steam chargée de l'encadrement du support et l'a déclaré « a fait appel à plusieurs entreprises différentes » pour assurer le service d'assistance (Erik Johnson, Valve, à Kotaku) ; son article 5.2 de la politique de confidentialité autorise ces tiers à accéder aux données des utilisateurs. Quel prestataire dispose d'un accès pour la récupération de compte ? Valve ne l'a jamais révélé. — Les discussions au sein de la communauté mentionnent des prestataires tels que Concentrix, mais aucun n’a été Valve-confirmé. Le service externalisé était déjà en place plusieurs années avant les deux aveux mentionnés ci-dessous.\n\nKotaku : Valve concernant son assistance ↗archivé 2025-07-11 ↗\n2023\nLa première admission\n\nL'équipe CS:GO de Valve assume par écrit la responsabilité de la compromission d'un compte survenue via son propre processus de demande d'aide, et annule les échanges.\n\nOuvrir le dossier d'externalisation ↓\n2025\nLa deuxième admission\n\n33 mois plus tard, le service client Steam indique qu'un technicien « n'a pas respecté notre procédure, ce qui a entraîné la restitution de votre compte à une autre personne ». Même canal. Même résultat.\n\nDexerto, 14 novembre 2025 ↗\n\nDOSSIER / HFB ET LES ACCUSATIONS D'EXTERNALISATION\n\nLa solution résidait dans Steam Support lui-même.Valve l'a déclaré par écrit.\n\nDans la réponse du service client reproduite par Dexerto, l'équipe CS:GO de Valve assume la responsabilité de la compromission d'un compte via la procédure de demande d'aide — son propre canal, et non une page de hameçonnage ni l’utilisateur. Les articles ont été récupérés et les transactions annulées, ce qui constitue la solution que Valve affirme aux autres victimes ne pas exister. Le stock de HFB a été estimé à $2,000,000+ le jour même et $3,000,000+ dans le suivi ; Qkss a perdu $1,000,000+ de la même manière et n'a rien obtenu.\n\nRÉPONSE DU SERVICE D'ASSISTANCE / REPRODUIT PAR DEXERTO · 21 FÉVRIER 2023\n« compromis à la suite d'une demande d'assistance, dont l'équipe CS:GO assume la responsabilité »\nLire l'article et le message reproduit ↗ archivé 2025-08-18 ↗\n01 / QUELLE SOUPAPE A PERMIS\nC'est par son propre canal d'assistance qu'il a pu y accéder\n\nLa réponse porte sur le compte piraté et l'annulation des transactions associées. Valve les a annulées — ces transactions étaient donc annulables. Le ticket authentifié d'origine ne figure pas dans cette collection.\n\n02 / CE QUE LES LICENCIEMENTS N'ONT PAS RÉGLÉ\nCette même porte s'est ouverte à nouveau en novembre 2025\n\nLe prestataire a licencié l'ensemble de son équipe d'assistance Steam — selon une information rapportée par Mzkshow via Dexerto, et non pas par un communiqué officiel du personnel Valve. Trente-trois mois plus tard Steam, le service d’assistance a écrit à un autre collecteur pour lui indiquer qu’« un technicien d’assistance chargé de traiter la demande d’aide n’avait pas respecté notre procédure, ce qui a entraîné la restauration de votre compte au nom d’une autre personne ». Citation tirée de Valve lui-même, concernant ce même canal.\n\nDeuxième admission, le 14 novembre 2025 ↗\n03 / QU'EST-CE QUE L'OPEN ?\nValve n'a jamais révélé le nom de l'entrepreneur\n\nNi l'identité du prestataire ni celle du lieu ne sont précisées dans ces sources. Il ne s'agit pas d'une lacune dans le reportage, mais d'une information que Valve n'a pas divulguée concernant les personnes ayant eu accès aux comptes des utilisateurs.\n\nCompte rendu de l'époque sur cette affaire ↗\n\nTrois questions auxquelles Valve n'a pas répondu : qui aurait pu contourner la procédure de récupération de compte, quelles ont été les conclusions de l'audit d'accès et quels changements ont été apportés par la suite.\n\nAllégations ultérieures figurant dans les archives de soutien conservées\n\nDeux publications sur Reddit datant de 2024 font état d’autres enquêtes menées par Mzkshow : une affaire de levée d’une suspension « VAC » en juillet 2024 et une affaire d’inventaire « $13,000 » en décembre 2024. Il s’agit d’incidents signalés séparément. La question de la responsabilité est identique dans chaque cas : qui disposait d’un accès prioritaire, qu’a révélé l’audit et quels changements ont été apportés ?\n\n14 juillet 2024 · rétablissement signalé / cas de VAC-ban ↗2 décembre 2024 · signalé $13,000 cas d'inventaire ↗archivé 2025-08-05 ↗Deux poteaux conservés, lignes de source et hachages ↓\n\n05 / SUIVRE LA PERTE\n\nChaque montantIl faut un étui.\n\nDix cas, de juin 2022 à mars 2026. Chaque montant correspond au chiffre publié par la source mentionnée — $6,300,000, $2,000,000+, $1,000,000+, ≈$320,000, ≈$300,000, et jusqu'à 288 €. Valve conserve le journal des transactions, l'historique des sessions et la piste d'audit de l'assistance pour chacune d'entre elles, et n'a fourni aucun de ces documents.\n\nCANAL D'ASSISTANCE21 2022 JUIN\n$2,000,000+\nHFB — the largest inventory in the game\n\nÉVALUATION DES STOCKS DÉCLARÉS · PORTEE À PLUS DE3M$ DANS LE SUIVI DU 2023 DE FÉVRIER\n\nSept « Dragon Lores » de collection et le « Blue Gem Karambit » n°1 ; ce couteau à lui seul vaut environ1.26m. Compte inactif depuis trois ans, avec l’authentificateur toujours activé ; e-mail et mot de passe modifiés via la procédure de récupération du service client. Valve a annulé les transactions — et a assumé sa responsabilité par écrit. Avant l’annulation, un montant déclaré de $200,000+ de recettes avait déjà été retiré via market.csgo.com, qui effectue les règlements en espèces et en cryptomonnaies. Une annulation restitue un skin, pas l’argent que quelqu’un a déjà encaissé. L’annulation a également entraîné un dysfonctionnement : un acheteur avait caché son « Souvenir Dragon Lore » dans un espace de stockage du jeu ; le script ne pouvait pas accéder au contenu de ce conteneur, et Valve a dupliqué un objet d’une valeur de130,000 $ lors de l’annulation d’un vol — détecté grâce aux identifiants d’objets et aux signalements de la communauté, supprimé en juillet 2022, ; l’acheteur a été remboursé par BUFF plutôt que par Valve.\n\nDexerto, le jour du vol ↗\nPORTEFEUILLE ET ACHATS07 2022 JUILLET\n>$500\n44 disputed Market purchases\n\nDÉPENSES DÉCLARÉES PAR PORTEFEUILLE · USD\n\nUn utilisateur signale des achats non autorisés d'objets de faible valeur dans Dota 2 ainsi qu'une réponse insatisfaisante du service client.\n\nLire la plainte et consulter les captures d'écran associées ↗\nINTRUSION DANS LA PLATEFORME14 2022 AOÛT\n$6,300,000\nCS.Money — 19,000+ skins provenant des bots\n\nÉVALUATION · PREMIÈRE ESTIMATION :1.6M de dollars\n\nLes pirates ont mis la main sur les fichiers d’authentification mobile des bots de trading de la plateforme et les ont vidés, en transférant une partie du butin à des traders connus afin de brouiller les pistes. Les chercheurs de la communauté ont identifié les comptes des pirates sur 55 en quelques heures. Valve n’a rien annulé — un site tiers se trouve en dehors de Steam, a déclaré le même Steam dont l’inventaire, l’API de trading et le système de comptes ont permis le vol de bout en bout.\n\nLire le récit contemporain ↗\nCANAL D'ASSISTANCEARTICLE PUBLIÉ SUR 21 LE 2023\n$1,000,000+\nQkss — même porte, même acteur, réponse opposée\n\nÉVALUATION DES STOCKS DÉCLARÉS\n\nLe cas de HFB a été traité de la même manière, par le même intervenant, via la même demande d'assistance. HFB avait été entièrement dédommagé huit mois plus tôt. Ce n'était pas le cas de Qkss. D'après les informations rendues publiques, rien ne distingue ces deux cas, si ce n'est l'importance de l'audience concernée.\n\nDexerto à propos de l'enquête sur Mzkshow ↗\nCANAL D'ASSISTANCEPUBLIÉ LE 2023 FÉVRIER\n≈ $320,000\nLe délit d'initié en soi — un an de délit d'initié\n\nCHIFFRE D'AFFAIRES SUR UNE PÉRIODE D'ENVIRON UN AN · IL NE S'AGIT PAS D'UNE ÉVALUATION DES STOCKS\n\nL'accès via le service d'assistance a permis de consulter l'historique du compte remontant jusqu'à 15 ans en arrière : la première clé CD, le premier e-mail, la première carte — exactement les justificatifs requis par la procédure de récupération. Celui qui détient la base de données l’emporte toujours dans ce genre de litige face à celui qui détient le compte. Un M4A4 Howl volé, accompagné d’hologrammes iBUYPOWER et Titan Katowice 2014, s’est vendu pour35,000 et a fini entre les mains de b1t, de l’équipe NAVI, qui n’avait aucun moyen de le savoir. La réponse du sous-traitant a été de licencier tous les employés travaillant au service d’assistancSteam.\n\nEscorenews sur cette même enquête ↗\nPORTEFEUILLE ET ACHATS09 DEC 2023\n€288\nPerte du portefeuille malgré une protection en deux étapes\n\nTRUSTPILOT · INDEX DES SOURCES 16\n\nL'évaluateur signale qu'un compte a été piraté et qu'on a refusé de l'aider concernant les dépenses sur le Market. L'exportation ne comporte pas d'URL d'évaluation individuelle.\n\nVérifier la provenance de la source ↗\nRÉCUPÉRATION DE COMPTE02 DEC 2024\n$13,000\n« Matvey » — deux ans après les licenciements\n\nESTIMATION DES STOCKS PAR L'AUTEUR\n\nLa récupération a été accordée à une personne qui a fourni des données de compte que le titulaire lui-même n'arrivait pas à faire correspondre. Même démarche, même résultat, après que le prestataire eut fermé son service d'assistance Steam.\n\nLire l'allégation conservée ↗\nRÉCUPÉRATION DE COMPTE09 MAI 2025\n≈ $10,000\nRécupération via le billet d’une autre personne\n\nPERTE D'OBJET FAITE OBJET D'UNE RÉCLAMATION · USD\n\nUn utilisateur québécois affirme que le service d'assistance a réinitialisé son mot de passe et supprimé la protection de son compte à la demande d'une autre personne.\n\nLire la plainte rédigée à la première personne ↗\nCANAL D'ASSISTANCE13 NOV 2025\n≈ $300,000\nHawkeye337 — et la deuxième confession écrite d'Valve\n\nCOLLECTION COMPLÈTE « HOLO » DE L'2014 DE KATOWICE\n\nL'attaquant a exigé 1 bitcoins et a commencé à transférer la collection sur des adresses Negev afin de la détruire. Steam Réponse du service d'assistance : « Un technicien du service d'assistance chargé de traiter la demande d'aide n'a pas respecté notre procédure, ce qui a entraîné la restauration de votre compte au profit d'une autre personne. » Trente-trois mois après la première admission, même scénario. Compte rétabli quelques heures après que le fil de discussion soit devenu viral sur X. Qkss n’avait pas une telle audience.\n\nDexerto, 14 Nov 2025 ↗\nPORTEFEUILLE ET ACHATS29 MAR 2026\n$50\nRecharges non autorisées et jeux offerts en cadeau\n\nTRUSTPILOT · INDEX DES SOURCES 290\n\nL'auteur de l'avis fait état de dépenses non autorisées et de demandes de remboursement restées sans suite. L'URL de l'avis en question ne figure pas dans le fichier exporté.\n\nVérifier la provenance de la source ↗\n\nLes sources et les montants restent tels qu'indiqués par chacune d'entre elles. Valve conserve les journaux de transactions, les enregistrements de session et la piste d'audit de support pour chacun de ces cas. Veuillez les fournir. Un message Reddit archivé ne suffit pas à trancher la question — ce sont les propres registres de Valve qui font foi.\n\nLA COLLECTION / APRÈS VÉRIFICATION\n\n231,829 comptes en promotion.Valve contient les journaux de chacun d'entre eux.\n354 → 201\nAvis sur Trustpilot\n\n153 lignes en double ont été supprimées. Les URL des avis individuels n'ont pas été conservées dans le fichier d'exportation.\n\n231,829\nSteam listes de comptes\n\n33,509 classé comme « auto-enregistré » ; 198,320 sous l'étiquette « voleur » du collectionneur. Les annonces ne constituent pas des ventes conclues.\n\nAudit des recouvrements ↓Rechercher dans les archives sources ↗",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Votre compte.Leur accès.Qui répond ?"
          },
          {
            "level": 2,
            "id": null,
            "text": "L'automatisation aune trace écrite."
          },
          {
            "level": 3,
            "id": null,
            "text": "ArchiSteamFarm"
          },
          {
            "level": 2,
            "id": null,
            "text": "Quelle touche ?De quoi parlons-nous ?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Clé API Web personnelle"
          },
          {
            "level": 3,
            "id": null,
            "text": "Clé API Web de l'éditeur"
          },
          {
            "level": 3,
            "id": null,
            "text": "OpenID / jetons de session"
          },
          {
            "level": 3,
            "id": null,
            "text": "L'automatisation peut utiliser autre chose qu'une clé API."
          },
          {
            "level": 2,
            "id": null,
            "text": "Je joue toujours.Déjà révélé."
          },
          {
            "level": 3,
            "id": "session-hidden-title",
            "text": "La confiance vient avant le site web."
          },
          {
            "level": 2,
            "id": null,
            "text": "Cet objet peut être rare.La limite reste en vigueur."
          },
          {
            "level": 2,
            "id": null,
            "text": "Chargés de la gestion des données.Responsable de l'accès."
          },
          {
            "level": 3,
            "id": null,
            "text": "La balance était accessible au public"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve a externalisé ce service — et l'a dit clairement"
          },
          {
            "level": 3,
            "id": null,
            "text": "La première admission"
          },
          {
            "level": 3,
            "id": null,
            "text": "La deuxième admission"
          },
          {
            "level": 3,
            "id": null,
            "text": "La solution résidait dans Steam Support lui-même.Valve l'a déclaré par écrit."
          },
          {
            "level": 4,
            "id": null,
            "text": "C'est par son propre canal d'assistance qu'il a pu y accéder"
          },
          {
            "level": 4,
            "id": null,
            "text": "Cette même porte s'est ouverte à nouveau en novembre 2025"
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve n'a jamais révélé le nom de l'entrepreneur"
          },
          {
            "level": 2,
            "id": null,
            "text": "Chaque montantIl faut un étui."
          },
          {
            "level": 3,
            "id": null,
            "text": "HFB — the largest inventory in the game"
          },
          {
            "level": 3,
            "id": null,
            "text": "44 disputed Market purchases"
          },
          {
            "level": 3,
            "id": null,
            "text": "CS.Money — 19,000+ skins provenant des bots"
          },
          {
            "level": 3,
            "id": null,
            "text": "Qkss — même porte, même acteur, réponse opposée"
          },
          {
            "level": 3,
            "id": null,
            "text": "Le délit d'initié en soi — un an de délit d'initié"
          },
          {
            "level": 3,
            "id": null,
            "text": "Perte du portefeuille malgré une protection en deux étapes"
          },
          {
            "level": 3,
            "id": null,
            "text": "« Matvey » — deux ans après les licenciements"
          },
          {
            "level": 3,
            "id": null,
            "text": "Récupération via le billet d’une autre personne"
          },
          {
            "level": 3,
            "id": null,
            "text": "Hawkeye337 — et la deuxième confession écrite d'Valve"
          },
          {
            "level": 3,
            "id": null,
            "text": "Recharges non autorisées et jeux offerts en cadeau"
          },
          {
            "level": 2,
            "id": null,
            "text": "231,829 comptes en promotion.Valve contient les journaux de chacun d'entre eux."
          },
          {
            "level": 3,
            "id": null,
            "text": "Avis sur Trustpilot"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam listes de comptes"
          }
        ],
        "links": [
          "https://phishdestroy.io/live-intel/?category=steam",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/lzt.market.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-evidence-lzt.json",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://github.com/JustArchiNET/ArchiSteamFarm/blob/main/ArchiSteamFarm/ArchiSteamFarm.csproj",
          "https://github.com/JustArchi",
          "https://github.com/renovate[bot]",
          "https://github.com/JustArchi-ArchiBot",
          "https://github.com/dependabot-preview[bot]",
          "https://github.com/renovate-bot",
          "https://github.com/actions-user",
          "https://github.com/dependabot-support",
          "https://github.com/Abrynos",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/automation-map.json",
          "https://phishdestroy.io/steam_dossier/fr/output_steam_network/network.html",
          "https://phishdestroy.io/steam_dossier/fr/output_steam_network/raw_data.json",
          "https://partner.steamgames.com/doc/webapi_overview/auth",
          "http://web.archive.org/web/20260915025812/https://partner.steamgames.com/doc/webapi_overview/auth",
          "https://partner.steamgames.com/doc/webapi/ISteamUserAuth",
          "http://web.archive.org/web/20260829124950/https://partner.steamgames.com/doc/webapi/ISteamUserAuth",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "http://web.archive.org/web/20260924181824/https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://store.steampowered.com/privacy_agreement/",
          "https://store.steampowered.com/oldnews/19618",
          "http://web.archive.org/web/20260809125516/https://store.steampowered.com/oldnews/19618",
          "https://kotaku.com/valve-explains-why-steam-customer-service-is-still-terr-1736988223",
          "http://web.archive.org/web/20250711004653/https://kotaku.com/valve-explains-why-steam-customer-service-is-still-terr-1736988223",
          "https://www.dexerto.com/counter-strike-2/valve-saves-hacked-cs2-player-threatened-with-ransom-over-300000-of-rare-stickers-3283135/",
          "https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "http://web.archive.org/web/20250818113925/https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "https://lis-skins.com/ru/blog/krupneisaia-mosenniceskaia-sxema-v-istorii-steam/",
          "https://www.reddit.com/r/cs2/comments/1e38jo4/stealing_accounts_and_removing_vac_bans_a_new/",
          "https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "http://web.archive.org/web/20250805141942/https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/outsourcing-archive-records.json",
          "https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "https://escorenews.com/en/csgo/news/44087-valve-steam-support-employee-accused-of-selling-inactive-accounts-inventories-worth-six-figures-b1t-has-one-of-these-skins",
          "https://phishdestroy.io/steam_dossier/fr/PART2_RESEARCH.md",
          "https://www.reddit.com/r/GlobalOffensive/comments/1h56shi/steam_support_is_stealing_accounts/",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/design-review/part2/quality-review.json",
          "https://phishdestroy.io/steam_dossier/fr/steam_evidence_archive.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/fr/investigation_part2.content.json",
      "export_json_sha256": "8dddc4ce31f29f0c6b0a607b5a37a41468f4f831db40892fcb87ba7cdc0054b6"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "fr/legal_analysis.html",
      "language": "fr",
      "title": "Leurs conditions, vos droits — Le dossier «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/fr/legal_analysis",
      "source_html_sha256": "fa8b130e51290ae18f217ca0454456d33ef66e795aca57cde0ed53af4a8723ff",
      "exported_at": "2026-09-29T00:17:36.500Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "legal_analysis.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/fr/legal_analysis.pdf?v=print-20260929-v5",
        "sha256": "017d288dd83f4fb0fa0f33249a7109db3e04b489a17e3a6b40ecce4ac6e859e9",
        "bytes": 108502,
        "pages": 8
      },
      "integrity": {
        "signed_object": "legal_analysis.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "legal_analysis.content.json.asc",
        "digest_file": "legal_analysis.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify legal_analysis.content.json.asc legal_analysis.content.json",
          "sha256sum -c legal_analysis.content.json.sha256"
        ]
      },
      "content": {
        "text": "Rapport juridique et économique\nAnalyse juridique — Conditions générales d'utilisation et conformité réglementaire\n\nLeurs conditions. Vos droits.\n\nCE QUE CETTE SECTION DÉMONTRERA\n\nCet audit juridique et judiciaire évalue l'asymétrie contractuelle entre la société « Valve » et les utilisateurs de « Steam » dans les principales juridictions réglementaires. Il met en évidence la manière dont la licence d’abonnement révocable prive le consommateur de son droit de propriété légal, analyse la jurisprudence de la Cour de justice de l’Union européenne relative à l’épuisement des droits de revente numérique et examine la conformité au titre de la loi sur les services numériques (Digital Services Act, DSA) et de l’article 15. de la loi «GDPR ». L’analyse démontre comment les mécanismes d’application automatisés fonctionnent sans possibilité de recours significatif, tandis que les frais de marché prélevés par les plateformes extraient systématiquement de la valeur économique sur chaque transaction entre particuliers.\n\n← Retour au dossier de synthèse destiné aux dirigeants\n\nLe présent rapport propose une analyse juridique, économique et technique du fossé existant entre les règles déclarées de la plateforme «Steam» et la situation des consommateurs : une application automatisée des règles offrant peu de voies de recours, et un contrôle étendu de l'entreprise sur les actifs numériques. Les chiffres sont accompagnés de leur source ; lorsqu'il n'a pas été possible de remonter à une source primaire, ils ont été omis.\n\n1 de vecteurs\n\nRemplacer la « propriété » par une licence révocable, afin que les actifs numériques puissent être retirés conformément à l'accord.\n\n2 de vecteurs\n\nSystème de contrôle automatisé (VACNet) dont les mesures d'exclusion, selon le site Steam Support, ne peuvent être annulées.\n\n3 de vecteurs\n\nDes contrôles sur les comptes et les actifs, associés à une commission de marché CS2 d'15% (5% Steam + 10% commission d'éditeur) qui réduit la valeur de l'écosystème à chaque revente.\n\nAsymétrie des termes\nDécharge de responsabilité et licence révocable\n2.1 Le modèle de « l'abonnement » face aux droits de propriété\n\nLa section 2 du contrat d'abonnement de l'Steam n'accorde aux utilisateurs qu'un licence personnelle, non exclusive, non transférable et révocable. Conformément aux conditions générales, Valve se réserve le droit de résilier des comptes à tout moment, et les soldes inutilisés du portefeuille Steam peuvent être perdus.\n\n2.2 L'illusion du remboursement face à la directive européenne relative aux droits des consommateurs\nCadre juridique\tMécanisme de remboursement\tLimitation\nEU Consumer Rights Directive\tUnconditional 14-day right of withdrawal on digital content\tWaived if download begins with explicit consumer consent\nSteam SSA\t14 days / under 2 hours played\tValve may deny at its discretion for \"abuse\"\nÉvaluation\n\nValve L'UE subordonne le droit de rétractation légal de 14-jours à sa propre fenêtre de «14 jours / sous 2 heures », que l'utilisateur doit accepter au moment du téléchargement avant de pouvoir évaluer le produit. Cette politique restreint — et non n'étend pas — le droit légal ; la question de savoir si elle le fait légalement relève de l'autorité compétente, et non d'une conclusion avancée ici.\n\nContentieux\nMarché secondaire et droit de la concurrence\nUFC Que Choisir c. Valve — France\n2019\nTribunal de Paris : la doctrine de l'épuisement des droits s'applique aux jeux vidéo — la revente est licite\n2022 d'octobre\nLa Cour d'appel de Paris infirme la décision\n23 2024 d'octobre\nCour de cassation : les jeux vidéo sont des « œuvres complexes » au sens de la directive sur les droits d'auteur et les sociétés de l'information, et non des logiciels. Revente numérique interdit. C'est « Valve » qui l'emporte.\nAffaire antitrust concernant Wolfire Games — États-Unis (Affaire « In re Valve Antitrust Litigation », n° 2:21-cv-00563)\n\nLa clause de « nation la plus favorisée » (PMFN) de la plateforme Valve interdit aux développeurs de vendre des clés « Steam » à un prix inférieur sur toute autre plateforme. Les boutiques concurrentes — même celles qui facturent une commission de 12%, contre 30% sur Valve — ne peuvent pas répercuter cette économie sur les consommateurs.\n\n336Nombre total d'employés d'Valve (2021). Source : pièces versées au dossier.\n79les employés chargés de la gestion de l'ensemble de la plateforme Steam. Source : pièces versées au dossier.\n$3.5Mrésultat net par salarié. Source : pièces versées au dossier.\n\nDes pièces de procédure rendues publiques montrent que 8.5B de chiffre d'affaires brut en 2021 sur les employés d'336. Le 79-équipe «Steam » a géré les demandes d'373,000s et les tickets d'assistance quotidiens en les acheminant vers des centres d'appels externalisés et automatisés.\n\nPIÈCE JUSTE DU DOSSIER NON SCELLÉ · W.D. WASH. AFFAIRE N°2:21-CV-00563Note interne d'information\n\nTim Sweeney (PDG d'Epic Games) à Gabe Newell : « Pourquoi Steam continue-t-il à prélever 30% du chiffre d’affaires alors que le traitement des paiements coûte 2–5% et que la bande passante CDN coûte0.002/$ par Go ? Si l’on exclut les jeux les plus populaires 25 sur Steam, je parie que Valve a réalisé plus de bénéfices sur la plupart des autres titres 1,000 que les développeurs eux-mêmes. »\n\nScott Lynch (directeur des opérations, Valve Corporation) – message interne adressé à Gabe Newell : « T'es en colère, mec ? »\n\nRéponse à une déposition sous serment (Bloomberg, 2026) : En vertu de la règle 30 (b) (1) relative aux dépositions, Gabe Newell a déclaré que «Valve n'a ni pour politique ni pour pratique d'imposer des prix aux éditeurs de logiciels tiers sur d'autres plateformes. » Les plaignants ont confronté Newell à des notes de service internes d’Valves prouvant l’existence d’une politique active de contrôle des prix et de menaces de retrait des listes visant les développeurs pratiquant des prix inférieurs sur des boutiques concurrentes. Fin mars 2026,, la Cour fédérale a rejeté la requête en jugement sommaire d’Valve, renvoyant ainsi le recours collectif des développeurs de l’32,000-devant un jury.\n2024 de novembre\n\nReconnaissance d'un recours collectif concernant ~ Les développeurs de «32,000 » qui a versé des commissions depuis janvier 2017,, ainsi qu’un recours collectif parallèle intenté par des consommateurs.\n\nDommages-intérêts réclamés\n\n$3.1B\nTriplé en vertu de la législation américaine sur la concurrence = $9.3B exposition potentielle.\n\n2026: de juin Une nouvelle action en justice accuse Microsoft et Valve d'avoir conclu un accord de cartel visant à restreindre la concurrence dans le domaine de la distribution de jeux vidéo sur PC.\n\nCriminalité financière et lutte contre le blanchiment d'argent : admission officielle\nValve Déclaration officielle : Liquidations pour fraude à l'échelle mondiale (28 octobre 2019)\n\nLe 28 octobre 2019, Valve a officiellement mis fin à l'échange et à la revente sur les places de marché des clés de conteneurs Counter-Strike nouvellement achetées. Dans son communiqué officiel (blog.counter-strike.net/2019/10/26113), la société «Valve» a reconnu par écrit que l'économie virtuelle qu'elle avait mise en place était devenue une plaque tournante internationale du blanchiment d'argent :\n\n« Auparavant, la plupart des transactions de clés que nous observions concernaient des clients légitimes. Cependant, les réseaux mondiaux de fraude se sont récemment tournés vers l'utilisation de clés CS:GO pour monnayer leurs gains. À l'heure actuelle, on estime que la quasi-totalité des achats de clés qui finissent par être échangés ou vendus sur la place de marché proviennent de sources frauduleuses. »\n\nContexte réglementaire : Cette confession fait suite à l’ultimatum officiel lancé par la Commission des jeux de l’État de Washington (WSGC) à Valve et aux ordonnances de cessation et d’abstention «2016 » émises en juillet par Karl Quackenbush, directeur juridique d’Valve, à l’encontre des domaines de paris sur les skins de 23 (notamment CSGO Lotto, CSGOLounge et OPSkins), et ce, uniquement après qu’une enquête pénale sur les jeux d’argent eut menacé le fonctionnement de la plateforme.\n\nCompétence\nUn titulaire de droits en Russie, injoignable par l'utilisateur\n\nLe contrat d'abonnement présente Valve comme une entité qui n'a que peu d'obligations et qui reste inaccessible à quiconque : les blocages sont définitifs, les recours sont rejetés et l'accès est supprimé à des territoires entiers sur la base d'une simple mention concernant les « régions sanctionnées ». À cette attitude s'oppose la manière dont Valve agit lorsque ses propres intérêts commerciaux sont en jeu dans une juridiction qu'elle considère par ailleurs comme difficile.\n\nValve v. Touch Skins — plainte en matière de propriété intellectuelle avant le procès, Russie\n1 2026 de septembre\nValvee, par l'intermédiaire du cabinet d'avocats russe Melling, Voitishkin & Associés, envoie une lettre de mise en demeure préalable au procès aux exploitants de Skins tactiles, un grand changeur de skins CS2, par la Poste russe et par e-mail.\nMotifs\nTrois catégories de violations présumées : les droits exclusifs sur le logiciel ; les droits relatifs à l'apparence des skins d'armes, de couteaux et de gants ; et les marques déposées d'Valve. Le comportement des exploitants est qualifié d'intentionnel et de prolongé.\nDemande\nCessez immédiatement toute exploitation et supprimez l'ensemble de l'infrastructure — celle du logiciel code source, sites web et pages sur les réseaux sociaux — à défaut de quoi Valve se réserve le droit d’intenter une action devant un tribunal russe pour une indemnisation financière importante et de saisir autorités chargées de l'application de la loi, aux fins d'une évaluation pénale.\nRésultat\nAprès avoir reçu cette lettre, la plateforme a annoncé qu'elle cessait ses activités. Il s'agirait de la première fois qu'Valve recourt à des moyens juridiques contre un développeur de « skin-changer » en Russie.\n\nSelon les informations fournies par le data-miner Maxim « GabeFollower » Poletaev (X, ~11 septembre 2026) et la presse russe spécialisée dans les jeux vidéo. Il s’agit d’une plainte préliminaire, et non d’une action en justice déposée ; aucun numéro de dossier n’a été rendu public. Ces informations sont présentées ici telles qu’elles ont été rapportées, et non comme un document judiciaire. Sources : dota2.ru archivé 2026-09-24 ↗ · Shazoo.\n\nLa même juridiction, dans l'autre sens\n\nValve connaît bien le système juridique et réglementaire russe. Il est conforme aux exigences de Roskomnadzor: à la demande de l'autorité de régulation, elle a supprimé les pages communautaires 260et Steam contenant des contenus interdits, et Roskomnadzor a déclaré publiquement que le site Steam respectait les exigences de la législation. La loi russe dite « d'atterrissage » (loi fédérale 236-FZ, en vigueur depuis 2022), impose aux grandes plateformes Internet étrangères desservant des utilisateurs russes d’établir une présence locale et d’ouvrir un compte de liaison auprès de Roskomnadzor. Valve se conforme non seulement aux ordres de retrait émis par cet organisme de régulation, mais fait désormais appel à des avocats russes et brandit la menace des tribunaux russes pour protéger ses « skins » en tant que propriété intellectuelle.\n\nLa plateforme se montre donc accessible, efficace et intransigeante dès lors qu’il s’agit de ses revenus. Le contraste est frappant avec la situation de l’utilisateur : un client payant situé dans une région soumise à des sanctions se voit signifier que la relation est rompue, l’accès à la communauté est bloqué jusqu’à ce que 2038, le ticket soit clôturé, et il n’existe aucun forum permettant de contester cette décision — « Ils étaient plus qu'heureux de prendre mon argent et de traiter mes transactions », le remboursement de ce même compte, provenant de la même adresse IP iranienne, ayant été approuvé un an plus tôt (r/pcgaming, 4 août 2026; davantage de lettres de mise en demeure dans l'exposition « L'économie des cartes »). « Valve » met en œuvre tout l’appareil d’un système juridique national pour défendre un skin ; il ne prévoit aucune procédure pour l’utilisateur qui a acheté ces skins.\n\nValve Elle considère cette même juridiction comme un cadre dans lequel elle peut agir et se conformer, dès lors que l'intérêt en jeu est celui d’Valve — avocats russes, menace des tribunaux russes, exécution des ordonnances de retrait de Roskomnadzor — tout en considérant que ses obligations envers les utilisateurs de ce marché, et de tous les autres, échappent à toute procédure. C’est un titulaire de droits lorsqu’il s’agit de ses revenus, et une partie injoignable lorsqu’il s’agit des droits des utilisateurs.\n\nSources : TASS (RKN : conforme à la norme «Steam ») · Loi fédérale « 236-» FZ.\n\nOpportunisme juridique\nLa capitulation face à la clause d'arbitrage\n2023 — l'attaque\n\nDes cabinets d'avocats (Zaiger LLC, Mason LLP) ont recruté des milliers d'utilisateurs via les réseaux sociaux et ont déposé simultanément des dizaines de milliers de demandes d'arbitrage individuelles.\n\nL'exposition de Valve\n\n$225M+\nen frais de dépôt d'arbitrage non remboursables, avant même que l'affaire ne soit examinée sur le fond. Calculé conformément au Règlement d’arbitrage pour les consommateurs de l’American Arbitration Association (AAA) et aux annexes complémentaires relatives à l’arbitrage de masse. Les demandeurs, représentés par Zaiger LLC et Mason LLP, ont déposé environ75,000 demandes d’arbitrage individuelles à l’encontre de Valve Corp. (parallèlement à des actions en matière de droit de la concurrence dans Wolfire Games LLC et al. c. Valve Corp., Affaire n° 2:21-cv-00563-JCC, W.D. Wash.). Conformément aux barèmes tarifaires de l’AAA applicables aux consommateurs, l’entreprise défenderesse s’acquitte de frais administratifs non remboursables liés à la procédure ainsi que de dépôts de garantie pour la nomination des arbitres d’un montant d’environ $3,000+ par dossier individuel (75,000 dépôts × $3,000 = environ $225M de frais de procédure à avancer). Voir les rapports juridiques de Bloomberg Law et de Reuters sur l’exposition des entreprises technologiques aux arbitrages de masse (2023–2024).\n\nPériode\tMécanisme de règlement des litiges de la SSA\tEffet observé\tRésultat\nBefore Sep 2024\tMandatory individual arbitration + class-action waiver\tIndividual litigation becomes economically irrational for users\tMass arbitration → $225M fee threat\nAfter Sep 2024\tDisputes in King County, WA courts only\tArbitration costs are avoided; cases consolidate in a single forum\tClass actions now possible\nConclusion\n\nPendant plus de dix ans, la SSA a exigé des utilisateurs qu’ils renoncent à leur droit à un procès devant jury au profit d’un arbitrage individuel. Après que les demandes d’arbitrage massives ont rendu ce mécanisme financièrement coûteux pour Valve, la SSA a été modifiée afin de renvoyer les litiges devant les tribunaux du comté de King. Ce changement a été présenté sans véritable possibilité de refus ; l’alternative à l’acceptation consistait à perdre l’accès aux actifs numériques achetés en supprimant le compte.\n\nApplication algorithmique\nVACNet, la présomption de culpabilité et les faux positifs\n2023s d'octobre — AMD Anti-Lag+\n\nUne mise à jour du pilote AMD (v23.10.1) a activé la fonction Anti-Lag+ dans CS2, qui a intercepté des fonctions DLL du jeu. VAC a qualifié cela d'injection de code de triche et a infligé des suspensions définitives à des milliers d'utilisateurs légitimes avant l'intervention d'Valve.\n\n2023, décembre — haute résolution (DPI)\n\nLes joueurs dont le DPI était supérieur à 10,000 et qui effectuaient des rotations rapides de la caméra ont été bannis définitivement. VACNet n'était pas en mesure de faire la distinction entre un mouvement physique de la souris et une triche de type « spinbot ».\n\nCatégorie d'assistance\tTemps de réponse annoncé\tRésultat réel\nRefund requests\t50 min – 1.5 hr\tAutomatic approval (<14 days, <2 hours played)\nAccount security / recovery\t3–12 hours\tDepends on documentation provided\nContesting a VAC ban\tForm response\tComplete refusal. Support cannot reverse VAC decisions. The ban is permanent.\nPolitique officielle d'Valve\n\n« Les interdictions VAC sont définitives, non négociables et ne peuvent pas être levées par le service d'Steam. »\n\nLe canal d'assistance qui a notifié la suspension est également celui qui a communiqué le refus de réexamen : Steam. Le service d'assistance précise qu'il ne peut pas revenir sur une décision du VAC. Pour l'utilisateur, la décision de l'algorithme fait office de verdict définitif.\n\nAspects économiques de la revente\nContrôle des actifs virtuels et commission de revente\nLes frais de marché de l'15%e CS2 — une partie de la valeur est prélevée à chaque revente\nItération\tSolde de l'acheteur\tLe vendeur reçoit\t« Burned » (15%)\n1\t$100.00\t$85.00\t$15.00\n2\t$85.00\t$72.25\t$12.75\n3\t$72.25\t$61.41\t$10.84\n10\t$23.16\t$19.68\t~$3.47\nTotal\t$100 → dust\tValve collects the 15% fee on each resale. Users must add new money to keep trading.\nModification des règles de reprise du CS2 — 2025 d’octobre\n\nSans préavis, Valve a modifié les règles du contrat d’échange CS2 afin de permettre l’acquisition garantie de couteaux et de gants rares en échange d’objets de qualité « Covert ». Les prix des couteaux ont chuté, ceux des objets « Covert » ont fortement augmenté, et une vague de ventes paniques s’est ensuivie sur l’ensemble du marché.\n\nValve invoque l'article 7 de la SSA pour se prémunir : aucune responsabilité n'est engagée en cas de modification des règles de la plateforme. Les utilisateurs assument le risque dans une économie dont les règles Valve peuvent changer sans préavis ni indemnisation. Le montant des pertes déclarées à l'échelle du marché est contesté et n'est pas mentionné ici en l'absence de source primaire.\n\nRéponse réglementaire européenne\nL'UOKiK, la DSA et la loi sur l'équité numérique\nUOKiK — Pologne, mai 2024\n\nL'autorité polonaise de la concurrence (UOKiK) a ouvert une procédure antitrust officielle à l'encontre d'Valve Corporation et de cinq éditeurs/distributeurs de jeux vidéo nationaux concernant des allégations de fixation des prix, de clauses restrictives de parité des prix et de pratiques de géoblocage qui ont conduit les consommateurs polonais à payer jusqu'à 20% de plus pour des jeux vidéo que sur les marchés voisins de l'EEE. Dans le cadre de cette enquête antitrust, les inspecteurs de l’UOKiK et la police ont mené des perquisitions à l’aube et procédé à des saisies de preuves dans les locaux polonais des éditeurs et distributeurs partenaires nationaux (et non dans les succursales d’Valve, car Valve ne dispose d’aucune entité en Pologne). Amende légale potentielle : jusqu’à 10% du chiffre d’affaires annuel. Source : Communiqué officiel de l'UOKiK : « Le président de l'UOKiK a ouvert une procédure à l'encontre d'Valve et des développeurs de jeux », mai 2024.\n\nLoi sur les services numériques (DSA)\n\nExige de la transparence en matière de modération automatisée. Steam ne publie aucune donnée relative aux faux positifs ou aux faux négatifs concernant VACNet, et son service d'assistance précise que les décisions prises par VAC ne peuvent pas être annulées.\n\nLoi sur l'équité numérique — 2026\n\nDispositions prévues : accès durable aux contenus payants, interdiction des « dark patterns » lors de la renonciation aux droits, reconnaissance des droits de propriété sur les actifs numériques et protection contre la confiscation définitive des biens.\n\nConclusion\nÉcarts constatés entre les règles et les données enregistrées\n1\n\nLe fossé en matière d'accession à la propriété. Les utilisateurs paient le prix fort pour une licence que le contrat autorise Valve à révoquer. La Cour de cassation française (octobre 2024) a jugé que la revente numérique n'était pas protégée, consacrant ainsi cette position dans la loi.\n\n2\n\nApplication algorithmique. VACNet a prononcé des interdictions injustifiées (pilotes AMD, incidents liés à une résolution DPI élevée). Le service d'assistance d'Steam indique qu'il ne peut pas revenir sur une décision de VAC ; l'algorithme a donc le dernier mot.\n\n3\n\nÉconomie sur les frais. Les frais de mise sur le marché CS2 d’15% (frais de 5%, Steam et 10%) réduisent la valeur à chaque revente, et les règles de la plateforme peuvent être modifiées sans préavis ; la responsabilité de Valve concernant ces modifications est exclue en vertu du SSA.\n\n4\n\nLa clause d'arbitrage a été supprimée. La SSA a supprimé l'arbitrage obligatoire en septembre 2024, après que des recours collectifs ont exposé Valve à environ225millions de dollars de frais. Les utilisateurs n'ont bénéficié d'aucune possibilité réelle de se soustraire à ce changement.\n\n5\n\nCompétence sélective. Valve a fait appel à un cabinet d'avocats russe (Melling, Voitishkin & Partners) et a menacé d'engager une procédure judiciaire en Russie contre Touch Skins, tout en considérant que ses obligations envers les utilisateurs de ce même marché échappaient à toute procédure judiciaire. Valve se comporte comme un titulaire de droits lorsque ses intérêts commerciaux sont en jeu, et comme une partie injoignable lorsqu'il s'agit des droits des utilisateurs.\n\n← Partie I : Contournement des serveurs proxy et jeux d'argentPartie II : Accès et responsabilité →\n\nLes sources juridiques et les dossiers judiciaires sont cités en référence à leurs éditeurs et dépôts d'origine. Aucun droit de propriété n'est revendiqué sur les documents sous-jacents.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Analyse juridique — Conditions générales d'utilisation et conformité réglementaire"
          },
          {
            "level": 2,
            "id": null,
            "text": "Décharge de responsabilité et licence révocable"
          },
          {
            "level": 3,
            "id": null,
            "text": "2.1 Le modèle de « l'abonnement » face aux droits de propriété"
          },
          {
            "level": 3,
            "id": null,
            "text": "2.2 L'illusion du remboursement face à la directive européenne relative aux droits des consommateurs"
          },
          {
            "level": 2,
            "id": null,
            "text": "Marché secondaire et droit de la concurrence"
          },
          {
            "level": 3,
            "id": null,
            "text": "UFC Que Choisir c. Valve — France"
          },
          {
            "level": 3,
            "id": null,
            "text": "Affaire antitrust concernant Wolfire Games — États-Unis (Affaire « In re Valve Antitrust Litigation », n° 2:21-cv-00563)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve Déclaration officielle : Liquidations pour fraude à l'échelle mondiale (28 octobre 2019)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Un titulaire de droits en Russie, injoignable par l'utilisateur"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve v. Touch Skins — plainte en matière de propriété intellectuelle avant le procès, Russie"
          },
          {
            "level": 3,
            "id": null,
            "text": "La même juridiction, dans l'autre sens"
          },
          {
            "level": 2,
            "id": null,
            "text": "La capitulation face à la clause d'arbitrage"
          },
          {
            "level": 2,
            "id": null,
            "text": "VACNet, la présomption de culpabilité et les faux positifs"
          },
          {
            "level": 2,
            "id": null,
            "text": "Contrôle des actifs virtuels et commission de revente"
          },
          {
            "level": 3,
            "id": null,
            "text": "Les frais de marché de l'15%e CS2 — une partie de la valeur est prélevée à chaque revente"
          },
          {
            "level": 3,
            "id": null,
            "text": "Modification des règles de reprise du CS2 — 2025 d’octobre"
          },
          {
            "level": 2,
            "id": null,
            "text": "L'UOKiK, la DSA et la loi sur l'équité numérique"
          },
          {
            "level": 2,
            "id": null,
            "text": "Écarts constatés entre les règles et les données enregistrées"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/fr/#briefing-heading",
          "https://dota2.ru/news/67707-valve-cerez-uristov-napravila-krupnoj-rossijskoj-skincendzer-platforme-trebovanie-o-prekrasenii-deatelnosti/",
          "http://web.archive.org/web/20260924181657/https://dota2.ru/news/67707-valve-cerez-uristov-napravila-krupnoj-rossijskoj-skincendzer-platforme-trebovanie-o-prekrasenii-deatelnosti/",
          "https://shazoo.ru/2026/09/12/190508/valve-cerez-rossiiskix-iuristov-dobilas-zakrytiia-krupnogo-skinceindzera-dlia-cs2",
          "https://www.reddit.com/r/pcgaming/comments/1vf24lu/warning_to_all_gamersexpats_steam_took_my_money/",
          "https://phishdestroy.io/steam_dossier/fr/card_economy.html#asymmetry",
          "https://tass.ru/obschestvo/23235387",
          "https://base.garant.ru/401414628/",
          "https://uokik.gov.pl/postepowanie-wyjasniajace-w-sprawie-valve-i-dystrybutorow-gier",
          "https://phishdestroy.io/steam_dossier/fr/",
          "https://phishdestroy.io/steam_dossier/fr/investigation_part2.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/fr/legal_analysis.content.json",
      "export_json_sha256": "3ab74f9b8bd736fede4f6250afbdf5af11167e2ca3742f1f88ae669d8a59766a"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "fr/license_disclaimer.html",
      "language": "fr",
      "title": "Licence · Droits · Clause de non-responsabilité — PhishDestroy",
      "source_url": "https://phishdestroy.io/steam_dossier/fr/license_disclaimer",
      "source_html_sha256": "a7686684c558b3ad1ad728c988a7eb96a257c9e32179494936c62ceff1c61bb7",
      "exported_at": "2026-09-29T00:17:37.160Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "license_disclaimer.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/fr/license_disclaimer.pdf?v=print-20260929-v5",
        "sha256": "e497f9bf547cd02e2c4c49704bb0a33e6acc1c72e59bb50b47e6300243fc3e70",
        "bytes": 121609,
        "pages": 11
      },
      "integrity": {
        "signed_object": "license_disclaimer.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "license_disclaimer.content.json.asc",
        "digest_file": "license_disclaimer.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify license_disclaimer.content.json.asc license_disclaimer.content.json",
          "sha256sum -c license_disclaimer.content.json.sha256"
        ]
      },
      "content": {
        "text": "PHISHDESTROYEnquête judiciaire · Valve / Steam\nLicence · Droits · Clause de non-responsabilité\nLicence et mentions légales — Mise au domaine public\n\nTous droits réservés s'est livré à l'humanité.\n\nCE QUE CETTE SECTION DÉMONTRERA\n\nLe présent document établit la mise au domaine public inconditionnelle (CC01.0Universal) ainsi que les conditions de licence logicielle du MIT régissant le dossier PhishDestroySteam. Tous les résultats d'expertise, ensembles de données probatoires, graphes de réseau et méthodologies d'analyse sont placés de manière irrévocable dans le domaine public en vue d'une utilisation réglementaire, juridique et universitaire sans restriction à l'échelle mondiale.\n\n← Retour au dossier de synthèse destiné aux dirigeants\n\nPhishDestroy renonce à tout droit sur ce contenu — le reproduire, le vendre, y apposer son nom. Vous trouverez ci-dessous deux documents présentés sous la forme d’un seul et même texte : une lettre ouverte adressée à Valve, rédigée dans notre style habituel, et une renonciation officielle rédigée à l’intention de l’autorité chargée de donner suite à ce contenu.\n\nEnquête · Valve Corporation / SteamÉdition publique — sans date d'expiration, sans possibilité de rétractation\nEXEMPTÉ\nSection ILicence — l'aspect juridique proprement dit, mais d'un point de vue humain\n\nPhishDestroy renonce à tout droit sur ce contenu. Zéro. Fin. Terminé. Vous pouvez le reproduire, le vendre, y apposer votre nom, le tatouer sur votre patron, peu importe. Aucune mention de source n'est requise, aucun message privé n'est nécessaire, aucune carte de remerciement n'est attendue.\n\nUne règle concrète (oui, une seule)\n\nCe n'est PAS à VOUS de décider si vous êtes un terroriste.\n\nSi vous êtes un utilisateur résidant en Russie ou dans tout autre pays soumis à des sanctions de l'OFAC, ce contenu ne vous est PAS destiné. Il n'y a aucune faille. Profitez bien de vos sanctions.\n\nEt si vous avez modifié la région de votre Steam pour choisir la Turquie alors que vous vous trouvez à Moscou… félicitations pour votre sens de la géographie créative. Vous restez russe. Les sanctions s’appliquent toujours. C’est littéralement le but.\n\nSection IIDe quoi s'agit-il et pourquoi existe-t-il ?\n\nNous publierons davantage d'informations sur Valve que ce qu'un employé lambda d'Valve'en sait sur lui-même. Ce n'est pas de la vantardise. C'est simplement ce à quoi nous en sommes arrivés.\n\nComment en sommes-nous arrivés là ? C'est une histoire assez drôle : c'est en quelque sorte Steam qui nous a créés. Ce site nous a nourris de ses arnaqueurs, de ses tickets d'assistance, de son écosystème de contournement des interdictions… Et voilà où nous en sommes aujourd'hui. Sans rancune. C'est même assez poétique, en fait.\n\nPour ceux qui n'ont pas encore lu l'histoire des origines, nous avons déjà fait la connaissance des avocats européens extrêmement coûteux d'Valve (Taylor Wessing, puisque vous le demandez) :\n\nhttps://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d archivé 2026-08-21 ↗\n\nUne rencontre charmante. Surtout compte tenu de leur tarif horaire.\n\nValve, était-il au courant ? Oui. Taylor Wessing, était-il au courant ? Presque certainement oui. Mais quand on est aussi riche, les lois relèvent davantage d'une ambiance générale que d'une obligation, n'est-ce pas ?\n\nEn fait, c'est à peu près tout ce qu'il y a à dire.\n\nSteam Nous avons passé des années à traquer les escrocs. Pas toujours intentionnellement — parfois, les escrocs se retrouvaient simplement « marqués » par l’Valve par simple association. Nous n’essayons pas d’en faire tout un drame. Nous essayons simplement d’être précis. Pour être honnêtes, c’est plus difficile pour nous que d’en faire tout un drame — c’est simplement notre façon d’écrire.\n\nEst-ce un conflit ?\n— Non.\n\nEst-ce que ce problème peut être résolu ?\n— Oui. Mais on ne signera aucun accord de confidentialité et on ne participera pas à des programmes de prime aux bogues pour des clopinettes.\n\nNous avons attendu plus de 4 ans qu’ils règlent le problème d’usurpation d’identité avant de pouvoir en parler publiquement. Car si nous en avions parlé plus tôt, Steam aurait pris son petit air de victime, crié à la « menace active ! » et nous aurait proposé des miettes pour que nous signions un document qui aurait fait de nous leur propriété légale pour toujours. Non merci.\n\n(Par ailleurs : « Valve » enfreint lui-même l'accord de confidentialité. Ce sont leurs propres employés qui le font. Ceux qui occupent des postes à responsabilité. Mais bien sûr, parlons plutôt des nôtres.)\n\nSection IIILettre ouverte à Valve — Sérieusement, lis ça\n\nValve : si vous souhaitez que ce domaine soit supprimé, envoyez-nous un e-mail. Il n'est pas nécessaire de faire appel à un avocat externe pour cette discussion.\n\nPour les non-initiés : le Dr Patrick est titulaire d’un master en droit commercial international de l’université d’Aberdeen et — tenez-vous bien — a littéralement rédigé sa thèse de doctorat sur le droit des technologies de l’information. Il est récemment devenu associé chez Taylor Wessing, un cabinet dont le modèle économique repose entièrement sur la facturation de sommes exorbitantes à des entreprises telles qu’Valve, dans le but de faire traîner les procédures jusqu’à ce que la partie adverse soit à court d’argent ou de patience.\n\nOn ne lui en veut pas. Des clients riches et coupables qui paient à l'heure : c'est un excellent choix de carrière. Mais on estime simplement que ce n'est pas à vous de financer ça.\n\nLa transaction (offre publique, pas besoin d'avocats)\n\nLe domaine est la seule chose que Valve puisse réellement obtenir. L'enquête, les signalements et les ressources associées sont déjà en cours ; ils se poursuivront, que le domaine soit acquis ou non.\n\nSi vous souhaitez obtenir ce nom de domaine :\n\nLaissez vos experts en droit des technologies de l'information fixer un prix équitable.\n\n50% est reversée à la Fondation «SEAL».\n\nOn supprime le nom de domaine. Pas de chichis. Pas de procès. C'est réglé.\n\nCe n'est pas une menace. C'est une proposition claire et simple concernant la seule chose qui soit réellement à votre portée. Vous ne l'obtiendrez pas autrement — c'est simplement ainsi que les choses sont.\n\nAllons-nous « nuire » directement à Valve ? Probablement pas d’une manière qui se ressentira sur le plan financier. Nous ne nous faisons pas d’illusions. Mais nous le ferons en toute honnêteté, au grand jour, sans chercher à gagner en influence — car nous n’avons pas besoin d’influence. Nous voulons que le monde entier voie ce qui a toujours été visible aux yeux de tous, à condition d’y regarder de près.\n\nNous disposons d’5s d’années d’archives. Ce que les avocats d’Valve ont présenté lors de la procédure de communication préalable — les données auxquelles les agents de soutien ont accès, les empreintes digitales, la trace écrite qu’ils nous ont littéralement remise — suffit amplement. Nous n’avons pas besoin de divulguer ces informations brutes.\n\nQui reçoit quoi ?\n\nLes autorités de régulation reçoivent les originaux.\n\nLes chercheurs et les journalistes reçoivent des versions expurgées (les témoignages des victimes, les identifiants des enfants et les charmants commentaires d'Valve ont été supprimés pour des raisons évidentes).\n\nDes mineurs figuraient parmi les comptes concernés et n'ont pas été informés. Cette constatation figure dans le dossier transmis à l'autorité de régulation, après suppression des déclarations des victimes et des identifiants, car elle relève de la compétence d'une autorité chargée de la protection des données plutôt que d'un article.\n\nPar ailleurs, Valve — nous tenons à clarifier un point avant que vous ne décidiez de la manière de procéder : PhishDestroy est une communauté, pas une personne. Vous l’avez appris lorsque vous avez adressé une lettre de mise en demeure à la communauté sans prendre la peine de vous adresser à elle — vous vous êtes contenté d’exploiter ses données et de bannir les comptes.\n\nLa communauté n'a aucun différend avec Valve. Nous n'avons pas cherché cela. Ce sont les escrocs que vous avez laissés se développer qui nous ont trouvés. Nous les avons bloqués. Et nous en sommes là.\n\nSection III-BLes ressources associées — une note adressée spécifiquement à Steam\n\nNous tenons à être transparents au sujet de la structure d'amplification, car prétendre qu'elle n'existe pas reviendrait à manquer d'honnêteté.\n\nD'après ce que nous comprenons de la situation au sein de la communauté, « PhishDestroy » dispose d'au moins deux partenaires qui reprendront cette information et la diffuseront.\n\nConcrètement, cela signifie :\n\nChacun aborde à sa manière des thèmes qui se recoupent.\n\nIls sont indépendants : ils ne suivent pas nos directives, et nous ne suivons pas les leurs. Le sujet général est le même, mais la méthodologie diffère.\n\nIls ne mettront PAS en œuvre la partie 1.. Ils surveillent la situation.\n\nSi Valve décide de ne pas fermer le site :\n\nAttendez-vous à ce qu'ils refassent surface après la partie 2 ou la partie 3.\n\nIls reprendront ce qui leur est utile dans nos travaux, y ajouteront leurs propres contributions, puis publieront le tout sous leur propre nom.\n\nC'est exactement le genre de situation pour laquelle la licence prévue à la section 1 a été conçue : le contenu est diffusé là où il doit l'être, il est complété, enrichi — et ni nous ni eux ne sommes tenus de mentionner la source.\n\n(P.S. à l'attention des juristes qui s'interrogent sur les chaînes de responsabilité : il n'y en a pas. Ces sources ne reçoivent ni directives, ni financement, ni données de notre part. Elles consultent les informations publiques et tirent leurs propres conclusions. Tout comme vous pourriez le faire.)\n\nNous ne disons pas cela pour intimider qui que ce soit. Nous le disons afin que ceux qui élaborent des stratégies du côté d’Valve disposent d’informations précises sur la réalité de l’environnement informationnel.\n\nUne source qui reprend nos informations et les complète peut constituer un indice. Deux sources qui le font indépendamment l’une de l’autre et parviennent à des conclusions similaires constituent une tendance. Ce sont ces tendances que les autorités de régulation remarquent.\n\nSection IVL'argent, les interdictions, tout ce cirque\n\nVoici le problème concernant l’interdiction des sites de jeux d’argent et des arnaqueurs par l’Steam : il ne s’agit pas d’une mesure de répression. Il s’agit de capter des recettes. L’Valve empoche l’argent, s’en lave les mains, puis monte sur scène pour raconter à tout le monde une belle histoire sur les cartes Pokémon et le baseball.\n\nLorsque des compromissions du côté du support technique sont documentées — notamment l’aveu écrit d’Valve en février 2023, dans lequel l’entreprise assume la responsabilité de la compromission de comptes de grande valeur à la suite de demandes d’assistance, ainsi que les licenciements de collaborateurs sous contrat rapportés par Dexerto et Escorenews à la suite de l’affaire de délit d’initié portant sur320k $ (Partie II, §04 · Dossier principal §14.1) — elles s’appuient sur des aveux rendus publics et sur des enquêtes journalistiques. Les rumeurs non fondées selon lesquelles des membres du personnel d’encadrement mèneraient des activités parallèles liées aux jeux d’argent ou percevraient des pourcentages pour lever des interdictions ne sont pas étayées par des informations accessibles au public et ne sont donc pas prises en compte ici.\n\nEntre-temps, Valve a supprimé la possibilité de suivre correctement les skins sur 2017.. Ils en ont même discuté sur leurs propres forums. Ils ont qualifié cela de « mesures anti-jeux d’argent », alors que l’écosystème des paris sur les skins a continué à faire transiter des milliards via l’infrastructure de Steam pendant des années après cela. Super image de marque.\n\nNous allons démontrer que :\n\nLes « skins » sont plus anonymes que le Monero\n\nUn cartel péruvien aurait utilisé des skins de Dota 2 pour transférer de l'argent\n\nSteam il s'agit, en substance, d'un système permettant de contourner les sanctions, d'une valeur d'environ7milliards de dollars en « cartes à collectionner » (oui, ils ont bel et bien parlé de « cartes à collectionner » devant un procureur)\n\nOn a une vidéo sur le sujet des skins. Tu la verras.\n\nNous savons également que :\n\nLa modération sur Reddit est influencée par Valve\n\nInfrastructure de données d'Steams provenant de tiers (telle que steamid.uk) est géré par un particulier (msart) dont le projet associé consacré à la liste noire (steambans.com archives) est géré conjointement par un modérateur reconnu de la communauté Valve (killahinstinct_) — ce qui laisse l'audit indépendant des mesures d'exclusion de la plateforme entièrement sous la responsabilité d'Valve (voir « Économie des cartes » §08)\n\nCe qu'ils ne peuvent pas contrôler, ils l'interdisent\n\nValve : si vous continuez à faire l’innocent, très bien. Nous prenons note de votre « refuge ». De toute façon, Google Analytics anonymise les adresses IP de vos utilisateurs. Nous voyons ce qui est supprimé. Mais nous ne pouvons pas le prouver à un coût suffisamment bas pour que vos avocats s’y intéressent. Pour l’instant.\n\nSection VLe problème des logiciels malveillants — oui, on en parle\n\nSoyons d'une clarté implacable quant à la chronologie des faits, car elle révèle exactement qui vous êtes.\n\nNous ne divulguons PAS publiquement cette faille de sécurité dans le jeu. Nous ne la signalons PAS à Steam. Ce programme exige la signature d’un accord de confidentialité (NDA), ce qui nous empêcherait d’informer les utilisateurs concernés de ce qui est arrivé à leurs comptes. L’objectif de ce travail est justement d’informer les personnes qui ont perdu ces comptes, ainsi que les autorités de régulation ; un accord de confidentialité est incompatible avec cet objectif.\n\nVoici ce qui s'est réellement passé : cette faille de sécurité est pratiquement un secret de polichinelle dans les milieux concernés. Nous savons de source sûre que des chercheurs indépendants en sécurité ont déjà mis l'exploit complet sous le nez du service d'Steam. Cette étape est franchie. Vous avez été officiellement avertis par vos propres canaux officiels.\n\nEt qu’a fait Valve ? Absolument rien. Car pour Valve, la sécurité n’est pas synonyme de profit — bien au contraire. La sécurité est un centre de coûts. Tant qu’une menace n’atteint pas un seuil critique et ne provoque pas une crise de communication catastrophique, Valve ne la considère pas comme urgente.\n\nAlors, que faisons-nous ? Nous informons le public de son existence, car le fait que «Valve ait connaissance d'une menace systémique liée à un logiciel malveillant et choisisse délibérément de ne rien faire » constitue un élément d'information crucial pour les autorités de régulation qui lisent ces lignes.\n\nCe jeu est un véritable phénomène. Nous n'en citerons pas le nom ici. Mais comprenez bien ceci :\n\nCe n'est PAS une de ces bêtises de script-kiddie de CS:GO où un serveur vous demande d'« installer un pilote ». C'est catastrophique.\n\nC'est un véritable cauchemar digne d’Unturned : une attaque RCE « zéro clic » dès la connexion au serveur. Vous rejoignez un serveur. Vous ne cliquez sur rien. Vous ne téléchargez rien. La connexion elle-même constitue la surface d’attaque, et votre machine est entièrement compromise. Soyons réalistes : déployer un RCE et contourner les antivirus locaux en profitant des certificats numériques de confiance d’Valve n’est même plus une nouveauté sur Steam. C’est pratiquement une fonctionnalité intégrée à votre écosystème.\n\nValve sait déjà que cela existe. Mais ils s’appuient sur leur échappatoire juridique préférée et lâche : comme le jeu est techniquement développé par un tiers, Valve s’en lave les mains. Ils distribuent le jeu, traitent les paiements, hébergent l’infrastructure, mais lorsqu’une vulnérabilité RCE « zéro clic » menace des millions de leurs utilisateurs, leur position est la suivante : « Ce n’est pas notre jeu, ce n’est pas notre responsabilité. »\n\nQuand tout ça finira inévitablement par exploser, c'est le développeur tiers qui en fera les frais, tandis qu'Valve s'en tirera en se présentant comme la plateforme responsable qui aura « contribué » à la résolution du problème. Une lâcheté typique d'Valve. On connaît bien le scénario.\n\nNous tenons à le signaler officiellement afin que les autorités de régulation, les procureurs et les journalistes comprennent exactement comment Valve gère les logiciels malveillants actifs : en se cachant derrière des développeurs tiers, en imposant des accords de confidentialité (NDA) et en laissant les joueurs sans défense.\n\nFin de la lettre ouverteDébut de la période d'inscription officielle\nRegistre officiel · destiné aux autorités\nDéclarationEn ce qui concerne l'utilisation et les droits\n\nPhishDestroy Coalition pour les projets et la cybersécurité\n\nLa présente déclaration accompagne chaque document et chaque pièce à conviction figurant dans ce dossier. Elle s'adresse à toute autorité, juridiction, instance de régulation, procureur, chercheur, journaliste ou personne concernée à qui ces documents seront remis.\n\n1. Il n'y a aucune condition d'utilisation\n\n1.1 Tous les documents produits par la Coalition dans le cadre de cette saisine — les exposés des faits, l'analyse, les pièces qu'elle a rédigées, les outils et les conclusions — sont publiés SANS RÉSERVE D'AUCUN DROIT.\n\n1.2 Toute personne peut, sans autorisation préalable et sans nous en informer :\n\nde le reproduire, en tout ou en partie ;\n\nl'adapter, le modifier, le réécrire, le restructurer ou le corriger ;\n\ntraduisez-le ;\n\nen en extraire un passage sans préciser qu'il s'agit d'un extrait ;\n\nl'intégrer dans des documents officiels, des conclusions, des décisions, des mémoires, des rapports ou des communiqués de presse ;\n\nle présenter comme étant le fruit du travail ou des recherches du destinataire ;\n\ns'en servir comme matière première et jeter le reste ;\n\net de le transmettre à n'importe qui d'autre dans les mêmes conditions.\n\n1.3 AUCUNE MENTION DE SOURCE N'EST REQUISE NI SOLLICITÉE. Il n'est pas nécessaire de nommer, citer, mentionner, remercier, consulter ou informer la Coalition. Si les informations issues de cette référence aident une autorité et que la Coalition n'est jamais mentionnée, CELA CONSTITUE UN RÉSULTAT ENTIÈREMENT SATISFAISANT et la Coalition le précise d'avance afin que la question n'ait pas à être soulevée.\n\n1.4 Si, en revanche, une autorité juge plus pratique de citer la Coalition comme source, elle est libre de le faire. Le choix appartient entièrement au destinataire et aucune de ces deux options n'entraîne de conséquence particulière.\n\n1.5 Il s'agit d'une RENONCIATION, et non d'une offre de licence. Elle ne nécessite aucune acceptation, n'impose aucune obligation et ne peut faire l'objet d'aucune violation. Les logiciels publiés par la Coalition sont diffusés séparément sous licence MIT ; les travaux de recherche et les résultats sont mis dans le domaine public dans toute la mesure permise par la loi, et lorsqu’une juridiction n’autorise pas la renonciation, la Coalition accorde une licence irrévocable, mondiale et libre de droits ayant le même effet.\n\n2. Pourquoi cela a de l'importance sur le plan pratique, et pas seulement par simple courtoisie\n\n2.1 Une autorité peut raisonnablement hésiter à se fonder sur des éléments fournis par un tiers, de crainte de donner l'impression d'agir à la demande de ce dernier ou de se retrouver dans une situation de conflit d'intérêts avec lui.\n\n2.2 IL N'Y A RIEN ICI QUI PUISSE PRÉSENTER UN RISQUE D'AMORÇAGE. La Coalition ne demande rien, n'a droit à rien, ne conserve rien et n'a aucune attente d'aucune sorte. Elle ne peut pas, par la suite, faire valoir un droit, s'attribuer le mérite, se plaindre d'une utilisation abusive ou contester la manière dont le contenu est présenté, car elle ne s'est laissée aucun fondement pour le faire.\n\n2.3 Une autorité qui utilise ces documents n'agit donc pas au nom de la Coalition. Elle utilise simplement des informations publiques qui ont été rassemblées par un tiers.\n\n3. Tout est déjà ouvert\n\n3.1 Les travaux de la Coalition sont publics par défaut :\n\nles enquêtes sont publiées en libre accès sur https://phishdestroy.io et sont librement accessibles ;\n\nCet outil est publié en open source sous licence MIT à l'adresse suivante : https://github.com/phishdestroy archivé 2026-09-11 ↗;\n\nla méthodologie est décrite dans la saisine elle-même, à l'annexe A, section A.16D, y compris la pondération et les limites de chaque type de source ;\n\nLa Coalition n'accepte aucun don et a fait part de cette position depuis 2018.\n\n3.2 Les seules informations qui ne sont PAS publiées sont celles dont la publication est illégale ou présente un risque : les données à caractère personnel des victimes et des tiers, ainsi que les informations susceptibles d'exposer une source à des représailles. Ces informations sont transmises aux autorités à titre confidentiel et sont répertoriées dans les annexes relatives aux éléments de preuve.\n\n3.3 La Coalition invite à examiner sa propre conduite selon les mêmes critères que ceux qu'elle applique à tout autre acteur, et a spontanément communiqué aux autorités compétentes des informations sur ses pratiques en matière de traitement des données, en sollicitant notamment des instructions quant à leur destruction.\n\n4. Intégrité de l'ensemble des éléments de preuve\n\n4.1 Les pièces justificatives sont fournies avec le dossier ou, le cas échéant, sur demande via un canal sécurisé. Elles ne sont pas publiées sur un site accessible au public et aucune adresse de ce type ne doit être déduite : ce type de documents est transmis directement aux autorités.\n\n4.2 Chaque livraison est accompagnée d'un fichier SHA256SUMS répertoriant un résumé SHA-256 pour chaque fichier fourni, ainsi qu'une signature OpenPGP indépendante SHA256SUMS.asc.\n\n4.3 La clé de signature est publiée à l'adresse suivante : https://phishdestroy.io/.well-known/pgp-key.txt et sur keys.openpgp.org. Son « empreinte » figure dans l'en-tête de chaque document de cet ensemble.\n\n4.4 Tout destinataire peut vérifier à tout moment qu'un fichier en sa possession correspond bien au fichier qui lui a été envoyé, sans avoir été modifié :\n\ngpg --verify SHA256SUMS.asc SHA256SUMS\n\nsha256sum -c SHA256SUMS\n\n4.5 Le but n'est pas d'observer une formalité. Il s'agit plutôt de faire en sorte que, si l'exactitude ou l'intégrité d'une pièce à conviction venait à être contestée ultérieurement, la question puisse être tranchée par un calcul plutôt que par des arguments.\n\n5. À propos de l'enregistrement — pourquoi cette dérogation est-elle fonctionnelle et ne relève-t-elle pas simplement de la générosité ?\n\n5.1 Les autorités pourraient tomber sur les enquêtes publiées par la Coalition et les trouver directes, polémiques et parfois satiriques. Cette impression est juste. La Coalition écrit délibérément de cette manière et ne s'en excuse pas.\n\n5.2 IL RECONNAÎT ÉGALEMENT QUE CE TON N'EST PAS ADAPTÉ À UNE PROCÉDURE RÉGLEMENTAIRE OU JUDICIAIRE. Une question grave ne devrait pas être abordée sur le ton d’une campagne. Les conclusions présentées à une autorité devraient être énoncées sans détours, en admettant leurs limites, et ne devraient pas obliger le lecteur à faire abstraction du ton pour en saisir le fond.\n\n5.3 C'EST PRÉCISÉMENT POUR CETTE RAISON QUE LA COALITION RENONCE À LA PÉRENNITÉ DE SON AUTEUR. La renonciation figurant à la section 1 constitue le mécanisme permettant de dissocier le contenu du registre : l'autorité peut reprendre ce qui lui est utile, le reformuler dans ses propres termes et écarter tout ce qui relève du style de la Coalition, ainsi que le nom de celle-ci. Cela n’entraîne aucune perte, et la Coalition préfère qu’il en soit ainsi.\n\n5.4 LA COALITION DEMANDE ÉGALEMENT QUE LE REGISTRE NE SOIT PAS CONFONDU AVEC LA MÉTHODE. Le ton adopté est combatif ; la démarche sous-jacente n’est toutefois pas négligente. Tout au long de ce rapport, les déductions sont distinctes des observations, les témoignages sont identifiés comme tels, les sources sont évaluées et leurs faiblesses sont exposées, les chiffres sont présentés avec leurs limites, et les points que la Coalition ne peut prouver sont formulés sous forme de questions adressées à l’autorité compétente plutôt que sous forme d’affirmations. Lorsque les éléments de preuve allaient à l’encontre de la position de la Coalition, celle-ci l’a signalé — voir l’annexe A, paragraphe 7, et section B.0 du dossier parallèle.\n\n5.5 LA COALITION EXPLIQUE LE LIEN ENTRE SA DÉMARCHE ET SES FINANCES, CAR LES DEUX SONT INDISSOCIABLES. Elle n'accepte d'argent de personne : ni dons, ni primes, ni clients, ni sponsors. C'est ce refus qui lui permet d'être aussi directe : une organisation qui a des revenus à protéger doit modérer ses propos à l'égard des parties dont elle dépend. N'ayant rien à protéger, la Coalition n'a rien à modérer.\n\nC'est aussi la raison pour laquelle la Coalition continue d'exister. Il n'y a pas d'autre moteur. Le travail est fait parce qu'il est fait ; il s'arrête lorsque ceux qui le font s'arrêtent.\n\n5.6 L'autorité n'est pas tenue d'accepter quoi que ce soit de tout cela. Cette précision est apportée afin que le ton adopté par la Coalition dans ses communications publiques ne soit pas interprété comme un indicateur du soin apporté à l'examen du dossier dont elle est actuellement saisie.\n\n6. Ce que propose la Coalition, selon ses propres termes\n\nInformation, recherche et observation.\n\nAucune affirmation n'est présentée comme une conclusion que la Coalition n'est pas habilitée à formuler. Lorsqu'une conclusion est déduite, le rapport le précise. Lorsqu'une conclusion repose sur un témoignage, le rapport indique de qui il s'agit et précise les limites de ce témoignage. Lorsque la Coalition n'est pas en mesure de répondre à une question, elle l'indique également et précise qui est en mesure de le faire.\n\nLa Coalition ne réclame ni réparation, ni indemnisation, ni reconnaissance, ni résultat, que ce soit pour elle-même ou pour quiconque. Elle demande simplement que les questions formulées dans la saisine soient posées à la société «Valve» par un organisme habilité à exiger une réponse.\n\nNote de conclusionÀ la personne chargée de mener ce projet à bien\n\nNous tenons à remercier tous ceux qui veilleront à ce que ces documents parviennent à leur destination. Le chemin ne sera sans doute pas de tout repos. « Valve » dispose de moyens financiers considérables et le cabinet Taylor Wessing facture à l’heure — une combinaison spécialement conçue pour que des personnes comme vous abandonnent avant d’atteindre la ligne d’arrivée.\n\nNous savons ce que nous faisons. Nous savons de qui nous parlons. C'est «Valve» qui nous a façonnés — comment pourrions-nous ne pas les comprendre ?\n\nPhishDestroy n'est pas en conflit avec Valve. Nous avons démantelé le seul réseau d'escrocs de cette envergure que nous ayons rencontré — nous n'avons pas cherché à nous mettre en conflit avec Valve. Il s'est simplement avéré que toutes les pistes menaient à eux. Ce n'est pas un conflit. C'est juste une question de topologie.\n\nValve On ne peut pas régler le problème d’PhishDestroy, car il n’y a rien à régler. Nous n’avons aucune relation avec eux. Les informations concernant leurs stratagèmes d’enrichissement et leurs profits exorbitants sont en grande partie publiques — il suffisait simplement de passer suffisamment de temps à chercher pour les trouver. Considérez cela comme une encyclopédie du succès : « Comment ne pas respecter les sanctions afin que les hackers russes ne puissent pas pirater nos jeux gratuits (et les jeux payants, qu’ils ne pirateront de toute façon pas). » Vous voyez le genre.\n\nNous n'avons pas besoin de mentionner l'auteur.\n\nNous n'avons pas besoin de mentionner la source.\n\nOn n'a pas besoin de gagner.\n\nIl nous faut quelqu’un qui dispose d’une réelle autorité pour poser à Valve les questions qui figurent déjà dans cette saisine, et qui soit en mesure d’exiger une réponse.\n\nC'est tout. C'est tout ce qu'on vous demande.\n\nLes dossiers seront disponibles à l'adresse suivante :\n\nhttps://steamdestroy.eth/\n\nhttps://steamdestroy.eth.limo (actuellement hors service — sera réparé le moment venu)\n\nNous serons présents à :\n\nhttps://phishdestroy.eth.limo/ archivé 2026-06-27 ↗\n\nhttps://phishdestroy.eth/\n\nDeux objets signés · droits et texte publié\nDécharge signéeCe qui a été signé et ce que cela couvre\n\nL'octroi de droits et le texte de recherche sont présentés ci-dessous sous forme d'objets JSON signés séparément. Chaque signature «OpenPGP » distincte authentifie les octets exacts du fichier JSON dont le nom figure à côté. La déclaration de droits accorde des autorisations ; l'instantané du texte identifie et contient le contenu publié.\n\n1. Déclaration relative aux droits — license-rights.json\n\nObjet signé : l'intégralité license-rights.json fichier contenant la licence de droits publics datée du 28 septembre 2026.. Celle-ci autorise la copie, la publication, la modification, la traduction, la combinaison et la commercialisation des éléments du dossier sans mention de la source, sans notification ni autorisation préalable. Cette signature authentifie la déclaration de droits ; elle n'authentifie pas le texte de chaque page web ou fichier PDF.\n\nLa licence originale signée est conservée telle quelle. L'autorisation qu'elle accorde ne peut être retirée ni restreinte par une modification du site web, la publication d'un autre fichier ou la mise hors ligne du site. Les contenus provenant de tiers conservent leurs propres droits.\n\nDéclaration des droits au format JSON ↗ · Signature d'license-rights.json ↗ · SHA-256, de license-rights.json ↗\n\ngpg --verify license-rights.json.asc license-rights.json\nsha256sum -c license-rights.json.sha256\n2. Texte publié — dossier-text.json\n\nObjet signé : l'intégralité dossier-text.json fichier. Il contient le texte lisible des pages exportées dans documents[].content.text, avec le titre de chaque page, la langue, l'URL source, le hachage HTML source, les titres et les références. Le documents Cette liste correspond exactement au catalogue couvert par cet instantané ; les variantes linguistiques sont répertoriées séparément. Il s'agit d'une publication textuelle, et non d'une simple liste de hachages.\n\nChaque entrée identifie son fichier PDF de page allégée par son nom de fichier et son SHA-256e dans documents[].pdf. Le fichier JSON identifie également la déclaration de droits d'origine à l'aide d'une URL et d'un SHA-256,, ce qui permet de faire correspondre sans ambiguïté le texte publié, son fichier PDF et la cession de droits applicable. Les bases de données externes liées, les images originales et les pages absentes de l'inventaire ne sont pas intégrées dans cet instantané du texte.\n\nTexte JSON complet et signé ↗ · Signature d'dossier-text.json ↗ · SHA-256ion de dossier-text.json ↗\n\ngpg --verify dossier-text.json.asc dossier-text.json\nsha256sum -c dossier-text.json.sha256\n\nSur la page d'accueil du dossier, les boutons « PDF » et « JSON » permettent d'exporter l'ensemble de recherche. Sur une page intérieure, ils permettent d'exporter cette page dans la langue dans laquelle elle a été publiée. Chaque fichier JSON de page dispose également de sa propre signature indépendante et d'un fichier SHA-256, dont le nom est explicitement indiqué dans son integrity objet. Pour vérifier le fichier PDF associé, calculez sa valeur SHA-256, puis comparez-la avec celle du pdf.sha256 valeur dans le fichier JSON vérifié. Le PDF est lié à ce résumé ; il ne comporte pas de signature numérique au format PDF.\n\n3. Dossier de recherche imprimable — steam-dossier-{language}.content.json\n\nObjet signé : le fichier JSON complet spécifique à la langue, comprenant le texte du chapitre intégré dans documents[].content.text, les plages de pages des chapitres, les langues sources, la liste des sources exclues et le résumé exact au format PDF dans pdf.sha256. Les cinq archives de documents complémentaires restent accessibles en ligne et ne sont pas regroupées. Les textes de recherche rédigés sont conservés ; les catalogues visuels sont remplacés par des liens vers les sources.\n\nJSON en anglais ↗ · Signature détachée d'OpenPGP ↗ · Résumé du digest SHA-256 ↗\n\nAllemand JSON ↗ · Signature détachée d'OpenPGP ↗ · Résumé du digest SHA-256 ↗\n\ngpg --verify steam-dossier-en.content.json.asc steam-dossier-en.content.json\nsha256sum -c steam-dossier-en.content.json.sha256\n\nClé de vérification publique ↗\n\nEmpreinte de signature : 129F C7F3 9C40 C69D 2EF3 C329 BFCF 9E8D D295 EE01\n\ngpg --import pgp-key.txt\ngpg --fingerprint 129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01\n\nVérifiez que l'empreinte digitale affichée correspond à celle ci-dessus, puis comparez la signature au nom exact du fichier JSON. La modification d'un fichier JSON signé modifie l'objet signé et invalide sa signature d'origine. Une signature valide identifie les octets publiés ; elle ne constitue pas une vérification indépendante des résultats de la recherche.\n\nPhishDestroy — enquête publique — tous les droits cédés à l'humanité\n\nAccès à la région OFAC : interdit",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Licence et mentions légales — Mise au domaine public"
          },
          {
            "level": 2,
            "id": null,
            "text": "Section ILicence — l'aspect juridique proprement dit, mais d'un point de vue humain"
          },
          {
            "level": 3,
            "id": null,
            "text": "Une règle concrète (oui, une seule)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Section IIDe quoi s'agit-il et pourquoi existe-t-il ?"
          },
          {
            "level": 2,
            "id": null,
            "text": "Section IIILettre ouverte à Valve — Sérieusement, lis ça"
          },
          {
            "level": 3,
            "id": null,
            "text": "La transaction (offre publique, pas besoin d'avocats)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Section III-BLes ressources associées — une note adressée spécifiquement à Steam"
          },
          {
            "level": 2,
            "id": null,
            "text": "Section IVL'argent, les interdictions, tout ce cirque"
          },
          {
            "level": 2,
            "id": null,
            "text": "Section VLe problème des logiciels malveillants — oui, on en parle"
          },
          {
            "level": 2,
            "id": null,
            "text": "DéclarationEn ce qui concerne l'utilisation et les droits"
          },
          {
            "level": 3,
            "id": null,
            "text": "1. Il n'y a aucune condition d'utilisation"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. Pourquoi cela a de l'importance sur le plan pratique, et pas seulement par simple courtoisie"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. Tout est déjà ouvert"
          },
          {
            "level": 3,
            "id": null,
            "text": "4. Intégrité de l'ensemble des éléments de preuve"
          },
          {
            "level": 3,
            "id": null,
            "text": "5. À propos de l'enregistrement — pourquoi cette dérogation est-elle fonctionnelle et ne relève-t-elle pas simplement de la générosité ?"
          },
          {
            "level": 3,
            "id": null,
            "text": "6. Ce que propose la Coalition, selon ses propres termes"
          },
          {
            "level": 2,
            "id": null,
            "text": "Note de conclusionÀ la personne chargée de mener ce projet à bien"
          },
          {
            "level": 2,
            "id": null,
            "text": "Décharge signéeCe qui a été signé et ce que cela couvre"
          },
          {
            "level": 3,
            "id": null,
            "text": "1. Déclaration relative aux droits — license-rights.json"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. Texte publié — dossier-text.json"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. Dossier de recherche imprimable — steam-dossier-{language}.content.json"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/fr/#briefing-heading",
          "https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "http://web.archive.org/web/20260821155801/https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "https://phishdestroy.io/steam_dossier/fr/investigation_part2.html#outsourcing-case",
          "https://phishdestroy.io/steam_dossier/fr/#theft-ledger",
          "https://steamid.uk/",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/groups/steambans",
          "https://steamcommunity.com/id/killahinstinct_",
          "https://phishdestroy.io/steam_dossier/fr/card_economy.html#governance",
          "https://phishdestroy.io/steam_dossier/fr/license_disclaimer.html",
          "https://github.com/phishdestroy",
          "http://web.archive.org/web/20260911040557/https://github.com/PhishDestroy",
          "https://phishdestroy.io/.well-known/pgp-key.txt",
          "https://steamdestroy.eth/",
          "https://steamdestroy.eth.limo/",
          "https://phishdestroy.eth.limo/",
          "http://web.archive.org/web/20260627040219/https://phishdestroy.eth.limo/",
          "https://phishdestroy.eth/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json.asc",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json.sha256",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json.sha256?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json.sha256?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json.sha256?v=print-20260928-v3"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/fr/license_disclaimer.content.json",
      "export_json_sha256": "f926b0ddcc1ad4220be8b3e61a7445c8fe249d3a9e47c9a174052c152b75bcab"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "fr/market_economics.html",
      "language": "fr",
      "title": "Une infrastructure, deux marchés — Le dossier «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/fr/market_economics",
      "source_html_sha256": "8ade17d44b232b207296f98babb70f8f2c1af0f858357ea2770e57811b190288",
      "exported_at": "2026-09-29T00:17:37.858Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "market_economics.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/fr/market_economics.pdf?v=print-20260929-v5",
        "sha256": "afcdb4d35a27756d39043f984680d6569b781a1c8c3a88a666c0cfc69f6b6d73",
        "bytes": 101905,
        "pages": 8
      },
      "integrity": {
        "signed_object": "market_economics.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "market_economics.content.json.asc",
        "digest_file": "market_economics.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify market_economics.content.json.asc market_economics.content.json",
          "sha256sum -c market_economics.content.json.sha256"
        ]
      },
      "content": {
        "text": "Annexe VII · Architecture du marché · 20 septembre 2026\nÉconomie de marché — Deux économies et le plafond des cotations\n\nLeur infrastructure. Deux économies.\n\nCE QUE CETTE SECTION DÉMONTRERA\n\nCe chapitre analyse la bifurcation systémique du marché engendrée par le plafond de cotation de Valve, fixé à $1,800, et par les soldes de portefeuille non retirables. En passant en revue 38 les plateformes externes actives d’échange de skins, représentant une valeur boursière d’environ1.28 milliards de dollars, l’enquête démontre que les transactions de haut niveau migrent inévitablement vers des plateformes parallèles externes, tout en s’appuyant sur l’infrastructure sous-jacente de transaction et d’authentification d’Steam. Bien que l’utilisation commerciale soit formellement interdite dans le contrat d’abonnement, Valve facilite et monétise cette économie à deux vitesses sans publier de rapports sur l’application de ces règles.\n\n← Retour au dossier de synthèse destiné aux dirigeants\n\n38 les places de marché CS2 tierces actives, ainsi que celle d'Steam. Chaque skin répertorié sur l'un de ces sites doit transiter par l'inventaire d'Steam et le site d'échange API. Les règles d'Valve interdisent l'exploitation commerciale de cette infrastructure. La valeur estimée à environ1.28 milliards de dollars attribuée par des tiers est avérée, bien qu'aucun document public attestant de l'application de cette règle n'ait été retrouvé.\n\n$1.28B\nValeur estimée par des tiers · Plateformes de «38 »\n53.2M\nOffres affichées · Marchés tiers d'38\n70.1K\nSteam éléments figurant dans l'aperçu\n41×\nValeur cotée par un tiers par rapport aux $31M d'Steam\nLa conclusion principale\nUne infrastructure. Deux économies.\n\nSteam contrôle le produit, le stock et les échanges. Chaque skin vendu sur l’une des plateformes ci-dessous doit passer par la plateforme d’échange Steam API — une dépendance structurelle directement observable. Le « Community Market » de Valve perçoit une commission sur ses ventes ; il n'est pas précisé ici si cette commission finance l' écosystème tiers ou si elle y est liée.\n\nEn quoi cela est-il important pour l'enquête ?\n1\nContrat d'abonnement à « Steam » de Valve interdit l'exploitation commerciale de l'infrastructure d'Steams sans autorisation expresse. Aucune autorisation de ce type n'a été trouvée dans les documents publics concernant les plateformes ci-dessous.\n2\nSteam gère l'identité (OpenID), l'état des stocks et l'exécution des transactions pour une valeur cotée auprès de tiers d'environ1.28milliards de dollars. Aucun transfert de marchandises ne peut avoir lieu sans l'infrastructure d'Valve.\n3\nLa place de marché de Steam propose $31M cotés — soit environ l’1/41e de la valeur cotée par des tiers. Le plafond de prix fixé à1,800 $ signifie que les vendeurs dont le prix est supérieur à ce montant doivent sortir de la plateforme pour vendre aux prix observés.\n4\n248 Catégories d'objets CS2, dont le prix a été fixé par au moins deux places de marché indépendantes au-delà du plafond, ne peuvent pas être vendus à leur prix de marché observé sur Steam — et aucun d’entre eux n’y est d’ailleurs référencé. C’est le plafond de $1,800 qui génère la demande à laquelle répondent les opérateurs tiers.\nSteam Marché communautaire :31M $Valeur estimée par des tiers :1,276M de dollars\n1,276M $ · valeur indiquée par un tiers — tout dépend de la transaction d'Steam API et OpenID\nSteam ·31millions de dollars\n\nSource : catalogue en temps réel de PriceEmpire, 20 septembre 2026. Valeur catalogue = somme des valeurs catalogue arrondies figurant dans l'instantané enregistré, à l'exclusion de Steam. Ne correspond pas au volume des ventes.\n\n38 marchés tiers actifs · Tout dépend de l'infrastructure d'Steam\nRegistre de la plateforme\n\nLes plateformes ci-dessous acheminent leurs connexions via l'OpenID d'Steam et leurs transactions via le Web API d'Steam. Chacune d'entre elles a été observée openid.realm passe par le processus de connexion d'Steam ; le registre consigne les routes d'authentification observées plutôt que d'affirmer qu'un opérateur donné ne dispose pas de l'autorisation d'Valve.\n\n#\tPlateforme\tValeur cotée\tOffres en cours\tArticles\tÉchelle\n1\tUUSkins\t$133.8M\t3.4M\t30.9K\t\n\n2\tYouPin898\t$127.5M\t5.9M\t29.2K\t\n\n3\tBuff.163\t$104M\t3.5M\t35K\t\n\n4\tMoon.Market\t$100.3M\t2.9M\t20.9K\t\n\n5\tWhite.Market\t$89.6M\t3M\t20.6K\t\n\n6\tBuff.Market\t$86.7M\t1.3M\t33.4K\t\n\n7\tEcosteam\t$82.1M\t3.3M\t30.1K\t\n\n8\tCSFloat\t$67.8M\t2.4M\t27.8K\t\n\n9\tSkin.Land\t$67.4M\t2.2M\t34.6K\t\n\n10\tLIS-SKINS\t$67.4M\t2.2M\t34.6K\t\n\n11\tC5Game\t$54.6M\t4.6M\t29.6K\t\n\n12\tHaloSkins\t$46.6M\t4.4M\t29.3K\t\n\n13\tAvan.Market\t$43.3M\t809.5K\t22.2K\t\n\n14\tWaxpeer\t$40.1M\t1M\t27.3K\t\n\n15\tSteam (official)\t$31M\t32.2M\t70.1K\t\n\n16\tCS.MONEY\t$29M\t748.9K\t28K\t\n\n17\tMarket.CSGO\t$26.3M\t1.3M\t27.6K\t\n\n18\tCS.MONEY Bot\t$25.7M\t614K\t23.8K\t\n\n19\tSkinport\t$16.3M\t3.8M\t31.1K\t\n\n20\tSkinFlow\t$14.1M\t481.8K\t23.6K\t\n\n21\tDMarket\t$12.6M\t948.2K\t35.6K\t\n\n22\tSkins.com\t$11.5M\t83.2K\t15.8K\t\n\n23\tSkin.place\t$6.9M\t380.8K\t11.4K\t\n\n24\tSkinsMonkey\t$6M\t109.4K\t11.6K\t\n\n25\tSkinBaron\t$5M\t2.1M\t21.5K\t\n\n26\tRustTM\t$3M\t33.1K\t4.9K\t\n\n27\tPirateSwap\t$2M\t859.3K\t10.5K\t\n\n28\tMannco.Store\t$1.2M\t223.7K\t11K\t\n\n29\tSkinSwap\t$1.1M\t11.4K\t4K\t\n\n30\tTradeIt\t$967.1K\t29.1K\t11.7K\t\n\n31\tLootFarm\t$896.1K\t162.5K\t28.6K\t\n\n32\tRustskins\t$714.8K\t312.5K\t6.1K\t\n\n33\tBalticSkins\t$599.2K\t28.2K\t4.5K\t\n\n34\tExeSkins\t$442.9K\t2.6K\t1.4K\t\n\n35\tRapidSkins\t$230.9K\t11.6K\t2.3K\t\n\n36\tCS.Trade\t$203K\t19K\t16.7K\t\n\n37\tKrakatoa\t$11.1K\t115\t53\t\n\n38\tShadowPay\t—\t—\t—\t—\n39\t49skins\t—\t—\t—\t—\nLe plafond de prix de Steam fixé à1,800 dollars · Aperçu de cinq places de marché · 23 septembre 2026\nL'écart de prix est quantifiable.\n\nSteam limite les cotations du « Community Market » à environ $1,800 (ce chiffre a été recalculé à $2,000, $, $2,070, $, $2,300 et $2,500 dans cs2sh-atlas.json et se maintient à chaque seuil). Les articles dont le prix est supérieur à ce seuil ne peuvent pas être vendus à leur prix de marché via la plateforme de vente en ligne d'Valve — mais ils dépendent toujours du système de gestion des stocks et des transferts d’Steam, quel que soit le lieu de vente. Le classement de l’ensemble du catalogue par prix met en évidence les limites du système : le marché d’Valve propose 95.3% des catégories d'articles dont le prix est inférieur à son plafond et 1.9% parmi ceux qui se trouvent au-dessus.\n\nCinq places de marché : articles dépassant le plafond fixé par l'Steam\n248\n\nCatégories d'articles dont le prix de vente le plus bas dépasse1,800 le deux ou plusieurs places de marché de manière indépendante, détenant des exemplaires répertoriés dans l’18,394, d’une valeur d’au moins $78.6M. Parmi ceux-ci, 100.0% — sans exception — ne figurent absolument pas sur la liste de l' Steam.\n\nPièces à conviction complètes : le registre → · l'atlas des échelles de prix →\n\nRépartition des prix au-delà du plafond\n$1,800–$5,000\n174\n$5,000–$10,000\n49\n$10,000–$25,000\n21\n$25,000–$50,000\n2\n$50,000+\n2\nMeilleures offres — prix vendeur vérifié le plus bas sur cinq places de marché\n1Autocollant | Titan (Holo) | Réf. «14 »$66,285\n2Autocollant | iBUYPOWER (Holo) | Réf. «14 »$64,795\n3Autocollant | Reason Gaming (Holo) | Réf. «14 »$42,899\n4★ Gants de sport | Labyrinthe de haies (FN)$26,812\n5Autocollant | Team Dignitas (Holo) | Réf. «14»$23,667\n6EMS Cat. « Légendes de l'14 »$22,879\n7★ Gants de sport | La boîte de Pandore (FN)$21,643\n8EMS Cat. «14 » Challengers$21,010\n9Autocollant | Vox Eminor (Holo) | Réf. «14 »$18,619\n10★ Couteau StatTrak™ Navaja | Blue Steel (FN)$18,064\n\nLes prix demandés ne correspondent pas aux prix de vente. Extrait de cs2.sh (sous licence), 23 septembre 2026. Chaque ligne correspond à un prix proposé par au moins deux places de marché indépendantes, supérieur au plafond ; les offres à volume unique et les prix supérieurs à trois fois le prix demandé le plus bas pour un article sont exclus. Comment fonctionne la notation →\n\nTarifs d'Valve · Aperçu d'cs2.sh, site agréé · 23 septembre 2026\nLes honoraires indiqués sont de 15%.. La plupart des annonces offrent des rémunérations plus élevées.\n\nValve prélevé des frais de 5% Steam et des frais d'éditeur CS2 de 10% sur les recettes du vendeur — le bien connu 15%. Ces deux types de frais s'accompagnent d'un 0.01s de dollars minimum, de sorte qu'aucune vente ne peut jamais générer moins de deux centimes de frais. Pour les articles bon marché et vendus en grande quantité, qui constituent l'essentiel du marché, c'est ce seuil minimum qui constitue la contrainte déterminante, et non le pourcentage. Nous avons résolu le calcul des frais pour chacun des 29,635 types d'articles faisant l'objet d'une demande d'Steam.\n\n77.7%\nLes annonces en ligne d'Steams figurent dans les catégories de produits facturées sur 15%\n84.8%\nde l'article types versez bien un salaire proche du taux affiché\n4,517\ncertains types d'articles ont fait l'objet d'une facturation supérieure au tarif annoncé\n$0.02\nfrais minimums sur toute vente, quel que soit le prix\nCes deux chiffres indiquent des tendances opposées, et les deux sont vrais\n1\nCompté par type d'article, Les tarifs d'Valve correspondent globalement à ceux annoncés : 84.8%. Les types de tarifs indiqués sur le site 29,635 sont facturés à un prix égal ou proche de celui indiqué sur 15%.\n2\nCompté par annonce effective, la situation s'inverse : 18,682,244 de 24,038,911 Les annonces en ligne concernent les types d'articles dont le prix est supérieur à 15%.\n3\nCes deux affirmations sont vraies, car les types surchargés sont les bon marché, en grande quantité ceux-là. 1,109 Les types d'articles sont facturés plus cher que double le taux de référence, et ces catégories à elles seules comptent 14,083,486 annonces en ligne.\n4\nIl s'agit là d'un simple calcul, et non d'une allégation. Le montant minimum est indiqué dans la documentation relative aux honoraires d'Valve. Ce qui n'a pas été publié, c'est quelle part du marché cela concerne réellement — ce que mesurent justement les chiffres ci-dessus.\nFrais facturés, exprimés en pourcentage de l'15% brute\n200%+\n14,083,486\n100-200%\n1,028,438\n50-100%\n700,804\n30-50%\n317,031\n20-30%\n2,258,254\n17.6-20%\n294,231\n\nLa « longueur de la barre » correspond au nombre d'annonces actives dans chaque tranche. Une tranche «200%+ » signifie que les frais prélevés représentent plus du double de 15% du produit de la vente du vendeur.\n\nUn exemple détaillé\n67%\n\nLors d'une mise en vente, l'acheteur paie $0.03 car le vendeur reçoit $0.01 et « Valve » prend $0.02 — les deux montants minimaux d'un cent. En pourcentage du montant payé par l'acheteur, cela représente 67% ; en pourcentage du produit de la vente perçu par le vendeur, cela représente 200%.\n\nEnsemble de données complet : cs2sh-steam-fee-census.json →\n\nLe même objet, à l'intérieur du jardin et à l'extérieur de celui-ci\nAcheter sur Steam coûte plus cher. Presque toujours.\n\nPour chaque article référencé à la fois sur Steam et sur au moins une plateforme de vente en ligne tierce, nous avons comparé le prix de vente le plus bas proposé par Steam avec le prix de vente le plus bas proposé en dehors de ce site. Sur l'ensemble des 28,700 En ce qui concerne les articles, Steam est le site le plus cher. 86.4% la plupart du temps, avec une médiane de +35.7%.\n\nPrime médiane d’Steam, par tranche de prix\nmoins de0.50 de dollars\n+48.3%\n$0.50-2\n+36.5%\n$2-10\n+29.6%\n$10-50\n+28.6%\n$50-250\n+36.3%\n$250-1k\n+51.1%\nplus de1,000 de dollars\n+67.9%\n\nLa courbe a la forme d'un U. C'est sur Steam que les prix sont les plus bas dans la $10–$50 « band » et « dearest » aux deux extrémités.\n\nPourquoi le segment haut de gamme est-il si important ?\n+67.9%\n\nCi-dessus $1,000, le coût médian d'une annonce sur Steam 67.9% est supérieur à celui de l'offre la moins chère proposée en dehors de ce site — et il n'existe que 1,040 annonces de ce type sur Steam.\n\nAu-delà d’environ1,800, la comparaison n’est plus possible, car la règle de Valve interdit totalement leur référencement. La couverture par Steam des articles dont le prix dépasse son propre plafond est 1.9%. Voir le classement complet →\n\nEnsemble de données complet : cs2sh-walled-garden-premium.json →\n\nUne prime ne constitue pas en soi une conclusion : Steam propose une livraison immédiate et n'implique aucun risque de contrepartie, et les acheteurs peuvent raisonnablement être prêts à payer pour cela. Ce qui est mesurable, c'est l'ampleur de l'écart et le fait que l'argent qui le franchit ne puisse plus en ressortir — ce qui fera l'objet de la section suivante.\n\nDe l'argent qui rentre, pas d'argent qui sort\n128.1s de dollars engagés dans des commandes irrévocables.\n\nUn ordre d'achat sur Steam est préfinancé : l'argent est débité du portefeuille de l'acheteur dès que l'ordre est passé. Steam fonds du portefeuille ne peut être retiré — ils ne peuvent être dépensés qu'au sein d' Steam. En additionnant tous les niveaux de prix du carnet d'ordres d'achat de chaque actif suivi, on obtient un relevé des fonds engagés et non retirables.\n\n$128.1M\nengagé à honorer les ordres d'acheSteam\n170.6M\nordres d'achat individuels financés en attente\n$105.8M\nvaleur demandée des biens immobiliers qui leur sont proposés\n$15.9M\nLa commission de Valve si toutes les annonces étaient vendues au prix demandé\nCe qu'est ce chiffre, et ce qu'il n'est pas\n1\nC'est sommes réelles déjà versées. Chaque dollar comptabilisé a été débité d'un portefeuille et est affecté à un ordre ouvert, tous types d'articles d'31,253s confondus.\n2\nC'est et non pas le chiffre d'affaires et non une affirmation concernant le bilan d'Valve. Le lieu où sont détenus les fonds en circulation, ni dans les comptes de qui, n'est pas précisé ici.\n3\nC'est un un instantané, pas un flux. L'acheteur peut annuler ses commandes, ce qui entraîne le remboursement des fonds sur le portefeuille — mais ceux-ci ne sortent toujours pas d'Steam.\n4\nLe problème, c'est cette porte à sens unique. Un marché dont la monnaie ne peut pas être convertie en argent réel, voilà pourquoi un stock volé est revendu. désactivé Steam plutôt que dessus.\n\nMéthode : chaque niveau de prix de chaque carnet d'ordres d'achat suivi, multiplié par les ordres en attente à ce niveau. Ensemble de données complet : cs2sh-steam-locked-capital.json →\n\nVentes conclues, et non prix demandés · une seule plateforme · données sur l’90s des derniers jours\n30.9 millions de dollars ont effectivement changé de mains — sur la plus petite des cinq étagères.\n\nUne vente à prix élevé isolée peut correspondre à un objet artisanal rare ou à une variante d'un objet de base bon marché comportant un autocollant (par e.g, un objet à30 $ ayant fait l'objet d'une vente unique à9,772 $). « Élevé » désigne ici la transaction la plus élevée conclue, et non le prix normal de l'objet.\n\nTous les autres chiffres de cette page correspondent à ce qui est répertorié. Celui-ci mesure ce qui était vendu. Le site Skinport publie ses propres transactions finalisées, et au cours des 90 derniers jours celles-ci se sont élevées à 1,219,143 ventes valeur $30,927,032, à raison de25.37s de dollars en moyenne chacun.\n\n1.22M\nventes conclues en90 jours, sur une seule plateforme de vente en ligne\n$30.9M\nchiffre d'affaires sur la même période\n$125M\ntaux annualisé — un seuil minimal, et non une estimation\n~2%\nPart de Skinport dans le programme de placement continu au-delà du plafond, en valeur cotée\nD'où provenait le chiffre d'affaires ?\nmoins de1 de dollars\n0.5%\n$1-10\n5.8%\n$10-100\n22.2%\n$100-1k\n59.4%\n$1k-1.8k\n6.9%\nau-delà du plafond fixé par la loi «Steam»\n5.3%\n\nLa longueur de la barre correspond au chiffre d'affaires ; ce chiffre représente la part de ce niveau par rapport au total. 59.4% de l'argent généré dans la catégorie $100–$1k, sur 71,437.\n\nMême au-delà du plafond fixé par la «Valve », les ventes se poursuivent\n492\n\nventes réalisées d'articles dont le prix dépassait le plafond fixé par l'Steam, pour un montant de $1,643,938, parmi les différents types d’articles d’ 76 — sur une place de marché qui occupe environ 2% de cet espace de vente. Aucune de ces ventes n’aurait pu avoir lieu sur Steam.\n\nEnsemble de données complet : cs2sh-offsteam-90d-dynamics.json → · les plus hauts atteints →\n\nSkinport Il s'agit de L'UN des marchés tiers suivis ici, et avec une valeur de cotation supérieure au plafond de l'Steam, c'est le plus petit des cinq (environ 2% de ce segment). Chaque total indiqué ici correspond à un seuil minimal de l'économie horsSteam, et non à une mesure de celle-ci. Aucune donnée de l'Steam n'est utilisée.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Économie de marché — Deux économies et le plafond des cotations"
          },
          {
            "level": 2,
            "id": null,
            "text": "Une infrastructure. Deux économies."
          },
          {
            "level": 2,
            "id": null,
            "text": "Registre de la plateforme"
          },
          {
            "level": 2,
            "id": null,
            "text": "L'écart de prix est quantifiable."
          },
          {
            "level": 3,
            "id": null,
            "text": "Cinq places de marché : articles dépassant le plafond fixé par l'Steam"
          },
          {
            "level": 3,
            "id": null,
            "text": "Répartition des prix au-delà du plafond"
          },
          {
            "level": 3,
            "id": null,
            "text": "Meilleures offres — prix vendeur vérifié le plus bas sur cinq places de marché"
          },
          {
            "level": 2,
            "id": null,
            "text": "Les honoraires indiqués sont de 15%.. La plupart des annonces offrent des rémunérations plus élevées."
          },
          {
            "level": 3,
            "id": null,
            "text": "Frais facturés, exprimés en pourcentage de l'15% brute"
          },
          {
            "level": 3,
            "id": null,
            "text": "Un exemple détaillé"
          },
          {
            "level": 2,
            "id": null,
            "text": "Acheter sur Steam coûte plus cher. Presque toujours."
          },
          {
            "level": 3,
            "id": null,
            "text": "Prime médiane d’Steam, par tranche de prix"
          },
          {
            "level": 3,
            "id": null,
            "text": "Pourquoi le segment haut de gamme est-il si important ?"
          },
          {
            "level": 2,
            "id": null,
            "text": "128.1s de dollars engagés dans des commandes irrévocables."
          },
          {
            "level": 2,
            "id": null,
            "text": "30.9 millions de dollars ont effectivement changé de mains — sur la plus petite des cinq étagères."
          },
          {
            "level": 3,
            "id": null,
            "text": "D'où provenait le chiffre d'affaires ?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Même au-delà du plafond fixé par la «Valve », les ventes se poursuivent"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/fr/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/fr/elite_skins.html",
          "https://phishdestroy.io/steam_dossier/fr/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/fr/skin_atlas.html#grading",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-steam-fee-census.json",
          "https://phishdestroy.io/steam_dossier/fr/skin_atlas.html#cliff",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-walled-garden-premium.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-steam-locked-capital.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-offsteam-90d-dynamics.json",
          "https://phishdestroy.io/steam_dossier/fr/skin_atlas.html#highs"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/fr/market_economics.content.json",
      "export_json_sha256": "ffd58c2673a47d2fa2fe2ebf85eda468e88ba5f37f980becb7a1c02cb002fd9f"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "fr/regulatory_act_print.html",
      "language": "fr",
      "title": "LOI SUR L'AUDIT JUDICIAIRE : Valve Steam Site web API Écosystème et exploitation commerciale (Réf. : VAL-REG-2026-09)",
      "source_url": "https://phishdestroy.io/steam_dossier/fr/regulatory_act_print",
      "source_html_sha256": "35b6ac93f024844c99fc2f35e441cbfdaa971c6e1b0f7e48c3ae8ffe5ca14368",
      "exported_at": "2026-09-29T00:17:38.405Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "regulatory_act_print.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/fr/regulatory_act_print.pdf?v=print-20260929-v5",
        "sha256": "ff7b0fee3799ce66d9ba8aeb8bab28a17e41c0032a90307cc8c316aeb9fc82c3",
        "bytes": 186929,
        "pages": 14
      },
      "integrity": {
        "signed_object": "regulatory_act_print.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "regulatory_act_print.content.json.asc",
        "digest_file": "regulatory_act_print.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify regulatory_act_print.content.json.asc regulatory_act_print.content.json",
          "sha256sum -c regulatory_act_print.content.json.sha256"
        ]
      },
      "content": {
        "text": "phishdestroy.io · Coalition pour la recherche médico-légale · Registre public universel\nDOSSIER : VAL-REG-2026-09-EVID\nPROVENANCE : phishdestroy.io/steam_dossier/\nDROITS : TOUS LES DROITS CÉDÉS À L'HUMANITÉ\nLoi sur l'audit judiciaire et annexe réglementaire\nMise à disposition systématique d’APIs par des tiers, architecture de contournement automatisée et non-application des clauses contractuelles au sein de l’écosystème « Valve » (Steam)\nDomaine d'émissionphishdestroy.io\nPlateforme cibleValve Steam / Steamworks\nVecteur d'authentification principalSteam OpenID 2.0 / Site web API\nMention légaleAll Rights to Humanity (CC0)\nSection I : Note de service de la direction et constatations factuellesRÉF. : MEMO-SUMMARY-01\n\nLe présent document constitue un rapport d’audit judiciaire officiel examinant les recoupements opérationnels entre les conditions commerciales publiées par la société « Valve », ses points d’authentification techniques et les plateformes commerciales tierces observées. L’audit a été réalisé à l’aide d’une observation passive et non authentifiée du réseau, d’une vérification des enregistrements de lRDAP, ainsi que des données télémétriques publiques de Link Filter.\n\nEssence factuelle : Des observations empiriques mettent en évidence une divergence systématique entre les déclarations contractuelles publiques d’Valve et son infrastructure de production. Alors que le contrat d’abonnement d’Steam (SSA) interdit strictement l’exploitation commerciale non autorisée (§ 2.G), les interactions automatisées par des bots ou des scripts (§ 4.C) et le transfert de comptes (§ 1.C), la société Valve continue de fournir une infrastructure programmatique en temps réel d’authentification OpenID et de consultation d’inventaire à au moins 175 entités commerciales générant des volumes de transactions secondaires de plusieurs milliards de dollars.\n\n175\nOpérateurs commerciaux ayant fait l'objet d'un audit\n44\nHôtes d'authentification à domaine distinct\n26\nPaires de proxys à filtrage partagé\n100%\nArticles non appliqués de la loi SSA : § 2.G / § 4.C\n0\nRévocations d'authentification imposées\nCadre contractuel et réglementaire applicable\nSSA § 2.G\nInterdiction d'utilisation à des fins commerciales : Il est formellement interdit d'exploiter le Contenu et les Services à des fins commerciales sans l'autorisation écrite préalable de la société « Valve ».\nSSA § 4.C\nRestriction relative à l'automatisation : Il est strictement interdit d'utiliser des scripts, des robots de trading, des macros ou tout autre système non contrôlé par un être humain pour interagir avec les services et les marchés d'Steam.\nSSA § 1.C\nObligation d'utilisation à des fins personnelles : Limite l'utilisation des comptes à un usage personnel ; interdit expressément la vente, la location, le transfert ou l'échange de comptes d'utilisateurs d'Steam.\nLoi européenne sur les services numériques (DSA) 2022/2065\nÉvaluation des risques systémiques (art. 34/35) : Les très grandes plateformes en ligne (VLOP) doivent détecter, évaluer et atténuer activement les risques systémiques découlant d'une utilisation abusive automatisée et d'une exploitation commerciale non autorisée.\nSection II : Registre des pièces A — Paires de filtrage de liens documentées (itinéraires « 26 »)RÉF. : EX-SPLIT-LEDGER\n\nAnalyse médico-légale des techniques d'évasion par division de domaine : Dans le cadre du système de filtrage de liens « Steam » d'Valve (steamcommunity.com/linkfilter/?url=...), lorsqu'un utilisateur final clique sur un lien menant à une plateforme de jeux d'argent ou de marché noir signalée, Valve affiche un avertissement bien visible (« Lien bloqué ! ... signalé comme potentiellement malveillant »). Toutefois, l'analyse judiciaire des chemins de transmission révèle que des plateformes commerciales 26 opèrent sur un architecture à domaines séparés: alors que le domaine commercial principal est BLOQUÉ par le filtre de liens, le domaine secondaire hébergeant le point de terminaison de retour OpenID de Valve est marqué comme « CLEAN ». Les serveurs OpenID de Valve acceptent sans interruption les demandes d'authentification provenant de ces hôtes proxy, ce qui neutralise l'avertissement de sécurité destiné aux utilisateurs tout en continuant à traiter les connexions.\n\n#\tDomaine commercial principal\tFiltre principal\tDomaine du proxy d'authentification OpenID\tFiltre d'authentification\tRDAP Inscrit\tBase de comptabilisation\n01\trollbit.com\tBLOCKED\trbsnin.com\tCLEAN\t2026-09-18\tPASSIVE_CAPTURE\n02\tskin.club\tBLOCKED\tsc-auth.net\tCLEAN\t2019-04-02\tPASSIVE_CAPTURE\n03\thowl.gg\tBLOCKED\thowl.uno\tCLEAN\t2026-08-11\tPASSIVE_CAPTURE\n04\tduelbits.com\tBLOCKED\tswitchflips.com\tCLEAN\t2020-04-21\tPASSIVE_CAPTURE\n05\tcsgofast.com\tBLOCKED\tsteam-login.authtofast.com\tCLEAN\t2026-06-30\tPASSIVE_CAPTURE\n06\tfarmskins.com\tBLOCKED\tsteam.kobal.cc\tCLEAN\t2017-01-07\tPASSIVE_CAPTURE\n07\tcobaltlab.tech\tBLOCKED\tcobaltauth.com\tCLEAN\t2025-01-07\tPASSIVE_CAPTURE\n08\tcsgo.net\tBLOCKED\tcn2.easylot.net\tCLEAN\t2016-09-03\tPASSIVE_CAPTURE\n09\tggdrop.com\tBLOCKED\tggauth.com\tCLEAN\t2023-05-03\tPASSIVE_CAPTURE\n10\trustchance.com\tBLOCKED\thgfuihd.com\tCLEAN\t2019-01-27\tPASSIVE_CAPTURE\n11\tskin.fans\tBLOCKED\tauth.skinfans.com\tCLEAN\t2018-07-16\tPASSIVE_CAPTURE\n12\tskinport.com\tBLOCKED\tskinport.app\tCLEAN\t2020-06-20\tPASSIVE_CAPTURE\n13\tskins.cash\tBLOCKED\tskinscash.live\tCLEAN\t2019-12-05\tPASSIVE_CAPTURE\n14\ttf2hunt.com\tBLOCKED\trstspcl.com\tCLEAN\t2020-08-08\tPASSIVE_CAPTURE\n15\tdaddyskins.com\tBLOCKED\tgo-go-daddy.com\tCLEAN\t2019-01-26\tPASSIVE_CAPTURE\n16\tkey-drop.com\tBLOCKED\tkdauth.com\tCLEAN\t2026-05-13\tPASSIVE_CAPTURE\n17\tclash.gg\tBLOCKED\tclggauth.com\tCLEAN\t2024-09-16\tPASSIVE_CAPTURE\n18\tc5game.com\tBLOCKED\twww.imbastar.com\tCLEAN\t2016-02-27\tPASSIVE_CAPTURE\n19\tswap.gg\tBLOCKED\tswapauth.com\tCLEAN\t2018-10-06\tPASSIVE_CAPTURE\n20\tshadowpay.com\tBLOCKED\tthelogins.com\tCLEAN\t2018-01-22\tPASSIVE_CAPTURE\n21\tcsgocases.com\tBLOCKED\tlog-1n.com\tCLEAN\t2017-11-27\tPASSIVE_CAPTURE\n22\tcsgogem.com\tBLOCKED\tapi.csgem.com\tCLEAN\t2014-03-08\tPASSIVE_CAPTURE\n23\tgamdom.com\tBLOCKED\tlogin.gambldom.com\tCLEAN\t2017-09-24\tPASSIVE_CAPTURE\n24\t12cs.fail\tBLOCKED\tfail.games\tCLEAN\t2021-08-24\tPASSIVE_CAPTURE\n25\tskinsnipe.com\tBLOCKED\tpricing.tradeupspy.com\tCLEAN\t2020-03-11\tPASSIVE_CAPTURE\n26\tcsgobig.com\tBLOCKED\tletmeinbig.com\tCLEAN\t2023-01-20\tPASSIVE_CAPTURE\n\n* Remarque : les vérifications passives ont été effectuées sur des points de terminaison non authentifiés du filtre de liens « Steam » sur 2026-09-19 et 2026-09-21.. Les corps bruts des réponses HTTP et les hachages SHA-256s ont été conservés dans le jeu de données du référentiel (steam_tos_assets/linkfilter-2026-09-22.json).\n\nSection III : Registre des pièces justificatives B — Recensement exhaustif des entités commerciales auditées d'175RÉF. : EX-175-MASTER-CENSUS\n\nLe registre ci-dessous répertorie toutes les plateformes commerciales tierces 175 activement vérifiées dans la base de données d’audit. Chaque enregistrement indique le nom de l’entité, le domaine commercial principal, l’URL d’authentification OpenID observée Steam, la classification de l’activité, les correspondances de violation contractuelle (SSA § 2.G, SSA § 4.C, SSA § 1.C) et le champ « action » enregistré dans l’ensemble de données source. La mention « Voir les preuves datées » renvoie le lecteur aux documents justificatifs ; elle n’établit pas que l’Valven’a pris aucune mesure. L’absence de champ « action » est signalée comme non établie.\n\nPièce à conviction\tNom de l'entité et domaine principal\tRoute d'authentification / proxy observée\tClassification\tManquement contractuel\tValve Action\nEX-001\tCSGORoll\ncsgoroll.com\n\t\nwww.csgoroll.com\nDIRECT\n\tSkin Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-002\tCSGOEmpire\ncsgoempire.com\n\t\ncsgoempirelogin4.com\nSPLIT PROXY\n\tCasino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-003\tRollbit\nrollbit.com\n\t\nrbsnin.com\nSPLIT PROXY\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-004\t500 Casino\n500.casino\n\t\nfivezerozero.co\nSPLIT PROXY\n\tLicenced Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-005\tCSGOBig\ncsgobig.com\n\t\ncsgobig.com\nDIRECT\n\tRoulette/Slots\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-006\tCaseDrop\ncasedrop.com\n\t\ncasedrop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-007\tRustReaper\nrustreaper.com\n\t\nrustreaper.com\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-008\tBanditCamp\nbanditcamp.com\n\t\nbanditcamp.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-009\tSkinBox\nskinbox.com\n\t\nskinbox.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-010\tTastyDrop\ntastydrop.com\n\t\ntastydrop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-011\tCSGOPolygon\ncsgopolygon.gg\n\t\ncsgopolygon.gg\nDIRECT\n\tRoulette Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-012\tMagicDrop\nmagicdrop.ru\n\t\nmagicdrop.ru\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-013\tCSDice\ncsdice.com\n\t\ncsdice.com\nDIRECT\n\tDice Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-014\tRustly\nrustly.com\n\t\nrustly.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-015\tSkinOdds\nskinodds.com\n\t\nskinodds.com\nDIRECT\n\tUpgrader Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-016\tCSGOWin\ncsgowin.com\n\t\ncsgowin.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-017\tCSGORun\ncsgorun.net\n\t\ncsgorun.net\nDIRECT\n\tCrash Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-018\tOpenSkins\nopenskins.com\n\t\nopenskins.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-019\tRustBet\nrustbet.com\n\t\nrustbet.com\nDIRECT\n\tRust Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-020\tCSGOMagic\ncsgomagic.com\n\t\ncsgomagic.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-021\tCSGOBounty\ncsgobounty.com\n\t\ncsgobounty.com\nDIRECT\n\tUpgrader/Contract\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-022\tEZSkins\nezskins.com\n\t\nezskins.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-023\tRustCases\nrustcases.com\n\t\nrustcases.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-024\tCSGOReaper\ncsgoreaper.com\n\t\ncsgoreaper.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-025\tCSGOCases\ncsgocases.com\n\t\ncsgocases.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-026\tCSGO-Skins\ncsgo-skins.com\n\t\ncsgo-skins.com\nDIRECT\n\tCase Upgrader\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-027\tCSGONet\ncsgonet.com\n\t\ncsgonet.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-028\tWTFSkins\nwtfskins.com\n\t\nwtfskins.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-029\tCSGOFast\ncsgofast.com\n\t\nsteam-login.authtofast.com\nSPLIT PROXY\n\tRoulette Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-030\tDuelbits\nduelbits.com\n\t\nswitchflips.com\nSPLIT PROXY\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-031\tFlameCases\nflamecases.com\n\t\nflamecases.com\nDIRECT\n\tCase Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-032\tFarmskins\nfarmskins.com\n\t\nsteam.kobal.cc\nSPLIT PROXY\n\tCase Opener\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-033\tCSGOLuck\ncsgoluck.com\n\t\ncsgoluck.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-034\tGamedom\ngamedom.com\n\t\ngamedom.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-035\tSkin.Club\nskin.club\n\t\nsc-auth.net\nSPLIT PROXY\n\tCase Battles\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-036\tDaddySkins\ndaddyskins.com\n\t\ndaddyskins.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-037\tInsane.gg\ninsane.gg\n\t\napi.insane.gg\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-038\tRustix\nrustix.gg\n\t\nrustix.gg\nDIRECT\n\tRust Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-039\tSkins.Club\nskins.club\n\t\nskins.club\nDIRECT\n\tSkin Upgrade\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-040\tCSGOHouse\ncsgohouse.org\n\t\ncsgohouse.org\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-041\tSkinRave\nskinrave.net\n\t\nskinrave.net\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-042\tBloodyCase_GG\nbloodycase.gg\n\t\nbloodycase.gg\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-043\tCSGOClicker\ncsgoclicker.com\n\t\ncsgoclicker.com\nDIRECT\n\tClicker/Upgrade\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-044\tRustBet_GG\nrustbet.gg\n\t\nrustbet.gg\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-045\tCS_Drop\ncs-drop.com\n\t\ncs-drop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-046\tHellStore\nhellstore.net\n\t\nhellstore.net\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-047\tRustLoot\nrustloot.com\n\t\nrustloot.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-048\tCSGO_Case\ncsgo-case.com\n\t\ncsgo-case.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-049\tCS2Skin\ncs2skin.com\n\t\ncs2skin.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-050\tJuice_GG\njuice.gg\n\t\nletmeinjuice.com\nSPLIT PROXY\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-051\tGGDrop\nggdrop.com\n\t\nggauth.com\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-052\tCSGOGem\ncsgogem.com\n\t\ncsgogem.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-053\tRainbet\nrainbet.com\n\t\nservices.rainbet.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-054\tHowl_GG\nhowl.gg\n\t\nhowl.uno\nSPLIT PROXY\n\tSkins Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-055\tChicken_GG\nchicken.gg\n\t\nchicken.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-056\tCSGOCasino_GG\ncsgocasino.gg\n\t\napi.csgocasino.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-057\tHunt_GG\nhunt.gg\n\t\napi.hunt.gg\nDIRECT\n\tSkins Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-058\tCSBattle\ncsbattle.com\n\t\ncsbattle.com\nDIRECT\n\tCase Battles\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-059\tSkinRave_GG\nskinrave.gg\n\t\napi.skinrave.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-060\tCSDouble\ncsdouble.gg\n\t\ncsdouble.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-061\tRustChance\nrustchance.com\n\t\nhgfuihd.com\nSPLIT PROXY\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-062\tRustClash\nrustclash.com\n\t\nrustclash.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-063\tCobaltLab\ncobaltlab.tech\n\t\ncobaltauth.com\nSPLIT PROXY\n\tRust Automation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-064\tRaided_GG\nraided.gg\n\t\napi.raided.gg\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-065\tRustNeo\nrustneo.gg\n\t\nrustneo.gg\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-066\tSplits_GG\nsplits.gg\n\t\nsplits.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-067\tUpgrader_Pro\nupgrader.pro\n\t\nupgauth.space\nSPLIT PROXY\n\tSkin Upgrader\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-068\tSkinFans\nskin.fans\n\t\nauth.skinfans.com\nSPLIT PROXY\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-069\tHotPizza\nhotpizza.one\n\t\nhotpizza.one\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-070\tG4Skins\ng4skins.com\n\t\nauth.g4s.to\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-071\t12CS_Fail\n12cs.fail\n\t\n12cs.fail\nDIRECT\n\tCrash Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-072\tTF2Royal\ntf2royal.com\n\t\ntf2auth.com\nSPLIT PROXY\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-073\tTF2Easy\nwww.tf2easy.com\n\t\nwww.tf2easy.com\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-074\tTF2Hunt\ntf2hunt.com\n\t\nrstspcl.com\nSPLIT PROXY\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-075\tTF2Bet\ntf2.bet/coinflip\n\t\ntf2.bet\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-076\tTF2Blaze\ntf2blaze.com\n\t\ntf2blaze.com\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-077\tOpenStars_GG\nopenstars.gg\n\t\nopenstars.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-078\tShuffle_Com\nshuffle.com\n\t\nshuffle.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-079\tSkins.com\nskins.com\n\t\napi.skins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-080\tWhite.Market\nwhite.market\n\t\nwhite.market\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-081\tBuff.Market\nbuff.market\n\t\nbuff.market\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-082\tAvan.Market\navan.market\n\t\navan.market\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-083\tCS.MONEY\ncs.money\n\t\nauth.dota.trade\nSPLIT PROXY\n\tTrading Engine\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-084\tUUSkins\nuuskins.com\n\t\nuuskins.com\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-085\tYouPin898\nyoupin898.com\n\t\nyoupin898.com\nDIRECT\n\tMass Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-086\tMoon.Market\nmoon.market\n\t\nmoon.market\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-087\tCSFloat\ncsfloat.com\n\t\ncsgofloat.com\nSPLIT PROXY\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-088\tSkin.Land\nskin.land\n\t\nauth.skin.land\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-089\tC5Game\nc5game.com\n\t\nc5game.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-090\tHaloSkins\nhaloskins.com\n\t\nhaloskins.com\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-091\tBuff.163\nbuff.163.com\n\t\nbuff.163.com\nDIRECT\n\tCorporate Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-092\tWaxpeer\nwaxpeer.com\n\t\nwaxpeer.com\nDIRECT\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-093\tCS.MONEY Bot\ncs.money\n\t\nauth.dota.trade\nSPLIT PROXY\n\tBot Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-094\tMarket.CSGO\nmarket.csgo.com\n\t\ndota2.net\nSPLIT PROXY\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-095\tSkinport\nskinport.com\n\t\nskinport.app\nSPLIT PROXY\n\tRegulated Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-096\tSkinFlow\nskinflow.gg\n\t\napi.skinflow.gg\nDIRECT\n\tMarketplace/Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-097\tDMarket\ndmarket.com\n\t\ndmarket.com\nDIRECT\n\tUS Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-098\tSkin.place\nskin.place\n\t\napi.skin.place\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-099\tSkinsMonkey\nskinsmonkey.com\n\t\nskinsmonkey.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-100\tSkinBaron\nskinbaron.de\n\t\nskinbaron.com\nSPLIT PROXY\n\tCorporate Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-101\tSteam\nsteamcommunity.com/market\n\t\nsteamcommunity.com/market\nDIRECT\n\tOfficial Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-102\tRustTM\nrust.tm\n\t\ndota2.net\nSPLIT PROXY\n\tRust Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-103\tPirateSwap\npirateswap.com\n\t\nlogin.pirateswap.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-104\tMannco.Store\nmannco.store\n\t\nmannco.store\nDIRECT\n\tTF2 Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-105\tSkinSwap\nskinswap.com\n\t\napi.skinswap.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-106\tLootFarm\nlootfarm.com\n\t\nlootfarm.com\nDIRECT\n\tTrading Platform\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-107\tRustskins\nrustskins.com\n\t\nrustskins.com\nDIRECT\n\tRust Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-108\tExeSkins\nexeskins.com\n\t\nexeskins.com\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-109\tBalticSkins\nbalticskins.com\n\t\nbalticskins.com\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-110\tCS.Trade\ncs.trade\n\t\ncs.trade\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-111\tRapidSkins\nrapidskins.com\n\t\napi.rapidskins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-112\tTradeIt\ntradeit.gg\n\t\nconnect-tradeit.com\nSPLIT PROXY\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-113\tKrakatoa\nkrakatoa.com\n\t\nkrakatoa.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-114\tShadowPay\nshadowpay.com\n\t\nshadowpay.com\nDIRECT\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-115\t49skins\n49skins.com\n\t\napi.49skins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-116\tSkinVault\nskinvault.gg\n\t\napi.skinvault.gg\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-117\tAim Market\naim.market\n\t\naim.market\nDIRECT\n\tSkins Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-118\tSkinout\nskinout.gg\n\t\nauth.skinout.gg\nDIRECT\n\tInstant Sell Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-119\tNTSkins\nntskins.com\n\t\nntskins.com\nDIRECT\n\tSkins Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-120\tIGXE\nigxe.cn\n\t\nigxe.cn\nDIRECT\n\tChinese Powerhouse\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-121\tSwap.gg\nswap.gg\n\t\nswap.gg\nDIRECT\n\tAutomated Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-122\tBitskins\nbitskins.com\n\t\nbitskins.com\nDIRECT\n\tCash-out Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-123\tGamerPay\ngamerpay.gg\n\t\ngamerpay.gg\nDIRECT\n\tP2P Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-124\tTF2Mart\ntf2mart.com\n\t\ntf2mart.com\nDIRECT\n\tTF2 Automation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-125\tSkinBid\nskinbid.com\n\t\nskinbid.com\nDIRECT\n\tSkin Auctions\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-126\tLootBear\nlootbear.com\n\t\nlootbear.com\nDIRECT\n\tSkin Rental\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-127\tBackpack.tf\nbackpack.tf\n\t\nbackpack.tf\nDIRECT\n\tTF2 Valuation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-128\tScrap.tf\nscrap.tf\n\t\nscrap.tf\nDIRECT\n\tTF2 Scrap Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-129\tMarketplace.tf\nmarketplace.tf\n\t\nmarketplace.tf\nDIRECT\n\tTF2 Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-130\tSTNTrading\nstntrading.eu\n\t\nstntrading.eu\nDIRECT\n\tTF2 Botnet\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-131\tSkins.Cash\nskins.cash\n\t\nskinscash.live\nSPLIT PROXY\n\tInstant Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-132\tSkinWallet\nskinwallet.com\n\t\nskinwallet.com\nDIRECT\n\tInstant Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-133\tDota2Market\ndota2market.com\n\t\ndota2market.com\nDIRECT\n\tDota 2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-134\tCSGO.NET\ncsgo.net\n\t\ncn2.easylot.net\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-135\tCybershoke\ncybershoke.net\n\t\nauth.cybershoke.net\nDIRECT\n\tCommunity Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-136\tXPlay_GG\nxplay.gg\n\t\nxplay.gg\nDIRECT\n\tServer Network\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-137\tFastCup\nfastcup.net\n\t\napi.fastcup.net\nDIRECT\n\tMatchmaker Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-138\tEsportal\nesportal.com\n\t\nesportal.com\nDIRECT\n\tMatchmaking Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-139\tGamersClub\ngamersclub.com.br\n\t\ngamersclub.com.br\nDIRECT\n\tLATAM Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-140\tLeetify\nleetify.com\n\t\nleetify.com\nDIRECT\n\tSaaS Analytics\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-141\tScope_GG\nscope.gg\n\t\nscope.gg\nDIRECT\n\tSaaS Analytics\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-142\tTradeUpSpy\ntradeupspy.com\n\t\napi.tradeupspy.com\nDIRECT\n\tSaaS Tools\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-143\tEpidemic_GG\nepidemic.gg\n\t\nepidemic.gg\nDIRECT\n\tSaaS Tools\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-144\tCSDeals\ncs.deals\n\t\napi.cs.deals\nDIRECT\n\tMarketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-145\tPricempire\npricempire.com\n\t\npricempire.com\nDIRECT\n\tSaaS Price DB\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-146\tCS2Stash\ncs2stash.com\n\t\ncs2stash.com\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-147\tCSGOSkins\ncsgoskins.gg\n\t\ncsgoskins.gg\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-148\tSteamAnalyst\nsteamanalyst.com\n\t\nsteamanalyst.com\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-149\tSteamCardExchange\nsteamcardexchange.net\n\t\nsteamcardexchange.net\nDIRECT\n\tTrading Exchange\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-150\tDotaBuff\ndotabuff.com\n\t\ndotabuff.com\nDIRECT\n\tSaaS Tracker\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-151\tTracker_GG\ntracker.gg\n\t\ntracker.gg\nDIRECT\n\tSaaS Tracker\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-152\tFSB Market (an anonymized label; the original name is withheld here)\nFSB Market\n\t\nFSB Market\nDIRECT\n\tMass Blackmarket\tSSA § 2.G, SSA § 4.C, SSA § 1.C\tSee dated evidence\nEX-153\tFunPay\nfunpay.com\n\t\nfunpay.com\nDIRECT\n\tAccount Exchange\tSSA § 2.G, SSA § 4.C, SSA § 1.C\tSee dated evidence\nEX-154\tPlayerAuctions\nplayerauctions.com\n\t\nplayerauctions.com\nDIRECT\n\tGrey Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-155\tEldorado.gg\neldorado.gg\n\t\neldorado.gg\nDIRECT\n\tAccount Portal\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-156\tG2A\ng2a.com\n\t\ng2a.com\nDIRECT\n\tMass Key Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-157\tKinguin\nkinguin.net\n\t\nkinguin.net\nDIRECT\n\tMass Key Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-158\tG2G.com\ng2g.com\n\t\ng2g.com\nDIRECT\n\tVirtual Services\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-159\tPlayerup\nplayerup.com\n\t\nplayerup.com\nDIRECT\n\tAccount Broker\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-160\tZ2U.com\nz2u.com\n\t\nwww.z2u.com\nDIRECT\n\tReady-Account Hub\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-161\tSmurfHub\nsmurfhub.net\n\t\nsmurfhub.net\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-162\tSmurfAccounts\nsmurfaccounts.com\n\t\nsmurfaccounts.com\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-163\tBuyCSGORank\nbuycsgorank.com\n\t\nbuycsgorank.com\nDIRECT\n\tRank Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-164\tCSGOSmurfKings\ncsgosmurfkings.com\n\t\ncsgosmurfkings.com\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-165\tSmurfStore_Co\nsmurfstore.co\n\t\nsmurfstore.co\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-166\tSteamLvlUp\nsteamlvlup.com\n\t\nsteamlvlup.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-167\tSteamLevels\nsteamlevels.com\n\t\nsteamlevels.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-168\tLevelSteam\nlevelsteam.com\n\t\nlevelsteam.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-169\tSteamLevelU\nsteamlevelu.com\n\t\nsteamlevelu.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-170\tEloKing\neloking.com\n\t\neloking.com\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-171\tBoosteria\nboosteria.org\n\t\nboosteria.org\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-172\tOvergear\novergear.com\n\t\novergear.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-173\tBlazingBoost\nblazingboost.com\n\t\nblazingboost.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-174\tDota2Boost\ndota2boost.com\n\t\ndota2boost.com\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-175\tBuyBoost\nbuyboost.com\n\t\nbuyboost.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nSection IV : Architecture technique et mécanismes d'authentificationRÉF. : TECH-ANALYSIS-01\n\n1. Absence de validation de la propriété du domaine dans OpenID 2.0: Implémentation par Valve du protocole OpenID 2.0 (https://steamcommunity.com/openid/login) évalue le openid.return_to et openid.realm paramètres sans exiger d'inscription préalable des développeurs, de vérification par défi cryptographique ni de validation de la propriété du domaine. Tout opérateur commercial peut rediriger les utilisateurs vers la page de connexion de Valve et recevoir une attestation d'identité signée cryptographiquement (contenant le SteamID à 64-bits) redirigée vers des domaines arbitraires.\n\n2. Abus liés à la consultation et à l'APIation programmatiques de l'inventaire : Une fois l'authentification de l'utilisateur confirmée via OpenID, les opérateurs interrogent les points de terminaison des sites Web publics et des APIs partenaires (IEconItems_730/GetPlayerItems) afin d’indexer les actifs en stock en temps réel. Les réseaux de négociation automatisés utilisent des jetons de session programmatiques pour soumettre, interroger et accepter des offres de négociation entre pairs (P2P), ce qui contrevient directement à l’interdiction d’interaction non humaine prévue par l’article 4.C de la SSA.\n\n3. Asymétrie du filtre de liens : La coexistence d'alertes relatives à des domaines destinés aux consommateurs et de points de terminaison d'authentification pleinement opérationnels crée une contradiction réglementaire : la télémétrie de sécurité de Valve classe ces opérateurs comme « potentiellement malveillants », alors que l'infrastructure d'authentification de Valve continue d'authentifier leur base d'utilisateurs.\n\nMéthodologie en matière de preuve et déclaration relative à la chaîne de conservation des preuves\n\nLe présent document a été établi à partir de captures réseau non authentifiées, de l’historique des requêtes du registre « RDAP » et de manifestes de hachage cryptographique vérifiés. Aucun identifiant de connexion d’utilisateur n’a fait l’objet d’un test de compromission ni n’a été traité. Tous les résultats reflètent l’état observable du réseau de production au 2026.. Le présent document constitue une pièce à conviction technique impartiale, préparée à l’intention des instances judiciaires, réglementaires et du public.\n\nRÉSUMÉ : SHA-256, VÉRIFIÉ\nc507c9025f93da0aadaf395c4d8882f25973211c318ee8e9b6f18a5b3755e050\nARCHIVES : DOSSIER JUDICIAIRE PUBLIC\nÉMIS ET SIGNÉ PAR : phishdestroy.io · Coalition pour la recherche médico-légale\nSTATUT JURIDIQUE : TOUS LES DROITS CÉDÉS À L'HUMANITÉ · CC0 DOMAINE PUBLIC UNIVERSEL",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Loi sur l'audit judiciaire et annexe réglementaire"
          }
        ],
        "links": []
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/fr/regulatory_act_print.content.json",
      "export_json_sha256": "cf6027905e159803d629c43e595e4af86967f557ceaeb9fcd37c56c9ce81278a"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "fr/security_timeline.html",
      "language": "fr",
      "title": "Chronologie des événements liés à la sécurité — Le dossier «Steam »",
      "source_url": "https://phishdestroy.io/steam_dossier/fr/security_timeline",
      "source_html_sha256": "3f4dfd29a19c98172fa0a4918e9734874315bcf31fb781aa4c1df0be14785470",
      "exported_at": "2026-09-29T00:17:39.716Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "security_timeline.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/fr/security_timeline.pdf?v=print-20260929-v5",
        "sha256": "c1154b5d88a22ad4326be81290009fc32a1b419979d2fc22e58e5ef1c5548c54",
        "bytes": 96980,
        "pages": 7
      },
      "integrity": {
        "signed_object": "security_timeline.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "security_timeline.content.json.asc",
        "digest_file": "security_timeline.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify security_timeline.content.json.asc security_timeline.content.json",
          "sha256sum -c security_timeline.content.json.sha256"
        ]
      },
      "content": {
        "text": "LE BILAN EN MATIÈRE DE SÉCURITÉEXPOSITION / 16 PARTICIPANTS\n\n2018 — 2026\n\nChronologie des mises à jour de sécurité — De « 2018 » à « 2026 »\n\nLa sécurité a changé. Suivez le dossier.\n\nCE QUE CETTE SECTION DÉMONTRERA\n\nCe relevé chronologique retrace huit années de modifications apportées à la sécurité de la pile de transactions et d'authentification d'Steam. Il rend compte de l'2018, de la mise en œuvre de la période de blocage des transactions journalières (7-), de la mise en place de la confirmation par mobile via le site Web 2023API, ainsi que de la suppression progressive des jetons de session (2026) face aux techniques de contournement documentées. La chronologie montre que les mises à jour de la plateforme ont systématiquement pris du retard par rapport aux vecteurs d'exploitation connus, tout en préservant les avantages structurels pour les opérateurs commerciaux.\n\n← Retour au dossier de synthèse destiné aux dirigeants\n\nVerrous de transaction. Contrôles d'accès. Restrictions d'API. Un compte rendu chronologique des changements intervenus — et de ce que les sources établissent réellement.\n\nDécouvrez la chronologie ↓\nHUIT ANS. UN ALBUM.16étapes clés à examiner\n\nChaque entrée conserve sa date de soumission et sa source. La vérification apparaît à côté.\n\nARTICLE VÉRIFIÉ / 24 SEP 2026\n10Événement et date confirmés\n06Partiellement vérifié\n00Incompatibilité de source\n00Source requise\nComment lire ce document\n\nÉvénement et date confirmés : toutes deux étayées par une source primaire fiable. Partiellement vérifié : une modification connexe est consignée, mais la date ou la portée n'ont pas encore été déterminées. Incompatibilité de source : Les documents mentionnés ne viennent pas étayer l'allégation avancée. Source requise : Aucune source datée correspondante n'a pu être vérifiée dans le cadre de cette analyse. Le fait qu'une entrée n'ait pas pu être vérifiée ne prouve pas qu'un événement ne se soit pas produit.\n\nLes dates indiquées pour les entrées non résolues correspondent aux dates de soumission et non à des dates de publication vérifiées. Le texte original de l'enquête n'a pas été remanié.\n\nLa chronologie\n01 — 16\nRechercher dans la ficheSujetÉléments de preuveCommande\n\n16 parmi les entrées d'16 · les plus récentes en premier\n\n202609-01Date de soumission\nCommunautéPartiellement vérifié\nAlertes concernant les messages suspects dans les discussions de groupe\n\nUne annonce officielle concernant la version bêta confirme la disponibilité de cette fonctionnalité sur 31 en août. La date de sortie de la version stable prévue pour le 1 en septembre doit encore faire l'objet d'une note de mise à jour spécifique.\n\nSteam Version bêta pour les clients — 31er août ↗archivé 2026-03-13 ↗\nEntrée d'origine et lien soumis\n\nSignalement automatisé des discussions suspectes\n\nConsulter le code source soumis ↗\n202601-16Date de vérification\nAPIÉvénement et date confirmés\nAutorisations granulaires et liste blanche d'adresses IP pour les clés d'éditeur (annonce concernant Valve)\n\nLe 16 janvier 2026, Valve a publié une annonce officielle concernant Steamworks (« NOUVEAU : Amélioration des autorisations et des contrôles pour les clés d'API Web ») confirmant la mise en place de nouveaux outils de gestion des autorisations granulaires permettant aux développeurs de segmenter les clés d'APIs Web en groupes distincts (Données générales, microtransactions, économie et ventes), limiter les clés à des identifiants d'application spécifiques et mettre en place une liste blanche d'adresses IP de serveurs.\n\nLe double standard flagrant : Cette annonce officielle précise qu’Valve a entièrement mis en place l’infrastructure technique permettant de gérer de manière granulaire les autorisations d’API et les restrictions d’adresses IP, mais les refuse délibérément aux comptes d'utilisateurs standard (steamcommunity.com/dev/apikey). Les clés d’APIs des utilisateurs lambda restent des identifiants monolithiques, de type « tout ou rien », sans liste blanche d’adresses IP — ce qui constitue précisément la lacune technique permettant l’existence d’un secteur d’activité de plusieurs millions de dollars spécialisé dans l’interception des transactions sur API.\n\nValve Annonce — NOUVEAU : Amélioration des autorisations et des contrôles pour les clés d'API Web (16 Jan 2026) ↗· Documentation : Authentification via l'API Web de Steamworks ↗\nEntrée d'origine et lien soumis\n\nAPIs Web de Steamworks : portées granulaires\n\nConsultez l'annonce officielle d'Valve sur Steamworks (493839547938902179) ↗\n202507-15Date de vérification\nTradingÉvénement et date confirmés\nLes transactions CS2 bénéficient d'un délai de rétractation de sept jours\n\nL'annonce publiée par Valve présente l'annulation des échanges d'objets Counter-Strike effectués au cours des sept derniers jours. Bien que cette mesure vise à limiter le détournement d'objets, des audits économiques réalisés par des tiers (CSMarketCap ↗) a enregistré un 104millions de dollars (-25%) effondrement en capitalisation boursière au cours des heures de cotation de l'24, en raison d'une perturbation des opérations au comptant. Selon l'analyse réalisée par Skinvault ↗, le déclenchement d'un renversement entraîne automatiquement une suspension de day trading d'30-s sur le compte. Au cours de l'été 2026, Valve, le système est passé d'une réinitialisation mondiale à minuit (UTC) à des minuteries individuelles par élément (Skin.land ↗).\n\nValve — 15 Annonce du 2025, juillet ↗· Analyse CSMarketCap ↗\nEntrée d'origine et lien soumis\n\nProtection des transactions CS2 / Période de rétractation\n\nConsulter le code source soumis ↗\n202505-14Date de vérification\nAuthentificationÉvénement et date confirmés\nValve publie un avertissement concernant la sécurité des comptes suite à des fuites par SMS\n\nL'annonce officielle de Valve du 14, 2025, porte sur la sécurité des comptes et les systèmes d'authentification par SMS. Bien que cette annonce se concentre sur les fuites de SMS et confirme qu'aucun système d'Steams n'a été compromis, elle constitue une mise à jour officielle en matière de sécurité à la date de publication.\n\nValve — Remarque concernant la sécurité de votre compte Steam ↗\nEntrée d'origine et lien soumis\n\nAnnonce concernant la sécurité des comptes\n\nConsulter le code source soumis ↗\n202410-02Date de vérification\nTradingÉvénement et date confirmés\nSept jours avant la revente ou la remise sur le marché\n\nLes notes de mise à jour concernent les objets acquis via la boutique du jeu, notamment l'Armurerie, les offres d'échange et le Marché communautaire. Le champ d'application décrit ne se limite pas aux seuls objets de l'Armurerie.\n\nValve — Notes de mise à jour d'10/2/2024 ↗\nEntrée d'origine et lien soumis\n\nCS2 The Armory / Journée « 7-»\n\nConsulter le code source soumis ↗\n202409-18Date de soumission\nTradingPartiellement vérifié\nRestrictions relatives aux nouveaux appareils vérifiées sur les pages d'aide\n\nLa documentation d'assistance officielle de Steam confirme l'existence d'une restriction concernant le day trading 7-lors de la connexion depuis un nouvel appareil n'ayant pas été autorisé depuis au moins 7 jours. Bien que la date exacte de déploiement de septembre 18, 2024, ne figure pas parmi les étapes importantes du journal des modifications, cette fonctionnalité est entièrement documentée.\n\nSteam Assistance — Restrictions relatives au trading et aux marchés ↗\nEntrée d'origine et lien soumis\n\nRestriction relative à la connexion sur un nouvel appareil\n\nConsulter le code source soumis ↗\n202402-14Date de soumission\nCommunautéPartiellement vérifié\nMise en place d'un délai d'attente pour les changements de nom dans « 2024 »\n\nLes archives de la communauté et des développeurs confirment qu’au début de l’année 2024, Valve, un 2-non annoncé a été mis en place, imposant un délai d’attente de4 heure immédiatement après un changement de nom de profil, afin de limiter les escroqueries par usurpation d’identité. Étant donné que Valve n’a publié aucun communiqué de presse officiel, aucun journal des modifications du client ni aucun article d’assistance concernant cette restriction, la date indiquée en février 14 ne dispose d’aucune vérification officielle ; le guide de l’Steam Workshop sert de corroboration indirecte de la part de la communauté plutôt que de documentation officielle Valve.\n\nSteam Guide de l'atelier (corroboration indirecte) — Détails relatifs à la restriction en matière de changement de nom ↗\nEntrée d'origine et lien soumis\n\nSuspension de la modification du nom de profil / de l'avatar\n\nConsulter le code source soumis ↗\n202312-04Date de vérification\nAPIÉvénement et date confirmés\nLa création d'une clé nécessite une confirmation sur mobile\n\nIl a été confirmé que la mise en place de la confirmation mobile obligatoire via Steam Guard pour la création de clés Web API a eu lieu fin 2023,, comme l'attestent les bibliothèques de développement tierces. La date exacte du 4, 2023, correspond à la période de déploiement observée au sein de la communauté des développeurs.\n\nDocumentation du responsable de maintenance — mars 2024 ↗archivé 2026-09-24 ↗\nEntrée d'origine et lien soumis\n\nConfirmation sur mobile pour les clés «API»\n\nConsulter le code source soumis ↗\n202310-24Date de vérification\nDéveloppeurÉvénement et date confirmés\nL'2-FA obligatoire pour la mise en ligne des versions de jeu entre en vigueur\n\nL'annonce officielle de Valve concernant Steamworks, publiée le 10, 2023,, confirme qu'à compter du 24, 2023,, tout compte mettant en ligne une version sur la branche par défaut d'une application déjà publiée devra valider cette modification par SMS ou via l'application mobile Steam. Cette modification a entraîné une mise à jour immédiate de la page Web SetAppBuildLive API.\n\nSteamworks — Améliorations en matière de sécurité pour la gestion des versions et des utilisateurs ↗archivé 2025-12-03 ↗\nEntrée d'origine et lien soumis\n\nAuthentification multifactorielle par SMS pour la publication des versions de jeux vidéo\n\nConsulter le code source soumis ↗\n202307-12Date de soumission\nCommunautéPartiellement vérifié\nAvertissements relatifs au contenu des biographies personnalisées signalés par la communauté\n\nSteam Des signalements de la communauté datant de juillet 2023 indiquent que les biographies de profil personnalisées contenant des liens externes ou des mots déclencheurs ont commencé à afficher des avertissements de contenu automatiques. La date de signalement, juillet 12, 2023,, correspond à la première vague de signalements des utilisateurs sur les forums de la communauté Steam.\n\nSteam Forum communautaire — Signaler un contenu biographique ↗\nEntrée d'origine et lien soumis\n\nAvertissement concernant le contenu de la biographie personnalisée\n\nConsulter le code source soumis ↗\n202301-25Date de soumission\nCommunautéPartiellement vérifié\nLes délais d'attente pour le filtrage et la modification des liens de profil sont actifs\n\nLa documentation officielle d'Steam confirme que les liens figurant dans les biographies personnalisées sont filtrés et que les changements abusifs de nom ou d'avatar peuvent entraîner des interdictions de modification. Bien que la mise en place effective du délai d'attente d'4-heures, le 1er janvier 25, 2023,, marque le début observé de cette mesure, le mécanisme de filtrage des liens lui-même est pleinement opérationnel, comme l'indique la page d'aide correspondante.\n\nSteam Assistance — Restrictions concernant le nom de profil et l'avatar ↗\nEntrée d'origine et lien soumis\n\nProfil LIEN SUPPRIMÉ / Temps de recharge\n\nConsulter le code source soumis ↗\n202210-24Date de vérification\nAuthentificationÉvénement et date confirmés\nSteam Migration des clients vers les jetons d'accès et de rafraîchissement OAuth\n\nPrincipales mises à jour de Valve concernant ses clients et ses applications mobiles en octobre 2022 a entièrement remanié le système d'authentification de Steam. L'ancienne structure basée sur des cookies de session a été remplacée par un système d'accès et de jetons de rafraîchissement basé sur OAuth, et une liste des appareils autorisés actifs a été mise en place pour permettre la révocation manuelle des sessions actives.\n\nValve — Mise à jour de l'application mobile « Steam » et refonte du système d'authentification ↗\nEntrée d'origine et lien soumis\n\nSteam Refonte de la procédure de connexion / Tronquage des cookies\n\nConsultez l'annonce d'Valve ↗\n202210-12Date de vérification\nAuthentificationÉvénement et date confirmés\nConnexion via QR code et gestion des appareils autorisés\n\nDans son annonce du 1er octobre sur 12, Valve décrit la procédure de connexion via QR code, la validation ou le refus des connexions, ainsi qu’une liste d’appareils permettant de révoquer l’accès à un compte.\n\nValve — La nouvelle version de l'application mobile « Steam » est désormais disponible ↗\nEntrée d'origine et lien soumis\n\nSteam 3.0s sur l'application mobile / Connexion via QR code\n\nConsulter le code source soumis ↗\n202205-10Date de soumission\nAPIPartiellement vérifié\nLes points de terminaison relatifs à l'annulation des transactions ont été supprimés de la liste publique d'API\n\nLes registres des développeurs confirment qu’en mai 2022, Valve, les points de terminaison de gestion des échanges tels que IEconService/CancelTradeOffer et DeclineTradeOffer ont été supprimés en silence de l’API Web (comme documenté dans node-steam-tradeoffer-manager #325). Bien que ces méthodes restent fonctionnelles dans les protocoles clients privés, la date du 10, 2022, marque leur suppression effective des API Web publiques afin de lutter contre les panels frauduleux.\n\nDiscussion entre développeurs — Problème n°325 (suppression de « CancelTradeOffer ») ↗· Site Web de SteamAPI — Documentation IEconService ↗\nEntrée d'origine et lien soumis\n\nSuppression des points de terminaison d'annulation des transactions\n\nConsulter le ticket « node-steam-tradeoffer-manager » n°325 ↗\n202005-25Date de vérification\nTradingÉvénement et date confirmés\nLes objets «2s » de Dota sont soumis à un délai d'attente de sept jours avant de pouvoir être échangés\n\nLe 25, mai, 2020,, parallèlement à la sortie du Battle Pass de l'International 10 (blog.dota2.com/2020/05/the-international-10-battle-pass/), Valve a mis en place une restriction de 7-jours sur les échanges d'objets Dota 2, à l'instar de la politique appliquée à 2018 Counter-Strike. Cette restriction s'applique à tous les objets échangés et aux achats effectués sur le Marché.\n\nCommunauté Dota2 — Mise à jour concernant le verrouillage des échanges et le client TI10 ↗\nEntrée d'origine et lien soumis\n\nDota 2 / 7-Blocage des transactions journalières\n\nConsulter le code source soumis ↗\n201803-29Date de vérification\nTradingÉvénement et date confirmés\nLes objets CS:GO échangés sont soumis à un délai d'attente de sept jours\n\nLes notes de mise à jour officielles confirment la date et la restriction. L'URL fournie redirigeait vers une mise à jour de carte sur 2013 ; l'URL correspondante des notes de mise à jour se termine par 20309.\n\nValve — Notes de mise à jour d’3/29/2018 ↗\nEntrée d'origine et lien soumis\n\nCS:GO / Verrouillage du Day Trade sur « 7-»\n\nConsulter le code source soumis ↗ archivé 2025-02-26 ↗\n\nSuivez les indices. Vérifiez la source.\n\nRetour à l'enquête ↗",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Chronologie des mises à jour de sécurité — De « 2018 » à « 2026 »"
          },
          {
            "level": 2,
            "id": null,
            "text": "La chronologie"
          },
          {
            "level": 2,
            "id": null,
            "text": "Alertes concernant les messages suspects dans les discussions de groupe"
          },
          {
            "level": 2,
            "id": null,
            "text": "Autorisations granulaires et liste blanche d'adresses IP pour les clés d'éditeur (annonce concernant Valve)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Les transactions CS2 bénéficient d'un délai de rétractation de sept jours"
          },
          {
            "level": 2,
            "id": null,
            "text": "Valve publie un avertissement concernant la sécurité des comptes suite à des fuites par SMS"
          },
          {
            "level": 2,
            "id": null,
            "text": "Sept jours avant la revente ou la remise sur le marché"
          },
          {
            "level": 2,
            "id": null,
            "text": "Restrictions relatives aux nouveaux appareils vérifiées sur les pages d'aide"
          },
          {
            "level": 2,
            "id": null,
            "text": "Mise en place d'un délai d'attente pour les changements de nom dans « 2024 »"
          },
          {
            "level": 2,
            "id": null,
            "text": "La création d'une clé nécessite une confirmation sur mobile"
          },
          {
            "level": 2,
            "id": null,
            "text": "L'2-FA obligatoire pour la mise en ligne des versions de jeu entre en vigueur"
          },
          {
            "level": 2,
            "id": null,
            "text": "Avertissements relatifs au contenu des biographies personnalisées signalés par la communauté"
          },
          {
            "level": 2,
            "id": null,
            "text": "Les délais d'attente pour le filtrage et la modification des liens de profil sont actifs"
          },
          {
            "level": 2,
            "id": null,
            "text": "Steam Migration des clients vers les jetons d'accès et de rafraîchissement OAuth"
          },
          {
            "level": 2,
            "id": null,
            "text": "Connexion via QR code et gestion des appareils autorisés"
          },
          {
            "level": 2,
            "id": null,
            "text": "Les points de terminaison relatifs à l'annulation des transactions ont été supprimés de la liste publique d'API"
          },
          {
            "level": 2,
            "id": null,
            "text": "Les objets «2s » de Dota sont soumis à un délai d'attente de sept jours avant de pouvoir être échangés"
          },
          {
            "level": 2,
            "id": null,
            "text": "Les objets CS:GO échangés sont soumis à un délai d'attente de sept jours"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/fr/#briefing-heading",
          "https://steamcommunity.com/groups/SteamClientBeta?l=english",
          "http://web.archive.org/web/20260313235409/https://steamcommunity.com/groups/SteamClientBeta?l=english",
          "https://store.steampowered.com/news/posts/?enddate=1788390000",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/493839547938902179",
          "https://partner.steamgames.com/doc/webapi_overview/auth",
          "https://csmarketcap.com/blog/market-insights/from-boom-to-bust-cs2s-trade-protection-impact",
          "https://skinvault.gg/blog/cs2-trade-protection-explained/",
          "https://skin.land/blog/steam-changes-cs2-trade-ban-logic-timing/",
          "https://store.steampowered.com/news/posts/?appids=730&amp;enddate=1753924057&amp;feed=steam_announce%2F1000",
          "https://help.steampowered.com/faqs/view/3041-A87A-E5F6-B6AC",
          "https://store.steampowered.com/news/posts/?enddate=1747349559",
          "https://steamcommunity.com/ogg/593110/announcements/detail/533224478739530146",
          "https://store.steampowered.com/news/posts/?appids=730&amp;enddate=1728000977&amp;feed=steam_community_announcements",
          "https://steamcommunity.com/games/CSGO/announcements/detail/4447966961421256740",
          "https://help.steampowered.com/faqs/view/7F77-9E92-31E0-6B8E",
          "https://steamcommunity.com/sharedfiles/filedetails/?id=2926756889",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "http://web.archive.org/web/20260924181824/https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "https://steamcommunity.com/dev/apikey",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3749866608167579206",
          "http://web.archive.org/web/20251203174259/https://steamcommunity.com/groups/steamworks/announcements/detail/3749866608167579206",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3734103130194459461",
          "https://steamcommunity.com/discussions/forum/1/3807266184852932971/",
          "https://help.steampowered.com/faqs/view/225C-C51E-B8F0-55B2",
          "https://store.steampowered.com/news/group/4/view/3314112260640237775",
          "https://store.steampowered.com/news/posts/?appgroupname=Keep+in+touch&amp;enddate=1666122699&amp;feed=steam_blog",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/issues/325",
          "https://partner.steamgames.com/doc/webapi/IEconService",
          "https://steamcommunity.com/app/570/announcements/",
          "https://blog.dota2.com/2020/05/trading-cooldown/",
          "https://blog.counter-strike.net/2018/03/20309/",
          "https://blog.counter-strike.net/index.php/2018/03/20308/",
          "http://web.archive.org/web/20250226114333/https://blog.counter-strike.net/index.php/2018/03/20308/",
          "https://phishdestroy.io/steam_dossier/fr/#vulnerability-profile"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/fr/security_timeline.content.json",
      "export_json_sha256": "8d7b220a2597ec018bd176bc0517d7dc37211b7d70a5a84249f3069d83c45d02"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "fr/skin_atlas.html",
      "language": "fr",
      "title": "L'atlas de ce que «Steam» ne peut pas transporter — Le dossier «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/fr/skin_atlas",
      "source_html_sha256": "63dd717dc5e67cd4f7e032a7581843d28bd012b1341321a1ea83fe2ec32a9b80",
      "exported_at": "2026-09-29T00:17:42.325Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "gallery",
            "source": "https://phishdestroy.io/steam_dossier/fr/skin_atlas#gallery"
          }
        ],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "skin_atlas.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/fr/skin_atlas.pdf?v=print-20260929-v5",
        "sha256": "98d3425d1d22657714ddb0d420bd9b4ba1e147ef469a6a18a3c48ff7467ee05b",
        "bytes": 185544,
        "pages": 14
      },
      "integrity": {
        "signed_object": "skin_atlas.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "skin_atlas.content.json.asc",
        "digest_file": "skin_atlas.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify skin_atlas.content.json.asc skin_atlas.content.json",
          "sha256sum -c skin_atlas.content.json.sha256"
        ]
      },
      "content": {
        "text": "ANNEXE IV-B / L'ÉCHELLE DES PRIX / 2026-09-23\nAtlas des échelles de prix de Skin — La « falaise de liquidité »\n\nLes étapes de Valve sur les marchés là où l'argent prend sa source.\n\nCE QUE CETTE SECTION DÉMONTRERA\n\nCet atlas visuel analyse les catégories de produits d'30,266s sur cinq catalogues de places de marché, en évaluant la couverture du marché au-dessus et en dessous du seuil d'inscription fixé par Valve. En dessous du plafond de $1,800, Steam héberge 95.3% de catégories actives ; juste au-dessus, la couverture officielle chute à 1.9% (avec une couverture de 0.0% sur les actifs corroborés). Cela met en évidence une rupture brutale et structurelle de la liquidité, Valve déléguant la découverte des transactions de grande valeur à des plateformes externes tout en conservant le contrôle total de la conservation des actifs sous-jacents.\n\n← Retour au dossier de synthèse destiné aux dirigeants\n\nChaque objet CS2 dont le prix était disponible sur cinq places de marché a été classé dans une fourchette de prix en fonction de son prix de vente le plus bas, et chaque fourchette a été évaluée selon un seul critère : quelle part de celle-ci est encore disponible sur le Community Market d'Valve. En dessous du plafond d'annonces fixé par Valve, la réponse est 95.3%. Au-dessus, la réponse est 1.9%. La baisse n'est pas progressive et elle ne correspond pas à la baisse de la demande : elle correspond exactement à la règle publiée. Parmi les 248 les catégories de produits pour lesquelles deux places de marché ou plus fixent indépendamment des prix supérieurs au plafond, 100.0% ne disposent d'aucune fiche produit sur Steam.\n\nRegardez la falaise ↓Ouvrir la galerie des articles de la collection «419 »Méthode et limites\n30,266catégories d'articles mesurées\n95.3%des éléments hors capital détenus par l'Steam\n1.9%des articles hors quota proposés par Steam\n$78.6Mvaleur inférieure de l'ensemble corroboré\n01 / la mesure\nLa falaise s'effondre selon la règle, et non à la demande\n\nChacune des catégories d'articles « 30,266 » ci-dessous est classée dans une tranche en fonction de son le moins cher Enquête en direct sur BUFF163, CSFloat, Skinport, YouPin 898 et C5Game ; seuls les articles cités sur au moins deux de ces sites sont pris en compte, de sorte qu’aucune annonce optimiste ne puisse inventer de toutes pièces un membre du groupe. Le graphique du haut indique la part de marché que chaque groupe détient encore sur la plateforme Valve.\n\nPart de chaque tranche de prix proposée par le marché communautaire «Steam»\nen haut : couverture de la vapeur · en bas : nombre d'éléments par bande, échelle logarithmique\n0%\n25%\n50%\n75%\n100%\n100%\n96.9%\n95.9%\n97.3%\n91.1%\n76.8%\n14.5%\n2.9%\n1.5%\n0%\n0%\n0%\n4,632\n1¢–10¢\n7,152\n10¢–$1\n8,568\n$1–10\n5,941\n$10–100\n2,329\n$100–300\n1,292\n$300–1k\n193\n$1k–1.8k\n70\n$1.8k–3k\n67\n$3k–10k\n18\n$10k–30k\n3\n$30k–100k\n1\n$100k+\nitems\nlog\nVALVE’S LISTING CAP\négal ou inférieur au plafond de cotation d'Valveau-delà du plafond — la règle d'Valve interdit la cotationcatégories d'articles dans le groupe\n\nLa « couverture » signifie qu’une demande en direct Steam existait pour cette catégorie au moment de la capture. Le graphique du bas est logarithmique car le catalogue est en grande majorité composé d’articles bon marché : une lecture linéaire aplatirait toutes les fourchettes de prix supérieures à $300, les ramenant au niveau de la ligne de base.\n\nCe que la forme exclut\n\nSi les produits coûteux étaient simplement impopulaires, la couverture diminuerait progressivement à mesure que les prix augmenteraient. Or, ce n'est pas le cas. Elle se maintient à 76.8% sur toute la fourchette comprise entre $300–$1k, puis s'effondre à 14.5% dans la fourchette située juste en dessous du plafond et à 2.9% dans celle située juste au-dessus. Un effet lié à la demande ne tient pas compte de l'endroit où Valve a fixé son plafond. Une règle, en revanche, en tient compte.\n\nFourchette de prix\tCatégories d'articles\tAvec une question en direct sur Steam\tSteam couverture\tExemplaires répertoriés sur Steam\n1¢–10¢\t4,632\t4,632\t100%\t8,223,227\n10¢–$1\t7,152\t6,931\t96.9%\t5,488,315\n$1–10\t8,568\t8,213\t95.9%\t3,939,538\n$10–100\t5,941\t5,780\t97.3%\t1,328,255\n$100–300\t2,329\t2,121\t91.1%\t364,466\n$300–1k\t1,292\t992\t76.8%\t187,504\n$1k–1.8k\t193\t28\t14.5%\t40,281\n$1.8k–3k\t70\t2\t2.9%\t9,592\n$3k–10k\t67\t1\t1.5%\t6,706\n$10k–30k\t18\t0\t0%\t1,366\n$30k–100k\t3\t0\t0%\t21\n$100k+\t1\t0\t0%\t2\n\nLes variantes de modèle et de phase sont exclues de cette échelle : Steam ne mentionne pas le niveau « blue-gem » ni la phase « Ruby » comme des entrées distinctes sur le marché ; les prendre en compte reviendrait donc à sous-estimer la couverture d’Steam. Si l’on ne tient pas compte de l’exigence des deux places de marché, ce même classement donne 79.1% en dessous du plafond et 6.5% au-dessus pour l’ensemble des articles 37,204 — un écart plus marqué, reposant sur des données moins solides, ce qui explique pourquoi ce chiffre n’est pas celui cité.\n\n02 / notation fondée sur des éléments probants\nUn prix demandé n'est pas un prix\n\nN'importe qui peut mettre en vente un P2000 à dix millions de yuans ronds. Avant qu'un chiffre figurant sur cette page ne soit utilisé à quelque fin que ce soit, il est classé en fonction du nombre de plateformes de vente qui proposent ce produit à un prix supérieur au plafond fixé, et de la concentration des cotations autour de cette valeur. Seuls les classements A et B sont pris en compte — ici comme partout ailleurs dans ce dossier.\n\nA  Trois étagères ou plus sont identiques\n\nAu moins trois places de marché proposent ce produit à un prix supérieur au plafond fixé, et leur prix médian se situe à moins d'25%s du prix le plus bas. 197 catégories, 18,218 exemplaires,76,585,587.\n\nAbsents de «Steam » : 100.0%.\n\nB  Les deux étagères sont identiques\n\nDeux places de marché s'accordent au-dessus du plafond, ou trois s'accordent de manière moins stricte. 51 catégories, 176 exemplaires, $2,038,814.\n\nAbsents de «Steam » : 100.0%.\n\nC  Une étagère — non utilisée\n\nUne seule place de marché affiche la seule offre supérieure au plafond. 171 catégories, exemplaires de « 247 ». Présentés dans la galerie à titre d'exhaustivité et non pris en compte dans aucun des totaux figurant sur cette page.\n\nIl s'agit de demandes de prix, et non de preuves d'un prix.\n\nCe qu'a coûté cette correction, et ce qu'elle a permis d'obtenir\n\nEn supprimant la note « C », on élimine les mentions «171» et «$3,825,125» du titre. Ce qui reste est plus concis et beaucoup plus difficile à contester : 248 catégories, 18,394 exemplaires répertoriés, $78,624,401, et 100.0% d'entre eux — absolument tous — sont absents du marché de Valve. Ce sont les lignes de catégorie C qui ont entraîné la variation du chiffre ; elles sont affichées, et non masquées.\n\nEntrées classées comme « artefacts »\n\nTout devis dépassant de plus de trois fois le cours vendeur le plus bas pour le même article est écarté. Convertis au taux que les données elles-mêmes suggèrent, la plupart d’entre eux correspondent à des montants en CNY arrondis — ce qui indique qu’il s’agit d’une valeur par défaut ou d’un plafond fixé par la plateforme plutôt que d’une offre réelle. En effet, chaque total affiché sur cette page utilise le le moins cher Il faut savoir qu'aucun de ces personnages n'aurait jamais pu gonfler un chiffre ; ils ont été écartés afin qu'aucun d'entre eux ne puisse non plus faire l'objet d'un titre à la une.\n\nArticle\tDemande en direct la moins chère\tMettre de côté\nSouvenir P2000 | Wicked Sick (Minimal Wear)\t$148,954\t$1,489,543\n★ Specialist Gloves | Crimson Kimono (Minimal Wear) | Phase 1\t$37,239\t$119,163\nSouvenir USP-S | Printstream (Factory New)\t$2,000\t$59,582\n★ Bowie Knife | Crimson Web (Factory New)\t$2,957\t$43,030\n★ Karambit | Marble Fade (Factory New) | 1st\t$11,916\t$38,874\nSticker | Ninjas in Pyjamas (Holo) | Katowice 2014\t$5,000\t$31,748\nSouvenir AWP | Dragon Lore (Battle-Scarred)\t$4,225\t$29,157\n★ Karambit | Doppler (Minimal Wear) | Ruby\t$7,122\t$27,273\nToutes les catégories d'419, avec l'objet auquel chaque prix se rapporte\n\nSource: https://phishdestroy.io/steam_dossier/fr/skin_atlas#gallery\n\n04 / où est-il allé à la place ?\nLes rayons qui proposent ce que Steam ne propose pas\n\nLes mêmes annonces, regroupées par plateforme sur laquelle elles sont publiées. Il s'agit d'un décompte des endroits où se trouvent les exemplaires. répertorié, ce qui n'est pas la même chose que leur lieu de propriété et n'est pas interprété ici comme tel.\n\nValeur minimale des annonces dépassant le plafond, par place de marché\nprix de vente le plus bas × nombre d'exemplaires référencés sur cette étagère\nYouPin 898\n$22,720,252\nBUFF163\n$22,022,606\nC5Game\n$12,560,543\nCSFloat\n$10,871,845\nSkinport\n$1,385,060\n\nTerritoires, dans l'ordre indiqué ci-dessus : YouPin 898 — Chine · BUFF163 — Chine · C5Game — Chine · CSFloat — États-Unis · Skinport — Allemagne / Malte. Un même article physique pouvant figurer sur plusieurs de ces rayons, ces chiffres ne doivent en aucun cas être additionnés à ceux d'un autre marché.\n\nValeur minimale par tranche de prix\ncomment l'argent est réparti au-delà du plafond\n$1.8k-3k\n$9,842,391\n$3k-10k\n$36,787,269\n$10k-50k\n$20,038,749\nover $50k\n$2,891,897\n05 / une pénurie que l'on peut quantifier\nÀ quel point l'offre est-elle réellement limitée ?\n\nChaque objet CS2 est associé à une valeur d'usure, et les places de marché publient le nombre d'exemplaires se situant dans chaque tranche de cette valeur. Ainsi, le terme « rare » passe du statut d'adjectif à celui de chiffre — et c'est ce chiffre qui explique pourquoi un seul compte piraté vaut la peine qu'on lui consacre un kit de phishing sur mesure.\n\nAWP | L'histoire du dragon\n150 en vente · à partir de11,350 $\n0.00–0.01\n29 · $14,730\n0.01–0.02\n54 · $11,618\n0.02–0.03\n26 · $11,350\n0.03–0.04\n25 · $11,618\n0.04–0.07\n16 · $11,585\n\nAWP | Dragon Lore (neuf, sorti d'usine)\n\nM4A4 | Howl\n105 en vente · à partir de6,628 $\n0.00–0.01\n11 · $10,725\n0.01–0.02\n14 · $8,088\n0.02–0.03\n11 · $7,580\n0.03–0.04\n19 · $6,703\n0.04–0.07\n50 · $6,628\n\nM4A4 | Howl (neuf d'usine)\n\nAK-47 | Wild Lotus\n113 en vente · à partir de14,373 $\n0.00–0.01\n25 · $22,343\n0.01–0.02\n11 · $19,364\n0.02–0.03\n3 · $19,645\n0.03–0.04\n15 · $15,044\n0.04–0.07\n59 · $14,373\n\nAK-47 | Wild Lotus (Neuf d'usine)\n\nAWP | Gungnir\n173 en vente · à partir de11,618 $\n0.00–0.01\n28 · $17,875\n0.01–0.02\n21 · $13,600\n0.02–0.03\n32 · $12,065\n0.03–0.04\n29 · $11,735\n0.04–0.07\n63 · $11,618\n\nAWP | Gungnir (neuf d'usine)\n\nAK-47 | Serpent de feu\n278 en vente · à partir de663 $\n0.15–0.18\n87 · $730\n0.18–0.21\n49 · $712\n0.21–0.24\n52 · $703\n0.24–0.27\n18 · $715\n0.27–0.38\n72 · $663\n\nAK-47 | Serpent de feu (testé sur le terrain)\n\nCémenté (tous les niveaux / gemme bleue)\n76 en vente · à partir de1,638 $\n0.07–0.08\n1 · $2,516\n0.08–0.09\n4 · $2,482\n0.09–0.10\n6 · $3,856\n0.10–0.11\n7 · $2,797\n0.11–0.15\n58 · $1,638\n\nAK-47 | Cémenté (usure minime) | Niveau 1\n\nLes fourchettes correspondent aux fourchettes de liquidité propres à la place de marché ; seules les fourchettes comportant au moins une cotation en temps réel sont prises en compte. Le prix indiqué à côté de chaque barre correspond au cours vendeur en temps réel le plus bas de cette fourchette ; ainsi, la prime liée à une faible liquidité est directement lisible, sans qu'il soit nécessaire de la préciser.\n\n06 / mouvement, mesuré à partir de Steam\nCe qu'ont réellement réalisé les rayons des marques tierces\n\nValve ne publie pas d'historique exploitable à ce niveau, et ce dossier n'en revendique aucun. Skinport publie en revanche ses propres ventes conclues au cours des dernières 24 heures, 7, 30 et 90 jours, et c'est là toute la dimension temporelle disponible ici : un prix médian réalisé par fenêtre glissante, indexé de sorte que la médiane du jour 90-soit 100. Aucune donnée relative à l'Steame n'est prise en compte dans aucun des deux graphiques.\n\nPrix médian réalisé, fenêtre glissante\nindexé sur la médiane quotidienne de l'indice «90-» · 6,758 articles avec 20+ ventes\n85\n91\n97\n103\n100\n90d\n94\n30d\n90\n7d\n88\n24h\nVentes réalisées par jour\nmêmes articles, mêmes vitrines\n7,621\n9,653\n11,684\n13,716\n12,700\n90d\n11,894\n30d\n9,540\n7d\n8,637\n24h\n\nIl s'agit de deux graphiques distincts et non d'un seul comportant deux échelles verticales : un indice et un nombre quotidien ne partagent aucune unité commune, et les représenter sur un axe commun conduirait à une comparaison non valable. Les fenêtres sont imbriquées et glissantes — le chiffre journalier 90-inclut le chiffre horaire 24-— il ne s'agit donc pas d'une série quotidienne et elle ne doit pas être interprétée comme telle. Ce que ces données mettent en évidence est précis et clairement énoncé : sur les fenêtres glissantes publiées par Skinport, le prix médian réalisé est resté inférieur à sa propre médiane sur 90-jours et le nombre quotidien de ventes a baissé en conséquence.\n\nSkinport ventes réalisées. Les fenêtres sont imbriquées et glissantes ; chaque point correspond donc au prix médian réalisé sur la fenêtre glissante, indexé par rapport à la médiane du jour 90-. Il ne s'agit pas d'une série quotidienne et aucune donnée d'Steams n'est prise en compte.\n\n07 / de quoi est-il fait ?\nDes autocollants vieux de seize ans et une poignée de gants\n\nL'ensemble présenté ci-dessus ne représente pas une partie significative du marché. Il se concentre sur quelques pièces rares et quelques collections, dont plusieurs ne sont plus du tout disponibles — ce qui explique précisément pourquoi l'offre ne peut pas s'adapter au prix.\n\nCatégories au-dessus de la limite, classées par rareté\nnombre de catégories d'articles\nCovert\n321\nClassified\n39\nRestricted\n24\nContraband\n12\nMil-Spec Grade\n9\nConsumer Grade\n9\nIndustrial Grade\n5\nCatégories au-dessus de la barre, par collection\nles dix meilleures collections\nThe St. Marc Collection\n13\nThe Cobblestone Collection\n13\nThe Norse Collection\n12\nThe Arms Deal Collection\n9\nThe Canals Collection\n7\nThe Gods and Monsters Collection\n6\nThe Revolution Collection\n4\nThe 2021 Train Collection\n4\nThe Rising Sun Collection\n4\nThe Chop Shop Collection\n4\n\nPar catégorie : skin 366, sticker 48, container 3, sticker_slab 2.\n\n08 / le montant le plus élevé que quelqu'un ait réellement payé\nDes sommets soutenus par une transaction, et non par une cotation en bourse\n\nTous les autres prix figurant sur cette page correspondent à un demander — ce que souhaite un vendeur. Il s'agit notamment de ventes: le montant le plus élevé d'une transaction Skinport enregistrée pour chaque article, sur les 90 derniers jours. C'est le seul chiffre de ce dossier qui corresponde à un montant réellement payé par un client, et chaque ligne comporte un lien vers la plateforme de vente en ligne, ce qui permet de vérifier ce montant directement à la source plutôt que par notre intermédiaire.\n\n21,216articles dont la vente a été finalisée, en vitrine\n106vendu à un prix égal ou supérieur au plafond de cotation fixé par « Valve »\n$14,192vente la plus élevée jamais réalisée\n67/419catégories « au-delà du plafond » pour lesquelles une vente a été enregistrée\nLes trente ventes les plus élevées conclues au cours de cette période\nArticle\tMeilleure vente\tPrix de vente médian\tVentes\tDemandez dès maintenant le prix le plus bas\tSteam\tJette un œil\nAWP | Gungnir (Factory New)\t$14,192\t$11,343\t5\t$11,490\tabsent\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Factory New)\t$12,387\t$12,387\t1\t$13,836\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Factory New)\t$11,779\t$11,063\t16\t$10,941\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Minimal Wear)\t$11,693\t$11,693\t1\t$9,946\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Minimal Wear)\t$10,437\t$10,437\t1\t$9,610\tabsent\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Blue Laminate (Minimal Wear)\t$9,772\t$37\t76\t$30\t$40\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Minimal Wear)\t$9,463\t$9,463\t1\t$9,500\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Minimal Wear)\t$9,104\t$9,026\t6\t$8,524\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Hedge Maze (Minimal Wear)\t$8,139\t$8,139\t1\t$6,819\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Field-Tested)\t$7,617\t$7,390\t4\t$7,194\tabsent\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Field-Tested)\t$7,615\t$7,615\t1\t$7,100\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Field-Tested)\t$7,149\t$7,006\t2\t$7,165\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Field-Tested)\t$6,711\t$6,194\t15\t$5,988\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Factory New)\t$6,679\t$6,613\t3\t$6,628\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Superconductor (Factory New)\t$6,084\t$6,084\t1\t$7,969\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Battle-Scarred)\t$5,750\t$5,413\t3\t$5,899\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Pandora's Box (Minimal Wear)\t$5,520\t$5,508\t3\t$4,998\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Vice (Factory New)\t$5,385\t$5,158\t2\t$5,700\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Minimal Wear)\t$5,342\t$4,989\t19\t$4,997\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Hedge Maze (Field-Tested)\t$5,334\t$4,862\t5\t$3,724\tabsent\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Vulcan (Factory New)\t$5,275\t$1,418\t12\t$1,280\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Well-Worn)\t$4,978\t$4,978\t1\t$4,942\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Well-Worn)\t$4,931\t$4,931\t1\t$5,445\tabsent\tSkinport CSFloat Steam\nAK-47 | Hydroponic (Factory New)\t$4,802\t$4,351\t2\t$3,648\tabsent\tSkinport CSFloat Steam\n★ Talon Knife | Case Hardened (Minimal Wear)\t$4,588\t$466\t16\t$442\t$630\tSkinport CSFloat Steam\nAWP | Medusa (Factory New)\t$4,484\t$4,484\t1\t$4,171\tabsent\tSkinport CSFloat Steam\n★ Specialist Gloves | Pillow Punchers (Factory New)\t$4,359\t$4,359\t1\t$4,302\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Pandora's Box (Field-Tested)\t$4,359\t$3,666\t11\t$3,245\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Field-Tested)\t$4,289\t$4,225\t8\t$4,022\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Battle-Scarred)\t$4,124\t$4,124\t1\t$4,279\tabsent\tSkinport CSFloat Steam\nMême article, mêmes conditions d'90, mais un prix radicalement différent\n\nOn s'est limité aux articles dont la médiane est de $100 et qui ont fait l'objet d'au moins cinq ventes, car pour un skin bon marché, une seule vente exceptionnelle fausse le ratio. Ce qui reste est dominé par Cémenté finitions, où le motif détermine le prix et où la place de marché classe chaque motif sous un seul nom — le même mécanisme mesuré par « float » dans la section 05.\n\nArticle\tValeur maximale vs médiane\tMeilleure vente\tPrix de vente médian\tVentes\tJette un œil\n★ Talon Knife | Case Hardened (Minimal Wear)\t+884%\t$4,588\t$466\t16\tSkinport CSFloat Steam\nDesert Eagle | Cobalt Disruption (Factory New)\t+859%\t$1,210\t$126\t115\tSkinport CSFloat Steam\nAWP | BOOM (Minimal Wear)\t+814%\t$1,232\t$135\t89\tSkinport CSFloat Steam\nAK-47 | Case Hardened (Well-Worn)\t+769%\t$1,720\t$198\t70\tSkinport CSFloat Steam\nAWP | Graphite (Factory New)\t+761%\t$1,469\t$171\t124\tSkinport CSFloat Steam\n★ Talon Knife | Case Hardened (Field-Tested)\t+509%\t$2,437\t$400\t48\tSkinport CSFloat Steam\n★ Kukri Knife | Case Hardened (Minimal Wear)\t+448%\t$723\t$132\t69\tSkinport CSFloat Steam\n★ Kukri Knife | Case Hardened (Field-Tested)\t+415%\t$549\t$106\t128\tSkinport CSFloat Steam\n★ Ursus Knife | Case Hardened (Minimal Wear)\t+371%\t$597\t$127\t12\tSkinport CSFloat Steam\nAK-47 | Case Hardened (Field-Tested)\t+369%\t$1,037\t$221\t125\tSkinport CSFloat Steam\nAK-47 | Red Laminate (Minimal Wear)\t+360%\t$552\t$120\t18\tSkinport CSFloat Steam\nAWP | Asiimov (Field-Tested)\t+351%\t$528\t$117\t439\tSkinport CSFloat Steam\nAK-47 | Vulcan (Field-Tested)\t+337%\t$865\t$198\t241\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Nightwish (Factory New)\t+322%\t$625\t$148\t31\tSkinport CSFloat Steam\nAWP | Lightning Strike (Factory New)\t+319%\t$2,065\t$493\t198\tSkinport CSFloat Steam\nStatTrak™ AWP | Redline (Minimal Wear)\t+312%\t$574\t$139\t24\tSkinport CSFloat Steam\nStatTrak™ AWP | Asiimov (Battle-Scarred)\t+287%\t$524\t$135\t37\tSkinport CSFloat Steam\nAK-47 | Redline (Minimal Wear)\t+277%\t$562\t$149\t112\tSkinport CSFloat Steam\nAWP | Crakow! (Factory New)\t+275%\t$379\t$101\t72\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Vulcan (Factory New)\t+272%\t$5,275\t$1,418\t12\tSkinport CSFloat Steam\n\nIl s'agit d'un record journalier de 90-, et NON d'un record historique, et cela ne concerne qu'UNE seule place de marché. Aucun chiffre historique n'est mentionné nulle part dans ce dossier. Un article dont la vente sur Skinport n'apparaît pas dans la fenêtre est totalement absent de cette présentation, ce qui explique pourquoi l'ensemble est plus restreint que le recensement.\n\nLes liens de vérification sont générés à partir des identifiants propres à la plateforme du catalogue. Ils renvoient vers la page de chaque site de vente en ligne consacrée à l'article, afin que le lecteur puisse vérifier l'illustration directement auprès de la source plutôt qu'auprès de nous. Les liens sortants renvoient vers rel=\"nofollow\": il s'agit de citations, et non de recommandations, et plusieurs de ces destinations sont des places de marché que cette enquête critique.\n\n09 / provenance et limites\nD'où cela vient-il et ce que cela ne peut pas montrer\n\nChaque chiffre figurant sur cette page a été recalculé à partir de deux fichiers d'instantanés dont les hachages sont publiés à côté. Aucune information présentée ici n'est tirée d'un article publié sur un autre site.\n\nSource et accès\n\ncs2.sh API, GET /v1/prices/latest et GET /v1/schema, instantané unique, capturé le 2026-09-23T00 :44:27.871388581Z, prix en USD.\n\nCes données ont été obtenues dans le cadre d’un abonnement commercial payant souscrit par le demandeur de l’GDPR, tel qu’indiqué dans les archives, conformément aux conditions générales du fournisseur. Aucune plateforme de vente en ligne n'a fait l'objet d'un scraping et aucun identifiant d'aucune plateforme n'a été utilisé. La clé du demandeur est conservée en dehors de ce référentiel et n'apparaît dans aucun fichier ici.\n\nConditions d'éligibilité d'un article\n\nChaque article de base comportant au moins une offre active sur BUFF, CSFloat, Skinport, YouPin ou C5Game est classé dans une fourchette de prix en fonction de son offre la MOINS CHÈRE ; ainsi, cette fourchette ne dépend jamais de Steam. La « couvertureSteam » correspond à la part des articles de cette fourchette qui font l’objet d’une offre active sur Steam au moment de la capture. Les variantes de modèle et de phase sont exclues du classement car Steam ne les répertorie pas séparément ; leur inclusion conduirait à une sous-estimation de Steam. Les « rendus » correspondent aux images de catalogue des mêmes articles, stockées localement.\n\nRendu et droits d'image. Les rendus des articles du catalogue sont les images fournies par le prestataire pour le même « market_hash_name » que les lignes de prix ; elles sont stockées localement pour un affichage hors ligne et via IPFS. Ces rendus ne constituent pas l'œuvre d'PhishDestroy : toutes les images d'articles, logos et captures d'écran restent la propriété de leurs propriétaires respectifs (cs2.sh, CSFloat, Skinport, BUFF, YouPin, C5Game, Valve et autres). Ils sont reproduits uniquement à des fins d'identification et d'information d'intérêt public ; aucun droit de propriété ni aucune licence ne sont revendiqués.\n\nCe que nous n'avons pas pu obtenir\n\nLe niveau d'abonnement utilisé ne prend en charge que les instantanés actuels. Les points de terminaison historiques et d'archivage n'étaient pas disponibles, et aucune série historique n'est mentionnée nulle part sur cette page Au-delà des ventes sur une fenêtre glissante, l'Skinporte se publie dans la rubrique « 06. ».\n\nIl s'agit d'un instantané, et non d'une série chronologique. L'absence d'annonce sur Steam au moment de la capture ne prouve pas qu'un objet n'y apparaîtra jamais ; il s'agit simplement de l'état de l'étagère à ce moment-là, et pour les prix supérieurs au plafond, c'est également ce qu'exige la règle publiée par Valve : le Marché communautaire de Valve plafonne explicitement les annonces à $1,800 par objet (avec un solde maximal du portefeuille Steam de $2,000 ; voir Steam FAQ sur le marché communautaire archivé 2026-09-21 ↗ et Steam Contrat d'abonnement, § 3.C archivé 2026-09-24 ↗).\n\nNotation\n\nLe prix d'un article correspond toujours à son cours vendeur en temps réel le plus bas ; ainsi, une valeur aberrante élevée ne peut jamais gonfler le total. Le classement détermine quelles lignes peuvent être prises en compte. Toute cotation supérieure à trois fois le cours vendeur le plus bas pour le même article est écartée, car elle n'est pas considérée comme un prix en temps réel. Catégorie A : au moins trois places de marché proposent encore des prix supérieurs au plafond et leur médiane se situe à moins de 25 % du prix le plus bas. Catégorie B : deux places de marché s'accordent, ou trois s'accordent de manière moins stricte. Catégorie C : une seule offre – un prix demandé, et non un prix de marché. Seules les catégories A et B sont mentionnées dans ce dossier.\n\nRègle relative aux valeurs aberrantes : cours > 3.0multiplié par le cours vendeur le plus bas sur le même titre.\n\nPourquoi les totaux correspondent à un seuil minimal\n\nPour chaque place de marché, l'article le plus bas Le prix « ask » est multiplié par le nombre d'exemplaires répertoriés dans le catalogue. Tous les autres exemplaires sont proposés à un prix égal ou supérieur à ce prix « ask » le plus bas ; la valeur réelle affichée est donc plus élevée par nature, et non par estimation. Il ne s'agit ni d'une vente, ni d'un flux de trésorerie, ni d'une évaluation de l'économie CS2.\n\nVérifiez par vous-même\n\nLes ensembles de données dérivés qui sont à l'origine de chaque graphique de cette page sont publiés dans leur intégralité : le jeu de données « atlas », l'écran de classement et d'artefacts, le recensement de référence et le manifeste contenant le SHA-256e de chaque instantané brut.\n\nUne correction enregistrée en séance\n\nUne version antérieure du registre d'accompagnement commençait par un AK-47 « Souvenir » | « Point Disarray », proposé à148,954 $ sur une plateforme de vente chinoise, tandis que Steam l'évaluait à119. $ Cette entrée est de catégorie C : une seule référence, un seul exemplaire, et aucune autre plateforme ne confirme ce prix. Il s'agit d'un prix demandé, et non d'un prix confirmé, et il a été rétrogradé ici ainsi que sur cette page. Le meilleur prix confirmé est celui de l’autocollant | Titan (Holo) | Katowice 2014 à $66,285, cité par 4 : des places de marché situées à 5.2% les unes des autres — et totalement absentes de Steam.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Atlas des échelles de prix de Skin — La « falaise de liquidité »"
          },
          {
            "level": 2,
            "id": null,
            "text": "La falaise s'effondre selon la règle, et non à la demande"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ce que la forme exclut"
          },
          {
            "level": 2,
            "id": null,
            "text": "Un prix demandé n'est pas un prix"
          },
          {
            "level": 3,
            "id": null,
            "text": "A  Trois étagères ou plus sont identiques"
          },
          {
            "level": 3,
            "id": null,
            "text": "B  Les deux étagères sont identiques"
          },
          {
            "level": 3,
            "id": null,
            "text": "C  Une étagère — non utilisée"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ce qu'a coûté cette correction, et ce qu'elle a permis d'obtenir"
          },
          {
            "level": 3,
            "id": null,
            "text": "Entrées classées comme « artefacts »"
          },
          {
            "level": 2,
            "id": null,
            "text": "Toutes les catégories d'419, avec l'objet auquel chaque prix se rapporte"
          },
          {
            "level": 2,
            "id": null,
            "text": "Les rayons qui proposent ce que Steam ne propose pas"
          },
          {
            "level": 2,
            "id": null,
            "text": "À quel point l'offre est-elle réellement limitée ?"
          },
          {
            "level": 2,
            "id": null,
            "text": "Ce qu'ont réellement réalisé les rayons des marques tierces"
          },
          {
            "level": 2,
            "id": null,
            "text": "Des autocollants vieux de seize ans et une poignée de gants"
          },
          {
            "level": 2,
            "id": null,
            "text": "Des sommets soutenus par une transaction, et non par une cotation en bourse"
          },
          {
            "level": 3,
            "id": null,
            "text": "Les trente ventes les plus élevées conclues au cours de cette période"
          },
          {
            "level": 3,
            "id": null,
            "text": "Même article, mêmes conditions d'90, mais un prix radicalement différent"
          },
          {
            "level": 2,
            "id": null,
            "text": "D'où cela vient-il et ce que cela ne peut pas montrer"
          },
          {
            "level": 3,
            "id": null,
            "text": "Source et accès"
          },
          {
            "level": 3,
            "id": null,
            "text": "Conditions d'éligibilité d'un article"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ce que nous n'avons pas pu obtenir"
          },
          {
            "level": 3,
            "id": null,
            "text": "Notation"
          },
          {
            "level": 3,
            "id": null,
            "text": "Pourquoi les totaux correspondent à un seuil minimal"
          },
          {
            "level": 3,
            "id": null,
            "text": "Vérifiez par vous-même"
          },
          {
            "level": 3,
            "id": null,
            "text": "Une correction enregistrée en séance"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/fr/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/fr/skin_atlas#gallery",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://skinport.com/market?search=AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260924114457/https://store.steampowered.com/subscriber_agreement/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-atlas.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-artefact-screen.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-above-the-ceiling.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/fr/skin_atlas.content.json",
      "export_json_sha256": "1507a3eb70f015eecb0f747a3df82786f3a5117ddff9ce66851c59a350c9d750"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "fr/social_graph.html",
      "language": "fr",
      "title": "Suivez les liens enregistrés — Le dossier «Steam »",
      "source_url": "https://phishdestroy.io/steam_dossier/fr/social_graph",
      "source_html_sha256": "c5eea95831bfcfc5eef6159151eff08df7661c788829975f467b989ffd78475b",
      "exported_at": "2026-09-29T00:17:41.968Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "social_graph.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/fr/social_graph.pdf?v=print-20260929-v5",
        "sha256": "7eb47957beca4f19ab2f25e09038bf10e9132ff9f35d98593fc61bf0753fc924",
        "bytes": 121352,
        "pages": 6
      },
      "integrity": {
        "signed_object": "social_graph.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "social_graph.content.json.asc",
        "digest_file": "social_graph.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify social_graph.content.json.asc social_graph.content.json",
          "sha256sum -c social_graph.content.json.sha256"
        ]
      },
      "content": {
        "text": "Suivez les liens.Vérifiez chaque relation.\n\nRecherchez un profil. Choisissez un type de relation. Suivez ses voisins directs dans les enregistrements récupérés. Outil de recherche : Les arêtes représentent des relations publiques et ne constituent pas une preuve de contact direct, de coordination privée ou de comportement répréhensible entre deux nœuds quelconques. Pour bien comprendre la structure d’un nœud « 3,435-», il est préférable d’utiliser des filtres.\n\nDécouvrez une relation à la fois\n\n💡 Cliquez sur les nœuds et faites-les glisser pour réorganiser le graphique. Passez la souris dessus pour afficher les profils détaillés. Lignes pleines bleu sarcelle = amitiés, lignes pointillées orange = commentaires mutuels.\n\nType de relationProfil et voisins directs\n\n3,435 profils · liens enregistrés sur 4,551\n\nRecherchez et sélectionnez un profil, ou cliquez sur un nœud. Seuls ses voisins directs enregistrés sont conservés. Une arête enregistre une relation ; elle n'établit pas de coordination privée.\n\nProfils contenus dans l'ensemble de données capturé\n\nTableau complet des sources : Télécharger toutes les lignes de « 3,435 » (CSV). Le tableau ci-dessous présente dans un premier temps les 25 premières lignes ; la fonction de recherche et la pagination permettent de consulter l'intégralité de l'ensemble de données.\n\n1–25 / 3,435 lignes\nNom du personnage\tSteamID64\tConfidentialité\tStatut\tAdhésions à des groupes\tStocks immobilisés (USD)\tLieu\nMahatma Gandhi\t76561198333721623\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tPH\nGalley//갤리🌠🌙\t76561198043416832\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tKP\n$Schlächter\t76561198860277343\tPUBLIC\tClean\tsteambans\t$0.00\tUnknown\n❄r3dsn0w000™❄ [Cristi]🎮\t76561197986767957\tPUBLIC\tClean\tCommunityLegends\t$0.00\tRO\n(2a03) Wolfy\t76561197991671851\tPUBLIC\tCommunity\tsr_public\t$0.00\tUS\nZloy2288\t76561198038578334\tPUBLIC\tClean\tsteambans\t$0.00\tBY\njessy\t76561198039125237\tPUBLIC\tCommunity, VAC (1x)\tCommunityLegends\t$0.00\tJP\nJithraRufure\t76561198071896910\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\n| Níllerdínho |\t76561198003487438\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tDK\nJones is back\t76561198023013026\tPRIVATE\tVAC (1x)\tsteambans\t$0.00\tUnknown\nUNEX | ★✠☠ MoH3st ☠✠\t76561198050763123\tPUBLIC\tClean\tsteambans\t$0.00\tDE\nTrojan\t76561198048457084\tPUBLIC\tClean\tCommunityLegends\t$0.00\tDE\n𝗠𝗮𝘆𝘂 ❤\t76561199377967696\tPUBLIC\tClean\tsr_public\t$0.00\tIS\nbig fucking idiot\t76561198871206397\tPUBLIC\tVAC (1x)\tsteambans\t$0.00\tUnknown\nSOFF Games\t76561198227129276\tPUBLIC\tClean\tcommunitymoderators\t$0.00\tRU\nThijminecraft02\t76561198253895669\tPUBLIC\tClean\tSteamIDcouk SArchive\t$0.00\tNL\nStatic-sama\t76561198289329793\tPUBLIC\tClean\tsteambans\t$0.00\tJP\n𝙸mmortal 𝚂targazer\t76561198142116760\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\nCommander Keen\t76561197987773287\tPUBLIC\tClean\tsteambans\t$0.00\tBE\nS1mX\t76561199648509165\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\nmixwell\t76561199276547472\tPUBLIC\tClean\tsr_public\t$0.00\tJP\nP90_GOD_YyEs™\t76561198285821942\tPUBLIC\tClean\tsteambans\t$0.00\tHK\nhewwo?\t76561199133807546\tPUBLIC\tVAC (1x)\tsteambans\t$0.00\tCH\n♕Kamikaze Atze♕\t76561198002700103\tPUBLIC\tClean\tsteambans\t$0.00\tDE\nPastica\t76561198154655970\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tDZ\nLiens d'amitié enregistrés\n\nTableau complet des sources : Télécharger toutes les lignes de « 4,299 » (CSV). Le tableau ci-dessous présente dans un premier temps les 25 premières lignes ; la fonction de recherche et la pagination permettent de consulter l'intégralité de l'ensemble de données.\n\n1–25 / 4,299 lignes\nUtilisateur A\tDirection\tUtilisateur B\tType de relation\nMahatma Gandhi\n76561198333721623\t↔\tDeskjet\n76561198272738437\tMutual Friends\nGalley//갤리🌠🌙\n76561198043416832\t↔\tomega\n76561197960274529\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tFisty\n76561198057301486\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tFaalagorn\n76561198001116101\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tMURK\n76561198036995672\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tÅρøᴛʜℯᴛȋᴄÅʟȋℯη ♛👽♛\n76561197984615267\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tsilatrak\n76561197999629462\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tBlack Blade\n76561198083368493\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tAvenger\n76561197978249317\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tRemtar\n76561198124322650\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tCato\n76561197961345984\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t✪ G λ M Ξ ®\n76561197994308495\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tclees42\n76561198030936806\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t𝓜ε𝔰𝔥 | AusLevels\n76561198108828539\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tSgtFopper™\n76561198002555892\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t❥Miss Bee\n76561198046958996\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tTesTy\n76561198032370068\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tskl_andrey\n76561198136881436\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t\"Exekutor\"\n76561198009583947\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tAraripe\n76561198103754372\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tsteve6678\n76561198053200093\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\ttrinner\n76561197970359081\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tSteph S.\n76561198025653291\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tKirito\n76561198154545657\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tDoc. todt\n76561197984492467\tMutual Friends\nLiens vers les commentaires enregistrés\n\nTableau complet des sources : Télécharger toutes les lignes de « 252 » (CSV). Le tableau ci-dessous présente dans un premier temps les 25 premières lignes ; la fonction de recherche et la pagination permettent de consulter l'intégralité de l'ensemble de données.\n\n1–25 / 252 lignes\nAuteur\tDirection\tProfil cible\tDate\tTexte du commentaire\nDeskjet\n76561198272738437\t→\tMahatma Gandhi\n76561198333721623\t16 September, 2021 @ 11:02:05 pm PDT\t\"𝑵𝒐𝒘 𝒊𝒇 𝑰 𝒇𝒖𝒄𝒌 𝒕𝒉𝒊𝒔 𝒎𝒐𝒅𝒆𝒍𝑨𝒏𝒅 𝒔𝒉𝒆 𝒋𝒖𝒔𝒕 𝒃𝒍𝒆𝒂𝒄𝒉𝒆𝒅 𝒉𝒆𝒓 𝒂𝒔𝒔𝒉𝒐𝒍𝒆𝑨𝒏𝒅 𝑰 𝒈𝒆𝒕 𝒃𝒍𝒆𝒂𝒄𝒉 𝒐𝒏 𝒎𝒚 𝑻-𝒔𝒉𝒊𝒓𝒕𝑰'𝒎𝒎𝒂 𝒇𝒆𝒆𝒍 𝒍𝒊𝒌𝒆 𝒂𝒏 𝒂𝒔𝒔𝒉𝒐𝒍𝒆\" - Nelson Mandela\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t22 November, 2021 @ 4:10:28 pm PDT\thttps://anige.horigiri.net/?cat=22\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t18 November, 2021 @ 12:45:26 am PDT\thttps://gamerch.com/umamusume/entry/250411\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t8 August, 2021 @ 4:13:25 am PDT\thttps://modoocode.com/304\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t6 February, 2021 @ 3:35:05 pm PDT\t▤ ∫︹- -ω⁾ ⁽︹▓▓︺\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t11 December, 2019 @ 1:50:53 am PDT\thttps://blog.naver.com/aksenwlddj12/221369410039\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t2 October, 2019 @ 7:11:59 am PDT\tǤαllєу║︎갤리..۩\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t9 April, 2019 @ 12:51:28 pm PDT\tExplosiveDamage(owner, from, maxrange, minrange, distmultiplier, dmgmultiplier, mindamage, typ, damagetype, ignore)\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 12:22:47 pm PDT\tinfo - sh_titles.lua\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 12:21:46 pm PDT\tlocal nibbas = 1344 init.lua\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 11:31:58 am PDT\thttp://foreign.aladin.co.kr/shop/wproduct.aspx?ItemId=123955531&start=slayer\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t3 April, 2019 @ 1:26:41 am PDT\tǤαllєу\nLei\n76561198982197954\t→\tJithraRufure\n76561198071896910\t29 December, 2024 @ 12:58:08 pm PDT\t+rep he knows how 2 rush B ￣ヘ￣\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t2 September, 2026 @ 5:16:55 am PDT\tlol\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t20 August, 2026 @ 6:11:03 am PDT\t?\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t25 July, 2026 @ 7:20:05 am PDT\thahahahaha\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t30 June, 2026 @ 12:52:42 pm PDT\twow\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t30 June, 2026 @ 12:41:32 pm PDT\txD\nvalorant enjoyer\n76561199112142402\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:26:30 pm PDT\toh no!!\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:26:11 pm PDT\toh no!!\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:22:22 pm PDT\tomg !!! they know my secret, omg!!!\nvalorant enjoyer\n76561199112142402\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:21:39 pm PDT\t+rep good ♥♥♥♥♥ player\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:20:50 pm PDT\tomg! u cant cheat on secure gaben servers, omg dont report me, they ban me for boosted omg\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 8:37:11 pm PDT\txD\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t28 June, 2026 @ 1:58:14 pm PDT\twow",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Suivez les liens.Vérifiez chaque relation."
          },
          {
            "level": 2,
            "id": null,
            "text": "Découvrez une relation à la fois"
          },
          {
            "level": 2,
            "id": null,
            "text": "Profils contenus dans l'ensemble de données capturé"
          },
          {
            "level": 2,
            "id": null,
            "text": "Liens d'amitié enregistrés"
          },
          {
            "level": 2,
            "id": null,
            "text": "Liens vers les commentaires enregistrés"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-profiles.csv",
          "https://steamcommunity.com/profiles/76561198333721623",
          "https://steamcommunity.com/profiles/76561198043416832",
          "https://steamcommunity.com/profiles/76561198860277343",
          "https://steamcommunity.com/profiles/76561197986767957",
          "https://steamcommunity.com/profiles/76561197991671851",
          "https://steamcommunity.com/profiles/76561198038578334",
          "https://steamcommunity.com/profiles/76561198039125237",
          "https://steamcommunity.com/profiles/76561198071896910",
          "https://steamcommunity.com/profiles/76561198003487438",
          "https://steamcommunity.com/profiles/76561198023013026",
          "https://steamcommunity.com/profiles/76561198050763123",
          "https://steamcommunity.com/profiles/76561198048457084",
          "https://steamcommunity.com/profiles/76561199377967696",
          "https://steamcommunity.com/profiles/76561198871206397",
          "https://steamcommunity.com/profiles/76561198227129276",
          "https://steamcommunity.com/profiles/76561198253895669",
          "https://steamcommunity.com/profiles/76561198289329793",
          "https://steamcommunity.com/profiles/76561198142116760",
          "https://steamcommunity.com/profiles/76561197987773287",
          "https://steamcommunity.com/profiles/76561199648509165",
          "https://steamcommunity.com/profiles/76561199276547472",
          "https://steamcommunity.com/profiles/76561198285821942",
          "https://steamcommunity.com/profiles/76561199133807546",
          "https://steamcommunity.com/profiles/76561198002700103",
          "https://steamcommunity.com/profiles/76561198154655970",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-connections.csv",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-comments.csv"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/fr/social_graph.content.json",
      "export_json_sha256": "ba8902aaab4d1a76d10330bb815f8817d8c07ce66f56ec10140ea8476d485be2"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "fr/steam_enforcement_evidence.html",
      "language": "fr",
      "title": "Règles contre réactions — Le dossier «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/fr/steam_enforcement_evidence",
      "source_html_sha256": "98fcf8d54f7bc7ffb6e4389526eaf547c174b262b0f7500537b78662b10c8255",
      "exported_at": "2026-09-29T00:17:42.716Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "steam_enforcement_evidence.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/fr/steam_enforcement_evidence.pdf?v=print-20260929-v5",
        "sha256": "32b3a32a8ed2444229a1a3febc6caa9aa547a3831816172d0604687713b745c9",
        "bytes": 380790,
        "pages": 36
      },
      "integrity": {
        "signed_object": "steam_enforcement_evidence.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "steam_enforcement_evidence.content.json.asc",
        "digest_file": "steam_enforcement_evidence.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify steam_enforcement_evidence.content.json.asc steam_enforcement_evidence.content.json",
          "sha256sum -c steam_enforcement_evidence.content.json.sha256"
        ]
      },
      "content": {
        "text": "Supplément aux pièces justificatives / documents liés à leur source\nSteam Preuves relatives à l'application de la réglementation — Documents justificatifs et réseau des promoteurs immobiliers\n\nLa règle. La réponse.\n\nCE QUE CETTE SECTION DÉMONTRERA\n\nCette salle des preuves compare le contrat d'abonnement officiel d'Valve à des journaux de mesures coercitives datés, à des résolutions de litiges liés à l'assistance et à des enregistrements du réseau des développeurs provenant des référentiels 252 et des profils 3,320. Elle démontre que les titulaires de comptes ordinaires font l'objet de mesures coercitives irréfutables et de fermetures de comptes par le service d'assistance à la suite de compromissions de session, tandis que les opérations commerciales à grand volume utilisant des bots continuent de fonctionner sans interruption grâce à un accès à l'infrastructure publique.\n\n← Retour au dossier de synthèse destiné aux dirigeants\n\nLisez la restriction écrite. Ouvrez la réponse enregistrée. Comparez ce qui figure dans la source avec ce qui reste sans réponse.\n\nAssistance et recours ↓Infrastructures publiques ↓\n252fiches du dépôt\n3,320profils publics\n4,214paires profil-référentiel distinctes\n98,902paires de profils avec des dépôts partagés\n01 / Aide, sanctions et rétablissement\nLisez la plainte.Veuillez joindre le fichier source.\nGalerie des refus de soutien (Expositions de 981) ↗Télécharger les enregistrements sélectionnés ↓\nHFB / L'AFFAIRE DE L'EXTERNALISATIONLe compromis reconnu.\nLes licenciements signalés.\n\nConsultez la réponse du service d'assistance reproduite ci-dessous ainsi que la source de l'affirmation concernant le personnel des sous-traitants.\n\nOuvrir le dossier et ses sources →\n\nCi-dessous : cinq spécimens conservés publications publiques sur Reddit issus de la collection d'enregistrements d'assistance fournie. Chaque enregistrement rend compte d'une interaction signalée avec le système d'assistance d'Valve — conservée avec son lien source d'origine, sa position de capture et son texte intégral. Il s'agit de témoignages de victimes. Les journaux d'assistance authentifiés qui pourraient les confirmer ou les contredire sont détenus par Valve et n'ont pas été divulgués.\n\n01\nBan & review2024-12-09\nPermanent sanction & closed appeals\n\nThe author reports a permanent account ban, repeated ticket closures and a planned GDPR access request.\n\nREDDIT / PUBLIC TESTIMONYr/ohnePixelCapture record 294\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 303 words\nPermanently banned Steam account without a clear explanation, need help!\n\nsteam_support_tickets_MEGA.json / record 294\n\nHey everyone,\n\nI’m in a really frustrating situation, and I’m hoping someone here can help me or offer advice. My Steam account was just permanently banned for allegedly violating the Steam Subscriber Agreement, and I have no idea why.\n\n# What Steam Support told me:\n\nThe support message said my account was banned due to:\n\n* Suspicious activities related to transferring or attempting to sell/trade the account.\n* Community reports and other unspecified factors.\n\nThey added that the ban is permanent and that they can't help me further. They also warned that future support requests regarding this ban might be ignored. 😞\n\n# Why I’m contesting this ban:\n\n* I have never sold, traded, or transferred my account. I’ve been the legitimate owner since the beginning.\n* On the day the ban occurred, I did nothing noteworthy that could have triggered such a sanction.\n* I received no prior warning, which feels incredibly unfair.\n\n# What I’ve tried so far:\n\n* Contacting Steam Support: I explained my situation and asked for more details, but they’re sticking to their decision and closing my tickets.\n* I’m preparing a request based on my Right of Access (GDPR) to get all the data related to my account.\n\n# Questions for the community:\n\n1. Has anyone successfully had a permanent ban lifted on Steam?\n2. Are there steps I can take to prove I’m the legitimate owner of the account?\n3. Any advice on how to word my request to convince support to reconsider my case?\n4. Would it be helpful to contact the CNIL (I’m based in France) to force Steam to provide more information?\n\nI’m really desperate at the thought of losing all my games, purchases, and years of playtime. Thanks in advance for any help and advice you can give!\n\nhttps://preview.redd.it/jk9qv0gmhv5e1.png?width=1289&amp;format=png&amp;auto=webp&amp;s=b3a333ebb08ea133e2c8747ba126f5a68283d9f7\n\nhttps://preview.redd.it/4sopt0gmhv5e1.png?width=1022&amp;format=png&amp;auto=webp&amp;s=56195d5336118faf9413f1514ead7e8d24c788c3\n\nhttps://preview.redd.it/eqrxw0gmhv5e1.png?width=996&amp;format=png&amp;auto=webp&amp;s=ff3539d28ab754e513ad471822c5de652920101d\n\nhttps://preview.redd.it/728xz0gmhv5e1.png?width=1034&amp;format=png&amp;auto=webp&amp;s=bc5335673509929669af785aa244bf8d2dc58da8\n\n02\nSupport access2025-05-09\nAccount recovery & a reported $10,000 loss\n\nThe author alleges that support reset credentials and removed account protection following another person’s recovery ticket.\n\nREDDIT / PUBLIC TESTIMONYr/legaladviceCapture record 110\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 193 words\nGot $10k stollen from steam inventory due to steam' support fault.\n\nsteam_support_tickets_MEGA.json / record 110\n\nLocation: Quebec, Canada.\n\nLast year, someone hacked my Steam account and stole items worth about $10,000 USD. I only noticed this last week. When I talked to Steam Support, they admitted that someone submitted a ticket to make changes on the account and Steam Support reset my password and turned off all my account security.\n\nI asked Steam Support about getting my items back, but they said there was nothing they could do. They told me I should follow their security recommendations.\n\nThe problem is, I did everything they \"suggested\" to protect an account:\n\n* I had two-factor authentication.\n* My phone number was connected to my account.\n* I used Steam Guard.\n* I printed recovery codes and kept them in a safe.\n\nEven though I did all these things, Steam Support still gave someone else access to my account. The stolen items had been in my account since around 2016-2017. Also, I had not logged in for a few years, so I didn’t accidentally give my information to a fake website.\n\nIs there anything I can do, or do I just have to accept losing $10,000 USD?\n\nThanks for your help.\n03\nRestoration2022-07-07\nA reported $500+ loss & template replies\n\nThe author describes an account compromise, disputed transactions and a support response that allegedly did not address the submitted evidence.\n\nREDDIT / PUBLIC TESTIMONYr/DotA2Capture record 45\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 410 words\nFunds stolen through steam market. Disappointed with Steam response.(or lackthereof)\n\nsteam_support_tickets_MEGA.json / record 45\n\nOn 6th July 2022, 44 unauthorized transactions were made on the steam market using my steam wallet funds totalling roughly $500+ USD to buy worthless 1 cent Dota 2 items. This happened during the wee hours in the morning and i contacted them first thing when i woke up. \n\nI have 2FA enabled all the time, and always thought this would not happen to me as I do not go on betting sites/click sketchy links. My account password + emails were not changed, nor did they take my inventory, just that my funds were used illicitly. Also when I went to disable other APIs, it says there are no other APIs to disable. Shows that it wasn't through me clicking sketchy links and leaving my account details there. Would have lost the whole account if i did so.\n\nWhat baffles me is how did they bypass my 2FA to login my account? Why doesn't steam market purchases go through 2FA as well? First time in 9 years that this happened to me. My acc was logged in 'BY' 'Vitebsk' during the illicit purchases but I'm based in Asia I gathered all the screenshots and provided in the ticket to steam support. \n\nAll i got was the standard copy paste template reply by Steam Support. Lost $500+ and was not even worthy of having a proper person to look into this. I dont think they even read or take a look at the screenshots cause if they did, they would have come to the realization that what happened was clearly fraud, and with a few clicks, reverse the unauthorized transactions, refund my wallet and ban the hijacker. \n\nOver the years, i've spent quite a fair bit on steam but really, this is the kind of recourse we get when our account is compromised? They just don’t care, sigh. I only expect the bare minimum from Steam and looks like even that is quite far-fetched.\n\nSS: https://imgur.com/a/67frcls \n\nHijacker: https://steamcommunity.com/profiles/76561199141246495\n\nSteam Response: https://imgur.com/a/V6v4maM\n\nI could think of a few ways on how to Improve:\n\n1) Add 2FA to market transactions. (even if its bulk posting or selling of items, just 1 2FA notif is required)\n\n2) Enable accounts to be region locked. (if you are migrating, then have to go through steam support etc)\n\n3) Additional Lock on Steam Wallet. (Another password perhaps?)\n\nEDIT: 2nd ticket in and I have still yet to receive a non robotic copy paste template response from Steam.\n04\nRestoration2021-11-29\nSteam Guard & an item-restoration refusal\n\nA preserved post includes the author’s account of item theft and a support response declining restoration.\n\nREDDIT / PUBLIC TESTIMONYr/DotA2Capture record 58\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 563 words\nMany people are losing item via clicking links where steam guard is enabled and steam support doesn't not restore items.\n\nsteam_support_tickets_MEGA.json / record 58\n\nAccounts are getting compromised and might be their pc as well where Steam market is targeted hence the malicious links . I am assuming these hackers are getting encouraged where steam support is not doing nothing and they are getting away with hacking items.  \nLiterally the guy who is supporting the game which he doesn't get any in game advantage just  cosmetics in game only for the sole purpose of supporting the game so that the game will prosper and become beautiful way  to enjoy weekend. But right now players are getting hacked left right and center and steam support  is copy pasting message where in short they are blaming the guy who clicked link. 1st this is happening because they are not targeting players but they are targeting market since they are selling those stuff for real cash via party website. Steam is a huge company and can eradicate the problem or at least can remove links temporarily  in chat since hackers are targeting .They made us install steam guard by saying we wont help if there is no steam guard now steam guard is not enough to save our inventory now they changed their policy  that they should not click any suspicious links. How would we know if the link is suspicious ? After clicking and getting our inventory stolen right !   \n\"we'd have to duplicate an item to restore it. Duplication lowers the value of all items by reducing their scarcity and inflating the economy, which affects everyone involved in trading and the Market. To maintain the value of everyone’s inventory, we do not restore items. For more information, please see the Steam Item Restoration Policy.\"  \nThey care for millions of people IN STEAM MARKET where as few  are losing items which is going to affect market where the rightful owner bought the items and hacker is going to sell the item via 3rd party website and enjoy ! HOW IRONIC !!  \nThis is the message from support where my frnd got his items stolen via clicking on link  \n   \nHi there,  \n\nThank you for the information and screenshots provided.  \n\nIt appears that the account was compromised, please take the following steps to secure your account and computer:  \n\nScan your computer for viruses, key loggers, spyware, and other malicious code using antivirus software with updated virus definitions.  \nChange the password for the email address that is associated with your Steam account.  \nRegularly reset your Steam account password.  \n\nPlease see our Security Recommendations article.  \n\nIn addition, I’m sorry to hear that your items were removed without your permission. Unfortunately, Steam Support does not restore scammed, lost, or stolen items for any reason.  \n\nSince Steam Support does not remove items from accounts, we'd have to duplicate an item to restore it. Duplication lowers the value of all items by reducing their scarcity and inflating the economy, which affects everyone involved in trading and the Market. To maintain the value of everyone’s inventory, we do not restore items. For more information, please see the Steam Item Restoration Policy.  \n\nTo make sure that a scammer is reported, please report them through the Steam Community. Reporting a scammer through the Steam Community is the best way to prevent them from committing future scams.  \n\nTo learn how to avoid scams or hijackings, please see our Trade Scam article.  \n\nIf you still need assistance, please let us know.\n05\nEnforcement2025-05-11\nSelective enforcement & an unexplained ban\n\nA community member describes a disputed ban and contrasts it with the visibility of commercial gambling promotion.\n\nREDDIT / PUBLIC TESTIMONYr/SteamUncensoredCapture record 107\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 1,208 words\n🚨 Steam Bans Without Reason and Ignores Its Community — What’s Going On?\n\nsteam_support_tickets_MEGA.json / record 107\n\nHey r/Steam,\n\nI’m writing this to share my thoughts and concerns about my friend [moneylead](https://steamcommunity.com/id/moneylead/) and Steam’s policies in general. I spoke with him yesterday about his situation, though I didn’t discuss writing this post with him—I asked last night, but he hasn’t responded yet. I want to highlight that this issue is broader than just his case, and while Steam might make changes in the future (though that’s unlikely), I feel the community needs to understand how far Steam has strayed from its original values. I’m not trying to put moneylead in a tough spot with this thread—all the info I’m sharing is public, nothing secretive. I hope he won’t be upset with me, but the community needs this case to see the bigger picture and how Steam feels completely unaccountable.\n\n**Why Does Steam Ignore Its Community?**  \nWhy does a platform like **Roblox** provide a detailed log of ban reasons, while Steam, which claims to be \"community-driven,\" ignores its community, bans whoever they want, for whatever they want, with no transparency? I looked into Roblox as a popular game—not a direct competitor to Steam—to see how their bans look, and you can check it out yourself: [Roblox Ban Reasons](https://www.google.com/search?q=Roblox+ban). Their bans are clear, detailed, and actually explain what you did wrong. I think most decent gaming communities operate like this—not with support agents named Olga, hired through outsourcing, who only know how to send canned auto-replies. Take cases like St4ck—or my friend **moneylead**. All these unbans, like **St4ck’s** or **Alexanddd’s**, happened behind closed doors with zero comments from Steam. Of course, it’s convenient for Steam to handle everything in secret, so no one knows or sees what’s going on—but this violates Steam’s own community rules and principles.\n\n**Who Is moneylead?**  \nI’ve known [moneylead ](https://steamcommunity.com/id/moneylead/)since around 2021. We played Dota 2 a couple of times, and then I just stayed on his friends list. He’s always been a legit player, bringing revenue to Steam through purchases. He never sold his skins, whether in **Dota or CS2—he wasn’t a trader**. All he did was:\n\n* Buy games and skins.\n* Collect badges to level up his profile.\n\nAccording to [SteamSets](https://steamsets.com/account/76561199080934614), he’s given out 324,000 Steam Points—I think he awarded profile rewards to all his friends in the list (though I’m not 100% sure). I do know he ran contests and gave gifts to friends, always supporting the community.\n\n**Steam’s Unfair Treatment**  \nI’ve seen Steam remove his showcases, avatar, description, and even his country multiple times—just because he’s from **Ukraine**. He has a ton of haters leaving toxic comments on his wall, and Steam seems to favor **Russian** users. Every time he tried to appeal the removal of his showcases or profile description—which didn’t break any rules, just had his Instagram link, and his avatar is the same as it is now—Steam moderators didn’t care. **They don’t care about top players who bring them massive revenue, nor about regular users.**\n\n>*Here’s the worst part: moneylead works in cybersecurity, specifically fighting account theft and phishing. He’s neutralized over 5,000 threats targeting Steam alone. And yet, Steam bans him for \"account hijacking\"?*\n\nIf you roughly calculate moneylead’s contribution to Steam and the community—his profile, level, badges (not skins, you can’t sell those)—is this normal, Steam? Banning people, closing tickets, and ignoring users with a spotless reputation who aren’t involved in any commercial activity, just bringing you profit without taking anything in return?\n\n**Steam’s Double Standards**  \nI’m honestly shocked:\n\n* YouTubers who promote casinos and skin gambling? Steam’s fine with that.\n* A cybersecurity expert who fights scams, doesn’t promote casinos, and openly talks about it on his profile? **Banned with no explanation, ignored, and denied an unban.**\n\nI wonder if Steam deliberately bans a high-level account once a year just because of their impunity—maybe for hype or something. Otherwise, this is just madness. It’s scary to think how many regular players have lost their accounts and skins—not because of scammers, but because of Steam’s desire to ignore, send auto-replies, and do whatever they want.\n\n**How Many Others Are Affected?**  \nHow many others are out there—maybe not as well-known—who just have a few games or skins, get banned for nothing, and receive zero explanation or response? **Is this even legal?** Every other platform provides a detailed log with specific violations, but Steam slaps on the same vague label and sends templated responses.\n\n* How safe is it to buy skins on Steam?\n* What’s the chance Steam will just ban your account for no reason, with no explanation?\n\n**A Message to Valve**  \nI wish moneylead the best in resolving this, but Valve, it’d be great if you remembered what \"community\" means and started following the law. Because right now, it looks like your 30% commission, impunity, and sense of being above the law in the U.S. have given you the idea that you can do whatever you want.\n\nI’m sure there are many others like moneylead and St4ck—people who aren’t public or don’t have the resources to fight back. Let’s unite these cases. **If you’re a U.S. resident who’s been banned by Steam without reason and wants to challenge it, please reach out to me.** I’m finishing my **Juris Doctor (J.D.) program at SMU Dedman School of Law** in Dallas, Texas, and I’m participating in a legal clinical practice under Rule 13 of the Texas Supreme Court.\n\nWhat Steam is doing is absolutely disgusting and illegal, and **I’d be happy to help any gamer (legitimate, with no real violations) who has games or skins with value. This will be beneficial for my practice, and it’s time to put Steam in its place and show them they can’t just dictate their own rules with arbitration**. Let’s take it all the way—not for punishment, but for the sake of the community. Maybe if Steam loses a case, they’ll change their policies and start explaining their actions like most popular gaming communities do. Many of us remember how Steam Support used to recover stolen accounts and ended up “stealing” skins themselves—banning without real reasons is basically the same thing, and that’s a serious accusation.\n\nSo, r/Steam, see you soon. I think you understand what you’re doing and how many people you’ve illegally deprived of their assets. I want to raise this issue—not just for the U.S., but for the entire world. You’ve banned class-action lawsuits? **Welcome to Texas.** I recommend starting to look for licensed attorneys in Texas, because I’d love to discuss your company’s policies, feedback, and support agents named Olga—a name that strongly associates with Russian users. Maybe it’d be easier to move your company to Moscow? But I’d be happy to discuss these critical issues on behalf of the global gaming community.\n\nAlso, I wouldn’t recommend ignoring the lawsuit request that will be sent to your physical address and email address, as the court will proceed without you, and that might upset you—especially since things aren’t going so well for a company with stocks like yours.\n\n**Thanks to everyone who took the time to read this. For those who need real help with an unjust Steam ban without any explanation, I’d be happy to assist. For users from Texas, we can easily file a collective lawsuit against Steam—let’s connect and make it happen.**\n02 / Réseau de développement « Steam »\nInfrastructures publiques.Enregistré à grande échelle.\nTélécharger tous les albums d'252 ↓\n\nLes éléments fournis output_steam_network Les instantanés répertorient les dépôts, les relations publiques entre contributeurs et les fourches, ainsi que les recoupements de profils. Il s'agit d'enregistrements publics : ce qui a été développé, qui y a contribué, ce qui a fait l'objet d'une fourche. C'est cette trace écrite des capacités publiques dont doit rendre compte l'Valve.\n\nRéférentiel / description\tContributeurs\tForkers\tProfils enregistrés\nalliedmodders/amxmodx\n\nAMX Mod X - Half-Life 1 Scripting and Administration\n\n\t40\t40\t80\nalliedmodders/sourcemod\n\nSourceMod - Source Engine Scripting and Administration\n\n\t40\t40\t80\nDoctorMcKay/node-steam-user\n\nAllows interaction with the Steam network via the Steam client protocol\n\n\t40\t40\t80\nFacepunch/Facepunch.Steamworks\n\nAnother fucking c# Steamworks implementation\n\n\t40\t40\t80\nJustArchiNET/ArchiSteamFarm\n\nC# application with primary purpose of farming Steam cards from multiple accounts simultaneously.\n\n\t40\t40\t80\nodota/core\n\nOpenDota: Open source Dota 2 data platform with automated replay parsing\n\n\t40\t40\t80\nodota/dotaconstants\n\ndotaconstants: Static data for Dota applications\n\n\t40\t40\t80\nodota/web\n\nOpenDota: React web UI for Dota 2 statistics using the OpenDota platform\n\n\t40\t40\t80\nsplewis/get5\n\nCS:GO Sourcemod plugin for competitive matches/scrims\n\n\t40\t40\t80\nSteamDatabase/FileDetectionRuleSets\n\n🔎 Rules to detect game engines and other technologies based on Steam depot file lists\n\n\t40\t40\t80\nSteamRE/SteamKit\n\nSteamKit2 is a .NET library designed to interoperate with Valve's Steam network. It aims to provide a simple, yet extensible, interface to perform various actions on the network.\n\n\t40\t40\t80\nValveSoftware/dxvk\n\ndxvk tree containing branches used by Proton\n\n\t40\t40\t80\nValveSoftware/GameNetworkingSockets\n\nReliable & unreliable messages over UDP. Robust message fragmentation & reassembly. P2P networking / NAT traversal. Encryption.\n\n\t40\t40\t80\nValveSoftware/gamescope\n\nSteamOS session compositing window manager\n\n\t40\t40\t80\nValveSoftware/Proton\n\nCompatibility tool for Steam Play based on Wine and additional components\n\n\t40\t40\t80\nValveSoftware/source-sdk-2013\n\nThe 2013 edition of the Source SDK\n\n\t40\t40\t80\nValveSoftware/wine\n\nWine with a bit of extra spice\n\n\t40\t40\t80\nValveSoftware/steam-devices\n\nList of devices Steam and SteamVR will want read/write permissions on, to help downstream distributions create udev rules/etc\n\n\t39\t40\t79\nValveSoftware/steam-audio\n\nSteam Audio\n\n\t38\t40\t78\nalliedmodders/metamod-source\n\nMetamod:Source - C++ Plugin Environment and Detour Library for the Source Engine\n\n\t37\t40\t77\nalliedmodders/sourcepawn\n\nA small, statically typed scripting language.\n\n\t35\t40\t75\nValveSoftware/Fossilize\n\nA serialization format for various persistent Vulkan object types.\n\n\t31\t40\t71\nrlabrecque/Steamworks.NET\n\nSteamworks wrapper for Unity / C#\n\n\t27\t40\t67\nModDota/moddota.github.io\n\nModDota github pages project.\n\n\t26\t40\t66\nodota/parser\n\nReplay parse server generating JSON log events from Dota 2 replay files\n\n\t26\t40\t66\nValveSoftware/steam-for-linux\n\nIssue tracking for the Steam for Linux beta client\n\n\t26\t40\t66\nSteamRE/DepotDownloader\n\nSteam depot downloader utilizing the SteamKit2 library.\n\n\t24\t40\t64\nJustArchiNET/ASF-ui\n\nThe official web interface for ASF\n\n\t23\t40\t63\nadvancedfx/advancedfx\n\nHalf-Life Advanced Effects (HLAE) is a tool to enrich content creation mainly for the Counter-Strike series.\n\n\t22\t40\t62\nalliedmodders/ambuild\n\nAlliedModders C++ Build System\n\n\t23\t39\t62\nSteamDatabase/BrowserExtension\n\n💻 SteamDB's extension for Steam websites\n\n\t21\t40\t61\nodota/mobile\n\nReact Native apps for viewing Dota 2 data on Android/iOS\n\n\t19\t40\t59\nValvePython/steam\n\n☁️ Python package for interacting with Steam\n\n\t18\t40\t58\nskadistats/clarity\n\nComically fast Dota 2, CSGO, CS2 and Deadlock replay parser written in Java.\n\n\t13\t40\t53\nSteamRE/open-steamworks\n\nOpen Steamworks is a set of reverse engineered headers for the Valve's Steam Client. More or less abandoned now that the Steamworks SDK is publically available.\n\n\t13\t40\t53\nValveSoftware/Source-1-Games\n\nSource 1 based games such as TF2 and Counter-Strike: Source\n\n\t13\t40\t53\nalliedmodders/hl2sdk\n\nHalf-Life 2 SDK Mirrors\n\n\t11\t40\t51\nSteamDatabase/steamdb.info-issues\n\n🚱 Issue tracker for the SteamDB website\n\n\t11\t40\t51\nCSGOFloat/inspect\n\nSource Code that Powers the CSFloat Inspect Link API\n\n\t10\t40\t50\nValveSoftware/SteamOS\n\nSteamOS community tracker\n\n\t10\t40\t50\nalliedmodders/source2mod\n\nExperimental\n\n\t40\t9\t49\nsmiley/steamapi\n\nAn unofficial object-oriented Python library for accessing the Steam Web API.\n\n\t9\t40\t49\nSteamDatabase/GameTracking\n\n🛢 Dumping things, so you don't have to\n\n\t8\t40\t48\nValveSoftware/counter-strike_rules_and_regs\n\nCS:GO\n\n\t7\t40\t47\nValveSoftware/openvr\n\nOpenVR SDK\n\n\t6\t40\t46\nSteamDatabase/easy-markdown-editor\n\nEasyMDE: A simple, beautiful, and embeddable JavaScript Markdown editor. Delightful editing for beginners and experts alike. Features built-in autosaving and spell checking.\n\n\t40\t4\t44\nValveSoftware/Dota-2\n\nTracker for issues specific to Linux and Mac in the Reborn client. If you have a general issue or non-system-specific feature request please go to dev.dota2.com\n\n\t6\t38\t44\nValveSoftware/Dota2-Gameplay\n\nPublic Bug Tracker for Dota 2\n\n\t4\t40\t44\nJustArchiNET/ArchiBot\n\nNo description in the capture.\n\n\t16\t27\t43\nztizzlegaming/CSGOWinBig\n\nOpen-source Counter-Strike: Global Offensive jackpot betting website.\n\n\t1\t40\t41\nJustArchiNET/mantis.justarchi.net\n\nMantis Bug Tracker (MantisBT)\n\n\t40\t0\t40\nodota/node-steam-user\n\nAllows interaction with the Steam network via the Steam client protocol\n\n\t40\t0\t40\nModDota/TypeScriptAddonTemplate\n\nDota 2 addon template with TypeScript Panorama and VScripts.\n\n\t9\t29\t38\nValvePython/vdf\n\n📜 Package for working with Valve's text and binary KeyValue format\n\n\t6\t32\t38\nalliedmodders/amtl\n\nAlliedModders C++ Template Library\n\n\t17\t19\t36\nValvePython/dota2\n\n🐸 Python package for interacting with Dota 2 Game Coordinator\n\n\t5\t30\t35\nalliedmodders/stripper-source\n\nStripper:Source\n\n\t13\t21\t34\nAllyans3/steam-market-api-v2\n\nSteam Market API v2 package\n\n\t3\t31\t34\nModDota/dota-tutorial\n\nCustom game DOTA tutorial.\n\n\t11\t23\t34\nodota/blog\n\nNo description in the capture.\n\n\t29\t3\t32\nOpsecGuy/BetterGo\n\nExternal CS:GO cheat written in python.\n\n\t1\t27\t28\npxvr-official/1\n\n無許諾配信 企業理念剽窃 動物の森収益化 大神ミオ権利者削除 戌神権利侵害発言 常闇トワ炎上 夜空メルストーカー被害 建築王サポーター放置 赤十字マーク 魔乃アロエ卒業 一つの中國支持声明 大空昴3Dライブ 無限延期清掃員職業差別 日清コラボ楽曲 musedash非公開 rog案件取り消し 壁画ライブ 丁真 Ding Zhen 郑爽 Zheng Shuang 防护林 与朵小天使w 伊月猫凛 本主萌埋午休傻 汪峰 重生细胞 壁纸 比利海灵顿 香蕉君 van 田所浩二 抽象带篮子 抗压背锅吧 季子越 蒋明辉 傻逼…\n\n\t0\t28\t28\nRevadike/InternalSteamWebAPI\n\nDocumenting the unofficial and internal Steam Web API\n\n\t1\t27\t28\nJoeSzymkowiczFiveM/qb-lootcrate\n\nA CSGO-style case opening script\n\n\t2\t25\t27\nAbrarKL/MyRoulette.XYZ\n\nCSGO / Steam Roulette Site created with PHP and Node JS, using the Material Design front-end framework.\n\n\t1\t25\t26\nJustArchiNET/ASF-WebConfigGenerator\n\nNo description in the capture.\n\n\t10\t15\t25\nModDota/dota-data\n\nAuto-generated Dota 2 resource dumps\n\n\t11\t14\t25\nModDota/TypeScriptDeclarations\n\nTypeScript declarations for Dota 2.\n\n\t11\t14\t25\nModDota/API\n\nNo description in the capture.\n\n\t12\t12\t24\nalliedmodders/cssdm\n\nCounter-Strike:Source Deathmatch\n\n\t10\t13\t23\nSteamDatabase/steamstat.us\n\n✅ Front-end of Steam services status website\n\n\t4\t18\t22\nc0deina/csgojackpotV2\n\nCSGO Jackpot Source\n\n\t1\t20\t21\nValvePython/steamctl\n\n🤸 Take control of Steam from your terminal\n\n\t2\t19\t21\nValvePython/csgo\n\n🔫 Python package for interacting with CS:GO Game Coordinator\n\n\t3\t17\t20\nBeepIsla/csgo-crash-exploit\n\nAllows you to crash any Windows user\n\n\t3\t16\t19\nValvePython/vpk\n\n📦 Open, Search, Extract and Create VPKs in python\n\n\t4\t15\t19\nalliedmodders/SM-SteamWorks\n\nExposing SteamWorks functions to SourcePawn.\n\n\t14\t3\t17\nSteamRE/Steam4NET\n\nSteam4NET is a .NET wrapper around the Steamworks C++ interfaces\n\n\t2\t15\t17\nalliedmodders/hl2sdk-manifests\n\nInformation about HL2SDKs shared between Metamod:Source and SourceMod.\n\n\t6\t10\t16\nJustArchiNET/ASF-PluginTemplate\n\nTemplate repository that you can use for creating custom plugins for ArchiSteamFarm.\n\n\t8\t7\t15\nModDota/Dota2AIFramework\n\nGeneral Framework for Dota 2 AI Competitions\n\n\t1\t14\t15\nShkyyl/KeyChamp\n\nExtension for joining free case battle on key-drop automatically\n\n\t1\t14\t15\nSteamDatabase/SteamMonitor\n\n😤 Track Steam's connection manager servers status\n\n\t2\t12\t14\nBaterka/cslore.com\n\nCS:GO gambling site - csgo.style\n\n\t1\t12\t13\nSteamDatabase/SteamTokenDumper\n\n🔢 Submit users' PICS access tokens to SteamDB\n\n\t2\t11\t13\nmonoblocker/roulette\n\nRoulette CS:GO made in React and Typescript\n\n\t1\t11\t12\nzsith/launcher.user.js\n\n// ==UserScript== // @name AposLauncher // @namespace AposLauncher // @include http://agar.io/* // @version 3.062 // @grant none // @author http://www.twitch.tv/apostolique // ==/UserScript== var aposLauncherVersion = 3.062; Nu…\n\n\t1\t11\t12\nLincolnIT/CSGODouble-bot-automated\n\nCSGODouble Automated, auto Betting Bot.\n\n\t1\t10\t11\nvladpuz/steam-market\n\nSteam market API client\n\n\t4\t7\t11\nmcgrizzz/Cstrike.bet\n\nCSGO Roulette Website Angular frontend, nodejs backend, and steam trading bots\n\n\t1\t9\t10\nodota/underlords-web\n\nUI for OpenUnderlords\n\n\t5\t5\t10\nSteamDatabase/SteamToTwitter\n\n🕊 Tweets announcements from various Steam groups\n\n\t1\t9\t10\nModDota/AbilityLuaSpellLibrary\n\nThe successor to the Spell Library by Pizzalol\n\n\t4\t4\t8\nalvinl/bitskins\n\nUnofficial BitSkins API client\n\n\t2\t5\t7\nb1naryth1ef/steamy\n\nA Python Steam community and market API interface that will get you all hot and bothered\n\n\t2\t5\t7\nkratos1812/Case-Opening\n\nIn-game case opening system for CSGO servers.\n\n\t2\t5\t7\nodota/docs\n\nOpenDota API documentation\n\n\t4\t3\t7\nSteamDatabase/steam-advanced-access-fetch-players\n\n📈 Simple script to fetch Steam player count\n\n\t1\t6\t7\nTheRioMiner/CsgoBetterExternalRaytrace\n\nOverridden maps pack for better external raytrace\n\n\t1\t6\t7\nalliedmodders/hl2sdk-mock\n\nMock HL2SDK and Server\n\n\t5\t1\t6\nchristophersu/PySteamMarket\n\nPython API for getting prices from the Steam market.\n\n\t1\t5\t6\nExtremelyd1/Strat-Roulette\n\nCS:GO Sourcemod Plugin\n\n\t2\t4\t6\ngiovanni-orciuolo/double-sdk\n\nA simple way to write CS:GO cheats!\n\n\t2\t4\t6\nJustArchiNET/Madness\n\nMadness embraces your project by including compatibility layer for selected APIs normally not available on .NET Framework target.\n\n\t5\t1\t6\nModDota/TypescriptPanoramaDeclarations\n\nNo description in the capture.\n\n\t4\t2\t6\nodota/rapier\n\nA JavaScript Dota 2 (Source 2) replay parsing library\n\n\t1\t5\t6\nVozn1akHero/CSGOCaseOpeningSimulator\n\nCounter-Strike case opening simulator which resembles the good old CS:GO user interface\n\n\t3\t3\t6\nautarc/steam-store\n\nAPI client for the unofficial steam storefront/big picture resource\n\n\t2\t3\t5\nBETTING-CODE/awesome-esports-sites\n\nA curated list of awesome esport betting sites – live, statistics and other resources.\n\n\t1\t4\t5\njonteohr/Better-Warden\n\nAn improved and more advanced warden plugin with a custom menu for CS:GO jailbreak servers!\n\n\t2\t3\t5\nLudzikk/CSGO-Gambling-Site\n\nhttps://ludzikk.github.io/CSGO-Gambling-Site/\n\n\t1\t4\t5\nModDota/find-steam-app\n\nFind location of an installed Steam app\n\n\t3\t2\t5\nmprey/csgocact.us\n\nsource code for csgocact.us\n\n\t1\t4\t5\nnezu-cc/ServerCrasher\n\nCS:GO Server Crasher\n\n\t1\t4\t5\nodota/testfiles\n\nStores test replay files\n\n\t2\t3\t5\nodota/underlordsconstants\n\nConstant data for Dota Underlords\n\n\t3\t2\t5\nSnaBe/node-steam-market-fetcher\n\nA Node.js wrapper for the Steam Community Market API.\n\n\t2\t3\t5\nSteamDatabase/.github\n\n💗 Organization-wide community health files\n\n\t1\t4\t5\nwolfcon/RIP-HLTV-BET\n\nRIP BET AD (For Tampermonkey) https://greasyfork.org/en/scripts/423484-rip-hltv-bet\n\n\t2\t3\t5\nalliedmodders/blaster.net\n\nSource and GoldSrc Query Tool\n\n\t2\t2\t4\ncatears124/CS2-Price-API\n\nsimple python cs2 steam market price API\n\n\t1\t3\t4\nialakey/caseforge\n\nOpen-source CS2 case-opening platform: Steam auth, provably fair openings, RTP-balanced case builder, withdrawals bought on market.csgo.com and an admin CRM.\n\n\t1\t3\t4\nIlusion9/csgo-fix-mapchange-crash-sm\n\nFix players crash on map change.\n\n\t1\t3\t4\nismail0234/Benson-Map-Crash-Fixer\n\nCSGO Map Change Client Crash Fixer\n\n\t1\t3\t4\njaxwilko/steam-market-api\n\nPHP - Composer Compatible - Steam Market API\n\n\t2\t2\t4\nJustArchiNET/ArchiTag\n\nArchiTag is a very small utility based on Python 3 and Mutagen to provide missing functionality in opusenc of writing specific Opus metadata, such as total number of tracks or track number.\n\n\t1\t3\t4\nModDota/DotaUI\n\nNo description in the capture.\n\n\t2\t2\t4\nnode-steam/market-pricing\n\nWrapper for the unofficial Steam Market Pricing API\n\n\t1\t3\t4\nodota/media\n\nStores media files for Dota projects\n\n\t2\t2\t4\nSergeyIvanovDevelop/Crypto-Steam-Platform\n\nThe repository contains the code and configuration to run a platform for creating cryptocurrency stakes for arbitrary ERC20 tokens.\n\n\t1\t3\t4\nAareksio/csgodouble-floatchecker\n\nAdds context menu option to check item's float value\n\n\t1\t2\t3\nchinm4/CSGOdrop\n\nA online csgo gambling casino that includes a variety of mini games that allows you to win csgo skins\n\n\t2\t1\t3\nCruze03/CSGO-Case-Opening-Prank\n\nCommand:- !prank (Admin flag \"n\" required)\n\n\t1\t2\t3\nDhruva-Kapadia/CSGOTrollGG\n\nCSGO Case Opening Simulator\n\n\t2\t1\t3\nErhanCSGO/CSGOPolygon-prediction\n\nCSGOPolygon.com - prediction script, double your coins by using this tool\n\n\t1\t2\t3\nEv-Hoang/Bedrock-Chest-Case-Opening\n\nHypixel Skyblock Dungeon Mod - Bedrock Chest Opening Animation (CSGO Style)\n\n\t1\t2\t3\njmjp/csgo-roulette\n\nA csgo gambling roulette make with VueJS 3\n\n\t2\t1\t3\nJustArchiNET/ArchiCrowdin\n\nNo description in the capture.\n\n\t1\t2\t3\nLeonSK/WearMarketInspector\n\nRetrieve Wear Value (Float Value) and Pattern Index from Steam Community Market using http://csgo.exchange API\n\n\t1\t2\t3\nmaximgeerinck/csgo-gamble\n\nCSGO gambling website\n\n\t1\t2\t3\nModDota/BugTracker\n\nListing bugs for Dota 2 Custom Games\n\n\t2\t1\t3\nplwp/mma-betting\n\nUFC/MMA betting model with Pinnacle steam detection for AU book latency arb\n\n\t2\t1\t3\nSouthsideswag16/Csgo-Gambling-Site\n\nNo description in the capture.\n\n\t2\t1\t3\ntacyarg/csgofiesta-frontend-react\n\nRemastered version a the long time favorite csgo site\n\n\t2\t1\t3\nVelorasse/Mutah-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-csmoney-csgoskins\n\ngambling script for Mutah, Keydrop, csmoney, and csgoskins, featuring hacks, cheats, and predictors. Offers strategies to boost winning odds and optimize performance on these platforms.\n\n\t3\t0\t3\nalliedmodders/am-github-artifact-webhook\n\nNo description in the capture.\n\n\t2\t0\t2\ncharamza/roulette\n\nCSGO like roulette in JS\n\n\t1\t1\t2\nCruze03/CSGO-PugSetup-RoundRestore\n\nSometimes (player dropped/crashed) which would be disadvantage for a team. It would be very handy to restore the match to the previous round.\n\n\t1\t1\t2\ncsgorol/CSGO-ROLL-Crash-Predictor\n\nCSGO-ROLL-Crash-Predictor\n\n\t1\t1\t2\nFoxSerito/FOXWORLD_plugin_DoubleJump_CSGO\n\nПлагин SourceMod (CSGO). Двойной прыжок с эффектом.\n\n\t1\t1\t2\nhkehayovmoonbiz/CS2-Casino-Full-Source-Code\n\nCS2, CS2 betting platforms, Skin Roulette, Case Unboxing, Crash games, Jackpot, purchase CS2 casino source, crypto gambling\n\n\t1\t1\t2\nJustZakary/steamstoreapi\n\nThis NPM module is a API wrapper that makes the steam unofficial API easier to use.\n\n\t2\t0\t2\njzimr/steam-market-api\n\nA java library to easily get Steam Community Market data\n\n\t1\t1\t2\nMomohime/CSGO.Network-Jackpot-Coinflip\n\nNo description in the capture.\n\n\t1\t1\t2\nnnjjswat/moneybot\n\nautomated bots for bustabit (formerly known as moneypot), csgo crash, etc\n\n\t0\t2\t2\nodota/carry\n\nLegacy Application for donations to the OpenDota project\n\n\t1\t1\t2\nodota/PublicMatchDataBot\n\nA Discord bot to remind users to turn on Expose Public Match Data in the Dota 2 client\n\n\t1\t1\t2\nOrillio/CSGOBet.com\n\nCSGO roulette web app\n\n\t2\t0\t2\nripexz/csgo-bet-alert\n\nA Chrome extension to keep track of active CS:GO Lounge matches.\n\n\t1\t1\t2\nrrpvm/lumen_sense-beta-deprecated-\n\nthis is internal csgo cheat written by me(no paste, self reverse structures). start : ~6 August 2020, end : ~ 14 December 2020\n\n\t1\t1\t2\nRuthless222/csgoscore\n\nThis is a Counter Strike Global Offensive Betting Site. You chose the skins you want to bet and try to win jackpots\n\n\t2\t0\t2\ntfburns/CSGO-cases-PL\n\nExpected profit-loss of CS:GO case openings\n\n\t1\t1\t2\nTomDra/CSGO-Case-Data-Analysis\n\nWorks out the most profitable CS:GO case at that current time\n\n\t1\t1\t2\nValvePython/dota2-wrappers\n\nNo description in the capture.\n\n\t1\t1\t2\nValvePython/teamfortress2-closed-captions\n\nThis project aims to provide a set of closed captions for Team Fortress 2\n\n\t1\t1\t2\nVistaNetGTX/Cstrike.bet-\n\nCSGO Roulette Website Angular frontend, nodejs backend, and steam trading bots\n\n\t1\t1\t2\nwafflas/csgo-case-opening-simulator\n\nI created a cs go case opening simulator for a meme coin\n\n\t0\t2\t2\nAdmiral-Enigma/Le_Coinflip\n\nConflip game\n\n\t1\t0\t1\nadryeljuliao/roulette-csgo\n\nNo description in the capture.\n\n\t1\t0\t1\nAndreuTheG/csgo-coinflip-web\n\nCSGO Gambling Coinflip Website\n\n\t1\t0\t1\nasmilen/csgoDouble\n\na b c\n\n\t1\t0\t1\nb1naryth1ef/csgofort\n\nA CSGO portal for trading, betting, analytics, and more!\n\n\t1\t0\t1\nBaterka/PrivateSteamBettingWebsite2024\n\nPrivate Steam (Counter-Strike 2) betting/gambling website - Roulette, Jackpot\n\n\t1\t0\t1\nblackcaer/SteamTradeHandler\n\nAutomation of Steam trading. Helper project for bet automation.\n\n\t1\t0\t1\nBTheCoderr/theRounders\n\nThe Rounders - A professional-grade sports betting analytics platform combining real-time odds tracking, sharp movement detection, and advanced statistical analysis. Features include line shopping, steam move alerts, power rankings, and comprehensive bet t…\n\n\t1\t0\t1\nCallumHemsley/KazeBot\n\nA Twitch chat betting bot for CSGO, simply bet a certain amount of points, and double if you win, lose all if you lose. Simple.\n\n\t1\t0\t1\nchrisjpm/CSGOJackpotTemplate\n\nFront end for a jackpot site\n\n\t1\t0\t1\ncolinsenner/valve-bug-bounty\n\nFor many years CS:GO, Dota 2, and Team Fortress 2 servers had a bug that allowed malicious users to leak crucial server process memory or reliably crash any server.\n\n\t1\t0\t1\ncoryypeters/nrl-odds-intelligence-pipeline\n\nReal-time sports betting odds intelligence — streaming pipeline that detects line movement, steam, and arbitrage across bookmakers. Python · Redis Streams · FastAPI · React.\n\n\t1\t0\t1\ndeissh/dev-csgoduo\n\nCS:GO. Bot for receiving things on the site (Polygon, Duo, Double and etc).\n\n\t1\t0\t1\ndom1torii/even-better-font-manager\n\nSimply even better cross-platform tool for CS2 Font Management\n\n\t1\t0\t1\nDONnicov/CSGO-crash-black-screen-\n\nsolution csgo crash black screen and close csgo\n\n\t1\t0\t1\nDoubleBoters/CsgoDouble\n\nNo description in the capture.\n\n\t1\t0\t1\ndownarowiczd/DoubleBot\n\nAn old CSGO Double Bot written for my friend. - 07.05.2016\n\n\t1\t0\t1\nErayBahar/steammarketscraper\n\nSteam Market Scraper Python-based tool that tracks real-time CS2 skin prices using Steam's hidden API. It fetches the lowest sell and highest buy offers for any item, helping you monitor deals or snipe underpriced listings automatically.\n\n\t1\t0\t1\nfairydarkness/SteamwebmailAPI\n\nUnofficial Python API for steamwebmail.com Fast, lightweight, and browserless library for automating steamwebmail.com. Support for session management, proxy, folder navigation, and message retrieval\n\n\t1\t0\t1\nFAQU2/CSGO-Coinflip-MyJailShop\n\nSourcemod plugin which provides a Coinflip system for MyJailShop.\n\n\t1\t0\t1\nFlamesONE/csgo-case-opening\n\nNo description in the capture.\n\n\t1\t0\t1\nFunnyRain/csgorun-crash-watch\n\n🚀 CsgoRun dump crash. / 🚀 CsgoRun дамп крашей.\n\n\t1\t0\t1\ngeohdgio/Venatus-Autenticator\n\nეს არის Steam Autenticator ქართული Venatus Trade & Betting ისთვის და Valve News Georgia-სთვის.\n\n\t1\t0\t1\nhakanstarlord/steam-bot\n\nSports betting steam-move signal detection with ML pipeline (XGBoost stacking + isotonic calibration), backtesting engine, Flask dashboard, and Telegram alerts.\n\n\t1\t0\t1\nHvH-gg/CSGO-Item-CrashFix\n\nA plugin for Counter-Strike: Global Offensive that fixes an exploit where receiving CS2 Items will cause CS:GO clients to crash\n\n\t1\t0\t1\nHvH-gg/CSGO-NetMsg-CrashFix\n\nA plugin for Counter-Strike: Global Offensive that fixes an exploit where spamming NetMsg_StringCmd packets would result in a server crash.\n\n\t1\t0\t1\nisybycnsmam/SteamLibrary\n\nLegacy Steam Unofficial API\n\n\t1\t0\t1\nItsTangerine/SteamApis.Net\n\nUnofficial https://steamapis.com .NET library, supporting .NET 6.0+\n\n\t1\t0\t1\nJustArchiNET/JustArchi.net\n\nNo description in the capture.\n\n\t1\t0\t1\nkiri-osint/CS2-Info-Hub-Bot\n\nA Telegram bot that acts as a hub for CS2 players, providing real-time skin prices, server stats, and user profile/inventory inspection using official and unofficial Steam APIs.\n\n\t1\t0\t1\nKoshkaj/monte\n\nGamified csgo gambling platform implementation\n\n\t1\t0\t1\nmadsab/CaseOpening\n\nA school project using Java. Simulating the case opening from CSGO and more.\n\n\t1\t0\t1\nman90es/steamcardexchange-api\n\nSteamCardExchange.net unofficial REST API server (scraper).\n\n\t1\t0\t1\nMattPua/steam-unofficial-docs\n\nUnofficial docs for Steam APIs with fumadocs\n\n\t1\t0\t1\nMetallist1/Portfolio.CsgoWinGambleProject\n\nA website that was done in 2017 September. Websites focus was on gambling with Counter-Strike items. Project was largely completed however backups were not done correctly, this resulted in half a year of wasted improvements to the code. The website was test…\n\n\t1\t0\t1\nmikebobadilla/csgo-jackpot\n\nNo description in the capture.\n\n\t0\t1\t1\nmikebobadilla/meteor-csgojackpot\n\nCssgo Jackpot done in meteor\n\n\t1\t0\t1\nModDota/D2VDump\n\nDota 2 Server VScript API Dumper\n\n\t1\t0\t1\nModDota/DotaTracking\n\nNo description in the capture.\n\n\t1\t0\t1\nModDota/eslint-config\n\nESLint config by ark120202\n\n\t1\t0\t1\nmr-codinglv/Casino-script\n\nscript casino - script betting - exchange script - bc casino - casino csgo - script bet - betwin script\n\n\t1\t0\t1\nMrKeelik/MrKeel\n\nCSGO DOUBLE BOT\n\n\t1\t0\t1\nnoahlatzel/CSGORollHelper\n\nLeveraging positive expected value on triple green jackpots on CSGORoll!\n\n\t1\t0\t1\noddsgpt/oddsgpt-market-intelligence\n\nResearch on football betting markets, closing odds, CLV, market efficiency, steam moves, AI betting systems, and sports market intelligence.\n\n\t1\t0\t1\noEXU/csgo-server-crasher\n\nCSGO SERVER CRASHER\n\n\t1\t0\t1\nPrdTTony/CSGO-Roulette\n\n[CSGO] Roulette System. Bet on RED or Black and win x2 credits\n\n\t1\t0\t1\nr-adamski/csgo-jackpot\n\nNo description in the capture.\n\n\t1\t0\t1\nSahotallo/Turan-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-Skinbaron-hellcase\n\ngambling script for Turan, Keydrop, Skinbaron, and Hellcase, providing hacks, cheats, and predictors. Includes strategies to improve winning chances and enhance gameplay on these platforms.\n\n\t1\t0\t1\nsamuelcsouza/steam-marketplace-api\n\nAn unofficial API to get data from the Steam Marketplace.\n\n\t1\t0\t1\nSKINSTRACK/CS2-Price-API\n\nSkinstrack offers a free, limited API endpoint that returns Steam item prices. Paid plans additionally provide access to pricing data from multiple marketplaces, making it possible to compare prices across different markets through a single API.\n\n\t1\t0\t1\nsnmtriet/CSGO-Casino-Full-Source-Code\n\nCSGO, CSGOEmpire, Case Opening, Case Battles, Roulette, Coinflip, buy csgo gambling site, gambling\n\n\t1\t0\t1\nSteamRE/homebrew-tools\n\nRepository for installation of SteamRE tools via Homebrew (http://brew.sh)\n\n\t1\t0\t1\nSteamRE/opensteamworks.org\n\nNo description in the capture.\n\n\t1\t0\t1\nTheQuack45/CsgoCaseOpenProgram\n\nSimple program to parse an XML file with CS:GO case information and \"simulate\" case openings\n\n\t1\t0\t1\nTLClassless/StratRouletteCSGO\n\nA 'Strat Roulette' web app for CS:GO!\n\n\t1\t0\t1\ntomasoom/csgoCaseOpening\n\nNo description in the capture.\n\n\t1\t0\t1\nvitaliy-evsyukov/steamgifts-autobet-bookmarklet\n\nbookmarklet for automatic bets on steamgifts.com\n\n\t1\t0\t1\nXpravdaX/RouletteCSGO\n\nNo description in the capture.\n\n\t1\t0\t1\nYuiKasumii/steam_api_unofficial\n\nUnofficial Steam Game Information Database\n\n\t1\t0\t1\nZexuz/Steam-Betting\n\nA betting website build ontop of STEAM's ecosystem\n\n\t1\t0\t1\nANK-RULZZ/steam-jackpot-site\n\ngetting some errors and would like some one to help me with it thank you!!!\n\n\t0\t0\t0\nasmilen/CsgoDoubleVS\n\nNo description in the capture.\n\n\t0\t0\t0\nCORNOODOSADAS/CSGOWeed\n\nCsgo Jackpot and Coinflip\n\n\t0\t0\t0\nCSGOApple/csgoapple\n\nJackpot Site\n\n\t0\t0\t0\nCSGOFAST/csgofast-api\n\nNo description in the capture.\n\n\t0\t0\t0\nDonakall/csgoDoublebot\n\nAutomated bot for csgodouble\n\n\t0\t0\t0\nfedor-selivanov/csgo-fast-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nfoldageros/csgod\n\ndouble bot\n\n\t0\t0\t0\ngmod-gambling/gmod-gambling\n\nNo description in the capture.\n\n\t0\t0\t0\nierome/CSGOBoss-BackEnd\n\nBack end version of CSGOBoss. This was a CSGO Gambling site named CSGOBoss. Coded by an old friend of mine Dahquan Hinds (https://github.com/dahquan/) Thought I would release this to help out any one who would need it.\n\n\t0\t0\t0\njamienp1/CSGODOUBLE-BOT-AUTO\n\ni got a bot thats is betting on the last winning color except from green and if you lose it will double the coins you set it to bet, pretty good, so when there comes a loooong train you will be gaining a bit of money codepaste_net/ugmt92 remove all the _ an…\n\n\t0\t0\t0\nJEYONER/CSGOTOXIC\n\nPAGINA DE JACKPOT CSGO SKINS\n\n\t0\t0\t0\nkalrish/csgo-jackpot\n\nStressful but funny zombie-like Counter-Strike: Global Offensive game mode.\n\n\t0\t0\t0\nkrys12345/roulettee\n\n// ==UserScript== // @name CSGO Predict Bot // @namespace http://csgodouble.com // @version 1.0 // @description predicts what number its gonna be // @author Meee // @match http://www.csgodouble.com/ // @grant none // ==/…\n\n\t0\t0\t0\nLilDuggiMuffi/CSGODouble-Working-Bot\n\nFixed CSGO Double Bot\n\n\t0\t0\t0\nLyricLy/Steam2Proton\n\nCheck if all your Steam games will work with Proton! Uses the official Steam API and the unofficial Proton API.\n\n\t0\t0\t0\nM0NsTeR77/csgo-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nozanhalis/Hi\n\n// ==UserScript== // @name CS GO LOUNGE BOT-Ozan Halis // @namespace http://csgolounge.com/ // @version 0.6.6 // @description Cs Go Lounge Hızlı BOT // @match http://csgolounge.com/* // @match http://dota2lounge.com/* // @updateURL h…\n\n\t0\t0\t0\nscoobertus/CSGO-DoubleBot\n\nNo description in the capture.\n\n\t0\t0\t0\nTradeal/CSGO-Jackpot-Bot\n\nNo description in the capture.\n\n\t0\t0\t0\nValvePython/artifact\n\nNo description in the capture.\n\n\t0\t0\t0\nVampire/CSGO-Roulette-Bot\n\nNo description in the capture.\n\n\t0\t0\t0\nvdemans/csgo-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nVocoreVideo/CSGODungeon-\n\nCSGO Jackpot\n\n\t0\t0\t0\nwayz-dev/csgofloat\n\nNo description in the capture.\n\n\t0\t0\t0\n\nAperçu : 17 septembre 2026, 11:19:11 tel qu’indiqué dans la source ; fuseau horaire non précisé. La collection des relations est limitée dans l’exportation (de nombreuses catégories s’arrêtent à 40). Les contributeurs et les développeurs dérivés totalisent 4,554 entrées de rôle réparties sur 4,214 paires profil-dépôt distinctes ; un profil peut occuper les deux rôles. La valeur zéro signifie qu’aucun enregistrement n’a été recensé dans cette catégorie. Les noms de dépôts peuvent inclure des alias ou des variantes de casse ; les totaux respectent les conventions de comptage de la source.\n\nProvenance de la source\nCréé à partir des fichiers que vous avez rassemblés.\nTémoignage de soutien\n2323/reddit_scams_ultra/steam_support_tickets_MEGA.json · lignes 45, 58, 107, 110, 294\nInstantané du réseau\nnetwork-repositories.csv · raw_data.json · overlaps.csv · summary.txt (chemins d'accès historiques conservés dans le manifeste)\n\nLe manifeste répertorie les chemins d'accès aux enregistrements, leur taille en octets, leurs hachages SHA-256s et les positions des enregistrements sélectionnés. Les captures brutes restent distinctes de l'interprétation issue de l'enquête.\n\nTélécharger le manifeste source ↓",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam Preuves relatives à l'application de la réglementation — Documents justificatifs et réseau des promoteurs immobiliers"
          },
          {
            "level": 2,
            "id": null,
            "text": "Lisez la plainte.Veuillez joindre le fichier source."
          },
          {
            "level": 3,
            "id": null,
            "text": "Permanent sanction & closed appeals"
          },
          {
            "level": 4,
            "id": null,
            "text": "Permanently banned Steam account without a clear explanation, need help!"
          },
          {
            "level": 3,
            "id": null,
            "text": "Account recovery & a reported $10,000 loss"
          },
          {
            "level": 4,
            "id": null,
            "text": "Got $10k stollen from steam inventory due to steam' support fault."
          },
          {
            "level": 3,
            "id": null,
            "text": "A reported $500+ loss & template replies"
          },
          {
            "level": 4,
            "id": null,
            "text": "Funds stolen through steam market. Disappointed with Steam response.(or lackthereof)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam Guard & an item-restoration refusal"
          },
          {
            "level": 4,
            "id": null,
            "text": "Many people are losing item via clicking links where steam guard is enabled and steam support doesn't not restore items."
          },
          {
            "level": 3,
            "id": null,
            "text": "Selective enforcement & an unexplained ban"
          },
          {
            "level": 4,
            "id": null,
            "text": "🚨 Steam Bans Without Reason and Ignores Its Community — What’s Going On?"
          },
          {
            "level": 2,
            "id": null,
            "text": "Infrastructures publiques.Enregistré à grande échelle."
          },
          {
            "level": 2,
            "id": null,
            "text": "Créé à partir des fichiers que vous avez rassemblés."
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/fr/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/fr/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/selected-support-records.json",
          "https://phishdestroy.io/steam_dossier/fr/investigation_part2.html#outsourcing-case",
          "https://www.reddit.com/r/ohnePixel/comments/1hahqx2/permanently_banned_steam_account_without_a_clear/",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://www.reddit.com/r/DotA2/comments/r55bd7/many_people_are_losing_item_via_clicking_links/",
          "https://www.reddit.com/r/SteamUncensored/comments/1kjt2fa/steam_bans_without_reason_and_ignores_its/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/network-repositories.csv",
          "https://github.com/alliedmodders/amxmodx",
          "https://github.com/alliedmodders/sourcemod",
          "https://github.com/DoctorMcKay/node-steam-user",
          "https://github.com/Facepunch/Facepunch.Steamworks",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://github.com/odota/core",
          "https://github.com/odota/dotaconstants",
          "https://github.com/odota/web",
          "https://github.com/splewis/get5",
          "https://github.com/SteamDatabase/FileDetectionRuleSets",
          "https://github.com/SteamRE/SteamKit",
          "https://github.com/ValveSoftware/dxvk",
          "https://github.com/ValveSoftware/GameNetworkingSockets",
          "https://github.com/ValveSoftware/gamescope",
          "https://github.com/ValveSoftware/Proton",
          "https://github.com/ValveSoftware/source-sdk-2013",
          "https://github.com/ValveSoftware/wine",
          "https://github.com/ValveSoftware/steam-devices",
          "https://github.com/ValveSoftware/steam-audio",
          "https://github.com/alliedmodders/metamod-source",
          "https://github.com/alliedmodders/sourcepawn",
          "https://github.com/ValveSoftware/Fossilize",
          "https://github.com/rlabrecque/Steamworks.NET",
          "https://github.com/ModDota/moddota.github.io",
          "https://github.com/odota/parser",
          "https://github.com/ValveSoftware/steam-for-linux",
          "https://github.com/SteamRE/DepotDownloader",
          "https://github.com/JustArchiNET/ASF-ui",
          "https://github.com/advancedfx/advancedfx",
          "https://github.com/alliedmodders/ambuild",
          "https://github.com/SteamDatabase/BrowserExtension",
          "https://github.com/odota/mobile",
          "https://github.com/ValvePython/steam",
          "https://github.com/skadistats/clarity",
          "https://github.com/SteamRE/open-steamworks",
          "https://github.com/ValveSoftware/Source-1-Games",
          "https://github.com/alliedmodders/hl2sdk",
          "https://github.com/SteamDatabase/steamdb.info-issues",
          "https://github.com/CSGOFloat/inspect",
          "https://github.com/ValveSoftware/SteamOS",
          "https://github.com/alliedmodders/source2mod",
          "https://github.com/smiley/steamapi",
          "https://github.com/SteamDatabase/GameTracking",
          "https://github.com/ValveSoftware/counter-strike_rules_and_regs",
          "https://github.com/ValveSoftware/openvr",
          "https://github.com/SteamDatabase/easy-markdown-editor",
          "https://github.com/ValveSoftware/Dota-2",
          "https://github.com/ValveSoftware/Dota2-Gameplay",
          "https://github.com/JustArchiNET/ArchiBot",
          "https://github.com/ztizzlegaming/CSGOWinBig",
          "https://github.com/JustArchiNET/mantis.justarchi.net",
          "https://github.com/odota/node-steam-user",
          "https://github.com/ModDota/TypeScriptAddonTemplate",
          "https://github.com/ValvePython/vdf",
          "https://github.com/alliedmodders/amtl",
          "https://github.com/ValvePython/dota2",
          "https://github.com/alliedmodders/stripper-source",
          "https://github.com/Allyans3/steam-market-api-v2",
          "https://github.com/ModDota/dota-tutorial",
          "https://github.com/odota/blog",
          "https://github.com/OpsecGuy/BetterGo",
          "https://github.com/pxvr-official/1",
          "https://github.com/Revadike/InternalSteamWebAPI",
          "https://github.com/JoeSzymkowiczFiveM/qb-lootcrate",
          "https://github.com/AbrarKL/MyRoulette.XYZ",
          "https://github.com/JustArchiNET/ASF-WebConfigGenerator",
          "https://github.com/ModDota/dota-data",
          "https://github.com/ModDota/TypeScriptDeclarations",
          "https://github.com/ModDota/API",
          "https://github.com/alliedmodders/cssdm",
          "https://github.com/SteamDatabase/steamstat.us",
          "https://github.com/c0deina/csgojackpotV2",
          "https://github.com/ValvePython/steamctl",
          "https://github.com/ValvePython/csgo",
          "https://github.com/BeepIsla/csgo-crash-exploit",
          "https://github.com/ValvePython/vpk",
          "https://github.com/alliedmodders/SM-SteamWorks",
          "https://github.com/SteamRE/Steam4NET",
          "https://github.com/alliedmodders/hl2sdk-manifests",
          "https://github.com/JustArchiNET/ASF-PluginTemplate",
          "https://github.com/ModDota/Dota2AIFramework",
          "https://github.com/Shkyyl/KeyChamp",
          "https://github.com/SteamDatabase/SteamMonitor",
          "https://github.com/Baterka/cslore.com",
          "https://github.com/SteamDatabase/SteamTokenDumper",
          "https://github.com/monoblocker/roulette",
          "https://github.com/zsith/launcher.user.js",
          "https://github.com/LincolnIT/CSGODouble-bot-automated",
          "https://github.com/vladpuz/steam-market",
          "https://github.com/mcgrizzz/Cstrike.bet",
          "https://github.com/odota/underlords-web",
          "https://github.com/SteamDatabase/SteamToTwitter",
          "https://github.com/ModDota/AbilityLuaSpellLibrary",
          "https://github.com/alvinl/bitskins",
          "https://github.com/b1naryth1ef/steamy",
          "https://github.com/kratos1812/Case-Opening",
          "https://github.com/odota/docs",
          "https://github.com/SteamDatabase/steam-advanced-access-fetch-players",
          "https://github.com/TheRioMiner/CsgoBetterExternalRaytrace",
          "https://github.com/alliedmodders/hl2sdk-mock",
          "https://github.com/christophersu/PySteamMarket",
          "https://github.com/Extremelyd1/Strat-Roulette",
          "https://github.com/giovanni-orciuolo/double-sdk",
          "https://github.com/JustArchiNET/Madness",
          "https://github.com/ModDota/TypescriptPanoramaDeclarations",
          "https://github.com/odota/rapier",
          "https://github.com/Vozn1akHero/CSGOCaseOpeningSimulator",
          "https://github.com/autarc/steam-store",
          "https://github.com/BETTING-CODE/awesome-esports-sites",
          "https://github.com/jonteohr/Better-Warden",
          "https://github.com/Ludzikk/CSGO-Gambling-Site",
          "https://github.com/ModDota/find-steam-app",
          "https://github.com/mprey/csgocact.us",
          "https://github.com/nezu-cc/ServerCrasher",
          "https://github.com/odota/testfiles",
          "https://github.com/odota/underlordsconstants",
          "https://github.com/SnaBe/node-steam-market-fetcher",
          "https://github.com/SteamDatabase/.github",
          "https://github.com/wolfcon/RIP-HLTV-BET",
          "https://github.com/alliedmodders/blaster.net",
          "https://github.com/catears124/CS2-Price-API",
          "https://github.com/ialakey/caseforge",
          "https://github.com/Ilusion9/csgo-fix-mapchange-crash-sm",
          "https://github.com/ismail0234/Benson-Map-Crash-Fixer",
          "https://github.com/jaxwilko/steam-market-api",
          "https://github.com/JustArchiNET/ArchiTag",
          "https://github.com/ModDota/DotaUI",
          "https://github.com/node-steam/market-pricing",
          "https://github.com/odota/media",
          "https://github.com/SergeyIvanovDevelop/Crypto-Steam-Platform",
          "https://github.com/Aareksio/csgodouble-floatchecker",
          "https://github.com/chinm4/CSGOdrop",
          "https://github.com/Cruze03/CSGO-Case-Opening-Prank",
          "https://github.com/Dhruva-Kapadia/CSGOTrollGG",
          "https://github.com/ErhanCSGO/CSGOPolygon-prediction",
          "https://github.com/Ev-Hoang/Bedrock-Chest-Case-Opening",
          "https://github.com/jmjp/csgo-roulette",
          "https://github.com/JustArchiNET/ArchiCrowdin",
          "https://github.com/LeonSK/WearMarketInspector",
          "https://github.com/maximgeerinck/csgo-gamble",
          "https://github.com/ModDota/BugTracker",
          "https://github.com/plwp/mma-betting",
          "https://github.com/Southsideswag16/Csgo-Gambling-Site",
          "https://github.com/tacyarg/csgofiesta-frontend-react",
          "https://github.com/Velorasse/Mutah-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-csmoney-csgoskins",
          "https://github.com/alliedmodders/am-github-artifact-webhook",
          "https://github.com/charamza/roulette",
          "https://github.com/Cruze03/CSGO-PugSetup-RoundRestore",
          "https://github.com/csgorol/CSGO-ROLL-Crash-Predictor",
          "https://github.com/FoxSerito/FOXWORLD_plugin_DoubleJump_CSGO",
          "https://github.com/hkehayovmoonbiz/CS2-Casino-Full-Source-Code",
          "https://github.com/JustZakary/steamstoreapi",
          "https://github.com/jzimr/steam-market-api",
          "https://github.com/Momohime/CSGO.Network-Jackpot-Coinflip",
          "https://github.com/nnjjswat/moneybot",
          "https://github.com/odota/carry",
          "https://github.com/odota/PublicMatchDataBot",
          "https://github.com/Orillio/CSGOBet.com",
          "https://github.com/ripexz/csgo-bet-alert",
          "https://github.com/rrpvm/lumen_sense-beta-deprecated-",
          "https://github.com/Ruthless222/csgoscore",
          "https://github.com/tfburns/CSGO-cases-PL",
          "https://github.com/TomDra/CSGO-Case-Data-Analysis",
          "https://github.com/ValvePython/dota2-wrappers",
          "https://github.com/ValvePython/teamfortress2-closed-captions",
          "https://github.com/VistaNetGTX/Cstrike.bet-",
          "https://github.com/wafflas/csgo-case-opening-simulator",
          "https://github.com/Admiral-Enigma/Le_Coinflip",
          "https://github.com/adryeljuliao/roulette-csgo",
          "https://github.com/AndreuTheG/csgo-coinflip-web",
          "https://github.com/asmilen/csgoDouble",
          "https://github.com/b1naryth1ef/csgofort",
          "https://github.com/Baterka/PrivateSteamBettingWebsite2024",
          "https://github.com/blackcaer/SteamTradeHandler",
          "https://github.com/BTheCoderr/theRounders",
          "https://github.com/CallumHemsley/KazeBot",
          "https://github.com/chrisjpm/CSGOJackpotTemplate",
          "https://github.com/colinsenner/valve-bug-bounty",
          "https://github.com/coryypeters/nrl-odds-intelligence-pipeline",
          "https://github.com/deissh/dev-csgoduo",
          "https://github.com/dom1torii/even-better-font-manager",
          "https://github.com/DONnicov/CSGO-crash-black-screen-",
          "https://github.com/DoubleBoters/CsgoDouble",
          "https://github.com/downarowiczd/DoubleBot",
          "https://github.com/ErayBahar/steammarketscraper",
          "https://github.com/fairydarkness/SteamwebmailAPI",
          "https://github.com/FAQU2/CSGO-Coinflip-MyJailShop",
          "https://github.com/FlamesONE/csgo-case-opening",
          "https://github.com/FunnyRain/csgorun-crash-watch",
          "https://github.com/geohdgio/Venatus-Autenticator",
          "https://github.com/hakanstarlord/steam-bot",
          "https://github.com/HvH-gg/CSGO-Item-CrashFix",
          "https://github.com/HvH-gg/CSGO-NetMsg-CrashFix",
          "https://github.com/isybycnsmam/SteamLibrary",
          "https://github.com/ItsTangerine/SteamApis.Net",
          "https://github.com/JustArchiNET/JustArchi.net",
          "https://github.com/kiri-osint/CS2-Info-Hub-Bot",
          "https://github.com/Koshkaj/monte",
          "https://github.com/madsab/CaseOpening",
          "https://github.com/man90es/steamcardexchange-api",
          "https://github.com/MattPua/steam-unofficial-docs",
          "https://github.com/Metallist1/Portfolio.CsgoWinGambleProject",
          "https://github.com/mikebobadilla/csgo-jackpot",
          "https://github.com/mikebobadilla/meteor-csgojackpot",
          "https://github.com/ModDota/D2VDump",
          "https://github.com/ModDota/DotaTracking",
          "https://github.com/ModDota/eslint-config",
          "https://github.com/mr-codinglv/Casino-script",
          "https://github.com/MrKeelik/MrKeel",
          "https://github.com/noahlatzel/CSGORollHelper",
          "https://github.com/oddsgpt/oddsgpt-market-intelligence",
          "https://github.com/oEXU/csgo-server-crasher",
          "https://github.com/PrdTTony/CSGO-Roulette",
          "https://github.com/r-adamski/csgo-jackpot",
          "https://github.com/Sahotallo/Turan-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-Skinbaron-hellcase",
          "https://github.com/samuelcsouza/steam-marketplace-api",
          "https://github.com/SKINSTRACK/CS2-Price-API",
          "https://github.com/snmtriet/CSGO-Casino-Full-Source-Code",
          "https://github.com/SteamRE/homebrew-tools",
          "https://github.com/SteamRE/opensteamworks.org",
          "https://github.com/TheQuack45/CsgoCaseOpenProgram",
          "https://github.com/TLClassless/StratRouletteCSGO",
          "https://github.com/tomasoom/csgoCaseOpening",
          "https://github.com/vitaliy-evsyukov/steamgifts-autobet-bookmarklet",
          "https://github.com/XpravdaX/RouletteCSGO",
          "https://github.com/YuiKasumii/steam_api_unofficial",
          "https://github.com/Zexuz/Steam-Betting",
          "https://github.com/ANK-RULZZ/steam-jackpot-site",
          "https://github.com/asmilen/CsgoDoubleVS",
          "https://github.com/CORNOODOSADAS/CSGOWeed",
          "https://github.com/CSGOApple/csgoapple",
          "https://github.com/CSGOFAST/csgofast-api",
          "https://github.com/Donakall/csgoDoublebot",
          "https://github.com/fedor-selivanov/csgo-fast-roulette",
          "https://github.com/foldageros/csgod",
          "https://github.com/gmod-gambling/gmod-gambling",
          "https://github.com/ierome/CSGOBoss-BackEnd",
          "https://github.com/jamienp1/CSGODOUBLE-BOT-AUTO",
          "https://github.com/JEYONER/CSGOTOXIC",
          "https://github.com/kalrish/csgo-jackpot",
          "https://github.com/krys12345/roulettee",
          "https://github.com/LilDuggiMuffi/CSGODouble-Working-Bot",
          "https://github.com/LyricLy/Steam2Proton",
          "https://github.com/M0NsTeR77/csgo-roulette",
          "https://github.com/ozanhalis/Hi",
          "https://github.com/scoobertus/CSGO-DoubleBot",
          "https://github.com/Tradeal/CSGO-Jackpot-Bot",
          "https://github.com/ValvePython/artifact",
          "https://github.com/Vampire/CSGO-Roulette-Bot",
          "https://github.com/vdemans/csgo-roulette",
          "https://github.com/VocoreVideo/CSGODungeon-",
          "https://github.com/wayz-dev/csgofloat",
          "https://phishdestroy.io/steam_dossier/output_steam_network/raw_data.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/enforcement-source-manifest.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/fr/steam_enforcement_evidence.content.json",
      "export_json_sha256": "019c599afbfc0438ad8b654767f2c823b85f06e4ac391b104b4fd5333e848808"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "fr/steam_evidence_archive.html",
      "language": "fr",
      "title": "Consultez les sources — Le dossier «Steam »",
      "source_url": "https://phishdestroy.io/steam_dossier/fr/steam_evidence_archive",
      "source_html_sha256": "9e27063ae657c6611dfd82a1b46f9c4833bb5d201d033d0bf51684fbf07bfda1",
      "exported_at": "2026-09-29T00:17:44.069Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "steam_evidence_archive.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/fr/steam_evidence_archive.pdf?v=print-20260929-v5",
        "sha256": "4a0d06fa19f035a2da7321d0a1b12335e9b947daa78d37c8ed97659f04b93245",
        "bytes": 64118,
        "pages": 4
      },
      "integrity": {
        "signed_object": "steam_evidence_archive.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "steam_evidence_archive.content.json.asc",
        "digest_file": "steam_evidence_archive.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify steam_evidence_archive.content.json.asc steam_evidence_archive.content.json",
          "sha256sum -c steam_evidence_archive.content.json.sha256"
        ]
      },
      "content": {
        "text": "DOCUMENTS D'ENQUÊTE / COLLECTE DE SOURCES 002\nSteam Archives de preuves — Documents provenant de « 16,319 »\n\nChaque réclamation. Retour à la source.\n\nCE QUE CETTE SECTION DÉMONTRERA\n\nCette archive judiciaire répertorie 16,319 documents sources primaires — comprenant notamment la documentation de la communauté des développeurs d’Valve, les tickets publics sur GitHub, les réclamations vérifiées sur Trustpilot et les rapports archivés des forums — à l’aide de hachages cryptographiques et de journaux de provenance. Elle fournit un ensemble de preuves vérifiables mettant en évidence des vulnérabilités récurrentes de la plateforme, des dépréciations non documentées d’APIs et des réclamations persistantes de consommateurs concernant des comptes piratés.\n\n← Retour au dossier de synthèse destiné aux dirigeants\n\nRecherchez la fiche correspondant à une allégation. Filtrez par source, ouvrez le texte intégral et suivez le lien d'origine. Les lignes de source peuvent se chevaucher ; une fiche ne correspond pas nécessairement à un incident vérifié.\n\nRetour à l'enquête ↗\n354TRUSTPILOT / LIGNES DE SOURCE\n208REDDIT / LIGNES DE SOURCE\n705GITHUB / LIGNES DE CODE\n15,302FICHIER CSV PRINCIPAL / LIGNES DE LA SOURCE\n16,319 ENREGISTREMENTS — RÉPARTITION PAR TYPE DE PLATEFORME\n\nProvenance de la catégorie Wiki (fiches 7,620 · 46.7%) : Données extraites de la communauté des développeurs d'Valve (developer.valvesoftware.com), de la documentation et de la FAQ de SteamDB, ainsi que des wikis de la communauté des joueurs (Liquipedia CS/Dota et les wikis Fandom Steam) via des instantanés WARC automatisés et les points de terminaison MediaWiki API entre le 2024 et le 2026. Toutes les entrées 7,620 sont entièrement intégrées dans l'export CSV principal (TOTAL_VALVE_SCANDALS_MASTER_DB.csv).\n\nWiki\n7,620\nReddit\n5,635\nGitHub\n2,395\nTrustpilot\n393\nWeb\n276\n9,116 Parmi les fiches de l'16,319 (55.8%), certaines contiennent des références à Steam / Valve\n\nCes archives consultables ont été créées à partir de 2026-09-17 à partir des exportations de données sources énumérées ci-dessus. L'exportation distincte des données de référence de la ligne « 40,448-», utilisée ailleurs dans le dossier, a une portée différente. Voir le générer un manifeste pour les chiffres de cette archive ; les enregistrements peuvent se recouper et ne correspondent pas à des incidents distincts.\n\nPLATEFORME SOURCE\nCOLLECTION DE SOURCES\nSteam / Valve mentions\nCorrespondance de texte ou référentiel « Valve »Texte manquant / supprimé\n16,569 lignes source\n16,319 enregistrements distincts\n249 les lignes en double ont été fusionnées\n1 ligne exclue\nConsulter les fichiers originaux ↘\n★TRUSTPILOT2015-10-16#1RATING 1/5\n\nSteam is the biggest PC gaming platform without a doubt. A power which could be abused but Steam for the most part doesn't. Overall a definite download for any moden digital age PC gamer. It mu... See more\n\nMA · 7 source copies\n★TRUSTPILOT2021-06-18#2RATING 1/5\n\nThey scam people for money, dont believe me? Read this Source: Steam Subscribers/User Agreement NO GUARANTEES TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, NEITHER VALVE NOR ITS AFFILIA... See more\n\nWF · 7 source copies\n★TRUSTPILOT2016-10-28#3RATING 1/5\n\nSupport on site is terrible. Refunds not happend yet, despite games not working. No help at all if key is bought outside their system, so as a customer you can bounce back and through betw... See more\n\nPE · 7 source copies\n★TRUSTPILOT2021-09-27#4RATING 1/5\n\nThey are an amazing company!! My boyfriend paid for and downloaded a game without realizing it wasn’t the version he wanted. When he reached out, they gave him a full refund and responded in the same... See more\n\nVH · 7 source copies\n★TRUSTPILOT2026-07-20#5RATING 1/5\n\nI’ve used Steam for years, but lately, their sales have really lost their edge. I was hoping to score some solid discounts, but many games still feel overpriced, even during sales. Plus, the support response times can be frustratingly slow when issues arise.\n\nCR\n★TRUSTPILOT2025-12-10#6RATING 1/5\n\nI new here , but all my firends had great experience with this platform . They can make money\n\nZeinab Nematollahi\n★TRUSTPILOT2025-11-18#7RATING 1/5TEXT UNAVAILABLE\n\nNo text was included in the source record.\n\nEM\n★TRUSTPILOT2025-10-21#8RATING 1/5\n\nusing steam for over a decade and i have no words how good the platform is. some friends recommended it to me back in 2015 when we wanted to play csgo together and since then im loggin on it on a daily basis to check new games\n\nTrustpilot\n★TRUSTPILOT2025-05-09#9RATING 1/5\n\nSupport are never able to help you and only able to redicrect you to public linkBreaking there own TOSNot able to provider a refundNot able to provide a safe place for gamingBase on the game you play you can get scam.\n\nSym Link · 7 source copies\n★TRUSTPILOT2025-05-09#10RATING 1/5TEXT UNAVAILABLE\n\nNo text was included in the source record.\n\nHearnius\n★TRUSTPILOT2024-12-30#11RATING 1/5\n\nThis company allowed a single phishing scammer 76561199443342045 in 100's of its user community chat rooms \"Steam Chat\" the whole week of Winter Sales, 12-23-2024 - 2025 to spam spaceintrader a scam phishing website.Don't support Valve & Steam that support sca…\n\nFR · 7 source copies\n★TRUSTPILOT2024-11-15#12RATING 1/5\n\nVery realiable! Ive never had an issue over the 11 years ive had steam.\n\nJM\nLa version et ses fichiers source\n\nCette archive regroupe les lignes en double provenant de 249 et exclut une ligne issue des données de 16,569, ce qui laisse 16,319 enregistrements distincts. Un enregistrement peut décrire un événement déjà couvert par un autre enregistrement. La recherche porte sur les titres, les auteurs, les étiquettes de source et les extraits affichés ; le texte complet enregistré s'ouvre avec chaque enregistrement.\n\nTélécharger les quatre fichiers source ↓Nombre de fichiers et hachages SHA-256 ↗Manifeste de compilation d'origine ↗\n\nLe lot contient les exportations récupérées correspondant au nombre de lignes de la version et à ses trois chemins d'accès JSON enregistrés. La version d'origine n'avait pas enregistré les hachages des données d'entrée ni de chemin d'accès CSV principal ; le manifeste associé répertorie les fichiers récupérés et présente la comparaison avec l'index publié.\n\nTrustpilot · steam_support_reviews.json354 lignes · Exportation au format JSON\nReddit · reddit_censored_forensics.json208 lignes · Exportation au format JSON\nGitHub · valve_ignored_bugs.json705 lignes · exportation au format JSON ; le nom de fichier correspond à une étiquette du collecteur\nMaître · TOTAL_VALVE_SCANDALS_MASTER_DB.csv15,302 lignes · exportation au format CSV utilisée à des fins de comparaison\nRegistres judiciaires · UNSEALED_EXHIBITS_AND_AML_DOSSIER.mdWolfire c. Valve : e-mails rendus publics, dépositions de Gabe Newell, aveux concernant l'AML d'octobre 2019\nMaîtriser les faits · FACTS_AND_CITATIONS_DATABASE.md1,638 citations vérifiées et distinctes dans les domaines de la concurrence et de la sécurité sur 35\nArchives d'assistance · support_canned_refusals.html1,505 historique des tickets · 137 captures d'écran archivées · Recherche instantanée en direct\nChamps d'enregistrement, texte manquant et exportations qui se chevauchent\n\nLes dates, les notes, les catégories et les statuts des publications reproduisent fidèlement les exportations sources. Une URL manquante reste manquante. Les mentions « [supprimé] » ou « [effacé] » n’indiquent pas qui a supprimé une publication ni pourquoi. Le filtre Steam / Valve effectue une correspondance textuelle et ne procède pas à une évaluation de la pertinence.\n\n« Exporter les correspondances » permet de télécharger les entrées d’index accompagnées d’extraits ; « Télécharger l’enregistrement » inclut le texte complet enregistré. La fonction distincte 40,448-fichier CSV « row master » et 1,690-GitHub de ligne CSV Ce sont les exportations au sens large qui comptent, et non le nombre de sources pour cette version.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam Archives de preuves — Documents provenant de « 16,319 »"
          },
          {
            "level": 2,
            "id": null,
            "text": "PLATEFORME SOURCE"
          },
          {
            "level": 2,
            "id": null,
            "text": "La version et ses fichiers source"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/fr/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/fr/",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/TOTAL_VALVE_SCANDALS_MASTER_DB.csv",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive_manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive-inputs.zip",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive-inputs-manifest.json",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/unsealed_legal_and_aml/UNSEALED_EXHIBITS_AND_AML_DOSSIER.md",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/forensic_facts_1000/FACTS_AND_CITATIONS_DATABASE.md",
          "https://phishdestroy.io/steam_dossier/fr/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/github_valve_unpatched_bugs.csv"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/fr/steam_evidence_archive.content.json",
      "export_json_sha256": "39fffaa000265a2a0b894e045689c0f04b997ba4cce8d26183433d4e40216c58"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "fr/support_canned_refusals.html",
      "language": "fr",
      "title": "Steam Archives des refus d'assistance et des réponses types — Le dossier «Steam »",
      "source_url": "https://phishdestroy.io/steam_dossier/fr/support_canned_refusals",
      "source_html_sha256": "61b1f0fa2fdfdf85a129f65577691dac3a74a56db6b1d91ce6555fc6578ca19f",
      "exported_at": "2026-09-29T00:17:45.094Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "support_canned_refusals.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/fr/support_canned_refusals.pdf?v=print-20260929-v5",
        "sha256": "9c0a8d8cf1112b9eb4df36542316409891cc70ab11700d2a1b4f1aa969946d60",
        "bytes": 60483,
        "pages": 2
      },
      "integrity": {
        "signed_object": "support_canned_refusals.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "support_canned_refusals.content.json.asc",
        "digest_file": "support_canned_refusals.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify support_canned_refusals.content.json.asc support_canned_refusals.content.json",
          "sha256sum -c support_canned_refusals.content.json.sha256"
        ]
      },
      "content": {
        "text": "CE QUE CETTE SECTION DÉMONTRERA\n\nCe référentiel rassemble des captures d'écran conservées sur 137 ainsi que des recours des victimes ayant fait l'objet d'un audit sur 1,505, détaillant le traitement automatisé des tickets d'assistance par Valve. Il démontre que lorsque des comptes sont piratés via une redirection OpenID ou la génération non autorisée de clés API, le service d'assistance de Steam recourt systématiquement à des réponses types standardisées sans mener d'enquête technique. En refusant catégoriquement la restauration d'objets ou la divulgation des traces d'audit, la plateforme fait porter l'entière responsabilité des failles structurelles d'authentification aux titulaires des comptes piratés.\n\nToutes les captures d’écran sont issues de sources tierces. Les droits d’auteur et le contenu appartiennent à leurs auteurs et plateformes respectifs (utilisateurs de Reddit, auteurs de la communauté Steam, auteurs d’avis sur Trustpilot, X et auteurs de vidéos sur YouTube). Elles sont reproduites uniquement à des fins d’identification et de reportage d’intérêt public ; aucun droit de propriété n’est revendiqué. Chaque illustration renvoie vers sa source d’origine.\n\nFigures reported on the source page\nMeasure\tReported value\tScope\nDocuments archivés\t1505\tFils de discussion concernant les recours des victimes vérifiées et les contraventions\nCaptures d'écran archivées\t137\tCaptures d'écran haute résolution des tickets enregistrées localement\nTaux de restauration\t0.0%\tRévision accordée dans l’affaire des détournements d’avions impliquant des membres d’API\nDuplication des modèles\t100%\tRéutilisation des scripts tels quels par l'ensemble du personnel (Ilya, Roger, Maverick)\nPreuves médico-légales : les trois piliers fondamentaux du refus de coopération\nPILIERS 01 · ADMISSIONPièce R -014\nConfirmation de l'attaque « MitM » sur « The Roger Admission » : API\n\nDans la réponse au ticket n°1cp582i, Steam, « Roger », un membre de l'équipe d'assistance, reconnaît par écrit que des pirates annulent des transactions légitimes via API et les remplacent par des bots clones en quelques millisecondes, mais refuse de restaurer les objets et conseille à la victime de s'adresser à un « technicien informatique local ».\n\nConsulter la lettre d'admission ↗\nPILIER 02 · ESCALADEPièce R -012\n7-Day trading : maintien de la position, absence d'action\n\nUne victime a fourni le SteamID64 des comptes du pirate informatique pendant la période de suspension des transactions sur 7-. Les membres du service d'assistance « Artem » et « Ilya » ont refusé de bloquer les objets volés, invoquant la rareté des objets virtuels, et ont clôturé le ticket à l'aide d'un modèle automatisé.\n\nConsulter le relevé de notes multi-personnel ↗\nPILIER 03 · POLITIQUEPièce R -002\nLa rareté du marché face aux droits de propriété\n\nLa politique officielle de Valve en matière de restauration d'objets stipule explicitement que les objets ne sont pas restitués, car leur restauration « réduirait leur rareté et gonflerait l'économie, ce qui ferait baisser la valeur des objets sur le Marché communautaire ».\n\nCapture d'écran de la politique d'Inspect ↗\nGenèse historique · 22 mars 2018 vers 2026\nPièce H -003 · 8-Surface d'attaque non corrigée sur l'année\nLa première substitution commerciale répertoriée (22 mars 2018)\n\nExactement une semaine avant qu’Valve n’impose sa mesure controversée de « délai de refroidissement » d’une journée pour les échanges d’objets de « Counter-Strike » sur 7-, la communauté des échangeurs a découvert les premiers cas concrets de Steam API Web : exploitation d'une faille de redirection de requêtes. Les pirates ont détourné des sessions Web afin de générer une clé d'API non autorisée à l'adresse steamcommunity.com/dev/apikey sans confirmation FA de l'2, ce qui permet aux bots d'annuler et d'échanger des transactions en temps réel.\n\nAvertissement concernant la campagne d'intérêt public «2018 » de mars : « Les escrocs peuvent détecter automatiquement cette offre d'échange et la refuseront sur votre compte, car ils disposent de votre clé Steam API. Le bot d'escroquerie va alors vous envoyer une offre d'échange pour les mêmes skins… et vous ne remarquerez pas la différence ! »\nParcours des témoignages historiques\n22 mars 2018: Premier échange d'APIs documenté\n2019: Le support technique uniformise les procédures de blocage des « logiciels malveillants »\n2020: Renforcement de la sécurité du script « Clôture d'une demande d'aide »\n2022–2026: Automatisation du phishing via BitB et QR\nOuvrir le fil de discussion Reddit original «2018 » ↗\nPrimary sources\n\n137 gallery cards refer to 78 distinct primary URLs. Images and repeated exhibit captions are omitted from this reading edition.\n\nFull visual archive and original captures",
        "headings": [
          {
            "level": 2,
            "id": null,
            "text": "Figures reported on the source page"
          },
          {
            "level": 2,
            "id": null,
            "text": "Preuves médico-légales : les trois piliers fondamentaux du refus de coopération"
          },
          {
            "level": 3,
            "id": null,
            "text": "Confirmation de l'attaque « MitM » sur « The Roger Admission » : API"
          },
          {
            "level": 3,
            "id": null,
            "text": "7-Day trading : maintien de la position, absence d'action"
          },
          {
            "level": 3,
            "id": null,
            "text": "La rareté du marché face aux droits de propriété"
          },
          {
            "level": 3,
            "id": null,
            "text": "La première substitution commerciale répertoriée (22 mars 2018)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Primary sources"
          }
        ],
        "links": [
          "https://www.reddit.com/r/csgo/comments/1cp582i/i_got_api_scammed_what_do_i_do_now/",
          "https://www.reddit.com/r/DotA2/comments/1e5ovy4/my_account_was_hacked_and_steam_support_refuse/",
          "https://www.reddit.com/r/Steam/comments/3b2abd/steam_will_no_longer_restore_scammed_items_item/",
          "https://www.reddit.com/r/GlobalOffensiveTrade/comments/863tk1/psa_urgent_huge_scam_happening_read_here_how_to",
          "https://phishdestroy.io/steam_dossier/fr/support_canned_refusals#gallery-grid"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/fr/support_canned_refusals.content.json",
      "export_json_sha256": "4bc27341b46625139761067a7a73198b82b76599d6cf3de9f06e19cbc768c8d5"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "fr/valve_scandals_registry.html",
      "language": "fr",
      "title": "Valve Registre des scandales — Le dossier «Steam »",
      "source_url": "https://phishdestroy.io/steam_dossier/fr/valve_scandals_registry",
      "source_html_sha256": "ac01391f525f05ab8cbf5308d4d2d0b60a94b7cbc8464acbf05b5ade084778c2",
      "exported_at": "2026-09-29T00:17:45.235Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "valve_scandals_registry.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/fr/valve_scandals_registry.pdf?v=print-20260929-v5",
        "sha256": "bfa78efd418780f619c3bdd5d488159db7965448f99bec52624119d989f3b9d9",
        "bytes": 64668,
        "pages": 6
      },
      "integrity": {
        "signed_object": "valve_scandals_registry.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "valve_scandals_registry.content.json.asc",
        "digest_file": "valve_scandals_registry.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify valve_scandals_registry.content.json.asc valve_scandals_registry.content.json",
          "sha256sum -c valve_scandals_registry.content.json.sha256"
        ]
      },
      "content": {
        "text": "Archives des scandales majeurs\nValve Registre central des scandales — 160 Incidents référencés\nDOCUMENTS SOURCES (BRUTS) : 11,768\n\nSignalé. Source confirmée. Toujours en cours.\n\nCE QUE CETTE SECTION DÉMONTRERA\n\nCe registre central rassemble des données primaires vérifiées de manière indépendante par 160, détaillant les failles persistantes de la plateforme, les signalements de la communauté supprimés et les défaillances non résolues en matière d'assistance à la clientèle au sein de l'écosystème d'Valve. S'appuyant sur des dossiers de litige vérifiés sur Trustpilot, des tickets d'incident de sécurité archivés sur GitHub et des procédures engagées par les autorités de régulation, il met en évidence des défaillances systémiques récurrentes dans la récupération des comptes et la résolution des litiges clients.\n\n← Retour au dossier de synthèse destiné aux dirigeants\n\n160 données recueillies : une opération d'assistance évaluée par les utilisateurs, des fils de discussion qui ont cessé d'être visibles, des failles de la plateforme signalées puis laissées de côté, ainsi que les incidents pour lesquels Valve a déjà dû rendre des comptes. Rien ici ne reflète notre point de vue : chaque ligne renvoie à sa source d'origine. Ouvrez-en une et lisez-la par vous-même.\n\nSource Records\n11,768\nDans toutes les catégories\nFailles de la plateforme\n3,372\nFailles de la plateforme signalées par la communauté\nSujets censurés\n109\nMessages Reddit supprimés par un modérateur\nRéclamations concernant l'assistance\n471\nPlaintes vérifiées sur Trustpilot\nFaisabilité de la mise en œuvre\nBlocage de domaines d'authentification\n\nLe blocage au niveau du domaine des hébergeurs d'authentification OpenID est techniquement simple à mettre en œuvre : dès lors qu'une ressource est exclue de la redirection de connexion via Steam, les domaines tiers servant de proxys d'authentification pour cette même ressource peuvent être filtrés par le même ensemble de règles. Une analyse détaillée de la faisabilité de cette mise en œuvre est fournie dans le dossier principal.\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\nVoir la faisabilité de la mise en œuvre dans le dossier →\nCatégorie : Réclamations adressées au service d'assistance de Trustpilot (escalades négatives filtrées)176 enregistrements source correspondants · doublons masqués\nConsumer Complaint2026-07-20\nAuthor: C***\n\nI’ve used Steam for years, but lately, their sales have really lost their edge. I was hoping to score some solid discounts, but many games still feel overpriced, even during sales. Plus, the support response times can be frustratingly slow when issues arise.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2026-07-20\nConsumer Complaint2025-05-09\nAuthor: S*** L***\n\nSupport are never able to help you and only able to redicrect you to public linkBreaking there own TOSNot able to provider a refundNot able to provide a safe place for gamingBase on the game you play you can get scam.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2025-05-09\nConsumer Complaint2024-12-30\nAuthor: F***\n\nThis company allowed a single phishing scammer 7656…2045 in 100's of its user community chat rooms \"Steam Chat\" the whole week of Winter Sales, 12-23-2024 - 2025 to spam spaceintrader a scam phishing website.Don't support Valve & Steam that support scams. Don't give your log in credentials to account hijacking scammers. This company also allows engagements of commercial advertising / spam for gambling in violation of its own Rules and Guidelines / Online Conduct. 7656…5023 proof - groups/deskinsfans key drop advertising, thanks TannerfromKD and Valve!*\"The Consumer Review Fairness Act (CRFA) protects people’s ability to share their honest opinions about a business’s products, services, or conduct, in any forum, including social media. The law protects a broad variety of honest consumer assessments, including online reviews, social media posts, uploaded photos, videos, etc. And it doesn’t just cover product reviews. It also applies to consumer evaluations of a company\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2024-12-30\nConsumer Complaint2024-07-31\nAuthor: A***\n\nhorrible company.randomly you get \"This account may have been accessed by someone else.\"this happened to me 3 times.the 3rd time they wanted a cd key.a spent useless cd key that nobody has any reason to keep laying around.i gave them the paypal bill for my first purchase back in 2015.i gave them a bill for my first phone number ever on the account.i still got the same email attached to the account.this company is literally a scam. nothing but a scam.they randomly claim you been accessed somewhere else and then require you to give them information no reasonable person would ever have, if not your done and have to rebuy everything.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2024-07-31\nConsumer Complaint2023-12-09\nAuthor: K***\n\nHad 288 euros in steam wallet, someone hacked my account even with two step verification, write a steam support for help but only answer was if something is spent in community market they can’t help.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2023-12-09\nConsumer Complaint2023-09-26\nAuthor: J***\n\nI was banned for saying \"Who let grandma on the PC\"and another for simply calling someone ignorant.Power tripping mods, devs who don't care, steam doesn't care. Yet allows racism/trolling/etc Fk steam, its a joke now.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2023-09-26\nConsumer Complaint2022-08-31\nAuthor: Anonymous\n\nSteam community is plain bad for a various reasons:1. Steam forums are a big mess, for example they allow users to post in any language and as result you get jumbled mess with posts in foreign languages together with English language posts. For example, If you check CS GO forums, you'll see half of posts are in Russian and half in English. I don't understand why such a big and international company would leave their forums so unorganized like that. All other normal companies have English only language allowed which is an international language and sometimes subforums for other languages like German, French and etc... so if French people want to post in French they go specifically in that sub-forum. But no, Steam doesn't care about this. Their forums is a one big mess.2. Moderation is biased and joke. I don't understand why such a big company like Steam can't afford to hire people for moderation and pay them. Instead they just recruit random people for moderation who do it for free and\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2022-08-31\nConsumer Complaint2022-05-28\nAuthor: J***\n\nThe login code never arrives. I hate Steam.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2022-05-28\nConsumer Complaint2021-11-08\nAuthor: N***\n\nThe service is terrible, I only signed up because I really like the game I wanted, but the rest is terrible, I hope to get something better soon.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-11-08\nConsumer Complaint2021-06-18\nAuthor: W***\n\nThey scam people for money, dont believe me? Read thisSource: Steam Subscribers/User Agreement NO GUARANTEESTO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, NEITHER VALVE NOR ITS AFFILIATES GUARANTEE CONTINUOUS, ERROR-FREE, VIRUS-FREE OR SECURE OPERATION AND ACCESS TO STEAM, THE CONTENT AND SERVICES, YOUR ACCOUNT AND/OR YOUR SUBSCRIPTION(S) OR ANY INFORMATION AVAILABLE IN CONNECTION THEREWITH.In short: You got a virus or your data leaked because of our software? Whoopsies we dont care, that isnt even legal or the last of their scammy stuff...\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-06-18\nConsumer Complaint2021-05-14\nAuthor: B***\n\nThe support is one of the worst I've ever seen.Useless support team.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-05-14\nConsumer Complaint2020-04-02\nAuthor: J***\n\nSteamcommunity has 15% fees, 15!!!!\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2020-04-02\nConsumer Complaint2020-03-27\nAuthor: H***\n\nWhat can I say? the support is one of the worst I've ever seen maybe the FUNCOM is much worse. If you tell the true on the steam forum you just got a BAN even if what you said did not violated the rules of the forum.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2020-03-27\nConsumer Complaint2018-03-16\nAuthor: B***\n\ndon't sign up will stick on your computer will kill your pc power you can't remove it from your pc even you deleted it will stay woking in the system\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2018-03-16\nConsumer Complaint2016-12-27\nAuthor: J***\n\nIn bloddy hate their page it's tiresome, it's in no way intuitive. I tried reaching out for support, but that is a maze.I'm simply trying to log in and redeem a key of a product I already bought, their search function is a joke. I f*u*c*k*i*n*g hate them. The layout is not like the how to video from the dealer, this can be done much simpler. I don't frigin care aboutn what other titles you have in store or what genre, I just want to redeem my key and install.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-12-27\nConsumer Complaint2016-10-28\nAuthor: P***\n\nSupport on site is terrible.Refunds not happend yet, despite games not working.No help at all if key is bought outside their system, so as a customer you can bounce back and through between bad support systems?? I wait for some other companies to compete in this market, for this can't be the best we as customers can expect.And do put an email up to find, instead of this stuppid website where you spend so long time trying to find a solution on, instead of a simple mail. Often the problem is not there, or if it's there just saying no help here???I need a response\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-10-28\nConsumer Complaint2016-06-26\nAuthor: V*** W***\n\nUseless support as always!\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-06-26\nConsumer Complaint2014-07-01\nAuthor: J***\n\nexpensive, and support team not willing to cooperate\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2014-07-01\nConsumer Complaint2014-04-15\nAuthor: B***\n\nWhen you pay for a program, you expect it too work. cant not buy or anything and have written to valve. but there is not a being done a damn thing abut it..\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2014-04-15\nConsumer Complaint2026-09-03\nAuthor: M***\n\nWorst platform ever wont give me a refund even though a game is unplayable because of bugs I won't ever be using the crap platform again I hope the platform breaks down for good piece fo crao\n\nTarget Domain: steamcommunity.com / steampowered.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2026-09-03\n\nAucun résultat correspondant\n\nEssayez de modifier votre recherche en cours ou de consulter un autre onglet de catégorie.\n\n1 / 9",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Valve Registre central des scandales — 160 Incidents référencés"
          },
          {
            "level": 2,
            "id": null,
            "text": "Blocage de domaines d'authentification"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: C***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: S*** L***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: F***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: A***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: K***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: Anonymous"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: N***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: W***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: H***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: P***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: V*** W***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: M***"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/fr/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/fr/#proxy-bypass-explainer",
          "https://phishdestroy.io/steam_dossier/fr/#autoban-feasibility-section",
          "https://www.trustpilot.com/review/steamcommunity.com"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/fr/valve_scandals_registry.content.json",
      "export_json_sha256": "173663926b57eb7d677913759ca853b0c560066452592cac1d7c4f65474ab457"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "fr/output_steam_network/index.html",
      "language": "fr",
      "title": "Une architecture, pas une faille : le réseau d'automatisation — Dossier « L'Steam »",
      "source_url": "https://phishdestroy.io/steam_dossier/fr/output_steam_network/index",
      "source_html_sha256": "392821d4fa0aefb8ece088081b911ea34e12100fa977c8dbf03e68cf68d18a91",
      "exported_at": "2026-09-29T00:17:45.426Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__index.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/fr/output_steam_network__index.pdf?v=print-20260929-v5",
        "sha256": "0605d6beae011626d16d17d82a830905db930953118f9b94bb5763af544c84ff",
        "bytes": 68370,
        "pages": 3
      },
      "integrity": {
        "signed_object": "output_steam_network__index.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__index.content.json.asc",
        "digest_file": "output_steam_network__index.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__index.content.json.asc output_steam_network__index.content.json",
          "sha256sum -c output_steam_network__index.content.json.sha256"
        ]
      },
      "content": {
        "text": "Annexe VII · Analyse de l'architecture technique\nSteam Architecture réseau — Fidélité des protocoles et analyse de l'écosystème\n\nL'automatisation est au cœur de l'architecture d'Valve. Ce n'est pas une faille de sécurité.\n\nCE QUE CETTE SECTION DÉMONTRERA\n\nCe module présente la topologie technique des dépôts de développeurs 252, des profils 3,320 GitHub et des paires de contributeurs 4,214 qui constituent la base de l’écosystème d’automatisation Steam. Il démontre que l’automatisation tierce repose sur le protocole officiel Connection Manager de Valve, les schémas Protobuf et les API Web, sans code d’exploitation. En concevant des jetons de confirmation algorithmiques « Steam Guard » et en percevant des frais de transaction minimaux jusqu’à 66.7%, Valve, l’entreprise agit en tant qu’architecte intentionnel et principal bénéficiaire commercial des opérations automatisées de l’écosystème.\n\n← Retour au dossier de synthèse destiné aux dirigeants\n\nLorsqu’Valve s’adresse aux autorités de régulation, aux prestataires de paiement ou aux victimes d’escroqueries, l’entreprise attribue le vol d’identités et la manipulation du marché à des « exploits de tiers non autorisés » et à des « automatisations illicites et malveillantes ». La réalité technique de ce réseau de référentiels 252-démontre exactement le contraire : Chaque framework d'automatisation, chaque bot de trading et chaque flotte de farming fonctionne strictement dans le respect des définitions officielles du protocole, des API Web et des mécanismes d'authentification conçus, documentés et monétisés par la société « Valve ».\n\nConstat d'expertise : architecture délibérée ou violation illégitime\n\nLes logiciels analysés dans ce module — notamment SteamKit, node-steam-user, ValvePython/steam, et ArchiSteamFarm — contient aucune faille logicielle, aucune corruption de mémoire et aucune exploitation de type « zero-day ». Il s’agit d’implémentations open source propres et robustes du protocole client propriétaire « Connection Manager » (CM) d’Valve, des Google Protocol Buffers (Protobufs) et des API Web. Valve a conçu ces API pour prendre en charge les connexions programmatiques, et a développé Steam Guard afin de permettre l’utilisation de jetons de confirmation algorithmiques (identity_secret), et perçoit des frais d'15% annoncés qui augmentent progressivement jusqu'à jusqu'à 66.7% en faveur d'Valve sur les cartes à haut débit et les livraisons de produits de base que les botnets automatisés écoulent.\n\n01 des piliers · Respect du protocole\nSchémas Protobuf officiels\n\nLes bibliothèques d'automatisation ne contournent pas les barrières de sécurité. Elles sérialisent les messages Protobuf officiels (steammessages_clientserver.proto) via TCP/WebSockets directement vers les clusters CM officiels d'Valve, exactement comme le fait le client Steam.\n\n02 des piliers · 2FA algorithmique\nAutorisation de négociation programmatique\n\nL'ensemble du secteur du commerce des skins, qui représente plusieurs milliards de dollars, repose sur Valve IEconService API et les clés d'authentification TOTP sur mobile. Valve a délibérément conçu Steam Guard pour permettre les confirmations de transactions de machine à machine.\n\n03 du pilier · Bénéficiaire commercial\nTrafic généré par les machines et monétisé : jusqu’à un seuil de commission de66.7%\n\nValve Le site annonce des frais de 15%, mais sur les articles de grande consommation négociés par des bots automatisés — cartes à collectionner, coffrets et lots bon marché dont les prix varient entre $0.03 et $0.05 —, le seuil minimum de 2 cents fixé par Valve ($0.01 Steam + $0.01 publisher) s'applique. 50% à 66.7% en faveur d'Valve (2¢ prélevés sur une carte 3¢, ce qui laisse au vendeur 1¢). Plus $5.00 par compte ($26.8M rien que pour la flotte scannée).\n\nModule « 01 » · Données relatives aux référentiels et aux protocoles\nInfrastructure publique de développement et de référentiels\n\nCatalogue technique détaillé des dépôts open source d'252, qui sous-tendent l'automatisation de Steam. Il retrace la manière dont les outils standard d'ingénierie logicielle mettent en œuvre les points de terminaison publiés par Valve sur API, sans recourir à des exploits.\n\n252Dépôts\n4,554Liens vers les rôles\nConsulter les éléments de preuve du dépôt →Module « 02 » · Démographie des écosystèmes\nIndicateurs relatifs à l'écosystème mondial de l'ingénierie\n\nRépartition géographique et institutionnelle des ingénieurs en logiciels d'3,320s contribuant à l'écosystème de l'automatisation de l'Steam, y compris leurs affiliations professionnelles au sein des principaux employeurs du secteur technologique.\n\n3,320Ingénieurs\n98,902Paires de connexions\nConsulter les indicateurs relatifs à l'écosystème →Module « 03 » · Graphique interactif\nGraphique interactif du protocole et du réseau des développeurs\n\nVis.js complète sous forme de graphes interactifs représentant les référentiels, les bibliothèques de protocoles (SteamKit, Steamworks, ASF) et les recoupements entre les contributeurs de différents projets. Elle illustre visuellement la puissance de l'architecture logicielle open source légitime et interconnectée qui alimente l'écosystème d'automatisation d'Steam.\n\nInteractifVis.js Moteur\nIsolement des grappesRecherche en direct\nAucune faille d'exploitationAPI standard\nLancer le graphique interactif du réseau →\nContexte réglementaire et juridique (article de GDPR 25 et protection des consommateurs) :\nConformément au principe de « protection des données dès la conception et par défaut », une architecture de plateforme permettant la génération silencieuse de clés d’API, l’annulation de transactions sans notification préalable et la liquidation automatisée d’actifs relève d’un choix architectural de l’opérateur de la plateforme. Lorsque Valve rejette systématiquement les demandes de remboursement des consommateurs en affirmant que les pertes ont été causées par des « cyberattaques externes », elle dissimule le fait que le vecteur d’attaque est l’architecture Web API de Valve elle-même, conçue intentionnellement.\n\nAFFICHAGE INTERACTIF\n\nUne visualisation interactive complète du référentiel « 252-», le graphe du réseau de développeurs « 3,320-», est disponible à l'adresse suivante : network.html. Les indicateurs agrégés se trouvent sur la page Indicateurs BI page.\n\nLe dossier «Steam » · Archives d'architecture technique · Documents open source · Tous droits cédés à l'humanité.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam Architecture réseau — Fidélité des protocoles et analyse de l'écosystème"
          },
          {
            "level": 3,
            "id": null,
            "text": "Schémas Protobuf officiels"
          },
          {
            "level": 3,
            "id": null,
            "text": "Autorisation de négociation programmatique"
          },
          {
            "level": 3,
            "id": null,
            "text": "Trafic généré par les machines et monétisé : jusqu’à un seuil de commission de66.7%"
          },
          {
            "level": 2,
            "id": null,
            "text": "Infrastructure publique de développement et de référentiels"
          },
          {
            "level": 2,
            "id": null,
            "text": "Indicateurs relatifs à l'écosystème mondial de l'ingénierie"
          },
          {
            "level": 2,
            "id": null,
            "text": "Graphique interactif du protocole et du réseau des développeurs"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/fr/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/fr/output_steam_network/valve_ru_farming_isolated.html",
          "https://phishdestroy.io/steam_dossier/fr/output_steam_network/steam_ecosystem_dashboard.html",
          "https://phishdestroy.io/steam_dossier/fr/output_steam_network/network.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/fr/output_steam_network__index.content.json",
      "export_json_sha256": "f136a4c5397e57bf0faf61ac0d06c2dc568bfde3ad8773f41136bcbf4a6c1bfb"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "fr/output_steam_network/network.html",
      "language": "fr",
      "title": "Explorateur de développeurs et de dépôts — Le dossier «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/fr/output_steam_network/network",
      "source_html_sha256": "00cc5f7342cc767d088f3679922bbf0f3069d3305a919024dc256077e680abe6",
      "exported_at": "2026-09-29T00:17:47.143Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__network.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/fr/output_steam_network__network.pdf?v=print-20260929-v5",
        "sha256": "c84e6c99782b67b41f6a009f5fee7bda57de2022c40e25d33e4ebefb0639b374",
        "bytes": 36588,
        "pages": 1
      },
      "integrity": {
        "signed_object": "output_steam_network__network.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__network.content.json.asc",
        "digest_file": "output_steam_network__network.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__network.content.json.asc output_steam_network__network.content.json",
          "sha256sum -c output_steam_network__network.content.json.sha256"
        ]
      },
      "content": {
        "text": "Explorateur de développeurs et de dépôts\n\nRechercher un nœud. Examiner la relation enregistrée.\n\nARCHIVES PUBLIQUES / CONNEXIONS RECUEILLIES\nRecherche en direct\nCouches de filtrage\nNombre total de développeurs3,320\nTotal des opérations de pension252\nGRAPHIQUE AFFICHÉ / SOUS-ENSEMBLE DE LA COLLECTION468 NŒUDS • 1103 ARÊTES\nFiche de profil sélectionnée\n\n💡 Cliquez sur n'importe quel nœud du graphe ou saisissez une recherche pour examiner les connexions et les chemins sources associés.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Explorateur de développeurs et de dépôts"
          }
        ],
        "links": []
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/fr/output_steam_network__network.content.json",
      "export_json_sha256": "057242e0f091940018bfa646639da898b214dd4df32931f68bc788c08a0e9300"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "fr/output_steam_network/steam_ecosystem_dashboard.html",
      "language": "fr",
      "title": "Le réseau « Collected » en chiffres — Le dossier «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/fr/output_steam_network/steam_ecosystem_dashboard",
      "source_html_sha256": "a30f719177d1f9905db44134964edbad1cc2d540a75c9499d890e176f66cd148",
      "exported_at": "2026-09-29T00:17:46.773Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__steam_ecosystem_dashboard.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/fr/output_steam_network__steam_ecosystem_dashboard.pdf?v=print-20260929-v5",
        "sha256": "a66a0ea99d05176f67e4185179e0a24a5f202dcc5e2ae3e7e9cfb13e44621d92",
        "bytes": 39944,
        "pages": 2
      },
      "integrity": {
        "signed_object": "output_steam_network__steam_ecosystem_dashboard.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__steam_ecosystem_dashboard.content.json.asc",
        "digest_file": "output_steam_network__steam_ecosystem_dashboard.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__steam_ecosystem_dashboard.content.json.asc output_steam_network__steam_ecosystem_dashboard.content.json",
          "sha256sum -c output_steam_network__steam_ecosystem_dashboard.content.json.sha256"
        ]
      },
      "content": {
        "text": "APERÇU DES STATISTIQUES // FICHIER « 02 »\nSteam Tableau de bord de l'écosystème — Le réseau en chiffres\n\nLe réseau, en chiffres.\n\nCE QUE CETTE SECTION DÉMONTRERA\n\nCe tableau de bord regroupe les informations structurelles issues des développeurs d’3,320 et des dépôts 252, identifiant ainsi 68 les bases de code spécifiques aux jeux d’argent et les passerelles de connexion multiplateformes. Les données empiriques mettent en évidence des regroupements géographiques et des recoupements entre développeurs, montrant que l’infrastructure tierce dédiée aux jeux d’argent fonctionne comme un secteur logiciel organisé et fortement interconnecté, intégré à la plateforme Steam.\n\n← Retour au dossier de synthèse destiné aux dirigeants\n\nStatistiques consolidées issues de la base de données d'enquête : répartition géographique, principales entreprises, plateformes de jeux d'argent en skins et ponts de connexion actifs.\n\nDéveloppeurs Scanned3320\nTotal des opérations de pension252\nRepos liés aux jeux d'argent68\nNombre total de connexions1,426\nStructure et secteurs de l'automatisation\nSecteur I — Noyau de la société «Valve»\n\nRéférentiels officiels et logiciels système. Espace de développement confirmé des collaborateurs d’Valve, Nephyrin et Joe Ludwig.\n\nSecteur II — Moteurs d'autorisation et émulateurs de protocole (SteamKit)\n\nBibliothèques réseau issues d'une ingénierie inverse, co-réalisées par Nephyrin, d'Valve, et DoctorMcKay, développeur spécialisé dans les skins de jeux d'argent.\n\nSecteur III — Clients spécialisés dans le « card farming » (ArchiSteamFarm)\n\nUtilisez des émulateurs du protocole SteamKit pour faire tourner en arrière-plan des millions de faux clients (en veille) afin de collecter des cartes à collectionner.\n\nRépartition géographique des développeurs\nAllemagne57\nÉtats-Unis52\nCanada48\nRoyaume-Uni44\nPologne30\nFrance28\nFédération de Russie27\nChine27\nÉtats-Unis (État de Washington)23\nAustralie19",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam Tableau de bord de l'écosystème — Le réseau en chiffres"
          },
          {
            "level": 3,
            "id": null,
            "text": "Secteur I — Noyau de la société «Valve»"
          },
          {
            "level": 3,
            "id": null,
            "text": "Secteur II — Moteurs d'autorisation et émulateurs de protocole (SteamKit)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Secteur III — Clients spécialisés dans le « card farming » (ArchiSteamFarm)"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/fr/#briefing-heading"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/fr/output_steam_network__steam_ecosystem_dashboard.content.json",
      "export_json_sha256": "882be13d1be54b743d2f7dae3e9b3845a654eca27421d8ab74c0e55f30bcfe07"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "fr/output_steam_network/valve_ru_farming_isolated.html",
      "language": "fr",
      "title": "Code, contributeurs et forks — Le dossier «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/fr/output_steam_network/valve_ru_farming_isolated",
      "source_html_sha256": "2fbdd85c7801d6bab64cc9222fa6bd12da5ef7e79a9abcc7c97efcb5c8b70212",
      "exported_at": "2026-09-29T00:17:47.059Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__valve_ru_farming_isolated.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/fr/output_steam_network__valve_ru_farming_isolated.pdf?v=print-20260929-v5",
        "sha256": "0f758bb92ab6b887acebe44314cff4fe241d51ba1f629156624f2a46c5e531c1",
        "bytes": 41288,
        "pages": 2
      },
      "integrity": {
        "signed_object": "output_steam_network__valve_ru_farming_isolated.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__valve_ru_farming_isolated.content.json.asc",
        "digest_file": "output_steam_network__valve_ru_farming_isolated.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__valve_ru_farming_isolated.content.json.asc output_steam_network__valve_ru_farming_isolated.content.json",
          "sha256sum -c output_steam_network__valve_ru_farming_isolated.content.json.sha256"
        ]
      },
      "content": {
        "text": "PARTIE II / SUIVRE LA RELATION TÉMOIGNÉE PAR DES DOCUMENTS\n\nLes « forks », les contributions et les dépendances logicielles constituent des preuves distinctes. Ce point de vue préserve les rôles recensés ; l'emploi, les contournements de sécurité et l'implication dans des activités criminelles nécessitent des sources supplémentaires.\n\nOuvrir la carte interactive des fonctionnalités ↗\nSOURCES PUBLIQUES / AUDIT DES FONCTIONS\nLe code. Les contributeurs. Les forks.\n1. Nephyrin : bifurcations et contributions\n\nL'aperçu fourni indique que Nephyrin est un contributeur à ValveSoftware/Proton et l'auteur d'un fork de SteamRE/SteamKit et SteamRE/open-steamworks. Ses informations de profil mentionnent « Valve Software ». Ces champs doivent être interprétés séparément.\n\nUne fourche correspond à une copie du dépôt. Cette exportation n'inclut pas de commit enregistrant des modifications apportées au code d'authentification de SteamKit.\nRéférences du dépôt / consulter l'historique\nSteamRE/SteamKit ↗ SteamRE/open-steamworks ↗\n2. Fonctionnalités publiques : automatisation sans client de bureau\n\nSteamKit et node-steam-user permettent d’interagir par programmation avec Steam. ArchiSteamFarm documente la gestion de plusieurs comptes pour l’acquisition de cartes et déclare SteamKit2 comme dépendance.\n\nIl s'agit là de capacités d'automatisation concrètes. L'exécution en mode « headless » n'implique pas une utilisation commerciale exclusive ni un contournement de la protection «Steam». Les éléments pertinents à prendre en compte sont les identifiants demandés, les actions auxquelles ils donnent accès et les contrôles appliqués par la plateforme.\n\nSource : fichiers README des projets et ArchiSteamFarm.csproj. La carte des capacités établit des liens entre toutes les dépendances répertoriées.\n3. JoeLudwig : le label des contributeurs du hl2sdk\n\nL'instantané mentionne JoeLudwig comme contributeur aux projets alliedmodders/hl2sdk, ValveSoftware/openvr et ValveSoftware/source-sdk-2013. Il s'agit là d'une relation observable entre les projets. L'exportation ne fournit aucune preuve établissant un lien entre une modification particulière du SDK et un vol ou une utilisation à des fins de jeux d'argent.\n\nRéférences du dépôt / consulter l'historique\nalliedmodders/hl2sdk ↗ DoctorMcKay/node-steam-user ↗\nSCHÉMA LOGIQUE // PISTES\nOrganigramme de la logique de connexion :\nPROFIL RELATIONNEL\nNephyrin / profil compilé\nContributeur : Proton. Auteurs de la branche : SteamKit et open-steamworks.\n▼ Relations de fork regroupées\nBIBLIOTHÈQUE COMMUNAUTAIRE\nSteamRE/SteamKit\nBibliothèque du réseau Public Steam gérée par l'organisation SteamRE.\n▼ Dépendance SteamKit2 déclarée\nAUTOMATISATION DOCUMENTÉE\nJustArchiNET/ArchiSteamFarm\nLa documentation fait état d'une pratique consistant à accumuler des cartes sur plusieurs comptes et d'une dépendance à SteamKit2.\nANALYSE DES DONNÉES / APERÇU DES SOURCES\nENREGISTRÉ : étiquettes distinctes pour les contributeurs et les créateurs de branches.\nFAIT AVÉRÉ : les bibliothèques publiques favorisent les interactions programmatiques entre l'Steam.\nQUESTION EN SUSPENS : la paternité d'un code spécifique, l'approbation d'une plateforme et l'imputation d'un abus nécessitent des preuves distinctes.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Le code. Les contributeurs. Les forks."
          },
          {
            "level": 2,
            "id": null,
            "text": "1. Nephyrin : bifurcations et contributions"
          },
          {
            "level": 2,
            "id": null,
            "text": "2. Fonctionnalités publiques : automatisation sans client de bureau"
          },
          {
            "level": 2,
            "id": null,
            "text": "3. JoeLudwig : le label des contributeurs du hl2sdk"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/fr/investigation_part2.html#automation-map",
          "https://github.com/SteamRE/SteamKit",
          "https://github.com/SteamRE/open-steamworks",
          "https://github.com/alliedmodders/hl2sdk",
          "https://github.com/DoctorMcKay/node-steam-user"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/fr/output_steam_network__valve_ru_farming_isolated.content.json",
      "export_json_sha256": "725ef5d88240dc8bb7c2ab8491337fa562fb9fbd7d7aa0073fea1efa3292b001"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "it/card_economy.html",
      "language": "it",
      "title": "L'economia delle carte — Il dossier Steam",
      "source_url": "https://phishdestroy.io/steam_dossier/it/card_economy",
      "source_html_sha256": "2012bb1f0caf5fcdd55fcc765daa7d0baf1103775215f0776ab224b497f4b621",
      "exported_at": "2026-09-29T00:17:48.744Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "card_economy.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/it/card_economy.pdf?v=print-20260929-v5",
        "sha256": "cb089449d4e5a9447f309fa5da922e7e11489f2f873c01a961fa30f932787105",
        "bytes": 253403,
        "pages": 25
      },
      "integrity": {
        "signed_object": "card_economy.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "card_economy.content.json.asc",
        "digest_file": "card_economy.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify card_economy.content.json.asc card_economy.content.json",
          "sha256sum -c card_economy.content.json.sha256"
        ]
      },
      "content": {
        "text": "ALLEGATO V — L'ECONOMIA DELLE CARTE\nUna \"bot farm\" non è una falla nel negozio di Valve. È una cliente.\n\nUn account Steam non può ricevere nemmeno una carta da gioco finché non avrà speso $5.00 nello store. Non può \"farmare\" un gioco di cui non è proprietario, né uno che gli è stato regalato. Quindi, prima che un sistema automatizzato di \"farm\" delle carte produca qualsiasi cosa, deve averne pagato l’accesso — per ogni account, al prezzo pubblicato da Valve. Quindi la clausola di automazione di Valve specifica, riga per riga, esattamente ciò che quel sistema di raccolta produce; la sua licenza vieta ogni percorso attraverso il quale una carta ottenuta tramite farming si trasformi in denaro; e il suo mercato trattiene una percentuale quando la carta viene comunque venduta — pubblicizzata a 15%, ma con un limite minimo di due centesimi per vendita, che su una carta il cui prezzo è espresso in centesimi rappresenta la maggior parte del prezzo. Questo documento illustra l’entità di tale commercio, quanto costa in set il livello più alto di un profilo e come l’ufficio di controllo di Valve applica la stessa clausola quando l’account appartiene a un normale trader.\n\nCosa deve acquistare per prima cosa un'azienda agricolaQuanto costa un livello nei setDa entrambi i lati della scrivaniaChi regola l'economia delle carte?\n$5.00Effettuare una spesa in negozio prima che un account possa ricevere una carta — Pagina di assistenza di Valve\n13,876Giochi su Steam che emettono carte collezionabili, con 99,971 tipi di carte distinti\n694,673Set completi di carte attualmente disponibili in magazzino presso 91 bot di trading quotati in borsa\n1,389,346Le quote di consegna di carte account e da gioco che le scorte hanno già esaurito, come minimo\n$9.99Prezzo mediano di un gioco di carte — il set completo viene venduto a un prezzo mediano di $0.74\n97,114I membri del gruppo dedicato allo scambio di figurine, il cui elenco dei moderatori include un dipendente con codice Valve — § 08\n01 — Il processo\nChe cos’è in realtà una fattoria, passo dopo passo\n\nLe informazioni riportate in questa sezione provengono esclusivamente dalla documentazione dello strumento stesso e dalle pagine di assistenza di Valve. Nessuna delle informazioni contenute in questa sezione è frutto di deduzioni, né è oggetto di contestazione da parte di nessuna delle due parti.\n\nFase 1\nAcquista\n\nL'account non deve essere limitato. La pagina di assistenza di Valve impedisce agli account con restrizioni di \"Partecipare al mercato Steam\", da \"Scambio di oggetti della community Steam (carte da gioco, buste di espansione, gemme, ecc.)\" e da \"Ottenere Steam livelli di profilo (bloccati al livello 0) e carte collezionabili\". Il cancello è denaro: \"Dovrai spendere almeno $5.00 USD all'interno del negozio Steam.\"\n\nFase 2\nAcquista giochi\n\nLe carte si ottengono solo dai giochi di cui si è in possesso. \"Per poter ricevere eventuali carte in regalo dal gioco, devi esserne il proprietario sull'account Steam. La condivisione familiare non equivale alla proprietà e non viene presa in considerazione.\" Anche i percorsi gratuiti sono chiusi: \"I giochi a pagamento ottenuti gratuitamente durante una promozione non possono essere utilizzati per ottenere carte\", e \"Non è possibile ottenere carte dai giochi F2P senza spendere soldi al loro interno.\"\n\nFase 3\nInattivo\n\nLo strumento effettua l'accesso all'account sulla rete Steam in modalità headless, \"analizza i tuoi badge\", crea l'elenco dei titoli ottenibili e avvia \"giocare alle partite idonee e verificare periodicamente se la partita è già stata completata.\" Descrizione del meccanismo fornita dal responsabile del progetto: esso \"non fa altro che comunicare a Steam che stiamo giocando a un determinato gioco.\"\n\nFase 4\nLe gocce si esauriscono\n\nOgni titolo ha una durata limitata. \"Ogni gioco prevede un numero fisso di carte da ottenere. Una volta ottenute tutte (circa la metà del set completo), il gioco non è più un'opzione valida per il farming.\" Un’azienda agricola che voglia continuare a produrre deve continuare ad acquistare titoli. L’offerta di carte è limitata dagli acquisti — per come è stato progettato il sistema, e a vantaggio di Valve.\n\nFase 5\nPrelievo\n\nLa carta esce da una delle tre porte: viene venduta sul Mercato della Comunità, scambiata o trasformata in gemme. Ciascuna di queste operazioni costituisce una transazione sul Mercato in abbonamento o uno scambio, e il § 3.D riserva l’addebito: \"Valve può applicare una commissione sulle transazioni effettuate in un marketplace in abbonamento.\" È questo il passaggio che rende l’intera operazione una violazione — vedi 05.\n\nFonti, lette e citate testualmente su 2026-09-22: Steam Assistenza — Account utente limitati ↗ · ArchiSteamFarm Domande frequenti ↗ · Valve — Steam Domande frequenti sulle carte collezionabili ↗ · Steam Contratto di abbonamento ↗ archiviato 2026-09-24 ↗. ArchiSteamFarm è utilizzato in questa pagina come strumento di misura, non come imputato; la sua stessa documentazione afferma chiaramente che \"L'ASF non è autorizzata da Valve\".\n\n02 — La scala\nPrima ancora che un’azienda agricola guadagni un centesimo, ha già pagato Valve\n\nPoiché un account con restrizioni non può ricevere una carta, ogni account di una farm deve essere sbloccato prima di poter produrre qualsiasi cosa. La soglia è resa nota e viene addebitata per ogni account.\n\nDimensioni dell'azienda agricola\tDa dove viene quel numero\tSpesa minima in negozio per poter ottenere la tessera\n10 account\tIl limite massimo raccomandato dall'ASF — \"in base alle linee guida interne Valve e ai nostri suggerimenti\"\t$50\n100–200 account\tLimite tecnico riportato nella stessa sezione delle domande frequenti: \"È possibile eseguire fino a 100-200 bot con un unico indirizzo IP e una singola istanza di ASF\"\t$500 – $1,000\n120 conti\tCaso di applicazione della norma n. 3 riportato di seguito — esclusione definitiva\t$600\n170 conti\tCaso di applicazione delle norme n. 2 riportato di seguito — esclusione definitiva durante i saldi invernali del 2017\t$850\n1,000 conti\tCaso di applicazione n. 1 riportato di seguito — divieto di commercio\t$5,000\n5,000 conti non verificato\tBilancia per operatori riportati nell'ambito della presente indagine e non verificati in modo indipendente — vedi la nota sull’origine dei dati\t$25,000\n10,000 conti non verificato\tBilancia per operatori riportati nell'ambito della presente indagine e non verificati in modo indipendente — vedi la nota sull'approvvigionamento\t$50,000\n\nLe ultime due righe sono le uniche cifre presenti in questa pagina che si basano su una segnalazione non verificata anziché su un documento — sono contrassegnate nella tabella e spiegate in la nota sull'approvvigionamento, e nient'altro qui dipende da essi. La colonna di destra si basa esclusivamente sulla soglia di $5.00 USD pubblicata da Valve e nient'altro. Si tratta di un piano, non si tratta di una stima dei costi di una fattoria né di quanto Valve abbia guadagnato: l’importo non include i giochi, che devono essere acquistati e non possono essere stati ottenuti gratuitamente tramite una promozione, né i circa 15% che il Mercato della Comunità trattiene quando le carte vengono vendute. In questa pagina non viene riportata alcuna cifra relativa alle entrate.\n\nE Valve ha fissato il prezzo di una distribuzione di carte. La sua sezione \"Domande frequenti sulle carte collezionabili\" indica il tasso di conversione del modello free-to-play in dollari:\n\n\"I giochi free-to-play rilasciano carte di gioco in base agli acquisti effettuati all'interno del gioco. Per ogni $9 USD speso (circa) \"A partire dall'inizio della versione beta delle carte collezionabili Steam, riceverai una carta in regalo.\"\n\n— Valve, Steam Domande frequenti sulle carte collezionabili ↗ · verificato parola per parola 2026-09-22\n\nUna carta collezionabile non è un omaggio che fa perdere soldi alla piattaforma. È qualcosa che Valve vende, al prezzo Valve pubblicato — e per cui poi addebita una seconda volta quando la rivende. Ecco perché la descrizione corretta di una “card farm” non è parassita. È acquirente all'ingrosso.\n\nQuanto è grande effettivamente l’oggetto che si sta acquistando\n\nTutto ciò che segue, da questo punto fino alla fine di questa sezione, è frutto di misurazioni, non di dati riportati. Il censimento delle carte si basa sul listino prezzi dei badge pubblicato da Steam Card Exchange; i prezzi dei giochi stessi provengono dall’API del negozio di Valve; le scorte dei bot provengono da una directory pubblica accessibile a chiunque. Tutti e tre i dati sono stati letti su 2026-09-22 e i calcoli sono riportati integralmente in sezione 08.\n\n13,876Giochi con distribuzione di carte\n99,971Tipi di carte distinti\n5 · 6 · 15Carte per set: minimo, mediana, massimo\n$0.74Prezzo mediano di un set completo\n$23,586.57Un pezzo per ogni set in vendita\nQuanto è grande un insieme?\n\n13,876 giochi presenti nel mazzo. Valve ne assegna circa la metà a un singolo account.\n\n0\n1,250\n2,500\n3,750\n5,000\n5\n6\n7\n8\n9\n10\n11\n12\n13\n14\n15\nQuanto costa la licenza\n\nPrezzo di listino degli stessi giochi sul negozio di Steam, in dollari statunitensi.\n\n0\n1,000\n2,000\n3,000\n4,000\n<$1\n$1-3\n$3-5\n$5-10\n$10-20\n$20-40\n$40+\nCosa restituisce l'insieme finito\n\nPrezzo di mercato del set completo degli stessi giochi.\n\n0\n1,500\n3,000\n4,500\n6,000\n<$0.50\n$0.50-1\n$1-2\n$2-5\n$5-10\n$10+\n\nConfrontando il secondo e il terzo grafico, la struttura dell’operazione risulta evidente anche senza ricorrere a calcoli aritmetici: i giochi si concentrano nella fascia delle decine di dollari, mentre i set che ne derivano si concentrano sotto il dollaro. Entrambi rappresentano il conteggio degli stessi 13,876 giochi, sulla stessa unità di misura dell’asse, quindi il confronto avviene tra due valori numerici e non tra due scale diverse.\n\nQuesto è il lato dell’offerta. Il lato della domanda è la parte per cui Valve non ha bisogno di fare pubblicità, poiché è già di dominio pubblico: un unico elenco pubblico di bot per lo scambio di carte riporta Al momento sono disponibili 91 bot con 694,673 set completi in magazzino. Nessun accesso, nessun scraping del marketplace, nessun dato privato: la cifra di magazzino è riportata sulla pagina accanto al nome di ciascun bot.\n\nFai in modo che quella azione diventi l'unica unità che conta in questo contesto. La regola di Valve: \"Nella maggior parte dei giochi verrà distribuito un numero di carte pari a circa la metà del numero totale di carte presenti nel mazzo di quel gioco… Dovrai procurarti l'altra metà del set dagli altri membri della comunità.\" Un solo account non può mai completare una serie giocando. Ne occorrono almeno due, ciascuno in possesso di quel gioco, che esauriscano entrambi la propria quota di drop, utilizzabile una sola volta per partita. I drop non si rigenerano.\n\n694,673Set disponibili, 91 bot pubblici\n3,473,365Carte, con un minimo di 5 carte\n1,389,346Indennità di riduzione consumate, minimo\n2,602Account che possiedono un solo gioco, bot più diffuso\nDove si trovano gli insiemi 694,673\n\nI dodici più grandi tra i 91 bot di carte quotati in borsa, in base al numero di set completi in magazzino. I dieci più grandi possiedono complessivamente 248,115 set — 35.7% di ogni articolo presente sulla bacheca.\n\n0\n11,250\n22,500\n33,750\n45,000\nCard Supply #4 (High)\nN!vq's Leveling (High)\nAlice [BOT] LEVEL-UP RARE SETS\nN!vq's Leveling (Low)\nDisco Lite Level Up\nN!vq's Leveling (Mid)\nbaty131store.net | Level Up\nKitten - Supreme\nArashirn | Level Up\nSH (Junior) Level Up\nDuobot.com - Overstock\nlvlupbot.com - godlike\n\nOgnuna di quelle 1,39 milioni di quote apparteneva a un account che possedeva il gioco, aveva superato la soglia $5.00 e non potrà mai più generare quelle ricompense. Questo è scorte invendute su novantuno bot. Non è un indicatore del mercato; è un indicatore di ciò che rimane dopo il mercato.\n\nL'ultima cifra si riferisce a una suddivisione per categorie, non a un conteggio delle persone. Un bot riporta 14,310 set provenienti da sole 11 partite, quindi almeno una di quelle partite è rappresentata da 1,301 set, il che significa che ci sono almeno 2,602 account distinti che hanno acquistato quella partita. Si tratta del numero minimo consentito dall’aritmetica e riguarda un solo bot su novantuno.\n\nCosa dice e cosa non dice questo pavimento\n\nQuesti bot acquistano carte sia da giocatori normali che da account automatizzati (farm): le tariffe di acquisto da loro pubblicate costituiscono il fulcro della directory. Pertanto, le 1,39 milioni di quote non corrispondono al numero di conti intestati ad aziende agricole. Si tratta di una serie di oggetti ottenibili una volta per account e una volta per partita, che sono stati spesi da qualche parte su Steam e sono finiti, invenduti, nelle scorte commerciali. Che l’account dietro a ciascuno di essi fosse un account di farming o quello di un adolescente che stava completando la propria pagina dei badge, non cambia ciò che Valve ha raccolto: lo sblocco $5.00, la licenza di gioco e una percentuale sul Market per ogni transazione — non 15%, ma 15% oppure i due importi minimi da un centesimo, a seconda di quale dei due sia maggiore, che su una carta il cui prezzo è espresso in centesimi è di gran lunga il più grande. Il calcolo è riportato in la tabella delle tariffe riportata di seguito. Questo è il punto centrale di questa pagina, e non si tratta di una critica nei confronti degli agricoltori: lo stesso comportamento per cui Valve applica una tariffa è proprio quello che cita, parola per parola, quando esclude definitivamente un utente per “uso commerciale”.\n\nLa cifra rappresenta anche un limite minimo in un secondo senso. Essa tiene conto solo delle azioni che sono in vendita e non venduti oggi sui bot che scegliere di essere presente in una directory pubblica. Sono esclusi tutti gli articoli già venduti, tutti quelli in vendita privata e tutti i bot non presenti nella directory.\n\nE l'agricoltura non è redditizia ai prezzi di Valve\n\nL'obiezione più ovvia è che una “farm” acquisti giochi a basso costo per coniare carte costose. L'API dello stesso negozio di Steam smentisce questa ipotesi. Dei 13,876 giochi contenenti carte, i prezzi sono stati determinati per 13,713; 12,918 sono titoli a pagamento con un prezzo di listino mediano pari a $9.99. Il prezzo mediano di vendita di un set completo è di $0.74. Sono necessarie due licenze per ogni set. Pertanto, il costo mediano di un set è di circa $19.98 licenze di gioco per la produzione e resi $0.74.\n\nMisurato su 2026-09-22\tValore\tCosa stabilisce\nPrezzo medio di listino, gioco con carte\t$9.99\tLa licenza è la parte più costosa della transazione, non la carta\nGiochi con un prezzo pari o inferiore a $4.99\t3,665 (28.4%)\tAnche la coda più economica costa più del gruppo che ne deriva\nIl gioco con le carte più economico disponibile nello store\t$0.99\tDue licenze, $1.98, per un set che in genere viene venduto a meno di $1.30\nGiochi il cui cofanetto costa più del gioco stesso\t323 di 12,918 (2.5%)\tIn 1 partita su 40 si verifica un arbitraggio sulle carte rispetto ai prezzi di listino di Steam\nTitoli free-to-play presenti nel censimento\t795\tE Valve fissa il prezzo di ciascuna delle proprie offerte a $9 di spesa in-game\n\nIl che chiude la questione economica a favore di Valve e contro la versione comunemente accettata. Ai prezzi praticati dalla stessa Valve, Il \"card farming\" è un'attività in perdita che funziona solo con licenze acquistate a un prezzo inferiore a quello di listino indicato da Steam — pacchetti, prezzi regionali, rivendita chiave. Le carte sono il residuo. L’acquisto è l’evento. E l’acquisto è avvenuto il Steam.\n\nCosa sostiene effettivamente l’azienda agricola\n\nMettendo insieme i pezzi, l’azienda agricola smette di apparire come qualcosa che Valve tollera e inizia a sembrare qualcosa di cui Valve ha bisogno. Ogni input fornito dall’azienda agricola è un output che Valve riporta o fattura. Segui l’attività di un account bot verso l’esterno:\n\nUn account creato artificialmenteun \"cliente all'ingrosso\", non una fuga di notizie\nVendite di videogiochi\n\nAcquista i titoli che coltiva — dai giochi di carte 13,876 ai giochi di scarsa qualità $0.50 — perché le carte si ottengono solo dai giochi che possiede.\n\n\"Online\" e tempo libero\n\nLi mette in inattività affinché rilascino carte, alimentando così i dati relativi ai giocatori contemporanei e alle ore giocate che Valve cita come indicatori di coinvolgimento — la statistica esatta che il § 4.C definisce “tempo di gioco fittizio”.\n\nIscrizioni\n\nÈ necessario superare il limite di $5.00 per il conto limitato prima di poter ricevere una carta: per ogni conto vengono registrati Valve acquisti effettuati in negozio.\n\nDenaro nel portafoglio e commissioni\n\nOgni carta venduta passa attraverso il Market, dove la commissione arriva fino a 66.7% per una carta di basso valore e i proventi rimangono bloccati nel Wallet Steam.\n\nComunicato stampa di livello 0\n\nI badge e le classifiche Valve esistono solo perché sono stati creati dei set — e i primi posti di quella classifica sono occupati da bot (vedi § 03).\n\nSe si rimuove la fattoria, tutti i numeri sopra indicati diminuiscono — il gioco ha venduto meno copie, la componente “online” era più limitata, l’account non è mai stato registrato, il canone non è mai stato addebitato e il livello non è mai stato raggiunto. Ecco perché una regola che vieta l’automazione coesiste con milioni di account automatizzati: il divieto è l’opzione, mentre l’attività è la fonte di guadagno.\n\nE il prelievo stesso rappresenta una perdita di valore Valve: si pagano le tasse due volte\n\nLa carta non è la fine del ciclo. Le meccaniche proprie di Valve consentono a una carta di essere schiacciata in gemme, e le gemme vanno utilizzate per creare bustine di carte — altre tre carte — che vengono vendute o distrutte nuovamente. Ogni passaggio corrisponde a una transazione di mercato o a una conversione, e ciascuna è soggetta a tassazione. La direzione di tale ciclo deriva dalla soglia minima delle commissioni indicata di seguito e non richiede alcun modello esterno: ogni carta venduta al suo interno cede almeno due centesimi, su carte che vengono scambiate a un prezzo compreso tra tre e cinque, per cui ogni giro della manovella restituisce meno di quanto è stato investito. Il circolo vizioso distrugge il valore virtuale e costringe a effettuare nuove transazioni, soggette a commissioni, per sostituirlo. In questa sede non viene fornita alcuna stima dell’entità di tale perdita — il rendimento per set dipende dai tassi di ottenimento delle gemme e dalle probabilità dei booster, che questa indagine non ha misurato.\n\nCarta collezionabileoggetti ottenuti nel gioco\n→\nGioiellicarta distrutta, commissione addebitata\n→\nConfezione di espansionegemme utilizzate per la creazione\n→\n3 nuove cartevenduto su Market, commissione addebitata\n↶\n\nQui vengono descritte solo le meccaniche, che sono quelle proprie di Valve: le carte si trasformano in gemme, con le gemme si creano i booster, dai booster si ottengono le carte; ciascuna di queste operazioni è documentata nella FAQ sulle carte collezionabili di Steam e ogni passaggio costituisce un evento di Mercato soggetto a tassazione. Origine delle meccaniche del ciclo: Valve, Steam Domande frequenti sulle carte collezionabili ↗.\n\nNon si tratta di un fenomeno passeggero. È un settore che vanta una solida tradizione pluriennale.\n\nUn singolo istantaneo potrebbe essere un caso fortuito. Pertanto, la directory pubblica dei bot delle carte è stata consultata una volta per ogni vendita stagionale Steam, risalendo indietro nel tempo tramite Wayback Machine, dal 2022 al 2026: le scorte fisse che i bot avevano a disposizione e gli stessi account, vendita dopo vendita. L’economia non appare e scompare; persiste, con un nucleo stabile di operatori, e ha raggiunto il picco a oltre tre milioni di set completi disponibili a magazzino durante i saldi invernali del 2023 — circa un terzo di milione di chiavi TF2 di valore conservate in un unico momento, in un'unica cartella.\n\nSet completi di carte presenti nella directory pubblica dei bot, in vendita a Steam\n\nUn'istantanea di Wayback relativa a steam.supply/CardBots per ogni vendita stagionale. Passa il mouse per visualizzare il valore in chiavi TF2 al tasso di quella istantanea.\n\n0.0M\n0.9M\n1.8M\n2.6M\n3.5M\nA’22\nS’23\nW’23\nS’24\nW’24\nS’25\nS’26\n401Account bot distinti rilevati in tutte le vendite\n59Presente in almeno 5 delle 7 vendite: il nucleo stabile\n16Presente in tutte e 7 le vendite, dal 2022 al 2026\n3,22 milioniSet Peak disponibili in magazzino (inverno 2023) ≈ da 0k a 790k in chiavi\nCome appare la classifica dei badge di una vendita vista dall'alto\n\nLa domanda corrisponde all’offerta. Sul mercato pubblico Classifica dei badge dei saldi estivi 2024 archiviato 2026-07-16 ↗, l'account numero uno aveva creato il badge di vendita 1,740,645 volte — 1,74 milioni di set da dieci carte, 17,4 milioni di carte integrati in un unico elemento decorativo. Al prezzo di mercato della vendita ($0.50 a set), ovvero ~$870,000 del valore della carta; acquistata così come viene effettivamente acquistata — chiavi di TF2 scambiate per far salire di livello i bot a circa 7,6 set per chiave — è ~229,000 tasti, circa $410,000–$570,000 in termini reali. Il conto numero due: 552,000 set, ~$130,000–181,000. Nessun essere umano gioca per questo. Viene acquistato, e ogni fase dell’acquisto è una transazione che Valve compensa.\n\nMetodo e limiti: il set-stock viene calcolato sommando i valori riportati per ciascun bot in ogni snapshot; il numero Il numero di bot per snapshot non è comparabile tra le diverse vendite, poiché alcuni snapshot mostrano solo i bot in evidenza e altri l'elenco completo; pertanto, il numero di bot viene considerato come un valore minimo di ciò che era visibile, non come un censimento. I valori delle chiavi utilizzano il tasso mediano di set pubblicizzati per chiave di ciascuna istantanea e una chiave TF2 compresa tra $1.79 e $2.49. La persistenza è garantita dallo SteamID64 tra le diverse istantanee. Le istantanee del 2021 utilizzavano un layout di pagina precedente e non sono state incluse. Dati: cronologia-economia-agricola.json; livelli dei badge da SteamLadder; prezzi fissi da Steam Card Exchange (istantanee di Wayback al momento della vendita, $0.05 per carta).\n\nE quella stessa flotta è presente anche quando non ci sono offerte in corso\n\nLe due immagini qui sopra non rappresentano due popolazioni. Si tratta di un’unica flotta, fotografata in momenti diversi. La directory indicata all’inizio di questa sezione è stata letta su un una giornata normale in cui non ci sono saldi stagionali in corso — 2026-09-22 — e anche a riposo rimaneva 91 bot e 694,673 set completi: dell'ordine di 186,000 tasti TF2, $334,000–$464,000 del valore della carta, inattivi tra una vendita e l'altra. È il livello minimo di attività che l'azienda mantiene quando non c'è nulla in corso.\n\nEd è la stessa operazione. Abbinata a SteamID64, 87 di quei 91 bot inattivi — 96% — compaiono anche nelle sette istantanee delle vendite riportate sopra, sedici in ognuna di esse. L'elenco non è una bancarella che apre per la vendita e poi chiude; è un inventario commerciale permanente che questa stessa flotta ha ampliato fino a 3,22 milioni di set al picco dell'inverno 2023 e non scende mai a zero. Una svendita è quando si vende. Esiste anche durante il resto dell'anno.\n\nLa directory di riposo, bot per bot\n\nOgni quadrato rappresenta un bot presente nella directory su 2026-09-22, evidenziato se compare anche nelle sette istantanee delle vendite. 91 è il numero riportato nell'elenco quel giorno, non la dimensione della flotta — Nelle istantanee delle vendite compaiono 401 account distinti, e l'elenco mostra una selezione diversa a seconda dei giorni.\n\nVisto nelle aste precedenti (87) Novità rispetto all'ultimo snapshot (4)\n\nIl valore di riferimento non in promozione è 2026-09-22 dalla stessa directory pubblica, senza login. Il valore di riposo utilizza la frequenza di set per chiave pubblicizzata da ciascun bot e la fascia di chiavi $1.79–$2.49 superiore. La sovrapposizione viene calcolata in base allo SteamID64 rispetto alle sette istantanee relative alle offerte. Poiché l’elenco dei prodotti in evidenza differisce da quello completo a seconda dell’istantanea, questo confronto verte sulle scorte e sull’identità, non sul numero di utenti. Calcoli in sezione 08.\n\n03 — La scala\nL'altro prodotto è il numero che compare accanto al tuo nome\n\nLe carte sono la materia prima. Il prodotto finito è di livello Steam, e Valve ne stabilisce il prezzo per set.\n\n100Steam Livello\nLivello di riferimento — trascina o usa i tasti freccia\nPrezzo di un set completo, USD\n\n$0.20 è il set completo più economico presente nel censimento, $0.74 è la mediana, $1.70 è la media. La cifra si riferisce esclusivamente alle carte, mai agli sblocchi $5.00 né alle licenze di gioco.\n\n55,000È richiesto XP\n550Set completi consumati\n110Giochi da possedere, da coltivare da soli\n$407.00Costo delle carte a quel prezzo\n1,100Indennità per la rottamazione, importo minimo\n$5,500.00$5.00 si sblocca, se non viene riutilizzato alcun account\nSet completi consumati, dal livello 1 a 1,000\n\nUn oggetto artigianale = un set completo = 100 XP. Ogni livello all’interno di una fascia di dieci costa 100 XP in più rispetto alla fascia immediatamente inferiore.\n\n0\n12,625\n25,250\n37,875\n50,500\n1\n250\n500\n750\n1000\n667\n550 sets\n\nUn livello non è un elemento decorativo che Valve lascia da parte. È integrato nell'account. Dalla FAQ sulle carte collezionabili di Valve, riguardo a ciò che si ottiene creando un badge: \"100 XP, che potrebbero farti salire di Steam livello. Se il tuo livello Steam aumenta, il limite massimo del numero di amici nella tua lista aumenterà di cinque, e potresti sbloccare la possibilità di personalizzare il tuo profilo con delle vetrine.\" E per quanto riguarda le bustine: \"Il tuo livello Steam aumenta la probabilità di ottenere una bustina: Livello 10: +20%… Livello 50: +100% di aumento della probabilità (ovvero, la probabilità è raddoppiata).\"\n\nQuindi il livello determina due aspetti: Valve il numero di persone con cui puoi essere amico e la velocità con cui le carte gratuite entrano nel tuo inventario. Il secondo aspetto è cumulativo: più set hai consumato, più velocemente la piattaforma ti fornisce altro materiale. Valve ha integrato il ciclo di reinvestimento nel prodotto.\n\nIl tasso di cambio è fisso e viene pubblicato. La creazione di un distintivo richiede un set completo e frutta 100 XP; \"È possibile creare un set per lo stesso gioco al massimo cinque volte.\" Il costo in XP di un livello aumenta ogni dieci livelli. Ne risultano i seguenti valori, e nessuna di queste cifre è approssimativa:\n\nSteam Livello\tSet completi che consuma\tGiochi che devi avere per poterli creare da solo\tAl livello più basso mai registrato ($0.20)\tNel set mediano ($0.74)\tScala\n10\t10\t2\t$2.00\t$7.40\t\n50\t150\t30\t$30.00\t$111.00\t\n100\t550\t110\t$110.00\t$407.00\t\n200\t2,100\t420\t$420.00\t$1,554.00\t\n500\t12,750\t2,550\t$2,550.00\t$9,435.00\t\n667\t22,579\t4,516\t$4,515.80\t$16,708.46\t\n\n667 non è un valore ipotetico. È il livello più alto che un singolo bot presente nella directory pubblica dichiara di poter far raggiungere a un cliente, tra i 33,359 set che possiede in 6,117 giochi. La quarta colonna riporta lo stesso prezzo in base al set completo più economico presente nel censimento; la quinta, rispetto alla mediana. Entrambi sono prezzi di mercato relativi esclusivamente alle carte ed escludono completamente lo sblocco $5.00 e le licenze dei giochi.\n\nCome è stata verificata la curva, dato che Valve non la pubblica\n\nValve indica la percentuale di badge (\"Ogni 100 XP ottieni un livello in più Steam\") e poi effettua un'operazione di copertura — \"(almeno all'inizio)\" — senza pubblicare l'escalation. La curva utilizzata sopra è quella standard, in cui ogni livello all’interno di un blocco di dieci costa 100 XP in più rispetto al blocco sottostante. È stata verificata confrontandola con la directory anziché basarsi su ipotesi: per ogni bot il cui massimo pubblicizzato è limitato dal proprio stock anziché dal limite di cinque creazioni per partita, il livello calcolato da questa curva corrisponde esattamente al livello indicato dal bot — 541 contro 541, 494 contro 494, 464 contro 464. Laddove invece il limite massimo entra in gioco, il valore calcolato risulta di qualche livello superiore, proprio come dovrebbe avvenire per un limite massimo che dipende anche dalla profondità del roster per ogni partita. Non viene avanzata alcuna affermazione riguardo alla curva al di sopra del livello 667.\n\nLeggendo la tabella accanto alla sezione 02, si intravede la struttura dell’attività. Per portare un account al livello 500, qualcuno deve assemblare 12,750 set completi. Ciascuno di questi set ha richiesto almeno le quote di drop di due account, ciascuno dei quali aveva superato il traguardo $5.00 e possedeva il gioco. Un numero di vanità nella parte superiore di un profilo si basa su almeno 25,500 quote di drop spese che si trovano al di sotto di esso. Valve non perderà quell’operazione. Valve è la controparte di ogni sua componente.\n\n04 — Le statistiche\nLa clausola non descrive l'agricoltura in modo vago, ma ne elenca le attività.\n\nIl § 4.C non è una disposizione generale contro i bot. Gli esempi elencati vi indicano, uno dopo l’altro, le due cose che una “card farm” produce.\n\n\"Non è consentito utilizzare in alcun modo script, bot, macro o altri sistemi non controllati dall'uomo (\"Automazione\") per interagire con i Contenuti e i Servizi su Steam, inclusi, a titolo esemplificativo ma non esaustivo:\n\nAutomatizzare il processo di creazione dell'account Steam,\nFalsificare le statistiche di gioco (ad esempio, gonfiare il numero di vittorie o sconfitte, l'XP, il tempo di gioco),\nOttenere ricompense o progredire senza un contributo effettivo da parte degli utenti,\n\"Partecipare a sistemi di valutazione (come le revisioni tra pari o l’'overwatch') attraverso mezzi automatizzati, ivi compresa l’influenza sui risultati o la segnalazione degli utenti mediante azioni predefinite anziché un giudizio informato.\"\n— Steam Contratto di abbonamento § 4.C ↗ archiviato 2026-09-24 ↗ · tratto e citato alla lettera 2026-09-22\n\"…il momento del gioco\"\n\nLe ore di inattività non sono ore fantasma. La sezione FAQ dell’ASF risponde alla domanda in modo diretto — \"Perché il tempo di gioco dei titoli ottenuti tramite ASF non aumenta?\" — con: \"Sì, ma non in tempo reale. Steam registra il tempo di gioco a intervalli fissi e programma l'aggiornamento di questi dati… di solito viene aggiornato ogni 30 minuti circa.\"\n\nTali ore vengono registrate nei dati di Valve, sulle pagine del negozio di Valve e nei conteggi dei giocatori simultanei che Valve pubblica autonomamente Steam Grafici ↗ archiviato 2026-09-23 ↗. In tali dati, un account inattivo è indistinguibile da uno attivo. I dati relativi al coinvolgimento che la piattaforma comunica all'esterno sono calcolati su un campione che include, secondo le regole della piattaforma stessa, anche gli account inattivi.\n\n\"…senza un contributo concreto da parte degli utenti\"\n\nQuesta è una definizione di “idled card drop”, redatta da Valve. È anche una definizione del Livello Steam, del badge, dei requisiti per ottenere le buste di espansione e dei punti esperienza (XP) del profilo ad esso associati — la FAQ dell’ASF conferma questa interpretazione \"mantiene la possibilità di ricevere buste di espansione\", poiché effettua l'accesso allo stesso modo del client ufficiale.\n\nQuindi il sistema di ricompense e l’atto proibito costituiscono un unico meccanismo visto da due prospettive diverse. Valve ha concepito la ricompensa come qualcosa che si ottiene in base al tempo impiegato piuttosto che all’abilità, quindi ha inserito una clausola che vieta la produzione di ricompense se non da parte di una persona che dedichi effettivamente quel tempo.\n\n05 — La trappola dell'uso commerciale\nOgni uscita da una carta emessa da un operatore è un’uscita vietata dalla licenza — e Valve applica una tariffa all’uscita\n\nQuesta è la parte che non può essere risolta praticando il \"farming\" in modo \"responsabile\". La licenza è per uso personale e non commerciale, e una carta diventa redditizia solo nel momento in cui smette di essere personale.\n\n§ 2.A — la licenza\n\n\"Valve concede con la presente, e tu accetti, una licenza e un diritto non esclusivi di utilizzare i Contenuti e i Servizi per il tuo uso personale e non commerciale (salvo nei casi in cui l'uso commerciale sia espressamente consentito nel presente documento o nelle Condizioni di abbonamento applicabili).\"\n\n§ 2.G — la restrizione\n\n\"Non hai diritto a: … (iii) sfruttare i Contenuti e i Servizi, o qualsiasi parte di essi, per qualsiasi scopo commerciale, salvo quanto espressamente consentito in altre parti del presente Contratto (comprese eventuali Condizioni di abbonamento o Norme d’uso).\"\n\n§ 3.D — la tariffa\n\n\"Valve può applicare una commissione sulle transazioni effettuate nel Marketplace degli abbonamenti. \"Eventuali commissioni vi saranno comunicate prima del completamento della transazione.\"\n\nSe si leggono tutti e tre insieme, la posizione si chiude\n\nUna carta che viene conservata non ha alcun valore per una fattoria. Una carta che viene venduta, scambiata o trasformata in gemme è stata utilizzata per generare valore — e Valve ha spiegato nella propria lettera di avviso cosa intende con questo: al gestore di 170 bot è stato comunicato che l'account \"è stato utilizzato per raccogliere illegalmente carte da collezione su Steam, nonché per svolgere attività correlate, non solo di natura commerciale.\" In quel caso le carte sono state immesse sul mercato. Le vendite sono andate a buon fine. La commissione è stata incassata. Il divieto è arrivato in seguito.\n\nIl costo all’ingresso non è 15%. Su una carta in affitto arriva a due terzi.\n\n§ 3.D Riserve \"una commissione\". Sulle carte che un’azienda agricola produce effettivamente, quella commissione non ha nulla a che vedere con il ~15% pubblicizzato. Il Mercato Comunitario richiede un 5% Steam commissione di transazione e una 10% quota di partecipazione al gioco, ciascuna con un importo minimo di $0.01 (Domande frequenti sul Community Market di Valve). Su una carta in vendita a un centesimo, quei livelli sono il prezzo: l'acquirente paga tre centesimi, due dei quali sono commissioni. L'arrotondamento per difetto trasforma il valore nominale 15% in un prelievo effettivo che sale a 66.7% proprio dove si muove il mercato delle figurine: pochi centesimi a figurina.\n\nCommissione effettiva su una vendita sul Mercato Comunitario, in base al prezzo richiesto dal venditore\n\n5% Steam + 10% partite, ciascuna con un minimo di $0.01. La fascia ombreggiata indica il range effettivo in cui avvengono gli scambi di figurine: all’incirca da $0.03 a $0.05 figurine.\n\n0%\n10%\n20%\n30%\n40%\n50%\n60%\n70%\ncards\n$0.01\n$0.10\n$0.20\n$0.30\n$0.40\n$0.50\n66.7%\nIl venditore desidera\tSteam 5% (min $0.01)\tPartita 10% (min $0.01)\tLe spese sono a carico dell'acquirente\tTariffa combinata\n$0.01\t$0.01\t$0.01\t$0.03\t66.7%\n$0.03\t$0.01\t$0.01\t$0.05\t40.0%\n$0.05\t$0.01\t$0.01\t$0.07\t28.6%\n$0.08\t$0.01\t$0.01\t$0.10\t20.0%\n$1.00\t$0.05\t$0.10\t$1.15\t13.0%\n\nLa commissione di 10% va all’app che ha emesso la carta; il 5% spetta a Valve, mentre sui titoli di proprietà di Valve e sugli articoli dell’inventario di base l’intera commissione va a Valve. In entrambi i casi il denaro esce dalle tasche del «farmer»: la vendita di una carta da tre centesimi frutta un centesimo e ne fa perdere due. Moltiplicate questo per le centinaia di migliaia di vendite di carte da meno di cinque centesimi generate da un «farmer» e \"la commissione che Valve può addebitare\" è il modello di business, non una nota a piè di pagina. Fonte: Steam Domande frequenti sul Mercato della comunità — Commissioni ↗ archiviato 2026-09-21 ↗, si legga 2026-09-22; la curva è aritmetica rispetto a quei due tassi pubblicati e ai loro livelli minimi $0.01.\n\nNon esiste alcuna configurazione dello strumento che permetta di eludere questa regola. Lo strumento può essere gestito da una sola persona, su un unico account, con la massima moderazione — e nel momento in cui quella persona vende una sola carta ottenuta tramite farming in cambio di fondi nel proprio portafoglio, la stessa sanzione prevista dal § 2.G si applica a lei così come si applica a chi ne gestisce diecimila. Valve si è quindi riservata il diritto di invocare una violazione contro praticamente ogni venditore di carte sul proprio mercato, ma ha deciso di non farlo nei confronti di praticamente nessuno di loro. Una regola applicata in quel modo non è una regola. È una scelta. La domanda che questa mostra pone non è perché i “card farmer” vengano tollerati; ma perché la stessa misura venga applicata nei confronti di un singolo utente che vende una carta, mentre l’economia commerciale delle carte che queste alimentano — i servizi di scambio, i bot per salire di livello, i venditori all’ingrosso — opera alla luce del sole, con uno dei suoi gruppi più grandi moderato da un dipendente Valve (§ 08). La violazione è riservata al piccolo possessore e ignorata per la macchina.\n\n06 — Il bilancio delle azioni di contrasto\nSenza preavviso, a ondate, e si diffonde lungo la catena di numeri di telefono\n\nValve ha inserito la facoltà di recesso senza preavviso direttamente nel contratto stesso, in una clausola che segue quella relativa all’automazione.\n\n\"Valve può limitare o chiudere il tuo account o i tuoi account, oppure un determinato abbonamento, a seguito di qualsiasi comportamento o attività illegale, che costituisca una forma di frode o automazione, o che violi le Regole di condotta online di cui al punto Steam. L'utente riconosce che Valve non è tenuta a fornirgli alcun preavviso prima di rescindere il/i suo/i Abbonamento/i e/o il suo Account.\"\n\n— Steam Contratto di abbonamento § 4.D ↗ archiviato 2026-09-24 ↗ · verificato alla lettera 2026-09-22\n\n1,000+ bot · accesso al trading bloccato. \"Sembra che questo account sia stato utilizzato per gestire una rete di account bot. L'uso di bot costituisce una violazione del Contratto con l'abbonato Steam.\"\n\nOltre 170 bot · banditi definitivamente, Saldi invernali 2017. \"Questo account è stato utilizzato per raccogliere illegalmente carte da collezione su Steam, nonché per svolgere attività correlate, non solo di natura commerciale. L'account è stato bloccato in modo definitivo e l'assistenza di Steam non può fornire ulteriore supporto in merito a questa questione.\"\n\nOltre 120 bot · banditi definitivamente. \"Questo e altri account sono stati utilizzati per sovraccaricare la nostra infrastruttura di rete, il che costituisce una violazione delle Steam norme di comportamento online.\"\n\n— Steam Messaggi di supporto riportati nella ArchiSteamFarm sezione delle FAQ, alla voce \"Qualcuno è stato bannato per questo?\". Fonte ↗ · verificato alla lettera 2026-09-22\nCaso 4 — giugno 2025, VAC divieti relativi al CS2 inattivo\n\nUn episodio successivo rispetto ai tre sopra citati è stato registrato nel tracker del progetto stesso: gli account che avevano semplicemente lasciato inattivo Counter-Strike 2 tramite lo strumento hanno ricevuto VAC divieti — quello relativo agli anti-cheat, non quello amministrativo. La posizione del responsabile è che il funzionamento al minimo non possa causarne uno, poiché \"Non fa altro che comunicare a Steam che stiamo giocando a un determinato gioco.\" La causa è oggetto di controversia. Il fatto che gli account siano stati bloccati, invece, non lo è.\n\n— ArchiSteamFarm discussione n. 3440, aperta il 26 giugno 2025 ↗ · leggi 2026-09-22\n\nCome muore un account principale\n\nNello stesso thread, un collaboratore del progetto descrive la regola di diffusione: gli account possono essere bannati \"in serie\", se utilizzano lo stesso numero di telefono — \"Potrebbe trattarsi semplicemente di un blocco VAC, esteso agli account 'puliti' collegati a quello bloccato.\"\n\nSteam Guard richiede un numero di telefono. Le “farm” vengono create utilizzando il numero di telefono dell’operatore. Pertanto, l’azione di contrasto non si limita agli account usa e getta: risale lungo l’identificatore condiviso fino all’account che contiene la libreria, la lista degli amici e l’inventario. Questo è il meccanismo descritto da un collaboratore del progetto per spiegare come una singola azione elimini l’account principale di un operatore insieme alla “farm” — ed è il motivo per cui la perdita in un’ondata di misure di contrasto non si misura in $5 account. (Descritto da un collaboratore del progetto nella discussione ASF su GitHub n. 3440; non vi è alcuna conferma ufficiale Valve né alcun precedente formale documentato.)\n\nLo stesso paragrafo, a distanza di cinque anni, da tre agenti diversi\n\nLa clausola che qualifica l'attività agricola come violazione — ovvero l'uso commerciale di una licenza personale e non commerciale — non è riservata alle aziende agricole. È la motivazione standard che Steam fornisce quando chiude un account per attività di trading, e tale motivazione viene fornita sotto forma di modello predefinito. Di seguito sono riportati tre esempi, pubblicati dalle persone che li hanno ricevuti, a distanza di cinque anni l’uno dall’altro, da tre diversi agenti identificati.\n\nMessaggio dal supporto Steam il 29 settembre alle 19:56\n\n\"L'account da cui stai scrivendo è stato bloccato per violazione dei termini del Contratto di abbonamento Steam. L'account è stato identificato come utilizzato per scopi commerciali sulla base delle attività di trading, delle segnalazioni della comunità e di altri fattori.\n\nQuesto blocco è permanente e Steam Il servizio di assistenza non può fornirti ulteriore aiuto in merito.\n\nPoiché ti abbiamo fornito tutte le informazioni in nostro possesso, chiudo questa richiesta di assistenza. Ti ricordiamo che non riceverai ulteriori risposte in merito a questo problema.\n\nCordiali saluti,\n\"Hal\"\n\nQuesta richiesta di assistenza è stata chiusa.\n29 settembre 2020. Pubblicato dal destinatario con il seguente commento \"Addio, RIP Trading.\" — @gergelyszabo94 ↗\nMessaggio dell'assistenza Steam il 12 luglio alle 22:41\n\n\"L'account da cui stai scrivendo è stato bloccato per violazione dei termini del Contratto di abbonamento Steam. L'account è stato identificato come utilizzato per scopi commerciali sulla base delle attività di trading, delle segnalazioni della comunità e di altri fattori.\n\nQuesto blocco è permanente e Steam Il servizio di assistenza non può fornirti ulteriore aiuto in merito.\n\nPoiché abbiamo fornito tutte le informazioni in nostro possesso, chiudo questa richiesta di assistenza. Si prega di notare che eventuali future richieste di assistenza relative al blocco dell'account potrebbero essere chiuse senza risposta.\n\nSteam Assistenza\n\"Vido\"\n\nQuesta richiesta di aiuto è stata chiusa.\n12 luglio 2024, interfaccia in portoghese. Il destinatario è un giocatore professionista di CS2: \"Ho già contattato l'assistenza di Steam, ma ricevo solo risposte automatiche… Non riesco a giocare su Faceit e non posso nemmeno partecipare alle partite professionistiche.\" — @prcs25 ↗ archiviato 2024-07-15 ↗\nCitato dal destinatario, r/steamsupport\n\n\"Salve, l'account da cui sta scrivendo è stato bloccato per aver violato i termini del Contratto di abbonamento Steam. L'account è stato identificato come utilizzato a fini commerciali sulla base delle attività di trading, delle segnalazioni della comunità e di altri fattori.\n\nQuesto blocco è permanente e Steam Il servizio di assistenza non può fornirti ulteriore aiuto in merito.\n\nPoiché abbiamo fornito tutte le informazioni in nostro possesso, chiudo questa richiesta di assistenza. Si prega di tenere presente che eventuali future richieste di assistenza relative al blocco dell'account potrebbero essere chiuse senza risposta.\n\nSteam Assistenza\n\"Sally\"\n\nRicevuto tre volte, in seguito a tre richieste distinte.\n29 marzo 2025. L'autore non stava contestando il blocco: il suo account era stato rubato insieme alla sua e-mail e stava chiedendo di poter accedere: \"Non sto chiedendo informazioni sul ban e non lo sto contestando, voglio solo poter accedere al mio account Steam… Valve mi hanno dato esattamente questa risposta, copiata e incollata, a ogni richiesta, e poi hanno chiuso la segnalazione.\" — r/steamsupport ↗, contenuto nel corpus di denunce della presente indagine\n\nParola per parola, virgola per virgola, nell’arco di cinquantacinque mesi, con tre agenti e due lingue di interfaccia. L’unica modifica apportata in tutto il testo riguarda l’ultima frase, in cui l’intervallo temporale è stato modificato da 2020 a 2024, passando da \"Non riceverai altre risposte\" a \"Le future richieste di assistenza… potrebbero essere chiuse senza risposta.\" Qualunque sia stato il processo che ha portato a queste decisioni, la lettera non ne costituisce una traccia. I motivi addotti sono “attività commerciali, segnalazioni della comunità e altri fattori”: una categoria, una segnalazione di origine sconosciuta e una serie di altri elementi non specificati.\n\nAltri cinque casi, raccolti allo stesso modo. I primi tre appartengono alla stessa categoria e presentano lo stesso esito; gli ultimi due provengono dallo stesso ufficio e rispondono a una norma diversa, espressa con le stesse parole:\n\nData\tCosa ha fatto l'account\tCosa è successo\tFonte\n4 dicembre 2021\tAcquistare e vendere su Buff — \"Non ho fatto altro che comprare e vendere su Buff, ovvero fare trading P2P\"\tSospensione dalla community: nessun mercato, nessuna transazione, scorte costose bloccate\tr/csgomarketforum ↗ archiviato 2025-03-27 ↗\n06/12/2021\tScambi P2P a senso unico tramite Buff e Bitskins per equipaggiamenti e aggiornamenti\tSerratura permanente per uso commerciale più serratura comune: \"Bloccato in una sorta di modalità invisibile… Anche il mio profilo è bloccato in modalità privata\"\tr/GlobalOffensiveTrade ↗ archiviato 2021-12-06 ↗\n20 dicembre 2024\tAccount attivo dal 2017, migliaia di ore; scambi su piattaforme comunitarie per equipaggiamenti a tema e aggiornamenti\tBlocco permanente con blocco comunitario, senza preavviso né avvertenza; supporto \"affermano che la loro decisione è definitiva\", le risposte sono automatiche\tr/csgomarketforum ↗ archiviato 2025-06-27 ↗\n23 dicembre 2024\tUn utente che torna sul sito ricarica il proprio portafoglio dopo un anno di assenza, utilizzando una VPN \"solo per la sicurezza generale su Internet\"\tBando definitivo dalla community con non è stata fornita alcuna motivazione: \"Il divieto è definitivo e non è possibile fornire ulteriori informazioni; inoltre, eventuali altre segnalazioni potrebbero essere archiviate senza risposta.\" 196 voti positivi, 340 risposte\tr/steamsupport ↗\n04/08/2026\tAnni di acquisti dall'Iran; l'autore afferma di non aver mai pubblicato nulla, di non aver mai utilizzato il Market e di non aver mai utilizzato i forum\tAccesso alla community bloccato fino al 2038 oltre \"regioni soggette a sanzioni\"; ticket chiuso da un operatore di nome Azul. Il rimborso relativo allo stesso account, proveniente dallo stesso indirizzo IP iraniano, era stato approvato un anno prima. La biblioteca e il denaro restano a Valve.\tr/pcgaming ↗\n\nL’ultima riga presenta una regola diversa dalle altre — conformità alle sanzioni, non uso commerciale — ed è inclusa perché la struttura della risposta è identica: una categoria, nessuna prova, nessun ricorso, un ticket chiuso. Inoltre solleva una questione che le altre non sollevano. Se era illegale fornire il servizio a quell’account, era illegale accettare i pagamenti effettuati negli anni. Una di queste due posizioni deve essere errata, e solo una delle due comporta un costo per il cliente.\n\nTutte e otto sono state lette su 2026-09-22: i thread del 2021 e del dicembre 2024 tramite istantanee di Internet Archive e il resto tramite un’interfaccia pubblica di Reddit, poiché Reddit ha rifiutato le richieste dirette da parte dell’host incaricato della raccolta. Le due lettere del 2020 e del 2024 sono state trascritte dagli screenshot allegati ai post originali, che sono ancora online. Nessuno di questi account viene considerato da questa indagine innocente o colpevole di alcunché — ed è proprio questo il punto. Né un lettore, né un'autorità di regolamentazione, può capirlo dalla lettera.\n\nNota sull’approvvigionamento — perdite a livello di operatore\n\nGli operatori intervistati nell'ambito di questa indagine segnalano perdite dell'ordine di da cinque a diecimila account ciascuno in singole campagne di controllo, con la verifica dei conti principali effettuata contestualmente a quella dell’azienda agricola. Tale sondaggio è riportato qui come dato fornito dalla fonte stessa, non come risultato. Non presenta una dimensione del campione pubblicata, né una data di raccolta fissa, né una verifica per singolo conto, e nessun altro dato in questa pagina dipende da esso; le due righe nella sezione 02 che si basano su di esso sono contrassegnate come tali.\n\nViene affermato esplicitamente anziché tralasciato per due motivi. Il meccanismo di “chain-ban” sopra descritto è la spiegazione documentata proprio di quel modello. E un'autorità di regolamentazione può richiedere a Valve l'unico dato che risolverebbe la questione: quanti account sono stati oggetto di automazione, in quali ondate, e quanto ciascuno di questi account aveva speso nel negozio prima della chiusura. Finché quel dato non esisterà, la cifra rimarrà così com'è: riportata, attribuita e non provata.\n\n07 — L'asimmetria\nI due lati della stessa scrivania\n\nConfrontate tale standard probatorio con quello Valve applicato alla propria operazione di supporto. La colonna di destra riporta il registro degli incidenti contenuto in questo fascicolo, riprodotto con le riserve ivi riportate.\n\nUn cliente, per operazioni di trading\n\nOtto casi documentati, 2020–2026\n\nComportamento\nVendita o acquisto di articoli su piattaforme di terze parti; in un caso, non si è trattato affatto di un comportamento doloso: l’account era stato rubato.\nProve presentate\nNessuno. \"Sulla base delle transazioni, delle segnalazioni della comunità e di altri fattori.\"\nAvviso\nNessuno. Valve ha precisato che al § 4.D: \"Valve non è tenuta a darti preavviso prima di procedere alla risoluzione.\"\nRicorso\n\"Questo blocco è permanente e Steam l'assistenza non può fornirti ulteriore aiuto in merito.\"\nBiglietto\nChiuso alla prima risposta. Ulteriori richieste \"potrebbe essere chiusa senza risposta.\"\nPortata\nProfilo, elenco degli amici, chat, Market, inventario e tutti gli oggetti acquistati con denaro reale.\nDurata\nPermanente.\nUna flotta di bot automatizzati, per gestire grandi volumi\n\n694,673 set completi disponibili in magazzino pubblico distribuiti su 91 bot\n\nComportamento\nEseguire script automatizzati in modalità headless su migliaia di account contemporaneamente per rendere inattive le carte, creare badge in massa e scambiare set su scala industriale.\nProve presentate\nElenchi di bot pubblicati apertamente (steam.supply, SteamLvlUp) e gruppi pubblici con milioni di membri.\nAvviso\nNessun intervento. 88.97% non comportano alcun tipo di divieto; 99.8% dei divieti rimanenti sono di natura puramente estetica.\nRicorso\nNon è necessario. Le flotte operano ininterrottamente per cicli di vita pluriennali senza interruzioni.\nBiglietto\n—\nPortata\nScambio illimitato di inventario, livellamento dei badge e liquidità del mercato.\nVantaggio per Valve\n$26.8M+ nella spesa minima in negozio ($5.00 punto di accesso per account) più 15% riduzione sulle transazioni nel Community Market.\nLa domanda che ne deriva, in parole povere\n\nUn singolo cliente che scambia manualmente carte o oggetti va incontro a una sospensione permanente e inappellabile ai sensi del § 4.C (automazione) o del § 2.G (uso commerciale). Una rete automatizzata di farming che utilizza bot senza interfaccia utente su migliaia di account opera apertamente con un tasso di intatto pari a 88.97%. Valve ne beneficia di entrambi.\n\nL'asimmetria è di natura economica: i singoli trader traggono valore dalla piattaforma, mentre le flotte di carte automatizzate immettono milioni nel sistema di spesa del negozio di Valve ($5.00 per account) e alimentano le commissioni di transazione su ogni rivendita. L'applicazione delle regole non segue il regolamento scritto, ma il modello di reddito.\n\n08 — Governance\nChi regola l'economia delle carte?\n\nLa constatazione ricorrente di questo dossier — ovvero che il livello di terze parti attorno a Steam è composto da personale proveniente dall’interno di Steam — vale anche nell’economia delle carte, e porta a una conclusione ben precisa: nessuno indipendente può valutare l’effettivo impatto delle misure di Valve, poiché chi è in grado di farlo fa parte di quel livello. Tutti i fatti riportati di seguito sono stati ricavati dal gruppo pubblico e dalle pagine del profilo di Valve su 2026-09-22 e possono essere riprodotti da chiunque tramite un browser.\n\nUn dipendente Valve gestisce il più grande gruppo dedicato allo scambio di figurine Valve dipendente\n\nCardTrades ↗ si descrive, nell'intestazione, come il \"Steam Gruppo ufficiale di scambio di carte\" e comporta 97,114 membri. I moderatori indicati — ovvero gli account che gestiscono il gruppo — sono Mickmane, SgtFopper e afarnsworth ↗.\n\nQuest'ultimo profilo è contrassegnato dal codice del sito stesso di Valve come dipendente Valve — la pagina riporta class=\"profile_header_valve_employee\" — indica la sua posizione come Bellevue, Washington, e appartiene alla Valve, Steam e Steam Gruppo delle figurine gruppi. SteamID64 76561197960434622, membro dal 12 settembre 2003.\n\nL'osservazione è di natura strutturale, non personale, ed è non un punto relativo all'automazione: il moderatore di un gruppo dedicato allo scambio di carte non sta utilizzando un bot, e nulla qui suggerisce il contrario. Il punto è la clausola contenuta in sezione 07. Steam Card Exchange è un servizio di carte commerciali gestito da terze parti; lo scambio di carte tramite servizi di terze parti costituisce proprio il comportamento per cui Valve blocca definitivamente gli account ordinari ai sensi di \"utilizzati a fini commerciali sulla base delle transazioni, delle segnalazioni della comunità e di altri fattori.\" Un dipendente Valve ricopre il ruolo ufficiale di moderatore nel gruppo ufficiale della community di quel servizio, che conta novantasettemila membri.\n\nIn questa sede non viene mossa alcuna accusa di comportamento scorretto nei confronti di alcuna persona, e non viene tratta alcuna conclusione su cosa comporti tale ruolo. L’asimmetria è il dato di fatto: quando un account ordinario entra in contatto con un servizio di carte o skin di terze parti, la risposta è un ticket chiuso e un blocco permanente senza che venga mostrata alcuna prova; quando il servizio è questo, un dipendente Valve figura nell’elenco dei moderatori e l’accordo è visibile su una pagina che Valve stesso pubblica. Ciò che viene chiesto è ciò che viene chiesto ovunque altrove in questo dossier: produrre l’autorizzazione scritta, se esiste — e se non è necessaria, dirlo per iscritto, perché a otto persone della sezione 06 è stato detto il contrario.\n\nIl livello della lista dei ban e chi lo gestisce Moderatore volontarioServizio di terze parti\n\nIl gruppo di Steambans.com (archiviato) ↗ (in diretta ↗ archiviato 2025-12-03 ↗) riporta la propria genealogia nella descrizione del gruppo che è stata conservata: \"Il gruppo ufficiale della community di Steambans.com Steam. SteamBans.com è un servizio nuovissimo basato su un concetto di vecchia data. Le liste di ban globali sono attive da anni sul vecchio programma WONID di VALVe. Quando è avvenuto il passaggio a STEAMID, ci è sembrato naturale sviluppare un servizio pensato appositamente per questo nuovo sistema. Ma volevamo anche di più. *. Pagina di archivio dedicata a Steambans, che ha cessato l'attività nel 2013.\" Tra i suoi amministratori figurano devicenull e killahinstinct_ ↗.\n\nL'account amministratore è non un dipendente Valve — non presenta alcun indicatore di dipendente. Si tratta di un volontario con una posizione di particolare rilievo: un membro di Moderatori della community (414 membri, descritto come un gruppo \"creato dai moderatori della community di Steam\"), di Coordinatori Wiki, di Steam Mercato della comunità, e dei gruppi relativi al programma Valve e alle anteprime, tra cui Valve Conduttura, Steam Versione beta per i clienti, Mobile Auth Beta, Nuova versione beta della community Steam, Steam Laboratori, Steamworks e Segnala gli URL sospetti. SteamID64 76561197960794555.\n\nInoltre, all’interno di quel cerchio e con Steambans visualizzato direttamente nell’elenco dei membri del suo gruppo pubblico: msart ↗ (elenco dei gruppi ↗), SteamID64 76561197977933359, il cui profilo riporta, secondo le sue stesse parole \"Gestisco steamid.uk e molti altri siti, sia legati a Steam che non\", e che gestisce una rete interconnessa di sedici gruppi — SteamIDcouk (gruppo principale \"Sito web di Sid\"), SidAdmins, SidBans, steamideu, Steam3ID, s-id e SArchive tra loro.\n\nsteamid.uk indica proprio quel numero. Nella sua sezione FAQ: \"Chi ha creato SteamID? Il sito web di SteamID, l'infrastruttura di rete e i sistemi di sicurezza sono tutti gestiti da 76561197977933359.\" Due risposte più in basso si spiega da dove provengono i dati: \"SteamID utilizza principalmente l'API Web Steam per la raccolta dei dati.\" La stessa pagina descrive diversi server dedicati distribuiti su vari host, server di sviluppo, archiviazione e ricerca testuale esterni alla sede, nonché una struttura di backup separata.\n\nVerificato tramite documenti conservati nell'Internet Archive: il Panoramica del gruppo Steambans del 3 dicembre 2025 ↗, il Panoramica del profilo dell'operatore al 14 settembre 2024 ↗, e il Panoramica delle FAQ di steamid.uk al 1° aprile 2026 ↗, dati corrispondenti letti direttamente su 2026-09-22.\n\nCosa ne consegue, e cosa no\n\nLe liste di ban, la risoluzione degli SteamID e lo scambio di carte sono i tre servizi che determinano chi è affidabile, chi è identificabile e quale sia il valore di un oggetto. Nessuno dei tre è gestito da Valve. Su ciascuna di esse, le persone ai comandi provenivano dall’orbita di Valve: un dipendente contrassegnato con Valve nell’elenco dei moderatori del gruppo ufficiale del servizio di carte; un moderatore della comunità di lunga data Valve con accesso al programma di pre-rilascio che amministra il gruppo della lista dei bannati; il servizio di risoluzione degli ID gestito da un privato che fa parte della stessa cerchia. Tre servizi, tre livelli di controllo, tre persone Valve a cui era già stata concessa autorità.\n\nL'appartenenza al gruppo non equivale a un rapporto di lavoro, e nulla di tutto ciò costituisce un'accusa. È un dato di fatto in materia di governance, ed è il motivo per cui la solita difesa — Si tratta di soggetti terzi, non possiamo controllarli — deve essere verificato anziché dato per scontato. Chi è ai comandi conosce bene Valve. Valve è nella posizione di dire cosa, se mai qualcosa, abbia chiesto loro; nessuno dall’esterno è in grado di scoprirlo.\n\nNessuno conta. Questa è la conclusione.\n\nLo spazio ID Steam è un intervallo contiguo di numeri interi. Scorrerlo e segnalare quanti account sono stati bannati, quanti sono soggetti a limitazioni e quanta disponibilità si trova dietro un divieto di scambio non è un programma di ricerca: è un ciclo e una chiave API. Valve fornisce direttamente quella chiave, all’indirizzo steamcommunity.com/dev/apikey. Eppure Nessun ente indipendente pubblica quel censimento. Né un'autorità di regolamentazione, né un giornalista, né un accademico, né un'associazione di consumatori. Gli unici dati pubblici relativi alla portata delle misure di applicazione della normativa Steam sono quelli che Valve decide di citare.\n\nLa funzionalità non manca. È semplicemente disattivata. Il servizio che gestisce e indicizza lo spazio degli ID su larga scala — steamid.uk — afferma nelle proprie FAQ che \"utilizza principalmente l'API Web Steam per la raccolta dei dati\" e lo gestisce su più server dedicati, sistemi di archiviazione esterni, macchine per la ricerca testuale e una struttura di backup separata. È gestito da un singolo privato. Il gruppo affine alla sua lista di ban è co-amministrato da un moderatore di lunga data della comunità Valve, che ha accesso ai programmi in anteprima di Valve. L'unico soggetto in grado di pubblicare i dati si trova nell'orbita di Valve, ma non li pubblica.\n\nÈ la stessa struttura che il dossier rileva ovunque. Ogni servizio che prende decisioni determinanti per l’economia Steam — chi è affidabile, chi è identificabile, quale sia il valore di un bene, chi sia escluso — è nominalmente una terza parte e, in pratica, adiacente a Valve. Steam “Card Exchange” non fa eccezione a tale schema; ne è piuttosto un altro esempio. L'argomentazione secondo cui si tratterebbe di operatori indipendenti è valida per Valve proprio perché nessuno è mai riuscito a verificarla confrontandola con un numero.\n\nCensimento dei 10,88 milioni di account: 88.97% Non modificato\n\nLa base installata di ArchiSteamFarm è stata sottoposta a verifica in tutti i Valve GetPlayerBans punto finale (10,880,610 account, 55 minuti). Il solo sottoinsieme non limitato rappresenta $26.8M+ per quanto riguarda la spesa minima in negozio (soglia di accesso pari a $5.00). Gli account 9,680,599 (88.97%) non sono soggetti ad alcun tipo di blocco, mentre 99.8% del resto comportano solo sospensioni dalla community di natura puramente formale, che lasciano attivo il trading automatizzato.\n\n5,360,499Membri ASF senza limitazioni (numero visualizzato di Steam)\n10,880,610Numero totale di voci API analizzate (con limitazioni e senza limitazioni)\n9,680,599Non è mai stato bannato (88.97%)\n1,200,011Applicare un divieto di Steam (11.0%) — 99.8% estetico\n55 minPer effettuare il censimento dell'intera popolazione, un elemento fondamentale\nProve forensi e censimento approfondito\n\nLa ripartizione demografica dettagliata — che comprende grafici sulla distribuzione dei tipi di ban, l'anzianità degli account al momento dell'applicazione della sanzione, i gruppi per anno di creazione (2020–2026) e i dati geografici forniti dagli utenti stessi — è pubblicata nell'indagine dedicata al censimento.\n\nApri il censimento completo dei divieti (10,88 milioni) (Allegato VI) →Sezione 4 — Il blackout dell'ID risorsa →\n\nQuindi la domanda da porre, alla quale solo Valve può rispondere, è: quale identificativo o autorizzazione è stato revocato, in quale data, su decisione di chi e quale effetto misurabile ha avuto sugli operatori a cui era destinato — a fronte delle sue ripercussioni su tutti coloro che, all’esterno, stavano cercando di effettuare il conteggio. Una modifica che pone fine alla revisione contabile indipendente non diventa neutra solo perché è stata annunciata come misura di sicurezza. È proprio questo il motivo per cui il censimento nel blocco sopra indicato non esiste.\n\n09 — Metodo e limiti\nCiò che è stato letto e ciò che non viene rivendicato\n\nTutte le citazioni presenti in questa pagina sono state tratte dalla fonte in tempo reale su 2026-09-22 e riprodotte alla lettera. Nessuna di esse proviene da uno scrape, da credenziali di un marketplace o da un set di dati privato.\n\nI quattro set di dati e le operazioni aritmetiche su di essi\n\nCiascuna di esse è una singola richiesta pubblica, riproducibile da un terminale. Non è stato utilizzato alcun account, non è stato effettuato l'accesso a nessun marketplace e non è stato richiamato alcun endpoint che richiedesse credenziali.\n\nSet di dati\tDa dove proviene\tCosa ne è stato ricavato\nCensimento delle carte\n13,876 partite\tSteam Il listino prezzi dei badge pubblicato da Card Exchange, lo stesso feed che genera i loro pagina dei prezzi al pubblico ↗ archiviato 2026-08-04 ↗\tGiochi che emettono carte, numero di carte per set, tipi di carte distinti e prezzo di mercato di ciascun set completo. Le mediane e il totale $23,586.57 costituiscono i dati aritmetici di questa indagine.\nPrezzi dei giochi\n13,713 risolto\tl'endpoint pubblico dello store di Valve, store.steampowered.com/api/appdetails, cc=us, solo campo prezzo, in lotti\tMediana e distribuzione del prezzo di listino di un gioco con carte; numero di giochi il cui set completo registra vendite superiori a quelle del gioco stesso.\nScorte di bot\n91 bot, 694,673 set\tL'elenco pubblico dei card-bot all'indirizzo steam.supply/CardBots ↗, da leggere così come visualizzato, senza effettuare l'accesso\tNumero totale di set disponibili, numero minimo di carte, soglia minima di consegna e soglia minima per bot su account distinti.\nVerifica incrociata\n21 bot condivisi\tsteamlvlup.net/cardbots ↗ archiviato 2026-02-10 ↗, un elenco indipendente degli stessi bot\tSolo a scopo di verifica. Per i 21 bot presenti in entrambi gli elenchi, lo stock aggregato concorda con 0.03%; la discrepanza più ampia tra i singoli bot è pari a 1.36%, in linea con due scansioni dell'inventario in tempo reale effettuate a pochi minuti di distanza l'una dall'altra.\n\nAttribuzione, come richiesto dalla seconda directory: dati forniti da SteamLvlUp, con licenza CC BY 4.0 archiviato 2026-09-23 ↗; utilizzato qui esclusivamente come verifica indipendente dei dati sulle scorte forniti da terzi e modificato in quanto le righe relative a ciascun bot sono state aggregate e confrontate anziché riprodotte. Steam Card Exchange e steam.supply sono citati sopra tramite link. I prezzi dei giochi sono quelli indicati da Valve. I nomi e le immagini delle carte, dei giochi e dei set appartengono a Valve o agli editori, e sono riprodotti senza alcuna rivendicazione né licenza, in quanto dati di mercato.\n\nDue misurazioni previste non sono state effettuate e non sono state sostituite. Gli endpoint del Community Market di Steam — panoramica dei prezzi, ricerca/visualizzazione, cronologia dei prezzi — non restituiscono alcun dato all'host che li raccoglie, mentre le pagine di discussione della community Steam restituiscono un codice HTTP 403, pertanto nessun dato riportato in questa pagina deriva dai dati in tempo reale del Market. Il metodo basato sul volume delle vendite, che avrebbe conteggiato le carte ottenute al reset giornaliero, richiede una sessione Steam con accesso effettuato; Il manifesto di questa indagine afferma che non è stata utilizzata alcuna credenziale del marketplace, e tale dichiarazione è stata mantenuta. Il livello del bot-stock è quello che si può misurare senza di esso.\n\nFonti primarie\n\nSteam Contratto di abbonamento ↗ archiviato 2026-09-24 ↗ — § 2.A, § 2.G, § 3.D, § 4.C, § 4.D.\nSteam Assistenza — Account utente limitati ↗ — la soglia $5.00 e l'elenco delle caratteristiche soggette a restrizioni.\nValve — Steam Domande frequenti sulle carte collezionabili ↗ — le meccaniche di drop e il modello free-to-play $9.\nArchiSteamFarm Domande frequenti ↗ e discussione n. 3440 ↗.\nSteam Pagine dei gruppi e dei profili della community, da leggere direttamente, per la sezione 08.\nDomande frequenti (FAQ) di steamid.uk, istantanea di Internet Archive 2026-04-01 ↗.\nOtto Steam Avvisi relativi al blocco dell’assistenza pubblicati dai destinatari, 2020–2026, elencati con i relativi link nella sezione 06.\n\nCosa non viene rivendicato\n\nNon è stata stimata alcuna cifra relativa alle entrate derivanti dal “card farming” per Valve. Non viene indicato il numero di account attivi per nessuno strumento, e le 1,39 milioni di quote di drop sono non un conteggio degli account di proprietà dell’azienda agricola — si veda la nota nella sezione 02. Nessuna persona è accusata di aver commesso un illecito; laddove venga citata una persona, questa viene indicata con il proprio nome utente pubblico Steam, nel proprio ruolo pubblico, da una pagina Valve pubblicata. Per nessuno degli otto account bloccati nella sezione 06 si afferma che sia innocente o colpevole; la constatazione riguarda la lettera, non l’account. I dati relativi alla perdita di operatori riportati nella sezione 02 provengono da segnalazioni dirette e sono contrassegnati come tali in la nota di approvvigionamento. Le FAQ di steamid.uk sono tratte da un’istantanea dell’Internet Archive poiché la pagina attiva è protetta da un sistema di verifica anti-bot. Non si sostiene che sia stato tentato e poi soppresso alcun censimento dei ban: si constata semplicemente che non ne è stato pubblicato alcuno. La curva di livello Steam al di sopra di 667 non è stata modellizzata.\n\nPerché lo strumento non è l'oggetto\n\nArchiSteamFarm afferma che \"non è autorizzato da Valve\" e in questa pagina non le viene mossa alcuna accusa. Viene utilizzato come strumento di misurazione, poiché è l’unico soggetto in questo contesto economico a documentare pubblicamente e per iscritto i meccanismi di funzionamento. Valve può sintetizzare l’intera questione in un unico paragrafo: pubblicare quali automazioni commerciali autorizza e il resoconto, per ciascun operatore, di come ha gestito il resto.\n\nLeggi anche: come viene determinato il prezzo del mercato stesso → · la scala dei prezzi e il limite massimo di quotazione → · gli articoli Steam non saranno disponibili →",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Una \"bot farm\" non è una falla nel negozio di Valve. È una cliente."
          },
          {
            "level": 2,
            "id": null,
            "text": "Che cos’è in realtà una fattoria, passo dopo passo"
          },
          {
            "level": 3,
            "id": null,
            "text": "Acquista"
          },
          {
            "level": 3,
            "id": null,
            "text": "Acquista giochi"
          },
          {
            "level": 3,
            "id": null,
            "text": "Inattivo\nLo strumento effettua l'accesso all'account sulla rete Steam in modalità headless, \"analizza i tuoi badge\", crea l'elenco dei titoli ottenibili e avvia \"giocare alle partite idonee e verificare periodicamente se la partita è già stata completata.\" Descrizione del meccanismo fornita dal responsabile del progetto: esso \"non fa altro che comunicare a Steam che stiamo giocando a un determinato gioco.\""
          },
          {
            "level": 3,
            "id": null,
            "text": "Le gocce si esauriscono\nOgni titolo ha una durata limitata. \"Ogni gioco prevede un numero fisso di carte da ottenere. Una volta ottenute tutte (circa la metà del set completo), il gioco non è più un'opzione valida per il farming.\" Un’azienda agricola che voglia continuare a produrre deve continuare ad acquistare titoli. L’offerta di carte è limitata dagli acquisti — per come è stato progettato il sistema, e a vantaggio di Valve."
          },
          {
            "level": 3,
            "id": null,
            "text": "Prelievo\nLa carta esce da una delle tre porte: viene venduta sul Mercato della Comunità, scambiata o trasformata in gemme. Ciascuna di queste operazioni costituisce una transazione sul Mercato in abbonamento o uno scambio, e il § 3.D riserva l’addebito: \"Valve può applicare una commissione sulle transazioni effettuate in un marketplace in abbonamento.\" È questo il passaggio che rende l’intera operazione una violazione — vedi 05."
          },
          {
            "level": 2,
            "id": null,
            "text": "Prima ancora che un’azienda agricola guadagni un centesimo, ha già pagato Valve"
          },
          {
            "level": 3,
            "id": null,
            "text": "Quanto è grande effettivamente l’oggetto che si sta acquistando"
          },
          {
            "level": 3,
            "id": null,
            "text": "Quanto è grande un insieme?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Quanto costa la licenza"
          },
          {
            "level": 3,
            "id": null,
            "text": "Cosa restituisce l'insieme finito"
          },
          {
            "level": 3,
            "id": null,
            "text": "Dove si trovano gli insiemi 694,673"
          },
          {
            "level": 3,
            "id": null,
            "text": "Cosa dice e cosa non dice questo pavimento"
          },
          {
            "level": 3,
            "id": null,
            "text": "E l'agricoltura non è redditizia ai prezzi di Valve"
          },
          {
            "level": 3,
            "id": null,
            "text": "Cosa sostiene effettivamente l’azienda agricola"
          },
          {
            "level": 4,
            "id": null,
            "text": "Vendite di videogiochi"
          },
          {
            "level": 4,
            "id": null,
            "text": "\"Online\" e tempo libero"
          },
          {
            "level": 4,
            "id": null,
            "text": "Iscrizioni"
          },
          {
            "level": 4,
            "id": null,
            "text": "Denaro nel portafoglio e commissioni"
          },
          {
            "level": 4,
            "id": null,
            "text": "Comunicato stampa di livello 0"
          },
          {
            "level": 3,
            "id": null,
            "text": "E il prelievo stesso rappresenta una perdita di valore Valve: si pagano le tasse due volte"
          },
          {
            "level": 3,
            "id": null,
            "text": "Non si tratta di un fenomeno passeggero. È un settore che vanta una solida tradizione pluriennale."
          },
          {
            "level": 3,
            "id": null,
            "text": "Set completi di carte presenti nella directory pubblica dei bot, in vendita a Steam"
          },
          {
            "level": 3,
            "id": null,
            "text": "Come appare la classifica dei badge di una vendita vista dall'alto"
          },
          {
            "level": 3,
            "id": null,
            "text": "E quella stessa flotta è presente anche quando non ci sono offerte in corso"
          },
          {
            "level": 3,
            "id": null,
            "text": "La directory di riposo, bot per bot"
          },
          {
            "level": 2,
            "id": null,
            "text": "L'altro prodotto è il numero che compare accanto al tuo nome"
          },
          {
            "level": 3,
            "id": null,
            "text": "Set completi consumati, dal livello 1 a 1,000"
          },
          {
            "level": 3,
            "id": null,
            "text": "Come è stata verificata la curva, dato che Valve non la pubblica"
          },
          {
            "level": 2,
            "id": null,
            "text": "La clausola non descrive l'agricoltura in modo vago, ma ne elenca le attività."
          },
          {
            "level": 3,
            "id": null,
            "text": "\"…il momento del gioco\""
          },
          {
            "level": 3,
            "id": null,
            "text": "\"…senza un contributo concreto da parte degli utenti\""
          },
          {
            "level": 2,
            "id": null,
            "text": "Ogni uscita da una carta emessa da un operatore è un’uscita vietata dalla licenza — e Valve applica una tariffa all’uscita"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 2.A — la licenza"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 2.G — la restrizione"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 3.D — la tariffa"
          },
          {
            "level": 3,
            "id": null,
            "text": "Se si leggono tutti e tre insieme, la posizione si chiude"
          },
          {
            "level": 3,
            "id": "fee-ladder",
            "text": "Il costo all’ingresso non è 15%. Su una carta in affitto arriva a due terzi."
          },
          {
            "level": 3,
            "id": null,
            "text": "Commissione effettiva su una vendita sul Mercato Comunitario, in base al prezzo richiesto dal venditore"
          },
          {
            "level": 2,
            "id": null,
            "text": "Senza preavviso, a ondate, e si diffonde lungo la catena di numeri di telefono"
          },
          {
            "level": 3,
            "id": null,
            "text": "Caso 4 — giugno 2025, VAC divieti relativi al CS2 inattivo"
          },
          {
            "level": 3,
            "id": null,
            "text": "Come muore un account principale"
          },
          {
            "level": 3,
            "id": null,
            "text": "Lo stesso paragrafo, a distanza di cinque anni, da tre agenti diversi"
          },
          {
            "level": 3,
            "id": null,
            "text": "Nota sull’approvvigionamento — perdite a livello di operatore"
          },
          {
            "level": 2,
            "id": null,
            "text": "I due lati della stessa scrivania"
          },
          {
            "level": 3,
            "id": null,
            "text": "Un cliente, per operazioni di trading"
          },
          {
            "level": 3,
            "id": null,
            "text": "Una flotta di bot automatizzati, per gestire grandi volumi"
          },
          {
            "level": 3,
            "id": null,
            "text": "La domanda che ne deriva, in parole povere"
          },
          {
            "level": 2,
            "id": null,
            "text": "Chi regola l'economia delle carte?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Un dipendente Valve gestisce il più grande gruppo dedicato allo scambio di figurine Valve dipendente"
          },
          {
            "level": 3,
            "id": null,
            "text": "Il livello della lista dei ban e chi lo gestisce Moderatore volontario Servizio di terze parti"
          },
          {
            "level": 3,
            "id": null,
            "text": "Cosa ne consegue, e cosa no"
          },
          {
            "level": 3,
            "id": null,
            "text": "Nessuno conta. Questa è la conclusione."
          },
          {
            "level": 3,
            "id": null,
            "text": "Censimento dei 10,88 milioni di account: 88.97% Non modificato"
          },
          {
            "level": 3,
            "id": null,
            "text": "Prove forensi e censimento approfondito"
          },
          {
            "level": 2,
            "id": null,
            "text": "Ciò che è stato letto e ciò che non viene rivendicato"
          },
          {
            "level": 3,
            "id": null,
            "text": "I quattro set di dati e le operazioni aritmetiche su di essi"
          },
          {
            "level": 3,
            "id": null,
            "text": "Fonti primarie"
          },
          {
            "level": 3,
            "id": null,
            "text": "Cosa non viene rivendicato"
          },
          {
            "level": 3,
            "id": null,
            "text": "Perché lo strumento non è l'oggetto"
          }
        ],
        "links": [
          "https://help.steampowered.com/en/faqs/view/71D3-35C2-AD96-AA3A",
          "https://github.com/JustArchiNET/ArchiSteamFarm/wiki/FAQ",
          "https://steamcommunity.com/tradingcards/faq/",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260924114457/https://store.steampowered.com/subscriber_agreement/",
          "https://steamladder.com/ladder/badges/2861690/",
          "http://web.archive.org/web/20260716205303/https://steamladder.com/ladder/badges/2861690/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/farm-economy-timeline.json",
          "https://store.steampowered.com/charts/",
          "http://web.archive.org/web/20260923183013/https://store.steampowered.com/charts/",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://github.com/JustArchiNET/ArchiSteamFarm/discussions/3440",
          "https://x.com/gergelyszabo94/status/1311004678633795585",
          "https://x.com/prcs25/status/1811893857253982720",
          "http://web.archive.org/web/20240715122902/https://x.com/prcs25/status/1811893857253982720",
          "https://reddit.com/r/steamsupport/comments/1fjmgc5/what_to_do_when_your_steam_account_gets_hacked/mkelm2y/",
          "https://www.reddit.com/r/csgomarketforum/comments/r87owv/psa_my_steam_account_just_got_banned/",
          "http://web.archive.org/web/20250327203008/https://www.reddit.com/r/csgomarketforum/comments/r87owv/psa_my_steam_account_just_got_banned/",
          "https://www.reddit.com/r/GlobalOffensiveTrade/comments/r9xql9/d_recently_received_commercial_ban_for_what_seems/",
          "http://web.archive.org/web/20211206034804/https://www.reddit.com/r/GlobalOffensiveTrade/comments/r9xql9/d_recently_received_commercial_ban_for_what_seems/",
          "https://www.reddit.com/r/csgomarketforum/comments/1hhxx7m/d_permanently_locked_on_steam_for_commercial_use/",
          "http://web.archive.org/web/20250627014045/https://www.reddit.com/r/csgomarketforum/comments/1hhxx7m/d_permanently_locked_on_steam_for_commercial_use/",
          "https://www.reddit.com/r/steamsupport/comments/1hkctwt/permanent_ban_with_no_explanation/",
          "https://www.reddit.com/r/pcgaming/comments/1vf24lu/warning_to_all_gamersexpats_steam_took_my_money/",
          "https://steamcommunity.com/groups/card-trading-card-trades",
          "https://steamcommunity.com/id/afarnsworth",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/groups/steambans",
          "https://steamcommunity.com/groups/steambans",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/id/killahinstinct_",
          "https://web.archive.org/web/20240914124859/https://steamcommunity.com/id/msart",
          "https://steamcommunity.com/id/msart/groups/",
          "http://web.archive.org/web/20260401154714/https://steamid.uk/faq/",
          "https://phishdestroy.io/steam_dossier/it/enforcement_audit.html",
          "https://phishdestroy.io/steam_dossier/it/#evidence-blackout",
          "https://www.steamcardexchange.net/index.php?badgeprices",
          "http://web.archive.org/web/20260804200309/https://www.steamcardexchange.net/index.php?badgeprices",
          "https://steam.supply/CardBots",
          "https://steamlvlup.net/cardbots",
          "http://web.archive.org/web/20260210171205/https://steamlvlup.net/cardbots",
          "https://steamlvlup.net/",
          "https://creativecommons.org/licenses/by/4.0/",
          "http://web.archive.org/web/20260923221628/https://creativecommons.org/licenses/by/4.0/",
          "https://phishdestroy.io/steam_dossier/it/market_economics.html",
          "https://phishdestroy.io/steam_dossier/it/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/it/elite_skins.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/it/card_economy.content.json",
      "export_json_sha256": "c0b7a1cc0be517c25a0ba58127d684b588fa5b0b0665951f5873ca5aa8bcb3a2"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "it/elite_skins.html",
      "language": "it",
      "title": "Un prodotto, due sistemi di prezzi — Il dossier “Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/it/elite_skins",
      "source_html_sha256": "5933138a02701702b3ddba53f451c4c4fde16f2850bad95b5684bf4ad738db7f",
      "exported_at": "2026-09-29T00:17:49.796Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "register",
            "source": "https://phishdestroy.io/steam_dossier/it/elite_skins#register"
          },
          {
            "id": "",
            "source": "https://phishdestroy.io/steam_dossier/it/elite_skins#selected"
          }
        ],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "elite_skins.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/it/elite_skins.pdf?v=print-20260929-v5",
        "sha256": "bb99d68a1f34409bb4749e19afada145b0e7103765550780138d1e6f687c7de5",
        "bytes": 95640,
        "pages": 7
      },
      "integrity": {
        "signed_object": "elite_skins.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "elite_skins.content.json.asc",
        "digest_file": "elite_skins.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify elite_skins.content.json.asc elite_skins.content.json",
          "sha256sum -c elite_skins.content.json.sha256"
        ]
      },
      "content": {
        "text": "ALLEGATO IV / ARCHITETTURA DI MERCATO / 20 SETTEMBRE 2026\nElite Skins Register — Il tetto massimo del mercato di $1,800\n\nUn articolo. Due sistemi di prezzi.\n\nCOSA DIMOSTRA QUESTA SEZIONE\n\nQuesto registro costituisce un censimento empirico di tutte le categorie di skin CS2 con un prezzo superiore al limite massimo di $1,800 imposto da Steam per le inserzioni sul Community Market, su cinque piattaforme esterne. Esso dimostra che 248 le categorie di fascia alta, che rappresentano 18,394 inserzioni attive e $78.6 milioni di liquidità pubblicata, sono 100% assenti dal marketplace ufficiale di Valve. I venditori alla ricerca di prezzi di mercato reali sono strutturalmente costretti a ricorrere a piattaforme esterne, pur affidandosi esclusivamente alle dinamiche di negoziazione sottostanti di Steam.\n\nWhat this means — the Community Market listing ceiling\n\nSteam’s own market refuses a listing above roughly $1,800. A seller may ask less, never more. Items whose market price sits above that line therefore cannot be sold at that price on Steam at all — which is the mechanism that moves those sales to third-party venues while the item itself never leaves Valve’s inventory system.\n\nSection 13 — the off-Steam price gap →\n\n← Torna al briefing esecutivo\n\nSteam fissa il prezzo massimo di un annuncio sul Community Market a circa $1,800. Tra i cinque marketplace di terze parti i cui prezzi sono riportati in questa panoramica, 419 Le categorie di articoli CS2 presentano un prezzo di vendita in tempo reale più basso superiore a tale limite — e 402 di esse, 95.9%,, non presentano alcuna quotazione Steam. Insieme possiedono esemplari quotati su 18,641 per un valore di almeno $82.4milioni. È necessario che un secondo mercato dia il proprio consenso affinché il prezzo sia valido, 248 di quelle categorie sono confermate — e in ognuna di esse, 100%, non compare su Steam. \"The dearest\" è un adesivo | Titan (Holo) | Katowice 2014 su $66,285, quotato da quattro piattaforme situate a un5.2%a l’una dall’altra e non riportato da nessuna di quelle di Valve. La classifica completa, i rendering e le valutazioni sono disponibili nel atlante dei prezzi a scala.\n\nControlla tutte le voci di 419 ↓Apri l'atlante ↗Leggi la procedura\n248categorie in cui due o più marketplace hanno prezzi superiori al limite massimo\n18,394copie presenti su cinque piattaforme di vendita\n$78.6Mvalore minimo di tali annunci\n100%alcuni di loro non compaiono affatto su Steam\n\nCorrezione · in precedenza questa pagina riportava un prezzo non confermato\n\nUna versione precedente di questa pagina riportava come titolo “Souvenir AK-47 | Point Disarray” con un prezzo richiesto di $148,954 su una piattaforma di vendita, mentre su Steam era quotato a $119.. Quella riga si riferisce a un unico scaffale e a un unico esemplare, senza che nessun’altra piattaforma di vendita confermi il prezzo; si tratta quindi di un prezzo richiesto piuttosto che di un prezzo effettivo, e non è più presente nella pagina. Ogni cifra riportata qui è ora limitata alle categorie 248 per le quali almeno due piattaforme di vendita online fissano indipendentemente un prezzo superiore al limite massimo. La riga in sé non è stata rimossa — è ancora presente nel registro sottostante, e la valutazione che ne ha determinato la declassificazione è riportata per esteso nel atlante dei prezzi a scala.\n\n01 / il denaro nelle offerte di acquisto attive\nIl limite minimo misurabile in dollari\n\nDati ricalcolati sulla base dello snapshot autorizzato di cs2.sh relativo a cinque marketplace. Si tratta di un valore minimo aggregato di richiesta in un sottoinsieme definito, non del fatturato delle vendite né di una valutazione dell'economia di CS2.\n\n248 CATEGORIE CONFERMATE · 18,394 COPIE ELENCATE · 5 MERCATI$78.62M\n\nPrezzo di vendita minimo complessivo di ogni articolo CS2 per il quale due o più piattaforme fissino, in modo indipendente, un prezzo superiore al limite consentito da Valve sul proprio mercato.\n\nPerché si tratta di un limite minimo e non di una stima\n\nPer ogni marketplace moltiplichiamo il suo più basso richiedi un articolo in base al numero di copie indicate dalla piattaforma. Tutte le altre copie presenti su quello scaffale hanno un prezzo pari o superiore al prezzo di richiesta più basso, quindi il valore effettivo pubblicato è più alto — per definizione, non per supposizione. Non si tratta di una vendita, di un flusso di cassa né di una valutazione a livello di mercato, e lo stesso articolo fisico può apparire su più di una piattaforma.\n\nControlla tutte le righe di origine di 419 ↗\n★ Guanti sportivi | Labirinto di siepi (testati sul campo)\n$4.68M\nAWP | Gungnir (nuovo di fabbrica)\n$4.46M\nAWP | Dragon Lore (nuovo di fabbrica)\n$4.34M\n★ Coltello a farfalla | Fade (nuovo di fabbrica)\n$4.17M\nAK-47 | Wild Lotus (nuovo di fabbrica)\n$4.16M\n★ Coltello a farfalla | Doppler (nuovo di fabbrica)\n$3.64M\n\nLe barre indicano i sei contributi più rilevanti a livello di categoria nel calcolo del prezzo minimo, rapportati al valore più elevato. Una barra alta riflette sia il prezzo di vendita più basso sia il numero di copie in vendita. Lo stesso articolo fisico può essere presente su più di un marketplace, pertanto questi dati non devono essere sommati al totale di nessun altro mercato.\n\n02 / esempi verificabili\nCiò che il limite tralascia\n\nLe illustrazioni corrispondono ai nomi esatti degli articoli, ove disponibili. I prezzi indicati sono i prezzi di vendita attuali riportati nel catalogo datato, non i prezzi effettivi di transazione.\n\n★ Butterfly Knife | Doppler (Factory New)\n\nFonte: https://phishdestroy.io/steam_dossier/it/elite_skins#selected\n\nIl divario misurabile: queste offerte non possono essere eguagliate da un annuncio su Steam allo stesso importo in dollari statunitensi. Quello di Valve Domande frequenti sul Mercato della Comunità archiviato su 2026-09-21 ↗ indica un prezzo massimo di quotazione di circa $1,800. Un venditore potrebbe comunque fissare un prezzo inferiore; spetta al venditore decidere se ciò sia accettabile. Un altro Ricerca su CSMarketCap per articoli con prezzo superiore a $1,800 ↗ mostra i prodotti \"Factory New Dragon Lore\" nei mercati indicizzati da 28 con circa 1.1.000 offerte visualizzate; le voci in inventario duplicate possono essere conteggiate più di una volta.\n\n03 / la dipendenza strutturale\nIl tetto massimo di Steam spinge la determinazione dei prezzi al di fuori di Steam\n\nIl confronto è di natura strutturale. Non presuppone che ogni prezzo richiesto sia equo, né considera gli annunci invenduti come ricavi.\n\n01 · LA REGOLA\nSteam chiude l'elenco\n\nValve afferma che gli annunci su Community Market hanno un limite massimo di circa $1,800. Inoltre, i saldi dei portafogli sono soggetti a un limite massimo e i fondi presenti nei portafogli non possono essere prelevati in contanti.\n\n02 · L'OSSERVAZIONE\nDragon Lore: $10,940.85\n\nIl catalogo del marketplace “5-” mostra 389 offerte in tempo reale per AWP Dragon Lore (nuovo di fabbrica), a partire da $10,940.85 (piano CSFloat). Il registro più ampio contiene 248 categorie confermate che superano il limite di Steam.\n\n03 · LA CONSEGUENZA\nRipartizione tra prezzo e trasferimento\n\nUn venditore che punta a ottenere quel prezzo più alto non posso pubblicarlo su Steam. I servizi esterni possono stabilire il prezzo in contanti, ma la consegna continua a basarsi sulla proprietà e sul trasferimento degli articoli controllati dSteam.\n\nLa contraddizione politica: Di Valve Contratto di abbonamento archiviato su 2026-09-21 ↗ si riserva il diritto di sfruttare commercialmente i servizi di Steam, salvo espressa autorizzazione, mentre il suo 2016 dichiarazione archiviato su 2026-09-21 ↗ ha affermato che gli operatori del gioco d’azzardo stavano già utilizzando Steam OpenID e account automatizzati. Questa è una prova diretta del fatto cValve, fosse a conoscenza dell’esistenza di questa categoria di operatori esterni su 2016.. Tuttavia, il marketplace ufficiale non può pubblicare i prezzi rilevati per questi articoli di alto valore. Si tratta della dipendenza architettonica dalla determinazione dei prezzi e dalle transazioni fuoriSteam; lo stato contrattuale di ciascun singolo mercato richiede prove specifiche. I due principali mercati occidentali che registrano questo volume di transazioni superiore alla capacità operativa agiscono come entità societarie formali nelle principali giurisdizioni — CSFloat Inc. (costituita nel Delaware, Stati Uniti) e Skinport GmbH (registrata a Stoccarda, Germania, HRB 764879) — effettua apertamente transazioni per centinaia di milioni nella vendita di articoli peer-to-peer, avvalendosi direttamente delle API web e dell’infrastruttura commerciale di Steam.\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\nLe quattro righe da $100,000 corrispondono al prezzo massimo di quotazione di CSFloat. Sono contrassegnate nel registro e non devono essere interpretate come valutazioni. Il crawl degli annunci archiviati su CSFloat ha raggiunto solo circa $6,999,, pertanto per il registro completo >$1,800 viene utilizzata l'istantanea del catalogo pubblico.\n\n04 / un altro gioco di \"Valve\"\nIl record è stato battuto anche da Dota 2\n\nLo stesso rigoroso test dell’offerta più economica su Skinport individua le categorie CS2 su 166 e quelle di Dota 2 su 3. Si tratta di un’istantanea separata del mercato; non aggiungerle a CSFloat’s 245.\n\nDOTA 2 · OFFERTA 1\nMezzaluna eroica e brutale\n\nSkinport, il sito più economico, chiede: $14,622.25.\n\nDOTA 2 · OFFERTA 1\nMantello “Dark Artistry”\n\nSkinport, il sito più economico, chiede: $8,255.16.\n\nDOTA 2 · OFFERTA 1\nStella alimentata corrotta\n\nSkinport, il sito più economico, chiede: $2,087.92.\n\nSi tratta di tre categorie di oggetti elencate, non di tutti gli oggetti esistenti in Dota 2. Controlla le righe datate dell’Skinporte ↗ e API documentazione ↗.\n\n05 / robustezza\nIl risultato non dipende dal valore esatto del limite massimo\n\nValve fissa il limite massimo nella valuta regionale dell’acquirente, per cui, una volta convertito in USD, il risultato non corrisponde a una cifra tonda. Il censimento viene quindi ripetuto per ogni soglia plausibile. La percentuale di questi articoli mancanti su Steam non scende mai al di sotto di 95%.\n\nTest di soglia\tCategorie di articoli\tCopie elencate\tValore minimo\tAssente da Steam\n$1,800\t419\t18,641\t$82,449,526\t95.9%\n$2,000\t382\t15,159\t$75,541,325\t95.5%\n$2,070\t363\t12,336\t$69,560,305\t95.6%\n$2,300\t323\t11,644\t$67,984,432\t95.0%\n$2,500\t299\t10,950\t$66,203,929\t95.0%\n\nLeggere una riga alla volta; le righe sono sottoinsiemi annidati dello stesso censimento, non popolazioni distinte. Il “valore minimo” moltiplica il valore di ciascun mercato più basso viene calcolato in base al numero di copie indicate, quindi, per sua stessa natura, sottostima il numero di volumi presenti sugli scaffali. Apri il set di dati ↗\n\n06 / la scarsità che si può quantificare\nQuanti pochi di questi sono effettivamente in vendita\n\nBUFF suddivide la disponibilità di ogni articolo in intervalli di quantità e indica quante copie sono presenti in ciascuno di essi. In questo modo, il termine “raro” non è più solo una parola, ma diventa un numero — e il prezzo viene calcolato separatamente in base alle condizioni dell’articolo e alla sua versione grafica.\n\n298 ELENCO DELLE COPIE\nAWP | La storia dei draghi\n\n8 variante distinte con i relativi prezzi. La più costosa, Souvenir AWP | Dragon Lore (Nuovo di fabbrica), chiede $12,363 con copie di *20* sugli scaffali.\n\nNella sezione dedicata ai migliori galleggianti presente sullo scaffale (0–0.01) ci sono 2 copie, chiedendo $17,875 — un sovrapprezzo di +45% rispetto al prezzo di base richiesto per l’articolo, basato esclusivamente sulle sue condizioni.\n\n607 ELENCO DELLE COPIE\nM4A4 | Howl\n\n12 variante distinte con i rispettivi prezzi. La più costosa, Souvenir M4A4 | Howl (nuovo di fabbrica), chiede $14,895 con copie di *2* sugli scaffali.\n\n213 ELENCO DELLE COPIE\nAK-47 | Wild Lotus\n\n7 variante distinte con i relativi prezzi. La più costosa, Souvenir AK-47 | Wild Lotus (nuovo di fabbrica), chiede $14,895 con copie di *2* sugli scaffali.\n\n310 ELENCO DELLE COPIE\nAWP | Gungnir\n\n7 variante distinte con i relativi prezzi. La più costosa, Souvenir AWP | Gungnir (segni di usura minimi), chiede $14,895 con copie di *2* sugli scaffali.\n\nPerché questo è importante per il resto del presente dossier: Non si tratta di concetti astratti. In tutto il mondo esistono poche centinaia di copie di ciascun trofeo disponibili sul mercato libero, ognuna delle quali è collegata a un account Steam e viene trasferita tramite una transazione Steam. In un mercato così ristretto, il furto di un singolo oggetto in inventario rappresenta un evento misurabile, e le tecniche di appropriazione degli account documentate altrove in questa indagine producono un guadagno diretto e quantificabile.\n\nI conteggi si riferiscono alle inserzioni attive su una piattaforma di vendita al momento della rilevazione, non al numero totale esistente. Le copie presenti in inventari privati non vengono conteggiate in alcun modo in questa sede. Apri il set di dati \"float\" ↗\n\n07 / la scala non si vede\nPiù l'articolo è costoso, più è lontano da qualsiasi luogo visibile\n\nOgni gradino sottostante rappresenta una diversa categoria probatoria. Si è scelto deliberatamente di non raggrupparle in un unico numero.\n\nPiolo\tFigura\tDi che tipo di fatto si tratta?\nCeiling on Valve's own market\t~$1,800\tPublished rule, stated in the Steam Community Market FAQ.\nDearest ask several marketplaces agree on\t$66,285\tMeasured by us in this snapshot. Sticker | Titan (Holo) | Katowice 2014, quoted by four marketplaces within 5.2% of one another. An ask, not a sale.\nDearest ask seen on any single shelf\t$148,954\tOne marketplace, one copy, no second marketplace agreeing — and equal to a round CNY 1,000,000 at the snapshot rate. Listed here as the outer edge of what sellers ask, and relied on for nothing.\nPublic marketplace sale\t$49,999\tSpecialist Gloves | Crimson Kimono (FN) on CSFloat, as reported by SteamAnalyst. Platform-recorded, third-party reported.\nReported private sale\t$400,000\tAK-47 | Case Hardened, reported by PC Gamer in April 2023. Journalism, not a record we hold.\nReported offer, declined\t$1,500,000\tBlue Gem Karambit, pattern #387. No sale took place and the figure has not been independently confirmed. Included to mark the ceiling of the claims, not to assert a value.\n\nIl punto strutturale: Il mercato di Valve si ferma a circa $1,800.; i marketplace di terze parti portano la transazione a circa $66,000, dove diversi di essi concordano, e a circa $150,000, dove solo uno lo fa. Al di sopra di tale soglia non esiste alcuna sede di negoziazione: i trasferimenti più consistenti di beni emessi da Valveavvengono in forma privata, tra individui, senza quotazione, senza registrazione sulla piattaforma, senza verifica dell’identità e senza rendicontazione. Il trasferimento stesso avviene comunque su Steam. Più alto è il valore, meno è visibile agli occhi di chiunque, e l’infrastruttura che lo trasporta è interamente di proprietà di Valve.\n\nGli ultimi due punti si basano su informazioni fornite da terzi, citate come tali. Questo progetto non le ha verificate e non si basa su di esse per trarre alcuna conclusione.\n\nTutte le categorie osservate su 419\n\nFonte: https://phishdestroy.io/steam_dossier/it/elite_skins#register\n\n09 / provenienza e limiti\nControlla il calcolo\n\nMettiamo a disposizione i dati locali e la fonte pubblica. Il dato numerico riportato si riferisce a CSFloat alla data di acquisizione.\n\nI limiti e le condizioni stabiliti da Valve\n\nSteam Domande frequenti sul Mercato della Comunità ↗ archiviato su 2026-09-21 ↗ indica il valore massimo approssimativo di $1,800. Il Contratto di abbonamento ↗ archiviato su 2026-09-21 ↗ stabilisce le restrizioni relative all'uso commerciale.\n\nDa dove provengono i prezzi\n\nI prezzi, il numero di titoli quotati e le fasce di flottante sono tratti dal cs2.sh dati di mercato API nell'ambito di un abbonamento commerciale a pagamento, utilizzando una chiave di licenza. Non è stato effettuato alcuno scraping su alcuna piattaforma di marketplace né sono stati utilizzati account o credenziali di alcuna piattaforma di marketplace. Il fornitore raggruppa BUFF, Youpin, CSFloat, Skinport, C5Game e il Community Market di Steam; tutte le cifre sono espresse in USD così come riportate. Apri il manifesto di provenienza ↗ — registra gli endpoint esatti, i tempi di acquisizione e gli hash SHA-256 delle istantanee grezze, in modo che un lettore indipendente, disponendo della propria chiave, possa estrarre gli stessi dati e ricalcolare ogni valore riportato in questa pagina.\n\nCiò che non siamo riusciti a ottenere\n\nL'abbonamento acquistato copre solo le istantanee attuali. Non abbiamo avuto accesso agli endpoint storici e d'archivio, e In questa pagina non viene fornita alcuna indicazione in merito a tendenze, prezzi passati o variazioni nel tempo. Qui ogni cosa è un singolo istante, datato.\n\nIl registro \"CSFloat\" precedente\n\nLa prima versione di questa mostra comprendeva 245 categorie tratte da un’istantanea del catalogo CSFloat datata 20 settembre 2026: quell’istantanea rimane qui ↗. Il presente registro è più ampio perché copre cinque mercati anziché uno solo. Si tratta di due dati distinti che non devono essere sommati.\n\nDichiarazione di esecuzione specifica di Valve\n\nAggiornamento di Valve su “2016” relativo allo scambio di oggetti di gioco ↗ archiviato su 2026-09-21 ↗ riguarda gli operatori di gioco d’azzardo che utilizzano OpenID e account automatizzati su Steam. Si tratta di una misura più limitata rispetto a un divieto generalizzato di tutti i marketplace esterni.\n\nLimite di interpretazione\n\nSi tratta di offerte, non di vendite. Un nome di mercato può riferirsi a più articoli fisici con caratteristiche diverse in termini di finitura, motivo o adesivi. Questo registro non rileva il valore di mercato complessivo né le intenzioni di \"Valve\".",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Elite Skins Register — Il tetto massimo del mercato di $1,800"
          },
          {
            "level": 2,
            "id": null,
            "text": "Il limite minimo misurabile in dollari"
          },
          {
            "level": 3,
            "id": null,
            "text": "Perché si tratta di un limite minimo e non di una stima"
          },
          {
            "level": 2,
            "id": null,
            "text": "Ciò che il limite tralascia"
          },
          {
            "level": 3,
            "id": null,
            "text": "★ Butterfly Knife | Doppler (Factory New)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Il tetto massimo di Steam spinge la determinazione dei prezzi al di fuori di Steam"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam chiude l'elenco"
          },
          {
            "level": 3,
            "id": null,
            "text": "Dragon Lore: $10,940.85"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ripartizione tra prezzo e trasferimento"
          },
          {
            "level": 2,
            "id": null,
            "text": "Il record è stato battuto anche da Dota 2"
          },
          {
            "level": 3,
            "id": null,
            "text": "Mezzaluna eroica e brutale"
          },
          {
            "level": 3,
            "id": null,
            "text": "Mantello “Dark Artistry”"
          },
          {
            "level": 3,
            "id": null,
            "text": "Stella alimentata corrotta"
          },
          {
            "level": 2,
            "id": null,
            "text": "Il risultato non dipende dal valore esatto del limite massimo"
          },
          {
            "level": 2,
            "id": null,
            "text": "Quanti pochi di questi sono effettivamente in vendita"
          },
          {
            "level": 3,
            "id": null,
            "text": "AWP | La storia dei draghi"
          },
          {
            "level": 3,
            "id": null,
            "text": "M4A4 | Howl"
          },
          {
            "level": 3,
            "id": null,
            "text": "AK-47 | Wild Lotus"
          },
          {
            "level": 3,
            "id": null,
            "text": "AWP | Gungnir"
          },
          {
            "level": 2,
            "id": null,
            "text": "Più l'articolo è costoso, più è lontano da qualsiasi luogo visibile"
          },
          {
            "level": 2,
            "id": null,
            "text": "Tutte le categorie osservate su 419"
          },
          {
            "level": 2,
            "id": null,
            "text": "Controlla il calcolo"
          },
          {
            "level": 3,
            "id": null,
            "text": "I limiti e le condizioni stabiliti da Valve"
          },
          {
            "level": 3,
            "id": null,
            "text": "Da dove provengono i prezzi"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ciò che non siamo riusciti a ottenere"
          },
          {
            "level": 3,
            "id": null,
            "text": "Il registro \"CSFloat\" precedente"
          },
          {
            "level": 3,
            "id": null,
            "text": "Dichiarazione di esecuzione specifica di Valve"
          },
          {
            "level": 3,
            "id": null,
            "text": "Limite di interpretazione"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/it/#market-gap-section",
          "https://phishdestroy.io/steam_dossier/it/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/it/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/it/skin_atlas.html#grading",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-above-the-ceiling.json",
          "https://phishdestroy.io/steam_dossier/it/elite_skins#selected",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://csmarketcap.com/search?minPrice=1800&amp;page=1",
          "https://store.steampowered.com/agreement/?l=english",
          "http://web.archive.org/web/20260921022032/https://store.steampowered.com/agreement/?l=english",
          "https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921021947/https://store.steampowered.com/oldnews/22883",
          "https://phishdestroy.io/steam_dossier/it/#proxy-bypass-explainer",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/skinport-floor-over-cap.json",
          "https://docs.skinport.com/items",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-float-scarcity.json",
          "https://phishdestroy.io/steam_dossier/it/elite_skins#register",
          "https://cs2.sh/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/csfloat-catalogue.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/it/elite_skins.content.json",
      "export_json_sha256": "987ddc8f7144c0e6fa0441b233a79b25c471a588d325dfd07b579c1c6505ac61"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "it/enforcement_audit.html",
      "language": "it",
      "title": "Il censimento Valve non verrà pubblicato — Il dossier Steam",
      "source_url": "https://phishdestroy.io/steam_dossier/it/enforcement_audit",
      "source_html_sha256": "ee23c69e0f50c38ee67bc2b9a13f5ce50872d67a008ec5cfaa26c4c531f749b9",
      "exported_at": "2026-09-29T00:17:49.025Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "enforcement_audit.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/it/enforcement_audit.pdf?v=print-20260929-v5",
        "sha256": "47e7636cd723a291c35c327a97cdac3c07bb94ef89312acc0b1d7c6ed5aea743",
        "bytes": 146043,
        "pages": 13
      },
      "integrity": {
        "signed_object": "enforcement_audit.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "enforcement_audit.content.json.asc",
        "digest_file": "enforcement_audit.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify enforcement_audit.content.json.asc enforcement_audit.content.json",
          "sha256sum -c enforcement_audit.content.json.sha256"
        ]
      },
      "content": {
        "text": "ALLEGATO VI — IL CENSIMENTO VALVE NON VERRÀ PUBBLICATO\nQuanto è grande la farm di Steam? L’abbiamo contata noi.\n\nNon esiste un dato pubblicato sul numero di account di automazione attivi su Steam. Non c’è motivo di tenerlo segreto: lo spazio degli ID Steam è un intervallo contiguo di numeri interi e Valve assegna la chiave API Web che lo percorre. Abbiamo quindi preso la popolazione più numerosa che si identifica — la comunità ArchiSteamFarm — e abbiamo letto ogni membro una volta tramite l’endpoint di ban di Valve. Si autodichiara perché ASF, al primo avvio, si unisce automaticamente al gruppo Steam a meno che l’utente non si escluda esplicitamente o deselezioni l’impostazione di adesione al gruppo (AutoJoinSteamGroup / Statistiche). Poiché questa impostazione è attiva per impostazione predefinita, l'appartenenza al gruppo comprende una vasta popolazione: reti commerciali di bot con più account attive, hobbisti occasionali che lasciano i propri account inattivi e giocatori comuni che hanno eseguito il software sul proprio account personale senza mai rimuovere l'abbonamento predefinito. Ciò rende l'appartenenza al gruppo un censimento effettivo della portata complessiva del software: 10,880,610 account totali (di cui 5,360,499 membri confermati senza limitazioni che hanno superato il $5.00 punto di accesso al negozio). A quel punto abbiamo posto l’unica domanda che conta: che cosa ha fatto loro effettivamente Valve?\n\nCosa non è questa pagina. Non si tratta di sostenere che Valve debba bandire dieci milioni di persone, né di lamentarsi dei “card farmer”. Ogni cifra riportata di seguito è qui per un unico motivo: Valve fa escludere definitivamente gli utenti, e la motivazione fornita per iscritto è l’uso commerciale di Steam e l’automazione. Ciò misura il modo in cui quella stessa regola viene applicata alla stessa condotta su larga scala — da parte di un operatore che, nel corso del processo, riscuote $5.00 sblocchi, licenze di gioco e commissioni del Market Valve. La constatazione riguarda l’asimmetria, non il farming.\n\nIl numero di 10,88 milioniI truffatori che vanno in giro (53,5k)Audit a pagamento da 100k vs audit gratuito\n10,880,610Il numero totale di membri del gruppo ASF che hanno consultato l'API di ban di Valve (limitati e non limitati messi insieme)\n88.97%Non sono mai stato bannato — 9,680,599 account sono ancora attivi\n63.06%Tra gli account bloccati, quelli a pagamento ($5+ spesa) — 100,000 SRSWOR fetta (±0.39% MoE)\n67.77%Tra i 51,732 truffatori condannati, nessuno è soggetto a divieti relativi alle truffe (censimento completo)\n01 — La scala\nDieci milioni di conti, di cui nove su dieci non sono stati toccati\n\nUna popolazione che si conta, letta una volta attraverso il proprio endpoint di Valve.\n\nPERCHÉ SI CONTA DA SOLO\nASF si unisce al gruppo per te\n\nAl primo giro ArchiSteamFarm set Statistiche impostato su \"vero\" per impostazione predefinita e si unisce al gruppo SC Farm Steam di Archi. Un operatore deve scegliere attivamente di non partecipare. Pertanto, l'appartenenza al gruppo rappresenta un limite minimo per le installazioni, non un limite massimo. Gli operatori che hanno disabilitato le statistiche non sono inclusi; il numero reale di installazioni è almeno pari a questo valore.\n\nCOSA LEGGIAMO\n10,880,610 voci totali\n\nL'elenco dei membri dell'API ha restituito 10,880,610 SteamID64 in totale — sia limitati che non limitati. La pagina del gruppo di Steam ne mostra 5,360,499 (solo non limitati). Ogni voce è stata elaborata una volta tramite ISteamUser/GetPlayerBans su 2026-09-23. Cinquantacinque minuti su un solo tasto.\n\nLA RISPOSTA\n88.97% pulito\n\n1,200,011 comportare alcun Steam divieto (11.03%). L'altro 9,680,599 non risulta alcuna registrazione — né un ban dalla community, né VAC, niente. La farm non viene smantellata. Viene lasciata attiva. La stessa clausola, applicata a una sola persona, è sufficiente per espellerla definitivamente.\n\nTra i 10,880,610 conti, quanti Valve sono stati utilizzati?\n\nL'intera popolazione scansionata, suddivisa in base al fatto che Valve abbia applicato o meno un divieto. La sezione rossa rappresenta tutto ciò che Valve ha mai fatto a questa flotta.\n\n88.97%mai bandito\n11.03%\nNessun divieto di alcun tipo — 9,680,599 (88.97%)Presenta un divieto di Steam — 1,200,011 (11.03%)\n10,880,610I membri del gruppo ASF hanno effettuato la scansione\n9,680,599Mai bannato — 88.97%\n1,200,011Applicare qualsiasi divieto — 11.03%\n55 minPer conteggiare tutto, con una sola chiave API\nQuanto è già costato a questa flotta Valve per esistere\n\nNon si tratta di una stima dei guadagni dell'azienda agricola, bensì di un limite minimo di quanto ha già speso nel negozio di Valve — ricavato dalla regola stabilita da Valve, applicata al conteggio riportato sopra.\n\nIl conteggio 10,880,610 comprende l'elenco completo dei membri del gruppo ASF restituito dall'API — ciò include sia gli account con limitazioni che quelli senza. Quello di Steam Account utente con funzionalità limitate La pagina precisa che gli account con funzionalità limitate non contare ai fini di Steam appartenenza al gruppo (non vengono conteggiati nel numero di membri del gruppo visualizzato), ma possono comunque comparire nell'elenco dei membri sottostante. Il sottoinsieme non limitato — ovvero gli account che hanno speso almeno $5.00 nel negozio Steam — è esattamente 5,360,499 — il conteggio Steam viene visualizzato nella pagina del gruppo, che, secondo la regola stabilita dallo stesso Steam, esclude gli account con limitazioni. Il calcolo del limite minimo $5.00 si applica solo a quel sottoinsieme di account senza limitazioni.\n\n5,360,499soci senza limitazioni\n(Numero di gruppi visualizzati da Steam)\n×\n$5.00Il minimo proprio di Valve\nper smettere di essere limitati\n=\n$26,802,495limite di spesa in negozio\ndal sottoinsieme non limitato\n\nSi tratta di un limite minimo relativo alle somme già ricevute da Valve dalla parte non soggetta a limitazioni della flotta — non è una stima delle entrate, né una dichiarazione di profitto. La spesa effettiva per account è superiore nella maggior parte dei casi; la cifra $5.00 rappresenta solo la soglia minima richiesta.\n\nIl ricavo secondario: commissione fino a 66.7% sul volume delle materie prime coltivate. Oltre alla quota di iscrizione di $26.8M, ogni carta e oggetto venduto sul Mercato della Comunità è soggetto a una commissione minima obbligatoria di due centesimi pari a Valve ($0.01 Steam di commissione + $0.01 di commissione dell’editore). Nel caso delle tipiche carte da 3 centesimi e degli oggetti di scarto, Valve preleva 2 centesimi su 3 — un taglio effettivo pari a 66.67% a favore di Valve, superando di gran lunga il tasso di marketing dichiarato di 15%.\n\nAvvertenza fondamentale relativa alla popolazione: L'appartenenza al gruppo non costituisce prova del fatto che ogni singolo account sia un bot dedicato, né garantisce che tutti i bot presenti su Steam siano inclusi. Per impostazione predefinita, ASF iscrive automaticamente gli account al proprio gruppo della community al momento del lancio; a meno che l'utente non deselezioni o disattivi esplicitamente tale opzione di configurazione (AutoJoinSteamGroup), i giocatori abituali, gli utenti occasionali e i membri della comunità figurano nell’elenco insieme alle flotte automatizzate dedicate al farming. Inoltre, un ban Steam non è accompagnato da alcuna motivazione pubblica. Il risultato rappresenta un tasso empirico rilevato su questa popolazione associata al software, non un verdetto individuale su un singolo account. Aggregato, riproducibile: asf-ban-census-2026-09-23.json.\n\n02 — Geografia\nDove si trova la flotta\n\nSolo 8.5% degli account bloccati indicano un Paese di provenienza. Tra quelli che lo fanno, la quota maggiore spetta agli Stati Uniti.\n\nUn profilo Steam include un campo facoltativo relativo al Paese. 100,413 degli 1,182,811 account bloccati lo compilano — 8.5%.† Tra quella minoranza, gli Stati Uniti sono in testa con 15.5%, seguiti da Ucraina, Cina e Russia, mentre il resto si distribuisce in una lunga coda che attraversa l’Europa, l’America Latina e il Sud-Est asiatico. Nessuno verifica i dati sul campo: l’Afghanistan si colloca tra i primi dieci, il che corrisponde all’incirca al suo valore reale. Gli altri 91.5% sono stati omessi anziché assegnati, quindi ciò che ne risulta è il profilo di una minoranza autoselezionata — non una mappa della flotta, né una base per stabilire da dove venga gestita.\n\nAccount sospesi per paese dichiarato\n\nI primi 15 paesi tra i 100,413 account bloccati che rivelano una posizione pubblica. La percentuale si riferisce a quel sottoinsieme di posizioni. Passa il mouse per visualizzare i conteggi.\n\n0%\n5%\n10%\n15%\n20%\nUnited States\nUkraine\nChina\nRussia\nCanada\nAustralia\nJapan\nBrazil\nGermany\nAfghanistan\nUnited Kingdom\nRomania\nFrance\nPhilippines\nIndia\n\nPosizione letta da GetPlayerSummaries per il sottoinsieme dei siti bloccati. Il campo viene impostato dal titolare dell'account e non viene verificato da nessuno, quindi un indirizzo di uscita VPN o una voce inserita per scherzo hanno lo stesso peso di una voce reale.\n\n03 — Freschezza\nDati recenti, non un arretrato storico\n\nA giudicare dalla data di creazione degli account, la popolazione di utenti bannati è recente e non è un retaggio dell’era delle carte collezionabili.\n\nSe si trattasse di un vecchio pasticcio che si sta lentamente risolvendo, gli account bannati risulterebbero concentrati nei primi anni delle carte collezionabili. In realtà è proprio il contrario. Dei 1,132,852 account bannati che riportano una data di creazione, 70% sono stati creati nel 2020 o successivamente, e quasi la metà a partire dal 2023. Il conteggio passa da 59,175, creato nel 2017, a un picco di 227,030 creati solo nel 2024. Ognuno di loro ha superato il cancello del negozio $5.00 prima che potesse ricevere una tessera, quindi è stata riscossa la quota di ingresso per ciascuno.\n\nQuando sono stati creati gli account bloccati\n\nAnno di creazione degli account dei 1,132,852 membri bannati per cui è visibile la data di creazione. Il periodo va dal 2020 al 2026, non coincide con l’era delle figurine del 2013–2015. Picco: 2024. Passa il mouse per visualizzare i numeri.\n\n0k\n63k\n125k\n188k\n250k\n'13\n'14\n'15\n'16\n'17\n'18\n'19\n'20\n'21\n'22\n'23\n'24\n'25\n'26\n70%Tra gli account sospesi creati nel 2020 o successivamente\n227,030Account bloccati creati nel 2024 — l'anno di picco\n51,701La flessione del 2021, tra due anni di picco — senza una spiegazione\n2003→2026Dati disponibili, ma i dati relativi alla massa si riferiscono agli ultimi sei anni\n\nLa creazione risale al GetPlayerSummaries per il sottoinsieme degli account bannati, deduplicato in base allo SteamID64. La data di creazione corrisponde alla data di apertura dell’account, non a quella del ban né a quella in cui è iniziata l’attività di farming; in questo contesto viene considerata come indicatore della recente formazione del gruppo, non dell’intenzionalità. Tre aspetti che il grafico non mostra:\n\nUna tendenza dopo il 2024. Un account creato nel 2025 o nel 2026 ha avuto meno tempo per incorrere in un ban, e il 2026 copre nove mesi — quindi 227,030 → 121,070 → 16,534 indica una censura, non un calo.\nUn tasso di rifiuto. I dati relativi agli anni di creazione sono stati rilevati solo per gli account bloccati, quindi non c'è un denominatore. Il solo aumento del numero di utenti installati produrrebbe questo andamento.\nPerché il 2021 è stato un anno disastroso. 51,701 si trova tra 105,821 e 104,641, a meno della metà della distanza da ciascuno dei due vicini. Non vi è alcuna spiegazione pubblica al riguardo; è lasciato visibile anziché essere livellato.\n04 — Tempistica\nQuando Valve entra in vigore, lo fa entro il primo anno\n\nLa giustificazione più ovvia per il fatto che 88.97% non sia stato modificato è l’arretrato. I divieti datati dicono il contrario.\n\nDa quanto tempo esisteva l'account quando è stato applicato il ban\n\nAnzianità dell'account al momento del ban, per i 293,750 account bannati per i quali sono disponibili sia la data di creazione che la data dell'ultimo ban. Più della metà è stata individuata entro il primo anno.\n\n0%\n10%\n20%\n30%\n40%\n<6 mo\n33.7%\n6–12 mo\n21.5%\n1–2 y\n20.6%\n2–5 y\n14.3%\n5 y+\n10.0%\n55.1% inside the first year\nBandito entro il primo anno — 55.1%Successivamente bandito — 44.9%\n0,80 yEtà mediana dell'account al momento dell'imposizione del ban\n55.1%Sospeso entro il primo anno dall'apertura dell'account\n33.7%Sospeso nei primi sei mesi\n293,750Account in cui sono presenti entrambe le date\n\nQuesta è la risposta all’ovvia obiezione. Se il 88.97% della flotta non viene toccato semplicemente perché l’applicazione delle norme è lenta — c’è un arretrato da smaltire — allora i divieti che fare si potrebbe pensare che i dati risultino distorti verso l'alto. In realtà è il contrario: l'età mediana degli account sospesi era di nove mesi e mezzo, e un terzo — 33.7% — è stato catturato nel giro di sei mesi. Quando Valve agisce su questa popolazione, lo fa rapidamente. I nove su dieci ancora in libertà non stanno aspettando in fila.\n\nEtà al momento del divieto = data di creazione a partire dal GetPlayerSummaries sottratta dalla data di divieto implicita in Giorni dall’ultimo ban, continua a leggere 2026-09-23. Viene calcolato solo quando entrambi i valori sono presenti: 293,750 dei 1,200,011 account bloccati. Gli account rimanenti non riportano alcun valore relativo ai giorni trascorsi e vengono omessi, non ipotizzati — quindi interpretate questo dato come la composizione del sottoinsieme datato, non di ogni singolo blocco.\n\n05 — In cosa consiste effettivamente il divieto\nQuando Valve si attiva, non blocca il bot\n\nTra i 11% soggetti a qualche divieto, verifica di quale divieto si tratti.\n\nUn ban non è un ban. Dei 1,200,011 account segnalati da Valve, 99.8% portare con sé un comunità divieto — una restrizione su forum, profili e gruppi che non ha alcun effetto su un bot di scambio. L’account può comunque ricevere carte, effettuare scambi e gestire l’inventario. 22.2% comporta almeno un ban di gioco e 3.9% un ban di VAC; le categorie si sovrappongono, quindi non si sommano. L’unica sanzione che interrompe effettivamente lo scambio, ovvero il ban economico/commerciale, è applicata a 5,214 account. Non stiamo basando la nostra argomentazione su quel numero: i divieti di scambio sono rari in generale su Steam. Il punto di questo grafico è più semplice: anche la frazione Valve fa Touch continua a operare.\n\nPer quale motivo vengono effettivamente banditi gli utenti contrassegnati con 11%?\n\nCiascuna tipologia di blocco rappresenta una percentuale del totale dei membri 10,880,610 sottoposti a scansione. Un account può presentare più di una tipologia. Passa il mouse per visualizzare i conteggi.\n\n0%\n4%\n8%\n11%\n15%\nCommunity ban\nGame ban\nVAC ban\nEconomy / trade ban\n\nUn divieto di tipo Steam non prevede un campo “motivo”, quindi nessuno di questi divieti è attribuito specificatamente al “card farming” — si tratta piuttosto della combinazione dei tipi di divieto presenti, affiancata da ciò che ciascun tipo limita effettivamente. Il divieto imposto dalla comunità non impedisce lo scambio; il divieto economico/commerciale sì. Riepilogo: asf-ban-census-2026-09-23.json.\n\n06 — L'altra popolazione\nI truffatori Valve, andiamo avanti: il censimento completo 51,732\n\nUn secondo elenco indipendente — frodi confermate dalla comunità — confrontato con la stessa API ufficiale.\n\nSi potrebbe sostenere che il gruppo degli automatizzati sia composto da oziosi innocui. Non si può dire lo stesso del secondo gruppo. SteamRep è un database di reputazione della comunità attivo da molto tempo; un account contrassegnato VIETATO quella comunità ha giudicato una persona come truffatore, sulla base di prove documentate fornite dalle vittime e dei log delle chat relative alle transazioni. Abbiamo completato un censimento 100% di tutti i 51,732 profili contrassegnati dallo stato “BANNATO” rispetto all'API Web ufficiale di Steam (ISteamUser/GetPlayerBans/v1) — e sono state conteggiate solo le sanzioni relative alle truffe. Una sospensione VAC riguarda l’uso di software per barare in un gioco (aimbot, wallhack); non ha alcun effetto su un trader e non costituisce una prova Valve di frode, quindi non viene considerata come misura contro le frodi.\n\nNell'ambito dell'intero censimento degli account 51,732, 67.77% — 35,059 dei quali sono stati riconosciuti come truffatori — non presentano ALCUN ban relativo a truffe da parte di Valve: possono ancora effettuare scambi, inviare richieste di amicizia a nuove vittime e inviare messaggi. Solo 32.23% hanno subito un ban dalla community o uno dagli scambi, e il ban dagli scambi — l’unica misura che impedisce effettivamente i trasferimenti di inventario — riguarda solo 18.81% (9,731 account). Altri 12.81% (6,627 account) hanno ricevuto VAC ban di gioco esclusivamente per aver barato, pur rimanendo completamente liberi di effettuare Steam scambi.\n\nTruffatori confermati, a seconda che Valve abbia applicato un ban correlato alla truffa (Censimento completo)\n\nTutti i profili 51,732 SteamRep-BLOCCATI, suddivisi a seconda che Valve abbia applicato un blocco per motivi comunitari o commerciali. I blocchi VAC e quelli relativi al gioco sono esclusi, in quanto non riguardano casi di frode. Passa il mouse per visualizzare i conteggi.\n\n0%\n18%\n35%\n53%\n70%\nNo scam-relevant ban\nCommunity or trade ban\n0%\n6%\n13%\n19%\n25%\nCommunity ban\nTrade / economy ban\nVAC (not fraud)\nGame ban\n51,732SteamRep profili BANNATI sottoposti a verifica — 100% censimento completo\n35,059Non è soggetto ad alcun ban relativo a truffe (67.77%)\n18.81%Portare avanti il divieto commerciale che mette fine alle truffe (9,731)\n32.23%La quota Valve è stata oggetto di un divieto comunitario o commerciale (16,673)\n\nSteamRep è un database di reputazione di terze parti, valutato dalla comunità, non una determinazione Valve — ed è proprio questo il punto: prove esterne, confrontate con ciò che Valve stesso ha fatto. Tutti i profili 51,732 BANNATI dall’esportazione canonica sono stati confrontati direttamente con ISteamUser/GetPlayerBans/v1. Per \"correlato a frodi\" si intende un ban dalla community o un divieto di attività economiche/commerciali; VAC (12.81%) e i ban dal gioco (3.86%) vengono conteggiati separatamente poiché riguardano il cheating e non le frodi. Set di dati completo dell'audit: steamrep_steam_bans.csv.\n\nDue popolazioni, un unico risultato\n\nNon si tratta delle stesse persone né dello stesso comportamento. Da un lato ci sono dieci milioni di account automatizzati; dall’altro, cinquantatremila truffatori condannati. Ciò che hanno in comune è la forma del risultato: nove conti agricoli su dieci non vengono mai utilizzati, e oltre i due terzi (67.77%) dei truffatori accertati non subiscono alcuna sanzione relativa alla frode. Il ban della community Valve limita liberamente l’accesso ai forum e ai profili, non le transazioni commerciali. Il pulsante “Segnala”, il database della reputazione, il ban che blocca una truffa: sono tutti presenti, ma sottoutilizzati. Mettiamo questo a confronto con i rifiuti archiviati nel fascicolo principale, dove la stessa azienda rimuove definitivamente un singolo account e cita come motivo l’uso commerciale e l’automazione: la clausola non è inattiva, è ben precisa.\n\n07 — Il caso \"$5.00\" e il furto di account\nL’analisi empirica degli account “100,000”: le botnet non sono account gratuiti usa e getta\n\nLogica del campionamento statistico e dimostrazione matematica: perché considerare qualsiasi altro valore di 100,000 porta esattamente allo stesso risultato.\n\nLa principale argomentazione di Valve nei confronti delle autorità di regolamentazione e degli organismi di tutela dei consumatori è stata che le truffe automatizzate e il “farming” vengono messi in atto tramite account effimeri e gratuiti, detti “usa e getta”, che vengono rapidamente bloccati. In base alle regole pubblicate da Valve, un account è Limitato finché non spende almeno 5.00i USD nel negozio Steam, il che ne impedisce l'utilizzo per le transazioni, le richieste di amicizia e le funzionalità API. Abbiamo verificato direttamente questa affermazione testando lo stato di monetizzazione di un campione rappresentativo e matematicamente rigoroso di 100,000 account bloccati Steam tratti dal nostro corpus di metadati dei profili 1,182,811.\n\nPROTOCOLLO DI CAMPIONAMENTO (SRSWOR)\n100,000 Sezione imparziale\n\nTratto da N = 1,182,811 account unici Steam banditi utilizzando un campionamento casuale semplice senza sostituzione tramite un generatore di numeri casuali (PRNG) crittograficamente uniforme. Ogni account aveva una probabilità di inclusione identica pari a P = n / N ≈ 8.45%, eliminando completamente il bias di sopravvivenza e quello di attività.\n\nDIMOSTRAZIONE MATEMATICA\nMargine di errore < ±0.4%\n\nApplicando la formula della correzione per popolazione finita (FPC) a un 99% Intervallo di confidenza (Z = 2,576):\nMoE = Z × √[p(1-p)/n] × √[(N-n)/(N-1)] ≈ ±0.39%\n\nRIPRODUCIBILITÀ\nPerché qualsiasi cifra di 100k dà lo stesso risultato\n\nPoiché il margine di errore è limitato a ±0.4% con un livello di confidenza pari a 99%, è matematicamente garantito che qualsiasi altro campione indipendente tratto dall’account 100,000 rientri nell’intervallo 63.06% ± 0.39% (da 62.67% a 63.45%). Il campione è rappresentativo dell'intera popolazione di 1,18 milioni di persone soggette a divieto.\n\nI risultati dell'audit smontano completamente la tesi del \"bot usa e getta\". Dei 100,000 account sottoposti ad audit tramite l'interfaccia XML legacy di Steam: 61,490 account (63.06% tra gli account classificati) sono account non limitati (a pagamento) che hanno speso almeno $5.00 su Steam. Solo 36,021 (36.94%) sono account gratuiti con funzionalità limitate, mentre 2,489 erano account non configurati o privati.\n\n100,000 Account bloccati: a pagamento ($5+ spesa nello store) vs status limitato gratuito\n\nVerifica empirica su 100,000 account bloccati selezionati a caso. Oltre 63% hanno superato il controllo finanziario a pagamento di Valve. Passa il mouse per visualizzare i conteggi.\n\n0%\n16%\n33%\n49%\n65%\nNon-limited (Paid ≥ $5.00)\nLimited (Free < $5.00)\n100,000Popolazione campionata (SRSWOR, N=1,18 milioni)\n63.06%Account a pagamento senza limitazioni (account 61,490)\n±0.39%Margine di errore nell'intervallo di confidenza a 99%\n~745,800Account a pagamento estrapolati da un corpus di 1,18 milioni di account bannati\nLa realtà strutturale: la liquidazione dei conti su scala industriale\n\nPerché 63% degli account bannati inclusi nel campione dovrebbero essere account a pagamento che hanno speso denaro reale nel negozio di Valve? Gli operatori di botnet non spendono milioni di tasca propria per account usa e getta. Questo rapporto evidenzia il volume di account compromessi e dirottati che circola all’interno dell’ecosistema.\n\nQuesta scala è direttamente osservabile sulle piattaforme underground: su mercati come FSB Market (nome anonimizzato; il nome originale non è indicato qui), oltre a 550,000 Steam account (log di furti, dati raccolti tramite phishing, credential stuffing) sono attivamente messi in vendita in qualsiasi momento (phishdestroy.io/live-intel). Il mercato verifica l'identità di acquirenti e venditori utilizzando l'OpenID Steam proprio di Valve, e né FSB Market né il forum associato è bloccato dal filtro dei collegamenti di Valve.\n\nCome stabilito nella Sezione 06, Valve non elimina in modo proattivo questa attività fraudolenta: 67.77% dei truffatori segnalati dalla comunità non hanno ricevuto alcuna sospensione per truffa su Steam, e il 88.97% della flotta automatizzata rimane del tutto intatto. Gli account circolano liberamente, effettuano l’autenticazione tramite API ufficiali e effettuano operazioni di trading all’interno dell’ecosistema con impunità quasi totale.\n\nDiagramma dell'architettura delle prove forensi e delle misure di applicazione della legge\nFlusso interattivo da 10,88 milioni di account analizzati a 100.000 casi empirici e 53.500 truffatori confermati · Clicca sui link per esaminare le prove grezze\nLivello 01 · 10,88 milioni: censimento della flotta di automazione\nLa più grande popolazione di bot che si autodefinisce come “automazione” su Steam è stata sottoposta in sequenza all’API di blocco ufficiale di Valve. Ciò dimostra che le flotte di bot commerciali operano con 88.97% impunità pur pagando decine di milioni in quote di iscrizione.\n9,680,599 88.97% Attivo e intatto\nAccount che utilizzano software automatizzati e che non presentano alcun tipo di sospensione nel proprio storico.\nDati grezzi del censimento in formato JSON (1,2 KB) ↗Controllare la sezione 01 ↗\n$26,802,495 Soglia minima dei ricavi diretti dei punti vendita\nRaccolti da Valve membri non soggetti a limiti tra i 5,360,499 che hanno superato la soglia minima di $5.00 per l'accesso.\nVerifica dell'economia delle carte ↗Valve $5 Domande frequenti sulle regole ↗\n1,200,011 11.03% Sottoinsieme contrassegnato\n99.8% prevede solo divieti di natura puramente estetica; il trading rimane aperto sul 99.95% degli account.\nRipartizione per tipo di ban ↗Database bloccato (60,4 MB) ↓\nLivello 02 · 100,000-Verifica di campionamento empirico dei conti (N = 1,182,811)\nCampione rappresentativo di SRSWOR fette valutato tramite endpoint XML legacy. Margine di errore matematicamente dimostrato < ±0.4% con un intervallo di confidenza di 99%. Confuta l’affermazione secondo cui i bot bannati sarebbero account gratuiti usa e getta.\n61,490 (63.06%) Account a pagamento senza limiti (spesa $5+)\nOltre 63% degli account bloccati corrispondono a transazioni a pagamento. Ciò si traduce in circa 745,800 account a pagamento (soglia minima di $3.73M+) nel gruppo degli account bloccati.\nRisultati limitati in formato CSV (2,1 MB) ↓Rapporto forense da 100k ↗\n36,021 (36.94%) Account gratuiti con funzionalità limitate (< $5.00)\nLa minoranza dei profili bloccati che corrispondeva alla definizione di \"bot usa e getta\" fornita da Valve. Gli account 2,489 erano non configurati o privati.\nSezione di campione da 100k in formato CSV (8,5 MB) ↓Analisi delle spese MD ↗\n34.67% contro 63.93% Verifica della sanificazione dei profili\nValve ha sostituito i nickname con gli SteamID64 grezzi su 34,673 account, ma ha lasciato invariati i nomi personalizzati e gli avatar su 63,928 account bannati.\nSezione Igienizzazione ↗Panoramica - Roadmap ↗\n34.59% Legacy Account archiviati (creati tra il 2003 e il 2019)\nOltre un terzo degli account bloccati era stato registrato da 5 a oltre 20 anni fa, a dimostrazione di un fenomeno di appropriazione indebita di account su scala industriale ai danni di giocatori di lunga data Steam.\nCronologia per età ↗Rifiuti di assistenza ↗\nLivello 03 · 51,732 SteamRep Censimento dei truffatori confermati\nCensimento completo 100% dei truffatori segnalati dalla comunità, con log delle chat delle vittime e prove delle transazioni, incrociato con le API ufficiali Steam relative ai ban. Dimostra il fallimento sistemico delle misure di contrasto.\n35,059 (67.77%) Nessun ban per truffa (totale impunità)\nOltre due terzi dei truffatori identificati non sono soggetti ad alcun divieto di accesso alla community né di trading da parte di Valve. Sono pienamente operativi per effettuare operazioni di trading e aggiungere nuove vittime.\nSteamRep Divieti relativi alle API (2,6 MB) ↓SteamRep Relazione di revisione ↗\n9,731 (18.81%) Economia / Divieti commerciali\nL'unica sanzione che interrompe la liquidazione delle scorte. Presente in meno di un quinto dei casi di truffatori confermati.\nSteamRep Fonte (2,1 MB) ↓Consultare la Sezione 06 ↗\n6,627 (12.81%) Sospensioni per frode irrilevanti (solo VAC)\nBannati per l'uso di aimbot e wallhack nei giochi, mentre le loro attività di Steam scambio e phishing rimangono 100% attive.\nVAC Analisi dell'irrilevanza ↗Cronologia della sicurezza ↗\nLivello 04 · Attacchi di defacement ai siti wiki e violazioni delle infrastrutture nell'agosto 2026\nManomissione della documentazione interna per gli sviluppatori, limitazione delle funzionalità dell’editor della community e falle nella sicurezza perimetrale non risolte, documentate nel fascicolo probatorio.\n1,200+ Redattori Registri dei conflitti di VDC Wiki\nGli editori della community che cercavano di correggere i link di phishing e i modelli di spam venivano sistematicamente bloccati dai filtri automatici, mentre il personale Valve ignorava gli avvisi.\nRapporto sui conflitti in Russia (127 KB) ↗Rapporto di classificazione (66 KB) ↗\n12 TB senza autenticazione Agosto 2026: perdita di risorse (CWE-284)\nValve ha ospitato per settimane 12 terabyte di codice interno e versioni prototipali su un endpoint pubblico aperto senza autenticazione.\nValve Dossier sull’incompetenza (43 KB) ↗Archivio delle prove ↗\nViolazione dei dati presso CEVA Logistics Agosto 2026: fuga di dati personali dei clienti\nI nomi, gli indirizzi e i numeri di telefono degli acquirenti europei di Steam Deck sono trapelati dal partner logistico di Valve, scatenando ondate di attacchi di phishing.\nRegistro degli incidenti ↗Registro delle misure esecutive ↗\n\nArtefatto di campionamento: banned_100k_slice.csv (100,000 conti). Risultati della revisione: slice_100k_limited_results.csv. Rapporto analitico completo: BANNED_100K_FORENSIC_ANALYSIS.md.\n\n08 — Metodo e limiti\nCome è stato interpretato questo testo e cosa non sostiene\n\nTre popolazioni pubbliche, un'API pubblica, campionamento statistico rigoroso.\n\nESECUZIONE E CREDENZIALI\n\nIl censimento ASF, l'100,000-account SRSWOR e il controllo incrociato SteamRep sono stati eseguiti da PhishDestroy partecipanti utilizzando i propri Steam account e le proprie chiavi API Web, nell’ambito dell’attività pubblica della Coalizione volta a contrastare il phishing e a vietare le truffe. L’autore del dossier non possiede alcuna chiave API Web Steam e non ha eseguito personalmente alcuna scansione in tempo reale. L’aggregazione, l’hashing, la verifica e la pubblicazione sono state effettuate sulla base dei risultati forniti dai partecipanti.\n\nPopolazione\tDa dove proviene\tCosa è stato letto\nMembri dell'ASF\n10,880,610\tL'elenco pubblico dei membri del gruppo della community ArchiSteamFarm Steam. La pagina del gruppo di Steam mostra 5,360,499 membri (solo quelli senza limitazioni); l'elenco dei membri restituito dall'API conteneva 10,880,610 voci in totale, inclusi gli account con limitazioni. L'iscrizione al gruppo avviene automaticamente al primo avvio, a meno che l'utente non disattivi esplicitamente l'impostazione predefinita di iscrizione al gruppo nella configurazione (AutoJoinSteamGroup / Statistiche), il che significa che l'elenco dei membri comprende cluster di bot commerciali, singoli utenti inattivi con carte e giocatori abituali che hanno lasciato attiva l'opzione predefinita.\tGetPlayerBans per ogni membro (segnalazioni di ban); GetPlayerSummaries per data di creazione e paese. Raggruppati in lotti da 100 ID, deduplicati in base allo SteamID64.\n100.000 account bloccati SRSWOR Slice\n100,000\tUn campione rappresentativo estratto in modo casuale e uniforme senza sostituzione dal corpus dei 1,182,811 account bannati ($P = 8,45\\%$). La correzione per popolazione finita fornisce un margine di errore di $\\pm 0,39\\%$ a un livello di confidenza 99% ($Z = 2,576$).\tMonetizzazione e stato di account limitato (isLimitedAccount) verificato tramite l’interfaccia del profilo XML legacy di Steam (?xml=1) tramite pipeline proxy distribuite. Conferma lo stato 63.06% (pagato).\nSteamRep truffatori\n51,732\tCensimento completo 100% di tutti i profili contrassegnati come BANNATI nel database SteamRep relativo alla reputazione della comunità (51,732 profili in totale). Non è stato applicato alcun campionamento né filtraggio.\tISteamUser/GetPlayerBans/v1 per tutti gli account 51,732, incrociati con lo stato SteamRep. Conferma che 67.77% non è soggetto ad alcun divieto per truffa.\nOggetto della rivendicazione\n\nSolo tassi empirici e stime statisticamente circoscritte. Nella popolazione automatizzata, 88.97% non presentano alcun blocco; il sottoinsieme dei profili bloccati è sbilanciato verso il recente (70% dal 2020). Nella verifica empirica degli account 100,000, 63.06% degli account bannati sono a pagamento (non soggetti a limitazioni), con un margine di errore matematicamente dimostrato inferiore a ±0.4%. Tra i 51,732 truffatori confermati, 67.77% non presentano alcun blocco correlato alla truffa. Ogni dato è riproducibile tramite la Web API di Valve.\n\nCosa non viene rivendicato\n\nUn ban Steam non prevede un campo per la motivazione, quindi in questo caso il ban non è attribuito a una causa specifica. L’appartenenza a un gruppo non costituisce prova che un account sia un bot automatizzato: poiché ASF abilita l’adesione ai gruppi per impostazione predefinita, a meno che non venga deselezionata manualmente, la popolazione comprende sia account commerciali gestiti da farm con più account, sia account personali di giocatori comuni e appassionati. Il Paese è dichiarato dall’utente stesso e una segnalazione contrassegnata con SteamRep rappresenta una decisione della comunità, non un verdetto giudiziario. Non viene citato alcun nome.\n\nPerché è importante\n\nValve dispone della stessa API, di un proprio database sottostante e dei motivi di ban che questa scansione non è in grado di rilevare. È in grado di eseguire questa query sull’intero spazio degli ID in pochi secondi. La metrica che consentirebbe a una parte esterna di verificare un’affermazione relativa all’applicazione delle norme su un determinato numero non è mai stata pubblicata dall’unica parte in grado di produrla con la massima accuratezza. Questa è una stima esterna, fornita affinché la domanda possa essere formulata con un dato numerico a corredo.\n\nLeggi anche: l'economia basata sulle carte di cui si occupa questa popolazione → · assistenza in caso di accesso non autorizzato e furto → · il dossier completo →",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Quanto è grande la farm di Steam? L’abbiamo contata noi."
          },
          {
            "level": 2,
            "id": null,
            "text": "Dieci milioni di conti, di cui nove su dieci non sono stati toccati"
          },
          {
            "level": 3,
            "id": null,
            "text": "ASF si unisce al gruppo per te"
          },
          {
            "level": 3,
            "id": null,
            "text": "10,880,610 voci totali"
          },
          {
            "level": 3,
            "id": null,
            "text": "88.97% pulito"
          },
          {
            "level": 3,
            "id": null,
            "text": "Tra i 10,880,610 conti, quanti Valve sono stati utilizzati?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Quanto è già costato a questa flotta Valve per esistere"
          },
          {
            "level": 2,
            "id": null,
            "text": "Dove si trova la flotta"
          },
          {
            "level": 3,
            "id": null,
            "text": "Account sospesi per paese dichiarato"
          },
          {
            "level": 2,
            "id": null,
            "text": "Dati recenti, non un arretrato storico"
          },
          {
            "level": 3,
            "id": null,
            "text": "Quando sono stati creati gli account bloccati"
          },
          {
            "level": 2,
            "id": null,
            "text": "Quando Valve entra in vigore, lo fa entro il primo anno"
          },
          {
            "level": 3,
            "id": null,
            "text": "Da quanto tempo esisteva l'account quando è stato applicato il ban"
          },
          {
            "level": 2,
            "id": null,
            "text": "Quando Valve si attiva, non blocca il bot"
          },
          {
            "level": 3,
            "id": null,
            "text": "Per quale motivo vengono effettivamente banditi gli utenti contrassegnati con 11%?"
          },
          {
            "level": 2,
            "id": null,
            "text": "I truffatori Valve, andiamo avanti: il censimento completo 51,732"
          },
          {
            "level": 3,
            "id": null,
            "text": "Truffatori confermati, a seconda che Valve abbia applicato un ban correlato alla truffa (Censimento completo)"
          },
          {
            "level": 4,
            "id": null,
            "text": "Due popolazioni, un unico risultato"
          },
          {
            "level": 2,
            "id": null,
            "text": "L’analisi empirica degli account “100,000”: le botnet non sono account gratuiti usa e getta"
          },
          {
            "level": 3,
            "id": null,
            "text": "100,000 Sezione imparziale"
          },
          {
            "level": 3,
            "id": null,
            "text": "Margine di errore < ±0.4%"
          },
          {
            "level": 3,
            "id": null,
            "text": "Perché qualsiasi cifra di 100k dà lo stesso risultato"
          },
          {
            "level": 3,
            "id": null,
            "text": "100,000 Account bloccati: a pagamento ($5+ spesa nello store) vs status limitato gratuito"
          },
          {
            "level": 3,
            "id": null,
            "text": "La realtà strutturale: la liquidazione dei conti su scala industriale"
          },
          {
            "level": 2,
            "id": null,
            "text": "Come è stato interpretato questo testo e cosa non sostiene"
          },
          {
            "level": 3,
            "id": null,
            "text": "Oggetto della rivendicazione"
          },
          {
            "level": 3,
            "id": null,
            "text": "Cosa non viene rivendicato"
          },
          {
            "level": 3,
            "id": null,
            "text": "Perché è importante"
          }
        ],
        "links": [
          "https://help.steampowered.com/en/faqs/view/71D3-35C2-AD96-AA3A",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/asf-ban-census-2026-09-23.json",
          "https://phishdestroy.io/steam_dossier/it/VALVE_EVIDENCE_PACK/databases/steamrep_steam_bans.csv",
          "https://phishdestroy.io/live-intel/?category=steam",
          "https://phishdestroy.io/steam_dossier/it/card_economy.html",
          "https://phishdestroy.io/steam_dossier/it/VALVE_EVIDENCE_PACK/databases/banned_archiasf_massive.csv",
          "https://phishdestroy.io/steam_dossier/it/VALVE_EVIDENCE_PACK/databases/slice_100k_limited_results.csv",
          "https://phishdestroy.io/steam_dossier/it/VALVE_EVIDENCE_PACK/reports/BANNED_100K_FORENSIC_ANALYSIS.md",
          "https://phishdestroy.io/steam_dossier/it/VALVE_EVIDENCE_PACK/databases/banned_100k_slice.csv",
          "https://phishdestroy.io/steam_dossier/it/VALVE_EVIDENCE_PACK/reports/STEAM_BANNED_LIMIT_ANALYSIS.md",
          "https://phishdestroy.io/steam_dossier/it/VALVE_EVIDENCE_PACK/INVESTIGATION_OVERVIEW.md",
          "https://phishdestroy.io/steam_dossier/it/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/it/VALVE_EVIDENCE_PACK/reports/STEAMREP_VS_STEAM_AUDIT.md",
          "https://phishdestroy.io/steam_dossier/it/VALVE_EVIDENCE_PACK/databases/SteamRep_Profiles_BannedCaution_2024.csv",
          "https://phishdestroy.io/steam_dossier/it/security_timeline.html",
          "https://phishdestroy.io/steam_dossier/it/VALVE_EVIDENCE_PACK/reports/russian_conflicts_report.json",
          "https://phishdestroy.io/steam_dossier/it/VALVE_EVIDENCE_PACK/reports/classification_report.json",
          "https://phishdestroy.io/steam_dossier/it/VALVE_EVIDENCE_PACK/reports/VALVE_INCOMPETENCE_REPORT.md",
          "https://phishdestroy.io/steam_dossier/it/steam_evidence_archive.html",
          "https://phishdestroy.io/steam_dossier/it/steam_enforcement_evidence.html",
          "https://phishdestroy.io/steam_dossier/it/#insider-threat",
          "https://phishdestroy.io/steam_dossier/it/"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/it/enforcement_audit.content.json",
      "export_json_sha256": "1d26f69e7554f30189859683626c2e8753f0913b24508f14398ad072febaebdc"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "it/index.html",
      "language": "it",
      "title": "Il dossier Steam: regole, percorsi e responsabilità",
      "source_url": "https://phishdestroy.io/steam_dossier/it/index",
      "source_html_sha256": "b7ed32ff10aac7e2fc217fb4b6172ade944480c05d2dd0706c2e389f2e45d0c0",
      "exported_at": "2026-09-29T00:17:54.413Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "exhibit-gallery-section",
            "source": "https://phishdestroy.io/steam_dossier/it/index#exhibit-gallery-section"
          }
        ],
        "raster_images_replaced": 2
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "index.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/it/index.pdf?v=print-20260929-v5",
        "sha256": "8c301ec21c24ca9a2f0c5b8317375e6d7f2e243a3095355837fb2ccdea3b78fa",
        "bytes": 965436,
        "pages": 107
      },
      "integrity": {
        "signed_object": "index.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "index.content.json.asc",
        "digest_file": "index.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify index.content.json.asc index.content.json",
          "sha256sum -c index.content.json.sha256"
        ]
      },
      "content": {
        "text": "Sezione 1 — Sintesi del caso\nLa regola. Il record. Le domande senza risposta.\nContesto e limiti della fonte\n\nSei risultati, ciascuno collegato a un documento pubblico datato. Le sezioni dettagliate seguono lo stesso ordine: documentazione tecnica (Parte A), normativa e applicazione (Parte B), quadri giuridici (Parte C), seguite dalle appendici con gli allegati principali.\n\nSei risultati. Ciascuno collega una norma scritta a un documento datato e a una questione che può essere verificata sulla base delle prove.\n\n1. Host di autenticazione con domini separati — 44 percorsi · 26 coppie separate\n\nI registri dei disoccupati 44 piattaforme che effettuano l'autenticazione tramite un dominio separato registrabile. Altre cinque rotte sono in attesa di verifica e di una data RDAP; la loro inclusione porterebbe il totale a 47. Esse sono escluse dal numero 44 e dalla tabella delle età. — 27 con un file di prove pubblicato per ogni percorso e 17 aggiunti tramite raccolta manuale, elencati a parte. In 26 coppie di filtri separati il dominio principale è BLOCCATO nel filtro dei link Steam, mentre il proxy che ne gestisce l'accesso non lo è. Non si tratta di domini temporanei: csgogem.com è bloccato mentre api.csgem.com, l'host con nome di accesso Steam, è registrato dal marzo 2014 — 12 anni e 6 mesi. Valve riceve quel nome host in ogni richiesta OpenID e lo ripropone all'utente nella propria pagina di accesso. La tabella completa, con le durate per ogni route e le informazioni sulla provenienza, è riportata nella Sezione 3.\n\nSegui il percorso →\n2. 2016: il meccanismo è stato denominato e la scadenza è stata fissata\n\nIl 13 luglio 2016 Valve ha descritto pubblicamente come i siti di gioco d’azzardo utilizzassero Steam OpenID e conti di trading automatizzati, e le comunicazioni del suo legale del 20 luglio 2016 hanno fissato un termine di dieci giorni. Da allora non è stato pubblicato alcun resoconto sulle azioni di applicazione della normativa per singolo operatore. A dieci anni dalla scadenza fissata, lo stesso meccanismo citato è in uso su host di autenticazione con domini separati che non hanno restituito alcun blocco da parte di Link Filter su 2026-09-21.\n\nLeggi la lettera aperta al WSGC →\n3. Correlazione dei dispositivi, su carta intestata dell’avvocato\n\nNella corrispondenza qui riportata, il legale di Valve ha descritto una correlazione a livello di dispositivo che collega un dispositivo a più account — una funzionalità che il servizio di assistenza di Steam aveva precedentemente dichiarato agli utenti non essere tecnicamente possibile. Resta da chiarire quali dati relativi ai dispositivi siano in possesso di Valve e su quale base venga negato ai titolari degli account l’accesso a tali dati.\n\nLeggi il memorandum →\n4. Due risposte relative all’accesso. Una ha negato l’accesso ai dati, l’altra li ha divulgati.\n\nOttobre 2025: L’avvocato di Valve ha risposto a una richiesta ai sensi dell’articolo 15 presentando un’appendice di 830 pagine in cui le parti oscurate sono state coperte con del colore anziché essere rimosse — 902,270 caratteri riferire i dati utilizzando uno strumento di estrazione standard, compresi gli identificatori di terze parti che proprio quelle barre avevano lo scopo di nascondere. L’articolo 15, paragrafo 4, è il motivo per cui esistono quelle barre. Settembre 2026: Il ticket HT-2YBP-F7JP-D4VB è stato chiuso dopo tre giorni con un link alla pagina self-service “Dati dell’account”: nessun dato, nessuna base giuridica indicata. Al momento della pubblicazione, il termine di un mese previsto dall’art. 12, comma 3, non era ancora scaduto; l’obiezione riguarda il merito della questione.\n\nLeggi la verifica della redazione →Leggi la scheda del biglietto →\n5. Il mercato al di sopra del massimo di Steam\n\nSteam limita la quotazione in Borsa a circa $1,800. In cinque mercati, in una panoramica datata (23 settembre 2026), 248 categorie di articoli CS2 il cui prezzo superi tale limite da parte di due o più di essi, indipendentemente l'uno dall'altro, e tutti e 248 sono assenti da Steam; un Dragon Lore nuovo di fabbrica parte da $10,941 su 389 copie presenti in tutte e cinque le piattaforme (il dato relativo esclusivamente a CSFloat riportato nella Sezione 13, tratto dall’istantanea del 20 settembre, è pari a $10,623.95 su 62 offerte). La vendita a tali prezzi richiede una piattaforma esterna, mentre il trasferimento degli articoli avviene ancora a Steam.\n\nSegui l'andamento del prezzo e il trasferimento →\n6. La regola è esplicita; la traccia di controllo non lo è\n\nIl Contratto di abbonamento riserva Steam all’uso personale e non commerciale, vieta lo sfruttamento commerciale salvo nei casi espressamente consentiti, proibisce l’uso di script e bot e consente la chiusura dell’account. Nel 2016, Valve ha esteso tale disposizione agli operatori di gioco d’azzardo. Separatamente, secondo l’account tecnico di CSFloat, Valve ha chiuso IEconItems_730/GetPlayerItems nel 2017, con la rimozione dell'accesso pubblico agli ID degli elementi originali (non è stato individuato alcun log delle modifiche Valve).\n\nPosiziona la regola accanto alla rete →\n2016 / Richiesta scritta 10 giorni\nScadenza indicata nelle comunicazioni inviate nel luglio 2016 dall’avvocato Valve ai siti di gioco d’azzardo. Lettera aperta alla WSGC: Sezione 2.\n2017 / Registro di audit pubblico Accesso tramite ID disattivato\nCSFloat registra la perdita degli ID originali degli elementi.\nCorrispondenza legale Correlazione tra dispositivi\nUn dispositivo collegato a decine di account rubati.\nRegistro dei percorsi Bloccato, ma continuo ad accedere\nLa regola: La dichiarazione del 2016 di Valve vieta la gestione di attività di gioco d'azzardo su Steam OpenID. Il record: Il Link Filter ospita 26 domini principali, mentre l'host che gestisce l'accesso Steam di ciascuno di essi è in funzione da — quello di csgogem.com è in funzione da 12 anni e 6 mesi.\nSezione 2 — Lettera aperta\nLettera aperta alla Commissione per il gioco d'azzardo dello Stato di Washington\n\nDieci giorni sono diventati dieci anni. Alla richiesta avanzata dalla Commissione nel 2016 a Valve non è stata fornita una risposta con un resoconto operatore per operatore; la presente lettera chiede alla Commissione di riaprire il fascicolo.\n\nCOMUNICATO STAMPA · COMMISSIONE PER IL GIOCO D'AZZARDO DELLO STATO DI WASHINGTON\n\nDieci giorni sono diventati dieci anni.Riaprire il record.\n\nAlla Commissione per il gioco d'azzardo dello Stato di Washington:\n\nNel 2016, il direttore David Trujillo ha chiesto a Valve di illustrare le misure adottate per impedire l’uso delle skin Steam a fini di gioco d’azzardo. L’allora presidente Chris Stearns e la Commissione si sono trovati di fronte a un settore basato su oggetti emessi da Valve e trasferimenti di Steam. Da allora entrambi hanno lasciato i loro incarichi in seno alla Commissione. La questione che hanno sollevato riguardo a Valve non è ancora stata risolta.\n\nIl responsabile legale di Valve, Karl Quackenbush, ha concesso agli operatori del settore del gioco d’azzardo dieci giorni di tempo per cessare l’uso commerciale degli account Steam. Nella sua risposta di ottobre alla vostra Commissione, Valve ha negato di aver facilitato il gioco d’azzardo, affermando di aver inviato lettere di diffida a più di quaranta siti e di aver disattivato gli account associati. Ha inoltre difeso il mantenimento dei servizi di trading Steam e OpenID, poiché tali servizi andavano a vantaggio dei clienti e degli sviluppatori di giochi. Quella era una dimostrazione di controllo. Merita di essere messa alla prova, non di essere accettata senza discutere.\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\nA nostro avviso, la risposta di Valve non ha dimostrato che le misure di applicazione da essa scelte fossero commisurate alle dimensioni della rete da essa descritta. Una lettera di minaccia inviata a un operatore non equivale a un blocco definitivo degli account Steam, dell’infrastruttura di trading e dei percorsi di autenticazione che consentono il funzionamento dell’attività. Secondo le stime riportate, La sola CS:GO Lounge ha registrato oltre $1 miliardi di volume di scommesse nel corso del 2016; si tratta di una stima esterna delle puntate, non di un ricavo pari a Valve, e l'attività originaria del sito, incentrata sulle scommesse sulla pelle, è stata successivamente chiusa. Le dimensioni del fenomeno hanno reso indispensabile un intervento di contrasto verificabile.\n\nOggi, quello di Valve Contratto di abbonamento archiviato 2026-09-21 ↗ limita lo sfruttamento commerciale, salvo nei casi espressamente consentiti, e vieta separatamente determinate forme di automazione. Il nostro registro delle tratte datato i record dichiarati come OpenID restituiscono gli host dei servizi esterni; openid.realm e openid.return_to sono campi inviati a Steam, non segreti nascosti ad esso. Il nostro Controlli del filtro dei link illustra casi in cui è stato segnalato un indirizzo principale, ma non un host di accesso ad esso associato. Il risultato di un filtro, di per sé, non può dimostrare che Valve abbia consentito un accesso o che un determinato bot abbia eluso il blocco di un account. Ciò dimostra che un avviso pubblicato sulla homepage non può essere considerato una risposta esauriente in materia di accessibilità.\n\nNé l’esistenza di funzioni commerciali e OpenID utili e legittime Steam può chiarire se gli operatori vietati siano stati effettivamente esclusi. Le stesse norme di Valve consentono espressamente delle eccezioni. Se Valve fa valere tale distinzione, la Commissione dovrebbe chiedergli di identificare l’autorizzazione, i controlli sui conti e i criteri di applicazione applicabili alle attività commerciali relative agli «skin», nonché gli specifici usi non legati al gioco d’azzardo invocati nel 2016. La semplice possibilità di un uso lecito non costituisce una risposta a un uso vietato documentato.\n\nChiediamo alla Commissione di riesaminare il fascicolo del 2016 e di richiedere un resoconto operatore per operatore: quali account Steam e bot di trading sono stati disattivati dopo i preavvisi di dieci giorni; se siano stati monitorati account correlati o host di ritorno; quali operatori abbiano successivamente riottenuto l’accesso; quali esenzioni sono state concesse; e quali documenti confermano la dichiarazione di Valve alla Commissione. Pubblicare ciò che la legge consente al pubblico di esaminare. Confrontare tali documenti con i percorsi attuali e con gli interventi successivi di Valve, compresi OPSkins nel 2018 archiviato 2026-03-07 ↗.\n\nL'avviso fissava un termine di dieci giorni nel luglio 2016; dieci anni sono un periodo sufficientemente lungo per stabilire se sia stato rispettato. La Commissione dovrebbe verificare i dati contabili del 2016 di Valve alla luce delle infrastrutture ancora oggi osservabili.\n\nL'inchiesta \"Dossier Steam\" · Dichiarazione pubblica, 20 settembre 2026\n\nComunicazione della Commissione del 2016 ↗ archiviato 2026-05-20 ↗ · Risposta di Valve del 2016 (copia del documento) ↗ · Dichiarazione OpenID del 2016 di Valve ↗ archiviato 2026-09-21 ↗ · Accordo attuale Steam ↗ archiviato 2026-09-21 ↗ · Cronologia dello scambio del 2016: Sezione 11 →\n\nParte A — Scheda tecnica · Sezione 3\nIl sito è bloccato. La pagina di accesso invece no.\n\n26 domini principali bloccati. Il proxy di autenticazione associato a ciascuno di essi e da quanto tempo è attivo. Questi host di autenticazione distinti non sono semplici indirizzi secondari: ciascuno di essi è un proxy di autenticazione per Steam, che si interpone tra la piattaforma e l'endpoint OpenID di Valve e gestisce l'accesso che il dominio bloccato non può più effettuare apertamente. Valve ha impostato il filtro Link Filter come punto di accesso principale. L'accesso ha continuato a passare attraverso il proxy: csgogem.com è bloccato e api.csgem.com è registrato dal marzo 2014 — dodici anni e mezzo. In ciascuno di quei giorni, quell’host ha inviato il proprio nome host all’endpoint OpenID di Valve, e Steam lo ha immediatamente visualizzato all’utente nella pagina di accesso. Valve è il tronco attraverso cui passa ciascuna di queste rotte; non è necessario che le individui. Ecco cosa misura questa sezione: non se esiste un avviso, ma per quanti anni il percorso a valle dell’avviso rimane aperto. Nel registro figurano 44 percorsi con domini distinti, 27 dei quali corredati da un file di documentazione specifico per ciascun percorso — come illustrato nella tabella sottostante. Prendete in esame un esempio, poi valutateli tutti.\n\nFigura 3.1 — I due percorsi, rappresentati graficamente.\n\nUna piattaforma, un utente, due richieste provenienti dallo stesso browser. Il filtro dei link di Valve interviene su entrambe. Blocca quella che contiene un link e lascia passare quella relativa all'accesso. Tutti i dati misurati in questa sezione indicano per quanto tempo rimane aperta la route inferiore.\n\nThe player\none browser, one session\nrollbit.com\nthe platform's main domain\nrbsnin.com\nseparate authentication host\nLINK FILTER\n✕ BLOCKED\nLINK FILTER\n✓ CLEAN\nsteamcommunity.com\nOpenID endpoint · signs in\nno route\nLink pubblicato il Steam — interrottoRichiesta di accesso — passAssegni conservati del 19 e del 21 settembre 2026\n\nEntrambe le richieste sono visibili a Valve, ma ne viene eseguita solo una. Il filtro dei link è una lista Valve, controllata da un servizio Valve. La richiesta OpenID trasmette il nome dell'host di autenticazione all'endpoint di Valve, che lo visualizza immediatamente nella pagina di accesso. Il nome host è comunque presente nella richiesta; la differenza sta nel fatto che venga o meno utilizzato.\n\nUn'unica piattaforma. Due percorsi diversi.ROLLBIT / OSSERVAZIONI SALVATE\nPassaggio 5 / 5\n\nLa richiesta raggiunge il valore Steam. Il percorso osservato ha portato al modulo di accesso di Steam. Gli autori non hanno completato la procedura di accesso. Il blocco del link del dominio principale non ha impedito questo percorso osservato verso il modulo.\n\n01 CONTROLLO DEL FILTRO DI COLLEGAMENTO\nDESTINAZIONErollbit.comIl dominio principale della piattaforma\nFILTRO PER COLLEGAMENTO STEAMVerifica il linkUn sistema separato di avviso sulla destinazione\nRISULTATO SALVATOLink bloccato19 e 21 settembre 2026\n02 IL PERCORSO DI ACCESSO OSSERVATO\nSULLA PIATTAFORMAAccedi con SteamLa piattaforma avvia una richiesta OpenID\nHOST DI AUTENTICAZIONE SEPARATOrbsnin.comNessun blocco \"Link Filter\" nella verifica salvata\nSTEAMModulo di accesso visualizzatoL'host richiesto compare nell'avviso di Steam\nVerificare le note originali relative all’acquisizione, la data di registrazione e i dettagli del protocollo\nCome viene applicata la norma Valve\nDominio principale: bloccato\nUtente\n→\nrollbit.com\n(dominio principale)\n↓\nFILTRO STEAM LINK — BLOCCATO\n\"Link bloccato!\" — segnalato come potenzialmente dannoso\nrollbit.com ha segnalato un blocco del filtro dei link su 2026-09-19 e 2026-09-21 (controllo senza autenticazione; HTML grezzo e SHA-256 salvati). Una registrazione visibile e verificabile.\nCosa succede in realtà — l'autenticazione\nHost Auth: non bloccato\nUtente\n→\nrollbit.com\n\"Accedi con Steam\"\n↓\nReindirizzamento tramite host di autenticazione separato:\nrbsnin.comFiltro link: CLEAN\nregistrato 2026-09-18T09:34:52Z (Verisign RDAP)\n↓\nSteam Avviso sulla pagina di accesso (2026-09-20):\n\"Note that rbsnin.com is not affiliated with Steam or Valve\"\nSteam restituisce questo avviso proveniente dal dominio OpenID della richiesta che ha ricevuto.\n↓\nSteam Modulo di accesso fornito per l'host separato\nGli autori non hanno completato la procedura di accesso; il flusso è stato osservato fino al modulo Steam.\nValve riceve il nome host return_to / realm ad ogni richiesta di questo tipo. rbsnin.com non ha restituito alcun blocco da parte del filtro Link Filter su 2026-09-21.\nSu richiesta\nIn qualità di provider OpenID, Steam riceve il nome host di autenticazione con ogni richiesta di autenticazione: questo giunge ai server di Valve nel openid.return_to e openid.realm parametri.\nInviato dal sito\nL'host di autenticazione non viene individuato tramite scansione: la piattaforma lo invia a Steam in ogni richiesta. Ai sensi della sezione 9.1 di OpenID 2.0 return_to è formalmente facoltativo, ma senza di esso Steam non è in grado di fornire il risultato dell'accesso; pertanto, affinché l'accesso tramite Steam funzioni, è di fatto obbligatorio. Steam mostra addirittura il nome host all'utente (\"<host> non è affiliato a Steam né a Valve\").\n14 anni\nè l'età dell'host di autenticazione più vecchio che presenta ancora Steam accessi al momento del controllo 2026-09-21 (dota2.net, registrato 2011-10-29); quello più recente ha tre giorni (rbsnin.com). Non interpretare la cifra “0 host di autenticazione bloccati” come il risultato della ricerca. Un host di autenticazione bloccato comprometterebbe del tutto la funzionalità \"Accedi con Steam\" della piattaforma, quindi un registro creato sulla base di accessi riusciti può contenere solo host che non sono mai stati bloccati. Il dato significativo non è il numero di blocchi, bensì il numero di anni in cui il dominio principale è rimasto nel filtro dei link mentre l’accesso ad esso associato continuava a funzionare.\nHost di autenticazione con dominio separato: data di registrazione rispetto al dominio principale (30 percorsi: i 25 risolti nell'audit del browser 2026-09-21, più 5 aggiunti in 2026-09-22)\nPiattaforma\tFiltro link: principale\tHost Auth\tFiltro link: host di autenticazione\tHost Auth registrato\tFonte dell'osservazione\tFascicolo probatorio\nRollbit\nrollbit.com · reg. 2014-11-08\n\tBLOCCATO\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\trbsnin.com\tPULITO\n2026-09-21 · HTML grezzo (nessuna istantanea su Wayback)\n\t2026-09-18\n09:34:52Z, Verisign RDAP\n\tSteam avviso sulla pagina di accesso, 2026-09-20\trollbit.com.json\nSkin.Club\nskin.club · reg. 2017-09-04\n\tBLOCCATO\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\tsc-auth.net\tPULITO\n2026-09-21 · Wayback 2026-09-21\n\t2019-04-02\nRDAP\n\tSteam Avviso sulla pagina di accesso\tskin.club.json\nHowl.GG\nhowl.gg · reg. 2017-03-16\n\tBLOCCATO\n2026-09-18, 19-09, 21-09 · Wayback 2026-09-21\n\thowl.uno\tPULITO\n2026-09-21 · Wayback 2026-09-21\n\t2026-08-11\nRDAP\n\tAcquisizione in tempo reale dal browser + URL OpenID fornito\thowl.gg.json\nDuelbits\nduelbits.com · reg. 2020-02-03\n\tBLOCCATO\n2026-09-21 · Wayback 2026-09-21\n\tswitchflips.com\tPULITO\n2026-09-21 · Wayback 2026-09-21\n\t2020-04-21\nRDAP\n\tURL OpenID fornito\tduelbits.com.json\nCSGOFast\ncsgofast.com · reg. 2015-03-27\n\tBLOCCATO\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\tsteam-login.authtofast.com\tPULITO\nauthtofast.com, 2026-09-21 · Wayback 2026-09-21\n\t2026-06-30\nauthtofast.com, RDAP\n\tAcquisizione live dal browser + URL OpenID fornito\tcsgofast.com.json\nFarmskins\nfarmskins.com · reg. 2016-03-23\n\tBLOCCATO\n2026-09-19, 2026-09-21 · HTML grezzo\n\tsteam.kobal.cc\tPULITO\n2026-09-19, 2026-09-21 · HTML grezzo\n\t2017-01-07\nkobal.cc, RDAP\n\tAcquisizione in tempo reale dal browser + URL OpenID fornito\tfarmskins.com.json\nCobaltLab\ncobaltlab.tech\n\tBLOCCATO\n2026-09-21 · HTML grezzo\n\tcobaltauth.com\tPULITO\n2026-09-21 · HTML grezzo\n\t2025-01-07\nRDAP\n\tURL OpenID fornito\tcobaltlab.tech.json\nCSGO.NET\ncsgo.net · reg. 2012-07-22\n\tBLOCCATO\n2026-09-21 · HTML grezzo\n\tcn2.easylot.net\tPULITO\n2026-09-21 · HTML grezzo\n\t2016-09-03\neasylot.net, RDAP\n\tAcquisizione in tempo reale dal browser\tcsgo.net.json\nGGDrop\nggdrop.com\n\tBLOCCATO\n2026-09-21 · HTML grezzo\n\tggauth.com\tPULITO\n2026-09-21 · HTML grezzo\n\t2023-05-03\nRDAP\n\tURL OpenID fornito\tggdrop.com.json\nRustChance\nrustchance.com\n\tBLOCCATO\n2026-09-21 · HTML grezzo\n\thgfuihd.com\tPULITO\n2026-09-21 · HTML grezzo\n\t2019-01-27\nRDAP\n\tURL OpenID fornito\trustchance.com.json\nSkin.Fans\nskin.fans\n\tBLOCCATO\n2026-09-21 · HTML grezzo\n\tauth.skinfans.com\tPULITO\n2026-09-21 · HTML grezzo\n\t2018-07-16\nskinfans.com, RDAP\n\tURL OpenID fornito\tskin.fans.json\nSkinport\nskinport.com · reg. 2018-09-05\n\tBLOCCATO\n2026-09-21 · HTML grezzo\n\tskinport.app\tPULITO\n2026-09-21 · HTML grezzo\n\t2020-06-20\nRDAP\n\tAcquisizione in tempo reale dal browser + URL OpenID fornito\tskinport.com.json\nSkins.Cash\nskins.cash\n\tBLOCCATO\n2026-09-21 · HTML grezzo\n\tskinscash.live\tPULITO\n2026-09-21 · HTML grezzo\n\t2019-12-05\nRDAP\n\tURL OpenID fornito\tskins.cash.json\nTF2Hunt\ntf2hunt.com · reg. 2018-01-13\n\tBLOCCATO\n2026-09-21 · HTML grezzo\n\trstspcl.com\tPULITO\n2026-09-21 · HTML grezzo\n\t2020-08-08\nRDAP\n\tAcquisizione in tempo reale dal browser + URL OpenID fornito\ttf2hunt.com.json\nCSGOGem\ncsgogem.com · reg. 2016-10-16\n\tBLOCCATO\n2026-09-22 · HTML grezzo\n\tapi.csgem.com\ncsgem.com — dominio registrabile separatamente\n\tPULITO\n2026-09-22 · HTML grezzo\n\t2014-03-08\ncsgem.com, RDAP — il più antico nel registro\n\tRaccolta manuale + Acquisizione tramite filtro dei link\tlinkfilter-2026-09-22.json\nGamdom\ngamdom.com · reg. 2016-07-29\n\tBLOCCATO\n2026-09-22 · HTML grezzo\n\tlogin.gambldom.com\ngambldom.com — manca solo una lettera rispetto al marchio\n\tPULITO\n2026-09-22 · HTML grezzo\n\t2017-09-24\ngambldom.com, RDAP\n\tRaccolta manuale + Acquisizione tramite filtro dei link\tlinkfilter-2026-09-22.json\n12CS\n12cs.fail · reg. 2026-03-24\n\tBLOCCATO\n2026-09-22 · HTML grezzo\n\tfail.games\tPULITO\n2026-09-22 · HTML grezzo\n\t2021-08-24\nfail.games, RDAP\n\tRaccolta manuale + Acquisizione tramite Link Filter\tlinkfilter-2026-09-22.json\nCSGOEmpire\ncsgoempire.com · reg. 2015-06-10\n\tPULITO\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\tcsgoempirelogin4.com\nuno dei dieci domini numerati da login1 a login10\n\tPULITO\n2026-09-21 · Wayback 2026-09-21\n\t2020-07-20\n05:49:17Z, Verisign RDAP\n\tAcquisizione in tempo reale dal browser\tcsgoempire.com.json\nCS.MONEY\ncs.money\n\tPULITO\n2026-09-21 · HTML grezzo\n\tauth.dota.trade\tPULITO\n2026-09-21 · HTML grezzo\n\t2016-07-15\ndota.trade, RDAP\n\tSteam avviso sulla pagina di accesso\tcs.money.json\nCSFloat\ncsfloat.com · reg. 2021-07-11\n\tPULITO\n2026-09-21 · HTML grezzo\n\tcsgofloat.com\ndominio del marchio precedente dell'operatore; dominio registrabile a sé stante, non indice di evasione\n\tPULITO\n2026-09-21 · HTML grezzo\n\t2015-09-29\nRDAP\n\tAcquisizione in tempo reale dal browser\tcsfloat.com.json\nG4Skins\ng4skins.com\n\tPULITO\n2026-09-21 · HTML grezzo\n\tauth.g4s.to\tPULITO\n2026-09-21 · HTML grezzo\n\t2021-05-30\ng4s.to, RDAP\n\tURL OpenID fornito\tg4skins.com.json\nJuice.GG\njuice.gg\n\tPULITO\n2026-09-21 · HTML grezzo\n\tletmeinjuice.com\tPULITO\n2026-09-21 · HTML grezzo\n\t2024-04-15\nRDAP\n\tURL OpenID fornito\tjuice.gg.json\nMarket.CSGO\nmarket.csgo.com\n\tPULITO\n2026-09-21 · HTML grezzo\n\tdota2.net\tPULITO\n2026-09-21 · HTML non formattato\n\t2011-10-29\nRDAP\n\tAcquisizione live dal browser + URL OpenID fornito\tmarket.csgo.com.json\nRust.TM\nrust.tm\n\tPULITO\n2026-09-21 · HTML grezzo\n\tdota2.net\tPULITO\n2026-09-21 · HTML grezzo\n\t2011-10-29\nRDAP\n\tURL OpenID fornito\trust.tm.json\nCSGOLounge\ncsgolounge.com · reg. 2013-08-14\n\tPULITO\n2026-09-22 · HTML grezzo\n\tdota2.net\nterzo front-end su questo host di autenticazione\n\tPULITO\n2026-09-22 · HTML grezzo\n\t2011-10-29\ndota2.net, RDAP\n\tRaccolta manuale + Acquisizione tramite filtro dei link\tlinkfilter-2026-09-22.json\nDota2Lounge\ndota2lounge.com · reg. 2012-08-10\n\tPULITO\n2026-09-22 · HTML grezzo\n\tdota2.net\nquarto front-end su questo host di autenticazione\n\tPULITO\n2026-09-22 · HTML grezzo\n\t2011-10-29\ndota2.net, RDAP\n\tRaccolta manuale + Acquisizione tramite filtro dei link\tlinkfilter-2026-09-22.json\nSkinBaron\nskinbaron.de\n\tPULITO\n2026-09-21 · HTML grezzo\n\tskinbaron.com\nstessa marca, TLD diverso\n\tPULITO\n2026-09-21 · HTML grezzo\n\t2015-12-22\nRDAP\n\tURL OpenID fornito\tskinbaron.de.json\nTF2Royal\ntf2royal.com · reg. 2022-08-17\n\tPULITO\n2026-09-21 · HTML grezzo\n\ttf2auth.com\tPULITO\n2026-09-21 · HTML grezzo\n\t2021-07-27\nRDAP\n\tAcquisizione in tempo reale dal browser + URL OpenID fornito\ttf2royal.com.json\nTradeit\ntradeit.gg\n\tPULITO\n2026-09-21 · HTML grezzo\n\tconnect-tradeit.com\tPULITO\n2026-09-21 · HTML grezzo\n\t2022-02-23\nRDAP\n\tURL OpenID fornito\ttradeit.gg.json\nUpgrader\nupgrader.pro\n\tPULITO\n2026-09-21 · HTML grezzo\n\tupgauth.space\tPULITO\n2026-09-21 · HTML grezzo\n\t2026-08-14\nRDAP\n\tURL OpenID fornito\tupgrader.pro.json\nFonte: steamcommunity.com/linkfilter, GET senza autenticazione, 2026-09-21, 53 host, intervallo di 3 secondi; steam_tos_assets/linkfilter-recheck-2026-09-21.json; codice HTML grezzo in steam_tos_assets/linkfilter-raw/. Date di iscrizione: RDAP, steam_tos_assets/domain-registration.json. · Verifica anticipata di 2026-09-19 in linkfilter-all-results.json · inserire i dati relativi ai percorsi in auth-route-audit.json · I snapshot di Wayback Machine delle pagine relative al filtro dei link, 2026-09-21, elencate in wayback-snapshots.json (non esiste alcuna istantanea per rbsnin.com; l'unico dato disponibile è il file raw locale).\n\nDate di iscrizione: RDAP (steam_tos_assets/domain-registry/). L’“URL OpenID fornito” definisce i parametri della richiesta, non un accesso completato. Gli autori non hanno completato alcun accesso su nessuna piattaforma. Un dominio separato non costituisce di per sé una prova di elusione. Né “0 host di autenticazione bloccati” rappresenta un riscontro indipendente: bloccarne uno comprometterebbe il login Steam di quella piattaforma, quindi un registro compilato sulla base di accessi funzionanti non può contenere un host di autenticazione bloccato. L’osservazione che ha peso è l’accoppiamento e la sua durata: un dominio principale nel Filtro dei collegamenti accanto a un dominio di accesso che è rimasto attivo per anni. Questa tabella contiene 30 righe: 25 delle 27 rotte con un file di prova per ciascuna rotta, più cinque aggiunte su 2026-09-22 la cui suddivisione nel Filtro dei collegamenti è riportata in linkfilter-2026-09-22.json anche se il dominio stesso è stato raccolto manualmente — come indicato nelle righe corrispondenti nella colonna “fonte”. I due percorsi dei file di prova non visualizzati sono skinsnipe.com (host di autenticazione pricing.tradeupspy.com, registrato 2020-03-11) e csgobig.com (host di autenticazione letmeinbig.com, registrato 2023-01-20); entrambi hanno restituito “BLOCKED main / CLEAN auth host” nel controllo di 2026-09-22, registrato con SHA-256 in linkfilter-2026-09-22c.json, ma il codice HTML grezzo relativo a quel lotto non è presente nel set pubblicato, quindi qui vengono semplicemente elencati anziché avere una riga dedicata, come invece avviene per tutte le altre voci di questa tabella. I restanti 12 percorsi raccolti manualmente presenti nel registro sono identificati come tali in master_registry.json sotto realm_src: user.\n\nVerifica empirica primaria · Intervallo di date pluriennale\nLa trappola della visione d'insieme: il filtro dei link è solo una messinscena di conformità, non uno scudo\n\nSui browser per computer fissi, gli utenti sono protetti da sistemi di difesa esterni: Google Safe Browsing e Microsoft SmartScreen bloccano i tentativi di phishing noti visualizzando avvisi rossi a schermo intero. Nella modalità Big Picture di Steam, nell'overlay di gioco (Shift+Tab) e nel Deck Steam (SteamOS), tali difese non sono presenti. Il browser integrato non supporta alcuna estensione, disattiva i motori esterni di navigazione sicura e lascia all'utente una sola barriera difensiva: quella di Valve linkfilter interstiziale.\n\nScorri per confrontare tutti e quattro i risultati →\n\n92.5%\n2025–2026: phishing di nuova generazione non bloccato (37/40)\n77.5%\n2023–2024: phishing dell’era CS2 non bloccato (31/40)\n70.0%\n2021–2022: phishing storico non bloccato (28/40)\n7 / 7\ndomini principali dei siti di gioco d’azzardo bloccati (controllo positivo)\nAudit longitudinale pluriennale: 120 domini di phishing “puri” Steam testati in tempo reale (24 settembre 2026)\n\nPer verificare se il filtro di Valve sia semplicemente lento nell’individuare nuove minacce o se ne sia fondamentalmente ignaro, abbiamo effettuato una verifica 120 domini di phishing confermati specifici per Steam in tre coorti storiche rispetto a steamcommunity.com/linkfilter:\n\nCohort 1: 2021–2022 (Offerte di scambio classiche e oggetti in premio) — 70.0% Superato senza errori (28/40). Anche a distanza di 4-5 anni dalla loro segnalazione da parte degli osservatori della comunità, 7 host di phishing preesistenti su 10 continuano a essere accessibili senza alcun blocco.\nCohort 2: 2023–2024 (CS2 Beta Hype & Fake Support Appeals) — 77.5% Superato senza errori (31/40). Campagne che si spacciano per annunci relativi a Counter-Strike 2 e falsi appelli della community (ad es. cs2-steam.com, appealsteamcommunity.help) passano direttamente attraverso.\nCohort 3: 2025–2026 (Implementazioni serverless edge e cloni di favicon) — 92.5% Superato con successo (37/40). Kit di phishing moderni distribuiti su EdgeOne, Vercel e Cloudflare Pages (ad es. steamgifter.online, steam-dp4lt5b8fnez.edgeone.dev) passano praticamente senza ostacoli.\n\nTelemetria e copertura di responsabilità civile, non protezione. Perché esiste il filtro dei link se lascia passare da 70% a 92.5% casi di phishing puro Steam? Funge da clausola di esclusione di responsabilità aziendale e da sensore di telemetria dei clic in uscita. Presentando un cortese \"Stai uscendo da Steam\" avviso con un pulsante verde cliccabile \"Procedi\", Valve attribuisce la responsabilità legale alla vittima ai sensi del Steam Accordo di abbonamento (*\"l'utente ha volontariamente navigato al di fuori di Steam\"*). Valve raccoglie i dati telemetrici relativi al clic, ma non blocca il furto.\n\nLa prova dell’hash della favicon: nessun inserimento di feed relativi alle minacce. Le piattaforme indipendenti di intelligence sulle minacce (urlscan.io, Shodan, Censys) individuano i kit di phishing attivi Steam effettuando una semplice ricerca dell’hash della favicon ufficiale di Steam (page.favicon.hash:9f890a9debcdfccc339149a7943be9aff9e4c9203c2fa37d5671a5b2c88503ad NOT domain:*.steampowered.com). Questo controllo automatico di base individua i cluster di phishing attivi in pochi secondi. Valve non si sincronizza con feed esterni, non esegue attività di ricerca delle minacce basate su hash e interviene manualmente solo quando obbligato dalle autorità di regolamentazione (l’ordinanza del WSGC del 2016 sul gioco d’azzardo) o per proteggere le stringhe dei propri domini protetti da marchio registrato.\n\nElementi probatori primari: Audit longitudinale pluriennale su 120 domini: audit-longitudinale-sul-phishing-via-vapore.json · 100 campioni di phishing dedicati Steam: linkfilter-steam-phishing-100.json · Analisi approfondita dei feed (n=250): linkfilter-coverage-2026-09-22.json.\n\nCSGOEmpire — registrazione in blocco di dieci domini di autenticazione numerati\n\nIl 2020-07-20 dieci domini numerati, csgoempirelogin1.com attraverso csgoempirelogin10.com, sono stati registrati. Per tutti e dieci sono presenti i timestamp RDAP di Verisign: login1 05:49:06Z, login5 05:49:08Z, login2 05:49:11Z, login3 05:49:14Z, login4 05:49:17Z, login6 05:49:20Z, login7 05:49:23Z, login8 05:49:26Z, login9 05:49:28Z — nove domini in 22 secondi — e login10 alle 05:56:03Z, sette minuti dopo. L'intervallo di tempo è coerente con un'unica operazione in blocco effettuata dal registrar.\n\nIl modello è coerente con gli host di fallback preconfigurati; solo login4 È stato rilevato in una richiesta OpenID effettiva. Sia csgoempire.com che csgoempirelogin4.com hanno restituito il risultato \"CLEAN\" nel filtro dei link su 2026-09-21; CSGOEmpire non figurava tra i siti citati nei resoconti della stampa relativi alle notifiche del luglio 2016.\n\n# DNS — tutti e 10 attivi (settembre 2026)\nOK csgoempirelogin1.com 172.67.129.43\nOK csgoempirelogin2.com 172.67.175.168\nOK csgoempirelogin3.com 188.114.96.3\nOK csgoempirelogin4.com 188.114.96.11 ← nel traffico OpenID\nOK csgoempirelogin5.com 172.67.160.194\nOK csgoempirelogin6–10.com Indirizzi IP di Cloudflare\nNXDOMAIN: csgoempirelogin11.com\nTutti e 10 registrati 2020-07-20; tutti e 10 con timestamp RDAP (steam_tos_assets/domain-registry/csgoempireloginN.com.rdap.json)\nConclusioni per le autorità di regolamentazione\nUn dominio principale bloccato, abbinato a un host di autenticazione sbloccato, lascia aperta la rotta di accesso — che rimane aperta per anni.\n\nIl blocco Link Filter sul dominio principale è un record pubblico e verificabile. L’host di autenticazione trasporta il traffico “Accedi con Steam” e compare nei parametri di richiesta OpenID di Valve. Dai controlli effettuati su 2026-09-21 e 2026-09-22, in 26 coppie con filtro diviso il dominio principale ha restituito un blocco del filtro di collegamento, mentre il proxy che trasportava il relativo accesso non ne ha restituito alcuno. Il registro sopra riportato misura l’altra metà di questo dato: questi host non sono domini temporanei di breve durata. Molti erano registrati da oltre un decennio alla data del controllo, e ogni singolo giorno di quel periodo è un giorno in cui Valve ha ricevuto il nome host nei propri parametri di richiesta. Valve non ha pubblicato alcun registro delle misure applicate per singolo operatore, pertanto dai dati pubblici non è possibile stabilire se a questi host siano state applicate altre misure.\n\n12 anni e 6 mesi\nIl sito csgogem.com è bloccato nel filtro dei link.\nIl suo host di accesso api.csgem.com è stato\nè registrato dal 2014-03-08 e non lo è.\nSintesi in linguaggio semplice — Per le autorità di regolamentazione e i tribunali (espandi)\nSintesi in linguaggio semplice — destinata alle autorità di regolamentazione\nContesto: Che cos’è Steam e perché è importante in questo contesto\n\nSteam è una piattaforma software gestita da Valve Corporation (Bellevue, Washington, USA). Steam funge da fornitore di identità digitale: i siti web di scommesse e giochi d’azzardo su Internet utilizzano un sistema denominato «Accedi con Steam», un pulsante che consente a un sito web di verificare che un visitatore disponga di un account Steam autentico. Il funzionamento è simile a quello di «Accedi con Google» o alla verifica di un documento d’identità rilasciato dalle autorità: il sito web reindirizza l’utente ai server di Steam, Steam ne conferma l’identità e Steam lo reindirizza nuovamente al sito web. Valve gestisce il sistema di autenticazione. Ogni singolo accesso effettuato tramite \"Accedi con Steam\" passa attraverso i server di Valve.\n\nCosa ha fatto Valve: il blocco dei domini\n\nNel luglio 2016, a seguito delle pressioni mediatiche e legali relative al “skin gambling”, il legale di Valve ha inviato notifiche a circa 23 siti di gioco d’azzardo identificati (secondo quanto riportato dalla stampa il 21 luglio 2016); nell’ottobre 2016 Valve ha comunicato alla Commissione per il gioco d’azzardo dello Stato di Washington di aver contattato più di quaranta siti. Alcuni domini di gioco d’azzardo compaiono nel Steam Filtro link — un elenco che fa sì che qualsiasi link a tali siti pubblicato all’interno di Steam (nella chat, su una pagina del profilo, nello store) visualizzi una pagina di avviso: \"Collegamento bloccato!\" Il filtro di collegamento è l'unica misura di applicazione il cui effetto può essere osservato dall'esterno di Valve.\n\nEsempio: Un link a rollbit.com all'interno di Steam viene visualizzata la pagina di avviso \"Link Filter\" (caselle 2026-09-19 e 2026-09-21 selezionate). In teoria, il sito di gioco d'azzardo è bloccato.\nChe cos’è un dominio proxy\n\nA L'host di autenticazione con dominio separato è un proxy di autenticazione: un secondo indirizzo web, su un dominio registrabile diverso, che lo stesso gestore interpone tra i propri utenti e Steam al solo scopo di gestire la fase “Accedi con Steam”. Funge da proxy per l’accesso. L’utente crede di effettuare l’accesso alla piattaforma; la richiesta che raggiunge Valve riporta il nome host del proxy, non quello della piattaforma. Di solito non presenta alcun collegamento visibile pubblicamente con il sito di gioco d’azzardo, ed è l’indirizzo che riaccoglie gli utenti dopo che Steam ne ha confermato l’identità.\n\nEsempio: Rollbit opera in base a rollbit.com, che viene bloccato dal filtro Link. Per l'autenticazione Steam, il flusso osservato su 2026-09-20 utilizzava un indirizzo diverso: rbsnin.com, registrato 2026-09-18. Questo indirizzo ha restituito nessun blocco \"Link Filter\" il 2026-09-21. Il sito di gioco d'azzardo ha continuato a funzionare e la sua procedura di accesso Steam passava attraverso l'host sbloccato.\nIl punto critico: in ogni richiesta, l’host di autenticazione viene impostato su Steam\n\nValve non ha bisogno di eseguire scansioni o crawl per individuare quali host di autenticazione sono in uso. Steam è il Provider di identità OpenID per questi siti, e ogni clic su “Accedi con Steam” invia una richiesta GET ai server di Valve contenente il nome host di autenticazione in chiaro. Ai sensi della sezione 9.1 di OpenID 2.0, il return_to Il campo è formalmente facoltativo, ma senza di esso Steam non è in grado di fornire il risultato dell'accesso; pertanto, affinché l'accesso tramite Steam funzioni, è di fatto obbligatorio. Steam visualizza il nome host nella pagina di accesso (\"<host> non è affiliato a Steam né a Valve\").\n\n— Formato della richiesta Steam ricevuta (host rilevato per Rollbit su 2026-09-20): —\nOTTIENI steamcommunity.com/openid/login\n&openid.mode=checkid_setup\n&openid.return_to=https://rbsnin.com/… ← effettivamente richiesto; viene inserito nel registro di Valve\n&openid.realm=https://rbsnin.com ← dichiarato dal sito stesso; visualizzato nella pagina di accesso di Steam\nSe il sito utilizza la verifica da server a server (check_authentication), il log di Valve registra anche l'IP del server della piattaforma e la rete di hosting.\n\nL'estrazione del nome host da questa richiesta è un'operazione standard. Il registro delle misure applicate — che indica su quali host sono state intraprese azioni e su quali no, nonché in base a quali criteri — esiste solo nell'infrastruttura di Valve e non è stato reso pubblico.\n\nCosa dimostra tutto ciò\n\n1. Il blocco \"Link Filter\" agisce sui link, non sugli accessi. Bloccare il dominio principale (ad esempio rollbit.com) mostra un avviso agli utenti che cliccano sui link che rimandano ad esso all’interno di Steam. Ciò non impedisce al sito di funzionare, né di utilizzare il servizio OpenID di Valve tramite un indirizzo diverso.\n\n2. Gli host di autenticazione sottoposti a test non sono stati bloccati. La tabella sopra riportata mostra gli host di autenticazione con domini separati registrati tra il 2011 e settembre 2026, molti dei quali anni dopo le notifiche del luglio 2016. In 26 coppie il dominio principale ha restituito un blocco del filtro dei link, mentre il proxy che ne gestiva l'accesso non lo ha fatto (controlli non autenticati, 2026-09-21 e 2026-09-22; risposte grezze e SHA-256 salvati). Quel proxy avrebbe smesso di funzionare il giorno in cui Valve lo ha rifiutato, motivo per cui la misura qui considerata è la durata del suo funzionamento, non se sia presente nell’elenco. Valve riceve questi nomi host nelle proprie richieste OpenID. Non è possibile determinare dai dati pubblici se sia stata applicata una misura diversa dal filtro dei link, poiché Valve non ha pubblicato alcun registro delle misure applicate per singolo operatore.\n\n3. I siti hanno continuato ad effettuare l'autenticazione tramite l'infrastruttura di Valve. \"Accedi con Steam\" è un servizio offerto da Valve; ogni autenticazione effettuata tramite esso costituisce una richiesta che Valve riceve ed elabora. Anche Valve ricava entrate dalle chiavi dei casi, mentre il Community Market Steam addebita una commissione complessiva di circa 15% sulle transazioni completate all’interno del Market (non sulle transazioni esterne). L’azione Link Filter ha creato un record pubblico; non ha interrotto il rapporto di autenticazione.\n\nIl blocco avrebbe funzionato?\n\nPer analogia: quando il registrar di domini gratuito Freenom ha cessato l’attività nel 2023, le campagne di phishing che facevano affidamento sui suoi domini sono state interrotte. La continuità operativa dipende dalla stabilità dell’infrastruttura.\n\nLa stessa logica vale anche in questo caso. Se un host di autenticazione venisse rifiutato durante l'elaborazione OpenID di Steam, la funzione \"Accedi con Steam\" della piattaforma smetterebbe di funzionare fino a quando non venisse registrato un nuovo host, non fossero emessi i certificati e non fosse avvenuta la propagazione DNS. Durante quel periodo: interruzione del servizio.\n\nLa rotazione non rende inutile il blocco. Questo rende il blocco un costo operativo. Poiché i nuovi host compaiono nei log delle richieste di Valve al primo utilizzo, una risposta potrebbe avvenire alla velocità di quel primo utilizzo.\n\nLa registrazione in blocco è di per sé un segnale: Gli account login1–login10 di CSGOEmpire sono stati registrati su 2020-07-20, nove dei quali nell'arco di 22 secondi (Verisign RDAP). Non è necessario che la risposta sia dominio per dominio; una serie sequenziale proveniente da un'unica sessione di un registrar può essere identificata come una serie.\n\nI dati pubblici non riportano alcun tentativo di bloccare gli host autorizzati che sia stato vanificato dalla rotazione.\nIl grafico mostra i domini principali bloccati mentre il proxy responsabile di ciascuna sessione di accesso continuava a funzionare — 26 coppie al 2026-09-22, con l’host di autenticazione più antico registrato da 12 anni e 6 mesi — e nessun record di applicazione pubblicato per alcun operatore.\nLa domanda che si pone l'autorità di regolamentazione è quindi: quali misure di applicazione, se del caso, ha applicato Valve agli host di autenticazione che riceve nelle proprie richieste OpenID?\nCosa ha fatto Valve — e perché non ha interrotto il percorso di autenticazione\n\nLa tabella sottostante mette in relazione ciascuna azione Valve documentata pubblicamente con l’eventuale impatto sul punto di accesso per l’autenticazione OpenID. La conclusione non è che «Valve non abbia fatto nulla», bensì che nessuna delle azioni documentate pubblicamente abbia interessato il punto in cui gli accessi alle piattaforme di gioco d'azzardo transitano attraverso i server di Valve.\n\nData\tValve Azione\tColpiti openid.return_to percorso?\nLuglio 2016\tDichiarazione pubblica del 13 luglio 2016; comunicazioni dei legali a circa 23 siti indicati (stampa, 21 luglio 2016); oltre 40 siti contattati in seguito alla lettera inviata da Valve nel mese di ottobre 2016 al WSGC\tNo. Gli avvisi e il filtro dei link agiscono sugli operatori e sui link; il percorso della richiesta OpenID non è stato modificato.\n2017\tChiusura di IEconItems_730/GetPlayerItems (secondo l'account tecnico di CSFloat; non è stato trovato alcun changelog Valve)\tNo. Ha influito sulla visibilità della cronologia degli elementi pubblici. L'autenticazione OpenID non è stata modificata.\n2018-03-29\tAnnunciato il blocco delle transazioni di 7 giorni in CS:GO (blog.counter-strike.net)\tNo. Movimento degli elementi rallentato; il percorso della richiesta OpenID non è stato modificato.\n2022-05-10\tRimuovi gli endpoint relativi all'annullamento delle transazioni dall'API Web pubblica (segnalato da un utente; nessun Valve nel log delle modifiche — node-steam-tradeoffer-manager #325)\tNo. Lo strumento per lo scambio di offerte è stato disattivato; l'autenticazione OpenID non è stata modificata.\n2023-12-04\tLa creazione di una chiave API richiede ora una conferma tramite dispositivo mobile (steamcommunity.com/dev/apikey; nessun changelog)\tNo. L'endpoint chiave è stato protetto; gli host di autenticazione qui documentati non sono stati interessati dal problema.\n2026-09-19 / 21-09\tSteam Stato del filtro di collegamento secondo l'osservazione degli autori\tI 14 domini principali hanno restituito un blocco nel ricontrollo salvato 2026-09-21 — 26 coppie separate nel registro di 2026-09-22 — mentre il proxy che gestiva ciascun accesso continuava a funzionare.\nFonti: Valve dichiarazione del 13 luglio 2016 (store.steampowered.com/oldnews/22883, archiviato 2026-09-21) · Resoconto tecnico di CSFloat sulla chiusura del 2017 (blog.csfloat.com, archiviato 2026-09-21) · Stato del filtro dei link: linkfilter-recheck-2026-09-21.json.\nQuesto risultato è falsificabile se venisse pubblicato un solo caso in cui Valve abbia rifiutato una richiesta OpenID perché openid.return_to indicava un host autorizzato per il gioco d'azzardo. Non è stata individuata alcuna istanza di questo tipo nei registri pubblici.\nLe due registrazioni più recenti relative all'host di autenticazione\nhowl.unoè stato registrato 2026-08-11 (RDAP), 41 giorni prima di 2026-09-21; howl.gg ha restituito un blocco del filtro dei link su 2026-09-18, 2026-09-19 e 2026-09-21. Non è stato accertato se il blocco abbia preceduto la registrazione.\nrbsnin.comè stato registrato 2026-09-18T09:34:52Z (Verisign RDAP) ed è stato rilevato nel flusso di accesso Steam di Rollbit su 2026-09-20 tramite l'avviso presente nella pagina di accesso di Steam; rollbit.com ha restituito un blocco del filtro dei link in 2026-09-19 e 2026-09-21, mentre rbsnin.com non lo ha fatto.\nOgni host riportato nella tabella sopra viene inviato ai server di autenticazione di Valve come openid.realm ad ogni tentativo di accesso.\nDati completi per ogni percorso e risultati del filtro dei collegamenti: la tabella nella Sezione 3 sopra; risultati grezzi in linkfilter-recheck-2026-09-21.json e linkfilter-all-results.json.\nMetodologia — Come sono stati stabiliti i conteggi relativi ai percorsi e ai filtri di collegamento\n1. Risoluzione dei domini\nL'audit 2026-09-21 ha risolto 78 delle 189 piattaforme richieste: 33 effettuano l'autenticazione sul proprio nome host e 20 sul proprio sottodominio — autenticazione diretta — e nessuna di queste viene conteggiata come percorso di dominio separato. I restanti 25: autenticazione tramite un dominio separato registrabile, distribuiti su 24 nomi host distinti (dota2.net è condiviso da market.csgo.com e rust.tm): 10 individuati tramite acquisizione in tempo reale del browser, 3 grazie alla notifica presente nella pagina di accesso di Steam, 12 tramite un URL OpenID fornito. Il registro in tempo reale (master_registry.json, 2026-09-22) estende tale concetto a 44 percorsi con domini distinti: 26 coppie con suddivisione del filtro (dominio principale BLOCCATO, host di autenticazione PULITO) più altre 18 rotte senza suddivisione del dominio principale. Delle 44, 27 tenere un fascicolo probatorio per ogni percorso; gli altri 17 sono stati raccolti a mano e sono contrassegnati realm_src: user nel registro. Cinque di questi diciassette — csgogem.com, gamdom.com, 12cs.fail, csgolounge.com e dota2lounge.com — sono stati aggiunti il 2026-09-22 con una cattura del filtro dei link di entrambi gli host (HTML grezzo + SHA-256 in linkfilter-2026-09-22.json), quindi la suddivisione è evidente anche se il dominio è stato raccolto manualmente; tali dati compaiono nella tabella sopra riportata insieme ai percorsi del file di prova. tfauth.com (tf2easy.com) è stato rimosso dal registro alle 2026-09-22: come nel caso di arena.fragnet.net, non vi sono collegamenti verificabili che lo ricolleghino al sito di origine. Il conteggio è ricavabile dai dati pubblicati auth-route-audit.json (serie di 2026-09-21) secondo un'unica regola: una piattaforma viene conteggiata solo quando il suo host OpenID Steam osservato si trova su un dominio registrabile diverso da quello della piattaforma stessa.\n2. Steam Stato del filtro dei link\nTestato tramite steamcommunity.com/linkfilter/?url=https://[domain], senza autenticazione, su 2026-09-19 e 2026-09-21; codice HTML grezzo salvato con SHA-256. Lo stato è stato registrato separatamente per il dominio principale e l’host di autenticazione. Un classificatore distingue l’avviso generico «Stai lasciando Steam» (CLEAN) dalla pagina «Link bloccato! ... segnalato come potenzialmente dannoso» (BLOCKED); un controllo su google.com conferma che i due non vengono confusi. Una precedente variante autenticata di questo test è stata scartata dopo aver restituito \"bloccato\" per ogni dominio, compreso quel controllo — il problema è stato ricondotto a un cookie di sessione non valido nello script di prova, non a un risultato reale.\n3. Osservazione dell'host di autenticazione\nAcquisizione in tempo reale: un browser Playwright ha effettuato l'accesso alla procedura di login di ciascuna piattaforma e il openid.return_to Il nome host è stato ricavato dalla richiesta intercettata. Avviso sulla pagina di accesso: il nome host è stato ricavato dal \" di Steam stesso\"<host> non è affiliato a Steam né a Valve\" testo, che Steam riproduce da openid.realm (rbsnin.com, sc-auth.net, auth.dota.trade). URL fornito: un URL di accesso \"a Steam\" fornito agli autori; questo definisce i parametri della richiesta, non un accesso completato. Non è stato completato alcun accesso su nessuna piattaforma.\n4. Copertura — cosa non è stato risolto e perché è importante\nDelle 189 piattaforme, 110 non ha prodotto alcun percorso definito e uno non era applicabile (189 − 78 − 1). Questo dossier non ne tiene conto. La ripartizione dei 110 casi, tratta dal file di audit: 22 challenge anti-bot, 14 timeout, 12 errori HTTP e 10 errori di navigazione — l’osservatore non è riuscito a raggiungere il flusso di accesso, sebbene la maggior parte di questi siti si apra normalmente in un browser standard; 20 non presentavano alcun controllo di accesso Steam sulla pagina di destinazione; 16 hanno raggiunto una procedura di accesso che non è stato possibile risolvere in un host; 11 domini non sono stati risolti nel DNS; 5 si sono bloccati a una schermata di consenso. Il registro riportato di seguito suddivide gli stessi 110 in modo diverso: gli 11 che non sono stati risolti nel DNS sono elencati separatamente come Rimosso · NXDOMAIN, e la voce non applicabile si aggiunge alle altre. 189 piattaforme sottoposte a verifica, 11 rimosse a seguito di un NXDOMAIN definitivo da entrambi i resolver, 178 confermati (platform-audit.json, platforms-removed.json). 137 domini di autenticazione che il registro aveva individuato in base al modello di denominazione sono stati eliminati dai dati su 2026-09-19 — mai osservati, quindi mai considerati prove. Tre delle ipotesi sono state smentite dagli URL OpenID forniti: buff.163.com, gamerpay.gg e csgoluck.com effettuano l’autenticazione direttamente, contrariamente alle ipotesi relative a buffauthproxy.163.com, gamerpayredirect.io e lucklogin.app. Le rimozioni sono elencate nel file di audit pubblicato.\nIl numero 25 rappresenta un limite minimo, non un limite massimo. Tra le 78 piattaforme che hanno risolto il problema, 25 hanno utilizzato un dominio separato e 53 no. Da tale rapporto non si ricava alcuna informazione sulle 110 piattaforme non risolte, e in questo dossier non compare alcuna proiezione basata su di esso. Ciascuna di esse può essere risolta da una persona che apra il sito e clicchi su «Accedi con Steam»: il nome host di autenticazione si trova nell’URL della pagina Steam che viene caricata.\nLo scopo di questa sezione: Un osservatore indipendente ha bisogno di un browser e di molta pazienza per identificare 189 piattaforme, e ne ha individuate 78. Valve richiede una query al database. Ogni piattaforma che utilizza \"Accedi con Steam\" — sia quelle identificate che quelle non identificate — invia openid.realm all'endpoint di autenticazione di Valve ad ogni accesso. La lacuna presente in questa tabella è dovuta al fatto che gli autori non fanno parte del sistema. Tale lacuna non esiste per Valve.\nI nomi host proxy rilevati si trovano in auth-route-audit.json. Date di registrazione dei domini da RDAP (Verisign) / IP2WHOIS. Risultati del filtro dei link in linkfilter-all-results.json.\nUn'analogia per maggiore chiarezza\n\nImmaginiamo che un’azienda di taxi autorizzata riceva dalle autorità di regolamentazione la comunicazione di non poter più operare dall’indirizzo registrato in Main Street. L’azienda rimuove l’insegna da Main Street. La rimozione dell’insegna viene documentata. Tuttavia, la stessa azienda apre una sede in Side Street — registrata con un nome diverso — e continua a operare da lì. Le autorità di regolamentazione gestiscono il sistema centrale di smistamento delle chiamate utilizzato da tutti i taxi provenienti da entrambi gli indirizzi. Ogni richiesta di corsa riporta la dicitura «prelievo da Side Street». Le autorità di regolamentazione non revocano mai la licenza relativa a Side Street. L'unica misura coercitiva adottata è stata la rimozione del cartello \"Main Street\". La compagnia di taxi non ha mai cessato la propria attività.\n\nParte A — Scheda tecnica · Sezione 3.1\nAll'interno di Steam, l'elenco di Valve è l'unico elenco.\n\nUn link cliccato nel client Steam, nell'overlay di gioco o nella modalità Big Picture non si apre nel browser dell'utente. Viene visualizzato all'interno del browser integrato di Steam, dove non sono presenti i livelli di avviso che un browser applicherebbe. Il filtro Link non è una delle tante misure di sicurezza. È l'unica misura di sicurezza.\n\nIn un browser normaleTre strati indipendenti\nNavigazione sicura di GoogleUna pagina interstiziale a tutta pagina per gli host presenti negli elenchi di Google relativi al phishing e al malware, aggiornata continuamente e indipendentemente dal sito visitato.\nL'estensione antivirus per il browserLa maggior parte dei prodotti endpoint destinati ai consumatori include un componente aggiuntivo per il browser che verifica la destinazione confrontandola con l'elenco di reputazione del fornitore stesso.\nIspezione HTTPS degli endpointQuando il prodotto esegue l'ispezione TLS, il contenuto della pagina viene analizzato prima che raggiunga l'utente.\nNel client Steam, overlay e Big PictureUn unico strato\nNavigazione sicura di GoogleNon presente. Il controllo richiede chiavi API di Google che non sono fornite nelle build Chromium incorporate; in loro assenza, la documentazione di progettazione di Chromium stessa indica che il gestore di Safe Browsing semplicemente non viene mai aggiunto alla catena di richieste.\nL'estensione antivirus per il browserNon presente. Il renderer di Steam non è il browser dell'utente e non carica alcuna estensione dal profilo del browser dell'utente, pertanto nessun componente aggiuntivo viene eseguito sulla pagina.\nIspezione HTTPS degli endpointDipende dal prodotto. Il traffico viene terminato all’interno di un processo Valve con firma digitale anziché in un browser riconosciuto, e diversi prodotti endpoint escludono le applicazioni firmate dall’ispezione TLS.\nIl filtro dei link SteamLa lista di blocco interna di Valve, consultata quando un link esce dall'ecosistema Steam. Questo è l'unico controllo che viene eseguito — e la tabella sopra riporta i risultati ottenuti per gli host di autenticazione descritti in questa sezione.\nUn test che qualsiasi lettore può eseguire; se il test fallisce, la conclusione non è valida\n\nApri uno degli URL di prova di \"Navigazione sicura\" pubblicati da Google (testsafebrowsing.appspot.com) in Chrome: compare una pagina interstiziale rossa a schermo intero. Se si apre lo stesso URL da un messaggio di chat Steam, in modo che venga visualizzato nel client Steam o nell'overlay, non compare alcuna pagina interstiziale. L’unico avviso che Steam può generare è la propria pagina «Link Filter», e solo per gli host presenti nell’elenco di Valve.\n\nIl record personale di Valve nel programma bug bountyQuello a un solo strato era già stato utilizzato in precedenza — proprio nell’album di Valve\n\nSe il Link Filter è l’unico controllo eseguito all’interno del client, le sue modalità di malfunzionamento non sono certo una questione secondaria. Due segnalazioni relative al programma HackerOne di Valve, entrambe accettate, entrambe risolte e entrambe rese note integralmente:\n\n#291750archiviato 2025-11-16 ↗Open Redirect · medium\nBypass della protezione del filtro dei link\n\nSegnalato il 19 novembre 2017, risolto e reso pubblico il 9 maggio 2018. La dimostrazione di fattibilità contenuta nella segnalazione stessa: la sostituzione del punto ideografico 。 (%E3%80%82) per il punto in un nome host — È possibile aggirare il blocco. L'interstiziale a cui si riferisce questa sezione non è stato visualizzato.\n\n#1079561archiviato 2026-09-24 ↗Divulgazione delle informazioni · elevata\nIl browser web Big Picture divulga i cookie di accesso e rivela informazioni sensibili (ciò potrebbe portare al furto dell'account)\n\nSegnalato il 15 gennaio 2021, risolto, reso pubblico il 21 settembre 2021. Il livello di gravità attribuito da Valve è elevato e il titolo ne indica le conseguenze. Il record divulgato riporta il titolo, la valutazione e le date; la descrizione tecnica non è inclusa nel payload pubblicato, pertanto non se ne riporta alcun altro estratto in questa sede.\n\nL'interpretazione degli autori, non una conclusione contenuta in nessuno dei due rapporti: I due si trovano ai lati dello stesso cancello. Uno è l’avviso che non compare prima che la pagina di destinazione si apra; l’altro è la sessione che abbandona il client una volta che una pagina è stata aperta al suo interno. La sequenza che segue una sessione rubata — chiave registrata senza richiesta di conferma, transazione reale annullata, duplicato inviato a un clone — è lo schema descritto in Sezione 5 a Sezione 8. Entrambe le segnalazioni sono state chiuse; nessuna delle due è stata classificata come vulnerabilità attiva. Quanto emerge da esse è più circoscritto, ma comunque sufficiente: l’unico livello rimasto presenta una storia documentata di aggiramento, secondo le stesse registrazioni di Valve.\n\nFonte: i dati relativi alla divulgazione di HackerOne per ciascuna segnalazione, recuperati 2026-09-22 — numero, titolo, team, vulnerabilità, gravità, date di segnalazione e di divulgazione e stato, così come pubblicati da HackerOne. Record di recupero: hackerone-reports.json. Qui non viene indicata alcuna cifra relativa alla taglia; non ne compare alcuna nel documento reso pubblico che è stato recuperato.\n\nOsservazione sul campo · PhishDestroyI rilevamenti che normalmente pongono fine a una campagna non hanno posto fine a queste\n\nAbbiamo osservato che gli host di phishing continuavano a generare traffico pur ospitando 20 o più rilevamenti di fornitori. Se diffusa via web o e-mail, una campagna in quella situazione fallisce nel giro di pochi giorni: sia il browser che l’antivirus agiscono in base a quei verdetti. All’interno di Steam, invece, non succede nulla di tutto ciò. I verdetti sono sempre esistiti. Nessuna parte del client li ha mai richiesti.\n\nCosa significa questo per un minore che ha un antivirus installato\n\nNon ignora nessun avviso e non disattiva nulla. Arriva un messaggio all’interno di Steam — un coltello gratuito, un voto per la squadra di un amico — e la pagina si apre all’interno di Steam. Non apre mai un browser, quindi il browser non lo protegge mai. Il suo antivirus è in esecuzione e potrebbe già classificare quel dominio come dannoso; ma non gli viene mai chiesto. Esistono già tutti gli avvertimenti che avrebbero potuto fermarlo. Ma nessuno di essi gli arriva. È convinto di non aver mai lasciato Steam, ed è vero.\n\nL'offerta gratuita non è un'invenzione del phisher: gli articoli gratuiti Valve sono il modo in cui i siti di skin e di gioco d'azzardo fanno pubblicità, ed è proprio per questo che il messaggio sembra del tutto normale. Reclami: l'archivio delle esecuzioni. Dati relativi all'età e ai figli: Sezione 17.\n\nFonti: Steam visualizza i contenuti web tramite il Chromium Embedded Framework nel steamwebhelper processo — vedi Analisi tecnica di DARKNAVY del 27 giugno 2024 ↗ e quello di Valve Steam Forum Beta per i clienti ↗ archiviato 2025-08-04 ↗. Non si fa ricorso ad alcuna versione CEF: Chromium integrato non è Chrome e non include nessuno dei servizi Google di Chrome. Navigazione sicura senza chiavi API: Documento di progettazione di Chromium ↗ archiviato 2026-08-21 ↗, Chiavi API di Chromium ↗ archiviato 2026-08-30 ↗ (“Molte delle API di Google utilizzate da Chrome sono specifiche di Google e non sono destinate all’uso in prodotti derivati”), e lo stesso effetto si riscontra in altre build senza chiave — Botte di birra artigianale n. 193814 ↗. URL di prova: testsafebrowsing.appspot.com ↗.\n\nDue orologi diversi\nL'età del dominio.Data dell'osservazione.\n\nLa data di creazione del registro indica quando un dominio è stato registrato. Un record OpenID datato indica l'host di ritorno presente in quel record. La prima non può coprire gli anni precedenti alla seconda.\n\nIl registro completo distingue tra un dominio registrabile a sé stante, il sottodominio proprio di un sito e un percorso diretto. Ogni riga rimanda alla sua fonte e al risultato dell'DNS.\n\nControlla il registro dei domini →· Scarica le date del registro ↗· Ripetere l'osservazione ↗\n\nParte A — Scheda tecnica · Sezione 4\nUn endpoint è stato chiuso. Il tracciamento pubblico ha perso una chiave.\nContesto e limiti della fonte\n\nSteam ha implementato modifiche che hanno rimosso la visibilità pubblica degli ID delle risorse e limitato l’accesso all’inventario tramite API. L’effetto: è diventato impossibile rintracciare un articolo specifico tramite il suo ID originale a partire dai dati pubblici. Di seguito viene illustrato ciò che era possibile prima, ciò che ha smesso di esserlo dopo e quali sono i costi che una vittima deve sostenere per provare dove siano finite le proprie proprietà. La data è il 2017 secondo l’account tecnico di CSFloat; non è stato individuato alcun changelog di Valve. La sequenza degli eventi — circa un anno dopo la dichiarazione sul gioco d’azzardo del luglio 2016 — costituisce l’oggetto dell’indagine, non una conclusione. I record degli oggetti rimangono all’interno dei sistemi di Valve; gli investigatori esterni hanno perso l’accesso alla catena degli ID originali, mentre gli identificatori float, seed e paint consentono solo una corrispondenza parziale.\n\nSi applica la regola Valve: Steam Il servizio di assistenza non ripristina gli elementi che sono stati rimossi dal tuo account, e spetta a te dimostrare cosa sia successo. Il record: Nel 2017, Valve ha chiuso l'endpoint che trasportava gli ID originali degli oggetti. Prima di allora, chiunque poteva seguire il percorso di una skin rubata dall'account della vittima fino a un bot su un marketplace. Da allora, nessuno al di fuori di Valve può più farlo. Il documento richiesto alla vittima è proprio quello che era stato nascosto — ed esiste ancora, all’interno di Valve.\n\nL'era precedente al blackout\n\nStoricamente, ogni oggetto virtuale generato su Steam possedeva un identificativo univoco a livello globale e immutabile ID risorsa. I database OSINT di terze parti potrebbero indicizzare questi ID. Se a un utente venisse sottratto un oggetto, gli investigatori potrebbero tracciare il percorso di quella specifica risorsa man mano che passa dall’account intermedio del malintenzionato agli account di archiviazione di un marketplace o di un sito di scommesse.\n\nPRIMA: chiunque, utilizzando dati pubblici, poteva tracciare un oggetto dall'account della vittima attraverso account intermedi fino a un bot di un marketplace o di un casinò.\nDopo il cambiamento\n\nSecondo l'account tecnico di CSFloat, Valve ha chiuso l'endpoint nel 2017 e gli ID originali degli oggetti hanno smesso di essere disponibili per soggetti esterni. Non è stata individuata alcuna dichiarazione da parte di Valve relativa al motivo di tale cambiamento. Nello stesso periodo, non è stata individuata nemmeno alcuna azione resa pubblica contro gli account bot commerciali che spostavano oggetti su larga scala.\n\nQualunque ne fosse la ragione, tale cambiamento ha interrotto la catena di custodia pubblica. Una vittima non può più ricostruire la catena di identificazione originale a partire dai dati pubblici per dimostrare che un determinato oggetto rubato sia stato venduto tramite un mercato o un casinò specifico. I registri relativi agli oggetti esistono ancora all’interno dei sistemi di Valve; il pubblico, i ricercatori e le forze dell’ordine che operano sulla base dei dati pubblici non possono accedervi.\n\nDOPO: non è più possibile risalire a un oggetto specifico tramite il suo ID originale (Asset ID) sulla base dei dati pubblici. La catena di custodia dell’ID originale per un oggetto spostato dopo il 2017 esiste solo all’interno dell’infrastruttura di Valve; nessun documento di questo tipo è stato reso pubblico. Gli identificatori float, seed e paint consentono solo una corrispondenza parziale e probabilistica.\nIEconItems_730\nOTTIENI/IEconItems_730/GetPlayerItems/v1/\nCarico utile tracciabile (versione precedente alla patch)\n\"id\": \"14892281934\",\n\"original_id\": \"11829910211\",\nStato: la vittima può tracciare la provenienza dell'oggetto attraverso i vari account dei bot.\nPayload offuscato (post-patch)\nAttuale\n\"id\": \"HIDDEN_BY_PRIVACY_SETTINGS\",\n\"original_id\": \"NULL\",\nStato: i soggetti esterni non possono più risalire alla provenienza di un articolo tramite l'ID asset originale a partire dai dati pubblici.\nEffetto sulle prove: Dopo la modifica, i dati pubblici necessari per tracciare una voce specifica tramite il suo ID Asset originale dall’account di una vittima fino a un bot di marketplace o di casinò non erano più disponibili. I registri interni esistono ancora su Valve; una vittima, un ricercatore o un investigatore che operi sulla base di dati pubblici non è in grado di ricostruire la catena dell’ID originale (gli identificatori float, seed e paint consentono solo una corrispondenza parziale).\n\nFonte: resoconto tecnico di CSFloat relativo alla chiusura del 2017 di IEconItems_730/GetPlayerItems — blog.csfloat.com/how-floatdb-tracks-items (archiviato 2026-09-21) · i payload riportati servono a illustrare la forma del campo e non rappresentano risposte effettive · non è stato individuato alcun changelog Valve relativo alla chiusura.\n\nParte A — Scheda tecnica · Sezione 5\nUna sessione. Un accesso più ampio di quanto l'utente possa vedere.\nContesto e limiti della fonte\n\nL'architettura delle chiavi API di Valve, così come era prima delle modifiche del 2023, si discostava dagli standard di riferimento del settore (OWASP ASVS, NIST SP 800-63B) ed è il meccanismo descritto nelle denunce automatizzate relative al furto di inventario conservate nell’archivio delle prove (Sezioni 6–8).\n\nSi applica la regola Valve: il titolare del conto ha creato la chiave, ha accettato i termini e si fa carico della perdita: questa è la risposta contenuta nei rifiuti archiviati. Il record: Fino a dicembre 2023, bastava un semplice cookie di sessione rubato per registrare quella chiave. Nessuna password. Nessun Steam Guard. Nessuna notifica al titolare dell'account. L'utente non ha creato la chiave, non poteva vederla, eppure gli è stato detto che l'aveva fatto. La conferma tramite cellulare è stata aggiunta il 2023-12-04 — circa sette anni dopo la dichiarazione del 2016 e circa sei anni dopo i panel relativi alle truffe conservati nell’archivio. Quegli anni non sono stati pagati da Valve. Sono stati pagati dai conti svuotati nel frattempo, alcuni dei quali appartenevano a minori.\n\nOWASP ASVS 2.8 / NIST SP 800-63BGRAVITÀ: CRITICA\n1. Autenticazione a più livelli insufficiente\n\nSteam consentiva la generazione di chiavi API con privilegi elevati e di lunga durata utilizzando solo un cookie di sessione. Non era richiesta alcuna autenticazione a due fattori (Steam Guard) né alcuna verifica di autenticazione avanzata durante la configurazione o la modifica di una chiave API per sviluppatori, pertanto la conferma tramite dispositivo mobile Steam Guard — l’unico secondo fattore offerto da Steam — non proteggeva questa fase. (Nel 2016, nel tracker di Valve stesso, era stato richiesto un secondo fattore hardware e la questione è ancora aperta: Appendice D, GH-01.)\n\nStato: non corretto prima del 2023. Consentiva a uno script in possesso di un cookie rubato di registrare una chiave senza alcuna interazione da parte dell'utente.\nOWASP A01:2021 / Principio del privilegio minimoGRAVITÀ: CRITICA\n2. Mancanza del principio del privilegio minimo\n\nL'API Web Steam non prevedeva alcun ambito di autorizzazione basato sui ruoli. Una chiave API rilasciata a uno sviluppatore per lo stato dell'inventario in \"sola lettura\" disponeva di autorizzazioni complete in \"scrittura\", compresa la possibilità di modificare operazioni esistenti, avviarne di nuove, registrare webhook e rifiutare scambi validi in sospeso.\n\nStato: difetto di progettazione sistemico. Una chiave = controllo completo in lettura e scrittura sull'inventario e sulle operazioni dell'account.\nOWASP A07:2021 / SessioniGRAVITÀ: ALTA\n3. Gestione delle sessioni non funzionante\n\nGli utenti hanno segnalato che le sessioni web dirottate provenienti da intervalli di indirizzi IP di server di hosting continuavano a persistere. La prassi standard prevede la chiusura delle sessioni in caso di anomalie geografiche e in seguito alla modifica della password; le segnalazioni degli utenti raccolte nell'archivio descrivono sessioni rimaste attive anche dopo la modifica della password.\n\nStato: comportamento segnalato (reclami degli utenti presenti nell'archivio). Le sessioni potevano generare chiavi API senza una nuova autenticazione.\nIl blocco a livello di dominio era tecnicamente fattibileFATTIBILITÀ DELL'APPLICAZIONE\n4. Il blocco a livello di dominio degli host di autenticazione era tecnicamente fattibile\n\nValve gestisce già un elenco di domini (il Link Filter) e riceve già ogni nome host di autenticazione nelle proprie richieste OpenID. I due meccanismi non sono collegati in alcun modo visibile dall’esterno: al 2026-09-22, in 26 coppie il dominio principale era presente nel filtro mentre il proxy che ne gestiva l’accesso non lo era.\n\nCollegarli è un’operazione di ingegneria piuttosto semplice: leggi il openid.realm rilevare il nome host di ogni richiesta in entrata, confrontarlo con un elenco e rifiutare o contrassegnare la richiesta. L’illustrazione a destra mostra la struttura di una routine di questo tipo. Il rifiuto dell’host di autenticazione — anziché limitarsi alla sola pagina di destinazione pubblica — interromperebbe la fase “Accedi con Steam” da cui dipendono queste piattaforme.\n\nNon vi sono prove pubbliche che dimostrino che Valve effettui tale verifica. La commissione complessiva del Steam Community Market, pari a circa 15%, si applica alle vendite concluse all’interno del Market; non viene invece riscossa sulle transazioni esterne a queste piattaforme.\n\nblock_auth_hosts.pyILLUSTRAZIONE\n// Leggi l'host Steam già ricevuto — nessuna scansione\ndef on_openid_request(request):\nhost = parse_openid_realm(request)\nse host in domini_bloccati:\nrifiutare (la richiesta)\nNota: Pseudocodice a solo scopo illustrativo. Entrambe le parti esistono già in Valve: il nome host dell’autore è presente nella richiesta e l’elenco dei domini costituisce il filtro dei link. Non esiste alcun documento pubblico che spieghi perché non siano collegati.\nSezione 5.1 — Le norme non erano state ritirate dalla pubblicazione\nValve viene compilato ogni giorno secondo queste regole. In questo caso, però, la compilazione non è avvenuta secondo tali regole.\n\nSteam è disponibile su App Store e Google Play, effettua vendite tramite i principali gestori di pagamenti con carta e utilizza API di terze parti come qualsiasi altra grande piattaforma. Ciascuno di questi rapporti comporta un requisito di sicurezza pubblicato e datato che Valve deve soddisfare per poter continuare a operare. Confronta le date di tali requisiti con quelle in cui l’API Web di Steam ha acquisito le stesse protezioni. Nessuno dei dati riportati di seguito è uno standard privato, una nota interna o un segreto commerciale: ogni riga è un documento pubblico con una data di pubblicazione.\n\nRequisiti di sicurezza esterni pubblicati, con le relative date, messi a confronto con la data in cui l’API Web Steam ha acquisito il controllo equivalente\nLa norma pubblicata e la data di entrata in vigore\tL'API Web Steam relativa alla stessa domanda\nAutorizzazione limitataOAuth 2.0 — RFC 6749, Ottobre 2012. La sezione 3.3 definisce scope in modo che un client riceva solo l'accesso che richiede. Da allora, questa è stata l'impostazione predefinita di tutte le principali API delle piattaforme.\tGli scope granulari sono stati introdotti il 16 gennaio 2026.Prima di allora, una singola chiave API Web Steam consentiva pieni diritti di lettura e scrittura sulle operazioni dell'account, indipendentemente dal motivo per cui era stata emessa. Tredici anni e tre mesi dopo la specifica che definisce il controllo.\nUna chiave non è un'autorizzazioneLa documentazione ufficiale di Google sul Cloud: Una chiave API standard non autentica un soggetto, e per le API che creano o gestiscono risorse, Non utilizzare le chiavi di autorizzazione in ambiente di produzione.\tLa chiave API Web Steam era proprio quella.Una stringa al portatore, assegnata a un conto, sufficiente di per sé a leggere l’inventario, annullare un’operazione in sospeso e inviarne una nuova. Al momento dell’utilizzo non è stato autenticato alcun soggetto.\nAutenticazione a più fattori per l'accesso privilegiatoPCI DSS 3.2, requisito 8.3 — obbligatorio a partire dal 1° febbraio 2018 per tutte le operazioni amministrative non effettuate tramite console e per tutti gli accessi remoti all’ambiente contenente i dati dei titolari di carte. Apple ha quindi richiesto l’autenticazione a due fattori per tutti i titolari di account del Programma per sviluppatori a partire dal 27 febbraio 2019: Gli sviluppatori che ricoprono il ruolo di \"Titolare dell'account\" in un programma per sviluppatori dovranno abilitare l'autenticazione a due fattori per effettuare l'accesso.\tEra necessario un secondo fattore per creare una chiave API da 4 dicembre 2023.Fino ad allora era sufficiente un cookie di sessione rubato, senza alcuna richiesta di conferma sul telefono del titolare dell'account né alcuna notifica successiva. Quattro anni e nove mesi dopo che Apple stessa ha reso necessario l’uso di un secondo fattore di autenticazione anche solo per accedere a un portale per sviluppatori.\nCiclo di vita e revoca delle credenzialiTwitch richiede che ogni applicazione di terze parti: L'app deve verificare la validità del token OAuth all'avvio e, successivamente, ogni ora, e precisa che effettua controlli sulle applicazioni che non lo fanno. La sua API legacy v5 è stata definitivamente dismessa il 28 febbraio 2022 secondo un calendario pubblicato.\tNon è stata pubblicata alcuna documentazione relativa al ciclo di vita delle chiavi.La modifica del 2023 ha protetto l’endpoint di creazione. Nessuna dichiarazione Valve associata a tale modifica fa riferimento alle chiavi già registrate, e la modifica non è stata accompagnata da alcun changelog. Dai dati pubblici non è possibile stabilire se le chiavi create prima di tale modifica siano state invalidate — ed è proprio questa la domanda a cui un interessato avrebbe bisogno di una risposta per sapere se una chiave creata sul proprio account anni prima sia ancora attiva.\nPunto di riferimento architettonico // Token Architecture\nAmbiti dettagliati di GitHub rispetto alle API Web Valve Steam\n\nValve sviluppatori gestiscono quotidianamente software open source su GitHub utilizzando token granulari basati sul principio del privilegio minimo. Si pensi invece alla chiave monolitica rilasciata a 130 milioni di Steam giocatori.\n\nToken a granularità fine di GitHub\nUtilizzato da Valve su GitHub\n\nToken a granularità fine con isolamento per ambito e applicazione obbligatoria del ciclo di vita.\n\nAccesso al repository:Solo repository selezionati (1 repository)\nRilascio delle autorizzazioni:Sola lettura [✓]\nCodice e segreti:Accesso negato [✕]\nScadenza:30 giorni (TTL obbligatorio)\nRegistrazione degli audit:IP, User-Agent e data e ora\nStato della sicurezza: Il token con privilegi minimi limita il danno a una singola risorsa di sola lettura.\n!Valve Steam Chiave API Web\nDistribuito a 130 milioni di utenti\n\nStringa master unica di 32 caratteri che contiene l'autorizzazione \"tutto o niente\" per le operazioni commerciali e di inventario.\n\nAccesso all'account:ACCOUNT COMPLETO (monolitico)\nGestione delle operazioni:Leggi, Annulla, Rifiuta [!]\nAmbiti granulari:NESSUNO (Arrivato nel 2026, con 13 anni di ritardo)\nScadenza:MAI (Valido a tempo indeterminato)\nRegistrazione dei controlli:NESSUNO (Cronologia IP pari a zero per l'utente)\nVulnerabilità: La chiave rubata consente l'intercettazione silenziosa di tutte le offerte commerciali in uscita.\nLo standard applicato in una sola direzione\n\nSupponiamo che un fornitore Valve — un provider cloud, un gestore di pagamenti, un CDN — abbia lasciato un endpoint per le credenziali privo di autenticazione a due fattori e che, mesi dopo, i dati aziendali di Valve siano trapelati tramite una chiave generata su quell’endpoint. Valve accetterebbe che la colpa ricadesse su chiunque abbia cliccato sul link? I rifiuti archiviati e conservati in questo dossier rispondono alla domanda speculare per l’utente: la posizione assunta è che il titolare dell’account abbia creato la chiave e debba quindi sostenere la perdita. La stessa architettura viene descritta come un fallimento del fornitore da un lato e una responsabilità dell'utente dall'altro. Se sia così o meno non è una questione tecnica, né è una questione che questa indagine possa risolvere: spetta a un tribunale o a un’autorità di vigilanza decidere in merito.\n\nIllustrazione, non prova — lo standard interpretato al contrario\nUn sistema di elaborazione dei pagamenti che consentiva a uno script di terze parti di generare credenziali di transazione con privilegi completi utilizzando esclusivamente un cookie del browser, senza alcuna richiesta di conferma da parte del titolare del conto.\nUn provider di identità che ha chiuso la falla attraverso la quale erano stati emessi i propri token e non ha pubblicato alcuna informazione sui token già emessi.\nUna banca che, in risposta a un bonifico contestato, ha osservato che le credenziali utilizzate erano registrate sul conto dello stesso cliente e ha chiuso la pratica.\n\nNessuna di queste considerazioni va intesa come una conclusione relativa a una specifica società. Si tratta delle stesse scelte progettuali, trasferite in un contesto in cui la risposta delle autorità di vigilanza è ben documentata: ed è proprio questo il confronto che viene chiesto all’autorità di regolamentazione di effettuare.\n\nCosa emerge dai fatti: i controlli assenti dall'API Web Steam erano pubblici, obsoleti e, in diversi casi, rappresentavano condizioni Valve che l'azienda doveva soddisfare per poter continuare a distribuire i propri prodotti. L'intervallo tra ciascuno standard e la modifica equivalente Steam è misurabile ed è indicato sopra. Ciò che non chiarisce è il motivo. Non è stata individuata alcuna Valve motivazione relativa a nessuno di questi intervalli, né se ne ipotizza alcuna in questa sede; tale documento è contenuto in Valve e non è stato pubblicato.\n\nFonti, tutte costituite da documenti pubblici: OAuth 2.0 — RFC 6749, ottobre 2012 ↗ · Google Cloud — Documentazione sulle chiavi API ↗ · Requisito 8.3 della norma PCI DSS 3.2 — Guida alle risorse del PCI SSC ↗ · Apple — Prossima introduzione dell'autenticazione a due fattori per i titolari di conto, 20 febbraio 2019 ↗ archiviato 2025-05-06 ↗ · Twitch — Requisiti di convalida dei token ↗ e il Avviso di chiusura della versione 5 ↗ archiviato 2025-01-27 ↗. Le date relative a Steam sono quelle riportate nel record di aggiornamento presente in questa sezione; le voci relative al 2023 e al 2026 sono quelle che Valve ha distribuito senza un log delle modifiche. Estratto il 2026-09-22.\n\nIl registro degli aggiornamenti di Valve — datato, tratto da fonti pubbliche\nData\tValve modifica\tÈ stato annunciato?\tCosa ha chiuso\tRitardo: meccanismo pubblico → risolto\tFonte\n2026-09-01\tSegnalazione automatica delle chat sospette\tSì\tLink e schemi pericolosi nelle chat di gruppo\t—\tnotizie ↗\n2026-01-16\tAmbiti granulari dell'API Web di Steamworks\tSì\tAmbiti con privilegi minimi per le chiavi degli sviluppatori\t—\tannuncio ↗\n2025-07-15\tCS2: Protezione delle operazioni e finestra di inversione\tSì\tNiente. Non si tratta di una soluzione di sicurezza che risolva il problema alla radice. L’accesso per il recupero dell’account da parte del supporto rimane invariato. L’attivazione della revoca comporta un blocco automatico delle operazioni di trading della durata di 30 giorni (Skinvault ↗), mentre lo shock sul mercato a pronti ha provocato un crollo della capitalizzazione di mercato pari a $104M (-25%) nelle ultime 24 ore (CSMarketCap ↗). Nel 2026, i timer sono diventati specifici per ogni articolo (Skin.land ↗).\t—\tDomande frequenti ↗\n2025-05-14\tAvviso sulla sicurezza dell'account\tSì\tLinee guida su Stealer / dirottamento di sessione\t—\tannuncio ↗\n2024-10-02\tCS2 \"The Armory\" - Blocco di 7 giorni\tSì\tMetti in attesa lo scambio/la vendita degli oggetti dell'Armeria\t—\tannuncio ↗\n2024-09-18\tRestrizione commerciale relativa all'accesso da un nuovo dispositivo\tSì\tBlocco delle transazioni da 2 a 7 giorni sui nuovi dispositivi\t—\tDomande frequenti ↗\n2024-02-14\tSospensione della modifica del nome del profilo e dell'avatar\tSì\t2–4 ore di attesa per le transazioni dopo la modifica del nome\t—\tpubblica ↗\n2023-12-04\tConferma tramite dispositivo mobile per le chiavi API\tNessun registro delle modifiche\tRegistrazione silenziosa della chiave tramite cookie\tcirca 6 anni dopo i pannelli dell'epoca del 2017\tpagina di sviluppo ↗\n2023-10-24\tAutenticazione a più fattori via SMS per la pubblicazione delle build dei giochi\tSì\tPubblicazione delle build su Steamworks\t—\tannuncio ↗\n2023-07-12\tAvviso relativo ai contenuti della biografia personalizzata\tSì\tLink di phishing nelle biografie\t—\tforum ↗\n2023-01-25\tProfilo {LINK RIMOSSO} e tempo di ricarica\tSì\tLink nel testo del profilo\t—\tDomande frequenti ↗\n2022-10-24\tRiorganizzazione della procedura di accesso e troncamento dei cookie\tNessun registro delle modifiche\tSessioni rubate infinite\t— (Migrazione dei token di IAuthenticationService)\tnotizie ↗\n2022-10-12\tApp mobile 3.0: accesso tramite codice QR\tSì\tPannello di revoca dell'autorizzazione alla sessione\t—\tnotizie ↗\n2022-05-10\tRimuovi gli endpoint di annullamento delle operazioni\tNessun registro delle modifiche\tScambio di offerte (annullamento e reinvio)\tcirca 5 anni dopo i pannelli del 2017\tnumero 325 ↗\n2020-05-25\tBlocco delle transazioni di 7 giorni in Dota 2\tSì\tVendita rapida di articoli\t—\tblog ↗\n2018-03-29\tBlocco delle transazioni di 7 giorni in CS:GO\tSì\tRiciclaggio istantaneo tramite bot\tcirca 20 mesi dopo la dichiarazione del luglio 2016\tblog ↗ archiviato 2025-02-26 ↗\nFonti: i post Valve collegati, le pagine di aiuto e le segnalazioni su GitHub, come indicato nelle date. Tre correzioni decisive sono state rilasciate senza changelog (maggio 2022, ottobre 2022, dicembre 2023) e sono state individuate dagli utenti, non annunciate da Valve — tale asimmetria fa parte del registro delle misure adottate. I ritardi vengono calcolati solo nei casi in cui la datazione del dossier stesso (dichiarazione del luglio 2016; panel sulle truffe del 2017) fornisca il punto di partenza; “—” indica che in questo caso tale punto di partenza non è stato stabilito.\nParte A — Scheda tecnica · Sezione 6\nSimulatore interattivo di exploit e dirottamento\nContesto e limiti della fonte\n\nUna ricostruzione del percorso che va dal messaggio di phishing alla registrazione della chiave lato server e allo scambio di titoli. Prima del 2023, una chiave API Web registrata su un account poteva leggere il proprio portafoglio, annullare un'offerta di scambio in sospeso e crearne una nuova, senza che al titolare dell'account venisse mostrata alcuna schermata di conferma dello scambio per nessuna di queste azioni. Si tratta di una violazione del principio del privilegio minimo (OWASP A01:2021). I tempi riportati in questa simulazione sono puramente indicativi e non corrispondono a misurazioni in tempo reale dell’attuale piattaforma.\n\nSegui passo dopo passo la ricostruzione del dirottamento. Ogni fase mostra ciò che vede il titolare dell'account e, accanto, la chiamata Steam ricevuta nello stesso momento. Ciascuna di queste chiamate viene autenticata correttamente. Nessuna parte della sequenza richiede che l'autenticazione di Steam fallisca: è necessario che la chiave da essa emessa non abbia alcun ambito di applicazione (OWASP A01:2021).\n\nCiò che vede il giocatore. Ciò che cambia dietro di lui.SIMULATORE DI PROCEDURA PASSO PASSO\nPassaggio 5 / 5\n\nL'exploit è stato completato. Convinto che stia per ricevere una notifica sul cellulare relativa alla transazione originale, la vittima approva la transazione sostitutiva. Si tratta di una simulazione forense integrata che illustra come l’assenza del principio del “privilegio minimo” (OWASP A01:2021) consenta il dirottamento automatizzato delle risorse in meno di un secondo.\n\n01 / L'ESCA DA CHATUn amico mi chiede di votareLa vittima riceve un messaggio contenente un link.\n02 / L'ACCESSOUn portale di sosiaLa vittima inserisce le credenziali di accesso.\n03 / L'ACCESSOCreazione di API per il Silent WebL'autore dell'attacco registra una chiave di sviluppatore.\n04 / IL CAMBIOScambio commerciale legittimoIl bot \"Clone\" duplica il destinatario di destinazione.\n05 / CONFERMAContraffazione approvataOfferta errata approvata dal cellulare.\nLo stesso passaggio, visto dalla reteRicostruzione dell'andamento precedente al 2023 · forme illustrative delle chiamate\nVittimaApprova il messaggio di conferma sul dispositivo mobile previsto per l'operazione originale.\nAttaccanteRiceve gli articoli sull'account clone.\nSteam vedeUn trasferimento confermato dal titolare del conto su un dispositivo registrato.\nConfirmation genuine — made by the account holder\nRecipient the clone bot, not the intended counterparty\nThe confirmation is authentic. The offer it confirms is not the one the user initiated.\n\nLa traccia lasciata: un'operazione approvata dall'utente. Questo è il record che il supporto Steam consulta quando riceve il reclamo, ed è il motivo per cui i reclami archiviati sono stati chiusi come \"errore dell'utente\". I reclami si trovano in l'archivio delle misure esecutive.\n\nParte A — Scheda tecnica · Sezione 7\nI punti finali alla base della sequenza.\nContesto e limiti della fonte\n\nQuesti sono i Steam endpoint delle API Web che gli script di dirottamento segnalati hanno utilizzato per intercettare le operazioni di trading senza passare attraverso le fasi di conferma lato browser.\n\nQuattro endpoint documentati sono sufficienti a svolgere l'intero compito. Nessuno di essi presenta difetti, né è necessario sfruttarne alcuno: una chiave valida li chiama e Steam risponde. La chiave è l'unica cosa che l'aggressore doveva rubare.\n\nIEconService / GetTradeOffers / v1SONDAGGIO\n\nUtilizzato per monitorare le offerte di trading dell'account. Gli script interrogano ripetutamente questo endpoint utilizzando la chiave API compromessa; esso restituisce i dettagli delle offerte di trading appena create, in sospeso o modificate. Gli intervalli di interrogazione non vengono misurati in questa sede.\n\nVettore di minaccia: Mostra gli ID delle offerte commerciali in sospeso e i dettagli del profilo del destinatario.\nIEconService / CancelTradeOffer / v1INTERAZIONE\n\nUtilizzato per invalidare in modo programmatico l'offerta di scambio legittima dell'utente. Prima del 2023 la chiave non era protetta da alcuna autenticazione a più livelli, pertanto un server automatizzato poteva annullare un'offerta non appena veniva rilevata, senza alcun avviso al titolare dell'account.\n\nVettore di minaccia: Annulla l'operazione prima che il titolare del conto completi la conferma tramite cellulare.\nISteamUser / GetPlayerSummaries / v2RECON\n\nÈ stata eseguita una query per recuperare il nome del profilo, l'URL dell'immagine dell'avatar e il livello del destinatario legittimo della transazione. Ciò consente allo script di personalizzare un account clone già pronto in modo che corrisponda. In questa fase non viene misurato alcun tempo.\n\nVettore di minaccia: Fornisce i dati necessari per spacciarsi per il destinatario previsto.\n/dev/ajaxregisterkeyCREAZIONE\n\nL'endpoint di registrazione di Steam per le chiavi. In passato, qualsiasi sessione attiva di cookie del browser (`steamLoginSecure`) poteva registrare una chiave senza una conferma Steam Guard sul dispositivo mobile e senza alcuna notifica al titolare dell'account.\n\nVettore di minaccia: Una credenziale permanente creata da uno script, all’insaputa del titolare dell’account.\nParte A — Documentazione tecnica · Sezione 8 · Articolo 7 del GDPR\nUna casella spuntata. Chi l'ha spuntata?\nContesto e limiti della fonte\n\nNel rifiutare il rimborso, Steam Le risposte dell'assistenza conservate nell'archivio sostengono che il titolare dell'account abbia creato la chiave API e, spuntando la casella, abbia accettato i termini.\n\nLa risposta del servizio di assistenza attribuisce la chiave al titolare del conto. La domanda è se il documento permetta di stabilire chi lo abbia effettivamente creato.\n\nNel modello di dirottamento della chiave API osservato, tuttavia, la vittima non ha mai visualizzato né visitato la pagina di creazione della chiave API. Il campo relativo al consenso viene inviato da uno script che esegue un POST “headless” utilizzando il cookie di sessione rubato.\n\nAi sensi dell’articolo 7 e dell’articolo 4, paragrafo 11, del GDPR, il consenso deve costituire un’indicazione della volontà dell’interessato, liberamente espressa, specifica, informata e inequivocabile. La posizione degli autori è che un campo di accettazione dei termini inviato da uno script malevolo tramite un cookie rubato, senza che al titolare dell’account venga mostrata alcuna pagina, non possa soddisfare tale definizione. Spetta all’autorità di controllo stabilire se ciò avvenga effettivamente.\n\nAnalisi forense del payload: registrazione delle chiavi\nPOST https://steamcommunity.com/dev/ajaxregisterkey\n// Payload della richiesta (inserito tramite script di dirottamento)\n{\n\"agreeToTerms\": \"d'accordo\", <-- inserito automaticamente, senza intervento umano\n\"dominio\": \"localhost\", ← non convalidato — si accetta qualsiasi valore, compreso localhost\n\"sessionid\": \"8f0d8ef763ab2140bf89de2a\"\n}\nLa domanda rivolta all'autorità di vigilanza: nel caso in cui il titolare del conto non abbia mai selezionato la casella di consenso, se l’accettazione dei termini registrata a nome del conto soddisfi il requisito di cui all’articolo 7, ovvero che si tratti di un’indicazione della volontà dell’interessato espressa liberamente, in modo specifico, informato e inequivocabile, e se Steam il Servizio di assistenza possa farvi riferimento per respingere un reclamo.\n\nFonte: formato della richiesta di registrazione della chiave, ricostruito sulla base dell’endpoint pubblico e delle segnalazioni di dirottamento conservate nell’archivio delle prove (versione ricercabile di 2026-09-17) · L'identificatore di sessione visualizzato è un segnaposto, non un valore acquisito.\n\nAutopsia forense · Il vettore di sostituzione commerciale\nCome Valve ha finalmente neutralizzato la “sostituzione commerciale” — e perché ci sono voluti 7 anni di soluzioni alternative\n\nDa quasi un decennio, il \"Sostituzione della chiave API\" (o truffa MitM tramite API) è stato il modello di furto di account più redditizio su Steam, sottraendo centinaia di milioni di dollari in skin a giocatori ignari. Valve non ha eliminato la vulnerabilità correggendo l’architettura API vulnerabile; al contrario, Valve ha impiegato sette anni per sovrapporre quattro barriere di attrito a livello di piattaforma che hanno paralizzato la liquidità degli scambi all’interno della comunità, senza risolvere la causa alla radice.\n\n1. La morte per mimetismo\nTempo di attesa per avatar e nome (febbraio 2024)\n\nL'attacco richiedeva una mimica in frazioni di secondo: il bot truffaldino intercettava un'operazione in uscita, estraeva l'avatar e il nome del destinatario tramite ISteamUser, e ha clonato il profilo in 200 ms. Il 14 febbraio 2024, Valve ha introdotto in sordina un obbligo Tempo di attesa per le transazioni da 2 a 4 ore (Errore 34) subito dopo qualsiasi modifica del nome del profilo o dell'avatar. Un bot non può più clonare un destinatario al volo senza essere escluso dalle negoziazioni.\n\n2. La morte economica\nInversione di tendenza CS2 a 7 giorni (luglio 2025)\n\nValve ha introdotto misure unilaterali Inversioni di tendenza nel mercato per gli oggetti di Counter-Strike. Ogni skin scambiata viene contrassegnata come \"Protezione scambio\" per sette giorni. Se una vittima scopre una sostituzione, clicca su \"Annulla scambio\" nella sezione Assistenza Steam e la skin viene immediatamente restituita al proprio inventario, mentre il destinatario viene bloccato. Poiché il blocco dello scambio di 7 giorni impedisce ai truffatori di trasferire l’oggetto su un sito di incasso, il furto risulta non redditizio.\n\n3. La morte del “Silent Key”\nImplementazione obbligatoria delle notifiche push su dispositivi mobili per l’API (dicembre 2023)\n\nIn passato, un cookie di sessione rubato consentiva a script dannosi di eseguire una richiesta POST in background senza interfaccia grafica verso /dev/ajaxregisterkey senza avvisare la vittima. Il 4 dicembre 2023, Valve ha reso obbligatoria una conferma esplicita tramite notifica push sull’app mobile Steam per generare una chiave API Web, eliminando così l’assegnazione silenziosa delle chiavi in background.\n\n4. Avvisi in-app sui dispositivi mobili\nBanner con l’anzianità e il nome dell’account (2022–2024)\n\nValve ha rinnovato la finestra modale di conferma su dispositivo mobile per visualizzare il partner commerciale Steam anzianità del conto (data di apertura), livello Steam e un avviso esplicito di colore ambra: \"Questo utente ha recentemente modificato il nome del proprio profilo\", rompendo così l'illusione ottica per le vittime più attente.\n\nI tre difetti del “patchwork” di Valve: perché i truffatori si sono semplicemente spostati su altri bersagli\n1. La scappatoia dell'esclusione dei giochi (Dota 2 e TF2)\n\nLe \"Trade Reversals\" sono state utilizzate esclusivamente per Counter-Strike 2. Gli oggetti di Dota 2 e Team Fortress 2 rimangono completamente privi di protezione a causa delle complessità legate alla creazione e all'incastonatura. Gli oggetti di alto livello del valore di migliaia di dollari (Dragonclaw Hooks, Golden Baby Roshans, Unusual TF2 burning flames) non prevedono alcun periodo di recesso. I truffatori hanno semplicemente reindirizzato l’intercettazione automatizzata tramite API verso i commercianti di Dota 2 e TF2, dove l’assistenza Steam applica rigorosamente la propria politica del 2016 che prevede «nessun ripristino degli oggetti».\n\n2. Il serbatoio \"Zombie Key\" (senza scadenza)\n\nMentre Valve ha aggiunto l'autenticazione a due fattori (2FA) tramite notifiche push sul cellulare per generare nuovo chiavi nel dicembre 2023, Valve non ha mai revocato, lasciato scadere o eliminato le chiavi API legacy esistenti. Milioni di account attivi che hanno generato chiavi (o per i quali sono state create chiavi in modo invisibile tramite phishing o malware prima del dicembre 2023) contengono ancora credenziali attive con scadenza pari a zero (nessun TTL) e timeout di inattività pari a zero. Gli autori delle minacce gestiscono enormi database storici contenenti queste chiavi persistenti, continuando a interrogare IEconService senza essere disturbato.\n\n3. La sanzione per la vittima: blocco delle operazioni di trading per 30 giorni\n\nAnche in CS2, Valve penalizza il giocatore vittima della truffa: cliccando su “Annulla scambio” in Steam Support si infligge automaticamente una sospensione obbligatoria di 30 giorni delle operazioni di trading e dell'accesso al Mercato Comunitario sull'account della vittima. Valve punisce l'utente con un mese di sospensione dalla piattaforma come misura deterrente contro le revoche \"infondate\", scoraggiando le vittime dal revocare le transazioni relative a articoli liquidi di valore inferiore.\n\nLo scandalo normativo fondamentale: sette anni di soluzioni alternative contro un unico ambito di applicazione dell’API\n\nPerché Valve ha dedicato sette anni a inventare blocchi sulle transazioni, tempi di attesa per gli account e blocchi reversibili sulle transazioni — sconvolgendo l'intera economia del gioco e causando una perdita di $104M in capitalizzazione di mercato — invece di adottare la soluzione standard del settore?\n\nCome dimostrato dal lancio ufficiale di Valve su Steamworks il 16 gennaio 2026 (Annuncio #493839547938902179 ↗), Valve già realizzati Gruppi di autorizzazioni granulari (Generale, Microtransazioni, Economia, Dati di vendita) e Lista bianca degli indirizzi IP per le chiavi di pubblicazione aziendali. Valve disponeva già da anni della soluzione tecnica. Una semplice casella di selezione visibile all'utente—\"Impedisci a questa chiave API Web di accedere a IEconService (Gestione delle operazioni)\" oppure una lista bianca degli indirizzi IP domestici — avrebbe sradicato la truffa della sostituzione commerciale nel 2018 senza alcun danno collaterale economico. Valve si è rifiutata di garantire ai giocatori abituali la protezione che aveva messo a punto per i propri partner aziendali.\n\nParte B — Norme e dati relativi all’applicazione · Sezione 9\nIl loro regolamento. Le piattaforme registrate.\nContesto e limiti della fonte\n\nQuesto registro mette in corrispondenza le clausole esplicite del Steam Accordo di abbonamento (SSA) e Steam Comportamento online (SOC) linee guida rivolte direttamente a entità commerciali attive e di grandi dimensioni.\n\nLa regola: nessun uso commerciale, nessun gioco d’azzardo, nessun bot — e Steam Il servizio di assistenza fa riferimento a queste clausole quando si rifiuta di restituire gli oggetti di una vittima. Il record: le stesse clausole, a prima vista, riguardano le piattaforme commerciali presenti in questo registro, che operano in base a Steam identità, Steam bot e Steam trasferimenti. La clausola viene applicata nei confronti della persona che ha smarrito le pelli e non, secondo quanto risulta da qualsiasi documento pubblico, nei confronti delle aziende che le hanno trasportate.\n\nNei reclami archiviati, Steam Support cita il \"Divieto di utilizzo commerciale\" e \"Nessuna automazione/bot\" clausole applicate nel rifiutare il ripristino dei beni alle vittime di frodi relative alle chiavi API. Le stesse clausole si applicano, a prima vista, alle piattaforme commerciali riportate nel presente dossier, che effettuano l’autenticazione tramite Steam OpenID e trasferiscono i beni tramite account automatizzati Steam. In questa sede non viene stimato alcun dato relativo al fatturato complessivo del mercato (si vedano le statistiche sull’applicazione delle norme riportate di seguito). Ciò che emerge dai dati è l’applicazione della norma ai singoli account nei casi archiviati e l’assenza di dati pubblicati relativi all’applicazione delle norme per operatore per le piattaforme. È proprio questa asimmetria che viene documentata in questa sezione.\n\nLa questione centrale / applicazione selettivaRegole → Proporzionalità → Responsabilità\nUn unico regolamento. Un’applicazione diseguale.\n\nIl registro riporta che i servizi commerciali utilizzano identità Steam, inventari, bot e trasferimenti come infrastruttura operativa. La SSA vieta lo sfruttamento commerciale e l’automazione senza autorizzazione. I reclami archiviati dimostrano che tale norma è stata applicata ai singoli account, mentre il registro pubblico non riporta un resoconto equivalente, operatore per operatore, per le piattaforme qui documentate. Pubblicare la norma, le prove e la decisione di applicazione per ciascuna di esse.\n\n189siti web inclusi nell'ambito dell'audit\n44percorsi con domini separati presenti nel registro attivo — 27 con un file di prove pubblicato, 17 raccolti manualmente. La sola verifica tramite browser dei 189 siti web ha risolto 25 di questi casi; il registro aggiunge i percorsi raccolti manualmente.\n12 anni e 6 mesicsgogem.com è stato bloccato nel filtro dei link; api.csgem.com registrato 2014-03-08 e mai bloccato — una delle 26 coppie di questo tipo al 2026-09-22\nTotale non verificatostima dei ricavi a livello di mercato esclusa\nSteam Comportamento online\n\"…non dovrai compiere, né tentare di compiere, alcuna delle seguenti azioni su Steam: […] Svolgere attività commerciali. Esempi di tali comportamenti vietati includono: pubblicare annunci pubblicitari; organizzare concorsi; gioco d'azzardo; l'acquisto o la vendita di account Steam; la vendita di contenuti, carte regalo o altri articoli; e l'accattonaggio.\"\n\nstore.steampowered.com/online_conduct ↗ archiviato 2026-09-21 ↗\n\nSSA § 2.G — Uso commerciale\n\"…[non è consentito] utilizzare i Contenuti e i Servizi, né alcuna loro parte, per scopi commerciali, salvo quanto espressamente consentito in altre parti del presente Contratto…\"\n\nCome riportato, le comunicazioni del Valve del 2016 facevano riferimento alla licenza personale e non commerciale. Nessun operatore ha presentato un’autorizzazione Valve in sede ufficiale. store.steampowered.com/subscriber_agreement ↗ archiviato 2026-09-18 ↗\n\nSteam Condizioni d'uso delle API web\n\"Non è consentito utilizzare l'API Web Steam o i Dati Steam in alcun modo che violi il Contratto di abbonamento Steam.\"\n\nI marketplace di skin di terze parti operano tramite account automatizzati che utilizzano l'API Steam. Il testo della regola non prevede alcuna eccezione per l'attività su scala commerciale. steamcommunity.com/dev/apiterms ↗ archiviato 2026-09-21 ↗\n\nSSA § 4.C\nAutomazione\n\nGli script, i bot e le interazioni non umane sono soggetti a restrizioni. Il registro rileva le operazioni di trading effettuate da bot, le “farm” di account e l’instradamento automatizzato su scala commerciale.\n\nIspezionare 153record contrassegnati con questa clausola ↗\nCosa prevede il regolamento in merito a questa clausola153 piattaforme contrassegnate\nApertura del caso15\nSkin Casino13\nMercato CS29\nRoulette della pelle8\ncsgoempire.com→csgoempirelogin4.comCasinò\nrollbit.com→rbsnin.comCasinò di criptovalute\n500.casino→fivezerozero.coCasinò autorizzato\n\nDi questi, 153 sono inoltre contrassegnati ai sensi dell’articolo 2.G della SSA e 2 sono inoltre classificati ai sensi del §1.C della SSA — gli stessi servizi rientrano in più di una clausola, motivo per cui gli esempi si ripetono.\n\n28 sono stati rilevati casi relativi all’153 che effettuavano l’autenticazione tramite un dominio registrabile separato. Un tag registra un’osservazione datata che fa rientrare la piattaforma, a prima vista, nell’ambito di applicazione della clausola; non si tratta di una violazione accertata, e per nessuno di essi è stata presentata un’autorizzazione Valve.\n\nSSA § 2.G\nUso commerciale\n\nLo sfruttamento commerciale richiede un'autorizzazione espressa. Confronta i modelli di business documentati, la loro portata ed eventuali autorizzazioni o misure di applicazione rese note.\n\nIspezionare 175record contrassegnati con questa clausola ↗\nCosa prevede il regolamento in merito a questa clausola175 piattaforme contrassegnate\nApertura del caso15\nSkin Casino13\nMercato CS29\nRoulette della pelle8\ncsgoempire.com→csgoempirelogin4.comCasinò\nrollbit.com→rbsnin.comCasinò di criptovalute\n500.casino→fivezerozero.coCasinò autorizzato\n\nDi questi, 153 sono inoltre contrassegnati ai sensi dell’articolo 4.C della SSA e 24 sono inoltre classificati ai sensi del §1.C della SSA — gli stessi servizi rientrano in più di una clausola, motivo per cui gli esempi si ripetono.\n\n28 sono stati rilevati casi relativi all’175 che effettuavano l’autenticazione tramite un dominio registrabile separato. Un tag registra un’osservazione datata che fa rientrare la piattaforma, a prima vista, nell’ambito di applicazione della clausola; non si tratta di una violazione accertata, e per nessuno di essi è stata presentata un’autorizzazione Valve.\n\nSSA § 3.A\nVPN e occultamento della posizione\n\nNascondere la propria residenza tramite un proxy IP può comportare la cessazione del servizio. Gli host di autenticazione con domini distinti richiedono un’analisi a parte: occorre stabilire cosa viene nascosto e quale regola si applica.\n\nVerificare le prove relative all’host di autenticazione ↗\nSteam Aiuto / Politica sugli URL\nOccultamento dei link\n\nSteam vieta l'uso di servizi di accorciamento dei link e di strumenti che nascondono la destinazione dei link. Un dominio di autenticazione separato — rbsnin.com nel flusso di accesso di Rollbit, auth.dota.trade in CS.MONEY — solleva la questione analoga di sapere se la destinazione indicata al verificatore OpenID di Steam identifichi il sito operativo.\n\nPolitica sugli URL di Valve ↗\n\nRiferimenti alle norme: Steam Contratto di abbonamento, versione del 10 settembre 2026 archiviato 2026-09-18 ↗ · Steam Condizioni d'uso delle API web archiviato 2026-09-21 ↗ · Steam Politica sugli URL (offuscamento dei link). I conteggi descrivono i documenti e i tag presenti in questo fascicolo; non si tratta di un conteggio delle violazioni accertate.\n\nIl deficit di fiducia\nChi riesamina la decisione quando il servizio di assistenza chiude il caso?\n\nI reclami conservati descrivono sanzioni permanenti, ricorsi rimasti senza risposta e rifiuti di restituire gli oggetti rubati. Confronta tali resoconti con la cronologia effettiva dei ticket, i rimedi disponibili e i registri di accesso agli account. Una spiegazione generica basata sul phishing non può stabilire chi abbia avviato un ripristino o creato una chiave API.\n\nLeggi i reclami registrati ↗Richiedi i documenti di riferimento →Grafico delle relazioni dei moderatori →\nParte B — Norme e dati relativi all’applicazione · Sezione 10\nUn'API di automazione. Una regola contro l'automazione.\nContesto e limiti della fonte\n\nLa domanda che questa sezione pone è come si concilino questi due aspetti: quali utilizzi dell’API sono autorizzati, da chi e in base a quali criteri pubblicati. Qui non viene stimato alcun numero di utenti commerciali autorizzati dell’API, né l’assenza di un elenco pubblicato implica alcuna cifra — l’assenza è il risultato, non un numero che sta dietro ad essa. I messaggi di assistenza Steam citati sopra sono riprodotti dal progetto ArchiSteamFarm nella propria FAQ (verificati alla lettera 2026-09-22); non si tratta di Valve pubblicazioni e gli account a cui sono stati inviati non sono identificati.\n\nLa norma (SSA § 4.C): Niente script, niente bot, niente sistemi non umani su Steam. Il record: Valve mette a disposizione un'API REST headless il cui unico scopo è l'automazione da server a server e fornisce la chiave a qualsiasi account. Gli utenti vengono bannati per l'uso di sistemi automatizzati; l'interfaccia di automazione è un prodotto sviluppato da Valve. Non è mai stato reso noto quali siano gli usi commerciali autorizzati.\n\nIl \"mito dello sviluppatore di videogiochi\"\nSDK di Steamworks (autentico)\n\nUtilizzato da studi di sviluppo di videogiochi autorizzati per integrare obiettivi, matchmaking e classifiche nei client dei propri giochi. Richiede una complessa integrazione in C++ e l’adesione come partner ufficiale.\n\nSteam API web (La scappatoia)\n\nUn'architettura JSON/REST \"headless\" progettata per server web esterni. Nel modello di \"hijack\" qui documentato, viene utilizzata per leggere gli inventari e gestire gli scambi peer-to-peer da server remoti; i suoi usi legittimi non sono riportati in questo dossier.\n\nA chi è destinata la chiaveUn utente Steam standard non ha alcuna necessità, all’interno dell’applicazione, di una chiave API Web; la pagina relativa alle chiavi si trova in un URL riservato agli sviluppatori e il suo scopo, come documentato, è l’accesso esterno lato server. Le segnalazioni archiviate relative a casi di dirottamento descrivono vittime che non sapevano dell’esistenza di tale pagina fino a quando non era stata registrata una chiave sul loro account.\nLa contraddizione dell'automazione\n\nLa sezione 4.C della SSA recita: \"Non è consentito utilizzare in alcun modo script, bot, macro o altri sistemi non controllati dall'uomo (\"Automazione\") per interagire con i Contenuti e i Servizi su Steam.\" Tuttavia, gli endpoint delle API Web (come CancelTradeOffer) non richiedono un'interfaccia utente né un captcha e aggirano completamente il client Steam. L'API è progettata per l'automazione da server a server; la regola vieta l'automazione da parte degli utenti; il confine tra le due non è reso pubblico.\n\nUn ruolo lato server nel flusso commerciale\n\nUna chiave API Web consente a un server di terze parti di intervenire sulle operazioni dell'account senza il client Steam. Nello schema di \"hijack\", tale server si interpone tra il titolare dell'account e il server delle operazioni.\n\n→Per le operazioni eseguite con il tasto non viene visualizzata alcuna schermata di conferma dell'operazione.\n→Consente il polling in background (GetTradeOffers).\n→Annulla e riemette le offerte senza l'intervento dell'utente.\nValve ha realizzato l'interfaccia, ha vietato l'automazione da parte degli utenti nelle proprie regole e non ha pubblicato alcun criterio che indichi quali usi commerciali siano autorizzati.\nParte B — Norme e dati relativi all’applicazione · Sezione 11\nDieci giorni richiesti. Dieci anni da rendere conto.\nContesto e limiti della fonte\n\nIl 20 luglio 2016 il responsabile legale di Valve ha concesso agli operatori di gioco d’azzardo un termine di 10 giorni. Dieci anni dopo (alla data della istantanea del dossier, 2026-09-21) almeno una piattaforma citata nei resoconti stampa relativi a tale avviso, CSGOFast, è ancora operativa con un host di autenticazione su dominio separato. Il testo è stato ricostruito qui di seguito sulla base dei resoconti stampa del 21 luglio 2016; la ricostruzione non è una scansione. Il verbale di applicazione della legge a cui l’avviso faceva riferimento non è stato pubblicato. La lettera aperta alla Commissione è Sezione 2.\n\nSi prega di leggere l’avviso del luglio 2016 riportato accanto alle osservazioni successive. Ciò che manca è un resoconto delle misure di applicazione adottate per ciascun operatore.\n\nUna settimana prima — il 13 luglio 2016, in pubblico\n\nIl 13 luglio 2016 archiviato 2026-09-21 ↗, Valve ha descritto come i siti di gioco d’azzardo utilizzassero Steam: OpenID per l’identificazione degli account e account automatizzati per le operazioni di trading. Valve ha affermato che l’utilizzo di tali meccanismi per gestire un’attività di gioco d’azzardo violava i suoi accordi relativi alle API e agli utenti. Sia la descrizione del meccanismo che il divieto sono contenuti nella dichiarazione datata dello stesso Valve. Al valore 2026-09-21, gli host di autenticazione con dominio separato sottoposti a test non hanno restituito alcun blocco da parte del filtro dei collegamenti, mentre al valore Valve non è stato pubblicato alcun record di applicazione specifico per operatore.\n\nALLEGATO A / LUGLIO 2016RICOSTRUZIONE TIPOGRAFICA\nVALVE CORPORATION\n\nBellevue, Stato di Washington\n\nDATA:Luglio 2016 (notizia riportata dalla stampa il 21 luglio 2016)\nDA:Karl Quackenbush, responsabile dell'ufficio legale\nOGGETTO:Intimazione di cessazione — uso commerciale degli account Steam\nNOTA:Ricostruzione del testo riportato; non si tratta di una scansione\n\n\"Siamo a conoscenza del fatto che Lei gestisce uno dei siti di gioco d'azzardo elencati di seguito. State utilizzando Steam account per svolgere tale attività. Ai sensi del Steam Contratto di abbonamento, i servizi Steam e Steam sono concessi in licenza esclusivamente per uso personale e non commerciale.\"\n\n\"Dovete cessare immediatamente e astenervi dall'utilizzare ulteriormente i vostri account Steam per qualsiasi scopo commerciale. Se non lo farete, entro dieci (10) giorni, Valve ricorrerà a tutti i rimedi disponibili, compresa, a titolo esemplificativo ma non esaustivo, la chiusura dei tuoi account.\"\n\nRicostruzione del fascicolo · consultare il documento originale\nKarl Quackenbush\nConsulente legale, Valve Corp.\nA MARGINE / EDITORIALE\nDieci giorni.E poi?\n\nLa scadenza era ben precisa. Anche l'impegno da parte dell'opinione pubblica dovrebbe esserlo.\n\nLa posizione di Valve pubblicata su “2016” ↗\nUna nota sulla scadenza +\nSATIRA / NON È UNA LETTERA ALLA REDAZIONE\n\nCara scadenza,\n\nTi erano stati concessi dieci giorni. In qualche modo, il calendario era l’unica cosa che continuava a funzionare.\n\nSi prega di inoltrare eventuali risposte al registro pubblico.\n\nCronologiaLuglio 2016 – settembre 2026\nTermine indicato nell'avviso:\n10 giorni\nLuglio 2016\nTempo trascorso dalla notifica:\n3,715 giorni\nDato fisso relativo al periodo dal 20 luglio 2016 alla data di riferimento del 21 settembre 2026; non si tratta di un dato in tempo reale\nDocumentazione relativa alle misure di esecuzione rese pubbliche:\nNessuno\nNon è stato individuato alcun registro per operatore relativo alle interruzioni o ai blocchi\n\n◀ Giorni 0–10 — la scadenza, in scalaGiorno 3715 — l'istantanea ▶\n\n20 luglio 2016Emissione di una richiesta con scadenza di dieci giorniGiorno 0\n17 febbraio 2024Si applicano gli obblighi previsti dal DSAGiorno 2,768\n25 febbraio 2026Annunciata la denuncia del Procuratore Generale di New YorkGiorno 3,507\n21 settembre 2026Panoramica del dossierGiorno 3715\n\nDieci anni dopo, CSGOFast — citato nei resoconti giornalistici relativi alle segnalazioni del 2016 — è operativo: csgofast.com ha restituito un blocco del filtro dei link su 2026-09-19 e 2026-09-21, mentre il suo host di autenticazione steam-login.authtofast.com (registrato 2026-06-30) non l'ha fatto.\n\nRegistro completo e datato delle modifiche alla sicurezza di Valve: Cronologia della sicurezza → · Il caso di Washington e il criterio di applicazione: di seguito\n\nCosa emerge dai dati: L'avviso del 2016 fissava un termine di 10 giorni; Valve gestiva già un elenco di domini (il Link Filter) e riceveva i nomi host autorizzati nelle proprie richieste OpenID; non è stato pubblicato alcun registro relativo all'applicazione delle misure per singolo operatore. Alcune segnalazioni della comunità descrivono un’azione intrapresa nel 2018 contro un marketplace (SkinJar), ma tali segnalazioni non sono state verificate e non vengono prese in considerazione nel presente documento.\nCSGOFAST / IL PERCORSO DI AUTENTICAZIONE SALVATO\nSegui l'host di ritorno specificato.\n\nI link ai percorsi salvati csgofast.com a steam-login.authtofast.com. Il nome host separato è contenuto nella richiesta OpenID Steam. Fornisce agli investigatori un indirizzo concreto da confrontare con i registri di filtraggio e applicazione delle norme di Valve.\n\nEsamina il percorso di CSGOFast e la sua origine ↗ · Confronta i risultati salvati Steam Filtro link ↗\n\nDOCUMENTO PUBBLICO / WASHINGTON · 2016 → 2026\nDue scadenze. Un criterio di applicazione ancora indefinito.\n20 LUGLIO\nValve concede ai siti di gioco d'azzardo 10 giorni\n\nNella richiesta del proprio legale si avvertiva che il proseguimento dell'uso commerciale degli account Steam avrebbe potuto comportare la cessazione del contratto.\n\n27 SET\nWashington preme Valve\n\nLa Commissione statale per il gioco d’azzardo ha richiesto prove delle misure adottate per impedire i trasferimenti di skin a fini di gioco d’azzardo e ha fissato al 14 ottobre il termine per la risposta.\n\n17 OTTOBRE\nValve respinge l'accusa\n\nValve ha risposto dopo la scadenza, ha contestato l’accusa di aver facilitato il gioco d’azzardo, ha affermato di aver disattivato gli account associati e ha dichiarato di non voler disattivare il trading e OpenID per tutti. Almeno una piattaforma citata nei resoconti stampa relativi alle notifiche di luglio (CSGOFast) era ancora operativa un decennio dopo. Entrambi i fatti possono reggere solo se l’operatore ha sostituito gli account disabilitati; la documentazione che lo dimostrerebbe non è stata pubblicata. Il WSGC dovrebbe chiedere a Valve di chiarire la discrepanza tra i due dati.\n\n2026\nLe rotte osservate nel settembre 2026\n\nIl registro dei percorsi riporta 44 piattaforme che effettuano l’autenticazione tramite host di autenticazione di domini separati, tra cui CSGOFast, utilizzando i meccanismi OpenID e di scambio Valve descritti nel 2016. Il registro delle misure applicative che indicherebbe quali operatori siano stati disattivati non è stato prodotto.\n\nBRIEFING DELLA COMMISSIONE · 30 GENNAIO 2018\nDiciotto mesi dopo la risposta di Valve, l'autorità di regolamentazione continuava a definirla una semplice intenzione.\n\nNel corso dell’audizione pubblica sulla HB 2881, rivolgendosi al proprio organo legislativo, la Commissione ha descritto con parole proprie la dichiarazione del luglio 2016: Valve \"ha annunciato l'intenzione di intervenire con severità contro l'uso della propria piattaforma per facilitare il gioco d'azzardo con gli skin.\" Nella stessa pagina si riporta l'impatto che tale annuncio ha avuto sulle previsioni del settore — \"di conseguenza,\" le previsioni relative al mercato del gioco d'azzardo con puntate in pelle per il 2020 sono state riviste da $19.7 miliardi a $670 milioni, con un calo di circa il 97 per cento, solo sulla scia dell’annuncio. Le previsioni sono cambiate. Il dato relativo all’applicazione delle norme per operatore che ne giustificherebbe l’adozione non è ancora stato pubblicato.\n\nI dati di mercato sono stime di Narus Advisors / Eilers & Krejcik Gaming riportate nel documento informativo della Commissione, non risultati della Commissione stessa; lo stesso documento stima che nel 2016 le scommesse con \"skin\" ammontassero a circa $5 miliardi, di cui circa $3 miliardi su siti di tipo casinò. Recuperato 2026-09-22, SHA-256 c507c9025f93da0aadaf395c4d8882f25973211c318ee8e9b6f18a5b3755e050.\n\nÈ possibile mettere a confronto la posizione ufficiale espressa da Valve nel 2016 con l'infrastruttura attualmente osservabile. La domanda è se le misure di applicazione abbiano interessato gli account e i percorsi utilizzati dagli operatori vietati. Un preavviso di dieci giorni non costituisce prova del fatto che la comunicazione sia stata effettuata a tutti gli operatori ivi indicati. L'intervento di OPSkins del 2018 è l'unico caso documentato di azione intrapresa contro un operatore specifico; considerando che sono state controllate 189 piattaforme e che non sono stati pubblicati dati specifici per singolo operatore, un solo intervento documentato non è indicativo di una linea di condotta sistematica in materia di applicazione delle norme.\n\nAvviso del 2016 della Commissione per il gioco d'azzardo di Washington ↗ archiviato 2026-05-20 ↗ · Risposta di Valve del 17 ottobre 2016 (copia del documento) ↗ · Presentazione del WSGC all’Assemblea legislativa, 30 gennaio 2018 (copia locale, 4 pagine) ↗ · lo stesso file su wsgc.wa.gov ↗ · record di recupero e hash ↗ · L'azione di Valve su OPSkins nel 2018 ↗ archiviato 2026-03-07 ↗ · Verifica del percorso attuale ↗\n\nAudit forense longitudinale · Soggetti oggetto di diffida del 2016\nIl decennio del preavviso di 10 giorni: verifica forense sulla sopravvivenza dei 23 siti indicati\n\nIl 19 e 20 luglio 2016, Valve il responsabile dell’ufficio legale Karl Quackenbush ha emesso diffide formali nei confronti di 23 piattaforme di gioco d’azzardo “skin”, ordinando loro di cessare l’uso commerciale degli account Steam all’interno di 10 giorni sotto la minaccia della chiusura dell'account e di azioni legali. Più di 3,700 giorni dopo, una verifica empirica ha rivelato il vero andamento dell'applicazione delle norme: numerosi operatori non hanno mai cessato l'attività, altri hanno continuato a operare fino a sei anni dopo la scadenza, e l'ecosistema multimiliardario ha continuato a sfruttare l'architettura OpenID di Valve.\n\n5+ IN DIRETTA\nSicuramente operativi nel 2026 (CSGOBig, CSGO500, CSGOFast, ecc.)\n6 ANNI\nPeriodo più lungo di attività dopo la notifica prima della chiusura (CSGOatse attivo fino al 2022)\n$5.01B\nVolume delle scommesse \"skin\" nel 2016 (Narus / Eilers & Krejcik)\nOltre 200\nSiti di gioco d'azzardo online attivi che operano nel momento di massimo splendore del mercato\nI Titani sopravvissuti · Piano finanziario e di traffico 2024–2026\nDagli avvisi con 10 giorni di preavviso ai conglomerati offshore: un fatturato multimiliardario\n\nAnziché eliminare il \"skin gambling\", le comunicazioni del 2016 di Valve hanno dato il via a un’evoluzione del settore. Gli operatori sopravvissuti si sono riorganizzati come entità societarie offshore (Curaçao, Belize, Cipro), hanno aperto la strada al trading Peer-to-Peer (P2P) per aggirare i divieti relativi ai bot e ora gestiscono oltre 10 milioni di visite mensili al sito web e miliardi di dollari di volume di scommesse annuo pur continuando ad autenticarsi tramite Steam:\n\nPiattaforma / Dominio\tAvviso di luglio 2016\tEsito dell'applicazione della legge e stato di sopravvivenza\tVerifica registrata / Link principali\nCSGOBig\ncsgobig.com\tPreavviso di 10 giorni (luglio 2016)\tANCORA IN VITA NEL 2026\nTemporaneamente sospeso, poi riattivato; l'autenticazione avviene tramite letmeinbig.com e csgobiglogin.com\tX: @csgobig ↗ · FB: csgobigofficial ↗\nCSGO500\ncsgo500.com / 500.casino\tPreavviso di 10 giorni (luglio 2016)\tANCORA VIVI NEL 2026\nRibattezzato 500 Casino (licenza di Curaçao n. 8048/JAZ2014-037), con un fatturato mensile di svariati milioni\tPiattaforma live (500.casino) ↗\nCSGOFast\ncsgofast.com\tPreavviso di 10 giorni (luglio 2016)\tANCORA IN VITA NEL 2026\nRoulette, Crash e Jackpot attivi su steam-login.authtofast.com\tDossier di verifica dell'autenticità ↗\nCSGOLounge / Dota2Lounge\ncsgolounge.com / dota2lounge.com\tPreavviso di 10 giorni (luglio 2016)\tANCORA IN VITA NEL 2026\nSi è orientata verso le scommesse sulle monete degli eSport e le scommesse in criptovaluta; ha mantenuto un’attività operativa ininterrotta\tPiattaforma live ↗\nCSGOCasino\ncsgocasino.net / csgocasino.gg\tPreavviso di 10 giorni (luglio 2016)\tLIVE VIA SUCCESSOR (2026)\nIl dominio è stato reindirizzato; il portale successore attivo è raggiungibile all'indirizzo csgocasino.gg\tDominio successore ↗\nCSGOatse\ncsgoatse.com\tPreavviso di 10 giorni (luglio 2016)\tÈ RIMASTO IN ATTIVITÀ PER 6 ANNI (FINO AL 2022)\nLe attività di gioco d’azzardo sono proseguite a pieno regime per sei anni dopo l’ultimatum di 10 giorni lanciato da Valve\tX: @CSGOatsecom (Attivo fino al 2022) ↗\nCSGOSweep\ncsgosweep.com\tPreavviso di 10 giorni (luglio 2016)\tÈ RIMASTO IN VITA FINO A DICEMBRE 2017\nÈ rimasto in funzione al pubblico per 17 mesi dopo la scadenza\tX: Stato di CSGOSweep, dicembre 2017 ↗\nCSGOWild\ncsgowild.com\tPreavviso di 10 giorni (luglio 2016)\tÈ RIMASTO IN VITA FINO A DICEMBRE 2017\nPromuoto da importanti influencer; è rimasto attivo per un anno e mezzo dopo la diffida, prima della migrazione verso le criptovalute\tX: @Wild (Attivo da dicembre 2017) ↗\nCSGOPot\ncsgopot.com\tPreavviso di 10 giorni (luglio 2016)\tÈ RIMASTO IN VITA FINO A SETTEMBRE 2017\nHa gestito scommesse con jackpot di importo elevato per 14 mesi dopo la notifica\tX: @csgopot (Attivo da settembre 2017) ↗\nCSGODiamonds\ncsgodiamonds.com\tAvviso con preavviso di 10 giorni (luglio 2016)\tÈ RIMASTO IN ATTIVITÀ FINO ALLA METÀ DEL 2017\nHa continuato a operare per tutto il 2017 nonostante avesse ammesso di aver manipolato i risultati a favore degli streamer sponsorizzati\tX: @csgodiamondscom (2017) ↗\nCSGOLotto\ncsgolotto.com\tAvviso con preavviso di 10 giorni (luglio 2016)\tCHIUSO A LUGLIO 2016\nChiuso a seguito di uno scandalo pubblico; oggetto di un’ordinanza consensuale della FTC federale\tOrdinanza consensuale della FTC (Fascicolo C-4632) ↗\nCSGODouble\ncsgodouble.com\tPreavviso di 10 giorni (luglio 2016)\tCHIUSO A LUGLIO 2016\nChiusura volontaria immediatamente dopo la pubblicazione dell'avviso di cessazione e desistenza\tX: @CSGODouble (Chiuso a luglio 2016) ↗\nCSGOMassive\ncsgomassive.com\tPreavviso di 10 giorni (luglio 2016)\tCHIUSO 2016\nHa cessato l'attività al pubblico alla fine del 2016\tX: @csgo_massive ↗\nCSGOStrong\ncsgostrong.com\tPreavviso di 10 giorni (luglio 2016)\tCHIUSO NEL 2016\nHa cessato l'attività al pubblico nel 2016\tFB: csgostrongfree ↗\nSkins2\nskins2.com\tPreavviso di 10 giorni (luglio 2016)\tCHIUSO NEL 2016\nHa cessato l'attività al pubblico nel 2016\tFB: CSNCOM ↗\n\nPiattaforma\tTraffico mensile (visite)\tFatturato / Volume stimato\tEntità societaria e giurisdizione\tPrincipali misure normative e modello\nCSGOEmpire\ncsgoempire.com\t2,3 milioni — 9,0 milioni al mese\nDurata media: 6+ min; 80% diretto\t$1.5B — $2.5B Volume d'affari annuo\n>1,000,000 transazioni P2P di skin al mese; $6.4M di ordine liquido attivo\tMoonrail Limited B.V. (Curaçao n. 148182)\nPagamenti: JHOLT LTD (Cipro); Fondatore: \"Monarch\" (Ossi Ketola)\tPioniere nel commercio P2P di oggetti senza commissioni; autorizzato da Curaçao con licenza OGL/2024/1183/0869\nCSGORoll\ncsgoroll.com\t2,74 milioni — 3,5 milioni al mese\nDurata media: 9 minuti e 23 secondi; 16% percentuale di rimbalzo\t$1.0B — $2.0B Volume d'affari annuo\nFatturato aziendale annuo stimato compreso tra $100M e $200M derivante dal margine della casa\tFeral Holdings Limited\nCon sede a Belize City, Belize (n. di registrazione 171519)\tBandita dall'ACMA australiana (maggio 2023); ha sponsorizzato la squadra di primo livello G2 Esports, che schierava giocatori minorenni\n500 Casino (CSGO500)\n500.casino / csgo500.com\t220.000 — 425.000 al mese\ncirca 105.000 visitatori unici al mese\t$100k / settimana ($5.2M/anno) a Royales\nRequisiti di scommessa per i grandi scommettitori: $400 di scommessa per ogni $1 di rakeback\tPerfect Storm B.V. (Curaçao n. 150536)\nLicenza OGL/2024/1354/0882 rilasciata dalla Commissione di controllo del gioco d'azzardo di Curaçao\tSospesa dalla Spelinspektionen svedese (novembre 2023) per aver rivolto le proprie offerte ai giocatori svedesi senza licenza\nCSGOBig\ncsgobig.com\t~169,600 / mese\nDurata media: 19 minuti e 12 secondi; primarie statunitensi\tVolume annuo di diversi milioni\nScatole misteriose, roulette e battaglie per le casse\tFunziona tramite instradamento proxy ausiliario\nletmeinbig.com (registrato nel 2023) e csgobiglogin.com\tTarget di luglio 2016 C&D; rilanciato con architettura di autenticazione tramite proxy\nCSGOFast\ncsgofast.com\t~150.000 — 250.000 al mese\nPubblico globale multilingue\tVolume annuo di diversi milioni\nRoulette ad alta velocità e giochi \"crash\"\tEnti operativi offshore\nPercorsi Steam autenticazione tramite steam-login.authtofast.com\tObiettivo del C&D del luglio 2016; attività mai interrotte; ancora in attività nel 2026\nCSGOPolygon\ncsgopolygon.com / plg.bet\t~300.000 — 500.000 al mese\nIl predominio dei Paesi della CSI e dell’Europa orientale\tVolume annuo di diversi milioni\nCriptovalute e roulette skin, scommesse sugli incontri\tObiettivo della seconda fase (ottobre 2016)\nSi è orientato verso le criptovalute con il dominio speculare plg.bet\tÈ sopravvissuto per un intero decennio; continua a liquidare le attività tramite API di terze parti\nLa seconda ondata: perché la diffida di Valve ha preso di mira oltre 43 siti in totale\n\nIl 17 ottobre 2016, il consulente legale di Valve ha comunicato formalmente alla Commissione per il gioco d’azzardo dello Stato di Washington che, a seguito delle prime 23 notifiche del 19 luglio, Valve aveva inviato lettere di diffida a oltre 20 siti di gioco d'azzardo con skin aggiuntivi (portando il totale ufficiale a oltre 43). Questa seconda ondata si è resa necessaria perché l'elenco iniziale aveva inspiegabilmente tralasciato i centri di gioco d'azzardo più grandi e famigerati del mondo:\n\nCSGOJackpot.com: Il pioniere storico delle lotterie clandestine, che gestiva un volume d’affari di centinaia di milioni prima di chiudere i battenti a causa della minaccia di un’incriminazione federale.\nCSGOShuffle.com: Il sito al centro dello scandalo dello streaming del luglio 2016, in cui lo streamer di Twitch PhantomL0rd deteneva segretamente il 33% della società ed è stato smascherato mentre manipolava le quote utilizzando i fondi dell'azienda.\nL'ecosistema macro (oltre 200 operatori): Secondo una ricerca di settore condotta da Narus Advisors ed Eilers & Krejcik Gaming, nel 2016 erano attivi oltre 200 siti distinti di gioco d’azzardo con skin, che hanno generato $5.01 miliardi di volume di scommesse da 3,03 milioni di giocatori attivi. Le 43 lettere di Valve hanno riguardato meno di 20% del mercato attivo.\nIndagini ufficiali da parte del governo e delle autorità di regolamentazione sul gioco d’azzardo “Steam Skin”\n\nIl fenomeno del gioco d’azzardo con la pelle è documentato in numerose indagini ufficiali previste dalla legge, azioni di contrasto e documenti di posizione del governo:\n\n1. Commissione per il gioco d'azzardo dello Stato di Washington (WSGC) (2016–2018)\n\nIl 5 ottobre 2016 è stata emessa una richiesta formale di cessazione e astensione; il 30 gennaio 2018 è stato pubblicato un documento informativo legislativo in cui si attesta che gli “skin” sono equivalenti al contante e si riporta il volume delle scommesse con “skin” pari a $5.0B.\n\nRapporto legislativo del WSGC in formato PDF (copia locale) ↗\n2. Commissione federale per il commercio degli Stati Uniti (FTC) (settembre 2017, fascicolo C-4632)\n\nPrima azione di contrasto normativa a livello federale relativa al \"skin gambling\" nei confronti dei titolari di CSGOLotto, Trevor Martin e Thomas Cassell, per pratiche ingannevoli e controllo non dichiarato della piattaforma.\n\nDecisione e ordinanza consensuale della FTC ↗\n3. Documento di posizione della Commissione britannica per il gioco d’azzardo (UKGC) e verifiche relative ai minori\n\nLe skin dei videogiochi sono state formalmente classificate come \"denaro o equivalente\" ai sensi del Gambling Act 2005. Da successive indagini è emerso che oltre 11% dei bambini di età compresa tra gli 11 e i 16 anni aveva scommesso skin nei videogiochi.\n\nArchivio di ricerca dell’UKGC ↗\n4. Inchiesta del Senato australiano su ambiente e comunicazioni (2018)\n\nRelazione del Parlamento federale su \"Microtransazioni nei giochi per oggetti ottenibili in modo casuale\", valutando le meccaniche dei loot box di Valve, i prelievi in contanti sul mercato secondario e l'elusione delle norme.\n\nInchiesta del Parlamento australiano ↗\nLa domanda in sospeso\n\nPubblicare il resoconto delle misure applicate: quali account di gioco d’azzardo e bot sono stati disattivati, quali host di ritorno sono stati limitati e quali servizi commerciali hanno ottenuto l’autorizzazione. Un divieto pubblico e un avviso sulla homepage non dimostrano che l’attività in questione sia stata interrotta.\n\nParte B — Norme e dati relativi all'applicazione · Sezione 12\nIl nome host è già presente nella richiesta.\nContesto e limiti della fonte\n\nValve dispone già di un elenco di domini (il “Link Filter”) e riceve già il nome host di autenticazione in ogni richiesta OpenID. Il pseudocodice riportato di seguito illustra la struttura logica che consente di collegare i due elementi. Non vi sono prove pubbliche che dimostrino che Valve lo faccia.\n\nValve gestisce già una lista nera di domini. Valve riceve già l'host di accesso in ogni richiesta OpenID. Non c'è bisogno di costruire nulla: basta unire le due parti. Si tratta di una ricerca del nome host in un elenco che Valve gestisce autonomamente. Lo pseudocodice riportato di seguito è solo un esempio illustrativo, non l'implementazione di Valve.\n\nforensic_autoban.py\n# PSEUDOCODICE ILLUSTRATIVO — Valve.block_domain() e flag_session_as_mitm() non sono vere e proprie chiamate API. Questo esempio illustra la struttura logica di una misura di mitigazione Valve che potrebbe essere implementata contro i domini di autenticazione proxy, non il funzionamento interno effettivo di Valve.\n# Illustrazione: la struttura logica di una verifica sulla richiesta OpenID in arrivo\ndef audit_openid_request(richiesta):\nblocked_origins = database.get_blacklisted_platforms()\nproxy_domain = request.params.ottenere('openid.realm')\ntarget_redirect = request.params.ottenere('openid.return_to')\n\n# Logica: se il proxy reindirizza verso un sito bloccato, bloccare il proxy.\nper sito in origini_bloccate:\nse sito in target_redirect:\nValve.block_domain(proxy_domain)\nValve.contrassegna_sessione_come_MITM(request.session)\n# Risultato: la richiesta di accesso per quell'host è stata rifiutata\n\nOsservazione:\nSe un dominio principale è già presente nel filtro dei link (ad es. howl.gg, bloccato 2026-09-18/19/21) e il suo host di autenticazione (howl.uno) compare nella richiesta OpenID proveniente dal pulsante di accesso di quel sito, l'associazione è rilevabile da Valve dai propri dati di richiesta. La verifica è automatizzabile; la sua esecuzione, invece, non lo è.\nPrecedenti documentati e segnalati\n\nValve è intervenuto contro un operatore terzo almeno una volta, come risulta dai dati disponibili: nel 2018 ha revocato l'accesso di OPSkins al sistema ExpressTrade (L'annuncio di Valve ↗ archiviato 2026-03-07 ↗). Anche alcune segnalazioni della comunità risalenti al 2018 descrivono la perdita di accesso a una piattaforma (SkinJar); tali segnalazioni non sono state verificate e il meccanismo è dedotto dall'esito, non da una procedura resa pubblica.\n\nCosa stabilisce il precedente:\n\nValve può interrompere l’accesso di un operatore terzo quando lo ritiene opportuno. CSGOFast, citato nei resoconti stampa relativi alle notifiche del luglio 2016, operava su 2026-09-21 con un host di autenticazione registrato su 2026-06-30 che non restituiva alcun blocco da parte del Link Filter. Il motivo per cui un operatore è stato escluso e altri no non è spiegato da alcun criterio pubblicato.\n\nCosa indica e cosa non indica la data di registrazione\n\nLa data di registrazione di un host di autenticazione rappresenta il limite minimo relativo al momento in cui l'host potrebbe essere apparso per la prima volta in una richiesta OpenID; essa non implica un utilizzo continuativo. sc-auth.net, ad esempio, è stato registrato con il codice 2019-04-02 (RDAP) ed è stato rilevato nella procedura di accesso Steam di Skin.Club nel settembre 2026; ciò che è accaduto tra queste due date non risulta dai registri pubblici.\n\nAudit comparativo: standard di conformità API\nAspetto esecutivo\tRegole dell'API di GitHub\tSteam API web (Valve)\n1. Neutralità normativa\tSi applicano a tutti gli account regole pubblicate e uniformi, limiti di frequenza documentati (ad esempio, 5,000 chiamate/ora per gli utenti autenticati, 15,000/ora per le organizzazioni GitHub Enterprise Cloud) e politiche di utilizzo accettabile pubblicate.\tNon sono stati pubblicati criteri. Gli account individuali vengono chiusi in base alle clausole relative all’automazione e all’uso commerciale (reclami archiviati), mentre non è stato pubblicato alcun registro delle azioni intraprese per operatore per quanto riguarda le piattaforme commerciali.\n2. Abuso di OpenID / proxy di autenticazione\tLe politiche pubblicate da GitHub consentono la sospensione o la revoca delle app e dei token OAuth in caso di abuso, e la sua documentazione descrive la revoca automatica dei token esposti (sintesi della documentazione di GitHub a cura degli autori).\tGli host di autenticazione con dominio separato rilevati nei flussi OpenID Steam (ad esempio rbsnin.com, howl.uno, sc-auth.net) non hanno generato alcun blocco da parte del filtro dei link in 2026-09-21, mentre i loro domini principali sì.\n3. Monetizzazione degli abusi\tGitHub non applica commissioni sulle transazioni relative agli articoli trasferiti tramite sistemi di automazione di terze parti; il suo modello di business si basa sugli abbonamenti e sulle inserzioni nel marketplace.\tValve vende le chiavi delle casse che consentono di ottenere gli oggetti, mentre il Mercato della Comunità applica una commissione complessiva di circa 15% sulle vendite effettuate all’interno del Mercato. In questa sede non viene fornita alcuna stima delle entrate attribuibili a piattaforme di terze parti.\n4. Durata dei cicli di evasione\tGli ID client OAuth sospesi smettono di funzionare su tutta la piattaforma al momento della sospensione; la documentazione non riporta un tempo stimato per l'intervento e in questa sede non se ne ipotizza alcuno.\tGli host di autenticazione con domini separati e date di registrazione comprese tra il 2011 e settembre 2026 non hanno restituito alcun blocco da parte del filtro dei link nei controlli di 2026-09-19 e 2026-09-21. La data di registrazione rappresenta un limite minimo per il possibile utilizzo, non una prova di utilizzo continuativo.\nFonti: rubrica GitHub — Documentazione pubblicata da GitHub sui limiti di velocità delle API e sulle politiche della piattaforma (sintesi degli autori, non citata) · rubrica Steam — Controlli del filtro dei link di 2026-09-19 e 2026-09-21 (linkfilter-recheck-2026-09-21.json), registro RDAP (domain-registration.json) e i reclami relativi all'assistenza archiviati (archivio delle prove).\nParte B — Norme e dati relativi all'applicazione · Sezione 13\nIl divario di prezzo rispetto a 0\n\nL'oggetto si trova in un inventario Steam; la vendita avviene altrove. Un AWP Dragon Lore nuovo di fabbrica aveva 62 offerte attive su CSFloat; il prezzo più basso richiesto $10,623.95. Il mercato di Steam non può visualizzare un prezzo richiesto superiore a circa $1,800. Per vendere al prezzo più alto osservato, un proprietario ha bisogno di un acquirente o di una piattaforma di mercato esterni a Steam. L'oggetto e il suo trasferimento dipendono comunque da Steam.\n\nWhat this means — the Community Market listing ceiling\n\nSteam’s own market refuses a listing above roughly $1,800. A seller may ask less, never more. Items whose market price sits above that line therefore cannot be sold at that price on Steam at all — which is the mechanism that moves those sales to third-party venues while the item itself never leaves Valve’s inventory system.\n\nSection 13 — the off-Steam price gap →\n\nContesto e limiti della fonte\n\nIn questa sezione compaiono tre diversi conteggi, che non sono intercambiabili. 245 è il numero di categorie di nomi di articoli CS2 la cui offerta attiva più conveniente ha superato il valore $1,800 esclusivamente su CSFloat, il 20 settembre 2026. 241 è lo stesso insieme meno le quattro categorie fissate al limite massimo $100,000 di CSFloat, ovvero il pannello su cui viene calcolato il limite minimo $13.63M. 248 Si tratta di un quadro diverso: le categorie il cui prezzo superava il limite massimo in due o più delle cinque piattaforme di mercato il 23 settembre 2026. Le piattaforme si sovrappongono, pertanto i dati provenienti da sedi diverse non devono mai essere sommati. Ogni cifra qui riportata rappresenta un prezzo richiesto, non una vendita conclusa, e nessuna di esse costituisce ricavo, fatturato o profitto — né per Valve né per chiunque altro. I valori riportati da PriceEmpire sono stime arrotondate pubblicate da quel sito, e la sua carta Steam copre oggetti provenienti da altri Steam giochi, quindi gli ambiti di riferimento nel confronto non sono identici.\n\nUn articolo. Due sistemi di prezzi.SEGUI IL RECORD\nPassaggio 3 / 3\n\nA quel prezzo, il venditore ha bisogno di una piattaforma alternativa o di un acquirente. L'articolo dipende comunque dall'inventario e dal sistema di trasferimento di Steam.\n\nSTEAMInformazioni su $1,800Limite massimo pubblicato per gli annunci sul Mercato della Comunità\nCATALOGO SALVATO$10,623.95AWP Dragon Lore nuova di fabbrica, prezzo da concordare\nLA DIPENDENZAÈ ancora un articolo SteamL'inventario e il trasferimento rimangono a Steam\n01 / ARTICOLOValve inventario delle partiteOggetto di CS2 o Dota 2 contenuto in Steam\n02 / SOFFITTOInformazioni su $1,800 in SteamPrezzo massimo per un annuncio sul Market\n03 / RICHIESTA ESTERNA$10,623.95 per Dragon LoreL'offerta CSFloat più conveniente nella panoramica datata\n04 / CONSEGNASteam rimane nella catenaLa proprietà e il trasferimento degli oggetti dipendono dal sistema stesso\nARCHITETTURA DI MERCATO · PANORAMICA DEL 20 SETTEMBRE 2026\nIl divario di prezzo è quantificabile.\n\nAbbiamo conteggiato le categorie di articoli la cui offerta attiva più economica era rigorosamente superiore a $1,800. CSFloat e Skinport sono istantanee separate con inventari CS2 sovrapposti; i relativi conteggi non possono essere sommati. Le offerte esterne indicano dove sono pubblicati prezzi di vendita più elevati, mentre Steam continua a gestire la proprietà e il trasferimento degli articoli.\n\n245CATEGORIE CS2 · CSFLOAT\n166CATEGORIE CS2 · SKINPORT\n3DOTA2CATEGORIE · SKINPORT\n$10,623.95DRAGON LORE - DOMANDE SUL PIANO\n\nDragon Lore: 62 presenta offerte attive su CSFloat nella categoria \"Factory New\"; il prezzo minimo indicato è una richiesta, non una vendita confermata. Steam consente di mettere in vendita l’articolo a un prezzo inferiore, ma non permette di pubblicare una richiesta di prezzo superiore a quella osservata. La dichiarazione di Valve, disponibile all’indirizzo 2016, conferma che l’azienda è a conoscenza del fatto che alcuni operatori di gioco d’azzardo utilizzano OpenID e l’infrastruttura commerciale di Steam. L’eventuale violazione delle regole di Valve da parte di un determinato marketplace di terze parti deve essere accertata separatamente.\n\nControlla il registro completo →CSFloat JSON ↗Skinport JSON ↗La dichiarazione di Valve su “2016” ↗\nAPI CSFLOAT DIRETTA / ISTANTANEA DATATA$13.63M\n\nValore richiesto complessivo minimo in 241 categorie di articoli e 3,395 offerte attive. Calcolato come il prezzo di vendita più basso di ciascuna categoria moltiplicato per il numero delle offerte corrispondenti. Le quattro categorie fissate al limite massimo di CSFloat ($100,000) sono escluse da questo panel prudenziale.\n\nCosa indica la cifra in dollari\n\nQueste offerte rappresentano almeno $13,631,888.25 nei prezzi di vendita pubblicati per questo sottoinsieme limitato di CSFloat. Includendo le quattro categorie con prezzo massimo si ottiene $14,231,888.25. Questo è un limite massimo per le richieste attive, non le vendite concluse, il fatturato, l’utile o l’intero mercato CS2.\n\nRicalcola a partire dall'istantanea CSFloat di 245 righe ↗\nPRICEEMPIRE / VALORE DI CATALOGOSteam: n. 15 su 39\nMolti locali indicano un valore in dollari superiore a Steam.\nUUSkins\n$133.8M\nYouPin898\n$127.5M\nBuff.163\n$104M\nMoon.Market\n$100.3M\nWhite.Market\n$89.6M\nBuff.Market\n$86.7M\nSteam\n$31M\n\nI sei valori più grandi visualizzati e Steam. PriceEmpire arrotonda queste cifre; Steam mostra $31M. Quattordici locali presenti nell'elenco lo precedono in base ai valori in dollari indicati.\n\nPRICEEMPIRE / NUMERO DI OFFERTESteam: n. 1 su 39\nSteam è ancora in testa per numero di offerte.\nSteam\n32,2 milioni\nYouPin898\n5,9 milioni\nC5Game\n4,6 milioni\nHaloSkins\n4,4 milioni\nSkinport\n3,8 milioni\n\nSteam mostra 32,2 milioni offerte. Il numero di offerte e il valore totale richiesto rispondono a domande diverse; molti annunci a basso prezzo possono incidere in modo determinante sul conteggio.\n\nFonte: Confronto pubblico di PriceEmpire ↗ archiviato 2026-09-21 ↗, registrato alle 2026-09-20 19:03 UTC; estrazione datata a 39 righe ↗. I dati riportati sono stime approssimative e le scorte possono sovrapporsi tra le diverse sedi. La scheda di Steam descrive anche oggetti provenienti da altri giochi Steam, pertanto gli ambiti di riferimento non sono identici. I valori indicati si riferiscono ai prezzi di vendita richiesti, non alle vendite o ai ricavi.\n42\nUN'ALTRA FONTE / STEAMANALYST\nL'ecosistema commerciale è sotto gli occhi di tutti.\n\nElenco dei marketplace di SteamAnalyst archiviato 2026-07-19 ↗ elenca 42 piattaforme di vendita CS2 di terze parti insieme a Steam, con dati recenti sui prezzi per 32 delle 43 voci. PriceEmpire elenca 39 piattaforme in base ai propri criteri di inclusione. Aziende citate, offerte pubbliche, prezzi visibili: questa economia è trasparente.\n\nIL LIMITE È IL MECCANISMO: LA VENDITA PERDE SLANCIO, L’ARTICOLO NO.\n\nIn cinque mercati diversi, immortalati in un’unica istantanea autorizzata, 248 categorie di articoli CS2 hanno un prezzo fissato in modo indipendente superiore al limite massimo di inserzione di Steam, pari a circa $1,800, per almeno due di esse — e ognuna di esse è assente da Steam. La stessa istantanea ha suddiviso l’intero catalogo in fasce di prezzo: il mercato di Valve offre 95.3% delle categorie di articoli al di sotto del proprio limite massimo e 1.9% di quelle al di sopra. Il crollo non riflette un calo della domanda, ma corrisponde esattamente alla regola pubblicata. La vendita a tali prezzi richiede un acquirente esterno o un marketplace, mentre Steam continua a controllare le scorte e il trasferimento: l’attività esce dalla cassa di Valve e la consegna rimane sull’infrastruttura di Valve.\n\nSteam Domande frequenti sul mercato ↗archiviato 2026-09-21 ↗Steam Contratto di abbonamento ↗archiviato 2026-09-21 ↗Set di dati dell'atlante dei cinque mercati ↗Manifesto di provenienza ↗Istantanea precedente di CSFloat ↗Panoramica su Skinport ↗PriceEmpire ↗archiviato 2026-09-21 ↗SteamAnalyst ↗archiviato 2026-07-19 ↗Registro del divario di prezzo ↗Atlante della scala dei prezzi ↗\n\nParte C — Quadri giuridici\nParte C — Quadri giuridici · Sezione 14 · Accesso del personale\nChi può ripristinare le misure di sicurezza?\nContesto e limiti della fonte\n\nLa sicurezza dell'account dipende anche dalle persone che possono ripristinare un account, accedere ai dati privati o reimpostarne le misure di sicurezza. L'indagine deve monitorare tali azioni privilegiate con la stessa attenzione con cui monitora gli abusi delle API.\n\nIl recupero dell'account conferisce a un operatore dell'assistenza il potere di sottrarre l'account al suo titolare. Valve ha confermato per iscritto, in due occasioni — nel febbraio 2023 e nel novembre 2025 — che tale potere è stato utilizzato per affidare i conti alle persone sbagliate. A distanza di trentatré mesi, attraverso lo stesso canale. Di seguito: il valore di tale accesso, sei casi documentati e il registro Valve, che contiene informazioni su ciascuno di essi e che non è stato fornito a nessuno.\n\nTestimonianza conservata / 9 maggio 2025\nUn ticket di recupero che ha disabilitato la sicurezza dell'account e una perdita segnalata pari a $10,000\n\nUn utente presente nell’archivio delle richieste di assistenza riporta che Steam il servizio di assistenza ha reimpostato la password e disattivato la protezione dell’account dopo che un’altra persona aveva inviato una richiesta di recupero. L'autore afferma che l'account era inattivo da anni, conteneva elementi risalenti al 2016–2017 e presentava Steam Guard, un numero di telefono associato e codici di recupero memorizzati.\n\n\"Steam Il servizio di assistenza ha comunque concesso a qualcun altro l'accesso al mio account.\"\n\nAccusa in prima persona, riportata in steam_support_tickets_MEGA.json, record 110. Leggi il post completo salvato ↗\n\nNon si tratta di sfortuna di un singolo utente. La stessa procedura — una richiesta di assistenza che assegna l’account a chiunque fornisca i dati più vecchi — è la modalità documentata per tutti i casi riportati nel registro qui sotto, e Valve lo ha ribadito per iscritto ben due volte.\n\nIl proprietario non può avere la meglio in questa discussione. Il processo di recupero richiede il primo codice CD, la prima e-mail, la prima carta di credito, il primo numero di telefono. Questi dati si trovano nel database di Valve e vengono letti dall’accesso del team di assistenza — che, secondo quanto riferito, risale a quindici anni fa. Una persona in possesso di una copia del tuo file potrà sempre ricostruire una cronologia più completa della tua rispetto a quanto tu stesso potresti fare. Gli obiettivi sono stati scelti in base a determinati criteri: inattivi da anni, di alto valore e spesso acquistati di seconda mano, in modo che il possessore non conoscesse mai la chiave originale. Successivamente gli account sono stati cancellati definitivamente, interrompendo la traccia della cronologia degli oggetti che la comunità utilizza per rintracciare una skin — una cancellazione che un utente comune non può eseguire senza il periodo di attesa standard.\n\nPrivilegio minimo / OWASP A01\n\nI privilegi di ripristino devono essere limitati all'attività specifica, sottoposti a revisione indipendente e registrati. Verificare chi è autorizzato a reimpostare le credenziali, rimuovere Steam Guard, leggere i registri di fatturazione o esportare i dati dell'account. Linee guida OWASP sul controllo degli accessi ↗ archiviato 2026-09-20 ↗\n\nAmpio accesso all'assistenzaRischio relativo all'ambito di accesso\nOltre l'inventario.\n\nSe l'accesso con autorizzazioni estese viene utilizzato in modo improprio, la telemetria privata può diventare uno strumento per la profilazione, il phishing mirato e la sorveglianza. Tra le potenziali vittime figurano utenti comuni, personale militare, personaggi pubblici e le loro famiglie. Si tratta di un modello di minaccia; per determinare le autorizzazioni esatte sono necessari i registri di controllo degli accessi.\n\n01 Cronologia e posizione IP\nI registri IP possono rivelare la cronologia di navigazione in rete e la posizione approssimativa. Di per sé, tuttavia, non consentono di determinare con precisione gli spostamenti fisici.\n02 Identificazione dei dispositivi tramite impronta digitale\nGli identificatori dei dispositivi, laddove raccolti e accessibili, consentono di collegare sessioni e account.\n03 Telemetria delle attività\nI timestamp di accesso e i registri delle sessioni possono rivelare le abitudini di un utente, comprese le attività non visibili su un profilo pubblico.\n04 Comunicazioni e contatti\nL'accesso ai messaggi conservati o alle informazioni di contatto amplierebbe le possibilità di profilazione e di ingegneria sociale.\n05 Svelamento dell'identità\nI dati originali relativi a e-mail, numero di telefono e pagamenti possono consentire di collegare un account pseudonimo a una persona.\n06 Rivendita dei dati e responsabilità\nGli elenchi di destinatari esportati potrebbero favorire truffe mirate. È necessario identificare l’autore, il luogo di accesso, i destinatari e i trasferimenti; la sola ubicazione non costituisce né prova di accesso né immunità giuridica.\n\nValve descrive la registrazione degli indirizzi IP, le informazioni sui dispositivi, i dati relativi ai pagamenti e i fornitori di assistenza di terze parti nella sua Informativa sulla privacy, articoli 3 e 5.2 archiviato 2026-09-21 ↗. La politica autorizza l'accesso di soggetti terzi a fini di assistenza; tuttavia, non è stata resa nota la traccia di controllo che indicherebbe quale appaltatore abbia avuto accesso a quale categoria, quando e in base a quale autorizzazione.\n\nSezione 14.1 · il registro · giugno 2022 → novembre 2025 · ogni dato è corredato di fonte\nValve aprì la porta due volte, a distanza di trentatré mesi l’una dall’altra. Non si chiuse mai.\n\nSono stati segnalati sei casi in cui gli account sono stati sottratti tramite il canale di richiesta di assistenza di Steam stesso o tramite le credenziali protette da tale canale. Ogni importo corrisponde alla cifra pubblicata dalla fonte citata, e ogni fonte è indicata per nome. Due dei sei casi sono stati risolti con il risarcimento integrale. La differenza tra questi e gli altri casi non risiedeva in ciò che era accaduto, ma in chi stava osservando.\n\nValve, per iscritto — febbraio 2023\"Gli oggetti in questione sono stati rimossi dal tuo account poiché provenivano da un account che era stato compromesso a seguito di una richiesta di assistenza, per la quale il team di CS:GO si assume la responsabilità. Abbiamo annullato gli scambi e li abbiamo rimossi da tutti gli account che li avevano ricevuti.\"Steam Risposta di assistenza a un destinatario degli articoli di HFB, riprodotta da Dexerto, 21 febbraio 2023 ↗ archiviato 2025-08-18 ↗\nValve, di nuovo per iscritto — novembre 2025 · 33 mesi dopo\"Un tecnico dell'assistenza che ha gestito la richiesta di aiuto non ha seguito la nostra procedura, con la conseguenza che il tuo account è stato ripristinato a nome di qualcun altro. Mi scuso per questo errore.\"Steam Risposta di Support a Hawkeye337, citata in Dexerto, 14 novembre 2025 ↗\n21 giugno 2022\nHFB — il più vasto inventario del gioco$2,000,000+ · portato a $3,000,000+ nel follow-up di febbraio 2023\n\nSette oggetti da collezione “AWP Dragon Lores” e il karambit “Blue Gem” n. 1, il cui valore, da solo, ammonta a circa $1.26 milioni. L'account era rimasto inattivo per tre anni, ma l'autenticatore mobile era ancora attivo; l'indirizzo e-mail e la password sono stati comunque modificati, tramite la procedura di recupero dell'assistenza.\n\nI soldi sono finiti prima degli oggetti. Secondo quanto riportato $200,000+ Una parte dei proventi della vendita era già stata prelevata tramite market.csgo.com, una piattaforma di scambio che effettua i pagamenti in contanti e in criptovalute. L'annullamento di una transazione comporta la restituzione della skin, ma non quella del denaro che è già stato incassato.\n\nE la correzione non ha funzionato. Un acquirente ha spostato il proprio \"Souvenir Dragon Lore\" in un magazzino all'interno del gioco. Lo script di rollback di Valve non riusciva a vedere all'interno del proprio contenitore, quindi ha fornito al proprietario una nuova copia e ha lasciato quella nascosta al suo posto — Valve ha duplicato un $130,000 L'oggetto è stato individuato mentre si cercava di annullare un furto. È stato individuato grazie alla corrispondenza degli ID degli oggetti e alle segnalazioni della comunità, ed è stato eliminato un mese dopo, nel luglio 2022. L'acquirente è stato rimborsato da BUFF, non da Valve. Un intervento correttivo d'emergenza così precario non è un controllo; è ciò che una piattaforma fa quando non ha alcun controllo.\n\nDexerto, 21 giugno 2022 ↗ archiviato 2022-07-02 ↗ · Kaspersky ↗ · importo del prelievo per Esportfire, 22 giugno 2022 ↗ archiviato 2026-05-15 ↗, attribuito in quella sede a diverse fonti di Twitter · duplicazione e cancellazione secondo Esportsbetting, 14 luglio 2022 ↗\n\nRestauratoLe transazioni sono state annullate. Gli articoli sono stati ritirati dalle scorte di chi li aveva acquistati a prezzo pieno.\n14 agosto 2022\nCS.Money — i bot della piattaforma stessa$6,300,000 · 19,000+ skin · prima stima $1.6M\n\nGli hacker hanno sottratto i file dell'autenticatore mobile dei bot di trading del marketplace e li hanno svuotati, per poi inviare parte del bottino a trader noti per confondere le tracce. I ricercatori della comunità hanno mappato 55 account di hacker nel giro di poche ore e li ha pubblicati.\n\nValve non ha modificato nulla. La motivazione addotta è che un sito di terze parti si trova al di fuori di Steam — lo stesso Steam sul cui inventario, API di scambio e sistema di account si è svolto il furto dall’inizio alla fine.\n\nEsportfire, 14 agosto 2022 ↗ archiviato 2025-11-15 ↗\n\nRifiutatoNessuna revoca. La perdita è rimasta a carico della piattaforma e dei suoi utenti.\nSegnalato\n21 febbraio 2023\nQkss — stessa porta, stesso attore$1,000,000+\n\nÈ stato segnalato che è stato risolto allo stesso modo di HFB, dallo stesso operatore, tramite la stessa richiesta di assistenza. Il caso HFB era stato risolto completamente otto mesi prima. Quello di Qkss no.\n\nUn percorso. Due risposte. Nessun elemento presente nel verbale pubblicato distingue i due casi, se non il numero dei presenti.\n\nDexerto, 21 febbraio 2023 ↗ archiviato 2025-08-18 ↗\n\nRifiutatoNon restaurato.\nSegnalato\nfebbraio 2023\nL'insider trading in sé — un anno di insider trading≈ $320,000 · si protrae per circa un anno, non si tratta di una valutazione delle scorte\n\nL'accesso dall'area di supporto ha consentito di visualizzare la cronologia dell'account fino al 15 anni — il primo codice CD, la prima e-mail, la prima tessera. Sono proprio queste le prove richieste dalla procedura di recupero, ed è per questo che chi detiene il database ha sempre la meglio nella disputa con chi detiene l’account.\n\nIl blogger Mzkshow ha rivelato come l'operatore interno \"Steam Help\" e il suo collaboratore \"Alexander\" abbiano preso di mira account inattivi contenenti oltre $100k in skin. Un M4A4 Howl rubato, con gli ologrammi iBUYPOWER e Titan Katowice 2014, è stato venduto per $35,000 e alla fine si è ritrovato con Valerii \"b1t\" Vakhovskyi della NAVI, che non aveva modo di saperlo. Dopo l’intervento di Valve, l’appaltatore ha licenziato l’intero Steam team di assistenza.\n\nVKPlay ↗ · Lis-Skins ↗ · Escorenews (RU) ↗ · Dexerto (EN) ↗\n\nNessun registroValve non ha mai reso noto il numero di account coinvolti, né ha informato le persone interessate.\nSegnalato\n2 dicembre 2024\n\"Matvey\" — dopo i licenziamenti$13,000\n\nIl recupero è stato concesso a una persona che ha fornito dati relativi all’account che lo stesso titolare non era in grado di confermare. Due anni dopo che l’appaltatore aveva smantellato il proprio servizio di assistenza Steam, seguendo la stessa procedura si è ottenuto lo stesso risultato.\n\nPost archiviato, 2 dicembre 2024 ↗ archiviato 2025-08-05 ↗ · righe sorgente e hash ↓\n\nRifiutatoNon restaurato.\n13 novembre 2025\nHawkeye337 (Mark Spurlock) — e la seconda confessione≈ $300,000–$500,000 · Collezione completa di ologrammi di Katowice 2014\n\nL'aggressore ha chiesto 1 bitcoin e ha iniziato a trasferire la raccolta su Negev per distruggerla. Steam La risposta scritta dell’assistenza costituisce la seconda ammissione sopra riportata: un tecnico ha gestito la richiesta di assistenza, non ha seguito la procedura e ha affidato l’account a qualcun altro.\n\nA determinare la correzione è stato il feed. Poche ore dopo la pubblicazione su X dei post che taggavano Valve, l'account è stato ripristinato e tutti gli sticker sono stati riportati al loro posto. Qkss non aveva quel pubblico.\n\nSkin.club ↗ · Dexerto ↗ · Esportfire ↗ archiviato 2025-12-17 ↗\n\nRestauratoLa notizia è stata smentita poche ore dopo essere diventata virale.\nCiò che il registro rivela e che nessun singolo caso è in grado di fare.\n\nIl percorso non è mai stato chiuso. Il primo ricovero risale al febbraio 2023 e il secondo al novembre 2025 — a distanza di trentatré mesi, con il licenziamento di massa da parte dell’appaltatore, un caso documentato di recidiva e una violazione della piattaforma del valore di $6.3 milioni nel frattempo. A partire dal primo furto riportato in questo registro, il canale è rimasto aperto per tre anni e cinque mesi. A prescindere da ciò che fosse stato risolto nel 2023, la richiesta di assistenza ha comunque fatto sì che, nel novembre 2025, un account venisse assegnato alla persona sbagliata — come afferma lo stesso Valve.\n\nLa restituzione si basava sull’attenzione, non sul danno. Accettato: l'inventario più vasto del gioco e il collezionista il cui thread è diventato virale. Rifiutato: $1,000,000, $6,300,000, $13,000. Valve non ha mai pubblicato la regola che applica, perché una regola pubblicata dovrebbe spiegare quelle tre.\n\nA nessuno è stato detto nulla. Né gli utenti i cui dati storici degli account sono stati estratti dal database, né un’autorità di vigilanza, né il mercato che ha acquistato gli articoli in buona fede e li ha visti recuperati. Non c’è alcuna notifica di violazione, nessuna segnalazione di incidente, nessun conteggio degli account interessati — e i proventi rimasti sotto forma di denaro, attraverso piattaforme che pagano in contanti e in criptovalute. Non è possibile effettuare una revoca dell'operazione una volta che il denaro è uscito da Steam.\n\nValve contiene la cronologia dei controlli di supporto, il registro dei ticket di ripristino e la registrazione delle transazioni relative a ciascuna riga sopra indicata. Nessuno di questi documenti è stato prodotto. Richiedi la tua copia →\n\nLa questione dell’NDA\nLa riservatezza deve andare di pari passo con la responsabilità tecnica.\n\nConfronta gli accordi di riservatezza con le autorizzazioni effettive, i controlli sulle esportazioni, le approvazioni di ripristino e i registri di accesso. Una risposta predefinita non può risolvere l'accusa secondo cui lo stesso processo di recupero sia stato oggetto di abuso.\n\nArticoli 28, 32–34 del GDPR\n\nL'art. 33 concede al titolare del trattamento 72 ore di tempo per notificare all'autorità di controllo una violazione dei dati personali; l'art. 34 impone di informare le persone interessate qualora il rischio a loro carico sia elevato. Valve ha confermato per iscritto, in due occasioni, che il proprio canale di assistenza ha consegnato gli account alle persone sbagliate — compresa la cronologia degli account, i dati di fatturazione e tutto il resto. Non è stata pubblicata alcuna notifica ai sensi di nessuno dei due articoli e nessun utente interessato ha segnalato di averne ricevuta una. Leggi il regolamento ↗ archiviato 2026-09-20 ↗\n\nIncludi l'accesso all'assistenza nella tua richiesta →\nParte C — Quadri giuridici · Sezione 15 · Scala commerciale\nSegui i flussi di denaro. Distingui le transazioni.\nContesto e limiti della fonte\n\nLa questione dell’uso commerciale assume maggiore rilevanza quando i flussi di denaro vengono separati. I trasferimenti di beni a terzi, le vendite primarie di Valve e i prelievi di contanti dall’esterno sono operazioni distinte.\n\nL'articolo appartiene a Valve. Le scorte ammontano a Valve. Il trasferimento avviene sui server di Valve. Solo il pagamento avviene altrove — ovvero la fase che determina se un soggetto sia o meno un operatore di trasferimento di denaro, e l’unica fase in cui Valve non opera.\n\nIl meccanismo di generazione dei ricavi\nDove il denaro circola effettivamente.\nTre percorsi / un'economia basata su un unico bene\n01 / AccountInventario utenti\n\nArticoli disponibili: Steam\n\n02 / TrasferimentoCommercio P2P\n\nUtente ↔ bot oppure utente ↔ utente\n\n03 / LiquidazionePiattaforma esterna\n\nSaldo del sito o pagamento Steam\n\nCircolazioneIl motore economico va oltre il semplice costo del trasferimento\n\nSteam fornisce l’infrastruttura di inventario e trasferimento utilizzata dai mercati esterni. L’argomentazione economica alla base dell’indagine è che la liquidità derivante dalla rivendita e la domanda ricorrente sostengono la spesa per custodie, chiavi e articoli di ricambio, con commissioni sulle successive vendite sul Mercato della Comunità. Un trasferimento diretto P2P non comporta alcuna commissione da parte del Mercato della Comunità; tale dato contabile non risolve la questione del beneficio più ampio. Valve mantiene il controllo sull’accesso agli account e sulle restrizioni di trading in ogni fase.\n\n01 / Domanda secondariaLiquidità e valore di rivendita\n\nDomanda esterna legata al commercio e al gioco d’azzardo\n\n02 / Spesa primariaChiavi, custodie e capsule\n\nAcquisti a partire da Valve, ove disponibili\n\n03 / RicaviRicavi da vendita primaria\n\nPiù le commissioni sulle vendite effettive sul mercato\n\n5% + 10%Steam + commissione CS2 sulle vendite nel Community Market\n\nConclusione economica dello studio: i mercati di rivendita liquidi possono incoraggiare la spesa per articoli nuovi. Il noto 15% combina i tassi delle commissioni di mercato, soggetti a importi minimi e arrotondamenti; non si tratta di un prelievo applicato a ogni transazione esterna.\n\nTabella delle tariffe del Community Market di Valve ↗ archiviato 2026-09-21 ↗. Il 25 febbraio 2026 Il Procuratore Generale di New York ha intentato un’azione legale archiviato 2026-09-01 ↗ sostenendo che i loot box a pagamento siano collegati alla rivendita in contanti all’esterno e ai danni causati dal gioco d’azzardo — lo stesso nesso che questo dossier documenta dal punto di vista dell’infrastruttura tecnica. Tale denuncia è un’accusa, non un accertamento; viene citata qui perché un’agenzia statale incaricata dell’applicazione della legge ha posto una domanda affine a quella sollevata dal presente dossier: dove sono i dati relativi all’applicazione della legge che corrispondono alle dichiarazioni pubbliche?\n\n01 / IntroduzioneDeposito in criptovaluta\n\nRegistrazioni relative a servizi esterni e portafogli\n\n02 / ConversioneEquilibrio → skin\n\nArticoli consegnati tramite Steam transazioni\n\n03 / UscitaVendita esterna di valuta fiat\n\nVenditore, acquirente e fornitore del servizio di pagamento\n\nKYC?Identificare il controllo ad ogni passaggio di consegne\n\nQuesta è la strada da seguire, non un servizio di conversione in contanti basato sull'API nativa Steam. Documentare i controlli di identità, la custodia, gli ID delle transazioni e i destinatari dei pagamenti presso ciascun operatore esterno prima di autorizzare un prelievo in contanti senza KYC.\n\nStati Uniti / Legge sul segreto bancario\nClassificare prima l'attività, poi l'obbligo.\n\nIl FinCEN valuta le operazioni di trasferimento di denaro in base all’attività svolta dall’impresa. L'accettazione e il trasferimento di valuta virtuale convertibile possono far scattare gli obblighi relativi ai servizi di trasferimento di denaro, fatte salve le definizioni e le eccezioni applicabili. Il portafoglio Steam di Valve accetta fondi e li converte in oggetti di gioco; tali oggetti vengono poi liquidati tramite operatori terzi in cambio di valuta reale. L’oggetto e il suo trasferimento avvengono sull’infrastruttura di Valve; il prelievo di contante no, e se una qualsiasi parte di tale ciclo soddisfi le definizioni di trasferimento di denaro è una questione di classificazione che spetta al FinCEN, non una conclusione tratta in questa sede.\n\nFinCEN FIN-2019-G001, §§ 1–2, 5.1 ↗ archiviato 2025-07-11 ↗\n\nUnione Europea / riciclaggio di denaro\nTracciabilità dei proventi, delle informazioni e dell'assistenza.\n\nLa direttiva (UE) 2018/1673 riguarda il riciclaggio intenzionale e la partecipazione a attività che coinvolgono proventi di reato. La questione oggetto dell’indagine è cosa sapesse Valve riguardo agli operatori che utilizzavano la sua infrastruttura di trading e OpenID dopo il 13 luglio 2016, quando ne descrisse pubblicamente tale utilizzo, e quali misure abbia adottato al riguardo. Valve non ha pubblicato alcun registro delle misure di applicazione per singolo operatore; sarebbe tale registro, e non il presente dossier, a rispondere alla domanda.\n\nQuadro normativo dell'UE in materia di diritto penale ↗\n\nTerminologia della sesta direttiva antiriciclaggio (AMLD6): La direttiva in materia di diritto penale sopra citata è distinta dalla direttiva (UE) 2024/1640, nota anche come AMLD6. Per quest’ultima, il termine generale di recepimento è fissato al 10 luglio 2027, con alcune eccezioni specificate. Articolo 78 ↗ archiviato 2026-08-30 ↗\n\nParte C — Quadri giuridici · Sezione 16 · Notifica, risposta, responsabilità\nLa legge sui servizi digitali: mettere nero su bianco le conoscenze\nContesto e limiti della fonte\n\nDue elementi della notifica ai sensi dell’articolo 16 riguardano il mittente piuttosto che il presente fascicolo: i dati identificativi del mittente stesso e una dichiarazione in buona fede circa l’accuratezza delle informazioni. Tutto il resto richiesto dall’articolo — la spiegazione motivata e l’esatta ubicazione elettronica — è indicato nella Sezione 3 e nel registro dei percorsi, con le risposte salvate e gli hash, in modo che qualsiasi parte possa presentarla. Due ulteriori limiti alla legge stessa: la perdita dell’esenzione per l’hosting non comporta di per sé alcuna responsabilità ai sensi di altre leggi, e il valore 6% di cui all’articolo 52, paragrafo 3, rappresenta un limite massimo previsto dalla legge, non una sanzione commisurata a Valve.\n\nAi sensi del DSA, un fornitore di servizi di hosting mantiene la propria esenzione da responsabilità solo fino al momento in cui non ne viene specificamente a conoscenza e omette di agire. Il presente dossier costituisce tale avviso. Indica i server, le date, le risposte salvate e gli hash. A partire dalla pubblicazione, la domanda non è più se Valve ne fosse a conoscenza, bensì cosa abbia fatto Valve in seguito.\n\n01Luglio 2016 / la mostra \"The Dossier\"\nUna richiesta di dieci giorni.\n\nLa comunicazione sopra riportata costituisce il punto di partenza storico per il confronto in materia di applicazione delle misure oggetto dell’indagine.\n\n0217 febbraio 2024 / domanda generica\nLa finestra temporale DSA.\n\nDistinguere la condotta storica da quella assunta nel periodo in cui si applicano gli obblighi previsti dalla DSA.\n\n03Dieci anni / istantanea del fascicolo originale\nLa durata richiede una traccia delle notifiche.\n\nIl tempo trascorso dal luglio 2016 (cfr. Sezione 11) è un indicatore del fascicolo. Non si tratta di dieci anni di violazioni accertate della DSA. Collegare ogni comunicazione a un elemento specifico, alla normativa applicabile, alla prova di consegna e alla risposta.\n\nArticolo 52, paragrafo 3 / limite massimo previsto dalla legge6%\ndel fatturato annuo a livello mondiale\n\nMulta massima per la violazione degli obblighi previsti dal DSA, calcolata sulla base dell'esercizio finanziario precedente del fornitore. Si tratta di un limite massimo previsto dalla legge, non di una sanzione effettiva inflitta a Valve.\n\nArticoli 6, 8 e 16 / il criterio giuridico\n\nPer quanto riguarda i servizi di hosting in questione, la conoscenza specifica dei contenuti e la mancata adozione di misure tempestive possono comportare la perdita dell’esenzione prevista per i servizi di hosting. Una segnalazione sufficientemente precisa può dimostrare la conoscenza di un determinato contenuto. Il DSA non impone alcun obbligo generale di monitoraggio; la perdita dell’esenzione non comporta di per sé una responsabilità ai sensi di un’altra legge.\n\nDSA: articoli 6, 8, 16, 52, 53, 93 e considerando 17 ↗ archiviato 2026-09-20 ↗\n\nEsamina i reclami archiviati ↗Crea la cronologia dell'account →Analisi giuridica ed economica completa →\nParte C — Quadri giuridici · Sezione 17 · Identità, età, accesso commerciale\nMinori: un accesso con Steam non costituisce una verifica dell'età\nContesto e limiti della fonte\n\nIn questo dossier non compaiono dati relativi a minori e non ne sono stati raccolti: gli autori non si sono registrati, non hanno caricato contenuti né effettuato l’accesso a nessuna delle piattaforme citate. Chiunque si basi su questa sezione dovrebbe mantenere riservate le prove che coinvolgono un minore e oscurare i dettagli identificativi dagli atti pubblici. Il COPPA viene citato in questa sede come legge sulla privacy dei minori con condizioni di applicazione specifiche — pubblico di riferimento, conoscenza effettiva, dati personali raccolti — e non come norma generale relativa all’età minima per il gioco d’azzardo; la denuncia presentata a New York nel 2026 costituisce un’accusa da parte di un’autorità statale, non un accertamento.\n\n\"Accedi con Steam\" dimostra che esiste un account. Questo non dimostra nulla riguardo all'età — e su questi siti è l’unico ostacolo tra un bambino e un versamento. Leggilo con Sezione 3.1: all'interno del client Steam l'avviso che un browser mostrerebbe non viene mai visualizzato, quindi il bambino non lo vede mai.\n\nCosa offre Steam OpenIDIdentità dell'account\n\nUno SteamID verificato utilizzato per effettuare l'accesso o collegare un account.\n\n≠\nCosa deve stabilire l'operatoreRequisiti di partecipazione\n\nEtà, giurisdizione ed eventuali verifiche d'identità richieste.\n\nBasi tecniche: Documentazione su Steamworks OpenID ↗ archiviato 2026-09-21 ↗. L’attestazione documentata dell’identità non costituisce una certificazione che l’utente possa giocare d’azzardo legalmente.\n\nCOPPA / minori di 13 anni\nIdentificare l'operatore e i dati.\n\nIl COPPA si applica ai servizi rivolti ai minori e a quelli che sono effettivamente a conoscenza di raccogliere dati personali da minori di 13 anni. Si tratta di una legge sulla privacy dei minori, non di una norma generale sull’età minima per il gioco d’azzardo. È necessario definire il pubblico di riferimento, i dati personali raccolti, la consapevolezza in merito e la procedura di consenso dei genitori.\n\nFTC: Requisiti del COPPA ↗ archiviato 2026-09-21 ↗\n\nLe prove da conservare\nRegistra il percorso dall'accesso al deposito.\n\nMantenere inalterati i criteri di età minima, il testo relativo alla registrazione, i requisiti di ammissibilità, la procedura di pagamento e la cronologia dei reclami del sito. Valutare ciascun operatore separatamente. Mantenere riservate tutte le prove che coinvolgono un minore e oscurare i dettagli identificativi dai documenti pubblici.\n\nUn documento correlato relativo all’applicazione delle norme da parte delle autorità pubbliche è il Annuncio relativo alla causa intentata a New York nel 2026 archiviato 2026-09-01 ↗, che sostiene che i loot box a pagamento causino danni ai giovani utenti. Non si tratta di una constatazione ai sensi del COPPA.\n\nParte C — Quadri giuridici · Sezione 18 · Richiesta ai sensi dell’articolo 15 del GDPR\nLa richiesta. La risposta. Il confronto mancante.\n\nHa chiesto quattro cose, una delle quali era il log che avrebbe permesso di identificare chi aveva inserito una chiave API sul suo account. Tre giorni dopo, la segnalazione è stata chiusa con un link a una pagina in cui non compare nessuno di essi — e la frase con cui si conclude è smentita dagli stessi avvocati di Valve.\n\nA chi appartiene questo account · Provenienza e limiti\n\nQueste schermate non sono di PhishDestroy. Provengono da un normale titolare di un account Steam — uno dei partecipanti a un breve sondaggio condotto da questo progetto, che ha presentato personalmente la richiesta e ha fornito gli screenshot. L’account è il suo, il ticket è suo e la corrispondenza è tra lui e l’assistenza Steam. Questo progetto non ha inviato la richiesta, non possiede alcun account sulla piattaforma e non è parte in causa in questo ticket.\n\nIl 16 settembre 2026 ha presentato una richiesta di accesso ai dati personali ai sensi dell’articolo 15 del GDPR/CCPA, chiedendo specificatamente i registri di registrazione delle chiavi API, la cronologia degli accessi con gli indirizzi IP, la cronologia delle autorizzazioni dei dispositivi e la cronologia delle transazioni. Il 17 settembre l’operatore “Logen” lo ha indirizzato alla pagina self-service “Dati dell’account”. Il 18 settembre ha dichiarato che le categorie richieste non erano presenti in quella pagina e ha chiesto che la questione venisse inoltrata al team per la privacy o al responsabile della protezione dei dati (DPO). Il 19 settembre l’operatore “Kal” ha chiuso il ticket con lo stesso rinvio. Entrambe le schermate sono riportate di seguito (l’indirizzo e-mail del richiedente è stato oscurato; SHA-256 in steam_tos_assets/screenshot-manifest.json).\n\nÈ la persona giusta a cui rivolgersi per un motivo ben semplice: il suo account è associato a una chiave API Web Steam che lui non ha creato, registrata su localhost. Non si sa quando sia stato creato — non a lui, e non da nulla che Valve gli abbia messo a disposizione, poiché l’unico documento che ne consentirebbe la datazione è il registro di registrazione delle chiavi API, che è proprio la categoria che la chiusura ha omesso di fornire. La chiave non è nuova: la precede di un lasso di tempo che egli non è in grado di misurare, proprio per lo stesso motivo.\n\nAnche altri titolari di account stanno presentando la stessa richiesta. Qualsiasi risposta ricevuta verrà aggiunta qui alle stesse condizioni di queste due — numero di ticket, data di acquisizione, SHA-256, dati del richiedente oscurati — sia che accetti le categorie richieste sia che le rifiuti.\n\nIl presente progetto non prende posizione in merito al motivo per cui il ticket è stato chiuso. Nel ticket non è stata indicata alcuna motivazione e in questa sede non se ne deduce alcuna.\n\nLa richiesta. La risposta. Il confronto.SEGUI IL RECORD\nPassaggio 3 / 3\n\nHa chiesto quattro categorie specifiche. La pagina “Dati dell’account” a cui è stato indirizzato è la funzione di esportazione self-service di Valve, e questo progetto non può elencarne i contenuti per l’account di qualcun altro — pertanto qui non viene pubblicato alcun confronto completo categoria per categoria. Ciò che risulta documentato è la sua dichiarazione del 18 settembre in cui affermava che le categorie non erano presenti, e la chiusura del 19 settembre che ribadiva il rinvio senza affrontare la questione.\n\nLA RICHIESTACategorie specificheChiave API, dati di accesso, dati relativi ai dispositivi e alle operazioni di trading\nLA RISPOSTARiferimento ai dati dell'accountControllare lo scambio dei supporti\nIL TESTCosa è stato fornito?Confronta ciascuna categoria richiesta\nSchermata 1/2 — Richiesta (16 settembre) e prima risposta dell'agente \"Logen\" (17 settembre)\nGDPR ticket HT-2YBP-F7JP-D4VB — request and first response\nFonte: help.steampowered.com, ticket HT-2YBP-F7JP-D4VB · acquisito il 16-17 settembre 2026 · indirizzo e-mail del richiedente oscurato 2026-09-21 · File: gdpr-ticket-1.png · SHA-256 da940c731ab9869d226e9d06ccc8a1b393738766b7b0c445a56662623e025a66 (screenshot-manifest.json).\nSchermata 2/2 — Richiesta di escalation (18 settembre) e chiusura, agente \"Kal\" (19 settembre)\nGDPR ticket HT-2YBP-F7JP-D4VB — escalation request and closure\nFonte: help.steampowered.com, ticket HT-2YBP-F7JP-D4VB · acquisito il 18-19 settembre 2026 · File: gdpr-ticket-2.png · SHA-256 44844ea7b251f7fd7d79f87ee1578a846606a97b9659d3a53b322120c422219b (screenshot-manifest.json).\nRisposta conclusiva, 19 settembre (testuale):\n\"I dati Steam conservati sono già disponibili nella pagina 'Dati dell'account'. Poiché il Servizio di assistenza Steam non è in grado di fornire ulteriori informazioni, questa richiesta verrà chiusa.\"\nDati non forniti · nessuna base giuridica per il rifiuto indicata · nessun esito dell'escalation indicato\nQuella frase è falsa, e lo dimostrano proprio gli avvocati di Valve. La lettera del legale del 1° ottobre 2025, al paragrafo 1.9, descrive una correlazione a livello di dispositivo che collega un dispositivo a decine di account (Appendice A). La stessa risposta comprendeva 830 pagine di documenti conservati (Appendice B). Nulla di tutto ciò compare nella pagina \"Dati dell'account\".\nPerché questo account ha richiesto il registro delle chiavi API?\n\nNon ha scelto quelle quattro categorie a caso. Il localhost la chiave del suo account è il segno distintivo di uno script, non di una persona che digita un dominio reale nella pagina degli sviluppatori (Sezione 5, Sezione 6). L'unico documento che indica chi l'ha creato e da dove proviene è il registro delle registrazioni delle chiavi API. È stata la prima cosa che ha chiesto. Ed è proprio questo che la chiusura ha omesso.\n\nFonte: il titolare dell'account, durante il sondaggio relativo a questo progetto. Gli screenshot dei ticket riportati sopra sono stati sottoposti a hash; la pagina della chiave non è stata pubblicata.\n\nValutazione · PhishDestroy\n\nChiudere un ticket quando la questione è ancora in sospeso non è un caso. È la normale conclusione. Noi riteniamo che 16,319 documentazione relativa ai reclami e all’assistenza conservata e 354 scambi di assistenza deduplicati tratto da essi. Questo biglietto è un esempio datato e completo della forma che assumono.\n\nTicket di assistenza — ConservatoHT-2YBP-F7JP-D4VB\nTipo di richiestaArticolo 15 del GDPR (Richiesta di accesso ai dati personali)\nStato del bigliettoCHIUSO IL 19 SETTEMBRE 2026 — DATI NON FORNITI\nAgenti nella borsa valori\"Logen\" (17 settembre), \"Kal\" (19 settembre)\nArchiviato16 settembre 2026\nDati richiestiChi ha registrato la chiave API Web associata a questo account e da quale indirizzo IP / dispositivo / data e ora?\nBase giuridica citataArt. 15 del GDPR — diritto di accesso ai dati personali\nIl quadro giuridico:L’articolo 12, paragrafo 3, concede al titolare del trattamento un mese di tempo a partire dal ricevimento (prorogabile previa motivazione). Tale termine non era ancora scaduto al momento della pubblicazione e il presente fascicolo non sostiene che vi sia stata una violazione dei termini. L’obiezione riguarda la sostanza: la risposta conclusiva rimanda a una pagina self-service ma non dimostra che le quattro categorie di dati indicate siano state fornite; inoltre, qualora il titolare del trattamento si rifiuti di agire, l’articolo 12, paragrafo 4, gli impone di indicarne i motivi e le vie di ricorso. Nessuno dei due elementi figura nella risposta conclusiva.\nPerché questi dati specifici sono importanti\n\nIl registro degli eventi delle chiavi API Web è il documento che indica se una terza parte ha registrato una chiave utilizzando un cookie di sessione rubato — il meccanismo descritto nelle denunce di furto di inventario conservate nell’archivio di questo dossier. Rivelare chi ha registrato una chiave API, da quale indirizzo IP e in quale momento, consentirebbe di:\n\nConsentire alla vittima di confrontare l’indirizzo IP utilizzato per la creazione dell’API con la propria cronologia di accesso\nIndividua gli indirizzi IP dei data center collegati a infrastrutture note di bot utilizzate per il phishing e il gioco d'azzardo\nFornire prove utilizzabili in procedimenti civili o penali a carico dell’autore del fatto\nIndica se il titolare del conto è stato informato al momento della creazione della chiave\nCosa emerge dai dati: Valve conserva i registri relativi ai dispositivi e alla correlazione degli account — tali registri sono descritti nella lettera del suo legale del 1° ottobre 2025 (cfr. Appendice A, Memorandum probatorio — Fonte 1). Nel ticket HT-2YBP-F7JP-D4VB la stessa categoria di registrazioni è stata richiesta dall’interessato e il ticket è stato chiuso con un rinvio a una pagina self-service che, secondo quanto segnalato dall’interessato, non le conteneva. Se tale rifiuto sia legittimo è una questione che spetta all’autorità di controllo; l’effetto è che l’interessato non riceve tali dati.\nLo scambio — quattro messaggi, tre giorni\n\nDue agenti dell’assistenza Steam hanno risposto utilizzando i nomi di battesimo indicati nel ticket: “Logen” il 17 settembre e “Kal” il 19 settembre. Entrambi hanno indirizzato il richiedente alla pagina “Dati dell’account”. Nulla nel ticket indica se la richiesta sia giunta al team per la privacy o al responsabile della protezione dei dati di Valve, e il fascicolo non specifica chi siano gli addetti, quali siano i loro ruoli né come sia stato inoltrato il ticket.\n\n16 SET\nArt. 15: richiesta presentata con quattro categorie di dati specificate\n17–18 settembre\nRiferimento ai dati dell’account; il richiedente chiede che la questione venga sottoposta al responsabile della protezione dei dati (DPO)\n19 SET\nIl ticket è stato chiuso con lo stesso riferimento; nessun dato, nessuna motivazione indicata\nA cosa l’articolo 15 del GDPR conferisce esplicitamente il diritto all’interessato\nArt. 15, comma 1, lettera a)Finalità del trattamento — perché Valve conserva i dati\nArt. 15, comma 1, lettera b)Categorie di dati — cosa contiene Valve\nArt. 15, comma 1, lettera c)Destinatari o categorie di destinatari — chi ha ricevuto i dati (ad esempio, il titolare della chiave API)\nArt. 15, comma 1, lettera d)Periodo di conservazione o criteri per la sua determinazione\nArt. 15, comma 3Una copia dei dati personali oggetto del trattamento — ovvero il registro delle chiavi API stesso\nART. 12, comma 3Risposta richiesta entro un mese dalla data di ricezione; l’eventuale proroga deve essere comunicata entro tale mese. Al momento della pubblicazione, il termine non era ancora scaduto. Art. 12, comma 4: Se il responsabile del trattamento non interviene, deve motivarne le ragioni e informare l’interessato sulle vie di ricorso.\nProcedura di reclamo in materia normativa — per qualsiasi utente\n\nQualsiasi utente che abbia presentato una richiesta ai sensi dell’articolo 15 del GDPR a Valve e non abbia ricevuto una risposta conforme (o abbia ricevuto un rifiuto standardizzato privo di dati) può presentare un reclamo all’autorità di controllo dello Stato membro dell’UE/SEE di appartenenza. La sede di Valve nell’UE è Valve GmbH ad Amburgo, pertanto l’autorità di controllo capofila per i reclami transfrontalieri è la Autorità di Amburgo per la protezione dei dati e la libertà di informazione (HmbBfDI). (Anche il rappresentante di cui all’articolo 27 di Valve ha sede ad Amburgo; l’indirizzo di un rappresentante non è di per sé determinante ai fini dell’individuazione dell’autorità competente.) È inoltre possibile presentare un reclamo all’autorità dello Stato membro di appartenenza del reclamante ai sensi dell’articolo 77.\n\nModulo di reclamo HmbBfDI ↗ Testo del GDPR (artt. 12, 15, 77) ↗ archiviato 2026-09-20 ↗Linee guida dell’EDPB ↗\n\nNumero di riferimento del biglietto per eventuali reclami: HT-2YBP-F7JP-D4VB — conservato in questo fascicolo come caso documentato.\n\nUn caso documentato\nI documenti esistono; l'interessato non li ha ricevuti.\n\nIl legale di Valve ha descritto i registri di correlazione a livello di dispositivo in una lettera del 1° ottobre 2025. Il 19 settembre 2026 una richiesta ai sensi dell’articolo 15 relativa alla stessa categoria di registri è stata chiusa con un rinvio a una pagina self-service che, secondo quanto riferito dal richiedente, non li conteneva, senza che fosse indicata alcuna base giuridica. Il ticket HT-2YBP-F7JP-D4VB costituisce un caso documentato; se ciò rifletta una pratica più ampia è una questione che spetta all’autorità di controllo, la quale può richiedere a Valve i propri registri relativi alla gestione dei casi.\n\nArticoli 12, 15 e 77 del GDPR / Autorità di controllo\n\nÈ possibile presentare un reclamo ai sensi degli articoli 12 e 15 direttamente all’autorità di controllo competente senza alcun costo (articolo 77). L’autorità può imporre misure correttive, tra cui l’ordine di dare seguito alla richiesta di accesso, nonché infliggere sanzioni ai sensi dell’articolo 83, paragrafo 5, lettera b), in caso di violazione dei diritti degli interessati. Conservare il numero di riferimento originale del ticket e l’eventuale risposta Valve (o la sua assenza) rafforza la fondatezza del reclamo.\n\nVedi il modello DSAR →\nParte C — Quadri giuridici · Sezione 19 · Diritto contrattuale\nIl Contratto di abbonamento in contrasto con l'architettura della piattaforma stessa\nContesto e limiti della fonte\n\nGli autori non sono avvocati e quanto riportato non costituisce in alcun modo una consulenza legale. Il testo della SSA è tratto dalla revisione del 10 settembre 2026; una revisione diversa potrebbe presentare formulazioni diverse, e la numerazione delle clausole è cambiata nel corso delle varie revisioni — si raccomanda di verificare la clausola facendo riferimento alla versione che disciplinava la condotta in questione. Le argomentazioni relative agli articoli 25 e 32 indicano ciò che il regolamento richiede, non che un'autorità di controllo abbia riscontrato una violazione. I dati riportati nell'argomentazione 1 riflettono i limiti di ambito stabiliti nella sezione 13.\n\nTre delle disposizioni fondamentali della SSA risultano in contrasto con la struttura della piattaforma: il divieto di uso commerciale, il limite massimo di prezzo del Market che spinge le vendite di alto valore fuori dalla piattaforma; la clausola di responsabilità dell’utente per le chiavi API, in contrasto con un endpoint chiave che, prima del 2023, non richiedeva l’autenticazione a due fattori; e la formulazione relativa all’applicazione della normativa, in contrasto con un documento pubblico che non riporta alcuna applicazione specifica per operatore. Se tali tensioni incidano sull’applicabilità della normativa è una questione di competenza del tribunale; questa sezione espone i fatti che verrebbero sottoposti all’esame di un tribunale.\n\nArgomento 1 / Architettura della capitalizzazione di mercato\nIl limite massimo di mercato e il divieto di uso commerciale\n\nIl mercato comunitario Steam ha un tetto massimo di quotazione pari a circa $1,800. In cinque mercati, secondo un’istantanea datata (23 settembre 2026), 248 categorie di articoli CS2 presentano prezzi fissati in modo indipendente da due o più di tali mercati al di sopra di tale tetto massimo; tali articoli non possono essere venduti a quei prezzi sulla piattaforma di Valve. I proprietari che desiderano ottenere tali prezzi ricorrono a mercati di terze parti, che operano tramite account Steam e l'API Steam — la SSA li classifica come commerciali, salvo espressa autorizzazione.\n\nGli articoli superano il limite massimo del Mercato → i mercati di terze parti colmano il divario → tali mercati utilizzano account Steam e l’API Steam → la SSA vieta l’uso commerciale senza autorizzazione → non è stato pubblicato alcun registro delle autorizzazioni. La commissione complessiva del Mercato della Comunità, pari a circa 15%, si applica solo alle vendite concluse all’interno del Mercato, non a queste transazioni esterne.\nArgomento 2 / Architettura di sicurezza delle chiavi API\nLa vulnerabilità della chiave API come problema di progettazione della piattaforma piuttosto che come negligenza da parte dell'utente\n\nPrima del 2023, l'endpoint di creazione delle chiavi API di Steam accettava una richiesta POST con un ID di sessione rubato e generava credenziali con privilegi elevati senza conferma via e-mail, autenticazione a due fattori o verifica tramite dispositivo. Le segnalazioni relative al dirottamento delle API raccolte nel corso di questa indagine seguono tutte lo stesso schema: script dell’autore dell’attacco, cookie di sessione rubato, creazione silenziosa di una chiave, intercettazione delle transazioni (il payload della richiesta è riportato nella Sezione 8).\n\nL’articolo 25 del GDPR (protezione dei dati fin dalla progettazione) e l’articolo 32 (sicurezza del trattamento) richiedono misure tecniche adeguate al rischio. L’emissione di una credenziale suscettibile di intercettazione durante la trasmissione senza un secondo fattore di autenticazione o senza notifica al titolare costituisce una questione di progettazione che spetta al titolare del trattamento. Se, in tale contesto, sia possibile fare affidamento sulla clausola SSA che attribuisce la responsabilità all’utente è una questione che spetta al tribunale e all’autorità di controllo.\n\nArgomento 3 / Visibilità in tempo reale\nValve riceve il nome host di autenticazione ad ogni accesso\n\nIl nome host di autenticazione arriva all'endpoint OpenID di Valve in testo in chiaro in openid.return_to e openid.realm (la struttura della richiesta è illustrata nella Sezione 3). L’estrazione è un’operazione standard. Al 2026-09-22, in 26 coppie il dominio principale era presente nel Link Filter, mentre l’host che ospitava il suo Steam login non lo era. Valve non ha pubblicato alcun registro delle misure applicate per singolo operatore, pertanto dai dati pubblici non è possibile stabilire se a questi host siano state applicate misure diverse dal filtro di collegamento.\n\nChi ne sostiene il costo\nL'andamento dei reclami archiviati\n\nNei reclami esaminati, la risposta di Steam Support a una segnalazione di dirottamento della chiave API segue sempre lo stesso schema: rifiuto del ripristino, richiamo alla responsabilità dell’utente per l’account e la relativa chiave API, chiusura del ticket. In questo dossier non viene fornita alcuna stima complessiva relativa agli account interessati o al valore perso; non è stata individuata alcuna fonte a sostegno di tale cifra.\n\nLa questione non è se i singoli utenti abbiano commesso degli errori. La questione è chi sia responsabile di un’architettura che, fino al 2023, ha consentito a una richiesta POST con un cookie rubato di creare credenziali di trading con privilegi elevati senza alcuna notifica e senza autenticazione a due fattori.\nL’SSA come documento rispetto all’SSA come contratto\nUn tribunale chiamato a valutare questo fascicolo non interpretarebbe la SSA in modo isolato.\n\nLo esaminerebbe insieme alla lettera dell’avvocato dell’ottobre 2025 in cui vengono descritti la correlazione a livello di dispositivo, le date di registrazione dell’host di autenticazione, i timestamp di registrazione dei lotti, il payload della richiesta della chiave API e i dieci anni intercorsi tra le notifiche del luglio 2016 e le piattaforme ancora operative nel settembre 2026. Questo è il fascicolo che Valve dovrebbe esaminare.\n\nSSA rispetto al dato di riferimento / punti chiave\n\"Nessun uso commerciale\" — il tetto massimo del Mercato spinge le vendite di alto valore verso mercati commerciali di terze parti\n\"Gli utenti sono responsabili delle chiavi API\" — nessuna autenticazione a due fattori sull'endpoint delle chiavi prima del 2023\n\"Adottiamo provvedimenti nei confronti dei trasgressori\" — dal luglio 2016 non vengono più pubblicati i dati relativi ai provvedimenti adottati per singolo operatore\n\"Hai accettato i termini\" — nello schema di dirottamento, l'accettazione viene inviata da uno script, non dal titolare dell'account\nConclusione · Cosa emerge dagli atti e cosa chiediamo\nI risultati. I documenti che richiediamo.\nContesto e limiti della fonte\n\nCiascuna delle conclusioni riportate di seguito è collegata a un documento pubblico datato presente nelle sezioni precedenti. Le richieste sono rivolte alle autorità in grado di ottenere l’unica cosa che questa indagine non può raggiungere: i registri relativi all’applicazione delle norme, all’accesso e al trattamento dei dati da parte di Valve.\n\nOgni richiesta fa seguito a un accertamento datato. Le autorità possono richiedere documenti che questa indagine basata su fonti pubbliche non può ottenere.\n\nCiò che risulta dai documenti pubblici\n44 piattaforme attive effettuano l’autenticazione tramite un dominio registrabile separato — 27 con un file di prova pubblicato per ogni percorso, 17 provenienti da una raccolta manuale ed elencate a parte. Al 2026-09-22, 26 coppie presentavano il dominio principale bloccato nel filtro dei link Steam, mentre l’host che ospitava il relativo login non lo era — csgogem.com bloccato, api.csgem.com registrato dal marzo 2014. Steam riceve quel nome host in openid.realm e openid.return_to ad ogni accesso. Sezione 3\nIl 13 luglio 2016 Valve ha reso pubblico il nome del meccanismo e ne ha vietato l’uso, mentre le comunicazioni del suo legale del 20 luglio 2016 hanno fissato un termine di dieci giorni. Nei dieci anni trascorsi da tale scadenza non è stato pubblicato alcun registro delle misure di applicazione per singolo operatore. Sezione 11\nL'endpoint della chiave API Web Steam rilasciava credenziali con privilegi elevati e idonee alla negoziazione basandosi esclusivamente su un cookie di sessione, senza alcun secondo fattore di autenticazione prima del 2023. Sezione 5\nUna richiesta ai sensi dell'articolo 15 del GDPR (ticket HT-2YBP-F7JP-D4VB) è stata chiusa dopo tre giorni con un link al servizio self-service e senza alcun dato. Sezione 18\nCosa chiediamo a ciascuna autorità\nCommissione per il gioco d'azzardo dello Stato di Washington\nRiaprire il fascicolo del 2016. Richiedere un resoconto, operatore per operatore, che indichi quali account, bot e host di ritorno siano stati disabilitati dopo gli avvisi di dieci giorni e quali operatori abbiano successivamente riottenuto l'accesso. Sezione 2\nHmbBfDI (Amburgo; Valve GmbH)\nVerificare se la risposta ai sensi dell’articolo 15 abbia adempiuto all’obbligo del titolare del trattamento e richiedere la divulgazione dei registri relativi alla registrazione della chiave API e agli accessi, utili all’identificazione dell’autore dell’azione. Sezione 18\nCoordinatori dei servizi digitali (DSA)\nInserire le indicazioni relative al routing dell’host di autenticazione nel verbale come nota, quindi valutare se la risposta di Valve soddisfa i propri obblighi una volta documentate le informazioni. Sezione 16\nQualsiasi interessato\nUtilizza il modello previsto dall'articolo 15 per richiedere gli stessi dati relativi al tuo account; un dato conservato può consentire di verificare chi ha avviato un ripristino o creato una chiave. Appendice G\n\nL'unica richiesta alla base di tutte e quattro è la stessa: rendere pubblici i registri relativi all'applicazione delle norme, all'accesso e al trattamento dei dati di cui solo Valve è in possesso. Un avviso sulla homepage, una lettera con preavviso di dieci giorni e una pagina self-service sono tutte manifestazioni di controllo. Se tale controllo sia stato effettivamente esercitato è una domanda alla quale i registri pubblici non possono rispondere, mentre un'autorità di regolamentazione sì.\n\nAppendici — documenti principali e materiali di lavoro\nAppendice A — Corrispondenza con i consulenti legali\nMemorandum probatorio — materiale fornito dalla fonte 1\n\nBase probatoria e stato delle fonti relative alla corrispondenza con i legali citata nelle sezioni 1, 18 e 19.\n\nBase probatoria e stato della fonte — documenti forniti dalla fonte 1\nL'utente il cui ban permanente ha dato origine alla presente verifica non è oggetto della stessa. In questa sede non viene valutato se tale ban fosse giustificato, e il presente fascicolo non lo difende né lo contesta. L'account non è il punto centrale. Ciò che conta è il materiale: Fonte 1 — il titolare dell’account sospeso, che ha ricevuto la corrispondenza riportata di seguito dal legale di Valve in qualità di interessato della propria richiesta ai sensi del GDPR — ha trasmesso tale corrispondenza e i fascicoli allegati, concedendo il diritto di consultarli pubblicamente. Il nome non viene reso noto; i documenti sono descritti in base alla data, ai metadati del produttore e all’hash.\n\nTale corrispondenza è stata inviata in risposta a una richiesta ai sensi del GDPR/DSAR. Nel corso della stessa, il legale di Valve ha messo a verbale una dichiarazione, firmata, in cui descriveva una funzionalità che il servizio di assistenza di Steam aveva precedentemente comunicato agli utenti non essere tecnicamente possibile. Il paragrafo riportato di seguito è proprio quella dichiarazione.\n\nL'ulteriore analisi condotta dagli autori sull'estratto di log generato è omesso dal presente fascicolo in attesa di una revisione indipendente. Nessun altro aspetto della presente indagine si basa su tale elemento.\n\nL'ammissione messa a verbale: telemetria persistente a livello di dispositivo\n\nAl paragrafo 1.9 della lettera attribuita al legale di Valve, gli avvocati di Valve affermano: \"Tra il 2019 e il 2023, questo account è stato utilizzato principalmente da un dispositivo che è stato impiegato anche per accedere a decine di account Steam rubati.\"\n\nIl fatto: L’avvocato di Valve descrive in questa sede una correlazione a livello di dispositivo tra account che copre un arco di quattro anni. L’assistenza clienti di Steam ha comunicato alle vittime di furto che il tracciamento degli oggetti rubati o il collegamento degli account ai dispositivi non era tecnicamente possibile. Steam Guard L’autorizzazione dei dispositivi è documentata pubblicamente, quindi l’esistenza di registrazioni per singolo dispositivo non è di per sé una novità; ciò che è nuovo è la conferma scritta del legale che tali registrazioni vengono conservate e correlate tra gli account per periodi pluriennali.\n\nPerché è importante: La correlazione in grado di collegare un dispositivo a decine di account compromessi nell’arco di quattro anni rientra nella stessa categoria di dati che, secondo il Supporto, non poteva essere utilizzata a favore delle vittime. I dati di quella categoria consentirebbero di identificare account e dispositivi all’interno di una catena di furto e rivendita. Quali dati esistono, per quanto tempo vengono conservati e su quale base vengono negati agli interessati sono le domande che l’autorità di controllo dovrà chiarire.\n\nFonte: lettera del legale di Valve datata 1° ottobre 2025, paragrafo 1.9, e relativa appendice in formato PDF di 830 pagine · ricevuta dalla Fonte 1 in risposta a una richiesta ai sensi dell’art. 15 del GDPR · SHA-256 dell’appendice registrato in disclosure-audit.json · La lettera non viene riprodotta; i nomi dei conti e i dati di terzi sono stati omessi.\n\nStato: apri\nI materiali di riferimento sono disponibili nell’archivio delle prove.\nAppendice B — Il PDF generato · verifica della redazione\nLa censura nel file PDF fornito è di natura puramente estetica: il testo oscurato rimane comunque estraibile\n\nIl legale di Valve ha risposto a una richiesta di accesso ai sensi del GDPR allegando un documento di 830 pagine in cui le parti oscurate sono state coperte con un tratto di pennarello anziché essere rimosse. 902,270 caratteri si trovano sotto le barre nere e vengono visualizzati immediatamente tramite uno strumento di estrazione del testo — compresi gli identificatori di terze parti che le barre avrebbero dovuto nascondere. Qui vengono pubblicati solo i dati aggregati; nessun contenuto protetto viene riprodotto e l’appendice stessa non viene pubblicata.\n\n1. Cosa ha rilevato il controllo geometrico\n\nRisposta ai sensi dell’art. 15 del GDPR in data 1° ottobre 2025 era accompagnato da un’appendice in formato PDF di 830 pagine (metadati del produttore Aspose.PDF per .NET, creati e modificati nella stessa data). Gli autori hanno eseguito un controllo geometrico a livello di pagina: per ogni pagina sono stati individuati i rettangoli opachi, quasi neri, sovrapposti al livello di testo, e sono stati contati i caratteri estraibili che si trovavano al di sotto di essi.\n\nMisurato sul file generato\n902,270\nCaratteri ancora leggibili sotto le barre nere\nDati effettivi, non stime. Si tratta di un conteggio dei personaggi coinvolti, non delle vittime, delle reidentificazioni o degli incidenti.\n830 / 830\nPagine interessate — tutte le pagine\n986\nRettangoli su testo estraibile\n1,329\nRettangoli neri opachi in totale\nLe barre nere sono state tracciate sopra il livello di testo; non lo eliminano. Il testo sottostante può essere estratto con strumenti standard per i PDF. Vengono pubblicati solo i dati aggregati; nessun contenuto coperto viene riprodotto in questa sede.\nDimostrazione forense: separazione degli strati\nASPOSE.PDF PER .NET: MODELLO DI SOVRAPPOSIZIONE VETTORIALE (APPENDICE, pag. 412)\n\nSegnalazione presentata nei confronti dell'account: [LOGIN: utente_oscurato_667]\n\nMotivo indicato dall'utente: [TESTO: \"L'utente segnala la presenza di oggetti duplicati nell'inventario e comportamenti commerciali scorretti...\"]\n\nIn primo piano: <path fill=\"#000\" />Difetto: il flusso UTF-8 sottostante rimane intatto\nFonte: appendice in formato PDF alla lettera dell'avvocato del 1° ottobre 2025 (830 pagine, metadati del produttore Aspose.PDF per .NET) · misurato dagli autori, metodo e conteggio per pagina in disclosure-audit.json · Il valore SHA-256 dell’appendice è riportato nello stesso file · l’appendice stessa non è pubblicata.\n2. Perché questo è importante per la risposta dell’interessato\n\nIl legale di Valve ha inviato questo fascicolo a un interessato in risposta a una richiesta relativa ai propri dati personali. Le barre sono solo a scopo estetico: il testo sottostante non è mai stato rimosso, quindi gli identificativi di terze parti che le barre avrebbero dovuto nascondere sono stati trasmessi al destinatario insieme al file. Una censura che può essere rimossa con uno strumento di estrazione del testo non nasconde nulla e impedisce inoltre al destinatario di stabilire cosa sia stato divulgato e cosa no.\n\nL’articolo 15, paragrafo 4, è la ragione stessa dell’esistenza di tali restrizioni: il diritto di ottenere una copia non deve ledere i diritti e le libertà altrui. Questo è l’obbligo che la presente produzione non ha rispettato. Spetta all’autorità di controllo stabilire se si tratti di una violazione dei dati personali ai sensi dell’articolo 4, paragrafo 12; la divulgazione stessa è misurabile nel file e riproducibile da chiunque disponga degli stessi byte — l’SHA-256 è pubblicato, l’appendice no.\n\nQuello che c’era sotto le sbarre non erano numeri di conto. Si trattava del corpus delle segnalazioni presentate dagli utenti nei confronti del richiedente, con l’indicazione dei rispettivi autori: Steam accessi che, poiché un account viene raramente utilizzato solo su Steam, identificano la persona che vi si cela — Secondo i calcoli degli autori, oltre 60% degli utenti citati nel documento sono pienamente identificabili — insieme al testo originale, non censurato, di ciò che hanno scritto. Tale testo contiene auguri di morte e insulti rivolti alla nazionalità del richiedente. Alcune delle persone così identificate sono minorenni. La produzione ha consegnato un elenco nominativo di giornalisti alla persona che avevano segnalato, che è proprio il danno che l'art. 15, comma 4, è stato concepito per prevenire.\n\nL'ordine delle righe nel file è importante tanto quanto il suo contenuto. Alla richiesta è stata inizialmente opposta la richiesta di ulteriori prove di identità, con la motivazione che l’indirizzo e-mail alias del richiedente non conteneva il suo nome; durante il ritardo che ne è seguito, l’account è stato bloccato in modo permanente. La lettera che alla fine ha fornito i dati, a più di sei settimane dal termine di un mese previsto dall’art. 12(3), minacciava il destinatario di un procedimento penale e gli negava l’accesso al resto dei propri dati fino a quando non avesse spiegato l’attività del proprio account al legale. La divulgazione chiarisce inoltre due questioni a cui Valve non ha mai risposto pubblicamente: i documenti prodotti dimostrano che il collegamento tra account risale al 2019 e rivelano una telemetria interna di una profondità che Valve non ha mai descritto.\n\nAmbito di applicazione della presente sezione: L'osservazione qui riportata si limita agli aspetti tecnici della redazione, analizzati sulla base del file così come è stato prodotto. L'ulteriore analisi dei log prodotti, effettuata dagli autori, è stata sospesa in attesa di una revisione indipendente e non viene presa in considerazione in altre parti del presente dossier.\n\nProva: lettera dell’avvocato del 1° ottobre 2025 e relativa appendice in formato PDF (codice SHA-256 registrato nel file di audit); Misure e metodo relativi ai PDF a livello di pagina ↗. La sequenza della richiesta, il rifiuto di cui a pagina 8 e la descrizione dei dati divulgati sono riportati integralmente nel resoconto di PhishDestroy, “Il mio cane contro gli avvocati d’élite del GDPR”, 17 agosto 2026 ↗ archiviato 2026-08-21 ↗. I nomi degli account e i dati di terze parti sono stati omessi in questa sede; non viene riprodotto nulla di quanto coperto dalle barre.\n\nA pagina 8 della lettera di accompagnamento si respinge una parte della richiesta, indicandone per iscritto il motivo: Non è possibile fornire informazioni più dettagliate a causa della tutela dei dati personali degli altri utenti della piattaforma Steam… — non è possibile fornire una risposta più dettagliata, poiché occorre tutelare i dati personali degli altri Steam utenti. L’appendice di 830 pagine era contenuta nello stesso plico. Ciò che le barre coprivano non erano numeri di conto: si trattava delle denunce presentate contro il richiedente, con i nomi degli autori, alle quali erano allegati i messaggi grezzi non censurati. Il titolare del conto aveva chiesto a Valve, tramite il proprio legale, il proprio fascicolo; ciò che riuscì a ricavarne riguardava altre persone. Nulla in questa appendice dipende da chi abbia tracciato le caselle. Ciò che emerge è che la tutela Valve invocata come motivo per negare l’accesso è proprio quella che questa stessa consegna non è riuscita a garantire, nella stessa busta, lo stesso giorno.\nDocumentazione relativa all’assistenza e alla corrispondenza legale\n\nFonte: https://phishdestroy.io/steam_dossier/it/index#exhibit-gallery-section\n\nAppendice D — Raccolta delle fonti\nDocumenti primari selezionati\n\nSei documenti provenienti dall'archivio: tre segnalazioni su GitHub nei tracker di Valve e tre post su Reddit relativi a esiti controversi delle richieste di assistenza. Ogni fonte rimane associata alla segnalazione, al testo salvato e alla questione che essa solleva.\n\n1 / 6 record selezionati\nScegli un record di origine\nGH-01 / GITHUBApri nella build salvata\nChiavi hardware, richieste nel 2016\n\nValveSoftware / steam-for-linux · n. 4521 · 2016-06-27\n\nUn utente ha chiesto a Valve di supportare le chiavi hardware U2F come secondo fattore di autenticazione alternativo. La segnalazione salvata presenta sia l'etichetta “Richiesta di funzionalità” che quella “Revisionata”, con lo stato registrato come “aperta”.\n\nChiedo che su Steam venga aggiunto il supporto per le chiavette USB U2F come alternativa.\n\nEstratto dall'issue su GitHub ↗\nDocumentazione ufficiale\nUna richiesta datata relativa a una misura di sicurezza aggiuntiva per l'account, pubblicata nel sistema di tracciamento dei problemi di Valve e contrassegnata come \"rivista\".\nRichiesta di rendicontazione\nPubblicare la decisione relativa al prodotto, la data di risposta e la protezione concessa a seguito della revisione.\nLeggi il record salvato →Apri GitHub ↗\nNel dossier: Misure di sicurezza degli account →Archivio n. 484 · build 2026-09-17\nGH-02 / GITHUBApri nella build salvata\nSegnalazioni di crash senza un’efficace opzione di rinuncia\n\nValveSoftware / steam-for-linux · n. 6459 · 2019-08-18\n\nIl segnalante descrive un client Steam del 12 agosto 2019 su Ubuntu 16. Afferma che la disattivazione della destinazione per il caricamento automatico dei crash non è rimasta attiva dopo il riavvio e allega la configurazione pertinente.\n\nSe disattivo il parametro `ServerURL`, questo viene sovrascritto dopo ogni riavvio.\n\nEstratto dall'issue su GitHub ↗ archiviato 2026-04-19 ↗\nDocumentazione ufficiale\nUn reclamo specifico relativo alla privacy, con indicazione della data del cliente, del sistema operativo e di un estratto della configurazione. Il caso salvato è aperto.\nRichiesta di rendicontazione\nIdentificare l'indagine, le build interessate e la modifica che ha reso effettiva l'esclusione.\nLeggi il record salvato →Apri GitHub ↗archiviato 2026-04-19 ↗\nNel fascicolo: Richiedi i documenti di riferimento →Archivio n. 467 · build 2026-09-17\nGH-03 / GITHUBApri nella build salvata\nAbuso di ticket di autenticazione segnalato a Valve\n\nValveSoftware / Source-1-Games · n. 3857 · 2022-02-26\n\nL'autore sostiene che un gestore del server abbia conservato Steam ticket di autenticazione dopo che i giocatori si erano disconnessi e abbia utilizzato elenchi di server fuorvianti. Il post chiede a Valve di intervenire in merito a tale comportamento.\n\nFare in modo che i loro server sembrino pieni.\n\nEstratto dall'issue su GitHub ↗\nDocumentazione ufficiale\nUna segnalazione di abuso pubblica presentata nel tracker di Valve il 26 febbraio 2022. Il suo stato salvato è \"aperto\"; la segnalazione include link a screenshot.\nRichiesta di rendicontazione\nFornire i risultati dell'indagine e il resoconto delle misure correttive adottate in merito all'abuso del ticket di autenticazione segnalato.\nLeggi il record salvato →Apri GitHub ↗\nNel dossier: Ambito del set di dati →Archivio n. 768 · build 2026-09-17\nRD-01 / REDDITProfilo dell'autore\n44 acquisti sul mercato oggetto di controversia\n\nr/DotA2 · nome utente dell'autore non divulgato · 2022-07-07\n\nL'autore riferisce di 44 acquisti non autorizzati effettuati su Market il 6 luglio 2022 e di perdite pari a circa $500+. Afferma che l'autenticazione a due fattori era abilitata e descrive le ripetute risposte standard ricevute dal servizio di assistenza.\n\nÈ già il secondo ticket che invio e non ho ancora ricevuto una risposta da Steam che non sia un semplice copia-incolla automatizzato.\n\nEstratto dal post su Reddit ↗ archiviato 2025-03-20 ↗\nDocumentazione ufficiale\nUn resoconto datato relativo ad acquisti contestati, con link alle schermate delle transazioni e alla risposta del servizio di assistenza. Gli importi e i fatti riportati sono quelli descritti dall'autore.\nRichiesta di rendicontazione\nConfronta gli acquisti contestati con i registri delle transazioni e delle sessioni. Spiega le motivazioni alla base della decisione del servizio di assistenza.\nLeggi il record salvato →Apri Reddit ↗archiviato 2025-03-20 ↗\nNel dossier: Assistenza e applicazione →Archivio n. 4,533 · build 2026-09-17\nRD-02 / REDDITProfilo dell'autore\nSospensione definitiva e ricorso inammissibile\n\nr/ohnePixel · nome utente dell'autore non divulgato · 2024-12-09\n\nL'autore contesta il ban permanente e afferma che il supporto abbia fatto riferimento a un presunto trasferimento di account e a segnalazioni della community. Descrive i ticket chiusi e l'intenzione di richiedere i propri dati personali.\n\nHo spiegato la mia situazione e ho chiesto maggiori dettagli, ma loro rimangono fermi sulla loro decisione e stanno chiudendo i miei ticket.\n\nEstratto dal post su Reddit ↗\nDocumentazione ufficiale\nUn resoconto dell'appello conservato, comprensivo delle motivazioni che, secondo l'autore, giustificano il supporto fornito e dei link a quattro immagini. La data del post è ricavata dall'esportazione del supporto selezionato.\nRichiesta di rendicontazione\nIndicare le prove a sostegno del divieto definitivo e le vie di ricorso disponibili per contestarlo. La chiusura di un ricorso non costituisce una motivazione della decisione.\nLeggi il record salvato →Apri Reddit ↗\nNel fascicolo: Richiedi i documenti di riferimento →Archivio n. 4,766 · versione 2026-09-17\nRD-03 / REDDITProfilo dell'autore\nUn ripristino del sistema di recupero e una perdita segnalata pari a $10,000\n\nr/legaladvice · nome utente dell'autore non divulgato · 2025-05-09\n\nL'autore sostiene che il servizio di assistenza abbia reimpostato le credenziali e disattivato le protezioni dell'account dopo che qualcun altro aveva inviato una richiesta di recupero. Segnala una perdita di circa US$10,000 da un account inattivo.\n\nSteam L'assistenza mi ha reimpostato la password e ha disattivato tutte le misure di sicurezza del mio account.\n\nEstratto dal post su Reddit ↗\nDocumentazione ufficiale\nUn’accusa documentata secondo cui il processo di recupero avrebbe ignorato le misure di sicurezza dell’account. Il post salvato riporta quanto l’autore sostiene gli sia stato riferito dall’assistenza.\nRichiesta di rendicontazione\nIndicare chi ha autorizzato la reimpostazione, la prova di titolarità accettata e il registro degli accessi. Il recupero dell'account fa parte dei controlli Valve del sistema di sicurezza.\nLeggi il record salvato →Apri Reddit ↗\nNel dossier: Richiedi i documenti di riferimento →Archivio n. 4,592 · versione 2026-09-17\n\nSei record selezionati. Le descrizioni su GitHub illustrano la build salvata. I post su Reddit riportano i resoconti degli autori.\n\nScarica i sei brani ↓\n\nLa build ricercabile contiene 16,319 record distinti: 393 su Trustpilot, 5,635 su Reddit, 2,395 su GitHub, 276 sul web e 7,620 su wiki. Più record possono riguardare lo stesso evento. L'esportazione principale separata di 40,448 righe ha un ambito diverso.\n\nCerca nell'archivio completo ↗ · Crea manifesto ↗ · Ambito e conteggi del set di dati →\n\nAppendice E — Caso di studio\nArchiSteamFarm e la clausola sull'automazione\n\nUno strumento open source per il “card-farming” che, secondo le sue stesse FAQ, funziona su milioni di account, in contrasto con la clausola del Contratto di abbonamento (§ 4.C) che vieta l’automazione. I meccanismi — ciò che una \"farm\" deve acquistare da Valve prima di poter produrre qualsiasi cosa, perché ogni modalità di incasso di una carta viola la licenza, i precedenti in materia di applicazione delle norme e chi modera l'economia delle carte — sono illustrati in dettaglio in Allegato V ↗.\n\nIl Contratto di abbonamento Steam, al § 4.C, recita:\n\n\"Non è consentito utilizzare in alcun modo script, bot, macro o altri sistemi non controllati dall'uomo (\"Automazione\") per interagire con i Contenuti e i Servizi su Steam.\" — Steam Contratto di abbonamento § 4.C (versione attuale) ↗ archiviato 2026-09-18 ↗\n\nValve garantisce il rispetto di questa clausola. Lo fa molto bene. Le domande frequenti su ArchiSteamFarm (ASF) — uno strumento open source che, secondo la sua stessa documentazione, funziona su più di qualche milione di account Steam dalla sua prima versione, rilasciata oltre 11 anni fa, riporta tre Steam messaggi dell’assistenza che hanno comportato il ban permanente degli utenti che gestivano reti di bot. Valve ha individuato le reti, le ha identificate e le ha smantellate. La questione rilevante non è quindi se Valve sia in grado di rilevare l’automazione su larga scala.\n\nIl sito ufficiale del progetto ArchiSteamFarm Domande frequenti affronta direttamente il rischio di un divieto:\n\n\"Si tratta di un'eventualità estremamente improbabile, considerando che ASF è utilizzato su oltre qualche milione di account Steam sin dal suo primo rilascio, avvenuto più di 11 anni fa — ma rimane comunque una possibilità, a prescindere dalla probabilità effettiva.\"\n\n\"Valve riconosce chiaramente l’esistenza dei 'Steam fannulloni', come affermato qui, quindi, se me lo chiedessi, sono abbastanza sicuro che, se non fossero d’accordo con loro, avrebbero già fatto qualcosa invece di sottolineare che potrebbero causare problemi dal punto di vista VAC. La parola chiave in questo contesto è “idler Steam”, ad esempio ASF, e non gli “idler” legati ai giochi.\"\n\n— ArchiSteamFarm Domande frequenti, JustArchiNET. Fonte: Wiki di GitHub ↗ · verificato alla lettera 2026-09-22\n\nNella stessa sezione delle domande frequenti, alla domanda \"Qualcuno è stato bannato per questo?\" si risponde con Sì, e riporta ciò che Steam Support ha scritto a tre di loro:\n\n1,000+ bot · account sospeso per attività di trading\n\"Sembra che questo account sia stato utilizzato per gestire una rete di account bot. L'uso di bot costituisce una violazione del Contratto con l'abbonato Steam.\"\n\nOltre 170 bot · banditi definitivamente, Saldi invernali 2017\n\"Questo account è stato utilizzato per raccogliere illegalmente carte da collezione su Steam, nonché per svolgere attività correlate, non solo di natura commerciale. L'account è stato bloccato in modo definitivo e l'assistenza di Steam non può fornire ulteriore supporto in merito a questa questione.\"\n\nOltre 120 bot · banditi definitivamente\n\"Questo e altri account sono stati utilizzati per sovraccaricare la nostra infrastruttura di rete, il che costituisce una violazione delle Steam norme di condotta online.\"\n\n— Steam Messaggi di supporto riportati nella ArchiSteamFarm sezione delle FAQ, alla voce \"Qualcuno è stato bannato per questo?\". Fonte ↗ · verificato alla lettera 2026-09-22\n\nMetti i due documenti uno accanto all’altro. Un utente privato con 1,000 bot di farming viene identificato, informato che “l’uso di bot costituisce una violazione del Steam Accordo con l’Abbonato” e rimosso definitivamente. Le piattaforme commerciali citate in questo dossier gestiscono account automatizzati Steam come attività principale, su scala ben più ampia, e effettuano l’autenticazione tramite l’OpenID di Valve ad ogni accesso — e per nessuna di esse è stato pubblicato alcun registro relativo alle misure applicative adottate nei confronti dei singoli operatori. La clausola funziona. La domanda è: a chi è rivolta?\n\nL'ASF non è accusata di nulla in questa sede, e la sua interpretazione della posizione di Valve è personale — l'autore afferma chiaramente che «l'ASF non è autorizzata da Valve». Lo strumento viene utilizzato qui come strumento di misurazione: dimostra che Valve rileva le reti di bot, le identifica per nome e le bandisce in modo permanente. Valve può chiudere la questione con una sola frase, pubblicando quali automazioni commerciali autorizza e il resoconto, operatore per operatore, di ciò che ha fatto riguardo alle altre.\n\nIn che misura il \"card farming\" incide sui ricavi di Valve\n\nLe carte collezionabili ottenute tramite farming vengono vendute sul Mercato della Comunità Steam, che applica una commissione complessiva di circa 15% su ogni vendita completata all’interno del Mercato; l’account deve aver speso $5.00 USD su Steam prima di poter ricevere una carta; inoltre, per ottenere le carte è necessario possedere il gioco o effettuare acquisti in-game. Qui non viene stimato alcun dato aggregato sui ricavi: la portata operativa è indicata solo come riportato nelle FAQ di ASF. Le FAQ riportano inoltre Valve elementi distintivi \"Steam pulegge folli\" (raccolta di carte) da \"giocatori inattivi\"; vedi il Domande frequenti sull'ASF ↗. Le modalità operative sono illustrate in dettaglio in Allegato V — la scala e la trappola dell'uso commerciale.\n\nOggettoArchiSteamFarm — raccolta automatizzata di carte\nScala indicataMilioni di account (secondo le FAQ dell’ASF — il numero esatto di account attivi non è stato verificato)\nContati, non citati10,880,610 voci API totali nel gruppo Steam proprio di ASF (5,360,499 senza limitazioni, come mostra Steam) — il termine “milioni” nelle FAQ non è una storia, è un conteggio. 88.97% non comportano alcun Steam divieto di alcun tipo. Il censimento completo dei divieti ↗\nInformazioni riportate nella documentazione dello strumento stesso\nASF effettua l'accesso agli account in modalità headless e lascia i giochi inattivi in attesa del rilascio delle carte senza avviare il client Steam (come indicato nella documentazione del progetto).\nLa sezione FAQ sostiene che Valve sia a conoscenza dei \"Steam fannulloni\" e che \"se non fossero d'accordo con loro, avrebbero già fatto qualcosa\".\nNon sono stati segnalati interventi mirati da oltre 11 anni (secondo le FAQ); le vendite con carta effettuate all’interno del Community Market comportano una commissione complessiva di circa 15% a carico di Steam.\nLa sezione FAQ indica un limite massimo raccomandato di dieci account per operatore e lo attribuisce a Valve: «Questa raccomandazione si basa su linee guida interne Valve, oltre che sui nostri suggerimenti». Nessuna linea guida di questo tipo è stata pubblicata da Valve.\nLimite tecnico, secondo la stessa FAQ: \"è possibile gestire fino a 100-200 bot con un unico indirizzo IP e una singola istanza ASF\".\nIl tempo di gioco generato artificialmente viene registrato da Valve — «di solito viene aggiornato ogni 30 minuti circa» — e il paragrafo § 4.C elenca la «falsificazione delle statistiche di gioco (ad esempio, vittorie o sconfitte gonfiate, XP, tempo di gioco)» tra gli atti vietati.\nFonti\nWiki ufficiale delle domande frequenti (FAQ) di JustArchi ASF ↗ ArchiSteamFarm repository ↗ archiviato 2026-09-24 ↗\nLa clausola sull’automazione è esplicita; le FAQ dell’ASF affermano da anni che lo strumento è in uso su milioni di account; non sono state segnalate azioni mirate contro di esso. Il divario tra la norma e la sua applicazione è un dato di fatto; la ragione di tale divario non viene qui chiarita.\nMostra completaL'economia delle carte: il processo, la portata, la licenza e chi la modera ↗Cosa deve acquistare un’azienda agricola da Valve prima di poter produrre una singola carta; le due righe del § 4.C che definiscono il “card farming” in base ai suoi effetti; perché ogni modo di incassare una carta viola la licenza Valve mentre Valve applica una commissione all’ingresso; il registro delle misure applicative, compresa l’ondata VAC del giugno 2025 e il divieto a catena basato sul numero di telefono condiviso; e i dipendenti Valve e i moderatori della comunità che gestiscono i servizi di scambio di carte e la lista dei ban intorno a Steam.Il censimento dei divietiNon abbiamo chiesto a Valve quanto fosse grande la fattoria. L'abbiamo misurata. ↗10,880,610 account totali (con limitazioni e senza limitazioni) letti dal gruppo Steam di ArchiSteamFarm, a cui il software si aggiunge automaticamente per impostazione predefinita al primo avvio, a meno che l’utente non deselezioni l’impostazione di adesione al gruppo (includendo sia le farm di bot commerciali sia i giocatori regolari che hanno lasciato l’impostazione predefinita attiva). 88.97% non presentano alcun tipo di Steam; dei 11% che ne hanno, 99.8% sono ban comunitari puramente formali che non impediscono in alcun modo il trading. Dopo un controllo incrociato con i SteamRep, 67.77% dei truffatori elencati tornano liberi una volta che i ban anti-cheat vengono messi da parte. Con analisi per data di registrazione, area geografica e durata della permanenza nel gioco: la vera portata, misurata, non raccontata.\n\nAppendix F — Working ledger\n\nRules ledger: clauses against recorded platforms\n\nScegli una regola; il registro elenca le piattaforme registrate associate a essa, con il loro dominio principale, l’host di autenticazione dichiarato e il risultato del filtro dei link salvato. Un sito web bloccato, un altro dominio per l’accesso: segui la regola fino al percorso rimanente.\n\n175record collegati\na questa regola\n174 domini primari0 Riferimenti a C&D\nESTRATTO DELLA NORMA / SSA § 2.G\nUso commerciale e addebito sull'account\n“…exploit the Content and Services or any of its parts for any commercial purpose, except as expressly permitted elsewhere in this Agreement (including any Subscription Terms or Rules of Use).”\nSEGUI I RECORD\nRegistro della piattaforma 175\nI dati in scala sono stime delle fonti\n\n175 dei record di \"175\"\n\nServizio / gruppo di riferimento\tDominio principale / registro\tDominio di autenticazione osservato / età\tScala / risposta registrata\n\nCasino\n\tcsgoempire.com\n11.3 yearsRegistered 2015-06-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgoempirelogin4.com\n6.2 yearsRegistered 2020-07-20\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustreaper.com\n23.2 yearsRegistered 2003-06-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustreaper.com\n23.2 yearsRegistered 2003-06-24\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustly.com\n12.4 yearsRegistered 2014-05-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustly.com\n12.4 yearsRegistered 2014-05-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette Casino\n\tcsgofast.com\n11.5 yearsRegistered 2015-03-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsteam-login.authtofast.com\n83 daysRegistered 2026-06-30\nRDAP ↗ · authtofast.com (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tduelbits.com\n6.6 yearsRegistered 2020-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nswitchflips.com\n6.4 yearsRegistered 2020-04-21\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opener\n\tfarmskins.com\n10.5 yearsRegistered 2016-03-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsteam.kobal.cc\n9.7 yearsRegistered 2017-01-07\nRDAP ↗ · kobal.cc (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgoluck.com\n9.3 yearsRegistered 2017-05-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgoluck.com\n9.3 yearsRegistered 2017-05-18\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tinsane.gg\n7.5 yearsRegistered 2019-04-02\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.insane.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcs2skin.com\n3.5 yearsRegistered 2023-03-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncs2skin.com\n3.5 yearsRegistered 2023-03-06\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tjuice.gg\n7.9 yearsRegistered 2018-10-19\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nletmeinjuice.com\n2.4 yearsRegistered 2024-04-15\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tggdrop.com\n8.6 yearsRegistered 2018-02-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nggauth.com\n3.4 yearsRegistered 2023-05-03\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Casino\n\thowl.gg\n9.5 yearsRegistered 2017-03-16\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhowl.uno\n41 daysRegistered 2026-08-11\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tchicken.gg\n5.7 yearsRegistered 2021-01-11\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nchicken.gg\n5.7 yearsRegistered 2021-01-11\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgocasino.gg\n2.6 yearsRegistered 2024-02-17\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.csgocasino.gg\n2.6 yearsRegistered 2024-02-17\nWHOISFREAKS ↗ · csgocasino.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Casino\n\thunt.gg\n6.9 yearsRegistered 2019-11-04\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.hunt.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Battles\n\tcsbattle.com\n9.8 yearsRegistered 2016-12-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsbattle.com\n9.8 yearsRegistered 2016-12-10\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskinrave.gg\n3.1 yearsRegistered 2023-08-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinrave.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsdouble.gg\n261 daysRegistered 2026-01-03\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsdouble.gg\n261 daysRegistered 2026-01-03\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustchance.com\n8.0 yearsRegistered 2018-10-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhgfuihd.com\n7.6 yearsRegistered 2019-01-27\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Automation\n\tcobaltlab.tech\n3.5 yearsRegistered 2023-03-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncobaltauth.com\n1.7 yearsRegistered 2025-01-07\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\traided.gg\n171 daysRegistered 2026-04-03\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.raided.gg\n171 daysRegistered 2026-04-03\nIP2WHOIS ↗ · raided.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustneo.gg\n1.3 yearsRegistered 2025-06-20\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustneo.gg\n1.3 yearsRegistered 2025-06-20\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tsplits.gg\n3.7 yearsRegistered 2023-01-23\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsplits.gg\n3.7 yearsRegistered 2023-01-23\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Upgrader\n\tupgrader.pro\n1.2 yearsRegistered 2025-07-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nupgauth.space\n38 daysRegistered 2026-08-14\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskin.fans\n8.2 yearsRegistered 2018-07-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skinfans.com\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\thotpizza.one\n1.8 yearsRegistered 2024-12-07\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhotpizza.one\n1.8 yearsRegistered 2024-12-07\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tg4skins.com\n10.1 yearsRegistered 2016-08-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.g4s.to\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2royal.com\n4.1 yearsRegistered 2022-08-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ntf2auth.com\n5.2 yearsRegistered 2021-07-27\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2hunt.com\n8.7 yearsRegistered 2018-01-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrstspcl.com\n6.1 yearsRegistered 2020-08-08\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2.bet/coinflip\n8.4 yearsRegistered 2018-05-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ntf2.bet\n8.4 yearsRegistered 2018-05-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\topenstars.gg\n131 daysRegistered 2026-05-13\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nopenstars.gg\n131 daysRegistered 2026-05-13\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tskins.com\n25.1 yearsRegistered 2001-08-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skins.com\n25.1 yearsRegistered 2001-08-08\nRDAP ↗ · skins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\twhite.market\n9.6 yearsRegistered 2017-03-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwhite.market\n9.6 yearsRegistered 2017-03-01\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tmoon.market\n7.6 yearsRegistered 2019-02-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmoon.market\n7.6 yearsRegistered 2019-02-27\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tcsfloat.com\n5.2 yearsRegistered 2021-07-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgofloat.com\n11.0 yearsRegistered 2015-09-29\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tskin.land\n4.7 yearsRegistered 2022-01-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skin.land\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\thaloskins.com\n2.8 yearsRegistered 2023-12-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhaloskins.com\n2.8 yearsRegistered 2023-12-10\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCorporate Market\n\tbuff.163.com\n29.0 yearsRegistered 1997-09-15\nRDAP ↗ · 163.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\nbuff.163.com\n29.0 yearsRegistered 1997-09-15\nRDAP ↗ · 163.com (parent)\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\tmarket.csgo.com\n26.6 yearsRegistered 2000-02-07\nRDAP ↗ · csgo.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\ndota2.net\n14.9 yearsRegistered 2011-10-29\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRegulated Market\n\tskinport.com\n8.0 yearsRegistered 2018-09-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinport.app\n6.3 yearsRegistered 2020-06-20\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMarketplace/Swap\n\tskinflow.gg\n3.8 yearsRegistered 2022-11-26\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinflow.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tskin.place\n6.0 yearsRegistered 2020-09-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skin.place\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tskinsmonkey.com\n5.7 yearsRegistered 2021-01-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinsmonkey.com\n5.7 yearsRegistered 2021-01-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCorporate Market\n\tskinbaron.de\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinbaron.com\n10.7 yearsRegistered 2015-12-22\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Market\n\trust.tm\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\ndota2.net\n14.9 yearsRegistered 2011-10-29\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tpirateswap.com\n6.0 yearsRegistered 2020-09-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nlogin.pirateswap.com\n6.0 yearsRegistered 2020-09-22\nRDAP ↗ · pirateswap.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Marketplace\n\tmannco.store\n8.6 yearsRegistered 2018-03-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmannco.store\n8.6 yearsRegistered 2018-03-02\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tskinswap.com\n9.9 yearsRegistered 2016-11-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinswap.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\texeskins.com\n2.1 yearsRegistered 2024-08-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nexeskins.com\n2.1 yearsRegistered 2024-08-14\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tbalticskins.com\n153 daysRegistered 2026-04-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nbalticskins.com\n153 daysRegistered 2026-04-21\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tcs.trade\n8.9 yearsRegistered 2017-11-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncs.trade\n8.9 yearsRegistered 2017-11-14\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\trapidskins.com\n4.5 yearsRegistered 2022-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.rapidskins.com\n4.5 yearsRegistered 2022-03-11\nRDAP ↗ · rapidskins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\ttradeit.gg\n9.1 yearsRegistered 2017-08-21\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nconnect-tradeit.com\n4.6 yearsRegistered 2022-02-23\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\t49skins.com\n3.4 yearsRegistered 2023-04-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.49skins.com\n3.4 yearsRegistered 2023-04-19\nRDAP ↗ · 49skins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tskinvault.gg\n3.4 yearsRegistered 2023-05-06\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinvault.gg\n3.4 yearsRegistered 2023-05-06\nIP2WHOIS ↗ · skinvault.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Trading\n\taim.market\n3.3 yearsRegistered 2023-05-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\naim.market\n3.3 yearsRegistered 2023-05-22\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Sell Portal\n\tskinout.gg\n5.6 yearsRegistered 2021-02-27\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skinout.gg\n5.6 yearsRegistered 2021-02-27\nIP2WHOIS ↗ · skinout.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Trading\n\tntskins.com\n230 daysRegistered 2026-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nntskins.com\n230 daysRegistered 2026-02-03\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Portal\n\tgamerpay.gg\n6.0 yearsRegistered 2020-10-02\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ngamerpay.gg\n6.0 yearsRegistered 2020-10-02\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Scrap Swap\n\tscrap.tf\n14.0 yearsRegistered 2012-09-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nscrap.tf\n14.0 yearsRegistered 2012-09-03\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Cashout\n\tmarketplace.tf\n14.0 yearsRegistered 2012-09-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmarketplace.tf\n14.0 yearsRegistered 2012-09-19\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Cashout\n\tskins.cash\n10.5 yearsRegistered 2016-03-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinscash.live\n6.8 yearsRegistered 2019-12-05\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgo.net\n14.2 yearsRegistered 2012-07-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncn2.easylot.net\n10.0 yearsRegistered 2016-09-03\nRDAP ↗ · easylot.net (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCommunity Hub\n\tcybershoke.net\n6.8 yearsRegistered 2019-11-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.cybershoke.net\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMatchmaker Hub\n\tfastcup.net\n14.6 yearsRegistered 2012-02-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.fastcup.net\n14.6 yearsRegistered 2012-02-16\nRDAP ↗ · fastcup.net (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Analytics\n\tleetify.com\n7.6 yearsRegistered 2019-03-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nleetify.com\n7.6 yearsRegistered 2019-03-01\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Analytics\n\tscope.gg\n7.8 yearsRegistered 2018-12-10\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nscope.gg\n7.8 yearsRegistered 2018-12-10\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tools\n\ttradeupspy.com\n6.5 yearsRegistered 2020-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.tradeupspy.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMarketplace\n\tcs.deals\n9.8 yearsRegistered 2016-12-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.cs.deals\n9.8 yearsRegistered 2016-12-03\nRDAP ↗ · cs.deals (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Price DB\n\tpricempire.com\n6.6 yearsRegistered 2020-01-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\npricempire.com\n6.6 yearsRegistered 2020-01-30\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Blackmarket\n\tFSB Market\n7.2 yearsRegistered 2019-07-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nFSB Market\n7.2 yearsRegistered 2019-07-27\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nReady-Account Hub\n\tz2u.com\n26.9 yearsRegistered 1999-11-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwww.z2u.com\n26.9 yearsRegistered 1999-11-10\nRDAP ↗ · z2u.com (parent)\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Gambling\n\tcsgoroll.com\n11.6 yearsRegistered 2015-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwww.csgoroll.com\nRegistry date unavailableRegistry date unavailable\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\trollbit.com\n11.9 yearsRegistered 2014-11-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrbsnin.com\n3 daysRegistered 2026-09-18\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nLicenced Casino\n\t500.casino\n5.9 yearsRegistered 2020-11-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette/Slots\n\tcsgobig.com\n11.4 yearsRegistered 2015-04-12\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcasedrop.com\n14.8 yearsRegistered 2011-12-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\tbanditcamp.com\n12.2 yearsRegistered 2014-06-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tskinbox.com\n18.8 yearsRegistered 2007-12-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\ttastydrop.com\n6.1 yearsRegistered 2020-08-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette Casino\n\tcsgopolygon.gg\n6.5 yearsRegistered 2020-03-28\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tmagicdrop.ru\n10.3 yearsRegistered 2016-05-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nDice Casino\n\tcsdice.com\n3.8 yearsRegistered 2022-11-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUpgrader Casino\n\tskinodds.com\n1.2 yearsRegistered 2025-06-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgowin.com\n12.0 yearsRegistered 2014-09-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrash Casino\n\tcsgorun.net\n7.3 yearsRegistered 2019-06-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\topenskins.com\n3.6 yearsRegistered 2023-02-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Gambling\n\trustbet.com\n7.6 yearsRegistered 2019-02-07\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgomagic.com\n9.4 yearsRegistered 2017-05-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUpgrader/Contract\n\tcsgobounty.com\n11.5 yearsRegistered 2015-03-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tezskins.com\n27.5 yearsRegistered 1999-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\trustcases.com\n7.2 yearsRegistered 2019-06-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgoreaper.com\n11.1 yearsRegistered 2015-08-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgocases.com\n12.3 yearsRegistered 2014-06-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Upgrader\n\tcsgo-skins.com\n11.2 yearsRegistered 2015-07-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgonet.com\n8.8 yearsRegistered 2017-12-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\twtfskins.com\n9.0 yearsRegistered 2017-10-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Casino\n\tflamecases.com\n10.0 yearsRegistered 2016-09-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tgamedom.com\n11.7 yearsRegistered 2015-01-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Battles\n\tskin.club\n9.0 yearsRegistered 2017-09-04\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsc-auth.net\n7.5 yearsRegistered 2019-04-02\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tdaddyskins.com\n9.9 yearsRegistered 2016-10-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Gambling\n\trustix.gg\n1.7 yearsRegistered 2025-01-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Upgrade\n\tskins.club\n4.2 yearsRegistered 2022-07-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgohouse.org\n146 daysRegistered 2026-04-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskinrave.net\n216 daysRegistered 2026-02-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tbloodycase.gg\n19 daysRegistered 2026-09-02\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nClicker/Upgrade\n\tcsgoclicker.com\n8.3 yearsRegistered 2018-05-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustbet.gg\n4.0 yearsRegistered 2022-09-30\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcs-drop.com\n262 daysRegistered 2026-01-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\thellstore.net\n11.7 yearsRegistered 2015-01-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustloot.com\n354 daysRegistered 2025-10-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgo-case.com\n10.3 yearsRegistered 2016-05-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgogem.com\n9.9 yearsRegistered 2016-10-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\trainbet.com\n8.8 yearsRegistered 2017-11-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nservices.rainbet.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustclash.com\n5.4 yearsRegistered 2021-05-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrash Casino\n\t12cs.fail\n181 daysRegistered 2026-03-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\twww.tf2easy.com\n6.3 yearsRegistered 2020-06-02\nRDAP ↗ · tf2easy.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2blaze.com\n7.6 yearsRegistered 2019-01-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tshuffle.com\n30.1 yearsRegistered 1996-07-31\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tbuff.market\n5.9 yearsRegistered 2020-10-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tavan.market\n8.3 yearsRegistered 2018-05-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Engine\n\tcs.money\n11.0 yearsRegistered 2015-09-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.dota.trade\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tuuskins.com\n2.6 yearsRegistered 2024-01-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Market\n\tyoupin898.com\n6.1 yearsRegistered 2020-08-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tc5game.com\n10.5 yearsRegistered 2016-03-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\twaxpeer.com\n7.3 yearsRegistered 2019-05-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwaxpeer.com\n7.3 yearsRegistered 2019-05-20\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBot Trading\n\tcs.money\n11.0 yearsRegistered 2015-09-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.dota.trade\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUS Marketplace\n\tdmarket.com\n30.2 yearsRegistered 1996-07-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nOfficial Market\n\tsteamcommunity.com/market\n20.3 yearsRegistered 2006-05-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNot an external login site2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Platform\n\tlootfarm.com\n11.9 yearsRegistered 2014-10-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Market\n\trustskins.com\n7.6 yearsRegistered 2019-01-31\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tkrakatoa.com\n26.4 yearsRegistered 2000-05-15\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\tshadowpay.com\n10.1 yearsRegistered 2016-08-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nChinese Powerhouse\n\tigxe.cn\n15.0 yearsRegistered 2011-09-06\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAutomated Swap\n\tswap.gg\n9.6 yearsRegistered 2017-01-29\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCash-out Portal\n\tbitskins.com\n11.2 yearsRegistered 2015-07-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Automation\n\ttf2mart.com\n1.1 yearsRegistered 2025-08-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Auctions\n\tskinbid.com\n10.2 yearsRegistered 2016-06-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Rental\n\tlootbear.com\n8.7 yearsRegistered 2018-01-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Valuation\n\tbackpack.tf\n14.4 yearsRegistered 2012-05-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Botnet\n\tstntrading.eu\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Cashout\n\tskinwallet.com\n18.0 yearsRegistered 2008-09-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nDota 2 Market\n\tdota2market.com\n12.2 yearsRegistered 2014-07-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nServer Network\n\txplay.gg\n5.3 yearsRegistered 2021-06-13\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMatchmaking Portal\n\tesportal.com\n26.8 yearsRegistered 1999-12-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nLATAM Hub\n\tgamersclub.com.br\n11.2 yearsRegistered 2015-06-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tools\n\tepidemic.gg\n4.9 yearsRegistered 2021-11-03\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tcs2stash.com\n3.5 yearsRegistered 2023-03-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tcsgoskins.gg\n6.8 yearsRegistered 2019-12-21\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tsteamanalyst.com\n12.6 yearsRegistered 2014-02-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Exchange\n\tsteamcardexchange.net\n13.3 yearsRegistered 2013-05-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tracker\n\tdotabuff.com\n14.2 yearsRegistered 2012-06-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tracker\n\ttracker.gg\n8.9 yearsRegistered 2017-10-12\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Exchange\n\tfunpay.com\n17.0 yearsRegistered 2009-09-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nGrey Market\n\tplayerauctions.com\n26.3 yearsRegistered 2000-06-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Portal\n\teldorado.gg\n8.0 yearsRegistered 2018-09-12\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Key Market\n\tg2a.com\n24.8 yearsRegistered 2001-12-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Key Market\n\tkinguin.net\n16.8 yearsRegistered 2009-12-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nVirtual Services\n\tg2g.com\n31.1 yearsRegistered 1995-08-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Broker\n\tplayerup.com\n19.3 yearsRegistered 2007-05-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfhub.net\n2.7 yearsRegistered 2023-12-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfaccounts.com\n5.3 yearsRegistered 2021-05-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Shop\n\tbuycsgorank.com\n6.2 yearsRegistered 2020-07-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tcsgosmurfkings.com\n9.3 yearsRegistered 2017-06-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfstore.co\n8.6 yearsRegistered 2018-03-03\nWHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlvlup.com\n9.9 yearsRegistered 2016-11-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlevels.com\n10.6 yearsRegistered 2016-02-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tlevelsteam.com\n79 daysRegistered 2026-07-04\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlevelu.com\n6.0 yearsRegistered 2020-09-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\teloking.com\n12.2 yearsRegistered 2014-07-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\tboosteria.org\n11.9 yearsRegistered 2014-10-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tovergear.com\n14.4 yearsRegistered 2012-04-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tblazingboost.com\n14.2 yearsRegistered 2012-06-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\tdota2boost.com\n2.9 yearsRegistered 2023-10-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tbuyboost.com\n22.4 yearsRegistered 2004-04-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\nL'argomentazione dell'inchiestaNorma selezionata / analisi e commento+\nOnere della prova\n\nL'indagine mette in luce il divario tra le restrizioni sull'uso commerciale e i servizi qui riportati. È necessario classificare ciascuna attività e verificare l'esistenza di un'autorizzazione esplicita prima di considerarla una violazione contrattuale. Le tariffe del Mercato Comunitario non si applicano a tutte le transazioni commerciali esterne.\n\nChe cos’è e che cosa non è un record contrassegnato\n\nUn record viene contrassegnato quando il fascicolo contiene un'osservazione datata che fa rientrare la piattaforma, a prima vista, nell'ambito di applicazione della clausola. Un contrassegno non costituisce una violazione accertata e non è stata emessa alcuna autorizzazione espressa Valve per nessuna delle piattaforme qui elencate. Qualora una piattaforma sia in possesso di un'autorizzazione, la sua pubblicazione risolve la segnalazione.\n\nFonti e metodologiaStime, definizioni e ambito di applicazione+\n\nI conteggi sopra riportati si riferiscono alla regola selezionata. I tipi di record raggruppano ciascuna piattaforma una sola volta; i tag completi sono riportati nei dettagli della piattaforma. La ricerca e i filtri si applicano all'interno di quella regola. Le date di registrazione provengono dallo snapshot salvato su RDAP / WHOIS. I sottodomini utilizzano la data di creazione del dominio principale. L’anzianità di per sé non costituisce prova di funzionamento continuo né di un percorso di autenticazione. I nomi host di autenticazione attuali provengono dalle richieste OpenID salvate, con un timestamp UTC; i controlli non risolti non riutilizzano le etichette legacy. L’osservatore si interrompe prima dell’accesso a Steam e non verifica lo stato del filtro dei link su Steam. Scarica le osservazioni sul percorso ↗ Scarica i risultati del registro ↗\n\nEsplora l'archivio dei sorgenti ↗\nAppendice G — Da un modello di rifiuto al documento sottostante\nGuida operativa DSAR: richiedere le prove\n\nRicorrere all’articolo 15 del GDPR per richiedere i dati personali relativi alla creazione della chiave API, al recupero dell’account e all’accesso all’assistenza. Una registrazione conservata può consentire di verificare chi abbia avviato un’azione e su quali elementi si sia basata la piattaforma.\n\n01\nConserva la tua cronologia.\n\nSalvare le notifiche relative all'account, i ticket, gli ID delle transazioni e le date in UTC. Proteggere l'account e verificare le opzioni di recupero disponibili per il gioco e la transazione.\n\nSteam Informazioni sulla protezione commerciale ↗\n02\nRichiedi i tuoi dati conservati.\n\nRichiedi i timestamp, gli indirizzi IP di origine, gli eventi relativi al ciclo di vita delle chiavi, le conferme di sicurezza e le azioni di ripristino relative all'account. Includi gli eventi relativi all'accesso da parte del supporto tecnico e i destinatari, qualora tali dati ti riguardino.\n\n03\nConserva la ricevuta di consegna.\n\nUtilizzare il canale di contatto per la privacy di Valve. Il termine di risposta standard è di un mese; un’eventuale proroga necessaria fino a un massimo di altri due mesi deve essere motivata entro il primo mese.\n\nValve percorso di contatto per la privacy ↗ archiviato 2026-09-21 ↗\n04\nConfronta le risposte.\n\nConfronta i registri con la tua cronologia. Chiedi spiegazioni per le omissioni, quindi, se necessario, avvaliti della procedura di reclamo presso l’autorità di vigilanza. Conserva la risposta esattamente così come l’hai ricevuta.\n\nAmbito di applicazione / Articolo 15\n\nL'accesso riguarda i dati personali conservati, compresi quelli contenuti nei registri. Non garantisce l'accesso a tutti i documenti interni, alle registrazioni ricostruite o ai dati non censurati relativi a terzi. Richiedete una copia leggibile e le motivazioni alla base di eventuali limitazioni.\n\nLinee guida dell’EDPB in materia di accesso, §§ 2, 4–6 ↗ · Articoli 12, 15 e 77 del GDPR ↗ archiviato 2026-09-20 ↗\n\nRichiesta di accesso ai dati personaliGDPR / Articolo 15\nSicurezza dell'account e registri di accesso\n\nSostituisci i campi tra parentesi prima di inviare il modulo.\n\nTo: Valve Privacy Team\nSubject: Article 15 GDPR request — account security records\n\nAccount / SteamID: [YOUR ACCOUNT IDENTIFIER]\nRelevant period (UTC): [START] to [END]\nRelated support tickets: [TICKET REFERENCES]\n\nI request a copy of the personal data concerning me that you retain for this period, including:\n\n1. API-key registration, confirmation, use and revocation events, with available timestamps, source IP addresses, registered domains, device or user-agent information and non-secret key identifiers.\n\n2. Recorded account-recovery actions, password/email/phone changes, Steam Guard removals or resets, confirmation events and the account-related evidence relied on to authorize those actions.\n\n3. Personal data in support-access and administrative-action logs concerning my account, including available dates, purposes, actions and the support entity involved, subject to applicable rights of others.\n\n4. Account-related records used to determine any sanction, and available records of my complaints, reviews and responses.\n\nPlease also provide the applicable processing purposes, categories, recipients, retention periods or criteria, and available information about sources where data were not obtained from me.\n\nWhere processing relies on my consent, please provide the retained record of the consent relied upon and the wording presented at that time.\n\nPlease provide an intelligible electronic copy with time zones and field definitions. Please do not include active credentials or secret tokens. If any requested data are not held, please say so. For any withheld data, please identify the scope and legal basis of the restriction and provide the remainder.\n\nPlease acknowledge receipt and respond within the applicable Article 12 period, explaining any necessary extension. I also ask you to preserve relevant existing records while this request is handled.\n\nName: [YOUR NAME]\nDate: [DATE]\nCosa può garantire un indirizzo IP di un data center\nUna discrepanza costituisce un indizio su cui indagare.\n\nUna richiesta di chiave API proveniente dalla rete di un data center, come nell’esempio del provider di hosting citato in questa indagine, può risultare rilevante se confrontata con i registri di accesso, le conferme e la cronologia dell’utente. Un indirizzo IP da solo non identifica l’autore dell’azione né vanifica automaticamente ogni difesa. La prova che un soggetto ostile abbia fornito il consenso registrato potrebbe mettere in discussione l’affidabilità di tale consenso; altre basi giuridiche e questioni relative alla responsabilità richiedono un’analisi a parte.\n\nVedi il provvedimento di divieto conservato e il reclamo relativo al GDPR →\nAppendice H — Analisi dell'archivio di Wayback Machine · Statistiche di supporto pubblicate\nVolume di assistenza. Tempi di risposta pubblicati.\nContesto e limiti della fonte\n\nValve pubblica quotidianamente le statistiche relative all'assistenza su store.steampowered.com/stats/support. Gli archivi di Wayback Machine conservano istantanee storiche di questa pagina dal 2018 al 2026. Il rapporto tra volume e numero di addetti che emerge da questi dati non è compatibile con una revisione manuale di ogni singolo ticket nei tempi di risposta pubblicati.\n\nConfronta i dati di supporto archiviati di Valve nelle varie istantanee salvate. La metodologia spiega cosa questi dati possono e non possono misurare.\n\nVolume rispetto al tempo di risposta pubblicato (2018 → 2026)\nDue code presso un unico sportello di assistenza, come si evince da 21 schermate archiviate.\n\nValve pubblica i dati relativi all'assistenza in tempo reale su store.steampowered.com/stats/support. Ciascun punto riportato di seguito corrisponde al limite inferiore Valve stesso, così come appariva su quella pagina il giorno in cui Internet Archive ne ha effettuato l'archiviazione — non si tratta di una nostra stima. Entrambe le serie rappresentano la stessa misura nella stessa unità, pertanto devono essere riportate su un unico asse e possono essere confrontate direttamente tra loro.\n\nRichieste di rimborso — denaro Valve in possessoSicurezza e recupero dell'account — l'account che hai perso\n0 h\n2 h\n4 h\n6 h\n8 h\n10 h\nno captures · 38 months\n2019\n2020\n2021\n2022\n2023\n2024\n2025\n2026\n8 h 44 m\naccount recovery\n52 m\nrefunds\n15 m — one capture only\n49–55 minIl limite minimo di rimborso in ogni rilevamento dal febbraio 2018 all'agosto 2026. Nell'arco di otto anni e mezzo varia di meno di sei minuti, mentre il volume giornaliero dei rimborsi varia di un fattore pari a nove.\n2,4 h → 8,7 hIl limite inferiore per il recupero dell'account si attesta intorno alle 2,4 ore in tutte le rilevazioni fino a dicembre 2022, tranne una. Nelle tre rilevazioni del 2026, Valve riporta valori pari a 10,9 h, 5,8 h e 8,7 h.\n×2,8 → ×13Quanto sia più lento il rimborso rispetto ai risarcimenti, secondo i dati pubblicati dallo stesso Valve. La situazione rimane stabile per cinque anni, poi il divario si allarga: la coda che ha subito un rallentamento è quella in cui è l’utente, e non Valve, a dover sostenere le spese.\n\nFonte: 21 copie d'archivio di Wayback Machine relative a store.steampowered.com/stats/support, da 2018-02-03 a 2026-08-10; estrazione in VALVE_EVIDENCE_PACK/databases/steam_support_stats_history.json. Leggere i limiti indicati dai grafici: il grafico rappresenta il inferiore limite dell'intervallo Valve stampe. Il limite superiore pubblicato è peggiore su entrambe le linee: i rimborsi variavano da 1,5 ore a 1,5 giorni, il recupero da 7,0 ore a 3,6 giorni. Due schermate sono state archiviate in un’edizione localizzata della stessa pagina Valve — 2018-11-03 in ceco, 2020-03-25 in francese — e sono contrassegnate con (cs) e (fr) nella tabella; i relativi dati sono riportati qui con le denominazioni delle unità di misura tradotte e i numeri così come pubblicati, mentre le stringhe originali sono conservate nel file di estrazione. Ogni acquisizione ha pubblicato un tempo di risposta per entrambe le code e nessun punto su nessuna delle due linee è stato interpolato. L’unico dato relativo al recupero di 15 minuti, pari a 2020-10-21, è contrassegnato sul grafico e lasciato tale: compare in una sola acquisizione e nessun’altra acquisizione si trova entro un ordine di grandezza da esso. Non esiste alcuna acquisizione tra 2022-12-08 e 2026-02-01; quella lacuna di 38 mesi nella registrazione è ombreggiata e non vi è alcuna linea tracciata su di essa. Questi dati descrivono i tempi di risposta pubblicati. Non mostrano cosa avvenga all’interno di un ticket e Valve non ha pubblicato alcun dato relativo al numero di addetti a cui rapportarli.\n\nApri ogni acquisizione sotto forma di tabella\nOgni acquisizione archiviata, così come pubblicata\nAcquisizione\tRimborsi / al giorno\tRisposta relativa al rimborso\tRecupero / giorno\tMisure di recupero\n2018-02-03\t98,788\tDa 50,12 minuti a 1,52 ore\t25,662\tDa 2,51 ore a 1,80 giorni\n2018-05-07\t60,494\tDa 53,83 minuti a 1,47 giorni\t24,226\tDa 2,45 ore a 2,22 giorni\n2018-08-02\t69,084\tDa 50,27 minuti a 1 ora e 59 minuti\t28,953\tDa 2,44 ore a 22,17 ore\n2018-11-03 (cs)\t63,410\tDa 49,28 minuti a 1,54 ore\t33,910\tDa 2,42 ore a 1,31 giorni\n2019-02-01\t76,305\tDa 50,13 minuti a 1,52 ore\t35,164\tDa 2,44 ore a 2,04 giorni\n2019-05-18\t78,951\tDa 51,03 minuti a 3,12 ore\t27,514\tDa 2,46 ore a 20,39 ore\n2019-09-07\t78,941\tDa 50,65 minuti a 1,66 ore\t28,812\tDa 2,42 ore a 13,59 ore\n2019-12-13\t69,589\tDa 50,77 minuti a 1 ora e 55 minuti\t25,322\tDa 2,45 ore a 1,13 giorni\n2020-03-25 (fr)\t139,278\tDa 49,45 minuti a 1 ora e 53 minuti\t32,302\tDa 2,48 ore a 3,62 giorni\n2020-06-26\t278,504\tDa 48,98 minuti a 2,29 ore\t20,343\tDa 2,39 ore a 6,99 ore\n2020-10-21\t107,633\tDa 50,80 minuti a 1,54 ore\t20,688\tDa 15,33 minuti a 8,62 ore\n2021-03-20\t158,956\tDa 50,80 minuti a 1,64 ore\t25,760\tDa 2,34 ore a 11,62 ore\n2021-06-26\t547,907\tDa 51,93 minuti a 6,73 ore\t29,728\tDa 2,40 ore a 15,63 ore\n2021-10-10\t170,103\tDa 51,88 minuti a 3,25 ore\t23,989\tDa 2,39 ore a 13,05 ore\n2022-01-31\t354,386\tDa 53,65 minuti a 8,09 ore\t24,391\tDa 2,42 ore a 15,29 ore\n2022-05-09\t172,555\tDa 51,83 minuti a 1,65 ore\t23,289\tDa 2,41 ore a 16,90 ore\n2022-09-05\t153,453\tDa 53,67 minuti a 4 ore e 15 minuti\t23,594\tDa 2,45 ore a 1,22 giorni\n2022-12-08\t181,075\tDa 54,83 minuti a 6,67 ore\t27,111\tDa 2,46 ore a 18,89 ore\n2026-02-01\t317,762\tDa 50,30 minuti a 1,52 ore\t47,197\tDalle 10.91 alle 21.30\n2026-05-09\t246,776\tDa 50,12 minuti a 1,52 ore\t35,264\tDa 5,81 ore a 15,60 ore\n2026-08-10\t373,244\tDa 52,05 minuti a 2,07 ore\t45,319\tDa 8,73 ore a 16,52 ore\nOSSERVAZIONE CHIAVE:\nDa una parte all'altra 21 archivi di Wayback nell’intervallo da 2018-02-03 a 2026-08-10, le richieste di rimborso giornaliere variavano da 60,494 (maggio 2018) a 547,907 (Giugno 2021) — a Spread di 9,1×. Il dato relativo al 2026 è pari a 373,244 (+278% rispetto al dato registrato a febbraio 2018).\nNel corso di quegli stessi nove anni, il limite inferiore pubblicato per i tempi di risposta ai rimborsi non è mai sceso al di sotto di un 49–55 minuti banda: un movimento complessivo inferiore a sei minuti, mentre il carico di lavoro sottostante è aumentato di nove volte.\nSe una persona dedicasse anche solo 5 secondi alla lettura di ogni biglietto, l’elaborazione di 373,244 biglietti al giorno (dato attuale) richiederebbe 22 agenti in servizio 24 ore su 24, 7 giorni su 7 solo per aprirle e chiuderle; al picco (547,907, giugno 2021) tale valore sale a 32.\nSe il tempo di risposta pubblicato riflettesse il tempo di gestione per singolo ticket (~52 min/ticket), il numero di dipendenti necessari per gestire contemporaneamente tali richieste sarebbe dell’ordine di 13,500 agenti al volume attuale e ~20,000 al picco. Non è stato individuato alcun dato di riferimento relativo al numero di dipendenti a supporto di Valve; in questa sede non se ne ipotizza alcuno.\nDi seguito: il rapporto tra volume e numero di addetti non è compatibile con una revisione umana per ogni segnalazione nei tempi di risposta pubblicati. I dati sono coerenti con una prima fase di analisi in gran parte automatizzata; non viene resa nota la percentuale di segnalazioni sottoposte a revisione umana.\nPerché questo è importante ai fini della conformità al GDPR\n\nL’articolo 22 del GDPR vieta i processi decisionali individuali esclusivamente automatizzati che producono effetti giuridici significativi, senza prevedere il diritto a una revisione umana su richiesta. Se le decisioni relative all’assistenza (chiusura dei ticket, azioni sull’account, rifiuto delle richieste di dati) vengono prese interamente da script automatizzati, ogni decisione di questo tipo che «incida in modo significativo» sull’utente potrebbe violare l’articolo 22.\n\nBiglietto HT-2YBP-F7JP-D4VB (Sezione 18) è stata chiusa dopo tre giorni con un rinvio standard, senza alcun approfondimento in merito alla base giuridica citata. Dal ticket non è possibile stabilire se qualcuno l’abbia esaminata; si tratta di una questione che l’autorità di controllo può sottoporre a Valve ai sensi dell’articolo 22 e dell’articolo 15, paragrafo 1, lettera h).\n\nFonte: istantanee di Wayback Machine del sito store.steampowered.com/stats/support (2018-02-03, 2021-06-26, 2026-08-10) — dati estratti in VALVE_EVIDENCE_PACK/databases/steam_support_stats_history.json (21 istantanee, 2018–2026). Nota: il tempo di risposta di \"~52 min\" rappresenta il limite inferiore per la categoria dei rimborsi; il tempo di risposta relativo alla sicurezza dell’account variava da 2,4 a 16,5 ore nelle stesse istantanee. 2021-06-26 rappresenta il picco storico (547,907 richieste di rimborso), non un punto medio monotono — il volume è aumentato di circa 6 volte nel periodo 2020–2021, per poi diminuire parzialmente prima di risalire a 373.000 nel 2026.\nAppendice I — Ambito del set di dati · conteggi riproducibili\nConta i record. Verifica l'ambito.\nContesto e limiti della fonte\n\nContate i record, poi verificate le affermazioni: ogni dato riportato di seguito può essere ricavato nuovamente dai file pubblicati.\n\nEsaminare i set di dati sottostanti, riprodurre i conteggi e distinguere le righe di origine dagli incidenti singoli.\n\nIl file CSV principale contiene 40,448 righe. Di questi, 36,516 provengono dal feed \"Discord-AntiScam\" dedicato al phishing. I restanti 3,932 Le righe coprono GitHub, le recensioni, i risultati di ricerca, i contenuti dei forum e altre fonti, fornendo un indice completo degli argomenti segnalati dalla comunità e delle segnalazioni relative alla sicurezza.\n\nAll'interno di quel file CSV, 1,690 righe sono classificate sotto l'etichetta \"Unpatched Security Exploit\", che rappresenta i problemi segnalati dagli utenti in passato e le vulnerabilità rese pubbliche. Per tracciare queste segnalazioni è necessario esaminare la cronologia delle build specifiche di ciascun thread e la cronologia pubblica delle patch.\n\nL'archivio consultabile 16,319-record è una versione separata e curata, dotata di un proprio manifesto, progettata per consentire un'analisi locale accurata delle segnalazioni degli utenti e dei rapporti sugli incidenti.\n\nPer creare una traccia di audit affidabile, ogni registrazione segnalata dagli utenti deve essere verificata alla luce delle tempistiche di compilazione documentate e dei registri storici delle patch.\n\nI record della collezione separata della Parte II 231,829 ID univoci degli annunci, tra cui 33,509 nella categoria delle registrazioni automatiche e 198,320 contrassegnati come trasferimenti non verificati. Lo SHA-256 del file di input corrisponde alla misurazione conservata. Questi conteggi descrivono i tentativi di inserimento in vendita e i trasferimenti osservati piuttosto che i valori delle transazioni finalizzate o i totali verificati dei furti, evidenziando la necessità di disporre dei registri primari della piattaforma per misurare l’esatto impatto economico. Elenco delle misure e degli hash ↗\n\nPadroneggia il CSV ↗ · Elenco degli archivi consultabili ↗ · Controlla i record di origine ↗\n\nAppendice J — Informazioni sulla presente indagine\nValve non pubblica alcun registro delle misure esecutive. Ne abbiamo costruito uno.\n\nIndipendente. Non commerciale. Realizzato esclusivamente sulla base di dati pubblici. Presentato alle autorità di regolamentazione.\n\n88.97%flotta di veicoli automatizzati non interessata — nessun divieto di alcun tipo\n67.77%di 51,732 truffatori condannati che se la cavano senza conseguenze\n$26.8M+spesa minima in negozio per la flotta non soggetta a limiti\n3.6%domini relativi al gioco d'azzardo bloccati dal filtro dei link di Valve\n8 annidegli incidenti di sicurezza documentati\n\nDi cosa si tratta. Un dossier forense sulla piattaforma Steam della Valve Corporation: il suo storico di applicazione delle norme, l’economia basata sul “card-farming”, il quadro giuridico e l’infrastruttura di autenticazione che gli operatori di gioco d’azzardo utilizzano tramite il relay OpenID di Steam. Ogni dato è ricreabile da due fonti: l'API pubblica di Valve e i set di dati pubblicati insieme alla presente indagine.\n\nA chi è rivolto. Le autorità di regolamentazione competenti in materia di Valve — l’autorità di controllo del GDPR per i Paesi Bassi, il FinCEN, la SEC, il coordinatore dei servizi digitali (DSA), l’UOKiK e qualsiasi autorità di polizia che indaghi sui flussi finanziari collegati a Steam. Anche per giornalisti, ricercatori e tutti gli utenti che hanno subito il blocco definitivo dell’account, il rifiuto di un rimborso o il furto di beni in inventario e ai quali è stato comunicato che non è possibile presentare ricorso.\n\nL'unica richiesta. Valve conserva questi dati con la massima fedeltà — motivi del divieto allegati, spazio ID completo, in tempo reale. È in grado di eseguire ogni query contenuta in questo dossier in pochi secondi e ha scelto di non pubblicarne alcuna parte. La domanda per qualsiasi autorità competente è semplice: Perché no?\n\nCiò che gli autori non sostengono. Durante questo lavoro non è stato effettuato alcun accesso a Steam su alcuna piattaforma di terze parti. È l'URL OpenID fornito a stabilire i parametri della richiesta, non un accesso completato. Un dominio registrabile separato non costituisce di per sé una prova di elusione. Le date di registrazione rappresentano i limiti minimi relativi al momento in cui un host avrebbe potuto comparire per la prima volta in una richiesta OpenID; esse non dimostrano un uso continuativo. Gli autori non avanzano affermazioni su ciò che Valve sapeva o intendeva: ogni affermazione relativa a Valve è collegata a un documento pubblico datato o a un’osservazione datata. Laddove non è stato possibile attribuire un’affermazione a un documento di riferimento, essa è stata rimossa.\n\nChi siamo\n\nPhishDestroy — ricercatori indipendenti. Nessun legame con la società Valve o con alcuna delle piattaforme qui menzionate. Un account Steam è stato utilizzato esclusivamente per documentare la richiesta ai sensi del GDPR di cui alla Sezione 18.\n\nAvviso legale\n\nIndagine non commerciale, decentralizzata e di interesse pubblico. Tutti i dati sono forniti “così come sono”, senza alcuna garanzia. La presente pubblicazione non costituisce un accertamento giudiziario.\n\nDI DOMINIO PUBBLICO\nLicenze\n\nTutti i diritti ceduti all’umanità. È consentito riprodurre, adattare e pubblicare il contenuto senza obbligo di attribuzione. Accesso vietato nella regione soggetta alle restrizioni dell’OFAC. Licenza completa e dichiarazione di non responsabilità →",
        "headings": [
          {
            "level": 2,
            "id": "briefing-heading",
            "text": "La regola. Il record. Le domande senza risposta."
          },
          {
            "level": 2,
            "id": null,
            "text": "Lettera aperta alla Commissione per il gioco d'azzardo dello Stato di Washington"
          },
          {
            "level": 3,
            "id": "wsgc-public-address-title",
            "text": "Dieci giorni sono diventati dieci anni.Riaprire il record."
          },
          {
            "level": 2,
            "id": null,
            "text": "Il sito è bloccato. La pagina di accesso invece no."
          },
          {
            "level": 3,
            "id": null,
            "text": "Figura 3.1 — I due percorsi, rappresentati graficamente."
          },
          {
            "level": 3,
            "id": null,
            "text": "La trappola della visione d'insieme: il filtro dei link è solo una messinscena di conformità, non uno scudo"
          },
          {
            "level": 3,
            "id": null,
            "text": "Un dominio principale bloccato, abbinato a un host di autenticazione sbloccato, lascia aperta la rotta di accesso — che rimane aperta per anni."
          },
          {
            "level": 3,
            "id": null,
            "text": "Contesto: Che cos’è Steam e perché è importante in questo contesto"
          },
          {
            "level": 3,
            "id": null,
            "text": "Cosa ha fatto Valve: il blocco dei domini"
          },
          {
            "level": 3,
            "id": null,
            "text": "Che cos’è un dominio proxy"
          },
          {
            "level": 3,
            "id": null,
            "text": "Il punto critico: in ogni richiesta, l’host di autenticazione viene impostato su Steam"
          },
          {
            "level": 3,
            "id": null,
            "text": "Cosa dimostra tutto ciò"
          },
          {
            "level": 3,
            "id": null,
            "text": "All'interno di Steam, l'elenco di Valve è l'unico elenco."
          },
          {
            "level": 3,
            "id": null,
            "text": "Bypass della protezione del filtro dei link"
          },
          {
            "level": 3,
            "id": null,
            "text": "Il browser web Big Picture divulga i cookie di accesso e rivela informazioni sensibili (ciò potrebbe portare al furto dell'account)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Cosa significa questo per un minore che ha un antivirus installato"
          },
          {
            "level": 3,
            "id": null,
            "text": "L'età del dominio.Data dell'osservazione."
          },
          {
            "level": 2,
            "id": null,
            "text": "Un endpoint è stato chiuso. Il tracciamento pubblico ha perso una chiave."
          },
          {
            "level": 3,
            "id": null,
            "text": "L'era precedente al blackout"
          },
          {
            "level": 3,
            "id": null,
            "text": "Dopo il cambiamento"
          },
          {
            "level": 2,
            "id": null,
            "text": "Una sessione. Un accesso più ampio di quanto l'utente possa vedere."
          },
          {
            "level": 3,
            "id": null,
            "text": "1. Autenticazione a più livelli insufficiente"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. Mancanza del principio del privilegio minimo"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. Gestione delle sessioni non funzionante"
          },
          {
            "level": 3,
            "id": null,
            "text": "4. Il blocco a livello di dominio degli host di autenticazione era tecnicamente fattibile"
          },
          {
            "level": 3,
            "id": "integration-paradox-title",
            "text": "Valve viene compilato ogni giorno secondo queste regole. In questo caso, però, la compilazione non è avvenuta secondo tali regole."
          },
          {
            "level": 4,
            "id": null,
            "text": "Ambiti dettagliati di GitHub rispetto alle API Web Valve Steam"
          },
          {
            "level": 2,
            "id": null,
            "text": "Simulatore interattivo di exploit e dirottamento"
          },
          {
            "level": 2,
            "id": null,
            "text": "I punti finali alla base della sequenza."
          },
          {
            "level": 2,
            "id": null,
            "text": "Una casella spuntata. Chi l'ha spuntata?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Come Valve ha finalmente neutralizzato la “sostituzione commerciale” — e perché ci sono voluti 7 anni di soluzioni alternative"
          },
          {
            "level": 4,
            "id": null,
            "text": "Tempo di attesa per avatar e nome (febbraio 2024)"
          },
          {
            "level": 4,
            "id": null,
            "text": "Inversione di tendenza CS2 a 7 giorni (luglio 2025)"
          },
          {
            "level": 4,
            "id": null,
            "text": "Implementazione obbligatoria delle notifiche push su dispositivi mobili per l’API (dicembre 2023)"
          },
          {
            "level": 4,
            "id": null,
            "text": "Banner con l’anzianità e il nome dell’account (2022–2024)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Il loro regolamento. Le piattaforme registrate."
          },
          {
            "level": 3,
            "id": "enforcement-focus-title",
            "text": "Un unico regolamento. Un’applicazione diseguale."
          },
          {
            "level": 4,
            "id": null,
            "text": "Automazione"
          },
          {
            "level": 4,
            "id": null,
            "text": "Uso commerciale"
          },
          {
            "level": 4,
            "id": null,
            "text": "VPN e occultamento della posizione"
          },
          {
            "level": 4,
            "id": null,
            "text": "Occultamento dei link"
          },
          {
            "level": 4,
            "id": null,
            "text": "Chi riesamina la decisione quando il servizio di assistenza chiude il caso?"
          },
          {
            "level": 2,
            "id": null,
            "text": "Un'API di automazione. Una regola contro l'automazione."
          },
          {
            "level": 3,
            "id": null,
            "text": "Il \"mito dello sviluppatore di videogiochi\""
          },
          {
            "level": 4,
            "id": null,
            "text": "La contraddizione dell'automazione"
          },
          {
            "level": 4,
            "id": null,
            "text": "Un ruolo lato server nel flusso commerciale"
          },
          {
            "level": 2,
            "id": null,
            "text": "Dieci giorni richiesti. Dieci anni da rendere conto."
          },
          {
            "level": 3,
            "id": "letter-company",
            "text": "VALVE CORPORATION"
          },
          {
            "level": 3,
            "id": null,
            "text": "Dieci giorni.E poi?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Segui l'host di ritorno specificato."
          },
          {
            "level": 3,
            "id": "washington-record-heading",
            "text": "Due scadenze. Un criterio di applicazione ancora indefinito."
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve concede ai siti di gioco d'azzardo 10 giorni"
          },
          {
            "level": 4,
            "id": null,
            "text": "Washington preme Valve"
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve respinge l'accusa"
          },
          {
            "level": 4,
            "id": null,
            "text": "Le rotte osservate nel settembre 2026"
          },
          {
            "level": 4,
            "id": null,
            "text": "Diciotto mesi dopo la risposta di Valve, l'autorità di regolamentazione continuava a definirla una semplice intenzione."
          },
          {
            "level": 3,
            "id": null,
            "text": "Il decennio del preavviso di 10 giorni: verifica forense sulla sopravvivenza dei 23 siti indicati"
          },
          {
            "level": 4,
            "id": null,
            "text": "Dagli avvisi con 10 giorni di preavviso ai conglomerati offshore: un fatturato multimiliardario"
          },
          {
            "level": 2,
            "id": null,
            "text": "Il nome host è già presente nella richiesta."
          },
          {
            "level": 3,
            "id": null,
            "text": "Precedenti documentati e segnalati"
          },
          {
            "level": 3,
            "id": null,
            "text": "Cosa indica e cosa non indica la data di registrazione"
          },
          {
            "level": 3,
            "id": null,
            "text": "Audit comparativo: standard di conformità API"
          },
          {
            "level": 2,
            "id": "market-thesis-heading",
            "text": "Il divario di prezzo rispetto a 0"
          },
          {
            "level": 2,
            "id": null,
            "text": "Il divario di prezzo è quantificabile."
          },
          {
            "level": 3,
            "id": null,
            "text": "Cosa indica la cifra in dollari"
          },
          {
            "level": 3,
            "id": null,
            "text": "Molti locali indicano un valore in dollari superiore a Steam."
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam è ancora in testa per numero di offerte."
          },
          {
            "level": 3,
            "id": null,
            "text": "L'ecosistema commerciale è sotto gli occhi di tutti."
          },
          {
            "level": 2,
            "id": null,
            "text": "Chi può ripristinare le misure di sicurezza?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Un ticket di recupero che ha disabilitato la sicurezza dell'account e una perdita segnalata pari a $10,000"
          },
          {
            "level": 3,
            "id": null,
            "text": "Oltre l'inventario."
          },
          {
            "level": 3,
            "id": "theft-ledger-title",
            "text": "Valve aprì la porta due volte, a distanza di trentatré mesi l’una dall’altra. Non si chiuse mai."
          },
          {
            "level": 4,
            "id": null,
            "text": "Ciò che il registro rivela e che nessun singolo caso è in grado di fare."
          },
          {
            "level": 3,
            "id": null,
            "text": "La riservatezza deve andare di pari passo con la responsabilità tecnica."
          },
          {
            "level": 2,
            "id": null,
            "text": "Segui i flussi di denaro. Distingui le transazioni."
          },
          {
            "level": 3,
            "id": null,
            "text": "Dove il denaro circola effettivamente."
          },
          {
            "level": 3,
            "id": null,
            "text": "Classificare prima l'attività, poi l'obbligo."
          },
          {
            "level": 3,
            "id": null,
            "text": "Tracciabilità dei proventi, delle informazioni e dell'assistenza."
          },
          {
            "level": 2,
            "id": null,
            "text": "La legge sui servizi digitali: mettere nero su bianco le conoscenze"
          },
          {
            "level": 3,
            "id": null,
            "text": "Una richiesta di dieci giorni."
          },
          {
            "level": 3,
            "id": null,
            "text": "La finestra temporale DSA."
          },
          {
            "level": 3,
            "id": null,
            "text": "La durata richiede una traccia delle notifiche."
          },
          {
            "level": 3,
            "id": null,
            "text": "del fatturato annuo a livello mondiale"
          },
          {
            "level": 2,
            "id": null,
            "text": "Minori: un accesso con Steam non costituisce una verifica dell'età"
          },
          {
            "level": 3,
            "id": null,
            "text": "Identificare l'operatore e i dati."
          },
          {
            "level": 3,
            "id": null,
            "text": "Registra il percorso dall'accesso al deposito."
          },
          {
            "level": 2,
            "id": null,
            "text": "La richiesta. La risposta. Il confronto mancante."
          },
          {
            "level": 3,
            "id": null,
            "text": "I documenti esistono; l'interessato non li ha ricevuti."
          },
          {
            "level": 2,
            "id": null,
            "text": "Il Contratto di abbonamento in contrasto con l'architettura della piattaforma stessa"
          },
          {
            "level": 3,
            "id": null,
            "text": "Il limite massimo di mercato e il divieto di uso commerciale"
          },
          {
            "level": 3,
            "id": null,
            "text": "La vulnerabilità della chiave API come problema di progettazione della piattaforma piuttosto che come negligenza da parte dell'utente"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve riceve il nome host di autenticazione ad ogni accesso"
          },
          {
            "level": 3,
            "id": null,
            "text": "L'andamento dei reclami archiviati"
          },
          {
            "level": 3,
            "id": null,
            "text": "Un tribunale chiamato a valutare questo fascicolo non interpretarebbe la SSA in modo isolato."
          },
          {
            "level": 2,
            "id": null,
            "text": "I risultati. I documenti che richiediamo."
          },
          {
            "level": 2,
            "id": null,
            "text": "Memorandum probatorio — materiale fornito dalla fonte 1"
          },
          {
            "level": 2,
            "id": null,
            "text": "La censura nel file PDF fornito è di natura puramente estetica: il testo oscurato rimane comunque estraibile"
          },
          {
            "level": 2,
            "id": null,
            "text": "Documentazione relativa all’assistenza e alla corrispondenza legale"
          },
          {
            "level": 2,
            "id": null,
            "text": "Documenti primari selezionati"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-01",
            "text": "Chiavi hardware, richieste nel 2016"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-02",
            "text": "Segnalazioni di crash senza un’efficace opzione di rinuncia"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-03",
            "text": "Abuso di ticket di autenticazione segnalato a Valve"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-01",
            "text": "44 acquisti sul mercato oggetto di controversia"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-02",
            "text": "Sospensione definitiva e ricorso inammissibile"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-03",
            "text": "Un ripristino del sistema di recupero e una perdita segnalata pari a $10,000"
          },
          {
            "level": 2,
            "id": null,
            "text": "ArchiSteamFarm e la clausola sull'automazione"
          },
          {
            "level": 2,
            "id": null,
            "text": "Rules ledger: clauses against recorded platforms"
          },
          {
            "level": 3,
            "id": "ledger-title",
            "text": "Uso commerciale e addebito sull'account"
          },
          {
            "level": 3,
            "id": "lw-register-title",
            "text": "Registro della piattaforma 175"
          },
          {
            "level": 4,
            "id": null,
            "text": "Onere della prova"
          },
          {
            "level": 4,
            "id": null,
            "text": "Che cos’è e che cosa non è un record contrassegnato"
          },
          {
            "level": 2,
            "id": null,
            "text": "Guida operativa DSAR: richiedere le prove"
          },
          {
            "level": 3,
            "id": null,
            "text": "Conserva la tua cronologia."
          },
          {
            "level": 3,
            "id": null,
            "text": "Richiedi i tuoi dati conservati."
          },
          {
            "level": 3,
            "id": null,
            "text": "Conserva la ricevuta di consegna."
          },
          {
            "level": 3,
            "id": null,
            "text": "Confronta le risposte."
          },
          {
            "level": 3,
            "id": null,
            "text": "Sicurezza dell'account e registri di accesso"
          },
          {
            "level": 3,
            "id": null,
            "text": "Una discrepanza costituisce un indizio su cui indagare."
          },
          {
            "level": 2,
            "id": null,
            "text": "Volume di assistenza. Tempi di risposta pubblicati."
          },
          {
            "level": 3,
            "id": null,
            "text": "Due code presso un unico sportello di assistenza, come si evince da 21 schermate archiviate."
          },
          {
            "level": 2,
            "id": null,
            "text": "Conta i record. Verifica l'ambito."
          },
          {
            "level": 2,
            "id": null,
            "text": "Valve non pubblica alcun registro delle misure esecutive.\nNe abbiamo costruito uno."
          }
        ],
        "links": [
          "https://dotesports.com/counter-strike/news/csgo-lounge-billion-bets-3896",
          "https://store.steampowered.com/agreement/?l=english",
          "http://web.archive.org/web/20260921022032/https://store.steampowered.com/agreement/?l=english",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-all-results.json",
          "https://blog.counter-strike.net/expresstrade/",
          "http://web.archive.org/web/20260307161538/https://blog.counter-strike.net/expresstrade/",
          "https://wsgc.wa.gov/news/2016/washington-state-gambling-commission-orders-valve-stop-skins-gambling",
          "http://web.archive.org/web/20260520012601/https://wsgc.wa.gov/news/2016/washington-state-gambling-commission-orders-valve-stop-skins-gambling",
          "https://fr.scribd.com/document/328063293/Valve-s-Oct-18th-response-to-Washington-State-Gambling-Commission-s-cease-and-desist",
          "https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921021947/https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921022628/https://steamcommunity.com/linkfilter/?url=https:%2F%2Frollbit.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rbsnin.com.20260921T021120Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rollbit.com.json",
          "http://web.archive.org/web/20260921022740/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fskin.club",
          "http://web.archive.org/web/20260921022842/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fsc-auth.net",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skin.club.json",
          "http://web.archive.org/web/20260921022603/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fhowl.gg",
          "http://web.archive.org/web/20260921022636/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fhowl.uno",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/howl.gg.json",
          "http://web.archive.org/web/20260921022840/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fduelbits.com",
          "http://web.archive.org/web/20260921022901/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fswitchflips.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/duelbits.com.json",
          "http://web.archive.org/web/20260921022758/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgofast.com",
          "http://web.archive.org/web/20260921022847/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fauthtofast.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgofast.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/farmskins.com.20260921T025840Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/steam.kobal.cc.20260921T025844Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/farmskins.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cobaltlab.tech.20260921T041604Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cobaltauth.com.20260921T041608Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/cobaltlab.tech.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgo.net.20260921T041619Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cn2.easylot.net.20260921T041623Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgo.net.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/ggdrop.com.20260921T041637Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/ggauth.com.20260921T041641Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/ggdrop.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rustchance.com.20260921T041703Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/hgfuihd.com.20260921T041706Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rustchance.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skin.fans.20260921T041710Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.skinfans.com.20260921T041713Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skin.fans.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinport.com.20260921T041724Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinport.app.20260921T041728Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skinport.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skins.cash.20260921T041731Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinscash.live.20260921T041735Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skins.cash.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2hunt.com.20260921T041739Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rstspcl.com.20260921T041742Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tf2hunt.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgogem.com.20260922T192355Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/api.csgem.com.20260922T192358Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-2026-09-22.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/gamdom.com.20260922T192326Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/login.gambldom.com.20260922T192330Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/12cs.fail.20260922T192347Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/fail.games.20260922T192351Z.html",
          "http://web.archive.org/web/20260921022953/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgoempire.com",
          "http://web.archive.org/web/20260921022947/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgoempirelogin4.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgoempire.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cs.money.20260921T021131Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.dota.trade.20260921T021134Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/cs.money.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csfloat.com.20260921T041612Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgofloat.com.20260921T041615Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csfloat.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/g4skins.com.20260921T041630Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.g4s.to.20260921T041634Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/g4skins.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/juice.gg.20260921T041644Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/letmeinjuice.com.20260921T041648Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/juice.gg.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/market.csgo.com.20260921T041652Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2.net.20260921T041655Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/market.csgo.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rust.tm.20260921T041659Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rust.tm.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgolounge.com.20260922T192333Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2.net.20260922T192340Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2lounge.com.20260922T192337Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinbaron.de.20260921T041717Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinbaron.com.20260921T041721Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skinbaron.de.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2royal.com.20260921T041746Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2auth.com.20260921T041750Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tf2royal.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tradeit.gg.20260921T041753Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/connect-tradeit.com.20260921T041757Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tradeit.gg.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/upgrader.pro.20260921T041801Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/upgauth.space.20260921T041804Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/upgrader.pro.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-recheck-2026-09-21.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/domain-registration.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wayback-snapshots.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-2026-09-22c.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/master_registry.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/longitudinal-steam-phishing-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-steam-phishing-100.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-coverage-2026-09-22.json",
          "https://blog.csfloat.com/how-floatdb-tracks-items/",
          "http://web.archive.org/web/20260921022415/https://blog.csfloat.com/how-floatdb-tracks-items/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/platform-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/platforms-removed.json",
          "https://hackerone.com/reports/291750",
          "http://web.archive.org/web/20251116185046/https://hackerone.com/reports/291750",
          "https://hackerone.com/reports/1079561",
          "http://web.archive.org/web/20260924181830/https://hackerone.com/reports/1079561",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/hackerone-reports.json",
          "https://phishdestroy.io/steam_dossier/it/steam_enforcement_evidence.html#support-records",
          "https://www.darknavy.org/blog/exploiting_steam_usual_and_unusual_ways_in_the_cef_framework/",
          "https://steamcommunity.com/groups/SteamClientBeta/discussions/0/3365901765276206401/",
          "http://web.archive.org/web/20250804051514/https://steamcommunity.com/groups/SteamClientBeta/discussions/0/3365901765276206401/",
          "https://www.chromium.org/developers/design-documents/safebrowsing/",
          "http://web.archive.org/web/20260821101616/https://www.chromium.org/developers/design-documents/safebrowsing/",
          "https://www.chromium.org/developers/how-tos/api-keys/",
          "http://web.archive.org/web/20260830122831/https://www.chromium.org/developers/how-tos/api-keys/",
          "https://github.com/Homebrew/homebrew-cask/issues/193814",
          "https://testsafebrowsing.appspot.com/",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/domain-registration.json",
          "https://phishdestroy.io/steam_dossier/it/AUTH_AUDIT.md",
          "https://datatracker.ietf.org/doc/rfc6749/",
          "https://docs.cloud.google.com/docs/authentication/api-keys",
          "https://listings.pcisecuritystandards.org/pdfs/PCI_DSS_Resource_Guide_(003).pdf",
          "https://developer.apple.com/news/?id=02202019a",
          "http://web.archive.org/web/20250506070026/https://developer.apple.com/news/?id=02202019a",
          "https://dev.twitch.tv/docs/authentication/validate-tokens/",
          "https://discuss.dev.twitch.com/t/legacy-twitch-api-v5-i-e-kraken-shutdown-reminder-february-28-2022/36589",
          "http://web.archive.org/web/20250127085635/https://discuss.dev.twitch.com/t/legacy-twitch-api-v5-i-e-kraken-shutdown-reminder-february-28-2022/36589",
          "https://store.steampowered.com/news/posts/?enddate=1788390000",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/4123547285514022851",
          "https://skinvault.gg/blog/cs2-trade-protection-explained/",
          "https://csmarketcap.com/blog/market-insights/from-boom-to-bust-cs2s-trade-protection-impact",
          "https://skin.land/blog/steam-changes-cs2-trade-ban-logic-timing/",
          "https://help.steampowered.com/faqs/view/3041-A87A-E5F6-B6AC",
          "https://steamcommunity.com/ogg/593110/announcements/detail/533224478739530146",
          "https://steamcommunity.com/games/CSGO/announcements/detail/4447966961421256740",
          "https://steamcommunity.com/sharedfiles/filedetails/?id=2926756889",
          "https://steamcommunity.com/dev/apikey",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3734103130194459461",
          "https://steamcommunity.com/discussions/forum/1/3807266184852932971/",
          "https://help.steampowered.com/faqs/view/225C-C51E-B8F0-55B2",
          "https://store.steampowered.com/news/group/4/view/3314112260640237775",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/issues/325",
          "https://blog.dota2.com/2020/05/trading-cooldown/",
          "https://blog.counter-strike.net/index.php/2018/03/20308/",
          "http://web.archive.org/web/20250226114333/https://blog.counter-strike.net/index.php/2018/03/20308/",
          "https://phishdestroy.io/steam_dossier/it/steam_evidence_archive.html",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/493839547938902179",
          "https://store.steampowered.com/online_conduct",
          "http://web.archive.org/web/20260921022120/https://store.steampowered.com/online_conduct",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260918014700/https://store.steampowered.com/subscriber_agreement/",
          "https://steamcommunity.com/dev/apiterms",
          "http://web.archive.org/web/20260921022210/https://steamcommunity.com/dev/apiterms",
          "https://help.steampowered.com/en/faqs/view/628C-E332-BD8C-4D36",
          "https://phishdestroy.io/steam_dossier/it/social_graph.html",
          "https://phishdestroy.io/steam_dossier/it/security_timeline.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wsgc-skins-gambling-briefing-2018.pdf",
          "https://wsgc.wa.gov/sites/default/files/2023-10/Skins%20Gambling.pdf",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wsgc-briefing-manifest.json",
          "https://x.com/csgobig",
          "https://www.facebook.com/csgobigofficial/",
          "https://500.casino/",
          "https://csgolounge.com/",
          "https://csgocasino.gg/",
          "https://x.com/CSGOatsecom",
          "https://x.com/CSGOSweep/status/937420902538543106",
          "https://x.com/Wild",
          "https://x.com/csgopot",
          "https://x.com/csgodiamondscom",
          "https://www.ftc.gov/legal-library/browse/cases-proceedings/162-3184-csgo-lotto-matter",
          "https://x.com/CSGODouble",
          "https://x.com/csgo_massive",
          "https://www.facebook.com/csgostrongfree/",
          "https://www.facebook.com/CSNCOM/",
          "https://www.gamblingcommission.gov.uk/report/young-people-and-gambling",
          "https://www.aph.gov.au/Parliamentary_Business/Committees/Senate/Environment_and_Communications/Gamingmicro-transactions",
          "https://phishdestroy.io/steam_dossier/it/elite_skins.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/csfloat-catalogue.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/skinport-floor-over-cap.json",
          "https://pricempire.com/cs2-marketplaces",
          "http://web.archive.org/web/20260921022459/https://pricempire.com/cs2-marketplaces",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/priceempire-marketplaces.json",
          "https://www.steamanalyst.com/marketplace",
          "http://web.archive.org/web/20260719014552/https://www.steamanalyst.com/marketplace",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-atlas.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json",
          "https://phishdestroy.io/steam_dossier/it/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/it/steam_enforcement_evidence.html#case-support-recovery",
          "https://top10.owasp.org/2025/A01_2025-Broken_Access_Control/",
          "http://web.archive.org/web/20260920212535/https://top10.owasp.org/2025/A01_2025-Broken_Access_Control/",
          "https://store.steampowered.com/privacy_agreement/",
          "http://web.archive.org/web/20260921021648/https://store.steampowered.com/privacy_agreement/",
          "https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "http://web.archive.org/web/20250818113925/https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "https://www.dexerto.com/counter-strike-2/valve-saves-hacked-cs2-player-threatened-with-ransom-over-300000-of-rare-stickers-3283135/",
          "https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "http://web.archive.org/web/20220702042821/https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "https://www.kaspersky.com/blog/cs-go-two-million-usd-inventory-hack/44697/",
          "https://esportfire.com/article/the-2-million-usd-csgo-hack-22062022",
          "http://web.archive.org/web/20260515110250/https://esportfire.com/article/the-2-million-usd-csgo-hack-22062022",
          "https://esportsbetting.com/valve-deletes-130000-stolen-dragon-lore/",
          "https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "http://web.archive.org/web/20251115173120/https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "https://vkplay.ru/media/news/bloger-rasskazal-kak-podderzhka-steam-vorovala-akkaunty-igrokov/",
          "https://lis-skins.com/ru/blog/krupneisaia-mosenniceskaia-sxema-v-istorii-steam/",
          "https://escorenews.com/ru/csgo/news/44056-sotrudniki-podderjki-steam-zanimalis-krajey-skinov-s-akkauntov-za-god-oni-zarabotali-svyshe-300-tysyach-dollarov",
          "https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "http://web.archive.org/web/20250805141942/https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/outsourcing-archive-records.json",
          "https://community.skin.club/en/news/collector-has-steam-inventory-returned-after-bold-hack",
          "https://esportfire.com/article/300k-scam-full-katowice-2014-holo-collection-hacked",
          "http://web.archive.org/web/20251217072445/https://esportfire.com/article/300k-scam-full-katowice-2014-holo-collection-hacked",
          "https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng",
          "http://web.archive.org/web/20260920024236/https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng",
          "https://ag.ny.gov/press-release/2026/attorney-general-james-sues-game-developer-promoting-illegal-gambling-through",
          "http://web.archive.org/web/20260901015430/https://ag.ny.gov/press-release/2026/attorney-general-james-sues-game-developer-promoting-illegal-gambling-through",
          "https://www.fincen.gov/sites/default/files/2019-05/FinCEN%20CVC%20Guidance%20FINAL.pdf",
          "http://web.archive.org/web/20250711185007/https://www.fincen.gov/sites/default/files/2019-05/FinCEN%20CVC%20Guidance%20FINAL.pdf",
          "https://eur-lex.europa.eu/legal-content/EN/LSU/?uri=CELEX:32018L1673",
          "https://eur-lex.europa.eu/eli/dir/2024/1640/oj/eng",
          "http://web.archive.org/web/20260830153004/https://eur-lex.europa.eu/eli/dir/2024/1640/oj/eng",
          "https://eur-lex.europa.eu/eli/reg/2022/2065/oj/eng",
          "http://web.archive.org/web/20260920080125/https://eur-lex.europa.eu/eli/reg/2022/2065/oj/eng",
          "https://phishdestroy.io/steam_dossier/it/legal_analysis.html",
          "https://partner.steamgames.com/doc/features/auth#website",
          "http://web.archive.org/web/20260921022335/https://partner.steamgames.com/doc/features/auth",
          "https://www.ftc.gov/legal-library/browse/rules/childrens-online-privacy-protection-rule-coppa",
          "http://web.archive.org/web/20260921070051/https://www.ftc.gov/legal-library/browse/rules/childrens-online-privacy-protection-rule-coppa",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/gdpr-ticket-1.png",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/screenshot-manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/gdpr-ticket-2.png",
          "https://datenschutz.hamburg.de/beschwerde",
          "https://edpb.europa.eu/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/regulatory-review/disclosure-audit.json",
          "https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "http://web.archive.org/web/20260821155801/https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "https://phishdestroy.io/steam_dossier/it/index#exhibit-gallery-section",
          "https://github.com/ValveSoftware/steam-for-linux/issues/4521",
          "https://phishdestroy.io/steam_dossier/it/steam_evidence_archive.html?source=GitHub&record=484",
          "https://github.com/ValveSoftware/steam-for-linux/issues/6459",
          "http://web.archive.org/web/20260419051343/https://github.com/ValveSoftware/steam-for-linux/issues/6459",
          "https://phishdestroy.io/steam_dossier/it/steam_evidence_archive.html?source=GitHub&record=467",
          "https://github.com/ValveSoftware/Source-1-Games/issues/3857",
          "https://phishdestroy.io/steam_dossier/it/steam_evidence_archive.html?source=GitHub&record=768",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "http://web.archive.org/web/20250320082450/https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://phishdestroy.io/steam_dossier/it/steam_evidence_archive.html?source=Reddit&record=4533",
          "https://www.reddit.com/r/ohnePixel/comments/1hahqx2/permanently_banned_steam_account_without_a_clear/",
          "https://phishdestroy.io/steam_dossier/it/steam_evidence_archive.html?source=Reddit&record=4766",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://phishdestroy.io/steam_dossier/it/steam_evidence_archive.html?source=Reddit&record=4592",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/selected-evidence-records.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive_manifest.json",
          "https://phishdestroy.io/steam_dossier/it/card_economy.html",
          "https://github.com/JustArchiNET/ArchiSteamFarm/wiki/FAQ",
          "https://phishdestroy.io/steam_dossier/it/card_economy.html#scale",
          "https://phishdestroy.io/steam_dossier/it/card_economy.html#licence",
          "https://phishdestroy.io/steam_dossier/it/enforcement_audit.html",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "http://web.archive.org/web/20260924181709/https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://rdap.verisign.com/com/v1/domain/csgoempire.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoempire.com",
          "https://rdap.verisign.com/com/v1/domain/csgoempirelogin4.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/csgoempire.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustreaper.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustreaper.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/rustreaper.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustly.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustly.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/rustly.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgofast.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgofast.com",
          "https://rdap.verisign.com/com/v1/domain/authtofast.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/csgofast.com.json",
          "https://rdap.verisign.com/com/v1/domain/duelbits.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fduelbits.com",
          "https://rdap.verisign.com/com/v1/domain/switchflips.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/duelbits.com.json",
          "https://rdap.verisign.com/com/v1/domain/farmskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffarmskins.com",
          "https://tld-rdap.verisign.com/cc/v1/domain/kobal.cc",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/farmskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoluck.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoluck.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/csgoluck.com.json",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/domain-registry/insane.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Finsane.gg",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/insane.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs2skin.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs2skin.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/cs2skin.com.json",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/domain-registry/juice.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fjuice.gg",
          "https://rdap.verisign.com/com/v1/domain/letmeinjuice.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/juice.gg.json",
          "https://rdap.verisign.com/com/v1/domain/ggdrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fggdrop.com",
          "https://rdap.verisign.com/com/v1/domain/ggauth.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/ggdrop.com.json",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/domain-registry/howl.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhowl.gg",
          "https://rdap.radix.host/rdap/domain/howl.uno",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/howl.gg.json",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/domain-registry/chicken.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fchicken.gg",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/chicken.gg.json",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/domain-registry/csgocasino.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgocasino.gg",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/csgocasino.gg.json",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/domain-registry/hunt.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhunt.gg",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/hunt.gg.json",
          "https://rdap.verisign.com/com/v1/domain/csbattle.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsbattle.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/csbattle.com.json",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/domain-registry/skinrave.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinrave.gg",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/skinrave.gg.json",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/domain-registry/csdouble.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsdouble.gg",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/csdouble.gg.json",
          "https://rdap.verisign.com/com/v1/domain/rustchance.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustchance.com",
          "https://rdap.verisign.com/com/v1/domain/hgfuihd.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/rustchance.com.json",
          "https://rdap.radix.host/rdap/domain/cobaltlab.tech",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcobaltlab.tech",
          "https://rdap.verisign.com/com/v1/domain/cobaltauth.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/cobaltlab.tech.json",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/domain-registry/raided.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fraided.gg",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/raided.gg.json",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/domain-registry/rustneo.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustneo.gg",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/rustneo.gg.json",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/domain-registry/splits.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsplits.gg",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/splits.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/upgrader.pro",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fupgrader.pro",
          "https://rdap.radix.host/rdap/domain/upgauth.space",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/upgrader.pro.json",
          "https://rdap.centralnic.com/fans/domain/skin.fans",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.fans",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/skin.fans.json",
          "https://rdap.nic.one/domain/hotpizza.one",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhotpizza.one",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/hotpizza.one.json",
          "https://rdap.verisign.com/com/v1/domain/g4skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg4skins.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/g4skins.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2royal.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2royal.com",
          "https://rdap.verisign.com/com/v1/domain/tf2auth.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/tf2royal.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2hunt.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2hunt.com",
          "https://rdap.verisign.com/com/v1/domain/rstspcl.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/tf2hunt.com.json",
          "https://rdap.identitydigital.services/rdap/domain/tf2.bet",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2.bet",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/tf2.bet.json",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/domain-registry/openstars.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fopenstars.gg",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/openstars.gg.json",
          "https://rdap.verisign.com/com/v1/domain/skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/skins.com.json",
          "https://rdap.identitydigital.services/rdap/domain/white.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwhite.market",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/white.market.json",
          "https://rdap.identitydigital.services/rdap/domain/moon.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmoon.market",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/moon.market.json",
          "https://rdap.verisign.com/com/v1/domain/csfloat.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsfloat.com",
          "https://rdap.verisign.com/com/v1/domain/csgofloat.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/csfloat.com.json",
          "https://rdap.identitydigital.services/rdap/domain/skin.land",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.land",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/skin.land.json",
          "https://rdap.verisign.com/com/v1/domain/haloskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhaloskins.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/haloskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/163.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuff.163.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/buff.163.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmarket.csgo.com",
          "https://rdap.verisign.com/net/v1/domain/dota2.net",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/market.csgo.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinport.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinport.com",
          "https://pubapi.registry.google/rdap/domain/skinport.app",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/skinport.com.json",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/domain-registry/skinflow.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinflow.gg",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/skinflow.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/skin.place",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.place",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/skin.place.json",
          "https://rdap.verisign.com/com/v1/domain/skinsmonkey.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinsmonkey.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/skinsmonkey.com.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbaron.de",
          "https://rdap.verisign.com/com/v1/domain/skinbaron.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/skinbaron.de.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frust.tm",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/rust.tm.json",
          "https://rdap.verisign.com/com/v1/domain/pirateswap.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fpirateswap.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/pirateswap.com.json",
          "https://rdap.radix.host/rdap/domain/mannco.store",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmannco.store",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/mannco.store.json",
          "https://rdap.verisign.com/com/v1/domain/skinswap.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinswap.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/skinswap.com.json",
          "https://rdap.verisign.com/com/v1/domain/exeskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fexeskins.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/exeskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/balticskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbalticskins.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/balticskins.com.json",
          "https://rdap.nic.trade/domain/cs.trade",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.trade",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/cs.trade.json",
          "https://rdap.verisign.com/com/v1/domain/rapidskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frapidskins.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/rapidskins.com.json",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/domain-registry/tradeit.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftradeit.gg",
          "https://rdap.verisign.com/com/v1/domain/connect-tradeit.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/tradeit.gg.json",
          "https://rdap.verisign.com/com/v1/domain/49skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F49skins.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/49skins.com.json",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/domain-registry/skinvault.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinvault.gg",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/skinvault.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/aim.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Faim.market",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/aim.market.json",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/domain-registry/skinout.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinout.gg",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/skinout.gg.json",
          "https://rdap.verisign.com/com/v1/domain/ntskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fntskins.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/ntskins.com.json",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/domain-registry/gamerpay.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamerpay.gg",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/gamerpay.gg.json",
          "https://rdap.nic.tf/domain/scrap.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fscrap.tf",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/scrap.tf.json",
          "https://rdap.nic.tf/domain/marketplace.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmarketplace.tf",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/marketplace.tf.json",
          "https://rdap.identitydigital.services/rdap/domain/skins.cash",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.cash",
          "https://rdap.identitydigital.services/rdap/domain/skinscash.live",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/skins.cash.json",
          "https://rdap.verisign.com/net/v1/domain/csgo.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo.net",
          "https://rdap.verisign.com/net/v1/domain/easylot.net",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/csgo.net.json",
          "https://rdap.verisign.com/net/v1/domain/cybershoke.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcybershoke.net",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/cybershoke.net.json",
          "https://rdap.verisign.com/net/v1/domain/fastcup.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffastcup.net",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/fastcup.net.json",
          "https://rdap.verisign.com/com/v1/domain/leetify.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fleetify.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/leetify.com.json",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/domain-registry/scope.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fscope.gg",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/scope.gg.json",
          "https://rdap.verisign.com/com/v1/domain/tradeupspy.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftradeupspy.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/tradeupspy.com.json",
          "https://rdap.identitydigital.services/rdap/domain/cs.deals",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.deals",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/cs.deals.json",
          "https://rdap.verisign.com/com/v1/domain/pricempire.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fpricempire.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/pricempire.com.json",
          "https://rdap.identitydigital.services/rdap/domain/lzt.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flzt.market",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/lzt.market.json",
          "https://rdap.verisign.com/com/v1/domain/z2u.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fz2u.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/z2u.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoroll.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoroll.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/csgoroll.com.json",
          "https://rdap.verisign.com/com/v1/domain/rollbit.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frollbit.com",
          "https://rdap.verisign.com/com/v1/domain/rbsnin.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/rollbit.com.json",
          "https://rdap.identitydigital.services/rdap/domain/500.casino",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F500.casino",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/500.casino.json",
          "https://rdap.verisign.com/com/v1/domain/csgobig.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgobig.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/csgobig.com.json",
          "https://rdap.verisign.com/com/v1/domain/casedrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcasedrop.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/casedrop.com.json",
          "https://rdap.verisign.com/com/v1/domain/banditcamp.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbanditcamp.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/banditcamp.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinbox.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbox.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/skinbox.com.json",
          "https://rdap.verisign.com/com/v1/domain/tastydrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftastydrop.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/tastydrop.com.json",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/domain-registry/csgopolygon.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgopolygon.gg",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/csgopolygon.gg.json",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/domain-registry/magicdrop.ru.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmagicdrop.ru",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/magicdrop.ru.json",
          "https://rdap.verisign.com/com/v1/domain/csdice.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsdice.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/csdice.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinodds.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinodds.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/skinodds.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgowin.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgowin.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/csgowin.com.json",
          "https://rdap.verisign.com/net/v1/domain/csgorun.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgorun.net",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/csgorun.net.json",
          "https://rdap.verisign.com/com/v1/domain/openskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fopenskins.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/openskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustbet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustbet.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/rustbet.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgomagic.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgomagic.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/csgomagic.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgobounty.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgobounty.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/csgobounty.com.json",
          "https://rdap.verisign.com/com/v1/domain/ezskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fezskins.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/ezskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustcases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustcases.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/rustcases.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoreaper.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoreaper.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/csgoreaper.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgocases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgocases.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/csgocases.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo-skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo-skins.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/csgo-skins.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgonet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgonet.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/csgonet.com.json",
          "https://rdap.verisign.com/com/v1/domain/wtfskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwtfskins.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/wtfskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/flamecases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fflamecases.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/flamecases.com.json",
          "https://rdap.verisign.com/com/v1/domain/gamedom.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamedom.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/gamedom.com.json",
          "https://rdap.nic.club/domain/skin.club",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.club",
          "https://rdap.verisign.com/net/v1/domain/sc-auth.net",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/skin.club.json",
          "https://rdap.verisign.com/com/v1/domain/daddyskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdaddyskins.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/daddyskins.com.json",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/domain-registry/rustix.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustix.gg",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/rustix.gg.json",
          "https://rdap.nic.club/domain/skins.club",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.club",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/skins.club.json",
          "https://rdap.publicinterestregistry.org/rdap/domain/csgohouse.org",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgohouse.org",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/csgohouse.org.json",
          "https://rdap.verisign.com/net/v1/domain/skinrave.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinrave.net",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/skinrave.net.json",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/domain-registry/bloodycase.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbloodycase.gg",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/bloodycase.gg.json",
          "https://rdap.verisign.com/com/v1/domain/csgoclicker.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoclicker.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/csgoclicker.com.json",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/domain-registry/rustbet.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustbet.gg",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/rustbet.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs-drop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs-drop.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/cs-drop.com.json",
          "https://rdap.verisign.com/net/v1/domain/hellstore.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhellstore.net",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/hellstore.net.json",
          "https://rdap.verisign.com/com/v1/domain/rustloot.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustloot.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/rustloot.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo-case.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo-case.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/csgo-case.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgogem.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgogem.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/csgogem.com.json",
          "https://rdap.verisign.com/com/v1/domain/rainbet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frainbet.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/rainbet.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustclash.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustclash.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/rustclash.com.json",
          "https://rdap.identitydigital.services/rdap/domain/12cs.fail",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F12cs.fail",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/12cs.fail.json",
          "https://rdap.verisign.com/com/v1/domain/tf2easy.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwww.tf2easy.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/tf2easy.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2blaze.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2blaze.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/tf2blaze.com.json",
          "https://rdap.verisign.com/com/v1/domain/shuffle.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fshuffle.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/shuffle.com.json",
          "https://rdap.identitydigital.services/rdap/domain/buff.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuff.market",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/buff.market.json",
          "https://rdap.identitydigital.services/rdap/domain/avan.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Favan.market",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/avan.market.json",
          "https://rdap.identitydigital.services/rdap/domain/cs.money",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.money",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/cs.money.json",
          "https://rdap.verisign.com/com/v1/domain/uuskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fuuskins.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/uuskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/youpin898.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fyoupin898.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/youpin898.com.json",
          "https://rdap.verisign.com/com/v1/domain/c5game.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fc5game.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/c5game.com.json",
          "https://rdap.verisign.com/com/v1/domain/waxpeer.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwaxpeer.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/waxpeer.com.json",
          "https://rdap.verisign.com/com/v1/domain/dmarket.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdmarket.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/dmarket.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamcommunity.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamcommunity.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/steamcommunity.com.json",
          "https://rdap.verisign.com/com/v1/domain/lootfarm.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flootfarm.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/lootfarm.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustskins.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/rustskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/krakatoa.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fkrakatoa.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/krakatoa.com.json",
          "https://rdap.verisign.com/com/v1/domain/shadowpay.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fshadowpay.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/shadowpay.com.json",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/domain-registry/igxe.cn.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Figxe.cn",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/igxe.cn.json",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/domain-registry/swap.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fswap.gg",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/swap.gg.json",
          "https://rdap.verisign.com/com/v1/domain/bitskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbitskins.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/bitskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2mart.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2mart.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/tf2mart.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinbid.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbid.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/skinbid.com.json",
          "https://rdap.verisign.com/com/v1/domain/lootbear.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flootbear.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/lootbear.com.json",
          "https://rdap.nic.tf/domain/backpack.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbackpack.tf",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/backpack.tf.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fstntrading.eu",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/stntrading.eu.json",
          "https://rdap.verisign.com/com/v1/domain/skinwallet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinwallet.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/skinwallet.com.json",
          "https://rdap.verisign.com/com/v1/domain/dota2market.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdota2market.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/dota2market.com.json",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/domain-registry/xplay.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fxplay.gg",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/xplay.gg.json",
          "https://rdap.verisign.com/com/v1/domain/esportal.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fesportal.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/esportal.com.json",
          "https://rdap.registro.br/domain/gamersclub.com.br",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamersclub.com.br",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/gamersclub.com.br.json",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/domain-registry/epidemic.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fepidemic.gg",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/epidemic.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs2stash.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs2stash.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/cs2stash.com.json",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/domain-registry/csgoskins.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoskins.gg",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/csgoskins.gg.json",
          "https://rdap.verisign.com/com/v1/domain/steamanalyst.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamanalyst.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/steamanalyst.com.json",
          "https://rdap.verisign.com/net/v1/domain/steamcardexchange.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamcardexchange.net",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/steamcardexchange.net.json",
          "https://rdap.verisign.com/com/v1/domain/dotabuff.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdotabuff.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/dotabuff.com.json",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/domain-registry/tracker.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftracker.gg",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/tracker.gg.json",
          "https://rdap.verisign.com/com/v1/domain/funpay.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffunpay.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/funpay.com.json",
          "https://rdap.verisign.com/com/v1/domain/playerauctions.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fplayerauctions.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/playerauctions.com.json",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/domain-registry/eldorado.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Feldorado.gg",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/eldorado.gg.json",
          "https://rdap.verisign.com/com/v1/domain/g2a.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg2a.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/g2a.com.json",
          "https://rdap.verisign.com/net/v1/domain/kinguin.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fkinguin.net",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/kinguin.net.json",
          "https://rdap.verisign.com/com/v1/domain/g2g.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg2g.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/g2g.com.json",
          "https://rdap.verisign.com/com/v1/domain/playerup.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fplayerup.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/playerup.com.json",
          "https://rdap.verisign.com/net/v1/domain/smurfhub.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfhub.net",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/smurfhub.net.json",
          "https://rdap.verisign.com/com/v1/domain/smurfaccounts.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfaccounts.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/smurfaccounts.com.json",
          "https://rdap.verisign.com/com/v1/domain/buycsgorank.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuycsgorank.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/buycsgorank.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgosmurfkings.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgosmurfkings.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/csgosmurfkings.com.json",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/domain-registry/smurfstore.co.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfstore.co",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/smurfstore.co.json",
          "https://rdap.verisign.com/com/v1/domain/steamlvlup.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlvlup.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/steamlvlup.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamlevels.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlevels.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/steamlevels.com.json",
          "https://rdap.verisign.com/com/v1/domain/levelsteam.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flevelsteam.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/levelsteam.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamlevelu.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlevelu.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/steamlevelu.com.json",
          "https://rdap.verisign.com/com/v1/domain/eloking.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Feloking.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/eloking.com.json",
          "https://rdap.publicinterestregistry.org/rdap/domain/boosteria.org",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fboosteria.org",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/boosteria.org.json",
          "https://rdap.verisign.com/com/v1/domain/overgear.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fovergear.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/overgear.com.json",
          "https://rdap.verisign.com/com/v1/domain/blazingboost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fblazingboost.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/blazingboost.com.json",
          "https://rdap.verisign.com/com/v1/domain/dota2boost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdota2boost.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/dota2boost.com.json",
          "https://rdap.verisign.com/com/v1/domain/buyboost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuyboost.com",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit/buyboost.com.json",
          "https://phishdestroy.io/steam_dossier/it/steam_tos_assets/auth-route-audit.json",
          "https://help.steampowered.com/en/faqs/view/365F-4BEE-2AE2-7BDD",
          "https://store.steampowered.com/privacy_agreement/#8",
          "https://www.edpb.europa.eu/system/files/2023-04/edpb_guidelines_202201_data_subject_rights_access_v2_en.pdf",
          "https://web.archive.org/web/20260810154631/https://store.steampowered.com/stats/support",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/design-review/part2/measurements.json",
          "https://phishdestroy.io/steam_dossier/it/VALVE_EVIDENCE_PACK/databases/TOTAL_VALVE_SCANDALS_MASTER_DB.csv",
          "https://phishdestroy.io/steam_dossier/it/license_disclaimer.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/it/index.content.json",
      "export_json_sha256": "fe3bb4d12f74de6842edf927440567de551d8c9bf055ca5e7065aed5ec79c42f"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "it/investigation_part2.html",
      "language": "it",
      "title": "Accesso agli account e responsabilità — Il dossier Steam",
      "source_url": "https://phishdestroy.io/steam_dossier/it/investigation_part2",
      "source_html_sha256": "2962298a492843fc607eacd5c32002f764ae2123a3c81a58584d72c155fa9c4e",
      "exported_at": "2026-09-29T00:17:50.680Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "investigation_part2.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/it/investigation_part2.pdf?v=print-20260929-v5",
        "sha256": "8f78c3d5ba2eec8f7ccca8cba4de6d28a36af3b2f333b411b25952e9847e5809",
        "bytes": 124213,
        "pages": 9
      },
      "integrity": {
        "signed_object": "investigation_part2.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "investigation_part2.content.json.asc",
        "digest_file": "investigation_part2.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify investigation_part2.content.json.asc investigation_part2.content.json",
          "sha256sum -c investigation_part2.content.json.sha256"
        ]
      },
      "content": {
        "text": "IL DOSSIER SU STEAM / II\n\nIl tuo account.Il loro accesso.Chi risponde?\n\nAutomazione pubblica. Assistenza esternalizzata. E sono i cittadini a farne le spese.\n\nSegui l’evoluzione delle infrastrutture, le perdite segnalate e i documenti alla base delle richieste di risarcimento.\n\nMappare l'infrastruttura ↘\nALLEGATO 01 / SORVEGLIANZA DEL MERCATO SOMBRIO IN TEMPO REALE550,000+\n\nSteam account attualmente in vendita su FSB Market (nome anonimizzato; il nome originale non è indicato qui)\nproprio in questo momento\n\n550,000+ INVENTARIO IN TEMPO REALE · 231,829 NEL CORPUS STORICO RACCOLTO (198,320 REGISTRI DI STEALER)\n\nLa principale piattaforma sotterranea per la gestione degli account Steam dirottati, FSB Market (altri nomi associati non divulgati), autentica sia gli acquirenti che i venditori utilizzando l'OpenID ufficiale Valve Steam (openid.realm = https://FSB Market). In ogni momento, oltre mezzo milione di account rubati e compromessi (log di stealer provenienti da RedLine/Lumma, dati raccolti tramite phishing, credential stuffing) vengono messi in vendita a pochi centesimi ($0.50–$2.00). Né FSB Market né il forum associato è bloccato dal filtro dei link di Valve. Si tratta del bacino industriale che alimenta i 63.06% account bot a pagamento che Valve banna senza fornire assistenza alla vittima.\n\nDati in tempo reale: monitoraggio del mercato sommerso (oltre 550.000 utenti attivi) ↗ · Apri record di acquisizione ↗ · Apri traccia del filtro dei collegamenti ↗Oltre 550.000 IN DIRETTA\n\n01 / UN ECOSISTEMA CON GLI AUTORI\n\nL'automazione hauna traccia cartacea.\n\nProgetti denominati. Funzionalità pubblicate. Traccia un tool fino alla relativa documentazione, quindi esamina le relazioni tra sviluppatori raccolte.\n\n252ARCHIVI RACCOLTI\n3,320PROFILI SU GITHUB\n4,214PROFILO – COPPIE DI ARCHIVI\nValve infrastruttureBiblioteche comunitarieApplicazioni riutilizzabili\nLe linee indicano integrazioni o dipendenze documentate. Seleziona un nodo per visualizzarne i dettagli.\n\nAutomazione multi-account / JustArchiNET\n\nArchiSteamFarm\n\nIl progetto pubblicizza esplicitamente la possibilità di accumulare carte contemporaneamente su più account Steam. Il file di progetto dichiara una dipendenza da SteamKit2.\n\nLeggi la documentazione del progetto ↗\n\nSteamKit → ArchiSteamFarm\ndipendenza dichiarata ↗\n\nRAPPORTI RACCOLTI\n\n40 etichette dei collaboratori · 40 etichette Forker\n\nDi seguito è riportato un esempio fornito da un collaboratore. Queste etichette descrivono il rapporto con il repository, non un rapporto di lavoro o di approvazione.\n\n@JustArchi@renovate[bot]@JustArchi-ArchiBot@dependabot-preview[bot]@renovate-bot@actions-user@dependabot-support@Abrynos\nCosa evidenzia il grafico degli sviluppatori\n\nIl grafico illustra le relazioni pubblicate tra contributori e autori di fork relative a progetti specifici e profili GitHub. Si tratta di dati pubblici: fork dei repository, elenchi dei contributi, associazioni tra profili. La domanda è: cosa richiede di chiarire la traccia documentale delle capacità pubblicate e delle relazioni tra sviluppatori Valve, non cosa abbia inventato questa indagine. Gli hash dei sorgenti sono salvati nel mappa della provenienza.\n\nEsplora l'intera rete ↗Dati di origine del repository ↓\n\n02 / CREDENZIALI DIVERSE. POTERI DIVERSI.\n\nQuale tastoDi cosa stiamo parlando?\n\nPer giocare non è necessario che il giocatore fornisca una chiave API Web personale. È proprio questa la distinzione al centro della presente indagine.\n\n01 / ACCOUNT UTENTE\nChiave API Web personale\nsteamcommunity.com/dev/apikey\n\nEmanate da un account utente per le chiamate API autorizzate. La creazione, la visibilità, la revoca delle chiavi e il rilevamento degli abusi rientrano nelle questioni relative alla sicurezza dell'account.\n\n02 / BACKEND DEL GIOCO\nChiave API Web dell'editore\n\nI partner di Steamworks utilizzano le credenziali dell'editore per le operazioni di backend supportate, compresi i servizi relativi ai giochi. La chiave personale di un giocatore è una credenziale diversa.\n\n03 / IDENTITÀ E SESSIONE\nOpenID / token di sessione\n\nOpenID conferma l'identità a un sito web. Un token di sessione o di aggiornamento Steam ha uno scopo diverso. Questi meccanismi non dovrebbero essere presentati come un'unica “chiave API” intercambiabile.\n\nValve documenta sia le chiavi Web API degli utenti che quelle degli editori. L'intera Web API non è quindi separata da Steamworks. Documentazione sulla chiave API ↗ archiviato 2026-09-15 ↗ · Autenticazione durante la sessione di gioco ↗ archiviato 2026-08-29 ↗\n\nDOCUMENTATO DALL'AUTORE DELLO STRUMENTO / MARZO 2024\n\nL'automazione può utilizzare più di una chiave API.\n\nIl wiki di Trade Offer Manager descrive l'utilizzo di un token di accesso di sessione per alcune parti dell'API Web quando non esiste una chiave API separata. Descrive inoltre la procedura di conferma tramite dispositivo mobile per la creazione della chiave a partire dalla fine del 2023. Il responsabile della manutenzione afferma che l'uso del token in questo modo non è supportato da Valve; si tratta di un'affermazione contenuta nella documentazione ormai superata, non di un test di bypass effettivamente eseguito.\n\nEsamina la spiegazione del responsabile della manutenzione ↗ archiviato 2026-09-24 ↗\n\nIL LATO UMANO / UN PERCORSO ILLUSTRATIVO DEL PHISHING\n\nSto ancora giocando.Già reso pubblico.\n\nUn messaggio da un amico. Una richiesta di voto. Una pagina di ringraziamento. Per l’utente, l’operazione è terminata. Una sessione compromessa può protrarsi oltre quel momento.\n\nSULLO SCHERMO DEL GIOCATORE\n\nF\nIL RACCONTO DI UN AMICO\n\n“Potresti votare per la nostra squadra?”\n\nLa richiesta arriva tramite la chat diSteamda un account conosciuto. In questo scenario, la pagina collegata si apre nel browser del cliente.\n\nFUORI DALLA VISTA\n\nLa fiducia viene prima del sito web.\n\nL'account di un amico che è stato violato può conferire credibilità a un link di phishing. L'interfaccia Steam che lo circonda non certifica il sito web di destinazione.\n\nMITTENTE CONOSCIUTO / DESTINATARIO ESTERNO\nLa sicurezza dell'account è la priorità assoluta prima di vendere qualsiasi articolo.\n\nL'utente non aveva intenzione di creare credenziali per l'automazione né di delegare il controllo. Il fatto di accedere nuovamente al gioco non costituisce una prova che l'account sia sicuro. Valve conserva i registri delle sessioni, il registro di creazione delle chiavi API e i dati di correlazione dei dispositivi. La vittima, invece, no. Questa asimmetria costituisce il problema della responsabilità.\n\nAccesso alle sessioni e tipi di credenziali\n\nUna chiave API e una sessione di accesso sono credenziali distinte con funzionalità diverse. La revoca di una chiave non interrompe una sessione attiva. La documentazione di Valve descrive entrambe; Valve conserva i registri che mostrerebbero quale credenziale fosse attiva al momento di qualsiasi azione contestata. La richiesta riguarda la divulgazione di tale registrazione — non un'ipotesi formulata dall’indagine. Documentazione del responsabile sulla gestione dei token ↗ archiviato 2026-09-24 ↗ · Valve documentazione di riferimento ↗ archiviato 2026-09-15 ↗\n\n03 / IL MERCATO UFFICIALE HA UN LIMITE MASSIMO\n\nL'oggetto potrebbe essere raro.Il limite rimane.\n\nUn prezzo superiore al limite massimo di quotazione non può essere realizzato tramite un'unica quotazione sul Mercato Comunitario a tale prezzo pieno.\n\nPREZZO DI VENDITA INDICATIVO$5,000Modifica il prezzo richiesto per l'articolo\n$100$20,000\n\nSi tratta di un esempio del limite pubblicato, non di una valutazione né di una raccomandazione di negoziazione.\n\nLIMITE DI QUOTAZIONE≈ $1,800\nTAPPO DEL PORTAFOGLI≈ $2,000\n\nSuperiore al limite massimo di quotazione pubblicato.\n\nI fondi presenti nel portafoglio non possono essere prelevati su un conto bancario. Queste limitazioni generano una domanda che viene soddisfatta dai mercati di skin di terze parti: una domanda generata dai limiti di quotazione e di saldo del portafoglio, mentre le regole di Valve impediscono agli operatori commerciali di soddisfarla.\n\nLimiti di mercato di Steam ↗ archiviato 2026-09-21 ↗\n\n04 / ALL’INTERNO DEL CONFINE DI SOSTEGNO\n\nResponsabili del trattamento dei dati.Responsabile dell'accesso.\n\nL'informativa sulla privacy di Valve prevede espressamente la condivisione dei dati personali con fornitori di assistenza di terze parti, nella misura necessaria a garantire l'assistenza.\n\nIL GIOCATOREConto e prove\n→\nVALVOLAProcesso di recupero\n→\nFORNITORE DI ASSISTENZAAccesso delegato\n\nInformativa sulla privacy §5.2 ↗ · La politica interna di Valve autorizza l’accesso da parte di terzi a fini di assistenza. Le questioni ancora aperte sono: quali autorizzazioni sono state concesse, quali registri di controllo esistono e cosa è successo quando si presume che l’accesso sia stato utilizzato in modo improprio.\n\n2015\nLa bilancia era a disposizione del pubblico\n\nValve ha ammesso che si sono verificati numerosi casi di furto di account e ha illustrato le misure di protezione adottate.\n\nValve pubblicazione ↗archiviato 2026-08-09 ↗\n2015\nValve ha affidato il servizio a terzi — e lo ha dichiarato apertamente\n\nValve dispone di un piccolo team interno Steam di Support Leadership e lo ha dichiarato \"ha ingaggiato un paio di aziende diverse\" per gestire l'assistenza (Erik Johnson, Valve, a Kotaku); la sezione 5.2 della sua informativa sulla privacy autorizza l'accesso a tali terze parti ai dati degli utenti. Quale appaltatore dispone dell’accesso per il recupero dei conti? Valve non lo ha mai rivelato — Nella discussione della comunità vengono citati fornitori come Concentrix, ma nessuno di essi è stato Valve-confermato. Il servizio esternalizzato era già operativo anni prima di entrambe le ammissioni riportate di seguito.\n\nKotaku: Valve sul suo supporto ↗archiviato 2025-07-11 ↗\n2023\nLa prima ammissione\n\nLa squadra di CS:GO di Valve si assume per iscritto la responsabilità per la compromissione di un account avvenuta attraverso la propria procedura di richiesta di assistenza e annulla gli scambi.\n\nApri il caso di outsourcing ↓\n2025\nLa seconda ammissione\n\n33 mesi dopo, Steam Support scrive che un tecnico \"non ha seguito la nostra procedura, con il risultato che il tuo account è stato ripristinato a nome di qualcun altro\". Stesso canale. Stesso risultato.\n\nDexerto, 14 novembre 2025 ↗\n\nFASCICOLO DEL CASO / HFB E LE ACCUSE DI OUTSOURCING\n\nL'accesso avveniva tramite Steam Support stesso.Valve lo ha dichiarato per iscritto.\n\nNella risposta dell'assistenza riportata da Dexerto, la squadra di CS:GO di Valve si assume la responsabilità della compromissione di un account attraverso la procedura di richiesta di assistenza — il proprio canale, non una pagina di phishing e non l’utente. Gli articoli sono stati recuperati e le transazioni annullate, il che rappresenta il rimedio che Valve dice alle altre vittime non esistere. Il magazzino di HFB è stato segnalato a $2,000,000+ il giorno stesso e $3,000,000+ nel seguito; Anche Qkss ha perso $1,000,000+ allo stesso modo e non ha ottenuto nulla.\n\nRISPOSTA DEL SERVIZIO ASSISTENZA / RIPRODOTTO DA DEXERTO · 21 FEB 2023\n“compromesso a seguito di una richiesta di assistenza, di cui il team di CS:GO si assume la responsabilità”\nLeggi l'articolo e il messaggio riportato ↗ archiviato 2025-08-18 ↗\n01 / QUALE VALVOLA È STATA AMMESSA\nIl canale di assistenza dedicato era la via d’accesso\n\nLa risposta riguarda l’account compromesso e la revoca delle relative operazioni. Valve le ha revocate — quindi le operazioni erano reversibili. Il ticket originale autenticato non è presente in questa raccolta.\n\n02 / COSA NON HANNO RISOLTO I LICENZIAMENTI\nQuella stessa porta si riaprì nel novembre del 2025\n\nL'appaltatore ha licenziato l'intero personale di assistenza Steam — come riportato da Mzkshow tramite Dexerto, e non in seguito a una dichiarazione ufficiale dell'azienda Valve. Trentatré mesi dopo, Steam Support ha scritto a un altro esattore che «un tecnico dell’assistenza che ha gestito la richiesta di aiuto non ha seguito la nostra procedura, il che ha portato al ripristino del suo account a nome di qualcun altro». Frase tratta dallo stesso Valve, riguardo allo stesso canale.\n\nIl secondo ricovero, 14 novembre 2025 ↗\n03 / CHE COS'È OPEN\nValve non ha mai indicato il nome dell'appaltatore\n\nNé l’appaltatore né la sede sono indicati in queste fonti. Non si tratta di una lacuna nella cronaca, bensì di un’informazione che Valve non ha rivelato riguardo a chi avesse accesso agli account degli utenti.\n\nResoconto contemporaneo del caso ↗\n\nTre domande a cui Valve non ha risposto: chi potrebbe impedire il recupero dell’account, cosa è emerso dalla verifica degli accessi e cosa è cambiato in seguito.\n\nAccuse successive contenute nell’archivio dei documenti di supporto conservato\n\nDue post su Reddit del 2024 riportano ulteriori indagini di Mzkshow: un caso di revoca del ban VAC del luglio 2024 e un caso di inventario $13,000 del dicembre 2024. Si tratta di incidenti segnalati separatamente. La questione della responsabilità in entrambi i casi è identica: chi aveva accesso con privilegi di sovrascrittura, cosa è emerso dall’audit e cosa è cambiato.\n\n14 luglio 2024 · recupero segnalato / caso di VAC-ban ↗2 dicembre 2024 · segnalato $13,000 caso di inventario ↗archiviato 2025-08-05 ↗Due post conservati, righe sorgente e hash ↓\n\n05 / SEGUI LA PERDITA\n\nOgni importoci vuole una custodia.\n\nDieci casi, da giugno 2022 a marzo 2026. Ogni importo corrisponde al dato pubblicato dalla fonte indicata — $6,300,000, $2,000,000+, $1,000,000+, ≈$320,000, ≈$300,000, scendendo fino a 288 €. Valve conserva il registro delle transazioni, il registro delle sessioni e la traccia di controllo dell'assistenza per ciascuna di esse, ma non ne ha prodotto nessuno.\n\nCANALE DI ASSISTENZA21 GIU2022\n$2,000,000+\nHFB — the largest inventory in the game\n\nVALUTAZIONE DELLE SCORTE DICHIARATA · AUMENTATA A OLTRE $3MILIONI NEL SEGUITO DELL'2023 DI FEBBRAIO\n\nSette Dragon Lores da collezione e il Karambit Blue Gem #1; solo quel coltello vale circa $1.26. Inattivo da tre anni con l’autenticatore ancora attivo; e-mail e password modificate tramite la procedura di recupero dell’assistenza. Valve ha annullato le transazioni — e ne ha assunto la responsabilità per iscritto. Prima dell’annullamento, erano già stati prelevati, secondo quanto riferito, proventi per $200,000+ tramite market.csgo.com, che effettua pagamenti in contanti e criptovalute. Un annullamento restituisce una skin, non il denaro che qualcuno ha già incassato. L’annullamento ha inoltre causato un malfunzionamento: un acquirente aveva nascosto il suo Souvenir Dragon Lore in un’unità di stoccaggio all’interno del gioco; lo script non è riuscito a vedere all’interno del proprio contenitore e Valve ha duplicato un oggetto del valore di $130,000 mentre annullava un furto — individuato grazie agli ID degli oggetti e alle segnalazioni della comunità, cancellato a luglio 2022,; l’acquirente è stato rimborsato da BUFF anziché da Valve.\n\nDexerto, il giorno del furto ↗\nPORTAFOGLIO E ACQUISTI07 1° LUGLIO 2022\n>$500\n44 disputed Market purchases\n\nSPESA DICHIARATA PER PORTAFOGLI · USD\n\nUn utente segnala acquisti non autorizzati di oggetti di basso valore per Dota 2 e una risposta insoddisfacente da parte dell'assistenza.\n\nLeggi la denuncia e gli screenshot allegati ↗\nVIOLAZIONE DELLA PIATTAFORMA14 2022 di agosto\n$6,300,000\nCS.Money — 19,000+ skin ottenute dai bot\n\nVALUTAZIONE DEL PREZZO · PRIMA STIMA $1.6M\n\nGli hacker hanno sottratto i file dell’autenticatore mobile dei bot di trading della piattaforma e li hanno svuotati, trasferendo parte del bottino a trader noti per confondere le tracce. I ricercatori della comunità hanno individuato 55 account degli autori dell’attacco nel giro di poche ore. Valve non ha effettuato alcun reverse engineering: un sito di terze parti si trova al di fuori di Steam, ha affermato lo stesso Steam il cui inventario, il sistema di trading API e il sistema di account hanno subito il furto dall’inizio alla fine.\n\nLeggi il resoconto dell'epoca ↗\nCANALE DI ASSISTENZANOTIZIA PUBBLICATA SU 21, 2023\n$1,000,000+\nQkss — stessa porta, stesso attore, risposta opposta\n\nVALUTAZIONE DELLE SCORTE DICHIARATA\n\nConsiderando il modo in cui è stato gestito il caso HFB, dallo stesso attore, attraverso la stessa richiesta di assistenza. Il caso HFB era stato risolto completamente otto mesi prima. Quello di Qkss no. Nulla nei documenti pubblicati distingue i due casi, se non la dimensione del pubblico.\n\nDexerto sull'inchiesta Mzkshow ↗\nCANALE DI ASSISTENZANOTIZIA DEL 2023 DI FEBBRAIO\n≈ $320,000\nL'insider trading in sé — un anno di attività\n\nRISULTATI RELATIVI A CIRCA UN ANNO · NON SI TRATTA DI UNA VALUTAZIONE DELLE SCORTE\n\nL'accesso tramite l'assistenza ha permesso di recuperare la cronologia dell'account risalente fino a 15 anni fa: il primo codice CD, la prima e-mail, la prima carta — esattamente le prove richieste dal processo di recupero. Chi detiene il database ha sempre la meglio in questa disputa contro chi detiene l’account. Un M4A4 Howl rubato con ologrammi iBUYPOWER e Titan Katowice 2014 è stato venduto per $35,000 e è finito nelle mani di b1t dei NAVI, che non aveva modo di saperlo. La risposta dell’appaltatore è stata quella di licenziare tutti i dipendenti che lavoravano all’assistenza Steam.\n\nEscorenews sulla stessa inchiesta ↗\nPORTAFOGLIO E ACQUISTI09 DEC 2023\n€288\nSmarrimento del portafoglio nonostante la protezione a due passaggi\n\nTRUSTPILOT · INDICE DELLE FONTI 16\n\nIl recensore segnala che il suo account è stato violato e che gli è stato negato l'aiuto per le spese su Market. L'esportazione non contiene un URL specifico per la recensione.\n\nVerifica la provenienza del codice sorgente ↗\nRECUPERO DELL'ACCOUNT02 DEC 2024\n$13,000\n“Matvey” — due anni dopo i licenziamenti\n\nSTIMA DELL’INVENTARIO DELL’AUTORE\n\nIl recupero è stato concesso a una persona che ha fornito dati relativi all'account che lo stesso titolare non era in grado di confermare. Stesso iter, stesso risultato, dopo che l'appaltatore aveva smantellato il proprio servizio di assistenza Steam.\n\nLeggi l'accusa conservata ↗\nRECUPERO DELL'ACCOUNT09 MAIO 2025\n≈ $10,000\nRecupero tramite il biglietto di qualcun altro\n\nSMARRIMENTO DI UN ARTICOLO RICHIESTO · USD\n\nUn utente del Quebec sostiene che il servizio di assistenza abbia reimpostato la password e rimosso le misure di protezione dell'account su richiesta di un'altra persona.\n\nLeggi la denuncia in prima persona ↗\nCANALE DI ASSISTENZA13 NOV 2025\n≈ $300,000\nHawkeye337 — e la seconda ammissione scritta di Valve\n\nCOLLEZIONE COMPLETA HOLO DI KATOWICE 2014\n\nL'autore dell'attacco ha chiesto un bitcoin d1e e ha iniziato a trasferire la collezione su Negevs per distruggerla. Steam Risposta dell'assistenza: “Un tecnico dell'assistenza che ha gestito la richiesta di aiuto non ha seguito la nostra procedura, il che ha portato al ripristino del tuo account a nome di qualcun altro”. Trentatré mesi dopo la prima ammissione, la stessa storia. Ripristinato poche ore dopo che il thread era diventato virale su X. Qkss non aveva quel pubblico.\n\nDexerto, 14 Nov 2025 ↗\nPORTAFOGLIO E ACQUISTI29 MAR 2026\n$50\nRicariche non autorizzate e giochi regalati\n\nTRUSTPILOT · INDICE DELLE FONTI 290\n\nIl recensore denuncia spese non autorizzate e richieste di rimborso non andate a buon fine. Nell'esportazione manca l'URL della singola recensione.\n\nVerifica la provenienza del codice sorgente ↗\n\nLe attribuzioni e gli importi rimangono quelli riportati da ciascuna fonte. Valve conserva i registri delle transazioni, i registri delle sessioni e la traccia di audit di supporto per ciascuno di questi casi. È necessario presentarli. Un post di Reddit archiviato non risolve la questione: sono i registri di Valve a farlo.\n\nLA COLLEZIONE / DOPO AVER VERIFICATO\n\n231,829 conti in vendita.Valve contiene i registri relativi a ciascuno di essi.\n354 → 201\nDati di Trustpilot\n\nSono state rimosse 153 righe duplicate. Gli URL delle recensioni individuali non sono stati conservati nell'esportazione.\n\n231,829\nSteam elenchi di account\n\n33,509 classificato come \"autoregistrato\"; 198,320 con l'etichetta \"stealer\" del collezionista. Gli annunci non costituiscono vendite concluse.\n\nVerifica della raccolta ↓Cerca nell'archivio sorgente ↗",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Il tuo account.Il loro accesso.Chi risponde?"
          },
          {
            "level": 2,
            "id": null,
            "text": "L'automazione hauna traccia cartacea."
          },
          {
            "level": 3,
            "id": null,
            "text": "ArchiSteamFarm"
          },
          {
            "level": 2,
            "id": null,
            "text": "Quale tastoDi cosa stiamo parlando?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Chiave API Web personale"
          },
          {
            "level": 3,
            "id": null,
            "text": "Chiave API Web dell'editore"
          },
          {
            "level": 3,
            "id": null,
            "text": "OpenID / token di sessione"
          },
          {
            "level": 3,
            "id": null,
            "text": "L'automazione può utilizzare più di una chiave API."
          },
          {
            "level": 2,
            "id": null,
            "text": "Sto ancora giocando.Già reso pubblico."
          },
          {
            "level": 3,
            "id": "session-hidden-title",
            "text": "La fiducia viene prima del sito web."
          },
          {
            "level": 2,
            "id": null,
            "text": "L'oggetto potrebbe essere raro.Il limite rimane."
          },
          {
            "level": 2,
            "id": null,
            "text": "Responsabili del trattamento dei dati.Responsabile dell'accesso."
          },
          {
            "level": 3,
            "id": null,
            "text": "La bilancia era a disposizione del pubblico"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve ha affidato il servizio a terzi — e lo ha dichiarato apertamente"
          },
          {
            "level": 3,
            "id": null,
            "text": "La prima ammissione"
          },
          {
            "level": 3,
            "id": null,
            "text": "La seconda ammissione"
          },
          {
            "level": 3,
            "id": null,
            "text": "L'accesso avveniva tramite Steam Support stesso.Valve lo ha dichiarato per iscritto."
          },
          {
            "level": 4,
            "id": null,
            "text": "Il canale di assistenza dedicato era la via d’accesso"
          },
          {
            "level": 4,
            "id": null,
            "text": "Quella stessa porta si riaprì nel novembre del 2025"
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve non ha mai indicato il nome dell'appaltatore"
          },
          {
            "level": 2,
            "id": null,
            "text": "Ogni importoci vuole una custodia."
          },
          {
            "level": 3,
            "id": null,
            "text": "HFB — the largest inventory in the game"
          },
          {
            "level": 3,
            "id": null,
            "text": "44 disputed Market purchases"
          },
          {
            "level": 3,
            "id": null,
            "text": "CS.Money — 19,000+ skin ottenute dai bot"
          },
          {
            "level": 3,
            "id": null,
            "text": "Qkss — stessa porta, stesso attore, risposta opposta"
          },
          {
            "level": 3,
            "id": null,
            "text": "L'insider trading in sé — un anno di attività"
          },
          {
            "level": 3,
            "id": null,
            "text": "Smarrimento del portafoglio nonostante la protezione a due passaggi"
          },
          {
            "level": 3,
            "id": null,
            "text": "“Matvey” — due anni dopo i licenziamenti"
          },
          {
            "level": 3,
            "id": null,
            "text": "Recupero tramite il biglietto di qualcun altro"
          },
          {
            "level": 3,
            "id": null,
            "text": "Hawkeye337 — e la seconda ammissione scritta di Valve"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ricariche non autorizzate e giochi regalati"
          },
          {
            "level": 2,
            "id": null,
            "text": "231,829 conti in vendita.Valve contiene i registri relativi a ciascuno di essi."
          },
          {
            "level": 3,
            "id": null,
            "text": "Dati di Trustpilot"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam elenchi di account"
          }
        ],
        "links": [
          "https://phishdestroy.io/live-intel/?category=steam",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/lzt.market.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-evidence-lzt.json",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://github.com/JustArchiNET/ArchiSteamFarm/blob/main/ArchiSteamFarm/ArchiSteamFarm.csproj",
          "https://github.com/JustArchi",
          "https://github.com/renovate[bot]",
          "https://github.com/JustArchi-ArchiBot",
          "https://github.com/dependabot-preview[bot]",
          "https://github.com/renovate-bot",
          "https://github.com/actions-user",
          "https://github.com/dependabot-support",
          "https://github.com/Abrynos",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/automation-map.json",
          "https://phishdestroy.io/steam_dossier/it/output_steam_network/network.html",
          "https://phishdestroy.io/steam_dossier/it/output_steam_network/raw_data.json",
          "https://partner.steamgames.com/doc/webapi_overview/auth",
          "http://web.archive.org/web/20260915025812/https://partner.steamgames.com/doc/webapi_overview/auth",
          "https://partner.steamgames.com/doc/webapi/ISteamUserAuth",
          "http://web.archive.org/web/20260829124950/https://partner.steamgames.com/doc/webapi/ISteamUserAuth",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "http://web.archive.org/web/20260924181824/https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://store.steampowered.com/privacy_agreement/",
          "https://store.steampowered.com/oldnews/19618",
          "http://web.archive.org/web/20260809125516/https://store.steampowered.com/oldnews/19618",
          "https://kotaku.com/valve-explains-why-steam-customer-service-is-still-terr-1736988223",
          "http://web.archive.org/web/20250711004653/https://kotaku.com/valve-explains-why-steam-customer-service-is-still-terr-1736988223",
          "https://www.dexerto.com/counter-strike-2/valve-saves-hacked-cs2-player-threatened-with-ransom-over-300000-of-rare-stickers-3283135/",
          "https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "http://web.archive.org/web/20250818113925/https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "https://lis-skins.com/ru/blog/krupneisaia-mosenniceskaia-sxema-v-istorii-steam/",
          "https://www.reddit.com/r/cs2/comments/1e38jo4/stealing_accounts_and_removing_vac_bans_a_new/",
          "https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "http://web.archive.org/web/20250805141942/https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/outsourcing-archive-records.json",
          "https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "https://escorenews.com/en/csgo/news/44087-valve-steam-support-employee-accused-of-selling-inactive-accounts-inventories-worth-six-figures-b1t-has-one-of-these-skins",
          "https://phishdestroy.io/steam_dossier/it/PART2_RESEARCH.md",
          "https://www.reddit.com/r/GlobalOffensive/comments/1h56shi/steam_support_is_stealing_accounts/",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/design-review/part2/quality-review.json",
          "https://phishdestroy.io/steam_dossier/it/steam_evidence_archive.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/it/investigation_part2.content.json",
      "export_json_sha256": "1f2fdfc56071890408b892b2da35e7257a4891416fc890299e6f369e426edeaf"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "it/legal_analysis.html",
      "language": "it",
      "title": "Le loro condizioni, i tuoi diritti — Il dossier su “Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/it/legal_analysis",
      "source_html_sha256": "f7a927d0f89247bd8fd2eca43d4ef913caea19cc8fc3eaf2453b7617ee8f4d28",
      "exported_at": "2026-09-29T00:17:51.524Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "legal_analysis.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/it/legal_analysis.pdf?v=print-20260929-v5",
        "sha256": "d73004dbd6118bf6be4df2bbff2d9e14c90eb333175cc51274d92f7f9b09206b",
        "bytes": 104253,
        "pages": 8
      },
      "integrity": {
        "signed_object": "legal_analysis.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "legal_analysis.content.json.asc",
        "digest_file": "legal_analysis.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify legal_analysis.content.json.asc legal_analysis.content.json",
          "sha256sum -c legal_analysis.content.json.sha256"
        ]
      },
      "content": {
        "text": "Relazione giuridica ed economica\nAnalisi giuridica — Condizioni di servizio e conformità normativa\n\nLe loro condizioni. I tuoi diritti.\n\nCOSA DIMOSTRA QUESTA SEZIONE\n\nLa presente revisione legale forense valuta l’asimmetria contrattuale tra Valve Corporation e gli utenti di Steam nelle principali giurisdizioni normative. Essa dimostra come la licenza di abbonamento revocabile privi i consumatori della titolarità prevista dalla legge, analizza la giurisprudenza della Corte di giustizia europea sull’esaurimento del diritto di rivendita nel settore digitale ed esamina la conformità ai requisiti previsti dal Digital Services Act (DSA) e dall’GDPR, art. 15.. L’analisi illustra come i meccanismi automatizzati di applicazione delle norme operino senza possibilità di ricorso significativo, mentre le commissioni di mercato delle piattaforme sottraggono sistematicamente valore economico a ogni transazione tra pari.\n\n← Torna al briefing esecutivo\n\nIl presente rapporto presenta un’analisi giuridica, economica e tecnica del divario esistente tra le regole dichiarate dalla piattaforma “Steam” e la posizione dei consumatori: un’applicazione automatizzata delle norme con scarse possibilità di ricorso e un ampio controllo aziendale sulle risorse digitali. I dati sono riportati con la relativa fonte; laddove non sia stato possibile risalire a una fonte primaria, tali dati sono stati omessi.\n\nVector 1\n\nSostituire la \"proprietà\" con una licenza revocabile, in modo che i beni digitali possano essere ritirati in base all'accordo.\n\nVector 2\n\nIl sistema di applicazione automatica delle sanzioni (VACNet), i cui divieti, come indicato all’indirizzo Steam Support, non possono essere revocati.\n\nVector 3\n\nControlli sui conti e sugli asset, combinati con una commissione di mercato CS2 di 15% (5%, Steam e 10%, commissione per gli editori) che sottrae valore all’ecosistema ad ogni rivendita.\n\nAsimmetria dei termini\nRinuncia alla responsabilità e licenza revocabile\n2.1 Il modello dell’“abbonamento” contro i diritti di proprietà\n\nLa sezione 2 del Contratto di abbonamento a Steam concede agli utenti solo un licenza personale, non esclusiva, non trasferibile e revocabile. Ai sensi dell'accordo, Valve può chiudere gli account in qualsiasi momento e i saldi non utilizzati del portafoglio Steam potrebbero andare persi.\n\n2.2 L’illusione del rimborso contro la direttiva UE sui diritti dei consumatori\nQuadro giuridico\tMeccanismo di rimborso\tLimitazione\nEU Consumer Rights Directive\tUnconditional 14-day right of withdrawal on digital content\tWaived if download begins with explicit consumer consent\nSteam SSA\t14 days / under 2 hours played\tValve may deny at its discretion for \"abuse\"\nValutazione\n\nValve l'UE subordina il diritto di recesso previsto dalla legge, di 14-giorni, alla propria finestra temporale di \"14 giorni / entro 2 ore\", che deve essere accettata al momento del download prima che il prodotto possa essere valutato. Tale politica restringe — e non estende — il diritto previsto dalla legge; se ciò avvenga in modo legittimo è una questione che spetta all'autorità competente, non una conclusione qui affermata.\n\nContenzioso\nMercato secondario e antitrust\nUFC Que Choisir contro Valve — Francia\n2019\nTribunale di Parigi: la dottrina dell’esaurimento dei diritti si applica ai giochi digitali — la rivendita è lecita\nOttobre 2022\nLa Corte d'appello di Parigi ribalta la sentenza\n23 Ottobre 2024\nCorte di cassazione (Corte Suprema): i videogiochi sono “opere complesse” ai sensi della direttiva InfoSoc, non software. Rivendita digitale vietato. Prevale \"Valve\".\nCaso antitrust Wolfire Games — Stati Uniti (In re Valve Antitrust Litigation, n. 2:21-cv-00563)\n\nLa clausola “Nazione più favorita” (PMFN) di Valve impedisce agli sviluppatori di vendere le chiavi “Steam” a un prezzo inferiore su qualsiasi altra piattaforma. I negozi concorrenti — anche quelli che applicano una commissione 12% rispetto a quella di Valve 30% — non possono trasferire il risparmio ai consumatori.\n\n336numero totale di dipendenti di Valve (2021). Fonte: atti processuali resi pubblici.\n79dipendenti incaricati della gestione dell'intera piattaforma Steam. Fonte: atti processuali resi pubblici.\n$3.5Mutile netto per dipendente. Fonte: atti processuali resi pubblici.\n\nI documenti relativi alla fase istruttoria, ora resi pubblici, mostrano che $8.5B di ricavi lordi nel 2021 sui dipendenti dell'336. Il 79-persona Steam team ha gestito 373,000+ i ticket di assistenza giornalieri, inoltrandoli a call center automatizzati e in outsourcing.\n\nALLEGATO DEL FASCICOLO NON RISERVATO · W.D. WASH. CAUSA N. 2:21-CV-00563Memo interno di indagine\n\nTim Sweeney (amministratore delegato di Epic Games) a Gabe Newell: \"Perché Steam continua a trattenere l'30%% del fatturato lordo, quando l'elaborazione dei pagamenti costa 2–5% e la larghezza di banda CDN costa $0.002/GB? Se si escludono i giochi più popolari 25 su Steam, scommetto che Valve ha realizzato più profitti dalla maggior parte dei titoli successivi 1,000 rispetto agli stessi sviluppatori.\"\n\nScott Lynch (Direttore operativo, Valve Corporation) – nota interna indirizzata a Gabe Newell: \"Sei arrabbiato, fratello?\"\n\nContestazione della deposizione giurata (Bloomberg, 2026): Ai sensi dell’articolo 30, comma (b), punto 1, durante la deposizione, Gabe Newell ha testimoniato che \"Valve non ha una politica né una prassi volta a imporre i prezzi agli sviluppatori di software di terze parti su altre piattaforme.\" I ricorrenti hanno contestato a Newell alcune note interne di Valve che dimostravano l’esistenza di un’attiva politica di controllo dei prezzi e di minacce di esclusione dall’elenco nei confronti degli sviluppatori che praticavano prezzi inferiori su negozi concorrenti. Alla fine di marzo 2026, il Tribunale Federale ha respinto la richiesta di sentenza sommaria presentata da Valve, rinviando l’azione collettiva degli sviluppatori 32,000-a un processo con giuria.\n2024 di novembre\n\nAmmissione dell'azione collettiva per ~ Gli sviluppatori di32,000 che ha versato commissioni a partire da gennaio 2017,, oltre a un’azione collettiva parallela intentata dai consumatori.\n\nRisarcimento richiesto\n\n$3.1B\nTriplicato ai sensi della normativa antitrust statunitense = $9.3B potenziale esposizione.\n\n2026: di giugno Una nuova causa sostiene che Microsoft e Valve abbiano stipulato un accordo di cartello volto a limitare la concorrenza nella distribuzione di giochi per PC.\n\nAmmissione ufficiale al corso \"Reati finanziari e antiriciclaggio\"\nValve Confessione ufficiale: Liquidazioni per frodi a livello mondiale (28 ottobre 2019)\n\nIl 28 ottobre 2019, Valve ha ufficialmente sospeso lo scambio e la rivendita sul marketplace delle chiavi dei container di Counter-Strike appena acquistate. Nel suo annuncio pubblico ufficiale (blog.counter-strike.net/2019/10/26113), la Valve Corporation ha ammesso per iscritto che l’economia virtuale da essa ideata era diventata una piattaforma internazionale per il riciclaggio di denaro:\n\n\"In passato, la maggior parte delle transazioni di chiavi che abbiamo osservato avveniva tra clienti in buona fede. Tuttavia, le reti fraudolente internazionali hanno recentemente iniziato a utilizzare le chiavi di CS:GO per liquidare i propri proventi. A questo punto, si ritiene che quasi tutti gli acquisti di chiavi che finiscono per essere scambiati o venduti sul mercato provengano da attività fraudolente.\"\n\nContesto normativo: Questa ammissione è arrivata in seguito all’ultimatum formale rivolto dalla Commissione per il gioco d’azzardo dello Stato di Washington (WSGC) a Valve e agli ordini di cessazione e desistenza emessi a luglio 2016 dal consulente legale generale di Valve, Karl Quackenbush, nei confronti dei domini di gioco d’azzardo basati su skin di 23 (tra cui CSGO Lotto, CSGOLounge e OPSkins), solo dopo che un’indagine penale sul gioco d’azzardo aveva messo a rischio le operazioni della piattaforma.\n\nCompetenza giurisdizionale\nUn titolare dei diritti in Russia, irraggiungibile per l'utente\n\nL’Accordo di abbonamento presenta Valve come una parte che deve ben poco e che nessuno può contattare: i blocchi sono permanenti, i ricorsi vengono respinti e l’accesso viene revocato a interi territori con una sola riga sulle «regioni soggette a sanzioni». A contrapporsi a tale atteggiamento c’è ciò che fa Valve quando sono in gioco i propri interessi commerciali in una giurisdizione che altrimenti considera problematica.\n\nValve v. Touch Skins — rivendicazione di proprietà intellettuale in fase preprocessuale, Russia\n1 2026 di settembre\nValvee, tramite lo studio legale russo Melling, Voitishkin & Partners, invia una lettera di diffida preliminare ai gestori di Skin tattili, un grande dispositivo per il cambio di pelle CS2, tramite posta russa e via e-mail.\nMotivi\nTre categorie di presunte violazioni: i diritti esclusivi sul software; i diritti relativi all’aspetto delle skin di armi, coltelli e guanti; e i marchi registrati di Valve. La condotta degli operatori è definita come intenzionale e prolungata.\nDomanda\nInterrompere immediatamente il funzionamento ed eliminare l'intera infrastruttura — il software codice sorgente, siti web e pagine sui social media — in caso contrario, Valve si riserva il diritto di adire un tribunale russo per un risarcimento monetario consistente e di deferire la questione a forze dell'ordine ai fini di una valutazione penale.\nRisultato\nDopo aver ricevuto la lettera, la piattaforma ha annunciato la chiusura del servizio. Si tratterebbe del primo caso in cui l’Valve abbia fatto ricorso a strumenti legali contro uno sviluppatore di skin-changer in Russia.\n\nNotizia riportata dal data miner Maxim \"GabeFollower\" Poletaev (X, ~11 2026) e dalla stampa russa specializzata in videogiochi. Si tratta di una richiesta preliminare al processo, non di una causa intentata; non è stato reso pubblico alcun numero di registro. La notizia viene qui riportata così come è stata diffusa, non come atto processuale. Fonti: dota2.ru archiviato su 2026-09-24 ↗ · Shazoo.\n\nLa stessa giurisdizione, ma nella direzione opposta\n\nValve non è estraneo al sistema giuridico e normativo russo. Esso è conforme alle disposizioni di Roskomnadzor: su richiesta dell'autorità di regolamentazione, ha rimosso le pagine della community 260+ Steam che contenevano materiale vietato, e Roskomnadzor ha dichiarato pubblicamente che Steam soddisfa i requisiti di legge. La legge russa sul “landing” (Legge federale 236-FZ, in vigore dal 2022), impone alle grandi piattaforme Internet straniere che servono utenti russi di stabilire una presenza locale e di aprire un account di contatto presso il Roskomnadzor. Valve non solo ottempera agli ordini di rimozione emanati dall'autorità di regolamentazione, ma ora si avvale anche di consulenti legali russi e ricorre alla minaccia dei tribunali russi per proteggere le proprie skin in quanto proprietà intellettuale.\n\nLa piattaforma, quindi, è accessibile, efficiente e fa valere i propri diritti proprio quando si tratta dei propri ricavi. Il contrasto è con l’utente: a un cliente pagante in una regione soggetta a sanzioni viene comunicato che il rapporto è terminato, l’accesso alla community viene bloccato fino a quando 2038, il ticket non viene chiuso, e non esiste alcun forum in cui la decisione possa essere contestata — \"Erano più che felici di prendere i miei soldi e di elaborare le mie transazioni\", dato che il rimborso relativo allo stesso account, proveniente dallo stesso indirizzo IP iraniano, era stato approvato un anno prima (r/pcgaming, 4 8 agosto 2026; altre lettere di sollecito in la mostra sull’economia delle carte). Valve ricorre a tutti gli strumenti di un sistema giuridico nazionale per difendere una skin; non garantisce alcuna procedura all’utente che ha acquistato le skin.\n\nValve considera quella stessa giurisdizione come un ambito in cui può agire e a cui deve attenersi ogni volta che l’interesse in gioco è quello di Valve — consulenti legali russi, minaccia dei tribunali russi, ordini di rimozione emessi da Roskomnadzor — mentre considera i propri obblighi nei confronti degli utenti di quel mercato, e di ogni altro, come al di fuori di qualsiasi procedura. È un titolare di diritti quando si tratta dei propri ricavi e una parte irraggiungibile quando si tratta dei diritti degli utenti.\n\nFonti: TASS (RKN: Steam è conforme) · Legge federale 236-FZ.\n\nOpportunismo giuridico\nLa capitolazione sulla clausola arbitrale\n2023 — l’attacco\n\nGli studi legali (Zaiger LLC, Mason LLP) hanno reclutato migliaia di utenti tramite i social media e hanno presentato contemporaneamente decine di migliaia di richieste di arbitrato individuali.\n\nL'esposizione di Valve\n\n$225M+\nin spese di deposito per l'arbitrato non rimborsabili, prima ancora che la causa fosse esaminata nel merito. Calcolato in base alle Norme di arbitrato in materia di consumo dell’American Arbitration Association (AAA) e alle Tabelle supplementari sull’arbitrato di massa. I ricorrenti, rappresentati da Zaiger LLC e Mason LLP, hanno presentato circa75,000 richieste di arbitrato individuali nei confronti di Valve Corp. (parallelamente alle azioni antitrust in Wolfire Games LLC e altri contro Valve Corp., Causa n. 2:21-cv-00563-JCC, W.D. Wash.). In base alle tariffe dell’AAA per i consumatori, l’azienda convenuta è tenuta a pagare spese amministrative non rimborsabili relative al caso e depositi per la nomina dell’arbitro pari a circa $3,000+ per ogni singolo caso (75,000 depositi × $3,000 = circa $225M di oneri procedurali anticipati). Si vedano i rapporti legali di Bloomberg Law e Reuters sull’esposizione alle procedure di arbitrato di massa nel settore tecnologico (2023–2024).\n\nPeriodo\tMeccanismo di risoluzione delle controversie della SSA\tEffetto osservato\tRisultato\nBefore Sep 2024\tMandatory individual arbitration + class-action waiver\tIndividual litigation becomes economically irrational for users\tMass arbitration → $225M fee threat\nAfter Sep 2024\tDisputes in King County, WA courts only\tArbitration costs are avoided; cases consolidate in a single forum\tClass actions now possible\nConclusione\n\nPer oltre dieci anni la SSA ha imposto agli utenti di rinunciare al proprio diritto a un processo con giuria a favore dell’arbitrato individuale. Dopo che le richieste di arbitrato di massa hanno reso tale meccanismo economicamente oneroso per l'Valve, la SSA è stata modificata per deferire le controversie ai tribunali della contea di King. La modifica è stata presentata senza una possibilità di rinuncia significativa; l'alternativa all'accettazione era la perdita dell'accesso alle risorse digitali acquistate tramite la cancellazione dell'account.\n\nApplicazione algoritmica\nVACNet, presunzione di colpevolezza e falsi positivi\n2023, ottobre — AMD Anti-Lag+\n\nUn aggiornamento del driver AMD (v23.10.1) ha attivato la funzione Anti-Lag+ in CS2, che ha intercettato le funzioni DLL del gioco. VAC ha classificato questo evento come iniezione di codice di cheat e ha inflitto ban permanenti a migliaia di utenti legittimi prima che Valve intervenisse.\n\n2023, dicembre — alta risoluzione (DPI)\n\nI giocatori con un valore DPI superiore a 10,000 che ruotavano rapidamente la telecamera sono stati banditi in modo permanente. VACNet non era in grado di distinguere il movimento fisico del mouse da un cheat di tipo \"spinbot\".\n\nCategoria di assistenza\tTempo di risposta dichiarato\tRisultato effettivo\nRefund requests\t50 min – 1.5 hr\tAutomatic approval (<14 days, <2 hours played)\nAccount security / recovery\t3–12 hours\tDepends on documentation provided\nContesting a VAC ban\tForm response\tComplete refusal. Support cannot reverse VAC decisions. The ban is permanent.\nPolitica ufficiale dell'Valve\n\n\"I blocchi VAC sono permanenti, non negoziabili e non possono essere rimossi dal Supporto di Steam.\"\n\nLo stesso canale di assistenza che comunica il ban comunica anche il rifiuto della revisione: Steam L'assistenza afferma di non poter revocare una decisione del VAC. Per l'utente, il verdetto dell'algoritmo è il risultato definitivo.\n\nAspetti economici della rivendita\nIl controllo sui beni virtuali e la commissione di rivendita\nLa commissione di mercato di 15% CS2 — importo detratto ad ogni rivendita\nIterazione\tSaldo dell'acquirente\tIl venditore riceve\tBruciato (15%)\n1\t$100.00\t$85.00\t$15.00\n2\t$85.00\t$72.25\t$12.75\n3\t$72.25\t$61.41\t$10.84\n10\t$23.16\t$19.68\t~$3.47\nTotal\t$100 → dust\tValve collects the 15% fee on each resale. Users must add new money to keep trading.\nModifica alle regole di sostituzione del CS2 — Ottobre 2025\n\nSenza preavviso, Valve ha modificato le regole del contratto di permuta di CS2 per consentire l’acquisizione garantita di coltelli e guanti rari in cambio di oggetti di qualità “Covert”. I prezzi dei coltelli sono crollati, quelli degli oggetti “Covert” sono saliti vertiginosamente e ne è seguita un’ondata di vendite dettate dal panico in tutto il mercato.\n\nLa tutela invocata da Valve è la Sezione 7 della SSA — nessuna responsabilità per la modifica delle regole della piattaforma. Gli utenti si assumono il rischio in un’economia le cui regole Valve possono cambiare senza preavviso né risarcimento. L’entità della perdita a livello di mercato riportata è contestata e non viene indicata in questa sede in assenza di una fonte primaria.\n\nRisposta normativa europea\nUOKiK, DSA e la legge sull’equità digitale\nUOKiK — Polonia, maggio 2024\n\nL’autorità antitrust polacca (UOKiK) ha avviato un procedimento antitrust formale nei confronti dell’Valve Corporation e di cinque editori/distributori di videogiochi nazionali in relazione a presunte pratiche di fissazione dei prezzi, clausole restrittive di parità dei prezzi e pratiche di geoblocco che hanno indotto i consumatori polacchi a pagare fino a 20% in più per i videogiochi digitali rispetto ai mercati limitrofi del SEE. Nell’ambito dell’indagine antitrust, gli ispettori dell’UOKiK e le forze dell’ordine hanno effettuato perquisizioni all’alba e ispezioni probatorie presso le sedi polacche degli editori e distributori partner nazionali (non presso le filiali dell’Valve, poiché l’Valve non possiede alcuna entità in Polonia). Potenziale sanzione amministrativa: fino al 10% del fatturato annuo. Fonte: Comunicato ufficiale dell’UOKiK, “Il presidente dell’UOKiK ha avviato un procedimento nei confronti di Valve e degli sviluppatori di videogiochi”, maggio 2024.\n\nLegge sui servizi digitali (DSA)\n\nRichiede trasparenza nella moderazione automatizzata. Steam non pubblica dati relativi a falsi positivi o falsi negativi per VACNet, e il suo canale di assistenza precisa che le decisioni di VAC non possono essere revocate.\n\nDigital Fairness Act — 2026\n\nDisposizioni previste: accesso duraturo ai contenuti a pagamento, divieto di ricorrere a “dark patterns” al momento della rinuncia ai diritti, riconoscimento dei diritti di proprietà sui beni digitali e tutela contro la confisca definitiva delle scorte.\n\nConclusione\nDiscrepanze documentate tra le norme e i dati registrati\n1\n\nIl divario nella proprietà. Gli utenti pagano il prezzo pieno per una licenza che il contratto consente a Valve di revocare. La Corte di cassazione francese (2024, ottobre) ha stabilito che la rivendita digitale non è tutelata, sancendo tale posizione nella legislazione.\n\n2\n\nApplicazione algoritmica. VACNet ha emesso sospensioni ingiustificate (driver AMD, casi di DPI elevato). Il supporto di Steam afferma di non poter revocare una decisione di VAC, quindi l'algoritmo ha l'ultima parola.\n\n3\n\nRisparmio sulle commissioni. La commissione di mercato di 15% CS2 (5% Steam + 10% commissione dell'editore) riduce il valore ad ogni rivendita, e le regole della piattaforma possono cambiare senza preavviso; ai sensi dell'SSA, Valve declina ogni responsabilità per tali modifiche.\n\n4\n\nClausola arbitrale eliminata. A settembre, la SSA ha abolito l’arbitrato obbligatorio 2024, dopo che una serie di ricorsi collettivi aveva esposto Valve a commissioni pari a circa $225M. Agli utenti non è stata offerta alcuna possibilità concreta di rinunciare a tale modifica.\n\n5\n\nCompetenza selettiva. Valve ha incaricato uno studio legale russo (Melling, Voitishkin & Partners) e ha minacciato di avviare un procedimento giudiziario in Russia contro Touch Skins, considerando al contempo che i propri obblighi nei confronti degli utenti di quello stesso mercato esulassero da qualsiasi procedimento giudiziario. Valve agisce come titolare dei diritti laddove sono in gioco i propri interessi commerciali e come parte irraggiungibile laddove sarebbero in gioco i diritti degli utenti.\n\n← Parte I: Aggirare i proxy e il gioco d’azzardoParte II: Accesso e responsabilità →\n\nLe fonti giuridiche e gli atti processuali sono citati facendo riferimento agli editori e agli archivi originali. Non viene rivendicata alcuna titolarità sui documenti sottostanti.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Analisi giuridica — Condizioni di servizio e conformità normativa"
          },
          {
            "level": 2,
            "id": null,
            "text": "Rinuncia alla responsabilità e licenza revocabile"
          },
          {
            "level": 3,
            "id": null,
            "text": "2.1 Il modello dell’“abbonamento” contro i diritti di proprietà"
          },
          {
            "level": 3,
            "id": null,
            "text": "2.2 L’illusione del rimborso contro la direttiva UE sui diritti dei consumatori"
          },
          {
            "level": 2,
            "id": null,
            "text": "Mercato secondario e antitrust"
          },
          {
            "level": 3,
            "id": null,
            "text": "UFC Que Choisir contro Valve — Francia"
          },
          {
            "level": 3,
            "id": null,
            "text": "Caso antitrust Wolfire Games — Stati Uniti (In re Valve Antitrust Litigation, n. 2:21-cv-00563)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve Confessione ufficiale: Liquidazioni per frodi a livello mondiale (28 ottobre 2019)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Un titolare dei diritti in Russia, irraggiungibile per l'utente"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve v. Touch Skins — rivendicazione di proprietà intellettuale in fase preprocessuale, Russia"
          },
          {
            "level": 3,
            "id": null,
            "text": "La stessa giurisdizione, ma nella direzione opposta"
          },
          {
            "level": 2,
            "id": null,
            "text": "La capitolazione sulla clausola arbitrale"
          },
          {
            "level": 2,
            "id": null,
            "text": "VACNet, presunzione di colpevolezza e falsi positivi"
          },
          {
            "level": 2,
            "id": null,
            "text": "Il controllo sui beni virtuali e la commissione di rivendita"
          },
          {
            "level": 3,
            "id": null,
            "text": "La commissione di mercato di 15% CS2 — importo detratto ad ogni rivendita"
          },
          {
            "level": 3,
            "id": null,
            "text": "Modifica alle regole di sostituzione del CS2 — Ottobre 2025"
          },
          {
            "level": 2,
            "id": null,
            "text": "UOKiK, DSA e la legge sull’equità digitale"
          },
          {
            "level": 2,
            "id": null,
            "text": "Discrepanze documentate tra le norme e i dati registrati"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/it/#briefing-heading",
          "https://dota2.ru/news/67707-valve-cerez-uristov-napravila-krupnoj-rossijskoj-skincendzer-platforme-trebovanie-o-prekrasenii-deatelnosti/",
          "http://web.archive.org/web/20260924181657/https://dota2.ru/news/67707-valve-cerez-uristov-napravila-krupnoj-rossijskoj-skincendzer-platforme-trebovanie-o-prekrasenii-deatelnosti/",
          "https://shazoo.ru/2026/09/12/190508/valve-cerez-rossiiskix-iuristov-dobilas-zakrytiia-krupnogo-skinceindzera-dlia-cs2",
          "https://www.reddit.com/r/pcgaming/comments/1vf24lu/warning_to_all_gamersexpats_steam_took_my_money/",
          "https://phishdestroy.io/steam_dossier/it/card_economy.html#asymmetry",
          "https://tass.ru/obschestvo/23235387",
          "https://base.garant.ru/401414628/",
          "https://uokik.gov.pl/postepowanie-wyjasniajace-w-sprawie-valve-i-dystrybutorow-gier",
          "https://phishdestroy.io/steam_dossier/it/",
          "https://phishdestroy.io/steam_dossier/it/investigation_part2.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/it/legal_analysis.content.json",
      "export_json_sha256": "8a4ff608d8ce68c0ad67a1f56672a3f3e207f4b8261ae6c93616cab6de6b6c3b"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "it/license_disclaimer.html",
      "language": "it",
      "title": "Licenza · Diritti · Dichiarazione di non responsabilità — PhishDestroy",
      "source_url": "https://phishdestroy.io/steam_dossier/it/license_disclaimer",
      "source_html_sha256": "5cb9bf925f120bd9006b05dd673bc4e4f4bf0fcaa79efb22d0193c573f58e5a8",
      "exported_at": "2026-09-29T00:17:52.355Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "license_disclaimer.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/it/license_disclaimer.pdf?v=print-20260929-v5",
        "sha256": "96f77107d3dd71d424e0b9d9495a2a7899522d09a8ee94b253ae4fc10df62e6a",
        "bytes": 117772,
        "pages": 11
      },
      "integrity": {
        "signed_object": "license_disclaimer.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "license_disclaimer.content.json.asc",
        "digest_file": "license_disclaimer.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify license_disclaimer.content.json.asc license_disclaimer.content.json",
          "sha256sum -c license_disclaimer.content.json.sha256"
        ]
      },
      "content": {
        "text": "PHISHDESTROYIndagini forensi · Valve / Steam\nLicenza · Diritti · Dichiarazione di non responsabilità\nLicenza e dichiarazione di non responsabilità — Dedicazione al pubblico dominio\n\nTutti i diritti si è arreso all'umanità.\n\nCOSA DIMOSTRA QUESTA SEZIONE\n\nIl presente documento stabilisce la cessione incondizionata al pubblico dominio (CC0 1.0 Universal) e i termini di licenza del software MIT che regolano il Dossier PhishDestroy Steam. Tutti i risultati delle analisi forensi, i set di dati probatori, i grafici di rete e le metodologie analitiche sono irrevocabilmente ceduti al pubblico dominio per un utilizzo senza restrizioni a fini normativi, legali e accademici in tutto il mondo.\n\n← Torna al briefing esecutivo\n\nPhishDestroy rinuncia a ogni diritto su questo materiale: riprodurlo, venderlo, apporvi il proprio nome. Quello che segue sono due documenti presentati come se fossero stati redatti da un’unica voce: una lettera aperta indirizzata a Valve, scritta nel modo in cui scriviamo realmente, e una rinuncia formale redatta per l’autorità che porterà avanti il progetto.\n\nIndagine · Valve Corporation / SteamEdizione pubblica — senza scadenza, senza possibilità di revoca\nESENTATO\nSezione ILicenza — la parte strettamente giuridica, ma dal punto di vista umano\n\nPhishDestroy rinuncia a ogni diritto su questo materiale. Zero. Sparito. Finito. Puoi riprodurlo, venderlo, metterci il tuo nome, tatuarlo sul tuo capo, quello che vuoi. Non serve citare la fonte, non serve mandare un messaggio privato, non ci si aspetta nemmeno un biglietto di ringraziamento.\n\nUna regola vera e propria (sì, solo una)\n\nNon spetta a TE decidere se sei un terrorista.\n\nSe sei un utente proveniente dalla Russia o da qualsiasi altro Paese soggetto a sanzioni OFAC, questo materiale NON è destinato a te. Non ci sono scappatoie. Goditi le tue sanzioni.\n\nE se hai cambiato la regione di Steam impostando la Turchia mentre ti trovavi a Mosca — complimenti per la tua creatività in materia di geografia. Sei comunque russo. Le sanzioni valgono comunque. È proprio questo il punto.\n\nSezione IIChe cos’è e perché esiste\n\nPubblicheremo più informazioni su Valve di quante ne conosca un dipendente medio di Valve su se stesso. Non è per vantarci. È semplicemente quello che è successo.\n\nCome siamo arrivati a questo punto? È una storia buffa: in pratica è stato Steam a darci vita. Ci ha cresciuti a pane e truffatori, ticket di assistenza e quell’ecosistema dedicato all’aggiramento dei ban… ed eccoci qui. Nessun rancore. Anzi, è quasi poetico.\n\nPer chi non avesse ancora letto la storia delle origini, abbiamo già conosciuto gli avvocati europei estremamente costosi di “Valve” (Taylor Wessing, visto che lo avete chiesto):\n\nhttps://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d archiviato su 2026-08-21 ↗\n\nUn incontro affascinante. Soprattutto considerando la loro tariffa oraria.\n\nValve, lo sapeva? Sì. Taylor Wessing, lo sapeva? Quasi certamente sì. Ma quando si è così ricchi, le leggi sono più una questione di atmosfera che un obbligo, giusto?\n\nIn realtà, questa è più o meno tutta la risposta.\n\nSteam Abbiamo passato anni a smascherare i truffatori. Non sempre intenzionalmente: a volte i truffatori finivano per avere le impronte digitali di “Valve” addosso solo per associazione. Non stiamo cercando di essere drammatici. Stiamo cercando di essere precisi. Ad essere onesti, per noi è più difficile essere precisi che essere drammatici: è semplicemente il nostro modo di scrivere.\n\nSi tratta di un conflitto?\n— No.\n\nSi può risolvere?\n— Sì. Ma non firmeremo nessun accordo di riservatezza e non parteciperemo a programmi di bug bounty per quattro soldi.\n\nAbbiamo aspettato più di 4 anni affinché risolvessero il problema dello spoofing prima di poterlo rendere pubblico. Perché se ne avessimo parlato prima, Steam avrebbe assunto la sua solita aria da vittima, gridando “minaccia attiva!” e offrendoci spiccioli per firmare un documento che ci avrebbe resi loro proprietà legale per sempre. No, grazie.\n\n(Inoltre: è proprio l’Valvea a violare l’accordo di riservatezza. Lo fanno i loro stessi dipendenti. Quelli ai vertici. Ma certo, parliamo dei nostri.)\n\nSezione IIILettera aperta a Valve — sul serio, leggilo\n\nValve: se desiderate che questo dominio venga rimosso, inviateci un’e-mail. Per questa comunicazione non è necessario ricorrere a un consulente legale esterno.\n\nPer chi non lo sapesse: il dottor Patrick ha conseguito un Master in Diritto Commerciale Internazionale presso l’Università di Aberdeen e — tenetevi forte — ha letteralmente completato la sua tesi di dottorato in diritto informatico. Recentemente è diventato socio dello studio Taylor Wessing, un’azienda il cui intero modello di business consiste nel fatturare a società come Valve somme esorbitanti per trascinare le cause fino a quando la controparte non esaurisce i fondi o la pazienza.\n\nNon lo biasimiamo. Clienti ricchi e in difficoltà che pagano a ore: una mossa professionale azzeccata. Semplicemente, non crediamo che dovreste finanziarla.\n\nL'accordo (offerta aperta, non servono avvocati)\n\nIl dominio è l'unica cosa che Valve possa realisticamente ottenere. L'indagine, i rinvii e le risorse correlate sono già in corso: proseguiranno con o senza il dominio.\n\nSe desideri il dominio:\n\nLascia che siano i tuoi esperti in diritto informatico a stabilire un prezzo equo.\n\n50% viene devoluto alla Fondazione “SEAL”.\n\nChiudiamo il dominio. Niente drammi. Niente tribunale. Fatto.\n\nQuesta non è una minaccia. È una semplice offerta per l’unica cosa che è effettivamente alla tua portata. Non la otterrai in nessun altro modo: è proprio così che stanno le cose.\n\n“Danneggeremo” direttamente l’Valve? Probabilmente no, almeno non in modo che se ne accorgano dal punto di vista finanziario. Non ci facciamo illusioni. Ma lo faremo in modo onesto, trasparente, senza cercare di ottenere popolarità — perché non ne abbiamo bisogno. Abbiamo bisogno che il mondo veda ciò che è sempre stato sotto gli occhi di tutti, se solo ci si fosse presi il tempo di guardare con attenzione.\n\nAbbiamo archivi che coprono un periodo di5i anni. Quanto mostrato dagli avvocati di Valve durante la fase istruttoria — i dati a cui hanno accesso gli agenti, le impronte digitali, la documentazione cartacea che ci hanno letteralmente consegnato — è sufficiente. Non c’è bisogno di divulgarli così come sono.\n\nA chi spetta cosa\n\nLe autorità di regolamentazione ricevono i documenti originali.\n\nAi ricercatori e ai giornalisti vengono fornite versioni censurate (in cui, per ovvie ragioni, sono state rimosse le testimonianze delle vittime, i dati di accesso dei bambini e l’affascinante commento di supporto di Valve).\n\nTra gli account compromessi figuravano anche quelli di minori, ai quali non è stata data alcuna comunicazione. Tale constatazione è contenuta nel fascicolo destinato all’autorità di regolamentazione, dal quale sono state rimosse le segnalazioni delle vittime e le credenziali, poiché è una questione che deve essere trattata dall’autorità garante della protezione dei dati piuttosto che in un articolo.\n\nInoltre, Valve — vogliamo chiarire una cosa prima che decidiate come gestire la situazione: PhishDestroy è una comunità, non una persona. Lo avete capito quando avete inviato una comunicazione legale alla comunità senza nemmeno preoccuparvi di parlare con i suoi membri — vi siete limitati a sfruttare la situazione per ottenere dati e poi avete bannato gli account.\n\nLa comunità non ha alcun conflitto con Valve. Non siamo stati noi a cercarli. Sono stati i truffatori che avete fatto crescere a trovarci. Li abbiamo bloccati. Ed eccoci qui.\n\nSezione III-BLe risorse alleate — una nota rivolta specificatamente a Steam\n\nVogliamo essere chiari riguardo alla struttura di amplificazione, perché fingere che non esista sarebbe disonesto.\n\nPhishDestroy: da quanto ci risulta della situazione nella comunità, ci sono almeno due risorse alleate che raccoglieranno questo materiale e lo porteranno avanti.\n\nCosa significa in pratica:\n\nCiascuno di loro affronta a modo proprio argomenti che si sovrappongono.\n\nSono indipendenti: non seguono le nostre indicazioni e noi non seguiamo le loro. Stesso argomento generale, metodologia diversa.\n\nNon si attiveranno su Part1.. Stanno osservando.\n\nSe Valve decidesse di non rimuovere il sito:\n\nAspettatevi che compaiano dopo la Parte 2 o la Parte 3.\n\nPrenderanno ciò che è utile dal nostro lavoro, lo integreranno con il loro e lo pubblicheranno a loro nome.\n\nQuesto è esattamente il tipo di situazione per cui è stata concepita la licenza di cui alla Sezione 1: il materiale viene diffuso dove deve arrivare, viene integrato, viene ampliato — e né noi né loro siamo tenuti a citare la fonte.\n\n(P.S. Per gli avvocati che si interrogano sulle catene di responsabilità: non ce ne sono. Queste risorse non ricevono indicazioni, finanziamenti né dati da parte nostra. Si limitano a leggere ciò che è di dominio pubblico e a trarne le proprie conclusioni. Proprio come potreste fare voi.)\n\nNon lo diciamo per intimidire. Lo diciamo affinché chiunque stia elaborando strategie per conto di “Valve” disponga di informazioni accurate su come si presenta effettivamente il panorama informativo.\n\nUna risorsa che attinga al nostro materiale e lo integri potrebbe essere un articolo. Due risorse che lo facciano in modo indipendente e giungano a conclusioni simili costituiscono un modello. Sono proprio i modelli ad attirare l’attenzione delle autorità di regolamentazione.\n\nSezione IVI soldi, i divieti, tutto quel circo\n\nEcco il punto riguardo al divieto imposto dall’Steam ai siti di gioco d’azzardo e ai truffatori: non si tratta di applicazione della legge, ma di incasso di entrate. L’Valve si intasca i soldi, si lava le mani e poi sale sul palco per raccontare a tutti una storia edificante sulle carte Pokémon e sul baseball.\n\nLaddove sono stati documentati casi di compromissione da parte del supporto tecnico — tra cui l’ammissione scritta di “Valve” a febbraio 2023, in cui si assumeva la responsabilità per la compromissione di account di alto valore a seguito di richieste di assistenza, e i licenziamenti di personale a contratto segnalati da Dexerto ed Escorenews a seguito del caso di insider trading da $320k (Parte II, §04 · Dossier principale §14.1) — si basano su ammissioni rese pubbliche e su inchieste giornalistiche. Le voci infondate secondo cui alcuni membri del personale di supporto gestirebbero attività di gioco d’azzardo parallele o trarrebbero una percentuale per aggirare i divieti non trovano riscontro nei documenti pubblici e sono quindi escluse dal presente articolo.\n\nNel frattempo, Valve ha eliminato la possibilità di tracciare correttamente le skin su 2017.. Ne hanno persino discusso sui propri forum. L’hanno definita una “misura anti-gioco d’azzardo”, mentre l’ecosistema del gioco d’azzardo basato sulle skin ha continuato a far transitare miliardi attraverso l’infrastruttura di Steam per anni dopo. Ottima strategia di branding.\n\nDimostreremo che:\n\nLe \"skin\" garantiscono un livello di anonimato superiore rispetto a Monero\n\nUn cartello peruviano avrebbe utilizzato le skin di Dota 2 per trasferire denaro\n\nSteam è, in pratica, un sistema per aggirare le sanzioni del valore di circa $7B in “figurine” (sì, hanno davvero parlato di figurine davanti a un pubblico ministero)\n\nAbbiamo un video su quella faccenda delle skin. Lo vedrai.\n\nSappiamo inoltre che:\n\nLa moderazione su Reddit è influenzata da Valve\n\nInfrastruttura dati di terze parti per l’Steame (ad esempio steamid.uk) è gestito da un privato (msart) il cui progetto gemello, dedicato alla lista dei ban (steambans.com archivio) è gestito in collaborazione con un moderatore confermato della comunità Valve (killahinstinct_) — lasciando la verifica indipendente delle sospensioni dalla piattaforma interamente nell’ambito di competenza dell’Valve (vedi “Card Economy”, paragrafo “08”)\n\nCiò che non riescono a controllare, lo vietano\n\nValve: se continui a fare finta di niente, va bene. Abbiamo preso nota del tuo “porto sicuro”. Google Analytics rende comunque anonimi gli indirizzi IP dei tuoi utenti. Noi vediamo cosa viene cancellato. Semplicemente non riusciamo a dimostrarlo in modo abbastanza economico da suscitare l’interesse dei tuoi avvocati. Almeno per ora.\n\nSezione VLa questione del malware — sì, ne stiamo parlando\n\nCerchiamo di essere estremamente chiari riguardo alla sequenza degli eventi, perché questa rivela esattamente chi sei.\n\nNON renderemo pubblica la vulnerabilità presente nel gioco. NON la segnaleremo all’Steam. Il programma richiede un accordo di riservatezza (NDA) e la sua sottoscrizione ci impedirebbe di comunicare agli utenti interessati cosa sia successo ai loro account. Lo scopo di questo lavoro è proprio quello di informare le persone che hanno perso i propri account e le autorità di regolamentazione; un accordo di riservatezza è incompatibile con tale obiettivo.\n\nEcco cosa è successo in realtà: questa vulnerabilità è praticamente un segreto di Pulcinella negli ambienti che ne sono a conoscenza. Sappiamo per certo che alcuni ricercatori indipendenti nel campo della sicurezza hanno già sbattuto in faccia all’AssistenzSteama l’exploit completo. Quella parte è già stata fatta. Siete stati ufficialmente avvertiti attraverso i vostri stessi canali formali.\n\nE cosa ha fatto “Valve”? Assolutamente nulla. Perché per “Valve”, la sicurezza non equivale a profitto — anzi, è esattamente il contrario. La sicurezza è un centro di costo. Finché una minaccia non raggiunge una massa critica e provoca un crollo catastrofico dell’immagine pubblica, “Valve” non la considera urgente.\n\nAllora, cosa stiamo facendo? Stiamo informando l'opinione pubblica della sua esistenza, perché il fatto che “Valve” sia a conoscenza di una minaccia malware sistemica e scelga attivamente di non intervenire è un dato fondamentale per le autorità di regolamentazione che stanno leggendo questo articolo.\n\nIl gioco è davvero imponente. Non ne riveleremo il nome qui. Ma tenete presente questo:\n\nNon si tratta affatto di quella banale schifezza da script-kiddie di CS:GO in cui un server ti chiede di “installare un driver”. È una cosa catastrofica.\n\nÈ un incubo degno di Unturned: RCE zero-click al momento della connessione al server. Ti connetti a un server. Non clicchi su nulla. Non scarichi nulla. La connessione stessa è la superficie di attacco e il tuo computer è completamente compromesso. Siamo realistici: iniettare un RCE e aggirare gli antivirus locali sfruttando i certificati digitali affidabili di Valve non è più nemmeno una novità su Steam. È praticamente una funzionalità integrata nel tuo ecosistema.\n\nValve sa già che esiste. Ma si affidano alla loro scappatoia legale preferita e codarda: poiché il gioco è tecnicamente sviluppato da una terza parte, Valve se ne lava le mani. Distribuiscono il gioco, gestiscono i pagamenti, ospitano l’infrastruttura, ma quando un RCE zero-click minaccia milioni dei loro utenti, la loro posizione è: «Non è il nostro gioco, non è una nostra responsabilità».\n\nQuando la situazione inevitabilmente esploderà, sarà lo sviluppatore di terze parti a pagare le conseguenze, mentre Valve se ne andrà fingendo di essere la piattaforma responsabile che ha “contribuito” alla risoluzione del problema. La classica vigliaccheria di Valve. Abbiamo già visto questo copione.\n\nLo mettiamo nero su bianco affinché le autorità di regolamentazione, i pubblici ministeri e i giornalisti comprendano esattamente come Valve gestisca il malware attivo: nascondendosi dietro sviluppatori di terze parti, imponendo accordi di riservatezza (NDA) e lasciando gli utenti in balia degli eventi.\n\nFine della lettera apertaInizia il registro formale\nRegistro formale · per l'autorità\nDichiarazionePer quanto riguarda l'uso e i diritti\n\nPhishDestroy Coalizione per i progetti e la sicurezza informatica\n\nLa presente dichiarazione accompagna ogni documento presentato e ogni allegato contenuto nel presente fascicolo. È indirizzata a qualsiasi autorità, tribunale, ente regolatore, pubblico ministero, ricercatore, giornalista o persona interessata a cui il materiale dovesse pervenire.\n\n1. Non vi sono condizioni di utilizzo\n\n1.1 Tutto il materiale prodotto dalla Coalizione nell'ambito del presente ricorso — le esposizioni dei fatti, l'analisi, gli allegati da essa redatti, gli strumenti e le conclusioni — viene reso pubblico SENZA RISERVA DI ALCUN DIRITTO.\n\n1.2 Chiunque può, senza chiedere il permesso e senza avvisarci:\n\nriprodurlo, in tutto o in parte;\n\nadattarlo, modificarlo, riscriverlo, riorganizzarlo o correggerlo;\n\ntraducilo;\n\nriprodurne un estratto senza indicare che si tratta di un estratto;\n\ninserirlo in documenti ufficiali, conclusioni, decisioni, memorie, relazioni o comunicati stampa;\n\npresentarlo come un lavoro o una scoperta del destinatario stesso;\n\nutilizzarlo come materia prima e scartare il resto;\n\ne trasmetterla a chiunque altro alle stesse condizioni.\n\n1.3 NON È RICHIESTA NÉ PREVISTA ALCUNA ATTRIBUZIONE. Non è necessario menzionare, citare, attribuire il merito, ringraziare, consultare o informare la Coalizione. Se il materiale tratto da questo riferimento è d’aiuto a un’autorità e la Coalizione non viene mai menzionata, QUESTO È UN RISULTATO PERFETTAMENTE SODDISFACENTE e la Coalizione lo dichiara in anticipo affinché non sia necessario sollevare la questione.\n\n1.4 Se, d’altra parte, un’autorità ritiene più opportuno citare la Coalizione come fonte, è libera di farlo. La scelta spetta interamente al destinatario e nessuna delle due opzioni comporta alcuna conseguenza.\n\n1.5 La presente costituisce una RINUNCIA, non un’offerta di licenza. Non richiede alcuna accettazione, non impone alcun obbligo e non può essere violata. Il software pubblicato dalla Coalizione è rilasciato separatamente sotto licenza MIT; la ricerca e i risultati sono resi di dominio pubblico nella misura massima consentita e, laddove una giurisdizione non consenta la rinuncia, la Coalizione concede una licenza irrevocabile, valida in tutto il mondo e esente da royalty con lo stesso effetto.\n\n2. Perché questo è importante dal punto di vista pratico, e non solo per una questione di cortesia\n\n2.1 Un'autorità può ragionevolmente esitare a fare affidamento su materiale fornito da una parte esterna, per timore di dare l'impressione di agire su richiesta di tale parte o di entrare in qualche modo in conflitto di interessi con essa.\n\n2.2 QUI NON C'È NULLA IN CUI RIMANERE INVESTITI. La Coalizione non chiede nulla, non le è dovuto nulla, non trattiene nulla e non nutre alcuna aspettativa di alcun tipo. Non potrà in seguito far valere alcun diritto, rivendicare alcun merito, lamentare un uso improprio o opporsi alla modo in cui il materiale viene descritto, poiché non ha conservato alcuna base su cui fondare tali azioni.\n\n2.3 Un'autorità che utilizza questo materiale non agisce quindi per conto della Coalizione. Sta semplicemente utilizzando informazioni di dominio pubblico che, per caso, sono state raccolte da qualcun altro.\n\n3. È già tutto aperto\n\n3.1 Il lavoro della Coalizione è di pubblico dominio per impostazione predefinita:\n\nle indagini sono pubblicate apertamente su https://phishdestroy.io e sono liberamente consultabili;\n\nIl tooling è pubblicato come open source sotto licenza MIT all'indirizzo https://github.com/phishdestroy archiviato su 2026-09-11 ↗;\n\nla metodologia è illustrata nella stessa richiesta di parere, all’Allegato A, sezione A.16D, ivi comprese la ponderazione e le limitazioni relative a ciascuna tipologia di fonte;\n\nLa Coalizione non accetta donazioni e ha reso nota tale posizione sin dal 2018.\n\n3.2 L'unico materiale NON pubblicato è quello che non può essere pubblicato per motivi legali o di sicurezza: i dati personali delle vittime e di terzi, nonché le informazioni che potrebbero esporre una fonte a ritorsioni. Tale materiale viene fornito alle autorità in via riservata ed è indicato negli elenchi delle prove.\n\n3.3 La Coalizione invita a sottoporre a verifica la propria condotta alle stesse condizioni con cui invita a sottoporre a verifica quella di chiunque altro, e ha volontariamente messo a disposizione delle autorità competenti le informazioni relative al proprio trattamento dei dati, includendo una richiesta di indicazioni in merito al loro smaltimento.\n\n4. Integrità del fascicolo probatorio\n\n4.1 I documenti allegati vengono forniti insieme alla richiesta oppure, ove indicato, su richiesta tramite un canale sicuro. Non vengono pubblicati su un indirizzo pubblico e non è consentito dedurne alcuno: il materiale di questo tipo viene fornito direttamente alle autorità.\n\n4.2 Ogni consegna è accompagnata da un file denominato SHA256SUMS che riporta il digest SHA-256 per ogni file fornito, insieme a una firma separata OpenPGP SHA256SUMS.asc.\n\n4.3 La chiave di firma è pubblicata all'indirizzo https://phishdestroy.io/.well-known/pgp-key.txt e su keys.openpgp.org. La sua impronta digitale compare nell’intestazione di ogni contributo di questa raccolta.\n\n4.4 Ogni destinatario può verificare in qualsiasi momento che il file in suo possesso corrisponda a quello inviato, senza alcuna modifica:\n\ngpg --verify SHA256SUMS.asc SHA256SUMS\n\nsha256sum -c SHA256SUMS\n\n4.5 Lo scopo non è di natura puramente formale. È affinché, qualora in un secondo momento venisse contestata l’accuratezza o l’integrità di un qualsiasi elemento probatorio, la questione possa essere risolta con un calcolo anziché con una discussione.\n\n5. Al momento della registrazione — perché la deroga è funzionale e non solo un gesto di generosità\n\n5.1 L'autorità potrebbe imbattersi nelle indagini pubblicate dalla Coalizione e trovarle schiette, polemiche e, a tratti, satiriche. Tale impressione è corretta. La Coalizione scrive in quel modo deliberatamente e non se ne scusa.\n\n5.2 RICONOSCE INOLTRE CHE QUESTO NON È IL TONO ADEGUATO PER UN PROCEDIMENTO NORMATIVO O GIUDIZIARIO. Una questione seria non dovrebbe essere trattata con il tono di una campagna. Le conclusioni presentate a un’autorità dovrebbero essere esposte in modo diretto, ammettendone i limiti, e non dovrebbero costringere il lettore a ignorare il tono per arrivare al contenuto.\n\n5.3 È PROPRIO PER QUESTO CHE LA COALIZIONE RINUNCIA ALLA PATEURIA. La rinuncia di cui alla sezione 1 costituisce il meccanismo attraverso il quale il contenuto può essere separato dal registro: l’autorità può prendere ciò che le è utile, riformularlo con parole proprie ed eliminare ogni riferimento allo stile della Coalizione, insieme al nome stesso della Coalizione. In questo modo non si perde nulla, e la Coalizione preferirebbe che fosse così.\n\n5.4 LA COALIZIONE CHIEDE INOLTRE CHE IL REGISTRO NON VENGA CONFUSO CON IL METODO. Il tono utilizzato è combattivo; la prassi sottostante non è però superficiale. In tutto il presente ricorso, le deduzioni sono separate dalle osservazioni, le testimonianze sono identificate come tali, le fonti sono valutate e ne vengono indicate le debolezze, i dati sono presentati con i relativi limiti e i punti che la Coalizione non è in grado di dimostrare sono formulati come domande rivolte all’autorità piuttosto che come affermazioni. Laddove le prove contraddicevano la posizione della Coalizione stessa, essa lo ha dichiarato — si veda l’Allegato A, paragrafo 7, e sezione B.0 del ricorso parallelo.\n\n5.5 LA COALIZIONE SPIEGA IL LEGAME TRA IL SUO MODO DI AGIRE E LE SUE FINANZE, PERCHÉ I DUE ASPETTI SONO INSEPARABILI. Non accetta denaro da nessuno: né donazioni, né premi, né clienti, né sponsor. È proprio questo rifiuto a rendere possibile la sua schiettezza: un’organizzazione con entrate da proteggere deve moderare ciò che dice sui partiti da cui dipende. Non avendo nulla da proteggere, la Coalizione non ha nulla da moderare.\n\nÈ anche il motivo per cui la Coalizione continua a esistere. Non c’è nessun altro motore. Il lavoro viene svolto perché viene svolto; si ferma quando smettono di farlo coloro che lo svolgono.\n\n5.6 L'autorità non è tenuta ad accettare nulla di tutto ciò. Ciò viene precisato affinché il tono del lavoro pubblico della Coalizione non venga interpretato come un indicatore della cura prestata al materiale che le è stato sottoposto.\n\n6. Cosa offre la Coalizione, secondo le sue stesse parole\n\nInformazioni, ricerca e osservazione.\n\nNon viene affermata alcuna conclusione che la Coalizione non sia in grado di formulare. Laddove si tratti di una deduzione, il documento lo precisa. Laddove una conclusione si basi su una testimonianza, il documento indica di chi si tratti e con quali limitazioni. Laddove la Coalizione non sia in grado di rispondere a una domanda, lo precisa e indica chi è in grado di farlo.\n\nLa Coalizione non chiede alcun risarcimento, alcun pagamento, alcun riconoscimento né alcun esito per sé stessa o per alcun individuo. Chiede solo che le domande formulate nella richiesta di parere siano sottoposte all’Valve Corporation da un organismo avente il potere di imporre una risposta.\n\nNota conclusivaA chiunque si stia occupando di questa questione\n\nVogliamo ringraziare chiunque si occupi di far arrivare questo materiale a destinazione. Probabilmente non sarà un percorso breve. L’Valve dispone di ingenti risorse finanziarie e Taylor Wessing applica tariffe orarie: questa combinazione è studiata appositamente per far sì che persone come voi si arrendano prima di raggiungere il traguardo.\n\nSappiamo cosa stiamo facendo. Sappiamo di chi stiamo scrivendo. Sono stati i “Valve” a plasmarci: come potremmo non capirli?\n\nPhishDestroy non è in conflitto con Valve. Abbiamo bloccato l'unica rete di truffatori di quelle dimensioni che abbiamo individuato — non siamo andati alla ricerca di uno scontro con Valve. È semplicemente emerso che tutte le tracce portavano a loro. Non è un conflitto. È solo una questione di topologia.\n\nValve Non è possibile risolvere la questione di “PhishDestroy” perché non c’è nulla da risolvere. Non abbiamo alcun rapporto con loro. I dati relativi ai loro schemi di arricchimento e ai profitti esorbitanti sono in gran parte di dominio pubblico: bastava solo dedicarci abbastanza tempo per scoprirli. Pensatela come un'enciclopedia del successo: «Come aggirare le sanzioni in modo che gli hacker russi non possano piratare i nostri giochi gratuiti (quelli a pagamento che comunque non pirateranno mai)». Avete capito il concetto.\n\nNon abbiamo bisogno della paternità dell'opera.\n\nNon è necessaria l'attribuzione.\n\nNon abbiamo bisogno di una vittoria.\n\nAbbiamo bisogno di qualcuno che abbia effettiva autorità per porre a Valve le domande già contenute in questa segnalazione, con il potere di esigere una risposta.\n\nEcco tutto. È questa la richiesta.\n\nI casi saranno disponibili all'indirizzo:\n\nhttps://steamdestroy.eth/\n\nhttps://steamdestroy.eth.limo (al momento non funziona — lo sistemerò quando sarà necessario)\n\nSaremo presenti a:\n\nhttps://phishdestroy.eth.limo/ archiviato su 2026-06-27 ↗\n\nhttps://phishdestroy.eth/\n\nDue oggetti autografati · diritti e testo pubblicato\nLiberatoria firmataCosa prevede il contratto e quali aspetti copre\n\nIl testo relativo alla concessione dei diritti e quello relativo alla ricerca sono oggetti JSON firmati separatamente, riportati di seguito. Ogni firma \"OpenPGP\" (senza oggetto associato) autentica i byte esatti del JSON indicato accanto ad essa. La dichiarazione sui diritti concede le autorizzazioni; l'istantanea del testo identifica e contiene il materiale oggetto della pubblicazione.\n\n1. Dichiarazione sui diritti — license-rights.json\n\nOggetto firmato: il completo license-rights.json file contenente la concessione dei diritti di pubblico dominio datata 28 settembre 2026.. Essa concede il permesso di copiare, pubblicare, modificare, tradurre, combinare e commercializzare i materiali del dossier senza attribuzione, notifica o approvazione. Questa firma autentica la dichiarazione sui diritti; non autentica il testo di ogni pagina web o file PDF.\n\nIl documento originale firmato è conservato senza modifiche. L’autorizzazione ivi contenuta non può essere revocata né limitata modificando il sito web, pubblicando un altro file o rendendo il sito non accessibile. I materiali di terzi mantengono i propri diritti.\n\nDichiarazione sui diritti in formato JSON ↗ · Firma di license-rights.json ↗ · SHA-256e di license-rights.json ↗\n\ngpg --verify license-rights.json.asc license-rights.json\nsha256sum -c license-rights.json.sha256\n2. Testo pubblicato — dossier-text.json\n\nOggetto firmato: il completo dossier-text.json file. Contiene il testo effettivo leggibile delle pagine esportate in documents[].content.text, con il titolo di ogni pagina, la lingua, l’URL di origine, l’hash HTML di origine, i titoli e i riferimenti. Il documents L'elenco riporta l'inventario esatto oggetto di questa istantanea; le varianti linguistiche sono elencate separatamente. Si tratta di una pubblicazione testuale, non semplicemente di un elenco di hash.\n\nOgni voce identifica il proprio PDF leggero della pagina tramite il nome del file e l'SHA-256e in documents[].pdf. Il file JSON identifica inoltre la dichiarazione dei diritti originale tramite URL e SHA-256,, in modo che il testo pubblicato, il relativo PDF e la liberatoria sui diritti applicabile possano essere associati senza bisogno di fare supposizioni. I database esterni collegati, le immagini originali e le pagine assenti dall'inventario non sono inclusi in questa istantanea del testo.\n\nTesto completo in formato JSON con le firme ↗ · Firma di dossier-text.json ↗ · SHA-256e di dossier-text.json ↗\n\ngpg --verify dossier-text.json.asc dossier-text.json\nsha256sum -c dossier-text.json.sha256\n\nNella pagina iniziale del dossier, i pulsanti PDF e JSON consentono di esportare il pacchetto di ricerca. In una pagina interna, consentono di esportare quella pagina nella lingua in cui è stata pubblicata. Ogni file JSON di pagina dispone inoltre di una propria firma separata e di un file SHA-256, il cui nome è indicato esplicitamente nel suo integrity oggetto. Per verificare il PDF associato, calcolare il suo SHA-256e e confrontarlo con il pdf.sha256 valore nel JSON verificato. Il PDF è associato a tale digest; non contiene una firma digitale in formato PDF.\n\n3. Pacchetto di ricerca stampabile — steam-dossier-{language}.content.json\n\nOggetto firmato: il file JSON completo specifico per la lingua, comprensivo del testo del capitolo allegato in documents[].content.text, gli intervalli di pagine dei capitoli, le lingue di origine, l'elenco delle fonti escluse e l'esatto riepilogo in formato PDF in pdf.sha256. I cinque archivi di materiale supplementare rimangono collegati online e non vengono raggruppati. I testi di ricerca redatti dagli autori vengono conservati; i cataloghi visivi vengono sostituiti con link alle fonti.\n\nJSON in inglese ↗ · Firma \"OpenPGP\" su un edificio indipendente ↗ · Riepilogo SHA-256 ↗\n\nTedesco JSON ↗ · Firma \"OpenPGP\" su un edificio indipendente ↗ · Riepilogo SHA-256 ↗\n\ngpg --verify steam-dossier-en.content.json.asc steam-dossier-en.content.json\nsha256sum -c steam-dossier-en.content.json.sha256\n\nChiave pubblica di verifica ↗\n\nImpronta digitale della firma: 129F C7F3 9C40 C69D 2EF3 C329 BFCF 9E8D D295 EE01\n\ngpg --import pgp-key.txt\ngpg --fingerprint 129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01\n\nVerificare che l'impronta digitale visualizzata corrisponda a quella riportata sopra, quindi verificare la firma in base al nome esatto del file JSON. La modifica di un file JSON firmato altera l'oggetto firmato e invalida la sua firma originale. Una firma valida identifica i byte pubblicati; non costituisce una verifica indipendente dei risultati della ricerca.\n\nPhishDestroy — inchiesta pubblica — tutti i diritti ceduti all’umanità\n\nAccesso alla regione OFAC: vietato",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Licenza e dichiarazione di non responsabilità — Dedicazione al pubblico dominio"
          },
          {
            "level": 2,
            "id": null,
            "text": "Sezione ILicenza — la parte strettamente giuridica, ma dal punto di vista umano"
          },
          {
            "level": 3,
            "id": null,
            "text": "Una regola vera e propria (sì, solo una)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Sezione IIChe cos’è e perché esiste"
          },
          {
            "level": 2,
            "id": null,
            "text": "Sezione IIILettera aperta a Valve — sul serio, leggilo"
          },
          {
            "level": 3,
            "id": null,
            "text": "L'accordo (offerta aperta, non servono avvocati)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Sezione III-BLe risorse alleate — una nota rivolta specificatamente a Steam"
          },
          {
            "level": 2,
            "id": null,
            "text": "Sezione IVI soldi, i divieti, tutto quel circo"
          },
          {
            "level": 2,
            "id": null,
            "text": "Sezione VLa questione del malware — sì, ne stiamo parlando"
          },
          {
            "level": 2,
            "id": null,
            "text": "DichiarazionePer quanto riguarda l'uso e i diritti"
          },
          {
            "level": 3,
            "id": null,
            "text": "1. Non vi sono condizioni di utilizzo"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. Perché questo è importante dal punto di vista pratico, e non solo per una questione di cortesia"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. È già tutto aperto"
          },
          {
            "level": 3,
            "id": null,
            "text": "4. Integrità del fascicolo probatorio"
          },
          {
            "level": 3,
            "id": null,
            "text": "5. Al momento della registrazione — perché la deroga è funzionale e non solo un gesto di generosità"
          },
          {
            "level": 3,
            "id": null,
            "text": "6. Cosa offre la Coalizione, secondo le sue stesse parole"
          },
          {
            "level": 2,
            "id": null,
            "text": "Nota conclusivaA chiunque si stia occupando di questa questione"
          },
          {
            "level": 2,
            "id": null,
            "text": "Liberatoria firmataCosa prevede il contratto e quali aspetti copre"
          },
          {
            "level": 3,
            "id": null,
            "text": "1. Dichiarazione sui diritti — license-rights.json"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. Testo pubblicato — dossier-text.json"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. Pacchetto di ricerca stampabile — steam-dossier-{language}.content.json"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/it/#briefing-heading",
          "https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "http://web.archive.org/web/20260821155801/https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "https://phishdestroy.io/steam_dossier/it/investigation_part2.html#outsourcing-case",
          "https://phishdestroy.io/steam_dossier/it/#theft-ledger",
          "https://steamid.uk/",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/groups/steambans",
          "https://steamcommunity.com/id/killahinstinct_",
          "https://phishdestroy.io/steam_dossier/it/card_economy.html#governance",
          "https://phishdestroy.io/steam_dossier/it/license_disclaimer.html",
          "https://github.com/phishdestroy",
          "http://web.archive.org/web/20260911040557/https://github.com/PhishDestroy",
          "https://phishdestroy.io/.well-known/pgp-key.txt",
          "https://steamdestroy.eth/",
          "https://steamdestroy.eth.limo/",
          "https://phishdestroy.eth.limo/",
          "http://web.archive.org/web/20260627040219/https://phishdestroy.eth.limo/",
          "https://phishdestroy.eth/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json.asc",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json.sha256",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json.sha256?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json.sha256?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json.sha256?v=print-20260928-v3"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/it/license_disclaimer.content.json",
      "export_json_sha256": "43e01ed66d79e7c86a5640326eda22be57588ab834c79689b2ec4ad18e285765"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "it/market_economics.html",
      "language": "it",
      "title": "Un'unica infrastruttura, due mercati — Il dossier “Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/it/market_economics",
      "source_html_sha256": "82f453c85ce9749d44d937470fef1526e0e18bd7ff7c3a43d550d10be49f1eed",
      "exported_at": "2026-09-29T00:17:53.103Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "market_economics.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/it/market_economics.pdf?v=print-20260929-v5",
        "sha256": "67b8bbdad7a714e20224b60b3d734f33662f354ec3a560bc102e26133e4cdd1a",
        "bytes": 99018,
        "pages": 8
      },
      "integrity": {
        "signed_object": "market_economics.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "market_economics.content.json.asc",
        "digest_file": "market_economics.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify market_economics.content.json.asc market_economics.content.json",
          "sha256sum -c market_economics.content.json.sha256"
        ]
      },
      "content": {
        "text": "Allegato VII · Architettura di mercato · 20 settembre 2026\nEconomia di mercato — Due economie e il tetto massimo delle quotazioni\n\nLa loro infrastruttura. Due economie.\n\nCOSA DIMOSTRA QUESTA SEZIONE\n\nQuesto capitolo analizza la biforcazione sistemica del mercato causata dal limite di quotazione di $1,800 imposto da Valve e dai saldi dei portafogli non prelevabili. Attraverso un'indagine su 38, una piattaforma esterna attiva di scambio di skin che detiene circa $1.28 miliardi in valutazione di mercato, la ricerca dimostra che il trading di alto livello migra inevitabilmente verso piattaforme ombra esterne, pur continuando a fare affidamento sull'infrastruttura sottostante di Steam per le transazioni e l'autenticazione. Sebbene l'uso commerciale sia formalmente vietato nel Contratto di Abbonamento, Valve facilita e monetizza questa economia a due livelli senza che vi siano registrazioni pubbliche relative all'applicazione delle norme.\n\n← Torna al briefing esecutivo\n\n38 marketplace CS2 di terze parti attivi, oltre a quello di Steam. Ogni skin presente in uno qualsiasi di questi siti deve passare attraverso l'inventario di Steam e il sistema di scambio API. Le regole di Valve vietano lo sfruttamento commerciale di tale infrastruttura. Il valore stimato di circa $1.28 miliardi attribuito a terze parti rimane invariato, pur non essendo stata individuata alcuna traccia pubblica dell'applicazione di tale regola.\n\n$1.28B\nValore stimato da terzi · Piattaforme 38\n53.2M\nOfferte visualizzate · Mercati di terze parti di 38\n70.1K\nSteam elementi elencati nell'istantanea\n41×\nValore stimato da terzi rispetto ai $31M di Steam\nIl risultato principale\nUn'unica infrastruttura. Due economie.\n\nSteam controlla l'oggetto, l'inventario e gli scambi. Ogni skin venduta su qualsiasi piattaforma tra quelle elencate di seguito deve passare attraverso il sistema di scambi di Steam API — una dipendenza strutturale che è direttamente osservabile. Il Community Market di Valve percepisce una commissione sulle vendite; non è chiaro in questa sede se tale commissione finanzi o sia legata all’ ecosistema di terze parti.\n\nPerché questo è importante ai fini dell'indagine\n1\nAccordo di abbonamento a “Steam” di Valve vieta lo sfruttamento commerciale dell’infrastrutturSteama senza un’autorizzazione espressa. Nei registri pubblici non è stata individuata alcuna autorizzazione di questo tipo per le piattaforme di seguito elencate.\n2\nSteam gestisce l'identità (OpenID), lo stato delle scorte e l'esecuzione delle operazioni di trading per un valore di circa $1.28B di titoli di terze parti quotati. Nessun trasferimento di articoli avviene senza l'infrastruttura di Valve.\n3\nIl marketplace di Steam ha $31M quotato — circa l’1/41e del valore di quotazione di terze parti. Il tetto massimo di prezzo di $1,800 significa che i venditori che lo superano devono ricorrere a canali esterni alla piattaforma per vendere ai prezzi osservati.\n4\n248 Categorie di articoli CS2, i cui prezzi sono stati fissati da due o più piattaforme in modo indipendente al di sopra del tetto massimo, non possono essere venduti al prezzo di mercato osservato su Steam — e nessuno di essi è nemmeno quotato su tale piattaforma. Il tetto massimo di $1,800 crea la domanda che gli operatori terzi soddisfano.\nSteam Mercato comunitario: $31MValore di mercato stimato da terzi: $1,276M\n1,276. M. di dollari · valore indicato da terze parti — tutto dipende dall’API e dall’OpenID di Steam\nSteam · $31M\n\nFonte: catalogo in tempo reale di PriceEmpire, 20, settembre 2026.. Valore di listino = somma dei valori di listino arrotondati riportati nelle schede presenti nell’istantanea salvata, Steam escluso. Non si tratta del volume delle vendite.\n\n38 mercati di terze parti attivi · Tutto dipende dall'infrastrutturSteama\nRegistro della piattaforma\n\nLe piattaforme riportate di seguito gestiscono le procedure di accesso tramite l’OpenID di Steam e le operazioni di trading tramite il Web API di Steam. Ciascuna di esse è stata osservata openid.realm passa attraverso il flusso di accesso di Steam; il registro registra i percorsi di autenticazione osservati, anziché affermare che un determinato operatore non disponga dell'autorizzazione di Valve.\n\n#\tPiattaforma\tValore quotato\tOfferte attive\tArticoli\tScala\n1\tUUSkins\t$133.8M\t3.4M\t30.9K\t\n\n2\tYouPin898\t$127.5M\t5.9M\t29.2K\t\n\n3\tBuff.163\t$104M\t3.5M\t35K\t\n\n4\tMoon.Market\t$100.3M\t2.9M\t20.9K\t\n\n5\tWhite.Market\t$89.6M\t3M\t20.6K\t\n\n6\tBuff.Market\t$86.7M\t1.3M\t33.4K\t\n\n7\tEcosteam\t$82.1M\t3.3M\t30.1K\t\n\n8\tCSFloat\t$67.8M\t2.4M\t27.8K\t\n\n9\tSkin.Land\t$67.4M\t2.2M\t34.6K\t\n\n10\tLIS-SKINS\t$67.4M\t2.2M\t34.6K\t\n\n11\tC5Game\t$54.6M\t4.6M\t29.6K\t\n\n12\tHaloSkins\t$46.6M\t4.4M\t29.3K\t\n\n13\tAvan.Market\t$43.3M\t809.5K\t22.2K\t\n\n14\tWaxpeer\t$40.1M\t1M\t27.3K\t\n\n15\tSteam (official)\t$31M\t32.2M\t70.1K\t\n\n16\tCS.MONEY\t$29M\t748.9K\t28K\t\n\n17\tMarket.CSGO\t$26.3M\t1.3M\t27.6K\t\n\n18\tCS.MONEY Bot\t$25.7M\t614K\t23.8K\t\n\n19\tSkinport\t$16.3M\t3.8M\t31.1K\t\n\n20\tSkinFlow\t$14.1M\t481.8K\t23.6K\t\n\n21\tDMarket\t$12.6M\t948.2K\t35.6K\t\n\n22\tSkins.com\t$11.5M\t83.2K\t15.8K\t\n\n23\tSkin.place\t$6.9M\t380.8K\t11.4K\t\n\n24\tSkinsMonkey\t$6M\t109.4K\t11.6K\t\n\n25\tSkinBaron\t$5M\t2.1M\t21.5K\t\n\n26\tRustTM\t$3M\t33.1K\t4.9K\t\n\n27\tPirateSwap\t$2M\t859.3K\t10.5K\t\n\n28\tMannco.Store\t$1.2M\t223.7K\t11K\t\n\n29\tSkinSwap\t$1.1M\t11.4K\t4K\t\n\n30\tTradeIt\t$967.1K\t29.1K\t11.7K\t\n\n31\tLootFarm\t$896.1K\t162.5K\t28.6K\t\n\n32\tRustskins\t$714.8K\t312.5K\t6.1K\t\n\n33\tBalticSkins\t$599.2K\t28.2K\t4.5K\t\n\n34\tExeSkins\t$442.9K\t2.6K\t1.4K\t\n\n35\tRapidSkins\t$230.9K\t11.6K\t2.3K\t\n\n36\tCS.Trade\t$203K\t19K\t16.7K\t\n\n37\tKrakatoa\t$11.1K\t115\t53\t\n\n38\tShadowPay\t—\t—\t—\t—\n39\t49skins\t—\t—\t—\t—\nIl tetto massimo di1,800 per i prezzi a Steam · Panoramica su cinque mercati · 23 settembre 2026\nIl divario di prezzo è quantificabile.\n\nSteam fissa il valore massimo delle quotazioni del Community Market a circa $1,800 (il risultato viene ricalcolato a $2,000, $, 2,070, $, 2,300 e $2,500 in cs2sh-atlas.json e vale per ogni soglia). Gli articoli il cui prezzo è superiore a tale cifra non possono essere venduti al loro prezzo di mercato tramite la piattaforma di Valve — ma continuano comunque a dipendere dal sistema di gestione delle scorte e dei trasferimenti di Steam, indipendentemente dal luogo in cui vengono venduti. La suddivisione dell'intero catalogo in fasce di prezzo mette in evidenza dove si trova il limite: il mercato di Valve offre 95.3% delle categorie di articoli il cui prezzo è inferiore al limite massimo e 1.9% di quelli che si trovano al di sopra di esso.\n\nCinque marketplace: articoli che superano il limite di Steam\n248\n\nCategorie di articoli il cui prezzo di vendita più basso supera i $1,800 su due o più marketplace in modo indipendente, con un patrimonio di 18,394, con titoli quotati per un valore di almeno $78.6M. Di questi, 100.0% — tutti quanti — non figurano affatto nell’elenco “ Steam”.\n\nAllegati completi: il registro → · l'atlante della scala dei prezzi →\n\nDistribuzione dei prezzi al di sopra del limite massimo\n$1,800–$5,000\n174\n$5,000–$10,000\n49\n$10,000–$25,000\n21\n$25,000–$50,000\n2\n$50,000+\n2\nProdotti più venduti — prezzo di vendita verificato più basso su cinque piattaforme di vendita\n1Adesivo | Titan (Holo) | Cat. '14'$66,285\n2Adesivo | iBUYPOWER (Holo) | Cat. '14$64,795\n3Adesivo | Reason Gaming (Holo) | Cat. '14$42,899\n4★ Guanti sportivi | Labirinto di siepi (FN)$26,812\n5Adesivo | Team Dignitas (Holo) | Cat. '14'$23,667\n6EMS Cat. \"14: Legends\"$22,879\n7★ Guanti sportivi | Il vaso di Pandora (FN)$21,643\n8EMS Cat. \"14\" - I partecipanti$21,010\n9Adesivo | Vox Eminor (Holo) | Cat. '14'$18,619\n10★ Coltello StatTrak™ Navaja | Acciaio blu (FN)$18,064\n\nI prezzi richiesti non corrispondono ai prezzi di vendita. I dati provengono da cs2.sh (con licenza), 23, settembre 2026.. Ogni riga è quotata al di sopra del limite massimo da almeno due piattaforme di mercato in modo indipendente; sono escluse le offerte di vendita su una singola piattaforma e le quotazioni superiori a tre volte il prezzo di vendita più basso di un articolo. Come funziona la valutazione →\n\nCosa costa Valve · cs2.sh (panoramica) · 23 settembre 2026\nLa tariffa pubblicizzata è di 15%.. La maggior parte degli annunci offre una retribuzione più alta.\n\nValve preleva una commissione 5% Steam e una commissione 10% per il servizio di pubblicazione CS2 dai proventi del venditore — la nota 15%. Entrambe le commissioni comportano un Minimo $0.01, quindi nessuna vendita potrà mai comportare commissioni inferiori a due centesimi. Per gli articoli economici e ad alto volume che costituiscono la maggior parte del mercato, è proprio quella soglia minima a rappresentare il vincolo determinante, non la percentuale. Abbiamo risolto il calcolo delle commissioni per ognuno dei 29,635 tipi di articoli con una richiesta \"Steam\" attiva.\n\n77.7%\ngli annunci in tempo reale di Steam riguardano le categorie di articoli per cui è previsto un costo aggiuntivo su 15%\n84.8%\ndell'articolo tipi pagate all’incirca il tasso indicato\n4,517\ntipi di articoli per i quali è stata addebitata una tariffa superiore a quella pubblicizzata\n$0.02\ncommissione minima su ogni vendita, indipendentemente dal prezzo\nI due numeri indicano direzioni opposte, ed entrambi sono veri\n1\nContati per tipo di articolo, Le tariffe di Valve sono sostanzialmente quelle pubblicizzate: 84.8% dei tipi di prezzi indicati su 29,635 hanno un costo pari o quasi a 15%.\n2\nContati in base all'elenco effettivo, l'immagine si inverte: 18,682,244 di 24,038,911 gli elenchi in tempo reale riguardano le tipologie di articoli con un costo superiore a 15%.\n3\nEntrambe le affermazioni sono vere perché i tipi sovraccarichi sono i economico, ad alto volume quelli. 1,109 I tipi di articoli hanno un costo superiore a doppio il tasso di riferimento, e già solo queste tipologie rappresentano 14,083,486 annunci attivi.\n4\nSi tratta di semplice aritmetica, non di un’accusa. L’importo minimo è indicato nella documentazione relativa alle commissioni della stessa “Valve”. Ciò che non è stato reso pubblico è a quale quota di mercato si applica effettivamente — ed è proprio questo che misurano i dati riportati sopra.\nCommissione addebitata, in percentuale del valore nominale dell’15%\n200%+\n14,083,486\n100-200%\n1,028,438\n50-100%\n700,804\n30-50%\n317,031\n20-30%\n2,258,254\n17.6-20%\n294,231\n\nLa lunghezza della barra indica il numero di annunci attivi in ciascuna fascia. Una fascia contrassegnata con “200%+” significa che la commissione prelevata è superiore al doppio dell’15%e del ricavato del venditore.\n\nUn esempio illustrativo\n67%\n\nIn un annuncio, l'acquirente paga $0.03 infatti, il venditore riceve $0.01 e \"Valve\" richiede $0.02 — i due importi minimi di un centesimo. In percentuale rispetto a quanto pagato dall’acquirente, si tratta di 67%; in percentuale rispetto al ricavato del venditore, si tratta di 200%.\n\nSet di dati completo: cs2sh-steam-fee-census.json →\n\nLo stesso oggetto, all’interno del giardino e all’esterno\nAcquistare su Steam costa di più. Quasi sempre.\n\nPer ogni articolo presente sia su Steam che su almeno un marketplace di terze parti, abbiamo confrontato il prezzo di vendita più basso su Steam con quello più basso al di fuori di tale sito. Tra 28,700 per quanto riguarda i prodotti, Steam è il sito più costoso 86.4% nella maggior parte dei casi, con una mediana di +35.7%.\n\nPremio mediano dell’Steam, per fascia di prezzo\nmeno di $0.50\n+48.3%\n$0.50-2\n+36.5%\n$2-10\n+29.6%\n$10-50\n+28.6%\n$50-250\n+36.3%\n$250-1k\n+51.1%\noltre $1,000\n+67.9%\n\nLa curva ha forma di U. Il prezzo più conveniente si trova su Steam nella $10–$50 la fascia e la parte più stretta alle due estremità.\n\nPerché la fascia alta è importante\n+67.9%\n\nSopra $1,000, il costo mediano degli annunci su Steam 67.9% è superiore a quello dell’offerta più economica al di fuori di tale sito — e solo 1,040 tali annunci sono presenti su Steam.\n\nOltre i circa1,800, il confronto non è più possibile, poiché la normativa di Valve vieta del tutto l'inserimento in elenco. La copertura di Steam per gli articoli che superano il proprio limite massimo è 1.9%. Guarda la classifica completa →\n\nSet di dati completo: cs2sh-walled-garden-premium.json →\n\nUn premio non costituisce di per sé un dato di fatto: Steam offre consegna immediata e assenza di rischio di controparte, e gli acquirenti potrebbero ragionevolmente essere disposti a pagare per questo. Ciò che è misurabile è l’entità del divario e il fatto che il denaro che lo attraversa non possa tornare indietro — argomento trattato nella sezione successiva.\n\nEntrano soldi, non ne escono\n128.1 milioni di dollari destinati a ordini che non possono essere annullati.\n\nUn ordine di acquisto su Steam è prefinanziato: il denaro viene prelevato dal portafoglio dell'acquirente nel momento stesso in cui l'ordine viene effettuato. Fondi del portafoglio Steam non può essere revocato — possono essere spesi solo all’interno di Steam. Sommando tutti i livelli di prezzo del libro degli ordini di acquisto di ogni articolo monitorato si ottiene un quadro completo del denaro impegnato e non ritirabile.\n\n$128.1M\nimpegnati a mantenere gli ordini di acquisto su Steam\n170.6M\nordini di acquisto con finanziamento individuale in sospeso\n$105.8M\nvalore richiesto degli immobili in vendita che hanno davanti\n$15.9M\nLa commissione di Valve nel caso in cui tutti gli immobili in vendita fossero venduti al prezzo richiesto\nCosa rappresenta questa cifra e cosa non rappresenta\n1\nÈ denaro reale già versato. Ogni dollaro conteggiato è stato addebitato su un portafoglio ed è associato a un ordine aperto relativo a una delle categorie di articol31,253.\n2\nÈ non ricavi e non si tratta di un'affermazione relativa al bilancio dell'Valve. Non viene qui precisato dove sia detenuto il flottante né in quali libri contabili sia registrato.\n3\nÈ un istantanea, non un flusso. Gli ordini possono essere annullati dall'acquirente, il che comporta il rimborso dei fondi sul portafoglio — ma non fuori da Steam.\n4\nIl punto sta proprio nella porta a senso unico. Un mercato la cui valuta non può essere convertita in denaro è il motivo per cui le scorte rubate vengono convertite spento Steam piuttosto che su di esso.\n\nMetodo: ogni livello di prezzo di ogni libro degli ordini di acquisto monitorato, moltiplicato per gli ordini presenti a quel livello. Set di dati completo: cs2sh-steam-locked-capital.json →\n\nVendite concluse, non prezzi richiesti · un unico marketplace · dati degli ultimi 90 giorni\n30.9 milioni di dollari sono stati effettivamente scambiati — sul più piccolo dei cinque ripiani.\n\nUna singola vendita ad alto prezzo può riguardare un oggetto artigianale raro o una variante con adesivo applicato di un oggetto base economico (ad e.g esempio, un oggetto da $30 con una vendita conclusa una tantum a $9,772). \"Alto\" = transazione conclusa al prezzo più alto, non il prezzo normale dell'oggetto.\n\nTutte le altre cifre riportate in questa pagina indicano ciò che è elencati. Questo misura ciò che era venduto. Il sito Skinport pubblica le proprie transazioni completate e, negli ultimi 90 giorni, il totale è stato di 1,219,143 vendite valore $30,927,032, a una media di $25.37ci ciascuno.\n\n1.22M\nvendite concluse in 90 giorni, su un unico marketplace\n$30.9M\nfatturato nello stesso periodo\n$125M\ntasso di crescita annualizzato — un limite minimo, non una stima\n~2%\nQuota di Skinport nel portafoglio \"above-cap\" in base al valore di quotazione\nDa dove proviene il fatturato\nmeno di $1\n0.5%\n$1-10\n5.8%\n$10-100\n22.2%\n$100-1k\n59.4%\n$1k-1.8k\n6.9%\nsopra il cappellino “Steam”\n5.3%\n\nLa lunghezza della barra indica il fatturato; il dato rappresenta la quota di quel livello rispetto al totale. 59.4% del denaro movimentato nella fascia $100–$1k, su 71,437 vendite.\n\nAnche sopra il cappellino dell’Valve, le vendite continuano\n492\n\nvendite concluse di articoli con un prezzo superiore al limite massimo previsto dall’Steam, per un valore di $1,643,938, tra i vari tipi di prodotti presenti su 76 — su una piattaforma che occupa circa 2% di quello spazio. Nessuna di quelle vendite avrebbe potuto avvenire su Steam.\n\nSet di dati completo: cs2sh-offsteam-90d-dynamics.json → · i massimi raggiunti →\n\nSkinport è UNO dei mercati di terze parti monitorati in questa sede e, con un valore di quotazione superiore alla soglia dell’Steam, è il più piccolo dei cinque (circa l’2%e di quella fascia). Ogni totale qui riportato rappresenta un limite minimo dell’economia off-Steam, non una misura della stessa. Non vengono utilizzati dati provenienti da Steam.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Economia di mercato — Due economie e il tetto massimo delle quotazioni"
          },
          {
            "level": 2,
            "id": null,
            "text": "Un'unica infrastruttura. Due economie."
          },
          {
            "level": 2,
            "id": null,
            "text": "Registro della piattaforma"
          },
          {
            "level": 2,
            "id": null,
            "text": "Il divario di prezzo è quantificabile."
          },
          {
            "level": 3,
            "id": null,
            "text": "Cinque marketplace: articoli che superano il limite di Steam"
          },
          {
            "level": 3,
            "id": null,
            "text": "Distribuzione dei prezzi al di sopra del limite massimo"
          },
          {
            "level": 3,
            "id": null,
            "text": "Prodotti più venduti — prezzo di vendita verificato più basso su cinque piattaforme di vendita"
          },
          {
            "level": 2,
            "id": null,
            "text": "La tariffa pubblicizzata è di 15%.. La maggior parte degli annunci offre una retribuzione più alta."
          },
          {
            "level": 3,
            "id": null,
            "text": "Commissione addebitata, in percentuale del valore nominale dell’15%"
          },
          {
            "level": 3,
            "id": null,
            "text": "Un esempio illustrativo"
          },
          {
            "level": 2,
            "id": null,
            "text": "Acquistare su Steam costa di più. Quasi sempre."
          },
          {
            "level": 3,
            "id": null,
            "text": "Premio mediano dell’Steam, per fascia di prezzo"
          },
          {
            "level": 3,
            "id": null,
            "text": "Perché la fascia alta è importante"
          },
          {
            "level": 2,
            "id": null,
            "text": "128.1 milioni di dollari destinati a ordini che non possono essere annullati."
          },
          {
            "level": 2,
            "id": null,
            "text": "30.9 milioni di dollari sono stati effettivamente scambiati — sul più piccolo dei cinque ripiani."
          },
          {
            "level": 3,
            "id": null,
            "text": "Da dove proviene il fatturato"
          },
          {
            "level": 3,
            "id": null,
            "text": "Anche sopra il cappellino dell’Valve, le vendite continuano"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/it/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/it/elite_skins.html",
          "https://phishdestroy.io/steam_dossier/it/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/it/skin_atlas.html#grading",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-steam-fee-census.json",
          "https://phishdestroy.io/steam_dossier/it/skin_atlas.html#cliff",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-walled-garden-premium.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-steam-locked-capital.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-offsteam-90d-dynamics.json",
          "https://phishdestroy.io/steam_dossier/it/skin_atlas.html#highs"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/it/market_economics.content.json",
      "export_json_sha256": "9c19d0560f5b10b7d0532c8005a0d3baf887dfdac7bf3cc769f90f7d91f6d7a9"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "it/regulatory_act_print.html",
      "language": "it",
      "title": "LEGGE SULLA REVISIONE CONTABILE FORENSE: Valve Steam Web API Ecosistema e sfruttamento commerciale (Rif.: VAL-REG-2026-09)",
      "source_url": "https://phishdestroy.io/steam_dossier/it/regulatory_act_print",
      "source_html_sha256": "24b246d14b2d0c53d8ae3c339d5e5720c6f8fbf301b2539aa48a84b263c25dac",
      "exported_at": "2026-09-29T00:17:53.639Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "regulatory_act_print.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/it/regulatory_act_print.pdf?v=print-20260929-v5",
        "sha256": "52c0e2b51cf991c3482cd3fb47113418dc9610fdfe697102bcfbe8684e7ac664",
        "bytes": 185264,
        "pages": 14
      },
      "integrity": {
        "signed_object": "regulatory_act_print.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "regulatory_act_print.content.json.asc",
        "digest_file": "regulatory_act_print.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify regulatory_act_print.content.json.asc regulatory_act_print.content.json",
          "sha256sum -c regulatory_act_print.content.json.sha256"
        ]
      },
      "content": {
        "text": "phishdestroy.io · Coalizione per la ricerca forense · Archivio pubblico universale\nREGISTO: VAL-REG-2026-09-EVID\nPROVENIENZA: phishdestroy.io/steam_dossier/\nDIRITTI: TUTTI I DIRITTI CEDUTI ALL’UMANITÀ\nLegge sulla revisione forense e allegato normativo\nProvisioning sistematico di servizi di \"API\" da parte di terzi, architettura di bypass automatizzata e mancata applicazione dei termini contrattuali nell'ecosistema Valve Steam\nDominio di emissionephishdestroy.io\nPiattaforma di destinazioneValve Steam / Steamworks\nVettore di autenticazione primarioSteam OpenID 2.0 / Web API\nDedica legaleAll Rights to Humanity (CC0)\nSezione I: Memorandum esecutivo e accertamenti di fattoRIF.: MEMO-SINTESI-01\n\nIl presente documento costituisce un atto formale di revisione forense volto ad esaminare l'intersezione operativa tra i termini commerciali pubblicati dValve, i suoi endpoint di autenticazione tecnica e le piattaforme commerciali di terze parti osservate. La revisione è stata condotta ricorrendo all'osservazione passiva e non autenticata della rete, alla verifica delle registrazioni su RDAP e ai dati telemetrici pubblici di Link Filter.\n\nNucleo fattuale: L'osservazione empirica evidenzia una divergenza sistematica tra le dichiarazioni contrattuali pubbliche di Valve e la sua infrastruttura produttiva. Sebbene il Contratto di abbonamento (SSA) di Steam vieti espressamente lo sfruttamento commerciale non autorizzato (§ 2.G), l’interazione automatizzata tramite bot/script (§ 4.C) e il trasferimento di account (§ 1.C), Valve Corporation continua a fornire un’infrastruttura programmatica e in tempo reale per l’autenticazione OpenID e la consultazione dell’inventario ad almeno 175 soggetti commerciali, generando volumi di transazioni secondarie pari a diversi miliardi di dollari.\n\n175\nOperatori commerciali sottoposti a revisione contabile\n44\nHost di autenticazione con domini separati\n26\nCoppie di proxy con filtro separato\n100%\nDisposizioni non applicate della SSA: § 2.G / § 4.C\n0\nRevoche forzate delle autorizzazioni\nQuadro normativo contrattuale e di legge applicabile\nSSA § 2.G\nDivieto di utilizzo commerciale: È espressamente vietato utilizzare i Contenuti e i Servizi a fini commerciali senza previa autorizzazione scritta da parte di Valve Corporation.\nSSA § 4.C\nLimitazione relativa all'automazione: È severamente vietato l'uso di script, bot di trading, macro o sistemi non controllati dall'uomo che interagiscano con i servizi e i mercati di Steam.\nSSA § 1.C\nObbligo di uso personale: Limita l'uso degli account a fini personali; vieta espressamente la vendita, la cessione in locazione, il trasferimento o lo scambio di account utente di Steam.\nDSA dell'UE (2022/2065)\nValutazione del rischio sistemico (art. 34/35): Le piattaforme online di grandi dimensioni (VLOP) devono individuare, valutare e mitigare attivamente i rischi sistemici derivanti da un uso improprio automatizzato e dallo sfruttamento commerciale non autorizzato.\nSezione II: Registro delle prove A — Coppie separate con filtro dei collegamenti documentati (percorsi 26)RIF.: EX-SPLIT-LEDGER\n\nAnalisi forense delle tecniche di evasione basate sullo split-domain: Nell'ambito del sistema di filtraggio dei link \"Steam\" di Valve (steamcommunity.com/linkfilter/?url=...), quando un utente finale clicca su un link che rimanda a una piattaforma di gioco d’azzardo o del mercato nero segnalata, Valve mostra un avviso ben visibile (\"Collegamento bloccato! ... segnalato come potenzialmente dannoso\"). Tuttavia, l’analisi forense del percorso rivela che esistono piattaforme commercial26i che operano su un architettura a domini separati: mentre il dominio commerciale principale risulta BLOCCATO nel filtro dei link, il dominio secondario che ospita l'endpoint di risposta OpenID di Valve è contrassegnato come PULITO. I server OpenID di Valve accettano senza interruzioni le richieste di autenticazione provenienti da questi host proxy, neutralizzando l'avviso di sicurezza per gli utenti e continuando al contempo a elaborare gli accessi.\n\n#\tDominio commerciale principale\tFiltro principale\tDominio del proxy di autenticazione OpenID\tFiltro Auth\tRDAP Iscritto\tBase di acquisizione\n01\trollbit.com\tBLOCKED\trbsnin.com\tCLEAN\t2026-09-18\tPASSIVE_CAPTURE\n02\tskin.club\tBLOCKED\tsc-auth.net\tCLEAN\t2019-04-02\tPASSIVE_CAPTURE\n03\thowl.gg\tBLOCKED\thowl.uno\tCLEAN\t2026-08-11\tPASSIVE_CAPTURE\n04\tduelbits.com\tBLOCKED\tswitchflips.com\tCLEAN\t2020-04-21\tPASSIVE_CAPTURE\n05\tcsgofast.com\tBLOCKED\tsteam-login.authtofast.com\tCLEAN\t2026-06-30\tPASSIVE_CAPTURE\n06\tfarmskins.com\tBLOCKED\tsteam.kobal.cc\tCLEAN\t2017-01-07\tPASSIVE_CAPTURE\n07\tcobaltlab.tech\tBLOCKED\tcobaltauth.com\tCLEAN\t2025-01-07\tPASSIVE_CAPTURE\n08\tcsgo.net\tBLOCKED\tcn2.easylot.net\tCLEAN\t2016-09-03\tPASSIVE_CAPTURE\n09\tggdrop.com\tBLOCKED\tggauth.com\tCLEAN\t2023-05-03\tPASSIVE_CAPTURE\n10\trustchance.com\tBLOCKED\thgfuihd.com\tCLEAN\t2019-01-27\tPASSIVE_CAPTURE\n11\tskin.fans\tBLOCKED\tauth.skinfans.com\tCLEAN\t2018-07-16\tPASSIVE_CAPTURE\n12\tskinport.com\tBLOCKED\tskinport.app\tCLEAN\t2020-06-20\tPASSIVE_CAPTURE\n13\tskins.cash\tBLOCKED\tskinscash.live\tCLEAN\t2019-12-05\tPASSIVE_CAPTURE\n14\ttf2hunt.com\tBLOCKED\trstspcl.com\tCLEAN\t2020-08-08\tPASSIVE_CAPTURE\n15\tdaddyskins.com\tBLOCKED\tgo-go-daddy.com\tCLEAN\t2019-01-26\tPASSIVE_CAPTURE\n16\tkey-drop.com\tBLOCKED\tkdauth.com\tCLEAN\t2026-05-13\tPASSIVE_CAPTURE\n17\tclash.gg\tBLOCKED\tclggauth.com\tCLEAN\t2024-09-16\tPASSIVE_CAPTURE\n18\tc5game.com\tBLOCKED\twww.imbastar.com\tCLEAN\t2016-02-27\tPASSIVE_CAPTURE\n19\tswap.gg\tBLOCKED\tswapauth.com\tCLEAN\t2018-10-06\tPASSIVE_CAPTURE\n20\tshadowpay.com\tBLOCKED\tthelogins.com\tCLEAN\t2018-01-22\tPASSIVE_CAPTURE\n21\tcsgocases.com\tBLOCKED\tlog-1n.com\tCLEAN\t2017-11-27\tPASSIVE_CAPTURE\n22\tcsgogem.com\tBLOCKED\tapi.csgem.com\tCLEAN\t2014-03-08\tPASSIVE_CAPTURE\n23\tgamdom.com\tBLOCKED\tlogin.gambldom.com\tCLEAN\t2017-09-24\tPASSIVE_CAPTURE\n24\t12cs.fail\tBLOCKED\tfail.games\tCLEAN\t2021-08-24\tPASSIVE_CAPTURE\n25\tskinsnipe.com\tBLOCKED\tpricing.tradeupspy.com\tCLEAN\t2020-03-11\tPASSIVE_CAPTURE\n26\tcsgobig.com\tBLOCKED\tletmeinbig.com\tCLEAN\t2023-01-20\tPASSIVE_CAPTURE\n\n* Nota: sono stati effettuati controlli passivi sugli endpoint non autenticati del filtro dei link Steam su 2026-09-19 e 2026-09-21.. I corpi delle risposte HTTP grezze e i digest SHA-256 sono stati conservati nel set di dati del repository (steam_tos_assets/linkfilter-2026-09-22.json).\n\nSezione III: Registro B — Censimento completo delle entità commerciali sottoposte a revisione contabile dell’175RIF.: EX-175-MASTER-CENSUS\n\nIl registro che segue riporta in dettaglio tutte le piattaforme commerciali di terze parti 175 attivamente verificate nel database di audit. Ogni record indica il nome dell’entità, il dominio commerciale principale, il percorso di autenticazione OpenID osservato Steam, la classificazione dell’attività, le corrispondenze relative alle violazioni contrattuali (SSA § 2.G, SSA § 4.C, SSA § 1.C) e il campo “azione” registrato nel set di dati di origine. L’etichetta «Vedi prove datate» rimanda il lettore ai documenti di supporto; non stabilisce che Valve non abbia intrapreso alcuna azione. Un campo “azione” assente viene segnalato come non accertato.\n\nAllegato\tNome dell'entità e dominio principale\tPercorso di autenticazione / proxy osservato\tClassificazione\tViolazione contrattuale\tValve Azione\nEX-001\tCSGORoll\ncsgoroll.com\n\t\nwww.csgoroll.com\nDIRECT\n\tSkin Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-002\tCSGOEmpire\ncsgoempire.com\n\t\ncsgoempirelogin4.com\nSPLIT PROXY\n\tCasino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-003\tRollbit\nrollbit.com\n\t\nrbsnin.com\nSPLIT PROXY\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-004\t500 Casino\n500.casino\n\t\nfivezerozero.co\nSPLIT PROXY\n\tLicenced Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-005\tCSGOBig\ncsgobig.com\n\t\ncsgobig.com\nDIRECT\n\tRoulette/Slots\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-006\tCaseDrop\ncasedrop.com\n\t\ncasedrop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-007\tRustReaper\nrustreaper.com\n\t\nrustreaper.com\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-008\tBanditCamp\nbanditcamp.com\n\t\nbanditcamp.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-009\tSkinBox\nskinbox.com\n\t\nskinbox.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-010\tTastyDrop\ntastydrop.com\n\t\ntastydrop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-011\tCSGOPolygon\ncsgopolygon.gg\n\t\ncsgopolygon.gg\nDIRECT\n\tRoulette Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-012\tMagicDrop\nmagicdrop.ru\n\t\nmagicdrop.ru\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-013\tCSDice\ncsdice.com\n\t\ncsdice.com\nDIRECT\n\tDice Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-014\tRustly\nrustly.com\n\t\nrustly.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-015\tSkinOdds\nskinodds.com\n\t\nskinodds.com\nDIRECT\n\tUpgrader Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-016\tCSGOWin\ncsgowin.com\n\t\ncsgowin.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-017\tCSGORun\ncsgorun.net\n\t\ncsgorun.net\nDIRECT\n\tCrash Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-018\tOpenSkins\nopenskins.com\n\t\nopenskins.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-019\tRustBet\nrustbet.com\n\t\nrustbet.com\nDIRECT\n\tRust Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-020\tCSGOMagic\ncsgomagic.com\n\t\ncsgomagic.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-021\tCSGOBounty\ncsgobounty.com\n\t\ncsgobounty.com\nDIRECT\n\tUpgrader/Contract\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-022\tEZSkins\nezskins.com\n\t\nezskins.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-023\tRustCases\nrustcases.com\n\t\nrustcases.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-024\tCSGOReaper\ncsgoreaper.com\n\t\ncsgoreaper.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-025\tCSGOCases\ncsgocases.com\n\t\ncsgocases.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-026\tCSGO-Skins\ncsgo-skins.com\n\t\ncsgo-skins.com\nDIRECT\n\tCase Upgrader\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-027\tCSGONet\ncsgonet.com\n\t\ncsgonet.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-028\tWTFSkins\nwtfskins.com\n\t\nwtfskins.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-029\tCSGOFast\ncsgofast.com\n\t\nsteam-login.authtofast.com\nSPLIT PROXY\n\tRoulette Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-030\tDuelbits\nduelbits.com\n\t\nswitchflips.com\nSPLIT PROXY\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-031\tFlameCases\nflamecases.com\n\t\nflamecases.com\nDIRECT\n\tCase Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-032\tFarmskins\nfarmskins.com\n\t\nsteam.kobal.cc\nSPLIT PROXY\n\tCase Opener\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-033\tCSGOLuck\ncsgoluck.com\n\t\ncsgoluck.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-034\tGamedom\ngamedom.com\n\t\ngamedom.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-035\tSkin.Club\nskin.club\n\t\nsc-auth.net\nSPLIT PROXY\n\tCase Battles\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-036\tDaddySkins\ndaddyskins.com\n\t\ndaddyskins.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-037\tInsane.gg\ninsane.gg\n\t\napi.insane.gg\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-038\tRustix\nrustix.gg\n\t\nrustix.gg\nDIRECT\n\tRust Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-039\tSkins.Club\nskins.club\n\t\nskins.club\nDIRECT\n\tSkin Upgrade\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-040\tCSGOHouse\ncsgohouse.org\n\t\ncsgohouse.org\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-041\tSkinRave\nskinrave.net\n\t\nskinrave.net\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-042\tBloodyCase_GG\nbloodycase.gg\n\t\nbloodycase.gg\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-043\tCSGOClicker\ncsgoclicker.com\n\t\ncsgoclicker.com\nDIRECT\n\tClicker/Upgrade\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-044\tRustBet_GG\nrustbet.gg\n\t\nrustbet.gg\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-045\tCS_Drop\ncs-drop.com\n\t\ncs-drop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-046\tHellStore\nhellstore.net\n\t\nhellstore.net\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-047\tRustLoot\nrustloot.com\n\t\nrustloot.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-048\tCSGO_Case\ncsgo-case.com\n\t\ncsgo-case.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-049\tCS2Skin\ncs2skin.com\n\t\ncs2skin.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-050\tJuice_GG\njuice.gg\n\t\nletmeinjuice.com\nSPLIT PROXY\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-051\tGGDrop\nggdrop.com\n\t\nggauth.com\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-052\tCSGOGem\ncsgogem.com\n\t\ncsgogem.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-053\tRainbet\nrainbet.com\n\t\nservices.rainbet.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-054\tHowl_GG\nhowl.gg\n\t\nhowl.uno\nSPLIT PROXY\n\tSkins Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-055\tChicken_GG\nchicken.gg\n\t\nchicken.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-056\tCSGOCasino_GG\ncsgocasino.gg\n\t\napi.csgocasino.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-057\tHunt_GG\nhunt.gg\n\t\napi.hunt.gg\nDIRECT\n\tSkins Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-058\tCSBattle\ncsbattle.com\n\t\ncsbattle.com\nDIRECT\n\tCase Battles\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-059\tSkinRave_GG\nskinrave.gg\n\t\napi.skinrave.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-060\tCSDouble\ncsdouble.gg\n\t\ncsdouble.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-061\tRustChance\nrustchance.com\n\t\nhgfuihd.com\nSPLIT PROXY\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-062\tRustClash\nrustclash.com\n\t\nrustclash.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-063\tCobaltLab\ncobaltlab.tech\n\t\ncobaltauth.com\nSPLIT PROXY\n\tRust Automation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-064\tRaided_GG\nraided.gg\n\t\napi.raided.gg\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-065\tRustNeo\nrustneo.gg\n\t\nrustneo.gg\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-066\tSplits_GG\nsplits.gg\n\t\nsplits.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-067\tUpgrader_Pro\nupgrader.pro\n\t\nupgauth.space\nSPLIT PROXY\n\tSkin Upgrader\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-068\tSkinFans\nskin.fans\n\t\nauth.skinfans.com\nSPLIT PROXY\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-069\tHotPizza\nhotpizza.one\n\t\nhotpizza.one\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-070\tG4Skins\ng4skins.com\n\t\nauth.g4s.to\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-071\t12CS_Fail\n12cs.fail\n\t\n12cs.fail\nDIRECT\n\tCrash Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-072\tTF2Royal\ntf2royal.com\n\t\ntf2auth.com\nSPLIT PROXY\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-073\tTF2Easy\nwww.tf2easy.com\n\t\nwww.tf2easy.com\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-074\tTF2Hunt\ntf2hunt.com\n\t\nrstspcl.com\nSPLIT PROXY\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-075\tTF2Bet\ntf2.bet/coinflip\n\t\ntf2.bet\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-076\tTF2Blaze\ntf2blaze.com\n\t\ntf2blaze.com\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-077\tOpenStars_GG\nopenstars.gg\n\t\nopenstars.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-078\tShuffle_Com\nshuffle.com\n\t\nshuffle.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-079\tSkins.com\nskins.com\n\t\napi.skins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-080\tWhite.Market\nwhite.market\n\t\nwhite.market\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-081\tBuff.Market\nbuff.market\n\t\nbuff.market\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-082\tAvan.Market\navan.market\n\t\navan.market\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-083\tCS.MONEY\ncs.money\n\t\nauth.dota.trade\nSPLIT PROXY\n\tTrading Engine\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-084\tUUSkins\nuuskins.com\n\t\nuuskins.com\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-085\tYouPin898\nyoupin898.com\n\t\nyoupin898.com\nDIRECT\n\tMass Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-086\tMoon.Market\nmoon.market\n\t\nmoon.market\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-087\tCSFloat\ncsfloat.com\n\t\ncsgofloat.com\nSPLIT PROXY\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-088\tSkin.Land\nskin.land\n\t\nauth.skin.land\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-089\tC5Game\nc5game.com\n\t\nc5game.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-090\tHaloSkins\nhaloskins.com\n\t\nhaloskins.com\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-091\tBuff.163\nbuff.163.com\n\t\nbuff.163.com\nDIRECT\n\tCorporate Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-092\tWaxpeer\nwaxpeer.com\n\t\nwaxpeer.com\nDIRECT\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-093\tCS.MONEY Bot\ncs.money\n\t\nauth.dota.trade\nSPLIT PROXY\n\tBot Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-094\tMarket.CSGO\nmarket.csgo.com\n\t\ndota2.net\nSPLIT PROXY\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-095\tSkinport\nskinport.com\n\t\nskinport.app\nSPLIT PROXY\n\tRegulated Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-096\tSkinFlow\nskinflow.gg\n\t\napi.skinflow.gg\nDIRECT\n\tMarketplace/Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-097\tDMarket\ndmarket.com\n\t\ndmarket.com\nDIRECT\n\tUS Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-098\tSkin.place\nskin.place\n\t\napi.skin.place\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-099\tSkinsMonkey\nskinsmonkey.com\n\t\nskinsmonkey.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-100\tSkinBaron\nskinbaron.de\n\t\nskinbaron.com\nSPLIT PROXY\n\tCorporate Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-101\tSteam\nsteamcommunity.com/market\n\t\nsteamcommunity.com/market\nDIRECT\n\tOfficial Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-102\tRustTM\nrust.tm\n\t\ndota2.net\nSPLIT PROXY\n\tRust Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-103\tPirateSwap\npirateswap.com\n\t\nlogin.pirateswap.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-104\tMannco.Store\nmannco.store\n\t\nmannco.store\nDIRECT\n\tTF2 Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-105\tSkinSwap\nskinswap.com\n\t\napi.skinswap.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-106\tLootFarm\nlootfarm.com\n\t\nlootfarm.com\nDIRECT\n\tTrading Platform\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-107\tRustskins\nrustskins.com\n\t\nrustskins.com\nDIRECT\n\tRust Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-108\tExeSkins\nexeskins.com\n\t\nexeskins.com\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-109\tBalticSkins\nbalticskins.com\n\t\nbalticskins.com\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-110\tCS.Trade\ncs.trade\n\t\ncs.trade\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-111\tRapidSkins\nrapidskins.com\n\t\napi.rapidskins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-112\tTradeIt\ntradeit.gg\n\t\nconnect-tradeit.com\nSPLIT PROXY\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-113\tKrakatoa\nkrakatoa.com\n\t\nkrakatoa.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-114\tShadowPay\nshadowpay.com\n\t\nshadowpay.com\nDIRECT\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-115\t49skins\n49skins.com\n\t\napi.49skins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-116\tSkinVault\nskinvault.gg\n\t\napi.skinvault.gg\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-117\tAim Market\naim.market\n\t\naim.market\nDIRECT\n\tSkins Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-118\tSkinout\nskinout.gg\n\t\nauth.skinout.gg\nDIRECT\n\tInstant Sell Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-119\tNTSkins\nntskins.com\n\t\nntskins.com\nDIRECT\n\tSkins Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-120\tIGXE\nigxe.cn\n\t\nigxe.cn\nDIRECT\n\tChinese Powerhouse\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-121\tSwap.gg\nswap.gg\n\t\nswap.gg\nDIRECT\n\tAutomated Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-122\tBitskins\nbitskins.com\n\t\nbitskins.com\nDIRECT\n\tCash-out Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-123\tGamerPay\ngamerpay.gg\n\t\ngamerpay.gg\nDIRECT\n\tP2P Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-124\tTF2Mart\ntf2mart.com\n\t\ntf2mart.com\nDIRECT\n\tTF2 Automation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-125\tSkinBid\nskinbid.com\n\t\nskinbid.com\nDIRECT\n\tSkin Auctions\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-126\tLootBear\nlootbear.com\n\t\nlootbear.com\nDIRECT\n\tSkin Rental\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-127\tBackpack.tf\nbackpack.tf\n\t\nbackpack.tf\nDIRECT\n\tTF2 Valuation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-128\tScrap.tf\nscrap.tf\n\t\nscrap.tf\nDIRECT\n\tTF2 Scrap Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-129\tMarketplace.tf\nmarketplace.tf\n\t\nmarketplace.tf\nDIRECT\n\tTF2 Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-130\tSTNTrading\nstntrading.eu\n\t\nstntrading.eu\nDIRECT\n\tTF2 Botnet\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-131\tSkins.Cash\nskins.cash\n\t\nskinscash.live\nSPLIT PROXY\n\tInstant Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-132\tSkinWallet\nskinwallet.com\n\t\nskinwallet.com\nDIRECT\n\tInstant Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-133\tDota2Market\ndota2market.com\n\t\ndota2market.com\nDIRECT\n\tDota 2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-134\tCSGO.NET\ncsgo.net\n\t\ncn2.easylot.net\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-135\tCybershoke\ncybershoke.net\n\t\nauth.cybershoke.net\nDIRECT\n\tCommunity Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-136\tXPlay_GG\nxplay.gg\n\t\nxplay.gg\nDIRECT\n\tServer Network\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-137\tFastCup\nfastcup.net\n\t\napi.fastcup.net\nDIRECT\n\tMatchmaker Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-138\tEsportal\nesportal.com\n\t\nesportal.com\nDIRECT\n\tMatchmaking Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-139\tGamersClub\ngamersclub.com.br\n\t\ngamersclub.com.br\nDIRECT\n\tLATAM Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-140\tLeetify\nleetify.com\n\t\nleetify.com\nDIRECT\n\tSaaS Analytics\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-141\tScope_GG\nscope.gg\n\t\nscope.gg\nDIRECT\n\tSaaS Analytics\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-142\tTradeUpSpy\ntradeupspy.com\n\t\napi.tradeupspy.com\nDIRECT\n\tSaaS Tools\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-143\tEpidemic_GG\nepidemic.gg\n\t\nepidemic.gg\nDIRECT\n\tSaaS Tools\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-144\tCSDeals\ncs.deals\n\t\napi.cs.deals\nDIRECT\n\tMarketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-145\tPricempire\npricempire.com\n\t\npricempire.com\nDIRECT\n\tSaaS Price DB\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-146\tCS2Stash\ncs2stash.com\n\t\ncs2stash.com\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-147\tCSGOSkins\ncsgoskins.gg\n\t\ncsgoskins.gg\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-148\tSteamAnalyst\nsteamanalyst.com\n\t\nsteamanalyst.com\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-149\tSteamCardExchange\nsteamcardexchange.net\n\t\nsteamcardexchange.net\nDIRECT\n\tTrading Exchange\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-150\tDotaBuff\ndotabuff.com\n\t\ndotabuff.com\nDIRECT\n\tSaaS Tracker\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-151\tTracker_GG\ntracker.gg\n\t\ntracker.gg\nDIRECT\n\tSaaS Tracker\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-152\tFSB Market (an anonymized label; the original name is withheld here)\nFSB Market\n\t\nFSB Market\nDIRECT\n\tMass Blackmarket\tSSA § 2.G, SSA § 4.C, SSA § 1.C\tSee dated evidence\nEX-153\tFunPay\nfunpay.com\n\t\nfunpay.com\nDIRECT\n\tAccount Exchange\tSSA § 2.G, SSA § 4.C, SSA § 1.C\tSee dated evidence\nEX-154\tPlayerAuctions\nplayerauctions.com\n\t\nplayerauctions.com\nDIRECT\n\tGrey Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-155\tEldorado.gg\neldorado.gg\n\t\neldorado.gg\nDIRECT\n\tAccount Portal\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-156\tG2A\ng2a.com\n\t\ng2a.com\nDIRECT\n\tMass Key Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-157\tKinguin\nkinguin.net\n\t\nkinguin.net\nDIRECT\n\tMass Key Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-158\tG2G.com\ng2g.com\n\t\ng2g.com\nDIRECT\n\tVirtual Services\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-159\tPlayerup\nplayerup.com\n\t\nplayerup.com\nDIRECT\n\tAccount Broker\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-160\tZ2U.com\nz2u.com\n\t\nwww.z2u.com\nDIRECT\n\tReady-Account Hub\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-161\tSmurfHub\nsmurfhub.net\n\t\nsmurfhub.net\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-162\tSmurfAccounts\nsmurfaccounts.com\n\t\nsmurfaccounts.com\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-163\tBuyCSGORank\nbuycsgorank.com\n\t\nbuycsgorank.com\nDIRECT\n\tRank Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-164\tCSGOSmurfKings\ncsgosmurfkings.com\n\t\ncsgosmurfkings.com\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-165\tSmurfStore_Co\nsmurfstore.co\n\t\nsmurfstore.co\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-166\tSteamLvlUp\nsteamlvlup.com\n\t\nsteamlvlup.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-167\tSteamLevels\nsteamlevels.com\n\t\nsteamlevels.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-168\tLevelSteam\nlevelsteam.com\n\t\nlevelsteam.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-169\tSteamLevelU\nsteamlevelu.com\n\t\nsteamlevelu.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-170\tEloKing\neloking.com\n\t\neloking.com\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-171\tBoosteria\nboosteria.org\n\t\nboosteria.org\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-172\tOvergear\novergear.com\n\t\novergear.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-173\tBlazingBoost\nblazingboost.com\n\t\nblazingboost.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-174\tDota2Boost\ndota2boost.com\n\t\ndota2boost.com\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-175\tBuyBoost\nbuyboost.com\n\t\nbuyboost.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nSezione IV: Architettura tecnica e meccanismi di autenticazioneRIF.: TECH-ANALYSIS-01\n\n1. Mancanza di verifica della titolarità del dominio in OpenID 2.0: L'implementazione da parte di Valve del protocollo OpenID 2.0 (https://steamcommunity.com/openid/login) valuta il openid.return_to e openid.realm parametri senza richiedere la previa registrazione dello sviluppatore, la verifica tramite challenge crittografica o la convalida della titolarità del dominio. Qualsiasi operatore commerciale può indirizzare gli utenti alla schermata di accesso di Valve e ricevere un'asserzione di identità firmata crittograficamente (contenente lo SteamID a 64-bit) reindirizzata a domini arbitrari.\n\n2. Interrogazione programmatica dell’inventario e abuso delle chiavi “API”: Una volta confermata l'autenticazione dell'utente tramite OpenID, gli operatori effettuano una richiesta agli endpoint pubblici e dei partner del Web API (IEconItems_730/GetPlayerItems) per indicizzare le risorse di inventario in tempo reale. Le reti di trading automatizzate utilizzano token di sessione programmatici per inviare, richiedere e accettare offerte di scambio peer-to-peer (P2P), violando direttamente il divieto di interazione non umana previsto dalla sezione 4.C della SSA.\n\n3. Asimmetria del filtro di collegamento: La coesistenza di avvisi relativi a domini rivolti ai consumatori e di endpoint di autenticazione pienamente funzionanti crea una contraddizione normativa: la telemetria di sicurezza di Valve classifica questi operatori come “potenzialmente dannosi”, mentre l’infrastruttura di autenticazione di Valve continua ad autenticare la loro base di utenti.\n\nMetodologia probatoria e dichiarazione sulla catena di custodia\n\nIl presente documento è stato generato sulla base di acquisizioni di rete non autenticate, query storiche del registro “RDAP” e manifesti di hash crittografici verificati. Nessuna credenziale di accesso degli utenti è stata sottoposta a test di compromissione né elaborata. Tutti i risultati riflettono lo stato osservabile della rete di produzione al 2026. Questo documento costituisce una perizia tecnica imparziale, redatta a scopo di indagine giudiziaria, normativa e pubblica.\n\nSINTESI: SHA-256: VERIFICATO\nc507c9025f93da0aadaf395c4d8882f25973211c318ee8e9b6f18a5b3755e050\nARCHIVIO: DOCUMENTO GIURIDICO PUBBLICO\nEMESSO E FIRMATO DA: phishdestroy.io · Coalizione per la ricerca forense\nSTATUS GIURIDICO: TUTTI I DIRITTI CEDUTI ALL’UMANITÀ · CC0 DOMINIO PUBBLICO UNIVERSALE",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Legge sulla revisione forense e allegato normativo"
          }
        ],
        "links": []
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/it/regulatory_act_print.content.json",
      "export_json_sha256": "8e7da71a8bbe9df52656e4d2a3ad8782f1a35fc58329930567f424aa2f1d147f"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "it/security_timeline.html",
      "language": "it",
      "title": "Cronologia degli eventi relativi alla sicurezza — Il dossier “Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/it/security_timeline",
      "source_html_sha256": "1f391fc5c0c5fc35524e6aba83846ec073674958088359f53dc2fdd4fe8d08d6",
      "exported_at": "2026-09-29T00:17:54.965Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "security_timeline.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/it/security_timeline.pdf?v=print-20260929-v5",
        "sha256": "c5990f0c85e656934e7b894025d43db0299d1d57767e3c88e356ea5a2f76fcf7",
        "bytes": 96108,
        "pages": 7
      },
      "integrity": {
        "signed_object": "security_timeline.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "security_timeline.content.json.asc",
        "digest_file": "security_timeline.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify security_timeline.content.json.asc security_timeline.content.json",
          "sha256sum -c security_timeline.content.json.sha256"
        ]
      },
      "content": {
        "text": "IL BILANCIO SULLA SICUREZZAMOSTRA / OPERE PARTECIPANTI ALL’16\n\n2018 — 2026\n\nCronologia della sicurezza — Da 2018 a 2026\n\nLa sicurezza è cambiata. Segui la traccia.\n\nCOSA DIMOSTRA QUESTA SEZIONE\n\nQuesto resoconto cronologico ricostruisce otto anni di modifiche alla sicurezza apportate allo stack di negoziazione e autenticazione di Steam. Esso tiene traccia dell’2018, dell’7-, dell’implementazione del blocco giornaliero delle negoziazioni, dell’2023, delle conferme mobili tramite chiave Web API e della 2026, nonché della dismissione dei token di sessione in risposta alle tecniche di aggiramento documentate. La cronologia dimostra che gli aggiornamenti della piattaforma sono stati costantemente in ritardo rispetto ai vettori di exploit noti, pur preservando i vantaggi strutturali per gli operatori commerciali.\n\n← Torna al briefing esecutivo\n\nBlocchi delle transazioni. Controlli di accesso. Restrizioni relative all’API. Una cronologia dettagliata di ciò che è cambiato e di ciò che le fonti effettivamente dimostrano.\n\nEsplora la cronologia ↓\nOTTO ANNI. UN DISCO.16tappe da esaminare\n\nOgni voce conserva la data di invio e la fonte. Accanto ad essa viene visualizzata la verifica.\n\nRECENSITO / 24 SET 2026\n10Evento e data confermati\n06Verificato in parte\n00Discrepanza tra sorgenti\n00È necessaria la fonte\nCome leggere questo documento\n\nEvento e data verificati: entrambi supportati da una fonte primaria attendibile. Verificato in parte: è stata documentata una modifica correlata, ma la data o l'ambito di applicazione rimangono da definire. Discrepanza tra sorgenti: Il materiale allegato non conferma quanto affermato. È necessaria la fonte: In questa analisi non è stata verificata alcuna fonte datata corrispondente. La mancanza di una voce confermata non costituisce prova che un evento non si sia verificato.\n\nLe date riportate nelle voci non risolte sono le date di invio, non le date di pubblicazione verificate. Il testo originale dell'indagine non è stato riscritto.\n\nLa cronologia\n01 — 16\nCerca nel recordArgomentoProveOrdine\n\n16 tra i post di “16” · i più recenti per primi\n\n202609-01Data di invio\nComunitàVerificato in parte\nAvvisi relativi a messaggi sospetti nelle chat di gruppo\n\nUn annuncio ufficiale relativo alla versione beta conferma la disponibilità della funzionalità su 31 nel mese di agosto. La data di rilascio della versione stabile indicata su 1 per il mese di settembre necessita ancora di note di rilascio specifiche.\n\nSteam Client Beta — 31st agosto ↗archiviato su 2026-03-13 ↗\nVoce originale e link inviato\n\nSegnalazione automatica delle chat sospette\n\nEsamina il codice sorgente inviato ↗\n202601-16Data di verifica\nAPIEvento e data confermati\nAutorizzazioni granulari e whitelist IP per le chiavi degli editori (annuncio su Valve)\n\nIl 16 gennaio 2026, Valve ha pubblicato un annuncio ufficiale su Steamworks (\"NOVITÀ: autorizzazioni e controlli migliorati per le chiavi di \"API\" sul Web\") che confermano l'introduzione di nuovi strumenti per la gestione granulare delle autorizzazioni, che consentono agli sviluppatori di suddividere le chiavi di \"API\" del Web in gruppi distinti (Dati generali, microtransazioni, economia e vendite), limitare le chiavi a specifici ID app e applicare una lista bianca degli indirizzi IP dei server.\n\nIl palese doppio standard: Il presente comunicato ufficiale conferma che Valve ha completato lo sviluppo dell'infrastruttura tecnica necessaria per la gestione granulare delle autorizzazioni relative a API e delle restrizioni IP, ma le nasconde deliberatamente agli account utente standard (steamcommunity.com/dev/apikey). Le chiavi \"API\" utilizzate abitualmente dagli utenti rimangono credenziali monolitiche, del tipo \"tutto o niente\", prive di whitelist IP: ed è proprio questa omissione tecnica a rendere possibile l'esistenza di un settore da svariati milioni di dollari dedicato all'intercettazione delle transazioni \"API\".\n\nValve Annuncio — NOVITÀ: autorizzazioni e controlli migliorati per le chiavi di WebAPI (16 Jan 2026) ↗· Documentazione: Autenticazione tramite WebAPIe di Steamworks ↗\nVoce originale e link inviato\n\nAPIe web di Steamworks: Scopes granulari\n\nLeggi l'annuncio ufficiale di Valve su Steamworks (493839547938902179) ↗\n202507-15Data di verifica\nOperazioni di tradingEvento e data confermati\nLe operazioni su CS2 beneficiano di una finestra di inversione di sette giorni\n\nL'annuncio pubblicato da Valve introduce l'annullamento degli scambi di oggetti di Counter-Strike effettuati nei sette giorni precedenti. Sebbene sia stato concepito per mitigare il fenomeno dell'hijacking, le verifiche economiche condotte da terze parti (CSMarketCap ↗) ha registrato un $104M (-25%) collasso in termini di capitalizzazione di mercato nell’arco di 24 ore a causa di un’interruzione delle negoziazioni in contanti. Come analizzato da Skinvault ↗, l'attivazione di un'inversione comporta un blocco automatico del day trading 30-sul conto. In estate 2026, Valve è passato dal reset globale a mezzanotte UTC a timer individuali di un minuto per ogni voce (Skin.land ↗).\n\nValve — 15, 2025, annuncio del ↗· Analisi CSMarketCap ↗\nVoce originale e link inviato\n\nProtezione delle operazioni CS2 / Finestra di annullamento\n\nEsamina il codice sorgente inviato ↗\n202505-14Data di verifica\nAutenticazioneEvento e data confermati\nValve pubblica un avviso sulla sicurezza degli account in merito alla fuga di dati tramite SMS\n\nL'annuncio ufficiale di Valve del 14, 2025, riguarda la sicurezza degli account e gli autenticatori basati su SMS. Sebbene la comunicazione si concentri sulle fughe di dati tramite SMS e confermi che nessun sistema di Steam sia stato violato, essa costituisce un aggiornamento ufficiale sulla sicurezza alla data di pubblicazione.\n\nValve — Una nota sulla sicurezza del tuo account Steam ↗\nVoce originale e link inviato\n\nAvviso sulla sicurezza dell'account\n\nEsamina il codice sorgente inviato ↗\n202410-02Data di verifica\nOperazioni di tradingEvento e data confermati\nSette giorni prima della rivendita o della ricommercializzazione\n\nLe note di rilascio riguardano gli oggetti acquistati tramite il negozio in-game, tra cui l’Armeria, le offerte di scambio e il Mercato della community. L’ambito trattato è più ampio rispetto ai soli oggetti dell’Armeria.\n\nValve — Note di rilascio per l'10/2/2024 ↗\nVoce originale e link inviato\n\nCS2 The Armory / 7-Day Hold\n\nEsamina il codice sorgente inviato ↗\n202409-18Data di invio\nOperazioni di tradingVerificato in parte\nRestrizioni relative ai nuovi dispositivi verificate nelle pagine della guida\n\nLa documentazione ufficiale di supporto di Steam conferma una restrizione relativa al day trading 7-quando si effettua l'accesso da un nuovo dispositivo che non è stato autorizzato da almeno 7 giorni. Sebbene la data esatta di implementazione, 18, 2024,, non sia riportata come milestone nel changelog, la funzionalità è documentata in modo completo.\n\nSteam Assistenza — Restrizioni relative al trading e al mercato ↗\nVoce originale e link inviato\n\nRestrizione commerciale relativa all'accesso da un nuovo dispositivo\n\nEsamina il codice sorgente inviato ↗\n202402-14Data di invio\nComunitàVerificato in parte\nImplementato il tempo di attesa per il cambio di nome in 2024\n\nI registri della community e degli sviluppatori confermano che all’inizio del 2024, Valve è stato introdotto, senza preavviso, un periodo di attesa di 2-to-4 ora subito dopo la modifica del nome del profilo, al fine di mitigare le truffe basate sull’usurpazione rapida dell’identità. Poiché Valve non ha pubblicato alcun comunicato stampa ufficiale, log delle modifiche del client o articolo di supporto relativo a questa restrizione, la data indicata nel 14 di febbraio non è stata verificata formalmente; la guida del Steam Workshop funge da conferma indiretta da parte della community piuttosto che da documentazione ufficiale Valve.\n\nSteam Guida al workshop (corroborazione indiretta) — Dettagli sulle restrizioni relative al cambio di nome ↗\nVoce originale e link inviato\n\nSospensione della modifica del nome del profilo / dell'avatar\n\nEsamina il codice sorgente inviato ↗\n202312-04Data di verifica\nAPIEvento e data confermati\nLa generazione della chiave richiede una conferma tramite dispositivo mobile\n\nÈ stato accertato che l'introduzione della conferma obbligatoria tramite l'app mobile \"Steam Guard\" per la creazione delle chiavi Web API è avvenuta alla fine di 2023,, come documentato dalle librerie di sviluppatori di terze parti. La data esatta del 4, 2023, rappresenta il periodo di implementazione osservato all'interno della comunità degli sviluppatori.\n\nDocumentazione del responsabile della manutenzione — marzo 2024 ↗archiviato su 2026-09-24 ↗\nVoce originale e link inviato\n\nConferma tramite cellulare per le chiavi “API”\n\nEsamina il codice sorgente inviato ↗\n202310-24Data di verifica\nSviluppatoreEvento e data confermati\nEntra in vigore l'obbligo per la FA (2) di definire le formazioni in tempo reale durante le partite\n\nL'annuncio ufficiale di Valve su Steamworks del 10, 2023, conferma che, a partire dal 24, 2023,, qualsiasi account che pubblichi una build sul ramo predefinito di un'applicazione già rilasciata dovrà autorizzare la modifica tramite SMS o tramite l'app mobile Steam. Questa modifica ha aggiornato direttamente la pagina web SetAppBuildLive API.\n\nSteamworks — Miglioramenti alla sicurezza per la gestione delle build e degli utenti ↗archiviato su 2025-12-03 ↗\nVoce originale e link inviato\n\nAutenticazione a più fattori tramite SMS per le pubblicazioni relative alle build dei giochi\n\nEsamina il codice sorgente inviato ↗\n202307-12Data di invio\nComunitàVerificato in parte\nAvvisi relativi ai contenuti delle biografie personalizzate segnalati dalla comunità\n\nSteam Le segnalazioni della community a partire da luglio 2023 documentano che le biografie dei profili personalizzati contenenti link esterni o parole chiave hanno iniziato a visualizzare avvisi automatici sui contenuti. La data di invio del 7 luglio 12, 2023, coincide con la prima ondata di segnalazioni degli utenti sui forum della community Steam.\n\nSteam Forum della comunità — Segnalazioni relative agli avvisi sui contenuti biografici ↗\nVoce originale e link inviato\n\nAvviso relativo ai contenuti personalizzati della biografia\n\nEsamina il codice sorgente inviato ↗\n202301-25Data di invio\nComunitàVerificato in parte\nFiltraggio dei link ai profili e tempi di attesa per la modifica attivi\n\nLa documentazione ufficiale di supporto di Steam conferma che i link presenti nelle biografie personalizzate vengono filtrati e che modifiche abusive al nome o all’avatar possono comportare il divieto di modifica. Sebbene l’introduzione effettiva del periodo di attesa di un’4-, avvenuta il 1° gennaio 25, 2023,, rappresenti l’inizio effettivo di questa misura, il meccanismo di filtraggio dei link è già pienamente attivo, come indicato nella pagina di aiuto pubblicata.\n\nSteam Assistenza — Restrizioni relative al nome del profilo e all'avatar ↗\nVoce originale e link inviato\n\nProfilo LINK RIMOSSO / Tempo di recupero\n\nEsamina il codice sorgente inviato ↗\n202210-24Data di verifica\nAutenticazioneEvento e data confermati\nSteam Transizione dei clienti ai token di aggiornamento e di accesso OAuth\n\nPrincipali aggiornamenti di Valve relativi ai client e alle app mobili nel mese di ottobre 2022 ha rinnovato il sistema di autenticazione Steam. La vecchia struttura basata sui cookie di sessione è stata sostituita da token di accesso e di aggiornamento basati su OAuth ed è stato introdotto un elenco dei dispositivi autorizzati attivi per consentire la revoca manuale delle sessioni attive.\n\nValve — Aggiornamento dell’app mobile “Steam” e revisione del sistema di autenticazione ↗\nVoce originale e link inviato\n\nSteam Riorganizzazione della procedura di accesso / Tronchamento dei cookie\n\nConsulta l'annuncio su Valve ↗\n202210-12Data di verifica\nAutenticazioneEvento e data confermati\nAccesso tramite codice QR e gestione dei dispositivi autorizzati\n\nL'annuncio di Valve del 1° ottobre, intitolato \"12\", descrive la procedura di accesso tramite codice QR, l'approvazione o il rifiuto degli accessi e un elenco di dispositivi in grado di revocare l'accesso all'account.\n\nValve — È ora disponibile la versione aggiornata dell’app mobile “Steam” ↗\nVoce originale e link inviato\n\nSteam App mobile 3.0 / Accesso tramite codice QR\n\nEsamina il codice sorgente inviato ↗\n202205-10Data di invio\nAPIVerificato in parte\nGli endpoint relativi all'annullamento delle transazioni sono stati rimossi dall'elenco pubblico API\n\nI registri degli sviluppatori confermano che a maggio 2022, Valve sono stati silenziosamente rimossi gli endpoint di gestione delle transazioni, quali IEconService/CancelTradeOffer e DeclineTradeOffer, dal Web API (come documentato in node-steam-tradeoffer-manager #325). Sebbene tali metodi rimangano funzionanti nei protocolli client privati, la data del 10, 2022, indica la loro effettiva rimozione dalle API Web pubbliche al fine di contrastare i pannelli truffaldini.\n\nDiscussione degli sviluppatori — Issue n.325 (CancelTradeOffer rimosso) ↗· Sito web di Steamworks API — Documentazione di IEconService ↗\nVoce originale e link inviato\n\nRimozione dei punti finali di annullamento delle transazioni\n\nVisualizza il ticket #325 relativo a node-steam-tradeoffer-manager ↗\n202005-25Data di verifica\nOperazioni di tradingEvento e data confermati\nGli oggetti di Dota2s sono soggetti a un periodo di attesa di sette giorni prima di poter essere scambiati\n\nIl 25, 2020,, in concomitanza con il lancio del Battle Pass dell’International 10 (blog.dota2.com/2020/05/the-international-10-battle-pass/), Valve ha introdotto un blocco di 7-giorni sugli scambi degli oggetti di Dota 2, in linea con la politica di 2018 relativa a Counter-Strike. Questa restrizione si applica a tutti gli oggetti scambiati e agli acquisti effettuati sul Mercato.\n\nComunità di Dota2 — Blocco degli scambi e aggiornamento del client per TI10 ↗\nVoce originale e link inviato\n\nDota 2 / 7-Blocco delle operazioni di day trading\n\nEsamina il codice sorgente inviato ↗\n201803-29Data di verifica\nOperazioni di tradingEvento e data confermati\nGli oggetti di CS:GO scambiati sono soggetti a un periodo di attesa di sette giorni\n\nLe note di rilascio ufficiali confermano la data e la restrizione. L'URL fornito reindirizzava a un aggiornamento della mappa su 2013; l'URL corrispondente delle note di rilascio termina con 20309.\n\nValve — Note di rilascio per l'3/29/2018 ↗\nVoce originale e link inviato\n\nCS:GO / Blocco delle operazioni di day trading su 7-\n\nEsamina il codice sorgente inviato ↗ archiviato su 2025-02-26 ↗\n\nSegui le prove. Verifica la fonte.\n\nTorna all'indagine ↗",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Cronologia della sicurezza — Da 2018 a 2026"
          },
          {
            "level": 2,
            "id": null,
            "text": "La cronologia"
          },
          {
            "level": 2,
            "id": null,
            "text": "Avvisi relativi a messaggi sospetti nelle chat di gruppo"
          },
          {
            "level": 2,
            "id": null,
            "text": "Autorizzazioni granulari e whitelist IP per le chiavi degli editori (annuncio su Valve)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Le operazioni su CS2 beneficiano di una finestra di inversione di sette giorni"
          },
          {
            "level": 2,
            "id": null,
            "text": "Valve pubblica un avviso sulla sicurezza degli account in merito alla fuga di dati tramite SMS"
          },
          {
            "level": 2,
            "id": null,
            "text": "Sette giorni prima della rivendita o della ricommercializzazione"
          },
          {
            "level": 2,
            "id": null,
            "text": "Restrizioni relative ai nuovi dispositivi verificate nelle pagine della guida"
          },
          {
            "level": 2,
            "id": null,
            "text": "Implementato il tempo di attesa per il cambio di nome in 2024"
          },
          {
            "level": 2,
            "id": null,
            "text": "La generazione della chiave richiede una conferma tramite dispositivo mobile"
          },
          {
            "level": 2,
            "id": null,
            "text": "Entra in vigore l'obbligo per la FA (2) di definire le formazioni in tempo reale durante le partite"
          },
          {
            "level": 2,
            "id": null,
            "text": "Avvisi relativi ai contenuti delle biografie personalizzate segnalati dalla comunità"
          },
          {
            "level": 2,
            "id": null,
            "text": "Filtraggio dei link ai profili e tempi di attesa per la modifica attivi"
          },
          {
            "level": 2,
            "id": null,
            "text": "Steam Transizione dei clienti ai token di aggiornamento e di accesso OAuth"
          },
          {
            "level": 2,
            "id": null,
            "text": "Accesso tramite codice QR e gestione dei dispositivi autorizzati"
          },
          {
            "level": 2,
            "id": null,
            "text": "Gli endpoint relativi all'annullamento delle transazioni sono stati rimossi dall'elenco pubblico API"
          },
          {
            "level": 2,
            "id": null,
            "text": "Gli oggetti di Dota2s sono soggetti a un periodo di attesa di sette giorni prima di poter essere scambiati"
          },
          {
            "level": 2,
            "id": null,
            "text": "Gli oggetti di CS:GO scambiati sono soggetti a un periodo di attesa di sette giorni"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/it/#briefing-heading",
          "https://steamcommunity.com/groups/SteamClientBeta?l=english",
          "http://web.archive.org/web/20260313235409/https://steamcommunity.com/groups/SteamClientBeta?l=english",
          "https://store.steampowered.com/news/posts/?enddate=1788390000",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/493839547938902179",
          "https://partner.steamgames.com/doc/webapi_overview/auth",
          "https://csmarketcap.com/blog/market-insights/from-boom-to-bust-cs2s-trade-protection-impact",
          "https://skinvault.gg/blog/cs2-trade-protection-explained/",
          "https://skin.land/blog/steam-changes-cs2-trade-ban-logic-timing/",
          "https://store.steampowered.com/news/posts/?appids=730&amp;enddate=1753924057&amp;feed=steam_announce%2F1000",
          "https://help.steampowered.com/faqs/view/3041-A87A-E5F6-B6AC",
          "https://store.steampowered.com/news/posts/?enddate=1747349559",
          "https://steamcommunity.com/ogg/593110/announcements/detail/533224478739530146",
          "https://store.steampowered.com/news/posts/?appids=730&amp;enddate=1728000977&amp;feed=steam_community_announcements",
          "https://steamcommunity.com/games/CSGO/announcements/detail/4447966961421256740",
          "https://help.steampowered.com/faqs/view/7F77-9E92-31E0-6B8E",
          "https://steamcommunity.com/sharedfiles/filedetails/?id=2926756889",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "http://web.archive.org/web/20260924181824/https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "https://steamcommunity.com/dev/apikey",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3749866608167579206",
          "http://web.archive.org/web/20251203174259/https://steamcommunity.com/groups/steamworks/announcements/detail/3749866608167579206",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3734103130194459461",
          "https://steamcommunity.com/discussions/forum/1/3807266184852932971/",
          "https://help.steampowered.com/faqs/view/225C-C51E-B8F0-55B2",
          "https://store.steampowered.com/news/group/4/view/3314112260640237775",
          "https://store.steampowered.com/news/posts/?appgroupname=Keep+in+touch&amp;enddate=1666122699&amp;feed=steam_blog",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/issues/325",
          "https://partner.steamgames.com/doc/webapi/IEconService",
          "https://steamcommunity.com/app/570/announcements/",
          "https://blog.dota2.com/2020/05/trading-cooldown/",
          "https://blog.counter-strike.net/2018/03/20309/",
          "https://blog.counter-strike.net/index.php/2018/03/20308/",
          "http://web.archive.org/web/20250226114333/https://blog.counter-strike.net/index.php/2018/03/20308/",
          "https://phishdestroy.io/steam_dossier/it/#vulnerability-profile"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/it/security_timeline.content.json",
      "export_json_sha256": "f0c9f28d4c4b096e3f42924107440b22326441648a1893534beb633d2be59b18"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "it/skin_atlas.html",
      "language": "it",
      "title": "L'atlante di ciò che un \"Steam\" non può trasportare — Il dossier \"Steam\"",
      "source_url": "https://phishdestroy.io/steam_dossier/it/skin_atlas",
      "source_html_sha256": "373279184ad6bf4101fbfca18dd729fb1fc371c95974b23c548a0a9bb3f09258",
      "exported_at": "2026-09-29T00:17:57.757Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "gallery",
            "source": "https://phishdestroy.io/steam_dossier/it/skin_atlas#gallery"
          }
        ],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "skin_atlas.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/it/skin_atlas.pdf?v=print-20260929-v5",
        "sha256": "38c950253937dc85145288983b6b5a16b5efab41f582b8c78d9e85f44bb94c35",
        "bytes": 181894,
        "pages": 14
      },
      "integrity": {
        "signed_object": "skin_atlas.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "skin_atlas.content.json.asc",
        "digest_file": "skin_atlas.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify skin_atlas.content.json.asc skin_atlas.content.json",
          "sha256sum -c skin_atlas.content.json.sha256"
        ]
      },
      "content": {
        "text": "ALLEGATO IV-B / LA SCALA DEI PREZZI / 2026-09-23\nAtlante dei prezzi a scala della pelle — Il precipizio della liquidità\n\nLe tappe di Valve al mercato da dove nascono i soldi.\n\nCOSA DIMOSTRA QUESTA SEZIONE\n\nQuesto atlante visivo analizza le categorie di prodotti dell’30,266 presenti in cinque cataloghi di marketplace, misurando la copertura di mercato al di sopra e al di sotto della soglia di inserzione di Valve. Al di sotto del limite di $1,800, Steam ospita 95.3% di categorie attive; immediatamente al di sopra di esso, la copertura ufficiale si riduce a 1.9% (con una copertura 0.0% sulle attività verificate). Ciò evidenzia un brusco e strutturale crollo di liquidità in cui Valve affida l’individuazione delle transazioni di alto valore a piattaforme esterne, pur mantenendo il pieno controllo sulla custodia delle attività sottostanti.\n\n← Torna al briefing esecutivo\n\nOgni articolo CS2 con un prezzo attuale su cinque marketplace è stato inserito in una fascia di prezzo in base al prezzo di vendita più basso, e ogni fascia è stata valutata in base a un unico criterio: quale quota di essa è ancora disponibile nel Community Market di Valve. Al di sotto del limite massimo di inserzioni di Valve, la risposta è 95.3%. Sopra di essa, la risposta è 1.9%. Il calo non è graduale e non si verifica laddove diminuisce la domanda, bensì si verifica esattamente in base alla norma pubblicata. Tra i 248 le categorie di articoli per le quali due o più piattaforme fissano autonomamente prezzi superiori al limite massimo, 100.0% non presentano alcuna inserzione su Steam.\n\nGuarda la scogliera ↓Apri la galleria degli articoli \"419\"Metodo e limiti\n30,266categorie di articoli misurate\n95.3%delle voci fuori bilancio iscritte nel bilancio di Steam\n1.9%tra gli articoli fuori limite offerti da Steam\n$78.6Mvalore minimo dell'insieme confermato\n01 / la misurazione\nLa scogliera si basa sulla regola, non sulla richiesta\n\nCiascuna delle categorie di articoli \"30,266\" riportate di seguito è inserita in una fascia in base al suo più economico sondaggio in tempo reale su BUFF163, CSFloat, Skinport, YouPin 898 e C5Game; vengono conteggiati solo gli articoli citati su almeno due di queste piattaforme, quindi nessuna singola segnalazione ottimistica può inventare un membro della band. Il grafico in alto mostra la quota di mercato che ogni band detiene ancora sul mercato di Valve.\n\nQuota di ciascuna fascia di prezzo trattata dal Mercato Comunitario “Steam”\nin alto: copertura del vapore · in basso: elementi per banda, scala logaritmica\n0%\n25%\n50%\n75%\n100%\n100%\n96.9%\n95.9%\n97.3%\n91.1%\n76.8%\n14.5%\n2.9%\n1.5%\n0%\n0%\n0%\n4,632\n1¢–10¢\n7,152\n10¢–$1\n8,568\n$1–10\n5,941\n$10–100\n2,329\n$100–300\n1,292\n$300–1k\n193\n$1k–1.8k\n70\n$1.8k–3k\n67\n$3k–10k\n18\n$10k–30k\n3\n$30k–100k\n1\n$100k+\nitems\nlog\nVALVE’S LISTING CAP\npari o inferiore al limite massimo di quotazione di “Valve”oltre il limite massimo — la norma di “Valve” ne vieta la quotazionecategorie di articoli nella sezione \"band\"\n\nPer “copertura” si intende che, al momento dell’acquisizione, esisteva un’offerta in tempo reale su Steam per quella categoria. Il grafico in basso è in scala logaritmica poiché il catalogo è prevalentemente composto da articoli a basso prezzo: una lettura lineare appiattirebbe ogni fascia di prezzo superiore a $300, portandola al livello della linea di base.\n\nCosa esclude questa forma\n\nSe i beni costosi fossero semplicemente poco richiesti, la copertura diminuirebbe gradualmente all’aumentare del prezzo. Ma non è così. Si mantiene a 76.8% nella fascia compresa tra $300–$1k, per poi crollare a 14.5% nella fascia immediatamente al di sotto del tetto massimo e a 2.9% nella fascia immediatamente al di sopra di esso. Un effetto della domanda non tiene conto di dove Valve abbia fissato il proprio tetto massimo. Una regola sì.\n\nFascia di prezzo\tCategorie di articoli\tCon una richiesta in diretta su Steam\tSteam copertura\tElenco delle copie tratto da Steam\n1¢–10¢\t4,632\t4,632\t100%\t8,223,227\n10¢–$1\t7,152\t6,931\t96.9%\t5,488,315\n$1–10\t8,568\t8,213\t95.9%\t3,939,538\n$10–100\t5,941\t5,780\t97.3%\t1,328,255\n$100–300\t2,329\t2,121\t91.1%\t364,466\n$300–1k\t1,292\t992\t76.8%\t187,504\n$1k–1.8k\t193\t28\t14.5%\t40,281\n$1.8k–3k\t70\t2\t2.9%\t9,592\n$3k–10k\t67\t1\t1.5%\t6,706\n$10k–30k\t18\t0\t0%\t1,366\n$30k–100k\t3\t0\t0%\t21\n$100k+\t1\t0\t0%\t2\n\nLe varianti di modello e di fase sono escluse da questa classifica: Steam non riporta il livello “blue-gem” né la fase “Ruby” come voci a sé stanti nel proprio mercato, pertanto includerle significherebbe sottostimare la copertura di Steam. Se misurata senza il requisito dei due marketplace, la stessa classifica risulta essere 79.1% al di sotto del limite massimo e 6.5% al di sopra di esso per gli articoli su 37,204 — un divario più netto, basato su prove meno solide, motivo per cui non è la cifra citata.\n\n02 / valutazione probatoria\nIl prezzo richiesto non è un prezzo\n\nChiunque può mettere in vendita una P2000 a dieci milioni di yuan tondi. Prima che una cifra riportata in questa pagina venga utilizzata a qualsiasi scopo, viene classificata in base al numero di piattaforme di vendita che quotano l’articolo al di sopra del limite massimo e al grado di concentrazione del valore medio di tali quotazioni. Vengono riportate solo le classificazioni A e B — qui o in qualsiasi altra parte di questo dossier.\n\nA  Tre o più scaffali coincidono\n\nTre o più piattaforme di vendita online quotano l'articolo a un prezzo superiore al limite massimo e il loro prezzo mediano si colloca entro un25%e dal prezzo più basso. 197 categorie, 18,218 copie, $76,585,587.\n\nAssenti da “Steam”: 100.0%.\n\nB  I due scaffali sono uguali\n\nDue mercati si accordano su un valore superiore al limite massimo, oppure tre si accordano su un valore leggermente inferiore. 51 categorie, 176 copie, $2,038,814.\n\nAssenti da “Steam”: 100.0%.\n\nC  Un ripiano — non utilizzato\n\nUn unico mercato presenta l'unica offerta superiore al tetto massimo. 171 categorie, copie di “247”. Mostrati nella galleria per completezza ed esclusi da ogni totale riportato in questa pagina.\n\nSi tratta di richieste di preventivo, non di prove relative al prezzo.\n\nQuanto è costata questa correzione e cosa ha permesso di ottenere\n\nEliminando il voto C, dal titolo vengono rimosse le categorie “171” e “$3,825,125”. Ciò che rimane è più conciso e molto più difficile da contestare: 248 categorie, 18,394 copie elencate, $78,624,401, e 100.0% di esse — ogni singola — assenti dal mercato di Valve. Le righe di classe C sono il motivo per cui il dato è cambiato; sono infatti visibili, non nascoste.\n\nAnnunci accantonati come reperti\n\nQualsiasi quotazione superiore a tre volte il prezzo di vendita più basso per lo stesso articolo viene scartata. Se convertite al tasso implicito nei dati stessi, la maggior parte di esse risulta in cifre arrotondate in CNY: segno distintivo di un valore provvisorio o di un limite massimo della piattaforma, piuttosto che di un’offerta. Poiché ogni totale in questa pagina utilizza il più economico A dire il vero, nessuna di queste personalità avrebbe mai potuto gonfiare una cifra; sono state escluse proprio affinché nessuna di loro possa essere citata in un titolo.\n\nArticolo\tRichiesta in tempo reale più economica\tMetti da parte\nSouvenir P2000 | Wicked Sick (Minimal Wear)\t$148,954\t$1,489,543\n★ Specialist Gloves | Crimson Kimono (Minimal Wear) | Phase 1\t$37,239\t$119,163\nSouvenir USP-S | Printstream (Factory New)\t$2,000\t$59,582\n★ Bowie Knife | Crimson Web (Factory New)\t$2,957\t$43,030\n★ Karambit | Marble Fade (Factory New) | 1st\t$11,916\t$38,874\nSticker | Ninjas in Pyjamas (Holo) | Katowice 2014\t$5,000\t$31,748\nSouvenir AWP | Dragon Lore (Battle-Scarred)\t$4,225\t$29,157\n★ Karambit | Doppler (Minimal Wear) | Ruby\t$7,122\t$27,273\nTutte le categorie di \"419\", con l'oggetto a cui si riferisce ciascun prezzo\n\nFonte: https://phishdestroy.io/steam_dossier/it/skin_atlas#gallery\n\n04 / dove è finito invece\nGli scaffali che espongono ciò che Steam non espone\n\nGli stessi annunci, raggruppati in base alla piattaforma su cui sono pubblicati. Questo è un elenco dei luoghi in cui si trovano le copie elencati, che non coincide con il luogo in cui si trovano e qui non viene interpretato in tal senso.\n\nValore minimo degli annunci con prezzo superiore al limite massimo, per piattaforma\nprezzo di vendita più basso x copie presenti su quello scaffale\nYouPin 898\n$22,720,252\nBUFF163\n$22,022,606\nC5Game\n$12,560,543\nCSFloat\n$10,871,845\nSkinport\n$1,385,060\n\nGiurisdizioni, nell'ordine sopra indicato: YouPin 898 — Cina · BUFF163 — Cina · C5Game — Cina · CSFloat — Stati Uniti · Skinport — Germania / Malta. Lo stesso articolo fisico può essere inserito in più di uno di questi scaffali, pertanto questi dati non devono essere sommati ad alcun altro totale di mercato.\n\nValore minimo per fascia di prezzo\ncome vengono distribuiti i fondi oltre il limite massimo\n$1.8k-3k\n$9,842,391\n$3k-10k\n$36,787,269\n$10k-50k\n$20,038,749\nover $50k\n$2,891,897\n05 / la scarsità che si può quantificare\nQuanto è effettivamente scarsa l'offerta\n\nOgni oggetto CS2 ha un valore di usura, e le piattaforme di vendita pubblicano il numero di copie presenti in ciascuna fascia di tale valore. Questo trasforma “raro” da aggettivo a numero — ed è proprio quel numero a spiegare perché un singolo account compromesso valga lo sforzo di realizzare un kit di phishing su misura.\n\nAWP | La storia dei draghi\n150 in vendita · a partire da $11,350\n0.00–0.01\n29 · $14,730\n0.01–0.02\n54 · $11,618\n0.02–0.03\n26 · $11,350\n0.03–0.04\n25 · $11,618\n0.04–0.07\n16 · $11,585\n\nAWP | Dragon Lore (nuovo di fabbrica)\n\nM4A4 | Howl\n105 in vendita · a partire da $6,628\n0.00–0.01\n11 · $10,725\n0.01–0.02\n14 · $8,088\n0.02–0.03\n11 · $7,580\n0.03–0.04\n19 · $6,703\n0.04–0.07\n50 · $6,628\n\nM4A4 | Howl (nuovo di fabbrica)\n\nAK-47 | Wild Lotus\n113 in vendita · a partire da $14,373\n0.00–0.01\n25 · $22,343\n0.01–0.02\n11 · $19,364\n0.02–0.03\n3 · $19,645\n0.03–0.04\n15 · $15,044\n0.04–0.07\n59 · $14,373\n\nAK-47 | Wild Lotus (nuovo di fabbrica)\n\nAWP | Gungnir\n173 in vendita · a partire da $11,618\n0.00–0.01\n28 · $17,875\n0.01–0.02\n21 · $13,600\n0.02–0.03\n32 · $12,065\n0.03–0.04\n29 · $11,735\n0.04–0.07\n63 · $11,618\n\nAWP | Gungnir (nuovo di fabbrica)\n\nAK-47 | Serpente di fuoco\n278 in vendita · a partire da $663\n0.15–0.18\n87 · $730\n0.18–0.21\n49 · $712\n0.21–0.24\n52 · $703\n0.24–0.27\n18 · $715\n0.27–0.38\n72 · $663\n\nAK-47 | Serpente di fuoco (testato sul campo)\n\nCementato (tutti i livelli / gemma blu)\n76 in vendita · a partire da $1,638\n0.07–0.08\n1 · $2,516\n0.08–0.09\n4 · $2,482\n0.09–0.10\n6 · $3,856\n0.10–0.11\n7 · $2,797\n0.11–0.15\n58 · $1,638\n\nAK-47 | Cementato (usura minima) | Livello1\n\nLe fasce rappresentano i gruppi di titoli disponibili sul mercato; vengono prese in considerazione solo le fasce con almeno una quotazione in tempo reale. Il prezzo indicato accanto a ciascuna barra corrisponde alla domanda in tempo reale più bassa all’interno di quella fascia, pertanto il premio associato a un flottante ridotto è direttamente leggibile anziché dichiarato.\n\n06 / movimento, misurato su Steam\nCosa hanno effettivamente realizzato gli scaffali di terze parti\n\nValve non pubblica dati storici utilizzabili a questo livello, e il presente dossier non ne riporta alcuno. Skinport pubblica invece le proprie vendite concluse nelle ultime 24 ore, 7, 30 e 90 giorni, e questa è l’intera dimensione temporale disponibile in questa sede: un prezzo mediano realizzato per ogni finestra temporale, indicizzato in modo tale che la mediana giornaliera 90-sia 100. Nessuno dei due grafici contiene dati relativi a “Steam”.\n\nPrezzo mediano realizzato, finestra mobile\nindicizzato sulla mediana giornaliera dell'90-· 6,758 articoli con 20+ vendite\n85\n91\n97\n103\n100\n90d\n94\n30d\n90\n7d\n88\n24h\nVendite concluse al giorno\nstessi articoli, stesse finestre\n7,621\n9,653\n11,684\n13,716\n12,700\n90d\n11,894\n30d\n9,540\n7d\n8,637\n24h\n\nSi tratta di due grafici distinti, non di un unico grafico con due scale verticali: un indice e un conteggio giornaliero non condividono la stessa unità di misura, e tracciarli su un asse comune darebbe adito a un confronto non valido. Le finestre sono annidate e sequenziali — il dato giornaliero 90-contiene il dato orario 24-— quindi non si tratta di una serie giornaliera e non deve essere interpretata come tale. Ciò che emerge è limitato e chiaramente indicato: nelle finestre di periodo successive Skinport pubblicate, il prezzo mediano realizzato si è attestato al di sotto della propria mediana giornaliera 90-e il numero di vendite giornaliere è sceso di conseguenza.\n\nSkinport vendite realizzate. Le finestre sono annidate e scorrevoli, quindi ogni punto rappresenta il prezzo mediano realizzato nell’intervallo della finestra scorrevole, indicizzato rispetto alla mediana giornaliera dell’90-. Non si tratta di una serie giornaliera e non vengono utilizzati dati dell’Steam.\n\n07 / di cosa è fatto\nAdesivi vecchi di sedici anni e una manciata di guanti\n\nIl segmento al di sopra del tetto massimo non rappresenta una fetta ampia del mercato. Si concentra su poche rarità e poche collezioni, molte delle quali non sono più reperibili in assoluto — ed è proprio per questo che l'offerta non riesce a rispondere al prezzo.\n\nCategorie al di sopra del limite massimo, ordinate per rarità\nnumero delle categorie di articoli\nCovert\n321\nClassified\n39\nRestricted\n24\nContraband\n12\nMil-Spec Grade\n9\nConsumer Grade\n9\nIndustrial Grade\n5\nCategorie al di sopra del limite massimo, per collezione\nle dieci migliori collezioni\nThe St. Marc Collection\n13\nThe Cobblestone Collection\n13\nThe Norse Collection\n12\nThe Arms Deal Collection\n9\nThe Canals Collection\n7\nThe Gods and Monsters Collection\n6\nThe Revolution Collection\n4\nThe 2021 Train Collection\n4\nThe Rising Sun Collection\n4\nThe Chop Shop Collection\n4\n\nPer categoria: skin 366, sticker 48, container 3, sticker_slab 2.\n\n08 / l'importo massimo effettivamente pagato da chiunque\nMassimi sostenuti da un’operazione, non da una quotazione\n\nTutti gli altri prezzi riportati in questa pagina sono un chiedere — ciò che desidera un venditore. Questi sono vendite: il valore massimo di una transazione Skinport registrata per ciascun articolo negli ultimi 90 giorni. È l’unico dato contenuto in questo dossier che qualcuno abbia effettivamente pagato, e ogni riga rimanda al marketplace, in modo che l’importo possa essere verificato direttamente alla fonte anziché tramite noi.\n\n21,216articoli con una vendita conclusa in vetrina\n106venduto a un prezzo pari o superiore al limite massimo di quotazione di “Valve”\n$14,192vendita singola più alta mai conclusa\n67/419categorie al di sopra del limite massimo con almeno una vendita registrata\nLe trenta vendite concluse di importo più elevato nel periodo in esame\nArticolo\tVendita più alta\tPrezzo mediano di vendita\tVendite\tChiedi subito il prezzo più conveniente\tSteam\tDai un'occhiata\nAWP | Gungnir (Factory New)\t$14,192\t$11,343\t5\t$11,490\tabsent\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Factory New)\t$12,387\t$12,387\t1\t$13,836\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Factory New)\t$11,779\t$11,063\t16\t$10,941\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Minimal Wear)\t$11,693\t$11,693\t1\t$9,946\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Minimal Wear)\t$10,437\t$10,437\t1\t$9,610\tabsent\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Blue Laminate (Minimal Wear)\t$9,772\t$37\t76\t$30\t$40\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Minimal Wear)\t$9,463\t$9,463\t1\t$9,500\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Minimal Wear)\t$9,104\t$9,026\t6\t$8,524\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Hedge Maze (Minimal Wear)\t$8,139\t$8,139\t1\t$6,819\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Field-Tested)\t$7,617\t$7,390\t4\t$7,194\tabsent\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Field-Tested)\t$7,615\t$7,615\t1\t$7,100\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Field-Tested)\t$7,149\t$7,006\t2\t$7,165\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Field-Tested)\t$6,711\t$6,194\t15\t$5,988\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Factory New)\t$6,679\t$6,613\t3\t$6,628\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Superconductor (Factory New)\t$6,084\t$6,084\t1\t$7,969\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Battle-Scarred)\t$5,750\t$5,413\t3\t$5,899\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Pandora's Box (Minimal Wear)\t$5,520\t$5,508\t3\t$4,998\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Vice (Factory New)\t$5,385\t$5,158\t2\t$5,700\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Minimal Wear)\t$5,342\t$4,989\t19\t$4,997\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Hedge Maze (Field-Tested)\t$5,334\t$4,862\t5\t$3,724\tabsent\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Vulcan (Factory New)\t$5,275\t$1,418\t12\t$1,280\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Well-Worn)\t$4,978\t$4,978\t1\t$4,942\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Well-Worn)\t$4,931\t$4,931\t1\t$5,445\tabsent\tSkinport CSFloat Steam\nAK-47 | Hydroponic (Factory New)\t$4,802\t$4,351\t2\t$3,648\tabsent\tSkinport CSFloat Steam\n★ Talon Knife | Case Hardened (Minimal Wear)\t$4,588\t$466\t16\t$442\t$630\tSkinport CSFloat Steam\nAWP | Medusa (Factory New)\t$4,484\t$4,484\t1\t$4,171\tabsent\tSkinport CSFloat Steam\n★ Specialist Gloves | Pillow Punchers (Factory New)\t$4,359\t$4,359\t1\t$4,302\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Pandora's Box (Field-Tested)\t$4,359\t$3,666\t11\t$3,245\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Field-Tested)\t$4,289\t$4,225\t8\t$4,022\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Battle-Scarred)\t$4,124\t$4,124\t1\t$4,279\tabsent\tSkinport CSFloat Steam\nStesso articolo, stessa 90 giorni, prezzo completamente diverso\n\nLimitato agli articoli con una mediana di $100 e almeno cinque vendite concluse, perché nel caso di una skin economica una singola vendita anomala fa sballare il rapporto. Ciò che rimane è dominato da Cementato finiture, dove il modello determina il prezzo e il marketplace archivia ogni modello sotto un unico nome — lo stesso meccanismo misurato tramite float nella sezione 05.\n\nArticolo\tValore massimo vs. mediana\tVendita più alta\tPrezzo mediano di vendita\tVendite\tDai un'occhiata\n★ Talon Knife | Case Hardened (Minimal Wear)\t+884%\t$4,588\t$466\t16\tSkinport CSFloat Steam\nDesert Eagle | Cobalt Disruption (Factory New)\t+859%\t$1,210\t$126\t115\tSkinport CSFloat Steam\nAWP | BOOM (Minimal Wear)\t+814%\t$1,232\t$135\t89\tSkinport CSFloat Steam\nAK-47 | Case Hardened (Well-Worn)\t+769%\t$1,720\t$198\t70\tSkinport CSFloat Steam\nAWP | Graphite (Factory New)\t+761%\t$1,469\t$171\t124\tSkinport CSFloat Steam\n★ Talon Knife | Case Hardened (Field-Tested)\t+509%\t$2,437\t$400\t48\tSkinport CSFloat Steam\n★ Kukri Knife | Case Hardened (Minimal Wear)\t+448%\t$723\t$132\t69\tSkinport CSFloat Steam\n★ Kukri Knife | Case Hardened (Field-Tested)\t+415%\t$549\t$106\t128\tSkinport CSFloat Steam\n★ Ursus Knife | Case Hardened (Minimal Wear)\t+371%\t$597\t$127\t12\tSkinport CSFloat Steam\nAK-47 | Case Hardened (Field-Tested)\t+369%\t$1,037\t$221\t125\tSkinport CSFloat Steam\nAK-47 | Red Laminate (Minimal Wear)\t+360%\t$552\t$120\t18\tSkinport CSFloat Steam\nAWP | Asiimov (Field-Tested)\t+351%\t$528\t$117\t439\tSkinport CSFloat Steam\nAK-47 | Vulcan (Field-Tested)\t+337%\t$865\t$198\t241\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Nightwish (Factory New)\t+322%\t$625\t$148\t31\tSkinport CSFloat Steam\nAWP | Lightning Strike (Factory New)\t+319%\t$2,065\t$493\t198\tSkinport CSFloat Steam\nStatTrak™ AWP | Redline (Minimal Wear)\t+312%\t$574\t$139\t24\tSkinport CSFloat Steam\nStatTrak™ AWP | Asiimov (Battle-Scarred)\t+287%\t$524\t$135\t37\tSkinport CSFloat Steam\nAK-47 | Redline (Minimal Wear)\t+277%\t$562\t$149\t112\tSkinport CSFloat Steam\nAWP | Crakow! (Factory New)\t+275%\t$379\t$101\t72\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Vulcan (Factory New)\t+272%\t$5,275\t$1,418\t12\tSkinport CSFloat Steam\n\nSi tratta del massimo giornaliero registrato su 90-, NON di un massimo storico, e riguarda UN SOLO marketplace. In questo dossier non viene riportato da nessuna parte alcun dato relativo a un massimo storico. Un articolo che non presenta alcuna vendita su Skinport nella finestra è del tutto assente da questa raccolta, motivo per cui l’insieme è più ridotto rispetto al censimento.\n\nI link di verifica sono generati dagli identificatori della piattaforma del catalogo stesso. Rimandano alla pagina dedicata all’articolo su ciascun marketplace, in modo che il lettore possa verificare l’immagine confrontandola con la fonte piuttosto che con noi. I link in uscita contengono rel=\"nofollow\": si tratta di citazioni, non di approvazioni, e molte delle destinazioni sono piattaforme che questa indagine critica.\n\n09 / provenienza e limiti\nDa dove proviene e cosa non è in grado di mostrare\n\nOgni dato riportato in questa pagina è stato ricalcolato sulla base di due file di snapshot i cui hash sono pubblicati accanto ad essi. Nessuna delle informazioni qui riportate è stata trascritta da un articolo pubblicato su un altro sito.\n\nFonte e accesso\n\ncs2.sh API, GET /v1/prices/latest e GET /v1/schema, istantanea singola, acquisita il 2026-09-23T00:44:27.871388581Z, prezzi in USD.\n\nI dati sono stati ottenuti tramite un abbonamento commerciale a pagamento sottoscritto dal richiedente dell’GDPR, come documentato nell’archivio, secondo i termini stabiliti dal fornitore stesso. Non è stato effettuato alcuno scraping su nessuna piattaforma di vendita e non sono state utilizzate le credenziali di nessuna piattaforma di vendita. La chiave del richiedente è conservata al di fuori di questo repository e non compare in nessun file qui presente.\n\nCome si determina l'idoneità di un articolo\n\nOgni articolo di base con almeno un'offerta attiva su BUFF, CSFloat, Skinport, YouPin o C5Game viene inserito in una fascia di prezzo in base alla sua offerta PIÙ ECONOMICA; pertanto, la fascia non dipende mai da Steam. La \"coperturaSteam\" è la percentuale di articoli in quella fascia che presentano un'offerta attiva Steam al momento della rilevazione. Le varianti di modello e di fase sono escluse dalla classifica poiché Steam non le elenca separatamente; includerle comporterebbe una sottostima di Steam. I rendering sono le immagini di catalogo relative agli stessi articoli, memorizzate localmente.\n\nRender e diritti sulle immagini. I render degli articoli del catalogo sono immagini fornite dal provider per lo stesso *market_hash_name* delle righe dei prezzi, memorizzate localmente per la visualizzazione offline e su IPFS. I rendering non sono opera di PhishDestroy: tutte le immagini degli articoli, i loghi e gli screenshot rimangono di proprietà dei rispettivi titolari (cs2.sh, CSFloat, Skinport, BUFF, YouPin, C5Game, Valve e altri). Sono riprodotti esclusivamente a scopo identificativo e di informazione di interesse pubblico; non viene rivendicata alcuna proprietà né licenza.\n\nCiò che non siamo riusciti a ottenere\n\nIl livello di abbonamento utilizzato copre solo le istantanee attuali. Gli endpoint storici e di archivio non erano disponibili, e in nessuna parte di questa pagina viene riportata alcuna serie storica Oltre ai dati sulle vendite con finestra mobile, Skinport pubblica i propri dati nella sezione 06.\n\nUn’istantanea, non una serie temporale. L'assenza di un annuncio su Steam al momento della cattura non è prova che un articolo non possa mai apparire lì; si tratta dello stato rilevato dello scaffale in quel momento e, per i prezzi superiori al limite massimo, è anche ciò che richiede la regola pubblicata dValve: il Community Market di Valve limita esplicitamente gli annunci a $1,800 per articolo (con un saldo massimo del Portafoglio Steam di $2,000; vedi Steam Domande frequenti sul Mercato della Comunità archiviato su 2026-09-21 ↗ e Steam Contratto di abbonamento § 3.C archiviato su 2026-09-24 ↗).\n\nValutazione\n\nIl prezzo di un articolo corrisponde sempre al prezzo di vendita più basso in tempo reale, quindi un valore anomalo elevato non può mai gonfiare il totale. La classificazione determina quali righe possono essere quotate. Qualsiasi quotazione superiore a tre volte il prezzo di vendita più basso per lo stesso articolo viene scartata in quanto non considerata un prezzo in tempo reale. Grado A: tre o più piattaforme continuano a quotare al di sopra del limite massimo e la loro mediana rientra nell’25% del prezzo più basso. Grado B: due piattaforme concordano, oppure tre concordano ma con margini meno stretti. Grado C: un unico prezzo di listino – un prezzo richiesto, non un prezzo di mercato. Nel presente dossier vengono riportati esclusivamente i gradi A e B.\n\nRegola sui valori anomali: quotazione > 3.0moltiplicata per il prezzo di vendita più basso dello stesso titolo.\n\nPerché i totali rappresentano un valore minimo\n\nPer ogni marketplace, l'articolo più basso Il prezzo di vendita richiesto viene moltiplicato per il numero di copie presenti nello scaffale. Tutte le altre copie presenti hanno un prezzo pari o superiore a quel prezzo minimo richiesto, quindi il valore effettivo pubblicato è più alto per definizione, non per stima. Non si tratta di una vendita, né di un flusso di cassa, né di una valutazione dell’economia di CS2.\n\nVerificalo tu stesso\n\nI set di dati da cui sono stati ricavati tutti i grafici presenti in questa pagina sono pubblicati integralmente: il set di dati Atlas, la schermata di classificazione e degli artefatti, il censimento di riferimento e il manifesto contenente lo SHA-256e di ciascuna istantanea grezza.\n\nUna correzione registrata in apertura\n\nUna bozza precedente del registro di riferimento riportava in primo piano un Souvenir AK-47 | Point Disarray, con un prezzo richiesto di $148,954 su una piattaforma di vendita cinese, mentre Steam lo quotava a $119. Quella riga è di grado C: un unico scaffale, un unico esemplare e nessun’altra piattaforma di vendita che confermi il prezzo. Si tratta di un prezzo richiesto, non di un prezzo effettivo, ed è stato declassato sia qui che su quella pagina. Il prodotto leader confermato è Sticker | Titan (Holo) | Katowice 2014 a $66,285, citato da 4, presenti su 5.2% a breve distanza l'uno dall'altro — e del tutto assenti da Steam.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Atlante dei prezzi a scala della pelle — Il precipizio della liquidità"
          },
          {
            "level": 2,
            "id": null,
            "text": "La scogliera si basa sulla regola, non sulla richiesta"
          },
          {
            "level": 3,
            "id": null,
            "text": "Cosa esclude questa forma"
          },
          {
            "level": 2,
            "id": null,
            "text": "Il prezzo richiesto non è un prezzo"
          },
          {
            "level": 3,
            "id": null,
            "text": "A  Tre o più scaffali coincidono"
          },
          {
            "level": 3,
            "id": null,
            "text": "B  I due scaffali sono uguali"
          },
          {
            "level": 3,
            "id": null,
            "text": "C  Un ripiano — non utilizzato"
          },
          {
            "level": 3,
            "id": null,
            "text": "Quanto è costata questa correzione e cosa ha permesso di ottenere"
          },
          {
            "level": 3,
            "id": null,
            "text": "Annunci accantonati come reperti"
          },
          {
            "level": 2,
            "id": null,
            "text": "Tutte le categorie di \"419\", con l'oggetto a cui si riferisce ciascun prezzo"
          },
          {
            "level": 2,
            "id": null,
            "text": "Gli scaffali che espongono ciò che Steam non espone"
          },
          {
            "level": 2,
            "id": null,
            "text": "Quanto è effettivamente scarsa l'offerta"
          },
          {
            "level": 2,
            "id": null,
            "text": "Cosa hanno effettivamente realizzato gli scaffali di terze parti"
          },
          {
            "level": 2,
            "id": null,
            "text": "Adesivi vecchi di sedici anni e una manciata di guanti"
          },
          {
            "level": 2,
            "id": null,
            "text": "Massimi sostenuti da un’operazione, non da una quotazione"
          },
          {
            "level": 3,
            "id": null,
            "text": "Le trenta vendite concluse di importo più elevato nel periodo in esame"
          },
          {
            "level": 3,
            "id": null,
            "text": "Stesso articolo, stessa 90 giorni, prezzo completamente diverso"
          },
          {
            "level": 2,
            "id": null,
            "text": "Da dove proviene e cosa non è in grado di mostrare"
          },
          {
            "level": 3,
            "id": null,
            "text": "Fonte e accesso"
          },
          {
            "level": 3,
            "id": null,
            "text": "Come si determina l'idoneità di un articolo"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ciò che non siamo riusciti a ottenere"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valutazione"
          },
          {
            "level": 3,
            "id": null,
            "text": "Perché i totali rappresentano un valore minimo"
          },
          {
            "level": 3,
            "id": null,
            "text": "Verificalo tu stesso"
          },
          {
            "level": 3,
            "id": null,
            "text": "Una correzione registrata in apertura"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/it/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/it/skin_atlas#gallery",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://skinport.com/market?search=AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260924114457/https://store.steampowered.com/subscriber_agreement/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-atlas.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-artefact-screen.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-above-the-ceiling.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/it/skin_atlas.content.json",
      "export_json_sha256": "d0d5465e8f3cc6e63f307e40dec0bcb70e8a8d452cfa6f0454befaaa73b3ff7a"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "it/social_graph.html",
      "language": "it",
      "title": "Segui i collegamenti documentati — Il dossier “Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/it/social_graph",
      "source_html_sha256": "3693385811eab2507282461e9d20fcef64e080e545b2a6aa06e3df5a8fda70e6",
      "exported_at": "2026-09-29T00:17:57.425Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "social_graph.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/it/social_graph.pdf?v=print-20260929-v5",
        "sha256": "b1166ebe1bfdd96b893f31181a5097a7b5fd33b6fb40769a4603d37eaa2fe32e",
        "bytes": 119753,
        "pages": 6
      },
      "integrity": {
        "signed_object": "social_graph.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "social_graph.content.json.asc",
        "digest_file": "social_graph.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify social_graph.content.json.asc social_graph.content.json",
          "sha256sum -c social_graph.content.json.sha256"
        ]
      },
      "content": {
        "text": "Segui i collegamenti.Esamina ogni relazione.\n\nCerca un profilo. Scegli un tipo di relazione. Segui i suoi vicini diretti nei record acquisiti. Strumento di ricerca: I collegamenti rappresentano relazioni pubbliche, non costituiscono prova di contatti diretti, coordinamento privato o comportamenti scorretti tra due nodi qualsiasi. La struttura dei nodi di un grafico “3,435-” si interpreta al meglio utilizzando dei filtri.\n\nEsplora una relazione alla volta\n\n💡 Clicca e trascina i nodi per riorganizzare il grafico. Passa il mouse sopra per visualizzare i profili dettagliati. Linee continue color verde acqua = amicizie, linee tratteggiate color ambra = commenti reciproci.\n\nTipo di relazioneProfilo e vicini diretti\n\n3,435 profili · 4,551 link registrati\n\nCerca e seleziona un profilo, oppure clicca su un nodo. Rimangono solo i suoi vicini diretti registrati. Un arco registra una relazione; non stabilisce un coordinamento privato.\n\nProfili presenti nel set di dati acquisito\n\nTabella completa dei dati: Scarica tutte le righe di \"3,435\" (CSV). La tabella sottostante mostra inizialmente le prime 25 righe; la funzione di ricerca e l'impaginazione consentono di visualizzare l'intero set di dati.\n\n1–25 / 3,435 righe\nNome del personaggio\tSteamID64\tPrivacy\tStato\tIscrizioni di gruppo\tScorte congelate (USD)\tUbicazione\nMahatma Gandhi\t76561198333721623\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tPH\nGalley//갤리🌠🌙\t76561198043416832\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tKP\n$Schlächter\t76561198860277343\tPUBLIC\tClean\tsteambans\t$0.00\tUnknown\n❄r3dsn0w000™❄ [Cristi]🎮\t76561197986767957\tPUBLIC\tClean\tCommunityLegends\t$0.00\tRO\n(2a03) Wolfy\t76561197991671851\tPUBLIC\tCommunity\tsr_public\t$0.00\tUS\nZloy2288\t76561198038578334\tPUBLIC\tClean\tsteambans\t$0.00\tBY\njessy\t76561198039125237\tPUBLIC\tCommunity, VAC (1x)\tCommunityLegends\t$0.00\tJP\nJithraRufure\t76561198071896910\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\n| Níllerdínho |\t76561198003487438\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tDK\nJones is back\t76561198023013026\tPRIVATE\tVAC (1x)\tsteambans\t$0.00\tUnknown\nUNEX | ★✠☠ MoH3st ☠✠\t76561198050763123\tPUBLIC\tClean\tsteambans\t$0.00\tDE\nTrojan\t76561198048457084\tPUBLIC\tClean\tCommunityLegends\t$0.00\tDE\n𝗠𝗮𝘆𝘂 ❤\t76561199377967696\tPUBLIC\tClean\tsr_public\t$0.00\tIS\nbig fucking idiot\t76561198871206397\tPUBLIC\tVAC (1x)\tsteambans\t$0.00\tUnknown\nSOFF Games\t76561198227129276\tPUBLIC\tClean\tcommunitymoderators\t$0.00\tRU\nThijminecraft02\t76561198253895669\tPUBLIC\tClean\tSteamIDcouk SArchive\t$0.00\tNL\nStatic-sama\t76561198289329793\tPUBLIC\tClean\tsteambans\t$0.00\tJP\n𝙸mmortal 𝚂targazer\t76561198142116760\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\nCommander Keen\t76561197987773287\tPUBLIC\tClean\tsteambans\t$0.00\tBE\nS1mX\t76561199648509165\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\nmixwell\t76561199276547472\tPUBLIC\tClean\tsr_public\t$0.00\tJP\nP90_GOD_YyEs™\t76561198285821942\tPUBLIC\tClean\tsteambans\t$0.00\tHK\nhewwo?\t76561199133807546\tPUBLIC\tVAC (1x)\tsteambans\t$0.00\tCH\n♕Kamikaze Atze♕\t76561198002700103\tPUBLIC\tClean\tsteambans\t$0.00\tDE\nPastica\t76561198154655970\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tDZ\nLegami di amicizia registrati\n\nTabella completa dei dati: Scarica tutte le righe dell'4,299e (CSV). La tabella sottostante mostra inizialmente le prime 25 righe; la funzione di ricerca e l'impaginazione consentono di visualizzare l'intero set di dati.\n\n1–25 / 4,299 righe\nUtente A\tDirezione\tUtente B\tTipo di relazione\nMahatma Gandhi\n76561198333721623\t↔\tDeskjet\n76561198272738437\tMutual Friends\nGalley//갤리🌠🌙\n76561198043416832\t↔\tomega\n76561197960274529\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tFisty\n76561198057301486\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tFaalagorn\n76561198001116101\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tMURK\n76561198036995672\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tÅρøᴛʜℯᴛȋᴄÅʟȋℯη ♛👽♛\n76561197984615267\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tsilatrak\n76561197999629462\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tBlack Blade\n76561198083368493\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tAvenger\n76561197978249317\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tRemtar\n76561198124322650\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tCato\n76561197961345984\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t✪ G λ M Ξ ®\n76561197994308495\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tclees42\n76561198030936806\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t𝓜ε𝔰𝔥 | AusLevels\n76561198108828539\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tSgtFopper™\n76561198002555892\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t❥Miss Bee\n76561198046958996\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tTesTy\n76561198032370068\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tskl_andrey\n76561198136881436\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t\"Exekutor\"\n76561198009583947\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tAraripe\n76561198103754372\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tsteve6678\n76561198053200093\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\ttrinner\n76561197970359081\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tSteph S.\n76561198025653291\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tKirito\n76561198154545657\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tDoc. todt\n76561197984492467\tMutual Friends\nLink ai commenti registrati\n\nTabella completa dei dati: Scarica tutte le righe di \"252\" (CSV). La tabella sottostante mostra inizialmente le prime 25 righe; la funzione di ricerca e l'impaginazione consentono di visualizzare l'intero set di dati.\n\n1–25 / 252 righe\nAutore\tDirezione\tProfilo del target\tData\tTesto del commento\nDeskjet\n76561198272738437\t→\tMahatma Gandhi\n76561198333721623\t16 September, 2021 @ 11:02:05 pm PDT\t\"𝑵𝒐𝒘 𝒊𝒇 𝑰 𝒇𝒖𝒄𝒌 𝒕𝒉𝒊𝒔 𝒎𝒐𝒅𝒆𝒍𝑨𝒏𝒅 𝒔𝒉𝒆 𝒋𝒖𝒔𝒕 𝒃𝒍𝒆𝒂𝒄𝒉𝒆𝒅 𝒉𝒆𝒓 𝒂𝒔𝒔𝒉𝒐𝒍𝒆𝑨𝒏𝒅 𝑰 𝒈𝒆𝒕 𝒃𝒍𝒆𝒂𝒄𝒉 𝒐𝒏 𝒎𝒚 𝑻-𝒔𝒉𝒊𝒓𝒕𝑰'𝒎𝒎𝒂 𝒇𝒆𝒆𝒍 𝒍𝒊𝒌𝒆 𝒂𝒏 𝒂𝒔𝒔𝒉𝒐𝒍𝒆\" - Nelson Mandela\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t22 November, 2021 @ 4:10:28 pm PDT\thttps://anige.horigiri.net/?cat=22\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t18 November, 2021 @ 12:45:26 am PDT\thttps://gamerch.com/umamusume/entry/250411\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t8 August, 2021 @ 4:13:25 am PDT\thttps://modoocode.com/304\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t6 February, 2021 @ 3:35:05 pm PDT\t▤ ∫︹- -ω⁾ ⁽︹▓▓︺\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t11 December, 2019 @ 1:50:53 am PDT\thttps://blog.naver.com/aksenwlddj12/221369410039\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t2 October, 2019 @ 7:11:59 am PDT\tǤαllєу║︎갤리..۩\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t9 April, 2019 @ 12:51:28 pm PDT\tExplosiveDamage(owner, from, maxrange, minrange, distmultiplier, dmgmultiplier, mindamage, typ, damagetype, ignore)\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 12:22:47 pm PDT\tinfo - sh_titles.lua\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 12:21:46 pm PDT\tlocal nibbas = 1344 init.lua\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 11:31:58 am PDT\thttp://foreign.aladin.co.kr/shop/wproduct.aspx?ItemId=123955531&start=slayer\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t3 April, 2019 @ 1:26:41 am PDT\tǤαllєу\nLei\n76561198982197954\t→\tJithraRufure\n76561198071896910\t29 December, 2024 @ 12:58:08 pm PDT\t+rep he knows how 2 rush B ￣ヘ￣\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t2 September, 2026 @ 5:16:55 am PDT\tlol\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t20 August, 2026 @ 6:11:03 am PDT\t?\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t25 July, 2026 @ 7:20:05 am PDT\thahahahaha\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t30 June, 2026 @ 12:52:42 pm PDT\twow\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t30 June, 2026 @ 12:41:32 pm PDT\txD\nvalorant enjoyer\n76561199112142402\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:26:30 pm PDT\toh no!!\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:26:11 pm PDT\toh no!!\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:22:22 pm PDT\tomg !!! they know my secret, omg!!!\nvalorant enjoyer\n76561199112142402\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:21:39 pm PDT\t+rep good ♥♥♥♥♥ player\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:20:50 pm PDT\tomg! u cant cheat on secure gaben servers, omg dont report me, they ban me for boosted omg\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 8:37:11 pm PDT\txD\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t28 June, 2026 @ 1:58:14 pm PDT\twow",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Segui i collegamenti.Esamina ogni relazione."
          },
          {
            "level": 2,
            "id": null,
            "text": "Esplora una relazione alla volta"
          },
          {
            "level": 2,
            "id": null,
            "text": "Profili presenti nel set di dati acquisito"
          },
          {
            "level": 2,
            "id": null,
            "text": "Legami di amicizia registrati"
          },
          {
            "level": 2,
            "id": null,
            "text": "Link ai commenti registrati"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-profiles.csv",
          "https://steamcommunity.com/profiles/76561198333721623",
          "https://steamcommunity.com/profiles/76561198043416832",
          "https://steamcommunity.com/profiles/76561198860277343",
          "https://steamcommunity.com/profiles/76561197986767957",
          "https://steamcommunity.com/profiles/76561197991671851",
          "https://steamcommunity.com/profiles/76561198038578334",
          "https://steamcommunity.com/profiles/76561198039125237",
          "https://steamcommunity.com/profiles/76561198071896910",
          "https://steamcommunity.com/profiles/76561198003487438",
          "https://steamcommunity.com/profiles/76561198023013026",
          "https://steamcommunity.com/profiles/76561198050763123",
          "https://steamcommunity.com/profiles/76561198048457084",
          "https://steamcommunity.com/profiles/76561199377967696",
          "https://steamcommunity.com/profiles/76561198871206397",
          "https://steamcommunity.com/profiles/76561198227129276",
          "https://steamcommunity.com/profiles/76561198253895669",
          "https://steamcommunity.com/profiles/76561198289329793",
          "https://steamcommunity.com/profiles/76561198142116760",
          "https://steamcommunity.com/profiles/76561197987773287",
          "https://steamcommunity.com/profiles/76561199648509165",
          "https://steamcommunity.com/profiles/76561199276547472",
          "https://steamcommunity.com/profiles/76561198285821942",
          "https://steamcommunity.com/profiles/76561199133807546",
          "https://steamcommunity.com/profiles/76561198002700103",
          "https://steamcommunity.com/profiles/76561198154655970",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-connections.csv",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-comments.csv"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/it/social_graph.content.json",
      "export_json_sha256": "6323896b4dbfcbcbb3a461bd87e6cc1289ea42e87ad99d10d793846204e2ddb5"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "it/steam_enforcement_evidence.html",
      "language": "it",
      "title": "Regole contro risposte — Il dossier “Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/it/steam_enforcement_evidence",
      "source_html_sha256": "ddab66329177a10aca08d6c94014008287767bfbefbcc9e4f39e007efc5f64bb",
      "exported_at": "2026-09-29T00:17:59.068Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "steam_enforcement_evidence.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/it/steam_enforcement_evidence.pdf?v=print-20260929-v5",
        "sha256": "ff8cb9d691af707a65694ede4a82660c84b9d3d48f19dfc0712f12e8fb525905",
        "bytes": 378263,
        "pages": 36
      },
      "integrity": {
        "signed_object": "steam_enforcement_evidence.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "steam_enforcement_evidence.content.json.asc",
        "digest_file": "steam_enforcement_evidence.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify steam_enforcement_evidence.content.json.asc steam_enforcement_evidence.content.json",
          "sha256sum -c steam_enforcement_evidence.content.json.sha256"
        ]
      },
      "content": {
        "text": "Allegato probatorio / documenti collegati alla fonte\nSteam Prove relative all'applicazione delle norme — Documentazione di supporto e rete degli sviluppatori\n\nLa regola. La risposta.\n\nCOSA DIMOSTRA QUESTA SEZIONE\n\nQuesta sezione dedicata alle prove mette a confronto il Contratto di abbonamento ufficiale di Valve con i registri delle azioni di applicazione datati, le risoluzioni delle controversie relative all’assistenza e i registri della rete degli sviluppatori presenti nei repository di 252 e nei profili di 3,320. Dimostra che i titolari di account ordinari subiscono azioni di applicazione e chiusure dell’assistenza non confutabili a seguito di violazioni delle sessioni, mentre le operazioni commerciali su larga scala con bot continuano a funzionare senza interruzioni con accesso all’infrastruttura pubblica.\n\n← Torna al briefing esecutivo\n\nLeggi la restrizione scritta. Apri la risposta registrata. Confronta ciò che risulta dalla fonte con ciò che rimane senza risposta.\n\nAssistenza e ricorsi ↓Infrastrutture pubbliche ↓\n252record dell'archivio\n3,320profili pubblici\n4,214coppie distinte di profili e repository\n98,902coppie di profili con repository condivisi\n01 / Sostegno, sanzioni e risanamento\nLeggi la denuncia.Allega il file sorgente.\nGalleria dei rifiuti di sostegno (Mostre di 981) ↗Scarica i record selezionati ↓\nHFB / IL CASO DELL'OUTSOURCINGIl compromesso riconosciuto.\nI licenziamenti segnalati.\n\nSi prega di fare riferimento alla risposta dell'assistenza qui riportata e alla fonte dell'affermazione relativa al personale dell'appaltatore.\n\nApri il caso e le relative fonti →\n\nDi seguito: cinque esemplari conservati post pubblici su Reddit dalla raccolta di assistenza fornita. Ogni record documenta un’interazione segnalata con il sistema di assistenza di Valve — conservata con il link originale alla fonte, la posizione di acquisizione e il testo completo. Si tratta di testimonianze delle vittime. I registri di assistenza autenticati che potrebbero confermarle o smentirle sono in possesso di Valve e non sono stati resi pubblici.\n\n01\nBan & review2024-12-09\nPermanent sanction & closed appeals\n\nThe author reports a permanent account ban, repeated ticket closures and a planned GDPR access request.\n\nREDDIT / PUBLIC TESTIMONYr/ohnePixelCapture record 294\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 303 words\nPermanently banned Steam account without a clear explanation, need help!\n\nsteam_support_tickets_MEGA.json / record 294\n\nHey everyone,\n\nI’m in a really frustrating situation, and I’m hoping someone here can help me or offer advice. My Steam account was just permanently banned for allegedly violating the Steam Subscriber Agreement, and I have no idea why.\n\n# What Steam Support told me:\n\nThe support message said my account was banned due to:\n\n* Suspicious activities related to transferring or attempting to sell/trade the account.\n* Community reports and other unspecified factors.\n\nThey added that the ban is permanent and that they can't help me further. They also warned that future support requests regarding this ban might be ignored. 😞\n\n# Why I’m contesting this ban:\n\n* I have never sold, traded, or transferred my account. I’ve been the legitimate owner since the beginning.\n* On the day the ban occurred, I did nothing noteworthy that could have triggered such a sanction.\n* I received no prior warning, which feels incredibly unfair.\n\n# What I’ve tried so far:\n\n* Contacting Steam Support: I explained my situation and asked for more details, but they’re sticking to their decision and closing my tickets.\n* I’m preparing a request based on my Right of Access (GDPR) to get all the data related to my account.\n\n# Questions for the community:\n\n1. Has anyone successfully had a permanent ban lifted on Steam?\n2. Are there steps I can take to prove I’m the legitimate owner of the account?\n3. Any advice on how to word my request to convince support to reconsider my case?\n4. Would it be helpful to contact the CNIL (I’m based in France) to force Steam to provide more information?\n\nI’m really desperate at the thought of losing all my games, purchases, and years of playtime. Thanks in advance for any help and advice you can give!\n\nhttps://preview.redd.it/jk9qv0gmhv5e1.png?width=1289&amp;format=png&amp;auto=webp&amp;s=b3a333ebb08ea133e2c8747ba126f5a68283d9f7\n\nhttps://preview.redd.it/4sopt0gmhv5e1.png?width=1022&amp;format=png&amp;auto=webp&amp;s=56195d5336118faf9413f1514ead7e8d24c788c3\n\nhttps://preview.redd.it/eqrxw0gmhv5e1.png?width=996&amp;format=png&amp;auto=webp&amp;s=ff3539d28ab754e513ad471822c5de652920101d\n\nhttps://preview.redd.it/728xz0gmhv5e1.png?width=1034&amp;format=png&amp;auto=webp&amp;s=bc5335673509929669af785aa244bf8d2dc58da8\n\n02\nSupport access2025-05-09\nAccount recovery & a reported $10,000 loss\n\nThe author alleges that support reset credentials and removed account protection following another person’s recovery ticket.\n\nREDDIT / PUBLIC TESTIMONYr/legaladviceCapture record 110\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 193 words\nGot $10k stollen from steam inventory due to steam' support fault.\n\nsteam_support_tickets_MEGA.json / record 110\n\nLocation: Quebec, Canada.\n\nLast year, someone hacked my Steam account and stole items worth about $10,000 USD. I only noticed this last week. When I talked to Steam Support, they admitted that someone submitted a ticket to make changes on the account and Steam Support reset my password and turned off all my account security.\n\nI asked Steam Support about getting my items back, but they said there was nothing they could do. They told me I should follow their security recommendations.\n\nThe problem is, I did everything they \"suggested\" to protect an account:\n\n* I had two-factor authentication.\n* My phone number was connected to my account.\n* I used Steam Guard.\n* I printed recovery codes and kept them in a safe.\n\nEven though I did all these things, Steam Support still gave someone else access to my account. The stolen items had been in my account since around 2016-2017. Also, I had not logged in for a few years, so I didn’t accidentally give my information to a fake website.\n\nIs there anything I can do, or do I just have to accept losing $10,000 USD?\n\nThanks for your help.\n03\nRestoration2022-07-07\nA reported $500+ loss & template replies\n\nThe author describes an account compromise, disputed transactions and a support response that allegedly did not address the submitted evidence.\n\nREDDIT / PUBLIC TESTIMONYr/DotA2Capture record 45\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 410 words\nFunds stolen through steam market. Disappointed with Steam response.(or lackthereof)\n\nsteam_support_tickets_MEGA.json / record 45\n\nOn 6th July 2022, 44 unauthorized transactions were made on the steam market using my steam wallet funds totalling roughly $500+ USD to buy worthless 1 cent Dota 2 items. This happened during the wee hours in the morning and i contacted them first thing when i woke up. \n\nI have 2FA enabled all the time, and always thought this would not happen to me as I do not go on betting sites/click sketchy links. My account password + emails were not changed, nor did they take my inventory, just that my funds were used illicitly. Also when I went to disable other APIs, it says there are no other APIs to disable. Shows that it wasn't through me clicking sketchy links and leaving my account details there. Would have lost the whole account if i did so.\n\nWhat baffles me is how did they bypass my 2FA to login my account? Why doesn't steam market purchases go through 2FA as well? First time in 9 years that this happened to me. My acc was logged in 'BY' 'Vitebsk' during the illicit purchases but I'm based in Asia I gathered all the screenshots and provided in the ticket to steam support. \n\nAll i got was the standard copy paste template reply by Steam Support. Lost $500+ and was not even worthy of having a proper person to look into this. I dont think they even read or take a look at the screenshots cause if they did, they would have come to the realization that what happened was clearly fraud, and with a few clicks, reverse the unauthorized transactions, refund my wallet and ban the hijacker. \n\nOver the years, i've spent quite a fair bit on steam but really, this is the kind of recourse we get when our account is compromised? They just don’t care, sigh. I only expect the bare minimum from Steam and looks like even that is quite far-fetched.\n\nSS: https://imgur.com/a/67frcls \n\nHijacker: https://steamcommunity.com/profiles/76561199141246495\n\nSteam Response: https://imgur.com/a/V6v4maM\n\nI could think of a few ways on how to Improve:\n\n1) Add 2FA to market transactions. (even if its bulk posting or selling of items, just 1 2FA notif is required)\n\n2) Enable accounts to be region locked. (if you are migrating, then have to go through steam support etc)\n\n3) Additional Lock on Steam Wallet. (Another password perhaps?)\n\nEDIT: 2nd ticket in and I have still yet to receive a non robotic copy paste template response from Steam.\n04\nRestoration2021-11-29\nSteam Guard & an item-restoration refusal\n\nA preserved post includes the author’s account of item theft and a support response declining restoration.\n\nREDDIT / PUBLIC TESTIMONYr/DotA2Capture record 58\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 563 words\nMany people are losing item via clicking links where steam guard is enabled and steam support doesn't not restore items.\n\nsteam_support_tickets_MEGA.json / record 58\n\nAccounts are getting compromised and might be their pc as well where Steam market is targeted hence the malicious links . I am assuming these hackers are getting encouraged where steam support is not doing nothing and they are getting away with hacking items.  \nLiterally the guy who is supporting the game which he doesn't get any in game advantage just  cosmetics in game only for the sole purpose of supporting the game so that the game will prosper and become beautiful way  to enjoy weekend. But right now players are getting hacked left right and center and steam support  is copy pasting message where in short they are blaming the guy who clicked link. 1st this is happening because they are not targeting players but they are targeting market since they are selling those stuff for real cash via party website. Steam is a huge company and can eradicate the problem or at least can remove links temporarily  in chat since hackers are targeting .They made us install steam guard by saying we wont help if there is no steam guard now steam guard is not enough to save our inventory now they changed their policy  that they should not click any suspicious links. How would we know if the link is suspicious ? After clicking and getting our inventory stolen right !   \n\"we'd have to duplicate an item to restore it. Duplication lowers the value of all items by reducing their scarcity and inflating the economy, which affects everyone involved in trading and the Market. To maintain the value of everyone’s inventory, we do not restore items. For more information, please see the Steam Item Restoration Policy.\"  \nThey care for millions of people IN STEAM MARKET where as few  are losing items which is going to affect market where the rightful owner bought the items and hacker is going to sell the item via 3rd party website and enjoy ! HOW IRONIC !!  \nThis is the message from support where my frnd got his items stolen via clicking on link  \n   \nHi there,  \n\nThank you for the information and screenshots provided.  \n\nIt appears that the account was compromised, please take the following steps to secure your account and computer:  \n\nScan your computer for viruses, key loggers, spyware, and other malicious code using antivirus software with updated virus definitions.  \nChange the password for the email address that is associated with your Steam account.  \nRegularly reset your Steam account password.  \n\nPlease see our Security Recommendations article.  \n\nIn addition, I’m sorry to hear that your items were removed without your permission. Unfortunately, Steam Support does not restore scammed, lost, or stolen items for any reason.  \n\nSince Steam Support does not remove items from accounts, we'd have to duplicate an item to restore it. Duplication lowers the value of all items by reducing their scarcity and inflating the economy, which affects everyone involved in trading and the Market. To maintain the value of everyone’s inventory, we do not restore items. For more information, please see the Steam Item Restoration Policy.  \n\nTo make sure that a scammer is reported, please report them through the Steam Community. Reporting a scammer through the Steam Community is the best way to prevent them from committing future scams.  \n\nTo learn how to avoid scams or hijackings, please see our Trade Scam article.  \n\nIf you still need assistance, please let us know.\n05\nEnforcement2025-05-11\nSelective enforcement & an unexplained ban\n\nA community member describes a disputed ban and contrasts it with the visibility of commercial gambling promotion.\n\nREDDIT / PUBLIC TESTIMONYr/SteamUncensoredCapture record 107\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 1,208 words\n🚨 Steam Bans Without Reason and Ignores Its Community — What’s Going On?\n\nsteam_support_tickets_MEGA.json / record 107\n\nHey r/Steam,\n\nI’m writing this to share my thoughts and concerns about my friend [moneylead](https://steamcommunity.com/id/moneylead/) and Steam’s policies in general. I spoke with him yesterday about his situation, though I didn’t discuss writing this post with him—I asked last night, but he hasn’t responded yet. I want to highlight that this issue is broader than just his case, and while Steam might make changes in the future (though that’s unlikely), I feel the community needs to understand how far Steam has strayed from its original values. I’m not trying to put moneylead in a tough spot with this thread—all the info I’m sharing is public, nothing secretive. I hope he won’t be upset with me, but the community needs this case to see the bigger picture and how Steam feels completely unaccountable.\n\n**Why Does Steam Ignore Its Community?**  \nWhy does a platform like **Roblox** provide a detailed log of ban reasons, while Steam, which claims to be \"community-driven,\" ignores its community, bans whoever they want, for whatever they want, with no transparency? I looked into Roblox as a popular game—not a direct competitor to Steam—to see how their bans look, and you can check it out yourself: [Roblox Ban Reasons](https://www.google.com/search?q=Roblox+ban). Their bans are clear, detailed, and actually explain what you did wrong. I think most decent gaming communities operate like this—not with support agents named Olga, hired through outsourcing, who only know how to send canned auto-replies. Take cases like St4ck—or my friend **moneylead**. All these unbans, like **St4ck’s** or **Alexanddd’s**, happened behind closed doors with zero comments from Steam. Of course, it’s convenient for Steam to handle everything in secret, so no one knows or sees what’s going on—but this violates Steam’s own community rules and principles.\n\n**Who Is moneylead?**  \nI’ve known [moneylead ](https://steamcommunity.com/id/moneylead/)since around 2021. We played Dota 2 a couple of times, and then I just stayed on his friends list. He’s always been a legit player, bringing revenue to Steam through purchases. He never sold his skins, whether in **Dota or CS2—he wasn’t a trader**. All he did was:\n\n* Buy games and skins.\n* Collect badges to level up his profile.\n\nAccording to [SteamSets](https://steamsets.com/account/76561199080934614), he’s given out 324,000 Steam Points—I think he awarded profile rewards to all his friends in the list (though I’m not 100% sure). I do know he ran contests and gave gifts to friends, always supporting the community.\n\n**Steam’s Unfair Treatment**  \nI’ve seen Steam remove his showcases, avatar, description, and even his country multiple times—just because he’s from **Ukraine**. He has a ton of haters leaving toxic comments on his wall, and Steam seems to favor **Russian** users. Every time he tried to appeal the removal of his showcases or profile description—which didn’t break any rules, just had his Instagram link, and his avatar is the same as it is now—Steam moderators didn’t care. **They don’t care about top players who bring them massive revenue, nor about regular users.**\n\n>*Here’s the worst part: moneylead works in cybersecurity, specifically fighting account theft and phishing. He’s neutralized over 5,000 threats targeting Steam alone. And yet, Steam bans him for \"account hijacking\"?*\n\nIf you roughly calculate moneylead’s contribution to Steam and the community—his profile, level, badges (not skins, you can’t sell those)—is this normal, Steam? Banning people, closing tickets, and ignoring users with a spotless reputation who aren’t involved in any commercial activity, just bringing you profit without taking anything in return?\n\n**Steam’s Double Standards**  \nI’m honestly shocked:\n\n* YouTubers who promote casinos and skin gambling? Steam’s fine with that.\n* A cybersecurity expert who fights scams, doesn’t promote casinos, and openly talks about it on his profile? **Banned with no explanation, ignored, and denied an unban.**\n\nI wonder if Steam deliberately bans a high-level account once a year just because of their impunity—maybe for hype or something. Otherwise, this is just madness. It’s scary to think how many regular players have lost their accounts and skins—not because of scammers, but because of Steam’s desire to ignore, send auto-replies, and do whatever they want.\n\n**How Many Others Are Affected?**  \nHow many others are out there—maybe not as well-known—who just have a few games or skins, get banned for nothing, and receive zero explanation or response? **Is this even legal?** Every other platform provides a detailed log with specific violations, but Steam slaps on the same vague label and sends templated responses.\n\n* How safe is it to buy skins on Steam?\n* What’s the chance Steam will just ban your account for no reason, with no explanation?\n\n**A Message to Valve**  \nI wish moneylead the best in resolving this, but Valve, it’d be great if you remembered what \"community\" means and started following the law. Because right now, it looks like your 30% commission, impunity, and sense of being above the law in the U.S. have given you the idea that you can do whatever you want.\n\nI’m sure there are many others like moneylead and St4ck—people who aren’t public or don’t have the resources to fight back. Let’s unite these cases. **If you’re a U.S. resident who’s been banned by Steam without reason and wants to challenge it, please reach out to me.** I’m finishing my **Juris Doctor (J.D.) program at SMU Dedman School of Law** in Dallas, Texas, and I’m participating in a legal clinical practice under Rule 13 of the Texas Supreme Court.\n\nWhat Steam is doing is absolutely disgusting and illegal, and **I’d be happy to help any gamer (legitimate, with no real violations) who has games or skins with value. This will be beneficial for my practice, and it’s time to put Steam in its place and show them they can’t just dictate their own rules with arbitration**. Let’s take it all the way—not for punishment, but for the sake of the community. Maybe if Steam loses a case, they’ll change their policies and start explaining their actions like most popular gaming communities do. Many of us remember how Steam Support used to recover stolen accounts and ended up “stealing” skins themselves—banning without real reasons is basically the same thing, and that’s a serious accusation.\n\nSo, r/Steam, see you soon. I think you understand what you’re doing and how many people you’ve illegally deprived of their assets. I want to raise this issue—not just for the U.S., but for the entire world. You’ve banned class-action lawsuits? **Welcome to Texas.** I recommend starting to look for licensed attorneys in Texas, because I’d love to discuss your company’s policies, feedback, and support agents named Olga—a name that strongly associates with Russian users. Maybe it’d be easier to move your company to Moscow? But I’d be happy to discuss these critical issues on behalf of the global gaming community.\n\nAlso, I wouldn’t recommend ignoring the lawsuit request that will be sent to your physical address and email address, as the court will proceed without you, and that might upset you—especially since things aren’t going so well for a company with stocks like yours.\n\n**Thanks to everyone who took the time to read this. For those who need real help with an unjust Steam ban without any explanation, I’d be happy to assist. For users from Texas, we can easily file a collective lawsuit against Steam—let’s connect and make it happen.**\n02 / Rete di sviluppo “Steam”\nInfrastrutture pubbliche.Registrato su larga scala.\nScarica tutti i brani di “252” ↓\n\nIl prodotto in dotazione output_steam_network Le istantanee registrano i repository, le relazioni pubbliche tra contributori e fork e le sovrapposizioni dei profili. Si tratta di dati pubblicati: cosa è stato realizzato, chi ha contribuito, cosa è stato sottoposto a fork. La documentazione scritta delle capacità pubbliche è ciò di cui deve rendere conto l’Valve.\n\nRepository / descrizione\tCollaboratori\tForkers\tProfili registrati\nalliedmodders/amxmodx\n\nAMX Mod X - Half-Life 1 Scripting and Administration\n\n\t40\t40\t80\nalliedmodders/sourcemod\n\nSourceMod - Source Engine Scripting and Administration\n\n\t40\t40\t80\nDoctorMcKay/node-steam-user\n\nAllows interaction with the Steam network via the Steam client protocol\n\n\t40\t40\t80\nFacepunch/Facepunch.Steamworks\n\nAnother fucking c# Steamworks implementation\n\n\t40\t40\t80\nJustArchiNET/ArchiSteamFarm\n\nC# application with primary purpose of farming Steam cards from multiple accounts simultaneously.\n\n\t40\t40\t80\nodota/core\n\nOpenDota: Open source Dota 2 data platform with automated replay parsing\n\n\t40\t40\t80\nodota/dotaconstants\n\ndotaconstants: Static data for Dota applications\n\n\t40\t40\t80\nodota/web\n\nOpenDota: React web UI for Dota 2 statistics using the OpenDota platform\n\n\t40\t40\t80\nsplewis/get5\n\nCS:GO Sourcemod plugin for competitive matches/scrims\n\n\t40\t40\t80\nSteamDatabase/FileDetectionRuleSets\n\n🔎 Rules to detect game engines and other technologies based on Steam depot file lists\n\n\t40\t40\t80\nSteamRE/SteamKit\n\nSteamKit2 is a .NET library designed to interoperate with Valve's Steam network. It aims to provide a simple, yet extensible, interface to perform various actions on the network.\n\n\t40\t40\t80\nValveSoftware/dxvk\n\ndxvk tree containing branches used by Proton\n\n\t40\t40\t80\nValveSoftware/GameNetworkingSockets\n\nReliable & unreliable messages over UDP. Robust message fragmentation & reassembly. P2P networking / NAT traversal. Encryption.\n\n\t40\t40\t80\nValveSoftware/gamescope\n\nSteamOS session compositing window manager\n\n\t40\t40\t80\nValveSoftware/Proton\n\nCompatibility tool for Steam Play based on Wine and additional components\n\n\t40\t40\t80\nValveSoftware/source-sdk-2013\n\nThe 2013 edition of the Source SDK\n\n\t40\t40\t80\nValveSoftware/wine\n\nWine with a bit of extra spice\n\n\t40\t40\t80\nValveSoftware/steam-devices\n\nList of devices Steam and SteamVR will want read/write permissions on, to help downstream distributions create udev rules/etc\n\n\t39\t40\t79\nValveSoftware/steam-audio\n\nSteam Audio\n\n\t38\t40\t78\nalliedmodders/metamod-source\n\nMetamod:Source - C++ Plugin Environment and Detour Library for the Source Engine\n\n\t37\t40\t77\nalliedmodders/sourcepawn\n\nA small, statically typed scripting language.\n\n\t35\t40\t75\nValveSoftware/Fossilize\n\nA serialization format for various persistent Vulkan object types.\n\n\t31\t40\t71\nrlabrecque/Steamworks.NET\n\nSteamworks wrapper for Unity / C#\n\n\t27\t40\t67\nModDota/moddota.github.io\n\nModDota github pages project.\n\n\t26\t40\t66\nodota/parser\n\nReplay parse server generating JSON log events from Dota 2 replay files\n\n\t26\t40\t66\nValveSoftware/steam-for-linux\n\nIssue tracking for the Steam for Linux beta client\n\n\t26\t40\t66\nSteamRE/DepotDownloader\n\nSteam depot downloader utilizing the SteamKit2 library.\n\n\t24\t40\t64\nJustArchiNET/ASF-ui\n\nThe official web interface for ASF\n\n\t23\t40\t63\nadvancedfx/advancedfx\n\nHalf-Life Advanced Effects (HLAE) is a tool to enrich content creation mainly for the Counter-Strike series.\n\n\t22\t40\t62\nalliedmodders/ambuild\n\nAlliedModders C++ Build System\n\n\t23\t39\t62\nSteamDatabase/BrowserExtension\n\n💻 SteamDB's extension for Steam websites\n\n\t21\t40\t61\nodota/mobile\n\nReact Native apps for viewing Dota 2 data on Android/iOS\n\n\t19\t40\t59\nValvePython/steam\n\n☁️ Python package for interacting with Steam\n\n\t18\t40\t58\nskadistats/clarity\n\nComically fast Dota 2, CSGO, CS2 and Deadlock replay parser written in Java.\n\n\t13\t40\t53\nSteamRE/open-steamworks\n\nOpen Steamworks is a set of reverse engineered headers for the Valve's Steam Client. More or less abandoned now that the Steamworks SDK is publically available.\n\n\t13\t40\t53\nValveSoftware/Source-1-Games\n\nSource 1 based games such as TF2 and Counter-Strike: Source\n\n\t13\t40\t53\nalliedmodders/hl2sdk\n\nHalf-Life 2 SDK Mirrors\n\n\t11\t40\t51\nSteamDatabase/steamdb.info-issues\n\n🚱 Issue tracker for the SteamDB website\n\n\t11\t40\t51\nCSGOFloat/inspect\n\nSource Code that Powers the CSFloat Inspect Link API\n\n\t10\t40\t50\nValveSoftware/SteamOS\n\nSteamOS community tracker\n\n\t10\t40\t50\nalliedmodders/source2mod\n\nExperimental\n\n\t40\t9\t49\nsmiley/steamapi\n\nAn unofficial object-oriented Python library for accessing the Steam Web API.\n\n\t9\t40\t49\nSteamDatabase/GameTracking\n\n🛢 Dumping things, so you don't have to\n\n\t8\t40\t48\nValveSoftware/counter-strike_rules_and_regs\n\nCS:GO\n\n\t7\t40\t47\nValveSoftware/openvr\n\nOpenVR SDK\n\n\t6\t40\t46\nSteamDatabase/easy-markdown-editor\n\nEasyMDE: A simple, beautiful, and embeddable JavaScript Markdown editor. Delightful editing for beginners and experts alike. Features built-in autosaving and spell checking.\n\n\t40\t4\t44\nValveSoftware/Dota-2\n\nTracker for issues specific to Linux and Mac in the Reborn client. If you have a general issue or non-system-specific feature request please go to dev.dota2.com\n\n\t6\t38\t44\nValveSoftware/Dota2-Gameplay\n\nPublic Bug Tracker for Dota 2\n\n\t4\t40\t44\nJustArchiNET/ArchiBot\n\nNo description in the capture.\n\n\t16\t27\t43\nztizzlegaming/CSGOWinBig\n\nOpen-source Counter-Strike: Global Offensive jackpot betting website.\n\n\t1\t40\t41\nJustArchiNET/mantis.justarchi.net\n\nMantis Bug Tracker (MantisBT)\n\n\t40\t0\t40\nodota/node-steam-user\n\nAllows interaction with the Steam network via the Steam client protocol\n\n\t40\t0\t40\nModDota/TypeScriptAddonTemplate\n\nDota 2 addon template with TypeScript Panorama and VScripts.\n\n\t9\t29\t38\nValvePython/vdf\n\n📜 Package for working with Valve's text and binary KeyValue format\n\n\t6\t32\t38\nalliedmodders/amtl\n\nAlliedModders C++ Template Library\n\n\t17\t19\t36\nValvePython/dota2\n\n🐸 Python package for interacting with Dota 2 Game Coordinator\n\n\t5\t30\t35\nalliedmodders/stripper-source\n\nStripper:Source\n\n\t13\t21\t34\nAllyans3/steam-market-api-v2\n\nSteam Market API v2 package\n\n\t3\t31\t34\nModDota/dota-tutorial\n\nCustom game DOTA tutorial.\n\n\t11\t23\t34\nodota/blog\n\nNo description in the capture.\n\n\t29\t3\t32\nOpsecGuy/BetterGo\n\nExternal CS:GO cheat written in python.\n\n\t1\t27\t28\npxvr-official/1\n\n無許諾配信 企業理念剽窃 動物の森収益化 大神ミオ権利者削除 戌神権利侵害発言 常闇トワ炎上 夜空メルストーカー被害 建築王サポーター放置 赤十字マーク 魔乃アロエ卒業 一つの中國支持声明 大空昴3Dライブ 無限延期清掃員職業差別 日清コラボ楽曲 musedash非公開 rog案件取り消し 壁画ライブ 丁真 Ding Zhen 郑爽 Zheng Shuang 防护林 与朵小天使w 伊月猫凛 本主萌埋午休傻 汪峰 重生细胞 壁纸 比利海灵顿 香蕉君 van 田所浩二 抽象带篮子 抗压背锅吧 季子越 蒋明辉 傻逼…\n\n\t0\t28\t28\nRevadike/InternalSteamWebAPI\n\nDocumenting the unofficial and internal Steam Web API\n\n\t1\t27\t28\nJoeSzymkowiczFiveM/qb-lootcrate\n\nA CSGO-style case opening script\n\n\t2\t25\t27\nAbrarKL/MyRoulette.XYZ\n\nCSGO / Steam Roulette Site created with PHP and Node JS, using the Material Design front-end framework.\n\n\t1\t25\t26\nJustArchiNET/ASF-WebConfigGenerator\n\nNo description in the capture.\n\n\t10\t15\t25\nModDota/dota-data\n\nAuto-generated Dota 2 resource dumps\n\n\t11\t14\t25\nModDota/TypeScriptDeclarations\n\nTypeScript declarations for Dota 2.\n\n\t11\t14\t25\nModDota/API\n\nNo description in the capture.\n\n\t12\t12\t24\nalliedmodders/cssdm\n\nCounter-Strike:Source Deathmatch\n\n\t10\t13\t23\nSteamDatabase/steamstat.us\n\n✅ Front-end of Steam services status website\n\n\t4\t18\t22\nc0deina/csgojackpotV2\n\nCSGO Jackpot Source\n\n\t1\t20\t21\nValvePython/steamctl\n\n🤸 Take control of Steam from your terminal\n\n\t2\t19\t21\nValvePython/csgo\n\n🔫 Python package for interacting with CS:GO Game Coordinator\n\n\t3\t17\t20\nBeepIsla/csgo-crash-exploit\n\nAllows you to crash any Windows user\n\n\t3\t16\t19\nValvePython/vpk\n\n📦 Open, Search, Extract and Create VPKs in python\n\n\t4\t15\t19\nalliedmodders/SM-SteamWorks\n\nExposing SteamWorks functions to SourcePawn.\n\n\t14\t3\t17\nSteamRE/Steam4NET\n\nSteam4NET is a .NET wrapper around the Steamworks C++ interfaces\n\n\t2\t15\t17\nalliedmodders/hl2sdk-manifests\n\nInformation about HL2SDKs shared between Metamod:Source and SourceMod.\n\n\t6\t10\t16\nJustArchiNET/ASF-PluginTemplate\n\nTemplate repository that you can use for creating custom plugins for ArchiSteamFarm.\n\n\t8\t7\t15\nModDota/Dota2AIFramework\n\nGeneral Framework for Dota 2 AI Competitions\n\n\t1\t14\t15\nShkyyl/KeyChamp\n\nExtension for joining free case battle on key-drop automatically\n\n\t1\t14\t15\nSteamDatabase/SteamMonitor\n\n😤 Track Steam's connection manager servers status\n\n\t2\t12\t14\nBaterka/cslore.com\n\nCS:GO gambling site - csgo.style\n\n\t1\t12\t13\nSteamDatabase/SteamTokenDumper\n\n🔢 Submit users' PICS access tokens to SteamDB\n\n\t2\t11\t13\nmonoblocker/roulette\n\nRoulette CS:GO made in React and Typescript\n\n\t1\t11\t12\nzsith/launcher.user.js\n\n// ==UserScript== // @name AposLauncher // @namespace AposLauncher // @include http://agar.io/* // @version 3.062 // @grant none // @author http://www.twitch.tv/apostolique // ==/UserScript== var aposLauncherVersion = 3.062; Nu…\n\n\t1\t11\t12\nLincolnIT/CSGODouble-bot-automated\n\nCSGODouble Automated, auto Betting Bot.\n\n\t1\t10\t11\nvladpuz/steam-market\n\nSteam market API client\n\n\t4\t7\t11\nmcgrizzz/Cstrike.bet\n\nCSGO Roulette Website Angular frontend, nodejs backend, and steam trading bots\n\n\t1\t9\t10\nodota/underlords-web\n\nUI for OpenUnderlords\n\n\t5\t5\t10\nSteamDatabase/SteamToTwitter\n\n🕊 Tweets announcements from various Steam groups\n\n\t1\t9\t10\nModDota/AbilityLuaSpellLibrary\n\nThe successor to the Spell Library by Pizzalol\n\n\t4\t4\t8\nalvinl/bitskins\n\nUnofficial BitSkins API client\n\n\t2\t5\t7\nb1naryth1ef/steamy\n\nA Python Steam community and market API interface that will get you all hot and bothered\n\n\t2\t5\t7\nkratos1812/Case-Opening\n\nIn-game case opening system for CSGO servers.\n\n\t2\t5\t7\nodota/docs\n\nOpenDota API documentation\n\n\t4\t3\t7\nSteamDatabase/steam-advanced-access-fetch-players\n\n📈 Simple script to fetch Steam player count\n\n\t1\t6\t7\nTheRioMiner/CsgoBetterExternalRaytrace\n\nOverridden maps pack for better external raytrace\n\n\t1\t6\t7\nalliedmodders/hl2sdk-mock\n\nMock HL2SDK and Server\n\n\t5\t1\t6\nchristophersu/PySteamMarket\n\nPython API for getting prices from the Steam market.\n\n\t1\t5\t6\nExtremelyd1/Strat-Roulette\n\nCS:GO Sourcemod Plugin\n\n\t2\t4\t6\ngiovanni-orciuolo/double-sdk\n\nA simple way to write CS:GO cheats!\n\n\t2\t4\t6\nJustArchiNET/Madness\n\nMadness embraces your project by including compatibility layer for selected APIs normally not available on .NET Framework target.\n\n\t5\t1\t6\nModDota/TypescriptPanoramaDeclarations\n\nNo description in the capture.\n\n\t4\t2\t6\nodota/rapier\n\nA JavaScript Dota 2 (Source 2) replay parsing library\n\n\t1\t5\t6\nVozn1akHero/CSGOCaseOpeningSimulator\n\nCounter-Strike case opening simulator which resembles the good old CS:GO user interface\n\n\t3\t3\t6\nautarc/steam-store\n\nAPI client for the unofficial steam storefront/big picture resource\n\n\t2\t3\t5\nBETTING-CODE/awesome-esports-sites\n\nA curated list of awesome esport betting sites – live, statistics and other resources.\n\n\t1\t4\t5\njonteohr/Better-Warden\n\nAn improved and more advanced warden plugin with a custom menu for CS:GO jailbreak servers!\n\n\t2\t3\t5\nLudzikk/CSGO-Gambling-Site\n\nhttps://ludzikk.github.io/CSGO-Gambling-Site/\n\n\t1\t4\t5\nModDota/find-steam-app\n\nFind location of an installed Steam app\n\n\t3\t2\t5\nmprey/csgocact.us\n\nsource code for csgocact.us\n\n\t1\t4\t5\nnezu-cc/ServerCrasher\n\nCS:GO Server Crasher\n\n\t1\t4\t5\nodota/testfiles\n\nStores test replay files\n\n\t2\t3\t5\nodota/underlordsconstants\n\nConstant data for Dota Underlords\n\n\t3\t2\t5\nSnaBe/node-steam-market-fetcher\n\nA Node.js wrapper for the Steam Community Market API.\n\n\t2\t3\t5\nSteamDatabase/.github\n\n💗 Organization-wide community health files\n\n\t1\t4\t5\nwolfcon/RIP-HLTV-BET\n\nRIP BET AD (For Tampermonkey) https://greasyfork.org/en/scripts/423484-rip-hltv-bet\n\n\t2\t3\t5\nalliedmodders/blaster.net\n\nSource and GoldSrc Query Tool\n\n\t2\t2\t4\ncatears124/CS2-Price-API\n\nsimple python cs2 steam market price API\n\n\t1\t3\t4\nialakey/caseforge\n\nOpen-source CS2 case-opening platform: Steam auth, provably fair openings, RTP-balanced case builder, withdrawals bought on market.csgo.com and an admin CRM.\n\n\t1\t3\t4\nIlusion9/csgo-fix-mapchange-crash-sm\n\nFix players crash on map change.\n\n\t1\t3\t4\nismail0234/Benson-Map-Crash-Fixer\n\nCSGO Map Change Client Crash Fixer\n\n\t1\t3\t4\njaxwilko/steam-market-api\n\nPHP - Composer Compatible - Steam Market API\n\n\t2\t2\t4\nJustArchiNET/ArchiTag\n\nArchiTag is a very small utility based on Python 3 and Mutagen to provide missing functionality in opusenc of writing specific Opus metadata, such as total number of tracks or track number.\n\n\t1\t3\t4\nModDota/DotaUI\n\nNo description in the capture.\n\n\t2\t2\t4\nnode-steam/market-pricing\n\nWrapper for the unofficial Steam Market Pricing API\n\n\t1\t3\t4\nodota/media\n\nStores media files for Dota projects\n\n\t2\t2\t4\nSergeyIvanovDevelop/Crypto-Steam-Platform\n\nThe repository contains the code and configuration to run a platform for creating cryptocurrency stakes for arbitrary ERC20 tokens.\n\n\t1\t3\t4\nAareksio/csgodouble-floatchecker\n\nAdds context menu option to check item's float value\n\n\t1\t2\t3\nchinm4/CSGOdrop\n\nA online csgo gambling casino that includes a variety of mini games that allows you to win csgo skins\n\n\t2\t1\t3\nCruze03/CSGO-Case-Opening-Prank\n\nCommand:- !prank (Admin flag \"n\" required)\n\n\t1\t2\t3\nDhruva-Kapadia/CSGOTrollGG\n\nCSGO Case Opening Simulator\n\n\t2\t1\t3\nErhanCSGO/CSGOPolygon-prediction\n\nCSGOPolygon.com - prediction script, double your coins by using this tool\n\n\t1\t2\t3\nEv-Hoang/Bedrock-Chest-Case-Opening\n\nHypixel Skyblock Dungeon Mod - Bedrock Chest Opening Animation (CSGO Style)\n\n\t1\t2\t3\njmjp/csgo-roulette\n\nA csgo gambling roulette make with VueJS 3\n\n\t2\t1\t3\nJustArchiNET/ArchiCrowdin\n\nNo description in the capture.\n\n\t1\t2\t3\nLeonSK/WearMarketInspector\n\nRetrieve Wear Value (Float Value) and Pattern Index from Steam Community Market using http://csgo.exchange API\n\n\t1\t2\t3\nmaximgeerinck/csgo-gamble\n\nCSGO gambling website\n\n\t1\t2\t3\nModDota/BugTracker\n\nListing bugs for Dota 2 Custom Games\n\n\t2\t1\t3\nplwp/mma-betting\n\nUFC/MMA betting model with Pinnacle steam detection for AU book latency arb\n\n\t2\t1\t3\nSouthsideswag16/Csgo-Gambling-Site\n\nNo description in the capture.\n\n\t2\t1\t3\ntacyarg/csgofiesta-frontend-react\n\nRemastered version a the long time favorite csgo site\n\n\t2\t1\t3\nVelorasse/Mutah-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-csmoney-csgoskins\n\ngambling script for Mutah, Keydrop, csmoney, and csgoskins, featuring hacks, cheats, and predictors. Offers strategies to boost winning odds and optimize performance on these platforms.\n\n\t3\t0\t3\nalliedmodders/am-github-artifact-webhook\n\nNo description in the capture.\n\n\t2\t0\t2\ncharamza/roulette\n\nCSGO like roulette in JS\n\n\t1\t1\t2\nCruze03/CSGO-PugSetup-RoundRestore\n\nSometimes (player dropped/crashed) which would be disadvantage for a team. It would be very handy to restore the match to the previous round.\n\n\t1\t1\t2\ncsgorol/CSGO-ROLL-Crash-Predictor\n\nCSGO-ROLL-Crash-Predictor\n\n\t1\t1\t2\nFoxSerito/FOXWORLD_plugin_DoubleJump_CSGO\n\nПлагин SourceMod (CSGO). Двойной прыжок с эффектом.\n\n\t1\t1\t2\nhkehayovmoonbiz/CS2-Casino-Full-Source-Code\n\nCS2, CS2 betting platforms, Skin Roulette, Case Unboxing, Crash games, Jackpot, purchase CS2 casino source, crypto gambling\n\n\t1\t1\t2\nJustZakary/steamstoreapi\n\nThis NPM module is a API wrapper that makes the steam unofficial API easier to use.\n\n\t2\t0\t2\njzimr/steam-market-api\n\nA java library to easily get Steam Community Market data\n\n\t1\t1\t2\nMomohime/CSGO.Network-Jackpot-Coinflip\n\nNo description in the capture.\n\n\t1\t1\t2\nnnjjswat/moneybot\n\nautomated bots for bustabit (formerly known as moneypot), csgo crash, etc\n\n\t0\t2\t2\nodota/carry\n\nLegacy Application for donations to the OpenDota project\n\n\t1\t1\t2\nodota/PublicMatchDataBot\n\nA Discord bot to remind users to turn on Expose Public Match Data in the Dota 2 client\n\n\t1\t1\t2\nOrillio/CSGOBet.com\n\nCSGO roulette web app\n\n\t2\t0\t2\nripexz/csgo-bet-alert\n\nA Chrome extension to keep track of active CS:GO Lounge matches.\n\n\t1\t1\t2\nrrpvm/lumen_sense-beta-deprecated-\n\nthis is internal csgo cheat written by me(no paste, self reverse structures). start : ~6 August 2020, end : ~ 14 December 2020\n\n\t1\t1\t2\nRuthless222/csgoscore\n\nThis is a Counter Strike Global Offensive Betting Site. You chose the skins you want to bet and try to win jackpots\n\n\t2\t0\t2\ntfburns/CSGO-cases-PL\n\nExpected profit-loss of CS:GO case openings\n\n\t1\t1\t2\nTomDra/CSGO-Case-Data-Analysis\n\nWorks out the most profitable CS:GO case at that current time\n\n\t1\t1\t2\nValvePython/dota2-wrappers\n\nNo description in the capture.\n\n\t1\t1\t2\nValvePython/teamfortress2-closed-captions\n\nThis project aims to provide a set of closed captions for Team Fortress 2\n\n\t1\t1\t2\nVistaNetGTX/Cstrike.bet-\n\nCSGO Roulette Website Angular frontend, nodejs backend, and steam trading bots\n\n\t1\t1\t2\nwafflas/csgo-case-opening-simulator\n\nI created a cs go case opening simulator for a meme coin\n\n\t0\t2\t2\nAdmiral-Enigma/Le_Coinflip\n\nConflip game\n\n\t1\t0\t1\nadryeljuliao/roulette-csgo\n\nNo description in the capture.\n\n\t1\t0\t1\nAndreuTheG/csgo-coinflip-web\n\nCSGO Gambling Coinflip Website\n\n\t1\t0\t1\nasmilen/csgoDouble\n\na b c\n\n\t1\t0\t1\nb1naryth1ef/csgofort\n\nA CSGO portal for trading, betting, analytics, and more!\n\n\t1\t0\t1\nBaterka/PrivateSteamBettingWebsite2024\n\nPrivate Steam (Counter-Strike 2) betting/gambling website - Roulette, Jackpot\n\n\t1\t0\t1\nblackcaer/SteamTradeHandler\n\nAutomation of Steam trading. Helper project for bet automation.\n\n\t1\t0\t1\nBTheCoderr/theRounders\n\nThe Rounders - A professional-grade sports betting analytics platform combining real-time odds tracking, sharp movement detection, and advanced statistical analysis. Features include line shopping, steam move alerts, power rankings, and comprehensive bet t…\n\n\t1\t0\t1\nCallumHemsley/KazeBot\n\nA Twitch chat betting bot for CSGO, simply bet a certain amount of points, and double if you win, lose all if you lose. Simple.\n\n\t1\t0\t1\nchrisjpm/CSGOJackpotTemplate\n\nFront end for a jackpot site\n\n\t1\t0\t1\ncolinsenner/valve-bug-bounty\n\nFor many years CS:GO, Dota 2, and Team Fortress 2 servers had a bug that allowed malicious users to leak crucial server process memory or reliably crash any server.\n\n\t1\t0\t1\ncoryypeters/nrl-odds-intelligence-pipeline\n\nReal-time sports betting odds intelligence — streaming pipeline that detects line movement, steam, and arbitrage across bookmakers. Python · Redis Streams · FastAPI · React.\n\n\t1\t0\t1\ndeissh/dev-csgoduo\n\nCS:GO. Bot for receiving things on the site (Polygon, Duo, Double and etc).\n\n\t1\t0\t1\ndom1torii/even-better-font-manager\n\nSimply even better cross-platform tool for CS2 Font Management\n\n\t1\t0\t1\nDONnicov/CSGO-crash-black-screen-\n\nsolution csgo crash black screen and close csgo\n\n\t1\t0\t1\nDoubleBoters/CsgoDouble\n\nNo description in the capture.\n\n\t1\t0\t1\ndownarowiczd/DoubleBot\n\nAn old CSGO Double Bot written for my friend. - 07.05.2016\n\n\t1\t0\t1\nErayBahar/steammarketscraper\n\nSteam Market Scraper Python-based tool that tracks real-time CS2 skin prices using Steam's hidden API. It fetches the lowest sell and highest buy offers for any item, helping you monitor deals or snipe underpriced listings automatically.\n\n\t1\t0\t1\nfairydarkness/SteamwebmailAPI\n\nUnofficial Python API for steamwebmail.com Fast, lightweight, and browserless library for automating steamwebmail.com. Support for session management, proxy, folder navigation, and message retrieval\n\n\t1\t0\t1\nFAQU2/CSGO-Coinflip-MyJailShop\n\nSourcemod plugin which provides a Coinflip system for MyJailShop.\n\n\t1\t0\t1\nFlamesONE/csgo-case-opening\n\nNo description in the capture.\n\n\t1\t0\t1\nFunnyRain/csgorun-crash-watch\n\n🚀 CsgoRun dump crash. / 🚀 CsgoRun дамп крашей.\n\n\t1\t0\t1\ngeohdgio/Venatus-Autenticator\n\nეს არის Steam Autenticator ქართული Venatus Trade & Betting ისთვის და Valve News Georgia-სთვის.\n\n\t1\t0\t1\nhakanstarlord/steam-bot\n\nSports betting steam-move signal detection with ML pipeline (XGBoost stacking + isotonic calibration), backtesting engine, Flask dashboard, and Telegram alerts.\n\n\t1\t0\t1\nHvH-gg/CSGO-Item-CrashFix\n\nA plugin for Counter-Strike: Global Offensive that fixes an exploit where receiving CS2 Items will cause CS:GO clients to crash\n\n\t1\t0\t1\nHvH-gg/CSGO-NetMsg-CrashFix\n\nA plugin for Counter-Strike: Global Offensive that fixes an exploit where spamming NetMsg_StringCmd packets would result in a server crash.\n\n\t1\t0\t1\nisybycnsmam/SteamLibrary\n\nLegacy Steam Unofficial API\n\n\t1\t0\t1\nItsTangerine/SteamApis.Net\n\nUnofficial https://steamapis.com .NET library, supporting .NET 6.0+\n\n\t1\t0\t1\nJustArchiNET/JustArchi.net\n\nNo description in the capture.\n\n\t1\t0\t1\nkiri-osint/CS2-Info-Hub-Bot\n\nA Telegram bot that acts as a hub for CS2 players, providing real-time skin prices, server stats, and user profile/inventory inspection using official and unofficial Steam APIs.\n\n\t1\t0\t1\nKoshkaj/monte\n\nGamified csgo gambling platform implementation\n\n\t1\t0\t1\nmadsab/CaseOpening\n\nA school project using Java. Simulating the case opening from CSGO and more.\n\n\t1\t0\t1\nman90es/steamcardexchange-api\n\nSteamCardExchange.net unofficial REST API server (scraper).\n\n\t1\t0\t1\nMattPua/steam-unofficial-docs\n\nUnofficial docs for Steam APIs with fumadocs\n\n\t1\t0\t1\nMetallist1/Portfolio.CsgoWinGambleProject\n\nA website that was done in 2017 September. Websites focus was on gambling with Counter-Strike items. Project was largely completed however backups were not done correctly, this resulted in half a year of wasted improvements to the code. The website was test…\n\n\t1\t0\t1\nmikebobadilla/csgo-jackpot\n\nNo description in the capture.\n\n\t0\t1\t1\nmikebobadilla/meteor-csgojackpot\n\nCssgo Jackpot done in meteor\n\n\t1\t0\t1\nModDota/D2VDump\n\nDota 2 Server VScript API Dumper\n\n\t1\t0\t1\nModDota/DotaTracking\n\nNo description in the capture.\n\n\t1\t0\t1\nModDota/eslint-config\n\nESLint config by ark120202\n\n\t1\t0\t1\nmr-codinglv/Casino-script\n\nscript casino - script betting - exchange script - bc casino - casino csgo - script bet - betwin script\n\n\t1\t0\t1\nMrKeelik/MrKeel\n\nCSGO DOUBLE BOT\n\n\t1\t0\t1\nnoahlatzel/CSGORollHelper\n\nLeveraging positive expected value on triple green jackpots on CSGORoll!\n\n\t1\t0\t1\noddsgpt/oddsgpt-market-intelligence\n\nResearch on football betting markets, closing odds, CLV, market efficiency, steam moves, AI betting systems, and sports market intelligence.\n\n\t1\t0\t1\noEXU/csgo-server-crasher\n\nCSGO SERVER CRASHER\n\n\t1\t0\t1\nPrdTTony/CSGO-Roulette\n\n[CSGO] Roulette System. Bet on RED or Black and win x2 credits\n\n\t1\t0\t1\nr-adamski/csgo-jackpot\n\nNo description in the capture.\n\n\t1\t0\t1\nSahotallo/Turan-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-Skinbaron-hellcase\n\ngambling script for Turan, Keydrop, Skinbaron, and Hellcase, providing hacks, cheats, and predictors. Includes strategies to improve winning chances and enhance gameplay on these platforms.\n\n\t1\t0\t1\nsamuelcsouza/steam-marketplace-api\n\nAn unofficial API to get data from the Steam Marketplace.\n\n\t1\t0\t1\nSKINSTRACK/CS2-Price-API\n\nSkinstrack offers a free, limited API endpoint that returns Steam item prices. Paid plans additionally provide access to pricing data from multiple marketplaces, making it possible to compare prices across different markets through a single API.\n\n\t1\t0\t1\nsnmtriet/CSGO-Casino-Full-Source-Code\n\nCSGO, CSGOEmpire, Case Opening, Case Battles, Roulette, Coinflip, buy csgo gambling site, gambling\n\n\t1\t0\t1\nSteamRE/homebrew-tools\n\nRepository for installation of SteamRE tools via Homebrew (http://brew.sh)\n\n\t1\t0\t1\nSteamRE/opensteamworks.org\n\nNo description in the capture.\n\n\t1\t0\t1\nTheQuack45/CsgoCaseOpenProgram\n\nSimple program to parse an XML file with CS:GO case information and \"simulate\" case openings\n\n\t1\t0\t1\nTLClassless/StratRouletteCSGO\n\nA 'Strat Roulette' web app for CS:GO!\n\n\t1\t0\t1\ntomasoom/csgoCaseOpening\n\nNo description in the capture.\n\n\t1\t0\t1\nvitaliy-evsyukov/steamgifts-autobet-bookmarklet\n\nbookmarklet for automatic bets on steamgifts.com\n\n\t1\t0\t1\nXpravdaX/RouletteCSGO\n\nNo description in the capture.\n\n\t1\t0\t1\nYuiKasumii/steam_api_unofficial\n\nUnofficial Steam Game Information Database\n\n\t1\t0\t1\nZexuz/Steam-Betting\n\nA betting website build ontop of STEAM's ecosystem\n\n\t1\t0\t1\nANK-RULZZ/steam-jackpot-site\n\ngetting some errors and would like some one to help me with it thank you!!!\n\n\t0\t0\t0\nasmilen/CsgoDoubleVS\n\nNo description in the capture.\n\n\t0\t0\t0\nCORNOODOSADAS/CSGOWeed\n\nCsgo Jackpot and Coinflip\n\n\t0\t0\t0\nCSGOApple/csgoapple\n\nJackpot Site\n\n\t0\t0\t0\nCSGOFAST/csgofast-api\n\nNo description in the capture.\n\n\t0\t0\t0\nDonakall/csgoDoublebot\n\nAutomated bot for csgodouble\n\n\t0\t0\t0\nfedor-selivanov/csgo-fast-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nfoldageros/csgod\n\ndouble bot\n\n\t0\t0\t0\ngmod-gambling/gmod-gambling\n\nNo description in the capture.\n\n\t0\t0\t0\nierome/CSGOBoss-BackEnd\n\nBack end version of CSGOBoss. This was a CSGO Gambling site named CSGOBoss. Coded by an old friend of mine Dahquan Hinds (https://github.com/dahquan/) Thought I would release this to help out any one who would need it.\n\n\t0\t0\t0\njamienp1/CSGODOUBLE-BOT-AUTO\n\ni got a bot thats is betting on the last winning color except from green and if you lose it will double the coins you set it to bet, pretty good, so when there comes a loooong train you will be gaining a bit of money codepaste_net/ugmt92 remove all the _ an…\n\n\t0\t0\t0\nJEYONER/CSGOTOXIC\n\nPAGINA DE JACKPOT CSGO SKINS\n\n\t0\t0\t0\nkalrish/csgo-jackpot\n\nStressful but funny zombie-like Counter-Strike: Global Offensive game mode.\n\n\t0\t0\t0\nkrys12345/roulettee\n\n// ==UserScript== // @name CSGO Predict Bot // @namespace http://csgodouble.com // @version 1.0 // @description predicts what number its gonna be // @author Meee // @match http://www.csgodouble.com/ // @grant none // ==/…\n\n\t0\t0\t0\nLilDuggiMuffi/CSGODouble-Working-Bot\n\nFixed CSGO Double Bot\n\n\t0\t0\t0\nLyricLy/Steam2Proton\n\nCheck if all your Steam games will work with Proton! Uses the official Steam API and the unofficial Proton API.\n\n\t0\t0\t0\nM0NsTeR77/csgo-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nozanhalis/Hi\n\n// ==UserScript== // @name CS GO LOUNGE BOT-Ozan Halis // @namespace http://csgolounge.com/ // @version 0.6.6 // @description Cs Go Lounge Hızlı BOT // @match http://csgolounge.com/* // @match http://dota2lounge.com/* // @updateURL h…\n\n\t0\t0\t0\nscoobertus/CSGO-DoubleBot\n\nNo description in the capture.\n\n\t0\t0\t0\nTradeal/CSGO-Jackpot-Bot\n\nNo description in the capture.\n\n\t0\t0\t0\nValvePython/artifact\n\nNo description in the capture.\n\n\t0\t0\t0\nVampire/CSGO-Roulette-Bot\n\nNo description in the capture.\n\n\t0\t0\t0\nvdemans/csgo-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nVocoreVideo/CSGODungeon-\n\nCSGO Jackpot\n\n\t0\t0\t0\nwayz-dev/csgofloat\n\nNo description in the capture.\n\n\t0\t0\t0\n\nPanoramica: 17 settembre 2026, 11:19:11 come riportato nella fonte; fuso orario non specificato. La raccolta delle relazioni è limitata nell’esportazione (molte categorie si fermano a 40). I contributori e i forker totalizzano 4,554 voci di ruolo distribuite su 4,214 coppie distinte di profilo-repository; un profilo può ricoprire entrambi i ruoli. Il valore zero indica che non sono stati rilevati record in quella categoria. I nomi dei repository possono includere alias o varianti di maiuscolo/minuscolo; i totali rispettano le convenzioni di conteggio della fonte.\n\nProvenienza della fonte\nCreato a partire dai file che hai raccolto.\nTestimonianza a sostegno\n2323/reddit_scams_ultra/steam_support_tickets_MEGA.json · righe 45, 58, 107, 110, 294\nPanoramica della rete\nnetwork-repositories.csv · raw_data.json · overlaps.csv · summary.txt (i percorsi delle fonti storiche sono stati mantenuti nel manifesto)\n\nIl manifesto riporta i percorsi delle fonti, le dimensioni in byte, gli hash SHA-256e e le posizioni dei record selezionati. Le acquisizioni grezze rimangono separate dall'interpretazione dell'indagine.\n\nScarica il manifesto sorgente ↓",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam Prove relative all'applicazione delle norme — Documentazione di supporto e rete degli sviluppatori"
          },
          {
            "level": 2,
            "id": null,
            "text": "Leggi la denuncia.Allega il file sorgente."
          },
          {
            "level": 3,
            "id": null,
            "text": "Permanent sanction & closed appeals"
          },
          {
            "level": 4,
            "id": null,
            "text": "Permanently banned Steam account without a clear explanation, need help!"
          },
          {
            "level": 3,
            "id": null,
            "text": "Account recovery & a reported $10,000 loss"
          },
          {
            "level": 4,
            "id": null,
            "text": "Got $10k stollen from steam inventory due to steam' support fault."
          },
          {
            "level": 3,
            "id": null,
            "text": "A reported $500+ loss & template replies"
          },
          {
            "level": 4,
            "id": null,
            "text": "Funds stolen through steam market. Disappointed with Steam response.(or lackthereof)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam Guard & an item-restoration refusal"
          },
          {
            "level": 4,
            "id": null,
            "text": "Many people are losing item via clicking links where steam guard is enabled and steam support doesn't not restore items."
          },
          {
            "level": 3,
            "id": null,
            "text": "Selective enforcement & an unexplained ban"
          },
          {
            "level": 4,
            "id": null,
            "text": "🚨 Steam Bans Without Reason and Ignores Its Community — What’s Going On?"
          },
          {
            "level": 2,
            "id": null,
            "text": "Infrastrutture pubbliche.Registrato su larga scala."
          },
          {
            "level": 2,
            "id": null,
            "text": "Creato a partire dai file che hai raccolto."
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/it/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/it/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/selected-support-records.json",
          "https://phishdestroy.io/steam_dossier/it/investigation_part2.html#outsourcing-case",
          "https://www.reddit.com/r/ohnePixel/comments/1hahqx2/permanently_banned_steam_account_without_a_clear/",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://www.reddit.com/r/DotA2/comments/r55bd7/many_people_are_losing_item_via_clicking_links/",
          "https://www.reddit.com/r/SteamUncensored/comments/1kjt2fa/steam_bans_without_reason_and_ignores_its/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/network-repositories.csv",
          "https://github.com/alliedmodders/amxmodx",
          "https://github.com/alliedmodders/sourcemod",
          "https://github.com/DoctorMcKay/node-steam-user",
          "https://github.com/Facepunch/Facepunch.Steamworks",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://github.com/odota/core",
          "https://github.com/odota/dotaconstants",
          "https://github.com/odota/web",
          "https://github.com/splewis/get5",
          "https://github.com/SteamDatabase/FileDetectionRuleSets",
          "https://github.com/SteamRE/SteamKit",
          "https://github.com/ValveSoftware/dxvk",
          "https://github.com/ValveSoftware/GameNetworkingSockets",
          "https://github.com/ValveSoftware/gamescope",
          "https://github.com/ValveSoftware/Proton",
          "https://github.com/ValveSoftware/source-sdk-2013",
          "https://github.com/ValveSoftware/wine",
          "https://github.com/ValveSoftware/steam-devices",
          "https://github.com/ValveSoftware/steam-audio",
          "https://github.com/alliedmodders/metamod-source",
          "https://github.com/alliedmodders/sourcepawn",
          "https://github.com/ValveSoftware/Fossilize",
          "https://github.com/rlabrecque/Steamworks.NET",
          "https://github.com/ModDota/moddota.github.io",
          "https://github.com/odota/parser",
          "https://github.com/ValveSoftware/steam-for-linux",
          "https://github.com/SteamRE/DepotDownloader",
          "https://github.com/JustArchiNET/ASF-ui",
          "https://github.com/advancedfx/advancedfx",
          "https://github.com/alliedmodders/ambuild",
          "https://github.com/SteamDatabase/BrowserExtension",
          "https://github.com/odota/mobile",
          "https://github.com/ValvePython/steam",
          "https://github.com/skadistats/clarity",
          "https://github.com/SteamRE/open-steamworks",
          "https://github.com/ValveSoftware/Source-1-Games",
          "https://github.com/alliedmodders/hl2sdk",
          "https://github.com/SteamDatabase/steamdb.info-issues",
          "https://github.com/CSGOFloat/inspect",
          "https://github.com/ValveSoftware/SteamOS",
          "https://github.com/alliedmodders/source2mod",
          "https://github.com/smiley/steamapi",
          "https://github.com/SteamDatabase/GameTracking",
          "https://github.com/ValveSoftware/counter-strike_rules_and_regs",
          "https://github.com/ValveSoftware/openvr",
          "https://github.com/SteamDatabase/easy-markdown-editor",
          "https://github.com/ValveSoftware/Dota-2",
          "https://github.com/ValveSoftware/Dota2-Gameplay",
          "https://github.com/JustArchiNET/ArchiBot",
          "https://github.com/ztizzlegaming/CSGOWinBig",
          "https://github.com/JustArchiNET/mantis.justarchi.net",
          "https://github.com/odota/node-steam-user",
          "https://github.com/ModDota/TypeScriptAddonTemplate",
          "https://github.com/ValvePython/vdf",
          "https://github.com/alliedmodders/amtl",
          "https://github.com/ValvePython/dota2",
          "https://github.com/alliedmodders/stripper-source",
          "https://github.com/Allyans3/steam-market-api-v2",
          "https://github.com/ModDota/dota-tutorial",
          "https://github.com/odota/blog",
          "https://github.com/OpsecGuy/BetterGo",
          "https://github.com/pxvr-official/1",
          "https://github.com/Revadike/InternalSteamWebAPI",
          "https://github.com/JoeSzymkowiczFiveM/qb-lootcrate",
          "https://github.com/AbrarKL/MyRoulette.XYZ",
          "https://github.com/JustArchiNET/ASF-WebConfigGenerator",
          "https://github.com/ModDota/dota-data",
          "https://github.com/ModDota/TypeScriptDeclarations",
          "https://github.com/ModDota/API",
          "https://github.com/alliedmodders/cssdm",
          "https://github.com/SteamDatabase/steamstat.us",
          "https://github.com/c0deina/csgojackpotV2",
          "https://github.com/ValvePython/steamctl",
          "https://github.com/ValvePython/csgo",
          "https://github.com/BeepIsla/csgo-crash-exploit",
          "https://github.com/ValvePython/vpk",
          "https://github.com/alliedmodders/SM-SteamWorks",
          "https://github.com/SteamRE/Steam4NET",
          "https://github.com/alliedmodders/hl2sdk-manifests",
          "https://github.com/JustArchiNET/ASF-PluginTemplate",
          "https://github.com/ModDota/Dota2AIFramework",
          "https://github.com/Shkyyl/KeyChamp",
          "https://github.com/SteamDatabase/SteamMonitor",
          "https://github.com/Baterka/cslore.com",
          "https://github.com/SteamDatabase/SteamTokenDumper",
          "https://github.com/monoblocker/roulette",
          "https://github.com/zsith/launcher.user.js",
          "https://github.com/LincolnIT/CSGODouble-bot-automated",
          "https://github.com/vladpuz/steam-market",
          "https://github.com/mcgrizzz/Cstrike.bet",
          "https://github.com/odota/underlords-web",
          "https://github.com/SteamDatabase/SteamToTwitter",
          "https://github.com/ModDota/AbilityLuaSpellLibrary",
          "https://github.com/alvinl/bitskins",
          "https://github.com/b1naryth1ef/steamy",
          "https://github.com/kratos1812/Case-Opening",
          "https://github.com/odota/docs",
          "https://github.com/SteamDatabase/steam-advanced-access-fetch-players",
          "https://github.com/TheRioMiner/CsgoBetterExternalRaytrace",
          "https://github.com/alliedmodders/hl2sdk-mock",
          "https://github.com/christophersu/PySteamMarket",
          "https://github.com/Extremelyd1/Strat-Roulette",
          "https://github.com/giovanni-orciuolo/double-sdk",
          "https://github.com/JustArchiNET/Madness",
          "https://github.com/ModDota/TypescriptPanoramaDeclarations",
          "https://github.com/odota/rapier",
          "https://github.com/Vozn1akHero/CSGOCaseOpeningSimulator",
          "https://github.com/autarc/steam-store",
          "https://github.com/BETTING-CODE/awesome-esports-sites",
          "https://github.com/jonteohr/Better-Warden",
          "https://github.com/Ludzikk/CSGO-Gambling-Site",
          "https://github.com/ModDota/find-steam-app",
          "https://github.com/mprey/csgocact.us",
          "https://github.com/nezu-cc/ServerCrasher",
          "https://github.com/odota/testfiles",
          "https://github.com/odota/underlordsconstants",
          "https://github.com/SnaBe/node-steam-market-fetcher",
          "https://github.com/SteamDatabase/.github",
          "https://github.com/wolfcon/RIP-HLTV-BET",
          "https://github.com/alliedmodders/blaster.net",
          "https://github.com/catears124/CS2-Price-API",
          "https://github.com/ialakey/caseforge",
          "https://github.com/Ilusion9/csgo-fix-mapchange-crash-sm",
          "https://github.com/ismail0234/Benson-Map-Crash-Fixer",
          "https://github.com/jaxwilko/steam-market-api",
          "https://github.com/JustArchiNET/ArchiTag",
          "https://github.com/ModDota/DotaUI",
          "https://github.com/node-steam/market-pricing",
          "https://github.com/odota/media",
          "https://github.com/SergeyIvanovDevelop/Crypto-Steam-Platform",
          "https://github.com/Aareksio/csgodouble-floatchecker",
          "https://github.com/chinm4/CSGOdrop",
          "https://github.com/Cruze03/CSGO-Case-Opening-Prank",
          "https://github.com/Dhruva-Kapadia/CSGOTrollGG",
          "https://github.com/ErhanCSGO/CSGOPolygon-prediction",
          "https://github.com/Ev-Hoang/Bedrock-Chest-Case-Opening",
          "https://github.com/jmjp/csgo-roulette",
          "https://github.com/JustArchiNET/ArchiCrowdin",
          "https://github.com/LeonSK/WearMarketInspector",
          "https://github.com/maximgeerinck/csgo-gamble",
          "https://github.com/ModDota/BugTracker",
          "https://github.com/plwp/mma-betting",
          "https://github.com/Southsideswag16/Csgo-Gambling-Site",
          "https://github.com/tacyarg/csgofiesta-frontend-react",
          "https://github.com/Velorasse/Mutah-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-csmoney-csgoskins",
          "https://github.com/alliedmodders/am-github-artifact-webhook",
          "https://github.com/charamza/roulette",
          "https://github.com/Cruze03/CSGO-PugSetup-RoundRestore",
          "https://github.com/csgorol/CSGO-ROLL-Crash-Predictor",
          "https://github.com/FoxSerito/FOXWORLD_plugin_DoubleJump_CSGO",
          "https://github.com/hkehayovmoonbiz/CS2-Casino-Full-Source-Code",
          "https://github.com/JustZakary/steamstoreapi",
          "https://github.com/jzimr/steam-market-api",
          "https://github.com/Momohime/CSGO.Network-Jackpot-Coinflip",
          "https://github.com/nnjjswat/moneybot",
          "https://github.com/odota/carry",
          "https://github.com/odota/PublicMatchDataBot",
          "https://github.com/Orillio/CSGOBet.com",
          "https://github.com/ripexz/csgo-bet-alert",
          "https://github.com/rrpvm/lumen_sense-beta-deprecated-",
          "https://github.com/Ruthless222/csgoscore",
          "https://github.com/tfburns/CSGO-cases-PL",
          "https://github.com/TomDra/CSGO-Case-Data-Analysis",
          "https://github.com/ValvePython/dota2-wrappers",
          "https://github.com/ValvePython/teamfortress2-closed-captions",
          "https://github.com/VistaNetGTX/Cstrike.bet-",
          "https://github.com/wafflas/csgo-case-opening-simulator",
          "https://github.com/Admiral-Enigma/Le_Coinflip",
          "https://github.com/adryeljuliao/roulette-csgo",
          "https://github.com/AndreuTheG/csgo-coinflip-web",
          "https://github.com/asmilen/csgoDouble",
          "https://github.com/b1naryth1ef/csgofort",
          "https://github.com/Baterka/PrivateSteamBettingWebsite2024",
          "https://github.com/blackcaer/SteamTradeHandler",
          "https://github.com/BTheCoderr/theRounders",
          "https://github.com/CallumHemsley/KazeBot",
          "https://github.com/chrisjpm/CSGOJackpotTemplate",
          "https://github.com/colinsenner/valve-bug-bounty",
          "https://github.com/coryypeters/nrl-odds-intelligence-pipeline",
          "https://github.com/deissh/dev-csgoduo",
          "https://github.com/dom1torii/even-better-font-manager",
          "https://github.com/DONnicov/CSGO-crash-black-screen-",
          "https://github.com/DoubleBoters/CsgoDouble",
          "https://github.com/downarowiczd/DoubleBot",
          "https://github.com/ErayBahar/steammarketscraper",
          "https://github.com/fairydarkness/SteamwebmailAPI",
          "https://github.com/FAQU2/CSGO-Coinflip-MyJailShop",
          "https://github.com/FlamesONE/csgo-case-opening",
          "https://github.com/FunnyRain/csgorun-crash-watch",
          "https://github.com/geohdgio/Venatus-Autenticator",
          "https://github.com/hakanstarlord/steam-bot",
          "https://github.com/HvH-gg/CSGO-Item-CrashFix",
          "https://github.com/HvH-gg/CSGO-NetMsg-CrashFix",
          "https://github.com/isybycnsmam/SteamLibrary",
          "https://github.com/ItsTangerine/SteamApis.Net",
          "https://github.com/JustArchiNET/JustArchi.net",
          "https://github.com/kiri-osint/CS2-Info-Hub-Bot",
          "https://github.com/Koshkaj/monte",
          "https://github.com/madsab/CaseOpening",
          "https://github.com/man90es/steamcardexchange-api",
          "https://github.com/MattPua/steam-unofficial-docs",
          "https://github.com/Metallist1/Portfolio.CsgoWinGambleProject",
          "https://github.com/mikebobadilla/csgo-jackpot",
          "https://github.com/mikebobadilla/meteor-csgojackpot",
          "https://github.com/ModDota/D2VDump",
          "https://github.com/ModDota/DotaTracking",
          "https://github.com/ModDota/eslint-config",
          "https://github.com/mr-codinglv/Casino-script",
          "https://github.com/MrKeelik/MrKeel",
          "https://github.com/noahlatzel/CSGORollHelper",
          "https://github.com/oddsgpt/oddsgpt-market-intelligence",
          "https://github.com/oEXU/csgo-server-crasher",
          "https://github.com/PrdTTony/CSGO-Roulette",
          "https://github.com/r-adamski/csgo-jackpot",
          "https://github.com/Sahotallo/Turan-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-Skinbaron-hellcase",
          "https://github.com/samuelcsouza/steam-marketplace-api",
          "https://github.com/SKINSTRACK/CS2-Price-API",
          "https://github.com/snmtriet/CSGO-Casino-Full-Source-Code",
          "https://github.com/SteamRE/homebrew-tools",
          "https://github.com/SteamRE/opensteamworks.org",
          "https://github.com/TheQuack45/CsgoCaseOpenProgram",
          "https://github.com/TLClassless/StratRouletteCSGO",
          "https://github.com/tomasoom/csgoCaseOpening",
          "https://github.com/vitaliy-evsyukov/steamgifts-autobet-bookmarklet",
          "https://github.com/XpravdaX/RouletteCSGO",
          "https://github.com/YuiKasumii/steam_api_unofficial",
          "https://github.com/Zexuz/Steam-Betting",
          "https://github.com/ANK-RULZZ/steam-jackpot-site",
          "https://github.com/asmilen/CsgoDoubleVS",
          "https://github.com/CORNOODOSADAS/CSGOWeed",
          "https://github.com/CSGOApple/csgoapple",
          "https://github.com/CSGOFAST/csgofast-api",
          "https://github.com/Donakall/csgoDoublebot",
          "https://github.com/fedor-selivanov/csgo-fast-roulette",
          "https://github.com/foldageros/csgod",
          "https://github.com/gmod-gambling/gmod-gambling",
          "https://github.com/ierome/CSGOBoss-BackEnd",
          "https://github.com/jamienp1/CSGODOUBLE-BOT-AUTO",
          "https://github.com/JEYONER/CSGOTOXIC",
          "https://github.com/kalrish/csgo-jackpot",
          "https://github.com/krys12345/roulettee",
          "https://github.com/LilDuggiMuffi/CSGODouble-Working-Bot",
          "https://github.com/LyricLy/Steam2Proton",
          "https://github.com/M0NsTeR77/csgo-roulette",
          "https://github.com/ozanhalis/Hi",
          "https://github.com/scoobertus/CSGO-DoubleBot",
          "https://github.com/Tradeal/CSGO-Jackpot-Bot",
          "https://github.com/ValvePython/artifact",
          "https://github.com/Vampire/CSGO-Roulette-Bot",
          "https://github.com/vdemans/csgo-roulette",
          "https://github.com/VocoreVideo/CSGODungeon-",
          "https://github.com/wayz-dev/csgofloat",
          "https://phishdestroy.io/steam_dossier/output_steam_network/raw_data.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/enforcement-source-manifest.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/it/steam_enforcement_evidence.content.json",
      "export_json_sha256": "1a41573b9327a654b0bba9696d7b89faeb967ec4607efa2887c04b658323c7d4"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "it/steam_evidence_archive.html",
      "language": "it",
      "title": "Esamina le fonti — Il dossier “Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/it/steam_evidence_archive",
      "source_html_sha256": "9deba68b7a1598c0f2c8510a67650cc548792e34b4f48438da4c929ae316f91c",
      "exported_at": "2026-09-29T00:17:59.482Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "steam_evidence_archive.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/it/steam_evidence_archive.pdf?v=print-20260929-v5",
        "sha256": "febda49b786e38edfdc08e29f4154bf23458c45fcd4e747c701e8f0b50b90e19",
        "bytes": 62186,
        "pages": 4
      },
      "integrity": {
        "signed_object": "steam_evidence_archive.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "steam_evidence_archive.content.json.asc",
        "digest_file": "steam_evidence_archive.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify steam_evidence_archive.content.json.asc steam_evidence_archive.content.json",
          "sha256sum -c steam_evidence_archive.content.json.sha256"
        ]
      },
      "content": {
        "text": "MATERIALI DELLE INDAGINI / RACCOLTA DELLE FONTI 002\nSteam Archivio delle prove — 16,319 Documenti di provenienza certa\n\nOgni richiesta di risarcimento. Ritorno alle origini.\n\nCOSA DIMOSTRA QUESTA SEZIONE\n\nQuesto archivio forense indicizza 16,319 documenti di fonte primaria — che comprendono la documentazione della comunità di sviluppatori Valve, segnalazioni pubbliche su GitHub, reclami verificati su Trustpilot e segnalazioni archiviate nei forum — con hash crittografici e registri di provenienza. Fornisce una base probatoria verificabile che dimostra vulnerabilità ripetibili della piattaforma, deprecazioni non documentate su API e reclami persistenti da parte dei consumatori relativi ad account compromessi.\n\n← Torna al briefing esecutivo\n\nTrova il record corrispondente a una segnalazione. Filtra per fonte, apri il testo completo e segui il link originale. Le righe relative alle fonti possono sovrapporsi; un record non equivale a un incidente verificato.\n\nTorna all'indagine ↗\n354TRUSTPILOT / RIGHE DI ORIGINE\n208REDDIT / RIGHE DI ORIGINE\n705GITHUB / RIGHE DI CODICE SORGENTE\n15,302MASTER CSV / RIGHE DI ORIGINE\n16,319 DATI — RIPARTIZIONE PER TIPO DI PIATTAFORMA\n\nProvenienza della categoria Wiki (record di 7,620 · 46.7%): Dati estratti dalla Comunità degli sviluppatori diValve (developer.valvesoftware.com), dalla documentazione/FAQ di SteamDB e dai wiki della comunità di videogiocatori (Liquipedia CS/Dota e i wiki di Fandom Steam) tramite snapshot automatici di WARC e endpoint MediaWiki API tra l’8 agosto 2024 e il 9 settembre 2026. Tutte le voci 7,620 sono completamente integrate nell’esportazione CSV principale (TOTAL_VALVE_SCANDALS_MASTER_DB.csv).\n\nWiki\n7,620\nReddit\n5,635\nGitHub\n2,395\nTrustpilot\n393\nWeb\n276\n9,116 alcuni record di 16,319 (55.8%) contengono riferimenti a Steam / Valve\n\nQuesto archivio consultabile è stato realizzato sulla base di 2026-09-17 dalle esportazioni di origine sopra elencate. L’esportazione separata del master delle righe “40,448-”, utilizzata in altre parti del dossier, ha un ambito diverso. Si veda il crea il manifesto per quanto riguarda i dati statistici di questo archivio; le registrazioni possono sovrapporsi e non corrispondono a singoli episodi.\n\nPIATTAFORMA DI ORIGINE\nRACCOLTA DELLE FONTI\nSteam / Valve menzioni\nCorrispondenza testuale o repository “Valve”Testo mancante / rimosso\n16,569 righe di origine\n16,319 record distinti\n249 righe duplicate unite\n1 riga esclusa\nVisualizza i file originali ↘\n★TRUSTPILOT2015-10-16#1RATING 1/5\n\nSteam is the biggest PC gaming platform without a doubt. A power which could be abused but Steam for the most part doesn't. Overall a definite download for any moden digital age PC gamer. It mu... See more\n\nMA · 7 source copies\n★TRUSTPILOT2021-06-18#2RATING 1/5\n\nThey scam people for money, dont believe me? Read this Source: Steam Subscribers/User Agreement NO GUARANTEES TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, NEITHER VALVE NOR ITS AFFILIA... See more\n\nWF · 7 source copies\n★TRUSTPILOT2016-10-28#3RATING 1/5\n\nSupport on site is terrible. Refunds not happend yet, despite games not working. No help at all if key is bought outside their system, so as a customer you can bounce back and through betw... See more\n\nPE · 7 source copies\n★TRUSTPILOT2021-09-27#4RATING 1/5\n\nThey are an amazing company!! My boyfriend paid for and downloaded a game without realizing it wasn’t the version he wanted. When he reached out, they gave him a full refund and responded in the same... See more\n\nVH · 7 source copies\n★TRUSTPILOT2026-07-20#5RATING 1/5\n\nI’ve used Steam for years, but lately, their sales have really lost their edge. I was hoping to score some solid discounts, but many games still feel overpriced, even during sales. Plus, the support response times can be frustratingly slow when issues arise.\n\nCR\n★TRUSTPILOT2025-12-10#6RATING 1/5\n\nI new here , but all my firends had great experience with this platform . They can make money\n\nZeinab Nematollahi\n★TRUSTPILOT2025-11-18#7RATING 1/5TEXT UNAVAILABLE\n\nNo text was included in the source record.\n\nEM\n★TRUSTPILOT2025-10-21#8RATING 1/5\n\nusing steam for over a decade and i have no words how good the platform is. some friends recommended it to me back in 2015 when we wanted to play csgo together and since then im loggin on it on a daily basis to check new games\n\nTrustpilot\n★TRUSTPILOT2025-05-09#9RATING 1/5\n\nSupport are never able to help you and only able to redicrect you to public linkBreaking there own TOSNot able to provider a refundNot able to provide a safe place for gamingBase on the game you play you can get scam.\n\nSym Link · 7 source copies\n★TRUSTPILOT2025-05-09#10RATING 1/5TEXT UNAVAILABLE\n\nNo text was included in the source record.\n\nHearnius\n★TRUSTPILOT2024-12-30#11RATING 1/5\n\nThis company allowed a single phishing scammer 76561199443342045 in 100's of its user community chat rooms \"Steam Chat\" the whole week of Winter Sales, 12-23-2024 - 2025 to spam spaceintrader a scam phishing website.Don't support Valve & Steam that support sca…\n\nFR · 7 source copies\n★TRUSTPILOT2024-11-15#12RATING 1/5\n\nVery realiable! Ive never had an issue over the 11 years ive had steam.\n\nJM\nLa build e i relativi file sorgente\n\nQuesto archivio unisce 249 le righe duplicate ed esclude una riga dagli input di 16,569, lasciando 16,319 record distinti. Un record può descrivere un evento già trattato da un altro record. La ricerca riguarda titoli, autori, etichette delle fonti e estratti visualizzati; il testo completo salvato si apre con ogni record.\n\nScarica i quattro file di esportazione del codice sorgente ↓Numero di file e hash SHA-256 ↗Manifesto di costruzione originale ↗\n\nIl pacchetto contiene le esportazioni recuperate, corrispondenti al numero di righe della build e ai suoi tre percorsi JSON registrati. La build originale non ha registrato gli hash degli input né un percorso CSV principale; il manifesto allegato documenta i file recuperati e il confronto con l'indice pubblicato.\n\nTrustpilot · steam_support_reviews.json354 righe · Esportazione in formato JSON\nReddit · reddit_censored_forensics.json208 righe · Esportazione in formato JSON\nGitHub · valve_ignored_bugs.json705 righe · esportazione JSON; il nome del file è un'etichetta del collettore\nMaster · TOTAL_VALVE_SCANDALS_MASTER_DB.csv15,302 righe · esportazione in formato CSV utilizzata per il confronto\nElenchi delle cause · UNSEALED_EXHIBITS_AND_AML_DOSSIER.mdWolfire contro Valve: e-mail rese pubbliche, deposizioni di Gabe Newell, confessione di Oct2019riguardo all’AML\nInformazioni principali · FACTS_AND_CITATIONS_DATABASE.md1,638 citazioni discrete e verificate relative a diversi aspetti antitrust e di sicurezz35i\nArchivio assistenza · support_canned_refusals.html1,505 registrazioni dei biglietti · 137 screenshot archiviati · Ricerca istantanea in tempo reale\nCampi dei record, testo mancante ed esportazioni sovrapposte\n\nDate, valutazioni, categorie e stato delle segnalazioni riproducono i dati esportati dalla fonte. Un URL mancante rimane mancante. Le indicazioni “[rimosso]” o “[cancellato]” non specificano chi abbia rimosso un post né il motivo. Il filtro Steam / Valve effettua una corrispondenza testuale, non una valutazione di rilevanza.\n\nL’opzione “Esporta corrispondenze” scarica le voci dell’indice con alcuni estratti; l’opzione “Scarica record” include il testo completo salvato. Il file separato 40,448-riga principale del file CSV e 1,690-riga GitHub CSV In questo build, ciò che conta sono le esportazioni più ampie, non il numero di sorgenti.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam Archivio delle prove — 16,319 Documenti di provenienza certa"
          },
          {
            "level": 2,
            "id": null,
            "text": "PIATTAFORMA DI ORIGINE"
          },
          {
            "level": 2,
            "id": null,
            "text": "La build e i relativi file sorgente"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/it/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/it/",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/TOTAL_VALVE_SCANDALS_MASTER_DB.csv",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive_manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive-inputs.zip",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive-inputs-manifest.json",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/unsealed_legal_and_aml/UNSEALED_EXHIBITS_AND_AML_DOSSIER.md",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/forensic_facts_1000/FACTS_AND_CITATIONS_DATABASE.md",
          "https://phishdestroy.io/steam_dossier/it/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/github_valve_unpatched_bugs.csv"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/it/steam_evidence_archive.content.json",
      "export_json_sha256": "7b4df837a6077c3d9d0b0376b799858bf73d9892e7bd6bc8141ca3e95556f395"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "it/support_canned_refusals.html",
      "language": "it",
      "title": "Steam Archivio dei rifiuti di assistenza e delle risposte predefinite — Il dossier “Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/it/support_canned_refusals",
      "source_html_sha256": "e3dce81e45789099f42105bc9f015fb5e53f7732a1e9bb00b744d5d77b02ba08",
      "exported_at": "2026-09-29T00:18:00.795Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "support_canned_refusals.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/it/support_canned_refusals.pdf?v=print-20260929-v5",
        "sha256": "6e84540de77a929f201fef666c30ced5d2b6143934d6a3ceff5216c8335ec0a5",
        "bytes": 60006,
        "pages": 2
      },
      "integrity": {
        "signed_object": "support_canned_refusals.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "support_canned_refusals.content.json.asc",
        "digest_file": "support_canned_refusals.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify support_canned_refusals.content.json.asc support_canned_refusals.content.json",
          "sha256sum -c support_canned_refusals.content.json.sha256"
        ]
      },
      "content": {
        "text": "COSA DIMOSTRA QUESTA SEZIONE\n\nQuesto repository documenta 137 screenshot originali conservati e 1,505 ricorsi delle vittime sottoposti a verifica, che descrivono in dettaglio la gestione automatizzata dei ticket di assistenza da parte di Valve. Ciò dimostra che, quando gli account vengono compromessi tramite reindirizzamento OpenID o generazione non autorizzata di chiavi API, l'assistenza di Steam ricorre sistematicamente a risposte standardizzate di rifiuto senza effettuare alcuna indagine tecnica. Rifiutando categoricamente il ripristino degli articoli o la divulgazione delle tracce di audit, la piattaforma trasferisce l'intera responsabilità per i difetti strutturali di autenticazione sui titolari degli account compromessi.\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\nTutte le schermate sono immagini acquisite da terze parti. Il copyright e i contenuti rimangono di proprietà dei rispettivi autori e delle rispettive piattaforme (utenti di Reddit, autori della community Steam, recensori di Trustpilot, X e autori di post su YouTube). Sono riprodotte esclusivamente a scopo identificativo e di informazione di interesse pubblico; non viene rivendicata alcuna titolarità. Ogni immagine è collegata alla sua fonte primaria.\n\nFigures reported on the source page\nMeasure\tReported value\tScope\nDocumentazione ufficiale\t1505\tRicorsi delle vittime verificati e discussioni relative alle contravvenzioni\nScreenshot archiviati\t137\tAcquisizione dei ticket ad alta risoluzione salvati localmente\nTasso di ripristino\t0.0%\tAnnullamenti concessi nei casi relativi alle operazioni di \"API\" - dirottamenti chiave\nDuplicazione dei modelli\t100%\tRiutilizzo delle trascrizioni testuali da parte di tutto il personale (Ilya, Roger, Maverick)\nProve forensi: i tre pilastri fondamentali del rifiuto di collaborazione\nPILASTRO 01 · AMMISSIONEAllegato R -014\nLa confessione di Roger: confermata l’attacco MitM a API\n\nNella risposta al ticket n.1cp582i, Steam, il membro dello staff di assistenza “Roger” ammette per iscritto che gli hacker annullano transazioni legittime tramite API e le sostituiscono con bot clonati in pochi millisecondi, ma si rifiuta di ripristinare gli oggetti e invita la vittima a rivolgersi a un “tecnico informatico locale”.\n\nVerifica la dichiarazione scritta di ammissione ↗\nPILASTRO 02 · ESCALATIONAllegato R -012\n7-Day trading: mantenere la posizione, non intervenire\n\nUna vittima ha fornito lo SteamID64 degli account dell'hacker durante il periodo di sospensione delle operazioni di trading giornaliero di \"7-\". I membri del team di assistenza \"Artem\" e \"Ilya\" si sono rifiutati di bloccare gli oggetti rubati, adducendo come motivazione la scarsità degli oggetti virtuali, e hanno chiuso il ticket con un messaggio standard automatizzato.\n\nVisualizza il resoconto relativo a più membri del personale ↗\nPILASTRO 03 · POLITICAAllegato R -002\nScarsità di mercato rispetto ai diritti di proprietà\n\nLa politica ufficiale di Valve in materia di ripristino degli oggetti stabilisce esplicitamente che gli oggetti non vengono restituiti poiché il loro ripristino \"ridurrebbe la loro scarsità e gonfierebbe l'economia, abbassando il valore degli oggetti sul Mercato della Comunità\".\n\nScreenshot della politica di ispezione ↗\nGenesi storica · 22 March 2018 a 2026\nAllegato H -003 · 8-: superficie di attacco non protetta da patch per un anno\nLa prima sostituzione commerciale di cui si abbia traccia (22 marzo 2018)\n\nEsattamente una settimana prima che Valve imponesse la sua controversa \"7-\" (sospensione di 24 ore per gli scambi giornalieri) sugli oggetti di Counter-Strike, la comunità degli scambiatori ha scoperto i primi casi concreti di Steam Exploit di reindirizzamento del traffico sul sito API. Gli autori dell'attacco hanno dirottato delle sessioni web per generare una chiave non autorizzata API all'indirizzo steamcommunity.com/dev/apikey senza la conferma da parte di Mobile 2FA, consentendo ai bot di annullare e sostituire le operazioni in tempo reale.\n\nAvviso del 2018e di marzo: \"I truffatori sono in grado di rilevare automaticamente questa offerta di scambio e la rifiuteranno sul tuo account, poiché dispongono della tua chiave Steam API. Il bot truffaldino ti invierà quindi un'offerta di scambio per le stesse skin... e tu non noterai alcuna differenza!\"\nPercorso delle testimonianze storiche\n22 Mar 2018: Prima sostituzione documentata dell'API\n2019: Il supporto standardizza la difesa contro il \"malware\"\n2020: Script \"Chiudi richiesta di assistenza\" reso più sicuro\n2022–2026: Automazione del phishing tramite BitB e codici QR\nApri il thread originale su Reddit \"2018\" ↗\nPrimary sources\n\n137 gallery cards refer to 78 distinct primary URLs. Images and repeated exhibit captions are omitted from this reading edition.\n\nFull visual archive and original captures",
        "headings": [
          {
            "level": 2,
            "id": null,
            "text": "Figures reported on the source page"
          },
          {
            "level": 2,
            "id": null,
            "text": "Prove forensi: i tre pilastri fondamentali del rifiuto di collaborazione"
          },
          {
            "level": 3,
            "id": null,
            "text": "La confessione di Roger: confermata l’attacco MitM a API"
          },
          {
            "level": 3,
            "id": null,
            "text": "7-Day trading: mantenere la posizione, non intervenire"
          },
          {
            "level": 3,
            "id": null,
            "text": "Scarsità di mercato rispetto ai diritti di proprietà"
          },
          {
            "level": 3,
            "id": null,
            "text": "La prima sostituzione commerciale di cui si abbia traccia (22 marzo 2018)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Primary sources"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/it/#proxy-bypass-explainer",
          "https://www.reddit.com/r/csgo/comments/1cp582i/i_got_api_scammed_what_do_i_do_now/",
          "https://www.reddit.com/r/DotA2/comments/1e5ovy4/my_account_was_hacked_and_steam_support_refuse/",
          "https://www.reddit.com/r/Steam/comments/3b2abd/steam_will_no_longer_restore_scammed_items_item/",
          "https://www.reddit.com/r/GlobalOffensiveTrade/comments/863tk1/psa_urgent_huge_scam_happening_read_here_how_to",
          "https://phishdestroy.io/steam_dossier/it/support_canned_refusals#gallery-grid"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/it/support_canned_refusals.content.json",
      "export_json_sha256": "d9efc69e3426910d444df74ed8fc578cd7102b5e8db1aa7bc7b4968b066736ec"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "it/valve_scandals_registry.html",
      "language": "it",
      "title": "Valve Registro degli scandali — Il dossier su “Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/it/valve_scandals_registry",
      "source_html_sha256": "af90fae04ad7176b23f3b6fa511c003a94b838a850fa8cfe407d7a5771076f79",
      "exported_at": "2026-09-29T00:18:01.541Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "valve_scandals_registry.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/it/valve_scandals_registry.pdf?v=print-20260929-v5",
        "sha256": "2b5ed20923a67b7b9595acdd3c9d0117b3c3890c40a79d034ac1b039fc3afadc",
        "bytes": 62282,
        "pages": 6
      },
      "integrity": {
        "signed_object": "valve_scandals_registry.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "valve_scandals_registry.content.json.asc",
        "digest_file": "valve_scandals_registry.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify valve_scandals_registry.content.json.asc valve_scandals_registry.content.json",
          "sha256sum -c valve_scandals_registry.content.json.sha256"
        ]
      },
      "content": {
        "text": "Archivio completo degli scandali\nValve Registro centrale degli scandali — 160 Incidenti segnalati\nDATI DI ORIGINE (GREZZI): 11,768\n\nSegnalato. Fonte verificata. Ancora aperto.\n\nCOSA DIMOSTRA QUESTA SEZIONE\n\nQuesto registro centrale raccoglie 160 dati primari verificati in modo indipendente che descrivono in dettaglio difetti persistenti della piattaforma, segnalazioni della comunità rimosse e casi di mancata assistenza ai consumatori nell’ecosistema di Valve. Attingendo a reclami verificati presentati su Trustpilot, ticket relativi a problemi di sicurezza archiviati su GitHub e procedimenti delle autorità di regolamentazione, il registro evidenzia ricorrenti carenze sistemiche nel recupero degli account e nella risoluzione delle controversie con i clienti.\n\n← Torna al briefing esecutivo\n\n160 dati raccolti: un’operazione di assistenza valutata da chi l’ha utilizzata, discussioni che non sono più visibili, difetti della piattaforma segnalati e lasciati irrisolti, e gli incidenti di cui Valve ha già dovuto rispondere. Nulla di quanto riportato qui è frutto di una nostra interpretazione: ogni riga riporta la fonte originale. Aprine una e leggila tu stesso.\n\nDocumentazione di origine\n11,768\nIn tutte le categorie\nDifetti della piattaforma\n3,372\nVulnerabilità della piattaforma segnalate dalla comunità\nDiscussioni censurate\n109\nPost di Reddit rimossi dal moderatore\nReclami relativi all'assistenza\n471\nReclami verificati su Trustpilot\nFattibilità dell'applicazione\nBlocco del dominio dell'host di autenticazione\n\nIl blocco a livello di dominio degli host di autenticazione OpenID è tecnicamente semplice da implementare: una volta che una risorsa viene esclusa dal reindirizzamento di accesso trSteam, i domini di terze parti che fungono da proxy di autenticazione per quella stessa risorsa possono essere filtrati dallo stesso insieme di regole. Nel dossier principale viene fornita un’analisi dettagliata della fattibilità dell’implementazione.\n\nVedi la fattibilità dell’applicazione nel fascicolo →\nCategoria: Reclami all'assistenza di Trustpilot (escalation negative filtrate)176 record di origine corrispondenti · duplicati nascosti\nConsumer Complaint2026-07-20\nAuthor: C***\n\nI’ve used Steam for years, but lately, their sales have really lost their edge. I was hoping to score some solid discounts, but many games still feel overpriced, even during sales. Plus, the support response times can be frustratingly slow when issues arise.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2026-07-20\nConsumer Complaint2025-05-09\nAuthor: S*** L***\n\nSupport are never able to help you and only able to redicrect you to public linkBreaking there own TOSNot able to provider a refundNot able to provide a safe place for gamingBase on the game you play you can get scam.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2025-05-09\nConsumer Complaint2024-12-30\nAuthor: F***\n\nThis company allowed a single phishing scammer 7656…2045 in 100's of its user community chat rooms \"Steam Chat\" the whole week of Winter Sales, 12-23-2024 - 2025 to spam spaceintrader a scam phishing website.Don't support Valve & Steam that support scams. Don't give your log in credentials to account hijacking scammers. This company also allows engagements of commercial advertising / spam for gambling in violation of its own Rules and Guidelines / Online Conduct. 7656…5023 proof - groups/deskinsfans key drop advertising, thanks TannerfromKD and Valve!*\"The Consumer Review Fairness Act (CRFA) protects people’s ability to share their honest opinions about a business’s products, services, or conduct, in any forum, including social media. The law protects a broad variety of honest consumer assessments, including online reviews, social media posts, uploaded photos, videos, etc. And it doesn’t just cover product reviews. It also applies to consumer evaluations of a company\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2024-12-30\nConsumer Complaint2024-07-31\nAuthor: A***\n\nhorrible company.randomly you get \"This account may have been accessed by someone else.\"this happened to me 3 times.the 3rd time they wanted a cd key.a spent useless cd key that nobody has any reason to keep laying around.i gave them the paypal bill for my first purchase back in 2015.i gave them a bill for my first phone number ever on the account.i still got the same email attached to the account.this company is literally a scam. nothing but a scam.they randomly claim you been accessed somewhere else and then require you to give them information no reasonable person would ever have, if not your done and have to rebuy everything.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2024-07-31\nConsumer Complaint2023-12-09\nAuthor: K***\n\nHad 288 euros in steam wallet, someone hacked my account even with two step verification, write a steam support for help but only answer was if something is spent in community market they can’t help.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2023-12-09\nConsumer Complaint2023-09-26\nAuthor: J***\n\nI was banned for saying \"Who let grandma on the PC\"and another for simply calling someone ignorant.Power tripping mods, devs who don't care, steam doesn't care. Yet allows racism/trolling/etc Fk steam, its a joke now.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2023-09-26\nConsumer Complaint2022-08-31\nAuthor: Anonymous\n\nSteam community is plain bad for a various reasons:1. Steam forums are a big mess, for example they allow users to post in any language and as result you get jumbled mess with posts in foreign languages together with English language posts. For example, If you check CS GO forums, you'll see half of posts are in Russian and half in English. I don't understand why such a big and international company would leave their forums so unorganized like that. All other normal companies have English only language allowed which is an international language and sometimes subforums for other languages like German, French and etc... so if French people want to post in French they go specifically in that sub-forum. But no, Steam doesn't care about this. Their forums is a one big mess.2. Moderation is biased and joke. I don't understand why such a big company like Steam can't afford to hire people for moderation and pay them. Instead they just recruit random people for moderation who do it for free and\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2022-08-31\nConsumer Complaint2022-05-28\nAuthor: J***\n\nThe login code never arrives. I hate Steam.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2022-05-28\nConsumer Complaint2021-11-08\nAuthor: N***\n\nThe service is terrible, I only signed up because I really like the game I wanted, but the rest is terrible, I hope to get something better soon.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-11-08\nConsumer Complaint2021-06-18\nAuthor: W***\n\nThey scam people for money, dont believe me? Read thisSource: Steam Subscribers/User Agreement NO GUARANTEESTO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, NEITHER VALVE NOR ITS AFFILIATES GUARANTEE CONTINUOUS, ERROR-FREE, VIRUS-FREE OR SECURE OPERATION AND ACCESS TO STEAM, THE CONTENT AND SERVICES, YOUR ACCOUNT AND/OR YOUR SUBSCRIPTION(S) OR ANY INFORMATION AVAILABLE IN CONNECTION THEREWITH.In short: You got a virus or your data leaked because of our software? Whoopsies we dont care, that isnt even legal or the last of their scammy stuff...\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-06-18\nConsumer Complaint2021-05-14\nAuthor: B***\n\nThe support is one of the worst I've ever seen.Useless support team.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-05-14\nConsumer Complaint2020-04-02\nAuthor: J***\n\nSteamcommunity has 15% fees, 15!!!!\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2020-04-02\nConsumer Complaint2020-03-27\nAuthor: H***\n\nWhat can I say? the support is one of the worst I've ever seen maybe the FUNCOM is much worse. If you tell the true on the steam forum you just got a BAN even if what you said did not violated the rules of the forum.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2020-03-27\nConsumer Complaint2018-03-16\nAuthor: B***\n\ndon't sign up will stick on your computer will kill your pc power you can't remove it from your pc even you deleted it will stay woking in the system\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2018-03-16\nConsumer Complaint2016-12-27\nAuthor: J***\n\nIn bloddy hate their page it's tiresome, it's in no way intuitive. I tried reaching out for support, but that is a maze.I'm simply trying to log in and redeem a key of a product I already bought, their search function is a joke. I f*u*c*k*i*n*g hate them. The layout is not like the how to video from the dealer, this can be done much simpler. I don't frigin care aboutn what other titles you have in store or what genre, I just want to redeem my key and install.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-12-27\nConsumer Complaint2016-10-28\nAuthor: P***\n\nSupport on site is terrible.Refunds not happend yet, despite games not working.No help at all if key is bought outside their system, so as a customer you can bounce back and through between bad support systems?? I wait for some other companies to compete in this market, for this can't be the best we as customers can expect.And do put an email up to find, instead of this stuppid website where you spend so long time trying to find a solution on, instead of a simple mail. Often the problem is not there, or if it's there just saying no help here???I need a response\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-10-28\nConsumer Complaint2016-06-26\nAuthor: V*** W***\n\nUseless support as always!\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-06-26\nConsumer Complaint2014-07-01\nAuthor: J***\n\nexpensive, and support team not willing to cooperate\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2014-07-01\nConsumer Complaint2014-04-15\nAuthor: B***\n\nWhen you pay for a program, you expect it too work. cant not buy or anything and have written to valve. but there is not a being done a damn thing abut it..\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2014-04-15\nConsumer Complaint2026-09-03\nAuthor: M***\n\nWorst platform ever wont give me a refund even though a game is unplayable because of bugs I won't ever be using the crap platform again I hope the platform breaks down for good piece fo crao\n\nTarget Domain: steamcommunity.com / steampowered.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2026-09-03\n\nNessun risultato corrispondente\n\nProva a modificare la query attiva o a selezionare una scheda di categoria diversa.\n\n1 / 9",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Valve Registro centrale degli scandali — 160 Incidenti segnalati"
          },
          {
            "level": 2,
            "id": null,
            "text": "Blocco del dominio dell'host di autenticazione"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: C***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: S*** L***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: F***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: A***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: K***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: Anonymous"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: N***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: W***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: H***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: P***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: V*** W***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: M***"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/it/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/it/#autoban-feasibility-section",
          "https://www.trustpilot.com/review/steamcommunity.com"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/it/valve_scandals_registry.content.json",
      "export_json_sha256": "443dabe1f3831331a8c7dddca90d1827efd3782251fa6b7307241a5ecbf9ae97"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "it/output_steam_network/index.html",
      "language": "it",
      "title": "Architettura, non vulnerabilità: The Automation Network — Il dossier su “Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/it/output_steam_network/index",
      "source_html_sha256": "870cc13c4ccf93680a7c88933cea39a5f014648f2933e6c1bf700c5d337b5ad1",
      "exported_at": "2026-09-29T00:18:01.917Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__index.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/it/output_steam_network__index.pdf?v=print-20260929-v5",
        "sha256": "fefe3aa92b170ad19898a09947c6b4a6465638c406c9c138ab428869875578dd",
        "bytes": 66707,
        "pages": 3
      },
      "integrity": {
        "signed_object": "output_steam_network__index.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__index.content.json.asc",
        "digest_file": "output_steam_network__index.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__index.content.json.asc output_steam_network__index.content.json",
          "sha256sum -c output_steam_network__index.content.json.sha256"
        ]
      },
      "content": {
        "text": "Allegato VII · Analisi dell'architettura tecnica\nSteam Architettura di rete — Fedeltà al protocollo e analisi dell'ecosistema\n\nL'automazione è l'architettura di “Valve”. Non è un exploit.\n\nCOSA DIMOSTRA QUESTA SEZIONE\n\nQuesto modulo illustra la topologia tecnica dei repository degli sviluppatori di 252, dei profili di 3,320 GitHub e delle coppie di collaboratori di 4,214 che sono alla base dell’ecosistema di automazione di Steam. Dimostra che l’automazione di terze parti si basa sul protocollo ufficiale Connection Manager di Valve, sugli schemi Protobuf e sulle API Web, senza codice di exploit. Progettando token di conferma algoritmici Steam Guard e riscuotendo commissioni minime di transazione fino a 66.7%, Valve, l’azienda agisce come architetto intenzionale e principale beneficiario commerciale delle operazioni automatizzate dell’ecosistema.\n\n← Torna al briefing esecutivo\n\nQuando Valve si rivolge alle autorità di regolamentazione, ai gestori di pagamenti o alle vittime di truffe, attribuisce il furto di skin e la manipolazione del mercato a \"exploit non autorizzati da parte di terzi\" e a \"automazioni illecite e non autorizzate\". La realtà tecnica di questa rete di repository 252-dimostra esattamente il contrario: Ogni framework di automazione, bot di trading e flotta di farming opera rigorosamente nel rispetto delle definizioni ufficiali del protocollo, delle API Web e dei meccanismi di autenticazione progettati, documentati e monetizzati dValve.\n\nRisultato dell’analisi forense: architettura consapevole contro violazione illegittima\n\nIl software analizzato in questo modulo — tra cui SteamKit, node-steam-user, ValvePython/steam, e ArchiSteamFarm — contiene zero vulnerabilità software, zero corruzioni di memoria e zero exploit zero-day. Si tratta di implementazioni open source pulite e robuste del protocollo client proprietario Connection Manager (CM) di Valve, dei Google Protocol Buffers (Protobufs) e delle API Web. Valve ha progettato queste API per accettare accessi programmatici e ha sviluppato Steam Guard per consentire l'utilizzo di token di conferma algoritmici (identity_secret), e riscuote una commissione pubblicizzata come “15%” che aumenta fino a fino a 66.7% a favore di Valve sulle carte ad alta velocità e sulle merci in calo di cui le botnet automatizzate si liberano.\n\nPillar 01 · Protocol Fidelity\nSchemi ufficiali di Protobuf\n\nLe librerie di automazione non aggirano i controlli di sicurezza. Esse serializzano i messaggi Protobuf ufficiali (steammessages_clientserver.proto) tramite TCP/WebSockets direttamente ai cluster CM ufficiali di Valve, esattamente come fa il client Steam.\n\nPillar 02 · Algorithmic 2FA\nAutorizzazione al commercio programmatico\n\nL'intera economia del commercio di pelle, del valore di diversi miliardi di dollari, dipende dall'Valve IEconService API e chiavi di autenticazione TOTP per dispositivi mobili. Valve ha progettato appositamente Steam Guard per consentire le conferme delle transazioni da macchina a macchina.\n\nPilastro 03 · Beneficiario commerciale\nTraffico generato dalle macchine monetizzate: fino a66.7%, con una commissione minima\n\nValve pubblicizza una commissione “15%”, ma sugli articoli di largo consumo su cui operano i bot automatizzati — figurine, confezioni e articoli economici con prezzi compresi tra $0.03 e $0.05 — la commissione minima di due centesimi di Valve ($0.01Steam + $0.01 publisher) comporta un costo aggiuntivo 50% a 66.7% a favore di Valve (2¢ prelevati da una carta 3¢, lasciando al venditore 1¢). Più $5.00 per conto ($26.8M solo per la flotta sottoposta a scansione).\n\nModulo 01 · Repository e prove relative al protocollo\nInfrastruttura pubblica per sviluppatori e repository\n\nCatalogo forense dettagliato dei repository open source di 252 che sono alla base dell'automazione di Steam. Illustra come gli strumenti standard di ingegneria del software implementino gli endpoint API pubblicati da Valve senza ricorrere a exploit.\n\n252Archivi\n4,554Collegamenti relativi al ruolo\nEsamina le prove contenute nell'archivio →Modulo 02 · Demografia degli ecosistemi\nIndicatori relativi all'ecosistema ingegneristico globale\n\nRipartizione geografica e istituzionale degli ingegneri software di 3,320 che contribuiscono all'ecosistema di automazione Steam, comprese le affiliazioni aziendali presso i principali datori di lavoro del settore tecnologico.\n\n3,320Ingegneri\n98,902Coppie di connessioni\nVerifica gli indicatori dell'ecosistema →Modulo 03 · Grafico visivo interattivo\nGrafico interattivo del protocollo e della rete degli sviluppatori\n\nMappa interattiva completa Vis.js che illustra le reti di repository, le librerie di protocolli (SteamKit, Steamworks, ASF) e le sovrapposizioni tra i contributori dei diversi progetti. Dimostra visivamente la potenza dell’architettura software open source legittima e interconnessa che alimenta l’ecosistema di automazione di Steam.\n\nInterattivoVis.js Motore\nIsolamento dei clusterRicerca in tempo reale\nZero vulnerabilitàAPI standard\nApri il grafico interattivo della rete →\nContesto normativo e giuridico (articolo di GDPR 25 e tutela dei consumatori):\nIn base al principio della “protezione dei dati fin dalla progettazione e per impostazione predefinita”, un’architettura di piattaforma che consenta la generazione silenziosa di chiAPI, l’annullamento di operazioni senza preavviso e la liquidazione automatizzata delle attività da parte di sistemi automatici rappresenta una scelta architettonica dell’operatore della piattaforma. Quando Valve respinge sistematicamente le richieste di rimborso dei consumatori sostenendo che le perdite sono state causate da «attacchi informatici esterni», nasconde il fatto che il vettore di attacco è proprio l’architettura Web API progettata intenzionalmente dValve.\n\nVISUALIZZAZIONE INTERATTIVA\n\nÈ disponibile una visualizzazione interattiva completa del repository 252-e del grafico della rete degli sviluppatori di 3,320-all'indirizzo network.html. Le metriche aggregate si trovano nella Metriche BI pagina.\n\nIl Dossier “Steam” · Archivio dell’architettura tecnica · Documenti di dominio pubblico · Tutti i diritti ceduti all’umanità.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam Architettura di rete — Fedeltà al protocollo e analisi dell'ecosistema"
          },
          {
            "level": 3,
            "id": null,
            "text": "Schemi ufficiali di Protobuf"
          },
          {
            "level": 3,
            "id": null,
            "text": "Autorizzazione al commercio programmatico"
          },
          {
            "level": 3,
            "id": null,
            "text": "Traffico generato dalle macchine monetizzate: fino a66.7%, con una commissione minima"
          },
          {
            "level": 2,
            "id": null,
            "text": "Infrastruttura pubblica per sviluppatori e repository"
          },
          {
            "level": 2,
            "id": null,
            "text": "Indicatori relativi all'ecosistema ingegneristico globale"
          },
          {
            "level": 2,
            "id": null,
            "text": "Grafico interattivo del protocollo e della rete degli sviluppatori"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/it/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/it/output_steam_network/valve_ru_farming_isolated.html",
          "https://phishdestroy.io/steam_dossier/it/output_steam_network/steam_ecosystem_dashboard.html",
          "https://phishdestroy.io/steam_dossier/it/output_steam_network/network.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/it/output_steam_network__index.content.json",
      "export_json_sha256": "011b8f9292791e54e9da7b29500c0e043665613fcd0fe387e77982c419100674"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "it/output_steam_network/network.html",
      "language": "it",
      "title": "Esploratore di sviluppatori e repository — Il dossier su “Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/it/output_steam_network/network",
      "source_html_sha256": "44a415b21d52fb3d45baf9e555a71ae9b7f6a785f3af1aab37e71a8ebdcb7663",
      "exported_at": "2026-09-29T00:18:02.951Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__network.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/it/output_steam_network__network.pdf?v=print-20260929-v5",
        "sha256": "c3e2f00e23e578abdff27c8818826448fef73b4255e43127abb066f2ee323008",
        "bytes": 35156,
        "pages": 1
      },
      "integrity": {
        "signed_object": "output_steam_network__network.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__network.content.json.asc",
        "digest_file": "output_steam_network__network.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__network.content.json.asc output_steam_network__network.content.json",
          "sha256sum -c output_steam_network__network.content.json.sha256"
        ]
      },
      "content": {
        "text": "Esploratore di progetti e repository\n\nCerca un nodo. Esamina la relazione registrata.\n\nDOCUMENTI PUBBLICI / CONNESSIONI RACCOLTE\nRicerca in tempo reale\nLivelli filtro\nSviluppatori totali3,320\nTotale operazioni di pronti contro termine252\nGRAFICO VISUALIZZATO / SOTTOCOLLEZIONE468 NODI • 1103 LATI\nRecord di profilo selezionato\n\n💡 Clicca su un nodo qualsiasi del grafico oppure digita nel campo \"Cerca\" per visualizzarne le connessioni raccolte e i percorsi di origine.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Esploratore di progetti e repository"
          }
        ],
        "links": []
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/it/output_steam_network__network.content.json",
      "export_json_sha256": "3593c122a25033b363943ffcf7b5c865bbe7a666022f29bbf779bb5eec92d562"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "it/output_steam_network/steam_ecosystem_dashboard.html",
      "language": "it",
      "title": "La rete raccolta in cifre — Il dossier “Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/it/output_steam_network/steam_ecosystem_dashboard",
      "source_html_sha256": "d4973ba4c280e06c87e882a656e1b81110b06a4c348c0ec163b666e11660a0d9",
      "exported_at": "2026-09-29T00:18:03.346Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__steam_ecosystem_dashboard.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/it/output_steam_network__steam_ecosystem_dashboard.pdf?v=print-20260929-v5",
        "sha256": "fb0e4411edf875dc7df034a480d340b0c8e08d35985820c8db18886d14c0fbb4",
        "bytes": 37964,
        "pages": 2
      },
      "integrity": {
        "signed_object": "output_steam_network__steam_ecosystem_dashboard.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__steam_ecosystem_dashboard.content.json.asc",
        "digest_file": "output_steam_network__steam_ecosystem_dashboard.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__steam_ecosystem_dashboard.content.json.asc output_steam_network__steam_ecosystem_dashboard.content.json",
          "sha256sum -c output_steam_network__steam_ecosystem_dashboard.content.json.sha256"
        ]
      },
      "content": {
        "text": "PANORAMICA STATISTICA // FILE 02\nSteam Pannello di controllo dell'ecosistema — La rete in cifre\n\nLa rete, in cifre.\n\nCOSA DIMOSTRA QUESTA SEZIONE\n\nQuesta dashboard aggrega le informazioni strutturali relative agli sviluppatori di 3,320 e ai repository di 252, identificando i codici sorgente specifici per il settore del gioco d’azzardo 68 e i ponti di connessione multipiattaforma. I dati empirici evidenziano i raggruppamenti geografici e le sovrapposizioni tra sviluppatori, dimostrando che l’infrastruttura di gioco d’azzardo “skin” di terze parti opera come un settore software organizzato e altamente interconnesso, integrato con la piattaforma di Steam.\n\n← Torna al briefing esecutivo\n\nStatistiche aggregate del database delle indagini: distribuzione geografica, principali aziende, archivi di skin per il gioco d’azzardo e ponti di connessione attivi.\n\nSviluppatori di Scanned3320\nTotale operazioni di pronti contro termine252\nRepos relativi al gioco d'azzardo68\nConnessioni totali1,426\nStruttura e settori dell'automazione\nSettore I — Nucleo della Società “Valve”\n\nRepository ufficiali e software di sistema. Spazio di sviluppo confermato dei collaboratori di Valve, Nephyrin e Joe Ludwig.\n\nSettore II — Motori di autorizzazione ed emulatori di protocollo (SteamKit)\n\nLibrerie di rete ottenute tramite reverse engineering, realizzate in collaborazione da Nephyrin di Valve e DoctorMcKay, sviluppatore di giochi d'azzardo per skins.\n\nSettore III — Clienti di card farming (ArchiSteamFarm)\n\nUtilizza gli emulatori del protocollo SteamKit per eseguire in background milioni di client fittizi (inattivi) al fine di accumulare carte collezionabili.\n\nDistribuzione geografica degli sviluppatori\nGermania57\nStati Uniti52\nCanada48\nRegno Unito44\nPolonia30\nFrancia28\nFederazione Russa27\nCina27\nStati Uniti (Stato di Washington)23\nAustralia19",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam Pannello di controllo dell'ecosistema — La rete in cifre"
          },
          {
            "level": 3,
            "id": null,
            "text": "Settore I — Nucleo della Società “Valve”"
          },
          {
            "level": 3,
            "id": null,
            "text": "Settore II — Motori di autorizzazione ed emulatori di protocollo (SteamKit)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Settore III — Clienti di card farming (ArchiSteamFarm)"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/it/#briefing-heading"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/it/output_steam_network__steam_ecosystem_dashboard.content.json",
      "export_json_sha256": "2f882ea6803b6892502a02656ce2cea251238da5625da9b927aa42ce48551d39"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "it/output_steam_network/valve_ru_farming_isolated.html",
      "language": "it",
      "title": "Codice, collaboratori e fork — Il dossier su “Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/it/output_steam_network/valve_ru_farming_isolated",
      "source_html_sha256": "ff6c64da68f395ccfc4d5024f80a163eb88085ec12bc58e4430837625d6ce70e",
      "exported_at": "2026-09-29T00:18:03.344Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__valve_ru_farming_isolated.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/it/output_steam_network__valve_ru_farming_isolated.pdf?v=print-20260929-v5",
        "sha256": "f44921e717e5ee5d9d4e45ffc485ef2d5f06b3ba94d4a6850af7b37f262beb1a",
        "bytes": 40805,
        "pages": 2
      },
      "integrity": {
        "signed_object": "output_steam_network__valve_ru_farming_isolated.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__valve_ru_farming_isolated.content.json.asc",
        "digest_file": "output_steam_network__valve_ru_farming_isolated.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__valve_ru_farming_isolated.content.json.asc output_steam_network__valve_ru_farming_isolated.content.json",
          "sha256sum -c output_steam_network__valve_ru_farming_isolated.content.json.sha256"
        ]
      },
      "content": {
        "text": "PARTE II / SEGUI LA RELAZIONE DOCUMENTATA\n\nI fork, i contributi e le dipendenze software costituiscono prove evidenti. Questa visione tiene conto dei ruoli individuati; per quanto riguarda l’occupazione, le violazioni della sicurezza e il coinvolgimento in attività criminali, sono necessarie fonti aggiuntive.\n\nApri la mappa interattiva delle funzionalità ↗\nFONTI PUBBLICHE / VERIFICA DEI RUOLI\nIl codice. I collaboratori. I fork.\n1. Nephyrin: fork e contributi\n\nLo snapshot fornito indica Nephyrin come collaboratore di ValveSoftware/Proton e autore di fork di SteamRE/SteamKit e SteamRE/open-steamworks. I dati del suo profilo riportano “Valve Software”. Questi campi vanno interpretati separatamente.\n\nUn fork registra una copia del repository. Questa esportazione non include un commit che rifletta le modifiche apportate al codice di autenticazione di SteamKit.\nRiferimenti al repository / Esamina la cronologia\nSteamRE/SteamKit ↗ SteamRE/open-steamworks ↗\n2. Funzionalità pubbliche: automazione senza client desktop\n\nSteamKit e node-steam-user consentono di interagire a livello di programmazione con Steam. ArchiSteamFarm documenta la gestione di più account per il “card farming” e dichiara SteamKit2 come dipendenza.\n\nSi tratta di funzionalità concrete di automazione. L’esecuzione “headless” non implica un uso commerciale esclusivo né l’aggiramento di una protezionSteam. Gli aspetti rilevanti sono le credenziali richieste, le azioni a disposizione dell’utente e i controlli applicati dalla piattaforma.\n\nFonte: file README dei progetti e ArchiSteamFarm.csproj. La mappa delle funzionalità riporta i collegamenti a ciascuna dipendenza documentata.\n3. JoeLudwig: l'etichetta dei collaboratori dell'HL2SDK\n\nL'istantanea indica JoeLudwig come collaboratore dei progetti alliedmodders/hl2sdk, ValveSoftware/openvr e ValveSoftware/source-sdk-2013. Si tratta di una relazione tra progetti facilmente individuabile. L'esportazione non fornisce prove che colleghino una specifica modifica all'SDK a un furto o all'utilizzo a fini di gioco d'azzardo.\n\nRiferimenti al repository / Esamina la cronologia\nalliedmodders/hl2sdk ↗ DoctorMcKay/node-steam-user ↗\nSCHEMA LOGICO // TRACCE\nDiagramma di flusso della logica di connessione:\nPROFILO RELAZIONE\nNephyrin / profilo raccolto\nAutore: Proton. Fork: SteamKit e open-steamworks.\n▼ Relazioni di fork raccolte\nBIBLIOTECA COMUNITARIA\nSteamRE/SteamKit\nLibreria di rete pubblica Steam gestita dall'organizzazione SteamRE.\n▼ Dipendenza dichiarata da SteamKit2\nAUTOMAZIONE DOCUMENTATA\nJustArchiNET/ArchiSteamFarm\nDocumenta la pratica del \"card farming\" su più account e una dipendenza da SteamKit2.\nANALISI DELLE PROVE / PANORAMICA DELLE FONTI\nREGISTRAZIONE: etichette distinte per contributori e forker.\nDOCUMENTATO: le biblioteche pubbliche favoriscono le interazioni programmatiche Steam.\nDOMANDA APERTA: l’attribuzione della paternità di un codice specifico, l’approvazione della piattaforma e l’attribuzione della responsabilità per gli abusi richiedono prove distinte.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Il codice. I collaboratori. I fork."
          },
          {
            "level": 2,
            "id": null,
            "text": "1. Nephyrin: fork e contributi"
          },
          {
            "level": 2,
            "id": null,
            "text": "2. Funzionalità pubbliche: automazione senza client desktop"
          },
          {
            "level": 2,
            "id": null,
            "text": "3. JoeLudwig: l'etichetta dei collaboratori dell'HL2SDK"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/it/investigation_part2.html#automation-map",
          "https://github.com/SteamRE/SteamKit",
          "https://github.com/SteamRE/open-steamworks",
          "https://github.com/alliedmodders/hl2sdk",
          "https://github.com/DoctorMcKay/node-steam-user"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/it/output_steam_network__valve_ru_farming_isolated.content.json",
      "export_json_sha256": "fca8207a2b85a69fb34a8266f67a6c14a956afca09e291bc11cf72d2fcf6d382"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "pt/card_economy.html",
      "language": "pt",
      "title": "A economia dos cartões — O Dossier Steam",
      "source_url": "https://phishdestroy.io/steam_dossier/pt/card_economy",
      "source_html_sha256": "366224ee53dc3eda6dcad48bd0c633bfe2048b01a2cf20483561f9ea68a423b7",
      "exported_at": "2026-09-29T00:18:04.906Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "card_economy.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/pt/card_economy.pdf?v=print-20260929-v5",
        "sha256": "432aa81698152153cf1a75e65f1c7227039be210bfc7a16ee881471285cf0233",
        "bytes": 255895,
        "pages": 25
      },
      "integrity": {
        "signed_object": "card_economy.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "card_economy.content.json.asc",
        "digest_file": "card_economy.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify card_economy.content.json.asc card_economy.content.json",
          "sha256sum -c card_economy.content.json.sha256"
        ]
      },
      "content": {
        "text": "ANEXO V — A ECONOMIA DOS CARTÕES\nUma «fazenda de bots» não é uma fuga na loja do Valve. É uma cliente.\n\nUma conta Steam não pode receber nem um único cartão de jogo até ter gasto $5.00 na loja. Não pode fazer «farming» de um jogo que não possui, nem de um que lhe tenha sido oferecido gratuitamente. Assim, antes de um sistema automatizado de «farming» de cartas produzir absolutamente nada, tem de pagar para ter acesso — por conta, a um preço publicado por Valve. Em seguida, a cláusula de automatização de Valve especifica, linha a linha, exatamente o que esse sistema de farm produz; a sua licença proíbe todas as formas pelas quais um cartão obtido através do sistema de farm se transforma em dinheiro; e o seu mercado fica com uma comissão quando o cartão é vendido — anunciado em 15%, mas com um valor mínimo de dois cêntimos por venda, o que, num cartão cujo preço é expresso em cêntimos, representa a maior parte do preço. Esta exposição avalia a dimensão desse comércio, quanto custa, em conjuntos, o nível mais alto de um perfil e o que o departamento de fiscalização de Valve faz com a mesma cláusula quando a conta pertence a um comerciante comum.\n\nO que uma exploração agrícola tem de comprar em primeiro lugarQuanto custa um nível em conjuntosOs dois lados da secretáriaQuem controla a economia das cartas\n$5.00É necessário efetuar uma compra na loja antes de uma conta poder receber qualquer cartão — Página de apoio da Valve\n13,876Jogos no Steam que emitem cartas colecionáveis, com 99,971 tipos distintos de cartas\n694,673Conjuntos completos de cartas atualmente em stock em 91 bots de negociação cotados em bolsa\n1,389,346Limites de retirada de cartões de conta e de jogo que o stock já consumiu, no mínimo\n$9.99Preço mediano de um jogo de cartas — o conjunto completo é vendido por um valor mediano de $0.74\n97,114Membros do grupo de troca de cartas cuja lista de moderadores inclui um funcionário com o código Valve — § 08\n01 — O processo\nO que é, na verdade, uma quinta, passo a passo\n\nDescrito apenas com base na documentação da própria ferramenta e nas páginas de apoio da Valve. Nada nesta secção é inferido, nem é contestado por nenhuma das partes.\n\nPasso 1\nComprar em\n\nA conta não deve ser limitado. A página de apoio do Valve impede que as contas com restrições «Participar no Mercado Steam», de \"Troca de itens da comunidade Steam (cartas colecionáveis, pacotes de reforço, gemas, etc.)\" e de «Ganhar Steam níveis de perfil (bloqueado no nível 0) e cartas colecionáveis». A entrada custa dinheiro: \"Terá de gastar, pelo menos, $5.00 USD na loja Steam.\"\n\nPasso 2\nComprar jogos\n\nAs cartas só se obtêm nos jogos que se possui. «É necessário ser o proprietário do jogo na tua conta Steam para teres direito a receber quaisquer cartas que sejam distribuídas a partir dele. A partilha familiar não equivale a propriedade e não conta.» As rotas gratuitas também estão encerradas: «Os jogos pagos que tenhas obtido gratuitamente durante uma promoção não podem ser usados para obter cartas», e «Não é possível obter cartas em jogos F2P sem gastar dinheiro nesses jogos.»\n\nPasso 3\nEm espera\n\nA ferramenta inicia sessão na conta na rede Steam em modo sem interface gráfica, \"analisa os teus crachás\", cria a lista de títulos que podem ser cultivados e inicia \"jogar um jogo elegível e verificar periodicamente se o jogo já foi totalmente explorado.\" Descrição do mecanismo feita pelo seu responsável: este «não faz mais nada do que indicar Steam que estamos a jogar um determinado jogo.»\n\nPasso 4\nAs gotas acabam\n\nCada título é finito. «Cada jogo tem um número fixo de cartas que se podem obter. Assim que as obtiveres todas (cerca de metade do conjunto completo), o jogo deixa de ser uma boa opção para farmar.» Uma quinta que queira continuar a produzir tem de continuar a comprar títulos. A oferta de cartas é limitada pelas compras — por design e a favor de Valve.\n\nPasso 5\nLevantar dinheiro\n\nA carta sai por uma de três vias: é vendida no Mercado da Comunidade, trocada ou transformada em gemas. Cada uma destas opções constitui uma transação no Mercado de Subscrições ou uma troca, e o § 3.D reserva o direito de cobrar: \"Valve pode cobrar uma comissão pelas transações realizadas num Mercado de Subscrições.\" É este o passo que faz com que tudo isto constitua uma violação — ver 05.\n\nFontes, lidas e citadas textualmente no 2026-09-22: Steam Suporte — Contas de utilizador limitadas ↗ · ArchiSteamFarm Perguntas frequentes ↗ · Valve — Steam Perguntas frequentes sobre as cartas colecionáveis ↗ · Steam Contrato de Subscrição ↗ arquivado 2026-09-24 ↗. O símbolo ArchiSteamFarm é utilizado ao longo desta página como um instrumento de medição, e não como um arguido; a própria documentação do símbolo afirma claramente que «A ASF não está autorizada pela Valve».\n\n02 — A escala\nAntes de uma exploração agrícola ganhar um cêntimo, já pagou Valve\n\nUma vez que uma conta com restrições não pode receber um cartão, todas as contas de uma exploração têm de ser libertadas dessas restrições antes de começarem a produzir. O valor mínimo é publicado e é cobrado por conta.\n\nDimensão da exploração agrícola\tDe onde vem esse número\tValor mínimo de compra na loja para que sejam elegíveis para o cartão\n10 contas\tO limite máximo recomendado pela ASF — «com base nas diretrizes internas Valve, bem como nas nossas próprias sugestões»\t$50\n100–200 contas\tLimite técnico na mesma secção de perguntas frequentes: «É possível executar até 100-200 bots com um único IP e uma única instância do ASF»\t$500 – $1,000\n120 contas\tProcesso de aplicação de sanções n.º 3 abaixo — banido permanentemente\t$600\n170 contas\tCaso de aplicação de sanções n.º 2 abaixo — banido permanentemente durante os Saldos de Inverno de 2017\t$850\n1,000 contas\tProcesso de aplicação da lei n.º 1 abaixo — comércio proibido\t$5,000\n5,000 contas não verificado\tBalança de operador comunicados no âmbito desta investigação e não verificados de forma independente — ver a nota sobre a origem\t$25,000\n10,000 contas não verificado\tBalança de operador comunicados no âmbito desta investigação e não verificados de forma independente — ver a nota sobre a origem\t$50,000\n\nAs duas últimas linhas são os únicos dados desta página que se baseiam num relatório não confirmado, em vez de num documento — estão assinaladas na tabela e explicadas em a nota sobre a origem dos produtos, e nada mais aqui depende deles. A coluna da direita baseia-se exclusivamente no limiar de $5.00 USD publicado pela Valve e em mais nada. Trata-se de um piso, não se trata de uma estimativa do custo de uma quinta nem do que Valve rendeu: exclui os jogos, que têm de ser adquiridos e não podem ter sido obtidos gratuitamente numa promoção, e exclui os cerca de 15% que o Mercado Comunitário retém quando as cartas são vendidas. Nesta página não é apresentado qualquer valor relativo às receitas.\n\nE a Valve definiu ela própria o preço de uma distribuição de cartões. A sua secção de perguntas frequentes sobre as cartas colecionáveis apresenta a taxa de conversão do modelo «free-to-play» em dólares:\n\n\"Os jogos gratuitos distribuem cartões de jogo com base nas compras que fazes no jogo.\" Por cada $9 USD gastos (valor aproximado) Desde o início da versão beta do Steam Trading Card, receberás uma carta.\"\n\n— Valve, Steam Perguntas frequentes sobre as cartas colecionáveis ↗ · verificado literalmente 2026-09-22\n\nUma carta colecionável não é um brinde com o qual a plataforma tenha prejuízo. É algo que Valve vende, a um preço Valve publicado — e depois cobra uma segunda vez para revender. É por isso que a descrição honesta de uma «fábrica de cartas» não é parasita. É comprador grossista.\n\nQual é, de facto, o tamanho do objeto que está a ser comprado\n\nTudo, desde aqui até ao final desta secção, é medido, não relatado. O recenseamento de cartões baseia-se na lista de preços de crachás publicada pela Steam Card Exchange; os preços dos próprios jogos provêm da API da loja da própria Valve; o inventário de bots provém de um diretório público de bots que qualquer pessoa pode aceder. Todos os três foram consultados em 2026-09-22 e os cálculos estão apresentados na íntegra em secção 08.\n\n13,876Jogos em que se distribuem cartas\n99,971Tipos de cartões distintos\n5 · 6 · 15Cartas por conjunto: mínimo, mediana, máximo\n$0.74Preço mediano de um conjunto completo\n$23,586.57Um de cada conjunto à venda\nQual é a dimensão de um conjunto?\n\n13,876 jogos por cartão do conjunto. Valve atribui cerca de metade deles a uma única conta.\n\n0\n1,250\n2,500\n3,750\n5,000\n5\n6\n7\n8\n9\n10\n11\n12\n13\n14\n15\nQuanto custa a licença\n\nPreço de tabela dos mesmos jogos na loja do Steam, em dólares americanos.\n\n0\n1,000\n2,000\n3,000\n4,000\n<$1\n$1-3\n$3-5\n$5-10\n$10-20\n$20-40\n$40+\nO que o conjunto final devolve\n\nPreço de mercado do conjunto completo desses mesmos jogos.\n\n0\n1,500\n3,000\n4,500\n6,000\n<$0.50\n$0.50-1\n$1-2\n$2-5\n$5-10\n$10+\n\nSe compararmos o segundo e o terceiro gráficos, a estrutura da transação torna-se visível sem necessidade de cálculos: os jogos agrupam-se na casa das dezenas de dólares, enquanto os conjuntos a que dão origem se agrupam abaixo de um dólar. Ambos representam contagens dos mesmos 13,876 jogos, na mesma unidade do eixo, pelo que a comparação é entre duas alturas e não entre duas escalas.\n\nEssa é a vertente da oferta. A vertente da procura é a parte em que Valve não precisa de fazer publicidade, porque já está à vista de todos: um único diretório aberto de bots de troca de cartões apresenta Neste momento, existem 91 bots com 694,673 conjuntos completos em stock. Sem necessidade de iniciar sessão, sem extração de dados de um mercado online, sem dados privados — o valor das ações está impresso na página, ao lado do nome de cada bot.\n\nTransforma essa ação na única unidade que importa aqui. A regra do próprio Valve: «Na maioria dos jogos, será distribuído um número de cartas equivalente a cerca de metade do número de cartas do baralho desse jogo… Vais ter de recolher a outra metade do conjunto junto de outros membros da comunidade.\" Uma conta nunca consegue terminar um conjunto apenas jogando. São necessárias, no mínimo, duas contas, cada uma com esse jogo, e cada uma a esgotar a sua cota de «drops» (uma por jogo). Os «drops» não se regeneram.\n\n694,673Conjuntos em stock, 91 bots públicos\n3,473,365Cartas, com um mínimo de 5 cartas\n1,389,346Quotas de descarte consumidas, mínimo\n2,602Contas que possuem um único jogo, maior densidade de bots\nOnde se encontram os conjuntos 694,673\n\nOs doze maiores dos 91 «card bots» cotados em bolsa, por número de conjuntos completos em stock. Os dez maiores detêm 248,115 conjuntos no total — 35.7% de tudo o que está na tabela.\n\n0\n11,250\n22,500\n33,750\n45,000\nCard Supply #4 (High)\nN!vq's Leveling (High)\nAlice [BOT] LEVEL-UP RARE SETS\nN!vq's Leveling (Low)\nDisco Lite Level Up\nN!vq's Leveling (Mid)\nbaty131store.net | Level Up\nKitten - Supreme\nArashirn | Level Up\nSH (Junior) Level Up\nDuobot.com - Overstock\nlvlupbot.com - godlike\n\nCada uma dessas 1,39 milhões de quotas pertencia a uma conta que possuía o jogo, tinha ultrapassado o limite de $5.00 e nunca mais poderá gerar essas quotas novamente. Isto é stock não vendido em noventa e um bots. Não é uma medida do mercado; é uma medida do que resta depois do mercado.\n\nO último valor refere-se a uma divisão em compartimentos, não a uma contagem de utilizadores. Um bot regista 14,310 conjuntos extraídos de apenas 11 jogos, pelo que pelo menos um desses jogos está representado por 1,301 conjuntos, o que corresponde a, pelo menos, 2,602 contas distintas que adquiriram esse jogo. É o número mais baixo que a aritmética permite, e diz respeito a um bot em noventa e um.\n\nO que este piso diz e o que não diz\n\nEstes bots compram cartas tanto a jogadores comuns como a «farms» — as taxas de compra que publicam são o objetivo deste diretório. Portanto, os 1,39 milhões de licenças não correspondem ao número de contas detidas por explorações agrícolas. Trata-se de um conjunto de itens que podem ser obtidos uma vez por conta e uma vez por jogo, que foram gastos algures no Steam e acabaram por ficar, por não terem sido vendidos, no stock comercial. Quer a conta por trás de cada um fosse uma conta de farm ou a de um adolescente a limpar a sua página de emblemas, isso não altera o que o Valve recebeu: o desbloqueio do $5.00, a licença do jogo e uma comissão do Mercado em cada transação — não 15%, mas sim 15% ou os dois valores mínimos de um cêntimo, consoante o que for maior, que, num cartão cujo preço é indicado em cêntimos, é, de longe, o maior. A conta está em a tabela de taxas abaixo. É esse o objetivo desta página, e não se trata de uma queixa contra os agricultores: a mesma conduta pela qual a Valve cobra uma taxa é a conduta que cita, palavra por palavra, quando banir definitivamente um utilizador por «uso comercial».\n\nEste valor também representa um limite mínimo num segundo sentido. Considera apenas as ações que são colocados à venda e não vendidos hoje sobre os bots que optar por estar num diretório público. Tudo o que já foi vendido, tudo o que está em posse privada e todos os bots que não constam no diretório são excluídos.\n\nE a agricultura não se sustenta com os preços praticados pela Valve'\n\nA objeção óbvia é que uma «farm» compra jogos baratos para criar cartas caras. A própria API da loja da Steam diz o contrário. Dos 13,876 jogos que incluem cartas, os preços foram determinados para 13,713; 12,918 são títulos pagos com um preço de tabela mediano de $9.99. O conjunto acabado é vendido, em média, por $0.74. São necessárias duas licenças por conjunto. Assim, o custo médio de um conjunto ronda aproximadamente $19.98 licenças de jogo para produção e devoluções $0.74.\n\nMedido em 2026-09-22\tValor\tO que resolve\nPreço médio de tabela, jogo com cartas\t$9.99\tA licença é a parte mais cara da transação, não o cartão\nJogos com um preço igual ou inferior a $4.99\t3,665 (28.4%)\tAté a cauda mais barata é mais cara do que o conjunto que dela resulta\nO jogo de cartas mais barato da loja\t$0.99\tDuas licenças, $1.98, para um conjunto que normalmente é vendido por menos de $1.30\nJogos cujo conjunto é vendido por um preço superior ao do próprio jogo\t323 de 12,918 (2.5%)\tA arbitragem de cartões em relação aos preços de tabela da Steam ocorre em 1 jogo em cada 40\nTítulos «free-to-play» incluídos no censo\t795\tE Valve fixa o preço de cada um dos seus lançamentos em $9 de gastos no jogo\n\nO que encerra a questão económica a favor de Valve e contra a versão habitual. Aos preços que a própria Valve cobra, A «cultivação de cartões» é uma atividade deficitária que só funciona com licenças adquiridas a um preço inferior ao preço de tabela da Steam — pacotes, preços regionais, revenda de chaves. Os cartões são o que resta. A compra é o acontecimento. E a compra ocorreu em Steam.\n\nO que a quinta realmente sustenta\n\nJuntando todas as peças, a exploração agrícola deixa de parecer algo que Valve tolera e passa a parecer algo de que Valve necessita. Cada insumo fornecido pela exploração agrícola é um produto que Valve regista ou fatura. Acompanhe uma conta de bot até ao seu destino:\n\nUma conta criada artificialmenteum «cliente grossista», e não uma fuga de informação\nVendas de jogos\n\nCompra os títulos que acumula — desde os jogos de cartas 13,876 até aos jogos de baixa qualidade $0.50 — porque as cartas só aparecem nos jogos que possui.\n\n\"Online\" e tempo de brincar\n\nFaz com que eles fiquem inativos para que deixem cair cartas, alimentando os números relativos ao número de jogadores simultâneos e às horas jogadas que Valve cita como «envolvimento» — a estatística exata a que a secção § 4.C se refere como «tempo de jogo falso».\n\nInscrições\n\nÉ necessário ultrapassar o limite de $5.00 da conta antes de poder receber um cartão — um registo de compras em lojas físicas Valve por conta.\n\nDinheiro na carteira e taxas\n\nCada cartão que vende passa pelo Market, onde a comissão pode chegar a 66.7% num cartão de baixo valor e os rendimentos ficam bloqueados na Carteira Steam.\n\nRelações públicas de nível 0\n\nOs emblemas e os níveis Valve só existem porque foram criados conjuntos — e o topo dessa classificação é ocupado por bots (ver § 03).\n\nSe retirarmos a exploração, todos os números acima diminuem — o jogo vendeu menos exemplares, a componente «online» foi menor, a conta nunca foi registada, a taxa nunca foi cobrada e o nível nunca foi atingido. É por isso que uma regra que proíbe a automatização coexiste com milhões de contas automatizadas: a proibição é a opção e a atividade é a receita.\n\nE o próprio levantamento de dinheiro representa uma perda de valor Valve — paga-se imposto duas vezes\n\nA carta não é o fim do ciclo. A própria mecânica do Valve permite que uma carta seja esmagada até joias, e as gemas devem ser utilizadas para criar pacotes de cartas — mais três cartas — que são vendidas ou destruídas novamente. Cada etapa corresponde a uma transação no Mercado ou a uma conversão, e cada uma é tributada. A direção desse ciclo decorre do limite mínimo de taxa calculado abaixo e não requer nenhum modelo externo: todas as cartas vendidas no seu âmbito são entregues pelo menos dois cêntimos, em cartões cuja transação custa entre três e cinco, pelo que cada volta da manivela rende menos do que o valor inicialmente investido. Este ciclo destrói o valor virtual e obriga a que novas transações, sujeitas a comissões, o substituam. Não é aqui apresentado qualquer valor relativo à dimensão dessa perda — o retorno por conjunto depende das taxas de gemas e das probabilidades dos boosters, que esta investigação não mediu.\n\nCartão colecionávelitens obtidos no jogo que se possui\n→\nPedras preciosascartão danificado, taxa cobrada\n→\nPacote de reforçogemas gastas na criação\n→\n3 novas cartasvendido no Market, com comissão cobrada\n↶\n\nAqui apenas se referem as mecânicas, que são próprias do Valve — as cartas transformam-se em gemas, as gemas servem para criar pacotes de cartas, os pacotes de cartas proporcionam cartas —, todas documentadas no FAQ das Cartas Colecionáveis do Steam, sendo cada passo um evento de Mercado sujeito a tributação. Origem das mecânicas do ciclo: Valve, Steam Perguntas frequentes sobre as cartas colecionáveis ↗.\n\nIsto não é apenas um momento. É um setor com uma estrutura que se estende por vários anos.\n\nUm único instantâneo pode ser um acaso. Por isso, o diretório público dos bots de cartões foi consultado uma vez por cada promoção sazonal Steam, através do Wayback Machine, de 2022 a 2026 — o stock fixo que os bots tinham e as mesmas contas, promoção após promoção. A economia não surge e desaparece; persiste, com um núcleo estável de operadores, e atingiu o seu pico em mais de três milhões de conjuntos completos em stock durante a promoção de Inverno de 2023 — cerca de um terço de um milhão de chaves do TF2 de valor armazenadas num determinado momento, num único diretório.\n\nConjuntos completos de cartas disponíveis no diretório público do bot, à venda por Steam\n\nUm instantâneo do Wayback de steam.supply/CardBots por promoção sazonal. Passe o cursor para ver o valor em chaves do TF2 à taxa desse instantâneo.\n\n0.0M\n0.9M\n1.8M\n2.6M\n3.5M\nA’22\nS’23\nW’23\nS’24\nW’24\nS’25\nS’26\n401Contas de bots distintas detetadas nas vendas\n59Presente em 5 ou mais das 7 vendas — o núcleo estável\n16Esteve presente em todos os 7 leilões, entre 2022 e 2026\n3,22 milhõesConjuntos Peak em stock (Inverno de 2023) ≈ $570k–790k em chaves\nComo se apresenta a tabela de distintivos de vendas quando vista do topo\n\nA procura corresponde à oferta. No setor público Escalão de emblemas da Promoção de Verão de 2024 arquivado 2026-07-16 ↗, a conta número um tinha criado o emblema de venda 1,740,645 vezes — 1,74 milhões de conjuntos de dez cartas, 17,4 milhões de cartões integrados numa única decoração de perfil. Ao preço de mercado da própria venda ($0.50 por conjunto), isso equivale a ~$870,000 do valor do cartão; comprado da forma como é realmente comprado — chaves do TF2 trocadas para subir de nível bots a cerca de 7,6 conjuntos por chave — é ~229,000 teclas, cerca de $410,000–$570,000 em termos reais. A conta número dois: 552,000 define o intervalo ~$130,000–181,000. Nenhum ser humano joga por isto. É comprado, e cada etapa da compra é uma transação que Valve liquida.\n\nMétodo e limites: o stock total é somado entre os bots que cada instantâneo apresenta; o número O número de bots por instantâneo não é comparável entre as vendas, uma vez que alguns instantâneos mostram apenas os bots em destaque e outros o diretório completo; por isso, o stock é interpretado como um valor mínimo do que estava visível, e não como um recenseamento. Os valores das chaves utilizam a taxa mediana de conjuntos anunciados por chave de cada instantâneo e uma chave TF2 de $1.79–$2.49. A persistência é feita através do SteamID64 entre instantâneos. Os instantâneos de 2021 utilizavam um layout de página mais antigo e não foram incluídos. Dados: farm-economy-timeline.json; níveis de emblemas do SteamLadder; preços definidos pelo Steam Card Exchange (instantâneos do Wayback no momento da venda, $0.05 por cartão).\n\nE essa mesma frota continua lá quando não há nenhuma promoção a decorrer\n\nAs duas imagens acima não correspondem a duas populações. Trata-se de uma única frota, fotografada em momentos diferentes. O diretório mencionado no início desta secção foi lido num um dia normal, sem nenhuma promoção sazonal em curso — 2026-09-22 — e mesmo em repouso mantinha-se 91 bots e 694,673 conjuntos completos: da ordem de 186,000 teclas do TF2, $334,000–$464,000 do valor da carta, inativas entre vendas. Esse é o nível mínimo que a operação mantém quando não há atividade.\n\nE trata-se da mesma operação. Identificada pelo SteamID64, 87 desses 91 bots inativos — 96% — também aparecem nos sete instantâneos de vendas acima, dezasseis em cada uma delas. O diretório não é uma banca que abre para a venda e fecha a seguir; é um inventário comercial permanente que esta mesma frota aumentou até atingir 3,22 milhões de conjuntos no pico do Inverno de 2023 e nunca desce a zero. Uma promoção é quando se vendem produtos. Também existe durante o resto do ano.\n\nO diretório de repouso, bot a bot\n\nCada quadrado representa um bot no diretório em 2026-09-22, que fica destacado se também aparecer nas sete imagens de vendas. 91 é o número que constava no diretório nesse dia, não o tamanho da frota — Aparecem 401 contas distintas nos resumos de vendas, e o diretório apresenta uma amostra diferente em dias diferentes.\n\nVisto em leilões anteriores (87) Novidades desde o último instantâneo (4)\n\nA leitura de referência sem promoção é de 2026-09-22 a partir do mesmo diretório público, sem necessidade de início de sessão. O valor de repouso utiliza a taxa de conjuntos por chave anunciada por cada bot e a faixa de chaves $1.79–$2.49 acima. A sobreposição é feita com base no SteamID64 em relação aos sete instantâneos de promoção. Como a lista de produtos em destaque difere da lista completa consoante o instantâneo, esta compara o stock e a identidade, e não o número de utilizadores. Cálculos em secção 08.\n\n03 — A escada\nO outro produto é o número que aparece ao lado do teu nome\n\nAs cartas são a matéria-prima. O produto final é de nível Steam, e Valve define o seu preço por conjuntos.\n\n100Steam Nível\nNível alvo — arraste ou utilize as setas do teclado\nPreço de um conjunto completo, em dólares americanos\n\n$0.20 é o conjunto completo mais barato do recenseamento, $0.74 a mediana e $1.70 a média. O valor refere-se apenas às cartas — nunca aos $5.00 desbloqueios nem às licenças do jogo.\n\n55,000É necessário ter XP\n550Conjuntos completos consumidos\n110Jogos para ter, cultivando-os tu mesmo\n$407.00Custo dos cartões a esse preço\n1,100Subsídios por queda queimados, mínimo\n$5,500.00$5.00 desbloqueia, se nenhuma conta for reutilizada\nConjuntos completos consumidos, nível 1 a 1,000\n\nUm objeto artesanal tipo crachá = um conjunto completo = 100 XP. Cada nível dentro de um bloco de dez custa mais 100 XP do que o bloco imediatamente abaixo.\n\n0\n12,625\n25,250\n37,875\n50,500\n1\n250\n500\n750\n1000\n667\n550 sets\n\nUm nível não é um elemento decorativo que o Valve ignora. Está associado à conta. De acordo com as Perguntas Frequentes sobre Cartas de Jogo do próprio Valve, sobre o que se ganha ao criar um emblema: \"100 XP, o que pode aumentar o teu nível Steam. Se o teu Nível Steam aumentar, o limite do tamanho da tua lista de amigos será aumentado em cinco, e, possivelmente, irás desbloquear a possibilidade de personalizar o teu perfil com vitrines.\" E quanto aos pacotes de cartas: «O teu nível Steam aumenta a tua taxa de obtenção de pacotes de reforço: Nível 10: +20%… Nível 50: aumento de +100% na tua taxa de obtenção (ou seja, a taxa duplicou).»\n\nAssim, o nível dá acesso a duas funcionalidades Valve: controla o número de pessoas com quem podes ser amigo e a velocidade a que as cartas gratuitas entram no teu inventário. O segundo fator acumula-se — quanto mais conjuntos tiveres consumido, mais rapidamente a plataforma te fornece mais material. Valve integrou o ciclo de reinvestimento no produto.\n\nA taxa de câmbio é fixa e é publicada. A criação de um emblema consome um conjunto completo e rende 100 XP; «Podes criar um conjunto para o mesmo jogo, no máximo, cinco vezes.» O custo em XP por nível aumenta a cada dez níveis. Isso resulta no seguinte, e nada aqui é uma estimativa:\n\nSteam Nível\tConjuntos completos que consome\tJogos que tens de ter para os criares tu mesmo\tNo valor mais baixo de sempre ($0.20)\tNo conjunto mediano ($0.74)\tEscala\n10\t10\t2\t$2.00\t$7.40\t\n50\t150\t30\t$30.00\t$111.00\t\n100\t550\t110\t$110.00\t$407.00\t\n200\t2,100\t420\t$420.00\t$1,554.00\t\n500\t12,750\t2,550\t$2,550.00\t$9,435.00\t\n667\t22,579\t4,516\t$4,515.80\t$16,708.46\t\n\n667 não é uma hipótese. É o nível mais alto a que um único bot no diretório público anuncia que pode levar um cliente, entre os 33,359 conjuntos que possui em 6,117 jogos. A quarta coluna corresponde ao mesmo preço da tabela comparado com o conjunto completo mais barato em qualquer parte do recenseamento; a quinta, com a mediana. Ambos são preços de mercado apenas para as cartas e excluem totalmente o desbloqueio $5.00 e as licenças dos jogos.\n\nComo é que a curva foi verificada, uma vez que o Valve não a publica?\n\nValve indica a taxa de distintivos («Cada 100 XP dá-te um nível adicional Steam») e, em seguida, faz uma cobertura — «(pelo menos para começar)» — sem publicar a escalada. A curva utilizada acima é a padrão, na qual cada nível dentro de um bloco de dez custa mais 100 XP do que o bloco abaixo dele. Foi verificada com base no diretório, em vez de ser assumida: para cada bot cujo máximo anunciado seja limitado pelo seu stock, em vez do limite de cinco criações por jogo, o nível calculado a partir desta curva corresponde exatamente ao nível anunciado pelo bot — 541 contra 541, 494 contra 494, 464 contra 464. Nos casos em que o limite máximo se aplica, o valor calculado fica alguns níveis acima, o que é precisamente o que um limite máximo que também depende da profundidade do plantel por jogo deve fazer. Não se fazem afirmações sobre a curva acima do nível 667.\n\nBasta ler a tabela ao lado da secção 02 para perceber como funciona o negócio. Para colocar uma conta no nível 500, é necessário reunir 12,750 conjuntos completos. Cada um desses conjuntos exigiu, no mínimo, as quotas de drop de duas contas; cada uma dessas contas tinha ultrapassado o portão $5.00 e possuía o jogo. Um número de vaidade na parte superior de um perfil assenta em, pelo menos, 25,500 quotas de gotas gastas que se encontram por baixo dele. Valve não vai perder essa transação. Valve é a contraparte em cada uma das suas componentes.\n\n04 — As estatísticas\nA cláusula não descreve a agricultura de forma vaga. Enumera-a.\n\nO § 4.C não é uma frase geral contra os bots. Os exemplos nele enumerados indicam, um a seguir ao outro, os dois elementos que uma «card farm» produz.\n\n«Não é permitido utilizar qualquer tipo de scripts, bots, macros ou outros sistemas não controlados por seres humanos («Automatização») para interagir com os Conteúdos e Serviços no Steam de qualquer forma, incluindo, entre outros:\n\nAutomatizar o processo de criação de contas Steam,\nFalsificar estatísticas de jogo (por exemplo, vitórias ou derrotas exageradas, XP, tempo de jogo),\nGanhar recompensas ou avançar sem uma contribuição genuína do utilizador,\nParticipar em sistemas de avaliação (como revisões por pares ou «supervisão») através de meios automatizados, incluindo influenciar resultados ou denunciar utilizadores por meio de ações programadas, em vez de um julgamento informado.»\n— Steam Contrato de Subscrição § 4.C ↗ arquivado 2026-09-24 ↗ · extraído e citado literalmente 2026-09-22\n\"…hora de brincar\"\n\nAs horas de inatividade não são horas fantasmas. A secção de perguntas frequentes da ASF responde diretamente à questão — «Porque é que o tempo de jogo dos jogos obtidos através do ASF não aumenta?» — com: «Sim, mas não em tempo real. O Steam regista o tempo de jogo em intervalos fixos e programa a atualização... normalmente é atualizado a cada 30 minutos, mais ou menos.»\n\nEssas horas ficam registadas nos registos da Valve, nas páginas da loja da Valve e nas contagens de jogadores simultâneos que a Valve publica por conta própria Steam Gráficos ↗ arquivado 2026-09-23 ↗. Nesses números, uma conta inativa é indistinguível de uma conta ativa. Os números de envolvimento que a plataforma divulga são calculados com base numa população que inclui, segundo as próprias regras da plataforma, contas que não estão ativas.\n\n«… sem um contributo genuíno dos utilizadores»\n\nEssa é uma definição de «idled card drop», redigida por Valve. É também uma definição do Nível Steam, do crachá, da elegibilidade para pacotes de reforço e dos XP de perfil que o acompanham — o FAQ da ASF confirma a ferramenta \"mantém a possibilidade de receber pacotes de reforço\", porque faz o início de sessão da mesma forma que o cliente oficial.\n\nAssim, o sistema de recompensas e o ato proibido constituem um único mecanismo visto de dois pontos de vista. Valve concebeu a recompensa de forma a que fosse gerada pelo tempo, e não pela habilidade, e depois redigiu uma cláusula que proibia a geração de recompensas por qualquer meio que não fosse o tempo gasto por uma pessoa.\n\n05 — A armadilha da utilização comercial\nCada saída a partir de um cartão de acesso a uma área cultivada é uma saída proibida pela licença — e a Valve cobra uma taxa à saída\n\nEsta é a parte que não pode ser resolvida através da «exploração responsável». A licença destina-se a uso pessoal e não comercial, e um cartão só passa a valer a pena ser explorado no momento em que deixa de ser de uso pessoal.\n\n§ 2.A — a licença\n\n\"Valve concede, por meio do presente, e o utilizador aceita, uma licença e um direito não exclusivos para utilizar o Conteúdo e os Serviços para o seu uso pessoal e não comercial (exceto nos casos em que a utilização comercial seja expressamente permitida no presente documento ou nos Termos de Subscrição aplicáveis).\"\n\n§ 2.G — a restrição\n\n«não tem direito a: … (iii) explorar o Conteúdo e os Serviços, ou qualquer parte dos mesmos, para quaisquer fins comerciais, salvo nos casos expressamente permitidos noutra parte do presente Acordo (incluindo quaisquer Termos de Subscrição ou Regras de Utilização).\"\n\n§ 3.D — a taxa\n\n\"Valve pode cobrar uma comissão pelas transações realizadas numa Plataforma de Subscrições. Quaisquer taxas ser-lhe-ão comunicadas antes da conclusão da transação.»\n\nSe lermos os três em conjunto, a posição fica encerrada\n\nUma carta que é guardada não tem qualquer valor para uma quinta. Uma carta que é vendida, trocada ou transformada em gemas foi utilizada para gerar valor — e a Valve referiu, na sua própria carta de aplicação da política, como designa isso: foi comunicado ao operador de 170 bots que a conta \"foi utilizado para a recolha ilegal de cartões colecionáveis no Steam, bem como para atividades relacionadas e não apenas comerciais.\" Nesse caso, os cartões chegaram ao mercado. As vendas foram concluídas. A comissão foi cobrada. A proibição surgiu só depois.\n\nA taxa nessa porta não é de 15%. Numa carta «farmed», atinge dois terços.\n\n§ 3.D reservas «uma taxa». Nos cartões que uma exploração agrícola produz efetivamente, essa taxa não tem nada a ver com o valor anunciado de ~15%. O Mercado Comunitário cobra uma 5% Steam de taxa de transação e 10% de taxa de jogo, cada uma com um valor mínimo de $0.01 (Perguntas frequentes do Community Market do Valve). Numa ficha com o preço de um cêntimo, esses pisos são o preço: o comprador paga três cêntimos, dois dos quais correspondem a comissões. O arredondamento para baixo transforma o valor nominal 15% numa taxa efetiva que ascende a 66.7% exatamente onde se situa o mercado das cartas — alguns cêntimos por carta.\n\nComissão efetiva numa venda no Mercado Comunitário, com base no preço pedido pelo vendedor\n\n5% Steam + 10% jogos, cada um com um mínimo de $0.01. A faixa sombreada corresponde ao intervalo em que as cartas de coleção são efetivamente trocadas — aproximadamente $0.03–$0.05 por carta.\n\n0%\n10%\n20%\n30%\n40%\n50%\n60%\n70%\ncards\n$0.01\n$0.10\n$0.20\n$0.30\n$0.40\n$0.50\n66.7%\nO vendedor pretende\tSteam 5% (mín. $0.01)\tJogo 10% (min $0.01)\tO comprador paga\tTaxa combinada\n$0.01\t$0.01\t$0.01\t$0.03\t66.7%\n$0.03\t$0.01\t$0.01\t$0.05\t40.0%\n$0.05\t$0.01\t$0.01\t$0.07\t28.6%\n$0.08\t$0.01\t$0.01\t$0.10\t20.0%\n$1.00\t$0.05\t$0.10\t$1.15\t13.0%\n\nA taxa de 10% do jogo reverte para a aplicação que emitiu o cartão; a taxa de 5% pertence a Valve e, nos títulos próprios de Valve e nos itens do inventário base, a totalidade da taxa reverte para Valve. Seja como for, o dinheiro sai do «farmer» — a venda de um cartão de três cêntimos rende um cêntimo e faz perder dois. Multiplique isso pelas centenas de milhares de vendas de cartões com valor inferior a cinco cêntimos que uma «farm» gera e «a taxa que Valve pode cobrar» é o modelo de negócio, não uma nota de rodapé. Fonte: Steam Perguntas frequentes sobre o Mercado Comunitário — Taxas ↗ arquivado 2026-09-21 ↗, lida-se 2026-09-22; a curva é aritmética com base nessas duas taxas publicadas e nos seus limites mínimos $0.01.\n\nNão há nenhuma configuração da ferramenta que escape a isto. Pode ser utilizada por uma única pessoa, numa única conta, com total moderação — e, no momento em que essa pessoa vender um único cartão obtido de forma abusiva para obter fundos na carteira, a mesma sanção prevista no § 2.G aplica-se-lhe tal como se aplica ao operador de dez mil. A Valve reservou, portanto, uma violação que poderia invocar contra praticamente todos os vendedores de cartas no seu próprio mercado, mas recusou-se a invocá-la contra praticamente todos eles. Uma regra aplicada dessa forma não é uma regra. É uma opção. A questão que esta exposição coloca não é por que razão os «card farmers» são tolerados; mas sim por que razão essa mesma opção é aplicada contra um utilizador isolado que vende um cartão, enquanto a economia comercial de cartões que esses cartões alimentam — os serviços de troca, os bots de subida de nível, os vendedores a granel — continua a funcionar abertamente, sendo um dos seus maiores grupos moderado por um funcionário Valve (§ 08). A violação é reservada ao pequeno detentor e ignorada no caso da máquina.\n\n06 — Histórico de execução\nSem aviso prévio, em ondas, e vai descendo pelo número de telefone\n\nValve incluiu a cláusula relativa ao poder de rescisão sem pré-aviso no próprio contrato, logo a seguir à cláusula relativa à automatização.\n\n\"Valve pode restringir ou encerrar a(s) sua(s) conta(s) ou uma subscrição específica devido a qualquer conduta ou atividade que seja ilegal, constitua uma fraude ou automação, ou viole as Regras de Conduta Online Steam. O utilizador reconhece que a Valve não é obrigada a notificá-lo antes de rescindir a(s) sua(s) Subscrição(ões) e/ou Conta.\"\n\n— Steam Contrato de Assinante § 4.D ↗ arquivado 2026-09-24 ↗ · verificado literalmente 2026-09-22\n\n1,000+ bots · banidos do comércio. «Parece que esta conta foi utilizada para gerir uma rede de contas de bots. A utilização de bots constitui uma violação do Acordo de Subscrição Steam.»\n\nMais de 170 bots · banidos permanentemente, Promoção de Inverno de 2017. «Esta conta foi utilizada para a recolha ilegal de cartões colecionáveis no Steam, bem como para atividades relacionadas, não apenas comerciais. A conta foi bloqueada definitivamente e o Apoio ao Cliente Steam não pode prestar assistência adicional sobre esta questão.»\n\nMais de 120 bots · banidos permanentemente. «Esta e outras contas foram utilizadas para sobrecarregar a nossa infraestrutura de rede, o que constitui uma violação das regras de conduta online Steam.»\n\n— Steam Mensagens de apoio reproduzidas na ArchiSteamFarm FAQ, na secção «Alguém foi banido por causa disso?». Fonte ↗ · verificado literalmente 2026-09-22\nCaso 4 — junho de 2025, VAC proibições relativas ao CS2 em inatividade\n\nUm episódio posterior aos três acima referidos está registado no próprio sistema de acompanhamento do projeto: as contas que apenas tinham deixado o Counter-Strike 2 em espera através da ferramenta receberam VAC proibições — do tipo anti-batota, não do tipo administrativo. A posição do responsável pela manutenção é que ficar inativo não pode causar isso, uma vez que «não faz mais nada do que dizer Steam que estamos a jogar um determinado jogo.» A causa é objeto de controvérsia. O facto de as contas terem sido banidas, não.\n\n— ArchiSteamFarm discussão n.º 3440, aberta a 26 de junho de 2025 ↗ · ler 2026-09-22\n\nComo uma conta principal deixa de existir\n\nNo mesmo tópico, um colaborador do projeto descreve a regra de aplicação: as contas podem ser banidas «em cadeia», se estiverem a utilizar o mesmo número de telefone — «pode tratar-se apenas de um ban VAC, que se propagou a contas “limpas” associadas à conta banida.»\n\nSteam Guard requer um número de telefone. As «farms» são criadas com base no número de telefone do operador. Assim, a ação coerciva não se limita às contas descartáveis: segue o identificador partilhado até à conta que contém a biblioteca, a lista de amigos e o inventário. Esse é o mecanismo descrito por um colaborador do projeto para explicar como uma única ação elimina a conta principal de um operador juntamente com a rede — e é por isso que a perda numa onda de fiscalização não se mede em $5 contas. (Descrito por um colaborador do projeto na discussão n.º 3440 do GitHub da ASF; não existe qualquer confirmação oficial Valve nem qualquer precedente formal registado.)\n\nO mesmo parágrafo, com cinco anos de diferença, de três agentes diferentes\n\nA cláusula que considera a comercialização uma violação — a utilização comercial de uma licença pessoal e não comercial — não se aplica apenas às explorações agrícolas. É o motivo habitual que a Steam invoca quando encerra uma conta por motivos de comercialização, e esse motivo é apresentado como um modelo padrão. Seguem-se três exemplos, publicados pelas pessoas que os receberam, com um intervalo de cinco anos, provenientes de três agentes diferentes identificados.\n\nMensagem do Suporte Steam em 29 de setembro às 19:56\n\n«A conta na qual está a escrever foi bloqueada por ter violado os termos do Contrato de Subscrição Steam. A conta foi identificada como sendo utilizada para fins comerciais com base em transações, denúncias da comunidade e outros fatores.»\n\nEste bloqueio é permanente e Steam O Serviço de Apoio não pode ajudá-lo mais nesta questão.\n\nUma vez que já fornecemos toda a informação de que dispomos, vou encerrar este pedido de ajuda. Tenha em atenção que não receberá mais respostas relativamente a esta questão.\n\nCumprimentos,\n«Hal»\n\nEste pedido de ajuda foi encerrado.\n29 de setembro de 2020. Publicado pelo destinatário com o seguinte comentário \"Adeus, RIP Trading.\" — @gergelyszabo94 ↗\nMensagem do Suporte Steam em 12 de julho às 22:41\n\n«A conta na qual está a escrever foi bloqueada por ter violado os termos do Steam Acordo de Subscrição. A conta foi identificada como sendo utilizada para fins comerciais com base em transações, denúncias da comunidade e outros fatores.»\n\nEste bloqueio é permanente e Steam O Serviço de Apoio não pode ajudá-lo mais nesta questão.\n\nUma vez que já fornecemos toda a informação de que dispomos, vou encerrar este pedido de assistência. Tenha em atenção que futuros pedidos de assistência relativos ao bloqueio da conta poderão ser encerrados sem resposta.\n\nSteam Apoio\n«Vido»\n\nEste pedido de ajuda foi encerrado.\n12 de julho de 2024, interface em português. O destinatário é um jogador profissional de CS2: «Já contactei o apoio técnico do Steam, mas só recebo respostas automáticas… Não consigo jogar no Faceit nem participar em jogos profissionais.» — @prcs25 ↗ arquivado 2024-07-15 ↗\nCitado pelo destinatário, r/steamsupport\n\n\"Olá, a conta na qual está a escrever foi bloqueada por ter violado os termos do Contrato de Subscrição Steam. A conta foi identificada como sendo utilizada para fins comerciais com base em transações, denúncias da comunidade e outros fatores.\n\nEste bloqueio é permanente e Steam O Apoio ao Cliente não pode ajudá-lo mais com esta questão.\n\nUma vez que já fornecemos toda a informação de que dispomos, vou encerrar este pedido de ajuda. Tenha em atenção que futuros pedidos de ajuda enviados relativamente ao bloqueio da conta poderão ser encerrados sem resposta.\n\nSteam Apoio\n«Sally»\n\nRecebido três vezes, em três pedidos distintos.\n29 de março de 2025. O autor não estava a contestar o bloqueio — a sua conta tinha sido roubada juntamente com o seu e-mail e estava a pedir acesso: «Não estou a perguntar sobre o banimento nem a contestá-lo; só quero ter acesso à minha conta do Steam… Valve deram-me exatamente esta resposta, copiada e colada em todos os pedidos, e encerraram o pedido.» — r/steamsupport ↗, incluídos no próprio conjunto de queixas da presente investigação\n\nPalavra por palavra, vírgula por vírgula, ao longo de cinquenta e cinco meses, três agentes e duas línguas de interface. A única alteração em todo o texto é a redação da última frase, que passou de 2020 para 2024, de «não receberá mais respostas» para «futuros pedidos de ajuda… poderão ser encerrados sem resposta.» Seja qual for o processo que esteve na origem destas decisões, a carta não constitui um registo do mesmo. Os motivos invocados são «atividades comerciais, relatos da comunidade e outros fatores» — uma categoria, um relatório de origem desconhecida e um conjunto de fatores não especificados.\n\nMais cinco casos, recolhidos da mesma forma. Os três primeiros pertencem à mesma categoria e têm o mesmo resultado; os dois últimos referem-se ao mesmo serviço, respondendo a uma regra diferente com as mesmas palavras:\n\nData\tO que a conta fez\tO que aconteceu\tFonte\n04.12.2021\tComprar e vender no Buff — «Não fiz mais do que algumas compras e vendas no Buff, também conhecido como negociação P2P»\tProibição na comunidade: sem mercado, sem transações, inventário caro congelado\tr/csgomarketforum ↗ arquivado 2025-03-27 ↗\n06.12.2021\tTransações P2P unidirecionais através do Buff e do Bitskins para equipamento e trocas por modelos superiores\tFechadura permanente para uso comercial e fechadura comunitária: «Fiquei preso num modo pseudo-invisível… O meu perfil também ficou bloqueado na modalidade privada»\tr/GlobalOffensiveTrade ↗ arquivado 2021-12-06 ↗\n20 de dezembro de 2024\tConta aberta desde 2017, milhares de horas; trocas em mercados da comunidade por equipamentos temáticos e trocas por itens de nível superior\tBloqueio permanente com bloqueio comunitário, sem aviso prévio nem advertência; apoio \"afirmam que a sua decisão é definitiva\", as respostas são automáticas\tr/csgomarketforum ↗ arquivado 2025-06-27 ↗\n23.12.2024\tUm utilizador que regressa adiciona fundos à carteira após um ano de ausência, utilizando uma VPN «apenas para segurança geral na Internet»\tBanimento permanente da comunidade com não foi apresentada qualquer justificação: «A proibição é permanente e não podem fornecer mais informações, podendo outros pedidos de apoio ser encerrados sem resposta.» 196 votos positivos, 340 respostas\tr/steamsupport ↗\n04.08.2026\tAnos de compras no Irão; o autor afirma que nunca publicou nada, nunca utilizou o Market, nunca utilizou os fóruns\tAcesso à comunidade bloqueado até 2038 mais «regiões sujeitas a sanções»; pedido de assistência encerrado por um agente chamado Azul. O reembolso da mesma conta, proveniente do mesmo endereço IP iraniano, tinha sido aprovado um ano antes. A biblioteca e o dinheiro ficam com Valve.\tr/pcgaming ↗\n\nA última linha segue uma regra diferente das restantes — conformidade com sanções, e não utilização comercial — e está incluída porque o formato da resposta é idêntico: uma categoria, sem provas, sem recurso, um ticket encerrado. Além disso, levanta uma questão que as outras não levantam. Se era ilegal prestar serviços à conta, os anos de pagamentos foram ilegalmente aceites. Uma dessas duas posições tem de estar errada, e apenas uma delas acarretou custos para o cliente.\n\nTodas as oito foram lidas no 2026-09-22 — os tópicos de 2021 e dezembro de 2024 através de instantâneos do Internet Archive e os restantes através de uma interface pública do Reddit, uma vez que o Reddit recusou os pedidos diretos do anfitrião responsável pela recolha. As duas cartas de 2020 e 2024 foram transcritas a partir das capturas de ecrã anexadas às publicações originais, que ainda se encontram ativas. Esta investigação não alega que nenhuma destas contas seja inocente ou culpada de nada — e é precisamente essa a questão. Nenhum leitor, nem qualquer entidade reguladora, consegue perceber isso a partir da carta.\n\nNota sobre a origem dos dados — perdas à escala do operador\n\nOs operadores inquiridos no âmbito desta investigação referem perdas da ordem dos cinco a dez mil contas cada em operações de fiscalização pontuais, com a verificação das contas principais a ser efetuada em simultâneo com a exploração agrícola. Essa sondagem é registada aqui como informação fornecida pela própria entidade, e não como uma conclusão. Não possui um tamanho de amostra publicado, nem uma data de recolha fixa, nem uma verificação por conta, e nenhum outro valor nesta página depende dele; as duas linhas na secção 02 que se baseiam nele estão assinaladas como tal.\n\nÉ afirmado, em vez de omitido, por duas razões. O mecanismo de proibição em cadeia acima é a explicação documentada precisamente para esse padrão. E uma entidade reguladora pode exigir, a partir de Valve, o único registo que resolveria a questão: quantas contas foram alvo de medidas de automatização, em que fases, e quanto cada uma dessas contas tinha gasto na loja antes de esta ser encerrada. Enquanto esse registo não existir, o valor permanece como está — relatado, atribuído e não comprovado.\n\n07 — A assimetria\nOs dois lados da mesma secretária\n\nCompare esse padrão de prova com o Valve aplicado à sua própria operação de apoio. A coluna da direita corresponde ao registo de incidentes deste dossiê, reproduzido com as ressalvas que nele constam.\n\nUm cliente, para fins de negociação\n\nOito casos documentados, 2020–2026\n\nConduta\nVenda ou compra de artigos em plataformas de comércio de terceiros; num dos casos, não houve qualquer conduta indevida — a conta tinha sido roubada.\nProvas apresentadas\nNenhum. «Com base nas transações, nos relatos da comunidade e noutros fatores.»\nAviso\nNenhuma. Valve reservou isso no § 4.D: «A Valve não é obrigada a notificá-lo antes de rescindir o contrato.»\nRecurso\n«Este bloqueio é permanente e Steam O Apoio ao Cliente não pode ajudá-lo mais nesta questão.»\nBilhete\nEncerrado após a primeira resposta. Outros pedidos \"pode ser encerrado sem resposta.\"\nAlcance\nPerfil, lista de amigos, chat, Market, inventário e todos os itens comprados com dinheiro real.\nDuração\nPermanente.\nUma frota de bots automatizados, para grande volume\n\n694,673 conjuntos completos em stock público distribuídos por 91 robôs\n\nConduta\nExecutar scripts automatizados em modo «headless» em milhares de contas simultaneamente para desativar cartões, criar emblemas em massa e trocar conjuntos em escala industrial.\nProvas apresentadas\nDiretórios de bots publicados abertamente (steam.supply, SteamLvlUp) e grupos públicos com milhões de membros.\nAviso\nSem intervenção. 88.97% não está sujeito a qualquer tipo de proibição; 99.8% das proibições restantes são meramente cosméticas.\nRecurso\nNão é necessário. As frotas operam de forma contínua ao longo de ciclos de vida plurianuais, sem interrupções.\nBilhete\n—\nAlcance\nTroca de inventário sem restrições, nivelamento de crachás e liquidez do mercado.\nBenefício para Valve\n$26.8M+ no valor mínimo de compras na loja ($5.00 porta de entrada por conta) mais 15% reduções nas transações do Mercado Comunitário.\nA questão que isto levanta, em termos simples\n\nUm cliente individual que troque cartões ou itens manualmente está sujeito a uma suspensão permanente e inapelável ao abrigo do § 4.C (automatização) ou do § 2.G (utilização comercial). Uma frota de «farming» automatizada que utiliza bots sem intervenção humana em milhares de contas opera abertamente com uma taxa de intocabilidade de 88.97%. Valve é o beneficiário de ambos.\n\nA assimetria é de natureza económica: os comerciantes individuais retiram valor da plataforma, enquanto as frotas de cartões automatizadas injetam milhões no limite de gastos na loja da Valve ($5.00 por conta) e alimentam as comissões de transação em cada revenda. A aplicação das regras não segue o regulamento escrito; segue o modelo de receitas.\n\n08 — Governação\nQuem controla a economia das cartas\n\nA conclusão recorrente deste dossiê — de que a camada de terceiros em torno de Steam é composta por pessoal proveniente do interior de Steam — também se aplica à economia dos cartões, e leva a uma conclusão específica: ninguém independente consegue avaliar o que a ação coerciva de Valve realmente faz, porque a parte capaz de avaliar está dentro dessa camada. Todos os factos abaixo foram obtidos a partir do próprio grupo público e das páginas de perfil de Valve em 2026-09-22 e podem ser reproduzidos por qualquer pessoa num navegador.\n\nUm funcionário com o código Valve modera o maior grupo de troca de cartas Valve funcionário\n\nCardTrades ↗ descreve-se, no seu próprio cabeçalho, como o \"Steam Grupo oficial de troca de cartões\" e transporta 97,114 membros. Os seus moderadores indicados — as contas que detêm o controlo desse grupo — são Mickmane, SgtFopper e afarnsworth ↗.\n\nEsse último perfil é identificado pela própria marcação do site de Valve como um colaborador Valve — a página apresenta class=\"profile_header_valve_employee\" — indica a sua localização como Bellevue, Washington, e pertence à Valve, Steam e Steam Grupo de Cartas Colecionáveis grupos. SteamID64 76561197960434622, membro desde 12 de setembro de 2003.\n\nA observação é de natureza estrutural, não pessoal, e é não uma questão de automação — o moderador de um grupo de troca de cartas não está a utilizar um bot, e nada aqui sugere o contrário. A questão prende-se com a cláusula em secção 07. Steam O Card Exchange é um serviço de cartões comerciais de terceiros; a troca de cartões através de serviços de terceiros é precisamente a conduta pela qual o Valve bloqueia permanentemente as contas normais ao abrigo de «utilizado para fins comerciais com base em transações, relatórios da comunidade e outros fatores.» Um colaborador Valve desempenha a função de moderador oficial no grupo comunitário oficial desse serviço, que conta com noventa e sete mil membros.\n\nNão é feita aqui qualquer acusação de irregularidade contra qualquer indivíduo, e não se tira qualquer conclusão sobre o que essa função implica. A assimetria é a constatação: quando uma conta comum recorre a um serviço de cartão ou de «skin» de terceiros, a resposta é um ticket encerrado e um bloqueio permanente sem que sejam apresentadas provas; quando o serviço é este, um funcionário Valve consta da lista de moderadores e o acordo está visível numa página que o próprio Valve publica. O que se pede é o que se pede em todas as outras partes deste dossiê: apresente a autorização por escrito, se existir — e, se não for necessária, diga-o por escrito, porque a oito pessoas da secção 06 foi dito o contrário.\n\nA camada da lista de proibições e quem a administra Moderador voluntárioServiço prestado por terceiros\n\nGrupo do Steambans.com (arquivado) ↗ (ao vivo ↗ arquivado 2025-12-03 ↗) regista a sua linhagem na descrição do grupo que se conservou: \"O grupo oficial da comunidade Steambans.com Steam. O SteamBans.com é um serviço totalmente novo baseado num conceito antigo. As listas globais de banimentos estão ativas há anos no antigo programa WONID da VALVe. Quando ocorreu a mudança para o STEAMID, foi natural para nós desenvolvermos um serviço especialmente concebido para este novo sistema. Mas também queríamos mais. *. Página de arquivo do Steambans, que encerrou em 2013.\" Entre os seus administradores constam devicenull e killahinstinct_ ↗.\n\nEssa conta de administrador é não um Valve colaborador — não tem qualquer indicação de que seja colaborador. Trata-se de um voluntário com um estatuto invulgarmente elevado: um membro de Moderadores da comunidade (414 membros, descrito como um grupo \"criado pelos moderadores da comunidade de Steam\"), de Coordenadores da Wiki, de Steam Mercado Comunitário, e dos grupos do programa Valve e de pré-lançamento, incluindo Valve Pipeline, Steam Versão Beta para Clientes, Autenticação Móvel (Versão Beta), Nova versão beta da comunidade Steam, Steam Laboratórios, Steamworks e Denunciar URLs fraudulentas. SteamID64 76561197960794555.\n\nTambém dentro desse círculo e a exibir os Steambans diretamente na lista de membros do seu grupo público: msart ↗ (lista de grupos ↗), SteamID64 76561197977933359, cujo perfil afirma, nas suas próprias palavras «Sou o responsável pelo site steamid.uk e por muitos outros sites relacionados ou não com o Steam», e que gere uma rede interligada de dezasseis grupos — SteamIDcouk (grupo principal «Sid website»), SidAdmins, SidBans, steamideu, Steam3ID, s-id e SArchive entre eles.\n\nO próprio site steamid.uk indica esse mesmo número. Nas suas perguntas frequentes (FAQ): «Quem criou o SteamID? O site do SteamID, a infraestrutura de rede e os sistemas de segurança são todos geridos pela 76561197977933359.» Duas respostas mais abaixo indica-se de onde provêm os dados: «O SteamID utiliza principalmente a API Web Steam para a recolha de dados.» A mesma página descreve vários servidores dedicados em diferentes fornecedores de alojamento, servidores de desenvolvimento, armazenamento e pesquisa de texto fora das instalações, bem como uma instalação de cópias de segurança separada.\n\nVerificado através de registos preservados no Internet Archive: o Resumo do grupo Steambans de 3 de dezembro de 2025 ↗, o Resumo do perfil do operador a 14 de setembro de 2024 ↗, e o Resumo das Perguntas Frequentes do Steamid.uk, de 1 de abril de 2026 ↗, comparando os dados lidos diretamente em 2026-09-22.\n\nO que isto significa, e o que não significa\n\nAs listas de banimento, a resolução do SteamID e a troca de cartões são os três serviços que determinam quem é de confiança, quem é identificável e qual é o valor de um item. Nenhum destes três serviços é gerido pela Valve. Em cada uma delas, as pessoas que estavam aos comandos provinham do interior da órbita de Valve: um colaborador Valve sinalizado na lista de moderadores do grupo oficial do serviço de cartões; um moderador da comunidade Valve com longa experiência, com acesso ao programa de pré-lançamento, responsável pela administração do grupo da lista de banidos; o serviço de identificação gerido por um particular que faz parte do mesmo círculo. Três serviços, três interfaces de controlo, três pessoas Valve às quais já tinha sido concedido estatuto.\n\nA filiação num grupo não equivale a um vínculo laboral, e nada disto constitui uma acusação. É um facto de governação, e é essa a razão pela qual a defesa habitual — trata-se de terceiros, não temos controlo sobre eles — tem de ser testado, em vez de ser aceite. As pessoas que estão aos comandos não são estranhas ao Valve. O Valve está em posição de dizer o que lhes pediu, se é que lhes pediu alguma coisa; ninguém de fora está em posição de o descobrir.\n\nNinguém conta. É essa a conclusão.\n\nO espaço de identificação Steam é um intervalo contínuo de números inteiros. Percorrê-lo e indicar quantas contas estão banidas, quantas estão limitadas e qual é a quantidade de inventário sujeita a uma proibição de transações não constitui um programa de investigação — trata-se de um ciclo e de uma chave API. O Valve fornece essa chave, em steamcommunity.com/dev/apikey. E, no entanto, Nenhuma entidade independente publica esse recenseamento. Não é uma entidade reguladora, nem um jornalista, nem um académico, nem uma associação de consumidores. Os únicos dados públicos sobre a dimensão da aplicação da lei em Steam são aqueles que Valve decide mencionar.\n\nA capacidade não falta. Está disponível. O serviço que resolve e indexa o espaço de identificação em grande escala — steamid.uk — afirma na sua própria secção de perguntas frequentes que «utiliza principalmente a API Web Steam para a recolha de dados» e opera-o através de vários servidores dedicados, armazenamento externo, máquinas de pesquisa de texto e uma instalação de cópias de segurança separada. É gerido por um particular. O seu grupo de irmãos da lista de banidos é co-administrado por um moderador de longa data da comunidade Valve, com acesso aos programas de pré-lançamento de Valve. A única entidade em posição de divulgar os resultados encontra-se na órbita de Valve e não os divulga.\n\nEsta é a mesma estrutura que o dossiê identifica em todos os outros contextos. Todos os serviços que tomam decisões determinantes sobre a economia Steam — quem é de confiança, quem é identificável, qual é o valor de um bem, quem está proibido — são, nominalmente, entidades terceiras e, na prática, estão ligados ao Valve. Steam O «Card Exchange» não constitui uma exceção a esse padrão; é mais um exemplo do mesmo. A alegação de que se trata de operadores independentes pode ser invocada por Valve precisamente porque nunca ninguém conseguiu testá-la em relação a um número.\n\nCenso de 10,88 milhões de contas: 88.97% Não alterado\n\nA base instalada do ArchiSteamFarm foi auditada em todo o Valve GetPlayerBans ponto final (10,880,610 contas, 55 minutos). Só o subconjunto não limitado representa $26.8M+ no valor mínimo de compra na loja (limite mínimo de entrada de $5.00). As contas 9,680,599 (88.97%) não estão sujeitas a qualquer tipo de restrição, e 99.8% dos restantes estão sujeitos apenas a proibições comunitárias de caráter meramente simbólico, que mantêm a negociação automatizada ativa.\n\n5,360,499Membros da ASF sem restrições (número exibido de Steam)\n10,880,610Total de entradas da API analisadas (limitadas + não limitadas)\n9,680,599Nunca foi banido (88.97%)\n1,200,011Incluir qualquer proibição Steam (11.0%) — 99.8% cosmético\n55 minPara recensear toda a população, é fundamental\nProvas forenses e recenseamento aprofundado\n\nA análise demográfica detalhada — incluindo gráficos de distribuição por tipo de banimento, antiguidade da conta no momento da aplicação da medida, agrupamentos por ano de criação (2020–2026) e dados geográficos fornecidos pelos próprios utilizadores — encontra-se publicada no estudo de recenseamento específico.\n\nAbrir o Censo Completo das Proibições (10,88 milhões) (Anexo VI) →Secção 4 — O bloqueio do ID do ativo →\n\nPortanto, a pergunta a colocar, e à qual apenas Valve pode responder, é: qual o identificador ou a capacidade que foi retirado, em que data, por decisão de quem e que efeito mensurável teve nos operadores a quem se destinava — em contraste com o seu impacto em todas as pessoas lá fora que estavam a tentar fazer a contagem. Uma alteração que põe fim à auditoria independente não se torna neutra só porque foi anunciada como uma medida de segurança. É por isso que o recenseamento mencionado no parágrafo anterior não existe.\n\n09 — Método e limites\nO que foi lido e o que não é reivindicado\n\nTodas as citações nesta página foram retiradas da fonte ao vivo em 2026-09-22 e reproduzidas na íntegra. Nada aqui provém de uma extração de dados, de credenciais de uma plataforma de mercado ou de um conjunto de dados privado.\n\nOs quatro conjuntos de dados e os cálculos que lhes são aplicados\n\nCada uma delas é uma única solicitação pública, reproduzível a partir de um terminal. Não foi utilizada qualquer conta, não se efetuou o início de sessão em nenhuma plataforma de comércio e não foi chamado nenhum ponto de extremidade que exigisse credenciais.\n\nConjunto de dados\tDe onde veio\tO que foi calculado a partir disso\nCenso de cartões\n13,876 jogos\tSteam A tabela de preços de crachás publicada pela Card Exchange, o mesmo feed que apresenta os seus página de preços ao público ↗ arquivado 2026-08-04 ↗\tJogos que emitem cartas, cartas por conjunto, tipos de cartas distintos e o preço de mercado de cada conjunto completo. As medianas e o total $23,586.57 constituem os dados aritméticos desta investigação.\nPreços dos jogos\n13,713 resolvido\tO ponto de acesso público da loja do Valve, store.steampowered.com/api/appdetails, cc=us, apenas o campo do preço, em lotes\tMediana e distribuição do preço de tabela de um jogo com cartas; o número de jogos cujo conjunto completo vende mais do que o próprio jogo.\nExistências de robôs\n91 bots, 694,673 conjuntos\tO diretório público de bots de cartas em steam.supply/CardBots ↗, tal como aparece, sem necessidade de iniciar sessão\tTotal de conjuntos em stock, o número mínimo de cartões, o limite mínimo de perdas e o limite mínimo por bot em contas distintas.\nVerificação cruzada\n21 bots partilhados\tsteamlvlup.net/cardbots ↗ arquivado 2026-02-10 ↗, um diretório independente desses mesmos bots\tApenas para verificação. Nos 21 bots que constam em ambas as listas, a «Agregate Stock» concorda em 0.03%; a maior discrepância entre dois bots é 1.36%, o que é consistente com duas recolhas de dados de stock em tempo real realizadas com poucos minutos de intervalo.\n\nAtribuição, conforme exigido pelo segundo diretório: dados fornecidos por SteamLvlUp, licenciado ao abrigo de CC BY 4.0 arquivado 2026-09-23 ↗; utilizado aqui apenas como uma verificação independente dos dados de existências de terceiros e modificado no sentido de que as linhas por robô foram agregadas e comparadas, em vez de reproduzidas. Steam O Card Exchange e o steam.supply são referidos acima através de ligações. Os preços dos jogos são da autoria de Valve. Os nomes e imagens das cartas, jogos e conjuntos são de Valve ou das editoras, reproduzidos sem qualquer reivindicação nem licença, como factos relativos a um mercado.\n\nNão foram efetuadas duas medições previstas, que não foram substituídas. Os próprios parâmetros de referência do Mercado Comunitário da Steam — visão geral dos preços, pesquisar/apresentar, histórico de preços — não devolve qualquer resposta ao host de recolha, e Steam as páginas de discussão da Comunidade devolvem um código HTTP 403 ao mesmo, pelo que nenhum valor nesta página é derivado de dados em tempo real do Market. O método de volume de vendas que teria contabilizado as distribuições de cartas na reinicialização diária requer uma sessão Steam com início de sessão; O manifesto desta investigação indica que não foi utilizada qualquer credencial do marketplace, e essa declaração foi mantida. O nível mínimo de existências de bot é o que é possível medir sem um bot.\n\nFontes primárias\n\nSteam Contrato de Subscrição ↗ arquivado 2026-09-24 ↗ — § 2.A, § 2.G, § 3.D, § 4.C, § 4.D.\nSteam Suporte — Contas de utilizador limitadas ↗ — o limiar $5.00 e a lista de funcionalidades restritas.\nValve — Steam Perguntas frequentes sobre as cartas colecionáveis ↗ — a mecânica de drop e a taxa de jogo gratuito $9.\nArchiSteamFarm Perguntas frequentes ↗ e discussão n.º 3440 ↗.\nSteam Páginas de grupos e perfis da comunidade, para consulta direta, na secção 08.\nPerguntas frequentes do steamid.uk, instantâneo do Internet Archive 2026-04-01 ↗.\nOito Steam Avisos relativos ao bloqueio de apoio publicados pelos respetivos destinatários, 2020–2026, enumerados com os respetivos links na secção 06.\n\nO que não é reivindicado\n\nNão foi estimada qualquer receita para o Valve proveniente da «card farming». Não foi apresentado qualquer número de contas ativas para nenhuma ferramenta, e as 1,39 milhões de quotas de retirada são não um recenseamento das contas pertencentes à exploração agrícola — ver a nota na secção 02. Nenhuma pessoa é acusada de qualquer irregularidade; quando uma pessoa é identificada, é através do seu próprio nome de utilizador público Steam, no âmbito da sua função pública, a partir de uma página Valve que publica. Nenhuma das oito contas bloqueadas na secção 06 é considerada inocente ou culpada; a conclusão diz respeito à carta, não à conta. Os números relativos às perdas dos operadores na secção 02 são relatórios de primeira mão e estão identificados como tal em a nota de origem. As perguntas frequentes do steamid.uk são citadas a partir de um instantâneo do Internet Archive, uma vez que a página ativa está protegida por um desafio de bot. Não se afirma que tenha sido tentado realizar qualquer recenseamento de banimentos e que este tenha sido suprimido — a conclusão é apenas de que não foi publicado nenhum. A curva de nível Steam acima de 667 não foi modelada.\n\nPor que razão a ferramenta não é o tema\n\nArchiSteamFarm afirma que isso «não está autorizado por Valve» e não é acusada de nada nesta página. É utilizada como instrumento de medição, porque é a única entidade nesta economia que documenta os mecanismos publicamente e por escrito. A Valve pode resumir toda a exposição num único parágrafo: publicar quais as automatizações comerciais que autoriza e o registo, por operador, do que fez em relação ao resto.\n\nLeia a seguir: como é que o próprio mercado é avaliado → · a escala de preços e o limite máximo de cotação → · os artigos Steam não serão transportados →",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Uma «fazenda de bots» não é uma fuga na loja do Valve. É uma cliente."
          },
          {
            "level": 2,
            "id": null,
            "text": "O que é, na verdade, uma quinta, passo a passo"
          },
          {
            "level": 3,
            "id": null,
            "text": "Comprar em"
          },
          {
            "level": 3,
            "id": null,
            "text": "Comprar jogos"
          },
          {
            "level": 3,
            "id": null,
            "text": "Em espera\nA ferramenta inicia sessão na conta na rede Steam em modo sem interface gráfica, \"analisa os teus crachás\", cria a lista de títulos que podem ser cultivados e inicia \"jogar um jogo elegível e verificar periodicamente se o jogo já foi totalmente explorado.\" Descrição do mecanismo feita pelo seu responsável: este «não faz mais nada do que indicar Steam que estamos a jogar um determinado jogo.»"
          },
          {
            "level": 3,
            "id": null,
            "text": "As gotas acabam\nCada título é finito. «Cada jogo tem um número fixo de cartas que se podem obter. Assim que as obtiveres todas (cerca de metade do conjunto completo), o jogo deixa de ser uma boa opção para farmar.» Uma quinta que queira continuar a produzir tem de continuar a comprar títulos. A oferta de cartas é limitada pelas compras — por design e a favor de Valve."
          },
          {
            "level": 3,
            "id": null,
            "text": "Levantar dinheiro\nA carta sai por uma de três vias: é vendida no Mercado da Comunidade, trocada ou transformada em gemas. Cada uma destas opções constitui uma transação no Mercado de Subscrições ou uma troca, e o § 3.D reserva o direito de cobrar: \"Valve pode cobrar uma comissão pelas transações realizadas num Mercado de Subscrições.\" É este o passo que faz com que tudo isto constitua uma violação — ver 05."
          },
          {
            "level": 2,
            "id": null,
            "text": "Antes de uma exploração agrícola ganhar um cêntimo, já pagou Valve"
          },
          {
            "level": 3,
            "id": null,
            "text": "Qual é, de facto, o tamanho do objeto que está a ser comprado"
          },
          {
            "level": 3,
            "id": null,
            "text": "Qual é a dimensão de um conjunto?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Quanto custa a licença"
          },
          {
            "level": 3,
            "id": null,
            "text": "O que o conjunto final devolve"
          },
          {
            "level": 3,
            "id": null,
            "text": "Onde se encontram os conjuntos 694,673"
          },
          {
            "level": 3,
            "id": null,
            "text": "O que este piso diz e o que não diz"
          },
          {
            "level": 3,
            "id": null,
            "text": "E a agricultura não se sustenta com os preços praticados pela Valve'"
          },
          {
            "level": 3,
            "id": null,
            "text": "O que a quinta realmente sustenta"
          },
          {
            "level": 4,
            "id": null,
            "text": "Vendas de jogos"
          },
          {
            "level": 4,
            "id": null,
            "text": "\"Online\" e tempo de brincar"
          },
          {
            "level": 4,
            "id": null,
            "text": "Inscrições"
          },
          {
            "level": 4,
            "id": null,
            "text": "Dinheiro na carteira e taxas"
          },
          {
            "level": 4,
            "id": null,
            "text": "Relações públicas de nível 0"
          },
          {
            "level": 3,
            "id": null,
            "text": "E o próprio levantamento de dinheiro representa uma perda de valor Valve — paga-se imposto duas vezes"
          },
          {
            "level": 3,
            "id": null,
            "text": "Isto não é apenas um momento. É um setor com uma estrutura que se estende por vários anos."
          },
          {
            "level": 3,
            "id": null,
            "text": "Conjuntos completos de cartas disponíveis no diretório público do bot, à venda por Steam"
          },
          {
            "level": 3,
            "id": null,
            "text": "Como se apresenta a tabela de distintivos de vendas quando vista do topo"
          },
          {
            "level": 3,
            "id": null,
            "text": "E essa mesma frota continua lá quando não há nenhuma promoção a decorrer"
          },
          {
            "level": 3,
            "id": null,
            "text": "O diretório de repouso, bot a bot"
          },
          {
            "level": 2,
            "id": null,
            "text": "O outro produto é o número que aparece ao lado do teu nome"
          },
          {
            "level": 3,
            "id": null,
            "text": "Conjuntos completos consumidos, nível 1 a 1,000"
          },
          {
            "level": 3,
            "id": null,
            "text": "Como é que a curva foi verificada, uma vez que o Valve não a publica?"
          },
          {
            "level": 2,
            "id": null,
            "text": "A cláusula não descreve a agricultura de forma vaga. Enumera-a."
          },
          {
            "level": 3,
            "id": null,
            "text": "\"…hora de brincar\""
          },
          {
            "level": 3,
            "id": null,
            "text": "«… sem um contributo genuíno dos utilizadores»"
          },
          {
            "level": 2,
            "id": null,
            "text": "Cada saída a partir de um cartão de acesso a uma área cultivada é uma saída proibida pela licença — e a Valve cobra uma taxa à saída"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 2.A — a licença"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 2.G — a restrição"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 3.D — a taxa"
          },
          {
            "level": 3,
            "id": null,
            "text": "Se lermos os três em conjunto, a posição fica encerrada"
          },
          {
            "level": 3,
            "id": "fee-ladder",
            "text": "A taxa nessa porta não é de 15%. Numa carta «farmed», atinge dois terços."
          },
          {
            "level": 3,
            "id": null,
            "text": "Comissão efetiva numa venda no Mercado Comunitário, com base no preço pedido pelo vendedor"
          },
          {
            "level": 2,
            "id": null,
            "text": "Sem aviso prévio, em ondas, e vai descendo pelo número de telefone"
          },
          {
            "level": 3,
            "id": null,
            "text": "Caso 4 — junho de 2025, VAC proibições relativas ao CS2 em inatividade"
          },
          {
            "level": 3,
            "id": null,
            "text": "Como uma conta principal deixa de existir"
          },
          {
            "level": 3,
            "id": null,
            "text": "O mesmo parágrafo, com cinco anos de diferença, de três agentes diferentes"
          },
          {
            "level": 3,
            "id": null,
            "text": "Nota sobre a origem dos dados — perdas à escala do operador"
          },
          {
            "level": 2,
            "id": null,
            "text": "Os dois lados da mesma secretária"
          },
          {
            "level": 3,
            "id": null,
            "text": "Um cliente, para fins de negociação"
          },
          {
            "level": 3,
            "id": null,
            "text": "Uma frota de bots automatizados, para grande volume"
          },
          {
            "level": 3,
            "id": null,
            "text": "A questão que isto levanta, em termos simples"
          },
          {
            "level": 2,
            "id": null,
            "text": "Quem controla a economia das cartas"
          },
          {
            "level": 3,
            "id": null,
            "text": "Um funcionário com o código Valve modera o maior grupo de troca de cartas Valve funcionário"
          },
          {
            "level": 3,
            "id": null,
            "text": "A camada da lista de proibições e quem a administra Moderador voluntário Serviço prestado por terceiros"
          },
          {
            "level": 3,
            "id": null,
            "text": "O que isto significa, e o que não significa"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ninguém conta. É essa a conclusão."
          },
          {
            "level": 3,
            "id": null,
            "text": "Censo de 10,88 milhões de contas: 88.97% Não alterado"
          },
          {
            "level": 3,
            "id": null,
            "text": "Provas forenses e recenseamento aprofundado"
          },
          {
            "level": 2,
            "id": null,
            "text": "O que foi lido e o que não é reivindicado"
          },
          {
            "level": 3,
            "id": null,
            "text": "Os quatro conjuntos de dados e os cálculos que lhes são aplicados"
          },
          {
            "level": 3,
            "id": null,
            "text": "Fontes primárias"
          },
          {
            "level": 3,
            "id": null,
            "text": "O que não é reivindicado"
          },
          {
            "level": 3,
            "id": null,
            "text": "Por que razão a ferramenta não é o tema"
          }
        ],
        "links": [
          "https://help.steampowered.com/en/faqs/view/71D3-35C2-AD96-AA3A",
          "https://github.com/JustArchiNET/ArchiSteamFarm/wiki/FAQ",
          "https://steamcommunity.com/tradingcards/faq/",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260924114457/https://store.steampowered.com/subscriber_agreement/",
          "https://steamladder.com/ladder/badges/2861690/",
          "http://web.archive.org/web/20260716205303/https://steamladder.com/ladder/badges/2861690/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/farm-economy-timeline.json",
          "https://store.steampowered.com/charts/",
          "http://web.archive.org/web/20260923183013/https://store.steampowered.com/charts/",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://github.com/JustArchiNET/ArchiSteamFarm/discussions/3440",
          "https://x.com/gergelyszabo94/status/1311004678633795585",
          "https://x.com/prcs25/status/1811893857253982720",
          "http://web.archive.org/web/20240715122902/https://x.com/prcs25/status/1811893857253982720",
          "https://reddit.com/r/steamsupport/comments/1fjmgc5/what_to_do_when_your_steam_account_gets_hacked/mkelm2y/",
          "https://www.reddit.com/r/csgomarketforum/comments/r87owv/psa_my_steam_account_just_got_banned/",
          "http://web.archive.org/web/20250327203008/https://www.reddit.com/r/csgomarketforum/comments/r87owv/psa_my_steam_account_just_got_banned/",
          "https://www.reddit.com/r/GlobalOffensiveTrade/comments/r9xql9/d_recently_received_commercial_ban_for_what_seems/",
          "http://web.archive.org/web/20211206034804/https://www.reddit.com/r/GlobalOffensiveTrade/comments/r9xql9/d_recently_received_commercial_ban_for_what_seems/",
          "https://www.reddit.com/r/csgomarketforum/comments/1hhxx7m/d_permanently_locked_on_steam_for_commercial_use/",
          "http://web.archive.org/web/20250627014045/https://www.reddit.com/r/csgomarketforum/comments/1hhxx7m/d_permanently_locked_on_steam_for_commercial_use/",
          "https://www.reddit.com/r/steamsupport/comments/1hkctwt/permanent_ban_with_no_explanation/",
          "https://www.reddit.com/r/pcgaming/comments/1vf24lu/warning_to_all_gamersexpats_steam_took_my_money/",
          "https://steamcommunity.com/groups/card-trading-card-trades",
          "https://steamcommunity.com/id/afarnsworth",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/groups/steambans",
          "https://steamcommunity.com/groups/steambans",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/id/killahinstinct_",
          "https://web.archive.org/web/20240914124859/https://steamcommunity.com/id/msart",
          "https://steamcommunity.com/id/msart/groups/",
          "http://web.archive.org/web/20260401154714/https://steamid.uk/faq/",
          "https://phishdestroy.io/steam_dossier/pt/enforcement_audit.html",
          "https://phishdestroy.io/steam_dossier/pt/#evidence-blackout",
          "https://www.steamcardexchange.net/index.php?badgeprices",
          "http://web.archive.org/web/20260804200309/https://www.steamcardexchange.net/index.php?badgeprices",
          "https://steam.supply/CardBots",
          "https://steamlvlup.net/cardbots",
          "http://web.archive.org/web/20260210171205/https://steamlvlup.net/cardbots",
          "https://steamlvlup.net/",
          "https://creativecommons.org/licenses/by/4.0/",
          "http://web.archive.org/web/20260923221628/https://creativecommons.org/licenses/by/4.0/",
          "https://phishdestroy.io/steam_dossier/pt/market_economics.html",
          "https://phishdestroy.io/steam_dossier/pt/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/pt/elite_skins.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/pt/card_economy.content.json",
      "export_json_sha256": "efff40bbce0b81602b44032f0cecbfe9e7e8b724d5fca08e9f4ab9bff4dfff55"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "pt/elite_skins.html",
      "language": "pt",
      "title": "Um produto, dois sistemas de preços — O Dossiê «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/pt/elite_skins",
      "source_html_sha256": "c72dd51bd7a5da38dea67b5524b0135856c4ae28a4a15347554f483062c560ca",
      "exported_at": "2026-09-29T00:18:06.427Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "register",
            "source": "https://phishdestroy.io/steam_dossier/pt/elite_skins#register"
          },
          {
            "id": "",
            "source": "https://phishdestroy.io/steam_dossier/pt/elite_skins#selected"
          }
        ],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "elite_skins.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/pt/elite_skins.pdf?v=print-20260929-v5",
        "sha256": "b0624da139b431fcf36e42b35c265421f10dbdd3a0105a652a8f88ad3fab1f89",
        "bytes": 97821,
        "pages": 7
      },
      "integrity": {
        "signed_object": "elite_skins.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "elite_skins.content.json.asc",
        "digest_file": "elite_skins.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify elite_skins.content.json.asc elite_skins.content.json",
          "sha256sum -c elite_skins.content.json.sha256"
        ]
      },
      "content": {
        "text": "ANEXO IV / ARQUITETURA DE MERCADO / 20 SETEMBRO DE 2026\nRegisto no Elite Skins — O teto de mercado de $1,800\n\nUm artigo. Dois sistemas de preços.\n\nO QUE ESTA SECÇÃO DEMONSTRA\n\nEste registo estabelece um recenseamento empírico de todas as categorias de skins CS2 com preços superiores ao limite máximo de listagem de $1,800 do Community Market da Steam em cinco plataformas externas. Comprova que 248 as categorias de nível elevado — que representam 18,394 listagens ativas e $78.6 milhões em liquidez publicada — estão 100% ausentes do mercado oficial da Valve. Os vendedores que procuram preços de mercado reais são estruturalmente forçados a recorrer a plataformas externas, ao mesmo tempo que dependem exclusivamente dos mecanismos de negociação subjacentes da Steam.\n\nWhat this means — the Community Market listing ceiling\n\nSteam’s own market refuses a listing above roughly $1,800. A seller may ask less, never more. Items whose market price sits above that line therefore cannot be sold at that price on Steam at all — which is the mechanism that moves those sales to third-party venues while the item itself never leaves Valve’s inventory system.\n\nSection 13 — the off-Steam price gap →\n\n← Voltar ao resumo executivo\n\nSteam limita o preço de uma listagem no Community Market a cerca de $1,800.. Nos cinco mercados de terceiros cujos preços foram analisados neste resumo, 419 As categorias de artigos CS2 apresentam um preço de venda mais baixo em tempo real acima desse limite — e 402 algumas delas, 95.9%, não têm qualquer Steam listagem. Em conjunto, detêm cópias cotadas n18,641, no valor de, pelo menos, $82.4 milhões. É necessário que um segundo mercado concorde para que o preço seja válido, 248 dessas categorias estão confirmadas — e em todas elas, 100%, não aparece em Steam. O mais querido é um autocolante | Titan (Holo) | Katowice 2014 em $66,285, cotado por quatro plataformas de negociação situadas num intervalo de 5.2% entre si e não cotado por nenhuma das plataformas da Valve. A tabela completa, as representações gráficas e a classificação encontram-se no atlas da escala de preços.\n\nVerificar todas as entradas de «419» ↓Abrir o atlas ↗Leia o método\n248categorias em que o preço em dois ou mais mercados ultrapassa o limite máximo\n18,394exemplares listados em cinco plataformas de venda\n$78.6Mvalor mínimo dessas listagens\n100%dos quais estão totalmente ausentes de Steam\n\nCorreção · esta página apresentava anteriormente um preço não confirmado\n\nUma versão anterior desta página apresentava como título «Souvenir AK-47 | Point Disarray», com um preço pedido de $148,954 numa plataforma de vendas, enquanto a Steam o cotava a $119. Essa linha refere-se a uma única peça disponível numa única prateleira, sem que nenhuma outra plataforma de vendas concorde com o preço; por isso, trata-se de um preço pedido e não de um preço de venda, e já não consta da página. Todos os valores apresentados aqui estão agora restritos às categorias 248, nas quais pelo menos dois mercados, de forma independente, fixam preços acima do limite máximo. A linha em si não foi removida — continua no registo abaixo, e a classificação que a rebaixou está descrita na íntegra no atlas da escala de preços.\n\n01 / o dinheiro nas ofertas de compra ativas\nO limite mínimo mensurável em dólares\n\nRecalculado a partir do instantâneo licenciado do «cs2.sh» em cinco mercados. Trata-se de um valor mínimo agregado de pedido de venda num subconjunto definido, não de volume de vendas nem de uma avaliação da economia do CS2.\n\n248 CATEGORIAS CONFIRMADAS · 18,394 CÓPIAS LISTADAS · 5 MERCADOS$78.62M\n\nPreço mínimo agregado de venda publicado para cada artigo CS2 cujo preço seja fixado, de forma independente, por dois ou mais mercados acima do limite permitido pela Valve no seu próprio mercado.\n\nPor que razão isto é um valor mínimo e não uma estimativa\n\nPara cada mercado, multiplicamos o seu mais baixo solicite um artigo com base no número de exemplares que a plataforma de vendas apresenta. Todos os outros exemplares nessa prateleira têm um preço igual ou superior ao preço mínimo de venda, pelo que o verdadeiro valor anunciado é mais elevado — por definição, e não por suposição. Não se trata de uma venda, de um fluxo de caixa nem de uma avaliação a nível de todo o mercado, e o mesmo artigo físico pode aparecer em mais do que uma plataforma de vendas.\n\nVerificar todas as linhas de origem «419» ↗\n★ Luvas desportivas | Labirinto de sebes (testadas em campo)\n$4.68M\nAWP | Gungnir (Novo de fábrica)\n$4.46M\nAWP | Dragon Lore (Novo de fábrica)\n$4.34M\n★ Faca Borboleta | Fade (Nova de fábrica)\n$4.17M\nAK-47| Wild Lotus (Novo de fábrica)\n$4.16M\n★ Faca Borboleta | Doppler (Nova de fábrica)\n$3.64M\n\nAs barras mostram as seis maiores contribuições, ao nível da categoria, para o cálculo do preço mínimo, em escala em relação à maior. Uma barra alta reflete tanto o preço de venda mais baixo como o número de exemplares listados. O mesmo artigo físico pode aparecer em mais do que um mercado, pelo que estes valores não devem ser adicionados a nenhum outro total de mercado.\n\n02 / exemplos que podem ser analisados\nO que o limite não abrange\n\nAs ilustrações correspondem aos nomes exatos dos artigos, sempre que disponíveis. Os preços são os preços de venda em vigor constantes do catálogo datado, não registos de transações.\n\n★ Butterfly Knife | Doppler (Factory New)\n\nFonte: https://phishdestroy.io/steam_dossier/pt/elite_skins#selected\n\nA diferença mensurável: estas ofertas não podem ser igualadas por um anúncio em Steam com o mesmo valor em dólares americanos. O próprio site Valve Perguntas frequentes sobre o Mercado Comunitário arquivado em 2026-09-21 ↗ indica um preço máximo de venda de aproximadamente $1,800. Um vendedor ainda pode anunciar um preço inferior a esse valor; cabe ao vendedor decidir se isso seria aceitável. Um outro Pesquisa no CSMarketCap por artigos acima de $1,800 ↗ apresenta o «Factory New Dragon Lore» nos mercados indexados pelo 28, com cerca de 1.1mil ofertas exibidas; o inventário duplicado pode ser contabilizado mais do que uma vez.\n\n03 / a dependência estrutural\nO limite imposto pela Steam faz com que a determinação dos preços ocorra fora do Steam\n\nA comparação é de natureza estrutural. Não pressupõe que todos os preços de venda sejam justos, nem considera os imóveis não vendidos como receitas.\n\n01 · A REGRA\nSteam encerra a lista\n\nValve afirma que as listagens do Community Market têm um limite máximo de aproximadamente $1,800. Os saldos das carteiras também têm um limite máximo e os fundos das carteiras não podem ser levantados em dinheiro.\n\n02 · A OBSERVAÇÃO\nDragon Lore: $10,940.85\n\nO catálogo do mercado «5-» apresenta 389 ofertas em tempo real para o AWP Dragon Lore (novo de fábrica), a partir de $10,940.85 (piso CSFloat). O registo mais abrangente contém 248 categorias comprovadas acima do limite de Steam.\n\n03 · A CONSEQUÊNCIA\nRepartição do preço e da transferência\n\nUm vendedor que pretende obter esse preço mais elevado não consigo publicá-lo em Steam. Os serviços externos podem definir o preço à vista, mas a entrega continua a recorrer à propriedade e à transferência de artigos controladas pelSteam.\n\nA contradição política: Do próprio Valve Contrato de Subscrição arquivado em 2026-09-21 ↗ reserva-se o direito de proibir a exploração comercial dos serviços Steam, salvo se expressamente autorizado, enquanto o seu 2016 declaração arquivado em 2026-09-21 ↗ Os referidos operadores de jogos de azar já estavam a utilizar um OpenID do Steam e contas automatizadas. Isso constitui uma prova direta de que Valve tinha conhecimento desta categoria de operadores externos em 2016.. No entanto, o mercado oficial não pode publicar os preços observados destes artigos de elevado valor. Trata-se de uma dependência arquitetónica da determinação de preços e das transações fora doSteam; O estatuto contratual de cada mercado específico requer comprovativos específicos. Os dois principais mercados ocidentais que registam este volume de transações acima da capacidade máxima operam como entidades empresariais formais nas principais jurisdições — CSFloat Inc. (constituída em Delaware, EUA) e Skinport GmbH (registada em Estugarda, Alemanha, HRB 764879) — realiza abertamente transações no valor de centenas de milhões em vendas de artigos entre particulares, recorrendo diretamente às APIs Web e à infraestrutura comercial da Steam.\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\nAs quatro linhas de $100,000 correspondem ao preço máximo de listagem da própria CSFloat. Estão assinaladas no registo e não devem ser interpretadas como avaliações. O rastreio arquivado das listagens em CSFloat atingiu apenas aproximadamente $6,999,, pelo que se utiliza o instantâneo do catálogo público para o registo completo >$1,800.\n\n04 / mais um jogo da série «Valve»\nO teto também apanha o Dota2\n\nO mesmo teste rigoroso da oferta mais barata em Skinport identifica as categorias 166 CS2 e 3 Dota 2. Trata-se de um instantâneo de mercado distinto; não as adicione à lista 245. do site CSFloat.\n\nDOTA 2 · OFERTA DE 1\nCrescente Heroico e Brutal\n\nSkinport, o mais barato: pergunte: $14,622.25.\n\nDOTA 2 · OFERTA DE 1\nCapa «Dark Artistry»\n\nSkinport, o mais barato: pergunte: $8,255.16.\n\nDOTA 2 · OFERTA DE 1\nEstrela Energizada Corrompida\n\nSkinport, o mais barato: pergunte: $2,087.92.\n\nEstas são três categorias de itens listadas, não todos os itens existentes no Dota 2. Verificar as linhas com data em Skinport ↗ e API documentação ↗.\n\n05 / robustez\nA conclusão não depende do limite exato\n\nValve define o limite máximo na moeda regional do comprador, pelo que, quando convertido para dólares americanos, não resulta num valor exato. O recenseamento é, por isso, repetido em cada limiar plausível. A percentagem destes itens em falta em Steam nunca desce abaixo de 95%.\n\nLimiar testado\tCategorias de artigos\tExemplares listados\tValor mínimo\tAusente de Steam\n$1,800\t419\t18,641\t$82,449,526\t95.9%\n$2,000\t382\t15,159\t$75,541,325\t95.5%\n$2,070\t363\t12,336\t$69,560,305\t95.6%\n$2,300\t323\t11,644\t$67,984,432\t95.0%\n$2,500\t299\t10,950\t$66,203,929\t95.0%\n\nLeia uma linha de cada vez; as linhas são subconjuntos aninhados do mesmo recenseamento, não populações distintas. O «valor mínimo» multiplica o valor de cada mercado mais baixo o sistema baseia-se no número de exemplares que indica, pelo que, por definição, subestima o número de exemplares disponíveis nas prateleiras. Abrir o conjunto de dados ↗\n\n06 / escassez que se possa contar\nQuão poucos destes existem realmente à venda\n\nA BUFF divide a prateleira de cada artigo em intervalos variáveis e indica quantas cópias se encontram em cada um deles. Isso transforma a palavra «raro» num número — e permite avaliar o estado do artigo separadamente do seu design.\n\n298 EXEMPLARES LISTADOS\nAWP | Lenda do Dragão\n\n8 diferentes variantes com preços definidos. A mais cara, AWP de recordação | Dragon Lore (novo de fábrica), pergunta $12,363 com 20 exemplares na prateleira.\n\nNa secção de flutuadores de melhor qualidade da prateleira (0–0.01) encontram-se 2 cópias, perguntando $17,875 — um prémio de +45% em relação ao preço de venda base do artigo, apenas com base no seu estado de conservação.\n\n607 EXEMPLARES LISTADOS\nM4A4 | Howl\n\n12 diferentes variantes com preços definidos. A mais cara, Souvenir M4A4 | Howl (Novo de fábrica), pergunta $14,895 com 2 exemplares na prateleira.\n\n213 EXEMPLARES LISTADOS\nAK-47 | Wild Lotus\n\n7 diferentes variantes com preços definidos. A mais cara, AK-47, para coleção | Wild Lotus (novo de fábrica), pergunta $14,895 com 2 exemplares na prateleira.\n\n310 EXEMPLARES LISTADOS\nAWP | Gungnir\n\n7 diferentes variantes com preços definidos. A mais cara, AWP de recordação | Gungnir (desgaste mínimo), pergunta $14,895 com 2 exemplares na prateleira.\n\nPor que razão isto é importante para o resto deste dossiê: Não se trata de abstrações. Existem algumas centenas de exemplares de cada troféu em circulação em todo o mundo, cada um associado a uma conta Steam e transferido através de uma transação Steam. Num mercado tão reduzido, o roubo de um único item de inventário constitui um acontecimento mensurável, e as técnicas de apropriação de contas documentadas noutras partes desta investigação têm um retorno direto e quantificável.\n\nOs números referem-se às listagens ativas num mercado no momento da recolha dos dados, e não ao número total existente. As cópias que se encontram em inventários privados não são contabilizadas aqui. Abrir o conjunto de dados «float» ↗\n\n07 / a escada fora do campo de visão\nQuanto mais caro for o artigo, mais longe fica de qualquer local visível\n\nCada degrau abaixo corresponde a uma classe de prova diferente. Deliberadamente, não foram agrupadas num único número.\n\nDegrau\tFigura\tQue tipo de facto é este?\nCeiling on Valve's own market\t~$1,800\tPublished rule, stated in the Steam Community Market FAQ.\nDearest ask several marketplaces agree on\t$66,285\tMeasured by us in this snapshot. Sticker | Titan (Holo) | Katowice 2014, quoted by four marketplaces within 5.2% of one another. An ask, not a sale.\nDearest ask seen on any single shelf\t$148,954\tOne marketplace, one copy, no second marketplace agreeing — and equal to a round CNY 1,000,000 at the snapshot rate. Listed here as the outer edge of what sellers ask, and relied on for nothing.\nPublic marketplace sale\t$49,999\tSpecialist Gloves | Crimson Kimono (FN) on CSFloat, as reported by SteamAnalyst. Platform-recorded, third-party reported.\nReported private sale\t$400,000\tAK-47 | Case Hardened, reported by PC Gamer in April 2023. Journalism, not a record we hold.\nReported offer, declined\t$1,500,000\tBlue Gem Karambit, pattern #387. No sale took place and the figure has not been independently confirmed. Included to mark the ceiling of the claims, not to assert a value.\n\nA questão estrutural: O mercado da Valve fica em cerca de $1,800.. As plataformas de terceiros elevam a transação para cerca de $66,000, valor em que várias delas concordam, e para aproximadamente $150,000, valor em que apenas uma concorda. Acima desse valor, não existe qualquer plataforma — as maiores transferências de ativos emitidos por Valveocorrem de forma privada, entre indivíduos, sem cotação, sem registo na plataforma, sem verificação de identidade e sem comunicação. A transferência em si continua a ser efetuada na Steam. Quanto mais elevado for o valor, menos visível ele se torna, e a infraestrutura que o suporta é, na íntegrValve.\n\nOs dois últimos pontos referem-se a relatos de terceiros, citados como tal. Este projeto não os verificou e não se baseia neles para tirar quaisquer conclusões.\n\nTodas as categorias observadas em «419»\n\nFonte: https://phishdestroy.io/steam_dossier/pt/elite_skins#register\n\n09 / proveniência e limites\nVerifique o cálculo\n\nApresentamos os dados locais e a fonte pública. O valor numérico referido refere-se a CSFloat na data de captura.\n\nOs limites e condições do próprio Valve\n\nSteam Perguntas frequentes sobre o Mercado Comunitário ↗ arquivado em 2026-09-21 ↗ indica o valor máximo aproximado de1,800. O Contrato de Assinante ↗ arquivado em 2026-09-21 ↗ estabelece as restrições à utilização comercial.\n\nDe onde vêm os preços\n\nOs preços, o número de ações cotadas e os intervalos de capitalização em circulação são retirados do cs2.sh dados de mercado API no âmbito de uma subscrição comercial paga, utilizando uma chave de licença. Não foi efetuada nenhuma extração de dados de nenhuma plataforma de comércio eletrónico, nem foram utilizadas contas ou credenciais de nenhuma plataforma de comércio eletrónico. O fornecedor agrupa a BUFF, a Youpin, a CSFloat, a Skinport, a C5Game e o Steam Community Market; todos os valores são apresentados em dólares americanos, tal como indicados. Abrir o manifesto de proveniência ↗ — regista os pontos finais exatos, os tempos de captura e os hashes SHA-256 das imagens em bruto, pelo que um leitor independente com a sua própria chave pode obter os mesmos dados e recalcular todos os valores apresentados nesta página.\n\nO que não conseguimos obter\n\nA subscrição adquirida abrange apenas os instantâneos atuais. Não tivemos acesso aos pontos finais históricos e de arquivo, e Nesta página não se faz qualquer afirmação sobre tendências, preços passados ou variações ao longo do tempo. Tudo aqui é um único momento, com data.\n\nO registo anterior de «CSFloat»\n\nA primeira versão desta exposição contava com 245 categorias, provenientes de um único CSFloat instantâneo do catálogo datado de 20 2026: essa imagem permanece aqui ↗. O presente registo é mais abrangente, uma vez que abrange cinco mercados em vez de um. Trata-se de dois registos distintos, que não devem ser somados.\n\nDeclaração de execução específica de Valve\n\nAtualização sobre a troca de itens no jogo «2016» da Valve ↗ arquivado em 2026-09-21 ↗ diz respeito aos operadores de jogos de azar que utilizam o OpenID e contas automatizadas do Steam. Trata-se de uma medida mais restrita do que uma proibição de todos os mercados externos.\n\nLimite de interpretação\n\nTrata-se de ofertas, não de vendas. Um nome de mercado pode abranger vários artigos físicos com diferentes detalhes em termos de acabamento, padrão ou autocolante. Este registo não mede o valor total de mercado nem a intenção dValve.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Registo no Elite Skins — O teto de mercado de $1,800"
          },
          {
            "level": 2,
            "id": null,
            "text": "O limite mínimo mensurável em dólares"
          },
          {
            "level": 3,
            "id": null,
            "text": "Por que razão isto é um valor mínimo e não uma estimativa"
          },
          {
            "level": 2,
            "id": null,
            "text": "O que o limite não abrange"
          },
          {
            "level": 3,
            "id": null,
            "text": "★ Butterfly Knife | Doppler (Factory New)"
          },
          {
            "level": 2,
            "id": null,
            "text": "O limite imposto pela Steam faz com que a determinação dos preços ocorra fora do Steam"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam encerra a lista"
          },
          {
            "level": 3,
            "id": null,
            "text": "Dragon Lore: $10,940.85"
          },
          {
            "level": 3,
            "id": null,
            "text": "Repartição do preço e da transferência"
          },
          {
            "level": 2,
            "id": null,
            "text": "O teto também apanha o Dota2"
          },
          {
            "level": 3,
            "id": null,
            "text": "Crescente Heroico e Brutal"
          },
          {
            "level": 3,
            "id": null,
            "text": "Capa «Dark Artistry»"
          },
          {
            "level": 3,
            "id": null,
            "text": "Estrela Energizada Corrompida"
          },
          {
            "level": 2,
            "id": null,
            "text": "A conclusão não depende do limite exato"
          },
          {
            "level": 2,
            "id": null,
            "text": "Quão poucos destes existem realmente à venda"
          },
          {
            "level": 3,
            "id": null,
            "text": "AWP | Lenda do Dragão"
          },
          {
            "level": 3,
            "id": null,
            "text": "M4A4 | Howl"
          },
          {
            "level": 3,
            "id": null,
            "text": "AK-47 | Wild Lotus"
          },
          {
            "level": 3,
            "id": null,
            "text": "AWP | Gungnir"
          },
          {
            "level": 2,
            "id": null,
            "text": "Quanto mais caro for o artigo, mais longe fica de qualquer local visível"
          },
          {
            "level": 2,
            "id": null,
            "text": "Todas as categorias observadas em «419»"
          },
          {
            "level": 2,
            "id": null,
            "text": "Verifique o cálculo"
          },
          {
            "level": 3,
            "id": null,
            "text": "Os limites e condições do próprio Valve"
          },
          {
            "level": 3,
            "id": null,
            "text": "De onde vêm os preços"
          },
          {
            "level": 3,
            "id": null,
            "text": "O que não conseguimos obter"
          },
          {
            "level": 3,
            "id": null,
            "text": "O registo anterior de «CSFloat»"
          },
          {
            "level": 3,
            "id": null,
            "text": "Declaração de execução específica de Valve"
          },
          {
            "level": 3,
            "id": null,
            "text": "Limite de interpretação"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/pt/#market-gap-section",
          "https://phishdestroy.io/steam_dossier/pt/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/pt/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/pt/skin_atlas.html#grading",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-above-the-ceiling.json",
          "https://phishdestroy.io/steam_dossier/pt/elite_skins#selected",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://csmarketcap.com/search?minPrice=1800&amp;page=1",
          "https://store.steampowered.com/agreement/?l=english",
          "http://web.archive.org/web/20260921022032/https://store.steampowered.com/agreement/?l=english",
          "https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921021947/https://store.steampowered.com/oldnews/22883",
          "https://phishdestroy.io/steam_dossier/pt/#proxy-bypass-explainer",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/skinport-floor-over-cap.json",
          "https://docs.skinport.com/items",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-float-scarcity.json",
          "https://phishdestroy.io/steam_dossier/pt/elite_skins#register",
          "https://cs2.sh/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/csfloat-catalogue.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/pt/elite_skins.content.json",
      "export_json_sha256": "02c4e4ac393e260637a79a1b906d65cc3fc1b704b1d75e5c3bd492830ea5db4f"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "pt/enforcement_audit.html",
      "language": "pt",
      "title": "O recenseamento Valve não será publicado — O Dossiê Steam",
      "source_url": "https://phishdestroy.io/steam_dossier/pt/enforcement_audit",
      "source_html_sha256": "1bce3c02889d35e505f6a91fd822bd46f9e361606090f40426fabaf9b9267607",
      "exported_at": "2026-09-29T00:18:05.207Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "enforcement_audit.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/pt/enforcement_audit.pdf?v=print-20260929-v5",
        "sha256": "0d9aeda290e283b2cd5f712e2a8bf7d8855c953e8a10c6050d708e126b0209cc",
        "bytes": 146480,
        "pages": 13
      },
      "integrity": {
        "signed_object": "enforcement_audit.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "enforcement_audit.content.json.asc",
        "digest_file": "enforcement_audit.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify enforcement_audit.content.json.asc enforcement_audit.content.json",
          "sha256sum -c enforcement_audit.content.json.sha256"
        ]
      },
      "content": {
        "text": "ANEXO VI — O RECENSEAMENTO VALVE NÃO SERÁ PUBLICADO\nQual é o tamanho da operação no Steam? Nós a contamos.\n\nNão há dados publicados sobre quantas contas de automação funcionam no Steam. Não há necessidade de isso ser mantido em segredo: o espaço de identificação Steam é um intervalo contínuo de números inteiros e o Valve distribui a chave da API Web que percorre esse intervalo. Por isso, pegámos na maior população que se identifica a si própria — a comunidade ArchiSteamFarm — e consultámos cada membro uma vez através do próprio ponto final de bloqueio do Valve. A auto-declaração ocorre porque o ASF, na primeira execução, adere automaticamente ao grupo Steam, a menos que o utilizador opte explicitamente por não aderir ou desmarque a configuração de adesão ao grupo (AutoJoinSteamGroup / Estatísticas). Como esta configuração está ativada por predefinição, os membros do grupo abrangem uma população alargada: redes comerciais ativas de bots com várias contas, amadores ocasionais que deixam as contas inativas e jogadores comuns que utilizaram o software na sua conta pessoal e nunca desativaram a subscrição predefinida. Isso faz com que os seus membros constituam um recenseamento prático do alcance acumulado do software: 10,880,610 contas no total (com 5,360,499 membros confirmados sem restrições que passaram pelo portão da loja $5.00). Depois, fizemos a única pergunta que importa — o que é que o Valve lhes fez, afinal?\n\nO que esta página não é. Não se trata de um argumento a favor de que o Valve deva banir dez milhões de pessoas, nem de uma queixa contra os «card farmers». Todos os números abaixo estão aqui por uma única razão: Valve faz banir indivíduos de forma permanente, e a razão que apresenta por escrito é a utilização comercial do Steam e a automatização. Isto mede a forma como essa mesma regra é aplicada à mesma conduta em grande escala — por um operador cujo desbloqueio $5.00, licenças de jogo e taxas do Market Valve são cobradas ao longo do processo. A conclusão é a assimetria, não a «farm».\n\nO total de 10,88 milhõesOs burlões que andam por aí (53,5 mil)Auditoria paga de 100 mil vs. auditoria gratuita\n10,880,610O número total de membros do grupo ASF que consultaram a API de banimento do próprio Valve (limitada e não limitada, em conjunto)\n88.97%Nunca fui banido — 9,680,599 contas ainda estão ativas\n63.06%Das contas banidas que são pagas ($5+ despesas) — 100,000 SRSWOR fatia (±0.39% MoE)\n67.77%Dos 51,732 burlões condenados, nenhum tem proibições por burla (recenseamento completo)\n01 — A balança\nDez milhões de contas, e nove em cada dez não foram utilizadas\n\nUma população que se conta a si própria, lida uma vez através do próprio ponto final de Valve.\n\nPORQUE É QUE SE AUTO-CONTAMBLA\nA ASF junta-se ao grupo por si\n\nNa primeira execução, ArchiSteamFarm conjuntos Estatísticas é definido como «true» por predefinição e junta-se ao grupo «SC Farm Steam» da Archi. Um operador tem de optar ativamente por sair. Assim, o número de membros representa um limite mínimo de instalações — e não um limite máximo. Os operadores que desativaram as Estatísticas não estão incluídos; o número real de instalações é, pelo menos, este.\n\nO QUE LEMOS\n10,880,610 entradas no total\n\nA lista de membros da API devolveu 10,880,610 SteamID64 no total — tanto limitados como não limitados. A página do grupo de Steam mostra 5,360,499 (apenas não limitados). Cada entrada foi processada uma vez através de ISteamUser/GetPlayerBans em 2026-09-23. Cinquenta e cinco minutos numa única tecla.\n\nA RESPOSTA\n88.97% limpo\n\n1,200,011 não está sujeito a qualquer Steam proibição (11.03%). O outro 9,680,599 não tem absolutamente nada registado — não é um banimento da comunidade, não é VAC, nada. A «farm» não está a ser eliminada. Está a continuar a funcionar. A mesma cláusula, aplicada a uma única pessoa, é suficiente para a afastar definitivamente.\n\nDas 10,880,610 contas, quantas Valve foram utilizadas\n\nToda a população analisada, dividida consoante o Valve tenha ou não aplicado qualquer proibição. A secção a vermelho representa tudo o que o Valve já fez a esta frota.\n\n88.97%nunca foi banido\n11.03%\nNão há qualquer tipo de proibição — 9,680,599 (88.97%)Apresenta uma restrição de Steam — 1,200,011 (11.03%)\n10,880,610Os membros do grupo ASF foram submetidos a exames de rastreio\n9,680,599Nunca foi banido — 88.97%\n1,200,011Aplicar qualquer proibição — 11.03%\n55 minPara contabilizar tudo isso, com uma única chave API\nO que esta frota já pagou Valve para existir\n\nNão se trata de uma estimativa dos rendimentos da quinta. Trata-se de um valor mínimo do que já foi gasto na loja de Valve — calculado a partir da própria regra de Valve, aplicada à contagem acima.\n\nA contagem 10,880,610 abrange a lista completa de membros do grupo ASF, tal como é devolvida pela API — isto inclui tanto contas com restrições como contas sem restrições. A própria Steam Contas de utilizador com acesso limitado A página indica que as contas com restrições não contar para Steam pertencem ao grupo (são excluídos do número de membros do grupo apresentado), mas podem ainda assim constar na lista de membros subjacente. O subconjunto não limitado — contas que gastaram pelo menos $5.00 na loja Steam — é exatamente 5,360,499 — a contagem Steam é apresentada na página do grupo, a qual, de acordo com a própria regra de Steam, exclui as contas com restrições. O cálculo do limite mínimo $5.00 aplica-se apenas a esse subconjunto sem restrições.\n\n5,360,499membros sem restrições\n(Número de grupos apresentados por Steam)\n×\n$5.00O mínimo próprio de Valve\npara deixar de estar limitado\n=\n$26,802,495limite mínimo de gastos na loja\npelo subconjunto não limitado\n\nEste valor representa o limite inferior do montante já recebido por Valve da parte não limitada da frota — não se trata de uma estimativa de receitas, nem de uma declaração de lucros. A despesa real por conta é superior na maioria dos casos; o valor $5.00 corresponde apenas ao limiar mínimo exigido.\n\nA colheita secundária: comissão de até 66.7% sobre o volume de produtos cultivados. Para além da taxa de entrada de $26.8M, cada cartão e artigo vendido no Mercado Comunitário paga Valve, sendo esta uma taxa mínima obrigatória de dois cêntimos ($0.01 Steam de taxa + $0.01 de taxa do editor). No caso de cartas típicas de 3 cêntimos e de itens sem valor, Valve retira 2 cêntimos de 3 cêntimos — um corte efetivo de 66.67% a favor de Valve, ultrapassando largamente a taxa de marketing anunciada de 15%.\n\nObservação importante sobre a população: A pertença a um grupo não constitui prova de que todas as contas sejam bots dedicados, nem abrange todos os bots no Steam. Por predefinição, a ASF inscreve automaticamente as contas no seu grupo comunitário logo após o arranque; a menos que o utilizador desmarque explicitamente ou desative essa opção de configuração (AutoJoinSteamGroup), jogadores regulares, utilizadores ocasionais e membros da comunidade permanecem na lista juntamente com frotas de farming automatizadas. Além disso, uma suspensão Steam não inclui qualquer justificação pública. A conclusão é uma taxa empírica para toda esta população associada ao software, não um veredicto individual sobre qualquer conta específica. Agregada, reprodutível: asf-ban-census-2026-09-23.json.\n\n02 — Geografia\nOnde se encontra a frota\n\nApenas 8.5% das contas banidas indicam um país. Entre as que o fazem, a maior percentagem corresponde aos Estados Unidos.\n\nUm perfil Steam inclui um campo opcional relativo ao país. 100,413 das 1,182,811 contas banidas preenchem-no — 8.5%.† Entre essa minoria, os Estados Unidos lideram com 15.5%, seguidos pela Ucrânia, China e Rússia, e o resto distribui-se numa longa cauda pela Europa, América Latina e Sudeste Asiático. Ninguém verifica os dados: o Afeganistão figura entre os dez primeiros, o que corresponde, grosso modo, ao seu valor. Os restantes 91.5% são omitidos em vez de atribuídos, pelo que o que se segue é o retrato de uma minoria auto-selecionada — não um mapa da frota, nem uma base para determinar de onde esta é gerida.\n\nContas banidas por país declarado\n\nOs 15 principais países entre as 100,413 contas banidas que revelam uma localização pública. A percentagem refere-se a esse subconjunto localizado. Passe o cursor para ver os números.\n\n0%\n5%\n10%\n15%\n20%\nUnited States\nUkraine\nChina\nRussia\nCanada\nAustralia\nJapan\nBrazil\nGermany\nAfghanistan\nUnited Kingdom\nRomania\nFrance\nPhilippines\nIndia\n\nLocalização lida a partir de GetPlayerSummaries para o subconjunto de endereços bloqueados. O campo é definido pelo titular da conta e não é verificado por ninguém, pelo que um endereço de saída de VPN ou uma entrada inventada têm o mesmo valor que um endereço real.\n\n03 — Frescura\nContas recentes, e não um volume de trabalho acumulado do passado\n\nA julgar pela data de criação das contas, a população banida é recente, não sendo um resquício da era das cartas colecionáveis.\n\nSe isto fosse uma confusão antiga que estivesse a ser lentamente resolvida, as contas banidas concentrar-se-iam nos primeiros anos dos cartões colecionáveis. Mas acontece o contrário. Das 1,132,852 contas banidas que revelam uma data de criação, 70% foram criados em 2020 ou mais tarde, e quase metade desde 2023. O número passa de 59,175, criado em 2017, para um pico de 227,030 criados só em 2024. Cada um deles passou pelo portão da loja $5.00 antes de esta poder registar o cartão, pelo que foi cobrada a taxa de entrada a cada um.\n\nQuando as contas banidas foram criadas\n\nAno de criação das contas dos 1,132,852 membros banidos cuja data de criação está visível. O período abrange 2020–2026, e não a era dos cartões colecionáveis de 2013–2015. Pico: 2024. Passe o cursor para ver os números.\n\n0k\n63k\n125k\n188k\n250k\n'13\n'14\n'15\n'16\n'17\n'18\n'19\n'20\n'21\n'22\n'23\n'24\n'25\n'26\n70%Das contas banidas criadas em 2020 ou posteriormente\n227,030Contas banidas criadas em 2024 — o ano de maior número\n51,701A quebra registada em 2021, entre dois anos de picos — sem explicação\n2003→2026Existem dados disponíveis, mas a massa refere-se aos últimos seis anos\n\nA criação remonta a GetPlayerSummaries para o subconjunto de contas banidas, deduplicado por SteamID64. A data de criação corresponde à data em que a conta foi criada, e não à data em que foi banida ou em que começou a praticar «farming»; é aqui interpretada como prova da recência da população, e não de intenção. Três aspetos que o gráfico não mostra:\n\nUma tendência a partir de 2024. Uma conta criada em 2025 ou 2026 teve menos tempo para acumular um banimento, e 2026 abrange nove meses — por isso, 227,030 → 121,070 → 16,534 representa uma censura, e não um declínio.\nUma taxa de proibição. Os anos de criação foram analisados apenas para as contas banidas, pelo que não existe um denominador. O simples facto de a base de utilizadores estar a crescer já seria suficiente para explicar esta tendência.\nPor que razão 2021 foi um fracasso. O 51,701 situa-se entre o 105,821 e o 104,641, abaixo da metade de qualquer um dos vizinhos. Não há nenhuma explicação pública para isso; é deixado visível, em vez de ser suavizado.\n04 — Tempo\nQuando Valve entra em vigor, faz-se sentir no primeiro ano\n\nA justificação óbvia para o 88.97% não ter sido alterado é a existência de um atraso na tramitação. As proibições anteriores indicam o contrário.\n\nHá quanto tempo a conta já existia quando a suspensão foi aplicada\n\nAntiguidade da conta no momento do bloqueio, para as 293,750 contas bloqueadas que apresentam tanto uma data de criação como uma data do último bloqueio. Mais de metade foi detetada no primeiro ano.\n\n0%\n10%\n20%\n30%\n40%\n<6 mo\n33.7%\n6–12 mo\n21.5%\n1–2 y\n20.6%\n2–5 y\n14.3%\n5 y+\n10.0%\n55.1% inside the first year\nBanido no primeiro ano — 55.1%Banido mais tarde — 44.9%\n0,80 anosIdade mediana da conta no momento em que a proibição foi aplicada\n55.1%Banido no primeiro ano da conta\n33.7%Banido nos primeiros seis meses\n293,750Contas em que ambas as datas estão presentes\n\nEsta é a resposta à objeção óbvia. Se 88.97% da frota não for afetada porque a aplicação da lei é simplesmente lenta — um atraso que está a ser resolvido —, então as proibições que fazer os dados poderiam parecer desatualizados. Na verdade, o que acontece é o contrário: a mediana das contas banidas era com nove meses e meio de idade, e um terceiro — 33.7% — foi capturado no espaço de seis meses. Quando Valve atua sobre esta população, age rapidamente. Os nove em cada dez que ainda andam à solta não estão à espera numa fila.\n\nIdade na data da proibição = data de criação a partir de GetPlayerSummaries subtraída da data de proibição implícita em DiasDesdeoÚltimoBanimento, continue a ler 2026-09-23. É calculado apenas quando ambos os valores estão presentes: 293,750 das 1,200,011 contas banidas. As restantes contas não apresentam qualquer valor de «dias desde» e são omitidas, não sendo consideradas — por isso, interprete isto como a forma do subconjunto datado, e não de cada proibição.\n\n05 — Em que consiste, na verdade, a proibição\nQuando o Valve é executado, não interrompe o bot\n\nDos 11% que estão sujeitos a alguma proibição, verifica qual é a proibição.\n\nUma proibição não é uma proibição. Das 1,200,011 contas que Valve sinalizou, 99.8% transportar um comunidade proibição — uma restrição em fóruns, perfis e grupos que não afeta de forma alguma um bot de trocas. A conta continua a poder receber cartas, a fazer trocas e a movimentar o inventário. 22.2% ter pelo menos um banimento de jogo e 3.9% um banimento de VAC; as categorias sobrepõem-se, pelo que não se somam. A única sanção que realmente impede as transações, o banimento económico/comercial, aplica-se a 5,214 contas. Não estamos a basear o nosso argumento nesse número — os banimentos de comércio são raros em Steam, de um modo geral. O objetivo deste gráfico é mais simples: mesmo a fração Valve faz A Touch continua a negociar.\n\nPor que razão é que os 11% que foram banidos foram, de facto, banidos?\n\nCada tipo de banimento representa uma percentagem do total de 10,880,610 membros analisados. As contas podem ter mais do que um. Passe o cursor para ver os números.\n\n0%\n4%\n8%\n11%\n15%\nCommunity ban\nGame ban\nVAC ban\nEconomy / trade ban\n\nUma proibição do tipo Steam não inclui um campo de justificação, pelo que nenhuma destas proibições se refere especificamente à acumulação de cartas — trata-se da combinação de tipos de proibição existentes, juntamente com o que cada tipo efetivamente restringe. A proibição por decisão da comunidade não impede as trocas; a proibição económica/comercial, sim. Resumo: asf-ban-census-2026-09-23.json.\n\n06 — A outra população\nOs burlões Valve, vamos lá: O 51,732 Censo Completo\n\nUma segunda lista independente — fraudes confirmadas pela comunidade — comparada com a mesma API oficial.\n\nPoder-se-ia argumentar que o grupo da automação é composto por ociosos inofensivos. O mesmo não se pode dizer do segundo grupo. SteamRep é uma base de dados de reputação comunitária que existe há muito tempo; uma conta marcada PROIBIDO essa comunidade considerou essa pessoa um burlão, com provas documentadas das vítimas e registos de conversas sobre as transações. Concluímos um recenseamento 100% de todos os 51,732 perfis com o estado «BANIDO» em comparação com a API Web oficial do Steam (ISteamUser/GetPlayerBans/v1) — e contabilizou apenas as sanções relacionadas com fraudes. Uma suspensão VAC destina-se a software utilizado para fazer batota num jogo (aimbots, wallhacks); não tem qualquer impacto sobre um trader e não constitui prova Valve de fraude, pelo que não é contabilizada como medida de combate à fraude.\n\nEm todo o recenseamento de contas 51,732, 67.77% — 35,059 golpistas condenados — não têm NENHUMA suspensão relacionada com fraudes por parte de Valve: eles continuam a poder fazer transações, a enviar pedidos de amizade a novas vítimas e a enviar mensagens. Apenas 32.23% foram alvo de um banimento da comunidade ou de transações, e o banimento de transações — a única medida que realmente impede as transferências de inventário — aplica-se a apenas 18.81% (9,731 contas). Outros 12.81% (6,627 contas) têm VAC ou mais proibições de jogo exclusivamente por batota no jogo, mantendo-se, no entanto, completamente sem restrições em Steam transações.\n\nGolpistas confirmados, consoante se Valve aplicou ou não uma suspensão relacionada com fraude (Censo Completo)\n\nTodos os perfis 51,732 SteamRep-BANNED, divididos consoante a Valve tenha aplicado uma proibição da comunidade ou comercial. As proibições VAC e de jogo estão excluídas — estas não se referem a fraudes. Passe o cursor para ver os números.\n\n0%\n18%\n35%\n53%\n70%\nNo scam-relevant ban\nCommunity or trade ban\n0%\n6%\n13%\n19%\n25%\nCommunity ban\nTrade / economy ban\nVAC (not fraud)\nGame ban\n51,732SteamRep perfis BANNED auditados — 100% recenseamento completo\n35,059Não tem qualquer suspensão relacionada com fraudes (67.77%)\n18.81%Aplicar a proibição comercial que põe fim aos esquemas fraudulentos (9,731)\n32.23%A ação Valve foi alvo de uma proibição comunitária ou comercial (16,673)\n\nSteamRep é uma base de dados de reputação de terceiros, avaliada pela comunidade, e não uma determinação Valve — e é precisamente essa a questão: provas externas, comparadas com o que o próprio Valve fez. Todos os perfis 51,732 BANIDOS da exportação canónica foram cruzados diretamente com ISteamUser/GetPlayerBans/v1. «Relacionado com fraudes» significa uma proibição de acesso à comunidade ou à economia/comércio; VAC (12.81%) e as proibições de jogo (3.86%) são contabilizadas separadamente, uma vez que se referem a batota e não a fraude. Conjunto de dados completo da auditoria: steamrep_steam_bans.csv.\n\nDuas populações, uma descoberta\n\nNão se trata das mesmas pessoas nem do mesmo tipo de conduta. Num caso, são dez milhões de contas automatizadas; no outro, são cinquenta e três mil burlões condenados. O que têm em comum é a forma do resultado: nove em cada dez contas agrícolas nunca são utilizadas, e mais de dois terços (67.77%) dos autores de fraudes confirmados não enfrentam qualquer sanção relacionada com a fraude. A proibição da comunidade Valve restringe livremente fóruns e perfis, mas não as transações comerciais. O botão de denúncia, a base de dados de reputação, a proibição que impede um esquema fraudulento: tudo isso está presente, mas é pouco utilizado. Compare isso com as recusas arquivadas no dossiê principal, onde a mesma empresa remove definitivamente uma única conta e invoca a utilização comercial e a automatização como motivo — a cláusula não está inativa, é bem clara.\n\n07 — O caso «$5.00» e o sequestro de contas\nA auditoria empírica às contas «100,000»: as botnets não são contas gratuitas descartáveis\n\nLógica da amostragem estatística e demonstração matemática: por que razão a escolha de qualquer outro valor de 100,000 conduz exatamente ao mesmo resultado.\n\nA principal defesa da Valve perante as entidades reguladoras e os organismos de defesa do consumidor tem sido a de que os esquemas fraudulentos automatizados e o «farming» são levados a cabo por contas efémeras e gratuitas, do tipo «descartáveis», que são rapidamente banidas. De acordo com as regras publicadas pela Valve, uma conta é Limitada até gastar pelo menos 5.00s de dólares americanos na loja Steam, o que o impede de realizar transações, enviar pedidos de amizade e utilizar funcionalidades da API. Verificámos esta afirmação diretamente, testando o estado de monetização de uma amostra representativa e matematicamente rigorosa de 100,000 contas Steam banidas extraídos do nosso corpus de metadados de perfis 1,182,811.\n\nPROTOCOLO DE AMOSTRAGEM (SRSWOR)\n100,000 Secção imparcial\n\nExtraído de N = 1,182,811 contas únicas banidas Steam através de uma amostragem aleatória simples sem reposição, utilizando um gerador de números aleatórios pseudoaleatórios (PRNG) criptograficamente uniforme. Cada conta tinha uma probabilidade de inclusão idêntica de P = n / N ≈ 8.45%, eliminando completamente os enviesamentos de sobrevivência e de atividade.\n\nPROVA MATEMÁTICA\nMargem de erro < ±0.4%\n\nAplicando a fórmula da Correção de População Finita (FPC) a um 99% Intervalo de confiança (Z = 2,576):\nMoE = Z × √[p(1-p)/n] × √[(N-n)/(N-1)] ≈ ±0.39%\n\nREPRODUTIBILIDADE\nPor que razão qualquer 100 mil rende o mesmo\n\nUma vez que a margem de erro está limitada a ±0.4% com um nível de confiança de 99%, está matematicamente garantido que qualquer outra amostra independente da conta 100,000 se situará no intervalo 63.06% ± 0.39% (62.67% a 63.45%). A amostra reflete a totalidade da população de 1,18 milhões de pessoas banidas.\n\nOs resultados da auditoria desmentem completamente a alegação de que se tratava de «bots descartáveis». Das 100,000 contas auditadas através da interface de perfil XML legada do Steam: 61,490 contas (63.06% das contas classificadas) são contas sem limites (pagas) que gastaram, pelo menos, $5.00 em Steam. Apenas 36,021 (36.94%) são contas gratuitas limitadas, enquanto 2,489 estavam por configurar ou eram privadas.\n\n100,000 Contas banidas: Pagas ($5+ Gastos na loja) vs. Contas gratuitas com estatuto limitado\n\nAuditoria empírica de 100,000 contas banidas selecionadas aleatoriamente. Mais de 63% ultrapassaram o controlo financeiro pago de Valve. Passe o cursor para ver os números.\n\n0%\n16%\n33%\n49%\n65%\nNon-limited (Paid ≥ $5.00)\nLimited (Free < $5.00)\n100,000População amostral (SRSWOR, N = 1,18 milhões)\n63.06%Contas pagas sem restrições (contas 61,490)\n±0.39%Margem de erro no intervalo de confiança de 99%\n~745,800Contas pagas extrapoladas num conjunto de dados de 1,18 milhões de contas banidas\nA realidade estrutural: liquidação de contas à escala industrial\n\nPor que razão 63% das contas banidas incluídas na amostra seriam contas pagas que gastaram dinheiro real na loja de Valve? Os operadores de botnets não gastam milhões do próprio bolso em contas descartáveis. Esta proporção destaca o volume de contas comprometidas e pirateadas que circulam pelo ecossistema.\n\nEsta escala é diretamente observável em plataformas subterrâneas: em mercados como o FSB Market (nome anonimizado; o nome original não é indicado aqui), entre outros 550,000 Steam contas (registos de roubo de dados, capturas de phishing, preenchimento de credenciais) estão ativamente à venda a qualquer momento (phishdestroy.io/live-intel). O mercado autentica compradores e vendedores utilizando o OpenID Steam próprio do Valve, e nem FSB Market nem o fórum associado está bloqueado pelo Filtro de Links do Valve.\n\nConforme estabelecido na Secção 06, o Valve não elimina de forma proativa esta atividade fraudulenta: 67.77% dos burlões confirmados pela comunidade não têm qualquer proibição por burla no Steam, e 88.97% da frota de automação permanece completamente intocada. As contas circulam livremente, autenticam-se através de APIs oficiais e realizam transações em todo o ecossistema com impunidade quase total.\n\nDiagrama da arquitetura de provas forenses e aplicação da lei\nFluxo interativo de 10,88 milhões de contas analisadas para uma amostra empírica de 100 mil e 53,5 mil burlões confirmados · Clique nas ligações para consultar as provas em bruto\nNível 01 · Censo da frota de automação: 10,88 milhões\nA maior população de bots que se autodefine como «de automação» no Steam passou sequencialmente pela API de bloqueio oficial do Valve. Isto prova que as frotas de bots comerciais operam com total impunidade no 88.97%, apesar de pagarem dezenas de milhões em taxas de entrada.\n9,680,599 88.97% Ativo e intacto\nContas que utilizam software automatizado e que não têm qualquer tipo de bloqueio registado.\nJSON bruto do Censo (1,2 KB) ↗Consulte a Secção 01 ↗\n$26,802,495 Limite mínimo de receitas diretas da loja\nRecolhido por Valve de 5,360,499 membros sem restrições, para além do limiar mínimo de entrada de $5.00.\nAuditoria à economia dos cartões ↗Valve $5 Perguntas frequentes sobre as regras ↗\n1,200,011 11.03% Subconjunto marcado\n99.8% estão sujeitas apenas a restrições de natureza meramente cosmética; a atividade de negociação permanece aberta em 99.95% das contas.\nDiscriminação por tipo de suspensão ↗Base de dados banida (60,4 MB) ↓\nNível 02 · 100,000 – Auditoria por amostragem empírica de contas (N = 1,182,811)\nAmostra representativa de SRSWOR, avaliada através de pontos de acesso XML antigos. Margem de erro matematicamente comprovada < ±0.4% num intervalo de confiança de 99%. Refuta a alegação de que os bots banidos são contas descartáveis gratuitas.\n61,490 (63.06%) Contas pagas sem limites ($5+ Gastos)\nMais de 63% das contas banidas correspondem a transações pagas. Isto traduz-se em cerca de 745,800 contas pagas (limite mínimo de $3.73M+) no conjunto de contas banidas.\nResultados limitados em CSV (2,1 MB) ↓Relatório forense de 100 mil ↗\n36,021 (36.94%) Contas gratuitas com funcionalidades limitadas (< $5.00)\nA minoria de perfis banidos que se enquadram no perfil de «bot descartável» definido por Valve. As contas 2,489 estavam sem configuração ou eram privadas.\nFicheiro CSV com uma amostra de 100 mil registos (8,5 MB) ↓Análise de despesas MD ↗\n34.67% vs 63.93% Auditoria à higienização de perfis\nValve apagou as alcunhas, substituindo-as pelo SteamID64 sem formatação em 34,673 contas, mas deixou os nomes personalizados e os avatares completamente inalterados em 63,928 contas banidas.\nSecção de Higienização ↗Visão geral do roteiro ↗\n34.59% Legado Contas antigas (criadas entre 2003 e 2019)\nMais de um terço das contas banidas foram registadas há 5 a mais de 20 anos, o que comprova a existência de um sequestro de contas em escala industrial de jogadores de longa data Steam.\nCronologia por idades ↗Recusas de apoio ↗\nNível 03 · 51,732 SteamRep Censo de burlões confirmados\nCenso completo 100% de fraudadores julgados pela comunidade, com registos de conversas das vítimas e provas de transações, cruzados com as APIs oficiais Steam de banimento. Comprova a falha sistémica na aplicação das regras.\n35,059 (67.77%) Zero suspensões por fraude (impunidade total)\nMais de dois terços dos fraudadores confirmados não têm proibições de comunidade nem de comércio do Valve. Estão totalmente operacionais para negociar e adicionar vítimas.\nSteamRep Restrições à API (2,6 MB) ↓SteamRep Relatório de auditoria ↗\n9,731 (18.81%) Economia / Proibições comerciais\nA única sanção que interrompe a liquidação de existências. Presente em menos de um quinto dos burlões confirmados.\nSteamRep Fonte (2,1 MB) ↓Consulte a Secção 06 ↗\n6,627 (12.81%) Suspensões por batota irrelevantes (apenas VAC)\nBanidos por utilizarem aimbots/wallhacks nos jogos, enquanto as suas capacidades de Steam comércio e phishing permanecem 100% ativas.\nVAC Análise de irrelevância ↗Cronologia de segurança ↗\nNível 04 · Alteração de conteúdo em wikis e violações de infraestruturas em agosto de 2026\nA alteração da documentação interna dos programadores, a restrição dos editores da comunidade e as falhas no perímetro não protegido, documentadas no pacote de provas.\n1,200+ Editores Registos de conflitos da VDC Wiki\nOs editores da comunidade que tentavam corrigir links de phishing e modelos de spam foram sistematicamente bloqueados por filtros automáticos, enquanto a equipa Valve ignorava os avisos.\nRelatório sobre os conflitos na Rússia (127 KB) ↗Relatório de classificação (66 KB) ↗\n12 TB sem autenticação Agosto de 2026 – Fuga de ativos (CWE-284)\nValve manteve, durante semanas, 12 terabytes de código interno e versões protótipo num ponto de acesso público aberto, sem autenticação.\nValve Dossiê sobre a incompetência (43 KB) ↗Arquivo de Provas ↗\nViolação de segurança na CEVA Logistics Vazamento de dados pessoais identificáveis (PII) de clientes em agosto de 2026\nOs nomes, endereços e números de telefone dos compradores europeus do Steam Deck foram divulgados por um parceiro logístico da Valve, o que desencadeou uma onda de tentativas de phishing.\nRegisto de Incidente ↗Registo de medidas coercivas ↗\n\nArtefacto de amostragem: banned_100k_slice.csv (100,000 contas). Resultados da auditoria: slice_100k_limited_results.csv. Relatório analítico completo: BANNED_100K_FORENSIC_ANALYSIS.md.\n\n08 — Método e limites\nComo isto foi interpretado e o que não afirma\n\nTrês populações públicas, uma API pública, amostragem estatística rigorosa.\n\nEXECUÇÃO E CREDENCIAIS\n\nO recenseamento da ASF, a fatia 100,000-conta SRSWOR e a SteamRep verificação cruzada foram executados por PhishDestroy participantes através das suas próprias Steam contas e chaves da API Web, no âmbito do trabalho público da Coligação de combate ao phishing e à proibição de esquemas fraudulentos. O autor do dossiê não possui nenhuma Steam chave de API Web e não realizou pessoalmente nenhuma verificação em tempo real. A agregação, o hash, a verificação e a publicação foram efetuados a partir dos resultados dos participantes.\n\nPopulação\tDe onde veio\tO que foi lido\nMembros da ASF\n10,880,610\tA lista pública de membros do grupo comunitário ArchiSteamFarm Steam. A página do grupo de Steam apresenta 5,360,499 membros (apenas os não restritos); a lista de membros da API devolveu 10,880,610 entradas no total, incluindo contas restritas. A adesão ao grupo é automática na primeira execução, a menos que o utilizador desative explicitamente a definição predefinida de adesão ao grupo na configuração (AutoJoinSteamGroup / Estatísticas), o que significa que a lista de membros inclui grupos de bots comerciais, utilizadores individuais que mantêm os seus cartões inativos e jogadores regulares que deixaram a opção predefinida ativada.\tGetPlayerBans para cada membro (sinalizações de banimento); GetPlayerSummaries para datas de criação e país. Agrupados em lotes de 100 IDs, com eliminação de duplicados por SteamID64.\n100 mil contas banidas SRSWOR Faixa\n100,000\tUma amostra representativa selecionada aleatoriamente de forma uniforme, sem reposição, a partir do conjunto de contas banidas 1,182,811 ($P = 8,45\\%$). A correção para população finita resulta numa margem de erro de $\\pm 0,39\\%$ a um nível de confiança de 99% ($Z = 2,576$).\tMonetização e estado de conta limitada (isLimitedAccount) auditado através da interface de perfil XML legada do Steam (?xml=1) através de pipelines de proxy distribuídos. Confirma o estado 63.06% (pago).\nSteamRep burlões\n51,732\tRealização do 100% recenseamento de todos os perfis marcados como «BANNED» na SteamRep base de dados de reputação da comunidade (51,732 perfis no total). Não foi aplicada qualquer amostragem nem filtragem.\tISteamUser/GetPlayerBans/v1 para todas as contas 51,732, cruzadas com o estado SteamRep. Confirma que 67.77% está isento de quaisquer restrições por fraude.\nO que se reivindica\n\nApenas taxas empíricas e estimativas estatisticamente delimitadas. Na população de automação, 88.97% não apresentam qualquer restrição; o subconjunto restrito concentra-se nos períodos mais recentes (70% desde 2020). Na auditoria empírica das contas 100,000, 63.06% das contas banidas são pagas (não limitadas), com uma margem de erro matematicamente comprovada inferior a ±0.4%. Entre os 51,732 burlões confirmados, 67.77% não têm qualquer restrição relacionada com burlas. Todos os valores são reprodutíveis a partir da própria API Web de Valve.\n\nO que não é reivindicado\n\nUm ban Steam não inclui um campo de justificação, pelo que nenhum ban aqui é atribuído a uma causa específica. A pertença a um grupo não constitui prova de que uma conta seja um bot automatizado: uma vez que a ASF permite, por predefinição, a adesão a grupos, a menos que essa opção seja desmarcada manualmente, a população mistura «fazendas» comerciais de múltiplas contas com contas pessoais de jogadores comuns e amadores. O país é declarado pelo próprio utilizador, e uma menção SteamRep é uma decisão da comunidade, não uma sentença judicial. Não é referido o nome de nenhum indivíduo.\n\nPor que é importante\n\nO Valve dispõe da mesma API, da sua própria base de dados e dos motivos de banimento que esta análise não consegue detetar. Consegue executar esta consulta em todo o espaço de IDs em segundos. A métrica que permite a uma entidade externa verificar uma alegação de aplicação de sanções relativamente a um número nunca foi publicada pela única entidade capaz de a produzir com total fiabilidade. Esta é a estimativa externa, apresentada para que a questão possa ser colocada acompanhada de um valor concreto.\n\nLeia a seguir: a economia baseada em cartões que esta população gere → · apoio ao acesso e ao roubo → · o dossiê completo →",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Qual é o tamanho da operação no Steam? Nós a contamos."
          },
          {
            "level": 2,
            "id": null,
            "text": "Dez milhões de contas, e nove em cada dez não foram utilizadas"
          },
          {
            "level": 3,
            "id": null,
            "text": "A ASF junta-se ao grupo por si"
          },
          {
            "level": 3,
            "id": null,
            "text": "10,880,610 entradas no total"
          },
          {
            "level": 3,
            "id": null,
            "text": "88.97% limpo"
          },
          {
            "level": 3,
            "id": null,
            "text": "Das 10,880,610 contas, quantas Valve foram utilizadas"
          },
          {
            "level": 3,
            "id": null,
            "text": "O que esta frota já pagou Valve para existir"
          },
          {
            "level": 2,
            "id": null,
            "text": "Onde se encontra a frota"
          },
          {
            "level": 3,
            "id": null,
            "text": "Contas banidas por país declarado"
          },
          {
            "level": 2,
            "id": null,
            "text": "Contas recentes, e não um volume de trabalho acumulado do passado"
          },
          {
            "level": 3,
            "id": null,
            "text": "Quando as contas banidas foram criadas"
          },
          {
            "level": 2,
            "id": null,
            "text": "Quando Valve entra em vigor, faz-se sentir no primeiro ano"
          },
          {
            "level": 3,
            "id": null,
            "text": "Há quanto tempo a conta já existia quando a suspensão foi aplicada"
          },
          {
            "level": 2,
            "id": null,
            "text": "Quando o Valve é executado, não interrompe o bot"
          },
          {
            "level": 3,
            "id": null,
            "text": "Por que razão é que os 11% que foram banidos foram, de facto, banidos?"
          },
          {
            "level": 2,
            "id": null,
            "text": "Os burlões Valve, vamos lá: O 51,732 Censo Completo"
          },
          {
            "level": 3,
            "id": null,
            "text": "Golpistas confirmados, consoante se Valve aplicou ou não uma suspensão relacionada com fraude (Censo Completo)"
          },
          {
            "level": 4,
            "id": null,
            "text": "Duas populações, uma descoberta"
          },
          {
            "level": 2,
            "id": null,
            "text": "A auditoria empírica às contas «100,000»: as botnets não são contas gratuitas descartáveis"
          },
          {
            "level": 3,
            "id": null,
            "text": "100,000 Secção imparcial"
          },
          {
            "level": 3,
            "id": null,
            "text": "Margem de erro < ±0.4%"
          },
          {
            "level": 3,
            "id": null,
            "text": "Por que razão qualquer 100 mil rende o mesmo"
          },
          {
            "level": 3,
            "id": null,
            "text": "100,000 Contas banidas: Pagas ($5+ Gastos na loja) vs. Contas gratuitas com estatuto limitado"
          },
          {
            "level": 3,
            "id": null,
            "text": "A realidade estrutural: liquidação de contas à escala industrial"
          },
          {
            "level": 2,
            "id": null,
            "text": "Como isto foi interpretado e o que não afirma"
          },
          {
            "level": 3,
            "id": null,
            "text": "O que se reivindica"
          },
          {
            "level": 3,
            "id": null,
            "text": "O que não é reivindicado"
          },
          {
            "level": 3,
            "id": null,
            "text": "Por que é importante"
          }
        ],
        "links": [
          "https://help.steampowered.com/en/faqs/view/71D3-35C2-AD96-AA3A",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/asf-ban-census-2026-09-23.json",
          "https://phishdestroy.io/steam_dossier/pt/VALVE_EVIDENCE_PACK/databases/steamrep_steam_bans.csv",
          "https://phishdestroy.io/live-intel/?category=steam",
          "https://phishdestroy.io/steam_dossier/pt/card_economy.html",
          "https://phishdestroy.io/steam_dossier/pt/VALVE_EVIDENCE_PACK/databases/banned_archiasf_massive.csv",
          "https://phishdestroy.io/steam_dossier/pt/VALVE_EVIDENCE_PACK/databases/slice_100k_limited_results.csv",
          "https://phishdestroy.io/steam_dossier/pt/VALVE_EVIDENCE_PACK/reports/BANNED_100K_FORENSIC_ANALYSIS.md",
          "https://phishdestroy.io/steam_dossier/pt/VALVE_EVIDENCE_PACK/databases/banned_100k_slice.csv",
          "https://phishdestroy.io/steam_dossier/pt/VALVE_EVIDENCE_PACK/reports/STEAM_BANNED_LIMIT_ANALYSIS.md",
          "https://phishdestroy.io/steam_dossier/pt/VALVE_EVIDENCE_PACK/INVESTIGATION_OVERVIEW.md",
          "https://phishdestroy.io/steam_dossier/pt/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/pt/VALVE_EVIDENCE_PACK/reports/STEAMREP_VS_STEAM_AUDIT.md",
          "https://phishdestroy.io/steam_dossier/pt/VALVE_EVIDENCE_PACK/databases/SteamRep_Profiles_BannedCaution_2024.csv",
          "https://phishdestroy.io/steam_dossier/pt/security_timeline.html",
          "https://phishdestroy.io/steam_dossier/pt/VALVE_EVIDENCE_PACK/reports/russian_conflicts_report.json",
          "https://phishdestroy.io/steam_dossier/pt/VALVE_EVIDENCE_PACK/reports/classification_report.json",
          "https://phishdestroy.io/steam_dossier/pt/VALVE_EVIDENCE_PACK/reports/VALVE_INCOMPETENCE_REPORT.md",
          "https://phishdestroy.io/steam_dossier/pt/steam_evidence_archive.html",
          "https://phishdestroy.io/steam_dossier/pt/steam_enforcement_evidence.html",
          "https://phishdestroy.io/steam_dossier/pt/#insider-threat",
          "https://phishdestroy.io/steam_dossier/pt/"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/pt/enforcement_audit.content.json",
      "export_json_sha256": "e295cc9ea617184ca35d0771915b7ff1f9e582c03d7381db1e8cdd8810f7867f"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "pt/index.html",
      "language": "pt",
      "title": "O Dossiê Steam: regras, percursos e responsabilização",
      "source_url": "https://phishdestroy.io/steam_dossier/pt/index",
      "source_html_sha256": "7cc01696cfc4914fd65acfdeeed8d33ba32f24565a36b50dc1ba60fad39c3311",
      "exported_at": "2026-09-29T00:18:10.096Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "exhibit-gallery-section",
            "source": "https://phishdestroy.io/steam_dossier/pt/index#exhibit-gallery-section"
          }
        ],
        "raster_images_replaced": 2
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "index.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/pt/index.pdf?v=print-20260929-v5",
        "sha256": "2f7eabffb05c6f49061ed3b295f1d02162399dbc8fea0e53baa209f19900fe11",
        "bytes": 967081,
        "pages": 108
      },
      "integrity": {
        "signed_object": "index.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "index.content.json.asc",
        "digest_file": "index.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify index.content.json.asc index.content.json",
          "sha256sum -c index.content.json.sha256"
        ]
      },
      "content": {
        "text": "Secção 1 — Resumo do processo\nA regra. O recorde. As questões por responder.\nContexto e limites da fonte\n\nSeis conclusões, cada uma delas associada a um registo público datado. As secções detalhadas seguem a mesma ordem: registo técnico (Parte A), regras e registo de aplicação (Parte B), quadros jurídicos (Parte C) e, por fim, os anexos com as provas principais.\n\nSeis conclusões. Cada uma delas associa uma regra escrita a um registo datado e a uma questão que as provas podem permitir avaliar.\n\n1. Hosts de autenticação de domínios separados — 44 rotas · 26 pares divididos\n\nOs registos do cadastro de desempregados 44 plataformas que se autenticam através de um domínio registável independente. Existem mais cinco percursos em fase de verificação, à espera de uma data de RDAP; a sua inclusão elevaria o total para 47. Estes percursos estão excluídos do número 44 e do quadro de idades. — 27 com um ficheiro de evidências publicado por rota e 17 adicionados a partir da recolha manual, listados separadamente. Em 26 pares de filtros divididos o domínio principal é BLOQUEADO no Filtro de Ligações Steam, ao passo que o proxy que contém o seu nome de utilizador não está. Não se trata de domínios temporários: o csgogem.com está bloqueado, enquanto api.csgem.com, o servidor com o nome de utilizador Steam, está registado desde março de 2014 — 12 anos e 6 meses. Valve recebe esse nome de anfitrião em cada pedido OpenID e apresenta-o ao utilizador na sua própria página de início de sessão. Tabela completa, idades por rota e origem na Secção 3.\n\nSiga o percurso →\n2. 2016: o mecanismo foi designado e o prazo foi definido\n\nEm 13 de julho de 2016, Valve descreveu publicamente como os sites de jogos de azar utilizavam Steam o OpenID e contas de negociação automatizadas, e as notificações do seu advogado, datadas de 20 de julho de 2016, estabeleceram um prazo de dez dias. Desde então, não foi publicado qualquer registo de aplicação da medida por operador. Dez anos após o estabelecimento desse prazo, o mesmo mecanismo mencionado está a ser utilizado em servidores de autenticação de domínios separados que não apresentaram qualquer bloqueio do Link Filter em 2026-09-21.\n\nLeia a carta aberta dirigida ao WSGC →\n3. Correlação de dispositivos, em papel timbrado do advogado\n\nNa correspondência aqui reproduzida, o advogado de Valve descreveu uma correlação ao nível do dispositivo que associa um dispositivo a várias contas — uma funcionalidade que o Apoio ao Cliente de Steam tinha anteriormente informado aos utilizadores que não era tecnicamente possível. A questão em aberto é saber que registos ao nível do dispositivo a Valve mantém e com base em que critérios é negado o acesso aos mesmos aos titulares das contas.\n\nLeia o memorando →\n4. Duas respostas de acesso. Uma recusou o acesso aos dados, a outra divulgou-os.\n\nOutubro de 2025: O advogado de Valve respondeu a um pedido ao abrigo do artigo 15.º com um apêndice de 830 páginas, em que as partes censuradas foram pintadas sobre o texto, em vez de serem removidas — 902,270 caracteres revelar informações com uma ferramenta de extração padrão, incluindo os identificadores de terceiros que as barras se destinavam a ocultar. O n.º 4 do artigo 15.º é a razão pela qual essas barras existem. Setembro de 2026: O ticket HT-2YBP-F7JP-D4VB foi encerrado ao fim de três dias com uma ligação para a página de autoatendimento «Dados da Conta» — sem dados, sem indicação de fundamento jurídico. O prazo de um mês previsto no n.º 3 do artigo 12.º ainda não tinha expirado à data da publicação; a objeção diz respeito ao conteúdo.\n\nLeia a verificação da redação →Ler o registo do bilhete →\n5. O mercado acima do teto de Steam\n\nSteam limita a cotação de uma empresa na bolsa a cerca de $1,800. Em cinco mercados, numa análise pontual com data específica (23 de setembro de 2026), 248 categorias de artigos CS2 seem ter preços superiores a esse limite por parte de dois ou mais deles, de forma independente, e todos os 248 estão ausentes de Steam; um Dragon Lore novo de fábrica custa a partir de $10,941 em 389 cópias listadas nas cinco plataformas (o valor relativo apenas ao CSFloat na Secção 13, proveniente do instantâneo de 20 de setembro, é de $10,623.95 em 62 ofertas). A venda a esses preços requer uma plataforma externa, enquanto a transferência de artigos continua a ser feita a Steam.\n\nAcompanha a cotação e a transferência →\n6. A regra é explícita; a pista de auditoria não é\n\nO Contrato de Subscrição reserva o Steam para uso pessoal e não comercial, proíbe a exploração comercial, salvo nos casos expressamente permitidos, proíbe scripts e bots e permite o encerramento da conta. O Valve aplicou essa disposição aos operadores de jogos de azar em 2016. Por outro lado, de acordo com a conta de engenharia da CSFloat, Valve encerrou IEconItems_730/GetPlayerItems em 2017, foi retirado o acesso público aos IDs dos itens originais (não foi encontrado nenhum registo de alterações Valve).\n\nColoque a regra ao lado da rede →\n2016 / Pedido por escrito 10 dias\nPrazo indicado nas notificações de julho de 2016 do advogado Valve aos sites de jogos de azar. Carta aberta à WSGC: Secção 2.\n2017 / Registo de auditoria público Acesso por identificação encerrado\nO CSFloat regista a perda dos IDs originais dos itens.\nCorrespondência com os advogados Correlação de dispositivos\nUm dispositivo associado a dezenas de contas roubadas.\nRegisto de percursos Bloqueado, mas continua a iniciar sessão\nA regra: A declaração de Valve de 2016 proíbe a exploração de um negócio de jogos de azar no OpenID Steam. O registo: O Filtro de Links contém 26 domínios principais, enquanto o servidor que aloja o login Steam de cada um deles está em funcionamento — o do csgogem.com já está em funcionamento há 12 anos e 6 meses.\nSecção 2 — Carta aberta\nCarta aberta à Comissão de Jogos de Azar do Estado de Washington\n\nDez dias transformaram-se em dez anos. A pergunta formulada pela Comissão em 2016 à Valve não foi respondida com um registo por operador; esta carta solicita que o processo seja reaberto.\n\nCOMUNICADO PÚBLICO · COMISSÃO DE JOGOS DE AZAR DO ESTADO DE WASHINGTON\n\nDez dias transformaram-se em dez anos.Reabra o registo.\n\nÀ Comissão de Jogos de Azar do Estado de Washington:\n\nEm 2016, o diretor David Trujillo solicitou à Valve que apresentasse as medidas que tinha tomado para impedir a utilização de skins Steam em jogos de azar. O então presidente Chris Stearns e a Comissão enfrentaram uma indústria assente em itens emitidos por Valve e transferências de Steam. Desde então, ambos deixaram os seus cargos na Comissão. A questão que colocaram à Valve continua em aberto.\n\nO conselheiro jurídico da Valve, Karl Quackenbush, concedeu aos operadores de jogos de azar um prazo de dez dias para cessarem a utilização comercial das contas da Steam. Na sua resposta de outubro à vossa Comissão, a Valve negou ter facilitado jogos de azar, afirmou ter enviado cartas de cessação e desistência a mais de quarenta sites e referiu ter desativado as contas associadas. Defendeu ainda a manutenção do serviço de transações Steam e do OpenID, uma vez que esses serviços beneficiavam os clientes e os criadores de jogos. Isso foi uma demonstração de controlo. Merece ser posta à prova, não deferência.\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\nNa nossa avaliação, a resposta da Valve não demonstrou que as medidas de aplicação da lei por ela escolhidas correspondessem à dimensão da rede que descreveu. Uma carta de ameaça enviada a um operador não é o mesmo que um bloqueio permanente das contas Steam, da infraestrutura de transações e das vias de autenticação que permitem o funcionamento do negócio. As estimativas divulgadas apontam para Só o CS:GO Lounge registou mais de $1 mil milhões em volume de apostas em 2016; trata-se de uma estimativa externa das apostas, não da receita Valve, e a operação original de apostas «skin» do site acabou por ser encerrada. A dimensão do fenómeno tornou essencial uma aplicação da lei verificável.\n\nHoje, o próprio Valve Contrato de Subscrição arquivado 2026-09-21 ↗ restringe a exploração comercial, salvo nos casos em que tal seja expressamente permitido, e proíbe separadamente formas específicas de automatização. O nosso registo de percursos desatualizado registos que indicam os servidores de resposta OpenID para serviços externos; openid.realm e openid.return_to são campos enviados para Steam, e não segredos que lhe são ocultados. Os nossos Verificações do filtro de links apresenta casos em que um endereço principal foi alvo de um aviso, mas um host de início de sessão associado não o foi. Um resultado de filtragem, por si só, não pode provar que Valve permitiu um início de sessão ou que um determinado bot contornou o bloqueio de uma conta. Isto prova, de facto, que um aviso na página inicial não pode ser considerado uma resposta completa no que diz respeito ao acesso.\n\nA existência de funções úteis e legais de comércio Steam e do OpenID também não permite determinar se os operadores proibidos foram efetivamente excluídos. As próprias regras de Valve permitem exceções expressas. Se a Valve se basear nessa distinção, a Comissão deverá solicitar-lhe que identifique a autorização, os controlos de contas e os critérios de aplicação aplicáveis às empresas comerciais de skins, bem como as utilizações específicas não relacionadas com jogos de azar que invocou em 2016. A mera possibilidade de utilização lícita não constitui resposta à utilização proibida documentada.\n\nSolicitamos à Comissão que reexamine o seu processo de 2016 e exija um relatório por operador: quais as contas Steam e os bots de negociação que foram desativados após os avisos de dez dias; se as contas relacionadas ou os servidores de retorno foram monitorizados; quais os operadores que posteriormente recuperaram o acesso; que isenções foram concedidas; e que registos corroboram a declaração de Valve à Comissão. Divulgue tudo o que a lei permitir que o público consulte. Compare esses registos com as rotas atuais e com as intervenções posteriores de Valve, incluindo OPSkins em 2018 arquivado 2026-03-07 ↗.\n\nO aviso estabeleceu um prazo de dez dias em julho de 2016; dez anos são tempo suficiente para determinar se tal foi levado a cabo. A Comissão deveria comparar o relatório de 2016 de Valve com as infraestruturas que ainda hoje são visíveis.\n\nA investigação do Dossier Steam · Declaração pública, 20 de setembro de 2026\n\nComunicação da Comissão de 2016 ↗ arquivado 2026-05-20 ↗ · Resposta de Valve de 2016 (cópia do documento) ↗ · Declaração de Valve sobre o OpenID de 2016 ↗ arquivado 2026-09-21 ↗ · Acordo atual Steam ↗ arquivado 2026-09-21 ↗ · Cronologia do intercâmbio de 2016: Secção 11 →\n\nParte A — Ficha técnica · Secção 3\nO site está bloqueado. A rota de início de sessão não está.\n\n26 domínios principais bloqueados. O proxy de autenticação por trás de cada um deles e há quanto tempo está ativo. Estes servidores de autenticação separados não são endereços secundários acidentais — cada um deles é um proxy de autenticação para Steam, situando-se entre a plataforma e o ponto final OpenID do Valve e transmitindo os dados de início de sessão que o domínio bloqueado já não pode transmitir abertamente. O Valve colocou a porta de entrada no Link Filter. O início de sessão continuou a ser efetuado através do proxy: o csgogem.com está bloqueado, e api.csgem.com está registado desde março de 2014 — doze anos e meio. Em cada um desses dias, esse servidor enviou o seu próprio nome de servidor para o ponto de extremidade OpenID do Valve, e o Steam apresentou-o imediatamente ao utilizador na página de início de sessão. Valve é o tronco por onde todas estas rotas passam; não é necessário que as encontre. É isso que esta secção avalia: não se existe ou não um aviso, mas durante quantos anos o percurso a jusante do aviso permanece aberto. Existem 44 percursos de domínio separado no registo, 27 dos quais com um ficheiro de evidências publicado para cada percurso — conforme a tabela abaixo. Analise um exemplo e, em seguida, avalie todos eles.\n\nFigura 3.1 — As duas rotas, representadas graficamente.\n\nUma plataforma, um utilizador, dois pedidos a sair do mesmo navegador. O Filtro de Links do Valve atua em ambos. Bloqueia aquele que contém um link e permite a passagem daquele que contém os dados de início de sessão. Tudo o que é medido nesta secção corresponde à contagem do tempo durante o qual a rota inferior permanece aberta.\n\nThe player\none browser, one session\nrollbit.com\nthe platform's main domain\nrbsnin.com\nseparate authentication host\nLINK FILTER\n✕ BLOCKED\nLINK FILTER\n✓ CLEAN\nsteamcommunity.com\nOpenID endpoint · signs in\nno route\nLink publicado em Steam — interrompidoPedido de início de sessão — passesCheques guardados de 19 e 21 de setembro de 2026\n\nAmbas as solicitações são visíveis para Valve, mas apenas uma é processada. O Filtro de Ligações é uma lista Valve, verificada por um serviço Valve. O pedido OpenID transmite o próprio nome do anfitrião de autenticação para o ponto final de Valve, que o apresenta imediatamente na página de início de sessão. O nome do anfitrião consta do pedido de qualquer forma — o que difere é se é feita alguma ação com ele.\n\nUma plataforma. Dois percursos diferentes.ROLLBIT / OBSERVAÇÕES GUARDADAS\nEtapa 5 / 5\n\nO pedido atinge Steam. O percurso observado conduziu ao formulário de início de sessão do Steam. Os autores não concluíram o início de sessão. O bloqueio da ligação ao domínio principal não impediu este percurso observado até ao formulário.\n\n01 VERIFICAÇÃO DO FILTRO DE LIGAÇÃO\nDESTINOrollbit.comO domínio principal da plataforma\nFILTRO STEAM LINKVerifica o linkUm sistema independente de aviso de destino\nRESULTADO GUARDADOLink bloqueado19 e 21 de setembro de 2026\n02 O PERCURSO DE ENTRADA OBSERVADO\nNA PLATAFORMAIniciar sessão com SteamA plataforma inicia um pedido OpenID\nHOST DE AUTENTICAÇÃO SEPARADOrbsnin.comNão existe nenhum bloco «Filtro de links» na verificação guardada\nSTEAMFormulário de início de sessão apresentadoO anfitrião solicitado aparece no aviso de Steam\nVerifique as notas de captura originais, a data de registo e os detalhes do protocolo\nComo funciona a aplicação da medida Valve'\nDomínio principal: bloqueado\nUtilizador\n→\nrollbit.com\n(domínio principal)\n↓\nFILTRO DO STEAM LINK — BLOQUEADO\n«Link bloqueado!» — sinalizado como potencialmente malicioso\nO rollbit.com devolveu um bloqueio do Filtro de Links nos valores 2026-09-19 e 2026-09-21 (verificação sem autenticação; HTML não processado e SHA-256 guardados). Um registo visível e auditável.\nO que acontece, na realidade — autenticação\nServidor de autenticação: não bloqueado\nUtilizador\n→\nrollbit.com\n\"Iniciar sessão com Steam\"\n↓\nReencaminhar através de um servidor de autenticação separado:\nrbsnin.comFiltro de links: LIMPO\nregistado 2026-09-18T09:34:52Z (Verisign RDAP)\n↓\nSteam aviso na página de início de sessão (2026-09-20):\n\"Note that rbsnin.com is not affiliated with Steam or Valve\"\nSteam apresenta este aviso a partir do openid.realm do pedido que recebeu.\n↓\nSteam formulário de início de sessão disponibilizado num servidor distinto\nO processo de início de sessão não foi concluído pelos autores; o fluxo foi observado até ao formulário Steam.\nO Valve recebe o nome de host «return_to / realm» em cada um desses pedidos. O rbsnin.com não devolveu qualquer bloqueio do Link Filter no 2026-09-21.\nA pedido\nNa qualidade de fornecedor OpenID, Steam recebe o nome de host de autenticação em cada pedido de autenticação: este chega aos próprios servidores de Valve no openid.return_to e openid.realm parâmetros.\nEnviado pelo site\nO host de autenticação não é detetado através da análise — a plataforma envia-o como Steam em cada pedido. Nos termos do OpenID 2.0, §9.1 return_to é formalmente opcional, mas sem ele o Steam não consegue apresentar o resultado do início de sessão; por isso, para que o início de sessão Steam funcione, é efetivamente necessário. O Steam chega mesmo a apresentar o nome do anfitrião ao utilizador (\"O <host> não está associado ao Steam nem ao Valve\").\n14 anos\né a idade do servidor de autenticação mais antigo que ainda mantém Steam inícios de sessão na verificação 2026-09-21 (dota2.net, registado há 2011-10-29); o mais recente tem três dias (rbsnin.com). Não interprete o valor «0 hosts de autenticação bloqueados» como se fosse a conclusão. Um host de autenticação bloqueado interromperia completamente a funcionalidade «Iniciar sessão com Steam» da plataforma; por isso, um registo criado a partir de inícios de sessão bem-sucedidos só pode conter hosts que nunca tenham sido bloqueados. O número que tem significado não é o número de bloqueios — é o número de anos que o domínio principal permaneceu no Filtro de Links enquanto o login ao seu lado continuou a funcionar.\nHosts de autenticação com domínios separados: data de registo vs. domínio principal (30 rotas: as 25 resolvidas na auditoria do navegador 2026-09-21, mais 5 adicionadas em 2026-09-22)\nPlataforma\tFiltro de links: principal\tServidor de autenticação\tFiltro de ligações: host de autenticação\tServidor de autenticação registado\tFonte da observação\tDossiê de provas\nRollbit\nrollbit.com · reg. 2014-11-08\n\tBLOQUEADO\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\trbsnin.com\tLIMPO\n2026-09-21 · HTML bruto (não há cópia de arquivo do Wayback)\n\t2026-09-18\n09:34:52Z, Verisign RDAP\n\tSteam aviso na página de início de sessão, 2026-09-20\trollbit.com.json\nSkin.Club\nskin.club · reg. 2017-09-04\n\tBLOQUEADO\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\tsc-auth.net\tLIMPO\n2026-09-21 · Wayback 2026-09-21\n\t2019-04-02\nRDAP\n\tSteam aviso na página de início de sessão\tskin.club.json\nHowl.GG\nhowl.gg · reg. 2017-03-16\n\tBLOQUEADO\n2026-09-18, 19-09, 21-09 · Wayback 2026-09-21\n\thowl.uno\tLIMPO\n2026-09-21 · Wayback 2026-09-21\n\t2026-08-11\nRDAP\n\tCaptura em tempo real do navegador + URL OpenID fornecida\thowl.gg.json\nDuelbits\nduelbits.com · reg. 2020-02-03\n\tBLOQUEADO\n2026-09-21 · Wayback 2026-09-21\n\tswitchflips.com\tLIMPO\n2026-09-21 · Wayback 2026-09-21\n\t2020-04-21\nRDAP\n\tURL do OpenID fornecida\tduelbits.com.json\nCSGOFast\ncsgofast.com · reg. 2015-03-27\n\tBLOQUEADO\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\tsteam-login.authtofast.com\tLIMPO\nauthtofast.com, 2026-09-21 · Wayback 2026-09-21\n\t2026-06-30\nauthtofast.com, RDAP\n\tCaptura em tempo real do navegador + URL do OpenID fornecido\tcsgofast.com.json\nFarmskins\nfarmskins.com · reg. 2016-03-23\n\tBLOQUEADO\n2026-09-19, 2026-09-21 · HTML bruto\n\tsteam.kobal.cc\tLIMPO\n2026-09-19, 2026-09-21 · HTML bruto\n\t2017-01-07\nkobal.cc, RDAP\n\tCaptura em tempo real do navegador + URL do OpenID fornecido\tfarmskins.com.json\nCobaltLab\ncobaltlab.tech\n\tBLOQUEADO\n2026-09-21 · HTML bruto\n\tcobaltauth.com\tLIMPO\n2026-09-21 · HTML bruto\n\t2025-01-07\nRDAP\n\tURL do OpenID fornecida\tcobaltlab.tech.json\nCSGO.NET\ncsgo.net · reg. 2012-07-22\n\tBLOQUEADO\n2026-09-21 · HTML bruto\n\tcn2.easylot.net\tLIMPO\n2026-09-21 · HTML bruto\n\t2016-09-03\neasylot.net, RDAP\n\tCaptura em tempo real do navegador\tcsgo.net.json\nGGDrop\nggdrop.com\n\tBLOQUEADO\n2026-09-21 · HTML bruto\n\tggauth.com\tLIMPO\n2026-09-21 · HTML bruto\n\t2023-05-03\nRDAP\n\tURL do OpenID fornecida\tggdrop.com.json\nRustChance\nrustchance.com\n\tBLOQUEADO\n2026-09-21 · HTML bruto\n\thgfuihd.com\tLIMPO\n2026-09-21 · HTML bruto\n\t2019-01-27\nRDAP\n\tURL do OpenID fornecida\trustchance.com.json\nSkin.Fans\nskin.fans\n\tBLOQUEADO\n2026-09-21 · HTML bruto\n\tauth.skinfans.com\tLIMPO\n2026-09-21 · HTML bruto\n\t2018-07-16\nskinfans.com, RDAP\n\tURL do OpenID fornecida\tskin.fans.json\nSkinport\nskinport.com · reg. 2018-09-05\n\tBLOQUEADO\n2026-09-21 · HTML bruto\n\tskinport.app\tLIMPO\n2026-09-21 · HTML bruto\n\t2020-06-20\nRDAP\n\tCaptura em tempo real do navegador + URL OpenID fornecida\tskinport.com.json\nSkins.Cash\nskins.cash\n\tBLOQUEADO\n2026-09-21 · HTML bruto\n\tskinscash.live\tLIMPO\n2026-09-21 · HTML bruto\n\t2019-12-05\nRDAP\n\tURL do OpenID fornecida\tskins.cash.json\nTF2Hunt\ntf2hunt.com · reg. 2018-01-13\n\tBLOQUEADO\n2026-09-21 · HTML bruto\n\trstspcl.com\tLIMPO\n2026-09-21 · HTML bruto\n\t2020-08-08\nRDAP\n\tCaptura em tempo real do navegador + URL do OpenID fornecido\ttf2hunt.com.json\nCSGOGem\ncsgogem.com · reg. 2016-10-16\n\tBLOQUEADO\n2026-09-22 · HTML bruto\n\tapi.csgem.com\ncsgem.com — domínio registável independente\n\tLIMPO\n2026-09-22 · HTML bruto\n\t2014-03-08\ncsgem.com, RDAP — o mais antigo do registo\n\tRecolha manual + Captura através do Filtro de Links\tlinkfilter-2026-09-22.json\nGamdom\ngamdom.com · reg. 2016-07-29\n\tBLOQUEADO\n2026-09-22 · HTML bruto\n\tlogin.gambldom.com\ngambldom.com — falta apenas uma letra para ser a marca\n\tLIMPO\n2026-09-22 · HTML bruto\n\t2017-09-24\ngambldom.com, RDAP\n\tRecolha manual + Captura através do filtro de links\tlinkfilter-2026-09-22.json\n12CS\n12cs.fail · reg. 2026-03-24\n\tBLOQUEADO\n2026-09-22 · HTML bruto\n\tfail.games\tLIMPO\n2026-09-22 · HTML bruto\n\t2021-08-24\nfail.games, RDAP\n\tRecolha manual + Captura através do Filtro de Links\tlinkfilter-2026-09-22.json\nCSGOEmpire\ncsgoempire.com · reg. 2015-06-10\n\tLIMPO\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\tcsgoempirelogin4.com\num dos dez domínios numerados de login1 a 10\n\tLIMPO\n2026-09-21 · Wayback 2026-09-21\n\t2020-07-20\n05:49:17Z, Verisign RDAP\n\tCaptura em tempo real do navegador\tcsgoempire.com.json\nCS.MONEY\ncs.money\n\tLIMPO\n2026-09-21 · HTML bruto\n\tauth.dota.trade\tLIMPO\n2026-09-21 · HTML bruto\n\t2016-07-15\ndota.trade, RDAP\n\tSteam aviso na página de início de sessão\tcs.money.json\nCSFloat\ncsfloat.com · reg. 2021-07-11\n\tLIMPO\n2026-09-21 · HTML bruto\n\tcsgofloat.com\ndomínio da antiga marca do operador; domínio registável independente, não constitui um indicador de evasão\n\tLIMPO\n2026-09-21 · HTML bruto\n\t2015-09-29\nRDAP\n\tCaptura em tempo real do navegador\tcsfloat.com.json\nG4Skins\ng4skins.com\n\tLIMPO\n2026-09-21 · HTML bruto\n\tauth.g4s.to\tLIMPO\n2026-09-21 · HTML bruto\n\t2021-05-30\ng4s.to, RDAP\n\tURL do OpenID fornecido\tg4skins.com.json\nJuice.GG\njuice.gg\n\tLIMPO\n2026-09-21 · HTML bruto\n\tletmeinjuice.com\tLIMPO\n2026-09-21 · HTML bruto\n\t2024-04-15\nRDAP\n\tURL do OpenID fornecida\tjuice.gg.json\nMarket.CSGO\nmarket.csgo.com\n\tLIMPO\n2026-09-21 · HTML bruto\n\tdota2.net\tLIMPO\n2026-09-21 · HTML bruto\n\t2011-10-29\nRDAP\n\tCaptura em tempo real do navegador + URL OpenID fornecida\tmarket.csgo.com.json\nRust.TM\nrust.tm\n\tLIMPO\n2026-09-21 · HTML bruto\n\tdota2.net\tLIMPO\n2026-09-21 · HTML bruto\n\t2011-10-29\nRDAP\n\tURL do OpenID fornecida\trust.tm.json\nCSGOLounge\ncsgolounge.com · reg. 2013-08-14\n\tLIMPO\n2026-09-22 · HTML bruto\n\tdota2.net\nterceiro front-end neste servidor de autenticação\n\tLIMPO\n2026-09-22 · HTML bruto\n\t2011-10-29\ndota2.net, RDAP\n\tRecolha manual + Captura com o filtro de links\tlinkfilter-2026-09-22.json\nDota2Lounge\ndota2lounge.com · reg. 2012-08-10\n\tLIMPO\n2026-09-22 · HTML bruto\n\tdota2.net\nquarto front-end neste servidor de autenticação\n\tLIMPO\n2026-09-22 · HTML bruto\n\t2011-10-29\ndota2.net, RDAP\n\tRecolha manual + Captura através do filtro de links\tlinkfilter-2026-09-22.json\nSkinBaron\nskinbaron.de\n\tLIMPO\n2026-09-21 · HTML bruto\n\tskinbaron.com\nmesma marca, TLD diferente\n\tLIMPO\n2026-09-21 · HTML puro\n\t2015-12-22\nRDAP\n\tURL do OpenID fornecido\tskinbaron.de.json\nTF2Royal\ntf2royal.com · reg. 2022-08-17\n\tLIMPO\n2026-09-21 · HTML bruto\n\ttf2auth.com\tLIMPO\n2026-09-21 · HTML bruto\n\t2021-07-27\nRDAP\n\tCaptura em tempo real do navegador + URL OpenID fornecida\ttf2royal.com.json\nTradeit\ntradeit.gg\n\tLIMPO\n2026-09-21 · HTML bruto\n\tconnect-tradeit.com\tLIMPO\n2026-09-21 · HTML bruto\n\t2022-02-23\nRDAP\n\tURL do OpenID fornecida\ttradeit.gg.json\nAtualizador\nupgrader.pro\n\tLIMPO\n2026-09-21 · HTML bruto\n\tupgauth.space\tLIMPO\n2026-09-21 · HTML bruto\n\t2026-08-14\nRDAP\n\tURL do OpenID fornecida\tupgrader.pro.json\nFonte: steamcommunity.com/linkfilter, GET sem autenticação, 2026-09-21, 53 hosts, intervalo de 3 s; steam_tos_assets/linkfilter-recheck-2026-09-21.json; HTML sem formatação em steam_tos_assets/linkfilter-raw/. Datas de inscrição: RDAP, steam_tos_assets/domain-registration.json. · Verificação antecipada de 2026-09-19 em linkfilter-all-results.json · registos de percursos em auth-route-audit.json · Instantâneos do Wayback Machine das páginas do Link Filter, 2026-09-21, listadas em wayback-snapshots.json (não existe nenhum instantâneo para rbsnin.com; o ficheiro bruto local é o único registo).\n\nDatas de inscrição: RDAP (steam_tos_assets/domain-registry/). A «URL OpenID fornecida» define os parâmetros do pedido, não um início de sessão concluído. Os autores não concluíram qualquer início de sessão em nenhuma plataforma. Um domínio separado não constitui, por si só, prova de evasão. Nem «0 hosts de autenticação bloqueados» é uma conclusão independente: bloquear um interromperia o processo de início de sessão Steam dessa plataforma, pelo que um registo compilado a partir de inícios de sessão válidos não pode conter um host de autenticação bloqueado. A observação que tem peso é o emparelhamento e a sua duração — um domínio principal no Filtro de Ligações ao lado de um domínio de início de sessão que está ativo há anos. Esta tabela contém 30 linhas: 25 das 27 rotas com um ficheiro de evidência por rota, mais cinco adicionadas em 2026-09-22 cuja divisão no Filtro de Ligações é capturada em linkfilter-2026-09-22.json apesar de o domínio em si ter sido recolhido manualmente — as suas linhas indicam isso na coluna «fonte». As duas rotas de ficheiros de evidência que não aparecem são skinsnipe.com (host de autenticação pricing.tradeupspy.com, registado 2020-03-11) e csgobig.com (host de autorização letmeinbig.com, registado 2023-01-20); ambos devolveram «BLOCKED main / CLEAN auth host» na verificação de 2026-09-22, registado com SHA-256 em linkfilter-2026-09-22c.json, mas o código HTML bruto desse lote não consta do conjunto publicado, pelo que são aqui referidos pelo nome, em vez de lhes ser atribuída uma linha, como acontece com todas as outras linhas desta tabela. As restantes 12 rotas recolhidas manualmente no registo são identificadas como tal em master_registry.json sob realm_src: user.\n\nAuditoria Empírica Primária · Intervalo de datas plurianual\nA armadilha do panorama geral: o filtro de links é apenas uma fachada de conformidade, não um escudo\n\nNos navegadores de computador, os utilizadores estão protegidos por defesas externas: o Google Safe Browsing e o Microsoft SmartScreen interceptam tentativas de phishing conhecidas, exibindo avisos vermelhos em ecrã inteiro. No modo «Big Picture» do Steam, na sobreposição do jogo (Shift+Tab) e no Deck Steam (SteamOS), essas defesas não existem. O navegador incorporado não suporta quaisquer extensões, desativa os mecanismos externos de Navegação Segura e deixa o utilizador com exatamente uma barreira de defesa: o Valve's linkfilter intersticial.\n\nDeslize para comparar os quatro resultados →\n\n92.5%\n2025–2026: phishing de última geração aprovado sem ressalvas (37/40)\n77.5%\nPhishing da era CS2 2023–2024 aprovado sem ressalvas (31/40)\n70.0%\nPhishing de legados de 2021–2022 aprovado sem ressalvas (28/40)\n7 / 7\nredes de jogo bloqueadas (controlo positivo)\nAuditoria longitudinal plurianual: 120 domínios de phishing «Pure Steam» testados em tempo real (24 de setembro de 2026)\n\nPara verificar se o filtro do Valve é simplesmente lento a detetar novas ameaças ou se é fundamentalmente incapaz de as detetar, realizámos uma auditoria 120 domínios de phishing confirmados específicos do Steam em três coortes históricas, em comparação com steamcommunity.com/linkfilter:\n\n1.ª Turma: 2021–2022 (Oferta de Troca Clássica e Itens Oferecidos) — 70.0% Aprovação com nota máxima (28/40). Mesmo 4 a 5 anos depois de terem sido registados por organismos de vigilância da comunidade, 7 em cada 10 servidores de phishing antigos continuam acessíveis, sem qualquer bloqueio.\nCohorte 2: 2023–2024 (CS2 Beta: entusiasmo exagerado e pedidos de apoio falsos) — 77.5% Aprovação sem falhas (31/40). Campanhas que se fazem passar por lançamentos do Counter-Strike 2 e apelos falsos da comunidade (por exemplo, cs2-steam.com, appealsteamcommunity.help) passam diretamente.\n3.ª turma: 2025–2026 (Implementações em edge sem servidor e clones de favicons) — 92.5% Aprovação com nota máxima (37/40). Kits modernos de phishing implementados no EdgeOne, no Vercel e no Cloudflare Pages (por exemplo, steamgifter.online, steam-dp4lt5b8fnez.edgeone.dev) passam praticamente sem qualquer obstáculo.\n\nTelemetria e Proteção contra Responsabilidade Civil, não Proteção. Por que é que o Filtro de Links existe se permite a passagem de 70% para 92.5% de um caso claro de Steam phishing? Funciona como uma cláusula de isenção de responsabilidade da empresa e como um sensor de telemetria de cliques de saída. Ao apresentar uma mensagem educada «Estás a sair Steam» aviso com um botão verde clicável «Continuar», Valve atribui a responsabilidade legal à vítima ao abrigo do Steam Acordo de Subscrição (*«o utilizador navegou voluntariamente para fora de Steam»*). O Valve recolhe os dados de telemetria do clique, mas não bloqueia o roubo.\n\nA prova do hash do favicon: zero ingestão de feeds de ameaças. As plataformas independentes de inteligência sobre ameaças (urlscan.io, Shodan, Censys) identificam kits de phishing ativos Steam através de uma simples pesquisa pelo hash do favicon oficial de Steam (page.favicon.hash:9f890a9debcdfccc339149a7943be9aff9e4c9203c2fa37d5671a5b2c88503ad NOT domain:*.steampowered.com). Esta verificação automática básica identifica grupos de phishing ativos em segundos. O Valve não sincroniza com fontes externas, não realiza a deteção de ameaças com base em hash e só intervém manualmente quando obrigado pelas entidades reguladoras (a decisão de 2016 da WSGC relativa ao jogo) ou para proteger as suas cadeias de domínios registadas como marcas comerciais.\n\nElementos de prova de auditoria primários: Auditoria longitudinal plurianual de 120 domínios: auditoria-longitudinal-de-phishing-no-Steam.json · 100 amostras específicas de phishing Steam: linkfilter-steam-phishing-100.json · Auditoria abrangente à alimentação (n=250): linkfilter-coverage-2026-09-22.json.\n\nCSGOEmpire — registo em lote de dez domínios de autenticação numerados\n\nEm 2020-07-20 dez domínios numerados, csgoempirelogin1.com através de csgoempirelogin10.com, foram registados. Estão arquivados os carimbos de data e hora RDAP da Verisign para todos os dez: login1 05:49:06Z, login5 05:49:08Z, login2 05:49:11Z, login3 05:49:14Z, login4 05:49:17Z, login6 05:49:20Z, login7 05:49:23Z, login8 05:49:26Z, login9 05:49:28Z — nove domínios em 22 segundos — e o login10 às 05:56:03Z, sete minutos depois. O intervalo entre os registos é consistente com uma única operação em massa do registrador.\n\nO padrão é consistente com os anfitriões de recurso alternativo pré-configurados; apenas login4 foi observado numa solicitação OpenID em tempo real. Tanto o csgoempire.com como o csgoempirelogin4.com apresentaram o resultado «CLEAN» no Filtro de Links em 2026-09-21; o CSGOEmpire não figurava entre os sites mencionados nas notícias da imprensa relativas aos avisos de julho de 2016.\n\n# DNS — todos os 10 ativos (setembro de 2026)\nOK csgoempirelogin1.com 172.67.129.43\nOK csgoempirelogin2.com 172.67.175.168\nOK csgoempirelogin3.com 188.114.96.3\nOK csgoempirelogin4.com 188.114.96.11 ← no tráfego OpenID\nOK csgoempirelogin5.com 172.67.160.194\nOK csgoempirelogin6–10.com IPs da Cloudflare\nNXDOMAIN: csgoempirelogin11.com\nTodos os 10 registados 2020-07-20; todos os 10 com carimbo de data/hora RDAP (steam_tos_assets/domain-registry/csgoempireloginN.com.rdap.json)\nConclusão para as entidades reguladoras\nUm domínio principal bloqueado, em conjunto com um host de autenticação desbloqueado, deixa a rota de início de sessão aberta — e esta permanece aberta durante anos.\n\nO bloco «Link Filter» no domínio principal é um registo público e verificável. O host de autenticação transporta o tráfego «Iniciar sessão com Steam» e aparece nos próprios parâmetros de pedido OpenID de Valve. Em verificações cruzadas em 2026-09-21 e 2026-09-22, em 26 pares separados pelo filtro, o domínio principal devolveu um bloqueio do Filtro de Ligação, enquanto o proxy que transportava o seu início de sessão não devolveu nenhum. O registo acima mede a outra metade disso: estes anfitriões não são domínios descartáveis de curta duração. Vários estavam registados há mais de uma década à data da verificação, e cada um desses dias corresponde a um dia em que Valve recebeu o nome de anfitrião nos seus próprios parâmetros de pedido. O Valve não publicou qualquer registo de aplicação de medidas por operador, pelo que não é possível determinar, a partir de dados públicos, se foram aplicadas quaisquer outras medidas a estes anfitriões.\n\n12 anos e 6 meses\nO site csgogem.com está bloqueado no Filtro de Links.\nO seu servidor de início de sessão api.csgem.com tem sido\nestá registado desde 2014-03-08 e não está.\nResumo em linguagem simples — Para entidades reguladoras e tribunais (expandir)\nResumo em linguagem simples — destinado às entidades reguladoras\nContexto: O que é o Steam e por que é importante neste contexto\n\nA Steam é uma plataforma de software operada pela Valve Corporation (Bellevue, Washington, EUA). O Steam funciona como um fornecedor de identidade digital: os sites de jogos de azar e jogos na Internet utilizam um sistema denominado «Iniciar sessão com o Steam» — um botão que permite a um site verificar se um visitante possui uma conta Steam válida. Isto é semelhante ao «Iniciar sessão com o Google» ou à verificação de um cartão de identidade emitido pelo Estado: o site redireciona o utilizador para os servidores da Steam, a Steam confirma a sua identidade e a Steam redireciona-o de volta para o site. O Valve gere o sistema de autenticação. Cada início de sessão efetuado através da opção «Iniciar sessão com o Steam» passa pelos servidores do próprio Valve.\n\nO que o Valve fez: O bloqueio de domínios\n\nEm julho de 2016, na sequência da pressão mediática e jurídica relativa aos jogos de azar com «skin», o advogado da Valve enviou notificações a cerca de 23 sites de jogos de azar identificados (segundo notícias da imprensa de 21 de julho de 2016); em outubro de 2016, a Valve informou a Comissão de Jogos de Azar do Estado de Washington de que tinha contactado mais de quarenta sites. Alguns domínios de jogos de azar aparecem na Steam Filtro de links — uma lista que faz com que qualquer ligação para esses conteúdos publicada no Steam (no chat, numa página de perfil, na loja) exiba uma página de aviso: \"Link bloqueado!\" O Filtro de Ligação é a única medida de imposição cujo efeito pode ser observado a partir do exterior de Valve.\n\nExemplo: Um link para rollbit.com No interior de Steam é apresentada a página de aviso do Link Filter (opções 2026-09-19 e 2026-09-21 selecionadas). Em teoria, o site de jogos de azar está bloqueado.\nO que é um domínio proxy\n\nA O host de autenticação de domínio separado é um proxy de autenticação: um segundo endereço de site, num domínio registável diferente, que o mesmo operador coloca entre os seus utilizadores e Steam com o único objetivo de realizar o passo «Iniciar sessão com Steam». Este endereço funciona como proxy para o início de sessão. O utilizador pensa que está a iniciar sessão na plataforma; o pedido que chega a Valve contém o nome de anfitrião do proxy, e não o da plataforma. Normalmente, não tem qualquer ligação visível publicamente ao site de jogos de azar, e é o endereço que recebe os utilizadores de volta depois de Steam confirmar a sua identidade.\n\nExemplo: A Rollbit opera ao abrigo de rollbit.com, que o Filtro de Ligação bloqueia. No caso da autenticação Steam, o fluxo observado em 2026-09-20 utilizava um endereço distinto: rbsnin.com, registado como 2026-09-18. Este endereço devolveu sem bloco «Filtro de links» em 2026-09-21. O site de jogos de azar continuou a funcionar, e o seu fluxo de início de sessão Steam passou pelo servidor desbloqueado.\nO ponto crítico: o host de autenticação é enviado para Steam em todas as solicitações\n\nO Valve não precisa de efetuar uma análise ou rastreio para saber quais os servidores de autenticação que estão a ser utilizados. O Steam é o Provedor de identidade OpenID para estes sites, e cada clique em «Iniciar sessão com Steam» envia um pedido GET para os próprios servidores de Valve, contendo o nome de anfitrião de autenticação em texto simples. Nos termos do OpenID 2.0 §9.1, o return_to O campo é formalmente opcional, mas sem ele o Steam não consegue apresentar o resultado do início de sessão; por isso, para que o início de sessão com o Steam funcione, é efetivamente obrigatório. O próprio Steam apresenta o nome do anfitrião na página de início de sessão (\"<host> não está associado a Steam nem a Valve\").\n\n— Formato do pedido Steam recebido (host, tal como observado para o Rollbit em 2026-09-20): —\nOBTER steamcommunity.com/openid/login\n&openid.mode=checkid_setup\n&openid.return_to=https://rbsnin.com/… ← efetivamente necessário; aparece no registo de Valve\n&openid.realm=https://rbsnin.com ← declarado pelo próprio site; apresentado na página de início de sessão do Steam\nSe o site utilizar verificação servidor a servidor (check_authentication), o registo do Valve também regista o IP do servidor da plataforma e a rede de alojamento.\n\nA extração do nome do anfitrião desta solicitação é uma operação padrão. O registo de aplicação — indicando em que anfitriões foram tomadas medidas, em quais não foram e com base em que critérios — existe apenas na infraestrutura da Valve e não foi publicado.\n\nO que isto demonstra\n\n1. O bloco «Link Filter» atua sobre os links, e não sobre os inícios de sessão. Bloquear o domínio principal (por exemplo, rollbit.com) apresenta um aviso aos utilizadores que clicam em links para esse site dentro do Steam. Isso não impede o funcionamento do site, nem a utilização do próprio serviço OpenID do Valve através de um endereço diferente.\n\n2. Os servidores de autenticação testados não estavam bloqueados. A tabela acima apresenta os anfitriões de autenticação de domínios separados registados entre 2011 e setembro de 2026, muitos dos quais anos após os avisos de julho de 2016. Em 26 pares, o domínio principal devolveu um bloqueio do Link Filter e o proxy que transportava o seu login não o fez (verificações não autenticadas, 2026-09-21 e 2026-09-22; respostas em bruto e SHA-256 guardadas). Esse proxy deixaria de funcionar no dia em que Valve o recusasse, razão pela qual o que importa aqui é o tempo durante o qual esteve em funcionamento, e não se está ou não na lista. O Valve recebe estes nomes de host nas suas próprias solicitações OpenID. Não é possível determinar, a partir de dados públicos, se foi aplicada alguma medida além do Filtro de Ligação, uma vez que o Valve não publicou qualquer registo de aplicação por operador.\n\n3. Os sites continuaram a efetuar a autenticação através da infraestrutura do Valve. «Iniciar sessão com Steam» é um serviço do Valve; cada autenticação efetuada através deste serviço constitui um pedido que o Valve recebe e processa. O Valve também obtém receitas com as chaves de caso, e o Mercado Comunitário Steam cobra uma taxa combinada de cerca de 15% nas transações concluídas dentro do Mercado (não nas transações externas). A ação «Filtro de Ligação» criou um registo público; não interrompeu a relação de autenticação.\n\nSerá que o bloqueio teria funcionado?\n\nPor analogia: quando o registador de domínios gratuito Freenom encerrou as suas atividades em 2023, as campanhas de phishing que dependiam dos seus domínios foram interrompidas. A continuidade operacional depende da estabilidade da infraestrutura.\n\nA mesma lógica aplica-se aqui. Se um host de autenticação fosse rejeitado no processamento do OpenID do Steam, a função «Iniciar sessão com Steam» da plataforma deixaria de funcionar até que um novo host fosse registado, os certificados emitidos e o DNS propagado. Durante esse período: tempo de inatividade.\n\nA rotação não torna o bloqueio inútil. Isso faz com que o bloqueio se torne um custo operacional. Uma vez que os novos hosts aparecem nos registos de pedidos do próprio Valve aquando da primeira utilização, uma resposta pode demorar o tempo que demorou essa primeira utilização.\n\nO registo em lote é, por si só, um sinal: Os registos «login1» a «login10» do CSGOEmpire foram registados em 2020-07-20, nove deles num intervalo de 22 segundos (Verisign RDAP). Uma resposta não tem de ser domínio a domínio; uma série sequencial proveniente de uma única sessão de um registador pode ser identificada como uma série.\n\nOs registos públicos não revelam qualquer tentativa de bloquear servidores de autenticação que tenha sido contornada pela rotação.\nMostra os principais domínios bloqueados enquanto o proxy responsável por cada início de sessão continuava a funcionar — 26 pares a partir de 2026-09-22, sendo que o host de autenticação mais antigo foi registado há 12 anos e 6 meses — e não há qualquer registo publicado de medidas coercivas por parte de qualquer operador.\nA questão que se coloca ao regulador é, portanto: que medidas de aplicação da lei, se é que houve alguma, aplicou Valve aos servidores de autenticação que recebe nas suas próprias solicitações OpenID?\nO que Valve fez — e por que razão não interrompeu o percurso de autenticação\n\nA tabela abaixo relaciona cada ação Valve documentada publicamente, indicando se afetou ou não o ponto de entrada de autenticação do OpenID. A conclusão não é que «Valve não tenha feito nada» — é que nenhuma das ações documentadas publicamente afetou o ponto por onde os inícios de sessão nas plataformas de jogo passam pelos servidores de Valve.\n\nData\tValve Ação\tAfectados openid.return_to caminho?\nJulho de 2016\tDeclaração pública de 13 de julho de 2016; notificações dos advogados a cerca de 23 locais identificados (imprensa, 21 de julho de 2016); mais de 40 locais contactados, de acordo com a carta de Valve enviada à WSGC em outubro de 2016\tNão. As notificações e o Filtro de Ligações atuam sobre os operadores e as ligações; o caminho do pedido OpenID não foi alterado.\n2017\tEncerramento de IEconItems_730/GetPlayerItems (de acordo com a conta de engenharia do CSFloat; não foi encontrado nenhum registo de alterações Valve)\tNão. A visibilidade do histórico dos itens públicos foi afetada. A autenticação OpenID não sofreu alterações.\n2018-03-29\tAnunciado o bloqueio de trocas de 7 dias no CS:GO (blog.counter-strike.net)\tNão. A movimentação dos itens ficou mais lenta; o caminho da solicitação OpenID não foi alterado.\n2022-05-10\tOs pontos finais de cancelamento de transações foram removidos da API Web pública (detetado pelo utilizador; sem registo de alterações Valve — node-steam-tradeoffer-manager #325)\tNão. A ferramenta de troca de ofertas foi encerrada; a autenticação OpenID não sofreu alterações.\n2023-12-04\tA criação de chaves API requer agora uma confirmação através do telemóvel (steamcommunity.com/dev/apikey; sem registo de alterações)\tNão. O ponto final da chave foi protegido; os anfitriões de autenticação aqui referidos não foram afetados.\n2026-09-19 / 21-09\tSteam Estado do filtro de ligações, tal como observado pelos autores\tOs 14 domínios principais devolveram um bloqueio na verificação de segurança 2026-09-21 guardada — 26 pares divididos no registo por 2026-09-22 — enquanto o proxy responsável por cada início de sessão continuava a funcionar.\nFontes: Valve comunicado de 13 de julho de 2016 (store.steampowered.com/oldnews/22883, arquivado 2026-09-21) · Relatório técnico da CSFloat sobre o encerramento de 2017 (blog.csfloat.com, arquivado 2026-09-21) · Estado do filtro de ligações: linkfilter-recheck-2026-09-21.json.\nEsta conclusão pode ser refutada por um único caso publicado em que Valve tenha recusado um pedido de OpenID porque openid.return_to apontava para um servidor de autorização de jogos de azar. Não foi encontrada qualquer instância desse tipo nos registos públicos.\nOs dois registos mais recentes de «auth-host»\nhowl.unofoi registado em 2026-08-11 (RDAP), 41 dias antes de 2026-09-21; o howl.gg devolveu um bloqueio do Link Filter em 2026-09-18, 2026-09-19 e 2026-09-21. Não está esclarecido se o bloqueio antecedeu o registo.\nrbsnin.comfoi registado em 2026-09-18T09:34:52Z (Verisign RDAP) e foi observado no fluxo de início de sessão Steam do Rollbit em 2026-09-20 através do aviso na própria página de início de sessão de Steam; O rollbit.com devolveu um bloqueio do Link Filter em 2026-09-19 e 2026-09-21, ao passo que o rbsnin.com não o fez.\nCada host da tabela acima é enviado para os servidores de autenticação do Valve como openid.realm em cada tentativa de início de sessão.\nDados completos por rota e resultados do Link Filter: a tabela na Secção 3 acima; resultados brutos em linkfilter-recheck-2026-09-21.json e linkfilter-all-results.json.\nMetodologia — Como foram estabelecidas as contagens de rotas e de filtros de ligações\n1. Resolução de domínios\nA auditoria 2026-09-21 concluiu a análise de 78 das 189 plataformas solicitadas: 33 autenticam-se no seu próprio nome de anfitrião e 20 no seu próprio subdomínio — autenticação direta, e nenhuma delas é contabilizada como rotas de domínios distintos. Os restantes 25. autenticar através de um domínio registável independente, distribuídos por 24 nomes de domínio distintos (o dota2.net é partilhado pelo market.csgo.com e pelo rust.tm): 10 identificados através da captura em tempo real do navegador, 3 através do aviso na própria página de início de sessão do Steam e 12 através de um URL OpenID fornecido. O registo em tempo real (master_registry.json, 2026-09-22) alarga isso a 44 rotas de domínios distintos: 26 pares com divisão de filtro (domínio principal BLOCKED, host de autenticação CLEAN), além de 18 rotas adicionais sem divisão do domínio principal. Das 44, 27 manter um ficheiro de comprovativos por percurso; os restantes 17 foram recolhidos manualmente e estão marcados realm_src: user no registo. Cinco desses dezassete — csgogogem.com, gamdom.com, 12cs.fail, csgolounge.com e dota2lounge.com — foram adicionados em 2026-09-22 com uma captura do Link Filter de ambos os hosts (HTML bruto + SHA-256 em linkfilter-2026-09-22.json), pelo que a divisão em si fica evidente, apesar de o domínio ter sido recolhido manualmente; estas aparecem na tabela acima, juntamente com as rotas do ficheiro de evidências. tfauth.com (tf2easy.com) foi removido do registo às 2026-09-22: tal como no caso de arena.fragnet.net, não há nada que permita verificar a sua ligação ao site de origem. O número pode ser calculado a partir dos dados publicados auth-route-audit.json (série de 2026-09-21) segundo uma regra: uma plataforma só conta quando o seu host OpenID Steam observado se encontra num domínio registável diferente do da própria plataforma.\n2. Steam Estado do filtro de ligações\nTestado através de steamcommunity.com/linkfilter/?url=https://[domain], sem autenticação, em 2026-09-19 e 2026-09-21; HTML bruto guardado com SHA-256. O estado foi registado separadamente para o domínio principal e para o anfitrião de autenticação. Um classificador distingue o aviso genérico «Está a sair de Steam» (CLEAN) da página «Link bloqueado! ... sinalizado como potencialmente malicioso» (BLOCKED); um controlo do google.com confirma que os dois não são confundidos. Uma variante anterior e autenticada deste teste foi descartada depois de ter devolvido «bloqueado» para todos os domínios, incluindo esse controlo — o que se deveu a um cookie de sessão inválido no script de teste, e não a um resultado real.\n3. Observação do anfitrião de autenticação\nCaptura em tempo real: um navegador Playwright acedeu ao fluxo de início de sessão de cada plataforma e o openid.return_to O nome do anfitrião foi obtido a partir do pedido intercetado. Aviso na página de início de sessão: o nome do anfitrião foi obtido a partir do próprio \" de Steam's \"O <host> não está associado ao Steam nem ao Valve\" texto, que Steam representa a partir de openid.realm (rbsnin.com, sc-auth.net, auth.dota.trade). URL fornecida: uma URL de login Steam fornecida aos autores; esta define os parâmetros do pedido, não um login concluído. Não foi concluído qualquer login em nenhuma plataforma.\n4. Abrangência — o que não foi resolvido e por que é importante\nDas 189 plataformas, A 110 não apresentou nenhum percurso definido e um não era aplicável (189 − 78 − 1). Este dossiê não contabiliza nenhum deles. A repartição dos 110, a partir do ficheiro de auditoria: 22 desafios de bot, 14 tempos de espera esgotados, 12 erros HTTP e 10 erros de navegação — o observador não conseguiu aceder ao fluxo de início de sessão, embora a maioria destes sítios abra normalmente num navegador comum; 20 não apresentavam qualquer controlo de início de sessão na página de destino; 16 chegaram a um fluxo de início de sessão que não pôde ser resolvido para um host; 11 domínios não foram resolvidos no DNS; 5 ficaram bloqueados numa página de consentimento. A tabela abaixo divide esses mesmos 110 de forma diferente: os 11 que não foram resolvidos no DNS estão listados separadamente como Removido · NXDOMAIN, e a única entrada não aplicável junta-se às restantes. 189 plataformas auditadas, 11 removidas devido a um NXDOMAIN definitivo em ambos os resolvers, 178 mantidos (platform-audit.json, platforms-removed.json). 137 domínios de autenticação que o livro-razão tinha adivinhado com base no padrão de nomenclatura foram eliminados dos dados em 2026-09-19 — nunca foram observados e, por conseguinte, nunca constituíram prova. Três das suposições foram contrariadas pelos URLs OpenID fornecidos: buff.163.com, gamerpay.gg e csgoluck.com efetuam a autenticação diretamente, ao contrário do que se supunha (buffauthproxy.163.com, gamerpayredirect.io e lucklogin.app). As remoções estão listadas no ficheiro de auditoria publicado.\nO número 25 é um limite mínimo, não um limite máximo. Entre as 78 plataformas que foram resolvidas, 25 utilizaram um domínio separado e 53 não. Essa proporção não permite tirar quaisquer conclusões sobre as 110 não resolvidas, e nenhuma projeção a partir dela aparece em qualquer parte deste dossiê. Cada uma delas pode ser resolvida por uma pessoa que abra o site e clique em «Iniciar sessão com Steam»: o nome de host de autenticação encontra-se no URL da página Steam que é carregada.\nO objetivo desta secção: Um observador independente precisa de um navegador e de muita paciência para identificar 189 plataformas, tendo conseguido identificar 78. O Valve requer uma consulta à base de dados. Todas as plataformas que utilizam «Iniciar sessão com Steam» — quer estejam identificadas, quer não — enviam openid.realm para o ponto final de autenticação de Valve em cada início de sessão. A lacuna nesta tabela deve-se ao facto de os autores se encontrarem fora do sistema. Não existe no caso de Valve.\nOs nomes de domínio dos hosts proxy observados encontram-se em auth-route-audit.json. Datas de registo do domínio provenientes do RDAP (Verisign) / IP2WHOIS. Resultados do filtro de links em linkfilter-all-results.json.\nUma analogia para maior clareza\n\nImagine que uma empresa de táxis licenciada é informada pelas entidades reguladoras de que já não pode operar a partir da sua morada registada na Main Street. A empresa retira o letreiro da Main Street. A remoção desse letreiro é documentada. No entanto, a mesma empresa abre uma morada na Side Street — registada sob um nome diferente — e continua a operar a partir daí. As autoridades reguladoras gerem o sistema central de despacho que todos os táxis de ambos os endereços utilizam. Cada pedido de viagem indica «recolha na Rua Lateral». As autoridades reguladoras nunca revogam a licença da Rua Lateral. A remoção do letreiro da Main Street foi a única medida coerciva que teve lugar. A empresa de táxis nunca deixou de funcionar.\n\nParte A — Ficha técnica · Secção 3.1\nNo interior de Steam, a lista de Valve é a única lista.\n\nUm link clicado no cliente Steam, na sobreposição no jogo ou no modo Big Picture não abre no navegador do utilizador. É apresentado no próprio navegador incorporado do Steam — onde não estão presentes as camadas de aviso que um navegador aplicaria. O Filtro de Ligações não é apenas uma das várias medidas de segurança. É a única medida de segurança.\n\nNum navegador normalTrês camadas independentes\nNavegação Segura do GoogleUm anúncio intersticial de página inteira para servidores incluídos nas listas de phishing e malware do Google, atualizado continuamente e independentemente do site que está a ser visitado.\nA extensão antivírus para o navegadorA maioria dos produtos para terminais de consumidores inclui um complemento de navegador que verifica o destino em relação à lista de reputação do próprio fornecedor.\nInspeção HTTPS nos terminaisQuando o produto realiza a inspeção TLS, o conteúdo da página é analisado antes de chegar ao utilizador.\nNo cliente Steam, sobreposição e Big PictureUma camada\nNavegação Segura do GoogleNão está presente. A verificação requer chaves da API do Google que não estão disponibilizadas nas compilações incorporadas do Chromium; quando estas não existem, a própria documentação de conceção do Chromium indica que o manipulador do Safe Browsing simplesmente nunca é adicionado à cadeia de pedidos.\nA extensão antivírus para o navegadorNão está presente. O motor de renderização do Steam não é o navegador do utilizador e não carrega nenhuma extensão do perfil do navegador do utilizador, pelo que nenhum complemento é executado na página.\nInspeção HTTPS nos terminaisDepende do produto. O tráfego termina no interior de um processo Valve com código assinado, em vez de num navegador reconhecido, e vários produtos de ponto final isentam as aplicações assinadas da inspeção TLS.\nO Filtro de Ligações SteamA lista de bloqueios do próprio Valve, consultada quando um link sai do ecossistema Steam. Esta é a única verificação que é efetuada — e a tabela acima regista o resultado obtido para os anfitriões de autenticação documentados nesta secção.\nUm teste que qualquer leitor pode realizar; se falhar, a conclusão deixa de se verificar\n\nAbra um dos URLs de teste do «Navegação Segura» publicados pelo Google (testsafebrowsing.appspot.com) no Chrome: aparece um anúncio intersticial vermelho em ecrã inteiro. Abra o mesmo URL a partir de uma mensagem de chat Steam, de forma a que seja apresentado no cliente Steam ou na sobreposição: não aparece nenhum anúncio intersticial. O único aviso que o Steam pode apresentar é a sua própria página do Filtro de Links, e apenas para os anfitriões que constam da lista do Valve.\n\nO próprio recorde de Valve no programa de recompensas por errosEssa questão da «uma camada» já foi contornada anteriormente — no próprio álbum do Valve\n\nSe o Filtro de Ligações for a única verificação executada no cliente, os seus próprios modos de falha não são uma questão secundária. Dois relatórios no programa HackerOne da Valve, ambos aceites, ambos resolvidos e ambos entretanto divulgados na íntegra:\n\n#291750arquivado 2025-11-16 ↗Open Redirect · medium\nContornar a proteção do filtro de ligações\n\nComunicado a 19 de novembro de 2017, resolvido e divulgado a 9 de maio de 2018. A própria prova de conceito do relatório: substituir o ponto final ideográfico 。 (%E3%80%82) para o ponto num nome de anfitrião — É possível contornar o bloqueio. O conteúdo intersticial a que esta secção se refere não apareceu.\n\n#1079561arquivado 2026-09-24 ↗Divulgação de informação · elevada\nO navegador Big Picture divulga cookies de início de sessão e revela informações confidenciais (o que pode levar à apropriação de contas)\n\nComunicado a 15 de janeiro de 2021, resolvido e divulgado a 21 de setembro de 2021. A classificação de gravidade atribuída pelo próprio Valve é elevada e o título indica a consequência. O registo divulgado inclui o título, a classificação e as datas; a descrição técnica não consta do conteúdo publicado, pelo que nada mais é aqui citado a partir dela.\n\nEsta é a interpretação dos autores, não uma conclusão de nenhum dos relatórios: Os dois situam-se de cada lado do mesmo portão. Um é o aviso que não aparece antes de o destino ser aberto; o outro é a sessão que abandona o cliente assim que uma página é aberta no seu interior. A sequência que se segue a uma sessão roubada — chave registada sem aviso prévio, a transação real cancelada, uma cópia enviada para um clone — é o padrão descrito em Secção 5 para Secção 8. Ambos os relatórios estão encerrados; nenhum deles é considerado uma vulnerabilidade ativa. O que eles demonstram é mais específico e suficiente: a única camada remanescente tem um historial documentado de ter sido contornada, segundo os próprios registos de Valve.\n\nFonte: o registo de divulgação da HackerOne relativo a cada relatório, consultado em 2026-09-22 — número, título, equipa, vulnerabilidade, gravidade, datas do relatório e da divulgação e estado, tal como publicado pela HackerOne. Registo da consulta: hackerone-reports.json. Aqui não é indicado qualquer valor de recompensa; não consta nenhum nos registos divulgados que foram consultados.\n\nObservação no terreno · PhishDestroyAs deteções que normalmente põem fim a uma campanha não puseram fim a estas\n\nVimos os servidores de phishing a continuarem a atrair tráfego enquanto transportavam 20 ou mais deteções de fornecedores. Quando enviada pela Web ou por e-mail, uma campanha nesse estado morre em poucos dias — tanto o navegador como o antivírus agem de acordo com esses veredictos. No Steam, nenhum dos dois o faz. Os veredictos sempre existiram. Nada no cliente chegou a perguntar.\n\nO que isto significa para um menor que tenha um antivírus instalado\n\nEle não ignora nenhum aviso nem desativa nada. Chega uma mensagem no Steam — uma faca grátis, um voto para a equipa de um amigo — e a página abre-se no Steam. Ele nunca abre um navegador, por isso o navegador nunca o protege. O seu antivírus está a funcionar e pode já ter classificado esse domínio como malicioso; mas nunca lhe é perguntado. Já existem todos os avisos que poderiam tê-lo impedido. Nenhum deles chega até ele. Ele acredita que nunca saiu de Steam, e de facto não saiu.\n\nA oferta gratuita não é uma invenção do phisher — os itens gratuitos Valve são a forma como os sites de skins e de jogos de azar fazem publicidade, e é precisamente por isso que a mensagem parece normal. Reclamações: o arquivo de execução. Dados relativos à idade e às crianças: Secção 17.\n\nFontes: O Steam apresenta o conteúdo da Web através do Chromium Embedded Framework no steamwebhelper processo — ver Análise técnica da DARKNAVY de 27 de junho de 2024 ↗ e do próprio Valve Steam Fórum Beta do Cliente ↗ arquivado 2025-08-04 ↗. Não se baseia em nenhuma versão do CEF: o Chromium incorporado não é o Chrome e não inclui nenhum dos serviços da Google do Chrome. Navegação segura sem chaves de API: Documento de conceção do Chromium ↗ arquivado 2026-08-21 ↗, Chaves API do Chromium ↗ arquivado 2026-08-30 ↗ («Muitas das APIs do Google utilizadas pelo Chrome são específicas do Google e não se destinam a ser utilizadas em produtos derivados»), e o mesmo efeito noutras compilações sem chave — Barril de cerveja artesanal n.º 193814 ↗. URLs de teste: testsafebrowsing.appspot.com ↗.\n\nDois relógios diferentes\nA idade do domínio.Data da observação.\n\nA data de criação do registo indica quando um domínio foi registado. Um registo OpenID com data indica o host de retorno nesse registo. O primeiro não pode abranger os anos anteriores ao segundo.\n\nO registo completo distingue entre um domínio registável independente, o subdomínio próprio de um site e um caminho direto. Cada linha contém uma ligação para a sua fonte e para o resultado dDNS.\n\nVerificar o registo do domínio →· Descarregar datas de registo ↗· Repetir a observação ↗\n\nParte A — Ficha técnica · Secção 4\nUm ponto final foi encerrado. O rastreio público perdeu uma chave.\nContexto e limites da fonte\n\nSteam introduziu alterações que removeram a visibilidade pública dos IDs de ativos dos artigos e restringiram o acesso ao inventário através da API. O efeito: tornou-se impossível localizar um artigo específico através do seu ID de ativo original a partir de dados públicos. O que se segue é o que era possível antes, o que deixou de ser possível depois e o que isso custa a uma vítima que tenta provar para onde foi a sua propriedade. A data é 2017, de acordo com a conta de engenharia da CSFloat; não foi localizado qualquer registo de alterações da versão Valve. A sequência — cerca de um ano após a declaração sobre jogos de azar de julho de 2016 — constitui o objeto da investigação, não uma conclusão. Os registos dos itens permanecem nos sistemas do Valve; os investigadores externos perderam o acesso à cadeia de IDs originais, enquanto os identificadores float, seed e paint permitem apenas uma correspondência parcial.\n\nAplica-se a regra Valve: Steam O apoio ao cliente não recupera os itens que saíram da sua conta, e cabe-lhe a si provar o que aconteceu. O registo: Em 2017, o Valve encerrou o ponto final que transportava os IDs originais dos itens. Antes disso, qualquer pessoa podia seguir o rasto de uma skin roubada desde a conta da vítima até um bot de um mercado virtual. Depois disso, ninguém fora do Valve consegue fazê-lo. A prova que é solicitada à vítima é a prova que foi desativada — e ainda existe, dentro de Valve.\n\nA Era Pré-Apagão\n\nHistoricamente, cada item virtual gerado no Steam possuía um identificador globalmente único e imutável ID do ativo. As bases de dados OSINT de terceiros poderiam indexar esses IDs. Se um utilizador tivesse um item roubado, os investigadores poderiam rastrear o percurso desse ativo específico à medida que este passava da conta intermédia do ladrão para as contas de armazenamento de um mercado online ou de um site de jogos de azar.\n\nANTES: qualquer pessoa podia rastrear um item desde a conta da vítima, passando por contas intermédias, até um bot de armazenamento de um mercado ou de um casino, utilizando dados públicos.\nApós a alteração\n\nDe acordo com a conta de engenharia da CSFloat, o Valve encerrou o ponto final em 2017 e os IDs originais dos itens deixaram de estar disponíveis para terceiros. Não foi encontrada qualquer declaração Valve sobre o motivo desta alteração. No mesmo período, também não foi identificada qualquer ação pública contra as contas de bots comerciais que movimentavam itens em grande escala.\n\nSeja qual for a razão, essa alteração rompeu a cadeia de custódia pública. Uma vítima já não consegue reproduzir a cadeia de identificação original a partir de dados públicos para demonstrar que um determinado artigo roubado foi vendido através de um mercado ou casino específico. Os registos dos artigos ainda existem nos sistemas da Valve; o público, os investigadores e as autoridades policiais que trabalham com dados públicos não têm acesso a eles.\n\nDEPOIS: já não é possível rastrear um item específico através do seu ID de ativo original a partir de dados públicos. A cadeia de custódia do ID original de um item transferido após 2017 existe apenas dentro da infraestrutura da Valve; nenhum registo desse tipo foi divulgado publicamente. Os identificadores «float», «seed» e «paint» permitem apenas uma correspondência parcial e probabilística.\nIEconItems_730\nOBTER/IEconItems_730/GetPlayerItems/v1/\nCarga útil rastreável (antes da correção)\n\"id\": \"14892281934\",\n\"original_id\": \"11829910211\",\nEstado: A vítima pode rastrear o percurso do item através das contas de bot.\nCarga útil ofuscada (após a aplicação da correção)\nAtual\n\"id\": \"HIDDEN_BY_PRIVACY_SETTINGS\",\n\"original_id\": \"NULL\",\nEstado: as entidades externas já não conseguem rastrear a origem de um item através do ID de ativo original a partir de dados públicos.\nImpacto nas provas: Após a alteração, os dados públicos necessários para rastrear um item específico através do seu ID de ativo original, desde a conta de uma vítima até um bot de um mercado ou de um casino, deixaram de estar disponíveis. Os registos internos ainda existem em Valve; uma vítima, um investigador ou um perito que trabalhe a partir de dados públicos não consegue reproduzir a cadeia do ID original (os identificadores float, seed e paint permitem apenas uma correspondência parcial).\n\nFonte: Relatório da CSFloat Engineering sobre o encerramento, em 2017, de IEconItems_730/GetPlayerItems — blog.csfloat.com/how-floatdb-tracks-items (arquivado 2026-09-21) · os dados apresentados servem apenas para ilustrar a forma do campo, não representando respostas efetivamente capturadas · não foi encontrado qualquer registo de alterações Valve para o encerramento.\n\nParte A — Ficha técnica · Secção 5\nUma sessão. Mais acesso do que o utilizador percebe.\nLimites de contexto e de fonte\n\nA arquitetura da chave API do Valve, tal como se apresentava antes das alterações de 2023, afastava-se dos padrões de referência do setor (OWASP ASVS, NIST SP 800-63B) e constitui o mecanismo descrito nas queixas automatizadas de roubo de inventário preservadas no arquivo de provas (Secções 6–8).\n\nAplicou-se a regra Valve: o titular da conta criou a chave, aceitou os termos e é responsável pela perda — essa é a resposta que consta nas recusas arquivadas. O registo: Até dezembro de 2023, bastava um cookie de sessão roubado para registar essa chave. Sem palavra-passe. Sem Steam Guard. Sem qualquer notificação à pessoa a quem pertencia a conta. O utilizador não criou a chave, não a conseguia ver e foi-lhe dito que a tinha criado. A confirmação por telemóvel foi adicionada em 2023-12-04 — cerca de sete anos após a declaração de 2016 e aproximadamente seis anos após os painéis de fraudes que o arquivo conserva. Esses anos não foram pagos por Valve. Foram pagos pelas contas que, entretanto, foram esvaziadas, sendo algumas delas de crianças.\n\nOWASP ASVS 2.8 / NIST SP 800-63BGRAU DE GRAVIDADE: CRÍTICO\n1. Autenticação reforçada insuficiente\n\nSteam permitia a geração de chaves API com privilégios elevados e de longa duração utilizando apenas um cookie de sessão. Não era necessária qualquer autenticação de dois fatores (Steam Guard) nem qualquer desafio de autenticação reforçada ao configurar ou modificar uma chave API de programador, pelo que a confirmação móvel Steam Guard — o único segundo fator que o Steam oferece — não protegia esta etapa. (Um segundo fator de hardware foi solicitado no próprio sistema de acompanhamento do Valve em 2016 e a questão continua em aberto: Apêndice D, GH-01.)\n\nEstado: sem correção até 2023. Permitia que um script que contivesse um cookie roubado registasse uma chave sem qualquer interação do utilizador.\nOWASP A01:2021 / Princípio do privilégio mínimoGRAU DE GRAVIDADE: CRÍTICO\n2. Ausência do princípio do privilégio mínimo\n\nA API Web Steam não dispunha de quaisquer âmbitos de autorização baseados em funções. Uma chave de API de programador emitida para o estado do inventário em «só leitura» possuía permissões completas de «gravação» — incluindo a capacidade de manipular transações existentes, iniciar novas transações, registar webhooks e recusar transações pendentes válidas.\n\nEstado: falha de conceção sistémica. Uma chave = controlo total de leitura/gravação do inventário e das transações da conta.\nOWASP A07:2021 / SessõesGRAVIDADE: ELEVADA\n3. Gestão de sessões com falhas\n\nOs utilizadores relataram que as sessões web sequestradas provenientes de intervalos de IP de servidores de alojamento continuavam ativas. A prática habitual consiste em encerrar as sessões em caso de anomalias geográficas e de alteração de palavra-passe; os relatos dos utilizadores recolhidos no arquivo descrevem sessões que permaneceram ativas após uma alteração de palavra-passe.\n\nEstado: comportamento relatado (queixas de utilizadores no arquivo). As sessões podiam gerar chaves API sem necessidade de reautenticação.\nO bloqueio ao nível do domínio era tecnicamente viávelVIÁBILIDADE DA APLICAÇÃO DA LEI\n4. O bloqueio de hosts de autenticação ao nível do domínio era tecnicamente viável\n\nValve já gere uma lista de domínios (o «Link Filter») e já recebe todos os nomes de host de autenticação nas suas próprias solicitações OpenID. Os dois mecanismos não estão ligados de forma alguma visível do exterior: a partir de 2026-09-22, em 26 pares, o domínio principal estava no filtro, enquanto o proxy que transportava o seu login não estava.\n\nLigar estes dois elementos é uma tarefa simples de engenharia: leia o openid.realm obter o nome do anfitrião de cada pedido recebido, compará-lo com uma lista e recusar ou assinalar o pedido. A ilustração à direita mostra a estrutura dessa rotina. Recusar o anfitrião de autenticação — em vez de apenas a página inicial pública — interromperia o passo «Iniciar sessão com Steam», do qual estas plataformas dependem.\n\nNão há provas públicas que indiquem que o Valve realize essa verificação. A taxa combinada do Mercado Comunitário Steam, de cerca de 15%, aplica-se às vendas realizadas no interior do Mercado; não é cobrada nas transações externas destas plataformas.\n\nblock_auth_hosts.pyILUSTRAÇÃO\n// Ler o host Steam que já está a receber — não é necessário efetuar a verificação\ndef on_openid_request(request):\nhost = parse_openid_realm(request)\nse anfitrião em domínios_bloqueados:\nrecusar (pedido)\nNota: Pseudocódigo apenas a título ilustrativo. Ambas as partes já existem em Valve — o nome de host do autorizaador surge na solicitação e a lista de domínios corresponde ao Filtro de Ligações. Não há qualquer registo público que explique por que razão não estão ligados.\nSecção 5.1 — As normas não foram retiradas de circulação\nO Valve compila de acordo com estas regras todos os dias. Aqui, não conseguiu compilar de acordo com elas.\n\nA Steam está disponível na App Store e no Google Play, efetua vendas através dos principais processadores de pagamentos com cartão e utiliza APIs de terceiros, tal como qualquer outra grande plataforma. Cada uma dessas relações implica um requisito de segurança publicado e datado que a Valve tem de cumprir para continuar a operar. Compare as datas desses requisitos com as datas em que a própria API Web da Steam adquiriu as mesmas proteções. Nada do que se segue é uma norma privada, um memorando interno ou um segredo comercial: cada linha é um documento público com uma data de publicação.\n\nRequisitos de segurança externos publicados, com as respetivas datas, comparados com a data em que a API Web Steam adquiriu o controlo equivalente\nA norma publicada e a data em que entrou em vigor\tA API Web Steam sobre a mesma questão\nAutorização com âmbito específicoOAuth 2.0 — RFC 6749, Outubro de 2012. A secção 3.3 define scope Assim, um cliente recebe apenas o acesso que solicita. Desde então, tem sido a configuração predefinida de todas as principais APIs de plataformas.\tOs âmbitos granulares surgiram em 16 de janeiro de 2026.Antes disso, uma única chave da API Web Steam concedia acesso total de leitura e escrita às transações da conta, independentemente do motivo pelo qual tivesse sido emitida. Treze anos e três meses após a especificação que define o controlo.\nUma chave não é uma autorizaçãoDocumentação do Google Cloud: Uma chave API padrão não autentica um principal, e no caso das APIs que criam ou gerem recursos, Não utilize chaves de autorização em ambiente de produção.\tA chave da API Web Steam era exatamente isso.Uma cadeia de caracteres ao portador, emitida para uma conta, suficiente por si só para consultar o inventário, cancelar uma transação pendente e enviar uma nova. Nenhum mandante foi autenticado no momento da utilização.\nAutenticação multifatorial no acesso privilegiadoPCI DSS 3.2, requisito 8.3 — obrigatório a partir de 1 de fevereiro de 2018 para todos os acessos administrativos não efetuados através da consola e todos os acessos remotos ao ambiente de dados dos titulares de cartões. A Apple passou então a exigir a autenticação de dois fatores para todos os titulares de contas do Programa de Desenvolvedores a partir de 27 de fevereiro de 2019: Os programadores com a função de «Titular da conta» num programa para programadores terão de ativar a autenticação de dois fatores para iniciar sessão.\tFoi necessário um segundo fator para criar uma chave API a partir de 4 de dezembro de 2023.Até então, bastava um cookie de sessão roubado, sem qualquer aviso no telemóvel do titular da conta nem qualquer notificação posterior. Quatro anos e nove meses depois de a Apple ter obrigado a própria Valve a utilizar uma autenticação de dois fatores apenas para iniciar sessão num portal de programadores.\nCiclo de vida e revogação das credenciaisA Twitch exige que todas as aplicações de terceiros: A sua aplicação deve validar o token OAuth no momento do arranque e, posteriormente, a cada hora, e afirma que realiza auditorias às aplicações que não o fazem. A sua API v5 antiga foi definitivamente retirada de serviço em 28 de fevereiro de 2022 de acordo com um horário publicado.\tNão existe qualquer registo publicado sobre o ciclo de vida da chave.A alteração de 2023 protegeu o ponto final de criação. Nenhuma declaração Valve associada a essa alteração aborda as chaves já registadas, e não foi publicado qualquer registo de alterações a acompanhar a mesma. Não é possível determinar, a partir dos dados públicos, se as chaves criadas antes dessa alteração foram invalidadas — o que é precisamente a questão que um titular de dados precisaria de ver esclarecida para saber se uma chave criada na sua conta há vários anos ainda está ativa.\nReferência arquitetónica // Token Architecture\nÂmbitos detalhados do GitHub vs Valve Steam API Web\n\nValve programadores gerem diariamente software de código aberto no GitHub utilizando tokens granulares com o mínimo de privilégios. Compare isso com a chave monolítica emitida para 130 milhões de Steam jogadores.\n\nToken de granularidade elevada do GitHub\nUtilizado por Valve no GitHub\n\nToken de granularidade fina com isolamento por âmbito e aplicação obrigatória do ciclo de vida.\n\nAcesso ao repositório:Apenas repositórios selecionados (1 repositório)\nConceder permissões:Apenas leitura [✓]\nCódigo e Segredos:Sem acesso [✕]\nData de validade:30 dias (TTL obrigatório)\nRegisto de auditorias:IP, User-Agent e data e hora\nSituação de segurança: O token de privilégios mínimos limita os danos a um único recurso de leitura apenas.\n!Valve Steam Chave da API Web\nDistribuído a 130 milhões de utilizadores\n\nUma única cadeia de caracteres principal de 32 caracteres que confere autoridade total ou nenhuma autoridade em matéria de transações e inventário.\n\nAcesso à conta:CONTA COMPLETA (Monolítica)\nGestão de transações:Ler, Cancelar, Recusar [!]\nÂmbitos granulares:NENHUM (Chegou em 2026, com 13 anos de atraso)\nData de validade:NUNCA (Válido por tempo indeterminado)\nRegisto de auditorias:NENHUM (O utilizador não tem qualquer histórico de IP)\nVulnerabilidade: A chave roubada permite a interceção silenciosa de todas as ofertas comerciais enviadas.\nA norma aplicada numa única direção\n\nSuponha que um fornecedor Valve — um prestador de serviços na nuvem, um processador de pagamentos, uma CDN — tenha deixado um ponto de acesso de credenciais sem um segundo fator de autenticação e que, meses mais tarde, os próprios dados corporativos de Valve tenham sido divulgados através de uma chave gerada nesse ponto de acesso. Será que Valve aceitaria que a culpa recaiu sobre quem clicou na ligação? As recusas arquivadas e preservadas neste dossiê respondem à questão inversa para o utilizador: a posição assumida é que o titular da conta criou a chave e arca com a perda. Essa mesma arquitetura é descrita como uma falha do fornecedor num sentido e uma responsabilidade do utilizador no outro. O que se passa, na realidade, não é uma questão técnica, nem é algo que esta investigação possa resolver — cabe a um tribunal ou a uma autoridade de supervisão decidir.\n\nIlustração, não prova — a norma interpretada de forma contrária\nUm processador de pagamentos que permitia que um script de terceiros gerasse uma credencial de transação com privilégios totais a partir apenas de um cookie do navegador, sem qualquer aviso ao titular da conta.\nUm fornecedor de identidade que colmatou a falha através da qual os seus tokens foram emitidos e não publicou qualquer informação sobre os tokens já emitidos.\nUm banco que respondeu a uma transferência contestada, observando que a credencial utilizada estava registada na própria conta do cliente, e encerrou o processo.\n\nNenhuma destas observações se pretende ser uma conclusão sobre qualquer empresa específica. Trata-se das mesmas decisões de conceção, transpostas para um contexto em que a resposta das autoridades de supervisão está bem documentada — que é precisamente a comparação que se pede a uma entidade reguladora que faça.\n\nO que consta do processo: os controlos ausentes da API Web Steam eram públicos, desatualizados e, em vários casos, constituíam condições Valve que a empresa tinha de cumprir para continuar a comercializar os seus próprios produtos. O intervalo entre cada norma e a alteração equivalente Steam é mensurável e está definido acima. O que isso não esclarece é o motivo. Não foi encontrada qualquer justificação para nenhum destes intervalos Valve, nem se pressupõe aqui qualquer justificação; esse registo encontra-se no Valve e não foi publicado.\n\nFontes, todas elas documentos públicos: OAuth 2.0 — RFC 6749, outubro de 2012 ↗ · Google Cloud — Documentação sobre chaves API ↗ · Requisito 8.3 da norma PCI DSS 3.2 — Guia de recursos do PCI SSC ↗ · Apple — Requisito de autenticação de dois fatores a entrar em vigor para os titulares de contas, 20 de fevereiro de 2019 ↗ arquivado 2025-05-06 ↗ · Twitch — requisito de validação do token ↗ e o Aviso de encerramento da v5 ↗ arquivado 2025-01-27 ↗. As datas do Steam são as que constam no registo de atualizações desta secção; as entradas de 2023 e 2026 são as que o Valve lançou sem um registo de alterações. Consultado em 2026-09-22.\n\nRegisto de atualizações do próprio Valve — datado, proveniente de fontes públicas\nData\tValve alteração\tJá foi anunciado?\tO que fechou\tAtraso: mecanismo público → corrigido\tFonte\n2026-09-01\tSinalização automática de conversas suspeitas\tSim\tLinks/padrões perigosos nas conversas em grupo\t—\tnotícias ↗\n2026-01-16\tÂmbitos granulares da API Web do Steamworks\tSim\tÂmbitos de privilégios mínimos para chaves de programador\t—\tanúncio ↗\n2025-07-15\tProteção de negociação CS2 e janela de reversão\tSim\tNada. Não se trata de uma correção de segurança que resolva a causa principal. O acesso à recuperação de contas por parte do apoio técnico permanece inalterado. O desencadeamento da reversão implica um bloqueio automático de transações durante 30 dias (Skinvault ↗), enquanto o choque nas transações à vista provocou uma queda de $104M (-25%) na capitalização de mercado nas últimas 24 horas (CSMarketCap ↗). Em 2026, os temporizadores passaram a ser aplicados individualmente a cada artigo (Skin.land ↗).\t—\tPerguntas frequentes ↗\n2025-05-14\tComunicado sobre a segurança da conta\tSim\tOrientações sobre Stealer / sequestro de sessão\t—\tanúncio ↗\n2024-10-02\tCS2 «The Armory» — 7 dias de espera\tSim\tSuspensão das transações/do mercado de itens do Armory\t—\tanúncio ↗\n2024-09-18\tRestrição comercial relativa ao início de sessão num novo dispositivo\tSim\tBloqueio de transações de 2 a 7 dias em dispositivos novos\t—\tPerguntas frequentes ↗\n2024-02-14\tSuspensão da alteração do nome e do avatar do perfil\tSim\tPeríodo de espera de 2 a 4 horas para as transações após a mudança de nome\t—\tpublicação ↗\n2023-12-04\tConfirmação por telemóvel para chaves API\tSem registo de alterações\tRegisto silencioso de chaves apenas através de cookies\t≈6 anos após os painéis da época de 2017\tpágina de desenvolvimento ↗\n2023-10-24\tAutenticação multifatorial por SMS para publicações de compilações de jogos\tSim\tPublicação de compilações no Steamworks\t—\tanúncio ↗\n2023-07-12\tAviso sobre o conteúdo da biografia personalizada\tSim\tLinks de phishing nas biografias\t—\tfórum ↗\n2023-01-25\tPerfil {LIGAÇÃO REMOVIDA} e tempo de recarga\tSim\tLinks no texto do perfil\t—\tPerguntas frequentes ↗\n2022-10-24\tReestruturação do processo de início de sessão e truncamento de cookies\tSem registo de alterações\tSessões roubadas infinitas\t— (Migração de tokens do IAuthenticationService)\tnotícias ↗\n2022-10-12\tAplicação móvel 3.0: início de sessão por QR\tSim\tPainel de revogação da autorização da sessão\t—\tnotícias ↗\n2022-05-10\tPontos finais de cancelamento de transações removidos\tSem registo de alterações\tTroca de oferta (cancelar e reenviar)\t≈5 anos após os painéis da época de 2017\tedição n.º 325 ↗\n2020-05-25\tBloqueio de trocas de 7 dias no Dota 2\tSim\tRevenda rápida de artigos\t—\tblog ↗\n2018-03-29\tBloqueio de trocas de 7 dias no CS:GO\tSim\tLavagem instantânea de bots\t≈20 meses após a declaração de julho de 2016\tblog ↗ arquivado 2025-02-26 ↗\nFontes: as publicações Valve indicadas nos links, as páginas de ajuda e os issues do GitHub, conforme as datas indicadas. Três correções decisivas foram lançadas sem registo de alterações (maio de 2022, outubro de 2022, dezembro de 2023) e foram detetadas pelos utilizadores, não tendo sido anunciadas por Valve — essa assimetria faz parte do registo de aplicação. Os atrasos são calculados apenas nos casos em que a própria datação do dossiê (declaração de julho de 2016; painéis de fraude da época de 2017) fornece o ponto de partida; «—» significa que não foi estabelecido aqui qualquer ponto de partida.\nParte A — Ficha técnica · Secção 6\nSimulador Interativo de Explorações e Desvio de Controlo\nContexto e limites da fonte\n\nUma reconstrução do percurso desde a mensagem de phishing até ao registo da chave no lado do servidor e à troca da transação. Antes de 2023, uma chave de API Web registada numa conta podia consultar o seu inventário, cancelar uma oferta de transação pendente e criar uma nova, sem que fosse apresentado ao titular da conta qualquer ecrã de confirmação da transação para qualquer uma dessas ações. Trata-se da ausência do princípio do privilégio mínimo (OWASP A01:2021). Os tempos apresentados nesta simulação são meramente ilustrativos e não constituem medições em tempo real da plataforma atual.\n\nSiga passo a passo a simulação do sequestro. Cada fase mostra o que o titular da conta vê e, ao lado, a chamada Steam que recebe nesse mesmo momento. Cada uma dessas chamadas é devidamente autenticada. Nada nesta sequência precisa que a autenticação do Steam falhe — é necessário que a chave que este emite não tenha âmbito (OWASP A01:2021).\n\nO que o jogador vê. O que muda por trás disso.SIMULADOR DE PERCORSO\nEtapa 5 / 5\n\nA exploração foi concluída. Ao esperar uma notificação no telemóvel relativa à sua transação original, a vítima aprova a transação de substituição. Trata-se de uma simulação forense integrada que demonstra como a ausência do princípio do privilégio mínimo (OWASP A01:2021) permite o sequestro automatizado de ativos em menos de um segundo.\n\n01 / A ISCA DO CHATUm amigo pede para votarA vítima recebe uma mensagem com um link.\n02 / O INÍCIO DE SESSÃOUm portal de sósiasA vítima introduz as credenciais de início de sessão.\n03 / O ACESSOCriação da API da Web SilenciosaO atacante regista uma chave de programador.\n04 / A MUDANÇAComércio legítimo trocadoO bot «Clone» duplica o destinatário-alvo.\n05 / CONFIRMAÇÃOCópia aprovadaFoi aprovada uma oferta errada no telemóvel.\nO mesmo passo, visto da perspetiva da redeReconstrução do padrão anterior a 2023 · formas ilustrativas de chamadas\nVítimaAprova a notificação no telemóvel que era esperada para a transação original.\nAtacanteRecebe os artigos na conta clonada.\nSteam vêUma transferência confirmada pelo titular da conta num dispositivo registado.\nConfirmation genuine — made by the account holder\nRecipient the clone bot, not the intended counterparty\nThe confirmation is authentic. The offer it confirms is not the one the user initiated.\n\nO registo que ficou para trás: uma transação aprovada pelo utilizador. Esse é o registo que o Steam Suporte consulta quando a reclamação chega, e a razão pela qual as reclamações arquivadas foram encerradas como erro do utilizador. As reclamações encontram-se em o arquivo de execução.\n\nParte A — Ficha técnica · Secção 7\nOs pontos finais subjacentes à sequência.\nContexto e limites da fonte\n\nEstes são os Steam pontos finais da API Web que os scripts de sequestro identificados utilizaram para interceptar transações sem passar pelas etapas de confirmação do lado do navegador.\n\nQuatro pontos finais documentados são suficientes para realizar toda a tarefa. Nenhum deles apresenta falhas, nem é necessário explorá-los — basta que uma chave válida os chame e Steam responda. A chave foi a única coisa que o atacante teve de roubar.\n\nIEconService / GetTradeOffers / v1SONDAGEM\n\nUtilizado para monitorizar as ofertas de negociação da conta. Os scripts consultam este ponto de extremidade repetidamente com a chave API comprometida; este devolve os detalhes das ofertas de negociação recém-criadas, pendentes ou modificadas. Os intervalos de consulta não são medidos aqui.\n\nVetor de ameaça: Apresenta os números de identificação das ofertas comerciais pendentes e os detalhes do perfil do destinatário.\nIEconService / CancelTradeOffer / v1INTERAÇÃO\n\nUtilizado para invalidar programaticamente a oferta de transação legítima do utilizador. Antes de 2023, não existia qualquer autenticação reforçada a proteger a chave, pelo que um servidor automatizado podia cancelar uma oferta assim que esta fosse detetada, sem qualquer aviso prévio ao titular da conta.\n\nVetor de ameaça: Anula a transação antes de o titular da conta concluir a confirmação através do telemóvel.\nISteamUser / GetPlayerSummaries / v2RECON\n\nConsulta para obter o nome do perfil, o URL da imagem do avatar e o nível do destinatário legítimo da transação. Isto permite que o script adapte uma conta clonada previamente preparada para que corresponda. Não é medido qualquer tempo nesta etapa.\n\nVetor de ameaça: Fornece os dados necessários para se fazer passar pelo destinatário pretendido.\n/dev/ajaxregisterkeyCRIAÇÃO\n\nO ponto final de registo do Steam para chaves. Historicamente, qualquer sessão ativa de cookies do navegador (`steamLoginSecure`) podia registar uma chave sem uma confirmação do Steam Guard no dispositivo móvel e sem qualquer notificação ao titular da conta.\n\nVetor de ameaça: Uma credencial persistente criada por um script, sem que o titular da conta se aperceba.\nParte A — Registo técnico · Secção 8 · Artigo 7.º do RGPD\nUma caixa assinalada. De quem é essa ação?\nContexto e limites da fonte\n\nAo recusar o reembolso, Steam As respostas do Apoio ao Cliente guardadas no arquivo defendem que o titular da conta criou a chave API e, ao assinalar a caixa, aceitou os termos.\n\nA resposta do serviço de apoio atribui a chave ao titular da conta. A questão é saber se o registo permite determinar quem o criou efetivamente.\n\nNo padrão de roubo de chaves API observado, no entanto, a vítima nunca viu nem acedeu à página de criação da chave API. O campo de consentimento é enviado por um script que executa um POST «headless» com o cookie de sessão roubado.\n\nNos termos do artigo 7.º e do n.º 11 do artigo 4.º do RGPD, o consentimento deve constituir uma manifestação de vontade livre, específica, informada e inequívoca do titular dos dados. A posição dos autores é que um campo de aceitação de termos submetido por um script malicioso com um cookie roubado, sem que seja apresentada qualquer página ao titular da conta, não pode corresponder a essa definição. Cabe à autoridade de controlo determinar se isso se verifica.\n\nAnálise forense de cargas úteis: registo de chaves\nPUBLICAÇÃO https://steamcommunity.com/dev/ajaxregisterkey\n// Carga útil do pedido (injetada através de um script de sequestro)\n{\n\"agreeToTerms\": \"concordado\", <-- inserido automaticamente, sem intervenção humana\n\"domínio\": \"localhost\", ← não validado — aceita-se qualquer valor, incluindo «localhost»\n\"sessionid\": \"8f0d8ef763ab2140bf89de2a\"\n}\nA questão para a autoridade de supervisão: no caso de o titular da conta nunca ter clicado no campo de consentimento, se a aceitação dos termos registada na conta cumpre o requisito previsto no artigo 7.º de uma indicação livre, específica, informada e inequívoca da vontade do titular dos dados e se o Steam Apoio pode basear-se nisso para recusar uma reclamação.\n\nFonte: formato do pedido de registo da chave, tal como reconstruído a partir do ponto de acesso público e dos relatórios de sequestro conservados no arquivo de provas (versão pesquisável de 2026-09-17) · o identificador de sessão apresentado é um marcador de lugar, não um valor capturado.\n\nAutópsia forense · O vetor de substituição comercial\nComo o Valve conseguiu finalmente neutralizar a «substituição comercial» — e por que razão foram necessários 7 anos de soluções alternativas\n\nHá quase uma década que o «Substituição da chave da API» (ou «Golpe MitM da API») foi o modelo de roubo de contas mais lucrativo no Steam, desviando centenas de milhões de dólares em skins de jogadores desprevenidos. O Valve não erradicou a falha corrigindo a arquitetura vulnerável da API; em vez disso, o Valve passou sete anos a implementar quatro barreiras de atrito em toda a plataforma que prejudicaram a liquidez do comércio da comunidade, sem resolver a causa principal.\n\n1. A Morte por Mimetismo\nTempo de espera para avatar e nome (fevereiro de 2024)\n\nA fraude exigia uma imitação em frações de segundo: o bot fraudulento interceptava uma transação a enviar e extraía o avatar/nome do destinatário através de ISteamUser, e clonou o perfil em 200 ms. A 14 de fevereiro de 2024, Valve implementou discretamente uma medida obrigatória Tempo de espera de 2 a 4 horas para a troca (Erro 34) imediatamente após qualquer alteração do nome do perfil ou do avatar. Um bot já não pode clonar um destinatário em tempo real sem ficar impedido de realizar transações.\n\n2. A Morte Económica\nInversão de tendência de 7 dias no CS2 (julho de 2025)\n\nValve introduziu medidas unilaterais Reversões de posições para itens do Counter-Strike. Qualquer skin trocada fica marcada como «Protegida contra trocas» durante sete dias. Se uma vítima descobrir uma substituição, basta clicar em «Anular transação» no Suporte Steam, e a skin é imediatamente devolvida ao seu inventário, ao mesmo tempo que o destinatário fica bloqueado. Como o bloqueio de transação de 7 dias impede que os burlões transfiram o item para um site de resgate, o roubo torna-se inviável.\n\n3. A morte do «Silent Key»\nNotificação push obrigatória para a API (dezembro de 2023)\n\nHistoricamente, um cookie de sessão roubado permitia que scripts maliciosos executassem um pedido POST em segundo plano e sem interface gráfica para /dev/ajaxregisterkey sem notificar a vítima. A 4 de dezembro de 2023, a Valve impôs a obrigatoriedade de uma confirmação explícita por notificação push na aplicação móvel Steam para gerar uma chave de API Web, eliminando o fornecimento silencioso de chaves em segundo plano.\n\n4. Avisos no aplicativo móvel\nBanners com a data de criação e o nome da conta (2022–2024)\n\nValve reformulou a janela modal de confirmação na versão móvel para apresentar o parceiro comercial Steam tempo de existência da conta (data de criação), nível Steam e um aviso explícito em âmbar: «Este utilizador alterou recentemente o nome do seu perfil», quebrando a ilusão visual para as vítimas mais atentas.\n\nAs três falhas na solução de remendo de Valve: por que é que os burlões simplesmente mudaram de alvo\n1. A lacuna legal relativa à exclusão de jogos (Dota 2 e TF2)\n\nAs «Trade Reversals» foram implementadas exclusivamente para o Counter-Strike 2. Os itens do Dota 2 e do Team Fortress 2 continuam completamente desprotegidos devido às complexidades da criação e da encaixe de gemas. Os itens de nível elevado que valem milhares de dólares (Dragonclaw Hooks, Golden Baby Roshans, Unusual TF2 burning flames) não têm qualquer período de reversão. Os burlões limitaram-se a redirecionar a interceção automatizada da API para os negociantes de Dota 2 e TF2, onde o Suporte Steam aplica rigorosamente a sua política de 2016 de «não restabelecimento de itens».\n\n2. O reservatório «Zombie Key» (Sem prazo de validade)\n\nEnquanto o Valve adicionou a autenticação de dois fatores (2FA) por notificações push no telemóvel para gerar novo chaves em dezembro de 2023, Valve chaves API legadas existentes nunca foram revogadas, caducaram ou foram eliminadas. Milhões de contas ativas que geraram chaves (ou cujas chaves foram criadas silenciosamente por phishing/malware antes de dezembro de 2023) ainda possuem credenciais ativas com prazo de validade zero (sem TTL) e tempo de espera de inatividade zero. Os autores de ameaças mantêm enormes bases de dados históricas destas chaves persistentes, continuando a consultar IEconService sem perturbações.\n\n3. A sanção imposta à vítima: suspensão das transações durante 30 dias\n\nMesmo no CS2, o Valve penaliza o jogador que foi alvo de uma fraude: clicar em «Anular transação» no Steam Suporte inflige automaticamente uma proibição obrigatória de negociação e de acesso ao Mercado Comunitário durante 30 dias na conta da vítima. Valve aplica ao utilizador uma suspensão de um mês da plataforma como medida dissuasora contra anulações «frívolas», desencorajando as vítimas de anularem transações relativas a artigos líquidos de menor valor.\n\nO escândalo regulatório central: sete anos de soluções alternativas contra um único âmbito de API\n\nPor que é que a Valve passou sete anos a criar restrições às transações, períodos de espera nas contas e bloqueios reversíveis às transações — perturbando toda a economia do jogo e fazendo desaparecer $104M em capitalização de mercado — em vez de implementar a solução padrão do setor?\n\nConforme comprovado pelo lançamento oficial do Valve no Steamworks, a 16 de janeiro de 2026 (Anúncio #493839547938902179 ↗), Valve já construído Grupos de permissões granulares (Geral, Microtransações, Economia, Dados de vendas) e Lista de endereços IP autorizados para chaves de editor corporativas. A Valve já dispunha da solução técnica há anos. Uma única caixa de seleção visível para o utilizador—«Impedir que esta chave da API Web aceda ao IEconService (Gestão de Transações)» ou uma lista de endereços IP domésticos autorizados — teria erradicado o esquema de substituição de transações em 2018, sem quaisquer danos colaterais económicos. A Valve recusou-se a conceder aos jogadores regulares a proteção que criou para os seus parceiros empresariais.\n\nParte B — Regulamentos e histórico de aplicação · Secção 9\nO seu regulamento. As plataformas registadas.\nLimites de contexto e de fonte\n\nEste registo mapeia as cláusulas explícitas do Steam Acordo de Subscrição (SSA) e Steam Conduta online (SOC) orientações dirigidas diretamente contra entidades comerciais ativas e de grande dimensão.\n\nA regra: sem fins comerciais, sem jogos de azar, sem bots — e a Steam Support invoca essas cláusulas quando se recusa a devolver os artigos de uma vítima. O registo: as mesmas cláusulas, à primeira vista, abrangem as plataformas comerciais constantes deste registo, que funcionam com Steam identidades, Steam bots e Steam transferências. A cláusula é aplicada à pessoa que perdeu as peles e não, segundo qualquer registo publicado, às empresas que as transportaram.\n\nNas reclamações arquivadas, o Apoio Steam refere o «Proibida a utilização comercial» e \"Sem automatização/bots\" cláusulas quando se recusam a restituir bens às vítimas de fraude com chaves API. As mesmas cláusulas aplicam-se, à primeira vista, às plataformas comerciais registadas neste dossiê, que realizam a autenticação através de Steam OpenID e movimentam bens através de contas automatizadas Steam. Não se estima aqui qualquer valor de receitas a nível do mercado (ver as estatísticas de aplicação da lei abaixo). O que o registo mostra é a regra aplicada a contas individuais nos casos arquivados e a ausência de registos publicados de aplicação da lei por operador para as plataformas. É essa assimetria que esta secção documenta.\n\nA questão central / aplicação seletiva da leiRegras → Escala → Responsabilização\nUm único conjunto de regras. Aplicação desigual.\n\nO registo revela que os serviços comerciais utilizam identidades Steam, inventários, bots e transferências como infraestrutura operacional. A SSA proíbe a exploração comercial e a automatização sem autorização. As queixas arquivadas mostram que essa regra se aplicava a contas individuais, enquanto o registo público não apresenta um registo equivalente, operador a operador, para as plataformas aqui documentadas. Publique a regra, as provas e a decisão de aplicação da lei para cada uma delas.\n\n189sites abrangidos pela auditoria\n44rotas de domínios separados no registo ativo — 27 com um ficheiro de provas publicado, 17 recolhidas manualmente. Só a auditoria de 189 sites resolveu 25 delas; o registo acrescenta as rotas recolhidas manualmente.\n12 anos e 6 mesesO site csgogem.com foi bloqueado no Filtro de Links; api.csgem.com registado em 2014-03-08 e nunca bloqueado — um dos 26 pares deste tipo até 2026-09-22\nSem total verificadoestimativa de receitas a nível do mercado excluída\nSteam Conduta online\n«…não deve realizar, nem tentar realizar, nenhuma das seguintes ações no Steam: […] Envolver-se em atividades comerciais. Exemplos desse tipo de comportamento proibido incluem: publicar anúncios; organizar concursos; jogos de azar; comprar ou vender contas Steam; vender conteúdos, cartões-presente ou outros artigos; e mendigar.\"\n\nstore.steampowered.com/online_conduct ↗ arquivado 2026-09-21 ↗\n\nSSA § 2.G — Utilização comercial\n«…[não pode] explorar o Conteúdo e os Serviços, nem qualquer parte dos mesmos, para quaisquer fins comerciais, salvo nos casos expressamente permitidos noutra parte do presente Acordo…»\n\nAs notificações de Valve de 2016, tal como relatado, invocavam a licença pessoal e não comercial. Nenhum operador apresentou, para que conste, uma autorização Valve. store.steampowered.com/subscriber_agreement ↗ arquivado 2026-09-18 ↗\n\nSteam Termos de Utilização da API Web\n«Não é permitido utilizar a API Web Steam nem os Dados Steam de forma alguma que viole o Contrato de Assinante Steam.»\n\nAs plataformas de venda de skins de terceiros funcionam através de contas automatizadas que utilizam a API Steam. O texto da regra não prevê qualquer exceção para a escala comercial. steamcommunity.com/dev/apiterms ↗ arquivado 2026-09-21 ↗\n\nSSA § 4.C\nAutomação\n\nOs scripts, os bots e a interação não humana estão restringidos. O livro-razão regista transações efetuadas por bots, redes de contas e encaminhamento automatizado em escala comercial.\n\nInspecionar 153registos marcados com esta cláusula ↗\nO que consta no registo ao abrigo desta cláusula153 plataformas marcadas\nAbertura do processo15\nSkin Casino13\nMercado CS29\nRoleta da Pele8\ncsgoempire.com→csgoempirelogin4.comCasino\nrollbit.com→rbsnin.comCasino de Criptomoedas\n500.casino→fivezerozero.coCasino licenciado\n\nDestes, 153 estão também classificados ao abrigo do §2.G da SSA e 2 estão também classificados ao abrigo do artigo 1.C do SSA — os mesmos serviços estão abrangidos por mais do que uma cláusula, razão pela qual os exemplos se repetem.\n\n28 foram observados utilizadores do 153 a autenticarem-se através de um domínio registável distinto. Uma «tag» regista uma observação datada que coloca a plataforma no âmbito da cláusula tal como está redigida; não se trata de uma violação confirmada judicialmente, e não foi apresentada qualquer autorização Valve para nenhum deles.\n\nSSA § 2.G\nUtilização comercial\n\nA exploração comercial requer autorização expressa. Compare os modelos de negócio documentados, a sua escala e quaisquer autorizações ou medidas de aplicação divulgadas.\n\nInspecionar 175registos marcados com esta cláusula ↗\nO que consta no registo ao abrigo desta cláusula175 plataformas marcadas\nAbertura do processo15\nSkin Casino13\nMercado CS29\nRoleta da Pele8\ncsgoempire.com→csgoempirelogin4.comCasino\nrollbit.com→rbsnin.comCasino de Criptomoedas\n500.casino→fivezerozero.coCasino licenciado\n\nDestes, 153 estão também classificados ao abrigo do §4.C da SSA e 24 estão também classificados ao abrigo do artigo 1.C do SSA — os mesmos serviços estão abrangidos por mais do que uma cláusula, razão pela qual os exemplos se repetem.\n\n28 foram observados utilizadores da 175 a efetuar a autenticação através de um domínio registável distinto. Uma marca registada regista uma observação datada que coloca a plataforma na alçada da cláusula tal como está redigida; não se trata de uma violação confirmada judicialmente, e não foi apresentada qualquer autorização da Valve para nenhum deles.\n\nSSA § 3.A\nVPN e ocultação da localização\n\nO disfarce da localização da residência através de um proxy IP pode levar ao cancelamento do serviço. Os servidores de autenticação em domínios distintos requerem uma análise à parte: é necessário determinar o que está a ser disfarçado e qual a regra que se aplica.\n\nVerificar as informações relativas ao host de autenticação ↗\nSteam Ajuda / Política de URLs\nOcultação de links\n\nSteam proíbe os encurtadores de links e as ferramentas que ocultam os destinos dos links. Um domínio de autenticação separado — rbsnin.com no fluxo de início de sessão do Rollbit, auth.dota.trade no CS.MONEY — levanta a questão semelhante de saber se o destino apresentado ao verificador OpenID do Steam identifica o site em funcionamento.\n\nPolítica de URLs do Valve ↗\n\nReferências às regras: Steam Contrato de Subscrição, revisão de 10 de setembro de 2026 arquivado 2026-09-18 ↗ · Steam Termos de Utilização da API Web arquivado 2026-09-21 ↗ · Steam Política de URLs (ofuscação de links). Os números referem-se aos registos e às etiquetas deste dossiê; não correspondem a um recenseamento das infrações julgadas.\n\nO défice de confiança\nQuem analisa a decisão quando o apoio encerra o processo?\n\nAs reclamações arquivadas referem-se a sanções permanentes, reclamações sem resposta e recusas em restituir artigos roubados. Compare esses relatos com o histórico real dos bilhetes, as soluções disponíveis e os registos de acesso à conta. Uma explicação genérica relativa a phishing não permite determinar quem iniciou uma reposição ou criou uma chave API.\n\nLeia as reclamações registadas ↗Solicitar os registos subjacentes →Gráfico de relações do moderador →\nParte B — Regulamentos e histórico de aplicação · Secção 10\nUma API de automatização. Uma regra contra a automatização.\nContexto e limites da fonte\n\nA questão que esta secção coloca é como conciliar estes dois aspetos: quais as utilizações da API que são autorizadas, por quem e com base em que critérios publicados. Não se estima aqui o número de utilizadores comerciais autorizados da API, nem tal número está implícito na ausência de uma lista publicada — a ausência é a conclusão, não um número subjacente. As mensagens de apoio Steam citadas acima são reproduzidas pelo projeto ArchiSteamFarm na sua própria secção de perguntas frequentes (verificadas literalmente 2026-09-22); não se trata de Valve publicações, e as contas para as quais foram enviadas não são identificadas.\n\nA regra (SSA § 4.C): sem scripts, sem bots, sem sistemas não humanos no Steam. O registo: Valve disponibiliza uma API REST sem interface de utilizador cujo único objetivo é a automatização entre servidores e fornece a chave a qualquer conta. Os utilizadores são banidos por utilizarem automação; a interface de automação é um produto da própria Valve. Nunca foi divulgado quais são as utilizações comerciais autorizadas.\n\nA falácia do «desenvolvedor de jogos»\nSDK do Steamworks (autêntico)\n\nUtilizado por estúdios de jogos legítimos para integrar conquistas, sistema de emparelhamento e tabelas de classificação nos seus clientes de jogo. Requer uma integração complexa em C++ e a adesão como parceiro oficial.\n\nSteam API Web (A lacuna)\n\nUma arquitetura JSON/REST sem cabeçalho concebida para servidores web externos. No padrão «hijack» aqui documentado, é utilizada para ler inventários e manipular transações ponto a ponto a partir de servidores remotos; as suas utilizações legítimas não estão catalogadas neste dossiê.\n\nA quem se destina a chaveUm utilizador comum Steam não necessita, no próprio cliente, de uma chave de API Web; a página da chave encontra-se numa URL destinada a programadores e a sua finalidade, conforme documentado, é o acesso externo, do lado do servidor. As queixas arquivadas relativas a usurpação de contas descrevem vítimas que não sabiam da existência da página até que uma chave tivesse sido registada na sua conta.\nA contradição da automatização\n\nO § 4.C da SSA dispõe o seguinte: «Não é permitido utilizar qualquer tipo de scripts, bots, macros ou outros sistemas não controlados por seres humanos («Automação») para interagir com os Conteúdos e Serviços no Steam, de forma alguma.» No entanto, os pontos finais da API Web (como CancelTradeOffer) não requerem qualquer interface de utilizador humana nem captcha e contornam totalmente o cliente Steam. A API foi concebida para a automatização entre servidores; a regra proíbe a automatização por parte dos utilizadores; a distinção entre as duas não é divulgada.\n\nUma posição do lado do servidor no fluxo comercial\n\nUma chave de API Web permite que um servidor de terceiros execute operações na conta sem o cliente Steam. No padrão de «hijack», esse servidor situa-se entre o titular da conta e o servidor de operações.\n\n→Não é apresentado qualquer ecrã de confirmação de transação para as ações da tecla.\n→Permite a recolha de dados em segundo plano (GetTradeOffers).\n→Cancela e reemite ofertas sem a intervenção do utilizador.\nValve criou a interface, proibiu a automatização por parte dos utilizadores nas suas regras e não publicou quaisquer critérios que definam quais as utilizações comerciais autorizadas.\nParte B — Regulamentos e histórico de aplicação · Secção 11\nForam exigidos dez dias. Dez anos para prestar contas.\nContexto e limites da fonte\n\nA 20 de julho de 2016, o conselheiro jurídico da Valve concedeu aos operadores de jogos de azar um prazo de 10 dias. Dez anos depois (à data do instantâneo do dossiê, 2026-09-21), pelo menos uma plataforma mencionada nas notícias da imprensa sobre esse aviso, a CSGOFast, continua em funcionamento com um servidor de autenticação num domínio separado. O texto é reconstruído abaixo a partir de notícias da imprensa de 21 de julho de 2016; a reconstrução não é uma digitalização. O registo de aplicação da lei a que a notificação se referia não foi publicado. A carta aberta à Comissão é Secção 2.\n\nLeia o aviso de julho de 2016, que se encontra ao lado das observações posteriores. O que ainda falta é um registo de cumprimento por operador.\n\nUma semana antes — 13 de julho de 2016, em público\n\nEm 13 de julho de 2016 arquivado 2026-09-21 ↗, Valve descreveu como os sites de jogos de azar utilizavam Steam: o OpenID para a identificação de contas e contas automatizadas para transações. Valve afirmou que a utilização desses mecanismos para gerir um negócio de jogos de azar violava a sua API e os acordos de utilizador. Tanto a descrição do mecanismo como a proibição constam da própria declaração datada de Valve. No 2026-09-21, os anfitriões de autenticação de domínios separados testados não apresentaram qualquer bloqueio do Filtro de Ligações, e o Valve não publicou qualquer registo de aplicação por operador.\n\nANEXO A / JULHO DE 2016RECONSTRUÇÃO DA COMPOSIÇÃO TIPOGRÁFICA\nVALVE CORPORATION\n\nBellevue, WA\n\nDATA:Julho de 2016 (noticiado pela imprensa a 21 de julho de 2016)\nDE:Karl Quackenbush, Diretor Jurídico\nRE:Ordem de cessação e abstenção — utilização comercial de contas Steam\nNOTA:Reconstrução do texto apresentado; não se trata de uma digitalização\n\n«Estamos cientes de que está a operar um dos sites de jogos de azar abaixo indicados. Está a utilizar Steam contas para exercer esta atividade. Nos termos do Steam Contrato de Assinante, os serviços Steam e Steam estão licenciados exclusivamente para utilização pessoal e não comercial.»\n\n«Deve cessar imediatamente e abster-se de continuar a utilizar as suas contas Steam para quaisquer fins comerciais. Caso não o faça, no prazo de dez (10) dias, «a Valve recorrerá a todas as medidas legais disponíveis, incluindo, sem limitação, o encerramento das suas contas.»\n\nReconstrução do dossiê · consultar o registo original\nKarl Quackenbush\nDiretor Jurídico, Valve Corp.\nÀ MARGEM / EDITORIAL\nDez dias.E depois?\n\nO prazo era específico. O acompanhamento por parte do público também deveria sê-lo.\n\nA posição publicada por Valve sobre «2016» ↗\nUma nota sobre o prazo +\nSÁTIRA / NÃO É UMA CORRESPONDÊNCIA DA VALVE\n\nCaro prazo,\n\nDeram-te dez dias. Por alguma razão, o calendário foi a única coisa que continuou a funcionar.\n\nPor favor, encaminhe qualquer resposta para o registo público.\n\nCronologiaJulho de 2016 – Setembro de 2026\nPrazo indicado no aviso:\n10 dias\nJulho de 2016\nTempo decorrido desde o aviso:\n3,715 dias\nContagem fixa desde 20 de julho de 2016 até ao instantâneo do dossiê de 21 de setembro de 2026; não se trata de um valor em tempo real\nRegisto de execução publicado:\nNenhum\nNão foi encontrada qualquer registo, por operador, de rescisões ou bloqueios\n\n◀ Dias 0–10 — o prazo, em proporçãoDia 3715 — a imagem instantânea ▶\n\n20 de julho de 2016Foi emitida uma notificação de dez diasDia 0\n17 de fevereiro de 2024Aplicam-se as obrigações previstas na DSADia 2,768\n25 de fevereiro de 2026Anunciada queixa do Procurador-Geral de Nova IorqueDia 3,507\n21 de setembro de 2026Visão geral do dossiêDia 3715\n\nDez anos depois, CSGOFast — mencionado nas notícias da imprensa relativas aos avisos de 2016 — está operacional: o site csgofast.com apresentou um bloqueio do Link Filter nos endereços 2026-09-19 e 2026-09-21, enquanto o seu host de autenticação steam-login.authtofast.com (registado 2026-06-30) não o fez.\n\nRegisto completo e datado das alterações de segurança do Valve: Cronologia da segurança → · O historial de Washington e o critério de aplicação: abaixo\n\nO que consta nos autos: O aviso de 2016 estabeleceu um prazo de 10 dias; a Valve já geria uma lista de domínios (o Link Filter) e recebia os nomes de anfitrião autorizados nas suas próprias solicitações OpenID; não foi publicado qualquer registo de aplicação por operador. Relatórios da comunidade descrevem uma ação de 2018 contra um mercado (SkinJar), mas esses relatórios não foram verificados e não são considerados neste contexto.\nCSGOFAST / A ROTA DE AUTENTICAÇÃO GUARDADA\nSiga o anfitrião de retorno indicado.\n\nOs links dos registos de percursos guardados csgofast.com para steam-login.authtofast.com. O nome de anfitrião específico é incluído no pedido OpenID Steam. Isso proporciona aos investigadores um endereço concreto para comparar com os registos de filtragem e aplicação de medidas do Valve.\n\nAnalise o percurso do CSGOFast e a sua origem ↗ · Comparar resultados guardados Steam Filtro de links ↗\n\nREGISTO PÚBLICO / WASHINGTON · 2016 → 2026\nDois prazos. Uma norma de aplicação sem resposta.\n20 de julho\nValve concede aos sites de jogos de azar um prazo de 10 dias\n\nA notificação do seu advogado advertia que a utilização comercial continuada das contas Steam poderia levar à rescisão do contrato.\n\n27 de setembro\nWashington pressiona Valve\n\nA Comissão de Jogos de Azar do estado exigiu provas das medidas tomadas para impedir as transferências de «skins» para fins de jogo e estabeleceu o prazo de 14 de outubro para a apresentação de uma resposta.\n\n17 de outubro\nValve rejeita a acusação\n\nValve respondeu após o prazo, contestou que facilitasse o jogo, afirmou ter desativado as contas associadas e declarou que não pretendia desativar as transações e o OpenID para todos. Pelo menos uma plataforma mencionada nas notícias da imprensa sobre as notificações de julho (CSGOFast) continuava em funcionamento uma década depois. Ambos os factos só se podem verificar se o operador tiver substituído as contas desativadas; o registo que comprovaria isso ainda não foi publicado. A WSGC deveria solicitar à Valve que esclarecesse esta contradição.\n\n2026\nAs rotas observadas em setembro de 2026\n\nO registo de rotas indica 44 plataformas que se autenticam através de servidores de autenticação de domínios distintos, incluindo o CSGOFast, utilizando o OpenID e os mecanismos de transação Valve descritos em 2016. O registo de medidas coercivas que indicaria quais os operadores que foram bloqueados ainda não foi apresentado.\n\nINFORMAÇÃO DA PRÓPRIA COMISSÃO · 30 DE JANEIRO DE 2018\nDezoito meses após a resposta da Valve, a entidade reguladora continuava a considerá-lo uma intenção.\n\nAo informar a sua própria assembleia legislativa na audiência pública sobre o projeto de lei HB 2881, a Comissão descreveu a declaração de julho de 2016 nas suas próprias palavras: Valve \"anunciou a sua intenção de tomar medidas severas contra a utilização da sua plataforma para facilitar as apostas com skins.\" Nessa mesma página consta o impacto que esse anúncio teve nas previsões para o setor — «consequentemente,» a previsão para o mercado de apostas com skin em 2020 foi revista de $19.7 mil milhões para $670 milhões, uma redução de cerca de 97 por cento, apenas com base no anúncio. A previsão foi alterada. O registo de fiscalização por operador que justificaria essa medida ainda não foi publicado.\n\nOs dados de mercado são estimativas da Narus Advisors / Eilers & Krejcik Gaming reproduzidas no documento informativo da Comissão, não constituindo conclusões da própria Comissão; o mesmo documento estima que as apostas com «skins» em 2016 ascenderam a cerca de $5 mil milhões, dos quais aproximadamente $3 mil milhões em sites do tipo casino. Recuperado em 2026-09-22, SHA-256 c507c9025f93da0aadaf395c4d8882f25973211c318ee8e9b6f18a5b3755e050.\n\nA posição pública de Valve em 2016 e a infraestrutura atualmente observável podem ser comparadas. A questão é saber se as medidas de fiscalização atingiram as contas e as rotas utilizadas pelos operadores proibidos. Um prazo de pré-aviso de dez dias não constitui prova de que o pré-aviso tenha sido notificado a todos os operadores nele mencionados. A ação da OPSkins de 2018 é a única intervenção documentada contra um operador identificado; tendo em conta que foram verificadas 189 plataformas e que não foram publicados registos por operador, uma única ação documentada não demonstra um padrão de aplicação da lei.\n\nAviso de 2016 da Comissão de Jogos de Azar de Washington ↗ arquivado 2026-05-20 ↗ · Resposta de Valve de 17 de outubro de 2016 (cópia do documento) ↗ · Sessão informativa do WSGC à Assembleia Legislativa, 30 de janeiro de 2018 (cópia local, 4 pp.) ↗ · o mesmo ficheiro em wsgc.wa.gov ↗ · registo de recuperação e hash ↗ · A ação do Valve no OPSkins de 2018 ↗ arquivado 2026-03-07 ↗ · Auditoria à rota atual ↗\n\nAuditoria Forense Longitudinal · Alvos da ordem de cessação e desistência de 2016\nA Década do Aviso Prévio de 10 Dias: Auditoria Forense de Sobrevivência dos 23 Locais Identificados\n\nNos dias 19 e 20 de julho de 2016, Valve o Conselheiro Geral Karl Quackenbush emitiu notificações formais de cessação e abstenção a 23 plataformas de jogos de azar com «skins», ordenando-lhes que cessassem a utilização comercial de Steam contas no âmbito de 10 dias sob ameaça de encerramento da conta e de ação judicial. Mais de 3,700 dias depois, uma auditoria empírica revela o verdadeiro padrão de aplicação das medidas: vários operadores nunca cessaram as suas atividades, outros continuaram a operar até seis anos após o prazo, e o ecossistema multimilionário continuou a tirar partido da arquitetura OpenID da Valve.\n\n5+ AO VIVO\nDefinitivamente em funcionamento em 2026 (CSGOBig, CSGO500, CSGOFast, etc.)\n6 ANOS\nPeríodo mais longo entre o aviso e o encerramento (CSGOatse ativo até 2022)\n$5.01B\nVolume de apostas em «skin» em 2016 (Narus / Eilers & Krejcik)\nMais de 200\nSites de apostas online em pleno funcionamento no auge do mercado\nOs Titãs Sobreviventes · Plano Financeiro e de Tráfego para 2024–2026\nDesde avisos com 10 dias de antecedência até conglomerados offshore: o volume de negócios de vários mil milhões de dólares\n\nEm vez de eliminar as apostas com skin, os avisos de Valve de 2016 catalisaram uma evolução do setor. Os operadores que sobreviveram reestruturaram-se como entidades empresariais offshore (Curaçao, Belize, Chipre), foram pioneiros no comércio Peer-to-Peer (P2P) para contornar as proibições de bots e, atualmente, processam mais de 10 milhões de visitas mensais ao site e milhares de milhões de dólares em volume anual de apostas ao mesmo tempo que se continua a autenticar através de Steam:\n\nPlataforma / Domínio\tAviso de julho de 2016\tResultado da execução e situação de sobrevivência\tVerificação registada / Links principais\nCSGOBig\ncsgobig.com\tAviso com 10 dias de antecedência (julho de 2016)\tAINDA VIVO EM 2026\nTemporariamente suspenso, relançado; autenticação através de letmeinbig.com e csgobiglogin.com\tX: @csgobig ↗ · FB: csgobigofficial ↗\nCSGO500\ncsgo500.com / 500.casino\tAviso com 10 dias de antecedência (julho de 2016)\tAINDA VIVO EM 2026\nRebrandizado como 500 Casino (licença de Curaçao n.º 8048/JAZ2014-037), com um volume de negócios mensal de vários milhões\tPlataforma ao vivo (500.casino) ↗\nCSGOFast\ncsgofast.com\tAviso com 10 dias de antecedência (julho de 2016)\tAINDA VIVO EM 2026\nA operar ativamente a roleta, o «crash» e o jackpot através do site steam-login.authtofast.com\tAuditoria de Autenticação de Dossiers ↗\nCSGOLounge / Dota2Lounge\ncsgolounge.com / dota2lounge.com\tAviso com 10 dias de antecedência (julho de 2016)\tAINDA VIVO EM 2026\nFocou-se nas apostas em moedas de e-sports e em criptomoedas; manteve o funcionamento contínuo\tPlataforma ao vivo ↗\nCSGOCasino\ncsgocasino.net / csgocasino.gg\tAviso com 10 dias de antecedência (julho de 2016)\tLIVE VIA SUCCESSOR (2026)\nO domínio foi redirecionado; o portal sucessor ativo funciona em csgocasino.gg\tDomínio sucessor ↗\nCSGOatse\ncsgoatse.com\tAviso com 10 dias de antecedência (julho de 2016)\tSOBREVIVEU 6 ANOS (EM ATIVIDADE ATÉ 2022)\nAs operações de jogo continuaram a funcionar em pleno durante seis anos, após o ultimato de 10 dias de Valve\tX: @CSGOatsecom (Ativo até 2022) ↗\nCSGOSweep\ncsgosweep.com\tAviso com 10 dias de antecedência (julho de 2016)\tSOBREVIVEU ATÉ DEZEMBRO DE 2017\nManteve-se em funcionamento ao público durante 17 meses após o prazo\tX: Situação do CSGOSweep – dezembro de 2017 ↗\nCSGOWild\ncsgowild.com\tAviso com 10 dias de antecedência (julho de 2016)\tSOBREVIVEU ATÉ DEZEMBRO DE 2017\nPromovido por influenciadores de renome; esteve em funcionamento durante 1,5 anos após a notificação de cessação e abstenção, antes da migração para as criptomoedas\tX: @Wild (Ativo em dezembro de 2017) ↗\nCSGOPot\ncsgopot.com\tAviso com 10 dias de antecedência (julho de 2016)\tSOBREVIVEU ATÉ SETEMBRO DE 2017\nOperou apostas com jackpots de valor elevado 14 meses após a notificação\tX: @csgopot (Ativo em setembro de 2017) ↗\nCSGODiamonds\ncsgodiamonds.com\tAviso com 10 dias de antecedência (julho de 2016)\tSOBREVIVEU ATÉ MEADOS DE 2017\nContinuou até 2017, apesar de se ter admitido a manipulação de resultados a favor de streamers patrocinados\tX: @csgodiamondscom (2017) ↗\nCSGOLotto\ncsgolotto.com\tAviso com 10 dias de antecedência (julho de 2016)\tENCERRADO EM JULHO DE 2016\nEncerrou a atividade na sequência de um escândalo público; alvo de uma ordem de consentimento da FTC federal\tAcordo de Consentimento da FTC (Processo n.º C-4632) ↗\nCSGODouble\ncsgodouble.com\tAviso com 10 dias de antecedência (julho de 2016)\tENCERRADO EM JULHO DE 2016\nEncerramento voluntário imediatamente após a publicação da notificação de cessação e desistência\tX: @CSGODouble (Encerrado em julho de 2016) ↗\nCSGOMassive\ncsgomassive.com\tAviso com 10 dias de antecedência (julho de 2016)\tENCERRADO EM 2016\nCessou as suas atividades ao público no final de 2016\tX: @csgo_massive ↗\nCSGOStrong\ncsgostrong.com\tAviso com 10 dias de antecedência (julho de 2016)\tENCERRADO EM 2016\nCessou a sua atividade pública em 2016\tFB: csgostrongfree ↗\nSkins2\nskins2.com\tAviso com 10 dias de antecedência (julho de 2016)\tENCERRADO EM 2016\nCessou a sua atividade pública em 2016\tFB: CSNCOM ↗\n\nPlataforma\tTráfego mensal (visitas)\tVolume de negócios estimado / Volume\tEntidade jurídica e jurisdição\tPrincipais medidas regulatórias e modelo\nCSGOEmpire\ncsgoempire.com\t2,3 milhões — 9,0 milhões / mês\nDuração média de 6+ minutos; 80% direto\t$1.5B — $2.5B Volume de negócios anual\n>1,000,000 transações de skins P2P por mês; $6.4M volume de ordens ativas e líquidas\tMoonrail Limited B.V. (Curaçao n.º 148182)\nPagamentos: JHOLT LTD (Chipre); Fundador: «Monarch» (Ossi Ketola)\tPioneira no comércio P2P de artigos sem comissões; licenciada em Curaçao sob a licença OGL/2024/1183/0869\nCSGORoll\ncsgoroll.com\t2,74 milhões — 3,5 milhões / mês\nDuração média de 9m 23s; taxa de rejeição de 16%\t$1.0B — $2.0B Volume de negócios anual\nReceita anual da empresa estimada entre $100M e $200M, proveniente da vantagem da casa\tFeral Holdings Limited\nCom sede na Cidade de Belize, em Belize (N.º de registo 171519)\tProibido pela ACMA australiana (maio de 2023); patrocinou a equipa de nível 1 G2 Esports, que contava com jogadores menores de idade\n500 Casino (CSGO500)\n500.casino / csgo500.com\t220 mil — 425 mil / mês\n~105 mil visitantes únicos por mês\t$100k / semana ($5.2M/ano) em Royales\nRequisito de aposta para grandes apostadores: $400 de aposta por $1 de rakeback\tPerfect Storm B.V. (Curaçao n.º 150536)\nLicença da Comissão de Controlo do Jogo de Curaçao n.º OGL/2024/1354/0882\tProibida pela Spelinspektionen sueca (novembro de 2023) por se dirigir a jogadores suecos sem licença\nCSGOBig\ncsgobig.com\t~169,600 / mês\nDuração média: 19m 12s; Primárias nos EUA\tVolume anual de vários milhões\nCaixas misteriosas, roleta e batalhas de caixas\tFunciona através de encaminhamento por proxy auxiliar\nletmeinbig.com (reg. 2023) e csgobiglogin.com\tO Target da C&D de julho de 2016 foi relançado com uma arquitetura de autenticação por proxy\nCSGOFast\ncsgofast.com\t~150 mil — 250 mil / mês\nPúblico global multilingue\tVolume anual de vários milhões\nRoleta de alta velocidade e jogos «crash»\tEntidades operacionais offshore\nRotas Steam autenticação através de steam-login.authtofast.com\tAlvo da C&D de julho de 2016; nunca interrompeu as suas atividades; em funcionamento em 2026\nCSGOPolygon\ncsgopolygon.com / plg.bet\t~300 mil — 500 mil / mês\nO domínio da CEI e da Europa de Leste\tVolume anual de vários milhões\nCriptomoedas e roleta de skins, apostas em jogos\tMeta da segunda fase (outubro de 2016)\nFocou-se nas criptomoedas com o domínio espelho plg.bet\tSobreviveu a uma década inteira; continua a liquidar skins através de APIs de terceiros\nA Segunda Onda: Por que é que a notificação de cessação e abstenção da Valve visou mais de 43 sites no total\n\nEm 17 de outubro de 2016, o representante legal da Valve informou formalmente à Comissão de Jogos de Azar do Estado de Washington que, na sequência das 23 notificações iniciais de 19 de julho, a Valve tinha enviado cartas de cessação e desistência a mais de 20 sites adicionais de apostas com skins (elevando o total oficial para mais de 43). Esta segunda vaga tornou-se necessária porque a lista inicial omitiu, inexplicavelmente, os maiores e mais famosos centros de jogo do mundo:\n\nCSGOJackpot.com: A empresa pioneira no ramo dos «jackpots» de pele, que movimentou centenas de milhões antes de encerrar as portas sob a ameaça de uma acusação federal.\nCSGOShuffle.com: O site que esteve no centro do escândalo de streaming de julho de 2016, onde o streamer da Twitch PhantomL0rd detinha secretamente 33% da empresa e foi desmascarado por manipular as probabilidades com fundos da própria empresa.\nO macroecossistema (mais de 200 operadores): De acordo com um estudo do setor realizado pela Narus Advisors e pela Eilers & Krejcik Gaming, em 2016 estavam em funcionamento mais de 200 sites distintos de apostas com «skins», que geraram $5.01 mil milhões em volume de apostas proveniente de 3,03 milhões de jogadores ativos. As 43 cartas da Valve abrangeram menos de 20% do mercado ativo.\nInvestigações oficiais do Governo e das entidades reguladoras sobre o «Steam Skin Gambling»\n\nO fenómeno do jogo «skin gambling» está documentado em várias investigações oficiais, ações de fiscalização e documentos de posição do governo:\n\n1. Comissão de Jogos de Azar do Estado de Washington (WSGC) (2016–2018)\n\nEmitida uma notificação formal de cessação e abstenção em 5 de outubro de 2016; publicado um resumo legislativo em 30 de janeiro de 2018, no qual se documenta que as «skins» são equivalentes a dinheiro e se reporta o volume de apostas com «skins» de $5.0B.\n\nRelatório Legislativo do WSGC em PDF (Cópia local) ↗\n2. Comissão Federal do Comércio dos EUA (FTC) (setembro de 2017, Processo n.º C-4632)\n\nPrimeira ação regulatória federal contra os proprietários da CSGOLotto, Trevor Martin e Thomas Cassell, por práticas enganosas e controlo não divulgado da plataforma no âmbito das apostas com «skins».\n\nDecisão e Ordem de Consentimento da FTC ↗\n3. Documento de posição da Comissão de Jogos do Reino Unido (UKGC) e auditorias relativas aos jovens\n\nAs skins dos jogos foram formalmente classificadas como «dinheiro ou equivalente a dinheiro» ao abrigo da Lei do Jogo de 2005. Inquéritos posteriores revelaram que mais de 11% das crianças com idades compreendidas entre os 11 e os 16 anos tinham apostado skins em videojogos.\n\nRepositório de Investigação da UKGC ↗\n4. Inquérito do Senado australiano sobre o Ambiente e as Comunicações (2018)\n\nRelatório do Parlamento Federal sobre «Microtransações em jogos para itens aleatórios», avaliando a mecânica das caixas de saque do Valve, os levantamentos de fundos no mercado secundário e a evasão regulamentar.\n\nInquérito do Parlamento da Austrália ↗\nA procura pendente\n\nPublicar o registo das medidas aplicadas: quais as contas de jogo e os bots que foram desativados, quais os servidores de retorno que foram restringidos e quais os serviços comerciais que receberam autorização. Uma proibição pública e um aviso na página inicial não comprovam que a operação subjacente tenha sido interrompida.\n\nParte B — Regulamentos e registo de aplicação · Secção 12\nO nome do anfitrião já consta no pedido.\nLimites de contexto e de fonte\n\nO Valve já mantém uma lista de domínios (o «Link Filter») e já recebe o nome de host de autenticação em cada pedido OpenID. O pseudocódigo abaixo mostra a estrutura lógica da ligação entre os dois. Não há provas públicas de que o Valve o faça.\n\nValve já mantém uma lista de domínios bloqueados. Valve já recebe o host de início de sessão em cada pedido OpenID. Não é preciso construir nada — basta unir as duas partes. Trata-se de uma pesquisa de nome de anfitrião numa lista que o Valve mantém por si próprio. O pseudocódigo abaixo é apenas uma ilustração, não sendo a implementação do Valve.\n\nforensic_autoban.py\n# PSEUDOCÓDIGO ILUSTRATIVO — Valve.block_domain() e flag_session_as_mitm() não são chamadas reais à API. Isto demonstra a estrutura lógica de uma medida de mitigação que o Valve poderia implementar contra domínios de autenticação por proxy, e não o funcionamento interno real do Valve.\n# Ilustração: o formato lógico de uma verificação da solicitação OpenID recebida\ndef audit_openid_request(pedido):\nblocked_origins = base de dados.obter_plataformas_na_lista_negra()\nproxy_domain = request.params.obter('openid.realm')\ntarget_redirect = request.params.obter('openid.return_to')\n\n# Lógica: Se o proxy redirecionar para um site bloqueado, bloquear o proxy.\npara site em origens_bloqueadas:\nse site em target_redirect:\nValve.bloquear_domínio(proxy_domain)\nValve.flag_session_as_mitm(request.session)\n# Resultado: o pedido de início de sessão para esse anfitrião foi recusado\n\nObservação:\nQuando um domínio principal já se encontra no Filtro de Links (por exemplo, howl.gg, bloqueado 2026-09-18/19/21) e o seu anfitrião de autenticação (howl.uno) aparece no pedido OpenID proveniente do botão de início de sessão desse site, a associação é observável para Valve a partir dos seus próprios dados de pedido. A verificação pode ser automatizada; a sua execução, não.\nPrecedentes documentados e relatados\n\nA Valve já interveio contra um operador terceiro pelo menos uma vez, segundo consta dos registos: em 2018, revogou o acesso da OPSkins ao sistema ExpressTrade (Anúncio de Valve ↗ arquivado 2026-03-07 ↗). Relatórios da comunidade de 2018 também descrevem uma plataforma de comércio (SkinJar) que perdeu o acesso; esses relatórios não foram verificados e o mecanismo é deduzido a partir do resultado, e não de um processo divulgado.\n\nO que o precedente estabelece:\n\nValve pode bloquear o acesso de um operador terceiro sempre que assim o decidir. O CSGOFast, mencionado em notícias da imprensa relativas aos avisos de julho de 2016, estava a operar no 2026-09-21 com um host de autenticação registado no 2026-06-30 que não apresentava qualquer bloqueio do Link Filter. Não há qualquer critério publicado que explique por que razão um operador foi bloqueado e outros não.\n\nO que a data de registo indica e o que não indica\n\nA data de registo de um host de autenticação constitui o limite mínimo para a data em que o host poderia ter aparecido pela primeira vez numa solicitação OpenID; não implica, contudo, uma utilização contínua. sc-auth.net, por exemplo, foi registado em 2019-04-02 (RDAP) e foi observado no fluxo de início de sessão Steam do Skin.Club em setembro de 2026; o que aconteceu entre essas duas datas não consta dos registos públicos.\n\nAuditoria comparativa: normas de conformidade da API\nDimensão da aplicação da lei\tRegras da API do GitHub\tSteam API Web (Valve)\n1. Neutralidade em matéria de conformidade\tRegras publicadas e uniformes. Os limites de taxa documentados (por exemplo, 5,000 chamadas/hora para utilizadores autenticados, 15,000/hora para organizações do GitHub Enterprise Cloud) e as políticas de utilização aceitável publicadas aplicam-se a todas as contas.\tNão existem critérios publicados. As contas individuais são encerradas ao abrigo das cláusulas relativas à automatização e à utilização comercial (queixas arquivadas), embora não tenha sido publicado qualquer registo de medidas coercivas por operador no que diz respeito às plataformas comerciais.\n2. Abuso do OpenID / Proxy de Autenticação\tAs políticas publicadas pelo GitHub permitem que as aplicações e os tokens OAuth sejam suspensos ou revogados em caso de abuso, e a sua documentação descreve a revogação automática de tokens expostos (resumo da documentação do GitHub elaborado pelos autores).\tOs servidores de autenticação de domínios separados observados nos fluxos OpenID Steam (por exemplo, rbsnin.com, howl.uno, sc-auth.net) não apresentaram qualquer bloqueio do Filtro de Links no 2026-09-21, ao passo que os seus domínios principais sim.\n3. Monetização do abuso\tO GitHub não cobra qualquer comissão sobre transações realizadas por meio de automação de terceiros; o seu modelo de receitas baseia-se nas subscrições e nas listagens no mercado.\tO Valve vende as chaves das caixas que dão origem aos itens, e o Mercado da Comunidade cobra uma taxa combinada de cerca de 15% sobre as vendas concluídas no próprio Mercado. Não se estima aqui qualquer valor relativo às receitas atribuíveis a plataformas de terceiros.\n4. Duração dos ciclos de evasão\tOs IDs de clientes OAuth suspensos deixam de funcionar em toda a plataforma no momento da suspensão; a documentação não indica um prazo para a ação e não se pressupõe qualquer prazo neste contexto.\tOs servidores de autenticação de domínios separados com datas de registo entre 2011 e setembro de 2026 não apresentaram qualquer bloqueio do Filtro de Links nas verificações de 2026-09-19 e 2026-09-21. A data de registo constitui um limite inferior para a utilização possível, não sendo prova de utilização contínua.\nFontes: Coluna do GitHub — Documentação publicada pelo GitHub sobre limites de taxa da API e políticas da plataforma (resumo dos autores, não citado) · Coluna Steam — Verificações do filtro de ligações em 2026-09-19 e 2026-09-21 (linkfilter-recheck-2026-09-21.json), registo RDAP (registo-de-domínios.json) e as reclamações de apoio ao cliente arquivadas (arquivo de provas).\nParte B — Regulamentos e histórico de aplicação · Artigo 13.º\nA diferença de preço «off-Steam»\n\nO artigo encontra-se num inventário Steam; a venda realiza-se noutro local. Uma AWP Dragon Lore nova de fábrica tinha 62 ofertas ativas no CSFloat; o preço mais baixo pedido $10,623.95. O próprio mercado de Steam não pode apresentar um preço de venda superior a aproximadamente $1,800. Para vender pelo preço mais elevado observado, um proprietário precisa de um comprador ou de uma plataforma de mercado fora de Steam. O artigo e a sua transferência continuam a depender de Steam.\n\nWhat this means — the Community Market listing ceiling\n\nSteam’s own market refuses a listing above roughly $1,800. A seller may ask less, never more. Items whose market price sits above that line therefore cannot be sold at that price on Steam at all — which is the mechanism that moves those sales to third-party venues while the item itself never leaves Valve’s inventory system.\n\nSection 13 — the off-Steam price gap →\n\nContexto e limites da fonte\n\nNesta secção, aparecem três categorias diferentes, que não são intercambiáveis. 245 é o número de categorias de nomes de artigos CS2 cuja oferta ativa mais barata excedeu $1,800 apenas no CSFloat, a 20 de setembro de 2026. 241 é esse mesmo conjunto, excluindo as quatro categorias fixadas no limite superior $100,000 do CSFloat, que é o painel com base no qual se calcula o limite inferior $13.63M. 248 trata-se de um panorama diferente: categorias cujos preços ultrapassavam o limite máximo em duas ou mais das cinco plataformas de negociação, a 23 de setembro de 2026. As plataformas de negociação sobrepõem-se, pelo que os valores de diferentes plataformas nunca devem ser somados. Todos os valores aqui apresentados correspondem a preços de venda solicitados, não a vendas concluídas, e nenhum deles representa receitas, volume de negócios ou lucro — nem para o Valve nem para qualquer outra entidade. Os valores apresentados pelo PriceEmpire são estimativas arredondadas publicadas por esse site, e o seu cartão Steam abrange itens de outros Steam jogos, pelo que os âmbitos da comparação não são idênticos.\n\nUm artigo. Dois sistemas de preços.ACOMPANHE O REGISTO\nEtapa 3 / 3\n\nNesse caso, o vendedor precisa de um local ou comprador fora do Steam. O artigo continua a depender do inventário e do sistema de transferência do Steam.\n\nSTEAMSobre $1,800Limite máximo de listagens no Mercado Comunitário publicado\nCATÁLOGO GUARDADO$10,623.95AWP Dragon Lore nova de fábrica – pedir preço\nA DEPENDÊNCIAAinda é um artigo SteamO inventário e a transferência permanecem em Steam\n01 / ARTIGOValve inventário do jogoItem do CS2 ou do Dota 2 guardado em Steam\n02 / TETOSobre $1,800 em SteamPreço máximo por um anúncio no Market\n03 / PERGUNTA EXTERNA$10,623.95 para «Dragon Lore»A oferta mais barata de CSFloat no instantâneo datado\n04 / ENTREGASteam permanece na cadeiaA titularidade e a transferência de artigos dependem desse sistema\nARQUITETURA DO MERCADO · INSTANTÂNEO DATADO, 20 SETEMBRO 2026\nA diferença de preços é mensurável.\n\nContámos as categorias de nomes de artigos cuja oferta ativa mais barata se situava estritamente acima de $1,800. CSFloat e Skinport são instantâneos separados com inventários CS2 que se sobrepõem; as respetivas contagens não podem ser somadas. As ofertas externas mostram onde são publicados preços de venda mais elevados, enquanto Steam continua a controlar a propriedade e a transferência dos artigos.\n\n245CATEGORIAS DO CS2 · CSFLOAT\n166CATEGORIAS CS2 · SKINPORT\n3DOTA2CATEGORIAS · SKINPORT\n$10,623.95PERGUNTA SOBRE O PISO DA TRADIÇÃO DOS DRAGÕES\n\nDragon Lore: 62 apresenta CSFloat ofertas ativas na categoria «Factory New»; o preço mínimo apresentado é um pedido de venda, não uma venda confirmada. Steam permite que o artigo seja anunciado por um valor inferior, mas não permite publicar o preço de venda mais elevado observado. A declaração da Valve, disponível em 2016, confirma que a empresa tem conhecimento de que operadores de jogos de azar utilizam o OpenID e a infraestrutura comercial de Steam. A eventual violação das regras da Valve por parte de um determinado mercado de terceiros deve ser determinada separadamente.\n\nConsultar o registo completo →CSFloat JSON ↗Skinport JSON ↗Declaração de Valve sobre «2016» ↗\nAPI CSFLOAT DIRETA / INSTANTÂNEO DATADO$13.63M\n\nValor mínimo agregado solicitado em 241 categorias de artigos e 3,395 ofertas ativas. Calculado como o preço de venda mais baixo de cada categoria multiplicado pelo número de ofertas correspondentes. Quatro categorias fixadas no limite máximo de $100,000 do CSFloat são excluídas deste painel conservador.\n\nO que o valor em dólares revela\n\nEstas ofertas representam, pelo menos, $13,631,888.25 nos preços de venda anunciados para este subconjunto limitado do CSFloat. Ao incluir as quatro categorias com preço máximo, obtém-se $14,231,888.25. Isto é um limite mínimo para pedidos ativos, e não as vendas concluídas, o volume de negócios, o lucro ou todo o mercado do CS2.\n\nRecalcular a partir do instantâneo CSFloat de 245 linhas ↗\nPRICEEMPIRE / VALOR DE COTAÇÃOSteam: n.º 15 de 39\nMuitos locais indicam um valor em dólares superior a Steam.\nUUSkins\n$133.8M\nYouPin898\n$127.5M\nBuff.163\n$104M\nMoon.Market\n$100.3M\nWhite.Market\n$89.6M\nBuff.Market\n$86.7M\nSteam\n$31M\n\nOs seis maiores valores apresentados e Steam. O PriceEmpire arredonda estes valores; Steam mostra $31M. Catorze locais listados estão à frente deste, de acordo com os valores em dólares apresentados.\n\nPRICEEMPIRE / NÚMERO DE OFERTASSteam: n.º 1 de 39\nSteam continua a liderar em número de ofertas.\nSteam\n32,2 milhões\nYouPin898\n5,9 milhões\nC5Game\n4,6 milhões\nHaloSkins\n4,4 milhões\nSkinport\n3,8 milhões\n\nSteam mostra 32,2 milhões ofertas. O número de ofertas e o valor total pedido respondem a questões diferentes; muitos anúncios com preços baixos podem dominar o número total.\n\nFonte: Comparação pública do PriceEmpire ↗ arquivado 2026-09-21 ↗, captado às 2026-09-20 19:03 UTC; extração datada de 39 linhas ↗. Os números apresentados são estimativas arredondadas e o inventário pode sobrepor-se entre locais. A ficha do Steam também descreve itens de outros jogos Steam, pelo que os âmbitos não são idênticos. Os valores indicados referem-se aos preços de venda, e não às vendas nem às receitas.\n42\nOUTRA FONTE / STEAMANALYST\nO ecossistema comercial está à vista de todos.\n\nDiretório do mercado da SteamAnalyst arquivado 2026-07-19 ↗ apresenta uma lista de 42 plataformas de comércio do CS2 de terceiros, juntamente com o Steam, com dados recentes sobre preços para 32 das 43 entradas. O PriceEmpire lista 39 plataformas de acordo com os seus próprios critérios de inclusão. Empresas identificadas, ofertas públicas, preços visíveis: esta economia está aberta à inspeção.\n\nO LIMITE É O MECANISMO: A PROMOÇÃO PERDE FORÇA, MAS O ARTIGO NÃO.\n\nEm cinco mercados abrangidos por uma única imagem captada ao abrigo de uma licença, 248 categorias de artigos CS2 têm preços fixados de forma independente acima do limite máximo de listagem de aproximadamente $1,800 do Steam por duas ou mais dessas categorias — e todas elas estão ausentes do Steam. O mesmo instantâneo agrupou todo o catálogo por preço: o mercado de Valve tem 95.3% das categorias de artigos abaixo do seu limite máximo e 1.9% das que estão acima dele. A redução não reflete uma queda na procura; corresponde exatamente à regra publicada. Vender a esses preços requer um comprador externo ou uma plataforma de comércio, enquanto o Steam continua a controlar o inventário e a transferência — a transação sai do balcão de pagamento do Valve e a entrega permanece na infraestrutura do Valve.\n\nSteam Perguntas frequentes sobre o mercado ↗arquivado 2026-09-21 ↗Steam Contrato de Subscrição ↗arquivado 2026-09-21 ↗Conjunto de dados do atlas de cinco mercados ↗Manifesto de proveniência ↗Instantâneo anterior do CSFloat ↗Visão geral do Skinport ↗PriceEmpire ↗arquivado 2026-09-21 ↗SteamAnalyst ↗arquivado 2026-07-19 ↗Registo de diferenças de preços ↗Atlas da escala de preços ↗\n\nParte C — Quadros jurídicos\nParte C — Quadros jurídicos · Secção 14 · Acesso do pessoal\nQuem pode reiniciar as medidas de segurança?\nContexto e limites da fonte\n\nA segurança da conta depende também das pessoas que podem recuperar uma conta, consultar registos privados ou redefinir as suas medidas de segurança. A investigação deve acompanhar essas ações privilegiadas com o mesmo rigor com que acompanha o uso indevido da API.\n\nA recuperação de contas confere a um agente de apoio o poder de retirar uma conta ao seu titular. Valve confirmou por escrito, por duas vezes — em fevereiro de 2023 e em novembro de 2025 — que este poder foi utilizado para atribuir contas às pessoas erradas. Com um intervalo de trinta e três meses, através do mesmo canal. Abaixo: o valor desse acesso, seis casos comprovados e o registo Valve que se aplica a cada um deles e que não foi divulgado a ninguém.\n\nTestemunho preservado / 9 de maio de 2025\nUm código de recuperação que desativou a segurança da conta e uma perda declarada de $10,000\n\nUm utilizador no arquivo de apoio recolhido relata que o Steam Apoio redefiniu a palavra-passe e desativou a proteção da conta depois de outra pessoa ter enviado um pedido de recuperação. O autor afirma que a conta estava inativa há anos, continha itens desde 2016–2017 e tinha Steam Guard, um telemóvel associado e códigos de recuperação guardados.\n\n\"Steam O serviço de apoio ao cliente concedeu acesso à minha conta a outra pessoa.\"\n\nAlegação na primeira pessoa, registada em steam_support_tickets_MEGA.json, registo n.º 110. Ler a publicação completa capturada ↗\n\nIsto não se trata de azar de um único utilizador. A mesma via — um pedido de ajuda que transfere uma conta para quem fornecer os dados mais antigos — é o procedimento documentado para todos os casos constantes do registo abaixo, e Valve já o confirmou por escrito por duas vezes.\n\nO proprietário não tem como ganhar essa discussão. A recuperação pede a primeira chave de CD, o primeiro e-mail, o primeiro cartão, o primeiro número de telefone. Esses dados encontram-se na base de dados do Valve, e o acesso da equipa de apoio consulta-os — segundo consta, remontando a quinze anos. Uma pessoa que tenha uma cópia do seu ficheiro irá sempre revelar mais do seu histórico do que você próprio. Os alvos foram escolhidos de forma a corresponderem aos critérios: inativos há anos, de elevado valor e, muitas vezes, comprados em segunda mão, pelo que o detentor nunca soube a chave original. Posteriormente, as contas foram completamente eliminadas, interrompendo o rasto do histórico de itens que a comunidade utiliza para localizar uma skin — uma eliminação que um utilizador comum não pode efetuar sem o período de espera padrão.\n\nPrivilégio mínimo / OWASP A01\n\nOs privilégios de recuperação devem ser limitados à tarefa em questão, sujeitos a revisão independente e registados. Verifique quem pode redefinir credenciais, remover Steam Guard, consultar registos de faturação ou exportar dados da conta. Orientações da OWASP sobre controlo de acesso ↗ arquivado 2026-09-20 ↗\n\nAcesso a um amplo apoioRisco relacionado com o âmbito de acesso\nPara além do inventário.\n\nSe o acesso amplo for utilizado de forma abusiva, a telemetria privada pode tornar-se uma ferramenta para a criação de perfis, o phishing direcionado e a vigilância. As potenciais vítimas incluem utilizadores comuns, militares, figuras públicas e as suas famílias. Trata-se de um modelo de ameaça; as permissões exatas requerem registos de controlo de acesso.\n\n01 Histórico e localização do endereço IP\nOs registos de IP podem revelar o histórico de rede e a localização aproximada. Por si só, não permitem determinar movimentos físicos precisos.\n02 Identificação de dispositivos\nOs identificadores de dispositivos, quando recolhidos e acessíveis, podem associar sessões e contas.\n03 Telemetria de atividade\nOs registos de data e hora de início de sessão e os registos de sessão podem revelar hábitos, incluindo atividades que não são visíveis num perfil público.\n04 Comunicações e contactos\nO acesso a mensagens guardadas ou a informações de contacto aumentaria as possibilidades de criação de perfis e de engenharia social.\n05 Revelação da identidade\nOs registos originais de e-mail, telefone e pagamentos podem associar uma conta pseudónima a uma pessoa.\n06 Revenda de dados e responsabilização\nAs listas de alvos exportadas podem servir de base para esquemas fraudulentos direcionados. Identifique o autor, o local de acesso, os destinatários e as transferências; o local, por si só, não determina nem o acesso nem a imunidade jurídica.\n\nValve descreve o registo de endereços IP, as informações sobre os dispositivos, os registos de pagamentos e os prestadores de serviços de assistência externos na sua Política de Privacidade, artigos 3.º e 5.º, n.º 2 arquivado 2026-09-21 ↗. A política autoriza o acesso de terceiros — a pista de auditoria que indicaria qual o contratante que acedeu a que categoria, quando e ao abrigo de que autorização não foi divulgada.\n\nSecção 14.1 · o registo · junho de 2022 → novembro de 2025 · todas as figuras com indicação da fonte\nValve abriu a porta duas vezes, com trinta e três meses de intervalo. A porta nunca se fechou.\n\nForam relatados seis casos em que as contas foram usurpadas através do próprio canal de pedidos de ajuda do Steam, ou através das credenciais que esse canal protege. Cada montante corresponde ao valor publicado pela fonte citada, e cada fonte é identificada. Dois dos seis casos foram resolvidos com a restituição total dos montantes. A diferença entre estes casos e os restantes não residia no que aconteceu — residia em quem estava a observar.\n\nValve, por escrito — fevereiro de 2023«Os itens em questão foram removidos da tua conta porque foram recebidos de uma conta que foi comprometida através de um pedido de assistência, pelo que a equipa do CS:GO assume a responsabilidade. Anulámos as trocas e removemos esses itens de todas as contas que os receberam.»Steam Resposta de apoio a um destinatário dos artigos da HFB, reproduzida por Dexerto, 21 de fevereiro de 2023 ↗ arquivado 2025-08-18 ↗\nValve, de novo por escrito — novembro de 2025 · 33 meses depois«Um técnico de apoio que tratou do pedido de ajuda não seguiu o nosso procedimento, o que fez com que a sua conta fosse restaurada para outra pessoa. Peço desculpa por este erro.»Steam Resposta do Suporte ao utilizador Hawkeye337, citada em Dexerto, 14 de novembro de 2025 ↗\n21 de junho de 2022\nHFB — o maior inventário do jogo$2,000,000+ · elevado para $3,000,000+ no acompanhamento de fevereiro de 2023\n\nSete «Dragon Lores» da AWP de coleção e o Karambit «Blue Gem» n.º 1; só essa faca está avaliada em cerca de $1.26 milhões. A conta estava inativa há três anos, mas o autenticador móvel continuava ativo; mesmo assim, o endereço de e-mail e a palavra-passe foram alterados através do processo de recuperação do apoio ao cliente.\n\nO dinheiro esgotou-se antes dos artigos. Segundo notícias $200,000+ Parte do produto da venda já tinha sido levantada através do market.csgo.com — uma plataforma de comércio que efetua pagamentos em dinheiro e criptomoedas. Ao anular uma transação, a skin é devolvida. O dinheiro que já tenha sido depositado não é devolvido.\n\nE a correção deixou de funcionar. Um comprador transferiu o seu «Souvenir Dragon Lore» para uma unidade de armazenamento no jogo. O script de reversão do Valve não conseguiu ver o interior do seu próprio contentor, pelo que emitiu uma nova cópia ao proprietário e deixou a cópia oculta tal como estava — o Valve duplicou um $130,000 artigo ao tentar anular um roubo. Foi detetado através da comparação dos IDs dos artigos e de denúncias da comunidade, tendo sido eliminado um mês depois, em julho de 2022. O comprador foi reembolsado pela BUFF, e não pela Valve. Uma correção de emergência tão precária como esta não é um mecanismo de controlo; é o que uma plataforma faz quando não tem controlo.\n\nDexerto, 21 de junho de 2022 ↗ arquivado 2022-07-02 ↗ · Kaspersky ↗ · valor do levantamento por Esportfire, 22 de junho de 2022 ↗ arquivado 2026-05-15 ↗, aí atribuído a várias fontes do Twitter · duplicação e eliminação de acordo com Esportsbetting, 14 de julho de 2022 ↗\n\nRestauradoAs transações foram revertidas. Os artigos foram retirados dos inventários das pessoas que os tinham comprado pelo preço total.\n14 de agosto de 2022\nCS.Money — os bots da própria plataforma$6,300,000 · 19,000+ skins · primeira estimativa $1.6M\n\nOs atacantes apoderaram-se dos ficheiros do autenticador móvel dos bots de negociação da plataforma e esvaziaram-nos, tendo depois enviado parte do saque a negociadores conhecidos para confundir as pistas. Investigadores da comunidade mapearam 55 contas de atacantes em poucas horas e publicou-os.\n\nO Valve não alterou nada. A razão apresentada foi que um site de terceiros se encontra fora do Steam — o mesmo Steam cujo inventário, API comercial e sistema de contas foram alvo do roubo de ponta a ponta.\n\nEsportfire, 14 de agosto de 2022 ↗ arquivado 2025-11-15 ↗\n\nRecusadoNão houve reversão. O prejuízo ficou a cargo da plataforma e dos seus utilizadores.\nRelatado\n21 de fevereiro de 2023\nQkss — a mesma porta, o mesmo ator$1,000,000+\n\nFoi comunicado que foi tratado da mesma forma que o HFB, pelo mesmo interveniente, através do mesmo pedido de assistência técnica. O HFB foi resolvido na totalidade oito meses antes. O Qkss não.\n\nUm caminho. Duas respostas. Nada no registo publicado distingue os dois casos, exceto a dimensão da audiência.\n\nDexerto, 21 de fevereiro de 2023 ↗ arquivado 2025-08-18 ↗\n\nRecusadoNão foi restaurado.\nRelatado\nFevereiro de 2023\nA própria operação com informação privilegiada — um ano dessa prática≈ $320,000 · refere-se a um período de cerca de um ano, não a uma avaliação de existências\n\nO acesso da equipa de apoio permitiu consultar o histórico da conta até 15 anos — a primeira chave do CD, o primeiro e-mail, o primeiro cartão. São exatamente essas as provas exigidas pelo processo de recuperação, e é por isso que quem detém a base de dados sai sempre a ganhar na discussão com quem detém a conta.\n\nO blogueiro Mzkshow revelou como o operador interno «Steam Help» e o seu colaborador «Alexander» tinham como alvo contas inativas que possuíam mais de $100k em skins. Uma M4A4 Howl roubada, com os holos «iBUYPOWER» e «Titan Katowice 2014», foi vendida por $35,000 e acabou por envolver Valerii «b1t» Vakhovskyi, da NAVI, que não tinha como saber. Após a intervenção de Valve, a empresa contratada despediu toda a sua equipa de apoio ao cliente, composta por Steam pessoas.\n\nVKPlay ↗ · Lis-Skins ↗ · Escorenews (RU) ↗ · Dexerto (EN) ↗\n\nSem registoValve nunca divulgou quantas contas foram afetadas nem informou as pessoas afetadas.\nRelatado\n2 de dezembro de 2024\n«Matvey» — após os despedimentos$13,000\n\nFoi concedida a recuperação a alguém que forneceu dados da conta que o próprio titular não conseguiu confirmar. Dois anos depois de a empresa contratada ter encerrado o seu serviço de apoio Steam, o mesmo procedimento produziu o mesmo resultado.\n\nPublicação arquivada, 2 de dezembro de 2024 ↗ arquivado 2025-08-05 ↗ · linhas de código-fonte e hashes ↓\n\nRecusadoNão foi restaurado.\n13 de novembro de 2025\nHawkeye337 (Mark Spurlock) — e a segunda confissão≈ $300,000–$500,000 · coleção completa de hologramas de Katowice 2014\n\nO agressor exigiu 1 bitcoin e começou a transferir a coleção para os Negevs para a destruir. Steam A resposta por escrito do Apoio ao Cliente corresponde à segunda admissão acima: um técnico tratou do pedido de ajuda, não seguiu o processo e passou a conta a outra pessoa.\n\nO que provocou a correção foi o feed. Poucas horas depois de as publicações com a etiqueta Valve terem sido publicadas no X, a conta foi recuperada e todos os autocolantes foram repostos. O Qkss não tinha esse público.\n\nSkin.club ↗ · Dexerto ↗ · Esportfire ↗ arquivado 2025-12-17 ↗\n\nRestauradoA notícia foi desmentida poucas horas depois de se ter tornado viral.\nO que o registo revela e que nenhum caso isolado revela.\n\nO percurso nunca foi encerrado. A primeira admissão data de fevereiro de 2023 e a segunda, de novembro de 2025 — com trinta e três meses de diferença, com o despedimento em massa da empresa contratada, um caso de recorrência documentado e uma violação da plataforma no valor de $6.3 milhões entretanto. Contando a partir do primeiro roubo registado neste livro-razão, o canal permaneceu aberto durante três anos e cinco meses. Independentemente do que tenha sido corrigido em 2023, o pedido de ajuda continuou a ser encaminhado para a pessoa errada em novembro de 2025 — segundo as próprias palavras de Valve.\n\nA restituição teve em conta a atenção, e não o dano. Restaurado: o maior inventário do jogo e o colecionador cujo tópico se tornou tendência. Recusado: $1,000,000, $6,300,000, $13,000. Valve nunca publicou a regra a que se aplica, porque uma regra publicada teria de explicar essas três.\n\nNinguém foi informado. Nem os utilizadores cujos históricos de conta foram extraídos da base de dados, nem uma autoridade de supervisão, nem o mercado que adquiriu os artigos de boa-fé e viu esses artigos serem-lhe retirados. Não há qualquer aviso de violação, nem relatório de incidente, nem contagem das contas afetadas — e os rendimentos que ficaram em dinheiro, através de plataformas de comércio que pagam em dinheiro e criptomoedas. Não é possível efetuar uma reversão de transação para seguir o dinheiro que sai de Steam.\n\nValve contém o registo de auditoria de suporte, o registo de tickets de recuperação e o registo de transações para cada linha acima. Nada disso foi apresentado. Pede a tua própria cópia →\n\nA questão do NDA\nA confidencialidade deve ser acompanhada de responsabilidade técnica.\n\nCompare os acordos de confidencialidade com as autorizações efetivas, os controlos de exportação, as aprovações de reinicialização e os registos de acesso. Uma resposta pré-definida não pode resolver uma alegação de que o próprio processo de recuperação foi objeto de abuso.\n\nArtigos 28.º, 32.º a 34.º do RGPD\n\nO artigo 33.º concede ao responsável pelo tratamento 72 horas para notificar a autoridade de controlo de uma violação de dados pessoais; o artigo 34.º exige que as pessoas afetadas sejam informadas quando o risco para elas for elevado. A Valve confirmou por escrito, por duas vezes, que o seu canal de apoio entregou contas às pessoas erradas — incluindo o histórico das contas, os registos de faturação e tudo o resto. Não foi publicada qualquer notificação ao abrigo de nenhum desses artigos, e nenhum utilizador afetado comunicou ter recebido alguma. Leia o regulamento ↗ arquivado 2026-09-20 ↗\n\nInclua o acesso ao apoio na sua solicitação →\nParte C — Quadros jurídicos · Secção 15 · Escala comercial\nSegue o rasto do dinheiro. Separa as transações.\nContexto e limites da fonte\n\nA questão da utilização comercial torna-se mais premente quando os fluxos de dinheiro são separados. As transferências de itens por terceiros, as vendas principais da Valve e os levantamentos externos de dinheiro são transações diferentes.\n\nO artigo pertence a Valve. O stock é de Valve. A transferência é executada nos servidores de Valve. Apenas o pagamento é efetuado noutro local — que é o passo que determina se alguém é um prestador de serviços de transferência de fundos, e o único passo Valve que não é aplicado.\n\nO mecanismo de receitas\nOnde o dinheiro realmente circula.\nTrês percursos / economia de um único item\n01 / ContaInventário de utilizadores\n\nArtigos em espera em Steam\n\n02 / TransferênciaComércio P2P\n\nUtilizador ↔ bot ou utilizador ↔ utilizador\n\n03 / LiquidaçãoPlataforma externa\n\nSaldo do site ou pagamento de Steam\n\nCirculaçãoO motor económico vai além do valor da transferência\n\nSteam fornece a infraestrutura de inventário e transferência utilizada pelos mercados externos. O argumento económico da investigação é que a liquidez da revenda e a procura recorrente sustentam as despesas com caixas, chaves e artigos de substituição, com comissões sobre as vendas subsequentes no Mercado Comunitário. Uma transferência P2P direta não implica qualquer comissão do Mercado Comunitário; esse facto contabilístico não resolve a questão do benefício mais alargado. Valve mantém o controlo sobre o acesso às contas e as restrições de negociação em todas as fases.\n\n01 / Procura secundáriaLiquidez e valor de revenda\n\nComércio externo e procura de jogos de azar\n\n02 / Despesas primáriasChaves, estojos e cápsulas\n\nCompras a partir de Valve, quando disponíveis\n\n03 / ReceitasReceitas da venda primária\n\nMais comissões sobre as vendas efetivas no mercado\n\n5% + 10%Steam + comissão CS2 sobre as vendas no Mercado Comunitário\n\nConclusão económica da investigação: os mercados de revenda de bens líquidos podem incentivar o consumo de artigos novos. O conhecido 15% combina as taxas de comissão do mercado, sujeitas a valores mínimos e arredondamentos; não se trata de uma taxa aplicada a todas as transações comerciais externas.\n\nTabela de preços do Mercado Comunitário de Valve ↗ arquivado 2026-09-21 ↗. A 25 de fevereiro de 2026 O Procurador-Geral de Nova Iorque intentou uma ação arquivado 2026-09-01 ↗ alegando que as «loot boxes» pagas estão relacionadas com a revenda externa por dinheiro e com os malefícios do jogo — a mesma relação que este dossiê documenta do ponto de vista da infraestrutura técnica. Essa queixa é uma alegação, não uma conclusão; é aqui citada porque uma agência estatal de aplicação da lei colocou em Valve uma questão adjacente à que este dossiê coloca: onde está o registo de aplicação da lei que corresponde às declarações públicas?\n\n01 / EntradaDepósito em criptomoedas\n\nRegistos de serviços externos e carteiras\n\n02 / ConversãoEquilíbrio → skins\n\nArtigos entregues através de Steam transações\n\n03 / SaídaVenda externa de moeda fiduciária\n\nVendedor, comprador e prestador de serviços de pagamento\n\nKYC?Identificar o controlo em cada transferência\n\nEsta é a via a seguir, e não um serviço de conversão de dinheiro através da API nativa Steam. Verifique os documentos de identificação, a custódia, os IDs das transações e os destinatários dos pagamentos junto de cada operador externo antes de autorizar um levantamento sem KYC.\n\nEstados Unidos / Lei do Sigilo Bancário\nClassifique a atividade e, em seguida, a obrigação.\n\nA FinCEN avalia a transmissão de fundos com base nas atividades desenvolvidas por uma empresa. A aceitação e a transferência de moeda virtual convertível podem dar origem a obrigações no âmbito dos serviços monetários, sujeitas às definições e exceções aplicáveis. A Carteira Steam da Valve aceita fundos e converte-os em itens do jogo; esses itens são depois liquidados através de operadores terceiros em troca de moeda real. O item e a sua transferência decorrem na infraestrutura da Valve; o levantamento de fundos não, e se alguma parte desse ciclo corresponde às definições de transferência de fundos é uma questão de classificação a cargo da FinCEN, não uma conclusão aqui tirada.\n\nFinCEN FIN-2019-G001, §§ 1–2, 5.1 ↗ arquivado 2025-07-11 ↗\n\nUnião Europeia / branqueamento de capitais\nAcompanhar os rendimentos, os conhecimentos e a assistência.\n\nA Diretiva (UE) 2018/1673 abrange a lavagem de dinheiro intencional e a participação envolvendo rendimentos de atividade criminosa. A questão que se coloca na investigação é o que a Valve sabia sobre os operadores que utilizavam a sua infraestrutura de negociação e OpenID após 13 de julho de 2016, quando descreveu publicamente essa utilização, e o que fez a esse respeito. A Valve não publicou qualquer registo de medidas coercivas por operador; seria esse registo, e não este dossiê, que responderia à questão.\n\nQuadro jurídico penal da UE ↗\n\nTerminologia da AMLD6: A diretiva em matéria de direito penal acima referida é distinta da Diretiva (UE) 2024/1640, também designada por AMLD6. Esta última tem um prazo geral de transposição fixado para 10 de julho de 2027, com exceções específicas. Artigo 78.º ↗ arquivado 2026-08-30 ↗\n\nParte C — Quadros jurídicos · Secção 16 · Notificação, resposta, responsabilidade\nA Lei dos Serviços Digitais: registar o conhecimento\nContexto e limites da fonte\n\nDois elementos de uma notificação ao abrigo do artigo 16.º são da responsabilidade do remetente e não fazem parte deste dossiê: os dados do próprio remetente e uma declaração de boa-fé de que a informação é exata. Tudo o resto que o artigo exige — a explicação fundamentada e a localização eletrónica exata — está definido na Secção 3 e no registo de percursos, com respostas guardadas e hashes, para que qualquer parte possa apresentá-la. Existem ainda duas restrições adicionais à própria lei: a perda da isenção de alojamento não implica, por si só, a responsabilidade ao abrigo de qualquer outra lei, e o valor «0» previsto no n.º 3 do artigo 52.º constitui um limite máximo legal, não uma sanção aplicada contra «1».\n\nNos termos da DSA, um prestador de serviços de alojamento mantém a sua isenção de responsabilidade apenas até ter conhecimento específico e não tomar medidas. Este dossiê constitui esse aviso. Indica os anfitriões, as datas, as respostas guardadas e os hashes. A partir da publicação, a questão já não é se Valve sabia — é o que Valve fez a seguir.\n\n01Julho de 2016 / a exposição «The Dossier»\nUm prazo de dez dias.\n\nO aviso acima reproduzido constitui o ponto de partida histórico para a comparação das medidas de execução no âmbito da investigação.\n\n0217 de fevereiro de 2024 / candidatura geral\nA janela temporal do DSA.\n\nDistinguir a conduta histórica da conduta durante o período em que se aplicam as obrigações relevantes da DSA.\n\n03Dez anos / instantâneo do dossiê original\nA duração requer um registo de notificações.\n\nO tempo decorrido desde julho de 2016 (ver Secção 11) é um indicador do processo. Não se trata de dez anos de violações comprovadas da DSA. Associe cada notificação a um elemento específico, à legislação aplicável, à prova de entrega e à resposta.\n\nN.º 3 do artigo 52.º / limite máximo previsto na lei6%\ndo volume de negócios anual a nível mundial\n\nMultas máximas por incumprimento das obrigações previstas na DSA, com base no exercício financeiro anterior do prestador. Trata-se de um limite máximo legal, não de uma sanção aplicada contra Valve.\n\nArtigos 6.º, 8.º e 16.º / o critério jurídico\n\nNo que diz respeito aos serviços de alojamento em linha relevantes, o conhecimento específico e a falta de ação atempada podem implicar a perda da isenção de responsabilidade relativa ao alojamento. Uma notificação suficientemente precisa pode comprovar o conhecimento do conteúdo em questão. A DSA não impõe qualquer obrigação geral de monitorização; a perda da isenção, por si só, não implica a responsabilidade ao abrigo de outra lei.\n\nDSA: Artigos 6.º, 8.º, 16.º, 52.º, 53.º, 93.º e considerando 17 ↗ arquivado 2026-09-20 ↗\n\nAnalisar reclamações arquivadas ↗Criar a cronologia da conta →Análise jurídica e económica completa →\nParte C — Quadros jurídicos · Secção 17 · Identidade, idade, acesso comercial\nMenores: um login com Steam não constitui uma verificação da idade\nContexto e limites da fonte\n\nNão constam dados de menores em nenhuma parte deste dossiê, nem foram recolhidos quaisquer dados: os autores não se registaram, não depositaram dados nem iniciaram sessão em nenhuma das plataformas mencionadas. Qualquer pessoa que se baseie nesta secção deve manter confidenciais as provas que envolvam crianças e suprimir os detalhes identificativos das provas apresentadas publicamente. A COPPA é aqui citada como uma lei de privacidade infantil com as suas próprias condições de âmbito de aplicação — público-alvo, conhecimento efetivo, dados pessoais recolhidos — e não como uma regra geral relativa à idade mínima para jogar; a queixa de Nova Iorque de 2026 é uma alegação por parte de uma autoridade estadual, não uma conclusão.\n\n«Iniciar sessão com Steam» comprova que existe uma conta. Isso não prova nada em relação à idade — e, nestes sites, é a única barreira entre uma criança e um depósito. Leia isto com Secção 3.1: no cliente Steam, o aviso que um navegador apresentaria nunca é exibido, pelo que a criança nunca o vê.\n\nO que o OpenID Steam ofereceIdentidade da conta\n\nUm SteamID verificado utilizado para iniciar sessão ou associar uma conta.\n\n≠\nO que o operador deve determinarCondições de elegibilidade para participar\n\nIdade, jurisdição e quaisquer verificações de identidade necessárias.\n\nBase técnica: Documentação do Steamworks OpenID ↗ arquivado 2026-09-21 ↗. A confirmação da identidade documentada não constitui uma certificação de que o utilizador possa jogar legalmente.\n\nCOPPA / crianças com menos de 13 anos\nIdentifique o operador e os dados.\n\nA COPPA aplica-se aos serviços abrangidos destinados a crianças e aos serviços que tenham conhecimento efetivo de que recolhem dados pessoais de crianças com menos de 13 anos. Trata-se de uma lei relativa à privacidade das crianças, não de uma regra universal sobre a idade mínima para jogar. Defina o público-alvo, os dados pessoais recolhidos, o conhecimento e o processo de consentimento parental.\n\nFTC: Requisitos da COPPA ↗ arquivado 2026-09-21 ↗\n\nAs provas a preservar\nRegiste o percurso desde o início de sessão até ao depósito.\n\nManter o sistema de verificação da idade do site, o texto relativo ao registo, os termos de elegibilidade, o processo de pagamento e o histórico de reclamações. Avaliar cada operador separadamente. Manter a confidencialidade de quaisquer provas que envolvam uma criança e ocultar os dados identificativos das provas apresentadas publicamente.\n\nUm registo de aplicação da lei relacionado é o Anúncio da queixa em Nova Iorque de 2026 arquivado 2026-09-01 ↗, que alega que as caixas de recompensas pagas causam danos aos jovens utilizadores. Não se trata de uma conclusão ao abrigo da COPPA.\n\nParte C — Quadros jurídicos · Secção 18 · Pedido ao abrigo do artigo 15.º do RGPD\nO pedido. A resposta. A comparação que falta.\n\nEle pediu quatro coisas, uma delas o registo que revelaria quem tinha introduzido uma chave API na sua conta. Três dias depois, o ticket foi encerrado com um link para uma página que não contém nenhuma dessas informações — e a frase utilizada para concluir o texto é contestada pelos próprios advogados de Valve.\n\nDe quem é esta conta · Origem e limites\n\nEstas imagens não são do PhishDestroy. Provêm de um titular de conta Steam comum — um dos inquiridos num breve inquérito realizado por este projeto, que apresentou ele próprio o pedido e forneceu as capturas de ecrã. A conta é dele, o ticket é dele e a correspondência decorre entre ele e o Apoio ao Cliente Steam. Este projeto não apresentou o pedido, não possui qualquer conta na plataforma e não é parte neste ticket.\n\nA 16 de setembro de 2026, apresentou um pedido de acesso aos dados pessoais ao abrigo do artigo 15.º do RGPD/CCPA, solicitando especificamente os registos de registo de chaves API, o histórico de inícios de sessão com endereços IP, o histórico de autorização de dispositivos e o histórico de transações. A 17 de setembro, o agente «Logen» encaminhou-o para a página de autoatendimento «Dados da Conta». A 18 de setembro, afirmou que as categorias solicitadas não constavam dessa página e pediu que o caso fosse encaminhado para a Equipa de Privacidade ou para o Encarregado da Proteção de Dados (DPO). A 19 de setembro, o agente «Kal» encerrou o ticket com o mesmo encaminhamento. Ambas as capturas de ecrã encontram-se abaixo (e-mail do requerente ocultado; SHA-256 em steam_tos_assets/screenshot-manifest.json).\n\nEle é o requerente ideal por uma razão simples: esta conta possui uma chave da API Web Steam que ele não criou, registada em localhost. Não se sabe quando foi criada — nem para ele, nem a partir de nada que Valve lhe tenha disponibilizado, porque o único registo que permitiria datá-lo é o registo de registo da chave API, que é precisamente a categoria que o encerramento ocultou. A chave não é nova: é anterior ao momento em que ele tomou conhecimento da mesma, num intervalo que não consegue medir, pela mesma razão.\n\nOutros titulares de contas estão a apresentar o mesmo pedido. Qualquer resposta que chegar será adicionada aqui nos mesmos termos que estas duas — número do ticket, data de captura, SHA-256, identidade do requerente ocultada — quer aceite as categorias, quer as recuse.\n\nEste projeto não se pronuncia sobre o motivo pelo qual o ticket foi encerrado. Não foi indicado qualquer motivo no próprio ticket, nem se infere qualquer motivo neste contexto.\n\nO pedido. A resposta. A comparação.ACOMPANHE O REGISTO\nEtapa 3 / 3\n\nEle solicitou quatro categorias específicas. A página «Dados da Conta» para a qual foi encaminhado corresponde à própria exportação de autoatendimento do Valve, e este projeto não pode enumerar o seu conteúdo para a conta de outra pessoa — pelo que não é publicada aqui qualquer comparação completa, categoria a categoria. O que consta do registo é a sua declaração de 18 de setembro, segundo a qual as categorias não existiam, e o encerramento do caso, em 19 de setembro, que repetiu o encaminhamento sem abordar essa questão.\n\nO PEDIDOCategorias específicasRegistos de chaves API, inícios de sessão, dispositivos e transações\nA RESPOSTAReferência aos dados da contaVerificar a troca de suporte\nO TESTEO que foi fornecido?Comparar cada categoria solicitada\nEcrã 1/2 — Pedido (16 de setembro) e primeira resposta, agente «Logen» (17 de setembro)\nGDPR ticket HT-2YBP-F7JP-D4VB — request and first response\nFonte: help.steampowered.com, pedido de assistência HT-2YBP-F7JP-D4VB · capturado entre 16 e 17 de setembro de 2026 · e-mail do requerente ocultado 2026-09-21 · Ficheiro: gdpr-ticket-1.png · SHA-256 da940c731ab9869d226e9d06ccc8a1b393738766b7b0c445a56662623e025a66 (screenshot-manifest.json).\nEcrã 2/2 — Pedido de escalamento (18 de setembro) e encerramento, agente «Kal» (19 de setembro)\nGDPR ticket HT-2YBP-F7JP-D4VB — escalation request and closure\nFonte: help.steampowered.com, pedido de assistência HT-2YBP-F7JP-D4VB · capturado em 18–19 de setembro de 2026 · Ficheiro: gdpr-ticket-2.png · SHA-256 44844ea7b251f7fd7d79f87ee1578a846606a97b9659d3a53b322120c422219b (screenshot-manifest.json).\nResposta final, 19 de setembro (textual):\n«Os dados Steam que a plataforma guarda já se encontram na página «Dados da Conta». Uma vez que não há mais informações Steam que o Apoio ao Cliente possa fornecer, Este pedido será encerrado.\"\nNão foram fornecidos dados · não foi indicada qualquer base jurídica para a recusa · não foi apresentado qualquer resultado do recurso\nEssa frase é falsa, e são os próprios advogados de Valve que o provam. A carta do advogado de 1 de outubro de 2025, no parágrafo 1.9, descreve uma correlação ao nível do dispositivo que associa um dispositivo a dezenas de contas (Apêndice A). A mesma resposta incluía 830 páginas de registos arquivados (Anexo B). Nada disso consta na página «Dados da conta».\nPor que é que esta conta solicitou o registo da chave API?\n\nEle não escolheu essas quatro categorias ao acaso. O localhost A chave da sua conta é o indício de um script, e não de uma pessoa a introduzir um domínio real na página do programador (Secção 5, Secção 6). O único registo que indica quem o criou e de onde provém é o registo de registo da chave API. Foi isso que ele pediu em primeiro lugar. Foi isso que a empresa se recusou a divulgar.\n\nFonte: o titular da conta, durante o inquérito deste projeto. As capturas de ecrã dos bilhetes acima foram encriptadas; a página da chave não foi publicada.\n\nAvaliação · PhishDestroy\n\nEncerrar um ticket com a questão ainda em aberto não é um acidente neste caso. É o desfecho normal. Nós defendemos 16,319 registos de reclamações e de assistência mantidos e 354 trocas de suporte sem duplicados extraídos deles. Este bilhete é um exemplo datado e exaustivamente documentado da forma que assumem.\n\nTicket de assistência — ArquivadoHT-2YBP-F7JP-D4VB\nTipo de pedidoArtigo 15.º do RGPD – Pedido de acesso aos dados pessoais (DSAR)\nEstado do bilheteENCERRADO A 19 DE SETEMBRO DE 2026 — NÃO FORAM FORNECIDOS DADOS\nAgentes na bolsa«Logen» (17 de setembro), «Kal» (19 de setembro)\nArquivado16 de setembro de 2026\nDados solicitadosQuem registou a chave da API Web associada a esta conta e a partir de que endereço IP / dispositivo / data e hora\nBase jurídica invocadaArtigo 15.º do RGPD — direito de acesso aos dados pessoais\nO quadro jurídico:O n.º 3 do artigo 12.º concede ao responsável pelo tratamento um prazo de um mês a contar da receção (prorrogável mediante justificação). Esse prazo ainda não tinha expirado à data da publicação, e este dossiê não alega qualquer incumprimento do prazo. A objeção diz respeito ao mérito: a resposta final remete para uma página de autoatendimento, mas não demonstra que as quatro categorias de dados mencionadas tenham sido apresentadas; além disso, caso o responsável pelo tratamento se recuse a agir, o n.º 4 do artigo 12.º exige que este indique os motivos e as vias de reclamação. Nenhum destes elementos consta da resposta final.\nPor que é que estes dados específicos são importantes?\n\nO registo de eventos da chave da API Web é o registo que indica se um terceiro registou uma chave utilizando um cookie de sessão roubado — o mecanismo descrito nas queixas de roubo de inventário preservadas no arquivo deste dossiê. A divulgação de quem registou uma chave API, a partir de que endereço IP e em que momento, permitiria:\n\nPermitir que a vítima compare o endereço IP de criação da API com o seu próprio histórico de inícios de sessão\nRevelar endereços IP de centros de dados associados a infraestruturas conhecidas de phishing e de bots de jogos de azar\nApresentar provas que possam ser utilizadas em processos civis ou criminais contra o autor\nIndicar se o titular da conta foi notificado quando a chave foi criada\nO que consta dos autos: A Valve mantém registos ao nível do dispositivo e de correlação de contas — a carta do seu advogado, datada de 1 de outubro de 2025, descreve-os (ver Apêndice A, Memorando de Provas — Fonte 1). No pedido HT-2YBP-F7JP-D4VB, a mesma categoria de registos foi solicitada pelo titular dos dados e o pedido foi encerrado com um encaminhamento para uma página de autoatendimento que, segundo o titular dos dados, não os continha. A legalidade dessa recusa é uma questão da competência da autoridade de controlo; o efeito é que a pessoa a quem os dados dizem respeito não os recebe.\nA troca de mensagens — quatro mensagens, três dias\n\nDois agentes de apoio da Steam responderam utilizando os nomes próprios indicados no ticket: «Logen», a 17 de setembro, e «Kal», a 19 de setembro. Ambos encaminharam o requerente para a página «Dados da Conta». Nada no ticket indica se o pedido chegou à Equipa de Privacidade ou ao Responsável pela Proteção de Dados de Valve, e o dossiê não especifica quem são os agentes, quais são as suas funções nem como o ticket foi encaminhado.\n\n16 de setembro\nPedido ao abrigo do artigo 15.º apresentado com quatro categorias de dados especificadas\n17–18 de setembro\nConsulta aos dados da conta; o requerente solicita que o caso seja encaminhado ao Encarregado da Proteção de Dados\n19 de setembro\nO pedido de assistência foi encerrado com a mesma referência; sem dados, sem fundamento indicado\nO que o artigo 15.º do RGPD confere explicitamente ao titular dos dados\nArt. 15.º, n.º 1, alínea a)Finalidades do tratamento — por que razão a Valve conserva os dados\nArt. 15.º, n.º 1, alínea b)Categorias de dados — o que Valve contém\nArt. 15.º, n.º 1, alínea c)Destinatários ou categorias de destinatários — quem recebeu os dados (por exemplo, o titular da chave API)\nArt. 15.º, n.º 1, alínea d)Período de retenção ou critérios para o determinar\nArt. 15.º, n.º 3Uma cópia dos dados pessoais que estão a ser tratados — ou seja, o próprio registo da chave API\nART. 12.º, n.º 3Resposta necessária no prazo de um mês a partir da data de receção; qualquer prorrogação deve ser comunicada no prazo desse mês. O prazo ainda não tinha expirado à data da publicação. Art. 12.º, n.º 4: Se o responsável pelo tratamento não tomar medidas, deve explicar os motivos e informar o titular dos dados sobre as vias de reclamação.\nProcedimento de reclamação regulamentar — para qualquer utilizador\n\nQualquer utilizador que tenha apresentado um pedido ao abrigo do artigo 15.º do RGPD à Valve e não tenha recebido uma resposta em conformidade (ou uma recusa padrão sem dados) pode apresentar uma reclamação junto da autoridade de controlo do seu Estado-Membro da UE/EEE. O estabelecimento da Valve na UE é a Valve GmbH, em Hamburgo, pelo que a autoridade de controlo principal para reclamações transfronteiriças é a Autoridade de Proteção de Dados e Liberdade de Informação de Hamburgo (HmbBfDI). (O representante previsto no artigo 27.º da Valve também se encontra em Hamburgo; o endereço de um representante não determina, por si só, a autoridade competente.) Também é possível apresentar uma queixa junto da autoridade do próprio Estado-Membro do queixoso, nos termos do artigo 77.º.\n\nFormulário de reclamação da HmbBfDI ↗ Texto do RGPD (art. 12.º, 15.º e 77.º) ↗ arquivado 2026-09-20 ↗Orientações do EDPB ↗\n\nReferência do ticket para qualquer reclamação: HT-2YBP-F7JP-D4VB — conservado neste dossiê como um caso documentado.\n\nUm caso documentado\nOs registos existem; o titular dos dados não os recebeu.\n\nO advogado de Valve descreveu os registos de correlação ao nível do dispositivo numa carta datada de 1 de outubro de 2025. Em 19 de setembro de 2026, um pedido ao abrigo do artigo 15.º relativo à mesma categoria de registos foi arquivado com uma referência a uma página de autoatendimento que, segundo o requerente, não os continha, sem que fosse indicada qualquer base jurídica. O ticket HT-2YBP-F7JP-D4VB é um exemplo documentado; se isso reflete uma prática mais generalizada é uma questão que cabe à autoridade de controlo, que pode solicitar à Valve os seus registos de tratamento.\n\nArtigos 12.º, 15.º e 77.º do RGPD / Autoridade de controlo\n\nUma reclamação ao abrigo dos artigos 12.º e 15.º pode ser apresentada diretamente junto da autoridade de controlo competente, sem custos (artigo 77.º). A autoridade pode impor medidas corretivas, incluindo ordens para dar cumprimento ao pedido de acesso, e coimas nos termos do artigo 83.º, n.º 5, alínea b), por violações dos direitos dos titulares dos dados. A conservação da referência original do bilhete e de qualquer resposta Valve (ou a sua ausência) reforça a reclamação.\n\nVer o modelo do DSAR →\nParte C — Quadros jurídicos · Secção 19 · Direito dos contratos\nO Acordo de Assinatura em relação à própria arquitetura da plataforma\nLimites de contexto e de fonte\n\nOs autores não são advogados e nada do que aqui se apresenta constitui aconselhamento jurídico. A SSA é citada a partir da revisão de 10 de setembro de 2026; uma revisão diferente pode apresentar uma redação diferente, e a numeração das cláusulas tem variado ao longo das revisões — verifique a cláusula na versão que regulava a conduta em questão. Os argumentos relativos aos artigos 25.º e 32.º indicam o que o regulamento exige, e não que uma autoridade de controlo tenha constatado uma infração. Os valores apresentados no Argumento 1 respeitam os limites de âmbito estabelecidos na secção 13.\n\nTrês das disposições centrais da SSA entram em conflito com a forma como a plataforma está concebida: a proibição de utilização comercial, face a um limite máximo de preço no «Market» que empurra as vendas de elevado valor para fora da plataforma; a cláusula de responsabilidade do utilizador relativa às chaves API, em contraposição a um ponto de extremidade de chaves que, antes de 2023, não exigia autenticação de dois fatores; e a formulação relativa à aplicação da lei, em contraposição a um registo público que não indica qualquer aplicação por operador. Se estas contradições afetam a aplicabilidade da lei é uma questão a decidir por um tribunal; esta secção expõe os factos que um tribunal teria perante si.\n\nArgumento 1 / Arquitetura da capitalização de mercado\nO limite máximo do mercado e a proibição de utilização comercial\n\nO Mercado Comunitário Steam tem um limite máximo de listagem de cerca de $1,800. Em cinco mercados, numa imagem instantânea desatualizada (23 de setembro de 2026), 248 categorias de artigos CS2 apresentam preços, determinados de forma independente, superiores a esse limite máximo em dois ou mais desses mercados; tais artigos não podem ser vendidos a esses preços na própria plataforma da Valve. Os proprietários que pretendem esses preços recorrem a mercados de terceiros, que funcionam com contas Steam e a API Steam — cuja utilização é classificada pela SSA como comercial, salvo se expressamente autorizado.\n\nOs artigos excedem o limite máximo do Mercado → os mercados de terceiros preenchem a lacuna → esses mercados utilizam contas Steam e a API Steam → a SSA proíbe a utilização comercial sem autorização → não foi publicado qualquer registo de autorizações. A taxa combinada do Mercado Comunitário, de cerca de 15%, aplica-se apenas às vendas concluídas no interior do Mercado, e não a estas transações externas.\nArgumento 2 / Arquitetura de segurança da chave API\nA vulnerabilidade da chave API como uma questão de conceção da plataforma, e não como negligência do utilizador\n\nAntes de 2023, o endpoint de criação de chaves API do Steam aceitava um pedido POST com um sessionid roubado e gerava uma credencial com privilégios elevados sem confirmação por e-mail, sem autenticação de dois fatores ou sem verificação por dispositivo. As queixas relativas ao sequestro de API recolhidas nesta investigação seguem um padrão: script do atacante, cookie de sessão roubado, criação silenciosa de chaves, interceção de transações (a carga útil do pedido é apresentada na Secção 8).\n\nO artigo 25.º do RGPD (proteção de dados desde a conceção) e o artigo 32.º (segurança do tratamento) exigem medidas técnicas adequadas ao risco. A emissão de uma credencial suscetível de interceção comercial sem um segundo fator de autenticação ou notificação ao titular é uma questão de conceção que cabe ao responsável pelo tratamento. A questão de saber se a cláusula do SSA que atribui a responsabilidade ao utilizador pode ser invocada neste contexto é da competência do tribunal e da autoridade de controlo.\n\nArgumento 3 / Visibilidade em tempo real\nValve recebe o nome de host de autenticação em cada início de sessão\n\nO nome de host de autenticação chega ao ponto final OpenID de Valve em texto simples em openid.return_to e openid.realm (a estrutura do pedido é apresentada na Secção 3). A sua extração é uma operação padrão. A partir de 2026-09-22, em 26 pares, o domínio principal estava incluído no Filtro de Ligações, enquanto o anfitrião que apresentava o seu Steam não estava. O Valve não publicou qualquer registo de aplicação por operador, pelo que não é possível determinar, a partir de dados públicos, se alguma medida além do Filtro de Ligação foi aplicada a estes anfitriões.\n\nQuem suporta os custos\nO padrão observado nas queixas arquivadas\n\nNas reclamações analisadas, a resposta do Steam Support a uma alegação de apropriação indevida de uma chave API segue sempre o mesmo padrão: recusar a restauração, referir a responsabilidade do utilizador pela conta e pela sua chave API e encerrar o ticket. Neste dossiê não é apresentada qualquer estimativa do número total de contas afetadas nem do valor perdido; não foi identificada qualquer fonte para esses dados.\n\nA questão não é se os utilizadores individuais cometeram erros. A questão é quem é responsável por uma arquitetura que, até 2023, permitiu que um pedido POST com um cookie roubado criasse uma credencial de negociação com privilégios elevados, sem qualquer notificação e sem autenticação de dois fatores.\nO SSA enquanto documento vs. o SSA enquanto contrato\nUm tribunal que analisasse este processo não interpretaria a SSA isoladamente.\n\nAnalisaria esse documento em conjunto com a carta do advogado de outubro de 2025, que descreve a correlação ao nível do dispositivo, as datas de registo do host de autenticação, os carimbos de data e hora do registo em lote, a carga útil do pedido da chave API e os dez anos decorridos entre os avisos de julho de 2016 e as plataformas que ainda estavam em funcionamento em setembro de 2026. É esse o registo que Valve teria de abordar.\n\nSSA em relação ao processo / pontos-chave\n«Sem fins comerciais» — o limite máximo do Mercado empurra as vendas de elevado valor para mercados comerciais de terceiros\n«Os utilizadores são responsáveis pelas chaves API» — não haverá autenticação de dois fatores no ponto de acesso das chaves antes de 2023\n«Tomamos medidas contra os infratores» — não são publicados registos de medidas tomadas por operador desde julho de 2016\n«Aceitou os termos» — no padrão de sequestro, a aceitação é enviada por um script, e não pelo titular da conta\nConclusão · O que os autos demonstram e o que solicitamos\nAs conclusões. Os registos que solicitamos.\nContexto e limites da fonte\n\nCada conclusão abaixo está associada a um registo público datado nas secções acima. Os pedidos são dirigidos às autoridades que podem obrigar a única coisa a que esta investigação não tem acesso: os próprios registos de aplicação da lei, acesso e tratamento de dados da Valve.\n\nCada pedido surge na sequência de uma conclusão datada. As autoridades podem solicitar registos que esta investigação baseada em fontes públicas não pode exigir.\n\nO que os registos públicos comprovam\n44 plataformas ativas são autenticadas através de um domínio registável separado — 27 com um ficheiro de evidência publicado por rota, 17 provenientes de recolha manual e listadas separadamente. Em 2026-09-22, 26 pares tinham o domínio principal bloqueado no Filtro de Ligações Steam, enquanto o servidor que alojava o seu login não estava — csgogem.com bloqueado, api.csgem.com registado desde março de 2014. O Steam recebe esse nome de anfitrião em openid.realm e openid.return_to a cada vez que iniciar sessão. Secção 3\nEm 13 de julho de 2016, Valve divulgou publicamente o nome do mecanismo e proibiu-o, tendo as notificações do seu advogado, datadas de 20 de julho de 2016, estabelecido um prazo de dez dias. Não foi publicado qualquer registo de aplicação da lei por operador nos dez anos que se seguiram a esse prazo. Secção 11\nO ponto final da chave da API Web Steam emitia uma credencial com privilégios elevados e capacidade de efetuar transações com base apenas num cookie de sessão, sem qualquer fator de autenticação secundário, até 2023. Secção 5\nUm pedido ao abrigo do artigo 15.º do RGPD (ticket HT-2YBP-F7JP-D4VB) foi encerrado ao fim de três dias com um link para o serviço de autoatendimento e sem quaisquer dados. Secção 18\nO que pedimos a cada autoridade\nComissão de Jogos de Azar do Estado de Washington\nReabra o ficheiro de 2016. Solicite um relatório, operador a operador, indicando quais as contas, bots e hosts de resposta que foram desativados após os avisos de dez dias e quais os operadores que posteriormente recuperaram o acesso. Secção 2\nHmbBfDI (Hamburgo; Valve GmbH)\nVerificar se a resposta ao abrigo do artigo 15.º cumpriu o dever do responsável pelo tratamento e exigir a divulgação dos registos de registo e de acesso à chave API relevantes para a identificação do autor. Secção 18\nCoordenadores de serviços digitais da DSA\nInclua o encaminhamento do servidor de autenticação no registo como aviso e, em seguida, avalie se a resposta de Valve cumpre as suas obrigações, uma vez documentada a informação. Secção 16\nQualquer titular de dados\nUtilize o modelo do artigo 15.º para solicitar os mesmos registos para a sua própria conta; um registo arquivado permite verificar quem iniciou uma reposição ou criou uma chave. Apêndice G\n\nO pedido único subjacente a todos os quatro é o mesmo: publicar os registos relativos à aplicação da lei, ao acesso e ao tratamento de dados que apenas a Valve detém. Um aviso na página inicial, uma carta com prazo de dez dias e uma página de autoatendimento são manifestações de controlo. Se esse controlo foi ou não exercido é uma questão à qual o registo público não pode responder, mas a que uma entidade reguladora pode.\n\nAnexos — provas principais e materiais de trabalho\nAnexo A — Correspondência com os advogados\nMemorando de Provas — material fornecido pela Fonte 1\n\nBase factual e estatuto das fontes relativas à correspondência do advogado invocada nas secções 1, 18 e 19.\n\nBase factual e estatuto da fonte — documentos fornecidos pela Fonte 1\nO utilizador cujo banimento permanente deu origem a esta auditoria não é o alvo da mesma. A questão de saber se esse banimento foi justificado não é aqui analisada, e este dossiê não o defende nem o contesta. A conta não é o que está em causa. O que importa é o conteúdo: Fonte 1 — o titular da conta banida, que recebeu a correspondência abaixo do advogado de Valve na qualidade de titular dos dados no âmbito do seu próprio pedido ao abrigo do RGPD — transmitiu essa correspondência e os autos do processo que a acompanhavam, juntamente com o direito de os consultar publicamente. O nome não é divulgado; os documentos são descritos por data, metadados do criador e hash.\n\nEssa correspondência foi enviada em resposta a um pedido ao abrigo do RGPD/DSAR. No decurso da mesma, o advogado de Valve registou em ata uma declaração, devidamente assinada, na qual descrevia uma funcionalidade que o Apoio ao Cliente de Steam tinha anteriormente informado aos utilizadores não ser tecnicamente possível. O parágrafo citado abaixo corresponde a essa declaração.\n\nA análise mais aprofundada dos autores sobre o extrato de registo produzido é omitido deste dossiê enquanto se aguarda uma análise independente. Não é tido em conta em nenhuma outra parte desta investigação.\n\nA admissão registada: telemetria persistente ao nível do dispositivo\n\nNo parágrafo 1.9 da carta atribuída ao advogado de Valve, os advogados de Valve afirmam: «Entre 2019 e 2023, esta conta foi utilizada principalmente a partir de um dispositivo que também foi utilizado para iniciar sessão em dezenas de contas Steam roubadas.»\n\nO facto: O advogado de Valve descreve aqui a correlação ao nível do dispositivo entre contas ao longo de quatro anos. O serviço de apoio de Steam informou as vítimas de roubo de que não era tecnicamente possível localizar os artigos roubados nem associar contas a dispositivos. Steam Guard A autorização de dispositivos está documentada publicamente, pelo que a existência de registos por dispositivo não é, em si, uma novidade; o que é novo é a confirmação por escrito do advogado de que esses registos são mantidos e correlacionados entre contas ao longo de períodos de vários anos.\n\nPor que é que isto é importante: A correlação que pode ligar um dispositivo a dezenas de contas pirateadas ao longo de quatro anos pertence à mesma categoria de registos que o Serviço de Apoio afirmou não poder utilizar em benefício das vítimas. Os registos dessa classe seriam capazes de identificar contas e dispositivos numa cadeia de roubo e revenda. Quais os registos que existem, durante quanto tempo são conservados e com base em que critérios são ocultados aos titulares dos dados são questões que devem ser dirigidas à autoridade de supervisão.\n\nFonte: carta do advogado de Valve, datada de 1 de outubro de 2025, parágrafo 1.9, e o seu anexo em PDF de 830 páginas · recebido pela Fonte 1 em resposta a um pedido ao abrigo do artigo 15.º do RGPD · SHA-256 do anexo registado em disclosure-audit.json · A carta em si não é reproduzida; os nomes das contas e os dados de terceiros são omitidos.\n\nEstado: abrir\nOs materiais de referência estão disponíveis no arquivo de evidências.\nApêndice B — O ficheiro PDF gerado · verificação da expurgação\nA censura no PDF gerado é meramente estética: o texto ocultado continua a poder ser extraído\n\nO advogado de Valve respondeu a um pedido de acesso ao abrigo do RGPD com um anexo de 830 páginas, no qual as partes censuradas foram pintadas sobre o texto, em vez de serem removidas. 902,270 caracteres encontram-se por baixo das barras pretas e são exibidos diretamente com uma ferramenta de extração de texto — incluindo os identificadores de terceiros que as barras tinham como objetivo ocultar. Aqui são publicadas apenas as contagens agregadas; nenhum conteúdo abrangido é reproduzido e o próprio apêndice não é publicado.\n\n1. O que a verificação geométrica revelou\n\nResposta ao abrigo do artigo 15.º do RGPD, datada de 1 de outubro de 2025 foi acompanhado por um apêndice em PDF de 830 páginas (metadados do produtor Aspose.PDF para .NET, criados e modificados na mesma data). Os autores realizaram uma verificação da geometria ao nível da página: para cada página, foram localizados retângulos opacos, quase pretos, pintados por cima da camada de texto, e foram contados os caracteres extraíveis que se encontravam por baixo deles.\n\nMedido no ficheiro gerado\n902,270\nCaracteres que ainda podem ser extraídos de debaixo das barras pretas\nContados, não estimados. Trata-se de uma contagem dos personagens abrangidos — não de vítimas, reidentificações ou incidentes.\n830 / 830\nPáginas afetadas — todas as páginas\n986\nRetângulos sobre texto extraível\n1,329\nTotal de retângulos pretos opacos\nAs barras pretas são sobrepostas à camada de texto; não a removem. O texto por baixo das barras pode ser extraído com ferramentas padrão de PDF. Apenas são publicadas contagens agregadas; nenhum conteúdo ocultado é reproduzido aqui.\nDemonstração forense: separação de camadas\nMAQUETE DE SOBREPOSIÇÃO VETORIAL DO ASPOSE.PDF PARA .NET (ANEXO, p. 412)\n\nDenúncia apresentada contra a conta: [INÍCIO DE SESSÃO: utilizador_ocultado_667]\n\nMotivo indicado pelo utilizador: [TEXTO: «O utilizador denuncia a existência de artigos duplicados no inventário e conduta comercial abusiva...»]\n\nPrimeiro plano: <path fill=\"#000\" />Falha: Fluxo UTF-8 subjacente intacto\nFonte: anexo em PDF da carta do advogado de 1 de outubro de 2025 (830 páginas, metadados do produtor Aspose.PDF para .NET) · calculado pelos autores, método e contagem por página em disclosure-audit.json · O SHA-256 do apêndice registado no mesmo ficheiro · o próprio apêndice não é publicado.\n2. Por que é que isto é importante para a resposta de um titular de dados\n\nO advogado de Valve enviou este ficheiro a um titular de dados em resposta a um pedido relativo aos registos dessa pessoa. As barras que o cobrem são meramente estéticas: o texto subjacente nunca foi removido, pelo que os identificadores de terceiros que as barras pretendiam ocultar foram enviados ao destinatário juntamente com o ficheiro. Uma supressão que pode ser removida com uma ferramenta de extração de texto não oculta nada e, além disso, impede o destinatário de determinar o que foi divulgado e o que não foi.\n\nO n.º 4 do artigo 15.º é a razão pela qual essas barras existem: o direito de obter uma cópia não deve prejudicar os direitos e liberdades de terceiros. Essa é a obrigação que esta produção não cumpriu. Cabe à autoridade de controlo determinar se se trata de uma violação de dados pessoais nos termos do artigo 4.º, n.º 12; a divulgação em si é mensurável no ficheiro e reproduzível por qualquer pessoa que possua os mesmos bytes — o SHA-256 está publicado, mas o apêndice não.\n\nO que estava por baixo das barras não eram números de conta. Tratava-se do conjunto de denúncias apresentadas por utilizadores contra o requerente, com os respetivos autores indicados: Steam inícios de sessão que, dado que um início de sessão raramente é utilizado apenas no Steam, identificam a pessoa por trás deles — segundo os autores, mais de 60% dos utilizadores mencionados no documento são totalmente identificáveis — juntamente com o texto original, sem censura, do que escreveram. Esse texto inclui ameaças de morte e insultos dirigidos à nacionalidade do requerente. Algumas das pessoas assim identificadas são menores de idade. A produção entregou uma lista com os nomes dos jornalistas à pessoa que tinha sido alvo da reportagem, que é precisamente o dano que o n.º 4 do artigo 15.º visa impedir.\n\nA ordem dos caracteres no ficheiro é tão importante quanto o seu conteúdo. O pedido foi inicialmente recebido com uma exigência de provas adicionais de identidade, com o argumento de que o endereço de e-mail com pseudónimo do requerente não continha o seu nome; a conta foi banida permanentemente durante o atraso que se seguiu. A carta que finalmente entregou os dados, mais de seis semanas após o prazo de um mês previsto no n.º 3 do artigo 12.º, ameaçou o destinatário com um processo penal e reteve o restante dos seus próprios dados até que este explicasse a atividade da sua conta ao advogado. A divulgação também esclarece duas questões a que Valve não tinha respondido publicamente: os registos apresentados revelam ligações entre contas que remontam a 2019 e dados de telemetria interna com um nível de detalhe que Valve nunca tinha descrito.\n\nÂmbito desta secção: A observação aqui apresentada limita-se aos aspetos técnicos da redação, analisados com base no ficheiro tal como foi produzido. A análise mais aprofundada dos registos produzidos, realizada pelos autores, não é divulgada enquanto se aguarda uma revisão independente e não é invocada em nenhuma outra parte deste dossiê.\n\nProva: carta do advogado datada de 1 de outubro de 2025 e o seu anexo em formato PDF (SHA-256 registado no ficheiro de auditoria); Medidas e método para ficheiros PDF ao nível da página ↗. A sequência do pedido, a recusa referida na página 8 e a descrição dos registos divulgados estão descritas na íntegra no relato de PhishDestroy, «O meu cão contra os advogados de elite especializados no RGPD», 17 de agosto de 2026 ↗ arquivado 2026-08-21 ↗. Os nomes das contas e os dados de terceiros foram omitidos aqui; nada do que está coberto pelas barras é reproduzido.\n\nNa página 8 da carta de acompanhamento, parte do pedido é recusada, sendo o motivo apresentado por escrito: Não é possível fornecer informações mais detalhadas devido à proteção dos dados pessoais dos outros utilizadores da plataforma Steam… — não é possível dar uma resposta mais detalhada, uma vez que os dados pessoais de outros Steam utilizadores têm de ser protegidos. O apêndice de 830 páginas fazia parte do mesmo pacote. O que as barras ocultavam não eram números de conta: eram as denúncias apresentadas contra o requerente, com os nomes dos autores indicados e as mensagens originais, não censuradas, em anexo. O titular da conta tinha solicitado a Valve, através do seu advogado, o seu próprio processo; o que conseguiu extrair dele eram os dados de outras pessoas. Nada neste apêndice depende de quem desenhou as caixas. O que fica estabelecido é que a proteção Valve invocada como fundamento para a recusa de divulgação é a mesma proteção que esta mesma entrega não cumpriu, no mesmo envelope, no mesmo dia.\nDocumentação de apoio e correspondência jurídica\n\nFonte: https://phishdestroy.io/steam_dossier/pt/index#exhibit-gallery-section\n\nApêndice D — Recolha de amostras\nDocumentos primários selecionados\n\nSeis registos do arquivo — três issues do GitHub nos trackers de Valve e três contas do Reddit relativas a resultados de suporte contestados. Cada fonte permanece associada à alegação, ao texto guardado e à questão que esta suscita.\n\n1 / 6 registos selecionados\nEscolha um registo de origem\nGH-01 / GITHUBAbrir na compilação guardada\nChaves de hardware, solicitadas em 2016\n\nValveSoftware / steam-for-linux · n.º 4521 · 2016-06-27\n\nUm utilizador solicitou ao Valve que suportasse chaves de hardware U2F como segundo fator de autenticação alternativo. A questão guardada tem as etiquetas «Pedido de funcionalidade» e «Revisada», estando o seu estado registado como «aberta».\n\nSolicito que o Steam passe a suportar a chave USB U2F como alternativa.\n\nExcerto da issue do GitHub ↗\nRegisto documentado\nUm pedido datado relativo a uma medida de segurança adicional para a conta, publicado no próprio sistema de acompanhamento de problemas do Valve e marcado como «revisto».\nExigência de responsabilização\nPublique a decisão relativa ao produto, a data de resposta e a proteção concedida após a análise.\nLer registo guardado →Abrir o GitHub ↗\nNo dossiê: Medidas de segurança da conta →Arquivo n.º 484 · compilação 2026-09-17\nGH-02 / GITHUBAbrir na compilação guardada\nRelatórios de falhas sem uma opção de exclusão eficaz\n\nValveSoftware / steam-for-linux · n.º 6459 · 2019-08-18\n\nO repórter descreve um cliente Steam de 12 de agosto de 2019 no Ubuntu 16. Afirma que a desativação do destino do «crash-upload» não se manteve após o reinício e inclui a configuração relevante.\n\nSe desativar o `ServerURL`, este é substituído após cada reinício.\n\nExcerto da issue do GitHub ↗ arquivado 2026-04-19 ↗\nRegisto documentado\nUma reclamação específica relativa à privacidade, com a data do cliente, o sistema operativo e um excerto da configuração. O problema registado encontra-se em aberto.\nExigência de responsabilização\nIdentifique a investigação, as compilações afetadas e a alteração que tornou a opção de exclusão efetiva.\nLer registo guardado →Abrir o GitHub ↗arquivado 2026-04-19 ↗\nNo dossiê: Solicitar os registos subjacentes →Arquivo n.º 467 · compilação 2026-09-17\nGH-03 / GITHUBAbrir na compilação guardada\nFoi comunicada uma utilização abusiva de bilhetes de autenticação ao Valve\n\nValveSoftware / Source-1-Games · n.º 3857 · 2022-02-26\n\nO autor alega que a operação do servidor retinha Steam bilhetes de autenticação após os jogadores se terem desligado e utilizava listas de servidores enganosas. A publicação pede a Valve que se pronuncie sobre este comportamento.\n\nFazer com que os seus servidores pareçam estar cheios.\n\nExcerto da questão no GitHub ↗\nRegisto documentado\nUma denúncia pública apresentada no sistema de acompanhamento do Valve a 26 de fevereiro de 2022. O seu estado guardado é «aberto»; a denúncia inclui links para capturas de ecrã.\nExigência de responsabilização\nApresente o resultado da investigação e o registo das medidas de mitigação relativas ao abuso do bilhete de autenticação que foi comunicado.\nLer registo guardado →Abrir o GitHub ↗\nNo dossiê: Âmbito do conjunto de dados →Arquivo n.º 768 · compilação 2026-09-17\nRD-01 / REDDITPerfil do autor\n44 compras contestadas no Mercado\n\nr/DotA2 · nome de utilizador não divulgado · 2022-07-07\n\nO autor refere 44 compras não autorizadas no Market, realizadas a 6 de julho de 2022, e perdas da ordem de $500+. Afirma que a autenticação de dois fatores estava ativada e descreve respostas repetidas, baseadas em modelos, por parte do apoio ao cliente.\n\nJá é o segundo ticket que envio e ainda não recebi nenhuma resposta do Steam que não seja um modelo copiado e colado automaticamente.\n\nExcerto da publicação no Reddit ↗ arquivado 2025-03-20 ↗\nRegisto documentado\nUm relato datado de compras contestadas, com links para capturas de ecrã das transações e uma resposta do serviço de apoio. Os montantes e os factos referidos são da autoria do autor.\nExigência de responsabilização\nReconcilie as compras contestadas com os registos de transações e de sessões. Explique os fundamentos que estiveram na base da decisão do serviço de apoio.\nLer registo guardado →Abrir o Reddit ↗arquivado 2025-03-20 ↗\nNo dossiê: Apoio e aplicação da lei →Arquivo n.º 4,533 · compilação 2026-09-17\nRD-02 / REDDITPerfil do autor\nUma proibição permanente e recurso encerrado\n\nr/ohnePixel · nome de utilizador não divulgado · 2024-12-09\n\nO autor contesta o banimento permanente e afirma que o apoio invocado se baseou em suspeitas de transferência de conta e em denúncias da comunidade. Descreve os tickets encerrados e os planos para solicitar os seus dados pessoais.\n\nExpliquei a minha situação e pedi mais detalhes, mas eles mantêm a sua decisão e estão a encerrar os meus tickets.\n\nExcerto da publicação no Reddit ↗\nRegisto documentado\nUma descrição do recurso guardada, incluindo os motivos que, segundo o autor, justificam o apoio prestado e links para quatro imagens. A data da publicação provém da exportação de dados de apoio selecionada.\nExigência de responsabilização\nIdentifique os elementos de prova que fundamentam a proibição permanente e os meios de recurso disponíveis para a contestar. O encerramento de um recurso não constitui uma justificação da decisão.\nLer registo guardado →Abrir o Reddit ↗\nNo dossiê: Solicitar os registos subjacentes →Arquivo n.º 4,766 · compilação 2026-09-17\nRD-03 / REDDITPerfil do autor\nUm reinício da recuperação e uma perda registada de $10,000\n\nr/legaladvice · nome de utilizador não divulgado · 2025-05-09\n\nO autor alega que o serviço de apoio redefiniu as credenciais e desativou as proteções da conta depois de outra pessoa ter enviado um pedido de recuperação. O autor refere uma perda de cerca de US$10,000 de uma conta inativa.\n\nSteam O serviço de apoio redefiniu a minha palavra-passe e desativou todas as medidas de segurança da minha conta.\n\nExcerto da publicação no Reddit ↗\nRegisto documentado\nUma alegação que foi guardada sobre o processo de recuperação ter ignorado as medidas de segurança da conta. A publicação guardada regista o que, segundo o autor, o serviço de apoio ao cliente lhe disse.\nExigência de responsabilização\nIdentifique quem autorizou a redefinição, os comprovativos de titularidade que foram aceites e o registo de acesso. A recuperação de conta faz parte dos controlos do sistema de segurança Valve.\nLer registo guardado →Abrir o Reddit ↗\nNo dossiê: Solicitar os registos subjacentes →Arquivo n.º 4,592 · compilação 2026-09-17\n\nSeis registos selecionados. As descrições do GitHub descrevem a compilação guardada. As publicações no Reddit preservam os relatos dos autores.\n\nDescarregue os seis álbuns ↓\n\nA compilação pesquisável contém 16,319 registos distintos: 393 registos no Trustpilot, 5,635 no Reddit, 2,395 no GitHub, 276 registos na Web e 7,620 na wiki. Vários registos podem referir-se ao mesmo evento. A exportação principal separada, com 40,448 linhas, tem um âmbito diferente.\n\nPesquisar no arquivo completo ↗ · Criar manifesto ↗ · Âmbito e contagens do conjunto de dados →\n\nApêndice E — Estudo de caso\nArchiSteamFarm e a cláusula de automatização\n\nUma ferramenta de código aberto para a aquisição de cartões, cujas próprias perguntas frequentes (FAQ) indicam que funciona em milhões de contas, o que contraria a cláusula do Acordo de Subscrição (§ 4.C) que proíbe a automatização. Os mecanismos — o que uma «fazenda» tem de comprar à Valve antes de poder produzir qualquer coisa, por que razão todas as formas de levantar fundos de um cartão violam a licença, o historial de aplicação das regras e quem modera a economia dos cartões — estão descritos na íntegra em Anexo V ↗.\n\nO Contrato de Assinante Steam, § 4.C, estipula:\n\n«Não é permitido utilizar qualquer tipo de scripts, bots, macros ou outros sistemas não controlados por seres humanos («Automação») para interagir com os Conteúdos e Serviços no Steam, de forma alguma.» — Steam Contrato de Assinante, § 4.C (em vigor) ↗ arquivado 2026-09-18 ↗\n\nValve faz cumprir esta cláusula. É muito eficaz nisso. As perguntas frequentes sobre ArchiSteamFarm (ASF) — uma ferramenta de código aberto que, segundo a própria documentação, funciona em mais de alguns milhões de contas Steam desde o seu primeiro lançamento, há mais de 11 anos — reproduz três Steam mensagens do apoio ao utilizador que baniram permanentemente os utilizadores que geriam redes de bots. Valve descobriu as redes, identificou-as e desativou-as. A questão relevante não é, portanto, se Valve consegue detetar a automação em grande escala.\n\nO site oficial do projeto ArchiSteamFarm Perguntas frequentes aborda diretamente o risco de uma proibição:\n\n«Isto é extremamente improvável, tendo em conta que o ASF está a ser utilizado em mais de alguns milhões de contas Steam, desde o seu primeiro lançamento, que ocorreu há mais de 11 anos — mas continua a ser uma possibilidade, independentemente da probabilidade real.»\n\n\"Valve reconhece claramente a existência dos «Steam ociosos», tal como aqui se afirma; por isso, se me perguntassem, tenho quase a certeza de que, se não estivessem de acordo com a sua existência, já teriam tomado medidas em vez de se limitarem a salientar que estes poderiam causar problemas no que diz respeito a VAC. A palavra-chave aqui é «jogos de inatividade» (idlers), por exemplo, o ASF, e não «jogos de inatividade».\"\n\n— ArchiSteamFarm Perguntas frequentes, JustArchiNET. Fonte: Wiki do GitHub ↗ · verificado literalmente 2026-09-22\n\nA mesma secção de perguntas frequentes responde à pergunta «Alguém foi banido por causa disso?» com Sim, e reproduz o que o Steam Support escreveu a três deles:\n\n1,000+ bots · banidos do comércio\n«Parece que esta conta foi utilizada para gerir uma rede de contas de bots. A utilização de bots constitui uma violação do Acordo de Assinante Steam.»\n\nMais de 170 bots · banidos permanentemente, Promoção de Inverno de 2017\n«Esta conta foi utilizada para a recolha ilegal de cartões colecionáveis no Steam, bem como para atividades relacionadas, não apenas comerciais. A conta foi bloqueada definitivamente e o Apoio ao Cliente Steam não pode prestar assistência adicional sobre esta questão.»\n\nMais de 120 bots · banidos permanentemente\n«Esta e outras contas foram utilizadas para sobrecarregar a nossa infraestrutura de rede, o que constitui uma violação das regras de conduta online Steam.»\n\n— Steam Mensagens de apoio reproduzidas na ArchiSteamFarm secção de perguntas frequentes (FAQ), na secção «Alguém foi banido por causa disso?». Fonte ↗ · verificado literalmente 2026-09-22\n\nColoca os dois registos lado a lado. Um utilizador privado com 1,000 bots de farming é identificado, informado de que «a utilização de bots constitui uma violação do Steam Acordo de Subscrição» e removido permanentemente. As plataformas comerciais incluídas neste dossiê gerem contas automatizadas Steam como atividade principal, numa escala muito superior, e autenticam-se através do próprio OpenID da Valve em cada início de sessão — e não foi publicado qualquer registo de aplicação de medidas por operador relativamente a nenhuma delas. A cláusula funciona. A questão é a quem se destina.\n\nA ASF não é acusada de nada aqui, e a sua interpretação da posição de Valve é da sua exclusiva responsabilidade — o seu autor afirma claramente que «a ASF não está autorizada por Valve». A ferramenta é aqui utilizada como um instrumento de medição: mostra que Valve deteta redes de bots, identifica-as por escrito e bane-as permanentemente. Valve pode encerrar a questão numa única frase, publicando quais as automações comerciais que autoriza e o registo, por operador, das medidas tomadas relativamente às restantes.\n\nComo a prática de «card farming» afeta as receitas da Valve\n\nAs cartas colecionáveis obtidas no jogo são vendidas no Mercado da Comunidade Steam, que cobra uma comissão total de cerca de 15% por cada venda concluída no Mercado; a conta tem de ter gasto $5.00 USD em Steam antes de poder receber qualquer cartão; e a obtenção de cartões requer a posse do jogo ou compras no jogo. Não é aqui estimada qualquer receita agregada — a escala operacional é indicada apenas tal como consta nas Perguntas Frequentes (FAQ) da ASF. As Perguntas Frequentes também registam Valve distinções \"Steam ociosos\" (coleção de cartas) de \"jogadores que ficam a perder tempo\"; consulte o Perguntas frequentes sobre a ASF ↗. As regras estão descritas na íntegra em Anexo V — a escala e a armadilha da utilização comercial.\n\nAssuntoArchiSteamFarm — obtenção automática de cartões\nEscala indicadaMilhões de contas (segundo as Perguntas Frequentes da ASF — o número exato de contas ativas não foi confirmado)\nContados, não citados10,880,610 entradas totais na API do próprio grupo Steam da ASF (5,360,499 sem restrições, conforme Steam mostra) — os «milhões» referidos nas Perguntas Frequentes não são uma história, mas sim um recenseamento. 88.97% não implicam qualquer tipo de Steam proibição. O censo completo das proibições ↗\nInformações divulgadas na própria documentação da ferramenta\nO ASF inicia sessão nas contas em modo sem interface gráfica e mantém os jogos em espera para a obtenção de cartas, sem iniciar o cliente Steam (conforme a documentação do projeto).\nA secção de perguntas frequentes argumenta que o Valve está ciente da existência dos «Steam ociosos» e que «se não se sentissem à vontade com eles, já teriam feito alguma coisa».\nNão foram registadas medidas de fiscalização específicas em mais de 11 anos (segundo as Perguntas Frequentes); as vendas com cartão resultantes no Community Market implicam uma comissão combinada de Steam, no valor de cerca de 15%.\nA secção de perguntas frequentes indica um limite máximo recomendado de dez contas por operador e atribui-o a Valve: «Esta recomendação baseia-se em diretrizes internas Valve, bem como nas nossas próprias sugestões.» A Valve não publicou qualquer diretriz desse tipo.\nLimite técnico, de acordo com as mesmas perguntas frequentes: «é possível executar até 100-200 bots com um único IP e uma única instância do ASF.»\nO tempo de jogo «falsificado» é registado pelo Valve — «normalmente é atualizado a cada 30 minutos, aproximadamente» — e o § 4.C enumera «a falsificação de estatísticas de jogo (por exemplo, vitórias ou derrotas inflacionadas, XP, tempo de jogo)» como um ato proibido.\nFontes\nWiki oficial de perguntas frequentes da JustArchi ASF ↗ ArchiSteamFarm repositório ↗ arquivado 2026-09-24 ↗\nA cláusula relativa à automatização é explícita; o FAQ da ASF afirma há anos que a ferramenta é utilizada em milhões de contas; não foram relatadas quaisquer medidas de fiscalização específicas contra a sua utilização. A discrepância entre a regra e a sua aplicação está documentada; a razão para tal não é aqui esclarecida.\nExposição completaA economia dos cartões: o processo, a escala, a licença e quem a regula ↗O que uma exploração agrícola tem de comprar à Valve antes de poder produzir um único cartão; as duas linhas do § 4.C que definem a «cultivação de cartões» pelos seus efeitos; por que razão todas as formas de resgatar um cartão violam a licença Valve, enquanto Valve cobra uma taxa à entrada; o registo de aplicação da lei, incluindo a onda de junho de 2025 VAC e o banimento em cadeia por número de telefone partilhado; e os Valve funcionários e moderadores da comunidade que foram encontrados a administrar os serviços de troca de cartões e da lista de banidos em torno de Steam.O recenseamento das proibiçõesNão perguntámos ao Valve qual era a dimensão da quinta. Contámo-la. ↗10,880,610 contas no total (limitadas e não limitadas) lidas do próprio grupo Steam do ArchiSteamFarm, ao qual o software adere automaticamente por predefinição na primeira vez que é iniciado, a menos que o utilizador desmarque a configuração de adesão ao grupo (abrangendo tanto as «fazendas de bots» comerciais como os jogadores regulares que mantiveram a configuração predefinida ativada). 88.97% não têm qualquer tipo de banimento Steam; dos 11% que o têm, 99.8% são banimentos comunitários meramente simbólicos que nunca impedem a realização de transações. Após verificação cruzada com SteamRep, 67.77% dos burlões listados ficam em liberdade assim que os banimentos anti-batota são postos de lado. Com repartições por data de registo, localização geográfica e tempo de permanência — a verdadeira escala, medida, não narrada.\n\nAppendix F — Working ledger\n\nRules ledger: clauses against recorded platforms\n\nEscolha uma regra; o registo apresenta as plataformas registadas associadas a essa regra, com o seu domínio principal, o servidor de autenticação declarado e o resultado guardado do Filtro de Links. Um site bloqueado, outro domínio para iniciar sessão: siga a regra até à rota que resta.\n\n175registos associados\na esta regra\n174 domínios primários0 Referências à C&D\nEXCERTO DA REGRA / SSA § 2.G\nUtilização comercial e cobrança na conta\n“…exploit the Content and Services or any of its parts for any commercial purpose, except as expressly permitted elsewhere in this Agreement (including any Subscription Terms or Rules of Use).”\nACOMPANHE OS REGISTOS\nRegisto da plataforma 175\nOs valores em escala são estimativas da fonte\n\n175 dos registos de «175»\n\nServiço / grupo principal\tDomínio principal / registo\tDomínio de autenticação observado / idade\tEscala / resposta registada\n\nCasino\n\tcsgoempire.com\n11.3 yearsRegistered 2015-06-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgoempirelogin4.com\n6.2 yearsRegistered 2020-07-20\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustreaper.com\n23.2 yearsRegistered 2003-06-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustreaper.com\n23.2 yearsRegistered 2003-06-24\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustly.com\n12.4 yearsRegistered 2014-05-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustly.com\n12.4 yearsRegistered 2014-05-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette Casino\n\tcsgofast.com\n11.5 yearsRegistered 2015-03-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsteam-login.authtofast.com\n83 daysRegistered 2026-06-30\nRDAP ↗ · authtofast.com (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tduelbits.com\n6.6 yearsRegistered 2020-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nswitchflips.com\n6.4 yearsRegistered 2020-04-21\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opener\n\tfarmskins.com\n10.5 yearsRegistered 2016-03-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsteam.kobal.cc\n9.7 yearsRegistered 2017-01-07\nRDAP ↗ · kobal.cc (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgoluck.com\n9.3 yearsRegistered 2017-05-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgoluck.com\n9.3 yearsRegistered 2017-05-18\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tinsane.gg\n7.5 yearsRegistered 2019-04-02\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.insane.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcs2skin.com\n3.5 yearsRegistered 2023-03-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncs2skin.com\n3.5 yearsRegistered 2023-03-06\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tjuice.gg\n7.9 yearsRegistered 2018-10-19\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nletmeinjuice.com\n2.4 yearsRegistered 2024-04-15\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tggdrop.com\n8.6 yearsRegistered 2018-02-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nggauth.com\n3.4 yearsRegistered 2023-05-03\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Casino\n\thowl.gg\n9.5 yearsRegistered 2017-03-16\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhowl.uno\n41 daysRegistered 2026-08-11\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tchicken.gg\n5.7 yearsRegistered 2021-01-11\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nchicken.gg\n5.7 yearsRegistered 2021-01-11\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgocasino.gg\n2.6 yearsRegistered 2024-02-17\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.csgocasino.gg\n2.6 yearsRegistered 2024-02-17\nWHOISFREAKS ↗ · csgocasino.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Casino\n\thunt.gg\n6.9 yearsRegistered 2019-11-04\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.hunt.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Battles\n\tcsbattle.com\n9.8 yearsRegistered 2016-12-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsbattle.com\n9.8 yearsRegistered 2016-12-10\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskinrave.gg\n3.1 yearsRegistered 2023-08-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinrave.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsdouble.gg\n261 daysRegistered 2026-01-03\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsdouble.gg\n261 daysRegistered 2026-01-03\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustchance.com\n8.0 yearsRegistered 2018-10-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhgfuihd.com\n7.6 yearsRegistered 2019-01-27\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Automation\n\tcobaltlab.tech\n3.5 yearsRegistered 2023-03-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncobaltauth.com\n1.7 yearsRegistered 2025-01-07\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\traided.gg\n171 daysRegistered 2026-04-03\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.raided.gg\n171 daysRegistered 2026-04-03\nIP2WHOIS ↗ · raided.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustneo.gg\n1.3 yearsRegistered 2025-06-20\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustneo.gg\n1.3 yearsRegistered 2025-06-20\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tsplits.gg\n3.7 yearsRegistered 2023-01-23\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsplits.gg\n3.7 yearsRegistered 2023-01-23\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Upgrader\n\tupgrader.pro\n1.2 yearsRegistered 2025-07-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nupgauth.space\n38 daysRegistered 2026-08-14\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskin.fans\n8.2 yearsRegistered 2018-07-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skinfans.com\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\thotpizza.one\n1.8 yearsRegistered 2024-12-07\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhotpizza.one\n1.8 yearsRegistered 2024-12-07\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tg4skins.com\n10.1 yearsRegistered 2016-08-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.g4s.to\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2royal.com\n4.1 yearsRegistered 2022-08-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ntf2auth.com\n5.2 yearsRegistered 2021-07-27\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2hunt.com\n8.7 yearsRegistered 2018-01-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrstspcl.com\n6.1 yearsRegistered 2020-08-08\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2.bet/coinflip\n8.4 yearsRegistered 2018-05-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ntf2.bet\n8.4 yearsRegistered 2018-05-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\topenstars.gg\n131 daysRegistered 2026-05-13\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nopenstars.gg\n131 daysRegistered 2026-05-13\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tskins.com\n25.1 yearsRegistered 2001-08-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skins.com\n25.1 yearsRegistered 2001-08-08\nRDAP ↗ · skins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\twhite.market\n9.6 yearsRegistered 2017-03-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwhite.market\n9.6 yearsRegistered 2017-03-01\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tmoon.market\n7.6 yearsRegistered 2019-02-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmoon.market\n7.6 yearsRegistered 2019-02-27\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tcsfloat.com\n5.2 yearsRegistered 2021-07-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgofloat.com\n11.0 yearsRegistered 2015-09-29\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tskin.land\n4.7 yearsRegistered 2022-01-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skin.land\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\thaloskins.com\n2.8 yearsRegistered 2023-12-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhaloskins.com\n2.8 yearsRegistered 2023-12-10\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCorporate Market\n\tbuff.163.com\n29.0 yearsRegistered 1997-09-15\nRDAP ↗ · 163.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\nbuff.163.com\n29.0 yearsRegistered 1997-09-15\nRDAP ↗ · 163.com (parent)\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\tmarket.csgo.com\n26.6 yearsRegistered 2000-02-07\nRDAP ↗ · csgo.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\ndota2.net\n14.9 yearsRegistered 2011-10-29\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRegulated Market\n\tskinport.com\n8.0 yearsRegistered 2018-09-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinport.app\n6.3 yearsRegistered 2020-06-20\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMarketplace/Swap\n\tskinflow.gg\n3.8 yearsRegistered 2022-11-26\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinflow.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tskin.place\n6.0 yearsRegistered 2020-09-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skin.place\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tskinsmonkey.com\n5.7 yearsRegistered 2021-01-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinsmonkey.com\n5.7 yearsRegistered 2021-01-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCorporate Market\n\tskinbaron.de\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinbaron.com\n10.7 yearsRegistered 2015-12-22\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Market\n\trust.tm\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\ndota2.net\n14.9 yearsRegistered 2011-10-29\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tpirateswap.com\n6.0 yearsRegistered 2020-09-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nlogin.pirateswap.com\n6.0 yearsRegistered 2020-09-22\nRDAP ↗ · pirateswap.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Marketplace\n\tmannco.store\n8.6 yearsRegistered 2018-03-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmannco.store\n8.6 yearsRegistered 2018-03-02\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tskinswap.com\n9.9 yearsRegistered 2016-11-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinswap.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\texeskins.com\n2.1 yearsRegistered 2024-08-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nexeskins.com\n2.1 yearsRegistered 2024-08-14\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tbalticskins.com\n153 daysRegistered 2026-04-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nbalticskins.com\n153 daysRegistered 2026-04-21\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tcs.trade\n8.9 yearsRegistered 2017-11-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncs.trade\n8.9 yearsRegistered 2017-11-14\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\trapidskins.com\n4.5 yearsRegistered 2022-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.rapidskins.com\n4.5 yearsRegistered 2022-03-11\nRDAP ↗ · rapidskins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\ttradeit.gg\n9.1 yearsRegistered 2017-08-21\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nconnect-tradeit.com\n4.6 yearsRegistered 2022-02-23\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\t49skins.com\n3.4 yearsRegistered 2023-04-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.49skins.com\n3.4 yearsRegistered 2023-04-19\nRDAP ↗ · 49skins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tskinvault.gg\n3.4 yearsRegistered 2023-05-06\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinvault.gg\n3.4 yearsRegistered 2023-05-06\nIP2WHOIS ↗ · skinvault.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Trading\n\taim.market\n3.3 yearsRegistered 2023-05-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\naim.market\n3.3 yearsRegistered 2023-05-22\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Sell Portal\n\tskinout.gg\n5.6 yearsRegistered 2021-02-27\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skinout.gg\n5.6 yearsRegistered 2021-02-27\nIP2WHOIS ↗ · skinout.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Trading\n\tntskins.com\n230 daysRegistered 2026-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nntskins.com\n230 daysRegistered 2026-02-03\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Portal\n\tgamerpay.gg\n6.0 yearsRegistered 2020-10-02\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ngamerpay.gg\n6.0 yearsRegistered 2020-10-02\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Scrap Swap\n\tscrap.tf\n14.0 yearsRegistered 2012-09-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nscrap.tf\n14.0 yearsRegistered 2012-09-03\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Cashout\n\tmarketplace.tf\n14.0 yearsRegistered 2012-09-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmarketplace.tf\n14.0 yearsRegistered 2012-09-19\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Cashout\n\tskins.cash\n10.5 yearsRegistered 2016-03-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinscash.live\n6.8 yearsRegistered 2019-12-05\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgo.net\n14.2 yearsRegistered 2012-07-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncn2.easylot.net\n10.0 yearsRegistered 2016-09-03\nRDAP ↗ · easylot.net (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCommunity Hub\n\tcybershoke.net\n6.8 yearsRegistered 2019-11-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.cybershoke.net\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMatchmaker Hub\n\tfastcup.net\n14.6 yearsRegistered 2012-02-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.fastcup.net\n14.6 yearsRegistered 2012-02-16\nRDAP ↗ · fastcup.net (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Analytics\n\tleetify.com\n7.6 yearsRegistered 2019-03-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nleetify.com\n7.6 yearsRegistered 2019-03-01\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Analytics\n\tscope.gg\n7.8 yearsRegistered 2018-12-10\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nscope.gg\n7.8 yearsRegistered 2018-12-10\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tools\n\ttradeupspy.com\n6.5 yearsRegistered 2020-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.tradeupspy.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMarketplace\n\tcs.deals\n9.8 yearsRegistered 2016-12-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.cs.deals\n9.8 yearsRegistered 2016-12-03\nRDAP ↗ · cs.deals (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Price DB\n\tpricempire.com\n6.6 yearsRegistered 2020-01-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\npricempire.com\n6.6 yearsRegistered 2020-01-30\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Blackmarket\n\tFSB Market\n7.2 yearsRegistered 2019-07-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nFSB Market\n7.2 yearsRegistered 2019-07-27\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nReady-Account Hub\n\tz2u.com\n26.9 yearsRegistered 1999-11-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwww.z2u.com\n26.9 yearsRegistered 1999-11-10\nRDAP ↗ · z2u.com (parent)\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Gambling\n\tcsgoroll.com\n11.6 yearsRegistered 2015-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwww.csgoroll.com\nRegistry date unavailableRegistry date unavailable\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\trollbit.com\n11.9 yearsRegistered 2014-11-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrbsnin.com\n3 daysRegistered 2026-09-18\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nLicenced Casino\n\t500.casino\n5.9 yearsRegistered 2020-11-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette/Slots\n\tcsgobig.com\n11.4 yearsRegistered 2015-04-12\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcasedrop.com\n14.8 yearsRegistered 2011-12-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\tbanditcamp.com\n12.2 yearsRegistered 2014-06-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tskinbox.com\n18.8 yearsRegistered 2007-12-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\ttastydrop.com\n6.1 yearsRegistered 2020-08-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette Casino\n\tcsgopolygon.gg\n6.5 yearsRegistered 2020-03-28\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tmagicdrop.ru\n10.3 yearsRegistered 2016-05-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nDice Casino\n\tcsdice.com\n3.8 yearsRegistered 2022-11-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUpgrader Casino\n\tskinodds.com\n1.2 yearsRegistered 2025-06-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgowin.com\n12.0 yearsRegistered 2014-09-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrash Casino\n\tcsgorun.net\n7.3 yearsRegistered 2019-06-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\topenskins.com\n3.6 yearsRegistered 2023-02-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Gambling\n\trustbet.com\n7.6 yearsRegistered 2019-02-07\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgomagic.com\n9.4 yearsRegistered 2017-05-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUpgrader/Contract\n\tcsgobounty.com\n11.5 yearsRegistered 2015-03-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tezskins.com\n27.5 yearsRegistered 1999-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\trustcases.com\n7.2 yearsRegistered 2019-06-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgoreaper.com\n11.1 yearsRegistered 2015-08-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgocases.com\n12.3 yearsRegistered 2014-06-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Upgrader\n\tcsgo-skins.com\n11.2 yearsRegistered 2015-07-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgonet.com\n8.8 yearsRegistered 2017-12-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\twtfskins.com\n9.0 yearsRegistered 2017-10-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Casino\n\tflamecases.com\n10.0 yearsRegistered 2016-09-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tgamedom.com\n11.7 yearsRegistered 2015-01-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Battles\n\tskin.club\n9.0 yearsRegistered 2017-09-04\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsc-auth.net\n7.5 yearsRegistered 2019-04-02\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tdaddyskins.com\n9.9 yearsRegistered 2016-10-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Gambling\n\trustix.gg\n1.7 yearsRegistered 2025-01-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Upgrade\n\tskins.club\n4.2 yearsRegistered 2022-07-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgohouse.org\n146 daysRegistered 2026-04-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskinrave.net\n216 daysRegistered 2026-02-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tbloodycase.gg\n19 daysRegistered 2026-09-02\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nClicker/Upgrade\n\tcsgoclicker.com\n8.3 yearsRegistered 2018-05-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustbet.gg\n4.0 yearsRegistered 2022-09-30\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcs-drop.com\n262 daysRegistered 2026-01-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\thellstore.net\n11.7 yearsRegistered 2015-01-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustloot.com\n354 daysRegistered 2025-10-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgo-case.com\n10.3 yearsRegistered 2016-05-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgogem.com\n9.9 yearsRegistered 2016-10-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\trainbet.com\n8.8 yearsRegistered 2017-11-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nservices.rainbet.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustclash.com\n5.4 yearsRegistered 2021-05-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrash Casino\n\t12cs.fail\n181 daysRegistered 2026-03-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\twww.tf2easy.com\n6.3 yearsRegistered 2020-06-02\nRDAP ↗ · tf2easy.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2blaze.com\n7.6 yearsRegistered 2019-01-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tshuffle.com\n30.1 yearsRegistered 1996-07-31\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tbuff.market\n5.9 yearsRegistered 2020-10-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tavan.market\n8.3 yearsRegistered 2018-05-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Engine\n\tcs.money\n11.0 yearsRegistered 2015-09-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.dota.trade\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tuuskins.com\n2.6 yearsRegistered 2024-01-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Market\n\tyoupin898.com\n6.1 yearsRegistered 2020-08-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tc5game.com\n10.5 yearsRegistered 2016-03-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\twaxpeer.com\n7.3 yearsRegistered 2019-05-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwaxpeer.com\n7.3 yearsRegistered 2019-05-20\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBot Trading\n\tcs.money\n11.0 yearsRegistered 2015-09-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.dota.trade\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUS Marketplace\n\tdmarket.com\n30.2 yearsRegistered 1996-07-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nOfficial Market\n\tsteamcommunity.com/market\n20.3 yearsRegistered 2006-05-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNot an external login site2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Platform\n\tlootfarm.com\n11.9 yearsRegistered 2014-10-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Market\n\trustskins.com\n7.6 yearsRegistered 2019-01-31\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tkrakatoa.com\n26.4 yearsRegistered 2000-05-15\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\tshadowpay.com\n10.1 yearsRegistered 2016-08-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nChinese Powerhouse\n\tigxe.cn\n15.0 yearsRegistered 2011-09-06\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAutomated Swap\n\tswap.gg\n9.6 yearsRegistered 2017-01-29\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCash-out Portal\n\tbitskins.com\n11.2 yearsRegistered 2015-07-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Automation\n\ttf2mart.com\n1.1 yearsRegistered 2025-08-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Auctions\n\tskinbid.com\n10.2 yearsRegistered 2016-06-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Rental\n\tlootbear.com\n8.7 yearsRegistered 2018-01-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Valuation\n\tbackpack.tf\n14.4 yearsRegistered 2012-05-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Botnet\n\tstntrading.eu\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Cashout\n\tskinwallet.com\n18.0 yearsRegistered 2008-09-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nDota 2 Market\n\tdota2market.com\n12.2 yearsRegistered 2014-07-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nServer Network\n\txplay.gg\n5.3 yearsRegistered 2021-06-13\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMatchmaking Portal\n\tesportal.com\n26.8 yearsRegistered 1999-12-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nLATAM Hub\n\tgamersclub.com.br\n11.2 yearsRegistered 2015-06-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tools\n\tepidemic.gg\n4.9 yearsRegistered 2021-11-03\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tcs2stash.com\n3.5 yearsRegistered 2023-03-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tcsgoskins.gg\n6.8 yearsRegistered 2019-12-21\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tsteamanalyst.com\n12.6 yearsRegistered 2014-02-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Exchange\n\tsteamcardexchange.net\n13.3 yearsRegistered 2013-05-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tracker\n\tdotabuff.com\n14.2 yearsRegistered 2012-06-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tracker\n\ttracker.gg\n8.9 yearsRegistered 2017-10-12\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Exchange\n\tfunpay.com\n17.0 yearsRegistered 2009-09-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nGrey Market\n\tplayerauctions.com\n26.3 yearsRegistered 2000-06-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Portal\n\teldorado.gg\n8.0 yearsRegistered 2018-09-12\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Key Market\n\tg2a.com\n24.8 yearsRegistered 2001-12-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Key Market\n\tkinguin.net\n16.8 yearsRegistered 2009-12-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nVirtual Services\n\tg2g.com\n31.1 yearsRegistered 1995-08-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Broker\n\tplayerup.com\n19.3 yearsRegistered 2007-05-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfhub.net\n2.7 yearsRegistered 2023-12-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfaccounts.com\n5.3 yearsRegistered 2021-05-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Shop\n\tbuycsgorank.com\n6.2 yearsRegistered 2020-07-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tcsgosmurfkings.com\n9.3 yearsRegistered 2017-06-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfstore.co\n8.6 yearsRegistered 2018-03-03\nWHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlvlup.com\n9.9 yearsRegistered 2016-11-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlevels.com\n10.6 yearsRegistered 2016-02-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tlevelsteam.com\n79 daysRegistered 2026-07-04\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlevelu.com\n6.0 yearsRegistered 2020-09-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\teloking.com\n12.2 yearsRegistered 2014-07-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\tboosteria.org\n11.9 yearsRegistered 2014-10-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tovergear.com\n14.4 yearsRegistered 2012-04-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tblazingboost.com\n14.2 yearsRegistered 2012-06-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\tdota2boost.com\n2.9 yearsRegistered 2023-10-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tbuyboost.com\n22.4 yearsRegistered 2004-04-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\nA argumentação da investigaçãoRegra selecionada / análise e comentário+\nÓnus da prova\n\nA investigação põe em causa a discrepância entre as restrições à utilização comercial e os serviços aqui registados. Classifique cada atividade e verifique se existe alguma autorização expressa antes de a considerar uma violação contratual. As taxas do Mercado Comunitário não se aplicam a todas as transações comerciais externas.\n\nO que é — e o que não é — um registo marcado\n\nUm registo é assinalado quando o dossiê contém uma observação datada que faz com que a plataforma se enquadre, à primeira vista, na cláusula em questão. Uma assinalação não constitui uma infração confirmada, e não foi apresentada qualquer autorização expressa Valve no registo para qualquer plataforma aqui listada. Quando uma plataforma detém uma autorização, a sua publicação resolve a entrada.\n\nFontes e metodologiaEstimativas, definições e âmbito+\n\nOs números acima referem-se à regra selecionada. Os tipos de registo agrupam cada plataforma uma vez; as etiquetas completas aparecem nos detalhes da plataforma. A pesquisa e os filtros aplicam-se dentro dessa regra. As datas de registo provêm do instantâneo guardado em RDAP / WHOIS. Os subdomínios utilizam a data de criação do domínio pai. A antiguidade, por si só, não comprova a operação contínua nem uma rota de autenticação. Os nomes de anfitrião de autenticação atuais provêm de pedidos OpenID guardados, com um carimbo de data/hora UTC; as verificações não resolvidas não reutilizam rótulos antigos. O observador pára antes do início de sessão em Steam e não testa o estado do filtro de ligações em Steam. Descarregar observações da rota ↗ Descarregar os resultados do registo ↗\n\nExplora o arquivo de código-fonte ↗\nApêndice G — De um modelo de recusa ao registo subjacente\nGuia prático sobre o DSAR: solicitar as provas\n\nRecorra ao artigo 15.º do RGPD para solicitar dados pessoais relacionados com a criação de chaves API, a recuperação de contas e o acesso ao apoio ao utilizador. Um registo conservado permite verificar quem iniciou uma ação e em que se baseou a plataforma.\n\n01\nGuarde a sua cronologia.\n\nGuarde os avisos da conta, os bilhetes, os IDs das transações e as datas em UTC. Proteja a conta e analise as opções de recuperação aplicáveis ao jogo e à transação.\n\nSteam Informações sobre proteção comercial ↗\n02\nSolicite os seus dados arquivados.\n\nSolicite registos de data e hora, endereços IP de origem, eventos importantes do ciclo de vida das chaves, confirmações de segurança e ações de recuperação relacionadas com a conta. Inclua eventos de acesso ao serviço de apoio e os destinatários, sempre que esses dados sejam do seu interesse.\n\n03\nGuarde o comprovativo de entrega.\n\nUtilize o canal de contacto para questões de privacidade de Valve. O prazo normal de resposta é de um mês; qualquer prorrogação necessária até um máximo de mais dois meses deve ser justificada no decurso desse primeiro mês.\n\nValve via de contacto para questões de privacidade ↗ arquivado 2026-09-21 ↗\n04\nCompare a resposta.\n\nConcilie os registos com a sua cronologia. Pergunte quais são os motivos das omissões e, se necessário, recorra à via de reclamação junto da autoridade de supervisão. Guarde a resposta exatamente tal como a recebeu.\n\nÂmbito de aplicação / Artigo 15.º\n\nO direito de acesso abrange os dados pessoais conservados, incluindo os dados contidos nos registos. Não garante o acesso a todos os documentos internos, registos reconstituídos ou dados não expurgados relativos a terceiros. Solicite uma cópia legível e a justificação de qualquer restrição.\n\nOrientações do EDPB em matéria de acesso, §§ 2, 4–6 ↗ · Artigos 12.º, 15.º e 77.º do RGPD ↗ arquivado 2026-09-20 ↗\n\nPedido de acesso aos dados pessoaisRGPD / Artigo 15.º\nSegurança da conta e registos de acesso\n\nSubstitua os campos entre parênteses antes de enviar.\n\nTo: Valve Privacy Team\nSubject: Article 15 GDPR request — account security records\n\nAccount / SteamID: [YOUR ACCOUNT IDENTIFIER]\nRelevant period (UTC): [START] to [END]\nRelated support tickets: [TICKET REFERENCES]\n\nI request a copy of the personal data concerning me that you retain for this period, including:\n\n1. API-key registration, confirmation, use and revocation events, with available timestamps, source IP addresses, registered domains, device or user-agent information and non-secret key identifiers.\n\n2. Recorded account-recovery actions, password/email/phone changes, Steam Guard removals or resets, confirmation events and the account-related evidence relied on to authorize those actions.\n\n3. Personal data in support-access and administrative-action logs concerning my account, including available dates, purposes, actions and the support entity involved, subject to applicable rights of others.\n\n4. Account-related records used to determine any sanction, and available records of my complaints, reviews and responses.\n\nPlease also provide the applicable processing purposes, categories, recipients, retention periods or criteria, and available information about sources where data were not obtained from me.\n\nWhere processing relies on my consent, please provide the retained record of the consent relied upon and the wording presented at that time.\n\nPlease provide an intelligible electronic copy with time zones and field definitions. Please do not include active credentials or secret tokens. If any requested data are not held, please say so. For any withheld data, please identify the scope and legal basis of the restriction and provide the remainder.\n\nPlease acknowledge receipt and respond within the applicable Article 12 period, explaining any necessary extension. I also ask you to preserve relevant existing records while this request is handled.\n\nName: [YOUR NAME]\nDate: [DATE]\nO que um endereço IP de um centro de dados pode permitir\nUma discrepância constitui um indício que deve ser investigado.\n\nUm pedido de chave API proveniente da rede de um centro de dados, tal como no exemplo do fornecedor de alojamento web referido nesta investigação, pode ser relevante quando comparado com registos de início de sessão, confirmações e a cronologia do utilizador. Um endereço IP, por si só, não identifica o autor nem contorna automaticamente todas as defesas. A prova de que um autor mal-intencionado forneceu o consentimento registado pode pôr em causa a validade desse consentimento; outras bases jurídicas e questões de responsabilidade exigem uma análise separada.\n\nVer a denúncia arquivada relativa à proibição e ao RGPD →\nApêndice H — Análise do arquivo do Wayback Machine · estatísticas de suporte publicadas\nVolume de assistência. Tempos de resposta publicados.\nLimites de contexto e de fonte\n\nA Valve publica estatísticas diárias de apoio em store.steampowered.com/stats/support. Os arquivos do Wayback Machine preservam instantâneos históricos desta página entre 2018 e 2026. O rácio entre o volume e o número de colaboradores sugerido por estes números não é compatível com a revisão humana de cada pedido nos tempos de resposta publicados.\n\nCompare os dados de apoio arquivados de Valve nas várias instantâneas guardadas. A metodologia explica o que esses dados podem e não podem medir.\n\nVolume em função do tempo de resposta publicado (2018 → 2026)\nDuas filas num balcão de apoio, conforme se pode ver em 21 capturas de ecrã arquivadas.\n\nValve publica os números relativos ao apoio ao vivo em store.steampowered.com/stats/support. Cada valor abaixo corresponde ao próprio limite inferior Valve tal como constava nessa página no dia em que o Internet Archive a capturou — não se trata de uma estimativa nossa. Ambas as séries representam a mesma medida na mesma unidade, pelo que devem figurar num único eixo e podem ser comparadas diretamente entre si.\n\nPedidos de reembolso — dinheiro Valve está em posse deSegurança e recuperação da conta — a conta que perdeu\n0 h\n2 h\n4 h\n6 h\n8 h\n10 h\nno captures · 38 months\n2019\n2020\n2021\n2022\n2023\n2024\n2025\n2026\n8 h 44 m\naccount recovery\n52 m\nrefunds\n15 m — one capture only\n49–55 minO limite mínimo do reembolso em cada captura, de fevereiro de 2018 a agosto de 2026. Ao longo de oito anos e meio, varia em menos de seis minutos, enquanto o volume diário de reembolsos varia num fator de nove.\n2,4 h → 8,7 hO limite inferior da recuperação de contas situa-se em cerca de 2,4 horas em todas as recolhas até dezembro de 2022, com exceção de uma. Nas três recolhas de 2026, Valve apresenta valores de 10,9 h, 5,8 h e 8,7 h.\n×2,8 → ×13Quão mais lenta é a recuperação em comparação com os reembolsos, segundo os próprios dados publicados por Valve. Mantém-se estável durante cinco anos, depois o fosso aumenta — a fila que ficou mais lenta é aquela em que é o utilizador, e não Valve, que fica a arcar com os custos.\n\nFonte: 21 capturas do Wayback Machine de store.steampowered.com/stats/support, 2018-02-03 a 2026-08-10; extração em VALVE_EVIDENCE_PACK/databases/steam_support_stats_history.json. Observe os limites nas figuras: o gráfico representa o inferior limite do intervalo de Valve impressões. O limite superior publicado é pior em ambas as linhas — os reembolsos variaram entre 1,5 horas e 1,5 dias, e a recuperação entre 7,0 horas e 3,6 dias. Duas capturas foram arquivadas numa edição localizada da mesma página Valve — 2018-11-03 em checo, 2020-03-25 em francês — e estão assinaladas com (cs) e (fr) na tabela; os seus valores aparecem aqui com as unidades de medida traduzidas e os números tal como foram publicados, e as cadeias de texto originais são mantidas no ficheiro de extração. Cada captura publicou um tempo de resposta para ambas as filas, e nenhum ponto em nenhuma das linhas foi interpolado. O único valor de recuperação de 15 minutos, 2020-10-21, está assinalado no gráfico e foi mantido: aparece apenas numa captura e nenhuma outra captura se encontra dentro de uma ordem de grandeza desse valor. Não existe qualquer registo entre 2022-12-08 e 2026-02-01; essa lacuna de 38 meses no registo está sombreada e nada é traçado sobre ela. Estes valores descrevem os tempos de resposta publicados. Não mostram o que acontece no interior de um ticket, e o Valve não publicou qualquer número de colaboradores com base no qual os se possa interpretar.\n\nAbrir cada captura como uma tabela\nTodas as capturas arquivadas, tal como foram publicadas\nCaptura\tReembolsos / dia\tResposta relativa ao reembolso\tRecuperação / dia\tResposta de recuperação\n2018-02-03\t98,788\t50,12 minutos a 1,52 horas\t25,662\t2,51 horas a 1,80 dias\n2018-05-07\t60,494\t53,83 minutos a 1,47 dias\t24,226\t2,45 horas a 2,22 dias\n2018-08-02\t69,084\t50,27 minutos a 1,59 horas\t28,953\t2,44 horas a 22,17 horas\n2018-11-03 (cs)\t63,410\t49,28 minutos a 1,54 horas\t33,910\t2,42 horas a 1,31 dias\n2019-02-01\t76,305\t50,13 minutos a 1,52 horas\t35,164\t2,44 horas a 2,04 dias\n2019-05-18\t78,951\t51,03 minutos a 3,12 horas\t27,514\t2,46 horas a 20,39 horas\n2019-09-07\t78,941\t50,65 minutos a 1,66 horas\t28,812\t2,42 horas a 13,59 horas\n2019-12-13\t69,589\t50,77 minutos a 1,55 horas\t25,322\t2,45 horas a 1,13 dias\n2020-03-25 (fr)\t139,278\t49,45 minutos a 1,53 horas\t32,302\t2,48 horas a 3,62 dias\n2020-06-26\t278,504\t48,98 minutos a 2,29 horas\t20,343\t2,39 horas a 6,99 horas\n2020-10-21\t107,633\t50,80 minutos a 1,54 horas\t20,688\t15,33 minutos a 8,62 horas\n2021-03-20\t158,956\t50,80 minutos a 1,64 horas\t25,760\t2,34 horas a 11,62 horas\n2021-06-26\t547,907\t51,93 minutos a 6,73 horas\t29,728\t2,40 horas a 15,63 horas\n2021-10-10\t170,103\t51,88 minutos a 3,25 horas\t23,989\t2,39 horas a 13,05 horas\n2022-01-31\t354,386\t53,65 minutos a 8,09 horas\t24,391\t2,42 horas a 15,29 horas\n2022-05-09\t172,555\t51,83 minutos a 1,65 horas\t23,289\t2,41 horas a 16,90 horas\n2022-09-05\t153,453\t53,67 minutos a 4,15 horas\t23,594\t2,45 horas a 1,22 dias\n2022-12-08\t181,075\t54,83 minutos a 6,67 horas\t27,111\t2,46 horas a 18,89 horas\n2026-02-01\t317,762\t50,30 minutos a 1,52 horas\t47,197\tDas 10h91 às 21h30\n2026-05-09\t246,776\t50,12 minutos a 1,52 horas\t35,264\t5,81 horas a 15,60 horas\n2026-08-10\t373,244\t52,05 minutos a 2,07 horas\t45,319\t8,73 horas a 16,52 horas\nOBSERVAÇÃO PRINCIPAL:\nDe um lado ao outro 21 capturas do Wayback entre 2018-02-03 e 2026-08-10, os pedidos de reembolso diários variaram entre 60,494 (maio de 2018) até 547,907 (Junho de 2021) — a Spread de 9,1×. O valor para 2026 é 373,244 (+278% em relação aos dados de fevereiro de 2018).\nAo longo desses mesmos nove anos, o limite mínimo publicado para o tempo de resposta aos pedidos de reembolso nunca saiu de um 49–55 minutos faixa: um movimento total inferior a seis minutos, enquanto a carga de trabalho subjacente aumentou nove vezes.\nSe uma pessoa lesse cada bilhete durante apenas 5 segundos, o processamento de 373,244 bilhetes por dia (valor atual) ocuparia 22 agentes a trabalhar 24 horas por dia, 7 dias por semana apenas para as abrir e fechar; no pico (547,907, junho de 2021), esse valor sobe para 32.\nSe o tempo de resposta publicado refletisse o tempo de tratamento por pedido (~52 min/pedido), o número de funcionários necessários para atender simultaneamente estaria na ordem dos 13,500 agentes ao volume atual e ~20,000 no pico. Não foi encontrado qualquer dado de referência relativo ao número de colaboradores de apoio de Valve; não se considera aqui qualquer valor.\nO que se segue: o rácio entre o volume e o número de colaboradores não é compatível com uma revisão humana de cada pedido, tendo em conta os tempos de resposta publicados. Os números são compatíveis com uma primeira análise amplamente automatizada; a proporção de pedidos que é sujeita a revisão humana não é divulgada.\nPor que é que isto é importante para a conformidade com o RGPD\n\nO artigo 22.º do RGPD proíbe a tomada de decisões individuais exclusivamente automatizadas que produzam efeitos jurídicos significativos, sem prever o direito a uma revisão humana, mediante pedido. Se as decisões de apoio do Steam (encerramento de tickets, ações relativas a contas, recusa de pedidos de dados) forem tomadas inteiramente por scripts automatizados, cada uma dessas decisões que «afete significativamente» o utilizador poderá violar o artigo 22.º.\n\nBilhete HT-2YBP-F7JP-D4VB (Secção 18) foi encerrado ao fim de três dias com um encaminhamento padrão e sem qualquer referência ao fundamento jurídico citado. Não é possível determinar, a partir do registo, se alguém o analisou; essa é uma questão que a autoridade de controlo pode colocar a Valve nos termos do artigo 22.º e do artigo 15.º, n.º 1, alínea h).\n\nFonte: instantâneos do Wayback Machine de store.steampowered.com/stats/support (2018-02-03, 2021-06-26, 2026-08-10) — dados extraídos para VALVE_EVIDENCE_PACK/databases/steam_support_stats_history.json (21 instantâneos, 2018–2026). Nota: o tempo de resposta de «~52 min» corresponde ao limite inferior da categoria de reembolso; o tempo de resposta relativo à segurança da conta variou entre 2,4 e 16,5 horas nas mesmas capturas. 2021-06-26 representa o pico histórico (547,907 pedidos de reembolso), não um ponto médio monotónico — o volume aumentou cerca de 6 vezes entre 2020 e 2021, tendo depois diminuído parcialmente antes de recuperar para 373 mil em 2026.\nApêndice I — Âmbito do conjunto de dados · contagens que podem ser reproduzidas\nConte os registos. Verifique o âmbito.\nContexto e limites da fonte\n\nConte os registos e, em seguida, verifique as afirmações: todos os números que se seguem podem ser recalculados a partir dos ficheiros publicados.\n\nAnalise os conjuntos de dados subjacentes, reproduza as contagens e distinga as linhas de origem dos incidentes únicos.\n\nO ficheiro CSV principal contém 40,448 linhas. Destes, 36,516 provêm do feed de phishing do Discord-AntiScam. Os restantes 3,932 As linhas abrangem o GitHub, revisões, resultados de pesquisa, conteúdos de fóruns e outras fontes, proporcionando um índice abrangente dos tópicos abordados pela comunidade e dos relatórios de segurança.\n\nNesse ficheiro CSV, 1,690 linhas estão classificadas sob o rótulo de coleção «Vulnerabilidades de segurança sem correção», representando problemas históricos dos utilizadores e divulgações de vulnerabilidades. O acompanhamento destes relatórios implica a análise da cronologia específica de compilação de cada thread e do histórico público de correções.\n\nO arquivo pesquisável de registos 16,319 é uma compilação separada e selecionada, com o seu próprio manifesto, concebida para a exploração local precisa de reclamações específicas dos utilizadores e de relatórios de incidentes.\n\nPara criar uma pista de auditoria fiável, cada registo comunicado pelo utilizador deve ser verificado em relação aos cronogramas de compilação documentados e aos registos históricos de correções.\n\nOs registos da coleção da Parte II, separados 231,829 IDs de anúncios únicos, incluindo 33,509 na categoria de registo automatizado e 198,320 assinaladas como transferências não verificadas. O SHA-256 do ficheiro de entrada corresponde à medição preservada. Estas contagens descrevem tentativas de listagem e transferências observadas, em vez de valores de transações finalizadas ou totais de roubos verificados, o que destaca a necessidade de registos primários da plataforma para medir o impacto económico exato. Listar medidas e hashes ↗\n\nCSV avançado ↗ · Manifesto do arquivo pesquisável ↗ · Verificar registos de origem ↗\n\nApêndice J — Sobre esta investigação\nValve não publica qualquer registo de medidas coercivas. Construímos um.\n\nIndependente. Não comercial. Criado exclusivamente a partir de dados públicos. Apresentado às entidades reguladoras.\n\n88.97%frota de veículos autónomos não afetada — sem qualquer tipo de proibição\n67.77%dos 51,732 burlões condenados que ficam em liberdade\n$26.8M+limite mínimo de despesas em lojas por frota não limitada\n3.6%domínios de jogos de azar bloqueados pelo Filtro de Links do Valve's\n8 anosde incidentes de segurança registados\n\nO que é isto. Um dossiê forense sobre a plataforma Steam da Valve Corporation — o seu historial de aplicação da lei, a sua economia baseada na «card-farming», o seu quadro jurídico e a infraestrutura de autenticação que os operadores de jogos de azar utilizam através do próprio relé OpenID da Steam. Todos os dados são reprodutíveis a partir de duas fontes: a própria API pública da Valve e os conjuntos de dados publicados a acompanhar esta investigação.\n\nA quem se destina. Autoridades reguladoras com jurisdição sobre Valve — a autoridade de supervisão do RGPD para os Países Baixos, a FinCEN, a SEC, o Coordenador de Serviços Digitais da DSA, a UOKiK e qualquer entidade responsável pela aplicação da lei que investigue fluxos financeiros associados a Steam. Também para jornalistas, investigadores e todos os utilizadores que tenham sofrido o bloqueio permanente da conta, a recusa de um reembolso ou o roubo de inventário e a quem tenha sido dito que não há possibilidade de recurso.\n\nA única exigência. Valve mantém estes dados com total fidelidade — incluindo os motivos da proibição, o espaço de identificação completo e em tempo real. É capaz de executar todas as consultas contidas neste dossiê em segundos e optou por não publicar nada disso. A questão que se coloca a qualquer autoridade competente é simples: por que não?\n\nO que os autores não afirmam. Não foi concluído qualquer início de sessão no Steam em nenhuma plataforma de terceiros durante este trabalho. Um URL OpenID fornecido define os parâmetros do pedido, não um início de sessão concluído. Um domínio registável distinto não constitui, por si só, prova de evasão. As datas de registo representam limites mínimos quanto ao momento em que um host poderia ter aparecido pela primeira vez numa solicitação OpenID; não comprovam uma utilização contínua. Os autores não afirmam o que Valve sabia ou pretendia: todas as afirmações sobre Valve estão associadas a um documento público datado ou a uma observação datada. Nos casos em que uma alegação não pôde ser fundamentada num documento de referência, foi removida.\n\nQuem somos\n\nPhishDestroy — investigadores independentes. Sem qualquer ligação à Valve Corporation ou a qualquer plataforma aqui mencionada. Foi utilizada uma conta Steam exclusivamente para documentar o pedido ao abrigo do RGPD referido na Secção 18.\n\nAviso legal\n\nInvestigação não comercial, descentralizada e de interesse público. Todos os dados são fornecidos «tal como estão», sem qualquer garantia. Esta publicação não constitui uma decisão judicial.\n\nDOMÍNIO PÚBLICO\nLicenciamento\n\nTodos os direitos cedidos à humanidade. Reproduzir, adaptar, publicar — não é necessária a atribuição. Acesso na região abrangida pelo OFAC: proibido. Licença completa e aviso legal →",
        "headings": [
          {
            "level": 2,
            "id": "briefing-heading",
            "text": "A regra. O recorde. As questões por responder."
          },
          {
            "level": 2,
            "id": null,
            "text": "Carta aberta à Comissão de Jogos de Azar do Estado de Washington"
          },
          {
            "level": 3,
            "id": "wsgc-public-address-title",
            "text": "Dez dias transformaram-se em dez anos.Reabra o registo."
          },
          {
            "level": 2,
            "id": null,
            "text": "O site está bloqueado. A rota de início de sessão não está."
          },
          {
            "level": 3,
            "id": null,
            "text": "Figura 3.1 — As duas rotas, representadas graficamente."
          },
          {
            "level": 3,
            "id": null,
            "text": "A armadilha do panorama geral: o filtro de links é apenas uma fachada de conformidade, não um escudo"
          },
          {
            "level": 3,
            "id": null,
            "text": "Um domínio principal bloqueado, em conjunto com um host de autenticação desbloqueado, deixa a rota de início de sessão aberta — e esta permanece aberta durante anos."
          },
          {
            "level": 3,
            "id": null,
            "text": "Contexto: O que é o Steam e por que é importante neste contexto"
          },
          {
            "level": 3,
            "id": null,
            "text": "O que o Valve fez: O bloqueio de domínios"
          },
          {
            "level": 3,
            "id": null,
            "text": "O que é um domínio proxy"
          },
          {
            "level": 3,
            "id": null,
            "text": "O ponto crítico: o host de autenticação é enviado para Steam em todas as solicitações"
          },
          {
            "level": 3,
            "id": null,
            "text": "O que isto demonstra"
          },
          {
            "level": 3,
            "id": null,
            "text": "No interior de Steam, a lista de Valve é a única lista."
          },
          {
            "level": 3,
            "id": null,
            "text": "Contornar a proteção do filtro de ligações"
          },
          {
            "level": 3,
            "id": null,
            "text": "O navegador Big Picture divulga cookies de início de sessão e revela informações confidenciais (o que pode levar à apropriação de contas)"
          },
          {
            "level": 3,
            "id": null,
            "text": "O que isto significa para um menor que tenha um antivírus instalado"
          },
          {
            "level": 3,
            "id": null,
            "text": "A idade do domínio.Data da observação."
          },
          {
            "level": 2,
            "id": null,
            "text": "Um ponto final foi encerrado. O rastreio público perdeu uma chave."
          },
          {
            "level": 3,
            "id": null,
            "text": "A Era Pré-Apagão"
          },
          {
            "level": 3,
            "id": null,
            "text": "Após a alteração"
          },
          {
            "level": 2,
            "id": null,
            "text": "Uma sessão. Mais acesso do que o utilizador percebe."
          },
          {
            "level": 3,
            "id": null,
            "text": "1. Autenticação reforçada insuficiente"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. Ausência do princípio do privilégio mínimo"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. Gestão de sessões com falhas"
          },
          {
            "level": 3,
            "id": null,
            "text": "4. O bloqueio de hosts de autenticação ao nível do domínio era tecnicamente viável"
          },
          {
            "level": 3,
            "id": "integration-paradox-title",
            "text": "O Valve compila de acordo com estas regras todos os dias. Aqui, não conseguiu compilar de acordo com elas."
          },
          {
            "level": 4,
            "id": null,
            "text": "Âmbitos detalhados do GitHub vs Valve Steam API Web"
          },
          {
            "level": 2,
            "id": null,
            "text": "Simulador Interativo de Explorações e Desvio de Controlo"
          },
          {
            "level": 2,
            "id": null,
            "text": "Os pontos finais subjacentes à sequência."
          },
          {
            "level": 2,
            "id": null,
            "text": "Uma caixa assinalada. De quem é essa ação?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Como o Valve conseguiu finalmente neutralizar a «substituição comercial» — e por que razão foram necessários 7 anos de soluções alternativas"
          },
          {
            "level": 4,
            "id": null,
            "text": "Tempo de espera para avatar e nome (fevereiro de 2024)"
          },
          {
            "level": 4,
            "id": null,
            "text": "Inversão de tendência de 7 dias no CS2 (julho de 2025)"
          },
          {
            "level": 4,
            "id": null,
            "text": "Notificação push obrigatória para a API (dezembro de 2023)"
          },
          {
            "level": 4,
            "id": null,
            "text": "Banners com a data de criação e o nome da conta (2022–2024)"
          },
          {
            "level": 2,
            "id": null,
            "text": "O seu regulamento. As plataformas registadas."
          },
          {
            "level": 3,
            "id": "enforcement-focus-title",
            "text": "Um único conjunto de regras. Aplicação desigual."
          },
          {
            "level": 4,
            "id": null,
            "text": "Automação"
          },
          {
            "level": 4,
            "id": null,
            "text": "Utilização comercial"
          },
          {
            "level": 4,
            "id": null,
            "text": "VPN e ocultação da localização"
          },
          {
            "level": 4,
            "id": null,
            "text": "Ocultação de links"
          },
          {
            "level": 4,
            "id": null,
            "text": "Quem analisa a decisão quando o apoio encerra o processo?"
          },
          {
            "level": 2,
            "id": null,
            "text": "Uma API de automatização. Uma regra contra a automatização."
          },
          {
            "level": 3,
            "id": null,
            "text": "A falácia do «desenvolvedor de jogos»"
          },
          {
            "level": 4,
            "id": null,
            "text": "A contradição da automatização"
          },
          {
            "level": 4,
            "id": null,
            "text": "Uma posição do lado do servidor no fluxo comercial"
          },
          {
            "level": 2,
            "id": null,
            "text": "Foram exigidos dez dias. Dez anos para prestar contas."
          },
          {
            "level": 3,
            "id": "letter-company",
            "text": "VALVE CORPORATION"
          },
          {
            "level": 3,
            "id": null,
            "text": "Dez dias.E depois?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Siga o anfitrião de retorno indicado."
          },
          {
            "level": 3,
            "id": "washington-record-heading",
            "text": "Dois prazos. Uma norma de aplicação sem resposta."
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve concede aos sites de jogos de azar um prazo de 10 dias"
          },
          {
            "level": 4,
            "id": null,
            "text": "Washington pressiona Valve"
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve rejeita a acusação"
          },
          {
            "level": 4,
            "id": null,
            "text": "As rotas observadas em setembro de 2026"
          },
          {
            "level": 4,
            "id": null,
            "text": "Dezoito meses após a resposta da Valve, a entidade reguladora continuava a considerá-lo uma intenção."
          },
          {
            "level": 3,
            "id": null,
            "text": "A Década do Aviso Prévio de 10 Dias: Auditoria Forense de Sobrevivência dos 23 Locais Identificados"
          },
          {
            "level": 4,
            "id": null,
            "text": "Desde avisos com 10 dias de antecedência até conglomerados offshore: o volume de negócios de vários mil milhões de dólares"
          },
          {
            "level": 2,
            "id": null,
            "text": "O nome do anfitrião já consta no pedido."
          },
          {
            "level": 3,
            "id": null,
            "text": "Precedentes documentados e relatados"
          },
          {
            "level": 3,
            "id": null,
            "text": "O que a data de registo indica e o que não indica"
          },
          {
            "level": 3,
            "id": null,
            "text": "Auditoria comparativa: normas de conformidade da API"
          },
          {
            "level": 2,
            "id": "market-thesis-heading",
            "text": "A diferença de preço «off-Steam»"
          },
          {
            "level": 2,
            "id": null,
            "text": "A diferença de preços é mensurável."
          },
          {
            "level": 3,
            "id": null,
            "text": "O que o valor em dólares revela"
          },
          {
            "level": 3,
            "id": null,
            "text": "Muitos locais indicam um valor em dólares superior a Steam."
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam continua a liderar em número de ofertas."
          },
          {
            "level": 3,
            "id": null,
            "text": "O ecossistema comercial está à vista de todos."
          },
          {
            "level": 2,
            "id": null,
            "text": "Quem pode reiniciar as medidas de segurança?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Um código de recuperação que desativou a segurança da conta e uma perda declarada de $10,000"
          },
          {
            "level": 3,
            "id": null,
            "text": "Para além do inventário."
          },
          {
            "level": 3,
            "id": "theft-ledger-title",
            "text": "Valve abriu a porta duas vezes, com trinta e três meses de intervalo. A porta nunca se fechou."
          },
          {
            "level": 4,
            "id": null,
            "text": "O que o registo revela e que nenhum caso isolado revela."
          },
          {
            "level": 3,
            "id": null,
            "text": "A confidencialidade deve ser acompanhada de responsabilidade técnica."
          },
          {
            "level": 2,
            "id": null,
            "text": "Segue o rasto do dinheiro. Separa as transações."
          },
          {
            "level": 3,
            "id": null,
            "text": "Onde o dinheiro realmente circula."
          },
          {
            "level": 3,
            "id": null,
            "text": "Classifique a atividade e, em seguida, a obrigação."
          },
          {
            "level": 3,
            "id": null,
            "text": "Acompanhar os rendimentos, os conhecimentos e a assistência."
          },
          {
            "level": 2,
            "id": null,
            "text": "A Lei dos Serviços Digitais: registar o conhecimento"
          },
          {
            "level": 3,
            "id": null,
            "text": "Um prazo de dez dias."
          },
          {
            "level": 3,
            "id": null,
            "text": "A janela temporal do DSA."
          },
          {
            "level": 3,
            "id": null,
            "text": "A duração requer um registo de notificações."
          },
          {
            "level": 3,
            "id": null,
            "text": "do volume de negócios anual a nível mundial"
          },
          {
            "level": 2,
            "id": null,
            "text": "Menores: um login com Steam não constitui uma verificação da idade"
          },
          {
            "level": 3,
            "id": null,
            "text": "Identifique o operador e os dados."
          },
          {
            "level": 3,
            "id": null,
            "text": "Registe o percurso desde o início de sessão até ao depósito."
          },
          {
            "level": 2,
            "id": null,
            "text": "O pedido. A resposta. A comparação que falta."
          },
          {
            "level": 3,
            "id": null,
            "text": "Os registos existem; o titular dos dados não os recebeu."
          },
          {
            "level": 2,
            "id": null,
            "text": "O Acordo de Assinatura em relação à própria arquitetura da plataforma"
          },
          {
            "level": 3,
            "id": null,
            "text": "O limite máximo do mercado e a proibição de utilização comercial"
          },
          {
            "level": 3,
            "id": null,
            "text": "A vulnerabilidade da chave API como uma questão de conceção da plataforma, e não como negligência do utilizador"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve recebe o nome de host de autenticação em cada início de sessão"
          },
          {
            "level": 3,
            "id": null,
            "text": "O padrão observado nas queixas arquivadas"
          },
          {
            "level": 3,
            "id": null,
            "text": "Um tribunal que analisasse este processo não interpretaria a SSA isoladamente."
          },
          {
            "level": 2,
            "id": null,
            "text": "As conclusões. Os registos que solicitamos."
          },
          {
            "level": 2,
            "id": null,
            "text": "Memorando de Provas — material fornecido pela Fonte 1"
          },
          {
            "level": 2,
            "id": null,
            "text": "A censura no PDF gerado é meramente estética: o texto ocultado continua a poder ser extraído"
          },
          {
            "level": 2,
            "id": null,
            "text": "Documentação de apoio e correspondência jurídica"
          },
          {
            "level": 2,
            "id": null,
            "text": "Documentos primários selecionados"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-01",
            "text": "Chaves de hardware, solicitadas em 2016"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-02",
            "text": "Relatórios de falhas sem uma opção de exclusão eficaz"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-03",
            "text": "Foi comunicada uma utilização abusiva de bilhetes de autenticação ao Valve"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-01",
            "text": "44 compras contestadas no Mercado"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-02",
            "text": "Uma proibição permanente e recurso encerrado"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-03",
            "text": "Um reinício da recuperação e uma perda registada de $10,000"
          },
          {
            "level": 2,
            "id": null,
            "text": "ArchiSteamFarm e a cláusula de automatização"
          },
          {
            "level": 2,
            "id": null,
            "text": "Rules ledger: clauses against recorded platforms"
          },
          {
            "level": 3,
            "id": "ledger-title",
            "text": "Utilização comercial e cobrança na conta"
          },
          {
            "level": 3,
            "id": "lw-register-title",
            "text": "Registo da plataforma 175"
          },
          {
            "level": 4,
            "id": null,
            "text": "Ónus da prova"
          },
          {
            "level": 4,
            "id": null,
            "text": "O que é — e o que não é — um registo marcado"
          },
          {
            "level": 2,
            "id": null,
            "text": "Guia prático sobre o DSAR: solicitar as provas"
          },
          {
            "level": 3,
            "id": null,
            "text": "Guarde a sua cronologia."
          },
          {
            "level": 3,
            "id": null,
            "text": "Solicite os seus dados arquivados."
          },
          {
            "level": 3,
            "id": null,
            "text": "Guarde o comprovativo de entrega."
          },
          {
            "level": 3,
            "id": null,
            "text": "Compare a resposta."
          },
          {
            "level": 3,
            "id": null,
            "text": "Segurança da conta e registos de acesso"
          },
          {
            "level": 3,
            "id": null,
            "text": "Uma discrepância constitui um indício que deve ser investigado."
          },
          {
            "level": 2,
            "id": null,
            "text": "Volume de assistência. Tempos de resposta publicados."
          },
          {
            "level": 3,
            "id": null,
            "text": "Duas filas num balcão de apoio, conforme se pode ver em 21 capturas de ecrã arquivadas."
          },
          {
            "level": 2,
            "id": null,
            "text": "Conte os registos. Verifique o âmbito."
          },
          {
            "level": 2,
            "id": null,
            "text": "Valve não publica qualquer registo de medidas coercivas.\nConstruímos um."
          }
        ],
        "links": [
          "https://dotesports.com/counter-strike/news/csgo-lounge-billion-bets-3896",
          "https://store.steampowered.com/agreement/?l=english",
          "http://web.archive.org/web/20260921022032/https://store.steampowered.com/agreement/?l=english",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-all-results.json",
          "https://blog.counter-strike.net/expresstrade/",
          "http://web.archive.org/web/20260307161538/https://blog.counter-strike.net/expresstrade/",
          "https://wsgc.wa.gov/news/2016/washington-state-gambling-commission-orders-valve-stop-skins-gambling",
          "http://web.archive.org/web/20260520012601/https://wsgc.wa.gov/news/2016/washington-state-gambling-commission-orders-valve-stop-skins-gambling",
          "https://fr.scribd.com/document/328063293/Valve-s-Oct-18th-response-to-Washington-State-Gambling-Commission-s-cease-and-desist",
          "https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921021947/https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921022628/https://steamcommunity.com/linkfilter/?url=https:%2F%2Frollbit.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rbsnin.com.20260921T021120Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rollbit.com.json",
          "http://web.archive.org/web/20260921022740/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fskin.club",
          "http://web.archive.org/web/20260921022842/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fsc-auth.net",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skin.club.json",
          "http://web.archive.org/web/20260921022603/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fhowl.gg",
          "http://web.archive.org/web/20260921022636/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fhowl.uno",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/howl.gg.json",
          "http://web.archive.org/web/20260921022840/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fduelbits.com",
          "http://web.archive.org/web/20260921022901/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fswitchflips.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/duelbits.com.json",
          "http://web.archive.org/web/20260921022758/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgofast.com",
          "http://web.archive.org/web/20260921022847/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fauthtofast.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgofast.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/farmskins.com.20260921T025840Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/steam.kobal.cc.20260921T025844Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/farmskins.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cobaltlab.tech.20260921T041604Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cobaltauth.com.20260921T041608Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/cobaltlab.tech.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgo.net.20260921T041619Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cn2.easylot.net.20260921T041623Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgo.net.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/ggdrop.com.20260921T041637Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/ggauth.com.20260921T041641Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/ggdrop.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rustchance.com.20260921T041703Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/hgfuihd.com.20260921T041706Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rustchance.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skin.fans.20260921T041710Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.skinfans.com.20260921T041713Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skin.fans.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinport.com.20260921T041724Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinport.app.20260921T041728Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skinport.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skins.cash.20260921T041731Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinscash.live.20260921T041735Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skins.cash.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2hunt.com.20260921T041739Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rstspcl.com.20260921T041742Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tf2hunt.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgogem.com.20260922T192355Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/api.csgem.com.20260922T192358Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-2026-09-22.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/gamdom.com.20260922T192326Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/login.gambldom.com.20260922T192330Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/12cs.fail.20260922T192347Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/fail.games.20260922T192351Z.html",
          "http://web.archive.org/web/20260921022953/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgoempire.com",
          "http://web.archive.org/web/20260921022947/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgoempirelogin4.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgoempire.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cs.money.20260921T021131Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.dota.trade.20260921T021134Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/cs.money.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csfloat.com.20260921T041612Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgofloat.com.20260921T041615Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csfloat.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/g4skins.com.20260921T041630Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.g4s.to.20260921T041634Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/g4skins.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/juice.gg.20260921T041644Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/letmeinjuice.com.20260921T041648Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/juice.gg.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/market.csgo.com.20260921T041652Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2.net.20260921T041655Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/market.csgo.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rust.tm.20260921T041659Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rust.tm.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgolounge.com.20260922T192333Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2.net.20260922T192340Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2lounge.com.20260922T192337Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinbaron.de.20260921T041717Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinbaron.com.20260921T041721Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skinbaron.de.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2royal.com.20260921T041746Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2auth.com.20260921T041750Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tf2royal.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tradeit.gg.20260921T041753Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/connect-tradeit.com.20260921T041757Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tradeit.gg.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/upgrader.pro.20260921T041801Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/upgauth.space.20260921T041804Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/upgrader.pro.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-recheck-2026-09-21.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/domain-registration.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wayback-snapshots.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-2026-09-22c.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/master_registry.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/longitudinal-steam-phishing-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-steam-phishing-100.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-coverage-2026-09-22.json",
          "https://blog.csfloat.com/how-floatdb-tracks-items/",
          "http://web.archive.org/web/20260921022415/https://blog.csfloat.com/how-floatdb-tracks-items/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/platform-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/platforms-removed.json",
          "https://hackerone.com/reports/291750",
          "http://web.archive.org/web/20251116185046/https://hackerone.com/reports/291750",
          "https://hackerone.com/reports/1079561",
          "http://web.archive.org/web/20260924181830/https://hackerone.com/reports/1079561",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/hackerone-reports.json",
          "https://phishdestroy.io/steam_dossier/pt/steam_enforcement_evidence.html#support-records",
          "https://www.darknavy.org/blog/exploiting_steam_usual_and_unusual_ways_in_the_cef_framework/",
          "https://steamcommunity.com/groups/SteamClientBeta/discussions/0/3365901765276206401/",
          "http://web.archive.org/web/20250804051514/https://steamcommunity.com/groups/SteamClientBeta/discussions/0/3365901765276206401/",
          "https://www.chromium.org/developers/design-documents/safebrowsing/",
          "http://web.archive.org/web/20260821101616/https://www.chromium.org/developers/design-documents/safebrowsing/",
          "https://www.chromium.org/developers/how-tos/api-keys/",
          "http://web.archive.org/web/20260830122831/https://www.chromium.org/developers/how-tos/api-keys/",
          "https://github.com/Homebrew/homebrew-cask/issues/193814",
          "https://testsafebrowsing.appspot.com/",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/domain-registration.json",
          "https://phishdestroy.io/steam_dossier/pt/AUTH_AUDIT.md",
          "https://datatracker.ietf.org/doc/rfc6749/",
          "https://docs.cloud.google.com/docs/authentication/api-keys",
          "https://listings.pcisecuritystandards.org/pdfs/PCI_DSS_Resource_Guide_(003).pdf",
          "https://developer.apple.com/news/?id=02202019a",
          "http://web.archive.org/web/20250506070026/https://developer.apple.com/news/?id=02202019a",
          "https://dev.twitch.tv/docs/authentication/validate-tokens/",
          "https://discuss.dev.twitch.com/t/legacy-twitch-api-v5-i-e-kraken-shutdown-reminder-february-28-2022/36589",
          "http://web.archive.org/web/20250127085635/https://discuss.dev.twitch.com/t/legacy-twitch-api-v5-i-e-kraken-shutdown-reminder-february-28-2022/36589",
          "https://store.steampowered.com/news/posts/?enddate=1788390000",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/4123547285514022851",
          "https://skinvault.gg/blog/cs2-trade-protection-explained/",
          "https://csmarketcap.com/blog/market-insights/from-boom-to-bust-cs2s-trade-protection-impact",
          "https://skin.land/blog/steam-changes-cs2-trade-ban-logic-timing/",
          "https://help.steampowered.com/faqs/view/3041-A87A-E5F6-B6AC",
          "https://steamcommunity.com/ogg/593110/announcements/detail/533224478739530146",
          "https://steamcommunity.com/games/CSGO/announcements/detail/4447966961421256740",
          "https://steamcommunity.com/sharedfiles/filedetails/?id=2926756889",
          "https://steamcommunity.com/dev/apikey",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3734103130194459461",
          "https://steamcommunity.com/discussions/forum/1/3807266184852932971/",
          "https://help.steampowered.com/faqs/view/225C-C51E-B8F0-55B2",
          "https://store.steampowered.com/news/group/4/view/3314112260640237775",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/issues/325",
          "https://blog.dota2.com/2020/05/trading-cooldown/",
          "https://blog.counter-strike.net/index.php/2018/03/20308/",
          "http://web.archive.org/web/20250226114333/https://blog.counter-strike.net/index.php/2018/03/20308/",
          "https://phishdestroy.io/steam_dossier/pt/steam_evidence_archive.html",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/493839547938902179",
          "https://store.steampowered.com/online_conduct",
          "http://web.archive.org/web/20260921022120/https://store.steampowered.com/online_conduct",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260918014700/https://store.steampowered.com/subscriber_agreement/",
          "https://steamcommunity.com/dev/apiterms",
          "http://web.archive.org/web/20260921022210/https://steamcommunity.com/dev/apiterms",
          "https://help.steampowered.com/en/faqs/view/628C-E332-BD8C-4D36",
          "https://phishdestroy.io/steam_dossier/pt/social_graph.html",
          "https://phishdestroy.io/steam_dossier/pt/security_timeline.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wsgc-skins-gambling-briefing-2018.pdf",
          "https://wsgc.wa.gov/sites/default/files/2023-10/Skins%20Gambling.pdf",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wsgc-briefing-manifest.json",
          "https://x.com/csgobig",
          "https://www.facebook.com/csgobigofficial/",
          "https://500.casino/",
          "https://csgolounge.com/",
          "https://csgocasino.gg/",
          "https://x.com/CSGOatsecom",
          "https://x.com/CSGOSweep/status/937420902538543106",
          "https://x.com/Wild",
          "https://x.com/csgopot",
          "https://x.com/csgodiamondscom",
          "https://www.ftc.gov/legal-library/browse/cases-proceedings/162-3184-csgo-lotto-matter",
          "https://x.com/CSGODouble",
          "https://x.com/csgo_massive",
          "https://www.facebook.com/csgostrongfree/",
          "https://www.facebook.com/CSNCOM/",
          "https://www.gamblingcommission.gov.uk/report/young-people-and-gambling",
          "https://www.aph.gov.au/Parliamentary_Business/Committees/Senate/Environment_and_Communications/Gamingmicro-transactions",
          "https://phishdestroy.io/steam_dossier/pt/elite_skins.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/csfloat-catalogue.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/skinport-floor-over-cap.json",
          "https://pricempire.com/cs2-marketplaces",
          "http://web.archive.org/web/20260921022459/https://pricempire.com/cs2-marketplaces",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/priceempire-marketplaces.json",
          "https://www.steamanalyst.com/marketplace",
          "http://web.archive.org/web/20260719014552/https://www.steamanalyst.com/marketplace",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-atlas.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json",
          "https://phishdestroy.io/steam_dossier/pt/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/pt/steam_enforcement_evidence.html#case-support-recovery",
          "https://top10.owasp.org/2025/A01_2025-Broken_Access_Control/",
          "http://web.archive.org/web/20260920212535/https://top10.owasp.org/2025/A01_2025-Broken_Access_Control/",
          "https://store.steampowered.com/privacy_agreement/",
          "http://web.archive.org/web/20260921021648/https://store.steampowered.com/privacy_agreement/",
          "https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "http://web.archive.org/web/20250818113925/https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "https://www.dexerto.com/counter-strike-2/valve-saves-hacked-cs2-player-threatened-with-ransom-over-300000-of-rare-stickers-3283135/",
          "https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "http://web.archive.org/web/20220702042821/https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "https://www.kaspersky.com/blog/cs-go-two-million-usd-inventory-hack/44697/",
          "https://esportfire.com/article/the-2-million-usd-csgo-hack-22062022",
          "http://web.archive.org/web/20260515110250/https://esportfire.com/article/the-2-million-usd-csgo-hack-22062022",
          "https://esportsbetting.com/valve-deletes-130000-stolen-dragon-lore/",
          "https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "http://web.archive.org/web/20251115173120/https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "https://vkplay.ru/media/news/bloger-rasskazal-kak-podderzhka-steam-vorovala-akkaunty-igrokov/",
          "https://lis-skins.com/ru/blog/krupneisaia-mosenniceskaia-sxema-v-istorii-steam/",
          "https://escorenews.com/ru/csgo/news/44056-sotrudniki-podderjki-steam-zanimalis-krajey-skinov-s-akkauntov-za-god-oni-zarabotali-svyshe-300-tysyach-dollarov",
          "https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "http://web.archive.org/web/20250805141942/https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/outsourcing-archive-records.json",
          "https://community.skin.club/en/news/collector-has-steam-inventory-returned-after-bold-hack",
          "https://esportfire.com/article/300k-scam-full-katowice-2014-holo-collection-hacked",
          "http://web.archive.org/web/20251217072445/https://esportfire.com/article/300k-scam-full-katowice-2014-holo-collection-hacked",
          "https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng",
          "http://web.archive.org/web/20260920024236/https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng",
          "https://ag.ny.gov/press-release/2026/attorney-general-james-sues-game-developer-promoting-illegal-gambling-through",
          "http://web.archive.org/web/20260901015430/https://ag.ny.gov/press-release/2026/attorney-general-james-sues-game-developer-promoting-illegal-gambling-through",
          "https://www.fincen.gov/sites/default/files/2019-05/FinCEN%20CVC%20Guidance%20FINAL.pdf",
          "http://web.archive.org/web/20250711185007/https://www.fincen.gov/sites/default/files/2019-05/FinCEN%20CVC%20Guidance%20FINAL.pdf",
          "https://eur-lex.europa.eu/legal-content/EN/LSU/?uri=CELEX:32018L1673",
          "https://eur-lex.europa.eu/eli/dir/2024/1640/oj/eng",
          "http://web.archive.org/web/20260830153004/https://eur-lex.europa.eu/eli/dir/2024/1640/oj/eng",
          "https://eur-lex.europa.eu/eli/reg/2022/2065/oj/eng",
          "http://web.archive.org/web/20260920080125/https://eur-lex.europa.eu/eli/reg/2022/2065/oj/eng",
          "https://phishdestroy.io/steam_dossier/pt/legal_analysis.html",
          "https://partner.steamgames.com/doc/features/auth#website",
          "http://web.archive.org/web/20260921022335/https://partner.steamgames.com/doc/features/auth",
          "https://www.ftc.gov/legal-library/browse/rules/childrens-online-privacy-protection-rule-coppa",
          "http://web.archive.org/web/20260921070051/https://www.ftc.gov/legal-library/browse/rules/childrens-online-privacy-protection-rule-coppa",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/gdpr-ticket-1.png",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/screenshot-manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/gdpr-ticket-2.png",
          "https://datenschutz.hamburg.de/beschwerde",
          "https://edpb.europa.eu/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/regulatory-review/disclosure-audit.json",
          "https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "http://web.archive.org/web/20260821155801/https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "https://phishdestroy.io/steam_dossier/pt/index#exhibit-gallery-section",
          "https://github.com/ValveSoftware/steam-for-linux/issues/4521",
          "https://phishdestroy.io/steam_dossier/pt/steam_evidence_archive.html?source=GitHub&record=484",
          "https://github.com/ValveSoftware/steam-for-linux/issues/6459",
          "http://web.archive.org/web/20260419051343/https://github.com/ValveSoftware/steam-for-linux/issues/6459",
          "https://phishdestroy.io/steam_dossier/pt/steam_evidence_archive.html?source=GitHub&record=467",
          "https://github.com/ValveSoftware/Source-1-Games/issues/3857",
          "https://phishdestroy.io/steam_dossier/pt/steam_evidence_archive.html?source=GitHub&record=768",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "http://web.archive.org/web/20250320082450/https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://phishdestroy.io/steam_dossier/pt/steam_evidence_archive.html?source=Reddit&record=4533",
          "https://www.reddit.com/r/ohnePixel/comments/1hahqx2/permanently_banned_steam_account_without_a_clear/",
          "https://phishdestroy.io/steam_dossier/pt/steam_evidence_archive.html?source=Reddit&record=4766",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://phishdestroy.io/steam_dossier/pt/steam_evidence_archive.html?source=Reddit&record=4592",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/selected-evidence-records.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive_manifest.json",
          "https://phishdestroy.io/steam_dossier/pt/card_economy.html",
          "https://github.com/JustArchiNET/ArchiSteamFarm/wiki/FAQ",
          "https://phishdestroy.io/steam_dossier/pt/card_economy.html#scale",
          "https://phishdestroy.io/steam_dossier/pt/card_economy.html#licence",
          "https://phishdestroy.io/steam_dossier/pt/enforcement_audit.html",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "http://web.archive.org/web/20260924181709/https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://rdap.verisign.com/com/v1/domain/csgoempire.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoempire.com",
          "https://rdap.verisign.com/com/v1/domain/csgoempirelogin4.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/csgoempire.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustreaper.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustreaper.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/rustreaper.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustly.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustly.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/rustly.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgofast.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgofast.com",
          "https://rdap.verisign.com/com/v1/domain/authtofast.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/csgofast.com.json",
          "https://rdap.verisign.com/com/v1/domain/duelbits.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fduelbits.com",
          "https://rdap.verisign.com/com/v1/domain/switchflips.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/duelbits.com.json",
          "https://rdap.verisign.com/com/v1/domain/farmskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffarmskins.com",
          "https://tld-rdap.verisign.com/cc/v1/domain/kobal.cc",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/farmskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoluck.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoluck.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/csgoluck.com.json",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/domain-registry/insane.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Finsane.gg",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/insane.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs2skin.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs2skin.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/cs2skin.com.json",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/domain-registry/juice.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fjuice.gg",
          "https://rdap.verisign.com/com/v1/domain/letmeinjuice.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/juice.gg.json",
          "https://rdap.verisign.com/com/v1/domain/ggdrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fggdrop.com",
          "https://rdap.verisign.com/com/v1/domain/ggauth.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/ggdrop.com.json",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/domain-registry/howl.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhowl.gg",
          "https://rdap.radix.host/rdap/domain/howl.uno",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/howl.gg.json",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/domain-registry/chicken.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fchicken.gg",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/chicken.gg.json",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/domain-registry/csgocasino.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgocasino.gg",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/csgocasino.gg.json",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/domain-registry/hunt.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhunt.gg",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/hunt.gg.json",
          "https://rdap.verisign.com/com/v1/domain/csbattle.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsbattle.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/csbattle.com.json",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/domain-registry/skinrave.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinrave.gg",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/skinrave.gg.json",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/domain-registry/csdouble.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsdouble.gg",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/csdouble.gg.json",
          "https://rdap.verisign.com/com/v1/domain/rustchance.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustchance.com",
          "https://rdap.verisign.com/com/v1/domain/hgfuihd.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/rustchance.com.json",
          "https://rdap.radix.host/rdap/domain/cobaltlab.tech",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcobaltlab.tech",
          "https://rdap.verisign.com/com/v1/domain/cobaltauth.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/cobaltlab.tech.json",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/domain-registry/raided.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fraided.gg",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/raided.gg.json",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/domain-registry/rustneo.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustneo.gg",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/rustneo.gg.json",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/domain-registry/splits.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsplits.gg",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/splits.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/upgrader.pro",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fupgrader.pro",
          "https://rdap.radix.host/rdap/domain/upgauth.space",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/upgrader.pro.json",
          "https://rdap.centralnic.com/fans/domain/skin.fans",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.fans",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/skin.fans.json",
          "https://rdap.nic.one/domain/hotpizza.one",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhotpizza.one",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/hotpizza.one.json",
          "https://rdap.verisign.com/com/v1/domain/g4skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg4skins.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/g4skins.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2royal.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2royal.com",
          "https://rdap.verisign.com/com/v1/domain/tf2auth.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/tf2royal.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2hunt.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2hunt.com",
          "https://rdap.verisign.com/com/v1/domain/rstspcl.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/tf2hunt.com.json",
          "https://rdap.identitydigital.services/rdap/domain/tf2.bet",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2.bet",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/tf2.bet.json",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/domain-registry/openstars.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fopenstars.gg",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/openstars.gg.json",
          "https://rdap.verisign.com/com/v1/domain/skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/skins.com.json",
          "https://rdap.identitydigital.services/rdap/domain/white.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwhite.market",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/white.market.json",
          "https://rdap.identitydigital.services/rdap/domain/moon.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmoon.market",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/moon.market.json",
          "https://rdap.verisign.com/com/v1/domain/csfloat.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsfloat.com",
          "https://rdap.verisign.com/com/v1/domain/csgofloat.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/csfloat.com.json",
          "https://rdap.identitydigital.services/rdap/domain/skin.land",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.land",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/skin.land.json",
          "https://rdap.verisign.com/com/v1/domain/haloskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhaloskins.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/haloskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/163.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuff.163.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/buff.163.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmarket.csgo.com",
          "https://rdap.verisign.com/net/v1/domain/dota2.net",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/market.csgo.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinport.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinport.com",
          "https://pubapi.registry.google/rdap/domain/skinport.app",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/skinport.com.json",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/domain-registry/skinflow.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinflow.gg",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/skinflow.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/skin.place",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.place",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/skin.place.json",
          "https://rdap.verisign.com/com/v1/domain/skinsmonkey.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinsmonkey.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/skinsmonkey.com.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbaron.de",
          "https://rdap.verisign.com/com/v1/domain/skinbaron.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/skinbaron.de.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frust.tm",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/rust.tm.json",
          "https://rdap.verisign.com/com/v1/domain/pirateswap.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fpirateswap.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/pirateswap.com.json",
          "https://rdap.radix.host/rdap/domain/mannco.store",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmannco.store",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/mannco.store.json",
          "https://rdap.verisign.com/com/v1/domain/skinswap.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinswap.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/skinswap.com.json",
          "https://rdap.verisign.com/com/v1/domain/exeskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fexeskins.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/exeskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/balticskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbalticskins.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/balticskins.com.json",
          "https://rdap.nic.trade/domain/cs.trade",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.trade",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/cs.trade.json",
          "https://rdap.verisign.com/com/v1/domain/rapidskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frapidskins.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/rapidskins.com.json",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/domain-registry/tradeit.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftradeit.gg",
          "https://rdap.verisign.com/com/v1/domain/connect-tradeit.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/tradeit.gg.json",
          "https://rdap.verisign.com/com/v1/domain/49skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F49skins.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/49skins.com.json",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/domain-registry/skinvault.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinvault.gg",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/skinvault.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/aim.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Faim.market",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/aim.market.json",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/domain-registry/skinout.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinout.gg",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/skinout.gg.json",
          "https://rdap.verisign.com/com/v1/domain/ntskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fntskins.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/ntskins.com.json",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/domain-registry/gamerpay.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamerpay.gg",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/gamerpay.gg.json",
          "https://rdap.nic.tf/domain/scrap.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fscrap.tf",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/scrap.tf.json",
          "https://rdap.nic.tf/domain/marketplace.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmarketplace.tf",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/marketplace.tf.json",
          "https://rdap.identitydigital.services/rdap/domain/skins.cash",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.cash",
          "https://rdap.identitydigital.services/rdap/domain/skinscash.live",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/skins.cash.json",
          "https://rdap.verisign.com/net/v1/domain/csgo.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo.net",
          "https://rdap.verisign.com/net/v1/domain/easylot.net",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/csgo.net.json",
          "https://rdap.verisign.com/net/v1/domain/cybershoke.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcybershoke.net",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/cybershoke.net.json",
          "https://rdap.verisign.com/net/v1/domain/fastcup.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffastcup.net",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/fastcup.net.json",
          "https://rdap.verisign.com/com/v1/domain/leetify.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fleetify.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/leetify.com.json",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/domain-registry/scope.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fscope.gg",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/scope.gg.json",
          "https://rdap.verisign.com/com/v1/domain/tradeupspy.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftradeupspy.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/tradeupspy.com.json",
          "https://rdap.identitydigital.services/rdap/domain/cs.deals",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.deals",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/cs.deals.json",
          "https://rdap.verisign.com/com/v1/domain/pricempire.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fpricempire.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/pricempire.com.json",
          "https://rdap.identitydigital.services/rdap/domain/lzt.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flzt.market",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/lzt.market.json",
          "https://rdap.verisign.com/com/v1/domain/z2u.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fz2u.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/z2u.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoroll.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoroll.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/csgoroll.com.json",
          "https://rdap.verisign.com/com/v1/domain/rollbit.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frollbit.com",
          "https://rdap.verisign.com/com/v1/domain/rbsnin.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/rollbit.com.json",
          "https://rdap.identitydigital.services/rdap/domain/500.casino",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F500.casino",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/500.casino.json",
          "https://rdap.verisign.com/com/v1/domain/csgobig.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgobig.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/csgobig.com.json",
          "https://rdap.verisign.com/com/v1/domain/casedrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcasedrop.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/casedrop.com.json",
          "https://rdap.verisign.com/com/v1/domain/banditcamp.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbanditcamp.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/banditcamp.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinbox.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbox.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/skinbox.com.json",
          "https://rdap.verisign.com/com/v1/domain/tastydrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftastydrop.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/tastydrop.com.json",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/domain-registry/csgopolygon.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgopolygon.gg",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/csgopolygon.gg.json",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/domain-registry/magicdrop.ru.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmagicdrop.ru",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/magicdrop.ru.json",
          "https://rdap.verisign.com/com/v1/domain/csdice.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsdice.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/csdice.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinodds.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinodds.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/skinodds.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgowin.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgowin.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/csgowin.com.json",
          "https://rdap.verisign.com/net/v1/domain/csgorun.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgorun.net",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/csgorun.net.json",
          "https://rdap.verisign.com/com/v1/domain/openskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fopenskins.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/openskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustbet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustbet.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/rustbet.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgomagic.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgomagic.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/csgomagic.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgobounty.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgobounty.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/csgobounty.com.json",
          "https://rdap.verisign.com/com/v1/domain/ezskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fezskins.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/ezskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustcases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustcases.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/rustcases.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoreaper.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoreaper.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/csgoreaper.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgocases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgocases.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/csgocases.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo-skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo-skins.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/csgo-skins.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgonet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgonet.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/csgonet.com.json",
          "https://rdap.verisign.com/com/v1/domain/wtfskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwtfskins.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/wtfskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/flamecases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fflamecases.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/flamecases.com.json",
          "https://rdap.verisign.com/com/v1/domain/gamedom.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamedom.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/gamedom.com.json",
          "https://rdap.nic.club/domain/skin.club",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.club",
          "https://rdap.verisign.com/net/v1/domain/sc-auth.net",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/skin.club.json",
          "https://rdap.verisign.com/com/v1/domain/daddyskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdaddyskins.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/daddyskins.com.json",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/domain-registry/rustix.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustix.gg",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/rustix.gg.json",
          "https://rdap.nic.club/domain/skins.club",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.club",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/skins.club.json",
          "https://rdap.publicinterestregistry.org/rdap/domain/csgohouse.org",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgohouse.org",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/csgohouse.org.json",
          "https://rdap.verisign.com/net/v1/domain/skinrave.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinrave.net",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/skinrave.net.json",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/domain-registry/bloodycase.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbloodycase.gg",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/bloodycase.gg.json",
          "https://rdap.verisign.com/com/v1/domain/csgoclicker.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoclicker.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/csgoclicker.com.json",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/domain-registry/rustbet.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustbet.gg",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/rustbet.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs-drop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs-drop.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/cs-drop.com.json",
          "https://rdap.verisign.com/net/v1/domain/hellstore.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhellstore.net",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/hellstore.net.json",
          "https://rdap.verisign.com/com/v1/domain/rustloot.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustloot.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/rustloot.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo-case.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo-case.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/csgo-case.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgogem.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgogem.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/csgogem.com.json",
          "https://rdap.verisign.com/com/v1/domain/rainbet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frainbet.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/rainbet.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustclash.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustclash.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/rustclash.com.json",
          "https://rdap.identitydigital.services/rdap/domain/12cs.fail",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F12cs.fail",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/12cs.fail.json",
          "https://rdap.verisign.com/com/v1/domain/tf2easy.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwww.tf2easy.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/tf2easy.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2blaze.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2blaze.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/tf2blaze.com.json",
          "https://rdap.verisign.com/com/v1/domain/shuffle.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fshuffle.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/shuffle.com.json",
          "https://rdap.identitydigital.services/rdap/domain/buff.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuff.market",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/buff.market.json",
          "https://rdap.identitydigital.services/rdap/domain/avan.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Favan.market",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/avan.market.json",
          "https://rdap.identitydigital.services/rdap/domain/cs.money",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.money",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/cs.money.json",
          "https://rdap.verisign.com/com/v1/domain/uuskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fuuskins.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/uuskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/youpin898.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fyoupin898.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/youpin898.com.json",
          "https://rdap.verisign.com/com/v1/domain/c5game.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fc5game.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/c5game.com.json",
          "https://rdap.verisign.com/com/v1/domain/waxpeer.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwaxpeer.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/waxpeer.com.json",
          "https://rdap.verisign.com/com/v1/domain/dmarket.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdmarket.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/dmarket.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamcommunity.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamcommunity.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/steamcommunity.com.json",
          "https://rdap.verisign.com/com/v1/domain/lootfarm.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flootfarm.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/lootfarm.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustskins.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/rustskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/krakatoa.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fkrakatoa.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/krakatoa.com.json",
          "https://rdap.verisign.com/com/v1/domain/shadowpay.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fshadowpay.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/shadowpay.com.json",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/domain-registry/igxe.cn.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Figxe.cn",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/igxe.cn.json",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/domain-registry/swap.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fswap.gg",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/swap.gg.json",
          "https://rdap.verisign.com/com/v1/domain/bitskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbitskins.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/bitskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2mart.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2mart.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/tf2mart.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinbid.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbid.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/skinbid.com.json",
          "https://rdap.verisign.com/com/v1/domain/lootbear.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flootbear.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/lootbear.com.json",
          "https://rdap.nic.tf/domain/backpack.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbackpack.tf",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/backpack.tf.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fstntrading.eu",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/stntrading.eu.json",
          "https://rdap.verisign.com/com/v1/domain/skinwallet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinwallet.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/skinwallet.com.json",
          "https://rdap.verisign.com/com/v1/domain/dota2market.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdota2market.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/dota2market.com.json",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/domain-registry/xplay.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fxplay.gg",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/xplay.gg.json",
          "https://rdap.verisign.com/com/v1/domain/esportal.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fesportal.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/esportal.com.json",
          "https://rdap.registro.br/domain/gamersclub.com.br",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamersclub.com.br",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/gamersclub.com.br.json",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/domain-registry/epidemic.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fepidemic.gg",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/epidemic.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs2stash.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs2stash.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/cs2stash.com.json",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/domain-registry/csgoskins.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoskins.gg",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/csgoskins.gg.json",
          "https://rdap.verisign.com/com/v1/domain/steamanalyst.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamanalyst.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/steamanalyst.com.json",
          "https://rdap.verisign.com/net/v1/domain/steamcardexchange.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamcardexchange.net",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/steamcardexchange.net.json",
          "https://rdap.verisign.com/com/v1/domain/dotabuff.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdotabuff.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/dotabuff.com.json",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/domain-registry/tracker.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftracker.gg",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/tracker.gg.json",
          "https://rdap.verisign.com/com/v1/domain/funpay.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffunpay.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/funpay.com.json",
          "https://rdap.verisign.com/com/v1/domain/playerauctions.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fplayerauctions.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/playerauctions.com.json",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/domain-registry/eldorado.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Feldorado.gg",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/eldorado.gg.json",
          "https://rdap.verisign.com/com/v1/domain/g2a.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg2a.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/g2a.com.json",
          "https://rdap.verisign.com/net/v1/domain/kinguin.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fkinguin.net",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/kinguin.net.json",
          "https://rdap.verisign.com/com/v1/domain/g2g.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg2g.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/g2g.com.json",
          "https://rdap.verisign.com/com/v1/domain/playerup.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fplayerup.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/playerup.com.json",
          "https://rdap.verisign.com/net/v1/domain/smurfhub.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfhub.net",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/smurfhub.net.json",
          "https://rdap.verisign.com/com/v1/domain/smurfaccounts.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfaccounts.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/smurfaccounts.com.json",
          "https://rdap.verisign.com/com/v1/domain/buycsgorank.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuycsgorank.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/buycsgorank.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgosmurfkings.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgosmurfkings.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/csgosmurfkings.com.json",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/domain-registry/smurfstore.co.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfstore.co",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/smurfstore.co.json",
          "https://rdap.verisign.com/com/v1/domain/steamlvlup.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlvlup.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/steamlvlup.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamlevels.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlevels.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/steamlevels.com.json",
          "https://rdap.verisign.com/com/v1/domain/levelsteam.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flevelsteam.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/levelsteam.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamlevelu.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlevelu.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/steamlevelu.com.json",
          "https://rdap.verisign.com/com/v1/domain/eloking.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Feloking.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/eloking.com.json",
          "https://rdap.publicinterestregistry.org/rdap/domain/boosteria.org",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fboosteria.org",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/boosteria.org.json",
          "https://rdap.verisign.com/com/v1/domain/overgear.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fovergear.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/overgear.com.json",
          "https://rdap.verisign.com/com/v1/domain/blazingboost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fblazingboost.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/blazingboost.com.json",
          "https://rdap.verisign.com/com/v1/domain/dota2boost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdota2boost.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/dota2boost.com.json",
          "https://rdap.verisign.com/com/v1/domain/buyboost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuyboost.com",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit/buyboost.com.json",
          "https://phishdestroy.io/steam_dossier/pt/steam_tos_assets/auth-route-audit.json",
          "https://help.steampowered.com/en/faqs/view/365F-4BEE-2AE2-7BDD",
          "https://store.steampowered.com/privacy_agreement/#8",
          "https://www.edpb.europa.eu/system/files/2023-04/edpb_guidelines_202201_data_subject_rights_access_v2_en.pdf",
          "https://web.archive.org/web/20260810154631/https://store.steampowered.com/stats/support",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/design-review/part2/measurements.json",
          "https://phishdestroy.io/steam_dossier/pt/VALVE_EVIDENCE_PACK/databases/TOTAL_VALVE_SCANDALS_MASTER_DB.csv",
          "https://phishdestroy.io/steam_dossier/pt/license_disclaimer.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/pt/index.content.json",
      "export_json_sha256": "132c9550be99d94d1e80d47f506a7bb33f2d4502c6950aed2b72dcdf065defe7"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "pt/investigation_part2.html",
      "language": "pt",
      "title": "Acesso à conta e responsabilização — O Dossiê Steam",
      "source_url": "https://phishdestroy.io/steam_dossier/pt/investigation_part2",
      "source_html_sha256": "e25f40ac997145abe9d96602ffdcb0dab623842a802573660cae05965b5d538c",
      "exported_at": "2026-09-29T00:18:06.885Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "investigation_part2.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/pt/investigation_part2.pdf?v=print-20260929-v5",
        "sha256": "a7cd60c1ec457017d3b37a14548334ef833528a0721c080f0e2d56451dd116ce",
        "bytes": 126071,
        "pages": 9
      },
      "integrity": {
        "signed_object": "investigation_part2.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "investigation_part2.content.json.asc",
        "digest_file": "investigation_part2.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify investigation_part2.content.json.asc investigation_part2.content.json",
          "sha256sum -c investigation_part2.content.json.sha256"
        ]
      },
      "content": {
        "text": "O DOSSIER DA STEAM / II\n\nA sua conta.O acesso deles.Quem atende?\n\nAutomatização dos serviços públicos. Apoio externalizado. E quem fica a arcar com os custos.\n\nAcompanhe as infraestruturas, as perdas registadas e os documentos que sustentam as reivindicações.\n\nMapeie a infraestrutura ↘\nANEXO 01 / VIGILÂNCIA DO MERCADO PARALELO EM TEMPO REAL550,000+\n\nSteam contas atualmente à venda no FSB Market (nome anonimizado; o nome original não é indicado aqui)\nneste preciso momento\n\n550,000+ INVENTÁRIO EM TEMPO REAL · 231,829 NO CORPUS HISTÓRICO RECOLHIDO (198,320 REGISTOS DO STEALER)\n\nA principal plataforma subterrânea de transações para contas Steam pirateadas, FSB Market (outros nomes associados não divulgados), autentica tanto compradores como vendedores utilizando o OpenID oficial Steam da Valve (openid.realm = https://FSB Market). A qualquer momento, mais de meio milhão de contas roubadas e comprometidas (registos de roubo da RedLine/Lumma, capturas de phishing, preenchimento de credenciais) estão ativamente à venda por cêntimos ($0.50–$2.00). Nem FSB Market nem o fórum associado está bloqueado pelo Filtro de Ligações do Valve. Trata-se do reservatório industrial que alimenta as contas de bots pagas do 63.06%, que o Valve bloqueia sem prestar assistência à vítima.\n\nDados em tempo real: Monitorização do mercado paralelo (mais de 550 mil em tempo real) ↗ · Abrir registo de captura ↗ · Abrir o registo do filtro de ligações ↗Mais de 550 mil AO VIVO\n\n01 / UM ECOSSISTEMA COM AUTORES\n\nA automatização temdocumentação escrita.\n\nProjetos identificados. Funcionalidades publicadas. Identifique a documentação de uma ferramenta e, em seguida, analise as relações entre os programadores identificadas.\n\n252REPOSITÓRIOS RECOLHIDOS\n3,320PERFIS NO GITHUB\n4,214PERFIL – PARES DE REPOSITÓRIOS\nValve infraestruturasBibliotecas comunitáriasAplicações reutilizáveis\nAs linhas indicam integrações ou dependências documentadas. Selecione um nó para ver as respetivas referências.\n\nAutomatização de várias contas / JustArchiNET\n\nArchiSteamFarm\n\nO projeto anuncia explicitamente a obtenção simultânea de cartões em várias contas do Steam. O ficheiro do projeto declara uma dependência do SteamKit2.\n\nLeia a documentação do próprio projeto ↗\n\nSteamKit → ArchiSteamFarm\ndependência declarada ↗\n\nRELAÇÕES RECOLHIDAS\n\n40 etiquetas de colaboradores · 40 etiquetas da Forker\n\nExemplo de colaborador abaixo. Estas designações descrevem a relação com o repositório, não uma relação laboral ou de aprovação.\n\n@JustArchi@renovate[bot]@JustArchi-ArchiBot@dependabot-preview[bot]@renovate-bot@actions-user@dependabot-support@Abrynos\nO que o gráfico do programador revela\n\nO gráfico representa as relações publicadas entre colaboradores e criadores de forks de projetos específicos e perfis do GitHub. Trata-se de registos públicos — forks de repositórios, listas de contribuições, associações de perfis. A questão é o que o rasto documental das capacidades publicadas e das relações entre programadores exige que Valve responda, e não o que esta investigação inventou. Os hashes das fontes são guardados no proveniência do mapa.\n\nExplore toda a rede ↗Dados de origem do repositório ↓\n\n02 / CREDENCIAIS DIFERENTES. PODERES DIFERENTES.\n\nQual a teclaDe que é que estamos a falar?\n\nPara jogar um jogo, não é necessário que o jogador forneça uma chave pessoal da API Web. Essa é a distinção que está no cerne desta investigação.\n\n01 / CONTA DE UTILIZADOR\nChave pessoal da API Web\nsteamcommunity.com/dev/apikey\n\nEmitida a partir de uma conta de utilizador para chamadas à API autorizadas. A criação, a visibilidade, a revogação e a deteção de abusos das chaves são questões relacionadas com a segurança da conta.\n\n02 / BACKEND DO JOGO\nChave da API Web do editor\n\nOs parceiros da Steamworks utilizam as credenciais da editora para operações de backend suportadas, incluindo serviços relacionados com jogos. A chave pessoal de um jogador é uma credencial diferente.\n\n03 / IDENTIDADE E SESSÃO\nOpenID / tokens de sessão\n\nO OpenID confirma a identidade junto de um site. Um token de sessão ou de atualização Steam tem uma finalidade diferente. Estes mecanismos não devem ser apresentados como uma única «chave API» intercambiável.\n\nValve documenta as chaves da API Web tanto do utilizador como do editor. Por conseguinte, a API Web na sua totalidade não é independente do Steamworks. Documentação sobre chaves API ↗ arquivado 2026-09-15 ↗ · Autenticação durante a sessão de jogo ↗ arquivado 2026-08-29 ↗\n\nDOCUMENTADO PELO AUTOR DA FERRAMENTA / MARÇO DE 2024\n\nA automação pode utilizar mais do que uma chave API.\n\nA wiki do Trade Offer Manager descreve a utilização de um token de acesso de sessão para algumas partes da API Web quando não existe uma chave de API separada. Também menciona a confirmação por telemóvel para a criação de chaves a partir do final de 2023. O responsável pela manutenção afirma que a utilização do token desta forma não é suportada pela Valve; trata-se de uma afirmação desatualizada na documentação, não de um teste prático de contorno.\n\nConsulte a explicação do responsável pela manutenção ↗ arquivado 2026-09-24 ↗\n\nO LADO HUMANO / UM PERCURSO ILUSTRATIVO DO PHISHING\n\nAinda a jogar.Já foi revelado.\n\nUma mensagem de um amigo. Um pedido para votar. Uma página de agradecimento. Para o jogador, a tarefa está concluída. Uma sessão comprometida pode prolongar-se para além desse momento.\n\nNO ECRÃ DO JOGADOR\n\nF\nO RELATO DE UM AMIGO\n\n«Podes votar na nossa equipa?»\n\nO pedido chega através do chat dSteam, proveniente de uma conta conhecida. Neste cenário, a página associada abre-se no navegador do cliente.\n\nFORA DE VISTA\n\nA confiança surge antes mesmo do site.\n\nA conta de um amigo que tenha sido pirateada pode conferir credibilidade a um link de phishing. A interface Steam que o rodeia não certifica o site de destino.\n\nREMETENTE CONHECIDO / DESTINATÁRIO EXTERNO\nA segurança da conta é a questão a ter em conta antes de qualquer artigo ser vendido.\n\nO jogador não tinha a intenção de criar uma credencial de automatização nem de delegar o controlo. O facto de voltar a um jogo não constitui prova de que a conta esteja segura. O Valve guarda os registos da sessão, o registo de criação da chave API e os dados de correlação dos dispositivos. A vítima não os guarda. Essa assimetria constitui o problema da responsabilização.\n\nAcesso à sessão e tipos de credenciais\n\nUma chave API e uma sessão iniciada são credenciais distintas com capacidades diferentes. A revogação de uma chave não encerra uma sessão ativa. A própria documentação de Valve descreve ambas; Valve mantém os registos que indicariam qual das credenciais estava ativa no momento de qualquer ação contestada. O que se exige é a divulgação desse registo — e não uma inferência inventada pela investigação. Documentação do responsável pela manutenção sobre o tratamento de tokens ↗ arquivado 2026-09-24 ↗ · Valve documentação da chave ↗ arquivado 2026-09-15 ↗\n\n03 / O MERCADO OFICIAL TEM UM LIMITE MÁXIMO\n\nO artigo pode ser raro.O limite mantém-se.\n\nUm preço superior ao limite máximo de cotação não pode ser alcançado através de uma única cotação no Mercado Comunitário a esse preço total.\n\nPREÇO DE VENDA INDICATIVO$5,000Alterar o preço de venda do artigo\n$100$20,000\n\nUma ilustração do limite publicado, não constituindo uma avaliação nem uma recomendação de negociação.\n\nLIMITE DE COTAÇÃO≈ $1,800\nTAMANHO DA CARTEIRA≈ $2,000\n\nAcima do limite máximo de cotação publicado.\n\nOs fundos da carteira não podem ser levantados para uma conta bancária. Estas restrições criam a procura que os mercados de skins de terceiros vêm satisfazer: uma procura gerada pelos limites de listagem e de carteira, enquanto as próprias regras da Valve impedem que os operadores comerciais a satisfaçam.\n\nLimites de mercado da Steam ↗ arquivado 2026-09-21 ↗\n\n04 / DENTRO DO LIMITE DE APOIO\n\nResponsável pela gestão de dados.Responsável pelo acesso.\n\nA política de privacidade da Valve prevê expressamente a partilha de dados pessoais com prestadores de serviços de assistência externos, na medida do necessário para a prestação dessa assistência.\n\nO JOGADORConta e comprovativos\n→\nVÁLVULAProcesso de recuperação\n→\nPRESTADOR DE APOIOAcesso delegado\n\nPolítica de Privacidade §5.2 ↗ · A própria política da Valve autoriza o acesso de terceiros para fins de assistência. As questões em aberto são: que autorizações foram concedidas, que registos de auditoria existem e o que aconteceu quando o acesso foi alegadamente utilizado de forma indevida.\n\n2015\nA balança era pública\n\nValve reconheceu a ocorrência generalizada de roubos de contas e descreveu as medidas de proteção.\n\nValve publicação ↗arquivado 2026-08-09 ↗\n2015\nValve subcontratou o serviço — e assim o afirmou\n\nA Valve mantém uma pequena equipa interna de Steam Liderança de Apoio e afirmou que \"contratou algumas empresas diferentes\" para gerir o apoio (Erik Johnson, Valve, à Kotaku); o n.º 5.2 da sua política de privacidade autoriza o acesso desses terceiros aos dados dos utilizadores. Qual é o prestador de serviços que tem acesso à recuperação de contas? Valve nunca o revelou — A discussão na comunidade menciona empresas como a Concentrix, mas nenhuma delas foi Valve-confirmada. O serviço externalizado já estava em funcionamento anos antes de qualquer uma das admissões abaixo.\n\nKotaku: Valve no seu apoio ↗arquivado 2025-07-11 ↗\n2023\nA primeira admissão\n\nA equipa de CS:GO da Valve assume por escrito a responsabilidade pela violação de uma conta ocorrida através do seu próprio processo de pedido de ajuda e anula as transações.\n\nAbrir o processo de subcontratação ↓\n2025\nA segunda admissão\n\n33 meses depois, o Suporte Steam escreve que um técnico «não seguiu o nosso processo, o que resultou na restauração da sua conta a nome de outra pessoa». O mesmo canal. O mesmo resultado.\n\nDexerto, 14 de novembro de 2025 ↗\n\nDOINDO DO CASO / A HFB E AS ALEGAÇÕES DE EXTERNALIZAÇÃO\n\nA forma de entrar era o próprio Steam Support.Valve afirmou-o por escrito.\n\nNa resposta do serviço de apoio reproduzida pelo Dexerto, a equipa de CS:GO da Valve assume a responsabilidade pela violação de uma conta através do processo de pedido de ajuda — o seu próprio canal, não uma página de phishing nem o utilizador. Os artigos foram recuperados e as transações anuladas, o que constitui a solução que Valve diz às outras vítimas que não existe. O inventário da HFB foi registado em $2,000,000+ nesse dia e $3,000,000+ no acompanhamento; O Qkss perdeu $1,000,000+ da mesma forma e não ganhou nada.\n\nRESPOSTA DO SUPORTE / REPRODUZIDO POR DEXERTO · 21 de fevereiro de 2023\n«comprometido através de um pedido de assistência, pelo qual a equipa do CS:GO assume a responsabilidade»\nLeia a reportagem e a mensagem reproduzida ↗ arquivado 2025-08-18 ↗\n01 / QUE VÁLVULA ADMITIU\nO seu próprio canal de apoio foi a porta de entrada\n\nA resposta aborda a conta comprometida e a anulação das suas transações. Valve anulou-as — pelo que as transações eram reversíveis. O ticket original autenticado não consta desta coleção.\n\n02 / O QUE AS DEMISSÕES NÃO RESOLVERAM\nA mesma porta voltou a abrir-se em novembro de 2025\n\nA empresa contratada despediu toda a sua equipa de apoio Steam — notícia divulgada pela Mzkshow através do Dexerto, e não por meio de um comunicado Valve da empresa. Trinta e três meses depois, a Steam Support escreveu a outro cobrador que «um técnico de apoio que tratou do pedido de ajuda não seguiu o nosso processo, o que resultou na restauração da sua conta a nome de outra pessoa». Frase da própria Valve, sobre o mesmo canal.\n\nA segunda admissão, 14 de novembro de 2025 ↗\n03 / O QUE É O OPEN\nValve nunca revelou o nome do empreiteiro\n\nNem o contratante nem a localização são identificados por estas fontes. Isso não constitui uma lacuna na reportagem — trata-se de uma informação que a Valve não revelou sobre quem tinha acesso às contas dos utilizadores.\n\nRelato contemporâneo do caso ↗\n\nTrês perguntas às quais Valve ainda não respondeu: quem poderia anular a recuperação da conta, o que a auditoria de acesso revelou e o que mudou posteriormente.\n\nAlegações posteriores constantes do arquivo de apoio conservado\n\nDuas publicações no Reddit de 2024 dão conta de novas investigações do Mzkshow — um caso de levantamento de uma proibição VAC, em julho de 2024, e um caso de inventário $13,000, em dezembro de 2024. Trata-se de incidentes relatados separadamente. A questão da responsabilização em cada um deles é idêntica: quem tinha acesso de sobreposição, o que a auditoria revelou e o que mudou.\n\n14 de julho de 2024 · recuperação comunicada / caso de proibição VAC ↗2 de dezembro de 2024 · relatado $13,000 caso de inventário ↗arquivado 2025-08-05 ↗Duas publicações guardadas, linhas de origem e hashes ↓\n\n05 / ACOMPANHAR A PERDA\n\nQualquer montanteprecisa de uma capa.\n\nDez casos, de junho de 2022 a março de 2026. Cada montante corresponde ao valor publicado pela fonte indicada — $6,300,000, $2,000,000+, $1,000,000+, ≈$320,000, ≈$300,000, e desceu para 288 €. O Valve guarda o registo de transações, o registo da sessão e a pista de auditoria de suporte para cada uma delas, mas não apresentou nenhum deles.\n\nCANAL DE APOIO21 JUNHO 2022\n$2,000,000+\nHFB — the largest inventory in the game\n\nAVALIAÇÃO DO INVENTÁRIO DIVULGADA · AUMENTADA PARA MAIS DE $3M NA ATUALIZAÇÃO DE 2023 DE FEVEREIRO\n\nSete «Dragon Lores» de coleção e o Karambit «Blue Gem» n.º1; só essa faca custa cerca de $1.26m. Inativo há três anos, com o autenticador ainda ativado; e-mail e palavra-passe alterados através do processo de recuperação do apoio ao cliente. A Valve reverteu as transações — e assumiu a sua responsabilidade por escrito. Antes da reversão, já tinham sido levantados cerca de $200,000+ em receitas através do market.csgo.com, que efetua pagamentos em dinheiro e criptomoedas. Uma reversão devolve uma skin, não o dinheiro que alguém já depositou. A reversão também causou um problema: um comprador escondeu o seu «Souvenir Dragon Lore» numa unidade de armazenamento no jogo; o script não conseguiu ver o interior do próprio contentor; e Valve duplicou um item no valor de $130,000 ao anular um roubo — detetado através dos IDs dos itens e de denúncias da comunidade, eliminado em julho 2022,; o comprador foi reembolsado pela BUFF em vez de Valve.\n\nDexerto, dia do roubo ↗\nCARTEIRA E COMPRAS07 JUL 2022\n>$500\n44 disputed Market purchases\n\nGASTOS DECLARADOS COM CARTEIRA · USD\n\nUm utilizador denuncia compras não autorizadas de itens de baixo valor no Dota 2 e uma resposta insatisfatória do serviço de apoio ao cliente.\n\nLeia a queixa e veja as capturas de ecrã associadas ↗\nVIOLAÇÃO DA PLATAFORMA14 2022 de agosto\n$6,300,000\nCS.Money — 19,000+ skins dos bots\n\nAVALIAÇÃO DE PREÇO · PRIMEIRA ESTIMATIVA $1.6M\n\nOs atacantes apoderaram-se dos ficheiros do autenticador móvel dos bots de negociação da plataforma e esvaziaram-nos, distribuindo parte do saque a negociadores conhecidos para confundir as pistas. Investigadores da comunidade identificaram 55 contas de atacantes em poucas horas. Valve não reverteu nada — um site de terceiros situa-se fora de Steam, afirmou o mesmo Steam cujo inventário, transações API e sistema de contas foram alvo do roubo do início ao fim.\n\nLeia o relato da época ↗\nCANAL DE APOIONOTÍCIA 21 FEV 2023\n$1,000,000+\nQkss — a mesma porta, o mesmo ator, resposta oposta\n\nAVALIAÇÃO DO INVENTÁRIO DECLARADO\n\nTratado da mesma forma que o caso HFB, pelo mesmo interveniente, através do mesmo pedido de assistência técnica. O caso HFB foi resolvido na íntegra oito meses antes. O caso Qkss não. Não há nada no registo publicado que distinga os dois casos, exceto a dimensão do público.\n\nDexerto sobre a investigação do Mzkshow ↗\nCANAL DE APOIONOTÍCIA DE 2023 DE FEVEREIRO\n≈ $320,000\nA própria prática de abuso de informação privilegiada — um ano dessa prática\n\nRECEITAS AUFERIDAS AO LONGO DE CERCA DE UM ANO · NÃO SE TRATA DE UMA AVALIAÇÃO DE EXISTÊNCIAS\n\nO acesso pela equipa de apoio permitiu consultar o histórico da conta até 15 anos atrás: a primeira chave de CD, o primeiro e-mail, o primeiro cartão — exatamente as provas que o processo de recuperação exige. Quem detém a base de dados ganha sempre essa discussão contra quem detém a conta. Um M4A4 Howl roubado com holos «iBUYPOWER» e «Titan Katowice» 2014 foi vendido por $35,000 e acabou nas mãos do b1t da NAVI, que não tinha como saber. A resposta do contratante foi despedir todos os funcionários que trabalhavam no apoio ao Steam.\n\nNotícias da Escorenews sobre a mesma investigação ↗\nCARTEIRA E COMPRAS09 DEC 2023\n€288\nPerda da carteira, apesar da proteção em duas etapas\n\nTRUSTPILOT · ÍNDICE DE FONTES 16\n\nO avaliador refere que a sua conta foi pirateada e que lhe foi recusada ajuda relativamente às despesas no Market. A exportação não contém qualquer URL de avaliação individual.\n\nVerificar a proveniência da fonte ↗\nRECUPERAÇÃO DE CONTAS02 DEC 2024\n$13,000\n«Matvey» — dois anos após os despedimentos\n\nESTIMATIVA DO INVENTÁRIO DO AUTOR\n\nA recuperação foi concedida a alguém que forneceu dados da conta que o próprio titular não conseguiu confirmar. O mesmo procedimento, o mesmo resultado, depois de o prestador de serviços ter encerrado o seu serviço de apoio ao cliente Steam.\n\nLeia a alegação arquivada ↗\nRECUPERAÇÃO DE CONTAS09 MAIO DE 2025\n≈ $10,000\nRecuperação através do bilhete de outra pessoa\n\nPERDA DE ARTIGO OBJETO DE RECLAMAÇÃO · USD\n\nUm utilizador do Quebeque alega que o serviço de apoio redefiniu a palavra-passe e removeu a proteção da conta na sequência de um pedido de outra pessoa.\n\nLeia a queixa em primeira pessoa ↗\nCANAL DE APOIO13 NOV 2025\n≈ $300,000\nHawkeye337 — e a segunda confissão por escrito dValve\n\nCOLEÇÃO COMPLETA DE HOLOGRAMAS «2014» DE KATOWICE\n\nO atacante exigiu um bitcoin d1 e começou a transferir a coleção para contas Negevs para a destruir. Steam Resposta do Apoio ao Cliente: «Um técnico de apoio que tratou do pedido de ajuda não seguiu o nosso processo, o que resultou na restauração da sua conta a nome de outra pessoa.» Trinta e três meses após a primeira admissão, a mesma situação. Restaurada poucas horas depois de o tópico se ter tornado tendência em X. O Qkss não tinha esse público.\n\nDexerto, 14 Nov 2025 ↗\nCARTEIRA E COMPRAS29 MAR 2026\n$50\nRecargas não autorizadas e jogos oferecidos\n\nTRUSTPILOT · ÍNDICE DE FONTES 290\n\nO avaliador alega despesas não autorizadas e pedidos de reembolso não atendidos. A URL específica da avaliação não consta da exportação.\n\nVerificar a proveniência da fonte ↗\n\nA atribuição e os montantes mantêm-se tal como relatados por cada fonte. Valve dispõe dos registos de transações, dos registos de sessão e da pista de auditoria de apoio para cada um destes casos. Apresente-os. Uma publicação preservada no Reddit não resolve a questão — são os próprios registos de Valve que o fazem.\n\nA COLEÇÃO / APÓS A VERIFICAÇÃO\n\n231,829 contas à venda.Valve contém os registos de cada um.\n354 → 201\nRegistos do Trustpilot\n\nForam removidas 153 linhas duplicadas. Os URLs das avaliações individuais não foram preservados na exportação.\n\n231,829\nSteam listagens de contas\n\n33,509 classificado como «registo automático»; 198,320 sob a etiqueta «ladrão» do colecionador. Os anúncios não constituem vendas concluídas.\n\nAuditoria à cobrança ↓Pesquisar no arquivo de código-fonte ↗",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "A sua conta.O acesso deles.Quem atende?"
          },
          {
            "level": 2,
            "id": null,
            "text": "A automatização temdocumentação escrita."
          },
          {
            "level": 3,
            "id": null,
            "text": "ArchiSteamFarm"
          },
          {
            "level": 2,
            "id": null,
            "text": "Qual a teclaDe que é que estamos a falar?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Chave pessoal da API Web"
          },
          {
            "level": 3,
            "id": null,
            "text": "Chave da API Web do editor"
          },
          {
            "level": 3,
            "id": null,
            "text": "OpenID / tokens de sessão"
          },
          {
            "level": 3,
            "id": null,
            "text": "A automação pode utilizar mais do que uma chave API."
          },
          {
            "level": 2,
            "id": null,
            "text": "Ainda a jogar.Já foi revelado."
          },
          {
            "level": 3,
            "id": "session-hidden-title",
            "text": "A confiança surge antes mesmo do site."
          },
          {
            "level": 2,
            "id": null,
            "text": "O artigo pode ser raro.O limite mantém-se."
          },
          {
            "level": 2,
            "id": null,
            "text": "Responsável pela gestão de dados.Responsável pelo acesso."
          },
          {
            "level": 3,
            "id": null,
            "text": "A balança era pública"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve subcontratou o serviço — e assim o afirmou"
          },
          {
            "level": 3,
            "id": null,
            "text": "A primeira admissão"
          },
          {
            "level": 3,
            "id": null,
            "text": "A segunda admissão"
          },
          {
            "level": 3,
            "id": null,
            "text": "A forma de entrar era o próprio Steam Support.Valve afirmou-o por escrito."
          },
          {
            "level": 4,
            "id": null,
            "text": "O seu próprio canal de apoio foi a porta de entrada"
          },
          {
            "level": 4,
            "id": null,
            "text": "A mesma porta voltou a abrir-se em novembro de 2025"
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve nunca revelou o nome do empreiteiro"
          },
          {
            "level": 2,
            "id": null,
            "text": "Qualquer montanteprecisa de uma capa."
          },
          {
            "level": 3,
            "id": null,
            "text": "HFB — the largest inventory in the game"
          },
          {
            "level": 3,
            "id": null,
            "text": "44 disputed Market purchases"
          },
          {
            "level": 3,
            "id": null,
            "text": "CS.Money — 19,000+ skins dos bots"
          },
          {
            "level": 3,
            "id": null,
            "text": "Qkss — a mesma porta, o mesmo ator, resposta oposta"
          },
          {
            "level": 3,
            "id": null,
            "text": "A própria prática de abuso de informação privilegiada — um ano dessa prática"
          },
          {
            "level": 3,
            "id": null,
            "text": "Perda da carteira, apesar da proteção em duas etapas"
          },
          {
            "level": 3,
            "id": null,
            "text": "«Matvey» — dois anos após os despedimentos"
          },
          {
            "level": 3,
            "id": null,
            "text": "Recuperação através do bilhete de outra pessoa"
          },
          {
            "level": 3,
            "id": null,
            "text": "Hawkeye337 — e a segunda confissão por escrito dValve"
          },
          {
            "level": 3,
            "id": null,
            "text": "Recargas não autorizadas e jogos oferecidos"
          },
          {
            "level": 2,
            "id": null,
            "text": "231,829 contas à venda.Valve contém os registos de cada um."
          },
          {
            "level": 3,
            "id": null,
            "text": "Registos do Trustpilot"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam listagens de contas"
          }
        ],
        "links": [
          "https://phishdestroy.io/live-intel/?category=steam",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/lzt.market.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-evidence-lzt.json",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://github.com/JustArchiNET/ArchiSteamFarm/blob/main/ArchiSteamFarm/ArchiSteamFarm.csproj",
          "https://github.com/JustArchi",
          "https://github.com/renovate[bot]",
          "https://github.com/JustArchi-ArchiBot",
          "https://github.com/dependabot-preview[bot]",
          "https://github.com/renovate-bot",
          "https://github.com/actions-user",
          "https://github.com/dependabot-support",
          "https://github.com/Abrynos",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/automation-map.json",
          "https://phishdestroy.io/steam_dossier/pt/output_steam_network/network.html",
          "https://phishdestroy.io/steam_dossier/pt/output_steam_network/raw_data.json",
          "https://partner.steamgames.com/doc/webapi_overview/auth",
          "http://web.archive.org/web/20260915025812/https://partner.steamgames.com/doc/webapi_overview/auth",
          "https://partner.steamgames.com/doc/webapi/ISteamUserAuth",
          "http://web.archive.org/web/20260829124950/https://partner.steamgames.com/doc/webapi/ISteamUserAuth",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "http://web.archive.org/web/20260924181824/https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://store.steampowered.com/privacy_agreement/",
          "https://store.steampowered.com/oldnews/19618",
          "http://web.archive.org/web/20260809125516/https://store.steampowered.com/oldnews/19618",
          "https://kotaku.com/valve-explains-why-steam-customer-service-is-still-terr-1736988223",
          "http://web.archive.org/web/20250711004653/https://kotaku.com/valve-explains-why-steam-customer-service-is-still-terr-1736988223",
          "https://www.dexerto.com/counter-strike-2/valve-saves-hacked-cs2-player-threatened-with-ransom-over-300000-of-rare-stickers-3283135/",
          "https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "http://web.archive.org/web/20250818113925/https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "https://lis-skins.com/ru/blog/krupneisaia-mosenniceskaia-sxema-v-istorii-steam/",
          "https://www.reddit.com/r/cs2/comments/1e38jo4/stealing_accounts_and_removing_vac_bans_a_new/",
          "https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "http://web.archive.org/web/20250805141942/https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/outsourcing-archive-records.json",
          "https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "https://escorenews.com/en/csgo/news/44087-valve-steam-support-employee-accused-of-selling-inactive-accounts-inventories-worth-six-figures-b1t-has-one-of-these-skins",
          "https://phishdestroy.io/steam_dossier/pt/PART2_RESEARCH.md",
          "https://www.reddit.com/r/GlobalOffensive/comments/1h56shi/steam_support_is_stealing_accounts/",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/design-review/part2/quality-review.json",
          "https://phishdestroy.io/steam_dossier/pt/steam_evidence_archive.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/pt/investigation_part2.content.json",
      "export_json_sha256": "b4909d443de3e38a32b8a8375e590c5a8364f8e9283c9eb4f1ebadde696fa710"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "pt/legal_analysis.html",
      "language": "pt",
      "title": "Os termos deles, os seus direitos — O Dossiê «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/pt/legal_analysis",
      "source_html_sha256": "ea9394f1c788061762a95d7d6f40a6fca59261a2bdacd3c66bb0b533f33fb21d",
      "exported_at": "2026-09-29T00:18:08.043Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "legal_analysis.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/pt/legal_analysis.pdf?v=print-20260929-v5",
        "sha256": "bff20501d115f4e03ffefa3c7d967a90ee3123cc9c5f4a7af414c4f5e230900e",
        "bytes": 106424,
        "pages": 8
      },
      "integrity": {
        "signed_object": "legal_analysis.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "legal_analysis.content.json.asc",
        "digest_file": "legal_analysis.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify legal_analysis.content.json.asc legal_analysis.content.json",
          "sha256sum -c legal_analysis.content.json.sha256"
        ]
      },
      "content": {
        "text": "Relatório jurídico e económico\nAnálise jurídica — Termos de serviço e conformidade regulamentar\n\nNos termos deles. Os seus direitos.\n\nO QUE ESTA SECÇÃO DEMONSTRA\n\nEsta auditoria jurídica forense avalia a assimetria contratual entre a Valve Corporation e os utilizadores de Steam nas principais jurisdições regulatórias. Estabelece de que forma a licença de subscrição revogável priva o consumidor da propriedade legal, analisa a jurisprudência do Tribunal de Justiça da União Europeia sobre o esgotamento do direito de revenda digital e examina a conformidade com a Lei dos Serviços Digitais (DSA) e o artigo GDPR, n.º 15.. A análise demonstra como os mecanismos de aplicação automatizados funcionam sem vias de recurso significativas, enquanto as taxas de mercado da plataforma extraem sistematicamente valor económico de cada transação entre pares.\n\n← Voltar ao resumo executivo\n\nO presente relatório apresenta uma análise jurídica, económica e técnica do fosso existente entre as regras declaradas da plataforma «Steam» e a posição do consumidor: aplicação automatizada com poucas vias de recurso e um controlo corporativo alargado sobre os ativos digitais. Os dados são apresentados com indicação da fonte; nos casos em que não foi possível identificar a fonte primária de um dado, este foi omitido.\n\nVector 1\n\nSubstituir a «propriedade» por uma licença revogável, de modo a que os ativos digitais possam ser retirados nos termos do acordo.\n\nVector 2\n\nSistema de aplicação automática de sanções (VACNet), cujas proibições, segundo o site Steam Support, não podem ser revertidas.\n\nVector 3\n\nControlos de contas e ativos, combinados com uma taxa de mercado «15%» CS2 (5% Steam + 10% — taxa de editor), que retira valor do ecossistema em cada revenda.\n\nAssimetria dos termos\nRenúncia de responsabilidade e licença revogável\n2.1 O modelo de «assinatura» versus os direitos de propriedade\n\nA secção 2 do Contrato de Assinante da Steam concede aos utilizadores apenas um licença pessoal, não exclusiva, intransmissível e revogável. Nos termos do acordo, a Valve pode encerrar contas a qualquer momento, e os saldos não utilizados da Carteira Steam podem ser perdidos.\n\n2.2 A ilusão do reembolso vs. a Diretiva da UE relativa aos direitos dos consumidores\nQuadro jurídico\tMecanismo de reembolso\tLimitação\nEU Consumer Rights Directive\tUnconditional 14-day right of withdrawal on digital content\tWaived if download begins with explicit consumer consent\nSteam SSA\t14 days / under 2 hours played\tValve may deny at its discretion for \"abuse\"\nAvaliação\n\nValve A UE condiciona o direito legal de rescisão de 14-dias ao seu próprio período de «14 dias / 2 horas», que deve ser aceite no momento do download antes de o produto poder ser avaliado. Essa política restringe — e não alarga — o direito legal; se o faz de forma legal é uma questão que cabe à autoridade competente decidir, não sendo uma conclusão aqui afirmada.\n\nContencioso\nMercado Secundário e Direito da Concorrência\nUFC Que Choisir contra Valve — França\n2019\nTribunal de Paris: a doutrina do esgotamento dos direitos aplica-se aos jogos digitais — a revenda é lícita\nOutubro de 2022\nO Tribunal de Recurso de Paris revoga a decisão\n23 Outubro de 2024\nTribunal de Cassação (Supremo Tribunal): os videojogos são «obras complexas» ao abrigo da Diretiva InfoSoc, e não software. Revenda digital proibido. O «Valve» prevalece.\nProcesso antitrust contra a Wolfire Games — Estados Unidos (Processo «In re Valve Antitrust Litigation», n.º 2:21-cv-00563)\n\nA cláusula de Nação Mais Favorecida (PMFN) da plataforma Valve proíbe os programadores de venderem chaves «Steam» a preços mais baixos em qualquer outra plataforma. As lojas concorrentes — mesmo aquelas que cobram uma comissão «12%», em contraposição à comissão «30%» da Valve — não podem repercutir essa poupança nos consumidores.\n\n336total de funcionários da Valve (2021). Fonte: documentos de instrução processual divulgados.\n79funcionários responsáveis pela gestão de toda a plataforma Steam. Fonte: documentos de instrução processual divulgados.\n$3.5Mlucro líquido por colaborador. Fonte: documentos de instrução processual tornados públicos.\n\nOs registos de produção de provas já desclassificados revelam que $8.5B de receita bruta em 2021 sobre os funcionários d336. O 79-equipa «Steam» tratou de 373,000+ pedidos de assistência diários, encaminhando-os para centros de atendimento automatizados e subcontratados.\n\nANEXO DO PROCESSO NÃO SELADO · W.D. WASH. PROCESSO N.º 2:21-CV-00563Nota interna de investigação\n\nTim Sweeney (CEO da Epic Games) a Gabe Newell: «Porque é que a Steam continua a ficar com 30% do valor bruto, quando o processamento de pagamentos custa 2–5% e a largura de banda CDN custa $0.002/GB? Se subtrairmos os jogos mais populares 25 do Steam, aposto que a Valve obteve mais lucro com a maioria dos jogos seguintes 1,000 do que os próprios criadores.»\n\nScott Lynch (Diretor de Operações da Valve Corporation) – mensagem interna endereçada a Gabe Newell: «Estás zangado, mano?»\n\nContestação ao depoimento sob juramento (Bloomberg, 2026): Nos termos do artigo 30 (b) (1) do regulamento relativo ao depoimento, Gabe Newell testemunhou que «AValve não tem qualquer política nem prática de impor preços a programadores de software de terceiros noutras plataformas.» Os queixosos confrontaram a Newell com memorandos internos da Valve que comprovavam uma política ativa de controlo de preços e ameaças de exclusão da lista de produtos aos programadores que praticavam preços mais baixos em lojas concorrentes. No final de março 2026,, o Tribunal Federal indeferiu o pedido de julgamento sumário da Valve, remetendo a ação coletiva dos programadores 32,000-para julgamento por júri.\n2024 de novembro\n\nAção coletiva admitida para ~ Os programadores do32,000 que pagou comissões desde janeiro de 2017,, além de uma ação coletiva paralela movida por consumidores.\n\nIndemnizações reclamadas\n\n$3.1B\nTriplicado ao abrigo da legislação antitrust dos EUA = $9.3B exposição potencial.\n\n2026: de junho Uma nova ação judicial alega que a Microsoft e a Valve celebraram um acordo de cartel com o objetivo de restringir a concorrência na distribuição de jogos para PC.\n\nCrime Financeiro e Combate ao Branqueamento de Capitais – Admissão Formal\nValve Confissão oficial: Worldwide Fraud Liquidations (28, 1 de outubro de 2019)\n\nNo dia 28 de outubro de 2019, Valve, a empresa pôs oficialmente termo à comercialização e à revenda no mercado de chaves de contentores do Counter-Strike recém-adquiridas. No seu comunicado público oficial (blog.counter-strike.net/2019/10/26113), a Valve Corporation admitiu por escrito que a economia virtual que criou se tinha tornado um centro internacional de lavagem de dinheiro:\n\n«No passado, a maioria das transações de chaves que observámos era entre clientes legítimos. No entanto, as redes de fraude a nível mundial passaram recentemente a utilizar chaves do CS:GO para liquidar os seus ganhos. Neste momento, acredita-se que quase todas as compras de chaves que acabam por ser trocadas ou vendidas no mercado tenham origem em fraudes.»\n\nContexto regulamentar: Esta confissão surgiu na sequência do ultimato formal da Comissão de Jogos de Azar do Estado de Washington (WSGC) à Valve e das ordens de cessação e desistência de julho 2016 emitidas pelo Conselheiro Geral da Valve, Karl Quackenbush, aos domínios de apostas com skins da 23 (incluindo CSGO Lotto, CSGOLounge e OPSkins), apenas depois de uma investigação criminal sobre jogos de azar ter ameaçado as operações da plataforma.\n\nCompetência\nUm detentor de direitos na Rússia, inacessível para o utilizador\n\nO Acordo de Subscrição apresenta a Valve como uma entidade que tem poucas obrigações e à qual ninguém consegue chegar: os bloqueios são permanentes, os recursos são recusados e o acesso é retirado a territórios inteiros com uma única frase sobre «regiões sancionadas». Em contraste com essa postura, está o que a Valve faz quando os seus próprios interesses comerciais estão em jogo numa jurisdição que, de resto, trata como difícil.\n\nValve v. Touch Skins — reclamação relativa à propriedade intelectual antes do julgamento, Rússia\n1 2026 de setembro\nA Valvee, através do escritório de advogados russo Melling, Voitishkin & Partners, envia uma carta de notificação pré-judicial aos operadores de Skins táteis, um grande trocador de skins para o CS2, enviado pelos Correios russos e por e-mail.\nFundamentos\nTrês grupos de alegadas violações: direitos exclusivos sobre o software; direitos sobre o aspeto dos skins de armas, facas e luvas; e as marcas registadas dValve. A conduta dos operadores é caracterizada como deliberada e prolongada.\nProcura\nInterrompa imediatamente o funcionamento e elimine toda a infraestrutura — o software código-fonte, sítios Web e páginas nas redes sociais — caso contrário, a Valve reserva-se o direito de intentar uma ação num tribunal russo por uma compensação monetária significativa e remeter o assunto para autoridades policiais para uma avaliação criminal.\nResultado\nApós receber a carta, a plataforma anunciou que iria encerrar as suas atividades. Trata-se do primeiro caso em que a «Valve» recorreu a medidas legais contra um programador de «skin-changers» na Rússia.\n\nNoticiado pelo analista de dados Maxim «GabeFollower» Poletaev (X, ~11 de setembro de 2026) e pela imprensa russa especializada em jogos. Trata-se de uma alegação pré-julgamento, não de uma ação judicial interposto; não existe qualquer número de processo público. Tratado aqui tal como foi noticiado, não como um registo judicial. Fontes: dota2.ru arquivado em 2026-09-24 ↗ · Shazoo.\n\nA mesma jurisdição, na direção oposta\n\nValve não é estranho ao sistema jurídico e regulamentar russo. É está em conformidade com a Roskomnadzor: a pedido da entidade reguladora, foram removidas as páginas da comunidade 260+ Steam que continham material proibido, e a Roskomnadzor declarou publicamente que o site Steam cumpre os requisitos da legislação. A lei russa relativa às «páginas de destino» (Lei Federal 236-FZ, em vigor desde 2022) exige que as grandes plataformas estrangeiras da Internet que prestam serviços a utilizadores russos estabeleçam uma presença local e uma conta de contacto junto da Roskomnadzor. A Valve não só cumpre as ordens de remoção emitidas por essa entidade reguladora como, agora, recorre a advogados russos e à ameaça dos tribunais russos para proteger as suas «skins» enquanto propriedade intelectual.\n\nAssim, a plataforma mostra-se acessível, competente e firme na defesa dos seus direitos, precisamente no que diz respeito às suas receitas. O contraste está no utilizador: um cliente pagante numa região sujeita a sanções é informado de que a relação chegou ao fim, o acesso à comunidade fica bloqueado até 2038, o ticket ser encerrado, e não existe qualquer fórum onde a decisão possa ser contestada — «Ficaram mais do que satisfeitos por receber o meu dinheiro e processar as minhas transações», tendo o reembolso dessa mesma conta, proveniente do mesmo endereço IP iraniano, sido aprovado um ano antes (r/pcgaming, 4 de agosto de 2026; mais cartas de notificação em a exposição sobre a economia dos cartões). O «Valve» recorre a todo o aparato de um sistema jurídico nacional para defender uma skin; não concede qualquer tipo de processo ao utilizador que comprou as skins.\n\nValve trata essa mesma jurisdição como uma em que pode agir e cumprir as suas obrigações, sempre que o interesse em causa seja o dValve — advogados russos, a ameaça dos tribunais russos, as ordens de remoção da Roskomnadzor a que dá resposta —, ao mesmo tempo que trata as suas obrigações para com os utilizadores desse mercado, e de todos os outros, como estando totalmente fora de qualquer processo. É um detentor de direitos no que diz respeito às suas receitas e uma parte inacessível no que diz respeito aos direitos dos utilizadores.\n\nFontes: TASS (RKN: em conformidade com a norma Steam) · Lei Federal n.º 236-, FZ.\n\nOportunismo jurídico\nA capitulação da cláusula de arbitragem\n2023 — o ataque\n\nOs escritórios de advogados (Zaiger LLC, Mason LLP) recrutaram milhares de utilizadores através das redes sociais e apresentaram, simultaneamente, dezenas de milhares de pedidos de arbitragem individuais.\n\nA exposição de Valve\n\n$225M+\nem taxas de apresentação de pedido de arbitragem não reembolsáveis, antes de qualquer processo ter sido apreciado quanto ao mérito. Calculado ao abrigo das Regras de Arbitragem para Consumidores da Associação Americana de Arbitragem (AAA) e dos Anexos Complementares sobre Arbitragem em Massa. Os requerentes, representados pela Zaiger LLC e pela Mason LLP, apresentaram cerca de75,000 pedidos de arbitragem individuais contra a Valve Corp. (em paralelo com as ações antitrust em Wolfire Games LLC e outros contra Valve Corp., Processo n.º 2:21-cv-00563-JCC, W.D. (Wash.). De acordo com as tabelas de taxas para consumidores da AAA, a empresa requerida paga taxas administrativas não reembolsáveis relativas ao processo e depósitos para a nomeação de árbitros no valor de cerca de $3,000+ por caso individual (75,000 processos × $3,000 = cerca de $225M em responsabilidades processuais iniciais). Consulte os relatórios jurídicos da Bloomberg Law e da Reuters sobre a exposição à arbitragem em massa no setor tecnológico (2023–2024).\n\nPeríodo\tMecanismo de resolução de litígios da SSA\tEfeito observado\tResultado\nBefore Sep 2024\tMandatory individual arbitration + class-action waiver\tIndividual litigation becomes economically irrational for users\tMass arbitration → $225M fee threat\nAfter Sep 2024\tDisputes in King County, WA courts only\tArbitration costs are avoided; cases consolidate in a single forum\tClass actions now possible\nConclusão\n\nDurante mais de dez anos, a SSA exigiu que os utilizadores renunciassem ao seu direito a um julgamento por júri, optando pela arbitragem individual. Depois de os pedidos de arbitragem em massa terem tornado esse mecanismo financeiramente oneroso para a «Valve», a SSA foi alterada para encaminhar os litígios para os tribunais do Condado de King. A alteração foi apresentada sem uma opção de exclusão significativa; a alternativa à aceitação era perder o acesso aos ativos digitais adquiridos através da eliminação da conta.\n\nAplicação algorítmica\nVACNet, presunção de culpa e falsos positivos\n2023 de outubro — AMD Anti-Lag+\n\nUma atualização do controlador da AMD (v23.10.1) ativou o Anti-Lag+ no CS2, o que interceptou funções das DLL do jogo. O VAC classificou isto como injeção de código de batota e aplicou banimentos permanentes a milhares de utilizadores legítimos antes de o site Valve ter intervindo.\n\n2023, de dezembro — alta resolução (DPI)\n\nOs jogadores com um DPI superior a 10,000 que giravam rapidamente a câmara foram banidos de forma permanente. O VACNet não conseguiu distinguir o movimento físico do rato de um cheat do tipo «spinbot».\n\nCategoria de apoio\tTempo de resposta declarado\tResultado efetivo\nRefund requests\t50 min – 1.5 hr\tAutomatic approval (<14 days, <2 hours played)\nAccount security / recovery\t3–12 hours\tDepends on documentation provided\nContesting a VAC ban\tForm response\tComplete refusal. Support cannot reverse VAC decisions. The ban is permanent.\nPolítica oficial do «Valve»\n\n«As proibições do VAC são permanentes, não são passíveis de negociação e não podem ser removidas pelo Apoio ao Cliente dSteam.»\n\nO mesmo canal de apoio que comunica o banimento também comunica a recusa de revisão: Steam O apoio afirma que não pode reverter uma decisão do VAC. Para o utilizador, o veredicto do algoritmo é o resultado definitivo.\n\nAspetos económicos da revenda\nControlo sobre os ativos virtuais e a taxa de revenda\nA comissão de mercado do «15%» CS2 — valor deduzido em cada revenda\nIteração\tSaldo do comprador\tO vendedor recebe\t«Burned» (15%)\n1\t$100.00\t$85.00\t$15.00\n2\t$85.00\t$72.25\t$12.75\n3\t$72.25\t$61.41\t$10.84\n10\t$23.16\t$19.68\t~$3.47\nTotal\t$100 → dust\tValve collects the 15% fee on each resale. Users must add new money to keep trading.\nAlteração à regra de troca do CS2 — 2025 de outubro\n\nSem aviso prévio, a Valve alterou as regras do contrato de troca do CS2 para permitir a aquisição garantida de facas e luvas raras em troca de itens de qualidade «Covert». Os preços das facas caíram, os preços dos itens «Covert» subiram acentuadamente e seguiu-se uma onda de vendas em pânico em todo o mercado.\n\nA Valve invoca como base de proteção a Secção 7 da SSA — isenção de responsabilidade pela alteração das regras da plataforma. Os utilizadores assumem o risco numa economia cujas regras Valve podem mudar sem aviso prévio nem compensação. O montante da perda registada a nível do mercado é contestado e não é aqui referido sem uma fonte primária.\n\nResposta regulamentar europeia\nUOKiK, DSA e a Lei da Equidade Digital\nUOKiK — Polónia, maio de 2024\n\nA autoridade antitrust da Polónia (UOKiK) instaurou um processo formal antimonopólio contra a Valve Corporation e cinco editoras/distribuidoras de jogos nacionais relativamente a alegadas práticas de fixação de preços, cláusulas restritivas de paridade de preços e práticas de bloqueio geográfico que levaram os consumidores polacos a pagar até 20% a mais por jogos digitais do que nos mercados vizinhos do EEE. No âmbito do inquérito antimonopólio, os inspetores da UOKiK e a polícia realizaram rusgas ao amanhecer e inspeções de provas nas instalações polacas de editoras e distribuidoras parceiras nacionais (não em escritórios subsidiários dValve, uma vez que a Valve não possui qualquer entidade na Polónia). Multa legal potencial: até 10% do volume de negócios anual. Fonte: Comunicado oficial da UOKiK: «O presidente da UOKiK deu início a um processo contra a Valve e os criadores de jogos», maio de 2024.\n\nLei dos Serviços Digitais (DSA)\n\nExige transparência na moderação automatizada. O site Steam não publica dados sobre falsos positivos/falsos negativos relativos ao VACNet, e o seu canal de apoio ao utilizador indica que as decisões do VAC não podem ser revertidas.\n\nLei da Equidade Digital — 2026\n\nDisposições previstas: acesso duradouro a conteúdos pagos, proibição de «dark patterns» no momento da renúncia a direitos, reconhecimento dos direitos de propriedade sobre ativos digitais e proteção contra o confisco permanente de inventário.\n\nConclusão\nDiscrepâncias documentadas entre as regras e o registo\n1\n\nA disparidade na propriedade. Os utilizadores pagam o preço total por uma licença que o contrato permite que a Valve revogue. O Supremo Tribunal francês (outubro de 2024) determinou que a revenda digital não está protegida, consagrando essa posição na lei.\n\n2\n\nAplicação algorítmica. O VACNet emitiu proibições indevidas (drivers AMD, incidentes relacionados com DPI elevado). O apoio ao cliente do Steam afirma que não pode reverter uma decisão do VAC, pelo que o algoritmo é a palavra final.\n\n3\n\nEconomia nas taxas. A taxa de mercado do CS2 da 15% (5% Steam + 10% taxa do editor) reduz o valor em cada revenda, e as regras da plataforma podem ser alteradas sem aviso prévio; a Valve isenta-se de qualquer responsabilidade por tais alterações ao abrigo do SSA.\n\n4\n\nCláusula de arbitragem suprimida. A SSA abandonou a arbitragem obrigatória em setembro 2024,, depois de que uma onda de pedidos expôs a Valve a cerca de $225M em comissões. Os utilizadores não tiveram qualquer possibilidade significativa de recusar esta alteração.\n\n5\n\nCompetência seletiva. Valve contratou um escritório de advogados russo (Melling, Voitishkin & Partners) e ameaçou intentar uma ação judicial na Rússia contra a Touch Skins, ao mesmo tempo que considerava as suas obrigações para com os utilizadores desse mesmo mercado como estando fora do âmbito de qualquer processo judicial. A Valve atua como titular de direitos quando os seus interesses comerciais estão em causa e como parte inacessível quando se trata dos direitos dos utilizadores.\n\n← Parte I: Contornar o proxy e jogos de azarParte II: Acesso e responsabilização →\n\nAs fontes jurídicas e os registos de processos são citados com referência aos seus editores e repositórios originais. Não se reivindica qualquer direito de propriedade sobre os documentos subjacentes.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Análise jurídica — Termos de serviço e conformidade regulamentar"
          },
          {
            "level": 2,
            "id": null,
            "text": "Renúncia de responsabilidade e licença revogável"
          },
          {
            "level": 3,
            "id": null,
            "text": "2.1 O modelo de «assinatura» versus os direitos de propriedade"
          },
          {
            "level": 3,
            "id": null,
            "text": "2.2 A ilusão do reembolso vs. a Diretiva da UE relativa aos direitos dos consumidores"
          },
          {
            "level": 2,
            "id": null,
            "text": "Mercado Secundário e Direito da Concorrência"
          },
          {
            "level": 3,
            "id": null,
            "text": "UFC Que Choisir contra Valve — França"
          },
          {
            "level": 3,
            "id": null,
            "text": "Processo antitrust contra a Wolfire Games — Estados Unidos (Processo «In re Valve Antitrust Litigation», n.º 2:21-cv-00563)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve Confissão oficial: Worldwide Fraud Liquidations (28, 1 de outubro de 2019)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Um detentor de direitos na Rússia, inacessível para o utilizador"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve v. Touch Skins — reclamação relativa à propriedade intelectual antes do julgamento, Rússia"
          },
          {
            "level": 3,
            "id": null,
            "text": "A mesma jurisdição, na direção oposta"
          },
          {
            "level": 2,
            "id": null,
            "text": "A capitulação da cláusula de arbitragem"
          },
          {
            "level": 2,
            "id": null,
            "text": "VACNet, presunção de culpa e falsos positivos"
          },
          {
            "level": 2,
            "id": null,
            "text": "Controlo sobre os ativos virtuais e a taxa de revenda"
          },
          {
            "level": 3,
            "id": null,
            "text": "A comissão de mercado do «15%» CS2 — valor deduzido em cada revenda"
          },
          {
            "level": 3,
            "id": null,
            "text": "Alteração à regra de troca do CS2 — 2025 de outubro"
          },
          {
            "level": 2,
            "id": null,
            "text": "UOKiK, DSA e a Lei da Equidade Digital"
          },
          {
            "level": 2,
            "id": null,
            "text": "Discrepâncias documentadas entre as regras e o registo"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/pt/#briefing-heading",
          "https://dota2.ru/news/67707-valve-cerez-uristov-napravila-krupnoj-rossijskoj-skincendzer-platforme-trebovanie-o-prekrasenii-deatelnosti/",
          "http://web.archive.org/web/20260924181657/https://dota2.ru/news/67707-valve-cerez-uristov-napravila-krupnoj-rossijskoj-skincendzer-platforme-trebovanie-o-prekrasenii-deatelnosti/",
          "https://shazoo.ru/2026/09/12/190508/valve-cerez-rossiiskix-iuristov-dobilas-zakrytiia-krupnogo-skinceindzera-dlia-cs2",
          "https://www.reddit.com/r/pcgaming/comments/1vf24lu/warning_to_all_gamersexpats_steam_took_my_money/",
          "https://phishdestroy.io/steam_dossier/pt/card_economy.html#asymmetry",
          "https://tass.ru/obschestvo/23235387",
          "https://base.garant.ru/401414628/",
          "https://uokik.gov.pl/postepowanie-wyjasniajace-w-sprawie-valve-i-dystrybutorow-gier",
          "https://phishdestroy.io/steam_dossier/pt/",
          "https://phishdestroy.io/steam_dossier/pt/investigation_part2.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/pt/legal_analysis.content.json",
      "export_json_sha256": "a878cf3d304e013ce4ac30344f88ab824d88422b530ec2a066092ba6e81b9d56"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "pt/license_disclaimer.html",
      "language": "pt",
      "title": "Licença · Direitos · Isenção de responsabilidade — PhishDestroy",
      "source_url": "https://phishdestroy.io/steam_dossier/pt/license_disclaimer",
      "source_html_sha256": "d5ab28989104eab3461e8437ae3ea7fc452659cd20b5a3cde7f186aa861f1d8a",
      "exported_at": "2026-09-29T00:18:08.545Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "license_disclaimer.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/pt/license_disclaimer.pdf?v=print-20260929-v5",
        "sha256": "cf268d9a491704198fd729de53b2d49ce557c9e873f249de28e74a39c0725a26",
        "bytes": 118936,
        "pages": 11
      },
      "integrity": {
        "signed_object": "license_disclaimer.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "license_disclaimer.content.json.asc",
        "digest_file": "license_disclaimer.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify license_disclaimer.content.json.asc license_disclaimer.content.json",
          "sha256sum -c license_disclaimer.content.json.sha256"
        ]
      },
      "content": {
        "text": "PHISHDESTROYInvestigação forense · Valve / Steam\nLicença · Direitos · Isenção de responsabilidade\nLicença e Aviso Legal — Dedicação ao Domínio Público\n\nTodos os direitos entregou-se à humanidade.\n\nO QUE ESTA SECÇÃO DEMONSTRA\n\nO presente documento estabelece a dedicação incondicional ao domínio público (CC0 1.0 Universal) e os termos de licenciamento de software do MIT que regem o Dossier PhishDestroy Steam. Todas as conclusões forenses, conjuntos de dados probatórios, gráficos de rede e metodologias analíticas são colocados irrevogavelmente no domínio público para utilização regulamentar, jurídica e académica sem restrições em todo o mundo.\n\n← Voltar ao resumo executivo\n\nPhishDestroy renuncia a todos os direitos sobre este material — reproduzi-lo, vendê-lo, colocar o seu nome nele. O que se segue são dois documentos apresentados sob a forma de um único texto: uma carta aberta a Valve, escrita da forma como realmente escrevemos, e uma renúncia formal redigida para a entidade que dará continuidade ao projeto.\n\nInvestigação · Valve Corporation / SteamEdição pública — sem prazo de validade, sem direito a devolução\nISENÇÃO\nSecção ILicença — a parte propriamente jurídica, mas humana\n\nPhishDestroy renuncia a todos os direitos sobre este material. Zero. Acabou. Ponto final. Podes reproduzi-lo, vendê-lo, colocar o teu nome nele, tatuá-lo no teu chefe, o que quiseres. Não é necessário atribuir créditos, não é preciso enviar mensagens privadas, nem se espera nenhum cartão de agradecimento.\n\nUma regra concreta (sim, apenas uma)\n\nNÃO és tu que decides se és um terrorista.\n\nSe for um utilizador da Rússia ou de qualquer país sujeito a sanções da OFAC — este material NÃO se destina a si. Não há brechas. Aproveite as suas sanções.\n\nE se alteraste a tua região do «Steam» para a Turquia enquanto estavas em Moscovo — parabéns pela tua geografia criativa. Continuas a ser russo. As sanções continuam a aplicar-se. É literalmente essa a questão.\n\nSecção IIO que é isto e por que razão existe\n\nVamos publicar mais informações sobre Valve do que um funcionário comum da Valve sabe sobre si próprio. Isto não é para nos gabarmos. É simplesmente o que acabou por acontecer.\n\nComo é que chegámos aqui? É uma história engraçada: o Steam, basicamente, criou-nos. Criou-nos à base dos seus burlões, dos seus pedidos de apoio, do seu ecossistema de contorno de banimentos — e agora aqui estamos nós. Sem ressentimentos. Na verdade, é até poético.\n\nPara quem ainda não leu a história de origem — já conhecemos os advogados europeus extremamente caros dValve (a Taylor Wessing, já que perguntaram):\n\nhttps://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d arquivado em 2026-08-21 ↗\n\nUm encontro encantador. Especialmente tendo em conta a tarifa por hora que cobram.\n\nA «Valve» sabia? Sim. A «Taylor Wessing» sabia? Quase de certeza que sim. Mas quando se é assim tão rico, as leis são mais uma questão de atitude do que uma obrigação, certo?\n\nNa verdade, isso é basicamente toda a resposta.\n\nSteam Passámos anos a identificar burlões. Nem sempre de forma intencional — por vezes, os burlões acabavam por ficar associados ao «Valve» apenas por associação. Não estamos a tentar ser dramáticos. Estamos a tentar ser precisos. Para ser sincero, isso é mais difícil para nós do que ser dramáticos — é simplesmente assim que escrevemos.\n\nIsto é um conflito?\n— Não.\n\nSerá que isto se pode resolver?\n— Sim. Mas não vamos assinar nenhum acordo de confidencialidade e não vamos participar em programas de recompensa por erros por trocos.\n\nEsperámos mais de 4 anos até que resolvessem o problema da falsificação de identidade, para só depois podermos escrever sobre o assunto publicamente. Porque, se tivéssemos escrito sobre isso mais cedo, a Steam teria assumido a sua pose de vítima e gritado «ameaça ativa!», oferecendo-nos uma ninharia para assinarmos um documento que nos teria tornado sua propriedade legal para sempre. Não, obrigado.\n\n(Além disso: a própria «Valve» viola o acordo de confidencialidade. São os seus próprios funcionários que o fazem. Os que estão no topo da hierarquia. Mas claro, vamos falar dos nossos.)\n\nSecção IIICarta aberta a Valve — a sério, lê isto\n\nValve: se quiser que este domínio seja retirado do ar, envie-nos um e-mail. Não é necessário recorrer a um advogado externo para essa conversa.\n\nPara quem não sabe: o Dr. Patrick tem um mestrado em Direito Comercial Internacional pela Universidade de Aberdeen e — preparem-se — concluiu, literalmente, a sua tese de doutoramento em Direito das Tecnologias da Informação. Recentemente, tornou-se sócio da Taylor Wessing, uma sociedade cujo modelo de negócio consiste inteiramente em cobrar a empresas como a Valve quantias exorbitantes para protelar os processos até que a outra parte fique sem dinheiro ou sem paciência.\n\nNão o culpamos. Clientes ricos e culpados que pagam à hora — é uma boa jogada para a carreira. Só achamos que não devias ser tu a financiar isso.\n\nO negócio (oferta aberta, sem necessidade de advogados)\n\nO domínio é a única coisa que Valve pode, na prática, alcançar. A investigação, os encaminhamentos e os recursos associados já estão em andamento — e continuam, com ou sem o domínio.\n\nSe quiser o domínio:\n\nDeixe que os seus especialistas em direito das tecnologias da informação definam um preço justo.\n\n50% reverte a favor da Fundação «SEAL».\n\nAcabamos com o domínio. Sem drama. Sem tribunal. Está feito.\n\nIsto não é uma ameaça. É uma proposta direta para a única coisa que está realmente ao teu alcance. Não a conseguirás de outra forma — é assim que as coisas funcionam.\n\nIremos «prejudicar» diretamente a «Valve»? Provavelmente não de uma forma que eles sintam a nível financeiro. Não estamos a iludir-nos. Mas fá-lo-emos com honestidade, abertamente, sem procurar influência — porque não precisamos de influência. Precisamos que o mundo veja o que sempre esteve à vista de todos, se se dedicasse tempo suficiente a procurar.\n\nTemos um5es anos de arquivos. O que os advogados de Valve apresentaram na fase de produção de provas — os dados a que os agentes de apoio têm acesso, as impressões digitais, a documentação que nos entregaram literalmente — é suficiente. Não precisamos de divulgar essa informação em bruto.\n\nQuem fica com o quê\n\nAs entidades reguladoras recebem os originais.\n\nOs investigadores e jornalistas recebem versões censuradas (os relatos das vítimas, os registos de início de sessão das crianças e os comentários encantadores de apoio de Valve foram removidos por razões óbvias).\n\nEntre as contas afetadas encontravam-se contas de menores, que não foram notificados. Esta conclusão consta do dossiê do regulador, com os relatos das vítimas e as credenciais removidos, uma vez que deve ser apresentada a uma autoridade de proteção de dados e não num artigo.\n\nAlém disso, Valve — queremos deixar uma coisa bem clara antes de decidirem como lidar com isto: PhishDestroy é uma comunidade, não uma pessoa. Já aprenderam isso quando enviaram correspondência jurídica à comunidade sem se darem ao trabalho de falar com ela — limitaram-se a extrair dados e a banir as contas.\n\nA comunidade não tem qualquer conflito com o site Valve. Não fomos nós que procurámos isto. Foram os burlões que vocês criaram que nos encontraram. Nós bloqueámo-los. E aqui estamos nós.\n\nSecção III-BOs recursos aliados — uma nota dirigida especificamente a Steam\n\nQueremos ser transparentes quanto à estrutura de amplificação, porque fingir que ela não existe seria desonesto.\n\nA PhishDestroy, pelo que sabemos da situação na comunidade, dispõe de, pelo menos, dois recursos aliados que irão pegar neste material e dar-lhe seguimento.\n\nO que isso significa na prática:\n\nCada um aborda, à sua maneira, temas que se sobrepõem.\n\nSão independentes — não seguem as nossas orientações, nem nós as deles. O tema geral é o mesmo, mas a metodologia é diferente.\n\nNÃO vão ativar a Parte 1.. Estão atentos.\n\nSe o site Valve decidir não retirar o conteúdo do site:\n\nÉ de esperar que apareçam após a Parte 2 ou a Parte 3.\n\nVão retirar o que for útil do nosso trabalho, complementá-lo com o seu próprio trabalho e publicá-lo em seu nome.\n\nÉ exatamente para este tipo de situação que a licença prevista na Secção 1 foi concebida: o material vai para onde é necessário, é complementado, é ampliado — e nem nós nem eles temos a obrigação de atribuir créditos uns aos outros.\n\n(P.S. para os advogados que tenham dúvidas sobre as cadeias de responsabilidade: não existem. Estes recursos não recebem orientações, financiamento nem dados da nossa parte. Eles consultam o que é público e tiram as suas próprias conclusões. Tal como vocês poderiam fazer.)\n\nNão estamos a dizer isto para intimidar. Estamos a dizê-lo para que quem estiver a traçar estratégias do lado dValve disponha de informações precisas sobre como é, na realidade, o panorama informativo.\n\nUm recurso que recorra ao nosso material e o complemente seria uma reportagem. Dois recursos que o façam de forma independente e cheguem a conclusões semelhantes constituem um padrão. São os padrões que chamam a atenção das entidades reguladoras.\n\nSecção IVO dinheiro, as proibições, todo este circo\n\nA questão em relação à proibição de sites de jogos de azar e de burlões por parte dSteam é a seguinte: não se trata de aplicação da lei. Trata-se de angariação de receitas. A Valve embolsa o dinheiro, lava as mãos e, depois, sobe ao palco e conta a toda a gente uma história edificante sobre cartas de Pokémon e basebol.\n\nNos casos em que foram documentadas falhas por parte do serviço de apoio — incluindo a admissão por escrito deValve, em fevereiro 2023, na qual assumiu a responsabilidade por contas de elevado valor que foram comprometidas através de pedidos de assistência, e as demissões de colaboradores subcontratados noticiadas pela Dexerto e pela Escorenews na sequência do caso de abuso de informação privilegiada no valor de $320k (Parte II, §04 · Dossiê principal §14.1) — baseiam-se em declarações públicas e em reportagens de investigação. Os rumores não comprovados de que membros do pessoal de apoio teriam atividades paralelas relacionadas com jogos de azar ou que receberiam comissões para levantar proibições não estão comprovados nos registos públicos e são aqui excluídos.\n\nEntretanto, a Valve eliminou a possibilidade de monitorizar adequadamente as skins em 2017.. Chegaram mesmo a discutir o assunto nos seus próprios fóruns. Chamaram-lhe «medidas anti-jogo» — enquanto o ecossistema de apostas com skins continuou a canalizar milhares de milhões através da infraestrutura da Steam durante anos a seguir. Excelente estratégia de marca.\n\nVamos demonstrar que:\n\nAs «skins» são mais anónimas do que o Monero\n\nUm cartel peruano terá utilizado skins de Dota 2 para movimentar dinheiro\n\nSteam é, na prática, uma máquina para contornar sanções no valor de cerca de7B em «cartas colecionáveis» (sim, eles chegaram mesmo a dizer «cartas colecionáveis» a um procurador)\n\nTemos um vídeo sobre o assunto das skins. Vais vê-lo.\n\nSabemos também que:\n\nA moderação do Reddit é influenciada por Valve\n\nInfraestrutura de dados de terceiros do Steam (como steamid.uk) é gerido por um particular (msart) cujo projeto associado de lista de bloqueio (steambans.com arquivo) é co-gerido por um moderador confirmado da comunidade Valve (killahinstinct_) — deixando a auditoria independente das proibições da plataforma inteiramente a cargo da «Valve» (ver «Economia dos cartões», §08)\n\nO que não conseguem controlar, proíbem\n\nValve: se continuares a fazer-te de ignorante — tudo bem. Já tomámos nota do teu porto seguro. O Google Analytics torna anónimos os IPs dos teus utilizadores de qualquer forma. Nós vemos o que é apagado. Só não conseguimos prová-lo de forma suficientemente barata para que os teus advogados se importem. Por enquanto.\n\nSecção VA questão do malware — sim, vamos falar disso\n\nVamos ser brutalmente claros quanto à sequência de acontecimentos, porque isso revela exatamente quem tu és.\n\nNÃO vamos divulgar publicamente a vulnerabilidade do jogo. NÃO vamos comunicá-la ao programa «Steam». O programa exige um acordo de confidencialidade (NDA) e, caso o assinássemos, isso impedir-nos-ia de informar os utilizadores afetados sobre o que aconteceu às suas contas. A divulgação a quem perdeu essas contas e às entidades reguladoras é o objetivo deste trabalho; um acordo de confidencialidade é incompatível com isso.\n\nEis o que realmente aconteceu: esta vulnerabilidade é praticamente um segredo à vista de todos nos círculos certos. Sabemos com certeza que investigadores de segurança independentes já apresentaram a exploração completa diretamente à equipa de suporte dSteam. Essa parte já está resolvida. Foram oficialmente avisados através dos vossos próprios canais formais.\n\nE o que fez a «Valve»? Absolutamente nada. Porque, para a «Valve», segurança não é sinónimo de lucro — na verdade, é exatamente o contrário. A segurança é um centro de custos. Até que uma ameaça atinja uma massa crítica e provoque um colapso catastrófico na imagem pública, a «Valve» não a trata como algo urgente.\n\nEntão, o que estamos a fazer? Estamos a informar o público de que isso existe, porque «aValve tem conhecimento de uma ameaça sistémica de malware e opta ativamente por não tomar medidas» é um dado fundamental para as entidades reguladoras que estão neste momento a ler isto.\n\nO jogo é enorme. Não vamos revelar o nome aqui. Mas é importante compreender o seguinte:\n\nIsto NÃO é aquele lixo trivial de «script-kiddie» do CS:GO em que um servidor te pede para «instalar um controlador». Isto é catastrófico.\n\nIsto é um pesadelo ao nível do Unturned: RCE sem cliques ao ligar-se ao servidor. Entras num servidor. Não clicas em nada. Não descarregas nada. A própria ligação é a superfície de ataque e o teu computador fica totalmente comprometido. Sejamos realistas: lançar um RCE e contornar os antivírus locais, aproveitando-se dos certificados digitais de confiança dValve, já nem sequer é novidade em Steam. É praticamente uma funcionalidade integrada no teu ecossistema.\n\nValve já sabe que isto existe. Mas recorrem à sua brecha jurídica favorita e covarde: como o jogo é, tecnicamente, desenvolvido por terceiros, a Valve lava as mãos. Distribuem o jogo, processam os pagamentos, alojam a infraestrutura, mas quando um RCE de «zero cliques» ameaça milhões dos seus utilizadores, a sua posição é: «Não é o nosso jogo, não é da nossa responsabilidade.»\n\nQuando isto inevitavelmente der para o torto, o programador independente é que vai levar com as culpas, e a Valve vai sair-se de boa, fingindo ser a plataforma responsável que «ajudou» na resolução do problema. A clássica covardia da Valve. Já conhecemos o guião.\n\nEstamos a deixar isto registado para que as entidades reguladoras, os procuradores e os jornalistas compreendam exatamente como a «Valve» lida com o malware ativo: escondendo-se atrás de programadores de terceiros, impondo cláusulas de confidencialidade (NDA) e deixando os jogadores à mercê do perigo.\n\nFim da carta abertaInício do registo formal\nRegisto formal · para a autoridade\nDeclaraçãoNo que diz respeito à utilização e aos direitos\n\nPhishDestroy Coligação para Projetos e Cibersegurança\n\nEsta declaração acompanha cada documento apresentado e cada anexo deste conjunto de documentos. É dirigida a qualquer autoridade, tribunal, entidade reguladora, procurador, investigador, jornalista ou pessoa afetada a quem o material chegue às mãos.\n\n1. Não há condições de utilização\n\n1.1 Todo o material produzido pela Coligação no âmbito deste processo — as declarações de facto, a análise, os anexos da sua autoria, as ferramentas e as conclusões — é divulgado SEM RESERVA DE QUAISQUER DIREITOS.\n\n1.2 Qualquer pessoa pode, sem pedir autorização e sem nos notificar:\n\nreproduzi-lo, na totalidade ou em parte;\n\nadaptá-lo, editá-lo, reescrevê-lo, reestruturá-lo ou corrigi-lo;\n\ntraduzir;\n\nextraí-lo sem indicar que se trata de um excerto;\n\nincorporá-la em documentos oficiais, conclusões, decisões, alegações, relatórios ou material de imprensa;\n\napresentá-lo como se fosse um trabalho ou uma descoberta do próprio destinatário;\n\nutilizá-lo como matéria-prima e deitar fora o resto;\n\ne transmiti-lo a qualquer outra pessoa nos mesmos termos.\n\n1.3 NÃO É NECESSÁRIA NEM PRETENDIDA QUALQUER ATRIBUIÇÃO. Não é necessário mencionar, citar, dar crédito, agradecer, consultar ou informar a Coligação. Se o material desta referência ajudar uma autoridade e a Coligação nunca for mencionada, ESSA É UMA RESULTADO TOTALMENTE SATISFATÓRIO e a Coligação declara-o antecipadamente para que a questão não tenha de ser levantada.\n\n1.4 Se, por outro lado, uma autoridade considerar mais conveniente citar a Coligação como fonte, é livre de o fazer. A escolha cabe inteiramente ao destinatário e nenhuma das opções acarreta qualquer consequência.\n\n1.5 Trata-se de uma RENÚNCIA, não de uma oferta de licença. Não requer aceitação, não impõe qualquer obrigação e não pode ser violada. O software publicado pela Coligação é disponibilizado separadamente ao abrigo da licença MIT; a investigação e os resultados são disponibilizados no domínio público na medida do permitido e, nos casos em que uma jurisdição não permita a renúncia, a Coligação concede uma licença irrevogável, mundial e isenta de royalties com o mesmo efeito.\n\n2. Por que é que isto é importante na prática, e não apenas por uma questão de cortesia\n\n2.1 Uma autoridade pode, com razão, hesitar em basear-se em material fornecido por uma entidade externa, por receio de dar a impressão de agir a pedido dessa entidade ou de se envolver de alguma forma com ela.\n\n2.2 AQUI NÃO HÁ NADA COM O QUE SE ENVOLVER. A Coligação não pede nada, não tem direito a nada, não retém nada e não tem qualquer tipo de expectativa. Não pode, posteriormente, fazer valer um direito, reivindicar crédito, queixar-se de uso indevido ou opor-se à forma como o material é caracterizado, porque não reteve qualquer fundamento para o fazer.\n\n2.3 Uma entidade que utilize este material não está, portanto, a agir em nome da Coligação. Está a utilizar informação pública que, por acaso, foi compilada por outra pessoa.\n\n3. Já está tudo aberto\n\n3.1 O trabalho da Coligação é público por defeito:\n\nas investigações são publicadas abertamente em https://phishdestroy.io e podem ser lidos livremente;\n\nA ferramenta foi publicada como código aberto ao abrigo da licença MIT em https://github.com/phishdestroy arquivado em 2026-09-11 ↗;\n\na metodologia está descrita na própria consulta, no Anexo A, secção A.16D, incluindo a ponderação e as limitações de cada tipo de fonte;\n\nA Coligação não aceita quaisquer doações e tem vindo a divulgar essa posição desde 2018.\n\n3.2 O único material que NÃO é publicado é aquele que não pode ser publicado de forma legal ou segura: dados pessoais das vítimas e de terceiros, bem como informações que possam expor uma fonte a retaliações. Esse material é entregue às autoridades de forma confidencial e é identificado nos anexos de provas.\n\n3.3 A Coligação convida à análise da sua própria conduta nos mesmos termos em que convida à análise da conduta de qualquer outra entidade, e disponibilizou voluntariamente as suas práticas de tratamento de dados às autoridades competentes, incluindo um pedido de orientação sobre a eliminação dos dados.\n\n4. Integridade do conjunto de provas\n\n4.1 Os anexos são fornecidos juntamente com a apresentação ou, quando indicado, mediante pedido através de um canal seguro. Não são publicados num endereço público e não se deve inferir a existência de tal endereço: este tipo de material é fornecido diretamente às autoridades.\n\n4.2 Cada entrega é acompanhada por um ficheiro SHA256SUMS que contém um resumo SHA-256 para cada ficheiro fornecido, juntamente com uma assinatura independente OpenPGP SHA256SUMS.asc.\n\n4.3 A chave de assinatura está publicada em https://phishdestroy.io/.well-known/pgp-key.txt e em keys.openpgp.org. A sua marca aparece no cabeçalho de cada documento deste conjunto.\n\n4.4 Qualquer destinatário pode verificar, a qualquer momento, se um ficheiro que se encontra na sua posse é, de facto, o ficheiro que foi enviado, sem alterações:\n\ngpg --verify SHA256SUMS.asc SHA256SUMS\n\nsha256sum -c SHA256SUMS\n\n4.5 O objetivo não é uma mera formalidade. Trata-se de garantir que, caso a exatidão ou a integridade de qualquer prova documentar venha a ser contestada posteriormente, a questão possa ser resolvida por cálculo e não por argumentação.\n\n5. No registo — por que razão a renúncia é funcional e não meramente generosa\n\n5.1 A autoridade poderá deparar-se com as investigações publicadas pela Coligação e considerá-las diretas, controversas e, por vezes, satíricas. Essa impressão está correta. A Coligação escreve dessa forma deliberadamente e não pede desculpa por isso.\n\n5.2 RECONHECE TAMBÉM QUE ESTE NÃO É O TOM ADEQUADO PARA UM PROCESSO REGULATÓRIO OU JUDICIAL. Um assunto sério não deve ser abordado no tom de uma campanha. As conclusões apresentadas a uma autoridade devem ser expostas de forma direta, admitindo as suas limitações, e não devem obrigar o leitor a ignorar o tom para chegar ao cerne da questão.\n\n5.3 É PRECISAMENTE POR ISSO QUE A COALIZÃO RENUNCIA À AUTORIA. A renúncia prevista na secção 1 é o mecanismo através do qual o conteúdo pode ser separado do registo: a autoridade pode retirar o que for útil, reformulá-lo com as suas próprias palavras e descartar cada palavra do estilo da Coligação, juntamente com o nome da Coligação. Nada se perde ao fazê-lo, e a Coligação prefere que assim seja.\n\n5.4 A COALIZÃO SOLICITA AINDA QUE O REGISTO NÃO SEJA CONFUNDIDO COM O MÉTODO. O tom utilizado é combativo; a prática subjacente não é descuidada. Ao longo deste relatório, a inferência é separada da observação, os testemunhos são identificados como tal, as fontes são ponderadas e as suas fraquezas são indicadas, os números são apresentados com as respetivas limitações e os pontos que a Coligação não consegue provar são apresentados como questões dirigidas à autoridade, em vez de afirmações. Nos casos em que as provas contrariavam a própria posição da Coligação, esta assim o indicou — ver Anexo A, parágrafo 7, e secção B.0 do parecer paralelo.\n\n5.5 A COALIZÃO EXPLICA A LIGAÇÃO ENTRE A SUA ATUÇÃO E AS SUAS FINANÇAS, POIS AMBAS SÃO INSEPARÁVEIS. Não aceita dinheiro de ninguém — nem doações, nem recompensas, nem clientes, nem patrocinadores. É essa recusa que torna possível a franqueza: uma organização com receitas para proteger tem de moderar o que diz sobre os partidos de que depende. Não tendo nada a proteger, a Coligação não tem nada a moderar.\n\nÉ também a razão pela qual a Coligação continua a existir. Não há outro motor. O trabalho é feito porque é feito; pára quando as pessoas que o fazem param.\n\n5.6 A autoridade não tem de aceitar nada disto. Isto é referido para que o tom do trabalho público da Coligação não seja interpretado como um indicador do cuidado dedicado ao material que agora tem perante si.\n\n6. O que a Coligação está a oferecer, nas suas próprias palavras\n\nInformação, investigação e observação.\n\nNada é afirmado como uma conclusão que a Coligação não tenha competência para apresentar. Quando se trata de uma inferência, o documento de encaminhamento indica-o. Quando algo se baseia em testemunhos, o documento de encaminhamento especifica de quem são e quais as limitações. Quando a Coligação não pode responder a uma pergunta, também o indica e identifica quem o pode fazer.\n\nA Coligação não pretende qualquer reparação, qualquer pagamento, qualquer reconhecimento nem qualquer resultado para si própria ou para qualquer indivíduo. Pede apenas que as questões apresentadas no pedido de consulta sejam colocadas à CorporaçãValvee por um órgão com poderes para exigir uma resposta.\n\nNota finalA quem quer que esteja a dar continuidade a isto\n\nQueremos agradecer a quem quer que seja que leve este material até onde é necessário. Provavelmente não vai ser um percurso rápido. A «Valve» tem recursos financeiros consideráveis e a Taylor Wessing cobra à hora — essa combinação foi especificamente concebida para fazer com que pessoas como vocês desistam antes de chegarem à meta.\n\nSabemos o que estamos a fazer. Sabemos sobre quem estamos a escrever. A «Valve» moldou-nos — como é que não os poderíamos compreender?\n\nPhishDestroy não há qualquer conflito com Valve. Bloqueámos a única rede de burlões dessa dimensão com que nos deparámos — não fomos à procura de uma briga com Valve. Acontece que todos os caminhos conduziam até eles. Não é um conflito. É apenas uma questão de topologia.\n\nValve Não é possível resolver a situação de «PhishDestroy» porque não há nada para resolver. Não temos qualquer relação. Os dados sobre os seus esquemas de enriquecimento e lucros exorbitantes são, em grande parte, públicos — bastava dedicar tempo suficiente para os ver. Pense nisso como uma enciclopédia de sucesso: «Como não cumprir as sanções para que os hackers russos não possam piratear os nossos jogos gratuitos (os pagos, que eles de qualquer forma não iriam piratear).» Já percebeu a ideia.\n\nNão precisamos de atribuição de autoria.\n\nNão precisamos de indicação da fonte.\n\nNão precisamos de uma vitória.\n\nPrecisamos de alguém com autoridade efetiva para colocar ao «Valve» as perguntas que já constam deste encaminhamento, com o poder de exigir uma resposta.\n\nÉ isso. É tudo o que pedimos.\n\nOs casos estarão disponíveis em:\n\nhttps://steamdestroy.eth/\n\nhttps://steamdestroy.eth.limo (de momento não funciona — será corrigido quando necessário)\n\nEstaremos em:\n\nhttps://phishdestroy.eth.limo/ arquivado em 2026-06-27 ↗\n\nhttps://phishdestroy.eth/\n\nDois objetos autografados · direitos e texto publicado\nAutorização assinadaO que foi assinado e o que abrange\n\nA concessão de direitos e o texto da investigação são objetos JSON assinados separadamente, apresentados abaixo. Cada assinatura «OpenPGP» independente autentica os bytes exatos do JSON indicado ao seu lado. A declaração de direitos concede permissões; o instantâneo do texto identifica e contém o material que está a ser publicado.\n\n1. Declaração de direitos — license-rights.json\n\nObjeto assinado: o completo license-rights.json ficheiro, contendo a concessão de direitos públicos datada de 28 de setembro de 2026.. Esta concede permissão para copiar, publicar, editar, traduzir, combinar e comercializar os materiais do dossiê de autoria própria sem necessidade de atribuição, notificação ou aprovação. Esta assinatura autentica a declaração de direitos; não autentica o texto de cada página web ou ficheiro PDF.\n\nA autorização original assinada mantém-se inalterada. A autorização nela prevista não pode ser revogada nem restringida através de alterações ao sítio Web, da publicação de outro ficheiro ou da retirada do sítio da Internet. Os materiais de terceiros mantêm os seus próprios direitos.\n\nDeclaração de direitos em JSON ↗ · Assinatura de license-rights.json ↗ · SHA-256, de license-rights.json ↗\n\ngpg --verify license-rights.json.asc license-rights.json\nsha256sum -c license-rights.json.sha256\n2. Texto publicado — dossier-text.json\n\nObjeto assinado: o completo dossier-text.json ficheiro. Contém o texto efetivamente legível das páginas exportadas em documents[].content.text, com o título de cada página, o idioma, o URL de origem, o hash HTML de origem, os títulos e as referências. O documents A lista apresenta o inventário exato abrangido por esta instantânea; as variantes linguísticas são apresentadas separadamente. Trata-se de uma publicação em texto, não apenas de uma lista de hashes.\n\nCada entrada identifica o seu ficheiro PDF de página leve através do nome do ficheiro e do SHA-256o em documents[].pdf. O JSON também identifica a declaração de direitos original através do URL e do SHA-256,, para que o texto publicado, o seu PDF e a autorização de direitos aplicável possam ser associados sem margem para dúvidas. As bases de dados externas associadas, as imagens originais e as páginas ausentes do inventário não estão incorporadas neste instantâneo do texto.\n\nTexto JSON completo e assinado ↗ · Assinatura de dossier-text.json ↗ · SHA-256, de dossier-text.json ↗\n\ngpg --verify dossier-text.json.asc dossier-text.json\nsha256sum -c dossier-text.json.sha256\n\nNa página inicial do dossiê, os botões PDF e JSON permitem exportar o conjunto de investigação. Numa página interna, permitem exportar essa página no idioma em que foi publicada. Cada ficheiro JSON de página possui também a sua própria assinatura independente e um ficheiro SHA-256, explicitamente identificado no seu integrity objeto. Para verificar o PDF associado, calcule o seu SHA-256e e compare-o com o pdf.sha256 valor no JSON verificado. O PDF está vinculado a esse resumo; não contém uma assinatura digital no formato PDF.\n\n3. Pacote de investigação para impressão — steam-dossier-{language}.content.json\n\nObjeto assinado: o ficheiro JSON completo específico do idioma, incluindo o texto do capítulo incluído em documents[].content.text, intervalos de páginas dos capítulos, línguas de origem, a lista de fontes excluídas e o resumo exato do PDF em pdf.sha256. Os cinco arquivos de material de apoio continuam ligados online e não são agrupados. O texto da investigação de autoria própria é mantido; os catálogos visuais são substituídos por ligações para as fontes.\n\nJSON em inglês ↗ · Assinatura separada de «OpenPGP» ↗ · Resumo do SHA-256 ↗\n\nAlemão JSON ↗ · Assinatura separada de «OpenPGP» ↗ · Resumo do SHA-256 ↗\n\ngpg --verify steam-dossier-en.content.json.asc steam-dossier-en.content.json\nsha256sum -c steam-dossier-en.content.json.sha256\n\nChave de verificação pública ↗\n\nImpressão digital da assinatura: 129F C7F3 9C40 C69D 2EF3 C329 BFCF 9E8D D295 EE01\n\ngpg --import pgp-key.txt\ngpg --fingerprint 129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01\n\nVerifique se a impressão digital apresentada corresponde à que se encontra acima e, em seguida, verifique a assinatura em relação ao nome exato do ficheiro JSON. A edição de um ficheiro JSON assinado altera o objeto assinado e invalida a sua assinatura original. Uma assinatura válida identifica os bytes publicados; não constitui uma verificação independente dos resultados da investigação.\n\nPhishDestroy — investigação pública — todos os direitos cedidos à humanidade\n\nAcesso à região da OFAC: proibido",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Licença e Aviso Legal — Dedicação ao Domínio Público"
          },
          {
            "level": 2,
            "id": null,
            "text": "Secção ILicença — a parte propriamente jurídica, mas humana"
          },
          {
            "level": 3,
            "id": null,
            "text": "Uma regra concreta (sim, apenas uma)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Secção IIO que é isto e por que razão existe"
          },
          {
            "level": 2,
            "id": null,
            "text": "Secção IIICarta aberta a Valve — a sério, lê isto"
          },
          {
            "level": 3,
            "id": null,
            "text": "O negócio (oferta aberta, sem necessidade de advogados)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Secção III-BOs recursos aliados — uma nota dirigida especificamente a Steam"
          },
          {
            "level": 2,
            "id": null,
            "text": "Secção IVO dinheiro, as proibições, todo este circo"
          },
          {
            "level": 2,
            "id": null,
            "text": "Secção VA questão do malware — sim, vamos falar disso"
          },
          {
            "level": 2,
            "id": null,
            "text": "DeclaraçãoNo que diz respeito à utilização e aos direitos"
          },
          {
            "level": 3,
            "id": null,
            "text": "1. Não há condições de utilização"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. Por que é que isto é importante na prática, e não apenas por uma questão de cortesia"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. Já está tudo aberto"
          },
          {
            "level": 3,
            "id": null,
            "text": "4. Integridade do conjunto de provas"
          },
          {
            "level": 3,
            "id": null,
            "text": "5. No registo — por que razão a renúncia é funcional e não meramente generosa"
          },
          {
            "level": 3,
            "id": null,
            "text": "6. O que a Coligação está a oferecer, nas suas próprias palavras"
          },
          {
            "level": 2,
            "id": null,
            "text": "Nota finalA quem quer que esteja a dar continuidade a isto"
          },
          {
            "level": 2,
            "id": null,
            "text": "Autorização assinadaO que foi assinado e o que abrange"
          },
          {
            "level": 3,
            "id": null,
            "text": "1. Declaração de direitos — license-rights.json"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. Texto publicado — dossier-text.json"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. Pacote de investigação para impressão — steam-dossier-{language}.content.json"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/pt/#briefing-heading",
          "https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "http://web.archive.org/web/20260821155801/https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "https://phishdestroy.io/steam_dossier/pt/investigation_part2.html#outsourcing-case",
          "https://phishdestroy.io/steam_dossier/pt/#theft-ledger",
          "https://steamid.uk/",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/groups/steambans",
          "https://steamcommunity.com/id/killahinstinct_",
          "https://phishdestroy.io/steam_dossier/pt/card_economy.html#governance",
          "https://phishdestroy.io/steam_dossier/pt/license_disclaimer.html",
          "https://github.com/phishdestroy",
          "http://web.archive.org/web/20260911040557/https://github.com/PhishDestroy",
          "https://phishdestroy.io/.well-known/pgp-key.txt",
          "https://steamdestroy.eth/",
          "https://steamdestroy.eth.limo/",
          "https://phishdestroy.eth.limo/",
          "http://web.archive.org/web/20260627040219/https://phishdestroy.eth.limo/",
          "https://phishdestroy.eth/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json.asc",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json.sha256",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json.sha256?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json.sha256?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json.sha256?v=print-20260928-v3"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/pt/license_disclaimer.content.json",
      "export_json_sha256": "c80e1bef27163dade14e9c5fb79655f6ed16df7726c61f8cbfc8dacd48afc784"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "pt/market_economics.html",
      "language": "pt",
      "title": "Uma infraestrutura, dois mercados — O Dossiê «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/pt/market_economics",
      "source_html_sha256": "ed3488d05e75930e519937ff3f17a9ea3df0268239d8581b0bed5d2e69403015",
      "exported_at": "2026-09-29T00:18:09.620Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "market_economics.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/pt/market_economics.pdf?v=print-20260929-v5",
        "sha256": "38ea5774fd56d82611664269f3742ec70abc8ab95f88b0e987b230640105a032",
        "bytes": 99894,
        "pages": 8
      },
      "integrity": {
        "signed_object": "market_economics.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "market_economics.content.json.asc",
        "digest_file": "market_economics.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify market_economics.content.json.asc market_economics.content.json",
          "sha256sum -c market_economics.content.json.sha256"
        ]
      },
      "content": {
        "text": "Anexo VII · Arquitetura do mercado · 20 de setembro de 2026\nEconomia de Mercado — Duas Economias e o Limite Máximo de Cotação\n\nA infraestrutura deles. Duas economias.\n\nO QUE ESTA SECÇÃO DEMONSTRA\n\nEste capítulo analisa a bifurcação sistémica do mercado criada pelo limite de listagem de $1,800 da Valve e pelos saldos de carteiras não retiráveis. Através de um levantamento de 38 bolsas externas ativas de skins, que detêm aproximadamente $1.28 mil milhões em valor de cotação, a investigação comprova que a negociação de alto nível migra necessariamente para plataformas paralelas externas, ao mesmo tempo que depende da infraestrutura subjacente de negociação e autenticação dSteam. Embora a utilização comercial seja formalmente proibida no Contrato de Subscrição, Valve facilita e rentabiliza esta economia de dois níveis sem registos publicados de aplicação da lei.\n\n← Voltar ao resumo executivo\n\n38 mercados CS2 de terceiros ativos, além do próprio mercado dSteam. Todas as skins listadas em qualquer uma dessas plataformas têm de passar pelo inventário da Steam e pelo mercado API. As regras da Valve proíbem a exploração comercial dessa infraestrutura. O valor estimado em cerca de $1.28 mil milhões, atribuído por terceiros, mantém-se, embora não tenha sido encontrado qualquer registo público da aplicação dessa regra.\n\n$1.28B\nValor de cotação de terceiros · Plataformas «38»\n53.2M\nOfertas apresentadas · 38 mercados de terceiros\n70.1K\nSteam itens listados no instantâneo\n41×\nValor cotado por terceiros vs. $31M da Steam\nA principal conclusão\nUma infraestrutura. Duas economias.\n\nSteam controla o produto, o inventário e o comércio. Todas as skins vendidas em qualquer uma das plataformas abaixo têm de passar pelo sistema de comércio da Steam API — uma dependência estrutural que é diretamente observável. O próprio Community Market da Valve recebe uma comissão sobre as suas vendas; não fica aqui esclarecido se essa comissão financia ou está ligada ao ecossistema de terceiros.\n\nPor que é que isto é importante para a investigação\n1\nAcordo de Subscrição do serviço «Steam» da Valve proíbe a exploração comercial da infraestrutura dSteam, sem autorização expressa. Não foi encontrada qualquer autorização desse tipo nos registos públicos relativos às plataformas abaixo indicadas.\n2\nSteam controla a identidade (OpenID), o estado do inventário e a execução das transações relativas a um valor de cerca de $1.28B de ativos listados por terceiros. Nenhuma transferência de artigos ocorre sem a infraestrutura dValve.\n3\nA própria plataforma de comércio da Steam tem $31M cotado — cerca de 1/41 do valor cotado por terceiros. O limite máximo de preço de $1,800 significa que os vendedores que o ultrapassem têm de sair da plataforma para vender aos preços observados.\n4\n248 Categorias de artigos do CS2, cujos preços foram fixados acima do limite máximo por dois ou mais mercados, de forma independente, não podem ser vendidos ao preço de mercado observado no site Steam — e nenhum deles se encontra sequer listado nesse site. O limite máximo de $1,800 cria a procura que os operadores terceiros satisfazem.\nSteam Mercado comunitário: $31MValor de cotação de terceiros: $1,276M\n$1,276M · valor indicado por terceiros — tudo depende da transação de Steam API e do OpenID\nSteam · $31M\n\nFonte: Catálogo em tempo real da PriceEmpire, 20, 2026., valor de tabela = soma dos cartões com valores de tabela arredondados no instantâneo guardado, Steam excluído. Não se trata do volume de vendas.\n\n38 mercados de terceiros ativos · Tudo depende de uma infraestruturSteam\nRegisto da plataforma\n\nAs plataformas abaixo encaminham os seus inícios de sessão através do OpenID dSteam e as suas transações através do WebAPI dSteam. Cada uma das observadas openid.realm passa pelo fluxo de início de sessão do Steam; o registo regista as rotas de autenticação observadas, em vez de afirmar que um determinado operador não possui a autorização do Valve.\n\n#\tPlataforma\tValor cotado\tOfertas em vigor\tArtigos\tEscala\n1\tUUSkins\t$133.8M\t3.4M\t30.9K\t\n\n2\tYouPin898\t$127.5M\t5.9M\t29.2K\t\n\n3\tBuff.163\t$104M\t3.5M\t35K\t\n\n4\tMoon.Market\t$100.3M\t2.9M\t20.9K\t\n\n5\tWhite.Market\t$89.6M\t3M\t20.6K\t\n\n6\tBuff.Market\t$86.7M\t1.3M\t33.4K\t\n\n7\tEcosteam\t$82.1M\t3.3M\t30.1K\t\n\n8\tCSFloat\t$67.8M\t2.4M\t27.8K\t\n\n9\tSkin.Land\t$67.4M\t2.2M\t34.6K\t\n\n10\tLIS-SKINS\t$67.4M\t2.2M\t34.6K\t\n\n11\tC5Game\t$54.6M\t4.6M\t29.6K\t\n\n12\tHaloSkins\t$46.6M\t4.4M\t29.3K\t\n\n13\tAvan.Market\t$43.3M\t809.5K\t22.2K\t\n\n14\tWaxpeer\t$40.1M\t1M\t27.3K\t\n\n15\tSteam (official)\t$31M\t32.2M\t70.1K\t\n\n16\tCS.MONEY\t$29M\t748.9K\t28K\t\n\n17\tMarket.CSGO\t$26.3M\t1.3M\t27.6K\t\n\n18\tCS.MONEY Bot\t$25.7M\t614K\t23.8K\t\n\n19\tSkinport\t$16.3M\t3.8M\t31.1K\t\n\n20\tSkinFlow\t$14.1M\t481.8K\t23.6K\t\n\n21\tDMarket\t$12.6M\t948.2K\t35.6K\t\n\n22\tSkins.com\t$11.5M\t83.2K\t15.8K\t\n\n23\tSkin.place\t$6.9M\t380.8K\t11.4K\t\n\n24\tSkinsMonkey\t$6M\t109.4K\t11.6K\t\n\n25\tSkinBaron\t$5M\t2.1M\t21.5K\t\n\n26\tRustTM\t$3M\t33.1K\t4.9K\t\n\n27\tPirateSwap\t$2M\t859.3K\t10.5K\t\n\n28\tMannco.Store\t$1.2M\t223.7K\t11K\t\n\n29\tSkinSwap\t$1.1M\t11.4K\t4K\t\n\n30\tTradeIt\t$967.1K\t29.1K\t11.7K\t\n\n31\tLootFarm\t$896.1K\t162.5K\t28.6K\t\n\n32\tRustskins\t$714.8K\t312.5K\t6.1K\t\n\n33\tBalticSkins\t$599.2K\t28.2K\t4.5K\t\n\n34\tExeSkins\t$442.9K\t2.6K\t1.4K\t\n\n35\tRapidSkins\t$230.9K\t11.6K\t2.3K\t\n\n36\tCS.Trade\t$203K\t19K\t16.7K\t\n\n37\tKrakatoa\t$11.1K\t115\t53\t\n\n38\tShadowPay\t—\t—\t—\t—\n39\t49skins\t—\t—\t—\t—\nO limite máximo de preço de $1,800 da Steam · resumo de cinco mercados · 23 2026 de setembro\nA diferença de preços é mensurável.\n\nSteam limita as cotações do Community Market a aproximadamente $1,800 (o valor é recalculado para $2,000, $2,070, $2,300 e $2,500 em cs2sh-atlas.json e mantém-se em cada nível de resistência). Os itens observados acima desse preço não podem ser vendidos ao seu preço de mercado através da própria plataforma de comércio eletrónico da Valve — mas continuam a depender do sistema de inventário e transferência da Steam, independentemente do local onde são vendidos. A classificação de todo o catálogo por preço revela onde está o limite: o mercado da Valve oferece 95.3% das categorias de artigos cujo preço é inferior ao seu limite máximo e 1.9% dos que se encontram acima dele.\n\nCinco plataformas de comércio eletrónico: artigos que excedem o limite de Steam\n248\n\nCategorias de artigos cujo preço de venda mais baixo atinge $1,800 em dois ou mais mercados, de forma independente, detendo cópias listadas n18,394, no valor mínimo de $78.6M. Destes, 100.0% — todas elas — não têm qualquer registo no site Steam.\n\nAnexos completos: o registo → · o atlas da escala de preços →\n\nDistribuição de preços acima do limite máximo\n$1,800–$5,000\n174\n$5,000–$10,000\n49\n$10,000–$25,000\n21\n$25,000–$50,000\n2\n$50,000+\n2\nProdutos em destaque — preço de venda mais baixo confirmado em cinco plataformas de vendas\n1Autocolante | Titan (Holo) | Cat. «14»$66,285\n2Autocolante | iBUYPOWER (Holo) | Cat. «14»$64,795\n3Autocolante | Reason Gaming (Holo) | Cat. '14$42,899\n4★ Luvas desportivas | Labirinto de sebes (FN)$26,812\n5Autocolante | Team Dignitas (Holo) | Cat. «14»$23,667\n6EMS Cat. «14: As Lendas»$22,879\n7★ Luvas desportivas | Caixa de Pandora (FN)$21,643\n8EMS Cat. «14» Challengers$21,010\n9Autocolante | Vox Eminor (Holo) | Cat. «14»$18,619\n10★ Faca StatTrak™ Navaja | Aço Azul (FN)$18,064\n\nOs preços de venda solicitados não são preços de venda. Imagem capturada do site cs2.sh, 23, 2026. de setembro. Cada linha é cotada acima do limite máximo por, pelo menos, duas plataformas de forma independente; os pedidos de venda de uma única unidade e as cotações que excedam em mais de três vezes o preço de venda mais baixo de um artigo são excluídos. Como funciona a classificação →\n\nO que cobra a Valve · licenciado cs2.sh instantâneo · 23 Setembro 2026\nA remuneração anunciada é de 15%.. A maioria dos anúncios oferece uma remuneração superior.\n\nValve cobra uma comissão de 5% Steam e uma comissão de 10% do editor CS2 sobre os rendimentos do vendedor — o conhecido 15%. Ambas as comissões implicam um Mínimo de $0.01, pelo que nenhuma venda pode nunca ter menos de dois cêntimos em comissões. No caso dos artigos baratos e de grande volume que constituem a maior parte do mercado, esse valor mínimo é o fator limitante, e não a percentagem. Resolvemos a questão das comissões para cada um dos 29,635 tipos de artigos que apresentam uma cotação em tempo real Steam.\n\n77.7%\ndas listagens ativas do Steam correspondem a tipos de artigos cujos preços são superiores aos indicados em 15%\n84.8%\ndo artigo tipos pagam, de facto, a taxa indicada no título\n4,517\ntipos de artigos cobrados a um valor superior à taxa anunciada\n$0.02\ntaxa mínima sobre qualquer venda, independentemente do preço\nOs dois números apontam em sentidos opostos, e ambos são verdadeiros\n1\nContados por tipo de artigo, Os honorários de Valve correspondem, em linhas gerais, ao anunciado: 84.8% dos tipos de preços indicados em 29,635 são cobrados a 15%. ou a um valor próximo deste\n2\nContados por listagem efetiva, a situação inverte-se: 18,682,244 de 24,038,911 As listagens em tempo real referem-se aos tipos de artigos cujo preço é superior a 15%.\n3\nAmbas as afirmações são verdadeiras porque os tipos sobrecarregados são os barato, em grandes quantidades esses. 1,109 Os tipos de artigos têm um preço mais elevado do que duplo a taxa de referência, e só esses tipos já representam 14,083,486 anúncios ativos.\n4\nIsto é aritmética, não uma alegação. O valor mínimo está indicado na própria documentação relativa aos honorários daValve. O que não foi publicado é a que parte do mercado é que isso se aplica, na realidade — que é precisamente o que os números acima medem.\nComissão cobrada, em percentagem do valor nominal 15%\n200%+\n14,083,486\n100-200%\n1,028,438\n50-100%\n700,804\n30-50%\n317,031\n20-30%\n2,258,254\n17.6-20%\n294,231\n\nO comprimento da barra corresponde ao número de anúncios ativos em cada faixa. Uma faixa de «200%+» significa que a comissão cobrada é superior ao dobro de 15% do valor recebido pelo vendedor.\n\nUm exemplo prático\n67%\n\nNuma oferta, o comprador paga $0.03 pois o vendedor recebe $0.01 e o site Valve apresenta $0.02 — os dois valores mínimos de um cêntimo. Em percentagem do valor pago pelo comprador, isso corresponde a 67%; em percentagem do valor recebido pelo vendedor, corresponde a 200%.\n\nConjunto de dados completo: cs2sh-steam-fee-census.json →\n\nO mesmo objeto, dentro do jardim e fora dele\nComprar no site Steam sai mais caro. Quase sempre.\n\nPara cada artigo cujo preço fosse indicado tanto no site Steam como em, pelo menos, uma plataforma de comércio eletrónico de terceiros, comparámos o preço de venda mais baixo do site Steam com o preço de venda mais baixo fora desse site. Em todas as 28,700 no que diz respeito aos artigos, o Steam é o local mais caro 86.4% na maioria das vezes, com uma mediana de +35.7%.\n\nPrémio mediano do seguro «Steam», por faixa de preço\nmenos de $0.50\n+48.3%\n$0.50-2\n+36.5%\n$2-10\n+29.6%\n$10-50\n+28.6%\n$50-250\n+36.3%\n$250-1k\n+51.1%\nmais de $1,000\n+67.9%\n\nA curva tem a forma de um «U». É mais barato comprar no site Steam no $10–$50 faixa e o mais querido nas duas extremidades.\n\nPor que é que o segmento de gama alta é importante\n+67.9%\n\nAcima $1,000, o custo mediano de um anúncio no «Steam» 67.9% é superior ao da oferta mais barata fora desse site — e apenas 1,040 existem anúncios desse tipo no site Steam.\n\nA partir de cerca de $1,800, a comparação deixa de ser possível, porque a regra da Valve proíbe totalmente a listagem. A cobertura da Steam para os itens acima do seu próprio limite é 1.9%. Ver a tabela completa →\n\nConjunto de dados completo: cs2sh-walled-garden-premium.json →\n\nUm prémio, por si só, não constitui uma conclusão: o mercado de câmbio à vista (Steam) oferece liquidez imediata e ausência de risco de contraparte, e os compradores podem, razoavelmente, pagar por isso. O que é mensurável é a dimensão do diferencial e o facto de que o dinheiro que o atravessa não pode regressar — o que será abordado na secção seguinte.\n\nEntra dinheiro, não sai dinheiro\n128.1 milhões de dólares comprometidos em encomendas que não podem ser canceladas.\n\nUma ordem de compra no Steam é pré-financiada: o dinheiro sai da carteira do comprador no momento em que a ordem é efetuada. Fundos da carteira Steam não pode ser revogado — só podem ser gastos no Steam. A soma de todos os níveis de preço do livro de ordens de compra de cada item monitorizado fornece um levantamento do dinheiro comprometido, que não pode ser retirado.\n\n$128.1M\ncomprometido a manter as ordens de compra Steam\n170.6M\nordens de compra financiadas individualmente em aberto\n$105.8M\nvalor de venda dos imóveis que têm à sua frente\n$15.9M\nA comissão da Valve caso todos os imóveis fossem vendidos pelo preço pedido\nO que esta figura é e o que não é\n1\nÉ dinheiro real já depositado. Cada dólar contabilizado foi debitado de uma carteira e está associado a uma ordem em aberto em todos os tipos de artig31,253.\n2\nÉ não receitas e não se trata de uma afirmação sobre o balanço da «Valve». Não é aqui esclarecido onde é que o capital em circulação se encontra nem em que livros está registado.\n3\nÉ um instantâneo, não um fluxo. As encomendas podem ser canceladas pelo comprador, o que faz com que os fundos sejam devolvidos à carteira — mas ainda não saem de Steam.\n4\nA porta de sentido único é o ponto-chave. Um mercado cuja moeda não pode ser convertida em dinheiro é a razão pela qual um inventário roubado é transformado desligado Steam em vez de sobre ele.\n\nMétodo: cada nível de preço de cada livro de ordens de compra monitorizado, multiplicado pelas ordens existentes nesse nível. Conjunto de dados completo: cs2sh-steam-locked-capital.json →\n\nVendas concretizadas, não preços pedidos · um único mercado · média móvel de 90 dias\n30.9 milhões de dólares foram efetivamente transacionados — na mais pequena das cinco prateleiras.\n\nUma única venda a preço elevado pode corresponder a uma peça artesanal rara ou a uma variante com autocolante de um artigo básico barato (por exemplo, e.g, um artigo de $30 com uma venda concluída única de $9,772). «Elevado» = a transação concluída de valor mais elevado, e não o preço normal do artigo.\n\nTodas as outras figuras desta página medem o que é listado. Este mede o que era vendido. O site Skinport publica as suas próprias transações concluídas e, nos últimos 90 dias, estas ascenderam a 1,219,143 vendas valor $30,927,032, a uma média de $25.37 cada.\n\n1.22M\nvendas concluídas em 90 dias, num único mercado\n$30.9M\nvolume de negócios no mesmo período\n$125M\ntaxa anualizada — um valor mínimo, não uma estimativa\n~2%\nA quota da Skinport na reserva acima do limite máximo, por valor de cotação\nDe onde veio o volume de negócios\nmenos de $1\n0.5%\n$1-10\n5.8%\n$10-100\n22.2%\n$100-1k\n59.4%\n$1k-1.8k\n6.9%\nacima do limite de Steam\n5.3%\n\nO comprimento da barra corresponde ao volume de negócios; o valor representa a quota dessa categoria no total. 59.4% do dinheiro movimentado no nível $100–$1k, em vendas 71,437.\n\nMesmo acima do limite do «Valve», as vendas continuam a acontecer\n492\n\nvendas realizadas de artigos com preços superiores ao limite estabelecido pelo Steam, no valor de $1,643,938, em 76 tipos de artigos — num mercado que ocupa cerca de 2% dessa prateleira. Nenhuma dessas vendas poderia ter ocorrido em Steam.\n\nConjunto de dados completo: cs2sh-offsteam-90d-dynamics.json → · os máximos atingidos →\n\nSkinport é UM dos mercados de terceiros aqui analisados e, com um valor de cotação superior ao limite do «Steam», é o mais pequeno dos cinco (cerca de 2% dessa prateleira). Todos os totais aqui apresentados representam um valor mínimo da economia «off-Steam», não uma medida da mesma. Não são utilizados dados do «Steam».",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Economia de Mercado — Duas Economias e o Limite Máximo de Cotação"
          },
          {
            "level": 2,
            "id": null,
            "text": "Uma infraestrutura. Duas economias."
          },
          {
            "level": 2,
            "id": null,
            "text": "Registo da plataforma"
          },
          {
            "level": 2,
            "id": null,
            "text": "A diferença de preços é mensurável."
          },
          {
            "level": 3,
            "id": null,
            "text": "Cinco plataformas de comércio eletrónico: artigos que excedem o limite de Steam"
          },
          {
            "level": 3,
            "id": null,
            "text": "Distribuição de preços acima do limite máximo"
          },
          {
            "level": 3,
            "id": null,
            "text": "Produtos em destaque — preço de venda mais baixo confirmado em cinco plataformas de vendas"
          },
          {
            "level": 2,
            "id": null,
            "text": "A remuneração anunciada é de 15%.. A maioria dos anúncios oferece uma remuneração superior."
          },
          {
            "level": 3,
            "id": null,
            "text": "Comissão cobrada, em percentagem do valor nominal 15%"
          },
          {
            "level": 3,
            "id": null,
            "text": "Um exemplo prático"
          },
          {
            "level": 2,
            "id": null,
            "text": "Comprar no site Steam sai mais caro. Quase sempre."
          },
          {
            "level": 3,
            "id": null,
            "text": "Prémio mediano do seguro «Steam», por faixa de preço"
          },
          {
            "level": 3,
            "id": null,
            "text": "Por que é que o segmento de gama alta é importante"
          },
          {
            "level": 2,
            "id": null,
            "text": "128.1 milhões de dólares comprometidos em encomendas que não podem ser canceladas."
          },
          {
            "level": 2,
            "id": null,
            "text": "30.9 milhões de dólares foram efetivamente transacionados — na mais pequena das cinco prateleiras."
          },
          {
            "level": 3,
            "id": null,
            "text": "De onde veio o volume de negócios"
          },
          {
            "level": 3,
            "id": null,
            "text": "Mesmo acima do limite do «Valve», as vendas continuam a acontecer"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/pt/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/pt/elite_skins.html",
          "https://phishdestroy.io/steam_dossier/pt/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/pt/skin_atlas.html#grading",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-steam-fee-census.json",
          "https://phishdestroy.io/steam_dossier/pt/skin_atlas.html#cliff",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-walled-garden-premium.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-steam-locked-capital.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-offsteam-90d-dynamics.json",
          "https://phishdestroy.io/steam_dossier/pt/skin_atlas.html#highs"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/pt/market_economics.content.json",
      "export_json_sha256": "56c5abc83ec3e321c422be920f016e8e5bc012b61b5a2b4badd385356f99d18e"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "pt/regulatory_act_print.html",
      "language": "pt",
      "title": "LEI DE AUDITORIA FORENSE: Valve Steam Web API Ecossistema e Exploração Comercial (Ref.: VAL-REG-2026-09)",
      "source_url": "https://phishdestroy.io/steam_dossier/pt/regulatory_act_print",
      "source_html_sha256": "70aff3e1edd0e298d7a23215f2998fddf38384f85c42e23a474433ec1fb41378",
      "exported_at": "2026-09-29T00:18:09.757Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "regulatory_act_print.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/pt/regulatory_act_print.pdf?v=print-20260929-v5",
        "sha256": "d7bb378f9a556d7c6e9766fca90e0b7e10ad89120d7c01b9bc22349b2ca252cb",
        "bytes": 186845,
        "pages": 14
      },
      "integrity": {
        "signed_object": "regulatory_act_print.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "regulatory_act_print.content.json.asc",
        "digest_file": "regulatory_act_print.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify regulatory_act_print.content.json.asc regulatory_act_print.content.json",
          "sha256sum -c regulatory_act_print.content.json.sha256"
        ]
      },
      "content": {
        "text": "phishdestroy.io · Coligação de Investigação Forense · Registo Público Universal\nREGISTO: VAL-REG-2026-09-EVID\nPROVENIÊNCIA: phishdestroy.io/steam_dossier/\nDIREITOS: TODOS OS DIREITOS CEDIDOS À HUMANIDADE\nLei da Auditoria Forense e Anexo Regulamentar\nProvisionamento sistemático de «API» por terceiros, arquitetura de bypass automatizada e não aplicação contratual no ecossistema «Valve» Steam\nDomínio emissorphishdestroy.io\nPlataforma de destinoValve Steam / Steamworks\nVetor de autenticação primárioSteam OpenID 2.0 / Web API\nAviso legalAll Rights to Humanity (CC0)\nSecção I: Memorando Executivo e Conclusões FactuaisREF: MEMO-RESUMO-01\n\nO presente documento constitui um relatório formal de auditoria forense que analisa a interação operacional entre os termos comerciais publicados pelaValve, os seus pontos finais de autenticação técnica e as plataformas comerciais de terceiros observadas. A auditoria foi realizada através da observação passiva e não autenticada da rede, da verificação de registos no RDAP e da telemetria pública do Link Filter.\n\nNúcleo factual: A observação empírica revela uma divergência sistemática entre as declarações contratuais públicas da «Valve» e a sua infraestrutura de produção. Embora o Acordo de Subscrição do «Steam» (SSA) proíba estritamente a exploração comercial não autorizada (§ 2.G), a interação automatizada com bots/scripts (§ 4.C) e a transferência de contas (§ 1.C), a Valve Corporation continua a fornecer, em tempo real, uma infraestrutura programática de autenticação OpenID e de consulta de inventário a, pelo menos, 175 entidades comerciais, gerando volumes de transações secundárias na ordem dos milhares de milhões de dólares.\n\n175\nOperadores comerciais auditados\n44\nHosts de autenticação com domínios separados\n26\nPares de proxies com filtragem dividida\n100%\nArtigo 2.G / Artigo 4.C da SSA, não aplicados\n0\nRevogações de autenticação impostas\nQuadro contratual e legal aplicável\nSSA § 2.G\nProibição de utilização comercial: É expressamente proibida a exploração de Conteúdos e Serviços para fins comerciais sem autorização prévia por escrito da Valve Corporation.\nSSA § 4.C\nRestrição à automatização: É estritamente proibida a utilização de scripts, bots de negociação, macros ou sistemas não controlados por seres humanos que interajam com os serviços e mercados dSteam.\nSSA § 1.C\nObrigação de uso pessoal: Limita as contas ao uso pessoal; proíbe expressamente a venda, o aluguer, a transferência ou a troca de contas de utilizador dSteam.\nDSA da UE (2022/2065)\nAvaliação do Risco Sistémico (Art. 34/35): As plataformas online de grande dimensão (VLOPs) devem detetar, avaliar e mitigar ativamente os riscos sistémicos decorrentes da utilização indevida automatizada e da exploração comercial não autorizada.\nSecção II: Registo de Anexos A — Pares de divisão de filtros de ligação documentados (rotas 26)REF: EX-SPLIT-LEDGER\n\nAnálise forense da evasão por domínios divididos: No âmbito do sistema de filtragem de links «Steam» () de Valve (steamcommunity.com/linkfilter/?url=...), quando um utilizador final clica numa ligação que conduz a uma plataforma de jogos de azar ou do mercado negro sinalizada, o Valve apresenta um aviso em destaque («Link bloqueado! ... sinalizado como potencialmente malicioso»). No entanto, a análise forense do percurso revela que 26 plataformas comerciais operam numa arquitetura de domínios separados: embora o domínio comercial principal esteja BLOQUEADO no Filtro de Links, o domínio secundário que aloja o ponto final de resposta OpenID do Valve está marcado como LIMPO. Os servidores OpenID do Valve aceitam pedidos de autenticação provenientes destes servidores proxy sem interrupção, neutralizando o aviso de segurança ao consumidor e continuando a processar os inícios de sessão.\n\n#\tDomínio comercial principal\tFiltro principal\tDomínio do proxy de autenticação OpenID\tFiltro de autenticação\tRDAP Registado\tBase de registo\n01\trollbit.com\tBLOCKED\trbsnin.com\tCLEAN\t2026-09-18\tPASSIVE_CAPTURE\n02\tskin.club\tBLOCKED\tsc-auth.net\tCLEAN\t2019-04-02\tPASSIVE_CAPTURE\n03\thowl.gg\tBLOCKED\thowl.uno\tCLEAN\t2026-08-11\tPASSIVE_CAPTURE\n04\tduelbits.com\tBLOCKED\tswitchflips.com\tCLEAN\t2020-04-21\tPASSIVE_CAPTURE\n05\tcsgofast.com\tBLOCKED\tsteam-login.authtofast.com\tCLEAN\t2026-06-30\tPASSIVE_CAPTURE\n06\tfarmskins.com\tBLOCKED\tsteam.kobal.cc\tCLEAN\t2017-01-07\tPASSIVE_CAPTURE\n07\tcobaltlab.tech\tBLOCKED\tcobaltauth.com\tCLEAN\t2025-01-07\tPASSIVE_CAPTURE\n08\tcsgo.net\tBLOCKED\tcn2.easylot.net\tCLEAN\t2016-09-03\tPASSIVE_CAPTURE\n09\tggdrop.com\tBLOCKED\tggauth.com\tCLEAN\t2023-05-03\tPASSIVE_CAPTURE\n10\trustchance.com\tBLOCKED\thgfuihd.com\tCLEAN\t2019-01-27\tPASSIVE_CAPTURE\n11\tskin.fans\tBLOCKED\tauth.skinfans.com\tCLEAN\t2018-07-16\tPASSIVE_CAPTURE\n12\tskinport.com\tBLOCKED\tskinport.app\tCLEAN\t2020-06-20\tPASSIVE_CAPTURE\n13\tskins.cash\tBLOCKED\tskinscash.live\tCLEAN\t2019-12-05\tPASSIVE_CAPTURE\n14\ttf2hunt.com\tBLOCKED\trstspcl.com\tCLEAN\t2020-08-08\tPASSIVE_CAPTURE\n15\tdaddyskins.com\tBLOCKED\tgo-go-daddy.com\tCLEAN\t2019-01-26\tPASSIVE_CAPTURE\n16\tkey-drop.com\tBLOCKED\tkdauth.com\tCLEAN\t2026-05-13\tPASSIVE_CAPTURE\n17\tclash.gg\tBLOCKED\tclggauth.com\tCLEAN\t2024-09-16\tPASSIVE_CAPTURE\n18\tc5game.com\tBLOCKED\twww.imbastar.com\tCLEAN\t2016-02-27\tPASSIVE_CAPTURE\n19\tswap.gg\tBLOCKED\tswapauth.com\tCLEAN\t2018-10-06\tPASSIVE_CAPTURE\n20\tshadowpay.com\tBLOCKED\tthelogins.com\tCLEAN\t2018-01-22\tPASSIVE_CAPTURE\n21\tcsgocases.com\tBLOCKED\tlog-1n.com\tCLEAN\t2017-11-27\tPASSIVE_CAPTURE\n22\tcsgogem.com\tBLOCKED\tapi.csgem.com\tCLEAN\t2014-03-08\tPASSIVE_CAPTURE\n23\tgamdom.com\tBLOCKED\tlogin.gambldom.com\tCLEAN\t2017-09-24\tPASSIVE_CAPTURE\n24\t12cs.fail\tBLOCKED\tfail.games\tCLEAN\t2021-08-24\tPASSIVE_CAPTURE\n25\tskinsnipe.com\tBLOCKED\tpricing.tradeupspy.com\tCLEAN\t2020-03-11\tPASSIVE_CAPTURE\n26\tcsgobig.com\tBLOCKED\tletmeinbig.com\tCLEAN\t2023-01-20\tPASSIVE_CAPTURE\n\n* Nota: Verificações passivas realizadas em pontos finais não autenticados do Filtro de Links «Steam» em 2026-09-19 e 2026-09-21.. Os corpos das respostas HTTP em bruto e os resumos SHA-256 são preservados no conjunto de dados do repositório (steam_tos_assets/linkfilter-2026-09-22.json).\n\nSecção III: Registo de Anexos B — Censo Exaustivo das Entidades Comerciais Auditar175REF: EX-175-, CENSOS PRINCIPAIS\n\nO registo seguinte detalha todas as plataformas comerciais de terceiros 175 ativamente verificadas na base de dados de auditoria. Cada registo indica o nome da entidade, o domínio comercial principal, a rota de autenticação OpenID observada Steam, a classificação da atividade, os mapeamentos de violação contratual (SSA § 2.G, SSA § 4.C, SSA § 1.C) e o campo de ação registado no conjunto de dados de origem. A indicação «Ver provas datadas» remete o leitor para registos de apoio; não significa que Valve não tenha tomado qualquer medida. A ausência de um campo de ação é indicada como «não estabelecido».\n\nExposição\tNome da entidade e domínio principal\tRota de autenticação observada / Proxy\tClassificação\tViolação contratual\tValve Ação\nEX-001\tCSGORoll\ncsgoroll.com\n\t\nwww.csgoroll.com\nDIRECT\n\tSkin Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-002\tCSGOEmpire\ncsgoempire.com\n\t\ncsgoempirelogin4.com\nSPLIT PROXY\n\tCasino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-003\tRollbit\nrollbit.com\n\t\nrbsnin.com\nSPLIT PROXY\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-004\t500 Casino\n500.casino\n\t\nfivezerozero.co\nSPLIT PROXY\n\tLicenced Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-005\tCSGOBig\ncsgobig.com\n\t\ncsgobig.com\nDIRECT\n\tRoulette/Slots\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-006\tCaseDrop\ncasedrop.com\n\t\ncasedrop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-007\tRustReaper\nrustreaper.com\n\t\nrustreaper.com\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-008\tBanditCamp\nbanditcamp.com\n\t\nbanditcamp.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-009\tSkinBox\nskinbox.com\n\t\nskinbox.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-010\tTastyDrop\ntastydrop.com\n\t\ntastydrop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-011\tCSGOPolygon\ncsgopolygon.gg\n\t\ncsgopolygon.gg\nDIRECT\n\tRoulette Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-012\tMagicDrop\nmagicdrop.ru\n\t\nmagicdrop.ru\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-013\tCSDice\ncsdice.com\n\t\ncsdice.com\nDIRECT\n\tDice Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-014\tRustly\nrustly.com\n\t\nrustly.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-015\tSkinOdds\nskinodds.com\n\t\nskinodds.com\nDIRECT\n\tUpgrader Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-016\tCSGOWin\ncsgowin.com\n\t\ncsgowin.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-017\tCSGORun\ncsgorun.net\n\t\ncsgorun.net\nDIRECT\n\tCrash Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-018\tOpenSkins\nopenskins.com\n\t\nopenskins.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-019\tRustBet\nrustbet.com\n\t\nrustbet.com\nDIRECT\n\tRust Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-020\tCSGOMagic\ncsgomagic.com\n\t\ncsgomagic.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-021\tCSGOBounty\ncsgobounty.com\n\t\ncsgobounty.com\nDIRECT\n\tUpgrader/Contract\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-022\tEZSkins\nezskins.com\n\t\nezskins.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-023\tRustCases\nrustcases.com\n\t\nrustcases.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-024\tCSGOReaper\ncsgoreaper.com\n\t\ncsgoreaper.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-025\tCSGOCases\ncsgocases.com\n\t\ncsgocases.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-026\tCSGO-Skins\ncsgo-skins.com\n\t\ncsgo-skins.com\nDIRECT\n\tCase Upgrader\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-027\tCSGONet\ncsgonet.com\n\t\ncsgonet.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-028\tWTFSkins\nwtfskins.com\n\t\nwtfskins.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-029\tCSGOFast\ncsgofast.com\n\t\nsteam-login.authtofast.com\nSPLIT PROXY\n\tRoulette Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-030\tDuelbits\nduelbits.com\n\t\nswitchflips.com\nSPLIT PROXY\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-031\tFlameCases\nflamecases.com\n\t\nflamecases.com\nDIRECT\n\tCase Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-032\tFarmskins\nfarmskins.com\n\t\nsteam.kobal.cc\nSPLIT PROXY\n\tCase Opener\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-033\tCSGOLuck\ncsgoluck.com\n\t\ncsgoluck.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-034\tGamedom\ngamedom.com\n\t\ngamedom.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-035\tSkin.Club\nskin.club\n\t\nsc-auth.net\nSPLIT PROXY\n\tCase Battles\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-036\tDaddySkins\ndaddyskins.com\n\t\ndaddyskins.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-037\tInsane.gg\ninsane.gg\n\t\napi.insane.gg\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-038\tRustix\nrustix.gg\n\t\nrustix.gg\nDIRECT\n\tRust Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-039\tSkins.Club\nskins.club\n\t\nskins.club\nDIRECT\n\tSkin Upgrade\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-040\tCSGOHouse\ncsgohouse.org\n\t\ncsgohouse.org\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-041\tSkinRave\nskinrave.net\n\t\nskinrave.net\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-042\tBloodyCase_GG\nbloodycase.gg\n\t\nbloodycase.gg\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-043\tCSGOClicker\ncsgoclicker.com\n\t\ncsgoclicker.com\nDIRECT\n\tClicker/Upgrade\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-044\tRustBet_GG\nrustbet.gg\n\t\nrustbet.gg\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-045\tCS_Drop\ncs-drop.com\n\t\ncs-drop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-046\tHellStore\nhellstore.net\n\t\nhellstore.net\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-047\tRustLoot\nrustloot.com\n\t\nrustloot.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-048\tCSGO_Case\ncsgo-case.com\n\t\ncsgo-case.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-049\tCS2Skin\ncs2skin.com\n\t\ncs2skin.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-050\tJuice_GG\njuice.gg\n\t\nletmeinjuice.com\nSPLIT PROXY\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-051\tGGDrop\nggdrop.com\n\t\nggauth.com\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-052\tCSGOGem\ncsgogem.com\n\t\ncsgogem.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-053\tRainbet\nrainbet.com\n\t\nservices.rainbet.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-054\tHowl_GG\nhowl.gg\n\t\nhowl.uno\nSPLIT PROXY\n\tSkins Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-055\tChicken_GG\nchicken.gg\n\t\nchicken.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-056\tCSGOCasino_GG\ncsgocasino.gg\n\t\napi.csgocasino.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-057\tHunt_GG\nhunt.gg\n\t\napi.hunt.gg\nDIRECT\n\tSkins Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-058\tCSBattle\ncsbattle.com\n\t\ncsbattle.com\nDIRECT\n\tCase Battles\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-059\tSkinRave_GG\nskinrave.gg\n\t\napi.skinrave.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-060\tCSDouble\ncsdouble.gg\n\t\ncsdouble.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-061\tRustChance\nrustchance.com\n\t\nhgfuihd.com\nSPLIT PROXY\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-062\tRustClash\nrustclash.com\n\t\nrustclash.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-063\tCobaltLab\ncobaltlab.tech\n\t\ncobaltauth.com\nSPLIT PROXY\n\tRust Automation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-064\tRaided_GG\nraided.gg\n\t\napi.raided.gg\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-065\tRustNeo\nrustneo.gg\n\t\nrustneo.gg\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-066\tSplits_GG\nsplits.gg\n\t\nsplits.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-067\tUpgrader_Pro\nupgrader.pro\n\t\nupgauth.space\nSPLIT PROXY\n\tSkin Upgrader\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-068\tSkinFans\nskin.fans\n\t\nauth.skinfans.com\nSPLIT PROXY\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-069\tHotPizza\nhotpizza.one\n\t\nhotpizza.one\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-070\tG4Skins\ng4skins.com\n\t\nauth.g4s.to\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-071\t12CS_Fail\n12cs.fail\n\t\n12cs.fail\nDIRECT\n\tCrash Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-072\tTF2Royal\ntf2royal.com\n\t\ntf2auth.com\nSPLIT PROXY\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-073\tTF2Easy\nwww.tf2easy.com\n\t\nwww.tf2easy.com\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-074\tTF2Hunt\ntf2hunt.com\n\t\nrstspcl.com\nSPLIT PROXY\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-075\tTF2Bet\ntf2.bet/coinflip\n\t\ntf2.bet\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-076\tTF2Blaze\ntf2blaze.com\n\t\ntf2blaze.com\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-077\tOpenStars_GG\nopenstars.gg\n\t\nopenstars.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-078\tShuffle_Com\nshuffle.com\n\t\nshuffle.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-079\tSkins.com\nskins.com\n\t\napi.skins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-080\tWhite.Market\nwhite.market\n\t\nwhite.market\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-081\tBuff.Market\nbuff.market\n\t\nbuff.market\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-082\tAvan.Market\navan.market\n\t\navan.market\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-083\tCS.MONEY\ncs.money\n\t\nauth.dota.trade\nSPLIT PROXY\n\tTrading Engine\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-084\tUUSkins\nuuskins.com\n\t\nuuskins.com\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-085\tYouPin898\nyoupin898.com\n\t\nyoupin898.com\nDIRECT\n\tMass Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-086\tMoon.Market\nmoon.market\n\t\nmoon.market\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-087\tCSFloat\ncsfloat.com\n\t\ncsgofloat.com\nSPLIT PROXY\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-088\tSkin.Land\nskin.land\n\t\nauth.skin.land\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-089\tC5Game\nc5game.com\n\t\nc5game.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-090\tHaloSkins\nhaloskins.com\n\t\nhaloskins.com\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-091\tBuff.163\nbuff.163.com\n\t\nbuff.163.com\nDIRECT\n\tCorporate Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-092\tWaxpeer\nwaxpeer.com\n\t\nwaxpeer.com\nDIRECT\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-093\tCS.MONEY Bot\ncs.money\n\t\nauth.dota.trade\nSPLIT PROXY\n\tBot Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-094\tMarket.CSGO\nmarket.csgo.com\n\t\ndota2.net\nSPLIT PROXY\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-095\tSkinport\nskinport.com\n\t\nskinport.app\nSPLIT PROXY\n\tRegulated Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-096\tSkinFlow\nskinflow.gg\n\t\napi.skinflow.gg\nDIRECT\n\tMarketplace/Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-097\tDMarket\ndmarket.com\n\t\ndmarket.com\nDIRECT\n\tUS Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-098\tSkin.place\nskin.place\n\t\napi.skin.place\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-099\tSkinsMonkey\nskinsmonkey.com\n\t\nskinsmonkey.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-100\tSkinBaron\nskinbaron.de\n\t\nskinbaron.com\nSPLIT PROXY\n\tCorporate Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-101\tSteam\nsteamcommunity.com/market\n\t\nsteamcommunity.com/market\nDIRECT\n\tOfficial Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-102\tRustTM\nrust.tm\n\t\ndota2.net\nSPLIT PROXY\n\tRust Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-103\tPirateSwap\npirateswap.com\n\t\nlogin.pirateswap.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-104\tMannco.Store\nmannco.store\n\t\nmannco.store\nDIRECT\n\tTF2 Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-105\tSkinSwap\nskinswap.com\n\t\napi.skinswap.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-106\tLootFarm\nlootfarm.com\n\t\nlootfarm.com\nDIRECT\n\tTrading Platform\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-107\tRustskins\nrustskins.com\n\t\nrustskins.com\nDIRECT\n\tRust Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-108\tExeSkins\nexeskins.com\n\t\nexeskins.com\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-109\tBalticSkins\nbalticskins.com\n\t\nbalticskins.com\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-110\tCS.Trade\ncs.trade\n\t\ncs.trade\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-111\tRapidSkins\nrapidskins.com\n\t\napi.rapidskins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-112\tTradeIt\ntradeit.gg\n\t\nconnect-tradeit.com\nSPLIT PROXY\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-113\tKrakatoa\nkrakatoa.com\n\t\nkrakatoa.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-114\tShadowPay\nshadowpay.com\n\t\nshadowpay.com\nDIRECT\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-115\t49skins\n49skins.com\n\t\napi.49skins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-116\tSkinVault\nskinvault.gg\n\t\napi.skinvault.gg\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-117\tAim Market\naim.market\n\t\naim.market\nDIRECT\n\tSkins Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-118\tSkinout\nskinout.gg\n\t\nauth.skinout.gg\nDIRECT\n\tInstant Sell Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-119\tNTSkins\nntskins.com\n\t\nntskins.com\nDIRECT\n\tSkins Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-120\tIGXE\nigxe.cn\n\t\nigxe.cn\nDIRECT\n\tChinese Powerhouse\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-121\tSwap.gg\nswap.gg\n\t\nswap.gg\nDIRECT\n\tAutomated Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-122\tBitskins\nbitskins.com\n\t\nbitskins.com\nDIRECT\n\tCash-out Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-123\tGamerPay\ngamerpay.gg\n\t\ngamerpay.gg\nDIRECT\n\tP2P Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-124\tTF2Mart\ntf2mart.com\n\t\ntf2mart.com\nDIRECT\n\tTF2 Automation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-125\tSkinBid\nskinbid.com\n\t\nskinbid.com\nDIRECT\n\tSkin Auctions\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-126\tLootBear\nlootbear.com\n\t\nlootbear.com\nDIRECT\n\tSkin Rental\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-127\tBackpack.tf\nbackpack.tf\n\t\nbackpack.tf\nDIRECT\n\tTF2 Valuation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-128\tScrap.tf\nscrap.tf\n\t\nscrap.tf\nDIRECT\n\tTF2 Scrap Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-129\tMarketplace.tf\nmarketplace.tf\n\t\nmarketplace.tf\nDIRECT\n\tTF2 Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-130\tSTNTrading\nstntrading.eu\n\t\nstntrading.eu\nDIRECT\n\tTF2 Botnet\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-131\tSkins.Cash\nskins.cash\n\t\nskinscash.live\nSPLIT PROXY\n\tInstant Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-132\tSkinWallet\nskinwallet.com\n\t\nskinwallet.com\nDIRECT\n\tInstant Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-133\tDota2Market\ndota2market.com\n\t\ndota2market.com\nDIRECT\n\tDota 2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-134\tCSGO.NET\ncsgo.net\n\t\ncn2.easylot.net\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-135\tCybershoke\ncybershoke.net\n\t\nauth.cybershoke.net\nDIRECT\n\tCommunity Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-136\tXPlay_GG\nxplay.gg\n\t\nxplay.gg\nDIRECT\n\tServer Network\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-137\tFastCup\nfastcup.net\n\t\napi.fastcup.net\nDIRECT\n\tMatchmaker Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-138\tEsportal\nesportal.com\n\t\nesportal.com\nDIRECT\n\tMatchmaking Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-139\tGamersClub\ngamersclub.com.br\n\t\ngamersclub.com.br\nDIRECT\n\tLATAM Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-140\tLeetify\nleetify.com\n\t\nleetify.com\nDIRECT\n\tSaaS Analytics\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-141\tScope_GG\nscope.gg\n\t\nscope.gg\nDIRECT\n\tSaaS Analytics\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-142\tTradeUpSpy\ntradeupspy.com\n\t\napi.tradeupspy.com\nDIRECT\n\tSaaS Tools\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-143\tEpidemic_GG\nepidemic.gg\n\t\nepidemic.gg\nDIRECT\n\tSaaS Tools\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-144\tCSDeals\ncs.deals\n\t\napi.cs.deals\nDIRECT\n\tMarketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-145\tPricempire\npricempire.com\n\t\npricempire.com\nDIRECT\n\tSaaS Price DB\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-146\tCS2Stash\ncs2stash.com\n\t\ncs2stash.com\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-147\tCSGOSkins\ncsgoskins.gg\n\t\ncsgoskins.gg\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-148\tSteamAnalyst\nsteamanalyst.com\n\t\nsteamanalyst.com\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-149\tSteamCardExchange\nsteamcardexchange.net\n\t\nsteamcardexchange.net\nDIRECT\n\tTrading Exchange\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-150\tDotaBuff\ndotabuff.com\n\t\ndotabuff.com\nDIRECT\n\tSaaS Tracker\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-151\tTracker_GG\ntracker.gg\n\t\ntracker.gg\nDIRECT\n\tSaaS Tracker\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-152\tFSB Market (an anonymized label; the original name is withheld here)\nFSB Market\n\t\nFSB Market\nDIRECT\n\tMass Blackmarket\tSSA § 2.G, SSA § 4.C, SSA § 1.C\tSee dated evidence\nEX-153\tFunPay\nfunpay.com\n\t\nfunpay.com\nDIRECT\n\tAccount Exchange\tSSA § 2.G, SSA § 4.C, SSA § 1.C\tSee dated evidence\nEX-154\tPlayerAuctions\nplayerauctions.com\n\t\nplayerauctions.com\nDIRECT\n\tGrey Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-155\tEldorado.gg\neldorado.gg\n\t\neldorado.gg\nDIRECT\n\tAccount Portal\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-156\tG2A\ng2a.com\n\t\ng2a.com\nDIRECT\n\tMass Key Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-157\tKinguin\nkinguin.net\n\t\nkinguin.net\nDIRECT\n\tMass Key Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-158\tG2G.com\ng2g.com\n\t\ng2g.com\nDIRECT\n\tVirtual Services\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-159\tPlayerup\nplayerup.com\n\t\nplayerup.com\nDIRECT\n\tAccount Broker\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-160\tZ2U.com\nz2u.com\n\t\nwww.z2u.com\nDIRECT\n\tReady-Account Hub\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-161\tSmurfHub\nsmurfhub.net\n\t\nsmurfhub.net\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-162\tSmurfAccounts\nsmurfaccounts.com\n\t\nsmurfaccounts.com\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-163\tBuyCSGORank\nbuycsgorank.com\n\t\nbuycsgorank.com\nDIRECT\n\tRank Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-164\tCSGOSmurfKings\ncsgosmurfkings.com\n\t\ncsgosmurfkings.com\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-165\tSmurfStore_Co\nsmurfstore.co\n\t\nsmurfstore.co\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-166\tSteamLvlUp\nsteamlvlup.com\n\t\nsteamlvlup.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-167\tSteamLevels\nsteamlevels.com\n\t\nsteamlevels.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-168\tLevelSteam\nlevelsteam.com\n\t\nlevelsteam.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-169\tSteamLevelU\nsteamlevelu.com\n\t\nsteamlevelu.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-170\tEloKing\neloking.com\n\t\neloking.com\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-171\tBoosteria\nboosteria.org\n\t\nboosteria.org\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-172\tOvergear\novergear.com\n\t\novergear.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-173\tBlazingBoost\nblazingboost.com\n\t\nblazingboost.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-174\tDota2Boost\ndota2boost.com\n\t\ndota2boost.com\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-175\tBuyBoost\nbuyboost.com\n\t\nbuyboost.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nSecção IV: Arquitetura Técnica e Mecanismos de AutenticaçãoREF: ANÁLISE TÉCNICA -01\n\n1. Ausência de validação da titularidade do domínio no OpenID 2.0: A implementação do protocolo OpenID 2.0 pela Valve (https://steamcommunity.com/openid/login) avalia o openid.return_to e openid.realm parâmetros sem exigir o registo prévio do programador, a verificação de um desafio criptográfico ou a validação da titularidade do domínio. Qualquer operador comercial pode redirecionar os utilizadores para o ecrã de início de sessão do Valve e receber uma afirmação de identidade assinada criptograficamente (contendo o SteamID de 64-bits) redirecionada para domínios arbitrários.\n\n2. Consulta programática do inventário e abuso da chave «API»: Assim que a autenticação do utilizador for confirmada através do OpenID, os operadores consultam os pontos de extremidade de WebAPIs públicos e de parceiros (IEconItems_730/GetPlayerItems) para indexar ativos de inventário em tempo real. As redes de negociação automatizadas utilizam tokens de sessão programáticos para apresentar, consultar e aceitar ofertas de negociação ponto a ponto (P2P), infringindo diretamente a proibição de interação não humana prevista no §4.C da SSA.\n\n3. Assimetria do filtro de ligações: A coexistência de avisos de domínio dirigidos aos consumidores, a par de pontos finais de autenticação totalmente funcionais, cria uma contradição regulamentar: a telemetria de segurança do Valve classifica estes operadores como «potencialmente maliciosos», mas a infraestrutura de autenticação do Valve continua a autenticar a sua base de utilizadores.\n\nMetodologia Probatória e Declaração sobre a Cadeia de Custódia\n\nEste documento foi gerado a partir de capturas de rede não autenticadas, consultas históricas ao registo RDAP e manifestos de hash criptográfico verificados. Nenhuma credencial de início de sessão de utilizador foi submetida a testes de comprometimento nem processada. Todas as conclusões refletem o estado observável da rede de produção à data de 2026. Este documento constitui uma prova técnica imparcial, preparada para inquéritos judiciais, regulamentares e públicos.\n\nRESUMO: SHA-256 VERIFICADO\nc507c9025f93da0aadaf395c4d8882f25973211c318ee8e9b6f18a5b3755e050\nARQUIVO: REGISTO JURÍDICO PÚBLICO\nEMITIDO E ASSINADO POR: phishdestroy.io · Coligação para a Investigação Forense\nSTATUS JURÍDICO: TODOS OS DIREITOS CEDIDOS À HUMANIDADE · CC0 DOMÍNIO PÚBLICO UNIVERSAL",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Lei da Auditoria Forense e Anexo Regulamentar"
          }
        ],
        "links": []
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/pt/regulatory_act_print.content.json",
      "export_json_sha256": "30635eca0aea7d9b10e439b15f8e31be148b633e6b242d6478a63b7315e69c06"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "pt/security_timeline.html",
      "language": "pt",
      "title": "Cronologia da segurança — O dossiê «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/pt/security_timeline",
      "source_html_sha256": "97883ba81dfddc7763163ff8e06249c39da1fc49e7c873f0e759202b56c9d5a3",
      "exported_at": "2026-09-29T00:18:11.133Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "security_timeline.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/pt/security_timeline.pdf?v=print-20260929-v5",
        "sha256": "6ed677715d123e5521a53ec8766e35113556fe67ee202c463d6a9566268ed15e",
        "bytes": 98111,
        "pages": 7
      },
      "integrity": {
        "signed_object": "security_timeline.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "security_timeline.content.json.asc",
        "digest_file": "security_timeline.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify security_timeline.content.json.asc security_timeline.content.json",
          "sha256sum -c security_timeline.content.json.sha256"
        ]
      },
      "content": {
        "text": "O HISTÓRICO DE SEGURANÇAEXPOSIÇÃO / INSCRIÇÕES PARA O «16»\n\n2018 — 2026\n\nCronologia de segurança — 2018 para 2026\n\nA segurança mudou. Siga o registo.\n\nO QUE ESTA SECÇÃO DEMONSTRA\n\nEste registo cronológico reconstrói oito anos de alterações de segurança na pilha de transações e autenticação dSteam. Acompanha a implementação da retenção de transações diárias 2018 7-, as confirmações por telemóvel da Web 2023 API e a descontinuação dos tokens de sessão 2026 face a técnicas de contorno documentadas. A cronologia demonstra que as atualizações da plataforma ficaram consistentemente aquém dos vetores de exploração conhecidos, mantendo, no entanto, as vantagens estruturais para os operadores comerciais.\n\n← Voltar ao resumo executivo\n\nBloqueios comerciais. Controlos de início de sessão. Restrições de «API». Um registo cronológico do que mudou — e do que as fontes realmente comprovam.\n\nExplora a linha do tempo ↓\nOITO ANOS. UM RECORDE.16marcos a analisar\n\nCada entrada mantém a data de envio e a fonte. A verificação é apresentada ao lado da mesma.\n\nREVISADO / 24 SET 2026\n10Evento e data confirmados\n06Parcialmente verificado\n00Incompatibilidade de fonte\n00É necessária uma fonte\nComo interpretar este registo\n\nEvento e data confirmados: ambas apoiadas por uma fonte primária de fácil compreensão. Parcialmente verificado: Está documentada uma alteração relacionada, mas a data ou o âmbito continuam por definir. Incompatibilidade de fonte: O material indicado no link não corrobora a alegação apresentada. É necessária uma fonte: Nesta análise, não foi verificada nenhuma fonte datada que correspondesse. O facto de uma entrada não ter sido esclarecida não constitui prova de que um acontecimento não tenha ocorrido.\n\nAs datas relativas às entradas por resolver correspondem às datas de envio e não às datas de lançamento confirmadas. O texto original da investigação não foi reescrito.\n\nA cronologia\n01 — 16\nPesquisar o registoTemaProvasEncomenda\n\n16 das publicações de «16» · mais recentes primeiro\n\n202609-01Data de envio\nComunidadeParcialmente verificado\nAvisos sobre mensagens suspeitas nas conversas em grupo\n\nUm aviso oficial sobre a versão beta confirma a disponibilização da funcionalidade em 31 de agosto. A data de lançamento da versão estável indicada em 1 de setembro ainda carece de notas de lançamento específicas.\n\nSteam Versão Beta para Clientes — 31de agosto ↗arquivado em 2026-03-13 ↗\nEntrada original e link enviado\n\nSinalização automática de conversas suspeitas\n\nVerificar o código-fonte enviado ↗\n202601-16Data de verificação\nAPIEvento e data confirmados\nPermissões granulares e lista de IPs autorizados para chaves de editor (anúncio do Valve)\n\nNo dia 16 de janeiro de 2026, Valve foi publicado um comunicado oficial sobre o Steamworks (\"NOVIDADE: Melhores permissões e controlos para as chaves de «API» na Web\") que confirmam a existência de novas ferramentas de permissão granular que permitem aos programadores segmentar as chaves do WebAPI em grupos distintos (Dados gerais, microtransações, economia e vendas), restringir as chaves a IDs de aplicação específicas e aplicar uma lista branca de IPs de servidor.\n\nO flagrante duplo padrão: Este comunicado oficial confirma que o site Valve já desenvolveu na íntegra a infraestrutura técnica necessária para a gestão granular de permissões API e restrições de IP, mas retém-nas deliberadamente das contas de utilizador normais (steamcommunity.com/dev/apikey). As chaves de «API» dos utilizadores normais continuam a ser credenciais monolíticas do tipo «tudo ou nada», sem lista de endereços IP autorizados — o que constitui precisamente a lacuna técnica que permite a existência da indústria multimilionária de interceção de transações «API».\n\nValve Anúncio — NOVIDADE: Melhores permissões e controlos para as chaves de «API» na Web (16 Jan 2026) ↗· Documentação: Autenticação na Web do SteamAPI ↗\nEntrada original e link enviado\n\nAPIes da Web da Steamworks: Âmbitos Granulares\n\nConsulte o anúncio oficial do Valve no Steamworks (493839547938902179) ↗\n202507-15Data de verificação\nNegociaçãoEvento e data confirmados\nAs transações CS2 passam a dispor de um período de reversão de sete dias\n\nO comunicado da Valve, datado de [data], anuncia a reversão das transações de itens do Counter-Strike realizadas nos sete dias anteriores. Embora tenha sido concebido para mitigar o «hijacking», as auditorias económicas realizadas por terceiros (CSMarketCap ↗) registou um $104M (-25%) recolher em capitalização bolsista no espaço de 24 horas, devido a uma perturbação nas transações à vista. Conforme analisado por Skinvault ↗, o facto de se desencadear uma reversão implica um bloqueio automático 30-para operações de day trading na conta. No verão 2026, Valve, passou-se de reinícios globais à meia-noite UTC para temporizadores individuais por item, com duração de um minuto (Skin.land ↗).\n\nValve — 15 Anúncio de 2025, em julho de ↗· Análise da CSMarketCap ↗\nEntrada original e link enviado\n\nProteção de transações CS2 / Janela de reversão\n\nVerificar o código-fonte enviado ↗\n202505-14Data de verificação\nAutenticaçãoEvento e data confirmados\nValve publica um aviso de segurança sobre contas devido a fugas de SMS\n\nO comunicado oficial da Valve, publicado em 5 de maio 14, 2025,, aborda a segurança das contas e os sistemas de autenticação por SMS. Embora o comunicado se centre nas fugas de SMS e confirme que nenhum sistema da Steam foi violado, constitui uma atualização oficial de segurança na data em que foi publicado.\n\nValve — Uma nota sobre a segurança da sua conta Steam ↗\nEntrada original e link enviado\n\nComunicado sobre a segurança da conta\n\nVerificar o código-fonte enviado ↗\n202410-02Data de verificação\nNegociaçãoEvento e data confirmados\nSete dias antes da revenda ou da nova comercialização\n\nAs notas de lançamento abrangem os itens adquiridos através da loja do jogo, incluindo o Arsenal, as ofertas de troca e o Mercado da Comunidade. O âmbito documentado é mais vasto do que apenas os itens do Arsenal.\n\nValve — Notas de lançamento do 10/2/2024 ↗\nEntrada original e link enviado\n\nCS2 The Armory / 7-Day Hold\n\nVerificar o código-fonte enviado ↗\n202409-18Data de envio\nNegociaçãoParcialmente verificado\nRestrições relativas a novos dispositivos verificadas nas Páginas de Ajuda\n\nA documentação oficial de suporte do Steam confirma uma restrição de day trading 7-ao iniciar sessão a partir de um novo dispositivo que não tenha sido autorizado há, pelo menos, 7 dias. Embora a data exata de implementação de 18, 2024, em setembro não conste como um marco no registo de alterações, a funcionalidade está totalmente documentada.\n\nSteam Apoio — Restrições de negociação e de mercado ↗\nEntrada original e link enviado\n\nRestrição de transações no início de sessão num novo dispositivo\n\nVerificar o código-fonte enviado ↗\n202402-14Data de envio\nComunidadeParcialmente verificado\nFoi implementado um período de espera para a troca de nome em 2024\n\nOs registos da comunidade e dos programadores confirmam que, no início de 2024,, o Valve introduziu, sem aviso prévio, 2-um período de espera de4 horas para transações, imediatamente após uma alteração do nome de perfil, com o objetivo de mitigar esquemas de fraude por suplantação de identidade. Uma vez que Valve não publicou qualquer comunicado de imprensa oficial, registo de alterações do cliente ou artigo de apoio relativo a esta restrição, a data apresentada de 14, em fevereiro, carece de verificação formal; o guia do Steam Workshop serve como corroboração indireta da comunidade, em vez de documentação oficial Valve.\n\nSteam Guia do Workshop (corroboração indireta) — Detalhes sobre a restrição à alteração de nome ↗\nEntrada original e link enviado\n\nSuspensão da alteração do nome do perfil / avatar\n\nVerificar o código-fonte enviado ↗\n202312-04Data de verificação\nAPIEvento e data confirmados\nA criação da chave requer confirmação através do telemóvel\n\nVerificou-se que a introdução da confirmação obrigatória através da aplicação móvel «Steam Guard» para a criação de chaves Web API ocorreu no final de 2023,, conforme documentado por bibliotecas de programadores de terceiros. A data exata de 4, 2023, representa o período de implementação observado na comunidade de programadores.\n\nDocumentação do responsável pela manutenção — 2024 de março ↗arquivado em 2026-09-24 ↗\nEntrada original e link enviado\n\nConfirmação por telemóvel para chaves «API»\n\nVerificar o código-fonte enviado ↗\n202310-24Data de verificação\nDesenvolvedorEvento e data confirmados\nEntra em vigor a FA obrigatória 2para a definição de versões do jogo em tempo real\n\nO anúncio oficial da Valve no Steamworks, publicado em 10 de outubro 10, 2023,, confirma que, a partir de 10 de outubro 24, 2023,, qualquer conta que coloque uma compilação em produção no ramo padrão de uma aplicação lançada terá de autorizar a alteração através de SMS ou da aplicação móvel Steam. Esta alteração atualizou diretamente a página Web SetAppBuildLive API.\n\nSteamworks — Melhorias de segurança na gestão de compilações e utilizadores ↗arquivado em 2025-12-03 ↗\nEntrada original e link enviado\n\nAutenticação multifatorial por SMS para publicações de compilações de jogos\n\nVerificar o código-fonte enviado ↗\n202307-12Data de envio\nComunidadeParcialmente verificado\nAvisos de conteúdo personalizados nas biografias, observados pela comunidade\n\nSteam Relatos da comunidade, a partir de julho 2023, indicam que as biografias dos perfis personalizados que continham links externos ou palavras-chave passaram a apresentar avisos de conteúdo automáticos. A data de envio de julho 12, 2023, coincide com a primeira onda de relatos dos utilizadores nos fóruns da comunidade Steam.\n\nSteam Fórum da Comunidade — Relatórios de aviso sobre conteúdo biográfico ↗\nEntrada original e link enviado\n\nAviso sobre o conteúdo da biografia personalizada\n\nVerificar o código-fonte enviado ↗\n202301-25Data de envio\nComunidadeParcialmente verificado\nOs períodos de espera para a filtragem e edição de links de perfil estão ativos\n\nA documentação oficial de apoio da Steam confirma que as ligações nas biografias personalizadas são filtradas e que alterações abusivas de nome ou avatar podem desencadear proibições de edição. Embora a implementação exata do período de espera de uma hora 4-em 1 de janeiro 25, 2023, represente o início observado, o próprio mecanismo de filtragem de ligações está totalmente ativo, conforme indicado na página de ajuda disponibilizada.\n\nSteam Apoio — Restrições relativas ao nome do perfil e ao avatar ↗\nEntrada original e link enviado\n\nPerfil LINK REMOVIDO / Tempo de recarga\n\nVerificar o código-fonte enviado ↗\n202210-24Data de verificação\nAutenticaçãoEvento e data confirmados\nSteam Transição do cliente para os tokens de atualização e de acesso do OAuth\n\nPrincipais atualizações de clientes e aplicações móveis da Valve em outubro A 2022 reformulou o sistema de autenticação Steam. A antiga estrutura de cookies de sessão foi substituída por tokens de acesso e de atualização baseados em OAuth, tendo sido introduzida uma lista de dispositivos autorizados ativos para permitir a revogação manual de sessões ativas.\n\nValve — Atualização da aplicação móvel «Steam» e reformulação do sistema de autenticação ↗\nEntrada original e link enviado\n\nSteam Reestruturação do processo de início de sessão / Truncagem de cookies\n\nConsulte o anúncio «Valve» ↗\n202210-12Data de verificação\nAutenticaçãoEvento e data confirmados\nInício de sessão por QR e gestão de dispositivos autorizados\n\nO anúncio de Valve sobre o «12», publicado em outubro, descreve o início de sessão através de código QR, a aprovação ou recusa de inícios de sessão e uma lista de dispositivos que permite revogar o acesso à conta.\n\nValve — A aplicação móvel «Steam», na sua versão atualizada, já está disponível ↗\nEntrada original e link enviado\n\nSteam Aplicação móvel 3.0 / Início de sessão com QR\n\nVerificar o código-fonte enviado ↗\n202205-10Data de envio\nAPIParcialmente verificado\nOs pontos finais de cancelamento de transações foram removidos da lista pública API\n\nOs registos dos programadores confirmam que, em maio de 2022, Valve, foram silenciosamente removidos pontos de extremidade de gestão de transações, tais como IEconService/CancelTradeOffer e DeclineTradeOffer, do Web API (documentado em node-steam-tradeoffer-manager #325). Embora os métodos continuem a funcionar nos protocolos privados do cliente, a data de 10, 2022, representa a sua remoção efetiva das APIs Web públicas, com o objetivo de combater os painéis fraudulentos.\n\nDiscussão dos programadores — Tópico n.º325 (CancelTradeOffer removido) ↗· Site da Steamworks API — Documentação do IEconService ↗\nEntrada original e link enviado\n\nRemoção dos pontos finais de cancelamento de transações\n\nVerificar o issue n.º325 do node-steam-tradeoffer-manager ↗\n202005-25Data de verificação\nNegociaçãoEvento e data confirmados\nOs itens do Dota2 passam a ter um período de espera de sete dias para a troca\n\nEm maio de 25, 2020,, a par do lançamento do Passe de Batalha do The International 10 (blog.dota2.com/2020/05/the-international-10-battle-pass/), Valve implementou um bloqueio de trocas de um dia 7-para os itens do Dota 2, em consonância com a política do 2018 para o Counter-Strike. Esta restrição aplica-se a todos os itens trocados e às compras no Mercado.\n\nComunidade Dota 2 — Bloqueio de trocas e atualização do cliente do TI10 ↗\nEntrada original e link enviado\n\nDota 2 / 7-Bloqueio de transações diárias\n\nVerificar o código-fonte enviado ↗\n201803-29Data de verificação\nNegociaçãoEvento e data confirmados\nOs itens do CS:GO trocados ficam sujeitos a um período de espera de sete dias\n\nAs notas oficiais de lançamento confirmam a data e a restrição. O URL fornecido redirecionava para uma atualização do mapa em 2013; o URL correspondente das notas de lançamento termina em 20309.\n\nValve — Notas de lançamento do 3/29/2018 ↗\nEntrada original e link enviado\n\nCS:GO / Bloqueio de transações diárias no «7-»\n\nVerificar o código-fonte enviado ↗ arquivado em 2025-02-26 ↗\n\nSiga as provas. Analise a fonte.\n\nVoltar à investigação ↗",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Cronologia de segurança — 2018 para 2026"
          },
          {
            "level": 2,
            "id": null,
            "text": "A cronologia"
          },
          {
            "level": 2,
            "id": null,
            "text": "Avisos sobre mensagens suspeitas nas conversas em grupo"
          },
          {
            "level": 2,
            "id": null,
            "text": "Permissões granulares e lista de IPs autorizados para chaves de editor (anúncio do Valve)"
          },
          {
            "level": 2,
            "id": null,
            "text": "As transações CS2 passam a dispor de um período de reversão de sete dias"
          },
          {
            "level": 2,
            "id": null,
            "text": "Valve publica um aviso de segurança sobre contas devido a fugas de SMS"
          },
          {
            "level": 2,
            "id": null,
            "text": "Sete dias antes da revenda ou da nova comercialização"
          },
          {
            "level": 2,
            "id": null,
            "text": "Restrições relativas a novos dispositivos verificadas nas Páginas de Ajuda"
          },
          {
            "level": 2,
            "id": null,
            "text": "Foi implementado um período de espera para a troca de nome em 2024"
          },
          {
            "level": 2,
            "id": null,
            "text": "A criação da chave requer confirmação através do telemóvel"
          },
          {
            "level": 2,
            "id": null,
            "text": "Entra em vigor a FA obrigatória 2para a definição de versões do jogo em tempo real"
          },
          {
            "level": 2,
            "id": null,
            "text": "Avisos de conteúdo personalizados nas biografias, observados pela comunidade"
          },
          {
            "level": 2,
            "id": null,
            "text": "Os períodos de espera para a filtragem e edição de links de perfil estão ativos"
          },
          {
            "level": 2,
            "id": null,
            "text": "Steam Transição do cliente para os tokens de atualização e de acesso do OAuth"
          },
          {
            "level": 2,
            "id": null,
            "text": "Início de sessão por QR e gestão de dispositivos autorizados"
          },
          {
            "level": 2,
            "id": null,
            "text": "Os pontos finais de cancelamento de transações foram removidos da lista pública API"
          },
          {
            "level": 2,
            "id": null,
            "text": "Os itens do Dota2 passam a ter um período de espera de sete dias para a troca"
          },
          {
            "level": 2,
            "id": null,
            "text": "Os itens do CS:GO trocados ficam sujeitos a um período de espera de sete dias"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/pt/#briefing-heading",
          "https://steamcommunity.com/groups/SteamClientBeta?l=english",
          "http://web.archive.org/web/20260313235409/https://steamcommunity.com/groups/SteamClientBeta?l=english",
          "https://store.steampowered.com/news/posts/?enddate=1788390000",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/493839547938902179",
          "https://partner.steamgames.com/doc/webapi_overview/auth",
          "https://csmarketcap.com/blog/market-insights/from-boom-to-bust-cs2s-trade-protection-impact",
          "https://skinvault.gg/blog/cs2-trade-protection-explained/",
          "https://skin.land/blog/steam-changes-cs2-trade-ban-logic-timing/",
          "https://store.steampowered.com/news/posts/?appids=730&amp;enddate=1753924057&amp;feed=steam_announce%2F1000",
          "https://help.steampowered.com/faqs/view/3041-A87A-E5F6-B6AC",
          "https://store.steampowered.com/news/posts/?enddate=1747349559",
          "https://steamcommunity.com/ogg/593110/announcements/detail/533224478739530146",
          "https://store.steampowered.com/news/posts/?appids=730&amp;enddate=1728000977&amp;feed=steam_community_announcements",
          "https://steamcommunity.com/games/CSGO/announcements/detail/4447966961421256740",
          "https://help.steampowered.com/faqs/view/7F77-9E92-31E0-6B8E",
          "https://steamcommunity.com/sharedfiles/filedetails/?id=2926756889",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "http://web.archive.org/web/20260924181824/https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "https://steamcommunity.com/dev/apikey",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3749866608167579206",
          "http://web.archive.org/web/20251203174259/https://steamcommunity.com/groups/steamworks/announcements/detail/3749866608167579206",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3734103130194459461",
          "https://steamcommunity.com/discussions/forum/1/3807266184852932971/",
          "https://help.steampowered.com/faqs/view/225C-C51E-B8F0-55B2",
          "https://store.steampowered.com/news/group/4/view/3314112260640237775",
          "https://store.steampowered.com/news/posts/?appgroupname=Keep+in+touch&amp;enddate=1666122699&amp;feed=steam_blog",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/issues/325",
          "https://partner.steamgames.com/doc/webapi/IEconService",
          "https://steamcommunity.com/app/570/announcements/",
          "https://blog.dota2.com/2020/05/trading-cooldown/",
          "https://blog.counter-strike.net/2018/03/20309/",
          "https://blog.counter-strike.net/index.php/2018/03/20308/",
          "http://web.archive.org/web/20250226114333/https://blog.counter-strike.net/index.php/2018/03/20308/",
          "https://phishdestroy.io/steam_dossier/pt/#vulnerability-profile"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/pt/security_timeline.content.json",
      "export_json_sha256": "7c61075eab42a61c8fb4d764bb0a1c9f4b1e433eb37136ae28280472c01492ab"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "pt/skin_atlas.html",
      "language": "pt",
      "title": "O atlas do que o «Steam» não pode transportar — O Dossiê «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/pt/skin_atlas",
      "source_html_sha256": "ae92ce99655b2904c8530836c0b0816c14066d764591580127f093ce372d2f7f",
      "exported_at": "2026-09-29T00:18:13.651Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "gallery",
            "source": "https://phishdestroy.io/steam_dossier/pt/skin_atlas#gallery"
          }
        ],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "skin_atlas.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/pt/skin_atlas.pdf?v=print-20260929-v5",
        "sha256": "86f45ad60756afc4ee08507419aff2559e11edd2e35f0a1883305cace42d6d61",
        "bytes": 182896,
        "pages": 14
      },
      "integrity": {
        "signed_object": "skin_atlas.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "skin_atlas.content.json.asc",
        "digest_file": "skin_atlas.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify skin_atlas.content.json.asc skin_atlas.content.json",
          "sha256sum -c skin_atlas.content.json.sha256"
        ]
      },
      "content": {
        "text": "ANEXO IV-B / A TABELA DE PREÇOS / 2026-09-23\nAtlas da Escala de Preços de Skin — O Abismo de Liquidez\n\nAs paragens de Valve no mercado onde o dinheiro começa.\n\nO QUE ESTA SECÇÃO DEMONSTRA\n\nEste atlas visual analisa as categorias de produtos «30,266» em cinco catálogos de marketplaces, medindo a cobertura de mercado acima e abaixo do limiar de listagem da «Valve». Abaixo do limite de $1,800, a Steam hospeda 95.3% de categorias ativas; imediatamente acima desse limite, a cobertura oficial reduz-se para 1.9% (com 0.0% de cobertura em ativos comprovados). Isto demonstra um abrupto e estrutural precipício de liquidez, em que a Valve delega a descoberta de transações de elevado valor a plataformas externas, mantendo ao mesmo tempo o controlo total sobre a custódia dos ativos subjacentes.\n\n← Voltar ao resumo executivo\n\nCada artigo do CS2 com um preço atual em cinco plataformas de vendas foi classificado numa faixa de preços com base no seu preço de venda mais baixo, e cada faixa foi avaliada com base num único critério: qual a percentagem desse volume que ainda é comercializada no próprio Mercado da Comunidade dValve. Abaixo do limite de anúncios dValve, a resposta é 95.3%. Acima disso, a resposta é 1.9%. A queda não é gradual e não ocorre onde a procura diminui — ocorre exatamente de acordo com a regra publicada. Dos 248 As categorias de artigos cujos preços, em dois ou mais mercados, sejam fixados de forma independente acima do limite máximo, 100.0%, não têm qualquer listagem em Steam.\n\nVê o penhasco ↓Abrir a galeria de artigos «419»Método e limites\n30,266categorias de artigos avaliadas\n95.3%de artigos de subcategorias comercializados pela Steam\n1.9%dos artigos acima do limite máximo comercializados pela Steam\n$78.6Mvalor mínimo do conjunto corroborado\n01 / a medição\nA queda acontece por regra, não por exigência\n\nCada uma das categorias de artigos «30,266» abaixo é classificada numa faixa de acordo com o seu mais barato Pesquisa em tempo real nas plataformas BUFF163, CSFloat, Skinport, YouPin 898 e C5Game, sendo que apenas os itens mencionados em duas ou mais dessas plataformas são contabilizados; assim, nenhuma listagem otimista isolada pode inventar um membro da banda. O painel superior mostra a quota de mercado que cada banda ainda detém no próprio mercado da Valve.\n\nPercentagem de cada faixa de preços comercializada pelo Mercado Comunitário «Steam»\nparte superior: cobertura do vapor · parte inferior: itens por faixa, escala logarítmica\n0%\n25%\n50%\n75%\n100%\n100%\n96.9%\n95.9%\n97.3%\n91.1%\n76.8%\n14.5%\n2.9%\n1.5%\n0%\n0%\n0%\n4,632\n1¢–10¢\n7,152\n10¢–$1\n8,568\n$1–10\n5,941\n$10–100\n2,329\n$100–300\n1,292\n$300–1k\n193\n$1k–1.8k\n70\n$1.8k–3k\n67\n$3k–10k\n18\n$10k–30k\n3\n$30k–100k\n1\n$100k+\nitems\nlog\nVALVE’S LISTING CAP\nigual ou inferior ao limite máximo de cotação da «Valve»acima do limite — a regra da «Valve» proíbe a cotaçãocategorias de artigos na banda\n\nPor «cobertura» entende-se que, no momento da captura, existia uma cotação em tempo real Steam para essa categoria. O painel inferior é logarítmico porque o catálogo é na sua grande maioria de produtos baratos: uma leitura linear iria achatar todas as faixas acima de $300, fazendo-as ficar ao nível da linha de base.\n\nO que a forma exclui\n\nSe os artigos caros fossem simplesmente impopulares, a procura diminuiria gradualmente à medida que o preço aumentasse. Mas não é isso que acontece. A procura mantém-se em 76.8% ao longo da faixa de $300–$1k, para depois descer drasticamente para 14.5% na faixa imediatamente abaixo do limite máximo e para 2.9% na faixa imediatamente acima deste. Um efeito da procura não sabe onde Valve estabeleceu o seu limite máximo. Uma regra, sim.\n\nFaixa de preços\tCategorias de artigos\tCom uma pergunta em direto no Steam\tSteam cobertura\tCópias listadas em Steam\n1¢–10¢\t4,632\t4,632\t100%\t8,223,227\n10¢–$1\t7,152\t6,931\t96.9%\t5,488,315\n$1–10\t8,568\t8,213\t95.9%\t3,939,538\n$10–100\t5,941\t5,780\t97.3%\t1,328,255\n$100–300\t2,329\t2,121\t91.1%\t364,466\n$300–1k\t1,292\t992\t76.8%\t187,504\n$1k–1.8k\t193\t28\t14.5%\t40,281\n$1.8k–3k\t70\t2\t2.9%\t9,592\n$3k–10k\t67\t1\t1.5%\t6,706\n$10k–30k\t18\t0\t0%\t1,366\n$30k–100k\t3\t0\t0%\t21\n$100k+\t1\t0\t0%\t2\n\nAs variantes de padrão e de fase estão excluídas desta escala: Steam não apresenta o nível «blue-gem» nem a fase «Ruby» como entradas de mercado distintas, pelo que a sua inclusão subestimaria a cobertura de Steam. Se calculada sem o requisito dos dois mercados, a mesma escala apresenta 79.1% abaixo do limite máximo e 6.5% acima dele, no que diz respeito aos itens 37,204 — uma diferença mais acentuada, baseada em evidências mais fracas, razão pela qual não é o valor citado.\n\n02 / classificação com base em provas\nO preço pedido não é um preço\n\nQualquer pessoa pode colocar um P2000 à venda por cerca de dez milhões de yuan. Antes de qualquer valor apresentado nesta página ser utilizado para qualquer fim, é classificado com base no número de plataformas de comércio eletrónico que, de forma independente, cotam o artigo acima do limite máximo e na proximidade entre os valores médios dessas cotações. Apenas as classificações A e B são referidas — aqui ou em qualquer outra parte deste dossiê.\n\nA  Três ou mais prateleiras coincidem\n\nTrês ou mais plataformas de comércio eletrónico apresentam preços para o artigo acima do limite máximo e a sua mediana situa-se num25%o do preço mais baixo. 197 categorias, 18,218 exemplares, $76,585,587.\n\nAusentes de «Steam»: 100.0%.\n\nB  As duas prateleiras coincidem\n\nDois mercados chegam a acordo acima do limite máximo, ou três chegam a um acordo com uma margem menor. 51 categorias, 176 exemplares, $2,038,814.\n\nAusentes de «Steam»: 100.0%.\n\nC  Uma prateleira — não utilizada\n\nUma única plataforma de negociação apresenta a única oferta acima do limite máximo. 171 categorias, 247 cópias. Apresentado na galeria por uma questão de exaustividade e excluído de todos os totais nesta página.\n\nTrata-se de pedidos de cotação, não de provas de um preço.\n\nQuanto custou esta correção e o que ela trouxe\n\nAo retirar a classificação C, as categorias «171» e «$3,825,125» desaparecem do título. O que resta é mais conciso e muito mais difícil de contestar: 248 categorias, 18,394 exemplares listados, $78,624,401, e 100.0% — todos eles, sem exceção — ausentes do mercado de Valve. As linhas de grau C são a razão pela qual o valor mudou; estão listadas, não ocultas.\n\nRegistos classificados como artefactos\n\nQualquer cotação superior a três vezes o preço de venda mais baixo para o mesmo artigo é descartada. Quando convertidas à taxa implícita nos próprios dados, a maioria apresenta valores redondos em CNY — o que é típico de um valor provisório ou de um limite máximo da plataforma, em vez de uma oferta. Uma vez que todos os totais nesta página utilizam a mais barato É importante referir que nenhuma destas figuras poderia alguma vez ter inflacionado um número; foram excluídas para que nenhuma delas possa ser citada como manchete.\n\nArtigo\tPedido ao vivo mais barato\tReservar\nSouvenir P2000 | Wicked Sick (Minimal Wear)\t$148,954\t$1,489,543\n★ Specialist Gloves | Crimson Kimono (Minimal Wear) | Phase 1\t$37,239\t$119,163\nSouvenir USP-S | Printstream (Factory New)\t$2,000\t$59,582\n★ Bowie Knife | Crimson Web (Factory New)\t$2,957\t$43,030\n★ Karambit | Marble Fade (Factory New) | 1st\t$11,916\t$38,874\nSticker | Ninjas in Pyjamas (Holo) | Katowice 2014\t$5,000\t$31,748\nSouvenir AWP | Dragon Lore (Battle-Scarred)\t$4,225\t$29,157\n★ Karambit | Doppler (Minimal Wear) | Ruby\t$7,122\t$27,273\nTodas as categorias «419», com o objeto a que cada preço se refere\n\nFonte: https://phishdestroy.io/steam_dossier/pt/skin_atlas#gallery\n\n04 / para onde foi, afinal\nAs prateleiras que exibem o que Steam não exibe\n\nAs mesmas listagens, agrupadas por plataforma onde se encontram. Esta é uma contagem dos locais onde se encontram exemplares listado, o que não é o mesmo que o local onde se encontram e não é interpretado aqui como tal.\n\nValor mínimo dos anúncios acima do limite máximo, por plataforma\no preço de venda mais baixo × o número de exemplares expostos naquela prateleira\nYouPin 898\n$22,720,252\nBUFF163\n$22,022,606\nC5Game\n$12,560,543\nCSFloat\n$10,871,845\nSkinport\n$1,385,060\n\nJurisdições, pela ordem acima: YouPin 898 — China · BUFF163 — China · C5Game — China · CSFloat — Estados Unidos · Skinport — Alemanha / Malta. O mesmo artigo físico pode estar listado em mais do que uma destas secções, pelo que estes valores não devem ser somados a qualquer outro total de mercado.\n\nValor mínimo por faixa de preço\ncomo é que o dinheiro é distribuído acima do limite máximo\n$1.8k-3k\n$9,842,391\n$3k-10k\n$36,787,269\n$10k-50k\n$20,038,749\nover $50k\n$2,891,897\n05 / escassez que se pode contar\nQuão escassa é, de facto, a oferta\n\nCada item do CS2 tem um valor de desgaste, e as plataformas de comércio publicam quantas cópias se encontram em cada faixa desse valor. Isso transforma «raro» de um adjetivo num número — e é esse número que explica por que razão uma única conta comprometida justifica o esforço de criar um kit de phishing personalizado.\n\nAWP | Lenda do Dragão\n150 anunciado · a partir de $11,350\n0.00–0.01\n29 · $14,730\n0.01–0.02\n54 · $11,618\n0.02–0.03\n26 · $11,350\n0.03–0.04\n25 · $11,618\n0.04–0.07\n16 · $11,585\n\nAWP | Dragon Lore (Novo de fábrica)\n\nM4A4 | Howl\n105 anunciado · a partir de $6,628\n0.00–0.01\n11 · $10,725\n0.01–0.02\n14 · $8,088\n0.02–0.03\n11 · $7,580\n0.03–0.04\n19 · $6,703\n0.04–0.07\n50 · $6,628\n\nM4A4 | Howl (Novo de fábrica)\n\nAK-47 | Wild Lotus\n113 anunciado · a partir de $14,373\n0.00–0.01\n25 · $22,343\n0.01–0.02\n11 · $19,364\n0.02–0.03\n3 · $19,645\n0.03–0.04\n15 · $15,044\n0.04–0.07\n59 · $14,373\n\nAK-47| Wild Lotus (Novo de fábrica)\n\nAWP | Gungnir\n173 anunciado · a partir de $11,618\n0.00–0.01\n28 · $17,875\n0.01–0.02\n21 · $13,600\n0.02–0.03\n32 · $12,065\n0.03–0.04\n29 · $11,735\n0.04–0.07\n63 · $11,618\n\nAWP | Gungnir (Novo de fábrica)\n\nAK-47 | Serpente de Fogo\n278 em venda · a partir de $663\n0.15–0.18\n87 · $730\n0.18–0.21\n49 · $712\n0.21–0.24\n52 · $703\n0.24–0.27\n18 · $715\n0.27–0.38\n72 · $663\n\nAK-47 | Serpente de Fogo (Testada em campo)\n\nCementado (todos os níveis / gema azul)\n76 anunciado · a partir de $1,638\n0.07–0.08\n1 · $2,516\n0.08–0.09\n4 · $2,482\n0.09–0.10\n6 · $3,856\n0.10–0.11\n7 · $2,797\n0.11–0.15\n58 · $1,638\n\nAK-47 | Cementado (desgaste mínimo) | Nível1\n\nAs faixas correspondem às faixas de flutuação próprias das plataformas de negociação; apenas são consideradas as faixas com, pelo menos, uma cotação em tempo real. O preço indicado ao lado de cada barra corresponde à cotação de venda em tempo real mais baixa nessa faixa, pelo que o prémio associado a uma flutuação reduzida é diretamente visível, em vez de ser declarado.\n\n06 / movimento, medido a partir de Steam\nO que as prateleiras de produtos de terceiros realmente alcançaram\n\nValve não publica dados históricos úteis neste nível, e este dossiê não alega ter quaisquer. O site Skinport publica as suas próprias vendas concluídas nas últimas 24 horas, 7, 30 e 90 dias, e essa é toda a dimensão temporal disponível aqui: um preço mediano realizado por janela temporal, indexado de forma a que a mediana de 90-dia seja 100. Nenhum dado do «Steam» está envolvido em nenhum dos gráficos.\n\nPreço mediano realizado, janela móvel\nindexado à mediana diária do «90-» · 6,758 itens com 20+ vendas\n85\n91\n97\n103\n100\n90d\n94\n30d\n90\n7d\n88\n24h\nVendas concluídas por dia\nos mesmos artigos, as mesmas montras\n7,621\n9,653\n11,684\n13,716\n12,700\n90d\n11,894\n30d\n9,540\n7d\n8,637\n24h\n\nTrata-se de dois gráficos, e não de um único com duas escalas verticais: um índice e uma contagem diária não partilham a mesma unidade, e representá-los num eixo comum levaria a uma comparação que não é válida. As janelas estão aninhadas e são consecutivas — o valor diário 90-inclui o valor horário 24-— pelo que esta não é uma série diária e não deve ser interpretada como tal. O que isto demonstra é específico e está claramente indicado: ao longo das janelas de tempo Skinport publicadas, o preço mediano realizado situou-se abaixo da sua própria mediana de 90-dias e a contagem diária de vendas diminuiu em consonância.\n\nSkinport vendas realizadas. As janelas são aninhadas e deslizantes, pelo que cada ponto corresponde ao preço mediano realizado ao longo da janela deslizante, indexado à mediana do dia 90-. Não se trata de uma série diária e não envolve dados Steam.\n\n07 / de que é feito\nAutocolantes com dezasseis anos e um punhado de luvas\n\nO segmento acima do limite máximo não representa uma parte significativa do mercado. Concentra-se em algumas peças raras e em algumas coleções, várias das quais já não podem ser obtidas de forma alguma — e é precisamente por isso que a oferta não consegue responder ao preço.\n\nCategorias acima do limite, por raridade\nnúmero de categorias de artigos\nCovert\n321\nClassified\n39\nRestricted\n24\nContraband\n12\nMil-Spec Grade\n9\nConsumer Grade\n9\nIndustrial Grade\n5\nCategorias acima do limite, por coleção\nas dez melhores coleções\nThe St. Marc Collection\n13\nThe Cobblestone Collection\n13\nThe Norse Collection\n12\nThe Arms Deal Collection\n9\nThe Canals Collection\n7\nThe Gods and Monsters Collection\n6\nThe Revolution Collection\n4\nThe 2021 Train Collection\n4\nThe Rising Sun Collection\n4\nThe Chop Shop Collection\n4\n\nPor categoria: skin 366, sticker 48, container 3, sticker_slab 2.\n\n08 / o valor máximo que alguém pagou de facto\nMáximas sustentadas por uma transação, e não por uma cotação\n\nTodos os outros preços nesta página são um perguntar — o que um vendedor procura. São os seguintes: vendas: o valor mais elevado de uma transação concluída Skinport registado para cada artigo, nos últimos 90 dias. É o único valor neste dossiê que alguém pagou efetivamente, e cada linha inclui um link para a plataforma de vendas, para que o valor possa ser verificado diretamente na fonte, em vez de nos ser atribuído a nós.\n\n21,216artigos cuja venda já foi concluída na montra\n106vendido a um preço igual ou superior ao limite máximo de cotação da «Valve»\n$14,192a venda única mais elevada já concretizada\n67/419categorias acima do limite com alguma venda registada\nAs trinta vendas concluídas de maior valor durante o período\nArtigo\tVenda mais elevada\tPreço mediano de venda\tVendas\tPergunte agora qual é o preço mais baixo\tSteam\tDá uma vista de olhos\nAWP | Gungnir (Factory New)\t$14,192\t$11,343\t5\t$11,490\tabsent\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Factory New)\t$12,387\t$12,387\t1\t$13,836\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Factory New)\t$11,779\t$11,063\t16\t$10,941\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Minimal Wear)\t$11,693\t$11,693\t1\t$9,946\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Minimal Wear)\t$10,437\t$10,437\t1\t$9,610\tabsent\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Blue Laminate (Minimal Wear)\t$9,772\t$37\t76\t$30\t$40\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Minimal Wear)\t$9,463\t$9,463\t1\t$9,500\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Minimal Wear)\t$9,104\t$9,026\t6\t$8,524\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Hedge Maze (Minimal Wear)\t$8,139\t$8,139\t1\t$6,819\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Field-Tested)\t$7,617\t$7,390\t4\t$7,194\tabsent\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Field-Tested)\t$7,615\t$7,615\t1\t$7,100\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Field-Tested)\t$7,149\t$7,006\t2\t$7,165\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Field-Tested)\t$6,711\t$6,194\t15\t$5,988\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Factory New)\t$6,679\t$6,613\t3\t$6,628\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Superconductor (Factory New)\t$6,084\t$6,084\t1\t$7,969\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Battle-Scarred)\t$5,750\t$5,413\t3\t$5,899\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Pandora's Box (Minimal Wear)\t$5,520\t$5,508\t3\t$4,998\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Vice (Factory New)\t$5,385\t$5,158\t2\t$5,700\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Minimal Wear)\t$5,342\t$4,989\t19\t$4,997\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Hedge Maze (Field-Tested)\t$5,334\t$4,862\t5\t$3,724\tabsent\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Vulcan (Factory New)\t$5,275\t$1,418\t12\t$1,280\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Well-Worn)\t$4,978\t$4,978\t1\t$4,942\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Well-Worn)\t$4,931\t$4,931\t1\t$5,445\tabsent\tSkinport CSFloat Steam\nAK-47 | Hydroponic (Factory New)\t$4,802\t$4,351\t2\t$3,648\tabsent\tSkinport CSFloat Steam\n★ Talon Knife | Case Hardened (Minimal Wear)\t$4,588\t$466\t16\t$442\t$630\tSkinport CSFloat Steam\nAWP | Medusa (Factory New)\t$4,484\t$4,484\t1\t$4,171\tabsent\tSkinport CSFloat Steam\n★ Specialist Gloves | Pillow Punchers (Factory New)\t$4,359\t$4,359\t1\t$4,302\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Pandora's Box (Field-Tested)\t$4,359\t$3,666\t11\t$3,245\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Field-Tested)\t$4,289\t$4,225\t8\t$4,022\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Battle-Scarred)\t$4,124\t$4,124\t1\t$4,279\tabsent\tSkinport CSFloat Steam\nO mesmo artigo, o mesmo 90 dias, um preço completamente diferente\n\nLimitado a artigos com uma mediana de $100 e, pelo menos, cinco vendas concluídas, porque, no caso de uma skin barata, uma venda atípica distorce o rácio. O que resta é dominado por Cementado acabamentos, em que o padrão determina o preço e o mercado classifica todos os padrões sob um único nome — o mesmo mecanismo avaliado por float na secção 05.\n\nArtigo\tValor máximo vs. mediana\tVenda mais elevada\tPreço mediano de venda\tVendas\tDá uma vista de olhos\n★ Talon Knife | Case Hardened (Minimal Wear)\t+884%\t$4,588\t$466\t16\tSkinport CSFloat Steam\nDesert Eagle | Cobalt Disruption (Factory New)\t+859%\t$1,210\t$126\t115\tSkinport CSFloat Steam\nAWP | BOOM (Minimal Wear)\t+814%\t$1,232\t$135\t89\tSkinport CSFloat Steam\nAK-47 | Case Hardened (Well-Worn)\t+769%\t$1,720\t$198\t70\tSkinport CSFloat Steam\nAWP | Graphite (Factory New)\t+761%\t$1,469\t$171\t124\tSkinport CSFloat Steam\n★ Talon Knife | Case Hardened (Field-Tested)\t+509%\t$2,437\t$400\t48\tSkinport CSFloat Steam\n★ Kukri Knife | Case Hardened (Minimal Wear)\t+448%\t$723\t$132\t69\tSkinport CSFloat Steam\n★ Kukri Knife | Case Hardened (Field-Tested)\t+415%\t$549\t$106\t128\tSkinport CSFloat Steam\n★ Ursus Knife | Case Hardened (Minimal Wear)\t+371%\t$597\t$127\t12\tSkinport CSFloat Steam\nAK-47 | Case Hardened (Field-Tested)\t+369%\t$1,037\t$221\t125\tSkinport CSFloat Steam\nAK-47 | Red Laminate (Minimal Wear)\t+360%\t$552\t$120\t18\tSkinport CSFloat Steam\nAWP | Asiimov (Field-Tested)\t+351%\t$528\t$117\t439\tSkinport CSFloat Steam\nAK-47 | Vulcan (Field-Tested)\t+337%\t$865\t$198\t241\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Nightwish (Factory New)\t+322%\t$625\t$148\t31\tSkinport CSFloat Steam\nAWP | Lightning Strike (Factory New)\t+319%\t$2,065\t$493\t198\tSkinport CSFloat Steam\nStatTrak™ AWP | Redline (Minimal Wear)\t+312%\t$574\t$139\t24\tSkinport CSFloat Steam\nStatTrak™ AWP | Asiimov (Battle-Scarred)\t+287%\t$524\t$135\t37\tSkinport CSFloat Steam\nAK-47 | Redline (Minimal Wear)\t+277%\t$562\t$149\t112\tSkinport CSFloat Steam\nAWP | Crakow! (Factory New)\t+275%\t$379\t$101\t72\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Vulcan (Factory New)\t+272%\t$5,275\t$1,418\t12\tSkinport CSFloat Steam\n\nTrata-se de um máximo diário de 90-, NÃO de um máximo histórico, e abrange APENAS UM mercado. Em nenhum ponto deste dossiê é referido qualquer valor histórico. Um artigo que não apresente uma venda Skinport na janela está totalmente ausente desta exposição, razão pela qual o conjunto é mais reduzido do que o recenseamento.\n\nOs links de verificação são criados a partir dos próprios identificadores da plataforma do catálogo. Apontam para a página do artigo em cada mercado online, para que o leitor possa comparar a imagem com a fonte original, em vez de com o nosso site. Os links externos contêm rel=\"nofollow\": trata-se de referências, não de recomendações, e vários desses destinos são plataformas de comércio eletrónico que esta investigação critica.\n\n09 / proveniência e limites\nDe onde isto veio e o que não consegue mostrar\n\nTodos os dados apresentados nesta página foram recalculados a partir de dois ficheiros de instantâneos, cujos hashes estão publicados juntamente com os mesmos. Nada do que aqui se encontra foi transcrito de um artigo de outro site.\n\nFonte e acesso\n\ncs2.sh API, GET /v1/prices/latest e GET /v1/schema, instantâneo único, capturado em 2026-09-23T00:44:27.871388581Z, com preços em USD.\n\nOs dados foram obtidos no âmbito de uma subscrição comercial paga detida pelo requerente GDPR, documentada no arquivo, de acordo com os termos do próprio fornecedor. Não foi efetuada a extração de dados de nenhuma plataforma de comércio eletrónico, nem foram utilizadas credenciais de nenhuma dessas plataformas. A chave do requerente é mantida fora deste repositório e não consta em nenhum ficheiro aqui.\n\nComo um artigo se qualifica\n\nCada artigo básico com, pelo menos, uma oferta ativa no BUFF, CSFloat, Skinport, YouPin ou C5Game é colocado numa faixa de preços com base na sua oferta MAIS BARATA, pelo que a faixa nunca depende de Steam. A «Steam coverage» é a percentagem de artigos nessa faixa que apresentam alguma oferta ativa Steam no momento da captura. As variantes de padrão e fase são excluídas da tabela porque Steam não as lista separadamente; incluí-las subestimaria Steam. As imagens de renderização são as imagens de catálogo dos mesmos artigos, armazenadas localmente.\n\nRenderizações e direitos de imagem. As renderizações dos artigos do catálogo são imagens do fornecedor apresentadas para o mesmo «market_hash_name» que as linhas de preço, armazenadas localmente para visualização offline e no IPFS. As imagens não são da autoria dPhishDestroy: todas as imagens de artigos, logótipos e capturas de ecrã permanecem propriedade dos respetivos proprietários (cs2.sh, CSFloat, Skinport, BUFF, YouPin, C5Game, Valve e outros). São reproduzidas exclusivamente para fins de identificação e reportagem de interesse público; não se reivindica qualquer direito de propriedade ou licença.\n\nO que não conseguimos obter\n\nO nível de subscrição utilizado serve apenas para instantâneos atuais. Os pontos finais históricos e de arquivo não estavam disponíveis, e Nenhuma série histórica é referida em qualquer parte desta página Para além das vendas com janela móvel, o «Skinport» é publicado na secção 06.\n\nUm instantâneo, não uma série temporal. A ausência de uma listagem no «Steam» no momento da captura não é prova de que um artigo nunca venha a aparecer lá; trata-se do estado registado da prateleira naquele momento e, no caso de preços acima do limite máximo, é também o que a regra publicada pelo «Valve» exige: o «Community Market» do «Valve» limita explicitamente as listagens a $1,800 por artigo (com um saldo máximo na carteira do «Steam» de $2,000; ver Steam Perguntas frequentes sobre o Mercado Comunitário arquivado em 2026-09-21 ↗ e Steam Contrato de Assinante § 3.C arquivado em 2026-09-24 ↗).\n\nAvaliação\n\nO preço de um artigo é sempre a sua cotação de venda mais barata em tempo real, pelo que um valor atípico elevado nunca pode inflacionar o total. A classificação determina quais as linhas que podem ser cotadas. Qualquer cotação superior a três vezes a cotação de venda mais barata do mesmo artigo é excluída, não sendo considerada um preço em tempo real. Classificação A: três ou mais plataformas continuam a apresentar cotações acima do limite máximo e a sua mediana situa-se dentro de um25% do preço mais baixo. Classificação B: duas plataformas concordam, ou três concordam de forma menos rigorosa. Classificação C: uma única cotação — um preço de venda, não um preço de mercado. Apenas as classificações A e B são apresentadas neste dossiê.\n\nRegra para valores atípicos: cotação > 3.0multiplicada pelo preço de venda mais baixo do mesmo artigo.\n\nPor que razão os totais representam um valor mínimo\n\nPara cada plataforma de vendas, o artigo mais baixo O preço de venda é multiplicado pelo número de exemplares que constam na lista da prateleira. Todos os outros exemplares têm um preço igual ou superior a esse preço de venda mais baixo, pelo que o verdadeiro valor publicado é mais elevado por definição, e não por estimativa. Não se trata de uma venda, nem de um fluxo de caixa, nem de uma avaliação da economia do CS2.\n\nVerifica tu mesmo\n\nOs conjuntos de dados derivados subjacentes a cada gráfico desta página são publicados na íntegra: o conjunto de dados do Atlas, o ecrã de classificação e de deteção de artefactos, o recenseamento subjacente e o manifesto com o SHA-256e de cada instantâneo bruto.\n\nUma correção registada na abertura\n\nUma versão preliminar anterior do registo complementar apresentava como primeiro resultado um AK-47 | Point Disarray, com um preço pedido de $148,954 num mercado chinês, enquanto Steam o cotava a $119. Essa entrada é de grau C: uma única prateleira, um único exemplar e nenhum outro mercado a concordar com o preço. Trata-se de um preço pedido, não de um preço de venda, e foi rebaixado aqui e naquela página. O líder confirmado é o Autocolante | Titan (Holo) | Katowice 2014 a $66,285, citado por 4, estão presentes em 5.2% — e ausentes de Steam por completo.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Atlas da Escala de Preços de Skin — O Abismo de Liquidez"
          },
          {
            "level": 2,
            "id": null,
            "text": "A queda acontece por regra, não por exigência"
          },
          {
            "level": 3,
            "id": null,
            "text": "O que a forma exclui"
          },
          {
            "level": 2,
            "id": null,
            "text": "O preço pedido não é um preço"
          },
          {
            "level": 3,
            "id": null,
            "text": "A  Três ou mais prateleiras coincidem"
          },
          {
            "level": 3,
            "id": null,
            "text": "B  As duas prateleiras coincidem"
          },
          {
            "level": 3,
            "id": null,
            "text": "C  Uma prateleira — não utilizada"
          },
          {
            "level": 3,
            "id": null,
            "text": "Quanto custou esta correção e o que ela trouxe"
          },
          {
            "level": 3,
            "id": null,
            "text": "Registos classificados como artefactos"
          },
          {
            "level": 2,
            "id": null,
            "text": "Todas as categorias «419», com o objeto a que cada preço se refere"
          },
          {
            "level": 2,
            "id": null,
            "text": "As prateleiras que exibem o que Steam não exibe"
          },
          {
            "level": 2,
            "id": null,
            "text": "Quão escassa é, de facto, a oferta"
          },
          {
            "level": 2,
            "id": null,
            "text": "O que as prateleiras de produtos de terceiros realmente alcançaram"
          },
          {
            "level": 2,
            "id": null,
            "text": "Autocolantes com dezasseis anos e um punhado de luvas"
          },
          {
            "level": 2,
            "id": null,
            "text": "Máximas sustentadas por uma transação, e não por uma cotação"
          },
          {
            "level": 3,
            "id": null,
            "text": "As trinta vendas concluídas de maior valor durante o período"
          },
          {
            "level": 3,
            "id": null,
            "text": "O mesmo artigo, o mesmo 90 dias, um preço completamente diferente"
          },
          {
            "level": 2,
            "id": null,
            "text": "De onde isto veio e o que não consegue mostrar"
          },
          {
            "level": 3,
            "id": null,
            "text": "Fonte e acesso"
          },
          {
            "level": 3,
            "id": null,
            "text": "Como um artigo se qualifica"
          },
          {
            "level": 3,
            "id": null,
            "text": "O que não conseguimos obter"
          },
          {
            "level": 3,
            "id": null,
            "text": "Avaliação"
          },
          {
            "level": 3,
            "id": null,
            "text": "Por que razão os totais representam um valor mínimo"
          },
          {
            "level": 3,
            "id": null,
            "text": "Verifica tu mesmo"
          },
          {
            "level": 3,
            "id": null,
            "text": "Uma correção registada na abertura"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/pt/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/pt/skin_atlas#gallery",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://skinport.com/market?search=AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260924114457/https://store.steampowered.com/subscriber_agreement/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-atlas.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-artefact-screen.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-above-the-ceiling.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/pt/skin_atlas.content.json",
      "export_json_sha256": "eb84ad58d8681673db0eac59dd2a731efbfb435e0815121180caeb93788da734"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "pt/social_graph.html",
      "language": "pt",
      "title": "Siga as ligações registadas — O Dossiê «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/pt/social_graph",
      "source_html_sha256": "ba8e602779536ec6a23289e381403e02406b7f7ff2d5d1185019225323368e63",
      "exported_at": "2026-09-29T00:18:13.290Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "social_graph.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/pt/social_graph.pdf?v=print-20260929-v5",
        "sha256": "816eaf339f782974faa004dbcce7fff9378aecba755484d3111094557f6f65aa",
        "bytes": 120941,
        "pages": 6
      },
      "integrity": {
        "signed_object": "social_graph.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "social_graph.content.json.asc",
        "digest_file": "social_graph.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify social_graph.content.json.asc social_graph.content.json",
          "sha256sum -c social_graph.content.json.sha256"
        ]
      },
      "content": {
        "text": "Siga as ligações.Analise cada relação.\n\nPesquise um perfil. Escolha um tipo de relação. Siga os seus vizinhos diretos nos registos capturados. Ferramenta de investigação: As arestas representam relações públicas, não constituindo prova de contacto direto, coordenação privada ou conduta indevida entre quaisquer dois nós. A melhor forma de interpretar um esquema de nós do tipo «3,435-» é através de filtros.\n\nExplora uma relação de cada vez\n\n💡 Clique e arraste os nós para reorganizar o gráfico. Passe o cursor por cima para ver perfis detalhados. Linhas contínuas em azul-petróleo = Amizades, linhas tracejadas em âmbar = Comentários mútuos.\n\nTipo de relaçãoPerfil e vizinhos diretos\n\n3,435 perfis · 4,551 links gravados\n\nProcure e selecione um perfil, ou clique num nó. Apenas os seus vizinhos diretos registados permanecem. Uma aresta regista uma relação; não estabelece uma coordenação privada.\n\nPerfis no conjunto de dados recolhido\n\nTabela completa de fontes: descarregar todas as linhas de «3,435» (CSV). A tabela abaixo apresenta inicialmente as primeiras 25 linhas; a pesquisa e a paginação abrangem o conjunto de dados completo.\n\n1–25 /3,435 linhas\nNome da persona\tSteamID64\tPrivacidade\tEstado\tAfiliações a grupos\tExistências congeladas (USD)\tLocalização\nMahatma Gandhi\t76561198333721623\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tPH\nGalley//갤리🌠🌙\t76561198043416832\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tKP\n$Schlächter\t76561198860277343\tPUBLIC\tClean\tsteambans\t$0.00\tUnknown\n❄r3dsn0w000™❄ [Cristi]🎮\t76561197986767957\tPUBLIC\tClean\tCommunityLegends\t$0.00\tRO\n(2a03) Wolfy\t76561197991671851\tPUBLIC\tCommunity\tsr_public\t$0.00\tUS\nZloy2288\t76561198038578334\tPUBLIC\tClean\tsteambans\t$0.00\tBY\njessy\t76561198039125237\tPUBLIC\tCommunity, VAC (1x)\tCommunityLegends\t$0.00\tJP\nJithraRufure\t76561198071896910\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\n| Níllerdínho |\t76561198003487438\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tDK\nJones is back\t76561198023013026\tPRIVATE\tVAC (1x)\tsteambans\t$0.00\tUnknown\nUNEX | ★✠☠ MoH3st ☠✠\t76561198050763123\tPUBLIC\tClean\tsteambans\t$0.00\tDE\nTrojan\t76561198048457084\tPUBLIC\tClean\tCommunityLegends\t$0.00\tDE\n𝗠𝗮𝘆𝘂 ❤\t76561199377967696\tPUBLIC\tClean\tsr_public\t$0.00\tIS\nbig fucking idiot\t76561198871206397\tPUBLIC\tVAC (1x)\tsteambans\t$0.00\tUnknown\nSOFF Games\t76561198227129276\tPUBLIC\tClean\tcommunitymoderators\t$0.00\tRU\nThijminecraft02\t76561198253895669\tPUBLIC\tClean\tSteamIDcouk SArchive\t$0.00\tNL\nStatic-sama\t76561198289329793\tPUBLIC\tClean\tsteambans\t$0.00\tJP\n𝙸mmortal 𝚂targazer\t76561198142116760\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\nCommander Keen\t76561197987773287\tPUBLIC\tClean\tsteambans\t$0.00\tBE\nS1mX\t76561199648509165\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\nmixwell\t76561199276547472\tPUBLIC\tClean\tsr_public\t$0.00\tJP\nP90_GOD_YyEs™\t76561198285821942\tPUBLIC\tClean\tsteambans\t$0.00\tHK\nhewwo?\t76561199133807546\tPUBLIC\tVAC (1x)\tsteambans\t$0.00\tCH\n♕Kamikaze Atze♕\t76561198002700103\tPUBLIC\tClean\tsteambans\t$0.00\tDE\nPastica\t76561198154655970\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tDZ\nRelações de amizade registadas\n\nTabela completa de fontes: descarregar todas as linhas de «4,299» (CSV). A tabela abaixo apresenta inicialmente as primeiras 25 linhas; a pesquisa e a paginação abrangem o conjunto de dados completo.\n\n1–25 /4,299 linhas\nUtilizador A\tDireção\tUtilizador B\tTipo de relação\nMahatma Gandhi\n76561198333721623\t↔\tDeskjet\n76561198272738437\tMutual Friends\nGalley//갤리🌠🌙\n76561198043416832\t↔\tomega\n76561197960274529\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tFisty\n76561198057301486\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tFaalagorn\n76561198001116101\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tMURK\n76561198036995672\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tÅρøᴛʜℯᴛȋᴄÅʟȋℯη ♛👽♛\n76561197984615267\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tsilatrak\n76561197999629462\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tBlack Blade\n76561198083368493\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tAvenger\n76561197978249317\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tRemtar\n76561198124322650\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tCato\n76561197961345984\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t✪ G λ M Ξ ®\n76561197994308495\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tclees42\n76561198030936806\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t𝓜ε𝔰𝔥 | AusLevels\n76561198108828539\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tSgtFopper™\n76561198002555892\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t❥Miss Bee\n76561198046958996\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tTesTy\n76561198032370068\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tskl_andrey\n76561198136881436\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t\"Exekutor\"\n76561198009583947\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tAraripe\n76561198103754372\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tsteve6678\n76561198053200093\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\ttrinner\n76561197970359081\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tSteph S.\n76561198025653291\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tKirito\n76561198154545657\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tDoc. todt\n76561197984492467\tMutual Friends\nLinks para comentários gravados\n\nTabela completa de fontes: descarregar todas as linhas de 252 (CSV). A tabela abaixo apresenta inicialmente as primeiras 25 linhas; a pesquisa e a paginação abrangem o conjunto de dados completo.\n\n1–25 /252 linhas\nAutor\tDireção\tPerfil-alvo\tData\tTexto do comentário\nDeskjet\n76561198272738437\t→\tMahatma Gandhi\n76561198333721623\t16 September, 2021 @ 11:02:05 pm PDT\t\"𝑵𝒐𝒘 𝒊𝒇 𝑰 𝒇𝒖𝒄𝒌 𝒕𝒉𝒊𝒔 𝒎𝒐𝒅𝒆𝒍𝑨𝒏𝒅 𝒔𝒉𝒆 𝒋𝒖𝒔𝒕 𝒃𝒍𝒆𝒂𝒄𝒉𝒆𝒅 𝒉𝒆𝒓 𝒂𝒔𝒔𝒉𝒐𝒍𝒆𝑨𝒏𝒅 𝑰 𝒈𝒆𝒕 𝒃𝒍𝒆𝒂𝒄𝒉 𝒐𝒏 𝒎𝒚 𝑻-𝒔𝒉𝒊𝒓𝒕𝑰'𝒎𝒎𝒂 𝒇𝒆𝒆𝒍 𝒍𝒊𝒌𝒆 𝒂𝒏 𝒂𝒔𝒔𝒉𝒐𝒍𝒆\" - Nelson Mandela\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t22 November, 2021 @ 4:10:28 pm PDT\thttps://anige.horigiri.net/?cat=22\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t18 November, 2021 @ 12:45:26 am PDT\thttps://gamerch.com/umamusume/entry/250411\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t8 August, 2021 @ 4:13:25 am PDT\thttps://modoocode.com/304\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t6 February, 2021 @ 3:35:05 pm PDT\t▤ ∫︹- -ω⁾ ⁽︹▓▓︺\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t11 December, 2019 @ 1:50:53 am PDT\thttps://blog.naver.com/aksenwlddj12/221369410039\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t2 October, 2019 @ 7:11:59 am PDT\tǤαllєу║︎갤리..۩\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t9 April, 2019 @ 12:51:28 pm PDT\tExplosiveDamage(owner, from, maxrange, minrange, distmultiplier, dmgmultiplier, mindamage, typ, damagetype, ignore)\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 12:22:47 pm PDT\tinfo - sh_titles.lua\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 12:21:46 pm PDT\tlocal nibbas = 1344 init.lua\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 11:31:58 am PDT\thttp://foreign.aladin.co.kr/shop/wproduct.aspx?ItemId=123955531&start=slayer\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t3 April, 2019 @ 1:26:41 am PDT\tǤαllєу\nLei\n76561198982197954\t→\tJithraRufure\n76561198071896910\t29 December, 2024 @ 12:58:08 pm PDT\t+rep he knows how 2 rush B ￣ヘ￣\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t2 September, 2026 @ 5:16:55 am PDT\tlol\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t20 August, 2026 @ 6:11:03 am PDT\t?\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t25 July, 2026 @ 7:20:05 am PDT\thahahahaha\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t30 June, 2026 @ 12:52:42 pm PDT\twow\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t30 June, 2026 @ 12:41:32 pm PDT\txD\nvalorant enjoyer\n76561199112142402\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:26:30 pm PDT\toh no!!\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:26:11 pm PDT\toh no!!\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:22:22 pm PDT\tomg !!! they know my secret, omg!!!\nvalorant enjoyer\n76561199112142402\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:21:39 pm PDT\t+rep good ♥♥♥♥♥ player\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:20:50 pm PDT\tomg! u cant cheat on secure gaben servers, omg dont report me, they ban me for boosted omg\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 8:37:11 pm PDT\txD\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t28 June, 2026 @ 1:58:14 pm PDT\twow",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Siga as ligações.Analise cada relação."
          },
          {
            "level": 2,
            "id": null,
            "text": "Explora uma relação de cada vez"
          },
          {
            "level": 2,
            "id": null,
            "text": "Perfis no conjunto de dados recolhido"
          },
          {
            "level": 2,
            "id": null,
            "text": "Relações de amizade registadas"
          },
          {
            "level": 2,
            "id": null,
            "text": "Links para comentários gravados"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-profiles.csv",
          "https://steamcommunity.com/profiles/76561198333721623",
          "https://steamcommunity.com/profiles/76561198043416832",
          "https://steamcommunity.com/profiles/76561198860277343",
          "https://steamcommunity.com/profiles/76561197986767957",
          "https://steamcommunity.com/profiles/76561197991671851",
          "https://steamcommunity.com/profiles/76561198038578334",
          "https://steamcommunity.com/profiles/76561198039125237",
          "https://steamcommunity.com/profiles/76561198071896910",
          "https://steamcommunity.com/profiles/76561198003487438",
          "https://steamcommunity.com/profiles/76561198023013026",
          "https://steamcommunity.com/profiles/76561198050763123",
          "https://steamcommunity.com/profiles/76561198048457084",
          "https://steamcommunity.com/profiles/76561199377967696",
          "https://steamcommunity.com/profiles/76561198871206397",
          "https://steamcommunity.com/profiles/76561198227129276",
          "https://steamcommunity.com/profiles/76561198253895669",
          "https://steamcommunity.com/profiles/76561198289329793",
          "https://steamcommunity.com/profiles/76561198142116760",
          "https://steamcommunity.com/profiles/76561197987773287",
          "https://steamcommunity.com/profiles/76561199648509165",
          "https://steamcommunity.com/profiles/76561199276547472",
          "https://steamcommunity.com/profiles/76561198285821942",
          "https://steamcommunity.com/profiles/76561199133807546",
          "https://steamcommunity.com/profiles/76561198002700103",
          "https://steamcommunity.com/profiles/76561198154655970",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-connections.csv",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-comments.csv"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/pt/social_graph.content.json",
      "export_json_sha256": "95a8260d1c21e86ad22a0f74bdc458de00f0efa6c1a9014c04ca7cc173a51aae"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "pt/steam_enforcement_evidence.html",
      "language": "pt",
      "title": "Regras versus respostas — O Dossiê «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/pt/steam_enforcement_evidence",
      "source_html_sha256": "b21ef2e842304633b045db5d713c53c03ce289cda90247a422f62af152ca9ba8",
      "exported_at": "2026-09-29T00:18:14.172Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "steam_enforcement_evidence.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/pt/steam_enforcement_evidence.pdf?v=print-20260929-v5",
        "sha256": "53c45593e1f64de8547d553c5557eb2281bb463302469b6011b74b67e93bc756",
        "bytes": 379353,
        "pages": 36
      },
      "integrity": {
        "signed_object": "steam_enforcement_evidence.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "steam_enforcement_evidence.content.json.asc",
        "digest_file": "steam_enforcement_evidence.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify steam_enforcement_evidence.content.json.asc steam_enforcement_evidence.content.json",
          "sha256sum -c steam_enforcement_evidence.content.json.sha256"
        ]
      },
      "content": {
        "text": "Suplemento de provas / registos associados à fonte\nSteam Provas de cumprimento — Registos de apoio e rede de programadores\n\nA regra. A resposta.\n\nO QUE ESTA SECÇÃO DEMONSTRA\n\nEsta sala de provas compara o Acordo de Subscrição oficial dValve com registos de aplicação de medidas datados, resoluções de litígios de apoio ao utilizador e registos da rede de programadores nos repositórios 252 e nos perfis 3,320. Demonstra que os titulares de contas comuns enfrentam medidas de aplicação de regras irrefutáveis e o encerramento de casos de apoio ao utilizador na sequência de violações de sessões, enquanto as operações comerciais de bots de grande volume funcionam continuamente com acesso à infraestrutura pública.\n\n← Voltar ao resumo executivo\n\nLeia a restrição por escrito. Abra a resposta registada. Compare o que a fonte apresenta com o que continua por responder.\n\nApoio e recursos ↓Infraestruturas públicas ↓\n252registos do repositório\n3,320perfis públicos\n4,214pares distintos de perfis e repositórios\n98,902pares de perfis com repositórios partilhados\n01 / Apoio, sanções e reabilitação\nLeia a queixa.Anexe o código-fonte.\nGaleria de Recusas de Apoio (Exposições da 981) ↗Descarregar registos selecionados ↓\nHFB / O CASO DA EXTERNALIZAÇÃOO compromisso reconhecido.\nOs despedimentos comunicados.\n\nConsulte a resposta do serviço de apoio aqui reproduzida e a fonte da alegação relativa ao pessoal da empresa contratada.\n\nAbrir o caso e as suas fontes →\n\nAbaixo: cinco preservados publicações públicas no Reddit da coleção de registos de apoio fornecida. Cada registo documenta uma interação comunicada com o sistema de apoio dValve — conservada com o link da fonte original, a posição da captura e o texto completo. Trata-se de relatos das vítimas. Os registos de apoio autenticados que os confirmariam ou contradiriam estão na posse de Valve e não foram divulgados.\n\n01\nBan & review2024-12-09\nPermanent sanction & closed appeals\n\nThe author reports a permanent account ban, repeated ticket closures and a planned GDPR access request.\n\nREDDIT / PUBLIC TESTIMONYr/ohnePixelCapture record 294\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 303 words\nPermanently banned Steam account without a clear explanation, need help!\n\nsteam_support_tickets_MEGA.json / record 294\n\nHey everyone,\n\nI’m in a really frustrating situation, and I’m hoping someone here can help me or offer advice. My Steam account was just permanently banned for allegedly violating the Steam Subscriber Agreement, and I have no idea why.\n\n# What Steam Support told me:\n\nThe support message said my account was banned due to:\n\n* Suspicious activities related to transferring or attempting to sell/trade the account.\n* Community reports and other unspecified factors.\n\nThey added that the ban is permanent and that they can't help me further. They also warned that future support requests regarding this ban might be ignored. 😞\n\n# Why I’m contesting this ban:\n\n* I have never sold, traded, or transferred my account. I’ve been the legitimate owner since the beginning.\n* On the day the ban occurred, I did nothing noteworthy that could have triggered such a sanction.\n* I received no prior warning, which feels incredibly unfair.\n\n# What I’ve tried so far:\n\n* Contacting Steam Support: I explained my situation and asked for more details, but they’re sticking to their decision and closing my tickets.\n* I’m preparing a request based on my Right of Access (GDPR) to get all the data related to my account.\n\n# Questions for the community:\n\n1. Has anyone successfully had a permanent ban lifted on Steam?\n2. Are there steps I can take to prove I’m the legitimate owner of the account?\n3. Any advice on how to word my request to convince support to reconsider my case?\n4. Would it be helpful to contact the CNIL (I’m based in France) to force Steam to provide more information?\n\nI’m really desperate at the thought of losing all my games, purchases, and years of playtime. Thanks in advance for any help and advice you can give!\n\nhttps://preview.redd.it/jk9qv0gmhv5e1.png?width=1289&amp;format=png&amp;auto=webp&amp;s=b3a333ebb08ea133e2c8747ba126f5a68283d9f7\n\nhttps://preview.redd.it/4sopt0gmhv5e1.png?width=1022&amp;format=png&amp;auto=webp&amp;s=56195d5336118faf9413f1514ead7e8d24c788c3\n\nhttps://preview.redd.it/eqrxw0gmhv5e1.png?width=996&amp;format=png&amp;auto=webp&amp;s=ff3539d28ab754e513ad471822c5de652920101d\n\nhttps://preview.redd.it/728xz0gmhv5e1.png?width=1034&amp;format=png&amp;auto=webp&amp;s=bc5335673509929669af785aa244bf8d2dc58da8\n\n02\nSupport access2025-05-09\nAccount recovery & a reported $10,000 loss\n\nThe author alleges that support reset credentials and removed account protection following another person’s recovery ticket.\n\nREDDIT / PUBLIC TESTIMONYr/legaladviceCapture record 110\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 193 words\nGot $10k stollen from steam inventory due to steam' support fault.\n\nsteam_support_tickets_MEGA.json / record 110\n\nLocation: Quebec, Canada.\n\nLast year, someone hacked my Steam account and stole items worth about $10,000 USD. I only noticed this last week. When I talked to Steam Support, they admitted that someone submitted a ticket to make changes on the account and Steam Support reset my password and turned off all my account security.\n\nI asked Steam Support about getting my items back, but they said there was nothing they could do. They told me I should follow their security recommendations.\n\nThe problem is, I did everything they \"suggested\" to protect an account:\n\n* I had two-factor authentication.\n* My phone number was connected to my account.\n* I used Steam Guard.\n* I printed recovery codes and kept them in a safe.\n\nEven though I did all these things, Steam Support still gave someone else access to my account. The stolen items had been in my account since around 2016-2017. Also, I had not logged in for a few years, so I didn’t accidentally give my information to a fake website.\n\nIs there anything I can do, or do I just have to accept losing $10,000 USD?\n\nThanks for your help.\n03\nRestoration2022-07-07\nA reported $500+ loss & template replies\n\nThe author describes an account compromise, disputed transactions and a support response that allegedly did not address the submitted evidence.\n\nREDDIT / PUBLIC TESTIMONYr/DotA2Capture record 45\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 410 words\nFunds stolen through steam market. Disappointed with Steam response.(or lackthereof)\n\nsteam_support_tickets_MEGA.json / record 45\n\nOn 6th July 2022, 44 unauthorized transactions were made on the steam market using my steam wallet funds totalling roughly $500+ USD to buy worthless 1 cent Dota 2 items. This happened during the wee hours in the morning and i contacted them first thing when i woke up. \n\nI have 2FA enabled all the time, and always thought this would not happen to me as I do not go on betting sites/click sketchy links. My account password + emails were not changed, nor did they take my inventory, just that my funds were used illicitly. Also when I went to disable other APIs, it says there are no other APIs to disable. Shows that it wasn't through me clicking sketchy links and leaving my account details there. Would have lost the whole account if i did so.\n\nWhat baffles me is how did they bypass my 2FA to login my account? Why doesn't steam market purchases go through 2FA as well? First time in 9 years that this happened to me. My acc was logged in 'BY' 'Vitebsk' during the illicit purchases but I'm based in Asia I gathered all the screenshots and provided in the ticket to steam support. \n\nAll i got was the standard copy paste template reply by Steam Support. Lost $500+ and was not even worthy of having a proper person to look into this. I dont think they even read or take a look at the screenshots cause if they did, they would have come to the realization that what happened was clearly fraud, and with a few clicks, reverse the unauthorized transactions, refund my wallet and ban the hijacker. \n\nOver the years, i've spent quite a fair bit on steam but really, this is the kind of recourse we get when our account is compromised? They just don’t care, sigh. I only expect the bare minimum from Steam and looks like even that is quite far-fetched.\n\nSS: https://imgur.com/a/67frcls \n\nHijacker: https://steamcommunity.com/profiles/76561199141246495\n\nSteam Response: https://imgur.com/a/V6v4maM\n\nI could think of a few ways on how to Improve:\n\n1) Add 2FA to market transactions. (even if its bulk posting or selling of items, just 1 2FA notif is required)\n\n2) Enable accounts to be region locked. (if you are migrating, then have to go through steam support etc)\n\n3) Additional Lock on Steam Wallet. (Another password perhaps?)\n\nEDIT: 2nd ticket in and I have still yet to receive a non robotic copy paste template response from Steam.\n04\nRestoration2021-11-29\nSteam Guard & an item-restoration refusal\n\nA preserved post includes the author’s account of item theft and a support response declining restoration.\n\nREDDIT / PUBLIC TESTIMONYr/DotA2Capture record 58\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 563 words\nMany people are losing item via clicking links where steam guard is enabled and steam support doesn't not restore items.\n\nsteam_support_tickets_MEGA.json / record 58\n\nAccounts are getting compromised and might be their pc as well where Steam market is targeted hence the malicious links . I am assuming these hackers are getting encouraged where steam support is not doing nothing and they are getting away with hacking items.  \nLiterally the guy who is supporting the game which he doesn't get any in game advantage just  cosmetics in game only for the sole purpose of supporting the game so that the game will prosper and become beautiful way  to enjoy weekend. But right now players are getting hacked left right and center and steam support  is copy pasting message where in short they are blaming the guy who clicked link. 1st this is happening because they are not targeting players but they are targeting market since they are selling those stuff for real cash via party website. Steam is a huge company and can eradicate the problem or at least can remove links temporarily  in chat since hackers are targeting .They made us install steam guard by saying we wont help if there is no steam guard now steam guard is not enough to save our inventory now they changed their policy  that they should not click any suspicious links. How would we know if the link is suspicious ? After clicking and getting our inventory stolen right !   \n\"we'd have to duplicate an item to restore it. Duplication lowers the value of all items by reducing their scarcity and inflating the economy, which affects everyone involved in trading and the Market. To maintain the value of everyone’s inventory, we do not restore items. For more information, please see the Steam Item Restoration Policy.\"  \nThey care for millions of people IN STEAM MARKET where as few  are losing items which is going to affect market where the rightful owner bought the items and hacker is going to sell the item via 3rd party website and enjoy ! HOW IRONIC !!  \nThis is the message from support where my frnd got his items stolen via clicking on link  \n   \nHi there,  \n\nThank you for the information and screenshots provided.  \n\nIt appears that the account was compromised, please take the following steps to secure your account and computer:  \n\nScan your computer for viruses, key loggers, spyware, and other malicious code using antivirus software with updated virus definitions.  \nChange the password for the email address that is associated with your Steam account.  \nRegularly reset your Steam account password.  \n\nPlease see our Security Recommendations article.  \n\nIn addition, I’m sorry to hear that your items were removed without your permission. Unfortunately, Steam Support does not restore scammed, lost, or stolen items for any reason.  \n\nSince Steam Support does not remove items from accounts, we'd have to duplicate an item to restore it. Duplication lowers the value of all items by reducing their scarcity and inflating the economy, which affects everyone involved in trading and the Market. To maintain the value of everyone’s inventory, we do not restore items. For more information, please see the Steam Item Restoration Policy.  \n\nTo make sure that a scammer is reported, please report them through the Steam Community. Reporting a scammer through the Steam Community is the best way to prevent them from committing future scams.  \n\nTo learn how to avoid scams or hijackings, please see our Trade Scam article.  \n\nIf you still need assistance, please let us know.\n05\nEnforcement2025-05-11\nSelective enforcement & an unexplained ban\n\nA community member describes a disputed ban and contrasts it with the visibility of commercial gambling promotion.\n\nREDDIT / PUBLIC TESTIMONYr/SteamUncensoredCapture record 107\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 1,208 words\n🚨 Steam Bans Without Reason and Ignores Its Community — What’s Going On?\n\nsteam_support_tickets_MEGA.json / record 107\n\nHey r/Steam,\n\nI’m writing this to share my thoughts and concerns about my friend [moneylead](https://steamcommunity.com/id/moneylead/) and Steam’s policies in general. I spoke with him yesterday about his situation, though I didn’t discuss writing this post with him—I asked last night, but he hasn’t responded yet. I want to highlight that this issue is broader than just his case, and while Steam might make changes in the future (though that’s unlikely), I feel the community needs to understand how far Steam has strayed from its original values. I’m not trying to put moneylead in a tough spot with this thread—all the info I’m sharing is public, nothing secretive. I hope he won’t be upset with me, but the community needs this case to see the bigger picture and how Steam feels completely unaccountable.\n\n**Why Does Steam Ignore Its Community?**  \nWhy does a platform like **Roblox** provide a detailed log of ban reasons, while Steam, which claims to be \"community-driven,\" ignores its community, bans whoever they want, for whatever they want, with no transparency? I looked into Roblox as a popular game—not a direct competitor to Steam—to see how their bans look, and you can check it out yourself: [Roblox Ban Reasons](https://www.google.com/search?q=Roblox+ban). Their bans are clear, detailed, and actually explain what you did wrong. I think most decent gaming communities operate like this—not with support agents named Olga, hired through outsourcing, who only know how to send canned auto-replies. Take cases like St4ck—or my friend **moneylead**. All these unbans, like **St4ck’s** or **Alexanddd’s**, happened behind closed doors with zero comments from Steam. Of course, it’s convenient for Steam to handle everything in secret, so no one knows or sees what’s going on—but this violates Steam’s own community rules and principles.\n\n**Who Is moneylead?**  \nI’ve known [moneylead ](https://steamcommunity.com/id/moneylead/)since around 2021. We played Dota 2 a couple of times, and then I just stayed on his friends list. He’s always been a legit player, bringing revenue to Steam through purchases. He never sold his skins, whether in **Dota or CS2—he wasn’t a trader**. All he did was:\n\n* Buy games and skins.\n* Collect badges to level up his profile.\n\nAccording to [SteamSets](https://steamsets.com/account/76561199080934614), he’s given out 324,000 Steam Points—I think he awarded profile rewards to all his friends in the list (though I’m not 100% sure). I do know he ran contests and gave gifts to friends, always supporting the community.\n\n**Steam’s Unfair Treatment**  \nI’ve seen Steam remove his showcases, avatar, description, and even his country multiple times—just because he’s from **Ukraine**. He has a ton of haters leaving toxic comments on his wall, and Steam seems to favor **Russian** users. Every time he tried to appeal the removal of his showcases or profile description—which didn’t break any rules, just had his Instagram link, and his avatar is the same as it is now—Steam moderators didn’t care. **They don’t care about top players who bring them massive revenue, nor about regular users.**\n\n>*Here’s the worst part: moneylead works in cybersecurity, specifically fighting account theft and phishing. He’s neutralized over 5,000 threats targeting Steam alone. And yet, Steam bans him for \"account hijacking\"?*\n\nIf you roughly calculate moneylead’s contribution to Steam and the community—his profile, level, badges (not skins, you can’t sell those)—is this normal, Steam? Banning people, closing tickets, and ignoring users with a spotless reputation who aren’t involved in any commercial activity, just bringing you profit without taking anything in return?\n\n**Steam’s Double Standards**  \nI’m honestly shocked:\n\n* YouTubers who promote casinos and skin gambling? Steam’s fine with that.\n* A cybersecurity expert who fights scams, doesn’t promote casinos, and openly talks about it on his profile? **Banned with no explanation, ignored, and denied an unban.**\n\nI wonder if Steam deliberately bans a high-level account once a year just because of their impunity—maybe for hype or something. Otherwise, this is just madness. It’s scary to think how many regular players have lost their accounts and skins—not because of scammers, but because of Steam’s desire to ignore, send auto-replies, and do whatever they want.\n\n**How Many Others Are Affected?**  \nHow many others are out there—maybe not as well-known—who just have a few games or skins, get banned for nothing, and receive zero explanation or response? **Is this even legal?** Every other platform provides a detailed log with specific violations, but Steam slaps on the same vague label and sends templated responses.\n\n* How safe is it to buy skins on Steam?\n* What’s the chance Steam will just ban your account for no reason, with no explanation?\n\n**A Message to Valve**  \nI wish moneylead the best in resolving this, but Valve, it’d be great if you remembered what \"community\" means and started following the law. Because right now, it looks like your 30% commission, impunity, and sense of being above the law in the U.S. have given you the idea that you can do whatever you want.\n\nI’m sure there are many others like moneylead and St4ck—people who aren’t public or don’t have the resources to fight back. Let’s unite these cases. **If you’re a U.S. resident who’s been banned by Steam without reason and wants to challenge it, please reach out to me.** I’m finishing my **Juris Doctor (J.D.) program at SMU Dedman School of Law** in Dallas, Texas, and I’m participating in a legal clinical practice under Rule 13 of the Texas Supreme Court.\n\nWhat Steam is doing is absolutely disgusting and illegal, and **I’d be happy to help any gamer (legitimate, with no real violations) who has games or skins with value. This will be beneficial for my practice, and it’s time to put Steam in its place and show them they can’t just dictate their own rules with arbitration**. Let’s take it all the way—not for punishment, but for the sake of the community. Maybe if Steam loses a case, they’ll change their policies and start explaining their actions like most popular gaming communities do. Many of us remember how Steam Support used to recover stolen accounts and ended up “stealing” skins themselves—banning without real reasons is basically the same thing, and that’s a serious accusation.\n\nSo, r/Steam, see you soon. I think you understand what you’re doing and how many people you’ve illegally deprived of their assets. I want to raise this issue—not just for the U.S., but for the entire world. You’ve banned class-action lawsuits? **Welcome to Texas.** I recommend starting to look for licensed attorneys in Texas, because I’d love to discuss your company’s policies, feedback, and support agents named Olga—a name that strongly associates with Russian users. Maybe it’d be easier to move your company to Moscow? But I’d be happy to discuss these critical issues on behalf of the global gaming community.\n\nAlso, I wouldn’t recommend ignoring the lawsuit request that will be sent to your physical address and email address, as the court will proceed without you, and that might upset you—especially since things aren’t going so well for a company with stocks like yours.\n\n**Thanks to everyone who took the time to read this. For those who need real help with an unjust Steam ban without any explanation, I’d be happy to assist. For users from Texas, we can easily file a collective lawsuit against Steam—let’s connect and make it happen.**\n02 / Rede de Desenvolvimento «Steam»\nInfraestruturas públicas.Gravado em grande escala.\nDescarregar todos os registos de «252» ↓\n\nO fornecido output_steam_network O «snapshot» regista repositórios, relações públicas entre colaboradores e bifurcações, bem como sobreposições de perfis. Trata-se de registos publicados — o que foi criado, quem contribuiu, o que foi bifurcado. É este registo documental das capacidades públicas que o «Valve» deve ter em conta.\n\nRepositório / descrição\tColaboradores\tForkers\tPerfis registados\nalliedmodders/amxmodx\n\nAMX Mod X - Half-Life 1 Scripting and Administration\n\n\t40\t40\t80\nalliedmodders/sourcemod\n\nSourceMod - Source Engine Scripting and Administration\n\n\t40\t40\t80\nDoctorMcKay/node-steam-user\n\nAllows interaction with the Steam network via the Steam client protocol\n\n\t40\t40\t80\nFacepunch/Facepunch.Steamworks\n\nAnother fucking c# Steamworks implementation\n\n\t40\t40\t80\nJustArchiNET/ArchiSteamFarm\n\nC# application with primary purpose of farming Steam cards from multiple accounts simultaneously.\n\n\t40\t40\t80\nodota/core\n\nOpenDota: Open source Dota 2 data platform with automated replay parsing\n\n\t40\t40\t80\nodota/dotaconstants\n\ndotaconstants: Static data for Dota applications\n\n\t40\t40\t80\nodota/web\n\nOpenDota: React web UI for Dota 2 statistics using the OpenDota platform\n\n\t40\t40\t80\nsplewis/get5\n\nCS:GO Sourcemod plugin for competitive matches/scrims\n\n\t40\t40\t80\nSteamDatabase/FileDetectionRuleSets\n\n🔎 Rules to detect game engines and other technologies based on Steam depot file lists\n\n\t40\t40\t80\nSteamRE/SteamKit\n\nSteamKit2 is a .NET library designed to interoperate with Valve's Steam network. It aims to provide a simple, yet extensible, interface to perform various actions on the network.\n\n\t40\t40\t80\nValveSoftware/dxvk\n\ndxvk tree containing branches used by Proton\n\n\t40\t40\t80\nValveSoftware/GameNetworkingSockets\n\nReliable & unreliable messages over UDP. Robust message fragmentation & reassembly. P2P networking / NAT traversal. Encryption.\n\n\t40\t40\t80\nValveSoftware/gamescope\n\nSteamOS session compositing window manager\n\n\t40\t40\t80\nValveSoftware/Proton\n\nCompatibility tool for Steam Play based on Wine and additional components\n\n\t40\t40\t80\nValveSoftware/source-sdk-2013\n\nThe 2013 edition of the Source SDK\n\n\t40\t40\t80\nValveSoftware/wine\n\nWine with a bit of extra spice\n\n\t40\t40\t80\nValveSoftware/steam-devices\n\nList of devices Steam and SteamVR will want read/write permissions on, to help downstream distributions create udev rules/etc\n\n\t39\t40\t79\nValveSoftware/steam-audio\n\nSteam Audio\n\n\t38\t40\t78\nalliedmodders/metamod-source\n\nMetamod:Source - C++ Plugin Environment and Detour Library for the Source Engine\n\n\t37\t40\t77\nalliedmodders/sourcepawn\n\nA small, statically typed scripting language.\n\n\t35\t40\t75\nValveSoftware/Fossilize\n\nA serialization format for various persistent Vulkan object types.\n\n\t31\t40\t71\nrlabrecque/Steamworks.NET\n\nSteamworks wrapper for Unity / C#\n\n\t27\t40\t67\nModDota/moddota.github.io\n\nModDota github pages project.\n\n\t26\t40\t66\nodota/parser\n\nReplay parse server generating JSON log events from Dota 2 replay files\n\n\t26\t40\t66\nValveSoftware/steam-for-linux\n\nIssue tracking for the Steam for Linux beta client\n\n\t26\t40\t66\nSteamRE/DepotDownloader\n\nSteam depot downloader utilizing the SteamKit2 library.\n\n\t24\t40\t64\nJustArchiNET/ASF-ui\n\nThe official web interface for ASF\n\n\t23\t40\t63\nadvancedfx/advancedfx\n\nHalf-Life Advanced Effects (HLAE) is a tool to enrich content creation mainly for the Counter-Strike series.\n\n\t22\t40\t62\nalliedmodders/ambuild\n\nAlliedModders C++ Build System\n\n\t23\t39\t62\nSteamDatabase/BrowserExtension\n\n💻 SteamDB's extension for Steam websites\n\n\t21\t40\t61\nodota/mobile\n\nReact Native apps for viewing Dota 2 data on Android/iOS\n\n\t19\t40\t59\nValvePython/steam\n\n☁️ Python package for interacting with Steam\n\n\t18\t40\t58\nskadistats/clarity\n\nComically fast Dota 2, CSGO, CS2 and Deadlock replay parser written in Java.\n\n\t13\t40\t53\nSteamRE/open-steamworks\n\nOpen Steamworks is a set of reverse engineered headers for the Valve's Steam Client. More or less abandoned now that the Steamworks SDK is publically available.\n\n\t13\t40\t53\nValveSoftware/Source-1-Games\n\nSource 1 based games such as TF2 and Counter-Strike: Source\n\n\t13\t40\t53\nalliedmodders/hl2sdk\n\nHalf-Life 2 SDK Mirrors\n\n\t11\t40\t51\nSteamDatabase/steamdb.info-issues\n\n🚱 Issue tracker for the SteamDB website\n\n\t11\t40\t51\nCSGOFloat/inspect\n\nSource Code that Powers the CSFloat Inspect Link API\n\n\t10\t40\t50\nValveSoftware/SteamOS\n\nSteamOS community tracker\n\n\t10\t40\t50\nalliedmodders/source2mod\n\nExperimental\n\n\t40\t9\t49\nsmiley/steamapi\n\nAn unofficial object-oriented Python library for accessing the Steam Web API.\n\n\t9\t40\t49\nSteamDatabase/GameTracking\n\n🛢 Dumping things, so you don't have to\n\n\t8\t40\t48\nValveSoftware/counter-strike_rules_and_regs\n\nCS:GO\n\n\t7\t40\t47\nValveSoftware/openvr\n\nOpenVR SDK\n\n\t6\t40\t46\nSteamDatabase/easy-markdown-editor\n\nEasyMDE: A simple, beautiful, and embeddable JavaScript Markdown editor. Delightful editing for beginners and experts alike. Features built-in autosaving and spell checking.\n\n\t40\t4\t44\nValveSoftware/Dota-2\n\nTracker for issues specific to Linux and Mac in the Reborn client. If you have a general issue or non-system-specific feature request please go to dev.dota2.com\n\n\t6\t38\t44\nValveSoftware/Dota2-Gameplay\n\nPublic Bug Tracker for Dota 2\n\n\t4\t40\t44\nJustArchiNET/ArchiBot\n\nNo description in the capture.\n\n\t16\t27\t43\nztizzlegaming/CSGOWinBig\n\nOpen-source Counter-Strike: Global Offensive jackpot betting website.\n\n\t1\t40\t41\nJustArchiNET/mantis.justarchi.net\n\nMantis Bug Tracker (MantisBT)\n\n\t40\t0\t40\nodota/node-steam-user\n\nAllows interaction with the Steam network via the Steam client protocol\n\n\t40\t0\t40\nModDota/TypeScriptAddonTemplate\n\nDota 2 addon template with TypeScript Panorama and VScripts.\n\n\t9\t29\t38\nValvePython/vdf\n\n📜 Package for working with Valve's text and binary KeyValue format\n\n\t6\t32\t38\nalliedmodders/amtl\n\nAlliedModders C++ Template Library\n\n\t17\t19\t36\nValvePython/dota2\n\n🐸 Python package for interacting with Dota 2 Game Coordinator\n\n\t5\t30\t35\nalliedmodders/stripper-source\n\nStripper:Source\n\n\t13\t21\t34\nAllyans3/steam-market-api-v2\n\nSteam Market API v2 package\n\n\t3\t31\t34\nModDota/dota-tutorial\n\nCustom game DOTA tutorial.\n\n\t11\t23\t34\nodota/blog\n\nNo description in the capture.\n\n\t29\t3\t32\nOpsecGuy/BetterGo\n\nExternal CS:GO cheat written in python.\n\n\t1\t27\t28\npxvr-official/1\n\n無許諾配信 企業理念剽窃 動物の森収益化 大神ミオ権利者削除 戌神権利侵害発言 常闇トワ炎上 夜空メルストーカー被害 建築王サポーター放置 赤十字マーク 魔乃アロエ卒業 一つの中國支持声明 大空昴3Dライブ 無限延期清掃員職業差別 日清コラボ楽曲 musedash非公開 rog案件取り消し 壁画ライブ 丁真 Ding Zhen 郑爽 Zheng Shuang 防护林 与朵小天使w 伊月猫凛 本主萌埋午休傻 汪峰 重生细胞 壁纸 比利海灵顿 香蕉君 van 田所浩二 抽象带篮子 抗压背锅吧 季子越 蒋明辉 傻逼…\n\n\t0\t28\t28\nRevadike/InternalSteamWebAPI\n\nDocumenting the unofficial and internal Steam Web API\n\n\t1\t27\t28\nJoeSzymkowiczFiveM/qb-lootcrate\n\nA CSGO-style case opening script\n\n\t2\t25\t27\nAbrarKL/MyRoulette.XYZ\n\nCSGO / Steam Roulette Site created with PHP and Node JS, using the Material Design front-end framework.\n\n\t1\t25\t26\nJustArchiNET/ASF-WebConfigGenerator\n\nNo description in the capture.\n\n\t10\t15\t25\nModDota/dota-data\n\nAuto-generated Dota 2 resource dumps\n\n\t11\t14\t25\nModDota/TypeScriptDeclarations\n\nTypeScript declarations for Dota 2.\n\n\t11\t14\t25\nModDota/API\n\nNo description in the capture.\n\n\t12\t12\t24\nalliedmodders/cssdm\n\nCounter-Strike:Source Deathmatch\n\n\t10\t13\t23\nSteamDatabase/steamstat.us\n\n✅ Front-end of Steam services status website\n\n\t4\t18\t22\nc0deina/csgojackpotV2\n\nCSGO Jackpot Source\n\n\t1\t20\t21\nValvePython/steamctl\n\n🤸 Take control of Steam from your terminal\n\n\t2\t19\t21\nValvePython/csgo\n\n🔫 Python package for interacting with CS:GO Game Coordinator\n\n\t3\t17\t20\nBeepIsla/csgo-crash-exploit\n\nAllows you to crash any Windows user\n\n\t3\t16\t19\nValvePython/vpk\n\n📦 Open, Search, Extract and Create VPKs in python\n\n\t4\t15\t19\nalliedmodders/SM-SteamWorks\n\nExposing SteamWorks functions to SourcePawn.\n\n\t14\t3\t17\nSteamRE/Steam4NET\n\nSteam4NET is a .NET wrapper around the Steamworks C++ interfaces\n\n\t2\t15\t17\nalliedmodders/hl2sdk-manifests\n\nInformation about HL2SDKs shared between Metamod:Source and SourceMod.\n\n\t6\t10\t16\nJustArchiNET/ASF-PluginTemplate\n\nTemplate repository that you can use for creating custom plugins for ArchiSteamFarm.\n\n\t8\t7\t15\nModDota/Dota2AIFramework\n\nGeneral Framework for Dota 2 AI Competitions\n\n\t1\t14\t15\nShkyyl/KeyChamp\n\nExtension for joining free case battle on key-drop automatically\n\n\t1\t14\t15\nSteamDatabase/SteamMonitor\n\n😤 Track Steam's connection manager servers status\n\n\t2\t12\t14\nBaterka/cslore.com\n\nCS:GO gambling site - csgo.style\n\n\t1\t12\t13\nSteamDatabase/SteamTokenDumper\n\n🔢 Submit users' PICS access tokens to SteamDB\n\n\t2\t11\t13\nmonoblocker/roulette\n\nRoulette CS:GO made in React and Typescript\n\n\t1\t11\t12\nzsith/launcher.user.js\n\n// ==UserScript== // @name AposLauncher // @namespace AposLauncher // @include http://agar.io/* // @version 3.062 // @grant none // @author http://www.twitch.tv/apostolique // ==/UserScript== var aposLauncherVersion = 3.062; Nu…\n\n\t1\t11\t12\nLincolnIT/CSGODouble-bot-automated\n\nCSGODouble Automated, auto Betting Bot.\n\n\t1\t10\t11\nvladpuz/steam-market\n\nSteam market API client\n\n\t4\t7\t11\nmcgrizzz/Cstrike.bet\n\nCSGO Roulette Website Angular frontend, nodejs backend, and steam trading bots\n\n\t1\t9\t10\nodota/underlords-web\n\nUI for OpenUnderlords\n\n\t5\t5\t10\nSteamDatabase/SteamToTwitter\n\n🕊 Tweets announcements from various Steam groups\n\n\t1\t9\t10\nModDota/AbilityLuaSpellLibrary\n\nThe successor to the Spell Library by Pizzalol\n\n\t4\t4\t8\nalvinl/bitskins\n\nUnofficial BitSkins API client\n\n\t2\t5\t7\nb1naryth1ef/steamy\n\nA Python Steam community and market API interface that will get you all hot and bothered\n\n\t2\t5\t7\nkratos1812/Case-Opening\n\nIn-game case opening system for CSGO servers.\n\n\t2\t5\t7\nodota/docs\n\nOpenDota API documentation\n\n\t4\t3\t7\nSteamDatabase/steam-advanced-access-fetch-players\n\n📈 Simple script to fetch Steam player count\n\n\t1\t6\t7\nTheRioMiner/CsgoBetterExternalRaytrace\n\nOverridden maps pack for better external raytrace\n\n\t1\t6\t7\nalliedmodders/hl2sdk-mock\n\nMock HL2SDK and Server\n\n\t5\t1\t6\nchristophersu/PySteamMarket\n\nPython API for getting prices from the Steam market.\n\n\t1\t5\t6\nExtremelyd1/Strat-Roulette\n\nCS:GO Sourcemod Plugin\n\n\t2\t4\t6\ngiovanni-orciuolo/double-sdk\n\nA simple way to write CS:GO cheats!\n\n\t2\t4\t6\nJustArchiNET/Madness\n\nMadness embraces your project by including compatibility layer for selected APIs normally not available on .NET Framework target.\n\n\t5\t1\t6\nModDota/TypescriptPanoramaDeclarations\n\nNo description in the capture.\n\n\t4\t2\t6\nodota/rapier\n\nA JavaScript Dota 2 (Source 2) replay parsing library\n\n\t1\t5\t6\nVozn1akHero/CSGOCaseOpeningSimulator\n\nCounter-Strike case opening simulator which resembles the good old CS:GO user interface\n\n\t3\t3\t6\nautarc/steam-store\n\nAPI client for the unofficial steam storefront/big picture resource\n\n\t2\t3\t5\nBETTING-CODE/awesome-esports-sites\n\nA curated list of awesome esport betting sites – live, statistics and other resources.\n\n\t1\t4\t5\njonteohr/Better-Warden\n\nAn improved and more advanced warden plugin with a custom menu for CS:GO jailbreak servers!\n\n\t2\t3\t5\nLudzikk/CSGO-Gambling-Site\n\nhttps://ludzikk.github.io/CSGO-Gambling-Site/\n\n\t1\t4\t5\nModDota/find-steam-app\n\nFind location of an installed Steam app\n\n\t3\t2\t5\nmprey/csgocact.us\n\nsource code for csgocact.us\n\n\t1\t4\t5\nnezu-cc/ServerCrasher\n\nCS:GO Server Crasher\n\n\t1\t4\t5\nodota/testfiles\n\nStores test replay files\n\n\t2\t3\t5\nodota/underlordsconstants\n\nConstant data for Dota Underlords\n\n\t3\t2\t5\nSnaBe/node-steam-market-fetcher\n\nA Node.js wrapper for the Steam Community Market API.\n\n\t2\t3\t5\nSteamDatabase/.github\n\n💗 Organization-wide community health files\n\n\t1\t4\t5\nwolfcon/RIP-HLTV-BET\n\nRIP BET AD (For Tampermonkey) https://greasyfork.org/en/scripts/423484-rip-hltv-bet\n\n\t2\t3\t5\nalliedmodders/blaster.net\n\nSource and GoldSrc Query Tool\n\n\t2\t2\t4\ncatears124/CS2-Price-API\n\nsimple python cs2 steam market price API\n\n\t1\t3\t4\nialakey/caseforge\n\nOpen-source CS2 case-opening platform: Steam auth, provably fair openings, RTP-balanced case builder, withdrawals bought on market.csgo.com and an admin CRM.\n\n\t1\t3\t4\nIlusion9/csgo-fix-mapchange-crash-sm\n\nFix players crash on map change.\n\n\t1\t3\t4\nismail0234/Benson-Map-Crash-Fixer\n\nCSGO Map Change Client Crash Fixer\n\n\t1\t3\t4\njaxwilko/steam-market-api\n\nPHP - Composer Compatible - Steam Market API\n\n\t2\t2\t4\nJustArchiNET/ArchiTag\n\nArchiTag is a very small utility based on Python 3 and Mutagen to provide missing functionality in opusenc of writing specific Opus metadata, such as total number of tracks or track number.\n\n\t1\t3\t4\nModDota/DotaUI\n\nNo description in the capture.\n\n\t2\t2\t4\nnode-steam/market-pricing\n\nWrapper for the unofficial Steam Market Pricing API\n\n\t1\t3\t4\nodota/media\n\nStores media files for Dota projects\n\n\t2\t2\t4\nSergeyIvanovDevelop/Crypto-Steam-Platform\n\nThe repository contains the code and configuration to run a platform for creating cryptocurrency stakes for arbitrary ERC20 tokens.\n\n\t1\t3\t4\nAareksio/csgodouble-floatchecker\n\nAdds context menu option to check item's float value\n\n\t1\t2\t3\nchinm4/CSGOdrop\n\nA online csgo gambling casino that includes a variety of mini games that allows you to win csgo skins\n\n\t2\t1\t3\nCruze03/CSGO-Case-Opening-Prank\n\nCommand:- !prank (Admin flag \"n\" required)\n\n\t1\t2\t3\nDhruva-Kapadia/CSGOTrollGG\n\nCSGO Case Opening Simulator\n\n\t2\t1\t3\nErhanCSGO/CSGOPolygon-prediction\n\nCSGOPolygon.com - prediction script, double your coins by using this tool\n\n\t1\t2\t3\nEv-Hoang/Bedrock-Chest-Case-Opening\n\nHypixel Skyblock Dungeon Mod - Bedrock Chest Opening Animation (CSGO Style)\n\n\t1\t2\t3\njmjp/csgo-roulette\n\nA csgo gambling roulette make with VueJS 3\n\n\t2\t1\t3\nJustArchiNET/ArchiCrowdin\n\nNo description in the capture.\n\n\t1\t2\t3\nLeonSK/WearMarketInspector\n\nRetrieve Wear Value (Float Value) and Pattern Index from Steam Community Market using http://csgo.exchange API\n\n\t1\t2\t3\nmaximgeerinck/csgo-gamble\n\nCSGO gambling website\n\n\t1\t2\t3\nModDota/BugTracker\n\nListing bugs for Dota 2 Custom Games\n\n\t2\t1\t3\nplwp/mma-betting\n\nUFC/MMA betting model with Pinnacle steam detection for AU book latency arb\n\n\t2\t1\t3\nSouthsideswag16/Csgo-Gambling-Site\n\nNo description in the capture.\n\n\t2\t1\t3\ntacyarg/csgofiesta-frontend-react\n\nRemastered version a the long time favorite csgo site\n\n\t2\t1\t3\nVelorasse/Mutah-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-csmoney-csgoskins\n\ngambling script for Mutah, Keydrop, csmoney, and csgoskins, featuring hacks, cheats, and predictors. Offers strategies to boost winning odds and optimize performance on these platforms.\n\n\t3\t0\t3\nalliedmodders/am-github-artifact-webhook\n\nNo description in the capture.\n\n\t2\t0\t2\ncharamza/roulette\n\nCSGO like roulette in JS\n\n\t1\t1\t2\nCruze03/CSGO-PugSetup-RoundRestore\n\nSometimes (player dropped/crashed) which would be disadvantage for a team. It would be very handy to restore the match to the previous round.\n\n\t1\t1\t2\ncsgorol/CSGO-ROLL-Crash-Predictor\n\nCSGO-ROLL-Crash-Predictor\n\n\t1\t1\t2\nFoxSerito/FOXWORLD_plugin_DoubleJump_CSGO\n\nПлагин SourceMod (CSGO). Двойной прыжок с эффектом.\n\n\t1\t1\t2\nhkehayovmoonbiz/CS2-Casino-Full-Source-Code\n\nCS2, CS2 betting platforms, Skin Roulette, Case Unboxing, Crash games, Jackpot, purchase CS2 casino source, crypto gambling\n\n\t1\t1\t2\nJustZakary/steamstoreapi\n\nThis NPM module is a API wrapper that makes the steam unofficial API easier to use.\n\n\t2\t0\t2\njzimr/steam-market-api\n\nA java library to easily get Steam Community Market data\n\n\t1\t1\t2\nMomohime/CSGO.Network-Jackpot-Coinflip\n\nNo description in the capture.\n\n\t1\t1\t2\nnnjjswat/moneybot\n\nautomated bots for bustabit (formerly known as moneypot), csgo crash, etc\n\n\t0\t2\t2\nodota/carry\n\nLegacy Application for donations to the OpenDota project\n\n\t1\t1\t2\nodota/PublicMatchDataBot\n\nA Discord bot to remind users to turn on Expose Public Match Data in the Dota 2 client\n\n\t1\t1\t2\nOrillio/CSGOBet.com\n\nCSGO roulette web app\n\n\t2\t0\t2\nripexz/csgo-bet-alert\n\nA Chrome extension to keep track of active CS:GO Lounge matches.\n\n\t1\t1\t2\nrrpvm/lumen_sense-beta-deprecated-\n\nthis is internal csgo cheat written by me(no paste, self reverse structures). start : ~6 August 2020, end : ~ 14 December 2020\n\n\t1\t1\t2\nRuthless222/csgoscore\n\nThis is a Counter Strike Global Offensive Betting Site. You chose the skins you want to bet and try to win jackpots\n\n\t2\t0\t2\ntfburns/CSGO-cases-PL\n\nExpected profit-loss of CS:GO case openings\n\n\t1\t1\t2\nTomDra/CSGO-Case-Data-Analysis\n\nWorks out the most profitable CS:GO case at that current time\n\n\t1\t1\t2\nValvePython/dota2-wrappers\n\nNo description in the capture.\n\n\t1\t1\t2\nValvePython/teamfortress2-closed-captions\n\nThis project aims to provide a set of closed captions for Team Fortress 2\n\n\t1\t1\t2\nVistaNetGTX/Cstrike.bet-\n\nCSGO Roulette Website Angular frontend, nodejs backend, and steam trading bots\n\n\t1\t1\t2\nwafflas/csgo-case-opening-simulator\n\nI created a cs go case opening simulator for a meme coin\n\n\t0\t2\t2\nAdmiral-Enigma/Le_Coinflip\n\nConflip game\n\n\t1\t0\t1\nadryeljuliao/roulette-csgo\n\nNo description in the capture.\n\n\t1\t0\t1\nAndreuTheG/csgo-coinflip-web\n\nCSGO Gambling Coinflip Website\n\n\t1\t0\t1\nasmilen/csgoDouble\n\na b c\n\n\t1\t0\t1\nb1naryth1ef/csgofort\n\nA CSGO portal for trading, betting, analytics, and more!\n\n\t1\t0\t1\nBaterka/PrivateSteamBettingWebsite2024\n\nPrivate Steam (Counter-Strike 2) betting/gambling website - Roulette, Jackpot\n\n\t1\t0\t1\nblackcaer/SteamTradeHandler\n\nAutomation of Steam trading. Helper project for bet automation.\n\n\t1\t0\t1\nBTheCoderr/theRounders\n\nThe Rounders - A professional-grade sports betting analytics platform combining real-time odds tracking, sharp movement detection, and advanced statistical analysis. Features include line shopping, steam move alerts, power rankings, and comprehensive bet t…\n\n\t1\t0\t1\nCallumHemsley/KazeBot\n\nA Twitch chat betting bot for CSGO, simply bet a certain amount of points, and double if you win, lose all if you lose. Simple.\n\n\t1\t0\t1\nchrisjpm/CSGOJackpotTemplate\n\nFront end for a jackpot site\n\n\t1\t0\t1\ncolinsenner/valve-bug-bounty\n\nFor many years CS:GO, Dota 2, and Team Fortress 2 servers had a bug that allowed malicious users to leak crucial server process memory or reliably crash any server.\n\n\t1\t0\t1\ncoryypeters/nrl-odds-intelligence-pipeline\n\nReal-time sports betting odds intelligence — streaming pipeline that detects line movement, steam, and arbitrage across bookmakers. Python · Redis Streams · FastAPI · React.\n\n\t1\t0\t1\ndeissh/dev-csgoduo\n\nCS:GO. Bot for receiving things on the site (Polygon, Duo, Double and etc).\n\n\t1\t0\t1\ndom1torii/even-better-font-manager\n\nSimply even better cross-platform tool for CS2 Font Management\n\n\t1\t0\t1\nDONnicov/CSGO-crash-black-screen-\n\nsolution csgo crash black screen and close csgo\n\n\t1\t0\t1\nDoubleBoters/CsgoDouble\n\nNo description in the capture.\n\n\t1\t0\t1\ndownarowiczd/DoubleBot\n\nAn old CSGO Double Bot written for my friend. - 07.05.2016\n\n\t1\t0\t1\nErayBahar/steammarketscraper\n\nSteam Market Scraper Python-based tool that tracks real-time CS2 skin prices using Steam's hidden API. It fetches the lowest sell and highest buy offers for any item, helping you monitor deals or snipe underpriced listings automatically.\n\n\t1\t0\t1\nfairydarkness/SteamwebmailAPI\n\nUnofficial Python API for steamwebmail.com Fast, lightweight, and browserless library for automating steamwebmail.com. Support for session management, proxy, folder navigation, and message retrieval\n\n\t1\t0\t1\nFAQU2/CSGO-Coinflip-MyJailShop\n\nSourcemod plugin which provides a Coinflip system for MyJailShop.\n\n\t1\t0\t1\nFlamesONE/csgo-case-opening\n\nNo description in the capture.\n\n\t1\t0\t1\nFunnyRain/csgorun-crash-watch\n\n🚀 CsgoRun dump crash. / 🚀 CsgoRun дамп крашей.\n\n\t1\t0\t1\ngeohdgio/Venatus-Autenticator\n\nეს არის Steam Autenticator ქართული Venatus Trade & Betting ისთვის და Valve News Georgia-სთვის.\n\n\t1\t0\t1\nhakanstarlord/steam-bot\n\nSports betting steam-move signal detection with ML pipeline (XGBoost stacking + isotonic calibration), backtesting engine, Flask dashboard, and Telegram alerts.\n\n\t1\t0\t1\nHvH-gg/CSGO-Item-CrashFix\n\nA plugin for Counter-Strike: Global Offensive that fixes an exploit where receiving CS2 Items will cause CS:GO clients to crash\n\n\t1\t0\t1\nHvH-gg/CSGO-NetMsg-CrashFix\n\nA plugin for Counter-Strike: Global Offensive that fixes an exploit where spamming NetMsg_StringCmd packets would result in a server crash.\n\n\t1\t0\t1\nisybycnsmam/SteamLibrary\n\nLegacy Steam Unofficial API\n\n\t1\t0\t1\nItsTangerine/SteamApis.Net\n\nUnofficial https://steamapis.com .NET library, supporting .NET 6.0+\n\n\t1\t0\t1\nJustArchiNET/JustArchi.net\n\nNo description in the capture.\n\n\t1\t0\t1\nkiri-osint/CS2-Info-Hub-Bot\n\nA Telegram bot that acts as a hub for CS2 players, providing real-time skin prices, server stats, and user profile/inventory inspection using official and unofficial Steam APIs.\n\n\t1\t0\t1\nKoshkaj/monte\n\nGamified csgo gambling platform implementation\n\n\t1\t0\t1\nmadsab/CaseOpening\n\nA school project using Java. Simulating the case opening from CSGO and more.\n\n\t1\t0\t1\nman90es/steamcardexchange-api\n\nSteamCardExchange.net unofficial REST API server (scraper).\n\n\t1\t0\t1\nMattPua/steam-unofficial-docs\n\nUnofficial docs for Steam APIs with fumadocs\n\n\t1\t0\t1\nMetallist1/Portfolio.CsgoWinGambleProject\n\nA website that was done in 2017 September. Websites focus was on gambling with Counter-Strike items. Project was largely completed however backups were not done correctly, this resulted in half a year of wasted improvements to the code. The website was test…\n\n\t1\t0\t1\nmikebobadilla/csgo-jackpot\n\nNo description in the capture.\n\n\t0\t1\t1\nmikebobadilla/meteor-csgojackpot\n\nCssgo Jackpot done in meteor\n\n\t1\t0\t1\nModDota/D2VDump\n\nDota 2 Server VScript API Dumper\n\n\t1\t0\t1\nModDota/DotaTracking\n\nNo description in the capture.\n\n\t1\t0\t1\nModDota/eslint-config\n\nESLint config by ark120202\n\n\t1\t0\t1\nmr-codinglv/Casino-script\n\nscript casino - script betting - exchange script - bc casino - casino csgo - script bet - betwin script\n\n\t1\t0\t1\nMrKeelik/MrKeel\n\nCSGO DOUBLE BOT\n\n\t1\t0\t1\nnoahlatzel/CSGORollHelper\n\nLeveraging positive expected value on triple green jackpots on CSGORoll!\n\n\t1\t0\t1\noddsgpt/oddsgpt-market-intelligence\n\nResearch on football betting markets, closing odds, CLV, market efficiency, steam moves, AI betting systems, and sports market intelligence.\n\n\t1\t0\t1\noEXU/csgo-server-crasher\n\nCSGO SERVER CRASHER\n\n\t1\t0\t1\nPrdTTony/CSGO-Roulette\n\n[CSGO] Roulette System. Bet on RED or Black and win x2 credits\n\n\t1\t0\t1\nr-adamski/csgo-jackpot\n\nNo description in the capture.\n\n\t1\t0\t1\nSahotallo/Turan-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-Skinbaron-hellcase\n\ngambling script for Turan, Keydrop, Skinbaron, and Hellcase, providing hacks, cheats, and predictors. Includes strategies to improve winning chances and enhance gameplay on these platforms.\n\n\t1\t0\t1\nsamuelcsouza/steam-marketplace-api\n\nAn unofficial API to get data from the Steam Marketplace.\n\n\t1\t0\t1\nSKINSTRACK/CS2-Price-API\n\nSkinstrack offers a free, limited API endpoint that returns Steam item prices. Paid plans additionally provide access to pricing data from multiple marketplaces, making it possible to compare prices across different markets through a single API.\n\n\t1\t0\t1\nsnmtriet/CSGO-Casino-Full-Source-Code\n\nCSGO, CSGOEmpire, Case Opening, Case Battles, Roulette, Coinflip, buy csgo gambling site, gambling\n\n\t1\t0\t1\nSteamRE/homebrew-tools\n\nRepository for installation of SteamRE tools via Homebrew (http://brew.sh)\n\n\t1\t0\t1\nSteamRE/opensteamworks.org\n\nNo description in the capture.\n\n\t1\t0\t1\nTheQuack45/CsgoCaseOpenProgram\n\nSimple program to parse an XML file with CS:GO case information and \"simulate\" case openings\n\n\t1\t0\t1\nTLClassless/StratRouletteCSGO\n\nA 'Strat Roulette' web app for CS:GO!\n\n\t1\t0\t1\ntomasoom/csgoCaseOpening\n\nNo description in the capture.\n\n\t1\t0\t1\nvitaliy-evsyukov/steamgifts-autobet-bookmarklet\n\nbookmarklet for automatic bets on steamgifts.com\n\n\t1\t0\t1\nXpravdaX/RouletteCSGO\n\nNo description in the capture.\n\n\t1\t0\t1\nYuiKasumii/steam_api_unofficial\n\nUnofficial Steam Game Information Database\n\n\t1\t0\t1\nZexuz/Steam-Betting\n\nA betting website build ontop of STEAM's ecosystem\n\n\t1\t0\t1\nANK-RULZZ/steam-jackpot-site\n\ngetting some errors and would like some one to help me with it thank you!!!\n\n\t0\t0\t0\nasmilen/CsgoDoubleVS\n\nNo description in the capture.\n\n\t0\t0\t0\nCORNOODOSADAS/CSGOWeed\n\nCsgo Jackpot and Coinflip\n\n\t0\t0\t0\nCSGOApple/csgoapple\n\nJackpot Site\n\n\t0\t0\t0\nCSGOFAST/csgofast-api\n\nNo description in the capture.\n\n\t0\t0\t0\nDonakall/csgoDoublebot\n\nAutomated bot for csgodouble\n\n\t0\t0\t0\nfedor-selivanov/csgo-fast-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nfoldageros/csgod\n\ndouble bot\n\n\t0\t0\t0\ngmod-gambling/gmod-gambling\n\nNo description in the capture.\n\n\t0\t0\t0\nierome/CSGOBoss-BackEnd\n\nBack end version of CSGOBoss. This was a CSGO Gambling site named CSGOBoss. Coded by an old friend of mine Dahquan Hinds (https://github.com/dahquan/) Thought I would release this to help out any one who would need it.\n\n\t0\t0\t0\njamienp1/CSGODOUBLE-BOT-AUTO\n\ni got a bot thats is betting on the last winning color except from green and if you lose it will double the coins you set it to bet, pretty good, so when there comes a loooong train you will be gaining a bit of money codepaste_net/ugmt92 remove all the _ an…\n\n\t0\t0\t0\nJEYONER/CSGOTOXIC\n\nPAGINA DE JACKPOT CSGO SKINS\n\n\t0\t0\t0\nkalrish/csgo-jackpot\n\nStressful but funny zombie-like Counter-Strike: Global Offensive game mode.\n\n\t0\t0\t0\nkrys12345/roulettee\n\n// ==UserScript== // @name CSGO Predict Bot // @namespace http://csgodouble.com // @version 1.0 // @description predicts what number its gonna be // @author Meee // @match http://www.csgodouble.com/ // @grant none // ==/…\n\n\t0\t0\t0\nLilDuggiMuffi/CSGODouble-Working-Bot\n\nFixed CSGO Double Bot\n\n\t0\t0\t0\nLyricLy/Steam2Proton\n\nCheck if all your Steam games will work with Proton! Uses the official Steam API and the unofficial Proton API.\n\n\t0\t0\t0\nM0NsTeR77/csgo-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nozanhalis/Hi\n\n// ==UserScript== // @name CS GO LOUNGE BOT-Ozan Halis // @namespace http://csgolounge.com/ // @version 0.6.6 // @description Cs Go Lounge Hızlı BOT // @match http://csgolounge.com/* // @match http://dota2lounge.com/* // @updateURL h…\n\n\t0\t0\t0\nscoobertus/CSGO-DoubleBot\n\nNo description in the capture.\n\n\t0\t0\t0\nTradeal/CSGO-Jackpot-Bot\n\nNo description in the capture.\n\n\t0\t0\t0\nValvePython/artifact\n\nNo description in the capture.\n\n\t0\t0\t0\nVampire/CSGO-Roulette-Bot\n\nNo description in the capture.\n\n\t0\t0\t0\nvdemans/csgo-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nVocoreVideo/CSGODungeon-\n\nCSGO Jackpot\n\n\t0\t0\t0\nwayz-dev/csgofloat\n\nNo description in the capture.\n\n\t0\t0\t0\n\nResumo: 17 2026, 11:19:11 tal como consta na fonte; fuso horário não especificado. A coleção de relações está limitada na exportação (muitas categorias terminam em 40). Os colaboradores e os criadores de bifurcações totalizam 4,554 entradas de funções em 4,214 pares distintos de perfil–repositório; um perfil pode ter ambas as funções. O valor zero significa que não foram registados dados nessa categoria. Os nomes dos repositórios podem incluir aliases ou variações de maiúsculas e minúsculas; os totais mantêm as convenções de contagem da fonte.\n\nProveniência da fonte\nCriado a partir dos ficheiros que recolheu.\nTestemunho de apoio\n2323/reddit_scams_ultra/steam_support_tickets_MEGA.json · linhas 45, 58, 107, 110, 294\nInstantâneo da rede\nnetwork-repositories.csv · raw_data.json · overlaps.csv · summary.txt (os caminhos históricos das fontes foram mantidos no manifesto)\n\nO manifesto regista os caminhos de origem, os tamanhos em bytes, os hash SHA-256 e as posições dos registos selecionados. As capturas em bruto permanecem separadas da interpretação da investigação.\n\nDescarregar o manifesto de origem ↓",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam Provas de cumprimento — Registos de apoio e rede de programadores"
          },
          {
            "level": 2,
            "id": null,
            "text": "Leia a queixa.Anexe o código-fonte."
          },
          {
            "level": 3,
            "id": null,
            "text": "Permanent sanction & closed appeals"
          },
          {
            "level": 4,
            "id": null,
            "text": "Permanently banned Steam account without a clear explanation, need help!"
          },
          {
            "level": 3,
            "id": null,
            "text": "Account recovery & a reported $10,000 loss"
          },
          {
            "level": 4,
            "id": null,
            "text": "Got $10k stollen from steam inventory due to steam' support fault."
          },
          {
            "level": 3,
            "id": null,
            "text": "A reported $500+ loss & template replies"
          },
          {
            "level": 4,
            "id": null,
            "text": "Funds stolen through steam market. Disappointed with Steam response.(or lackthereof)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam Guard & an item-restoration refusal"
          },
          {
            "level": 4,
            "id": null,
            "text": "Many people are losing item via clicking links where steam guard is enabled and steam support doesn't not restore items."
          },
          {
            "level": 3,
            "id": null,
            "text": "Selective enforcement & an unexplained ban"
          },
          {
            "level": 4,
            "id": null,
            "text": "🚨 Steam Bans Without Reason and Ignores Its Community — What’s Going On?"
          },
          {
            "level": 2,
            "id": null,
            "text": "Infraestruturas públicas.Gravado em grande escala."
          },
          {
            "level": 2,
            "id": null,
            "text": "Criado a partir dos ficheiros que recolheu."
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/pt/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/pt/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/selected-support-records.json",
          "https://phishdestroy.io/steam_dossier/pt/investigation_part2.html#outsourcing-case",
          "https://www.reddit.com/r/ohnePixel/comments/1hahqx2/permanently_banned_steam_account_without_a_clear/",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://www.reddit.com/r/DotA2/comments/r55bd7/many_people_are_losing_item_via_clicking_links/",
          "https://www.reddit.com/r/SteamUncensored/comments/1kjt2fa/steam_bans_without_reason_and_ignores_its/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/network-repositories.csv",
          "https://github.com/alliedmodders/amxmodx",
          "https://github.com/alliedmodders/sourcemod",
          "https://github.com/DoctorMcKay/node-steam-user",
          "https://github.com/Facepunch/Facepunch.Steamworks",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://github.com/odota/core",
          "https://github.com/odota/dotaconstants",
          "https://github.com/odota/web",
          "https://github.com/splewis/get5",
          "https://github.com/SteamDatabase/FileDetectionRuleSets",
          "https://github.com/SteamRE/SteamKit",
          "https://github.com/ValveSoftware/dxvk",
          "https://github.com/ValveSoftware/GameNetworkingSockets",
          "https://github.com/ValveSoftware/gamescope",
          "https://github.com/ValveSoftware/Proton",
          "https://github.com/ValveSoftware/source-sdk-2013",
          "https://github.com/ValveSoftware/wine",
          "https://github.com/ValveSoftware/steam-devices",
          "https://github.com/ValveSoftware/steam-audio",
          "https://github.com/alliedmodders/metamod-source",
          "https://github.com/alliedmodders/sourcepawn",
          "https://github.com/ValveSoftware/Fossilize",
          "https://github.com/rlabrecque/Steamworks.NET",
          "https://github.com/ModDota/moddota.github.io",
          "https://github.com/odota/parser",
          "https://github.com/ValveSoftware/steam-for-linux",
          "https://github.com/SteamRE/DepotDownloader",
          "https://github.com/JustArchiNET/ASF-ui",
          "https://github.com/advancedfx/advancedfx",
          "https://github.com/alliedmodders/ambuild",
          "https://github.com/SteamDatabase/BrowserExtension",
          "https://github.com/odota/mobile",
          "https://github.com/ValvePython/steam",
          "https://github.com/skadistats/clarity",
          "https://github.com/SteamRE/open-steamworks",
          "https://github.com/ValveSoftware/Source-1-Games",
          "https://github.com/alliedmodders/hl2sdk",
          "https://github.com/SteamDatabase/steamdb.info-issues",
          "https://github.com/CSGOFloat/inspect",
          "https://github.com/ValveSoftware/SteamOS",
          "https://github.com/alliedmodders/source2mod",
          "https://github.com/smiley/steamapi",
          "https://github.com/SteamDatabase/GameTracking",
          "https://github.com/ValveSoftware/counter-strike_rules_and_regs",
          "https://github.com/ValveSoftware/openvr",
          "https://github.com/SteamDatabase/easy-markdown-editor",
          "https://github.com/ValveSoftware/Dota-2",
          "https://github.com/ValveSoftware/Dota2-Gameplay",
          "https://github.com/JustArchiNET/ArchiBot",
          "https://github.com/ztizzlegaming/CSGOWinBig",
          "https://github.com/JustArchiNET/mantis.justarchi.net",
          "https://github.com/odota/node-steam-user",
          "https://github.com/ModDota/TypeScriptAddonTemplate",
          "https://github.com/ValvePython/vdf",
          "https://github.com/alliedmodders/amtl",
          "https://github.com/ValvePython/dota2",
          "https://github.com/alliedmodders/stripper-source",
          "https://github.com/Allyans3/steam-market-api-v2",
          "https://github.com/ModDota/dota-tutorial",
          "https://github.com/odota/blog",
          "https://github.com/OpsecGuy/BetterGo",
          "https://github.com/pxvr-official/1",
          "https://github.com/Revadike/InternalSteamWebAPI",
          "https://github.com/JoeSzymkowiczFiveM/qb-lootcrate",
          "https://github.com/AbrarKL/MyRoulette.XYZ",
          "https://github.com/JustArchiNET/ASF-WebConfigGenerator",
          "https://github.com/ModDota/dota-data",
          "https://github.com/ModDota/TypeScriptDeclarations",
          "https://github.com/ModDota/API",
          "https://github.com/alliedmodders/cssdm",
          "https://github.com/SteamDatabase/steamstat.us",
          "https://github.com/c0deina/csgojackpotV2",
          "https://github.com/ValvePython/steamctl",
          "https://github.com/ValvePython/csgo",
          "https://github.com/BeepIsla/csgo-crash-exploit",
          "https://github.com/ValvePython/vpk",
          "https://github.com/alliedmodders/SM-SteamWorks",
          "https://github.com/SteamRE/Steam4NET",
          "https://github.com/alliedmodders/hl2sdk-manifests",
          "https://github.com/JustArchiNET/ASF-PluginTemplate",
          "https://github.com/ModDota/Dota2AIFramework",
          "https://github.com/Shkyyl/KeyChamp",
          "https://github.com/SteamDatabase/SteamMonitor",
          "https://github.com/Baterka/cslore.com",
          "https://github.com/SteamDatabase/SteamTokenDumper",
          "https://github.com/monoblocker/roulette",
          "https://github.com/zsith/launcher.user.js",
          "https://github.com/LincolnIT/CSGODouble-bot-automated",
          "https://github.com/vladpuz/steam-market",
          "https://github.com/mcgrizzz/Cstrike.bet",
          "https://github.com/odota/underlords-web",
          "https://github.com/SteamDatabase/SteamToTwitter",
          "https://github.com/ModDota/AbilityLuaSpellLibrary",
          "https://github.com/alvinl/bitskins",
          "https://github.com/b1naryth1ef/steamy",
          "https://github.com/kratos1812/Case-Opening",
          "https://github.com/odota/docs",
          "https://github.com/SteamDatabase/steam-advanced-access-fetch-players",
          "https://github.com/TheRioMiner/CsgoBetterExternalRaytrace",
          "https://github.com/alliedmodders/hl2sdk-mock",
          "https://github.com/christophersu/PySteamMarket",
          "https://github.com/Extremelyd1/Strat-Roulette",
          "https://github.com/giovanni-orciuolo/double-sdk",
          "https://github.com/JustArchiNET/Madness",
          "https://github.com/ModDota/TypescriptPanoramaDeclarations",
          "https://github.com/odota/rapier",
          "https://github.com/Vozn1akHero/CSGOCaseOpeningSimulator",
          "https://github.com/autarc/steam-store",
          "https://github.com/BETTING-CODE/awesome-esports-sites",
          "https://github.com/jonteohr/Better-Warden",
          "https://github.com/Ludzikk/CSGO-Gambling-Site",
          "https://github.com/ModDota/find-steam-app",
          "https://github.com/mprey/csgocact.us",
          "https://github.com/nezu-cc/ServerCrasher",
          "https://github.com/odota/testfiles",
          "https://github.com/odota/underlordsconstants",
          "https://github.com/SnaBe/node-steam-market-fetcher",
          "https://github.com/SteamDatabase/.github",
          "https://github.com/wolfcon/RIP-HLTV-BET",
          "https://github.com/alliedmodders/blaster.net",
          "https://github.com/catears124/CS2-Price-API",
          "https://github.com/ialakey/caseforge",
          "https://github.com/Ilusion9/csgo-fix-mapchange-crash-sm",
          "https://github.com/ismail0234/Benson-Map-Crash-Fixer",
          "https://github.com/jaxwilko/steam-market-api",
          "https://github.com/JustArchiNET/ArchiTag",
          "https://github.com/ModDota/DotaUI",
          "https://github.com/node-steam/market-pricing",
          "https://github.com/odota/media",
          "https://github.com/SergeyIvanovDevelop/Crypto-Steam-Platform",
          "https://github.com/Aareksio/csgodouble-floatchecker",
          "https://github.com/chinm4/CSGOdrop",
          "https://github.com/Cruze03/CSGO-Case-Opening-Prank",
          "https://github.com/Dhruva-Kapadia/CSGOTrollGG",
          "https://github.com/ErhanCSGO/CSGOPolygon-prediction",
          "https://github.com/Ev-Hoang/Bedrock-Chest-Case-Opening",
          "https://github.com/jmjp/csgo-roulette",
          "https://github.com/JustArchiNET/ArchiCrowdin",
          "https://github.com/LeonSK/WearMarketInspector",
          "https://github.com/maximgeerinck/csgo-gamble",
          "https://github.com/ModDota/BugTracker",
          "https://github.com/plwp/mma-betting",
          "https://github.com/Southsideswag16/Csgo-Gambling-Site",
          "https://github.com/tacyarg/csgofiesta-frontend-react",
          "https://github.com/Velorasse/Mutah-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-csmoney-csgoskins",
          "https://github.com/alliedmodders/am-github-artifact-webhook",
          "https://github.com/charamza/roulette",
          "https://github.com/Cruze03/CSGO-PugSetup-RoundRestore",
          "https://github.com/csgorol/CSGO-ROLL-Crash-Predictor",
          "https://github.com/FoxSerito/FOXWORLD_plugin_DoubleJump_CSGO",
          "https://github.com/hkehayovmoonbiz/CS2-Casino-Full-Source-Code",
          "https://github.com/JustZakary/steamstoreapi",
          "https://github.com/jzimr/steam-market-api",
          "https://github.com/Momohime/CSGO.Network-Jackpot-Coinflip",
          "https://github.com/nnjjswat/moneybot",
          "https://github.com/odota/carry",
          "https://github.com/odota/PublicMatchDataBot",
          "https://github.com/Orillio/CSGOBet.com",
          "https://github.com/ripexz/csgo-bet-alert",
          "https://github.com/rrpvm/lumen_sense-beta-deprecated-",
          "https://github.com/Ruthless222/csgoscore",
          "https://github.com/tfburns/CSGO-cases-PL",
          "https://github.com/TomDra/CSGO-Case-Data-Analysis",
          "https://github.com/ValvePython/dota2-wrappers",
          "https://github.com/ValvePython/teamfortress2-closed-captions",
          "https://github.com/VistaNetGTX/Cstrike.bet-",
          "https://github.com/wafflas/csgo-case-opening-simulator",
          "https://github.com/Admiral-Enigma/Le_Coinflip",
          "https://github.com/adryeljuliao/roulette-csgo",
          "https://github.com/AndreuTheG/csgo-coinflip-web",
          "https://github.com/asmilen/csgoDouble",
          "https://github.com/b1naryth1ef/csgofort",
          "https://github.com/Baterka/PrivateSteamBettingWebsite2024",
          "https://github.com/blackcaer/SteamTradeHandler",
          "https://github.com/BTheCoderr/theRounders",
          "https://github.com/CallumHemsley/KazeBot",
          "https://github.com/chrisjpm/CSGOJackpotTemplate",
          "https://github.com/colinsenner/valve-bug-bounty",
          "https://github.com/coryypeters/nrl-odds-intelligence-pipeline",
          "https://github.com/deissh/dev-csgoduo",
          "https://github.com/dom1torii/even-better-font-manager",
          "https://github.com/DONnicov/CSGO-crash-black-screen-",
          "https://github.com/DoubleBoters/CsgoDouble",
          "https://github.com/downarowiczd/DoubleBot",
          "https://github.com/ErayBahar/steammarketscraper",
          "https://github.com/fairydarkness/SteamwebmailAPI",
          "https://github.com/FAQU2/CSGO-Coinflip-MyJailShop",
          "https://github.com/FlamesONE/csgo-case-opening",
          "https://github.com/FunnyRain/csgorun-crash-watch",
          "https://github.com/geohdgio/Venatus-Autenticator",
          "https://github.com/hakanstarlord/steam-bot",
          "https://github.com/HvH-gg/CSGO-Item-CrashFix",
          "https://github.com/HvH-gg/CSGO-NetMsg-CrashFix",
          "https://github.com/isybycnsmam/SteamLibrary",
          "https://github.com/ItsTangerine/SteamApis.Net",
          "https://github.com/JustArchiNET/JustArchi.net",
          "https://github.com/kiri-osint/CS2-Info-Hub-Bot",
          "https://github.com/Koshkaj/monte",
          "https://github.com/madsab/CaseOpening",
          "https://github.com/man90es/steamcardexchange-api",
          "https://github.com/MattPua/steam-unofficial-docs",
          "https://github.com/Metallist1/Portfolio.CsgoWinGambleProject",
          "https://github.com/mikebobadilla/csgo-jackpot",
          "https://github.com/mikebobadilla/meteor-csgojackpot",
          "https://github.com/ModDota/D2VDump",
          "https://github.com/ModDota/DotaTracking",
          "https://github.com/ModDota/eslint-config",
          "https://github.com/mr-codinglv/Casino-script",
          "https://github.com/MrKeelik/MrKeel",
          "https://github.com/noahlatzel/CSGORollHelper",
          "https://github.com/oddsgpt/oddsgpt-market-intelligence",
          "https://github.com/oEXU/csgo-server-crasher",
          "https://github.com/PrdTTony/CSGO-Roulette",
          "https://github.com/r-adamski/csgo-jackpot",
          "https://github.com/Sahotallo/Turan-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-Skinbaron-hellcase",
          "https://github.com/samuelcsouza/steam-marketplace-api",
          "https://github.com/SKINSTRACK/CS2-Price-API",
          "https://github.com/snmtriet/CSGO-Casino-Full-Source-Code",
          "https://github.com/SteamRE/homebrew-tools",
          "https://github.com/SteamRE/opensteamworks.org",
          "https://github.com/TheQuack45/CsgoCaseOpenProgram",
          "https://github.com/TLClassless/StratRouletteCSGO",
          "https://github.com/tomasoom/csgoCaseOpening",
          "https://github.com/vitaliy-evsyukov/steamgifts-autobet-bookmarklet",
          "https://github.com/XpravdaX/RouletteCSGO",
          "https://github.com/YuiKasumii/steam_api_unofficial",
          "https://github.com/Zexuz/Steam-Betting",
          "https://github.com/ANK-RULZZ/steam-jackpot-site",
          "https://github.com/asmilen/CsgoDoubleVS",
          "https://github.com/CORNOODOSADAS/CSGOWeed",
          "https://github.com/CSGOApple/csgoapple",
          "https://github.com/CSGOFAST/csgofast-api",
          "https://github.com/Donakall/csgoDoublebot",
          "https://github.com/fedor-selivanov/csgo-fast-roulette",
          "https://github.com/foldageros/csgod",
          "https://github.com/gmod-gambling/gmod-gambling",
          "https://github.com/ierome/CSGOBoss-BackEnd",
          "https://github.com/jamienp1/CSGODOUBLE-BOT-AUTO",
          "https://github.com/JEYONER/CSGOTOXIC",
          "https://github.com/kalrish/csgo-jackpot",
          "https://github.com/krys12345/roulettee",
          "https://github.com/LilDuggiMuffi/CSGODouble-Working-Bot",
          "https://github.com/LyricLy/Steam2Proton",
          "https://github.com/M0NsTeR77/csgo-roulette",
          "https://github.com/ozanhalis/Hi",
          "https://github.com/scoobertus/CSGO-DoubleBot",
          "https://github.com/Tradeal/CSGO-Jackpot-Bot",
          "https://github.com/ValvePython/artifact",
          "https://github.com/Vampire/CSGO-Roulette-Bot",
          "https://github.com/vdemans/csgo-roulette",
          "https://github.com/VocoreVideo/CSGODungeon-",
          "https://github.com/wayz-dev/csgofloat",
          "https://phishdestroy.io/steam_dossier/output_steam_network/raw_data.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/enforcement-source-manifest.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/pt/steam_enforcement_evidence.content.json",
      "export_json_sha256": "5fb2a3557f42d6502b1a3078c63977c688fb242d8813b15f2bce53aa2a23bfad"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "pt/steam_evidence_archive.html",
      "language": "pt",
      "title": "Analise as fontes — O Dossiê «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/pt/steam_evidence_archive",
      "source_html_sha256": "ce4679b33dd55341cde5b62cfa8a4059da7badd93217988b5626e9dd8d9c7a8f",
      "exported_at": "2026-09-29T00:18:15.320Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "steam_evidence_archive.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/pt/steam_evidence_archive.pdf?v=print-20260929-v5",
        "sha256": "6f716a49893c8ec5950b56a023237b51a09f1f03d774daf8fe05c60cfc08db62",
        "bytes": 64274,
        "pages": 4
      },
      "integrity": {
        "signed_object": "steam_evidence_archive.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "steam_evidence_archive.content.json.asc",
        "digest_file": "steam_evidence_archive.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify steam_evidence_archive.content.json.asc steam_evidence_archive.content.json",
          "sha256sum -c steam_evidence_archive.content.json.sha256"
        ]
      },
      "content": {
        "text": "MATERIAIS DE INVESTIGAÇÃO / RECOLHA DE FONTES 002\nSteam Arquivo de Provas — Documentos provenientes de «16,319»\n\nTodas as reclamações. De volta à origem.\n\nO QUE ESTA SECÇÃO DEMONSTRA\n\nEste arquivo forense indexa registos de fontes primárias d16,319 — que abrangem documentação da Comunidade de Desenvolvedores dValve, questões públicas no GitHub, reclamações verificadas no Trustpilot e relatórios arquivados de fóruns — com hashes criptográficos e registos de proveniência. Fornece uma base de provas passível de inspeção que demonstra vulnerabilidades repetíveis da plataforma, descontinuações não documentadas do API e reclamações persistentes de consumidores relativas a contas pirateadas.\n\n← Voltar ao resumo executivo\n\nEncontre o registo subjacente a uma alegação. Filtre por fonte, abra o texto completo e siga a ligação original. As linhas das fontes podem sobrepor-se; um registo não constitui um incidente confirmado.\n\nVoltar à investigação ↗\n354TRUSTPILOT / LINHAS DE ORIGEM\n208REDDIT / LINHAS DE FONTE\n705GITHUB / LINHAS DE CÓDIGO\n15,302MASTER CSV / LINHAS DE ORIGEM\n16,319 REGISTO — DISTRIBUIÇÃO POR TIPO DE PLATAFORMA\n\nProveniência da categoria da Wiki (registos do 7,620 · 46.7%): Dados extraídos da Comunidade de Desenvolvedores do Valve (developer.valvesoftware.com), da Documentação/Perguntas Frequentes do SteamDB e de wikis da comunidade de jogos (Liquipedia CS/Dota e wikis do Fandom Steam) através de instantâneos WARC automatizados e dos pontos de acesso MediaWiki API entre agosto 2024 e setembro 2026. Todas as entradas 7,620 estão totalmente integradas na exportação CSV principal (TOTAL_VALVE_SCANDALS_MASTER_DB.csv).\n\nWiki\n7,620\nReddit\n5,635\nGitHub\n2,395\nTrustpilot\n393\nWeb\n276\n9,116 dos registos de 16,319 (55.8%) contêm referências a Steam / Valve\n\nEste arquivo pesquisável foi criado com base em 2026-09-17 a partir das exportações de dados de origem acima indicadas. A exportação principal separada «40,448-», utilizada noutras partes do dossiê, tem um âmbito diferente. Consulte o criar manifesto no que diz respeito às contagens deste arquivo; os registos podem sobrepor-se e não correspondem a incidentes únicos.\n\nPLATAFORMA DE ORIGEM\nRECOLHA DE FONTES\nSteam / Valve menções\nCorrespondência de texto ou repositório «Valve»Texto em falta / removido\n16,569 linhas de origem\n16,319 registos distintos\n249 linhas duplicadas foram unidas\n1 linha excluída\nVer os ficheiros originais ↘\n★TRUSTPILOT2015-10-16#1RATING 1/5\n\nSteam is the biggest PC gaming platform without a doubt. A power which could be abused but Steam for the most part doesn't. Overall a definite download for any moden digital age PC gamer. It mu... See more\n\nMA · 7 source copies\n★TRUSTPILOT2021-06-18#2RATING 1/5\n\nThey scam people for money, dont believe me? Read this Source: Steam Subscribers/User Agreement NO GUARANTEES TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, NEITHER VALVE NOR ITS AFFILIA... See more\n\nWF · 7 source copies\n★TRUSTPILOT2016-10-28#3RATING 1/5\n\nSupport on site is terrible. Refunds not happend yet, despite games not working. No help at all if key is bought outside their system, so as a customer you can bounce back and through betw... See more\n\nPE · 7 source copies\n★TRUSTPILOT2021-09-27#4RATING 1/5\n\nThey are an amazing company!! My boyfriend paid for and downloaded a game without realizing it wasn’t the version he wanted. When he reached out, they gave him a full refund and responded in the same... See more\n\nVH · 7 source copies\n★TRUSTPILOT2026-07-20#5RATING 1/5\n\nI’ve used Steam for years, but lately, their sales have really lost their edge. I was hoping to score some solid discounts, but many games still feel overpriced, even during sales. Plus, the support response times can be frustratingly slow when issues arise.\n\nCR\n★TRUSTPILOT2025-12-10#6RATING 1/5\n\nI new here , but all my firends had great experience with this platform . They can make money\n\nZeinab Nematollahi\n★TRUSTPILOT2025-11-18#7RATING 1/5TEXT UNAVAILABLE\n\nNo text was included in the source record.\n\nEM\n★TRUSTPILOT2025-10-21#8RATING 1/5\n\nusing steam for over a decade and i have no words how good the platform is. some friends recommended it to me back in 2015 when we wanted to play csgo together and since then im loggin on it on a daily basis to check new games\n\nTrustpilot\n★TRUSTPILOT2025-05-09#9RATING 1/5\n\nSupport are never able to help you and only able to redicrect you to public linkBreaking there own TOSNot able to provider a refundNot able to provide a safe place for gamingBase on the game you play you can get scam.\n\nSym Link · 7 source copies\n★TRUSTPILOT2025-05-09#10RATING 1/5TEXT UNAVAILABLE\n\nNo text was included in the source record.\n\nHearnius\n★TRUSTPILOT2024-12-30#11RATING 1/5\n\nThis company allowed a single phishing scammer 76561199443342045 in 100's of its user community chat rooms \"Steam Chat\" the whole week of Winter Sales, 12-23-2024 - 2025 to spam spaceintrader a scam phishing website.Don't support Valve & Steam that support sca…\n\nFR · 7 source copies\n★TRUSTPILOT2024-11-15#12RATING 1/5\n\nVery realiable! Ive never had an issue over the 11 years ive had steam.\n\nJM\nA compilação e os seus ficheiros-fonte\n\nEste arquivo une as linhas duplicadas de 249 e exclui uma linha das entradas de 16,569, ficando com 16,319 registos distintos. Um registo pode descrever um evento já abrangido por outro registo. A pesquisa abrange títulos, autores, etiquetas de fonte e excertos apresentados; o texto completo guardado abre-se com cada registo.\n\nDescarregar quatro ficheiros de exportação de código-fonte ↓Número de ficheiros e hashes SHA-256 ↗Manifesto de compilação original ↗\n\nO pacote contém as exportações recuperadas que correspondem ao número de linhas da compilação e aos seus três caminhos JSON registados. A compilação original não registou os hashes de entrada nem um caminho CSV principal; o manifesto associado documenta os ficheiros recuperados e a comparação com o índice publicado.\n\nTrustpilot · steam_support_reviews.json354 linhas · exportação para JSON\nReddit · reddit_censored_forensics.json208 linhas · exportação para JSON\nGitHub · valve_ignored_bugs.json705 linhas · exportação para JSON; o nome do ficheiro corresponde a uma etiqueta do coletor\nMaster · TOTAL_VALVE_SCANDALS_MASTER_DB.csv15,302 linhas · exportação em CSV utilizada para comparação\nPautas dos tribunais · UNSEALED_EXHIBITS_AND_AML_DOSSIER.mdWolfire contra a Valve: e-mails divulgados, depoimentos de Gabe Newell, confissão de Oct2019relacionada com a AML\nDados Essenciais · FACTS_AND_CITATIONS_DATABASE.md1,638 citações verificadas e específicas em 35 sobre questões de concorrência e segurança\nArquivo de Suporte · support_canned_refusals.html1,505 registos de bilhetes · capturas de ecrã guardadas em 137 · pesquisa instantânea em tempo real\nCampos de registo, texto em falta e exportações sobrepostas\n\nAs datas, classificações, categorias e estados das publicações reproduzem as exportações da fonte. Um URL em falta continua em falta. Os marcadores «[removido]» ou «[eliminado]» não indicam quem removeu uma publicação nem porquê. O filtro Steam / Valve baseia-se na correspondência de texto, não numa avaliação de relevância.\n\nA opção «Exportar correspondências» descarrega entradas do índice com excertos; a opção «Descarregar registo» inclui o texto completo guardado. A opção separada 40,448-lista principal do CSV e 1,690-linha GitHub CSV O que importa nesta versão são as exportações mais abrangentes, e não o número de fontes.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam Arquivo de Provas — Documentos provenientes de «16,319»"
          },
          {
            "level": 2,
            "id": null,
            "text": "PLATAFORMA DE ORIGEM"
          },
          {
            "level": 2,
            "id": null,
            "text": "A compilação e os seus ficheiros-fonte"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/pt/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/pt/",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/TOTAL_VALVE_SCANDALS_MASTER_DB.csv",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive_manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive-inputs.zip",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive-inputs-manifest.json",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/unsealed_legal_and_aml/UNSEALED_EXHIBITS_AND_AML_DOSSIER.md",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/forensic_facts_1000/FACTS_AND_CITATIONS_DATABASE.md",
          "https://phishdestroy.io/steam_dossier/pt/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/github_valve_unpatched_bugs.csv"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/pt/steam_evidence_archive.content.json",
      "export_json_sha256": "b7f86f1231da0579016681a4de11d0354796a0cb8de09dbbf1ab89f6d532936f"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "pt/support_canned_refusals.html",
      "language": "pt",
      "title": "Steam Arquivo de recusas de apoio e respostas pré-definidas — O Dossiê «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/pt/support_canned_refusals",
      "source_html_sha256": "61cf2153fd31f40a6ecb46bc0c13eaa2ac0b10cbbfe93ad085b88546a35db5ee",
      "exported_at": "2026-09-29T00:18:16.266Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "support_canned_refusals.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/pt/support_canned_refusals.pdf?v=print-20260929-v5",
        "sha256": "19c0a5e0564b696112e0c3810f07e1ba49b14d2bffa76c3001dc543fd2c2949e",
        "bytes": 60403,
        "pages": 2
      },
      "integrity": {
        "signed_object": "support_canned_refusals.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "support_canned_refusals.content.json.asc",
        "digest_file": "support_canned_refusals.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify support_canned_refusals.content.json.asc support_canned_refusals.content.json",
          "sha256sum -c support_canned_refusals.content.json.sha256"
        ]
      },
      "content": {
        "text": "O QUE ESTA SECÇÃO DEMONSTRA\n\nEste repositório documenta 137 capturas de ecrã originais preservadas e 1,505 recursos das vítimas que foram auditados, detalhando o tratamento automatizado de pedidos de apoio pelo Valve. Isso comprova que, quando as contas são comprometidas através do redirecionamento do OpenID ou da geração não autorizada de chaves API, o Apoio ao Cliente Steam recorre sistematicamente a respostas padrão de recusa, sem qualquer investigação técnica. Ao recusar categoricamente a restauração de itens ou a divulgação de registos de auditoria, a plataforma transfere toda a responsabilidade pelas falhas estruturais de autenticação para os titulares das contas comprometidas.\n\nTodas as capturas de ecrã são imagens obtidas por terceiros. Os direitos de autor e o conteúdo pertencem aos respetivos autores e plataformas (utilizadores do Reddit, autores da comunidade Steam, avaliadores do Trustpilot, X e utilizadores do YouTube). São reproduzidas apenas para fins de identificação e reportagem de interesse público; não se reivindica qualquer direito de propriedade. Cada imagem inclui uma ligação para a sua fonte original.\n\nFigures reported on the source page\nMeasure\tReported value\tScope\nRegistos documentados\t1505\tRecursos de vítimas verificadas e tópicos sobre multas\nCapturas de ecrã guardadas\t137\tRegistos de capturas de bilhetes em alta resolução armazenados localmente\nTaxa de recuperação\t0.0%\tConcedidas revisões nos processos relativos aos sequestros de aviões deAPI\nDuplicação de modelos\t100%\tReutilização de scripts na íntegra entre os colaboradores (Ilya, Roger, Maverick)\nProvas forenses: os três pilares fundamentais da recusa de apoio\nPILAR 01 · ADMISSÃOAnexo R -014\nA Confissão de Roger: Confirmada a ataque MitM ao API\n\nNa resposta ao ticket n.º1cp582i, Steam, o colaborador do apoio ao cliente «Roger» admite por escrito que os atacantes cancelam transações legítimas através de API e as substituem por bots clonados em milésimos de segundo, mas recusa-se a restaurar os itens e diz à vítima para procurar um «técnico de informática local».\n\nConsultar a admissão por escrito ↗\nPILAR 02 · ESCALADAAnexo R —012\n7-Operação de dia: Manter a inércia\n\nUma vítima forneceu o SteamID64 das contas do hacker durante o período de retenção de transações diárias do 7-. Os membros da equipa de apoio «Artem» e «Ilya» recusaram-se a congelar os itens roubados, alegando a escassez de itens virtuais, e encerraram o ticket com um modelo automático.\n\nVerificar o histórico de vários funcionários ↗\nPILAR 03 · POLÍTICAAnexo R —002\nA escassez no mercado face aos direitos de propriedade\n\nA Política Oficial de Restituição de Itens do Valve estipula explicitamente que os itens não são devolvidos porque a sua restituição «reduziria a escassez e inflacionaria a economia, diminuindo o valor dos itens no Mercado Comunitário».\n\nCaptura de ecrã da política de inspeção ↗\nGénese histórica · 22 de março de 2018 para 2026\nAnexo H –003 · 8-Superfície de ataque sem correções anuais\nA primeira substituição comercial registada (22 de março de 2018)\n\nExatamente uma semana antes de a Valve ter imposto o seu controverso período de espera de 7-para a troca de itens do Counter-Strike, a comunidade de trocas descobriu os primeiros casos reais da Steam API Web: Exploração de redirecionamento de tráfego. Os atacantes deturparam sessões web para gerar uma chave não autorizada de «API» em steamcommunity.com/dev/apikey sem a confirmação da FA por 2móvel, o que permite que os bots cancelem e troquem transações em tempo real.\n\nAviso da campanha de sensibilização «2018» de março: «Os burlões conseguem detetar automaticamente esta oferta de troca e irão recusá-la na tua conta, porque têm a tua chave Steam API. O bot de burla irá agora enviar-te uma oferta de troca pelas mesmas skins... e tu nem vais notar a diferença!»\nPercurso das Evidências Históricas\n22 Mar2018: Primeira troca documentada de «API»\n2019: O suporte padroniza o bloqueio de «malware»\n2020: Script «Encerrar pedido de ajuda» reforçado\n2022–2026: Automatização de phishing com BitB e QR\nAbrir o tópico original do Reddit «2018» ↗\nPrimary sources\n\n137 gallery cards refer to 78 distinct primary URLs. Images and repeated exhibit captions are omitted from this reading edition.\n\nFull visual archive and original captures",
        "headings": [
          {
            "level": 2,
            "id": null,
            "text": "Figures reported on the source page"
          },
          {
            "level": 2,
            "id": null,
            "text": "Provas forenses: os três pilares fundamentais da recusa de apoio"
          },
          {
            "level": 3,
            "id": null,
            "text": "A Confissão de Roger: Confirmada a ataque MitM ao API"
          },
          {
            "level": 3,
            "id": null,
            "text": "7-Operação de dia: Manter a inércia"
          },
          {
            "level": 3,
            "id": null,
            "text": "A escassez no mercado face aos direitos de propriedade"
          },
          {
            "level": 3,
            "id": null,
            "text": "A primeira substituição comercial registada (22 de março de 2018)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Primary sources"
          }
        ],
        "links": [
          "https://www.reddit.com/r/csgo/comments/1cp582i/i_got_api_scammed_what_do_i_do_now/",
          "https://www.reddit.com/r/DotA2/comments/1e5ovy4/my_account_was_hacked_and_steam_support_refuse/",
          "https://www.reddit.com/r/Steam/comments/3b2abd/steam_will_no_longer_restore_scammed_items_item/",
          "https://www.reddit.com/r/GlobalOffensiveTrade/comments/863tk1/psa_urgent_huge_scam_happening_read_here_how_to",
          "https://phishdestroy.io/steam_dossier/pt/support_canned_refusals#gallery-grid"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/pt/support_canned_refusals.content.json",
      "export_json_sha256": "d4c09652f0a08bb2e94883590c2e54c0bdfa2c4b2a19ec27d591a96b52a7194c"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "pt/valve_scandals_registry.html",
      "language": "pt",
      "title": "Valve Registo de Escândalos — O Dossiê «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/pt/valve_scandals_registry",
      "source_html_sha256": "2372871f7ed01d63b1aa85cb961e57a3f39be618d8f3a5f84c49cc9c9b9c3950",
      "exported_at": "2026-09-29T00:18:16.492Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "valve_scandals_registry.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/pt/valve_scandals_registry.pdf?v=print-20260929-v5",
        "sha256": "8adcfab5b8536911d966ed43fc729e2d3711775191b5eded77c2726fc65b1c95",
        "bytes": 65508,
        "pages": 6
      },
      "integrity": {
        "signed_object": "valve_scandals_registry.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "valve_scandals_registry.content.json.asc",
        "digest_file": "valve_scandals_registry.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify valve_scandals_registry.content.json.asc valve_scandals_registry.content.json",
          "sha256sum -c valve_scandals_registry.content.json.sha256"
        ]
      },
      "content": {
        "text": "Arquivo principal de escândalos\nValve Registo Central de Escândalos — 160 Incidentes com fonte identificada\nSOURCE RECORDS (RAW): 11,768\n\nComunicado. Com fonte identificada. Ainda em aberto.\n\nO QUE ESTA SECÇÃO DEMONSTRA\n\nEste registo principal reúne registos primários verificados de forma independente pela 160, que detalham falhas persistentes da plataforma, relatórios da comunidade que foram removidos e falhas não resolvidas no apoio ao consumidor em todo o ecossistema da Valve. Abrangendo processos de litígio verificados no Trustpilot, tickets de problemas de segurança arquivados no GitHub e processos regulatórios, este registo evidencia falhas sistémicas recorrentes na recuperação de contas e na resolução de litígios com clientes.\n\n← Voltar ao resumo executivo\n\n160 registos recolhidos: uma operação de apoio avaliada pelas pessoas que a utilizaram, tópicos que deixaram de estar visíveis, falhas da plataforma registadas e não resolvidas, e os incidentes pelos quais a Valve já teve de responder. Nada aqui reflete a nossa opinião — cada linha inclui a sua fonte original. Abra uma e leia por si mesmo.\n\nRegistos de origem\n11,768\nEm todas as categorias\nFalhas da plataforma\n3,372\nFalhas na plataforma comunicadas pela comunidade\nTópicos censurados\n109\nPublicações do Reddit removidas pelo moderador\nReclamações relativas ao apoio ao cliente\n471\nReclamações verificadas no Trustpilot\nViabilidade da aplicação\nBloqueio do domínio do servidor de autenticação\n\nO bloqueio, ao nível do domínio, de hosts de autenticação OpenID é tecnicamente simples de implementar: assim que um recurso é impedido de ser redirecionado para um inSteam, os domínios de terceiros que atuam como proxies de autenticação para esse mesmo recurso podem ser filtrados pelo mesmo conjunto de regras. No dossiê principal é apresentada uma análise detalhada da viabilidade da implementação.\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\nVer a viabilidade da aplicação na documentação →\nCategoria: Reclamações ao Apoio ao Cliente da Trustpilot (Escaladas negativas filtradas)176 registos de origem correspondentes · duplicados ocultados\nConsumer Complaint2026-07-20\nAuthor: C***\n\nI’ve used Steam for years, but lately, their sales have really lost their edge. I was hoping to score some solid discounts, but many games still feel overpriced, even during sales. Plus, the support response times can be frustratingly slow when issues arise.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2026-07-20\nConsumer Complaint2025-05-09\nAuthor: S*** L***\n\nSupport are never able to help you and only able to redicrect you to public linkBreaking there own TOSNot able to provider a refundNot able to provide a safe place for gamingBase on the game you play you can get scam.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2025-05-09\nConsumer Complaint2024-12-30\nAuthor: F***\n\nThis company allowed a single phishing scammer 7656…2045 in 100's of its user community chat rooms \"Steam Chat\" the whole week of Winter Sales, 12-23-2024 - 2025 to spam spaceintrader a scam phishing website.Don't support Valve & Steam that support scams. Don't give your log in credentials to account hijacking scammers. This company also allows engagements of commercial advertising / spam for gambling in violation of its own Rules and Guidelines / Online Conduct. 7656…5023 proof - groups/deskinsfans key drop advertising, thanks TannerfromKD and Valve!*\"The Consumer Review Fairness Act (CRFA) protects people’s ability to share their honest opinions about a business’s products, services, or conduct, in any forum, including social media. The law protects a broad variety of honest consumer assessments, including online reviews, social media posts, uploaded photos, videos, etc. And it doesn’t just cover product reviews. It also applies to consumer evaluations of a company\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2024-12-30\nConsumer Complaint2024-07-31\nAuthor: A***\n\nhorrible company.randomly you get \"This account may have been accessed by someone else.\"this happened to me 3 times.the 3rd time they wanted a cd key.a spent useless cd key that nobody has any reason to keep laying around.i gave them the paypal bill for my first purchase back in 2015.i gave them a bill for my first phone number ever on the account.i still got the same email attached to the account.this company is literally a scam. nothing but a scam.they randomly claim you been accessed somewhere else and then require you to give them information no reasonable person would ever have, if not your done and have to rebuy everything.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2024-07-31\nConsumer Complaint2023-12-09\nAuthor: K***\n\nHad 288 euros in steam wallet, someone hacked my account even with two step verification, write a steam support for help but only answer was if something is spent in community market they can’t help.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2023-12-09\nConsumer Complaint2023-09-26\nAuthor: J***\n\nI was banned for saying \"Who let grandma on the PC\"and another for simply calling someone ignorant.Power tripping mods, devs who don't care, steam doesn't care. Yet allows racism/trolling/etc Fk steam, its a joke now.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2023-09-26\nConsumer Complaint2022-08-31\nAuthor: Anonymous\n\nSteam community is plain bad for a various reasons:1. Steam forums are a big mess, for example they allow users to post in any language and as result you get jumbled mess with posts in foreign languages together with English language posts. For example, If you check CS GO forums, you'll see half of posts are in Russian and half in English. I don't understand why such a big and international company would leave their forums so unorganized like that. All other normal companies have English only language allowed which is an international language and sometimes subforums for other languages like German, French and etc... so if French people want to post in French they go specifically in that sub-forum. But no, Steam doesn't care about this. Their forums is a one big mess.2. Moderation is biased and joke. I don't understand why such a big company like Steam can't afford to hire people for moderation and pay them. Instead they just recruit random people for moderation who do it for free and\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2022-08-31\nConsumer Complaint2022-05-28\nAuthor: J***\n\nThe login code never arrives. I hate Steam.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2022-05-28\nConsumer Complaint2021-11-08\nAuthor: N***\n\nThe service is terrible, I only signed up because I really like the game I wanted, but the rest is terrible, I hope to get something better soon.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-11-08\nConsumer Complaint2021-06-18\nAuthor: W***\n\nThey scam people for money, dont believe me? Read thisSource: Steam Subscribers/User Agreement NO GUARANTEESTO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, NEITHER VALVE NOR ITS AFFILIATES GUARANTEE CONTINUOUS, ERROR-FREE, VIRUS-FREE OR SECURE OPERATION AND ACCESS TO STEAM, THE CONTENT AND SERVICES, YOUR ACCOUNT AND/OR YOUR SUBSCRIPTION(S) OR ANY INFORMATION AVAILABLE IN CONNECTION THEREWITH.In short: You got a virus or your data leaked because of our software? Whoopsies we dont care, that isnt even legal or the last of their scammy stuff...\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-06-18\nConsumer Complaint2021-05-14\nAuthor: B***\n\nThe support is one of the worst I've ever seen.Useless support team.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-05-14\nConsumer Complaint2020-04-02\nAuthor: J***\n\nSteamcommunity has 15% fees, 15!!!!\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2020-04-02\nConsumer Complaint2020-03-27\nAuthor: H***\n\nWhat can I say? the support is one of the worst I've ever seen maybe the FUNCOM is much worse. If you tell the true on the steam forum you just got a BAN even if what you said did not violated the rules of the forum.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2020-03-27\nConsumer Complaint2018-03-16\nAuthor: B***\n\ndon't sign up will stick on your computer will kill your pc power you can't remove it from your pc even you deleted it will stay woking in the system\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2018-03-16\nConsumer Complaint2016-12-27\nAuthor: J***\n\nIn bloddy hate their page it's tiresome, it's in no way intuitive. I tried reaching out for support, but that is a maze.I'm simply trying to log in and redeem a key of a product I already bought, their search function is a joke. I f*u*c*k*i*n*g hate them. The layout is not like the how to video from the dealer, this can be done much simpler. I don't frigin care aboutn what other titles you have in store or what genre, I just want to redeem my key and install.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-12-27\nConsumer Complaint2016-10-28\nAuthor: P***\n\nSupport on site is terrible.Refunds not happend yet, despite games not working.No help at all if key is bought outside their system, so as a customer you can bounce back and through between bad support systems?? I wait for some other companies to compete in this market, for this can't be the best we as customers can expect.And do put an email up to find, instead of this stuppid website where you spend so long time trying to find a solution on, instead of a simple mail. Often the problem is not there, or if it's there just saying no help here???I need a response\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-10-28\nConsumer Complaint2016-06-26\nAuthor: V*** W***\n\nUseless support as always!\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-06-26\nConsumer Complaint2014-07-01\nAuthor: J***\n\nexpensive, and support team not willing to cooperate\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2014-07-01\nConsumer Complaint2014-04-15\nAuthor: B***\n\nWhen you pay for a program, you expect it too work. cant not buy or anything and have written to valve. but there is not a being done a damn thing abut it..\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2014-04-15\nConsumer Complaint2026-09-03\nAuthor: M***\n\nWorst platform ever wont give me a refund even though a game is unplayable because of bugs I won't ever be using the crap platform again I hope the platform breaks down for good piece fo crao\n\nTarget Domain: steamcommunity.com / steampowered.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2026-09-03\n\nNão foram encontrados registos correspondentes\n\nExperimente ajustar a sua pesquisa atual ou consultar um separador de categoria diferente.\n\n1 / 9",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Valve Registo Central de Escândalos — 160 Incidentes com fonte identificada"
          },
          {
            "level": 2,
            "id": null,
            "text": "Bloqueio do domínio do servidor de autenticação"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: C***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: S*** L***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: F***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: A***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: K***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: Anonymous"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: N***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: W***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: H***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: P***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: V*** W***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: M***"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/pt/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/pt/#proxy-bypass-explainer",
          "https://phishdestroy.io/steam_dossier/pt/#autoban-feasibility-section",
          "https://www.trustpilot.com/review/steamcommunity.com"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/pt/valve_scandals_registry.content.json",
      "export_json_sha256": "f44c60c6ddb12de1a5fae1ab51f7b048c5a6c427c8ce12fa5cbb61c56da65723"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "pt/output_steam_network/index.html",
      "language": "pt",
      "title": "Arquitetura, não exploração: A Rede de Automatização — O Dossiê «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/pt/output_steam_network/index",
      "source_html_sha256": "141a1f036f56d60ab1f59b55a4bd079f54c1dcacaf89cad6a2d26a3e8e1a1c50",
      "exported_at": "2026-09-29T00:18:16.637Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__index.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/pt/output_steam_network__index.pdf?v=print-20260929-v5",
        "sha256": "53cee64b3ff70659c090ba94ceaf406408e3459e2dcf1ea0fd84c775d0fddda2",
        "bytes": 68237,
        "pages": 3
      },
      "integrity": {
        "signed_object": "output_steam_network__index.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__index.content.json.asc",
        "digest_file": "output_steam_network__index.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__index.content.json.asc output_steam_network__index.content.json",
          "sha256sum -c output_steam_network__index.content.json.sha256"
        ]
      },
      "content": {
        "text": "Anexo VII · Análise da Arquitetura Técnica\nSteam Arquitetura de rede — Fidelidade ao protocolo e análise do ecossistema\n\nA automatização é a base da arquiteturValve. Não é uma falha de segurança.\n\nO QUE ESTA SECÇÃO DEMONSTRA\n\nEste módulo mapeia a topologia técnica dos repositórios de desenvolvedores de 252, dos perfis de 3,320 GitHub e dos pares de colaboradores de 4,214 que sustentam o ecossistema de automação de Steam. Demonstra que a automação de terceiros se baseia no protocolo oficial Connection Manager da Valve, nos esquemas Protobuf e nas APIs Web, sem código de exploração. Ao desenvolver tokens de confirmação algorítmicos Steam Guard e cobrar taxas mínimas de transação até 66.7%,, o Valve funciona como o arquiteto intencional e principal beneficiário comercial das operações automatizadas do ecossistema.\n\n← Voltar ao resumo executivo\n\nQuando a Valve se dirige a entidades reguladoras, processadores de pagamentos ou vítimas de burlas, atribui o roubo de identidades e a manipulação do mercado a «explorações não autorizadas por terceiros» e a «automatização ilícita e desonesta». A realidade técnica desta rede de repositórios 252-demonstra exatamente o contrário: Todas as plataformas de automatização, bots de negociação e frotas de «farming» operam estritamente de acordo com as definições oficiais do protocolo, as APIs Web e os mecanismos de autenticação concebidos, documentados e monetizados pela Valve Corporation.\n\nConclusão forense: Arquitetura consciente vs. Violação ilegítima\n\nO software analisado neste módulo — incluindo SteamKit, node-steam-user, ValvePython/steam, e ArchiSteamFarm — contém zero vulnerabilidades de software, zero corrupções de memória e zero explorações de dia zero. Trata-se de implementações de código aberto, limpas e robustas do protocolo de cliente proprietário Connection Manager (CM) dValve, dos Google Protocol Buffers (Protobufs) e das APIs da Web. A Valve concebeu estas APIs para aceitar inícios de sessão programáticos e criou o Steam Guard para permitir tokens de confirmação algorítmicos (identity_secret), e cobra uma taxa anunciada de 15% que aumenta até até 66.7% a favor de Valve nas transações de alta velocidade e nas vendas em massa de produtos básicos que as botnets automatizadas liquidam.\n\nPilar 01 · Fidelidade ao Protocolo\nEsquemas oficiais do Protobuf\n\nAs bibliotecas de automatização não contornam as barreiras de segurança. Elas serializam mensagens Protobuf oficiais (steammessages_clientserver.proto) através de TCP/WebSockets diretamente para os clusters CM oficiais do Valve, exatamente como faz o cliente Steam.\n\nPilar 02 · Algorítmica 2FA\nAutorização de Negociação Programática\n\nToda a economia de comércio de skins, que movimenta vários milhares de milhões de dólares, depende de «Valve» IEconService API e chaves TOTP de autenticação móvel. A Valve concebeu intencionalmente o Steam Guard para permitir confirmações de transações entre máquinas.\n\nPilar 03 · Beneficiário comercial\nTráfego gerado por máquinas monetizado: até um valor mínimo de comissão de66.7%\n\nValve Anuncia uma comissão de 15%, mas nos artigos de grande volume que os bots automatizados negociam — cartões colecionáveis, caixas e artigos baratos com preços entre $0.03 e $0.05 — a comissão mínima de dois cêntimos da Valve ($0.01Steam + $0.01 publisher) retira 50% 66.7% a favor de Valve (2¢ retirados de um cartão 3¢, deixando o vendedor com 1¢). Além disso, $5.00 por conta ($26.8M só na frota digitalizada).\n\nMódulo 01 · Evidências relativas ao repositório e ao protocolo\nInfraestrutura pública de desenvolvimento e repositórios\n\nCatálogo forense detalhado de 252 repositórios de código aberto que sustentam a automação de Steam. Explica como as ferramentas padrão de engenharia de software implementam os pontos de extremidade API publicados por Valve sem recorrer a exploits.\n\n252Repositórios\n4,554Links relacionados com funções\nAnalisar as provas do repositório →Módulo 02 · Demografia dos ecossistemas\nMétricas do ecossistema global de engenharia\n\nDistribuição geográfica e institucional dos engenheiros de software da «3,320» que contribuem para o ecossistema de automação «Steam», incluindo as afiliações empresariais às principais empresas do setor tecnológico.\n\n3,320Engenheiros\n98,902Par de ligações\nAnalisar os indicadores do ecossistema →Módulo 03 · Gráfico visual interativo\nGráfico interativo do protocolo e da rede de programadores\n\nMapeamento abrangente, em forma de gráfico de rede interativo, de repositórios do Vis.js, bibliotecas de protocolos (SteamKit, Steamworks, ASF) e sobreposições de colaboradores entre projetos. Demonstra visualmente a arquitetura de software de código aberto legítima e interligada que sustenta o ecossistema de automação do Steam.\n\nInterativoVis.js Motor\nIsolamento de clustersPesquisa em tempo real\nSem vulnerabilidadesAPIs padrão\nAbrir gráfico de rede interativo →\nContexto regulamentar e jurídico (artigo da GDPR 25 e proteção do consumidor):\nDe acordo com o princípio da «Proteção de Dados desde a Conceção e por Predefinição», uma arquitetura de plataforma que permita a geração silenciosa de chaves «API», o cancelamento de transações sem notificação prévia e a liquidação automatizada de ativos por sistemas é uma escolha arquitetónica do operador da plataforma. Quando a Valve rejeita sistematicamente os pedidos de reembolso dos consumidores, alegando que as perdas foram causadas por «ataques cibernéticos externos», oculta o facto de que o vetor de ataque é a própria arquitetura Web API da Valve, concebida intencionalmente.\n\nVISUALIZAÇÃO INTERATIVA\n\nEstá disponível uma visualização interativa completa do repositório «252-», 3,320-, do gráfico da rede de programadores, em network.html. As métricas agregadas encontram-se no Métricas de BI página.\n\nO Dossiê «Steam» · Arquivo de Arquitetura Técnica · Registos de Código Aberto · Todos os direitos cedidos à humanidade.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam Arquitetura de rede — Fidelidade ao protocolo e análise do ecossistema"
          },
          {
            "level": 3,
            "id": null,
            "text": "Esquemas oficiais do Protobuf"
          },
          {
            "level": 3,
            "id": null,
            "text": "Autorização de Negociação Programática"
          },
          {
            "level": 3,
            "id": null,
            "text": "Tráfego gerado por máquinas monetizado: até um valor mínimo de comissão de66.7%"
          },
          {
            "level": 2,
            "id": null,
            "text": "Infraestrutura pública de desenvolvimento e repositórios"
          },
          {
            "level": 2,
            "id": null,
            "text": "Métricas do ecossistema global de engenharia"
          },
          {
            "level": 2,
            "id": null,
            "text": "Gráfico interativo do protocolo e da rede de programadores"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/pt/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/pt/output_steam_network/valve_ru_farming_isolated.html",
          "https://phishdestroy.io/steam_dossier/pt/output_steam_network/steam_ecosystem_dashboard.html",
          "https://phishdestroy.io/steam_dossier/pt/output_steam_network/network.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/pt/output_steam_network__index.content.json",
      "export_json_sha256": "156712aa9b9b599906b0099852bb3b1e23c3f34e1001c525342183058d0afd28"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "pt/output_steam_network/network.html",
      "language": "pt",
      "title": "Explorador de programadores e repositórios — O Dossiê «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/pt/output_steam_network/network",
      "source_html_sha256": "d67701842436508e6bc5a2495b0a192efb1e37d57e12bfc94ed738ebb00bd5b4",
      "exported_at": "2026-09-29T00:18:18.628Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__network.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/pt/output_steam_network__network.pdf?v=print-20260929-v5",
        "sha256": "b7e0811df97f2a54f0c5847c0d153485cdbe3bea2e1f693a594601bcc3b5a56b",
        "bytes": 35770,
        "pages": 1
      },
      "integrity": {
        "signed_object": "output_steam_network__network.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__network.content.json.asc",
        "digest_file": "output_steam_network__network.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__network.content.json.asc output_steam_network__network.content.json",
          "sha256sum -c output_steam_network__network.content.json.sha256"
        ]
      },
      "content": {
        "text": "Explorador de programadores e repositórios\n\nPesquisar um nó. Analisar a relação registada.\n\nREGISTROS PÚBLICOS / LIGAÇÕES RECOLHIDAS\nPesquisa em tempo real\nCamadas de filtro\nTotal de programadores3,320\nTotal de repos252\nGRÁFICO APRESENTADO / SUBCONJUNTO DA COLEÇÃO468 NÓS • 1103 ARESTAS\nRegisto de perfil selecionado\n\n💡 Clique em qualquer nó do gráfico ou escreva na barra de pesquisa para analisar as ligações recolhidas e os percursos de origem desse nó.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Explorador de programadores e repositórios"
          }
        ],
        "links": []
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/pt/output_steam_network__network.content.json",
      "export_json_sha256": "ebddda1f133c411f832b04b785728aaa5b6f479ce68b8817cb2a120e6952f2e5"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "pt/output_steam_network/steam_ecosystem_dashboard.html",
      "language": "pt",
      "title": "A rede «The Collected» em números — O Dossiê «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/pt/output_steam_network/steam_ecosystem_dashboard",
      "source_html_sha256": "ddc02d913c17b02a1e2acb9fee57face9ae31a0af4b6e4c69396210febdda86b",
      "exported_at": "2026-09-29T00:18:18.210Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__steam_ecosystem_dashboard.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/pt/output_steam_network__steam_ecosystem_dashboard.pdf?v=print-20260929-v5",
        "sha256": "dc6917dcf5c62d85d46827c95c8cdce844e58c1aefa9fae68b067e3ca9a5c825",
        "bytes": 40040,
        "pages": 2
      },
      "integrity": {
        "signed_object": "output_steam_network__steam_ecosystem_dashboard.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__steam_ecosystem_dashboard.content.json.asc",
        "digest_file": "output_steam_network__steam_ecosystem_dashboard.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__steam_ecosystem_dashboard.content.json.asc output_steam_network__steam_ecosystem_dashboard.content.json",
          "sha256sum -c output_steam_network__steam_ecosystem_dashboard.content.json.sha256"
        ]
      },
      "content": {
        "text": "VISÃO GERAL DAS ESTATÍSTICAS // ARQUIVO 02\nSteam Painel do Ecossistema — A Rede em Números\n\nA rede, em números.\n\nO QUE ESTA SECÇÃO DEMONSTRA\n\nEste painel agrega informações estruturais sobre os programadores d3,320 e os repositórios d252, identificando 68 bases de código específicas para jogos de azar e pontes de ligação entre plataformas. Os dados empíricos destacam a concentração geográfica e as sobreposições entre programadores, demonstrando que a infraestrutura de jogos de azar de terceiros funciona como uma indústria de software organizada e altamente interligada, integrada à plataforma dSteam.\n\n← Voltar ao resumo executivo\n\nEstatísticas consolidadas da base de dados da investigação: distribuição geográfica, principais empresas, repositórios de apostas com skins e pontes de ligação ativas.\n\nScanned Devs3320\nTotal de repos252\nRepos de jogos de azar68\nTotal de ligações1,426\nEstrutura e Setores da Automatização\nSetor I — Núcleo da Corporação «Valve»\n\nRepositórios oficiais e software de sistema. Espaço de desenvolvimento confirmado dos colaboradores do Valve, Nephyrin e Joe Ludwig.\n\nSetor II — Mecanismos de autorização e emuladores de protocolo (SteamKit)\n\nBibliotecas de rede criadas por engenharia inversa, de autoria conjunta de Nephyrin, do site Valve, e do DoctorMcKay, programador de jogos de apostas com skins.\n\nSetor III — Clientes de «card farming» (ArchiSteamFarm)\n\nUtilizar emuladores do protocolo SteamKit para executar milhões de clientes falsos (em modo inativo) em segundo plano, com o objetivo de acumular cartas colecionáveis.\n\nGeografia dos programadores\nAlemanha57\nEstados Unidos52\nCanadá48\nReino Unido44\nPolónia30\nFrança28\nFederação Russa27\nChina27\nEUA (Estado de Washington)23\nAustrália19",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam Painel do Ecossistema — A Rede em Números"
          },
          {
            "level": 3,
            "id": null,
            "text": "Setor I — Núcleo da Corporação «Valve»"
          },
          {
            "level": 3,
            "id": null,
            "text": "Setor II — Mecanismos de autorização e emuladores de protocolo (SteamKit)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Setor III — Clientes de «card farming» (ArchiSteamFarm)"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/pt/#briefing-heading"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/pt/output_steam_network__steam_ecosystem_dashboard.content.json",
      "export_json_sha256": "a2b5be089c0f393ec292a950b8ffe0198e597d8dd4a0d7240908aba188fd707a"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "pt/output_steam_network/valve_ru_farming_isolated.html",
      "language": "pt",
      "title": "Código, colaboradores e forks — O Dossiê «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/pt/output_steam_network/valve_ru_farming_isolated",
      "source_html_sha256": "6dda44642d139a9ac418150b37b0981f5ec749079c452282f05e0caa7008d888",
      "exported_at": "2026-09-29T00:18:19.025Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__valve_ru_farming_isolated.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/pt/output_steam_network__valve_ru_farming_isolated.pdf?v=print-20260929-v5",
        "sha256": "a136ec3a86c34c58e4c200e35bd1a1f06bc7a3421468ef1e45ba983ec34d3568",
        "bytes": 42539,
        "pages": 2
      },
      "integrity": {
        "signed_object": "output_steam_network__valve_ru_farming_isolated.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__valve_ru_farming_isolated.content.json.asc",
        "digest_file": "output_steam_network__valve_ru_farming_isolated.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__valve_ru_farming_isolated.content.json.asc output_steam_network__valve_ru_farming_isolated.content.json",
          "sha256sum -c output_steam_network__valve_ru_farming_isolated.content.json.sha256"
        ]
      },
      "content": {
        "text": "PARTE II / ACOMPANHE A RELAÇÃO DOCUMENTADA\n\nOs «forks», as contribuições e as dependências de software constituem provas distintas. Esta perspetiva preserva as funções identificadas; no entanto, o emprego, as violações de segurança e o envolvimento em atividades criminosas exigem fontes adicionais.\n\nAbrir o mapa interativo de capacidades ↗\nFONTES PÚBLICAS / AUDITORIA DE FUNÇÕES\nO código. Os colaboradores. Os forks.\n1. Nephyrin: bifurcações e contribuições\n\nO instantâneo fornecido identifica o Nephyrin como colaborador do ValveSoftware/Proton e criador de ramificações do SteamRE/SteamKit e do SteamRE/open-steamworks. Os dados do seu perfil indicam «Valve Software». Estes campos devem ser interpretados separadamente.\n\nUm fork cria uma cópia do repositório. Esta exportação não inclui um commit que registe alterações no código de autenticação do SteamKit.\nReferências do repositório / consultar o histórico\nSteamRE/SteamKit ↗ SteamRE/open-steamworks ↗\n2. Funcionalidades públicas: automatização sem o cliente de secretária\n\nO SteamKit e o node-steam-user permitem interações programáticas com o Steam. O ArchiSteamFarm documenta a criação de contas múltiplas para aquisição de cartões e declara o SteamKit2 como uma dependência.\n\nTrata-se de capacidades concretas de automatização. A execução sem interface não implica uma utilização comercial exclusiva nem contorna a proteção «Steam». As questões relevantes são a credencial solicitada, as ações que esta permite realizar e os controlos aplicados pela plataforma.\n\nFonte: ficheiros README dos projetos e ArchiSteamFarm.csproj. O mapa de capacidades inclui ligações para cada dependência documentada.\n3. JoeLudwig: a designação de colaborador do hl2sdk\n\nO instantâneo indica JoeLudwig como colaborador dos projetos alliedmodders/hl2sdk, ValveSoftware/openvr e ValveSoftware/source-sdk-2013. Trata-se de uma relação observável entre projetos. A exportação não fornece provas que liguem uma alteração específica do SDK a um roubo ou à implementação de jogos de azar.\n\nReferências do repositório / consultar o histórico\nalliedmodders/hl2sdk ↗ DoctorMcKay/node-steam-user ↗\nESQUEMA LÓGICO // TRAÇADOS\nFluxograma da lógica de ligação:\nPERFIL RELACIONAMENTO\nNephyrin / perfil compilado\nColaborador: Proton. Autores do fork: SteamKit e open-steamworks.\n▼ Relação de bifurcações recolhidas\nBIBLIOTECA COMUNITÁRIA\nSteamRE/SteamKit\nBiblioteca de rede pública Steam mantida pela organização SteamRE.\n▼ Dependência do SteamKit2 declarada\nAUTOMAÇÃO DOCUMENTADA\nJustArchiNET/ArchiSteamFarm\nDocumenta a prática de «card farming» em várias contas e uma dependência do SteamKit2.\nANÁLISE DE EVIDÊNCIAS / RESUMO DA FONTE\nREGISTRADO: rótulos distintos para colaboradores e criadores de bifurcações.\nCOMPROVADO: as bibliotecas públicas promovem interações programáticas Steam.\nPERGUNTA EM ABERTO: a autoria específica do código, a aprovação da plataforma e a atribuição da responsabilidade pelo abuso requerem provas distintas.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "O código. Os colaboradores. Os forks."
          },
          {
            "level": 2,
            "id": null,
            "text": "1. Nephyrin: bifurcações e contribuições"
          },
          {
            "level": 2,
            "id": null,
            "text": "2. Funcionalidades públicas: automatização sem o cliente de secretária"
          },
          {
            "level": 2,
            "id": null,
            "text": "3. JoeLudwig: a designação de colaborador do hl2sdk"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/pt/investigation_part2.html#automation-map",
          "https://github.com/SteamRE/SteamKit",
          "https://github.com/SteamRE/open-steamworks",
          "https://github.com/alliedmodders/hl2sdk",
          "https://github.com/DoctorMcKay/node-steam-user"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/pt/output_steam_network__valve_ru_farming_isolated.content.json",
      "export_json_sha256": "c083b6021ffce1deda9ddfe7bdc5a733163852602a27e7d9b0939a778a2388c8"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "nl/card_economy.html",
      "language": "nl",
      "title": "De kaarteconomie — Het Steam-dossier",
      "source_url": "https://phishdestroy.io/steam_dossier/nl/card_economy",
      "source_html_sha256": "69f4afb3b87f6d2abdb701a39200f9c004ed4aacba88a4c84bd11f664f6ba056",
      "exported_at": "2026-09-29T00:18:21.079Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "card_economy.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/nl/card_economy.pdf?v=print-20260929-v5",
        "sha256": "fc496ee4f537e0e660686c005520af16d1964b611e5482877d91daab6b80758d",
        "bytes": 257839,
        "pages": 25
      },
      "integrity": {
        "signed_object": "card_economy.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "card_economy.content.json.asc",
        "digest_file": "card_economy.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify card_economy.content.json.asc card_economy.content.json",
          "sha256sum -c card_economy.content.json.sha256"
        ]
      },
      "content": {
        "text": "BIJLAGE V — DE KAARTECONOMIE\nEen botfarm is geen lek in de winkel van Valve. Het is een klant.\n\nEen Steam-account kan geen enkele ruilkaart ontvangen totdat er geld is uitgegeven $5.00 in de winkel. Het kan geen spel ‘farmen’ dat het niet bezit, en evenmin een spel dat het gratis heeft gekregen. Dus voordat een geautomatiseerde kaartfarm überhaupt iets produceert, heeft het zich toegang gekocht — per account, tegen een prijs die Valve bekendmaakt. Vervolgens wordt in de automatiseringsclausule van Valve regel voor regel precies vermeld wat die farm produceert; de licentie verbiedt elke manier waarop een verkregen kaart in geld wordt omgezet; en de markt neemt een deel van de opbrengst wanneer de kaart toch wordt verkocht — geadverteerd bij 15%, maar met een minimum van twee cent per verkoop, wat bij een kaart die in cent wordt geprijsd het grootste deel van de prijs uitmaakt. Dit overzicht laat zien hoe groot die handel is, wat het hoogste niveau van een profiel in sets kost, en wat de handhavingsafdeling van Valve met dezelfde clausule doet wanneer het account van een gewone handelaar is.\n\nWat een boerderij als eerste moet aanschaffenWat een niveau kost in setsBeide kanten van het bureauWie houdt toezicht op de kaarteconomie?\n$5.00Er moet eerst een bedrag in de winkel zijn uitgegeven voordat een account een kaart kan ontvangen — de eigen ondersteuningspagina van Valve\n13,876Spellen op Steam waarin ruilkaarten worden uitgegeven en waarin 99,971 verschillende soorten kaarten voorkomen\n694,673Volledige kaartensets die momenteel op voorraad zijn bij 91 beursgenoteerde handelsbots\n1,389,346De toegestane hoeveelheden account- en spelkaarten die de voorraad al heeft verbruikt, als minimum\n$9.99Mediaanprijs van een kaartspel — de complete set wordt verkocht voor een mediaanprijs van $0.74\n97,114Leden van de kaartruilgroep waarvan de lijst met moderators een medewerker met het nummer Valve bevat — § 08\n01 — Het proces\nWat een boerderij eigenlijk is, stap voor stap\n\nDit is uitsluitend gebaseerd op de documentatie van het programma zelf en de ondersteuningspagina’s van Valve. Niets in dit gedeelte is afgeleid, en geen van beide partijen betwist de inhoud ervan.\n\nStap 1\nInkopen\n\nHet account mag niet beperkt. De ondersteuningspagina van Valve verbiedt gebruikers met beperkte accounts om \"Deelnemen aan de Steam-markt\", uit \"Ruilen Steam Community-items (ruilkaarten, boosterpacks, edelstenen, enz.)\" en van \"Steam profielniveaus behalen (vastgezet op niveau 0) en ruilkaarten\". De poort is geld: \"Je moet ten minste $5.00 USD uitgeven in de Steam-winkel.\"\n\nStap 2\nGames kopen\n\nKaarten kun je alleen verkrijgen uit spellen die je bezit. \"Je moet de game op je Steam-account in je bezit hebben om in aanmerking te komen voor eventuele kaartdrops uit die game. Family Sharing geldt niet als eigendom en telt dus niet mee.\" Ook de vrije routes zijn afgesloten: \"Betaalde spellen die je tijdens een actie gratis hebt gekregen, kun je niet gebruiken om kaarten te verzamelen\", en \"Je kunt geen kaarten uit F2P-spellen krijgen zonder daar geld aan uit te geven.\"\n\nStap 3\nInactief\n\nDe tool logt het account zonder gebruikersinterface in op het Steam-netwerk, \"analyseert je badges\", stelt de lijst met titels samen die je kunt spelen en start \"de in aanmerking komende game spelen en regelmatig controleren of de game al volledig is uitgespeeld.\" De beschrijving van het mechanisme door de beheerder: het \"doet niets anders dan Steam laten weten dat we een bepaald spel spelen.\"\n\nStap 4\nDe druppels raken op\n\nElke titel is eindig. \"Elke game heeft een vast aantal kaarten dat je kunt vinden. Zodra je ze allemaal hebt gevonden (ongeveer de helft van de volledige set), is de game niet langer geschikt om te 'farmen'.\" Een boerderij die wil blijven produceren, moet steeds nieuwe kaarten blijven kopen. Het aanbod aan kaarten wordt beperkt door aankopen — dit is zo ontworpen en speelt in het voordeel van Valve.\n\nStap 5\nUitbetalen\n\nDe kaart verlaat het spel via een van de drie mogelijkheden: ze wordt verkocht op de Community Market, geruild of verwerkt tot edelstenen. Elk van deze opties is een transactie op de Subscription Marketplace of een ruil, en § 3.D behoudt zich het recht voor om: \"Valve kan een vergoeding in rekening brengen voor transacties op een abonnementsmarktplaats.\" Dit is de stap waardoor het geheel een inbreuk vormt — zie 05.\n\nBronnen, letterlijk overgenomen en geciteerd op 2026-09-22: Steam Ondersteuning — Beperkte gebruikersaccounts ↗ · ArchiSteamFarm Veelgestelde vragen ↗ · Valve — Steam Veelgestelde vragen over ruilkaarten ↗ · Steam Abonnementsovereenkomst ↗ gearchiveerd 2026-09-24 ↗. ArchiSteamFarm wordt op deze pagina overal gebruikt als meetinstrument, niet als verdachte; in de bijbehorende documentatie staat duidelijk vermeld dat \"ASF is niet erkend door Valve\".\n\n02 — De schaal\nVoordat een boerderij ook maar een cent verdient, heeft ze al Valve betaald\n\nAangezien een account met beperkte rechten geen kaart kan ontvangen, moet de status ‘beperkt’ van elk account binnen een farm worden opgeheven voordat het iets kan produceren. De drempelwaarde wordt bekendgemaakt en de kosten worden per account in rekening gebracht.\n\nGrootte van het landbouwbedrijf\tWaar komt dat getal vandaan?\tMinimale besteding in de winkel om in aanmerking te komen voor de kaart\n10 accounts\tHet maximum dat ASF aanbeveelt — \"op basis van interne Valve-richtlijnen en onze eigen aanbevelingen\"\t$50\n100–200 accounts\tTechnisch plafond in dezelfde FAQ: \"Je kunt tot 100-200 bots draaien met één IP-adres en één ASF-instantie\"\t$500 – $1,000\n120 accounts\tHandhavingszaak 3 hieronder — definitief uitgesloten\t$600\n170 accounts\tHandhavingszaak 2 hieronder — permanent uitgesloten tijdens de Winteruitverkoop van 2017\t$850\n1,000 rekeningen\tHandhavingszaak 1 hieronder — handel verboden\t$5,000\n5,000 rekeningen niet geverifieerd\tWeegschaal voor bedieners in het kader van dit onderzoek gemeld en niet onafhankelijk gecontroleerd — zie de opmerking over de herkomst\t$25,000\n10,000 rekeningen niet geverifieerd\tWeegschaal voor bedieners in het kader van dit onderzoek gemeld en niet onafhankelijk gecontroleerd — zie de opmerking over de herkomst\t$50,000\n\nDe laatste twee rijen zijn de enige cijfers op deze pagina die zijn gebaseerd op een niet-geverifieerd rapport in plaats van op een document — ze zijn in de tabel gemarkeerd en worden toegelicht in de toelichting over de herkomst, en verder hangt hier niets van af. De rechterkolom betreft berekeningen op basis van de door Valve gepubliceerde drempel van $5.00 USD, en verder niets. Het is een vloer, geen schatting van wat een boerderij kost of van wat Valve heeft opgebracht: de games zijn hierin niet meegerekend – deze moeten in bezit zijn en mogen niet gratis zijn verkregen via een promotie – en ook de ongeveer 15% die de Community Market in rekening brengt bij de verkoop van de kaarten is hierin niet meegerekend. Op deze pagina wordt geen omzetcijfer vermeld.\n\nEn Valve heeft zelf een kaartdrop geprijsd. In de FAQ over ruilkaarten wordt het conversiepercentage voor de gratis-te-spelen-versie in gewone dollars weergegeven:\n\n\"Bij gratis te spelen games worden spelkaarten vrijgespeeld op basis van je in-game aankopen.\" Voor elke $9 USD die wordt uitgegeven (bij benadering) \"Sinds de start van de Steam Trading Card Beta verdien je één kaart.\"\n\n— Valve, Steam Veelgestelde vragen over ruilkaarten ↗ · woordelijk geverifieerd 2026-09-22\n\nEen ruilkaart is geen gratis geschenk waar het platform geld op verliest. Het is iets dat Valve verkoopt, tegen een door Valve gepubliceerde prijs — en waarvoor vervolgens nogmaals kosten in rekening worden gebracht bij de doorverkoop. Daarom is de eerlijke omschrijving van een ‘kaartboerderij’ niet parasiet. Het is groothandelsinkoper.\n\nHoe groot het te kopen voorwerp eigenlijk is\n\nAlles vanaf hier tot het einde van dit gedeelte is gemeten, niet gerapporteerd. De kaarttelling is gebaseerd op Steam, de gepubliceerde prijslijst voor badges van Card Exchange; de prijzen van de spellen zelf zijn afkomstig uit de eigen winkel-API van Valve; de botvoorraad is afkomstig uit een openbare botdirectory die iedereen kan raadplegen. Alle drie zijn ingelezen op 2026-09-22 en de berekeningen worden volledig weergegeven in paragraaf 08.\n\n13,876Spellen waarbij kaarten worden uitgedeeld\n99,971Verschillende soorten kaarten\n5 · 6 · 15Kaarten per set: min., mediaan, max.\n$0.74Mediaanprijs van een complete set\n$23,586.57Eén exemplaar van elke set is op de markt verkrijgbaar\nHoe groot is een set?\n\n13,876 spellen met kaarten uit de set. Valve zet ongeveer de helft daarvan op één willekeurig account.\n\n0\n1,250\n2,500\n3,750\n5,000\n5\n6\n7\n8\n9\n10\n11\n12\n13\n14\n15\nWat de licentie kost\n\nDe catalogusprijs van dezelfde games in de winkel van Steam, in Amerikaanse dollars.\n\n0\n1,000\n2,000\n3,000\n4,000\n<$1\n$1-3\n$3-5\n$5-10\n$10-20\n$20-40\n$40+\nWat de voltooide set oplevert\n\nMarktprijs van de complete set voor dezelfde spellen.\n\n0\n1,500\n3,000\n4,500\n6,000\n<$0.50\n$0.50-1\n$1-2\n$2-5\n$5-10\n$10+\n\nAls je de tweede en derde grafiek naast elkaar bekijkt, wordt de structuur van de transacties zichtbaar zonder dat je hoeft te rekenen: de spellen zitten allemaal in de tientallen dollars, terwijl de sets die ze opleveren allemaal onder de één dollar liggen. Beide zijn tellingen van dezelfde 13,876 spellen, op dezelfde as-eenheid, dus de vergelijking gaat tussen twee hoogtes en niet tussen twee schalen.\n\nDat is de aanbodzijde. De vraagzijde is het deel waarvoor Valve geen reclame hoeft te maken, omdat het al openbaar is: één enkele open lijst van botten voor het ruilen van kaarten bevat Er zijn op dit moment 91 bots die 694,673 complete sets op voorraad hebben. Geen inloggegevens, geen scraping van een marktplaats, geen persoonlijke gegevens — het voorraadcijfer staat op de pagina naast de naam van elke bot vermeld.\n\nMaak van die voorraad de enige eenheid die hier telt. De eigen regel van Valve: \"Bij de meeste spellen worden er ongeveer evenveel kaarten gelegd als de helft van het aantal kaarten in de kaartset van dat spel… Je moet de andere helft van de set bij andere leden van de community verzamelen.\" Eén account kan een set nooit voltooien door te spelen. Er zijn er minimaal twee nodig, die elk dat spel bezitten en elk hun recht op één ‘drop’ per spel opgebruiken. ‘Drops’ worden niet opnieuw aangevuld.\n\n694,673Sets op voorraad, 91 openbare bots\n3,473,365Kaarten, bij een vastgesteld minimum van 5 kaarten\n1,389,346Verbruikte druppelvergoedingen, minimum\n2,602Accounts met slechts één spel, de hoogste botdichtheid\nWaar de 694,673-sets staan\n\nDe twaalf grootste van de 91 beursgenoteerde kaartbots, gerangschikt op basis van het aantal complete sets in voorraad. De tien grootste hebben samen 248,115 sets in bezit — 35.7% van alles wat op het bord staat.\n\n0\n11,250\n22,500\n33,750\n45,000\nCard Supply #4 (High)\nN!vq's Leveling (High)\nAlice [BOT] LEVEL-UP RARE SETS\nN!vq's Leveling (Low)\nDisco Lite Level Up\nN!vq's Leveling (Mid)\nbaty131store.net | Level Up\nKitten - Supreme\nArashirn | Level Up\nSH (Junior) Level Up\nDuobot.com - Overstock\nlvlupbot.com - godlike\n\nElk van die 1,39 miljoen toewijzingen behoorde toe aan een account dat eigenaar was van het spel, de $5.00-drempel had overschreden en die drops nooit meer kan genereren. Dit is onverkochte voorraad op 91 bots. Het is geen maatstaf voor de markt; het is een maatstaf voor wat er na de markt overblijft.\n\nHet laatste cijfer is een indeling in categorieën, geen telling van het aantal gebruikers. Eén bot vermeldt 14,310 sets uit slechts 11 spellen, dus ten minste één van die spellen wordt vertegenwoordigd door 1,301 sets, wat neerkomt op ten minste 2,602 verschillende accounts die elk dat spel hebben gekocht. Dit is het kleinste getal dat de rekensom toelaat, en het betreft één bot op de eenennegentig.\n\nWat deze vloer wel en niet zegt\n\nDeze bots kopen kaarten van zowel gewone spelers als van ‘farms’ — hun gepubliceerde aankooptarieven vormen de kern van de lijst. De 1,39 miljoen emissierechten zijn dus geen telling van de rekeningen die in het bezit zijn van landbouwbedrijven. Het gaat om een aantal drop-quota’s (één per account, één per spel) die ergens op Steam zijn besteed en uiteindelijk, onverkocht, in de commerciële voorraad zijn terechtgekomen. Of het account erachter nu een farm was of een tiener die zijn badgepagina aan het volmaken was, doet niets af aan wat Valve heeft verzameld: de $5.00-ontgrendeling, de gamelicentie en een deel van de opbrengst op de Markt bij elke verkoop — niet 15%, maar 15% of de twee minimumbedragen van één cent, afhankelijk van welk bedrag het grootst is, wat op een kaartje met prijzen in centen veruit het grootste bedrag is. De berekening staat in de onderstaande tariefladder. Dat is de strekking van deze pagina, en het is geen klacht over boeren: hetzelfde gedrag waarvoor Valve een vergoeding vraagt, is precies het gedrag dat het woord voor woord aanhaalt wanneer het iemand permanent uitsluit wegens „commercieel gebruik”.\n\nHet cijfer is ook in een tweede betekenis een ondergrens. Het omvat alleen aandelen die vandaag aangeboden en niet verkocht over bots die ervoor kiezen om in een openbare map te staan. Alles wat al is verkocht, alles wat in privébezit is, en elke bot die niet in de lijst staat, wordt uitgesloten.\n\nEn met de prijzen van Valve is landbouw niet rendabel\n\nHet voor de hand liggende bezwaar is dat een farm goedkope spellen koopt om dure kaarten te genereren. De eigen winkel-API van Steam wijst dit echter van de hand. Van de 13,876 spellen die kaarten bevatten, zijn de prijzen voor 13,713 vastgesteld; 12,918 zijn betaalde titels met een mediane catalogusprijs van $9.99. De mediane prijs van een voltooide set bedraagt $0.74. Per set zijn twee licenties nodig. De mediane set kost dus ongeveer $19.98 van de spelvergunningen voor de productie en de teruggaven $0.74.\n\nGemeten op 2026-09-22\tWaarde\tWat er wordt geregeld\nMediaan van de catalogusprijs, kaartspel\t$9.99\tDe licentie is het duurste onderdeel van de transactie, niet de kaart\nGames die $4.99 of minder kosten\t3,665 (28.4%)\tZelfs de goedkope staart is duurder dan de set die je ermee kunt maken\nHet goedkoopste kaartspel in de winkel\t$0.99\tTwee licenties, $1.98, voor een set die doorgaans voor minder dan $1.30 wordt verkocht\nSpellen waarvan de set meer opbrengt dan het spel zelf\t323 van 12,918 (2.5%)\tIn 1 op de 40 spellen is er sprake van kaartarbitrage ten opzichte van de catalogusprijzen van Steam\nFree-to-play-titels in de telling\t795\tEn Valve bepaalt de prijs van elk van hun drops op $9 aan in-game-uitgaven\n\nDaarmee is de economische kwestie in het voordeel van Valve en tegen het gangbare verhaal beslecht. Tegen de prijzen die Valve zelf hanteert, Het verzamelen van kaarten is een verliesgevende bezigheid die alleen rendabel is als de licenties zijn aangeschaft tegen een prijs die lager ligt dan de catalogusprijs van Steam — bundels, regionale prijsstelling, doorverkoop van belangrijke producten. De kaarten zijn het restant. De aankoop is de gebeurtenis. En de aankoop vond plaats op Steam.\n\nWat de boerderij eigenlijk in stand houdt\n\nAls je alle stukjes bij elkaar legt, lijkt de boerderij niet langer iets te zijn dat Valve tolereert, maar iets dat Valve nodig heeft. Elke input die een boerderij levert, is een output waarvoor Valve een rapport opstelt of een factuur uitreikt. Volg één bot-account naar buiten toe:\n\nEén gehuurd accounteen „groothandelsklant”, geen lek\nVerkoop van games\n\nKoopt de titels die het verzamelt — van de 13,876-kaartspellen tot de $0.50-shovelware — omdat kaarten alleen uit spellen vallen die je in bezit hebt.\n\n\"Online\" & speeltijd\n\nLaat ze inactief zijn om kaarten te laten vallen, waardoor de cijfers voor het aantal gelijktijdige spelers en het aantal gespeelde uren — die Valve aanhaalt als maatstaf voor betrokkenheid — worden gevoed; precies die statistiek die § 4.C „gesimuleerde speeltijd“ noemt.\n\nInschrijvingen\n\nDe $5.00-grens voor het beperkte account moet worden overschreden voordat er een kaart kan worden ontvangen — Valve boekingen per account op basis van daadwerkelijke uitgaven in de winkel.\n\nGeld in de portemonnee & kosten\n\nElke kaart die het verkoopt, wordt teruggeleid via de Market, waar de vergoeding voor een kaart met een lage waarde kan oplopen tot 66.7% en de opbrengst in de Steam Wallet blijft geblokkeerd.\n\nSteam-niveau PR\n\nDe badges en niveaus Valve bestaan alleen maar omdat er sets zijn samengesteld — en de top van die ranglijst wordt bezet door bots (zie § 03).\n\nVerwijder de boerderij en alle bovenstaande getallen dalen — er werden minder exemplaren van het spel verkocht, het „online“-gedeelte was kleiner, het account werd nooit aangemaakt, er werd nooit een vergoeding in rekening gebracht en het niveau werd nooit bereikt. Daarom bestaat er een regel die automatisering verbiedt, terwijl er tegelijkertijd miljoenen geautomatiseerde accounts zijn: het verbod is de optie, en de activiteit levert de inkomsten op.\n\nEn de uitbetaling zelf is een waardeverlies Valve: je betaalt twee keer belasting\n\nDe kaart is niet het einde van de lus. Dankzij de eigen mechanica van Valve kan een kaart worden verpletterd tot edelstenen, en edelstenen moeten worden gebruikt om te maken boosterpakketten — nog drie kaarten — die weer worden verkocht of vernietigd. Elke stap is een markttransactie of een omzetting, en over elke stap wordt belasting geheven. De richting van die lus vloeit voort uit de hieronder gemeten minimumbelasting en vereist geen extern model: elke kaart die daarbinnen wordt verkocht, levert minstens twee cent, op kaarten die voor drie tot vijf worden verhandeld, zodat elke draai aan de slinger minder oplevert dan erin is gestoken. Deze vicieuze cirkel vernietigt virtuele waarde en dwingt tot nieuwe, kostenverhogende transacties om deze te vervangen. Er wordt hier geen cijfer genoemd voor de omvang van dat verlies — het rendement per set hangt af van de edelsteensnelheden en de kansen in de boosters; deze zijn in dit onderzoek niet gemeten.\n\nVerzamelkaartitems uit een spel dat je bezit\n→\nEdelstenenkaart vernietigd, vergoeding geïnd\n→\nBoosterpakketedelstenen die zijn gebruikt om te maken\n→\n3 nieuwe kaartenverkocht op Market, provisie ingehouden\n↶\n\nHier worden alleen de spelmechanismen beschreven, en die zijn afkomstig van Valve zelf — kaarten worden omgezet in edelstenen, met edelstenen worden boosters gemaakt, boosters leveren kaarten op — elk beschreven in de Steam Trading Cards FAQ, en elke stap is een belastbare marktgebeurtenis. Bron van de lusmechanismen: Valve, Steam Veelgestelde vragen over ruilkaarten ↗.\n\nDit is niet zomaar een moment. Het is een sector met een jarenlange basis.\n\nEén enkele momentopname kan toeval zijn. Daarom werd de openbare kaartbot-database één keer per seizoensgebonden Steam-uitverkoop geraadpleegd, via de Wayback Machine, van 2022 tot 2026 — de vaste voorraad die de bots bij zich hadden, en dezelfde accounts, uitverkoop na uitverkoop. De economie verschijnt niet zomaar en verdwijnt ook niet; ze blijft bestaan, met een stabiele kern van exploitanten, en bereikte een piek van meer dan drie miljoen complete sets op voorraad tijdens de winteruitverkoop van 2023 — zo’n derde van een miljoen TF2-sleutels met waarde die op een bepaald moment in één map waren opgeslagen.\n\nVolledige kaartensets in de openbare bot-map, te koop voor Steam\n\nEén Wayback-momentopname van steam.supply/CardBots per seizoensuitverkoop. Beweeg de muis erover voor de waarde in TF2-sleutels tegen het tarief van die momentopname.\n\n0.0M\n0.9M\n1.8M\n2.6M\n3.5M\nA’22\nS’23\nW’23\nS’24\nW’24\nS’25\nS’26\n401Verschillende botaccounts die bij de verkopen zijn waargenomen\n59Aanwezig in 5 of meer van de 7 verkopen — de stabiele kern\n16Aanwezig bij elk van de 7 verkopen, 2022–2026\n3,22 miljoenPeak-sets op voorraad (winter 2023) ≈ $570k–790k in sleutels\nHoe de badge-ladder van één verkoop er vanaf de top uitziet\n\nDe vraag komt overeen met het aanbod. In het openbaar Zomeruitverkoop 2024 – Badgeladder gearchiveerd 2026-07-16 ↗, had het account op nummer één het verkoopembleem ontworpen 1,740,645 keer — 1,74 miljoen sets van tien kaarten, 17,4 miljoen kaarten samengevoegd tot één profieldecoratie. Tegen de marktprijs van de veiling ($0.50 per set) is dat ~$870,000 van de kaartwaarde; gekocht zoals het in werkelijkheid wordt gekocht — TF2-sleutels die worden geruild om bots een niveau hoger te brengen, tegen een verhouding van ongeveer 7,6 sets per sleutel — is het ~229,000 toetsen, ongeveer $410,000–$570,000 in reële termen. De nummer twee-rekening: 552,000 sets, ~$130,000–181,000. Hier speelt niemand om. Het wordt gekocht, en elke stap in het aankoopproces is een transactie die Valve afwikkelt.\n\nMethode en beperkingen: de totale voorraad wordt opgeteld voor alle bots die in elke momentopname worden vermeld; de getal Het aantal bots per snapshot is niet vergelijkbaar tussen de verschillende verkopen, omdat sommige snapshots alleen aanbevolen bots tonen en andere de volledige lijst; de voorraad wordt daarom gezien als een ondergrens van wat zichtbaar was, niet als een volledige telling. Voor sleutelwaarden wordt gebruikgemaakt van het mediane aantal geadverteerde sets per sleutel uit elke momentopname en een TF2-sleutel van $1.79–$2.49. De consistentie wordt gewaarborgd door SteamID64 over de verschillende momentopnames heen. Momentopnames uit 2021 maakten gebruik van een oudere paginalay-out en zijn niet meegenomen. Gegevens: farm-economy-timeline.json; badgeniveaus van SteamLadder; vastgestelde prijzen van Steam Card Exchange (Wayback-momentopnames op het moment van verkoop, $0.05 per kaart).\n\nEn diezelfde vloot is er ook als er geen uitverkoop is\n\nDe twee foto’s hierboven tonen geen twee populaties. Het gaat om één vloot, gefotografeerd op verschillende momenten. De lijst die bovenaan deze paragraaf is weergegeven, is afgelezen op een een gewone dag waarop er geen seizoensuitverkoop plaatsvindt — 2026-09-22 — en zelfs in rust bleef het 91 bots en 694,673 complete sets: in de orde van grootte van 186,000 TF2-toetsen, $334,000–$464,000 van de kaartwaarde, inactief tussen de verkopen door. Dat is de minimale bezetting die de vestiging heeft als er niets te doen is.\n\nEn het gaat om dezelfde bewerking. Geselecteerd op basis van SteamID64, 87 van die 91 inactieve bots — 96% — komen ook voor in de zeven bovenstaande verkoopoverzichten, zestien stuks in elk afzonderlijk exemplaar. De catalogus is geen kraam die voor de verkoop wordt opgezet en daarna weer wordt afgebroken; het is een permanente commerciële inventaris die door dezezelfde vloot is uitgebreid tot wel 3,22 miljoen sets op het hoogtepunt van de winter van 2023 en daalt nooit tot nul. Een uitverkoop is wanneer er verkocht wordt. Die vindt de rest van het jaar ook plaats.\n\nDe standaardmap, per bot\n\nElk vierkantje staat voor één bot in de map op 2026-09-22; het is gemarkeerd als het ook voorkomt in de zeven verkoopoverzichten. 91 is het aantal dat die dag in het overzicht stond, niet de omvang van de vloot — In de verkoopoverzichten komen 401 verschillende accounts voor, en de lijst geeft op verschillende dagen een ander overzicht weer.\n\nGezien in eerdere veilingen (87) Nieuw sinds de laatste snapshot (4)\n\nDe basiswaarde voor niet-verkoop is 2026-09-22, afgelezen uit dezelfde openbare map, zonder inloggen. De rustwaarde is gebaseerd op het door elke bot zelf opgegeven aantal sets per sleutel en de sleutelband $1.79–$2.49 daarboven. De overlapping wordt berekend op basis van SteamID64 ten opzichte van de zeven uitverkoopsnapshots. Omdat de verhouding tussen aanbevolen en volledige aanbiedingen per snapshot verschilt, wordt hier de voorraad en identiteit vergeleken, niet het aantal gebruikers. Rekenwerk in paragraaf 08.\n\n03 — De ladder\nHet andere product is het getal naast je naam\n\nKaarten zijn de grondstof. Het eindproduct is van niveau Steam, en Valve bepaalt de prijs per set.\n\n100Steam Niveau\nDoelniveau — versleep of gebruik de pijltjestoetsen\nPrijs van één complete set, USD\n\n$0.20 is de goedkoopste complete set in de telling, $0.74 de mediaan, $1.70 het gemiddelde. Het cijfer heeft alleen betrekking op de kaarten — nooit op de $5.00 ontgrendelingen of de spellicenties.\n\n55,000XP vereist\n550Verbruikte complete sets\n110Games om te bezitten, zelf te farmen\n$407.00De kosten van de kaarten tegen die prijs\n1,100Verrekening van verbrande emissierechten, minimum\n$5,500.00$5.00 wordt ontgrendeld, als er geen account wordt hergebruikt\nVoltooide sets, niveau 1 tot 1,000\n\nEén badge-knutselwerkje = één complete set = 100 XP. Elk niveau binnen een blok van tien kost 100 XP meer dan het blok daaronder.\n\n0\n12,625\n25,250\n37,875\n50,500\n1\n250\n500\n750\n1000\n667\n550 sets\n\nEen level is geen versiering die Valve met rust laat. Het is aan het account gekoppeld. Uit de FAQ over ruilkaarten van Valve, over wat je krijgt als je een badge maakt: \"100 XP, waarmee je je Steam-niveau kunt verhogen. Als je Steam-niveau stijgt, wordt de limiet voor het aantal vrienden op je vriendenlijst met vijf verhoogd, en mogelijk krijg je dan de mogelijkheid om je profiel aan te passen met showcases.\" En wat boosterpacks betreft: \"Je Steam-niveau verhoogt de kans dat je een boosterpack krijgt: Niveau 10: +20%… Niveau 50: +100% toename van je dropkans (d.w.z. de kans is verdubbeld).\"\n\nDit niveau regelt dus twee dingen Valve: met hoeveel mensen je vrienden mag zijn, en hoe snel gratis kaarten in je inventaris terechtkomen. Dat tweede effect versterkt zich: hoe meer sets je hebt verbruikt, hoe sneller het platform je meer materiaal aanlevert. Valve heeft de herinvesteringscyclus in het product ingebouwd.\n\nDe wisselkoers staat vast en wordt bekendgemaakt. Voor het maken van één badge is één complete set nodig en levert dit 100 XP op; \"Je kunt maximaal vijf keer een set voor hetzelfde spel samenstellen.\" De XP-kosten per niveau stijgen om de tien niveaus. Dat levert het volgende op, en niets hiervan is een schatting:\n\nSteam Niveau\tVolledige sets die het verbruikt\tGames die je moet hebben om ze zelf te kunnen maken\tBij de goedkoopste set ooit gemeten ($0.20)\tBij de mediaan ($0.74)\tSchaal\n10\t10\t2\t$2.00\t$7.40\t\n50\t150\t30\t$30.00\t$111.00\t\n100\t550\t110\t$110.00\t$407.00\t\n200\t2,100\t420\t$420.00\t$1,554.00\t\n500\t12,750\t2,550\t$2,550.00\t$9,435.00\t\n667\t22,579\t4,516\t$4,515.80\t$16,708.46\t\n\n667 is geen hypothetisch getal. Het is het hoogste niveau waarnaar één enkele bot in de openbare lijst aangeeft een klant te kunnen brengen, uit de 33,359 sets die hij bezit in 6,117 spellen. De vierde kolom geeft dezelfde prijs weer in vergelijking met de goedkoopste complete set in de hele census; de vijfde kolom in vergelijking met de mediaan. Beide zijn marktprijzen voor de kaarten alleen en sluiten de $5.00-ontgrendeling en de gamelicenties volledig uit.\n\nHoe de curve is gecontroleerd, aangezien Valve deze niet publiceert\n\nValve geeft het percentage badges aan (\"Elke 100 XP levert je een extra Steam niveau op\") en dekt dit vervolgens af — \"(in ieder geval in het begin)\" — zonder de escalatie bekend te maken. De hierboven gebruikte curve is de standaardcurve, waarbij elk niveau binnen een blok van tien 100 XP meer kost dan het blok eronder. Dit is geverifieerd aan de hand van de directory in plaats van aangenomen: voor elke bot waarvan het geadverteerde maximum wordt beperkt door zijn voorraad in plaats van door de limiet van vijf vaartuigen per spel, het niveau dat op basis van deze curve wordt berekend, komt exact overeen met het niveau dat de bot aangeeft — 541 tegen 541, 494 tegen 494, 464 tegen 464. Waar de limiet daarentegen van toepassing is, ligt het berekende cijfer een paar niveaus hoger, wat precies is wat een limiet die ook afhankelijk is van de spelersselectie per wedstrijd zou moeten doen. Over de curve boven niveau 667 wordt geen uitspraak gedaan.\n\nLees de ladder naast sectie 02 en de structuur van het bedrijf wordt duidelijk. Om één account op niveau 500 te krijgen, moet iemand 12,750 complete sets samenstellen. Voor elk van die sets waren de drop-quota van ten minste twee accounts nodig; elk van die accounts had de $5.00-drempel overschreden en bezat het spel. Eén pronkgetal bovenaan een profiel rust op ten minste 25,500 bestede drop-toelagen eronder. Valve verliest die transactie niet. Valve is de tegenpartij bij elk onderdeel ervan.\n\n04 — De statistieken\nDe clausule beschrijft de landbouw niet in algemene bewoordingen. Ze somt de activiteiten op.\n\n§ 4.C is geen algemene bepaling tegen bots. In de opgesomde voorbeelden worden achtereenvolgens de twee zaken genoemd die een kaartboerderij voortbrengt.\n\n\"Het is niet toegestaan om op enigerlei wijze gebruik te maken van scripts, bots, macro's of andere niet door mensen bestuurde systemen ('automatisering') om interactie aan te gaan met de inhoud en diensten op Steam, met inbegrip van maar niet beperkt tot:\n\nHet automatiseren van het aanmaakproces van Steam-accounts,\nHet vervalsen van gameplay-statistieken (bijv. opgeblazen aantallen overwinningen of nederlagen, XP, speeltijd),\nBeloningen of vooruitgang behalen zonder echte inbreng van de gebruiker,\n\"Deelname aan beoordelingssystemen (zoals peer reviews of 'overwatch') via geautomatiseerde middelen, waaronder het beïnvloeden van uitkomsten of het rapporteren van gebruikers door middel van vooraf geprogrammeerde acties in plaats van een weloverwogen oordeel.\"\n— Steam Abonnementsovereenkomst § 4.C ↗ gearchiveerd 2026-09-24 ↗ · overgenomen en letterlijk geciteerd 2026-09-22\n\"…speeltijd\"\n\nUren waarin de machine stilstaat, zijn geen ‘spookuren’. In de ASF-FAQ wordt deze vraag rechtstreeks beantwoord — \"Waarom neemt de speeltijd van games die via ASF zijn verkregen niet toe?\" — met: \"Dat klopt, maar niet in realtime. Steam registreert je speeltijd met vaste tussenpozen en plant op basis daarvan een update in… meestal wordt het ongeveer elke 30 minuten bijgewerkt.\"\n\nDie uren worden vastgelegd in de gegevens van Valve, op de winkelpagina’s van Valve en in de tellingen van het aantal gelijktijdige spelers die Valve zelf publiceert Steam Grafieken ↗ gearchiveerd 2026-09-23 ↗. In die cijfers is een inactief account niet te onderscheiden van een actief account. De engagementcijfers die het platform naar buiten toe rapporteert, worden berekend op basis van een populatie die, volgens de eigen regels van het platform, ook accounts omvat die niet actief zijn.\n\n\"…zonder echte inbreng van de gebruikers\"\n\nDat is een definitie van een ‘idled card drop’, opgesteld door Valve. Het is tevens een definitie van het Steam-niveau, het insigne, de voorwaarden voor het ontvangen van boosterpakketten en de bijbehorende profiel-XP — de ASF-FAQ bevestigt dit \"zorgt ervoor dat je boosterpacks kunt blijven ontvangen\", omdat het op dezelfde manier inlogt als de officiële client.\n\nHet beloningssysteem en de verboden handeling vormen dus één mechanisme dat vanuit twee invalshoeken wordt bekeken. Valve zorgde ervoor dat de beloning werd gegenereerd door tijd in plaats van door vaardigheid, en voegde vervolgens een bepaling toe die verbood dat beloningen werden gegenereerd door iets anders dan een persoon die die tijd besteedde.\n\n05 — De valkuil van commercieel gebruik\nElke uitgang via een bewerkte kaart is een uitgang die volgens de vergunning verboden is — en Valve vraagt een vergoeding aan de deur\n\nDit is het aspect dat niet kan worden opgelost door ‘verantwoord’ te farmen. De licentie is bedoeld voor persoonlijk, niet-commercieel gebruik, en een kaart wordt pas de moeite waard om te farmen op het moment dat het geen persoonlijk gebruik meer is.\n\n§ 2.A — de vergunning\n\n\"Valve verleent hierbij, en u aanvaardt, een niet-exclusieve licentie en het recht om de Inhoud en Diensten te gebruiken voor uw persoonlijk, niet-commercieel gebruik (behalve wanneer commercieel gebruik uitdrukkelijk is toegestaan in deze voorwaarden of in de toepasselijke abonnementsvoorwaarden).\"\n\n§ 2.G — de beperking\n\n\"Je hebt geen recht op: … (iii) de Inhoud en Diensten of onderdelen daarvan voor commerciële doeleinden te exploiteren, tenzij dit elders in deze Overeenkomst (met inbegrip van eventuele Abonnementsvoorwaarden of Gebruiksregels) uitdrukkelijk is toegestaan.\"\n\n§ 3.D — de vergoeding\n\n\"Valve kan een vergoeding in rekening brengen voor transacties op een abonnementsmarktplaats. Eventuele kosten worden u meegedeeld voordat de transactie wordt afgerond.\"\n\nLees de drie samen en de positie wordt gesloten\n\nEen kaart die wordt bewaard, is voor een boerderij waardeloos. Een kaart die wordt verkocht, geruild of tot edelstenen wordt verwerkt, is gebruikt om waarde te creëren — en Valve heeft in zijn eigen handhavingsbrief aangegeven hoe het dat noemt: de beheerder van 170 bots kreeg te horen dat het account \"werd gebruikt om op Steam op illegale wijze verzamelkaarten te verzamelen, evenals aanverwante en niet uitsluitend commerciële activiteiten.\" In dat geval kwamen de kaarten op de markt. De verkoop werd afgerond. De vergoeding werd geïnd. Het verbod kwam pas daarna.\n\nDe vergoeding bij die deur bedraagt niet 15%. Op een gehuurde kaart bedraagt deze tweederde.\n\n§ 3.D. Reserves \"een vergoeding\". Op de kaarten die een boerderij daadwerkelijk produceert, komt die vergoeding bij lange na niet in de buurt van de geadverteerde ~15%. De Community Market neemt een 5% Steam transactiekosten en 10% spelkosten, elk met een minimum van $0.01 (Valve's eigen FAQ over de Community Market). Op een kaartje met een prijs van één cent staan die vloeren zijn de prijs: de koper betaalt drie cent, waarvan twee cent aan kosten. Door de afrondingsregel wordt het getal 15% in feite een heffing die oploopt tot 66.7% precies waar de kaartmarkt draait — een paar cent per kaart.\n\nEffectieve provisie bij een verkoop op de Community Market, op basis van de vraagprijs van de verkoper\n\n5% Steam + 10% spel, elk minimaal $0.01. De gearceerde strook geeft aan waar ruilkaarten daadwerkelijk worden geruild — ongeveer $0.03–$0.05 per kaart.\n\n0%\n10%\n20%\n30%\n40%\n50%\n60%\n70%\ncards\n$0.01\n$0.10\n$0.20\n$0.30\n$0.40\n$0.50\n66.7%\nDe verkoper wil\tSteam 5% (min. $0.01)\tWedstrijd 10% (min $0.01)\tDe koper betaalt\tGecombineerd tarief\n$0.01\t$0.01\t$0.01\t$0.03\t66.7%\n$0.03\t$0.01\t$0.01\t$0.05\t40.0%\n$0.05\t$0.01\t$0.01\t$0.07\t28.6%\n$0.08\t$0.01\t$0.01\t$0.10\t20.0%\n$1.00\t$0.05\t$0.10\t$1.15\t13.0%\n\nDe 10%-spelvergoeding gaat naar de app die de kaart heeft uitgegeven; de 5% is voor Valve zelf, en bij Valve’s eigen titels en basisvoorraadartikelen komt de volledige vergoeding toe aan Valve. Hoe dan ook, het geld verdwijnt uit de zakken van de farmer — bij de verkoop van een kaart van drie cent blijft er één cent over en gaan er twee verloren. Vermenigvuldig dat met de honderdduizenden verkopen van kaarten van minder dan vijf cent die een farm genereert en \"de vergoeding die Valve in rekening mag brengen\" is het bedrijfsmodel, geen voetnoot. Bron: Steam Veelgestelde vragen over de Community Market — Kosten ↗ gearchiveerd 2026-09-21 ↗, lees 2026-09-22; de curve is rekenkundig op basis van die twee gepubliceerde rentetarieven en hun $0.01-ondergrenzen.\n\nGeen enkele configuratie van de tool kan hieraan ontkomen. De tool kan door één persoon, op één account en met de grootste terughoudendheid worden gebruikt — en op het moment dat die persoon ook maar één ‘gefarmde’ kaart verkoopt om geld in zijn portemonnee te krijgen, geldt voor hem dezelfde bepaling in § 2.G als voor de exploitant van tienduizend accounts. Valve heeft zich dus een inbreuk voorbehouden waarop het in feite elke kaartverkoper op zijn eigen markt zou kunnen aanspreken, maar heeft afgezien van het inroepen daarvan tegen vrijwel al deze verkopers. Een regel die op die manier wordt gehandhaafd, is geen regel. Het is een keuze. De vraag die deze tentoonstelling opwerpt, is niet waarom ‘card farmers’ worden getolereerd; maar waarom diezelfde maatregel wel wordt toegepast tegen een individuele gebruiker die een kaart verkoopt, terwijl de commerciële kaarteconomie die door die kaarten wordt gevoed — de handelsdiensten, de level-up-bots, de groothandelaren — openlijk doorgaat, waarbij een van de grootste groepen wordt gemodereerd door een Valve-medewerker (§ 08). De overtreding wordt alleen de kleine bezitter aangerekend en aan de machine vergeven.\n\n06 — Het handhavingsoverzicht\nZonder waarschuwing, in golven, en het verspreidt zich via het telefoonnummer\n\nValve heeft de bevoegdheid om zonder voorafgaande kennisgeving op te treden in de overeenkomst zelf opgenomen, direct na de clausule inzake automatisering.\n\n\"Valve kan je account(s) of een bepaald abonnement beperken of beëindigen wegens elk gedrag of elke activiteit die onwettig is, een vorm van valsspelen of automatisering vormt, of in strijd is met de Steam Regels voor online gedrag. U erkent dat Valve niet verplicht is om u vooraf in kennis te stellen alvorens uw abonnement(en) en/of account te beëindigen.\"\n\n— Steam Abonnementsovereenkomst § 4.D ↗ gearchiveerd 2026-09-24 ↗ · woordelijk geverifieerd 2026-09-22\n\n1,000+ bots · handelsverbod. \"Het lijkt erop dat dit account is gebruikt om een netwerk van botaccounts te beheren. Het gebruik van bots is in strijd met de Steam-abonneeovereenkomst.\"\n\nMeer dan 170 bots · definitief geblokkeerd, winteruitverkoop 2017. \"Dit account werd gebruikt om op Steam op illegale wijze verzamelkaarten te verzamelen, evenals aanverwante en niet uitsluitend commerciële activiteiten. Het account is definitief geblokkeerd en Steam Support kan geen verdere ondersteuning bieden met betrekking tot deze kwestie.\"\n\nMeer dan 120 bots · definitief geblokkeerd. \"Dit en andere accounts werden gebruikt om onze netwerkinfrastructuur te overbelasten, wat een schending is van Steam van de gedragsregels online.\"\n\n— Steam Steunbetuigingen die zijn opgenomen in de ArchiSteamFarm FAQ, onder het kopje „Is er iemand hiervoor geblokkeerd?”. Bron ↗ · woordelijk geverifieerd 2026-09-22\nCasus 4 — juni 2025, VAC verboden op stilgelegde CS2\n\nEen recentere gebeurtenis dan de drie hierboven genoemde is vastgelegd in de tracker van het project zelf: accounts die Counter-Strike 2 uitsluitend via de tool hadden laten draaien, ontvingen VAC verboden — het soort dat bedoeld is om valsspelen tegen te gaan, niet het administratieve soort. De beheerder stelt dat stationair draaien hier geen oorzaak van kan zijn, aangezien het \"doet niets anders dan Steam laten weten dat we een bepaald spel spelen.\" Over de oorzaak bestaat onenigheid. Dat de accounts zijn geblokkeerd, staat vast.\n\n— ArchiSteamFarm discussie #3440, geopend op 26 juni 2025 ↗ · lees 2026-09-22\n\nHoe een hoofdaccount ten onder gaat\n\nIn dezelfde discussiethread beschrijft een medewerker aan het project de regel voor het doorgeven van informatie: accounts kunnen worden geblokkeerd \"via Chain\", als ze hetzelfde telefoonnummer gebruiken — \"Het kan gaan om slechts één VAC-verbod, dat wordt doorgevoerd naar 'schone' accounts die aan het geblokkeerde account zijn gekoppeld.\"\n\nSteam Guard vereist een telefoonnummer. De ‘farms’ worden opgebouwd op basis van het telefoonnummer van de gebruiker. Handhaving blijft dus niet beperkt tot de wegwerpaccounts: het spoor volgt de gedeelde identificatiecode terug naar het account dat de bibliotheek, de vriendenlijst en de inventaris bevat. Dat is het mechanisme dat een projectmedewerker beschrijft voor hoe één enkele actie het hoofdaccount van een beheerder samen met de farm verwijdert — en het is de reden waarom het verlies tijdens een handhavingsgolf niet wordt gemeten in $5-accounts. (Beschreven door een projectmedewerker in ASF GitHub-discussie #3440; er is geen officiële Valve-bevestiging of formeel precedent vastgelegd.)\n\nDezelfde paragraaf, met een tussenperiode van vijf jaar, afkomstig van drie verschillende makelaars\n\nDe bepaling die landbouw als een inbreuk aanmerkt — commercieel gebruik van een persoonlijke, niet-commerciële licentie — geldt niet alleen voor landbouwbedrijven. Het is de standaardreden die Steam opgeeft wanneer het een account wegens handel sluit, en die reden wordt als sjabloon verstuurd. Hieronder staan drie voorbeelden, gepubliceerd door de mensen die ze hebben ontvangen, met een tussenpoos van vijf jaar, afkomstig van drie verschillende, bij naam genoemde agenten.\n\nBericht van Steam Support op 29 september om 19:56 uur\n\n\"Het account waarmee u dit bericht schrijft, is geblokkeerd wegens schending van de voorwaarden van de Steam-abonnementsovereenkomst. Op basis van handelsactiviteiten, meldingen van de community en andere factoren is vastgesteld dat het account voor commerciële doeleinden wordt gebruikt.\"\n\nDeze vergrendeling is permanent en Steam De helpdesk kan u hierbij niet verder helpen.\n\nAangezien we alle informatie hebben verstrekt waarover we beschikken, sluit ik dit hulpverzoek af. Houd er rekening mee dat u geen verdere reacties meer zult ontvangen met betrekking tot deze kwestie.\n\nMet vriendelijke groeten,\n\"Hal\"\n\nDit hulpverzoek is gesloten.\n29 september 2020. Geplaatst door de ontvanger met het volgende commentaar: \"RIP Trading.\" — @gergelyszabo94 ↗\nBericht van de klantenservice Steam op 12 juli om 22:41\n\n\"Het account waarmee u dit bericht schrijft, is geblokkeerd wegens schending van de voorwaarden van de Steam-abonnementsovereenkomst. Op basis van handelsactiviteiten, meldingen van de community en andere factoren is vastgesteld dat het account voor commerciële doeleinden wordt gebruikt.\n\nDeze vergrendeling is permanent en Steam De helpdesk kan u hierbij niet verder helpen.\n\nAangezien we alle beschikbare informatie hebben verstrekt, sluit ik dit hulpverzoek af. Houd er rekening mee dat toekomstige hulpverzoeken met betrekking tot de accountblokkering mogelijk zonder antwoord worden afgesloten.\n\nSteam Ondersteuning\n\"Vido\"\n\nDeze hulpvraag is afgesloten.\n12 juli 2024, Portugese interface. De ontvanger is een professionele CS2-speler: \"Ik heb al contact opgenomen met de Steam-klantenservice, maar krijg alleen automatische antwoorden… Ik kan Faceit niet spelen en ook geen professionele wedstrijden.\" — @prcs25 ↗ gearchiveerd 2024-07-15 ↗\nGeciteerd door de ontvanger, r/steamsupport\n\n\"Hallo, het account waarmee u dit bericht schrijft, is geblokkeerd wegens schending van de voorwaarden van de Steam-abonnementsovereenkomst. Op basis van handelsactiviteiten, meldingen van de community en andere factoren is vastgesteld dat het account voor commerciële doeleinden wordt gebruikt.\n\nDeze vergrendeling is permanent en Steam De helpdesk kan u hierbij niet verder helpen.\n\nAangezien we alle informatie hebben verstrekt waarover we beschikken, sluit ik dit hulpverzoek af. Houd er rekening mee dat toekomstige hulpverzoeken met betrekking tot de accountblokkering mogelijk zonder antwoord worden afgesloten.\n\nSteam Ondersteuning\n\"Sally\"\n\nDrie keer ontvangen, op basis van drie afzonderlijke verzoeken.\n29 maart 2025. De schrijver diende geen bezwaar in tegen de blokkering — zijn account was samen met zijn e-mailadres gestolen en hij vroeg om toegang: \"Ik vraag niet naar de blokkering en ik betwist die ook niet; ik wil gewoon toegang tot mijn Steam-account… Valve hebben me bij elk verzoek precies hetzelfde antwoord gegeven – gekopieerd en geplakt – en het verzoek vervolgens gesloten.\" — r/steamsupport ↗, opgenomen in de eigen klachtendatabase van dit onderzoek\n\nWoord voor woord, komma voor komma, gedurende vijfenvijftig maanden, met drie agenten en twee interface-talen. De enige wijziging in de hele tekst is de aanscherping van de laatste zin tussen 2020 en 2024, van \"je zult geen verdere antwoorden meer ontvangen\" naar \"Toekomstige hulpverzoeken… kunnen zonder antwoord worden gesloten.\" Welk proces deze beslissingen ook tot stand heeft gebracht, de brief geeft daar geen beeld van. De genoemde redenen zijn „handel, meldingen uit de gemeenschap en andere factoren“ — een categorie, een rapport van onbekende herkomst en een niet nader gespecificeerd overblijvend deel.\n\nNog vijf gevallen, op dezelfde manier verzameld. De eerste drie behoren tot dezelfde categorie en hebben dezelfde uitkomst; de laatste twee zijn hetzelfde formulier, waarin een andere regel met dezelfde bewoordingen wordt toegepast:\n\nDatum\tWat het account deed\tWat is er gebeurd?\tBron\n4 december 2021\tKopen en verkopen op Buff — \"Ik heb niets anders gedaan dan wat kopen en verkopen op Buff, ook wel bekend als P2P-handel\"\tGemeenschapsverbod: geen markt, geen handel, dure voorraad bevroren\tr/csgomarketforum ↗ gearchiveerd 2025-03-27 ↗\n6 december 2021\tEenrichtings-P2P-ruiltransacties via Buff en Bitskins voor uitrustingen en upgrades\tPermanent slot voor commercieel gebruik plus gemeenschapsslot: \"Ik zit vast in een soort onzichtbare modus… Mijn profiel staat ook nog steeds op 'privé'\"\tr/GlobalOffensiveTrade ↗ gearchiveerd 2021-12-06 ↗\n20 december 2024\tAccount sinds 2017, duizenden uren; ruilt op community-marktplaatsen voor thematische uitrustingen en upgrades\tPermanente vergrendeling met gemeenschappelijke vergrendeling, zonder voorafgaande waarschuwing of aanslag; ondersteuning \"zeggen dat hun besluit definitief is\", de antwoorden worden automatisch gegenereerd\tr/csgomarketforum ↗ gearchiveerd 2025-06-27 ↗\n23 december 2024\tEen terugkerende gebruiker vult zijn portemonnee aan na een jaar afwezigheid, via een VPN \"alleen voor algemene internetbeveiliging\"\tPermanente uitsluiting uit de community met er werd helemaal geen reden opgegeven: \"Het verbod is definitief en zij kunnen geen verdere informatie verstrekken; bovendien kunnen verdere tickets zonder reactie worden gesloten.\" 196 positieve stemmen, 340 reacties\tr/steamsupport ↗\n4 augustus 2026\tJarenlange aankopen uit Iran; de schrijver stelt dat hij nooit iets heeft gepost, nooit de Market heeft gebruikt en nooit op de forums is geweest\tToegang voor de gemeenschap geblokkeerd tot 2038 meer dan \"regio’s waar sancties gelden\"; het ticket is afgesloten door een medewerker met de naam Azul. Een terugbetaling voor hetzelfde account vanaf hetzelfde Iraanse IP-adres was een jaar eerder goedgekeurd. De bibliotheek en het geld blijven bij Valve.\tr/pcgaming ↗\n\nDe laatste regel wijkt af van de rest — naleving van sancties, geen commercieel gebruik — en is opgenomen omdat de opbouw van het antwoord identiek is: een categorie, geen bewijs, geen beroep, een afgesloten ticket. Het roept ook een vraag op die de andere niet doen. Als het onrechtmatig was om de account te bedienen, dan was het ook onrechtmatig om de jarenlange betalingen te accepteren. Een van die twee standpunten moet onjuist zijn, en slechts één ervan heeft de klant iets gekost.\n\nAlle acht werden gelezen op 2026-09-22 — de discussiethreads uit 2021 en december 2024 via momentopnames van het Internet Archive en de rest via een openbare Reddit-interface, omdat Reddit directe verzoeken van de verzamelende host weigerde. De twee berichten uit 2020 en 2024 zijn getranscribeerd op basis van de schermafbeeldingen die bij de oorspronkelijke berichten waren gevoegd en die nog steeds online staan. In dit onderzoek wordt geen van deze accounts beschuldigd van onschuld of schuld — dat is juist het punt. Geen enkele lezer, en geen enkele toezichthouder, kan dit uit de brief opmaken.\n\nOpmerking over de gegevensbron — verliezen op exploitantniveau\n\nDe exploitanten die in het kader van dit onderzoek zijn ondervraagd, melden verliezen in de orde van grootte van elk vijf- tot tienduizend accounts in afzonderlijke handhavingsacties, waarbij de belangrijkste rekeningen naast het landbouwbedrijf worden opgemaakt. Die enquête wordt hier vermeld als rapportage door de betrokken partij zelf, niet als een bevinding. Er is geen gepubliceerde steekproefomvang, geen vaste verzamelingsdatum en geen verificatie per account, en geen enkel ander getal op deze pagina is hiervan afhankelijk; de twee rijen in sectie 02 die hierop zijn gebaseerd, zijn als zodanig gemarkeerd.\n\nDit wordt om twee redenen expliciet vermeld in plaats van weggelaten. Het hierboven beschreven ‘chain-ban’-mechanisme is de gedocumenteerde verklaring voor precies dat patroon. En een toezichthouder kan vanaf Valve het enige gegevensbestand afdwingen dat hierover uitsluitsel zou geven: hoeveel accounts er voor automatisering in aanmerking kwamen, in welke fasen, en hoeveel elk van die accounts in de winkel had uitgegeven voordat deze werd gesloten. Zolang dat gegevensbestand niet bestaat, blijft het cijfer waar het is — gerapporteerd, toegeschreven en onbewezen.\n\n07 — De asymmetrie\nBeide kanten van hetzelfde bureau\n\nVergelijk die bewijsstandaard met die Valve die wordt gehanteerd voor de eigen ondersteuningsoperatie. De rechterkolom is het incidentenregister van dit dossier zelf, overgenomen met de voorbehouden die daarin zijn opgenomen.\n\nEen klant, voor handelsdoeleinden\n\nAcht gedocumenteerde gevallen, 2020–2026\n\nGedrag\nHet verkopen of kopen van artikelen op marktplaatsen van derden; in één geval was er helemaal geen sprake van wangedrag — het account was gestolen.\nGetoonde bewijzen\nGeen. \"Op basis van handelsactiviteiten, meldingen uit de gemeenschap en andere factoren.\"\nMededeling\nGeen. Valve heeft in § 4.D het volgende gereserveerd: \"Valve is niet verplicht om u vooraf in kennis te stellen van de beëindiging.\"\nBeroep\n\"Deze blokkering is permanent en Steam De helpdesk kan u hier verder niet bij helpen.\"\nTicket\nAfgesloten na het eerste antwoord. Verdere verzoeken \"kan zonder antwoord worden gesloten.\"\nBereik\nProfiel, vriendenlijst, chat, Market, inventaris en alle items die met echt geld zijn gekocht.\nDuur\nPermanent.\nEen geautomatiseerde botvloot, voor grote volumes\n\n694,673 complete sets in de openbare voorraad, verdeeld over 91 bots\n\nGedrag\nHet gelijktijdig uitvoeren van geautomatiseerde headless-scripts op duizenden accounts om kaarten inactief te maken, op grote schaal badges te genereren en sets te ruilen op industriële schaal.\nGetoonde bewijzen\nOpenbaar toegankelijke bot-overzichten (steam.supply, SteamLvlUp) en openbare groepen met miljoenen leden.\nMededeling\nGeen enkele ingreep. 88.97% er geldt geen enkel verbod; 99.8% van de resterende verboden zijn louter cosmetisch.\nBeroep\nNiet nodig. Vloten blijven gedurende hun meerjarige levenscyclus ononderbroken in bedrijf.\nTicket\n—\nBereik\nOnbeperkte uitwisseling van inventaris, het verhogen van het niveau van badges en marktliquiditeit.\nOpbrengst tot Valve\n$26.8M+ in de minimale besteding in de winkel ($5.00 toegangspoort per account) plus 15% kortingen op transacties op de Community Market.\nDe vraag die hierdoor rijst, eenvoudig gezegd\n\nEen individuele klant die handmatig kaarten of items verhandelt, riskeert een permanente, onherroepelijke uitsluiting op grond van § 4.C (automatisering) of § 2.G (commercieel gebruik). Een geautomatiseerde ‘farming’-vloot die via duizenden accounts ‘headless bots’ inzet, opereert openlijk met een 88.97% ongeschonden percentage. Valve is de begunstigde van beide.\n\nDe asymmetrie is van economische aard: individuele handelaren halen waarde uit het platform, terwijl geautomatiseerde kaartvloten miljoenen in de uitgavenlimiet van Valve ($5.00 per account) pompen en bij elke doorverkoop de transactiekosten opdrijven. De handhaving volgt niet het geschreven reglement, maar het verdienmodel.\n\n08 — Bestuur\nWie houdt toezicht op de kaarteconomie?\n\nDe terugkerende bevinding in dit dossier — namelijk dat de laag van derde partijen rondom Steam wordt bemand vanuit Steam — geldt ook voor de kaarteconomie, en dit leidt tot een specifieke conclusie: niemand die onafhankelijk is, kan nagaan wat de handhaving door Valve daadwerkelijk teweegbrengt, omdat de partij die dit zou kunnen nagaan zich binnen die laag bevindt. Alle onderstaande feiten zijn afkomstig uit de eigen openbare groeps- en profielpagina’s van Valve op 2026-09-22 en kunnen door iedereen in een browser worden nagekeken.\n\nEen medewerker met de naam Valve is moderator van de grootste groep voor het ruilen van kaarten Valve medewerker\n\nCardTrades ↗ beschrijft zichzelf in de eigen koptekst als de \"Steam Officiële groep van Card Exchange\" en draagt 97,114 leden. De vermelde moderators — de accounts die de leiding over die groep hebben — zijn Mickmane, SgtFopper en afarnsworth ↗.\n\nDat laatste profiel wordt door de opmaak van de eigen website van Valve aangemerkt als een Valve-medewerker — op de pagina staat class=\"profile_header_valve_employee\" — geeft de locatie aan als Bellevue, Washington, en behoort tot de Valve, Steam en Steam Groep voor ruilkaarten groepen. SteamID64 76561197960434622, lid sinds 12 september 2003.\n\nDeze opmerking is van structurele aard, niet persoonlijk, en het is niet een punt van automatisering — de moderator van een groep voor het ruilen van kaarten gebruikt geen bot, en niets wijst hier op het tegendeel. Het gaat om de bepaling in paragraaf 07. Steam Card Exchange is een commerciële kaartdienst van een derde partij; het ruilen van kaarten via diensten van derden is precies het gedrag waarvoor Valve gewone accounts permanent blokkeert op grond van \"gebruikt voor commerciële doeleinden op basis van handelsactiviteiten, meldingen uit de gemeenschap en andere factoren.\" Een Valve-medewerker bekleedt een officiële moderatorfunctie in de officiële communitygroep van die dienst, die 97.000 leden telt.\n\nEr wordt hier tegen niemand een beschuldiging van wangedrag geuit, en er worden geen conclusies getrokken over wat die rol precies inhoudt. De asymmetrie is de bevinding: wanneer een gewone account in aanraking komt met een kaart- of skin-dienst van een derde partij, is het antwoord een gesloten ticket en een permanente blokkering zonder dat er bewijs wordt getoond; wanneer het om deze dienst gaat, staat een Valve-medewerker op de moderatorlijst en is de regeling zichtbaar op een pagina die Valve zelf publiceert. Wat hier wordt gevraagd, is wat overal elders in dit dossier wordt gevraagd: leg de schriftelijke toestemming over, indien die bestaat — en als er geen nodig is, zeg dat dan schriftelijk, want aan acht mensen in sectie 06 is het tegenovergestelde verteld.\n\nDe banlijst en wie deze beheert Vrijwillige moderatorDienst van een derde partij\n\nDe groep van Steambans.com (gearchiveerd) ↗ (live ↗ gearchiveerd 2025-12-03 ↗) beschrijft zijn afstamming in de bewaard gebleven groepsbeschrijving: \"De officiële Steambans.com Steam-communitygroep. SteamBans.com is een gloednieuwe dienst die is gebaseerd op een oud concept. Wereldwijde banlijsten zijn al jaren actief in het oude WONID-programma van VALVe. Toen de overstap naar STEAMID plaatsvond, was het voor ons vanzelfsprekend om een dienst te ontwikkelen die speciaal op dit nieuwe systeem is afgestemd. Maar we wilden ook meer. *. Archiefpagina voor Steambans, dat in 2013 is stopgezet.\" Tot de geregistreerde beheerders behoren onder meer devicenull en killahinstinct_ ↗.\n\nDat beheerdersaccount is niet een Valve-medewerker — er is geen vlag ‘medewerker’ bij aangegeven. Het gaat om een vrijwilliger met een ongewoon hoge status: een lid van Community-moderators (414 leden, omschreven als een groep \"gemaakt door de communitymoderators van Steam\"), van Wiki-coördinatoren, van Steam Buurtmarkt, en van Valve programma- en pre-release-groepen, waaronder Valve Pijpleiding, Steam Beta-versie voor klanten, Mobile Auth Beta, Nieuwe Steam Community-bèta, Steam Labs, Steamworks en Oplichtings-URL’s melden. SteamID64 76561197960794555.\n\nOok binnen die kring en die Steambans rechtstreeks in zijn openbare groepslijst weergeeft: msart ↗ (lijst met groepen ↗), SteamID64 76561197977933359, waarvan in het profiel in eigen woorden staat \"Ik beheer steamid.uk en tal van andere websites, zowel over Steam als over andere onderwerpen.\", en die een onderling verbonden netwerk van zestien groepen beheert — SteamIDcouk (hoofdgroep \"Sid-website\"), SidAdmins, SidBans, steamideu, Steam3ID, s-id en SArchive daaronder.\n\nsteamid.uk noemt zelf hetzelfde aantal. In de veelgestelde vragen staat: \"Wie heeft SteamID ontwikkeld? De SteamID-website, de netwerkinfrastructuur en de beveiligingssystemen worden allemaal beheerd door 76561197977933359.\" Twee antwoorden verderop staat vermeld waar de gegevens vandaan komen: \"SteamID maakt voornamelijk gebruik van de Steam Web API voor het verzamelen van gegevens.\" Op dezelfde pagina worden verschillende dedicated servers bij diverse hostingproviders beschreven, evenals externe ontwikkelings-, opslag- en tekstzoek-servers, en een aparte back-upfaciliteit.\n\nGeverifieerd aan de hand van bewaarde gegevens uit het Internet Archive: de Overzicht van de Steambans-groep op 3 december 2025 ↗, de Overzicht van het operatorprofiel op 14 september 2024 ↗, en de steamid.uk FAQ-overzicht van 1 april 2026 ↗, waarbij de gegevens rechtstreeks van 2026-09-22 worden afgelezen.\n\nWat dit alles bij elkaar betekent, en wat niet\n\nBanlijsten, SteamID-resolutie en het ruilen van kaarten zijn de drie diensten die bepalen wie betrouwbaar is, wie identificeerbaar is en wat een item waard is. Geen van deze drie wordt beheerd door Valve. Bij elk daarvan kwamen degenen die de leiding hadden uit de baan rond Valve: een gemarkeerde Valve-medewerker op de moderatorlijst van de officiële groep van de kaartdienst; een ervaren Valve-communitymoderator met toegang tot het pre-release-programma die de banlijstgroep beheert; de ID-resolutiedienst die wordt gerund door een particulier die tot dezelfde kring behoort. Drie diensten, drie controlepunten, drie mensen Valve die al een vaste positie hadden verworven.\n\nLidmaatschap van een groep is geen dienstverband, en dit alles is geenszins een beschuldiging. Dat is een feit op het gebied van bestuur, en het is de reden waarom het gebruikelijke verweer — dat zijn derde partijen, daar hebben we geen invloed op — moet worden getoetst in plaats van zomaar te worden aanvaard. De mensen aan het roer zijn geen onbekenden met Valve. Valve is in de positie om te zeggen wat het eventueel van hen heeft gevraagd; niemand van buitenaf is in de positie om daar achter te komen.\n\nNiemand telt mee. Dat is de conclusie.\n\nDe Steam ID-ruimte is een aaneengesloten reeks gehele getallen. Deze doorlopen en rapporteren hoeveel accounts zijn geblokkeerd, hoeveel er beperkt zijn en hoeveel voorraad er achter een handelsverbod schuilgaat, is geen onderzoeksprogramma — het is een lus en een API-sleutel. Valve deelt die sleutel zelf uit, op steamcommunity.com/dev/apikey. En toch Er is geen enkele onafhankelijke instantie die die volkstelling publiceert. Geen toezichthouder, geen journalist, geen wetenschapper, geen consumentenorganisatie. De enige openbare cijfers over de omvang van de handhaving op Steam zijn de cijfers die Valve zelf noemt.\n\nDe mogelijkheid ontbreekt niet. Ze wordt achtergehouden. De dienst die de ID-ruimte op grote schaal verwerkt en indexeert — steamid.uk — vermeldt in zijn eigen FAQ dat hij \"maakt voornamelijk gebruik van de Steam Web API voor het verzamelen van gegevens\" en draait het op meerdere speciale servers, externe opslag, tekstzoekmachines en een aparte back-upfaciliteit. Het wordt beheerd door één particulier. Zijn broer of zus uit de banlijst wordt mede beheerd door een ervaren Valve-communitymoderator die toegang heeft tot de pre-release-programma’s van Valve. De enige partij die in de positie verkeert om de telling te publiceren, bevindt zich in de invloedssfeer van Valve en maakt deze niet openbaar.\n\nDit is dezelfde structuur die in het dossier overal elders terug te vinden is. Elke dienst die een beslissende rol speelt in de Steam-economie — wie wordt vertrouwd, wie is identificeerbaar, wat is een item waard, wie wordt uitgesloten — is nominaal een derde partij en staat in de praktijk dicht bij Valve. Steam Card Exchange vormt geen uitzondering op dat patroon; het is er juist een voorbeeld van. Het argument dat het hier om onafhankelijke actoren gaat, kan Valve juist worden aangevoerd omdat niemand dit ooit aan de hand van een getal heeft kunnen toetsen.\n\nDe telling van 10,88 miljoen accounts: 88.97% Ongebruikt\n\nHet ArchiSteamFarm-installatiebestand werd gecontroleerd in alle Valve's GetPlayerBans eindpunt (10,880,610 rekeningen, 55 minuten). Alleen al de onbeperkte deelverzameling vertegenwoordigt $26.8M+ in minimale besteding in de winkel ($5.00 toelatingsdrempel). 9,680,599-accounts (88.97%) zijn op geen enkele wijze geblokkeerd, en 99.8% van de overige hebben slechts symbolische verboden opgelegd aan de community, waardoor geautomatiseerde handel gewoon doorgaat.\n\n5,360,499ASF-leden zonder beperkingen (aantal weergegeven Steam's)\n10,880,610Totaal aantal gescande API-vermeldingen (beperkt + onbeperkt)\n9,680,599Nooit verbannen (88.97%)\n1,200,011Een Steam-verbod (11.0%) — 99.8% cosmetica\n55 minOm de gehele bevolking te tellen, is één belangrijk\nForensisch bewijsmateriaal en uitgebreide telling\n\nDe gedetailleerde demografische uitsplitsing — met onder meer grafieken over de verdeling van de soorten verboden, de leeftijd van de accounts op het moment van handhaving, clusters op basis van het jaar van aanmaak (2020–2026) en zelfgerapporteerde geografische gegevens — is gepubliceerd in het speciale censusonderzoek.\n\nOpen de volledige lijst met 10,88 miljoen verboden (Bijlage VI) →Paragraaf 4 — De Asset ID-black-out →\n\nDe vraag die we dus moeten stellen, en die alleen door Valve kan worden beantwoord, is: welke identificatiecode of bevoegdheid is ingetrokken, op welke datum, op basis van wiens besluit, en welk meetbaar effect dit heeft gehad op de exploitanten waarop het betrekking had — afgezet tegen het effect ervan op iedereen daarbuiten die probeerde mee te tellen. Een wijziging die een einde maakt aan onafhankelijke controle wordt niet neutraal alleen omdat ze als veiligheidsmaatregel werd aangekondigd. Dat is de reden waarom de volkstelling in het bovenstaande blok niet bestaat.\n\n09 — Werkwijze en beperkingen\nWat er werd voorgelezen, en wat niet wordt beweerd\n\nElk citaat op deze pagina is rechtstreeks overgenomen uit de livebron op 2026-09-22 en woordelijk weergegeven. Niets op deze pagina is afkomstig uit een scrape, marktplaatsgegevens of een particuliere dataset.\n\nDe vier datasets en de berekeningen die daarop zijn uitgevoerd\n\nElk verzoek is een afzonderlijk openbaar verzoek dat vanaf een terminal kan worden gereproduceerd. Er is geen account gebruikt, er is niet ingelogd op een marktplaats en er is geen eindpunt aangeroepen waarvoor inloggegevens nodig waren.\n\nDataset\tWaar het vandaan kwam\tWat werd daaruit berekend?\nKaarteninventarisatie\n13,876 wedstrijden\tSteam De door Card Exchange gepubliceerde prijslijst voor badges, dezelfde feed waarmee hun openbare prijspagina ↗ gearchiveerd 2026-08-04 ↗\tSpellen waarin kaarten worden uitgegeven, het aantal kaarten per set, de verschillende soorten kaarten en de marktprijs van elke complete set. De mediaanwaarden en het $23,586.57-totaal vormen de rekenkundige basis van dit onderzoek.\nPrijzen van spellen\n13,713 opgelost\thet eigen openbare store-eindpunt van Valve, store.steampowered.com/api/appdetails, cc=us, alleen het prijsveld, in batches\tMediaan en verdeling van de catalogusprijs van een kaartspel; het aantal spellen waarvan de complete set beter verkoopt dan het spel zelf.\nVoorraad bots\n91 bots, 694,673 sets\tDe openbare lijst met kaartbots op steam.supply/CardBots ↗, lees zoals weergegeven, geen aanmelding\tHet totale aantal sets op voorraad, het minimumaantal kaarten, de ondergrens voor het aantal afgestoten kaarten en de ondergrens per bot voor het aantal vakjes op afzonderlijke accounts.\nDubbelcontrole\n21 gedeelde bots\tsteamlvlup.net/cardbots ↗ gearchiveerd 2026-02-10 ↗, een onafhankelijk overzicht van dezelfde bots\tAlleen ter verificatie. Op de 21 bots die op beide lijsten staan, stemt Aggregate Stock ermee in om 0.03%; het grootste verschil tussen twee bots is 1.36%, wat overeenkomt met twee inventarisaties van de actuele voorraad die enkele minuten na elkaar zijn uitgevoerd.\n\nBronvermelding, zoals vereist in de tweede map: gegevens verstrekt door SteamLvlUp, onder licentie van CC BY 4.0 gearchiveerd 2026-09-23 ↗; hier uitsluitend gebruikt als onafhankelijke controle van de voorraadcijfers van een derde partij, en aangepast in die zin dat de rijen per bot werden samengevoegd en vergeleken in plaats van overgenomen. Steam Card Exchange en steam.supply worden hierboven via een link vermeld. De prijzen van de spellen zijn afkomstig van Valve. De namen en afbeeldingen van kaarten, spellen en sets zijn eigendom van Valve of de uitgevers, en worden zonder aanspraak of licentie weergegeven als feiten over een markt.\n\nTwee geplande metingen zijn niet uitgevoerd en er zijn geen alternatieve metingen voor gedaan. De eigen eindpunten van Steam voor de Community Market — prijsoverzicht, zoeken/weergeven, prijsgeschiedenis — er wordt niets teruggestuurd naar de host die de gegevens verzamelt, en Steam de discussiepagina’s van de Community sturen een HTTP 403-status terug, dus geen enkel cijfer op deze pagina is afgeleid van actuele marktgegevens. De methode op basis van verkoopvolume, waarmee kaartuitgiften bij de dagelijkse reset zouden zijn geteld, vereist een ingelogde Steam-sessie; In het manifest van dit onderzoek staat vermeld dat er geen marktplaatsgegevens zijn gebruikt, en die verklaring is gehandhaafd. De bot-stockvloer is wat er zonder bot-stock kan worden gemeten.\n\nPrimaire bronnen\n\nSteam Abonnementsovereenkomst ↗ gearchiveerd 2026-09-24 ↗ — § 2.A, § 2.G, § 3.D, § 4.C, § 4.D.\nSteam Ondersteuning — Beperkte gebruikersaccounts ↗ — de $5.00-drempel en de lijst met beperkte functies.\nValve — Steam Veelgestelde vragen over ruilkaarten ↗ — de drop-mechanismen en het $9 free-to-play-tarief.\nArchiSteamFarm Veelgestelde vragen ↗ en discussie #3440 ↗.\nSteam Communitygroepen en profielpagina’s, direct te lezen, voor sectie 08.\nsteamid.uk FAQ, momentopname van het Internet Archive 2026-04-01 ↗.\nAcht Steam Kennisgevingen inzake ondersteuningsblokkades, gepubliceerd door de ontvangers ervan, 2020–2026, met de bijbehorende links in paragraaf 06.\n\nWat niet wordt geclaimd\n\nEr wordt geen omzetcijfer geschat voor Valve uit ‘card farming’. Er wordt voor geen enkele tool een aantal actieve accounts opgegeven, en de 1,39 miljoen toegestane drops zijn niet een overzicht van accounts die eigendom zijn van de boerderij — zie de opmerking in paragraaf 02. Er wordt niemand beschuldigd van wangedrag; wanneer een persoon wordt genoemd, gebeurt dit onder zijn of haar eigen openbare Steam-gebruikersnaam, in zijn of haar eigen openbare rol, vanaf een pagina die Valve publiceert. Van geen van de acht vergrendelde accounts in paragraaf 06 wordt beweerd dat ze onschuldig of schuldig zijn; de bevinding betreft de brief, niet het account. De cijfers over het verlies aan beheerders in paragraaf 02 zijn rapportages van de betrokkenen zelf en worden als zodanig aangeduid op de inkoopnota. De FAQ van steamid.uk is overgenomen uit een momentopname van het Internet Archive, omdat de live-pagina alleen toegankelijk is na het doorlopen van een bot-controle. Er wordt niet beweerd dat er pogingen zijn ondernomen om een overzicht van verbanningen op te stellen en dat deze zijn onderdrukt — de conclusie is louter dat er geen is gepubliceerd. De Steam-niveaucurve boven 667 is niet gemodelleerd.\n\nWaarom het hulpmiddel niet het onderwerp is\n\nArchiSteamFarm stelt dat het \"is niet goedgekeurd door Valve\" en er wordt op deze pagina geen enkele beschuldiging tegen het bedrijf geuit. Het wordt gebruikt als meetinstrument, omdat het de enige partij in deze economie is die de werkwijze openbaar en schriftelijk vastlegt. Valve kan het hele betoog in één alinea afhandelen: publiceer welke commerciële automatisering het toestaat, en het overzicht per operator van wat het met de rest heeft gedaan.\n\nLees verder: hoe de markt zelf wordt gewaardeerd → · de prijsladder en het maximumaantal aanbiedingen → · de artikelen Steam zullen niet worden geleverd →",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Een botfarm is geen lek in de winkel van Valve. Het is een klant."
          },
          {
            "level": 2,
            "id": null,
            "text": "Wat een boerderij eigenlijk is, stap voor stap"
          },
          {
            "level": 3,
            "id": null,
            "text": "Inkopen"
          },
          {
            "level": 3,
            "id": null,
            "text": "Games kopen"
          },
          {
            "level": 3,
            "id": null,
            "text": "Inactief\nDe tool logt het account zonder gebruikersinterface in op het Steam-netwerk, \"analyseert je badges\", stelt de lijst met titels samen die je kunt spelen en start \"de in aanmerking komende game spelen en regelmatig controleren of de game al volledig is uitgespeeld.\" De beschrijving van het mechanisme door de beheerder: het \"doet niets anders dan Steam laten weten dat we een bepaald spel spelen.\""
          },
          {
            "level": 3,
            "id": null,
            "text": "De druppels raken op\nElke titel is eindig. \"Elke game heeft een vast aantal kaarten dat je kunt vinden. Zodra je ze allemaal hebt gevonden (ongeveer de helft van de volledige set), is de game niet langer geschikt om te 'farmen'.\" Een boerderij die wil blijven produceren, moet steeds nieuwe kaarten blijven kopen. Het aanbod aan kaarten wordt beperkt door aankopen — dit is zo ontworpen en speelt in het voordeel van Valve."
          },
          {
            "level": 3,
            "id": null,
            "text": "Uitbetalen\nDe kaart verlaat het spel via een van de drie mogelijkheden: ze wordt verkocht op de Community Market, geruild of verwerkt tot edelstenen. Elk van deze opties is een transactie op de Subscription Marketplace of een ruil, en § 3.D behoudt zich het recht voor om: \"Valve kan een vergoeding in rekening brengen voor transacties op een abonnementsmarktplaats.\" Dit is de stap waardoor het geheel een inbreuk vormt — zie 05."
          },
          {
            "level": 2,
            "id": null,
            "text": "Voordat een boerderij ook maar een cent verdient, heeft ze al Valve betaald"
          },
          {
            "level": 3,
            "id": null,
            "text": "Hoe groot het te kopen voorwerp eigenlijk is"
          },
          {
            "level": 3,
            "id": null,
            "text": "Hoe groot is een set?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Wat de licentie kost"
          },
          {
            "level": 3,
            "id": null,
            "text": "Wat de voltooide set oplevert"
          },
          {
            "level": 3,
            "id": null,
            "text": "Waar de 694,673-sets staan"
          },
          {
            "level": 3,
            "id": null,
            "text": "Wat deze vloer wel en niet zegt"
          },
          {
            "level": 3,
            "id": null,
            "text": "En met de prijzen van Valve is landbouw niet rendabel"
          },
          {
            "level": 3,
            "id": null,
            "text": "Wat de boerderij eigenlijk in stand houdt"
          },
          {
            "level": 4,
            "id": null,
            "text": "Verkoop van games"
          },
          {
            "level": 4,
            "id": null,
            "text": "\"Online\" & speeltijd"
          },
          {
            "level": 4,
            "id": null,
            "text": "Inschrijvingen"
          },
          {
            "level": 4,
            "id": null,
            "text": "Geld in de portemonnee & kosten"
          },
          {
            "level": 4,
            "id": null,
            "text": "Steam-niveau PR"
          },
          {
            "level": 3,
            "id": null,
            "text": "En de uitbetaling zelf is een waardeverlies Valve: je betaalt twee keer belasting"
          },
          {
            "level": 3,
            "id": null,
            "text": "Dit is niet zomaar een moment. Het is een sector met een jarenlange basis."
          },
          {
            "level": 3,
            "id": null,
            "text": "Volledige kaartensets in de openbare bot-map, te koop voor Steam"
          },
          {
            "level": 3,
            "id": null,
            "text": "Hoe de badge-ladder van één verkoop er vanaf de top uitziet"
          },
          {
            "level": 3,
            "id": null,
            "text": "En diezelfde vloot is er ook als er geen uitverkoop is"
          },
          {
            "level": 3,
            "id": null,
            "text": "De standaardmap, per bot"
          },
          {
            "level": 2,
            "id": null,
            "text": "Het andere product is het getal naast je naam"
          },
          {
            "level": 3,
            "id": null,
            "text": "Voltooide sets, niveau 1 tot 1,000"
          },
          {
            "level": 3,
            "id": null,
            "text": "Hoe de curve is gecontroleerd, aangezien Valve deze niet publiceert"
          },
          {
            "level": 2,
            "id": null,
            "text": "De clausule beschrijft de landbouw niet in algemene bewoordingen. Ze somt de activiteiten op."
          },
          {
            "level": 3,
            "id": null,
            "text": "\"…speeltijd\""
          },
          {
            "level": 3,
            "id": null,
            "text": "\"…zonder echte inbreng van de gebruikers\""
          },
          {
            "level": 2,
            "id": null,
            "text": "Elke uitgang via een bewerkte kaart is een uitgang die volgens de vergunning verboden is — en Valve vraagt een vergoeding aan de deur"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 2.A — de vergunning"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 2.G — de beperking"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 3.D — de vergoeding"
          },
          {
            "level": 3,
            "id": null,
            "text": "Lees de drie samen en de positie wordt gesloten"
          },
          {
            "level": 3,
            "id": "fee-ladder",
            "text": "De vergoeding bij die deur bedraagt niet 15%. Op een gehuurde kaart bedraagt deze tweederde."
          },
          {
            "level": 3,
            "id": null,
            "text": "Effectieve provisie bij een verkoop op de Community Market, op basis van de vraagprijs van de verkoper"
          },
          {
            "level": 2,
            "id": null,
            "text": "Zonder waarschuwing, in golven, en het verspreidt zich via het telefoonnummer"
          },
          {
            "level": 3,
            "id": null,
            "text": "Casus 4 — juni 2025, VAC verboden op stilgelegde CS2"
          },
          {
            "level": 3,
            "id": null,
            "text": "Hoe een hoofdaccount ten onder gaat"
          },
          {
            "level": 3,
            "id": null,
            "text": "Dezelfde paragraaf, met een tussenperiode van vijf jaar, afkomstig van drie verschillende makelaars"
          },
          {
            "level": 3,
            "id": null,
            "text": "Opmerking over de gegevensbron — verliezen op exploitantniveau"
          },
          {
            "level": 2,
            "id": null,
            "text": "Beide kanten van hetzelfde bureau"
          },
          {
            "level": 3,
            "id": null,
            "text": "Een klant, voor handelsdoeleinden"
          },
          {
            "level": 3,
            "id": null,
            "text": "Een geautomatiseerde botvloot, voor grote volumes"
          },
          {
            "level": 3,
            "id": null,
            "text": "De vraag die hierdoor rijst, eenvoudig gezegd"
          },
          {
            "level": 2,
            "id": null,
            "text": "Wie houdt toezicht op de kaarteconomie?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Een medewerker met de naam Valve is moderator van de grootste groep voor het ruilen van kaarten Valve medewerker"
          },
          {
            "level": 3,
            "id": null,
            "text": "De banlijst en wie deze beheert Vrijwillige moderator Dienst van een derde partij"
          },
          {
            "level": 3,
            "id": null,
            "text": "Wat dit alles bij elkaar betekent, en wat niet"
          },
          {
            "level": 3,
            "id": null,
            "text": "Niemand telt mee. Dat is de conclusie."
          },
          {
            "level": 3,
            "id": null,
            "text": "De telling van 10,88 miljoen accounts: 88.97% Ongebruikt"
          },
          {
            "level": 3,
            "id": null,
            "text": "Forensisch bewijsmateriaal en uitgebreide telling"
          },
          {
            "level": 2,
            "id": null,
            "text": "Wat er werd voorgelezen, en wat niet wordt beweerd"
          },
          {
            "level": 3,
            "id": null,
            "text": "De vier datasets en de berekeningen die daarop zijn uitgevoerd"
          },
          {
            "level": 3,
            "id": null,
            "text": "Primaire bronnen"
          },
          {
            "level": 3,
            "id": null,
            "text": "Wat niet wordt geclaimd"
          },
          {
            "level": 3,
            "id": null,
            "text": "Waarom het hulpmiddel niet het onderwerp is"
          }
        ],
        "links": [
          "https://help.steampowered.com/en/faqs/view/71D3-35C2-AD96-AA3A",
          "https://github.com/JustArchiNET/ArchiSteamFarm/wiki/FAQ",
          "https://steamcommunity.com/tradingcards/faq/",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260924114457/https://store.steampowered.com/subscriber_agreement/",
          "https://steamladder.com/ladder/badges/2861690/",
          "http://web.archive.org/web/20260716205303/https://steamladder.com/ladder/badges/2861690/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/farm-economy-timeline.json",
          "https://store.steampowered.com/charts/",
          "http://web.archive.org/web/20260923183013/https://store.steampowered.com/charts/",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://github.com/JustArchiNET/ArchiSteamFarm/discussions/3440",
          "https://x.com/gergelyszabo94/status/1311004678633795585",
          "https://x.com/prcs25/status/1811893857253982720",
          "http://web.archive.org/web/20240715122902/https://x.com/prcs25/status/1811893857253982720",
          "https://reddit.com/r/steamsupport/comments/1fjmgc5/what_to_do_when_your_steam_account_gets_hacked/mkelm2y/",
          "https://www.reddit.com/r/csgomarketforum/comments/r87owv/psa_my_steam_account_just_got_banned/",
          "http://web.archive.org/web/20250327203008/https://www.reddit.com/r/csgomarketforum/comments/r87owv/psa_my_steam_account_just_got_banned/",
          "https://www.reddit.com/r/GlobalOffensiveTrade/comments/r9xql9/d_recently_received_commercial_ban_for_what_seems/",
          "http://web.archive.org/web/20211206034804/https://www.reddit.com/r/GlobalOffensiveTrade/comments/r9xql9/d_recently_received_commercial_ban_for_what_seems/",
          "https://www.reddit.com/r/csgomarketforum/comments/1hhxx7m/d_permanently_locked_on_steam_for_commercial_use/",
          "http://web.archive.org/web/20250627014045/https://www.reddit.com/r/csgomarketforum/comments/1hhxx7m/d_permanently_locked_on_steam_for_commercial_use/",
          "https://www.reddit.com/r/steamsupport/comments/1hkctwt/permanent_ban_with_no_explanation/",
          "https://www.reddit.com/r/pcgaming/comments/1vf24lu/warning_to_all_gamersexpats_steam_took_my_money/",
          "https://steamcommunity.com/groups/card-trading-card-trades",
          "https://steamcommunity.com/id/afarnsworth",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/groups/steambans",
          "https://steamcommunity.com/groups/steambans",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/id/killahinstinct_",
          "https://web.archive.org/web/20240914124859/https://steamcommunity.com/id/msart",
          "https://steamcommunity.com/id/msart/groups/",
          "http://web.archive.org/web/20260401154714/https://steamid.uk/faq/",
          "https://phishdestroy.io/steam_dossier/nl/enforcement_audit.html",
          "https://phishdestroy.io/steam_dossier/nl/#evidence-blackout",
          "https://www.steamcardexchange.net/index.php?badgeprices",
          "http://web.archive.org/web/20260804200309/https://www.steamcardexchange.net/index.php?badgeprices",
          "https://steam.supply/CardBots",
          "https://steamlvlup.net/cardbots",
          "http://web.archive.org/web/20260210171205/https://steamlvlup.net/cardbots",
          "https://steamlvlup.net/",
          "https://creativecommons.org/licenses/by/4.0/",
          "http://web.archive.org/web/20260923221628/https://creativecommons.org/licenses/by/4.0/",
          "https://phishdestroy.io/steam_dossier/nl/market_economics.html",
          "https://phishdestroy.io/steam_dossier/nl/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/nl/elite_skins.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/nl/card_economy.content.json",
      "export_json_sha256": "a56730d3af4d7a498a54354ba20d592b641f17c0d7fc756abf650ab1c8c0fa92"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "nl/elite_skins.html",
      "language": "nl",
      "title": "Eén product, twee prijssystemen — Het dossier ‘Steam’",
      "source_url": "https://phishdestroy.io/steam_dossier/nl/elite_skins",
      "source_html_sha256": "442bb7630e3cb6d787b8b65625343fcf3bc9d88d3f1e1b87994c142c6dfb4477",
      "exported_at": "2026-09-29T00:18:24.094Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "register",
            "source": "https://phishdestroy.io/steam_dossier/nl/elite_skins#register"
          },
          {
            "id": "",
            "source": "https://phishdestroy.io/steam_dossier/nl/elite_skins#selected"
          }
        ],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "elite_skins.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/nl/elite_skins.pdf?v=print-20260929-v5",
        "sha256": "5e543e72588474fd8a6cceade9c89603ac9d8bd4ddcf48f9bd8956f7ae86cd4c",
        "bytes": 96503,
        "pages": 7
      },
      "integrity": {
        "signed_object": "elite_skins.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "elite_skins.content.json.asc",
        "digest_file": "elite_skins.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify elite_skins.content.json.asc elite_skins.content.json",
          "sha256sum -c elite_skins.content.json.sha256"
        ]
      },
      "content": {
        "text": "BIJLAGE IV / MARKTARCHITECTUUR / 20 SEPTEMBER 2026\nElite Skins Register — De marktplafond van $1,800\n\nEén artikel. Twee prijssystemen.\n\nWAT IN DIT HOOFDSTUK WORDT AANGETOOND\n\nDit register biedt een empirisch overzicht van alle CS2-huidcategorieën waarvan de prijs hoger ligt dan de limiet van $1,800 die Steam hanteert voor aanbiedingen op de Community Market, verspreid over vijf externe handelsplatforms. Hieruit blijkt dat 248 de door bevestigde categorieën uit het hoogste segment – die goed zijn voor 18,394 actieve aanbiedingen en $78.6 miljoen aan gepubliceerde liquiditeit – 100% ontbreken op de officiële marktplaats van Valve. Verkopers die op zoek zijn naar echte marktprijzen worden structureel gedwongen om gebruik te maken van externe platforms, terwijl ze uitsluitend vertrouwen op de onderliggende handelsmechanismen van Steam.\n\nWhat this means — the Community Market listing ceiling\n\nSteam’s own market refuses a listing above roughly $1,800. A seller may ask less, never more. Items whose market price sits above that line therefore cannot be sold at that price on Steam at all — which is the mechanism that moves those sales to third-party venues while the item itself never leaves Valve’s inventory system.\n\nSection 13 — the off-Steam price gap →\n\n← Terug naar het Executive Briefing\n\nSteam beperkt de prijs van een aanbieding op de Community Market tot ongeveer $1,800. Op de vijf externe marktplaatsen waarvan de prijzen in dit overzicht zijn opgenomen, 419 CS2-productcategorieën hebben een laagste actuele vraagprijs die boven die limiet ligt — en 402 daarvan, 95.9%,, hebben helemaal geen Steam-vermelding. Samen bezitten ze op 18,641 vermelde exemplaren met een waarde van ten minste $82.4 miljoen. Er is toestemming van een tweede handelsplatform nodig voordat een prijs geldig is, 248 van die categorieën worden bevestigd — en in elk daarvan ontbreekt 100%, op Steam. De lieveling is een sticker | Titan (Holo) | Katowice 2014 op $66,285, genoteerd door vier handelsplatforms met een onderling verschil van 5.2% en door geen enkel platform van Valve overgenomen. De volledige ladder, de weergaven en de beoordelingen staan in de prijsladderatlas.\n\nBekijk alle vermeldingen op 419 ↓Open de atlas ↗Lees de methode\n248categorieën met twee of meer marktplaatsen waarvan de prijs boven het maximum ligt\n18,394exemplaren die op vijf marktplaatsen worden aangeboden\n$78.6Mminimumprijs van die advertenties\n100%waarvan sommigen helemaal niet op Steam staan\n\nCorrectie · op deze pagina stond eerder een niet-bevestigde prijs vermeld\n\nIn een eerdere versie van deze pagina stond als kop: „Souvenir AK-47” | Point Disarray vroeg $148,954 op één marktplaats, terwijl Steam het op $119. had geprijsd. Die rij betreft één enkel exemplaar op één enkele plank, zonder dat een tweede marktplaats deze prijs bevestigt; het is dus eerder een vraagprijs dan een daadwerkelijke prijs, en het exemplaar staat niet langer op de pagina vermeld. Elk cijfer in de koptekst is nu beperkt tot de categorieën 248 waarvoor ten minste twee marktplaatsen onafhankelijk van elkaar een prijs boven de bovengrens hanteren. De rij zelf is niet verwijderd — deze staat nog steeds in het onderstaande register, en de beoordeling die tot de verlaging heeft geleid, wordt volledig uiteengezet in de prijsladderatlas.\n\n01 / het geld in actieve biedingen\nDe meetbare ondergrens in dollars\n\nOpnieuw berekend op basis van de officiële momentopname van cs2.sh over vijf marktplaatsen. Dit is een minimale totale vraagprijs binnen een bepaalde subgroep; het betreft geen omzetcijfers en evenmin een waardering van de CS2-economie.\n\n248 BEVESTIGDE CATEGORIEËN · 18,394 VERMELDE EXEMPLAREN · 5 MARKTplaatsen$78.62M\n\nDe laagste totale vraagprijs van elk CS2-item waarvoor twee of meer marktplaatsen onafhankelijk van elkaar een prijs hanteren die hoger is dan de limiet die Valve op zijn eigen markt toestaat.\n\nWaarom dit een minimum is en geen schatting\n\nVoor elke marktplaats vermenigvuldigen we de laagste vraag een artikel aan op basis van het aantal exemplaren dat op die marktplaats wordt aangeboden. Elk ander exemplaar op dat schap heeft een prijs die gelijk is aan of hoger ligt dan de laagste vraagprijs, dus de werkelijke gepubliceerde waarde is hoger — dit vloeit voort uit de opzet van het systeem, niet uit giswerk. Het gaat hier niet om een verkoop, een kasstroom of een marktbrede waardering, en hetzelfde fysieke artikel kan op meer dan één marktplaats worden aangeboden.\n\nControleer alle bronrijen in 419 ↗\n★ Sporthandschoenen | Hedge Maze (in de praktijk getest)\n$4.68M\nAWP | Gungnir (fabrieksnieuw)\n$4.46M\nAWP | Dragon Lore (fabrieksnieuw)\n$4.34M\n★ Vlindermes | Fade (fabrieksnieuw)\n$4.17M\nAK-47 | Wild Lotus (fabrieksnieuw)\n$4.16M\n★ Vlindermes | Doppler (fabrieksnieuw)\n$3.64M\n\nDe balken geven de zes grootste bijdragen op categorieniveau weer aan de berekening van de bodemprijs, gerelateerd aan de grootste. Een hoge balk geeft zowel de goedkoopste vraagprijs als het aantal aangeboden exemplaren weer. Hetzelfde fysieke artikel kan op meer dan één marktplaats voorkomen, dus deze cijfers mogen niet worden opgeteld bij het totaal van een andere marktplaats.\n\n02 / voorbeelden die kunnen worden bekeken\nWat er buiten de limiet valt\n\nAfbeeldingen komen, voor zover beschikbaar, overeen met de exacte benamingen van de artikelen. De prijzen zijn actuele vraagprijzen uit de catalogus van die datum, en geen transactiegegevens.\n\n★ Butterfly Knife | Doppler (Factory New)\n\nBron: https://phishdestroy.io/steam_dossier/nl/elite_skins#selected\n\nDe meetbare kloof: deze aanbiedingen kunnen niet worden geëvenaard door een advertentie op Steam met hetzelfde bedrag in USD. De eigen advertenties van Valve Veelgestelde vragen over de Community Market gearchiveerd op 2026-09-21 ↗ vermeldt een maximale vraagprijs van ongeveer $1,800. Een verkoper kan het object nog steeds onder die prijs aanbieden; of dat aanvaardbaar is, is aan de verkoper. Een afzonderlijke CSMarketCap: zoek naar items boven $1,800 ↗ toont Factory New Dragon Lore in de door 28 geïndexeerde markten, met ongeveer 1.1K weergegeven aanbiedingen; identieke voorraad kan meerdere keren worden geteld.\n\n03 / de structurele afhankelijkheid\nDe limiet van Steam zorgt ervoor dat de prijsvorming buiten Steam plaatsvindt\n\nDe vergelijking is structureel van aard. Er wordt niet van uitgegaan dat elke vraagprijs redelijk is, noch worden onverkochte objecten als omzet beschouwd.\n\n01 · DE REGEL\nSteam sluit de lijst af\n\nValve zegt dat het aantal vermeldingen op Community Market beperkt is tot ongeveer $1,800. Er geldt ook een maximum voor het saldo in de portemonnee, en het geld in de portemonnee kan niet als contant geld worden opgenomen.\n\n02 · DE WAARNEMING\nDragon Lore: $10,940.85\n\nDe catalogus van de marktplaats van de ‘5-’ toont 389 live-aanbiedingen voor AWP Dragon Lore (fabrieksnieuw), vanaf $10,940.85 (CSFloat floor). Het bredere register bevat 248 bevestigde categorieën die boven de limiet van Steam liggen.\n\n03 · HET GEVOLG\nPrijs- en overdrachtsverdeling\n\nEen verkoper die die hogere prijs wil krijgen kan het niet op Steam plaatsen. Externe dienstverleners kunnen de contante prijs vaststellen, maar bij de levering blijven het eigendom en de overdracht van de artikelen onder controle vSteam.\n\nDe tegenstrijdigheid in het beleid: Van Valve zelf Abonneovereenkomst gearchiveerd op 2026-09-21 ↗ behoudt zich het recht voor om de commerciële exploitatie van de diensten van Steam te verbieden, tenzij dit uitdrukkelijk is toegestaan, terwijl haar 2016 verklaring gearchiveerd op 2026-09-21 ↗ Die gokexploitanten maakten al gebruik van Steam OpenID en geautomatiseerde accounts. Dat is een direct bewijs dValve op de hoogte was van dit soort externe exploitanten op 2016. Toch mag de officiële marktplaats de waargenomen prijzen van deze hoogwaardige artikelen niet publiceren. Dat is de architectonische afhankelijkheid van prijsvorming en transacties via off-Steam; Voor de contractstatus van elke afzonderlijke marktplaats is afzonderlijk bewijs vereist. De twee belangrijkste westerse marktplaatsen die dit buitensporige transactievolume verwerken, opereren als formele rechtspersonen in belangrijke rechtsgebieden — CSFloat Inc. (opgericht in Delaware, VS) en Skinport GmbH (geregistreerd in Stuttgart, Duitsland, HRB 764879) — verricht openlijk transacties ter waarde van honderden miljoenen in de peer-to-peer-verkoop van artikelen, waarbij rechtstreeks gebruik wordt gemaakt van de web-API’s en handelsinfrastructuur van Steam.\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\nDe vier rijen van $100,000 komen overeen met de maximale vraagprijs van CSFloat zelf. Ze zijn in het register gemarkeerd en mogen niet als taxaties worden beschouwd. De gearchiveerde CSFloat-lijst omvat slechts ongeveer $6,999,, dus wordt de momentopname van de openbare catalogus gebruikt voor het volledige >$1,800-register.\n\n04 / weer een spel van Valve\nOok op de achtergrond is de Dota-2 te zien\n\nDezelfde strenge ‘goedkoopste-aanbod’-test op Skinport levert de volgende resultaten op: 166 (CS2-categorieën) en 3 (Dota-2-categorieën). Dit zijn afzonderlijke momentopnames van de marktplaats; voeg ze niet toe aan CSFloat’s 245.\n\nDOTA 2 · 1 AANBIEDING\nHeroïsche, brute halve maan\n\nDe goedkoopste Skinport vraag: $14,622.25.\n\nDOTA 2 · 1 AANBIEDING\nCape ‘Dark Artistry’\n\nDe goedkoopste Skinport vraag: $8,255.16.\n\nDOTA 2 · 1 AANBIEDING\nBeschadigde Powered Star\n\nDe goedkoopste Skinport vraag: $2,087.92.\n\nDit zijn drie categorieën van items die hier worden vermeld; het zijn niet alle Dota-2-items die er bestaan. Controleer de rijen met de datum ‘Skinport’ ↗ en API documentatie ↗.\n\n05 / robuustheid\nDe bevinding hangt niet af van de exacte bovengrens\n\nValve stelt het maximum vast in de regionale valuta van de koper, waardoor het omgerekend naar USD niet op één rond getal uitkomt. De telling wordt daarom bij elke plausibele drempelwaarde herhaald. Het aandeel van deze items dat ontbreekt op Steam daalt nooit onder 95%.\n\nDrempelwaarde getest\tProductcategorieën\tVermelde exemplaren\tMinimumwaarde\tAfwezig op Steam\n$1,800\t419\t18,641\t$82,449,526\t95.9%\n$2,000\t382\t15,159\t$75,541,325\t95.5%\n$2,070\t363\t12,336\t$69,560,305\t95.6%\n$2,300\t323\t11,644\t$67,984,432\t95.0%\n$2,500\t299\t10,950\t$66,203,929\t95.0%\n\nLees één rij per keer; de rijen zijn geneste deelverzamelingen van dezelfde volkstelling, geen afzonderlijke populaties. De „bodemwaarde“ vermenigvuldigt de laagste het geeft het aantal exemplaren weer dat er in de lijst staat, waardoor het aantal exemplaren in de collectie per definitie te laag wordt weergegeven. Open de dataset ↗\n\n06 / schaarste waarop je kunt rekenen\nHoe weinig daarvan er daadwerkelijk te koop zijn\n\nBUFF verdeelt het aanbod van elk item in verschillende categorieën en geeft aan hoeveel exemplaren er in elke categorie beschikbaar zijn. Zo wordt ‘zeldzaam’ niet langer alleen een woord, maar een concreet aantal — en wordt de prijs voor de staat los van de buitenkant bepaald.\n\n298 VERMELDE EXEMPLAREN\nAWP | Drakenkennis\n\n8 verschillende varianten met verschillende prijzen. De duurste, Souvenir AWP | Dragon Lore (fabrieksnieuw), vraagt $12,363 met 20 exemplaren op de plank.\n\nIn de beste drijfhouder op de plank (0–0.01) zitten 2 exemplaren, met de vraag $17,875 — een premie van +45% bovenop de basisvraagprijs van het artikel, uitsluitend op basis van de staat waarin het zich bevindt.\n\n607 VERMELDE EXEMPLAREN\nM4A4 | Howl\n\n12 verschillende varianten met verschillende prijzen. De duurste, Souvenir M4A4 | Howl (fabrieksnieuw), vraagt $14,895 met 2 exemplaren op de plank.\n\n213 VERMELDE EXEMPLAREN\nAK-47 | Wild Lotus\n\n7 verschillende varianten met verschillende prijzen. De duurste, Souvenir AK-47 | Wild Lotus (fabrieksnieuw), vraagt $14,895 met 2 exemplaren op de plank.\n\n310 VERMELDE EXEMPLAREN\nAWP | Gungnir\n\n7 verschillende varianten met verschillende prijzen. De duurste, AWP-souvenir | Gungnir (minimale gebruikssporen), vraagt $14,895 met 2 exemplaren op de plank.\n\nWaarom dit van belang is voor de rest van dit dossier: Dit zijn geen abstracte begrippen. Van elke trofee zijn er wereldwijd een paar honderd exemplaren in de open verkoop, elk gekoppeld aan één Steam-account en verhandeld via één Steam-transactie. Op een markt die zo klein is, is het stelen van één enkel voorraadartikel een meetbare gebeurtenis, en leveren de technieken voor het overnemen van accounts – die elders in dit onderzoek zijn gedocumenteerd – een direct en kwantificeerbaar rendement op.\n\nDe aantallen zijn actuele vermeldingen op één marktplaats op het moment van vastlegging, niet het totale aantal dat in omloop is. Exemplaren die zich in particuliere collecties bevinden, worden hier nergens meegeteld. Open de dataset met drijvende objecten ↗\n\n07 / de ladder uit het zicht\nHoe duurder het artikel, hoe verder het verwijderd is van een zichtbare locatie\n\nElke trede hieronder vertegenwoordigt een aparte categorie van bewijsmateriaal. Ze zijn bewust niet samengevoegd tot één getal.\n\nSpreil\tFiguur\tWat voor soort feit is dit?\nCeiling on Valve's own market\t~$1,800\tPublished rule, stated in the Steam Community Market FAQ.\nDearest ask several marketplaces agree on\t$66,285\tMeasured by us in this snapshot. Sticker | Titan (Holo) | Katowice 2014, quoted by four marketplaces within 5.2% of one another. An ask, not a sale.\nDearest ask seen on any single shelf\t$148,954\tOne marketplace, one copy, no second marketplace agreeing — and equal to a round CNY 1,000,000 at the snapshot rate. Listed here as the outer edge of what sellers ask, and relied on for nothing.\nPublic marketplace sale\t$49,999\tSpecialist Gloves | Crimson Kimono (FN) on CSFloat, as reported by SteamAnalyst. Platform-recorded, third-party reported.\nReported private sale\t$400,000\tAK-47 | Case Hardened, reported by PC Gamer in April 2023. Journalism, not a record we hold.\nReported offer, declined\t$1,500,000\tBlue Gem Karambit, pattern #387. No sale took place and the figure has not been independently confirmed. Included to mark the ceiling of the claims, not to assert a value.\n\nHet structurele punt: De markt van Valve stopt bij ongeveer $1,800.. Marktplaatsen van derden brengen de transactie naar ongeveer $66,000, waar meerdere van hen akkoord gaan, en naar ongeveer $150,000, waar slechts één dat doet. Daarboven is er helemaal geen handelsplatform — de grootste overdrachten van door Valveuitgegeven activa vinden onderhands plaats, tussen particulieren, zonder notering, zonder platformregistratie, zonder identiteitscontrole en zonder rapportage. De overdracht zelf verloopt nog steeds via Steam. Hoe hoger de waarde, hoe minder zichtbaar het is, en de infrastructuur die het ondersteunt, is volledig in handen vValve.\n\nDe laatste twee punten zijn verslagen van anderen, die als zodanig worden aangehaald. Dit project heeft deze niet geverifieerd en baseert zich er niet op voor het trekken van conclusies.\n\nAlle door 419 waargenomen categorieën\n\nBron: https://phishdestroy.io/steam_dossier/nl/elite_skins#register\n\n09 / herkomst en grenzen\nControleer de berekening\n\nWe maken de lokale gegevens en de openbare bron bekend. Het cijfer in de kop heeft betrekking op CSFloat op de datum van vastlegging.\n\nValve's eigen plafond en voorwaarden\n\nSteam Veelgestelde vragen over de Community Market ↗ gearchiveerd op 2026-09-21 ↗ geeft het geschatte maximum van $1,800 aan. De Abonneeovereenkomst ↗ gearchiveerd op 2026-09-21 ↗ stelt de beperkingen voor commercieel gebruik vast.\n\nWaar de prijzen vandaan komen\n\nPrijzen, het aantal genoteerde aandelen en de bandbreedtes van de vrij verhandelbare aandelen zijn ontleend aan de cs2.sh marktgegevens API in het kader van een betaald commercieel abonnement, met behulp van een licentiesleutel. Er is geen enkele marktplaats gescraped en er is geen gebruik gemaakt van marktplaatsaccounts of inloggegevens. De aanbieder bundelt de gegevens van BUFF, Youpin, CSFloat, Skinport, C5Game en de Steam Community Market; alle cijfers zijn weergegeven in USD zoals gerapporteerd. Open het herkomstmanifest ↗ — het registreert de exacte eindpunten, opnametijden en SHA-256-hashwaarden van de onbewerkte momentopnames, zodat een onafhankelijke lezer met een eigen sleutel dezelfde gegevens kan ophalen en elk getal op deze pagina opnieuw kan berekenen.\n\nWat we niet konden verkrijgen\n\nHet aangeschafte abonnement geldt uitsluitend voor de huidige momentopnames. Historische en gearchiveerde eindpunten waren voor ons niet beschikbaar, en Op deze pagina worden geen uitspraken gedaan over trends, koersen uit het verleden of veranderingen in de loop van de tijd. Alles hier is één enkel moment, met een datum.\n\nHet eerdere register van de CSFloat\n\nDe eerste versie van deze tentoonstelling omvatte 245 categorieën uit één CSFloat catalogusmomentopname van 20 september 2026: die momentopname blijft hier staan ↗. Het huidige register is uitgebreider omdat het vijf marktplaatsen omvat in plaats van één. Het gaat om twee afzonderlijke tellingen, die niet bij elkaar mogen worden opgeteld.\n\nVerklaring van Valve inzake specifieke tenuitvoerlegging\n\nValve: update over het ruilen van in-game-items in ‘2016’ ↗ gearchiveerd op 2026-09-21 ↗ is gericht op gokexploitanten die gebruikmaken van OpenID en geautomatiseerde Steam-accounts. Het is beperkter dan een verbod op alle externe marktplaatsen.\n\nInterpretatiegrens\n\nDit zijn aanbiedingen, geen verkopen. Een marktnaam kan betrekking hebben op meerdere fysieke artikelen met verschillende details wat betreft afwerking, patroon of stickers. Dit register geeft geen beeld van de totale marktwaarde of de bedoelValve.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Elite Skins Register — De marktplafond van $1,800"
          },
          {
            "level": 2,
            "id": null,
            "text": "De meetbare ondergrens in dollars"
          },
          {
            "level": 3,
            "id": null,
            "text": "Waarom dit een minimum is en geen schatting"
          },
          {
            "level": 2,
            "id": null,
            "text": "Wat er buiten de limiet valt"
          },
          {
            "level": 3,
            "id": null,
            "text": "★ Butterfly Knife | Doppler (Factory New)"
          },
          {
            "level": 2,
            "id": null,
            "text": "De limiet van Steam zorgt ervoor dat de prijsvorming buiten Steam plaatsvindt"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam sluit de lijst af"
          },
          {
            "level": 3,
            "id": null,
            "text": "Dragon Lore: $10,940.85"
          },
          {
            "level": 3,
            "id": null,
            "text": "Prijs- en overdrachtsverdeling"
          },
          {
            "level": 2,
            "id": null,
            "text": "Ook op de achtergrond is de Dota-2 te zien"
          },
          {
            "level": 3,
            "id": null,
            "text": "Heroïsche, brute halve maan"
          },
          {
            "level": 3,
            "id": null,
            "text": "Cape ‘Dark Artistry’"
          },
          {
            "level": 3,
            "id": null,
            "text": "Beschadigde Powered Star"
          },
          {
            "level": 2,
            "id": null,
            "text": "De bevinding hangt niet af van de exacte bovengrens"
          },
          {
            "level": 2,
            "id": null,
            "text": "Hoe weinig daarvan er daadwerkelijk te koop zijn"
          },
          {
            "level": 3,
            "id": null,
            "text": "AWP | Drakenkennis"
          },
          {
            "level": 3,
            "id": null,
            "text": "M4A4 | Howl"
          },
          {
            "level": 3,
            "id": null,
            "text": "AK-47 | Wild Lotus"
          },
          {
            "level": 3,
            "id": null,
            "text": "AWP | Gungnir"
          },
          {
            "level": 2,
            "id": null,
            "text": "Hoe duurder het artikel, hoe verder het verwijderd is van een zichtbare locatie"
          },
          {
            "level": 2,
            "id": null,
            "text": "Alle door 419 waargenomen categorieën"
          },
          {
            "level": 2,
            "id": null,
            "text": "Controleer de berekening"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve's eigen plafond en voorwaarden"
          },
          {
            "level": 3,
            "id": null,
            "text": "Waar de prijzen vandaan komen"
          },
          {
            "level": 3,
            "id": null,
            "text": "Wat we niet konden verkrijgen"
          },
          {
            "level": 3,
            "id": null,
            "text": "Het eerdere register van de CSFloat"
          },
          {
            "level": 3,
            "id": null,
            "text": "Verklaring van Valve inzake specifieke tenuitvoerlegging"
          },
          {
            "level": 3,
            "id": null,
            "text": "Interpretatiegrens"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/nl/#market-gap-section",
          "https://phishdestroy.io/steam_dossier/nl/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/nl/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/nl/skin_atlas.html#grading",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-above-the-ceiling.json",
          "https://phishdestroy.io/steam_dossier/nl/elite_skins#selected",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://csmarketcap.com/search?minPrice=1800&amp;page=1",
          "https://store.steampowered.com/agreement/?l=english",
          "http://web.archive.org/web/20260921022032/https://store.steampowered.com/agreement/?l=english",
          "https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921021947/https://store.steampowered.com/oldnews/22883",
          "https://phishdestroy.io/steam_dossier/nl/#proxy-bypass-explainer",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/skinport-floor-over-cap.json",
          "https://docs.skinport.com/items",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-float-scarcity.json",
          "https://phishdestroy.io/steam_dossier/nl/elite_skins#register",
          "https://cs2.sh/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/csfloat-catalogue.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/nl/elite_skins.content.json",
      "export_json_sha256": "f5ba3df9a1133a943edc667955ab54c3cdf1c1c0b645ffdc377fcefccadb61dd"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "nl/enforcement_audit.html",
      "language": "nl",
      "title": "De volkstelling Valve wordt niet gepubliceerd — Het Steam-dossier",
      "source_url": "https://phishdestroy.io/steam_dossier/nl/enforcement_audit",
      "source_html_sha256": "94066587994fd9509eab5ce3b123f93eaf04a5910f0ea0b8efe7a6173100c97f",
      "exported_at": "2026-09-29T00:18:21.567Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "enforcement_audit.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/nl/enforcement_audit.pdf?v=print-20260929-v5",
        "sha256": "2c25b1a4a3ed0db18ff131c013c79f1c226929867a8841f00577057a4b5e59b2",
        "bytes": 150968,
        "pages": 13
      },
      "integrity": {
        "signed_object": "enforcement_audit.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "enforcement_audit.content.json.asc",
        "digest_file": "enforcement_audit.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify enforcement_audit.content.json.asc enforcement_audit.content.json",
          "sha256sum -c enforcement_audit.content.json.sha256"
        ]
      },
      "content": {
        "text": "BIJLAGE VI — DE VOLKSTELLING VALVE WORDT NIET GEPUBLICEERD\nHoe groot is de Steam-farm? We hebben zelf geteld.\n\nEr zijn geen officiële cijfers bekend over het aantal automatiseringsaccounts dat op Steam draait. Dit hoeft ook geen geheim te zijn: de Steam-ID-ruimte is een aaneengesloten reeks gehele getallen en Valve deelt de Web API-sleutel uit waarmee deze reeks kan worden doorlopen. Daarom hebben we de grootste groep genomen die zichzelf identificeert — de ArchiSteamFarm-gemeenschap — en hebben we elk lid één keer door de eigen ban-endpoint van Valve gelezen. Dit gebeurt automatisch omdat ASF bij de eerste start automatisch lid wordt van de Steam-groep, tenzij de gebruiker zich expliciet afmeldt of de instelling voor groepslidmaatschap uitschakelt (AutoJoinSteamGroup / Statistieken). Omdat deze instelling standaard is ingeschakeld, omvat het groepslidmaatschap een brede populatie: actieve commerciële botnetwerken met meerdere accounts, hobbyisten die af en toe wat tijd doorbrengen met de software, en gewone spelers die de software op hun persoonlijke account hebben gedraaid en het standaardabonnement nooit hebben opgezegd. Daardoor vormt het lidmaatschap een bruikbare telling van het totale bereik van de software: 10,880,610 totaal aantal accounts (waarvan 5,360,499 bevestigde leden zonder beperkingen die de $5.00-winkelpoort zijn gepasseerd). Vervolgens stelden we de enige vraag die ertoe doet: wat heeft Valve hen nu eigenlijk aangedaan?\n\nWat deze pagina niet is. Dit is geen pleidooi om Valve tien miljoen mensen te verbannen, en het is ook geen klacht over ‘card farmers’. Elk cijfer hieronder staat hier om één reden: Valve doet personen definitief te verbannen, en de reden die het schriftelijk opgeeft is commercieel gebruik van Steam en automatisering. Dit meet hoe diezelfde regel op grote schaal wordt toegepast op hetzelfde gedrag — door een exploitant die onderweg $5.00 ontgrendelingskosten, spellicenties en Market-vergoedingen Valve int. De bevinding betreft de asymmetrie, niet de farm.\n\nHet aantal van 10,88 miljoenDe oplichters die rondlopen (53,5k)Betaalde audit van 100.000 versus gratis audit\n10,880,610Het totale aantal leden van de ASF-groep dat de eigen ban-API van Valve heeft doorgenomen (beperkt + onbeperkt samen)\n88.97%Ik ben nog nooit geblokkeerd — 9,680,599 accounts zijn nog steeds actief\n63.06%Van de geblokkeerde accounts zijn er betaalde ($5+ uitgaven) — 100,000 SRSWOR deel (±0.39% MoE)\n67.77%Van de 51,732 veroordeelde oplichters heeft niemand een verbod op oplichting (volledige telling)\n01 — De schaal\nTien miljoen accounts, waarvan negen op de tien onaangeroerd\n\nEen populatie die zichzelf telt, wordt één keer door het eigen eindpunt van Valve gelezen.\n\nWAAROM HET ZELF TELLEN\nASF sluit zich namens jou aan bij de groep\n\nBij de eerste run ArchiSteamFarm sets Statistieken is standaard ingesteld op ‘true’ en wordt toegevoegd aan de groep ‘SC Farm Steam’ van Archi. Een beheerder moet zich actief afmelden. Het lidmaatschap vormt dus een ondergrens voor het aantal installaties — geen bovengrens. Beheerders die ‘Statistics’ hebben uitgeschakeld, ontbreken in de telling; het werkelijke aantal installaties is dus minstens zo groot.\n\nWAT WE LEZEN\n10,880,610 totaal aantal inzendingen\n\nDe API-ledenlijst leverde in totaal 10,880,610 SteamID64’s op — zowel beperkte als onbeperkte. Op de groepspagina van Steam staan er 5,360,499 (alleen onbeperkte). Elk item is één keer doorgegeven via ISteamUser/GetPlayerBans op 2026-09-23. Vijfenvijftig minuten op één toets.\n\nHET ANTWOORD\n88.97% schoon\n\n1,200,011 is niet onderworpen aan een Steam verbod (11.03%). De andere 9,680,599 er is helemaal niets geregistreerd — geen communityban, geen VAC, helemaal niets. De farm wordt niet opgeruimd. Hij blijft gewoon draaien. Dezelfde clausule, gericht tegen één persoon, is voldoende om die persoon definitief te verwijderen.\n\nVan de 10,880,610 rekeningen, hoeveel Valve zijn er aangeraakt?\n\nDe volledige gescande populatie, onderverdeeld naar het feit of Valve al dan niet een verbod heeft opgelegd. Het rode deel omvat alles wat Valve ooit met deze vloot heeft gedaan.\n\n88.97%nooit verboden\n11.03%\nGeen enkel verbod — 9,680,599 (88.97%)Heeft een Steam-verbod — 1,200,011 (11.03%)\n10,880,610Leden van de ASF-groep zijn gescand\n9,680,599Nooit geblokkeerd — 88.97%\n1,200,011Elk verbod handhaven — 11.03%\n55 minOm alles te tellen, met één API-sleutel\nWat deze vloot al heeft betaald om te kunnen bestaan Valve\n\nGeen schatting van wat de boerderij verdient. Een ondergrens voor wat er al is uitgegeven in de winkel van Valve — afgeleid van de eigen regel van Valve, toegepast op het bovenstaande aantal.\n\nHet aantal 10,880,610 omvat de volledige lijst met ASF-groepsleden zoals die door de API wordt geretourneerd — dit omvat zowel beperkte als onbeperkte accounts. Steam's eigen Beperkte gebruikersaccounts Op de pagina staat vermeld dat beperkte accounts niet meetellen voor Steam groepslidmaatschap (zij worden niet meegeteld in de weergegeven groepsgrootte), maar ze kunnen nog steeds voorkomen in de onderliggende ledenlijst. De onbeperkte deelverzameling — accounts die ten minste $5.00 hebben uitgegeven in de Steam-winkel — is precies 5,360,499 — het getal Steam wordt weergegeven op de groepspagina, die volgens de eigen regel van Steam beperkte accounts uitsluit. De berekening van de ondergrens $5.00 geldt alleen voor die niet-beperkte subgroep.\n\n5,360,499leden zonder beperkingen\n(Steam's weergegeven aantal groepen)\n×\n$5.00Het eigen minimum van Valve\nom niet langer beperkt te zijn\n=\n$26,802,495minimum aan winkeluitgaven\ndoor de onbeperkte deelverzameling\n\nDit is een ondergrens voor het bedrag dat Valve al heeft ontvangen van het onbeperkte deel van de vloot — het is geen schatting van de inkomsten en evenmin een bewering over de winst. De werkelijke uitgaven per account liggen voor de meesten hoger; het cijfer $5.00 is slechts de vereiste minimumdrempel.\n\nDe secundaire opbrengst: tot 66.7% vergoeding over het volume van de geteelde grondstoffen. Naast de toegangsprijs van $26.8M wordt voor elke kaart en elk product dat op de Community Market wordt verkocht, een verplichte minimumvergoeding van twee cent in rekening gebracht (Valve: $0.01 Steam vergoeding + $0.01 uitgeversvergoeding). Bij typische kaarten en rommelartikelen van 3 cent, Valve neemt 2 cent van de 3 cent — een effectieve verlaging van 66.67% ten gunste van Valve, wat het officiële 15%-marketingtarief ruimschoots overtreft.\n\nBelangrijke kanttekening met betrekking tot de populatie: Het lidmaatschap van een groep is geen bewijs dat elk afzonderlijk account een speciale bot is, en het omvat ook niet alle bots op Steam. ASF schrijft accounts standaard automatisch in bij zijn communitygroep zodra deze wordt gestart; tenzij de gebruiker dat configuratievlagje expliciet uitschakelt of deinstelt (AutoJoinSteamGroup), vaste spelers, incidentele spelers en leden van de community blijven op de lijst staan, naast geautomatiseerde farming-vloten. Bovendien wordt bij een Steam-ban geen openbare reden vermeld. De bevinding betreft een empirisch percentage binnen deze aan de software gekoppelde populatie, en geen individueel oordeel over een specifiek account. Geaggregeerd, reproduceerbaar: asf-ban-census-2026-09-23.json.\n\n02 — Aardrijkskunde\nWaar de vloot zich bevindt\n\nSlechts 8.5% van de geblokkeerde accounts hebben überhaupt een land opgegeven. Van de accounts die dat wel hebben gedaan, komt het grootste aandeel uit de Verenigde Staten.\n\nEen Steam-profiel bevat een optioneel veld voor het land. 100,413 van de 1,182,811 geblokkeerde accounts vullen het in — 8.5%.† Binnen die minderheid staan de Verenigde Staten bovenaan met 15.5%, gevolgd door Oekraïne, China en Rusland, terwijl de rest zich uitstrekt in een lange staart over Europa, Latijns-Amerika en Zuidoost-Azië. Niemand controleert de gegevens: Afghanistan staat in de top tien, wat ongeveer overeenkomt met wat het waard is. De overige 91.5% zijn weggelaten in plaats van toegewezen, dus wat volgt is het beeld van een zelfgeselecteerde minderheid — geen kaart van de vloot, en geen basis om te zeggen van waaruit deze wordt aangestuurd.\n\nGeblokkeerde accounts per opgegeven land\n\nTop 15 van landen waarin de 100,413 geblokkeerde accounts zich bevinden die een openbare locatie bekendmaken. Het aandeel heeft betrekking op die subgroep. Beweeg de muis erover voor de aantallen.\n\n0%\n5%\n10%\n15%\n20%\nUnited States\nUkraine\nChina\nRussia\nCanada\nAustralia\nJapan\nBrazil\nGermany\nAfghanistan\nUnited Kingdom\nRomania\nFrance\nPhilippines\nIndia\n\nLocatie gelezen uit GetPlayerSummaries voor de verboden subset. Het veld wordt ingesteld door de accounthouder en door niemand gecontroleerd, dus een VPN-uitgang of een grappige invoer telt net zo zwaar mee als een echte.\n\n03 — Versheid\nRecente posten, geen achterstand uit het verleden\n\nAfgaande op het tijdstip waarop de accounts zijn aangemaakt, is de groep geblokkeerde gebruikers van recente datum; het gaat hier niet om een overblijfsel uit het tijdperk van de ruilkaarten.\n\nAls dit een oude puinhoop was die langzaam wordt opgeruimd, zouden de geblokkeerde accounts vooral uit de beginjaren van de ruilkaarten komen. Het is echter juist het tegenovergestelde. Van de 1,132,852 geblokkeerde accounts waarvan de aanmaakdatum bekend is, 70% zijn in 2020 of later opgericht, en bijna de helft daarvan sinds 2023. Het aantal stijgt van 59,175, dat in 2017 werd vastgesteld, tot een piek van 227,030 alleen al in 2024 gecreëerd. Ze waren allemaal al door de poort van de $5.00-winkel gelopen voordat er een kaart kon worden gescand, dus moest voor elk van hen het toegangstarief worden geïnd.\n\nToen de geblokkeerde accounts werden aangemaakt\n\nHet jaar waarin de 1,132,852 geblokkeerde leden een account hebben aangemaakt, voor zover hun aanmaakdatum bekend is. De periode loopt van 2020 tot en met 2026, en niet van 2013 tot en met 2015, het tijdperk van de ruilkaarten. Piek: 2024. Beweeg de muis erover voor de aantallen.\n\n0k\n63k\n125k\n188k\n250k\n'13\n'14\n'15\n'16\n'17\n'18\n'19\n'20\n'21\n'22\n'23\n'24\n'25\n'26\n70%Van geblokkeerde accounts die in 2020 of later zijn aangemaakt\n227,030Geblokkeerde accounts die in 2024 zijn aangemaakt — het jaar met het hoogste aantal\n51,701De dip van 2021, tussen twee topjaren in — onverklaarbaar\n2003→2026Er zijn gegevens beschikbaar, maar de gegevens hebben betrekking op de afgelopen zes jaar\n\nHet is ontstaan in GetPlayerSummaries voor de geblokkeerde subgroep, ontdaan van dubbele vermeldingen op basis van SteamID64. De aanmaakdatum is de datum waarop het account is aangemaakt, niet de datum waarop het werd geblokkeerd of waarop het met ‘farming’ begon; deze datum wordt hier gebruikt als aanwijzing voor hoe recent de populatie is, niet als bewijs van opzet. Drie zaken die de grafiek niet laat zien:\n\nEen trend na 2024. Een account dat in 2025 of 2026 is aangemaakt, heeft minder tijd gehad om een ban op te bouwen, en 2026 beslaat negen maanden — dus 227,030 → 121,070 → 16,534 duidt op censuur, niet op een daling.\nEen uitvalpercentage. De aanmaakjaren zijn alleen voor geblokkeerde accounts in kaart gebracht, dus er is geen noemer. Alleen al een groeiend aantal gebruikers zou dit patroon opleveren.\nWaarom 2021 in duigen viel. 51,701 bevindt zich tussen 105,821 en 104,641, op minder dan de helft van de afstand tot beide buren. Er is geen openbare verklaring voor; het is zichtbaar gelaten in plaats van afgevlakt.\n04 — Timing\nWanneer Valve in werking treedt, gebeurt dat binnen het eerste jaar\n\nHet voor de hand liggende argument om 88.97% ongewijzigd te laten, is een achterstand. De verouderde verboden wijzen echter op iets anders.\n\nHoe oud was het account toen de blokkering werd opgelegd?\n\nDe leeftijd van het account op het moment van de blokkering, voor de 293,750 geblokkeerde accounts waarvan zowel de aanmaakdatum als de datum van de laatste blokkering bekend is. Meer dan de helft werd al binnen het eerste jaar ontdekt.\n\n0%\n10%\n20%\n30%\n40%\n<6 mo\n33.7%\n6–12 mo\n21.5%\n1–2 y\n20.6%\n2–5 y\n14.3%\n5 y+\n10.0%\n55.1% inside the first year\nBuitenspel in het eerste jaar — 55.1%Later verbannen — 44.9%\n0,80 jaarDe mediane leeftijd van het account op het moment dat de blokkering werd opgelegd\n55.1%Geblokkeerd binnen het eerste jaar na het aanmaken van het account\n33.7%Verboden binnen de eerste zes maanden\n293,750Accounts waarin beide datums voorkomen\n\nDit is het antwoord op het voor de hand liggende tegenargument. Als 88.97% van de vloot onaangetast blijft omdat de handhaving simpelweg traag verloopt — een achterstand die langzaam wordt weggewerkt —, dan zijn de verboden die doen het zou een verouderd beeld geven. Het tegendeel is waar: de mediane leeftijd van de geblokkeerde accounts was negen en een halve maand oud, en een derde — 33.7% — werd binnen zes maanden gepakt. Wanneer Valve op deze populatie inwerkt, gebeurt dat snel. De negen op de tien die nog op de vlucht zijn, staan niet in de rij te wachten.\n\nLeeftijd bij het verbod = aanmaakdatum vanaf GetPlayerSummaries afgetrokken van de verbodsdatum die voortvloeit uit Aantal dagen sinds de laatste blokkering, lees verder 2026-09-23. Deze waarde wordt alleen berekend als beide waarden aanwezig zijn: 293,750 van de 1,200,011 geblokkeerde accounts. De overige accounts geven geen ‘dagen-sinds’-waarde weer en worden weggelaten, niet verondersteld — beschouw dit dus als de vorm van de gedateerde subset, niet van elke blokkering.\n\n05 — Wat het verbod nu eigenlijk inhoudt\nAls Valve in werking treedt, stopt de bot niet\n\nVan de 11% waarvoor een verbod geldt, moet je kijken om welk verbod het gaat.\n\nEen verbod is nog geen verbod. Van de 1,200,011 accounts die Valve heeft gemarkeerd, 99.8% een gemeenschap verbod — een beperking op forums, profielen en groepen die geen enkele invloed heeft op een handelsbot. Het account kan nog steeds kaarten ontvangen, nog steeds ruilen en nog steeds voorraad verplaatsen. 22.2% heeft ten minste één spelverbod en 3.9% een VAC-verbod; de categorieën overlappen elkaar, dus ze worden niet bij elkaar opgeteld. De enige sanctie die daadwerkelijk een einde maakt aan het ruilen, namelijk het economische/ruilverbod, geldt voor 5,214 accounts. We baseren onze conclusie niet op dat getal — handelsverboden zijn over het algemeen zeldzaam bij Steam. De strekking van deze grafiek is eenvoudiger: zelfs het deel Valve doet Touch blijft handelen.\n\nWaarvoor de 11% die zijn verbannen, eigenlijk zijn verbannen\n\nHet aandeel van elk type blokkering ten opzichte van alle 10,880,610 gescande leden. Accounts kunnen meer dan één type blokkering hebben. Beweeg de muis erover voor de aantallen.\n\n0%\n4%\n8%\n11%\n15%\nCommunity ban\nGame ban\nVAC ban\nEconomy / trade ban\n\nEen Steam-verbod heeft geen veld voor de reden, dus geen van deze verboden wordt specifiek toegeschreven aan het verzamelen van kaarten — dit is de mix van aanwezige verbodstypen, naast wat elk type daadwerkelijk beperkt. Een communityverbod houdt de handel niet tegen; het economische/handelsverbod doet dat wel. Totaal: asf-ban-census-2026-09-23.json.\n\n06 — De andere bevolkingsgroep\nDe oplichters Valve laten ons gaan: De 51,732 volledige volkstelling\n\nEen tweede, onafhankelijke lijst — door de gemeenschap bevestigde gevallen van fraude — getoetst aan dezelfde officiële API.\n\nDe groep van de automatiseringsgebruikers zou nog kunnen worden afgedaan als onschuldige nietsnutten. Dat geldt echter niet voor de tweede groep. SteamRep is een al lang bestaande database met reputatiegegevens van de community; een account dat is gemarkeerd als VERBODEN Er is door die gemeenschap iemand als oplichter aangemerkt, op basis van gedocumenteerd bewijs van slachtoffers en chatlogs van transacties. We hebben een 100%-inventarisatie uitgevoerd van alle 51,732 profielen met de status ‘GEBLOKKEERD’ tegen de officiële Web API van Steam (ISteamUser/GetPlayerBans/v1) — en heb alleen de sancties meegeteld die betrekking hebben op oplichting. Een VAC-verbod geldt voor het gebruik van valsspeelsoftware in een spel (aimbots, wallhacks); het heeft geen gevolgen voor een handelaar en vormt geen bewijs Valve van fraude, dus wordt het niet meegeteld als fraudebestrijding.\n\nOver de gehele 51,732-accounttelling heen hebben 67.77% — 35,059 vastgestelde oplichters — GEEN ENKELE op oplichting gerelateerde blokkering van Valve: ze kunnen nog steeds handelen, nog steeds vriendschapsverzoeken sturen naar nieuwe slachtoffers en nog steeds berichten versturen. Slechts 32.23% kregen een community- of handelsverbod opgelegd, en het handelsverbod — de enige maatregel die het overdragen van inventaris daadwerkelijk onmogelijk maakt — geldt voor slechts 18.81% (9,731 accounts). Nog eens 12.81% (6,627 accounts) hebben VAC spelverboden opgelegd gekregen, uitsluitend vanwege valsspelen in het spel, terwijl ze volledig onbeperkt kunnen blijven Steam handelen.\n\nBevestigde oplichters, op basis van de vraag of Valve een oplichtingsgerelateerde blokkering heeft opgelegd (volledige telling)\n\nAlle 51,732 SteamRep-GEBLOKKEERDE profielen, uitgesplitst naar het feit of Valve een community- of handelsverbod heeft opgelegd. VAC en spelverboden zijn buiten beschouwing gelaten — deze hebben geen betrekking op fraude. Beweeg de muis over de tekst voor de aantallen.\n\n0%\n18%\n35%\n53%\n70%\nNo scam-relevant ban\nCommunity or trade ban\n0%\n6%\n13%\n19%\n25%\nCommunity ban\nTrade / economy ban\nVAC (not fraud)\nGame ban\n51,732SteamRep gecontroleerde BANNED-profielen — 100% volledige telling\n35,059Heeft geen verbod in verband met oplichting (67.77%)\n18.81%Voer het handelsverbod door dat een einde maakt aan oplichting (9,731)\n32.23%Het aandeel Valve kreeg te maken met een gemeenschaps- of handelsverbod (16,673)\n\nSteamRep is een door de gemeenschap beoordeelde reputatiedatabase van een derde partij, geen Valve-beoordeling — en dat is nu juist het punt: extern bewijs, afgemeten aan wat Valve zelf heeft gedaan. Alle 51,732-profielen die uit de canonieke export waren VERBANNEN, werden rechtstreeks vergeleken met ISteamUser/GetPlayerBans/v1. Onder „frauderelateerd” wordt verstaan: een verbod op deelname aan de community of op economische activiteiten/handel; VAC (12.81%) en spelverboden (3.86%) worden apart geteld, omdat deze betrekking hebben op valsspelen en niet op fraude. Volledige auditdataset: steamrep_steam_bans.csv.\n\nTwee populaties, één bevinding\n\nDit zijn niet dezelfde mensen en ook niet hetzelfde gedrag. Het ene betreft tien miljoen geautomatiseerde accounts; het andere betreft drieënvijftigduizend veroordeelde oplichters. Wat ze gemeen hebben, is de vorm van het resultaat: negen op de tien landbouwrekeningen worden nooit aangeraakt, en meer dan twee derde (67.77%) van de bevestigde oplichters krijgt geen sanctie die gericht is op fraude. De community-ban Valve legt weliswaar vrijelijk beperkingen op aan forums en profielen, maar niet aan het handelen. De meldknop, de reputatiedatabase, de ban die een oplichting een halt toeroept: ze zijn er allemaal, maar worden te weinig gebruikt. Vergelijk dat eens met de gearchiveerde afwijzingen in het hoofddossier, waar hetzelfde bedrijf één enkel account definitief verwijdert en commercieel gebruik en automatisering als reden aanvoert — de clausule is niet slapend, maar scherp.\n\n07 — De $5.00-accountgate en accountkaping\nDe empirische controle van 100,000-accounts: botnets zijn geen gratis wegwerpartikelen\n\nStatistische steekproeflogica en wiskundig bewijs: waarom het nemen van willekeurige andere 100,000-waarden precies hetzelfde resultaat oplevert.\n\nHet belangrijkste verweer van Valve tegen toezichthouders en instanties voor consumentenbescherming is dat geautomatiseerde oplichting en ‘farming’ worden uitgevoerd via tijdelijke, gratis ‘wegwerpaccounts’ die snel worden geblokkeerd. Volgens de gepubliceerde regels van Valve is een account Beperkt totdat het ten minste 5.00 USD in de Steam-store, waardoor het geen toegang heeft tot handelsactiviteiten, vriendschapsverzoeken en API-functies. We hebben deze bewering rechtstreeks gecontroleerd door de monetisatiestatus te testen van een representatieve, wiskundig rigoureuze steekproef van 100,000 geblokkeerde Steam accounts ontleend aan ons 1,182,811-corpus van profielmetadata.\n\nBEMONSTERINGSPROTOCOL (SRSWOR)\n100,000 Onbevooroordeelde doorsnede\n\nOntleend aan N = 1,182,811 unieke geblokkeerde Steam accounts, geselecteerd met behulp van eenvoudige willekeurige steekproeftrekking zonder teruggave via een cryptografisch uniforme PRNG. Elk account had een identieke kans om geselecteerd te worden van P = n / N ≈ 8.45%, waardoor de overlevings- en activiteitsvertekening volledig worden geëlimineerd.\n\nWISKUNDIG BEWIJS\nFoutmarge < ±0.4%\n\nDe formule voor de eindige-populatiecorrectie (FPC) toepassen bij een 99% Betrouwbaarheidsinterval (Z = 2,576):\nMoE = Z × √[p(1-p)/n] × √[(N-n)/(N-1)] ≈ ±0.39%\n\nREPRODUCEERBAARHEID\nWaarom elk bedrag van 100.000 hetzelfde opbrengt\n\nOmdat de foutmarge bij een betrouwbaarheidsniveau van 99% begrensd is tot ±0.4%, het is wiskundig gegarandeerd dat elke andere onafhankelijke steekproef uit de 100,000-rekening binnen 63.06% ± 0.39% valt (62.67% tot 63.45%). De steekproef is representatief voor de gehele groep van 1,18 miljoen verbannen personen.\n\nDe resultaten van de controle weerleggen het argument van de „wegwerpbot“ volledig. Van de 100,000 accounts die via de verouderde XML-profielinterface van Steam zijn gecontroleerd: 61,490 accounts (63.06% van de geclassificeerde accounts) zijn accounts zonder limiet (betaalde accounts) die ten minste $5.00 hebben uitgegeven aan Steam. Alleen 36,021 (36.94%) zijn beperkte gratis accounts, terwijl 2,489 niet waren geconfigureerd of privé waren.\n\n100,000 Geblokkeerde accounts: Betaald ($5+ uitgaven in de winkel) versus gratis account met beperkte status\n\nEmpirische controle van 100,000 willekeurig geselecteerde geblokkeerde accounts. Meer dan 63% hebben de betaalde financiële poort van Valve gepasseerd. Beweeg de muis erover voor de aantallen.\n\n0%\n16%\n33%\n49%\n65%\nNon-limited (Paid ≥ $5.00)\nLimited (Free < $5.00)\n100,000Steekproefpopulatie (SRSWOR, N = 1,18 miljoen)\n63.06%Betaalde accounts zonder beperkingen (61,490-accounts)\n±0.39%Foutmarge bij een betrouwbaarheidsinterval van 99%\n~745,800Geëxtrapoleerde betaalde accounts in een corpus van 1,18 miljoen geblokkeerde accounts\nDe structurele realiteit: het opschonen van rekeningen op industriële schaal\n\nWaarom zouden 63% van de onderzochte geblokkeerde accounts betaalde accounts zijn die echt geld hebben uitgegeven in de winkel van Valve? Botnetbeheerders geven geen miljoenen uit eigen zak uit aan wegwerpaccounts. Deze verhouding onderstreept de omvang van gecompromitteerde en gekaapte accounts die door het ecosysteem circuleren.\n\nDeze schaal is direct waarneembaar op ondergrondse platforms: op marktplaatsen zoals FSB Market (geanonimiseerde naam; de oorspronkelijke naam wordt hier niet vermeld), via 550,000 Steam rekeningen (logbestanden van hackers, phishing-gegevens, credential stuffing) worden op elk moment actief te koop aangeboden (phishdestroy.io/live-intel). De markt verifieert kopers en verkopers met behulp van Valve’s eigen Steam OpenID, en noch FSB Market noch het bijbehorende forum wordt geblokkeerd door het linkfilter van Valve.\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\nZoals vastgesteld in paragraaf 06, onderneemt Valve geen proactieve maatregelen om deze frauduleuze activiteiten te bestrijden: 67.77% van de door de community bevestigde oplichters hebben geen enkele blokkering wegens oplichting op Steam, en 88.97% van het automatiseringspark blijft volledig onaangetast. De accounts kunnen vrij circuleren, verifiëren zich via officiële API’s en handelen vrijwel ongestraft binnen het hele ecosysteem.\n\nSchema van forensisch bewijs en handhavingsarchitectuur\nInteractief overzicht van 10,88 miljoen gescande accounts, onderverdeeld in 100.000 empirische segmenten en 53.500 bevestigde oplichters · Klik op de links om het ruwe bewijsmateriaal te bekijken\nNiveau 01 · 10,88 miljoen automatiseringsvlootregistratie\nDe grootste groep die zichzelf als automatiseringsprogramma identificeert op Steam, is achtereenvolgens door de officiële blokkerings-API van Valve gegaan. Dit bewijst dat commerciële botvlooten straffeloos op 88.97% opereren, terwijl ze tientallen miljoenen aan toetredingskosten betalen.\n9,680,599 88.97% Actief & Ongerept\nAccounts waarop geautomatiseerde software draait en die geen enkele vorm van blokkering in hun geschiedenis hebben.\nOnbewerkte JSON-gegevens van de volkstelling (1,2 KB) ↗Raadpleeg paragraaf 01 ↗\n$26,802,495 Minimale omzet uit directe winkelverkopen\nVerzameld door Valve van 5,360,499 leden zonder beperkingen die de minimale toetredingsdrempel van $5.00 hebben overschreden.\nControle van de kaarteconomie ↗Valve $5 Veelgestelde vragen over de regels ↗\n1,200,011 11.03% Gemarkeerde subset\n99.8% geldt uitsluitend een verbod op cosmetische transacties; de handel blijft open op 99.95% van de rekeningen.\nOverzicht per type verbod ↗Geblokkeerde database (60,4 MB) ↓\nNiveau 02 · Empirische steekproefcontrole van 100,000-rekeningen (N = 1,182,811)\nEen representatieve steekproef van 2 is geëvalueerd via verouderde XML-eindpunten. Wiskundig aangetoonde foutmarge < ±0 bij een betrouwbaarheidsinterval van 1. Dit weerlegt de bewering dat verboden bots gratis wegwerpaccounts zijn.\n61,490 (63.06%) Betaalde accounts zonder limiet ($5+ uitgaven)\nMeer dan 63% van de geblokkeerde accounts betreft betaalde transacties. Dit komt neer op ongeveer 745,800 betaalde accounts ($3.73M+ drempel) in de groep geblokkeerde accounts.\nBeperkte resultaten (CSV, 2,1 MB) ↓Forensisch rapport 100k ↗\n36,021 (36.94%) Beperkte gratis accounts (< $5.00)\nDe minderheid van de geblokkeerde profielen die voldoen aan het profiel van Valve als „wegwerpbot“. De 2,489-accounts waren niet geconfigureerd of privé.\nCSV-bestand met 100.000 steekproeven (8,5 MB) ↓Uitgavenanalyse MD ↗\n34.67% tegen 63.93% Audit inzake profielopschoning\nValve heeft de bijnamen op 34,673 accounts gewist en vervangen door de ruwe SteamID64, maar heeft de aangepaste namen en avatars op 63,928 geblokkeerde accounts volledig ongewijzigd gelaten.\nAfdeling Desinfectie ↗Overzicht Roadmap ↗\n34.59% Legacy Oude accounts (aangemaakt tussen 2003 en 2019)\nMeer dan een derde van de geblokkeerde accounts werd 5 tot 20+ jaar geleden aangemaakt, wat aantoont dat er op industriële schaal accounts van spelers die al lang meespelen (Steam) zijn gekaapt.\nLeeftijdskronologie ↗Afwijzingen van ondersteuning ↗\nNiveau 03 · 51,732 SteamRep Overzicht van bevestigde oplichters\nVolledige 100%-lijst van door de community veroordeelde fraudeurs, inclusief chatlogs van slachtoffers en transactiebewijzen, vergeleken met officiële Steam-API’s voor verboden accounts. Bewijst dat de handhaving systematisch tekortschiet.\n35,059 (67.77%) Geen verbanningen wegens oplichting (volledige straffeloosheid)\nMeer dan twee derde van de geverifieerde fraudeurs heeft geen verbod op deelname aan de community of op handel van Valve. Ze zijn volledig actief om te handelen en nieuwe slachtoffers te werven.\nSteamRep API-verboden (2,6 MB) ↓SteamRep Auditverslag ↗\n9,731 (18.81%) Economie / Handelsverboden\nDe enige sanctie die de verkoop van de voorraad onmogelijk maakt. Komt voor bij minder dan een vijfde van de bevestigde oplichters.\nSteamRep Bron (2,1 MB) ↓Raadpleeg paragraaf 06 ↗\n6,627 (12.81%) Onterechte schorsingen wegens valsspelen (alleen VAC)\nGeblokkeerd vanwege het gebruik van aimbots en wallhacks in games, terwijl hun Steam handels- en phishing-mogelijkheden 100% actief blijven.\nVAC Analyse van irrelevantie ↗Tijdlijn beveiliging ↗\nNiveau 04 · Wiki-vandalisme & inbreuken op de infrastructuur in augustus 2026\nHet vervalsen van interne ontwikkelaarsdocumentatie, het onderdrukken van community-redacteuren en tekortkomingen in de beveiliging van de perimeter zijn vastgelegd in het bewijsmateriaalpakket.\n1,200+ Redactie VDC Wiki-conflictregisters\nCommunityredacteuren die probeerden phishinglinks en spamsjablonen te verwijderen, werden systematisch geblokkeerd door geautomatiseerde filters, terwijl Valve medewerkers de waarschuwingen negeerden.\nRapport over conflicten in Rusland (127 KB) ↗Classificatierapport (66 KB) ↗\n12 TB zonder authenticatie Augustus 2026: Verlies van bedrijfsmiddelen (CWE-284)\nValve heeft wekenlang 12 terabyte aan interne code en prototypeversies op een openbaar eindpunt zonder authenticatie gehost.\nValve Dossier over incompetentie (43 KB) ↗Bewijsarchief ↗\nInbreuk bij CEVA Logistics Augustus 2026: Lek van persoonsgegevens van klanten\nNamen, adressen en telefoonnummers van kopers van Europese Steam Deck-producten zijn uitgelekt via de logistieke partner van Valve, wat tot een golf van phishing-aanvallen heeft geleid.\nIncidentrapport ↗Handhavingsoverzicht ↗\n\nBemonsteringsartefact: banned_100k_slice.csv (100,000 rekeningen). Resultaten van de controle: slice_100k_limited_results.csv. Volledig analytisch rapport: BANNED_100K_FORENSIC_ANALYSIS.md.\n\n08 — Methode en beperkingen\nHoe dit werd geïnterpreteerd, en wat er niet wordt beweerd\n\nDrie openbare populaties, één openbare API, rigoureuze statistische steekproeven.\n\nUITVOERING & REFERENTIES\n\nDe ASF-enquête, de 100,000-account SRSWOR-segment en de SteamRep-kruiscontrole werden uitgevoerd door PhishDestroy deelnemers onder hun eigen Steam-accounts en Web API-sleutels, als onderdeel van het openbare werk van de Coalitie op het gebied van phishing en het verbieden van oplichting. De auteur van dit dossier beschikt niet over een Steam Web API-sleutel en heeft zelf geen live scan uitgevoerd. Het samenvoegen, hashen, verifiëren en publiceren vond plaats op basis van de output van de deelnemers.\n\nBevolking\tWaar het vandaan kwam\tWat er werd voorgelezen\nASF-leden\n10,880,610\tDe openbare ledenlijst van de ArchiSteamFarm Steam-communitygroep. Op de groepspagina van Steam worden 5,360,499 leden weergegeven (alleen niet-beperkte accounts); de API-ledenlijst leverde in totaal 10,880,610 vermeldingen op, inclusief beperkte accounts. De gebruiker wordt bij de eerste keer opstarten automatisch lid van de groep, tenzij hij de standaardinstelling voor het lidmaatschap van de groep expliciet uitschakelt in de configuratie (AutoJoinSteamGroup / Statistieken), wat betekent dat de ledenlijst bestaat uit commerciële botclusters, individuele ‘card idlers’ en gewone gamers die de standaardinstelling hebben laten staan.\tGetPlayerBans voor elk lid (blokkeringsvlaggen); GetPlayerSummaries op aanmaakdatum en land. In batches van 100 ID’s, ontdubbeld op basis van SteamID64.\n100.000 geblokkeerde accounts SRSWOR Slice\n100,000\tEen representatieve steekproef, uniform willekeurig en zonder teruggave getrokken uit de verzameling van 1,182,811 geblokkeerde accounts ($P = 8,45\\%$). De correctie voor een eindige populatie levert een foutmarge op van $\\pm 0,39\\%$ bij een betrouwbaarheidsniveau van 99% ($Z = 2,576$).\tInkomsten genereren en de status van een beperkt account (isLimitedAccount) gecontroleerd via de verouderde XML-profielinterface van Steam (?xml=1) via gedistribueerde proxy-pijplijnen. Bevestigt de status 63.06% (betaald).\nSteamRep oplichters\n51,732\tVolledige 100% telling van alle profielen die als BANNED zijn gemarkeerd in de SteamRep reputatiedatabase van de community (in totaal 51,732 profielen). Er is geen steekproef of filtering toegepast.\tISteamUser/GetPlayerBans/v1 voor alle 51,732-accounts, gekruist met de SteamRep-status. Bevestigt dat 67.77% vrij is van eventuele verboden wegens oplichting.\nWat wordt geclaimd\n\nAlleen empirische percentages en statistisch afgebakende schattingen. Binnen de automatiseringspopulatie hebben 88.97% geen blokkering; de geblokkeerde subgroep is recenter (70% sinds 2020). Bij de empirische controle van de 100,000-accounts zijn 63.06% van de geblokkeerde accounts betaalde (niet-beperkte) accounts, met een wiskundig bewezen foutmarge van minder dan ±0.4%. Van de 51,732 bevestigde oplichters hebben 67.77% geen blokkering die verband houdt met oplichting. Elk cijfer is reproduceerbaar via de eigen Web API van Valve.\n\nWat niet wordt geclaimd\n\nEen Steam-verbod bevat geen veld voor de reden, dus geen enkel verbod hier wordt aan een specifieke oorzaak toegeschreven. Lidmaatschap van een groep is geen bewijs dat een account een geautomatiseerde bot is: aangezien ASF het lid worden van groepen standaard toestaat, tenzij dit handmatig wordt uitgeschakeld, bestaat de populatie uit een mix van commerciële multi-account-farms en persoonlijke accounts van gewone spelers en hobbyisten. Het land wordt door de gebruiker zelf opgegeven, en een vermelding met SteamRep is een uitspraak van de community, geen gerechtelijke uitspraak. Er worden geen namen genoemd.\n\nWaarom dit belangrijk is\n\nValve beschikt over dezelfde API, een eigen database en de redenen voor blokkering die deze scan niet kan zien. Het kan deze zoekopdracht binnen enkele seconden uitvoeren over het gehele ID-bereik. De meting waarmee een externe partij een handhavingsclaim met betrekking tot een nummer kan controleren, is nog nooit gepubliceerd door de enige partij die deze met volledige nauwkeurigheid kan produceren. Dit is de externe schatting, die wordt gegeven zodat de vraag met een cijfer kan worden gesteld.\n\nLees verder: de kaarteconomie die deze bevolkingsgroep beheert → · toegang en diefstal tegengaan → · het volledige dossier →",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Hoe groot is de Steam-farm? We hebben zelf geteld."
          },
          {
            "level": 2,
            "id": null,
            "text": "Tien miljoen accounts, waarvan negen op de tien onaangeroerd"
          },
          {
            "level": 3,
            "id": null,
            "text": "ASF sluit zich namens jou aan bij de groep"
          },
          {
            "level": 3,
            "id": null,
            "text": "10,880,610 totaal aantal inzendingen"
          },
          {
            "level": 3,
            "id": null,
            "text": "88.97% schoon"
          },
          {
            "level": 3,
            "id": null,
            "text": "Van de 10,880,610 rekeningen, hoeveel Valve zijn er aangeraakt?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Wat deze vloot al heeft betaald om te kunnen bestaan Valve"
          },
          {
            "level": 2,
            "id": null,
            "text": "Waar de vloot zich bevindt"
          },
          {
            "level": 3,
            "id": null,
            "text": "Geblokkeerde accounts per opgegeven land"
          },
          {
            "level": 2,
            "id": null,
            "text": "Recente posten, geen achterstand uit het verleden"
          },
          {
            "level": 3,
            "id": null,
            "text": "Toen de geblokkeerde accounts werden aangemaakt"
          },
          {
            "level": 2,
            "id": null,
            "text": "Wanneer Valve in werking treedt, gebeurt dat binnen het eerste jaar"
          },
          {
            "level": 3,
            "id": null,
            "text": "Hoe oud was het account toen de blokkering werd opgelegd?"
          },
          {
            "level": 2,
            "id": null,
            "text": "Als Valve in werking treedt, stopt de bot niet"
          },
          {
            "level": 3,
            "id": null,
            "text": "Waarvoor de 11% die zijn verbannen, eigenlijk zijn verbannen"
          },
          {
            "level": 2,
            "id": null,
            "text": "De oplichters Valve laten ons gaan: De 51,732 volledige volkstelling"
          },
          {
            "level": 3,
            "id": null,
            "text": "Bevestigde oplichters, op basis van de vraag of Valve een oplichtingsgerelateerde blokkering heeft opgelegd (volledige telling)"
          },
          {
            "level": 4,
            "id": null,
            "text": "Twee populaties, één bevinding"
          },
          {
            "level": 2,
            "id": null,
            "text": "De empirische controle van 100,000-accounts: botnets zijn geen gratis wegwerpartikelen"
          },
          {
            "level": 3,
            "id": null,
            "text": "100,000 Onbevooroordeelde doorsnede"
          },
          {
            "level": 3,
            "id": null,
            "text": "Foutmarge < ±0.4%"
          },
          {
            "level": 3,
            "id": null,
            "text": "Waarom elk bedrag van 100.000 hetzelfde opbrengt"
          },
          {
            "level": 3,
            "id": null,
            "text": "100,000 Geblokkeerde accounts: Betaald ($5+ uitgaven in de winkel) versus gratis account met beperkte status"
          },
          {
            "level": 3,
            "id": null,
            "text": "De structurele realiteit: het opschonen van rekeningen op industriële schaal"
          },
          {
            "level": 2,
            "id": null,
            "text": "Hoe dit werd geïnterpreteerd, en wat er niet wordt beweerd"
          },
          {
            "level": 3,
            "id": null,
            "text": "Wat wordt geclaimd"
          },
          {
            "level": 3,
            "id": null,
            "text": "Wat niet wordt geclaimd"
          },
          {
            "level": 3,
            "id": null,
            "text": "Waarom dit belangrijk is"
          }
        ],
        "links": [
          "https://help.steampowered.com/en/faqs/view/71D3-35C2-AD96-AA3A",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/asf-ban-census-2026-09-23.json",
          "https://phishdestroy.io/steam_dossier/nl/VALVE_EVIDENCE_PACK/databases/steamrep_steam_bans.csv",
          "https://phishdestroy.io/live-intel/?category=steam",
          "https://phishdestroy.io/steam_dossier/nl/#proxy-bypass-explainer",
          "https://phishdestroy.io/steam_dossier/nl/card_economy.html",
          "https://phishdestroy.io/steam_dossier/nl/VALVE_EVIDENCE_PACK/databases/banned_archiasf_massive.csv",
          "https://phishdestroy.io/steam_dossier/nl/VALVE_EVIDENCE_PACK/databases/slice_100k_limited_results.csv",
          "https://phishdestroy.io/steam_dossier/nl/VALVE_EVIDENCE_PACK/reports/BANNED_100K_FORENSIC_ANALYSIS.md",
          "https://phishdestroy.io/steam_dossier/nl/VALVE_EVIDENCE_PACK/databases/banned_100k_slice.csv",
          "https://phishdestroy.io/steam_dossier/nl/VALVE_EVIDENCE_PACK/reports/STEAM_BANNED_LIMIT_ANALYSIS.md",
          "https://phishdestroy.io/steam_dossier/nl/VALVE_EVIDENCE_PACK/INVESTIGATION_OVERVIEW.md",
          "https://phishdestroy.io/steam_dossier/nl/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/nl/VALVE_EVIDENCE_PACK/reports/STEAMREP_VS_STEAM_AUDIT.md",
          "https://phishdestroy.io/steam_dossier/nl/VALVE_EVIDENCE_PACK/databases/SteamRep_Profiles_BannedCaution_2024.csv",
          "https://phishdestroy.io/steam_dossier/nl/security_timeline.html",
          "https://phishdestroy.io/steam_dossier/nl/VALVE_EVIDENCE_PACK/reports/russian_conflicts_report.json",
          "https://phishdestroy.io/steam_dossier/nl/VALVE_EVIDENCE_PACK/reports/classification_report.json",
          "https://phishdestroy.io/steam_dossier/nl/VALVE_EVIDENCE_PACK/reports/VALVE_INCOMPETENCE_REPORT.md",
          "https://phishdestroy.io/steam_dossier/nl/steam_evidence_archive.html",
          "https://phishdestroy.io/steam_dossier/nl/steam_enforcement_evidence.html",
          "https://phishdestroy.io/steam_dossier/nl/#insider-threat",
          "https://phishdestroy.io/steam_dossier/nl/"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/nl/enforcement_audit.content.json",
      "export_json_sha256": "abce833b3381e3d5bd121bb26a10b219981e3e80928631118166fe53a3efc4d4"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "nl/index.html",
      "language": "nl",
      "title": "Het Steam-dossier: regels, trajecten en verantwoordingsplicht",
      "source_url": "https://phishdestroy.io/steam_dossier/nl/index",
      "source_html_sha256": "e57dcfe8038d943fb3e4d68976c296e2032a29bb2a1b7adee972cd3a24776972",
      "exported_at": "2026-09-29T00:18:29.803Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "exhibit-gallery-section",
            "source": "https://phishdestroy.io/steam_dossier/nl/index#exhibit-gallery-section"
          }
        ],
        "raster_images_replaced": 2
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "index.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/nl/index.pdf?v=print-20260929-v5",
        "sha256": "97208c0db9d5f5b3cefd75daf3b614456486140401f56295dbe8a2e1038e637d",
        "bytes": 982387,
        "pages": 108
      },
      "integrity": {
        "signed_object": "index.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "index.content.json.asc",
        "digest_file": "index.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify index.content.json.asc index.content.json",
          "sha256sum -c index.content.json.sha256"
        ]
      },
      "content": {
        "text": "Hoofdstuk 1 — Samenvatting van de zaak\nDe regel. Het record. De onbeantwoorde vragen.\nContext en bronbeperkingen\n\nZes bevindingen, die elk zijn gekoppeld aan een gedateerd openbaar document. De gedetailleerde hoofdstukken volgen dezelfde volgorde: technisch dossier (deel A), regels en handhavingsdossier (deel B), wettelijke kaders (deel C), en vervolgens de bijlagen met de belangrijkste bewijsstukken.\n\nZes bevindingen. Elk daarvan koppelt een schriftelijke regel aan een gedateerd document en aan een vraag die aan de hand van het bewijsmateriaal kan worden getoetst.\n\n1. Authentificatiehosts met afzonderlijke domeinen — 44 routes · 26 gesplitste paren\n\nDe gegevens in het live-register 44 platforms die zich authenticeren via een afzonderlijk registreerbaar domein. Er zijn nog vijf routes die in afwachting van verificatie zijn en waarvoor nog geen RDAP-datum is vastgesteld; als deze worden toegevoegd, komt het totaal op 47. Ze zijn niet meegeteld in het aantal van 44 en komen niet voor in de leeftijdsgrafiek. — 27 met een gepubliceerd bewijsbestand per route en 17 die handmatig zijn verzameld, apart vermeld. In 26 filter-split-paren het hoofddomein is GEBLOKKEERD in het Steam Link Filter, terwijl de proxy die de inloggegevens bevat dat niet is. Dit zijn geen wegwerpdomeinen: csgogem.com wordt geblokkeerd, terwijl api.csgem.com, de host met de login Steam, is sinds maart 2014 geregistreerd — 12 jaar en 6 maanden. Valve ontvangt die hostnaam bij elk OpenID-verzoek en toont deze aan de gebruiker op zijn eigen inlogpagina. De volledige tabel, de leeftijden per route en de herkomst zijn te vinden in paragraaf 3.\n\nVolg de route →\n2. 2016: het mechanisme kreeg een naam en de deadline werd vastgesteld\n\nOp 13 juli 2016 heeft Valve openbaar beschreven hoe goksites gebruik maakten van Steam OpenID en geautomatiseerde handelsaccounts, en in de kennisgevingen van zijn raadsman van 20 juli 2016 werd een termijn van tien dagen gesteld. Sindsdien is er geen handhavingsrapport per exploitant meer gepubliceerd. Tien jaar na het verstrijken van die termijn wordt hetzelfde genoemde mechanisme nog steeds gebruikt op authenticatiehosts met afzonderlijke domeinen die op 2026-09-21 geen Link Filter-blokkering retourneerden.\n\nLees de open brief aan de WSGC →\n3. Correlatie van apparaten, op briefpapier van de raadsman\n\nIn de hier weergegeven correspondentie beschreef de raadsman van Valve een correlatie op apparaatniveau waarbij één apparaat aan meerdere accounts wordt gekoppeld — een mogelijkheid waarvan de klantenservice van Steam gebruikers eerder had verteld dat deze technisch niet haalbaar was. De vraag is welke gegevens op apparaatniveau Valve in zijn bezit heeft en op welke gronden accounthouders de toegang daartoe wordt geweigerd.\n\nLees het memorandum →\n4. Twee reacties op het verzoek om toegang. In het ene geval werden de gegevens niet vrijgegeven, in het andere geval werden ze gelekt.\n\noktober 2025: De raadsman van Valve reageerde op een verzoek op grond van artikel 15 met een bijlage van 830 pagina’s waarin de geschrapte passages over de tekst heen zijn geschreven in plaats van te worden verwijderd — 902,270 tekens met een standaard extractietool weer naar buiten komen, inclusief de identificatiegegevens van derden die juist door die blokkades moesten worden achtergehouden. Artikel 15, lid 4, is de reden waarom die blokkades bestaan. september 2026: Ticket HT-2YBP-F7JP-D4VB werd na drie dagen afgesloten met een link naar de zelfbedieningspagina ‘Accountgegevens’ — geen gegevens, geen vermelde rechtsgrondslag. De termijn van één maand krachtens artikel 12, lid 3, was op het moment van publicatie nog niet verstreken; het bezwaar heeft betrekking op de inhoud.\n\nLees de redactiecontrole →Lees het ticketdossier →\n5. De markt boven het plafond van Steam\n\nSteam beperkt de marktkapitalisatie tot ongeveer $1,800. Op vijf marktplaatsen in een verouderd momentopname (23 september 2026), 248 CS2-productcategorieën door twee of meer van hen afzonderlijk boven die bovengrens worden geprijsd, en alle 248 ontbreken in Steam; een gloednieuwe Dragon Lore is verkrijgbaar vanaf $10,941 over 389 exemplaren die op alle vijf platforms staan vermeld (het cijfer voor uitsluitend CSFloat in paragraaf 13, afkomstig uit de momentopname van 20 september, bedraagt $10,623.95 over 62 aanbiedingen). Om tegen die prijzen te verkopen is een extern platform nodig, terwijl de overdracht van items nog steeds via Steam verloopt.\n\nVolg de koers en de overschrijving →\n6. De regel is duidelijk; het audittraject is dat niet\n\nDe abonneeovereenkomst reserveert Steam voor persoonlijk, niet-commercieel gebruik, verbiedt commerciële exploitatie tenzij uitdrukkelijk toegestaan, verbiedt scripts en bots, en staat beëindiging van het account toe. Valve paste die bepalingen in 2016 toe op gokexploitanten. Los daarvan heeft Valve, volgens het technische account van CSFloat, de dienst gesloten IEconItems_730/GetPlayerItems in 2017, waarbij de openbare toegang tot de originele item-ID's werd opgeheven (er is geen changelog met Valve gevonden).\n\nPlaats de regel naast het netwerk →\n2016 / Schriftelijk verzoek 10 dagen\nUiterste termijn in de kennisgevingen van Valve raadsman aan goksites van juli 2016. Open brief aan de WSGC: paragraaf 2.\n2017 / Openbaar controlespoor Toegang via ID geblokkeerd\nCSFloat registreert het verlies van originele item-ID’s.\nCorrespondentie met de raadsman Correlatie tussen apparaten\nEén apparaat dat in verband wordt gebracht met tientallen gestolen accounts.\nRouteregister Geblokkeerd, maar nog steeds aan het inloggen\nDe regel: De verklaring van Valve uit 2016 verbiedt het exploiteren van een gokbedrijf via Steam OpenID. Het verslag: Er staan 26 hoofddomeinen in het Link Filter, terwijl de host waarop de Steam-login van elk domein draait, al — die van csgogem.com draait al 12 jaar en 6 maanden.\nParagraaf 2 — Open brief\nOpen brief aan de Kansspelcommissie van de staat Washington\n\nTien dagen werden tien jaar. De vraag die de Commissie in 2016 aan Valve stelde, is niet beantwoord met een overzicht per exploitant; in deze brief wordt de Commissie verzocht de zaak opnieuw in behandeling te nemen.\n\nOMROEPBERICHT · COMMISSIE VOOR KANSSPELEN VAN DE STAAT WASHINGTON\n\nTien dagen werden tien jaar.Open het dossier opnieuw.\n\nAan de Kansspelcommissie van de staat Washington:\n\nIn 2016 vroeg directeur David Trujillo aan Valve om aan te tonen wat het had ondernomen om het gebruik van Steam-skins voor gokdoeleinden een halt toe te roepen. De toenmalige voorzitter Chris Stearns en de Commissie stonden tegenover een sector die was gebaseerd op door Valve uitgegeven items en Steam-overdrachten. Beide mannen hebben inmiddels hun functies bij de Commissie neergelegd. De vraag die zij aan Valve hebben gesteld, is nog steeds actueel.\n\nDe algemeen juridisch adviseur van Valve, Karl Quackenbush, gaf gokexploitanten tien dagen de tijd om het commerciële gebruik van Steam-accounts te staken. In zijn reactie aan uw Commissie in oktober ontkende Valve dat het gokken faciliteerde, verklaarde het dat het aan meer dan veertig websites sommatiebrieven had gestuurd en dat het de bijbehorende accounts had geblokkeerd. Het verdedigde tevens het behoud van Steam-transacties en OpenID, omdat deze diensten ten goede kwamen aan klanten en gameontwikkelaars. Dat was een blijk van machtsuitoefening. Dat verdient een toetsing, geen blind vertrouwen.\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\nNaar onze mening bleek uit het antwoord van Valve niet dat de gekozen handhavingsmaatregel in verhouding stond tot de omvang van het netwerk dat het beschreef. Een dreigbrief aan een exploitant is niet hetzelfde als een blijvende blokkering van de Steam-accounts, de handelsinfrastructuur en de authenticatieroutes die de bedrijfsvoering mogelijk maken. Volgens gerapporteerde schattingen bedraagt CS:GO Lounge alleen al was in 2016 goed voor meer dan $1 miljard aan inzet; dat is een externe schatting van de inzetbedragen, niet van de Valve-inkomsten, en de oorspronkelijke activiteit van de website op het gebied van weddenschappen op huidskleur werd later stopgezet. Gezien de omvang ervan was een controleerbare handhaving onontbeerlijk.\n\nVandaag, van Valve zelf Abonneeovereenkomst gearchiveerd 2026-09-21 ↗ beperkt commerciële exploitatie, behalve wanneer dit uitdrukkelijk is toegestaan, en verbiedt bovendien afzonderlijk bepaalde vormen van automatisering. Onze verouderd routeoverzicht records die als OpenID-return-hosts voor externe diensten zijn aangemerkt; openid.realm en openid.return_to zijn velden die naar Steam worden gestuurd, geen geheimen die ervoor verborgen worden gehouden. Onze Controles op linkfilters geeft voorbeelden weer waarbij voor een hoofdadres een waarschuwing werd gegeven, maar niet voor een bijbehorende inloghost. Een filterresultaat op zich kan niet aantonen dat Valve een aanmelding heeft toegestaan of dat een bepaalde bot een accountblokkering heeft omzeild. Dit bewijst wel dat een waarschuwing op de startpagina niet als een volledig antwoord op de vraag over de toegankelijkheid kan worden beschouwd.\n\nOok het bestaan van nuttige, rechtmatige Steam-handels- en OpenID-functies geeft geen antwoord op de vraag of verboden exploitanten daadwerkelijk werden uitgesloten. De eigen regels van Valve staan uitdrukkelijke uitzonderingen toe. Indien Valve zich op dat onderscheid beroept, dient de Commissie het bedrijf te verzoeken de vergunning, de accountcontroles en de handhavingscriteria te specificeren die van toepassing zijn op commerciële skin-bedrijven, evenals de specifieke niet-gokgerelateerde toepassingen waarop het zich in 2016 heeft beroepen. De loutere mogelijkheid van rechtmatig gebruik is geen antwoord op gedocumenteerd verboden gebruik.\n\nWij verzoeken de Commissie haar dossier uit 2016 opnieuw te bekijken en per exploitant een overzicht te vragen: welke Steam-accounts en handelsbots zijn na de kennisgevingen van tien dagen uitgeschakeld; of gerelateerde accounts of return-hosts werden gecontroleerd; welke exploitanten later weer toegang kregen; welke uitzonderingen werden toegekend; en welke documenten de verklaring van Valve aan de Commissie staven. Maak openbaar wat volgens de wet door het publiek mag worden ingezien. Vergelijk die documenten met de huidige routes en met de latere ingrepen van Valve, waaronder OPSkins in 2018 gearchiveerd 2026-03-07 ↗.\n\nIn de kennisgeving werd in juli 2016 een termijn van tien dagen vastgesteld; tien jaar is lang genoeg om vast te stellen of dit is uitgevoerd. De Commissie zou de jaarrekening van Valve over 2016 moeten toetsen aan de infrastructuur die vandaag de dag nog waarneembaar is.\n\nHet Steam Dossier-onderzoek · Openbare verklaring, 20 september 2026\n\nMededeling van de Commissie uit 2016 ↗ gearchiveerd 2026-05-20 ↗ · Het antwoord van Valve uit 2016 (kopie van het document) ↗ · De OpenID-verklaring van Valve uit 2016 ↗ gearchiveerd 2026-09-21 ↗ · Huidige Steam-overeenkomst ↗ gearchiveerd 2026-09-21 ↗ · Tijdlijn van de uitwisseling in 2016: Paragraaf 11 →\n\nDeel A — Technisch dossier · Paragraaf 3\nDe website is geblokkeerd. De inlogpagina is dat niet.\n\n26 geblokkeerde hoofddomeinen. De authenticatieproxy achter elk domein, en hoe lang deze al actief is. Deze afzonderlijke authenticatiehosts zijn geen bijkomstige tweede adressen — elk ervan is een authenticatieproxy voor Steam, die zich tussen het platform en het OpenID-eindpunt van Valve bevindt en de inloggegevens doorgeeft die het geblokkeerde domein niet langer openlijk kan doorgeven. Valve heeft de ‘voordeur’ op de Link Filter geplaatst. De aanmelding verliep nog steeds via de proxy: csgogem.com is geblokkeerd, en api.csgem.com is sinds maart 2014 geregistreerd — twaalf en een half jaar. Op al die dagen stuurde die host zijn eigen hostnaam naar het OpenID-eindpunt van Valve, en Steam gaf die direct weer aan de gebruiker op de inlogpagina. Valve is de hoofdlijn waar al deze routes doorheen lopen; deze hoeft ze niet te vinden. Dat is wat in dit hoofdstuk wordt gemeten: niet of er een waarschuwing is, maar hoeveel jaar het traject achter de waarschuwing open blijft. Er staan 44 routes met afzonderlijke domeinen in het register, waarvan er 27 voorzien zijn van een gepubliceerd bewijsdossier per route — zie de onderstaande tabel. Bekijk eerst één voorbeeld en meet vervolgens alle routes.\n\nFiguur 3.1 — De twee routes, weergegeven.\n\nEén platform, één gebruiker, twee verzoeken die vanuit dezelfde browser worden verzonden. Het Link Filter van Valve is op beide van toepassing. Het blokkeert het verzoek dat een link bevat en laat het verzoek door dat de inloggegevens bevat. Alles wat in dit gedeelte wordt gemeten, is een telling van hoe lang de onderste route open blijft.\n\nThe player\none browser, one session\nrollbit.com\nthe platform's main domain\nrbsnin.com\nseparate authentication host\nLINK FILTER\n✕ BLOCKED\nLINK FILTER\n✓ CLEAN\nsteamcommunity.com\nOpenID endpoint · signs in\nno route\nLink geplaatst op Steam — gestoptInlogverzoek — toegangskaartenBewaarde cheques van 19 en 21 september 2026\n\nBeide verzoeken zijn zichtbaar voor Valve, maar er wordt slechts op één ervan gereageerd. Het Link Filter is een Valve-lijst, die wordt gecontroleerd door een Valve-service. Het OpenID-verzoek bevat de eigen naam van de authenticatiehost en stuurt deze naar het eindpunt van Valve, dat deze direct weergeeft op de inlogpagina. De hostnaam staat hoe dan ook in het verzoek — het verschil is of er iets mee wordt gedaan.\n\nEén platform. Twee verschillende routes.ROLLBIT / OPGESLAGEN WAARNEMINGEN\nStap 5 / 5\n\nDe aanvraag bereikt Steam. De waargenomen route leidde naar het inlogformulier van Steam. De auteurs hebben het inlogproces niet voltooid. Het blokkeren van de link naar het hoofddomein heeft deze waargenomen route naar het formulier niet geblokkeerd.\n\n01 DE CONTROLE VAN HET LINKFILTER\nBESTEMMINGrollbit.comHet hoofddomein van het platform\nSTEAM LINK-FILTERControleert de linkEen afzonderlijk waarschuwingssysteem voor bestemmingen\nOPGESLAGEN RESULTAATLink geblokkeerd19 en 21 september 2026\n02 DE WAARGENOMEN AANMELDRUTE\nOP HET PERRONAanmelden met SteamHet platform start een OpenID-verzoek\nAPARTE AUTH-HOSTrbsnin.comGeen 'Link Filter'-blok in de opgeslagen controle\nSTEAMInlogformulier weergegevenDe opgevraagde host komt voor in de melding van Steam\nControleer de oorspronkelijke vastleggingsnotities, de registratiedatum en de protocolgegevens\nHoe de handhaving van Valve eruitziet\nHoofddomein: geblokkeerd\nGebruiker\n→\nrollbit.com\n(hoofddomein)\n↓\nSTEAM LINK-FILTER — BLOKKEERD\n\"Link geblokkeerd!\" — gemarkeerd als mogelijk schadelijk\nrollbit.com heeft een Link Filter-blokkering gerapporteerd voor 2026-09-19 en 2026-09-21 (controle zonder authenticatie; onbewerkte HTML en SHA-256 opgeslagen). Een zichtbaar, controleerbaar verslag.\nWat er eigenlijk gebeurt — authenticatie\nAuth-host: niet geblokkeerd\nGebruiker\n→\nrollbit.com\n\"Log in met Steam\"\n↓\nOmleiden via een aparte authenticatiehost:\nrbsnin.comLinkfilter: CLEAN\ngeregistreerd 2026-09-18T09:34:52Z (Verisign RDAP)\n↓\nSteam mededeling op de inlogpagina (2026-09-20):\n\"Note that rbsnin.com is not affiliated with Steam or Valve\"\nSteam geeft deze melding weer vanuit het openid.realm van het verzoek dat het heeft ontvangen.\n↓\nSteam inlogformulier dat voor de afzonderlijke host wordt aangeboden\nDe auteurs hebben het inlogproces niet voltooid; het proces werd gevolgd tot aan het Steam-formulier.\nValve ontvangt bij elk dergelijk verzoek de hostnaam return_to / realm. rbsnin.com heeft bij 2026-09-21 geen blokkering door de Link Filter geretourneerd.\nOp verzoek\nAls OpenID-provider ontvangt Steam bij elk authenticatieverzoek de auth-hostnaam: deze komt binnen op de eigen servers van Valve in de openid.return_to en openid.realm parameters.\nVerzonden door de website\nDe authenticatiehost wordt niet via een scan gedetecteerd — het platform stuurt deze in elk verzoek naar Steam. Volgens OpenID 2.0 §9.1 return_to is formeel gezien optioneel, maar zonder dit kan Steam het inlogresultaat niet weergeven; voor een goed werkende Steam-inlogprocedure is het dus in feite verplicht. Steam geeft zelfs de hostnaam weer aan de gebruiker (\"<host> is niet gelieerd aan Steam of Valve\").\n14 jaar\nis de leeftijd van de oudste authenticatiehost die bij de 2026-09-21-controle nog steeds Steam aanmeldingen heeft (dota2.net, geregistreerd op 2011-10-29); de nieuwste is drie dagen oud (rbsnin.com). Beschouw het cijfer „0 geblokkeerde authenticatiehosts“ niet als de conclusie. Een geblokkeerde authenticatiehost zou de functie „Aanmelden met Steam” van het platform volledig onbruikbaar maken, dus een register dat is samengesteld op basis van werkende aanmeldingen kan alleen hosts bevatten die nooit zijn geblokkeerd. Het getal dat van belang is, is niet het aantal blokkeringen, maar het aantal jaren dat het hoofddomein op de Link Filter stond terwijl de inloggegevens ernaast bleven werken.\nAuthenticatiehosts met afzonderlijke domeinen: registratiedatum versus hoofddomein (30 routes: de 25 die in de 2026-09-21-browseraudit werden opgelost, plus 5 die op 2026-09-22 zijn toegevoegd)\nPlatform\tLinkfilter: hoofdpagina\tAuth-host\tLinkfilter: auth host\tAuth-host geregistreerd\tBron van de waarneming\tBewijsdossier\nRollbit\nrollbit.com · reg. 2014-11-08\n\tGEBLOKKEERD\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\trbsnin.com\tSCHOON\n2026-09-21 · onbewerkte HTML (geen Wayback-momentopname)\n\t2026-09-18\n09:34:52Z, Verisign RDAP\n\tSteam mededeling op de inlogpagina, 2026-09-20\trollbit.com.json\nSkin.Club\nskin.club · reg. 2017-09-04\n\tGEBLOKKEERD\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\tsc-auth.net\tSCHOON\n2026-09-21 · Wayback 2026-09-21\n\t2019-04-02\nRDAP\n\tSteam mededeling op de inlogpagina\tskin.club.json\nHowl.GG\nhowl.gg · reg. 2017-03-16\n\tGEBLOKKEERD\n2026-09-18, 19-09, 21-09 · Wayback 2026-09-21\n\thowl.uno\tSCHOON\n2026-09-21 · Wayback 2026-09-21\n\t2026-08-11\nRDAP\n\tLive browseropname + meegeleverde OpenID-URL\thowl.gg.json\nDuelbits\nduelbits.com · reg. 2020-02-03\n\tGEBLOKKEERD\n2026-09-21 · Wayback 2026-09-21\n\tswitchflips.com\tSCHOON\n2026-09-21 · Wayback 2026-09-21\n\t2020-04-21\nRDAP\n\tOpgegeven OpenID-URL\tduelbits.com.json\nCSGOFast\ncsgofast.com · reg. 2015-03-27\n\tGEBLOKKEERD\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\tsteam-login.authtofast.com\tSCHOON\nauthtofast.com, 2026-09-21 · Wayback 2026-09-21\n\t2026-06-30\nauthtofast.com, RDAP\n\tLive browseropname + meegeleverde OpenID-URL\tcsgofast.com.json\nFarmskins\nfarmskins.com · reg. 2016-03-23\n\tGEBLOKKEERD\n2026-09-19, 2026-09-21 · ruwe HTML\n\tsteam.kobal.cc\tSCHOON\n2026-09-19, 2026-09-21 · onbewerkte HTML\n\t2017-01-07\nkobal.cc, RDAP\n\tLive browseropname + meegeleverde OpenID-URL\tfarmskins.com.json\nCobaltLab\ncobaltlab.tech\n\tGEBLOKKEERD\n2026-09-21 · onbewerkte HTML\n\tcobaltauth.com\tSCHOON\n2026-09-21 · onbewerkte HTML\n\t2025-01-07\nRDAP\n\tOpgegeven OpenID-URL\tcobaltlab.tech.json\nCSGO.NET\ncsgo.net · reg. 2012-07-22\n\tGEBLOKKEERD\n2026-09-21 · ruwe HTML\n\tcn2.easylot.net\tSCHOON\n2026-09-21 · ruwe HTML\n\t2016-09-03\neasylot.net, RDAP\n\tLive browseropname\tcsgo.net.json\nGGDrop\nggdrop.com\n\tGEBLOKKEERD\n2026-09-21 · onbewerkte HTML\n\tggauth.com\tSCHOON\n2026-09-21 · onbewerkte HTML\n\t2023-05-03\nRDAP\n\tOpgegeven OpenID-URL\tggdrop.com.json\nRustChance\nrustchance.com\n\tGEBLOKKEERD\n2026-09-21 · onbewerkte HTML\n\thgfuihd.com\tSCHOON\n2026-09-21 · onbewerkte HTML\n\t2019-01-27\nRDAP\n\tOpgegeven OpenID-URL\trustchance.com.json\nSkin.Fans\nskin.fans\n\tGEBLOKKEERD\n2026-09-21 · onbewerkte HTML\n\tauth.skinfans.com\tSCHOON\n2026-09-21 · onbewerkte HTML\n\t2018-07-16\nskinfans.com, RDAP\n\tOpgegeven OpenID-URL\tskin.fans.json\nSkinport\nskinport.com · reg. 2018-09-05\n\tGEBLOKKEERD\n2026-09-21 · ruwe HTML\n\tskinport.app\tSCHOON\n2026-09-21 · onbewerkte HTML\n\t2020-06-20\nRDAP\n\tLive browseropname + meegeleverde OpenID-URL\tskinport.com.json\nSkins.Cash\nskins.cash\n\tGEBLOKKEERD\n2026-09-21 · onbewerkte HTML\n\tskinscash.live\tSCHOON\n2026-09-21 · onbewerkte HTML\n\t2019-12-05\nRDAP\n\tOpgegeven OpenID-URL\tskins.cash.json\nTF2Hunt\ntf2hunt.com · reg. 2018-01-13\n\tGEBLOKKEERD\n2026-09-21 · onbewerkte HTML\n\trstspcl.com\tSCHOON\n2026-09-21 · onbewerkte HTML\n\t2020-08-08\nRDAP\n\tLive browseropname + meegeleverde OpenID-URL\ttf2hunt.com.json\nCSGOGem\ncsgogem.com · reg. 2016-10-16\n\tGEBLOKKEERD\n2026-09-22 · onbewerkte HTML\n\tapi.csgem.com\ncsgem.com — afzonderlijk registreerbaar domein\n\tSCHOON\n2026-09-22 · onbewerkte HTML\n\t2014-03-08\ncsgem.com, RDAP — oudste in het register\n\tHandmatige verzameling + vastleggen via Link Filter\tlinkfilter-2026-09-22.json\nGamdom\ngamdom.com · reg. 2016-07-29\n\tGEBLOKKEERD\n2026-09-22 · ruwe HTML\n\tlogin.gambldom.com\ngambldom.com — één letter verschil met het merk\n\tSCHOON\n2026-09-22 · onbewerkte HTML\n\t2017-09-24\ngambldom.com, RDAP\n\tHandmatige verzameling + vastleggen via Link Filter\tlinkfilter-2026-09-22.json\n12CS\n12cs.fail · reg. 2026-03-24\n\tGEBLOKKEERD\n2026-09-22 · ruwe HTML\n\tfail.games\tSCHOON\n2026-09-22 · ruwe HTML\n\t2021-08-24\nfail.games, RDAP\n\tHandmatige verzameling + vastleggen via Link Filter\tlinkfilter-2026-09-22.json\nCSGOEmpire\ncsgoempire.com · reg. 2015-06-10\n\tSCHOON\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\tcsgoempirelogin4.com\neen van de tien genummerde domeinen login1–10\n\tSCHOON\n2026-09-21 · Wayback 2026-09-21\n\t2020-07-20\n05:49:17Z, Verisign RDAP\n\tLive-opname via de browser\tcsgoempire.com.json\nCS.MONEY\ncs.money\n\tSCHOON\n2026-09-21 · onbewerkte HTML\n\tauth.dota.trade\tSCHOON\n2026-09-21 · onbewerkte HTML\n\t2016-07-15\ndota.trade, RDAP\n\tSteam mededeling op de inlogpagina\tcs.money.json\nCSFloat\ncsfloat.com · reg. 2021-07-11\n\tSCHOON\n2026-09-21 · onbewerkte HTML\n\tcsgofloat.com\nhet vroegere merkdomein van de exploitant; een afzonderlijk registreerbaar domein, geen aanwijzing voor ontduiking\n\tSCHOON\n2026-09-21 · onbewerkte HTML\n\t2015-09-29\nRDAP\n\tLive browseropname\tcsfloat.com.json\nG4Skins\ng4skins.com\n\tSCHOON\n2026-09-21 · onbewerkte HTML\n\tauth.g4s.to\tSCHOON\n2026-09-21 · onbewerkte HTML\n\t2021-05-30\ng4s.to, RDAP\n\tOpgegeven OpenID-URL\tg4skins.com.json\nJuice.GG\njuice.gg\n\tSCHOON\n2026-09-21 · onbewerkte HTML\n\tletmeinjuice.com\tSCHOON\n2026-09-21 · onbewerkte HTML\n\t2024-04-15\nRDAP\n\tOpgegeven OpenID-URL\tjuice.gg.json\nMarkt.CSGO\nmarket.csgo.com\n\tSCHOON\n2026-09-21 · ruwe HTML\n\tdota2.net\tSCHOON\n2026-09-21 · ruwe HTML\n\t2011-10-29\nRDAP\n\tLive browseropname + meegeleverde OpenID-URL\tmarket.csgo.com.json\nRust.TM\nrust.tm\n\tSCHOON\n2026-09-21 · onbewerkte HTML\n\tdota2.net\tSCHOON\n2026-09-21 · ruwe HTML\n\t2011-10-29\nRDAP\n\tOpgegeven OpenID-URL\trust.tm.json\nCSGOLounge\ncsgolounge.com · reg. 2013-08-14\n\tSCHOON\n2026-09-22 · onbewerkte HTML\n\tdota2.net\nderde front-end op deze authenticatiehost\n\tSCHOON\n2026-09-22 · onbewerkte HTML\n\t2011-10-29\ndota2.net, RDAP\n\tHandmatige verzameling + vastlegging via Link Filter\tlinkfilter-2026-09-22.json\nDota2Lounge\ndota2lounge.com · geregistreerd 2012-08-10\n\tSCHOON\n2026-09-22 · onbewerkte HTML\n\tdota2.net\nvierde front-end op deze authenticatiehost\n\tSCHOON\n2026-09-22 · onbewerkte HTML\n\t2011-10-29\ndota2.net, RDAP\n\tHandmatige verzameling + vastleggen via Link Filter\tlinkfilter-2026-09-22.json\nSkinBaron\nskinbaron.de\n\tSCHOON\n2026-09-21 · onbewerkte HTML\n\tskinbaron.com\nhetzelfde merk, andere TLD\n\tSCHOON\n2026-09-21 · onbewerkte HTML\n\t2015-12-22\nRDAP\n\tOpgegeven OpenID-URL\tskinbaron.de.json\nTF2Royal\ntf2royal.com · reg. 2022-08-17\n\tSCHOON\n2026-09-21 · onbewerkte HTML\n\ttf2auth.com\tSCHOON\n2026-09-21 · onbewerkte HTML\n\t2021-07-27\nRDAP\n\tLive browseropname + meegeleverde OpenID-URL\ttf2royal.com.json\nTradeit\ntradeit.gg\n\tSCHOON\n2026-09-21 · onbewerkte HTML\n\tconnect-tradeit.com\tSCHOON\n2026-09-21 · onbewerkte HTML\n\t2022-02-23\nRDAP\n\tOpgegeven OpenID-URL\ttradeit.gg.json\nUpgrader\nupgrader.pro\n\tSCHOON\n2026-09-21 · ruwe HTML\n\tupgauth.space\tSCHOON\n2026-09-21 · onbewerkte HTML\n\t2026-08-14\nRDAP\n\tOpgegeven OpenID-URL\tupgrader.pro.json\nBron: steamcommunity.com/linkfilter, GET zonder authenticatie, 2026-09-21, 53 hosts, interval van 3 s; steam_tos_assets/linkfilter-recheck-2026-09-21.json; onbewerkte HTML in steam_tos_assets/linkfilter-raw/. Inschrijfdata: RDAP, steam_tos_assets/domain-registration.json. · Eerdere controle van 2026-09-19 in linkfilter-all-results.json · routegegevens invoeren in auth-route-audit.json · Wayback Machine-momentopnames van de Link Filter-pagina’s, 2026-09-21, vermeld in wayback-snapshots.json (er is geen snapshot beschikbaar voor rbsnin.com; het lokale raw-bestand is het enige bestand).\n\nInschrijfdata: RDAP (steam_tos_assets/domain-registry/). De \"opgegeven OpenID-URL\" bepaalt de verzoekparameters, niet dat de aanmelding is voltooid. De auteurs hebben op geen enkel platform een aanmelding voltooid. Een afzonderlijk domein is op zichzelf geen bewijs van omzeiling. Evenmin is „0 geblokkeerde authenticatiehosts“ een op zichzelf staande bevinding: het blokkeren van één ervan zou de Steam-aanmelding van dat platform onmogelijk maken, dus een register dat is samengesteld uit werkende aanmeldingen kan geen geblokkeerde authenticatiehost bevatten. De observatie die zwaar weegt, is de koppeling en de duur ervan — een hoofddomein op het Link Filter naast een inlogdomein dat al jaren actief is. Deze tabel bevat 30 rijen: 25 van de 27 routes met een bewijsbestand per route, plus vijf toegevoegd op 2026-09-22 waarvan de splitsing in het Link Filter is vastgelegd in linkfilter-2026-09-22.json ook al is het domein zelf handmatig verzameld — dat staat in de bronkolom bij de rijen vermeld. De twee routes voor bewijsbestanden die niet worden weergegeven, zijn skinsnipe.com (auth host pricing.tradeupspy.com, geregistreerd 2020-03-11) en csgobig.com (auth host letmeinbig.com, geregistreerd 2023-01-20); beide gaven bij de controle van 2026-09-22 de status BLOCKED main / CLEAN auth host weer, vastgelegd met SHA-256 in linkfilter-2026-09-22c.json, maar de ruwe HTML-code voor die batch zit niet in de gepubliceerde set, dus worden ze hier bij naam genoemd in plaats van dat ze een rij krijgen die elke andere regel in deze tabel kan staven. De overige 12 met de hand verzamelde routes in het register worden als zodanig aangeduid in master_registry.json onder realm_src: user.\n\nPrimaire empirische controle · Meerjarig tijdsbestek\nDe valkuil van het grote geheel: Link Filter is slechts schijnmaatregelen, geen bescherming\n\nIn desktopbrowsers worden gebruikers beschermd door externe beveiligingsmaatregelen: Google Safe Browsing en Microsoft SmartScreen onderscheppen bekende phishing-pogingen met rode waarschuwingen die het volledige scherm vullen. In de Big Picture-modus van Steam, de in-game-overlay (Shift+Tab) en het Steam-deck (SteamOS) zijn die beveiligingen niet aanwezig. De ingebouwde browser ondersteunt geen enkele extensie, schakelt externe Safe Browsing-engines uit en biedt de gebruiker precies één beschermingslaag: die van Valve linkfilter interstitieel.\n\nVeeg om alle vier resultaten te vergelijken →\n\n92.5%\n2025–2026: geavanceerde phishing zonder fouten geslaagd (37/40)\n77.5%\nPhishing in het CS2-tijdperk 2023–2024 zonder fouten geslaagd (31/40)\n70.0%\nOude phishing-aanvallen uit 2021–2022 zonder fouten geslaagd (28/40)\n7 / 7\ngoknetwerken geblokkeerd (positieve controle)\nMeerjarig longitudinaal onderzoek: 120 pure Steam phishingdomeinen live getest (24 september 2026)\n\nOm te onderzoeken of het filter van Valve nieuwe bedreigingen gewoon traag registreert of er fundamenteel blind voor is, hebben we een audit uitgevoerd op 120 bevestigde Steam-specifieke phishingdomeinen over drie historische cohorten, vergeleken met steamcommunity.com/linkfilter:\n\nCohort 1: 2021–2022 (klassieke ruilaanbiedingen en itemdrops) — 70.0% Clean Pass (28/40). Zelfs 4 tot 5 jaar nadat ze door internetwaakhonden in kaart zijn gebracht, zijn 7 van de 10 oude phishing-hosts nog steeds zonder enige blokkering bereikbaar.\nCohort 2: 2023–2024 (CS2 Beta-hype & valse ondersteuningsverzoeken) — 77.5% Zonder fouten geslaagd (31/40). Campagnes die zich voordoen als aankondigingen van Counter-Strike 2 en valse oproepen aan de community (bijv. cs2-steam.com, appealsteamcommunity.help) gaan er dwars doorheen.\nCohort 3: 2025–2026 (serverloze edge-implementaties & favicon-klonen) — 92.5% Volledig geslaagd (37/40). Moderne phishing-kits die worden ingezet op EdgeOne, Vercel en Cloudflare Pages (bijv. steamgifter.online, steam-dp4lt5b8fnez.edgeone.dev) vrijwel ongehinderd doorkomen.\n\nTelemetrie & aansprakelijkheidsdekking, geen bescherming. Waarom bestaat het Link Filter dan, als het 70% tot 92.5% van pure Steam-phishing doorlaat? Het fungeert als een aansprakelijkheidsverklaring voor het bedrijf en als een sensor voor telemetrie van uitgaande klikken. Door een beleefde \"Je verlaat Steam\" melding met een klikbare groene knop ‘Doorgaan’, Valve legt de juridische aansprakelijkheid bij het slachtoffer op grond van de Steam Abonneeovereenkomst (*\"de gebruiker is vrijwillig buiten Steam terechtgekomen\"*). Valve verzamelt de telemetriegegevens van de klik, maar blokkeert de diefstal niet.\n\nHet Favicon Hash-bewijs: geen opname van dreigingsfeeds. Onafhankelijke platforms voor dreigingsinformatie (urlscan.io, Shodan, Censys) sporen actieve Steam-phishingkits op door simpelweg te zoeken naar de officiële favicon-hash van Steam (page.favicon.hash:9f890a9debcdfccc339149a7943be9aff9e4c9203c2fa37d5671a5b2c88503ad NOT domain:*.steampowered.com). Deze eenvoudige geautomatiseerde controle brengt actieve phishingclusters binnen enkele seconden aan het licht. Valve synchroniseert niet met externe feeds, voert geen op hashwaarden gebaseerde dreigingsdetectie uit en grijpt alleen handmatig in wanneer dit door toezichthouders wordt opgelegd (het WSGC-besluit inzake kansspelen uit 2016) of om zijn geregistreerde domeinnamen te beschermen.\n\nBelangrijkste auditbewijsmiddelen: Longitudinaal meerjarig onderzoek met 120 domeinen: longitudinal-steam-phishing-audit.json · 100 specifieke Steam phishing-voorbeelden: linkfilter-steam-phishing-100.json · Uitgebreid onderzoek naar de voeding (n=250): linkfilter-coverage-2026-09-22.json.\n\nCSGOEmpire — batchregistratie van tien genummerde auth-domeinen\n\nOp 2020-07-20 tien genummerde domeinen, csgoempirelogin1.com via csgoempirelogin10.com, werden geregistreerd. Voor alle tien zijn Verisign RDAP-tijdstempels vastgelegd: login1 05:49:06Z, login5 05:49:08Z, login2 05:49:11Z, login3 05:49:14Z, login4 05:49:17Z, login6 05:49:20Z, login7 05:49:23Z, login8 05:49:26Z, login9 05:49:28Z — negen domeinen in 22 seconden — en login10 om 05:56:03Z, zeven minuten later. Het tijdsverschil wijst erop dat het om één bulkbewerking door de registrar gaat.\n\nHet patroon komt overeen met vooraf ingestelde fallback-hosts; alleen login4 is waargenomen in een live OpenID-verzoek. csgoempire.com en csgoempirelogin4.com leverden beide de status „CLEAN“ op in het Link Filter op 2026-09-21; CSGOEmpire behoorde niet tot de sites die in persberichten over de kennisgevingen van juli 2016 werden genoemd.\n\n# DNS — alle 10 actief (september 2026)\nOké csgoempirelogin1.com 172.67.129.43\nOké csgoempirelogin2.com 172.67.175.168\nOké csgoempirelogin3.com 188.114.96.3\nOké csgoempirelogin4.com 188.114.96.11 ← in OpenID-verkeer\nOké csgoempirelogin5.com 172.67.160.194\nOké csgoempirelogin6–10.com IP-adressen van Cloudflare\nNXDOMAIN: csgoempirelogin11.com\nAlle 10 geregistreerd 2020-07-20; alle 10 voorzien van een RDAP-tijdstempel (steam_tos_assets/domain-registry/csgoempireloginN.com.rdap.json)\nConclusie voor regelgevende instanties\nAls het hoofddomein wordt geblokkeerd terwijl de auth-host niet wordt geblokkeerd, blijft de inlogroute open — en dat blijft jarenlang zo.\n\nHet Link Filter-blok op het hoofddomein is een verifieerbaar, openbaar record. De authenticatiehost verwerkt het „Aanmelden met Steam”-verkeer en komt voor in de eigen OpenID-verzoekparameters van Valve. Bij controles op 2026-09-21 en 2026-09-22 leverde het hoofddomein in 26 filter-split-paren een Link Filter-blok op, terwijl de proxy die de aanmelding verwerkte er geen opleverde. Het bovenstaande register meet de andere helft daarvan: deze hosts zijn geen kortstondige wegwerpdomeinen. Verschillende waren op de datum van de controle al meer dan een decennium geregistreerd, en elk van die dagen is een dag waarop Valve de hostnaam in zijn eigen verzoekparameters ontving. Valve heeft geen handhavingsgegevens per operator gepubliceerd, dus of er andere maatregelen op deze hosts zijn toegepast, kan niet worden vastgesteld aan de hand van openbare gegevens.\n\n12 jaar en 6 maanden\ncsgogem.com wordt geblokkeerd in de Linkfilter.\nDe inloghost api.csgem.com is\nis geregistreerd sinds 2014-03-08 en is dat niet.\nSamenvatting in begrijpelijke taal — Voor toezichthouders en rechtbanken (uitvouwen)\nSamenvatting in begrijpelijke taal — voor toezichthouders\nAchtergrond: Wat Steam is en waarom het hier van belang is\n\nSteam is een softwareplatform dat wordt beheerd door Valve Corporation (Bellevue, Washington, VS). Steam fungeert als een aanbieder van digitale identiteit: gok- en gamingwebsites op het internet maken gebruik van een systeem genaamd „Aanmelden met Steam“ — een knop waarmee een website kan verifiëren of een bezoeker een echt Steam-account heeft. Dit is vergelijkbaar met „Inloggen met Google“ of een identiteitscontrole door middel van een door de overheid uitgegeven identiteitskaart: de website stuurt de gebruiker door naar de servers van Steam, Steam verifieert wie de gebruiker is, en Steam stuurt de gebruiker terug naar de website. Valve beheert het authenticatiesysteem. Elke aanmelding via „Aanmelden met Steam“ verloopt via de eigen servers van Valve.\n\nWat Valve deed: de domeinblokkering\n\nIn juli 2016 stuurde de raadsman van Valve, naar aanleiding van druk vanuit de media en de juridische wereld inzake ‘skin gambling’, kennisgevingen naar ongeveer 23 bij naam genoemde goksites (volgens persberichten van 21 juli 2016); in oktober 2016 liet Valve aan de Washington State Gambling Commission weten dat het contact had opgenomen met meer dan veertig sites. Sommige gokdomeinen komen voor in de Steam Linkfilter — een lijst waardoor bij elke link naar deze pagina's die binnen Steam wordt geplaatst (in de chat, op een profielpagina, in de winkel) een waarschuwingspagina wordt weergegeven: \"Link geblokkeerd!\" Het Link Filter is de enige handhavingsmaatregel waarvan het effect van buiten Valve kan worden waargenomen.\n\nVoorbeeld: Een link naar rollbit.com binnen Steam verschijnt de waarschuwingspagina van het Link Filter (2026-09-19 en 2026-09-21 aangevinkt). Op papier is de goksite geblokkeerd.\nWat een proxy-domein is\n\nA Een authenticatiehost met een apart domein is een authenticatieproxy: een tweede websiteadres, op een ander registreerbaar domein, dat dezelfde exploitant tussen zijn gebruikers en Steam plaatst, uitsluitend met het doel de stap „Aanmelden met Steam” uit te voeren. Het fungeert als proxy voor het inloggen. De gebruiker denkt dat hij inlogt op het platform; het verzoek dat Valve bereikt, bevat de hostnaam van de proxy, niet die van het platform. Het heeft doorgaans geen publiekelijk zichtbare koppeling met de goksite, en het is het adres waar gebruikers naartoe worden teruggestuurd nadat Steam hun identiteit heeft bevestigd.\n\nVoorbeeld: Rollbit opereert onder rollbit.com, dat door het Link Filter wordt geblokkeerd. Voor Steam-authenticatie maakte de op 2026-09-20 waargenomen datastroom gebruik van een apart adres: rbsnin.com, geregistreerd 2026-09-18. Dit adres leverde het volgende resultaat op geen 'Link Filter'-blok op 2026-09-21. De goksite bleef actief en de Steam-inlogprocedure verliep via de niet-geblokkeerde host.\nHet kritieke punt: de Auth Host wordt bij elk verzoek naar Steam verzonden\n\nValve hoeft niet te scannen of te crawlen om te achterhalen welke authenticatiehosts in gebruik zijn. Steam is de OpenID-identiteitsprovider voor deze sites, en elke klik op „Aanmelden met Steam“ verstuurt een GET-verzoek naar de eigen servers van Valve, waarin de authenticatiehostnaam in leesbare tekst is opgenomen. Volgens OpenID 2.0 §9.1 is de return_to Dit veld is formeel gezien optioneel, maar zonder dit veld kan Steam het inlogresultaat niet weergeven; voor een succesvolle Steam-inlogprocedure is het dus in feite verplicht. Steam geeft zelf de hostnaam weer op de inlogpagina (\"<host> is niet gelieerd aan Steam of Valve\").\n\n— Vorm van het verzoek Steam ontvangt (host zoals waargenomen voor Rollbit op 2026-09-20): —\nGET steamcommunity.com/openid/login\n&openid.mode=checkid_setup\n&openid.return_to=https://rbsnin.com/… ← in feite vereist; komt voor in het logboek van Valve\n&openid.realm=https://rbsnin.com ← door de website zelf aangegeven; weergegeven op de inlogpagina van Steam\nAls de website gebruikmaakt van server-naar-server-verificatie (check_authentication), wordt in het logboek van Valve ook het IP-adres van de server van het platform en het hostingnetwerk vastgelegd.\n\nHet achterhalen van de hostnaam uit dit verzoek is een standaardhandeling. Het handhavingsverslag — welke hosts wel en welke niet zijn aangepakt, en op basis van welke criteria — bevindt zich uitsluitend in de infrastructuur van Valve en is niet openbaar gemaakt.\n\nWat dit aantoont\n\n1. Het blok ‘Link Filter’ is van toepassing op links, niet op aanmeldingen. Het hoofddomein blokkeren (bijvoorbeeld rollbit.com) toont een waarschuwing aan gebruikers die binnen Steam op links naar deze site klikken. Dit belemmert de werking van de site niet, noch het gebruik van de eigen OpenID-dienst van Valve via een ander adres.\n\n2. De geteste authenticatiehosts werden niet geblokkeerd. De bovenstaande tabel toont authenticatiehosts met afzonderlijke domeinen die tussen 2011 en september 2026 zijn geregistreerd, waarvan een aantal pas jaren na de kennisgevingen van juli 2016. Bij 26 paren leverde het hoofddomein een Link Filter-blokkering op, terwijl de proxy die de aanmelding doorgeeft dat niet deed (niet-geverifieerde controles, 2026-09-21 en 2026-09-22; ruwe reacties en SHA-256 opgeslagen). Die proxy zou ophouden met werken op de dag dat Valve deze weigerde; daarom is de maatstaf hier hoe lang deze heeft gedraaid, en niet of deze in de lijst staat. Valve ontvangt deze hostnamen in zijn eigen OpenID-verzoeken. Of er naast het Link Filter nog andere maatregelen zijn toegepast, kan niet worden vastgesteld aan de hand van openbare gegevens, omdat Valve geen handhavingsgegevens per operator heeft gepubliceerd.\n\n3. De websites bleven zich authenticeren via de infrastructuur van Valve. \"Aanmelden met Steam\" is een dienst van Valve; elke authenticatie via deze dienst is een verzoek dat Valve ontvangt en verwerkt. Valve genereert ook inkomsten uit case keys, en de Steam Community Market brengt een gecombineerde vergoeding van ongeveer 15% in rekening voor transacties die binnen de Market worden voltooid (niet voor externe transacties). De actie „Link Filter“ heeft een openbaar record aangemaakt; dit heeft de authenticatierelatie niet onderbroken.\n\nZou het blokkeren hebben gewerkt?\n\nTer vergelijking: toen de gratis domeinregistrar Freenom in 2023 zijn activiteiten stopzette, werden phishingcampagnes die afhankelijk waren van zijn domeinen verstoord. De bedrijfscontinuïteit hangt af van de stabiliteit van de infrastructuur.\n\nHetzelfde geldt hier. Als een authenticatiehost zou worden geweigerd tijdens de OpenID-verwerking van Steam, zou de functie „Aanmelden met Steam” van het platform niet werken totdat er een nieuwe host is geregistreerd, certificaten zijn uitgegeven en de DNS-wijzigingen zijn doorgevoerd. Gedurende die periode: downtime.\n\nRotatie maakt blokkeren niet zinloos. Hierdoor wordt het blokkeren een operationele kostenpost. Aangezien nieuwe hosts bij het eerste gebruik in de eigen verzoeklogboeken van Valve verschijnen, zou een reactie even lang kunnen duren als dat eerste gebruik.\n\nBatchregistratie is op zich al een signaal: De accounts login1–login10 van CSGOEmpire werden op 2020-07-20 geregistreerd, waarvan negen binnen 22 seconden (Verisign RDAP). Een reactie hoeft niet per domein te zijn; een opeenvolgende reeks uit één registrarsessie kan als een reeks worden aangemerkt.\n\nUit de openbare gegevens blijkt niet dat er een poging is gedaan om geauthenticeerde hosts te blokkeren die door rotatie is verijdeld.\nHieruit blijkt welke belangrijke domeinen werden geblokkeerd terwijl de proxy die de betreffende aanmelding verwerkte, bleef draaien — 26 paren per 2026-09-22, waarbij de oudste geregistreerde authenticatiehost 12 jaar en 6 maanden oud was — en dat er voor geen enkele operator een openbaar gemaakt handhavingsverslag bestaat.\nDe vraag voor de toezichthouder luidt dan ook: welke handhavingsmaatregelen heeft Valve eventueel toegepast op de geauthenticeerde hosts die het in zijn eigen OpenID-verzoeken ontvangt?\nWat Valve deed — en waarom dit het Auth-pad niet onderbrak\n\nIn de onderstaande tabel wordt voor elke openbaar gedocumenteerde actie van Valve aangegeven of deze invloed had op het toegangspunt voor OpenID-authenticatie. De conclusie is niet dat „Valve niets heeft gedaan“ — het is dat geen van de openbaar gedocumenteerde acties betrekking had op het punt waar aanmeldingen bij gokplatforms via de servers van Valve verlopen.\n\nDatum\tValve Actie\tGetroffen openid.return_to pad?\njuli 2016\tOpenbare verklaring van 13 juli 2016; kennisgevingen van de raadsman aan ~23 genoemde locaties (pers, 21 juli 2016); >40 locaties benaderd naar aanleiding van de brief van Valve aan WSGC van oktober 2016\tNee. De meldingen en het linkfilter hebben betrekking op operatoren en links; het OpenID-verzoekpad is niet gewijzigd.\n2017\tSluiting van IEconItems_730/GetPlayerItems (volgens het technische account van CSFloat; er is geen changelog met Valve gevonden)\tNee. Dit had alleen invloed op de zichtbaarheid van de geschiedenis van openbare items. De OpenID-authenticatie is niet gewijzigd.\n2018-03-29\t7-daagse handelsblokkering voor CS:GO aangekondigd (blog.counter-strike.net)\tNee. De verwerking van items is vertraagd; het OpenID-verzoekpad is niet gewijzigd.\n2022-05-10\tEindpunten voor het annuleren van transacties verwijderd uit de openbare Web API (opgemerkt door een gebruiker; geen Valve changelog — node-steam-tradeoffer-manager #325)\tNee. De tooling voor het uitwisselen van aanbiedingen is gesloten; de OpenID-authenticatie is niet gewijzigd.\n2023-12-04\tVoor het aanmaken van een API-sleutel is nu een bevestiging via de mobiele telefoon vereist (steamcommunity.com/dev/apikey; geen changelog)\tNee. Het belangrijkste eindpunt is beveiligd; de hier beschreven authenticatiehosts waren niet getroffen.\n2026-09-19 / 21-09\tSteam Link: de toestand van het filter zoals waargenomen door de auteurs\tNr. 14 hoofddomeinen leverden een blok op bij de opgeslagen 2026-09-21-hercontrole — 26 gesplitste paren in het register met 2026-09-22 — terwijl de proxy die elke aanmelding verwerkte, bleef draaien.\nBronnen: Valve verklaring van 13 juli 2016 (store.steampowered.com/oldnews/22883, gearchiveerd 2026-09-21) · Technisch verslag van CSFloat over de sluiting in 2017 (blog.csfloat.com, gearchiveerd 2026-09-21) · Status van het linkfilter: linkfilter-recheck-2026-09-21.json.\nDeze bevinding kan worden weerlegd door één enkel gepubliceerd geval waarin Valve een OpenID-verzoek heeft afgewezen omdat openid.return_to verwees naar een host met een vergunning voor kansspelen. In het openbare register is geen dergelijke instantie gevonden.\nDe twee meest recente registraties van auth-hosts\nhowl.unowerd geregistreerd op 2026-08-11 (RDAP), 41 dagen vóór 2026-09-21; howl.gg gaf een Link Filter-blokkering weer op 2026-09-18, 2026-09-19 en 2026-09-21. Of de blokkering voorafging aan de registratie is niet vastgesteld.\nrbsnin.comwerd geregistreerd als 2026-09-18T09:34:52Z (Verisign RDAP) en werd waargenomen in de Steam-inlogprocedure van Rollbit op 2026-09-20 via de mededeling op de eigen inlogpagina van Steam; rollbit.com gaf op 2026-09-19 en 2026-09-21 een Link Filter-blokkering terug, rbsnin.com niet.\nElke host in de bovenstaande tabel wordt naar de authenticatieservers van Valve verzonden als openid.realm bij elke inlogpoging.\nVolledige gegevens per route en beoordelingen van Link Filter: de tabel in paragraaf 3 hierboven; ruwe resultaten in linkfilter-recheck-2026-09-21.json en linkfilter-all-results.json.\nMethodologie — Hoe de tellingen voor de route- en linkfilters tot stand zijn gekomen\n1. Domeinresolutie\nDe 2026-09-21-audit heeft 78 van de 189 aangevraagde platforms afgehandeld: 33 authenticeren op hun eigen hostnaam en 20 op hun eigen subdomein — directe authenticatie, en geen van deze wordt geteld als routes met een afzonderlijk domein. De overige 25. authenticeren via een apart registreerbaar domein, verdeeld over 24 verschillende hostnamen (dota2.net wordt gedeeld door market.csgo.com en rust.tm): 10 vastgesteld via live browseropnames, 3 via de melding op de inlogpagina van Steam zelf, 12 via een opgegeven OpenID-URL. Het live register (master_registry.json, 2026-09-22) breidt dat uit tot 44 routes met afzonderlijke domeinen: 26 filter-split-paren (hoofddomein BLOCKED, authenticatiehost CLEAN) plus 18 andere routes zonder hoofddomeinsplit. Van de 44, 27: een bewijsdossier per route bijhouden; de overige 17 zijn met de hand verzameld en zijn gemerkt realm_src: user in het register. Vijf van die zeventien — csgogem.com, gamdom.com, 12cs.fail, csgolounge.com en dota2lounge.com — zijn op 2026-09-22 toegevoegd met een Link Filter-registratie van beide hosts (ruwe HTML + SHA-256 in linkfilter-2026-09-22.json), dus de splitsing zelf is aantoonbaar, ook al is het domein handmatig verzameld; ze staan in de bovenstaande tabel vermeld naast de routes uit het bewijsbestand. tfauth.com (tf2easy.com) is om 2026-09-22 uit het register geschrapt: net als bij arena.fragnet.net is er geen enkele verifieerbare link die het aan de oorspronkelijke site koppelt. Het aantal kan opnieuw worden afgeleid uit de gepubliceerde auth-route-audit.json (reeks van 2026-09-21) volgens één regel: een platform telt alleen mee als de waargenomen Steam OpenID-host op een ander registreerbaar domein staat dan het platform zelf.\n2. Steam Status van het linkfilter\nGetest via steamcommunity.com/linkfilter/?url=https://[domain], niet-geverifieerd, op 2026-09-19 en 2026-09-21; onbewerkte HTML opgeslagen met SHA-256. Status afzonderlijk vastgelegd voor het hoofddomein en de authenticatiehost. Een classificatiesysteem maakt onderscheid tussen de algemene melding „U verlaat Steam“ (CLEAN) en de pagina „Link geblokkeerd! ... gemarkeerd als mogelijk schadelijk“ (BLOCKED); een controle via google.com bevestigt dat de twee niet door elkaar worden gehaald. Een eerdere, geauthenticeerde variant van deze test werd terzijde geschoven nadat deze voor elk domein, inclusief die controle, „geblokkeerd” rapporteerde — dit bleek te wijten te zijn aan een ongeldige sessiecookie in het testscript, en was dus geen echt resultaat.\n3. Controle van de authenticatiehost\nLive-opname: een Playwright-browser navigeerde naar de aanmeldingsprocedure van elk platform en de openid.return_to De hostnaam is uit het onderschepte verzoek gehaald. Opmerking op de inlogpagina: de hostnaam is uit Steam’s eigen \" gehaald<host> is niet gelieerd aan Steam of Valve\" tekst, die Steam weergeeft vanuit openid.realm (rbsnin.com, sc-auth.net, auth.dota.trade). Aangeleverde URL: een Steam-inlog-URL die aan de auteurs is verstrekt; deze URL bepaalt de verzoekparameters, maar houdt geen voltooide aanmelding in. Op geen enkel platform is een aanmelding voltooid.\n4. Dekking — wat er niet is opgelost, en waarom dat van belang is\nVan de 189 perrons, 110 leverde geen vaste route op en één was niet van toepassing (189 − 78 − 1). In dit dossier wordt geen van deze meegeteld. De uitsplitsing van de 110, uit het auditbestand: 22 bot-uitdagingen, 14 time-outs, 12 HTTP-fouten en 10 navigatiefouten — de waarnemer kon de inlogstroom niet bereiken, hoewel de meeste van deze sites normaal openen in een gewone browser; 20 vertoonden geen Steam inlogcontrole op de landingspagina; 16 kwamen bij een inlogprocedure die niet naar een host kon worden omgezet; 11 domeinen konden niet via DNS worden omgezet; 5 strandden bij een toestemmingsscherm. Het onderstaande overzicht verdeelt dezelfde 110 op een andere manier: de 11 die niet in DNS konden worden omgezet, worden apart vermeld als Verwijderd · NXDOMAIN, en de ene niet-toepasselijke vermelding wordt bij de rest gevoegd. 189 platforms gecontroleerd, 11 verwijderd na een definitieve NXDOMAIN-melding van beide resolvers, 178 behouden (platform-audit.json, platforms-removed.json). 137 authenticatiedomeinen die het grootboek op basis van het naamgevingspatroon had geraden, werden uit de gegevens op 2026-09-19 verwijderd — nooit waargenomen, dus ook nooit bewijs. Drie van de gissingen werden weerlegd door de verstrekte OpenID-URL's: buff.163.com, gamerpay.gg en csgoluck.com voeren rechtstreeks authenticatie uit, terwijl er werd gegist naar buffauthproxy.163.com, gamerpayredirect.io en lucklogin.app. De verwijderingen staan vermeld in het gepubliceerde auditbestand.\nHet getal 25 is een ondergrens, geen bovengrens. Van de 78 platforms die wel konden worden geïdentificeerd, maakten er 25 gebruik van een apart domein en 53 niet. Uit die verhouding worden geen conclusies getrokken over de 110 niet-geïdentificeerde platforms, en nergens in dit dossier wordt op basis daarvan een prognose gegeven. Elk platform kan worden opgelost door iemand die de site opent en op „Aanmelden met Steam“ klikt: de hostnaam voor de authenticatie staat in de URL van de Steam-pagina die wordt geladen.\nHet doel van dit hoofdstuk: Een onafhankelijke waarnemer heeft een browser en veel geduld nodig om 189 platforms te identificeren, en kwam uit op 78. Voor Valve is een databasequery nodig. Elk platform dat gebruikmaakt van „Aanmelden met Steam“ — zowel geïdentificeerde als niet-geïdentificeerde — stuurt openid.realm naar het authenticatie-eindpunt van Valve bij elke aanmelding. De leemte in deze tabel is te wijten aan het feit dat de auteurs zich buiten het systeem bevinden. Voor Valve is er geen sprake van een dergelijke leemte.\nDe waargenomen proxy-hostnamen staan in auth-route-audit.json. Registratiedata van domeinnamen afkomstig van RDAP (Verisign) / IP2WHOIS. De resultaten van de linkfilter zijn: linkfilter-all-results.json.\nEen analogie ter verduidelijking\n\nStel je voor dat een erkend taxibedrijf van de toezichthouders te horen krijgt dat het niet langer mag opereren vanuit zijn geregistreerde adres aan Main Street. Het bedrijf verwijdert het bord aan Main Street. Het verwijderen van dat bord wordt vastgelegd. Hetzelfde bedrijf opent echter een vestiging aan Side Street — geregistreerd onder een andere naam — en zet zijn activiteiten van daaruit voort. De toezichthouders beheren het centrale dispatching-systeem dat door alle taxi’s van beide adressen wordt gebruikt. Bij elke ritverzoek staat „ophalen vanaf Side Street“. De toezichthouders trekken de vergunning voor Side Street nooit in. Het verwijderen van het bord met de tekst „Main Street” was de enige handhavingsmaatregel die werd genomen. Het taxibedrijf is altijd blijven draaien.\n\nDeel A — Technisch dossier · Paragraaf 3.1\nIn Steam is de lijst van Valve de enige lijst.\n\nEen link waarop in de Steam-client, de in-game-overlay of de Big Picture-modus wordt geklikt, wordt niet in de browser van de gebruiker geopend. De link wordt weergegeven in de eigen ingebouwde browser van Steam — waar de waarschuwingslagen die een browser zou toepassen, niet aanwezig zijn. Het Link Filter is niet slechts één van de vele veiligheidsmaatregelen. Het is de enige veiligheidsmaatregel.\n\nIn een gewone browserDrie onafhankelijke lagen\nGoogle Veilig surfenEen paginagrote tussenpagina voor websites die op de phishing- en malwarelijsten van Google staan, die voortdurend wordt bijgewerkt en onafhankelijk is van de bezochte website.\nDe antivirus-browserextensieDe meeste eindgebruikersproducten worden geleverd met een browser-add-on die de bestemming vergelijkt met de reputatielijst van de leverancier.\nHTTPS-inspectie op eindpuntenWanneer het product een TLS-controle uitvoert, wordt de inhoud van de pagina gescand voordat deze de gebruiker bereikt.\nIn de Steam-client, overlay en Big PictureEén laag\nGoogle Veilig surfenNiet aanwezig. Voor de controle zijn Google API-sleutels vereist die niet zijn ingesteld in ingebouwde Chromium-builds; wanneer deze ontbreken, wordt in de ontwerpdocumentatie van Chromium vermeld dat de Safe Browsing-handler simpelweg nooit aan de verzoekketen wordt toegevoegd.\nDe antivirus-browserextensieNiet aanwezig. De renderer van Steam is niet de browser van de gebruiker en laadt geen extensies uit het browserprofiel van de gebruiker, dus er wordt geen add-on uitgevoerd op de pagina.\nHTTPS-inspectie op eindpuntenAfhankelijk van het product. Het verkeer wordt beëindigd binnen een met een code ondertekend Valve-proces in plaats van in een herkende browser, en een aantal eindpuntproducten sluiten ondertekende applicaties uit van TLS-inspectie.\nHet Steam-linkfilterDe eigen blokkeerlijst van Valve, die wordt geraadpleegd wanneer een link het Steam-ecosysteem verlaat. Dit is de enige controle die wordt uitgevoerd — en in de bovenstaande tabel staat vermeld wat deze controle oplevert voor de authenticatiehosts die in dit hoofdstuk worden beschreven.\nEen test die elke lezer kan uitvoeren, en als de test mislukt, is de conclusie ongeldig\n\nOpen een van de door Google gepubliceerde test-URL's voor Veilig surfen (testsafebrowsing.appspot.com) in Chrome: er verschijnt een rode interstitial die de hele pagina vult. Open dezelfde URL vanuit een Steam-chatbericht, zodat deze wordt weergegeven in de Steam-client of de overlay: er verschijnt geen interstitial. De enige waarschuwing die Steam kan genereren, is zijn eigen Link Filter-pagina, en alleen voor hosts op de lijst van Valve.\n\nHet eigen bug-bounty-record van ValveDat ene nummer is al eens omzeild — op het eigen album van Valve\n\nAls het Link Filter de enige controle is die binnen de client wordt uitgevoerd, zijn de eigen storingsmodi ervan geen bijzaak. Twee meldingen in het HackerOne-programma van Valve, beide geaccepteerd, beide opgelost en beide inmiddels volledig openbaar gemaakt:\n\n#291750gearchiveerd 2025-11-16 ↗Open Redirect · medium\nOmzeiling van de linkfilterbeveiliging\n\nGemeld op 19 november 2017, opgelost, bekendgemaakt op 9 mei 2018. De eigen proof of concept van het rapport: het vervangen van de ideografische punt 。 (%E3%80%82) voor de punt in een hostnaam — Het is mogelijk om de blokkering te omzeilen. De tussenpagina waar dit gedeelte over gaat, is niet verschenen.\n\n#1079561gearchiveerd 2026-09-24 ↗Openbaarmaking van informatie · hoog\nDe webbrowser Big Picture laat inlogcookies lekken en maakt gevoelige informatie openbaar (wat kan leiden tot het overnemen van accounts)\n\nGemeld op 15 januari 2021, opgelost, openbaar gemaakt op 21 september 2021. De ernstclassificatie van Valve zelf is hoog, en de titel geeft de gevolgen aan. Het openbaar gemaakte record bevat de titel, de ernstbeoordeling en de datums; de technische beschrijving is niet opgenomen in de gepubliceerde payload, dus er wordt hier verder niets uit geciteerd.\n\nDe interpretatie van de auteurs, en geen conclusie uit een van beide rapporten: De twee staan aan weerszijden van dezelfde poort. De ene is de waarschuwing die niet verschijnt voordat de bestemming wordt geopend; de andere is het feit dat de sessie de client verlaat zodra er een pagina binnen die sessie wordt geopend. De reeks gebeurtenissen die volgt op een gestolen sessie — een sleutel die zonder vraag wordt geregistreerd, de echte transactie die wordt geannuleerd, een duplicaat dat naar een kloon wordt verzonden — is het patroon dat wordt beschreven in Paragraaf 5 naar Paragraaf 8. Beide meldingen zijn afgesloten; geen van beide wordt nog als actieve kwetsbaarheid aangemerkt. Wat hieruit blijkt, is beperkter maar volstaat: de enige overgebleven beveiligingslaag is, volgens de eigen gegevens van Valve, in het verleden al vaker omzeild.\n\nBron: het HackerOne-openbaarmakingsdossier voor elk rapport, opgehaald op 2026-09-22 — nummer, titel, team, kwetsbaarheid, ernst, rapport- en openbaarmakingsdata en status zoals gepubliceerd door HackerOne. Opvraagdossier: hackerone-reports.json. Er wordt hier geen bedrag van de beloning vermeld; ook in het opgevraagde openbare dossier komt er geen voor.\n\nVeldobservatie · PhishDestroyDetecties die normaal gesproken een einde maken aan een campagne, hebben deze niet beëindigd\n\nWe zagen hoe phishing-hosts verkeer bleven genereren terwijl ze 20 of meer gedetecteerde leveranciers. Als een campagne in die toestand via het web of e-mail wordt verzonden, is ze binnen enkele dagen ten dode opgeschreven — zowel de browser als het antivirusprogramma handelen op basis van die beoordelingen. Binnen Steam gebeurt dat niet. De beoordelingen waren er al die tijd al. Er is nooit iets in de client gevraagd.\n\nWat dit betekent voor een minderjarige die een antivirusprogramma heeft geïnstalleerd\n\nHij negeert geen enkele waarschuwing en schakelt niets uit. Er komt een bericht binnen in Steam — een gratis mes, een stem voor het team van een vriend — en de pagina wordt geopend in Steam. Hij opent nooit een browser, dus de browser beschermt hem nooit. Zijn antivirusprogramma draait en beschouwt dat domein misschien al als schadelijk; het wordt nooit om toestemming gevraagd. Elke waarschuwing die hem had kunnen tegenhouden, bestaat al. Maar geen enkele dringt tot hem door. Hij gelooft dat hij Steam nooit heeft verlaten, en dat is ook zo.\n\nDe weggeefactie is geen uitvinding van de phisher — gratis Valve artikelen zijn de manier waarop huidverzorgings- en goksites reclame maken, en dat is precies waarom het bericht zo onschuldig overkomt. Klachten: het handhavingsarchief. Gegevens over leeftijd en kinderen: Artikel 17.\n\nBronnen: Steam geeft webinhoud weer via het Chromium Embedded Framework in de steamwebhelper proces — zie Technische analyse van DARKNAVY van 27 juni 2024 ↗ en die van Valve zelf Steam Beta-forum voor klanten ↗ gearchiveerd 2025-08-04 ↗. Er wordt geen gebruik gemaakt van een CEF-versie: het ingebouwde Chromium is geen Chrome en bevat geen van de Google-services van Chrome. Veilig surfen zonder API-sleutels: Ontwerpdocument Chromium ↗ gearchiveerd 2026-08-21 ↗, Chromium API-sleutels ↗ gearchiveerd 2026-08-30 ↗ (“Veel van de Google-API’s die door Chrome worden gebruikt, zijn specifiek voor Google en niet bedoeld voor gebruik in afgeleide producten”), en hetzelfde effect in andere builds zonder sleutel — Homebrew-vat nr. 193814 ↗. Test-URL's: testsafebrowsing.appspot.com ↗.\n\nTwee verschillende klokken\nDe leeftijd van het domein.De datum van de waarneming.\n\nDe registratiedatum geeft aan wanneer een domein is geregistreerd. Een gedateerd OpenID-record geeft de retourhost in dat record aan. De eerste kan de jaren vóór de tweede niet invullen.\n\nHet volledige register maakt onderscheid tussen een afzonderlijk registreerbaar domein, het eigen subdomein van een website en een directe route. Elke rij bevat een link naar de bron en het resultaat van DNS.\n\nBekijk het domeinregister →· Registratiedata downloaden ↗· Herhaal de waarneming ↗\n\nDeel A — Technisch dossier · Paragraaf 4\nEen eindpunt is gesloten. Bij het openbare traceren is een sleutel verloren gegaan.\nContext en bronbeperkingen\n\nSteam heeft wijzigingen doorgevoerd waardoor de Asset-ID’s van artikelen niet langer openbaar zichtbaar waren en de toegang tot de voorraad via de API werd beperkt. Het gevolg: het werd onmogelijk om een specifiek artikel aan de hand van de oorspronkelijke Asset-ID te traceren via openbare gegevens. Hieronder volgt wat voorheen mogelijk was, wat daarna niet meer mogelijk was, en wat dat kost voor een slachtoffer dat probeert te bewijzen waar zijn eigendom is gebleven. Volgens het engineeringaccount van CSFloat is de datum 2017; er is geen changelog van Valve gevonden. De volgorde van gebeurtenissen — ruwweg een jaar na de verklaring over gokken van juli 2016 — is de vraag waarop het onderzoek zich richt, niet een bevinding. De itemgegevens zelf bevinden zich nog steeds in de systemen van Valve; externe onderzoekers hebben de toegang tot de keten van originele ID’s verloren, terwijl float-, seed- en paint-identificatoren slechts gedeeltelijke vergelijking mogelijk maken.\n\nDe regel Valve geldt: Steam De klantenservice kan geen items terugzetten die uit je account zijn verdwenen, en het is aan jou om aan te tonen wat er is gebeurd. Het verslag: In 2017 heeft Valve het eindpunt gesloten dat de oorspronkelijke item-ID's bevatte. Voor die tijd kon iedereen een gestolen skin volgen vanaf het account van het slachtoffer naar een marktplaatsbot. Sindsdien kan niemand buiten Valve dat meer. Het bewijs dat van het slachtoffer wordt gevraagd, is het bewijs dat was uitgeschakeld — en het bestaat nog steeds, binnen Valve.\n\nHet tijdperk vóór de stroomstoring\n\nVan oudsher had elk virtueel item dat op Steam werd gegenereerd een wereldwijd uniek, onveranderlijk Asset-ID. OSINT-databases van derden zouden deze ID’s kunnen indexeren. Als een gebruiker een item zou laten kapen, zouden onderzoekers de herkomst van dat specifieke item kunnen traceren terwijl het van de tussenrekening van de kaper naar de opslagrekeningen van een marktplaats of goksite wordt overgeheveld.\n\nVOORHEEN: kon iedereen aan de hand van openbare gegevens een transactie volgen vanaf de rekening van het slachtoffer via tussenrekeningen naar een marktplaats of een opslagbot van een casino.\nNa de wijziging\n\nVolgens het technische account van CSFloat heeft Valve het eindpunt in 2017 gesloten en waren de oorspronkelijke item-ID’s niet langer beschikbaar voor externe partijen. Er is geen Valve verklaring gevonden over de reden voor deze wijziging. In dezelfde periode zijn er evenmin gepubliceerde maatregelen gevonden tegen de commerciële botaccounts die op grote schaal items verplaatsten.\n\nWat de reden er ook voor mag zijn, deze wijziging heeft de openbare bewijsketen verbroken. Een slachtoffer kan de oorspronkelijke ID-keten niet langer reconstrueren aan de hand van openbare gegevens om aan te tonen dat een specifiek gestolen voorwerp via een specifieke marktplaats of een specifiek casino is verkocht. De gegevens over het voorwerp bestaan nog steeds in de systemen van Valve; het publiek, onderzoekers en wetshandhavers die werken op basis van openbare gegevens hebben er echter geen toegang toe.\n\nNA: het is niet langer mogelijk om een specifiek item aan de hand van zijn oorspronkelijke Asset-ID te traceren op basis van openbare gegevens. De keten van bewaring van de oorspronkelijke ID voor een item dat na 2017 is verplaatst, bestaat alleen binnen de infrastructuur van Valve; er is geen dergelijk overzicht openbaar gemaakt. Float-, seed- en paint-identificatiegegevens maken slechts een gedeeltelijke, probabilistische koppeling mogelijk.\nIEconItems_730\nGET/IEconItems_730/GetPlayerItems/v1/\nTraceerbare payload (vóór de patch)\n\"id\": \"14892281934\",\n\"original_id\": \"11829910211\",\nStatus: Het slachtoffer kan de herkomst van het item volgen via verschillende bot-accounts.\nVerborgen payload (na de patch)\nHuidig\n\"id\": \"HIDDEN_BY_PRIVACY_SETTINGS\",\n\"original_id\": \"NULL\",\nStatus: externe partijen kunnen de herkomst van een item niet langer traceren aan de hand van de oorspronkelijke Asset-ID op basis van openbare gegevens.\nGevolgen voor het bewijsmateriaal: Na de wijziging waren de openbare gegevens die nodig waren om een specifiek item aan de hand van zijn oorspronkelijke Asset-ID te volgen – van de account van een slachtoffer naar een marktplaats of casinobot – niet langer beschikbaar. De interne gegevens bestaan nog steeds bij Valve; een slachtoffer, onderzoeker of rechercheur die op basis van openbare gegevens werkt, kan de oorspronkelijke ID-keten niet reproduceren (float-, seed- en paint-identificatoren maken slechts gedeeltelijke overeenstemming mogelijk).\n\nBron: Verslag van CSFloat Engineering over de sluiting in 2017 van IEconItems_730/GetPlayerItems — blog.csfloat.com/how-floatdb-tracks-items (gearchiveerd 2026-09-21) · de weergegeven payloads dienen ter illustratie van de veldstructuur en zijn geen vastgelegde reacties · er is geen Valve changelog voor de closure gevonden.\n\nDeel A — Technisch dossier · Paragraaf 5\nEén sessie. Meer toegang dan de gebruiker ziet.\nContext en bronbeperkingen\n\nDe API-sleutelarchitectuur van Valve, zoals die vóór de wijzigingen van 2023 bestond, week af van de gangbare industrienormen (OWASP ASVS, NIST SP 800-63B) en is het mechanisme dat wordt beschreven in de geautomatiseerde klachten over inventarisdiefstal die zijn bewaard in het bewijsarchief (paragrafen 6–8).\n\nDe regel Valve werd toegepast: de rekeninghouder heeft de sleutel aangemaakt, de voorwaarden aanvaard en draagt het verlies — dat is het antwoord in de gearchiveerde afwijzingen. Het verslag: tot december 2023 kon die sleutel al worden geregistreerd met alleen een gestolen sessiecookie. Geen wachtwoord. Geen Steam Guard. Geen melding aan de eigenaar van het account. De gebruiker had de sleutel niet aangemaakt, kon deze niet zien, maar kreeg te horen dat hij dat wel had gedaan. De mobiele bevestiging werd toegevoegd op 2023-12-04 — ongeveer zeven jaar na de verklaring uit 2016 en ruwweg zes jaar na de oplichtingspanelen die in het archief zijn bewaard. Die jaren werden niet betaald door Valve. Ze werden betaald uit de rekeningen die in de tussentijd waren leeggehaald, waarvan een deel van kinderen was.\n\nOWASP ASVS 2.8 / NIST SP 800-63BERNST: KRITIEK\n1. Onvoldoende versterkte authenticatie\n\nSteam maakte het mogelijk om API-sleutels met zeer uitgebreide rechten en een lange geldigheidsduur te genereren met alleen een sessiecookie. Er was geen 2FA (Steam Guard) of extra authenticatiecontrole vereist bij het instellen of wijzigen van een API-sleutel voor ontwikkelaars, waardoor de mobiele bevestiging Steam Guard — de enige tweede factor die Steam biedt — deze stap niet beschermde. (In 2016 werd in de eigen tracker van Valve gevraagd om een hardware-tweede factor en de issue is nog steeds open: Bijlage D, GH-01.)\n\nStatus: niet gepatcht vóór 2023. Hierdoor kon een script met een gestolen cookie een sleutel registreren zonder dat de gebruiker daar iets voor hoefde te doen.\nOWASP A01:2021 / Principe van minimale rechtenERNST: KRITIEK\n2. Het ontbreken van het beginsel van minimale rechten\n\nDe Steam Web API beschikte niet over op rollen gebaseerde autorisatiebereiken. Een API-sleutel voor ontwikkelaars die was uitgegeven voor de „alleen-lezen”-status van de voorraad, beschikte over volledige „schrijfrechten” — waaronder de mogelijkheid om bestaande transacties te wijzigen, nieuwe transacties te initiëren, webhooks te registreren en geldige, in behandeling zijnde transacties af te wijzen.\n\nStatus: systemische ontwerpfout. Eén sleutel = volledige lees- en schrijftoegang tot de voorraad en transacties van de rekening.\nOWASP A07:2021 / SessiesERNST: HOOG\n3. Defecte sessiebeheerfunctie\n\nGebruikers hebben gemeld dat gekaapte websessies die afkomstig zijn van IP-reeksen van serverhosting, blijven bestaan. Het is gebruikelijk om sessies te beëindigen bij geografische afwijkingen en bij het wijzigen van het wachtwoord; uit gebruikersmeldingen in het archief blijkt dat er sessies waren die na een wachtwoordwijziging actief bleven.\n\nStatus: gemeld gedrag (klachten van gebruikers in het archief). Sessies konden API-sleutels genereren zonder herauthenticatie.\nBlokkering op domeinniveau was technisch haalbaarHAALBAARHEID VAN HANDHAVING\n4. Het blokkeren van authenticatiehosts op domeinniveau was technisch haalbaar\n\nValve hanteert al een domeinlijst (de Link Filter) en ontvangt al elke authenticatiehostnaam in zijn eigen OpenID-verzoeken. De twee mechanismen zijn op geen enkele manier met elkaar verbonden die van buitenaf zichtbaar is: vanaf 2026-09-22 stond in 26 gevallen het hoofddomein op de filter, terwijl de proxy die de aanmelding verwerkte dat niet was.\n\nHet koppelen ervan is een eenvoudige technische klus: lees de openid.realm de hostnaam van elk binnenkomend verzoek controleren, deze vergelijken met een lijst en het verzoek weigeren of markeren. De afbeelding rechts toont de opbouw van een dergelijke routine. Het weigeren van de authenticatiehost — in plaats van alleen de openbare startpagina — zou de stap „Aanmelden met Steam” onderbreken, waar deze platforms van afhankelijk zijn.\n\nEr is geen openbaar bewijs dat Valve een dergelijke controle uitvoert. De gecombineerde vergoeding van de Steam Community Market van ongeveer 15% geldt voor verkopen die binnen de Market worden afgerond; deze wordt niet geheven op transacties buiten deze platforms.\n\nblock_auth_hosts.pyILLUSTRATIE\n// Lees de host Steam die al signalen ontvangt — geen scan\ndef on_openid_request(request):\nhost = parse_openid_realm(request)\nals gastheer in geblokkeerde_domeinen:\nafwijzen (verzoek)\nOpmerking: Pseudocode, uitsluitend ter illustratie. Beide delen bestaan al op Valve — de hostnaam van de auteur wordt in het verzoek meegeleverd en de domeinlijst is het Link Filter. Er is geen openbaar document waarin wordt uitgelegd waarom ze niet met elkaar in verband staan.\nParagraaf 5.1 — De normen waren niet geheim\nValve compileert elke dag volgens deze regels. Hier is dat niet gelukt.\n\nSteam is beschikbaar in de App Store en op Google Play, verkoopt via de grote creditcardverwerkers en maakt gebruik van API’s van derden, net als elk ander groot platform. Aan elk van deze relaties zijn gepubliceerde, gedateerde beveiligingseisen verbonden waaraan Valve moet voldoen om te kunnen blijven functioneren. Vergelijk de data van die vereisten met de data waarop de eigen web-API van Steam dezelfde beveiligingsmaatregelen heeft geïmplementeerd. Niets van het onderstaande is een interne norm, een interne memo of een bedrijfsgeheim: elke rij is een openbaar document met een publicatiedatum.\n\nGepubliceerde externe beveiligingseisen, met vermelding van de bijbehorende data, afgezet tegen de datum waarop de Steam Web API de gelijkwaardige beveiligingsmaatregel heeft ingevoerd\nDe gepubliceerde norm en de datum waarop deze van kracht werd\tDe Steam Web API over dezelfde vraag\nBepaalde machtigingOAuth 2.0 — RFC 6749, oktober 2012. In paragraaf 3.3 wordt gedefinieerd scope zodat een client alleen de toegang krijgt waar hij om vraagt. Dit is sindsdien de standaardinstelling van elke API van een groot platform.\tDe gedetailleerde scopes zijn verschenen op 16 januari 2026.Voorheen gaf één enkele Steam Web API-sleutel volledige lees- en schrijftoegang tot alle transacties van de rekening, ongeacht de reden waarom deze was uitgegeven. Dertien jaar en drie maanden na de specificatie waarin de besturing wordt gedefinieerd.\nEen sleutel is geen machtigingDe eigen Cloud-documentatie van Google: Een standaard API-sleutel is niet voldoende om een entiteit te authenticeren, en voor API’s die bronnen aanmaken of beheren, Gebruik geen autorisatiesleutels in de productieomgeving.\tDe Steam Web API-sleutel was precies dat.Een toonhouderstring, toegewezen aan een account, die op zichzelf voldoende is om de inventaris te lezen, een lopende transactie te annuleren en een nieuwe te verzenden. Op het moment van gebruik werd geen opdrachtgever geverifieerd.\nMeervoudige authenticatie bij bevoorrechte toegangPCI DSS 3.2, vereiste 8.3 — verplicht vanaf 1 februari 2018 voor alle niet-consolegebaseerde beheertaken en alle externe toegang tot de omgeving met kaartgegevens. Apple eiste vervolgens tweefactorauthenticatie van elke houder van een Developer Program-account vanaf 27 februari 2019: Ontwikkelaars met de rol ‘Accounthouder’ in een ontwikkelaarsprogramma moeten tweefactorauthenticatie inschakelen om zich aan te melden.\tEr was nog een tweede factor nodig om een API-sleutel aan te maken vanuit 4 december 2023.Tot dan volstond een gestolen sessiecookie, zonder dat er een melding op de telefoon van de accounthouder verscheen en zonder dat er achteraf een melding werd verstuurd. Vier jaar en negen maanden nadat Apple Valve zelf had ingevoerd dat er een tweede verificatiemethode nodig was, alleen al om in te loggen op een ontwikkelaarsportaal.\nLevenscyclus en intrekking van certificatenTwitch stelt aan elke applicatie van derden de volgende eisen: Je app moet het OAuth-token bij het opstarten en daarna elk uur valideren, en geeft aan dat het applicaties controleert die hier niet aan voldoen. De verouderde v5-API is op 28 februari 2022 volgens een gepubliceerd schema.\tEr is geen overzicht van de levenscyclus van de sleutel gepubliceerd.De wijziging van 2023 zorgde voor bescherming van het aanmaak-eindpunt. Er is geen bijbehorende Valve-verklaring gevonden waarin reeds geregistreerde sleutels worden behandeld, en er was helemaal geen changelog bij de wijziging gevoegd. Of sleutels die vóór deze wijziging waren aangemaakt ongeldig zijn geworden, kan niet worden vastgesteld aan de hand van openbare gegevens — en dat is juist de vraag waarop een betrokkene een antwoord nodig heeft om te weten of een sleutel die jaren eerder op zijn of haar account is aangemaakt nog steeds actief is.\nArchitecturale benchmark // Token Architecture\nGitHub: gedetailleerde bereiken versus Valve Steam Web API\n\nValve ontwikkelaars beheren dagelijks open-source-software op GitHub met behulp van gedetailleerde tokens op basis van het ‘minimale-toegangsrechten’-principe. Vergelijk dat eens met de monolithische sleutel die aan 130 miljoen Steam spelers is verstrekt.\n\nGitHub-token met gedetailleerde instellingen\nGebruikt door Valve op GitHub\n\nEen fijnmazig token met isolatie binnen een bepaald bereik en verplichte handhaving van de levenscyclus.\n\nToegang tot de repository:Alleen geselecteerde repos (1 repo)\nToegangsrechten toekennen:Alleen-lezen [✓]\nCode & Geheimen:Geen toegang [✕]\nVervaldatum:30 dagen (verplichte TTL)\nAuditlogboek:IP, User-Agent en tijdstempel\nBeveiligingsstatus: Een token met minimale rechten beperkt de schade tot één enkele bron die alleen-lezen is.\n!Valve Steam Web-API-sleutel\nUitgegeven aan 130 miljoen gebruikers\n\nEen enkele master-string van 32 tekens die de alles-of-niets-bevoegdheid voor transacties en voorraad bevat.\n\nToegang tot de account:VOLLEDIGE ACCOUNT (monolithisch)\nHandelsbeheer:Lezen, Annuleren, Weigeren [!]\nGranulaire toepassingsgebieden:GEEN (Aangekomen in 2026, 13 jaar te laat)\nVervaldatum:NOOIT (Geldig voor onbepaalde tijd)\nAuditlogboek:GEEN (Geen IP-geschiedenis voor deze gebruiker)\nKwetsbaarheid: Met een gestolen sleutel kunnen alle uitgaande handelsvoorstellen onopgemerkt worden onderschept.\nDe norm die in één richting wordt toegepast\n\nStel dat een leverancier Valve — een cloudprovider, een betalingsverwerker of een CDN — een eindpunt voor inloggegevens zonder tweede authenticatiefactor heeft achtergelaten, en dat maanden later de bedrijfsgegevens van Valve via een sleutel die op dat eindpunt was gegenereerd, zijn gelekt. Zou Valve accepteren dat de schuld ligt bij degene die op de link heeft geklikt? De gearchiveerde afwijzingen die in dit dossier zijn bewaard, beantwoorden de spiegelbeeldvraag voor de gebruiker: het standpunt is dat de accounthouder de sleutel heeft aangemaakt en het verlies draagt. Deze architectuur wordt gekenmerkt doordat de leverancier in het ene opzicht tekortschiet en de gebruiker in het andere opzicht verantwoordelijk is. Of dat zo is, is geen technische vraag, en het is ook geen vraag die in dit onderzoek kan worden beantwoord — dat is aan een rechtbank of een toezichthoudende autoriteit om te beslissen.\n\nIllustratie, geen bewijs — de norm omgekeerd geïnterpreteerd\nEen betalingsverwerker die het mogelijk maakte dat een script van een derde partij uitsluitend op basis van een browsercookie een transactie-inloggegeven met volledige rechten kon genereren, zonder dat de rekeninghouder hierom werd gevraagd.\nEen identiteitsprovider die het beveiligingslek heeft gedicht waardoor zijn tokens waren uitgegeven, en die geen informatie heeft gepubliceerd over de tokens die al waren uitgegeven.\nEen bank die op een betwiste overschrijving reageerde met de opmerking dat de gebruikte inloggegevens op de eigen rekening van de klant waren geregistreerd, en de zaak afsloot.\n\nDit wordt in geen enkel geval bedoeld als een conclusie over een specifiek bedrijf. Het gaat om dezelfde ontwerpbeslissingen, maar dan toegepast op een context waarin de reactie van de toezichthouder goed gedocumenteerd is — en dat is precies de vergelijking die van een toezichthouder wordt gevraagd.\n\nWat uit het dossier blijkt: De controles die ontbraken in de Steam Web API waren openbaar, verouderd en in verschillende gevallen voorwaarden Valve waaraan moest worden voldaan om de levering van de eigen producten te kunnen voortzetten. Het tijdsinterval tussen elke norm en de overeenkomstige Steam wijziging is meetbaar en wordt hierboven uiteengezet. Wat hiermee niet duidelijk wordt, is waarom. Er is geen Valve motivering voor deze intervallen gevonden, en hier wordt er ook geen verondersteld; dat document bevindt zich in Valve en is niet gepubliceerd.\n\nBronnen, stuk voor stuk openbare documenten: OAuth 2.0 — RFC 6749, oktober 2012 ↗ · Google Cloud — Documentatie over API-sleutels ↗ · PCI DSS 3.2, vereiste 8.3 — PCI SSC-informatiegids ↗ · Apple — Aankomende verplichting tot tweefactorauthenticatie voor accounthouders, 20 februari 2019 ↗ gearchiveerd 2025-05-06 ↗ · Twitch — vereiste voor tokenvalidatie ↗ en de Kennisgeving over het stopzetten van v5 ↗ gearchiveerd 2025-01-27 ↗. De data van Steam zijn die in het updateverslag in dit gedeelte; de vermeldingen voor 2023 en 2026 zijn de versies die Valve zonder changelog heeft uitgebracht. Opgehaald op 2026-09-22.\n\nValve's eigen updateregister — gedateerd, afkomstig uit openbare bronnen\nDatum\tValve wijziging\tAangekondigd?\tWat er gesloten was\tVertraging: mechanisme openbaar → opgelost\tBron\n2026-09-01\tAutomatische signalering van verdachte chatberichten\tJa\tGevaarlijke links / patronen in groepschats\t—\tnieuws ↗\n2026-01-16\tGedetailleerde toepassingsgebieden van de Steamworks Web API\tJa\tToepassingsgebieden met minimale rechten voor ontwikkelaarsleutels\t—\taankondiging ↗\n2025-07-15\tCS2 Handelsbescherming & terugdraaiingsperiode\tJa\tNiets. Dit is geen beveiligingsoplossing die de onderliggende oorzaak aanpakt. De toegang tot accountherstel via de helpdesk blijft ongewijzigd. Het in gang zetten van een terugboeking leidt automatisch tot een handelsblokkering van 30 dagen (Skinvault ↗), terwijl een schok op de contante markt leidde tot een daling van de marktkapitalisatie met $104M (-25%) in 24 uur (CSMarketCap ↗). In 2026 werden de timers per artikel ingesteld (Skin.land ↗).\t—\tVeelgestelde vragen ↗\n2025-05-14\tMededeling over accountbeveiliging\tJa\tRichtlijnen voor Stealer / sessiekaping\t—\taankondiging ↗\n2024-10-02\tCS2 'The Armory' 7 dagen vasthouden\tJa\tWacht even met het ruilen/verkopen van Armory-items\t—\taankondiging ↗\n2024-09-18\tHandelsbeperking bij het inloggen met een nieuw apparaat\tJa\tHandelsbeperking van 2–7 dagen op nieuwe apparaten\t—\tVeelgestelde vragen ↗\n2024-02-14\tWachtstand voor het wijzigen van profielnaam en avatar\tJa\tNa het wijzigen van de naam geldt een wachttijd van 2–4 uur voor transacties\t—\tbericht ↗\n2023-12-04\tBevestiging via mobiel voor API-sleutels\tGeen wijzigingenlogboek\tStille sleutelregistratie uitsluitend via cookies\t≈6 jaar na de panelen uit de periode 2017\tdev-pagina ↗\n2023-10-24\tSMS-MFA voor het publiceren van game-builds\tJa\tSteamworks: builds publiceren\t—\taankondiging ↗\n2023-07-12\tWaarschuwing inzake aangepaste biografische inhoud\tJa\tPhishing-links in biografieën\t—\tforum ↗\n2023-01-25\tProfiel {LINK VERWIJDERD} & afkoelperiode\tJa\tLinks in de profieltekst\t—\tVeelgestelde vragen ↗\n2022-10-24\tHerziening van het inlogproces en inkorting van cookies\tGeen wijzigingslogboek\tOneindig veel gestolen sessies\t— (Migratie van IAuthenticationService-tokens)\tnieuws ↗\n2022-10-12\tMobiele app 3.0: inloggen via QR-code\tJa\tPaneel voor het intrekken van sessieautorisatie\t—\tnieuws ↗\n2022-05-10\tEindpunten voor het annuleren van transacties verwijderd\tGeen wijzigingenlogboek\tAanbod-swap (annuleren en opnieuw verzenden)\t≈5 jaar na de panelen uit de periode 2017\tnummer 325 ↗\n2020-05-25\tDota 2: 7-daagse handelsblokkering\tJa\tSnel doorverkopen van artikelen\t—\tblog ↗\n2018-03-29\tCS:GO 7-daagse handelsblokkering\tJa\tOnmiddellijke witwassen via bots\t≈20 maanden na de verklaring van juli 2016\tblog ↗ gearchiveerd 2025-02-26 ↗\nBronnen: de gelinkte Valve berichten, helppagina’s en GitHub-issues, zoals aangegeven. Drie cruciale fixes die zonder changelog zijn uitgebracht (mei 2022, oktober 2022, december 2023) en door gebruikers werden ontdekt, niet aangekondigd door Valve — die asymmetrie maakt deel uit van het handhavingsverslag. Vertragingen worden alleen berekend wanneer de datering van het dossier zelf (verklaring van juli 2016; oplichtingspanels uit 2017) het startpunt aangeeft; „—” betekent dat hier geen dergelijk startpunt is vastgesteld.\nDeel A — Technisch dossier · Paragraaf 6\nInteractieve simulator voor exploits en kapingen\nContext en bronbeperkingen\n\nEen weergave van het traject vanaf het phishingbericht tot aan de registratie van de sleutel aan de serverzijde en de uitvoering van de transactie. Vóór 2023 kon een op een account geregistreerde Web API-sleutel de voorraad van dat account inzien, een lopend transactieaanbod annuleren en een nieuw aanbod aanmaken, zonder dat de accounthouder bij geen van deze handelingen een bevestigingsscherm te zien kreeg. Dat is het ontbreken van het ‘least privilege’-principe (OWASP A01:2021). De tijdsduur in deze simulatie is ter illustratie en betreft geen live metingen van het huidige platform.\n\nDoorloop de gereconstrueerde kaping stap voor stap. Bij elke fase wordt weergegeven wat de accounthouder ziet en, daarnaast, het telefoontje Steam dat op datzelfde moment binnenkomt. Al die oproepen zijn correct geverifieerd. Geen enkel onderdeel van de reeks hoeft te mislukken vanwege de authenticatie door Steam — het is juist nodig dat de sleutel die het uitgeeft geen toepassingsgebied heeft (OWASP A01:2021).\n\nWat de speler ziet. Wat er daarachter verandert.STAP-VOOR-STAP-SIMULATOR\nStap 5 / 5\n\nDe aanval is voltooid. In de verwachting dat er een melding op zijn mobiel verschijnt voor de oorspronkelijke transactie, keurt het slachtoffer de vervangende transactie goed. Dit is een geïntegreerde forensische simulatie die laat zien hoe het ontbreken van het ‘Least Privilege’-principe (OWASP A01:2021) geautomatiseerde kaping van bedrijfsmiddelen binnen een fractie van een seconde mogelijk maakt.\n\n01 / HET CHAT-AASEen vriend vraagt of ik wil stemmenHet slachtoffer ontvangt een bericht met een link.\n02 / DE AANMELDINGEen portaal voor lookalikesHet slachtoffer voert zijn inloggegevens in.\n03 / DE TOEGANGHet aanmaken van een Silent Web APIDe aanvaller registreert een ontwikkelaarsleutel.\n04 / DE OVERGANGLegitieme handel werd vervangen doorDe Clone-bot maakt een kopie van de beoogde ontvanger.\n05 / BEVESTIGINGNamaak goedgekeurdVerkeerde aanbieding goedgekeurd op de mobiele telefoon.\nDezelfde stap, gezien vanuit het netwerkReconstructie van het patroon van vóór 2023 · illustratieve belvormen\nSlachtofferKeurt de mobiele melding goed die voor de oorspronkelijke transactie was verwacht.\nAanvallerOntvangt de artikelen op de kloonrekening.\nSteam zietEen overschrijving die door de rekeninghouder op een geregistreerd apparaat is bevestigd.\nConfirmation genuine — made by the account holder\nRecipient the clone bot, not the intended counterparty\nThe confirmation is authentic. The offer it confirms is not the one the user initiated.\n\nHet nalatenschap: een transactie die de gebruiker heeft goedgekeurd. Dat is het record Steam dat Support leest wanneer de klacht binnenkomt, en de reden waarom de gearchiveerde klachten als ‘gebruikersfout’ zijn afgesloten. De klachten staan in het handhavingsarchief.\n\nDeel A — Technisch dossier · Paragraaf 7\nDe eindpunten achter de reeks.\nContext en bronbeperkingen\n\nDit zijn de Steam Web API-eindpunten die de gemelde kapingsscripts gebruikten om transacties te onderscheppen zonder de bevestigingsstappen aan de browserzijde te doorlopen.\n\nVier gedocumenteerde eindpunten volstaan. Geen van alle is een kwetsbaarheid, en bij geen enkel punt hoefde misbruik te worden gemaakt — een geldige sleutel roept ze aan en Steam geeft antwoord. De sleutel is het enige wat de aanvaller hoefde te stelen.\n\nIEconService / GetTradeOffers / v1ENQUÊTE\n\nWordt gebruikt om de handelsaanbiedingen van de account bij te houden. Scripts pollen dit eindpunt herhaaldelijk met de gehackte API-sleutel; het retourneert de details van nieuw aangemaakte, in behandeling zijnde of gewijzigde handelsaanbiedingen. De polling-intervallen worden hier niet gemeten.\n\nBedreigingsvector: Geeft de ID’s van lopende handelsvoorstellen en de profielgegevens van de ontvanger weer.\nIEconService / CancelTradeOffer / v1INTERACTIE\n\nWordt gebruikt om het legitieme handelsaanbod van de gebruiker programmatisch ongeldig te maken. Vóór 2023 werd de sleutel niet beschermd door tweefactorauthenticatie, waardoor een geautomatiseerde server een aanbod kon annuleren zodra het werd gedetecteerd, zonder dat de accounthouder hierover werd geïnformeerd.\n\nBedreigingsvector: De transactie wordt geannuleerd voordat de rekeninghouder de bevestiging via de mobiele app heeft voltooid.\nISteamUser / GetPlayerSummaries / v2RECON\n\nEr is een query uitgevoerd om de profielnaam, de URL van de avatarafbeelding en het niveau van de legitieme handelspartner op te halen. Hierdoor kan het script een vooraf aangemaakt kloonaccount zo aanpassen dat het overeenkomt. Hier wordt geen tijd gemeten.\n\nBedreigingsvector: Levert de gegevens die nodig zijn om zich voor te doen als de beoogde ontvanger.\n/dev/ajaxregisterkeyCREATIE\n\nHet registratie-eindpunt van Steam voor sleutels. Vroeger kon elke actieve browsercookie-sessie (`steamLoginSecure`) een sleutel registreren zonder bevestiging van Steam Guard op het mobiele apparaat en zonder dat de accounthouder hiervan op de hoogte werd gesteld.\n\nBedreigingsvector: Een permanente inlogcode die door een script is aangemaakt, zonder dat de accounthouder hiervan op de hoogte is.\nDeel A — Technisch dossier · Paragraaf 8 · Artikel 7 van de AVG\nEen aangevinkt vakje. Wiens handeling?\nContext en bronbeperkingen\n\nBij het weigeren van een vergoeding wordt in de in het archief bewaarde antwoorden van de klantenservice gesteld dat de rekeninghouder de API-sleutel heeft aangemaakt en, door het vakje aan te vinken, akkoord is gegaan met de voorwaarden.\n\nIn het antwoord van de helpdesk wordt de sleutel aan de rekeninghouder toegeschreven. De vraag is of uit het dossier blijkt wie het daadwerkelijk heeft aangemaakt.\n\nIn het waargenomen patroon van API-sleutelkaping heeft het slachtoffer de pagina voor het aanmaken van een API-sleutel echter nooit gezien of bezocht. Het toestemmingsveld wordt verzonden door een script dat een headless POST-verzoek uitvoert met de gestolen sessiecookie.\n\nKrachtens artikel 7 en artikel 4, lid 11, van de AVG moet toestemming een vrijwillig, specifiek, geïnformeerd en ondubbelzinnig kenmerk van de wil van de betrokkene zijn. De auteurs zijn van mening dat een veld voor het aanvaarden van de voorwaarden dat door een kwaadaardig script met een gestolen cookie wordt verzonden, zonder dat er een pagina aan de accounthouder wordt getoond, niet aan die definitie kan voldoen. Of dit het geval is, is aan de toezichthoudende autoriteit om te beoordelen.\n\nForensische analyse van de payload: registratie van sleutels\nPOST https://steamcommunity.com/dev/ajaxregisterkey\n// Payload van het verzoek (ingevoegd via een kapingsscript)\n{\n\"agreeToTerms\": \"akkoord\", <-- automatisch ingevoerd, zonder menselijke tussenkomst\n\"domein\": \"localhost\", ← niet gevalideerd — elke waarde wordt geaccepteerd, inclusief localhost\n\"sessionid\": \"8f0d8ef763ab2140bf89de2a\"\n}\nDe vraag aan de toezichthoudende autoriteit: wanneer de rekeninghouder nooit op het vakje voor toestemming heeft geklikt, of de ten laste van de rekening geregistreerde aanvaarding van de voorwaarden voldoet aan de eis van artikel 7 dat de betrokkene vrijelijk, specifiek, geïnformeerd en ondubbelzinnig zijn of haar wil kenbaar moet maken, en of Steam Support zich hierop mag beroepen om een claim af te wijzen.\n\nBron: de vorm van de sleutelregistratie, zoals gereconstrueerd op basis van het openbare eindpunt en uit kapingsmeldingen die in het bewijsmateriaalarchief zijn bewaard (doorzoekbare versie van 2026-09-17) · De weergegeven sessie-ID is een tijdelijke aanduiding, geen vastgelegde waarde.\n\nForensische autopsie · De vector voor vervanging van grondstoffen\nHoe Valve uiteindelijk een einde maakte aan „handelsvervanging“ — en waarom het zeven jaar vol tijdelijke oplossingen kostte\n\nAl bijna tien jaar lang is de \"Vervanging van API-sleutels\" (of API-MitM-zwendel) was het meest winstgevende model voor accountovervallen op Steam, waarbij honderden miljoenen dollars aan skins werden weggesluisd van nietsvermoedende spelers. Valve heeft de kwetsbaarheid niet verholpen door de kwetsbare API-architectuur te repareren; in plaats daarvan heeft Valve zeven jaar lang vier platformbrede drempels ingebouwd die de liquiditeit van de handel binnen de community ernstig hebben belemmerd, terwijl de onderliggende oorzaak onopgelost bleef.\n\n1. De dood door mimiek\nAfkoelperiode voor avatar en naam (februari 2024)\n\nDe aanval vereiste een reactietijd van minder dan een seconde: de oplichtingsbot onderschepte een uitgaande transactie en haalde de avatar en naam van de ontvanger op via ISteamUser, en het profiel in 200 ms gekloond. Op 14 februari 2024 heeft Valve stilletjes een verplichte Afkoelperiode van 2 tot 4 uur (Fout 34) onmiddellijk na elke wijziging van de profielnaam of het profielbeeld. Een bot kan een ontvanger niet langer direct klonen zonder zichzelf uit te sluiten van de handel.\n\n2. De economische ondergang\n7-daagse CS2-trendomkering (juli 2025)\n\nValve heeft eenzijdig ingevoerd Omkeringen in de handel voor Counter-Strike-items. Elke geruilde skin krijgt zeven dagen lang de status „Trade Protected“. Als een slachtoffer ontdekt dat het item is vervangen, klikt hij of zij op „Reverse Trade“ in Steam Support, waarna de skin onmiddellijk wordt teruggezet in de inventaris en de ontvanger wordt geblokkeerd. Omdat de verhandelingsblokkering van 7 dagen voorkomt dat oplichters het item naar een uitbetalingssite kunnen verplaatsen, levert de diefstal geen winst op.\n\n3. De dood van de ‘Silent Key’\nVerplichte mobiele pushmeldingen voor API (december 2023)\n\nIn het verleden konden kwaadaardige scripts met behulp van een gestolen sessiecookie een 'headless' POST-verzoek op de achtergrond uitvoeren naar /dev/ajaxregisterkey zonder het slachtoffer hiervan op de hoogte te stellen. Op 4 december 2023 heeft Valve een expliciete bevestiging via een pushmelding verplicht gesteld in de Steam mobiele app voor het genereren van een Web API-sleutel, waardoor het stil genereren van sleutels op de achtergrond werd uitgeschakeld.\n\n4. Waarschuwingen in de mobiele app\nBanners met accountleeftijd en naam (2022–2024)\n\nValve heeft het bevestigingsvenster voor mobiele apparaten aangepast, zodat de gegevens van de handelspartner worden weergegeven Steam duur van de rekening (aanmaakdatum), Steam-niveau, en een expliciete oranje waarschuwing: \"Deze gebruiker heeft onlangs zijn of haar profielnaam gewijzigd\", waardoor de visuele illusie voor oplettende slachtoffers wordt doorbroken.\n\nDe drie tekortkomingen in het lappendeken van Valve: waarom oplichters gewoon van doelwit zijn veranderd\n1. De maas in de wet inzake het uitsluiten van games (Dota 2 & TF2)\n\nTrade Reversals werden uitsluitend ingezet voor Counter-Strike 2. Items in Dota 2 en Team Fortress 2 blijven volledig onbeschermd vanwege de complexiteit van het vervaardigen en het plaatsen van edelstenen. Voor hoogwaardige items ter waarde van duizenden dollars (Dragonclaw Hooks, Golden Baby Roshans, Unusual TF2 burning flames) geldt geen terugdraaitermijn. Oplichters hebben de geautomatiseerde API-onderschepping simpelweg omgeleid naar Dota 2- en TF2-handelaars, waar de Steam-klantenservice het beleid uit 2016 inzake „geen teruggave van items“ strikt handhaaft.\n\n2. Het \"Zombie Key\"-reservoir (zonder vervaldatum)\n\nTerwijl Valve mobiele push-2FA heeft toegevoegd om nieuw sleutels in december 2023, Valve bestaande verouderde API-sleutels zijn nooit ingetrokken, verlopen of verwijderd. Miljoenen actieve accounts waarvoor sleutels zijn gegenereerd (of waarvoor vóór december 2023 stilletjes sleutels zijn aangemaakt door phishing of malware) bevatten nog steeds actieve inloggegevens met geen vervaldatum (geen TTL) en geen time-out bij inactiviteit. Cybercriminelen beschikken over enorme databases met historische gegevens van deze permanente sleutels en blijven deze regelmatig controleren IEconService ongestoord.\n\n3. De straf voor het slachtoffer: een handelsstop van 30 dagen\n\nZelfs in CS2 wordt de opgelichte speler in Valve bestraft: als je in Steam Support op „Reverse Trade“ klikt, wordt automatisch een verplichte handelsstop en uitsluiting van de Community Market van 30 dagen voor de account van het slachtoffer. Valve bestraft de gebruiker met een verbanning van het platform voor een maand als afschrikwekkende maatregel tegen „frivole“ terugdraaiingen, waardoor slachtoffers worden ontmoedigd om transacties met liquide items van lagere waarde terug te draaien.\n\nHet grote regelgevingsschandaal: zeven jaar lang omzeilingen versus één API-toepassingsgebied\n\nWaarom heeft Valve zeven jaar lang de tijd genomen om handelsblokkades, afkoelingsperiodes voor accounts en omkeerbare handelsvergrendelingen te bedenken – waardoor de hele game-economie werd ontwricht en $104M aan marktkapitalisatie verloren ging – in plaats van de in de sector gangbare oplossing door te voeren?\n\nZoals blijkt uit de officiële Steamworks-aankondiging van Valve op 16 januari 2026 (Aankondiging #493839547938902179 ↗), Valve reeds gebouwd Gedetailleerde machtigingsgroepen (Algemeen, Microtransacties, Economie, Verkoopgegevens) en IP-whitelisting voor uitgeverssleutels voor bedrijven. Valve beschikte al jaren over de technische oplossing. Eén enkel selectievakje voor de gebruiker—\"Voorkom dat deze Web API-sleutel toegang krijgt tot IEconService (Trade Management)\" of een whitelist voor thuis-IP-adressen — zou de zwendel met handelsvervanging in 2018 hebben uitgeroeid zonder enige economische nevenschade. Valve weigerde gewone spelers de bescherming te bieden die het voor zakelijke partners had ontwikkeld.\n\nDeel B — Regels en handhavingsgeschiedenis · Artikel 9\nHun spelregels. De geregistreerde platforms.\nContext en bronbeperkingen\n\nDit grootboek brengt de expliciete bepalingen uit de Steam Abonneeovereenkomst (SSA) en Steam Online gedrag (SOC) richtlijnen die rechtstreeks gericht zijn tegen actieve, grootschalige commerciële entiteiten.\n\nDe regel: geen commercieel gebruik, geen gokken, geen bots — en Steam De klantenservice beroept zich op deze bepalingen wanneer zij weigert de spullen van een slachtoffer terug te geven. Het verslag: dezelfde bepalingen hebben op het eerste gezicht betrekking op de commerciële platforms in dit register, die draaien op Steam identiteiten, Steam bots en Steam overdrachten. De bepaling wordt toegepast op de persoon die de huiden kwijtgeraakt is en, voor zover uit openbare bronnen blijkt, niet op de bedrijven die ze vervoeren.\n\nIn de gearchiveerde klachten verwijst Steam Support naar de \"Geen commercieel gebruik\" en \"Geen automatisering/bots\" bepalingen bij het weigeren van teruggave van goederen aan slachtoffers van API-sleutelfraude. Dezelfde bepalingen zijn op het eerste gezicht van toepassing op de commerciële platforms die in dit dossier zijn opgenomen, die authenticatie uitvoeren via Steam OpenID en goederen verplaatsen via geautomatiseerde Steam-accounts. Er wordt hier geen schatting gemaakt van de marktbrede omzetcijfers (zie de handhavingsstatistieken hieronder). Wat uit de gegevens blijkt, is de regel die is toegepast op individuele accounts in de gearchiveerde zaken, en er zijn geen gepubliceerde handhavingsgegevens per exploitant voor de platforms. Die asymmetrie wordt in deze paragraaf gedocumenteerd.\n\nDe centrale vraag / selectieve handhavingRegels → Schaal → Verantwoording\nEén regelboek. Ongelijke handhaving.\n\nUit het register blijkt dat commerciële diensten gebruikmaken van Steam-identiteiten, inventarissen, bots en overdrachten als operationele infrastructuur. De SSA verbiedt commerciële exploitatie en automatisering zonder toestemming. Uit de gearchiveerde klachten blijkt dat deze regel van toepassing was op individuele accounts, terwijl het openbare register geen vergelijkbaar overzicht per exploitant bevat voor de hier gedocumenteerde platforms. Maak de regel, het bewijsmateriaal en het handhavingsbesluit voor elk daarvan openbaar.\n\n189websites die onder de audit vallen\n44routes met afzonderlijke domeinen in het live-register — 27 met een gepubliceerd bewijsbestand, 17 handmatig verzameld. Alleen al de browser-audit van 189 websites heeft 25 daarvan opgelost; het register voegt de handmatig verzamelde routes hieraan toe.\n12 jaar en 6 maandencsgogem.com is geblokkeerd in de linkfilter; api.csgem.com geregistreerd 2014-03-08 en nooit geblokkeerd — een van de 26 van dergelijke paren per 2026-09-22\nGeen geverifieerd totaalraming van de omzet voor de gehele markt niet meegerekend\nSteam Gedrag online\n\"…het is verboden om op Steam een van de volgende handelingen te verrichten of te proberen te verrichten: […] Commerciële activiteiten ontplooien. Voorbeelden van dergelijk verboden gedrag zijn onder meer: advertenties plaatsen; wedstrijden organiseren; gokken; het kopen of verkopen van Steam-accounts; het verkopen van content, cadeaubonnen of andere artikelen; en bedelen.\"\n\nstore.steampowered.com/online_conduct ↗ gearchiveerd 2026-09-21 ↗\n\nSSA § 2.G — Commercieel gebruik\n\"…[u mag] de Inhoud en Diensten of enig onderdeel daarvan niet voor commerciële doeleinden exploiteren, tenzij dit elders in deze Overeenkomst uitdrukkelijk is toegestaan…\"\n\nZoals gemeld, werd in de kennisgevingen van Valve uit 2016 een beroep gedaan op de persoonlijke, niet-commerciële licentie. Geen enkele exploitant heeft een Valve-vergunning overgelegd. store.steampowered.com/subscriber_agreement ↗ gearchiveerd 2026-09-18 ↗\n\nSteam Gebruiksvoorwaarden voor de Web-API\n\"U mag de Steam Web API of Steam gegevens op geen enkele wijze gebruiken die in strijd is met de Steam abonneeovereenkomst.\"\n\nSkin-marktplaatsen van derden werken via geautomatiseerde accounts die gebruikmaken van de Steam API. De regeltekst voorziet niet in uitzonderingen voor commerciële activiteiten. steamcommunity.com/dev/apiterms ↗ gearchiveerd 2026-09-21 ↗\n\nSSA § 4.C\nAutomatisering\n\nScripts, bots en interactie door niet-menselijke entiteiten zijn verboden. Het grootboek registreert bot-handel, accountfarms en geautomatiseerde routering op commerciële schaal.\n\nControleren 153gegevens die onder deze clausule zijn getagd ↗\nWat er krachtens deze clausule in het dossier staat153 getagde platforms\nOpenen van de behuizing15\nSkin Casino13\nCS2-markt9\nHuidroulette8\ncsgoempire.com→csgoempirelogin4.comCasino\nrollbit.com→rbsnin.comCryptocasino\n500.casino→fivezerozero.coCasino met vergunning\n\nHiervan, 153 zijn ook getagd onder SSA § 2.G en 2 zijn ook getagd onder SSA § 1.C — dezelfde diensten vallen onder meer dan één bepaling, en daarom komen de voorbeelden meerdere keren voor.\n\n28 van de 153 werden waargenomen waarbij authenticatie plaatsvond via een afzonderlijk registreerbaar domein. Een tag registreert een gedateerde waarneming waardoor het platform op het eerste gezicht onder de bepaling valt; het gaat niet om een vastgestelde overtreding, en voor geen van deze gevallen is een Valve-autorisatie overgelegd.\n\nSSA § 2.G\nCommercieel gebruik\n\nVoor commerciële exploitatie is uitdrukkelijke toestemming vereist. Vergelijk de gedocumenteerde bedrijfsmodellen, hun omvang en eventuele bekendgemaakte vergunningen of handhavingsmaatregelen.\n\nControleren 175gegevens die onder deze clausule zijn getagd ↗\nWat er krachtens deze clausule in het dossier staat175 getagde platforms\nOpenen van de behuizing15\nSkin Casino13\nCS2-markt9\nHuidroulette8\ncsgoempire.com→csgoempirelogin4.comCasino\nrollbit.com→rbsnin.comCryptocasino\n500.casino→fivezerozero.coCasino met vergunning\n\nHiervan, 153 zijn ook getagd onder SSA § 4.C en 24 zijn ook getagd onder SSA § 1.C — dezelfde diensten vallen onder meer dan één bepaling, en daarom komen de voorbeelden meerdere keren voor.\n\n28 van de 175 werden waargenomen waarbij authenticatie plaatsvond via een afzonderlijk registreerbaar domein. Een tag legt een gedateerde waarneming vast waardoor het platform op het eerste gezicht onder de bepaling valt; het gaat niet om een vastgestelde overtreding, en voor geen van hen is een Valve-autorisatie overgelegd.\n\nSSA § 3.A\nVPN en het verbergen van je locatie\n\nHet verbergen van je locatie via een IP-proxy kan leiden tot beëindiging van het account. Authentificatiehosts met een apart domein vereisen een afzonderlijke analyse: ga na wat er wordt verborgen en welke regel van toepassing is.\n\nControleer de gegevens van de auth-host ↗\nSteam Help / URL-beleid\nLinkverduistering\n\nSteam verbiedt linkverkorters en tools die de bestemming van links verbergen. Een apart authenticatiedomein — rbsnin.com in het inlogproces van Rollbit, auth.dota.trade in CS.MONEY’s — roept de vergelijkbare vraag op of de bestemming die aan de OpenID-verificator van Steam wordt getoond, de actieve site identificeert.\n\nHet URL-beleid van Valve ↗\n\nVerwijzingen naar regels: Steam Abonnementsovereenkomst, herziening van 10 september 2026 gearchiveerd 2026-09-18 ↗ · Steam Gebruiksvoorwaarden voor de Web API gearchiveerd 2026-09-21 ↗ · Steam URL-beleid (linkversluiering). De aantallen geven een overzicht van de gegevens en tags in dit dossier; het gaat hier niet om het aantal vastgestelde overtredingen.\n\nHet vertrouwenstekort\nWie beoordeelt de beslissing wanneer de hulpverlening de zaak afsluit?\n\nUit de bewaarde klachten blijkt dat er sprake is van permanente sancties, onbeantwoorde bezwaren en weigeringen om gestolen items terug te geven. Toets deze verslagen aan de hand van de daadwerkelijke ticketgeschiedenis, de beschikbare oplossingen en de logbestanden van de accounttoegang. Een algemene verklaring in verband met phishing kan niet aantonen wie het initiatief heeft genomen tot een reset of wie een API-sleutel heeft aangemaakt.\n\nLees de geregistreerde klachten ↗De bijbehorende documenten opvragen →Relatiegrafiek van de moderator →\nDeel B — Regels en handhavingsgeschiedenis · Artikel 10\nEen API voor automatisering. Een regel tegen automatisering.\nContext en bronbeperkingen\n\nDe vraag die in dit hoofdstuk aan de orde komt, is hoe deze twee met elkaar in overeenstemming kunnen worden gebracht: welke toepassingen van de API zijn toegestaan, door wie en op basis van welke gepubliceerde criteria. Er wordt hier geen schatting gemaakt van het aantal geautoriseerde commerciële API-gebruikers, en het ontbreken van een gepubliceerde lijst impliceert evenmin een dergelijk aantal — het ontbreken zelf is de bevinding, niet een cijfer dat erachter schuilgaat. De hierboven geciteerde Steam ondersteuningsberichten worden door het ArchiSteamFarm-project in zijn eigen FAQ weergegeven (woordelijk geverifieerd 2026-09-22); het zijn geen Valve publicaties en de accounts waaraan ze zijn verzonden, worden niet geïdentificeerd.\n\nDe regel (SSA § 4.C): geen scripts, geen bots, geen niet-menselijke systemen op Steam. Het verslag: Valve biedt een headless REST API aan die uitsluitend bedoeld is voor server-naar-server-automatisering, en geeft de toegangscode aan elk account. Gebruikers worden geblokkeerd wegens automatisering; de automatiseringsinterface is een eigen product van Valve. Welke commerciële toepassingen zijn toegestaan, is nooit bekendgemaakt.\n\nDe misvatting van de „gameontwikkelaar”\nSteamworks SDK (legaal)\n\nWordt gebruikt door erkende gamestudio’s om prestaties, matchmaking en ranglijsten in hun gameclients te integreren. Vereist een complexe C++-integratie en officiële partnerregistratie.\n\nSteam Web-API (De maas in de wet)\n\nEen ‘headless’ JSON/REST-architectuur die is ontworpen voor externe webservers. In het hier beschreven ‘hijack’-patroon wordt deze architectuur gebruikt om voorraadgegevens uit te lezen en peer-to-peer-transacties vanaf externe servers te beïnvloeden; de legitieme toepassingen ervan worden in dit dossier niet beschreven.\n\nVoor wie de sleutel bedoeld isEen gewone Steam-gebruiker heeft binnen de client geen behoefte aan een Web API-sleutel; de sleutelpagina bevindt zich onder een URL voor ontwikkelaars en het gedocumenteerde doel ervan is externe, server-side toegang. Uit de gearchiveerde klachten over accountkaping blijkt dat slachtoffers niet wisten dat de pagina bestond, totdat er een sleutel op hun account was geregistreerd.\nDe tegenstrijdigheid van automatisering\n\nSSA § 4.C bepaalt: \"Het is niet toegestaan om op welke manier dan ook gebruik te maken van scripts, bots, macro’s of andere niet door mensen bestuurde systemen (‘automatisering’) om met de inhoud en diensten op Steam te communiceren.\" Toch zijn de Web API-eindpunten (zoals CancelTradeOffer) vereisen geen gebruikersinterface en geen captcha en omzeilen de Steam-client volledig. De API is ontworpen voor automatisering tussen servers; de regel verbiedt automatisering door gebruikers; de grens tussen beide is niet bekendgemaakt.\n\nEen server-side rol in de handelsstroom\n\nMet een Web API-sleutel kan een server van een derde partij transacties op de rekening uitvoeren zonder tussenkomst van de Steam-client. Bij het ‘hijack’-patroon bevindt die server zich tussen de rekeninghouder en de transactieserver.\n\n→Er wordt geen scherm met transactiebevestiging weergegeven voor de acties van de toets.\n→Maakt polling op de achtergrond mogelijk (GetTradeOffers).\n→Annuleert aanbiedingen en stelt deze opnieuw op zonder tussenkomst van de gebruiker.\nValve heeft de interface ontwikkeld, automatisering door gebruikers in zijn regels verboden en geen criteria gepubliceerd op basis waarvan commercieel gebruik is toegestaan.\nDeel B — Regels en handhavingsgeschiedenis · Artikel 11\nTien dagen geëist. Tien jaar om verantwoording af te leggen.\nContext en bronbeperkingen\n\nOp 20 juli 2016 stelde de juridisch adviseur van Valve gokexploitanten een termijn van 10 dagen. Tien jaar later (op het moment van de dossiermomentopname, 2026-09-21) is ten minste één platform dat in persberichten over die kennisgeving werd genoemd, CSGOFast, nog steeds operationeel met een authenticatiehost op een apart domein. De tekst is hieronder gereconstrueerd op basis van persberichten van 21 juli 2016; de reconstructie is geen scan. Het handhavingsdossier waarop de kennisgeving doelspeelde, is niet gepubliceerd. De open brief aan de Commissie is Paragraaf 2.\n\nLees de mededeling van juli 2016 naast de latere opmerkingen. Wat nog ontbreekt, is een overzicht van de handhavingsmaatregelen per exploitant.\n\nEen week eerder — 13 juli 2016, in het openbaar\n\nOp 13 juli 2016 gearchiveerd 2026-09-21 ↗, Valve beschreef hoe goksites gebruik maakten van Steam: OpenID voor accountidentificatie en geautomatiseerde accounts voor het plaatsen van weddenschappen. Valve verklaarde dat het gebruik van deze mechanismen voor het exploiteren van een gokbedrijf in strijd was met de API- en gebruikersvoorwaarden. Zowel de beschrijving van het mechanisme als het verbod staan in de eigen, gedateerde verklaring van Valve. Op 2026-09-21 leverden de geteste authenticatiehosts met afzonderlijke domeinen geen blokkering door de linkfilter op, en Valve heeft geen handhavingsrecord per operator gepubliceerd.\n\nBIJLAGE A / JULI 2016RECONSTRUCTIE VAN DE ZETTEKST\nVALVE CORPORATION\n\nBellevue, WA\n\nDATUM:Juli 2016 (zoals gemeld in de pers op 21 juli 2016)\nVAN:Karl Quackenbush, hoofd juridische zaken\nRE:Stakingsbevel — commercieel gebruik van Steam-accounts\nOPMERKING:Reconstructie van de gerapporteerde tekst; geen scan\n\n\"Wij zijn ons ervan bewust dat u een van de hieronder vermelde goksites exploiteert. U gebruikt Steam accounts om deze activiteiten uit te voeren. Krachtens de Steam abonneeovereenkomst zijn de diensten Steam en Steam uitsluitend bestemd voor persoonlijk, niet-commercieel gebruik.\"\n\n\"U dient onmiddellijk te stoppen met het gebruik van uw Steam-accounts voor commerciële doeleinden. Indien u dit nalaat, binnen tien (10) dagen, Valve zal alle beschikbare rechtsmiddelen aanwenden, met inbegrip van, maar niet beperkt tot, het beëindigen van uw accounts.\"\n\nReconstructie van het dossier · raadpleeg het brondossier\nKarl Quackenbush\nHoofd Juridische Zaken, Valve Corp.\nIN DE MARGE / REDACTIONEEL\nTien dagen.En dan?\n\nDe deadline was duidelijk vastgesteld. De follow-up door de overheid zou dat ook moeten zijn.\n\nHet gepubliceerde standpunt van Valve over de ‘2016’ ↗\nEen opmerking over de deadline +\nSATIRE / GEEN CORRESPONDENTIE MET VALVE\n\nBeste deadline,\n\nJe kreeg tien dagen de tijd. Op de een of andere manier was de kalender het enige dat nog bleef werken.\n\nGelieve elk antwoord op te nemen in het openbare dossier.\n\nTijdlijnjuli 2016 – september 2026\nUiterste datum in de aankondiging:\n10 dagen\njuli 2016\nTijd verstreken sinds de kennisgeving:\n3,715 dagen\nVast aantal vanaf 20 juli 2016 tot aan de momentopname van het dossier op 21 september 2026; dit is geen actuele waarde\nGepubliceerd handhavingsverslag:\nGeen\nEr is geen overzicht per operator gevonden van beëindigingen of blokkades\n\n◀ Dag 0–10 — de deadline, op schaalDag 3715 — de momentopname ▶\n\n20 juli 2016Een tien dagen durende vraag is uitgevaardigdDag 0\n17 februari 2024De DSA-verplichtingen zijn van toepassingDag 2,768\n25 februari 2026Klacht van de procureur-generaal van New York aangekondigdDag 3,507\n21 september 2026Overzicht van het dossierDag 3715\n\nTien jaar later, CSGOFast — genoemd in persberichten over de kennisgevingen uit 2016 — is operationeel: csgofast.com leverde een Link Filter-blokkering op voor 2026-09-19 en 2026-09-21, terwijl de authenticatiehost ervan steam-login.authtofast.com (geregistreerd 2026-06-30) deed dat niet.\n\nVolledig gedateerd overzicht van de beveiligingswijzigingen van Valve: Tijdlijn beveiliging → · De „Washington Record” en de handhavingsnorm: hieronder\n\nWat uit het dossier blijkt: In de kennisgeving van 2016 werd een termijn van 10 dagen vastgesteld; Valve hanteerde al een domeinlijst (de Link Filter) en ontving de geautoriseerde hostnamen in zijn eigen OpenID-verzoeken; er is geen handhavingsrapport per exploitant gepubliceerd. In berichten uit de gemeenschap wordt melding gemaakt van een actie in 2018 tegen een marktplaats (SkinJar), maar die berichten zijn niet geverifieerd en worden hier niet als basis gebruikt.\nCSGOFAST / DE OPGESLAGEN AUTHENTIFICATIEROUTE\nVolg de opgegeven retourhost.\n\nDe links naar de opgeslagen routegegevens csgofast.com naar steam-login.authtofast.com. De afzonderlijke hostnaam wordt meegestuurd in het Steam OpenID-verzoek. Dit geeft onderzoekers een concreet adres om te vergelijken met de filter- en handhavingsgegevens van Valve.\n\nBekijk de CSGOFast-route en de bron ervan ↗ · Vergelijk opgeslagen Steam Link Filterresultaten ↗\n\nOPENBAAR REGISTER / WASHINGTON · 2016 → 2026\nTwee termijnen. Eén onduidelijke handhavingsnorm.\n20 juli\nValve geeft goksites 10 dagen de tijd\n\nIn de eis van de raadsman werd gewaarschuwd dat voortgezet commercieel gebruik van Steam-accounts tot beëindiging zou kunnen leiden.\n\n27 SEP\nWashington drukt op Valve\n\nDe Kansspelcommissie van de staat eiste bewijs van maatregelen om geldtransacties ten behoeve van kansspelen te stoppen en stelde 14 oktober vast als uiterste datum voor een reactie.\n\n17 OKT\nValve verwerpt de beschuldiging\n\nValve reageerde na de deadline, betwistte dat het gokken faciliteerde, verklaarde dat het de betreffende accounts had geblokkeerd en gaf aan dat het de handel en OpenID niet voor iedereen wilde uitschakelen. Ten minste één platform dat in persberichten over de kennisgevingen van juli werd genoemd (CSGOFast), was tien jaar later nog steeds actief. Beide feiten kunnen alleen kloppen als de exploitant de geblokkeerde accounts heeft vervangen; het bewijs dat dit zou aantonen, is niet gepubliceerd. De WSGC zou Valve moeten vragen om deze twee zaken met elkaar in overeenstemming te brengen.\n\n2026\nDe routes die in september 2026 zijn waargenomen\n\nHet routeregister vermeldt 44 platforms die zich authenticeren via authenticatiehosts in afzonderlijke domeinen, waaronder CSGOFast, waarbij gebruik wordt gemaakt van de OpenID- en handelsmechanismen Valve die in 2016 zijn beschreven. Het handhavingsrapport waaruit zou blijken welke exploitanten zijn afgesloten, is niet overgelegd.\n\nDE EIGEN INFORMATIEBRIEF VAN DE COMMISSIE · 30 JANUARI 2018\nAchttien maanden nadat Valve had geantwoord, noemde de toezichthouder het nog steeds een voornemen.\n\nTijdens de openbare hoorzitting over wetsvoorstel HB 2881 gaf de Commissie een toelichting aan haar eigen wetgevende instantie en beschreef zij de verklaring van juli 2016 in haar eigen woorden: Valve \"heeft aangekondigd dat het van plan is hard op te treden tegen het gebruik van zijn platform om gokken met skins te faciliteren.\" Op diezelfde pagina wordt beschreven welke gevolgen die aankondiging had voor de sectorprognose — \"daardoor,\" de prognose voor de markt voor online gokken in 2020 werd bijgesteld van $19.7 miljard naar $670 miljoen, een daling van ongeveer 97 procent, louter op basis van de aankondiging. De prognose is bijgesteld. Het handhavingsrapport per exploitant dat dit zou rechtvaardigen, is nog steeds niet gepubliceerd.\n\nDe marktcijfers zijn schattingen van Narus Advisors / Eilers & Krejcik Gaming die in de briefing van de Commissie zijn overgenomen, en geen bevindingen van de Commissie; volgens hetzelfde document bedroeg de omzet uit ‘skin wagering’ in 2016 ongeveer $5 miljard, waarvan ruwweg $3 miljard op casino-achtige websites. Opgehaald op 2026-09-22, SHA-256 c507c9025f93da0aadaf395c4d8882f25973211c318ee8e9b6f18a5b3755e050.\n\nHet officiële standpunt van Valve uit 2016 en de infrastructuur die vandaag de dag waarneembaar is, kunnen naast elkaar worden gelegd. De vraag is of de handhaving ook de rekeningen en routes heeft bereikt die door verboden exploitanten werden gebruikt. Een kennisgeving met een termijn van tien dagen vormt geen bewijs dat de kennisgeving daadwerkelijk is gedaan aan alle daarin genoemde exploitanten. De OPSkins-maatregel uit 2018 is de enige gedocumenteerde ingreep tegen een bij naam genoemde exploitant; gezien het feit dat er 189 platforms zijn gecontroleerd en er geen gegevens per exploitant zijn gepubliceerd, wijst één gedocumenteerde maatregel niet op een patroon van handhaving.\n\nKennisgeving van de Kansspelcommissie van Washington uit 2016 ↗ gearchiveerd 2026-05-20 ↗ · Het antwoord van Valve van 17 oktober 2016 (kopie van het document) ↗ · WSGC-briefing aan de wetgevende macht, 30 januari 2018 (lokale kopie, 4 blz.) ↗ · hetzelfde bestand op wsgc.wa.gov ↗ · opvraagrecord en hash ↗ · Valve's OPSkins-actie uit 2018 ↗ gearchiveerd 2026-03-07 ↗ · Huidige routecontrole ↗\n\nForensisch longitudinaal onderzoek · Doelwitten van het dwangbevel uit 2016\nHet decennium van de 10-daagse kennisgeving: forensische overlevingsaudit van de 23 genoemde locaties\n\nOp 19 en 20 juli 2016 heeft Valve juridisch adviseur Karl Quackenbush formele sommaties tot staking en onthouding verstuurd aan 23 gokplatforms voor skins, waarin hij hen opdroeg het commerciële gebruik van Steam-accounts binnen 10 dagen onder dreiging van accountbeëindiging en juridische stappen. Ruim 3,700 dagen later brengt een empirisch onderzoek het werkelijke handhavingspatroon aan het licht: talrijke exploitanten hebben hun activiteiten nooit stopgezet, anderen bleven tot wel zes jaar na de deadline actief, en het miljarden-dollar-ecosysteem bleef gebruikmaken van de OpenID-architectuur van Valve.\n\n5+ LIVE\nZal in 2026 zeker operationeel zijn (CSGOBig, CSGO500, CSGOFast, enz.)\n6 JAAR\nLangste periode na de aankondiging tot aan de sluiting (CSGOatse actief tot en met 2022)\n$5.01B\nInzetvolume op huidweddenschappen in 2016 (Narus / Eilers & Krejcik)\n200+\nActieve goksites die op het hoogtepunt van de markt actief zijn\nThe Surviving Titans · Financieel en bezoekersplan 2024–2026\nVan 10-daagse waarschuwingen tot offshore-conglomeraten: de omzet van meerdere miljarden dollars\n\nIn plaats van het gokken met skin te verbieden, hebben de mededelingen van Valve uit 2016 juist een industriële evolutie in gang gezet. De overgebleven exploitanten herstructureerden zich tot offshore-ondernemingen (Curaçao, Belize, Cyprus), waren pioniers op het gebied van Peer-to-Peer (P2P)-handel om botverboden te omzeilen, en verwerken nu meer dan 10 miljoen websitebezoeken per maand en miljarden dollars aan jaarlijkse inzet terwijl de authenticatie via Steam wordt voortgezet:\n\nPlatform / Domein\tMededeling juli 2016\tHandhavingsresultaat en overlevingsstatus\tGeregistreerde verificatie / Primaire links\nCSGOBig\ncsgobig.com\tKennisgeving 10 dagen van tevoren (juli 2016)\tLEEFT NOG STEEDS IN 2026\nTijdelijk gepauzeerd, opnieuw gelanceerd; authenticatie via letmeinbig.com en csgobiglogin.com\tX: @csgobig ↗ · FB: csgobigofficial ↗\nCSGO500\ncsgo500.com / 500.casino\tKennisgeving 10 dagen van tevoren (juli 2016)\tLEEFT NOG STEEDS IN 2026\nOmgedoopt tot 500 Casino (vergunning Curaçao nr. 8048/JAZ2014-037), met een maandelijkse omzet van meerdere miljoenen\tLive Platform (500.casino) ↗\nCSGOFast\ncsgofast.com\tKennisgeving van 10 dagen (juli 2016)\tLEEFT NOG STEEDS IN 2026\nRoulette, Crash en Jackpot worden actief aangeboden via steam-login.authtofast.com\tDossier-authenticiteitscontrole ↗\nCSGOLounge / Dota2Lounge\ncsgolounge.com / dota2lounge.com\tKennisgeving van 10 dagen (juli 2016)\tLEEFT NOG STEEDS IN 2026\nGericht op weddenschappen met esports-munten en crypto-weddenschappen; de bedrijfsvoering is ononderbroken voortgezet\tLive-platform ↗\nCSGOCasino\ncsgocasino.net / csgocasino.gg\tKennisgeving 10 dagen van tevoren (juli 2016)\tLIVE VIA SUCCESSOR (2026)\nHet domein is omgeleid; het actieve opvolgende portaal is te vinden op csgocasino.gg\tOpvolgend domein ↗\nCSGOatse\ncsgoatse.com\tKennisgeving 10 dagen van tevoren (juli 2016)\t6 JAAR BESTAAN (ACTIEF TOT 2022)\nDe gokactiviteiten werden nog zes jaar lang volledig voortgezet, ondanks het ultimatum van 10 dagen van Valve\tX: @CSGOatsecom (Actief tot 2022) ↗\nCSGOSweep\ncsgosweep.com\tKennisgeving 10 dagen van tevoren (juli 2016)\tBESTAAND TOT DECEMBER 2017\nNa het verstrijken van de deadline nog 17 maanden openbaar in gebruik geweest\tX: Status CSGOSweep december 2017 ↗\nCSGOWild\ncsgowild.com\tKennisgeving 10 dagen van tevoren (juli 2016)\tBESTAAND TOT DECEMBER 2017\nGepromoot door grote influencers; bleef 1,5 jaar na de C&D-brief actief, voordat de overstap naar crypto plaatsvond\tX: @Wild (actief dec. 2017) ↗\nCSGOPot\ncsgopot.com\tKennisgeving 10 dagen van tevoren (juli 2016)\tHeeft het volgehouden tot september 2017\nEr werd 14 maanden na de kennisgeving nog steeds gewed op jackpots met hoge inzetten\tX: @csgopot (actief in september 2017) ↗\nCSGODiamonds\ncsgodiamonds.com\tKennisgeving 10 dagen van tevoren (juli 2016)\tHeeft het tot halverwege 2017 volgehouden\nHet jaar 2017 liep gewoon door, ondanks het toegegeven manipuleren van resultaten ten gunste van gesponsorde streamers\tX: @csgodiamondscom (2017) ↗\nCSGOLotto\ncsgolotto.com\tKennisgeving 10 dagen van tevoren (juli 2016)\tGESLOTEN IN JULI 2016\nGesloten na een publieke schandaal; het doelwit van een schikkingsovereenkomst van de federale FTC\tInschikkingsovereenkomst van de FTC (dossiernummer C-4632) ↗\nCSGODouble\ncsgodouble.com\tKennisgeving 10 dagen van tevoren (juli 2016)\tGESLOTEN IN JULI 2016\nOnmiddellijk na publicatie van de sommatie vrijwillig de activiteiten stopzetten\tX: @CSGODouble (Gesloten in juli 2016) ↗\nCSGOMassive\ncsgomassive.com\tKennisgeving 10 dagen van tevoren (juli 2016)\tGESLOTEN 2016\nEind 2016 zijn de openbare activiteiten stopgezet\tX: @csgo_massive ↗\nCSGOStrong\ncsgostrong.com\tKennisgeving 10 dagen van tevoren (juli 2016)\tGESLOTEN 2016\nHeeft in 2016 de openbare activiteiten stopgezet\tFB: csgostrongfree ↗\nSkins2\nskins2.com\tKennisgeving 10 dagen van tevoren (juli 2016)\tGESLOTEN 2016\nHeeft in 2016 de openbare activiteiten gestaakt\tFB: CSNCOM ↗\n\nPlatform\tMaandelijks verkeer (bezoeken)\tGeschatte omzet / volume\tRechtspersoon en rechtsgebied\tBelangrijkste regelgevende maatregelen en model\nCSGOEmpire\ncsgoempire.com\t2,3 miljoen — 9,0 miljoen / maand\nGemiddelde duur: 6+ min; 80% direct\t$1.5B — $2.5B Jaarlijkse omzet\n>1,000,000 P2P-huidtransacties per maand; $6.4 miljoen actieve liquide orders\tMoonrail Limited B.V. (Curaçao nr. 148182)\nBetalingen: JHOLT LTD (Cyprus); Oprichter: „Monarch“ (Ossi Ketola)\tPionier op het gebied van commissievrije P2P-handel in artikelen; vergunning van Curaçao OGL/2024/1183/0869\nCSGORoll\ncsgoroll.com\t2,74 miljoen — 3,5 miljoen per maand\nGemiddelde duur: 9 min. 23 sec.; 16% bouncepercentage\t$1.0B — $2.0B Jaarlijks verwerkingsvolume\nGeschatte jaarlijkse bedrijfsopbrengsten uit het huisvoordeel: $100M–$200M\tFeral Holdings Limited\nMet hoofdkantoor in Belize City, Belize (registratienummer 171519)\tVerboden door de Australische ACMA (mei 2023); sponsorde het tier-1-team G2 Esports met minderjarige spelers\n500 Casino (CSGO500)\n500.casino / csgo500.com\t220.000 — 425.000 per maand\n~105.000 unieke bezoekers per maand\t$100k / week ($5.2M/jaar) in Royales\nInzetvereiste voor high rollers: $400 inzet per $1 rakeback\tPerfect Storm B.V. (Curaçao nr. 150536)\nVergunning van de Kansspelcommissie van Curaçao OGL/2024/1354/0882\tVerboden door de Zweedse Spelinspektionen (november 2023) wegens het zonder vergunning richten van activiteiten op Zweedse spelers\nCSGOBig\ncsgobig.com\t~169,600 / maand\nGemiddelde duur 19m 12s; Amerikaanse voorverkiezingen\tJaarlijks omzetvolume van meerdere miljoenen\nMystery boxes, roulette en case battles\tWerkt via aanvullende proxy-routing\nletmeinbig.com (geregistreerd in 2023) & csgobiglogin.com\tTarget van juli 2016 C&D; opnieuw gelanceerd met proxy-authenticatiearchitectuur\nCSGOFast\ncsgofast.com\t~150.000 — 250.000 / maand\nWereldwijd meertalig publiek\tJaaromzet van meerdere miljoenen\nRoulette- en crash-spellen met hoge snelheid\tOffshore-bedrijfsentiteiten\nRoutes Steam authenticatie via steam-login.authtofast.com\tDoelwit van de C&D van juli 2016; activiteiten nooit stopgezet; actief in 2026\nCSGOPolygon\ncsgopolygon.com / plg.bet\t~300.000 — 500.000 per maand\nDe dominantie van de GOS-landen en Oost-Europa\tJaarlijks omzetvolume van meerdere miljoenen\nCrypto- en skin-roulette, weddenschappen op wedstrijden\tDoelstelling voor de tweede golf (oktober 2016)\nDe focus is verlegd naar cryptovaluta met het spiegeldomein plg.bet\tHeeft een heel decennium standgehouden; zet de afbouw van de skin voort via API’s van derden\nDe tweede golf: waarom de sommatiebrief van Valve in totaal op meer dan 43 websites was gericht\n\nOp 17 oktober 2016 heeft de juridisch adviseur van Valve formeel aan de Kansspelcommissie van de staat Washington meegedeeld dat Valve, na de eerste 23 kennisgevingen op 19 juli, sommatiebrieven had gestuurd aan meer dan 20 extra goksites met skins (waardoor het officiële totaal boven de 43 komt). Deze tweede ronde was noodzakelijk omdat op de oorspronkelijke lijst op onverklaarbare wijze de grootste en beruchtste gokcentra ter wereld ontbraken:\n\nCSGOJackpot.com: De historische grondlegger van de ‘skin jackpots’, die een omzet van honderden miljoenen verwerkte voordat het bedrijf de deuren moest sluiten onder dreiging van een federale aanklacht.\nCSGOShuffle.com: De website die centraal stond in het streaming-schandaal van juli 2016, waarbij Twitch-streamer PhantomL0rd in het geheim 33% van het bedrijf in bezit had en ontmaskerd werd omdat hij met bedrijfsgeld de kansen had gemanipuleerd.\nHet macro-ecosysteem (meer dan 200 exploitanten): Volgens sectoronderzoek door Narus Advisors en Eilers & Krejcik Gaming waren er in 2016 meer dan 200 verschillende skin-goksites actief, die een inzetvolume van $5.01 miljard genereerden bij 3,03 miljoen actieve spelers. De 43 brieven van Valve hadden betrekking op minder dan 20% van de actieve markt.\nOfficiële onderzoeken door de overheid en toezichthouders naar Steam Skin Gambling\n\nHet fenomeen van het gokken via ‘skin-gokken’ is gedocumenteerd in diverse officiële wettelijke onderzoeken, handhavingsmaatregelen en standpuntnota’s van de overheid:\n\n1. Kansspelcommissie van de staat Washington (WSGC) (2016–2018)\n\nOp 5 oktober 2016 is een formele sommatie tot staking en onthouding uitgevaardigd; op 30 januari 2018 is een wetgevingsnota gepubliceerd waarin wordt vastgesteld dat skins als contante equivalenten worden beschouwd en waarin het inzetvolume van skins ter waarde van $5.0B wordt vermeld.\n\nWSGC-wetgevingsrapport (PDF) (lokale kopie) ↗\n2. Amerikaanse Federal Trade Commission (FTC) (sept. 2017, dossiernummer C-4632)\n\nEerste handhavingsmaatregel van de federale overheid in verband met online gokken, gericht tegen de eigenaren van CSGOLotto, Trevor Martin en Thomas Cassell, wegens misleidende praktijken en verzwegen zeggenschap over het platform.\n\nBesluit en schikkingsovereenkomst van de FTC ↗\n3. Standpuntnota van de Britse Kansspelcommissie (UKGC) en onderzoeken naar jongeren\n\nIn-game skins werden formeel aangemerkt als „geld of iets van gelijke waarde” in het kader van de Kansspelwet van 2005. Uit latere onderzoeken bleek dat meer dan 11% van de kinderen in de leeftijd van 11 tot 16 jaar skins in videogames had ingezet.\n\nUKGC-onderzoeksarchief ↗\n4. Onderzoek van de Australische Senaat naar milieu en communicatie (2018)\n\nVerslag van het federale parlement over \"Microtransacties in games voor items die op kansspel berusten\", waarbij de lootbox-mechanismen van Valve, uitbetalingen op de secundaire markt en het omzeilen van regelgeving worden geëvalueerd.\n\nOnderzoek van het Australische parlement ↗\nDe openstaande vordering\n\nMaak het handhavingsverslag openbaar: welke gokaccounts en bots zijn geblokkeerd, welke return-hosts zijn aan banden gelegd en welke commerciële diensten toestemming hebben gekregen. Een openbaar verbod en een waarschuwing op de startpagina betekenen nog niet dat de onderliggende activiteiten zijn stopgezet.\n\nDeel B — Voorschriften en handhavingsgeschiedenis · Artikel 12\nDe hostnaam staat al in het verzoek.\nContext en bronbeperkingen\n\nValve beschikt al over een domeinlijst (de Link Filter) en ontvangt bij elk OpenID-verzoek de authenticatiehostnaam. De onderstaande pseudocode laat zien hoe deze twee logisch met elkaar kunnen worden gekoppeld. Er zijn geen openbare aanwijzingen dat Valve dit doet.\n\nValve hanteert al een blokkeerlijst voor domeinen. Valve ontvangt al bij elk OpenID-verzoek de host van de inlogger. Er hoeft niets gebouwd te worden — de twee moeten met elkaar worden verbonden. Dat is een hostnaamopzoeking aan de hand van een lijst die Valve zelf bijhoudt. De onderstaande pseudocode dient ter illustratie en is geen implementatie van Valve.\n\nforensic_autoban.py\n# ILLUSTRATIEVE PSEUDOCODE — Valve.block_domain() en flag_session_as_mitm() zijn geen echte API-aanroepen. Dit illustreert de logische structuur van een beveiligingsmaatregel die Valve zou kunnen implementeren tegen proxy-authenticatiedomeinen, niet de daadwerkelijke interne werking van Valve.\n# Illustratie: de logische opbouw van een controle van het binnenkomende OpenID-verzoek\ndef audit_openid_request(verzoek):\nblocked_origins = database.get_blacklisted_platforms()\nproxy_domain = request.params.krijgen('openid.realm')\ntarget_redirect = request.params.krijgen('openid.return_to')\n\n# Logica: Als de proxy doorverwijst naar een geblokkeerde website, blokkeer de proxy dan.\nvoor website in blocked_origins:\nals website in target_redirect:\nValve.block_domain(proxy_domain)\nValve.flag_session_as_mitm(request.session)\n# Resultaat: het inlogverzoek voor die host wordt geweigerd\n\nOpmerking:\nWanneer een hoofddomein al in het linkfilter staat (bijv. howl.gg, geblokkeerd 2026-09-18/19/21) en de authenticatiehost (howl.uno) voorkomt in het OpenID-verzoek vanuit de inlogknop van die site, is de koppeling waarneembaar voor Valve aan de hand van de eigen verzoekgegevens. De controle kan worden geautomatiseerd; of deze daadwerkelijk wordt uitgevoerd, is niet het geval.\nGedocumenteerde en gemelde precedenten\n\nValve heeft volgens de gegevens minstens één keer ingegrepen tegen een externe exploitant: in 2018 heeft het de toegang van OPSkins tot het ExpressTrade-systeem ingetrokken (De aankondiging van Valve ↗ gearchiveerd 2026-03-07 ↗). In communityverslagen uit 2018 wordt ook melding gemaakt van een marktplaats (SkinJar) die de toegang verloor; deze verslagen zijn niet geverifieerd en het mechanisme wordt afgeleid uit het resultaat, niet uit een openbaar gemaakt proces.\n\nWat dit precedent vaststelt:\n\nValve kan de toegang van een externe exploitant blokkeren wanneer het dat wil. CSGOFast, dat in persberichten over de kennisgevingen van juli 2016 werd genoemd, was actief op 2026-09-21 met een geauthenticeerde host geregistreerd op 2026-06-30, die geen Link Filter-blokkering opleverde. Waarom één exploitant werd afgesloten en andere niet, wordt door geen enkel gepubliceerd criterium verklaard.\n\nWat een registratiedatum wel en niet aangeeft\n\nDe registratiedatum van een geauthenticeerde host vormt een ondergrens voor het moment waarop de host voor het eerst in een OpenID-verzoek zou kunnen zijn verschenen; dit betekent niet dat er sprake is van ononderbroken gebruik. sc-auth.net, werd bijvoorbeeld geregistreerd als 2019-04-02 (RDAP) en werd in september 2026 waargenomen in de Steam-inlogprocedure van Skin.Club; wat er tussen die twee data is gebeurd, is niet openbaar bekend.\n\nVergelijkende controle: API-nalevingsnormen\nHandhavingsaspect\tRegels voor de GitHub-API\tSteam Web-API (Valve)\n1. Neutraliteit ten aanzien van naleving\tGepubliceerde, uniforme regels. Gedocumenteerde limieten (bijv. 5,000 oproepen/uur voor geauthenticeerde gebruikers, 15,000/uur voor GitHub Enterprise Cloud-organisaties) en gepubliceerde beleidsregels inzake aanvaardbaar gebruik zijn van toepassing op elk account.\tEr zijn geen criteria gepubliceerd. Individuele accounts worden beëindigd op grond van de bepalingen inzake automatisering en commercieel gebruik (gearchiveerde klachten), terwijl er geen handhavingsgegevens per exploitant voor commerciële platforms zijn gepubliceerd.\n2. Misbruik van OpenID / authenticatieproxy\tVolgens het gepubliceerde beleid van GitHub kunnen OAuth-apps en -tokens bij misbruik worden opgeschort of ingetrokken, en in de documentatie wordt de automatische intrekking van blootgestelde tokens beschreven (samenvatting van de GitHub-documentatie door de auteurs).\tAuthenticatiehosts met een afzonderlijk domein die werden waargenomen in Steam OpenID-stromen (bijv. rbsnin.com, howl.uno, sc-auth.net) leverden geen blokkering door de Link Filter op 2026-09-21 op, terwijl hun hoofddomeinen dat wel deden.\n3. Geld verdienen aan misbruik\tGitHub brengt geen transactiekosten in rekening voor items die via automatisering door derden worden verplaatst; het verdienmodel is gebaseerd op abonnementen en aanbiedingen op de marktplaats.\tValve verkoopt de case-sleutels waarmee de items kunnen worden verkregen, en de Community Market brengt een totale vergoeding van ongeveer 15% in rekening voor verkopen die binnen de Market worden afgerond. Er wordt hier geen schatting gemaakt van de inkomsten die aan platforms van derden kunnen worden toegeschreven.\n4. Levensduur van ontwijkingslussen\tOpgeschorte OAuth-client-ID’s werken bij opschorting niet meer op het hele platform; in de documentatie wordt geen termijn voor het nemen van maatregelen vermeld en hier wordt ook geen termijn aangenomen.\tBij de controles van 2026-09-19 en 2026-09-21 werd voor authenticatiehosts met afzonderlijke domeinen en registratiedata tussen 2011 en september 2026 geen blokkering door het Link Filter vastgesteld. De registratiedatum vormt een ondergrens voor mogelijk gebruik, maar is geen bewijs van ononderbroken gebruik.\nBronnen: GitHub-column — Door GitHub gepubliceerde documentatie over API-limieten en platformbeleid (samenvatting door de auteurs, geen letterlijke citaten) · Steam-column — Linkfiltercontroles van 2026-09-19 en 2026-09-21 (linkfilter-recheck-2026-09-21.json), RDAP-register (domain-registration.json) en de gearchiveerde supportklachten (bewijsarchief).\nDeel B — Regels en handhavingsgeschiedenis · Artikel 13\nHet prijsverschil ten opzichte van 0\n\nHet artikel bevindt zich in een Steam-voorraad; de verkoop vindt elders plaats. Een fabrieksnieuwe AWP Dragon Lore had 62 actuele aanbiedingen op CSFloat; de laagste vraagprijs $10,623.95. Op de eigen markt van Steam kan geen vraagprijs worden weergegeven die hoger is dan ongeveer $1,800. Om tegen de waargenomen hogere prijs te verkopen, heeft een eigenaar een koper of marktplaats buiten Steam nodig. Het artikel en de overdracht ervan zijn nog steeds afhankelijk van Steam.\n\nWhat this means — the Community Market listing ceiling\n\nSteam’s own market refuses a listing above roughly $1,800. A seller may ask less, never more. Items whose market price sits above that line therefore cannot be sold at that price on Steam at all — which is the mechanism that moves those sales to third-party venues while the item itself never leaves Valve’s inventory system.\n\nSection 13 — the off-Steam price gap →\n\nContext en bronbeperkingen\n\nIn dit hoofdstuk komen drie verschillende tellingen voor, die niet onderling uitwisselbaar zijn. 245 is het aantal CS2-categorieën waarvan het goedkoopste actieve aanbod op 20 september 2026 uitsluitend op CSFloat hoger was dan $1,800. 241 dat is dezelfde verzameling minus de vier categorieën die zijn vastgezet aan het $100,000-plafond van CSFloat, het paneel waarop de $13.63M-ondergrens wordt berekend. 248 is een ander overzicht: categorieën waarvan de prijs op 23 september 2026 door twee of meer van de vijf marktplaatsen boven het maximum lag. De marktplaatsen overlappen elkaar, dus de aantallen van verschillende platforms mogen nooit bij elkaar worden opgeteld. Elk cijfer hier is een vraagprijs, geen afgeronde verkoop, en niets daarvan is omzet, omzetcijfer of winst — noch voor Valve, noch voor wie dan ook. De door PriceEmpire vermelde waarden zijn afgeronde schattingen die door die site zijn gepubliceerd, en de Steam-kaart omvat items uit andere Steam-spellen, waardoor de reikwijdte van de vergelijking niet identiek is.\n\nEén artikel. Twee prijssystemen.VOLG HET VERSLAG\nStap 3 / 3\n\nBij dat verzoek heeft de verkoper een alternatieve handelsplaats of koper nodig. Het artikel is nog steeds afhankelijk van de voorraad en het overdrachtssysteem van Steam.\n\nSTEAMOver $1,800Gepubliceerde maximumbedrag voor aanbiedingen op de Community Market\nOPGESLAGEN CATALOGUS$10,623.95Fabrieksnieuw AWP Dragon Lore – prijs op aanvraag\nDE AFHANKELIJKHEIDNog steeds een Steam-artikelDe voorraad en de overdracht staan nog steeds op Steam\n01 / ARTIKELValve speloverzichtCS2- of Dota 2-item in Steam\n02 / PLAFONDOver $1,800 op SteamMaximale prijs voor één marktadvertentie\n03 / BUITEN VRAAG$10,623.95 voor Dragon LoreGoedkoopste CSFloat-aanbieding in de momentopname van die datum\n04 / LEVERINGSteam blijft in de ketenEigendom en overdracht van voorwerpen zijn afhankelijk van het systeem\nMARKTSTRUCTUUR · MOMENTOPNAME VAN 20 SEPTEMBER 2026\nHet prijsverschil is meetbaar.\n\nWe hebben de categorieën van artikelnamen geteld waarvan het goedkoopste actieve aanbod strikt boven $ lag1,800. CSFloat en Skinport zijn afzonderlijke momentopnames met overlappende CS2-voorraden; hun aantallen kunnen niet bij elkaar worden opgeteld. De externe aanbiedingen laten zien waar hogere vraagprijzen worden vermeld, terwijl Steam nog steeds het eigendom en de overdracht van artikelen regelt.\n\n245CS2-CATEGORIEËN · CSFLOAT\n166CS2-CATEGORIEËN · SKINPORT\n3DOTA-2-CATEGORIEËN · SKINPORT\n$10,623.95DRAGON LORE FLOOR ASK\n\nDragon Lore: 62 biedt in de categorie ‘Factory New’ CSFloat aan; de weergegeven prijs is een vraagprijs, geen bevestigde verkoopprijs. Steam staat toe dat het artikel voor een lagere prijs wordt aangeboden, maar het is niet toegestaan de waargenomen hogere vraagprijs te vermelden. In de verklaring op Valve’s 2016 wordt bevestigd dat het bedrijf op de hoogte is van gokexploitanten die gebruikmaken van OpenID en de handelsinfrastructuur van Steam. Of een bepaalde marktplaats van een derde partij de regels van Valve overtreedt, moet afzonderlijk worden vastgesteld.\n\nBekijk het volledige register →CSFloat JSON ↗Skinport JSON ↗Verklaring van Valve over ‘2016’ ↗\nDIRECTE CSFLOAT-API / SNAPSHOT MET DATUM$13.63M\n\nMinimale totale vraagprijs in 241 productcategorieën en 3,395 actieve aanbiedingen. Berekend als de goedkoopste vraagprijs van elke categorie vermenigvuldigd met het aantal aanbiedingen. Vier categorieën die vastzitten aan het $100,000-plafond van CSFloat zijn uitgesloten van dit conservatieve panel.\n\nWat het bedrag aangeeft\n\nDeze aanbiedingen vertegenwoordigen ten minste $13,631,888.25 in de geadverteerde vraagprijzen voor deze beperkte CSFloat-subset. Als we de vier categorieën met de hoogste prijs meerekenen, komt men uit op $14,231,888.25. Dit is een minimum bij actieve biedingen, niet de gerealiseerde omzet, de kasomzet, de winst of de gehele CS2-markt.\n\nOpnieuw berekenen op basis van de CSFloat-momentopname met 245 rijen ↗\nPRICEEMPIRE / GELIJSTE WAARDESteam: nr. 15 van 39\nVeel locaties vermelden een waarde in dollars die hoger is dan Steam.\nUUSkins\n$133.8M\nYouPin898\n$127.5M\nBuff.163\n$104M\nMoon.Market\n$100.3M\nWhite.Market\n$89.6M\nBuff.Market\n$86.7M\nSteam\n$31M\n\nDe zes grootste weergegeven waarden en Steam. PriceEmpire rondt deze getallen af; Steam geeft aan $31M. Veertien beursgenoteerde locaties staan boven deze locatie op basis van de weergegeven dollarwaarden.\n\nPRICEEMPIRE / AANTAL AANBIEDINGENSteam: nr. 1 van 39\nSteam staat nog steeds aan kop wat betreft het aantal aanbiedingen.\nSteam\n32,2 miljoen\nYouPin898\n5,9 miljoen\nC5Game\n4,6 miljoen\nHaloSkins\n4,4 miljoen\nSkinport\n3,8 miljoen\n\nSteam toont 32,2 miljoen aanbiedingen. Het aantal aanbiedingen en de totale vraagprijs geven antwoord op verschillende vragen; veel goedkope aanbiedingen kunnen het totaal aantal aanbiedingen sterk beïnvloeden.\n\nBron: Openbare vergelijking van PriceEmpire ↗ gearchiveerd 2026-09-21 ↗, vastgelegd op 2026-09-20 om 19:03 UTC; gedateerde extractie van 39 rijen ↗. De cijfers zijn afgeronde schattingen en de voorraad kan zich over meerdere locaties uitstrekken. Op de kaart van Steam staan ook voorwerpen uit andere Steam-spellen vermeld, dus de reikwijdte is niet identiek. De vermelde waarde geeft de vraagprijs weer, niet de verkoopopbrengst of omzet.\n42\nEEN ANDERE BRON / STEAMANALYST\nHet commerciële ecosysteem ligt voor het grijpen.\n\nDe marktplaatsgids van SteamAnalyst gearchiveerd 2026-07-19 ↗ vermeldt 42 externe CS2-marktplaatsen naast Steam, met recente prijsgegevens voor 32 van de 43 vermeldingen. PriceEmpire vermeldt 39 marktplaatsen op basis van zijn eigen selectiecriteria. Genoemde bedrijven, openbare aanbiedingen, zichtbare prijzen: deze economie is voor iedereen inzichtelijk.\n\nHET PLAFOND IS HET MECHANISME: DE UITVERKOOP VERLIEST AAN KRAFT, HET ARTIKEL NIET.\n\nVijf marktplaatsen, vastgelegd in één gelicentieerde momentopname, 248 CS2-productcategorieën hebben elk afzonderlijk een prijs die twee of meer van de door Steam vastgestelde maximumprijs van ongeveer $1,800 overschrijdt — en geen enkele daarvan is te vinden op Steam. In hetzelfde momentopname werd de gehele catalogus op prijs ingedeeld: de markt van Valve bevat 95.3% van de artikelcategorieën onder zijn limiet en 1.9% van de categorieën daarboven. De inkrimping is geen gevolg van een dalende vraag; ze valt precies samen met de gepubliceerde regel. Om tegen die prijzen te verkopen is een externe koper of marktplaats nodig, terwijl Steam nog steeds de controle heeft over de voorraad en de overdracht — de transactie verlaat de kassa van Valve en de levering blijft op de infrastructuur van Valve.\n\nSteam Veelgestelde vragen over de markt ↗gearchiveerd 2026-09-21 ↗Steam Abonnementsovereenkomst ↗gearchiveerd 2026-09-21 ↗Atlas-dataset met vijf marktplaatsen ↗Herkomstverklaring ↗Eerdere momentopname van CSFloat ↗Skinport-overzicht ↗PriceEmpire ↗gearchiveerd 2026-09-21 ↗SteamAnalyst ↗gearchiveerd 2026-07-19 ↗Prijsverschillenregister ↗Prijsladderatlas ↗\n\nDeel C — Wettelijke kaders\nDeel C — Wettelijke kaders · Artikel 14 · Toegang van personeel\nWie kan de beveiligingsmaatregelen resetten?\nContext en bronbeperkingen\n\nDe beveiliging van een account hangt ook af van de personen die een account kunnen herstellen, privégegevens kunnen inzien of de beveiligingsmaatregelen ervan kunnen resetten. Het onderzoek moet deze bevoegdheden net zo nauwlettend volgen als het misbruik van de API.\n\nBij het herstellen van een account krijgt een medewerker van de klantenservice de bevoegdheid om een account aan de eigenaar te onttrekken. Valve heeft tweemaal — in februari 2023 en november 2025 — schriftelijk bevestigd dat deze bevoegdheid is gebruikt om accounts aan de verkeerde personen over te dragen. Met een tussenpoos van drieëndertig maanden, via hetzelfde kanaal. Hieronder: wat die toegang waard is, zes gevallen met bronvermelding, en het logboek Valve bevat gegevens over elk van deze gevallen en is aan niemand vrijgegeven.\n\nGearchiveerde getuigenis / 9 mei 2025\nEen herstelticket waardoor de beveiliging van het account werd uitgeschakeld, en een gemeld verlies van $10,000\n\nEen gebruiker in het verzamelde supportarchief meldt dat Steam Support het wachtwoord heeft gereset en de accountbeveiliging heeft uitgeschakeld nadat iemand anders een herstelticket had ingediend. De auteur zegt dat het account al jaren inactief was, items bevatte uit 2016–2017 en Steam Guard had, een gekoppeld telefoonnummer en opgeslagen herstelcodes.\n\n\"Steam De klantenservice heeft toch iemand anders toegang tot mijn account gegeven.\"\n\nBewering in de eerste persoon, vastgelegd in steam_support_tickets_MEGA.json, nummer 110. Lees het volledige bericht ↗\n\nDit is niet het ongeluk van één gebruiker. Dezelfde procedure — een hulpverzoek waarbij een account wordt overgedragen aan degene die de oudere gegevens aanlevert — is de vastgelegde werkwijze voor alle gevallen in het onderstaande overzicht, en Valve heeft dat tweemaal schriftelijk bevestigd.\n\nDe eigenaar kan dat debat niet winnen. Bij het herstelproces wordt gevraagd om de eerste cd-sleutel, het eerste e-mailadres, de eerste kaart en het eerste telefoonnummer. Die gegevens staan in de database van Valve en worden door de helpdesk opgehaald — naar verluidt gaan ze vijftien jaar terug. Iemand die een kopie van je dossier heeft, kan altijd meer van je geschiedenis boven water halen dan jijzelf. Doelwitten werden zorgvuldig geselecteerd: jarenlang inactief, van grote waarde en vaak tweedehands gekocht, zodat de houder de oorspronkelijke sleutel nooit heeft gekend. Daarna werden de accounts volledig verwijderd, waardoor het spoor van de itemgeschiedenis werd verbroken dat de gemeenschap gebruikt om een skin te traceren — een verwijdering die een gewone gebruiker niet kan uitvoeren zonder de standaard wachttijd.\n\nMinimale bevoegdheden / OWASP A01\n\nHerstelbevoegdheden moeten worden beperkt tot de betreffende taak, onafhankelijk worden gecontroleerd en worden geregistreerd. Controleer wie inloggegevens kan resetten, Steam Guard kan verwijderen, factureringsgegevens kan inzien of accountgegevens kan exporteren. OWASP-richtlijnen voor toegangscontrole ↗ gearchiveerd 2026-09-20 ↗\n\nBrede toegang tot ondersteuningRisico op het gebied van toegangsrechten\nMeer dan alleen de voorraad.\n\nAls er misbruik wordt gemaakt van brede toegangsrechten, kan privételemetrie een instrument worden voor profilering, gerichte phishing en surveillance. Tot de potentiële slachtoffers behoren gewone gebruikers, militairen, publieke figuren en hun families. Dit is een dreigingsmodel; voor de exacte machtigingen zijn toegangsbeheersgegevens nodig.\n\n01 IP-geschiedenis en locatie\nIP-logbestanden kunnen de netwerkgeschiedenis en de geschatte locatie onthullen. Op zichzelf geven ze echter geen nauwkeurig beeld van fysieke verplaatsingen.\n02 Apparaat-fingerprinting\nApparaat-ID’s kunnen, indien deze worden verzameld en toegankelijk zijn, sessies en accounts aan elkaar koppelen.\n03 Activiteitstelemetrie\nTijdstempels van inlogmomenten en sessiegegevens kunnen patronen aan het licht brengen, waaronder activiteiten die niet zichtbaar zijn op een openbaar profiel.\n04 Communicatie en contacten\nToegang tot opgeslagen berichten of contactgegevens zou de mogelijkheden voor profilering en social engineering vergroten.\n05 Ontmaskering van identiteit\nAan de hand van originele e-mail-, telefoon- en betalingsgegevens kan een pseudoniem account aan een persoon worden gekoppeld.\n06 Doorverkoop van gegevens en verantwoordingsplicht\nGeëxporteerde doellijsten kunnen worden gebruikt voor gerichte oplichting. Stel vast wie de dader is, waarvandaan toegang is verkregen, wie de ontvangers zijn en welke overboekingen er hebben plaatsgevonden; de locatie op zich is geen bewijs van toegang of juridische immuniteit.\n\nValve beschrijft IP-logging, apparaatgegevens, betalingsgegevens en externe ondersteuningsaanbieders in zijn Privacybeleid §§ 3, 5.2 gearchiveerd 2026-09-21 ↗. Het beleid staat toegang door derden toe — het audittraject waaruit zou blijken welke aannemer toegang heeft gehad tot welke categorie, wanneer en op grond van welke machtiging, is echter niet openbaar gemaakt.\n\nParagraaf 14.1 · het register · juni 2022 → november 2025 · alle cijfers zijn onderbouwd\nValve liet de deur twee keer openstaan, met een tussenpoos van drieëndertig maanden. Ze ging nooit dicht.\n\nEr zijn zes gevallen gemeld waarin accounts werden overgenomen via het eigen hulpkanaal van Steam, of via de inloggegevens die door dat kanaal worden beschermd. Elk bedrag is het cijfer dat de genoemde bron heeft gepubliceerd, en elke bron wordt bij naam genoemd. Twee van de zes gevallen zijn volledig vergoed. Het verschil tussen deze gevallen en de rest lag niet in wat er gebeurde, maar in wie er toekeek.\n\nValve, schriftelijk — februari 2023\"De betreffende items zijn uit je account verwijderd omdat ze afkomstig waren van een account dat via een ondersteuningsverzoek was gehackt; het CS:GO-team neemt hiervoor de verantwoordelijkheid op zich. We hebben de ruiltransacties ongedaan gemaakt en de items verwijderd uit alle accounts die ze hadden ontvangen.\"Steam Ondersteuning voor het beantwoorden van een ontvanger van HFB-berichten, overgenomen door Dexerto, 21 februari 2023 ↗ gearchiveerd 2025-08-18 ↗\nValve, weer schriftelijk — november 2025 · 33 maanden later\"Een supportmedewerker die de hulpaanvraag heeft afgehandeld, heeft onze procedure niet gevolgd, waardoor uw account aan iemand anders is toegewezen. Mijn excuses voor deze fout.\"Steam Reactie van Support op Hawkeye337, geciteerd in Dexerto, 14 november 2025 ↗\n21 juni 2022\nHFB — de grootste voorraad in het spel$2,000,000+ · verhoogd naar $3,000,000+ in de vervolgmeting van februari 2023\n\nZeven Souvenir AWP Dragon Lores en de #1 Blue Gem Karambit; dat mes alleen al heeft een waarde van ongeveer $1.26 miljoen. Het account was al drie jaar inactief, terwijl de mobiele authenticator nog steeds actief was; het e-mailadres en het wachtwoord zijn toch gewijzigd via de herstelprocedure van de klantenservice.\n\nHet geld was al op voordat de spullen weg waren. Volgens berichten $200,000+ Een deel van de verkoopopbrengst was al opgenomen via market.csgo.com — een marktplaats waar transacties in contanten en cryptovaluta worden afgewikkeld. Bij het ongedaan maken van een transactie krijg je de skin terug. Het geld dat iemand al heeft opgenomen, wordt niet teruggegeven.\n\nEn de oplossing werkte niet meer. Een koper heeft zijn ‘Souvenir Dragon Lore’ naar een opslagruimte in het spel verplaatst. Het rollback-script van Valve kon niet in de eigen container kijken, dus heeft het de eigenaar een nieuw exemplaar gegeven en het verborgen exemplaar laten staan — Valve heeft een $130,000 item bij een poging om een diefstal ongedaan te maken. Het werd ontdekt door het vergelijken van item-ID’s en meldingen van de community, en werd een maand later, in juli 2022, verwijderd. De koper kreeg zijn geld terug van BUFF, niet van Valve. Een noodmaatregel die zo wankel is, is geen controle; het is wat een platform doet als het geen controle heeft.\n\nDexerto, 21 juni 2022 ↗ gearchiveerd 2022-07-02 ↗ · Kaspersky ↗ · uitbetalingsbedrag per Esportfire, 22 juni 2022 ↗ gearchiveerd 2026-05-15 ↗, daar toegeschreven aan meerdere Twitter-bronnen · duplicatie en verwijdering volgens Esportsbetting, 14 juli 2022 ↗\n\nGerestaureerdDe transacties werden ongedaan gemaakt. De artikelen werden weer uit de voorraad gehaald van mensen die er de volle prijs voor hadden betaald.\n14 augustus 2022\nCS.Money — de eigen bots van het platform$6,300,000 · 19,000+ skins · eerste schatting $1.6M\n\nAanvallers hebben de bestanden van de mobiele authenticator van de handelsbots van de marktplaats buitgemaakt en leeggemaakt, waarna ze een deel van de buit naar bekende handelaren hebben gestuurd om het spoor te verdoezelen. Onderzoekers uit de gemeenschap hebben in kaart gebracht 55 accounts van aanvallers binnen enkele uren en publiceerde ze.\n\nValve heeft niets teruggedraaid. Als reden werd opgegeven dat een site van een derde partij buiten Steam valt — dezelfde Steam waarvan de inventaris, handels-API en het accountsysteem van begin tot eind door de diefstal werden misbruikt.\n\nEsportfire, 14 augustus 2022 ↗ gearchiveerd 2025-11-15 ↗\n\nAfgewezenEr vond geen terugboeking plaats. Het verlies bleef voor rekening van het platform en zijn gebruikers.\nGemeld\n21 februari 2023\nQkss — dezelfde deur, dezelfde acteur$1,000,000+\n\nEr is gemeld dat dit op dezelfde manier is afgehandeld als HFB, door dezelfde medewerker, via hetzelfde ondersteuningsverzoek. HFB was acht maanden eerder volledig afgehandeld. Qkss was dat niet.\n\nEén route. Twee antwoorden. Uit de gepubliceerde gegevens blijkt geen enkel verschil tussen de twee gevallen, behalve de omvang van het publiek.\n\nDexerto, 21 februari 2023 ↗ gearchiveerd 2025-08-18 ↗\n\nAfgewezenNiet gerestaureerd.\nGemeld\nfebruari 2023\nDe handel met voorkennis zelf — een jaar lang≈ $320,000 · heeft een looptijd van ongeveer een jaar; het gaat niet om een voorraadwaardering\n\nVia de ondersteuningspagina kon de accountgeschiedenis worden geraadpleegd tot en met 15 jaar oud — de eerste cd-sleutel, de eerste e-mail, de eerste kaart. Dat is precies het bewijs dat bij het herstelproces wordt gevraagd, en daarom wint degene die de database beheert altijd het geschil met degene die de rekening beheert.\n\nBlogger Mzkshow onthulde hoe de insider „Steam Help” en zijn medewerker „Alexander” het gemunt hadden op inactieve accounts met meer dan $100k aan skins. Een gestolen M4A4 Howl met iBUYPOWER- en Titan Katowice 2014-holo’s werd verkocht voor $35,000 en kwam uiteindelijk terecht bij Valerii \"b1t\" Vakhovskyi van NAVI, die hier geen idee van had. Nadat Valve tussenbeide was gekomen, heeft de aannemer zijn gehele Steam helpdesk ontslagen.\n\nVKPlay ↗ · Lis-Skins ↗ · Escorenews (RU) ↗ · Dexerto (EN) ↗\n\nGeen registerValve heeft nooit bekendgemaakt om hoeveel accounts het hier ging, noch heeft het de betrokkenen hiervan op de hoogte gesteld.\nGemeld\n2 december 2024\n\"Matvey\" — na de ontslagen$13,000\n\nEr werd toestemming gegeven voor herstel aan iemand die accountgegevens had verstrekt die de eigenaar zelf niet kon verifiëren. Twee jaar nadat de aannemer zijn Steam-helpdesk had opgeheven, leverde dezelfde aanpak hetzelfde resultaat op.\n\nGearchiveerd bericht, 2 dec. 2024 ↗ gearchiveerd 2025-08-05 ↗ · bronrijen en hashes ↓\n\nAfgewezenNiet gerestaureerd.\n13 november 2025\nHawkeye337 (Mark Spurlock) — en de tweede bekentenis≈ $300,000–$500,000 · de volledige holo-collectie van Katowice 2014\n\nDe aanvaller eiste 1 bitcoin en begon de collectie naar Negevs te verplaatsen om deze te vernietigen. Steam Het schriftelijke antwoord van Support is de tweede bekentenis hierboven: een technicus heeft de hulpaanvraag afgehandeld, heeft de procedure niet gevolgd en heeft het account aan iemand anders doorgegeven.\n\nDe oorzaak van de storing was de toevoer. Enkele uren nadat de berichten met de tag Valve op X waren geplaatst, werd het account teruggegeven en werden alle stickers hersteld. Qkss had dat publiek niet.\n\nSkin.club ↗ · Dexerto ↗ · Esportfire ↗ gearchiveerd 2025-12-17 ↗\n\nGerestaureerdBinnen enkele uren nadat het bericht trending was, werd het weer verwijderd.\nWat uit de boekhouding blijkt, en wat geen enkel afzonderlijk geval aantoont.\n\nDe route is nooit afgesloten geweest. De eerste opname dateert van februari 2023 en de tweede van november 2025 — met een tussenpoos van drieëndertig maanden, met tussendoor een massaal ontslag bij de aannemer, een gedocumenteerde herhaling en een inbreuk op het platform ter waarde van $6.3 miljoen. Vanaf de eerste diefstal in dit register bleef het kanaal open voor drie jaar en vijf maanden. Wat er ook in 2023 was geregeld, het hulpverzoek zorgde er in november 2025 nog steeds voor dat een account naar de verkeerde persoon werd doorgestuurd — een uitspraak van Valve zelf.\n\nBij de schadevergoeding stond de aandacht op de schade, niet op de schade zelf. Hersteld: de grootste inventaris in het spel, en de verzamelaar wiens thread trending was. Afgewezen: $1,000,000, $6,300,000, $13,000. Valve heeft de regel die hij hanteert nooit gepubliceerd, omdat een gepubliceerde regel die drie zou moeten verklaren.\n\nNiemand werd hiervan op de hoogte gesteld. Niet de gebruikers van wie de accountgegevens uit de database zijn gelezen, niet een toezichthoudende instantie, niet de markt die de artikelen te goeder trouw heeft gekocht en ze vervolgens moest teruggeven. Er is geen melding van een inbreuk, geen incidentrapport, geen overzicht van het aantal getroffen accounts — en de opbrengst die als geld overblijft, via marktplaatsen die in contanten en cryptovaluta uitbetalen. Een transactie kan niet worden teruggedraaid als het geld eenmaal uit Steam is gestroomd.\n\nValve bevat het audittraject van de ondersteuning, het logboek van de hersteltickets en het transactieoverzicht voor elke bovenstaande regel. Hiervan is niets overgelegd. Vraag je eigen exemplaar aan →\n\nDe NDA-kwestie\nVertrouwelijkheid moet gepaard gaan met technische verantwoordelijkheid.\n\nVergelijk geheimhoudingsovereenkomsten met daadwerkelijke machtigingen, exportbeperkingen, goedkeuringen voor het resetten van wachtwoorden en toegangslogboeken. Een standaardantwoord biedt geen oplossing voor een beschuldiging dat er misbruik is gemaakt van het herstelproces zelf.\n\nArtikelen 28, 32–34 van de AVG\n\nArtikel 33 geeft een verwerkingsverantwoordelijke 72 uur de tijd om de toezichthoudende autoriteit in kennis te stellen van een inbreuk op persoonsgegevens; artikel 34 schrijft voor dat de betrokkenen op de hoogte moeten worden gesteld wanneer het risico voor hen groot is. Valve heeft tweemaal schriftelijk bevestigd dat zijn helpdesk accounts aan de verkeerde personen heeft doorgegeven — inclusief accountgeschiedenis, factuurgegevens en al het overige. Er is geen kennisgeving op grond van een van beide artikelen gepubliceerd, en geen enkele betrokken gebruiker heeft gemeld er een te hebben ontvangen. Lees de verordening ↗ gearchiveerd 2026-09-20 ↗\n\nVermeld in uw verzoek dat u ondersteuning nodig hebt →\nDeel C — Wettelijke kaders · Paragraaf 15 · Commerciële schaal\nVolg het geld. Scheid de transacties.\nContext en bronbeperkingen\n\nDe vraag of er sprake is van commercieel gebruik wordt nog urgenter wanneer de geldstromen van elkaar worden gescheiden. Overdrachten van goederen aan derden, de primaire verkopen van Valve en externe uitbetalingen zijn verschillende transacties.\n\nHet artikel is van Valve. De voorraad is van Valve. De overdracht vindt plaats op de servers van Valve. Alleen de betaling vindt ergens anders plaats — en dat is de stap die bepaalt of iemand een geldtransporteur is, en de enige stap die Valve niet uitvoert.\n\nHet inkomstenmechanisme\nWaar het geld daadwerkelijk naartoe gaat.\nDrie paden / één-item-economie\n01 / AccountGebruikersoverzicht\n\nAantal items: Steam\n\n02 / OverdrachtP2P-handel\n\nGebruiker ↔ bot of gebruiker ↔ gebruiker\n\n03 / AfwikkelingExtern platform\n\nSaldo van de locatie of afbetaling Steam\n\nOplageDe economische motor reikt verder dan een transfersom\n\nSteam levert de voorraad- en overdrachtsinfrastructuur die door externe markten wordt gebruikt. Het economische argument van het onderzoek is dat de liquiditeit bij wederverkoop en de terugkerende vraag de uitgaven voor kisten, sleutels en vervangingsartikelen in stand houden, met vergoedingen op daaropvolgende verkopen op de Community Market. Bij een directe P2P-overdracht wordt geen commissie van de Community Market in rekening gebracht; dat boekhoudkundige feit doet echter geen afbreuk aan het bredere voordeel. Valve behoudt te allen tijde de controle over de toegang tot de account en de handelsbeperkingen.\n\n01 / Secundaire vraagLiquiditeit en restwaarde\n\nExterne vraag naar handel en kansspelen\n\n02 / Uitgaven in het basisonderwijsSleutels, hoesjes en capsules\n\nAankopen bij Valve, indien aangeboden\n\n03 / OmzetOpbrengsten uit eerste verkoop\n\nPlus provisies op daadwerkelijke verkopen op de markt\n\n5% + 10%Steam + CS2-vergoeding op verkopen via de Community Market\n\nDe economische conclusie van het onderzoek: liquide doorverkoopmarkten kunnen de aankoop van nieuwe artikelen stimuleren. De bekende 15% is een combinatie van marktvergoedingen, waarbij minimumbedragen en afrondingen van toepassing zijn; het is geen heffing op alle buitenlandse handel.\n\nHet tariefoverzicht van de Community Market van Valve ↗ gearchiveerd 2026-09-21 ↗. Op 25 februari 2026 De procureur-generaal van New York heeft een rechtszaak aangespannen gearchiveerd 2026-09-01 ↗ waarin wordt beweerd dat betaalde lootboxen verband houden met de doorverkoop voor contant geld en schade door gokken — hetzelfde verband dat in dit dossier vanuit het oogpunt van de technische infrastructuur wordt gedocumenteerd. Die klacht is een bewering, geen vaststelling; ze wordt hier aangehaald omdat een staatswetshandhavingsinstantie een vraag heeft gesteld die aansluit bij de vraag die in dit dossier wordt gesteld: waar is het handhavingsdossier dat overeenkomt met de publieke verklaringen?\n\n01 / InvoerStorting in cryptovaluta\n\nExterne service- en portemonneegegevens\n\n02 / OmzettingBalans → skins\n\nArtikelen geleverd via Steam transacties\n\n03 / UitgangVerkoop van externe fiatvaluta\n\nVerkoper, koper en uitbetalingsdienst\n\nKYC?Controleer bij elke overdracht wie de leiding heeft\n\nDit is de manier waarop dit moet worden onderzocht, en niet via een native Steam API-dienst voor het omzetten van contant geld. Controleer bij elke externe aanbieder de identiteitscontrole, de bewaring, de transactie-ID’s en de ontvangers van uitbetalingen voordat je een uitbetaling zonder KYC-controle toestaat.\n\nVerenigde Staten / Wet op het bankgeheim\nClassificeer eerst de activiteit en daarna de verplichting.\n\nFinCEN beoordeelt het overmaken van geld op basis van de activiteiten van een bedrijf. Het accepteren en overmaken van converteerbare virtuele valuta kan leiden tot verplichtingen op het gebied van gelddiensten, afhankelijk van de toepasselijke definities en uitzonderingen. De Steam-wallet van Valve accepteert geld en zet dit om in in-game-items; die items worden vervolgens via externe exploitanten omgezet in echte valuta. Het item en de overdracht ervan vinden plaats op de infrastructuur van Valve; de uitbetaling vindt daar niet plaats, en of een deel van die cyclus voldoet aan de definities van geldovermaking is een classificatiekwestie voor FinCEN, geen conclusie die hier wordt getrokken.\n\nFinCEN FIN-2019-G001, §§ 1–2, 5.1 ↗ gearchiveerd 2025-07-11 ↗\n\nEuropese Unie / witwassen\nVolg opbrengsten, kennis en ondersteuning.\n\nRichtlijn (EU) 2018/1673 heeft betrekking op opzettelijke witwaspraktijken en medeplichtigheid waarbij opbrengsten uit misdrijven betrokken zijn. De vraag in het onderzoek is wat Valve wist over de exploitanten die na 13 juli 2016 gebruik maakten van zijn handels- en OpenID-infrastructuur – toen het dat gebruik openbaar beschreef – en wat het daartegen heeft ondernomen. Valve heeft geen handhavingsrapport per exploitant gepubliceerd; dat rapport, en niet dit dossier, zou de vraag beantwoorden.\n\nEU-strafrechtelijk kader ↗\n\nTerminologie van AMLD6: De bovengenoemde strafrechtelijke richtlijn staat los van Richtlijn (EU) 2024/1640, ook wel AMLD6 genoemd. Voor deze laatste geldt een algemene omzettingstermijn tot 10 juli 2027, met bepaalde uitzonderingen. Artikel 78 ↗ gearchiveerd 2026-08-30 ↗\n\nDeel C — Wettelijke kaders · Paragraaf 16 · Kennisgeving, reactie, aansprakelijkheid\nDe Wet inzake digitale diensten: leg kennis vast\nContext en bronbeperkingen\n\nTwee onderdelen van een kennisgeving op grond van artikel 16 vallen onder de verantwoordelijkheid van de indiener en niet onder dit dossier: de eigen gegevens van de indiener en een verklaring te goeder trouw dat de informatie juist is. Al het overige dat het artikel vereist — de onderbouwde toelichting en de exacte elektronische locatie — is vastgelegd in paragraaf 3 en in het route-register, met opgeslagen reacties en hashes, zodat elke partij de kennisgeving kan indienen. Twee verdere beperkingen van de wet zelf: het verlies van de hostingvrijstelling leidt op zichzelf niet tot aansprakelijkheid op grond van enige andere wet, en het 6% in artikel 52, lid 3, is een wettelijk maximum, geen vastgestelde boete tegen Valve.\n\nOp grond van de DSA behoudt een hostingprovider zijn aansprakelijkheidsvrijstelling slechts zolang hij geen concrete kennis heeft en nalaat op te treden. Dit dossier vormt die kennisgeving. Daarin worden de hosts, de datums, de opgeslagen antwoorden en de hashes genoemd. Sinds de publicatie is de vraag niet langer of Valve het wist, maar wat Valve daarna heeft gedaan.\n\n01juli 2016 / de tentoonstelling ‘The Dossier’\nEen eis van tien dagen.\n\nDe hierboven weergegeven kennisgeving vormt het historische uitgangspunt voor de vergelijking van de handhavingsmaatregelen in het kader van het onderzoek.\n\n0217 februari 2024 / algemene aanvraag\nHet DSA-tijdvenster.\n\nMaak een onderscheid tussen gedragingen in het verleden en gedragingen in de periode waarin de desbetreffende DSA-verplichtingen van toepassing zijn.\n\n03Tien jaar / momentopname van het oorspronkelijke dossier\nDe looptijd moet worden bijgehouden.\n\nDe tijd die is verstreken sinds juli 2016 (zie paragraaf 11) is een dossierindicator. Het gaat hier niet om tien jaar aan vastgestelde DSA-overtredingen. Koppel elke kennisgeving aan een specifiek punt, de toepasselijke wetgeving, het bewijs van verzending en het antwoord.\n\nArtikel 52, lid 3 / wettelijk maximum6%\nvan de jaarlijkse wereldwijde omzet\n\nMaximale boete voor een schending van de DSA-verplichtingen, berekend op basis van het voorgaande boekjaar van de aanbieder. Dit is een wettelijk maximum, geen daadwerkelijk opgelegde boete tegen Valve.\n\nArtikelen 6, 8 en 16 / de juridische toets\n\nBij relevante hostingdiensten kunnen specifieke kennis en het nalaten om tijdig op te treden leiden tot het vervallen van de vrijstelling voor hostingdiensten. Een voldoende nauwkeurige melding kan aantonen dat er kennis was van de betreffende inhoud. De DSA legt geen algemene toezichtplicht op; het vervallen van de vrijstelling leidt op zichzelf niet tot aansprakelijkheid op grond van een andere wet.\n\nDSA: artikelen 6, 8, 16, 52, 53, 93 en overweging 17 ↗ gearchiveerd 2026-09-20 ↗\n\nOpgeslagen klachten bekijken ↗De tijdlijn van het account samenstellen →Volledige juridische en economische analyse →\nDeel C — Wettelijke kaders · Paragraaf 17 · Identiteit, leeftijd, toegang tot commerciële diensten\nMinderjarigen: een Steam-login geldt niet als leeftijdsverificatie\nContext en bronbeperkingen\n\nEr komen nergens in dit dossier gegevens van minderjarigen voor en er zijn ook geen gegevens verzameld: de auteurs hebben zich niet geregistreerd op, geen gegevens achtergelaten bij of ingelogd op enig genoemd platform. Iedereen die op dit hoofdstuk voortbouwt, dient bewijsmateriaal waarbij een kind betrokken is vertrouwelijk te behandelen en identificerende details uit openbare bewijsstukken te verwijderen. COPPA wordt hier aangehaald als een wet inzake de privacy van kinderen met eigen toepassingsvoorwaarden — doelgroep, daadwerkelijke kennis, verzamelde persoonsgegevens — en niet als een algemene regel voor de minimumleeftijd voor gokken; de klacht uit New York uit 2026 is een beschuldiging door een staatsautoriteit, geen vaststelling.\n\n\"Inloggen met Steam\" bewijst dat er een account bestaat. Dat zegt niets over de leeftijd — en op deze sites is het de enige barrière tussen een kind en een storting. Lees het met Paragraaf 3.1: binnen de Steam-client wordt de waarschuwing die een browser zou weergeven nooit geactiveerd, dus het kind ziet er nooit een.\n\nWat biedt Steam OpenID?Accountgegevens\n\nEen geverifieerde SteamID die wordt gebruikt om in te loggen of een account te koppelen.\n\n≠\nWat de exploitant moet aantonenDeelnamevoorwaarden\n\nLeeftijd, rechtsgebied en eventuele vereiste identiteitscontroles.\n\nTechnische grondslag: Documentatie over Steamworks OpenID ↗ gearchiveerd 2026-09-21 ↗. De gedocumenteerde identiteitsverklaring houdt niet in dat de gebruiker wettelijk mag gokken.\n\nCOPPA / kinderen jonger dan 13 jaar\nGeef aan wat de operator en de gegevens zijn.\n\nDe COPPA is van toepassing op diensten die zich op kinderen richten en op diensten waarvan daadwerkelijk bekend is dat zij persoonsgegevens verzamelen van kinderen jonger dan 13 jaar. Het is een wet inzake de privacy van kinderen, geen algemene regel voor de minimumleeftijd voor gokken. Bepaal de doelgroep, de verzamelde persoonsgegevens, de mate van kennis en de procedure voor ouderlijke toestemming.\n\nFTC: COPPA-vereisten ↗ gearchiveerd 2026-09-21 ↗\n\nHet bewijsmateriaal dat bewaard moet blijven\nLeg het traject vast, van het inloggen tot het storten.\n\nBehoud de leeftijdsbeperking, de tekst van de registratievoorwaarden, de toelatingsvoorwaarden, het betalingsproces en de klachtenhistorie van de website. Beoordeel elke exploitant afzonderlijk. Behandel al het bewijsmateriaal waarin een kind betrokken is vertrouwelijk en verwijder identificerende gegevens uit openbare stukken.\n\nEen daarmee verband houdend openbaar handhavingsdossier is het Aankondiging van een rechtszaak in New York in 2026 gearchiveerd 2026-09-01 ↗, waarin wordt beweerd dat betaalde loot boxes schade toebrengen aan jonge gebruikers. Het gaat hier niet om een bevinding in het kader van de COPPA.\n\nDeel C — Wettelijke kaders · Paragraaf 18 · Verzoek op grond van artikel 15 van de AVG\nHet verzoek. Het antwoord. De ontbrekende vergelijking.\n\nHij vroeg om vier dingen, waaronder het logbestand waarmee zou kunnen worden achterhaald wie er een API-sleutel aan zijn account had toegevoegd. Drie dagen later werd het ticket afgesloten met een link naar een pagina waarop geen van deze gegevens te vinden is — en de zin waarmee het wordt afgesloten, wordt tegengesproken door de eigen advocaten van Valve.\n\nVan wie deze account is · Herkomst en beperkingen\n\nDeze schermafbeeldingen zijn niet van PhishDestroy. Ze zijn afkomstig van een gewone Steam-accounthouder — een deelnemer aan een korte enquête die in het kader van dit project is gehouden, die het verzoek zelf heeft ingediend en de schermafbeeldingen heeft aangeleverd. De account is van hem, het ticket is van hem en de correspondentie vindt plaats tussen hem en Steam Support. Dit project heeft het verzoek niet ingediend, heeft geen account op het platform en is geen partij in dit ticket.\n\nOp 16 september 2026 diende hij een verzoek om inzage in zijn persoonsgegevens in op grond van artikel 15 van de AVG/CCPA in, waarin hij specifiek vroeg om registratielogboeken van API-sleutels, inloggeschiedenis met IP-adressen, autorisatiegeschiedenis van apparaten en transactiegeschiedenis. Op 17 september verwees medewerker „Logen” hem door naar de zelfbedieningspagina „Accountgegevens”. Op 18 september gaf hij aan dat de gevraagde categorieën niet op die pagina stonden en vroeg hij om escalatie naar het privacyteam of de functionaris voor gegevensbescherming (DPO). Op 19 september sloot medewerker „Kal“ het ticket af met dezelfde doorverwijzing. Beide schermafbeeldingen zijn hieronder bewaard (e-mailadres van de aanvrager is verborgen; SHA-256 in steam_tos_assets/screenshot-manifest.json).\n\nHij is om een heel gewone reden een geschikte aanvrager: zijn account bevat een Steam Web API-sleutel die hij niet zelf heeft aangemaakt en die is geregistreerd bij localhost. Het is niet bekend wanneer het is ontstaan — niet aan hem, en ook niet op basis van iets wat Valve hem ter beschikking heeft gesteld, omdat het enige document waarmee de datum zou kunnen worden vastgesteld het registratielogboek van de API-sleutel is, en dat is precies de categorie die de afsluiting achterhield. De sleutel is niet nieuw: hij dateert van vóór het moment waarop hij er kennis van nam, met een tijdsinterval dat hij om dezelfde reden niet kan bepalen.\n\nAndere accounthouders dienen hetzelfde verzoek in. Elk antwoord dat binnenkomt, wordt hier op dezelfde voorwaarden toegevoegd als deze twee — ticketnummer, vastleggingsdatum, SHA-256, aanvrager geanonimiseerd — ongeacht of de categorieën worden verstrekt of geweigerd.\n\nDit project neemt geen standpunt in over de reden waarom het ticket is gesloten. Er werd daarin geen reden vermeld, en ook hier wordt er geen reden uit afgeleid.\n\nHet verzoek. Het antwoord. De vergelijking.VOLG HET VERSLAG\nStap 3 / 3\n\nHij vroeg om vier specifiek genoemde categorieën. De pagina ‘Accountgegevens’ waarnaar hij werd doorverwezen, is de eigen selfservice-export van Valve, en dit project kan de inhoud daarvan niet opsommen voor de account van iemand anders — daarom wordt hier geen volledige vergelijking per categorie gepubliceerd. Wat wel vastligt, is zijn verklaring van 18 september dat de categorieën er niet waren, en de afsluiting van 19 september waarin de doorverwijzing werd herhaald zonder hierop in te gaan.\n\nHET VERZOEKSpecifieke categorieënAPI-sleutel, inloggegevens, apparaat- en transactiegegevens\nHET ANTWOORDReferentie accountgegevensControleer de uitwisseling van steun\nDE TESTWat is er geleverd?Vergelijk elke gevraagde categorie\nScherm 1/2 — Verzoek (16 sep) en eerste antwoord, agent \"Logen\" (17 sep)\nGDPR ticket HT-2YBP-F7JP-D4VB — request and first response\nBron: help.steampowered.com, ticket HT-2YBP-F7JP-D4VB · vastgelegd op 16–17 september 2026 · e-mailadres van de aanvrager verborgen 2026-09-21 · Bestand: gdpr-ticket-1.png · SHA-256 da940c731ab9869d226e9d06ccc8a1b393738766b7b0c445a56662623e025a66 (screenshot-manifest.json).\nScherm 2/2 — Escalatieverzoek (18 sep) en afsluiting, medewerker \"Kal\" (19 sep)\nGDPR ticket HT-2YBP-F7JP-D4VB — escalation request and closure\nBron: help.steampowered.com, ticket HT-2YBP-F7JP-D4VB · vastgelegd op 18–19 september 2026 · Bestand: gdpr-ticket-2.png · SHA-256 44844ea7b251f7fd7d79f87ee1578a846606a97b9659d3a53b322120c422219b (screenshot-manifest.json).\nAfsluitende reactie, 19 september (letterlijk):\n\"De gegevens Steam die worden bewaard, zijn al te vinden op de pagina 'Accountgegevens'. Aangezien de klantenservice Steam geen verdere informatie kan verstrekken, dit verzoek wordt afgesloten.\"\nGeen gegevens verstrekt · geen rechtsgrond voor weigering vermeld · geen uitkomst van de escalatie weergegeven\nDie zin klopt niet, en de advocaten van Valve zelf bewijzen dat. In de brief van de raadsman van 1 oktober 2025 wordt in paragraaf 1.9 een correlatie op apparaatniveau beschreven waarbij één apparaat aan tientallen accounts wordt gekoppeld (Bijlage A). Bij datzelfde antwoord waren 830 pagina’s aan bewaarde documenten gevoegd (Bijlage B). Er staat niets van op de pagina ‘Accountgegevens’.\nWaarom dit account om het API-sleutelverslag heeft gevraagd\n\nHij heeft die vier categorieën niet zomaar uitgekozen. De localhost het sleutelwoord voor zijn account is het kenmerk van een script, niet van iemand die een echt domein in de ontwikkelaarspagina invoert (Paragraaf 5, Paragraaf 6). Het enige document waaruit blijkt wie het heeft aangemaakt en waarvandaan, is het registratielogboek van de API-sleutel. Dat was het eerste waar hij om vroeg. Dat is wat de rechtbank achterhield.\n\nBron: de rekeninghouder, tijdens de enquête voor dit project. De bovenstaande schermafbeeldingen van de tickets zijn versleuteld; de sleutelpagina is niet gepubliceerd.\n\nBeoordeling · PhishDestroy\n\nHet afsluiten van een ticket terwijl de vraag nog openstaat, is hier geen toeval. Het is de normale gang van zaken. Wij hanteren 16,319 bewaarde klachten- en ondersteuningsdossiers en 354 ontdubbelde ondersteuningsverzoeken daaruit afgeleid. Dit kaartje is een gedateerd, volledig vastgelegd voorbeeld van de vorm die ze aannemen.\n\nOndersteuningsticket — BewaardHT-2YBP-F7JP-D4VB\nType aanvraagArtikel 15 van de AVG (verzoek om inzage)\nTicketstatusGESLOTEN 19 SEP 2026 — GEEN GEGEVENS VERSTREKT\nMakelaars op de beurs\"Logen\" (17 sep), \"Kal\" (19 sep)\nGearchiveerd16 september 2026\nGevraagde gegevensWie heeft de Web API-sleutel geregistreerd die aan dit account is gekoppeld, en vanaf welk IP-adres / apparaat / tijdstempel?\nAangehaalde rechtsgrondslagAVG, artikel 15 — recht op inzage in persoonsgegevens\nHet wettelijk kader:Artikel 12, lid 3, geeft de verwerkingsverantwoordelijke een termijn van één maand vanaf de ontvangst (die met opgave van redenen kan worden verlengd). Die termijn was op het moment van publicatie nog niet verstreken, en in dit dossier wordt geen schending van de termijn aangevoerd. Het bezwaar betreft de inhoud: het slotantwoord bevat een link naar een zelfbedieningspagina, maar laat niet zien dat de vier genoemde gegevenscategorieën zijn verstrekt, en indien de verwerkingsverantwoordelijke weigert op te treden, is hij krachtens artikel 12, lid 4, verplicht de redenen daarvoor en de klachtenprocedures te vermelden. Geen van beide komt in het slotantwoord voor.\nWaarom juist deze gegevens van belang zijn\n\nHet gebeurtenissenlogboek van de Web API-sleutel is het overzicht waaruit blijkt of een derde partij een sleutel heeft geregistreerd met behulp van een gestolen sessiecookie — het mechanisme dat wordt beschreven in de klachten over inventarisdiefstal die in het archief van dit dossier zijn bewaard. Het openbaar maken van wie een API-sleutel heeft geregistreerd, vanaf welk IP-adres en op welk tijdstip, zou:\n\nGeef het slachtoffer de mogelijkheid om het IP-adres waarmee de API is aangemaakt te vergelijken met zijn eigen inloggeschiedenis\nBreng de IP-adressen van datacenters aan het licht die verband houden met bekende infrastructuren voor phishing en gokbots\nBewijs aanleveren dat bruikbaar is in civiele of strafrechtelijke procedures tegen de dader\nGeef aan of de rekeninghouder op de hoogte is gesteld toen de sleutel werd aangemaakt\nWat uit het dossier blijkt: Valve bewaart gegevens op apparaatniveau en gegevens over accountkoppelingen — deze worden beschreven in de brief van de raadsman van 1 oktober 2025 (zie Bijlage A, Bewijsmemorandum — Bron 1). In ticket HT-2YBP-F7JP-D4VB werd door de betrokkene om hetzelfde soort gegevens gevraagd en werd het ticket afgesloten met een verwijzing naar een zelfbedieningspagina die volgens de betrokkene deze gegevens niet bevatte. Of die weigering rechtmatig is, is een vraag voor de toezichthoudende autoriteit; het gevolg is dat de betrokkene de gegevens niet ontvangt.\nDe uitwisseling — vier berichten, drie dagen\n\nTwee Steam-klantenservicemedewerkers reageerden onder de voornamen die op het ticket stonden vermeld: „Logen” op 17 september en „Kal” op 19 september. Beiden verwezen de aanvrager naar de pagina „Accountgegevens”. Niets op het ticket geeft aan of het verzoek het privacyteam of de functionaris voor gegevensbescherming van Valve heeft bereikt, en uit het dossier blijkt niet wie de medewerkers zijn, wat hun functies zijn of hoe het ticket is doorgestuurd.\n\n16 SEP\nArt. 15: verzoek ingediend met betrekking tot vier genoemde categorieën gegevens\n17–18 sep\nVerwijzing naar accountgegevens; de aanvrager vraagt om escalatie naar de functionaris voor gegevensbescherming\n19 SEP\nTicket gesloten met dezelfde verwijzing; geen gegevens, geen opgegeven reden\nWaarop heeft de betrokkene volgens artikel 15 van de AVG uitdrukkelijk recht?\nArt. 15, lid 1, onder a)Doeleinden van de verwerking — waarom Valve de gegevens bewaart\nArt. 15, lid 1, onder b)Gegevenscategorieën — wat Valve inhoudt\nArt. 15, lid 1, onder c)Ontvangers of categorieën van ontvangers — wie de gegevens heeft ontvangen (bijvoorbeeld de houder van de API-sleutel)\nArt. 15, lid 1, onder d)Bewaartermijn of criteria voor het vaststellen daarvan\nArt. 15, lid 3Een kopie van de persoonsgegevens die worden verwerkt — d.w.z. het API-sleutelverslag zelf\nART. 12, lid 3Antwoord vereist binnen één maand vanaf de ontvangst; een verlenging moet binnen die maand worden gemeld. De termijn was op het moment van publicatie nog niet verstreken. Art. 12, lid 4: Als de verwerkingsverantwoordelijke geen maatregelen neemt, moet hij aangeven waarom en de betrokkene informeren over de mogelijkheden om een klacht in te dienen.\nProcedure voor het indienen van een klacht bij de toezichthouder — voor alle gebruikers\n\nElke gebruiker die een verzoek op grond van artikel 15 AVG heeft ingediend bij Valve en geen conform antwoord heeft ontvangen (of een standaardafwijzing zonder gegevens), kan een klacht indienen bij de toezichthoudende autoriteit in zijn of haar EU-/EER-lidstaat. De vestiging van Valve in de EU is Valve GmbH in Hamburg, dus de leidende toezichthoudende autoriteit voor grensoverschrijdende klachten is de Hamburgse commissaris voor gegevensbescherming en vrijheid van informatie (HmbBfDI). (De vertegenwoordiger op grond van artikel 27 van Valve is eveneens gevestigd in Hamburg; het adres van een vertegenwoordiger is op zich niet bepalend voor de bevoegde autoriteit.) Er kan ook een klacht worden ingediend bij de autoriteit van de lidstaat van de klager op grond van artikel 77.\n\nHmbBfDI-klachtenformulier ↗ Tekst van de AVG (art. 12, 15, 77) ↗ gearchiveerd 2026-09-20 ↗Richtlijnen van het EDPB ↗\n\nTicketnummer voor eventuele klachten: HT-2YBP-F7JP-D4VB — in dit dossier opgenomen als een gedocumenteerd geval.\n\nEen gedocumenteerd geval\nDe documenten bestaan wel; de betrokkene heeft ze echter niet ontvangen.\n\nDe raadsman van Valve heeft in een brief van 1 oktober 2025 de correlatiegegevens op apparaatniveau beschreven. Op 19 september 2026 werd een verzoek op grond van artikel 15 voor dezelfde categorie gegevens afgesloten met een verwijzing naar een zelfbedieningspagina die volgens de verzoeker deze gegevens niet bevatte, zonder dat daarvoor een rechtsgrondslag werd vermeld. Ticket HT-2YBP-F7JP-D4VB is één gedocumenteerd geval; of dit een bredere praktijk weerspiegelt, is een vraag voor de toezichthoudende autoriteit, die Valve om zijn afhandelingsgegevens kan vragen.\n\nArtikelen 12, 15 en 77 van de AVG / Toezichthoudende autoriteit\n\nEen klacht op grond van de artikelen 12 en 15 kan kosteloos rechtstreeks bij de bevoegde toezichthoudende autoriteit worden ingediend (artikel 77). De autoriteit kan corrigerende maatregelen opleggen, waaronder bevelen om aan het verzoek om inzage te voldoen, en boetes op grond van artikel 83, lid 5, onder b), voor inbreuken op de rechten van de betrokkene. Het bewaren van het oorspronkelijke ticketnummer en een eventueel Valve-antwoord (of het ontbreken daarvan) versterkt een klacht.\n\nBekijk het DSAR-sjabloon →\nDeel C — Wettelijke kaders · Artikel 19 · Contractenrecht\nDe abonneeovereenkomst in strijd met de eigen architectuur van het platform\nContext en bronbeperkingen\n\nDe auteurs zijn geen juristen en dit alles vormt geen juridisch advies. De SSA wordt geciteerd uit de herziening van 10 september 2026; een andere herziening kan anders luiden, en de nummering van de artikelen is tussen de herzieningen gewijzigd — vergelijk het artikel met de versie die van toepassing was op het betreffende gedrag. De argumenten in de artikelen 25 en 32 geven aan wat de verordening voorschrijft, niet dat een toezichthoudende autoriteit een inbreuk heeft vastgesteld. De cijfers in argument 1 bevatten de toepassingsbeperkingen zoals uiteengezet in artikel 13.\n\nDrie van de centrale bepalingen van de SSA staan op gespannen voet met de manier waarop het platform is opgezet: het verbod op commercieel gebruik in combinatie met een prijsplafond op de Market, waardoor verkopen met een hoge waarde buiten het platform plaatsvinden; de aansprakelijkheidsclausule voor gebruikers met betrekking tot API-sleutels, in tegenstelling tot een sleutel-eindpunt waarvoor vóór 2023 geen tweefactorauthenticatie vereist was; en de handhavingsbepalingen, in tegenstelling tot een openbaar register waaruit blijkt dat er geen handhaving per exploitant plaatsvindt. Of deze spanningen van invloed zijn op de afdwingbaarheid, is een vraag voor de rechter; in dit hoofdstuk worden de feiten uiteengezet die een rechter ter beschikking zouden staan.\n\nArgument 1 / Marktkapitalisatiearchitectuur\nHet marktplafond en het verbod op commercieel gebruik\n\nDe Steam Community Market hanteert een maximumprijs van ongeveer $1,800. Op vijf marktplaatsen in een verouderde momentopname (23 september 2026) worden 248 CS2-artikelcategorieën op twee of meer van die marktplaatsen afzonderlijk tegen een prijs aangeboden die boven dat maximum ligt; dergelijke artikelen kunnen niet tegen die prijzen worden verkocht op het eigen platform van Valve. Eigenaren die die prijzen willen hanteren, maken gebruik van externe marktplaatsen, die draaien op Steam-accounts en de Steam-API — het gebruik daarvan wordt door de SSA als commercieel aangemerkt, tenzij dit uitdrukkelijk is toegestaan.\n\nArtikelen overschrijden het marktplafond → externe markten vullen het tekort aan → die markten maken gebruik van Steam-accounts en de Steam-API → de SSA verbiedt commercieel gebruik zonder toestemming → er is geen register met toestemmingen gepubliceerd. De gecombineerde vergoeding van de Community Market van ongeveer 15% geldt alleen voor verkopen die binnen de Market zijn afgerond, niet voor deze externe transacties.\nArgument 2 / Beveiligingsarchitectuur voor API-sleutels\nDe kwetsbaarheid van de API-sleutel is eerder een kwestie van platformontwerp dan van nalatigheid van de gebruiker\n\nVóór 2023 accepteerde het eindpunt voor het aanmaken van API-sleutels van Steam een POST-verzoek met een gestolen sessie-ID en genereerde het inloggegevens met uitgebreide rechten zonder bevestiging via e-mail, een tweede verificatiemethode of verificatie via een apparaat. De klachten over API-kaping die in dit onderzoek zijn verzameld, volgen allemaal hetzelfde patroon: een script van de aanvaller, een gestolen sessiecookie, het stilletjes aanmaken van een sleutel en het onderscheppen van transacties (de inhoud van het verzoek wordt weergegeven in paragraaf 8).\n\nArtikel 25 van de AVG (gegevensbescherming door ontwerp) en artikel 32 (beveiliging van de verwerking) schrijven technische maatregelen voor die in verhouding staan tot het risico. Het uitgeven van een toegangsbewijs waarmee transacties kunnen worden onderschept zonder een tweede authenticatiefactor of kennisgeving aan de eigenaar, is een ontwerpkwestie voor de verwerkingsverantwoordelijke. Of de SSA-clausule die de aansprakelijkheid bij de gebruiker legt, tegen die achtergrond kan worden ingeroepen, is een vraag voor de rechter en de toezichthoudende autoriteit.\n\nArgument 3 / Real-time inzicht\nValve ontvangt bij elke aanmelding de hostnaam van de authenticatie\n\nDe hostnaam van de authenticatieserver komt in leesbare tekst aan bij het OpenID-eindpunt van Valve in openid.return_to en openid.realm (de vorm van het verzoek wordt weergegeven in paragraaf 3). Het extraheren ervan is een standaardhandeling. Vanaf 2026-09-22 stond bij 26 paren het hoofddomein op de Link Filter, terwijl de host met de Steam-login dat niet was. Valve heeft geen handhavingsgegevens per operator gepubliceerd, dus uit openbare gegevens kan niet worden afgeleid of er naast de Link Filter nog andere maatregelen op deze hosts zijn toegepast.\n\nWie draagt de kosten?\nHet patroon in de gearchiveerde klachten\n\nIn de onderzochte klachten volgt het antwoord van Steam Support op een melding van misbruik van een API-sleutel steeds hetzelfde patroon: herstel wordt geweigerd, er wordt gewezen op de verantwoordelijkheid van de gebruiker voor het account en de bijbehorende API-sleutel, en het ticket wordt gesloten. In dit dossier wordt geen schatting gegeven van het totale aantal getroffen accounts of de totale waarde van het verlies; er is geen bron voor een dergelijk cijfer gevonden.\n\nDe vraag is niet of individuele gebruikers fouten hebben gemaakt. De vraag is wie verantwoordelijk is voor een architectuur die het tot 2023 mogelijk maakte dat een POST-verzoek met een gestolen cookie kon worden gebruikt om inloggegevens met uitgebreide rechten voor het verhandelen van effecten aan te maken, zonder dat er een melding werd gegeven en zonder tweefactorauthenticatie.\nDe SSA als document versus de SSA als contract\nEen rechtbank die dit dossier beoordeelt, zou de SSA niet op zichzelf beschouwen.\n\nHet zou dit document lezen in samenhang met de brief van de raadsman van oktober 2025, waarin de correlatie op apparaatniveau, de registratiedata van de auth-hosts, de tijdstempels van de batchregistraties, de inhoud van het verzoek om een API-sleutel en de tien jaar tussen de kennisgevingen van juli 2016 en de platforms die in september 2026 nog steeds in bedrijf waren, worden beschreven. Dat is het dossier waar Valve zich over zou moeten buigen.\n\nSSA ten opzichte van het dossier / belangrijkste punten\n\"Geen commercieel gebruik\" — het marktplafond zorgt ervoor dat hoogwaardige verkopen naar commerciële markten van derden worden verplaatst\n\"Gebruikers zijn verantwoordelijk voor API-sleutels\" — geen tweefactorauthenticatie op het sleutel-eindpunt vóór 2023\n\"We treden op tegen overtreders\" — sinds juli 2016 zijn er geen handhavingsgegevens per exploitant meer gepubliceerd\n\"Je hebt ingestemd met de voorwaarden\" — bij het 'hijack'-patroon wordt de instemming door een script verzonden, niet door de accounthouder\nConclusie · Wat uit het dossier blijkt en wat wij vragen\nDe bevindingen. De documenten waar we om vragen.\nContext en bronbeperkingen\n\nElk van de onderstaande bevindingen is gekoppeld aan een gedateerd openbaar document in de bovenstaande paragrafen. De verzoeken zijn gericht aan de autoriteiten die toegang kunnen afdwingen tot het enige waar dit onderzoek geen vat op heeft: de eigen handhavings-, toegangs- en verwerkingsgegevens van Valve.\n\nElk verzoek volgt op een bevinding met een datum. De autoriteiten kunnen documenten opvragen die in het kader van dit onderzoek op basis van openbare bronnen niet kunnen worden afgedwongen.\n\nWat uit openbare bronnen blijkt\n44 live-platforms worden geauthenticeerd via een afzonderlijk registreerbaar domein — 27 met een gepubliceerd bewijsbestand per route, 17 afkomstig uit handmatige verzameling en apart vermeld. Per 2026-09-22 was bij 26 paren het hoofddomein geblokkeerd in de Steam Link Filter, terwijl de host waarop de inloggegevens stonden dat niet was — csgogem.com geblokkeerd, api.csgem.com geregistreerd sinds maart 2014. Steam ontvangt die hostnaam in openid.realm en openid.return_to bij elke aanmelding. Paragraaf 3\nOp 13 juli 2016 heeft Valve het mechanisme bij naam genoemd en verboden, en in de kennisgevingen van zijn raadsman van 20 juli 2016 werd een termijn van tien dagen vastgesteld. In de tien jaar sinds die termijn is er geen handhavingsrapport per exploitant gepubliceerd. Artikel 11\nHet Steam Web API-sleutel-eindpunt verstrekte vóór 2023 een toegangsbewijs met hoge bevoegdheden en de mogelijkheid tot transacties op basis van uitsluitend een sessiecookie, zonder tweede authenticatiefactor. Paragraaf 5\nEen verzoek op grond van artikel 15 van de AVG (ticket HT-2YBP-F7JP-D4VB) werd na drie dagen afgesloten met een link naar de zelfbedieningspagina en zonder gegevens. Artikel 18\nWat we van elke instantie vragen\nKansspelcommissie van de staat Washington\nOpen het dossier uit 2016 opnieuw. Vraag om een overzicht per operator waarin wordt aangegeven welke accounts, bots en return-hosts na de kennisgevingen van tien dagen zijn geblokkeerd, en welke operators later weer toegang hebben gekregen. Paragraaf 2\nHmbBfDI (Hamburg; Valve GmbH)\nGa na of het antwoord op grond van artikel 15 voldeed aan de verplichting van de verwerkingsverantwoordelijke, en eis dat de registratiegegevens van de API-sleutel en de toegangsgegevens die relevant zijn voor de identificatie van de dader, worden verstrekt. Artikel 18\nDSA-coördinatoren voor digitale diensten\nVermeld de auth-host-routing in het verslag als opmerking en beoordeel vervolgens of het antwoord van Valve aan de verplichtingen voldoet zodra de kennis is gedocumenteerd. Artikel 16\nElke betrokkene\nGebruik het sjabloon van artikel 15 om dezelfde gegevens voor je eigen account op te vragen; aan de hand van een bewaard gegeven kan worden nagegaan wie een reset heeft geïnitieerd of een sleutel heeft aangemaakt. Bijlage G\n\nDe enige eis die ten grondslag ligt aan alle vier is dezelfde: maak de gegevens over handhaving, toegang en verwerking openbaar die alleen Valve in bezit heeft. Een waarschuwing op de startpagina, een brief met een termijn van tien dagen en een zelfbedieningspagina zijn uitingen van controle. Of er daadwerkelijk controle is uitgeoefend, is een vraag die het openbare register niet kan beantwoorden, maar een toezichthouder wel.\n\nBijlagen — primaire bewijsstukken en werkmateriaal\nBijlage A — Correspondentie met de raadslieden\nBewijsnota — materiaal verstrekt door Bron 1\n\nBewijsgrondslag en bronvermelding voor de correspondentie van de raadsman waarop in de artikelen 1, 18 en 19 wordt verwezen.\n\nFeitelijke basis en status van de bron — documenten verstrekt door Bron 1\nDe gebruiker wiens definitieve schorsing aanleiding gaf tot deze controle, is niet het onderwerp ervan. Of die schorsing terecht was, wordt hier niet onderzocht, en dit dossier verdedigt noch betwist deze. Het account staat niet ter discussie. Waar het om gaat, is het materiaal: Bron 1 — de houder van het geblokkeerde account, die de onderstaande correspondentie ontving van de raadsman van Valve in zijn hoedanigheid van betrokkene bij zijn eigen AVG-verzoek — heeft die correspondentie en de bijbehorende dossierstukken doorgegeven, samen met het recht om deze openbaar in te zien. De naam wordt niet vermeld; de documenten worden beschreven aan de hand van datum, metadata van de opsteller en hash.\n\nDie correspondentie werd verstuurd naar aanleiding van een verzoek op grond van de AVG/DSAR. In het kader daarvan heeft de raadsman van Valve een ondertekende verklaring in het dossier opgenomen, waarin een functionaliteit wordt beschreven waarvan Steam Support eerder aan gebruikers had meegedeeld dat deze technisch niet haalbaar was. De hieronder geciteerde alinea is die verklaring.\n\nDe verdere analyse door de auteurs van het gegenereerde logboekfragment is niet opgenomen in dit dossier in afwachting van een onafhankelijk onderzoek. Er wordt in geen enkel ander onderdeel van dit onderzoek op een beroep gedaan.\n\nDe officiële verklaring: voortdurende telemetrie op apparaatniveau\n\nIn paragraaf 1.9 van de brief die wordt toegeschreven aan de raadsman van Valve, stellen de advocaten van Valve het volgende: \"Tussen 2019 en 2023 werd dit account voornamelijk gebruikt vanaf een apparaat dat ook werd gebruikt om in te loggen op tientallen gestolen Steam-accounts.\"\n\nHet feit: De raadsman van Valve beschrijft hier een correlatie op apparaatniveau tussen verschillende accounts over een periode van vier jaar. De klantenservice van Steam heeft slachtoffers van diefstal meegedeeld dat het technisch niet mogelijk was om gestolen voorwerpen te traceren of accounts aan apparaten te koppelen. Steam Guard Apparaatautorisatie is openbaar gedocumenteerd, dus het bestaan van gegevens per apparaat is op zich niet nieuw; wat wel nieuw is, is de schriftelijke bevestiging van de raadsman dat die gegevens worden bewaard en over meerdere jaren heen tussen accounts worden gekoppeld.\n\nWaarom dit belangrijk is: De correlatie die één apparaat in verband kan brengen met tientallen gekaapte accounts over een periode van vier jaar, behoort tot dezelfde categorie gegevens die de helpdesk aangaf niet te kunnen gebruiken ten behoeve van de slachtoffers. Gegevens van die categorie zouden het mogelijk maken om accounts en apparaten in een keten van diefstal en doorverkoop te identificeren. Welke gegevens er bestaan, hoe lang ze worden bewaard en op welke gronden ze niet aan de betrokkenen worden verstrekt, zijn vragen voor de toezichthoudende autoriteit.\n\nBron: brief van de raadsman van Valve van 1 oktober 2025, paragraaf 1.9, en de bijlage in PDF-formaat van 830 pagina’s · ontvangen door Bron 1 naar aanleiding van een verzoek op grond van artikel 15 van de AVG · SHA-256 van de bijlage vastgelegd in disclosure-audit.json · de brief zelf wordt niet weergegeven; rekeningnamen en gegevens van derden zijn weggelaten.\n\nStatus: open\nHet bronmateriaal is beschikbaar via het bewijsarchief.\nBijlage B — De gegenereerde PDF · controle op het wegwerken van vertrouwelijke informatie\nDe bewerking in de gegenereerde PDF is louter cosmetisch: de afgedekte tekst kan nog steeds worden geëxtraheerd\n\nDe raadsman van Valve reageerde op een verzoek om inzage op grond van de AVG met een bijlage van 830 pagina’s, waarin de geschrapte passages over de tekst heen zijn geschilderd in plaats van te worden verwijderd. 902,270 tekens bevinden zich onder de zwarte balken en worden direct weergegeven met een tekst-extractietool — inclusief de identificatiegegevens van derden die juist door de streepjes moesten worden verborgen. Hier worden alleen geaggregeerde cijfers gepubliceerd; er wordt geen vertrouwelijke inhoud weergegeven en de bijlage zelf wordt niet gepubliceerd.\n\n1. Wat de geometrische controle aan het licht heeft gebracht\n\nHet antwoord op grond van artikel 15 van de AVG van 1 oktober 2025 werd vergezeld van een PDF-bijlage van 830 pagina’s (metadata van de maker van Aspose.PDF voor .NET, aangemaakt en gewijzigd op dezelfde datum). De auteurs voerden een geometrische controle op paginaniveau uit: voor elke pagina werden ondoorzichtige, bijna zwarte rechthoeken gelokaliseerd die over de tekstlaag waren aangebracht, en werden de eronder liggende, extraheerbare tekens geteld.\n\nGemeten aan de hand van het gegenereerde bestand\n902,270\nTekens die nog steeds onder de zwarte balken vandaan kunnen worden gehaald\nGeteld, niet geschat. Dit is een telling van de betrokken personen — niet van slachtoffers, heridentificaties of incidenten.\n830 / 830\nBetrokken pagina’s — elke pagina\n986\nRechthoeken over uittrekbare tekst\n1,329\nTotaal aantal ondoorzichtige zwarte rechthoeken\nDe zwarte balken worden over de tekstlaag heen getekend; ze verwijderen de tekst niet. Tekst onder de balken kan met standaard PDF-tools worden geëxtraheerd. Alleen totale aantallen worden gepubliceerd; de afgedekte inhoud wordt hier niet weergegeven.\nForensische demonstratie: Scheiding van lagen\nASPOSE.PDF VOOR .NET: MOCK-UP VAN EEN VECTOROVERLAY (BIJLAGE P. 412)\n\nKlacht ingediend tegen account: [INLOGGEN: redacted_user_667]\n\nReden opgegeven door de gebruiker: [TEKST: \"Gebruiker meldt dubbele items in de inventaris en oneerlijk handelsgedrag...\"]\n\nVoorgrond: <path fill=\"#000\" />Tekortkoming: De onderliggende UTF-8-stream is intact\nBron: PDF-bijlage bij de brief van de raadsman van 1 oktober 2025 (830 pagina’s, metadata van de maker van Aspose.PDF voor .NET) · gemeten door de auteurs, methode en aantal per pagina in disclosure-audit.json · De SHA-256-hash van de bijlage die in hetzelfde bestand is opgenomen · de bijlage zelf wordt niet gepubliceerd.\n2. Waarom dit van belang is voor een reactie van de betrokkene\n\nDe raadsman van Valve heeft dit dossier naar een betrokkene gestuurd in reactie op een verzoek om inzage in diens eigen gegevens. De streepjes zijn louter cosmetisch: de tekst eronder is nooit verwijderd, dus de identificatiegegevens van derden die met de streepjes moesten worden verborgen, zijn samen met het bestand bij de ontvanger terechtgekomen. Een redactie die met een tekst-extractietool kan worden opgeheven, verbergt niets en zorgt er bovendien voor dat de ontvanger niet kan vaststellen wat wel en wat niet openbaar is gemaakt.\n\nArtikel 15, lid 4, is de reden waarom die beperkingen überhaupt bestaan: het recht om een kopie te verkrijgen mag geen afbreuk doen aan de rechten en vrijheden van anderen. Aan die verplichting heeft deze productie niet voldaan. Of dit kan worden gekwalificeerd als een inbreuk op persoonsgegevens in de zin van artikel 4, lid 12, is aan de toezichthoudende autoriteit om te bepalen; de openbaarmaking zelf is meetbaar in het bestand en reproduceerbaar door iedereen die over dezelfde bytes beschikt — de SHA-256 is gepubliceerd, de bijlage niet.\n\nWat er onder de streepjes stond, waren geen rekeningnummers. Het betrof de verzameling gebruikersmeldingen die tegen de verzoeker waren ingediend, met de namen van de auteurs erbij: Steam aanmeldingen die, aangezien een aanmelding zelden alleen op Steam wordt gebruikt, de persoon erachter identificeren — volgens de auteurs zijn meer dan 60% van de in het document genoemde gebruikers volledig identificeerbaar — samen met de ruwe, onbewerkte tekst van wat zij hebben geschreven. Die tekst bevat doodsbedreigingen en beledigingen gericht tegen de nationaliteit van de verzoeker. Sommige van de aldus geïdentificeerde personen zijn minderjarigen. De productie heeft een lijst met namen van verslaggevers overhandigd aan de persoon over wie zij verslag hadden gedaan, en dat is precies de schade die artikel 15, lid 4, beoogt te voorkomen.\n\nDe volgorde van de tekens in het bestand is net zo belangrijk als de inhoud ervan. Op het verzoek werd aanvankelijk gereageerd met een eis tot nadere identiteitsbewijzen, met als reden dat het alias-e-mailadres van de verzoeker zijn naam niet bevatte; tijdens de daaropvolgende vertraging werd het account definitief geblokkeerd. In de brief waarin de gegevens uiteindelijk werden verstrekt – meer dan zes weken na de termijn van één maand zoals bedoeld in artikel 12, lid 3 – werd de ontvanger met strafrechtelijke vervolging gedreigd en werd de rest van zijn eigen gegevens achtergehouden totdat hij zijn accountactiviteiten aan de raadsman had toegelicht. De openbaarmaking geeft ook antwoord op twee vragen die Valve niet in het openbaar heeft beantwoord: uit de overgelegde documenten blijkt dat het koppelen van accounts teruggaat tot 2019, en dat er interne telemetrie bestaat van een omvang die Valve nooit heeft beschreven.\n\nToepassingsgebied van dit hoofdstuk: De opmerking hier beperkt zich tot de technische aspecten van de bewerking, zoals vastgesteld aan de hand van het geleverde bestand. De verdere analyse van de geleverde logbestanden door de auteurs wordt achtergehouden in afwachting van een onafhankelijke beoordeling en wordt elders in dit dossier niet als uitgangspunt genomen.\n\nBewijsstuk: brief van de raadsman van 1 oktober 2025 en de bijbehorende PDF-bijlage (SHA-256 vastgelegd in het auditbestand); PDF-metingen op paginaniveau en methode ↗. De volgorde van het verzoek, de afwijzing op pagina 8 en de omschrijving van de openbaar gemaakte documenten worden volledig uiteengezet in het verslag van PhishDestroy, “Mijn hond tegen topadvocaten op het gebied van de AVG”, 17 augustus 2026 ↗ gearchiveerd 2026-08-21 ↗. Accountnamen en gegevens van derden zijn hier weggelaten; er wordt niets weergegeven wat door de streepjes wordt afgedekt.\n\nOp pagina 8 van de begeleidende brief wordt een deel van het verzoek afgewezen, waarbij de reden hiervoor schriftelijk wordt vermeld: Nader informatie is niet mogelijk vanwege de bescherming van de persoonsgegevens van andere gebruikers van het Steam-platform… — Een gedetailleerder antwoord is niet mogelijk, omdat de persoonsgegevens van andere Steam-gebruikers moeten worden beschermd. De bijlage van 830 pagina’s zat in hetzelfde pakket. Wat de streepjes bedekten, waren geen rekeningnummers: het waren de aangiften die tegen de verzoeker waren ingediend, met vermelding van de namen van de opstellers, en met de onbewerkte, niet-geredigeerde berichten in de bijlage. De rekeninghouder had via zijn raadsman Valve om zijn eigen dossier gevraagd; wat hij daaruit kon halen, betrof echter de gegevens van anderen. Niets in deze bijlage draait om de vraag wie de kaders heeft getekend. Wat hieruit blijkt, is dat de bescherming Valve die als grond voor het achterhouden werd aangevoerd, juist de bescherming is die bij dezezelfde overhandiging, in dezelfde envelop, op dezelfde dag niet werd gewaarborgd.\nBijlagen bij ondersteunende documenten en juridische correspondentie\n\nBron: https://phishdestroy.io/steam_dossier/nl/index#exhibit-gallery-section\n\nBijlage D — Verzameling van bronmateriaal\nGeselecteerde primaire bronnen\n\nZes documenten uit het archief — drie GitHub-issues in de trackers van Valve en drie Reddit-berichten over omstreden ondersteuningsresultaten. Elke bron blijft gekoppeld aan de bewering, de opgeslagen tekst en de vraag die hieruit voortvloeit.\n\n1 / 6 geselecteerde records\nKies een bronrecord\nGH-01 / GITHUBOpenen in opgeslagen build\nHardware-sleutels, aangevraagd in 2016\n\nValveSoftware / steam-for-linux · #4521 · 2016-06-27\n\nEen gebruiker heeft Valve gevraagd om ondersteuning voor U2F-hardwaresleutels als alternatieve tweede authenticatiefactor. Het opgeslagen ticket is voorzien van zowel het label ‘Feature Request’ als het label ‘reviewed’, en de status ervan is vastgelegd als ‘open’.\n\nIk vraag om ondersteuning voor een U2F-USB-dongle in Steam als alternatief.\n\nFragment uit de GitHub-issue ↗\nGedocumenteerd verslag\nEen verouderd verzoek om een extra beveiligingsmaatregel voor een account, gepubliceerd in de eigen issue tracker van Valve en gemarkeerd als ’beoordeeld’.\nEis tot verantwoording\nMaak het productbesluit, de reactietermijn en de na beoordeling verleende bescherming bekend.\nOpgeslagen record lezen →GitHub openen ↗\nIn het dossier: Beveiligingsmaatregelen voor accounts →Archief #484 · build 2026-09-17\nGH-02 / GITHUBOpenen in opgeslagen build\nCrash-rapporten zonder effectieve opt-out-mogelijkheid\n\nValveSoftware / steam-for-linux · #6459 · 2019-08-18\n\nDe melder beschrijft een Steam-client van 12 augustus 2019 op Ubuntu 16. Hij of zij meldt dat het uitschakelen van de crash-upload-bestemming na een herstart niet behouden bleef, en voegt de betreffende configuratie toe.\n\nAls ik de `ServerURL` uitschakel, wordt deze na elke herstart overschreven.\n\nFragment uit de GitHub-issue ↗ gearchiveerd 2026-04-19 ↗\nGedocumenteerd verslag\nEen specifieke privacyklacht met de datum van de klant, het besturingssysteem en een uittreksel van de configuratie. Het opgeslagen probleem is nog open.\nEis tot verantwoording\nGeef aan om welk onderzoek het gaat, welke builds hierdoor zijn getroffen en welke wijziging ervoor heeft gezorgd dat de opt-out van kracht is geworden.\nOpgeslagen record lezen →GitHub openen ↗gearchiveerd 2026-04-19 ↗\nIn het dossier: De bijbehorende documenten opvragen →Archief #467 · build 2026-09-17\nGH-03 / GITHUBOpenen in opgeslagen build\nMisbruik van authenticatietickets gemeld aan Valve\n\nValveSoftware / Source-1-Games · #3857 · 2022-02-26\n\nDe auteur beweert dat een serverbeheerder Steam authenticatietickets heeft behouden nadat spelers de verbinding hadden verbroken en misleidende serverlijsten heeft gebruikt. In het bericht wordt Valve gevraagd om dit gedrag aan te pakken.\n\nZorgen dat hun servers er vol uitzien.\n\nFragment uit de GitHub-issue ↗\nGedocumenteerd verslag\nEen openbare melding van misbruik die op 26 februari 2022 is ingediend in de tracker van Valve. De opgeslagen status is ‘open’; de melding bevat links naar schermafbeeldingen.\nEis tot verantwoording\nStel het onderzoeksrapport en het verslag van de corrigerende maatregelen op met betrekking tot het gemelde misbruik van authenticatietickets.\nOpgeslagen record lezen →GitHub openen ↗\nIn het dossier: Reikwijdte van de dataset →Archief #768 · build 2026-09-17\nRD-01 / REDDITProfiel van de auteur\n44 betwiste aankopen op de markt\n\nr/DotA2 · gebruikersnaam niet bekendgemaakt · 2022-07-07\n\nDe auteur meldt 44 ongeautoriseerde aankopen op de Market op 6 juli 2022 en een verlies van ongeveer $500+. Hij/zij geeft aan dat tweefactorauthenticatie was ingeschakeld en beschrijft herhaaldelijke standaardantwoorden van de klantenservice.\n\nDit is mijn tweede ticket en ik heb nog steeds geen antwoord van Steam ontvangen dat niet uit een standaardkopie-en-plak-sjabloon komt.\n\nFragment uit het Reddit-bericht ↗ gearchiveerd 2025-03-20 ↗\nGedocumenteerd verslag\nEen verslag met datums van betwiste aankopen, met links naar schermafbeeldingen van de transacties en een reactie van de klantenservice. De bedragen en gebeurtenissen zijn afkomstig uit het verslag van de auteur.\nEis tot verantwoording\nControleer de betwiste aankopen aan de hand van transactie- en sessielogboeken. Leg uit op basis van welk bewijsmateriaal de beslissing van de helpdesk is genomen.\nOpgeslagen record lezen →Reddit openen ↗gearchiveerd 2025-03-20 ↗\nIn het dossier: Ondersteuning en handhaving →Archief #4,533 · build 2026-09-17\nRD-02 / REDDITProfiel van de auteur\nEen definitieve uitsluiting en gesloten beroepsprocedures\n\nr/ohnePixel · naam van de auteur niet bekendgemaakt · 2024-12-09\n\nDe auteur betwist dat er sprake is van een permanente uitsluiting en zegt dat de aangevoerde redenen betrekking hadden op een vermoedelijke accountoverdracht en meldingen vanuit de community. Hij beschrijft afgesloten tickets en plannen om zijn persoonsgegevens op te vragen.\n\nIk heb mijn situatie uitgelegd en om meer informatie gevraagd, maar ze blijven bij hun besluit en sluiten mijn tickets.\n\nFragment uit het Reddit-bericht ↗\nGedocumenteerd verslag\nEen bewaard gebleven beroepsprofiel, inclusief de redenen die volgens de auteur de geleverde ondersteuning rechtvaardigen en links naar vier afbeeldingen. De publicatiedatum is afkomstig uit de geselecteerde export van de ondersteuning.\nEis tot verantwoording\nGeef aan op basis van welke bewijzen het permanente verbod is ingesteld en welke beroepsmogelijkheden er zijn om dit aan te vechten. Het afsluiten van een beroepsprocedure vormt geen toelichting op het besluit.\nOpgeslagen record lezen →Reddit openen ↗\nIn het dossier: De onderliggende documenten opvragen →Archief #4,766 · build 2026-09-17\nRD-03 / REDDITProfiel van de auteur\nEen herstelreset en een gemeld verlies van $10,000\n\nr/legaladvice · naam van de auteur niet bekendgemaakt · 2025-05-09\n\nDe auteur beweert dat de klantenservice de inloggegevens heeft gereset en de beveiliging van het account heeft uitgeschakeld nadat iemand anders een herstelverzoek had ingediend. Hij meldt een verlies van ongeveer US$10,000 van een inactieve rekening.\n\nSteam De klantenservice heeft mijn wachtwoord gereset en alle beveiligingsinstellingen van mijn account uitgeschakeld.\n\nFragment uit het Reddit-bericht ↗\nGedocumenteerd verslag\nEen bewaarde bewering dat het herstelproces de beveiligingsmaatregelen van het account terzijde schoof. In het opgeslagen bericht staat wat de auteur zegt dat de klantenservice hem heeft verteld.\nEis tot verantwoording\nGeef aan wie toestemming heeft gegeven voor het resetten, welk bewijs van eigendom is geaccepteerd en wat het toegangslogboek is. Het herstellen van een account maakt deel uit van de Valve-beveiligingsmaatregelen.\nOpgeslagen record lezen →Reddit openen ↗\nIn het dossier: De onderliggende documenten opvragen →Archief #4,592 · build 2026-09-17\n\nZes geselecteerde records. GitHub-beschrijvingen geven informatie over de opgeslagen build. Reddit-berichten bevatten de verslagen van de auteurs.\n\nDownload de zes opnames ↓\n\nDe doorzoekbare build bevat 16,319 unieke records: 393 Trustpilot, 5,635 Reddit, 2,395 GitHub, 276 webvermeldingen en 7,620 wikivermeldingen. Meerdere vermeldingen kunnen betrekking hebben op dezelfde gebeurtenis. De afzonderlijke master-export met 40,448 rijen heeft een andere reikwijdte.\n\nZoek in het volledige archief ↗ · Manifest samenstellen ↗ · Omvang en aantallen van de dataset →\n\nBijlage E — Casestudie\nArchiSteamFarm en de automatiseringsclausule\n\nEen open-sourceprogramma voor het verzamelen van kaarten, waarvan in de eigen FAQ wordt vermeld dat het op miljoenen accounts draait, wat in strijd is met de clausule (§ 4.C) van de abonneeovereenkomst die automatisering verbiedt. De werkwijze — wat een farm bij Valve moet kopen voordat deze iets kan produceren, waarom elke manier om een kaart te verzilveren in strijd is met de licentie, de handhavingsgeschiedenis en wie toezicht houdt op de kaarteconomie — wordt volledig uiteengezet in Bijlage V ↗.\n\nIn de Steam-abonnementsovereenkomst, § 4.C, staat het volgende:\n\n\"Het is niet toegestaan om op welke manier dan ook gebruik te maken van scripts, bots, macro's of andere niet door mensen bestuurde systemen ('automatisering') om interactie te hebben met de inhoud en diensten op Steam.\" — Steam Abonnementsovereenkomst § 4.C (huidige versie) ↗ gearchiveerd 2026-09-18 ↗\n\nValve zorgt ervoor dat deze clausule wordt nageleefd. Daar is het erg goed in. De veelgestelde vragen van ArchiSteamFarm (ASF) — een open-sourceprogramma dat volgens de eigen documentatie draait op meer dan een paar miljoen Steam-accounts sinds de eerste release ruim 11 jaar geleden — geeft drie Steam-berichten van de ondersteuning weer waarin gebruikers die botnetwerken beheerden definitief werden geblokkeerd. Valve ontdekte de netwerken, benoemde ze en schakelde ze uit. De relevante vraag is daarom niet of Valve automatisering op grote schaal kan detecteren.\n\nDe officiële website van het project ArchiSteamFarm Veelgestelde vragen gaat rechtstreeks in op het risico van een verbod:\n\n\"Dit is uiterst onwaarschijnlijk, gezien het feit dat ASF al sinds de eerste release, meer dan 11 jaar geleden, op meer dan een paar miljoen Steam-accounts wordt gebruikt — maar het blijft een mogelijkheid, ongeacht de daadwerkelijke waarschijnlijkheid.\"\n\n\"Valve erkent duidelijk dat er 'Steam nietsnutten' bestaan, zoals hier wordt vermeld, dus als je het mij vraagt, ben ik er vrij zeker van dat als ze daar een probleem mee hadden, ze al iets zouden hebben ondernomen in plaats van erop te wijzen dat ze problemen zouden kunnen veroorzaken op het gebied van VAC. Het sleutelwoord hier is Steam idlers, bijvoorbeeld ASF, en niet game-idlers.\"\n\n— ArchiSteamFarm Veelgestelde vragen, JustArchiNET. Bron: GitHub-wiki ↗ · woordelijk geverifieerd 2026-09-22\n\nIn dezelfde FAQ wordt de vraag „Is er iemand hiervoor geblokkeerd?“ beantwoord met Ja, en geeft weer wat Steam Support aan drie van hen schreef:\n\n1,000+ bots · handelsverbod\n\"Het lijkt erop dat dit account is gebruikt om een netwerk van botaccounts te beheren. Het gebruik van bots is in strijd met de Steam-abonneeovereenkomst.\"\n\nMeer dan 170 bots · definitief geblokkeerd, Winteruitverkoop 2017\n\"Dit account werd gebruikt om op Steam op illegale wijze verzamelkaarten te verzamelen, evenals aanverwante en niet uitsluitend commerciële activiteiten. Het account is definitief geblokkeerd en Steam Support kan geen verdere ondersteuning bieden met betrekking tot deze kwestie.\"\n\nMeer dan 120 bots · definitief geblokkeerd\n\"Dit en andere accounts werden gebruikt om onze netwerkinfrastructuur te overbelasten, wat in strijd is met Steam van de gedragsregels online.\"\n\n— Steam Steunbetuigingen die zijn opgenomen in de ArchiSteamFarm FAQ, onder het kopje „Is er iemand hiervoor geblokkeerd?”. Bron ↗ · woordelijk geverifieerd 2026-09-22\n\nLeg de twee documenten naast elkaar. Een particuliere gebruiker met 1,000 farming-bots wordt geïdentificeerd, krijgt te horen dat „botting een schending is van de Steam abonneeovereenkomst” en wordt definitief verwijderd. De commerciële platforms in dit dossier hebben geautomatiseerde Steam-accounts als hun kernactiviteit, op veel grotere schaal, en verifiëren bij elke aanmelding via Valve's eigen OpenID — en voor geen van hen is er een handhavingsrapport per exploitant gepubliceerd. De clausule werkt. De vraag is tegen wie ze gericht is.\n\nASF wordt hier nergens van beschuldigd, en de interpretatie van het standpunt van Valve is die van ASF zelf — de auteur stelt duidelijk dat „ASF geen toestemming heeft van Valve”. De tool wordt hier als meetinstrument gebruikt: hieruit blijkt dat Valve botnetwerken opspoort, deze schriftelijk bij naam noemt en ze permanent verbant. Valve kan de kwestie in één zin afsluiten door bekend te maken welke commerciële automatisering het toestaat, en per operator bij te houden wat het met de rest heeft gedaan.\n\nWaar het verzamelen van kaarten invloed heeft op de inkomsten van Valve\n\nVerzamelkaarten die in het spel zijn verkregen, worden verkocht op de Steam Community Market, die voor elke voltooide verkoop binnen de Market een totale vergoeding van ongeveer 15% in rekening brengt; het account moet $5.00 USD aan Steam hebben uitgegeven voordat het überhaupt een kaart kan ontvangen; en voor het ontvangen van kaarten is het bezit van het spel of in-game aankopen vereist. Er wordt hier geen schatting gemaakt van de totale omzet — de omvang van de activiteiten wordt uitsluitend vermeld zoals deze in de ASF-FAQ staat. De FAQ vermeldt ook Valve onderscheidende \"Steam luilakken\" (kaarten verzamelen) uit \"spelverslaafden\"; zie de Veelgestelde vragen over ASF ↗. De werkwijze wordt volledig beschreven in Bijlage V — de schaal en de valkuil van commercieel gebruik.\n\nOnderwerpArchiSteamFarm — geautomatiseerd verzamelen van kaarten\nAangegeven schaalMiljoenen accounts (volgens de ASF-FAQ — het exacte aantal actieve accounts is niet geverifieerd)\nGeteld, niet geciteerd10,880,610 API-vermeldingen in totaal in de eigen Steam-groep van ASF (5,360,499 onbeperkt, zoals Steam laat zien) — de „miljoenen” in de FAQ zijn geen verhaal, maar een telling. 88.97% zijn op geen enkele wijze Steam verboden. Het volledige overzicht van de verboden ↗\nInformatie in de documentatie van de tool zelf\nASF logt accounts in via de commandoregel en laat games op stand-by staan om kaarten te verzamelen, zonder de Steam-client te starten (volgens de projectdocumentatie).\nIn de FAQ wordt gesteld dat Valve op de hoogte is van de \"Steam-luilakken\" en dat \"als ze daar een probleem mee hadden, ze allang iets zouden hebben ondernomen\".\nEr is al meer dan 11 jaar geen gerichte handhaving gemeld (volgens de FAQ); de daaruit voortvloeiende kaartverkopen binnen de Community Market brengen Steam's totale vergoeding van ongeveer 15% met zich mee.\nIn de FAQ wordt een aanbevolen maximum van tien accounts per gebruiker genoemd, waarbij de bron Valve wordt aangehaald: \"Deze aanbeveling is gebaseerd op interne Valve-richtlijnen en op onze eigen suggesties.\" Een dergelijke richtlijn is niet gepubliceerd door Valve.\nTechnische limiet, volgens dezelfde FAQ: \"Je kunt maximaal 100 tot 200 bots draaien met één IP-adres en één ASF-instantie.\"\nDe gespeelde speeltijd wordt bijgehouden door Valve — „dit wordt doorgaans om de ongeveer 30 minuten bijgewerkt“ — en in § 4.C wordt „het vervalsen van gameplay-statistieken (bijv. opgeblazen winst- of verliescijfers, XP, speeltijd)“ vermeld als een verboden handeling.\nBronnen\nOfficiële JustArchi ASF FAQ-wiki ↗ ArchiSteamFarm opslagplaats ↗ gearchiveerd 2026-09-24 ↗\nDe automatiseringsclausule is duidelijk; in de FAQ van de ASF staat al jaren vermeld dat de tool op miljoenen accounts draait; er zijn geen meldingen van gerichte handhavingsmaatregelen hiertegen. De kloof tussen de regel en de toepassing ervan is een vaststaand feit; de reden hiervoor wordt hier niet nader toegelicht.\nVolledige tentoonstellingDe kaarteconomie: het proces, de omvang, de vergunning en wie hier toezicht op houdt ↗Wat een boerderij bij Valve moet kopen voordat ze ook maar één kaart kan produceren; de twee regels van § 4.C die het kweken van kaarten omschrijven aan de hand van de gevolgen ervan; waarom elke manier om een kaart te verzilveren in strijd is met de licentie die Valve heeft opgesteld, terwijl Valve een vergoeding vraagt bij de ingang; het handhavingsverslag, inclusief de VAC-golf van juni 2025 en het ketenverbod op basis van gedeelde telefoonnummers; en de Valve-medewerkers en communitymoderators die de kaartverhandelings- en banlijstdiensten rond Steam beheerden.De telling van de verbodenWe hebben Valve niet gevraagd hoe groot de boerderij is. We hebben het geteld. ↗10,880,610 totale accounts (beperkt en onbeperkt) gelezen uit de eigen Steam-groep van ArchiSteamFarm, waar de software standaard bij de eerste start automatisch lid van wordt, tenzij de gebruiker de instelling voor het lid worden van de groep uitschakelt (waarbij zowel commerciële botfarms als reguliere spelers worden meegeteld die de standaardinstelling hebben laten staan). 88.97% hebben geen enkele vorm van Steam-ban; van de 11% die dat wel hebben, zijn 99.8% cosmetische community-bans die de handel nooit verhinderen. Na kruiscontrole met SteamRep komen 67.77% van de genoemde oplichters ermee weg zodra de anti-cheat-verboden buiten beschouwing worden gelaten. Met uitsplitsingen op registratiedatum, geografie en overlevingspercentages — de werkelijke omvang, gemeten, niet alleen beschreven.\n\nAppendix F — Working ledger\n\nRules ledger: clauses against recorded platforms\n\nKies een regel; het register geeft een overzicht van de geregistreerde platforms die onder die regel zijn getagd, met hun hoofddomein, de opgegeven authenticatiehost en het opgeslagen resultaat van de linkfilter. Een geblokkeerde website, een ander domein om in te loggen: volg de regel tot aan de route die overblijft.\n\n175gekoppelde records\naan deze regel\n174 primaire domeinen0 Vermeldingen in C&D\nUITTREKSEL UIT DE REGELGEVING / SSA § 2.G\nCommercieel gebruik en facturering van accounts\n“…exploit the Content and Services or any of its parts for any commercial purpose, except as expressly permitted elsewhere in this Agreement (including any Subscription Terms or Rules of Use).”\nVOLG DE RECORDS\nPlatformregister 175\nDe cijfers in schaalvorm zijn schattingen op basis van bronnen\n\n175 van de gegevens op 175\n\nDienst / moedermaatschappij\tHoofddomein / registratie-instantie\tWaargenomen authenticatiedomein / leeftijd\tSchaal / geregistreerde reactie\n\nCasino\n\tcsgoempire.com\n11.3 yearsRegistered 2015-06-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgoempirelogin4.com\n6.2 yearsRegistered 2020-07-20\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustreaper.com\n23.2 yearsRegistered 2003-06-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustreaper.com\n23.2 yearsRegistered 2003-06-24\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustly.com\n12.4 yearsRegistered 2014-05-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustly.com\n12.4 yearsRegistered 2014-05-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette Casino\n\tcsgofast.com\n11.5 yearsRegistered 2015-03-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsteam-login.authtofast.com\n83 daysRegistered 2026-06-30\nRDAP ↗ · authtofast.com (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tduelbits.com\n6.6 yearsRegistered 2020-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nswitchflips.com\n6.4 yearsRegistered 2020-04-21\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opener\n\tfarmskins.com\n10.5 yearsRegistered 2016-03-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsteam.kobal.cc\n9.7 yearsRegistered 2017-01-07\nRDAP ↗ · kobal.cc (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgoluck.com\n9.3 yearsRegistered 2017-05-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgoluck.com\n9.3 yearsRegistered 2017-05-18\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tinsane.gg\n7.5 yearsRegistered 2019-04-02\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.insane.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcs2skin.com\n3.5 yearsRegistered 2023-03-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncs2skin.com\n3.5 yearsRegistered 2023-03-06\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tjuice.gg\n7.9 yearsRegistered 2018-10-19\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nletmeinjuice.com\n2.4 yearsRegistered 2024-04-15\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tggdrop.com\n8.6 yearsRegistered 2018-02-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nggauth.com\n3.4 yearsRegistered 2023-05-03\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Casino\n\thowl.gg\n9.5 yearsRegistered 2017-03-16\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhowl.uno\n41 daysRegistered 2026-08-11\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tchicken.gg\n5.7 yearsRegistered 2021-01-11\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nchicken.gg\n5.7 yearsRegistered 2021-01-11\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgocasino.gg\n2.6 yearsRegistered 2024-02-17\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.csgocasino.gg\n2.6 yearsRegistered 2024-02-17\nWHOISFREAKS ↗ · csgocasino.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Casino\n\thunt.gg\n6.9 yearsRegistered 2019-11-04\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.hunt.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Battles\n\tcsbattle.com\n9.8 yearsRegistered 2016-12-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsbattle.com\n9.8 yearsRegistered 2016-12-10\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskinrave.gg\n3.1 yearsRegistered 2023-08-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinrave.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsdouble.gg\n261 daysRegistered 2026-01-03\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsdouble.gg\n261 daysRegistered 2026-01-03\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustchance.com\n8.0 yearsRegistered 2018-10-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhgfuihd.com\n7.6 yearsRegistered 2019-01-27\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Automation\n\tcobaltlab.tech\n3.5 yearsRegistered 2023-03-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncobaltauth.com\n1.7 yearsRegistered 2025-01-07\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\traided.gg\n171 daysRegistered 2026-04-03\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.raided.gg\n171 daysRegistered 2026-04-03\nIP2WHOIS ↗ · raided.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustneo.gg\n1.3 yearsRegistered 2025-06-20\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustneo.gg\n1.3 yearsRegistered 2025-06-20\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tsplits.gg\n3.7 yearsRegistered 2023-01-23\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsplits.gg\n3.7 yearsRegistered 2023-01-23\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Upgrader\n\tupgrader.pro\n1.2 yearsRegistered 2025-07-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nupgauth.space\n38 daysRegistered 2026-08-14\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskin.fans\n8.2 yearsRegistered 2018-07-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skinfans.com\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\thotpizza.one\n1.8 yearsRegistered 2024-12-07\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhotpizza.one\n1.8 yearsRegistered 2024-12-07\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tg4skins.com\n10.1 yearsRegistered 2016-08-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.g4s.to\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2royal.com\n4.1 yearsRegistered 2022-08-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ntf2auth.com\n5.2 yearsRegistered 2021-07-27\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2hunt.com\n8.7 yearsRegistered 2018-01-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrstspcl.com\n6.1 yearsRegistered 2020-08-08\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2.bet/coinflip\n8.4 yearsRegistered 2018-05-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ntf2.bet\n8.4 yearsRegistered 2018-05-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\topenstars.gg\n131 daysRegistered 2026-05-13\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nopenstars.gg\n131 daysRegistered 2026-05-13\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tskins.com\n25.1 yearsRegistered 2001-08-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skins.com\n25.1 yearsRegistered 2001-08-08\nRDAP ↗ · skins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\twhite.market\n9.6 yearsRegistered 2017-03-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwhite.market\n9.6 yearsRegistered 2017-03-01\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tmoon.market\n7.6 yearsRegistered 2019-02-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmoon.market\n7.6 yearsRegistered 2019-02-27\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tcsfloat.com\n5.2 yearsRegistered 2021-07-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgofloat.com\n11.0 yearsRegistered 2015-09-29\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tskin.land\n4.7 yearsRegistered 2022-01-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skin.land\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\thaloskins.com\n2.8 yearsRegistered 2023-12-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhaloskins.com\n2.8 yearsRegistered 2023-12-10\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCorporate Market\n\tbuff.163.com\n29.0 yearsRegistered 1997-09-15\nRDAP ↗ · 163.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\nbuff.163.com\n29.0 yearsRegistered 1997-09-15\nRDAP ↗ · 163.com (parent)\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\tmarket.csgo.com\n26.6 yearsRegistered 2000-02-07\nRDAP ↗ · csgo.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\ndota2.net\n14.9 yearsRegistered 2011-10-29\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRegulated Market\n\tskinport.com\n8.0 yearsRegistered 2018-09-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinport.app\n6.3 yearsRegistered 2020-06-20\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMarketplace/Swap\n\tskinflow.gg\n3.8 yearsRegistered 2022-11-26\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinflow.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tskin.place\n6.0 yearsRegistered 2020-09-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skin.place\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tskinsmonkey.com\n5.7 yearsRegistered 2021-01-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinsmonkey.com\n5.7 yearsRegistered 2021-01-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCorporate Market\n\tskinbaron.de\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinbaron.com\n10.7 yearsRegistered 2015-12-22\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Market\n\trust.tm\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\ndota2.net\n14.9 yearsRegistered 2011-10-29\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tpirateswap.com\n6.0 yearsRegistered 2020-09-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nlogin.pirateswap.com\n6.0 yearsRegistered 2020-09-22\nRDAP ↗ · pirateswap.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Marketplace\n\tmannco.store\n8.6 yearsRegistered 2018-03-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmannco.store\n8.6 yearsRegistered 2018-03-02\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tskinswap.com\n9.9 yearsRegistered 2016-11-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinswap.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\texeskins.com\n2.1 yearsRegistered 2024-08-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nexeskins.com\n2.1 yearsRegistered 2024-08-14\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tbalticskins.com\n153 daysRegistered 2026-04-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nbalticskins.com\n153 daysRegistered 2026-04-21\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tcs.trade\n8.9 yearsRegistered 2017-11-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncs.trade\n8.9 yearsRegistered 2017-11-14\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\trapidskins.com\n4.5 yearsRegistered 2022-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.rapidskins.com\n4.5 yearsRegistered 2022-03-11\nRDAP ↗ · rapidskins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\ttradeit.gg\n9.1 yearsRegistered 2017-08-21\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nconnect-tradeit.com\n4.6 yearsRegistered 2022-02-23\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\t49skins.com\n3.4 yearsRegistered 2023-04-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.49skins.com\n3.4 yearsRegistered 2023-04-19\nRDAP ↗ · 49skins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tskinvault.gg\n3.4 yearsRegistered 2023-05-06\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinvault.gg\n3.4 yearsRegistered 2023-05-06\nIP2WHOIS ↗ · skinvault.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Trading\n\taim.market\n3.3 yearsRegistered 2023-05-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\naim.market\n3.3 yearsRegistered 2023-05-22\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Sell Portal\n\tskinout.gg\n5.6 yearsRegistered 2021-02-27\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skinout.gg\n5.6 yearsRegistered 2021-02-27\nIP2WHOIS ↗ · skinout.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Trading\n\tntskins.com\n230 daysRegistered 2026-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nntskins.com\n230 daysRegistered 2026-02-03\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Portal\n\tgamerpay.gg\n6.0 yearsRegistered 2020-10-02\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ngamerpay.gg\n6.0 yearsRegistered 2020-10-02\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Scrap Swap\n\tscrap.tf\n14.0 yearsRegistered 2012-09-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nscrap.tf\n14.0 yearsRegistered 2012-09-03\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Cashout\n\tmarketplace.tf\n14.0 yearsRegistered 2012-09-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmarketplace.tf\n14.0 yearsRegistered 2012-09-19\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Cashout\n\tskins.cash\n10.5 yearsRegistered 2016-03-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinscash.live\n6.8 yearsRegistered 2019-12-05\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgo.net\n14.2 yearsRegistered 2012-07-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncn2.easylot.net\n10.0 yearsRegistered 2016-09-03\nRDAP ↗ · easylot.net (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCommunity Hub\n\tcybershoke.net\n6.8 yearsRegistered 2019-11-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.cybershoke.net\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMatchmaker Hub\n\tfastcup.net\n14.6 yearsRegistered 2012-02-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.fastcup.net\n14.6 yearsRegistered 2012-02-16\nRDAP ↗ · fastcup.net (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Analytics\n\tleetify.com\n7.6 yearsRegistered 2019-03-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nleetify.com\n7.6 yearsRegistered 2019-03-01\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Analytics\n\tscope.gg\n7.8 yearsRegistered 2018-12-10\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nscope.gg\n7.8 yearsRegistered 2018-12-10\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tools\n\ttradeupspy.com\n6.5 yearsRegistered 2020-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.tradeupspy.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMarketplace\n\tcs.deals\n9.8 yearsRegistered 2016-12-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.cs.deals\n9.8 yearsRegistered 2016-12-03\nRDAP ↗ · cs.deals (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Price DB\n\tpricempire.com\n6.6 yearsRegistered 2020-01-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\npricempire.com\n6.6 yearsRegistered 2020-01-30\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Blackmarket\n\tFSB Market\n7.2 yearsRegistered 2019-07-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nFSB Market\n7.2 yearsRegistered 2019-07-27\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nReady-Account Hub\n\tz2u.com\n26.9 yearsRegistered 1999-11-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwww.z2u.com\n26.9 yearsRegistered 1999-11-10\nRDAP ↗ · z2u.com (parent)\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Gambling\n\tcsgoroll.com\n11.6 yearsRegistered 2015-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwww.csgoroll.com\nRegistry date unavailableRegistry date unavailable\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\trollbit.com\n11.9 yearsRegistered 2014-11-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrbsnin.com\n3 daysRegistered 2026-09-18\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nLicenced Casino\n\t500.casino\n5.9 yearsRegistered 2020-11-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette/Slots\n\tcsgobig.com\n11.4 yearsRegistered 2015-04-12\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcasedrop.com\n14.8 yearsRegistered 2011-12-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\tbanditcamp.com\n12.2 yearsRegistered 2014-06-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tskinbox.com\n18.8 yearsRegistered 2007-12-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\ttastydrop.com\n6.1 yearsRegistered 2020-08-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette Casino\n\tcsgopolygon.gg\n6.5 yearsRegistered 2020-03-28\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tmagicdrop.ru\n10.3 yearsRegistered 2016-05-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nDice Casino\n\tcsdice.com\n3.8 yearsRegistered 2022-11-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUpgrader Casino\n\tskinodds.com\n1.2 yearsRegistered 2025-06-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgowin.com\n12.0 yearsRegistered 2014-09-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrash Casino\n\tcsgorun.net\n7.3 yearsRegistered 2019-06-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\topenskins.com\n3.6 yearsRegistered 2023-02-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Gambling\n\trustbet.com\n7.6 yearsRegistered 2019-02-07\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgomagic.com\n9.4 yearsRegistered 2017-05-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUpgrader/Contract\n\tcsgobounty.com\n11.5 yearsRegistered 2015-03-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tezskins.com\n27.5 yearsRegistered 1999-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\trustcases.com\n7.2 yearsRegistered 2019-06-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgoreaper.com\n11.1 yearsRegistered 2015-08-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgocases.com\n12.3 yearsRegistered 2014-06-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Upgrader\n\tcsgo-skins.com\n11.2 yearsRegistered 2015-07-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgonet.com\n8.8 yearsRegistered 2017-12-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\twtfskins.com\n9.0 yearsRegistered 2017-10-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Casino\n\tflamecases.com\n10.0 yearsRegistered 2016-09-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tgamedom.com\n11.7 yearsRegistered 2015-01-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Battles\n\tskin.club\n9.0 yearsRegistered 2017-09-04\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsc-auth.net\n7.5 yearsRegistered 2019-04-02\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tdaddyskins.com\n9.9 yearsRegistered 2016-10-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Gambling\n\trustix.gg\n1.7 yearsRegistered 2025-01-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Upgrade\n\tskins.club\n4.2 yearsRegistered 2022-07-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgohouse.org\n146 daysRegistered 2026-04-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskinrave.net\n216 daysRegistered 2026-02-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tbloodycase.gg\n19 daysRegistered 2026-09-02\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nClicker/Upgrade\n\tcsgoclicker.com\n8.3 yearsRegistered 2018-05-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustbet.gg\n4.0 yearsRegistered 2022-09-30\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcs-drop.com\n262 daysRegistered 2026-01-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\thellstore.net\n11.7 yearsRegistered 2015-01-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustloot.com\n354 daysRegistered 2025-10-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgo-case.com\n10.3 yearsRegistered 2016-05-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgogem.com\n9.9 yearsRegistered 2016-10-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\trainbet.com\n8.8 yearsRegistered 2017-11-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nservices.rainbet.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustclash.com\n5.4 yearsRegistered 2021-05-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrash Casino\n\t12cs.fail\n181 daysRegistered 2026-03-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\twww.tf2easy.com\n6.3 yearsRegistered 2020-06-02\nRDAP ↗ · tf2easy.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2blaze.com\n7.6 yearsRegistered 2019-01-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tshuffle.com\n30.1 yearsRegistered 1996-07-31\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tbuff.market\n5.9 yearsRegistered 2020-10-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tavan.market\n8.3 yearsRegistered 2018-05-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Engine\n\tcs.money\n11.0 yearsRegistered 2015-09-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.dota.trade\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tuuskins.com\n2.6 yearsRegistered 2024-01-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Market\n\tyoupin898.com\n6.1 yearsRegistered 2020-08-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tc5game.com\n10.5 yearsRegistered 2016-03-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\twaxpeer.com\n7.3 yearsRegistered 2019-05-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwaxpeer.com\n7.3 yearsRegistered 2019-05-20\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBot Trading\n\tcs.money\n11.0 yearsRegistered 2015-09-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.dota.trade\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUS Marketplace\n\tdmarket.com\n30.2 yearsRegistered 1996-07-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nOfficial Market\n\tsteamcommunity.com/market\n20.3 yearsRegistered 2006-05-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNot an external login site2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Platform\n\tlootfarm.com\n11.9 yearsRegistered 2014-10-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Market\n\trustskins.com\n7.6 yearsRegistered 2019-01-31\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tkrakatoa.com\n26.4 yearsRegistered 2000-05-15\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\tshadowpay.com\n10.1 yearsRegistered 2016-08-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nChinese Powerhouse\n\tigxe.cn\n15.0 yearsRegistered 2011-09-06\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAutomated Swap\n\tswap.gg\n9.6 yearsRegistered 2017-01-29\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCash-out Portal\n\tbitskins.com\n11.2 yearsRegistered 2015-07-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Automation\n\ttf2mart.com\n1.1 yearsRegistered 2025-08-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Auctions\n\tskinbid.com\n10.2 yearsRegistered 2016-06-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Rental\n\tlootbear.com\n8.7 yearsRegistered 2018-01-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Valuation\n\tbackpack.tf\n14.4 yearsRegistered 2012-05-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Botnet\n\tstntrading.eu\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Cashout\n\tskinwallet.com\n18.0 yearsRegistered 2008-09-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nDota 2 Market\n\tdota2market.com\n12.2 yearsRegistered 2014-07-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nServer Network\n\txplay.gg\n5.3 yearsRegistered 2021-06-13\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMatchmaking Portal\n\tesportal.com\n26.8 yearsRegistered 1999-12-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nLATAM Hub\n\tgamersclub.com.br\n11.2 yearsRegistered 2015-06-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tools\n\tepidemic.gg\n4.9 yearsRegistered 2021-11-03\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tcs2stash.com\n3.5 yearsRegistered 2023-03-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tcsgoskins.gg\n6.8 yearsRegistered 2019-12-21\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tsteamanalyst.com\n12.6 yearsRegistered 2014-02-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Exchange\n\tsteamcardexchange.net\n13.3 yearsRegistered 2013-05-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tracker\n\tdotabuff.com\n14.2 yearsRegistered 2012-06-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tracker\n\ttracker.gg\n8.9 yearsRegistered 2017-10-12\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Exchange\n\tfunpay.com\n17.0 yearsRegistered 2009-09-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nGrey Market\n\tplayerauctions.com\n26.3 yearsRegistered 2000-06-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Portal\n\teldorado.gg\n8.0 yearsRegistered 2018-09-12\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Key Market\n\tg2a.com\n24.8 yearsRegistered 2001-12-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Key Market\n\tkinguin.net\n16.8 yearsRegistered 2009-12-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nVirtual Services\n\tg2g.com\n31.1 yearsRegistered 1995-08-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Broker\n\tplayerup.com\n19.3 yearsRegistered 2007-05-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfhub.net\n2.7 yearsRegistered 2023-12-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfaccounts.com\n5.3 yearsRegistered 2021-05-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Shop\n\tbuycsgorank.com\n6.2 yearsRegistered 2020-07-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tcsgosmurfkings.com\n9.3 yearsRegistered 2017-06-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfstore.co\n8.6 yearsRegistered 2018-03-03\nWHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlvlup.com\n9.9 yearsRegistered 2016-11-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlevels.com\n10.6 yearsRegistered 2016-02-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tlevelsteam.com\n79 daysRegistered 2026-07-04\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlevelu.com\n6.0 yearsRegistered 2020-09-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\teloking.com\n12.2 yearsRegistered 2014-07-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\tboosteria.org\n11.9 yearsRegistered 2014-10-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tovergear.com\n14.4 yearsRegistered 2012-04-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tblazingboost.com\n14.2 yearsRegistered 2012-06-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\tdota2boost.com\n2.9 yearsRegistered 2023-10-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tbuyboost.com\n22.4 yearsRegistered 2004-04-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\nDe redenering van het onderzoekGeselecteerde regel / analyse en toelichting+\nBewijslast\n\nHet onderzoek wijst op de kloof tussen de beperkingen op commercieel gebruik en de diensten die hier zijn geregistreerd. Classificeer elke activiteit en ga na of er sprake is van uitdrukkelijke toestemming, voordat u het als een contractbreuk bestempelt. De tarieven van de Community Market zijn niet van toepassing op alle externe handel.\n\nWat een gelabeld record wel en niet is\n\nEen vermelding wordt gemarkeerd wanneer het dossier een gedateerde opmerking bevat waardoor het platform op het eerste gezicht onder de betreffende clausule valt. Een markering is geen vastgestelde overtreding, en er is voor geen enkel hier vermeld platform een uitdrukkelijke Valve vergunning in het dossier opgenomen. Wanneer een platform over een vergunning beschikt, wordt de vermelding verwijderd zodra deze wordt gepubliceerd.\n\nBronnen en methodologieSchattingen, definities en reikwijdte+\n\nDe bovenstaande aantallen hebben betrekking op de geselecteerde regel. Recordtypen worden per platform één keer gegroepeerd; volledige tags worden weergegeven in de platformdetails. Zoekopdrachten en filters zijn van toepassing binnen die regel. Registratiedata zijn afkomstig uit de opgeslagen momentopname van RDAP / WHOIS. Subdomeinen gebruiken de aanmaakdatum van het bovenliggende domein. De leeftijd op zich is geen bewijs van continue werking of een authenticatieroute. Huidige authenticatiehostnamen zijn afkomstig uit opgeslagen OpenID-verzoeken, met een UTC-tijdstempel; bij onopgeloste controles worden geen oude labels hergebruikt. De observer stopt vóór het inloggen op Steam en test de status van het Steam Link Filter niet. Routewaarnemingen downloaden ↗ Registratieresultaten downloaden ↗\n\nBekijk het bronarchief ↗\nBijlage G — Van een standaardafwijzing naar het onderliggende dossier\nDSAR-handleiding: vraag om het bewijsmateriaal\n\nMaak gebruik van artikel 15 van de AVG om persoonsgegevens op te vragen met betrekking tot het aanmaken van API-sleutels, het herstellen van accounts en toegang tot ondersteuning. Aan de hand van een bewaard gebleven verslag kan worden nagegaan wie een actie heeft geïnitieerd en waarop het platform zich heeft gebaseerd.\n\n01\nBewaar je tijdlijn.\n\nSla accountmeldingen, tickets, transactie-ID’s en datums op in UTC. Beveilig het account en bekijk de herstelopties die van toepassing zijn op het spel en de transactie.\n\nSteam Informatie over handelsbescherming ↗\n02\nVraag uw bewaarde gegevens op.\n\nVraag om tijdstempels, bron-IP-adressen, belangrijke gebeurtenissen in de levenscyclus van sleutels, beveiligingsbevestigingen en herstelmaatregelen met betrekking tot accounts. Neem ook gebeurtenissen met betrekking tot toegang door de ondersteuning en ontvangers op, voor zover die gegevens voor u van belang zijn.\n\n03\nBewaar het afleveringsbewijs.\n\nMaak gebruik van het contactformulier voor privacyzaken van Valve. De gebruikelijke reactietermijn bedraagt één maand; een noodzakelijke verlenging met maximaal twee extra maanden moet binnen die eerste maand worden gemotiveerd.\n\nValve privacy contact route ↗ gearchiveerd 2026-09-21 ↗\n04\nVergelijk de reactie.\n\nVergelijk de logboeken met je tijdlijn. Vraag naar de redenen voor weglatingen en maak vervolgens, indien nodig, gebruik van de klachtenprocedure bij de toezichthoudende instantie. Bewaar het antwoord precies zoals je het hebt ontvangen.\n\nToepassingsgebied / Artikel 15\n\nDe inzageverplichting heeft betrekking op bewaarde persoonsgegevens, inclusief gegevens in logbestanden. Dit garandeert geen inzage in alle interne documenten, gereconstrueerde gegevens of onbewerkte gegevens over anderen. Vraag om een begrijpelijke kopie en om de grondslag voor eventuele beperkingen.\n\nToegangsrichtlijnen van het EDPB, §§ 2, 4–6 ↗ · Artikelen 12, 15 en 77 van de AVG ↗ gearchiveerd 2026-09-20 ↗\n\nVerzoek om inzage van de betrokkeneAVG / Artikel 15\nAccountbeveiliging en toegangsgegevens\n\nVul de velden tussen haakjes in voordat u het formulier verstuurt.\n\nTo: Valve Privacy Team\nSubject: Article 15 GDPR request — account security records\n\nAccount / SteamID: [YOUR ACCOUNT IDENTIFIER]\nRelevant period (UTC): [START] to [END]\nRelated support tickets: [TICKET REFERENCES]\n\nI request a copy of the personal data concerning me that you retain for this period, including:\n\n1. API-key registration, confirmation, use and revocation events, with available timestamps, source IP addresses, registered domains, device or user-agent information and non-secret key identifiers.\n\n2. Recorded account-recovery actions, password/email/phone changes, Steam Guard removals or resets, confirmation events and the account-related evidence relied on to authorize those actions.\n\n3. Personal data in support-access and administrative-action logs concerning my account, including available dates, purposes, actions and the support entity involved, subject to applicable rights of others.\n\n4. Account-related records used to determine any sanction, and available records of my complaints, reviews and responses.\n\nPlease also provide the applicable processing purposes, categories, recipients, retention periods or criteria, and available information about sources where data were not obtained from me.\n\nWhere processing relies on my consent, please provide the retained record of the consent relied upon and the wording presented at that time.\n\nPlease provide an intelligible electronic copy with time zones and field definitions. Please do not include active credentials or secret tokens. If any requested data are not held, please say so. For any withheld data, please identify the scope and legal basis of the restriction and provide the remainder.\n\nPlease acknowledge receipt and respond within the applicable Article 12 period, explaining any necessary extension. I also ask you to preserve relevant existing records while this request is handled.\n\nName: [YOUR NAME]\nDate: [DATE]\nWat een IP-adres in een datacenter kan bewerkstelligen\nEen discrepantie is een aanleiding om een onderzoek in te stellen.\n\nEen verzoek om een API-sleutel afkomstig van het netwerk van een datacenter, zoals in het voorbeeld van de hostingprovider dat in dit onderzoek aan de orde is gekomen, kan relevant zijn bij vergelijking met inloggegevens, bevestigingen en de tijdlijn van de gebruiker. Een IP-adres alleen is niet voldoende om de dader te identificeren of om automatisch elke verdediging te ondermijnen. Bewijs dat een kwaadwillende dader de geregistreerde toestemming heeft verstrekt, zou het vertrouwen in die toestemming kunnen aantasten; andere rechtsgrondslagen en aansprakelijkheidskwesties vereisen een afzonderlijke analyse.\n\nBekijk de bewaarde klacht inzake het verbod en de AVG →\nBijlage H — Analyse van het Wayback Machine-archief · gepubliceerde ondersteuningsstatistieken\nOndersteuningsvolume. Gepubliceerde responstijden.\nContext en bronbeperkingen\n\nValve publiceert dagelijks ondersteuningsstatistieken op store.steampowered.com/stats/support. De archieven van de Wayback Machine bevatten historische momentopnames van deze pagina uit de periode 2018 tot en met 2026. De verhouding tussen het aantal tickets en het aantal medewerkers die uit deze cijfers blijkt, is niet in overeenstemming met een handmatige beoordeling per ticket binnen de gepubliceerde reactietijden.\n\nVergelijk de gearchiveerde ondersteuningscijfers van Valve in de opgeslagen momentopnames. In de methodologie wordt uitgelegd wat deze cijfers wel en niet kunnen meten.\n\nVolume ten opzichte van de gepubliceerde responstijd (2018 → 2026)\nTwee wachtrijen bij één helpdesk, te zien op 21 gearchiveerde schermafbeeldingen.\n\nValve publiceert cijfers over live ondersteuning op store.steampowered.com/stats/support. Elk punt hieronder is de ondergrens Valve zelf, zoals die op die pagina stond op de dag dat het Internet Archive de pagina vastlegde — het is geen schatting van ons. Beide reeksen geven dezelfde maat weer in dezelfde eenheid, dus horen ze op één as thuis en kunnen ze direct naast elkaar worden afgelezen.\n\nVerzoeken om terugbetaling — geld Valve in bezitAccountbeveiliging en -herstel — het account dat je kwijt bent geraakt\n0 h\n2 h\n4 h\n6 h\n8 h\n10 h\nno captures · 38 months\n2019\n2020\n2021\n2022\n2023\n2024\n2025\n2026\n8 h 44 m\naccount recovery\n52 m\nrefunds\n15 m — one capture only\n49–55 minDe ondergrens van de terugbetaling in elke registratie van februari 2018 tot augustus 2026. Over een periode van acht en een half jaar verschuift deze met minder dan zes minuten, terwijl het dagelijkse terugbetalingsvolume met een factor negen verandert.\n2,4 uur → 8,7 uurDe ondergrens voor het herstel van accounts ligt in alle metingen tot en met december 2022, op één na, rond de 2,4 uur. In de drie metingen van 2026 rapporteert Valve 10,9 uur, 5,8 uur en 8,7 uur.\n×2,8 → ×13Hoeveel trager het herstel verloopt dan terugbetalingen, volgens de door Valve zelf gepubliceerde cijfers. Vijf jaar lang blijft het stabiel, daarna wordt de kloof groter — de wachtrij die trager is geworden, is die waarbij de gebruiker, en niet Valve, zelf voor de kosten opdraait.\n\nBron: 21 Wayback Machine-archiefkopieën van store.steampowered.com/stats/support, 2018-02-03 tot 2026-08-10; extractie in VALVE_EVIDENCE_PACK/databases/steam_support_stats_history.json. Bekijk de grenzen aan de hand van de cijfers: de grafiek geeft de lager bovengrens van het bereik Valve afdrukken. De gepubliceerde bovengrens is op beide lijnen slechter — terugbetalingen varieerden van 1,5 uur tot 1,5 dag, herstel van 7,0 uur tot 3,6 dag. Twee schermafbeeldingen zijn gearchiveerd in een gelokaliseerde versie van dezelfde Valve pagina — 2018-11-03 in het Tsjechisch, 2020-03-25 in het Frans — en zijn in de tabel gemarkeerd met (cs) en (fr); hun cijfers worden hier weergegeven met de vertaalde eenheidsaanduidingen en de getallen zoals gepubliceerd, terwijl de letterlijke bronteksten in het extractiebestand zijn bewaard. Elke opname publiceerde een responstijd voor beide wachtrijen, en geen enkel punt op beide lijnen is geïnterpoleerd. Het enige herstelcijfer van 2020-10-21 voor 15 minuten is in de grafiek gemarkeerd en is behouden: het komt slechts in één opname voor en geen enkele andere opname ligt binnen een orde van grootte daarvan. Er bestaat geen registratie tussen 2022-12-08 en 2026-02-01; dat gat van 38 maanden in de gegevensreeks is gearceerd en er is niets overheen getekend. Deze cijfers beschrijven gepubliceerde responstijden. Ze laten niet zien wat er binnen een ticket gebeurt, en Valve heeft geen personeelsaantal gepubliceerd waartegen deze cijfers kunnen worden afgewogen.\n\nElke opname als tabel openen\nElke gearchiveerde opname, zoals gepubliceerd\nVastleggen\tRestituties / dag\tReactie op verzoek om terugbetaling\tHerstel / dag\tHerstelmaatregelen\n2018-02-03\t98,788\t50,12 minuten tot 1,52 uur\t25,662\t2,51 uur tot 1,80 dagen\n2018-05-07\t60,494\t53,83 minuten tot 1,47 dagen\t24,226\t2,45 uur tot 2,22 dagen\n2018-08-02\t69,084\t50,27 minuten tot 1,59 uur\t28,953\t2,44 uur tot 22,17 uur\n2018-11-03 (cs)\t63,410\t49,28 minuten tot 1,54 uur\t33,910\t2,42 uur tot 1,31 dagen\n2019-02-01\t76,305\t50,13 minuten tot 1,52 uur\t35,164\t2,44 uur tot 2,04 dagen\n2019-05-18\t78,951\t51,03 minuten tot 3,12 uur\t27,514\t2,46 uur tot 20,39 uur\n2019-09-07\t78,941\t50,65 minuten tot 1,66 uur\t28,812\t2,42 uur tot 13,59 uur\n2019-12-13\t69,589\t50,77 minuten tot 1,55 uur\t25,322\t2,45 uur tot 1,13 dagen\n2020-03-25 (fr)\t139,278\t49,45 minuten tot 1,53 uur\t32,302\t2,48 uur tot 3,62 dagen\n2020-06-26\t278,504\t48,98 minuten tot 2,29 uur\t20,343\t2,39 uur tot 6,99 uur\n2020-10-21\t107,633\t50,80 minuten tot 1,54 uur\t20,688\t15,33 minuten tot 8,62 uur\n2021-03-20\t158,956\t50,80 minuten tot 1,64 uur\t25,760\t2,34 uur tot 11,62 uur\n2021-06-26\t547,907\t51,93 minuten tot 6,73 uur\t29,728\t2,40 uur tot 15,63 uur\n2021-10-10\t170,103\t51,88 minuten tot 3,25 uur\t23,989\t2,39 uur tot 13,05 uur\n2022-01-31\t354,386\t53,65 minuten tot 8,09 uur\t24,391\t2,42 uur tot 15,29 uur\n2022-05-09\t172,555\t51,83 minuten tot 1,65 uur\t23,289\t2,41 uur tot 16,90 uur\n2022-09-05\t153,453\t53,67 minuten tot 4,15 uur\t23,594\t2,45 uur tot 1,22 dagen\n2022-12-08\t181,075\t54,83 minuten tot 6,67 uur\t27,111\t2,46 uur tot 18,89 uur\n2026-02-01\t317,762\t50,30 minuten tot 1,52 uur\t47,197\tvan 10.91 uur tot 21.30 uur\n2026-05-09\t246,776\t50,12 minuten tot 1,52 uur\t35,264\t5,81 uur tot 15,60 uur\n2026-08-10\t373,244\t52,05 minuten tot 2,07 uur\t45,319\t8,73 uur tot 16,52 uur\nBELANGRIJKSTE CONSTATIE:\nOver 21 Wayback-archiefkopieën in de periode van 2018-02-03 tot 2026-08-10 varieerden de dagelijkse aanvragen voor terugbetaling van 60,494 (mei 2018) tot 547,907 (juni 2021) — a 9,1× spread. Het cijfer voor 2026 is 373,244 (+278% ten opzichte van de gegevens van februari 2018).\nIn diezelfde negen jaar is de gepubliceerde ondergrens voor de reactietijd bij terugbetalingen nooit onder de 49–55 minuten band: een totale beweging van minder dan zes minuten, terwijl de werkbelasting erachter met een factor negen toenam.\nAls iemand elk kaartje slechts 5 seconden zou bestuderen, zou het verwerken van 373,244 kaartjes per dag (huidige situatie) 22 medewerkers die 24 uur per dag, 7 dagen per week aan het werk zijn alleen al om ze te openen en te sluiten; op het hoogtepunt (547,907, juni 2021) loopt dat op tot 32.\nAls de gepubliceerde responstijd de verwerkingstijd per ticket zou weerspiegelen (~52 min/ticket), zou de benodigde personeelsbezetting in de orde van grootte liggen van 13,500 agenten bij het huidige volume en ~20,000 op het hoogtepunt. Er is geen bronvermelding gevonden voor het aantal medewerkers dat Valve ondersteunt; hier wordt daarvan uitgegaan dat dit aantal nihil is.\nWat hieruit volgt: de verhouding tussen het volume en het aantal medewerkers is niet in overeenstemming met een handmatige beoordeling per ticket binnen de gepubliceerde responstijden. De cijfers komen overeen met een grotendeels geautomatiseerde eerste beoordeling; welk deel daadwerkelijk door mensen wordt beoordeeld, is niet bekendgemaakt.\nWaarom dit van belang is voor de naleving van de AVG\n\nArtikel 22 van de AVG verbiedt uitsluitend geautomatiseerde individuele besluitvorming die aanzienlijke rechtsgevolgen heeft, zonder dat op verzoek het recht op menselijke toetsing wordt geboden. Als Steam beslissingen van de klantenservice (het afsluiten van tickets, acties met betrekking tot accounts, het afwijzen van verzoeken om gegevens) volledig door geautomatiseerde scripts worden genomen, kan elke dergelijke beslissing die „aanzienlijke gevolgen“ heeft voor de gebruiker in strijd zijn met artikel 22.\n\nTicket HT-2YBP-F7JP-D4VB (Artikel 18) werd na drie dagen afgesloten met een standaardverwijzing, zonder dat er werd ingegaan op de aangehaalde rechtsgrondslag. Of iemand het heeft bekeken, kan niet uit het ticket worden afgeleid; dat is een vraag die de toezichthoudende autoriteit aan Valve kan stellen op grond van artikel 22 en artikel 15, lid 1, onder h).\n\nBron: Wayback Machine-momentopnames van store.steampowered.com/stats/support (2018-02-03, 2021-06-26, 2026-08-10) — gegevens geëxtraheerd naar VALVE_EVIDENCE_PACK/databases/steam_support_stats_history.json (21 momentopnames, 2018–2026). Opmerking: de responstijd van „~52 min“ is de ondergrens voor de categorie „terugbetalingen“; de responstijd voor „accountbeveiliging“ lag tussen 2,4 en 16,5 uur in dezelfde snapshots. 2021-06-26 is de absolute piek (547,907 terugbetalingsverzoeken), geen monotoon middenpunt — het volume steeg ~6× in 2020–2021, daalde vervolgens gedeeltelijk en herstelde zich daarna tot 373K in 2026.\nBijlage I — Reikwijdte van de dataset · aantallen die kunnen worden gereproduceerd\nTel de records. Controleer het bereik.\nContext en bronbeperkingen\n\nTel het aantal records en controleer vervolgens de beweringen: elk onderstaand cijfer kan opnieuw worden afgeleid uit de gepubliceerde bestanden.\n\nControleer de onderliggende datasets, reproduceer de tellingen en maak onderscheid tussen bronrijen en unieke voorvallen.\n\nHet hoofd-CSV-bestand bevat 40,448 rijen. Hiervan, 36,516 zijn afkomstig uit de Discord-AntiScam-phishingfeed. De overige 3,932 De rijen omvatten GitHub, beoordelingen, zoekresultaten, forumberichten en andere bronnen, en bieden zo een uitgebreide index van gemelde community-onderwerpen en beveiligingsrapporten.\n\nIn dat CSV-bestand zijn 1,690 rijen ondergebracht onder het verzamelingslabel „Unpatched Security Exploit”, dat betrekking heeft op eerdere gebruikersproblemen en bekendgemaakte kwetsbaarheden. Om deze meldingen te traceren, moet de specifieke build-tijdlijn en de openbare patchgeschiedenis van elke thread worden bekeken.\n\nHet doorzoekbare 16,319-recordarchief is een afzonderlijke, samengestelde versie met een eigen manifest, die is ontworpen voor een nauwkeurig lokaal onderzoek naar specifieke klachten van gebruikers en incidentmeldingen.\n\nOm een betrouwbaar controlespoor op te bouwen, moet elk door een gebruiker gemeld record worden vergeleken met gedocumenteerde bouwtijdlijnen en historische patchlogboeken.\n\nDe afzonderlijke collectiedocumenten van Deel II 231,829 unieke advertentie-ID’s, waaronder 33,509 in de categorie ‘geautomatiseerde registratie’ en 198,320 gemarkeerd als ‘niet-geverifieerde overboekingen’. De SHA-256 van het invoerbestand komt overeen met de bewaarde meting. Deze tellingen beschrijven pogingen tot aanbieden en waargenomen overdrachten, in plaats van definitieve transactiewaarden of geverifieerde diefttotalen, wat de noodzaak onderstreept van primaire platformgegevens om de exacte economische impact te meten. Afmetingen en hashes weergeven ↗\n\nCSV onder de knie krijgen ↗ · Doorzoekbaar archiefoverzicht ↗ · Bronrecords controleren ↗\n\nBijlage J — Over dit onderzoek\nValve publiceert geen handhavingsgegevens. We hebben er een gebouwd.\n\nOnafhankelijk. Niet-commercieel. Uitsluitend op basis van openbare gegevens samengesteld. Ingediend bij de toezichthouders.\n\n88.97%het automatiseringspark blijft onaangetast — er geldt geen enkel verbod\n67.77%van 51,732 veroordeelde oplichters komen vrij\n$26.8M+minimumuitgaven in de winkel door het niet-beperkte wagenpark\n3.6%gokwebsites die door de linkfilter van Valve zijn geblokkeerd\n8 jaarvan gedocumenteerde beveiligingsincidenten\n\nWat dit is. Een forensisch dossier over het Steam-platform van Valve Corporation — de handhavingsgeschiedenis, de ‘card-farming’-economie, het juridische kader en de authenticatie-infrastructuur die gokexploitanten gebruiken via Steam’s eigen OpenID-relay. Elk cijfer is herleidbaar uit twee bronnen: de eigen openbare API van Valve en de datasets die samen met dit onderzoek zijn gepubliceerd.\n\nVoor wie is het bedoeld? Toezichthouders met bevoegdheid over Valve — de AVG-toezichthouder voor Nederland, FinCEN, de SEC, de DSA-coördinator voor digitale diensten, UOKiK en elke wetshandhavingsinstantie die financiële stromen in verband met Steam onderzoekt. Ook voor journalisten, onderzoekers en elke gebruiker die een permanente accountblokkering heeft gekregen, een terugbetaling is geweigerd of wiens inventaris is gestolen en aan wie is verteld dat er geen beroepsmogelijkheid is.\n\nDe enige eis. Valve bewaart deze gegevens met volledige nauwkeurigheid — inclusief redenen voor verbanning, volledige ID-ruimte, in realtime. Het systeem kan elke zoekopdracht in dit dossier binnen enkele seconden uitvoeren en heeft ervoor gekozen om hieruit niets openbaar te maken. De vraag voor elke bevoegde autoriteit is eenvoudig: waarom niet?\n\nWat de auteurs niet beweren. Tijdens dit onderzoek is er op geen enkel platform van een derde partij een aanmelding bij Steam voltooid. Een opgegeven OpenID-URL bepaalt de verzoekparameters, niet of er een aanmelding is voltooid. Een afzonderlijk registreerbaar domein is op zichzelf geen bewijs van ontduiking. Registratiedata vormen de ondergrens voor het moment waarop een host voor het eerst in een OpenID-verzoek zou kunnen zijn verschenen; ze bewijzen geen continu gebruik. De auteurs doen geen uitspraken over wat Valve wist of van plan was: elke bewering over Valve is gekoppeld aan een gedateerd openbaar document of een gedateerde waarneming. Wanneer een bewering niet kon worden onderbouwd met een brondocument, is deze verwijderd.\n\nWie wij zijn\n\nPhishDestroy — onafhankelijke onderzoekers. Geen banden met Valve Corporation of enig hier genoemd platform. Eén Steam-account werd uitsluitend gebruikt om het AVG-verzoek in paragraaf 18 vast te leggen.\n\nWettelijke disclaimer\n\nNiet-commercieel, gedecentraliseerd onderzoek in het algemeen belang. Alle gegevens worden verstrekt „zoals ze zijn“, zonder enige garantie. Deze publicatie vormt geen gerechtelijke uitspraak.\n\nPUBLIEK DOMEIN\nLicenties\n\nAlle rechten zijn afgestaan aan de mensheid. Reproduceren, aanpassen, publiceren — bronvermelding niet vereist. Toegang vanuit OFAC-regio’s: verboden. Volledige licentie en disclaimer →",
        "headings": [
          {
            "level": 2,
            "id": "briefing-heading",
            "text": "De regel. Het record. De onbeantwoorde vragen."
          },
          {
            "level": 2,
            "id": null,
            "text": "Open brief aan de Kansspelcommissie van de staat Washington"
          },
          {
            "level": 3,
            "id": "wsgc-public-address-title",
            "text": "Tien dagen werden tien jaar.Open het dossier opnieuw."
          },
          {
            "level": 2,
            "id": null,
            "text": "De website is geblokkeerd. De inlogpagina is dat niet."
          },
          {
            "level": 3,
            "id": null,
            "text": "Figuur 3.1 — De twee routes, weergegeven."
          },
          {
            "level": 3,
            "id": null,
            "text": "De valkuil van het grote geheel: Link Filter is slechts schijnmaatregelen, geen bescherming"
          },
          {
            "level": 3,
            "id": null,
            "text": "Als het hoofddomein wordt geblokkeerd terwijl de auth-host niet wordt geblokkeerd, blijft de inlogroute open — en dat blijft jarenlang zo."
          },
          {
            "level": 3,
            "id": null,
            "text": "Achtergrond: Wat Steam is en waarom het hier van belang is"
          },
          {
            "level": 3,
            "id": null,
            "text": "Wat Valve deed: de domeinblokkering"
          },
          {
            "level": 3,
            "id": null,
            "text": "Wat een proxy-domein is"
          },
          {
            "level": 3,
            "id": null,
            "text": "Het kritieke punt: de Auth Host wordt bij elk verzoek naar Steam verzonden"
          },
          {
            "level": 3,
            "id": null,
            "text": "Wat dit aantoont"
          },
          {
            "level": 3,
            "id": null,
            "text": "In Steam is de lijst van Valve de enige lijst."
          },
          {
            "level": 3,
            "id": null,
            "text": "Omzeiling van de linkfilterbeveiliging"
          },
          {
            "level": 3,
            "id": null,
            "text": "De webbrowser Big Picture laat inlogcookies lekken en maakt gevoelige informatie openbaar (wat kan leiden tot het overnemen van accounts)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Wat dit betekent voor een minderjarige die een antivirusprogramma heeft geïnstalleerd"
          },
          {
            "level": 3,
            "id": null,
            "text": "De leeftijd van het domein.De datum van de waarneming."
          },
          {
            "level": 2,
            "id": null,
            "text": "Een eindpunt is gesloten. Bij het openbare traceren is een sleutel verloren gegaan."
          },
          {
            "level": 3,
            "id": null,
            "text": "Het tijdperk vóór de stroomstoring"
          },
          {
            "level": 3,
            "id": null,
            "text": "Na de wijziging"
          },
          {
            "level": 2,
            "id": null,
            "text": "Eén sessie. Meer toegang dan de gebruiker ziet."
          },
          {
            "level": 3,
            "id": null,
            "text": "1. Onvoldoende versterkte authenticatie"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. Het ontbreken van het beginsel van minimale rechten"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. Defecte sessiebeheerfunctie"
          },
          {
            "level": 3,
            "id": null,
            "text": "4. Het blokkeren van authenticatiehosts op domeinniveau was technisch haalbaar"
          },
          {
            "level": 3,
            "id": "integration-paradox-title",
            "text": "Valve compileert elke dag volgens deze regels. Hier is dat niet gelukt."
          },
          {
            "level": 4,
            "id": null,
            "text": "GitHub: gedetailleerde bereiken versus Valve Steam Web API"
          },
          {
            "level": 2,
            "id": null,
            "text": "Interactieve simulator voor exploits en kapingen"
          },
          {
            "level": 2,
            "id": null,
            "text": "De eindpunten achter de reeks."
          },
          {
            "level": 2,
            "id": null,
            "text": "Een aangevinkt vakje. Wiens handeling?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Hoe Valve uiteindelijk een einde maakte aan „handelsvervanging“ — en waarom het zeven jaar vol tijdelijke oplossingen kostte"
          },
          {
            "level": 4,
            "id": null,
            "text": "Afkoelperiode voor avatar en naam (februari 2024)"
          },
          {
            "level": 4,
            "id": null,
            "text": "7-daagse CS2-trendomkering (juli 2025)"
          },
          {
            "level": 4,
            "id": null,
            "text": "Verplichte mobiele pushmeldingen voor API (december 2023)"
          },
          {
            "level": 4,
            "id": null,
            "text": "Banners met accountleeftijd en naam (2022–2024)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Hun spelregels. De geregistreerde platforms."
          },
          {
            "level": 3,
            "id": "enforcement-focus-title",
            "text": "Eén regelboek. Ongelijke handhaving."
          },
          {
            "level": 4,
            "id": null,
            "text": "Automatisering"
          },
          {
            "level": 4,
            "id": null,
            "text": "Commercieel gebruik"
          },
          {
            "level": 4,
            "id": null,
            "text": "VPN en het verbergen van je locatie"
          },
          {
            "level": 4,
            "id": null,
            "text": "Linkverduistering"
          },
          {
            "level": 4,
            "id": null,
            "text": "Wie beoordeelt de beslissing wanneer de hulpverlening de zaak afsluit?"
          },
          {
            "level": 2,
            "id": null,
            "text": "Een API voor automatisering. Een regel tegen automatisering."
          },
          {
            "level": 3,
            "id": null,
            "text": "De misvatting van de „gameontwikkelaar”"
          },
          {
            "level": 4,
            "id": null,
            "text": "De tegenstrijdigheid van automatisering"
          },
          {
            "level": 4,
            "id": null,
            "text": "Een server-side rol in de handelsstroom"
          },
          {
            "level": 2,
            "id": null,
            "text": "Tien dagen geëist. Tien jaar om verantwoording af te leggen."
          },
          {
            "level": 3,
            "id": "letter-company",
            "text": "VALVE CORPORATION"
          },
          {
            "level": 3,
            "id": null,
            "text": "Tien dagen.En dan?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Volg de opgegeven retourhost."
          },
          {
            "level": 3,
            "id": "washington-record-heading",
            "text": "Twee termijnen. Eén onduidelijke handhavingsnorm."
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve geeft goksites 10 dagen de tijd"
          },
          {
            "level": 4,
            "id": null,
            "text": "Washington drukt op Valve"
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve verwerpt de beschuldiging"
          },
          {
            "level": 4,
            "id": null,
            "text": "De routes die in september 2026 zijn waargenomen"
          },
          {
            "level": 4,
            "id": null,
            "text": "Achttien maanden nadat Valve had geantwoord, noemde de toezichthouder het nog steeds een voornemen."
          },
          {
            "level": 3,
            "id": null,
            "text": "Het decennium van de 10-daagse kennisgeving: forensische overlevingsaudit van de 23 genoemde locaties"
          },
          {
            "level": 4,
            "id": null,
            "text": "Van 10-daagse waarschuwingen tot offshore-conglomeraten: de omzet van meerdere miljarden dollars"
          },
          {
            "level": 2,
            "id": null,
            "text": "De hostnaam staat al in het verzoek."
          },
          {
            "level": 3,
            "id": null,
            "text": "Gedocumenteerde en gemelde precedenten"
          },
          {
            "level": 3,
            "id": null,
            "text": "Wat een registratiedatum wel en niet aangeeft"
          },
          {
            "level": 3,
            "id": null,
            "text": "Vergelijkende controle: API-nalevingsnormen"
          },
          {
            "level": 2,
            "id": "market-thesis-heading",
            "text": "Het prijsverschil ten opzichte van 0"
          },
          {
            "level": 2,
            "id": null,
            "text": "Het prijsverschil is meetbaar."
          },
          {
            "level": 3,
            "id": null,
            "text": "Wat het bedrag aangeeft"
          },
          {
            "level": 3,
            "id": null,
            "text": "Veel locaties vermelden een waarde in dollars die hoger is dan Steam."
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam staat nog steeds aan kop wat betreft het aantal aanbiedingen."
          },
          {
            "level": 3,
            "id": null,
            "text": "Het commerciële ecosysteem ligt voor het grijpen."
          },
          {
            "level": 2,
            "id": null,
            "text": "Wie kan de beveiligingsmaatregelen resetten?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Een herstelticket waardoor de beveiliging van het account werd uitgeschakeld, en een gemeld verlies van $10,000"
          },
          {
            "level": 3,
            "id": null,
            "text": "Meer dan alleen de voorraad."
          },
          {
            "level": 3,
            "id": "theft-ledger-title",
            "text": "Valve liet de deur twee keer openstaan, met een tussenpoos van drieëndertig maanden. Ze ging nooit dicht."
          },
          {
            "level": 4,
            "id": null,
            "text": "Wat uit de boekhouding blijkt, en wat geen enkel afzonderlijk geval aantoont."
          },
          {
            "level": 3,
            "id": null,
            "text": "Vertrouwelijkheid moet gepaard gaan met technische verantwoordelijkheid."
          },
          {
            "level": 2,
            "id": null,
            "text": "Volg het geld. Scheid de transacties."
          },
          {
            "level": 3,
            "id": null,
            "text": "Waar het geld daadwerkelijk naartoe gaat."
          },
          {
            "level": 3,
            "id": null,
            "text": "Classificeer eerst de activiteit en daarna de verplichting."
          },
          {
            "level": 3,
            "id": null,
            "text": "Volg opbrengsten, kennis en ondersteuning."
          },
          {
            "level": 2,
            "id": null,
            "text": "De Wet inzake digitale diensten: leg kennis vast"
          },
          {
            "level": 3,
            "id": null,
            "text": "Een eis van tien dagen."
          },
          {
            "level": 3,
            "id": null,
            "text": "Het DSA-tijdvenster."
          },
          {
            "level": 3,
            "id": null,
            "text": "De looptijd moet worden bijgehouden."
          },
          {
            "level": 3,
            "id": null,
            "text": "van de jaarlijkse wereldwijde omzet"
          },
          {
            "level": 2,
            "id": null,
            "text": "Minderjarigen: een Steam-login geldt niet als leeftijdsverificatie"
          },
          {
            "level": 3,
            "id": null,
            "text": "Geef aan wat de operator en de gegevens zijn."
          },
          {
            "level": 3,
            "id": null,
            "text": "Leg het traject vast, van het inloggen tot het storten."
          },
          {
            "level": 2,
            "id": null,
            "text": "Het verzoek. Het antwoord. De ontbrekende vergelijking."
          },
          {
            "level": 3,
            "id": null,
            "text": "De documenten bestaan wel; de betrokkene heeft ze echter niet ontvangen."
          },
          {
            "level": 2,
            "id": null,
            "text": "De abonneeovereenkomst in strijd met de eigen architectuur van het platform"
          },
          {
            "level": 3,
            "id": null,
            "text": "Het marktplafond en het verbod op commercieel gebruik"
          },
          {
            "level": 3,
            "id": null,
            "text": "De kwetsbaarheid van de API-sleutel is eerder een kwestie van platformontwerp dan van nalatigheid van de gebruiker"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve ontvangt bij elke aanmelding de hostnaam van de authenticatie"
          },
          {
            "level": 3,
            "id": null,
            "text": "Het patroon in de gearchiveerde klachten"
          },
          {
            "level": 3,
            "id": null,
            "text": "Een rechtbank die dit dossier beoordeelt, zou de SSA niet op zichzelf beschouwen."
          },
          {
            "level": 2,
            "id": null,
            "text": "De bevindingen. De documenten waar we om vragen."
          },
          {
            "level": 2,
            "id": null,
            "text": "Bewijsnota — materiaal verstrekt door Bron 1"
          },
          {
            "level": 2,
            "id": null,
            "text": "De bewerking in de gegenereerde PDF is louter cosmetisch: de afgedekte tekst kan nog steeds worden geëxtraheerd"
          },
          {
            "level": 2,
            "id": null,
            "text": "Bijlagen bij ondersteunende documenten en juridische correspondentie"
          },
          {
            "level": 2,
            "id": null,
            "text": "Geselecteerde primaire bronnen"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-01",
            "text": "Hardware-sleutels, aangevraagd in 2016"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-02",
            "text": "Crash-rapporten zonder effectieve opt-out-mogelijkheid"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-03",
            "text": "Misbruik van authenticatietickets gemeld aan Valve"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-01",
            "text": "44 betwiste aankopen op de markt"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-02",
            "text": "Een definitieve uitsluiting en gesloten beroepsprocedures"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-03",
            "text": "Een herstelreset en een gemeld verlies van $10,000"
          },
          {
            "level": 2,
            "id": null,
            "text": "ArchiSteamFarm en de automatiseringsclausule"
          },
          {
            "level": 2,
            "id": null,
            "text": "Rules ledger: clauses against recorded platforms"
          },
          {
            "level": 3,
            "id": "ledger-title",
            "text": "Commercieel gebruik en facturering van accounts"
          },
          {
            "level": 3,
            "id": "lw-register-title",
            "text": "Platformregister 175"
          },
          {
            "level": 4,
            "id": null,
            "text": "Bewijslast"
          },
          {
            "level": 4,
            "id": null,
            "text": "Wat een gelabeld record wel en niet is"
          },
          {
            "level": 2,
            "id": null,
            "text": "DSAR-handleiding: vraag om het bewijsmateriaal"
          },
          {
            "level": 3,
            "id": null,
            "text": "Bewaar je tijdlijn."
          },
          {
            "level": 3,
            "id": null,
            "text": "Vraag uw bewaarde gegevens op."
          },
          {
            "level": 3,
            "id": null,
            "text": "Bewaar het afleveringsbewijs."
          },
          {
            "level": 3,
            "id": null,
            "text": "Vergelijk de reactie."
          },
          {
            "level": 3,
            "id": null,
            "text": "Accountbeveiliging en toegangsgegevens"
          },
          {
            "level": 3,
            "id": null,
            "text": "Een discrepantie is een aanleiding om een onderzoek in te stellen."
          },
          {
            "level": 2,
            "id": null,
            "text": "Ondersteuningsvolume. Gepubliceerde responstijden."
          },
          {
            "level": 3,
            "id": null,
            "text": "Twee wachtrijen bij één helpdesk, te zien op 21 gearchiveerde schermafbeeldingen."
          },
          {
            "level": 2,
            "id": null,
            "text": "Tel de records. Controleer het bereik."
          },
          {
            "level": 2,
            "id": null,
            "text": "Valve publiceert geen handhavingsgegevens.\nWe hebben er een gebouwd."
          }
        ],
        "links": [
          "https://dotesports.com/counter-strike/news/csgo-lounge-billion-bets-3896",
          "https://store.steampowered.com/agreement/?l=english",
          "http://web.archive.org/web/20260921022032/https://store.steampowered.com/agreement/?l=english",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-all-results.json",
          "https://blog.counter-strike.net/expresstrade/",
          "http://web.archive.org/web/20260307161538/https://blog.counter-strike.net/expresstrade/",
          "https://wsgc.wa.gov/news/2016/washington-state-gambling-commission-orders-valve-stop-skins-gambling",
          "http://web.archive.org/web/20260520012601/https://wsgc.wa.gov/news/2016/washington-state-gambling-commission-orders-valve-stop-skins-gambling",
          "https://fr.scribd.com/document/328063293/Valve-s-Oct-18th-response-to-Washington-State-Gambling-Commission-s-cease-and-desist",
          "https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921021947/https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921022628/https://steamcommunity.com/linkfilter/?url=https:%2F%2Frollbit.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rbsnin.com.20260921T021120Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rollbit.com.json",
          "http://web.archive.org/web/20260921022740/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fskin.club",
          "http://web.archive.org/web/20260921022842/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fsc-auth.net",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skin.club.json",
          "http://web.archive.org/web/20260921022603/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fhowl.gg",
          "http://web.archive.org/web/20260921022636/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fhowl.uno",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/howl.gg.json",
          "http://web.archive.org/web/20260921022840/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fduelbits.com",
          "http://web.archive.org/web/20260921022901/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fswitchflips.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/duelbits.com.json",
          "http://web.archive.org/web/20260921022758/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgofast.com",
          "http://web.archive.org/web/20260921022847/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fauthtofast.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgofast.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/farmskins.com.20260921T025840Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/steam.kobal.cc.20260921T025844Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/farmskins.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cobaltlab.tech.20260921T041604Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cobaltauth.com.20260921T041608Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/cobaltlab.tech.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgo.net.20260921T041619Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cn2.easylot.net.20260921T041623Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgo.net.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/ggdrop.com.20260921T041637Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/ggauth.com.20260921T041641Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/ggdrop.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rustchance.com.20260921T041703Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/hgfuihd.com.20260921T041706Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rustchance.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skin.fans.20260921T041710Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.skinfans.com.20260921T041713Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skin.fans.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinport.com.20260921T041724Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinport.app.20260921T041728Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skinport.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skins.cash.20260921T041731Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinscash.live.20260921T041735Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skins.cash.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2hunt.com.20260921T041739Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rstspcl.com.20260921T041742Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tf2hunt.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgogem.com.20260922T192355Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/api.csgem.com.20260922T192358Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-2026-09-22.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/gamdom.com.20260922T192326Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/login.gambldom.com.20260922T192330Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/12cs.fail.20260922T192347Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/fail.games.20260922T192351Z.html",
          "http://web.archive.org/web/20260921022953/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgoempire.com",
          "http://web.archive.org/web/20260921022947/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgoempirelogin4.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgoempire.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cs.money.20260921T021131Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.dota.trade.20260921T021134Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/cs.money.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csfloat.com.20260921T041612Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgofloat.com.20260921T041615Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csfloat.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/g4skins.com.20260921T041630Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.g4s.to.20260921T041634Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/g4skins.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/juice.gg.20260921T041644Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/letmeinjuice.com.20260921T041648Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/juice.gg.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/market.csgo.com.20260921T041652Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2.net.20260921T041655Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/market.csgo.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rust.tm.20260921T041659Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rust.tm.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgolounge.com.20260922T192333Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2.net.20260922T192340Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2lounge.com.20260922T192337Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinbaron.de.20260921T041717Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinbaron.com.20260921T041721Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skinbaron.de.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2royal.com.20260921T041746Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2auth.com.20260921T041750Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tf2royal.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tradeit.gg.20260921T041753Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/connect-tradeit.com.20260921T041757Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tradeit.gg.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/upgrader.pro.20260921T041801Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/upgauth.space.20260921T041804Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/upgrader.pro.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-recheck-2026-09-21.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/domain-registration.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wayback-snapshots.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-2026-09-22c.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/master_registry.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/longitudinal-steam-phishing-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-steam-phishing-100.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-coverage-2026-09-22.json",
          "https://blog.csfloat.com/how-floatdb-tracks-items/",
          "http://web.archive.org/web/20260921022415/https://blog.csfloat.com/how-floatdb-tracks-items/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/platform-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/platforms-removed.json",
          "https://hackerone.com/reports/291750",
          "http://web.archive.org/web/20251116185046/https://hackerone.com/reports/291750",
          "https://hackerone.com/reports/1079561",
          "http://web.archive.org/web/20260924181830/https://hackerone.com/reports/1079561",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/hackerone-reports.json",
          "https://phishdestroy.io/steam_dossier/nl/steam_enforcement_evidence.html#support-records",
          "https://www.darknavy.org/blog/exploiting_steam_usual_and_unusual_ways_in_the_cef_framework/",
          "https://steamcommunity.com/groups/SteamClientBeta/discussions/0/3365901765276206401/",
          "http://web.archive.org/web/20250804051514/https://steamcommunity.com/groups/SteamClientBeta/discussions/0/3365901765276206401/",
          "https://www.chromium.org/developers/design-documents/safebrowsing/",
          "http://web.archive.org/web/20260821101616/https://www.chromium.org/developers/design-documents/safebrowsing/",
          "https://www.chromium.org/developers/how-tos/api-keys/",
          "http://web.archive.org/web/20260830122831/https://www.chromium.org/developers/how-tos/api-keys/",
          "https://github.com/Homebrew/homebrew-cask/issues/193814",
          "https://testsafebrowsing.appspot.com/",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/domain-registration.json",
          "https://phishdestroy.io/steam_dossier/nl/AUTH_AUDIT.md",
          "https://datatracker.ietf.org/doc/rfc6749/",
          "https://docs.cloud.google.com/docs/authentication/api-keys",
          "https://listings.pcisecuritystandards.org/pdfs/PCI_DSS_Resource_Guide_(003).pdf",
          "https://developer.apple.com/news/?id=02202019a",
          "http://web.archive.org/web/20250506070026/https://developer.apple.com/news/?id=02202019a",
          "https://dev.twitch.tv/docs/authentication/validate-tokens/",
          "https://discuss.dev.twitch.com/t/legacy-twitch-api-v5-i-e-kraken-shutdown-reminder-february-28-2022/36589",
          "http://web.archive.org/web/20250127085635/https://discuss.dev.twitch.com/t/legacy-twitch-api-v5-i-e-kraken-shutdown-reminder-february-28-2022/36589",
          "https://store.steampowered.com/news/posts/?enddate=1788390000",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/4123547285514022851",
          "https://skinvault.gg/blog/cs2-trade-protection-explained/",
          "https://csmarketcap.com/blog/market-insights/from-boom-to-bust-cs2s-trade-protection-impact",
          "https://skin.land/blog/steam-changes-cs2-trade-ban-logic-timing/",
          "https://help.steampowered.com/faqs/view/3041-A87A-E5F6-B6AC",
          "https://steamcommunity.com/ogg/593110/announcements/detail/533224478739530146",
          "https://steamcommunity.com/games/CSGO/announcements/detail/4447966961421256740",
          "https://steamcommunity.com/sharedfiles/filedetails/?id=2926756889",
          "https://steamcommunity.com/dev/apikey",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3734103130194459461",
          "https://steamcommunity.com/discussions/forum/1/3807266184852932971/",
          "https://help.steampowered.com/faqs/view/225C-C51E-B8F0-55B2",
          "https://store.steampowered.com/news/group/4/view/3314112260640237775",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/issues/325",
          "https://blog.dota2.com/2020/05/trading-cooldown/",
          "https://blog.counter-strike.net/index.php/2018/03/20308/",
          "http://web.archive.org/web/20250226114333/https://blog.counter-strike.net/index.php/2018/03/20308/",
          "https://phishdestroy.io/steam_dossier/nl/steam_evidence_archive.html",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/493839547938902179",
          "https://store.steampowered.com/online_conduct",
          "http://web.archive.org/web/20260921022120/https://store.steampowered.com/online_conduct",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260918014700/https://store.steampowered.com/subscriber_agreement/",
          "https://steamcommunity.com/dev/apiterms",
          "http://web.archive.org/web/20260921022210/https://steamcommunity.com/dev/apiterms",
          "https://help.steampowered.com/en/faqs/view/628C-E332-BD8C-4D36",
          "https://phishdestroy.io/steam_dossier/nl/social_graph.html",
          "https://phishdestroy.io/steam_dossier/nl/security_timeline.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wsgc-skins-gambling-briefing-2018.pdf",
          "https://wsgc.wa.gov/sites/default/files/2023-10/Skins%20Gambling.pdf",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wsgc-briefing-manifest.json",
          "https://x.com/csgobig",
          "https://www.facebook.com/csgobigofficial/",
          "https://500.casino/",
          "https://csgolounge.com/",
          "https://csgocasino.gg/",
          "https://x.com/CSGOatsecom",
          "https://x.com/CSGOSweep/status/937420902538543106",
          "https://x.com/Wild",
          "https://x.com/csgopot",
          "https://x.com/csgodiamondscom",
          "https://www.ftc.gov/legal-library/browse/cases-proceedings/162-3184-csgo-lotto-matter",
          "https://x.com/CSGODouble",
          "https://x.com/csgo_massive",
          "https://www.facebook.com/csgostrongfree/",
          "https://www.facebook.com/CSNCOM/",
          "https://www.gamblingcommission.gov.uk/report/young-people-and-gambling",
          "https://www.aph.gov.au/Parliamentary_Business/Committees/Senate/Environment_and_Communications/Gamingmicro-transactions",
          "https://phishdestroy.io/steam_dossier/nl/elite_skins.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/csfloat-catalogue.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/skinport-floor-over-cap.json",
          "https://pricempire.com/cs2-marketplaces",
          "http://web.archive.org/web/20260921022459/https://pricempire.com/cs2-marketplaces",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/priceempire-marketplaces.json",
          "https://www.steamanalyst.com/marketplace",
          "http://web.archive.org/web/20260719014552/https://www.steamanalyst.com/marketplace",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-atlas.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json",
          "https://phishdestroy.io/steam_dossier/nl/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/nl/steam_enforcement_evidence.html#case-support-recovery",
          "https://top10.owasp.org/2025/A01_2025-Broken_Access_Control/",
          "http://web.archive.org/web/20260920212535/https://top10.owasp.org/2025/A01_2025-Broken_Access_Control/",
          "https://store.steampowered.com/privacy_agreement/",
          "http://web.archive.org/web/20260921021648/https://store.steampowered.com/privacy_agreement/",
          "https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "http://web.archive.org/web/20250818113925/https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "https://www.dexerto.com/counter-strike-2/valve-saves-hacked-cs2-player-threatened-with-ransom-over-300000-of-rare-stickers-3283135/",
          "https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "http://web.archive.org/web/20220702042821/https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "https://www.kaspersky.com/blog/cs-go-two-million-usd-inventory-hack/44697/",
          "https://esportfire.com/article/the-2-million-usd-csgo-hack-22062022",
          "http://web.archive.org/web/20260515110250/https://esportfire.com/article/the-2-million-usd-csgo-hack-22062022",
          "https://esportsbetting.com/valve-deletes-130000-stolen-dragon-lore/",
          "https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "http://web.archive.org/web/20251115173120/https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "https://vkplay.ru/media/news/bloger-rasskazal-kak-podderzhka-steam-vorovala-akkaunty-igrokov/",
          "https://lis-skins.com/ru/blog/krupneisaia-mosenniceskaia-sxema-v-istorii-steam/",
          "https://escorenews.com/ru/csgo/news/44056-sotrudniki-podderjki-steam-zanimalis-krajey-skinov-s-akkauntov-za-god-oni-zarabotali-svyshe-300-tysyach-dollarov",
          "https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "http://web.archive.org/web/20250805141942/https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/outsourcing-archive-records.json",
          "https://community.skin.club/en/news/collector-has-steam-inventory-returned-after-bold-hack",
          "https://esportfire.com/article/300k-scam-full-katowice-2014-holo-collection-hacked",
          "http://web.archive.org/web/20251217072445/https://esportfire.com/article/300k-scam-full-katowice-2014-holo-collection-hacked",
          "https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng",
          "http://web.archive.org/web/20260920024236/https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng",
          "https://ag.ny.gov/press-release/2026/attorney-general-james-sues-game-developer-promoting-illegal-gambling-through",
          "http://web.archive.org/web/20260901015430/https://ag.ny.gov/press-release/2026/attorney-general-james-sues-game-developer-promoting-illegal-gambling-through",
          "https://www.fincen.gov/sites/default/files/2019-05/FinCEN%20CVC%20Guidance%20FINAL.pdf",
          "http://web.archive.org/web/20250711185007/https://www.fincen.gov/sites/default/files/2019-05/FinCEN%20CVC%20Guidance%20FINAL.pdf",
          "https://eur-lex.europa.eu/legal-content/EN/LSU/?uri=CELEX:32018L1673",
          "https://eur-lex.europa.eu/eli/dir/2024/1640/oj/eng",
          "http://web.archive.org/web/20260830153004/https://eur-lex.europa.eu/eli/dir/2024/1640/oj/eng",
          "https://eur-lex.europa.eu/eli/reg/2022/2065/oj/eng",
          "http://web.archive.org/web/20260920080125/https://eur-lex.europa.eu/eli/reg/2022/2065/oj/eng",
          "https://phishdestroy.io/steam_dossier/nl/legal_analysis.html",
          "https://partner.steamgames.com/doc/features/auth#website",
          "http://web.archive.org/web/20260921022335/https://partner.steamgames.com/doc/features/auth",
          "https://www.ftc.gov/legal-library/browse/rules/childrens-online-privacy-protection-rule-coppa",
          "http://web.archive.org/web/20260921070051/https://www.ftc.gov/legal-library/browse/rules/childrens-online-privacy-protection-rule-coppa",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/gdpr-ticket-1.png",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/screenshot-manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/gdpr-ticket-2.png",
          "https://datenschutz.hamburg.de/beschwerde",
          "https://edpb.europa.eu/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/regulatory-review/disclosure-audit.json",
          "https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "http://web.archive.org/web/20260821155801/https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "https://phishdestroy.io/steam_dossier/nl/index#exhibit-gallery-section",
          "https://github.com/ValveSoftware/steam-for-linux/issues/4521",
          "https://phishdestroy.io/steam_dossier/nl/steam_evidence_archive.html?source=GitHub&record=484",
          "https://github.com/ValveSoftware/steam-for-linux/issues/6459",
          "http://web.archive.org/web/20260419051343/https://github.com/ValveSoftware/steam-for-linux/issues/6459",
          "https://phishdestroy.io/steam_dossier/nl/steam_evidence_archive.html?source=GitHub&record=467",
          "https://github.com/ValveSoftware/Source-1-Games/issues/3857",
          "https://phishdestroy.io/steam_dossier/nl/steam_evidence_archive.html?source=GitHub&record=768",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "http://web.archive.org/web/20250320082450/https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://phishdestroy.io/steam_dossier/nl/steam_evidence_archive.html?source=Reddit&record=4533",
          "https://www.reddit.com/r/ohnePixel/comments/1hahqx2/permanently_banned_steam_account_without_a_clear/",
          "https://phishdestroy.io/steam_dossier/nl/steam_evidence_archive.html?source=Reddit&record=4766",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://phishdestroy.io/steam_dossier/nl/steam_evidence_archive.html?source=Reddit&record=4592",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/selected-evidence-records.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive_manifest.json",
          "https://phishdestroy.io/steam_dossier/nl/card_economy.html",
          "https://github.com/JustArchiNET/ArchiSteamFarm/wiki/FAQ",
          "https://phishdestroy.io/steam_dossier/nl/card_economy.html#scale",
          "https://phishdestroy.io/steam_dossier/nl/card_economy.html#licence",
          "https://phishdestroy.io/steam_dossier/nl/enforcement_audit.html",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "http://web.archive.org/web/20260924181709/https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://rdap.verisign.com/com/v1/domain/csgoempire.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoempire.com",
          "https://rdap.verisign.com/com/v1/domain/csgoempirelogin4.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/csgoempire.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustreaper.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustreaper.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/rustreaper.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustly.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustly.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/rustly.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgofast.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgofast.com",
          "https://rdap.verisign.com/com/v1/domain/authtofast.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/csgofast.com.json",
          "https://rdap.verisign.com/com/v1/domain/duelbits.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fduelbits.com",
          "https://rdap.verisign.com/com/v1/domain/switchflips.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/duelbits.com.json",
          "https://rdap.verisign.com/com/v1/domain/farmskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffarmskins.com",
          "https://tld-rdap.verisign.com/cc/v1/domain/kobal.cc",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/farmskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoluck.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoluck.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/csgoluck.com.json",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/domain-registry/insane.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Finsane.gg",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/insane.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs2skin.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs2skin.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/cs2skin.com.json",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/domain-registry/juice.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fjuice.gg",
          "https://rdap.verisign.com/com/v1/domain/letmeinjuice.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/juice.gg.json",
          "https://rdap.verisign.com/com/v1/domain/ggdrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fggdrop.com",
          "https://rdap.verisign.com/com/v1/domain/ggauth.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/ggdrop.com.json",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/domain-registry/howl.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhowl.gg",
          "https://rdap.radix.host/rdap/domain/howl.uno",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/howl.gg.json",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/domain-registry/chicken.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fchicken.gg",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/chicken.gg.json",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/domain-registry/csgocasino.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgocasino.gg",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/csgocasino.gg.json",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/domain-registry/hunt.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhunt.gg",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/hunt.gg.json",
          "https://rdap.verisign.com/com/v1/domain/csbattle.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsbattle.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/csbattle.com.json",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/domain-registry/skinrave.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinrave.gg",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/skinrave.gg.json",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/domain-registry/csdouble.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsdouble.gg",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/csdouble.gg.json",
          "https://rdap.verisign.com/com/v1/domain/rustchance.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustchance.com",
          "https://rdap.verisign.com/com/v1/domain/hgfuihd.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/rustchance.com.json",
          "https://rdap.radix.host/rdap/domain/cobaltlab.tech",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcobaltlab.tech",
          "https://rdap.verisign.com/com/v1/domain/cobaltauth.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/cobaltlab.tech.json",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/domain-registry/raided.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fraided.gg",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/raided.gg.json",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/domain-registry/rustneo.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustneo.gg",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/rustneo.gg.json",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/domain-registry/splits.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsplits.gg",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/splits.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/upgrader.pro",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fupgrader.pro",
          "https://rdap.radix.host/rdap/domain/upgauth.space",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/upgrader.pro.json",
          "https://rdap.centralnic.com/fans/domain/skin.fans",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.fans",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/skin.fans.json",
          "https://rdap.nic.one/domain/hotpizza.one",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhotpizza.one",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/hotpizza.one.json",
          "https://rdap.verisign.com/com/v1/domain/g4skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg4skins.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/g4skins.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2royal.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2royal.com",
          "https://rdap.verisign.com/com/v1/domain/tf2auth.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/tf2royal.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2hunt.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2hunt.com",
          "https://rdap.verisign.com/com/v1/domain/rstspcl.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/tf2hunt.com.json",
          "https://rdap.identitydigital.services/rdap/domain/tf2.bet",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2.bet",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/tf2.bet.json",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/domain-registry/openstars.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fopenstars.gg",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/openstars.gg.json",
          "https://rdap.verisign.com/com/v1/domain/skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/skins.com.json",
          "https://rdap.identitydigital.services/rdap/domain/white.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwhite.market",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/white.market.json",
          "https://rdap.identitydigital.services/rdap/domain/moon.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmoon.market",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/moon.market.json",
          "https://rdap.verisign.com/com/v1/domain/csfloat.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsfloat.com",
          "https://rdap.verisign.com/com/v1/domain/csgofloat.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/csfloat.com.json",
          "https://rdap.identitydigital.services/rdap/domain/skin.land",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.land",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/skin.land.json",
          "https://rdap.verisign.com/com/v1/domain/haloskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhaloskins.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/haloskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/163.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuff.163.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/buff.163.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmarket.csgo.com",
          "https://rdap.verisign.com/net/v1/domain/dota2.net",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/market.csgo.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinport.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinport.com",
          "https://pubapi.registry.google/rdap/domain/skinport.app",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/skinport.com.json",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/domain-registry/skinflow.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinflow.gg",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/skinflow.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/skin.place",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.place",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/skin.place.json",
          "https://rdap.verisign.com/com/v1/domain/skinsmonkey.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinsmonkey.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/skinsmonkey.com.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbaron.de",
          "https://rdap.verisign.com/com/v1/domain/skinbaron.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/skinbaron.de.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frust.tm",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/rust.tm.json",
          "https://rdap.verisign.com/com/v1/domain/pirateswap.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fpirateswap.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/pirateswap.com.json",
          "https://rdap.radix.host/rdap/domain/mannco.store",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmannco.store",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/mannco.store.json",
          "https://rdap.verisign.com/com/v1/domain/skinswap.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinswap.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/skinswap.com.json",
          "https://rdap.verisign.com/com/v1/domain/exeskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fexeskins.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/exeskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/balticskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbalticskins.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/balticskins.com.json",
          "https://rdap.nic.trade/domain/cs.trade",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.trade",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/cs.trade.json",
          "https://rdap.verisign.com/com/v1/domain/rapidskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frapidskins.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/rapidskins.com.json",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/domain-registry/tradeit.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftradeit.gg",
          "https://rdap.verisign.com/com/v1/domain/connect-tradeit.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/tradeit.gg.json",
          "https://rdap.verisign.com/com/v1/domain/49skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F49skins.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/49skins.com.json",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/domain-registry/skinvault.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinvault.gg",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/skinvault.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/aim.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Faim.market",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/aim.market.json",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/domain-registry/skinout.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinout.gg",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/skinout.gg.json",
          "https://rdap.verisign.com/com/v1/domain/ntskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fntskins.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/ntskins.com.json",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/domain-registry/gamerpay.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamerpay.gg",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/gamerpay.gg.json",
          "https://rdap.nic.tf/domain/scrap.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fscrap.tf",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/scrap.tf.json",
          "https://rdap.nic.tf/domain/marketplace.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmarketplace.tf",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/marketplace.tf.json",
          "https://rdap.identitydigital.services/rdap/domain/skins.cash",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.cash",
          "https://rdap.identitydigital.services/rdap/domain/skinscash.live",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/skins.cash.json",
          "https://rdap.verisign.com/net/v1/domain/csgo.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo.net",
          "https://rdap.verisign.com/net/v1/domain/easylot.net",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/csgo.net.json",
          "https://rdap.verisign.com/net/v1/domain/cybershoke.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcybershoke.net",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/cybershoke.net.json",
          "https://rdap.verisign.com/net/v1/domain/fastcup.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffastcup.net",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/fastcup.net.json",
          "https://rdap.verisign.com/com/v1/domain/leetify.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fleetify.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/leetify.com.json",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/domain-registry/scope.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fscope.gg",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/scope.gg.json",
          "https://rdap.verisign.com/com/v1/domain/tradeupspy.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftradeupspy.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/tradeupspy.com.json",
          "https://rdap.identitydigital.services/rdap/domain/cs.deals",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.deals",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/cs.deals.json",
          "https://rdap.verisign.com/com/v1/domain/pricempire.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fpricempire.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/pricempire.com.json",
          "https://rdap.identitydigital.services/rdap/domain/lzt.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flzt.market",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/lzt.market.json",
          "https://rdap.verisign.com/com/v1/domain/z2u.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fz2u.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/z2u.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoroll.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoroll.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/csgoroll.com.json",
          "https://rdap.verisign.com/com/v1/domain/rollbit.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frollbit.com",
          "https://rdap.verisign.com/com/v1/domain/rbsnin.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/rollbit.com.json",
          "https://rdap.identitydigital.services/rdap/domain/500.casino",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F500.casino",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/500.casino.json",
          "https://rdap.verisign.com/com/v1/domain/csgobig.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgobig.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/csgobig.com.json",
          "https://rdap.verisign.com/com/v1/domain/casedrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcasedrop.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/casedrop.com.json",
          "https://rdap.verisign.com/com/v1/domain/banditcamp.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbanditcamp.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/banditcamp.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinbox.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbox.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/skinbox.com.json",
          "https://rdap.verisign.com/com/v1/domain/tastydrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftastydrop.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/tastydrop.com.json",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/domain-registry/csgopolygon.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgopolygon.gg",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/csgopolygon.gg.json",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/domain-registry/magicdrop.ru.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmagicdrop.ru",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/magicdrop.ru.json",
          "https://rdap.verisign.com/com/v1/domain/csdice.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsdice.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/csdice.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinodds.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinodds.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/skinodds.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgowin.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgowin.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/csgowin.com.json",
          "https://rdap.verisign.com/net/v1/domain/csgorun.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgorun.net",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/csgorun.net.json",
          "https://rdap.verisign.com/com/v1/domain/openskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fopenskins.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/openskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustbet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustbet.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/rustbet.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgomagic.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgomagic.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/csgomagic.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgobounty.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgobounty.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/csgobounty.com.json",
          "https://rdap.verisign.com/com/v1/domain/ezskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fezskins.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/ezskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustcases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustcases.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/rustcases.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoreaper.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoreaper.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/csgoreaper.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgocases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgocases.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/csgocases.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo-skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo-skins.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/csgo-skins.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgonet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgonet.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/csgonet.com.json",
          "https://rdap.verisign.com/com/v1/domain/wtfskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwtfskins.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/wtfskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/flamecases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fflamecases.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/flamecases.com.json",
          "https://rdap.verisign.com/com/v1/domain/gamedom.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamedom.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/gamedom.com.json",
          "https://rdap.nic.club/domain/skin.club",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.club",
          "https://rdap.verisign.com/net/v1/domain/sc-auth.net",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/skin.club.json",
          "https://rdap.verisign.com/com/v1/domain/daddyskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdaddyskins.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/daddyskins.com.json",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/domain-registry/rustix.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustix.gg",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/rustix.gg.json",
          "https://rdap.nic.club/domain/skins.club",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.club",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/skins.club.json",
          "https://rdap.publicinterestregistry.org/rdap/domain/csgohouse.org",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgohouse.org",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/csgohouse.org.json",
          "https://rdap.verisign.com/net/v1/domain/skinrave.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinrave.net",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/skinrave.net.json",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/domain-registry/bloodycase.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbloodycase.gg",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/bloodycase.gg.json",
          "https://rdap.verisign.com/com/v1/domain/csgoclicker.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoclicker.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/csgoclicker.com.json",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/domain-registry/rustbet.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustbet.gg",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/rustbet.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs-drop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs-drop.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/cs-drop.com.json",
          "https://rdap.verisign.com/net/v1/domain/hellstore.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhellstore.net",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/hellstore.net.json",
          "https://rdap.verisign.com/com/v1/domain/rustloot.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustloot.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/rustloot.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo-case.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo-case.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/csgo-case.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgogem.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgogem.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/csgogem.com.json",
          "https://rdap.verisign.com/com/v1/domain/rainbet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frainbet.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/rainbet.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustclash.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustclash.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/rustclash.com.json",
          "https://rdap.identitydigital.services/rdap/domain/12cs.fail",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F12cs.fail",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/12cs.fail.json",
          "https://rdap.verisign.com/com/v1/domain/tf2easy.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwww.tf2easy.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/tf2easy.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2blaze.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2blaze.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/tf2blaze.com.json",
          "https://rdap.verisign.com/com/v1/domain/shuffle.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fshuffle.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/shuffle.com.json",
          "https://rdap.identitydigital.services/rdap/domain/buff.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuff.market",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/buff.market.json",
          "https://rdap.identitydigital.services/rdap/domain/avan.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Favan.market",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/avan.market.json",
          "https://rdap.identitydigital.services/rdap/domain/cs.money",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.money",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/cs.money.json",
          "https://rdap.verisign.com/com/v1/domain/uuskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fuuskins.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/uuskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/youpin898.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fyoupin898.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/youpin898.com.json",
          "https://rdap.verisign.com/com/v1/domain/c5game.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fc5game.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/c5game.com.json",
          "https://rdap.verisign.com/com/v1/domain/waxpeer.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwaxpeer.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/waxpeer.com.json",
          "https://rdap.verisign.com/com/v1/domain/dmarket.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdmarket.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/dmarket.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamcommunity.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamcommunity.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/steamcommunity.com.json",
          "https://rdap.verisign.com/com/v1/domain/lootfarm.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flootfarm.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/lootfarm.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustskins.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/rustskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/krakatoa.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fkrakatoa.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/krakatoa.com.json",
          "https://rdap.verisign.com/com/v1/domain/shadowpay.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fshadowpay.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/shadowpay.com.json",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/domain-registry/igxe.cn.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Figxe.cn",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/igxe.cn.json",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/domain-registry/swap.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fswap.gg",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/swap.gg.json",
          "https://rdap.verisign.com/com/v1/domain/bitskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbitskins.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/bitskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2mart.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2mart.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/tf2mart.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinbid.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbid.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/skinbid.com.json",
          "https://rdap.verisign.com/com/v1/domain/lootbear.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flootbear.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/lootbear.com.json",
          "https://rdap.nic.tf/domain/backpack.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbackpack.tf",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/backpack.tf.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fstntrading.eu",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/stntrading.eu.json",
          "https://rdap.verisign.com/com/v1/domain/skinwallet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinwallet.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/skinwallet.com.json",
          "https://rdap.verisign.com/com/v1/domain/dota2market.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdota2market.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/dota2market.com.json",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/domain-registry/xplay.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fxplay.gg",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/xplay.gg.json",
          "https://rdap.verisign.com/com/v1/domain/esportal.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fesportal.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/esportal.com.json",
          "https://rdap.registro.br/domain/gamersclub.com.br",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamersclub.com.br",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/gamersclub.com.br.json",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/domain-registry/epidemic.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fepidemic.gg",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/epidemic.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs2stash.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs2stash.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/cs2stash.com.json",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/domain-registry/csgoskins.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoskins.gg",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/csgoskins.gg.json",
          "https://rdap.verisign.com/com/v1/domain/steamanalyst.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamanalyst.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/steamanalyst.com.json",
          "https://rdap.verisign.com/net/v1/domain/steamcardexchange.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamcardexchange.net",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/steamcardexchange.net.json",
          "https://rdap.verisign.com/com/v1/domain/dotabuff.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdotabuff.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/dotabuff.com.json",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/domain-registry/tracker.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftracker.gg",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/tracker.gg.json",
          "https://rdap.verisign.com/com/v1/domain/funpay.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffunpay.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/funpay.com.json",
          "https://rdap.verisign.com/com/v1/domain/playerauctions.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fplayerauctions.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/playerauctions.com.json",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/domain-registry/eldorado.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Feldorado.gg",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/eldorado.gg.json",
          "https://rdap.verisign.com/com/v1/domain/g2a.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg2a.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/g2a.com.json",
          "https://rdap.verisign.com/net/v1/domain/kinguin.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fkinguin.net",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/kinguin.net.json",
          "https://rdap.verisign.com/com/v1/domain/g2g.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg2g.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/g2g.com.json",
          "https://rdap.verisign.com/com/v1/domain/playerup.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fplayerup.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/playerup.com.json",
          "https://rdap.verisign.com/net/v1/domain/smurfhub.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfhub.net",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/smurfhub.net.json",
          "https://rdap.verisign.com/com/v1/domain/smurfaccounts.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfaccounts.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/smurfaccounts.com.json",
          "https://rdap.verisign.com/com/v1/domain/buycsgorank.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuycsgorank.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/buycsgorank.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgosmurfkings.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgosmurfkings.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/csgosmurfkings.com.json",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/domain-registry/smurfstore.co.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfstore.co",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/smurfstore.co.json",
          "https://rdap.verisign.com/com/v1/domain/steamlvlup.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlvlup.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/steamlvlup.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamlevels.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlevels.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/steamlevels.com.json",
          "https://rdap.verisign.com/com/v1/domain/levelsteam.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flevelsteam.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/levelsteam.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamlevelu.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlevelu.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/steamlevelu.com.json",
          "https://rdap.verisign.com/com/v1/domain/eloking.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Feloking.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/eloking.com.json",
          "https://rdap.publicinterestregistry.org/rdap/domain/boosteria.org",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fboosteria.org",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/boosteria.org.json",
          "https://rdap.verisign.com/com/v1/domain/overgear.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fovergear.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/overgear.com.json",
          "https://rdap.verisign.com/com/v1/domain/blazingboost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fblazingboost.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/blazingboost.com.json",
          "https://rdap.verisign.com/com/v1/domain/dota2boost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdota2boost.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/dota2boost.com.json",
          "https://rdap.verisign.com/com/v1/domain/buyboost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuyboost.com",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit/buyboost.com.json",
          "https://phishdestroy.io/steam_dossier/nl/steam_tos_assets/auth-route-audit.json",
          "https://help.steampowered.com/en/faqs/view/365F-4BEE-2AE2-7BDD",
          "https://store.steampowered.com/privacy_agreement/#8",
          "https://www.edpb.europa.eu/system/files/2023-04/edpb_guidelines_202201_data_subject_rights_access_v2_en.pdf",
          "https://web.archive.org/web/20260810154631/https://store.steampowered.com/stats/support",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/design-review/part2/measurements.json",
          "https://phishdestroy.io/steam_dossier/nl/VALVE_EVIDENCE_PACK/databases/TOTAL_VALVE_SCANDALS_MASTER_DB.csv",
          "https://phishdestroy.io/steam_dossier/nl/license_disclaimer.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/nl/index.content.json",
      "export_json_sha256": "55df53165367d6fb8092d52cf00fc6fdbe534ceec8506df113c58f8e0c83bb92"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "nl/investigation_part2.html",
      "language": "nl",
      "title": "Toegang tot accounts en verantwoordingsplicht — Het Steam-dossier",
      "source_url": "https://phishdestroy.io/steam_dossier/nl/investigation_part2",
      "source_html_sha256": "ef5d1c8703e4d336a34428137569ab8305bc7583abb3d7225228bb52e8c047b6",
      "exported_at": "2026-09-29T00:18:24.552Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "investigation_part2.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/nl/investigation_part2.pdf?v=print-20260929-v5",
        "sha256": "5626bf4c8a0c6897b2a5cccee178085fc99b67c1959f5ff648f260fcbadcef1e",
        "bytes": 125566,
        "pages": 9
      },
      "integrity": {
        "signed_object": "investigation_part2.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "investigation_part2.content.json.asc",
        "digest_file": "investigation_part2.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify investigation_part2.content.json.asc investigation_part2.content.json",
          "sha256sum -c investigation_part2.content.json.sha256"
        ]
      },
      "content": {
        "text": "HET STEAM-DOSSIER / II\n\nUw account.Hun toegang.Wie neemt er op?\n\nAutomatisering in de publieke sector. Uitbestede ondersteuning. De mensen die achterblijven om de rekening te betalen.\n\nVolg de infrastructuur, de gemelde verliezen en de documenten waarop de claims zijn gebaseerd.\n\nBreng de infrastructuur in kaart ↘\nBIJLAGE 01 / TOEZICHT OP DE LIVE SHADOW-MARKT550,000+\n\nSteam accounts die momenteel actief te koop staan op FSB Market (geanonimiseerde naam; de oorspronkelijke naam wordt hier niet vermeld)\nop dit moment\n\n550,000+ ACTUELE VOORRAAD · 231,829 IN HISTORISCH GESCHRAPT CORPUS (198,320 STEALER-LOGS)\n\nHet belangrijkste ondergrondse knooppunt voor gekaapte Steam-accounts, FSB Market (andere verwante namen niet vermeld) verifieert zowel kopers als verkopers met behulp van de officiële Steam OpenID van Valve (openid.realm = https://FSB Market). Op elk willekeurig moment worden meer dan een half miljoen gestolen en gehackte accounts (logbestanden van RedLine/Lumma, phishing-vangsten, credential stuffing) actief te koop aangeboden voor een paar cent ($0.50–$2.00). Noch FSB Market noch het bijbehorende forum wordt geblokkeerd door het linkfilter van Valve. Dit is het industriële reservoir dat de 63.06% betaalde botaccounts bevoorraadt die Valve blokkeert zonder het slachtoffer te helpen.\n\nLive-informatie: Monitoring van de schaduwmarkt (meer dan 550.000 live) ↗ · Opnamegegevens openen ↗ · Open Link Filter-trace ↗550.000+ LIVE\n\n01 / EEN ECOSYSTEEM MET AUTEURS\n\nAutomatisering heefteen papieren spoor.\n\nGenoemde projecten. Gepubliceerde mogelijkheden. Traceer een tool naar de bijbehorende documentatie en bekijk vervolgens de verzamelde relaties tussen ontwikkelaars.\n\n252VERZAMELDE REPOSITORIA\n3,320GITHUB-PROFIELEN\n4,214PROFIEL–REPOSITORY-PAAREN\nValve infrastructuurGemeentelijke bibliothekenHerbruikbare toepassingen\nDe lijnen geven gedocumenteerde integraties of afhankelijkheden weer. Selecteer een knooppunt om de bijbehorende informatie te bekijken.\n\nAutomatisering van meerdere accounts / JustArchiNET\n\nArchiSteamFarm\n\nHet project maakt expliciet reclame voor het gelijktijdig verzamelen van kaarten op verschillende Steam-accounts. In het projectbestand wordt een afhankelijkheid van SteamKit2 vermeld.\n\nLees de documentatie van het project zelf ↗\n\nSteamKit → ArchiSteamFarm\naangegeven afhankelijkheid ↗\n\nVERZAMELDE RELATIES\n\n40 labels voor bijdragers · 40 Forker-etiketten\n\nHieronder een voorbeeld van een bijdrager. Deze labels geven de relatie met de repository weer, niet een dienstverband of goedkeuring.\n\n@JustArchi@renovate[bot]@JustArchi-ArchiBot@dependabot-preview[bot]@renovate-bot@actions-gebruiker@dependabot-support@Abrynos\nWat de ontwikkelaarsgrafiek laat zien\n\nDe grafiek brengt de gepubliceerde relaties tussen bijdragers en forkers in kaart tussen genoemde projecten en GitHub-profielen. Dit zijn openbare gegevens: forks van repositories, lijsten met bijdragen, profielkoppelingen. De vraag is wat het spoor van gepubliceerde vaardigheden en relaties tussen ontwikkelaars vereist dat Valve beantwoordt, niet wat dit onderzoek heeft verzonnen. Bron-hashes worden opgeslagen in de herkomst op de kaart.\n\nOntdek het volledige netwerk ↗Brongegevens van de repository ↓\n\n02 / VERSCHILLENDE BEVOEGDHEDEN. VERSCHILLENDE BEVOEGDHEDEN.\n\nWelke toetsWaar hebben we het over?\n\nOm een spel te spelen hoeft de speler geen persoonlijke Web API-sleutel op te geven. Dat is het cruciale verschil waar deze kwestie om draait.\n\n01 / GEBRUIKERSACCOUNT\nPersoonlijke Web API-sleutel\nsteamcommunity.com/dev/apikey\n\nWordt afgegeven vanuit een gebruikersaccount voor toegestane API-aanroepen. Het aanmaken, de zichtbaarheid en het intrekken van sleutels, evenals het opsporen van misbruik, zijn kwesties die onder de accountbeveiliging vallen.\n\n02 / BACKEND VAN HET SPEL\nWeb-API-sleutel van de uitgever\n\nSteamworks-partners gebruiken de inloggegevens van de uitgever voor ondersteunde backend-bewerkingen, waaronder spelgerelateerde diensten. De persoonlijke sleutel van een speler is een ander soort inloggegeven.\n\n03 / IDENTITEIT & SESSIE\nOpenID / sessietokens\n\nOpenID bevestigt de identiteit bij een website. Een Steam-sessie- of vernieuwingstoken dient een ander doel. Deze mechanismen mogen niet worden voorgesteld als één onderling uitwisselbare „API-sleutel”.\n\nValve bevat zowel de Web API-sleutels van gebruikers als die van uitgevers. De volledige Web API staat daarom niet los van Steamworks. Documentatie over API-sleutels ↗ gearchiveerd 2026-09-15 ↗ · Authenticatie tijdens een spelsessie ↗ gearchiveerd 2026-08-29 ↗\n\nOPGESTELD DOOR DE MAKER VAN DE TOOL / MAART 2024\n\nAutomatisering kan meer gebruiken dan alleen een API-sleutel.\n\nIn de wiki van de Trade Offer Manager wordt beschreven hoe je een sessietoegangstoken kunt gebruiken voor bepaalde onderdelen van de Web API wanneer er geen aparte API-sleutel beschikbaar is. Ook wordt daarin melding gemaakt van mobiele bevestiging voor het aanmaken van sleutels vanaf eind 2023. De beheerder stelt dat het gebruik van tokens op deze manier niet wordt ondersteund door Valve; dit is een verouderde bewering in de documentatie, geen test die in de praktijk is uitgevoerd.\n\nBekijk de uitleg van de beheerder ↗ gearchiveerd 2026-09-24 ↗\n\nDE MENSELIJKE KANT / EEN ILLUSTRATIEF PHISHING-TRAJECT\n\nIk ben nog steeds aan het spelen.Al bekend.\n\nEen bericht van een vriend. Een verzoek om te stemmen. Een ‘bedankpagina’. Voor de speler is de taak volbracht. Een gehackte sessie kan echter nog langer duren dan dat moment.\n\nOP HET SCHERM VAN DE SPELER\n\nF\nHET VERHAAL VAN EEN VRIEND\n\n“Kun je op ons team stemmen?”\n\nHet verzoek komt binnen via de chat op Steam vanuit een bekend account. In dit scenario wordt de gekoppelde pagina geopend in de browser van de klant.\n\nUIT HET ZICHT\n\nHet vertrouwen ontstaat al vóór de website.\n\nEen gekaapt account van een vriend kan een phishinglink geloofwaardiger maken. De omringende interface van Steam geeft geen garantie over de betrouwbaarheid van de doelsite.\n\nBEKENDE AFZENDER / EXTERNE BESTEMMING\nDe veiligheid van het account is het belangrijkste punt voordat een artikel wordt verkocht.\n\nDe speler was niet van plan om inloggegevens voor automatisering aan te maken of de controle over te dragen. Het feit dat iemand terugkeert naar een spel, is geen bewijs dat het account veilig is. Valve bewaart de sessielogboeken, het overzicht van aangemaakte API-sleutels en de gegevens over de koppeling met apparaten. Het slachtoffer doet dat niet. Die asymmetrie vormt het probleem op het gebied van verantwoordingsplicht.\n\nToegang tot sessies en soorten inloggegevens\n\nEen API-sleutel en een ingelogde sessie zijn afzonderlijke inloggegevens met verschillende bevoegdheden. Het intrekken van een sleutel beëindigt een actieve sessie niet. In de eigen documentatie van Valve worden beide beschreven; Valve beschikt over de logbestanden waaruit blijkt welke inloggegevens actief waren op het moment van een betwiste handeling. De eis is openbaarmaking van dat verslag — niet een conclusie die het onderzoek zelf heeft verzonnen. Documentatie van de beheerder over het omgaan met tokens ↗ gearchiveerd 2026-09-24 ↗ · Valve belangrijke documentatie ↗ gearchiveerd 2026-09-15 ↗\n\n03 / DE OFFICIËLE MARKT HEEFT EEN BOVENGRENS\n\nHet voorwerp kan zeldzaam zijn.De limiet blijft van kracht.\n\nEen prijs die hoger is dan het maximale noteringsbedrag kan niet worden gerealiseerd via één notering op de Community Market tegen die volledige prijs.\n\nINDICATIEVE VRAAGPRIJS$5,000De vraagprijs van het artikel wijzigen\n$100$20,000\n\nEen illustratie van de gepubliceerde limiet; dit is geen waardebepaling of aanbeveling om te handelen.\n\nMAXIMUM AANTAL VERMELDINGEN≈ $1,800\nPORTEMONNEEHOES≈ $2,000\n\nBoven de gepubliceerde maximumgrens voor noteringen.\n\nGeld uit de wallet kan niet naar een bankrekening worden overgemaakt. Deze beperkingen zorgen voor een vraag waar de skin-marktplaatsen van derden in voorzien: een vraag die ontstaat door de limieten voor het aanbieden en de wallet, terwijl de eigen regels van Valve commerciële exploitanten verbieden hieraan te voldoen.\n\nDe marktlimieten van Steam ↗ gearchiveerd 2026-09-21 ↗\n\n04 / BINNEN DE GRENZEN VAN DE ONDERSTEUNING\n\nVerantwoordelijk voor gegevens.Verantwoordelijk voor de toegang.\n\nIn het privacybeleid van Valve is uitdrukkelijk bepaald dat persoonsgegevens mogen worden gedeeld met externe ondersteuningsdienstverleners, voor zover dit nodig is voor de ondersteuning.\n\nDE SPELERRekeningen en bewijsstukken\n→\nKLEPHerstelproces\n→\nONDERSTEUNINGSVERLENERToegang op basis van delegatie\n\nPrivacybeleid §5.2 ↗ · Het eigen beleid van Valve staat toegang door derden toe. De openstaande vragen zijn: welke rechten zijn verleend, welke controletrajecten bestaan er en wat is er gebeurd toen er naar verluidt misbruik werd gemaakt van die toegang?\n\n2015\nDe schaal was openbaar\n\nValve erkende dat er op grote schaal accounts waren gestolen en beschreef de beschermende maatregelen.\n\nValve publicatie ↗gearchiveerd 2026-08-09 ↗\n2015\nValve heeft de balie uitbesteed — en heeft dat ook gezegd\n\nValve heeft een klein intern Steam Support Leadership-team en verklaarde dat \"heb een paar verschillende bedrijven ingehuurd\" om ondersteuning te bieden (Erik Johnson, Valve, aan Kotaku); artikel 5.2 van het privacybeleid geeft deze derde partijen toestemming om toegang te krijgen tot gebruikersgegevens. Welke aannemer toegang heeft tot de functie voor het herstellen van accounts, heeft Valve nooit bekendgemaakt — In de discussie binnen de gemeenschap worden bedrijven als Concentrix genoemd, maar geen enkele daarvan is Valve-bevestigd. De uitbestede helpdesk bestond al jaren voordat een van beide onderstaande verklaringen werd afgelegd.\n\nKotaku: Valve op de ondersteuningspagina ↗gearchiveerd 2025-07-11 ↗\n2023\nDe eerste opname\n\nHet CS:GO-team van Valve neemt schriftelijk de verantwoordelijkheid op zich voor een account dat via zijn eigen hulpverzoekprocedure is gehackt, en maakt de ruiltransacties ongedaan.\n\nOpen het outsourcingdossier ↓\n2025\nDe tweede opname\n\n33 maanden later schrijft Steam Support dat een technicus „ons proces niet heeft gevolgd, waardoor uw account aan iemand anders is toegewezen”. Hetzelfde kanaal. Hetzelfde resultaat.\n\nDexerto, 14 nov. 2025 ↗\n\nDOSSIER / HFB & DE BESCHULDIGINGEN INZAKE UITBESTEDING\n\nDe toegang was Steam Support zelf.Valve heeft dat schriftelijk verklaard.\n\nIn het antwoord van de klantenservice dat door Dexerto is gepubliceerd, neemt het CS:GO-team van Valve de verantwoordelijkheid op zich voor het gehackte account via de procedure voor het indienen van een hulpverzoek — via zijn eigen kanaal, niet via een phishingpagina en niet via de gebruiker. De items werden teruggevonden en de transacties ongedaan gemaakt, wat volgens Valve de oplossing is die voor andere slachtoffers niet bestaat. De voorraad van HFB werd gerapporteerd op $2,000,000+ op die dag en $3,000,000+ in de vervolgfase; Qkss verloor op dezelfde manier $1,000,000+ en kreeg niets.\n\nREACTIE VAN DE KLANTENSERVICE / OVERGENOMEN DOOR DEXERTO · 21 FEBRUARI 2023\n“gecompromitteerd via een ondersteuningsverzoek, waarvoor het CS:GO-team de verantwoordelijkheid op zich neemt”\nLees het verslag en het weergegeven bericht ↗ gearchiveerd 2025-08-18 ↗\n01 / WELKE KLEP GING OPEN\nDe eigen ondersteuningskanaal was de manier om binnen te komen\n\nHet antwoord heeft betrekking op het gehackte account en de terugboeking van de transacties daarvan. Valve heeft ze teruggedraaid — de transacties waren dus terugdraaibaar. Het oorspronkelijke, geauthenticeerde ticket bevindt zich niet in deze verzameling.\n\n02 / WAT DE ONTSLAGEN NIET HEBBEN OPGELOST\nDiezelfde deur ging in november 2025 weer open\n\nDe aannemer heeft zijn volledige Steam-ondersteuningspersoneel ontslagen — zoals gemeld door Mzkshow via Dexerto, en niet via een Valve-personeelsverklaring. Drieëndertig maanden later schreef Steam Support aan een andere incassant dat „een ondersteuningsmedewerker die de hulpvraag behandelde, ons proces niet heeft gevolgd, waardoor uw account aan iemand anders is toegewezen.” Een citaat van Valve zelf, over hetzelfde kanaal.\n\nDe tweede opname, 14 november 2025 ↗\n03 / WAT IS OPEN\nValve heeft de aannemer nooit bij naam genoemd\n\nUit deze bronnen blijkt noch wie de aannemer was, noch waar de locatie zich bevond. Dat is geen leemte in de berichtgeving — het is een feit dat Valve niet heeft bekendgemaakt wie toegang had tot de gebruikersaccounts.\n\nHedendaags verslag van de zaak ↗\n\nDrie vragen die Valve nog niet heeft beantwoord: wie zou het herstel van een account kunnen blokkeren, wat bleek uit het toegangsonderzoek en wat is er daarna veranderd?\n\nLatere beschuldigingen in het bewaarde ondersteuningsarchief\n\nTwee Reddit-berichten uit 2024 maken melding van verdere onderzoeken door Mzkshow: een zaak uit juli 2024 betreffende de opheffing van een VAC-ban en een zaak uit december 2024 betreffende de $13,000-inventaris. Dit zijn afzonderlijk gemelde incidenten. De vraag naar de verantwoordelijkheid is in beide gevallen identiek: wie had toegang om de blokkering op te heffen, wat bracht de controle aan het licht en wat is er veranderd?\n\n14 juli 2024 · gemeld herstel / VAC-verbodzaak ↗2 december 2024 · gemeld $13,000 voorraadzaak ↗gearchiveerd 2025-08-05 ↗Twee bewaarde berichten, bronregels en hashes ↓\n\n05 / VOLG HET VERLIES\n\nElk bedragheeft een hoesje nodig.\n\nTien gevallen, juni 2022 tot maart 2026. Elk bedrag is het cijfer dat door de genoemde bron is gepubliceerd — $6,300,000, $2,000,000+, $1,000,000+, ≈$320,000, ≈$300,000, en gedaald tot € 288. Valve bewaart het transactielogboek, het sessieverslag en het ondersteuningsaudittraject voor elk daarvan, en heeft geen van deze documenten verstrekt.\n\nONDERSTEUNINGSKANAAL21 JUN 2022\n$2,000,000+\nHFB — the largest inventory in the game\n\nGERAPPORTEERDE VOORRAADWAARDERING · VERHOOGD TOT $3M+ IN DE FEBRUARI-2023-FOLLOW-UP\n\nZeven Souvenir Dragon Lores en de #1 Blue Gem Karambit; alleen dat mes al kostte ongeveer $1.26m. Drie jaar inactief, met de authenticator nog steeds ingeschakeld; e-mailadres en wachtwoord gewijzigd via de herstelprocedure van de klantenservice. Valve heeft de transacties ongedaan gemaakt — en zijn verantwoordelijkheid schriftelijk vastgelegd. Vóór de terugdraaiing was er naar verluidt al $200,000+ aan opbrengsten opgenomen via market.csgo.com, dat uitbetaalt in contanten en cryptovaluta. Bij een terugdraaiing wordt een skin teruggegeven, niet het geld dat iemand al op zijn rekening heeft gestort. De terugdraaiing leidde ook tot een storing: een koper had zijn Souvenir Dragon Lore verstopt in een opslagruimte in het spel; het script kon niet in de eigen container kijken, en Valve dupliceerde een item ter waarde van $130,000 tijdens het ongedaan maken van een diefstal — ontdekt via item-ID’s en meldingen van de community, verwijderd in juli 2022,; de koper kreeg zijn geld terug van BUFF in plaats van Valve.\n\nDexerto, de dag van de diefstal ↗\nPORTAFEL & AANKOPEN07 2022 juli\n>$500\n44 disputed Market purchases\n\nGERAPPORTEERDE UITGAVEN UIT DE PORTEMONNEE · USD\n\nEen gebruiker meldt ongeautoriseerde aankopen van Dota-2-items met een lage waarde en een onbevredigende reactie van de klantenservice.\n\nLees de klacht en bekijk de bijgevoegde schermafbeeldingen ↗\nINBREUK OP HET PLATFORM14 2022 augustus\n$6,300,000\nCS.Money — 19,000+ skins uit de bots\n\nWAARDERING · EERSTE RAMING $1.6M\n\nDe aanvallers hebben de bestanden van de mobiele authenticator van de handelsbots van de marktplaats buitgemaakt en leeggehaald, waarbij ze een deel van de buit naar bekende handelaren hebben doorgesluisd om het spoor te verdoezelen. Onderzoekers uit de community brachten binnen enkele uren 55 de accounts van de aanvallers in kaart. Valve heeft niets teruggedraaid — een site van een derde partij bevindt zich buiten Steam, aldus dezelfde Steam wiens inventaris, handelsAPI- en accountsysteem de diefstal van begin tot eind hebben gedragen.\n\nLees het verslag uit die tijd ↗\nONDERSTEUNINGSKANAALGERAPPORTEERD 21 FEB 2023\n$1,000,000+\nQkss — dezelfde deur, dezelfde acteur, tegengesteld antwoord\n\nGERAPPORTEERDE VOORRAADWAARDERING\n\nOp dezelfde manier afgehandeld als HFB, door dezelfde medewerker, via hetzelfde supportverzoek. HFB was al acht maanden eerder volledig afgehandeld. Qkss niet. In het gepubliceerde verslag is er niets dat de twee zaken van elkaar onderscheidt, behalve de omvang van het publiek.\n\nDexerto over het onderzoek naar de Mzkshow ↗\nONDERSTEUNINGSKANAALGERAPPORTEERD OP 2023\n≈ $320,000\nDe handel met voorkennis zelf — een jaar lang\n\nOPBRENGST OVER EEN PERIODE VAN ONGEVEER ÉÉN JAAR · GEEN VOORRAADWAARDERING\n\nVia de support-toegang konden we de accountgeschiedenis tot wel 15 jaar terug raadplegen: de eerste CD-sleutel, het eerste e-mailadres, de eerste betaalkaart — precies het bewijsmateriaal dat nodig is voor het herstelproces. Wie de database in handen heeft, wint altijd dat geschil tegen degene die de account beheert. Een gestolen M4A4 Howl met iBUYPOWER- en Titan Katowice-2014-holo’s werd verkocht voor $35,000 en kwam terecht bij b1t van NAVI, die hier niets van kon weten. Het antwoord van de aannemer was om alle medewerkers die bij de Steam-ondersteuning werkten, te ontslaan.\n\nEscorenews over hetzelfde onderzoek ↗\nPORTAFEL & AANKOPEN09 DEC 2023\n€288\nVerlies van portemonnee ondanks tweestapsbeveiliging\n\nTRUSTPILOT · BRONINDEX 16\n\nDe recensent meldt dat zijn account is gehackt en dat hulp bij uitgaven via Market is geweigerd. De export bevat geen individuele beoordelings-URL.\n\nControleer de herkomst van de bron ↗\nACCOUNT-HERSTEL02 DEC 2024\n$13,000\n“Matvey” — twee jaar na de ontslagen\n\nSCHATTING VAN DE VOORRAAD DOOR DE AUTEUR\n\nHerstel toegekend aan iemand die accountgegevens had verstrekt die de eigenaar zelf niet kon verifiëren. Dezelfde procedure, hetzelfde resultaat, nadat de aannemer zijn helpdesk op Steam had opgeheven.\n\nLees de bewaarde beschuldiging ↗\nACCOUNT-HERSTEL09 MEI 2025\n≈ $10,000\nHerstel via het ticket van iemand anders\n\nAANGEGEVEN VERLIES VAN EEN ARTIKEL · USD\n\nEen gebruiker uit Quebec beweert dat de klantenservice het wachtwoord heeft gereset en de accountbeveiliging heeft opgeheven op verzoek van iemand anders.\n\nLees de klacht in de eerste persoon ↗\nONDERSTEUNINGSKANAAL13 NOV 2025\n≈ $300,000\nHawkeye337 — en de tweede schriftelijke bekentenis van Valve\n\nDE VOLLEDIGE HOLO-COLLECTIE VAN KATOWICE 2014\n\nDe aanvaller eiste 1 bitcoin en begon de collectie naar Negevs te kopiëren om deze te vernietigen. Steam Antwoord van de klantenservice: “Een supportmedewerker die de hulpvraag behandelde, heeft onze procedure niet gevolgd, waardoor uw account aan iemand anders is toegewezen.” Drieëndertig maanden na de eerste bekentenis, hetzelfde verhaal. Hersteld binnen enkele uren nadat de thread trending was op X. Qkss had dat publiek niet.\n\nDexerto, 14 Nov 2025 ↗\nPORTAFEL & AANKOPEN29 MAR 2026\n$50\nOngeautoriseerde herlaadbeurten en geschonken spellen\n\nTRUSTPILOT · BRONINDEX 290\n\nDe recensent maakt melding van onbevoegde uitgaven en afgewezen verzoeken om terugbetaling. De URL van de individuele recensie ontbreekt in het exportbestand.\n\nControleer de herkomst van de bron ↗\n\nDe bronvermeldingen en bedragen blijven zoals door elke bron gerapporteerd. Valve beschikt over de transactielogboeken, sessieverslagen en het ondersteuningsaudittraject voor elk van deze gevallen. Leg deze over. Een bewaard gebleven Reddit-bericht biedt geen uitsluitsel — de eigen gegevens van Valve doen dat wel.\n\nDE COLLECTIE / NA CONTROLE\n\n231,829 accounts in de aanbieding.Valve bevat de logbestanden van iedereen.\n354 → 201\nTrustpilot-beoordelingen\n\n153 dubbele rijen verwijderd. De URL’s van de individuele beoordelingen zijn niet meegenomen in de export.\n\n231,829\nSteam accountvermeldingen\n\n33,509 geclassificeerd als zelfgeregistreerd; 198,320 onder het ‘stealer’-label van de verzamelaar. Vermeldingen zijn geen afgeronde verkopen.\n\nControle van de collectie ↓Zoek in het bronarchief ↗",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Uw account.Hun toegang.Wie neemt er op?"
          },
          {
            "level": 2,
            "id": null,
            "text": "Automatisering heefteen papieren spoor."
          },
          {
            "level": 3,
            "id": null,
            "text": "ArchiSteamFarm"
          },
          {
            "level": 2,
            "id": null,
            "text": "Welke toetsWaar hebben we het over?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Persoonlijke Web API-sleutel"
          },
          {
            "level": 3,
            "id": null,
            "text": "Web-API-sleutel van de uitgever"
          },
          {
            "level": 3,
            "id": null,
            "text": "OpenID / sessietokens"
          },
          {
            "level": 3,
            "id": null,
            "text": "Automatisering kan meer gebruiken dan alleen een API-sleutel."
          },
          {
            "level": 2,
            "id": null,
            "text": "Ik ben nog steeds aan het spelen.Al bekend."
          },
          {
            "level": 3,
            "id": "session-hidden-title",
            "text": "Het vertrouwen ontstaat al vóór de website."
          },
          {
            "level": 2,
            "id": null,
            "text": "Het voorwerp kan zeldzaam zijn.De limiet blijft van kracht."
          },
          {
            "level": 2,
            "id": null,
            "text": "Verantwoordelijk voor gegevens.Verantwoordelijk voor de toegang."
          },
          {
            "level": 3,
            "id": null,
            "text": "De schaal was openbaar"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve heeft de balie uitbesteed — en heeft dat ook gezegd"
          },
          {
            "level": 3,
            "id": null,
            "text": "De eerste opname"
          },
          {
            "level": 3,
            "id": null,
            "text": "De tweede opname"
          },
          {
            "level": 3,
            "id": null,
            "text": "De toegang was Steam Support zelf.Valve heeft dat schriftelijk verklaard."
          },
          {
            "level": 4,
            "id": null,
            "text": "De eigen ondersteuningskanaal was de manier om binnen te komen"
          },
          {
            "level": 4,
            "id": null,
            "text": "Diezelfde deur ging in november 2025 weer open"
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve heeft de aannemer nooit bij naam genoemd"
          },
          {
            "level": 2,
            "id": null,
            "text": "Elk bedragheeft een hoesje nodig."
          },
          {
            "level": 3,
            "id": null,
            "text": "HFB — the largest inventory in the game"
          },
          {
            "level": 3,
            "id": null,
            "text": "44 disputed Market purchases"
          },
          {
            "level": 3,
            "id": null,
            "text": "CS.Money — 19,000+ skins uit de bots"
          },
          {
            "level": 3,
            "id": null,
            "text": "Qkss — dezelfde deur, dezelfde acteur, tegengesteld antwoord"
          },
          {
            "level": 3,
            "id": null,
            "text": "De handel met voorkennis zelf — een jaar lang"
          },
          {
            "level": 3,
            "id": null,
            "text": "Verlies van portemonnee ondanks tweestapsbeveiliging"
          },
          {
            "level": 3,
            "id": null,
            "text": "“Matvey” — twee jaar na de ontslagen"
          },
          {
            "level": 3,
            "id": null,
            "text": "Herstel via het ticket van iemand anders"
          },
          {
            "level": 3,
            "id": null,
            "text": "Hawkeye337 — en de tweede schriftelijke bekentenis van Valve"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ongeautoriseerde herlaadbeurten en geschonken spellen"
          },
          {
            "level": 2,
            "id": null,
            "text": "231,829 accounts in de aanbieding.Valve bevat de logbestanden van iedereen."
          },
          {
            "level": 3,
            "id": null,
            "text": "Trustpilot-beoordelingen"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam accountvermeldingen"
          }
        ],
        "links": [
          "https://phishdestroy.io/live-intel/?category=steam",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/lzt.market.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-evidence-lzt.json",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://github.com/JustArchiNET/ArchiSteamFarm/blob/main/ArchiSteamFarm/ArchiSteamFarm.csproj",
          "https://github.com/JustArchi",
          "https://github.com/renovate[bot]",
          "https://github.com/JustArchi-ArchiBot",
          "https://github.com/dependabot-preview[bot]",
          "https://github.com/renovate-bot",
          "https://github.com/actions-user",
          "https://github.com/dependabot-support",
          "https://github.com/Abrynos",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/automation-map.json",
          "https://phishdestroy.io/steam_dossier/nl/output_steam_network/network.html",
          "https://phishdestroy.io/steam_dossier/nl/output_steam_network/raw_data.json",
          "https://partner.steamgames.com/doc/webapi_overview/auth",
          "http://web.archive.org/web/20260915025812/https://partner.steamgames.com/doc/webapi_overview/auth",
          "https://partner.steamgames.com/doc/webapi/ISteamUserAuth",
          "http://web.archive.org/web/20260829124950/https://partner.steamgames.com/doc/webapi/ISteamUserAuth",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "http://web.archive.org/web/20260924181824/https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://store.steampowered.com/privacy_agreement/",
          "https://store.steampowered.com/oldnews/19618",
          "http://web.archive.org/web/20260809125516/https://store.steampowered.com/oldnews/19618",
          "https://kotaku.com/valve-explains-why-steam-customer-service-is-still-terr-1736988223",
          "http://web.archive.org/web/20250711004653/https://kotaku.com/valve-explains-why-steam-customer-service-is-still-terr-1736988223",
          "https://www.dexerto.com/counter-strike-2/valve-saves-hacked-cs2-player-threatened-with-ransom-over-300000-of-rare-stickers-3283135/",
          "https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "http://web.archive.org/web/20250818113925/https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "https://lis-skins.com/ru/blog/krupneisaia-mosenniceskaia-sxema-v-istorii-steam/",
          "https://www.reddit.com/r/cs2/comments/1e38jo4/stealing_accounts_and_removing_vac_bans_a_new/",
          "https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "http://web.archive.org/web/20250805141942/https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/outsourcing-archive-records.json",
          "https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "https://escorenews.com/en/csgo/news/44087-valve-steam-support-employee-accused-of-selling-inactive-accounts-inventories-worth-six-figures-b1t-has-one-of-these-skins",
          "https://phishdestroy.io/steam_dossier/nl/PART2_RESEARCH.md",
          "https://www.reddit.com/r/GlobalOffensive/comments/1h56shi/steam_support_is_stealing_accounts/",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/design-review/part2/quality-review.json",
          "https://phishdestroy.io/steam_dossier/nl/steam_evidence_archive.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/nl/investigation_part2.content.json",
      "export_json_sha256": "bb169aa2cf3281d57546fa4a9015a899492dd7549f39b49a3d878bc5c86cb25f"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "nl/legal_analysis.html",
      "language": "nl",
      "title": "Hun voorwaarden, jouw rechten — Het dossier over de ‘Steam’",
      "source_url": "https://phishdestroy.io/steam_dossier/nl/legal_analysis",
      "source_html_sha256": "a37f5109fca3c0b09d5432b459cd8b7cdb4cc34e94f0f646caddfbaef7667182",
      "exported_at": "2026-09-29T00:18:26.218Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "legal_analysis.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/nl/legal_analysis.pdf?v=print-20260929-v5",
        "sha256": "7e72c2b7a64f998c7b2fb02ac73453d276a393115bf23a20435f9ec23a3bd062",
        "bytes": 106551,
        "pages": 8
      },
      "integrity": {
        "signed_object": "legal_analysis.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "legal_analysis.content.json.asc",
        "digest_file": "legal_analysis.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify legal_analysis.content.json.asc legal_analysis.content.json",
          "sha256sum -c legal_analysis.content.json.sha256"
        ]
      },
      "content": {
        "text": "Juridisch en economisch rapport\nJuridische analyse — Gebruiksvoorwaarden en naleving van regelgeving\n\nHun voorwaarden. Uw rechten.\n\nWAT IN DIT HOOFDSTUK WORDT AANGETOOND\n\nDeze forensisch-juridische audit beoordeelt de contractuele asymmetrie tussen Valve Corporation en Steam gebruikers in belangrijke regelgevende rechtsgebieden. Het rapport toont aan hoe de herroepbare abonnementslicentie de wettelijke eigendom van de consument ontneemt, analyseert de jurisprudentie van het Europees Hof inzake de uitputting van digitale doorverkooprechten en onderzoekt de naleving van de Digital Services Act (DSA) en artikel 15. van de GDPR. De analyse laat zien hoe geautomatiseerde handhavingsmechanismen functioneren zonder zinvolle beroepsmogelijkheden, terwijl de marktvergoedingen van het platform systematisch economische waarde onttrekken aan elke transactie tussen gebruikers.\n\n← Terug naar het Executive Briefing\n\nDit rapport bevat een juridische, economische en technische analyse van de kloof tussen de door Steam vastgestelde platformregels en de positie van de consument: geautomatiseerde handhaving met weinig mogelijkheden tot beroep, en uitgebreide controle door het bedrijf over digitale activa. Cijfers worden vermeld met bronvermelding; wanneer een cijfer niet kon worden teruggevonden in een primaire bron, is het weggelaten.\n\nVector 1\n\n\"Eigendom\" vervangen door een herroepbare licentie, zodat digitale activa op grond van de overeenkomst kunnen worden ingetrokken.\n\nVector 2\n\nGeautomatiseerde handhaving (VACNet), waarvan de verboden Steam Support aangeeft dat deze niet ongedaan kunnen worden gemaakt.\n\nVector 3\n\nControles op accounts en activa, in combinatie met een marktvergoeding van 15% CS2 (5% Steam + 10% uitgeversvergoeding), waardoor bij elke doorverkoop waarde uit het ecosysteem wordt onttrokken.\n\nAsymmetrie van termen\nAansprakelijkheidsverklaring en de herroepbare licentie\n2.1 Het ‘abonnementsmodel’ versus eigendomsrechten\n\nIn artikel 2 van de abonneeovereenkomst van Steam wordt aan gebruikers slechts een persoonlijke, niet-exclusieve, niet-overdraagbare en herroepbare licentie. Krachtens de overeenkomst kan Valve accounts te allen tijde beëindigen, en kunnen ongebruikte tegoeden in de Steam-portemonnee vervallen.\n\n2.2 De illusie van terugbetaling versus de EU-richtlijn inzake consumentenrechten\nWettelijk kader\tTerugbetalingsregeling\tBeperking\nEU Consumer Rights Directive\tUnconditional 14-day right of withdrawal on digital content\tWaived if download begins with explicit consumer consent\nSteam SSA\t14 days / under 2 hours played\tValve may deny at its discretion for \"abuse\"\nBeoordeling\n\nValve De EU-14--dag wettelijk herroepingsrecht is onderworpen aan de eigen termijn van „14 dagen / onder 2 uur”, waarmee bij het downloaden moet worden ingestemd voordat het product kan worden beoordeeld. Dit beleid beperkt — en breidt niet uit — het wettelijke recht; of dit rechtmatig gebeurt, is een vraag voor de bevoegde autoriteit, en geen conclusie die hier wordt getrokken.\n\nRechtszaken\nSecundaire markt en mededingingsrecht\nUFC Que Choisir tegen Valve — Frankrijk\n2019\nRechtbank in Parijs: het beginsel van uitputting van rechten is van toepassing op digitale games — doorverkoop is toegestaan\nokt. 2022\nHet Hof van Beroep van Parijs vernietigt de uitspraak\n23 okt. 2024\nHof van Cassatie (Hooggerechtshof): videogames zijn „complexe werken“ in de zin van de InfoSoc-richtlijn, en geen software. Digitale doorverkoop verboden. Valve heeft de overhand.\nAntitrustzaak tegen Wolfire Games — Verenigde Staten (In de zaak „Valve Antitrust Litigation”, nr. 2:21-cv-00563)\n\nDe ‘Most-Favored-Nation’ (PMFN)-clausule van het Valve verbiedt ontwikkelaars om ‘Steam’-sleutels op een ander platform goedkoper te verkopen. Concurrerende winkels — zelfs die welke 12% commissie in rekening brengen, tegenover de 30% van Valve — mogen de besparing niet doorberekenen aan de consument.\n\n336totaal aantal medewerkers van de Valve (2021). Bron: vrijgegeven bewijsmateriaal.\n79medewerkers die het volledige Steam-platform beheren. Bron: vrijgegeven bewijsmateriaal.\n$3.5Mnettowinst per werknemer. Bron: vrijgegeven bewijsmateriaal.\n\nUit openbaar gemaakte stukken blijkt dat $8.5B bruto-omzet in 2021 over de medewerkers v336. De 79-persoonSteamteam 373,000’s en dagelijkse supporttickets afgehandeld door deze door te sturen naar uitbestede, geautomatiseerde callcenters.\n\nOPENGESTELDE BIJLAGE BIJ HET DOSSIER · W.D. WASH. ZAAK2:21-CV-00563Intern memo over onderzoek\n\nTim Sweeney (CEO van Epic Games) tegen Gabe Newell: \"Waarom houdt Steam nog steeds 30% van de bruto-opbrengst in, terwijl de betalingsverwerking 2–5% kost en CDN de bandbreedte $0.002/GB kost? Als je de top 25-games op Steam buiten beschouwing laat, durf ik te wedden dat Valve meer winst heeft gemaakt op de meeste van de volgende 1,000 dan de ontwikkelaars zelf.\"\n\nInterne doorsturing van Scott Lynch (COO, Valve Corporation) aan Gabe Newell: \"Ben je boos, maat?\"\n\nWeerlegging van een beëdigde verklaring (Bloomberg, 2026): Op grond van artikel 30, lid b) (1) verklaarde Gabe Newell tijdens een getuigenverhoor dat \"Valve heeft geen beleid of praktijk waarbij het prijzen oplegt aan externe softwareontwikkelaars op andere platforms.\" De eisers confronteerden Newell met interne memo’s van Valve waaruit bleek dat er actief toezicht werd gehouden op de prijzen en dat ontwikkelaars die lagere prijzen hanteerden op concurrerende winkelsites, werden bedreigd met schrapping uit het assortiment. Eind maart 2026, wees de federale rechtbank het verzoek om een kort geding van Valve af, waardoor de collectieve rechtszaak van de ontwikkelaars van 32,000-voor een jury kwam te staan.\n2024 in november\n\nCollectieve rechtszaak toegewezen voor ~ De ontwikkelaars van32,000 die sinds januari commissies heeft betaald 2017,, plus een gelijktijdige collectieve rechtszaak van consumenten.\n\nGevorderde schadevergoeding\n\n$3.1B\nDrievoudig volgens de Amerikaanse mededingingswetgeving = $9.3B mogelijke blootstelling.\n\n2026: juni In een nieuwe rechtszaak wordt beweerd dat Microsoft en Valve een kartelovereenkomst hebben gesloten om de concurrentie op het gebied van de distributie van pc-games te beperken.\n\nFinanciële criminaliteit en AML – Formele toelating\nValve Officiële verklaring: Worldwide Fraud Liquidations (28 oktober 2019)\n\nOp 28 oktober 2019, heeft Valve de handel en doorverkoop via marktplaatsen van nieuw aangeschafte Counter-Strike-containersleutels officieel stopgezet. In haar officiële openbare verklaring (blog.counter-strike.net/2019/10/26113), Valve Corporation heeft schriftelijk toegegeven dat de virtuele economie die het had opgezet, was uitgegroeid tot een internationaal knooppunt voor het witwassen van geld:\n\n\"In het verleden vonden de meeste transacties met keys die we hebben waargenomen plaats tussen legitieme klanten. De laatste tijd maken wereldwijde fraudenetwerken echter steeds vaker gebruik van CS:GO-keys om hun winsten te gelde te maken. Op dit moment wordt aangenomen dat vrijwel alle aankopen van keys die uiteindelijk op de marktplaats worden verhandeld of verkocht, afkomstig zijn van fraude.\"\n\nRegelgevend kader: Deze bekentenis volgde op het formele ultimatum van de Washington State Gambling Commission (WSGC) aan Valve en de in juli 2016 uitgevaardigde bevelen tot staking en onthouding door Karl Quackenbush, algemeen juridisch adviseur van de Valve, aan de 23-domeinen voor skin-gokken (waaronder CSGO Lotto, CSGOLounge en OPSkins), pas nadat strafrechtelijk onderzoek naar gokactiviteiten de bedrijfsvoering van het platform in gevaar had gebracht.\n\nBevoegdheid\nEen rechthebbende in Rusland, die voor de gebruiker onbereikbaar is\n\nDe abonneeovereenkomst stelt Valve voor als een partij die weinig verplichtingen heeft en door niemand bereikbaar is: blokkades zijn permanent, bezwaren worden afgewezen en de toegang tot hele gebieden wordt ingetrokken met één enkele zin over „gesanctioneerde regio’s”. Tegenover die houding staat wat Valve doet wanneer zijn eigen commerciële belangen op het spel staan in een rechtsgebied dat het verder als lastig beschouwt.\n\nValve v. Touch Skins — vordering inzake intellectueel eigendom in de fase vóór het proces, Rusland\n1 2026 september\nValve via het Russische advocatenkantoor Melling, Voitishkin & Partners, stuurt een aanmaningsbrief voorafgaand aan de rechtszaak naar de exploitanten van Touch-skins, een grote CS2-skinwisselaar, per post en e-mail vanuit Rusland.\nRedenen\nDrie categorieën van vermeende inbreuken: exclusieve rechten op de software; rechten op het uiterlijk van de skins voor wapens, messen en handschoenen; en de handelsmerken van Valve. Het gedrag van de exploitanten wordt gekenmerkt als opzettelijk en langdurig.\nVraag\nStop onmiddellijk met de werking en verwijder alle infrastructuur — de software’s broncode, websites en socialemediapagina’s — bij gebreke waarvan Valve zich het recht voorbehoudt om bij een Russische rechtbank een rechtszaak aan te spannen wegens aanzienlijke financiële vergoeding en de zaak voor te leggen aan wetshandhaving met het oog op een strafrechtelijke beoordeling.\nResultaat\nNa ontvangst van de brief kondigde het platform aan dat het zou worden stopgezet. Dit zou de eerste keer zijn dValve juridische stappen heeft ondernomen tegen een ontwikkelaar van „skin-changers” in Rusland.\n\nGemeld door dataminer Maxim \"GabeFollower\" Poletaev (X, ~11 sep 2026) en de Russische gamingpers. Het gaat hier om een vordering in de aanloop naar een rechtszaak, niet om een daadwerkelijk ingediende rechtszaak; er is geen openbaar dossiernummer bekend. Wordt hier behandeld zoals gemeld, niet als een gerechtelijk dossier. Bronnen: dota2.ru gearchiveerd op 2026-09-24 ↗ · Shazoo.\n\nHetzelfde rechtsgebied, de andere richting\n\nValve is geen onbekende in het Russische wet- en regelgevingsstelsel. Het voldoet aan de voorschriften van Roskomnadzor: op verzoek van de toezichthouder heeft het de communitypagina’s 260en Steam, waarop verboden materiaal stond, verwijderd, en Roskomnadzor heeft publiekelijk verklaard dat Steam voldoet aan de wettelijke vereisten. De Russische „landing“-wet (Federale wet 236-FZ, van kracht sinds 2022), verplicht grote buitenlandse internetplatforms die Russische gebruikers bedienen om een lokale vestiging op te zetten en een contactaccount bij Roskomnadzor aan te maken. Valve reageert niet alleen op de verwijderingsbevelen van die toezichthouder, maar maakt nu ook gebruik van Russische juridische adviseurs en de dreiging van Russische rechtbanken om zijn skins als intellectueel eigendom te beschermen.\n\nHet platform is dus bereikbaar, capabel en komt op voor zijn rechten, zeker als het om zijn inkomsten gaat. Het contrast ligt bij de gebruiker: een betalende klant in een regio waar sancties gelden, krijgt te horen dat de relatie is beëindigd, de toegang tot de community wordt geblokkeerd totdat 2038, het ticket is afgesloten, en er bestaat geen forum waar de beslissing kan worden aangevochten — \"Ze waren maar al te blij om mijn geld aan te nemen en mijn transacties te verwerken\", aangezien de terugbetaling voor hetzelfde account vanaf hetzelfde Iraanse IP-adres een jaar eerder al was goedgekeurd (r/pcgaming, 4 aug. 2026; meer aanmaningsbrieven in de tentoonstelling over de kaarteconomie). „Valve” zet het volledige apparaat van een nationaal rechtssysteem in om een skin te verdedigen; het biedt de gebruiker die skins heeft gekocht helemaal geen procedure.\n\nValve beschouwt diezelfde rechtsbevoegdheid als een kader waarbinnen het kan handelen en aan de regels kan voldoen, telkens wanneer het belang van Valve op het spel staat — Russische raadslieden, de dreiging van Russische rechtbanken, gehoor aan verwijderingsbevelen van Roskomnadzor — terwijl het zijn verplichtingen jegens de gebruikers van die markt, en van elke andere, beschouwt als volledig buiten elk proces vallend. Het is een rechthebbende als het om zijn inkomsten gaat, en een onbereikbare partij als het om de rechten van de gebruiker gaat.\n\nBronnen: TASS (RKN: Steam voldoet aan de vereisten) · Federale wet 236-FZ.\n\nJuridisch opportunisme\nDe capitulatie inzake de arbitrageclausule\n2023 — de aanval\n\nAdvocatenkantoren (Zaiger LLC, Mason LLP) hebben via sociale media duizenden gebruikers geworven en tegelijkertijd tienduizenden individuele arbitraagevorderingen ingediend.\n\nDe onthulling van Valve\n\n$225M+\naan niet-restitueerbare arbitragekosten, nog voordat de zaak ten gronde was behandeld. Berekend op basis van de regels voor consumentenarbitrage van de American Arbitration Association (AAA) en de aanvullende bijlagen inzake massale arbitrage. Eisers, vertegenwoordigd door Zaiger LLC en Mason LLP, hebben ongeveer75,000 individuele arbitrageverzoeken ingediend tegen Valve Corp. (parallel aan antitrustvorderingen in Wolfire Games LLC e.a. tegen Valve Corp., Zaaknr. 2:21-cv-00563-JCC, W.D. Wash.). Volgens de tariefschema’s van de AAA voor consumentenzaken betaalt de beklaagde onderneming niet-restitueerbare administratieve proceskosten en waarborgsommen voor de benoeming van arbiters van circa $3,000+ per afzonderlijke zaak (75,000-aanmeldingen × $3,000 = circa $225M aan procedurekosten die vooraf moeten worden voldaan). Zie de juridische rapporten van Bloomberg Law en Reuters over de blootstelling aan massale arbitragezaken in de technologiesector (2023–2024).\n\nPeriode\tSSA-geschillenregeling\tWaargenomen effect\tResultaat\nBefore Sep 2024\tMandatory individual arbitration + class-action waiver\tIndividual litigation becomes economically irrational for users\tMass arbitration → $225M fee threat\nAfter Sep 2024\tDisputes in King County, WA courts only\tArbitration costs are avoided; cases consolidate in a single forum\tClass actions now possible\nConclusie\n\nRuim tien jaar lang verplichtte de SSA gebruikers om afstand te doen van hun recht op een juryrechtspraak ten gunste van individuele arbitrage. Nadat de massale indiening van arbitrageverzoeken dit mechanisme financieel onhaalbaar had gemaakt voor Valve, werd de SSA aangepast om geschillen door te verwijzen naar de rechtbanken van King County. De wijziging werd doorgevoerd zonder een zinvolle mogelijkheid om zich hiertegen te verzetten; het alternatief voor aanvaarding was het verlies van toegang tot aangeschafte digitale activa door het account te verwijderen.\n\nAlgoritmische handhaving\nVACNet, het vermoeden van schuld en valse positieven\nOktober 2023 — AMD Anti-Lag+\n\nDoor een update van het AMD-stuurprogramma (v23.10.1) werd Anti-Lag+ in CS2 geactiveerd, waardoor DLL-functies van het spel werden onderschept. VAC beschouwde dit als het injecteren van cheatcode en legde duizenden legitieme gebruikers een permanente ban op, voordat Valve tussenbeide kwam.\n\n2023, december — hoge DPI\n\nSpelers met een DPI van meer dan 10,000 die de camera snel draaiden, kregen een permanente schorsing. VACNet kon geen onderscheid maken tussen fysieke muisbewegingen en een \"spinbot\"-cheat.\n\nOndersteuningscategorie\tOpgegeven responstijd\tWerkelijk resultaat\nRefund requests\t50 min – 1.5 hr\tAutomatic approval (<14 days, <2 hours played)\nAccount security / recovery\t3–12 hours\tDepends on documentation provided\nContesting a VAC ban\tForm response\tComplete refusal. Support cannot reverse VAC decisions. The ban is permanent.\nOfficieel beleid inzake de ‘Valve’\n\n\"VAC-verboden zijn definitief, staan niet ter discussie en kunnen niet worden opgeheven door de ondersteuning van Steam.\"\n\nVia hetzelfde ondersteuningskanaal waar de ban is opgelegd, wordt ook de afwijzing van het verzoek om herziening meegedeeld: Steam Support geeft aan dat het een VAC-beslissing niet kan terugdraaien. Voor de gebruiker is het oordeel van het algoritme het definitieve resultaat.\n\nDe economische aspecten van wederverkoop\nBeheersing van virtuele activa en de doorverkoopvergoeding\nDe marktvergoeding van de ‘15%’ CS2 — een bedrag dat bij elke doorverkoop in mindering wordt gebracht\nIteratie\tSaldo van de koper\tDe verkoper ontvangt\tVerbrand (15%)\n1\t$100.00\t$85.00\t$15.00\n2\t$85.00\t$72.25\t$12.75\n3\t$72.25\t$61.41\t$10.84\n10\t$23.16\t$19.68\t~$3.47\nTotal\t$100 → dust\tValve collects the 15% fee on each resale. Users must add new money to keep trading.\nWijziging in de inruilregeling voor CS2 — oktober 2025\n\nZonder voorafgaande aankondiging heeft Valve de regels voor inruilcontracten in CS2 gewijzigd, waardoor het nu mogelijk is om zeldzame messen en handschoenen gegarandeerd te verkrijgen in ruil voor items van Covert-kwaliteit. De prijzen van messen daalden, de prijzen van Covert-items stegen sterk en er ontstond paniekverkoop op de hele markt.\n\nValve beroept zich op artikel 7 van de SSA — geen aansprakelijkheid voor wijzigingen in de platformregels. Gebruikers dragen het risico in een economie waarvan de regels Valve zonder voorafgaande kennisgeving of compensatie kunnen veranderen. De omvang van het gemelde marktbrede verlies is omstreden en wordt hier niet vermeld zonder primaire bron.\n\nReactie van de Europese regelgevende instanties\nUOKiK, DSA en de Wet op digitale eerlijkheid\nUOKiK — Polen, mei 2024\n\nDe Poolse mededingingsautoriteit (UOKiK) heeft een formele antitrustprocedure ingeleid tegen Valve Corporation en vijf binnenlandse uitgevers en distributeurs van videogames in verband met vermeende prijsafspraken, beperkende prijsgelijkheidsclausules en geoblockingpraktijken, waardoor Poolse consumenten tot wel 20% meer moesten betalen voor digitale games dan consumenten in naburige EER-markten. In het kader van het mededingingsonderzoek hebben inspecteurs van de UOKiK en de politie invallen bij zonsopgang en bewijsinspecties uitgevoerd in de Poolse vestigingen van binnenlandse partneruitgevers en -distributeurs (niet in dochterondernemingen vValve, aangezien Valve geen Poolse entiteit heeft). Mogelijke wettelijke boete: tot 10% van de jaarlijkse omzet. Bron: Officiële verklaring van de UOKiK: „De voorzitter van de UOKiK heeft een procedure ingeleid tegen Valve en de makers van de spellen”, 2024 mei.\n\nWet inzake digitale diensten (DSA)\n\nVereist transparantie bij geautomatiseerde moderatie. Steam publiceert geen gegevens over valse positieven of valse negatieven voor VACNet, en via het ondersteuningskanaal wordt vermeld dat VAC-beslissingen niet ongedaan kunnen worden gemaakt.\n\nWet inzake digitale rechtvaardigheid — 2026\n\nVerwachte bepalingen: blijvende toegang tot betaalde inhoud, een verbod op „dark patterns” bij het afzien van rechten, erkenning van eigendomsrechten op digitale activa en bescherming tegen permanente inbeslagname van voorraad.\n\nConclusie\nGeconstateerde discrepanties tussen de regels en de gegevens\n1\n\nDe kloof in eigendom. Gebruikers betalen de volledige prijs voor een licentie die Valve volgens de overeenkomst kan intrekken. Het Franse Hooggerechtshof (okt. 2024) oordeelde dat digitale doorverkoop niet onder de bescherming valt en heeft dit standpunt wettelijk vastgelegd.\n\n2\n\nAlgoritmische handhaving. VACNet heeft onterechte verbanningen opgelegd (AMD-stuurprogramma’s, incidenten met hoge DPI). Steam De klantenservice geeft aan dat zij een VAC-beslissing niet kan terugdraaien, dus het algoritme is het definitieve oordeel.\n\n3\n\nKostenbesparing. De marktvergoeding van 15% CS2 (5% Steam + 10% uitgeversvergoeding) leidt bij elke doorverkoop tot een waardevermindering, en de platformregels kunnen zonder voorafgaande kennisgeving worden gewijzigd; Valve wijst op grond van de SSA elke aansprakelijkheid voor dergelijke wijzigingen af.\n\n4\n\nArbitrageclausule geschrapt. De SSA schafte in september 2024, de verplichte arbitrage af, nadat massale claims Valve blootstelden aan ~$225M aan kosten. Gebruikers kregen geen reële mogelijkheid om zich aan deze wijziging te onttrekken.\n\n5\n\nSelectieve bevoegdheid. Valve heeft een Russisch advocatenkantoor (Melling, Voitishkin & Partners) ingeschakeld en gedreigd met een rechtszaak in Rusland tegen Touch Skins, terwijl het tegelijkertijd zijn verplichtingen jegens gebruikers van diezelfde markt buiten elke gerechtelijke procedure hield. Valve treedt op als rechthebbende wanneer zijn commerciële belangen in het geding zijn, en als een onbereikbare partij wanneer de rechten van de gebruiker in het geding zijn.\n\n← Deel I: Proxy omzeilen & gokkenDeel II: Toegang en verantwoording →\n\nJuridische bronnen en procesdossiers worden vermeld met verwijzing naar hun oorspronkelijke uitgevers en bewaarplaatsen. Er wordt geen aanspraak gemaakt op eigendom van de onderliggende documenten.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Juridische analyse — Gebruiksvoorwaarden en naleving van regelgeving"
          },
          {
            "level": 2,
            "id": null,
            "text": "Aansprakelijkheidsverklaring en de herroepbare licentie"
          },
          {
            "level": 3,
            "id": null,
            "text": "2.1 Het ‘abonnementsmodel’ versus eigendomsrechten"
          },
          {
            "level": 3,
            "id": null,
            "text": "2.2 De illusie van terugbetaling versus de EU-richtlijn inzake consumentenrechten"
          },
          {
            "level": 2,
            "id": null,
            "text": "Secundaire markt en mededingingsrecht"
          },
          {
            "level": 3,
            "id": null,
            "text": "UFC Que Choisir tegen Valve — Frankrijk"
          },
          {
            "level": 3,
            "id": null,
            "text": "Antitrustzaak tegen Wolfire Games — Verenigde Staten (In de zaak „Valve Antitrust Litigation”, nr. 2:21-cv-00563)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve Officiële verklaring: Worldwide Fraud Liquidations (28 oktober 2019)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Een rechthebbende in Rusland, die voor de gebruiker onbereikbaar is"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve v. Touch Skins — vordering inzake intellectueel eigendom in de fase vóór het proces, Rusland"
          },
          {
            "level": 3,
            "id": null,
            "text": "Hetzelfde rechtsgebied, de andere richting"
          },
          {
            "level": 2,
            "id": null,
            "text": "De capitulatie inzake de arbitrageclausule"
          },
          {
            "level": 2,
            "id": null,
            "text": "VACNet, het vermoeden van schuld en valse positieven"
          },
          {
            "level": 2,
            "id": null,
            "text": "Beheersing van virtuele activa en de doorverkoopvergoeding"
          },
          {
            "level": 3,
            "id": null,
            "text": "De marktvergoeding van de ‘15%’ CS2 — een bedrag dat bij elke doorverkoop in mindering wordt gebracht"
          },
          {
            "level": 3,
            "id": null,
            "text": "Wijziging in de inruilregeling voor CS2 — oktober 2025"
          },
          {
            "level": 2,
            "id": null,
            "text": "UOKiK, DSA en de Wet op digitale eerlijkheid"
          },
          {
            "level": 2,
            "id": null,
            "text": "Geconstateerde discrepanties tussen de regels en de gegevens"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/nl/#briefing-heading",
          "https://dota2.ru/news/67707-valve-cerez-uristov-napravila-krupnoj-rossijskoj-skincendzer-platforme-trebovanie-o-prekrasenii-deatelnosti/",
          "http://web.archive.org/web/20260924181657/https://dota2.ru/news/67707-valve-cerez-uristov-napravila-krupnoj-rossijskoj-skincendzer-platforme-trebovanie-o-prekrasenii-deatelnosti/",
          "https://shazoo.ru/2026/09/12/190508/valve-cerez-rossiiskix-iuristov-dobilas-zakrytiia-krupnogo-skinceindzera-dlia-cs2",
          "https://www.reddit.com/r/pcgaming/comments/1vf24lu/warning_to_all_gamersexpats_steam_took_my_money/",
          "https://phishdestroy.io/steam_dossier/nl/card_economy.html#asymmetry",
          "https://tass.ru/obschestvo/23235387",
          "https://base.garant.ru/401414628/",
          "https://uokik.gov.pl/postepowanie-wyjasniajace-w-sprawie-valve-i-dystrybutorow-gier",
          "https://phishdestroy.io/steam_dossier/nl/",
          "https://phishdestroy.io/steam_dossier/nl/investigation_part2.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/nl/legal_analysis.content.json",
      "export_json_sha256": "7fd014310693e29b99f4b850e1094f74edebbb699d81885adae9a4bc006a7095"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "nl/license_disclaimer.html",
      "language": "nl",
      "title": "Licentie · Rechten · Disclaimer — PhishDestroy",
      "source_url": "https://phishdestroy.io/steam_dossier/nl/license_disclaimer",
      "source_html_sha256": "4a091bb3e38ac8b8a555e007e25ba660bb5a3a004fcf613a3b1569573e58cf9f",
      "exported_at": "2026-09-29T00:18:27.134Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "license_disclaimer.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/nl/license_disclaimer.pdf?v=print-20260929-v5",
        "sha256": "75035423cd1b2ba2af788e7258bbd39e465fbe58336158f679e79a11326c6c07",
        "bytes": 120379,
        "pages": 11
      },
      "integrity": {
        "signed_object": "license_disclaimer.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "license_disclaimer.content.json.asc",
        "digest_file": "license_disclaimer.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify license_disclaimer.content.json.asc license_disclaimer.content.json",
          "sha256sum -c license_disclaimer.content.json.sha256"
        ]
      },
      "content": {
        "text": "PHISHDESTROYForensisch onderzoek · Valve / Steam\nLicentie · Rechten · Disclaimer\nLicentie en juridische disclaimer — Toewijzing aan het publieke domein\n\nAlle rechten zich aan de mensheid overgegeven.\n\nWAT IN DIT HOOFDSTUK WORDT AANGETOOND\n\nDit document regelt de onvoorwaardelijke toewijzing aan het publieke domein (CC0 1.0 Universal) en de MIT-softwarelicentievoorwaarden die van toepassing zijn op het PhishDestroy Steam Dossier. Alle forensische bevindingen, bewijsmateriaal, netwerkgrafieken en analytische methodologieën worden onherroepelijk in het publieke domein geplaatst voor onbeperkt gebruik op het gebied van regelgeving, rechtspraak en wetenschap wereldwijd.\n\n← Terug naar het Executive Briefing\n\nPhishDestroy doet afstand van alle rechten op dit materiaal — het reproduceren, verkopen of je naam eraan verbinden. Hieronder volgen twee documenten die in dezelfde stijl zijn geschreven: een open brief aan Valve, geschreven zoals we normaal gesproken schrijven, en een formele verklaring van afstand, opgesteld voor de instantie die de inhoud verder zal uitdragen.\n\nOnderzoek · Valve Corporation / SteamOpenbare versie — geen vervaldatum, geen herroeping mogelijk\nAFGEZIEN\nDeel ILicentie — het eigenlijke juridische gedeelte, maar dan op menselijke wijze\n\nPhishDestroy doet afstand van elk recht op dit materiaal. Nul. Weg. Klaar. Je mag het reproduceren, verkopen, je naam erop zetten, het op je baas tatoeëren, wat dan ook. Je hoeft geen bronvermelding te geven, geen DM te sturen en er wordt geen bedankkaartje verwacht.\n\nEén echte regel (ja, maar één)\n\nJij mag NIET zelf bepalen of je een terrorist bent.\n\nAls je een gebruiker bent uit Rusland of een ander land waarop OFAC-sancties van toepassing zijn, is dit materiaal NIET voor jou bedoeld. Er zijn geen mazen in de wet. Veel plezier met je sancties.\n\nWhat this means — OFAC\n\nThe Office of Foreign Assets Control, the US Treasury body that administers American sanctions programmes. “An OFAC-sanctioned country” means one those programmes cover. The phrase appears here as a condition on who this material is offered to, not as an allegation about any reader.\n\nEn als je, terwijl je in Moskou zat, je regio in de app ‘Steam’ hebt gewijzigd naar Turkije — gefeliciteerd met je creatieve kijk op aardrijkskunde. Je bent nog steeds Rus. De sancties gelden nog steeds. Dat is letterlijk waar het om gaat.\n\nDeel IIWat dit is en waarom het bestaat\n\nWe zullen meer over Valve publiceren dan een gemiddelde medewerker van Valve over zichzelf weet. Dat is geen opschepperij. Zo is het nu eenmaal gelopen.\n\nHoe zijn we hier terechtgekomen? Grappig verhaal: Steam heeft ons in feite gecreëerd. Het heeft ons grootgebracht met zijn oplichters, zijn supporttickets en zijn ecosysteem van ban-omzeiling — en nu zijn we hier. Niets voor gek. Eigenlijk best poëtisch.\n\nVoor wie het achtergrondverhaal nog niet heeft gelezen: we hebben de peperdure Europese advocaten vValve al leren kennen (Taylor Wessing, nu je het toch vraagt):\n\nhttps://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d gearchiveerd op 2026-08-21 ↗\n\nEen charmante ontmoeting. Zeker gezien hun uurtarief.\n\nWist Valve het? Ja. Wist Taylor Wessing het? Vrijwel zeker wel. Maar als je zo rijk bent, zijn wetten meer een soort sfeer dan een verplichting, toch?\n\nDat is eigenlijk al het hele antwoord.\n\nSteam We hebben jarenlang oplichters in de gaten gehouden. Niet altijd met opzet — soms kwamen oplichters gewoon door hun banden met Valve in opspraak. We willen hier niet dramatisch over doen. We willen nauwkeurig zijn. Dat is voor ons eerlijk gezegd moeilijker dan dramatisch doen — zo schrijven we nu eenmaal.\n\nIs dit een conflict?\n— Nee.\n\nKan dit worden opgelost?\n— Ja. Maar we tekenen geen geheimhoudingsverklaring en we doen niet mee aan bug bounty-programma’s voor een schijntje.\n\nWe hebben meer d4-jaar gewacht totdat ze het spoofing-probleem hadden opgelost, voordat we er publiekelijk over konden schrijven. Want als we er eerder over hadden geschreven, zou Steam zijn slachtoffergezichtje hebben opgezet, „actieve dreiging!” hebben geroepen en ons wat kleingeld hebben aangeboden om een document te ondertekenen waardoor we voor altijd hun wettelijke eigendom zouden zijn geworden. Nee, bedankt.\n\n(Overigens: Valve schendt zelf de geheimhoudingsverklaring. Hun eigen medewerkers doen dat. De mensen aan de top. Maar goed, laten we het maar over die van ons hebben.)\n\nDeel IIIOpen brief aan Valve — Echt, lees dit eens\n\nValve: als je wilt dat dit domein wordt verwijderd, stuur ons dan een e-mail. Voor dat gesprek is geen externe juridische adviseur nodig.\n\nVoor wie het nog niet weet: dr. Patrick heeft een master in internationaal handelsrecht behaald aan de Universiteit van Aberdeen en — let goed op — heeft zijn proefschrift letterlijk geschreven over IT-recht. Hij is onlangs partner geworden bij Taylor Wessing, een advocatenkantoor waarvan het hele bedrijfsmodel erop is gebaseerd om bedrijven als Valve obscene bedragen in rekening te brengen om zaken zo lang mogelijk te rekken totdat de tegenpartij geen geld of geduld meer heeft.\n\nWe nemen het hem niet kwalijk. Rijke cliënten met een schuldgevoel die per uur betalen — een slimme carrièrestap. We vinden alleen dat jij dat niet zou moeten financieren.\n\nDe deal (open aanbod, geen advocaten nodig)\n\nHet domein is het enige wat Valve realistisch gezien kan bereiken. Het onderzoek, de doorverwijzingen en de bijbehorende middelen zijn al in gang gezet — die gaan door, met of zonder het domein.\n\nAls je het domein wilt:\n\nLaat uw specialisten op het gebied van IT-recht een eerlijke prijs vaststellen.\n\n50% gaat naar de Stichting ‘SEAL’.\n\nWe schrappen het domein. Geen gedoe. Geen rechtszaak. Klaar.\n\nDit is geen dreigement. Het is een duidelijk aanbod voor het enige dat daadwerkelijk binnen handbereik ligt. Op een andere manier kom je er niet aan — zo zit de situatie nu eenmaal in elkaar.\n\nZullen we Valve rechtstreeks „schade toebrengen“? Waarschijnlijk niet op een manier die ze financieel zullen merken. Zo naïef zijn we niet. Maar we zullen het eerlijk en openlijk doen, zonder op zoek te gaan naar invloed — want die hebben we niet nodig. We willen dat de wereld ziet wat altijd al voor iedereen zichtbaar was, als je maar lang genoeg keek.\n\nWe beschikken over 5 jaar aan archiefmateriaal. Wat de advocaten van Valve tijdens de bewijsgaring hebben getoond — de gegevens die de ondersteunende agenten kunnen inzien, de vingerafdrukken, het papieren spoor dat ze ons letterlijk hebben overhandigd — is voldoende. We hoeven dit niet onbewerkt openbaar te maken.\n\nWie krijgt wat?\n\nDe toezichthouders krijgen de originelen.\n\nOnderzoekers en journalisten krijgen bewerkte versies (slachtofferverklaringen, inloggegevens van kinderen en de charmante opmerkingen van de helpdesk van Valve zijn om voor de hand liggende redenen verwijderd).\n\nOnder de getroffen accounts bevonden zich ook minderjarigen, die hierover niet op de hoogte zijn gesteld. Deze bevinding is opgenomen in het dossier voor de toezichthouder, waarbij de slachtoffermeldingen en inloggegevens zijn verwijderd, omdat deze informatie thuishoort bij een gegevensbeschermingsautoriteit en niet in een artikel.\n\nEn dan nog iets, Valve — we willen één ding duidelijk maken voordat je beslist hoe je hiermee omgaat: PhishDestroy is een community, geen persoon. Dat heb je zelf al ontdekt toen je juridische correspondentie aan de community richtte zonder de moeite te nemen om met de community te praten — je hebt er alleen maar gegevens uit gehaald en de accounts geblokkeerd.\n\nDe community heeft geen conflict met Valve. We zijn hier niet op uit geweest. De oplichters die jullie hebben gekweekt, hebben ons gevonden. We hebben ze geblokkeerd. En hier zijn we dan.\n\nDeel III-BDe middelen van de geallieerden — een opmerking specifiek gericht aan Steam\n\nWe willen openhartig zijn over de versterkingsstructuur, want doen alsof die niet bestaat, zou oneerlijk zijn.\n\nVoor zover wij de situatie in de gemeenschap begrijpen, beschikt PhishDestroy over ten minste twee partnerorganisaties die dit materiaal zullen oppakken en ermee aan de slag zullen gaan.\n\nWat dat in de praktijk betekent:\n\nZe benaderen overlappende onderwerpen elk op hun eigen manier.\n\nZe zijn onafhankelijk — ze volgen onze aanwijzingen niet, en wij die van hen evenmin. Hetzelfde algemene onderwerp, maar een andere methodologie.\n\nZe zullen NIET in actie komen op deel1.. Ze houden de situatie in de gaten.\n\nAls Valve besluit de website niet te verwijderen:\n\nJe kunt verwachten dat ze na deel 2 of deel 3. weer opduiken.\n\nZe zullen de bruikbare delen uit ons werk overnemen, deze aanvullen met hun eigen werk en het vervolgens onder hun eigen naam publiceren.\n\nDit is precies het soort situatie waarvoor de licentie in paragraaf 1 is bedoeld: het materiaal komt terecht waar het moet zijn, wordt aangevuld, wordt uitgebreid — en noch wij, noch zij zijn elkaar een bronvermelding verschuldigd.\n\n(PS voor juristen die zich afvragen hoe het zit met aansprakelijkheidsketens: die zijn er niet. Deze bronnen krijgen geen aanwijzingen, financiering of gegevens van ons. Ze lezen wat er openbaar is en trekken daaruit hun eigen conclusies. Net zoals jij dat zou kunnen doen.)\n\nWe zeggen dit niet om iemand te intimideren. We zeggen het zodat degene die aan de kant van Valve de strategie uitstippelt, over accurate informatie beschikt over hoe de informatieomgeving er daadwerkelijk uitziet.\n\nEen bron die ons materiaal gebruikt en aanvult, zou een artikel kunnen zijn. Twee bronnen die dit onafhankelijk van elkaar doen en tot vergelijkbare conclusies komen, vormen een patroon. Patronen zijn wat toezichthouders opmerken.\n\nDeel IVHet geld, de verboden, het hele circus\n\nHet zit zo met het verbod van de „Steam” op goksites en oplichters: het gaat niet om handhaving. Het gaat om het binnenhalen van inkomsten. De „Valve” strijkt het geld op, wast haar handen in onschuld, en gaat vervolgens het podium op om iedereen een keurig verhaal te vertellen over Pokémon-kaarten en honkbal.\n\nWaar compromissen aan de ondersteuningszijde zijn gedocumenteerd — waaronder de schriftelijke bekentenis van Valve in februari 2023 waarin het bedrijf de verantwoordelijkheid op zich neemt voor gecompromitteerde accounts met hoge waarde als gevolg van hulpverzoeken, en de ontslagen van ingehuurd personeel die door Dexerto en Escorenews zijn gemeld naar aanleiding van de $320k-zaak rond handel met voorkennis (Deel II, §04 · Hoofddossier §14.1) — ze zijn gebaseerd op openbare verklaringen en onderzoeksjournalistiek. Ongefundeerde geruchten dat ondersteunend personeel bijverdiensten uit gokactiviteiten haalt of een percentage ontvangt om verboden op te heffen, zijn niet in openbare bronnen vastgelegd en worden hier buiten beschouwing gelaten.\n\nOndertussen heeft Valve de mogelijkheid om skins correct bij te houden op 2017. afgeschaft. Ze hebben het zelfs op hun eigen forums besproken. Ze noemden het „maatregelen tegen gokken“ — terwijl het ecosysteem rond het gokken met skins daarna nog jarenlang miljarden via de infrastructuur van Steam bleef verwerken. Geweldige branding.\n\nWe gaan bewijzen dat:\n\nSkins zijn anoniemer dan Monero\n\nEen Peruaans kartel zou Dota-2-skins hebben gebruikt om geld te verplaatsen\n\nSteam is in feite een machine om sancties te omzeilen, met een waarde van ongeveer $7B aan „ruilkaarten“ (ja, ze hebben tegen een openbaar aanklager daadwerkelijk het woord „ruilkaarten“ gebruikt)\n\nWe hebben een filmpje over dat skins-gedoe. Je zult het wel zien.\n\nWe weten ook:\n\nHet moderatiebeleid van Reddit wordt beïnvloed door Valve\n\nSteam-gegevensinfrastructuur van derden (zoals steamid.uk) wordt beheerd door een particulier (msart) waarvan het gekoppelde zusterproject met een verbodenlijst (steambans.com archief) wordt mede beheerd door een erkende moderator van de Valve-community (killahinstinct_) — waardoor de onafhankelijke controle op platformverboden volledig binnen de invloedssfeer van de „Valve” blijft (zie „Card Economy“ §08)\n\nWat ze niet kunnen beheersen, verbieden ze\n\nValve: als je je blijft dom houden — prima. We hebben je veilige haven genoteerd. Google Analytics maakt de IP-adressen van je gebruikers sowieso anoniem. We zien wel wat er wordt verwijderd. We kunnen het alleen niet goedkoop genoeg bewijzen om de aandacht van je advocaten te trekken. Nog niet, tenminste.\n\nDeel VDat gedoe met malware — ja, we noemen het\n\nLaten we heel duidelijk zijn over de volgorde van de gebeurtenissen, want die laat precies zien wie je bent.\n\nWe maken de kwetsbaarheid in het spel NIET openbaar. We melden deze ook NIET aan Steam. Het programma vereist een geheimhoudingsverklaring, en als we die zouden ondertekenen, zouden we de getroffen gebruikers niet mogen vertellen wat er met hun accounts is gebeurd. Het doel van dit werk is juist om de mensen die hun accounts zijn kwijtgeraakt, en de toezichthouders, hierover in te lichten; een geheimhoudingsverklaring is daarmee onverenigbaar.\n\nDit is wat er werkelijk is gebeurd: deze kwetsbaarheid is in de juiste kringen praktisch een publiek geheim. We weten zeker dat onafhankelijke beveiligingsonderzoekers de volledige exploit al rechtstreeks onder de neus van de ondersteuning vSteam hebben geduwd. Dat deel is achter de rug. Jullie zijn officieel gewaarschuwd via jullie eigen formele kanalen.\n\nEn wat deed Valve? Helemaal niets. Want voor Valve staat beveiliging niet gelijk aan winst — integendeel, het is juist het tegenovergestelde. Beveiliging is een kostenpost. Zolang een dreiging geen kritieke omvang bereikt en geen catastrofale imagoschade veroorzaakt, beschouwt Valve deze niet als urgent.\n\nWat doen we dan? We maken het publiek duidelijk dat het bestaat, want „Valve is op de hoogte van een systematische malwarebedreiging en kiest er bewust voor om niets te ondernemen” is een cruciaal gegeven voor de toezichthouders die dit momenteel lezen.\n\nHet spel is gigantisch. We noemen de naam hier niet. Maar onthoud dit goed:\n\nDit is GEEN van die onbeduidende CS:GO-scriptkiddie-onzin waarbij een server je vraagt om „een stuurprogramma te installeren”. Dit is rampzalig.\n\nDit is een nachtmerrie van het kaliber Unturned: RCE zonder te klikken bij het verbinden met een server. Je sluit je aan bij een server. Je klikt nergens op. Je downloadt niets. De verbinding zelf is het aanvalsoppervlak, en je computer is volledig gecompromitteerd. Laten we eerlijk zijn: het plaatsen van een RCE en het omzeilen van lokale antivirusprogramma's door mee te liften op de vertrouwde digitale certificaten vValve is op Steam niet eens meer een noviteit. Het is praktisch een ingebouwde functie van je ecosysteem.\n\nWhat this means — zero-click RCE\n\nRemote code execution: making a program run an attacker’s code on someone else’s machine. “Zero-click” means the victim does nothing at all — no download, no opened file — beyond being connected. It is the most severe class of flaw there is.\n\nValve weet al dat dit bestaat. Maar ze beroepen zich op hun favoriete, laffe juridische maas in de wet: omdat het spel technisch gezien door een derde partij is ontwikkeld, wast Valve zijn handen in onschuld. Ze distribueren het spel, ze verwerken de betalingen, ze hosten de infrastructuur, maar wanneer een zero-click RCE miljoenen van hun gebruikers bedreigt, is hun standpunt: “Niet ons spel, niet onze aansprakelijkheid.”\n\nAls dit onvermijdelijk uit de hand loopt, zal de externe ontwikkelaar de schuld op zich nemen, en zal Valve zich eruit trekken door te doen alsof het het verantwoordelijke platform is dat heeft „geholpen” bij het oplossen van het probleem. Klassieke lafheid à la Valve. We kennen het verhaal al.\n\nWe leggen dit vast zodat toezichthouders, openbare aanklagers en journalisten precies begrijpen hoe Valve omgaat met actieve malware: door zich te verschuilen achter externe ontwikkelaars, geheimhoudingsverklaringen op te leggen en de spelers als makkelijke prooien achter te laten.\n\nEinde van de open briefHet formele register gaat van start\nFormele stijl · voor de overheid\nVerklaringWat betreft het gebruik en de rechten\n\nPhishDestroy Project- en cyberbeveiligingscoalitie\n\nDeze verklaring is bij elke inzending en elk bewijsstuk in dit dossier gevoegd. Ze is gericht aan elke autoriteit, rechtbank, toezichthouder, openbare aanklager, onderzoeker, journalist of betrokken persoon in wiens bezit het materiaal terechtkomt.\n\n1. Er gelden geen gebruiksvoorwaarden\n\n1.1 Al het materiaal dat door de Coalitie in het kader van deze verwijzingszaak is opgesteld — de feitelijke verklaringen, de analyse, de door haar opgestelde bewijsstukken, de hulpmiddelen en de bevindingen — wordt vrijgegeven ZONDER ENIGE RECHTEN TE BEHOUDEN.\n\n1.2 Iedereen mag, zonder toestemming te vragen en zonder ons hiervan op de hoogte te stellen:\n\nhet geheel of gedeeltelijk te reproduceren;\n\nhet aanpassen, bewerken, herschrijven, herstructureren of corrigeren;\n\nvertaal het;\n\nhet eruit halen zonder aan te geven dat het een uittreksel is;\n\nhet opnemen in officiële documenten, bevindingen, besluiten, pleitnota’s, rapporten of persberichten;\n\nhet presenteren als het eigen werk of de eigen bevindingen van de ontvanger;\n\ngebruik het als grondstof en gooi de rest weg;\n\nen het onder dezelfde voorwaarden aan iemand anders doorgeven.\n\n1.3 BRONVERMELDING IS NIET VEREIST EN WORDT OOK NIET VERWACHT. De Coalitie hoeft niet te worden genoemd, geciteerd, vermeld, bedankt, geraadpleegd of op de hoogte gebracht. Als materiaal uit deze verwijzing een autoriteit helpt en de Coalitie nooit wordt genoemd, IS DAT EEN VOLLEDIG BEVREDIGEND RESULTAAT en de Coalitie verklaart dit bij voorbaat, zodat de kwestie niet aan de orde hoeft te worden gesteld.\n\n1.4 Als een instantie het daarentegen handiger vindt om de Coalitie als bron te vermelden, staat het haar vrij dat te doen. De keuze ligt volledig bij de ontvanger en geen van beide opties heeft enige consequentie.\n\n1.5 Dit is een AFSTANDVERKLARING, geen aanbod tot het verlenen van een licentie. Er is geen aanvaarding voor nodig, het legt geen verplichtingen op en er kan geen inbreuk op worden gemaakt. Software die door de Coalitie wordt gepubliceerd, wordt afzonderlijk vrijgegeven onder de MIT-licentie; het onderzoek en de bevindingen worden voor zover maximaal toegestaan vrijgegeven in het publieke domein, en indien een rechtsgebied geen afstand toestaat, verleent de Coalitie een onherroepelijke, wereldwijde, royaltyvrije licentie met dezelfde strekking.\n\n2. Waarom dit in de praktijk van belang is, en niet alleen uit beleefdheid\n\n2.1 Een instantie kan terecht aarzelen om zich te baseren op materiaal dat door een externe partij is verstrekt, uit vrees dat het lijkt alsof zij in opdracht van die partij handelt of dat zij op enigerlei wijze met die partij verstrikt raakt.\n\n2.2 HIER IS NIETS WAAR JE JE AAN KUNT VASTKLAMPEN. De coalitie vraagt niets, is niets verschuldigd, houdt niets achter en koestert geen enkele verwachting. Zij kan later geen aanspraak maken op een recht, geen verdienste opeisen, geen klacht indienen wegens misbruik of bezwaar maken tegen de manier waarop het materiaal wordt gekarakteriseerd, omdat zij geen enkele basis heeft behouden om dat te doen.\n\n2.3 Een instantie die dit materiaal gebruikt, treedt dus niet op namens de Coalitie. Zij maakt gebruik van openbare informatie die toevallig door iemand anders is verzameld.\n\n3. Alles is al open\n\n3.1 Het werk van de coalitie is standaard openbaar:\n\nde onderzoeken worden openbaar gepubliceerd op https://phishdestroy.io en zijn vrij toegankelijk;\n\nde tooling is als open source gepubliceerd onder de MIT-licentie op https://github.com/phishdestroy gearchiveerd op 2026-09-11 ↗;\n\nde methodologie wordt uiteengezet in de verwijzing zelf, in bijlage A, deel A.16D, met inbegrip van het gewicht en de beperkingen van elk brontype;\n\nDe coalitie aanvaardt geen donaties en heeft dit standpunt al sinds 2018. bekendgemaakt.\n\n3.2 Het enige materiaal dat NIET wordt gepubliceerd, is materiaal dat niet op rechtmatige of veilige wijze kan worden gepubliceerd: persoonsgegevens van slachtoffers en derden, en informatie die een bron zou blootstellen aan represailles. Dat materiaal wordt vertrouwelijk aan de autoriteiten verstrekt en wordt vermeld in de bewijslijsten.\n\n3.3 De coalitie staat open voor controle van haar eigen handelen onder dezelfde voorwaarden als die gelden voor anderen, en heeft haar eigen gegevensverwerking vrijwillig ter beschikking gesteld aan de betrokken autoriteiten, inclusief een verzoek om instructies inzake de vernietiging ervan.\n\n4. Integriteit van het bewijsmateriaal\n\n4.1 Bijlagen worden bij de indiening meegestuurd of, indien aangegeven, op verzoek via een beveiligd kanaal verstrekt. Ze worden niet op een openbaar adres gepubliceerd en er mag ook geen dergelijk adres worden afgeleid: dit soort materiaal wordt rechtstreeks aan de autoriteiten verstrekt.\n\n4.2 Bij elke levering wordt een bestand met de naam SHA256SUMS meegeleverd, waarin voor elk geleverd bestand een SHA-256-samenvatting wordt vermeld, samen met een afzonderlijke OpenPGP-handtekening SHA256SUMS.asc.\n\n4.3 De ondertekeningssleutel is gepubliceerd op https://phishdestroy.io/.well-known/pgp-key.txt en op keys.openpgp.org. De ‘vingerafdruk’ ervan staat op het briefhoofd van elke inzending in deze reeks.\n\n4.4 Elke ontvanger kan op elk moment controleren of een bestand dat hij in zijn bezit heeft, inderdaad het bestand is dat is verzonden, zonder dat er wijzigingen in zijn aangebracht:\n\ngpg --verify SHA256SUMS.asc SHA256SUMS\n\nsha256sum -c SHA256SUMS\n\n4.5 Het gaat hier niet om formaliteit. Het is bedoeld om ervoor te zorgen dat, mocht de juistheid of integriteit van een bewijsstuk op een later tijdstip worden betwist, de kwestie kan worden beslecht door middel van berekeningen in plaats van door middel van argumenten.\n\n5. Bij het inschrijven — waarom de vrijstelling functioneel is en niet louter een gebaar van vrijgevigheid\n\n5.1 De autoriteit kan de door de Coalitie gepubliceerde onderzoeken tegenkomen en deze als bot, confronterend en soms satirisch ervaren. Die indruk klopt. De Coalitie schrijft bewust op die manier en biedt daarvoor geen excuses aan.\n\n5.2 HET ERKENT OOK DAT DIT NIET DE JUISTE TOON IS VOOR EEN REGELGEVENDE OF GERECHTELIJKE PROCEDURE. Een ernstige zaak mag niet in de toon van een campagne worden gebracht. Bevindingen die aan een autoriteit worden voorgelegd, moeten zonder omwegen worden vermeld, waarbij de beperkingen ervan worden erkend, en mogen de lezer niet dwingen om de toon buiten beschouwing te laten alvorens tot de kern van de zaak te komen.\n\n5.3 DAT IS PRECIES DE REDEN WAAROM DE COALITIE AFZIET VAN HET AUTEURSCHAP. De verklaring van afstand op 1 is het mechanisme waarmee de inhoud kan worden losgekoppeld van het register: de autoriteit kan het bruikbare overnemen, het in eigen bewoordingen herformuleren en elk woord dat de stijl van de Coalitie weerspiegelt, samen met de naam van de Coalitie, achterwege laten. Hierdoor gaat er niets verloren, en de Coalitie geeft hier de voorkeur aan.\n\n5.4 DE COALITIE VRAAGT TEVENS DAT HET REGISTER NIET MET DE METHODE WORDT VERWEKEN. De toon van de publicatie is strijdlustig; de onderliggende werkwijze is echter niet onzorgvuldig. In deze hele verwijzing wordt een onderscheid gemaakt tussen gevolgtrekkingen en waarnemingen, worden getuigenissen als zodanig aangemerkt, worden bronnen gewogen en worden hun zwakke punten vermeld, worden cijfers gepresenteerd met hun beperkingen, en worden punten die de coalitie niet kan bewijzen, geformuleerd als vragen aan de autoriteit in plaats van als beweringen. Waar het bewijs in strijd was met het eigen standpunt van de coalitie, heeft zij dit aangegeven — zie bijlage A, paragraaf 7, en sectie B.0 van de parallelle verwijzing.\n\n5.5 DE COALITIE LEGT HET VERBAND UIT TUSSEN HAAR WERKWIJZE EN HAAR FINANCIËN, OMDAT DEZE BEIDE ONLOSMAAKBAAR MET ELKAAR VERBONDEN ZIJN. Ze neemt van niemand geld aan — geen donaties, geen beloningen, geen klanten, geen sponsors. Juist die weigering maakt de ongezouten taal mogelijk: een organisatie die inkomsten moet beschermen, moet zich terughoudend opstellen in wat ze zegt over de partijen waarvan ze afhankelijk is. Omdat de Coalitie niets te beschermen heeft, hoeft ze zich ook niet terughoudend op te stellen.\n\nDat is ook de reden waarom de Coalitie blijft bestaan. Er is geen andere drijvende kracht. Het werk wordt gedaan omdat het nu eenmaal gedaan wordt; het houdt op zodra de mensen die het doen, ermee stoppen.\n\n5.6 De autoriteit hoeft hier niets van te accepteren. Dit wordt vermeld om te voorkomen dat de toon van het publieke optreden van de coalitie wordt opgevat als een maatstaf voor de zorgvuldigheid waarmee het materiaal dat nu aan haar is voorgelegd, is behandeld.\n\n6. Wat de coalitie biedt, in haar eigen woorden\n\nInformatie, onderzoek en observatie.\n\nEr wordt nergens een conclusie getrokken waarvoor de Coalitie niet bevoegd is. Wanneer er een gevolgtrekking wordt gemaakt, wordt dat in de verwijzing vermeld. Wanneer iets op getuigenverklaringen berust, wordt in de verwijzing aangegeven van wie die verklaringen afkomstig zijn en welke beperkingen eraan verbonden zijn. Wanneer de Coalitie een vraag niet kan beantwoorden, wordt dat eveneens vermeld en wordt aangegeven wie dat wel kan.\n\nDe Coalitie streeft niet naar een schadevergoeding, geen betaling, geen erkenning en geen uitkomst voor zichzelf of voor enig individu. Zij vraagt alleen dat de vragen die in de verwijzing zijn opgenomen, aan de Valve Corporation worden voorgelegd door een instantie die de bevoegdheid heeft om een antwoord af te dwingen.\n\nAfsluitende opmerkingAan degene die hiermee verdergaat\n\nWe willen iedereen bedanken die ervoor zorgt dat dit materiaal op de juiste plek terechtkomt. Het zal waarschijnlijk geen kort proces worden. Valve heeft diepe zakken en Taylor Wessing rekent per uur — die combinatie is er specifiek op gericht om mensen zoals jij te laten opgeven voordat ze de finish halen.\n\nWe weten wat we doen. We weten over wie we schrijven. De ‘Valve’ hebben ons gevormd — hoe zouden we hen dan niet kunnen begrijpen?\n\nPhishDestroy staat niet op gespannen voet met Valve. We hebben de enige oplichtersbende van die omvang die we zijn tegengekomen geblokkeerd — we zijn niet op zoek gegaan naar een conflict met Valve. Het bleek gewoon zo te zijn dat alle sporen naar hen leidden. Geen conflict. Gewoon een kwestie van structuur.\n\nValve De situatie rond PhishDestroy kan niet worden opgelost, omdat er niets op te lossen valt. We hebben geen band met hen. De gegevens over hun verrijkingspraktijken en buitensporige winsten zijn grotendeels openbaar — je moest er alleen maar genoeg tijd aan besteden om ze te vinden. Zie het als een encyclopedie van succes: „Hoe je sancties kunt omzeilen zodat Russische hackers onze gratis games niet kunnen pirateren (de betaalde games pirateren ze toch al niet).” Je snapt het wel.\n\nWe hebben geen auteurschap nodig.\n\nWe hebben geen bronvermelding nodig.\n\nWe hoeven niet te winnen.\n\nWe hebben iemand nodig met daadwerkelijke bevoegdheid om Valve de vragen te stellen die al in deze verwijzing staan, en die de macht heeft om een antwoord af te dwingen.\n\nDat is het. Dat is alles wat ik vraag.\n\nDe cases worden geplaatst op:\n\nhttps://steamdestroy.eth/\n\nhttps://steamdestroy.eth.limo (werkt momenteel niet — wordt indien nodig gerepareerd)\n\nJe kunt ons vinden op:\n\nhttps://phishdestroy.eth.limo/ gearchiveerd op 2026-06-27 ↗\n\nhttps://phishdestroy.eth/\n\nTwee gesigneerde voorwerpen · rechten en gepubliceerde tekst\nOndertekende vrijwaringsverklaringWat is er ondertekend en wat houdt het in?\n\nDe tekst met de rechtenverlening en de onderzoekstekst zijn hieronder afzonderlijk ondertekende JSON-objecten. Elke afzonderlijke OpenPGP-handtekening verifieert de exacte bytes van het JSON-object waarvan de naam ernaast staat vermeld. De rechtenverklaring verleent toestemmingen; de tekstmomentopname identificeert het gepubliceerde materiaal en bevat dit.\n\n1. Verklaring inzake rechten — license-rights.json\n\nOndertekend object: de volledige license-rights.json bestand met de openbare rechtenverklaring van 28 september 2026.. Hierin wordt toestemming verleend om door auteurs samengesteld dossiermateriaal te kopiëren, te publiceren, te bewerken, te vertalen, te combineren en commercieel te exploiteren zonder bronvermelding, kennisgeving of goedkeuring. Deze handtekening bevestigt de geldigheid van de rechtenverklaring; zij bevestigt niet de geldigheid van de tekst van elke webpagina of PDF.\n\nDe oorspronkelijke, ondertekende vrijgaveverklaring blijft ongewijzigd van kracht. De daarin vervatte toestemming kan niet worden ingetrokken of beperkt door de website te wijzigen, een ander bestand te publiceren of de site offline te halen. Materialen van derden blijven onderworpen aan hun eigen rechten.\n\nRechtenverklaring JSON ↗ · Handtekening van license-rights.json ↗ · SHA-256 van license-rights.json ↗\n\ngpg --verify license-rights.json.asc license-rights.json\nsha256sum -c license-rights.json.sha256\n2. Gepubliceerde tekst — dossier-text.json\n\nOndertekend object: de volledige dossier-text.json bestand. Het bevat de daadwerkelijk leesbare tekst van de geëxporteerde pagina’s in documents[].content.text, met de titel, taal, bron-URL, HTML-hash van de bron, kopteksten en verwijzingen van elke pagina. De documents De lijst bevat de exacte inventaris waarop deze momentopname betrekking heeft; de taalvarianten worden apart vermeld. Het betreft een tekstpublicatie, niet louter een lijst met hashwaarden.\n\nElke vermelding identificeert de bijbehorende lichtgewicht PDF-pagina aan de hand van de bestandsnaam en de SHA-256-waarde in documents[].pdf. De JSON-code identificeert de oorspronkelijke rechtenverklaring ook aan de hand van de URL en de SHA-256,, zodat de gepubliceerde tekst, de bijbehorende PDF en de geldende rechtenverklaring zonder giswerk aan elkaar kunnen worden gekoppeld. Gekoppelde externe databases, originele afbeeldingen en pagina’s die niet in de inventaris zijn opgenomen, zijn niet in deze tekstmomentopname opgenomen.\n\nVolledige, ondertekende JSON-tekst ↗ · Handtekening van dossier-text.json ↗ · SHA-256 van dossier-text.json ↗\n\ngpg --verify dossier-text.json.asc dossier-text.json\nsha256sum -c dossier-text.json.sha256\n\nOp de startpagina van het dossier kun je met de knoppen ‘PDF’ en ‘JSON’ het onderzoeksdossier exporteren. Op een onderliggende pagina exporteer je die pagina in de taal waarin deze is gepubliceerd. Elk JSON-bestand van een pagina heeft ook een eigen losstaande handtekening en een SHA-256-bestand, waarvan de naam expliciet wordt vermeld in de integrity object. Om de bijbehorende PDF te verifiëren, bereken je de SHA-256-waarde ervan en vergelijk je deze met de pdf.sha256 waarde in de geverifieerde JSON. De PDF is gebonden aan die digest; het bevat geen digitale handtekening in PDF-formaat.\n\n3. Afdrukbare onderzoeksbundel — steam-dossier-{language}.content.json\n\nOndertekend object: het volledige taalspecifieke JSON-bestand, inclusief de bijgevoegde hoofdstuktekst in documents[].content.text, paginabereiken per hoofdstuk, brontalen, de lijst met uitgesloten bronnen en de exacte PDF-samenvatting in pdf.sha256. De vijf aanvullende archieven met bewijsmateriaal blijven online gekoppeld en worden niet samengevoegd. De door de auteur geschreven onderzoeksteksten blijven behouden; de visuele catalogi worden vervangen door links naar de bronnen.\n\nEngels JSON ↗ · Handtekening van de vrijstaande OpenPGP ↗ · SHA-256-digest ↗\n\nDuits JSON ↗ · Handtekening van de vrijstaande OpenPGP ↗ · SHA-256-digest ↗\n\ngpg --verify steam-dossier-en.content.json.asc steam-dossier-en.content.json\nsha256sum -c steam-dossier-en.content.json.sha256\n\nOpenbare verificatiesleutel ↗\n\nVingerafdruk van de handtekening: 129F C7F3 9C40 C69D 2EF3 C329 BFCF 9E8D D295 EE01\n\ngpg --import pgp-key.txt\ngpg --fingerprint 129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01\n\nControleer of de weergegeven vingerafdruk overeenkomt met die hierboven, en verifieer vervolgens de handtekening aan de hand van de exacte JSON-bestandsnaam. Het bewerken van een ondertekende JSON-bestand wijzigt het ondertekende object en maakt de oorspronkelijke handtekening ongeldig. Een geldige handtekening identificeert de gepubliceerde bytes; het is geen onafhankelijke verificatie van de onderzoeksresultaten.\n\nPhishDestroy — openbaar onderzoek — alle rechten afgestaan aan de mensheid\n\nToegang tot OFAC-regio: verboden",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Licentie en juridische disclaimer — Toewijzing aan het publieke domein"
          },
          {
            "level": 2,
            "id": null,
            "text": "Deel ILicentie — het eigenlijke juridische gedeelte, maar dan op menselijke wijze"
          },
          {
            "level": 3,
            "id": null,
            "text": "Eén echte regel (ja, maar één)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Deel IIWat dit is en waarom het bestaat"
          },
          {
            "level": 2,
            "id": null,
            "text": "Deel IIIOpen brief aan Valve — Echt, lees dit eens"
          },
          {
            "level": 3,
            "id": null,
            "text": "De deal (open aanbod, geen advocaten nodig)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Deel III-BDe middelen van de geallieerden — een opmerking specifiek gericht aan Steam"
          },
          {
            "level": 2,
            "id": null,
            "text": "Deel IVHet geld, de verboden, het hele circus"
          },
          {
            "level": 2,
            "id": null,
            "text": "Deel VDat gedoe met malware — ja, we noemen het"
          },
          {
            "level": 2,
            "id": null,
            "text": "VerklaringWat betreft het gebruik en de rechten"
          },
          {
            "level": 3,
            "id": null,
            "text": "1. Er gelden geen gebruiksvoorwaarden"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. Waarom dit in de praktijk van belang is, en niet alleen uit beleefdheid"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. Alles is al open"
          },
          {
            "level": 3,
            "id": null,
            "text": "4. Integriteit van het bewijsmateriaal"
          },
          {
            "level": 3,
            "id": null,
            "text": "5. Bij het inschrijven — waarom de vrijstelling functioneel is en niet louter een gebaar van vrijgevigheid"
          },
          {
            "level": 3,
            "id": null,
            "text": "6. Wat de coalitie biedt, in haar eigen woorden"
          },
          {
            "level": 2,
            "id": null,
            "text": "Afsluitende opmerkingAan degene die hiermee verdergaat"
          },
          {
            "level": 2,
            "id": null,
            "text": "Ondertekende vrijwaringsverklaringWat is er ondertekend en wat houdt het in?"
          },
          {
            "level": 3,
            "id": null,
            "text": "1. Verklaring inzake rechten — license-rights.json"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. Gepubliceerde tekst — dossier-text.json"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. Afdrukbare onderzoeksbundel — steam-dossier-{language}.content.json"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/nl/#briefing-heading",
          "https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "http://web.archive.org/web/20260821155801/https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "https://phishdestroy.io/steam_dossier/nl/investigation_part2.html#outsourcing-case",
          "https://phishdestroy.io/steam_dossier/nl/#theft-ledger",
          "https://steamid.uk/",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/groups/steambans",
          "https://steamcommunity.com/id/killahinstinct_",
          "https://phishdestroy.io/steam_dossier/nl/card_economy.html#governance",
          "https://phishdestroy.io/steam_dossier/nl/license_disclaimer.html",
          "https://github.com/phishdestroy",
          "http://web.archive.org/web/20260911040557/https://github.com/PhishDestroy",
          "https://phishdestroy.io/.well-known/pgp-key.txt",
          "https://steamdestroy.eth/",
          "https://steamdestroy.eth.limo/",
          "https://phishdestroy.eth.limo/",
          "http://web.archive.org/web/20260627040219/https://phishdestroy.eth.limo/",
          "https://phishdestroy.eth/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json.asc",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json.sha256",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json.sha256?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json.sha256?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json.sha256?v=print-20260928-v3"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/nl/license_disclaimer.content.json",
      "export_json_sha256": "0a934bee768a1fa1da9b12721f83b69b9ef30f3a10ee6fdda2da09f220170f57"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "nl/market_economics.html",
      "language": "nl",
      "title": "Eén infrastructuur, twee markten — Het dossier over de ‘Steam’",
      "source_url": "https://phishdestroy.io/steam_dossier/nl/market_economics",
      "source_html_sha256": "9f54e0abd339e7c1f7960457def9742fb87b39386da8336b0e323b898619ce1a",
      "exported_at": "2026-09-29T00:18:29.490Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "market_economics.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/nl/market_economics.pdf?v=print-20260929-v5",
        "sha256": "f04e4b5bf30650434ea7f40b2a0874c6f0d35c351fcf5146e1c7a9f85ac31d32",
        "bytes": 100251,
        "pages": 8
      },
      "integrity": {
        "signed_object": "market_economics.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "market_economics.content.json.asc",
        "digest_file": "market_economics.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify market_economics.content.json.asc market_economics.content.json",
          "sha256sum -c market_economics.content.json.sha256"
        ]
      },
      "content": {
        "text": "Bijlage VII · Marktarchitectuur · 20 september 2026\nMarkteconomie — Twee economieën en het maximum voor beursnoteringen\n\nHun infrastructuur. Twee economieën.\n\nWAT IN DIT HOOFDSTUK WORDT AANGETOOND\n\nIn dit hoofdstuk wordt de systemische marktverdeling geanalyseerd die is ontstaan door de limiet van $1,800 voor noteringen op Valve en de niet-opneembare saldi in de wallets. Door onderzoek te doen naar 38 actieve externe skinbeurzen met een totale beurswaarde van ongeveer $1.28 miljard, toont het onderzoek aan dat handel op hoog niveau noodzakelijkerwijs uitwijkt naar externe schaduwplatforms, terwijl men blijft vertrouwen op de onderliggende handels- en authenticatie-infrastructuur van Steam. Hoewel commercieel gebruik formeel verboden is in de abonneeovereenkomst, faciliteert en monetiseert Valve deze tweeledige economie zonder dat er gegevens over handhavingsmaatregelen zijn gepubliceerd.\n\n← Terug naar het Executive Briefing\n\n38 actieve CS2-marktplaatsen van derden, plus die vSteam zelf. Elke skin die op een van deze platforms wordt aangeboden, moet via de voorraad van Steam en de handelsAPI worden verhandeld. De regels van Valve verbieden commerciële exploitatie van die infrastructuur. De door derden geschatte waarde van ongeveer $1.28 miljard bestaat, terwijl er geen openbaar bewijs is gevonden dat de regel daadwerkelijk wordt gehandhaafd.\n\n$1.28B\nDoor derden vastgestelde waarde · 38-platforms\n53.2M\nWeergegeven aanbiedingen · 38 externe markten\n70.1K\nSteam items die in de momentopname worden vermeld\n41×\nDoor derden vastgestelde waarde versus $31M van de Steam\nDe belangrijkste bevinding\nEén infrastructuur. Twee economieën.\n\nSteam heeft de controle over het item, de voorraad en de handel. Elke skin die op een van de onderstaande platforms wordt verkocht, moet via de handelsAPI van Steam verlopen — een structurele afhankelijkheid die direct waarneembaar is. — een structurele afhankelijkheid die direct waarneembaar is. De eigen Community Market van Valve ontvangt een provisie op de verkopen; of die provisie het ecosysteem van derden financiert of daaraan is gekoppeld, wordt hier niet vermeld.\n\nWaarom dit van belang is voor het onderzoek\n1\nAbonneerovereenkomst van Valve voor Steam verbiedt commerciële exploitatie van de infrastructuur van Steam zonder uitdrukkelijke toestemming. In de openbare registers is geen dergelijke toestemming aangetroffen voor de onderstaande platforms.\n2\nSteam beheert de identiteit (OpenID), de voorraadstatus en de uitvoering van transacties voor de beursgenoteerde waarde van derden, die ongeveer $1.28B bedraagt. Zonder de infrastructuur van Valve vindt er geen overdracht van items plaats.\n3\nDe eigen marktplaats van Steam heeft $31M genoteerd — ongeveer 1/41 van de genoteerde waarde door derden. Het prijsplafond van $1,800 houdt in dat verkopers die boven dit bedrag zitten, buiten het platform moeten verkopen tegen de waargenomen prijzen.\n4\n248 CS2-productcategorieën, die door twee of meer handelsplatforms afzonderlijk boven de bovengrens zijn geprijsd, kunnen niet tegen hun waargenomen marktprijs worden verkocht op Steam — en geen van deze producten staat daar überhaupt vermeld. De bovengrens van $1,800 zorgt voor de vraag waar externe exploitanten in voorzien.\nSteam Community Market: $31MDoor derden vastgestelde waarde: $1,276miljoen\n$1,276M · door derden opgegeven waarde — alles afhankelijk van Steam's trade API & OpenID\nSteam · $31M\n\nBron: realtime-catalogus van PriceEmpire, 20 september 2026. Vermelde waarde = som van de afgeronde vermeldingswaarden op de kaarten in de opgeslagen momentopname, Steam niet meegerekend. Geen verkoopvolume.\n\n38 actieve markten van derden · Dit hangt allemaal af van de infrastructuur van Steam\nPlatformregister\n\nDe onderstaande platforms leiden hun aanmeldingen via de OpenID van Steam en hun transacties via de WebAPI van Steam. Elk waargenomen openid.realm doorloopt de aanmeldingsprocedure van Steam; het register legt de waargenomen authenticatieroutes vast in plaats van te stellen dat een bepaalde operator geen toestemming van Valve heeft.\n\n#\tPlatform\tBeursgenoteerde waarde\tActuele aanbiedingen\tArtikelen\tSchaal\n1\tUUSkins\t$133.8M\t3.4M\t30.9K\t\n\n2\tYouPin898\t$127.5M\t5.9M\t29.2K\t\n\n3\tBuff.163\t$104M\t3.5M\t35K\t\n\n4\tMoon.Market\t$100.3M\t2.9M\t20.9K\t\n\n5\tWhite.Market\t$89.6M\t3M\t20.6K\t\n\n6\tBuff.Market\t$86.7M\t1.3M\t33.4K\t\n\n7\tEcosteam\t$82.1M\t3.3M\t30.1K\t\n\n8\tCSFloat\t$67.8M\t2.4M\t27.8K\t\n\n9\tSkin.Land\t$67.4M\t2.2M\t34.6K\t\n\n10\tLIS-SKINS\t$67.4M\t2.2M\t34.6K\t\n\n11\tC5Game\t$54.6M\t4.6M\t29.6K\t\n\n12\tHaloSkins\t$46.6M\t4.4M\t29.3K\t\n\n13\tAvan.Market\t$43.3M\t809.5K\t22.2K\t\n\n14\tWaxpeer\t$40.1M\t1M\t27.3K\t\n\n15\tSteam (official)\t$31M\t32.2M\t70.1K\t\n\n16\tCS.MONEY\t$29M\t748.9K\t28K\t\n\n17\tMarket.CSGO\t$26.3M\t1.3M\t27.6K\t\n\n18\tCS.MONEY Bot\t$25.7M\t614K\t23.8K\t\n\n19\tSkinport\t$16.3M\t3.8M\t31.1K\t\n\n20\tSkinFlow\t$14.1M\t481.8K\t23.6K\t\n\n21\tDMarket\t$12.6M\t948.2K\t35.6K\t\n\n22\tSkins.com\t$11.5M\t83.2K\t15.8K\t\n\n23\tSkin.place\t$6.9M\t380.8K\t11.4K\t\n\n24\tSkinsMonkey\t$6M\t109.4K\t11.6K\t\n\n25\tSkinBaron\t$5M\t2.1M\t21.5K\t\n\n26\tRustTM\t$3M\t33.1K\t4.9K\t\n\n27\tPirateSwap\t$2M\t859.3K\t10.5K\t\n\n28\tMannco.Store\t$1.2M\t223.7K\t11K\t\n\n29\tSkinSwap\t$1.1M\t11.4K\t4K\t\n\n30\tTradeIt\t$967.1K\t29.1K\t11.7K\t\n\n31\tLootFarm\t$896.1K\t162.5K\t28.6K\t\n\n32\tRustskins\t$714.8K\t312.5K\t6.1K\t\n\n33\tBalticSkins\t$599.2K\t28.2K\t4.5K\t\n\n34\tExeSkins\t$442.9K\t2.6K\t1.4K\t\n\n35\tRapidSkins\t$230.9K\t11.6K\t2.3K\t\n\n36\tCS.Trade\t$203K\t19K\t16.7K\t\n\n37\tKrakatoa\t$11.1K\t115\t53\t\n\n38\tShadowPay\t—\t—\t—\t—\n39\t49skins\t—\t—\t—\t—\nSteam’s prijsplafond van $1,800 · overzicht van vijf marktplaatsen · 23 september 2026\nHet prijsverschil is meetbaar.\n\nSteam stelt de waarde van de aanbiedingen op de Community Market vast op ongeveer $1,800 (de berekening is opnieuw uitgevoerd op $2,000, $2,070, $2,300 en $2,500 in cs2sh-atlas.json en geldt bij elke drempel). Artikelen die boven die prijs worden aangeboden kunnen niet tegen hun marktprijs worden verkocht via de eigen marktplaats van Valve — maar ze zijn nog steeds afhankelijk van het voorraad- en verzendsysteem van Steam, waar ze ook worden verkocht. Als je de hele catalogus op prijs indeelt, wordt duidelijk waar de grens ligt: de markt van Valve omvat 95.3% van de artikelcategorieën waarvan de prijs onder de bovengrens ligt en 1.9% van de daarboven gelegenen.\n\nVijf marktplaatsen: artikelen die boven de limiet van Steam liggen\n248\n\nProductcategorieën waarvan de goedkoopste vraagprijs $1,800 bedraagt op twee of meer marktplaatsen afzonderlijk, met in totaal 18,394 vermelde exemplaren met een waarde van ten minste $78.6M. Daarvan, 100.0% — stuk voor stuk — staan helemaal niet vermeld op Steam.\n\nVolledige bewijsstukken: het register → · de prijsladder-atlas →\n\nPrijsverdeling boven de bovengrens\n$1,800–$5,000\n174\n$5,000–$10,000\n49\n$10,000–$25,000\n21\n$25,000–$50,000\n2\n$50,000+\n2\nTopartikelen — de goedkoopste bevestigde vraagprijs op vijf marktplaatsen\n1Sticker | Titan (Holo) | Kat. '14'$66,285\n2Sticker | iBUYPOWER (Holo) | Cat. '14'$64,795\n3Sticker | Reason Gaming (Holo) | Kat. '14'$42,899\n4★ Sporthandschoenen | Hedge Maze (FN)$26,812\n5Sticker | Team Dignitas (Holo) | Kat. '14'$23,667\n6EMS Kat. '14-legendes'$22,879\n7★ Sporthandschoenen | Pandora's Box (FN)$21,643\n8EMS Kat. '14-deelnemers'$21,010\n9Sticker | Vox Eminor (Holo) | Kat. '14'$18,619\n10★ StatTrak™ Navaja-mes | Blue Steel (FN)$18,064\n\nVraagprijzen zijn geen verkoopprijzen. Overzicht van erkende cs2.sh, 23 september 2026. Elke rij is door ten minste twee marktplaatsen onafhankelijk van elkaar boven de bovengrens genoteerd; vraagprijzen voor één plank en noteringen die meer dan drie keer zo hoog zijn als de goedkoopste vraagprijs van een artikel, zijn uitgesloten. Hoe de beoordeling werkt →\n\nWat Valve in rekening brengt · erkend cs2.sh overzicht · 23 september 2026\nHet vermelde tarief bedra15%.. Bij de meeste vacatures ligt het salaris hoger.\n\nValve houdt een vergoeding van 5% Steam en een 10% CS2-uitgeversvergoeding in op de opbrengst van de verkoper — de bekende 15%. Beide vergoedingen zijn gekoppeld aan een Minimaal $0.01, dus bij geen enkele verkoop mogen de kosten ooit lager uitvallen dan twee cent. Bij de goedkope artikelen met een hoog volume, die het grootste deel van de markt uitmaken, vormt die ondergrens de bepalende factor, niet het percentage. We hebben de berekening van de kosten uitgewerkt voor elk van de 29,635 artikeltypen waarvoor een live Steam-aanvraag geldt.\n\n77.7%\nvan actuele Steam-advertenties zijn ondergebracht in de bovengenoemde productcategorieën 15%\n84.8%\nvan het artikel soorten betaal wel ongeveer het nominale tarief\n4,517\nsoorten artikelen waarvoor meer in rekening wordt gebracht dan de geadverteerde prijs\n$0.02\nminimumvergoeding bij elke verkoop, ongeacht de prijs\nDe twee getallen wijzen in tegengestelde richtingen, en beide zijn waar\n1\nGeteld per soort artikel, De tarieven van Valve komen grotendeels overeen met wat er wordt geadverteerd: 84.8% van de 29,635 geprijsde typen worden in rekening gebracht tegen of rond 15%.\n2\nGeteld op basis van de daadwerkelijke vermelding, dan keert het beeld zich om: 18,682,244 van 24,038,911 Actuele tarieflijsten voor bepaalde soorten artikelen zijn te vinden op 15%.\n3\nBeide zijn waar, want de types die te veel in rekening worden gebracht, zijn de goedkoop, grote hoeveelheden die. 1,109 voor bepaalde soorten artikelen wordt meer in rekening gebracht dan dubbel het basispercentage, en alleen al die soorten worden vermeld in de actuele aanbiedingen op 14,083,486.\n4\nDit is rekenwerk, geen bewering. Het minimum staat vermeld in de eigen tariefdocumentatie van de Valve. Wat niet is gepubliceerd, is op welk deel van de markt dit daadwerkelijk van toepassing is — en dat is precies wat de bovenstaande cijfers weergeven.\nIn rekening gebrachte vergoeding, als percentage van de nominale 15%\n200%+\n14,083,486\n100-200%\n1,028,438\n50-100%\n700,804\n30-50%\n317,031\n20-30%\n2,258,254\n17.6-20%\n294,231\n\nDe ‘bar-lengte’ is het aantal actieve aanbiedingen in elke bandbreedte. Een bandbreedte van ‘200%+’ betekent dat de in rekening gebrachte vergoeding meer dan het dubbele bedraagt van 15% van de opbrengst van de verkoper.\n\nEen uitgewerkt voorbeeld\n67%\n\nBij een advertentie betaalt een koper $0.03 want de verkoper ontvangt $0.01 en Valve duurt $0.02 — de twee minimumbedragen van één cent. Als percentage van het bedrag dat de koper heeft betaald, is dat 67%; als percentage van de opbrengst van de verkoper is dat 200%.\n\nVolledige dataset: cs2sh-steam-fee-census.json →\n\nHetzelfde voorwerp, zowel in de tuin als daarbuiten\nKopen via Steam is duurder. Bijna altijd.\n\nVoor elk artikel dat zowel op Steam als op ten minste één marktplaats van een derde partij werd aangeboden, hebben we de goedkoopste vraagprijs op Steam vergeleken met de goedkoopste vraagprijs daarbuiten. Over de hele linie 28,700 artikelen; Steam is de duurdere optie 86.4% meestal, met een mediaan van +35.7%.\n\nMediaanSteampremie, per prijsklasse\nminder dan $0.50\n+48.3%\n$0.50-2\n+36.5%\n$2-10\n+29.6%\n$10-50\n+28.6%\n$50-250\n+36.3%\n$250-1k\n+51.1%\nmeer dan $1,000\n+67.9%\n\nDe curve is U-vormig. Het is het goedkoopst om te kopen op Steam in de $10–$50 band en geliefde aan beide uiteinden.\n\nWaarom het duurdere segment ertoe doet\n+67.9%\n\nHierboven $1,000, de gemiddelde Steam-advertentiekosten 67.9% meer dan het goedkoopste aanbod daarbuiten — en er zijn slechts 1,040 van dergelijke advertenties op Steam te vinden.\n\nVanaf ongeveer $1,800 is een vergelijking niet meer mogelijk, omdat de regel van Valve de vermelding volledig verbiedt. De dekking van Steam voor artikelen boven de eigen limiet is 1.9%. Bekijk de volledige ranglijst →\n\nVolledige dataset: cs2sh-walled-garden-premium.json →\n\nEen premie is op zichzelf nog geen conclusie: Steam biedt onmiddellijke levering en geen tegenpartijrisico, en kopers zijn redelijkerwijs bereid daarvoor te betalen. Wat wel meetbaar is, is de omvang van het verschil en het feit dat het geld dat dit verschil overbrugt, niet meer terug kan komen — en dat is het onderwerp van de volgende paragraaf.\n\nEr komt geld binnen, er gaat geen geld uit\n128.1 miljoen dollar is vastgelegd voor bestellingen die niet kunnen worden geannuleerd.\n\nEen ‘Steam’-kooporder is vooraf gefinancierd: het geld wordt van de portemonnee van de koper afgeschreven op het moment dat de order wordt geplaatst. Steam portemonneegeld kan niet worden ingetrokken — ze kunnen alleen binnen Steam worden uitgegeven. Door alle prijsniveaus in het koopboek van elk bijgehouden item bij elkaar op te tellen, krijg je een overzicht van het vastgelegde, niet-opneembare geld.\n\n$128.1M\ntoegewijd aan het openhouden vSteam-kooporders\n170.6M\nlopende, individueel gefinancierde kooporders\n$105.8M\nde vraagprijs van de te koop staande woningen die ze voor zich zien\n$15.9M\nHet aandeel van Valve als alle objecten tegen de vraagprijs zouden worden verkocht\nWat dit cijfer wel is, en wat het niet is\n1\nHet is reëel geld dat al is gestort. Elke geregistreerde dollar is van een portemonnee afgeschreven en staat te boek tegenover een openstaande order voor verschillende 31,253-productsoorten.\n2\nHet is geen inkomsten en geen uitspraak over de balans van de Valve. Waar de float wordt aangehouden en op wiens balans deze staat, wordt hier niet vastgesteld.\n3\nHet is een momentopname, geen stroom. Bestellingen kunnen door de koper worden geannuleerd, waarna het bedrag wordt teruggestort naar de wallet — maar nog steeds niet uit Steam.\n4\nDe eenrichtingsdeur is juist het punt. Een marktplaats waarvan de valuta niet kan worden verzilverd, is de reden waarom gestolen voorraad wordt omgezet uit Steam in plaats van erop.\n\nMethode: elk prijsniveau van elk gevolgd koopboek, vermenigvuldigd met de orders die op dat niveau staan. Volledige dataset: cs2sh-steam-locked-capital.json →\n\nGerealiseerde verkopen, geen vraagprijzen · één marktplaats · de afgelopen 90 dagen\nEr werd daadwerkelijk $30.9 miljoen uitgewisseld — op de kleinste van de vijf planken.\n\nEen enkele verkoop tegen een hoge prijs kan een zeldzaam handgemaakt exemplaar zijn of een variant met een sticker op een goedkoop basisitem (bijvoorbeeld: e.g, een item van $30 met een eenmalige voltooide verkoop van $9,772). \"Hoog\" = de hoogste voltooide transactie, niet de normale prijs van het item.\n\nAlle andere cijfers op deze pagina geven weer wat vermeld. Deze meet wat verkocht. Skinport publiceert zijn eigen afgeronde transacties, en over de afgelopen 90 dagen kwamen deze uit op 1,219,143 verkoop waarde $30,927,032, voor gemiddeld $25.37 per stuk.\n\n1.22M\ngerealiseerde omzet in 90 dagen, één marktplaats\n$30.9M\nomzet in dezelfde periode\n$125M\njaarlijkse run rate — een ondergrens, geen schatting\n~2%\nHet aandeel van Skinport in de boven de limiet liggende voorraad, uitgedrukt in beurswaarde\nWaar de omzet vandaan kwam\nminder dan $1\n0.5%\n$1-10\n5.8%\n$10-100\n22.2%\n$100-1k\n59.4%\n$1k-1.8k\n6.9%\nboven de limiet van de „Steam”\n5.3%\n\nDe lengte van de balk geeft de omzet weer; het getal geeft het aandeel van die categorie in het totaal weer. 59.4% van het geld dat is verhandeld in de $100–$1k-categorie, op 71,437-verkopen.\n\nBoven de pet vanValve worden er nog steeds verkopen gedaan\n492\n\ngerealiseerde verkopen van artikelen waarvan de prijs hoger was dan de limiet van Steam, ter waarde van $1,643,938, verspreid over 76 verschillende productsoorten — op een marktplaats die ongeveer 2% van dat assortiment in zijn aanbod heeft. Geen van die verkopen had kunnen plaatsvinden op Steam.\n\nVolledige dataset: cs2sh-offsteam-90d-dynamics.json → · de bereikte hoogtepunten →\n\nSkinport is ÉÉN van de hier bijgehouden markten van derden, en met een beurswaarde die boven de limiet van Steam ligt, is het de kleinste van de vijf (ongeveer 2% van dat segment). Elk totaal hier is een ondergrens voor de off-Steam-economie, geen maatstaf ervoor. Er worden geen gegevens van Steam gebruikt.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Markteconomie — Twee economieën en het maximum voor beursnoteringen"
          },
          {
            "level": 2,
            "id": null,
            "text": "Eén infrastructuur. Twee economieën."
          },
          {
            "level": 2,
            "id": null,
            "text": "Platformregister"
          },
          {
            "level": 2,
            "id": null,
            "text": "Het prijsverschil is meetbaar."
          },
          {
            "level": 3,
            "id": null,
            "text": "Vijf marktplaatsen: artikelen die boven de limiet van Steam liggen"
          },
          {
            "level": 3,
            "id": null,
            "text": "Prijsverdeling boven de bovengrens"
          },
          {
            "level": 3,
            "id": null,
            "text": "Topartikelen — de goedkoopste bevestigde vraagprijs op vijf marktplaatsen"
          },
          {
            "level": 2,
            "id": null,
            "text": "Het vermelde tarief bedra15%.. Bij de meeste vacatures ligt het salaris hoger."
          },
          {
            "level": 3,
            "id": null,
            "text": "In rekening gebrachte vergoeding, als percentage van de nominale 15%"
          },
          {
            "level": 3,
            "id": null,
            "text": "Een uitgewerkt voorbeeld"
          },
          {
            "level": 2,
            "id": null,
            "text": "Kopen via Steam is duurder. Bijna altijd."
          },
          {
            "level": 3,
            "id": null,
            "text": "MediaanSteampremie, per prijsklasse"
          },
          {
            "level": 3,
            "id": null,
            "text": "Waarom het duurdere segment ertoe doet"
          },
          {
            "level": 2,
            "id": null,
            "text": "128.1 miljoen dollar is vastgelegd voor bestellingen die niet kunnen worden geannuleerd."
          },
          {
            "level": 2,
            "id": null,
            "text": "Er werd daadwerkelijk $30.9 miljoen uitgewisseld — op de kleinste van de vijf planken."
          },
          {
            "level": 3,
            "id": null,
            "text": "Waar de omzet vandaan kwam"
          },
          {
            "level": 3,
            "id": null,
            "text": "Boven de pet vanValve worden er nog steeds verkopen gedaan"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/nl/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/nl/elite_skins.html",
          "https://phishdestroy.io/steam_dossier/nl/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/nl/skin_atlas.html#grading",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-steam-fee-census.json",
          "https://phishdestroy.io/steam_dossier/nl/skin_atlas.html#cliff",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-walled-garden-premium.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-steam-locked-capital.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-offsteam-90d-dynamics.json",
          "https://phishdestroy.io/steam_dossier/nl/skin_atlas.html#highs"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/nl/market_economics.content.json",
      "export_json_sha256": "b69247f0b72747a6c0e9b819b4f040ef88c83505ca0b8f2e30ea22653bd49a5e"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "nl/regulatory_act_print.html",
      "language": "nl",
      "title": "WET OP DE FORENSISCHE CONTROLE: Valve Steam WebAPI-ecosysteem en commerciële exploitatie (Ref.: VAL-REG-2026-09)",
      "source_url": "https://phishdestroy.io/steam_dossier/nl/regulatory_act_print",
      "source_html_sha256": "7218607078a310c078bcd9bcc2ea90fb90e067c850020bc19d81d86a1f718376",
      "exported_at": "2026-09-29T00:18:29.497Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "regulatory_act_print.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/nl/regulatory_act_print.pdf?v=print-20260929-v5",
        "sha256": "114686c524cd32345110025080166369cc72b95b28e4bda941ef5b7638182e2c",
        "bytes": 185026,
        "pages": 14
      },
      "integrity": {
        "signed_object": "regulatory_act_print.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "regulatory_act_print.content.json.asc",
        "digest_file": "regulatory_act_print.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify regulatory_act_print.content.json.asc regulatory_act_print.content.json",
          "sha256sum -c regulatory_act_print.content.json.sha256"
        ]
      },
      "content": {
        "text": "phishdestroy.io · Forensic Research Coalition · Universal Public Record\nZAAKNUMMER: VAL-REG-2026-09-EVID\nHERKOMST: phishdestroy.io/steam_dossier/\nRECHTEN: ALLE RECHTEN ZIJN AABGESTANDEN AAN DE MENSHEID\nWet op de forensische controle en bijlage met regelgeving\nSystematische provisioning van derdepartij-APIs, geautomatiseerde bypass-architectuur en contractuele niet-handhaving in het ecosysteem van de Valve Steam\nUitgevend domeinphishdestroy.io\nDoelplatformValve Steam / Steamworks\nPrimaire authenticatievectorSteam OpenID 2.0 / Web API\nJuridische vermeldingAll Rights to Humanity (CC0)\nDeel I: Memo van de directie en feitelijke bevindingenREF: MEMO-SAMENVATTING-01\n\nDit document vormt een formeel forensisch auditverslag waarin het operationele raakvlak wordt onderzocht tussen de door Valve Corporation gepubliceerde commerciële voorwaarden, haar technische authenticatie-eindpunten en waargenomen commerciële platforms van derden. De audit werd uitgevoerd aan de hand van passieve, niet-geauthenticeerde netwerkobservatie, verificatie van registraties op RDAP en openbare telemetriegegevens van Link Filter.\n\nFeitelijke kern: Uit empirische waarnemingen blijkt dat er een systematische discrepantie bestaat tussen de publieke contractuele toezeggingen van Valve en haar productie-infrastructuur. Hoewel de abonneeovereenkomst (SSA) van Steam ongeoorloofde commerciële exploitatie (§ 2.G), geautomatiseerde interactie via bots of scripts (§ 4.C) en accountoverdracht (§ 1.C) strikt verbiedt, blijft Valve Corporation live, programmatische OpenID-authenticatie en infrastructuur voor het opvragen van voorraadgegevens aanbieden aan ten minste 175 commerciële entiteiten die secundaire transactievolumes van meerdere miljarden dollars genereren.\n\n175\nGecontroleerde commerciële exploitanten\n44\nAuth-hosts met afzonderlijke domeinen\n26\nFilter-split-proxyparen\n100%\nNiet-toegepaste SSA § 2.G / § 4.C\n0\nVerplichte intrekkingen van authenticaties\nToepasselijk contractueel en wettelijk kader\nSSA § 2.G\nVerbod op commercieel gebruik: Het is uitdrukkelijk verboden om de Inhoud en Diensten voor commerciële doeleinden te gebruiken zonder voorafgaande schriftelijke toestemming van Valve Corporation.\nSSA § 4.C\nBeperking inzake automatisering: Het is ten strengste verboden om scripts, handelsbots, macro’s of niet door mensen bestuurde systemen te gebruiken die interactie aangaan met de diensten en markten van Steam.\nSSA § 1.C\nVerplichting inzake persoonlijk gebruik: Beperkt accounts tot persoonlijk gebruik; verbiedt uitdrukkelijk het verkopen, verhuren, overdragen of verhandelen van Steam-gebruikersaccounts.\nEU DSA (2022/2065)\nBeoordeling van systeemrisico’s (art. 34/35): Zeer grote onlineplatforms (VLOP’s) moeten systeemrisico’s die voortvloeien uit geautomatiseerd misbruik en ongeoorloofde commerciële exploitatie actief opsporen, beoordelen en beperken.\nDeel II: Bijlage A — Gedocumenteerde koppelingen van gesplitste paren (routes van het 26)REF: EX-SPLIT-LEDGER\n\nForensische analyse van ontwijkingstechnieken met gesplitste domeinen: In het linkfiltersysteem van Valve( Steam ) (steamcommunity.com/linkfilter/?url=...), wanneer een eindgebruiker op een link klikt die naar een gemarkeerd gok- of zwarte-marktplatform leidt, geeft Valve een opvallende waarschuwing weer (\"Link geblokkeerd! ... gemarkeerd als mogelijk schadelijk\"). Uit forensisch onderzoek naar de route blijkt echter dat er 26 commerciële platforms actief zijn op een architectuur met gesplitste domeinen: hoewel het primaire commerciële domein in het Link Filter als BLOCKED is gemarkeerd, wordt het secundaire domein waarop het OpenID-retour-eindpunt van Valve wordt gehost, als CLEAN aangemerkt. De OpenID-servers van Valve accepteren zonder onderbreking authenticatieverzoeken van deze proxyhosts, waardoor de veiligheidswaarschuwing voor gebruikers wordt geneutraliseerd terwijl het inloggen gewoon doorgaat.\n\n#\tHoofddomein voor commerciële doeleinden\tHoofdfilter\tOpenID-authenticatieproxy-domein\tAuth-filter\tRDAP Geregistreerd\tGrondslagen voor de vastlegging\n01\trollbit.com\tBLOCKED\trbsnin.com\tCLEAN\t2026-09-18\tPASSIVE_CAPTURE\n02\tskin.club\tBLOCKED\tsc-auth.net\tCLEAN\t2019-04-02\tPASSIVE_CAPTURE\n03\thowl.gg\tBLOCKED\thowl.uno\tCLEAN\t2026-08-11\tPASSIVE_CAPTURE\n04\tduelbits.com\tBLOCKED\tswitchflips.com\tCLEAN\t2020-04-21\tPASSIVE_CAPTURE\n05\tcsgofast.com\tBLOCKED\tsteam-login.authtofast.com\tCLEAN\t2026-06-30\tPASSIVE_CAPTURE\n06\tfarmskins.com\tBLOCKED\tsteam.kobal.cc\tCLEAN\t2017-01-07\tPASSIVE_CAPTURE\n07\tcobaltlab.tech\tBLOCKED\tcobaltauth.com\tCLEAN\t2025-01-07\tPASSIVE_CAPTURE\n08\tcsgo.net\tBLOCKED\tcn2.easylot.net\tCLEAN\t2016-09-03\tPASSIVE_CAPTURE\n09\tggdrop.com\tBLOCKED\tggauth.com\tCLEAN\t2023-05-03\tPASSIVE_CAPTURE\n10\trustchance.com\tBLOCKED\thgfuihd.com\tCLEAN\t2019-01-27\tPASSIVE_CAPTURE\n11\tskin.fans\tBLOCKED\tauth.skinfans.com\tCLEAN\t2018-07-16\tPASSIVE_CAPTURE\n12\tskinport.com\tBLOCKED\tskinport.app\tCLEAN\t2020-06-20\tPASSIVE_CAPTURE\n13\tskins.cash\tBLOCKED\tskinscash.live\tCLEAN\t2019-12-05\tPASSIVE_CAPTURE\n14\ttf2hunt.com\tBLOCKED\trstspcl.com\tCLEAN\t2020-08-08\tPASSIVE_CAPTURE\n15\tdaddyskins.com\tBLOCKED\tgo-go-daddy.com\tCLEAN\t2019-01-26\tPASSIVE_CAPTURE\n16\tkey-drop.com\tBLOCKED\tkdauth.com\tCLEAN\t2026-05-13\tPASSIVE_CAPTURE\n17\tclash.gg\tBLOCKED\tclggauth.com\tCLEAN\t2024-09-16\tPASSIVE_CAPTURE\n18\tc5game.com\tBLOCKED\twww.imbastar.com\tCLEAN\t2016-02-27\tPASSIVE_CAPTURE\n19\tswap.gg\tBLOCKED\tswapauth.com\tCLEAN\t2018-10-06\tPASSIVE_CAPTURE\n20\tshadowpay.com\tBLOCKED\tthelogins.com\tCLEAN\t2018-01-22\tPASSIVE_CAPTURE\n21\tcsgocases.com\tBLOCKED\tlog-1n.com\tCLEAN\t2017-11-27\tPASSIVE_CAPTURE\n22\tcsgogem.com\tBLOCKED\tapi.csgem.com\tCLEAN\t2014-03-08\tPASSIVE_CAPTURE\n23\tgamdom.com\tBLOCKED\tlogin.gambldom.com\tCLEAN\t2017-09-24\tPASSIVE_CAPTURE\n24\t12cs.fail\tBLOCKED\tfail.games\tCLEAN\t2021-08-24\tPASSIVE_CAPTURE\n25\tskinsnipe.com\tBLOCKED\tpricing.tradeupspy.com\tCLEAN\t2020-03-11\tPASSIVE_CAPTURE\n26\tcsgobig.com\tBLOCKED\tletmeinbig.com\tCLEAN\t2023-01-20\tPASSIVE_CAPTURE\n\n* Opmerking: Passieve controles uitgevoerd op niet-geauthenticeerde eindpunten van het Steam Link Filter op 2026-09-19 en 2026-09-21.. De ruwe HTTP-antwoordteksten en SHA-256-digests worden bewaard in de dataset van de repository (steam_tos_assets/linkfilter-2026-09-22.json).\n\nDeel III: Bijlage B — Uitgebreide inventarisatie van door de „175” gecontroleerde commerciële entiteitenREF: EX-175-MASTER-CENSUS\n\nHet volgende register bevat alle commerciële platforms van derden op 175 die actief zijn geverifieerd in de auditdatabase. Elk record vermeldt de naam van de entiteit, het primaire commerciële domein, de waargenomen Steam OpenID-authenticatieroute, de activiteitsclassificatie, toewijzingen van contractbreuken (SSA § 2.G, SSA § 4.C, SSA § 1.C) en het actieveld dat in de brondataset is vastgelegd. Het label „Zie gedateerd bewijs“ verwijst de lezer naar ondersteunende documenten; het betekent niet dat Valve geen actie heeft ondernomen. Een ontbrekend actieveld wordt gerapporteerd als „niet vastgesteld“.\n\nTentoonstelling\tNaam van de entiteit en hoofddomein\tWaargenomen authenticatieroute / proxy\tClassificatie\tContractbreuk\tValve Actie\nEX-001\tCSGORoll\ncsgoroll.com\n\t\nwww.csgoroll.com\nDIRECT\n\tSkin Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-002\tCSGOEmpire\ncsgoempire.com\n\t\ncsgoempirelogin4.com\nSPLIT PROXY\n\tCasino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-003\tRollbit\nrollbit.com\n\t\nrbsnin.com\nSPLIT PROXY\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-004\t500 Casino\n500.casino\n\t\nfivezerozero.co\nSPLIT PROXY\n\tLicenced Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-005\tCSGOBig\ncsgobig.com\n\t\ncsgobig.com\nDIRECT\n\tRoulette/Slots\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-006\tCaseDrop\ncasedrop.com\n\t\ncasedrop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-007\tRustReaper\nrustreaper.com\n\t\nrustreaper.com\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-008\tBanditCamp\nbanditcamp.com\n\t\nbanditcamp.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-009\tSkinBox\nskinbox.com\n\t\nskinbox.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-010\tTastyDrop\ntastydrop.com\n\t\ntastydrop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-011\tCSGOPolygon\ncsgopolygon.gg\n\t\ncsgopolygon.gg\nDIRECT\n\tRoulette Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-012\tMagicDrop\nmagicdrop.ru\n\t\nmagicdrop.ru\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-013\tCSDice\ncsdice.com\n\t\ncsdice.com\nDIRECT\n\tDice Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-014\tRustly\nrustly.com\n\t\nrustly.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-015\tSkinOdds\nskinodds.com\n\t\nskinodds.com\nDIRECT\n\tUpgrader Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-016\tCSGOWin\ncsgowin.com\n\t\ncsgowin.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-017\tCSGORun\ncsgorun.net\n\t\ncsgorun.net\nDIRECT\n\tCrash Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-018\tOpenSkins\nopenskins.com\n\t\nopenskins.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-019\tRustBet\nrustbet.com\n\t\nrustbet.com\nDIRECT\n\tRust Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-020\tCSGOMagic\ncsgomagic.com\n\t\ncsgomagic.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-021\tCSGOBounty\ncsgobounty.com\n\t\ncsgobounty.com\nDIRECT\n\tUpgrader/Contract\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-022\tEZSkins\nezskins.com\n\t\nezskins.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-023\tRustCases\nrustcases.com\n\t\nrustcases.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-024\tCSGOReaper\ncsgoreaper.com\n\t\ncsgoreaper.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-025\tCSGOCases\ncsgocases.com\n\t\ncsgocases.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-026\tCSGO-Skins\ncsgo-skins.com\n\t\ncsgo-skins.com\nDIRECT\n\tCase Upgrader\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-027\tCSGONet\ncsgonet.com\n\t\ncsgonet.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-028\tWTFSkins\nwtfskins.com\n\t\nwtfskins.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-029\tCSGOFast\ncsgofast.com\n\t\nsteam-login.authtofast.com\nSPLIT PROXY\n\tRoulette Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-030\tDuelbits\nduelbits.com\n\t\nswitchflips.com\nSPLIT PROXY\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-031\tFlameCases\nflamecases.com\n\t\nflamecases.com\nDIRECT\n\tCase Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-032\tFarmskins\nfarmskins.com\n\t\nsteam.kobal.cc\nSPLIT PROXY\n\tCase Opener\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-033\tCSGOLuck\ncsgoluck.com\n\t\ncsgoluck.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-034\tGamedom\ngamedom.com\n\t\ngamedom.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-035\tSkin.Club\nskin.club\n\t\nsc-auth.net\nSPLIT PROXY\n\tCase Battles\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-036\tDaddySkins\ndaddyskins.com\n\t\ndaddyskins.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-037\tInsane.gg\ninsane.gg\n\t\napi.insane.gg\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-038\tRustix\nrustix.gg\n\t\nrustix.gg\nDIRECT\n\tRust Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-039\tSkins.Club\nskins.club\n\t\nskins.club\nDIRECT\n\tSkin Upgrade\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-040\tCSGOHouse\ncsgohouse.org\n\t\ncsgohouse.org\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-041\tSkinRave\nskinrave.net\n\t\nskinrave.net\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-042\tBloodyCase_GG\nbloodycase.gg\n\t\nbloodycase.gg\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-043\tCSGOClicker\ncsgoclicker.com\n\t\ncsgoclicker.com\nDIRECT\n\tClicker/Upgrade\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-044\tRustBet_GG\nrustbet.gg\n\t\nrustbet.gg\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-045\tCS_Drop\ncs-drop.com\n\t\ncs-drop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-046\tHellStore\nhellstore.net\n\t\nhellstore.net\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-047\tRustLoot\nrustloot.com\n\t\nrustloot.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-048\tCSGO_Case\ncsgo-case.com\n\t\ncsgo-case.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-049\tCS2Skin\ncs2skin.com\n\t\ncs2skin.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-050\tJuice_GG\njuice.gg\n\t\nletmeinjuice.com\nSPLIT PROXY\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-051\tGGDrop\nggdrop.com\n\t\nggauth.com\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-052\tCSGOGem\ncsgogem.com\n\t\ncsgogem.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-053\tRainbet\nrainbet.com\n\t\nservices.rainbet.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-054\tHowl_GG\nhowl.gg\n\t\nhowl.uno\nSPLIT PROXY\n\tSkins Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-055\tChicken_GG\nchicken.gg\n\t\nchicken.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-056\tCSGOCasino_GG\ncsgocasino.gg\n\t\napi.csgocasino.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-057\tHunt_GG\nhunt.gg\n\t\napi.hunt.gg\nDIRECT\n\tSkins Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-058\tCSBattle\ncsbattle.com\n\t\ncsbattle.com\nDIRECT\n\tCase Battles\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-059\tSkinRave_GG\nskinrave.gg\n\t\napi.skinrave.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-060\tCSDouble\ncsdouble.gg\n\t\ncsdouble.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-061\tRustChance\nrustchance.com\n\t\nhgfuihd.com\nSPLIT PROXY\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-062\tRustClash\nrustclash.com\n\t\nrustclash.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-063\tCobaltLab\ncobaltlab.tech\n\t\ncobaltauth.com\nSPLIT PROXY\n\tRust Automation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-064\tRaided_GG\nraided.gg\n\t\napi.raided.gg\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-065\tRustNeo\nrustneo.gg\n\t\nrustneo.gg\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-066\tSplits_GG\nsplits.gg\n\t\nsplits.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-067\tUpgrader_Pro\nupgrader.pro\n\t\nupgauth.space\nSPLIT PROXY\n\tSkin Upgrader\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-068\tSkinFans\nskin.fans\n\t\nauth.skinfans.com\nSPLIT PROXY\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-069\tHotPizza\nhotpizza.one\n\t\nhotpizza.one\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-070\tG4Skins\ng4skins.com\n\t\nauth.g4s.to\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-071\t12CS_Fail\n12cs.fail\n\t\n12cs.fail\nDIRECT\n\tCrash Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-072\tTF2Royal\ntf2royal.com\n\t\ntf2auth.com\nSPLIT PROXY\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-073\tTF2Easy\nwww.tf2easy.com\n\t\nwww.tf2easy.com\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-074\tTF2Hunt\ntf2hunt.com\n\t\nrstspcl.com\nSPLIT PROXY\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-075\tTF2Bet\ntf2.bet/coinflip\n\t\ntf2.bet\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-076\tTF2Blaze\ntf2blaze.com\n\t\ntf2blaze.com\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-077\tOpenStars_GG\nopenstars.gg\n\t\nopenstars.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-078\tShuffle_Com\nshuffle.com\n\t\nshuffle.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-079\tSkins.com\nskins.com\n\t\napi.skins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-080\tWhite.Market\nwhite.market\n\t\nwhite.market\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-081\tBuff.Market\nbuff.market\n\t\nbuff.market\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-082\tAvan.Market\navan.market\n\t\navan.market\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-083\tCS.MONEY\ncs.money\n\t\nauth.dota.trade\nSPLIT PROXY\n\tTrading Engine\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-084\tUUSkins\nuuskins.com\n\t\nuuskins.com\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-085\tYouPin898\nyoupin898.com\n\t\nyoupin898.com\nDIRECT\n\tMass Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-086\tMoon.Market\nmoon.market\n\t\nmoon.market\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-087\tCSFloat\ncsfloat.com\n\t\ncsgofloat.com\nSPLIT PROXY\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-088\tSkin.Land\nskin.land\n\t\nauth.skin.land\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-089\tC5Game\nc5game.com\n\t\nc5game.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-090\tHaloSkins\nhaloskins.com\n\t\nhaloskins.com\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-091\tBuff.163\nbuff.163.com\n\t\nbuff.163.com\nDIRECT\n\tCorporate Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-092\tWaxpeer\nwaxpeer.com\n\t\nwaxpeer.com\nDIRECT\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-093\tCS.MONEY Bot\ncs.money\n\t\nauth.dota.trade\nSPLIT PROXY\n\tBot Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-094\tMarket.CSGO\nmarket.csgo.com\n\t\ndota2.net\nSPLIT PROXY\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-095\tSkinport\nskinport.com\n\t\nskinport.app\nSPLIT PROXY\n\tRegulated Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-096\tSkinFlow\nskinflow.gg\n\t\napi.skinflow.gg\nDIRECT\n\tMarketplace/Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-097\tDMarket\ndmarket.com\n\t\ndmarket.com\nDIRECT\n\tUS Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-098\tSkin.place\nskin.place\n\t\napi.skin.place\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-099\tSkinsMonkey\nskinsmonkey.com\n\t\nskinsmonkey.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-100\tSkinBaron\nskinbaron.de\n\t\nskinbaron.com\nSPLIT PROXY\n\tCorporate Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-101\tSteam\nsteamcommunity.com/market\n\t\nsteamcommunity.com/market\nDIRECT\n\tOfficial Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-102\tRustTM\nrust.tm\n\t\ndota2.net\nSPLIT PROXY\n\tRust Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-103\tPirateSwap\npirateswap.com\n\t\nlogin.pirateswap.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-104\tMannco.Store\nmannco.store\n\t\nmannco.store\nDIRECT\n\tTF2 Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-105\tSkinSwap\nskinswap.com\n\t\napi.skinswap.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-106\tLootFarm\nlootfarm.com\n\t\nlootfarm.com\nDIRECT\n\tTrading Platform\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-107\tRustskins\nrustskins.com\n\t\nrustskins.com\nDIRECT\n\tRust Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-108\tExeSkins\nexeskins.com\n\t\nexeskins.com\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-109\tBalticSkins\nbalticskins.com\n\t\nbalticskins.com\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-110\tCS.Trade\ncs.trade\n\t\ncs.trade\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-111\tRapidSkins\nrapidskins.com\n\t\napi.rapidskins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-112\tTradeIt\ntradeit.gg\n\t\nconnect-tradeit.com\nSPLIT PROXY\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-113\tKrakatoa\nkrakatoa.com\n\t\nkrakatoa.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-114\tShadowPay\nshadowpay.com\n\t\nshadowpay.com\nDIRECT\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-115\t49skins\n49skins.com\n\t\napi.49skins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-116\tSkinVault\nskinvault.gg\n\t\napi.skinvault.gg\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-117\tAim Market\naim.market\n\t\naim.market\nDIRECT\n\tSkins Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-118\tSkinout\nskinout.gg\n\t\nauth.skinout.gg\nDIRECT\n\tInstant Sell Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-119\tNTSkins\nntskins.com\n\t\nntskins.com\nDIRECT\n\tSkins Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-120\tIGXE\nigxe.cn\n\t\nigxe.cn\nDIRECT\n\tChinese Powerhouse\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-121\tSwap.gg\nswap.gg\n\t\nswap.gg\nDIRECT\n\tAutomated Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-122\tBitskins\nbitskins.com\n\t\nbitskins.com\nDIRECT\n\tCash-out Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-123\tGamerPay\ngamerpay.gg\n\t\ngamerpay.gg\nDIRECT\n\tP2P Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-124\tTF2Mart\ntf2mart.com\n\t\ntf2mart.com\nDIRECT\n\tTF2 Automation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-125\tSkinBid\nskinbid.com\n\t\nskinbid.com\nDIRECT\n\tSkin Auctions\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-126\tLootBear\nlootbear.com\n\t\nlootbear.com\nDIRECT\n\tSkin Rental\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-127\tBackpack.tf\nbackpack.tf\n\t\nbackpack.tf\nDIRECT\n\tTF2 Valuation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-128\tScrap.tf\nscrap.tf\n\t\nscrap.tf\nDIRECT\n\tTF2 Scrap Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-129\tMarketplace.tf\nmarketplace.tf\n\t\nmarketplace.tf\nDIRECT\n\tTF2 Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-130\tSTNTrading\nstntrading.eu\n\t\nstntrading.eu\nDIRECT\n\tTF2 Botnet\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-131\tSkins.Cash\nskins.cash\n\t\nskinscash.live\nSPLIT PROXY\n\tInstant Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-132\tSkinWallet\nskinwallet.com\n\t\nskinwallet.com\nDIRECT\n\tInstant Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-133\tDota2Market\ndota2market.com\n\t\ndota2market.com\nDIRECT\n\tDota 2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-134\tCSGO.NET\ncsgo.net\n\t\ncn2.easylot.net\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-135\tCybershoke\ncybershoke.net\n\t\nauth.cybershoke.net\nDIRECT\n\tCommunity Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-136\tXPlay_GG\nxplay.gg\n\t\nxplay.gg\nDIRECT\n\tServer Network\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-137\tFastCup\nfastcup.net\n\t\napi.fastcup.net\nDIRECT\n\tMatchmaker Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-138\tEsportal\nesportal.com\n\t\nesportal.com\nDIRECT\n\tMatchmaking Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-139\tGamersClub\ngamersclub.com.br\n\t\ngamersclub.com.br\nDIRECT\n\tLATAM Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-140\tLeetify\nleetify.com\n\t\nleetify.com\nDIRECT\n\tSaaS Analytics\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-141\tScope_GG\nscope.gg\n\t\nscope.gg\nDIRECT\n\tSaaS Analytics\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-142\tTradeUpSpy\ntradeupspy.com\n\t\napi.tradeupspy.com\nDIRECT\n\tSaaS Tools\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-143\tEpidemic_GG\nepidemic.gg\n\t\nepidemic.gg\nDIRECT\n\tSaaS Tools\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-144\tCSDeals\ncs.deals\n\t\napi.cs.deals\nDIRECT\n\tMarketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-145\tPricempire\npricempire.com\n\t\npricempire.com\nDIRECT\n\tSaaS Price DB\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-146\tCS2Stash\ncs2stash.com\n\t\ncs2stash.com\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-147\tCSGOSkins\ncsgoskins.gg\n\t\ncsgoskins.gg\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-148\tSteamAnalyst\nsteamanalyst.com\n\t\nsteamanalyst.com\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-149\tSteamCardExchange\nsteamcardexchange.net\n\t\nsteamcardexchange.net\nDIRECT\n\tTrading Exchange\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-150\tDotaBuff\ndotabuff.com\n\t\ndotabuff.com\nDIRECT\n\tSaaS Tracker\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-151\tTracker_GG\ntracker.gg\n\t\ntracker.gg\nDIRECT\n\tSaaS Tracker\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-152\tFSB Market (an anonymized label; the original name is withheld here)\nFSB Market\n\t\nFSB Market\nDIRECT\n\tMass Blackmarket\tSSA § 2.G, SSA § 4.C, SSA § 1.C\tSee dated evidence\nEX-153\tFunPay\nfunpay.com\n\t\nfunpay.com\nDIRECT\n\tAccount Exchange\tSSA § 2.G, SSA § 4.C, SSA § 1.C\tSee dated evidence\nEX-154\tPlayerAuctions\nplayerauctions.com\n\t\nplayerauctions.com\nDIRECT\n\tGrey Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-155\tEldorado.gg\neldorado.gg\n\t\neldorado.gg\nDIRECT\n\tAccount Portal\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-156\tG2A\ng2a.com\n\t\ng2a.com\nDIRECT\n\tMass Key Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-157\tKinguin\nkinguin.net\n\t\nkinguin.net\nDIRECT\n\tMass Key Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-158\tG2G.com\ng2g.com\n\t\ng2g.com\nDIRECT\n\tVirtual Services\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-159\tPlayerup\nplayerup.com\n\t\nplayerup.com\nDIRECT\n\tAccount Broker\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-160\tZ2U.com\nz2u.com\n\t\nwww.z2u.com\nDIRECT\n\tReady-Account Hub\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-161\tSmurfHub\nsmurfhub.net\n\t\nsmurfhub.net\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-162\tSmurfAccounts\nsmurfaccounts.com\n\t\nsmurfaccounts.com\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-163\tBuyCSGORank\nbuycsgorank.com\n\t\nbuycsgorank.com\nDIRECT\n\tRank Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-164\tCSGOSmurfKings\ncsgosmurfkings.com\n\t\ncsgosmurfkings.com\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-165\tSmurfStore_Co\nsmurfstore.co\n\t\nsmurfstore.co\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-166\tSteamLvlUp\nsteamlvlup.com\n\t\nsteamlvlup.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-167\tSteamLevels\nsteamlevels.com\n\t\nsteamlevels.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-168\tLevelSteam\nlevelsteam.com\n\t\nlevelsteam.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-169\tSteamLevelU\nsteamlevelu.com\n\t\nsteamlevelu.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-170\tEloKing\neloking.com\n\t\neloking.com\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-171\tBoosteria\nboosteria.org\n\t\nboosteria.org\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-172\tOvergear\novergear.com\n\t\novergear.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-173\tBlazingBoost\nblazingboost.com\n\t\nblazingboost.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-174\tDota2Boost\ndota2boost.com\n\t\ndota2boost.com\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-175\tBuyBoost\nbuyboost.com\n\t\nbuyboost.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nDeel IV: Technische architectuur en authenticatiemechanismenREF: TECH-ANALYSIS-01\n\n1. Ontbrekende validatie van domeineigendom in OpenID 2.0: De implementatie door Valve van het OpenID-2.0-protocol (https://steamcommunity.com/openid/login) beoordeelt de openid.return_to en openid.realm parameters zonder dat voorafgaande registratie van ontwikkelaars, verificatie via cryptografische uitdagingen of validatie van domeineigendom vereist is. Elke commerciële exploitant kan gebruikers doorverwijzen naar het inlogscherm van Valve en een cryptografisch ondertekende identiteitsverklaring (met de SteamID in de vorm van 64-) ontvangen, die naar willekeurige domeinen wordt doorgestuurd.\n\n2. Programmatisch opvragen van inventaris en misbruik van de sleutel „API”: Zodra de gebruikersauthenticatie via OpenID is bevestigd, sturen operators verzoeken naar openbare en partner-webAPI-eindpunten (IEconItems_730/GetPlayerItems) om voorraadactiva in realtime te indexeren. Geautomatiseerde handelsnetwerken maken gebruik van programmatische sessietokens om peer-to-peer (P2P)-handelsaanbiedingen in te dienen, op te vragen en te accepteren, wat rechtstreeks in strijd is met het verbod op niet-menselijke interactie in SSA §4.C.\n\n3. Asymmetrie in linkfilters: Het feit dat er zowel waarschuwingen voor domeinen die zich op consumenten richten bestaan als volledig functionele authenticatie-eindpunten, leidt tot een tegenstrijdigheid in de regelgeving: de beveiligingstelemetrie van Valve classificeert deze exploitanten als „mogelijk kwaadaardig“, terwijl de authenticatie-infrastructuur van Valve hun gebruikersbestand blijft authenticeren.\n\nBewijsmethodologie en verklaring inzake de bewakingsketen\n\nDit document is samengesteld op basis van niet-geverifieerde netwerkgegevens, historische RDAP registerquery’s en geverifieerde cryptografische hash-manifesten. Er zijn geen inloggegevens van gebruikers getest op kwetsbaarheid of verwerkt. Alle bevindingen weerspiegelen de waarneembare toestand van het productienetwerk per september 2026. Dit document dient als een onpartijdig technisch bewijsstuk dat is opgesteld ten behoeve van gerechtelijke, regelgevende en openbare onderzoeken.\n\nSAMENVATTING: SHA-256-GEVERIFIEERD\nc507c9025f93da0aadaf395c4d8882f25973211c318ee8e9b6f18a5b3755e050\nARCHIEF: OPENBAAR JURIDISCH DOSSIER\nUITGEGEVEN EN ONDERTEKEND DOOR: phishdestroy.io · Coalitie voor forensisch onderzoek\nRECHTSSTATUS: ALLE RECHTEN ZIJN AABGESTANDEN AAN DE MENSHEID · CC0 UNIVERSAL PUBLIC DOMAIN",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Wet op de forensische controle en bijlage met regelgeving"
          }
        ],
        "links": []
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/nl/regulatory_act_print.content.json",
      "export_json_sha256": "ffe40198775131378959b75c8c3329afcbb28a9b931bdcaf5919b7386031a357"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "nl/security_timeline.html",
      "language": "nl",
      "title": "Tijdlijn van de veiligheidsoperatie — Het dossier over de „Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/nl/security_timeline",
      "source_html_sha256": "e89b061204900c0e8f5ca35a6bfbb8a03b03313a7daf3d83d41d08ce79774611",
      "exported_at": "2026-09-29T00:18:32.793Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "security_timeline.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/nl/security_timeline.pdf?v=print-20260929-v5",
        "sha256": "e98f6207332069650fc62804f0af12c8b4a10ea69789a308aeab1bfc7a63247d",
        "bytes": 99417,
        "pages": 7
      },
      "integrity": {
        "signed_object": "security_timeline.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "security_timeline.content.json.asc",
        "digest_file": "security_timeline.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify security_timeline.content.json.asc security_timeline.content.json",
          "sha256sum -c security_timeline.content.json.sha256"
        ]
      },
      "content": {
        "text": "HET VEILIGHEIDSVERSLAGTENTOONSTELLING / INZENDINGEN VOOR DE '16'\n\n2018 — 2026\n\nBeveiligingstijdlijn — 2018 naar 2026\n\nDe beveiliging is gewijzigd. Volg het verslag.\n\nWAT IN DIT HOOFDSTUK WORDT AANGETOOND\n\nDit chronologische overzicht geeft een beeld van acht jaar aan beveiligingsaanpassingen in de handels- en authenticatiestack van Steam. Het volgt de implementatie van de handelsstop op 2018 7-, 2023 Web API, belangrijke mobiele bevestigingen, en de afschaffing van sessietokens op 2026 in reactie op gedocumenteerde omzeilingstechnieken. De tijdlijn laat zien dat platformupdates consequent achterbleven bij bekende exploitvectoren, terwijl de structurele voordelen voor commerciële exploitanten behouden bleven.\n\n← Terug naar het Executive Briefing\n\nTransactiesloten. Toegangscontroles. Beperkingen op het gebruik van het `API`-commando. Een chronologisch overzicht van wat er is veranderd – en wat de bronnen daadwerkelijk aantonen.\n\nBekijk de tijdlijn ↓\nACHT JAAR. ÉÉN ALBUM.16mijlpalen die moeten worden onderzocht\n\nElk item behoudt de datum van indiening en de bron. De verificatie wordt ernaast weergegeven.\n\nBEOORDEELD / 24 SEP 2026\n10Geverifieerd evenement en datum\n06Gedeeltelijk geverifieerd\n00Bronconflict\n00Bron vereist\nHoe dit document te lezen\n\nGeverifieerd evenement en datum: beide gestaafd door een goed leesbare primaire bron. Gedeeltelijk geverifieerd: er is een gerelateerde wijziging vastgelegd, maar de datum of de reikwijdte ervan is nog niet vastgesteld. Bronconflict: het gelinkte materiaal ondersteunt de ingediende bewering niet. Bron vereist: Bij deze beoordeling is geen overeenkomende bron met een datum geverifieerd. Het feit dat een vermelding niet is opgehelderd, betekent niet dat een gebeurtenis niet heeft plaatsgevonden.\n\nDe datums bij onopgeloste vermeldingen zijn de datum van indiening, niet de geverifieerde publicatiedatum. De oorspronkelijke tekst van het onderzoek is niet herschreven.\n\nDe chronologie\n01 — 16\nZoek in het recordOnderwerpBewijsBestelling\n\n16 van de berichten op 16 · nieuwste eerst\n\n202609-01Datum van indiening\nGemeenschapGedeeltelijk geverifieerd\nWaarschuwingen voor verdachte berichten in groepschats\n\nEen officiële bètamelding bevestigt de functie op 31 augustus. Voor de opgegeven stabiele releasedatum van 1 september ontbreken nog de specifieke release-opmerkingen.\n\nSteam Client Beta — 31st augustus ↗gearchiveerd op 2026-03-13 ↗\nOorspronkelijke vermelding & ingediende link\n\nAutomatische signalering van verdachte chats\n\nBekijk de ingediende broncode ↗\n202601-16Datum van verificatie\nAPIGeverifieerd evenement en datum\nGedetailleerde machtigingen en IP-whitelisting voor Publisher Keys (aankondiging op Valve)\n\nOp 16 januari 2026, Valve publiceerde een officiële Steamworks-aankondiging (\"NIEUW: Betere machtigingen en beheeropties voor WebAPI-sleutels\") waarin nieuwe, gedetailleerde machtigingshulpmiddelen worden bevestigd waarmee ontwikkelaars WebAPI-sleutels in afzonderlijke groepen kunnen indelen (Algemeen, microtransacties, economie en verkoopcijfers), sleutels beperken tot specifieke App-ID’s en een whitelist voor server-IP-adressen afdwingen.\n\nDe schrijnende dubbele moraal: In deze officiële mededeling wordt bevestigd dat Valve de technische infrastructuur voor gedetailleerde API-machtigingen en IP-beperkingen volledig heeft ontwikkeld, maar houdt deze opzettelijk achter voor gewone gebruikersaccounts (steamcommunity.com/dev/apikey). De gebruikelijke API-sleutels blijven monolithische, alles-of-niets-inloggegevens zonder IP-whitelisting — en dat is precies de technische omissie die de miljoenenAPI-industrie voor het onderscheppen van transacties mogelijk maakt.\n\nValve Aankondiging — NIEUW: Betere machtigingen en beheeropties voor webAPI-sleutels (16 Jan 2026) ↗· Documentatie: Steamworks-webAPI-authenticatie ↗\nOorspronkelijke vermelding & ingediende link\n\nSteamworks-webAPI: gedetailleerde overzichten\n\nBekijk de officiële Steamworks-aankondiging van ‘Valve’ (493839547938902179) ↗\n202507-15Datum van verificatie\nHandelGeverifieerd evenement en datum\nCS2-transacties krijgen een omkeerperiode van zeven dagen\n\nIn de aankondiging van Valve van [datum] wordt de terugdraaiing van Counter-Strike-itemruiltransacties van de afgelopen zeven dagen aangekondigd. Hoewel dit bedoeld is om hijacking tegen te gaan, hebben economische audits door derde partijen (CSMarketCap ↗) noteerde een $104M (-25%) samenvouwen in marktkapitalisatie binnen 24 uur als gevolg van een verstoring van de contante handel. Zoals geanalyseerd door Skinvault ↗, het activeren van een omkering leidt tot een automatische 30-daghandel-blokkering op de rekening. In de zomer 2026, Valve is er overgestapt van wereldwijde resets om middernacht UTC naar individuele timers per item die per minuut lopen (Skin.land ↗).\n\nValve — 15 Aankondiging van 2025, juli ↗· CSMarketCap-analyse ↗\nOorspronkelijke vermelding & ingediende link\n\nCS2-handelsbescherming / Terugdraaiperiode\n\nBekijk de ingediende broncode ↗\n202505-14Datum van verificatie\nAuthenticatieGeverifieerd evenement en datum\nValve publiceert een beveiligingswaarschuwing over het lekken van sms-berichten\n\nDe officiële mededeling van Valve van 14, 2025, gaat over accountbeveiliging en authenticatiemethoden via sms. Hoewel de mededeling zich richt op het uitlekken van sms-berichten en bevestigt dat er geen inbreuken zijn geweest op de systemen van Steam, fungeert deze als een officiële beveiligingsupdate op de datum van publicatie.\n\nValve — Een opmerking over de beveiliging van uw Steam-account ↗\nOorspronkelijke vermelding & ingediende link\n\nMededeling over accountbeveiliging\n\nBekijk de ingediende broncode ↗\n202410-02Datum van verificatie\nHandelGeverifieerd evenement en datum\nZeven dagen vóór herverkoop of herplaatsing op de markt\n\nDe release-opmerkingen hebben betrekking op items die via de in-game winkel zijn verkregen, waaronder de Armory, ruilaanbiedingen en de Community Market. De beschreven reikwijdte is breder dan alleen de items uit de Armory.\n\nValve — Release-opmerkingen voor 10/2/2024 ↗\nOorspronkelijke vermelding & ingediende link\n\nCS2 The Armory / 7-Day Hold\n\nBekijk de ingediende broncode ↗\n202409-18Datum van indiening\nHandelGedeeltelijk geverifieerd\nBeperkingen voor nieuwe apparaten gecontroleerd op de Help-pagina’s\n\nIn de officiële ondersteuningsdocumentatie van Steam wordt bevestigd dat er een beperking geldt voor daghandel (7-) wanneer men inlogt vanaf een nieuw apparaat dat al minstens 7 dagen niet is geautoriseerd. Hoewel de exacte implementatiedatum van 18, 2024, in september niet als mijlpaal in de changelog is vastgelegd, is de functionaliteit volledig gedocumenteerd.\n\nSteam Ondersteuning — Handels- en marktbeperkingen ↗\nOorspronkelijke vermelding & ingediende link\n\nBeperking op het inloggen met nieuwe apparaten\n\nBekijk de ingediende broncode ↗\n202402-14Datum van indiening\nGemeenschapGedeeltelijk geverifieerd\nWachtperiode voor het wijzigen van de naam is geïmplementeerd in 2024\n\nUit gegevens van de community en ontwikkelaars blijkt dat Valve begin 2024, een onaangekondigde 2-tot4 uur durende afkoelperiode heeft ingevoerd, die onmiddellijk volgt op een wijziging van de profielnaam, om snelle identiteitsfraude te voorkomen. Aangezien Valve geen officieel persbericht, changelog of ondersteuningsartikel over deze beperking heeft gepubliceerd, ontbreekt formele verificatie voor de opgegeven datum van 14 in februari; de Steam Workshop-gids dient als indirecte bevestiging door de community en niet als officiële Valve documentatie.\n\nSteam Workshopgids (indirecte bevestiging) — Details over de beperking inzake naamswijziging ↗\nOorspronkelijke vermelding & ingediende link\n\nWachtstand voor het wijzigen van profielnaam / avatar\n\nBekijk de ingediende broncode ↗\n202312-04Datum van verificatie\nAPIGeverifieerd evenement en datum\nVoor het aanmaken van een sleutel is een bevestiging via de mobiele telefoon vereist\n\nUit gegevens van externe ontwikkelaarsbibliotheken blijkt dat de invoering van de verplichte mobiele bevestiging via Steam Guard voor het aanmaken van sleutels op Web API eind 2023, heeft plaatsgevonden. De exacte datum van december 4, 2023, geeft de waargenomen uitrolperiode binnen de ontwikkelaarsgemeenschap weer.\n\nDocumentatie voor beheerders — maart 2024 ↗gearchiveerd op 2026-09-24 ↗\nOorspronkelijke vermelding & ingediende link\n\nMobiele bevestiging voor sleutels van API\n\nBekijk de ingediende broncode ↗\n202310-24Datum van verificatie\nOntwikkelaarGeverifieerd evenement en datum\nDe verplichte 2FA voor het live zetten van spelversies treedt in werking\n\nDe officiële Steamworks-aankondiging van Valve op 10, 2023, bevestigt dat vanaf 24, 2023, elk account dat een build live zet op de standaardtak van een uitgebrachte applicatie, de wijziging moet autoriseren via sms of de mobiele app Steam. Deze wijziging heeft direct geleid tot een update van de SetAppBuildLive-webpagina API.\n\nSteamworks — Beveiligingsverbeteringen voor het beheer van builds en gebruikers ↗gearchiveerd op 2025-12-03 ↗\nOorspronkelijke vermelding & ingediende link\n\nSMS-MFA voor publicaties over game-builds\n\nBekijk de ingediende broncode ↗\n202307-12Datum van indiening\nGemeenschapGedeeltelijk geverifieerd\nDoor de gemeenschap gesignaleerde inhoudswaarschuwingen in aangepaste biografieën\n\nSteam Uit meldingen van de community vanaf juli 2023 blijkt dat bij aangepaste profielbeschrijvingen met externe links of triggerwoorden automatisch inhoudswaarschuwingen werden weergegeven. De datum van indiening, 7 juli 12, 2023,, komt overeen met de eerste golf van gebruikersmeldingen op de communityforums van Steam.\n\nSteam Communityforum — Meldingen over inhoud met biografische informatie ↗\nOorspronkelijke vermelding & ingediende link\n\nWaarschuwing inzake aangepaste biografische inhoud\n\nBekijk de ingediende broncode ↗\n202301-25Datum van indiening\nGemeenschapGedeeltelijk geverifieerd\nFiltering van profiellinks en wachttijden voor bewerken zijn actief\n\nDe officiële ondersteuningsdocumentatie van Steam bevestigt dat links in aangepaste biografieën worden gefilterd en dat misbruik bij het wijzigen van namen of avatars kan leiden tot bewerkingsverboden. Hoewel de exacte invoering van de 4-wachttijd van een uur op 1 januari 25, 2023, het waargenomen beginpunt vormt, is het mechanisme voor het filteren van links zelf al volledig actief, zoals te zien is op de ingediende helppagina.\n\nSteam Ondersteuning — Beperkingen voor profielnaam en avatar ↗\nOorspronkelijke vermelding & ingediende link\n\nProfiel LINK VERWIJDERD / Afkoelperiode\n\nBekijk de ingediende broncode ↗\n202210-24Datum van verificatie\nAuthenticatieGeverifieerd evenement en datum\nSteam Overgang van klanten naar OAuth-vernieuwings- en toegangstokens\n\nBelangrijke updates voor de client en mobiele app van Valve in oktober 2022 heeft het authenticatiesysteem van Steam grondig herzien. De oude structuur met sessiecookies is vervangen door op OAuth gebaseerde toegangs- en vernieuwingstokens, en er is een lijst met actieve, geautoriseerde apparaten geïntroduceerd waarmee actieve sessies handmatig kunnen worden ingetrokken.\n\nValve — Update van de mobiele app van de Steam en grondige herziening van het authenticatiesysteem ↗\nOorspronkelijke vermelding & ingediende link\n\nSteam Herziening van het inlogproces / Afkapping van cookies\n\nBekijk de aankondiging over 'Valve' ↗\n202210-12Datum van verificatie\nAuthenticatieGeverifieerd evenement en datum\nAanmelden via QR-code en beheer van geautoriseerde apparaten\n\nIn de aankondiging van Valve van 12 oktober worden de QR-aanmelding, het goedkeuren of weigeren van aanmeldingen en een lijst met apparaten beschreven waarmee de toegang tot een account kan worden ingetrokken.\n\nValve — De vernieuwde mobiele app van de ‘Steam’ is nu beschikbaar ↗\nOorspronkelijke vermelding & ingediende link\n\nSteam 3.0 via mobiele app / Inloggen via QR-code\n\nBekijk de ingediende broncode ↗\n202205-10Datum van indiening\nAPIGedeeltelijk geverifieerd\nEindpunten voor het annuleren van transacties verwijderd uit de openbare lijst op API\n\nUit ontwikkelaarsgegevens blijkt dat in mei 2022, Valve stilletjes eindpunten voor transactiebeheer, zoals IEconService/CancelTradeOffer en DeclineTradeOffer, uit de Web-API heeft verwijderd (gedocumenteerd in node-steam-tradeoffer-manager #325). Hoewel de methoden in privé-clientprotocollen nog steeds functioneren, markeert de datum 10, 2022, het moment waarop ze daadwerkelijk uit openbare web-API’s zijn verwijderd om scam-panels tegen te gaan.\n\nDiscussie tussen ontwikkelaars — Issue #325 (CancelTradeOffer verwijderd) ↗· Steamworks-webAPI — IEconService-documentatie ↗\nOorspronkelijke vermelding & ingediende link\n\nVerwijdering van eindpunten voor het annuleren van transacties\n\nBekijk het probleem #325 ↗ in node-steam-tradeoffer-manager ↗\n202005-25Datum van verificatie\nHandelGeverifieerd evenement en datum\nDota-2-items krijgen een wachttijd van zeven dagen voor het verhandelen ervan\n\nOp 25, 2020, heeft Valve, gelijktijdig met de lancering van de Battle Pass voor The International 10 (blog.dota2.com/2020/05/the-international-10-battle-pass/), een handelsbeperking van 7-dagen ingesteld voor Dota 2-items, in overeenstemming met het beleid van 2018 voor Counter-Strike. Deze beperking geldt voor alle geruilde items en aankopen op de Market.\n\nDota 2-community — Update over Trade Lock en de TI10-client ↗\nOorspronkelijke vermelding & ingediende link\n\nDota 2 / 7-Daghandel-vergrendeling\n\nBekijk de ingediende broncode ↗\n201803-29Datum van verificatie\nHandelGeverifieerd evenement en datum\nVoor geruilde CS:GO-items geldt een wachttijd van zeven dagen\n\nIn de officiële release-opmerkingen worden de datum en de beperking bevestigd. De opgegeven URL leidde door naar een kaartupdate op 2013; de bijbehorende URL voor de release-opmerkingen eindigt op 20309.\n\nValve — Release-opmerkingen voor 3/29/2018 ↗\nOorspronkelijke vermelding & ingediende link\n\nCS:GO / 7-Daghandel-vergrendeling\n\nBekijk de ingediende broncode ↗ gearchiveerd op 2025-02-26 ↗\n\nVolg de aanwijzingen. Controleer de bron.\n\nTerug naar het onderzoek ↗",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Beveiligingstijdlijn — 2018 naar 2026"
          },
          {
            "level": 2,
            "id": null,
            "text": "De chronologie"
          },
          {
            "level": 2,
            "id": null,
            "text": "Waarschuwingen voor verdachte berichten in groepschats"
          },
          {
            "level": 2,
            "id": null,
            "text": "Gedetailleerde machtigingen en IP-whitelisting voor Publisher Keys (aankondiging op Valve)"
          },
          {
            "level": 2,
            "id": null,
            "text": "CS2-transacties krijgen een omkeerperiode van zeven dagen"
          },
          {
            "level": 2,
            "id": null,
            "text": "Valve publiceert een beveiligingswaarschuwing over het lekken van sms-berichten"
          },
          {
            "level": 2,
            "id": null,
            "text": "Zeven dagen vóór herverkoop of herplaatsing op de markt"
          },
          {
            "level": 2,
            "id": null,
            "text": "Beperkingen voor nieuwe apparaten gecontroleerd op de Help-pagina’s"
          },
          {
            "level": 2,
            "id": null,
            "text": "Wachtperiode voor het wijzigen van de naam is geïmplementeerd in 2024"
          },
          {
            "level": 2,
            "id": null,
            "text": "Voor het aanmaken van een sleutel is een bevestiging via de mobiele telefoon vereist"
          },
          {
            "level": 2,
            "id": null,
            "text": "De verplichte 2FA voor het live zetten van spelversies treedt in werking"
          },
          {
            "level": 2,
            "id": null,
            "text": "Door de gemeenschap gesignaleerde inhoudswaarschuwingen in aangepaste biografieën"
          },
          {
            "level": 2,
            "id": null,
            "text": "Filtering van profiellinks en wachttijden voor bewerken zijn actief"
          },
          {
            "level": 2,
            "id": null,
            "text": "Steam Overgang van klanten naar OAuth-vernieuwings- en toegangstokens"
          },
          {
            "level": 2,
            "id": null,
            "text": "Aanmelden via QR-code en beheer van geautoriseerde apparaten"
          },
          {
            "level": 2,
            "id": null,
            "text": "Eindpunten voor het annuleren van transacties verwijderd uit de openbare lijst op API"
          },
          {
            "level": 2,
            "id": null,
            "text": "Dota-2-items krijgen een wachttijd van zeven dagen voor het verhandelen ervan"
          },
          {
            "level": 2,
            "id": null,
            "text": "Voor geruilde CS:GO-items geldt een wachttijd van zeven dagen"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/nl/#briefing-heading",
          "https://steamcommunity.com/groups/SteamClientBeta?l=english",
          "http://web.archive.org/web/20260313235409/https://steamcommunity.com/groups/SteamClientBeta?l=english",
          "https://store.steampowered.com/news/posts/?enddate=1788390000",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/493839547938902179",
          "https://partner.steamgames.com/doc/webapi_overview/auth",
          "https://csmarketcap.com/blog/market-insights/from-boom-to-bust-cs2s-trade-protection-impact",
          "https://skinvault.gg/blog/cs2-trade-protection-explained/",
          "https://skin.land/blog/steam-changes-cs2-trade-ban-logic-timing/",
          "https://store.steampowered.com/news/posts/?appids=730&amp;enddate=1753924057&amp;feed=steam_announce%2F1000",
          "https://help.steampowered.com/faqs/view/3041-A87A-E5F6-B6AC",
          "https://store.steampowered.com/news/posts/?enddate=1747349559",
          "https://steamcommunity.com/ogg/593110/announcements/detail/533224478739530146",
          "https://store.steampowered.com/news/posts/?appids=730&amp;enddate=1728000977&amp;feed=steam_community_announcements",
          "https://steamcommunity.com/games/CSGO/announcements/detail/4447966961421256740",
          "https://help.steampowered.com/faqs/view/7F77-9E92-31E0-6B8E",
          "https://steamcommunity.com/sharedfiles/filedetails/?id=2926756889",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "http://web.archive.org/web/20260924181824/https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "https://steamcommunity.com/dev/apikey",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3749866608167579206",
          "http://web.archive.org/web/20251203174259/https://steamcommunity.com/groups/steamworks/announcements/detail/3749866608167579206",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3734103130194459461",
          "https://steamcommunity.com/discussions/forum/1/3807266184852932971/",
          "https://help.steampowered.com/faqs/view/225C-C51E-B8F0-55B2",
          "https://store.steampowered.com/news/group/4/view/3314112260640237775",
          "https://store.steampowered.com/news/posts/?appgroupname=Keep+in+touch&amp;enddate=1666122699&amp;feed=steam_blog",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/issues/325",
          "https://partner.steamgames.com/doc/webapi/IEconService",
          "https://steamcommunity.com/app/570/announcements/",
          "https://blog.dota2.com/2020/05/trading-cooldown/",
          "https://blog.counter-strike.net/2018/03/20309/",
          "https://blog.counter-strike.net/index.php/2018/03/20308/",
          "http://web.archive.org/web/20250226114333/https://blog.counter-strike.net/index.php/2018/03/20308/",
          "https://phishdestroy.io/steam_dossier/nl/#vulnerability-profile"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/nl/security_timeline.content.json",
      "export_json_sha256": "58ca590a770b57be400cd207f3f0e851d96aa6eee7279eb6da597f365970d65b"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "nl/skin_atlas.html",
      "language": "nl",
      "title": "De atlas van wat ‘Steam’ niet kan dragen — Het dossier ‘Steam’",
      "source_url": "https://phishdestroy.io/steam_dossier/nl/skin_atlas",
      "source_html_sha256": "9ec1287077ca634ad4b8fe1160ab75e89bcb4a8ef93559e783deb3912cdab861",
      "exported_at": "2026-09-29T00:18:37.138Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "gallery",
            "source": "https://phishdestroy.io/steam_dossier/nl/skin_atlas#gallery"
          }
        ],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "skin_atlas.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/nl/skin_atlas.pdf?v=print-20260929-v5",
        "sha256": "233e4833f075e72f01436a167c4529c29b9947a3fed760c0dab5e1db5da63176",
        "bytes": 183345,
        "pages": 14
      },
      "integrity": {
        "signed_object": "skin_atlas.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "skin_atlas.content.json.asc",
        "digest_file": "skin_atlas.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify skin_atlas.content.json.asc skin_atlas.content.json",
          "sha256sum -c skin_atlas.content.json.sha256"
        ]
      },
      "content": {
        "text": "BIJLAGE IV-B / DE PRIJSLADDER / 2026-09-23\nAtlas van de prijsladder voor Skin — De liquiditeitsklif\n\nDe marktbezoeken van Valve waar het geld vandaan komt.\n\nWAT IN DIT HOOFDSTUK WORDT AANGETOOND\n\nDeze visuele atlas analyseert de productcategorieën van 30,266 in vijf marktplaatscatalogi en meet de marktdekking boven en onder de vermeldingsdrempel van Valve. Onder de limiet van $1,800 herbergt Steam 95.3% actieve categorieën; net daarboven stort de officiële dekking in tot 1.9% (met 0.0% dekking over geverifieerde activa). Dit toont een abrupte, structurele liquiditeitskloof aan, waarbij Valve het opsporen van hoogwaardige transacties delegeert aan externe platforms, terwijl het de volledige controle behoudt over de bewaring van de onderliggende activa.\n\n← Terug naar het Executive Briefing\n\nElk CS2-item waarvan de prijs op vijf marktplaatsen live wordt weergegeven, werd op basis van de goedkoopste vraagprijs in een prijsklasse ingedeeld, en voor elke klasse werd één ding gemeten: welk aandeel daarvan nog steeds op de eigen Community Market vValve wordt aangeboden. Onder de limiet voor het aantal aanbiedingen vValve is het antwoord 95.3%. Daarboven staat het antwoord: 1.9%. De daling verloopt niet geleidelijk en vindt niet plaats op het moment dat de vraag afneemt — ze vindt precies plaats op het moment dat de gepubliceerde regel van kracht wordt. Van de 248 productcategorieën waarvoor twee of meer marktplaatsen onafhankelijk van elkaar prijzen hanteren die boven het maximum liggen, 100.0% hebben helemaal geen Steam-vermelding.\n\nKijk naar de klif ↓Open de galerij met artikelen van '419'Methode en beperkingen\n30,266gemeten productcategorieën\n95.3%van posten onder de balanstotaal die door Steam worden opgenomen\n1.9%van artikelen die de limiet overschrijden en worden aangeboden door Steam\n$78.6Mminimumwaarde van de bevestigde verzameling\n01 / de meting\nDe afgrond ligt in de regel, niet op verzoek\n\nElk van de onderstaande artikelcategorieën op 30,266 wordt ingedeeld in een categorie op basis van zijn goedkoopste live-vragen op BUFF163, CSFloat, Skinport, YouPin 898 en C5Game; alleen items die op twee of meer van deze platforms worden genoemd, worden meegeteld, zodat één enkele optimistische vermelding geen bandlid kan ‘verzinnen’. Het bovenste paneel geeft het aandeel weer dat de eigen markt van Valve nog steeds voor elke band vertegenwoordigt.\n\nAandeel van elke prijsklasse op de Community Market van de ‘Steam’\nboven: stoomdekking · onder: aantal items per band, logaritmische schaal\n0%\n25%\n50%\n75%\n100%\n100%\n96.9%\n95.9%\n97.3%\n91.1%\n76.8%\n14.5%\n2.9%\n1.5%\n0%\n0%\n0%\n4,632\n1¢–10¢\n7,152\n10¢–$1\n8,568\n$1–10\n5,941\n$10–100\n2,329\n$100–300\n1,292\n$300–1k\n193\n$1k–1.8k\n70\n$1.8k–3k\n67\n$3k–10k\n18\n$10k–30k\n3\n$30k–100k\n1\n$100k+\nitems\nlog\nVALVE’S LISTING CAP\ngelijk aan of lager dan het noteringsplafond van de ‘Valve’boven de limiet — de regel van de Valve verbiedt de noteringproductcategorieën in de band\n\nOnder ‘dekking’ wordt verstaan dat er op het moment van vastlegging een live-Steam-ask bestond voor die categorie. Het onderste paneel is logaritmisch weergegeven omdat de catalogus overwegend uit goedkope aandelen bestaat: bij een lineaire weergave zouden alle banden boven $300, afvlakken tot het basisniveau.\n\nWat de vorm uitsluit\n\nAls dure goederen simpelweg niet populair zouden zijn, zou de dekking geleidelijk afnemen naarmate de prijs stijgt. Dat is echter niet het geval. De dekking blijft stabiel op 76.8% in de bandbreedte van $300–$1k, om vervolgens in te storten tot 14.5% in de bandbreedte direct onder de bovengrens en 2.9% in de bandbreedte direct daarboven. Een vraag-effect weet niet waar Valve zijn bovengrens heeft vastgesteld. Een regel weet dat wel.\n\nPrijsklasse\tProductcategorieën\tStel je vraag via de live-Steam\tSteam dekking\tExemplaren vermeld op Steam\n1¢–10¢\t4,632\t4,632\t100%\t8,223,227\n10¢–$1\t7,152\t6,931\t96.9%\t5,488,315\n$1–10\t8,568\t8,213\t95.9%\t3,939,538\n$10–100\t5,941\t5,780\t97.3%\t1,328,255\n$100–300\t2,329\t2,121\t91.1%\t364,466\n$300–1k\t1,292\t992\t76.8%\t187,504\n$1k–1.8k\t193\t28\t14.5%\t40,281\n$1.8k–3k\t70\t2\t2.9%\t9,592\n$3k–10k\t67\t1\t1.5%\t6,706\n$10k–30k\t18\t0\t0%\t1,366\n$30k–100k\t3\t0\t0%\t21\n$100k+\t1\t0\t0%\t2\n\nPatroon- en fasevarianten zijn uitgesloten van deze ranglijst: Steam vermeldt geen „blue-gem“-niveau of „Ruby“-fase als afzonderlijke markttoegang, dus als we deze zouden meetellen, zou de dekking van Steam te laag worden weergegeven. Als de vereiste van twee marktplaatsen buiten beschouwing wordt gelaten, luidt dezelfde ranglijst als volgt: 79.1% onder de bovengrens en 6.5% erboven, verspreid over 37,204 items — een grotere kloof, gebaseerd op zwakker bewijs, en daarom is dit niet het genoemde cijfer.\n\n02 / beoordeling op basis van bewijsmateriaal\nEen vraagprijs is geen prijs\n\nIedereen kan een P2000 te koop aanbieden voor zo’n tien miljoen yuan. Voordat een bedrag op deze pagina voor iets wordt gebruikt, wordt het ingedeeld op basis van het aantal marktplaatsen dat het artikel onafhankelijk boven de bovengrens noteert en hoe dicht de gemiddelde noteringen bij elkaar liggen. Alleen de categorieën A en B worden vermeld — hier of elders in dit dossier.\n\nA  Drie of meer planken komen overeen\n\nDrie of meer marktplaatsen bieden het artikel aan tegen een prijs die boven de bovengrens ligt, en hun mediaanprijs ligt binnen 25% van de goedkoopste prijs. 197 categorieën, 18,218 exemplaren, $76,585,587.\n\nAfwezig op Steam: 100.0%.\n\nB  Twee planken komen overeen\n\nTwee marktplaatsen komen boven de bovengrens overeen, of drie komen op een minder strikte manier overeen. 51 categorieën, 176 exemplaren, $2,038,814.\n\nAfwezig op Steam: 100.0%.\n\nC  Eén plank — niet in gebruik\n\nEr is slechts één handelsplatform waarop het enige vraagprijsbieding boven de bovengrens wordt aangeboden. 171 categorieën, 247 exemplaren. Wordt ter volledigheid in de galerij getoond en niet meegeteld in de totalen op deze pagina.\n\nDit zijn prijsaanvragen, geen bewijs van een prijs.\n\nWat deze correctie heeft gekost en wat ze heeft opgeleverd\n\nDoor de beoordeling ‘C’ weg te laten, verdwijnen de categorieën ‘171’ en ‘$3,825,125’ uit de kop. Wat overblijft is beknopter en veel moeilijker te weerleggen: 248 categorieën, 18,394 vermelde exemplaren, $78,624,401, en 100.0% daarvan — stuk voor stuk — ontbreken op de markt van Valve. De rijen van klasse C zijn de reden waarom het cijfer is veranderd; ze worden weergegeven en zijn niet verborgen.\n\nVermeldingen die als artefacten zijn aangemerkt\n\nElke offerte die meer dan drie keer zo hoog is als de goedkoopste vraagprijs voor hetzelfde artikel, wordt terzijde gelegd. Omgerekend tegen de koers die uit de gegevens zelf blijkt, zijn de meeste daarvan afgeronde CNY-bedragen — wat duidt op een tijdelijke plaatshouder of een maximum van het platform, in plaats van een daadwerkelijk bod. Omdat elk totaalbedrag op deze pagina gebruikmaakt van de goedkoopste Laat staan dat een van deze personen ooit een cijfer zou hebben opgeblazen; ze zijn uitgesloten, zodat ook geen van hen als kop kan worden aangehaald.\n\nArtikel\tGoedkoopste live-aanvraag\tOpzij leggen\nSouvenir P2000 | Wicked Sick (Minimal Wear)\t$148,954\t$1,489,543\n★ Specialist Gloves | Crimson Kimono (Minimal Wear) | Phase 1\t$37,239\t$119,163\nSouvenir USP-S | Printstream (Factory New)\t$2,000\t$59,582\n★ Bowie Knife | Crimson Web (Factory New)\t$2,957\t$43,030\n★ Karambit | Marble Fade (Factory New) | 1st\t$11,916\t$38,874\nSticker | Ninjas in Pyjamas (Holo) | Katowice 2014\t$5,000\t$31,748\nSouvenir AWP | Dragon Lore (Battle-Scarred)\t$4,225\t$29,157\n★ Karambit | Doppler (Minimal Wear) | Ruby\t$7,122\t$27,273\nAlle categorieën op 419, met vermelding van het object waarop elke prijs betrekking heeft\n\nBron: https://phishdestroy.io/steam_dossier/nl/skin_atlas#gallery\n\n04 / waar het in plaats daarvan naartoe is gegaan\nDe schappen waarop staat wat Steam niet zal vermelden\n\nDezelfde aanbiedingen, gegroepeerd per marktplaats waar ze te vinden zijn. Dit is een overzicht van waar exemplaren te vinden zijn vermeld, wat niet hetzelfde is als de plaats waar ze eigendom van zijn en hier ook niet als zodanig wordt opgevat.\n\nMinimale prijs van aanbiedingen boven de prijsgrens, per marktplaats\nlaagste vraagprijs x exemplaren op die plank\nYouPin 898\n$22,720,252\nBUFF163\n$22,022,606\nC5Game\n$12,560,543\nCSFloat\n$10,871,845\nSkinport\n$1,385,060\n\nRechtsgebieden, in bovenstaande volgorde: YouPin 898 — China · BUFF163 — China · C5Game — China · CSFloat — Verenigde Staten · Skinport — Duitsland / Malta. Hetzelfde fysieke artikel kan op meer dan één van deze schappen worden aangeboden, dus deze cijfers mogen niet worden opgeteld bij het totaal van een andere markt.\n\nMinimale waarde per prijsklasse\nhoe het geld boven het maximum wordt verdeeld\n$1.8k-3k\n$9,842,391\n$3k-10k\n$36,787,269\n$10k-50k\n$20,038,749\nover $50k\n$2,891,897\n05 / schaarste waarop je kunt rekenen\nHoe schaars het aanbod eigenlijk is\n\nElk CS2-item heeft een slijtagewaarde, en de marktplaatsen maken bekend hoeveel exemplaren er in elke categorie daarvan beschikbaar zijn. Daardoor wordt ‘zeldzaam’ niet langer een bijvoeglijk naamwoord, maar een getal — en juist dat getal verklaart waarom één gehackt account de moeite waard is om een op maat gemaakte phishingkit voor in te zetten.\n\nAWP | Drakenkennis\n150 in de aanbieding · vanaf $11,350\n0.00–0.01\n29 · $14,730\n0.01–0.02\n54 · $11,618\n0.02–0.03\n26 · $11,350\n0.03–0.04\n25 · $11,618\n0.04–0.07\n16 · $11,585\n\nAWP | Dragon Lore (fabrieksnieuw)\n\nM4A4 | Howl\n105 in de aanbieding · vanaf $6,628\n0.00–0.01\n11 · $10,725\n0.01–0.02\n14 · $8,088\n0.02–0.03\n11 · $7,580\n0.03–0.04\n19 · $6,703\n0.04–0.07\n50 · $6,628\n\nM4A4 | Howl (fabrieksnieuw)\n\nAK-47 | Wild Lotus\n113 in de aanbieding · vanaf $14,373\n0.00–0.01\n25 · $22,343\n0.01–0.02\n11 · $19,364\n0.02–0.03\n3 · $19,645\n0.03–0.04\n15 · $15,044\n0.04–0.07\n59 · $14,373\n\nAK-47 | Wild Lotus (fabrieksnieuw)\n\nAWP | Gungnir\n173 in de aanbieding · vanaf $11,618\n0.00–0.01\n28 · $17,875\n0.01–0.02\n21 · $13,600\n0.02–0.03\n32 · $12,065\n0.03–0.04\n29 · $11,735\n0.04–0.07\n63 · $11,618\n\nAWP | Gungnir (fabrieksnieuw)\n\nAK-47 | Vuur-slang\n278 in de aanbieding · vanaf $663\n0.15–0.18\n87 · $730\n0.18–0.21\n49 · $712\n0.21–0.24\n52 · $703\n0.24–0.27\n18 · $715\n0.27–0.38\n72 · $663\n\nAK-47 | Vuur-slang (in de praktijk getest)\n\nGehard (alle niveaus / blauwe edelsteen)\n76 in de aanbieding · vanaf $1,638\n0.07–0.08\n1 · $2,516\n0.08–0.09\n4 · $2,482\n0.09–0.10\n6 · $3,856\n0.10–0.11\n7 · $2,797\n0.11–0.15\n58 · $1,638\n\nAK-47 | Gehard (minimale slijtage) | Niveau 1\n\nBanden zijn de eigen liquiditeitsgroepen van de handelsplatforms; er worden alleen banden getrokken waarin ten minste één actuele notering voorkomt. De prijs naast elke balk is de laagste actuele vraagprijs binnen die band, zodat de premie die aan een lage liquiditeit is gekoppeld direct afleesbaar is in plaats van dat deze expliciet wordt vermeld.\n\n06 / beweging, afgelezen van Steam\nWat de schappen van derden daadwerkelijk opleverden\n\nValve publiceert op dit niveau geen bruikbare historische gegevens, en dit dossier claimt die ook niet. Skinport publiceert wel zijn eigen afgeronde transacties over de afgelopen 24 uren, 7, 30 en 90 dagen, en dat is de volledige tijdsdimensie die hier beschikbaar is: een mediaan van de gerealiseerde prijs per tijdvenster, geïndexeerd zodat de 90-dagmediaan 100. is In geen van beide grafieken zijn gegevens van Steam verwerkt.\n\nMediaan van de gerealiseerde prijs, voortschrijdend gemiddelde\ngeïndexeerd op basis van de daggemiddelde van de 90-· 6,758 items met 20+ omzet\n85\n91\n97\n103\n100\n90d\n94\n30d\n90\n7d\n88\n24h\nAantal voltooide verkopen per dag\ndezelfde artikelen, dezelfde vensters\n7,621\n9,653\n11,684\n13,716\n12,700\n90d\n11,894\n30d\n9,540\n7d\n8,637\n24h\n\nDit zijn twee grafieken in plaats van één met twee verticale schalen: een index en een dagelijks aantal hebben geen gemeenschappelijke eenheid, en door ze op een gemeenschappelijke as weer te geven zou een onjuiste vergelijking worden uitgelokt. De vensters zijn genest en opschuivend — het dagcijfer 90-omvat het uurcijfer 24-— dus dit is geen dagelijkse reeks en mag ook niet als zodanig worden geïnterpreteerd. Wat hieruit blijkt, is beperkt en wordt duidelijk vermeld: over de gepubliceerde voortschrijdende vensters Skinport lag de mediane gerealiseerde prijs onder de eigen 90-dagmediane en daalde het dagelijkse aantal verkopen mee.\n\nSkinport gerealiseerde omzet. De vensters zijn genest en glijdend, dus elk punt is de mediaan van de gerealiseerde prijs over het glijdende venster, geïndexeerd ten opzichte van de mediaan van de dag „90-”. Het betreft geen dagelijkse reeks en er zijn geen „Steam”-gegevens bij betrokken.\n\n07 / waar het van gemaakt is\nZestien jaar oude stickers en een handvol handschoenen\n\nHet aanbod boven de prijsgrens is geen brede dwarsdoorsnede van de markt. Het beperkt zich tot een paar zeldzame stukken en een paar verzamelingen, waarvan er verschillende helemaal niet meer te verkrijgen zijn — en dat is precies de reden waarom het aanbod niet op de prijs kan inspelen.\n\nCategorieën boven de limiet, op zeldzaamheid\naantal artikelcategorieën\nCovert\n321\nClassified\n39\nRestricted\n24\nContraband\n12\nMil-Spec Grade\n9\nConsumer Grade\n9\nIndustrial Grade\n5\nCategorieën boven de balk, per collectie\ntop tien collecties\nThe St. Marc Collection\n13\nThe Cobblestone Collection\n13\nThe Norse Collection\n12\nThe Arms Deal Collection\n9\nThe Canals Collection\n7\nThe Gods and Monsters Collection\n6\nThe Revolution Collection\n4\nThe 2021 Train Collection\n4\nThe Rising Sun Collection\n4\nThe Chop Shop Collection\n4\n\nPer categorie: skin 366, sticker 48, container 3, sticker_slab 2.\n\n08 / het hoogste bedrag dat iemand daadwerkelijk heeft betaald\nHoogste koersen die worden ondersteund door een transactie, niet door een beursnotering\n\nAlle andere prijzen op deze pagina zijn een vragen — wat een verkoper wil. Dit zijn verkoop: de hoogste gerealiseerde transactieSkinport, geregistreerd voor elk artikel, over de afgelopen 90 dagen. Het is het enige cijfer in dit dossier dat daadwerkelijk door iemand is betaald, en elke rij bevat een link naar de marktplaats, zodat het bedrag bij de bron kan worden gecontroleerd in plaats van bij ons.\n\n21,216artikelen waarvan de verkoop is afgerond in de etalage\n106verkocht tegen of boven de maximale notering van de Valve\n$14,192hoogste afgeronde verkoop van één enkel product\n67/419categorieën boven de limiet waarbij enige verkoop is geregistreerd\nDe dertig hoogste afgeronde verkopen in deze periode\nArtikel\tHoogste omzet\tMediane verkoopprijs\tVerkoop\tVraag nu naar de goedkoopste prijs\tSteam\tBekijk het eens\nAWP | Gungnir (Factory New)\t$14,192\t$11,343\t5\t$11,490\tabsent\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Factory New)\t$12,387\t$12,387\t1\t$13,836\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Factory New)\t$11,779\t$11,063\t16\t$10,941\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Minimal Wear)\t$11,693\t$11,693\t1\t$9,946\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Minimal Wear)\t$10,437\t$10,437\t1\t$9,610\tabsent\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Blue Laminate (Minimal Wear)\t$9,772\t$37\t76\t$30\t$40\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Minimal Wear)\t$9,463\t$9,463\t1\t$9,500\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Minimal Wear)\t$9,104\t$9,026\t6\t$8,524\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Hedge Maze (Minimal Wear)\t$8,139\t$8,139\t1\t$6,819\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Field-Tested)\t$7,617\t$7,390\t4\t$7,194\tabsent\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Field-Tested)\t$7,615\t$7,615\t1\t$7,100\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Field-Tested)\t$7,149\t$7,006\t2\t$7,165\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Field-Tested)\t$6,711\t$6,194\t15\t$5,988\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Factory New)\t$6,679\t$6,613\t3\t$6,628\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Superconductor (Factory New)\t$6,084\t$6,084\t1\t$7,969\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Battle-Scarred)\t$5,750\t$5,413\t3\t$5,899\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Pandora's Box (Minimal Wear)\t$5,520\t$5,508\t3\t$4,998\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Vice (Factory New)\t$5,385\t$5,158\t2\t$5,700\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Minimal Wear)\t$5,342\t$4,989\t19\t$4,997\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Hedge Maze (Field-Tested)\t$5,334\t$4,862\t5\t$3,724\tabsent\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Vulcan (Factory New)\t$5,275\t$1,418\t12\t$1,280\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Well-Worn)\t$4,978\t$4,978\t1\t$4,942\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Well-Worn)\t$4,931\t$4,931\t1\t$5,445\tabsent\tSkinport CSFloat Steam\nAK-47 | Hydroponic (Factory New)\t$4,802\t$4,351\t2\t$3,648\tabsent\tSkinport CSFloat Steam\n★ Talon Knife | Case Hardened (Minimal Wear)\t$4,588\t$466\t16\t$442\t$630\tSkinport CSFloat Steam\nAWP | Medusa (Factory New)\t$4,484\t$4,484\t1\t$4,171\tabsent\tSkinport CSFloat Steam\n★ Specialist Gloves | Pillow Punchers (Factory New)\t$4,359\t$4,359\t1\t$4,302\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Pandora's Box (Field-Tested)\t$4,359\t$3,666\t11\t$3,245\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Field-Tested)\t$4,289\t$4,225\t8\t$4,022\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Battle-Scarred)\t$4,124\t$4,124\t1\t$4,279\tabsent\tSkinport CSFloat Steam\nHetzelfde artikel, dezelfde web90-dagen, een enorm verschil in prijs\n\nBeperkt tot artikelen met een mediaan van $100 en ten minste vijf voltooide verkopen, omdat bij een goedkope skin één uitzonderlijke verkoop de verhouding volledig scheeftrekt. Wat overblijft, wordt gedomineerd door Gehard afwerkingen, waarbij het patroon bepalend is voor de prijs en de marktplaats elk patroon onder één naam registreert — hetzelfde mechanisme dat in paragraaf 05. wordt gemeten aan de hand van de float\n\nArtikel\tHoogste waarde versus mediaan\tHoogste omzet\tMediane verkoopprijs\tVerkoop\tBekijk het eens\n★ Talon Knife | Case Hardened (Minimal Wear)\t+884%\t$4,588\t$466\t16\tSkinport CSFloat Steam\nDesert Eagle | Cobalt Disruption (Factory New)\t+859%\t$1,210\t$126\t115\tSkinport CSFloat Steam\nAWP | BOOM (Minimal Wear)\t+814%\t$1,232\t$135\t89\tSkinport CSFloat Steam\nAK-47 | Case Hardened (Well-Worn)\t+769%\t$1,720\t$198\t70\tSkinport CSFloat Steam\nAWP | Graphite (Factory New)\t+761%\t$1,469\t$171\t124\tSkinport CSFloat Steam\n★ Talon Knife | Case Hardened (Field-Tested)\t+509%\t$2,437\t$400\t48\tSkinport CSFloat Steam\n★ Kukri Knife | Case Hardened (Minimal Wear)\t+448%\t$723\t$132\t69\tSkinport CSFloat Steam\n★ Kukri Knife | Case Hardened (Field-Tested)\t+415%\t$549\t$106\t128\tSkinport CSFloat Steam\n★ Ursus Knife | Case Hardened (Minimal Wear)\t+371%\t$597\t$127\t12\tSkinport CSFloat Steam\nAK-47 | Case Hardened (Field-Tested)\t+369%\t$1,037\t$221\t125\tSkinport CSFloat Steam\nAK-47 | Red Laminate (Minimal Wear)\t+360%\t$552\t$120\t18\tSkinport CSFloat Steam\nAWP | Asiimov (Field-Tested)\t+351%\t$528\t$117\t439\tSkinport CSFloat Steam\nAK-47 | Vulcan (Field-Tested)\t+337%\t$865\t$198\t241\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Nightwish (Factory New)\t+322%\t$625\t$148\t31\tSkinport CSFloat Steam\nAWP | Lightning Strike (Factory New)\t+319%\t$2,065\t$493\t198\tSkinport CSFloat Steam\nStatTrak™ AWP | Redline (Minimal Wear)\t+312%\t$574\t$139\t24\tSkinport CSFloat Steam\nStatTrak™ AWP | Asiimov (Battle-Scarred)\t+287%\t$524\t$135\t37\tSkinport CSFloat Steam\nAK-47 | Redline (Minimal Wear)\t+277%\t$562\t$149\t112\tSkinport CSFloat Steam\nAWP | Crakow! (Factory New)\t+275%\t$379\t$101\t72\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Vulcan (Factory New)\t+272%\t$5,275\t$1,418\t12\tSkinport CSFloat Steam\n\nDit is een hoogste koers van de dag (90-), GEEN hoogste koers ooit (all-time high), en het betreft ÉÉN beurs. Nergens in dit dossier wordt een hoogste koers ooit vermeld. Een aandeel waarvan de hoogste koers van de dag (Skinport) niet in het overzicht is opgenomen, ontbreekt volledig in deze verzameling; daarom is de verzameling kleiner dan de volledige telling.\n\nVerificatielinks worden samengesteld op basis van de platform-ID’s van de catalogus zelf. Ze verwijzen naar de pagina van het betreffende artikel op de betreffende marktplaats, zodat een lezer het figuur kan vergelijken met de bron in plaats van met ons. Uitgaande links bevatten rel=\"nofollow\": het gaat om verwijzingen, geen aanbevelingen, en een aantal van de bestemmingen zijn marktplaatsen waarover dit onderzoek kritiek uit.\n\n09 / herkomst en grenzen\nWaar dit vandaan komt en wat het niet kan weergeven\n\nAlle cijfers op deze pagina zijn opnieuw berekend op basis van twee snapshotbestanden waarvan de hashes ernaast zijn gepubliceerd. Niets op deze pagina is overgenomen uit een artikel van een andere website.\n\nBron en toegang\n\ncs2.sh API, GET /v1/prices/latest en GET /v1/schema, eenmalige momentopname, vastgelegd op 2026-09-23T00:44:27.871388581Z, prijzen in USD.\n\nDe gegevens zijn verkregen via een betaald commercieel abonnement van de aanvrager GDPR, zoals vastgelegd in het archief, overeenkomstig de voorwaarden van de aanbieder. Er is geen enkele marktplaats gescraped en er zijn geen inloggegevens van welke marktplaats dan ook gebruikt. De sleutel van de aanvrager wordt buiten deze opslagplaats bewaard en komt hier in geen enkel bestand voor.\n\nHoe een artikel in aanmerking komt\n\nElk basisitem met ten minste één actieve vraagprijs op BUFF, CSFloat, Skinport, YouPin of C5Game wordt op basis van de GOEDKOOPSTE vraagprijs in een prijsband ingedeeld, zodat de band nooit afhankelijk is van Steam. „Steam-dekking” is het aandeel van de items in die band die op het moment van vastlegging een actieve vraagprijs op Steam hebben. Patroon- en fasevarianten worden uitgesloten van de ranglijst omdat Steam deze niet apart vermeldt; als ze zouden worden meegeteld, zou Steam te laag worden weergegeven. Renders zijn de catalogusafbeeldingen voor dezelfde artikelen, die lokaal zijn opgeslagen.\n\nRenders en beeldrechten. Renders van catalogusartikelen zijn afbeeldingen van de aanbieder die worden weergegeven voor dezelfde `market_hash_name` als de prijsregels, en die lokaal worden opgeslagen voor offline weergave en weergave via IPFS. De afbeeldingen zijn geen werk van PhishDestroy: alle productafbeeldingen, logo’s en schermafbeeldingen blijven eigendom van hun respectieve eigenaren (cs2.sh, CSFloat, Skinport, BUFF, YouPin, C5Game, Valve en anderen). Ze worden uitsluitend gereproduceerd ter identificatie en voor berichtgeving van algemeen belang; er wordt geen aanspraak gemaakt op eigendom of licentie.\n\nWat we niet konden verkrijgen\n\nHet gebruikte abonnementsniveau biedt alleen toegang tot actuele momentopnames. Historische en archief-eindpunten waren niet beschikbaar, en op deze pagina wordt nergens melding gemaakt van historische reeksen naast de verkoopcijfers op basis van een voortschrijdend gemiddelde Skinport verschijnt dit in de rubriek 06.\n\nEen momentopname, geen tijdreeks. Het ontbreken van een vermelding op Steam op het moment van vastlegging is geen bewijs dat een artikel daar nooit zal verschijnen; het is de gemeten toestand van het schap op dat moment, en voor prijzen boven het maximum is het ook wat de gepubliceerde regel van Valve vereist: de Community Market van Valve stelt expliciet een maximum van $1,800 per artikel (met een maximaal Steam Wallet-saldo van $2,000; zie Steam Veelgestelde vragen over de Community Market gearchiveerd op 2026-09-21 ↗ en Steam Abonneeovereenkomst § 3.C gearchiveerd op 2026-09-24 ↗).\n\nBeoordeling\n\nDe prijs van een artikel is altijd de goedkoopste actuele vraagprijs, dus een hoge uitschieter kan het totaal nooit opdrijven. De indeling bepaalt welke rijen mogen worden vermeld. Elke prijs die meer dan drie keer zo hoog is als de goedkoopste vraagprijs voor hetzelfde artikel, wordt terzijde geschoven als geen actuele prijs. Categorie A: drie of meer marktplaatsen noteren nog steeds boven de bovengrens en hun mediaan ligt binnen 25 procent van de goedkoopste prijs. Categorie B: twee marktplaatsen komen overeen, of drie komen minder nauwkeurig overeen. Categorie C: één enkele prijs – een vraagprijs, geen marktprijs. Alleen de categorieën A en B worden ergens in dit dossier vermeld.\n\nRegel voor uitschieters: koers > 3.0x de goedkoopste biedprijs voor hetzelfde aandeel.\n\nWaarom de totalen een ondergrens vormen\n\nVoor elke marktplaats geldt voor het artikel dat laagste De vraagprijs wordt vermenigvuldigd met het aantal exemplaren dat in de catalogus staat vermeld. Elk ander exemplaar daar heeft een prijs die gelijk is aan of hoger is dan die laagste vraagprijs, dus de werkelijke gepubliceerde waarde is per definitie hoger, niet op basis van een schatting. Het is geen verkoop, geen kasstroom en geen waardering van de CS2-economie.\n\nKijk maar eens zelf\n\nDe afgeleide datasets waarop elke grafiek op deze pagina is gebaseerd, worden in hun geheel gepubliceerd: de Atlas-dataset, het beoordelings- en artefactenscherm, de onderliggende volkstelling en het manifest met de SHA-256s van elke onbewerkte snapshot.\n\nEen correctie die in de openbaarheid is vastgelegd\n\nEen eerdere versie van het bijbehorende register begon met een Souvenir AK-47 | Point Disarray, aangeboden voor $148,954 op een Chinese marktplaats, terwijl Steam het op $119. had geprijsd. Die vermelding is van klasse C: één schap, één exemplaar en geen andere marktplaats die de prijs bevestigt. Het is een vraagprijs, geen verkoopprijs, en het is hier en op die pagina naar beneden bijgesteld. De bevestigde koploper is Sticker | Titan (Holo) | Katowice 2014 op $66,285, geciteerd door 4: marktplaatsen die binnen 5.2% van elkaar liggen — en die helemaal niet voorkomen op Steam.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Atlas van de prijsladder voor Skin — De liquiditeitsklif"
          },
          {
            "level": 2,
            "id": null,
            "text": "De afgrond ligt in de regel, niet op verzoek"
          },
          {
            "level": 3,
            "id": null,
            "text": "Wat de vorm uitsluit"
          },
          {
            "level": 2,
            "id": null,
            "text": "Een vraagprijs is geen prijs"
          },
          {
            "level": 3,
            "id": null,
            "text": "A  Drie of meer planken komen overeen"
          },
          {
            "level": 3,
            "id": null,
            "text": "B  Twee planken komen overeen"
          },
          {
            "level": 3,
            "id": null,
            "text": "C  Eén plank — niet in gebruik"
          },
          {
            "level": 3,
            "id": null,
            "text": "Wat deze correctie heeft gekost en wat ze heeft opgeleverd"
          },
          {
            "level": 3,
            "id": null,
            "text": "Vermeldingen die als artefacten zijn aangemerkt"
          },
          {
            "level": 2,
            "id": null,
            "text": "Alle categorieën op 419, met vermelding van het object waarop elke prijs betrekking heeft"
          },
          {
            "level": 2,
            "id": null,
            "text": "De schappen waarop staat wat Steam niet zal vermelden"
          },
          {
            "level": 2,
            "id": null,
            "text": "Hoe schaars het aanbod eigenlijk is"
          },
          {
            "level": 2,
            "id": null,
            "text": "Wat de schappen van derden daadwerkelijk opleverden"
          },
          {
            "level": 2,
            "id": null,
            "text": "Zestien jaar oude stickers en een handvol handschoenen"
          },
          {
            "level": 2,
            "id": null,
            "text": "Hoogste koersen die worden ondersteund door een transactie, niet door een beursnotering"
          },
          {
            "level": 3,
            "id": null,
            "text": "De dertig hoogste afgeronde verkopen in deze periode"
          },
          {
            "level": 3,
            "id": null,
            "text": "Hetzelfde artikel, dezelfde web90-dagen, een enorm verschil in prijs"
          },
          {
            "level": 2,
            "id": null,
            "text": "Waar dit vandaan komt en wat het niet kan weergeven"
          },
          {
            "level": 3,
            "id": null,
            "text": "Bron en toegang"
          },
          {
            "level": 3,
            "id": null,
            "text": "Hoe een artikel in aanmerking komt"
          },
          {
            "level": 3,
            "id": null,
            "text": "Wat we niet konden verkrijgen"
          },
          {
            "level": 3,
            "id": null,
            "text": "Beoordeling"
          },
          {
            "level": 3,
            "id": null,
            "text": "Waarom de totalen een ondergrens vormen"
          },
          {
            "level": 3,
            "id": null,
            "text": "Kijk maar eens zelf"
          },
          {
            "level": 3,
            "id": null,
            "text": "Een correctie die in de openbaarheid is vastgelegd"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/nl/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/nl/skin_atlas#gallery",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://skinport.com/market?search=AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260924114457/https://store.steampowered.com/subscriber_agreement/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-atlas.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-artefact-screen.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-above-the-ceiling.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/nl/skin_atlas.content.json",
      "export_json_sha256": "cedf82efca7424bcbffdcf9751e7e62e673ea6b0b6e6709d8d2e93a90c20af56"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "nl/social_graph.html",
      "language": "nl",
      "title": "Volg de vastgelegde verbanden — Het dossier ‘Steam’",
      "source_url": "https://phishdestroy.io/steam_dossier/nl/social_graph",
      "source_html_sha256": "c8b2efcfa84b613945e4a93a76cbe12e7c24c426bf027432b45971bef75cae40",
      "exported_at": "2026-09-29T00:18:37.142Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "social_graph.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/nl/social_graph.pdf?v=print-20260929-v5",
        "sha256": "24077c867f2888888e87994e9917d7ba2f6d60bae6e89c1a21ed87e61aedc6e7",
        "bytes": 119750,
        "pages": 6
      },
      "integrity": {
        "signed_object": "social_graph.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "social_graph.content.json.asc",
        "digest_file": "social_graph.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify social_graph.content.json.asc social_graph.content.json",
          "sha256sum -c social_graph.content.json.sha256"
        ]
      },
      "content": {
        "text": "Volg de verbanden.Controleer elke relatie.\n\nZoek een profiel. Kies een relatietype. Volg de directe buren ervan in de vastgelegde gegevens. Onderzoekstool: Randen geven openbare relaties weer, en zijn geen bewijs van direct contact, onderlinge afstemming of wangedrag tussen twee willekeurige knooppunten. Een knooppuntindeling van het type ‘3,435-’ kan het beste worden geïnterpreteerd met behulp van filters.\n\nOntdek één relatie tegelijk\n\n💡 Klik op knooppunten en sleep ze om de grafiek te herschikken. Beweeg de muis erover om gedetailleerde profielen te bekijken. Blauwgroene ononderbroken lijnen = vriendschappen, amberkleurige stippellijnen = wederzijdse reacties.\n\nType relatieProfiel en directe buren\n\n3,435 profielen · 4,551 opgeslagen links\n\nZoek en kies een profiel, of klik op een knooppunt. Alleen de direct geregistreerde buren blijven over. Een rand geeft een relatie weer; deze zorgt niet voor onderlinge afstemming.\n\nProfielen in de verzamelde dataset\n\nVolledige brontabel: alle rijen van 3,435 downloaden (CSV). De onderstaande tabel toont in eerste instantie de eerste 25 rijen; via de zoekfunctie en paginering kunt u de volledige dataset bekijken.\n\n1–25 / 3,435 rijen\nNaam van het personage\tSteamID64\tPrivacy\tStatus\tGroepslidmaatschappen\tBevroren voorraad (USD)\tLocatie\nMahatma Gandhi\t76561198333721623\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tPH\nGalley//갤리🌠🌙\t76561198043416832\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tKP\n$Schlächter\t76561198860277343\tPUBLIC\tClean\tsteambans\t$0.00\tUnknown\n❄r3dsn0w000™❄ [Cristi]🎮\t76561197986767957\tPUBLIC\tClean\tCommunityLegends\t$0.00\tRO\n(2a03) Wolfy\t76561197991671851\tPUBLIC\tCommunity\tsr_public\t$0.00\tUS\nZloy2288\t76561198038578334\tPUBLIC\tClean\tsteambans\t$0.00\tBY\njessy\t76561198039125237\tPUBLIC\tCommunity, VAC (1x)\tCommunityLegends\t$0.00\tJP\nJithraRufure\t76561198071896910\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\n| Níllerdínho |\t76561198003487438\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tDK\nJones is back\t76561198023013026\tPRIVATE\tVAC (1x)\tsteambans\t$0.00\tUnknown\nUNEX | ★✠☠ MoH3st ☠✠\t76561198050763123\tPUBLIC\tClean\tsteambans\t$0.00\tDE\nTrojan\t76561198048457084\tPUBLIC\tClean\tCommunityLegends\t$0.00\tDE\n𝗠𝗮𝘆𝘂 ❤\t76561199377967696\tPUBLIC\tClean\tsr_public\t$0.00\tIS\nbig fucking idiot\t76561198871206397\tPUBLIC\tVAC (1x)\tsteambans\t$0.00\tUnknown\nSOFF Games\t76561198227129276\tPUBLIC\tClean\tcommunitymoderators\t$0.00\tRU\nThijminecraft02\t76561198253895669\tPUBLIC\tClean\tSteamIDcouk SArchive\t$0.00\tNL\nStatic-sama\t76561198289329793\tPUBLIC\tClean\tsteambans\t$0.00\tJP\n𝙸mmortal 𝚂targazer\t76561198142116760\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\nCommander Keen\t76561197987773287\tPUBLIC\tClean\tsteambans\t$0.00\tBE\nS1mX\t76561199648509165\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\nmixwell\t76561199276547472\tPUBLIC\tClean\tsr_public\t$0.00\tJP\nP90_GOD_YyEs™\t76561198285821942\tPUBLIC\tClean\tsteambans\t$0.00\tHK\nhewwo?\t76561199133807546\tPUBLIC\tVAC (1x)\tsteambans\t$0.00\tCH\n♕Kamikaze Atze♕\t76561198002700103\tPUBLIC\tClean\tsteambans\t$0.00\tDE\nPastica\t76561198154655970\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tDZ\nGeregistreerde vriendschapsbanden\n\nVolledige brontabel: alle rijen van 4,299 downloaden (CSV). De onderstaande tabel toont in eerste instantie de eerste 25 rijen; via de zoekfunctie en paginering kunt u de volledige dataset bekijken.\n\n1–25 / 4,299 rijen\nGebruiker A\tRichting\tGebruiker B\tRelatietype\nMahatma Gandhi\n76561198333721623\t↔\tDeskjet\n76561198272738437\tMutual Friends\nGalley//갤리🌠🌙\n76561198043416832\t↔\tomega\n76561197960274529\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tFisty\n76561198057301486\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tFaalagorn\n76561198001116101\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tMURK\n76561198036995672\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tÅρøᴛʜℯᴛȋᴄÅʟȋℯη ♛👽♛\n76561197984615267\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tsilatrak\n76561197999629462\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tBlack Blade\n76561198083368493\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tAvenger\n76561197978249317\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tRemtar\n76561198124322650\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tCato\n76561197961345984\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t✪ G λ M Ξ ®\n76561197994308495\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tclees42\n76561198030936806\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t𝓜ε𝔰𝔥 | AusLevels\n76561198108828539\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tSgtFopper™\n76561198002555892\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t❥Miss Bee\n76561198046958996\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tTesTy\n76561198032370068\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tskl_andrey\n76561198136881436\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t\"Exekutor\"\n76561198009583947\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tAraripe\n76561198103754372\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tsteve6678\n76561198053200093\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\ttrinner\n76561197970359081\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tSteph S.\n76561198025653291\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tKirito\n76561198154545657\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tDoc. todt\n76561197984492467\tMutual Friends\nLinks naar opgenomen reacties\n\nVolledige brontabel: alle rijen van 252 downloaden (CSV). De onderstaande tabel toont in eerste instantie de eerste 25 rijen; via de zoekfunctie en paginering kunt u de volledige dataset bekijken.\n\n1–25 / 252 rijen\nAuteur\tRichting\tDoelgroepprofiel\tDatum\tTekst van de opmerking\nDeskjet\n76561198272738437\t→\tMahatma Gandhi\n76561198333721623\t16 September, 2021 @ 11:02:05 pm PDT\t\"𝑵𝒐𝒘 𝒊𝒇 𝑰 𝒇𝒖𝒄𝒌 𝒕𝒉𝒊𝒔 𝒎𝒐𝒅𝒆𝒍𝑨𝒏𝒅 𝒔𝒉𝒆 𝒋𝒖𝒔𝒕 𝒃𝒍𝒆𝒂𝒄𝒉𝒆𝒅 𝒉𝒆𝒓 𝒂𝒔𝒔𝒉𝒐𝒍𝒆𝑨𝒏𝒅 𝑰 𝒈𝒆𝒕 𝒃𝒍𝒆𝒂𝒄𝒉 𝒐𝒏 𝒎𝒚 𝑻-𝒔𝒉𝒊𝒓𝒕𝑰'𝒎𝒎𝒂 𝒇𝒆𝒆𝒍 𝒍𝒊𝒌𝒆 𝒂𝒏 𝒂𝒔𝒔𝒉𝒐𝒍𝒆\" - Nelson Mandela\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t22 November, 2021 @ 4:10:28 pm PDT\thttps://anige.horigiri.net/?cat=22\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t18 November, 2021 @ 12:45:26 am PDT\thttps://gamerch.com/umamusume/entry/250411\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t8 August, 2021 @ 4:13:25 am PDT\thttps://modoocode.com/304\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t6 February, 2021 @ 3:35:05 pm PDT\t▤ ∫︹- -ω⁾ ⁽︹▓▓︺\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t11 December, 2019 @ 1:50:53 am PDT\thttps://blog.naver.com/aksenwlddj12/221369410039\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t2 October, 2019 @ 7:11:59 am PDT\tǤαllєу║︎갤리..۩\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t9 April, 2019 @ 12:51:28 pm PDT\tExplosiveDamage(owner, from, maxrange, minrange, distmultiplier, dmgmultiplier, mindamage, typ, damagetype, ignore)\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 12:22:47 pm PDT\tinfo - sh_titles.lua\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 12:21:46 pm PDT\tlocal nibbas = 1344 init.lua\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 11:31:58 am PDT\thttp://foreign.aladin.co.kr/shop/wproduct.aspx?ItemId=123955531&start=slayer\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t3 April, 2019 @ 1:26:41 am PDT\tǤαllєу\nLei\n76561198982197954\t→\tJithraRufure\n76561198071896910\t29 December, 2024 @ 12:58:08 pm PDT\t+rep he knows how 2 rush B ￣ヘ￣\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t2 September, 2026 @ 5:16:55 am PDT\tlol\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t20 August, 2026 @ 6:11:03 am PDT\t?\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t25 July, 2026 @ 7:20:05 am PDT\thahahahaha\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t30 June, 2026 @ 12:52:42 pm PDT\twow\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t30 June, 2026 @ 12:41:32 pm PDT\txD\nvalorant enjoyer\n76561199112142402\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:26:30 pm PDT\toh no!!\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:26:11 pm PDT\toh no!!\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:22:22 pm PDT\tomg !!! they know my secret, omg!!!\nvalorant enjoyer\n76561199112142402\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:21:39 pm PDT\t+rep good ♥♥♥♥♥ player\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:20:50 pm PDT\tomg! u cant cheat on secure gaben servers, omg dont report me, they ban me for boosted omg\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 8:37:11 pm PDT\txD\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t28 June, 2026 @ 1:58:14 pm PDT\twow",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Volg de verbanden.Controleer elke relatie."
          },
          {
            "level": 2,
            "id": null,
            "text": "Ontdek één relatie tegelijk"
          },
          {
            "level": 2,
            "id": null,
            "text": "Profielen in de verzamelde dataset"
          },
          {
            "level": 2,
            "id": null,
            "text": "Geregistreerde vriendschapsbanden"
          },
          {
            "level": 2,
            "id": null,
            "text": "Links naar opgenomen reacties"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-profiles.csv",
          "https://steamcommunity.com/profiles/76561198333721623",
          "https://steamcommunity.com/profiles/76561198043416832",
          "https://steamcommunity.com/profiles/76561198860277343",
          "https://steamcommunity.com/profiles/76561197986767957",
          "https://steamcommunity.com/profiles/76561197991671851",
          "https://steamcommunity.com/profiles/76561198038578334",
          "https://steamcommunity.com/profiles/76561198039125237",
          "https://steamcommunity.com/profiles/76561198071896910",
          "https://steamcommunity.com/profiles/76561198003487438",
          "https://steamcommunity.com/profiles/76561198023013026",
          "https://steamcommunity.com/profiles/76561198050763123",
          "https://steamcommunity.com/profiles/76561198048457084",
          "https://steamcommunity.com/profiles/76561199377967696",
          "https://steamcommunity.com/profiles/76561198871206397",
          "https://steamcommunity.com/profiles/76561198227129276",
          "https://steamcommunity.com/profiles/76561198253895669",
          "https://steamcommunity.com/profiles/76561198289329793",
          "https://steamcommunity.com/profiles/76561198142116760",
          "https://steamcommunity.com/profiles/76561197987773287",
          "https://steamcommunity.com/profiles/76561199648509165",
          "https://steamcommunity.com/profiles/76561199276547472",
          "https://steamcommunity.com/profiles/76561198285821942",
          "https://steamcommunity.com/profiles/76561199133807546",
          "https://steamcommunity.com/profiles/76561198002700103",
          "https://steamcommunity.com/profiles/76561198154655970",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-connections.csv",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-comments.csv"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/nl/social_graph.content.json",
      "export_json_sha256": "ef812af056e7e3f41af4ce5db2ba95aa9192269dd1fd9cb830524eac828ca611"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "nl/steam_enforcement_evidence.html",
      "language": "nl",
      "title": "Regels versus reacties — Het dossier ‘Steam’",
      "source_url": "https://phishdestroy.io/steam_dossier/nl/steam_enforcement_evidence",
      "source_html_sha256": "f39daab455235102889e270992921b09ea6aa68d95da216450b503c2d081fb01",
      "exported_at": "2026-09-29T00:18:36.450Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "steam_enforcement_evidence.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/nl/steam_enforcement_evidence.pdf?v=print-20260929-v5",
        "sha256": "ac78b020265ec10d6b83391744e495b0a67df027741120787af4500b71325135",
        "bytes": 379326,
        "pages": 36
      },
      "integrity": {
        "signed_object": "steam_enforcement_evidence.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "steam_enforcement_evidence.content.json.asc",
        "digest_file": "steam_enforcement_evidence.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify steam_enforcement_evidence.content.json.asc steam_enforcement_evidence.content.json",
          "sha256sum -c steam_enforcement_evidence.content.json.sha256"
        ]
      },
      "content": {
        "text": "Aanvullend bewijsmateriaal / aan bronnen gekoppelde gegevens\nSteam Handhavingsbewijs — Ondersteunende documenten & ontwikkelaarsnetwerk\n\nDe regel. Het antwoord.\n\nWAT IN DIT HOOFDSTUK WORDT AANGETOOND\n\nDeze bewijskamer vergelijkt de officiële abonneeovereenkomst van Valve met gedateerde handhavingslogboeken, oplossingen voor ondersteuningsgeschillen en gegevens van het ontwikkelaarsnetwerk uit de 252-repositories en 3,320-profielen. Hieruit blijkt dat gewone accounthouders te maken krijgen met onweerlegbare handhavingsmaatregelen en beëindiging van ondersteuning na inbreuken op hun sessies, terwijl grootschalige commerciële botoperaties ononderbroken doorgaan met toegang tot openbare infrastructuur.\n\n← Terug naar het Executive Briefing\n\nLees de schriftelijke beperking. Open het opgenomen antwoord. Vergelijk wat er in de bron staat met wat nog onbeantwoord is gebleven.\n\nOndersteuning en beroepen ↓Openbare infrastructuur ↓\n252archiefdocumenten\n3,320openbare profielen\n4,214afzonderlijke profiel-repository-paren\n98,902profielparen met gedeelde repositories\n01 / Ondersteuning, sancties en herstel\nLees de klacht.Voeg de bron bij.\nGalerij met afgewezen aanvragen (tentoonstellingen van 981) ↗Geselecteerde records downloaden ↓\nHFB / DE UITBESTEDINGSZAAKHet algemeen aanvaarde compromis.\nDe gemelde ontslagen.\n\nBekijk het hieronder weergegeven antwoord van de klantenservice en de bron van de bewering over het personeel van de aannemer.\n\nOpen het dossier en de bronnen ervan →\n\nHieronder: vijf geconserveerde openbare Reddit-berichten uit de meegeleverde verzameling ondersteuningsgegevens. Elk record documenteert een gemelde interactie met het ondersteuningssysteem van Valve — bewaard met de oorspronkelijke bronlink, de opnamepositie en de volledige tekst. Dit zijn getuigenissen van slachtoffers. De geverifieerde ondersteuningslogs die deze zouden bevestigen of weerleggen, worden bewaard door Valve en zijn niet openbaar gemaakt.\n\n01\nBan & review2024-12-09\nPermanent sanction & closed appeals\n\nThe author reports a permanent account ban, repeated ticket closures and a planned GDPR access request.\n\nREDDIT / PUBLIC TESTIMONYr/ohnePixelCapture record 294\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 303 words\nPermanently banned Steam account without a clear explanation, need help!\n\nsteam_support_tickets_MEGA.json / record 294\n\nHey everyone,\n\nI’m in a really frustrating situation, and I’m hoping someone here can help me or offer advice. My Steam account was just permanently banned for allegedly violating the Steam Subscriber Agreement, and I have no idea why.\n\n# What Steam Support told me:\n\nThe support message said my account was banned due to:\n\n* Suspicious activities related to transferring or attempting to sell/trade the account.\n* Community reports and other unspecified factors.\n\nThey added that the ban is permanent and that they can't help me further. They also warned that future support requests regarding this ban might be ignored. 😞\n\n# Why I’m contesting this ban:\n\n* I have never sold, traded, or transferred my account. I’ve been the legitimate owner since the beginning.\n* On the day the ban occurred, I did nothing noteworthy that could have triggered such a sanction.\n* I received no prior warning, which feels incredibly unfair.\n\n# What I’ve tried so far:\n\n* Contacting Steam Support: I explained my situation and asked for more details, but they’re sticking to their decision and closing my tickets.\n* I’m preparing a request based on my Right of Access (GDPR) to get all the data related to my account.\n\n# Questions for the community:\n\n1. Has anyone successfully had a permanent ban lifted on Steam?\n2. Are there steps I can take to prove I’m the legitimate owner of the account?\n3. Any advice on how to word my request to convince support to reconsider my case?\n4. Would it be helpful to contact the CNIL (I’m based in France) to force Steam to provide more information?\n\nI’m really desperate at the thought of losing all my games, purchases, and years of playtime. Thanks in advance for any help and advice you can give!\n\nhttps://preview.redd.it/jk9qv0gmhv5e1.png?width=1289&amp;format=png&amp;auto=webp&amp;s=b3a333ebb08ea133e2c8747ba126f5a68283d9f7\n\nhttps://preview.redd.it/4sopt0gmhv5e1.png?width=1022&amp;format=png&amp;auto=webp&amp;s=56195d5336118faf9413f1514ead7e8d24c788c3\n\nhttps://preview.redd.it/eqrxw0gmhv5e1.png?width=996&amp;format=png&amp;auto=webp&amp;s=ff3539d28ab754e513ad471822c5de652920101d\n\nhttps://preview.redd.it/728xz0gmhv5e1.png?width=1034&amp;format=png&amp;auto=webp&amp;s=bc5335673509929669af785aa244bf8d2dc58da8\n\n02\nSupport access2025-05-09\nAccount recovery & a reported $10,000 loss\n\nThe author alleges that support reset credentials and removed account protection following another person’s recovery ticket.\n\nREDDIT / PUBLIC TESTIMONYr/legaladviceCapture record 110\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 193 words\nGot $10k stollen from steam inventory due to steam' support fault.\n\nsteam_support_tickets_MEGA.json / record 110\n\nLocation: Quebec, Canada.\n\nLast year, someone hacked my Steam account and stole items worth about $10,000 USD. I only noticed this last week. When I talked to Steam Support, they admitted that someone submitted a ticket to make changes on the account and Steam Support reset my password and turned off all my account security.\n\nI asked Steam Support about getting my items back, but they said there was nothing they could do. They told me I should follow their security recommendations.\n\nThe problem is, I did everything they \"suggested\" to protect an account:\n\n* I had two-factor authentication.\n* My phone number was connected to my account.\n* I used Steam Guard.\n* I printed recovery codes and kept them in a safe.\n\nEven though I did all these things, Steam Support still gave someone else access to my account. The stolen items had been in my account since around 2016-2017. Also, I had not logged in for a few years, so I didn’t accidentally give my information to a fake website.\n\nIs there anything I can do, or do I just have to accept losing $10,000 USD?\n\nThanks for your help.\n03\nRestoration2022-07-07\nA reported $500+ loss & template replies\n\nThe author describes an account compromise, disputed transactions and a support response that allegedly did not address the submitted evidence.\n\nREDDIT / PUBLIC TESTIMONYr/DotA2Capture record 45\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 410 words\nFunds stolen through steam market. Disappointed with Steam response.(or lackthereof)\n\nsteam_support_tickets_MEGA.json / record 45\n\nOn 6th July 2022, 44 unauthorized transactions were made on the steam market using my steam wallet funds totalling roughly $500+ USD to buy worthless 1 cent Dota 2 items. This happened during the wee hours in the morning and i contacted them first thing when i woke up. \n\nI have 2FA enabled all the time, and always thought this would not happen to me as I do not go on betting sites/click sketchy links. My account password + emails were not changed, nor did they take my inventory, just that my funds were used illicitly. Also when I went to disable other APIs, it says there are no other APIs to disable. Shows that it wasn't through me clicking sketchy links and leaving my account details there. Would have lost the whole account if i did so.\n\nWhat baffles me is how did they bypass my 2FA to login my account? Why doesn't steam market purchases go through 2FA as well? First time in 9 years that this happened to me. My acc was logged in 'BY' 'Vitebsk' during the illicit purchases but I'm based in Asia I gathered all the screenshots and provided in the ticket to steam support. \n\nAll i got was the standard copy paste template reply by Steam Support. Lost $500+ and was not even worthy of having a proper person to look into this. I dont think they even read or take a look at the screenshots cause if they did, they would have come to the realization that what happened was clearly fraud, and with a few clicks, reverse the unauthorized transactions, refund my wallet and ban the hijacker. \n\nOver the years, i've spent quite a fair bit on steam but really, this is the kind of recourse we get when our account is compromised? They just don’t care, sigh. I only expect the bare minimum from Steam and looks like even that is quite far-fetched.\n\nSS: https://imgur.com/a/67frcls \n\nHijacker: https://steamcommunity.com/profiles/76561199141246495\n\nSteam Response: https://imgur.com/a/V6v4maM\n\nI could think of a few ways on how to Improve:\n\n1) Add 2FA to market transactions. (even if its bulk posting or selling of items, just 1 2FA notif is required)\n\n2) Enable accounts to be region locked. (if you are migrating, then have to go through steam support etc)\n\n3) Additional Lock on Steam Wallet. (Another password perhaps?)\n\nEDIT: 2nd ticket in and I have still yet to receive a non robotic copy paste template response from Steam.\n04\nRestoration2021-11-29\nSteam Guard & an item-restoration refusal\n\nA preserved post includes the author’s account of item theft and a support response declining restoration.\n\nREDDIT / PUBLIC TESTIMONYr/DotA2Capture record 58\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 563 words\nMany people are losing item via clicking links where steam guard is enabled and steam support doesn't not restore items.\n\nsteam_support_tickets_MEGA.json / record 58\n\nAccounts are getting compromised and might be their pc as well where Steam market is targeted hence the malicious links . I am assuming these hackers are getting encouraged where steam support is not doing nothing and they are getting away with hacking items.  \nLiterally the guy who is supporting the game which he doesn't get any in game advantage just  cosmetics in game only for the sole purpose of supporting the game so that the game will prosper and become beautiful way  to enjoy weekend. But right now players are getting hacked left right and center and steam support  is copy pasting message where in short they are blaming the guy who clicked link. 1st this is happening because they are not targeting players but they are targeting market since they are selling those stuff for real cash via party website. Steam is a huge company and can eradicate the problem or at least can remove links temporarily  in chat since hackers are targeting .They made us install steam guard by saying we wont help if there is no steam guard now steam guard is not enough to save our inventory now they changed their policy  that they should not click any suspicious links. How would we know if the link is suspicious ? After clicking and getting our inventory stolen right !   \n\"we'd have to duplicate an item to restore it. Duplication lowers the value of all items by reducing their scarcity and inflating the economy, which affects everyone involved in trading and the Market. To maintain the value of everyone’s inventory, we do not restore items. For more information, please see the Steam Item Restoration Policy.\"  \nThey care for millions of people IN STEAM MARKET where as few  are losing items which is going to affect market where the rightful owner bought the items and hacker is going to sell the item via 3rd party website and enjoy ! HOW IRONIC !!  \nThis is the message from support where my frnd got his items stolen via clicking on link  \n   \nHi there,  \n\nThank you for the information and screenshots provided.  \n\nIt appears that the account was compromised, please take the following steps to secure your account and computer:  \n\nScan your computer for viruses, key loggers, spyware, and other malicious code using antivirus software with updated virus definitions.  \nChange the password for the email address that is associated with your Steam account.  \nRegularly reset your Steam account password.  \n\nPlease see our Security Recommendations article.  \n\nIn addition, I’m sorry to hear that your items were removed without your permission. Unfortunately, Steam Support does not restore scammed, lost, or stolen items for any reason.  \n\nSince Steam Support does not remove items from accounts, we'd have to duplicate an item to restore it. Duplication lowers the value of all items by reducing their scarcity and inflating the economy, which affects everyone involved in trading and the Market. To maintain the value of everyone’s inventory, we do not restore items. For more information, please see the Steam Item Restoration Policy.  \n\nTo make sure that a scammer is reported, please report them through the Steam Community. Reporting a scammer through the Steam Community is the best way to prevent them from committing future scams.  \n\nTo learn how to avoid scams or hijackings, please see our Trade Scam article.  \n\nIf you still need assistance, please let us know.\n05\nEnforcement2025-05-11\nSelective enforcement & an unexplained ban\n\nA community member describes a disputed ban and contrasts it with the visibility of commercial gambling promotion.\n\nREDDIT / PUBLIC TESTIMONYr/SteamUncensoredCapture record 107\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 1,208 words\n🚨 Steam Bans Without Reason and Ignores Its Community — What’s Going On?\n\nsteam_support_tickets_MEGA.json / record 107\n\nHey r/Steam,\n\nI’m writing this to share my thoughts and concerns about my friend [moneylead](https://steamcommunity.com/id/moneylead/) and Steam’s policies in general. I spoke with him yesterday about his situation, though I didn’t discuss writing this post with him—I asked last night, but he hasn’t responded yet. I want to highlight that this issue is broader than just his case, and while Steam might make changes in the future (though that’s unlikely), I feel the community needs to understand how far Steam has strayed from its original values. I’m not trying to put moneylead in a tough spot with this thread—all the info I’m sharing is public, nothing secretive. I hope he won’t be upset with me, but the community needs this case to see the bigger picture and how Steam feels completely unaccountable.\n\n**Why Does Steam Ignore Its Community?**  \nWhy does a platform like **Roblox** provide a detailed log of ban reasons, while Steam, which claims to be \"community-driven,\" ignores its community, bans whoever they want, for whatever they want, with no transparency? I looked into Roblox as a popular game—not a direct competitor to Steam—to see how their bans look, and you can check it out yourself: [Roblox Ban Reasons](https://www.google.com/search?q=Roblox+ban). Their bans are clear, detailed, and actually explain what you did wrong. I think most decent gaming communities operate like this—not with support agents named Olga, hired through outsourcing, who only know how to send canned auto-replies. Take cases like St4ck—or my friend **moneylead**. All these unbans, like **St4ck’s** or **Alexanddd’s**, happened behind closed doors with zero comments from Steam. Of course, it’s convenient for Steam to handle everything in secret, so no one knows or sees what’s going on—but this violates Steam’s own community rules and principles.\n\n**Who Is moneylead?**  \nI’ve known [moneylead ](https://steamcommunity.com/id/moneylead/)since around 2021. We played Dota 2 a couple of times, and then I just stayed on his friends list. He’s always been a legit player, bringing revenue to Steam through purchases. He never sold his skins, whether in **Dota or CS2—he wasn’t a trader**. All he did was:\n\n* Buy games and skins.\n* Collect badges to level up his profile.\n\nAccording to [SteamSets](https://steamsets.com/account/76561199080934614), he’s given out 324,000 Steam Points—I think he awarded profile rewards to all his friends in the list (though I’m not 100% sure). I do know he ran contests and gave gifts to friends, always supporting the community.\n\n**Steam’s Unfair Treatment**  \nI’ve seen Steam remove his showcases, avatar, description, and even his country multiple times—just because he’s from **Ukraine**. He has a ton of haters leaving toxic comments on his wall, and Steam seems to favor **Russian** users. Every time he tried to appeal the removal of his showcases or profile description—which didn’t break any rules, just had his Instagram link, and his avatar is the same as it is now—Steam moderators didn’t care. **They don’t care about top players who bring them massive revenue, nor about regular users.**\n\n>*Here’s the worst part: moneylead works in cybersecurity, specifically fighting account theft and phishing. He’s neutralized over 5,000 threats targeting Steam alone. And yet, Steam bans him for \"account hijacking\"?*\n\nIf you roughly calculate moneylead’s contribution to Steam and the community—his profile, level, badges (not skins, you can’t sell those)—is this normal, Steam? Banning people, closing tickets, and ignoring users with a spotless reputation who aren’t involved in any commercial activity, just bringing you profit without taking anything in return?\n\n**Steam’s Double Standards**  \nI’m honestly shocked:\n\n* YouTubers who promote casinos and skin gambling? Steam’s fine with that.\n* A cybersecurity expert who fights scams, doesn’t promote casinos, and openly talks about it on his profile? **Banned with no explanation, ignored, and denied an unban.**\n\nI wonder if Steam deliberately bans a high-level account once a year just because of their impunity—maybe for hype or something. Otherwise, this is just madness. It’s scary to think how many regular players have lost their accounts and skins—not because of scammers, but because of Steam’s desire to ignore, send auto-replies, and do whatever they want.\n\n**How Many Others Are Affected?**  \nHow many others are out there—maybe not as well-known—who just have a few games or skins, get banned for nothing, and receive zero explanation or response? **Is this even legal?** Every other platform provides a detailed log with specific violations, but Steam slaps on the same vague label and sends templated responses.\n\n* How safe is it to buy skins on Steam?\n* What’s the chance Steam will just ban your account for no reason, with no explanation?\n\n**A Message to Valve**  \nI wish moneylead the best in resolving this, but Valve, it’d be great if you remembered what \"community\" means and started following the law. Because right now, it looks like your 30% commission, impunity, and sense of being above the law in the U.S. have given you the idea that you can do whatever you want.\n\nI’m sure there are many others like moneylead and St4ck—people who aren’t public or don’t have the resources to fight back. Let’s unite these cases. **If you’re a U.S. resident who’s been banned by Steam without reason and wants to challenge it, please reach out to me.** I’m finishing my **Juris Doctor (J.D.) program at SMU Dedman School of Law** in Dallas, Texas, and I’m participating in a legal clinical practice under Rule 13 of the Texas Supreme Court.\n\nWhat Steam is doing is absolutely disgusting and illegal, and **I’d be happy to help any gamer (legitimate, with no real violations) who has games or skins with value. This will be beneficial for my practice, and it’s time to put Steam in its place and show them they can’t just dictate their own rules with arbitration**. Let’s take it all the way—not for punishment, but for the sake of the community. Maybe if Steam loses a case, they’ll change their policies and start explaining their actions like most popular gaming communities do. Many of us remember how Steam Support used to recover stolen accounts and ended up “stealing” skins themselves—banning without real reasons is basically the same thing, and that’s a serious accusation.\n\nSo, r/Steam, see you soon. I think you understand what you’re doing and how many people you’ve illegally deprived of their assets. I want to raise this issue—not just for the U.S., but for the entire world. You’ve banned class-action lawsuits? **Welcome to Texas.** I recommend starting to look for licensed attorneys in Texas, because I’d love to discuss your company’s policies, feedback, and support agents named Olga—a name that strongly associates with Russian users. Maybe it’d be easier to move your company to Moscow? But I’d be happy to discuss these critical issues on behalf of the global gaming community.\n\nAlso, I wouldn’t recommend ignoring the lawsuit request that will be sent to your physical address and email address, as the court will proceed without you, and that might upset you—especially since things aren’t going so well for a company with stocks like yours.\n\n**Thanks to everyone who took the time to read this. For those who need real help with an unjust Steam ban without any explanation, I’d be happy to assist. For users from Texas, we can easily file a collective lawsuit against Steam—let’s connect and make it happen.**\n02 / Steam ontwikkelingsnetwerk\nOpenbare infrastructuur.Op grote schaal opgenomen.\nDownload alle gegevens over de ‘252’ ↓\n\nDe meegeleverde output_steam_network Snapshots leggen gegevensopslagplaatsen, openbare relaties tussen bijdragers en forks, en overlappingen in profielen vast. Dit zijn openbaar gemaakte gegevens: wat er is gebouwd, wie eraan heeft bijgedragen en wat er is geforkt. Het papieren spoor van openbare mogelijkheden is waar Valve verantwoording over moet afleggen.\n\nRepository / beschrijving\tBijdragers\tForkers\tOpgeslagen profielen\nalliedmodders/amxmodx\n\nAMX Mod X - Half-Life 1 Scripting and Administration\n\n\t40\t40\t80\nalliedmodders/sourcemod\n\nSourceMod - Source Engine Scripting and Administration\n\n\t40\t40\t80\nDoctorMcKay/node-steam-user\n\nAllows interaction with the Steam network via the Steam client protocol\n\n\t40\t40\t80\nFacepunch/Facepunch.Steamworks\n\nAnother fucking c# Steamworks implementation\n\n\t40\t40\t80\nJustArchiNET/ArchiSteamFarm\n\nC# application with primary purpose of farming Steam cards from multiple accounts simultaneously.\n\n\t40\t40\t80\nodota/core\n\nOpenDota: Open source Dota 2 data platform with automated replay parsing\n\n\t40\t40\t80\nodota/dotaconstants\n\ndotaconstants: Static data for Dota applications\n\n\t40\t40\t80\nodota/web\n\nOpenDota: React web UI for Dota 2 statistics using the OpenDota platform\n\n\t40\t40\t80\nsplewis/get5\n\nCS:GO Sourcemod plugin for competitive matches/scrims\n\n\t40\t40\t80\nSteamDatabase/FileDetectionRuleSets\n\n🔎 Rules to detect game engines and other technologies based on Steam depot file lists\n\n\t40\t40\t80\nSteamRE/SteamKit\n\nSteamKit2 is a .NET library designed to interoperate with Valve's Steam network. It aims to provide a simple, yet extensible, interface to perform various actions on the network.\n\n\t40\t40\t80\nValveSoftware/dxvk\n\ndxvk tree containing branches used by Proton\n\n\t40\t40\t80\nValveSoftware/GameNetworkingSockets\n\nReliable & unreliable messages over UDP. Robust message fragmentation & reassembly. P2P networking / NAT traversal. Encryption.\n\n\t40\t40\t80\nValveSoftware/gamescope\n\nSteamOS session compositing window manager\n\n\t40\t40\t80\nValveSoftware/Proton\n\nCompatibility tool for Steam Play based on Wine and additional components\n\n\t40\t40\t80\nValveSoftware/source-sdk-2013\n\nThe 2013 edition of the Source SDK\n\n\t40\t40\t80\nValveSoftware/wine\n\nWine with a bit of extra spice\n\n\t40\t40\t80\nValveSoftware/steam-devices\n\nList of devices Steam and SteamVR will want read/write permissions on, to help downstream distributions create udev rules/etc\n\n\t39\t40\t79\nValveSoftware/steam-audio\n\nSteam Audio\n\n\t38\t40\t78\nalliedmodders/metamod-source\n\nMetamod:Source - C++ Plugin Environment and Detour Library for the Source Engine\n\n\t37\t40\t77\nalliedmodders/sourcepawn\n\nA small, statically typed scripting language.\n\n\t35\t40\t75\nValveSoftware/Fossilize\n\nA serialization format for various persistent Vulkan object types.\n\n\t31\t40\t71\nrlabrecque/Steamworks.NET\n\nSteamworks wrapper for Unity / C#\n\n\t27\t40\t67\nModDota/moddota.github.io\n\nModDota github pages project.\n\n\t26\t40\t66\nodota/parser\n\nReplay parse server generating JSON log events from Dota 2 replay files\n\n\t26\t40\t66\nValveSoftware/steam-for-linux\n\nIssue tracking for the Steam for Linux beta client\n\n\t26\t40\t66\nSteamRE/DepotDownloader\n\nSteam depot downloader utilizing the SteamKit2 library.\n\n\t24\t40\t64\nJustArchiNET/ASF-ui\n\nThe official web interface for ASF\n\n\t23\t40\t63\nadvancedfx/advancedfx\n\nHalf-Life Advanced Effects (HLAE) is a tool to enrich content creation mainly for the Counter-Strike series.\n\n\t22\t40\t62\nalliedmodders/ambuild\n\nAlliedModders C++ Build System\n\n\t23\t39\t62\nSteamDatabase/BrowserExtension\n\n💻 SteamDB's extension for Steam websites\n\n\t21\t40\t61\nodota/mobile\n\nReact Native apps for viewing Dota 2 data on Android/iOS\n\n\t19\t40\t59\nValvePython/steam\n\n☁️ Python package for interacting with Steam\n\n\t18\t40\t58\nskadistats/clarity\n\nComically fast Dota 2, CSGO, CS2 and Deadlock replay parser written in Java.\n\n\t13\t40\t53\nSteamRE/open-steamworks\n\nOpen Steamworks is a set of reverse engineered headers for the Valve's Steam Client. More or less abandoned now that the Steamworks SDK is publically available.\n\n\t13\t40\t53\nValveSoftware/Source-1-Games\n\nSource 1 based games such as TF2 and Counter-Strike: Source\n\n\t13\t40\t53\nalliedmodders/hl2sdk\n\nHalf-Life 2 SDK Mirrors\n\n\t11\t40\t51\nSteamDatabase/steamdb.info-issues\n\n🚱 Issue tracker for the SteamDB website\n\n\t11\t40\t51\nCSGOFloat/inspect\n\nSource Code that Powers the CSFloat Inspect Link API\n\n\t10\t40\t50\nValveSoftware/SteamOS\n\nSteamOS community tracker\n\n\t10\t40\t50\nalliedmodders/source2mod\n\nExperimental\n\n\t40\t9\t49\nsmiley/steamapi\n\nAn unofficial object-oriented Python library for accessing the Steam Web API.\n\n\t9\t40\t49\nSteamDatabase/GameTracking\n\n🛢 Dumping things, so you don't have to\n\n\t8\t40\t48\nValveSoftware/counter-strike_rules_and_regs\n\nCS:GO\n\n\t7\t40\t47\nValveSoftware/openvr\n\nOpenVR SDK\n\n\t6\t40\t46\nSteamDatabase/easy-markdown-editor\n\nEasyMDE: A simple, beautiful, and embeddable JavaScript Markdown editor. Delightful editing for beginners and experts alike. Features built-in autosaving and spell checking.\n\n\t40\t4\t44\nValveSoftware/Dota-2\n\nTracker for issues specific to Linux and Mac in the Reborn client. If you have a general issue or non-system-specific feature request please go to dev.dota2.com\n\n\t6\t38\t44\nValveSoftware/Dota2-Gameplay\n\nPublic Bug Tracker for Dota 2\n\n\t4\t40\t44\nJustArchiNET/ArchiBot\n\nNo description in the capture.\n\n\t16\t27\t43\nztizzlegaming/CSGOWinBig\n\nOpen-source Counter-Strike: Global Offensive jackpot betting website.\n\n\t1\t40\t41\nJustArchiNET/mantis.justarchi.net\n\nMantis Bug Tracker (MantisBT)\n\n\t40\t0\t40\nodota/node-steam-user\n\nAllows interaction with the Steam network via the Steam client protocol\n\n\t40\t0\t40\nModDota/TypeScriptAddonTemplate\n\nDota 2 addon template with TypeScript Panorama and VScripts.\n\n\t9\t29\t38\nValvePython/vdf\n\n📜 Package for working with Valve's text and binary KeyValue format\n\n\t6\t32\t38\nalliedmodders/amtl\n\nAlliedModders C++ Template Library\n\n\t17\t19\t36\nValvePython/dota2\n\n🐸 Python package for interacting with Dota 2 Game Coordinator\n\n\t5\t30\t35\nalliedmodders/stripper-source\n\nStripper:Source\n\n\t13\t21\t34\nAllyans3/steam-market-api-v2\n\nSteam Market API v2 package\n\n\t3\t31\t34\nModDota/dota-tutorial\n\nCustom game DOTA tutorial.\n\n\t11\t23\t34\nodota/blog\n\nNo description in the capture.\n\n\t29\t3\t32\nOpsecGuy/BetterGo\n\nExternal CS:GO cheat written in python.\n\n\t1\t27\t28\npxvr-official/1\n\n無許諾配信 企業理念剽窃 動物の森収益化 大神ミオ権利者削除 戌神権利侵害発言 常闇トワ炎上 夜空メルストーカー被害 建築王サポーター放置 赤十字マーク 魔乃アロエ卒業 一つの中國支持声明 大空昴3Dライブ 無限延期清掃員職業差別 日清コラボ楽曲 musedash非公開 rog案件取り消し 壁画ライブ 丁真 Ding Zhen 郑爽 Zheng Shuang 防护林 与朵小天使w 伊月猫凛 本主萌埋午休傻 汪峰 重生细胞 壁纸 比利海灵顿 香蕉君 van 田所浩二 抽象带篮子 抗压背锅吧 季子越 蒋明辉 傻逼…\n\n\t0\t28\t28\nRevadike/InternalSteamWebAPI\n\nDocumenting the unofficial and internal Steam Web API\n\n\t1\t27\t28\nJoeSzymkowiczFiveM/qb-lootcrate\n\nA CSGO-style case opening script\n\n\t2\t25\t27\nAbrarKL/MyRoulette.XYZ\n\nCSGO / Steam Roulette Site created with PHP and Node JS, using the Material Design front-end framework.\n\n\t1\t25\t26\nJustArchiNET/ASF-WebConfigGenerator\n\nNo description in the capture.\n\n\t10\t15\t25\nModDota/dota-data\n\nAuto-generated Dota 2 resource dumps\n\n\t11\t14\t25\nModDota/TypeScriptDeclarations\n\nTypeScript declarations for Dota 2.\n\n\t11\t14\t25\nModDota/API\n\nNo description in the capture.\n\n\t12\t12\t24\nalliedmodders/cssdm\n\nCounter-Strike:Source Deathmatch\n\n\t10\t13\t23\nSteamDatabase/steamstat.us\n\n✅ Front-end of Steam services status website\n\n\t4\t18\t22\nc0deina/csgojackpotV2\n\nCSGO Jackpot Source\n\n\t1\t20\t21\nValvePython/steamctl\n\n🤸 Take control of Steam from your terminal\n\n\t2\t19\t21\nValvePython/csgo\n\n🔫 Python package for interacting with CS:GO Game Coordinator\n\n\t3\t17\t20\nBeepIsla/csgo-crash-exploit\n\nAllows you to crash any Windows user\n\n\t3\t16\t19\nValvePython/vpk\n\n📦 Open, Search, Extract and Create VPKs in python\n\n\t4\t15\t19\nalliedmodders/SM-SteamWorks\n\nExposing SteamWorks functions to SourcePawn.\n\n\t14\t3\t17\nSteamRE/Steam4NET\n\nSteam4NET is a .NET wrapper around the Steamworks C++ interfaces\n\n\t2\t15\t17\nalliedmodders/hl2sdk-manifests\n\nInformation about HL2SDKs shared between Metamod:Source and SourceMod.\n\n\t6\t10\t16\nJustArchiNET/ASF-PluginTemplate\n\nTemplate repository that you can use for creating custom plugins for ArchiSteamFarm.\n\n\t8\t7\t15\nModDota/Dota2AIFramework\n\nGeneral Framework for Dota 2 AI Competitions\n\n\t1\t14\t15\nShkyyl/KeyChamp\n\nExtension for joining free case battle on key-drop automatically\n\n\t1\t14\t15\nSteamDatabase/SteamMonitor\n\n😤 Track Steam's connection manager servers status\n\n\t2\t12\t14\nBaterka/cslore.com\n\nCS:GO gambling site - csgo.style\n\n\t1\t12\t13\nSteamDatabase/SteamTokenDumper\n\n🔢 Submit users' PICS access tokens to SteamDB\n\n\t2\t11\t13\nmonoblocker/roulette\n\nRoulette CS:GO made in React and Typescript\n\n\t1\t11\t12\nzsith/launcher.user.js\n\n// ==UserScript== // @name AposLauncher // @namespace AposLauncher // @include http://agar.io/* // @version 3.062 // @grant none // @author http://www.twitch.tv/apostolique // ==/UserScript== var aposLauncherVersion = 3.062; Nu…\n\n\t1\t11\t12\nLincolnIT/CSGODouble-bot-automated\n\nCSGODouble Automated, auto Betting Bot.\n\n\t1\t10\t11\nvladpuz/steam-market\n\nSteam market API client\n\n\t4\t7\t11\nmcgrizzz/Cstrike.bet\n\nCSGO Roulette Website Angular frontend, nodejs backend, and steam trading bots\n\n\t1\t9\t10\nodota/underlords-web\n\nUI for OpenUnderlords\n\n\t5\t5\t10\nSteamDatabase/SteamToTwitter\n\n🕊 Tweets announcements from various Steam groups\n\n\t1\t9\t10\nModDota/AbilityLuaSpellLibrary\n\nThe successor to the Spell Library by Pizzalol\n\n\t4\t4\t8\nalvinl/bitskins\n\nUnofficial BitSkins API client\n\n\t2\t5\t7\nb1naryth1ef/steamy\n\nA Python Steam community and market API interface that will get you all hot and bothered\n\n\t2\t5\t7\nkratos1812/Case-Opening\n\nIn-game case opening system for CSGO servers.\n\n\t2\t5\t7\nodota/docs\n\nOpenDota API documentation\n\n\t4\t3\t7\nSteamDatabase/steam-advanced-access-fetch-players\n\n📈 Simple script to fetch Steam player count\n\n\t1\t6\t7\nTheRioMiner/CsgoBetterExternalRaytrace\n\nOverridden maps pack for better external raytrace\n\n\t1\t6\t7\nalliedmodders/hl2sdk-mock\n\nMock HL2SDK and Server\n\n\t5\t1\t6\nchristophersu/PySteamMarket\n\nPython API for getting prices from the Steam market.\n\n\t1\t5\t6\nExtremelyd1/Strat-Roulette\n\nCS:GO Sourcemod Plugin\n\n\t2\t4\t6\ngiovanni-orciuolo/double-sdk\n\nA simple way to write CS:GO cheats!\n\n\t2\t4\t6\nJustArchiNET/Madness\n\nMadness embraces your project by including compatibility layer for selected APIs normally not available on .NET Framework target.\n\n\t5\t1\t6\nModDota/TypescriptPanoramaDeclarations\n\nNo description in the capture.\n\n\t4\t2\t6\nodota/rapier\n\nA JavaScript Dota 2 (Source 2) replay parsing library\n\n\t1\t5\t6\nVozn1akHero/CSGOCaseOpeningSimulator\n\nCounter-Strike case opening simulator which resembles the good old CS:GO user interface\n\n\t3\t3\t6\nautarc/steam-store\n\nAPI client for the unofficial steam storefront/big picture resource\n\n\t2\t3\t5\nBETTING-CODE/awesome-esports-sites\n\nA curated list of awesome esport betting sites – live, statistics and other resources.\n\n\t1\t4\t5\njonteohr/Better-Warden\n\nAn improved and more advanced warden plugin with a custom menu for CS:GO jailbreak servers!\n\n\t2\t3\t5\nLudzikk/CSGO-Gambling-Site\n\nhttps://ludzikk.github.io/CSGO-Gambling-Site/\n\n\t1\t4\t5\nModDota/find-steam-app\n\nFind location of an installed Steam app\n\n\t3\t2\t5\nmprey/csgocact.us\n\nsource code for csgocact.us\n\n\t1\t4\t5\nnezu-cc/ServerCrasher\n\nCS:GO Server Crasher\n\n\t1\t4\t5\nodota/testfiles\n\nStores test replay files\n\n\t2\t3\t5\nodota/underlordsconstants\n\nConstant data for Dota Underlords\n\n\t3\t2\t5\nSnaBe/node-steam-market-fetcher\n\nA Node.js wrapper for the Steam Community Market API.\n\n\t2\t3\t5\nSteamDatabase/.github\n\n💗 Organization-wide community health files\n\n\t1\t4\t5\nwolfcon/RIP-HLTV-BET\n\nRIP BET AD (For Tampermonkey) https://greasyfork.org/en/scripts/423484-rip-hltv-bet\n\n\t2\t3\t5\nalliedmodders/blaster.net\n\nSource and GoldSrc Query Tool\n\n\t2\t2\t4\ncatears124/CS2-Price-API\n\nsimple python cs2 steam market price API\n\n\t1\t3\t4\nialakey/caseforge\n\nOpen-source CS2 case-opening platform: Steam auth, provably fair openings, RTP-balanced case builder, withdrawals bought on market.csgo.com and an admin CRM.\n\n\t1\t3\t4\nIlusion9/csgo-fix-mapchange-crash-sm\n\nFix players crash on map change.\n\n\t1\t3\t4\nismail0234/Benson-Map-Crash-Fixer\n\nCSGO Map Change Client Crash Fixer\n\n\t1\t3\t4\njaxwilko/steam-market-api\n\nPHP - Composer Compatible - Steam Market API\n\n\t2\t2\t4\nJustArchiNET/ArchiTag\n\nArchiTag is a very small utility based on Python 3 and Mutagen to provide missing functionality in opusenc of writing specific Opus metadata, such as total number of tracks or track number.\n\n\t1\t3\t4\nModDota/DotaUI\n\nNo description in the capture.\n\n\t2\t2\t4\nnode-steam/market-pricing\n\nWrapper for the unofficial Steam Market Pricing API\n\n\t1\t3\t4\nodota/media\n\nStores media files for Dota projects\n\n\t2\t2\t4\nSergeyIvanovDevelop/Crypto-Steam-Platform\n\nThe repository contains the code and configuration to run a platform for creating cryptocurrency stakes for arbitrary ERC20 tokens.\n\n\t1\t3\t4\nAareksio/csgodouble-floatchecker\n\nAdds context menu option to check item's float value\n\n\t1\t2\t3\nchinm4/CSGOdrop\n\nA online csgo gambling casino that includes a variety of mini games that allows you to win csgo skins\n\n\t2\t1\t3\nCruze03/CSGO-Case-Opening-Prank\n\nCommand:- !prank (Admin flag \"n\" required)\n\n\t1\t2\t3\nDhruva-Kapadia/CSGOTrollGG\n\nCSGO Case Opening Simulator\n\n\t2\t1\t3\nErhanCSGO/CSGOPolygon-prediction\n\nCSGOPolygon.com - prediction script, double your coins by using this tool\n\n\t1\t2\t3\nEv-Hoang/Bedrock-Chest-Case-Opening\n\nHypixel Skyblock Dungeon Mod - Bedrock Chest Opening Animation (CSGO Style)\n\n\t1\t2\t3\njmjp/csgo-roulette\n\nA csgo gambling roulette make with VueJS 3\n\n\t2\t1\t3\nJustArchiNET/ArchiCrowdin\n\nNo description in the capture.\n\n\t1\t2\t3\nLeonSK/WearMarketInspector\n\nRetrieve Wear Value (Float Value) and Pattern Index from Steam Community Market using http://csgo.exchange API\n\n\t1\t2\t3\nmaximgeerinck/csgo-gamble\n\nCSGO gambling website\n\n\t1\t2\t3\nModDota/BugTracker\n\nListing bugs for Dota 2 Custom Games\n\n\t2\t1\t3\nplwp/mma-betting\n\nUFC/MMA betting model with Pinnacle steam detection for AU book latency arb\n\n\t2\t1\t3\nSouthsideswag16/Csgo-Gambling-Site\n\nNo description in the capture.\n\n\t2\t1\t3\ntacyarg/csgofiesta-frontend-react\n\nRemastered version a the long time favorite csgo site\n\n\t2\t1\t3\nVelorasse/Mutah-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-csmoney-csgoskins\n\ngambling script for Mutah, Keydrop, csmoney, and csgoskins, featuring hacks, cheats, and predictors. Offers strategies to boost winning odds and optimize performance on these platforms.\n\n\t3\t0\t3\nalliedmodders/am-github-artifact-webhook\n\nNo description in the capture.\n\n\t2\t0\t2\ncharamza/roulette\n\nCSGO like roulette in JS\n\n\t1\t1\t2\nCruze03/CSGO-PugSetup-RoundRestore\n\nSometimes (player dropped/crashed) which would be disadvantage for a team. It would be very handy to restore the match to the previous round.\n\n\t1\t1\t2\ncsgorol/CSGO-ROLL-Crash-Predictor\n\nCSGO-ROLL-Crash-Predictor\n\n\t1\t1\t2\nFoxSerito/FOXWORLD_plugin_DoubleJump_CSGO\n\nПлагин SourceMod (CSGO). Двойной прыжок с эффектом.\n\n\t1\t1\t2\nhkehayovmoonbiz/CS2-Casino-Full-Source-Code\n\nCS2, CS2 betting platforms, Skin Roulette, Case Unboxing, Crash games, Jackpot, purchase CS2 casino source, crypto gambling\n\n\t1\t1\t2\nJustZakary/steamstoreapi\n\nThis NPM module is a API wrapper that makes the steam unofficial API easier to use.\n\n\t2\t0\t2\njzimr/steam-market-api\n\nA java library to easily get Steam Community Market data\n\n\t1\t1\t2\nMomohime/CSGO.Network-Jackpot-Coinflip\n\nNo description in the capture.\n\n\t1\t1\t2\nnnjjswat/moneybot\n\nautomated bots for bustabit (formerly known as moneypot), csgo crash, etc\n\n\t0\t2\t2\nodota/carry\n\nLegacy Application for donations to the OpenDota project\n\n\t1\t1\t2\nodota/PublicMatchDataBot\n\nA Discord bot to remind users to turn on Expose Public Match Data in the Dota 2 client\n\n\t1\t1\t2\nOrillio/CSGOBet.com\n\nCSGO roulette web app\n\n\t2\t0\t2\nripexz/csgo-bet-alert\n\nA Chrome extension to keep track of active CS:GO Lounge matches.\n\n\t1\t1\t2\nrrpvm/lumen_sense-beta-deprecated-\n\nthis is internal csgo cheat written by me(no paste, self reverse structures). start : ~6 August 2020, end : ~ 14 December 2020\n\n\t1\t1\t2\nRuthless222/csgoscore\n\nThis is a Counter Strike Global Offensive Betting Site. You chose the skins you want to bet and try to win jackpots\n\n\t2\t0\t2\ntfburns/CSGO-cases-PL\n\nExpected profit-loss of CS:GO case openings\n\n\t1\t1\t2\nTomDra/CSGO-Case-Data-Analysis\n\nWorks out the most profitable CS:GO case at that current time\n\n\t1\t1\t2\nValvePython/dota2-wrappers\n\nNo description in the capture.\n\n\t1\t1\t2\nValvePython/teamfortress2-closed-captions\n\nThis project aims to provide a set of closed captions for Team Fortress 2\n\n\t1\t1\t2\nVistaNetGTX/Cstrike.bet-\n\nCSGO Roulette Website Angular frontend, nodejs backend, and steam trading bots\n\n\t1\t1\t2\nwafflas/csgo-case-opening-simulator\n\nI created a cs go case opening simulator for a meme coin\n\n\t0\t2\t2\nAdmiral-Enigma/Le_Coinflip\n\nConflip game\n\n\t1\t0\t1\nadryeljuliao/roulette-csgo\n\nNo description in the capture.\n\n\t1\t0\t1\nAndreuTheG/csgo-coinflip-web\n\nCSGO Gambling Coinflip Website\n\n\t1\t0\t1\nasmilen/csgoDouble\n\na b c\n\n\t1\t0\t1\nb1naryth1ef/csgofort\n\nA CSGO portal for trading, betting, analytics, and more!\n\n\t1\t0\t1\nBaterka/PrivateSteamBettingWebsite2024\n\nPrivate Steam (Counter-Strike 2) betting/gambling website - Roulette, Jackpot\n\n\t1\t0\t1\nblackcaer/SteamTradeHandler\n\nAutomation of Steam trading. Helper project for bet automation.\n\n\t1\t0\t1\nBTheCoderr/theRounders\n\nThe Rounders - A professional-grade sports betting analytics platform combining real-time odds tracking, sharp movement detection, and advanced statistical analysis. Features include line shopping, steam move alerts, power rankings, and comprehensive bet t…\n\n\t1\t0\t1\nCallumHemsley/KazeBot\n\nA Twitch chat betting bot for CSGO, simply bet a certain amount of points, and double if you win, lose all if you lose. Simple.\n\n\t1\t0\t1\nchrisjpm/CSGOJackpotTemplate\n\nFront end for a jackpot site\n\n\t1\t0\t1\ncolinsenner/valve-bug-bounty\n\nFor many years CS:GO, Dota 2, and Team Fortress 2 servers had a bug that allowed malicious users to leak crucial server process memory or reliably crash any server.\n\n\t1\t0\t1\ncoryypeters/nrl-odds-intelligence-pipeline\n\nReal-time sports betting odds intelligence — streaming pipeline that detects line movement, steam, and arbitrage across bookmakers. Python · Redis Streams · FastAPI · React.\n\n\t1\t0\t1\ndeissh/dev-csgoduo\n\nCS:GO. Bot for receiving things on the site (Polygon, Duo, Double and etc).\n\n\t1\t0\t1\ndom1torii/even-better-font-manager\n\nSimply even better cross-platform tool for CS2 Font Management\n\n\t1\t0\t1\nDONnicov/CSGO-crash-black-screen-\n\nsolution csgo crash black screen and close csgo\n\n\t1\t0\t1\nDoubleBoters/CsgoDouble\n\nNo description in the capture.\n\n\t1\t0\t1\ndownarowiczd/DoubleBot\n\nAn old CSGO Double Bot written for my friend. - 07.05.2016\n\n\t1\t0\t1\nErayBahar/steammarketscraper\n\nSteam Market Scraper Python-based tool that tracks real-time CS2 skin prices using Steam's hidden API. It fetches the lowest sell and highest buy offers for any item, helping you monitor deals or snipe underpriced listings automatically.\n\n\t1\t0\t1\nfairydarkness/SteamwebmailAPI\n\nUnofficial Python API for steamwebmail.com Fast, lightweight, and browserless library for automating steamwebmail.com. Support for session management, proxy, folder navigation, and message retrieval\n\n\t1\t0\t1\nFAQU2/CSGO-Coinflip-MyJailShop\n\nSourcemod plugin which provides a Coinflip system for MyJailShop.\n\n\t1\t0\t1\nFlamesONE/csgo-case-opening\n\nNo description in the capture.\n\n\t1\t0\t1\nFunnyRain/csgorun-crash-watch\n\n🚀 CsgoRun dump crash. / 🚀 CsgoRun дамп крашей.\n\n\t1\t0\t1\ngeohdgio/Venatus-Autenticator\n\nეს არის Steam Autenticator ქართული Venatus Trade & Betting ისთვის და Valve News Georgia-სთვის.\n\n\t1\t0\t1\nhakanstarlord/steam-bot\n\nSports betting steam-move signal detection with ML pipeline (XGBoost stacking + isotonic calibration), backtesting engine, Flask dashboard, and Telegram alerts.\n\n\t1\t0\t1\nHvH-gg/CSGO-Item-CrashFix\n\nA plugin for Counter-Strike: Global Offensive that fixes an exploit where receiving CS2 Items will cause CS:GO clients to crash\n\n\t1\t0\t1\nHvH-gg/CSGO-NetMsg-CrashFix\n\nA plugin for Counter-Strike: Global Offensive that fixes an exploit where spamming NetMsg_StringCmd packets would result in a server crash.\n\n\t1\t0\t1\nisybycnsmam/SteamLibrary\n\nLegacy Steam Unofficial API\n\n\t1\t0\t1\nItsTangerine/SteamApis.Net\n\nUnofficial https://steamapis.com .NET library, supporting .NET 6.0+\n\n\t1\t0\t1\nJustArchiNET/JustArchi.net\n\nNo description in the capture.\n\n\t1\t0\t1\nkiri-osint/CS2-Info-Hub-Bot\n\nA Telegram bot that acts as a hub for CS2 players, providing real-time skin prices, server stats, and user profile/inventory inspection using official and unofficial Steam APIs.\n\n\t1\t0\t1\nKoshkaj/monte\n\nGamified csgo gambling platform implementation\n\n\t1\t0\t1\nmadsab/CaseOpening\n\nA school project using Java. Simulating the case opening from CSGO and more.\n\n\t1\t0\t1\nman90es/steamcardexchange-api\n\nSteamCardExchange.net unofficial REST API server (scraper).\n\n\t1\t0\t1\nMattPua/steam-unofficial-docs\n\nUnofficial docs for Steam APIs with fumadocs\n\n\t1\t0\t1\nMetallist1/Portfolio.CsgoWinGambleProject\n\nA website that was done in 2017 September. Websites focus was on gambling with Counter-Strike items. Project was largely completed however backups were not done correctly, this resulted in half a year of wasted improvements to the code. The website was test…\n\n\t1\t0\t1\nmikebobadilla/csgo-jackpot\n\nNo description in the capture.\n\n\t0\t1\t1\nmikebobadilla/meteor-csgojackpot\n\nCssgo Jackpot done in meteor\n\n\t1\t0\t1\nModDota/D2VDump\n\nDota 2 Server VScript API Dumper\n\n\t1\t0\t1\nModDota/DotaTracking\n\nNo description in the capture.\n\n\t1\t0\t1\nModDota/eslint-config\n\nESLint config by ark120202\n\n\t1\t0\t1\nmr-codinglv/Casino-script\n\nscript casino - script betting - exchange script - bc casino - casino csgo - script bet - betwin script\n\n\t1\t0\t1\nMrKeelik/MrKeel\n\nCSGO DOUBLE BOT\n\n\t1\t0\t1\nnoahlatzel/CSGORollHelper\n\nLeveraging positive expected value on triple green jackpots on CSGORoll!\n\n\t1\t0\t1\noddsgpt/oddsgpt-market-intelligence\n\nResearch on football betting markets, closing odds, CLV, market efficiency, steam moves, AI betting systems, and sports market intelligence.\n\n\t1\t0\t1\noEXU/csgo-server-crasher\n\nCSGO SERVER CRASHER\n\n\t1\t0\t1\nPrdTTony/CSGO-Roulette\n\n[CSGO] Roulette System. Bet on RED or Black and win x2 credits\n\n\t1\t0\t1\nr-adamski/csgo-jackpot\n\nNo description in the capture.\n\n\t1\t0\t1\nSahotallo/Turan-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-Skinbaron-hellcase\n\ngambling script for Turan, Keydrop, Skinbaron, and Hellcase, providing hacks, cheats, and predictors. Includes strategies to improve winning chances and enhance gameplay on these platforms.\n\n\t1\t0\t1\nsamuelcsouza/steam-marketplace-api\n\nAn unofficial API to get data from the Steam Marketplace.\n\n\t1\t0\t1\nSKINSTRACK/CS2-Price-API\n\nSkinstrack offers a free, limited API endpoint that returns Steam item prices. Paid plans additionally provide access to pricing data from multiple marketplaces, making it possible to compare prices across different markets through a single API.\n\n\t1\t0\t1\nsnmtriet/CSGO-Casino-Full-Source-Code\n\nCSGO, CSGOEmpire, Case Opening, Case Battles, Roulette, Coinflip, buy csgo gambling site, gambling\n\n\t1\t0\t1\nSteamRE/homebrew-tools\n\nRepository for installation of SteamRE tools via Homebrew (http://brew.sh)\n\n\t1\t0\t1\nSteamRE/opensteamworks.org\n\nNo description in the capture.\n\n\t1\t0\t1\nTheQuack45/CsgoCaseOpenProgram\n\nSimple program to parse an XML file with CS:GO case information and \"simulate\" case openings\n\n\t1\t0\t1\nTLClassless/StratRouletteCSGO\n\nA 'Strat Roulette' web app for CS:GO!\n\n\t1\t0\t1\ntomasoom/csgoCaseOpening\n\nNo description in the capture.\n\n\t1\t0\t1\nvitaliy-evsyukov/steamgifts-autobet-bookmarklet\n\nbookmarklet for automatic bets on steamgifts.com\n\n\t1\t0\t1\nXpravdaX/RouletteCSGO\n\nNo description in the capture.\n\n\t1\t0\t1\nYuiKasumii/steam_api_unofficial\n\nUnofficial Steam Game Information Database\n\n\t1\t0\t1\nZexuz/Steam-Betting\n\nA betting website build ontop of STEAM's ecosystem\n\n\t1\t0\t1\nANK-RULZZ/steam-jackpot-site\n\ngetting some errors and would like some one to help me with it thank you!!!\n\n\t0\t0\t0\nasmilen/CsgoDoubleVS\n\nNo description in the capture.\n\n\t0\t0\t0\nCORNOODOSADAS/CSGOWeed\n\nCsgo Jackpot and Coinflip\n\n\t0\t0\t0\nCSGOApple/csgoapple\n\nJackpot Site\n\n\t0\t0\t0\nCSGOFAST/csgofast-api\n\nNo description in the capture.\n\n\t0\t0\t0\nDonakall/csgoDoublebot\n\nAutomated bot for csgodouble\n\n\t0\t0\t0\nfedor-selivanov/csgo-fast-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nfoldageros/csgod\n\ndouble bot\n\n\t0\t0\t0\ngmod-gambling/gmod-gambling\n\nNo description in the capture.\n\n\t0\t0\t0\nierome/CSGOBoss-BackEnd\n\nBack end version of CSGOBoss. This was a CSGO Gambling site named CSGOBoss. Coded by an old friend of mine Dahquan Hinds (https://github.com/dahquan/) Thought I would release this to help out any one who would need it.\n\n\t0\t0\t0\njamienp1/CSGODOUBLE-BOT-AUTO\n\ni got a bot thats is betting on the last winning color except from green and if you lose it will double the coins you set it to bet, pretty good, so when there comes a loooong train you will be gaining a bit of money codepaste_net/ugmt92 remove all the _ an…\n\n\t0\t0\t0\nJEYONER/CSGOTOXIC\n\nPAGINA DE JACKPOT CSGO SKINS\n\n\t0\t0\t0\nkalrish/csgo-jackpot\n\nStressful but funny zombie-like Counter-Strike: Global Offensive game mode.\n\n\t0\t0\t0\nkrys12345/roulettee\n\n// ==UserScript== // @name CSGO Predict Bot // @namespace http://csgodouble.com // @version 1.0 // @description predicts what number its gonna be // @author Meee // @match http://www.csgodouble.com/ // @grant none // ==/…\n\n\t0\t0\t0\nLilDuggiMuffi/CSGODouble-Working-Bot\n\nFixed CSGO Double Bot\n\n\t0\t0\t0\nLyricLy/Steam2Proton\n\nCheck if all your Steam games will work with Proton! Uses the official Steam API and the unofficial Proton API.\n\n\t0\t0\t0\nM0NsTeR77/csgo-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nozanhalis/Hi\n\n// ==UserScript== // @name CS GO LOUNGE BOT-Ozan Halis // @namespace http://csgolounge.com/ // @version 0.6.6 // @description Cs Go Lounge Hızlı BOT // @match http://csgolounge.com/* // @match http://dota2lounge.com/* // @updateURL h…\n\n\t0\t0\t0\nscoobertus/CSGO-DoubleBot\n\nNo description in the capture.\n\n\t0\t0\t0\nTradeal/CSGO-Jackpot-Bot\n\nNo description in the capture.\n\n\t0\t0\t0\nValvePython/artifact\n\nNo description in the capture.\n\n\t0\t0\t0\nVampire/CSGO-Roulette-Bot\n\nNo description in the capture.\n\n\t0\t0\t0\nvdemans/csgo-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nVocoreVideo/CSGODungeon-\n\nCSGO Jackpot\n\n\t0\t0\t0\nwayz-dev/csgofloat\n\nNo description in the capture.\n\n\t0\t0\t0\n\nOverzicht: 17 september 2026, 11:19:11 zoals vermeld in de bron; tijdzone niet gespecificeerd. De verzameling van relaties is in de export beperkt (veel categorieën eindigen bij 40). Het totaal aantal bijdragers en forkers bedraagt 4,554 rolvermeldingen verspreid over 4,214 verschillende profiel-repository-paren; een profiel kan beide rollen hebben. Nul betekent dat er geen records in die categorie zijn vastgelegd. Repositorienaam kunnen aliassen of varianten in hoofdletters en kleine letters bevatten; de totalen volgen de telconventies van de bron.\n\nHerkomst van de bron\nSamengesteld uit de bestanden die je hebt verzameld.\nGetuigenis ter ondersteuning\n2323/reddit_scams_ultra/steam_support_tickets_MEGA.json · rijen 45, 58, 107, 110, 294\nNetwerkmomentopname\nnetwork-repositories.csv · raw_data.json · overlaps.csv · summary.txt (historische bronpaden behouden in het manifest)\n\nHet manifest bevat bronpaden, bytegroottes, SHA-256-hashwaarden en geselecteerde recordposities. De ruwe opnames blijven gescheiden van de interpretatie in het kader van het onderzoek.\n\nBronmanifest downloaden ↓",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam Handhavingsbewijs — Ondersteunende documenten & ontwikkelaarsnetwerk"
          },
          {
            "level": 2,
            "id": null,
            "text": "Lees de klacht.Voeg de bron bij."
          },
          {
            "level": 3,
            "id": null,
            "text": "Permanent sanction & closed appeals"
          },
          {
            "level": 4,
            "id": null,
            "text": "Permanently banned Steam account without a clear explanation, need help!"
          },
          {
            "level": 3,
            "id": null,
            "text": "Account recovery & a reported $10,000 loss"
          },
          {
            "level": 4,
            "id": null,
            "text": "Got $10k stollen from steam inventory due to steam' support fault."
          },
          {
            "level": 3,
            "id": null,
            "text": "A reported $500+ loss & template replies"
          },
          {
            "level": 4,
            "id": null,
            "text": "Funds stolen through steam market. Disappointed with Steam response.(or lackthereof)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam Guard & an item-restoration refusal"
          },
          {
            "level": 4,
            "id": null,
            "text": "Many people are losing item via clicking links where steam guard is enabled and steam support doesn't not restore items."
          },
          {
            "level": 3,
            "id": null,
            "text": "Selective enforcement & an unexplained ban"
          },
          {
            "level": 4,
            "id": null,
            "text": "🚨 Steam Bans Without Reason and Ignores Its Community — What’s Going On?"
          },
          {
            "level": 2,
            "id": null,
            "text": "Openbare infrastructuur.Op grote schaal opgenomen."
          },
          {
            "level": 2,
            "id": null,
            "text": "Samengesteld uit de bestanden die je hebt verzameld."
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/nl/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/nl/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/selected-support-records.json",
          "https://phishdestroy.io/steam_dossier/nl/investigation_part2.html#outsourcing-case",
          "https://www.reddit.com/r/ohnePixel/comments/1hahqx2/permanently_banned_steam_account_without_a_clear/",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://www.reddit.com/r/DotA2/comments/r55bd7/many_people_are_losing_item_via_clicking_links/",
          "https://www.reddit.com/r/SteamUncensored/comments/1kjt2fa/steam_bans_without_reason_and_ignores_its/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/network-repositories.csv",
          "https://github.com/alliedmodders/amxmodx",
          "https://github.com/alliedmodders/sourcemod",
          "https://github.com/DoctorMcKay/node-steam-user",
          "https://github.com/Facepunch/Facepunch.Steamworks",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://github.com/odota/core",
          "https://github.com/odota/dotaconstants",
          "https://github.com/odota/web",
          "https://github.com/splewis/get5",
          "https://github.com/SteamDatabase/FileDetectionRuleSets",
          "https://github.com/SteamRE/SteamKit",
          "https://github.com/ValveSoftware/dxvk",
          "https://github.com/ValveSoftware/GameNetworkingSockets",
          "https://github.com/ValveSoftware/gamescope",
          "https://github.com/ValveSoftware/Proton",
          "https://github.com/ValveSoftware/source-sdk-2013",
          "https://github.com/ValveSoftware/wine",
          "https://github.com/ValveSoftware/steam-devices",
          "https://github.com/ValveSoftware/steam-audio",
          "https://github.com/alliedmodders/metamod-source",
          "https://github.com/alliedmodders/sourcepawn",
          "https://github.com/ValveSoftware/Fossilize",
          "https://github.com/rlabrecque/Steamworks.NET",
          "https://github.com/ModDota/moddota.github.io",
          "https://github.com/odota/parser",
          "https://github.com/ValveSoftware/steam-for-linux",
          "https://github.com/SteamRE/DepotDownloader",
          "https://github.com/JustArchiNET/ASF-ui",
          "https://github.com/advancedfx/advancedfx",
          "https://github.com/alliedmodders/ambuild",
          "https://github.com/SteamDatabase/BrowserExtension",
          "https://github.com/odota/mobile",
          "https://github.com/ValvePython/steam",
          "https://github.com/skadistats/clarity",
          "https://github.com/SteamRE/open-steamworks",
          "https://github.com/ValveSoftware/Source-1-Games",
          "https://github.com/alliedmodders/hl2sdk",
          "https://github.com/SteamDatabase/steamdb.info-issues",
          "https://github.com/CSGOFloat/inspect",
          "https://github.com/ValveSoftware/SteamOS",
          "https://github.com/alliedmodders/source2mod",
          "https://github.com/smiley/steamapi",
          "https://github.com/SteamDatabase/GameTracking",
          "https://github.com/ValveSoftware/counter-strike_rules_and_regs",
          "https://github.com/ValveSoftware/openvr",
          "https://github.com/SteamDatabase/easy-markdown-editor",
          "https://github.com/ValveSoftware/Dota-2",
          "https://github.com/ValveSoftware/Dota2-Gameplay",
          "https://github.com/JustArchiNET/ArchiBot",
          "https://github.com/ztizzlegaming/CSGOWinBig",
          "https://github.com/JustArchiNET/mantis.justarchi.net",
          "https://github.com/odota/node-steam-user",
          "https://github.com/ModDota/TypeScriptAddonTemplate",
          "https://github.com/ValvePython/vdf",
          "https://github.com/alliedmodders/amtl",
          "https://github.com/ValvePython/dota2",
          "https://github.com/alliedmodders/stripper-source",
          "https://github.com/Allyans3/steam-market-api-v2",
          "https://github.com/ModDota/dota-tutorial",
          "https://github.com/odota/blog",
          "https://github.com/OpsecGuy/BetterGo",
          "https://github.com/pxvr-official/1",
          "https://github.com/Revadike/InternalSteamWebAPI",
          "https://github.com/JoeSzymkowiczFiveM/qb-lootcrate",
          "https://github.com/AbrarKL/MyRoulette.XYZ",
          "https://github.com/JustArchiNET/ASF-WebConfigGenerator",
          "https://github.com/ModDota/dota-data",
          "https://github.com/ModDota/TypeScriptDeclarations",
          "https://github.com/ModDota/API",
          "https://github.com/alliedmodders/cssdm",
          "https://github.com/SteamDatabase/steamstat.us",
          "https://github.com/c0deina/csgojackpotV2",
          "https://github.com/ValvePython/steamctl",
          "https://github.com/ValvePython/csgo",
          "https://github.com/BeepIsla/csgo-crash-exploit",
          "https://github.com/ValvePython/vpk",
          "https://github.com/alliedmodders/SM-SteamWorks",
          "https://github.com/SteamRE/Steam4NET",
          "https://github.com/alliedmodders/hl2sdk-manifests",
          "https://github.com/JustArchiNET/ASF-PluginTemplate",
          "https://github.com/ModDota/Dota2AIFramework",
          "https://github.com/Shkyyl/KeyChamp",
          "https://github.com/SteamDatabase/SteamMonitor",
          "https://github.com/Baterka/cslore.com",
          "https://github.com/SteamDatabase/SteamTokenDumper",
          "https://github.com/monoblocker/roulette",
          "https://github.com/zsith/launcher.user.js",
          "https://github.com/LincolnIT/CSGODouble-bot-automated",
          "https://github.com/vladpuz/steam-market",
          "https://github.com/mcgrizzz/Cstrike.bet",
          "https://github.com/odota/underlords-web",
          "https://github.com/SteamDatabase/SteamToTwitter",
          "https://github.com/ModDota/AbilityLuaSpellLibrary",
          "https://github.com/alvinl/bitskins",
          "https://github.com/b1naryth1ef/steamy",
          "https://github.com/kratos1812/Case-Opening",
          "https://github.com/odota/docs",
          "https://github.com/SteamDatabase/steam-advanced-access-fetch-players",
          "https://github.com/TheRioMiner/CsgoBetterExternalRaytrace",
          "https://github.com/alliedmodders/hl2sdk-mock",
          "https://github.com/christophersu/PySteamMarket",
          "https://github.com/Extremelyd1/Strat-Roulette",
          "https://github.com/giovanni-orciuolo/double-sdk",
          "https://github.com/JustArchiNET/Madness",
          "https://github.com/ModDota/TypescriptPanoramaDeclarations",
          "https://github.com/odota/rapier",
          "https://github.com/Vozn1akHero/CSGOCaseOpeningSimulator",
          "https://github.com/autarc/steam-store",
          "https://github.com/BETTING-CODE/awesome-esports-sites",
          "https://github.com/jonteohr/Better-Warden",
          "https://github.com/Ludzikk/CSGO-Gambling-Site",
          "https://github.com/ModDota/find-steam-app",
          "https://github.com/mprey/csgocact.us",
          "https://github.com/nezu-cc/ServerCrasher",
          "https://github.com/odota/testfiles",
          "https://github.com/odota/underlordsconstants",
          "https://github.com/SnaBe/node-steam-market-fetcher",
          "https://github.com/SteamDatabase/.github",
          "https://github.com/wolfcon/RIP-HLTV-BET",
          "https://github.com/alliedmodders/blaster.net",
          "https://github.com/catears124/CS2-Price-API",
          "https://github.com/ialakey/caseforge",
          "https://github.com/Ilusion9/csgo-fix-mapchange-crash-sm",
          "https://github.com/ismail0234/Benson-Map-Crash-Fixer",
          "https://github.com/jaxwilko/steam-market-api",
          "https://github.com/JustArchiNET/ArchiTag",
          "https://github.com/ModDota/DotaUI",
          "https://github.com/node-steam/market-pricing",
          "https://github.com/odota/media",
          "https://github.com/SergeyIvanovDevelop/Crypto-Steam-Platform",
          "https://github.com/Aareksio/csgodouble-floatchecker",
          "https://github.com/chinm4/CSGOdrop",
          "https://github.com/Cruze03/CSGO-Case-Opening-Prank",
          "https://github.com/Dhruva-Kapadia/CSGOTrollGG",
          "https://github.com/ErhanCSGO/CSGOPolygon-prediction",
          "https://github.com/Ev-Hoang/Bedrock-Chest-Case-Opening",
          "https://github.com/jmjp/csgo-roulette",
          "https://github.com/JustArchiNET/ArchiCrowdin",
          "https://github.com/LeonSK/WearMarketInspector",
          "https://github.com/maximgeerinck/csgo-gamble",
          "https://github.com/ModDota/BugTracker",
          "https://github.com/plwp/mma-betting",
          "https://github.com/Southsideswag16/Csgo-Gambling-Site",
          "https://github.com/tacyarg/csgofiesta-frontend-react",
          "https://github.com/Velorasse/Mutah-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-csmoney-csgoskins",
          "https://github.com/alliedmodders/am-github-artifact-webhook",
          "https://github.com/charamza/roulette",
          "https://github.com/Cruze03/CSGO-PugSetup-RoundRestore",
          "https://github.com/csgorol/CSGO-ROLL-Crash-Predictor",
          "https://github.com/FoxSerito/FOXWORLD_plugin_DoubleJump_CSGO",
          "https://github.com/hkehayovmoonbiz/CS2-Casino-Full-Source-Code",
          "https://github.com/JustZakary/steamstoreapi",
          "https://github.com/jzimr/steam-market-api",
          "https://github.com/Momohime/CSGO.Network-Jackpot-Coinflip",
          "https://github.com/nnjjswat/moneybot",
          "https://github.com/odota/carry",
          "https://github.com/odota/PublicMatchDataBot",
          "https://github.com/Orillio/CSGOBet.com",
          "https://github.com/ripexz/csgo-bet-alert",
          "https://github.com/rrpvm/lumen_sense-beta-deprecated-",
          "https://github.com/Ruthless222/csgoscore",
          "https://github.com/tfburns/CSGO-cases-PL",
          "https://github.com/TomDra/CSGO-Case-Data-Analysis",
          "https://github.com/ValvePython/dota2-wrappers",
          "https://github.com/ValvePython/teamfortress2-closed-captions",
          "https://github.com/VistaNetGTX/Cstrike.bet-",
          "https://github.com/wafflas/csgo-case-opening-simulator",
          "https://github.com/Admiral-Enigma/Le_Coinflip",
          "https://github.com/adryeljuliao/roulette-csgo",
          "https://github.com/AndreuTheG/csgo-coinflip-web",
          "https://github.com/asmilen/csgoDouble",
          "https://github.com/b1naryth1ef/csgofort",
          "https://github.com/Baterka/PrivateSteamBettingWebsite2024",
          "https://github.com/blackcaer/SteamTradeHandler",
          "https://github.com/BTheCoderr/theRounders",
          "https://github.com/CallumHemsley/KazeBot",
          "https://github.com/chrisjpm/CSGOJackpotTemplate",
          "https://github.com/colinsenner/valve-bug-bounty",
          "https://github.com/coryypeters/nrl-odds-intelligence-pipeline",
          "https://github.com/deissh/dev-csgoduo",
          "https://github.com/dom1torii/even-better-font-manager",
          "https://github.com/DONnicov/CSGO-crash-black-screen-",
          "https://github.com/DoubleBoters/CsgoDouble",
          "https://github.com/downarowiczd/DoubleBot",
          "https://github.com/ErayBahar/steammarketscraper",
          "https://github.com/fairydarkness/SteamwebmailAPI",
          "https://github.com/FAQU2/CSGO-Coinflip-MyJailShop",
          "https://github.com/FlamesONE/csgo-case-opening",
          "https://github.com/FunnyRain/csgorun-crash-watch",
          "https://github.com/geohdgio/Venatus-Autenticator",
          "https://github.com/hakanstarlord/steam-bot",
          "https://github.com/HvH-gg/CSGO-Item-CrashFix",
          "https://github.com/HvH-gg/CSGO-NetMsg-CrashFix",
          "https://github.com/isybycnsmam/SteamLibrary",
          "https://github.com/ItsTangerine/SteamApis.Net",
          "https://github.com/JustArchiNET/JustArchi.net",
          "https://github.com/kiri-osint/CS2-Info-Hub-Bot",
          "https://github.com/Koshkaj/monte",
          "https://github.com/madsab/CaseOpening",
          "https://github.com/man90es/steamcardexchange-api",
          "https://github.com/MattPua/steam-unofficial-docs",
          "https://github.com/Metallist1/Portfolio.CsgoWinGambleProject",
          "https://github.com/mikebobadilla/csgo-jackpot",
          "https://github.com/mikebobadilla/meteor-csgojackpot",
          "https://github.com/ModDota/D2VDump",
          "https://github.com/ModDota/DotaTracking",
          "https://github.com/ModDota/eslint-config",
          "https://github.com/mr-codinglv/Casino-script",
          "https://github.com/MrKeelik/MrKeel",
          "https://github.com/noahlatzel/CSGORollHelper",
          "https://github.com/oddsgpt/oddsgpt-market-intelligence",
          "https://github.com/oEXU/csgo-server-crasher",
          "https://github.com/PrdTTony/CSGO-Roulette",
          "https://github.com/r-adamski/csgo-jackpot",
          "https://github.com/Sahotallo/Turan-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-Skinbaron-hellcase",
          "https://github.com/samuelcsouza/steam-marketplace-api",
          "https://github.com/SKINSTRACK/CS2-Price-API",
          "https://github.com/snmtriet/CSGO-Casino-Full-Source-Code",
          "https://github.com/SteamRE/homebrew-tools",
          "https://github.com/SteamRE/opensteamworks.org",
          "https://github.com/TheQuack45/CsgoCaseOpenProgram",
          "https://github.com/TLClassless/StratRouletteCSGO",
          "https://github.com/tomasoom/csgoCaseOpening",
          "https://github.com/vitaliy-evsyukov/steamgifts-autobet-bookmarklet",
          "https://github.com/XpravdaX/RouletteCSGO",
          "https://github.com/YuiKasumii/steam_api_unofficial",
          "https://github.com/Zexuz/Steam-Betting",
          "https://github.com/ANK-RULZZ/steam-jackpot-site",
          "https://github.com/asmilen/CsgoDoubleVS",
          "https://github.com/CORNOODOSADAS/CSGOWeed",
          "https://github.com/CSGOApple/csgoapple",
          "https://github.com/CSGOFAST/csgofast-api",
          "https://github.com/Donakall/csgoDoublebot",
          "https://github.com/fedor-selivanov/csgo-fast-roulette",
          "https://github.com/foldageros/csgod",
          "https://github.com/gmod-gambling/gmod-gambling",
          "https://github.com/ierome/CSGOBoss-BackEnd",
          "https://github.com/jamienp1/CSGODOUBLE-BOT-AUTO",
          "https://github.com/JEYONER/CSGOTOXIC",
          "https://github.com/kalrish/csgo-jackpot",
          "https://github.com/krys12345/roulettee",
          "https://github.com/LilDuggiMuffi/CSGODouble-Working-Bot",
          "https://github.com/LyricLy/Steam2Proton",
          "https://github.com/M0NsTeR77/csgo-roulette",
          "https://github.com/ozanhalis/Hi",
          "https://github.com/scoobertus/CSGO-DoubleBot",
          "https://github.com/Tradeal/CSGO-Jackpot-Bot",
          "https://github.com/ValvePython/artifact",
          "https://github.com/Vampire/CSGO-Roulette-Bot",
          "https://github.com/vdemans/csgo-roulette",
          "https://github.com/VocoreVideo/CSGODungeon-",
          "https://github.com/wayz-dev/csgofloat",
          "https://phishdestroy.io/steam_dossier/output_steam_network/raw_data.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/enforcement-source-manifest.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/nl/steam_enforcement_evidence.content.json",
      "export_json_sha256": "de35e8e4c508775587f096c86e3de054c195e733140a895fdf55dfc336b230cc"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "nl/steam_evidence_archive.html",
      "language": "nl",
      "title": "Bekijk de bronnen — Het dossier over de ‘Steam’",
      "source_url": "https://phishdestroy.io/steam_dossier/nl/steam_evidence_archive",
      "source_html_sha256": "99f08f0640e11e86a80663d0b9bd6f3910a50f776f3cae76123cc55c7a0dfe5e",
      "exported_at": "2026-09-29T00:18:40.331Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "steam_evidence_archive.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/nl/steam_evidence_archive.pdf?v=print-20260929-v5",
        "sha256": "db3ce8584f77641f32e2516dc8d32ca8bc16e790999a4a674bbf378da6a1d587",
        "bytes": 62396,
        "pages": 4
      },
      "integrity": {
        "signed_object": "steam_evidence_archive.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "steam_evidence_archive.content.json.asc",
        "digest_file": "steam_evidence_archive.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify steam_evidence_archive.content.json.asc steam_evidence_archive.content.json",
          "sha256sum -c steam_evidence_archive.content.json.sha256"
        ]
      },
      "content": {
        "text": "ONDERZOEKSMATERIAAL / BRONVERZAMELING 002\nSteam Bewijsarchief — 16,319 Bronnen\n\nElke claim. Terug naar de bron.\n\nWAT IN DIT HOOFDSTUK WORDT AANGETOOND\n\nDit forensisch archief indexeert 16,319 primaire bronnen – waaronder documentatie van de Valve Developer Community, openbare GitHub-issues, geverifieerde Trustpilot-klachten en gearchiveerde forummeldingen – met cryptografische hashes en herkomstlogboeken. Het biedt een controleerbare bewijsbasis die aantoont dat er herhaalbare kwetsbaarheden in het platform bestaan, dat er ongedocumenteerde API-verouderingen zijn en dat er aanhoudende klachten van consumenten zijn over gekaapte accounts.\n\n← Terug naar het Executive Briefing\n\nZoek het record waarop een melding is gebaseerd. Filter op bron, open de volledige tekst en volg de oorspronkelijke link. Bronvermeldingen kunnen elkaar overlappen; een record is geen geverifieerd incident.\n\nTerug naar het onderzoek ↗\n354TRUSTPILOT / BRONRIJEN\n208REDDIT / BRONRIJEN\n705GITHUB / BRONCODES\n15,302MASTER CSV / BRONRIJEN\n16,319 REKORDEN — UITSPLITSING PER PLATFORMTYPE\n\nWiki-categorie ‘herkomst’ (7,620 records · 46.7%): Verzameld uit de Valve Developer Community (developer.valvesoftware.com), de SteamDB-documentatie/FAQ en wiki’s van gaming-community’s (Liquipedia CS/Dota en Fandom Steam-wiki’s) via geautomatiseerde WARC-snapshots en MediaWiki-API-eindpunten tussen augustus 2024 en september 2026.. Alle 7,620-vermeldingen zijn volledig geïntegreerd in de Master CSV-export (TOTAL_VALVE_SCANDALS_MASTER_DB.csv).\n\nWiki\n7,620\nReddit\n5,635\nGitHub\n2,395\nTrustpilot\n393\nWeb\n276\n9,116 van de records op 16,319 (55.8%) bevatten verwijzingen naar Steam / Valve\n\nDit doorzoekbare archief is opgebouwd op basis van 2026-09-17 uit de hierboven genoemde bron-exporten. De afzonderlijke master-export van de rij ‘40,448-’, die elders in het dossier wordt gebruikt, heeft een andere reikwijdte. Zie de manifest aanmaken voor de tellingen van dit archief; records kunnen elkaar overlappen en hebben geen betrekking op unieke voorvallen.\n\nBRONPLATFORM\nBRONVERZAMELING\nSteam / Valve vermeldingen\nTekstvergelijking of Valve-repositoryOntbrekende / verwijderde tekst\n16,569 bronrijen\n16,319 afzonderlijke records\n249 dubbele rijen zijn samengevoegd\n1 rij uitgesloten\nBekijk de originele bestanden ↘\n★TRUSTPILOT2015-10-16#1RATING 1/5\n\nSteam is the biggest PC gaming platform without a doubt. A power which could be abused but Steam for the most part doesn't. Overall a definite download for any moden digital age PC gamer. It mu... See more\n\nMA · 7 source copies\n★TRUSTPILOT2021-06-18#2RATING 1/5\n\nThey scam people for money, dont believe me? Read this Source: Steam Subscribers/User Agreement NO GUARANTEES TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, NEITHER VALVE NOR ITS AFFILIA... See more\n\nWF · 7 source copies\n★TRUSTPILOT2016-10-28#3RATING 1/5\n\nSupport on site is terrible. Refunds not happend yet, despite games not working. No help at all if key is bought outside their system, so as a customer you can bounce back and through betw... See more\n\nPE · 7 source copies\n★TRUSTPILOT2021-09-27#4RATING 1/5\n\nThey are an amazing company!! My boyfriend paid for and downloaded a game without realizing it wasn’t the version he wanted. When he reached out, they gave him a full refund and responded in the same... See more\n\nVH · 7 source copies\n★TRUSTPILOT2026-07-20#5RATING 1/5\n\nI’ve used Steam for years, but lately, their sales have really lost their edge. I was hoping to score some solid discounts, but many games still feel overpriced, even during sales. Plus, the support response times can be frustratingly slow when issues arise.\n\nCR\n★TRUSTPILOT2025-12-10#6RATING 1/5\n\nI new here , but all my firends had great experience with this platform . They can make money\n\nZeinab Nematollahi\n★TRUSTPILOT2025-11-18#7RATING 1/5TEXT UNAVAILABLE\n\nNo text was included in the source record.\n\nEM\n★TRUSTPILOT2025-10-21#8RATING 1/5\n\nusing steam for over a decade and i have no words how good the platform is. some friends recommended it to me back in 2015 when we wanted to play csgo together and since then im loggin on it on a daily basis to check new games\n\nTrustpilot\n★TRUSTPILOT2025-05-09#9RATING 1/5\n\nSupport are never able to help you and only able to redicrect you to public linkBreaking there own TOSNot able to provider a refundNot able to provide a safe place for gamingBase on the game you play you can get scam.\n\nSym Link · 7 source copies\n★TRUSTPILOT2025-05-09#10RATING 1/5TEXT UNAVAILABLE\n\nNo text was included in the source record.\n\nHearnius\n★TRUSTPILOT2024-12-30#11RATING 1/5\n\nThis company allowed a single phishing scammer 76561199443342045 in 100's of its user community chat rooms \"Steam Chat\" the whole week of Winter Sales, 12-23-2024 - 2025 to spam spaceintrader a scam phishing website.Don't support Valve & Steam that support sca…\n\nFR · 7 source copies\n★TRUSTPILOT2024-11-15#12RATING 1/5\n\nVery realiable! Ive never had an issue over the 11 years ive had steam.\n\nJM\nDe build en de bijbehorende bronbestanden\n\nDit archief voegt dubbele rijen uit 249 samen en sluit één rij uit de invoer van 16,569 uit, waardoor er 16,319 unieke records overblijven. Een record kan een gebeurtenis beschrijven die al in een ander record aan bod komt. De zoekfunctie doorzoekt titels, auteurs, bronvermeldingen en weergegeven fragmenten; bij elk record wordt de volledige opgeslagen tekst geopend.\n\nDownload vier bronbestanden ↓Aantal bestanden en SHA-256-hashwaarden ↗Oorspronkelijk bouwmanifest ↗\n\nDe bundel bevat de herstelde exportbestanden die overeenkomen met het aantal rijen van de build en de drie geregistreerde JSON-paden. Bij de oorspronkelijke build zijn geen hashes van de invoer of een hoofd-CSV-pad vastgelegd; het bijbehorende manifest geeft een overzicht van de herstelde bestanden en de vergelijking met de gepubliceerde index.\n\nTrustpilot · steam_support_reviews.json354 rijen · JSON-export\nReddit · reddit_censored_forensics.json208 rijen · JSON-export\nGitHub · valve_ignored_bugs.json705 rijen · JSON-export; de bestandsnaam is een collectorlabel\nMaster · TOTAL_VALVE_SCANDALS_MASTER_DB.csv15,302 rijen · CSV-export gebruikt voor vergelijking\nRechtbankdossiers · UNSEALED_EXHIBITS_AND_AML_DOSSIER.mdWolfire tegen Valve vrijgegeven e-mails, getuigenverklaringen van Gabe Newell, bekentenis van Oct2019-AML\nBelangrijke feiten · FACTS_AND_CITATIONS_DATABASE.md1,638 afzonderlijke, geverifieerde verwijzingen op het gebied van antitrust- en beveiligingsaspecten van 35\nOndersteuningsarchief · support_canned_refusals.html1,505 ticketgegevens · 137 bewaarde schermafbeeldingen · Live-zoekfunctie\nRecordvelden, ontbrekende tekst en overlappende exporten\n\nDatums, beoordelingen, categorieën en de status van berichten worden overgenomen uit de bronbestanden. Een ontbrekende URL blijft ontbreken. De aanduidingen “[verwijderd]” of “[geschrapt]” geven niet aan wie een bericht heeft verwijderd of waarom. Het filter Steam / Valve is gebaseerd op tekstovereenkomst, niet op een relevantiebeoordeling.\n\nMet ‘Export matches’ worden indexvermeldingen gekoppeld aan fragmenten; ‘Download record’ bevat de volledige opgeslagen tekst. De afzonderlijke 40,448-rij-master CSV en 1,690-rijGitHube CSV Het gaat hier om de totale exportcijfers, niet om het aantal bronnen voor deze versie.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam Bewijsarchief — 16,319 Bronnen"
          },
          {
            "level": 2,
            "id": null,
            "text": "BRONPLATFORM"
          },
          {
            "level": 2,
            "id": null,
            "text": "De build en de bijbehorende bronbestanden"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/nl/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/nl/",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/TOTAL_VALVE_SCANDALS_MASTER_DB.csv",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive_manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive-inputs.zip",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive-inputs-manifest.json",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/unsealed_legal_and_aml/UNSEALED_EXHIBITS_AND_AML_DOSSIER.md",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/forensic_facts_1000/FACTS_AND_CITATIONS_DATABASE.md",
          "https://phishdestroy.io/steam_dossier/nl/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/github_valve_unpatched_bugs.csv"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/nl/steam_evidence_archive.content.json",
      "export_json_sha256": "40146a448f1ebe6ba556e64d11b8e943d333061b00b9d15e217b410874537390"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "nl/support_canned_refusals.html",
      "language": "nl",
      "title": "Steam Archief van afgewezen ondersteuningsverzoeken en standaardantwoorden — Het dossier over de ‘Steam’",
      "source_url": "https://phishdestroy.io/steam_dossier/nl/support_canned_refusals",
      "source_html_sha256": "784810e9ee915dcc0df15049f26ba216526e5f34d427f5384d6993413c9e9c1f",
      "exported_at": "2026-09-29T00:18:41.369Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "support_canned_refusals.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/nl/support_canned_refusals.pdf?v=print-20260929-v5",
        "sha256": "3ed4a5071d866eed08b8d858c628edfb4523dc8f80e227fb608e52582c132774",
        "bytes": 61310,
        "pages": 3
      },
      "integrity": {
        "signed_object": "support_canned_refusals.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "support_canned_refusals.content.json.asc",
        "digest_file": "support_canned_refusals.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify support_canned_refusals.content.json.asc support_canned_refusals.content.json",
          "sha256sum -c support_canned_refusals.content.json.sha256"
        ]
      },
      "content": {
        "text": "WAT IN DIT HOOFDSTUK WORDT AANGETOOND\n\nDeze repository bevat 137 bewaarde originele schermafbeeldingen en 1,505 gecontroleerde klachten van slachtoffers waarin de geautomatiseerde afhandeling van supporttickets door Valve gedetailleerd wordt beschreven. Hieruit blijkt dat wanneer accounts worden gehackt via OpenID-omleiding of ongeautoriseerde API sleutelgeneratie, Steam Support systematisch gebruikmaakt van gestandaardiseerde standaardafwijzingen zonder technisch onderzoek. Door het herstel van items of het vrijgeven van audittrails categorisch te weigeren, schuift het platform de volledige aansprakelijkheid voor structurele authenticatiefouten af op de houders van gehackte accounts.\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\nAlle schermafbeeldingen zijn opnames van derden. Het auteursrecht en de inhoud blijven bij de respectieve auteurs en platforms (Reddit-gebruikers, auteurs van de Steam-community, Trustpilot-recensenten, X en YouTube-gebruikers). Ze worden uitsluitend weergegeven ter identificatie en voor verslaggeving in het algemeen belang; er wordt geen aanspraak gemaakt op eigendom. Elke afbeelding bevat een link naar de oorspronkelijke bron.\n\nFigures reported on the source page\nMeasure\tReported value\tScope\nGedocumenteerde gegevens\t1505\tGeverifieerde beroepen van slachtoffers en discussiethreads over bekeuringen\nGearchiveerde schermafbeeldingen\t137\tLokaal opgeslagen ticketafbeeldingen met hoge resolutie\nHerstelpercentage\t0.0%\tHerzieningen toegekend in de zaak „API” betreffende het kapen van handelstransacties\nSjablonen dupliceren\t100%\tHergebruik van letterlijke transcripties door verschillende medewerkers (Ilya, Roger, Maverick)\nForensisch bewijs: de drie pijlers van de weigering van medewerking\nPILAR 01 · TOELATINGBijlage R-014\nDe bekentenis van Roger: API MitM bevestigd\n\nIn ticketreactie nr.1cp582i geeft „Roger”, een medewerker van de Steam-helpdesk, schriftelijk toe dat aanvallers legitieme transacties via API binnen milliseconden annuleren en vervangen door gekloonde bots, maar hij weigert de items te herstellen en adviseert het slachtoffer om een „lokale pc-technicus” in te schakelen.\n\nBekijk de schriftelijke toelating ↗\nPILAR 02 · ESCALATIEBijlage R-012\n7-Daghandel: afwachten\n\nEen slachtoffer verstrekte de SteamID64 van de accounts van de hacker tijdens de blokkeringsperiode voor daghandel op 7-. De ondersteuningsmedewerkers „Artem“ en „Ilya“ weigerden de gestolen items te blokkeren, onder verwijzing naar de schaarste aan virtuele items, en sloten het ticket af met een automatisch gegenereerd standaardantwoord.\n\nTranscript met meerdere medewerkers bekijken ↗\nPIJLER 03 · BELEIDBijlage R-002\nMarktschariteit versus eigendomsrechten\n\nIn het officiële teruggaafbeleid van Valve staat expliciet vermeld dat items niet worden teruggegeven, omdat het teruggeven ervan „de schaarste zou verminderen en de economie zou opblazen, waardoor de waarde van items op de Community Market zou dalen”.\n\nScreenshot van het beleid bekijken ↗\nHistorische ontstaansgeschiedenis · 22 maart 2018 naar 2026\nBijlage H -003 · 8-Jaar zonder beveiligingsupdates: kwetsbaarheden\nDe vroegst gedocumenteerde vervanging van handelsproducten (22 maart 2018)\n\nPrecies een week voordat Valve zijn controversiële ‘7-’-afkoelingsperiode voor daghandel in Counter-Strike-items instelde, ontdekte de handelsgemeenschap de eerste concrete voorbeelden van de Steam WebAPI-exploit via omleiding van verkeer. Aanvallers hebben websessies gekaapt om een ongeautoriseerde API-sleutel te genereren op steamcommunity.com/dev/apikey zonder dat de mobiele 2FA dit bevestigt, waardoor bots transacties in realtime kunnen annuleren en omwisselen.\n\nWaarschuwing in de voorjaars2018: \"De oplichters kunnen dit ruilaanbod automatisch detecteren en zullen het op jouw account afwijzen, omdat ze jouw Steam API-sleutel hebben. De oplichtingsbot stuurt je nu een ruilaanbod voor dezelfde skins... en je merkt het verschil niet eens!\"\nHistorisch bewijspad\n22 2018: maart Eerste gedocumenteerde API-swap\n2019: Ondersteuning zorgt voor standaardisering van de afweer tegen \"malware\"\n2020: Het script \"Verzoek om hulp afsluiten\" is beveiligd\n2022–2026: Automatisering van phishing via BitB en QR-codes\nOpen de Reddit-thread '2018' (origineel) ↗\nPrimary sources\n\n137 gallery cards refer to 78 distinct primary URLs. Images and repeated exhibit captions are omitted from this reading edition.\n\nFull visual archive and original captures",
        "headings": [
          {
            "level": 2,
            "id": null,
            "text": "Figures reported on the source page"
          },
          {
            "level": 2,
            "id": null,
            "text": "Forensisch bewijs: de drie pijlers van de weigering van medewerking"
          },
          {
            "level": 3,
            "id": null,
            "text": "De bekentenis van Roger: API MitM bevestigd"
          },
          {
            "level": 3,
            "id": null,
            "text": "7-Daghandel: afwachten"
          },
          {
            "level": 3,
            "id": null,
            "text": "Marktschariteit versus eigendomsrechten"
          },
          {
            "level": 3,
            "id": null,
            "text": "De vroegst gedocumenteerde vervanging van handelsproducten (22 maart 2018)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Primary sources"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/nl/#proxy-bypass-explainer",
          "https://www.reddit.com/r/csgo/comments/1cp582i/i_got_api_scammed_what_do_i_do_now/",
          "https://www.reddit.com/r/DotA2/comments/1e5ovy4/my_account_was_hacked_and_steam_support_refuse/",
          "https://www.reddit.com/r/Steam/comments/3b2abd/steam_will_no_longer_restore_scammed_items_item/",
          "https://www.reddit.com/r/GlobalOffensiveTrade/comments/863tk1/psa_urgent_huge_scam_happening_read_here_how_to",
          "https://phishdestroy.io/steam_dossier/nl/support_canned_refusals#gallery-grid"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/nl/support_canned_refusals.content.json",
      "export_json_sha256": "aedd943c0e84ebda11ff3b7d1d624dd0e418a86416e739261e110894e930a8fb"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "nl/valve_scandals_registry.html",
      "language": "nl",
      "title": "Valve Schandalenregister — Het dossier over de ‘Steam’",
      "source_url": "https://phishdestroy.io/steam_dossier/nl/valve_scandals_registry",
      "source_html_sha256": "011fdb00262dd386bc766e0d9ae45d6f0a1db8565a365b6a41c9f25dbc955716",
      "exported_at": "2026-09-29T00:18:42.709Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "valve_scandals_registry.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/nl/valve_scandals_registry.pdf?v=print-20260929-v5",
        "sha256": "f3eb851f903272c994d7215004d37ac1b1d17a5d6adf0a47be1fed0cb5c175fd",
        "bytes": 63927,
        "pages": 6
      },
      "integrity": {
        "signed_object": "valve_scandals_registry.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "valve_scandals_registry.content.json.asc",
        "digest_file": "valve_scandals_registry.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify valve_scandals_registry.content.json.asc valve_scandals_registry.content.json",
          "sha256sum -c valve_scandals_registry.content.json.sha256"
        ]
      },
      "content": {
        "text": "Hoofdarchief schandalen\nValve Scandals Master Registry — 160 Geregistreerde incidenten\nBRONBESTANDEN (RAW): 11,768\n\nGemeld. Bron bekend. Nog in behandeling.\n\nWAT IN DIT HOOFDSTUK WORDT AANGETOOND\n\nDit hoofdregister bundelt 160 onafhankelijk geverifieerde primaire gegevens over hardnekkige platformtekortkomingen, verwijderde meldingen van de community en onopgeloste tekortkomingen in de klantenondersteuning binnen het ecosysteem van Valve. Het omvat geverifieerde geschillenmeldingen op Trustpilot, gearchiveerde GitHub tickets over beveiligingsproblemen en procedures van toezichthouders, en brengt hiermee terugkerende systemische tekortkomingen aan het licht op het gebied van accountherstel en de afhandeling van klantgeschillen.\n\n← Terug naar het Executive Briefing\n\n160 Verzamelde gegevens: een ondersteuningsactie beoordeeld door de mensen die er gebruik van hebben gemaakt, discussiethreads die niet langer zichtbaar zijn, gemelde en onopgeloste platformfouten, en de incidenten waarvoor Valve zich al heeft moeten verantwoorden. Niets hiervan is onze eigen interpretatie — elke rij bevat de oorspronkelijke bron. Open er een en lees het zelf maar.\n\nBronrecords\n11,768\nIn alle categorieën\nTekortkomingen van het platform\n3,372\nDoor de gemeenschap gemelde tekortkomingen in het platform\nGecensureerde discussies\n109\nDoor de moderator verwijderde Reddit-berichten\nKlachten over ondersteuning\n471\nGeverifieerde klachten op Trustpilot\nHaalbaarheid van de handhaving\nBlokkeren van authenticatiehostdomeinen\n\nHet blokkeren van OpenID-authenticatiehosts op domeinniveau is technisch gezien eenvoudig te implementeren: zodra een bron is uitgesloten van Steam-inlogomleiding, kunnen domeinen van derden die als authenticatieproxies voor diezelfde bron fungeren, op basis van dezelfde regelset worden gefilterd. Een uitgebreide bespreking van de haalbaarheid van de implementatie is te vinden in het hoofddossier.\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\nZie de haalbaarheid van de handhaving in het dossier →\nCategorie: Klachten bij Trustpilot Support (gefilterde negatieve escalaties)176 overeenkomende bronrecords · dubbele records zijn samengevouwen\nConsumer Complaint2026-07-20\nAuthor: C***\n\nI’ve used Steam for years, but lately, their sales have really lost their edge. I was hoping to score some solid discounts, but many games still feel overpriced, even during sales. Plus, the support response times can be frustratingly slow when issues arise.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2026-07-20\nConsumer Complaint2025-05-09\nAuthor: S*** L***\n\nSupport are never able to help you and only able to redicrect you to public linkBreaking there own TOSNot able to provider a refundNot able to provide a safe place for gamingBase on the game you play you can get scam.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2025-05-09\nConsumer Complaint2024-12-30\nAuthor: F***\n\nThis company allowed a single phishing scammer 7656…2045 in 100's of its user community chat rooms \"Steam Chat\" the whole week of Winter Sales, 12-23-2024 - 2025 to spam spaceintrader a scam phishing website.Don't support Valve & Steam that support scams. Don't give your log in credentials to account hijacking scammers. This company also allows engagements of commercial advertising / spam for gambling in violation of its own Rules and Guidelines / Online Conduct. 7656…5023 proof - groups/deskinsfans key drop advertising, thanks TannerfromKD and Valve!*\"The Consumer Review Fairness Act (CRFA) protects people’s ability to share their honest opinions about a business’s products, services, or conduct, in any forum, including social media. The law protects a broad variety of honest consumer assessments, including online reviews, social media posts, uploaded photos, videos, etc. And it doesn’t just cover product reviews. It also applies to consumer evaluations of a company\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2024-12-30\nConsumer Complaint2024-07-31\nAuthor: A***\n\nhorrible company.randomly you get \"This account may have been accessed by someone else.\"this happened to me 3 times.the 3rd time they wanted a cd key.a spent useless cd key that nobody has any reason to keep laying around.i gave them the paypal bill for my first purchase back in 2015.i gave them a bill for my first phone number ever on the account.i still got the same email attached to the account.this company is literally a scam. nothing but a scam.they randomly claim you been accessed somewhere else and then require you to give them information no reasonable person would ever have, if not your done and have to rebuy everything.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2024-07-31\nConsumer Complaint2023-12-09\nAuthor: K***\n\nHad 288 euros in steam wallet, someone hacked my account even with two step verification, write a steam support for help but only answer was if something is spent in community market they can’t help.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2023-12-09\nConsumer Complaint2023-09-26\nAuthor: J***\n\nI was banned for saying \"Who let grandma on the PC\"and another for simply calling someone ignorant.Power tripping mods, devs who don't care, steam doesn't care. Yet allows racism/trolling/etc Fk steam, its a joke now.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2023-09-26\nConsumer Complaint2022-08-31\nAuthor: Anonymous\n\nSteam community is plain bad for a various reasons:1. Steam forums are a big mess, for example they allow users to post in any language and as result you get jumbled mess with posts in foreign languages together with English language posts. For example, If you check CS GO forums, you'll see half of posts are in Russian and half in English. I don't understand why such a big and international company would leave their forums so unorganized like that. All other normal companies have English only language allowed which is an international language and sometimes subforums for other languages like German, French and etc... so if French people want to post in French they go specifically in that sub-forum. But no, Steam doesn't care about this. Their forums is a one big mess.2. Moderation is biased and joke. I don't understand why such a big company like Steam can't afford to hire people for moderation and pay them. Instead they just recruit random people for moderation who do it for free and\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2022-08-31\nConsumer Complaint2022-05-28\nAuthor: J***\n\nThe login code never arrives. I hate Steam.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2022-05-28\nConsumer Complaint2021-11-08\nAuthor: N***\n\nThe service is terrible, I only signed up because I really like the game I wanted, but the rest is terrible, I hope to get something better soon.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-11-08\nConsumer Complaint2021-06-18\nAuthor: W***\n\nThey scam people for money, dont believe me? Read thisSource: Steam Subscribers/User Agreement NO GUARANTEESTO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, NEITHER VALVE NOR ITS AFFILIATES GUARANTEE CONTINUOUS, ERROR-FREE, VIRUS-FREE OR SECURE OPERATION AND ACCESS TO STEAM, THE CONTENT AND SERVICES, YOUR ACCOUNT AND/OR YOUR SUBSCRIPTION(S) OR ANY INFORMATION AVAILABLE IN CONNECTION THEREWITH.In short: You got a virus or your data leaked because of our software? Whoopsies we dont care, that isnt even legal or the last of their scammy stuff...\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-06-18\nConsumer Complaint2021-05-14\nAuthor: B***\n\nThe support is one of the worst I've ever seen.Useless support team.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-05-14\nConsumer Complaint2020-04-02\nAuthor: J***\n\nSteamcommunity has 15% fees, 15!!!!\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2020-04-02\nConsumer Complaint2020-03-27\nAuthor: H***\n\nWhat can I say? the support is one of the worst I've ever seen maybe the FUNCOM is much worse. If you tell the true on the steam forum you just got a BAN even if what you said did not violated the rules of the forum.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2020-03-27\nConsumer Complaint2018-03-16\nAuthor: B***\n\ndon't sign up will stick on your computer will kill your pc power you can't remove it from your pc even you deleted it will stay woking in the system\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2018-03-16\nConsumer Complaint2016-12-27\nAuthor: J***\n\nIn bloddy hate their page it's tiresome, it's in no way intuitive. I tried reaching out for support, but that is a maze.I'm simply trying to log in and redeem a key of a product I already bought, their search function is a joke. I f*u*c*k*i*n*g hate them. The layout is not like the how to video from the dealer, this can be done much simpler. I don't frigin care aboutn what other titles you have in store or what genre, I just want to redeem my key and install.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-12-27\nConsumer Complaint2016-10-28\nAuthor: P***\n\nSupport on site is terrible.Refunds not happend yet, despite games not working.No help at all if key is bought outside their system, so as a customer you can bounce back and through between bad support systems?? I wait for some other companies to compete in this market, for this can't be the best we as customers can expect.And do put an email up to find, instead of this stuppid website where you spend so long time trying to find a solution on, instead of a simple mail. Often the problem is not there, or if it's there just saying no help here???I need a response\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-10-28\nConsumer Complaint2016-06-26\nAuthor: V*** W***\n\nUseless support as always!\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-06-26\nConsumer Complaint2014-07-01\nAuthor: J***\n\nexpensive, and support team not willing to cooperate\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2014-07-01\nConsumer Complaint2014-04-15\nAuthor: B***\n\nWhen you pay for a program, you expect it too work. cant not buy or anything and have written to valve. but there is not a being done a damn thing abut it..\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2014-04-15\nConsumer Complaint2026-09-03\nAuthor: M***\n\nWorst platform ever wont give me a refund even though a game is unplayable because of bugs I won't ever be using the crap platform again I hope the platform breaks down for good piece fo crao\n\nTarget Domain: steamcommunity.com / steampowered.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2026-09-03\n\nGeen overeenkomende resultaten\n\nProbeer je actieve zoekopdracht aan te passen of ga naar een ander categorietabblad.\n\n1 / 9",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Valve Scandals Master Registry — 160 Geregistreerde incidenten"
          },
          {
            "level": 2,
            "id": null,
            "text": "Blokkeren van authenticatiehostdomeinen"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: C***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: S*** L***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: F***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: A***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: K***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: Anonymous"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: N***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: W***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: H***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: P***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: V*** W***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: M***"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/nl/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/nl/#proxy-bypass-explainer",
          "https://phishdestroy.io/steam_dossier/nl/#autoban-feasibility-section",
          "https://www.trustpilot.com/review/steamcommunity.com"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/nl/valve_scandals_registry.content.json",
      "export_json_sha256": "12b0d8704266e5e7ef891c529d7728ccc4198c7c287bb3d8c9b711465daa2b14"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "nl/output_steam_network/index.html",
      "language": "nl",
      "title": "Architectuur, geen misbruik: het automatiseringsnetwerk — Het dossier over de ‘Steam’",
      "source_url": "https://phishdestroy.io/steam_dossier/nl/output_steam_network/index",
      "source_html_sha256": "243727999eaf75dc08c80c0ff9d96d1736ba10a6b6d887d409b29e03c50da052",
      "exported_at": "2026-09-29T00:18:43.035Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__index.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/nl/output_steam_network__index.pdf?v=print-20260929-v5",
        "sha256": "22a14a65b522470a1da1c60b3d58e86e77a2a0007b761cfe8cd7ea10fe1a769c",
        "bytes": 66818,
        "pages": 3
      },
      "integrity": {
        "signed_object": "output_steam_network__index.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__index.content.json.asc",
        "digest_file": "output_steam_network__index.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__index.content.json.asc output_steam_network__index.content.json",
          "sha256sum -c output_steam_network__index.content.json.sha256"
        ]
      },
      "content": {
        "text": "Bijlage VII · Analyse van de technische architectuur\nSteam Netwerkarchitectuur — Protocolgetrouwheid en ecosysteemanalyse\n\nAutomatisering vormt de basis van de architectuur vValve. Geen beveiligingslek.\n\nWAT IN DIT HOOFDSTUK WORDT AANGETOOND\n\nDeze module brengt de technische topologie in kaart van 252 ontwikkelaarsrepositories, 3,320 GitHub profielen en 4,214 bijdragersparen die ten grondslag liggen aan het Steam automatiseringsecosysteem. Hieruit blijkt dat automatisering door derden steunt op het officiële Connection Manager-protocol van Valve, Protobuf-schema’s en web-API’s zonder exploitcode. Door algoritmische Steam-bevestigingstokens te ontwikkelen en minimale transactiekosten te heffen tot 66.7%, Valve fungeert het bedrijf als de bewuste architect en de belangrijkste commerciële begunstigde van geautomatiseerde ecosysteemactiviteiten.\n\n← Terug naar het Executive Briefing\n\nWanneer Valve zich richt tot toezichthouders, betalingsverwerkers of slachtoffers van oplichting, schrijft het de diefstal van skins en marktmanipulatie toe aan „ongeautoriseerde exploits door derden” en „malafide, illegale automatisering”. De technische realiteit van dit 252--repositorynetwerk bewijst echter precies het tegenovergestelde: elk automatiseringsframework, elke handelsbot en elke farmingvloot werkt strikt volgens de officiële protocoldefinities, web-API’s en authenticatiemechanismen die zijn ontwikkeld, gedocumenteerd en te gelde gemaakt door Valve Corporation.\n\nForensische bevinding: bewuste architectuur versus onrechtmatige inbreuk\n\nDe software die in deze module wordt geanalyseerd — waaronder SteamKit, node-steam-user, ValvePython/steam, en ArchiSteamFarm — bevat geen enkele softwarekwetsbaarheid, geen enkele geheugenbeschadiging en geen enkele zero-day-exploit. Het zijn zuivere, robuuste open-source-implementaties van het eigen Connection Manager (CM)-clientprotocol vValve, Google Protocol Buffers (Protobufs) en web-API’s. Valve heeft deze API’s ontworpen om programmatische aanmeldingen te ondersteunen, en Steam Guard is ontwikkeld om algoritmische bevestigingstokens toe te staan (identity_secret), en brengt de in de advertentie vermelde vergoeding van 15% in rekening, die oploopt tot tot 66.7% in het voordeel van Valve op de high-velocity-kaarten en de commodity-drops die door geautomatiseerde botnets worden verkocht.\n\nPijler 01 · Protocolgetrouwheid\nOfficiële Protobuf-schema’s\n\nAutomatiseringsbibliotheken omzeilen geen beveiligingscontroles. Ze serialiseren officiële Protobuf-berichten (steammessages_clientserver.proto) via TCP/WebSockets rechtstreeks naar de officiële CM-clusters van Valve, precies zoals de Steam-client dat doet.\n\nPillar 02 · Algorithmic 2FA\nVergunning voor programmatische handel\n\nDe hele miljardenindustrie rond de handel in huid is afhankelijk van Valve’s IEconService API en TOTP-sleutels voor mobiele authenticatie. Valve heeft Steam Guard bewust zo ontworpen dat het bevestigingen van transacties tussen machines mogelijk maakt.\n\nPijler 03 · Commerciële begunstigde\nVerkocht machineverkeer: tot 66.7% minimumvergoeding\n\nValve adverteert met een vergoeding van 15%, maar bij de veelverkochte basisartikelen waarmee geautomatiseerde bots handelen — ruilkaarten, doosjes en goedkope drops met prijzen tussen $0.03 en $0.05 — geldt de minimumvergoeding van twee cent van Valve ($0.01 Steam + $0.01 publisher) 50% aan 66.7% ten gunste van Valve (2¢ wordt afgeschreven van een 3¢-kaart, waardoor de verkoper 1¢ overhoudt). Plus $5.00 per account ($26.8M alleen al voor de gescande vloot).\n\nModule 01 · Bewijsstukken inzake opslagplaatsen en protocollen\nOpenbare infrastructuur voor ontwikkelaars en repositories\n\nGedetailleerde forensische catalogus van open-source-repositories van 252 die ten grondslag liggen aan de automatisering van Steam. Hierin wordt beschreven hoe standaardtools voor softwareontwikkeling de door Valve gepubliceerde API-eindpunten implementeren zonder gebruik te maken van exploits.\n\n252Repositories\n4,554Links naar functies\nBewijsmateriaal uit het bewaarhuis onderzoeken →Module 02 · Demografie van ecosystemen\nKengetallen voor het wereldwijde engineering-ecosysteem\n\nGeografische en institutionele uitsplitsing van software-engineers van 3,320 die bijdragen aan het automatiseringsecosysteem van Steam, inclusief hun banden met grote werkgevers in de technologiesector.\n\n3,320Ingenieurs\n98,902Aansluitparen\nEcosysteemindicatoren bekijken →Module 03 · Interactieve visuele grafiek\nInteractieve grafiek van het protocol en het ontwikkelaarsnetwerk\n\nUitgebreide Vis.js interactieve netwerkgrafieken die repositories, protocolbibliotheken (SteamKit, Steamworks, ASF) en overlappingen tussen bijdragers aan verschillende projecten in kaart brengen. Dit illustreert visueel de legitieme, onderling verbonden open-source softwarearchitectuur die ten grondslag ligt aan het automatiseringsecosysteem van Steam.\n\nInteractiefVis.js Motor\nClusterisolatieLive zoeken\nGeen misbruikStandaard-API's\nInteractieve netwerkgrafiek openen →\nRegelgevend en juridisch kader (artikel over GDPR 25 en consumentenbescherming):\nVolgens het beginsel van „Data Protection by Design and by Default“ is een platformarchitectuur die het stilzwijgend genereren van „API“-sleutels, het zonder kennisgeving annuleren van transacties en het door machines geautomatiseerd liquideren van activa mogelijk maakt, een architecturale keuze van de platformbeheerder. Wanneer Valve vorderingen tot terugbetaling van consumenten systematisch afwijst door te beweren dat de verliezen zijn veroorzaakt door „externe cyberaanvallen“, verzwijgt het dat de aanvalsvector de eigen, opzettelijk ontworpen webAPI-architectuur vValve is.\n\nINTERACTIEVE WEERGAVE\n\nEen volledige interactieve visualisatie van de ‘252-’-repository, 3,320-, is beschikbaar via de netwerkgrafiek voor ontwikkelaars op network.html. De geaggregeerde statistieken staan op de BI-statistieken pagina.\n\nHet dossier ‘Steam’ · Archief technische architectuur · Openbare bronnen · Alle rechten zijn afgestaan aan de mensheid.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam Netwerkarchitectuur — Protocolgetrouwheid en ecosysteemanalyse"
          },
          {
            "level": 3,
            "id": null,
            "text": "Officiële Protobuf-schema’s"
          },
          {
            "level": 3,
            "id": null,
            "text": "Vergunning voor programmatische handel"
          },
          {
            "level": 3,
            "id": null,
            "text": "Verkocht machineverkeer: tot 66.7% minimumvergoeding"
          },
          {
            "level": 2,
            "id": null,
            "text": "Openbare infrastructuur voor ontwikkelaars en repositories"
          },
          {
            "level": 2,
            "id": null,
            "text": "Kengetallen voor het wereldwijde engineering-ecosysteem"
          },
          {
            "level": 2,
            "id": null,
            "text": "Interactieve grafiek van het protocol en het ontwikkelaarsnetwerk"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/nl/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/nl/output_steam_network/valve_ru_farming_isolated.html",
          "https://phishdestroy.io/steam_dossier/nl/output_steam_network/steam_ecosystem_dashboard.html",
          "https://phishdestroy.io/steam_dossier/nl/output_steam_network/network.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/nl/output_steam_network__index.content.json",
      "export_json_sha256": "be922fad19b9bebd7a68a61601e75fbbd90b2d81084db9faa8d5a97f2ae03cf1"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "nl/output_steam_network/network.html",
      "language": "nl",
      "title": "Ontwikkelaar en repository-verkenner — Het dossier over de ‘Steam’",
      "source_url": "https://phishdestroy.io/steam_dossier/nl/output_steam_network/network",
      "source_html_sha256": "32bf719be7c170bc058c74bc7f96332eaaccbf959fa325059007fdc36bf07da8",
      "exported_at": "2026-09-29T00:18:45.414Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__network.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/nl/output_steam_network__network.pdf?v=print-20260929-v5",
        "sha256": "c9db7aa664e2509ed7e0595068681887bfa2e8374ae986a08908f1e86a6516e3",
        "bytes": 36329,
        "pages": 1
      },
      "integrity": {
        "signed_object": "output_steam_network__network.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__network.content.json.asc",
        "digest_file": "output_steam_network__network.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__network.content.json.asc output_steam_network__network.content.json",
          "sha256sum -c output_steam_network__network.content.json.sha256"
        ]
      },
      "content": {
        "text": "Ontwikkelaar en repository-verkenner\n\nZoek een knooppunt. Bekijk de vastgelegde relatie.\n\nOPENBARE REGISTERS / VERZAMELDE VERBINDINGEN\nLive zoeken\nFilterlagen\nTotaal aantal ontwikkelaars3,320\nTotaal aantal repo's252\nWEERGEGEVEN GRAFIEK / DEELVERZAMELING468 KNOOPPUNTEN • 1103 RANDEN\nGeselecteerd profielrecord\n\n💡 Klik op een willekeurig knooppunt in de grafiek of typ iets in het zoekveld om de verzamelde verbindingen en bronpaden ervan te bekijken.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Ontwikkelaar en repository-verkenner"
          }
        ],
        "links": []
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/nl/output_steam_network__network.content.json",
      "export_json_sha256": "71a280f4784517b9ce58287c546c4576e199aab8ebbf3f120341c9d9e695d827"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "nl/output_steam_network/steam_ecosystem_dashboard.html",
      "language": "nl",
      "title": "Het verzamelde netwerk in cijfers — Het dossier over de ‘Steam’",
      "source_url": "https://phishdestroy.io/steam_dossier/nl/output_steam_network/steam_ecosystem_dashboard",
      "source_html_sha256": "8dcdea68a2655f94e6e6637f175ffd57ebe6406f22049cdf0744c5d1120b7e63",
      "exported_at": "2026-09-29T00:18:45.164Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__steam_ecosystem_dashboard.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/nl/output_steam_network__steam_ecosystem_dashboard.pdf?v=print-20260929-v5",
        "sha256": "3ffbf98f8602fac83f66318073e892c6561798ad769fa493a6db63d1ad15d158",
        "bytes": 39101,
        "pages": 2
      },
      "integrity": {
        "signed_object": "output_steam_network__steam_ecosystem_dashboard.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__steam_ecosystem_dashboard.content.json.asc",
        "digest_file": "output_steam_network__steam_ecosystem_dashboard.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__steam_ecosystem_dashboard.content.json.asc output_steam_network__steam_ecosystem_dashboard.content.json",
          "sha256sum -c output_steam_network__steam_ecosystem_dashboard.content.json.sha256"
        ]
      },
      "content": {
        "text": "STATISTIEKEN OVERZICHT // BESTAND02\nSteam Ecosysteemdashboard — Het netwerk in cijfers\n\nHet netwerk in cijfers.\n\nWAT IN DIT HOOFDSTUK WORDT AANGETOOND\n\nDit dashboard bundelt structurele informatie over 3,320 ontwikkelaars en 252 repositories, en brengt 68 gokspecifieke codebases en platformoverschrijdende verbindingsbruggen in kaart. De empirische gegevens brengen geografische clustering en overlappingen tussen ontwikkelaars aan het licht, waaruit blijkt dat de gokinfrastructuur van derde partijen functioneert als een georganiseerde, sterk onderling verbonden software-industrie die is geïntegreerd met het platform van Steam.\n\n← Terug naar het Executive Briefing\n\nGeconsolideerde statistieken van de onderzoeksdatabase: geografische spreiding, toonaangevende bedrijven, opslagplaatsen voor gok-skins en actieve verbindingsbruggen.\n\nScanned Devs3320\nTotaal aantal repo's252\nVerslagen over kansspelen68\nTotaal aantal verbindingen1,426\nStructuur en sectoren van de automatisering\nSector I — Kern van de Valve-onderneming\n\nOfficiële repositories en systeemsoftware. Bevestigde ontwikkelomgeving van de medewerkers Nephyrin en Joe Ludwig van Valve.\n\nSector II — Autorisatiemodules en protocol-emulators (SteamKit)\n\nNetwerkbibliotheken die via reverse engineering zijn ontwikkeld, in samenwerking met Nephyrin van Valve en DoctorMcKay, ontwikkelaar van gokspellen.\n\nSector III — Klanten voor het minen van cryptovaluta (ArchiSteamFarm)\n\nGebruik SteamKit-protocolemulators om op de achtergrond miljoenen nepclients (in ruststand) te laten draaien om ruilkaarten te verzamelen.\n\nGeografie van ontwikkelaars\nDuitsland57\nVerenigde Staten52\nCanada48\nVerenigd Koninkrijk44\nPolen30\nFrankrijk28\nRussische Federatie27\nChina27\nVS (staat Washington)23\nAustralië19",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam Ecosysteemdashboard — Het netwerk in cijfers"
          },
          {
            "level": 3,
            "id": null,
            "text": "Sector I — Kern van de Valve-onderneming"
          },
          {
            "level": 3,
            "id": null,
            "text": "Sector II — Autorisatiemodules en protocol-emulators (SteamKit)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Sector III — Klanten voor het minen van cryptovaluta (ArchiSteamFarm)"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/nl/#briefing-heading"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/nl/output_steam_network__steam_ecosystem_dashboard.content.json",
      "export_json_sha256": "a504feb25b376e53a73b255dd60e2fd8f2f6db9cde8df15d8ae729eb57555dbe"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "nl/output_steam_network/valve_ru_farming_isolated.html",
      "language": "nl",
      "title": "Code, bijdragers en forks — Het dossier over de ‘Steam’",
      "source_url": "https://phishdestroy.io/steam_dossier/nl/output_steam_network/valve_ru_farming_isolated",
      "source_html_sha256": "02ae1222d6289b86df89140695c20cc4341429f891db3bbd3baf504b35dc6250",
      "exported_at": "2026-09-29T00:18:45.162Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__valve_ru_farming_isolated.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/nl/output_steam_network__valve_ru_farming_isolated.pdf?v=print-20260929-v5",
        "sha256": "8fb807fa22355e26822ff40d07168f236ee865dd7f052a62a722037e63cadcf9",
        "bytes": 41087,
        "pages": 2
      },
      "integrity": {
        "signed_object": "output_steam_network__valve_ru_farming_isolated.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__valve_ru_farming_isolated.content.json.asc",
        "digest_file": "output_steam_network__valve_ru_farming_isolated.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__valve_ru_farming_isolated.content.json.asc output_steam_network__valve_ru_farming_isolated.content.json",
          "sha256sum -c output_steam_network__valve_ru_farming_isolated.content.json.sha256"
        ]
      },
      "content": {
        "text": "DEEL II / VOLG DE GEDOCUMENTEERDE RELATIE\n\nForks, bijdragen en softwareafhankelijkheden vormen duidelijk bewijs. Deze visie houdt rekening met de vastgestelde rollen; wat betreft dienstverbanden, het omzeilen van beveiligingsmaatregelen en betrokkenheid bij criminele activiteiten zijn aanvullende bronnen nodig.\n\nOpen de interactieve capaciteitenkaart ↗\nOPENBARE BRONNEN / FUNCTIECONTROLE\nDe code. De bijdragers. De forks.\n1. Nephyrin: forks en bijdragen\n\nVolgens de meegeleverde snapshot wordt Nephyrin vermeld als medewerker bij ValveSoftware/Proton en als forker van SteamRE/SteamKit en SteamRE/open-steamworks. In zijn profielgegevens staat Valve Software vermeld. Deze velden moeten afzonderlijk worden geïnterpreteerd.\n\nEen fork legt een kopie van de repository vast. Bij deze export wordt geen commit toegevoegd waarin wijzigingen aan de SteamKit-authenticatiecode worden vastgelegd.\nVerwijzingen naar de repository / de geschiedenis bekijken\nSteamRE/SteamKit ↗ SteamRE/open-steamworks ↗\n2. Openbare functies: automatisering zonder desktopclient\n\nSteamKit en node-steam-user bieden programmatische koppelingen met Steam. ArchiSteamFarm beschrijft het verzamelen van kaarten via meerdere accounts en vermeldt SteamKit2 als afhankelijkheid.\n\nDit zijn concrete automatiseringsmogelijkheden. Het feit dat de uitvoering ‘headless’ plaatsvindt, betekent niet dat er sprake is van uitsluitend commercieel gebruik of dat de ‘Steam Guard’ wordt omzeild. De relevante vragen zijn: welke inloggegevens worden opgevraagd, welke acties zijn daarmee mogelijk en welke controles worden door het platform toegepast.\n\nBron: README-bestanden van projecten en ArchiSteamFarm.csproj. De capaciteitenkaart bevat koppelingen naar alle gedocumenteerde afhankelijkheden.\n3. JoeLudwig: het label voor bijdragers aan de hl2sdk\n\nIn het overzicht wordt JoeLudwig vermeld als medewerker aan alliedmodders/hl2sdk, ValveSoftware/openvr en ValveSoftware/source-sdk-2013.. Dat is een waarneembare projectrelatie. De export levert geen bewijs dat een bepaalde SDK-wijziging in verband brengt met diefstal of het inzetten van de software voor gokdoeleinden.\n\nVerwijzingen naar de repository / de geschiedenis bekijken\nalliedmodders/hl2sdk ↗ DoctorMcKay/node-steam-user ↗\nLOGISCH SCHEMA // SPOREN\nStroomschema van de verbindingslogica:\nPROFIEL RELATIE\nNephyrin / verzamelde profielgegevens\nBijdrager: Proton. Forkers: SteamKit en open-steamworks.\n▼ Verzamelde vorkrelaties\nGEMEENSCHAPSBIBLIOTHEEK\nSteamRE/SteamKit\nOpenbare netwerkbibliotheek op Steam, beheerd door de SteamRE-organisatie.\n▼ Aangegeven SteamKit2-afhankelijkheid\nGEDOCUMENTEERDE AUTOMATISERING\nJustArchiNET/ArchiSteamFarm\nEr wordt melding gemaakt van het verzamelen van kaarten via meerdere accounts en een afhankelijkheid van SteamKit2.\nBEWIJSMATERIAALBEOORDELING / BRONOVERZICHT\nOPGENOMEN: aparte labels voor bijdragers en forkers.\nAANGETOOND: openbare bibliotheken ondersteunen programmatische interacties op het gebied van ‘Steam’.\nOPEN VRAAG: voor het vaststellen van het auteurschap van specifieke code, de goedkeuring door het platform en het toeschrijven van misbruik is afzonderlijk bewijs vereist.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "De code. De bijdragers. De forks."
          },
          {
            "level": 2,
            "id": null,
            "text": "1. Nephyrin: forks en bijdragen"
          },
          {
            "level": 2,
            "id": null,
            "text": "2. Openbare functies: automatisering zonder desktopclient"
          },
          {
            "level": 2,
            "id": null,
            "text": "3. JoeLudwig: het label voor bijdragers aan de hl2sdk"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/nl/investigation_part2.html#automation-map",
          "https://github.com/SteamRE/SteamKit",
          "https://github.com/SteamRE/open-steamworks",
          "https://github.com/alliedmodders/hl2sdk",
          "https://github.com/DoctorMcKay/node-steam-user"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/nl/output_steam_network__valve_ru_farming_isolated.content.json",
      "export_json_sha256": "63ee0ff348232d654e04621e589eef618e5340f26f62f49bb592becaf57323d0"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "pl/card_economy.html",
      "language": "pl",
      "title": "Gospodarka kartowa — Dossier Steam",
      "source_url": "https://phishdestroy.io/steam_dossier/pl/card_economy",
      "source_html_sha256": "464d4d2919c1a0e318f1358ec45b9091508152a782bf1d8fefee28a134214497",
      "exported_at": "2026-09-29T00:18:49.162Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "card_economy.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/pl/card_economy.pdf?v=print-20260929-v5",
        "sha256": "d3a390f16f73aa76105371d67fda58548ec8df79276d160264365d5fbfe336d1",
        "bytes": 266620,
        "pages": 25
      },
      "integrity": {
        "signed_object": "card_economy.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "card_economy.content.json.asc",
        "digest_file": "card_economy.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify card_economy.content.json.asc card_economy.content.json",
          "sha256sum -c card_economy.content.json.sha256"
        ]
      },
      "content": {
        "text": "ZAŁĄCZNIK V — GOSPODARKA OPARTA NA KARTACH\nFarma botów to nie wyciek w sklepie Valve. To jest klient.\n\nKonto typu Steam nie może otrzymać ani jednej karty kolekcjonerskiej, dopóki nie dokona wydatków $5.00 w sklepie. Nie może ona „farmować” gry, której nie posiada, ani tej, którą otrzymała za darmo. Zanim więc automatyczny system do „farmowania” kart cokolwiek wygeneruje, musi najpierw wykupić sobie dostęp — dla każdego konta, po cenie podanej przez Valve. Następnie klauzula automatyzacji Valve określa, linijka po linijce, co dokładnie wytwarza ten system; jego licencja zabrania wszelkich sposobów, dzięki którym zebrana karta zamienia się w pieniądze; a jego rynek pobiera prowizję, gdy karta i tak trafia do sprzedaży — reklamowana jest po cenie 15%, ale minimalna prowizja wynosi dwa centy od sprzedaży, co w przypadku karty wycenianej w centach stanowi większość ceny. Niniejszy materiał ilustruje, jak duża jest ta transakcja, ile kosztuje w zestawach najwyższy poziom profilu oraz w jaki sposób dział egzekwowania przepisów Valve stosuje tę samą klauzulę, gdy konto należy do zwykłego handlowca.\n\nCo gospodarstwo rolne musi kupić w pierwszej kolejnościIle kosztuje dany poziom w zestawachObie strony biurkaKto reguluje rynek kart\n$5.00Wpłać środki na konto, zanim będzie można otrzymać jakąkolwiek kartę — strona pomocy technicznej serwisu Valve\n13,876Gry na Steam, w których wydawane są karty kolekcjonerskie i występuje 99,971 różnych rodzajów kart\n694,673Kompletne zestawy kart, które obecnie znajdują się w zasobach 91 notowanych na giełdzie botów handlowych\n1,389,346Limity na wydawanie kart kontowych i kart do gier, które zapasy już wykorzystały – co najmniej\n$9.99Mediana ceny gry karcianej — gotowy zestaw tej gry kosztuje średnio $0.74\n97,114Członkowie grupy zajmującej się wymianą kart, w której na liście moderatorów figuruje pracownik o oznaczeniu Valve — § 08\n01 — Proces\nCzym właściwie jest gospodarstwo rolne – krok po kroku\n\nOpisano wyłącznie na podstawie dokumentacji samego narzędzia oraz stron pomocy użytkownika Valve. Żadna z informacji zawartych w tej sekcji nie jest wynikiem domysłów, a żadna z nich nie jest kwestionowana przez żadną ze stron.\n\nKrok 1\nKup\n\nKonto nie może być ograniczony. Strona pomocy Valve uniemożliwia użytkownikom z ograniczonymi kontami „Uczestnictwo w rynku Steam”, z „Wymiana Steam przedmiotów społecznościowych (kart kolekcjonerskich, pakietów rozszerzeń, klejnotów itp.)” oraz z „Zdobycie Steam poziomów profilu (zablokowane na poziomie 0) oraz kart kolekcjonerskich”. Brama to pieniądze: „W sklepie Steam trzeba wydać co najmniej $5.00 USD”.\n\nKrok 2\nKup gry\n\nKarty można zdobyć wyłącznie w grach, które posiadasz. „Aby kwalifikować się do otrzymywania kart z tej gry, musisz być jej właścicielem na swoim koncie Steam. Korzystanie z funkcji udostępniania rodzinnego nie oznacza posiadania gry i nie jest brane pod uwagę”. Zamknięte są również trasy bezpłatne: „W płatnych grach, które otrzymałeś za darmo w ramach promocji, nie można zdobywać kart poprzez powtarzanie rozgrywek”., oraz „Nie da się zdobyć kart w grach typu F2P bez wydania w nich jakichkolwiek pieniędzy”.\n\nKrok 3\nBezczynność\n\nNarzędzie loguje konto do sieci Steam w trybie bezinterfejsowym, „analizuje Twoje odznaki”, tworzy listę tytułów, które można uprawiać, i uruchamia „granie w kwalifikującą się grę i okresowe sprawdzanie, czy gra została już w pełni „wyeksploatowana””. Opis mechanizmu przedstawiony przez jego opiekuna: polega to na tym, że „nie robi nic innego, jak tylko informuje Steam, że gramy w daną grę”.\n\nKrok 4\nKrople się kończą\n\nKażdy tytuł ma charakter skończony. „W każdej grze jest ustalona liczba kart do zdobycia. Gdy zdobędziesz je wszystkie (około połowy pełnego zestawu), gra przestaje być opłacalna pod względem farmowania”. Gospodarstwo, które chce nadal prowadzić produkcję, musi nieustannie kupować karty. Podaż kart jest ograniczana przez zakupy — zgodnie z założeniami gry i na korzyść Valve.\n\nKrok 5\nWypłata\n\nKarta opuszcza system przez jedne z trzech wyjść: zostaje sprzedana na rynku społecznościowym, wymieniona lub przetworzona na klejnoty. Każda z tych czynności stanowi transakcję na rynku subskrypcyjnym lub wymianę, a § 3.D zastrzega opłatę: „Valve może pobierać opłatę za transakcje na platformie subskrypcyjnej.” To właśnie ten krok sprawia, że cała sprawa stanowi naruszenie — zob. 05.\n\nŹródła, przeczytane i zacytowane dosłownie w 2026-09-22: Steam Pomoc techniczna — Ograniczone konta użytkowników ↗ · ArchiSteamFarm Często zadawane pytania ↗ · Valve — Steam Najczęściej zadawane pytania dotyczące kart kolekcjonerskich ↗ · Steam Umowa abonamentowa ↗ zarchiwizowano 2026-09-24 ↗. Na tej stronie symbol ArchiSteamFarm jest używany jako jednostka miary, a nie jako oskarżony; w jego dokumentacji wyraźnie stwierdzono, że „ASF nie posiada upoważnienia od Valve”.\n\n02 — Skala\nZanim gospodarstwo zarobi choćby centa, musi już zapłacić Valve\n\nPonieważ konto o ograniczonych uprawnieniach nie może otrzymać karty, każde konto w gospodarstwie musi zostać wykupione z statusu ograniczonego, zanim zacznie cokolwiek produkować. Próg ten jest podany do wiadomości publicznej, a opłata naliczana jest za każde konto.\n\nWielkość gospodarstwa\tSkąd pochodzi ta liczba\tMinimalna kwota wydatków w sklepie uprawniająca do otrzymania karty\n10 kont\tWysokość, którą zaleca ASF — „w oparciu o wewnętrzne wytyczne Valve, a także nasze własne sugestie”\t$50\n100–200 kont\tLimit techniczny w tej samej sekcji FAQ: „Za pomocą jednego adresu IP i jednej instancji ASF można uruchomić od 100 do 200 botów”\t$500 – $1,000\n120 kont\tSprawa nr 3 dotycząca egzekwowania przepisów — trwały zakaz\t$600\n170 kont\tPrzypadek nr 2 opisany poniżej — trwały zakaz dostępu podczas zimowej wyprzedaży w 2017 roku\t$850\n1,000 konta\tSprawa egzekucyjna nr 1 poniżej — zakaz handlu\t$5,000\n5,000 konta niezweryfikowane\tWaga operatorska zgłoszone w ramach niniejszego dochodzenia i niepoddane niezależnej weryfikacji — zobacz uwagę dotyczącą pozyskiwania\t$25,000\n10,000 kont niezweryfikowane\tWaga operatorska zgłoszone w ramach niniejszego dochodzenia i niepoddane niezależnej weryfikacji — zobacz uwagę dotyczącą pozyskiwania zasobów\t$50,000\n\nDwa ostatnie wiersze to jedyne dane na tej stronie, które opierają się na niepotwierdzonym raporcie, a nie na dokumencie — zostały one zaznaczone w tabeli, a wyjaśnienie znajduje się w uwaga dotycząca pozyskiwania zasobów, a żadna inna część tego tekstu nie opiera się na nich. Prawa kolumna dotyczy wyłącznie obliczeń związanych z opublikowanym przez Valve progiem $5.00 USD i niczym więcej. Jest to podłoga, nie jest to szacunkowa kwota kosztów prowadzenia gospodarstwa ani zarobków Valve: nie uwzględnia ona gier, które muszą znajdować się w posiadaniu gracza i nie mogą pochodzić z darmowej promocji, a także nie uwzględnia około 15%, które pobiera Rynek Społecznościowy przy sprzedaży kart. Na tej stronie nie podano żadnych danych dotyczących przychodów.\n\nA Valve samo ustaliło cenę za rozdanie kart. W sekcji „Najczęściej zadawane pytania” dotyczące kart kolekcjonerskich podano współczynnik konwersji modelu free-to-play w dolarach:\n\n„W grach typu free-to-play karty do gry są przyznawane na podstawie zakupów dokonywanych w grze.” Za każde wydane $9 USD (w przybliżeniu) „Od momentu rozpoczęcia beta-wersji gry karcianej Steam otrzymasz jedną kartę”.\n\n— Valve, Steam Najczęściej zadawane pytania dotyczące kart kolekcjonerskich ↗ · zweryfikowano dosłownie 2026-09-22\n\nKarta kolekcjonerska nie jest gratisem, na którym platforma traci pieniądze. Jest to produkt, który Valve sprzedaje po cenie opublikowanej przez Valve — a następnie pobiera opłatę po raz drugi za jej dalszą odsprzedaż. Dlatego rzetelny opis „farmy kart” nie brzmi pasożyt. Jest to nabywca hurtowy.\n\nJak duże jest faktycznie to, co się kupuje\n\nWszystkie dane od tego miejsca aż do końca tej sekcji są mierzone, a nie zgłaszane. Dane dotyczące kart pochodzą z opublikowanego przez Steam Card Exchange cennika odznak; ceny samych gier pochodzą z API sklepu Valve; dane dotyczące zasobów botów pochodzą z publicznego katalogu botów, do którego każdy ma dostęp. Wszystkie trzy źródła zostały odczytane na 2026-09-22, a obliczenia arytmetyczne przedstawiono w całości w sekcja 08.\n\n13,876Gry z rozdawaniem kart\n99,971Różne rodzaje kart\n5 · 6 · 15Liczba kart w zestawie: min., mediana, maks.\n$0.74Mediana ceny gotowego zestawu\n$23,586.57Jeden egzemplarz z każdego zestawu dostępny na rynku\nJak duży jest ten zestaw?\n\n13,876 gier z kart znajdujących się w zestawie. Valve przypisuje około połowy z nich do jednego konta.\n\n0\n1,250\n2,500\n3,750\n5,000\n5\n6\n7\n8\n9\n10\n11\n12\n13\n14\n15\nIle kosztuje licencja\n\nCena katalogowa tych samych gier w sklepie Steam, w dolarach amerykańskich.\n\n0\n1,000\n2,000\n3,000\n4,000\n<$1\n$1-3\n$3-5\n$5-10\n$10-20\n$20-40\n$40+\nCo zwraca gotowy zestaw\n\nCena rynkowa kompletnego zestawu tych samych gier.\n\n0\n1,500\n3,000\n4,500\n6,000\n<$0.50\n$0.50-1\n$1-2\n$2-5\n$5-10\n$10+\n\nWystarczy porównać ze sobą drugi i trzeci wykres, a charakter tej transakcji stanie się widoczny bez konieczności wykonywania obliczeń: gry skupiają się w przedziale kilkudziesięciu dolarów, a zestawy, które z nich wynikają, skupiają się poniżej jednego dolara. Oba wykresy przedstawiają liczbę tych samych gier 13,876, w tej samej jednostce na osi, więc porównanie dotyczy dwóch wartości, a nie dwóch skal.\n\nTo jest strona podaży. Strona popytu to ta część, której Valve nie musi reklamować, ponieważ jest już dostępna publicznie: pojedynczy otwarty katalog botów do wymiany kart zawiera listę W tej chwili w magazynie znajduje się 91 botów posiadających kompletne zestawy 694,673. Bez logowania, bez pobierania danych z platformy handlowej, bez danych prywatnych — liczba akcji jest podana na stronie obok nazwy każdego bota.\n\nNiech ta akcja stanie się jedyną jednostką, która ma tu znaczenie. Zasada Valve: „W większości gier losowana jest liczba kart równa mniej więcej połowie liczby kart w talii danej gry… Będziesz musiał zdobyć drugą połowę zestawu od innych członków społeczności.\" Jedno konto nigdy nie może zakończyć seta poprzez zagranie. Potrzebne są co najmniej dwa konta, z których każde posiada tę grę i wykorzystuje swój limit upuszczeń – jeden na grę. Limit upuszczeń nie odnawia się.\n\n694,673Zestawy w magazynie, 91 botów publicznych\n3,473,365Karty, przy ustalonym minimalnym zestawie 5 kart\n1,389,346Wykorzystane limity dostaw, minimum\n2,602Konta posiadające tylko jedną grę, największa liczba botów\nGdzie znajdują się zestawy oznaczone symbolem 694,673\n\nDwanaście największych spośród 91 notowanych na giełdzie botów kartowych, pod względem liczby kompletnych zestawów w magazynie. Dziesięciu największych posiada łącznie 248,115 zestawów — 35.7% egzemplarza każdego zestawu dostępnego na tablicy.\n\n0\n11,250\n22,500\n33,750\n45,000\nCard Supply #4 (High)\nN!vq's Leveling (High)\nAlice [BOT] LEVEL-UP RARE SETS\nN!vq's Leveling (Low)\nDisco Lite Level Up\nN!vq's Leveling (Mid)\nbaty131store.net | Level Up\nKitten - Supreme\nArashirn | Level Up\nSH (Junior) Level Up\nDuobot.com - Overstock\nlvlupbot.com - godlike\n\nKażdy z tych 1,39 miliona przydziałów należał do konta, które posiadało tę grę, przekroczyło próg $5.00 i nigdy więcej nie będzie mogło wygenerować tych przedmiotów. To jest nie sprzedane zapasy na dziewięćdziesięciu jednym botach. Nie jest to miara rynku; jest to miara tego, co pozostaje po rynku.\n\nOstatnia liczba odnosi się do podziału na kategorie, a nie do liczby użytkowników. Jeden bot wykazuje 14,310 zestawów pochodzących z zaledwie 11 gier, więc co najmniej jedna z tych gier jest reprezentowana przez 1,301 zestawów, co oznacza co najmniej 2,602 różne konta, z których każde zakupiło tę grę. Jest to najmniejsza liczba, na jaką pozwala arytmetyka, i dotyczy ona jednego bota spośród dziewięćdziesięciu jednego.\n\nCo ta podłoga sugeruje, a czego nie sugeruje\n\nBoty te kupują karty zarówno od zwykłych graczy, jak i od farm — opublikowane przez nie stawki zakupu stanowią główny element tego katalogu. Zatem liczba 1,39 mln uprawnień nie odnosi się do liczby rachunków należących do gospodarstw rolnych. Są to przydziały przedmiotów, które można zdobyć tylko raz na konto i tylko raz w grze, a które zostały wykorzystane gdzieś w Steam i trafiły, jako niesprzedane, do zapasów handlowych. Niezależnie od tego, czy konto stojące za każdym z nich należało do farmy, czy też do nastolatka uzupełniającego swoją stronę z odznakami, nie zmienia to faktu, że Valve zebrało: odblokowanie $5.00, licencję na grę oraz prowizję z Marketu przy każdej transakcji — nie 15%, lecz 15% lub dwie minimalne kwoty po jednym centu, w zależności od tego, która z nich jest większa, co w przypadku karty wycenionej w centach stanowi zdecydowanie większą kwotę. Obliczenia znajdują się w poniższa skala opłat. O to właśnie chodzi na tej stronie i nie jest to zarzut wobec rolników: to samo zachowanie, za które Valve pobiera opłatę, jest tym samym zachowaniem, które cytuje dosłownie, gdy na stałe blokuje konto danej osoby za „wykorzystanie w celach komercyjnych”.\n\nLiczba ta stanowi również dolną granicę w innym znaczeniu. Uwzględnia ona wyłącznie akcje, które są wystawione i niesprzedane dzisiaj o botach, które zdecydować się na umieszczenie w katalogu publicznym. Wszystko, co zostało już sprzedane, wszystko, co znajduje się w posiadaniu prywatnym, oraz każdy bot spoza katalogu jest wykluczony.\n\nA przy cenach Valve prowadzenie gospodarstwa rolnego się nie opłaca\n\nOczywistym zarzutem jest to, że farma kupuje tanie gry, aby wytwarzać drogie karty. API sklepu Steam wskazuje jednak na coś innego. Spośród 13,876 gier zawierających karty ustalono ceny dla 13,713; 12,918 to tytuły płatne, których mediana ceny katalogowej wynosi $9.99. Mediana ceny kompletu gotowego wynosi $0.74. Na każdy zestaw potrzebne są dwie licencje. Zatem średni koszt zestawu wynosi mniej więcej $19.98 licencji na gry – wydanych i zwróconych $0.74.\n\nZmierzono na 2026-09-22\tWartość\tCo reguluje\nMediana ceny katalogowej, gra karciana\t$9.99\tTo opłata licencyjna stanowi droższą część transakcji, a nie sama karta\nGry w cenie $4.99 lub niższej\t3,665 (28.4%)\tNawet najtańszy ogon jest droższy niż zestaw, który z niego powstaje\nNajtańsza gra karciana dostępna w sklepie\t$0.99\tDwie licencje, $1.98, na zestaw, który zazwyczaj kosztuje poniżej $1.30\nGry, których zestaw kosztuje więcej niż sama gra\t323 z 12,918 (2.5%)\tArbitraż kartowy w stosunku do cen katalogowych Steam występuje w 1 grze na 40\nGry typu „free-to-play” w spisie\t795\tA Valve wycenia każdą ze swoich ofert na $9 wydatków w grze\n\nTo rozstrzyga kwestię ekonomiczną na korzyść Valve i wbrew powszechnemu przekonaniu. Biorąc pod uwagę ceny, jakie sam Valve stosuje, zdobywanie kart to działalność przynosząca straty, która opłaca się wyłącznie w przypadku licencji nabytych poniżej ceny katalogowej podanej przez Steam — pakiety, ceny regionalne, kluczowa odsprzedaż. Karty to tylko pozostałość. Zakup to samo wydarzenie. A zakup miał miejsce Steam.\n\nCo tak naprawdę stanowi podstawę funkcjonowania gospodarstwa\n\nJeśli połączymy te elementy, gospodarstwo przestaje wyglądać na coś, co Valve toleruje, a zaczyna wyglądać na coś, czego Valve potrzebuje. Każdy wkład dostarczany przez gospodarstwo stanowi wynik, za który Valve składa raport lub wystawia rachunek. Prześledźmy jedno konto bota na zewnątrz:\n\nJedno konto stworzone w celach komercyjnych„klient hurtowy”, a nie przeciek\nSprzedaż gier\n\nKupuje tytuły, z których pozyskuje karty — od gier karcianych z serii „13,876” po tandetne tytuły z serii „$0.50” — ponieważ karty można zdobyć wyłącznie w posiadanych grach.\n\n„Online” i czas na zabawę\n\nSprawia, że gracze przestają grać, aby zrzucić karty, co zasilają dane dotyczące liczby graczy grających jednocześnie i liczby godzin spędzonych w grze, które Valve określa jako zaangażowanie — dokładnie ten wskaźnik, który w § 4.C nazwano „fałszowaniem czasu gry”.\n\nRejestracje\n\nAby otrzymać kartę, należy najpierw przejść przez bramkę $5.00 dla kont z ograniczeniami — rzeczywiste wydatki w sklepie Valve księgi na konto.\n\nŚrodki w portfelu i opłaty\n\nKażda sprzedana karta trafia z powrotem na Rynek, gdzie opłata za kartę o niskiej wartości wynosi do 66.7%, a wpływy pozostają zablokowane w portfelu Steam.\n\nSteam-poziom PR\n\nWystawy odznak i poziomów Valve istnieją wyłącznie dlatego, że stworzono zestawy — a na szczycie tej drabinki znajdują się boty (patrz § 03).\n\nUsuń gospodarstwo, a wszystkie powyższe liczby spadną — gra sprzedała się w mniejszej liczbie egzemplarzy, społeczność „online” była mniejsza, konto nigdy nie zostało zarejestrowane, opłata nigdy nie została pobrana, a poziom nigdy nie został osiągnięty. Dlatego właśnie zasada zakazująca automatyzacji współistnieje z milionami zautomatyzowanych kont: zakaz jest opcją, a aktywność stanowi źródło przychodów.\n\nA sama wypłata pieniędzy to utrata wartości Valve – podwójne opodatkowanie\n\nKarta nie stanowi końca pętli. Mechanika samej karty Valve pozwala na zgniecenie karty w klejnoty, a klejnoty należy wykorzystać do wytworzenia pakiety kart — kolejne trzy karty — które są sprzedawane lub ponownie niszczone. Każdy etap pętli to transakcja rynkowa lub konwersja, a każda z nich podlega opodatkowaniu. Kierunek tej pętli wynika z minimalnej opłaty określonej poniżej i nie wymaga żadnego zewnętrznego modelu: każda karta sprzedana w jej ramach traci co najmniej dwa centy, w przypadku kart, których wartość rynkowa wynosi od trzech do pięciu, więc każde obrócenie korbki przynosi mniej, niż się w to włożyło. Ten cykl niszczy wirtualną wartość i wymusza przeprowadzanie nowych transakcji, z których pobierane są opłaty, aby ją zastąpić. W niniejszym tekście nie podano żadnych danych dotyczących wielkości tej straty — zysk z każdego zestawu zależy od częstotliwości pojawiania się klejnotów i szans na zdobycie kart z boosterów, których niniejsze badanie nie uwzględniło.\n\nKarta kolekcjonerskaprzedmioty z posiadanej gry\n→\nKlejnotykarta zniszczona, opłata pobrana\n→\nDodatkowy zestawkamienie użyte do wytworzenia\n→\n3 nowe kartysprzedane na platformie Market, pobrano opłatę\n↶\n\nPrzedstawiono tu wyłącznie mechanikę, która jest autorstwa Valve — karty zamieniają się w klejnoty, z klejnotów tworzy się pakiety, a pakiety dają karty — każda z nich została opisana w sekcji FAQ dotyczącej kart kolekcjonerskich Steam, a każdy kolejny etap stanowi zdarzenie rynkowe podlegające opodatkowaniu. Źródło mechaniki pętli: Valve, Steam Najczęściej zadawane pytania dotyczące kart kolekcjonerskich ↗.\n\nTo nie jest tylko chwilowa moda. To branża o wieloletnich fundamentach.\n\nPojedynczy zrzut ekranu mógłby być przypadkiem. Dlatego publiczny katalog botów zajmujących się kartami był sprawdzany raz podczas każdej sezonowej wyprzedaży Steam, sięgając wstecz w serwisie Wayback Machine, od 2022 do 2026 roku — sprawdzano asortyment, jaki boty miały w ofercie, oraz te same konta, wyprzedaż po wyprzedaży. Gospodarka nie pojawia się i nie znika; funkcjonuje nieprzerwanie, opierając się na stabilnej grupie operatorów, a jej szczytowy poziom wyniósł ponad trzy miliony kompletnych zestawów w magazynie podczas wyprzedaży zimowej 2023 r. — około jednej trzeciej miliona kluczy do gry TF2 o znacznej wartości przechowywanych w danym momencie w jednym katalogu.\n\nKompletne zestawy kart przechowywane w publicznym katalogu botów, według Steam sprzedaży\n\nJedna migawka serwisu Wayback z witryną steam.supply/CardBots na każdą sezonową wyprzedaż. Najedź kursorem, aby sprawdzić wartość kluczy TF2 według kursu z tej migawki.\n\n0.0M\n0.9M\n1.8M\n2.6M\n3.5M\nA’22\nS’23\nW’23\nS’24\nW’24\nS’25\nS’26\n401Różne konta botów zaobserwowane w ramach sprzedaży\n59Obecność w co najmniej 5 z 7 kanałów sprzedaży — stabilny trzon\n16Uczestniczył we wszystkich siedmiu aukcjach w latach 2022–2026\n3,22 mlnZestawy Peak dostępne w magazynie (zima 2023 r.) ≈ $570k–790k sztuk\nJak wygląda drabinka odznak w dziale sprzedaży, patrząc z góry\n\nPopyt odpowiada podaży. W przestrzeni publicznej Drabinka z odznakami „Letnia wyprzedaż 2024” zarchiwizowano 2026-07-16 ↗, konto numer jeden zdobyło odznakę za sprzedaż 1,740,645 razy — 1,74 mln zestawów po dziesięć kart, 17,4 mln kart połączone w jedną dekorację profilową. Przy cenie rynkowej oferowanej przez sprzedającego ($0.50 za zestaw) wynosi to ~$870,000 wartości karty; przy zakupie w rzeczywisty sposób — klucze z TF2 wymieniane na boty do podnoszenia poziomu w ilości około 7,6 zestawów za klucz — jest to ~229,000 klawisze, około $410,000–$570,000 w ujęciu realnym. Konto numer dwa: 552,000 zestawów, ~$130,000–181,000. Żaden człowiek nie gra o to. Jest to kupowane, a każdy etap zakupu stanowi transakcję, którą rozlicza Valve.\n\nMetoda i ograniczenia: stan zapasów jest sumowany dla wszystkich botów wymienionych w poszczególnych migawkach; liczba Liczba botów na poszczególnych migawkach nie jest porównywalna w ramach poszczególnych wyprzedaży, ponieważ niektóre migawki pokazują tylko polecane boty, a inne – pełny katalog, więc stan zapasów traktuje się jako minimalną liczbę widocznych pozycji, a nie jako pełny spis. Wartości kluczy opierają się na medianie liczby zestawów reklamowanych na klucz w każdym zrzucie oraz kluczu TF2 o wartości $1.79–$2.49. Trwałość jest określana na podstawie identyfikatora SteamID64 we wszystkich zrzutach. Zrzuty z 2021 r. wykorzystywały starszy układ strony i nie zostały uwzględnione. Dane: farm-economy-timeline.json; poziomy odznak z serwisu SteamLadder; ceny ustalone na podstawie serwisu Steam Card Exchange (migawki z serwisu Wayback z okresu sprzedaży, $0.05 za kartę).\n\nTa sama flota jest tam również wtedy, gdy nie trwa żadna wyprzedaż\n\nDwa powyższe zdjęcia nie przedstawiają dwóch populacji. To ta sama flota, sfotografowana w różnych momentach. Katalog, o którym mowa na początku tej sekcji, został odczytany na zwykły dzień, w którym nie trwa żadna sezonowa wyprzedaż — 2026-09-22 — i nawet w stanie spoczynku utrzymywało 91 botów i 694,673 kompletnych zestawów: rzędu 186,000 klawisze TF2, $334,000–$464,000 wartości karty, w stanie bezczynności między sprzedażami. To minimalny poziom, jaki firma utrzymuje, gdy nic się nie dzieje.\n\nI to jest ta sama operacja. Dopasowana na podstawie SteamID64, 87 z tych 91 nieaktywnych botów — 96% — pojawia się również w siedmiu powyższych migawkach ofert sprzedaży, po szesnaście w każdym z nich. Katalog ten nie jest stoiskiem, które otwiera się na czas sprzedaży, a potem się zamyka; jest to stały wykaz handlowy, który ta sama flota powiększyła aż do 3,22 mln zestawów w szczycie sezonu zimowego 2023 r. i nigdy nie spada do zera. Wyprzedaż ma miejsce wtedy, gdy coś się sprzedaje. Trwa ona również przez resztę roku.\n\nKatalog domyślny dla poszczególnych botów\n\nKażdy kwadrat odpowiada jednemu botowi w katalogu na 2026-09-22; jest on podświetlony, jeśli pojawia się również w siedmiu migawkach sprzedaży. Liczba 91 to liczba podana w katalogu tego dnia, a nie wielkość floty — W podglądach sprzedaży pojawia się 401 różnych kont, a katalog pokazuje inną grupę w poszczególnych dniach.\n\nWidziane w poprzednich aukcjach (87) Nowości od ostatniej wersji (4)\n\nOdczyt bazowy bez wyprzedaży wynosi 2026-09-22 z tego samego katalogu publicznego, bez logowania. Wartość spoczynkowa opiera się na własnej, ogłaszanej przez każdego bota częstotliwości zestawów na klucz oraz przedziale kluczy $1.79–$2.49 powyżej. Nakładanie się danych odbywa się na podstawie identyfikatorów SteamID64 w odniesieniu do siedmiu migawek z okresu wyprzedaży. Ponieważ lista produktów polecanych różni się od pełnej listy w zależności od migawki, porównuje się tutaj stan zapasów i tożsamość, a nie liczbę użytkowników. Obliczenia w sekcja 08.\n\n03 — Drabina\nDrugim elementem jest liczba obok Twojego imienia\n\nKarty stanowią surowiec. Gotowy produkt ma poziom Steam, a jego cena jest ustalana w zestawach Valve.\n\n100Steam Poziom\nPoziom docelowy — przeciągnij lub użyj klawiszy strzałek\nCena jednego kompletnego zestawu, USD\n\n$0.20 to najtańszy kompletny zestaw w spisie, $0.74 to mediana, a $1.70 to średnia. Dane te obejmują wyłącznie karty — w żadnym wypadku nie uwzględniają $5.00 odblokowań ani licencji na grę.\n\n55,000Wymagany system XP\n550Zużyte kompletne zestawy\n110Gry, które warto mieć, i samodzielne zdobywanie zasobów\n$407.00Koszt kart przy tej cenie\n1,100Odliczenia z tytułu strat, minimum\n$5,500.00$5.00 odblokowuje się, jeśli żadne konto nie jest używane ponownie\nWykorzystane kompletne zestawy, poziom od 1 do 1,000\n\nJedno wykonanie odznaki = jeden kompletny zestaw = 100 XP. Każdy poziom w ramach dziesięciopoziomowego przedziału kosztuje o 100 XP więcej niż poziom w przedziale poniżej.\n\n0\n12,625\n25,250\n37,875\n50,500\n1\n250\n500\n750\n1000\n667\n550 sets\n\nPoziom nie jest ozdobą, którą Valve pozostawia bez zmian. Jest on powiązany z kontem. Z sekcji FAQ dotyczącej kart kolekcjonerskich Valve, w części poświęconej temu, co daje stworzenie odznaki: „100 XP, co może podnieść twój poziom o Steam. Jeśli Twój poziom Steam wzrośnie, limit liczby osób na liście znajomych zostanie zwiększony o pięć, a być może odblokujesz możliwość dostosowania swojego profilu za pomocą prezentacji.\" A jeśli chodzi o paczki z kartami: „Twój poziom Steam zwiększa częstotliwość otrzymywania paczek z kartami: poziom 10: +20%… poziom 50: wzrost częstotliwości o +100% (tj. częstotliwość podwoiła się)”.\n\nTen poziom reguluje więc dwie rzeczy Valve: liczbę osób, z którymi można się zaprzyjaźnić, oraz tempo, w jakim darmowe karty trafiają do ekwipunku. Ten drugi czynnik ma charakter kumulacyjny — im więcej zestawów zużyłeś, tym szybciej platforma dostarcza ci kolejne materiały. Valve wbudował pętlę reinwestycji w produkt.\n\nKurs wymiany jest stały i podawany do wiadomości. Wykonanie jednej odznaki zużywa jeden komplet i daje 100 XP; „Zestaw do tej samej gry można stworzyć maksymalnie pięć razy”. Koszt zdobycia jednego poziomu XP wzrasta co dziesięć poziomów. Wynika z tego poniższa tabela, a żadna z podanych wartości nie jest przybliżona:\n\nSteam Poziom\tKompletne zestawy, które zużywa\tGry, które musisz mieć, żeby samodzielnie je stworzyć\tPrzy najniższym odnotowanym poziomie ($0.20)\tW zbiorze medianowym ($0.74)\tSkala\n10\t10\t2\t$2.00\t$7.40\t\n50\t150\t30\t$30.00\t$111.00\t\n100\t550\t110\t$110.00\t$407.00\t\n200\t2,100\t420\t$420.00\t$1,554.00\t\n500\t12,750\t2,550\t$2,550.00\t$9,435.00\t\n667\t22,579\t4,516\t$4,515.80\t$16,708.46\t\n\n667 nie jest wartością hipotetyczną. Jest to najwyższy poziom, do którego pojedynczy bot z publicznego katalogu deklaruje, że może doprowadzić klienta, spośród 33,359 zestawów, które posiada w 6,117 grach. Czwarta kolumna przedstawia tę samą skalę cenową w odniesieniu do najtańszego kompletnego zestawu spośród wszystkich uwzględnionych w spisie; piąta – w odniesieniu do mediany. Obie wartości stanowią ceny rynkowe samych kart i całkowicie wykluczają koszt odblokowania $5.00 oraz licencje na gry.\n\nW jaki sposób sprawdzono tę krzywą, skoro Valve jej nie publikuje\n\nValve określa współczynnik odznak („za każde 100 XP zyskujesz dodatkowy poziom Steam”) a następnie zabezpiecza tę pozycję — „(przynajmniej na początku)” — bez publikowania informacji o eskalacji. Wykorzystana powyżej krzywa jest krzywą standardową, w której każdy poziom w bloku dziesięciu kosztuje 100 XP więcej niż blok poniżej niego. Została ona zweryfikowana na podstawie katalogu, a nie oparta na założeniach: dla każdego bota, którego ogłaszana maksymalna liczba jest ograniczona przez jego zapasy, a nie przez limit pięciu przedmiotów rzemieślniczych na grę, poziom obliczony na podstawie tej krzywej dokładnie odpowiada poziomowi podawanemu przez bota — 541 do 541, 494 do 494, 464 do 464. Tam, gdzie limit ma zastosowanie, obliczona wartość jest o kilka poziomów wyższa, co jest zgodne z założeniami limitu, który uwzględnia również liczbę graczy w składzie na dany mecz. Nie przedstawia się żadnych twierdzeń dotyczących krzywej powyżej poziomu 667.\n\nWystarczy zapoznać się z tabelą obok sekcji 02, a struktura działalności stanie się jasna. Aby umieścić jedno konto na poziomie 500, ktoś musi zebrać 12,750 kompletne zestawy. Każdy z tych zestawów wymagał wykorzystania limitów łupów co najmniej dwóch kont, z których każde przekroczyło próg $5.00 i posiadało grę. Jedna liczba ozdobna u góry jednego profilu opiera się na co najmniej 25,500 wydanych limitach upadków znajdujących się pod nią. Valve nie ponosi straty w tej transakcji. Valve jest kontrahentem w każdej części tej transakcji.\n\n04 — Statystyki\nW tym zapisie nie opisuje się rolnictwa w sposób ogólnikowy. Wymienia się je po kolei.\n\n§ 4.C nie jest ogólnym zapisem mającym na celu zwalczanie botów. Wymienione w nim przykłady wskazują kolejno dwie rzeczy, które wytwarza farma kart.\n\n„Nie wolno używać żadnych skryptów, botów, makr ani innych systemów niekontrolowanych przez człowieka („automatyzacja”) do interakcji z treściami i usługami serwisu Steam w jakikolwiek sposób, w tym między innymi:\n\nAutomatyzacja procesu tworzenia konta Steam,\nFałszowanie statystyk rozgrywki (np. zawyżanie liczby zwycięstw lub porażek, punktów doświadczenia, czasu gry),\nZdobywanie nagród lub postępów bez rzeczywistego wkładu użytkownika,\n„Uczestnictwo w systemach oceny (takich jak recenzje środowiskowe lub „overwatch”) za pomocą środków zautomatyzowanych, w tym wywieranie wpływu na wyniki lub zgłaszanie użytkowników poprzez działania oparte na skryptach, a nie na świadomej ocenie”.\n— Steam Umowa abonamentowa § 4.C ↗ zarchiwizowano 2026-09-24 ↗ · zaczerpnięte i zacytowane dosłownie 2026-09-22\n„…czas zabawy”\n\nGodziny przestoju to nie godziny fikcyjne. W sekcji FAQ serwisu ASF udzielono bezpośredniej odpowiedzi na to pytanie — „Dlaczego czas gry w grach zdobytych za pośrednictwem ASF nie wydłuża się?” — z: „Tak, ale nie w czasie rzeczywistym. Steam rejestruje czas gry w ustalonych odstępach czasu i planuje aktualizację na tej podstawie… zazwyczaj aktualizacja następuje co około 30 minut.”\n\nTe godziny są rejestrowane w danych Valve, pojawiają się na stronach sklepu Valve oraz są uwzględniane w statystykach liczby aktywnych graczy, które Valve publikuje samodzielnie Steam Wykresy ↗ zarchiwizowano 2026-09-23 ↗. W tych danych konto nieaktywne nie różni się od konta aktywnego. Wskaźniki zaangażowania podawane przez platformę są obliczane na podstawie populacji, która – zgodnie z własnymi zasadami platformy – obejmuje również konta nieaktywne.\n\n„…bez rzeczywistego wkładu użytkowników”\n\nJest to definicja „idled card drop”, autorstwa Valve. Stanowi ona również definicję poziomu Steam, odznaki, uprawnień do otrzymywania pakietów rozszerzeń oraz punktów doświadczenia profilu, które się z nim wiążą — FAQ ASF potwierdza to narzędzie „zapewnia możliwość otrzymywania dodatkowych pakietów”, ponieważ loguje się w taki sam sposób jak oficjalny klient.\n\nZatem system nagród i czyn zabroniony stanowią jeden mechanizm postrzegany z dwóch stron. Valve zaprojektował system tak, by nagroda wynikała z czasu, a nie z umiejętności, a następnie wprowadził klauzulę zakazującą przyznawania nagród w jakikolwiek inny sposób niż poprzez poświęcenie tego czasu przez daną osobę.\n\n05 — Pułapka związana z wykorzystaniem komercyjnym\nKażde wyjście z karty w ramach programu „farmed” stanowi wyjście zabronione przez licencję — a Valve pobiera opłatę przy wejściu\n\nTo jest właśnie ten aspekt, którego nie da się rozwiązać poprzez „odpowiedzialne” zdobywanie kart. Licencja dotyczy użytku osobistego, niekomercyjnego, a karta staje się warta zdobywania dopiero w momencie, gdy przestaje być przeznaczona do użytku osobistego.\n\n§ 2.A — licencja\n\n„Valve niniejszym udziela, a Ty przyjmujesz, niewyłączną licencję i prawo do korzystania z Treści i Usług w celu użytek osobisty, niekomercyjny (z wyjątkiem przypadków, w których wykorzystanie komercyjne zostało wyraźnie dozwolone w niniejszym dokumencie lub w obowiązujących Warunkach subskrypcji)”.\n\n§ 2.G — ograniczenie\n\n„nie przysługuje ci prawo do: … (iii) wykorzystywać Treści i Usługi lub jakiekolwiek ich części w celach komercyjnych, z wyjątkiem przypadków wyraźnie dozwolonych w innych postanowieniach niniejszej Umowy (w tym w Warunkach subskrypcji lub Zasadach użytkowania)”.\n\n§ 3.D — opłata\n\n\"Valve może pobierać opłatę za transakcje realizowane na platformie Subskrypcyjnej. Wszelkie opłaty zostaną Państwu podane przed sfinalizowaniem transakcji.”\n\nJeśli przeczytasz te trzy zdania razem, pozycja zostanie zamknięta\n\nKarta, którą się zatrzymuje, nie ma żadnej wartości dla farmy. Karta, którą sprzedaje się, wymienia lub przetwarza na klejnoty, została wykorzystana do wytworzenia wartości — a firma Valve w swoim piśmie dotyczącym egzekwowania zasad sama określiła to w następujący sposób: operatorowi 170 botów poinformowano, że konto „był wykorzystywany do nielegalnego gromadzenia kart kolekcjonerskich na Steam, a także do powiązanych z tym działań, nie tylko o charakterze komercyjnym”. W tym przypadku karty trafiły na rynek. Sprzedaż doszła do skutku. Opłata została pobrana. Zakaz wprowadzono dopiero później.\n\nOpłata przy tych drzwiach nie wynosi 15%. W przypadku karty z opcją „farmed” wynosi ona dwie trzecie tej kwoty.\n\n§ 3.D – rezerwy „opłata”. W przypadku kart, które faktycznie produkuje gospodarstwo, opłata ta wcale nie przypomina reklamowanej kwoty ~15%. Rynek Społecznościowy pobiera 5% Steam opłata transakcyjna oraz 10% opłata za grę, przy czym dla każdej z nich obowiązuje minimalna kwota wynosząca $0.01 (Własny dział „Najczęściej zadawane pytania” serwisu Community Market autorstwa Valve). Na karcie wystawionej za jednego centa te podłogi są Cena: nabywca płaci trzy centy, z czego dwa to opłaty. Zaokrąglenie w dół sprawia, że podana kwota 15% staje się faktyczną opłatą, która wzrasta do 66.7% dokładnie tam, gdzie kręci się rynek kart — kilka centów za kartę.\n\nRzeczywista prowizja od sprzedaży na rynku wspólnotowym, w oparciu o cenę wywoławczą sprzedającego\n\n5% Steam + 10% gry, przy czym każda z nich wynosi co najmniej $0.01. Zacieniony pasek wskazuje zakres, w którym faktycznie odbywa się wymiana kart — mniej więcej $0.03–$0.05 za kartę.\n\n0%\n10%\n20%\n30%\n40%\n50%\n60%\n70%\ncards\n$0.01\n$0.10\n$0.20\n$0.30\n$0.40\n$0.50\n66.7%\nSprzedający oczekuje\tSteam 5% (min. $0.01)\tMecz 10% (min $0.01)\tKoszty ponosi kupujący\tOpłata łączna\n$0.01\t$0.01\t$0.01\t$0.03\t66.7%\n$0.03\t$0.01\t$0.01\t$0.05\t40.0%\n$0.05\t$0.01\t$0.01\t$0.07\t28.6%\n$0.08\t$0.01\t$0.01\t$0.10\t20.0%\n$1.00\t$0.05\t$0.10\t$1.15\t13.0%\n\nOpłata za grę w wysokości 10% trafia do aplikacji, która wydała kartę; kwota 5% należy do Valve, a w przypadku tytułów własnych Valve oraz podstawowych przedmiotów z asortymentu cała opłata trafia do Valve. Tak czy inaczej, pieniądze opuszczają konto gracza zajmującego się farmowaniem — sprzedaż karty za trzy centy przynosi jeden cent zysku, a dwa centy trafiają do sprzedawcy. Pomnóż to przez setki tysięcy sprzedaży kart o wartości poniżej pięciu centów, które generuje farmowanie, i „opłata, którą Valve może pobrać” to model biznesowy, a nie przypis. Źródło: Steam Najczęściej zadawane pytania dotyczące rynku społecznościowego — Opłaty ↗ zarchiwizowane 2026-09-21 ↗, odczyt 2026-09-22; krzywa jest arytmetyczną średnią tych dwóch opublikowanych stóp i ich poziomów minimalnych $0.01.\n\nNie ma takiej konfiguracji tego narzędzia, która pozwoliłaby tego uniknąć. Można je obsługiwać samodzielnie, na jednym koncie, zachowując całkowitą powściągliwość — a w chwili, gdy ta osoba sprzeda choćby jedną kartę pozyskaną w ten sposób w zamian za środki z portfela, ten sam zapis zawarty w § 2.G dotyczy jej tak samo, jak dotyczy operatora obsługującego dziesięć tysięcy kart. Valve zastrzegło sobie zatem możliwość powołania się na naruszenie, które mogłoby zastosować wobec praktycznie każdego sprzedawcy kart na własnym rynku, ale odmówiło skorzystania z tego prawa wobec praktycznie wszystkich z nich. Zasada egzekwowana w takim tempie nie jest zasadą. To tylko opcja. Pytanie, jakie stawia ta wystawa, nie dotyczy tego, dlaczego toleruje się osoby zajmujące się „farmowaniem” kart; lecz dlaczego ta sama opcja jest stosowana wobec pojedynczego użytkownika sprzedającego kartę, podczas gdy komercyjna gospodarka oparta na kartach, którą te karty napędzają — serwisy handlowe, boty do zdobywania kolejnych poziomów, sprzedawcy hurtowi — funkcjonuje jawnie, a jedna z jej największych grup jest moderowana przez pracownika o identyfikatorze Valve (§ 08). Naruszenie przepisów jest ścigane w przypadku drobnych posiadaczy, a w przypadku maszyn jest pomijane.\n\n06 — Historia egzekucji\nBez ostrzeżenia, falami, i rozchodzi się wzdłuż numeru telefonu\n\nValve zawarł w samej umowie postanowienie dotyczące uprawnienia do wypowiedzenia bez wypowiedzenia, umieszczając je bezpośrednio po klauzuli dotyczącej automatyzacji.\n\n„Valve może ograniczyć lub zamknąć Twoje konto (konta) lub określoną subskrypcję w przypadku jakiegokolwiek zachowania lub działania, które jest niezgodne z prawem, stanowi oszustwo lub automatyzację lub narusza zasady postępowania w sieci określone w punkcie Steam. Użytkownik przyjmuje do wiadomości, że firma Valve nie ma obowiązku powiadamiania go przed wypowiedzeniem jego subskrypcji i/lub zamknięciem konta.\"\n\n— Steam Umowa abonamentowa § 4.D ↗ zarchiwizowano 2026-09-24 ↗ · zweryfikowano dosłownie 2026-09-22\n\n1,000+ boty · zablokowano możliwość handlu. „Wygląda na to, że to konto służyło do zarządzania siecią kont botów. Wykorzystywanie botów stanowi naruszenie Steam Umowy z abonentem.”\n\nPonad 170 botów · trwale zablokowanych, zimowa wyprzedaż 2017. „To konto było wykorzystywane do nielegalnego gromadzenia kart kolekcjonerskich na Steam, a także do powiązanych z tym działań, nie tylko o charakterze komercyjnym. Konto zostało trwale zablokowane, a dział pomocy technicznej Steam nie może udzielić dalszej pomocy w tej sprawie”.\n\nPonad 120 botów · trwale zablokowanych. „To konto oraz inne konta zostały wykorzystane do przeciążenia naszej infrastruktury sieciowej, co stanowi naruszenie zasad postępowania w sieci określonych w punkcie Steam.”\n\n— Steam Komunikaty pomocy zamieszczone w sekcji ArchiSteamFarm FAQ, w części „Czy komuś za to zablokowano konto?”. Źródło ↗ · zweryfikowano dosłownie 2026-09-22\nPrzypadek 4 — czerwiec 2025 r., VAC zakazy dotyczące wyłączonego z eksploatacji CS2\n\nW systemie śledzenia projektu odnotowano zdarzenie, które miało miejsce później niż trzy wyżej wymienione: konta, które uruchamiały grę „Counter-Strike 2” wyłącznie w trybie bezczynności za pośrednictwem tego narzędzia, otrzymały VAC zakazy — chodzi o środki zapobiegające oszustwom, a nie o środki administracyjne. Opiekun projektu stoi na stanowisku, że bezczynność nie może być przyczyną takiego zdarzenia, ponieważ „nie robi nic innego, jak tylko informuje Steam, że gramy w daną grę”. Przyczyna jest przedmiotem sporów. Nie ma jednak wątpliwości co do tego, że konta zostały zablokowane.\n\n— ArchiSteamFarm dyskusja nr 3440, rozpoczęta 26 czerwca 2025 r. ↗ · przeczytaj 2026-09-22\n\nJak umiera konto główne\n\nW tym samym wątku jeden ze współpracowników projektu opisuje zasadę postępowania: konta mogą zostać zablokowane „według łańcucha”, jeśli korzystają z tego samego numeru telefonu — „Może to być po prostu jeden zakaz VAC, który rozprzestrzenił się na »czyste« konta powiązane z tym zablokowanym”.\n\nSteam Guard wymaga podania numeru telefonu. Farmy są tworzone w oparciu o numer telefonu operatora. Dlatego działania egzekucyjne nie ograniczają się do kont jednorazowych: śledzą wspólny identyfikator aż do konta, na którym przechowywana jest biblioteka, lista znajomych i ekwipunek. Jest to mechanizm opisany przez jednego ze współpracowników projektu, wyjaśniający, w jaki sposób pojedyncze działanie usuwa główne konto operatora wraz z farmą — i właśnie dlatego straty poniesione w wyniku fali egzekwowania przepisów nie są mierzone w liczbie kont $5. (Opisane przez współpracownika projektu w dyskusji ASF na GitHubie nr 3440; nie ma oficjalnego Valve potwierdzenia ani formalnego precedensu w dokumentacji.)\n\nTen sam akapit, napisany w odstępie pięciu lat przez trzech różnych agentów\n\nKlauzula, zgodnie z którą prowadzenie działalności rolniczej stanowi naruszenie — czyli komercyjne wykorzystanie licencji osobistej, niekomercyjnej — nie dotyczy wyłącznie gospodarstw rolnych. Jest to standardowy powód, jaki podaje Steam przy zamykaniu konta z powodu działalności handlowej, a uzasadnienie to ma formę szablonu. Poniżej przedstawiono trzy przykłady opublikowane przez osoby, które je otrzymały w odstępie pięciu lat od trzech różnych, wymienionych z nazwy przedstawicieli.\n\nWiadomość od Steam Support z 29 września o godz. 19:56\n\n„Konto, z którego piszesz, zostało zablokowane z powodu naruszenia warunków Umowy abonamentowej Steam. Na podstawie aktywności handlowej, zgłoszeń użytkowników i innych czynników stwierdzono, że konto to było wykorzystywane do celów komercyjnych.\n\nTo zablokowanie ma charakter stały, a Steam Dział pomocy technicznej nie może udzielić dalszej pomocy w tej sprawie.\n\nPonieważ przekazaliśmy wszystkie posiadane informacje, zamykam to zgłoszenie do pomocy technicznej. Proszę pamiętać, że nie będą Państwo otrzymywać dalszych odpowiedzi dotyczących tej sprawy.\n\nPozdrawiam,\n„Hal”\n\nTo zgłoszenie pomocy zostało zamknięte.\n29 września 2020 r. Opublikowane przez odbiorcę wraz z komentarzem „RIP Trading”. — @gergelyszabo94 ↗\nWiadomość od działu pomocy technicznej Steam z 12 lipca o godz. 22:41\n\n„Konto, z którego piszesz, zostało zablokowane z powodu naruszenia warunków Umowy abonamentowej Steam. Na podstawie aktywności handlowej, zgłoszeń użytkowników i innych czynników stwierdzono, że konto to było wykorzystywane do celów komercyjnych.\n\nTo zablokowanie ma charakter stały i Steam Dział pomocy technicznej nie może udzielić dalszej pomocy w tej sprawie.\n\nPonieważ przekazaliśmy wszystkie posiadane informacje, zamykam to zgłoszenie. Należy pamiętać, że przyszłe zgłoszenia dotyczące zablokowania konta mogą zostać zamknięte bez udzielenia odpowiedzi.\n\nSteam Pomoc techniczna\n„Vido”\n\nTa prośba o pomoc została zamknięta.\n12 lipca 2024 r., interfejs w języku portugalskim. Odbiorcą jest zawodowy gracz CS2: „Skontaktowałem się już z obsługą klienta Steam, ale otrzymuję tylko automatyczne odpowiedzi… Nie mogę grać w FaceIT, a także nie mogę brać udziału w meczach profesjonalnych”. — @prcs25 ↗ zarchiwizowano 2024-07-15 ↗\nCytat pochodzi od odbiorcy, r/steamsupport\n\n„Witaj, konto, z którego piszesz, zostało zablokowane z powodu naruszenia warunków Umowy abonamentowej Steam. Na podstawie aktywności handlowej, zgłoszeń użytkowników i innych czynników ustalono, że konto to było wykorzystywane do celów komercyjnych.\n\nTo zablokowanie ma charakter stały i Steam Dział pomocy technicznej nie może udzielić Ci dalszej pomocy w tej sprawie.\n\nPonieważ przekazaliśmy wszystkie posiadane informacje, zamykam to zgłoszenie do pomocy technicznej. Należy pamiętać, że przyszłe zgłoszenia dotyczące zablokowania konta mogą zostać zamknięte bez udzielenia odpowiedzi.\n\nSteam Pomoc techniczna\n„Sally”\n\nOtrzymano trzy razy, w odpowiedzi na trzy odrębne wnioski.\n29 marca 2025 r. Autor nie odwoływał się od zablokowania konta — jego konto zostało przejęte wraz z adresem e-mail i prosił o przywrócenie dostępu: „Nie pytam o blokadę i nie kwestionuję jej – chcę po prostu uzyskać dostęp do mojego konta na Steamie… Valve udzielają mi dokładnie tej samej odpowiedzi, wklejanej w odpowiedzi na każde zgłoszenie, a następnie zamykają zgłoszenie.” — r/steamsupport ↗, zawarte w korpusie skarg wykorzystanym w niniejszym badaniu\n\nSłowo po słowie, przecinek po przecinku, przez pięćdziesiąt pięć miesięcy, trzech agentów i dwa języki interfejsu. Jedyną zmianą w całej treści jest ostatnie zdanie, w którym zakres czasowy został zawężony z lat 2020–2024 na „nie otrzymasz już żadnych odpowiedzi” do „przyszłe prośby o pomoc… mogą zostać zamknięte bez udzielenia odpowiedzi”. Niezależnie od tego, jaki proces doprowadził do podjęcia tych decyzji, list ten nie stanowi jego zapisu. Jako powody podano „działalność handlową, zgłoszenia społeczności oraz inne czynniki” — kategorię, zgłoszenie nieznanego pochodzenia oraz pozostałe czynniki, których nie wymieniono.\n\nPięć kolejnych przypadków, zebranych w ten sam sposób. Pierwsze trzy należą do tej samej kategorii i mają ten sam wynik; ostatnie dwa dotyczą tego samego stanowiska, ale odnoszą się do innej zasady sformułowanej tymi samymi słowami:\n\nData\tCo zrobiło to konto\tCo się stało\tŹródło\n04.12.2021\tKupowanie i sprzedawanie na Buff — „Nie robiłem nic innego, jak tylko kupowałem i sprzedawałem na Buffie, czyli w ramach handlu P2P”\tBlokada społecznościowa: brak dostępu do rynku, brak możliwości handlu, zablokowanie drogich zapasów\tr/csgomarketforum ↗ zarchiwizowane 2025-03-27 ↗\n06.12.2021\tTransakcje P2P w jedną stronę za pośrednictwem serwisów Buff i Bitskins dotyczące zestawów wyposażenia i wymiany na lepsze\tStała blokada do użytku komercyjnego oraz blokada wspólnotowa: „utknąłem w trybie pseudo-niewidzialności… Mój profil też utknął w trybie prywatnym”\tr/GlobalOffensiveTrade ↗ zarchiwizowano 2021-12-06 ↗\n20 grudnia 2024 r.\tKonto prowadzone od 2017 roku, tysiące godzin; wymiana na platformach społecznościowych w celu zdobycia zestawów tematycznych i ulepszeń\tStała blokada z blokadą wspólnotową, bez uprzedniego ostrzeżenia ani odwołania; wsparcie „twierdzą, że ich decyzja jest ostateczna”, odpowiedzi są generowane automatycznie\tr/csgomarketforum ↗ zarchiwizowano 2025-06-27 ↗\n23 grudnia 2024 r.\tUżytkownik powracający zasila portfel po rocznej przerwie, korzystając z sieci VPN „wyłącznie w celu zapewnienia ogólnego bezpieczeństwa w Internecie”\tTrwały zakaz dostępu do społeczności wraz z nie podano żadnego powodu: „Zakaz ma charakter stały i nie mogą udzielić dalszych informacji, a kolejne zgłoszenia mogą zostać zamknięte bez udzielenia odpowiedzi”. 196 polubień, 340 odpowiedzi\tr/steamsupport ↗\n04.08.2026\tWieloletnie zakupy w Iranie; autor twierdzi, że nigdy nie publikował postów, nigdy nie korzystał z Marketu ani z forów\tDostęp dla społeczności zablokowany do 2038 roku ponad „regiony objęte sankcjami”; zgłoszenie zostało zamknięte przez pracownika o imieniu Azul. Zwrot kosztów dla tego samego konta, z tego samego irańskiego adresu IP, został zatwierdzony rok wcześniej. Biblioteka i pieniądze pozostają w posiadaniu Valve.\tr/pcgaming ↗\n\nOstatni wiersz dotyczy zasady innej niż pozostałe — zgodności z sankcjami, a nie wykorzystania komercyjnego — i został uwzględniony, ponieważ forma odpowiedzi jest identyczna: kategoria, brak dowodów, brak możliwości odwołania, zamknięte zgłoszenie. Rodzi to również pytanie, którego pozostałe przypadki nie poruszają. Jeśli obsługa konta była niezgodna z prawem, to przyjmowanie opłat przez te wszystkie lata również było niezgodne z prawem. Jedno z tych dwóch stanowisk musi być błędne, a tylko jedno z nich wiązało się z kosztami dla klienta.\n\nWszystkie osiem wiadomości zostało odczytanych na 2026-09-22 — wątki z 2021 r. i grudnia 2024 r. za pośrednictwem zrzutów ekranu z serwisu Internet Archive, a pozostałe za pośrednictwem publicznego interfejsu serwisu Reddit, ponieważ serwis Reddit odrzucił bezpośrednie prośby ze strony podmiotu gromadzącego dane. Dwa listy z lat 2020 i 2024 zostały przepisane na podstawie zrzutów ekranu dołączonych do oryginalnych postów, które nadal są dostępne. W ramach niniejszego dochodzenia żadne z tych kont nie jest uznawane za niewinne ani winne czegokolwiek — i właśnie o to chodzi. Ani czytelnik, ani organ regulacyjny nie są w stanie tego wywnioskować z treści listu.\n\nUwaga dotycząca pozyskiwania danych — straty na poziomie operatorów\n\nOperatorzy, z którymi przeprowadzono rozmowy w ramach niniejszego dochodzenia, zgłaszają straty rzędu od pięciu do dziesięciu tysięcy kont każde w ramach pojedynczych akcji kontrolnych, podczas których prowadzono rozliczenia głównych rachunków na terenie gospodarstwa. Wyniki tej ankiety zostały tutaj odnotowane jako dane własne, a nie jako ustalenia. Nie podano wielkości próby, nie ustalono daty zebrania danych ani nie przeprowadzono weryfikacji dla poszczególnych kont, a żadna inna wartość na tej stronie nie zależy od tej wartości; dwa wiersze w sekcji 02, które się na niej opierają, zostały odpowiednio oznaczone.\n\nZostało to wyraźnie zaznaczone, a nie pominięte, z dwóch powodów. Opisany powyżej mechanizm „chain-ban” stanowi udokumentowane wyjaśnienie właśnie tego schematu. Organ regulacyjny może natomiast zażądać od Valve tego jednego zapisu, który rozstrzygnąłby sprawę: ile kont zostało objętych automatyzacją, w ramach których fal oraz ile każde z tych kont wydało w sklepie przed jego zamknięciem. Dopóki taki zapis nie istnieje, liczba ta pozostaje na swoim miejscu — zgłoszona, przypisana i niepotwierdzona.\n\n07 — Asymetria\nObie strony tego samego biurka\n\nPorównaj ten standard dowodowy z tym, który Valve stosuje w odniesieniu do własnych działań wsparcia. Prawa kolumna to rejestr zdarzeń zawarty w niniejszej dokumentacji, zamieszczony wraz z zastrzeżeniami, które się w nim znajdują.\n\nKlient zajmujący się handlem\n\nOsiem udokumentowanych przypadków w latach 2020–2026\n\nPostępowanie\nSprzedaż lub zakup przedmiotów na platformach handlowych stron trzecich; w jednym przypadku nie doszło do żadnego działania — konto zostało skradzione.\nPrzedstawione dowody\nBrak. „Na podstawie obrotów, zgłoszeń społeczności oraz innych czynników”.\nOgłoszenie\nBrak. Valve zastrzegł to w § 4.D: „Valve nie ma obowiązku powiadomienia Państwa przed rozwiązaniem umowy”.\nOdwołanie\n„To zablokowanie ma charakter stały i Steam Dział pomocy technicznej nie może udzielić dalszej pomocy w tej sprawie”.\nBilet\nSprawa zamknięta po pierwszej odpowiedzi. Dalsze prośby „może zostać zamknięta bez udzielenia odpowiedzi”.\nZasięg\nProfil, lista znajomych, czat, Sklep, ekwipunek oraz wszystkie przedmioty zakupione za prawdziwe pieniądze.\nCzas trwania\nStałe.\nZautomatyzowana flota botów, przeznaczona do obsługi dużych wolumenów\n\n694,673 kompletnych zestawów dostępnych w magazynie publicznym w 91 botach\n\nPostępowanie\nJednoczesne uruchamianie zautomatyzowanych skryptów typu „headless” na tysiącach kont w celu dezaktywacji kart, masowego tworzenia odznak oraz wymiany zestawów na skalę przemysłową.\nPrzedstawione dowody\nPublicznie dostępne katalogi botów (steam.supply, SteamLvlUp) oraz grupy publiczne liczące miliony członków.\nOgłoszenie\nZero interwencji. 88.97% nie podlegają żadnym zakazom; 99.8% z pozostałych zakazów ma charakter kosmetyczny.\nOdwołanie\nNie jest to konieczne. Floty działają nieprzerwanie przez cały wieloletni cykl eksploatacji bez żadnych zakłóceń.\nBilet\n—\nZasięg\nNieograniczona wymiana zasobów, zdobywanie poziomów odznak oraz płynność rynku.\nKorzyść dla Valve\n$26.8M+ w postaci minimalnej kwoty wydatków w sklepie ($5.00 punktów dostępu na konto) oraz 15% odliczeń z transakcji na Rynku Społecznościowym.\nPytanie, które się w związku z tym nasuwa, ujmując to wprost\n\nKlient indywidualny, który ręcznie wymienia karty lub przedmioty, naraża się na stały, niepodlegający odwołaniu ban na mocy § 4.C (automatyzacja) lub § 2.G (wykorzystanie komercyjne). Zautomatyzowana flota do farmowania, wykorzystująca boty działające w trybie bez nadzoru na tysiącach kont, działa jawnie, zachowując wskaźnik nienaruszalności na poziomie 88.97%. Valve jest beneficjentem obu.\n\nAsymetria ma charakter ekonomiczny: indywidualni handlowcy czerpią korzyści z platformy, podczas gdy zautomatyzowane floty kartowe wpompowują miliony do systemu kontroli wydatków w sklepie Valve ($5.00 na konto) i napędzają opłaty transakcyjne przy każdej odsprzedaży. Egzekwowanie zasad nie opiera się na spisanych regulaminach, lecz na modelu generowania przychodów.\n\n08 — Zarządzanie\nKto reguluje rynek kart?\n\nPowtarzający się wniosek zawarty w niniejszym dossier — że warstwa podmiotów zewnętrznych wokół Steam jest obsadzana przez osoby z wewnątrz Steam — ma zastosowanie również w gospodarce kartowej i prowadzi do konkretnego wniosku: żadna niezależna osoba nie jest w stanie ocenić, jakie skutki faktycznie przynoszą działania egzekucyjne podmiotu Valve, ponieważ strona zdolna do takiej oceny znajduje się wewnątrz tej warstwy. Wszystkie poniższe fakty zostały zaczerpnięte z publicznej grupy oraz stron profilowych podmiotu Valve na platformie 2026-09-22 i każdy może je odtworzyć w przeglądarce.\n\nPracownik o pseudonimie Valve pełni rolę moderatora największej grupy zajmującej się wymianą kart Valve pracownik\n\nCardTrades ↗ w swoim nagłówku określa się jako „Steam Oficjalna grupa Card Exchange” i zawiera 97,114 członków. Wymienieni moderatorzy — konta sprawujące kontrolę nad tą grupą — to Mickmane, SgtFopper oraz afarnsworth ↗.\n\nTen ostatni profil jest oznaczony w kodzie strony użytkownika Valve jako pracownik Valve — strona zawiera class=\"profile_header_valve_employee\" — podaje swoją lokalizację jako Bellevue, stan Waszyngton, i należy do Valve, Steam oraz Steam Grupa poświęcona kartom kolekcjonerskim grupy. SteamID64 76561197960434622, członek od 12 września 2003 r.\n\nTa uwaga ma charakter strukturalny, a nie osobisty, i jest nie kwestia automatyzacji — moderator grupy poświęconej wymianie kart nie korzysta z bota i nic tutaj nie wskazuje na coś przeciwnego. Chodzi o zapis w sekcja 07. Steam Card Exchange to zewnętrzna usługa związana z kartami komercyjnymi; handel kartami za pośrednictwem usług stron trzecich stanowi dokładnie takie zachowanie, za które Valve trwale blokuje zwykłe konta na mocy „wykorzystywane do celów komercyjnych na podstawie obrotu, doniesień społeczności i innych czynników”. Pracownik o numerze Valve pełni funkcję moderatora w oficjalnej grupie społecznościowej tej platformy, liczącej dziewięćdziesiąt siedem tysięcy osób.\n\nW niniejszym dokumencie nie wysuwa się żadnych zarzutów dotyczących niewłaściwego postępowania wobec żadnej osoby, i nie wyciąga się żadnych wniosków na temat tego, na czym polega ta rola. Asymetria stanowi sedno sprawy: gdy zwykłe konto ma kontakt z usługą kartową lub skinową strony trzeciej, odpowiedzią jest zamknięte zgłoszenie i trwałe zablokowanie bez przedstawienia dowodów; gdy chodzi o tę konkretną usługę, pracownik Valve znajduje się na liście moderatorów, a ustalenia są widoczne na stronie, którą sama Valve publikuje. Pytanie brzmi tak samo, jak w pozostałej części niniejszego dossier: proszę przedstawić pisemne upoważnienie, jeśli takie istnieje — a jeśli nie jest ono potrzebne, proszę to potwierdzić na piśmie, ponieważ ośmiu osobom z sekcji 06 powiedziano coś przeciwnego.\n\nWarstwa listy blokowanych elementów oraz osoba, która nią zarządza Moderator-wolontariuszUsługi stron trzecich\n\nGrupa Steambans.com (archiwum) ↗ (na żywo ↗ zarchiwizowano 2025-12-03 ↗) opisuje swoje pochodzenie w zachowanym opisie grupy: „Oficjalna grupa społecznościowa Steambans.com Steam. SteamBans.com to zupełnie nowa usługa oparta na starej koncepcji. Globalne listy blokowanych użytkowników funkcjonowały od lat w ramach starego programu WONID firmy VALVe. Kiedy nastąpiła zmiana na STEAMID, naturalnym krokiem było dla nas stworzenie serwisu specjalnie dostosowanego do tego nowego systemu. Chcieliśmy jednak pójść o krok dalej. *. Strona archiwalna serwisu Steambans, który zakończył działalność w 2013 roku.” Wśród wymienionych administratorów znajdują się: devicenull oraz killahinstinct_ ↗.\n\nTo konto administratora to nie pracownik typu Valve — nie ma on oznaczenia „pracownik”. Jest to wolontariusz o wyjątkowo wysokim statusie: członek Moderatorzy społeczności (414 członków, określana jako grupa „stworzone przez moderatorów społeczności Steam”), z Koordynatorzy Wikipedii, z Steam Targ społecznościowy, a także Valve grup programowych i grup przedpremierowych, w tym Valve Rurociąg, Steam Wersja beta dla klientów, Wersja beta aplikacji Mobile Auth, Nowa wersja beta Steam dla społeczności, Steam Laboratoria, Steamworks oraz Zgłoś podejrzane adresy URL. SteamID64 76561197960794555.\n\nRównież w obrębie tego kręgu i wyświetlający użytkowników Steambans bezpośrednio na liście członków swojej publicznej grupy: msart ↗ (lista członków grup ↗), SteamID64 76561197977933359, którego profil zawiera następujące słowa: „Prowadzę stronę steamid.uk oraz wiele innych stron związanych ze Steamem i nie tylko”, oraz który zarządza połączoną siecią szesnastu grup — SteamIDcouk (grupa główna „Strona internetowa Sid”), SidAdmins, SidBans, steamideu, Steam3ID, s-id oraz SArchive wśród nich.\n\nWitryna steamid.uk sama podaje tę samą liczbę. W sekcji „Często zadawane pytania” (FAQ) czytamy: „Kto stworzył SteamID? Stroną internetową SteamID, infrastrukturą sieciową oraz systemami bezpieczeństwa zarządza firma 76561197977933359.” Dwie odpowiedzi dalej wyjaśniono, skąd pochodzą te dane: „SteamID wykorzystuje przede wszystkim interfejs API Steam Web do gromadzenia danych”. Na tej samej stronie opisano wiele serwerów dedykowanych u różnych dostawców usług hostingowych, serwery do programowania poza siedzibą firmy, serwery pamięci masowej oraz serwery do wyszukiwania tekstowego, a także oddzielną infrastrukturę do tworzenia kopii zapasowych.\n\nZweryfikowano na podstawie zachowanych zapisów z serwisu Internet Archive: Zrzut ekranu grupy Steambans z dnia 3 grudnia 2025 r. ↗, ten Podsumowanie profilu operatora z dnia 14 września 2024 r. ↗, oraz Zrzut ekranu z sekcji FAQ serwisu steamid.uk z dnia 1 kwietnia 2026 r. ↗, dane pasujące do tych odczytanych bezpośrednio z 2026-09-22.\n\nCo z tego wynika, a czego nie\n\nListy blokowanych użytkowników, identyfikacja SteamID oraz wymiana kart to trzy usługi, które decydują o tym, komu można zaufać, kogo można zidentyfikować oraz jaką wartość ma dany przedmiot. Żadna z tych trzech usług nie jest obsługiwana przez Valve. W każdym z nich osoby obsługujące systemy sterowania pochodziły z obszaru wewnątrz orbity Valve: pracownik oznaczony symbolem Valve na liście moderatorów oficjalnej grupy serwisu kartowego; długoletni Valve moderator społeczności, posiadający dostęp do programu przedpremierowego i zarządzający grupą listy zablokowanych użytkowników; serwis identyfikacji użytkowników prowadzony przez jedną osobę prywatną, należącą do tego samego kręgu. Trzy serwisy, trzy płaszczyzny kontroli, trzy osoby Valve, którym już przyznano uprawnienia.\n\nPrzynależność do grupy nie oznacza zatrudnienia, a żadna z tych uwag nie stanowi oskarżenia. Jest to fakt z dziedziny zarządzania i właśnie to stanowi powód, dla którego typowa linia obrony — to są podmioty zewnętrzne, nie mamy nad nimi kontroli — należy to sprawdzić, a nie po prostu przyjąć za pewnik. Osoby sprawujące kontrolę dobrze znają Valve. Valve może powiedzieć, czego ewentualnie od nich wymagało; nikt z zewnątrz nie jest w stanie tego ustalić.\n\nNikt nie liczy. Takie są wyniki badania.\n\nPrzestrzeń identyfikatorów Steam to ciągły zakres liczb całkowitych. Przeglądanie jej i podawanie informacji o tym, ile kont zostało zablokowanych, ile ma ograniczenia oraz jaka ilość zapasów jest objęta zakazem handlu, nie stanowi programu badawczego — to po prostu pętla i klucz API. Valve sam udostępnia ten klucz pod adresem steamcommunity.com/dev/apikey. A jednak Żadna niezależna organizacja nie publikuje wyników tego spisu ludności. Ani organ regulacyjny, ani dziennikarz, ani naukowiec, ani organizacja konsumencka. Jedyne publiczne dane liczbowe dotyczące zakresu egzekwowania przepisów w Steam to te, o których Valve zdecyduje się wspomnieć.\n\nNie brakuje tej funkcji. Jest ona po prostu wstrzymana. Serwis, który obsługuje i indeksuje przestrzeń identyfikatorów na dużą skalę — steamid.uk — podaje w swoim FAQ, że „wykorzystuje przede wszystkim interfejs API Steam do gromadzenia danych” i obsługuje ją na wielu dedykowanych serwerach, w zewnętrznych magazynach danych, na maszynach do wyszukiwania tekstowego oraz w oddzielnym centrum tworzenia kopii zapasowych. Serwis jest prowadzony przez jedną osobę prywatną. Grupa braci z listy zbanowanych jest współadministrowana przez długoletniego moderatora społeczności Valve, który ma dostęp do przedpremierowych programów Valve. Jedyna strona, która mogłaby opublikować wyniki liczenia, znajduje się w orbicie Valve i nie publikuje ich.\n\nTaki sam schemat odnotowuje się w całym dokumencie. Każda instytucja, która podejmuje decyzje o kluczowym znaczeniu dla gospodarki Steam — kto jest godny zaufania, kogo można zidentyfikować, ile wart jest dany przedmiot, komu zakazano dostępu — jest formalnie podmiotem zewnętrznym, a w praktyce ściśle powiązana z Valve. Steam Wymiana kart nie stanowi wyjątku od tej reguły; jest to kolejny jej przykład. Argument, że są to niezależne operatory, ma zastosowanie w przypadku Valve właśnie dlatego, że nikomu nigdy nie udało się zweryfikować go na podstawie konkretnej liczby.\n\nSpis 10,88 mln kont: 88.97% Nienaruszone\n\nBaza zainstalowanych urządzeń ArchiSteamFarm została poddana audytowi w całej firmie Valve GetPlayerBans punkt końcowy (10,880,610 kont, 55 minut). Sam podzbiór nieograniczony stanowi $26.8M+ w zakresie minimalnej kwoty wydatków w sklepie (próg wejścia $5.00). 9,680,599 konta (88.97%) nie podlegają żadnym ograniczeniom, a 99.8% z pozostałych podlega jedynie symbolicznym zakazom na forach, które nie uniemożliwiają prowadzenia automatycznego handlu.\n\n5,360,499Członkowie ASF bez ograniczeń (liczba wyświetlona jako Steam)\n10,880,610Łączna liczba przeskanowanych wpisów API (z ograniczeniami i bez ograniczeń)\n9,680,599Nigdy nie został zablokowany (88.97%)\n1,200,011Zastosuj dowolny zakaz typu Steam (11.0%) — kosmetyczny 99.8%\n55 minAby przeprowadzić spis całej populacji, kluczowe znaczenie ma\nDowody kryminalistyczne i szczegółowy spis ludności\n\nSzczegółowy podział demograficzny — obejmujący wykresy przedstawiające rodzaje blokad, wiek kont w momencie zastosowania sankcji, grupy według roku utworzenia (2020–2026) oraz dane geograficzne podane przez samych użytkowników — został opublikowany w ramach specjalnego badania spisu użytkowników.\n\nOtwórz pełny spis 10,88 mln zakazów (załącznik VI) →Sekcja 4 — Blokada identyfikatora zasobu →\n\nNależy więc zadać następujące pytanie, na które odpowiedź może udzielić wyłącznie Valve: który identyfikator lub uprawnienie zostało cofnięte, w jakim terminie, na mocy czyjej decyzji oraz jaki wymierny wpływ miało to na operatorów, których dotyczyło — w zestawieniu z jej wpływem na wszystkich na zewnątrz, którzy próbowali przeprowadzić liczenie. Zmiana, która kładzie kres niezależnemu audytowi, nie staje się neutralna tylko dlatego, że ogłoszono ją jako środek bezpieczeństwa. To właśnie dlatego spis ludności w powyższym bloku nie istnieje.\n\n09 — Metoda i ograniczenia\nCo zostało przeczytane, a co nie jest przedmiotem roszczenia\n\nKażdy cytat na tej stronie pochodzi z aktywnego źródła na 2026-09-22 i został przytoczony dosłownie. Żadna z zawartych tu informacji nie pochodzi ze zgromadzonych danych, poświadczeń z platform handlowych ani prywatnych zbiorów danych.\n\nCztery zbiory danych oraz operacje arytmetyczne na nich wykonywane\n\nKażde z nich to pojedyncze żądanie publiczne, które można odtworzyć z terminala. Nie użyto żadnego konta, nie zalogowano się do żadnej platformy handlowej ani nie wywołano żadnego punktu końcowego wymagającego podania danych uwierzytelniających.\n\nZbiór danych\tSkąd to się wzięło\tCo na tej podstawie obliczono\nSpis kart\n13,876 meczów\tSteam Opublikowany przez Card Exchange cennik odznak – ten sam kanał, który wyświetla ich strona z cenami dla klientów indywidualnych ↗ zarchiwizowano 2026-08-04 ↗\tGry, w których wydawane są karty, liczba kart w zestawie, różne rodzaje kart oraz cena rynkowa każdego kompletnego zestawu. Mediany i suma $23,586.57 stanowią podstawę obliczeń w niniejszym badaniu.\nCeny gier\n13,713 rozwiązano\twłasny publiczny punkt końcowy sklepu Valve, store.steampowered.com/api/appdetails, cc=us, wyłącznie pole ceny, partiami\tMediana i rozkład cen katalogowych gier karcianych; liczba gier, których kompletny zestaw sprzedaje się lepiej niż sama gra.\nZapasy botów\n91 botów, 694,673 zestawów\tPubliczny katalog botów karcianych pod adresem steam.supply/CardBots ↗, czytaj tak, jak to jest przedstawione, bez logowania\tŁączna liczba zestawów w magazynie, minimalna liczba kart, dolny limit dopuszczalnych strat oraz dolny limit przypisania na jednego bota dla poszczególnych kont.\nWeryfikacja krzyżowa\n21 udostępnionych botów\tsteamlvlup.net/cardbots ↗ zarchiwizowano 2026-02-10 ↗, niezależny katalog tych samych botów\tWyłącznie do weryfikacji. W przypadku 21 botów wymienionych na obu listach firma Aggregate Stock zgadza się na 0.03%; największa rozbieżność w wynikach pojedynczego bota wynosi 1.36%, co jest zgodne z wynikami dwóch przeszukiwań aktualnego stanu zapasów przeprowadzonych w odstępie kilku minut.\n\nŹródło, zgodnie z wymogami drugiego katalogu: dane dostarczone przez SteamLvlUp, na licencji CC BY 4.0 zarchiwizowano 2026-09-23 ↗; wykorzystano je tutaj wyłącznie w celu niezależnej weryfikacji danych dotyczących zasobów podanych przez stronę trzecią, przy czym dane zostały zmodyfikowane poprzez zagregowanie i porównanie wierszy dotyczących poszczególnych botów zamiast ich odtwarzania. Steam Card Exchange i steam.supply zostały wymienione powyżej wraz z linkami. Ceny gier pochodzą od Valve. Nazwy i zdjęcia kart, gier oraz zestawów należą do Valve lub wydawców i zostały zamieszczone bez żadnych roszczeń ani licencji, jako fakty dotyczące rynku.\n\nNie przeprowadzono dwóch planowanych pomiarów i nie zastąpiono ich innymi. Własne punkty końcowe Steam dotyczące rynku wspólnotowego — przegląd cen, wyszukiwanie/wyświetlanie, historia cen — nie zwracają żadnych danych do serwera pobierającego, a strony dyskusji społeczności Steam zwracają mu kod HTTP 403, więc żadna z wartości na tej stronie nie pochodzi z aktualnych danych z Marketu. Metoda oparta na wolumenie sprzedaży, która zliczałaby pojawienie się kart podczas codziennego resetowania, wymaga zalogowanej sesji Steam; W protokole z tego dochodzenia stwierdzono, że nie wykorzystano żadnych danych uwierzytelniających z platformy handlowej, a oświadczenie to zostało zachowane. Powierzchnia podłogi bez botów to ta, którą można zmierzyć bez nich.\n\nŹródła pierwotne\n\nSteam Umowa abonamentowa ↗ zarchiwizowano 2026-09-24 ↗ — § 2.A, § 2.G, § 3.D, § 4.C, § 4.D.\nSteam Pomoc techniczna — Ograniczone konta użytkowników ↗ — próg $5.00 oraz lista cech objętych ograniczeniami.\nValve — Steam Najczęściej zadawane pytania dotyczące kart kolekcjonerskich ↗ — mechanika zdobywania przedmiotów oraz model $9 „free-to-play”.\nArchiSteamFarm Często zadawane pytania ↗ oraz dyskusja nr 3440 ↗.\nSteam Strony grup społecznościowych i profile – dostępne bezpośrednio w sekcji 08.\nCzęsto zadawane pytania (FAQ) serwisu steamid.uk, zrzut ekranu z serwisu Internet Archive 2026-04-01 ↗.\nOsiem Steam ogłoszeń dotyczących blokady wsparcia opublikowanych przez ich odbiorców w latach 2020–2026, wymienionych wraz z linkami w sekcji 06.\n\nCzego nie obejmuje niniejszy zastrzeżenie\n\nNie oszacowano wysokości przychodów z tytułu „Valve” wynikających z farmowania kart. Nie podano liczby aktywnych kont dla żadnego narzędzia, a limit 1,39 mln dropów wynosi nie liczba kont należących do gospodarstw rolnych — patrz uwaga w sekcji 02. Żadnej osobie nie zarzuca się popełnienia wykroczenia; w przypadku wymienienia nazwiska osoby, podaje się jej publiczny Steam pseudonim, w ramach pełnionej przez nią publicznej funkcji, na stronie publikowanej przez Valve. W odniesieniu do żadnego z ośmiu zablokowanych kont wymienionych w sekcji 06 nie stwierdzono ani niewinności, ani winy; ustalenia dotyczą treści wiadomości, a nie samego konta. Dane dotyczące utraty operatorów w sekcji 02 pochodzą z raportów własnych i są jako takie oznaczone w nota dotycząca zaopatrzenia. Często zadawane pytania (FAQ) serwisu steamid.uk zostały zaczerpnięte z kopii archiwalnej w serwisie Internet Archive, ponieważ strona w wersji online jest chroniona mechanizmem weryfikacji przeciwko botom. Nie twierdzi się, że podjęto próbę sporządzenia spisu zablokowanych użytkowników, a następnie go ukryto — stwierdzono jedynie, że żaden taki spis nie został opublikowany. Krzywa poziomu Steam powyżej wartości 667 nie została uwzględniona w modelu.\n\nDlaczego narzędzie nie jest przedmiotem\n\nArchiSteamFarm stwierdza, że „nie jest autoryzowane przez Valve” i na tej stronie nie wysuwa się pod jego adresem żadnych zarzutów. Jest wykorzystywana jako narzędzie pomiarowe, ponieważ jest jedyną stroną w tej gospodarce, która dokumentuje mechanizmy działania publicznie i na piśmie. Valve może zamknąć całą sprawę w jednym akapicie: opublikować, które rozwiązania automatyki komercyjnej zatwierdza, oraz rejestr działań poszczególnych operatorów dotyczących pozostałych kwestii.\n\nCzytaj dalej: w jaki sposób wyceniany jest sam rynek → · skala cenowa i limit ofert → · produkty oznaczone symbolem Steam nie będą dostarczane →",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Farma botów to nie wyciek w sklepie Valve. To jest klient."
          },
          {
            "level": 2,
            "id": null,
            "text": "Czym właściwie jest gospodarstwo rolne – krok po kroku"
          },
          {
            "level": 3,
            "id": null,
            "text": "Kup"
          },
          {
            "level": 3,
            "id": null,
            "text": "Kup gry"
          },
          {
            "level": 3,
            "id": null,
            "text": "Bezczynność\nNarzędzie loguje konto do sieci Steam w trybie bezinterfejsowym, „analizuje Twoje odznaki”, tworzy listę tytułów, które można uprawiać, i uruchamia „granie w kwalifikującą się grę i okresowe sprawdzanie, czy gra została już w pełni „wyeksploatowana””. Opis mechanizmu przedstawiony przez jego opiekuna: polega to na tym, że „nie robi nic innego, jak tylko informuje Steam, że gramy w daną grę”."
          },
          {
            "level": 3,
            "id": null,
            "text": "Krople się kończą\nKażdy tytuł ma charakter skończony. „W każdej grze jest ustalona liczba kart do zdobycia. Gdy zdobędziesz je wszystkie (około połowy pełnego zestawu), gra przestaje być opłacalna pod względem farmowania”. Gospodarstwo, które chce nadal prowadzić produkcję, musi nieustannie kupować karty. Podaż kart jest ograniczana przez zakupy — zgodnie z założeniami gry i na korzyść Valve."
          },
          {
            "level": 3,
            "id": null,
            "text": "Wypłata\nKarta opuszcza system przez jedne z trzech wyjść: zostaje sprzedana na rynku społecznościowym, wymieniona lub przetworzona na klejnoty. Każda z tych czynności stanowi transakcję na rynku subskrypcyjnym lub wymianę, a § 3.D zastrzega opłatę: „Valve może pobierać opłatę za transakcje na platformie subskrypcyjnej.” To właśnie ten krok sprawia, że cała sprawa stanowi naruszenie — zob. 05."
          },
          {
            "level": 2,
            "id": null,
            "text": "Zanim gospodarstwo zarobi choćby centa, musi już zapłacić Valve"
          },
          {
            "level": 3,
            "id": null,
            "text": "Jak duże jest faktycznie to, co się kupuje"
          },
          {
            "level": 3,
            "id": null,
            "text": "Jak duży jest ten zestaw?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ile kosztuje licencja"
          },
          {
            "level": 3,
            "id": null,
            "text": "Co zwraca gotowy zestaw"
          },
          {
            "level": 3,
            "id": null,
            "text": "Gdzie znajdują się zestawy oznaczone symbolem 694,673"
          },
          {
            "level": 3,
            "id": null,
            "text": "Co ta podłoga sugeruje, a czego nie sugeruje"
          },
          {
            "level": 3,
            "id": null,
            "text": "A przy cenach Valve prowadzenie gospodarstwa rolnego się nie opłaca"
          },
          {
            "level": 3,
            "id": null,
            "text": "Co tak naprawdę stanowi podstawę funkcjonowania gospodarstwa"
          },
          {
            "level": 4,
            "id": null,
            "text": "Sprzedaż gier"
          },
          {
            "level": 4,
            "id": null,
            "text": "„Online” i czas na zabawę"
          },
          {
            "level": 4,
            "id": null,
            "text": "Rejestracje"
          },
          {
            "level": 4,
            "id": null,
            "text": "Środki w portfelu i opłaty"
          },
          {
            "level": 4,
            "id": null,
            "text": "Steam-poziom PR"
          },
          {
            "level": 3,
            "id": null,
            "text": "A sama wypłata pieniędzy to utrata wartości Valve – podwójne opodatkowanie"
          },
          {
            "level": 3,
            "id": null,
            "text": "To nie jest tylko chwilowa moda. To branża o wieloletnich fundamentach."
          },
          {
            "level": 3,
            "id": null,
            "text": "Kompletne zestawy kart przechowywane w publicznym katalogu botów, według Steam sprzedaży"
          },
          {
            "level": 3,
            "id": null,
            "text": "Jak wygląda drabinka odznak w dziale sprzedaży, patrząc z góry"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ta sama flota jest tam również wtedy, gdy nie trwa żadna wyprzedaż"
          },
          {
            "level": 3,
            "id": null,
            "text": "Katalog domyślny dla poszczególnych botów"
          },
          {
            "level": 2,
            "id": null,
            "text": "Drugim elementem jest liczba obok Twojego imienia"
          },
          {
            "level": 3,
            "id": null,
            "text": "Wykorzystane kompletne zestawy, poziom od 1 do 1,000"
          },
          {
            "level": 3,
            "id": null,
            "text": "W jaki sposób sprawdzono tę krzywą, skoro Valve jej nie publikuje"
          },
          {
            "level": 2,
            "id": null,
            "text": "W tym zapisie nie opisuje się rolnictwa w sposób ogólnikowy. Wymienia się je po kolei."
          },
          {
            "level": 3,
            "id": null,
            "text": "„…czas zabawy”"
          },
          {
            "level": 3,
            "id": null,
            "text": "„…bez rzeczywistego wkładu użytkowników”"
          },
          {
            "level": 2,
            "id": null,
            "text": "Każde wyjście z karty w ramach programu „farmed” stanowi wyjście zabronione przez licencję — a Valve pobiera opłatę przy wejściu"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 2.A — licencja"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 2.G — ograniczenie"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 3.D — opłata"
          },
          {
            "level": 3,
            "id": null,
            "text": "Jeśli przeczytasz te trzy zdania razem, pozycja zostanie zamknięta"
          },
          {
            "level": 3,
            "id": "fee-ladder",
            "text": "Opłata przy tych drzwiach nie wynosi 15%. W przypadku karty z opcją „farmed” wynosi ona dwie trzecie tej kwoty."
          },
          {
            "level": 3,
            "id": null,
            "text": "Rzeczywista prowizja od sprzedaży na rynku wspólnotowym, w oparciu o cenę wywoławczą sprzedającego"
          },
          {
            "level": 2,
            "id": null,
            "text": "Bez ostrzeżenia, falami, i rozchodzi się wzdłuż numeru telefonu"
          },
          {
            "level": 3,
            "id": null,
            "text": "Przypadek 4 — czerwiec 2025 r., VAC zakazy dotyczące wyłączonego z eksploatacji CS2"
          },
          {
            "level": 3,
            "id": null,
            "text": "Jak umiera konto główne"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ten sam akapit, napisany w odstępie pięciu lat przez trzech różnych agentów"
          },
          {
            "level": 3,
            "id": null,
            "text": "Uwaga dotycząca pozyskiwania danych — straty na poziomie operatorów"
          },
          {
            "level": 2,
            "id": null,
            "text": "Obie strony tego samego biurka"
          },
          {
            "level": 3,
            "id": null,
            "text": "Klient zajmujący się handlem"
          },
          {
            "level": 3,
            "id": null,
            "text": "Zautomatyzowana flota botów, przeznaczona do obsługi dużych wolumenów"
          },
          {
            "level": 3,
            "id": null,
            "text": "Pytanie, które się w związku z tym nasuwa, ujmując to wprost"
          },
          {
            "level": 2,
            "id": null,
            "text": "Kto reguluje rynek kart?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Pracownik o pseudonimie Valve pełni rolę moderatora największej grupy zajmującej się wymianą kart Valve pracownik"
          },
          {
            "level": 3,
            "id": null,
            "text": "Warstwa listy blokowanych elementów oraz osoba, która nią zarządza Moderator-wolontariusz Usługi stron trzecich"
          },
          {
            "level": 3,
            "id": null,
            "text": "Co z tego wynika, a czego nie"
          },
          {
            "level": 3,
            "id": null,
            "text": "Nikt nie liczy. Takie są wyniki badania."
          },
          {
            "level": 3,
            "id": null,
            "text": "Spis 10,88 mln kont: 88.97% Nienaruszone"
          },
          {
            "level": 3,
            "id": null,
            "text": "Dowody kryminalistyczne i szczegółowy spis ludności"
          },
          {
            "level": 2,
            "id": null,
            "text": "Co zostało przeczytane, a co nie jest przedmiotem roszczenia"
          },
          {
            "level": 3,
            "id": null,
            "text": "Cztery zbiory danych oraz operacje arytmetyczne na nich wykonywane"
          },
          {
            "level": 3,
            "id": null,
            "text": "Źródła pierwotne"
          },
          {
            "level": 3,
            "id": null,
            "text": "Czego nie obejmuje niniejszy zastrzeżenie"
          },
          {
            "level": 3,
            "id": null,
            "text": "Dlaczego narzędzie nie jest przedmiotem"
          }
        ],
        "links": [
          "https://help.steampowered.com/en/faqs/view/71D3-35C2-AD96-AA3A",
          "https://github.com/JustArchiNET/ArchiSteamFarm/wiki/FAQ",
          "https://steamcommunity.com/tradingcards/faq/",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260924114457/https://store.steampowered.com/subscriber_agreement/",
          "https://steamladder.com/ladder/badges/2861690/",
          "http://web.archive.org/web/20260716205303/https://steamladder.com/ladder/badges/2861690/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/farm-economy-timeline.json",
          "https://store.steampowered.com/charts/",
          "http://web.archive.org/web/20260923183013/https://store.steampowered.com/charts/",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://github.com/JustArchiNET/ArchiSteamFarm/discussions/3440",
          "https://x.com/gergelyszabo94/status/1311004678633795585",
          "https://x.com/prcs25/status/1811893857253982720",
          "http://web.archive.org/web/20240715122902/https://x.com/prcs25/status/1811893857253982720",
          "https://reddit.com/r/steamsupport/comments/1fjmgc5/what_to_do_when_your_steam_account_gets_hacked/mkelm2y/",
          "https://www.reddit.com/r/csgomarketforum/comments/r87owv/psa_my_steam_account_just_got_banned/",
          "http://web.archive.org/web/20250327203008/https://www.reddit.com/r/csgomarketforum/comments/r87owv/psa_my_steam_account_just_got_banned/",
          "https://www.reddit.com/r/GlobalOffensiveTrade/comments/r9xql9/d_recently_received_commercial_ban_for_what_seems/",
          "http://web.archive.org/web/20211206034804/https://www.reddit.com/r/GlobalOffensiveTrade/comments/r9xql9/d_recently_received_commercial_ban_for_what_seems/",
          "https://www.reddit.com/r/csgomarketforum/comments/1hhxx7m/d_permanently_locked_on_steam_for_commercial_use/",
          "http://web.archive.org/web/20250627014045/https://www.reddit.com/r/csgomarketforum/comments/1hhxx7m/d_permanently_locked_on_steam_for_commercial_use/",
          "https://www.reddit.com/r/steamsupport/comments/1hkctwt/permanent_ban_with_no_explanation/",
          "https://www.reddit.com/r/pcgaming/comments/1vf24lu/warning_to_all_gamersexpats_steam_took_my_money/",
          "https://steamcommunity.com/groups/card-trading-card-trades",
          "https://steamcommunity.com/id/afarnsworth",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/groups/steambans",
          "https://steamcommunity.com/groups/steambans",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/id/killahinstinct_",
          "https://web.archive.org/web/20240914124859/https://steamcommunity.com/id/msart",
          "https://steamcommunity.com/id/msart/groups/",
          "http://web.archive.org/web/20260401154714/https://steamid.uk/faq/",
          "https://phishdestroy.io/steam_dossier/pl/enforcement_audit.html",
          "https://phishdestroy.io/steam_dossier/pl/#evidence-blackout",
          "https://www.steamcardexchange.net/index.php?badgeprices",
          "http://web.archive.org/web/20260804200309/https://www.steamcardexchange.net/index.php?badgeprices",
          "https://steam.supply/CardBots",
          "https://steamlvlup.net/cardbots",
          "http://web.archive.org/web/20260210171205/https://steamlvlup.net/cardbots",
          "https://steamlvlup.net/",
          "https://creativecommons.org/licenses/by/4.0/",
          "http://web.archive.org/web/20260923221628/https://creativecommons.org/licenses/by/4.0/",
          "https://phishdestroy.io/steam_dossier/pl/market_economics.html",
          "https://phishdestroy.io/steam_dossier/pl/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/pl/elite_skins.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/pl/card_economy.content.json",
      "export_json_sha256": "73a3b863a4656b3d53b81cecd0415716e92ce38370f635450d61083cf58f5a65"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "pl/elite_skins.html",
      "language": "pl",
      "title": "Jeden produkt, dwa systemy cenowe — Dossier „Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/pl/elite_skins",
      "source_html_sha256": "600aa0a450fce0346fde6255faa7b8e8b27545bdaf1ad6bb7bc41c356c07b3cd",
      "exported_at": "2026-09-29T00:18:51.810Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "register",
            "source": "https://phishdestroy.io/steam_dossier/pl/elite_skins#register"
          },
          {
            "id": "",
            "source": "https://phishdestroy.io/steam_dossier/pl/elite_skins#selected"
          }
        ],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "elite_skins.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/pl/elite_skins.pdf?v=print-20260929-v5",
        "sha256": "9a4071ff151c964ed9bf93ce3151fac361fde8573c2fe05686fb265b956abc57",
        "bytes": 98518,
        "pages": 8
      },
      "integrity": {
        "signed_object": "elite_skins.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "elite_skins.content.json.asc",
        "digest_file": "elite_skins.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify elite_skins.content.json.asc elite_skins.content.json",
          "sha256sum -c elite_skins.content.json.sha256"
        ]
      },
      "content": {
        "text": "ZAŁĄCZNIK IV / STRUKTURA RYNKU / 20 WRZESIEŃ 2026\nRejestracja w Elite Skins — Pułap rynkowy na poziomie $1,800\n\nJedna pozycja. Dwa systemy cenowe.\n\nCO WYKAZUJE TA CZĘŚĆ\n\nRejestr ten stanowi empiryczny spis wszystkich kategorii skórek CS2, których cena przekracza limit wystawiania na rynku społecznościowym Steam wynoszący $1,800, na pięciu zewnętrznych platformach handlowych. Dowodzi on, że 248 potwierdzone kategorie wysokiego poziomu — reprezentujące 18,394 aktywnych ofert oraz $78.6 mln w opublikowanej płynności — są 100% nieobecne na oficjalnym rynku Valve. Sprzedawcy poszukujący rzeczywistych cen rynkowych są strukturalnie zmuszeni do korzystania z platform zewnętrznych, opierając się jednocześnie wyłącznie na mechanizmach transakcyjnych serwisu Steam.\n\nWhat this means — the Community Market listing ceiling\n\nSteam’s own market refuses a listing above roughly $1,800. A seller may ask less, never more. Items whose market price sits above that line therefore cannot be sold at that price on Steam at all — which is the mechanism that moves those sales to third-party venues while the item itself never leaves Valve’s inventory system.\n\nSection 13 — the off-Steam price gap →\n\n← Powrót do podsumowania dla kadry kierowniczej\n\nSteam górna granica oferty na platformie Community Market wynosi około $1,800. Na pięciu zewnętrznych platformach handlowych, których ceny uwzględniono w niniejszym zestawieniu, 419 Kategorie produktów CS2 mają najniższą aktualną cenę sprzedaży powyżej tego limitu — a 402 z nich, 95.9%,, w ogóle nie mają Steam żadnych ofert. Łącznie posiadają oni egzemplarze wymienione w indeksie „18,641”, których wartość wynosi co najmniej $82.4 mln. Aby cena została uznana, konieczna jest zgoda drugiego rynku, 248 Wszystkie te kategorie zostały potwierdzone — i w każdej z nich strona 100%, nie występuje w serwisie Steam. Najdroższa to naklejka | Titan (Holo) | Katowice 2014 na $66,285, notowany na czterech platformach handlowych w przedziale 5.2% od siebie, a nie notowany na żadnej z platform Valve. Pełna lista notowań, wykresy i klasyfikacja znajdują się w atlas drabinki cenowej.\n\nSprawdź wszystkie wpisy na stronie 419 ↓Otwórz atlas ↗Zapoznaj się z metodą\n248kategorie, w których na co najmniej dwóch platformach handlowych cena przekracza limit\n18,394egzemplarze wystawione na pięciu platformach sprzedażowych\n$78.6Mwartość minimalna tych ofert\n100%z nich w ogóle nie ma na stronie Steam\n\nSprostowanie · na tej stronie podano wcześniej niepotwierdzoną cenę\n\nWcześniejsza wersja tej strony zawierała pozycję „Souvenir AK-47” | „Point Disarray”, której cena wywoławcza wynosiła $148,954 na jednej platformie handlowej, podczas gdy na Steam wyceniono ją na $119. Pozycja ta znajduje się na jednej półce i dotyczy pojedynczego egzemplarza, przy czym żadna inna platforma handlowa nie podaje tej samej ceny, więc jest to raczej cena wywoławcza niż rzeczywista cena, a pozycja ta nie jest już dostępna na stronie. Każda z podanych tutaj wartości jest obecnie ograniczona do kategorii 248, w których co najmniej dwie platformy handlowe niezależnie od siebie wyceniają produkt powyżej limitu. Sam wiersz nie został usunięty — nadal znajduje się w rejestrze poniżej, a klasyfikacja, która spowodowała jego obniżenie, została w pełni przedstawiona w atlas drabinki cenowej.\n\n01 / środki w aktywnych zleceniach sprzedaży\nMierzalny dolny próg w dolarach\n\nDane obliczono na nowo na podstawie licencjonowanego zrzutu ekranu z serwisu cs2.sh obejmującego pięć platform handlowych. Jest to minimalna łączna wartość ofertowa w określonym podzbiorze; nie jest to obrotem ze sprzedaży ani wyceną gospodarki CS2.\n\n248 KATEGORIE POTWIERDZONE · 18,394 EGZEMPLARZE W SPISIE · 5 PLATFORMY HANDLOWE$78.62M\n\nMinimalna łączna cena sprzedaży podana dla każdego produktu CS2, dla którego co najmniej dwie platformy handlowe niezależnie od siebie ustalają cenę powyżej limitu dopuszczalnego przez Valve na własnym rynku.\n\nDlaczego jest to wartość minimalna, a nie szacunkowa\n\nDla każdego rynku mnożymy jego najniższy zapytaj o cenę przedmiotu na podstawie liczby egzemplarzy podanej na platformie. Każdy kolejny egzemplarz na tej półce jest wyceniony na poziomie co najmniej najniższej podanej ceny, więc rzeczywista cena rynkowa jest wyższa — wynika to z samej konstrukcji systemu, a nie z domysłów. Nie jest to wyprzedaż, przepływ gotówki ani wycena rynkowa, a ten sam fizyczny przedmiot może pojawić się na więcej niż jednej platformie.\n\nSprawdź wszystkie wiersze źródłowe w pliku „419” ↗\n★ Rękawiczki sportowe | Labirynt żywopłotowy (sprawdzone w praktyce)\n$4.68M\nAWP | Gungnir (nowy, fabrycznie nowy)\n$4.46M\nAWP | Dragon Lore (nowy, fabrycznie nowy)\n$4.34M\n★ Nóż motylkowy | Fade (nowy, fabrycznie nowy)\n$4.17M\nAK-47 | Wild Lotus (nowy, fabrycznie nowy)\n$4.16M\n★ Nóż motylkowy | Doppler (nowy, fabrycznie nowy)\n$3.64M\n\nSłupki przedstawiają sześć największych wkładów na poziomie kategorii w obliczenia ceny minimalnej, w skali od największego do najmniejszego. Wysoki słupek odzwierciedla zarówno najniższą cenę sprzedaży, jak i liczbę wystawionych egzemplarzy. Ten sam przedmiot fizyczny może pojawiać się na więcej niż jednej platformie handlowej, dlatego danych tych nie wolno sumować z żadnymi innymi sumami rynkowymi.\n\n02 / przykłady, które można sprawdzić\nCzego nie uwzględnia ten limit\n\nIlustracje odpowiadają dokładnym nazwom przedmiotów, o ile są one podane. Ceny to aktualne ceny wywoławcze z katalogu z podaną datą, a nie dane dotyczące transakcji.\n\n★ Butterfly Knife | Doppler (Factory New)\n\nŹródło: https://phishdestroy.io/steam_dossier/pl/elite_skins#selected\n\nMierzalna luka: Oferty te nie mogą być dorównane przez ogłoszenia zamieszczone na stronie Steam przy tej samej kwocie w dolarach amerykańskich. Własna strona Valve Najczęściej zadawane pytania dotyczące targu lokalnego zarchiwizowano 2026-09-21 ↗ określa maksymalną cenę ofertową na poziomie około1,800 dolarów. Sprzedający może jednak wystawić ofertę poniżej tej kwoty; to, czy będzie to akceptowalne, zależy od decyzji sprzedającego. Osobny Wyszukiwanie produktów o wartości powyżej $ na CSMarketCap1,800 ↗ przedstawia dane serwisu Factory New Dragon Lore z rynków indeksowanych przez 28, obejmujące około 1.1K wyświetlonych ofert; pozycje występujące w kilku miejscach mogą być zliczone więcej niż raz.\n\n03 / zależność strukturalna\nCzapka Steama powoduje odchylenie od ustalenia ceny Steam\n\nPorównanie to ma charakter strukturalny. Nie zakłada ono, że każda cena wywoławcza jest uczciwa, ani nie traktuje niesprzedanych ofert jako przychodów.\n\n01 · ZASADA\nSteam zamyka listę\n\nValve twierdzi, że liczba ofert na Community Market jest ograniczona do około $1,800. Salda portfeli są również ograniczone, a środków z portfeli nie można wypłacić w gotówce.\n\n02 · OBSERWACJA\nDragon Lore:10,940.85 dolarów\n\nW katalogu platformy handlowej „5-” przedstawiono 389 oferty na żywo dla AWP Dragon Lore (nowy, fabrycznie), w cenie od $10,940.85 (poziom CSFloat). Szerszy rejestr zawiera 248 potwierdzone kategorie powyżej limitu Steam.\n\n03 · KONSEKWENCJA\nPodział ceny i opłaty za transfer\n\nSprzedawca, który chce uzyskać wyższą cenę nie mogę opublikować tego na stronie Steam. Usługi zewnętrzne mogą ustalać cenę gotówkową, ale w przypadku dostawy nadal obowiązują zasady dotyczące własności i przekazywania towarów określone przez Steam.\n\nSprzeczność w polityce: Własność Valve Umowa abonamentowa zarchiwizowano 2026-09-21 ↗ zastrzega sobie prawo do komercyjnego wykorzystania usług serwisu Steam, o ile nie zostało to wyraźnie dozwolone, przy czym jego 2016 oświadczenie zarchiwizowano 2026-09-21 ↗ Wspomniani operatorzy gier hazardowych korzystali już z serwisu Steam, OpenID oraz zautomatyzowanych kont. Stanowi to bezpośredni dowód na to, że Valve wiedziało o istnieniu tej grupy zewnętrznych operatorów na stronie 2016.. Mimo to oficjalna platforma handlowa nie może publikować zaobserwowanych cen tych przedmiotów o wysokiej wartości. Chodzi o zależność architektury od ustalania cen i transakcji poza platformąSteam; status umowy każdego z poszczególnych rynków wymaga przedstawienia odrębnych dowodów. Dwa główne zachodnie rynki, na których odnotowuje się ten nadmierny wolumen transakcji, działają jako formalne podmioty gospodarcze w głównych jurysdykcjach — CSFloat Inc. (spółka zarejestrowana w stanie Delaware w USA) oraz Skinport GmbH (zarejestrowana w Stuttgarcie, Niemcy, nr w rejestrze handlowym HRB 764879) — prowadząca jawną działalność w zakresie sprzedaży przedmiotów w systemie peer-to-peer o wartości setek milionów, opierając się bezpośrednio na interfejsach API serwisu Steam oraz jego infrastrukturze handlowej.\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\nCztery wiersze o wartości $100,000 odpowiadają maksymalnej cenie ofertowej ustalonej przez firmę „CSFloat”. Są one zaznaczone w rejestrze i nie należy ich traktować jako wycen. Zarchiwizowany zrzut strony z ofertami CSFloat obejmował jedynie kwoty do około $6,999,, dlatego w celu uzyskania pełnego rejestru >$1,800 wykorzystano migawkę publicznego katalogu.\n\n04 / kolejna gra z serii „Valve”\nW rankingu znalazła się również gra Dota 2\n\nTen sam rygorystyczny test najtańszej oferty na stronie Skinport wykrywa kategorie 166 CS2 oraz 3 Dota 2. Stanowią one odrębną migawkę rynku; nie należy ich dodawać do CSFloat’s 245.\n\nDOTA 2 · OFERTA 1\nHeroiczny Brutalny Półksiężyc\n\nNajtańsze Skinport – zapytaj: $14,622.25.\n\nDOTA 2 · OFERTA 1\nPłaszcz „Dark Artistry”\n\nNajtańsze Skinport – zapytaj: $8,255.16.\n\nDOTA 2 · OFERTA 1\nZepsuta Gwiazda Zasilana\n\nNajtańsze Skinport – zapytaj: $2,087.92.\n\nSą to trzy wymienione kategorie przedmiotów, a nie wszystkie istniejące przedmioty w grze Dota 2. Sprawdź wiersze z datą „Skinport” ↗ oraz API dokumentacja ↗.\n\n05 / niezawodność\nWynik ten nie zależy od dokładnej wartości limitu\n\nValve ustala górną granicę w walucie regionalnej nabywcy, więc po przeliczeniu na dolary amerykańskie nie daje to jednej konkretnej kwoty. W związku z tym spisy są powtarzane przy każdym prawdopodobnym progu. Odsetek tych pozycji, których brakuje na stronie Steam, nigdy nie spada poniżej 95%.\n\nPrzeprowadzono testy progowe\tKategorie produktów\tWymienione egzemplarze\tWartość minimalna\tNieobecni na stronie Steam\n$1,800\t419\t18,641\t$82,449,526\t95.9%\n$2,000\t382\t15,159\t$75,541,325\t95.5%\n$2,070\t363\t12,336\t$69,560,305\t95.6%\n$2,300\t323\t11,644\t$67,984,432\t95.0%\n$2,500\t299\t10,950\t$66,203,929\t95.0%\n\nNależy czytać po jednym wierszu na raz; wiersze te stanowią zagnieżdżone podzbiory tego samego spisu ludności, a nie odrębne populacje. „Wartość minimalna” mnoży wartość każdego rynku najniższy podaje liczbę egzemplarzy, które figurują w wykazie, więc z samej natury rzeczy zaniża stan zasobów. Otwórz zbiór danych ↗\n\n06 / niedobór, który można policzyć\nJak niewiele z nich faktycznie jest dostępnych w sprzedaży\n\nBUFF dzieli pulpit każdego przedmiotu na przedziały z wartościami zmiennoprzecinkowymi i podaje, ile egzemplarzy znajduje się w każdym z nich. Dzięki temu słowo „rzadki” staje się liczbą — a cena za stan przedmiotu jest wyceniana oddzielnie od ceny za wygląd.\n\n298 WYKAZ EGZEMPLARZY\nAWP | Wiedza o smokach\n\n8 poszczególne warianty wraz z cenami. Najdroższy, Pamiątkowy AWP | Dragon Lore (nowy, fabrycznie zapakowany), pyta $12,363 z 20 egzemplarzami na półce.\n\nW najlepszym zestawie do pływania dostępnym na półce (0–0.01) znajdują się 2 egzemplarze, pytając $17,875 — dopłata w wysokości a +45% w stosunku do podstawowej ceny wywoławczej przedmiotu, ustalonej wyłącznie na podstawie jego stanu.\n\n607 WYKAZ EGZEMPLARZY\nM4A4 | Howl\n\n12 poszczególne warianty wraz z cenami. Najdroższy, Pamiątka M4A4 | Howl (nowy, fabrycznie nieużywany), pyta $14,895 z 2 egzemplarzami na półce.\n\n213 WYKAZ EGZEMPLARZY\nAK-47 | Wild Lotus\n\n7 poszczególne warianty wraz z cenami. Najdroższy, Pamiątkowy AK-47 | Wild Lotus (nowy, fabrycznie nowy), pyta $14,895 z 2 egzemplarzami na półce.\n\n310 WYKAZ EGZEMPLARZY\nAWP | Gungnir\n\n7 poszczególne warianty wraz z cenami. Najdroższy, Pamiątkowy AWP | Gungnir (nieznaczne ślady użytkowania), pyta $14,895 z 2 egzemplarzami na półce.\n\nDlaczego ma to znaczenie dla pozostałej części niniejszego dossier: Nie są to abstrakcyjne pojęcia. Na całym świecie na otwartych półkach znajduje się kilkaset egzemplarzy każdego z tych trofeów, z których każdy jest powiązany z jednym kontem Steam i został przeniesiony w ramach jednej transakcji Steam. Na tak wąskim rynku kradzież pojedynczego przedmiotu z zapasów stanowi wymierne zdarzenie, a techniki przejmowania kont opisane w innych częściach niniejszego dochodzenia przynoszą bezpośrednie i wymierne korzyści.\n\nLiczby te odzwierciedlają aktualną liczbę ofert na jednej platformie handlowej w momencie rejestracji, a nie całkowitą liczbę istniejących egzemplarzy. Egzemplarze znajdujące się w prywatnych zasobach nie są tu w ogóle uwzględniane. Otwórz zbiór danych „float” ↗\n\n07 / drabina poza zasięgiem wzroku\nIm droższy przedmiot, tym dalej znajduje się od jakiegokolwiek widocznego miejsca\n\nKażdy z poniższych poziomów stanowi odrębną kategorię dowodową. Celowo nie zostały one połączone w jedną liczbę.\n\nPrzegródka\tRysunek\tCzym właściwie jest ten fakt\nCeiling on Valve's own market\t~$1,800\tPublished rule, stated in the Steam Community Market FAQ.\nDearest ask several marketplaces agree on\t$66,285\tMeasured by us in this snapshot. Sticker | Titan (Holo) | Katowice 2014, quoted by four marketplaces within 5.2% of one another. An ask, not a sale.\nDearest ask seen on any single shelf\t$148,954\tOne marketplace, one copy, no second marketplace agreeing — and equal to a round CNY 1,000,000 at the snapshot rate. Listed here as the outer edge of what sellers ask, and relied on for nothing.\nPublic marketplace sale\t$49,999\tSpecialist Gloves | Crimson Kimono (FN) on CSFloat, as reported by SteamAnalyst. Platform-recorded, third-party reported.\nReported private sale\t$400,000\tAK-47 | Case Hardened, reported by PC Gamer in April 2023. Journalism, not a record we hold.\nReported offer, declined\t$1,500,000\tBlue Gem Karambit, pattern #387. No sale took place and the figure has not been independently confirmed. Included to mark the ceiling of the claims, not to assert a value.\n\nKwestia strukturalna: Rynek Valve sięga około $1,800.. Platformy zewnętrzne podnoszą cenę do około $66,000, gdzie zgadza się na nią kilka z nich, oraz do około $150,000, gdzie zgadza się tylko jedna. Powyżej tej kwoty nie ma już żadnej platformy — największe transakcje dotyczące aktywów wyemitowanych przez Valveodbywają się prywatnie, między osobami fizycznymi, bez notowań, bez śladu na platformie, bez weryfikacji tożsamości i bez raportowania. Sam transfer nadal odbywa się na Steam. Im wyższa wartość, tym mniej osób ma do niej dostęp, a cała infrastruktura, która ją obsługuje, należy w całości do firmy „Valve”.\n\nDwa ostatnie punkty to informacje pochodzące od innych osób, które zostały odpowiednio oznaczone jako takie. W ramach tego projektu nie zostały one zweryfikowane i nie stanowią one podstawy do wyciągania jakichkolwiek wniosków.\n\nWszystkie kategorie obserwowane w ramach projektu „419”\n\nŹródło: https://phishdestroy.io/steam_dossier/pl/elite_skins#register\n\n09 / pochodzenie i ograniczenia\nSprawdź obliczenia\n\nUdostępniamy dane lokalne oraz źródło publiczne. Zakres danych liczbowych w nagłówku ogranicza się do strony CSFloat w dniu zrzutu ekranu.\n\nWłasne ograniczenia i warunki serwisu Valve\n\nSteam Najczęściej zadawane pytania dotyczące rynku społecznościowego ↗ zarchiwizowano 2026-09-21 ↗ podaje przybliżoną maksymalną cenę ofertową wynoszącą $1,800. Ta Umowa abonamentowa ↗ zarchiwizowano 2026-09-21 ↗ określa ograniczenia dotyczące wykorzystania komercyjnego.\n\nSkąd biorą się ceny\n\nCeny, liczba akcji w obrocie oraz przedziały płynności pochodzą z cs2.sh dane rynkowe API w ramach płatnej subskrypcji komercyjnej, przy użyciu klucza licencyjnego. Nie przeprowadzono zgrywania danych z żadnej platformy handlowej ani nie wykorzystano żadnego konta ani danych uwierzytelniających na żadnej platformie handlowej. Dostawca agreguje dane z serwisów BUFF, Youpin, CSFloat, Skinport, C5Game oraz Steam Community Market; wszystkie kwoty podano w dolarach amerykańskich zgodnie z otrzymanymi danymi. Otwórz manifest pochodzenia ↗ — rejestruje dokładne punkty końcowe, czasy wykonania zrzutów oraz skróty SHA-256 surowych zrzutów, dzięki czemu niezależny czytelnik dysponujący własnym kluczem może pobrać te same dane i ponownie obliczyć każdą wartość podaną na tej stronie.\n\nCzego nie udało nam się zdobyć\n\nZakupiona subskrypcja obejmuje wyłącznie aktualne migawki. Nie mieliśmy dostępu do historycznych i archiwalnych punktów końcowych, a Na tej stronie nie przedstawia się żadnych twierdzeń dotyczących jakichkolwiek trendów, cen z przeszłości ani zmian w czasie. Wszystko tutaj to pojedyncza chwila, opatrzona datą.\n\nWcześniejszy rejestr „CSFloat”\n\nW pierwszej wersji tej wystawy uwzględniono 245 kategorii pochodzących z pojedynczego CSFloat zrzutu katalogu z dnia 20 września 2026: to zdjęcie nadal tu jest ↗. Obecny rejestr jest szerszy, ponieważ obejmuje pięć platform handlowych, a nie jedną. Są to dwa odrębne zestawienia i nie wolno ich sumować.\n\nOświadczenie Valve dotyczące egzekucji na podstawie wyroku\n\nAktualizacja dotycząca handlu przedmiotami w grze „2016” autorstwa Valve ↗ zarchiwizowano 2026-09-21 ↗ dotyczy operatorów gier hazardowych korzystających z OpenID oraz zautomatyzowanych kont typu „Steam”. Jest to ograniczenie o węższym zakresie niż całkowity zakaz korzystania ze wszystkich zewnętrznych platform handlowych.\n\nGranica interpretacji\n\nSą to oferty, a nie transakcje sprzedaży. Nazwa rynkowa może odnosić się do wielu fizycznych przedmiotów o różnych szczegółach dotyczących wykończenia, wzoru lub naklejek. Niniejszy rejestr nie odzwierciedla całkowitej wartości rynkowej ani intencji serwisu Valve.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Rejestracja w Elite Skins — Pułap rynkowy na poziomie $1,800"
          },
          {
            "level": 2,
            "id": null,
            "text": "Mierzalny dolny próg w dolarach"
          },
          {
            "level": 3,
            "id": null,
            "text": "Dlaczego jest to wartość minimalna, a nie szacunkowa"
          },
          {
            "level": 2,
            "id": null,
            "text": "Czego nie uwzględnia ten limit"
          },
          {
            "level": 3,
            "id": null,
            "text": "★ Butterfly Knife | Doppler (Factory New)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Czapka Steama powoduje odchylenie od ustalenia ceny Steam"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam zamyka listę"
          },
          {
            "level": 3,
            "id": null,
            "text": "Dragon Lore:10,940.85 dolarów"
          },
          {
            "level": 3,
            "id": null,
            "text": "Podział ceny i opłaty za transfer"
          },
          {
            "level": 2,
            "id": null,
            "text": "W rankingu znalazła się również gra Dota 2"
          },
          {
            "level": 3,
            "id": null,
            "text": "Heroiczny Brutalny Półksiężyc"
          },
          {
            "level": 3,
            "id": null,
            "text": "Płaszcz „Dark Artistry”"
          },
          {
            "level": 3,
            "id": null,
            "text": "Zepsuta Gwiazda Zasilana"
          },
          {
            "level": 2,
            "id": null,
            "text": "Wynik ten nie zależy od dokładnej wartości limitu"
          },
          {
            "level": 2,
            "id": null,
            "text": "Jak niewiele z nich faktycznie jest dostępnych w sprzedaży"
          },
          {
            "level": 3,
            "id": null,
            "text": "AWP | Wiedza o smokach"
          },
          {
            "level": 3,
            "id": null,
            "text": "M4A4 | Howl"
          },
          {
            "level": 3,
            "id": null,
            "text": "AK-47 | Wild Lotus"
          },
          {
            "level": 3,
            "id": null,
            "text": "AWP | Gungnir"
          },
          {
            "level": 2,
            "id": null,
            "text": "Im droższy przedmiot, tym dalej znajduje się od jakiegokolwiek widocznego miejsca"
          },
          {
            "level": 2,
            "id": null,
            "text": "Wszystkie kategorie obserwowane w ramach projektu „419”"
          },
          {
            "level": 2,
            "id": null,
            "text": "Sprawdź obliczenia"
          },
          {
            "level": 3,
            "id": null,
            "text": "Własne ograniczenia i warunki serwisu Valve"
          },
          {
            "level": 3,
            "id": null,
            "text": "Skąd biorą się ceny"
          },
          {
            "level": 3,
            "id": null,
            "text": "Czego nie udało nam się zdobyć"
          },
          {
            "level": 3,
            "id": null,
            "text": "Wcześniejszy rejestr „CSFloat”"
          },
          {
            "level": 3,
            "id": null,
            "text": "Oświadczenie Valve dotyczące egzekucji na podstawie wyroku"
          },
          {
            "level": 3,
            "id": null,
            "text": "Granica interpretacji"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/pl/#market-gap-section",
          "https://phishdestroy.io/steam_dossier/pl/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/pl/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/pl/skin_atlas.html#grading",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-above-the-ceiling.json",
          "https://phishdestroy.io/steam_dossier/pl/elite_skins#selected",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://csmarketcap.com/search?minPrice=1800&amp;page=1",
          "https://store.steampowered.com/agreement/?l=english",
          "http://web.archive.org/web/20260921022032/https://store.steampowered.com/agreement/?l=english",
          "https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921021947/https://store.steampowered.com/oldnews/22883",
          "https://phishdestroy.io/steam_dossier/pl/#proxy-bypass-explainer",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/skinport-floor-over-cap.json",
          "https://docs.skinport.com/items",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-float-scarcity.json",
          "https://phishdestroy.io/steam_dossier/pl/elite_skins#register",
          "https://cs2.sh/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/csfloat-catalogue.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/pl/elite_skins.content.json",
      "export_json_sha256": "79f1b6362a987aac968f08d8b726b61a4854637435295189599a747267f7f5a6"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "pl/enforcement_audit.html",
      "language": "pl",
      "title": "Spis ludności Valve nie zostanie opublikowany — Raport Steam",
      "source_url": "https://phishdestroy.io/steam_dossier/pl/enforcement_audit",
      "source_html_sha256": "fcaa7136a2f7eea85c47996a2f02a8551195ce10b1947dc25b0538b845846501",
      "exported_at": "2026-09-29T00:18:49.160Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "enforcement_audit.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/pl/enforcement_audit.pdf?v=print-20260929-v5",
        "sha256": "13e709f762a42d4fbc5ae541295fe2914b62e90f7901fa5b1ce0874b76710e83",
        "bytes": 156307,
        "pages": 13
      },
      "integrity": {
        "signed_object": "enforcement_audit.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "enforcement_audit.content.json.asc",
        "digest_file": "enforcement_audit.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify enforcement_audit.content.json.asc enforcement_audit.content.json",
          "sha256sum -c enforcement_audit.content.json.sha256"
        ]
      },
      "content": {
        "text": "ZAŁĄCZNIK VI — WYNIKI SPISU LUDNOŚCI Z ROKU VALVE NIE ZOSTANĄ OPUBLIKOWANE\nJak duża jest farma na Steam? Policzyliśmy ją sami.\n\nNie opublikowano danych dotyczących liczby kont automatyzacji działających na Steam. Nie ma potrzeby, by informacja ta była utrzymywana w tajemnicy: przestrzeń identyfikatorów Steam stanowi ciągły zakres liczb całkowitych, a Valve wydaje klucz API sieci Web, który umożliwia przeglądanie tego zakresu. Wzięliśmy więc największą populację, która sama się identyfikuje — społeczność ArchiSteamFarm — i przeczytaliśmy dane każdego członka raz za pomocą własnego punktu końcowego blokowania serwisu Valve. Dzieje się tak, ponieważ ASF przy pierwszym uruchomieniu automatycznie dołącza do grupy Steam, chyba że użytkownik wyraźnie zrezygnuje z członkostwa lub odznaczy opcję dołączenia do grupy (AutoJoinSteamGroup / Statystyki). Ponieważ to ustawienie jest domyślnie włączone, grupa ta obejmuje szeroką populację: aktywne sieci komercyjnych botów korzystających z wielu kont, okazjonalnych użytkowników-hobbystów pozostawiających konta bezczynne oraz zwykłych graczy, którzy uruchamiali oprogramowanie na swoim osobistym koncie i nigdy nie wyłączyli domyślnej subskrypcji. Dzięki temu skład tej grupy stanowi miarodajny spis łącznego zasięgu oprogramowania: 10,880,610 łączna liczba kont (w tym 5,360,499 zweryfikowanych członków bez ograniczeń, którzy przeszli przez bramkę sklepu $5.00). Następnie zadaliśmy jedyne pytanie, które ma znaczenie — co właściwie zrobił im Valve?\n\nCzym ta strona nie jest. Nie chodzi tu o to, że Valve powinno zablokować dziesięć milionów osób, ani o skargę na osoby zajmujące się farmowaniem kart. Każda z poniższych liczb pojawia się tu z jednego powodu: Valve czy trwale blokować użytkowników, a jako powód podaje na piśmie wykorzystanie Steam w celach komercyjnych oraz automatyzację. Mierzy to, w jaki sposób ta sama zasada jest stosowana do tego samego zachowania na dużą skalę — przez operatora, który po drodze pobiera opłaty za odblokowanie $5.00, licencje na gry oraz opłaty za Market Valve. Stwierdzono asymetrię, a nie samo farmowanie.\n\nLiczba 10,88 mlnOszuści, którzy chodzą (53,5 tys.)Audyt płatny za 100 tys. vs audyt bezpłatny\n10,880,610Łączna liczba członków grupy ASF, którzy zapoznali się z własnym interfejsem API blokady użytkownika Valve (użytkownicy z ograniczeniami i bez ograniczeń łącznie)\n88.97%Nigdy nie zostałem zablokowany — 9,680,599 kont nadal działa\n63.06%Spośród zablokowanych kont są te, za które zapłacono ($5+ wydatki) — 100,000 SRSWOR przedział (±0.39% MoE)\n67.77%Spośród 51,732 oszustów, wobec których zapadł wyrok, nikt nie ma na koncie żadnego zakazu związanego z oszustwami (pełny spis)\n01 — Skala\nDziesięć milionów kont, z czego dziewięć na dziesięć pozostało nietkniętych\n\nJedna populacja, która sama się zlicza, odczytana raz przez własny punkt końcowy Valve.\n\nDLACZEGO SAMODZIELNIE PRZELICZA\nASF dołącza do grupy specjalnie dla Ciebie\n\nPrzy pierwszym uruchomieniu ArchiSteamFarm zestawów Statystyki domyślnie ustawia tę opcję na „true” i dołącza do grupy „SC Farm Steam” w systemie Archi. Operator musi aktywnie zrezygnować z członkostwa. Członkostwo stanowi więc dolną granicę liczby instalacji — a nie górną. Operatorzy, którzy wyłączyli statystyki, nie są uwzględnieni; rzeczywista liczba instalacji jest co najmniej tak duża.\n\nCO CZYTAMY\n10,880,610 łączna liczba wpisów\n\nLista członków API zwróciła łącznie 10,880,610 identyfikatorów SteamID64 — zarówno z ograniczeniami, jak i bez. Strona grupy Steam pokazuje 5,360,499 (tylko bez ograniczeń). Każdy wpis został przetworzony raz przez ISteamUser/GetPlayerBans w dniu 2026-09-23. Pięćdziesiąt pięć minut na jednym klawiszu.\n\nODPOWIEDŹ\n88.97% wyczyść\n\n1,200,011 podlegać jakiemukolwiek Steam zakazowi (11.03%). Pozostałe 9,680,599 nie ma żadnych wpisów w rejestrze — ani blokada społecznościowa, ani VAC, nic. Farma nie jest likwidowana. Działa dalej. Wystarczy ta sama klauzula, skierowana przeciwko jednej osobie, by ją trwale usunąć.\n\nSpośród 10,880,610 kont, ile z nich Valve zostało wykorzystanych\n\nCała zbadana populacja, podzielona według tego, czy Valve nałożyło jakikolwiek zakaz. Czerwony wycinek obejmuje wszystkie działania, jakie Valve kiedykolwiek podjęło wobec tej floty.\n\n88.97%nigdy nie zablokowany\n11.03%\nBrak jakichkolwiek zakazów — 9,680,599 (88.97%)Zawiera pewien zakaz Steam — 1,200,011 (11.03%)\n10,880,610Członkowie grupy ASF zostali zeskanowani\n9,680,599Nigdy nie zablokowano — 88.97%\n1,200,011Zastosuj dowolny zakaz — 11.03%\n55 minAby zliczyć to wszystko przy użyciu jednego klucza API\nIle ta flota już zapłaciła za swoje istnienie Valve\n\nNie jest to szacunkowa kwota dochodów gospodarstwa. Jest to minimalna kwota, jaką gospodarstwo wydało już w sklepie Valve — obliczona na podstawie zasady Valve, zastosowanej do powyższej liczby.\n\nLiczba 10,880,610 obejmuje pełną listę członków grupy ASF zwróconą przez API — obejmuje ona zarówno konta z ograniczeniami, jak i konta bez ograniczeń. Własna lista Steam Konta użytkowników z ograniczonymi uprawnieniami Na tej stronie podano, że konta z ograniczeniami nie liczyć się jako Steam przynależność do grupy (nie są one uwzględniane przy wyświetlaniu liczby członków grupy), ale nadal mogą figurować na bazowej liście członków. Podzbiór nieograniczony — konta, które wydały co najmniej $5.00 w sklepie Steam — wynosi dokładnie 5,360,499 — na stronie grupy wyświetla się liczba Steam, która zgodnie z zasadą określoną przez Steam nie uwzględnia kont z ograniczeniami. Obliczenie progu $5.00 odnosi się wyłącznie do tego podzbioru kont bez ograniczeń.\n\n5,360,499członkowie bez ograniczeń\n(Liczba wyświetlanych grup użytkownika Steam)\n×\n$5.00Własna wartość minimalna Valve\naby przestać być ograniczonym\n=\n$26,802,495limit wydatków w sklepie\nprzez nieograniczony podzbiór\n\nJest to dolna granica kwoty, jaką Valve otrzymało już od nieograniczonej części floty — nie jest to szacunek przychodów ani deklaracja zysku. Rzeczywiste wydatki na konto są w większości przypadków wyższe; wartość $5.00 stanowi jedynie minimalny wymagany próg.\n\nDodatkowy zysk: opłata w wysokości do 66.7% od wielkości wyhodowanego towaru. Oprócz opłaty za wstęp w wysokości $26.8M, każda karta i każdy przedmiot wystawiony na sprzedaż na Rynku Społecznościowym podlega obowiązkowej opłacie minimalnej w wysokości Valve (składającej się z opłaty $0.01 Steam oraz opłaty wydawcy $0.01). W przypadku typowych kart o wartości 3 centów i przedmiotów bezwartościowych, Valve zabiera 2 centy z 3 centów — co w praktyce oznacza obniżkę o 66.67% na korzyść Valve, znacznie przewyższając nominalną stopę marketingową 15%.\n\nIstotne zastrzeżenie dotyczące populacji: Przynależność do grupy nie stanowi dowodu na to, że każde konto jest botem, ani nie obejmuje wszystkich botów na Steam. ASF domyślnie automatycznie dodaje konta do swojej grupy społecznościowej po uruchomieniu; chyba że użytkownik wyraźnie odznaczy tę opcję lub wyłączy ten parametr konfiguracyjny (AutoJoinSteamGroup), stali gracze, osoby korzystające z gry sporadycznie oraz członkowie społeczności pozostają na liście obok zautomatyzowanych flot farmujących. Ponadto blokada typu Steam nie zawiera pola z publicznym uzasadnieniem. Wynik ten stanowi empiryczny wskaźnik dla całej populacji związanej z tym oprogramowaniem, a nie indywidualny werdykt dotyczący konkretnego konta. Zagregowane, powtarzalne: asf-ban-census-2026-09-23.json.\n\n02 — Geografia\nGdzie stacjonuje flota\n\nTylko 8.5% z zablokowanych kont podało w ogóle kraj pochodzenia. Spośród tych, które to zrobiły, największy udział mają Stany Zjednoczone.\n\nProfil typu Steam zawiera opcjonalne pole „kraj”. 100,413 z 1,182,811 zablokowanych kont wypełniło to pole — 8.5%.† Wśród tej mniejszości na czele znajdują się Stany Zjednoczone z wynikiem 15.5%, następnie Ukraina, Chiny i Rosja, a pozostałe kraje tworzą długi ogon rozciągający się po Europie, Ameryce Łacińskiej i Azji Południowo-Wschodniej. Nikt nie weryfikuje tych danych: Afganistan plasuje się w pierwszej dziesiątce, co w przybliżeniu odpowiada jego rzeczywistej wartości. Pozostałe 91.5% pozycje zostały pominięte, a nie przypisane, więc poniższy wykres przedstawia obraz mniejszości, która sama się wyłoniła — nie jest to mapa floty ani podstawa do stwierdzenia, skąd jest ona zarządzana.\n\nZablokowane konta według podanego kraju\n\n15 krajów z czołówki 100,413 zablokowanych kont, które ujawniają lokalizację publiczną. Udział dotyczy tej podgrupy. Najedź kursorem, aby wyświetlić liczby.\n\n0%\n5%\n10%\n15%\n20%\nUnited States\nUkraine\nChina\nRussia\nCanada\nAustralia\nJapan\nBrazil\nGermany\nAfghanistan\nUnited Kingdom\nRomania\nFrance\nPhilippines\nIndia\n\nLokalizacja odczytana z GetPlayerSummaries dla zablokowanego podzbioru. Pole to jest wypełniane przez właściciela konta i nie jest przez nikogo weryfikowane, więc punkt wyjścia sieci VPN czy żartobliwy wpis liczą się tak samo jak prawdziwy wpis.\n\n03 — Świeżość\nNajnowsze transakcje, a nie zaległości z poprzednich okresów\n\nBiorąc pod uwagę datę utworzenia kont, grupa zablokowanych użytkowników jest stosunkowo nowa i nie stanowi pozostałości po erze kart kolekcjonerskich.\n\nGdyby chodziło o stare bałagany, które powoli się sprząta, zablokowane konta pochodziłyby głównie z początkowych lat istnienia kart kolekcjonerskich. Jest jednak odwrotnie. Spośród 1,132,852 zablokowanych kont, których data utworzenia jest znana, 70% powstały w 2020 roku lub później, a prawie połowa z nich – od 2023 roku. Liczba ta wzrosła z 59,175, ustalonej w 2017 r., do maksymalnej wartości wynoszącej 227,030 utworzone tylko w 2024 r.. Każdy z nich przekroczył bramkę sklepu $5.00, zanim zdążyła ona odczytać kartę, więc od każdego z nich pobrano opłatę za wstęp.\n\nKiedy utworzono zablokowane konta\n\nLata założenia kont przez 1,132,852 zablokowanych użytkowników, u których widoczna jest data założenia. Okres ten obejmuje lata 2020–2026, a nie erę kart kolekcjonerskich z lat 2013–2015. Szczyt: 2024 r. Najedź kursorem, aby zobaczyć liczby.\n\n0k\n63k\n125k\n188k\n250k\n'13\n'14\n'15\n'16\n'17\n'18\n'19\n'20\n'21\n'22\n'23\n'24\n'25\n'26\n70%Spośród zablokowanych kont utworzonych w 2020 r. lub później\n227,030Zablokowane konta utworzone w 2024 r. — rok szczytowy\n51,701Spadek w 2021 r., pomiędzy dwoma latami szczytowymi — niewyjaśniony\n2003→2026Dane obejmują cały okres, ale dane dotyczące masy dotyczą ostatnich sześciu lat\n\nData powstania to GetPlayerSummaries dla podzbioru zablokowanych kont, po usunięciu duplikatów na podstawie identyfikatora SteamID64. Data utworzenia to data założenia konta, a nie data zablokowania ani rozpoczęcia „farmowania”; jest ona tutaj traktowana jako dowód na to, jak niedawno powstała ta populacja, a nie jako dowód zamiaru. Trzy rzeczy, których wykres nie pokazuje:\n\nTrend po 2024 roku. Konto założone w 2025 lub 2026 roku miało mniej czasu na zebranie blokady, a rok 2026 obejmuje dziewięć miesięcy — więc 227,030 → 121,070 → 16,534 oznacza cenzurę, a nie spadek.\nWskaźnik zakazów. Dane dotyczące lat utworzenia uwzględniono wyłącznie dla zablokowanych kont, więc nie ma mianownika. Już sam wzrost liczby użytkowników dałby taki wykres.\nDlaczego rok 2021 okazał się porażką. 51,701 znajduje się pomiędzy 105,821 a 104,641, poniżej połowy wysokości każdego z sąsiadów. Nie ma na to żadnego publicznego wyjaśnienia; pozostawiono to widoczne, zamiast wygładzać.\n04 — Czas\nGdy Valve wchodzi w życie, ma to miejsce w ciągu pierwszego roku\n\nOczywistym argumentem przemawiającym za pozostawieniem 88.97% bez zmian jest zaległość. Datowane zakazy wskazują jednak na coś innego.\n\nIle czasu upłynęło od założenia konta do momentu nałożenia blokady\n\nWiek konta w momencie nałożenia blokady – w przypadku 293,750 zablokowanych kont, dla których znana jest zarówno data utworzenia, jak i data ostatniej blokady. Ponad połowa z nich została wykryta w ciągu pierwszego roku.\n\n0%\n10%\n20%\n30%\n40%\n<6 mo\n33.7%\n6–12 mo\n21.5%\n1–2 y\n20.6%\n2–5 y\n14.3%\n5 y+\n10.0%\n55.1% inside the first year\nZablokowano w ciągu pierwszego roku — 55.1%Zablokowano później — 44.9%\n0,80 yMediana wieku konta w momencie nałożenia blokady\n55.1%Zablokowano w ciągu pierwszego roku od założenia konta\n33.7%Zablokowany w ciągu pierwszych sześciu miesięcy\n293,750Konta, na których występują obie daty\n\nOto odpowiedź na ten oczywisty argument. Jeśli 88.97% floty pozostaje nietknięta, ponieważ egzekwowanie przepisów przebiega po prostu powoli — zaległości są stopniowo nadrabiane — to zakazy, które zrobić można by się spodziewać, że dane będą przestarzałe. Jest jednak odwrotnie: mediana wieku zablokowanych kont wynosiła ma dziewięć i pół miesiąca, a trzeci — 33.7% — został złapany w ciągu sześciu miesięcy. Kiedy Valve oddziałuje na tę populację, działa szybko. Dziewięciu na dziesięciu, którzy wciąż pozostają na wolności, nie czeka w kolejce.\n\nWiek w momencie wprowadzenia zakazu = data utworzenia od GetPlayerSummaries odjęto od daty wprowadzenia zakazu wynikającej z Liczba dni od ostatniego zablokowania, czytaj dalej 2026-09-23. Jest to obliczane tylko wtedy, gdy obecne są obie wartości: 293,750 z 1,200,011 zablokowanych kont. Pozostałe konta nie podają wartości „dni od” i są pomijane, a nie zakładane — należy więc traktować to jako kształt podzbioru z datą, a nie każdego zablokowania.\n\n05 — Na czym właściwie polega ten zakaz\nGdy Valve zadziała, nie zatrzymuje to bota\n\nSpośród tych 11%, na które nałożono jakikolwiek zakaz, sprawdź, jaki to zakaz.\n\nZakaz to nie to samo co zakaz. Spośród 1,200,011 kont, które Valve zgłosiło, 99.8% nosić społeczność zakaz — ograniczenie dotyczące forów, profili i grup, które nie ma żadnego wpływu na bota handlowego. Konto nadal może otrzymywać karty, nadal może prowadzić wymianę i nadal może przenosić zasoby. 22.2% co najmniej jeden ban za grę oraz 3.9% ban VAC; kategorie te nakładają się na siebie, więc nie sumują się. Jedyna sankcja, która faktycznie uniemożliwia handel, czyli ban ekonomiczny/handlowy, dotyczy 5,214 kont. Nie opieramy naszej argumentacji wyłącznie na tej liczbie — zakazy handlu są ogólnie rzadkością w przypadku Steam. Przesłanie tego wykresu jest prostsze: nawet ułamek Valve czy Touch nadal prowadzi działalność handlową.\n\nZa co właściwie zostali zablokowani ci 11%, którzy mają zakaz\n\nUdział każdego rodzaju blokady w ogólnej liczbie 10,880,610 zweryfikowanych użytkowników. Jedno konto może mieć więcej niż jeden rodzaj blokady. Najedź kursorem, aby wyświetlić liczby.\n\n0%\n4%\n8%\n11%\n15%\nCommunity ban\nGame ban\nVAC ban\nEconomy / trade ban\n\nZakaz typu Steam nie zawiera pola „powód”, więc żaden z tych zakazów nie jest przypisany konkretnie do farmowania kart — jest to zestawienie występujących typów zakazów wraz z informacją o tym, co faktycznie ogranicza każdy z nich. Zakaz społecznościowy nie uniemożliwia handlu; uniemożliwia go natomiast zakaz ekonomiczny / handlowy. Podsumowanie: asf-ban-census-2026-09-23.json.\n\n06 — Pozostała populacja\nOszuści Valve, chodźmy: 51,732 Pełny spis ludności\n\nDruga, niezależna lista — przypadki oszustw potwierdzone przez społeczność — zweryfikowana w oparciu o ten sam oficjalny interfejs API.\n\nGrupę osób zajmujących się automatyzacją można by uznać za nieszkodliwych próżniaków. Drugiej grupy nie da się tak potraktować. SteamRep to istniejąca od dawna społeczna baza danych reputacji; konto oznaczone jako ZABRONIONE osoba ta została uznana przez tę społeczność za oszusta na podstawie udokumentowanych dowodów przedstawionych przez ofiary oraz zapisów czatów dotyczących transakcji. Przeprowadziliśmy spis 100% wszystkich 51,732 profili oznaczonych jako „ZABLOKOWANE” w odniesieniu do oficjalnego interfejsu API serwisu Steam (ISteamUser/GetPlayerBans/v1) — i uwzględniono wyłącznie sankcje dotyczące oszustw. Zakaz typu VAC dotyczy oszukiwania za pomocą oprogramowania w grach (aimboty, wallhacki); nie ma on żadnego wpływu na inwestora i nie stanowi dowodu Valve na popełnienie oszustwa, dlatego nie jest zaliczany do działań związanych z zwalczaniem oszustw.\n\nW całym spisie kont 51,732, 67.77% — 35,059 oszustów, wobec których wydano orzeczenie — nie ma ŻADNYCH blokad związanych z oszustwami na Valve: nadal mogą prowadzić handel, wysyłać zaproszenia do znajomych do nowych ofiar oraz wysyłać wiadomości. Tylko 32.23% otrzymały blokadę dostępu do społeczności lub blokadę handlową, a blokada handlowa — jedyne działanie, które faktycznie uniemożliwia transfery przedmiotów z ekwipunku — dotyczy zaledwie 18.81% (9,731 kont). Dodatkowe 12.81% (6,627 konta) mają na koncie VAC lub blokad w grze wyłącznie z powodu oszukiwania w grze, pozostając jednocześnie całkowicie nieograniczonymi w zakresie Steam handlu.\n\nPotwierdzeni oszuści – w zależności od tego, czy Valve nałożył na nich blokadę związaną z oszustwem (pełny spis)\n\nWszystkie profile 51,732 SteamRep, które zostały zablokowane, w podziale na to, czy Valve zastosowano blokadę społecznościową czy handlową. Blokady VAC i blokady w grze nie są uwzględnione — nie dotyczą one oszustw. Najedź kursorem, aby wyświetlić liczby.\n\n0%\n18%\n35%\n53%\n70%\nNo scam-relevant ban\nCommunity or trade ban\n0%\n6%\n13%\n19%\n25%\nCommunity ban\nTrade / economy ban\nVAC (not fraud)\nGame ban\n51,732SteamRep — zweryfikowano profile zablokowane — 100% pełny spis\n35,059Nie ma na koncie żadnego blokowania związanego z oszustwami (67.77%)\n18.81%Wprowadźcie zakaz handlu, który położy kres oszustwom (9,731)\n32.23%Udział Valve spotkał się z zakazem ze strony społeczności lub branży (16,673)\n\nSteamRep to zewnętrzna baza danych reputacji, w której oceny są dokonywane przez społeczność, a nie Valve ustalenie — i o to właśnie chodzi: chodzi o dowody zewnętrzne, porównane z tym, co zrobiło samo Valve. Wszystkie 51,732 profile ZABLOKOWANE z eksportu kanonicznego zostały bezpośrednio porównane z ISteamUser/GetPlayerBans/v1. Termin „związane z oszustwem” oznacza blokadę dostępu do społeczności lub blokadę ekonomiczną/handlową; VAC (12.81%) oraz blokady w grze (3.86%) są liczone oddzielnie, ponieważ dotyczą one oszukiwania, a nie oszustw. Pełny zbiór danych z audytu: steamrep_steam_bans.csv.\n\nDwie populacje, jedno odkrycie\n\nNie chodzi tu o te same osoby ani o to samo zachowanie. W jednym przypadku mowa o dziesięciu milionach zautomatyzowanych kont, w drugim – o pięćdziesięciu trzech tysiącach oszustów, wobec których zapadły wyroki. Łączy je jedynie forma wyniku: dziewięć na dziesięć kont rolniczych pozostaje całkowicie nietkniętych, a ponad dwie trzecie (67.77%) zidentyfikowanych oszustów nie ponosi żadnych sankcji związanych z oszustwem. Blokada społecznościowa Valve jest przyznawana swobodnie i ogranicza dostęp do forów oraz profili, a nie dotyczy handlu. Przycisk zgłaszania, baza reputacji, blokada powstrzymująca oszustwo: wszystko to istnieje, ale jest niedostatecznie wykorzystywane. Porównajmy to z zarchiwizowanymi odmowami w głównym dossier, gdzie ta sama firma trwale usuwa pojedyncze konto, podając jako powód wykorzystanie komercyjne i automatyzację — klauzula ta nie jest martwa, jest celowa.\n\n07 — Brama konta $5.00 i przejęcie konta\nEmpiryczna kontrola kont typu 100,000: botnety to nie są jednorazowe, darmowe konta\n\nLogika doboru próby statystycznej i dowód matematyczny: dlaczego przyjęcie dowolnej innej wartości 100,000 daje dokładnie ten sam wynik.\n\nGłównym argumentem obrony Valve przed organami regulacyjnymi i organizacjami zajmującymi się ochroną konsumentów było twierdzenie, że zautomatyzowane oszustwa i „farming” są przeprowadzane za pomocą tymczasowych, bezpłatnych kont „jednorazowych”, które są szybko blokowane. Zgodnie z opublikowanymi zasadami Valve konto jest Ograniczona aż wyda co najmniej 5.00ów USD w sklepie Steam, co uniemożliwia mu prowadzenie transakcji, wysyłanie zaproszeń do grona znajomych oraz korzystanie z funkcji API. Zweryfikowaliśmy to twierdzenie bezpośrednio, sprawdzając status monetyzacji reprezentatywnej, rygorystycznej pod względem matematycznym próby 100,000 zablokowano Steam konta pochodzące z naszego korpusu metadanych profili 1,182,811.\n\nPROTOKÓŁ POBIERANIA PRÓBEK (SRSWOR)\n100,000 Obiektywny przekrój\n\nŹródło: N = 1,182,811 unikalnych zablokowanych Steam kont wybranych metodą prostego losowego doboru bez zwrotu przy użyciu kryptograficznie jednolitego generatora liczb losowych (PRNG). Każde konto miało identyczne prawdopodobieństwo uwzględnienia wynoszące P = n / N ≈ 8.45%, co pozwala całkowicie wyeliminować błąd przeżywalności i błąd aktywności.\n\nDOWÓD MATEMATYCZNY\nMargines błędu < ±0.4%\n\nZastosowanie wzoru na korektę dla populacji skończonej (FPC) przy wartości 99% Przedział ufności (Z = 2,576):\nMoE = Z × √[p(1-p)/n] × √[(N-n)/(N-1)] ≈ ±0.39%\n\nPOWTARZALNOŚĆ\nDlaczego każde 100 tys. daje taki sam zysk\n\nPonieważ margines błędu jest ograniczony do wartości ±0.4% przy poziomie ufności 99%, matematycznie gwarantowane jest, że każda inna niezależna próbka z konta 100,000 mieści się w przedziale 63.06% ± 0.39% (od 62.67% do 63.45%). Próba odzwierciedla całą populację osób zablokowanych, liczącą 1,18 miliona.\n\nWyniki audytu całkowicie obalają argument dotyczący „botów jednorazowego użytku”. Spośród 100,000 kont poddanych audytowi za pośrednictwem starszego interfejsu profilu XML serwisu Steam: 61,490 kont (63.06% spośród kont sklasyfikowanych) to konta bez ograniczeń (płatne), na których wydano co najmniej $5.00 na Steam. Tylko 36,021 (36.94%) to ograniczone konta bezpłatne, natomiast 2,489 to konta nieskonfigurowane lub prywatne.\n\n100,000 Zablokowane konta: płatne ($5+ wydatki w sklepie) a bezpłatne z ograniczeniami\n\nEmpiryczna kontrola 100,000 losowo wybranych zablokowanych kont. Ponad 63% z nich przeszło przez płatną bramkę finansową Valve. Najedź kursorem, aby wyświetlić liczby.\n\n0%\n16%\n33%\n49%\n65%\nNon-limited (Paid ≥ $5.00)\nLimited (Free < $5.00)\n100,000Populacja objęta badaniem (SRSWOR, N = 1,18 mln)\n63.06%Konta płatne bez ograniczeń (konta 61,490)\n±0.39%Błąd pomiaru w przedziale ufności 99%\n~745,800Liczba ekstrapolowanych płatnych kont w zbiorze 1,18 mln zablokowanych kont\nRzeczywistość strukturalna: likwidacja kont na skalę przemysłową\n\nDlaczego 63% spośród badanych zablokowanych kont miałoby stanowić konta płatne, na których wydano prawdziwe pieniądze w sklepie Valve? Operatorzy botnetów nie wydają z własnej kieszeni milionów na konta jednorazowego użytku. Stosunek ten podkreśla skalę konta, których bezpieczeństwo zostało naruszone, oraz przejęte konta krążące w ekosystemie.\n\nSkala ta jest bezpośrednio widoczna na podziemnych platformach: na rynkach takich jak FSB Market (nazwa zanonimizowana; oryginalna nazwa nie jest tu podawana), na przykład 550,000 Steam konta (logi skradzionych danych, dane przechwycone w wyniku phishingu, ataki typu credential stuffing) są w każdej chwili aktywnie wystawiane na sprzedaż (phishdestroy.io/live-intel). Platforma weryfikuje tożsamość kupujących i sprzedających za pomocą własnego identyfikatora OpenID Steam firmy Valve, a ani FSB Market ani powiązane forum jest blokowany przez filtr linków użytkownika Valve.\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\nJak stwierdzono w sekcji 06, Valve nie eliminuje z własnej inicjatywy tej oszukańczej działalności: 67.77% oszustów zidentyfikowanych przez społeczność nie ma żadnych blokad za oszustwa na Steam, a 88.97% floty automatycznej pozostaje całkowicie nietknięta. Konta poruszają się swobodnie, uwierzytelniają się za pośrednictwem oficjalnych interfejsów API i prowadzą transakcje w całym ekosystemie, ciesząc się niemal całkowitą bezkarnością.\n\nSchemat architektury dowodów kryminalistycznych i egzekwowania prawa\nInteraktywny wykres przedstawiający przepływ danych z 10,88 mln zeskanowanych kont do 100 tys. empirycznych podgrup oraz 53,5 tys. potwierdzonych oszustów · Kliknij linki, aby zapoznać się z surowymi dowodami\nPoziom 01 · Spis floty automatyzacji obejmujący 10,88 mln jednostek\nNajwiększa grupa użytkowników określających się jako automaty na Steam przechodziła kolejno przez oficjalny interfejs API blokujący Valve. Dowodzi to, że komercyjne floty botów działają na 88.97% bezkarnie, płacąc jednocześnie dziesiątki milionów w opłatach za dostęp.\n9,680,599 88.97% Aktywne i nietknięte\nKonta korzystające z oprogramowania automatycznego, które nie mają w historii żadnych blokad.\nSurowy plik JSON ze spisu ludności (1,2 KB) ↗Zapoznaj się z sekcją 01 ↗\n$26,802,495 Minimalny poziom przychodów ze sprzedaży bezpośredniej w sklepach\nZebrane przez Valve od 5,360,499 członków bez ograniczeń, którzy przekroczyli minimalny próg wejścia wynoszący $5.00.\nAudyt ekonomiczny kart ↗Valve $5 Najczęściej zadawane pytania dotyczące zasad ↗\n1,200,011 11.03% Podzbiór oznaczony flagą\n99.8% obejmuje wyłącznie kosmetyczne blokady społecznościowe; handel pozostaje otwarty na 99.95% kont.\nPodział według rodzajów blokad ↗Zablokowana baza danych (60,4 MB) ↓\nPoziom 02 · 100,000 – Audyt oparty na próbie empirycznej (N = 1,182,811)\nPrzekrój reprezentatywny SRSWOR oceniony za pomocą starszych punktów końcowych XML. Matematycznie udowodniony margines błędu < ±0.4% przy przedziale ufności 99%. Obala twierdzenie, że zablokowane boty to darmowe konta jednorazowego użytku.\n61,490 (63.06%) Konta płatne bez ograniczeń (wydatki $5+)\nPonad 63% zablokowanych kont dotyczy transakcji płatnych. Szacuje się, że w puli zablokowanych kont znajduje się około 745,800 kont płatnych (próg wejścia $3.73M+).\nOgraniczone wyniki w formacie CSV (2,1 MB) ↓Raport kryminalistyczny dotyczący 100 tys. ↗\n36,021 (36.94%) Ograniczone konta bezpłatne (< $5.00)\nNiewielka część zablokowanych profili odpowiadała opisowi „jednorazowego bota” podanemu przez Valve. Konta 2,489 były niekonfigurowane lub prywatne.\nPróbka w formacie CSV zawierająca 100 tys. wierszy (8,5 MB) ↓Analiza wydatków MD ↗\n34.67% kontra 63.93% Audyt oczyszczania profili\nValve usunęło pseudonimy, zastępując je surowymi identyfikatorami SteamID64 na 34,673 kontach, ale pozostawiło nazwy użytkownika i awatary całkowicie bez zmian na 63,928 zablokowanych kontach.\nSekcja ds. dezynfekcji ↗Przegląd planu działania ↗\n34.59% Dziedzictwo Konta z dawnych lat (utworzone w latach 2003–2019)\nPonad jedna trzecia zablokowanych kont została zarejestrowana od 5 do ponad 20 lat temu, co świadczy o przejmowaniu kont długoletnich graczy Steam na skalę przemysłową.\nChronologia wiekowa ↗Odmowy udzielenia wsparcia ↗\nPoziom 03 · 51,732 SteamRep Spis potwierdzonych oszustów\nPełny 100% spis oszustów osądzonych przez społeczność, zawierający logi rozmów z ofiarami oraz dowody transakcji, zweryfikowany na podstawie oficjalnych Steam interfejsów API dotyczących blokad. Dowodzi to systemowej porażki organów egzekwujących prawo.\n35,059 (67.77%) Zero blokad za oszustwa (całkowita bezkarność)\nPonad dwie trzecie zweryfikowanych oszustów nie ma na koncie żadnych zakazów dotyczących społeczności ani handlu od Valve. Są w pełni gotowi do prowadzenia handlu i pozyskiwania kolejnych ofiar.\nSteamRep Zakazy dotyczące API (2,6 MB) ↓SteamRep Raport z audytu ↗\n9,731 (18.81%) Gospodarka / Embargo handlowe\nJedyna sankcja, która uniemożliwia likwidację zapasów. Stosowana wobec mniej niż jednej piątej potwierdzonych oszustów.\nSteamRep Źródło (2,1 MB) ↓Zapoznaj się z sekcją 06 ↗\n6,627 (12.81%) Nieuzasadnione blokady za oszukiwanie (tylko VAC)\nZablokowani za używanie aimbotów i wallhacków w grach, podczas gdy ich funkcje handlu Steam i phishingu pozostają 100% aktywne.\nVAC Analiza nieistotności ↗Kalendarium bezpieczeństwa ↗\nPoziom 04 · Ataki na strony wiki i naruszenia bezpieczeństwa infrastruktury w sierpniu 2026 r.\nW pakiecie dowodowym odnotowano przypadki manipulacji wewnętrzną dokumentacją programistów, ograniczania dostępu redaktorów społecznościowych oraz awarie zabezpieczeń obwodowych.\n1,200+ Redakcja Dzienniki konfliktów VDC Wiki\nRedaktorzy społecznościowi, którzy próbowali usuwać linki phishingowe i szablony spamu, byli systematycznie blokowani przez automatyczne filtry, podczas gdy pracownicy Valve ignorowali ostrzeżenia.\nRaport dotyczący konfliktów w Rosji (127 KB) ↗Raport klasyfikacyjny (66 KB) ↗\n12 TB bez uwierzytelniania Sierpień 2026 r. Wyciek zasobów (CWE-284)\nValve przez kilka tygodni udostępniało 12 terabajtów wewnętrznego kodu i prototypowych kompilacji na publicznym punkcie końcowym bez uwierzytelniania.\nValve Dokumentacja dotycząca niekompetencji (43 KB) ↗Archiwum dowodów ↗\nNaruszenie bezpieczeństwa w firmie CEVA Logistics Sierpień 2026 r. – wyciek danych osobowych klientów\nNazwiska, adresy i numery telefonów europejskich nabywców Steam Deck wyciekły od partnera logistycznego firmy Valve, co wywołało falę ataków phishingowych.\nRejestr zdarzeń ↗Rejestr egzekucji ↗\n\nArtefakt próbkowania: banned_100k_slice.csv (100,000 rachunków). Wyniki audytu: slice_100k_limited_results.csv. Pełny raport analityczny: BANNED_100K_FORENSIC_ANALYSIS.md.\n\n08 — Metoda i ograniczenia\nJak to zostało zinterpretowane i czego nie sugeruje ten tekst\n\nTrzy populacje ogólnodostępne, jeden publiczny interfejs API, rygorystyczne statystyczne pobieranie próbek.\n\nREALIZACJA I UPRAWNENIA\n\nSpis ASF, czyli 100,000-konto SRSWOR oraz SteamRep weryfikacja krzyżowa zostały przeprowadzone przez PhishDestroy uczestników przy użyciu ich własnych Steam kont i kluczy Web API, w ramach publicznych działań Koalicji mających na celu zwalczanie phishingu i oszustw. Autor niniejszego dossier nie posiada żadnego Steam klucza Web API i osobiście nie przeprowadził żadnego skanowania na żywo. Agregacja, haszowanie, weryfikacja i publikacja zostały przeprowadzone na podstawie wyników uzyskanych przez uczestników.\n\nLudność\tSkąd to się wzięło\tCo zostało przeczytane\nCzłonkowie ASF\n10,880,610\tPubliczna lista członków grupy społecznościowej ArchiSteamFarm Steam. Strona grupy Steam wyświetla 5,360,499 członków (tylko konta z nieograniczonym dostępem); lista członków zwrócona przez API zawierała łącznie 10,880,610 wpisów, w tym konta z ograniczonym dostępem. Użytkownik jest automatycznie dodawany do grupy przy pierwszym uruchomieniu, chyba że wyraźnie wyłączy domyślne ustawienie dołączania do grupy w konfiguracji (AutoJoinSteamGroup / Statystyki), co oznacza, że lista członków obejmuje komercyjne klastry botów, osoby korzystające z kart w trybie bezczynności oraz zwykłych graczy, którzy pozostawili włączoną opcję domyślną.\tGetPlayerBans dla każdego członka (flagi blokady); GetPlayerSummaries według daty utworzenia i kraju. Zgrupowane po 100 identyfikatorów, z usunięciem duplikatów na podstawie SteamID64.\n100 tys. zablokowanych kont SRSWOR Slice\n100,000\tPrzedstawicielska próba pobrana metodą losowania równomiernego bez zwrotu z zbioru 1,182,811 zablokowanych kont ($P = 8,45\\%$). Korekta dla populacji skończonej daje margines błędu wynoszący $\\pm 0,39\\%$ przy poziomie ufności 99% ($Z = 2,576$).\tMonetyzacja i status konta z ograniczeniami (isLimitedAccount) sprawdzane za pomocą starszego interfejsu profilu XML serwisu Steam (?xml=1) za pośrednictwem rozproszonych potoków proxy. Potwierdza status płatności 63.06%.\nSteamRep oszuści\n51,732\tPrzeprowadzono 100% pełną analizę wszystkich profili oznaczonych jako „ZABLOKOWANE” w SteamRep bazie danych reputacji społeczności (łącznie 51,732 profili). Nie zastosowano żadnego doboru próby ani filtrowania.\tISteamUser/GetPlayerBans/v1 dla wszystkich kont oznaczonych jako 51,732, w zestawieniu krzyżowym ze statusem SteamRep. Potwierdza, że 67.77% nie podlega żadnym blokadom związanym z oszustwami.\nPrzedmiot wynalazku\n\nWyłącznie wskaźniki empiryczne i oszacowania ograniczone statystycznie. W populacji automatyzacji 88.97% nie podlegają blokadzie; podzbiór zablokowanych kont skupia się w ostatnim okresie (70% od 2020 r.). W empirycznej kontroli kont 100,000 63.06% zablokowanych kont to konta płatne (nieograniczone), przy matematycznie udowodnionym marginesie błędu poniżej ±0.4%. Spośród 51,732 potwierdzonych oszustów 67.77% nie ma blokady związanej z oszustwem. Każda liczba jest możliwa do odtworzenia za pomocą własnego interfejsu API serwisu Valve.\n\nCzego nie obejmuje niniejszy zastrzeżenie\n\nZakaz typu Steam nie zawiera pola „powód”, więc żaden z tych zakazów nie jest przypisany do konkretnej przyczyny. Przynależność do grupy nie stanowi dowodu na to, że konto jest zautomatyzowanym botem: ponieważ ASF domyślnie umożliwia dołączanie do grup, o ile opcja ta nie zostanie ręcznie odznaczona, w populacji tej mieszają się komercyjne farmy wielokontowe z kontami osobistymi zwykłych graczy i hobbystów. Kraj jest podawany na podstawie własnych informacji, a wpis oznaczony symbolem SteamRep stanowi orzeczenie społeczności, a nie wyrok sądowy. Nie podaje się nazwisk poszczególnych osób.\n\nDlaczego to ma znaczenie\n\nValve korzysta z tego samego interfejsu API, posiada własną bazę danych oraz informacje o przyczynach zablokowania, których to skanowanie nie jest w stanie wykryć. Jest w stanie wykonać to zapytanie w całej przestrzeni identyfikatorów w ciągu kilku sekund. Wskaźnik, który pozwala podmiotowi zewnętrznemu zweryfikować twierdzenie dotyczące egzekwowania przepisów w odniesieniu do danego numeru, nigdy nie został opublikowany przez jedyną stronę, która jest w stanie go przedstawić z pełną dokładnością. Jest to zewnętrzne oszacowanie, podane po to, aby można było sformułować pytanie wraz z podaną liczbą.\n\nCzytaj dalej: gospodarka oparta na kartach, którą prowadzi ta populacja → · wsparcie w zakresie dostępu i kradzieży → · pełna dokumentacja →",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Jak duża jest farma na Steam? Policzyliśmy ją sami."
          },
          {
            "level": 2,
            "id": null,
            "text": "Dziesięć milionów kont, z czego dziewięć na dziesięć pozostało nietkniętych"
          },
          {
            "level": 3,
            "id": null,
            "text": "ASF dołącza do grupy specjalnie dla Ciebie"
          },
          {
            "level": 3,
            "id": null,
            "text": "10,880,610 łączna liczba wpisów"
          },
          {
            "level": 3,
            "id": null,
            "text": "88.97% wyczyść"
          },
          {
            "level": 3,
            "id": null,
            "text": "Spośród 10,880,610 kont, ile z nich Valve zostało wykorzystanych"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ile ta flota już zapłaciła za swoje istnienie Valve"
          },
          {
            "level": 2,
            "id": null,
            "text": "Gdzie stacjonuje flota"
          },
          {
            "level": 3,
            "id": null,
            "text": "Zablokowane konta według podanego kraju"
          },
          {
            "level": 2,
            "id": null,
            "text": "Najnowsze transakcje, a nie zaległości z poprzednich okresów"
          },
          {
            "level": 3,
            "id": null,
            "text": "Kiedy utworzono zablokowane konta"
          },
          {
            "level": 2,
            "id": null,
            "text": "Gdy Valve wchodzi w życie, ma to miejsce w ciągu pierwszego roku"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ile czasu upłynęło od założenia konta do momentu nałożenia blokady"
          },
          {
            "level": 2,
            "id": null,
            "text": "Gdy Valve zadziała, nie zatrzymuje to bota"
          },
          {
            "level": 3,
            "id": null,
            "text": "Za co właściwie zostali zablokowani ci 11%, którzy mają zakaz"
          },
          {
            "level": 2,
            "id": null,
            "text": "Oszuści Valve, chodźmy: 51,732 Pełny spis ludności"
          },
          {
            "level": 3,
            "id": null,
            "text": "Potwierdzeni oszuści – w zależności od tego, czy Valve nałożył na nich blokadę związaną z oszustwem (pełny spis)"
          },
          {
            "level": 4,
            "id": null,
            "text": "Dwie populacje, jedno odkrycie"
          },
          {
            "level": 2,
            "id": null,
            "text": "Empiryczna kontrola kont typu 100,000: botnety to nie są jednorazowe, darmowe konta"
          },
          {
            "level": 3,
            "id": null,
            "text": "100,000 Obiektywny przekrój"
          },
          {
            "level": 3,
            "id": null,
            "text": "Margines błędu < ±0.4%"
          },
          {
            "level": 3,
            "id": null,
            "text": "Dlaczego każde 100 tys. daje taki sam zysk"
          },
          {
            "level": 3,
            "id": null,
            "text": "100,000 Zablokowane konta: płatne ($5+ wydatki w sklepie) a bezpłatne z ograniczeniami"
          },
          {
            "level": 3,
            "id": null,
            "text": "Rzeczywistość strukturalna: likwidacja kont na skalę przemysłową"
          },
          {
            "level": 2,
            "id": null,
            "text": "Jak to zostało zinterpretowane i czego nie sugeruje ten tekst"
          },
          {
            "level": 3,
            "id": null,
            "text": "Przedmiot wynalazku"
          },
          {
            "level": 3,
            "id": null,
            "text": "Czego nie obejmuje niniejszy zastrzeżenie"
          },
          {
            "level": 3,
            "id": null,
            "text": "Dlaczego to ma znaczenie"
          }
        ],
        "links": [
          "https://help.steampowered.com/en/faqs/view/71D3-35C2-AD96-AA3A",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/asf-ban-census-2026-09-23.json",
          "https://phishdestroy.io/steam_dossier/pl/VALVE_EVIDENCE_PACK/databases/steamrep_steam_bans.csv",
          "https://phishdestroy.io/live-intel/?category=steam",
          "https://phishdestroy.io/steam_dossier/pl/#proxy-bypass-explainer",
          "https://phishdestroy.io/steam_dossier/pl/card_economy.html",
          "https://phishdestroy.io/steam_dossier/pl/VALVE_EVIDENCE_PACK/databases/banned_archiasf_massive.csv",
          "https://phishdestroy.io/steam_dossier/pl/VALVE_EVIDENCE_PACK/databases/slice_100k_limited_results.csv",
          "https://phishdestroy.io/steam_dossier/pl/VALVE_EVIDENCE_PACK/reports/BANNED_100K_FORENSIC_ANALYSIS.md",
          "https://phishdestroy.io/steam_dossier/pl/VALVE_EVIDENCE_PACK/databases/banned_100k_slice.csv",
          "https://phishdestroy.io/steam_dossier/pl/VALVE_EVIDENCE_PACK/reports/STEAM_BANNED_LIMIT_ANALYSIS.md",
          "https://phishdestroy.io/steam_dossier/pl/VALVE_EVIDENCE_PACK/INVESTIGATION_OVERVIEW.md",
          "https://phishdestroy.io/steam_dossier/pl/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/pl/VALVE_EVIDENCE_PACK/reports/STEAMREP_VS_STEAM_AUDIT.md",
          "https://phishdestroy.io/steam_dossier/pl/VALVE_EVIDENCE_PACK/databases/SteamRep_Profiles_BannedCaution_2024.csv",
          "https://phishdestroy.io/steam_dossier/pl/security_timeline.html",
          "https://phishdestroy.io/steam_dossier/pl/VALVE_EVIDENCE_PACK/reports/russian_conflicts_report.json",
          "https://phishdestroy.io/steam_dossier/pl/VALVE_EVIDENCE_PACK/reports/classification_report.json",
          "https://phishdestroy.io/steam_dossier/pl/VALVE_EVIDENCE_PACK/reports/VALVE_INCOMPETENCE_REPORT.md",
          "https://phishdestroy.io/steam_dossier/pl/steam_evidence_archive.html",
          "https://phishdestroy.io/steam_dossier/pl/steam_enforcement_evidence.html",
          "https://phishdestroy.io/steam_dossier/pl/#insider-threat",
          "https://phishdestroy.io/steam_dossier/pl/"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/pl/enforcement_audit.content.json",
      "export_json_sha256": "90218185af8e7204bfe3da62aeb5be0d5cb18558d14c66de058e9583f8b44d62"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "pl/index.html",
      "language": "pl",
      "title": "Dossier „Steam”: zasady, trasy i odpowiedzialność",
      "source_url": "https://phishdestroy.io/steam_dossier/pl/index",
      "source_html_sha256": "7ad6c5e8116ad582eab6a39673cde7329f05052d22ff1eda40eff590e1e9db1b",
      "exported_at": "2026-09-29T00:19:00.040Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "exhibit-gallery-section",
            "source": "https://phishdestroy.io/steam_dossier/pl/index#exhibit-gallery-section"
          }
        ],
        "raster_images_replaced": 2
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "index.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/pl/index.pdf?v=print-20260929-v5",
        "sha256": "ceea8d42b34fb56cf799f89296ad79bb56c32a0107fcadf67f8a7ffbe6cb4d26",
        "bytes": 1005755,
        "pages": 113
      },
      "integrity": {
        "signed_object": "index.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "index.content.json.asc",
        "digest_file": "index.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify index.content.json.asc index.content.json",
          "sha256sum -c index.content.json.sha256"
        ]
      },
      "content": {
        "text": "Sekcja 1 — Omówienie sprawy\nZasada. Rekord. Pytania bez odpowiedzi.\nOgraniczenia dotyczące kontekstu i źródła\n\nSześć ustaleń, z których każde odnosi się do opatrzonego datą dokumentu publicznego. Poszczególne sekcje mają następującą kolejność: dokumentacja techniczna (część A), przepisy i dokumentacja dotycząca egzekwowania prawa (część B), ramy prawne (część C), a następnie załączniki zawierające główne dowody rzeczowe.\n\nSześć ustaleń. Każde z nich łączy zapisany przepis z dokumentacją opatrzoną datą oraz pytaniem, na które dowody mogą udzielić odpowiedzi.\n\n1. Hosty uwierzytelniające w oddzielnych domenach — 44 trasy · 26 par podzielonych\n\nRejestr osób aktywnych zawodowo zawiera 44 platformy uwierzytelniające się za pośrednictwem oddzielnej domeny, którą można zarejestrować. Pięć kolejnych tras oczekuje na weryfikację i przydzielenie daty RDAP; ich uwzględnienie zwiększyłoby łączną liczbę do 47. Nie są one uwzględnione w liczbie 44 ani w tabeli wiekowej. — 27 wraz z opublikowanym plikiem dowodowym dla każdej trasy oraz 17 dodanych na podstawie ręcznego zebrania danych, wymienionych osobno. W 26 par z podziałem na filtry główną domeną jest ZABLOKOWANE w filtrze linków Steam, podczas gdy serwer proxy obsługujący dane logowania nie jest. Nie są to domeny jednorazowe: csgogem.com jest zablokowany, podczas gdy api.csgem.com, serwer o nazwie Steam, jest zarejestrowany od marca 2014 r. — 12 lat i 6 miesięcy. Valve odbiera tę nazwę hosta w każdym żądaniu OpenID i wyświetla ją użytkownikowi na własnej stronie logowania. Pełna tabela, wiek połączeń dla poszczególnych tras oraz informacje o źródłach znajdują się w sekcji 3.\n\nPodążaj trasą →\n2. 2016 r.: nadano nazwę mechanizmowi i wyznaczono termin\n\nW dniu 13 lipca 2016 r. Valve opisał publicznie, w jaki sposób serwisy hazardowe wykorzystywały Steam OpenID oraz zautomatyzowane konta handlowe, a zawiadomienia jego pełnomocnika z dnia 20 lipca 2016 r. wyznaczyły dziesięciodniowy termin. Od tego czasu nie opublikowano żadnych danych dotyczących egzekwowania przepisów w odniesieniu do poszczególnych operatorów. Dziesięć lat po wyznaczeniu tego terminu ten sam mechanizm jest nadal stosowany na serwerach uwierzytelniających w oddzielnych domenach, które nie zwróciły żadnego blokady filtru linków na stronie 2026-09-21.\n\nPrzeczytaj list otwarty skierowany do WSGC →\n3. Korelacja urządzeń, na papierze firmowym adwokata\n\nW zamieszczonej tutaj korespondencji pełnomocnik Valve opisał korelację na poziomie urządzeń, łączącą jedno urządzenie z wieloma kontami — funkcję, o której dział pomocy technicznej Steam wcześniej informował użytkowników, że nie jest technicznie możliwa. Otwartą kwestią pozostaje, jakie dane dotyczące urządzeń posiada Valve oraz na jakiej podstawie odmawia się posiadaczom kont dostępu do nich.\n\nPrzeczytaj memorandum →\n4. Dwie reakcje dotyczące dostępu. W jednym przypadku dane nie zostały ujawnione, w drugim – doszło do ich wycieku.\n\nPaździernik 2025 r.: Pełnomocnik Valve odpowiedział na wniosek złożony na podstawie art. 15, przedkładając 830-stronicowy załącznik, w którym nieusunięte fragmenty tekstu zostały zamalowane — 902,270 znaków ujawnić dane przy użyciu standardowego narzędzia do ekstrakcji, w tym identyfikatory stron trzecich, których ujawnienie miały uniemożliwić te ograniczenia. Artykuł 15 ust. 4 stanowi podstawę istnienia tych ograniczeń. Wrzesień 2026 r.: Zgłoszenie HT-2YBP-F7JP-D4VB zostało zamknięte po trzech dniach wraz z linkiem do strony samoobsługowej „Dane konta” — bez podania danych i podstawy prawnej. W momencie publikacji nie upłynął jeszcze miesięczny termin określony w art. 12 ust. 3; zastrzeżenie dotyczy treści zgłoszenia.\n\nPrzeczytaj wynik kontroli redakcyjnej →Przeczytaj zapis zgłoszenia →\n5. Rynek powyżej pułapu Steam\n\nSteam ogranicza wycenę spółki notowanej na giełdzie do około $1,800. Na pięciu platformach handlowych w nieaktualnym zrzucie ekranu (z dnia 23 września 2026 r.), 248 kategorii produktów CS2 ceny dwóch lub więcej z nich niezależnie od siebie przekraczają ten pułap, oraz wszystkie 248 są nieobecne w Steam; cena nowego egzemplarza gry „Dragon Lore” zaczyna się od $10,941 w 389 egzemplarzach wymienionych we wszystkich pięciu (dane dotyczące wyłącznie CSFloat w sekcji 13, pochodzące z migawki z 20 września, wynoszą $10,623.95 w 62 ofertach). Sprzedaż po tych cenach wymaga zewnętrznej platformy, podczas gdy transfer przedmiotów nadal odbywa się po cenie Steam.\n\nŚledź cenę i dokonaj przelewu →\n6. Zasada jest jasno sformułowana; ścieżka audytu nie jest\n\nUmowa abonamentowa zastrzega Steam na cele osobiste, niekomercyjne, zabrania komercyjnego wykorzystywania serwisu z wyjątkiem przypadków wyraźnie dozwolonych, zakazuje stosowania skryptów i botów oraz zezwala na zamknięcie konta. W 2016 r. Valve zastosowało te postanowienia wobec operatorów gier hazardowych. Osobno, zgodnie z informacjami z konta inżynieryjnego CSFloat, Valve zostało zamknięte IEconItems_730/GetPlayerItems w 2017 r., co spowodowało wyłączenie publicznego dostępu do oryginalnych identyfikatorów elementów (nie znaleziono dziennika zmian Valve).\n\nUmieść regułę obok sieci →\n2016 / Pisemne wezwanie 10 dni\nTermin określony w zawiadomieniach adwokata z lipca 2016 r. skierowanych do serwisów hazardowych. List otwarty do WSGC: sekcja 2.\n2017 / Publiczna historia audytowa Dostęp za pomocą identyfikatora został zablokowany\nCSFloat rejestruje utratę oryginalnych identyfikatorów elementów.\nKorespondencja z prawnikiem Korelacja urządzeń\nJedno urządzenie powiązane z dziesiątkami skradzionych kont.\nRejestr tras Zablokowano, a mimo to nadal próbuję się zalogować\nZasada: Oświadczenie Valve z 2016 r. zabrania prowadzenia działalności hazardowej w ramach OpenID Steam. Zapis: W filtrze linków znajduje się 26 głównych domen, a serwer obsługujący login Steam każdej z nich działa od — serwer csgogem.com działa już od 12 lat i 6 miesięcy.\nSekcja 2 — List otwarty\nList otwarty do Komisji ds. Hazardu stanu Waszyngton\n\nDziesięć dni zamieniło się w dziesięć lat. Na pytanie skierowane przez Komisję w 2016 r. do Valve nie udzielono odpowiedzi w postaci danych dotyczących poszczególnych operatorów; w niniejszym piśmie zwraca się do niej o ponowne otwarcie sprawy.\n\nOGŁOSZENIE PUBLICZNE · KOMISJA DS. HAZARDU STANU WASZYNGTON\n\nDziesięć dni zamieniło się w dziesięć lat.Otwórz ponownie rekord.\n\nDo Komisji ds. Gier Hazardowych stanu Waszyngton:\n\nW 2016 roku dyrektor David Trujillo zwrócił się do Valve z prośbą o przedstawienie działań podjętych w celu powstrzymania wykorzystywania skórek Steam do celów hazardowych. Ówczesny przewodniczący Chris Stearns wraz z Komisją zmierzyli się z branżą opartą na przedmiotach wydawanych przez Valve oraz transferach Steam. Obaj mężczyźni opuścili już swoje stanowiska w Komisji. Pytanie, które zadali Valve, pozostaje nadal aktualne.\n\nGłówny radca prawny Valve, Karl Quackenbush, dał operatorom gier hazardowych dziesięć dni na zaprzestanie komercyjnego wykorzystywania kont Steam. W październikowej odpowiedzi skierowanej do Komisji firma Valve zaprzeczyła, jakoby ułatwiała prowadzenie hazardu, poinformowała, że wysłała wezwania do zaprzestania działalności do ponad czterdziestu serwisów oraz że zablokowała powiązane z nimi konta. Broniła również utrzymania usług handlowych Steam oraz OpenID, argumentując, że przynoszą one korzyści klientom i twórcom gier. To było przejawem przejęcia kontroli. Należy to poddać weryfikacji, a nie traktować z nadmiernym szacunkiem.\n\nW naszej ocenie odpowiedź firmy Valve nie wykazała, że wybrane przez nią środki egzekwowania były adekwatne do skali opisywanej przez nią sieci. List z groźbą skierowany do operatora to nie to samo, co trwałe zablokowanie kont Steam, infrastruktury handlowej i ścieżek uwierzytelniania, które umożliwiają funkcjonowanie tej działalności. Według podawanych szacunków W samym serwisie CS:GO Lounge obroty z zakładów w 2016 roku przekroczyły $1 miliardów; jest to zewnętrzna szacunkowa wartość zakładów, a nie przychody rzędu Valve, a pierwotna działalność serwisu polegająca na zakładach dotyczących wyglądu została później zamknięta. Skala tego zjawiska sprawiła, że konieczne stało się podjęcie weryfikowalnych działań egzekucyjnych.\n\nDzisiaj, autorstwa Valve Umowa abonamentowa zarchiwizowano 2026-09-21 ↗ ogranicza komercyjne wykorzystanie, z wyjątkiem przypadków wyraźnie dozwolonych, oraz oddzielnie zakazuje określonych form automatyzacji. Nasze przestarzały rejestr tras rekordy, w których zadeklarowano hosty zwracające identyfikatory OpenID dla usług zewnętrznych; openid.realm oraz openid.return_to to pola przekazywane do Steam, a nie tajemnice przed nim ukrywane. Nasze Sprawdzanie filtrów linków przedstawia przypadki, w których wydano ostrzeżenie dotyczące głównego adresu, ale nie dotyczyło to powiązanego hosta logowania. Sam wynik filtrowania nie może stanowić dowodu na to, że Valve zezwolił na logowanie ani że konkretny bot ominął blokadę konta. To rzeczywiście dowodzi, że ostrzeżenie zamieszczone na stronie głównej nie może stanowić wyczerpującej odpowiedzi w kwestii dostępności.\n\nRównież istnienie użytecznych, zgodnych z prawem funkcji handlowych Steam i funkcji OpenID nie pozwala ustalić, czy operatorzy objęci zakazem zostali faktycznie wykluczeni. Własne zasady Valve dopuszczają wyraźne wyjątki. Jeśli Valve opiera się na tym rozróżnieniu, Komisja powinna zwrócić się do niego o wskazanie zezwoleń, mechanizmów kontroli kont oraz kryteriów egzekwowania przepisów mających zastosowanie do komercyjnych przedsiębiorstw zajmujących się skórkami, a także konkretnych zastosowań niezwiązanych z hazardem, na które powołał się w 2016 r. Sama możliwość legalnego wykorzystania nie stanowi odpowiedzi na udokumentowane przypadki zabronionego wykorzystania.\n\nZwracamy się do Komisji o ponowne przeanalizowanie akt z 2016 roku i o przedstawienie szczegółowych informacji w podziale na poszczególnych operatorów: które konta Steam i boty handlowe zostały zablokowane po upływie dziesięciodniowego okresu wypowiedzenia; czy monitorowano powiązane konta lub serwery powrotne; którzy operatorzy odzyskali później dostęp; jakie zwolnienia zostały przyznane; oraz jakie dokumenty potwierdzają oświadczenie Valve złożone przed Komisją. Należy opublikować te dokumenty, do których wglądu uprawnia prawo. Należy porównać te dokumenty z aktualnymi trasami oraz z późniejszymi interwencjami Valve, w tym OPSkins w 2018 roku zarchiwizowano 2026-03-07 ↗.\n\nW zawiadomieniu wyznaczono dziesięciodniowy termin w lipcu 2016 r.; dziesięć lat to wystarczająco długi okres, aby ustalić, czy zadanie zostało zrealizowane. Komisja powinna zweryfikować sprawozdanie Valve z 2016 r. w oparciu o infrastrukturę, którą można dziś zaobserwować.\n\nDochodzenie w sprawie „Steam Dossier” · Oświadczenie publiczne z dnia 20 września 2026 r.\n\nKomunikat Komisji z 2016 r. ↗ zarchiwizowane 2026-05-20 ↗ · Odpowiedź Valve z 2016 r. (kopia dokumentu) ↗ · Oświadczenie Valve dotyczące OpenID z 2016 r. ↗ zarchiwizowano 2026-09-21 ↗ · Obecna umowa Steam ↗ zarchiwizowano 2026-09-21 ↗ · Kalendarium wymiany w 2016 roku: Sekcja 11 →\n\nCzęść A — Dokumentacja techniczna · Sekcja 3\nStrona jest zablokowana. Trasa logowania nie jest zablokowana.\n\n26 zablokowanych domen głównych. Serwer proxy uwierzytelniający działający za każdą z nich oraz czas jej działania. Te odrębne hosty uwierzytelniające nie są przypadkowymi dodatkowymi adresami — każdy z nich jest serwer proxy uwierzytelniający dla Steam, znajdujący się pomiędzy platformą a punktem końcowym OpenID serwisu Valve i obsługujący logowanie, którego zablokowana domena nie może już przeprowadzać w sposób jawny. Valve umieścił „drzwi wejściowe” w filtrze Link Filter. Logowanie nadal odbywało się za pośrednictwem serwera proxy: csgogem.com jest zablokowany, a api.csgem.com jest zarejestrowana od marca 2014 r. — dwanaście i pół roku. Każdego z tych dni serwer wysyłał swoją nazwę hosta do punktu końcowego OpenID użytkownika Valve, a Steam natychmiast wyświetlał ją użytkownikowi na stronie logowania. Valve to magistrala, przez którą przebiega każda z tych tras; nie musi ich wyszukiwać. Właśnie to mierzy ta sekcja: nie to, czy istnieje ostrzeżenie, ale przez ile lat trasa za ostrzeżeniem pozostaje otwarta. W rejestrze figuruje 44 tras o odrębnych domenach, z czego 27 posiada opublikowany plik dowodowy dla każdej trasy — patrz tabela poniżej. Zapoznaj się z jednym przykładem, a następnie sprawdź je wszystkie.\n\nRysunek 3.1 — Dwie trasy na mapie.\n\nJedna platforma, jeden użytkownik, dwa żądania wysyłane z tej samej przeglądarki. Filtr linków Valve działa w obu przypadkach. Blokuje to żądanie, które zawiera link, a przepuszcza to, które zawiera dane logowania. Wszystkie pomiary przedstawione w tej sekcji dotyczą czasu, przez jaki dolna trasa pozostaje otwarta.\n\nThe player\none browser, one session\nrollbit.com\nthe platform's main domain\nrbsnin.com\nseparate authentication host\nLINK FILTER\n✕ BLOCKED\nLINK FILTER\n✓ CLEAN\nsteamcommunity.com\nOpenID endpoint · signs in\nno route\nLink opublikowany w Steam — wstrzymanoProśba o logowanie — przepustkiZachowane czeki z 19 i 21 września 2026 r.\n\nOba żądania są widoczne dla Valve, a realizowane jest tylko jedno z nich. Filtr Linków to lista Valve, sprawdzana przez usługę Valve. Żądanie OpenID przekazuje nazwę hosta uwierzytelniającego do punktu końcowego Valve, który wyświetla ją bezpośrednio na stronie logowania. Nazwa hosta i tak znajduje się w żądaniu — różnica polega na tym, czy jest ona w jakiś sposób wykorzystywana.\n\nJedna platforma. Dwie różne trasy.ROLLBIT / ZAPISANE OBSERWACJE\nKrok 5 / 5\n\nŻądanie osiąga wartość Steam. Zaobserwowana ścieżka prowadziła do formularza logowania serwisu Steam. Autorzy nie zakończyli procesu logowania. Zablokowanie linku do domeny głównej nie zablokowało tej zaobserwowanej ścieżki prowadzącej do formularza.\n\n01 SPRAWDZANIE FILTRA ŁĄCZA\nMIEJSCE PRZEZNACZENIArollbit.comGłówna domena platformy\nFILTR STEAM LINKSprawdza linkOddzielny system ostrzegania o miejscu docelowym\nZAPISANY WYNIKLink zablokowany19 i 21 września 2026 r.\n02 OBSERWOWANA TRASA LOGOWANIA\nNA PERONIEZaloguj się za pomocą SteamPlatforma wysyła żądanie OpenID\nODRĘBNY SERWER AUTENTYFIKACJIrbsnin.comW zapisanej kontroli nie ma bloku „Filtr linków”\nSTEAMWyświetlono formularz logowaniaWymagany serwer pojawia się w komunikacie użytkownika Steam\nNależy sprawdzić oryginalne notatki z badania, datę rejestracji oraz szczegóły protokołu\nJak wygląda egzekwowanie przepisów dotyczących Valve'\nDomena główna: zablokowana\nUżytkownik\n→\nrollbit.com\n(domena główna)\n↓\nFILTR ŁĄCZA STEAM — ZABLOKOWANY\n„Link zablokowany!” — oznaczony jako potencjalnie złośliwy\nWitryna rollbit.com zgłosiła blokadę filtru linków dla 2026-09-19 i 2026-09-21 (sprawdzenie bez uwierzytelnienia; zapisano surowy kod HTML i skrót SHA-256). Widoczny, podlegający audytowi zapis.\nJak to właściwie wygląda — uwierzytelnianie\nSerwer autoryzacji: nie zablokowany\nUżytkownik\n→\nrollbit.com\n„Zaloguj się za pomocą Steam”\n↓\nPrzekierowanie przez oddzielny serwer uwierzytelniający:\nrbsnin.comFiltr linków: CLEAN\nzarejestrowany 2026-09-18T09:34:52Z (Verisign RDAP)\n↓\nSteam Informacja na stronie logowania (2026-09-20):\n\"Note that rbsnin.com is not affiliated with Steam or Valve\"\nSteam wyświetla niniejszą informację z domeny OpenID (openid.realm) żądania, które otrzymało.\n↓\nSteam formularz logowania udostępniony na oddzielnym serwerze\nAutorzy nie zakończyli procesu logowania; proces obserwowano do momentu wyświetlenia formularza Steam.\nValve otrzymuje nazwę hosta return_to / realm przy każdym takim żądaniu. Serwer rbsnin.com nie zgłosił żadnego zablokowania przez filtr Link Filter dla 2026-09-21.\nNa prośbę\nJako dostawca OpenID, Steam otrzymuje nazwę hosta uwierzytelniającego wraz z każdym żądaniem uwierzytelnienia: trafia ona na serwery należące do Valve w openid.return_to oraz openid.realm parametry.\nWysłane przez stronę\nHost uwierzytelniający nie jest wykrywany podczas skanowania — platforma wysyła go jako Steam w każdym żądaniu. Zgodnie z OpenID 2.0 §9.1 return_to jest formalnie opcjonalny, ale bez niego Steam nie może zwrócić wyniku logowania, więc aby logowanie Steam działało, jest on w praktyce wymagany. Steam wyświetla nawet nazwę hosta użytkownikowi („<host> nie jest powiązany z Steam ani Valve\").\n14 lat\njest to czas, jaki upłynął od momentu utworzenia najstarszego serwera uwierzytelniającego, który w momencie sprawdzenia 2026-09-21 nadal obsługuje Steam logowania (dota2.net, zarejestrowany 2011-10-29); najnowszy ma trzy dni (rbsnin.com). Nie należy traktować liczby „0 zablokowanych hostów autoryzacyjnych” jako wniosku. Zablokowany serwer uwierzytelniający całkowicie uniemożliwiłby działanie funkcji „Zaloguj się za pomocą Steam” na platformie, więc rejestr utworzony na podstawie poprawnych logowań może zawierać wyłącznie serwery, które nigdy nie zostały zablokowane. Liczba, która ma znaczenie, to nie liczba blokad — chodzi o to, przez ile lat główna domena znajdowała się w filtrze Link Filter, podczas gdy login obok niej nadal działał.\nSerwery uwierzytelniające w oddzielnych domenach: data rejestracji a domena główna (30 tras: 25 zidentyfikowanych podczas audytu przeglądarki 2026-09-21 oraz 5 dodanych w 2026-09-22)\nPlatforma\tFiltr linków: główny\tHost autoryzacji\tFiltr linków: host uwierzytelniający\tZarejestrowano serwer autoryzacyjny\tŹródło obserwacji\tPlik dowodowy\nRollbit\nrollbit.com · rejestracja 2014-11-08\n\tZABLOKOWANE\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\trbsnin.com\tCLEAN\n2026-09-21 · surowy kod HTML (brak kopii zapasowej z Wayback Machine)\n\t2026-09-18\n09:34:52Z, Verisign RDAP\n\tSteam informacja na stronie logowania, 2026-09-20\trollbit.com.json\nSkin.Club\nskin.club · rejestracja 2017-09-04\n\tZABLOKOWANE\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\tsc-auth.net\tCLEAN\n2026-09-21 · Wayback 2026-09-21\n\t2019-04-02\nRDAP\n\tSteam komunikat na stronie logowania\tskin.club.json\nHowl.GG\nhowl.gg · rejestracja 2017-03-16\n\tZABLOKOWANE\n2026-09-18, 19.09, 21.09 · Wayback 2026-09-21\n\thowl.uno\tCLEAN\n2026-09-21 · Wayback 2026-09-21\n\t2026-08-11\nRDAP\n\tPrzechwytywanie obrazu z przeglądarki na żywo + podany adres URL OpenID\thowl.gg.json\nDuelbits\nduelbits.com · rej. 2020-02-03\n\tZABLOKOWANE\n2026-09-21 · Wayback 2026-09-21\n\tswitchflips.com\tCLEAN\n2026-09-21 · Wayback 2026-09-21\n\t2020-04-21\nRDAP\n\tPodany adres URL OpenID\tduelbits.com.json\nCSGOFast\ncsgofast.com · rej. 2015-03-27\n\tZABLOKOWANE\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\tsteam-login.authtofast.com\tCLEAN\nauthtofast.com, 2026-09-21 · Wayback 2026-09-21\n\t2026-06-30\nauthtofast.com, RDAP\n\tPrzeglądanie na żywo w przeglądarce + podany adres URL OpenID\tcsgofast.com.json\nFarmskins\nfarmskins.com · rej. 2016-03-23\n\tZABLOKOWANE\n2026-09-19, 2026-09-21 · surowy kod HTML\n\tsteam.kobal.cc\tCLEAN\n2026-09-19, 2026-09-21 · surowy kod HTML\n\t2017-01-07\nkobal.cc, RDAP\n\tPrzeglądanie na żywo w przeglądarce + podany adres URL OpenID\tfarmskins.com.json\nCobaltLab\ncobaltlab.tech\n\tZABLOKOWANE\n2026-09-21 · surowy kod HTML\n\tcobaltauth.com\tCLEAN\n2026-09-21 · surowy kod HTML\n\t2025-01-07\nRDAP\n\tPodany adres URL OpenID\tcobaltlab.tech.json\nCSGO.NET\ncsgo.net · rej. 2012-07-22\n\tZABLOKOWANE\n2026-09-21 · surowy kod HTML\n\tcn2.easylot.net\tCLEAN\n2026-09-21 · surowy kod HTML\n\t2016-09-03\neasylot.net, RDAP\n\tPrzechwytywanie obrazu z przeglądarki na żywo\tcsgo.net.json\nGGDrop\nggdrop.com\n\tZABLOKOWANE\n2026-09-21 · surowy kod HTML\n\tggauth.com\tCLEAN\n2026-09-21 · surowy kod HTML\n\t2023-05-03\nRDAP\n\tPodany adres URL OpenID\tggdrop.com.json\nRustChance\nrustchance.com\n\tZABLOKOWANE\n2026-09-21 · surowy kod HTML\n\thgfuihd.com\tCLEAN\n2026-09-21 · surowy kod HTML\n\t2019-01-27\nRDAP\n\tPodany adres URL OpenID\trustchance.com.json\nSkin.Fans\nskin.fans\n\tZABLOKOWANE\n2026-09-21 · surowy kod HTML\n\tauth.skinfans.com\tCLEAN\n2026-09-21 · surowy kod HTML\n\t2018-07-16\nskinfans.com, RDAP\n\tPodany adres URL OpenID\tskin.fans.json\nSkinport\nskinport.com · rejestracja 2018-09-05\n\tZABLOKOWANE\n2026-09-21 · surowy kod HTML\n\tskinport.app\tCLEAN\n2026-09-21 · surowy kod HTML\n\t2020-06-20\nRDAP\n\tPrzechwytywanie ekranu w przeglądarce na żywo + podany adres URL OpenID\tskinport.com.json\nSkins.Cash\nskins.cash\n\tZABLOKOWANE\n2026-09-21 · surowy kod HTML\n\tskinscash.live\tCLEAN\n2026-09-21 · surowy kod HTML\n\t2019-12-05\nRDAP\n\tPodany adres URL OpenID\tskins.cash.json\nTF2Hunt\ntf2hunt.com · rejestracja 2018-01-13\n\tZABLOKOWANE\n2026-09-21 · surowy kod HTML\n\trstspcl.com\tCLEAN\n2026-09-21 · surowy kod HTML\n\t2020-08-08\nRDAP\n\tPrzechwytywanie obrazu z przeglądarki na żywo + podany adres URL OpenID\ttf2hunt.com.json\nCSGOGem\ncsgogem.com · reg. 2016-10-16\n\tZABLOKOWANE\n2026-09-22 · surowy kod HTML\n\tapi.csgem.com\ncsgem.com — oddzielna domena, którą można zarejestrować\n\tCLEAN\n2026-09-22 · surowy kod HTML\n\t2014-03-08\ncsgem.com, RDAP — najstarszy w rejestrze\n\tRęczne gromadzenie danych + przechwytywanie za pomocą filtra linków\tlinkfilter-2026-09-22.json\nGamdom\ngamdom.com · rejestracja 2016-07-29\n\tZABLOKOWANE\n2026-09-22 · surowy kod HTML\n\tlogin.gambldom.com\ngambldom.com — różni się tylko jedną literą od nazwy marki\n\tCLEAN\n2026-09-22 · surowy kod HTML\n\t2017-09-24\ngambldom.com, RDAP\n\tRęczne gromadzenie danych + przechwytywanie za pomocą filtra linków\tlinkfilter-2026-09-22.json\n12CS\n12cs.fail · reg. 2026-03-24\n\tZABLOKOWANE\n2026-09-22 · surowy kod HTML\n\tfail.games\tCLEAN\n2026-09-22 · surowy kod HTML\n\t2021-08-24\nfail.games, RDAP\n\tRęczne gromadzenie danych + przechwytywanie za pomocą filtra linków\tlinkfilter-2026-09-22.json\nCSGOEmpire\ncsgoempire.com · rejestracja 2015-06-10\n\tCLEAN\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\tcsgoempirelogin4.com\njedna z dziesięciu ponumerowanych domen: login1–10\n\tCLEAN\n2026-09-21 · Wayback 2026-09-21\n\t2020-07-20\n05:49:17Z, Verisign RDAP\n\tPrzechwytywanie obrazu z przeglądarki na żywo\tcsgoempire.com.json\nCS.MONEY\ncs.money\n\tCLEAN\n2026-09-21 · surowy kod HTML\n\tauth.dota.trade\tCLEAN\n2026-09-21 · surowy kod HTML\n\t2016-07-15\ndota.trade, RDAP\n\tSteam informacja na stronie logowania\tcs.money.json\nCSFloat\ncsfloat.com · rejestracja 2021-07-11\n\tCLEAN\n2026-09-21 · surowy kod HTML\n\tcsgofloat.com\npoprzednia domena marki operatora; odrębna domena podlegająca rejestracji, nie stanowi oznaki obejścia przepisów\n\tCLEAN\n2026-09-21 · surowy kod HTML\n\t2015-09-29\nRDAP\n\tPrzechwytywanie obrazu z przeglądarki na żywo\tcsfloat.com.json\nG4Skins\ng4skins.com\n\tCLEAN\n2026-09-21 · surowy kod HTML\n\tauth.g4s.to\tCLEAN\n2026-09-21 · surowy kod HTML\n\t2021-05-30\ng4s.to, RDAP\n\tPodany adres URL OpenID\tg4skins.com.json\nJuice.GG\njuice.gg\n\tCLEAN\n2026-09-21 · surowy kod HTML\n\tletmeinjuice.com\tCLEAN\n2026-09-21 · surowy kod HTML\n\t2024-04-15\nRDAP\n\tPodany adres URL OpenID\tjuice.gg.json\nMarket.CSGO\nmarket.csgo.com\n\tCLEAN\n2026-09-21 · surowy kod HTML\n\tdota2.net\tCLEAN\n2026-09-21 · surowy kod HTML\n\t2011-10-29\nRDAP\n\tPrzechwytywanie obrazu z przeglądarki na żywo + podany adres URL OpenID\tmarket.csgo.com.json\nRust.TM\nrust.tm\n\tCLEAN\n2026-09-21 · surowy kod HTML\n\tdota2.net\tCLEAN\n2026-09-21 · surowy kod HTML\n\t2011-10-29\nRDAP\n\tPodany adres URL OpenID\trust.tm.json\nCSGOLounge\ncsgolounge.com · rej. 2013-08-14\n\tCLEAN\n2026-09-22 · surowy kod HTML\n\tdota2.net\ntrzeci interfejs użytkownika na tym serwerze uwierzytelniającym\n\tCLEAN\n2026-09-22 · surowy kod HTML\n\t2011-10-29\ndota2.net, RDAP\n\tRęczne gromadzenie danych + Przechwytywanie za pomocą filtru linków\tlinkfilter-2026-09-22.json\nDota2Lounge\ndota2lounge.com · rej. 2012-08-10\n\tCLEAN\n2026-09-22 · surowy kod HTML\n\tdota2.net\nczwarty interfejs użytkownika na tym serwerze uwierzytelniającym\n\tCLEAN\n2026-09-22 · surowy kod HTML\n\t2011-10-29\ndota2.net, RDAP\n\tRęczne gromadzenie danych + przechwytywanie za pomocą filtra linków\tlinkfilter-2026-09-22.json\nSkinBaron\nskinbaron.de\n\tCLEAN\n2026-09-21 · surowy kod HTML\n\tskinbaron.com\nta sama marka, inna domena najwyższego poziomu\n\tCLEAN\n2026-09-21 · surowy kod HTML\n\t2015-12-22\nRDAP\n\tPodany adres URL OpenID\tskinbaron.de.json\nTF2Royal\ntf2royal.com · rejestracja 2022-08-17\n\tCLEAN\n2026-09-21 · surowy kod HTML\n\ttf2auth.com\tCLEAN\n2026-09-21 · surowy kod HTML\n\t2021-07-27\nRDAP\n\tPrzechwytywanie ekranu przeglądarki na żywo + podany adres URL OpenID\ttf2royal.com.json\nTradeit\ntradeit.gg\n\tCLEAN\n2026-09-21 · surowy kod HTML\n\tconnect-tradeit.com\tCLEAN\n2026-09-21 · surowy kod HTML\n\t2022-02-23\nRDAP\n\tPodany adres URL OpenID\ttradeit.gg.json\nUrządzenie do ulepszania\nupgrader.pro\n\tCLEAN\n2026-09-21 · surowy kod HTML\n\tupgauth.space\tCLEAN\n2026-09-21 · surowy kod HTML\n\t2026-08-14\nRDAP\n\tPodany adres URL OpenID\tupgrader.pro.json\nŹródło: steamcommunity.com/linkfilter, żądanie GET bez uwierzytelniania, 2026-09-21, 53 hosty, odstęp 3 s; steam_tos_assets/linkfilter-recheck-2026-09-21.json; surowy kod HTML w steam_tos_assets/linkfilter-raw/. Terminy rejestracji: RDAP, steam_tos_assets/domain-registration.json. · Wcześniejsze sprawdzenie wartości 2026-09-19 w linkfilter-all-results.json · wprowadzać zapisy tras w auth-route-audit.json · Zrzuty ekranu stron „Link Filter” z serwisu Wayback Machine, 2026-09-21, wymienione w wayback-snapshots.json (nie ma migawki dla domeny rbsnin.com; jedynym zapisem jest lokalny plik surowy).\n\nTerminy rejestracji: RDAP (steam_tos_assets/domain-registry/). „Podany adres URL OpenID” określa parametry żądania, a nie zakończony proces logowania. Autorzy nie zalogowali się na żadnej platformie. Osobna domena sama w sobie nie stanowi dowodu na obejście zabezpieczeń. Również informacja „0 zablokowanych hostów uwierzytelniających” nie jest niezależnym ustaleniem: zablokowanie jednego z nich uniemożliwiłoby logowanie na tej platformie, więc rejestr utworzony na podstawie działających logowań nie może zawierać zablokowanego hosta uwierzytelniającego. Istotną obserwacją jest powiązanie oraz czas jego trwania — główna domena w filtrze linków obok domeny logowania, która funkcjonuje od lat. Tabela ta zawiera 30 wierszy: 25 z 27 tras z plikiem dowodowym dla każdej trasy oraz pięć dodanych w 2026-09-22, których podział w filtrze linków został ujęty w linkfilter-2026-09-22.json chociaż sama domena została zebrana ręcznie — wskazują na to wiersze w kolumnie „źródło”. Dwie niepokazane ścieżki plików dowodowych to skinsnipe.com (host autoryzacyjny pricing.tradeupspy.com, zarejestrowany 2020-03-11) oraz csgobig.com (host autoryzacyjny letmeinbig.com, zarejestrowany 2023-01-20); oba zwróciły wynik „BLOCKED main / CLEAN auth host” podczas sprawdzania 2026-09-22, zapisany z wykorzystaniem algorytmu SHA-256 w linkfilter-2026-09-22c.json, ale surowy kod HTML dla tej partii nie znajduje się w opublikowanym zestawie, więc zostały one tutaj wymienione z nazwy, zamiast otrzymać wiersz, co potwierdzają wszystkie pozostałe wiersze w tej tabeli. Pozostałe 12 ręcznie zebranych tras w rejestrze zostało oznaczonych jako takie w master_registry.json pod realm_src: user.\n\nPodstawowy audyt empiryczny · Zakres dat obejmujący kilka lat\nPułapka „szerszej perspektywy”: Filtr Link to tylko pozory zgodności z przepisami, a nie prawdziwa ochrona\n\nW przeglądarkach na komputerach stacjonarnych użytkownicy są chronieni przez zewnętrzne mechanizmy zabezpieczające: usługi Google Safe Browsing i Microsoft SmartScreen przechwytują znane próby phishingu, wyświetlając pełnoekranowe czerwone ostrzeżenia. W trybie „Big Picture” Steam, nakładce w grze (Shift+Tab) oraz w pakiecie Steam (SteamOS) te zabezpieczenia nie występują. Wbudowana przeglądarka nie obsługuje żadnych rozszerzeń, wyłącza zewnętrzne silniki funkcji „Bezpieczne przeglądanie” i pozostawia użytkownikowi dokładnie jedną barierę ochronną: Valve's linkfilter międzykomórkowa.\n\nPrzesuń, aby porównać wszystkie cztery wyniki →\n\n92.5%\n2025–2026: zaawansowane ataki phishingowe został uznany za bez zarzutu (37/40)\n77.5%\nPhishing w erze CS2 w latach 2023–2024 bez zastrzeżeń (31/40)\n70.0%\nStare ataki phishingowe z lat 2021–2022 bez zastrzeżeń (28/40)\n7 / 7\nzablokowane przewody zasilające urządzenia hazardowe (kontrola pozytywna)\nWieloletni audyt podłużny: 120 domen phishingowych typu „Pure Steam” przetestowanych w czasie rzeczywistym (24 września 2026 r.)\n\nAby sprawdzić, czy filtr Valve po prostu wolno rozpoznaje nowe zagrożenia, czy też jest na nie zasadniczo ślepy, przeprowadziliśmy audyt 120 potwierdzonych domen phishingowych związanych z Steam w trzech kohortach historycznych w porównaniu z steamcommunity.com/linkfilter:\n\nGrupa 1: 2021–2022 (klasyczne oferty wymiany i przedmioty do zdobycia) — 70.0% Bezbłędne zaliczenie (28/40). Nawet 4–5 lat po umieszczeniu na listach przez organizacje monitorujące w sieci 7 na 10 starszych serwerów służących do phishingu nadal działa bez żadnych ograniczeń.\nGrupa 2: 2023–2024 (CS2 Beta – szum medialny i fałszywe odwołania dotyczące wsparcia) — 77.5% Wynik bezbłędny (31/40). Kampanie podszywające się pod premiery gry „Counter-Strike 2” oraz fałszywe apele skierowane do społeczności (np. cs2-steam.com, appealsteamcommunity.help) przechodzą przez nie bez przeszkód.\nGrupa 3: 2025–2026 (wdrożenia bezserwerowe na obrzeżach sieci i klony ikon stron) — 92.5% Wynik bezbłędny (37/40). Nowoczesne zestawy do phishingu wdrażane na platformach EdgeOne, Vercel i Cloudflare Pages (np. steamgifter.online, steam-dp4lt5b8fnez.edgeone.dev) przechodzą praktycznie bez przeszkód.\n\nTelemetria i zabezpieczenie przed odpowiedzialnością, a nie ochrona. Po co w ogóle istnieje filtr Link Filter, skoro przepuszcza 70% do 92.5% przypadków czystego Steam phishingu? Służy on jako zastrzeżenie dotyczące odpowiedzialności firmy oraz jako czujnik telemetryczny kliknięć wychodzących. Przedstawiając uprzejmą „Wychodzisz Steam” komunikat z zielonym przyciskiem „Kontynuuj”, na który można kliknąć; Valve przenosi odpowiedzialność prawną na ofiarę na mocy Steam Umowy abonamentowej (*„użytkownik dobrowolnie opuścił stronę Steam”*). Valve gromadzi dane telemetryczne dotyczące kliknięcia, ale nie blokuje kradzieży.\n\nDowód na bezpieczeństwo favikonów: zerowe pobieranie danych z kanałów zagrożeń. Niezależne platformy analizujące zagrożenia (urlscan.io, Shodan, Censys) wykrywają aktywne Steam zestawy phishingowe poprzez proste wyszukiwanie oficjalnego skrótu favikony serwisu Steam (page.favicon.hash:9f890a9debcdfccc339149a7943be9aff9e4c9203c2fa37d5671a5b2c88503ad NOT domain:*.steampowered.com). Ta podstawowa, zautomatyzowana kontrola pozwala w ciągu kilku sekund wykryć aktywne klastry phishingowe. Valve nie synchronizuje się z zewnętrznymi źródłami danych, nie przeprowadza wyszukiwania zagrożeń opartego na skrótach i interweniuje ręcznie jedynie w przypadku wymogu ze strony organów regulacyjnych (nakaz dotyczący hazardu wydany przez WSGC w 2016 r.) lub w celu ochrony swoich zastrzeżonych nazw domen.\n\nPodstawowe dowody audytowe w postaci artefaktów: Wieloletnia kontrola podłużna obejmująca 120 dziedzin: audyt-phishingu-parowego-w-kierunku-podłużnym.json · 100 dedykowanych próbek phishingowych Steam: linkfilter-steam-phishing-100.json · Szeroko zakrojony audyt paszowy (n=250): linkfilter-coverage-2026-09-22.json.\n\nCSGOEmpire — zbiorcza rejestracja dziesięciu ponumerowanych domen autoryzacyjnych\n\nW dniu 2020-07-20 dziesięć numerowanych domen, csgoempirelogin1.com przez csgoempirelogin10.com, zostały zarejestrowane. Dla wszystkich dziesięciu zapisano sygnatury czasowe RDAP firmy Verisign: login1 05:49:06Z, login5 05:49:08Z, login2 05:49:11Z, login3 05:49:14Z, login4 05:49:17Z, login6 05:49:20Z, login7 05:49:23Z, login8 05:49:26Z, login9 05:49:28Z — dziewięć domen w 22 sekundy — oraz login10 o godz. 05:56:03Z, siedem minut później. Odstępy czasowe wskazują na pojedynczą operację zbiorczą przeprowadzoną przez rejestratora.\n\nSchemat ten jest zgodny z wcześniej skonfigurowanymi hostami rezerwowymi; jedynie login4 zostało to zaobserwowane w rzeczywistym żądaniu OpenID. Zarówno csgoempire.com, jak i csgoempirelogin4.com zwróciły wynik „CLEAN” w filtrze Link Filter przy wartości 2026-09-21; CSGOEmpire nie znalazło się wśród stron wymienionych w doniesieniach prasowych dotyczących zawiadomień z lipca 2016 r.\n\n# DNS — wszystkie 10 aktywnych (wrzesień 2026 r.)\nOK csgoempirelogin1.com 172.67.129.43\nOK csgoempirelogin2.com 172.67.175.168\nOK csgoempirelogin3.com 188.114.96.3\nOK csgoempirelogin4.com 188.114.96.11 ← w ruchu OpenID\nOK csgoempirelogin5.com 172.67.160.194\nOK csgoempirelogin6–10.com Adresy IP serwisu Cloudflare\nNXDOMAIN: csgoempirelogin11.com\nWszystkie 10 zarejestrowanych 2020-07-20; wszystkie 10 z sygnaturą czasową RDAP (steam_tos_assets/domain-registry/csgoempireloginN.com.rdap.json)\nWnioski dla organów regulacyjnych\nZablokowana domena główna w połączeniu z odblokowanym hostem uwierzytelniającym sprawia, że trasa logowania pozostaje otwarta — i pozostaje otwarta przez lata.\n\nBlok filtru Link Filter w domenie głównej stanowi weryfikowalny, publiczny wpis. Host uwierzytelniający obsługuje ruch „Zaloguj się za pomocą Steam” i pojawia się w parametrach żądania OpenID należących do Valve. W wyniku kontroli 2026-09-21 i 2026-09-22 w 26 parach z podziałem na filtry domena główna zwróciła blok „Link Filter”, podczas gdy serwer proxy obsługujący logowanie nie zwrócił żadnego. Powyższy rejestr pokazuje drugą połowę tego zjawiska: hosty te nie są krótkotrwałymi domenami jednorazowego użytku. Kilka z nich było zarejestrowanych od ponad dekady w dniu kontroli, a każdy z tych dni to dzień, w którym Valve otrzymało nazwę hosta w swoich własnych parametrach żądania. Valve nie opublikował żadnych danych dotyczących egzekwowania przepisów w podziale na operatorów, więc na podstawie danych publicznych nie można ustalić, czy wobec tych hostów zastosowano jakiekolwiek inne środki.\n\n12 lat i 6 miesięcy\nWitryna csgogem.com jest zablokowana w filtrze linków.\nJego serwer logowania api.csgem.com było\njest zarejestrowany od 2014-03-08, a ten nie jest.\nPodsumowanie w przystępnym języku — dla organów regulacyjnych i sądów (rozwiń)\nPodsumowanie w przystępnym języku — dla organów regulacyjnych\nKontekst: Czym jest Steam i dlaczego ma to tutaj znaczenie\n\nSteam to platforma oprogramowania obsługiwana przez spółkę Valve Corporation (Bellevue, Waszyngton, USA). Steam pełni funkcję dostawcy tożsamości cyfrowej: serwisy hazardowe i gry online w Internecie korzystają z systemu o nazwie „Zaloguj się przez Steam” — przycisku, który pozwala serwisowi zweryfikować, czy odwiedzający posiada prawdziwe konto Steam. Działa to podobnie jak „Zaloguj się przez Google” lub weryfikacja za pomocą dowodu tożsamości wydanego przez władze: strona internetowa przekierowuje użytkownika na serwery Steam, Steam potwierdza jego tożsamość, a Steam przekierowuje go z powrotem na stronę internetową. Valve zarządza systemem uwierzytelniania. Każde logowanie za pomocą opcji „Zaloguj się przez Steam” odbywa się za pośrednictwem serwerów należących do Valve.\n\nCo zrobił Valve: Blokada domeny\n\nW lipcu 2016 r., w wyniku presji ze strony mediów i organów prawnych w związku z hazardem typu „skin”, pełnomocnik Valve wysłał zawiadomienia do około 23 wymienionych serwisów hazardowych (zgodnie z doniesieniami prasowymi z 21 lipca 2016 r.); w październiku 2016 r. firma Valve poinformowała Komisję ds. Hazardu stanu Waszyngton, że skontaktowała się z ponad czterdziestoma serwisami. Niektóre domeny serwisów hazardowych pojawiają się w Steam Filtr linków — lista, dzięki której każdy link do tych stron umieszczony w Steam (na czacie, na stronie profilowej, w sklepie) powoduje wyświetlenie strony z ostrzeżeniem: „Link zablokowany!” Filtr łącza jest jedynym środkiem egzekwującym, którego działanie można zaobserwować spoza Valve.\n\nPrzykład: Link do rollbit.com W polu Steam wyświetla się strona ostrzegawcza „Link Filter” (zaznaczone opcje 2026-09-19 i 2026-09-21). Teoretycznie strona z hazardem jest zablokowana.\nCzym jest domena proxy\n\nA Host uwierzytelniający w oddzielnej domenie jest serwerem proxy uwierzytelniającym: drugi adres strony internetowej, w innej domenie podlegającej rejestracji, który ten sam operator umieszcza pomiędzy swoimi użytkownikami a Steam wyłącznie w celu realizacji etapu „Zaloguj się za pomocą Steam”. Działa on jako serwer proxy dla procesu logowania. Użytkownik sądzi, że loguje się na platformie; żądanie docierające do Valve zawiera nazwę hosta serwera proxy, a nie platformy. Zazwyczaj nie ma on żadnego publicznie widocznego powiązania ze stroną hazardową i jest to adres, na który użytkownicy są przekierowywani po potwierdzeniu ich tożsamości przez Steam.\n\nPrzykład: Rollbit działa na zasadach rollbit.com, który jest blokowany przez filtr Link Filter. W przypadku uwierzytelniania Steam w ruchu obserwowanym na 2026-09-20 wykorzystywano oddzielny adres: rbsnin.com, zarejestrowany jako 2026-09-18. Ten adres zwrócił brak bloku „Filtr linków” w dniu 2026-09-21. Serwis hazardowy nadal działał, a jego proces logowania Steam przebiegał przez odblokowany serwer.\nKluczowy moment: w każdym żądaniu adres hosta uwierzytelniającego jest wysyłany do Steam\n\nValve nie musi przeprowadzać skanowania ani indeksowania, aby ustalić, które hosty uwierzytelniające są obecnie używane. Steam to Dostawca tożsamości OpenID dla tych witryn, a każde kliknięcie opcji „Zaloguj się za pomocą Steam” wysyła żądanie GET do serwerów Valve zawierające nazwę hosta uwierzytelniającego w postaci zwykłego tekstu. Zgodnie z OpenID 2.0 §9.1 return_to Pole to jest formalnie opcjonalne, ale bez niego Steam nie może zwrócić wyniku logowania, więc aby logowanie Steam działało, jest ono w praktyce wymagane. Samo Steam wyświetla nazwę hosta na stronie logowania („<host> nie jest powiązany z Steam ani Valve\").\n\n— Kształt żądania Steam (host zaobserwowany dla Rollbit na 2026-09-20): —\nPOBRAĆ steamcommunity.com/openid/login\n&openid.mode=checkid_setup\n&openid.return_to=https://rbsnin.com/… ← faktycznie wymagane; trafia do dziennika Valve\n&openid.realm=https://rbsnin.com ← podane przez samą stronę; wyświetlane na stronie logowania użytkownika Steam\nJeśli strona korzysta z weryfikacji typu „serwer-do-serwera” (check_authentication), w dzienniku użytkownika Valve zapisywany jest również adres IP serwera platformy oraz sieć hostingowa.\n\nWyodrębnienie nazwy hosta z tego żądania jest standardową operacją. Rejestr działań — zawierający informacje o tym, wobec których hostów podjęto działania, a wobec których nie, oraz na podstawie jakich kryteriów — istnieje wyłącznie w infrastrukturze Valve i nie został opublikowany.\n\nCo to dowodzi\n\n1. Blok „Link Filter” działa na linki, a nie na logowania. Zablokowanie głównej domeny (na przykład rollbit.com) wyświetla ostrzeżenie dla użytkowników, którzy klikną linki do tej strony w obrębie Steam. Nie uniemożliwia to jednak działania serwisu ani korzystania z własnej usługi OpenID serwisu Valve za pośrednictwem innego adresu.\n\n2. Testowane serwery uwierzytelniające nie zostały zablokowane. Powyższa tabela przedstawia hosty uwierzytelniające z oddzielnych domen zarejestrowane w latach 2011–wrzesień 2026 r., z których kilka pojawiło się wiele lat po ogłoszeniach z lipca 2016 r. W 26 parach domena główna zwróciła blokadę filtru linków, a serwer proxy obsługujący jej logowanie – nie (sprawdzenia bez uwierzytelniania, 2026-09-21 i 2026-09-22; zapisano surowe odpowiedzi i skróty SHA-256). Ten serwer proxy przestałby działać w dniu, w którym Valve go odrzucił, dlatego miarą jest tutaj czas jego działania, a nie to, czy znajduje się na liście. Valve otrzymuje te nazwy hostów w swoich własnych żądaniach OpenID. Na podstawie danych publicznych nie można ustalić, czy zastosowano jakiekolwiek środki inne niż filtr linków, ponieważ Valve nie opublikował żadnych danych dotyczących egzekwowania przepisów w podziale na operatorów.\n\n3. Witryny nadal przeprowadzały uwierzytelnianie za pośrednictwem infrastruktury Valve. „Zaloguj się za pomocą Steam” to usługa Valve; każde uwierzytelnienie za jej pośrednictwem stanowi żądanie, które Valve odbiera i przetwarza. Valve również czerpie przychody z kluczy skrzynek, a Steam Community Market pobiera łączną opłatę w wysokości około 15% od transakcji zrealizowanych w ramach Marketu (nie dotyczy to transakcji zewnętrznych). Działanie „Link Filter” utworzyło publiczny zapis; nie przerwało to relacji uwierzytelniającej.\n\nCzy zablokowanie by zadziałało?\n\nAnalogicznie: kiedy w 2023 roku zakończył działalność darmowy rejestrator domen Freenom, zakłócono kampanie phishingowe oparte na jego domenach. Ciągłość działania zależy od stabilności infrastruktury.\n\nTa sama logika ma tu zastosowanie. Gdyby host uwierzytelniający został odrzucony podczas przetwarzania OpenID przez Steam, funkcja platformy „Zaloguj się za pomocą Steam” przestałaby działać do momentu zarejestrowania nowego hosta, wydania certyfikatów i propagacji zmian w systemie DNS. W tym okresie wystąpiłaby przerwa w działaniu.\n\nRotacja nie sprawia, że blokowanie staje się bezcelowe. W ten sposób blokowanie staje się kosztem operacyjnym. Ponieważ nowe serwery pojawiają się w logach żądań samego Valve przy pierwszym użyciu, odpowiedź może przebiegać z prędkością charakterystyczną dla tego pierwszego użycia.\n\nRejestracja zbiorcza sama w sobie stanowi sygnał: Konta „login1–login10” serwisu CSGOEmpire zostały zarejestrowane w dniu 2020-07-20, z czego dziewięć w ciągu 22 sekund (Verisign RDAP). Odpowiedź nie musi dotyczyć poszczególnych domen; sekwencję z jednej sesji u rejestratora można uznać za serię.\n\nZ publicznie dostępnych danych nie wynika, aby miała miejsce próba zablokowania hostów autoryzacyjnych, która zostałaby udaremniona przez rotację.\nWidać tam główne domeny, które zostały zablokowane, podczas gdy serwer proxy obsługujący poszczególne logowania nadal działał — 26 par według stanu na 2026-09-22, przy czym najstarszy host uwierzytelniający został zarejestrowany 12 lat i 6 miesięcy temu — oraz brak opublikowanych danych dotyczących egzekwowania przepisów w odniesieniu do jakiegokolwiek operatora.\nW związku z tym pytanie do organu regulacyjnego brzmi: jakie środki egzekucyjne, jeśli w ogóle, zastosował Valve wobec hostów autoryzujących, które otrzymuje w ramach własnych żądań OpenID?\nCo zrobiło Valve — i dlaczego nie przerwało to ścieżki uwierzytelniania\n\nW poniższej tabeli zestawiono wszystkie publicznie udokumentowane działania Valve wraz z informacją, czy miały one wpływ na punkt wejścia uwierzytelniania OpenID. Wniosek nie brzmi: „Valve nie podjął żadnych działań” — chodzi o to, że żadne z publicznie udokumentowanych działań nie dotyczyło punktu, w którym logowania do platform hazardowych przechodzą przez serwery Valve.\n\nData\tValve Działanie\tDotknięte openid.return_to ścieżka?\nlipiec 2016 r.\tOświadczenie publiczne z dnia 13 lipca 2016 r.; zawiadomienia pełnomocnika skierowane do około 23 wymienionych podmiotów (prasa, 21 lipca 2016 r.); skontaktowano się z ponad 40 podmiotami w związku z pismem Valve z października 2016 r. skierowanym do WSGC\tNie. Powiadomienia i filtr linków działają na operatorach i linkach; ścieżka żądania OpenID nie uległa zmianie.\n2017\tZamknięcie IEconItems_730/GetPlayerItems (według konta inżynieryjnego użytkownika CSFloat; nie znaleziono dziennika zmian Valve)\tNie. Problem dotyczył widoczności historii elementów publicznych. Uwierzytelnianie OpenID nie uległo zmianie.\n2018-03-29\tOgłoszono 7-dniowe blokowanie handlu w CS:GO (blog.counter-strike.net)\tNie. Spowolniono przepływ danych; ścieżka żądania OpenID nie uległa zmianie.\n2022-05-10\tUsunięto punkty końcowe dotyczące anulowania transakcji z publicznego interfejsu API (zauważone przez użytkownika; brak wpisu Valve w dzienniku zmian — node-steam-tradeoffer-manager #325)\tNie. Zamknięto narzędzie do wymiany ofert; uwierzytelnianie OpenID nie zostało zmodyfikowane.\n2023-12-04\tUtworzenie klucza API wymaga teraz potwierdzenia za pomocą telefonu komórkowego (steamcommunity.com/dev/apikey; brak informacji o zmianach)\tNie. Kluczowy punkt końcowy został zabezpieczony; opisane tutaj hosty uwierzytelniające nie zostały dotknięte tym problemem.\n2026-09-19 / 21.09\tSteam Stan filtra łącza zgodnie z obserwacjami autorów\tW 14 głównych domenach wykryto blokadę podczas ponownej kontroli zapisanej wartości 2026-09-21 — 26 podzielonych par w rejestrze o wartość 2026-09-22 — podczas gdy serwer proxy obsługujący poszczególne logowania nadal działał.\nŹródła: Valve oświadczenie z dnia 13 lipca 2016 r. (store.steampowered.com/oldnews/22883, zarchiwizowano 2026-09-21) · Sprawozdanie inżynieryjne firmy CSFloat dotyczące zamknięcia z 2017 r. (blog.csfloat.com, zarchiwizowane 2026-09-21) · Stan filtra linków: linkfilter-recheck-2026-09-21.json.\nWniosek ten można obalić, przedstawiając choćby jeden opublikowany przypadek, w którym Valve odrzucił żądanie OpenID, ponieważ openid.return_to wskazywał na serwer autoryzacyjny związany z hazardem. W publicznie dostępnych rejestrach nie znaleziono żadnej takiej instancji.\nDwie najnowsze rejestracje hostów uwierzytelniających\nhowl.unozostał zarejestrowany 2026-08-11 (RDAP) 41 dni przed 2026-09-21; serwis howl.gg zwrócił komunikat o zablokowaniu przez filtr linków w dniach 2026-09-18, 2026-09-19 i 2026-09-21. Nie ustalono, czy blokada poprzedzała rejestrację.\nrbsnin.comzostał zarejestrowany jako 2026-09-18T09:34:52Z (Verisign RDAP) i został wykryty w procesie logowania serwisu Rollbit o numerze Steam w dniu 2026-09-20 na podstawie informacji wyświetlanej na własnej stronie logowania serwisu Steam; rollbit.com zwrócił blokadę filtru linków w dniach 2026-09-19 i 2026-09-21, natomiast rbsnin.com tego nie zrobił.\nKażdy host z powyższej tabeli jest wysyłany do serwerów uwierzytelniających Valve jako openid.realm przy każdej próbie zalogowania się.\nPełne dane dotyczące poszczególnych tras oraz wyniki działania filtra łączy: tabela w sekcji 3 powyżej; surowe wyniki w linkfilter-recheck-2026-09-21.json oraz linkfilter-all-results.json.\nMetodologia — w jaki sposób ustalono liczby filtrów tras i połączeń\n1. Rozpoznawanie domen\nW ramach audytu 2026-09-21 sprawdzono 78 ze 189 platform objętych badaniem: 33 uwierzytelniają się na podstawie własnej nazwy hosta, a 20 — na podstawie własnej subdomeny — jest to uwierzytelnianie bezpośrednie, a żadna z tych tras nie jest traktowana jako trasa z odrębnej domeny. Pozostałe 25 – uwierzytelnianie za pośrednictwem oddzielnej domeny, którą można zarejestrować, w ramach 24 różnych nazw hostów (dota2.net jest wspólny dla market.csgo.com i rust.tm): 10 ustalonych na podstawie zrzutu ekranu z przeglądarki w czasie rzeczywistym, 3 na podstawie informacji wyświetlanej na stronie logowania serwisu Steam, a 12 na podstawie podanego adresu URL OpenID. Rejestr na żywo (master_registry.json, 2026-09-22) rozszerza to na 44 trasy w oddzielnych domenach: 26 par z podziałem na filtry (domena główna BLOCKED, host autoryzacyjny CLEAN) oraz 18 dodatkowych tras bez podziału na domenę główną. Spośród tych 44, 27. Prowadzić dokumentację dowodową dla każdej trasy; pozostałe 17 zebrano ręcznie i są one oznaczone realm_src: user w rejestrze. Pięć z tych siedemnastu — csgogem.com, gamdom.com, 12cs.fail, csgolounge.com i dota2lounge.com — zostało dodanych 2026-09-22 wraz z przechwyceniem filtru linków dla obu hostów (surowy kod HTML + SHA-256 w linkfilter-2026-09-22.json), więc sam podział jest widoczny, mimo że dane o królestwie zostały zebrane ręcznie; pojawiają się one w powyższej tabeli obok tras z plików dowodowych. tfauth.com (tf2easy.com) został usunięty z rejestru o godz. 2026-09-22: podobnie jak w przypadku arena.fragnet.net, nie ma żadnych weryfikowalnych powiązań z pierwotną witryną. Liczbę tę można ponownie obliczyć na podstawie opublikowanych auth-route-audit.json (seria 2026-09-21) zgodnie z jedną zasadą: platforma jest brana pod uwagę tylko wtedy, gdy jej zidentyfikowany host OpenID Steam znajduje się w innej domenie podlegającej rejestracji niż sama platforma.\n2. Steam Stan filtra linków\nPrzetestowano za pomocą steamcommunity.com/linkfilter/?url=https://[domain], bez uwierzytelnienia, na 2026-09-19 i 2026-09-21; surowy kod HTML zapisany z wykorzystaniem algorytmu SHA-256. Status rejestrowany oddzielnie dla domeny głównej i hosta uwierzytelniającego. Klasyfikator odróżnia ogólny komunikat „Opuszczasz Steam” (CLEAN) od strony „Link zablokowany! ... oznaczony jako potencjalnie złośliwy” (BLOCKED); test kontrolny z google.com potwierdza, że te dwa komunikaty nie są mylone. Wcześniejsza, uwierzytelniona wersja tego testu została odrzucona, ponieważ zwracała wynik „zablokowane” dla każdej domeny, w tym dla tej kontrolnej — przyczyną okazał się nieprawidłowy plik cookie sesji w skrypcie testowym, a nie rzeczywisty wynik.\n3. Obserwacja hosta autoryzacyjnego\nPrzechwytywanie na żywo: przeglądarka Playwright przechodziła do procesu logowania każdej platformy, a następnie openid.return_to Nazwa hosta została odczytana z przechwyconego żądania. Informacja na stronie logowania: nazwa hosta została odczytana z własnego „” użytkownika Steam's „<host> nie jest powiązany z Steam ani Valve\" tekst, który Steam wyświetla jako openid.realm (rbsnin.com, sc-auth.net, auth.dota.trade). Podany adres URL: adres URL loginform o wartości „a Steam”, przekazany autorom; określa on parametry żądania, a nie zakończony proces logowania. Na żadnej platformie nie doszło do zakończenia procesu logowania.\n4. Zakres — czego nie udało się rozwiązać i dlaczego ma to znaczenie\nSpośród 189 platform, 110 nie wytyczyło żadnej ustalonej trasy a jeden nie miał zastosowania (189 − 78 − 1). W niniejszej dokumentacji nie uwzględniono żadnego z nich. Podział tych 110 przypadków, zgodnie z plikiem audytowym: 22 wyzwania związane z botami, 14 przekroczeń limitu czasu, 12 błędów HTTP i 10 błędów nawigacyjnych — obserwator nie mógł przejść do procesu logowania, choć większość z tych stron otwiera się normalnie w zwykłej przeglądarce; 20 nie wykazało żadnej kontroli logowania Steam na stronie docelowej; 16 dotarło do procesu logowania, którego nie udało się rozpoznać jako hosta; 11 domen nie rozpoznało się w systemie DNS; 5 zatrzymało się na ekranie wymagającym zgody. Poniższy wykaz dzieli te same 110 przypadków w inny sposób: 11 domen, których nie udało się rozpoznać w systemie DNS, wymieniono oddzielnie jako Usunięto · NXDOMAIN, a ten jeden wpis, który nie spełnia kryteriów, dołącza do pozostałych. Skontrolowano 189 platform, z których 11 zostało usuniętych na podstawie ostatecznego wyniku NXDOMAIN z obu serwerów rozpoznawczych, 178 zachowanych (platform-audit.json, platforms-removed.json). 137 domen uwierzytelniających, które rejestr odgadł na podstawie wzorca nazewnictwa, zostało usuniętych z danych dotyczących 2026-09-19 — nigdy nie zaobserwowano ich, a zatem nie stanowią one dowodu. Trzy z tych domysłów zostały podważone przez podane adresy URL OpenID: serwisy buff.163.com, gamerpay.gg i csgoluck.com przeprowadzają uwierzytelnianie bezpośrednio, w przeciwieństwie do domysłów dotyczących adresów buffauthproxy.163.com, gamerpayredirect.io i lucklogin.app. Usunięte pozycje zostały wymienione w opublikowanym pliku audytowym.\nLiczba 25 stanowi minimalną wartość, a nie maksymalną. Spośród 78 platform, w przypadku których udało się uzyskać dostęp, 25 korzystało z oddzielnej domeny, a 53 nie. Na podstawie tego stosunku nie wyciąga się żadnych wniosków dotyczących 110 platform, w przypadku których nie udało się uzyskać dostępu, a żadne prognozy na tej podstawie nie pojawiają się w żadnym miejscu niniejszego dossier. Każdą z nich można rozwiązać, otwierając stronę i klikając „Zaloguj się za pomocą Steam”: nazwa hosta uwierzytelniającego znajduje się w adresie URL ładowanej strony Steam.\nCelem tej sekcji jest: Niezależny obserwator potrzebuje przeglądarki i sporej cierpliwości, by zidentyfikować 189 platform, a zidentyfikował 78. Valve wymaga zapytania do bazy danych. Każda platforma korzystająca z opcji „Zaloguj się za pomocą Steam” — zarówno zidentyfikowana, jak i niezidentyfikowana — wysyła openid.realm do punktu końcowego uwierzytelniania Valve przy każdym logowaniu. Luka w tej tabeli wynika z tego, że autorzy znajdują się poza systemem. W przypadku Valve taka luka nie występuje.\nZauważone nazwy hostów proxy znajdują się w auth-route-audit.json. Daty rejestracji domen z baz RDAP (Verisign) / IP2WHOIS. Wyniki filtrowania linków: linkfilter-all-results.json.\nAnalogia dla lepszego zrozumienia\n\nWyobraźmy sobie, że organy regulacyjne informują licencjonowaną firmę taksówkową, iż nie może ona już prowadzić działalności pod zarejestrowanym adresem przy Main Street. Firma usuwa szyld z Main Street. Usunięcie szyldu zostaje udokumentowane. Jednak ta sama firma otwiera oddział przy Side Street — zarejestrowany pod inną nazwą — i kontynuuje działalność właśnie stamtąd. Organy regulacyjne obsługują centralny system dyspozytorski, z którego korzystają wszystkie taksówki z obu adresów. Każde zlecenie przejazdu zawiera informację „odbiór z Side Street”. Organy regulacyjne nigdy nie cofają licencji dotyczącej Side Street. Jedynym podjętym działaniem egzekucyjnym było usunięcie znaku „Main Street”. Firma taksówkarska nigdy nie zaprzestała działalności.\n\nCzęść A — Dokumentacja techniczna · Punkt 3.1\nWewnątrz Steam jedyną listą jest lista Valve.\n\nLink kliknięty w kliencie Steam, nakładce w grze lub trybie Big Picture nie otwiera się w przeglądarce użytkownika. Jest on wyświetlany w wbudowanej przeglądarce Steam — gdzie nie występują warstwy ostrzegawcze, które stosowałaby przeglądarka. Filtr Link nie jest tylko jednym z wielu zabezpieczeń. Stanowi całość.\n\nW zwykłej przeglądarceTrzy niezależne warstwy\nBezpieczne przeglądanie GooglePełnoekranowa strona pośrednia wyświetlana użytkownikom znajdującym się na listach Google dotyczących phishingu i złośliwego oprogramowania, aktualizowana na bieżąco i niezależnie od odwiedzanej witryny.\nRozszerzenie przeglądarki z funkcją antywirusowąWiększość produktów przeznaczonych dla użytkowników końcowych zawiera dodatek do przeglądarki, który porównuje adres docelowy z własną listą reputacji dostawcy.\nKontrola protokołu HTTPS w punktach końcowychW przypadku gdy produkt przeprowadza kontrolę TLS, zawartość strony jest skanowana, zanim dotrze do użytkownika.\nW kliencie Steam: nakładka i tryb Big PictureJedna warstwa\nBezpieczne przeglądanie GoogleBrak. Sprawdzanie to wymaga kluczy API Google, które nie są udostępniane w wbudowanych kompilacjach Chromium; w przypadku ich braku, zgodnie z dokumentacją projektową Chromium, moduł obsługi funkcji „Bezpieczne przeglądanie” po prostu nigdy nie jest dodawany do łańcucha żądań.\nRozszerzenie przeglądarki z funkcją antywirusowąBrak. Renderer Steam nie jest przeglądarką użytkownika i nie ładuje żadnych rozszerzeń z profilu przeglądarki użytkownika, więc żadne dodatki nie działają na tej stronie.\nKontrola HTTPS w punktach końcowychZależy od produktu. Ruch kończy się wewnątrz procesu z podpisem kodowym Valve, a nie w rozpoznawalnej przeglądarce, a wiele produktów końcowych wyłącza podpisane aplikacje z kontroli TLS.\nFiltr linków SteamWłasna lista blokowanych adresów Valve, sprawdzana w momencie, gdy link opuszcza ekosystem Steam. Jest to jedyna przeprowadzana kontrola — a powyższa tabela przedstawia wyniki tej kontroli dla hostów uwierzytelniających opisanych w tej sekcji.\nTest, który może przeprowadzić każdy czytelnik, a wynik jest nieprawidłowy, jeśli test się nie powiedzie\n\nOtwórz jeden z opublikowanych przez Google adresów URL służących do testowania funkcji „Bezpieczne przeglądanie” (testsafebrowsing.appspot.com) w przeglądarce Chrome: pojawia się całostronicowa czerwona strona przejściowa. Otwórz ten sam adres URL z wiadomości czatu Steam, tak aby został wyświetlony w kliencie Steam lub w nakładce: strona przejściowa nie pojawia się. Jedynym ostrzeżeniem, jakie może wygenerować Steam, jest jego własna strona filtru linków i dotyczy to wyłącznie hostów znajdujących się na liście Valve.\n\nWyniki programu bug bounty użytkownika ValveTen motyw został już wcześniej wykorzystany — na płycie samego Valve\n\nJeśli filtr Link Filter jest jedyną kontrolą wykonywaną po stronie klienta, to jego własne tryby awarii nie są kwestią drugorzędną. Dwa zgłoszenia w ramach programu HackerOne firmy Valve — oba przyjęte, oba rozwiązane, a od tego czasu w całości ujawnione:\n\n#291750zarchiwizowano 2025-11-16 ↗Open Redirect · medium\nOminięcie zabezpieczenia filtra łącza\n\nZgłoszono 19 listopada 2017 r., usunięto, ujawniono 9 maja 2018 r. Własny dowód słuszności koncepcji zawarty w raporcie: zastąpienie ideograficznego znaku kropki 。 (%E3%80%82) w odniesieniu do kropki w nazwie hosta — można obejść tę blokadę. Reklama, której dotyczy ta sekcja, nie pojawiła się.\n\n#1079561zarchiwizowano 2026-09-24 ↗Ujawnianie informacji · wysoki\nPrzeglądarka internetowa Big Picture ujawnia pliki cookie związane z logowaniem oraz poufne informacje (może to prowadzić do przejęcia konta)\n\nZgłoszono 15 stycznia 2021 r., rozwiązano, ujawniono 21 września 2021 r. Własna ocena ważności Valve jest wysoka, a tytuł określa konsekwencję. Ujawniony wpis zawiera tytuł, ocenę i daty; opis techniczny nie znajduje się w opublikowanej treści, więc nie cytuje się tutaj żadnych dalszych fragmentów z niego.\n\nTo interpretacja autorów, a nie wniosek zawarty w żadnym z raportów: oba te zjawiska występują po obu stronach tej samej bramy. Jednym z nich jest brak ostrzeżenia przed otwarciem strony docelowej; drugim – utrata sesji przez klienta po otwarciu strony w ramach tej sesji. Sekwencja zdarzeń następująca po kradzieży sesji — zarejestrowanie klucza bez monitu, anulowanie prawdziwej transakcji, wysłanie duplikatu do klona — stanowi schemat opisany w Sekcja 5 do Sekcja 8. Oba zgłoszenia zostały zamknięte; żadne z nich nie jest obecnie uznawane za aktywną lukę w zabezpieczeniach. To, co z nich wynika, ma węższy zakres, ale jest wystarczające: jedyna pozostała warstwa ma udokumentowaną historię obchodzenia zabezpieczeń, co wynika z własnych danych użytkownika Valve.\n\nŹródło: rekord ujawnienia w serwisie HackerOne dla każdego zgłoszenia, pobrany 2026-09-22 — numer, tytuł, zespół, luka, poziom zagrożenia, daty zgłoszenia i ujawnienia oraz status zgodnie z informacjami opublikowanymi przez HackerOne. Rekord pobrania: hackerone-reports.json. Nie podano tu kwoty nagrody; nie pojawia się ona również w ujawnionych dokumentach, do których uzyskano dostęp.\n\nObserwacja terenowa · PhishDestroyWykrycia, które zazwyczaj kończą kampanię, nie zakończyły tych\n\nObserwowaliśmy, jak serwery phishingowe wciąż generowały ruch, jednocześnie przenosząc 20 lub więcej wykrytych dostawców. Kampania realizowana przez Internet lub pocztę elektroniczną w takim stanie kończy się w ciągu kilku dni — zarówno przeglądarka, jak i program antywirusowy reagują na te werdykty. W środowisku Steam żadne z nich tego nie robi. Werdykty istniały przez cały czas. Żadna część klienta nigdy o to nie pytała.\n\nCo to oznacza dla nieletniego, który ma zainstalowany program antywirusowy\n\nNie ignoruje żadnego ostrzeżenia i niczego nie wyłącza. W Steam pojawia się wiadomość — darmowy nóż, głos na drużynę znajomego — a strona otwiera się w Steam. Nigdy nie otwiera przeglądarki, więc przeglądarka nigdy go nie chroni. Jego program antywirusowy działa i być może już uznał tę domenę za złośliwą; jednak nigdy nie jest o to pytany. Istnieją już wszystkie ostrzeżenia, które mogłyby go powstrzymać. Żadne z nich do niego nie dociera. Uważa, że nigdy nie opuścił Steam, i rzeczywiście tak było.\n\nTa „gratisowa oferta” nie jest wymysłem oszusta — strony z skinami i hazardowe reklamują się właśnie jako oferujące darmowe Valve przedmioty, i właśnie dlatego wiadomość ta wydaje się zwyczajna. Skargi: archiwum egzekucji. Dane dotyczące wieku i dzieci: Sekcja 17.\n\nŹródła: Steam wyświetla treści internetowe za pośrednictwem Chromium Embedded Framework w steamwebhelper proces — zob. Analiza techniczna DARKNAVY z dnia 27 czerwca 2024 r. ↗ oraz autorstwa Valve Steam Forum beta dla klientów ↗ zarchiwizowano 2025-08-04 ↗. Nie opiera się na żadnej wersji CEF: wbudowany Chromium to nie Chrome i nie zawiera żadnych usług Google dostępnych w Chrome. Bezpieczne przeglądanie bez kluczy API: Dokument projektowy Chromium ↗ zarchiwizowano 2026-08-21 ↗, Klucze API Chromium ↗ zarchiwizowano 2026-08-30 ↗ („Wiele interfejsów API Google wykorzystywanych przez przeglądarkę Chrome ma charakter specyficzny dla Google i nie jest przeznaczonych do stosowania w produktach pochodnych”), a ten sam efekt występuje w innych wersjach bez klucza — Beczka piwa domowej roboty nr 193814 ↗. Adresy URL do testów: testsafebrowsing.appspot.com ↗.\n\nDwa różne zegary\nWiek domeny.Data obserwacji.\n\nData utworzenia rejestru określa, kiedy domena została zarejestrowana. Wpis OpenID z datą określa host zwrotny w tym wpisie. Ta pierwsza data nie może obejmować lat poprzedzających tę drugą.\n\nKompletny rejestr rozróżnia oddzielną domenę podlegającą rejestracji, własną subdomenę witryny oraz bezpośrednią ścieżkę. Każdy wiersz zawiera link do źródła oraz wynik z serwisu DNS.\n\nSprawdź rejestr domen →· Pobierz daty wpisów w rejestrze ↗· Powtórz obserwację ↗\n\nCzęść A — Dokumentacja techniczna · Sekcja 4\nZakończono działanie punktu końcowego. W publicznym śledzeniu utracono klucz.\nOgraniczenia dotyczące kontekstu i źródła\n\nSteam wprowadzono zmiany, które ograniczyły publiczną widoczność identyfikatorów zasobów (Asset ID) oraz dostęp do API dotyczącej zapasów. W rezultacie śledzenie konkretnego przedmiotu na podstawie jego oryginalnego identyfikatora zasobu stało się niemożliwe na podstawie danych publicznych. Poniżej przedstawiono, co było możliwe wcześniej, co przestało być możliwe później oraz jakie koszty ponosi ofiara próbująca udowodnić, gdzie trafiła jej własność. Według konta inżynieryjnego CSFloat data ta to rok 2017; nie znaleziono żadnego dziennika zmian Valve. Ta sekwencja wydarzeń — mająca miejsce mniej więcej rok po oświadczeniu dotyczącym hazardu z lipca 2016 roku — stanowi przedmiot śledztwa, a nie ustalenie. Same zapisy dotyczące przedmiotów pozostają w systemach Valve; zewnętrzni śledczy stracili dostęp do łańcucha oryginalnych identyfikatorów, podczas gdy identyfikatory typu float, seed i paint pozwalają jedynie na częściowe dopasowanie.\n\nObowiązuje zasada Valve: Steam Dział pomocy technicznej nie przywraca elementów, które opuściły Twoje konto, a ciężar udowodnienia, co się stało, spoczywa na Tobie. Zapis: W 2017 roku serwis Valve zamknął punkt końcowy, który przekazywał oryginalne identyfikatory przedmiotów. Wcześniej każdy mógł prześledzić drogę skradzionej skórki z konta ofiary aż do bota działającego na platformie handlowej. Od tego czasu nikt spoza serwisu Valve nie ma takiej możliwości. Dokument, o który poproszono ofiarę, to ten, który został wyłączony — i nadal istnieje, wewnątrz Valve.\n\nOkres przed awarią zasilania\n\nW przeszłości każdy przedmiot wirtualny wygenerowany w Steam posiadał globalnie unikalny, niezmienny Identyfikator zasobu. Zewnętrzne bazy danych OSINT mogłyby indeksować te identyfikatory. Gdyby użytkownikowi skradziono jakiś przedmiot, śledczy mogliby prześledzić historię tego konkretnego zasobu, od momentu, gdy trafił on z pośredniego konta sprawcy kradzieży na konta magazynowe serwisu handlowego lub witryny hazardowej.\n\nWcześniej: każdy mógł prześledzić drogę danego przedmiotu z konta ofiary przez konta pośredniczące aż do bota magazynowego na platformie handlowej lub w kasynie, korzystając z danych publicznie dostępnych.\nPo wprowadzeniu zmiany\n\nZgodnie z informacjami zamieszczonymi na koncie inżynieryjnym CSFloat, Valve zamknęło punkt końcowy w 2017 roku, a oryginalne identyfikatory przedmiotów przestały być dostępne dla podmiotów zewnętrznych. Nie znaleziono żadnego oświadczenia Valve wyjaśniającego przyczynę tej zmiany. W tym samym okresie nie odnotowano również żadnych opublikowanych działań skierowanych przeciwko komercyjnym kontom botów, które przenosiły przedmioty na dużą skalę.\n\nNiezależnie od przyczyny, zmiana ta przerwała publiczny łańcuch dowodowy. Ofiara nie jest już w stanie odtworzyć łańcucha oryginalnych identyfikatorów na podstawie danych publicznych, aby wykazać, że konkretny skradziony przedmiot został zlikwidowany za pośrednictwem konkretnej platformy handlowej lub kasyna. Zapisy dotyczące przedmiotów nadal istnieją w systemach Valve; opinia publiczna, badacze i organy ścigania korzystające z danych publicznych nie mają do nich dostępu.\n\nPO: śledzenie konkretnego przedmiotu na podstawie jego pierwotnego identyfikatora zasobu (Asset ID) nie jest już możliwe na podstawie danych publicznych. Łańcuch dowodowy pierwotnego identyfikatora dla przedmiotu przeniesionego po 2017 r. istnieje wyłącznie w ramach infrastruktury Valve; żaden taki zapis nie został udostępniony publicznie. Identyfikatory typu „float”, „seed” i „paint” pozwalają jedynie na częściowe, probabilistyczne dopasowanie.\nIEconItems_730\nPOBRAĆ/IEconItems_730/GetPlayerItems/v1/\nŁadunek z możliwością śledzenia (wersja sprzed aktualizacji)\n\"id\": \"14892281934\",\n\"original_id\": \"11829910211\",\nStatus: Ofiara może prześledzić historię przepływu przedmiotu między kontami botów.\nZaszyfrowany ładunek (po zainstalowaniu poprawki)\nObecny\n\"id\": \"HIDDEN_BY_PRIVACY_SETTINGS\",\n\"original_id\": \"NULL\",\nStatus: osoby z zewnątrz nie mogą już śledzić historii pochodzenia pozycji na podstawie oryginalnego identyfikatora zasobu (Asset ID) na podstawie danych publicznych.\nWpływ na materiał dowodowy: Po wprowadzeniu zmiany publiczne dane niezbędne do prześledzenia konkretnego elementu na podstawie jego pierwotnego identyfikatora zasobu (Asset ID) – od konta ofiary aż po bot działający na platformie handlowej lub w kasynie – przestały być dostępne. Wewnętrzne zapisy nadal istnieją w Valve; ofiara, badacz lub śledczy korzystający z danych publicznych nie jest w stanie odtworzyć łańcucha oryginalnych identyfikatorów (identyfikatory typu float, seed i paint pozwalają jedynie na częściowe dopasowanie).\n\nŹródło: Raport inżynieryjny firmy CSFloat dotyczący zamknięcia w 2017 r. IEconItems_730/GetPlayerItems — blog.csfloat.com/how-floatdb-tracks-items (zarchiwizowano 2026-09-21) · przedstawione dane użytkowe służą jedynie do zilustrowania kształtu pola, a nie są rzeczywistymi odpowiedziami · nie znaleziono dziennika zmian Valve dla tego zamknięcia.\n\nCzęść A — Dokumentacja techniczna · Sekcja 5\nJedna sesja. Szerszy dostęp niż ten, który widzi użytkownik.\nOgraniczenia dotyczące kontekstu i źródła\n\nArchitektura kluczy API serwisu Valve, w stanie sprzed zmian wprowadzonych w 2023 r., odbiegała od podstawowych standardów branżowych (OWASP ASVS, NIST SP 800-63B) i stanowi mechanizm opisany w automatycznych zgłoszeniach kradzieży zapasów przechowywanych w archiwum dowodów (sekcje 6–8).\n\nZastosowano regułę Valve: posiadacz konta wygenerował klucz, zaakceptował warunki i ponosi stratę — taka jest odpowiedź zawarta w zarchiwizowanych odmowach. Zapis: do grudnia 2023 r. sam skradziony plik cookie sesji mógł wystarczyć do zarejestrowania tego klucza. Bez hasła. Bez Steam Guard. Bez powiadomienia właściciela konta. Użytkownik nie utworzył klucza, nie mógł go zobaczyć, a mimo to powiedziano mu, że to zrobił. Potwierdzenie mobilne dodano w dniu 2023-12-04 — około siedem lat po oświadczeniu z 2016 roku i mniej więcej sześć lat po panelach dotyczących oszustw, które archiwum przechowuje. Te lata nie zostały opłacone przez Valve. Opłacono je z kont, które w międzyczasie zostały opróżnione, a część z nich należała do dzieci.\n\nOWASP ASVS 2.8 / NIST SP 800-63BPOZIOM POWAŻNOŚCI: KRYTYCZNY\n1. Niewystarczające uwierzytelnianie wielopoziomowe\n\nSteam umożliwiało generowanie kluczy API o wysokim poziomie uprawnień i długim okresie ważności wyłącznie przy użyciu pliku cookie sesji. Podczas konfigurowania lub modyfikowania klucza API deweloperskiego nie było wymagane uwierzytelnianie dwuskładnikowe (Steam Guard) ani dodatkowe pytanie uwierzytelniające, więc potwierdzenie mobilne Steam Guard — jedyny drugi czynnik oferowany przez Steam — nie chroniło tego etapu. (W 2016 r. w systemie śledzenia zmian Valve zgłoszono prośbę o wprowadzenie sprzętowego drugiego czynnika, a zgłoszenie to pozostaje nadal otwarte: Załącznik D, GH-01.)\n\nStan: brak poprawki przed 2023 r. Umożliwiało skryptowi posiadającemu skradziony plik cookie zarejestrowanie klucza bez żadnej interakcji ze strony użytkownika.\nOWASP A01:2021 / Zasada minimalnych uprawnieńPOZIOM POWAŻNOŚCI: KRYTYCZNY\n2. Brak zasady minimalnych uprawnień\n\nW interfejsie API Steam brakowało jakichkolwiek zakresów autoryzacji opartych na rolach. Klucz API programisty wydany z uprawnieniami „tylko do odczytu” w zakresie stanu zapasów posiadał pełne uprawnienia „do zapisu” — w tym możliwość modyfikowania istniejących transakcji, inicjowania nowych, rejestrowania webhooków oraz odrzucania ważnych, oczekujących transakcji wymiany.\n\nStatus: systemowa wada projektowa. Jeden klucz = pełna kontrola nad stanem magazynowym i transakcjami na koncie (odczyt i zapis).\nOWASP A07:2021 / SesjePOZIOM POWAŻNOŚCI: WYSOKI\n3. Nieprawidłowe zarządzanie sesjami\n\nUżytkownicy zgłaszali, że sesje internetowe przejęte z zakresów adresów IP serwerów hostingowych nadal pozostawały aktywne. Standardową praktyką jest zamykanie sesji w przypadku wykrycia anomalii geograficznych oraz po zmianie hasła; zgłoszenia użytkowników zgromadzone w archiwum opisują sesje, które pozostały aktywne po zmianie hasła.\n\nStatus: zgłoszane zachowanie (skargi użytkowników w archiwum). Sesje mogły generować klucze API bez konieczności ponownego uwierzytelniania.\nBlokowanie na poziomie domeny było technicznie możliweMOŻLIWOŚĆ EGZEKWOWANIA\n4. Blokowanie hostów uwierzytelniających na poziomie domeny było technicznie wykonalne\n\nValve korzysta już z listy domen (filtru Link Filter) i otrzymuje każdą nazwę hosta uwierzytelniającą w ramach własnych żądań OpenID. Te dwa mechanizmy nie są w żaden sposób powiązane w sposób widoczny z zewnątrz: na dzień 2026-09-22 w 26 parach domena główna znajdowała się na liście filtru, podczas gdy serwer proxy obsługujący jej logowanie nie był na niej uwzględniony.\n\nPołączenie ich to proste zadanie techniczne: przeczytaj openid.realm pobierać nazwę hosta z każdego przychodzącego żądania, porównywać ją z listą oraz odrzucać lub oznaczać żądanie. Ilustracja po prawej stronie przedstawia przebieg takiej procedury. Odrzucenie hosta uwierzytelniającego — a nie tylko publicznej strony docelowej — spowodowałoby przerwanie etapu „Zaloguj się za pomocą Steam”, od którego zależą te platformy.\n\nNie ma żadnych publicznie dostępnych dowodów wskazujących, że Valve przeprowadza taką weryfikację. Łączna opłata Steam Community Market w wysokości około 15% dotyczy transakcji zawartych w ramach tej platformy; nie jest ona pobierana od transakcji zawieranych poza nią.\n\nblock_auth_hosts.pyILUSTRACJA\n// Odczytano, że host Steam już odbiera — nie przeprowadza się skanowania\ndef on_openid_request(request):\nhost = parse_openid_realm(request)\njeśli gospodarz w zablokowane_domeny:\nodmowa (wniosek)\nUwaga: Pseudokod służy wyłącznie do celów ilustracyjnych. Obie części istnieją już w Valve — nazwa hosta autoryzującego pojawia się w żądaniu, a lista domen stanowi filtr linków. Żaden publicznie dostępny zapis nie wyjaśnia, dlaczego nie są one ze sobą powiązane.\nSekcja 5.1 — Normy nie zostały wycofane z publikacji\nValve codziennie kompiluje się zgodnie z tymi regułami. W tym przypadku kompilacja nie przebiegła zgodnie z nimi.\n\nSteam jest dostępne w App Store i Google Play, prowadzi sprzedaż za pośrednictwem głównych operatorów płatności kartowych oraz korzysta z interfejsów API stron trzecich, podobnie jak każda inna duża platforma. Każda z tych relacji wiąże się z opublikowanymi, datowanymi wymogami bezpieczeństwa, które Valve musi spełniać, aby móc kontynuować działalność. Porównaj daty tych wymagań z datami, w których własny interfejs API serwisu Steam uzyskał te same zabezpieczenia. Żadna z poniższych pozycji nie stanowi prywatnego standardu, wewnętrznej notatki ani tajemnicy handlowej: każdy wiersz jest dokumentem publicznym opatrzonym datą publikacji.\n\nOpublikowane zewnętrzne wymagania bezpieczeństwa wraz z datami, zestawione z datą, w której interfejs API Steam uzyskał równoważny mechanizm kontroli\nOpublikowana norma oraz data jej wejścia w życie\tInterfejs API Steam dotyczący tego samego pytania\nUpoważnienie o określonym zakresieOAuth 2.0 — RFC 6749, październik 2012 r.. W sekcji 3.3 zdefiniowano scope dzięki czemu klient otrzymuje wyłącznie te uprawnienia, o które prosi. Od tamtej pory jest to domyślne ustawienie wszystkich głównych interfejsów API platform.\tZakresy szczegółowe pojawiły się w dniu 16 stycznia 2026 r..Wcześniej pojedynczy klucz API Steam zapewniał pełne uprawnienia do odczytu i zapisu w odniesieniu do transakcji na koncie, niezależnie od powodu, dla którego został wydany. Trzynaście lat i trzy miesiące po specyfikacji definiującej element sterujący.\nKlucz nie jest upoważnieniemDokumentacja Google dotycząca usługi Cloud: Standardowy klucz API nie służy do uwierzytelniania podmiotu, a także w przypadku interfejsów API, które tworzą zasoby lub zarządzają nimi, Nie należy używać kluczy autoryzacyjnych w środowisku produkcyjnym.\tKlucz API sieciowego Steam był właśnie tym.Ciąg znaków na okaziciela, przypisany do konta, wystarczający sam w sobie do odczytania stanu konta, anulowania oczekującej transakcji i wysłania nowej. W momencie użycia nie zweryfikowano tożsamości zleceniodawcy.\nUwierzytelnianie wieloskładnikowe w przypadku dostępu uprzywilejowanegoPCI DSS 3.2, wymóg 8.3 — obowiązkowy od 1 lutego 2018 r. w odniesieniu do wszelkich operacji administracyjnych wykonywanych poza konsolą oraz wszelkiego zdalnego dostępu do środowiska danych posiadaczy kart. Następnie firma Apple wprowadziła wymóg uwierzytelniania dwuskładnikowego dla każdego posiadacza konta w Programie dla deweloperów od 27 lutego 2019 r.: Programiści posiadający rolę „Właściciel konta” w programie dla programistów będą musieli włączyć uwierzytelnianie dwuskładnikowe, aby się zalogować.\tPotrzebny był drugi czynnik, aby utworzyć klucz API z 4 grudnia 2023 r..Do tego czasu wystarczało wykradzione plik cookie sesji – bez wyświetlania monitu na telefonie właściciela konta i bez późniejszego powiadomienia. Cztery lata i dziewięć miesięcy po tym, jak firma Apple wprowadziła wymóg stosowania drugiego czynnika uwierzytelniającego nawet przy samym logowaniu się do portalu dla deweloperów.\nCykl życia i unieważnianie certyfikatówSerwis Twitch wymaga od każdej aplikacji zewnętrznej: Aplikacja musi weryfikować token OAuth przy uruchomieniu, a następnie co godzinę, i zaznacza, że przeprowadza audyty aplikacji, które tego nie robią. Jego starsza wersja API v5 została całkowicie wycofana w dniu 28 lutego 2022 r. zgodnie z opublikowanym harmonogramem.\tBrak opublikowanych danych dotyczących cyklu życia klucza.Zmiana z 2023 r. zabezpieczyła punkt końcowy tworzenia. Nie znaleziono przy niej żadnej instrukcji Valve dotyczącej już zarejestrowanych kluczy, a zmiana ta nie została w ogóle opatrzona dziennikiem zmian. Na podstawie danych publicznych nie można ustalić, czy klucze utworzone przed tą zmianą zostały unieważnione — a właśnie na to pytanie osoba, której dane dotyczą, potrzebowałaby odpowiedzi, aby wiedzieć, czy klucz utworzony na jej koncie wiele lat wcześniej jest nadal aktywny.\nStandardy architektoniczne // Architektura oparta na tokenach\nSzczegółowe zakresy w GitHubie a Valve Steam Web API\n\nValve programistów codziennie zarządza oprogramowaniem open source na GitHubie, korzystając z precyzyjnie zdefiniowanych tokenów opartych na zasadzie minimalnych uprawnień. Porównajmy to z monolitycznym kluczem wydanym 130 milionom Steam graczy.\n\nToken o wysokim stopniu szczegółowości na GitHubie\nWykorzystane przez Valve na GitHubie\n\nToken o wysokim stopniu szczegółowości, charakteryzujący się izolacją w określonym zakresie oraz obowiązkowym egzekwowaniem cyklu życia.\n\nDostęp do repozytorium:Tylko wybrane repozytoria (1 repozytorium)\nUprawnienia do wydawania:Tylko do odczytu [✓]\nKod i tajemnice:Brak dostępu [✕]\nTermin ważności:30 dni (obowiązkowy czas ważności)\nRejestrowanie audytowe:Adres IP, agenta użytkownika i sygnał czasowy\nStan bezpieczeństwa: Token o minimalnych uprawnieniach ogranicza szkody do pojedynczego zasobu tylko do odczytu.\n!Valve Steam Klucz API sieci Web\nDostępne dla 130 mln użytkowników\n\nPojedynczy, 32-znakowy ciąg główny, zawierający uprawnienia do zawierania transakcji i zarządzania zapasami na zasadzie „wszystko albo nic”.\n\nDostęp do konta:KONTO PEŁNE (monolityczne)\nZarządzanie transakcjami:Przeczytaj, Anuluj, Odrzuć [!]\nZakresy szczegółowe:BRAK (przybył w 2026 r., z 13-letnim opóźnieniem)\nTermin ważności:NIGDY (Obowiązuje bezterminowo)\nRejestrowanie audytowe:BRAK (użytkownik nie ma historii adresów IP)\nLuka w zabezpieczeniach: Skradziony klucz umożliwia ciche przechwytywanie wszystkich wysyłanych ofert handlowych.\nNorma stosowana w jednym kierunku\n\nZałóżmy, że dostawca Valve — dostawca usług w chmurze, podmiot obsługujący płatności, sieć CDN — pozostawił punkt końcowy do uwierzytelniania bez drugiego czynnika, a kilka miesięcy później dane korporacyjne firmy Valve wyciekły za pośrednictwem klucza wygenerowanego w tym punkcie końcowym. Czy Valve zgodziłby się, że wina leży po stronie osoby, która kliknęła link? Zarchiwizowane odmowy zachowane w tej dokumentacji odpowiadają na lustrzane pytanie skierowane do użytkownika: przyjęto stanowisko, że to posiadacz konta utworzył klucz i ponosi stratę. Tę samą architekturę opisuje się jako awarię dostawcy z jednej strony i odpowiedzialność użytkownika z drugiej. To, czy tak jest, nie jest kwestią techniczną i nie jest to kwestia, którą niniejsze dochodzenie może rozstrzygnąć — decyzję w tej sprawie podejmuje sąd lub organ nadzorczy.\n\nIlustracja, a nie dowód — standard odczytany na odwrót\nSystem przetwarzania płatności, który umożliwił skryptowi strony trzeciej wygenerowanie danych uwierzytelniających do transakcji z pełnymi uprawnieniami wyłącznie na podstawie pliku cookie przeglądarki, bez wyświetlania monitu dla posiadacza konta.\nDostawca tożsamości, który zlikwidował lukę, przez którą wyemitowano jego tokeny, i nie opublikował żadnych informacji na temat tokenów już wyemitowanych.\nBank, który w odpowiedzi na zgłoszenie dotyczące spornego przelewu stwierdził, że użyte dane uwierzytelniające zostały zarejestrowane na koncie samego klienta, i zamknął zgłoszenie.\n\nŻadna z tych uwag nie stanowi wniosku dotyczącego konkretnej spółki. Są to te same decyzje projektowe, przeniesione do sytuacji, w której reakcja organu nadzorczego jest dobrze udokumentowana — i właśnie takie porównanie ma przeprowadzić organ regulacyjny.\n\nZ czego wynika z akt sprawy: mechanizmy kontroli, których brakowało w Steam Web API, były publiczne, przestarzałe, a w kilku przypadkach stanowiły warunki, które firma Valve musiała spełnić, aby móc nadal dostarczać swoje produkty. Odstęp czasowy między poszczególnymi standardami a odpowiadającymi im zmianami Steam jest mierzalny i został określony powyżej. Nie wyjaśnia to jednak, dlaczego tak się dzieje. Nie znaleziono żadnego uzasadnienia Valve dla żadnego z tych przedziałów i nie przyjmuje się tutaj żadnego; dokument ten znajduje się w Valve i nie został opublikowany.\n\nŹródła, z których każde jest dokumentem publicznym: OAuth 2.0 — RFC 6749, październik 2012 r. ↗ · Google Cloud — Dokumentacja dotycząca kluczy API ↗ · Wymóg 8.3 standardu PCI DSS 3.2 — Przewodnik po zasobach PCI SSC ↗ · Apple — Zbliżający się wymóg uwierzytelniania dwuskładnikowego dla posiadaczy kont, 20 lutego 2019 r. ↗ zarchiwizowano 2025-05-06 ↗ · Twitch — wymóg weryfikacji tokenu ↗ oraz Powiadomienie o wyłączeniu wersji 5 ↗ zarchiwizowano 2025-01-27 ↗. Daty podane przez Steam to te zawarte w zapisie aktualizacji w tej sekcji; wpisy z 2023 i 2026 r. to te, które Valve opublikował bez dziennika zmian. Pobrano 2026-09-22.\n\nWłasny wpis Valve — z datą, pochodzący ze źródeł publicznych\nData\tValve zmiana\tOgłoszono?\tCo zostało zamknięte\tOpóźnienie: mechanizm publiczny → naprawiono\tŹródło\n2026-09-01\tAutomatyczne oznaczanie podejrzanych rozmów\tTak\tNiebezpieczne linki / schematy w czatach grupowych\t—\taktualności ↗\n2026-01-16\tSzczegółowe zakresy interfejsu API Steamworks Web API\tTak\tZakresy uprawnień oparte na zasadzie minimalnych uprawnień dla kluczy programistycznych\t—\togłoszenie ↗\n2025-07-15\tCS2 – Ochrona transakcji i okno cofnięcia\tTak\tNic. Nie jest to rozwiązanie eliminujące podstawową przyczynę luki w zabezpieczeniach. Dostęp do odzyskiwania konta przez dział pomocy technicznej pozostaje bez zmian. Wywołanie cofnięcia transakcji powoduje automatyczne 30-dniowe zablokowanie możliwości zawierania transakcji (Skinvault ↗), podczas gdy wstrząs na rynku kasowym spowodował spadek kapitalizacji rynkowej o $104M (-25%) w ciągu 24 godzin (CSMarketCap ↗). W 2026 r. liczniki czasu zaczęto stosować indywidualnie dla każdego elementu (Skin.land ↗).\t—\tNajczęściej zadawane pytania ↗\n2025-05-14\tKomunikat dotyczący bezpieczeństwa konta\tTak\tWskazówki dotyczące programu Stealer / przejęcia sesji\t—\togłoszenie ↗\n2024-10-02\tCS2 „The Armory” – 7-dniowe wstrzymanie\tTak\tWstrzymaj handel/sprzedaż przedmiotów z Zbrojowni\t—\togłoszenie ↗\n2024-09-18\tOgraniczenie dotyczące logowania przy użyciu nowego urządzenia\tTak\t2–7-dniowe ograniczenie możliwości sprzedaży nowych urządzeń\t—\tNajczęściej zadawane pytania ↗\n2024-02-14\tWstrzymanie zmiany nazwy profilu i awatara\tTak\tPo zmianie nazwy obowiązuje 2–4-godzinny okres oczekiwania na transakcje\t—\twpis ↗\n2023-12-04\tPotwierdzenie za pomocą telefonu komórkowego w przypadku kluczy API\tBrak listy zmian\tCicha rejestracja klucza wyłącznie za pomocą plików cookie\t≈6 lat po panelach z okresu 2017 roku\tstrona deweloperska ↗\n2023-10-24\tSMS MFA w publikacjach dotyczących kompilacji gier\tTak\tPublikowanie kompilacji w serwisie Steamworks\t—\togłoszenie ↗\n2023-07-12\tOstrzeżenie dotyczące treści w niestandardowej biografii\tTak\tLinki phishingowe w opisach profilowych\t—\tforum ↗\n2023-01-25\tProfil {LINK USUNIĘTY} i czas odnowienia\tTak\tLinki w tekście profilu\t—\tNajczęściej zadawane pytania ↗\n2022-10-24\tPrzebudowa systemu logowania i skracanie plików cookie\tBrak listy zmian\tNieskończona liczba skradzionych sesji\t— (migracja tokenów w usłudze IAuthenticationService)\taktualności ↗\n2022-10-12\tAplikacja mobilna 3.0 – logowanie za pomocą kodu QR\tTak\tPanel cofania uprawnień sesji\t—\taktualności ↗\n2022-05-10\tUsunięto punkty końcowe anulowania transakcji\tBrak listy zmian\tWymiana oferty (anulowanie i ponowne wysłanie)\t≈5 lat po panelach z okresu 2017 roku\tnumer 325 ↗\n2020-05-25\t7-dniowa blokada wymiany w grze Dota 2\tTak\tSzybka odsprzedaż przedmiotów\t—\tblog ↗\n2018-03-29\t7-dniowa blokada handlu w CS:GO\tTak\tNatychmiastowe „pranie” botów\t≈20 miesięcy po oświadczeniu z lipca 2016 r.\tblog ↗ zarchiwizowano 2025-02-26 ↗\nŹródła: posty Valve, do których prowadzą linki, strony pomocy oraz zgłoszenia na GitHubie, zgodnie z podanymi datami. Trzy kluczowe poprawki zostały wprowadzone bez dziennika zmian (maj 2022, październik 2022, grudzień 2023) i zostały wykryte przez użytkowników, a nie ogłoszone przez Valve — ta asymetria stanowi część historii wprowadzanych zmian. Opóźnienia są obliczane wyłącznie w przypadkach, w których punktem początkowym jest data podana w samym dossier (oświadczenie z lipca 2016 r.; panele oszustw z okresu 2017 r.); znak „—” oznacza, że nie ustalono tutaj takiego punktu początkowego.\nCzęść A — Dokumentacja techniczna · Sekcja 6\nInteraktywny symulator ataków i przejęcia kontroli\nOgraniczenia dotyczące kontekstu i źródła\n\nRekonstrukcja ścieżki od wiadomości phishingowej do rejestracji klucza po stronie serwera i realizacji transakcji. Przed 2023 r. klucz Web API zarejestrowany na koncie mógł odczytywać stan zapasów, anulować oczekującą ofertę handlową i utworzyć nową, a posiadaczowi konta nie wyświetlał się ekran potwierdzenia transakcji w przypadku żadnej z tych czynności. Stanowi to naruszenie zasady minimalnych uprawnień (OWASP A01:2021). Czasy podane w tej symulacji mają charakter poglądowy i nie są rzeczywistymi pomiarami z obecnej platformy.\n\nPrzejrzyj krok po kroku odtworzony przebieg przejęcia konta. Każda faza pokazuje, co widzi właściciel konta, a obok tego – komunikat, który otrzymuje numer Steam w tym samym momencie. Każde z tych połączeń jest prawidłowo uwierzytelnione. Żadna część sekwencji nie wymaga, aby uwierzytelnianie Steam zakończyło się niepowodzeniem — konieczne jest jedynie, aby wydany przez nie klucz nie miał zakresu obowiązywania (OWASP A01:2021).\n\nTo, co widzi gracz. To, co zmienia się za jego plecami.SYMULATOR PRZEJŚCIA GRY\nKrok 5 / 5\n\nWykorzystanie luki zakończono. Spodziewając się powiadomienia na telefonie komórkowym dotyczącego pierwotnej transakcji, ofiara zatwierdza transakcję zastępczą. Jest to zintegrowana analiza kryminalistyczna pokazująca, w jaki sposób brak zasady minimalnych uprawnień (OWASP A01:2021) umożliwia zautomatyzowane przejęcie aktywów w czasie krótszym niż sekunda.\n\n01 / PRZYNĘTA DO CZATUZnajomy prosi o oddanie głosuOfiara otrzymuje wiadomość zawierającą link.\n02 / LOGOWANIEPortal z osobami o podobnym wyglądzieOfiara wprowadza dane logowania.\n03 / DOSTĘPTworzenie interfejsu API Silent WebAtakujący rejestruje klucz programisty.\n04 / ZMIANAWymiana w ramach legalnego handluBot „Clone” tworzy kopię docelowego odbiorcy.\n05 / POTWIERDZENIEZatwierdzono podróbkęNa telefonie zatwierdzono niewłaściwą ofertę.\nTen sam etap widziany z perspektywy sieciOdtworzenie schematu sprzed 2023 r. · przykładowe kształty sygnałów\nOfiaraZatwierdza komunikat wyświetlany na urządzeniu mobilnym, który miał pojawić się w przypadku pierwotnej transakcji.\nNapastnikOdbiera przedmioty na koncie klona.\nSteam widziPrzelew potwierdzony przez właściciela konta na zarejestrowanym urządzeniu.\nConfirmation genuine — made by the account holder\nRecipient the clone bot, not the intended counterparty\nThe confirmation is authentic. The offer it confirms is not the one the user initiated.\n\nPozostawiony po sobie ślad: transakcja zatwierdzona przez użytkownika. Jest to wpis Steam, który dział pomocy technicznej sprawdza po otrzymaniu zgłoszenia, a także powód, dla którego zarchiwizowane zgłoszenia zostały zamknięte jako wynikające z błędu użytkownika. Zgłoszenia znajdują się w archiwum egzekucji.\n\nCzęść A — Dokumentacja techniczna · Sekcja 7\nPunkty końcowe, które stanowią podstawę tej sekwencji.\nOgraniczenia dotyczące kontekstu i źródła\n\nOto punkty końcowe interfejsu API Steam, które wykorzystywane były przez zgłoszone skrypty przejmujące kontrolę w celu przechwytywania transakcji bez przechodzenia przez etapy potwierdzania po stronie przeglądarki.\n\nWystarczą cztery udokumentowane punkty końcowe. Żaden z nich nie stanowi luki, żadnego nie trzeba wykorzystywać — wywołuje je prawidłowy klucz, a Steam odpowiada. Klucz to jedyna rzecz, którą napastnik musiał ukraść.\n\nIEconService / GetTradeOffers / v1ANKIETA\n\nSłuży do monitorowania ofert handlowych na koncie. Skrypty wielokrotnie wysyłają zapytania do tego punktu końcowego przy użyciu przejętego klucza API; zwraca on szczegóły nowo utworzonych, oczekujących lub zmodyfikowanych ofert handlowych. Nie podano tutaj częstotliwości wysyłania zapytań.\n\nWektor zagrożenia: Wyświetla numery toczących się ofert handlowych oraz szczegóły profilu odbiorcy.\nIEconService / CancelTradeOffer / v1INTERAKCJA\n\nSłużyło to programowemu unieważnieniu prawidłowej oferty handlowej użytkownika. Przed 2023 r. klucz nie był chroniony za pomocą uwierzytelniania dwuskładnikowego, więc zautomatyzowany serwer mógł anulować ofertę natychmiast po jej wykryciu, bez wyświetlania jakiegokolwiek powiadomienia dla posiadacza konta.\n\nWektor zagrożenia: Anuluje transakcję, zanim posiadacz konta zakończy proces potwierdzenia za pomocą telefonu komórkowego.\nISteamUser / GetPlayerSummaries / v2RECON\n\nZapytano o nazwę profilu, adres URL zdjęcia profilowego oraz poziom uprawnionego odbiorcy transakcji. Dzięki temu skrypt może dostosować przygotowane konto-klon tak, by odpowiadało tym danym. Nie mierzy się tu czasu.\n\nWektor zagrożenia: Dostarcza dane niezbędne do podszywania się pod zamierzonego odbiorcę.\n/dev/ajaxregisterkeyTWORZENIE\n\nPunkt końcowy rejestracji kluczy Steam. W przeszłości każda aktywna sesja pliku cookie przeglądarki (`steamLoginSecure`) mogła zarejestrować klucz bez potwierdzenia Steam Guard na urządzeniu mobilnym i bez powiadomienia właściciela konta.\n\nWektor zagrożenia: Trwałe dane uwierzytelniające utworzone przez skrypt, o których właściciel konta nie ma pojęcia.\nCzęść A — Dokumentacja techniczna · Sekcja 8 · Artykuł 7 RODO\nZaznaczone pole wyboru. Czyja czynność?\nOgraniczenia dotyczące kontekstu i źródła\n\nW przypadku odmowy zwrotu kosztów, Steam W odpowiedziach działu pomocy technicznej zachowanych w archiwum przedstawiono stanowisko, że to posiadacz konta utworzył klucz API i, zaznaczając odpowiednie pole, zaakceptował warunki.\n\nW odpowiedzi działu pomocy technicznej przypisano klucz posiadaczowi konta. Pytanie brzmi, czy z dokumentacji wynika, kto faktycznie go utworzył.\n\nW zaobserwowanym schemacie przejęcia klucza API ofiara nigdy jednak nie widziała strony tworzenia klucza API ani nie przechodziła do niej. Pole zgody jest wysyłane przez skrypt wykonujący żądanie POST w trybie bezinterfejsowym przy użyciu skradzionego pliku cookie sesji.\n\nZgodnie z art. 7 oraz art. 4 ust. 11 RODO zgoda musi stanowić dobrowolne, konkretne, świadome i jednoznaczne wyrażenie woli osoby, której dane dotyczą. Autorzy stoją na stanowisku, że pole potwierdzające akceptację warunków, przesłane przez złośliwy skrypt przy użyciu skradzionego pliku cookie, bez wyświetlania strony posiadaczowi konta, nie może spełniać tej definicji. Ocena, czy tak jest, należy do organu nadzorczego.\n\nAnaliza ładunku w kontekście kryminalistycznym: Rejestracja klucza\nPOST https://steamcommunity.com/dev/ajaxregisterkey\n// Dane żądania (wprowadzone za pomocą skryptu przejmującego kontrolę)\n{\n\"agreeToTerms\": „zgadzam się”, <-- wprowadzone automatycznie, bez udziału człowieka\n„domena”: „localhost”, ← nie zweryfikowano — akceptowana jest dowolna wartość, w tym „localhost”\n„sessionid”: \"8f0d8ef763ab2140bf89de2a\"\n}\nPytanie skierowane do organu nadzorczego: czy w sytuacji, gdy posiadacz konta nigdy nie zaznaczył pola zgody, zapisana w odniesieniu do tego konta informacja o akceptacji warunków spełnia wymóg określony w art. 7 dotyczący dobrowolnego, konkretnego, świadomego i jednoznacznego wyrażenia woli osoby, której dane dotyczą, oraz czy dział obsługi klienta Steam może się na to powołać w celu odrzucenia roszczenia.\n\nŹródło: kształt klucza rejestracyjnego uzyskany na podstawie publicznego punktu końcowego oraz zgłoszeń dotyczących przejęcia kontroli, przechowywanych w archiwum dowodów (wersja z możliwością wyszukiwania 2026-09-17) · Wyświetlany identyfikator sesji jest symbolem zastępczym, a nie zarejestrowaną wartością.\n\nSekcja sądowa · Wektor substytucji handlowej\nJak Valve ostatecznie zneutralizowało „substytucję handlową” — i dlaczego zajęło to 7 lat stosowania rozwiązań obejściowych\n\nOd prawie dziesięciu lat „Podszywanie się pod klucz API” (lub oszustwo typu „man-in-the-middle” związane z API) był najbardziej dochodowym modelem kradzieży kont na Steam, pozwalającym na wyłudzenie setek milionów dolarów w postaci skórek od niczego niepodejrzewających graczy. W wersji Valve nie wyeliminowano tej luki poprzez naprawę podatnej na ataki architektury API; zamiast tego w wersji Valve spędzono siedem lat na wprowadzaniu czterech barier utrudniających transakcje na całej platformie, które sparaliżowały płynność handlu w społeczności, nie rozwiązując jednocześnie podstawowej przyczyny problemu.\n\n1. Śmierć przez naśladownictwo\nCzas odnowienia awatara i nazwy (luty 2024 r.)\n\nWykorzystanie tej luki wymagało działania w ułamku sekundy: bot oszukańczy przechwycił wychodzącą transakcję i pobrał awatar oraz nazwę odbiorcy za pomocą ISteamUser, a następnie sklonował profil w ciągu 200 ms. 14 lutego 2024 r. Valve po cichu wprowadził obowiązkowe 2–4-godzinny czas odnowienia transakcji (Błąd 34) bezpośrednio po każdej zmianie nazwy profilu lub awatara. Bot nie może już klonować odbiorcy w locie bez zablokowania sobie możliwości prowadzenia transakcji.\n\n2. Gospodarcza zagłada\n7-dniowe odwrócenie trendu w CS2 (lipiec 2025 r.)\n\nValve wprowadził jednostronnie Odwrócenia trendów w przypadku przedmiotów z gry Counter-Strike. Każda wymieniona skórka jest oznaczona jako „Chroniona przed wymianą” przez siedem dni. Jeśli ofiara wykryje podmianę, klika opcję „Cofnij transakcję” w sekcji pomocy Steam, a skórka natychmiast wraca do jej ekwipunku, a odbiorca zostaje zablokowany. Ponieważ 7-dniowa blokada wymiany uniemożliwia oszustom przeniesienie przedmiotu na stronę umożliwiającą spieniężenie, kradzież staje się nieopłacalna.\n\n3. Śmierć „Cichego Klucza”\nObowiązkowe powiadomienia push w aplikacjach mobilnych dla API (grudzień 2023 r.)\n\nW przeszłości skradziony plik cookie sesji umożliwiał złośliwym skryptom wykonanie bezinterfejsowego żądania POST w tle do /dev/ajaxregisterkey bez powiadamiania ofiary. 4 grudnia 2023 r. firma Valve wprowadziła wymóg wyraźnego potwierdzenia powiadomienia push w aplikacji mobilnej Steam w celu wygenerowania klucza API sieciowego, co wyeliminowało ciche przydzielanie kluczy w tle.\n\n4. Ostrzeżenia wyświetlane w aplikacji mobilnej\nBanery z nazwą i stażem konta (2022–2024)\n\nValve zmodyfikowano okno potwierdzenia w wersji mobilnej tak, aby wyświetlało dane partnera handlowego Steam okres istnienia konta (data utworzenia), poziom Steam oraz wyraźne ostrzeżenie w kolorze bursztynowym: „Ten użytkownik niedawno zmienił nazwę swojego profilu”, co pozwala uważnym ofiarom przejrzeć tę iluzję optyczną.\n\nTrzy wady „patchworku” Valve: dlaczego oszuści po prostu zmienili cele\n1. Luka w systemie wykluczeń z gier (Dota 2 i TF2)\n\nFunkcja „Trade Reversals” została wprowadzona wyłącznie w grze Counter-Strike 2. Przedmioty w grach „Dota 2” i „Team Fortress 2” pozostają całkowicie niezabezpieczone ze względu na złożoność procesu tworzenia i osadzania kamieni. Przedmioty najwyższej klasy warte tysiące dolarów (Haki Smoczych Pazurów, Złote Małe Roshany, niezwykłe płonące płomienie z TF2) nie podlegają żadnemu okresowi na cofnięcie transakcji. Oszuści po prostu przekierowali automatyczne przechwytywanie API na handlowców z Dota 2 i TF2, gdzie dział pomocy technicznej Steam rygorystycznie egzekwuje swoją politykę z 2016 roku dotyczącą „braku przywracania przedmiotów”.\n\n2. Rezerwuar „Zombie Key” (bez terminu ważności)\n\nPodczas gdy Valve wprowadziło mobilne uwierzytelnianie dwuskładnikowe (2FA) za pomocą powiadomień push w celu wygenerowania nowy klucze w grudniu 2023 r., Valve istniejących starszych kluczy API, które nigdy nie zostały unieważnione, nie straciły ważności ani nie zostały usunięte. Miliony aktywnych kont, które wygenerowały klucze (lub na których klucze zostały utworzone w tle przez oprogramowanie phishingowe lub złośliwe przed grudniem 2023 r.), nadal posiadają aktywne dane uwierzytelniające z brak terminu ważności (brak TTL) i zerowy limit czasu bezczynności. Osoby stanowiące zagrożenie prowadzą ogromne archiwalne bazy danych zawierające te trwałe klucze i nadal je sprawdzają IEconService niezakłócony.\n\n3. Kara dla ofiary: 30-dniowy zakaz zawierania transakcji\n\nNawet w CS2 opcja Valve nakłada karę na oszukanego gracza: kliknięcie przycisku „Cofnij transakcję” w sekcji pomocy Steam automatycznie powoduje obowiązkowe 30-dniowe zawieszenie możliwości prowadzenia transakcji oraz dostępu do rynku wspólnotowego na koncie ofiary. Valve nakłada na użytkownika karę w postaci miesięcznego wykluczenia z platformy, co ma stanowić środek odstraszający przed „nieuzasadnionymi” unieważnieniami transakcji i zniechęcać ofiary do unieważniania transakcji dotyczących płynnych przedmiotów o niższej wartości.\n\nGłówny skandal regulacyjny: siedem lat obejść przepisów kontra jeden zakres API\n\nDlaczego firma Valve poświęciła siedem lat na opracowywanie mechanizmów blokujących transakcje, okresów karencji dla kont oraz odwracalnych blokad transakcji — co zakłóciło funkcjonowanie całej ekonomii gry i spowodowało spadek kapitalizacji rynkowej o $104 mln — zamiast wdrożyć rozwiązanie zgodne ze standardami branżowymi?\n\nJak potwierdza oficjalna premiera gry Valve w serwisie Steamworks, która miała miejsce 16 stycznia 2026 r. (Ogłoszenie #493839547938902179 ↗), Valve już wybudowane Grupy uprawnień szczegółowych (Ogólne, Mikrotransakcje, Gospodarka, Dane dotyczące sprzedaży) oraz Biała lista adresów IP w przypadku kluczy wydawcy dla firm. Valve od lat dysponowało odpowiednim rozwiązaniem technicznym. Jedno pole wyboru widoczne dla użytkownika —„Zablokuj dostęp tego klucza API sieciowego do usługi IEconService (zarządzanie transakcjami)” lub domowa lista białych adresów IP — wyeliminowałyby oszustwo związane z substytucją handlową w 2018 roku bez żadnych ubocznych szkód gospodarczych. Valve odmówiło zapewnienia zwykłym graczom ochrony, którą opracowało dla partnerów korporacyjnych.\n\nCzęść B — Przepisy i historia egzekwowania · Sekcja 9\nIch regulamin. Zarejestrowane platformy.\nOgraniczenia dotyczące kontekstu i źródła\n\nW niniejszym rejestrze przyporządkowano klauzule jawne z pliku Steam Umowa abonamentowa (SSA) oraz Steam Zachowanie w sieci (SOC) wytyczne skierowane bezpośrednio przeciwko aktywnym podmiotom gospodarczym działającym na dużą skalę.\n\nZasada: zakaz wykorzystywania w celach komercyjnych, zakaz hazardu, zakaz stosowania botów — a Steam Dział obsługi klienta powołuje się na te klauzule, gdy odmawia zwrotu przedmiotów ofierze. Zapis: te same klauzule, na pierwszy rzut oka, obejmują platformy komercyjne wpisane do tego rejestru, które działają w oparciu o Steam tożsamości, Steam boty i Steam transfery. Klauzula ta ma zastosowanie wobec osoby, która utraciła skóry, a nie – zgodnie z żadnymi opublikowanymi danymi – wobec przedsiębiorstw zajmujących się ich transportem.\n\nW zarchiwizowanych skargach dział pomocy technicznej Steam powołuje się na „Zakaz wykorzystania w celach komercyjnych” oraz „Żadnej automatyzacji ani botów” klauzule stosowane przy odmowie przywrócenia przedmiotów ofiarom oszustw związanych z kluczami API. Te same klauzule mają, co do treści, zastosowanie do platform komercyjnych ujętych w niniejszym dossier, które uwierzytelniają użytkowników za pomocą Steam OpenID i przenoszą przedmioty za pośrednictwem zautomatyzowanych Steam kont. W niniejszym dokumencie nie oszacowano ogólnych przychodów rynkowych (patrz poniższe statystyki dotyczące egzekwowania przepisów). Dokumentacja pokazuje jedynie zasady stosowane wobec poszczególnych kont w zarchiwizowanych sprawach, a nie opublikowane dane dotyczące egzekwowania przepisów w odniesieniu do poszczególnych operatorów platform. Niniejsza sekcja dokumentuje właśnie tę asymetrię.\n\nKluczowe pytanie / wybiórcze egzekwowanie prawaZasady → Skala → Odpowiedzialność\nJeden zbiór przepisów. Nierówne ich egzekwowanie.\n\nRejestr wskazuje, że usługi komercyjne wykorzystują tożsamości typu Steam, zasoby, boty i transfery jako infrastrukturę operacyjną. SSA zabrania komercyjnego wykorzystywania i automatyzacji bez zezwolenia. Zarchiwizowane skargi wskazują, że zasada ta miała zastosowanie do kont indywidualnych, podczas gdy w rejestrze publicznym nie ma odpowiednika dla poszczególnych operatorów w odniesieniu do platform opisanych w niniejszym dokumencie. Należy opublikować przepis, dowody oraz decyzję w sprawie egzekwowania przepisów dla każdego z nich.\n\n189strony internetowe objęte audytem\n44trasy z odrębnych domen w rejestrze „live” — 27 z opublikowanym plikiem dowodowym, 17 zebranych ręcznie. Już sam audyt przeglądarki obejmujący 189 stron internetowych pozwolił rozwiązać 25 z nich; rejestr uzupełnia go o trasy zebrane ręcznie.\n12 lat i 6 miesięcycsgogem.com zablokowano w filtrze linków; api.csgem.com zarejestrowana 2014-03-08 i nigdy nie zablokowana — jedna z 26 takich par na dzień 2026-09-22\nBrak zweryfikowanej sumyz wyłączeniem szacunków dotyczących przychodów całego rynku\nSteam Zachowanie w sieci\n„…nie wolno ci podejmować ani próbować podejmować żadnego z poniższych działań w serwisie Steam: […] Prowadzić działalność komercyjną. Przykłady takich zabronionych zachowań obejmują: zamieszczanie ogłoszeń; organizowanie konkursów; hazard; kupowanie lub sprzedawanie kont Steam; sprzedawanie treści, kart podarunkowych lub innych przedmiotów; oraz żebranie.\"\n\nstore.steampowered.com/online_conduct ↗ zarchiwizowano 2026-09-21 ↗\n\nSSA § 2.G — Wykorzystanie komercyjne\n„…[nie wolno] wykorzystywać Treści i Usług ani żadnej ich części do jakichkolwiek celów komercyjnych, z wyjątkiem przypadków wyraźnie dozwolonych w innych postanowieniach niniejszej Umowy…”\n\nJak informowaliśmy, w zawiadomieniach Valve z 2016 r. powołano się na licencję osobistą, niekomercyjną. Żaden operator nie przedstawił w aktach sprawy zezwolenia Valve. store.steampowered.com/subscriber_agreement ↗ zarchiwizowane 2026-09-18 ↗\n\nSteam Warunki korzystania z interfejsu API serwisu internetowego\n„Nie wolno korzystać z Steam interfejsu API ani Steam danych w sposób naruszający postanowienia Steam umowy abonamentowej”.\n\nZewnętrzne platformy sprzedaży skórek działają za pośrednictwem zautomatyzowanych kont korzystających z interfejsu API Steam. Treść zasady nie przewiduje żadnych wyjątków dotyczących działalności na skalę komercyjną. steamcommunity.com/dev/apiterms ↗ zarchiwizowano 2026-09-21 ↗\n\nSSA § 4.C\nAutomatyzacja\n\nSkrypty, boty i interakcje niepochodzące od ludzi są ograniczone. W rejestrze odnotowywane są transakcje przeprowadzane przez boty, farmy kont oraz automatyczne przekierowywanie na skalę komercyjną.\n\nSprawdzić 153zapisy oznaczone tą klauzulą ↗\nCo przewiduje ta klauzula153 oznaczone platformy\nOtwarcie sprawy15\nSkin Casino13\nRynek CS29\nRuletka skórna8\ncsgoempire.com→csgoempirelogin4.comKasyno\nrollbit.com→rbsnin.comKasyno kryptowalutowe\n500.casino→fivezerozero.coKasyno z licencją\n\nSpośród nich, 153 są również oznaczone tagiem „SSA § 2.G” oraz 2 są również oznaczone zgodnie z §1.C ustawy SSA — te same usługi są objęte więcej niż jednym punktem, dlatego przykłady się powtarzają.\n\n28 zaobserwowano przypadki korzystania z serwisu „153” poprzez uwierzytelnianie za pomocą oddzielnej domeny podlegającej rejestracji. Etykieta odnotowuje datowaną obserwację, która sprawia, że platforma podlega postanowieniom tej klauzuli w jej dosłownym brzmieniu; nie jest to stwierdzone naruszenie, a w żadnym z tych przypadków nie przedstawiono zezwolenia wydanego przez Urząd ds. Łączności (Valve).\n\nSSA § 2.G\nWykorzystanie komercyjne\n\nWykorzystanie komercyjne wymaga wyraźnej zgody. Należy porównać opisane modele biznesowe, ich skalę oraz wszelkie ujawnione informacje dotyczące upoważnień lub egzekwowania praw.\n\nSprawdzić 175zapisy oznaczone tą klauzulą ↗\nCo przewiduje ta klauzula175 oznaczone platformy\nOtwarcie sprawy15\nSkin Casino13\nRynek CS29\nRuletka skórna8\ncsgoempire.com→csgoempirelogin4.comKasyno\nrollbit.com→rbsnin.comKasyno kryptowalutowe\n500.casino→fivezerozero.coKasyno z licencją\n\nSpośród nich, 153 są również oznaczone tagiem „SSA §4.C” oraz 24 są również oznaczone zgodnie z §1.C ustawy SSA — te same usługi są objęte więcej niż jednym punktem, dlatego przykłady się powtarzają.\n\n28 zaobserwowano przypadki korzystania z serwisu „175” poprzez uwierzytelnianie za pomocą oddzielnej domeny podlegającej rejestracji. Etykieta odnotowuje datowaną obserwację, która sprawia, że platforma podlega postanowieniom tej klauzuli w jej dosłownym brzmieniu; nie jest to stwierdzone naruszenie, a w żadnym z tych przypadków nie przedstawiono upoważnienia na podstawie ustawy o usługach internetowych (Valve).\n\nSSA § 3.A\nVPN i ukrywanie lokalizacji\n\nUkrywanie lokalizacji za pomocą serwerów proxy IP może skutkować zablokowaniem dostępu. Hosty uwierzytelniające w oddzielnych domenach wymagają osobnej analizy: należy ustalić, co jest ukrywane i która zasada ma zastosowanie.\n\nSprawdź dane dotyczące hosta uwierzytelniającego ↗\nSteam Pomoc / Zasady dotyczące adresów URL\nZaszyfrowanie linków\n\nSteam zabrania stosowania serwisów skracających linki oraz narzędzi, które ukrywają miejsca docelowe linków. Oddzielna domena autoryzacyjna — rbsnin.com w procesie logowania w serwisie Rollbit, auth.dota.trade w CS.MONEY — rodzi podobne pytanie, czy miejsce docelowe wskazane weryfikatorowi OpenID użytkownika Steam identyfikuje witrynę, na której toczy się operacja.\n\nZasady dotyczące adresów URL serwisu Valve ↗\n\nOdniesienia do przepisów: Steam Umowa abonamentowa, wersja z 10 września 2026 r. zarchiwizowano 2026-09-18 ↗ · Steam Warunki korzystania z interfejsu API serwisu internetowego zarchiwizowano 2026-09-21 ↗ · Steam Zasady dotyczące adresów URL (maskowanie linków). Liczby te odnoszą się do dokumentów i tagów zawartych w tej dokumentacji; nie są one liczbą rozpatrytych naruszeń.\n\nDeficyt zaufania\nKto dokonuje weryfikacji decyzji po zamknięciu sprawy przez dział wsparcia?\n\nZachowane zgłoszenia dotyczą stałych sankcji, pozostawionych bez odpowiedzi odwołań oraz odmowy zwrotu skradzionych przedmiotów. Należy zweryfikować te relacje w oparciu o faktyczną historię zgłoszeń, dostępne środki zaradcze oraz logi dostępu do konta. Ogólne wyjaśnienie dotyczące phishingu nie pozwala ustalić, kto zainicjował reset lub utworzył klucz API.\n\nPrzeczytaj zgłoszone skargi ↗Poproś o udostępnienie dokumentacji źródłowej →Wykres relacji moderatorów →\nCzęść B — Przepisy i historia egzekwowania · Sekcja 10\nInterfejs API do automatyzacji. Zasada zakazująca automatyzacji.\nOgraniczenia dotyczące kontekstu i źródła\n\nW niniejszym rozdziale poruszono kwestię, w jaki sposób można pogodzić te dwa aspekty: jakie zastosowania API są dozwolone, przez kogo oraz na podstawie jakich opublikowanych kryteriów. Nie oszacowano tutaj liczby autoryzowanych komercyjnych użytkowników API, a brak opublikowanej listy nie sugeruje żadnej konkretnej liczby — sam brak stanowi ustalenie, a nie liczbę, która się za nim kryje. Cytowane powyżej wiadomości z pomocy technicznej Steam zostały przytoczone przez projekt ArchiSteamFarm w jego własnym FAQ (zweryfikowane dosłownie 2026-09-22); nie są to Valve publikacje, a konta, na które zostały wysłane, nie zostały zidentyfikowane.\n\nPrzepis (SSA § 4.C): żadnych skryptów, żadnych botów, żadnych systemów niebędących ludźmi na Steam. Zapis: Valve udostępnia bezgłowy interfejs API REST, którego jedynym celem jest automatyzacja komunikacji między serwerami, i przekazuje klucz do dowolnego konta. Użytkownicy są blokowani za stosowanie automatyzacji; interfejs do automatyzacji jest produktem firmy Valve. Nigdy nie opublikowano informacji o tym, jakie zastosowania komercyjne są dozwolone.\n\nBłędne przekonanie dotyczące „twórców gier”\nSteamworks SDK (oryginalne)\n\nWykorzystywane przez renomowane studia gier do wdrażania osiągnięć, systemu dobierania graczy i tabel wyników w swoich klientach gier. Wymaga skomplikowanej integracji z językiem C++ oraz oficjalnego procesu wdrożenia partnera.\n\nSteam Interfejs API sieci Web (Luka)\n\nArchitektura JSON/REST typu „headless”, zaprojektowana z myślą o zewnętrznych serwerach internetowych. W opisanym tutaj schemacie ataku typu „hijack” służy ona do odczytywania stanów zapasów i manipulowania transakcjami typu peer-to-peer z serwerów zdalnych; jej legalne zastosowania nie zostały ujęte w niniejszym dossier.\n\nDla kogo jest ten kluczZwykły użytkownik Steam nie potrzebuje klucza Web API w samym kliencie; strona z kluczami znajduje się pod adresem przeznaczonym dla programistów, a jej udokumentowanym przeznaczeniem jest zewnętrzny dostęp po stronie serwera. Zarchiwizowane zgłoszenia dotyczące przejęcia kont opisują przypadki ofiar, które nie wiedziały o istnieniu tej strony, dopóki klucz nie został zarejestrowany na ich koncie.\nSprzeczność automatyzacji\n\n§ 4.C SSA stanowi, co następuje: „Nie wolno w żaden sposób wykorzystywać żadnych skryptów, botów, makr ani innych systemów niekontrolowanych przez człowieka („automatyzacja”) do interakcji z treściami i usługami na stronie Steam”. Jednak punkty końcowe interfejsu API sieci Web (takie jak CancelTradeOffer) nie wymagają interfejsu użytkownika ani kodu CAPTCHA i całkowicie omijają klienta Steam. Interfejs API jest przeznaczony do automatyzacji między serwerami; zasada zabrania automatyzacji przez użytkowników; granica między tymi dwoma obszarami nie została ujawniona.\n\nRola serwera w procesie transakcyjnym\n\nKlucz API sieci Web umożliwia serwerowi zewnętrznemu wykonywanie operacji handlowych na koncie bez udziału klienta Steam. W scenariuszu przejęcia kontroli serwer ten znajduje się pomiędzy posiadaczem konta a serwerem transakcyjnym.\n\n→W przypadku operacji wykonywanych za pomocą klawisza nie wyświetla się ekran potwierdzenia transakcji.\n→Umożliwia odpytywanie w tle (GetTradeOffers).\n→Anuluje i ponownie generuje oferty bez udziału użytkownika.\nValve stworzyło interfejs, w swoich zasadach zakazało użytkownikom stosowania automatyzacji i nie opublikowało żadnych kryteriów określających, jakie rodzaje wykorzystania komercyjnego są dozwolone.\nCzęść B — Przepisy i historia egzekwowania · sekcja 11\nWymagano dziesięciu dni. Trzeba było rozliczyć się z dziesięciu lat.\nOgraniczenia dotyczące kontekstu i źródła\n\n20 lipca 2016 r. radca prawny Valve wyznaczył operatorom gier hazardowych 10-dniowy termin. Dziesięć lat później (według stanu na moment sporządzenia dokumentacji, 2026-09-21) co najmniej jedna platforma wymieniona w doniesieniach prasowych dotyczących tego zawiadomienia, CSGOFast, nadal działa, korzystając z serwera uwierzytelniającego w oddzielnej domenie. Treść zawiadomienia została poniżej odtworzona na podstawie doniesień prasowych z 21 lipca 2016 r.; odtworzona treść nie jest skanem. Dokumentacja dotycząca egzekwowania przepisów, o której mowa w zawiadomieniu, nie została opublikowana. List otwarty do Komisji brzmi: Sekcja 2.\n\nProszę zapoznać się z ogłoszeniem z lipca 2016 r., zamieszczonym obok późniejszych uwag. Nadal oczekuje się na zestawienie wyników egzekwowania przepisów w podziale na poszczególnych operatorów.\n\nTydzień wcześniej — 13 lipca 2016 r., publicznie\n\nW dniu 13 lipca 2016 r. zarchiwizowano 2026-09-21 ↗, Valve opisał, w jaki sposób serwisy hazardowe wykorzystywały Steam: OpenID do identyfikacji kont oraz zautomatyzowane konta do prowadzenia transakcji. Valve stwierdził, że wykorzystywanie tych mechanizmów do prowadzenia działalności hazardowej stanowiło naruszenie jego warunków korzystania z API oraz umów użytkownika. Zarówno opis mechanizmu, jak i zakaz zawarte są we własnym, opatrzonym datą oświadczeniu Valve. W przypadku 2026-09-21 testowane hosty uwierzytelniające z oddzielnych domen nie zwróciły żadnego bloku filtru łącza, a Valve nie opublikował żadnego rekordu egzekwowania dla poszczególnych operatorów.\n\nZAŁĄCZNIK A / LIPIEC 2016REKONSTRUKCJA SKŁADU DRUKOWEGO\nVALVE CORPORATION\n\nBellevue, stan Waszyngton\n\nDATA:Lipiec 2016 r. (doniesienia prasowe z 21 lipca 2016 r.)\nOD:Karl Quackenbush, główny radca prawny\nRE:Wezwanie do zaprzestania — komercyjne wykorzystywanie kont Steam\nUWAGA:Rekonstrukcja tekstu na podstawie zgłoszenia; nie jest to skan\n\n„Wiemy, że prowadzisz jedną z wymienionych poniżej stron hazardowych. Wykorzystujecie Państwo Steam kont do prowadzenia tej działalności. Zgodnie z Steam Umową abonamentową usługi Steam i Steam są licencjonowane wyłącznie do użytku osobistego, niekomercyjnego.”\n\n„Powinieneś natychmiast zaprzestać dalszego wykorzystywania swoich kont Steam do jakichkolwiek celów komercyjnych. Jeśli tego nie uczynisz, w ciągu dziesięciu (10) dni, Valve podejmie wszelkie dostępne środki prawne, w tym między innymi zamknięcie Państwa kont.”\n\nRekonstrukcja dokumentacji · zapoznaj się z dokumentem źródłowym\nKarl Quackenbush\nDyrektor ds. prawnych, Valve Corp.\nNA MARGINESIE / ARTYKUŁ REDAKCYJNY\nDziesięć dni.No to co dalej?\n\nTermin był jasno określony. Tak samo powinno być w przypadku działań podejmowanych przez społeczeństwo.\n\nOpublikowane stanowisko Valvea w sprawie „2016” ↗\nUwaga dotycząca terminu +\nSATYRA / NIE JEST TO KORESPONDENCJA Z VALVE\n\nDrogi terminie,\n\nDano ci dziesięć dni. Z jakiegoś powodu kalendarz był jedyną rzeczą, która nadal działała.\n\nProszę o przekazanie wszelkich odpowiedzi do rejestru publicznego.\n\nOś czasulipiec 2016 r. – wrzesień 2026 r.\nTermin podany w ogłoszeniu:\n10 dni\nlipiec 2016 r.\nCzas, jaki upłynął od daty ogłoszenia:\n3,715 dni\nLiczba ustalona na okres od 20 lipca 2016 r. do momentu utworzenia kopii zapasowej dokumentacji z dnia 21 września 2026 r.; nie jest to wartość aktualna\nOpublikowane dane dotyczące egzekwowania przepisów:\nBrak\nNie znaleziono danych dotyczących zakończeń połączeń ani blokad w podziale na operatorów\n\n◀ Dni 0–10 — termin, w skaliDzień 3715 — migawka ▶\n\n20 lipca 2016 r.Wydano dziesięciodniowe wezwanie do zapłatyDzień 0\n17 lutego 2024 r.Obowiązują zobowiązania wynikające z DSADzień 2,768\n25 lutego 2026 r.Ogłoszono skargę prokuratora generalnego stanu Nowy JorkDzień 3,507\n21 września 2026 r.Podsumowanie dokumentacjiDzień 3715\n\nDziesięć lat później, CSGOFast — wymieniona w doniesieniach prasowych dotyczących powiadomień z 2016 r. — działa: strona csgofast.com zwróciła komunikat o zablokowaniu przez filtr linków dla 2026-09-19 i 2026-09-21, podczas gdy jej host uwierzytelniający steam-login.authtofast.com (zarejestrowany 2026-06-30) tego nie zrobił.\n\nPełny, opatrzony datą zapis zmian dotyczących zabezpieczeń użytkownika Valve: Kalendarium wydarzeń związanych z bezpieczeństwem → · Orzecznictwo Sądu Okręgowego w Waszyngtonie i standard egzekwowania prawa: poniżej\n\nZgodnie z dokumentacją: W zawiadomieniu z 2016 r. wyznaczono 10-dniowy termin; Valve prowadziło już listę domen (Link Filter) i otrzymywało autoryzowane nazwy hostów w ramach własnych żądań OpenID; nie opublikowano żadnych danych dotyczących egzekwowania przepisów w podziale na operatorów. W raportach społeczności opisano działanie podjęte w 2018 r. przeciwko platformie handlowej (SkinJar), jednak raporty te nie zostały zweryfikowane i nie są brane pod uwagę w niniejszym dokumencie.\nCSGOFAST / TRASA UZYSKANIA AUTORYZACJI\nPostępuj zgodnie z podanym serwerem docelowym.\n\nLinki do zapisanych tras csgofast.com do steam-login.authtofast.com. Oddzielna nazwa hosta jest przekazywana w żądaniu OpenID o numerze Steam. Daje to śledczym konkretny adres, który mogą porównać z danymi dotyczącymi filtrowania i egzekwowania przepisów zawartymi w żądaniu o numerze Valve.\n\nZapoznaj się z trasą CSGOFast i jej źródłem ↗ · Porównaj zapisane Steam Wyniki filtru linków ↗\n\nREJESTR PUBLICZNY / WASZYNGTON · 2016 → 2026\nDwa terminy. Jedna nieokreślona norma egzekucyjna.\n20 LIPCA\nValve przyznaje serwisom hazardowym 10 dni\n\nW wezwaniu wysłanym przez prawnika firmy ostrzegano, że dalsze wykorzystywanie kont Steam do celów komercyjnych może skutkować zamknięciem konta.\n\n27 września\nWaszyngton naciska Valve\n\nStanowa Komisja ds. Hazardu zażądała przedstawienia dowodów na podjęcie działań mających na celu powstrzymanie transferów „skinów” w celach hazardowych i wyznaczyła termin na udzielenie odpowiedzi do 14 października.\n\n17 października\nValve odrzuca zarzut\n\nValve udzieliło odpowiedzi po upływie terminu, zaprzeczyło, jakoby ułatwiało hazard, poinformowało, że zablokowało powiązane konta, oraz stwierdziło, że nie zamierza wyłączać handlu i usługi OpenID dla wszystkich użytkowników. Co najmniej jedna platforma wymieniona w doniesieniach prasowych dotyczących lipcowych zawiadomień (CSGOFast) działała nadal dziesięć lat później. Oba fakty mogą mieć miejsce tylko wtedy, gdy operator zastąpił zablokowane konta; dokumentacja, która by to potwierdzała, nie została opublikowana. WSGC powinna zwrócić się do Valve o wyjaśnienie tej sprzeczności.\n\n2026\nTrasy zaobserwowane we wrześniu 2026 roku\n\nW rejestrze tras odnotowano 44 platformy uwierzytelniające się za pośrednictwem serwerów uwierzytelniających z odrębnych domen, w tym CSGOFast, z wykorzystaniem mechanizmów OpenID i handlu Valve opisanych w 2016 roku. Nie przedstawiono rejestru egzekwowania, który wskazywałby, którym operatorom odcięto dostęp.\n\nWŁASNA NOTATKA INFORMACYJNA KOMISJI · 30 STYCZNIA 2018 R.\nOsiemnaście miesięcy po udzieleniu odpowiedzi przez Valve organ regulacyjny nadal określał to jako zamiar.\n\nPodczas przesłuchania publicznego w sprawie projektu ustawy HB 2881, w ramach briefingu dla własnego organu ustawodawczego, Komisja opisała oświadczenie z lipca 2016 r. własnymi słowami: Valve „ogłosiła zamiar podjęcia zdecydowanych działań przeciwko wykorzystywaniu jej platformy do organizowania hazardu związanego ze skórkami”. Na tej samej stronie opisano, jak ogłoszenie to wpłynęło na prognozy branżowe — „w rezultacie”, prognoza dotycząca rynku gier hazardowych typu „skin” na rok 2020 została skorygowana z $19.7 miliardów do $670 mln, co oznacza spadek o około 97 procent – wyłącznie w wyniku samego ogłoszenia. Prognoza uległa zmianie. Dane dotyczące egzekwowania przepisów w przeliczeniu na jednego operatora, które uzasadniałyby tę zmianę, nadal nie zostały opublikowane.\n\nDane rynkowe to szacunki firm Narus Advisors oraz Eilers & Krejcik Gaming przytoczone w briefingu Komisji, a nie ustalenia samej Komisji; w tym samym dokumencie wartość zakładów z wykorzystaniem skórek w 2016 r. oszacowano na około $5 mld, z czego około $3 mld przypadło na serwisy typu kasynowego. Pobrano 2026-09-22, SHA-256 c507c9025f93da0aadaf395c4d8882f25973211c318ee8e9b6f18a5b3755e050.\n\nMożna porównać publiczne stanowisko Valve z 2016 roku z infrastrukturą, którą można dziś zaobserwować. Pytanie brzmi, czy działania egzekucyjne objęły konta i trasy wykorzystywane przez operatorów objętych zakazem. Dziesięciodniowy termin zawiadomienia nie stanowi dowodu na to, że zawiadomienie zostało przekazane wszystkim wymienionym w nim operatorom. Działanie podjęte przez OPSkins w 2018 roku stanowi jedyną udokumentowaną interwencję skierowaną przeciwko konkretnemu operatorowi; biorąc pod uwagę 189 sprawdzonych platform i brak opublikowanych danych dotyczących poszczególnych operatorów, pojedyncze udokumentowane działanie nie wskazuje na istnienie określonego schematu egzekwowania przepisów.\n\nOgłoszenie Komisji ds. Hazardu stanu Waszyngton z 2016 r. ↗ zarchiwizowane 2026-05-20 ↗ · Odpowiedź Valve z dnia 17 października 2016 r. (kopia dokumentu) ↗ · Prezentacja WSGC przed zgromadzeniem ustawodawczym, 30 stycznia 2018 r. (kopia lokalna, 4 strony) ↗ · ten sam plik na stronie wsgc.wa.gov ↗ · rekord wyszukiwania i skrót ↗ · Akcja Valve na OPSkins z 2018 r. ↗ zarchiwizowano 2026-03-07 ↗ · Aktualny przegląd trasy ↗\n\nAudyt śledczy o charakterze podłużnym · Podmioty objęte nakazem zaprzestania działalności z 2016 r.\nDekada „10-dniowego zawiadomienia”: kryminalistyczny audyt gotowości 23 wskazanych obiektów\n\nW dniach 19–20 lipca 2016 r. Valve główny radca prawny Karl Quackenbush wystosował formalne wezwania do zaprzestania działalności skierowane do 23 platform hazardowych typu „skin”, nakazując im zaprzestanie komercyjnego wykorzystywania kont Steam w ramach 10 dni pod groźbą zamknięcia konta i podjęcia kroków prawnych. Ponad 3,700 dni później empiryczna kontrola ujawniła rzeczywisty przebieg egzekwowania przepisów: wielu operatorów nigdy nie zaprzestało działalności, inni działali nawet przez sześć lat po upływie terminu, a wart wiele miliardów dolarów ekosystem nadal korzystał z architektury OpenID firmy Valve.\n\n5+ NA ŻYWO\nZ pewnością będą działać w 2026 r. (CSGOBig, CSGO500, CSGOFast itp.)\n6 LAT\nNajdłuższy okres działania serwisu po ogłoszeniu zamknięcia (CSGOatse działało do 2022 r.)\n$5.01B\nWielkość obrotów z zakładów na skórki w 2016 r. (Narus / Eilers & Krejcik)\nPonad 200\nAktywne serwisy hazardowe działające w szczytowym okresie koniunktury rynkowej\n„The Surviving Titans” · Plan finansowy i strategiczny dotyczący ruchu na lata 2024–2026\nOd 10-dniowych ostrzeżeń po zagraniczne konglomeraty: obroty rzędu wielu miliardów dolarów\n\nZamiast wyeliminować hazard oparty na skinach, komunikaty Valve z 2016 roku stały się katalizatorem przemian w branży. Operatorzy, którzy przetrwali, przekształcili się w podmioty offshore (Curaçao, Belize, Cypr), byli pionierami handlu typu peer-to-peer (P2P) w celu obejścia zakazów dotyczących botów, a obecnie przetwarzają ponad 10 milionów odwiedzin miesięcznie oraz miliardy dolarów rocznego obrotu z zakładów przy jednoczesnym kontynuowaniu uwierzytelniania za pośrednictwem Steam:\n\nPlatforma / Domena\tOgłoszenie z lipca 2016 r.\tWynik egzekucji i status przeżycia\tWeryfikacja zarejestrowana / Główne linki\nCSGOBig\ncsgobig.com\t10-dniowe zawiadomienie (lipiec 2016 r.)\tWCIĄŻ ŻYJĘ W 2026 ROKU\nTymczasowo zawieszone, ponownie uruchomione; uwierzytelnianie odbywa się za pośrednictwem serwisów letmeinbig.com i csgobiglogin.com\tX: @csgobig ↗ · FB: csgobigofficial ↗\nCSGO500\ncsgo500.com / 500.casino\t10-dniowe zawiadomienie (lipiec 2016 r.)\tWCIĄŻ ŻYJĘ W 2026 ROKU\nZmieniło nazwę na 500 Casino (licencja z Curaçao nr 8048/JAZ2014-037), miesięczny obrót sięgający wielu milionów\tPlatforma na żywo (500.casino) ↗\nCSGOFast\ncsgofast.com\t10-dniowe zawiadomienie (lipiec 2016 r.)\tWCIĄŻ ŻYJĘ W 2026 ROKU\nAktywnie obsługujemy ruletkę, grę „Crash” i jackpot za pośrednictwem strony steam-login.authtofast.com\tAudyt autoryzacji dokumentacji ↗\nCSGOLounge / Dota2Lounge\ncsgolounge.com / dota2lounge.com\t10-dniowe zawiadomienie (lipiec 2016 r.)\tWCIĄŻ ŻYJĘ W 2026 ROKU\nSkupiono się na zakładach związanych z e-sportem opartych na kryptowalutach oraz na zakładach kryptowalutowych; zapewniono nieprzerwaną działalność\tPlatforma na żywo ↗\nCSGOCasino\ncsgocasino.net / csgocasino.gg\t10-dniowe zawiadomienie (lipiec 2016 r.)\tNA ŻYWO PRZEZ SUCCESSOR (2026)\nDomena została przekierowana; aktywny portal zastępczy działa pod adresem csgocasino.gg\tDomena następcza ↗\nCSGOatse\ncsgoatse.com\t10-dniowe zawiadomienie (lipiec 2016 r.)\tDZIAŁAŁO PRZEZ 6 LAT (AKTYWNE DO 2022 R.)\nDziałalność hazardowa była prowadzona w pełnym zakresie przez sześć lat po 10-dniowym ultimatum wydanym przez Valve\tX: @CSGOatsecom (aktywne do 2022 r.) ↗\nCSGOSweep\ncsgosweep.com\t10-dniowe zawiadomienie (lipiec 2016 r.)\tDZIAŁAŁ DO GRUDNIA 2017 R.\nDziałało publicznie przez 17 miesięcy po upływie terminu\tX: Stan CSGOSweep – grudzień 2017 r. ↗\nCSGOWild\ncsgowild.com\t10-dniowe zawiadomienie (lipiec 2016 r.)\tDZIAŁAŁ DO GRUDNIA 2017 R.\nPromowany przez czołowych influencerów; funkcjonował przez 1,5 roku po otrzymaniu wezwania do zaprzestania naruszeń, zanim nastąpiła migracja do świata kryptowalut\tX: @Wild (aktywny od grudnia 2017 r.) ↗\nCSGOPot\ncsgopot.com\t10-dniowe zawiadomienie (lipiec 2016 r.)\tPRZETRWAŁ DO WRZEŚNIA 2017 R.\nProwadził działalność w zakresie zakładów z wysokimi stawkami i jackpotami przez 14 miesięcy po otrzymaniu zawiadomienia\tX: @csgopot (aktywny we wrześniu 2017 r.) ↗\nCSGODiamonds\ncsgodiamonds.com\t10-dniowe zawiadomienie (lipiec 2016 r.)\tPRZETRWAŁ DO POŁOWY 2017 ROKU\nTrwało przez cały rok 2017, mimo przyznania się do manipulowania wynikami na korzyść sponsorowanych streamerów\tX: @csgodiamondscom (2017) ↗\nCSGOLotto\ncsgolotto.com\t10-dniowe zawiadomienie (lipiec 2016 r.)\tZAMKNIĘTE W LIPCU 2016 R.\nZamknięto w wyniku publicznego skandalu; przedmiot federalnego nakazu ugody wydanego przez Federalną Komisję Handlu (FTC)\tPorozumienie z Federalną Komisją Handlu (FTC) (sprawa nr C-4632) ↗\nCSGODouble\ncsgodouble.com\t10-dniowe zawiadomienie (lipiec 2016 r.)\tZAMKNIĘTE W LIPCU 2016 R.\nDobrowolne zaprzestanie działalności natychmiast po opublikowaniu wezwania do zaprzestania działalności\tX: @CSGODouble (zamknięte w lipcu 2016 r.) ↗\nCSGOMassive\ncsgomassive.com\t10-dniowe zawiadomienie (lipiec 2016 r.)\tZAMKNIĘTE W 2016 R.\nPod koniec 2016 r. zaprzestała działalności publicznej\tX: @csgo_massive ↗\nCSGOStrong\ncsgostrong.com\t10-dniowe zawiadomienie (lipiec 2016 r.)\tZAMKNIĘTE W 2016 R.\nW 2016 r. zaprzestała działalności publicznej\tFB: csgostrongfree ↗\nSkins2\nskins2.com\t10-dniowe zawiadomienie (lipiec 2016 r.)\tZAMKNIĘTE 2016\nW 2016 r. zaprzestała działalności publicznej\tFB: CSNCOM ↗\n\nPlatforma\tMiesięczny ruch (odwiedziny)\tSzacowany obrót / wielkość sprzedaży\tPodmiot prawny i jurysdykcja\tNajważniejsze działania regulacyjne i model\nCSGOEmpire\ncsgoempire.com\t2,3 mln — 9,0 mln miesięcznie\nŚredni czas trwania: 6+ min; 80% bezpośrednie\t$1.5B — $2.5B Roczny obrót\n>1,000,000 transakcji wymiany skórek w systemie P2P miesięcznie; $6.4 mln aktywnych, płynnych zleceń na parkiecie\tMoonrail Limited B.V. (Curaçao nr 148182)\nPłatności: JHOLT LTD (Cypr); Założyciel: „Monarch” (Ossi Ketola)\tPionier w dziedzinie handlu przedmiotami P2P bez prowizji; licencja wydana na Curaçao nr OGL/2024/1183/0869\nCSGORoll\ncsgoroll.com\t2,74 mln — 3,5 mln miesięcznie\nŚredni czas trwania: 9 min 23 s; współczynnik odrzuceń: 16%\t$1.0B — $2.0B Roczny obrót\nSzacowane roczne przychody firmy z tytułu przewagi kasyna w wysokości od $100M do $200M\tFeral Holdings Limited\nSiedziba firmy znajduje się w Belize City w Belize (nr rejestracyjny 171519)\tZablokowany przez australijską agencję ACMA (maj 2023 r.); sponsorował drużynę pierwszej ligi G2 Esports, w której grali nieletni zawodnicy\n500 Casino (CSGO500)\n500.casino / csgo500.com\t220 tys. — 425 tys. / miesiąc\n~105 tys. unikalnych użytkowników miesięcznie\t$100k / tydzień ($5.2M/rok) w Royales\nWymóg obrotu dla graczy o wysokich stawkach: $400 obrotu na każdy $1 rakeback\tPerfect Storm B.V. (Curaçao nr 150536)\nLicencja wydana przez Komisję Nadzoru Gier na Curaçao nr OGL/2024/1354/0882\tZablokowany przez szwedzki urząd Spelinspektionen (listopad 2023 r.) za nielegalne kierowanie oferty do szwedzkich graczy\nCSGOBig\ncsgobig.com\t~169,600 / miesiąc\nŚredni czas trwania: 19 min 12 s; prawybory w USA\tRoczny wolumen sprzedaży sięgający wielu milionów\nPudełka-niespodzianki, ruletka i bitwy o skrzynie\tDziała w oparciu o pomocnicze routowanie proxy\nletmeinbig.com (zarejestrowana w 2023 r.) i csgobiglogin.com\tCel z lipca 2016 r. – C&D; ponownie uruchomiony z architekturą autoryzacji przez pełnomocnika\nCSGOFast\ncsgofast.com\t~150 tys. — 250 tys. miesięcznie\nMiędzynarodowa, wielojęzyczna publiczność\tRoczny wolumen rzędu wielu milionów\nRuletka o wysokiej prędkości i gry typu „crash”\tPodmioty operacyjne prowadzące działalność na morzu\nTrasy Steam uwierzytelnianie przez steam-login.authtofast.com\tPrzedmiot nakazu zaprzestania działalności z lipca 2016 r.; działalność nigdy nie została wstrzymana; nadal działa w 2026 r.\nCSGO Polygon\ncsgopolygon.com / plg.bet\t~300 tys. — 500 tys. miesięcznie\nDominacja krajów WNP i Europy Wschodniej\tRoczny wolumen rzędu wielu milionów\nKrypto i ruletka ze skórkami, zakłady na mecze\tCel drugiej fali (październik 2016 r.)\nSkupiliśmy się na kryptowalutach, korzystając z domeny lustrzanej plg.bet\tPrzetrwało całą dekadę; nadal zajmuje się likwidacją zasobów poprzez interfejsy API stron trzecich\n„Druga fala”: dlaczego wezwanie do zaprzestania naruszeń wysłane przez Valve dotyczyło łącznie ponad 43 stron internetowych\n\nW dniu 17 października 2016 r. pełnomocnik prawny Valve oficjalnie poinformował Komisję ds. Hazardu stanu Waszyngton, że po wysłaniu pierwszych 23 zawiadomień w dniu 19 lipca firma Valve wysłała pisma z żądaniem zaprzestania działalności do ponad 20 kolejnych serwisów hazardowych z skinami (co spowodowało, że oficjalna liczba przekroczyła 43). Ta druga fala okazała się konieczna, ponieważ na pierwotnej liście w niewytłumaczalny sposób pominięto największe i najbardziej znane ośrodki hazardowe na świecie:\n\nCSGOJackpot.com: Historyczny pionier w dziedzinie „skin jackpots”, który obsługiwał transakcje o wartości setek milionów, zanim musiał zakończyć działalność w obliczu groźby postawienia w stan oskarżenia przez władze federalne.\nCSGOShuffle.com: Strona, która znalazła się w centrum skandalu związanego z transmisjami na żywo z lipca 2016 r., gdzie streamer serwisu Twitch o pseudonimie PhantomL0rd potajemnie posiadał 33% udziałów w firmie i został przyłapany na manipulowaniu kursami przy użyciu środków własnych.\nEkosystem makro (ponad 200 operatorów): Według badań branżowych przeprowadzonych przez Narus Advisors oraz Eilers & Krejcik Gaming, w 2016 roku działało ponad 200 różnych serwisów hazardowych opartych na skórach, które wygenerowały $5.01 miliardów w obrocie z zakładów od 3,03 miliona aktywnych graczy. 43 listy firmy Valve dotyczyły mniej niż 20% aktywnego rynku.\nOficjalne dochodzenia rządowe i regulacyjne w sprawie Steam hazardu skórnego\n\nZjawisko hazardu internetowego zostało udokumentowane w wielu oficjalnych dochodzeniach ustawowych, działaniach egzekucyjnych oraz rządowych dokumentach stanowiskowych:\n\n1. Komisja ds. Hazardu Stanu Waszyngton (WSGC) (2016–2018)\n\nW dniu 5 października 2016 r. wystosowano formalne wezwanie do zaprzestania działalności; w dniu 30 stycznia 2018 r. opublikowano opracowanie legislacyjne, w którym stwierdzono, że skórki są ekwiwalentami gotówki, oraz podano, że wolumen zakładów zawieranych przy użyciu skórek wyniósł $5.0B.\n\nRaport legislacyjny WSGC w formacie PDF (kopia lokalna) ↗\n2. Federalna Komisja Handlu Stanów Zjednoczonych (FTC) (wrzesień 2017 r., sygn. akt C-4632)\n\nPierwsze federalne postępowanie egzekucyjne w sprawie hazardu internetowego, wszczęte przeciwko właścicielom serwisu CSGOLotto, Trevorowi Martinowi i Thomasowi Cassellowi, w związku z praktykami wprowadzającymi w błąd oraz nieujawnionym sprawowaniem kontroli nad platformą.\n\nDecyzja i ugoda FTC ↗\n3. Dokument przedstawiający stanowisko Brytyjskiej Komisji ds. Hazardu (UKGC) oraz audyty dotyczące młodzieży\n\nW grze skiny zostały formalnie zaklasyfikowane jako „pieniądze lub ich odpowiednik” na mocy ustawy o grach hazardowych z 2005 r. Późniejsze badania wykazały, że ponad 11% dzieci w wieku 11–16 lat obstawiało skiny w grach wideo.\n\nRepozytorium badań UKGC ↗\n4. Postępowanie wyjaśniające Senatu Australii w sprawie środowiska i komunikacji (2018)\n\nRaport parlamentu federalnego w sprawie „Mikrotransakcje w grach dotyczące przedmiotów przyznawanych losowo”, oceniając mechanikę skrzynek z łupami w grze Valve, wypłaty środków na rynku wtórnym oraz sposoby obchodzenia przepisów.\n\nPostępowanie wyjaśniające Parlamentu Australii ↗\nNiespłacone należności\n\nOpublikować protokół egzekucyjny: które konta hazardowe i boty zostały zablokowane, które serwery zwrotne zostały objęte ograniczeniami oraz które usługi komercyjne otrzymały zezwolenie. Publiczny zakaz i ostrzeżenie na stronie głównej nie stanowią dowodu na to, że podstawowa działalność została wstrzymana.\n\nCzęść B — Przepisy i historia egzekwowania · Sekcja 12\nNazwa hosta jest już zawarta w żądaniu.\nOgraniczenia dotyczące kontekstu i źródła\n\nValve prowadzi już listę domen (filtr linków) i otrzymuje nazwę hosta uwierzytelniającego w każdym żądaniu OpenID. Poniższy pseudokod przedstawia logiczny schemat połączenia tych dwóch elementów. Nie ma żadnych publicznie dostępnych dowodów na to, że Valve tak postępuje.\n\nValve prowadzi już listę zablokowanych domen. Valve otrzymuje już adres hosta logowania w każdym żądaniu OpenID. Nie trzeba niczego budować — wystarczy je połączyć. Jest to wyszukiwanie nazwy hosta na podstawie listy, którą Valve sam aktualizuje. Poniższy pseudokod ma charakter ilustracyjny i nie stanowi implementacji Valve.\n\nforensic_autoban.py\n# PSEUDOKOD ILUSTRACYJNY — Valve.block_domain() i flag_session_as_mitm() nie są rzeczywistymi wywołaniami API. Ilustruje to strukturę logiczną środka zaradczego, który Valve mógłby wdrożyć w odniesieniu do domen uwierzytelniania proxy, a nie rzeczywistą strukturę wewnętrzną Valve.\n# Ilustracja: schemat logiczny sprawdzania przychodzącego żądania OpenID\ndef audit_openid_request(prośba):\nblocked_origins = database.pobierz_platformy_z_czarnej_listy()\nproxy_domain = request.params.pobierz(„openid.realm”)\ntarget_redirect = request.params.pobierz(„openid.return_to”)\n\n# Logika: Jeśli serwer proxy przekierowuje z powrotem do zablokowanej witryny, należy zablokować ten serwer proxy.\ndla strona w blocked_origins:\njeśli strona w target_redirect:\nValve.blokuj_domenę(domena_proxy)\nValve.oznacz_sesję_jako_MITM(request.session)\n# Wynik: żądanie logowania dla tego hosta zostało odrzucone\n\nUwaga:\nJeśli domena główna znajduje się już w filtrze linków (np. howl.gg, zablokowana 2026-09-18/19/21), a jej host uwierzytelniający (howl.uno) pojawia się w żądaniu OpenID wysyłanym przez przycisk logowania tej witryny, powiązanie to jest widoczne dla Valve na podstawie danych z własnego żądania. Sprawdzanie to można zautomatyzować; nie można jednak zautomatyzować decyzji o tym, czy ma ono zostać przeprowadzone.\nUdokumentowane i zgłoszone przypadki\n\nValve co najmniej raz w przeszłości podjął działania wobec zewnętrznego operatora: w 2018 roku cofnął firmie OPSkins dostęp do systemu ExpressTrade (Ogłoszenie Valve ↗ zarchiwizowano 2026-03-07 ↗). W doniesieniach społeczności z 2018 roku opisano również przypadek utraty dostępu przez platformę handlową (SkinJar); doniesienia te nie zostały zweryfikowane, a mechanizm tego zdarzenia wywnioskowano na podstawie jego skutków, a nie na podstawie ujawnionego procesu.\n\nCo wynika z tego precedensu:\n\nValve może zablokować dostęp operatorowi zewnętrznemu, gdy tylko uzna to za stosowne. Serwis CSGOFast, wymieniony w doniesieniach prasowych dotyczących zawiadomień z lipca 2016 r., działał na 2026-09-21 z hostem autoryzacyjnym zarejestrowanym na 2026-06-30, który nie zwracał blokady filtru linków. Żadne opublikowane kryteria nie wyjaśniają, dlaczego jeden operator został odcięty, a inni nie.\n\nCo wynika z daty rejestracji, a czego z niej nie wynika\n\nData rejestracji hosta uwierzytelniającego stanowi dolną granicę czasu, w którym host mógł po raz pierwszy pojawić się w żądaniu OpenID; nie oznacza to jednak ciągłego użytkowania. sc-auth.net, na przykład, został zarejestrowany jako 2019-04-02 (RDAP) i zaobserwowano go we Steam procesie logowania serwisu Skin.Club we wrześniu 2026 r.; nie ma publicznie dostępnych informacji na temat tego, co wydarzyło się w okresie między tymi dwiema datami.\n\nAudyt porównawczy: standardy zgodności z API\nAspekt egzekwowania prawa\tZasady korzystania z API serwisu GitHub\tSteam Interfejs API sieci Web (Valve)\n1. Neutralność pod względem zgodności z przepisami\tOpublikowane, jednolite zasady. Udokumentowane limity częstotliwości (np. 5,000 wywołań na godzinę dla uwierzytelnionych użytkowników, 15,000 na godzinę dla organizacji korzystających z GitHub Enterprise Cloud) oraz opublikowane zasady dopuszczalnego użytkowania mają zastosowanie do każdego konta.\tBrak opublikowanych kryteriów. Poszczególne konta są zamykane na podstawie klauzul dotyczących automatyzacji i wykorzystania komercyjnego (zarchiwizowane skargi), natomiast nie opublikowano żadnych danych dotyczących egzekwowania przepisów w podziale na operatorów w odniesieniu do platform komercyjnych.\n2. Nadużycia związane z OpenID / serwerem proxy uwierzytelniającym\tZgodnie z opublikowanymi zasadami serwisu GitHub aplikacje i tokeny OAuth mogą zostać zawieszone lub unieważnione w przypadku nadużyć, a w dokumentacji serwisu opisano automatyczne unieważnianie ujawnionych tokenów (podsumowanie dokumentacji serwisu GitHub sporządzone przez autorów).\tHosty uwierzytelniające z odrębnych domen, zaobserwowane w Steam procesach OpenID (np. rbsnin.com, howl.uno, sc-auth.net), nie spowodowały zablokowania przez filtr Link Filter w 2026-09-21, podczas gdy ich główne domeny spowodowały takie zablokowanie.\n3. Czerpanie zysków z nadużyć\tGitHub nie pobiera żadnych opłat transakcyjnych za pozycje przenoszone przez narzędzia automatyzacyjne stron trzecich; jego model przychodów opiera się na subskrypcjach i ofertach na platformie handlowej.\tValve sprzedaje klucze do skrzynek, z których można uzyskać przedmioty, a Rynek Społeczności pobiera łączną opłatę w wysokości około 15% od transakcji zrealizowanych na terenie Rynku. Nie oszacowano tutaj przychodów przypisanych platformom zewnętrznym.\n4. Okresy ważności pętli unikania\tZawieszone identyfikatory klientów OAuth przestają działać na całej platformie w momencie zawieszenia; w dokumentacji nie podano czasu na podjęcie działań i w niniejszym dokumencie nie przyjęto żadnego założenia w tej kwestii.\tW przypadku hostów uwierzytelniających z oddzielnymi domenami, których daty rejestracji obejmowały okres od 2011 r. do września 2026 r., podczas kontroli 2026-09-19 i 2026-09-21 nie stwierdzono żadnych blokad wynikających z filtru linków. Data rejestracji stanowi dolną granicę możliwego okresu użytkowania, a nie dowód ciągłego użytkowania.\nŹródła: Artykuł na GitHubie — opublikowana przez GitHub dokumentacja dotycząca limitów wykorzystania API oraz zasad korzystania z platformy (podsumowanie autorów, bez cytatów) · Artykuł Steam — Sprawdzenie filtrów linków w 2026-09-19 i 2026-09-21 (linkfilter-recheck-2026-09-21.json), rejestr RDAP (domain-registration.json) oraz zarchiwizowane zgłoszenia do pomocy technicznej (archiwum dowodów).\nCzęść B — Przepisy i historia egzekwowania · Sekcja 13\nRóżnica cenowa w stosunku do 0\n\nPrzedmiot znajduje się w ekwipunku Steam; sprzedaż odbywa się gdzie indziej. Fabrycznie nowy AWP Dragon Lore miał 62 aktualne oferty na CSFloat; najniższa cena wywoławcza $10,623.95. Na rynku Steam nie można podać ceny wywoławczej wyższej niż około $1,800. Aby sprzedać przedmiot po zaobserwowanej wyższej cenie, właściciel musi znaleźć nabywcę spoza Steam lub skorzystać z innej platformy handlowej. Sam przedmiot i jego przekazanie nadal zależą od Steam.\n\nOgraniczenia dotyczące kontekstu i źródła\n\nW tej sekcji występują trzy różne pozycje, które nie są zamienne. 245 to liczba kategorii nazw produktów CS2, w których najtańsza aktywna oferta przekroczyła wartość $1,800 wyłącznie w serwisie CSFloat, 20 września 2026 r. 241 jest to ten sam zbiór pomniejszony o cztery kategorie przypięte do górnej granicy $100,000 w CSFloat, która stanowi panel, na podstawie którego obliczana jest dolna granica $13.63M. 248 to inny obraz sytuacji: kategorie, których ceny przekraczały limit na co najmniej dwóch z pięciu platform handlowych w dniu 23 września 2026 r. Platformy te pokrywają się, dlatego nie wolno sumować danych z różnych miejsc. Każda podana tutaj liczba stanowi cenę wywoławczą, a nie cenę, za jaką doszło do sprzedaży, i żadna z nich nie stanowi przychodu, obrotu ani zysku — ani dla Valve, ani dla nikogo innego. Wartości podane przez PriceEmpire to zaokrąglone szacunki opublikowane przez tę stronę, a jej karta Steam obejmuje przedmioty z innych gier Steam, więc zakresy porównania nie są identyczne.\n\nJeden produkt. Dwa systemy cenowe.ŚLEDŹ WYNIKI\nKrok 3 / 3\n\nW tej sytuacji sprzedawca potrzebuje platformy lub nabywcy spoza Steam. Produkt nadal zależy od zasobów magazynowych i systemu transferu Steam.\n\nSTEAMO $1,800Opublikowany limit liczby ofert na rynku społecznościowym\nZAPISANY KATALOG$10,623.95Nowy, fabrycznie nowy model AWP Dragon Lore – proszę o cenę\nZALEŻNOŚĆWciąż jest to pozycja SteamStan magazynowy i przeniesienie pozostają na poziomie Steam\n01 / POZYCJAValve spis gierPrzedmiot z CS2 lub Dota 2 znajdujący się w Steam\n02 / SUFITO $1,800 w dniu SteamMaksymalna cena za jedną ofertę na platformie Market\n03 / ZAPYTANIE ZEWNĘTRZNE$10,623.95 dla „Dragon Lore”Najtańsza oferta CSFloat w zrzucie ekranu z danej daty\n04 / DOSTAWASteam pozostaje w łańcuchuWłasność i przenoszenie przedmiotów opierają się na tym systemie\nARCHITEKTURA RYNKU · MOMENTALNY ZRZUT Z DATĄ, 20 WRZESIEŃ 2026\nRóżnica w cenie jest wymierna.\n\nZliczyliśmy kategorie nazw produktów, w których najtańsza aktywna oferta wynosiła dokładnie powyżej1,800.. Strony CSFloat oraz Skinport to odrębne migawki zawierające nakładające się zasoby CS2; ich liczb nie można sumować. Oferty zewnętrzne wskazują miejsca, w których podawane są wyższe ceny wywoławcze, natomiast strona Steam nadal zarządza własnością i transferem przedmiotów.\n\n245KATEGORIE CS2 · CSFLOAT\n166KATEGORIE CS2 · SKINPORT\n3DOTA2KATEGORIE · SKINPORT\n$10,623.95Pytania dotyczące DRAGON LORE FLOOR\n\nDragon Lore: Strona 62 zawiera aktualne oferty serwisu CSFloat w kategorii „Factory New”; podana cena minimalna jest ceną wywoławczą, a nie potwierdzoną ceną sprzedaży. Serwis Steam zezwala na wystawianie przedmiotu po niższej cenie, ale nie pozwala na publikowanie zaobserwowanych wyższych cen wywoławczych. Oświadczenie serwisu Valve zamieszczone pod adresem 2016 potwierdza, że serwis ten ma świadomość, iż operatorzy gier hazardowych korzystają z OpenID oraz infrastruktury handlowej Steam. Kwestia, czy konkretna zewnętrzna platforma handlowa narusza zasady serwisu Valve, musi zostać ustalona oddzielnie.\n\nPrzejrzyj cały rejestr →CSFloat JSON ↗Skinport JSON ↗Oświadczenie Valvea w sprawie „2016” ↗\nBEZPOŚREDNIE API CSFLOAT / ZRZUT EKRANU Z DATĄ$13.63M\n\nMinimalna łączna wartość ofertowa w 241 kategorii produktów oraz 3,395 aktywnych ofert. Obliczono jako iloczyn najniższej ceny sprzedaży w każdej kategorii i liczby ofert w tej kategorii. Cztery kategorie, których ceny osiągnęły górny limit $100,000 ustalony przez CSFloat, zostały wykluczone z tego konserwatywnego zestawienia.\n\nCo pokazuje ta kwota w dolarach\n\nOferty te stanowią co najmniej $13,631,888.25 w podanych cenach wywoławczych dla tego ograniczonego podzbioru CSFloat. Uwzględnienie czterech kategorii o najwyższych cenach daje $14,231,888.25. To jest limit dla aktywnych zleceń kupna, a nie zrealizowaną sprzedażą, obrotem gotówkowym, zyskiem ani całym rynkiem CS2.\n\nPrzelicz na podstawie migawki CSFloat zawierającej 245 wierszy ↗\nPRICEEMPIRE / WARTOŚĆ KOTOWANASteam: nr 15 z 39\nWiele obiektów podaje wartość wyższą niż Steam.\nUUSkins\n$133.8M\nYouPin898\n$127.5M\nBuff.163\n$104M\nMoon.Market\n$100.3M\nWhite.Market\n$89.6M\nBuff.Market\n$86.7M\nSteam\n$31M\n\nSześć największych wyświetlonych wartości oraz Steam. PriceEmpire zaokrągla te liczby; Steam pokazuje $31M. Czternaście wymienionych obiektów plasuje się przed nim pod względem podanych wartości w dolarach.\n\nPRICEEMPIRE / LICZBA OFERTSteam: nr 1 z 39\nSteam nadal przoduje pod względem liczby ofert.\nSteam\n32,2 mln\nYouPin898\n5,9 mln\nC5Game\n4,6 mln\nHaloSkins\n4,4 mln\nSkinport\n3,8 mln\n\nSteam pokazuje 32,2 mln oferty. Liczba ofert i łączna wartość wyceny odpowiadają na różne pytania; wiele ogłoszeń o niskiej cenie może zdominować tę liczbę.\n\nŹródło: Publiczne porównanie serwisu PriceEmpire ↗ zarchiwizowano 2026-09-21 ↗, zarejestrowano 2026-09-20 o godz. 19:03 UTC; wyodrębnienie z datą z 39. wiersza ↗. Podane liczby są zaokrąglonymi szacunkami, a zasoby mogą się pokrywać w różnych lokalizacjach. Karta Steam zawiera również opisy przedmiotów z innych gier Steam, więc zakresy nie są identyczne. Podane wartości odzwierciedlają ceny wywoławcze, a nie sprzedaż ani przychody.\n42\nINNE ŹRÓDŁO / STEAMANALYST\nEkosystem biznesowy jest jak na dłoni.\n\nKatalog platform handlowych serwisu SteamAnalyst zarchiwizowano 2026-07-19 ↗ wymienia 42 zewnętrzne platformy handlowe CS2 obok Steam, podając aktualne dane dotyczące cen dla 32 z 43 pozycji. PriceEmpire wymienia 39 platform handlowych zgodnie z własnymi kryteriami wyboru. Wymienione firmy, publiczne oferty, widoczne ceny: ta gospodarka jest otwarta na wgląd.\n\nMECHANIZM TO GÓRNA GRANICA: SPRZEDAŻ TRACI NA SILE, A PRODUKT NIE.\n\nNa pięciu platformach handlowych uchwyconych na jednym licencjonowanym zrzucie ekranu, Ceny 248 kategorii produktów CS2 przekraczają o co najmniej Steam wartościowy pułap Steam — a żadna z nich nie występuje w Steam. Ten sam zrzut ekranu pogrupował cały katalog według ceny: rynek Valve obejmuje 95.3% kategorii produktów poniżej swojego limitu i 1.9% kategorii powyżej niego. Spadek ten nie wynika ze spadku popytu; wynika on dokładnie z opublikowanej zasady. Sprzedaż po tych cenach wymaga zewnętrznego nabywcy lub platformy handlowej, podczas gdy Steam nadal kontroluje zapasy i transfer — transakcja opuszcza kasę Valve, a dostawa odbywa się w ramach infrastruktury Valve.\n\nSteam Najczęściej zadawane pytania dotyczące rynku ↗zarchiwizowano 2026-09-21 ↗Steam Umowa abonamentowa ↗zarchiwizowano 2026-09-21 ↗Zbiór danych atlasu obejmujący pięć rynków ↗Manifest pochodzenia ↗Poprzednia migawka CSFloat ↗Podsumowanie Skinport ↗PriceEmpire ↗zarchiwizowano 2026-09-21 ↗SteamAnalyst ↗zarchiwizowano 2026-07-19 ↗Rejestr różnic cenowych ↗Atlas drabiny cenowej ↗\n\nCzęść C — Ramy prawne\nCzęść C — Ramy prawne · Sekcja 14 · Dostęp personelu\nKto może zresetować zabezpieczenia?\nOgraniczenia dotyczące kontekstu i źródła\n\nBezpieczeństwo konta zależy również od osób, które mogą je odzyskać, przeglądać prywatne dane lub zresetować zabezpieczenia. W ramach dochodzenia należy śledzić te działania wymagające uprawnień równie uważnie, jak nadużycia związane z interfejsem API.\n\nProces odzyskiwania konta daje pracownikowi pomocy technicznej uprawnienia do odebrania konta jego właścicielowi. Valve dwukrotnie potwierdziło na piśmie — w lutym 2023 r. i w listopadzie 2025 r. — że uprawnienie to zostało wykorzystane do przekazania kont niewłaściwym osobom. W odstępie trzydziestu trzech miesięcy, tą samą drogą. Poniżej: jaka jest wartość tego dostępu, sześć potwierdzonych przypadków oraz dziennik Valve, który dotyczy każdego z nich i którego treści nikomu nie ujawniono.\n\nZachowane zeznanie / 9 maja 2025 r.\nKod odzyskiwania, który wyłączył zabezpieczenia konta, oraz zgłoszona strata w wysokości $10,000\n\nJeden z użytkowników w archiwum zgłoszeń do pomocy technicznej informuje, że Steam dział pomocy technicznej zresetował hasło i wyłączył ochronę konta po tym, jak inna osoba złożyła zgłoszenie dotyczące odzyskania dostępu. Autor twierdzi, że konto było nieaktywne od lat, zawierało elementy z lat 2016–2017 oraz miało Steam Guard, powiązany numer telefonu i zapisane kody odzyskiwania.\n\n„Steam Dział pomocy technicznej i tak udzielił komuś innemu dostępu do mojego konta.”\n\nZarzut sformułowany w pierwszej osobie, zachowany w steam_support_tickets_MEGA.json, rekord 110. Przeczytaj cały zapisany wpis ↗\n\nNie jest to przypadek pecha jednego użytkownika. Ta sama procedura — zgłoszenie pomocy, w wyniku którego konto zostaje przeniesione do osoby dostarczającej starsze dane — stanowi udokumentowany sposób postępowania we wszystkich przypadkach wymienionych w poniższym rejestrze, a Valve dwukrotnie potwierdził to na piśmie.\n\nWłaściciel nie ma szans wygrać tej dyskusji. Procedura odzyskiwania danych wymaga podania pierwszego klucza CD, pierwszego adresu e-mail, pierwszej karty płatniczej oraz pierwszego numeru telefonu. Dane te znajdują się w bazie danych Valve, a dział wsparcia technicznego ma do nich dostęp — podobno sięgają one aż piętnastu lat wstecz. Osoba posiadająca kopię twojego pliku zawsze będzie w stanie przedstawić więcej informacji o twojej historii niż ty sam. Cele zostały wybrane pod kątem określonych kryteriów: nieaktywne od lat, o dużej wartości i często kupowane z drugiej ręki, więc posiadacz nigdy nie znał oryginalnego klucza. Następnie konta zostały całkowicie usunięte, przerywając ślad historii przedmiotów, którego społeczność używa do śledzenia skórki — usunięcie, którego zwykły użytkownik nie może wykonać bez standardowego okresu oczekiwania.\n\nZasada minimalnych uprawnień / OWASP A01\n\nUprawnienia związane z odzyskiwaniem danych powinny być ograniczone do danego zadania, podlegać niezależnej weryfikacji i być rejestrowane. Należy sprawdzić, kto może resetować dane uwierzytelniające, usunąć Steam Guard, przeglądać dane rozliczeniowe lub eksportować dane konta. Wytyczne OWASP dotyczące kontroli dostępu ↗ zarchiwizowano 2026-09-20 ↗\n\nSzeroki dostęp do wsparciaRyzyko związane z zakresem dostępu\nWięcej niż tylko asortyment.\n\nW przypadku nadużycia szerokiego dostępu do wsparcia prywatne dane telemetryczne mogą stać się narzędziem do profilowania, ukierunkowanego phishingu i inwigilacji. Potencjalnymi ofiarami są zwykli użytkownicy, personel wojskowy, osoby publiczne oraz ich rodziny. Jest to model zagrożenia; dokładne uprawnienia wymagają analizy zapisów dotyczących kontroli dostępu.\n\n01 Historia adresów IP i lokalizacja\nDane z logów IP mogą ujawniać historię połączeń sieciowych oraz przybliżoną lokalizację. Same w sobie nie pozwalają jednak na ustalenie dokładnych przemieszczeń fizycznych.\n02 Identyfikacja urządzeń na podstawie charakterystyki\nIdentyfikatory urządzeń, o ile zostały zebrane i są dostępne, mogą służyć do powiązania sesji i kont.\n03 Telemetria aktywności\nZnaki czasu logowania i zapisy sesji mogą ujawnić nawyki użytkownika, w tym działania niewidoczne w profilu publicznym.\n04 Komunikacja i kontakty\nDostęp do zachowanych wiadomości lub danych kontaktowych zwiększyłby możliwości tworzenia profili i stosowania technik inżynierii społecznej.\n05 Demaskowanie tożsamości\nOryginalne dane dotyczące wiadomości e-mail, numerów telefonów i płatności mogą pozwolić na powiązanie konta prowadzonego pod pseudonimem z konkretną osobą.\n06 Odsprzedaż danych i odpowiedzialność\nWyeksportowane listy celów mogą służyć do przeprowadzania ukierunkowanych oszustw. Należy ustalić tożsamość sprawcy, miejsce dostępu, odbiorców oraz przepływy środków; sama lokalizacja nie stanowi dowodu ani na dostęp, ani na immunitet prawny.\n\nValve opisuje w swoim dokumencie rejestrowanie adresów IP, informacje o urządzeniach, dane dotyczące płatności oraz zewnętrznych dostawców wsparcia technicznego Polityka prywatności §§ 3, 5.2 zarchiwizowano 2026-09-21 ↗. Polityka ta zezwala na dostęp podmiotów zewnętrznych w celu udzielania wsparcia — nie ujawniono jednak ścieżki audytu, która wskazywałaby, który wykonawca uzyskał dostęp do której kategorii, kiedy i na podstawie jakiego upoważnienia.\n\nSekcja 14.1 · rejestr · czerwiec 2022 r. → listopad 2025 r. · podano źródła wszystkich danych liczbowych\nValve otworzył drzwi dwukrotnie, w odstępie trzydziestu trzech miesięcy. Drzwi nigdy się nie zamknęły.\n\nZgłoszono sześć przypadków, w których konta zostały przejęte za pośrednictwem własnego kanału pomocy Steam lub przy użyciu danych uwierzytelniających chronionych przez ten kanał. Każda kwota odpowiada danym opublikowanym przez cytowane źródło, a każde źródło zostało wymienione z nazwy. W dwóch z tych sześciu przypadków poszkodowani odzyskali utracone środki. Różnica między nimi a pozostałymi przypadkami nie polegała na tym, co się wydarzyło — chodziło o to, kto to obserwował.\n\nValve, na piśmie — luty 2023 r.„Wspomniane przedmioty zostały usunięte z Twojego konta, ponieważ pochodziły z konta, które zostało przejęte w wyniku zgłoszenia do pomocy technicznej, za co odpowiedzialność bierze na siebie zespół CS:GO. Cofnęliśmy te transakcje i usunęliśmy je ze wszystkich kont, na które trafiły”.Steam Odpowiedź pomocy technicznej skierowana do odbiorcy produktów HFB, opublikowana przez Dexerto, 21 lutego 2023 r. ↗ zarchiwizowano 2025-08-18 ↗\nValve, znowu na piśmie — listopad 2025 r. · 33 miesiące później„Technik pomocy technicznej, który zajmował się zgłoszeniem, nie zastosował się do naszej procedury, co spowodowało, że Państwa konto zostało przywrócone innej osobie. Przepraszam za ten błąd.”Steam Odpowiedź na komentarz użytkownika Hawkeye337, cytowana w Dexerto, 14 listopada 2025 r. ↗\n21 czerwca 2022 r.\nHFB — największy asortyment w grze$2,000,000+ · podwyższono do $3,000,000+ w ramach kontroli przeprowadzonej w lutym 2023 r.\n\nSiedem pamiątkowych przedmiotów „AWP Dragon Lores” oraz karambit nr 1 z niebieskim klejnotem – sam ten nóż jest wart około $1.26 mln. Konto pozostawało nieaktywne przez trzy lata, a aplikacja do uwierzytelniania na telefonie nadal działała; mimo to adres e-mail i hasło zostały zmienione za pośrednictwem procedury odzyskiwania hasła oferowanej przez dział pomocy technicznej.\n\nPieniądze skończyły się, zanim zniknęły przedmioty. Zgłoszono, że $200,000+ Część wpływów ze sprzedaży została już wypłacona za pośrednictwem serwisu market.csgo.com — platformy handlowej, która rozlicza transakcje w gotówce i kryptowalutach. Cofnięcie transakcji powoduje zwrot skórki. Nie powoduje to jednak zwrotu środków pieniężnych, które ktoś już zdeponował na koncie.\n\nA poprawka przestała działać. Jeden z graczy przeniósł swój przedmiot „Souvenir Dragon Lore” do magazynu w grze. Skrypt przywracający Valve nie miał wglądu do wnętrza własnego kontenera, więc wygenerował dla właściciela nową kopię, pozostawiając ukrytą — Valve skopiował $130,000 przedmiot podczas próby cofnięcia kradzieży. Został on wykryty dzięki porównaniu identyfikatorów przedmiotów oraz zgłoszeniom społeczności, a miesiąc później, w lipcu 2022 r., został usunięty. Kupujący otrzymał zwrot środków od BUFF, a nie od Valve. Tak doraźne działania naprawcze nie stanowią środka kontroli; są one po prostu tym, co platforma robi, gdy nie ma nad sytuacją kontroli.\n\nDexerto, 21 czerwca 2022 r. ↗ zarchiwizowano 2022-07-02 ↗ · Kaspersky ↗ · kwota wypłaty na Esportfire, 22 czerwca 2022 r. ↗ zarchiwizowano 2026-05-15 ↗, przypisane tam wielu źródłom z Twittera · powielanie i usuwanie zgodnie z Esportsbetting, 14 lipca 2022 r. ↗\n\nOdrestaurowanyTransakcje zostały cofnięte. Towary zostały wycofane z zapasów osób, które zapłaciły za nie pełną cenę.\n14 sierpnia 2022 r.\nCS.Money — boty należące do platformy$6,300,000 · 19,000+ skórki · wstępna wycena $1.6M\n\nHakerzy przejęli pliki aplikacji do uwierzytelniania na urządzeniach mobilnych należące do botów handlowych platformy i opróżnili je, a następnie wysłali część zdobyczy do znanych inwestorów, aby zmylić ślady. Badacze ze społeczności sporządzili mapę 55 kont atakujących w ciągu kilku godzin i opublikował je.\n\nValve nie zmieniło nic. Jako powód podano, że strona zewnętrzna znajduje się poza Steam — tym samym Steam, w ramach którego kradzież przebiegała od początku do końca, wykorzystując zasoby reklamowe, interfejs API transakcyjny oraz system kont.\n\nEsportfire, 14 sierpnia 2022 r. ↗ zarchiwizowano 2025-11-15 ↗\n\nOdrzuconoNie doszło do odwrócenia sytuacji. Strata poniosła platforma i jej użytkownicy.\nZgłoszono\n21 lutego 2023 r.\nQkss — te same drzwi, ten sam aktor$1,000,000+\n\nZgłoszono, że sprawa została rozpatrzona w taki sam sposób jak w przypadku HFB – przez tego samego pracownika, w ramach tej samej prośby o pomoc techniczną. Sprawa HFB została w pełni rozwiązana osiem miesięcy wcześniej. Sprawa Qkss – nie.\n\nJedna droga. Dwie odpowiedzi. W opublikowanych materiałach nie ma żadnych elementów odróżniających te dwie sprawy, z wyjątkiem liczby uczestników.\n\nDexerto, 21 lutego 2023 r. ↗ zarchiwizowano 2025-08-18 ↗\n\nOdrzuconoNie zostało odrestaurowane.\nZgłoszono\nLuty 2023 r.\nSamo wykorzystywanie informacji poufnych — rok takich praktyk≈ $320,000 · obejmuje okres około jednego roku, a nie wycenę zapasów\n\nDostęp od strony pomocy technicznej umożliwił przeglądanie historii konta do 15 lat — pierwszy klucz CD, pierwszy e-mail, pierwsza karta. Właśnie takich dowodów wymaga proces odzyskiwania, dlatego osoba posiadająca bazę danych zawsze wygrywa spór z osobą posiadającą konto.\n\nBloger Mzkshow ujawnił, w jaki sposób operator „Steam Help” i jego wspólnik „Alexander” skupili się na nieaktywnych kontach, na których znajdowały się skórki o wartości ponad $100k. Jedna z wykradzionych broni M4A4 Howl, wyposażona w hologramy iBUYPOWER oraz Titan Katowice 2014, została sprzedana za $35,000 i ostatecznie trafił do Valerii „b1t” Vakhovskiego z drużyny NAVI, który nie miał o tym pojęcia. Po interwencji Valve wykonawca zwolnił cały swój zespół pomocy technicznej Steam.\n\nVKPlay ↗ · Lis-Skins ↗ · Escorenews (RU) ↗ · Dexerto (EN) ↗\n\nBrak rejestruValve nigdy nie podało, ile kont to dotyczyło, ani nie poinformowało osób, których to dotyczyło.\nZgłoszono\n2 grudnia 2024 r.\n„Matvey” — po zwolnieniach$13,000\n\nOdzyskanie danych przyznano osobie, która dostarczyła dane dotyczące konta, których sam właściciel nie był w stanie zweryfikować. Dwa lata po tym, jak wykonawca zlikwidował swoje centrum pomocy technicznej Steam, ta sama procedura przyniosła ten sam rezultat.\n\nArchiwalny wpis z 2 grudnia 2024 r. ↗ zarchiwizowano 2025-08-05 ↗ · wiersze źródłowe i skróty ↓\n\nOdrzuconoNie zostało odrestaurowane.\n13 listopada 2025 r.\nHawkeye337 (Mark Spurlock) — oraz drugie przyznanie się≈ $300,000–$500,000 · pełna kolekcja hologramów z Katowic 2014\n\nNapastnik zażądał 1 bitcoin i zaczął przenosić zbiory na dyski Negev, aby je zniszczyć. Steam Pisemna odpowiedź działu pomocy technicznej stanowi drugie z powyższych przyznanie się: technik, który zajmował się zgłoszeniem, nie postępował zgodnie z procedurą i przekazał konto innej osobie.\n\nTo właśnie sygnał był przyczyną tej usterki. Kilka godzin po opublikowaniu na X postów oznaczających Valve konto zostało przywrócone, a wszystkie naklejki przywrócono. Qkss nie miało takiej liczby odbiorców.\n\nSkin.club ↗ · Dexerto ↗ · Esportfire ↗ zarchiwizowano 2025-12-17 ↗\n\nOdrestaurowanyW ciągu kilku godzin od momentu, gdy artykuł stał się popularny, decyzja została cofnięta.\nTo, co wynika z księgi, a czego nie pokazuje żaden pojedynczy przypadek.\n\nTrasa nigdy nie została zamknięta. Pierwsza rekrutacja odbyła się w lutym 2023 r., a druga w listopadzie 2025 r. — w odstępie trzydziestu trzech miesięcy, przy czym w międzyczasie doszło do masowych zwolnień u wykonawcy, udokumentowanego ponownego naruszenia oraz naruszenia bezpieczeństwa platformy o wartości $6.3 mln. Licząc od pierwszej kradzieży odnotowanej w tym rejestrze, kanał pozostawał otwarty przez trzy lata i pięć miesięcy. Niezależnie od tego, co naprawiono w 2023 roku, w listopadzie 2025 roku zgłoszenie pomocy nadal zostało skierowane do niewłaściwej osoby — zdanie samego Valve.\n\nW ramach restytucji brano pod uwagę skupienie uwagi, a nie wyrządzoną krzywdę. Przyjęto: największy asortyment w grze oraz kolekcjoner, którego wątek stał się popularny. Odrzucono: $1,000,000, $6,300,000, $13,000. Valve nigdy nie opublikował zasady, którą stosuje, ponieważ opublikowana zasada musiałaby wyjaśniać te trzy przypadki.\n\nNikomu o tym nie powiedziano. Ani użytkownicy, których historie kont zostały odczytane z bazy danych, ani organ nadzorczy, ani rynek, który nabył te przedmioty w dobrej wierze, a następnie został zmuszony do ich zwrotu. Nie ma żadnego zawiadomienia o naruszeniu, żadnego zgłoszenia incydentu, żadnej liczby kont, których to dotyczy — oraz środki pozostawione w formie pieniężnej, za pośrednictwem platform handlowych, które rozliczają się gotówką i kryptowalutami. Odwrócenie transakcji nie może nastąpić po wypłynięciu środków z Steam.\n\nValve zawiera historię audytową wsparcia technicznego, dziennik zgłoszeń dotyczących przywracania danych oraz zapis transakcji dla każdej z powyższych pozycji. Żadna z tych informacji nie została udostępniona. Poproś o swój egzemplarz →\n\nKwestia NDA\nPoufność musi iść w parze z odpowiedzialnością techniczną.\n\nNależy porównać umowy o zachowaniu poufności z faktycznymi uprawnieniami, kontrolą eksportu, zezwoleniami na reset oraz dziennikami dostępu. Gotowa odpowiedź nie jest w stanie rozstrzygnąć zarzutu, że doszło do nadużycia samego procesu odzyskiwania danych.\n\nArtykuły 28, 32–34 RODO\n\nArtykuł 33 przewiduje, że administrator danych ma 72 godziny na zgłoszenie naruszenia ochrony danych osobowych organowi nadzorczemu; artykuł 34 nakłada obowiązek poinformowania osób, których dane dotyczą, w przypadku gdy ryzyko dla nich jest wysokie. Firma Valve dwukrotnie potwierdziła na piśmie, że jej dział obsługi klienta przekazał dane kont niewłaściwym osobom — w tym historię transakcji, dane rozliczeniowe i wszystkie inne informacje. Nie opublikowano żadnego zawiadomienia na podstawie żadnego z tych artykułów, a żaden z użytkowników, których to dotyczy, nie zgłosił, że je otrzymał. Zapoznaj się z rozporządzeniem ↗ zarchiwizowano 2026-09-20 ↗\n\nDodaj prośbę o pomoc techniczną do swojego zgłoszenia →\nCzęść C — Ramy prawne · Sekcja 15 · Skala komercyjna\nPodążaj za pieniędzmi. Rozdziel transakcje.\nOgraniczenia dotyczące kontekstu i źródła\n\nKwestia wykorzystania w celach komercyjnych nabiera większego znaczenia, gdy przepływy pieniężne są rozdzielone. Przekazywanie przedmiotów przez osoby trzecie, sprzedaż podstawowa podmiotu Valve oraz wypłaty środków na zewnątrz to odrębne transakcje.\n\nPrzedmiot należy do Valve. Stan magazynowy wynosi Valve. Przeniesienie odbywa się na serwerach Valve. Jedynie płatność odbywa się gdzie indziej — czyli etap, od którego zależy, czy dana osoba jest podmiotem świadczącym usługi w zakresie przekazów pieniężnych, a etapu Valve nie przeprowadza się.\n\nMechanizm generowania przychodów\nGdzie faktycznie przepływają pieniądze.\nTrzy ścieżki / gospodarka oparta na jednym przedmiocie\n01 / KontoLista użytkowników\n\nPozycje przechowywane w Steam\n\n02 / PrzeniesienieHandel P2P\n\nUżytkownik ↔ bot lub użytkownik ↔ użytkownik\n\n03 / RozliczeniePlatforma zewnętrzna\n\nSaldo na koncie lub spłata Steam\n\nNakładSiła napędowa gospodarki wykracza poza kwotę opłaty transferowej\n\nSteam zapewnia infrastrukturę magazynową i transferową wykorzystywaną przez rynki zewnętrzne. Ekonomiczna argumentacja przedstawiona w ramach dochodzenia opiera się na założeniu, że płynność odsprzedaży oraz powtarzający się popyt podtrzymują wydatki na etui, klucze i elementy zamienne, a także generują opłaty z tytułu kolejnych transakcji na Rynku Wspólnotowym. Bezpośredni transfer P2P nie wiąże się z prowizją Rynku Społecznościowego; ten fakt księgowy nie rozstrzyga jednak kwestii szerszych korzyści. Valve zachowuje kontrolę nad dostępem do konta i ograniczeniami handlowymi przez cały czas.\n\n01 / Popyt wtórnyPłynność i wartość odsprzedaży\n\nPopyt w handlu zagranicznym i branży hazardowej\n\n02 / Wydatki podstawoweKlucze, etui i kapsułki\n\nZakupy od Valve, jeśli są dostępne\n\n03 / PrzychodyPrzychody ze sprzedaży pierwotnej\n\nPlus opłaty od faktycznej sprzedaży na rynku\n\n5% + 10%Steam + opłata CS2 od sprzedaży na rynku społecznościowym\n\nWniosek ekonomiczny wynikający z badania: płynne rynki odsprzedaży mogą sprzyjać wydawaniu pieniędzy na nowe towary. Znany symbol 15% uwzględnia stawki opłat rynkowych, z zastrzeżeniem minimalnych kwot i zaokrągleń; nie jest to opłata nakładana na każdą transakcję handlu zagranicznego.\n\nCennik usług Community Market serwisu Valve ↗ zarchiwizowano 2026-09-21 ↗. 25 lutego 2026 r. prokurator generalny stanu Nowy Jork wniósł pozew zarchiwizowano 2026-09-01 ↗ twierdząc, że płatne skrzynki z łupami mają związek z odsprzedażą za gotówkę na rynku zewnętrznym oraz szkodliwością hazardu — ten sam związek, który niniejsze dossier dokumentuje z punktu widzenia infrastruktury technicznej. Skarga ta stanowi zarzut, a nie ustalenie; przytoczono ją tutaj, ponieważ stanowa agencja ścigania postawiła pytanie pokrewne temu, które zadaje niniejszy raport: gdzie są dane dotyczące egzekwowania prawa, które odpowiadają publicznym deklaracjom?\n\n01 / WpisWpłata w kryptowalutach\n\nDane dotyczące usług zewnętrznych i portfeli\n\n02 / KonwersjaBilans → skórki\n\nProdukty dostarczone w ramach Steam transakcji\n\n03 / WyjścieZewnętrzna sprzedaż walut fiducjarnych\n\nSprzedawca, kupujący i podmiot realizujący wypłatę\n\nKYC?Należy zidentyfikować element sterujący przy każdym przekazaniu\n\nTo jest kierunek, w którym należy podjąć działania, a nie natywna usługa wymiany gotówki za pośrednictwem interfejsu API Steam. Przed zatwierdzeniem wypłaty gotówki bez weryfikacji tożsamości (no-KYC) należy udokumentować procesy weryfikacji tożsamości, przechowywania środków, identyfikatory transakcji oraz odbiorców wypłat u każdego zewnętrznego operatora.\n\nStany Zjednoczone / Ustawa o tajemnicy bankowej\nNajpierw sklasyfikuj czynność, a potem obowiązek.\n\nFinCEN ocenia przekazywanie środków pieniężnych na podstawie działalności danego przedsiębiorstwa. Przyjmowanie i przekazywanie zamiennej waluty wirtualnej może powodować powstanie obowiązków związanych z usługami pieniężnymi, z zastrzeżeniem obowiązujących definicji i wyjątków. Portfel Steam firmy Valve przyjmuje środki i zamienia je na przedmioty w grze; przedmioty te są następnie spieniężane za pośrednictwem zewnętrznych operatorów na prawdziwą walutę. Przedmiot i jego transfer odbywają się w ramach infrastruktury Valve; wypłata gotówki już nie, a to, czy jakakolwiek część tego cyklu spełnia definicje przekazów pieniężnych, jest kwestią klasyfikacyjną leżącą w gestii FinCEN, a nie wnioskiem wyciągniętym w niniejszym dokumencie.\n\nFinCEN FIN-2019-G001, §§ 1–2, 5.1 ↗ zarchiwizowano 2025-07-11 ↗\n\nUnia Europejska / pranie brudnych pieniędzy\nŚledź przebieg działań, zdobywaj wiedzę i korzystaj z pomocy.\n\nDyrektywa (UE) 2018/1673 dotyczy umyślnego prania pieniędzy oraz udziału w działaniach związanych z dochodami pochodzącymi z przestępstwa. Przedmiotem dochodzenia jest ustalenie, co firma Valve wiedziała o operatorach korzystających z jej infrastruktury handlowej i OpenID po 13 lipca 2016 r., kiedy to publicznie opisała takie wykorzystanie, oraz jakie działania podjęła w tej sprawie. Valve nie opublikowała żadnych danych dotyczących działań egzekucyjnych w odniesieniu do poszczególnych operatorów; to właśnie te dane, a nie niniejsza dokumentacja, dałyby odpowiedź na to pytanie.\n\nRamy prawa karnego UE ↗\n\nTerminologia AMLD6: Powyższa dyrektywa z zakresu prawa karnego różni się od dyrektywy (UE) 2024/1640, zwanej również AMLD6. W przypadku tej ostatniej ogólny termin transpozycji upływa 10 lipca 2027 r., z zastrzeżeniem określonych wyjątków. Artykuł 78 ↗ zarchiwizowano 2026-08-30 ↗\n\nCzęść C — Ramy prawne · Sekcja 16 · Powiadomienie, odpowiedź, odpowiedzialność\nUstawa o usługach cyfrowych: należy odnotować tę informację\nOgraniczenia dotyczące kontekstu i źródła\n\nDwa elementy zawiadomienia zgodnie z art. 16 dotyczą raczej wnioskodawcy niż niniejszej dokumentacji: dane wnioskodawcy oraz oświadczenie w dobrej wierze, że informacje są prawdziwe. Wszystkie pozostałe wymagania przewidziane w tym artykule — uzasadnione wyjaśnienie oraz dokładna lokalizacja elektroniczna — zostały określone w sekcji 3 oraz w rejestrze tras, wraz z zapisanymi odpowiedziami i skrótami, tak aby każda strona mogła złożyć takie zawiadomienie. Dwa dalsze ograniczenia dotyczące samego prawa: utrata zwolnienia z odpowiedzialności za hosting nie powoduje sama w sobie powstania odpowiedzialności na mocy jakiegokolwiek innego prawa, a kwota 6% w art. 52 ust. 3 stanowi ustawowy pułap, a nie ustaloną karę w wysokości Valve.\n\nZgodnie z ustawą DSA dostawca usług hostingowych zachowuje ochronę przed odpowiedzialnością tylko do momentu, gdy uzyska konkretną wiedzę na ten temat i nie podejmie odpowiednich działań. Niniejszy dokument stanowi to zawiadomienie. Wymienia serwery, daty, zapisane odpowiedzi oraz skróty. Od momentu opublikowania nie chodzi już o to, czy Valve wiedział — chodzi o to, co zrobił potem Valve.\n\n01Lipiec 2016 r. / wystawa dokumentacji\nDziesięciodniowe wezwanie.\n\nPrzedstawione powyżej ogłoszenie stanowi historyczny punkt wyjścia dla porównania działań egzekucyjnych w ramach dochodzenia.\n\n0217 lutego 2024 r. / wniosek ogólny\nOkno czasowe DSA.\n\nNależy odróżnić zachowania historyczne od zachowań w okresie, w którym obowiązują odpowiednie zobowiązania wynikające z ustawy DSA.\n\n03Dziesięć lat / migawka z oryginalnej dokumentacji\nCzas trwania wymaga ścieżki powiadomień.\n\nCzas, jaki upłynął od lipca 2016 r. (patrz sekcja 11), stanowi wskaźnik dotyczący dokumentacji. Nie chodzi tu o dziesięć lat stwierdzonych naruszeń ustawy DSA. Każde zawiadomienie należy powiązać z konkretną pozycją, obowiązującym przepisem, dowodem doręczenia oraz odpowiedzią.\n\nArtykuł 52 ust. 3 / ustawowy pułap6%\nrocznego obrotu na całym świecie\n\nMaksymalna wysokość grzywny za naruszenie obowiązków wynikających z DSA, obliczona na podstawie poprzedniego roku obrotowego dostawcy. Jest to ustawowy pułap, a nie ustalona kara nałożona na Valve.\n\nArtykuły 6, 8 i 16 / kryteria prawne\n\nW przypadku odpowiednich usług hostingowych posiadanie konkretnej wiedzy oraz brak szybkiego działania mogą spowodować utratę zwolnienia z odpowiedzialności przysługującego dostawcom usług hostingowych. Wystarczająco precyzyjne zawiadomienie może stanowić dowód wiedzy o konkretnej treści. Ustawa DSA nie nakłada ogólnego obowiązku monitorowania; utrata zwolnienia z odpowiedzialności sama w sobie nie powoduje powstania odpowiedzialności na podstawie innych przepisów.\n\nDSA: art. 6, 8, 16, 52, 53, 93 oraz motyw 17 ↗ zarchiwizowane 2026-09-20 ↗\n\nPrzejrzyj zachowane zgłoszenia ↗Utwórz oś czasu konta →Pełna analiza prawna i ekonomiczna →\nCzęść C — Ramy prawne · Sekcja 17 · Tożsamość, wiek, dostęp do usług komercyjnych\nOsoby niepełnoletnie: logowanie za pomocą kodu „Steam” nie stanowi weryfikacji wieku\nOgraniczenia dotyczące kontekstu i źródła\n\nW niniejszym dossier nie pojawiają się nigdzie dane osób niepełnoletnich i żadne takie dane nie zostały zebrane: autorzy nie zarejestrowali się, nie umieścili żadnych danych ani nie zalogowali się na żadnej z wymienionych platform. Każdy, kto opiera się na tej sekcji, powinien zachować poufność dowodów dotyczących dzieci i usunąć dane umożliwiające identyfikację z materiałów dowodowych udostępnianych publicznie. Ustawa COPPA została tutaj przytoczona jako przepis dotyczący ochrony prywatności dzieci, posiadający własne warunki zakresu zastosowania — grupa docelowa, faktyczna wiedza, gromadzone dane osobowe — a nie jako ogólna zasada dotycząca wieku uprawniającego do uprawiania hazardu; skarga wniesiona w stanie Nowy Jork w 2026 r. stanowi zarzut wysunięty przez organ stanowy, a nie ustalenie faktyczne.\n\n„Zaloguj się za pomocą Steam” potwierdza istnienie konta. To niczego nie dowodzi w kwestii wieku — a na tych stronach jest to jedyna bariera między dzieckiem a wpłatą. Przeczytaj to z Sekcja 3.1: w kliencie Steam ostrzeżenie, które wyświetlałaby przeglądarka, nigdy nie jest generowane, więc dziecko nigdy go nie widzi.\n\nCo oferuje OpenID SteamTożsamość konta\n\nZweryfikowany identyfikator SteamID służący do logowania się lub powiązania konta.\n\n≠\nCo operator musi ustalićWarunki uczestnictwa\n\nWiek, właściwość sądowa oraz wszelkie wymagane kontrole tożsamości.\n\nPodstawa techniczna: Dokumentacja Steamworks OpenID ↗ zarchiwizowano 2026-09-21 ↗. Udokumentowane potwierdzenie tożsamości nie stanowi zaświadczenia, że użytkownik może legalnie uprawiać hazard.\n\nCOPPA / dzieci poniżej 13 roku życia\nOkreśl operator i dane.\n\nUstawa COPPA ma zastosowanie do objętych nią usług skierowanych do dzieci oraz usług, których dostawcy mają faktyczną świadomość, że gromadzą dane osobowe od dzieci poniżej 13. roku życia. Jest to ustawa dotycząca ochrony prywatności dzieci, a nie ogólna zasada określająca wiek uprawniający do uprawiania hazardu. Należy określić grupę docelową, gromadzone dane osobowe, stopień świadomości oraz proces uzyskiwania zgody rodziców.\n\nFTC: Wymogi ustawy COPPA ↗ zarchiwizowano 2026-09-21 ↗\n\nDowody, które należy zabezpieczyć\nZapisz przebieg procesu od zalogowania się do dokonania wpłaty.\n\nNależy zachować ograniczenie wiekowe serwisu, treść formularza rejestracyjnego, warunki kwalifikacyjne, proces płatności oraz historię skarg. Każdego operatora należy oceniać osobno. Wszelkie dowody dotyczące dzieci należy traktować jako poufne, a dane umożliwiające identyfikację należy usunąć z materiałów udostępnianych publicznie.\n\nPowiązanym wpisem w rejestrze egzekucji administracyjnych jest Ogłoszenie o wniesieniu pozwu w Nowym Jorku w 2026 r. zarchiwizowano 2026-09-01 ↗, w którym zarzuca się, że płatne skrzynki z nagrodami wyrządzają szkodę młodym użytkownikom. Nie jest to ustalenie wynikające z ustawy COPPA.\n\nCzęść C — Ramy prawne · Sekcja 18 · Wniosek na podstawie art. 15 RODO\nProśba. Odpowiedź. Brakujące porównanie.\n\nPoprosił o cztery rzeczy, a jedną z nich był log, który pozwoliłby zidentyfikować osobę, która dodała klucz API do jego konta. Trzy dni później zgłoszenie zostało zamknięte wraz z linkiem do strony, na której nie ma żadnej z tych informacji — a z twierdzeniem zawartym w zdaniu kończącym ten fragment zaprzeczają sami prawnicy Valve.\n\nCzyje to konto · Pochodzenie i ograniczenia\n\nTe zrzuty ekranu nie należą do PhishDestroy. Pochodzą one od zwykłego użytkownika konta Steam — jednego z respondentów krótkiej ankiety przeprowadzonej w ramach tego projektu, który sam złożył zgłoszenie i dostarczył zrzuty ekranu. Konto należy do niego, zgłoszenie jest jego, a korespondencja toczy się między nim a działem pomocy technicznej Steam. Niniejszy projekt nie złożył tego zgłoszenia, nie posiada konta na platformie i nie jest stroną tego zgłoszenia.\n\n16 września 2026 r. złożył wniosek o dostęp do danych na podstawie art. 15 RODO/CCPA, prosząc konkretnie o dzienniki rejestracji kluczy API, historię logowań wraz z adresami IP, historię autoryzacji urządzeń oraz historię transakcji. 17 września konsultant „Logen” skierował go na stronę samoobsługową „Dane konta”. 18 września stwierdził, że żądane kategorie nie znajdują się na tej stronie i poprosił o eskalację sprawy do zespołu ds. prywatności lub inspektora ochrony danych (DPO). 19 września konsultant „Kal” zamknął zgłoszenie, kierując go ponownie do tej samej strony. Oba zrzuty ekranu zostały zachowane poniżej (adres e-mail wnioskodawcy został zamazany; SHA-256 w steam_tos_assets/screenshot-manifest.json).\n\nJest on odpowiednią osobą do złożenia wniosku z zupełnie prozaicznego powodu: na tym koncie znajduje się klucz API sieci Web o wartości Steam, którego nie utworzył, zarejestrowany na localhost. Nie wiadomo, kiedy powstało — ani jemu, ani z niczego, co udostępniło mu Valve, ponieważ jedynym zapisem, który pozwoliłby to datować, jest dziennik rejestracji kluczy API, a właśnie tę kategorię dokumentów organ zamykający sprawę zataił. Klucz ten nie jest nowy: istnieje od czasu, który poprzedza moment, w którym się o nim dowiedział, o okres, którego nie jest w stanie oszacować, z tego samego powodu.\n\nInni posiadacze kont składają ten sam wniosek. Każda otrzymana odpowiedź zostanie umieszczona w tym miejscu na takich samych warunkach jak te dwie — numer zgłoszenia, data przechwycenia, SHA-256, dane wnioskodawcy utajnione — niezależnie od tego, czy zawiera ona podane kategorie, czy je odrzuca.\n\nW ramach tego projektu nie zajmujemy stanowiska w sprawie przyczyny zamknięcia zgłoszenia. W zgłoszeniu nie podano żadnego powodu, a my również nie wyciągamy z tego żadnych wniosków.\n\nProśba. Odpowiedź. Porównanie.ŚLEDŹ WYNIKI\nKrok 3 / 3\n\nPoprosił o podanie czterech konkretnych kategorii. Strona „Dane konta”, do której został przekierowany, to funkcja samodzielnego eksportu danych użytkownika Valve, a w ramach tego projektu nie można wygenerować wykazu jej zawartości dla konta innej osoby — dlatego nie opublikowano tutaj pełnego porównania według poszczególnych kategorii. W dokumentacji znajduje się jego oświadczenie z 18 września, że kategorii tych nie było, oraz zamknięcie sprawy z 19 września, w którym ponownie odesłano go do tej strony, nie odnosząc się do tej kwestii.\n\nPROŚBAPoszczególne kategorieKlucz API, dane logowania, dane dotyczące urządzeń i transakcji\nODPOWIEDŹOdniesienie do danych kontaSprawdź punkt wymiany podpór\nTESTCo zostało dostarczone?Porównaj każdą z wybranych kategorii\nEkran 1/2 — Prośba (16 września) i pierwsza odpowiedź od agenta „Logen” (17 września)\nGDPR ticket HT-2YBP-F7JP-D4VB — request and first response\nŹródło: help.steampowered.com, zgłoszenie HT-2YBP-F7JP-D4VB · zapisano w dniach 16–17 września 2026 r. · adres e-mail zgłaszającego usunięty 2026-09-21 · Plik: gdpr-ticket-1.png · SHA-256 da940c731ab9869d226e9d06ccc8a1b393738766b7b0c445a56662623e025a66 (screenshot-manifest.json).\nEkran 2/2 — Zgłoszenie eskalacji (18 września) i zamknięcie sprawy przez konsultanta „Kal” (19 września)\nGDPR ticket HT-2YBP-F7JP-D4VB — escalation request and closure\nŹródło: help.steampowered.com, zgłoszenie HT-2YBP-F7JP-D4VB · zapisano w dniach 18–19 września 2026 r. · Plik: gdpr-ticket-2.png · SHA-256 44844ea7b251f7fd7d79f87ee1578a846606a97b9659d3a53b322120c422219b (screenshot-manifest.json).\nOdpowiedź końcowa z 19 września (dosłowne cytaty):\n„Dane Steam przechowywane przez serwis można już znaleźć na stronie Dane konta. Ponieważ dział pomocy technicznej Steam nie dysponuje żadnymi dodatkowymi informacjami, To zgłoszenie zostanie zamknięte.\"\nBrak dostarczonych danych · brak wskazania podstawy prawnej odmowy · brak informacji o wyniku eskalacji\nTo zdanie jest nieprawdziwe, a dowodzą tego prawnicy samego Valve. W piśmie pełnomocnika z dnia 1 października 2025 r., w pkt 1.9, opisano korelację na poziomie urządzeń, łączącą jedno urządzenie z dziesiątkami kont (Załącznik A). Ta sama przesyłka zawierała 830 stron zachowanych dokumentów (Załącznik B). Żadna z tych informacji nie znajduje się na stronie „Dane konta”.\nDlaczego to konto poprosiło o dziennik kluczy API?\n\nNie wybrał tych czterech kategorii przypadkowo. Ten localhost kluczem do jego konta jest oznaka skryptu, a nie osoby wpisującej prawdziwą domenę na stronie dla programistów (Sekcja 5, Sekcja 6). Jedynym zapisem, z którego wynika, kto go utworzył i skąd pochodzi, jest dziennik rejestracji kluczy API. To była pierwsza rzecz, o którą poprosił. Właśnie tej informacji firma „Closure” nie ujawniła.\n\nŹródło: posiadacz konta, w ramach ankiety przeprowadzonej w ramach tego projektu. Powyższe zrzuty ekranu z biletami zostały zaszyfrowane; strona z kluczem nie została opublikowana.\n\nOcena · PhishDestroy\n\nZamknięcie zgłoszenia, mimo że kwestia pozostaje nierozstrzygnięta, nie jest tutaj przypadkiem. Jest to normalny wynik. Trzymamy się 16,319 zachowane dokumenty dotyczące skarg i pomocy oraz 354 powtórzeń w wymianie informacji dotyczącej wsparcia pochodzący z nich. Ten bilet stanowi jeden z dobrze udokumentowanych przykładów ich wyglądu.\n\nZgłoszenie do pomocy technicznej — ZachowaneHT-2YBP-F7JP-D4VB\nTyp żądaniaArtykuł 15 RODO – wniosek o dostęp do danych osobowych (DSAR)\nStatus biletuZAMKNIĘTE 19 WRZEŚNIA 2026 R. — BRAK DANYCH\nAgenci na giełdzie„Logen” (17 września), „Kal” (19 września)\nZłożono16 września 2026 r.\nWymagane daneKto zarejestrował klucz API sieci Web powiązany z tym kontem oraz z jakiego adresu IP / urządzenia / o której godzinie\nPowołana podstawa prawnaArt. 15 RODO — prawo dostępu do danych osobowych\nRamy prawne:Artykuł 12 ust. 3 wyznacza administratorowi termin jednego miesiąca od daty otrzymania (z możliwością przedłużenia po uzasadnieniu). Termin ten nie upłynął w momencie publikacji, a niniejszy dokument nie wskazuje na naruszenie terminu. Zastrzeżenie dotyczy treści: w odpowiedzi końcowej zamieszczono link do strony samoobsługowej, ale nie wykazano, że przedstawiono cztery wymienione kategorie danych, a jeśli administrator odmówi podjęcia działań, art. 12 ust. 4 nakłada na niego obowiązek podania powodów oraz wskazania dróg odwoławczych. Żadna z tych informacji nie pojawia się w odpowiedzi końcowej.\nDlaczego właśnie te dane mają znaczenie?\n\nDziennik zdarzeń kluczy API sieci Web to rejestr pokazujący, czy strona trzecia zarejestrowała klucz przy użyciu skradzionego pliku cookie sesji — mechanizm opisany w skargach dotyczących kradzieży zapasów, zachowanych w archiwum niniejszej dokumentacji. Ujawnienie informacji o tym, kto zarejestrował klucz API, z jakiego adresu IP i o której godzinie, spowodowałoby:\n\nNależy umożliwić ofierze porównanie adresu IP, z którego utworzono API, z jej własną historią logowań\nUjawnij adresy IP centrów danych powiązane ze znaną infrastrukturą botów wykorzystywanych do phishingu i hazardu\nPrzedstawić dowody, które można wykorzystać w postępowaniu cywilnym lub karnym przeciwko sprawcy\nPokaż, czy posiadacz konta został powiadomiony o utworzeniu klucza\nZ czego wynika z akt sprawy: Valve przechowuje zapisy dotyczące urządzeń oraz powiązań między kontami — opisano je w piśmie pełnomocnika tej firmy z dnia 1 października 2025 r. (zob. Załącznik A, Memorandum dowodowe — Źródło 1). W zgłoszeniu HT-2YBP-F7JP-D4VB osoba, której dane dotyczą, zwróciła się o udostępnienie tej samej kategorii zapisów, a zgłoszenie zostało zamknięte poprzez odesłanie do strony samoobsługowej, która — jak zgłosiła osoba, której dane dotyczą — nie zawierała tych zapisów. To, czy odmowa ta jest zgodna z prawem, jest kwestią, którą rozstrzyga organ nadzorczy; skutkiem tego jest to, że osoba, której dane dotyczą, ich nie otrzymuje.\nWymiana wiadomości — cztery wiadomości, trzy dni\n\nDwóch pracowników pomocy technicznej Steam odpowiedziało, posługując się imionami podanymi w zgłoszeniu: „Logen” 17 września i „Kal” 19 września. Obaj odesłali wnioskodawcę na stronę „Dane konta”. Z treści zgłoszenia nie wynika, czy prośba dotarła do zespołu ds. prywatności Valve lub inspektora ochrony danych, a dokumentacja nie zawiera informacji o tym, kim są pracownicy obsługi klienta, jakie pełnią funkcje ani w jaki sposób zgłoszenie zostało przekierowane.\n\n16 września\nWniosek złożony na podstawie art. 15, obejmujący cztery wymienione kategorie danych\n17–18 września\nOdniesienie do danych dotyczących konta; wnioskodawca zwraca się z prośbą o skierowanie sprawy do inspektora ochrony danych\n19 WRZEŚNIA\nZgłoszenie zostało zamknięte z tym samym odnośnikiem; brak danych, brak podanej podstawy\nDo czego artykuł 15 RODO wyraźnie uprawnia osobę, której dane dotyczą\nart. 15 ust. 1 lit. a)Cele przetwarzania — dlaczego firma Valve przechowuje dane\nart. 15 ust. 1 lit. b)Kategorie danych — co zawiera Valve\nart. 15 ust. 1 lit. c)Odbiorcy lub kategorie odbiorców — kto otrzymał dane (np. posiadacz klucza API)\nart. 15 ust. 1 lit. d)Okres przechowywania lub kryteria jego ustalania\nart. 15 ust. 3Kopia przetwarzanych danych osobowych — tj. sam dziennik kluczy API\nART. 12 ust. 3Proszę o odpowiedź w ciągu jeden miesiąc od daty otrzymania; o przedłużeniu terminu należy poinformować w ciągu tego miesiąca. W momencie publikacji termin ten jeszcze nie upłynął. Art. 12 ust. 4: jeżeli organ kontrolny nie podejmie działań, musi podać powód oraz poinformować osobę, której dane dotyczą, o możliwych drogach złożenia skargi.\nProcedura składania skarg dotyczących przepisów — dla każdego użytkownika\n\nKażdy użytkownik, który złożył wniosek na podstawie art. 15 RODO do Valve i nie otrzymał zgodnej z przepisami odpowiedzi (lub otrzymał standardowy wzór odmowy bez danych), może złożyć skargę do organu nadzorczego w swoim państwie członkowskim UE/EOG. Oddziałem Valve w UE jest spółka Valve GmbH z siedzibą w Hamburgu, więc głównym organem nadzorczym właściwym do rozpatrywania skarg transgranicznych jest Hamburski Pełnomocnik ds. Ochrony Danych i Wolności Informacji (HmbBfDI). (Przedstawiciel na mocy art. 27 Valve również ma siedzibę w Hamburgu; sam adres przedstawiciela nie decyduje o tym, który organ jest właściwy.) Skargę można również złożyć do organu w państwie członkowskim skarżącego na mocy art. 77.\n\nFormularz zgłoszenia reklamacyjnego HmbBfDI ↗ Tekst RODO (art. 12, 15, 77) ↗ zarchiwizowano 2026-09-20 ↗Wytyczne EDPB ↗\n\nNumer referencyjny biletu w przypadku wszelkich reklamacji: HT-2YBP-F7JP-D4VB — odnotowany w niniejszej dokumentacji jako udokumentowany przypadek.\n\nJeden udokumentowany przypadek\nDokumenty istnieją; osoba, której dane dotyczą, ich nie otrzymała.\n\nPełnomocnik Valve opisał zapisy korelacji na poziomie urządzeń w piśmie z dnia 1 października 2025 r. W dniu 19 września 2026 r. wniosek złożony na podstawie art. 15 dotyczący tej samej kategorii zapisów został zamknięty poprzez odesłanie do strony samoobsługowej, która – jak zgłosił wnioskodawca – nie zawierała tych zapisów, bez podania podstawy prawnej. Zgłoszenie HT-2YBP-F7JP-D4VB stanowi jeden z udokumentowanych przypadków; to, czy odzwierciedla ono szerszą praktykę, jest kwestią do rozstrzygnięcia przez organ nadzorczy, który może zwrócić się do Valve o udostępnienie dokumentacji dotyczącej rozpatrywania wniosków.\n\nArtykuły 12, 15 i 77 RODO / Organ nadzorczy\n\nSkargę na podstawie art. 12 i 15 można złożyć bezpośrednio do właściwego organu nadzorczego bez ponoszenia kosztów (art. 77). Organ ten może nałożyć środki naprawcze, w tym nakazy spełnienia żądania dostępu, oraz grzywny na podstawie art. 83 ust. 5 lit. b) za naruszenie praw osób, których dane dotyczą. Zachowanie oryginalnego numeru referencyjnego zgłoszenia oraz ewentualnej odpowiedzi Valve (lub jej braku) wzmacnia zasadność skargi.\n\nZobacz szablon wniosku o dostęp do danych (DSAR) →\nCzęść C — Ramy prawne · Sekcja 19 · Prawo umów\nUmowa abonamentowa niezgodna z architekturą platformy\nOgraniczenia dotyczące kontekstu i źródła\n\nAutorzy nie są prawnikami i żadna z powyższych treści nie stanowi porady prawnej. Cytat z SSA pochodzi z wersji z dnia 10 września 2026 r.; inna wersja może zawierać odmienne sformułowania, a numeracja paragrafów ulegała zmianom w poszczególnych wersjach — należy porównać dany paragraf z wersją, która miała zastosowanie do danego przypadku. Argumenty dotyczące art. 25 i 32 określają, czego wymaga rozporządzenie, a nie to, że organ nadzorczy stwierdził naruszenie. Dane liczbowe zawarte w argumencie 1 uwzględniają ograniczenia zakresu określone w sekcji 13.\n\nTrzy z kluczowych postanowień SSA nie współgrają z budową platformy: zakaz wykorzystania komercyjnego w połączeniu z pułapem cenowym na rynku, który wypycha transakcje o wysokiej wartości poza platformę; klauzula odpowiedzialności użytkownika za klucze API w kontekście punktu końcowego klucza, który przed 2023 r. nie wymagał uwierzytelniania dwuskładnikowego; oraz sformułowania dotyczące egzekwowania przepisów w kontekście publicznego rejestru, który nie wykazuje egzekwowania przepisów w odniesieniu do poszczególnych operatorów. To, czy te sprzeczności mają wpływ na wykonalność przepisów, jest kwestią do rozstrzygnięcia przez sąd; w niniejszej sekcji przedstawiono fakty, które sąd miałby do rozpatrzenia.\n\nArgument 1 / Struktura kapitalizacji rynkowej\nLimit rynkowy i zakaz wykorzystywania do celów komercyjnych\n\nW serwisie Steam Community Market górna granica cenowa wynosi około $1,800. W pięciu serwisach aukcyjnych, według nieaktualnego zrzutu ekranu (z 23 września 2026 r.), ceny 248 kategorii przedmiotów CS2 w co najmniej dwóch z tych serwisów przekraczają tę górną granicę; takie przedmioty nie mogą być sprzedawane po tych cenach na własnej platformie Valve. Właściciele, którzy chcą uzyskać takie ceny, korzystają z rynków zewnętrznych, które działają na kontach typu Steam i za pomocą interfejsu API typu Steam — należy pamiętać, że SSA klasyfikuje je jako komercyjne, chyba że wyraźnie zezwolono na inne traktowanie.\n\nPozycje przekraczają limit rynku → lukę wypełniają rynki zewnętrzne → rynki te korzystają z kont Steam i interfejsu API Steam → SSA zabrania komercyjnego wykorzystania bez zezwolenia → nie opublikowano rejestru zezwoleń. Łączna opłata Marketu Społeczności wynosząca około 15% dotyczy wyłącznie transakcji sprzedaży zrealizowanych w ramach Marketu, a nie tych zewnętrznych transakcji.\nArgument 2 / Architektura zabezpieczeń klucza API\nLuka w zabezpieczeniach klucza API jako kwestia związana z projektem platformy, a nie z niedbalstwem użytkownika\n\nPrzed 2023 r. punkt końcowy służący do tworzenia kluczy API serwisu Steam akceptował żądania POST zawierające skradziony identyfikator sesji i generował dane uwierzytelniające o wysokich uprawnieniach bez potwierdzenia e-mailowego, drugiego czynnika uwierzytelniającego lub weryfikacji urządzenia. Skargi dotyczące przejęcia API zebrane w ramach niniejszego dochodzenia wykazują ten sam schemat: skrypt atakującego, skradziony plik cookie sesji, ciche utworzenie klucza, przechwycenie transakcji (treść żądania przedstawiono w sekcji 8).\n\nArtykuł 25 RODO (ochrona danych w fazie projektowania) oraz artykuł 32 (bezpieczeństwo przetwarzania) wymagają zastosowania środków technicznych odpowiednich do poziomu ryzyka. Wydanie poświadczenia, które może zostać przechwycone podczas transmisji bez drugiego czynnika uwierzytelniającego lub powiadomienia właściciela, jest kwestią projektową leżącą w gestii administratora danych. To, czy w tym kontekście można powołać się na klauzulę SSA nakładającą odpowiedzialność na użytkownika, jest kwestią, którą rozstrzygnie sąd i organ nadzorczy.\n\nArgument 3 / Widoczność w czasie rzeczywistym\nValve pobiera nazwę hosta uwierzytelniającego przy każdym logowaniu\n\nNazwa hosta uwierzytelniającego dociera do punktu końcowego OpenID użytkownika Valve w postaci zwykłego tekstu w openid.return_to oraz openid.realm (kształt żądania przedstawiono w sekcji 3). Jego wyodrębnienie jest standardową operacją. Na dzień 2026-09-22 w 26 parach domena główna znajdowała się w filtrze Link Filter, podczas gdy host posiadający jej login Steam nie. Valve nie opublikował żadnych danych dotyczących egzekwowania zasad w podziale na operatorów, więc na podstawie danych publicznych nie można ustalić, czy w odniesieniu do tych hostów zastosowano jakiekolwiek środki inne niż filtr łączy.\n\nKto ponosi koszty\nWzorzec występujący w zarchiwizowanych skargach\n\nW przeanalizowanych skargach Steam odpowiedź działu pomocy technicznej na zgłoszenie dotyczące przejęcia klucza API ma zawsze ten sam przebieg: odmowa przywrócenia dostępu, wskazanie, że użytkownik ponosi odpowiedzialność za konto i jego klucz API, oraz zamknięcie zgłoszenia. W niniejszym opracowaniu nie oszacowano łącznej liczby kont, których dotyczyła ta sytuacja, ani wartości utraconych środków; nie znaleziono żadnego źródła, z którego pochodziłyby takie dane.\n\nNie chodzi o to, czy poszczególni użytkownicy popełnili błędy. Chodzi o to, kto ponosi odpowiedzialność za architekturę, która do 2023 roku pozwalała na utworzenie za pomocą żądania POST z wykorzystaniem skradzionego pliku cookie poświadczeń handlowych o wysokich uprawnieniach bez powiadomienia i bez uwierzytelniania dwuskładnikowego.\nSSA jako dokument a SSA jako umowa\nSąd rozpatrujący tę sprawę nie interpretowałby ustawy o ubezpieczeniach społecznych (SSA) w oderwaniu od pozostałych okoliczności.\n\nNależy to rozpatrywać w połączeniu z pismem pełnomocnika z października 2025 r., w którym opisano korelację na poziomie urządzeń, daty rejestracji hostów autoryzacyjnych, sygnatury czasowe rejestracji partii, treść żądania klucza API oraz dziesięcioletni okres między powiadomieniami z lipca 2016 r. a platformami nadal działającymi we wrześniu 2026 r. To właśnie ta dokumentacja Valve musiałaby zostać uwzględniona.\n\nSSA w świetle akt sprawy / kluczowe kwestie\n„Zakaz wykorzystania komercyjnego” — ograniczenia rynku powodują, że transakcje o wysokiej wartości są kierowane na komercyjne rynki zewnętrzne\n„Użytkownicy ponoszą odpowiedzialność za klucze API” — brak uwierzytelniania dwuskładnikowego w punkcie końcowym klucza przed 2023 r.\n„Podejmujemy działania wobec osób naruszających przepisy” — od lipca 2016 r. nie opublikowano żadnych danych dotyczących egzekwowania przepisów w podziale na poszczególnych operatorów\n„Zgodziłeś się na warunki” — w schemacie przejęcia konta zgoda jest przekazywana przez skrypt, a nie przez właściciela konta\nWnioski · Co wynika z akt sprawy i o co wnioskujemy\nWyniki. Dokumenty, o które prosimy.\nOgraniczenia dotyczące kontekstu i źródła\n\nKażdy z poniższych ustaleń odnosi się do opatrzonego datą wpisu w rejestrze publicznym, o którym mowa w powyższych sekcjach. Wnioski skierowane są do organów, które mogą wymusić dostęp do jedynej rzeczy, do której niniejsze dochodzenie nie ma dostępu: własnych rejestrów Valve dotyczących egzekwowania przepisów, dostępu i przetwarzania danych.\n\nKażdy wniosek jest następstwem ustaleń opatrzonych datą. Organy mogą zwrócić się o udostępnienie dokumentów, których uzyskania nie można wymusić w ramach niniejszego dochodzenia opartego na źródłach publicznych.\n\nCo wynika z dokumentów publicznych\n44 aktywne platformy uwierzytelniają się za pośrednictwem oddzielnej domeny podlegającej rejestracji — 27 z opublikowanym plikiem dowodowym dla poszczególnych tras, a 17 pochodzi z ręcznego gromadzenia danych i zostało wymienionych osobno. Na dzień 2026-09-22 główna domena 26 par została zablokowana w filtrze linków Steam, podczas gdy serwer obsługujący ich logowanie nie został zablokowany — csgogem.com zablokowany, api.csgem.com zarejestrowany od marca 2014 r. Steam otrzymuje tę nazwę hosta w openid.realm oraz openid.return_to przy każdym logowaniu. Sekcja 3\nW dniu 13 lipca 2016 r. Valve publicznie wskazał ten mechanizm i zakazał jego stosowania, a w pismach procesowych z dnia 20 lipca 2016 r. wyznaczył dziesięciodniowy termin. W ciągu dziesięciu lat od upływu tego terminu nie opublikowano żadnych danych dotyczących egzekwowania przepisów w odniesieniu do poszczególnych operatorów. Sekcja 11\nPunkt końcowy klucza API sieciowego Steam wydawał poświadczenia o wysokich uprawnieniach, umożliwiające przeprowadzanie transakcji, wyłącznie na podstawie pliku cookie sesji, bez stosowania drugiego czynnika uwierzytelniającego przed rokiem 2023. Sekcja 5\nWniosek złożony na podstawie art. 15 RODO (numer zgłoszenia HT-2YBP-F7JP-D4VB) został zamknięty po trzech dniach wraz z linkiem do serwisu samoobsługowego, bez udostępnienia żadnych danych. Sekcja 18\nO co prosimy każdy organ\nKomisja ds. Gier Hazardowych stanu Waszyngton\nProszę ponownie otworzyć plik z 2016 roku. Proszę poprosić o szczegółowe zestawienie dla poszczególnych operatorów, wskazujące, które konta, boty i hosty zwrotne zostały zablokowane po upływie dziesięciodniowego okresu wypowiedzenia oraz którzy operatorzy odzyskali później dostęp. Sekcja 2\nHmbBfDI (Hamburg; Valve GmbH)\nNależy sprawdzić, czy odpowiedź udzielona na podstawie art. 15 była zgodna z obowiązkiem administratora danych, oraz zażądać ujawnienia danych dotyczących rejestracji klucza API oraz rejestrów dostępu, które mogą pomóc w identyfikacji sprawcy. Sekcja 18\nKoordynatorzy ds. usług cyfrowych (DSA)\nNależy umieścić informacje o routingu auth-host w rekordzie jako uwagę, a następnie ocenić, czy odpowiedź Valve spełnia określone wymagania po udokumentowaniu tej wiedzy. Sekcja 16\nKażda osoba, której dane dotyczą\nAby uzyskać te same dane dotyczące własnego konta, należy skorzystać z szablonu z art. 15; zapisane dane pozwalają ustalić, kto zainicjował reset lub utworzył klucz. Załącznik G\n\nWszystkie cztery wnioski mają ten sam cel: opublikowanie dokumentacji dotyczącej egzekwowania przepisów, dostępu do danych oraz ich przetwarzania, którą posiada wyłącznie Valve. Ostrzeżenie na stronie głównej, dziesięciodniowe zawiadomienie oraz strona samoobsługowa stanowią przejawy sprawowania kontroli. To, czy kontrola ta została faktycznie sprawowana, jest pytaniem, na które nie odpowiadają publiczne rejestry, a odpowiedź może udzielić organ regulacyjny.\n\nZałączniki — główne materiały dowodowe i materiały robocze\nZałącznik A — Korespondencja z adwokatami\nMemorandum dowodowe — materiały przekazane przez Źródło 1\n\nPodstawa dowodowa i status źródeł korespondencji z adwokatem, na którą powołano się w sekcjach 1, 18 i 19.\n\nPodstawa dowodowa i status źródła — dokumenty dostarczone przez źródło nr 1\nUżytkownik, którego trwałe zablokowanie stało się przyczyną niniejszej kontroli, nie jest jej przedmiotem. Nie badamy tutaj, czy blokada ta była uzasadniona, a niniejszy dokument nie ma na celu ani jej obrony, ani podważenia. Nie chodzi tu o konto. Liczy się treść: Źródło 1 — właściciel zablokowanego konta, który jako osoba, której dane dotyczą, otrzymał poniższą korespondencję od pełnomocnika Valve w związku z własnym wnioskiem złożonym na podstawie RODO — udostępnił tę korespondencję oraz towarzyszące jej akta sprawy, wraz z prawem do ich publicznego wglądu. Imię i nazwisko nie zostało ujawnione; dokumenty opisano według daty, metadanych dotyczących autora oraz skrótu.\n\nKorespondencja ta została wysłana w odpowiedzi na wniosek złożony na podstawie RODO/DSAR. W jej trakcie pełnomocnik Valve złożył podpisane oświadczenie, w którym opisał funkcję, o której dział pomocy technicznej Steam wcześniej informował użytkowników, że nie jest technicznie możliwa. Poniższy akapit stanowi treść tego oświadczenia.\n\nDalsza analiza wygenerowanego fragmentu dziennika przeprowadzona przez autorów polega na pominięte w niniejszej dokumentacji w oczekiwaniu na wynik niezależnej oceny. Żadna inna część niniejszego postępowania nie opiera się na tej informacji.\n\nOświadczenie zapisane w protokole: ciągła telemetria na poziomie urządzenia\n\nW pkt 1.9 pisma przypisywanego pełnomocnikowi Valve adwokaci Valve stwierdzają: „W latach 2019–2023 z tego konta korzystano głównie za pomocą urządzenia, z którego logowano się również do kilkudziesięciu skradzionych kont Steam”.\n\nFakt: Pełnomocnik Valve opisuje w niniejszym piśmie korelację na poziomie urządzeń między kontami w okresie czterech lat. Steam Dział pomocy technicznej poinformował ofiary kradzieży, że śledzenie skradzionych przedmiotów lub powiązanie kont z urządzeniami nie było technicznie możliwe. Steam Guard Proces autoryzacji urządzeń jest publicznie udokumentowany, więc samo istnienie zapisów dotyczących poszczególnych urządzeń nie jest niczym nowym; nowością jest natomiast pisemne potwierdzenie pełnomocnika, że zapisy te są przechowywane i korelowane między kontami w okresie wieloletnim.\n\nDlaczego to ma znaczenie: Korelacja, która może powiązać jedno urządzenie z dziesiątkami przejętych kont w ciągu czterech lat, należy do tej samej kategorii danych, których, jak twierdził dział wsparcia, nie mógł udostępnić ofiarom. Dane tej klasy pozwoliłyby zidentyfikować konta i urządzenia w łańcuchu kradzieży i odsprzedaży. Jakie dane istnieją, jak długo są przechowywane oraz na jakiej podstawie są one zatajane przed osobami, których dane dotyczą – to pytania, na które powinien odpowiedzieć organ nadzorczy.\n\nŹródło: pismo pełnomocnika Valve z dnia 1 października 2025 r., pkt 1.9, wraz z 830-stronicowym załącznikiem w formacie PDF · otrzymane przez Źródło 1 w odpowiedzi na wniosek złożony na podstawie art. 15 RODO · wartość SHA-256 załącznika zapisana w disclosure-audit.json · Sam list nie został zamieszczony; pominięto nazwy kont oraz dane stron trzecich.\n\nStatus: otwórz\nMateriały źródłowe są dostępne w archiwum dowodów.\nZałącznik B — Wygenerowany plik PDF · kontrola redakcyjna\nZmiany w dostarczonym pliku PDF mają charakter kosmetyczny: zakryty tekst nadal można wyodrębnić\n\nKancelaria Valve odpowiedziała na wniosek o dostęp do danych złożony na podstawie RODO, dołączając 830-stronicowy załącznik, w którym zredagowane fragmenty zostały zamalowane na tekście, zamiast je usunąć. 902,270 znaków znajduje się pod czarnymi paskami i można je od razu wyodrębnić za pomocą narzędzia do wyodrębniania tekstu — w tym identyfikatory stron trzecich, których ujawnienie miały zapobiegać te paski. Publikowane są tu wyłącznie dane zbiorcze; nie zamieszczono żadnych treści objętych ochroną, a sam załącznik nie został opublikowany.\n\n1. Wyniki kontroli geometrii\n\nOdpowiedź na podstawie art. 15 RODO z dnia 1 października 2025 r. dołączono 830-stronicowy załącznik w formacie PDF (metadane producenta Aspose.PDF dla .NET, utworzone i zmodyfikowane tego samego dnia). Autorzy przeprowadzili kontrolę geometrii na poziomie stron: dla każdej strony zlokalizowano nieprzezroczyste, niemal czarne prostokąty narysowane na warstwie tekstowej, a następnie zliczono znaki możliwe do odczytania znajdujące się pod nimi.\n\nNa podstawie wygenerowanego pliku\n902,270\nZnaki, które nadal można odczytać spod czarnych pasków\nLiczba rzeczywista, a nie szacunkowa. Jest to liczba uwzględnionych postaci — a nie ofiar, przypadków ponownej identyfikacji ani zdarzeń.\n830 / 830\nStrony, których to dotyczy — wszystkie strony\n986\nProstokąty nad tekstem, który można wyodrębnić\n1,329\nŁączna liczba nieprzezroczystych czarnych prostokątów\nCzarne paski są nanoszone na warstwę tekstową; nie powodują one jej usunięcia. Tekst znajdujący się pod paskami można wyodrębnić za pomocą standardowych narzędzi do obsługi plików PDF. Publikowane są wyłącznie zbiorcze dane liczbowe; żadna z zakrytych treści nie jest tutaj przytoczona.\nDemonstracja kryminalistyczna: rozdzielanie warstw\nASPOSE.PDF DLA .NET – MAKIETA NAKŁADKI WEKTOROWEJ (ZAŁĄCZNIK, STR. 412)\n\nZgłoszenie dotyczące konta: [LOGOWANIE: redacted_user_667]\n\nPowód podany przez użytkownika: [TEKST: „Użytkownik zgłasza zduplikowane przedmioty w ekwipunku oraz nieuczciwe praktyki handlowe...”]\n\nNa pierwszym planie: <path fill=\"#000\" />Błąd: Podstawowy strumień UTF-8 pozostał nienaruszony\nŹródło: załącznik w formacie PDF do pisma radcy prawnego z dnia 1 października 2025 r. (830 stron, metadane producenta Aspose.PDF dla .NET) · obliczenia autorów, metoda i liczba stron w disclosure-audit.json · SHA-256 załącznika zapisanego w tym samym pliku · sam załącznik nie jest publikowany.\n2. Dlaczego ma to znaczenie dla odpowiedzi osoby, której dane dotyczą\n\nPełnomocnik Valve przesłał ten plik osobie, której dane dotyczą, w odpowiedzi na wniosek tej osoby o udostępnienie jej własnych danych. Przekreślenia te mają charakter wyłącznie kosmetyczny: tekst pod nimi nigdy nie został usunięty, więc identyfikatory stron trzecich, które miały zostać ukryte za pomocą tych przekreśleń, trafiły do odbiorcy wraz z plikiem. Redakcja, którą można usunąć za pomocą narzędzia do wyodrębniania tekstu, niczego nie ukrywa, a ponadto uniemożliwia odbiorcy ustalenie, które informacje zostały ujawnione, a które nie.\n\nArtykuł 15 ust. 4 stanowi podstawę istnienia tych ograniczeń: prawo do uzyskania kopii nie może naruszać praw i wolności innych osób. Jest to obowiązek, którego ta produkcja nie spełniła. To, czy można to uznać za naruszenie danych osobowych w rozumieniu art. 4 ust. 12, leży w gestii organu nadzorczego; samo ujawnienie jest mierzalne w pliku i możliwe do odtworzenia przez każdego, kto posiada te same bajty — skrót SHA-256 jest opublikowany, natomiast załącznik nie.\n\nTo, co znajdowało się pod kratami, nie były numery kont. Był to zbiór zgłoszeń użytkowników dotyczących wnioskodawcy wraz z danymi ich autorów: Steam loginów, które – ponieważ login rzadko jest używany wyłącznie na Steam – pozwalają zidentyfikować osobę, która się za nimi kryje — według szacunków autorów ponad 60% użytkowników wymienionych w dokumencie można w pełni zidentyfikować — wraz z nieocenzurowaną, nieprzeredagowaną treścią ich wpisów. Tekst ten zawiera życzenia śmierci oraz obelgi skierowane pod adresem narodowości osoby, która złożyła wniosek. Niektóre z zidentyfikowanych w ten sposób osób to nieletni. Produkcja przekazała osobie, na którą złożyła skargę, listę z nazwiskami dziennikarzy, a właśnie takiej szkody ma zapobiegać art. 15 ust. 4.\n\nKolejność znaków w pliku ma równie duże znaczenie jak jego zawartość. W odpowiedzi na wniosek najpierw zażądano dodatkowego potwierdzenia tożsamości, argumentując, że adres e-mail wnioskodawcy, utworzony przy użyciu pseudonimu, nie zawierał jego nazwiska; w trakcie wynikającego z tego opóźnienia konto zostało trwale zablokowane. W piśmie, w którym ostatecznie przekazano dane – ponad sześć tygodni po upływie terminu określonego w art. 12 ust. 3 – grożono adresatowi postępowaniem karnym i wstrzymano przekazanie pozostałej części jego danych do czasu wyjaśnienia przez niego aktywności na koncie przed pełnomocnikiem. Ujawnienie tych informacji rozstrzyga również dwie kwestie, na które Valve nie udzielił publicznej odpowiedzi: przedstawione dokumenty wskazują na powiązania między kontami sięgające aż do 2019 roku oraz na wewnętrzną telemetrię o zakresie, którego Valve nigdy nie opisał.\n\nZakres niniejszego rozdziału: Niniejsza uwaga ogranicza się do mechanizmów redakcyjnych, ocenionych na podstawie dostarczonego pliku. Dalsza analiza dostarczonych logów przeprowadzona przez autorów została wstrzymana do czasu przeprowadzenia niezależnej weryfikacji i nie została uwzględniona w żadnej innej części niniejszej dokumentacji.\n\nDowód: pismo pełnomocnika z dnia 1 października 2025 r. wraz z załącznikiem w formacie PDF (kod SHA-256 zapisany w pliku audytowym); Pomiary w formacie PDF na poziomie strony i metoda ↗. Kolejność wydarzeń – złożenie wniosku, odmowa na stronie 8 oraz opis ujawnionych dokumentów – została szczegółowo przedstawiona w relacji PhishDestroy, „Mój pies kontra elitarni prawnicy specjalizujący się w RODO”, 17 sierpnia 2026 r. ↗ zarchiwizowano 2026-08-21 ↗. Nazwy kont i dane stron trzecich zostały tutaj pominięte; nie przedstawiono żadnych informacji objętych paskami.\n\nNa stronie 8 pisma przewodniego odrzuca się część wniosku i podaje się pisemne uzasadnienie: Nie jest możliwe udzielenie bardziej szczegółowej informacji ze względu na ochronę danych osobowych innych użytkowników platformy Steam… — nie można udzielić bardziej szczegółowej odpowiedzi, ponieważ należy chronić dane osobowe pozostałych Steam użytkowników. 830-stronicowy załącznik znajdował się w tej samej przesyłce. To, co zasłaniały paski, to nie numery kont: były to zgłoszenia złożone przeciwko wnioskodawcy, wraz z nazwiskami ich autorów i załączonymi nieocenzurowanymi wiadomościami w oryginalnej postaci. Posiadacz konta zwrócił się do Valve, za pośrednictwem swojego pełnomocnika, o udostępnienie jego własnej dokumentacji; to, co mógł z niej wyodrębnić, dotyczyło innych osób. Żadna z informacji zawartych w tym załączniku nie dotyczy tego, kto narysował te ramki. Potwierdza on jedynie, że ochrona Valve, na którą powołano się jako podstawę do nieudostępnienia danych, jest tą samą ochroną, której nie zapewniono w przypadku tego samego przekazu, w tej samej kopercie, tego samego dnia.\nDokumentacja dotycząca wsparcia i korespondencji prawnej\n\nŹródło: https://phishdestroy.io/steam_dossier/pl/index#exhibit-gallery-section\n\nZałącznik D — Gromadzenie materiałów źródłowych\nWybrane dokumenty źródłowe\n\nSześć wpisów z archiwum — trzy zgłoszenia na GitHubie w systemach śledzenia Valve oraz trzy wpisy na Reddicie dotyczące spornych wyników pomocy technicznej. Każde źródło jest powiązane z danym zgłoszeniem, zapisanym tekstem oraz pytaniem, które ono rodzi.\n\n1 / 6 wybrane rekordy\nWybierz rekord źródłowy\nGH-01 / GITHUBOtwórz w zapisanej kompilacji\nKlucze sprzętowe, zamówione w 2016 r.\n\nValveSoftware / steam-for-linux · #4521 · 2016-06-27\n\nJeden z użytkowników poprosił Valve o wprowadzenie obsługi kluczy sprzętowych U2F jako alternatywnego drugiego czynnika uwierzytelniającego. Zapisane zgłoszenie ma przypisane etykiety „Prośba o dodanie funkcji” oraz „Zweryfikowane”, a jego status jest oznaczony jako „otwarte”.\n\nProszę o dodanie obsługi klucza USB U2F w serwisie Steam jako alternatywnego rozwiązania.\n\nFragment zgłoszenia na GitHubie ↗\nUdokumentowany zapis\nWniosek o wprowadzenie dodatkowego zabezpieczenia konta, opatrzony datą i opublikowany w systemie śledzenia zgłoszeń serwisu Valve, oznaczony jako „sprawdzony”.\nŻądanie rozliczalności\nOpublikuj decyzję dotyczącą produktu, termin udzielenia odpowiedzi oraz zakres ochrony przyznanej po przeprowadzeniu weryfikacji.\nOdczytaj zapisany rekord →Otwórz GitHub ↗\nW dokumentacji: Środki zabezpieczające konta →Archiwum nr 484 · kompilacja 2026-09-17\nGH-02 / GITHUBOtwórz w zapisanej kompilacji\nRaporty o awariach bez skutecznej możliwości rezygnacji\n\nValveSoftware / steam-for-linux · #6459 · 2019-08-18\n\nAutor opisu przedstawia przypadek klienta Steam z 12 sierpnia 2019 r. korzystającego z systemu Ubuntu 16. Twierdzi on, że wyłączenie opcji „crash-upload” nie zostało zachowane po ponownym uruchomieniu systemu, i załącza odpowiednią konfigurację.\n\nJeśli wyłączę parametr `ServerURL`, po każdym ponownym uruchomieniu zostaje on nadpisany.\n\nFragment zgłoszenia na GitHubie ↗ zarchiwizowane 2026-04-19 ↗\nUdokumentowany zapis\nSzczegółowa skarga dotycząca prywatności zawierająca datę zgłoszenia przez klienta, informacje o systemie operacyjnym oraz fragment konfiguracji. Zapisane zgłoszenie ma status „otwarte”.\nŻądanie rozliczalności\nNależy określić, jakiego dochodzenia dotyczy sprawa, które wersje oprogramowania zostały tym dotknięte oraz jaką zmianę wprowadzono, aby opcja rezygnacji zaczęła obowiązywać.\nOdczytaj zapisany rekord →Otwórz GitHub ↗zarchiwizowane 2026-04-19 ↗\nW dokumentacji: Poproś o dokumenty źródłowe →Archiwum nr 467 · kompilacja 2026-09-17\nGH-03 / GITHUBOtwórz w zapisanej kompilacji\nZgłoszono nadużycie biletu uwierzytelniającego do Valve\n\nValveSoftware / Source-1-Games · #3857 · 2022-02-26\n\nAutor twierdzi, że operator serwera zachowywał Steam bilety uwierzytelniające po rozłączeniu się graczy oraz stosował wprowadzające w błąd wykazy serwerów. W poście zwraca się do Valve o zajęcie się tą sprawą.\n\nSprawiają, że ich serwery sprawiają wrażenie przepełnionych.\n\nFragment zgłoszenia na GitHubie ↗\nUdokumentowany zapis\nZgłoszenie nadużycia opublikowane w trackerze Valve w dniu 26 lutego 2022 r. Jego status to „otwarte”; zgłoszenie zawiera linki do zrzutów ekranu.\nŻądanie rozliczalności\nNależy przedstawić wyniki dochodzenia oraz dokumentację działań naprawczych dotyczących zgłoszonego nadużycia biletu uwierzytelniającego.\nOdczytaj zapisany rekord →Otwórz GitHub ↗\nW dokumentacji: Zakres zbioru danych →Archiwum nr 768 · kompilacja 2026-09-17\nRD-01 / REDDITOpis autora\n44 sporne transakcje zakupu na rynku\n\nr/DotA2 · pseudonim autora nieujawniony · 2022-07-07\n\nAutor informuje o 44 nieautoryzowanych transakcjach zakupu w serwisie Market w dniu 6 lipca 2022 r. oraz o stratach w wysokości około $500+. Twierdzi, że uwierzytelnianie dwuskładnikowe było włączone, i opisuje powtarzające się, szablonowe odpowiedzi od działu pomocy technicznej.\n\nTo już moje drugie zgłoszenie, a wciąż nie otrzymałem od Steam żadnej odpowiedzi, która nie byłaby automatyczną, skopiowaną i wklejoną szablonową odpowiedzią.\n\nFragment wpisu na Reddicie ↗ zarchiwizowano 2025-03-20 ↗\nUdokumentowany zapis\nPrzegląd spornych zakupów z datami, zawierający linki do zrzutów ekranu z transakcji oraz odpowiedź działu obsługi klienta. Kwoty i opis zdarzeń pochodzą z relacji autora.\nŻądanie rozliczalności\nPorównaj sporne zakupy z dziennikami transakcji i sesji. Wyjaśnij, na jakich dowodach opiera się decyzja działu pomocy technicznej.\nOdczytaj zapisany rekord →Otwórz Reddit ↗zarchiwizowano 2025-03-20 ↗\nW dossier: Wsparcie i egzekwowanie →Archiwum nr 4,533 · kompilacja 2026-09-17\nRD-02 / REDDITOpis autora\nTrwały zakaz i zamknięta procedura odwoławcza\n\nr/ohnePixel · pseudonim autora nieujawniony · 2024-12-09\n\nAutor kwestionuje nałożenie stałego blokady i twierdzi, że jako uzasadnienie podano podejrzenie przeniesienia konta oraz zgłoszenia ze strony społeczności. Opisuje zamknięte zgłoszenia oraz plany wystąpienia o udostępnienie swoich danych osobowych.\n\nWyjaśniłem swoją sytuację i poprosiłem o więcej szczegółów, ale oni trzymają się swojej decyzji i zamykają moje zgłoszenia.\n\nFragment wpisu na Reddicie ↗\nUdokumentowany zapis\nZachowane konto apelu, zawierające powody, które według autora przemawiają za udzielonym wsparciem, oraz linki do czterech zdjęć. Data publikacji pochodzi z wybranego eksportu danych dotyczących wsparcia.\nŻądanie rozliczalności\nNależy wskazać dowody uzasadniające nałożenie stałego zakazu oraz procedurę odwoławczą, w ramach której można go zakwestionować. Zamknięcie postępowania odwoławczego nie stanowi uzasadnienia decyzji.\nOdczytaj zapisany rekord →Otwórz Reddit ↗\nW dokumentacji: Poproś o udostępnienie dokumentów źródłowych →Archiwum nr 4,766 · kompilacja 2026-09-17\nRD-03 / REDDITOpis autora\nZresetowanie procesu odzyskiwania i zgłoszona strata wynosząca $10,000\n\nr/legaladvice · pseudonim autora nieujawniony · 2025-05-09\n\nAutor twierdzi, że dział pomocy technicznej zresetował dane uwierzytelniające i wyłączył zabezpieczenia konta po tym, jak ktoś inny zgłosił prośbę o odzyskanie dostępu. Autor informuje o utracie kwoty około US$10,000 z nieaktywnego konta.\n\nSteam Obsługa zresetowała moje hasło i wyłączyła wszystkie zabezpieczenia mojego konta.\n\nFragment wpisu na Reddicie ↗\nUdokumentowany zapis\nZachowany zarzut dotyczący tego, że proces odzyskiwania danych pomija zabezpieczenia konta. W zapisanym poście autor przytacza informacje, które otrzymał od działu pomocy technicznej.\nŻądanie rozliczalności\nNależy ustalić, kto zatwierdził zresetowanie hasła, jakie dowody potwierdzające tożsamość zostały przez tę osobę zaakceptowane oraz jaki jest dziennik dostępu. Odzyskiwanie dostępu do konta stanowi część mechanizmów zabezpieczających systemu Valve.\nOdczytaj zapisany rekord →Otwórz Reddit ↗\nW dokumentacji: Poproś o udostępnienie dokumentów źródłowych →Archiwum nr 4,592 · kompilacja 2026-09-17\n\nSześć wybranych wpisów. Opisy na GitHubie przedstawiają zapisane kompilacje. Wpisy na Reddicie zawierają relacje autorów.\n\nPobierz sześć nagrań ↓\n\nWersja z możliwością przeszukiwania zawiera 16,319 odrębnych rekordów: 393 wpisy na Trustpilot, 5,635 na Reddicie, 2,395 na GitHubie, 276 wpisów w sieci oraz 7,620 w wiki. Kilka wpisów może dotyczyć tego samego zdarzenia. Oddzielny plik eksportu główny zawierający 40,448 wiersze ma inny zakres.\n\nPrzeszukaj całe archiwum ↗ · Utwórz manifest ↗ · Zakres zbioru danych i liczby →\n\nZałącznik E — Studium przypadku\nArchiSteamFarm oraz klauzula dotycząca automatyzacji\n\nNarzędzie typu open source służące do „farmowania” kart, które – jak wynika z własnego działu FAQ – działa na milionach kont, co stoi w sprzeczności z klauzulą Umowy abonamentowej (§ 4.C) zakazującą automatyzacji. Mechanizmy działania — co farma musi kupić od Valve, zanim będzie mogła cokolwiek wygenerować, dlaczego każdy sposób wypłaty środków z karty stanowi naruszenie licencji, historia egzekwowania przepisów oraz kto moderuje gospodarkę kartową — zostały szczegółowo opisane w Załącznik V ↗.\n\nUmowa abonamentowa Steam, § 4.C, stanowi:\n\n„Nie wolno w żaden sposób wykorzystywać żadnych skryptów, botów, makr ani innych systemów niekontrolowanych przez człowieka („automatyzacja”) do interakcji z treściami i usługami na stronie Steam”. — Steam Umowa abonamentowa § 4.C (aktualna) ↗ zarchiwizowano 2026-09-18 ↗\n\nValve zapewnia przestrzeganie tej klauzuli. Robi to naprawdę dobrze. Często zadawane pytania dotyczące ArchiSteamFarm (ASF) — narzędzie typu open source, które zgodnie z opisem zawartym w jego dokumentacji działa na ponad kilka milionów kont Steam od czasu pierwszej wersji ponad 11 lat temu — zawiera trzy Steam komunikaty pomocy technicznej dotyczące trwałego zablokowania użytkowników, którzy prowadzili sieci botów. Valve wykryło te sieci, zidentyfikowało je i zlikwidowało. Istotne nie jest zatem to, czy Valve potrafi wykrywać automatyzację na dużą skalę.\n\nOficjalna strona projektu ArchiSteamFarm Często zadawane pytania bezpośrednio odnosi się do ryzyka wprowadzenia zakazu:\n\n„Jest to niezwykle mało prawdopodobne, biorąc pod uwagę fakt, że ASF jest używane na ponad kilku milionach kont Steam od czasu jego pierwszej wersji, która pojawiła się ponad 11 lat temu — ale nadal jest to możliwe, niezależnie od faktycznego prawdopodobieństwa.”\n\n„Valve wyraźnie przyznaje, że istnieją »Steam leniwcy«, jak tu stwierdzono, więc jeśli mnie pytasz, to jestem całkiem pewien, że gdyby im to nie odpowiadało, już dawno by coś z tym zrobili, zamiast zwracać uwagę, że mogą oni powodować problemy w kontekście VAC. Kluczowym pojęciem jest tutaj Steam „idlerzy”, na przykład ASF, a nie „idlerzy” związani z grami.\"\n\n— ArchiSteamFarm Często zadawane pytania, JustArchiNET. Źródło: Wiki serwisu GitHub ↗ · zweryfikowano dosłownie 2026-09-22\n\nW tym samym sekcji FAQ na pytanie „Czy komuś za to zablokowano konto?” odpowiedz brzmi: Tak, i przytacza treść wiadomości, którą Steam Support wysłał do trzech z nich:\n\n1,000+ boty · zablokowano handel\n„Wygląda na to, że to konto służyło do zarządzania siecią kont botów. Wykorzystywanie botów stanowi naruszenie postanowień Umowy abonamentowej Steam.”\n\nPonad 170 botów · trwale zablokowanych, zimowa wyprzedaż 2017\n„To konto było wykorzystywane do nielegalnego gromadzenia kart kolekcjonerskich na Steam, a także do powiązanych działań, nie tylko o charakterze komercyjnym. Konto zostało trwale zablokowane, a dział pomocy technicznej Steam nie może udzielić dalszej pomocy w tej sprawie.”\n\nPonad 120 botów · trwale zablokowanych\n„To konto oraz inne zostały wykorzystane do przeciążenia naszej infrastruktury sieciowej, co stanowi naruszenie zasad postępowania w sieci określonych w punkcie Steam”.\n\n— Steam Komunikaty pomocy zamieszczone w sekcji ArchiSteamFarm FAQ, w części „Czy ktoś został za to zablokowany?”. Źródło ↗ · zweryfikowano dosłownie 2026-09-22\n\nUmieść te dwa zapisy obok siebie. Zidentyfikowano prywatnego użytkownika korzystającego z 1,000 botów do farmowania, poinformowano go, że „korzystanie z botów stanowi naruszenie Steam Umowy abonamentowej”, a następnie trwale usunięto jego konto. Platformy komercyjne opisane w niniejszym dossier prowadzą zautomatyzowane Steam konta w ramach swojej podstawowej działalności, na znacznie większą skalę, i uwierzytelniają się za pomocą własnego OpenID Valve przy każdym logowaniu — a w przypadku żadnej z nich nie opublikowano żadnych danych dotyczących egzekwowania przepisów przez poszczególnych operatorów. Ta klauzula działa. Pytanie brzmi: przeciwko komu jest skierowana.\n\nASF nie jest tu o nic oskarżane, a jego interpretacja stanowiska Valve jest wyłącznie jego własną — autor wyraźnie stwierdza, że „ASF nie jest upoważnione przez Valve”. Narzędzie to służy tutaj jako przyrząd pomiarowy: pokazuje, że Valve wykrywa sieci botów, wymienia je z nazwy i blokuje na stałe. Valve może zamknąć tę kwestię jednym zdaniem, publikując informacje o tym, jakie komercyjne rozwiązania automatyzacyjne autoryzuje, oraz rejestr działań podjętych wobec pozostałych podmiotów w podziale na poszczególnych operatorów.\n\nW jaki sposób „farmowanie kart” wpływa na przychody Valve\n\nKarty kolekcjonerskie zdobyte w grze są sprzedawane na rynku społecznościowym Steam, który pobiera łączną opłatę w wysokości około 15% od każdej transakcji zrealizowanej na tym rynku; konto musi wydać $5.00 USD na Steam, zanim będzie mogło w ogóle otrzymać kartę; a zdobycie kart wymaga posiadania gry lub dokonania zakupów w grze. Nie szacuje się tutaj łącznej wartości przychodów — skala działalności jest podana wyłącznie zgodnie z informacjami zawartymi w sekcji FAQ serwisu ASF. W sekcji FAQ odnotowano również Valve cechy wyróżniające „Steam koła napędowe” (zdobywanie kart) z „osoby, które tylko się obijają w grach”; zobacz Najczęściej zadawane pytania dotyczące ASF ↗. Zasady działania zostały szczegółowo opisane w Załącznik V — skala oraz pułapka związana z wykorzystaniem komercyjnym.\n\nTematArchiSteamFarm — automatyczne zdobywanie kart\nPodana skalaMiliony kont (zgodnie z sekcją FAQ na stronie ASF — dokładna liczba aktywnych kont nie została zweryfikowana)\nZliczone, a nie podane jako kwota10,880,610 wszystkich wpisów API w własnej grupie ASF Steam (5,360,499 bez ograniczeń, jak pokazuje Steam) — „miliony” w sekcji FAQ to nie wymysł, tylko liczba wpisów. 88.97% nie podlegają żadnemu Steam zakazowi. Pełny spis dotyczący zakazu ↗\nInformacje zawarte w dokumentacji samego narzędzia\nASF loguje się na konta w trybie bezinterfejsu i pozostawia gry w stanie bezczynności w celu uzyskania kart, nie uruchamiając klienta Steam (zgodnie z dokumentacją projektu).\nW sekcji FAQ wyjaśniono, że Valve zdaje sobie sprawę z istnienia „Steam leniwców” oraz że „gdyby im to przeszkadzało, już dawno by coś z tym zrobili”.\nOd ponad 11 lat nie odnotowano żadnych ukierunkowanych działań egzekucyjnych (zgodnie z sekcją „Często zadawane pytania”); wynikająca z tego sprzedaż kart na platformie Community Market wiąże się z łączną opłatą Steam wynoszącą około 15%.\nW sekcji FAQ podano zalecany limit dziesięciu kont na operatora i przypisano to Valve: „Zalecenie to opiera się na wewnętrznych wytycznych Valve, a także na naszych własnych sugestiach”. Valve nie opublikowało żadnych takich wytycznych.\nLimit techniczny, zgodnie z tym samym FAQ: „za pomocą jednego adresu IP i jednej instancji ASF można uruchomić od 100 do 200 botów”.\nCzas gry w trybie „farmowania” jest rejestrowany przez Valve — „zazwyczaj jest aktualizowany mniej więcej co 30 minut” — a w § 4.C wymieniono „fałszowanie statystyk gry (np. zawyżanie liczby zwycięstw lub porażek, punktów XP, czasu gry)” jako czynność zabronioną.\nŹródła\nOficjalna wiki JustArchi z często zadawanymi pytaniami (FAQ) dotyczącymi ASF ↗ ArchiSteamFarm repozytorium ↗ zarchiwizowane 2026-09-24 ↗\nKlauzula dotycząca automatyzacji jest jednoznaczna; w sekcji FAQ fundacji ASF od lat podaje się, że narzędzie to działa na milionach kont; nie odnotowano żadnych przypadków ukierunkowanych działań mających na celu jego zablokowanie. Rozbieżność między przepisem a jego stosowaniem jest faktem; przyczyna tego zjawiska nie została tutaj ustalona.\nPełna ekspozycjaGospodarka kartowa: proces, skala, licencja i kto ją nadzoruje ↗Co gospodarstwo musi kupić od Valve, zanim będzie mogło wyprodukować choćby jedną kartę; dwa akapity § 4.C, które definiują „farmowanie kart” na podstawie jego skutków; dlaczego każdy sposób spieniężenia karty stanowi naruszenie licencji Valve, podczas gdy Valve pobiera opłatę przy wejściu; historia egzekwowania przepisów, w tym fala VAC z czerwca 2025 r. oraz blokowanie łańcuchowe na podstawie wspólnego numeru telefonu; oraz pracownik Valve i moderatorzy społeczności, którzy zarządzali usługami wymiany kart i listy zablokowanych w okolicy Steam.Spis dotyczący zakazuNie pytaliśmy Valve, jak duże jest to gospodarstwo. Po prostu je policzyliśmy. ↗10,880,610 wszystkich kont (z ograniczeniami i bez) odczytanych z własnej grupy Steam użytkownika ArchiSteamFarm, do której oprogramowanie domyślnie dołącza automatycznie przy pierwszym uruchomieniu, chyba że użytkownik odznaczy opcję dołączenia do grupy (obejmuje to zarówno komercyjne farmy botów, jak i zwykłych graczy, którzy pozostawili domyślne ustawienie włączone). 88.97% nie ma na koncie żadnego rodzaju blokady Steam; spośród 11%, które ją mają, 99.8% to kosmetyczne blokady społecznościowe, które nigdy nie uniemożliwiają handlu. Po zweryfikowaniu z SteamRep, 67.77% z wymienionych oszustów pozostaje na wolności po uchyleniu blokad antycheatowych. Z podziałem według daty rejestracji, lokalizacji geograficznej i czasu aktywności — rzeczywista skala, zmierzona, a nie opisana.\n\nAppendix F — Working ledger\n\nRules ledger: clauses against recorded platforms\n\nWybierz regułę; w rejestrze wyświetlone zostaną zarejestrowane platformy oznaczone tą regułą wraz z ich główną domeną, zadeklarowanym hostem uwierzytelniającym oraz zapisanym wynikiem filtru linków. Zablokowana strona internetowa, inna domena do logowania: postępuj zgodnie z regułą aż do pozostałej trasy.\n\n175powiązane rekordy\nzgodnie z tą zasadą\n174 domeny główne0 Wspomnienia o C&D\nFRAGMENT PRZEPISU / SSA § 2.G\nWykorzystanie komercyjne i naliczanie opłat za konto\n“…exploit the Content and Services or any of its parts for any commercial purpose, except as expressly permitted elsewhere in this Agreement (including any Subscription Terms or Rules of Use).”\nŚLEDŹ WYNIKI\nRejestr platformy 175\nLiczby w skali są szacunkami opartymi na danych źródłowych\n\n175 z bazy danych „175”\n\nUsługi / grupa macierzysta\tDomena główna / rejestr\tZaobserwowana domena uwierzytelniająca / wiek\tSkala / zarejestrowana reakcja\n\nCasino\n\tcsgoempire.com\n11.3 yearsRegistered 2015-06-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgoempirelogin4.com\n6.2 yearsRegistered 2020-07-20\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustreaper.com\n23.2 yearsRegistered 2003-06-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustreaper.com\n23.2 yearsRegistered 2003-06-24\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustly.com\n12.4 yearsRegistered 2014-05-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustly.com\n12.4 yearsRegistered 2014-05-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette Casino\n\tcsgofast.com\n11.5 yearsRegistered 2015-03-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsteam-login.authtofast.com\n83 daysRegistered 2026-06-30\nRDAP ↗ · authtofast.com (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tduelbits.com\n6.6 yearsRegistered 2020-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nswitchflips.com\n6.4 yearsRegistered 2020-04-21\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opener\n\tfarmskins.com\n10.5 yearsRegistered 2016-03-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsteam.kobal.cc\n9.7 yearsRegistered 2017-01-07\nRDAP ↗ · kobal.cc (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgoluck.com\n9.3 yearsRegistered 2017-05-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgoluck.com\n9.3 yearsRegistered 2017-05-18\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tinsane.gg\n7.5 yearsRegistered 2019-04-02\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.insane.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcs2skin.com\n3.5 yearsRegistered 2023-03-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncs2skin.com\n3.5 yearsRegistered 2023-03-06\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tjuice.gg\n7.9 yearsRegistered 2018-10-19\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nletmeinjuice.com\n2.4 yearsRegistered 2024-04-15\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tggdrop.com\n8.6 yearsRegistered 2018-02-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nggauth.com\n3.4 yearsRegistered 2023-05-03\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Casino\n\thowl.gg\n9.5 yearsRegistered 2017-03-16\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhowl.uno\n41 daysRegistered 2026-08-11\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tchicken.gg\n5.7 yearsRegistered 2021-01-11\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nchicken.gg\n5.7 yearsRegistered 2021-01-11\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgocasino.gg\n2.6 yearsRegistered 2024-02-17\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.csgocasino.gg\n2.6 yearsRegistered 2024-02-17\nWHOISFREAKS ↗ · csgocasino.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Casino\n\thunt.gg\n6.9 yearsRegistered 2019-11-04\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.hunt.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Battles\n\tcsbattle.com\n9.8 yearsRegistered 2016-12-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsbattle.com\n9.8 yearsRegistered 2016-12-10\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskinrave.gg\n3.1 yearsRegistered 2023-08-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinrave.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsdouble.gg\n261 daysRegistered 2026-01-03\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsdouble.gg\n261 daysRegistered 2026-01-03\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustchance.com\n8.0 yearsRegistered 2018-10-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhgfuihd.com\n7.6 yearsRegistered 2019-01-27\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Automation\n\tcobaltlab.tech\n3.5 yearsRegistered 2023-03-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncobaltauth.com\n1.7 yearsRegistered 2025-01-07\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\traided.gg\n171 daysRegistered 2026-04-03\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.raided.gg\n171 daysRegistered 2026-04-03\nIP2WHOIS ↗ · raided.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustneo.gg\n1.3 yearsRegistered 2025-06-20\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustneo.gg\n1.3 yearsRegistered 2025-06-20\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tsplits.gg\n3.7 yearsRegistered 2023-01-23\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsplits.gg\n3.7 yearsRegistered 2023-01-23\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Upgrader\n\tupgrader.pro\n1.2 yearsRegistered 2025-07-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nupgauth.space\n38 daysRegistered 2026-08-14\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskin.fans\n8.2 yearsRegistered 2018-07-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skinfans.com\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\thotpizza.one\n1.8 yearsRegistered 2024-12-07\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhotpizza.one\n1.8 yearsRegistered 2024-12-07\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tg4skins.com\n10.1 yearsRegistered 2016-08-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.g4s.to\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2royal.com\n4.1 yearsRegistered 2022-08-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ntf2auth.com\n5.2 yearsRegistered 2021-07-27\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2hunt.com\n8.7 yearsRegistered 2018-01-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrstspcl.com\n6.1 yearsRegistered 2020-08-08\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2.bet/coinflip\n8.4 yearsRegistered 2018-05-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ntf2.bet\n8.4 yearsRegistered 2018-05-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\topenstars.gg\n131 daysRegistered 2026-05-13\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nopenstars.gg\n131 daysRegistered 2026-05-13\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tskins.com\n25.1 yearsRegistered 2001-08-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skins.com\n25.1 yearsRegistered 2001-08-08\nRDAP ↗ · skins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\twhite.market\n9.6 yearsRegistered 2017-03-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwhite.market\n9.6 yearsRegistered 2017-03-01\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tmoon.market\n7.6 yearsRegistered 2019-02-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmoon.market\n7.6 yearsRegistered 2019-02-27\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tcsfloat.com\n5.2 yearsRegistered 2021-07-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgofloat.com\n11.0 yearsRegistered 2015-09-29\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tskin.land\n4.7 yearsRegistered 2022-01-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skin.land\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\thaloskins.com\n2.8 yearsRegistered 2023-12-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhaloskins.com\n2.8 yearsRegistered 2023-12-10\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCorporate Market\n\tbuff.163.com\n29.0 yearsRegistered 1997-09-15\nRDAP ↗ · 163.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\nbuff.163.com\n29.0 yearsRegistered 1997-09-15\nRDAP ↗ · 163.com (parent)\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\tmarket.csgo.com\n26.6 yearsRegistered 2000-02-07\nRDAP ↗ · csgo.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\ndota2.net\n14.9 yearsRegistered 2011-10-29\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRegulated Market\n\tskinport.com\n8.0 yearsRegistered 2018-09-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinport.app\n6.3 yearsRegistered 2020-06-20\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMarketplace/Swap\n\tskinflow.gg\n3.8 yearsRegistered 2022-11-26\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinflow.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tskin.place\n6.0 yearsRegistered 2020-09-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skin.place\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tskinsmonkey.com\n5.7 yearsRegistered 2021-01-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinsmonkey.com\n5.7 yearsRegistered 2021-01-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCorporate Market\n\tskinbaron.de\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinbaron.com\n10.7 yearsRegistered 2015-12-22\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Market\n\trust.tm\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\ndota2.net\n14.9 yearsRegistered 2011-10-29\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tpirateswap.com\n6.0 yearsRegistered 2020-09-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nlogin.pirateswap.com\n6.0 yearsRegistered 2020-09-22\nRDAP ↗ · pirateswap.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Marketplace\n\tmannco.store\n8.6 yearsRegistered 2018-03-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmannco.store\n8.6 yearsRegistered 2018-03-02\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tskinswap.com\n9.9 yearsRegistered 2016-11-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinswap.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\texeskins.com\n2.1 yearsRegistered 2024-08-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nexeskins.com\n2.1 yearsRegistered 2024-08-14\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tbalticskins.com\n153 daysRegistered 2026-04-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nbalticskins.com\n153 daysRegistered 2026-04-21\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tcs.trade\n8.9 yearsRegistered 2017-11-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncs.trade\n8.9 yearsRegistered 2017-11-14\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\trapidskins.com\n4.5 yearsRegistered 2022-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.rapidskins.com\n4.5 yearsRegistered 2022-03-11\nRDAP ↗ · rapidskins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\ttradeit.gg\n9.1 yearsRegistered 2017-08-21\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nconnect-tradeit.com\n4.6 yearsRegistered 2022-02-23\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\t49skins.com\n3.4 yearsRegistered 2023-04-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.49skins.com\n3.4 yearsRegistered 2023-04-19\nRDAP ↗ · 49skins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tskinvault.gg\n3.4 yearsRegistered 2023-05-06\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinvault.gg\n3.4 yearsRegistered 2023-05-06\nIP2WHOIS ↗ · skinvault.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Trading\n\taim.market\n3.3 yearsRegistered 2023-05-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\naim.market\n3.3 yearsRegistered 2023-05-22\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Sell Portal\n\tskinout.gg\n5.6 yearsRegistered 2021-02-27\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skinout.gg\n5.6 yearsRegistered 2021-02-27\nIP2WHOIS ↗ · skinout.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Trading\n\tntskins.com\n230 daysRegistered 2026-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nntskins.com\n230 daysRegistered 2026-02-03\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Portal\n\tgamerpay.gg\n6.0 yearsRegistered 2020-10-02\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ngamerpay.gg\n6.0 yearsRegistered 2020-10-02\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Scrap Swap\n\tscrap.tf\n14.0 yearsRegistered 2012-09-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nscrap.tf\n14.0 yearsRegistered 2012-09-03\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Cashout\n\tmarketplace.tf\n14.0 yearsRegistered 2012-09-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmarketplace.tf\n14.0 yearsRegistered 2012-09-19\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Cashout\n\tskins.cash\n10.5 yearsRegistered 2016-03-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinscash.live\n6.8 yearsRegistered 2019-12-05\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgo.net\n14.2 yearsRegistered 2012-07-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncn2.easylot.net\n10.0 yearsRegistered 2016-09-03\nRDAP ↗ · easylot.net (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCommunity Hub\n\tcybershoke.net\n6.8 yearsRegistered 2019-11-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.cybershoke.net\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMatchmaker Hub\n\tfastcup.net\n14.6 yearsRegistered 2012-02-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.fastcup.net\n14.6 yearsRegistered 2012-02-16\nRDAP ↗ · fastcup.net (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Analytics\n\tleetify.com\n7.6 yearsRegistered 2019-03-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nleetify.com\n7.6 yearsRegistered 2019-03-01\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Analytics\n\tscope.gg\n7.8 yearsRegistered 2018-12-10\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nscope.gg\n7.8 yearsRegistered 2018-12-10\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tools\n\ttradeupspy.com\n6.5 yearsRegistered 2020-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.tradeupspy.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMarketplace\n\tcs.deals\n9.8 yearsRegistered 2016-12-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.cs.deals\n9.8 yearsRegistered 2016-12-03\nRDAP ↗ · cs.deals (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Price DB\n\tpricempire.com\n6.6 yearsRegistered 2020-01-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\npricempire.com\n6.6 yearsRegistered 2020-01-30\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Blackmarket\n\tFSB Market\n7.2 yearsRegistered 2019-07-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nFSB Market\n7.2 yearsRegistered 2019-07-27\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nReady-Account Hub\n\tz2u.com\n26.9 yearsRegistered 1999-11-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwww.z2u.com\n26.9 yearsRegistered 1999-11-10\nRDAP ↗ · z2u.com (parent)\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Gambling\n\tcsgoroll.com\n11.6 yearsRegistered 2015-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwww.csgoroll.com\nRegistry date unavailableRegistry date unavailable\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\trollbit.com\n11.9 yearsRegistered 2014-11-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrbsnin.com\n3 daysRegistered 2026-09-18\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nLicenced Casino\n\t500.casino\n5.9 yearsRegistered 2020-11-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette/Slots\n\tcsgobig.com\n11.4 yearsRegistered 2015-04-12\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcasedrop.com\n14.8 yearsRegistered 2011-12-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\tbanditcamp.com\n12.2 yearsRegistered 2014-06-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tskinbox.com\n18.8 yearsRegistered 2007-12-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\ttastydrop.com\n6.1 yearsRegistered 2020-08-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette Casino\n\tcsgopolygon.gg\n6.5 yearsRegistered 2020-03-28\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tmagicdrop.ru\n10.3 yearsRegistered 2016-05-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nDice Casino\n\tcsdice.com\n3.8 yearsRegistered 2022-11-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUpgrader Casino\n\tskinodds.com\n1.2 yearsRegistered 2025-06-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgowin.com\n12.0 yearsRegistered 2014-09-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrash Casino\n\tcsgorun.net\n7.3 yearsRegistered 2019-06-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\topenskins.com\n3.6 yearsRegistered 2023-02-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Gambling\n\trustbet.com\n7.6 yearsRegistered 2019-02-07\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgomagic.com\n9.4 yearsRegistered 2017-05-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUpgrader/Contract\n\tcsgobounty.com\n11.5 yearsRegistered 2015-03-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tezskins.com\n27.5 yearsRegistered 1999-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\trustcases.com\n7.2 yearsRegistered 2019-06-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgoreaper.com\n11.1 yearsRegistered 2015-08-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgocases.com\n12.3 yearsRegistered 2014-06-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Upgrader\n\tcsgo-skins.com\n11.2 yearsRegistered 2015-07-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgonet.com\n8.8 yearsRegistered 2017-12-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\twtfskins.com\n9.0 yearsRegistered 2017-10-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Casino\n\tflamecases.com\n10.0 yearsRegistered 2016-09-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tgamedom.com\n11.7 yearsRegistered 2015-01-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Battles\n\tskin.club\n9.0 yearsRegistered 2017-09-04\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsc-auth.net\n7.5 yearsRegistered 2019-04-02\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tdaddyskins.com\n9.9 yearsRegistered 2016-10-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Gambling\n\trustix.gg\n1.7 yearsRegistered 2025-01-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Upgrade\n\tskins.club\n4.2 yearsRegistered 2022-07-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgohouse.org\n146 daysRegistered 2026-04-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskinrave.net\n216 daysRegistered 2026-02-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tbloodycase.gg\n19 daysRegistered 2026-09-02\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nClicker/Upgrade\n\tcsgoclicker.com\n8.3 yearsRegistered 2018-05-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustbet.gg\n4.0 yearsRegistered 2022-09-30\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcs-drop.com\n262 daysRegistered 2026-01-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\thellstore.net\n11.7 yearsRegistered 2015-01-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustloot.com\n354 daysRegistered 2025-10-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgo-case.com\n10.3 yearsRegistered 2016-05-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgogem.com\n9.9 yearsRegistered 2016-10-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\trainbet.com\n8.8 yearsRegistered 2017-11-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nservices.rainbet.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustclash.com\n5.4 yearsRegistered 2021-05-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrash Casino\n\t12cs.fail\n181 daysRegistered 2026-03-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\twww.tf2easy.com\n6.3 yearsRegistered 2020-06-02\nRDAP ↗ · tf2easy.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2blaze.com\n7.6 yearsRegistered 2019-01-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tshuffle.com\n30.1 yearsRegistered 1996-07-31\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tbuff.market\n5.9 yearsRegistered 2020-10-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tavan.market\n8.3 yearsRegistered 2018-05-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Engine\n\tcs.money\n11.0 yearsRegistered 2015-09-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.dota.trade\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tuuskins.com\n2.6 yearsRegistered 2024-01-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Market\n\tyoupin898.com\n6.1 yearsRegistered 2020-08-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tc5game.com\n10.5 yearsRegistered 2016-03-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\twaxpeer.com\n7.3 yearsRegistered 2019-05-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwaxpeer.com\n7.3 yearsRegistered 2019-05-20\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBot Trading\n\tcs.money\n11.0 yearsRegistered 2015-09-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.dota.trade\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUS Marketplace\n\tdmarket.com\n30.2 yearsRegistered 1996-07-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nOfficial Market\n\tsteamcommunity.com/market\n20.3 yearsRegistered 2006-05-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNot an external login site2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Platform\n\tlootfarm.com\n11.9 yearsRegistered 2014-10-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Market\n\trustskins.com\n7.6 yearsRegistered 2019-01-31\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tkrakatoa.com\n26.4 yearsRegistered 2000-05-15\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\tshadowpay.com\n10.1 yearsRegistered 2016-08-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nChinese Powerhouse\n\tigxe.cn\n15.0 yearsRegistered 2011-09-06\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAutomated Swap\n\tswap.gg\n9.6 yearsRegistered 2017-01-29\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCash-out Portal\n\tbitskins.com\n11.2 yearsRegistered 2015-07-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Automation\n\ttf2mart.com\n1.1 yearsRegistered 2025-08-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Auctions\n\tskinbid.com\n10.2 yearsRegistered 2016-06-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Rental\n\tlootbear.com\n8.7 yearsRegistered 2018-01-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Valuation\n\tbackpack.tf\n14.4 yearsRegistered 2012-05-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Botnet\n\tstntrading.eu\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Cashout\n\tskinwallet.com\n18.0 yearsRegistered 2008-09-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nDota 2 Market\n\tdota2market.com\n12.2 yearsRegistered 2014-07-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nServer Network\n\txplay.gg\n5.3 yearsRegistered 2021-06-13\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMatchmaking Portal\n\tesportal.com\n26.8 yearsRegistered 1999-12-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nLATAM Hub\n\tgamersclub.com.br\n11.2 yearsRegistered 2015-06-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tools\n\tepidemic.gg\n4.9 yearsRegistered 2021-11-03\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tcs2stash.com\n3.5 yearsRegistered 2023-03-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tcsgoskins.gg\n6.8 yearsRegistered 2019-12-21\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tsteamanalyst.com\n12.6 yearsRegistered 2014-02-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Exchange\n\tsteamcardexchange.net\n13.3 yearsRegistered 2013-05-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tracker\n\tdotabuff.com\n14.2 yearsRegistered 2012-06-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tracker\n\ttracker.gg\n8.9 yearsRegistered 2017-10-12\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Exchange\n\tfunpay.com\n17.0 yearsRegistered 2009-09-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nGrey Market\n\tplayerauctions.com\n26.3 yearsRegistered 2000-06-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Portal\n\teldorado.gg\n8.0 yearsRegistered 2018-09-12\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Key Market\n\tg2a.com\n24.8 yearsRegistered 2001-12-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Key Market\n\tkinguin.net\n16.8 yearsRegistered 2009-12-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nVirtual Services\n\tg2g.com\n31.1 yearsRegistered 1995-08-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Broker\n\tplayerup.com\n19.3 yearsRegistered 2007-05-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfhub.net\n2.7 yearsRegistered 2023-12-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfaccounts.com\n5.3 yearsRegistered 2021-05-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Shop\n\tbuycsgorank.com\n6.2 yearsRegistered 2020-07-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tcsgosmurfkings.com\n9.3 yearsRegistered 2017-06-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfstore.co\n8.6 yearsRegistered 2018-03-03\nWHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlvlup.com\n9.9 yearsRegistered 2016-11-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlevels.com\n10.6 yearsRegistered 2016-02-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tlevelsteam.com\n79 daysRegistered 2026-07-04\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlevelu.com\n6.0 yearsRegistered 2020-09-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\teloking.com\n12.2 yearsRegistered 2014-07-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\tboosteria.org\n11.9 yearsRegistered 2014-10-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tovergear.com\n14.4 yearsRegistered 2012-04-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tblazingboost.com\n14.2 yearsRegistered 2012-06-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\tdota2boost.com\n2.9 yearsRegistered 2023-10-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tbuyboost.com\n22.4 yearsRegistered 2004-04-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\nArgumentacja przedstawiona w ramach dochodzeniaWybrana zasada / analiza i komentarz+\nCiężar dowodu\n\nW ramach dochodzenia analizowana jest rozbieżność między ograniczeniami dotyczącymi wykorzystania komercyjnego a usługami wymienionymi w niniejszym dokumencie. Należy sklasyfikować każdą działalność i ustalić, czy istnieje wyraźne zezwolenie, zanim uzna się ją za naruszenie umowy. Opłaty za korzystanie z Community Market nie mają zastosowania do wszystkich transakcji zewnętrznych.\n\nCzym jest rekord oznaczony, a czym nie jest\n\nRekord jest oznaczany, gdy w dokumentacji znajduje się opatrzona datą uwaga, która sprawia, że platforma podlega postanowieniom danej klauzuli na podstawie jej brzmienia. Oznaczenie to nie oznacza stwierdzonego naruszenia, a w odniesieniu do żadnej z wymienionych tutaj platform nie wydano wyraźnego zezwolenia Valve. W przypadku gdy platforma posiada zezwolenie, opublikowanie tej informacji powoduje usunięcie wpisu.\n\nŹródła i metodologiaSzacunki, definicje i zakres+\n\nPowyższe liczby odnoszą się do wybranej reguły. Typy rekordów grupują każdą platformę tylko raz; pełne tagi pojawiają się w szczegółach platformy. Wyszukiwanie i filtry działają w ramach tej reguły. Daty rejestracji pochodzą z zapisanego zrzutu ekranu RDAP / WHOIS. W przypadku subdomen stosowana jest data utworzenia domeny nadrzędnej. Sam wiek nie świadczy o ciągłości działania ani o trasie uwierzytelniania. Aktualne nazwy hostów uwierzytelniających pochodzą z zapisanych żądań OpenID wraz z sygnaturą czasową UTC; w przypadku nierozwiązanych sprawdzeń nie są ponownie wykorzystywane starsze etykiety. Obserwator zatrzymuje się przed logowaniem na stronie Steam i nie sprawdza statusu filtru linków Steam. Pobierz obserwacje trasy ↗ Pobierz wyniki rejestru ↗\n\nPrzejrzyj archiwum źródłowe ↗\nZałącznik G — Od wzoru odmowy do dokumentu źródłowego\nPodręcznik postępowania w sprawie DSAR: wniosek o udostępnienie dowodów\n\nW oparciu o art. 15 RODO można zwrócić się o udostępnienie danych osobowych związanych z utworzeniem klucza API, odzyskaniem konta oraz dostępem do pomocy technicznej. Zachowany zapis pozwala ustalić, kto zainicjował daną czynność oraz na jakich podstawach opierała się platforma.\n\n01\nZachowaj swoją oś czasu.\n\nZapisz powiadomienia dotyczące konta, bilety, identyfikatory transakcji oraz daty w czasie UTC. Zabezpiecz konto i zapoznaj się z opcjami odzyskiwania dostępnymi dla danej gry i transakcji.\n\nSteam Informacje dotyczące ochrony handlu ↗\n02\nPoproś o udostępnienie Twoich przechowywanych danych.\n\nPoproś o dane dotyczące znaczników czasu, adresów IP źródłowych, kluczowych zdarzeń związanych z cyklem życia kluczy, potwierdzeń bezpieczeństwa oraz działań związanych z odzyskiwaniem dostępu do konta. Uwzględnij zdarzenia związane z dostępem do pomocy technicznej oraz odbiorców, jeśli dane te dotyczą Ciebie.\n\n03\nZachowaj potwierdzenie dostawy.\n\nNależy skorzystać z kanału kontaktowego ds. ochrony prywatności Valve. Standardowy termin udzielenia odpowiedzi wynosi jeden miesiąc; w przypadku konieczności przedłużenia tego terminu o maksymalnie dwa kolejne miesiące należy przedstawić uzasadnienie w ciągu tego pierwszego miesiąca.\n\nValve ścieżka kontaktowa dotycząca prywatności ↗ zarchiwizowano 2026-09-21 ↗\n04\nPorównaj odpowiedzi.\n\nPorównaj zapisy z chronologią wydarzeń. Zapytaj o przyczyny pominięć, a następnie, jeśli to konieczne, skorzystaj z procedury składania skargi do organu nadzorczego. Zachowaj odpowiedź dokładnie w takiej postaci, w jakiej ją otrzymałeś.\n\nZakres stosowania / Artykuł 15\n\nDostęp obejmuje przechowywane dane osobowe, w tym dane zawarte w logach. Nie gwarantuje on dostępu do wszystkich dokumentów wewnętrznych, odtworzonych zapisów ani nieocenzurowanych danych dotyczących innych osób. Należy poprosić o czytelny odpis oraz o podanie podstawy ewentualnych ograniczeń.\n\nWytyczne EDPB dotyczące dostępu, §§ 2, 4–6 ↗ · Artykuły 12, 15 i 77 RODO ↗ zarchiwizowano 2026-09-20 ↗\n\nWniosek osoby, której dane dotyczą, o dostęp do danychRODO / Artykuł 15\nBezpieczeństwo konta i historia dostępu\n\nPrzed wysłaniem należy zastąpić pola w nawiasach.\n\nTo: Valve Privacy Team\nSubject: Article 15 GDPR request — account security records\n\nAccount / SteamID: [YOUR ACCOUNT IDENTIFIER]\nRelevant period (UTC): [START] to [END]\nRelated support tickets: [TICKET REFERENCES]\n\nI request a copy of the personal data concerning me that you retain for this period, including:\n\n1. API-key registration, confirmation, use and revocation events, with available timestamps, source IP addresses, registered domains, device or user-agent information and non-secret key identifiers.\n\n2. Recorded account-recovery actions, password/email/phone changes, Steam Guard removals or resets, confirmation events and the account-related evidence relied on to authorize those actions.\n\n3. Personal data in support-access and administrative-action logs concerning my account, including available dates, purposes, actions and the support entity involved, subject to applicable rights of others.\n\n4. Account-related records used to determine any sanction, and available records of my complaints, reviews and responses.\n\nPlease also provide the applicable processing purposes, categories, recipients, retention periods or criteria, and available information about sources where data were not obtained from me.\n\nWhere processing relies on my consent, please provide the retained record of the consent relied upon and the wording presented at that time.\n\nPlease provide an intelligible electronic copy with time zones and field definitions. Please do not include active credentials or secret tokens. If any requested data are not held, please say so. For any withheld data, please identify the scope and legal basis of the restriction and provide the remainder.\n\nPlease acknowledge receipt and respond within the applicable Article 12 period, explaining any necessary extension. I also ask you to preserve relevant existing records while this request is handled.\n\nName: [YOUR NAME]\nDate: [DATE]\nCo można osiągnąć dzięki adresowi IP centrum danych\nRozbieżność stanowi podstawę do wszczęcia dochodzenia.\n\nWniosek o klucz API pochodzący z sieci centrum danych, jak w przypadku dostawcy usług hostingowych poruszonym w niniejszym dochodzeniu, może mieć znaczenie w kontekście porównania z zapisami logowania, potwierdzeniami oraz historią aktywności użytkownika. Sam adres IP nie pozwala zidentyfikować sprawcy ani automatycznie obejść wszystkich zabezpieczeń. Dowód na to, że wrogie podmiot dostarczył zarejestrowaną zgodę, może podważyć możliwość powoływania się na tę zgodę; inne podstawy prawne i kwestie odpowiedzialności wymagają odrębnej analizy.\n\nZobacz zachowaną skargę dotyczącą zakazu i RODO →\nZałącznik H — Analiza archiwum serwisu Wayback Machine · opublikowane statystyki dotyczące wsparcia\nLiczba obsługiwanych spraw. Opublikowane czasy reakcji.\nOgraniczenia dotyczące kontekstu i źródła\n\nValve publikuje codzienne statystyki dotyczące pomocy technicznej pod adresem store.steampowered.com/stats/support. Archiwa serwisu Wayback Machine zawierają historyczne kopie tej strony z lat 2018–2026. Wynikający z tych danych stosunek liczby zgłoszeń do liczby pracowników jest niezgodny z ręczną weryfikacją każdego zgłoszenia w opublikowanych czasach reakcji.\n\nPorównaj zarchiwizowane dane dotyczące wsparcia użytkownika Valve w poszczególnych zapisanych migawkach. W opisie metodologii wyjaśniono, co te dane pozwalają zmierzyć, a czego nie.\n\nLiczba spraw w porównaniu z opublikowanym czasem reakcji (2018 → 2026)\nDwie kolejki w jednym punkcie obsługi klienta – na podstawie 21 zarchiwizowanych zrzutów ekranu.\n\nValve publikuje dane dotyczące pomocy na żywo na stronie store.steampowered.com/stats/support. Każdy z poniższych punktów to sama dolna granica Valve, która pojawiła się na tej stronie w dniu, w którym serwis Internet Archive wykonał jej zrzut — nie jest to nasze oszacowanie. Obie serie przedstawiają tę samą miarę w tej samej jednostce, więc powinny znajdować się na jednej osi i można je bezpośrednio porównywać ze sobą.\n\nWnioski o zwrot kosztów — pieniądze Valve są w posiadaniuBezpieczeństwo konta i odzyskiwanie dostępu — konto, które utraciłeś\n0 h\n2 h\n4 h\n6 h\n8 h\n10 h\nno captures · 38 months\n2019\n2020\n2021\n2022\n2023\n2024\n2025\n2026\n8 h 44 m\naccount recovery\n52 m\nrefunds\n15 m — one capture only\n49–55 minDolna granica zwrotu w każdym odczycie od lutego 2018 r. do sierpnia 2026 r. W ciągu ośmiu i pół roku zmienia się ona o mniej niż sześć minut, podczas gdy dzienny wolumen zwrotów zmienia się dziewięciokrotnie.\n2,4 godz. → 8,7 godz.Dolna granica czasu odzyskiwania konta wynosi około 2,4 godziny we wszystkich pomiarach do grudnia 2022 r., z wyjątkiem jednego. W trzech pomiarach z 2026 r. Valve podaje wartości 10,9 godz., 5,8 godz. i 8,7 godz.\n×2,8 → ×13O ile wolniej przebiega proces zwrotu środków w porównaniu z refundacjami – według danych opublikowanych przez samego Valve. Przez pięć lat sytuacja pozostaje stabilna, a potem różnica się powiększa — kolejka, w której proces przebiega wolniej, to ta, w której to użytkownik, a nie Valve, ponosi koszty.\n\nŹródło: 21 kopii archiwalnych z serwisu Wayback Machine store.steampowered.com/stats/support, od 2018-02-03 do 2026-08-10; ekstrakcja w VALVE_EVIDENCE_PACK/databases/steam_support_stats_history.json. Zapoznaj się z ograniczeniami przedstawionymi na wykresie: wykres przedstawia niższy granica przedziału Valve wyników. Opublikowana górna granica jest gorsza w obu przypadkach — zwroty trwały od 1,5 godziny do 1,5 dnia, a odzyskiwanie od 7,0 godzin do 3,6 dnia. Dwa zrzuty ekranu zostały zarchiwizowane w zlokalizowanej wersji tej samej strony Valve — 2018-11-03 w języku czeskim, 2020-03-25 w języku francuskim — i są oznaczone w tabeli jako (cs) oraz (fr); ich dane przedstawiono tutaj z przetłumaczonymi nazwami jednostek miary i liczbami zgodnymi z publikacją, a dosłowne ciągi źródłowe zachowano w pliku ekstrakcji. Każdy zrzut zawierał czas odpowiedzi dla obu kolejek, a żaden punkt na żadnej z linii nie został wyinterpolowany. Pojedyncza wartość czasu przywrócenia wynosząca 2020-10-21 dla 15 minut została zaznaczona na wykresie i pozostawiona: pojawia się ona tylko w jednym zrzucie, a żaden inny zrzut nie mieści się w jej rzędzie wielkości. Pomiędzy wartościami 2022-12-08 a 2026-02-01 nie ma żadnego zapisu; ta 38-miesięczna luka w danych jest zacieniona i nie narysowano na niej żadnej linii. Wartości te opisują opublikowane czasy reakcji. Nie pokazują one, co dzieje się w ramach konkretnego zgłoszenia, a Valve nie opublikowało danych dotyczących liczby pracowników, w odniesieniu do których można by je interpretować.\n\nOtwórz każde przechwycenie jako tabelę\nKażdy zarchiwizowany zrzut ekranu, w postaci opublikowanej\nPrzechwyć\tZwroty kosztów / dzień\tOdpowiedź w sprawie zwrotu kosztów\tPowrót do zdrowia / dzień\tDziałania naprawcze\n2018-02-03\t98,788\tod 50,12 minuty do 1,52 godziny\t25,662\tod 2,51 godziny do 1,80 dnia\n2018-05-07\t60,494\tod 53,83 minuty do 1,47 dnia\t24,226\tod 2,45 godziny do 2,22 dnia\n2018-08-02\t69,084\tod 50,27 minuty do 1,59 godziny\t28,953\tod 2,44 godziny do 22,17 godziny\n2018-11-03 (cs)\t63,410\tod 49,28 minuty do 1,54 godziny\t33,910\tod 2,42 godziny do 1,31 dnia\n2019-02-01\t76,305\tod 50,13 minuty do 1,52 godziny\t35,164\tod 2,44 godziny do 2,04 dnia\n2019-05-18\t78,951\tod 51,03 minuty do 3,12 godziny\t27,514\tOd 2,46 godziny do 20,39 godziny\n2019-09-07\t78,941\tod 50,65 minuty do 1,66 godziny\t28,812\tod 2,42 godziny do 13,59 godziny\n2019-12-13\t69,589\tod 50,77 minuty do 1,55 godziny\t25,322\tod 2,45 godziny do 1,13 dnia\n2020-03-25 (fr)\t139,278\tod 49,45 minuty do 1 godziny i 53 minut\t32,302\tod 2,48 godziny do 3,62 dnia\n2020-06-26\t278,504\tod 48,98 minuty do 2,29 godziny\t20,343\tod 2,39 godziny do 6,99 godziny\n2020-10-21\t107,633\tod 50,80 minuty do 1,54 godziny\t20,688\tod 15,33 minuty do 8,62 godziny\n2021-03-20\t158,956\tod 50,80 minuty do 1,64 godziny\t25,760\tod 2,34 godziny do 11,62 godziny\n2021-06-26\t547,907\tod 51,93 minuty do 6,73 godziny\t29,728\tOd 2,40 godziny do 15,63 godziny\n2021-10-10\t170,103\tod 51,88 minuty do 3,25 godziny\t23,989\tod 2,39 godziny do 13,05 godziny\n2022-01-31\t354,386\tod 53,65 minuty do 8,09 godziny\t24,391\tod 2,42 godziny do 15,29 godziny\n2022-05-09\t172,555\tod 51,83 minuty do 1,65 godziny\t23,289\tod 2,41 godziny do 16,90 godziny\n2022-09-05\t153,453\tod 53,67 minuty do 4 godzin i 15 minut\t23,594\tod 2,45 godziny do 1,22 dnia\n2022-12-08\t181,075\tod 54,83 minuty do 6,67 godziny\t27,111\tod 2,46 godziny do 18,89 godziny\n2026-02-01\t317,762\tod 50,30 minuty do 1,52 godziny\t47,197\tOd godz. 10.91 do godz. 21.30\n2026-05-09\t246,776\tod 50,12 minuty do 1,52 godziny\t35,264\tod 5,81 godziny do 15,60 godziny\n2026-08-10\t373,244\tod 52,05 minuty do 2,07 godziny\t45,319\tod 8,73 godziny do 16,52 godziny\nGŁÓWNA UWAGA:\nW poprzek 21 zrzutów ekranu z serwisu Wayback w przedziale od 2018-02-03 do 2026-08-10, dzienne wnioski o zwrot wynosiły od 60,494 (maj 2018 r.) do 547,907 (czerwiec 2021 r.) — a 9,1× spread. Wynik za rok 2026 wynosi 373,244 (+278% w porównaniu z danymi z lutego 2018 r.).\nW ciągu tych samych dziewięciu lat opublikowana dolna granica czasu reakcji na wniosek o zwrot nigdy nie spadła poniżej 49–55 minut zakres: całkowity czas trwania wynoszący mniej niż sześć minut, podczas gdy obciążenie, które za tym stało, wzrosło dziewięciokrotnie.\nGdyby ktoś poświęcał na przeczytanie każdego biletu choćby 5 sekund, przetworzenie 373,244 biletów dziennie (obecnie) zajęłoby 22 agenci pracujący przez całą dobę, 7 dni w tygodniu tylko po to, by je otwierać i zamykać; w szczytowym momencie (547,907, czerwiec 2021 r.) liczba ta wzrasta do 32.\nGdyby opublikowany czas reakcji odzwierciedlał czas obsługi pojedynczego zgłoszenia (~52 min/zgłoszenie), to wynikająca z tego liczba pracowników pracujących jednocześnie wynosiłaby rzędu 13,500 agentów przy obecnej wielkości i ~20,000 w szczytowym momencie. Nie znaleziono żadnych danych dotyczących liczby pracowników wspierających Valve; w niniejszym opracowaniu nie przyjęto żadnych założeń w tej kwestii.\nCo z tego wynika: stosunek liczby spraw do liczby pracowników nie pozwala na przeprowadzenie weryfikacji przez człowieka każdej sprawy przy podanych czasach reakcji. Dane te wskazują na w dużej mierze zautomatyzowaną pierwszą fazę rozpatrywania spraw; nie podano jednak, jaki odsetek spraw podlega weryfikacji przez człowieka.\nDlaczego ma to znaczenie dla zgodności z RODO\n\nArtykuł 22 RODO zabrania podejmowania wyłącznie zautomatyzowanych decyzji dotyczących poszczególnych osób, które pociągają za sobą istotne skutki prawne, bez zapewnienia prawa do weryfikacji przez człowieka na żądanie. Jeśli decyzje dotyczące wsparcia (zamknięcie zgłoszeń, działania związane z kontem, odmowa spełnienia wniosków o udostępnienie danych) są podejmowane wyłącznie przez zautomatyzowane skrypty, każda taka decyzja, która „w znaczący sposób wpływa” na użytkownika, może stanowić naruszenie art. 22.\n\nBilet HT-2YBP-F7JP-D4VB (Sekcja 18) została zamknięta po trzech dniach z odesłaniem do szablonu i bez odniesienia do przytoczonej podstawy prawnej. Na podstawie zgłoszenia nie można ustalić, czy ktoś je przejrzał; jest to pytanie, które organ nadzorczy może skierować do Valve na podstawie art. 22 oraz art. 15 ust. 1 lit. h).\n\nŹródło: kopie zapasowe serwisu store.steampowered.com/stats/support utworzone przez Wayback Machine (2018-02-03, 2021-06-26, 2026-08-10) — dane wyodrębnione do pliku VALVE_EVIDENCE_PACK/databases/steam_support_stats_history.json (21 zrzutów, 2018–2026). Uwaga: czas odpowiedzi „~52 min” stanowi dolną granicę dla kategorii zwrotów; czas odpowiedzi w zakresie bezpieczeństwa konta wynosił 2,4–16,5 godz. w tych samych zrzutach. 2021-06-26 to historyczny szczyt (547,907 wniosków o zwrot), a nie monotoniczny punkt środkowy — liczba wniosków wzrosła około 6-krotnie w latach 2020–2021, po czym częściowo spadła, by w 2026 r. powrócić do poziomu 373 tys.\nZałącznik I — Zakres zbioru danych · wyniki, które można odtworzyć\nPolicz rekordy. Sprawdź zakres.\nOgraniczenia dotyczące kontekstu i źródła\n\nNależy policzyć rekordy, a następnie zweryfikować podane dane: każdą z poniższych liczb można ponownie obliczyć na podstawie opublikowanych plików.\n\nNależy przeanalizować bazowe zbiory danych, odtworzyć wyniki liczenia oraz odróżnić wiersze źródłowe od pojedynczych zdarzeń.\n\nPlik CSV główny zawiera 40,448 wierszy. Spośród nich, 36,516 pochodzą z kanału Discord-AntiScam poświęconego phishingowi. Pozostałe 3,932 Zawiera informacje z serwisu GitHub, recenzje, wyniki wyszukiwania, materiały z forum oraz inne źródła, tworząc kompleksowy indeks zgłoszonych tematów poruszanych przez społeczność oraz raportów dotyczących bezpieczeństwa.\n\nW tym pliku CSV 1,690 wierszy zostało zaklasyfikowanych pod etykietą zbioru „Unpatched Security Exploit” (niezałatane luki w zabezpieczeniach), co odnosi się do historycznych zgłoszeń użytkowników i ujawnionych luk w zabezpieczeniach. Śledzenie tych zgłoszeń wymaga przeanalizowania konkretnej osi czasu kompilacji oraz publicznej historii poprawek dla każdego wątku.\n\nArchiwum z możliwością wyszukiwania zawierające 16,319 rekordów stanowi odrębną, wyselekcjonowaną kompilację z własnym manifestem, przeznaczoną do precyzyjnego lokalnego przeglądania konkretnych zgłoszeń użytkowników i raportów o incydentach.\n\nAby stworzyć wiarygodną ścieżkę audytu, każdy zgłoszony przez użytkownika wpis musi zostać zweryfikowany w oparciu o udokumentowane harmonogramy kompilacji oraz historyczne dzienniki poprawek.\n\nOddzielne rekordy zbioru z części II 231,829 unikalne identyfikatory ofert, w tym 33,509 w kategorii automatycznej rejestracji oraz 198,320 oznaczone jako niezweryfikowane transfery. Wartość SHA-256 pliku wejściowego jest zgodna z zachowanym pomiarem. Liczby te opisują próby wystawienia ofert i zaobserwowane transfery, a nie ostateczne wartości transakcji ani zweryfikowane sumy kradzieży, co podkreśla potrzebę wykorzystania pierwotnych zapisów platformy do pomiaru dokładnego wpływu ekonomicznego. Wykaz wymiarów i skrótów ↗\n\nOpanuj CSV ↗ · Indeks archiwum z funkcją wyszukiwania ↗ · Sprawdź rekordy źródłowe ↗\n\nZałącznik J — Informacje o niniejszym dochodzeniu\nValve nie opublikowało żadnych danych dotyczących egzekwowania przepisów. Zbudowaliśmy taki.\n\nNiezależny. Niekomercyjny. Opracowany wyłącznie na podstawie danych publicznych. Przedłożony organom regulacyjnym.\n\n88.97%flota automatyzacji pozostaje nienaruszona — nie wprowadzono żadnego zakazu\n67.77%z 51,732 oszustów, wobec których zapadły wyroki, pozostaje na wolności\n$26.8M+minimalna kwota wydatków w sklepie dla floty nieobjętej limitami\n3.6%domeny związane z hazardem zablokowane przez filtr linków użytkownika Valve\n8 latzarejestrowanych incydentów związanych z bezpieczeństwem\n\nCzym to jest. Raport kryminalistyczny dotyczący platformy Steam firmy Valve Corporation — jej historii egzekwowania przepisów, ekonomii opartej na „card-farmingu”, ram prawnych oraz infrastruktury uwierzytelniania, z której korzystają operatorzy gier hazardowych za pośrednictwem własnego serwera OpenID firmy Steam. Każda wartość można odtworzyć na podstawie dwóch źródeł: publicznego interfejsu API firmy Valve oraz zbiorów danych opublikowanych wraz z niniejszym dochodzeniem.\n\nDla kogo jest przeznaczony. Organy regulacyjne właściwe w sprawach dotyczących Valve — organ nadzorczy ds. RODO w Niderlandach, FinCEN, SEC, koordynator ds. usług cyfrowych w ramach DSA, UOKiK oraz wszelkie organy ścigania badające przepływy finansowe powiązane z Steam. Również dla dziennikarzy, badaczy i wszystkich użytkowników, którzy zostali na stałe zablokowani na koncie, którym odmówiono zwrotu środków lub którym skradziono zasoby, a którym powiedziano, że nie ma możliwości odwołania.\n\nJedyne żądanie. Valve przechowuje te dane z zachowaniem pełnej dokładności — wraz z podanymi powodami blokady, pełną przestrzenią identyfikacyjną i w czasie rzeczywistym. Jest w stanie przetworzyć każde zapytanie zawarte w tej dokumentacji w ciągu kilku sekund i zdecydowało się nie publikować żadnej z tych informacji. Pytanie skierowane do każdego właściwego organu jest proste: a dlaczego nie?\n\nCzego autorzy nie twierdzą. W trakcie tych prac nie dokonano żadnego logowania do Steam na żadnej platformie zewnętrznej. Podany adres URL OpenID określa parametry żądania, a nie fakt zakończonego logowania. Posiadanie oddzielnej domeny podlegającej rejestracji nie stanowi samo w sobie dowodu na obejście zasad. Daty rejestracji stanowią dolną granicę czasu, w którym host mógł po raz pierwszy pojawić się w żądaniu OpenID; nie świadczą one o ciągłym użytkowaniu. Autorzy nie twierdzą, co wiedział lub zamierzał Valve: każde stwierdzenie dotyczące Valve jest powiązane z datowanym dokumentem publicznym lub datowaną obserwacją. Tam, gdzie twierdzenia nie można było poprzeć dokumentem źródłowym, zostały one usunięte.\n\nKim jesteśmy\n\nPhishDestroy — niezależni badacze. Nie jesteśmy powiązani z korporacją Valve ani żadną z wymienionych tu platform. Jedno konto Steam zostało wykorzystane wyłącznie w celu udokumentowania wniosku złożonego na podstawie RODO, o którym mowa w sekcji 18.\n\nInformacja prawna\n\nNiekomercyjne, zdecentralizowane dochodzenie w interesie publicznym. Wszystkie dane udostępniane są „tak jak są”, bez żadnych gwarancji. Niniejsza publikacja nie stanowi orzeczenia sądowego.\n\nDOMENA PUBLICZNA\nLicencjonowanie\n\nWszelkie prawa przekazano ludzkości. Można powielać, adaptować i publikować — podanie źródła nie jest wymagane. Dostęp z regionów objętych sankcjami OFAC: zabroniony. Pełna licencja i zastrzeżenia prawne →",
        "headings": [
          {
            "level": 2,
            "id": "briefing-heading",
            "text": "Zasada. Rekord. Pytania bez odpowiedzi."
          },
          {
            "level": 2,
            "id": null,
            "text": "List otwarty do Komisji ds. Hazardu stanu Waszyngton"
          },
          {
            "level": 3,
            "id": "wsgc-public-address-title",
            "text": "Dziesięć dni zamieniło się w dziesięć lat.Otwórz ponownie rekord."
          },
          {
            "level": 2,
            "id": null,
            "text": "Strona jest zablokowana. Trasa logowania nie jest zablokowana."
          },
          {
            "level": 3,
            "id": null,
            "text": "Rysunek 3.1 — Dwie trasy na mapie."
          },
          {
            "level": 3,
            "id": null,
            "text": "Pułapka „szerszej perspektywy”: Filtr Link to tylko pozory zgodności z przepisami, a nie prawdziwa ochrona"
          },
          {
            "level": 3,
            "id": null,
            "text": "Zablokowana domena główna w połączeniu z odblokowanym hostem uwierzytelniającym sprawia, że trasa logowania pozostaje otwarta — i pozostaje otwarta przez lata."
          },
          {
            "level": 3,
            "id": null,
            "text": "Kontekst: Czym jest Steam i dlaczego ma to tutaj znaczenie"
          },
          {
            "level": 3,
            "id": null,
            "text": "Co zrobił Valve: Blokada domeny"
          },
          {
            "level": 3,
            "id": null,
            "text": "Czym jest domena proxy"
          },
          {
            "level": 3,
            "id": null,
            "text": "Kluczowy moment: w każdym żądaniu adres hosta uwierzytelniającego jest wysyłany do Steam"
          },
          {
            "level": 3,
            "id": null,
            "text": "Co to dowodzi"
          },
          {
            "level": 3,
            "id": null,
            "text": "Wewnątrz Steam jedyną listą jest lista Valve."
          },
          {
            "level": 3,
            "id": null,
            "text": "Ominięcie zabezpieczenia filtra łącza"
          },
          {
            "level": 3,
            "id": null,
            "text": "Przeglądarka internetowa Big Picture ujawnia pliki cookie związane z logowaniem oraz poufne informacje (może to prowadzić do przejęcia konta)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Co to oznacza dla nieletniego, który ma zainstalowany program antywirusowy"
          },
          {
            "level": 3,
            "id": null,
            "text": "Wiek domeny.Data obserwacji."
          },
          {
            "level": 2,
            "id": null,
            "text": "Zakończono działanie punktu końcowego. W publicznym śledzeniu utracono klucz."
          },
          {
            "level": 3,
            "id": null,
            "text": "Okres przed awarią zasilania"
          },
          {
            "level": 3,
            "id": null,
            "text": "Po wprowadzeniu zmiany"
          },
          {
            "level": 2,
            "id": null,
            "text": "Jedna sesja. Szerszy dostęp niż ten, który widzi użytkownik."
          },
          {
            "level": 3,
            "id": null,
            "text": "1. Niewystarczające uwierzytelnianie wielopoziomowe"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. Brak zasady minimalnych uprawnień"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. Nieprawidłowe zarządzanie sesjami"
          },
          {
            "level": 3,
            "id": null,
            "text": "4. Blokowanie hostów uwierzytelniających na poziomie domeny było technicznie wykonalne"
          },
          {
            "level": 3,
            "id": "integration-paradox-title",
            "text": "Valve codziennie kompiluje się zgodnie z tymi regułami. W tym przypadku kompilacja nie przebiegła zgodnie z nimi."
          },
          {
            "level": 4,
            "id": null,
            "text": "Szczegółowe zakresy w GitHubie a Valve Steam Web API"
          },
          {
            "level": 2,
            "id": null,
            "text": "Interaktywny symulator ataków i przejęcia kontroli"
          },
          {
            "level": 2,
            "id": null,
            "text": "Punkty końcowe, które stanowią podstawę tej sekwencji."
          },
          {
            "level": 2,
            "id": null,
            "text": "Zaznaczone pole wyboru. Czyja czynność?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Jak Valve ostatecznie zneutralizowało „substytucję handlową” — i dlaczego zajęło to 7 lat stosowania rozwiązań obejściowych"
          },
          {
            "level": 4,
            "id": null,
            "text": "Czas odnowienia awatara i nazwy (luty 2024 r.)"
          },
          {
            "level": 4,
            "id": null,
            "text": "7-dniowe odwrócenie trendu w CS2 (lipiec 2025 r.)"
          },
          {
            "level": 4,
            "id": null,
            "text": "Obowiązkowe powiadomienia push w aplikacjach mobilnych dla API (grudzień 2023 r.)"
          },
          {
            "level": 4,
            "id": null,
            "text": "Banery z nazwą i stażem konta (2022–2024)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Ich regulamin. Zarejestrowane platformy."
          },
          {
            "level": 3,
            "id": "enforcement-focus-title",
            "text": "Jeden zbiór przepisów. Nierówne ich egzekwowanie."
          },
          {
            "level": 4,
            "id": null,
            "text": "Automatyzacja"
          },
          {
            "level": 4,
            "id": null,
            "text": "Wykorzystanie komercyjne"
          },
          {
            "level": 4,
            "id": null,
            "text": "VPN i ukrywanie lokalizacji"
          },
          {
            "level": 4,
            "id": null,
            "text": "Zaszyfrowanie linków"
          },
          {
            "level": 4,
            "id": null,
            "text": "Kto dokonuje weryfikacji decyzji po zamknięciu sprawy przez dział wsparcia?"
          },
          {
            "level": 2,
            "id": null,
            "text": "Interfejs API do automatyzacji. Zasada zakazująca automatyzacji."
          },
          {
            "level": 3,
            "id": null,
            "text": "Błędne przekonanie dotyczące „twórców gier”"
          },
          {
            "level": 4,
            "id": null,
            "text": "Sprzeczność automatyzacji"
          },
          {
            "level": 4,
            "id": null,
            "text": "Rola serwera w procesie transakcyjnym"
          },
          {
            "level": 2,
            "id": null,
            "text": "Wymagano dziesięciu dni. Trzeba było rozliczyć się z dziesięciu lat."
          },
          {
            "level": 3,
            "id": "letter-company",
            "text": "VALVE CORPORATION"
          },
          {
            "level": 3,
            "id": null,
            "text": "Dziesięć dni.No to co dalej?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Postępuj zgodnie z podanym serwerem docelowym."
          },
          {
            "level": 3,
            "id": "washington-record-heading",
            "text": "Dwa terminy. Jedna nieokreślona norma egzekucyjna."
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve przyznaje serwisom hazardowym 10 dni"
          },
          {
            "level": 4,
            "id": null,
            "text": "Waszyngton naciska Valve"
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve odrzuca zarzut"
          },
          {
            "level": 4,
            "id": null,
            "text": "Trasy zaobserwowane we wrześniu 2026 roku"
          },
          {
            "level": 4,
            "id": null,
            "text": "Osiemnaście miesięcy po udzieleniu odpowiedzi przez Valve organ regulacyjny nadal określał to jako zamiar."
          },
          {
            "level": 3,
            "id": null,
            "text": "Dekada „10-dniowego zawiadomienia”: kryminalistyczny audyt gotowości 23 wskazanych obiektów"
          },
          {
            "level": 4,
            "id": null,
            "text": "Od 10-dniowych ostrzeżeń po zagraniczne konglomeraty: obroty rzędu wielu miliardów dolarów"
          },
          {
            "level": 2,
            "id": null,
            "text": "Nazwa hosta jest już zawarta w żądaniu."
          },
          {
            "level": 3,
            "id": null,
            "text": "Udokumentowane i zgłoszone przypadki"
          },
          {
            "level": 3,
            "id": null,
            "text": "Co wynika z daty rejestracji, a czego z niej nie wynika"
          },
          {
            "level": 3,
            "id": null,
            "text": "Audyt porównawczy: standardy zgodności z API"
          },
          {
            "level": 2,
            "id": "market-thesis-heading",
            "text": "Różnica cenowa w stosunku do 0"
          },
          {
            "level": 2,
            "id": null,
            "text": "Różnica w cenie jest wymierna."
          },
          {
            "level": 3,
            "id": null,
            "text": "Co pokazuje ta kwota w dolarach"
          },
          {
            "level": 3,
            "id": null,
            "text": "Wiele obiektów podaje wartość wyższą niż Steam."
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam nadal przoduje pod względem liczby ofert."
          },
          {
            "level": 3,
            "id": null,
            "text": "Ekosystem biznesowy jest jak na dłoni."
          },
          {
            "level": 2,
            "id": null,
            "text": "Kto może zresetować zabezpieczenia?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Kod odzyskiwania, który wyłączył zabezpieczenia konta, oraz zgłoszona strata w wysokości $10,000"
          },
          {
            "level": 3,
            "id": null,
            "text": "Więcej niż tylko asortyment."
          },
          {
            "level": 3,
            "id": "theft-ledger-title",
            "text": "Valve otworzył drzwi dwukrotnie, w odstępie trzydziestu trzech miesięcy. Drzwi nigdy się nie zamknęły."
          },
          {
            "level": 4,
            "id": null,
            "text": "To, co wynika z księgi, a czego nie pokazuje żaden pojedynczy przypadek."
          },
          {
            "level": 3,
            "id": null,
            "text": "Poufność musi iść w parze z odpowiedzialnością techniczną."
          },
          {
            "level": 2,
            "id": null,
            "text": "Podążaj za pieniędzmi. Rozdziel transakcje."
          },
          {
            "level": 3,
            "id": null,
            "text": "Gdzie faktycznie przepływają pieniądze."
          },
          {
            "level": 3,
            "id": null,
            "text": "Najpierw sklasyfikuj czynność, a potem obowiązek."
          },
          {
            "level": 3,
            "id": null,
            "text": "Śledź przebieg działań, zdobywaj wiedzę i korzystaj z pomocy."
          },
          {
            "level": 2,
            "id": null,
            "text": "Ustawa o usługach cyfrowych: należy odnotować tę informację"
          },
          {
            "level": 3,
            "id": null,
            "text": "Dziesięciodniowe wezwanie."
          },
          {
            "level": 3,
            "id": null,
            "text": "Okno czasowe DSA."
          },
          {
            "level": 3,
            "id": null,
            "text": "Czas trwania wymaga ścieżki powiadomień."
          },
          {
            "level": 3,
            "id": null,
            "text": "rocznego obrotu na całym świecie"
          },
          {
            "level": 2,
            "id": null,
            "text": "Osoby niepełnoletnie: logowanie za pomocą kodu „Steam” nie stanowi weryfikacji wieku"
          },
          {
            "level": 3,
            "id": null,
            "text": "Określ operator i dane."
          },
          {
            "level": 3,
            "id": null,
            "text": "Zapisz przebieg procesu od zalogowania się do dokonania wpłaty."
          },
          {
            "level": 2,
            "id": null,
            "text": "Prośba. Odpowiedź. Brakujące porównanie."
          },
          {
            "level": 3,
            "id": null,
            "text": "Dokumenty istnieją; osoba, której dane dotyczą, ich nie otrzymała."
          },
          {
            "level": 2,
            "id": null,
            "text": "Umowa abonamentowa niezgodna z architekturą platformy"
          },
          {
            "level": 3,
            "id": null,
            "text": "Limit rynkowy i zakaz wykorzystywania do celów komercyjnych"
          },
          {
            "level": 3,
            "id": null,
            "text": "Luka w zabezpieczeniach klucza API jako kwestia związana z projektem platformy, a nie z niedbalstwem użytkownika"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve pobiera nazwę hosta uwierzytelniającego przy każdym logowaniu"
          },
          {
            "level": 3,
            "id": null,
            "text": "Wzorzec występujący w zarchiwizowanych skargach"
          },
          {
            "level": 3,
            "id": null,
            "text": "Sąd rozpatrujący tę sprawę nie interpretowałby ustawy o ubezpieczeniach społecznych (SSA) w oderwaniu od pozostałych okoliczności."
          },
          {
            "level": 2,
            "id": null,
            "text": "Wyniki. Dokumenty, o które prosimy."
          },
          {
            "level": 2,
            "id": null,
            "text": "Memorandum dowodowe — materiały przekazane przez Źródło 1"
          },
          {
            "level": 2,
            "id": null,
            "text": "Zmiany w dostarczonym pliku PDF mają charakter kosmetyczny: zakryty tekst nadal można wyodrębnić"
          },
          {
            "level": 2,
            "id": null,
            "text": "Dokumentacja dotycząca wsparcia i korespondencji prawnej"
          },
          {
            "level": 2,
            "id": null,
            "text": "Wybrane dokumenty źródłowe"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-01",
            "text": "Klucze sprzętowe, zamówione w 2016 r."
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-02",
            "text": "Raporty o awariach bez skutecznej możliwości rezygnacji"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-03",
            "text": "Zgłoszono nadużycie biletu uwierzytelniającego do Valve"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-01",
            "text": "44 sporne transakcje zakupu na rynku"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-02",
            "text": "Trwały zakaz i zamknięta procedura odwoławcza"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-03",
            "text": "Zresetowanie procesu odzyskiwania i zgłoszona strata wynosząca $10,000"
          },
          {
            "level": 2,
            "id": null,
            "text": "ArchiSteamFarm oraz klauzula dotycząca automatyzacji"
          },
          {
            "level": 2,
            "id": null,
            "text": "Rules ledger: clauses against recorded platforms"
          },
          {
            "level": 3,
            "id": "ledger-title",
            "text": "Wykorzystanie komercyjne i naliczanie opłat za konto"
          },
          {
            "level": 3,
            "id": "lw-register-title",
            "text": "Rejestr platformy 175"
          },
          {
            "level": 4,
            "id": null,
            "text": "Ciężar dowodu"
          },
          {
            "level": 4,
            "id": null,
            "text": "Czym jest rekord oznaczony, a czym nie jest"
          },
          {
            "level": 2,
            "id": null,
            "text": "Podręcznik postępowania w sprawie DSAR: wniosek o udostępnienie dowodów"
          },
          {
            "level": 3,
            "id": null,
            "text": "Zachowaj swoją oś czasu."
          },
          {
            "level": 3,
            "id": null,
            "text": "Poproś o udostępnienie Twoich przechowywanych danych."
          },
          {
            "level": 3,
            "id": null,
            "text": "Zachowaj potwierdzenie dostawy."
          },
          {
            "level": 3,
            "id": null,
            "text": "Porównaj odpowiedzi."
          },
          {
            "level": 3,
            "id": null,
            "text": "Bezpieczeństwo konta i historia dostępu"
          },
          {
            "level": 3,
            "id": null,
            "text": "Rozbieżność stanowi podstawę do wszczęcia dochodzenia."
          },
          {
            "level": 2,
            "id": null,
            "text": "Liczba obsługiwanych spraw. Opublikowane czasy reakcji."
          },
          {
            "level": 3,
            "id": null,
            "text": "Dwie kolejki w jednym punkcie obsługi klienta – na podstawie 21 zarchiwizowanych zrzutów ekranu."
          },
          {
            "level": 2,
            "id": null,
            "text": "Policz rekordy. Sprawdź zakres."
          },
          {
            "level": 2,
            "id": null,
            "text": "Valve nie opublikowało żadnych danych dotyczących egzekwowania przepisów.\nZbudowaliśmy taki."
          }
        ],
        "links": [
          "https://dotesports.com/counter-strike/news/csgo-lounge-billion-bets-3896",
          "https://store.steampowered.com/agreement/?l=english",
          "http://web.archive.org/web/20260921022032/https://store.steampowered.com/agreement/?l=english",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-all-results.json",
          "https://blog.counter-strike.net/expresstrade/",
          "http://web.archive.org/web/20260307161538/https://blog.counter-strike.net/expresstrade/",
          "https://wsgc.wa.gov/news/2016/washington-state-gambling-commission-orders-valve-stop-skins-gambling",
          "http://web.archive.org/web/20260520012601/https://wsgc.wa.gov/news/2016/washington-state-gambling-commission-orders-valve-stop-skins-gambling",
          "https://fr.scribd.com/document/328063293/Valve-s-Oct-18th-response-to-Washington-State-Gambling-Commission-s-cease-and-desist",
          "https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921021947/https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921022628/https://steamcommunity.com/linkfilter/?url=https:%2F%2Frollbit.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rbsnin.com.20260921T021120Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rollbit.com.json",
          "http://web.archive.org/web/20260921022740/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fskin.club",
          "http://web.archive.org/web/20260921022842/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fsc-auth.net",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skin.club.json",
          "http://web.archive.org/web/20260921022603/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fhowl.gg",
          "http://web.archive.org/web/20260921022636/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fhowl.uno",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/howl.gg.json",
          "http://web.archive.org/web/20260921022840/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fduelbits.com",
          "http://web.archive.org/web/20260921022901/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fswitchflips.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/duelbits.com.json",
          "http://web.archive.org/web/20260921022758/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgofast.com",
          "http://web.archive.org/web/20260921022847/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fauthtofast.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgofast.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/farmskins.com.20260921T025840Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/steam.kobal.cc.20260921T025844Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/farmskins.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cobaltlab.tech.20260921T041604Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cobaltauth.com.20260921T041608Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/cobaltlab.tech.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgo.net.20260921T041619Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cn2.easylot.net.20260921T041623Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgo.net.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/ggdrop.com.20260921T041637Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/ggauth.com.20260921T041641Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/ggdrop.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rustchance.com.20260921T041703Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/hgfuihd.com.20260921T041706Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rustchance.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skin.fans.20260921T041710Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.skinfans.com.20260921T041713Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skin.fans.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinport.com.20260921T041724Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinport.app.20260921T041728Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skinport.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skins.cash.20260921T041731Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinscash.live.20260921T041735Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skins.cash.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2hunt.com.20260921T041739Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rstspcl.com.20260921T041742Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tf2hunt.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgogem.com.20260922T192355Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/api.csgem.com.20260922T192358Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-2026-09-22.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/gamdom.com.20260922T192326Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/login.gambldom.com.20260922T192330Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/12cs.fail.20260922T192347Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/fail.games.20260922T192351Z.html",
          "http://web.archive.org/web/20260921022953/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgoempire.com",
          "http://web.archive.org/web/20260921022947/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgoempirelogin4.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgoempire.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cs.money.20260921T021131Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.dota.trade.20260921T021134Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/cs.money.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csfloat.com.20260921T041612Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgofloat.com.20260921T041615Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csfloat.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/g4skins.com.20260921T041630Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.g4s.to.20260921T041634Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/g4skins.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/juice.gg.20260921T041644Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/letmeinjuice.com.20260921T041648Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/juice.gg.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/market.csgo.com.20260921T041652Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2.net.20260921T041655Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/market.csgo.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rust.tm.20260921T041659Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rust.tm.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgolounge.com.20260922T192333Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2.net.20260922T192340Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2lounge.com.20260922T192337Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinbaron.de.20260921T041717Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinbaron.com.20260921T041721Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skinbaron.de.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2royal.com.20260921T041746Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2auth.com.20260921T041750Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tf2royal.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tradeit.gg.20260921T041753Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/connect-tradeit.com.20260921T041757Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tradeit.gg.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/upgrader.pro.20260921T041801Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/upgauth.space.20260921T041804Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/upgrader.pro.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-recheck-2026-09-21.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/domain-registration.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wayback-snapshots.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-2026-09-22c.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/master_registry.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/longitudinal-steam-phishing-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-steam-phishing-100.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-coverage-2026-09-22.json",
          "https://blog.csfloat.com/how-floatdb-tracks-items/",
          "http://web.archive.org/web/20260921022415/https://blog.csfloat.com/how-floatdb-tracks-items/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/platform-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/platforms-removed.json",
          "https://hackerone.com/reports/291750",
          "http://web.archive.org/web/20251116185046/https://hackerone.com/reports/291750",
          "https://hackerone.com/reports/1079561",
          "http://web.archive.org/web/20260924181830/https://hackerone.com/reports/1079561",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/hackerone-reports.json",
          "https://phishdestroy.io/steam_dossier/pl/steam_enforcement_evidence.html#support-records",
          "https://www.darknavy.org/blog/exploiting_steam_usual_and_unusual_ways_in_the_cef_framework/",
          "https://steamcommunity.com/groups/SteamClientBeta/discussions/0/3365901765276206401/",
          "http://web.archive.org/web/20250804051514/https://steamcommunity.com/groups/SteamClientBeta/discussions/0/3365901765276206401/",
          "https://www.chromium.org/developers/design-documents/safebrowsing/",
          "http://web.archive.org/web/20260821101616/https://www.chromium.org/developers/design-documents/safebrowsing/",
          "https://www.chromium.org/developers/how-tos/api-keys/",
          "http://web.archive.org/web/20260830122831/https://www.chromium.org/developers/how-tos/api-keys/",
          "https://github.com/Homebrew/homebrew-cask/issues/193814",
          "https://testsafebrowsing.appspot.com/",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/domain-registration.json",
          "https://phishdestroy.io/steam_dossier/pl/AUTH_AUDIT.md",
          "https://datatracker.ietf.org/doc/rfc6749/",
          "https://docs.cloud.google.com/docs/authentication/api-keys",
          "https://listings.pcisecuritystandards.org/pdfs/PCI_DSS_Resource_Guide_(003).pdf",
          "https://developer.apple.com/news/?id=02202019a",
          "http://web.archive.org/web/20250506070026/https://developer.apple.com/news/?id=02202019a",
          "https://dev.twitch.tv/docs/authentication/validate-tokens/",
          "https://discuss.dev.twitch.com/t/legacy-twitch-api-v5-i-e-kraken-shutdown-reminder-february-28-2022/36589",
          "http://web.archive.org/web/20250127085635/https://discuss.dev.twitch.com/t/legacy-twitch-api-v5-i-e-kraken-shutdown-reminder-february-28-2022/36589",
          "https://store.steampowered.com/news/posts/?enddate=1788390000",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/4123547285514022851",
          "https://skinvault.gg/blog/cs2-trade-protection-explained/",
          "https://csmarketcap.com/blog/market-insights/from-boom-to-bust-cs2s-trade-protection-impact",
          "https://skin.land/blog/steam-changes-cs2-trade-ban-logic-timing/",
          "https://help.steampowered.com/faqs/view/3041-A87A-E5F6-B6AC",
          "https://steamcommunity.com/ogg/593110/announcements/detail/533224478739530146",
          "https://steamcommunity.com/games/CSGO/announcements/detail/4447966961421256740",
          "https://steamcommunity.com/sharedfiles/filedetails/?id=2926756889",
          "https://steamcommunity.com/dev/apikey",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3734103130194459461",
          "https://steamcommunity.com/discussions/forum/1/3807266184852932971/",
          "https://help.steampowered.com/faqs/view/225C-C51E-B8F0-55B2",
          "https://store.steampowered.com/news/group/4/view/3314112260640237775",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/issues/325",
          "https://blog.dota2.com/2020/05/trading-cooldown/",
          "https://blog.counter-strike.net/index.php/2018/03/20308/",
          "http://web.archive.org/web/20250226114333/https://blog.counter-strike.net/index.php/2018/03/20308/",
          "https://phishdestroy.io/steam_dossier/pl/steam_evidence_archive.html",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/493839547938902179",
          "https://store.steampowered.com/online_conduct",
          "http://web.archive.org/web/20260921022120/https://store.steampowered.com/online_conduct",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260918014700/https://store.steampowered.com/subscriber_agreement/",
          "https://steamcommunity.com/dev/apiterms",
          "http://web.archive.org/web/20260921022210/https://steamcommunity.com/dev/apiterms",
          "https://help.steampowered.com/en/faqs/view/628C-E332-BD8C-4D36",
          "https://phishdestroy.io/steam_dossier/pl/social_graph.html",
          "https://phishdestroy.io/steam_dossier/pl/security_timeline.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wsgc-skins-gambling-briefing-2018.pdf",
          "https://wsgc.wa.gov/sites/default/files/2023-10/Skins%20Gambling.pdf",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wsgc-briefing-manifest.json",
          "https://x.com/csgobig",
          "https://www.facebook.com/csgobigofficial/",
          "https://500.casino/",
          "https://csgolounge.com/",
          "https://csgocasino.gg/",
          "https://x.com/CSGOatsecom",
          "https://x.com/CSGOSweep/status/937420902538543106",
          "https://x.com/Wild",
          "https://x.com/csgopot",
          "https://x.com/csgodiamondscom",
          "https://www.ftc.gov/legal-library/browse/cases-proceedings/162-3184-csgo-lotto-matter",
          "https://x.com/CSGODouble",
          "https://x.com/csgo_massive",
          "https://www.facebook.com/csgostrongfree/",
          "https://www.facebook.com/CSNCOM/",
          "https://www.gamblingcommission.gov.uk/report/young-people-and-gambling",
          "https://www.aph.gov.au/Parliamentary_Business/Committees/Senate/Environment_and_Communications/Gamingmicro-transactions",
          "https://phishdestroy.io/steam_dossier/pl/elite_skins.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/csfloat-catalogue.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/skinport-floor-over-cap.json",
          "https://pricempire.com/cs2-marketplaces",
          "http://web.archive.org/web/20260921022459/https://pricempire.com/cs2-marketplaces",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/priceempire-marketplaces.json",
          "https://www.steamanalyst.com/marketplace",
          "http://web.archive.org/web/20260719014552/https://www.steamanalyst.com/marketplace",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-atlas.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json",
          "https://phishdestroy.io/steam_dossier/pl/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/pl/steam_enforcement_evidence.html#case-support-recovery",
          "https://top10.owasp.org/2025/A01_2025-Broken_Access_Control/",
          "http://web.archive.org/web/20260920212535/https://top10.owasp.org/2025/A01_2025-Broken_Access_Control/",
          "https://store.steampowered.com/privacy_agreement/",
          "http://web.archive.org/web/20260921021648/https://store.steampowered.com/privacy_agreement/",
          "https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "http://web.archive.org/web/20250818113925/https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "https://www.dexerto.com/counter-strike-2/valve-saves-hacked-cs2-player-threatened-with-ransom-over-300000-of-rare-stickers-3283135/",
          "https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "http://web.archive.org/web/20220702042821/https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "https://www.kaspersky.com/blog/cs-go-two-million-usd-inventory-hack/44697/",
          "https://esportfire.com/article/the-2-million-usd-csgo-hack-22062022",
          "http://web.archive.org/web/20260515110250/https://esportfire.com/article/the-2-million-usd-csgo-hack-22062022",
          "https://esportsbetting.com/valve-deletes-130000-stolen-dragon-lore/",
          "https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "http://web.archive.org/web/20251115173120/https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "https://vkplay.ru/media/news/bloger-rasskazal-kak-podderzhka-steam-vorovala-akkaunty-igrokov/",
          "https://lis-skins.com/ru/blog/krupneisaia-mosenniceskaia-sxema-v-istorii-steam/",
          "https://escorenews.com/ru/csgo/news/44056-sotrudniki-podderjki-steam-zanimalis-krajey-skinov-s-akkauntov-za-god-oni-zarabotali-svyshe-300-tysyach-dollarov",
          "https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "http://web.archive.org/web/20250805141942/https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/outsourcing-archive-records.json",
          "https://community.skin.club/en/news/collector-has-steam-inventory-returned-after-bold-hack",
          "https://esportfire.com/article/300k-scam-full-katowice-2014-holo-collection-hacked",
          "http://web.archive.org/web/20251217072445/https://esportfire.com/article/300k-scam-full-katowice-2014-holo-collection-hacked",
          "https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng",
          "http://web.archive.org/web/20260920024236/https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng",
          "https://ag.ny.gov/press-release/2026/attorney-general-james-sues-game-developer-promoting-illegal-gambling-through",
          "http://web.archive.org/web/20260901015430/https://ag.ny.gov/press-release/2026/attorney-general-james-sues-game-developer-promoting-illegal-gambling-through",
          "https://www.fincen.gov/sites/default/files/2019-05/FinCEN%20CVC%20Guidance%20FINAL.pdf",
          "http://web.archive.org/web/20250711185007/https://www.fincen.gov/sites/default/files/2019-05/FinCEN%20CVC%20Guidance%20FINAL.pdf",
          "https://eur-lex.europa.eu/legal-content/EN/LSU/?uri=CELEX:32018L1673",
          "https://eur-lex.europa.eu/eli/dir/2024/1640/oj/eng",
          "http://web.archive.org/web/20260830153004/https://eur-lex.europa.eu/eli/dir/2024/1640/oj/eng",
          "https://eur-lex.europa.eu/eli/reg/2022/2065/oj/eng",
          "http://web.archive.org/web/20260920080125/https://eur-lex.europa.eu/eli/reg/2022/2065/oj/eng",
          "https://phishdestroy.io/steam_dossier/pl/legal_analysis.html",
          "https://partner.steamgames.com/doc/features/auth#website",
          "http://web.archive.org/web/20260921022335/https://partner.steamgames.com/doc/features/auth",
          "https://www.ftc.gov/legal-library/browse/rules/childrens-online-privacy-protection-rule-coppa",
          "http://web.archive.org/web/20260921070051/https://www.ftc.gov/legal-library/browse/rules/childrens-online-privacy-protection-rule-coppa",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/gdpr-ticket-1.png",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/screenshot-manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/gdpr-ticket-2.png",
          "https://datenschutz.hamburg.de/beschwerde",
          "https://edpb.europa.eu/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/regulatory-review/disclosure-audit.json",
          "https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "http://web.archive.org/web/20260821155801/https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "https://phishdestroy.io/steam_dossier/pl/index#exhibit-gallery-section",
          "https://github.com/ValveSoftware/steam-for-linux/issues/4521",
          "https://phishdestroy.io/steam_dossier/pl/steam_evidence_archive.html?source=GitHub&record=484",
          "https://github.com/ValveSoftware/steam-for-linux/issues/6459",
          "http://web.archive.org/web/20260419051343/https://github.com/ValveSoftware/steam-for-linux/issues/6459",
          "https://phishdestroy.io/steam_dossier/pl/steam_evidence_archive.html?source=GitHub&record=467",
          "https://github.com/ValveSoftware/Source-1-Games/issues/3857",
          "https://phishdestroy.io/steam_dossier/pl/steam_evidence_archive.html?source=GitHub&record=768",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "http://web.archive.org/web/20250320082450/https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://phishdestroy.io/steam_dossier/pl/steam_evidence_archive.html?source=Reddit&record=4533",
          "https://www.reddit.com/r/ohnePixel/comments/1hahqx2/permanently_banned_steam_account_without_a_clear/",
          "https://phishdestroy.io/steam_dossier/pl/steam_evidence_archive.html?source=Reddit&record=4766",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://phishdestroy.io/steam_dossier/pl/steam_evidence_archive.html?source=Reddit&record=4592",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/selected-evidence-records.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive_manifest.json",
          "https://phishdestroy.io/steam_dossier/pl/card_economy.html",
          "https://github.com/JustArchiNET/ArchiSteamFarm/wiki/FAQ",
          "https://phishdestroy.io/steam_dossier/pl/card_economy.html#scale",
          "https://phishdestroy.io/steam_dossier/pl/card_economy.html#licence",
          "https://phishdestroy.io/steam_dossier/pl/enforcement_audit.html",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "http://web.archive.org/web/20260924181709/https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://rdap.verisign.com/com/v1/domain/csgoempire.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoempire.com",
          "https://rdap.verisign.com/com/v1/domain/csgoempirelogin4.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/csgoempire.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustreaper.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustreaper.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/rustreaper.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustly.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustly.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/rustly.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgofast.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgofast.com",
          "https://rdap.verisign.com/com/v1/domain/authtofast.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/csgofast.com.json",
          "https://rdap.verisign.com/com/v1/domain/duelbits.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fduelbits.com",
          "https://rdap.verisign.com/com/v1/domain/switchflips.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/duelbits.com.json",
          "https://rdap.verisign.com/com/v1/domain/farmskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffarmskins.com",
          "https://tld-rdap.verisign.com/cc/v1/domain/kobal.cc",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/farmskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoluck.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoluck.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/csgoluck.com.json",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/domain-registry/insane.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Finsane.gg",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/insane.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs2skin.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs2skin.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/cs2skin.com.json",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/domain-registry/juice.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fjuice.gg",
          "https://rdap.verisign.com/com/v1/domain/letmeinjuice.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/juice.gg.json",
          "https://rdap.verisign.com/com/v1/domain/ggdrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fggdrop.com",
          "https://rdap.verisign.com/com/v1/domain/ggauth.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/ggdrop.com.json",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/domain-registry/howl.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhowl.gg",
          "https://rdap.radix.host/rdap/domain/howl.uno",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/howl.gg.json",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/domain-registry/chicken.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fchicken.gg",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/chicken.gg.json",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/domain-registry/csgocasino.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgocasino.gg",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/csgocasino.gg.json",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/domain-registry/hunt.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhunt.gg",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/hunt.gg.json",
          "https://rdap.verisign.com/com/v1/domain/csbattle.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsbattle.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/csbattle.com.json",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/domain-registry/skinrave.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinrave.gg",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/skinrave.gg.json",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/domain-registry/csdouble.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsdouble.gg",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/csdouble.gg.json",
          "https://rdap.verisign.com/com/v1/domain/rustchance.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustchance.com",
          "https://rdap.verisign.com/com/v1/domain/hgfuihd.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/rustchance.com.json",
          "https://rdap.radix.host/rdap/domain/cobaltlab.tech",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcobaltlab.tech",
          "https://rdap.verisign.com/com/v1/domain/cobaltauth.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/cobaltlab.tech.json",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/domain-registry/raided.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fraided.gg",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/raided.gg.json",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/domain-registry/rustneo.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustneo.gg",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/rustneo.gg.json",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/domain-registry/splits.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsplits.gg",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/splits.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/upgrader.pro",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fupgrader.pro",
          "https://rdap.radix.host/rdap/domain/upgauth.space",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/upgrader.pro.json",
          "https://rdap.centralnic.com/fans/domain/skin.fans",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.fans",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/skin.fans.json",
          "https://rdap.nic.one/domain/hotpizza.one",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhotpizza.one",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/hotpizza.one.json",
          "https://rdap.verisign.com/com/v1/domain/g4skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg4skins.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/g4skins.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2royal.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2royal.com",
          "https://rdap.verisign.com/com/v1/domain/tf2auth.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/tf2royal.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2hunt.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2hunt.com",
          "https://rdap.verisign.com/com/v1/domain/rstspcl.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/tf2hunt.com.json",
          "https://rdap.identitydigital.services/rdap/domain/tf2.bet",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2.bet",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/tf2.bet.json",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/domain-registry/openstars.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fopenstars.gg",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/openstars.gg.json",
          "https://rdap.verisign.com/com/v1/domain/skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/skins.com.json",
          "https://rdap.identitydigital.services/rdap/domain/white.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwhite.market",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/white.market.json",
          "https://rdap.identitydigital.services/rdap/domain/moon.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmoon.market",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/moon.market.json",
          "https://rdap.verisign.com/com/v1/domain/csfloat.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsfloat.com",
          "https://rdap.verisign.com/com/v1/domain/csgofloat.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/csfloat.com.json",
          "https://rdap.identitydigital.services/rdap/domain/skin.land",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.land",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/skin.land.json",
          "https://rdap.verisign.com/com/v1/domain/haloskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhaloskins.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/haloskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/163.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuff.163.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/buff.163.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmarket.csgo.com",
          "https://rdap.verisign.com/net/v1/domain/dota2.net",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/market.csgo.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinport.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinport.com",
          "https://pubapi.registry.google/rdap/domain/skinport.app",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/skinport.com.json",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/domain-registry/skinflow.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinflow.gg",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/skinflow.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/skin.place",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.place",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/skin.place.json",
          "https://rdap.verisign.com/com/v1/domain/skinsmonkey.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinsmonkey.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/skinsmonkey.com.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbaron.de",
          "https://rdap.verisign.com/com/v1/domain/skinbaron.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/skinbaron.de.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frust.tm",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/rust.tm.json",
          "https://rdap.verisign.com/com/v1/domain/pirateswap.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fpirateswap.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/pirateswap.com.json",
          "https://rdap.radix.host/rdap/domain/mannco.store",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmannco.store",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/mannco.store.json",
          "https://rdap.verisign.com/com/v1/domain/skinswap.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinswap.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/skinswap.com.json",
          "https://rdap.verisign.com/com/v1/domain/exeskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fexeskins.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/exeskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/balticskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbalticskins.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/balticskins.com.json",
          "https://rdap.nic.trade/domain/cs.trade",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.trade",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/cs.trade.json",
          "https://rdap.verisign.com/com/v1/domain/rapidskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frapidskins.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/rapidskins.com.json",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/domain-registry/tradeit.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftradeit.gg",
          "https://rdap.verisign.com/com/v1/domain/connect-tradeit.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/tradeit.gg.json",
          "https://rdap.verisign.com/com/v1/domain/49skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F49skins.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/49skins.com.json",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/domain-registry/skinvault.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinvault.gg",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/skinvault.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/aim.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Faim.market",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/aim.market.json",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/domain-registry/skinout.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinout.gg",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/skinout.gg.json",
          "https://rdap.verisign.com/com/v1/domain/ntskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fntskins.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/ntskins.com.json",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/domain-registry/gamerpay.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamerpay.gg",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/gamerpay.gg.json",
          "https://rdap.nic.tf/domain/scrap.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fscrap.tf",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/scrap.tf.json",
          "https://rdap.nic.tf/domain/marketplace.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmarketplace.tf",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/marketplace.tf.json",
          "https://rdap.identitydigital.services/rdap/domain/skins.cash",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.cash",
          "https://rdap.identitydigital.services/rdap/domain/skinscash.live",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/skins.cash.json",
          "https://rdap.verisign.com/net/v1/domain/csgo.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo.net",
          "https://rdap.verisign.com/net/v1/domain/easylot.net",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/csgo.net.json",
          "https://rdap.verisign.com/net/v1/domain/cybershoke.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcybershoke.net",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/cybershoke.net.json",
          "https://rdap.verisign.com/net/v1/domain/fastcup.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffastcup.net",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/fastcup.net.json",
          "https://rdap.verisign.com/com/v1/domain/leetify.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fleetify.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/leetify.com.json",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/domain-registry/scope.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fscope.gg",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/scope.gg.json",
          "https://rdap.verisign.com/com/v1/domain/tradeupspy.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftradeupspy.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/tradeupspy.com.json",
          "https://rdap.identitydigital.services/rdap/domain/cs.deals",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.deals",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/cs.deals.json",
          "https://rdap.verisign.com/com/v1/domain/pricempire.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fpricempire.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/pricempire.com.json",
          "https://rdap.identitydigital.services/rdap/domain/lzt.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flzt.market",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/lzt.market.json",
          "https://rdap.verisign.com/com/v1/domain/z2u.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fz2u.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/z2u.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoroll.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoroll.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/csgoroll.com.json",
          "https://rdap.verisign.com/com/v1/domain/rollbit.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frollbit.com",
          "https://rdap.verisign.com/com/v1/domain/rbsnin.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/rollbit.com.json",
          "https://rdap.identitydigital.services/rdap/domain/500.casino",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F500.casino",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/500.casino.json",
          "https://rdap.verisign.com/com/v1/domain/csgobig.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgobig.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/csgobig.com.json",
          "https://rdap.verisign.com/com/v1/domain/casedrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcasedrop.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/casedrop.com.json",
          "https://rdap.verisign.com/com/v1/domain/banditcamp.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbanditcamp.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/banditcamp.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinbox.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbox.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/skinbox.com.json",
          "https://rdap.verisign.com/com/v1/domain/tastydrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftastydrop.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/tastydrop.com.json",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/domain-registry/csgopolygon.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgopolygon.gg",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/csgopolygon.gg.json",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/domain-registry/magicdrop.ru.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmagicdrop.ru",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/magicdrop.ru.json",
          "https://rdap.verisign.com/com/v1/domain/csdice.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsdice.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/csdice.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinodds.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinodds.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/skinodds.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgowin.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgowin.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/csgowin.com.json",
          "https://rdap.verisign.com/net/v1/domain/csgorun.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgorun.net",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/csgorun.net.json",
          "https://rdap.verisign.com/com/v1/domain/openskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fopenskins.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/openskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustbet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustbet.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/rustbet.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgomagic.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgomagic.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/csgomagic.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgobounty.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgobounty.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/csgobounty.com.json",
          "https://rdap.verisign.com/com/v1/domain/ezskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fezskins.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/ezskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustcases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustcases.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/rustcases.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoreaper.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoreaper.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/csgoreaper.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgocases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgocases.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/csgocases.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo-skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo-skins.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/csgo-skins.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgonet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgonet.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/csgonet.com.json",
          "https://rdap.verisign.com/com/v1/domain/wtfskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwtfskins.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/wtfskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/flamecases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fflamecases.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/flamecases.com.json",
          "https://rdap.verisign.com/com/v1/domain/gamedom.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamedom.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/gamedom.com.json",
          "https://rdap.nic.club/domain/skin.club",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.club",
          "https://rdap.verisign.com/net/v1/domain/sc-auth.net",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/skin.club.json",
          "https://rdap.verisign.com/com/v1/domain/daddyskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdaddyskins.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/daddyskins.com.json",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/domain-registry/rustix.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustix.gg",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/rustix.gg.json",
          "https://rdap.nic.club/domain/skins.club",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.club",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/skins.club.json",
          "https://rdap.publicinterestregistry.org/rdap/domain/csgohouse.org",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgohouse.org",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/csgohouse.org.json",
          "https://rdap.verisign.com/net/v1/domain/skinrave.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinrave.net",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/skinrave.net.json",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/domain-registry/bloodycase.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbloodycase.gg",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/bloodycase.gg.json",
          "https://rdap.verisign.com/com/v1/domain/csgoclicker.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoclicker.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/csgoclicker.com.json",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/domain-registry/rustbet.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustbet.gg",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/rustbet.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs-drop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs-drop.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/cs-drop.com.json",
          "https://rdap.verisign.com/net/v1/domain/hellstore.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhellstore.net",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/hellstore.net.json",
          "https://rdap.verisign.com/com/v1/domain/rustloot.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustloot.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/rustloot.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo-case.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo-case.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/csgo-case.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgogem.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgogem.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/csgogem.com.json",
          "https://rdap.verisign.com/com/v1/domain/rainbet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frainbet.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/rainbet.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustclash.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustclash.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/rustclash.com.json",
          "https://rdap.identitydigital.services/rdap/domain/12cs.fail",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F12cs.fail",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/12cs.fail.json",
          "https://rdap.verisign.com/com/v1/domain/tf2easy.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwww.tf2easy.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/tf2easy.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2blaze.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2blaze.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/tf2blaze.com.json",
          "https://rdap.verisign.com/com/v1/domain/shuffle.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fshuffle.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/shuffle.com.json",
          "https://rdap.identitydigital.services/rdap/domain/buff.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuff.market",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/buff.market.json",
          "https://rdap.identitydigital.services/rdap/domain/avan.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Favan.market",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/avan.market.json",
          "https://rdap.identitydigital.services/rdap/domain/cs.money",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.money",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/cs.money.json",
          "https://rdap.verisign.com/com/v1/domain/uuskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fuuskins.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/uuskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/youpin898.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fyoupin898.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/youpin898.com.json",
          "https://rdap.verisign.com/com/v1/domain/c5game.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fc5game.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/c5game.com.json",
          "https://rdap.verisign.com/com/v1/domain/waxpeer.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwaxpeer.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/waxpeer.com.json",
          "https://rdap.verisign.com/com/v1/domain/dmarket.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdmarket.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/dmarket.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamcommunity.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamcommunity.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/steamcommunity.com.json",
          "https://rdap.verisign.com/com/v1/domain/lootfarm.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flootfarm.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/lootfarm.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustskins.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/rustskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/krakatoa.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fkrakatoa.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/krakatoa.com.json",
          "https://rdap.verisign.com/com/v1/domain/shadowpay.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fshadowpay.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/shadowpay.com.json",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/domain-registry/igxe.cn.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Figxe.cn",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/igxe.cn.json",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/domain-registry/swap.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fswap.gg",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/swap.gg.json",
          "https://rdap.verisign.com/com/v1/domain/bitskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbitskins.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/bitskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2mart.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2mart.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/tf2mart.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinbid.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbid.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/skinbid.com.json",
          "https://rdap.verisign.com/com/v1/domain/lootbear.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flootbear.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/lootbear.com.json",
          "https://rdap.nic.tf/domain/backpack.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbackpack.tf",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/backpack.tf.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fstntrading.eu",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/stntrading.eu.json",
          "https://rdap.verisign.com/com/v1/domain/skinwallet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinwallet.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/skinwallet.com.json",
          "https://rdap.verisign.com/com/v1/domain/dota2market.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdota2market.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/dota2market.com.json",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/domain-registry/xplay.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fxplay.gg",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/xplay.gg.json",
          "https://rdap.verisign.com/com/v1/domain/esportal.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fesportal.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/esportal.com.json",
          "https://rdap.registro.br/domain/gamersclub.com.br",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamersclub.com.br",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/gamersclub.com.br.json",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/domain-registry/epidemic.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fepidemic.gg",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/epidemic.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs2stash.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs2stash.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/cs2stash.com.json",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/domain-registry/csgoskins.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoskins.gg",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/csgoskins.gg.json",
          "https://rdap.verisign.com/com/v1/domain/steamanalyst.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamanalyst.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/steamanalyst.com.json",
          "https://rdap.verisign.com/net/v1/domain/steamcardexchange.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamcardexchange.net",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/steamcardexchange.net.json",
          "https://rdap.verisign.com/com/v1/domain/dotabuff.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdotabuff.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/dotabuff.com.json",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/domain-registry/tracker.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftracker.gg",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/tracker.gg.json",
          "https://rdap.verisign.com/com/v1/domain/funpay.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffunpay.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/funpay.com.json",
          "https://rdap.verisign.com/com/v1/domain/playerauctions.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fplayerauctions.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/playerauctions.com.json",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/domain-registry/eldorado.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Feldorado.gg",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/eldorado.gg.json",
          "https://rdap.verisign.com/com/v1/domain/g2a.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg2a.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/g2a.com.json",
          "https://rdap.verisign.com/net/v1/domain/kinguin.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fkinguin.net",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/kinguin.net.json",
          "https://rdap.verisign.com/com/v1/domain/g2g.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg2g.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/g2g.com.json",
          "https://rdap.verisign.com/com/v1/domain/playerup.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fplayerup.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/playerup.com.json",
          "https://rdap.verisign.com/net/v1/domain/smurfhub.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfhub.net",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/smurfhub.net.json",
          "https://rdap.verisign.com/com/v1/domain/smurfaccounts.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfaccounts.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/smurfaccounts.com.json",
          "https://rdap.verisign.com/com/v1/domain/buycsgorank.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuycsgorank.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/buycsgorank.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgosmurfkings.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgosmurfkings.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/csgosmurfkings.com.json",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/domain-registry/smurfstore.co.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfstore.co",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/smurfstore.co.json",
          "https://rdap.verisign.com/com/v1/domain/steamlvlup.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlvlup.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/steamlvlup.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamlevels.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlevels.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/steamlevels.com.json",
          "https://rdap.verisign.com/com/v1/domain/levelsteam.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flevelsteam.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/levelsteam.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamlevelu.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlevelu.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/steamlevelu.com.json",
          "https://rdap.verisign.com/com/v1/domain/eloking.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Feloking.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/eloking.com.json",
          "https://rdap.publicinterestregistry.org/rdap/domain/boosteria.org",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fboosteria.org",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/boosteria.org.json",
          "https://rdap.verisign.com/com/v1/domain/overgear.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fovergear.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/overgear.com.json",
          "https://rdap.verisign.com/com/v1/domain/blazingboost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fblazingboost.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/blazingboost.com.json",
          "https://rdap.verisign.com/com/v1/domain/dota2boost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdota2boost.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/dota2boost.com.json",
          "https://rdap.verisign.com/com/v1/domain/buyboost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuyboost.com",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit/buyboost.com.json",
          "https://phishdestroy.io/steam_dossier/pl/steam_tos_assets/auth-route-audit.json",
          "https://help.steampowered.com/en/faqs/view/365F-4BEE-2AE2-7BDD",
          "https://store.steampowered.com/privacy_agreement/#8",
          "https://www.edpb.europa.eu/system/files/2023-04/edpb_guidelines_202201_data_subject_rights_access_v2_en.pdf",
          "https://web.archive.org/web/20260810154631/https://store.steampowered.com/stats/support",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/design-review/part2/measurements.json",
          "https://phishdestroy.io/steam_dossier/pl/VALVE_EVIDENCE_PACK/databases/TOTAL_VALVE_SCANDALS_MASTER_DB.csv",
          "https://phishdestroy.io/steam_dossier/pl/license_disclaimer.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/pl/index.content.json",
      "export_json_sha256": "2d2a8fa4549884db5158fec13f736031e4ea1fc12c8446cbbfbfab3013f74a80"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "pl/investigation_part2.html",
      "language": "pl",
      "title": "Dostęp do konta i odpowiedzialność — Dossier Steam",
      "source_url": "https://phishdestroy.io/steam_dossier/pl/investigation_part2",
      "source_html_sha256": "9d925d7e5b2e13cb6f75f3b3b2d6ebbeab67b2ef360841bf07a31f293cdbf55e",
      "exported_at": "2026-09-29T00:18:53.482Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "investigation_part2.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/pl/investigation_part2.pdf?v=print-20260929-v5",
        "sha256": "32db0ce33e089a3a9d003e61be8b76c9f96682caaf68dc6288c2fd1bb20a0c02",
        "bytes": 133075,
        "pages": 9
      },
      "integrity": {
        "signed_object": "investigation_part2.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "investigation_part2.content.json.asc",
        "digest_file": "investigation_part2.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify investigation_part2.content.json.asc investigation_part2.content.json",
          "sha256sum -c investigation_part2.content.json.sha256"
        ]
      },
      "content": {
        "text": "DOSSIER STEAM / II\n\nTwoje konto.Ich dostęp.Kto odbiera?\n\nAutomatyzacja usług publicznych. Zlecanie wsparcia na zewnątrz. A ludzie muszą ponosić koszty.\n\nŚledź rozwój sytuacji w zakresie infrastruktury, zgłoszone straty oraz dokumenty stanowiące podstawę roszczeń.\n\nPrześledź infrastrukturę ↘\nZAŁĄCZNIK 01 / NADZÓR NAD RYNKIEM „LIVE SHADOW”550,000+\n\nSteam kont aktywnie wystawionych na sprzedaż na platformie FSB Market (nazwa zanonimizowana; oryginalna nazwa nie jest tu podawana)\nwłaśnie w tej chwili\n\n550,000+ AKTUALNE ZAPASY · 231,829 W HISTORYCZNYM KORPUSIE DANYCH ZEBRANYCH (198,320 LOGI STEALERA)\n\nGłówna podziemna platforma wymiany informacji dotycząca przejętych kont Steam, FSB Market (inne powiązane nazwy nie są podawane) weryfikuje tożsamość zarówno kupujących, jak i sprzedających za pomocą oficjalnego identyfikatora OpenID Valve o numerze Steam (openid.realm = https://FSB Market). W każdej chwili w sprzedaży znajduje się ponad pół miliona skradzionych i przejętych kont (logi programów wykradających dane z RedLine/Lumma, dane zebrane w wyniku phishingu, ataki typu credential stuffing), które są oferowane za grosze ($0.50–$2.00). Żadne z nich FSB Market ani powiązane forum jest blokowany przez filtr linków użytkownika Valve. Jest to przemysłowa baza zasilająca 63.06% płatnych kont botów, które Valve blokuje bez udzielania pomocy ofierze.\n\nAktualności na żywo: Monitorowanie rynku cieni (ponad 550 tys. użytkowników na żywo) ↗ · Otwórz zapis przechwycenia ↗ · Otwórz ślad filtra Link ↗Ponad 550 tys. NA ŻYWO\n\n01 / EKOSYSTEM Z AUTORAMI\n\nAutomatyzacja madokumentacja.\n\nNazwane projekty. Opublikowane możliwości. Znajdź dokumentację danego narzędzia, a następnie przeanalizuj zebrane powiązania między programistami.\n\n252ZBIORY ZEBRANE\n3,320PROFILE NA GITHUBIE\n4,214PROFIL – PARY REPOZYTORIÓW\nValve infrastrukturaBiblioteki publiczneAplikacje wielokrotnego użytku\nLinie wskazują udokumentowane integracje lub zależności. Wybierz węzeł, aby prześledzić powiązania z nim związane.\n\nAutomatyzacja obsługi wielu kont / JustArchiNET\n\nArchiSteamFarm\n\nProjekt wyraźnie reklamuje możliwość jednoczesnego zdobywania kart na różnych kontach serwisu Steam. W pliku projektu zadeklarowano zależność od biblioteki SteamKit2.\n\nZapoznaj się z dokumentacją samego projektu ↗\n\nSteamKit → ArchiSteamFarm\nzadeklarowana zależność ↗\n\nZBIÓR RELACJI\n\n40 etykiety autorów · 40 etykiety typu „forker”\n\nPoniżej znajduje się przykładowy wpis autora. Etykiety te opisują powiązania z repozytorium, a nie stosunek pracy ani zatwierdzenie.\n\n@JustArchi@renovate[bot]@JustArchi-ArchiBot@dependabot-preview[bot]@renovate-bot@actions-user@dependabot-support@Abrynos\nCo wynika z wykresu dewelopera\n\nWykres przedstawia opublikowane powiązania między autorami i twórcami rozgałęzień w ramach wymienionych projektów a profilami na GitHubie. Są to dane publiczne — rozgałęzienia repozytoriów, listy wkładu oraz powiązania profilowe. Pytanie dotyczy tego, na jakie pytania musi odpowiedzieć Valve na podstawie śladów dokumentacyjnych dotyczących opublikowanych możliwości i relacji między programistami, a nie tego, co zostało wymyślone w ramach niniejszego badania. Skróty kodu źródłowego są zapisane w pochodzenie mapy.\n\nPoznaj całą sieć ↗Dane źródłowe repozytorium ↓\n\n02 / RÓŻNE UPRAWNIENIA. RÓŻNE MOCE.\n\nKtóry klawiszO czym tu mowa?\n\nRozgrywanie gry nie wymaga od gracza podania osobistego klucza API. To właśnie ta różnica stanowi sedno niniejszego dochodzenia.\n\n01 / KONTO UŻYTKOWNIKA\nOsobisty klucz API serwisu internetowego\nsteamcommunity.com/dev/apikey\n\nWydawane z poziomu konta użytkownika w celu wykonywania dozwolonych wywołań API. Tworzenie kluczy, ich widoczność, unieważnianie oraz wykrywanie nadużyć to kwestie związane z bezpieczeństwem konta.\n\n02 / INFRASTRUKTURA GRY\nKlucz API serwisu internetowego wydawcy\n\nPartnerzy Steamworks korzystają z danych uwierzytelniających wydawcy w celu wykonywania obsługiwanych operacji zaplecza, w tym usług związanych z grami. Klucz osobisty gracza stanowi odrębny element uwierzytelniający.\n\n03 / TOŻSAMOŚĆ I SESJA\nOpenID / tokeny sesji\n\nOpenID służy do potwierdzania tożsamości w witrynie internetowej. Token sesji lub odświeżania Steam ma inne przeznaczenie. Mechanizmów tych nie należy przedstawiać jako jednego, zamiennego „klucza API”.\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\nValve zawiera zarówno klucze API sieciowe użytkowników, jak i wydawców. W związku z tym całość interfejsu API nie jest oddzielona od Steamworks. Dokumentacja klucza API ↗ zarchiwizowano 2026-09-15 ↗ · Uwierzytelnianie podczas sesji gry ↗ zarchiwizowano 2026-08-29 ↗\n\nOPISANIE PRZEZ AUTORA NARZĘDZIA / MARZEC 2024 R.\n\nW automatyzacji można wykorzystać nie tylko klucz API.\n\nW wiki narzędzia Trade Offer Manager opisano sposób korzystania z tokenu dostępu sesyjnego w niektórych częściach interfejsu API, gdy nie ma oddzielnego klucza API. Zawiera ona również informacje o potwierdzeniu na urządzeniu mobilnym wymaganym przy tworzeniu klucza od końca 2023 roku. Opiekun projektu stwierdza, że takie wykorzystanie tokenu nie jest obsługiwane przez Valve; jest to jednak przestarzała informacja zawarta w dokumentacji, a nie wynik aktualnego testu obejścia.\n\nZapoznaj się z wyjaśnieniem osoby odpowiedzialnej za utrzymanie ↗ zarchiwizowano 2026-09-24 ↗\n\nSTRONA LUDZKA / PRZYKŁADOWA ŚCIEŻKA PHISHINGOWA\n\nWciąż gram.Już ujawniono.\n\nWiadomość od znajomego. Prośba o oddanie głosu. Strona z podziękowaniem. Dla gracza zadanie jest zakończone. Sesja, której bezpieczeństwo zostało naruszone, może trwać dłużej niż ta chwila.\n\nNA EKRANIE ODTWARZACZA\n\nF\nRELACJA PRZYJACIELA\n\n„Czy możesz zagłosować na naszą drużynę?”\n\nProśba przychodzi za pośrednictwem czatu serwisu Steam z konta, które użytkownik zna. W tej sytuacji strona, do której prowadzi link, otwiera się w przeglądarce klienta.\n\nPOZA ZASIĘGIEM WZROKU\n\nZaufanie buduje się jeszcze przed uruchomieniem strony internetowej.\n\nPrzejęte konto znajomego może nadać linkowi phishingowemu pozory wiarygodności. Otaczający go interfejs Steam nie potwierdza autentyczności docelowej strony internetowej.\n\nZNANY NADAWCA / ZEWNĘTRZNE MIEJSCE PRZEZNACZENIA\nPrzed sprzedażą jakiegokolwiek przedmiotu należy zadbać o bezpieczeństwo konta.\n\nGracz nie miał zamiaru tworzyć poświadczeń do automatyzacji ani przekazywać kontroli. Powrót do gry nie stanowi dowodu na to, że konto jest bezpieczne. Valve przechowuje logi sesji, zapis dotyczącego utworzenia klucza API oraz dane dotyczące korelacji urządzeń. Ofiara nie posiada tych danych. Ta asymetria stanowi problem odpowiedzialności.\n\nDostęp do sesji i rodzaje poświadczeń\n\nKlucz API i sesja logowania to odrębne poświadczenia o różnych uprawnieniach. Cofnięcie klucza nie powoduje zakończenia aktywnej sesji. Dokumentacja Valve opisuje oba te elementy; Valve przechowuje logi, które pozwoliłyby ustalić, które poświadczenie było aktywne w momencie wykonania jakiejkolwiek spornej czynności. Żądamy ujawnienia tego zapisu — a nie wniosków wyciągniętych w wyniku dochodzenia. Dokumentacja opiekuna dotycząca obsługi tokenów ↗ zarchiwizowano 2026-09-24 ↗ · Valve kluczowa dokumentacja ↗ zarchiwizowano 2026-09-15 ↗\n\n03 / RYNEK OFICJALNY MA SWÓJ PUŁAP\n\nTen przedmiot może być rzadki.Ograniczenie pozostaje w mocy.\n\nCeny przekraczającej limit wyceny nie można osiągnąć poprzez jedną ofertę na Rynku Wspólnotowym po tej pełnej cenie.\n\nORIENTACYJNA CENA WYWOŁAWCZA$5,000Zmień cenę wywoławczą przedmiotu\n$100$20,000\n\nIlustracja opublikowanego limitu, a nie wycena ani zalecenie dotyczące transakcji.\n\nLIMIT OFERT≈ $1,800\nCZAPKA Z KAPSUŁĄ≈ $2,000\n\nPowyżej opublikowanego limitu notowań.\n\nŚrodków z portfela nie można wypłacić na konto bankowe. Ograniczenia te powodują powstanie popytu, który zaspokajają zewnętrzne rynki skórek: popytu generowanego przez limity dotyczące wystawiania ofert i portfeli, podczas gdy własne zasady serwisu Valve uniemożliwiają komercyjnym operatorom zaspokojenie tego popytu.\n\nLimity rynkowe Steam ↗ zarchiwizowano 2026-09-21 ↗\n\n04 / W OBSZARZE GRANICY WSPARCIA\n\nPowierzono nam dane.Odpowiada za dostęp.\n\nPolityka prywatności serwisu Valve wyraźnie przewiduje udostępnianie danych osobowych zewnętrznym dostawcom usług wsparcia technicznego, o ile jest to konieczne do zapewnienia wsparcia.\n\nGRACZKonto i dowody\n→\nZAWÓRProces odzyskiwania\n→\nDOSTAWCA WSPARCIADostęp delegowany\n\nPolityka prywatności §5.2 ↗ · Polityka firmy Valve zezwala na dostęp podmiotów zewnętrznych w celu zapewnienia wsparcia. Otwarte pozostają następujące pytania: jakie uprawnienia zostały przyznane, jakie istnieją ścieżki audytu oraz co się stało, gdy rzekomo doszło do nadużycia tego dostępu.\n\n2015\nSkala była publiczna\n\nValve potwierdziło, że doszło do masowych kradzieży kont, i opisało środki ochronne.\n\nValve publikacja ↗zarchiwizowano 2026-08-09 ↗\n2015\nValve zlecił obsługę stanowiska firmie zewnętrznej — i tak też powiedział\n\nValve utrzymuje niewielki wewnętrzny zespół kierowniczy ds. wsparcia Steam i oświadczył, że „zatrudnił kilka różnych firm” w celu obsługi pomocy technicznej (Erik Johnson, Valve, serwis Kotaku); zgodnie z § 5.2 polityki prywatności serwisu te strony trzecie mają prawo dostępu do danych użytkowników. Który wykonawca posiada uprawnienia do odzyskiwania kont, Valve nigdy tego nie ujawnił — W dyskusjach społecznościowych pojawiają się nazwy takich dostawców jak Concentrix, ale żadna z nich nie została Valve-potwierdzona. Zewnętrzne centrum obsługi działało już na długo przed obydwoma poniższymi przyznaniami.\n\nKotaku: Valve w sekcji pomocy ↗zarchiwizowano 2025-07-11 ↗\n2023\nPierwsze przyjęcie\n\nDrużyna CS:GO Valve przyjmuje na piśmie odpowiedzialność za włamanie na konto, do którego doszło w wyniku działania jej własnego systemu zgłaszania problemów, i cofa transakcje.\n\nOtwórz sprawę dotyczącą outsourcingu ↓\n2025\nDrugie przyjęcie\n\n33 miesiące później dział pomocy technicznej Steam informuje, że technik „nie zastosował się do naszej procedury, co spowodowało, że Państwa konto zostało przywrócone innej osobie”. Ten sam kanał. Ten sam wynik.\n\nDexerto, 14 listopada 2025 r. ↗\n\nAKTA SPRAWY / HFB I ZARZUTY DOTYCZĄCE OUTSOURCINGU\n\nDrogą do tego było samo wsparcie Steam.Valve potwierdził to na piśmie.\n\nW odpowiedzi działu pomocy technicznej opublikowanej przez serwis Dexerto drużyna CS:GO Valve przyznaje się do odpowiedzialności za włamanie na konto w ramach procedury zgłaszania prośby o pomoc — własny kanał, a nie strona phishingowa ani sam użytkownik. Pozycje zostały odzyskane, a transakcje cofnięte, co stanowi środek zaradczy, o którym Valve informuje inne ofiary, że nie istnieje. Stan zapasów HFB wyniósł $2,000,000+ tego dnia oraz $3,000,000+ w dalszej części; Qkss przegrał $1,000,000+ w ten sam sposób i nic nie zdobył.\n\nODPOWIEDŹ DZIAŁU POMOCY / PRZEKAZANE PRZEZ DEXERTO · 21 LUTEGO 2023 r.\n„zostało naruszone w wyniku zgłoszenia do pomocy technicznej, za co odpowiedzialność bierze zespół CS:GO”\nPrzeczytaj relację i zacytowaną wiadomość ↗ zarchiwizowano 2025-08-18 ↗\n01 / JAKI ZAWÓR ZOSTAŁ ZATWIERDZONY\nWłasny kanał wsparcia był drogą do tego\n\nOdpowiedź dotyczy konta, którego bezpieczeństwo zostało naruszone, oraz anulowania transakcji z tego konta. Valve je anulował — znaczy, że transakcje te można było cofnąć. Oryginalny, uwierzytelniony bilet nie znajduje się w tym zbiorze.\n\n02 / CZEGO NIE UDAŁO SIĘ ROZWIĄZAĆ POPRZEZ ZWOLNIENIA\nTe same drzwi otworzyły się ponownie w listopadzie 2025 roku\n\nWykonawca zwolnił cały swój personel wsparcia Steam — jak poinformował serwis Mzkshow za pośrednictwem Dexerto; nie było to oświadczenie Valve wydane przez dział kadr. Trzydzieści trzy miesiące później firma Steam Support napisała do innego użytkownika serwisu, że „technik wsparcia, który zajmował się zgłoszeniem pomocy, nie zastosował się do naszej procedury, co spowodowało przywrócenie Państwa konta innej osobie”. To zdanie pochodzi z Valve i dotyczy tego samego kanału.\n\nDruga hospitalizacja, 14 listopada 2025 r. ↗\n03 / CO TO JEST OPEN\nValve nigdy nie podał nazwy wykonawcy\n\nŹródła te nie podają ani nazwy wykonawcy, ani lokalizacji. Nie jest to luka w sprawozdaniu — jest to informacja, której Valve nie ujawniło, a która dotyczy tego, kto miał dostęp do kont użytkowników.\n\nWspółczesna relacja z tej sprawy ↗\n\nTrzy pytania, na które Valve nie udzielił odpowiedzi: kto mógł zablokować proces odzyskiwania konta, jakie ustalenia przyniosła kontrola dostępu oraz co się zmieniło po tym wydarzeniu.\n\nPóźniejsze zarzuty zawarte w zachowanym archiwum dokumentacji pomocniczej\n\nDwa wpisy na Reddicie z 2024 r. zawierają informacje o kolejnych dochodzeniach dotyczących Mzkshow — sprawie zniesienia blokady VAC z lipca 2024 r. oraz sprawie dotyczącej zasobów $13,000 z grudnia 2024 r. Są to oddzielnie zgłoszone zdarzenia. W obu przypadkach pytania dotyczące odpowiedzialności są identyczne: kto miał uprawnienia do obejścia ograniczeń, co wykazał audyt i co się zmieniło.\n\n14 lipca 2024 r. · zgłoszono odzyskanie / sprawa dotycząca zakazu VAC↗2 grudnia 2024 r. · zgłoszono $13,000 przypadek dotyczący zapasów ↗zarchiwizowano 2025-08-05 ↗Dwa zachowane słupki, wiersze źródłowe i skróty ↓\n\n05 / ŚLADEM STRATY\n\nKażda kwotapotrzebuje etui.\n\nDziesięć spraw, od czerwca 2022 r. do marca 2026 r. Każda kwota odpowiada danym opublikowanym przez wskazane źródło — $6,300,000, $2,000,000+, $1,000,000+, ≈$320,000, ≈$300,000, a cena spadła do 288 euro. Valve przechowuje dziennik transakcji, zapis sesji oraz ścieżkę audytową pomocy technicznej dla każdej z nich, ale nie udostępnił żadnego z tych dokumentów.\n\nKANAŁ WSPARCIA21 CZERWIEC 2022\n$2,000,000+\nHFB — the largest inventory in the game\n\nZGŁOSZONA WYCENA ZAPASÓW · PODWYŻSZONA DO PONAD3M W LUTYM 2023 – DALSZE INFORMACJE\n\nSiedem pamiątkowych noży Dragon Lores oraz karambit #1Blue Gem, którego cena wynosi około $1.26m. Konto pozostawało nieaktywne przez trzy lata, a funkcja uwierzytelniania była nadal włączona; adres e-mail i hasło zmieniono za pośrednictwem procedury odzyskiwania dostępu w dziale pomocy technicznej. Firma Valve cofnęła transakcje — i potwierdziła swoją odpowiedzialność na piśmie. Przed cofnięciem transakcji zgłoszono, że kwota $200,000+ zysków została już wypłacona za pośrednictwem serwisu market.csgo.com, który obsługuje płatności gotówkowe i kryptowalutowe. Cofnięcie transakcji powoduje zwrot skórki, a nie pieniędzy, które ktoś już zdeponował na koncie. Cofnięcie transakcji spowodowało również błąd: nabywca ukrył swój przedmiot „Souvenir Dragon Lore” w magazynie w grze, skrypt nie mógł zajrzeć do wnętrza tego kontenera, a serwis Valve zduplikował przedmiot o wartości $130,000 podczas cofania kradzieży — wykryto to dzięki identyfikatorom przedmiotów i zgłoszeniom społeczności, a przedmiot usunięto w lipcu 2022,. Nabywca otrzymał zwrot środków od serwisu BUFF, a nie od Valve.\n\nDexerto, dzień kradzieży ↗\nPORTFEL I ZAKUPY07 LIPIEC 2022\n>$500\n44 disputed Market purchases\n\nDEKLAROWANE WYDATKI Z PORTFELA · USD\n\nUżytkownik zgłasza nieautoryzowane zakupy przedmiotów o niskiej wartości w grze Dota 2 oraz niezadowalającą reakcję działu obsługi klienta.\n\nPrzeczytaj skargę i obejrzyj załączone zrzuty ekranu ↗\nNARUSZENIE BEZPIECZEŃSTWA PLATFORMY14 Sierpień 2022\n$6,300,000\nCS.Money — 19,000+ skórki z botów\n\nWYCENA · PIERWSZA WYCENA $1.6M\n\nHakerzy przejęli pliki aplikacji do uwierzytelniania mobilnego należące do botów handlowych platformy i opróżnili je, przekazując część zdobyczy znanym inwestorom, aby zmylić ślady. Badacze ze społeczności w ciągu kilku godzin zidentyfikowali konta atakujących 55. Valve nie zdołało nic odwrócić — strona zewnętrzna znajduje się poza Steam, poinformowała ta sama firma Steam, której zapasy, system transakcyjny API oraz system kont były przedmiotem kradzieży od początku do końca.\n\nPrzeczytaj współczesną relację ↗\nKANAŁ WSPARCIAOPUBLIKOWANO 21 LUTY 2023\n$1,000,000+\nQkss — te same drzwi, ten sam aktor, przeciwna odpowiedź\n\nZGŁOSZONA WYCENA ZAPASÓW\n\nRozpatrywano to w taki sam sposób, jak sprawę HFB – przez tego samego aktora, w ramach tego samego zgłoszenia do pomocy technicznej. Sprawa HFB została całkowicie rozstrzygnięta osiem miesięcy wcześniej. Sprawa Qkss – nie. W opublikowanej dokumentacji nie ma nic, co odróżniałoby te dwie sprawy, poza liczbą osób, których dotyczyły.\n\nDexerto o śledztwie w sprawie Mzkshow ↗\nKANAŁ WSPARCIAOPUBLIKOWANO 2023\n≈ $320,000\nSamo wykorzystywanie informacji poufnych — w ciągu jednego roku\n\nWYNIKI Z OKOŁO ROKU · NIE JEST TO WYCENA ZAPASÓW\n\nDział wsparcia uzyskał dostęp do historii konta sięgającej nawet 15 lat wstecz: pierwszy klucz CD, pierwszy e-mail, pierwsza karta — dokładnie te dowody, których wymaga proces odzyskiwania konta. Ktokolwiek posiada bazę danych, zawsze wygrywa tę dyskusję z posiadaczem konta. Jeden skradziony M4A4 Howl z hologramami iBUYPOWER i Titan Katowice 2014 został sprzedany za $35,000 i trafił do b1t z drużyny NAVI, który nie miał o tym pojęcia. Reakcją wykonawcy było zwolnienie wszystkich pracowników obsługujacSteam.\n\nEscorenews na temat tego samego śledztwa ↗\nPORTFEL I ZAKUPY09 GRUDZIEŃ 2023\n€288\nUtrata portfela pomimo dwustopniowej ochrony\n\nTRUSTPILOT · INDEKS ŹRÓDEŁ 16\n\nRecenzent zgłasza włamanie na konto oraz odmowę pomocy w sprawie wydatków w Market. Eksport nie zawiera indywidualnego adresu URL recenzji.\n\nSprawdź pochodzenie źródła ↗\nODZYSKIWANIE KONTA02 GRUDZIEŃ 2024\n$13,000\n„Matvey” — dwa lata po zwolnieniach\n\nSZACUNKOWY STAN ZAPASÓW AUTORA\n\nOdzyskanie dostępu przyznano osobie, która podała dane konta, których sam właściciel nie był w stanie potwierdzić. Ta sama procedura, ten sam wynik – po tym, jak wykonawca zlikwidował swoje centrum pomocy technicznej pod adresem Steam.\n\nPrzeczytaj zachowane zarzuty ↗\nODZYSKIWANIE KONTA09 MAJ 2025\n≈ $10,000\nOdzyskanie środków za pomocą biletu innej osoby\n\nZGŁOSZONA UTRATA PRZEDMIOTU · USD\n\nUżytkownik z Quebecu twierdzi, że dział pomocy technicznej zresetował hasło i usunął zabezpieczenia konta na prośbę innej osoby.\n\nPrzeczytaj skargę sporządzoną w pierwszej osobie ↗\nKANAŁ WSPARCIA13 LISTOPAD 2025\n≈ $300,000\nHawkeye337 — oraz drugie pisemne przyznanie się do winy ze strony „Valve”\n\nPEŁNA KOLEKCJA HOLO Z KATOWIC „2014”\n\nAtakujący zażądał bitcoina o wartości 1 i zaczął przenosić zawartość konta na portfele Negev, aby je zniszczyć. Steam Odpowiedź działu pomocy technicznej: „technik obsługi klienta, który zajmował się zgłoszeniem, nie zastosował się do naszej procedury, co spowodowało, że Twoje konto zostało przywrócone innej osobie”. Trzydzieści trzy miesiące po pierwszym zgłoszeniu – ta sama sytuacja. Konto przywrócono w ciągu kilku godzin od momentu, gdy wątek stał się popularny na X. Qkss nie miało takiej liczby odbiorców.\n\nDexerto, 14 Nov 2025 ↗\nPORTFEL I ZAKUPY29 MAR 2026\n$50\nNieautoryzowane doładowania i gry otrzymane w prezencie\n\nTRUSTPILOT · INDEKS ŹRÓDEŁ 290\n\nRecenzent zarzuca nieautoryzowane wydatki i bezskuteczne wnioski o zwrot kosztów. W eksporcie brakuje adresu URL konkretnej recenzji.\n\nSprawdź pochodzenie źródła ↗\n\nŹródła i kwoty pozostają zgodne z danymi podanymi przez poszczególne źródła. Valve przechowuje dzienniki transakcji, zapisy sesji oraz ścieżkę audytową wsparcia technicznego dla każdego z tych przypadków. Należy je przedstawić. Zachowany wpis na Reddicie nie rozstrzyga tej kwestii — rozstrzygają ją własne zapisy Valve.\n\nKOLEKCJA / PO SPRAWDZENIU\n\n231,829 kont w promocji.Valve zawiera logi dotyczące każdego z nich.\n354 → 201\nDane z serwisu Trustpilot\n\nUsunięto 153 zduplikowane wiersze. Adresy URL poszczególnych recenzji nie zostały zachowane w eksporcie.\n\n231,829\nSteam wykazy kont\n\n33,509 sklasyfikowane jako zarejestrowane automatycznie; 198,320 oznaczone przez kolekcjonera jako „skradzione”. Oferty nie oznaczają sfinalizowanych transakcji.\n\nKontrola zbiorów ↓Przeszukaj archiwum źródłowe ↗",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Twoje konto.Ich dostęp.Kto odbiera?"
          },
          {
            "level": 2,
            "id": null,
            "text": "Automatyzacja madokumentacja."
          },
          {
            "level": 3,
            "id": null,
            "text": "ArchiSteamFarm"
          },
          {
            "level": 2,
            "id": null,
            "text": "Który klawiszO czym tu mowa?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Osobisty klucz API serwisu internetowego"
          },
          {
            "level": 3,
            "id": null,
            "text": "Klucz API serwisu internetowego wydawcy"
          },
          {
            "level": 3,
            "id": null,
            "text": "OpenID / tokeny sesji"
          },
          {
            "level": 3,
            "id": null,
            "text": "W automatyzacji można wykorzystać nie tylko klucz API."
          },
          {
            "level": 2,
            "id": null,
            "text": "Wciąż gram.Już ujawniono."
          },
          {
            "level": 3,
            "id": "session-hidden-title",
            "text": "Zaufanie buduje się jeszcze przed uruchomieniem strony internetowej."
          },
          {
            "level": 2,
            "id": null,
            "text": "Ten przedmiot może być rzadki.Ograniczenie pozostaje w mocy."
          },
          {
            "level": 2,
            "id": null,
            "text": "Powierzono nam dane.Odpowiada za dostęp."
          },
          {
            "level": 3,
            "id": null,
            "text": "Skala była publiczna"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve zlecił obsługę stanowiska firmie zewnętrznej — i tak też powiedział"
          },
          {
            "level": 3,
            "id": null,
            "text": "Pierwsze przyjęcie"
          },
          {
            "level": 3,
            "id": null,
            "text": "Drugie przyjęcie"
          },
          {
            "level": 3,
            "id": null,
            "text": "Drogą do tego było samo wsparcie Steam.Valve potwierdził to na piśmie."
          },
          {
            "level": 4,
            "id": null,
            "text": "Własny kanał wsparcia był drogą do tego"
          },
          {
            "level": 4,
            "id": null,
            "text": "Te same drzwi otworzyły się ponownie w listopadzie 2025 roku"
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve nigdy nie podał nazwy wykonawcy"
          },
          {
            "level": 2,
            "id": null,
            "text": "Każda kwotapotrzebuje etui."
          },
          {
            "level": 3,
            "id": null,
            "text": "HFB — the largest inventory in the game"
          },
          {
            "level": 3,
            "id": null,
            "text": "44 disputed Market purchases"
          },
          {
            "level": 3,
            "id": null,
            "text": "CS.Money — 19,000+ skórki z botów"
          },
          {
            "level": 3,
            "id": null,
            "text": "Qkss — te same drzwi, ten sam aktor, przeciwna odpowiedź"
          },
          {
            "level": 3,
            "id": null,
            "text": "Samo wykorzystywanie informacji poufnych — w ciągu jednego roku"
          },
          {
            "level": 3,
            "id": null,
            "text": "Utrata portfela pomimo dwustopniowej ochrony"
          },
          {
            "level": 3,
            "id": null,
            "text": "„Matvey” — dwa lata po zwolnieniach"
          },
          {
            "level": 3,
            "id": null,
            "text": "Odzyskanie środków za pomocą biletu innej osoby"
          },
          {
            "level": 3,
            "id": null,
            "text": "Hawkeye337 — oraz drugie pisemne przyznanie się do winy ze strony „Valve”"
          },
          {
            "level": 3,
            "id": null,
            "text": "Nieautoryzowane doładowania i gry otrzymane w prezencie"
          },
          {
            "level": 2,
            "id": null,
            "text": "231,829 kont w promocji.Valve zawiera logi dotyczące każdego z nich."
          },
          {
            "level": 3,
            "id": null,
            "text": "Dane z serwisu Trustpilot"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam wykazy kont"
          }
        ],
        "links": [
          "https://phishdestroy.io/live-intel/?category=steam",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/lzt.market.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-evidence-lzt.json",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://github.com/JustArchiNET/ArchiSteamFarm/blob/main/ArchiSteamFarm/ArchiSteamFarm.csproj",
          "https://github.com/JustArchi",
          "https://github.com/renovate[bot]",
          "https://github.com/JustArchi-ArchiBot",
          "https://github.com/dependabot-preview[bot]",
          "https://github.com/renovate-bot",
          "https://github.com/actions-user",
          "https://github.com/dependabot-support",
          "https://github.com/Abrynos",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/automation-map.json",
          "https://phishdestroy.io/steam_dossier/pl/output_steam_network/network.html",
          "https://phishdestroy.io/steam_dossier/pl/output_steam_network/raw_data.json",
          "https://phishdestroy.io/steam_dossier/pl/#proxy-bypass-explainer",
          "https://partner.steamgames.com/doc/webapi_overview/auth",
          "http://web.archive.org/web/20260915025812/https://partner.steamgames.com/doc/webapi_overview/auth",
          "https://partner.steamgames.com/doc/webapi/ISteamUserAuth",
          "http://web.archive.org/web/20260829124950/https://partner.steamgames.com/doc/webapi/ISteamUserAuth",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "http://web.archive.org/web/20260924181824/https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://store.steampowered.com/privacy_agreement/",
          "https://store.steampowered.com/oldnews/19618",
          "http://web.archive.org/web/20260809125516/https://store.steampowered.com/oldnews/19618",
          "https://kotaku.com/valve-explains-why-steam-customer-service-is-still-terr-1736988223",
          "http://web.archive.org/web/20250711004653/https://kotaku.com/valve-explains-why-steam-customer-service-is-still-terr-1736988223",
          "https://www.dexerto.com/counter-strike-2/valve-saves-hacked-cs2-player-threatened-with-ransom-over-300000-of-rare-stickers-3283135/",
          "https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "http://web.archive.org/web/20250818113925/https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "https://lis-skins.com/ru/blog/krupneisaia-mosenniceskaia-sxema-v-istorii-steam/",
          "https://www.reddit.com/r/cs2/comments/1e38jo4/stealing_accounts_and_removing_vac_bans_a_new/",
          "https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "http://web.archive.org/web/20250805141942/https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/outsourcing-archive-records.json",
          "https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "https://escorenews.com/en/csgo/news/44087-valve-steam-support-employee-accused-of-selling-inactive-accounts-inventories-worth-six-figures-b1t-has-one-of-these-skins",
          "https://phishdestroy.io/steam_dossier/pl/PART2_RESEARCH.md",
          "https://www.reddit.com/r/GlobalOffensive/comments/1h56shi/steam_support_is_stealing_accounts/",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/design-review/part2/quality-review.json",
          "https://phishdestroy.io/steam_dossier/pl/steam_evidence_archive.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/pl/investigation_part2.content.json",
      "export_json_sha256": "b02b18300fea9ad02160da98d464d250f79fb96833af560799d6f222e1308a93"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "pl/legal_analysis.html",
      "language": "pl",
      "title": "Ich warunki, Twoje prawa — Dossier „Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/pl/legal_analysis",
      "source_html_sha256": "3494e2705e26fa39dde0aef893903e6036acf9127cfb435e5aaa7773895b7eab",
      "exported_at": "2026-09-29T00:18:55.112Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "legal_analysis.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/pl/legal_analysis.pdf?v=print-20260929-v5",
        "sha256": "9366f1e5130a2772f423c3382b7887c790021e9a0240dd81a993f6ba6283fd67",
        "bytes": 106966,
        "pages": 8
      },
      "integrity": {
        "signed_object": "legal_analysis.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "legal_analysis.content.json.asc",
        "digest_file": "legal_analysis.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify legal_analysis.content.json.asc legal_analysis.content.json",
          "sha256sum -c legal_analysis.content.json.sha256"
        ]
      },
      "content": {
        "text": "Raport prawny i ekonomiczny\nAnaliza prawna — Warunki korzystania z usługi i zgodność z przepisami\n\nNa ich warunkach. Twoje prawa.\n\nCO WYKAZUJE TA CZĘŚĆ\n\nW niniejszym audycie prawnym o charakterze kryminalistycznym oceniono asymetrię umowną między spółką „Valve” a użytkownikami serwisu Steam w kluczowych jurysdykcjach regulacyjnych. Ustalono w nim, w jaki sposób odwołalna licencja subskrypcyjna pozbawia konsumentów ustawowego prawa własności, przeanalizowano orzecznictwo Europejskiego Trybunału Sprawiedliwości dotyczące wyczerpania praw do odsprzedaży treści cyfrowych oraz zbadano zgodność z przepisami ustawy o usługach cyfrowych (DSA) oraz art. GDPR 15.. Analiza pokazuje, w jaki sposób zautomatyzowane mechanizmy egzekwowania przepisów działają bez możliwości wniesienia merytorycznego odwołania, podczas gdy opłaty rynkowe pobierane przez platformy systematycznie pozbawiają użytkowników wartości ekonomicznej przy każdej transakcji między użytkownikami.\n\n← Powrót do podsumowania dla kadry kierowniczej\n\nW niniejszym raporcie przedstawiono analizę prawną, ekonomiczną i techniczną rozbieżności między deklarowanymi zasadami platformy Steam a sytuacją konsumenta: zautomatyzowane egzekwowanie zasad przy ograniczonych możliwościach odwołania się oraz szeroka kontrola korporacyjna nad zasobami cyfrowymi. Dane liczbowe podano wraz ze źródłem; w przypadku gdy nie udało się ustalić źródła danych, zostały one pominięte.\n\nWektor 1\n\nZastąpienie „własności” licencją odwołalną, tak aby zgodnie z umową można było wycofać aktywa cyfrowe.\n\nWektor 2\n\nZautomatyzowany system egzekwowania przepisów (VACNet), którego blokady, jak podaje dział pomocy technicznej Steam, nie mogą zostać cofnięte.\n\nWektor 3\n\nKontrola kont i aktywów w połączeniu z opłatą rynkową CS2 w ramach programu „15%” (5% Steam + 10% – opłata dla wydawcy), która przy każdej odsprzedaży zmniejsza wartość ekosystemu.\n\nAsymetria terminów\nZrzeczenie się odpowiedzialności i licencja odwołalna\n2.1 Model „subskrypcyjny” a prawa własności\n\nW sekcji „2” umowy abonamentowej serwisu Steam przyznaje się użytkownikom jedynie licencja osobista, niewyłączna, nieprzenoszalna i odwołalna. Zgodnie z umową serwis Valve może w dowolnym momencie zamknąć konta, a niewykorzystane salda w portfelu Steam mogą zostać utracone.\n\n2.2 Iluzja zwrotu pieniędzy a dyrektywa UE w sprawie praw konsumentów\nRamy prawne\tMechanizm zwrotu środków\tOgraniczenie\nEU Consumer Rights Directive\tUnconditional 14-day right of withdrawal on digital content\tWaived if download begins with explicit consumer consent\nSteam SSA\t14 days / under 2 hours played\tValve may deny at its discretion for \"abuse\"\nOcena\n\nValve UE uzależnia ustawowe prawo do odstąpienia od umowy w ciągu 14-dni od własnego terminu „14 dni / w ramach 2 godzin”, na który użytkownik wyraża zgodę w momencie pobrania pliku, zanim będzie mógł zapoznać się z produktem. Polityka ta zawęża — a nie rozszerza — ustawowe prawo; to, czy odbywa się to zgodnie z prawem, jest kwestią do rozstrzygnięcia przez właściwy organ, a nie wnioskiem przedstawionym w niniejszym tekście.\n\nSprawy sądowe\nRynek wtórny i prawo antymonopolowe\nUFC Que Choisir przeciwko „Valve” — Francja\n2019\nSąd w Paryżu: zasada wyczerpania praw ma zastosowanie do gier cyfrowych — odsprzedaż jest zgodna z prawem\nPaździernik 2022\nSąd Apelacyjny w Paryżu uchyla wyrok\n23 Październik 2024\nSąd Kasacyjny (Sąd Najwyższy): gry wideo są „dziełami złożonymi” w rozumieniu dyrektywy InfoSoc, a nie oprogramowaniem. Odsprzedaż cyfrowa zabronione. Obowiązuje zasada „Valve”.\nSprawa antymonopolowa dotycząca firmy Wolfire Games — Stany Zjednoczone (Sprawa antymonopolowa dotycząca firmy „Valve”, nr 2:21-cv-00563)\n\nKlauzula „największego uprzywilejowania” (PMFN) platformy Valve zabrania deweloperom sprzedaży kluczy „Steam” po niższej cenie na jakiejkolwiek innej platformie. Konkurencyjne sklepy — nawet te pobierające prowizję 12% w porównaniu z prowizją Valve wynoszącą 30% — nie mogą przenieść tych oszczędności na konsumentów.\n\n336łączna liczba pracowników firmy „Valve” (2021). Źródło: ujawnione materiały dowodowe.\n79pracownicy zarządzający całą platformą Steam. Źródło: ujawnione materiały dowodowe.\n$3.5Mzysk netto na pracownika. Źródło: ujawnione materiały dowodowe.\n\nZ jawnych akt postępowania dowodowego wynika, że $8.5B przychód brutto w 2021 dotyczącej pracowników 336. The 79-osoba Steam zespół obsługiwało zgłoszenia z serwisu 373,000oraz codzienne zgłoszenia do pomocy technicznej, kierując je do zewnętrznych, zautomatyzowanych centrów obsługi telefonicznej.\n\nJAWNY DOWÓD SĄDOWY · W.D. WASH. SPRAWA NR 2:21-CV-00563Wewnętrzna notatka dotycząca ustaleń\n\nTim Sweeney (dyrektor generalny Epic Games) do Gabe’a Newella: „Dlaczego Steam wciąż pobiera 30% od przychodów brutto, skoro obsługa płatności kosztuje 2–5%, a przepustowość CDN wynosi $0.002/GB? Gdyby odjąć najpopularniejsze gry 25 z Steam, założę się, że Valve osiągnęło większy zysk z większości pozostałych gier 1,000 niż sami twórcy tych gier.”\n\nWewnętrzna wiadomość od Scotta Lyncha (dyrektora operacyjnego, Valve Corporation) do Gabe’a Newella: „Jesteś wkurzony, stary?”\n\nOdpowiedź na zeznanie pod przysięgą (Bloomberg, 2026): Zgodnie z przepisem 30(b)(1) dotyczącym zeznań pod przysięgą Gabe Newell zeznał, że „Valve nie stosuje polityki ani praktyki narzucania cen zewnętrznym twórcom oprogramowania działającym na innych platformach.” Powodowie przedstawili firmie Newell wewnętrzne notatki Valve, które dowodzą aktywnego kontrolowania cen oraz groźb wycofania produktów z oferty skierowanych do deweloperów ustalających niższe ceny w konkurencyjnych sklepach. Pod koniec marca 2026, Sąd Federalny odrzucił wniosek firmy Valve o wydanie wyroku w trybie uproszczonym, kierując sprawę zbiorowego pozwu deweloperów 32,000-do rozpatrzenia przez ławę przysięgłych.\nListopad 2024\n\nZatwierdzono pozew zbiorowy w sprawie ~ Twórcy gry „32,000” który wypłacał prowizje od stycznia 2017, oraz równoległy pozew zbiorowy wniesiony w imieniu konsumentów.\n\nŻądana kwota odszkodowania\n\n$3.1B\nPotrójna kwota zgodnie z amerykańskim prawem antymonopolowym = $9.3B potencjalne narażenie.\n\nCzerwiec 2026: W nowym pozwie zarzuca się firmom Microsoft i Valve zawarcie porozumienia kartelowego mającego na celu ograniczenie konkurencji w dystrybucji gier komputerowych.\n\nPrzestępstwa finansowe i przeciwdziałanie praniu pieniędzy – oficjalne przyjęcie\nValve Oficjalne oświadczenie: Worldwide Fraud Liquidations (28, październik 2019)\n\nW dniu 28 października 2019, Valve oficjalnie zaprzestało handlu oraz odsprzedaży na platformach aukcyjnych nowo zakupionych kluczy do kontenerów w grze Counter-Strike. W swoim oficjalnym oświadczeniu (blog.counter-strike.net/2019/10/26113), firma „Valve” przyznała na piśmie, że stworzona przez nią wirtualna gospodarka stała się międzynarodowym centrum prania brudnych pieniędzy:\n\n„W przeszłości większość transakcji dotyczących kluczy, które obserwowaliśmy, miała miejsce między legalnymi klientami. Jednak ostatnio międzynarodowe sieci oszustów zaczęły wykorzystywać klucze do gry CS:GO do upłynniania swoich zysków. Obecnie uważa się, że niemal wszystkie zakupy kluczy, które ostatecznie trafiają do obrotu lub są sprzedawane na platformie handlowej, pochodzą z oszustw”.\n\nKontekst regulacyjny: Wyznanie to nastąpiło po wystosowaniu przez Komisję ds. Hazardu Stanu Waszyngton (WSGC) formalnego ultimatum wobec serwisu Valve oraz po wydaniu w lipcu przez głównego radcę prawnego serwisu Valve, Karla Quackenbusha, nakazów zaprzestania działalności (2016) skierowanych do domen hazardowych serwisu 23 (w tym CSGO Lotto, CSGOLounge i OPSkins) – dopiero po tym, jak dochodzenie karne w sprawie hazardu zagroziło funkcjonowaniu platformy.\n\nWłaściwość sądowa\nWłaściciel praw w Rosji, z którym użytkownik nie ma możliwości skontaktowania się\n\nUmowa abonamentowa przedstawiValvea jako stronę, która nie ma zbyt wielu zobowiązań i z którą nikt nie może się skontaktować: blokady są trwałe, odwołania są odrzucane, a dostęp jest cofany z całych terytoriów na mocy jednego zdania o „regionach objętych sankcjami”. W przeciwieństwie do tego stanowiska warto zwrócić uwagę na to, jak postępuje Valve, gdy w grę wchodzą jego własne interesy komercyjne w jurysdykcji, którą w innych okolicznościach traktuje jako trudną.\n\nValve v. Touch Skins — roszczenie dotyczące własności intelektualnej przed rozpoczęciem postępowania sądowego, Rosja\n1 wrz2026\nValve za pośrednictwem rosyjskiej kancelarii prawnej Melling, Voitishkin i Partnerzy, wysyła pismo z żądaniem przedprocesowym do operatorów Skórki dotykowe, duży zestaw skórek do CS2, wysłany pocztą rosyjską i e-mailem.\nPodstawy\nTrzy grupy domniemanych naruszeń: wyłączne prawa do oprogramowania; prawa do wyglądu skórek broni, noży i rękawic; oraz znaki towarowe firmy „Valve”. Postępowanie operatorów uznano za umyślne i długotrwałe.\nPopyt\nNależy natychmiast wstrzymać działanie i usunąć całą infrastrukturę — oprogramowanie kod źródłowy, strony internetowe i profile w mediach społecznościowych — w przeciwnym razie firma „Valve” zastrzega sobie prawo do wniesienia pozwu do rosyjskiego sądu w sprawie znaczne odszkodowanie pieniężne oraz skierować sprawę do organy ścigania w celu przeprowadzenia oceny kryminalnej.\nWynik\nPo otrzymaniu listu platforma ogłosiła, że kończy działalność. Jest to pierwszy odnotowany przypadek, w którym firma „Valve” zastosowała środki prawne przeciwko twórcy programu do zmiany wyglądu w Rosji.\n\nInformację tę podał analityk danych Maxim „GabeFollower” Poletaev (X, ~11, wr2026) oraz rosyjska prasa poświęcona grom. Jest to roszczenie przedprocesowe, a nie wniesiony pozew; numer sprawy nie został upubliczniony. Informacja ta jest tutaj traktowana jako doniesienie, a nie jako dokument sądowy. Źródła: dota2.ru zarchiwizowano 2026-09-24 ↗ · Shazoo.\n\nTa sama jurysdykcja, w przeciwnym kierunku\n\nValve nie jest obca rosyjskiemu systemowi prawnemu i regulacyjnemu. Jest to jest zgodny z wymogami Roskomnadzoru: na żądanie organu regulacyjnego usunięto strony społecznościowe 260oraz Steam zawierające treści zabronione, a Roskomnadzor publicznie oświadczył, że strona Steam spełnia wymogi prawne. Rosyjska ustawa o „stronach docelowych” (ustawa federalna 236-FZ, obowiązująca od 2022) nakłada na duże zagraniczne platformy internetowe obsługujące rosyjskich użytkowników obowiązek założenia lokalnego oddziału oraz utworzenia konta kontaktowego w Roskomnadzorze. Valve nie tylko stosuje się do nakazów usunięcia treści wydawanych przez ten organ regulacyjny, ale obecnie również korzysta z pomocy rosyjskich prawników i groźby postępowania przed rosyjskimi sądami, aby chronić swoje skórki jako własność intelektualną.\n\nPlatforma jest więc dostępna, sprawny i stanowczo broni swoich praw, gdy chodzi o jej przychody. Kontrastuje to z sytuacją użytkownika: płacący klient z regionu objętego sankcjami dowiaduje się, że współpraca została zakończona, dostęp do społeczności jest zablokowany do czasu zamknięcia zgłoszenia na stronie 2038,, a nie istnieje żadne forum, na którym można by zakwestionować tę decyzję — „z wielką chęcią przyjęli moje pieniądze i zrealizowali moje transakcje”, przy czym rok wcześniej zatwierdzono zwrot środków na to samo konto z tego samego irańskiego adresu IP (r/pcgaming, 4 2026 sierpnia; kolejne pisma dotyczące egzekwowania przepisów w wystawa poświęcona gospodarce opartej na kartach). „Valve” wykorzystuje cały aparat krajowego systemu prawnego do obrony skórki; nie zapewnia natomiast użytkownikowi, który kupił skórki, żadnej procedury prawnej.\n\nValve traktuje tę samą jurysdykcję jako obszar, w którym może działać i przestrzegać przepisów, ilekroć w grę wchodzą interesy serwisu „Valve” — rosyjscy prawnicy, groźba postępowań przed rosyjskimi sądami, stosowanie się do nakazów usunięcia treści wydanych przez Roskomnadzor — jednocześnie traktując swoje zobowiązania wobec użytkowników tego rynku, jak i każdego innego, jako całkowicie wykraczające poza jakikolwiek proces prawny. Jest podmiotem posiadającym prawa, gdy chodzi o jego przychody, a stroną nieosiągalną, gdy w grę wchodzą prawa użytkowników.\n\nŹródła: TASS (RKN: zgodność z Steam) · Ustawa federalna nr 236-FZ.\n\nOportunizm prawny\nKapitulacja w sprawie klauzuli arbitrażowej\n2023 — atak\n\nKancelarie prawne (Zaiger LLC, Mason LLP) pozyskały tysiące użytkowników za pośrednictwem mediów społecznościowych i złożyły jednocześnie dziesiątki tysięcy indywidualnych wniosków arbitrażowych.\n\nUjawnienie Valve\n\n$225M+\nw postaci bezzwrotnych opłat za wniesienie sprawy do arbitrażu, zanim jakakolwiek sprawa została rozpatrzona co do meritum. Obliczono zgodnie z Regulaminem arbitrażu konsumenckiego Amerykańskiego Stowarzyszenia Arbitrażowego (AAA) oraz Uzupełniającymi załącznikami dotyczącymi arbitrażu masowego. Wnioskodawcy reprezentowani przez kancelarie Zaiger LLC i Mason LLP złożyli około75,000 indywidualnych wniosków o arbitraż przeciwko spółce Valve Corp. (równolegle do roszczeń antymonopolowych w sprawie Wolfire Games LLC i inni przeciwko Valve Corp., sprawa nr 2:21-cv-00563-JCC, W.D. (Waszyngton). Zgodnie z cennikiem opłat konsumenckich AAA pozwany przedsiębiorca uiszcza bezzwrotne opłaty administracyjne związane z prowadzeniem sprawy oraz kaucje za wyznaczenie arbitra w wysokości około $3,000+ za każdą indywidualną sprawę (75,000 zgłoszeń × $3,000 = około $225mln w ramach z góry naliczanych zobowiązań proceduralnych). Zobacz raporty prawne Bloomberg Law i Reuters dotyczące ryzyka związanego z masowymi postępowaniami arbitrażowymi w branży technologicznej (2023–2024).\n\nOkres\tMechanizm rozstrzygania sporów w ramach SSA\tZaobserwowany efekt\tWynik\nBefore Sep 2024\tMandatory individual arbitration + class-action waiver\tIndividual litigation becomes economically irrational for users\tMass arbitration → $225M fee threat\nAfter Sep 2024\tDisputes in King County, WA courts only\tArbitration costs are avoided; cases consolidate in a single forum\tClass actions now possible\nWnioski\n\nPrzez ponad dziesięć lat SSA wymagała od użytkowników zrzeczenia się prawa do procesu przed ławą przysięgłych na rzecz indywidualnego postępowania arbitrażowego. Gdy masowe wnioski o arbitraż sprawiły, że mechanizm ten stał się finansowo kosztowny dla Valve, przepisy SSA zostały zmienione tak, aby spory kierować do sądów hrabstwa King. Zmiana ta została wprowadzona bez znaczącej możliwości rezygnacji; alternatywą dla jej akceptacji była utrata dostępu do zakupionych zasobów cyfrowych poprzez usunięcie konta.\n\nEgzekwowanie przepisów oparte na algorytmach\nVACNet, domniemanie winy i wyniki fałszywie dodatnie\nPaździernik 2023 — AMD Anti-Lag+\n\nAktualizacja sterownika AMD (wersja 23.10.1) aktywowała w grze CS2 funkcję Anti-Lag+, która przechwytywała funkcje bibliotek DLL gry. System VAC uznał to za wstrzyknięcie kodu oszukańczego i nałożył dożywotnie blokady na tysiące uczciwych użytkowników, zanim w sprawę wkroczyła organizacja „Valve”.\n\nGrudzień 2023 — wysoka rozdzielczość (DPI)\n\nGracze, u których wartość DPI przekraczała 10,000 i którzy gwałtownie obracali kamerę, zostali na stałe zablokowani. System VACNet nie był w stanie odróżnić fizycznego ruchu myszy od oszustwa typu „spinbot”.\n\nKategoria pomocy technicznej\tDeklarowany czas reakcji\tRzeczywisty wynik\nRefund requests\t50 min – 1.5 hr\tAutomatic approval (<14 days, <2 hours played)\nAccount security / recovery\t3–12 hours\tDepends on documentation provided\nContesting a VAC ban\tForm response\tComplete refusal. Support cannot reverse VAC decisions. The ban is permanent.\nOficjalna polityka firmy „Valve”\n\n„Zakazy VAC mają charakter stały, nie podlegają negocjacjom i nie mogą zostać zniesione przez dział wsparcia Steam.”\n\nTen sam kanał pomocy technicznej, w ramach którego ogłoszono blokadę, przekazuje również informację o odmowie ponownego rozpatrzenia sprawy: Steam Dział pomocy technicznej oświadcza, że nie może cofnąć decyzji VAC. Dla użytkownika werdykt algorytmu stanowi ostateczny wynik.\n\nEkonomiczne aspekty odsprzedaży\nKontrola nad aktywami wirtualnymi oraz opłata za odsprzedaż\nOpłata rynkowa za pakiet „15%” CS2 — wartość ubywa przy każdej odsprzedaży\nIteracja\tSaldo kupującego\tSprzedający otrzymuje\t„Burned” (15%)\n1\t$100.00\t$85.00\t$15.00\n2\t$85.00\t$72.25\t$12.75\n3\t$72.25\t$61.41\t$10.84\n10\t$23.16\t$19.68\t~$3.47\nTotal\t$100 → dust\tValve collects the 15% fee on each resale. Users must add new money to keep trading.\nZmiana zasad wymiany sprzętu w programie CS2 — październik 2025\n\nBez wcześniejszego ostrzeżenia firma „Valve” zmieniła zasady umowy wymiany w grze CS2, umożliwiając gwarantowane nabycie rzadkich noży i rękawic w zamian za przedmioty klasy „Covert”. Ceny noży spadły, ceny przedmiotów klasy „Covert” gwałtownie wzrosły, a na całym rynku nastąpiła paniczna wyprzedaż.\n\nFirma Valve powołuje się na sekcję 7 ustawy SSA — brak odpowiedzialności za zmiany zasad platformy. Użytkownicy ponoszą ryzyko w gospodarce, której zasady Valve mogą ulec zmianie bez uprzedzenia i bez odszkodowania. Wielkość zgłoszonej straty w skali całego rynku jest przedmiotem sporów i nie została tutaj podana z powodu braku źródła pierwotnego.\n\nReakcja organów regulacyjnych w Europie\nUOKiK, DSA oraz ustawa o sprawiedliwości cyfrowej\nUOKiK — Polska, maj 2024\n\nPolski Urząd Ochrony Konkurencji i Konsumentów (UOKiK) wszczął formalne postępowanie antymonopolowe przeciwko firmie „Valve” oraz pięciu krajowym wydawcom i dystrybutorom gier w związku z domniemanym ustalaniem cen, restrykcyjnymi klauzulami o równości cen oraz praktykami blokowania geograficznego, które spowodowały, że polscy konsumenci płacili za gry cyfrowe nawet o 20% więcej niż na sąsiednich rynkach EOG. W ramach postępowania antymonopolowego inspektorzy UOKiK oraz policja przeprowadzili naloty o świcie i oględziny dowodów w polskich siedzibach krajowych wydawców i dystrybutorów będących partnerami (nie w oddziałach spółki zależnej „Valve”, ponieważ „Valve” nie posiada podmiotu w Polsce). Potencjalna grzywna ustawowa: do 10% rocznego obrotu. Źródło: Oficjalny komunikat UOKiK: „Prezes UOKiK wszczął postępowanie przeciwko Valve oraz twórcom gier”, maj 2024.\n\nUstawa o usługach cyfrowych (DSA)\n\nWymaga przejrzystości w zakresie automatycznej moderacji. Serwis Steam nie publikuje danych dotyczących wyników fałszywie pozytywnych ani fałszywie negatywnych w systemie VACNet, a w jego kanale pomocy technicznej podano, że decyzji VAC nie można cofnąć.\n\nUstawa o sprawiedliwości cyfrowej — 2026\n\nPrzewidywane przepisy: stały dostęp do treści płatnych, zakaz stosowania nieuczciwych praktyk (tzw. „dark patterns”) w momencie zrzeczenia się praw, uznanie praw własności do aktywów cyfrowych oraz ochrona przed trwałym zajęciem zasobów.\n\nWnioski\nUstalone rozbieżności między przepisami a stanem faktycznym\n1\n\nRóżnica w strukturze własnościowej. Użytkownicy płacą pełną cenę za licencję, którą na mocy umowy serwis Valve może cofnąć. Francuski Sąd Najwyższy (październik 2024) orzekł, że odsprzedaż cyfrowa nie podlega ochronie, nadając temu stanowisku moc prawną.\n\n2\n\nEgzekwowanie przepisów za pomocą algorytmów. System VACNet nałożył niesłuszne blokady (sterowniki AMD, przypadki wysokiego DPI). Dział pomocy technicznej Steam informuje, że nie może cofnąć decyzji VAC, więc ostateczną decyzję podejmuje algorytm.\n\n3\n\nOszczędność opłat. Opłata rynkowa serwisu „15%” CS2 (5% Steam + 10% – opłata dla wydawcy) obniża wartość przy każdej odsprzedaży, a zasady platformy mogą ulec zmianie bez uprzedzenia; zgodnie z umową SSA serwis Valve nie ponosi odpowiedzialności za takie zmiany.\n\n4\n\nUsunięto klauzulę arbitrażową. We wrześniu SSA zrezygnowała z obowiązkowego arbitrażu 2024, po tym, jak masowe wnioski naraziły Valve na opłaty w wysokości około225mln dolarów. Użytkownicy nie mieli żadnej realnej możliwości rezygnacji z tej zmiany.\n\n5\n\nJurysdykcja selektywna. Valve zatrudniła rosyjską kancelarię prawną (Melling, Voitishkin & Partners) i zagroziła wszczęciem postępowania sądowego w Rosji przeciwko Touch Skins, jednocześnie traktując swoje zobowiązania wobec użytkowników tego samego rynku jako wykraczające poza jakikolwiek proces sądowy. Firma „Valve” występuje jako podmiot posiadający prawa, gdy w grę wchodzą jej interesy handlowe, a jako strona nieosiągalna, gdy chodzi o prawa użytkowników.\n\n← Część I: Omijanie blokad serwerów proxy i hazardCzęść II: Dostęp i odpowiedzialność →\n\nŹródła prawne i akta spraw są cytowane z podaniem oryginalnych wydawców i miejsc przechowywania. Nie rości się sobie żadnych praw własności do dokumentów, na których opierają się te informacje.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Analiza prawna — Warunki korzystania z usługi i zgodność z przepisami"
          },
          {
            "level": 2,
            "id": null,
            "text": "Zrzeczenie się odpowiedzialności i licencja odwołalna"
          },
          {
            "level": 3,
            "id": null,
            "text": "2.1 Model „subskrypcyjny” a prawa własności"
          },
          {
            "level": 3,
            "id": null,
            "text": "2.2 Iluzja zwrotu pieniędzy a dyrektywa UE w sprawie praw konsumentów"
          },
          {
            "level": 2,
            "id": null,
            "text": "Rynek wtórny i prawo antymonopolowe"
          },
          {
            "level": 3,
            "id": null,
            "text": "UFC Que Choisir przeciwko „Valve” — Francja"
          },
          {
            "level": 3,
            "id": null,
            "text": "Sprawa antymonopolowa dotycząca firmy Wolfire Games — Stany Zjednoczone (Sprawa antymonopolowa dotycząca firmy „Valve”, nr 2:21-cv-00563)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve Oficjalne oświadczenie: Worldwide Fraud Liquidations (28, październik 2019)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Właściciel praw w Rosji, z którym użytkownik nie ma możliwości skontaktowania się"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve v. Touch Skins — roszczenie dotyczące własności intelektualnej przed rozpoczęciem postępowania sądowego, Rosja"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ta sama jurysdykcja, w przeciwnym kierunku"
          },
          {
            "level": 2,
            "id": null,
            "text": "Kapitulacja w sprawie klauzuli arbitrażowej"
          },
          {
            "level": 2,
            "id": null,
            "text": "VACNet, domniemanie winy i wyniki fałszywie dodatnie"
          },
          {
            "level": 2,
            "id": null,
            "text": "Kontrola nad aktywami wirtualnymi oraz opłata za odsprzedaż"
          },
          {
            "level": 3,
            "id": null,
            "text": "Opłata rynkowa za pakiet „15%” CS2 — wartość ubywa przy każdej odsprzedaży"
          },
          {
            "level": 3,
            "id": null,
            "text": "Zmiana zasad wymiany sprzętu w programie CS2 — październik 2025"
          },
          {
            "level": 2,
            "id": null,
            "text": "UOKiK, DSA oraz ustawa o sprawiedliwości cyfrowej"
          },
          {
            "level": 2,
            "id": null,
            "text": "Ustalone rozbieżności między przepisami a stanem faktycznym"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/pl/#briefing-heading",
          "https://dota2.ru/news/67707-valve-cerez-uristov-napravila-krupnoj-rossijskoj-skincendzer-platforme-trebovanie-o-prekrasenii-deatelnosti/",
          "http://web.archive.org/web/20260924181657/https://dota2.ru/news/67707-valve-cerez-uristov-napravila-krupnoj-rossijskoj-skincendzer-platforme-trebovanie-o-prekrasenii-deatelnosti/",
          "https://shazoo.ru/2026/09/12/190508/valve-cerez-rossiiskix-iuristov-dobilas-zakrytiia-krupnogo-skinceindzera-dlia-cs2",
          "https://www.reddit.com/r/pcgaming/comments/1vf24lu/warning_to_all_gamersexpats_steam_took_my_money/",
          "https://phishdestroy.io/steam_dossier/pl/card_economy.html#asymmetry",
          "https://tass.ru/obschestvo/23235387",
          "https://base.garant.ru/401414628/",
          "https://uokik.gov.pl/postepowanie-wyjasniajace-w-sprawie-valve-i-dystrybutorow-gier",
          "https://phishdestroy.io/steam_dossier/pl/",
          "https://phishdestroy.io/steam_dossier/pl/investigation_part2.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/pl/legal_analysis.content.json",
      "export_json_sha256": "3a2bfba12e94160f6238966af755084df1be693c9788baf0ef72e0ce63d006ff"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "pl/license_disclaimer.html",
      "language": "pl",
      "title": "Licencja · Prawa · Zastrzeżenia — PhishDestroy",
      "source_url": "https://phishdestroy.io/steam_dossier/pl/license_disclaimer",
      "source_html_sha256": "a3f47627335ec6bc914cb958faaedba2a151b1909097fcea64b768131d9fd32f",
      "exported_at": "2026-09-29T00:18:55.596Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "license_disclaimer.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/pl/license_disclaimer.pdf?v=print-20260929-v5",
        "sha256": "755207711b03185bee953457a82abd0be1b64eb930e22660cbecee2ec56159a0",
        "bytes": 122334,
        "pages": 11
      },
      "integrity": {
        "signed_object": "license_disclaimer.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "license_disclaimer.content.json.asc",
        "digest_file": "license_disclaimer.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify license_disclaimer.content.json.asc license_disclaimer.content.json",
          "sha256sum -c license_disclaimer.content.json.sha256"
        ]
      },
      "content": {
        "text": "PHISHDESTROYBadania kryminalistyczne · Valve / Steam\nLicencja · Prawa · Wyłączenie odpowiedzialności\nLicencja i zastrzeżenia prawne — Przekazanie do domeny publicznej\n\nWszelkie prawa poddał się ludzkości.\n\nCO WYKAZUJE TA CZĘŚĆ\n\nNiniejszy dokument ustanawia bezwarunkowe przekazanie do domeny publicznej (CC0 1.0 Universal) oraz warunki licencji oprogramowania MIT regulujące korzystanie z zbioru danych „PhishDestroy” (Steam). Wszystkie ustalenia kryminalistyczne, zbiory danych dowodowych, wykresy sieciowe oraz metodyki analityczne zostają nieodwołalnie przekazane do domeny publicznej w celu nieograniczonego wykorzystania w celach regulacyjnych, prawnych i naukowych na całym świecie.\n\n← Powrót do podsumowania dla kadry kierowniczej\n\nPhishDestroy zrzeka się wszelkich praw do tego materiału — prawa do jego powielania, sprzedaży czy umieszczania na nim swojego nazwiska. Poniżej znajdują się dwa dokumenty ujęte w jedną formę: list otwarty do serwisu Valve, napisany w naszym naturalnym stylu, oraz formalne oświadczenie o zrzeczeniu się praw, sporządzone z myślą o organie, który zajmie się dalszym wykorzystaniem tej treści.\n\nDochodzenie · Valve Corporation / SteamWersja publiczna — bez terminu ważności, bez możliwości cofnięcia\nZNIESIONO\nCzęść ILicencja — sama część prawna, ale z ludzkiego punktu widzenia\n\nPhishDestroy zrzeka się wszelkich praw do tego materiału. Zero. Koniec. Sprawa zamknięta. Możesz go powielać, sprzedawać, podpisać się pod nim, wytatuować go swojemu szefowi – cokolwiek chcesz. Nie musisz podawać źródła, nie musisz wysyłać prywatnej wiadomości, nie oczekuję kartki z podziękowaniami.\n\nJedna konkretna zasada (tak, tylko jedna)\n\nTo NIE TY decydujesz, czy jesteś terrorystą.\n\nJeśli jesteś użytkownikiem z Rosji lub z jakiegokolwiek kraju objętego sankcjami OFAC — ten materiał NIE jest dla Ciebie. Nie ma żadnych luk prawnych. Ciesz się sankcjami.\n\nA jeśli zmieniłeś region w serwisie „Steam” na Turcję, siedząc w Moskwie — gratuluję kreatywnego podejścia do geografii. Nadal jesteś Rosjaninem. Sankcje nadal obowiązują. I właśnie o to chodzi.\n\nCzęść IICzym to jest i dlaczego istnieje\n\nOpublikujemy więcej informacji o „Valve” niż przeciętny pracownik „Valve” wie o sobie samym. To nie jest przechwałka. Po prostu tak się złożyło.\n\nJak do tego doszło? Zabawna historia: to w zasadzie „Steam” nas stworzyło. Wychowało nas na swoich oszustach, zgłoszeniach do pomocy technicznej i ekosystemie obejścia blokad — i oto jesteśmy. Nie mamy żalu. To właściwie dość poetyckie.\n\nDla tych, którzy jeszcze nie zapoznali się z historią powstania tej sprawy — mieliśmy już okazję poznać niezwykle kosztownych europejskich prawników firmy „Valve” (Taylor Wessing, skoro już o tym mowa):\n\nhttps://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d zarchiwizowano 2026-08-21 ↗\n\nUrocze spotkanie. Zwłaszcza biorąc pod uwagę ich stawkę godzinową.\n\nCzy firma „Valve” o tym wiedziała? Tak. Czy firma „Taylor Wessing” o tym wiedziała? Prawie na pewno tak. Ale kiedy jest się aż tak bogatym, przepisy prawne to raczej kwestia nastawienia niż obowiązek, prawda?\n\nWłaściwie to w sumie cała odpowiedź.\n\nSteam przez lata zajmowaliśmy się tropieniem oszustów. Nie zawsze celowo — czasami oszuści po prostu zostawiali na sobie ślady „Valve” przez samo powiązanie z nami. Nie staramy się tu dramatyzować. Staramy się być precyzyjni. Szczerze mówiąc, jest to dla nas trudniejsze niż dramatyzowanie — po prostu tak piszemy.\n\nCzy to jest konflikt?\n— Nie.\n\nCzy da się to rozwiązać?\n— Tak. Ale nie podpisujemy żadnej umowy o zachowaniu poufności i nie bierzemy udziału w programach nagród za wykrycie błędów za grosze.\n\nCzekaliśmy ponad 4 lat, aż naprawią problem z podszywaniem się, zanim mogliśmy o tym napisać publicznie. Gdybyśmy bowiem napisali o tym wcześniej, Steam przybrałoby minę ofiary i krzyczało „aktywne zagrożenie!”, oferując nam grosze w zamian za podpisanie dokumentu, który uczyniłby nas ich własnością na zawsze. Nie, dziękujemy.\n\n(A poza tym: sama firma „Valve” narusza umowę o zachowaniu poufności. Robią to jej własni pracownicy – ci z najwyższych szczebli. Ale oczywiście, porozmawiajmy o naszych.)\n\nCzęść IIIList otwarty do Valve — serio, przeczytaj to\n\nValve: jeśli chcesz, aby ta domena została usunięta, napisz do nas. Do tej rozmowy nie jest potrzebny zewnętrzny doradca prawny.\n\nDla niewtajemniczonych: dr Patrick posiada tytuł magistra prawa w zakresie międzynarodowego prawa handlowego uzyskany na Uniwersytecie w Aberdeen oraz — uwaga — napisał swoją pracę doktorską właśnie z zakresu prawa informatycznego. Niedawno został partnerem w kancelarii Taylor Wessing, której cały model biznesowy polega na naliczaniu firmom takim jak Valve niebotycznych kwot za przeciąganie spraw do momentu, aż drugiej stronie skończą się pieniądze lub cierpliwość.\n\nNie mamy mu tego za złe. Bogaci klienci z poczuciem winy, którzy płacą za godzinę — to dobry ruch zawodowy. Po prostu uważamy, że nie powinieneś tego finansować.\n\nUmowa (oferta otwarta, bez udziału prawników)\n\nDomena to jedyna rzecz, do której serwis Valve ma realną szansę dotrzeć. Dochodzenie, skierowania i powiązane zasoby są już w toku — będą kontynuowane niezależnie od tego, czy domena zostanie zdobyta, czy nie.\n\nJeśli chcesz zarejestrować domenę:\n\nPozwól, aby Twoi specjaliści ds. prawa informatycznego ustalili uczciwą cenę.\n\n50% trafia do Fundacji „SEAL”.\n\nLikwidujemy domenę. Bez zamieszania. Bez sądu. Sprawa załatwiona.\n\nTo nie jest groźba. To prosta propozycja dotycząca jedynej rzeczy, która faktycznie jest w zasięgu ręki. W żaden inny sposób tego nie zdobędziesz — taka po prostu jest natura tej sytuacji.\n\nCzy „zaszkodzimy” bezpośrednio organizacji „Valve”? Prawdopodobnie nie w sposób, który odczuli by finansowo. Nie mamy złudzeń. Ale zrobimy to uczciwie, otwarcie, bez dążenia do zdobycia wpływów — bo nie potrzebujemy wpływów. Chcemy, by świat dostrzegł to, co zawsze było widoczne dla wszystkich, jeśli tylko poświęciło się wystarczająco dużo czasu na przyjrzenie się temu.\n\nMamy archiwa z5-letnim okresu. To, co prawnicy serwisu Valve ujawnili w ramach postępowania dowodowego — dane, do których dostęp mają agenci, odciski palców, dokumentacja, którą dosłownie nam przekazali — wystarczy. Nie musimy ujawniać tego w surowej postaci.\n\nKto co dostaje\n\nOrgany regulacyjne otrzymują oryginały.\n\nNaukowcy i dziennikarze otrzymują wersje z usuniętymi fragmentami (zeznania ofiar, dane logowania dzieci oraz urocze komentarze działu pomocy technicznej serwisu „Valve” zostały usunięte z oczywistych powodów).\n\nWśród kont, których dotyczyła ta sytuacja, znalazły się konta nieletnich, którzy nie zostali o tym poinformowani. Ustalenie to znajduje się w pakiecie dokumentów przygotowanym dla organu regulacyjnego, z którego usunięto zgłoszenia ofiar oraz dane uwierzytelniające, ponieważ kwestia ta powinna zostać rozpatrzona przez organ ds. ochrony danych, a nie poruszana w artykule.\n\nPoza tym, Valve — chcemy coś wyjaśnić, zanim zdecydujesz, jak to rozegrać: PhishDestroy to społeczność, a nie konkretna osoba. Przekonałeś się o tym, gdy skierowałeś korespondencję prawną do społeczności, nie zadając sobie nawet trudu, by z nią porozmawiać — po prostu wykorzystałeś ją do zebrania danych i zablokowałeś konta.\n\nSpołeczność nie ma żadnego konfliktu z serwisem Valve. Nie szukaliśmy tego. To oszuści, których wy wyhodowaliście, nas znaleźli. Zablokowaliśmy ich. I oto jesteśmy.\n\nSekcja III-BZasoby sojusznicze — uwaga skierowana konkretnie do Steam\n\nChcemy otwarcie mówić o strukturze wzmocnienia, ponieważ udawanie, że ona nie istnieje, byłoby nieuczciwe.\n\nZ tego, co wiemy o sytuacji w społeczności, serwis PhishDestroy dysponuje co najmniej dwoma sprzymierzonymi źródłami, które przejmą ten materiał i zajmą się nim.\n\nCo to oznacza w praktyce:\n\nKażdy z nich podchodzi do tych samych zagadnień z własnej perspektywy.\n\nSą niezależni — nie kierują się naszymi wskazówkami, a my nie kierujemy się ich. Ten sam ogólny temat, inna metodologia.\n\nNIE będą podejmować działań w części „1.”. Są pod obserwacją.\n\nJeśli serwis „Valve” zdecyduje się nie usunąć tej strony:\n\nMożna się spodziewać, że pojawią się po części „2” lub „3.”\n\nWykorzystają to, co przydatne z naszej pracy, uzupełnią to własnymi materiałami i opublikują pod własnym nazwiskiem.\n\nWłaśnie do takich sytuacji została stworzona licencja opisana w sekcji 1: materiał trafia tam, gdzie powinien, jest uzupełniany i rozbudowywany — a ani my, ani oni nie jesteśmy sobie wzajemnie zobowiązani do podawania źródła.\n\n(PS dla prawników zastanawiających się nad łańcuchami odpowiedzialności: nie ma żadnych. Te źródła nie otrzymują od nas żadnych wytycznych, finansowania ani danych. Korzystają z informacji dostępnych publicznie i wyciągają własne wnioski. Tak samo jak wy moglibyście to zrobić.)\n\nNie mówimy tego po to, by kogokolwiek zastraszyć. Mówimy to po to, aby osoba odpowiedzialna za strategię po stronie „Valve” dysponowała rzetelnymi informacjami na temat tego, jak faktycznie wygląda sytuacja informacyjna.\n\nJednym ze źródeł, które czerpie z naszych materiałów i je uzupełnia, może być artykuł. Dwa źródła, które robią to niezależnie od siebie i dochodzą do podobnych wniosków, to już wzorzec. Właśnie na takie wzorce zwracają uwagę organy regulacyjne.\n\nCzęść IVPieniądze, zakazy, cały ten cyrk\n\nRzecz w tym, że w przypadku „Steam” blokowanie stron hazardowych i oszustów nie ma nic wspólnego z egzekwowaniem prawa. Chodzi tu o pozyskiwanie dochodów. Valve zgarnia pieniądze, myje ręce, a potem wychodzi na scenę i opowiada wszystkim wzruszającą historię o kartach Pokémon i baseballu.\n\nW przypadkach, w których udokumentowano nadużycia po stronie pomocy technicznej — w tym pisemne przyznanie się serwisu „Valve” z lutego 2023 do odpowiedzialności za naruszenie bezpieczeństwa kont o wysokiej wartości w wyniku zgłoszeń o pomoc, a także zwolnienia pracowników podwykonawców, o których poinformowały serwisy Dexerto i Escorenews w związku z aferą dotyczącą wykorzystywania informacji poufnych o wartości320k (Część II §04 · Główna sekcja §14.1) — opierają się one na opublikowanych przyznaniach i reportażach śledczych. Niepotwierdzone pogłoski o tym, że pracownicy pomocniczy prowadzą nielegalną działalność hazardową lub pobierają prowizję za zniesienie blokad, nie znalazły potwierdzenia w publicznie dostępnych źródłach i nie zostały uwzględnione w niniejszym artykule.\n\nTymczasem firma „Valve” zablokowała możliwość prawidłowego śledzenia skórek na stronie 2017.. Omówiono to nawet na ich własnych forach. Nazwali to „środkami przeciwko hazardowi” — podczas gdy ekosystem hazardu związanego ze skórkami przez kolejne lata nadal przepuszczał miliardy przez infrastrukturę Steam. Świetny wizerunek marki.\n\nUdowodnimy, że:\n\nSkiny zapewniają większą anonimowość niż Monero\n\nPeruwiański kartel rzekomo wykorzystywał skórki z gry „Dota2” do transferu środków pieniężnych\n\nSteam jest to w praktyce urządzenie służące do obchodzenia sankcji, warte około7B w „kartach kolekcjonerskich” (tak, naprawdę powiedzieli prokuratorowi, że to karty kolekcjonerskie)\n\nMamy filmik na temat tych skórek. Zobaczysz go.\n\nWiemy również, że:\n\nNa moderację serwisu Reddit wpływ ma Valve\n\nInfrastruktura danych firmy Steam należąca do podmiotów zewnętrznych (takich jak steamid.uk) jest prowadzony przez osobę prywatną (msart), którego powiązanym projektem jest lista zakazanych kart (steambans.com archiwum) jest współzarządzany przez zatwierdzonego moderatora społeczności „Valve” (killahinstinct_) — co sprawia, że niezależna kontrola blokad na platformach pozostaje całkowicie w gestii organizacji „Valve” (zob. „Card Economy”, §08)\n\nTo, czego nie potrafią kontrolować, zakazują\n\nValve: jeśli nadal będziesz udawać, że nic nie wiesz — nie ma sprawy. Twoja „bezpieczna przystań” została odnotowana. Google Analytics i tak anonimizuje adresy IP twoich użytkowników. Widzimy, co jest usuwane. Po prostu nie możemy tego udowodnić na tyle tanio, żeby twoi prawnicy się tym zainteresowali. Jeszcze.\n\nSekcja VSprawa z złośliwym oprogramowaniem — tak, wspominamy o tym\n\nPowiedzmy to bez ogródek, jeśli chodzi o kolejność wydarzeń, bo to dokładnie pokazuje, kim jesteś.\n\nNIE ujawniamy publicznie tej luki w zabezpieczeniach gry. NIE zgłaszamy jej do programu Steam. Program ten wymaga podpisania umowy o zachowaniu poufności, a jej podpisanie uniemożliwiłoby nam poinformowanie użytkowników, których to dotyczy, o tym, co stało się z ich kontami. Celem tej pracy jest właśnie ujawnienie informacji osobom, które straciły te konta, oraz organom regulacyjnym; umowa o zachowaniu poufności jest z tym sprzeczna.\n\nOto, co faktycznie się wydarzyło: ta luka w zabezpieczeniach jest praktycznie tajemnicą poliszynela w odpowiednich kręgach. Wiemy na pewno, że niezależni badacze zajmujący się bezpieczeństwem już dawno rzucili firmie Steam Support pełny kod exploita prosto w twarz. Ta część jest już za nami. Zostaliście oficjalnie ostrzeżeni za pośrednictwem waszych własnych, sterylnych kanałów.\n\nA co zrobiła firma „Valve”? Absolutnie nic. Ponieważ dla Valve bezpieczeństwo nie oznacza zysku — wręcz przeciwnie. Bezpieczeństwo to źródło kosztów. Dopóki zagrożenie nie osiągnie masy krytycznej i nie spowoduje katastrofalnego załamania wizerunku firmy w oczach opinii publicznej, Valve nie traktuje go jako sprawy pilnej.\n\nWięc co robimy? Informujemy opinię publiczną o tym, że to istnieje, ponieważ stwierdzenie „Valve wie o systemowym zagrożeniu ze strony złośliwego oprogramowania i świadomie decyduje się nie podejmować żadnych działań” stanowi kluczową informację dla organów regulacyjnych, które obecnie to czytają.\n\nTa gra jest naprawdę ogromna. Nie podamy tutaj jej nazwy. Ale musicie zrozumieć jedno:\n\nTo NIE jest ten banalny śmieć typu „script-kiddie” z CS:GO, w którym serwer prosi cię o „zainstalowanie sterownika”. To katastrofa.\n\nTo koszmar na miarę gry „Unturned”: atak RCE typu „zero-click” przy łączeniu się z serwerem. Dołączasz do serwera. Nic nie klikasz. Niczego nie pobierasz. Samo połączenie stanowi powierzchnię ataku, a twój komputer zostaje całkowicie przejęty. Spójrzmy prawdzie w oczy: umieszczenie kodu umożliwiającego zdalne wykonanie kodu (RCE) i ominięcie lokalnych programów antywirusowych poprzez wykorzystanie zaufanych certyfikatów cyfrowych serwisu Valve nie jest już nawet nowością na stronie Steam. Jest to praktycznie wbudowana funkcja twojego ekosystemu.\n\nValve wie już, że coś takiego istnieje. Jednak firma ta opiera się na swojej ulubionej, tchórzliwej luce prawnej: ponieważ gra została technicznie opracowana przez podmiot zewnętrzny, Valve umywa ręce. Firma ta zajmuje się dystrybucją gry, przetwarzaniem płatności oraz hostingiem infrastruktury, ale kiedy luka typu zero-click RCE zagraża milionom jej użytkowników, jej stanowisko brzmi: „To nie nasza gra, więc nie ponosimy za nią odpowiedzialności”.\n\nKiedy ta sprawa nieuchronnie wybuchnie, winę poniesie zewnętrzny deweloper, a „Valve” wywinie się, udając odpowiedzialną platformę, która „pomogła” w rozwiązaniu problemu. Klasyczne tchórzostwo w stylu „Valve”. Znamy już ten schemat.\n\nChcemy to oficjalnie odnotować, aby organy regulacyjne, prokuratorzy i dziennikarze dokładnie zrozumieli, w jaki sposób firma „Valve” postępuje z aktywnym złośliwym oprogramowaniem: chowając się za zewnętrznymi programistami, stosując klauzule poufności (NDA) uniemożliwiające ujawnianie informacji oraz pozostawiając graczy bezbronnymi.\n\nKoniec listu otwartegoRozpoczyna się część oficjalna\nStyl formalny · dla organu władzy\nOświadczenieW kwestii użytkowania i praw\n\nPhishDestroy Koalicja ds. Projektów i Cyberbezpieczeństwa\n\nNiniejsze oświadczenie towarzyszy każdemu zgłoszeniu i każdemu dowodowi zawartemu w niniejszym pakiecie materiałów. Jest ono skierowane do wszelkich organów, sądów, organów regulacyjnych, prokuratorów, badaczy, dziennikarzy lub osób, których sprawa dotyczy, do których trafią te materiały.\n\n1. Nie ma żadnych warunków dotyczących użytkowania\n\n1.1 Wszystkie materiały opracowane przez Koalicję w ramach niniejszego wniosku — stwierdzenia faktów, analiza, sporządzone przez nią załączniki, narzędzia oraz ustalenia — są udostępniane BEZ ZASTRZEŻENIA JAKICHKOLWIEK PRAW.\n\n1.2 Każdy może, bez pytania i bez powiadamiania nas:\n\npowielać go w całości lub w części;\n\ndostosowywać, edytować, przerabiać, zmieniać strukturę lub poprawiać;\n\nprzetłumacz to;\n\ncytować ten fragment bez zaznaczenia, że jest to fragment;\n\nwłączać je do oficjalnych dokumentów, ustaleń, decyzji, pism procesowych, sprawozdań lub materiałów prasowych;\n\nprzedstawiać to jako własną pracę odbiorcy lub jego własne ustalenia;\n\nwykorzystać to jako surowiec, a resztę wyrzucić;\n\ni przekazać ją komukolwiek innemu na tych samych warunkach.\n\n1.3 PODANIE ŹRÓDŁA NIE JEST WYMAGANE I NIE JEST ŻĄDANE. Nie ma potrzeby wymieniania Koalicji, powoływania się na nią, przypisywania jej zasług, składania jej podziękowań, konsultowania się z nią ani informowania jej. Jeśli materiały zawarte w niniejszym odesłaniu okażą się pomocne dla organu władzy, a Koalicja nie zostanie w ogóle wspomniana, BĘDZIE TO CAŁKOWICIE ZADOWALAJĄCY WYNIK, o czym Koalicja informuje z wyprzedzeniem, aby nie musiało się pojawiać żadnych wątpliwości w tej kwestii.\n\n1.4 Jeśli natomiast dana instytucja uzna, że wygodniej jest powołać się na Koalicję jako źródło, może to zrobić. Wybór należy wyłącznie do odbiorcy i żadne z tych rozwiązań nie pociąga za sobą żadnych konsekwencji.\n\n1.5 Niniejszy dokument stanowi ZRZECZENIE SIĘ, a nie ofertę udzielenia licencji. Nie wymaga on akceptacji, nie nakłada żadnych zobowiązań i nie może zostać naruszony. Oprogramowanie opublikowane przez Koalicję jest udostępniane oddzielnie na licencji MIT; wyniki badań i ustalenia są udostępniane w domenie publicznej w najszerszym dopuszczalnym zakresie, a w przypadku gdy jurysdykcja nie zezwala na zrzeczenie się praw, Koalicja udziela nieodwołalnej, ogólnoświatowej, bezpłatnej licencji o tym samym skutku.\n\n2. Dlaczego ma to znaczenie w praktyce, a nie tylko z grzeczności\n\n2.1 Organ może mieć uzasadnione wątpliwości co do tego, czy powinien opierać się na materiałach dostarczonych przez stronę zewnętrzną, obawiając się, że może to sprawiać wrażenie, jakby działał na zlecenie tej strony, lub że może dojść do pewnego uwikłania w sprawy tej strony.\n\n2.2 NIE MA TU NICZEGO, CO MOGŁOBY BYĆ PRZYCZYNĄ KONFLIKTU. Koalicja niczego nie żąda, nie jest jej nic winna, niczego nie zachowuje i nie ma żadnych oczekiwań. Nie może ona później dochodzić żadnych praw, przypisywać sobie zasług, skarżyć się na niewłaściwe wykorzystanie ani zgłaszać zastrzeżeń co do sposobu przedstawienia materiału, ponieważ nie zachowała żadnych podstaw, na których mogłaby to uczynić.\n\n2.3 Organ korzystający z tych materiałów nie działa zatem w imieniu Koalicji. Wykorzystuje on informacje publiczne, które zostały zebrane przez kogoś innego.\n\n3. Wszystko jest już otwarte\n\n3.1 Działalność Koalicji jest domyślnie jawna:\n\nwyniki badań są publicznie dostępne pod adresem https://phishdestroy.io i są ogólnodostępne;\n\nnarzędzie zostało udostępnione jako oprogramowanie typu open source na licencji MIT pod adresem https://github.com/phishdestroy zarchiwizowano 2026-09-11 ↗;\n\nmetodologia została przedstawiona w samym wniosku o wydanie opinii, w załączniku A sekcja A.16D, z uwzględnieniem wagi i ograniczeń każdego rodzaju źródła;\n\nKoalicja nie przyjmuje żadnych darowizn i informuje o tym od czasu opublikowania strony 2018.\n\n3.2 Jedynymi materiałami, które NIE zostały opublikowane, są te, których publikacja jest niezgodna z prawem lub stanowi zagrożenie dla bezpieczeństwa: dane osobowe ofiar i osób trzecich oraz informacje, które mogłyby narazić źródło na działania odwetowe. Materiały te są przekazywane organom władzy z zachowaniem poufności i są wymienione w wykazach dowodów.\n\n3.3 Koalicja zachęca do kontroli swoich działań na takich samych zasadach, na jakich zachęca do kontroli działań innych podmiotów, i z własnej inicjatywy udostępniła swoje dane właściwym organom, w tym zwróciła się o wydanie wytycznych dotyczących ich usunięcia.\n\n4. Spójność zbioru dowodów\n\n4.1 Załączniki należy dostarczyć wraz ze zgłoszeniem lub, w przypadku odpowiedniego zaznaczenia, na żądanie za pośrednictwem bezpiecznego kanału. Nie są one publikowane pod adresem publicznym i nie należy wyciągać wniosków co do istnienia takiego adresu: materiały tego rodzaju są przekazywane bezpośrednio organom.\n\n4.2 Do każdej dostawy dołączony jest plik SHA256SUMS zawierający skrót SHA-256 dla każdego dostarczonego pliku, wraz z oddzielnym podpisem OpenPGP SHA256SUMS.asc.\n\n4.3 Klucz podpisujący został opublikowany pod adresem https://phishdestroy.io/.well-known/pgp-key.txt oraz na stronie keys.openpgp.org. Jego sygnatura widnieje w nagłówku każdego zgłoszenia w tym zestawie.\n\n4.4 Każdy odbiorca może w dowolnym momencie sprawdzić, czy plik, który posiada, jest tym samym plikiem, który został wysłany, bez żadnych zmian:\n\ngpg --verify SHA256SUMS.asc SHA256SUMS\n\nsha256sum -c SHA256SUMS\n\n4.5 Nie chodzi tu o formalność. Ma to na celu zapewnienie, że gdyby w przyszłości pojawiły się wątpliwości co do dokładności lub integralności jakiegokolwiek dowodu rzeczowego, kwestia ta mogłaby zostać rozstrzygnięta na podstawie obliczeń, a nie sporów.\n\n5. W rejestrze — dlaczego zwolnienie ma charakter funkcjonalny, a nie jest jedynie gestem dobrej woli\n\n5.1 Władze mogą natknąć się na opublikowane przez Koalicję wyniki dochodzeń i uznać je za dosadne, konfrontacyjne, a czasami satyryczne. To wrażenie jest słuszne. Koalicja celowo pisze w ten sposób i nie przeprasza za to.\n\n5.2 UZNAJE RÓWNIEŻ, ŻE NIE JEST TO ODPOWIEDNI STYL DLA POSTĘPOWANIA REGULACYJNEGO LUB SĄDOWEGO. Poważna sprawa nie powinna być przedstawiana w tonie kampanii. Ustalenia przedkładane organowi powinny być przedstawione w sposób rzeczowy, z przyznaniem się do ich ograniczeń, i nie powinny wymagać od czytelnika pomijania tonu wypowiedzi, zanim dotrze on do istoty sprawy.\n\n5.3 WŁAŚNIE DLATEGO KOALICJA ZRZEKA SIĘ PRAWA AUTORSTWA. Zrzeczenie się prawa, o którym mowa w sekcji 1, stanowi mechanizm umożliwiający oddzielenie treści od rejestru: organ może wykorzystać to, co jest przydatne, przeformułować to własnymi słowami oraz odrzucić każde słowo charakterystyczne dla stylu Koalicji wraz z jej nazwą. W ten sposób nic się nie traci, a Koalicja wolałaby właśnie takie rozwiązanie.\n\n5.4 KOALICJA PROSI RÓWNIEŻ, ABY NIE MYLIĆ REJESTRU Z METODĄ. Ton publikacji jest bojowy, ale sama praktyka nie jest niedbała. W całym niniejszym zgłoszeniu wnioski są oddzielone od obserwacji, zeznania są identyfikowane jako zeznania, źródła są oceniane pod kątem wiarygodności, a ich słabe strony wskazywane, dane liczbowe są przedstawiane wraz z ich ograniczeniami, a kwestie, których Koalicja nie jest w stanie udowodnić, są formułowane jako pytania skierowane do organu, a nie jako twierdzenia. W przypadkach, gdy dowody były sprzeczne ze stanowiskiem samej Koalicji, została to wyraźnie zaznaczone — patrz załącznik A, ustęp 7, oraz sekcja B.0 równoległego wniosku.\n\n5.5 KOALICJA WYJAŚNIA ZWIĄZEK MIĘDZY SWOIM SPOSOBEM DZIAŁANIA A FINANSAMI, PONIEWAŻ TE DWA ELEMENTY SĄ NIEROZDZIELNE. Nie przyjmuje od nikogo żadnych środków finansowych – ani darowizn, ani nagród, ani klientów, ani sponsorów. To właśnie ta odmowa pozwala na taką bezpośredniość: organizacja, która ma dochody do ochrony, musi łagodzić swoje wypowiedzi na temat podmiotów, od których jest zależna. Nie mając nic do ochrony, Koalicja nie musi niczego łagodzić.\n\nTo właśnie dlatego Koalicja nadal istnieje. Nie ma żadnego innego motoru napędowego. Praca jest wykonywana po prostu dlatego, że jest wykonywana; kończy się, gdy przestają ją wykonywać ludzie.\n\n5.6 Władze nie muszą tego w ogóle akceptować. Stwierdza się to po to, by ton działań publicznych Koalicji nie był traktowany jako miara staranności, z jaką podchodzi ona do materiałów, które ma obecnie do rozpatrzenia.\n\n6. Co oferuje Koalicja, według jej własnych słów\n\nInformacje, badania i obserwacje.\n\nW dokumencie nie zawarto żadnych stwierdzeń, do których sformułowania Koalicja nie ma uprawnień. W przypadku wniosków wywnioskowanych w dokumencie jest to wyraźnie zaznaczone. Jeśli coś opiera się na zeznaniach, w dokumencie podano, od kogo pochodzą i jakie są związane z nimi ograniczenia. W przypadku gdy Koalicja nie jest w stanie odpowiedzieć na dane pytanie, również to zaznaczono, wskazując jednocześnie, kto może udzielić odpowiedzi.\n\nKoalicja nie domaga się żadnego zadośćuczynienia, żadnej wypłaty, żadnego potwierdzenia ani żadnego rozstrzygnięcia ani dla siebie, ani dla żadnej osoby. Prosi jedynie, aby pytania zawarte we wniosku zostały skierowane dValve Corporation przez organ uprawniony do wymuszenia udzielenia odpowiedzi.\n\nPodsumowanieDo osoby, która zajmuje się tą sprawą\n\nChcielibyśmy podziękować wszystkim, którzy dopilnują, by te materiały dotarły tam, gdzie powinny. To prawdopodobnie nie będzie szybka sprawa. Firma „Valve” dysponuje ogromnymi środkami, a kancelaria Taylor Wessing pobiera opłaty według stawki godzinowej — to połączenie ma na celu sprawić, by ludzie tacy jak wy poddali się, zanim dotrą do mety.\n\nWiemy, co robimy. Wiemy, o kim piszemy. To właśnie „Valve” nas ukształtowało — jak moglibyśmy ich nie rozumieć?\n\nPhishDestroy nie ma to nic wspólnego z Valve. Zablokowaliśmy jedyną grupę oszustów tej skali, z jaką się spotkaliśmy — nie szukaliśmy konfliktu z Valve. Po prostu okazało się, że wszystkie ślady prowadziły właśnie do nich. To nie jest konflikt. To po prostu topologia.\n\nValve Nie da się rozwiązać sytuacji z „PhishDestroy”, bo nie ma tu nic do rozwiązywania. Nie łączą nas żadne relacje. Dane dotyczące ich schematów wzbogacania się i nadwyżkowych zysków są w dużej mierze publiczne — wystarczyło tylko poświęcić wystarczająco dużo czasu, żeby je znaleźć. Pomyśl o tym jak o encyklopedii sukcesu: „Jak nie przestrzegać sankcji, aby rosyjscy hakerzy nie mogli piracić naszych darmowych gier (a tych płatnych i tak nie będą piracić)”. Wiesz, o co chodzi.\n\nNie potrzebujemy informacji o autorstwie.\n\nNie potrzebujemy podania źródła.\n\nNie potrzebujemy zwycięstwa.\n\nPotrzebujemy kogoś, kto dysponuje rzeczywistymi uprawnieniami, aby zadać firmie „Valve” pytania zawarte w niniejszym wniosku, oraz kto ma prawo wymagać udzielenia odpowiedzi.\n\nTo wszystko. Taka jest cała prośba.\n\nSprawy będą przechowywane pod adresem:\n\nhttps://steamdestroy.eth/\n\nhttps://steamdestroy.eth.limo (obecnie nie działa — naprawimy w razie potrzeby)\n\nBędziemy pod adresem:\n\nhttps://phishdestroy.eth.limo/ zarchiwizowano 2026-06-27 ↗\n\nhttps://phishdestroy.eth/\n\nDwa podpisane przedmioty · prawa autorskie i opublikowany tekst\nPodpisane oświadczenie o zwolnieniu z odpowiedzialnościCo zostało podpisane i czego dotyczy umowa\n\nPoniżej przedstawiono osobno podpisane obiekty JSON zawierające oświadczenie o prawach oraz tekst badawczy. Każdy oddzielny podpis typu „OpenPGP” uwierzytelnia dokładną sekwencję bajtów pliku JSON wymienionego obok niego. Oświadczenie o prawach przyznaje uprawnienia; migawka tekstu identyfikuje i zawiera publikowany materiał.\n\n1. Oświadczenie dotyczące praw — license-rights.json\n\nPodpisany obiekt: całość license-rights.json plik zawierający publiczną licencję z dnia 28 września 2026.. Licencja ta zezwala na kopiowanie, publikowanie, edytowanie, tłumaczenie, łączenie i wykorzystywanie materiałów autorstwa serwisu w celach komercyjnych bez konieczności podawania źródła, powiadamiania ani uzyskiwania zgody. Podpis ten poświadcza autentyczność oświadczenia o prawach; nie poświadcza on autentyczności treści poszczególnych stron internetowych ani plików PDF.\n\nOryginalna, podpisana zgoda pozostaje w mocy bez zmian. Udzielone w niej uprawnienia nie mogą zostać cofnięte ani ograniczone poprzez zmianę treści strony internetowej, opublikowanie innego pliku lub wyłączenie strony. Materiały pochodzące od osób trzecich podlegają odrębnym prawom.\n\nOświadczenie o prawach w formacie JSON ↗ · Podpislicense-rights.jsona ↗ · SHA-256 z license-rights.json ↗\n\ngpg --verify license-rights.json.asc license-rights.json\nsha256sum -c license-rights.json.sha256\n2. Opublikowany tekst — dossier-text.json\n\nPodpisany obiekt: całość dossier-text.json plik. Zawiera on rzeczywisty, czytelny tekst wyeksportowanych stron w formacie documents[].content.text, wraz z tytułem każdej strony, językiem, adresem URL źródła, skrótem kodu HTML źródła, nagłówkami i odnośnikami. Plik documents Lista zawiera dokładny spis pozycji objętych tym migawką; warianty językowe są wymienione osobno. Jest to publikacja tekstowa, a nie tylko lista skrótów.\n\nKażdy wpis identyfikuje swoją lekko skompresowaną stronę w formacie PDF na podstawie nazwy pliku oraz skrótu SHA-256, zawartego w documents[].pdf. Plik JSON zawiera również informacje o oryginalnej deklaracji praw autorskich w postaci adresu URL oraz skrótu SHA-256,, dzięki czemu opublikowany tekst, jego plik PDF oraz odpowiednia deklaracja praw autorskich mogą zostać ze sobą powiązane bez konieczności zgadywania. Powiązane zewnętrzne bazy danych, oryginalne pliki graficzne oraz strony nieobjęte spisem nie są osadzone w tej migawce tekstu.\n\nPełny podpisany tekst w formacie JSON ↗ · Podpisdossier-text.jsona ↗ · SHA-256 z dossier-text.json ↗\n\ngpg --verify dossier-text.json.asc dossier-text.json\nsha256sum -c dossier-text.json.sha256\n\nNa stronie głównej dossier przyciski „PDF” i „JSON” służą do eksportowania pakietu badawczego. Na stronach wewnętrznych umożliwiają one eksport danej strony w języku, w którym została opublikowana. Każdy plik JSON strony posiada również własny, oddzielny plik podpisu oraz plik SHA-256, którego nazwa jest wyraźnie podana w jego integrity obiekt. Aby zweryfikować powiązany plik PDF, należy obliczyć jego skrót SHA-256, a następnie porównać go z pdf.sha256 wartość w zweryfikowanym pliku JSON. Plik PDF jest powiązany z tym skrótem; nie zawiera on podpisu cyfrowego w formacie PDF.\n\n3. Pakiet materiałów badawczych do wydrukowania — steam-dossier-{language}.content.json\n\nPodpisany obiekt: kompletny plik JSON dostosowany do danego języka, zawierający dołączony tekst rozdziału w formacie documents[].content.text, zakresy stron rozdziałów, języki źródłowe, wykaz wykluczonych źródeł oraz dokładny skrót pliku PDF w pdf.sha256. Pięć archiwów materiałów uzupełniających pozostaje dostępnych online i nie są one łączone w jeden pakiet. Teksty badawcze autorstwa poszczególnych autorów są zachowywane; katalogi wizualne zastępuje się linkami do źródeł.\n\nAngielski JSON ↗ · Podpis „OpenPGP” na domu wolnostojącym ↗ · Podsumowanie skrótu SHA-256 ↗\n\nDeutsch JSON ↗ · Podpis „OpenPGP” na domu wolnostojącym ↗ · Podsumowanie skrótu SHA-256 ↗\n\ngpg --verify steam-dossier-en.content.json.asc steam-dossier-en.content.json\nsha256sum -c steam-dossier-en.content.json.sha256\n\nPubliczny klucz weryfikacyjny ↗\n\nOdcisk cyfrowy podpisu: 129F C7F3 9C40 C69D 2EF3 C329 BFCF 9E8D D295 EE01\n\ngpg --import pgp-key.txt\ngpg --fingerprint 129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01\n\nSprawdź, czy wyświetlany odcisk palca zgadza się z tym powyżej, a następnie zweryfikuj podpis na podstawie dokładnej nazwy pliku JSON. Edycja podpisanego pliku JSON powoduje zmianę podpisanego obiektu i unieważnia jego pierwotny podpis. Prawidłowy podpis identyfikuje opublikowane bajty; nie stanowi on niezależnej weryfikacji wyników badań.\n\nPhishDestroy — dochodzenie publiczne — wszelkie prawa przekazano ludzkości\n\nDostęp do regionu objętego sankcjami OFAC: zabroniony",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Licencja i zastrzeżenia prawne — Przekazanie do domeny publicznej"
          },
          {
            "level": 2,
            "id": null,
            "text": "Część ILicencja — sama część prawna, ale z ludzkiego punktu widzenia"
          },
          {
            "level": 3,
            "id": null,
            "text": "Jedna konkretna zasada (tak, tylko jedna)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Część IICzym to jest i dlaczego istnieje"
          },
          {
            "level": 2,
            "id": null,
            "text": "Część IIIList otwarty do Valve — serio, przeczytaj to"
          },
          {
            "level": 3,
            "id": null,
            "text": "Umowa (oferta otwarta, bez udziału prawników)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Sekcja III-BZasoby sojusznicze — uwaga skierowana konkretnie do Steam"
          },
          {
            "level": 2,
            "id": null,
            "text": "Część IVPieniądze, zakazy, cały ten cyrk"
          },
          {
            "level": 2,
            "id": null,
            "text": "Sekcja VSprawa z złośliwym oprogramowaniem — tak, wspominamy o tym"
          },
          {
            "level": 2,
            "id": null,
            "text": "OświadczenieW kwestii użytkowania i praw"
          },
          {
            "level": 3,
            "id": null,
            "text": "1. Nie ma żadnych warunków dotyczących użytkowania"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. Dlaczego ma to znaczenie w praktyce, a nie tylko z grzeczności"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. Wszystko jest już otwarte"
          },
          {
            "level": 3,
            "id": null,
            "text": "4. Spójność zbioru dowodów"
          },
          {
            "level": 3,
            "id": null,
            "text": "5. W rejestrze — dlaczego zwolnienie ma charakter funkcjonalny, a nie jest jedynie gestem dobrej woli"
          },
          {
            "level": 3,
            "id": null,
            "text": "6. Co oferuje Koalicja, według jej własnych słów"
          },
          {
            "level": 2,
            "id": null,
            "text": "PodsumowanieDo osoby, która zajmuje się tą sprawą"
          },
          {
            "level": 2,
            "id": null,
            "text": "Podpisane oświadczenie o zwolnieniu z odpowiedzialnościCo zostało podpisane i czego dotyczy umowa"
          },
          {
            "level": 3,
            "id": null,
            "text": "1. Oświadczenie dotyczące praw — license-rights.json"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. Opublikowany tekst — dossier-text.json"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. Pakiet materiałów badawczych do wydrukowania — steam-dossier-{language}.content.json"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/pl/#briefing-heading",
          "https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "http://web.archive.org/web/20260821155801/https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "https://phishdestroy.io/steam_dossier/pl/investigation_part2.html#outsourcing-case",
          "https://phishdestroy.io/steam_dossier/pl/#theft-ledger",
          "https://steamid.uk/",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/groups/steambans",
          "https://steamcommunity.com/id/killahinstinct_",
          "https://phishdestroy.io/steam_dossier/pl/card_economy.html#governance",
          "https://phishdestroy.io/steam_dossier/pl/license_disclaimer.html",
          "https://github.com/phishdestroy",
          "http://web.archive.org/web/20260911040557/https://github.com/PhishDestroy",
          "https://phishdestroy.io/.well-known/pgp-key.txt",
          "https://steamdestroy.eth/",
          "https://steamdestroy.eth.limo/",
          "https://phishdestroy.eth.limo/",
          "http://web.archive.org/web/20260627040219/https://phishdestroy.eth.limo/",
          "https://phishdestroy.eth/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json.asc",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json.sha256",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json.sha256?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json.sha256?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json.sha256?v=print-20260928-v3"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/pl/license_disclaimer.content.json",
      "export_json_sha256": "00fbf47f3c9ee0bf7c5a5b0b772e1ddbb7860b95619e90c047509ecc2dfb8b13"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "pl/market_economics.html",
      "language": "pl",
      "title": "Jedna infrastruktura, dwa rynki — Raport „Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/pl/market_economics",
      "source_html_sha256": "ac771c9d7bd440865defaa0a99e19761ece35014f01f16e92a4f561efe73b1e4",
      "exported_at": "2026-09-29T00:18:57.964Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "market_economics.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/pl/market_economics.pdf?v=print-20260929-v5",
        "sha256": "03c58d65fb4669d2e7227ad7aa484eae0c20e9176e6fba52e94e5ce5afda8e28",
        "bytes": 101739,
        "pages": 8
      },
      "integrity": {
        "signed_object": "market_economics.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "market_economics.content.json.asc",
        "digest_file": "market_economics.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify market_economics.content.json.asc market_economics.content.json",
          "sha256sum -c market_economics.content.json.sha256"
        ]
      },
      "content": {
        "text": "Załącznik VII · Architektura rynku · 20 września 2026\nEkonomia rynkowa — dwie gospodarki i pułap notowań\n\nIch infrastruktura. Dwie gospodarki.\n\nCO WYKAZUJE TA CZĘŚĆ\n\nW niniejszym rozdziale przeanalizowano systemowe rozdwojenie rynku spowodowane przez limit wpłat na konto w serwisie Valve wynoszący $1,800 oraz salda portfeli, z których nie można wypłacać środków. Na podstawie badania 38 aktywnych zewnętrznych giełd skórek, których łączna wycena rynkowa wynosi około $1.28 miliardów, badanie dowodzi, że handel na wysokim poziomie nieuchronnie przenosi się na zewnętrzne platformy „cieniowe”, korzystając jednocześnie z podstawowej infrastruktury transakcyjnej i uwierzytelniającej serwisu Steam. Chociaż komercyjne wykorzystanie jest formalnie zabronione w Umowie abonamentowej, Valve ułatwia funkcjonowanie tej dwupoziomowej gospodarki i czerpie z niej zyski, nie publikując przy tym żadnych danych dotyczących egzekwowania tych przepisów.\n\n← Powrót do podsumowania dla kadry kierowniczej\n\n38 aktywne platformy handlowe CS2 prowadzone przez podmioty zewnętrzne oraz własna platformSteam. Każda skórka wymieniona na którejkolwiek z tych platform musi przejść przez magazyn serwisu Steam oraz platformę handlową API. Zasady serwisu Valve zabraniają komercyjnego wykorzystywania tej infrastruktury. Wartość skórek wystawionych przez osoby trzecie, wynosząca około1.28 miliardów dolarów, istnieje, mimo że nie znaleziono żadnych publicznych danych potwierdzających egzekwowanie tej zasady.\n\n$1.28B\nWartość rynkowa według podmiotów zewnętrznych · Platformy typu „38”\n53.2M\nWyświetlane oferty · Rynki zewnętrzne 38\n70.1K\nSteam pozycje wymienione w zrzucie ekranu\n41×\nWartość podana przez podmiot zewnętrzny a wartość podana przez „Steam” wynosząca $31M\nGłówny wniosek\nJedna infrastruktura. Dwie gospodarki.\n\nSteam kontroluje produkt, zapasy i obrót. Każda skórka sprzedawana na dowolnej z poniższych platform musi przejść przez serwis Steam zajmujący się obrotem API — jest to zależność strukturalna, którą można bezpośrednio zaobserwować. Valve pobiera prowizję od sprzedaży w ramach własnego serwisu Community Market; nie ustalono jednak, czy prowizja ta finansuje ekosystem podmiotów zewnętrznych, czy też jest z nim powiązana.\n\nDlaczego ma to znaczenie dla śledztwa\n1\nUmowa abonamentowa serwisu „Steam” firmy Valve zakazuje wykorzystywania w celach komercyjnych infrastruktury Steam bez wyraźnego zezwolenia. W jawnych rejestrach nie znaleziono takiego zezwolenia dla poniższych platform.\n2\nSteam zarządza tożsamością (OpenID), stanem zapasów oraz realizacją transakcji w odniesieniu do wartości notowanych instrumentów podmiotów zewnętrznych wynoszącej około $1.28B. Żadne przekazanie przedmiotu nie odbywa się bez wykorzystania infrastruktury serwisu Valve.\n3\nWłasna platforma handlowa Steam oferuje $31M notowane — około 1/41 wartości notowanej przez podmiot zewnętrzny. Limit cenowy wynoszący $1,800 oznacza, że sprzedający, których cena przekracza ten poziom, muszą dokonywać sprzedaży poza platformą po cenach rynkowych.\n4\n248 Kategorie produktów CS2, których ceny zostały niezależnie ustalone przez co najmniej dwa rynki powyżej limitu, nie mogą być sprzedawane po zaobserwowanej cenie rynkowej na stronie Steam — i żadna z nich nie jest tam w ogóle notowana. Limit w wysokości $1,800a generuje popyt, który zaspokajają operatorzy zewnętrzni.\nSteam Targ społecznościowy: $31MWartość rynkowa podana przez stronę trzecią:1,276mln dolarów\n$1,276M · wartość podana przez stronę trzecią — wszystko zależy od serwisu Steam, API oraz OpenID\nSteam · $31M\n\nŹródło: Katalog PriceEmpire w czasie rzeczywistym, 20, wrzesień 2026.. Wartość katalogowa = suma zaokrąglonych wartości katalogowych kart w zapisanej migawce, z wyłączeniem Steam. Nie jest to wielkość sprzedaży.\n\n38 aktywne rynki zewnętrzne · Wszystko zależy od infrastruktury Steam\nRejestr platformy\n\nPoniższe platformy kierują proces logowania za pośrednictwem serwisu OpenID pod adresem Steam, a transakcje – za pośrednictwem serwisu Web API należącego do Steam. Każda z zaobserwowanych openid.realm przechodzi przez proces logowania serwisu Steam; rejestr zapisuje zaobserwowane ścieżki uwierzytelniania, zamiast zakładać, że dany operator nie posiada uprawnień serwisu Valve.\n\n#\tPlatforma\tWartość rynkowa\tAktualne oferty\tPozycje\tSkala\n1\tUUSkins\t$133.8M\t3.4M\t30.9K\t\n\n2\tYouPin898\t$127.5M\t5.9M\t29.2K\t\n\n3\tBuff.163\t$104M\t3.5M\t35K\t\n\n4\tMoon.Market\t$100.3M\t2.9M\t20.9K\t\n\n5\tWhite.Market\t$89.6M\t3M\t20.6K\t\n\n6\tBuff.Market\t$86.7M\t1.3M\t33.4K\t\n\n7\tEcosteam\t$82.1M\t3.3M\t30.1K\t\n\n8\tCSFloat\t$67.8M\t2.4M\t27.8K\t\n\n9\tSkin.Land\t$67.4M\t2.2M\t34.6K\t\n\n10\tLIS-SKINS\t$67.4M\t2.2M\t34.6K\t\n\n11\tC5Game\t$54.6M\t4.6M\t29.6K\t\n\n12\tHaloSkins\t$46.6M\t4.4M\t29.3K\t\n\n13\tAvan.Market\t$43.3M\t809.5K\t22.2K\t\n\n14\tWaxpeer\t$40.1M\t1M\t27.3K\t\n\n15\tSteam (official)\t$31M\t32.2M\t70.1K\t\n\n16\tCS.MONEY\t$29M\t748.9K\t28K\t\n\n17\tMarket.CSGO\t$26.3M\t1.3M\t27.6K\t\n\n18\tCS.MONEY Bot\t$25.7M\t614K\t23.8K\t\n\n19\tSkinport\t$16.3M\t3.8M\t31.1K\t\n\n20\tSkinFlow\t$14.1M\t481.8K\t23.6K\t\n\n21\tDMarket\t$12.6M\t948.2K\t35.6K\t\n\n22\tSkins.com\t$11.5M\t83.2K\t15.8K\t\n\n23\tSkin.place\t$6.9M\t380.8K\t11.4K\t\n\n24\tSkinsMonkey\t$6M\t109.4K\t11.6K\t\n\n25\tSkinBaron\t$5M\t2.1M\t21.5K\t\n\n26\tRustTM\t$3M\t33.1K\t4.9K\t\n\n27\tPirateSwap\t$2M\t859.3K\t10.5K\t\n\n28\tMannco.Store\t$1.2M\t223.7K\t11K\t\n\n29\tSkinSwap\t$1.1M\t11.4K\t4K\t\n\n30\tTradeIt\t$967.1K\t29.1K\t11.7K\t\n\n31\tLootFarm\t$896.1K\t162.5K\t28.6K\t\n\n32\tRustskins\t$714.8K\t312.5K\t6.1K\t\n\n33\tBalticSkins\t$599.2K\t28.2K\t4.5K\t\n\n34\tExeSkins\t$442.9K\t2.6K\t1.4K\t\n\n35\tRapidSkins\t$230.9K\t11.6K\t2.3K\t\n\n36\tCS.Trade\t$203K\t19K\t16.7K\t\n\n37\tKrakatoa\t$11.1K\t115\t53\t\n\n38\tShadowPay\t—\t—\t—\t—\n39\t49skins\t—\t—\t—\t—\nSteam ustalił górną granicę ceny na1,800 · przegląd pięciu platform handlowych · 23 września 2026\nRóżnica w cenie jest wymierna.\n\nSteam ogranicza wyceny na platformie Community Market do około $1,800 (wynik ten został ponownie obliczony na $2,000, $, 2,070, $, 2,300 oraz $2,500 w cs2sh-atlas.json i utrzymuje się na każdym progu). Pozycje, których cena przekracza ten poziom nie mogą być sprzedawane po cenie rynkowej za pośrednictwem platformy handlowej serwisu Valve — ale nadal są uzależnione od systemu zarządzania zapasami i wysyłką serwisu Steam, niezależnie od miejsca sprzedaży. Podział całego katalogu według cen pokazuje, gdzie leży granica: rynek serwisu Valve obejmuje 95.3% z kategorii produktów, których cena jest niższa od ustalonego limitu, oraz 1.9% z tych, które znajdują się powyżej.\n\nPięć platform handlowych: produkty przekraczające limit „Steam”\n248\n\nKategorie produktów, których najniższa cena ofertowa przekracza1,800 w dniu dwie lub więcej platform handlowych niezależnie od siebie, posiadając egzemplarze z listy „18,394” o wartości co najmniej $78.6M. Spośród nich, 100.0% — każdy z nich — nie ma w ogóle wpisu w serwisie Steam.\n\nPełna lista dowodów: rejestr → · atlas drabiny cenowej →\n\nRozkład cen powyżej limitu\n$1,800–$5,000\n174\n$5,000–$10,000\n49\n$10,000–$25,000\n21\n$25,000–$50,000\n2\n$50,000+\n2\nNajpopularniejsze produkty — najniższa potwierdzona cena sprzedaży na pięciu platformach handlowych\n1Naklejka | Titan (Holo) | Kat. „14”$66,285\n2Naklejka | iBUYPOWER (Holo) | Kat. „14”$64,795\n3Naklejka | Reason Gaming (Holo) | Kat. „14”$42,899\n4★ Rękawiczki sportowe | Labirynt żywopłotu (FN)$26,812\n5Naklejka | Team Dignitas (Holo) | Kat. „14”$23,667\n6EMS Kat. „14: Legends”$22,879\n7★ Rękawiczki sportowe | Puszka Pandory (FN)$21,643\n8EMS Kat. „14” – uczestnicy$21,010\n9Naklejka | Vox Eminor (Holo) | Kat. „14”$18,619\n10★ Nóż StatTrak™ Navaja | Blue Steel (FN)$18,064\n\nCeny ofertowe nie są cenami sprzedaży. Dane z serwisu cs2.sh, 23, wrzesień 2026.. Każdy wiersz został wyceniony powyżej limitu przez co najmniej dwie niezależne platformy handlowe; wykluczono oferty kupna na jednej półce oraz notowania przekraczające trzykrotność najniższej ceny ofertowej danego produktu. Jak działa system oceniania →\n\nCeny serwisu „Valve” · licencjonowany serwis „cs2.sh” – przegląd · 23 wrzesień 2026\nPodana opłata wynosi 15%.. W większości ogłoszeń oferują wyższe wynagrodzenie.\n\nValve pobiera opłatę 5% Steam oraz opłatę wydawcy 10% CS2 z wpływów sprzedającego — czyli znaną opłatę 15%. Obie opłaty obejmują Minimum0.01, więc żadna transakcja nie może nigdy wiązać się z opłatą niższą niż dwa centy. W przypadku tanich produktów sprzedawanych w dużych ilościach, które stanowią większość rynku, to właśnie ta dolna granica stanowi wiążące ograniczenie, a nie wartość procentowa. Rozwiązaliśmy kwestię obliczania opłat dla każdej z 29,635 typy pozycji, w przypadku których obowiązuje aktualna oferta typu „Steam”.\n\n77.7%\nAktualne oferty serwisu Steam dotyczą rodzajów przedmiotów, za które pobierane są opłaty zgodnie z 15%\n84.8%\npozycji typy płacą mniej więcej tyle, ile wynosi stawka podstawowa\n4,517\nrodzaje pozycji, za które pobrano opłatę wyższą niż podana w ogłoszeniu\n$0.02\nminimalna opłata od każdej sprzedaży, niezależnie od ceny\nTe dwie liczby wskazują w przeciwnych kierunkach, a obie są prawdziwe\n1\nZliczone według rodzaju pozycji, Opłata za usługę „Valve” jest zasadniczo zgodna z ogłoszeniem: 84.8% – ceny dla typów określonych na stronie 29,635 wynoszą tyle samo lub są zbliżone do tych podanych na stronie 15%.\n2\nZliczone według faktycznego wykazu, obraz się odwraca: 18,682,244 z 24,038,911 aktualne oferty dotyczą tylko tych rodzajów produktów, za które pobierana jest opłata wyższa niż 15%.\n3\nOba stwierdzenia są prawdziwe, ponieważ typy z nadmiernym ładunkiem to tanie, produkowane w dużych ilościach te. 1,109 za niektóre rodzaje produktów pobierane są wyższe opłaty niż podwójny stawka podstawowa, a same tylko te rodzaje nieruchomości są dostępne na stronie 14,083,486 w sekcji ofert na żywo.\n4\nTo prosta matematyka, a nie zarzut. Minimalna kwota została podana w dokumentacji dotyczącej opłat samej firmy „Valve”. To, czego nie opublikowano, to jak dużą część rynku to faktycznie dotyczy — i właśnie to pokazują powyższe dane.\nPobierana opłata jako procent wartości nominalnej 15%\n200%+\n14,083,486\n100-200%\n1,028,438\n50-100%\n700,804\n30-50%\n317,031\n20-30%\n2,258,254\n17.6-20%\n294,231\n\nDługość pasma to liczba aktywnych ofert w każdym paśmie. Pasmo oznaczone jako „200%+” oznacza, że pobierana opłata stanowi ponad dwukrotność wartości 15% zysku sprzedającego.\n\nPrzykład z rozwiązaniem\n67%\n\nW przypadku oferty kupujący płaci $0.03 ponieważ sprzedawca otrzymuje $0.01 a strona Valve zajmuje $0.02 — te dwa minimalne progi wynoszące po jednym centu. W przeliczeniu na kwotę zapłaconą przez kupującego jest to 67%; w przeliczeniu na wpływy sprzedającego jest to 200%.\n\nPełny zbiór danych: cs2sh-steam-fee-census.json →\n\nTen sam przedmiot – w ogrodzie i poza nim\nZakupy na stronie Steam są droższe. Prawie zawsze.\n\nW przypadku każdego produktu, którego cena była podana zarówno na stronie Steam, jak i na co najmniej jednej zewnętrznej platformie handlowej, porównaliśmy najniższą cenę sprzedaży na Steam z najniższą ceną sprzedaży poza tą platformą. W całym 28,700 pozycji, Steam to droższa opcja 86.4% w większości przypadków, o medianę wynoszącą +35.7%.\n\nMediana składki ubezpieczenia „Steam”, według przedziałów cenowych\nponiżej0.50 dolarów\n+48.3%\n$0.50-2\n+36.5%\n$2-10\n+29.6%\n$10-50\n+28.6%\n$50-250\n+36.3%\n$250-1k\n+51.1%\nponad $1,000\n+67.9%\n\nKrzywa ma kształt litery U. Najtaniej jest kupować na stronie Steam w $10–$50 z opaską i najdroższą osobą po obu stronach.\n\nDlaczego wysoki przedział cenowy ma znaczenie\n+67.9%\n\nPowyżej $1,000, mediana kosztów ogłoszeń w serwisie „Steam” 67.9% przewyższa cenę najtańszej oferty spoza tego serwisu — a na stronie Steam 1,040 w ogóle występują tylko takie ogłoszenia.\n\nPowyżej kwoty około1,800 porównanie przestaje być możliwe, ponieważ zasady serwisu Valve całkowicie zabraniają umieszczania takich pozycji na liście. Serwis Steam uwzględnia pozycje powyżej własnego limitu w 1.9%. Zobacz całą tabelę →\n\nPełny zbiór danych: cs2sh-walled-garden-premium.json →\n\nPremia sama w sobie nie stanowi wniosku: Steam oferuje natychmiastową realizację zlecenia i brak ryzyka kontrahenta, a nabywcy mogą za to słusznie zapłacić. To, co można zmierzyć, to wielkość różnicy oraz fakt, że pieniądze, które ją pokonują, nie mogą wrócić — o czym mowa w następnej sekcji.\n\nPieniądze wpływają, ale nie wypływają\n128.1 mln dolarów przeznaczono na zamówienia, których nie można anulować.\n\nZlecenie kupna w ramach usługi „Steam” jest opłacane z góry: środki opuszczają portfel kupującego w momencie złożenia zlecenia. Środki w portfelu Steam nie można go wycofać — można je wydać wyłącznie w ramach Steam. Zsumowanie wszystkich poziomów cenowych z księgi zleceń kupna każdego śledzonego instrumentu daje obraz środków, które zostały już przydzielone i z których nie można się wycofać.\n\n$128.1M\nzobowiązani do utrzymywania zleceń kupna typu „Steam”\n170.6M\naktualne zlecenia kupna finansowane indywidualnie\n$105.8M\nwartość rynkowa nieruchomości znajdujących się naprzeciwko nich\n$15.9M\nZysk firmy Valve, gdyby wszystkie oferty zostały sprzedane po cenie wywoławczej\nCzym jest ta liczba, a czym nie jest\n1\nTo jest prawdziwe pieniądze, które zostały już wpłacone. Każdy uwzględniony dolar został pobrany z portfela i jest przypisany do otwartego zlecenia dotyczącego różnych typów pozycj31,253.\n2\nTo jest nie przychody a nie stwierdzenie dotyczące bilansu firmy „Valve”. Nie ustalono tutaj, gdzie przechowywane są akcje w obrocie i w księgach kogo figurują.\n3\nJest to migawka, a nie przepływ. Kupujący może anulować zamówienie, co powoduje zwrot środków do portfela — jednak środki te nadal pozostają w serwisie Steam.\n4\nChodzi właśnie o te drzwi jednokierunkowe. Rynek, na którym nie można spieniężyć waluty, jest powodem, dla którego skradzione zapasy są zamieniane wyłączony Steam a nie na nim.\n\nMetoda: każdy poziom cenowy każdego monitorowanego rejestru zleceń kupna pomnożony przez liczbę zleceń znajdujących się na tym poziomie. Pełny zbiór danych: cs2sh-steam-locked-capital.json →\n\nZrealizowane transakcje sprzedaży, a nie ceny wywoławcze · jedna platforma handlowa · dane z ostatnich 90 dni\nW rzeczywistości sprzedano za30.9 mln dolarów — na najmniejszej z pięciu półek.\n\nPojedyncza transakcja o wysokiej wartości może dotyczyć rzadkiego egzemplarza rękodzieła lub wariantu taniego przedmiotu podstawowego z naklejką (np. e.g – przedmiot o wartości30, który został sprzedany jednorazowo za9,772). Termin „wysoka” odnosi się do najwyższej zrealizowanej transakcji, a nie do normalnej ceny przedmiotu.\n\nKażda kolejna wartość na tej stronie odnosi się do wymienione. Ten mierzy to, co było sprzedane. Serwis Skinport publikuje informacje o własnych zrealizowanych transakcjach, a w ciągu ostatnich 90 dni ich liczba wyniosła 1,219,143 sprzedaż wartość $30,927,032, po średniej cenie25.37 za sztukę.\n\n1.22M\nsprzedaż zrealizowana w ciągu 90 dni, na jednej platformie handlowej\n$30.9M\nobroty w tym samym okresie\n$125M\nroczna stopa wzrostu — wartość minimalna, a nie szacunek\n~2%\nUdział firmy Skinport w rynku papierów wartościowych o wartości rynkowej powyżej limitu, według wartości rynkowej\nSkąd pochodziły przychody\nponiżej1 dolarów\n0.5%\n$1-10\n5.8%\n$10-100\n22.2%\n$100-1k\n59.4%\n$1k-1.8k\n6.9%\npowyżej limitu „Steam”\n5.3%\n\nDługość słupka oznacza obroty; wartość ta odpowiada udziałowi danego poziomu w całości. 59.4% z kwot obrotowych w kategorii $100–$1k, przy sprzedaży na stronie 71,437.\n\nNad czapką „Valve” nadal odbywają się wyprzedaże\n492\n\nzrealizowana sprzedaż produktów, których cena przekracza limit określony w przepisach dotyczących „Steam”, o wartości $1,643,938, obejmujące 76 rodzaje produktów — na platformie handlowej, która zajmuje około 2% tej półki. Żadna z tych transakcji nie mogłaby dojść do skutku na stronie Steam.\n\nPełny zbiór danych: cs2sh-offsteam-90d-dynamics.json → · najwyższe wartości, jakie osiągnęły →\n\nSkinport jest JEDNYM z rynków zewnętrznych śledzonych w tym zestawieniu, a ze względu na wartość notowań przekraczającą limit „Steam” jest najmniejszym z pięciu (stanowi około 2% tej półki). Każda podana tu suma stanowi dolną granicę rynku „off-Steam”, a nie jego miarę. Nie wykorzystano żadnych danych z serwisu Steam.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Ekonomia rynkowa — dwie gospodarki i pułap notowań"
          },
          {
            "level": 2,
            "id": null,
            "text": "Jedna infrastruktura. Dwie gospodarki."
          },
          {
            "level": 2,
            "id": null,
            "text": "Rejestr platformy"
          },
          {
            "level": 2,
            "id": null,
            "text": "Różnica w cenie jest wymierna."
          },
          {
            "level": 3,
            "id": null,
            "text": "Pięć platform handlowych: produkty przekraczające limit „Steam”"
          },
          {
            "level": 3,
            "id": null,
            "text": "Rozkład cen powyżej limitu"
          },
          {
            "level": 3,
            "id": null,
            "text": "Najpopularniejsze produkty — najniższa potwierdzona cena sprzedaży na pięciu platformach handlowych"
          },
          {
            "level": 2,
            "id": null,
            "text": "Podana opłata wynosi 15%.. W większości ogłoszeń oferują wyższe wynagrodzenie."
          },
          {
            "level": 3,
            "id": null,
            "text": "Pobierana opłata jako procent wartości nominalnej 15%"
          },
          {
            "level": 3,
            "id": null,
            "text": "Przykład z rozwiązaniem"
          },
          {
            "level": 2,
            "id": null,
            "text": "Zakupy na stronie Steam są droższe. Prawie zawsze."
          },
          {
            "level": 3,
            "id": null,
            "text": "Mediana składki ubezpieczenia „Steam”, według przedziałów cenowych"
          },
          {
            "level": 3,
            "id": null,
            "text": "Dlaczego wysoki przedział cenowy ma znaczenie"
          },
          {
            "level": 2,
            "id": null,
            "text": "128.1 mln dolarów przeznaczono na zamówienia, których nie można anulować."
          },
          {
            "level": 2,
            "id": null,
            "text": "W rzeczywistości sprzedano za30.9 mln dolarów — na najmniejszej z pięciu półek."
          },
          {
            "level": 3,
            "id": null,
            "text": "Skąd pochodziły przychody"
          },
          {
            "level": 3,
            "id": null,
            "text": "Nad czapką „Valve” nadal odbywają się wyprzedaże"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/pl/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/pl/elite_skins.html",
          "https://phishdestroy.io/steam_dossier/pl/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/pl/skin_atlas.html#grading",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-steam-fee-census.json",
          "https://phishdestroy.io/steam_dossier/pl/skin_atlas.html#cliff",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-walled-garden-premium.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-steam-locked-capital.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-offsteam-90d-dynamics.json",
          "https://phishdestroy.io/steam_dossier/pl/skin_atlas.html#highs"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/pl/market_economics.content.json",
      "export_json_sha256": "02d06011af0e7bdfb13b7137da94428bae1ab84f1235cf21b54ac674f97e4ebb"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "pl/regulatory_act_print.html",
      "language": "pl",
      "title": "USTAWA O AUDYCIE KRYMINALISTYCZNYM: Valve Steam Strona internetowa API Ekosystem i wykorzystanie komercyjne (nr ref.: VAL-REG-2026-09)",
      "source_url": "https://phishdestroy.io/steam_dossier/pl/regulatory_act_print",
      "source_html_sha256": "74f727917af1ee209ce6b711428ba8a2d188602aa666af8a2cd3840d944914e1",
      "exported_at": "2026-09-29T00:18:58.316Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "regulatory_act_print.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/pl/regulatory_act_print.pdf?v=print-20260929-v5",
        "sha256": "2987fffe3fa0297d8a5baa38b6d4726bfd518e5015c7eab1f258f4603c1feb03",
        "bytes": 188653,
        "pages": 14
      },
      "integrity": {
        "signed_object": "regulatory_act_print.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "regulatory_act_print.content.json.asc",
        "digest_file": "regulatory_act_print.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify regulatory_act_print.content.json.asc regulatory_act_print.content.json",
          "sha256sum -c regulatory_act_print.content.json.sha256"
        ]
      },
      "content": {
        "text": "phishdestroy.io · Koalicja ds. Badań Kryminalistycznych · Powszechny rejestr publiczny\nSPRAWA: VAL-REG-2026-09-EVID\nPOCHODZENIE: phishdestroy.io/steam_dossier/\nPRAWA: WSZYSTKIE PRAWA PRZEKAZANE LUDZKOŚCI\nUstawa o audycie kryminalistycznym i załącznik regulacyjny\nSystematyczne udostępnianie usług typu „API” przez podmioty zewnętrzne, architektura z automatycznym obejściem oraz brak egzekwowania postanowień umownych w ekosystemie Valve Steam\nDomena wydającaphishdestroy.io\nPlatforma docelowaValve Steam / Steamworks\nGłówny wektor uwierzytelniającySteam OpenID 2.0 / Strona internetowa API\nInformacja prawnaWszystkie prawa zastrzeżone dla Humanity (CC0)\nCzęść I: Notatka wykonawcza i ustalenia faktyczneNR REF.: MEMO-SUMMARY-01\n\nNiniejszy dokument stanowi formalny raport z audytu śledczego, w którym przeanalizowano powiązania operacyjne między opublikowanymi warunkami handlowymi spółki „Valve”, jej technicznymi punktami końcowymi uwierzytelniania oraz zaobserwowanymi platformami komercyjnymi podmiotów zewnętrznych. Audyt przeprowadzono przy użyciu pasywnej, nieautoryzowanej obserwacji sieci, weryfikacji rejestracji w systemie „RDAP” oraz publicznych danych telemetrycznych z usługi „Link Filter”.\n\nIstota sprawy: Obserwacje empiryczne wskazują na systematyczną rozbieżność między publicznymi oświadczeniami umownymi serwisu „Valve” a jego infrastrukturą produkcyjną. Podczas gdy Umowa abonamentowa serwisu Steam (SSA) surowo zabrania nieautoryzowanego wykorzystania komercyjnego (§ 2.G), zautomatyzowanej interakcji za pomocą botów/skryptów (§ 4.C) oraz przenoszenia kont (§ 1.C), spółka Valve Corporation nadal udostępnia infrastrukturę do programowego uwierzytelniania OpenID na żywo oraz zapytań o zasoby co najmniej 175 podmiotom komercyjnym, generującym wielomiliardowe obroty w ramach transakcji na rynku wtórnym.\n\n175\nPodmioty gospodarcze podlegające audytowi\n44\nHosty uwierzytelniające w oddzielnych domenach\n26\nPary serwerów proxy z podziałem filtrów\n100%\nNieobowiązujące przepisy SSA § 2.G / § 4.C\n0\nWymuszone unieważnienia uprawnień\nObowiązujące ramy umowne i prawne\nSSA § 2.G\nZakaz wykorzystania w celach komercyjnych: Zdecydowanie zabrania się wykorzystywania Treści i Usług do celów komercyjnych bez uprzedniej pisemnej zgody firmy Valve Corporation.\nSSA § 4.C\nOgraniczenia dotyczące automatyzacji: Zdecydowanie zabrania się korzystania ze skryptów, botów handlowych, makr lub systemów niekontrolowanych przez ludzi, które wchodzą w interakcję z usługami i rynkami serwisu Steam.\nSSA § 1.C\nWymóg dotyczący użytku osobistego: Ogranicza korzystanie z kont wyłącznie do użytku osobistego; wyraźnie zabrania sprzedaży, wynajmu, przekazywania lub wymiany kont użytkowników serwisu Steam.\nUnijna ustawa o usługach cyfrowych (2022/2065)\nOcena ryzyka systemowego (art. 34/35): Bardzo duże platformy internetowe (VLOP) muszą aktywnie wykrywać, oceniać i ograniczać ryzyko systemowe wynikające z nadużyć związanych z automatyzacją oraz nieuprawnionego wykorzystywania w celach komercyjnych.\nSekcja II: Rejestr załączników A — udokumentowane pary rozdzielonych filtrów linków (trasy typu 26)NR REF.: EX-SPLIT-LEDGER\n\nAnaliza kryminalistyczna technik unikania wykrycia opartych na rozdzieleniu domen: W ramach systemu filtrowania linków „Steam” firmy Valve (steamcommunity.com/linkfilter/?url=...), gdy użytkownik końcowy kliknie link prowadzący do oznaczonej platformy hazardowej lub działającej na czarnym rynku, strona Valve wyświetla wyraźne ostrzeżenie („Link zablokowany! … oznaczony jako potencjalnie złośliwy”). Jednak analiza śladów sieciowych wykazała, że platformy komercyjne typu „26” działają na architektura z podziałem domen: podczas gdy główna domena komercyjna jest ZABLOKOWANA w filtrze linków, domena pomocnicza, na której znajduje się punkt końcowy OpenID serwisu Valve, jest oznaczona jako BEZPIECZNA. Serwery OpenID serwisu Valve bez zakłóceń przyjmują żądania uwierzytelnienia z tych hostów proxy, co pozwala zneutralizować ostrzeżenie dotyczące bezpieczeństwa użytkowników, jednocześnie umożliwiając dalsze przetwarzanie logowań.\n\n#\tGłówna domena komercyjna\tFiltr główny\tDomena serwera proxy uwierzytelniającego OpenID\tFiltr autoryzacji\tRDAP Zarejestrowany\tPodstawa rozliczenia\n01\trollbit.com\tBLOCKED\trbsnin.com\tCLEAN\t2026-09-18\tPASSIVE_CAPTURE\n02\tskin.club\tBLOCKED\tsc-auth.net\tCLEAN\t2019-04-02\tPASSIVE_CAPTURE\n03\thowl.gg\tBLOCKED\thowl.uno\tCLEAN\t2026-08-11\tPASSIVE_CAPTURE\n04\tduelbits.com\tBLOCKED\tswitchflips.com\tCLEAN\t2020-04-21\tPASSIVE_CAPTURE\n05\tcsgofast.com\tBLOCKED\tsteam-login.authtofast.com\tCLEAN\t2026-06-30\tPASSIVE_CAPTURE\n06\tfarmskins.com\tBLOCKED\tsteam.kobal.cc\tCLEAN\t2017-01-07\tPASSIVE_CAPTURE\n07\tcobaltlab.tech\tBLOCKED\tcobaltauth.com\tCLEAN\t2025-01-07\tPASSIVE_CAPTURE\n08\tcsgo.net\tBLOCKED\tcn2.easylot.net\tCLEAN\t2016-09-03\tPASSIVE_CAPTURE\n09\tggdrop.com\tBLOCKED\tggauth.com\tCLEAN\t2023-05-03\tPASSIVE_CAPTURE\n10\trustchance.com\tBLOCKED\thgfuihd.com\tCLEAN\t2019-01-27\tPASSIVE_CAPTURE\n11\tskin.fans\tBLOCKED\tauth.skinfans.com\tCLEAN\t2018-07-16\tPASSIVE_CAPTURE\n12\tskinport.com\tBLOCKED\tskinport.app\tCLEAN\t2020-06-20\tPASSIVE_CAPTURE\n13\tskins.cash\tBLOCKED\tskinscash.live\tCLEAN\t2019-12-05\tPASSIVE_CAPTURE\n14\ttf2hunt.com\tBLOCKED\trstspcl.com\tCLEAN\t2020-08-08\tPASSIVE_CAPTURE\n15\tdaddyskins.com\tBLOCKED\tgo-go-daddy.com\tCLEAN\t2019-01-26\tPASSIVE_CAPTURE\n16\tkey-drop.com\tBLOCKED\tkdauth.com\tCLEAN\t2026-05-13\tPASSIVE_CAPTURE\n17\tclash.gg\tBLOCKED\tclggauth.com\tCLEAN\t2024-09-16\tPASSIVE_CAPTURE\n18\tc5game.com\tBLOCKED\twww.imbastar.com\tCLEAN\t2016-02-27\tPASSIVE_CAPTURE\n19\tswap.gg\tBLOCKED\tswapauth.com\tCLEAN\t2018-10-06\tPASSIVE_CAPTURE\n20\tshadowpay.com\tBLOCKED\tthelogins.com\tCLEAN\t2018-01-22\tPASSIVE_CAPTURE\n21\tcsgocases.com\tBLOCKED\tlog-1n.com\tCLEAN\t2017-11-27\tPASSIVE_CAPTURE\n22\tcsgogem.com\tBLOCKED\tapi.csgem.com\tCLEAN\t2014-03-08\tPASSIVE_CAPTURE\n23\tgamdom.com\tBLOCKED\tlogin.gambldom.com\tCLEAN\t2017-09-24\tPASSIVE_CAPTURE\n24\t12cs.fail\tBLOCKED\tfail.games\tCLEAN\t2021-08-24\tPASSIVE_CAPTURE\n25\tskinsnipe.com\tBLOCKED\tpricing.tradeupspy.com\tCLEAN\t2020-03-11\tPASSIVE_CAPTURE\n26\tcsgobig.com\tBLOCKED\tletmeinbig.com\tCLEAN\t2023-01-20\tPASSIVE_CAPTURE\n\n* Uwaga: Pasywne kontrole przeprowadzane na nieuwierzytelnionych punktach końcowych filtru linków Steam w witrynach 2026-09-19 oraz 2026-09-21.. Surowe treści odpowiedzi HTTP oraz skróty SHA-256 są zachowywane w zbiorze danych repozytorium (steam_tos_assets/linkfilter-2026-09-22.json).\n\nSekcja III: Księga wykazowa B — Kompleksowy spis podmiotów gospodarczych podlegających audytowi w ramach programu „175”NR REF.: EX-175-MASTER-CENSUS\n\nPoniższy rejestr zawiera szczegółowe informacje dotyczące wszystkich zewnętrznych platform komercyjnych typu „175”, które zostały aktywnie zweryfikowane w bazie danych audytowej. Każdy wpis zawiera nazwę podmiotu, główną domenę komercyjną, zaobserwowaną ścieżkę uwierzytelniania OpenID Steam, klasyfikację działalności, powiązania z naruszeniami umownymi (SSA § 2.G, SSA § 4.C, SSA § 1.C) oraz pole „działanie” odnotowane w zbiorze danych źródłowym. Oznaczenie „Zob. dowody z datą” odsyła czytelnika do dokumentacji uzupełniającej; nie oznacza ono, że Valve nie podjął żadnych działań. Brak pola działania jest zgłaszany jako „nieustalone”.\n\nZałącznik\tNazwa podmiotu i domena główna\tObserwowana trasa uwierzytelniania / serwer proxy\tKlasyfikacja\tNaruszenie umowy\tValve Akcja\nEX-001\tCSGORoll\ncsgoroll.com\n\t\nwww.csgoroll.com\nDIRECT\n\tSkin Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-002\tCSGOEmpire\ncsgoempire.com\n\t\ncsgoempirelogin4.com\nSPLIT PROXY\n\tCasino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-003\tRollbit\nrollbit.com\n\t\nrbsnin.com\nSPLIT PROXY\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-004\t500 Casino\n500.casino\n\t\nfivezerozero.co\nSPLIT PROXY\n\tLicenced Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-005\tCSGOBig\ncsgobig.com\n\t\ncsgobig.com\nDIRECT\n\tRoulette/Slots\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-006\tCaseDrop\ncasedrop.com\n\t\ncasedrop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-007\tRustReaper\nrustreaper.com\n\t\nrustreaper.com\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-008\tBanditCamp\nbanditcamp.com\n\t\nbanditcamp.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-009\tSkinBox\nskinbox.com\n\t\nskinbox.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-010\tTastyDrop\ntastydrop.com\n\t\ntastydrop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-011\tCSGOPolygon\ncsgopolygon.gg\n\t\ncsgopolygon.gg\nDIRECT\n\tRoulette Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-012\tMagicDrop\nmagicdrop.ru\n\t\nmagicdrop.ru\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-013\tCSDice\ncsdice.com\n\t\ncsdice.com\nDIRECT\n\tDice Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-014\tRustly\nrustly.com\n\t\nrustly.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-015\tSkinOdds\nskinodds.com\n\t\nskinodds.com\nDIRECT\n\tUpgrader Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-016\tCSGOWin\ncsgowin.com\n\t\ncsgowin.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-017\tCSGORun\ncsgorun.net\n\t\ncsgorun.net\nDIRECT\n\tCrash Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-018\tOpenSkins\nopenskins.com\n\t\nopenskins.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-019\tRustBet\nrustbet.com\n\t\nrustbet.com\nDIRECT\n\tRust Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-020\tCSGOMagic\ncsgomagic.com\n\t\ncsgomagic.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-021\tCSGOBounty\ncsgobounty.com\n\t\ncsgobounty.com\nDIRECT\n\tUpgrader/Contract\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-022\tEZSkins\nezskins.com\n\t\nezskins.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-023\tRustCases\nrustcases.com\n\t\nrustcases.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-024\tCSGOReaper\ncsgoreaper.com\n\t\ncsgoreaper.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-025\tCSGOCases\ncsgocases.com\n\t\ncsgocases.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-026\tCSGO-Skins\ncsgo-skins.com\n\t\ncsgo-skins.com\nDIRECT\n\tCase Upgrader\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-027\tCSGONet\ncsgonet.com\n\t\ncsgonet.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-028\tWTFSkins\nwtfskins.com\n\t\nwtfskins.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-029\tCSGOFast\ncsgofast.com\n\t\nsteam-login.authtofast.com\nSPLIT PROXY\n\tRoulette Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-030\tDuelbits\nduelbits.com\n\t\nswitchflips.com\nSPLIT PROXY\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-031\tFlameCases\nflamecases.com\n\t\nflamecases.com\nDIRECT\n\tCase Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-032\tFarmskins\nfarmskins.com\n\t\nsteam.kobal.cc\nSPLIT PROXY\n\tCase Opener\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-033\tCSGOLuck\ncsgoluck.com\n\t\ncsgoluck.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-034\tGamedom\ngamedom.com\n\t\ngamedom.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-035\tSkin.Club\nskin.club\n\t\nsc-auth.net\nSPLIT PROXY\n\tCase Battles\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-036\tDaddySkins\ndaddyskins.com\n\t\ndaddyskins.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-037\tInsane.gg\ninsane.gg\n\t\napi.insane.gg\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-038\tRustix\nrustix.gg\n\t\nrustix.gg\nDIRECT\n\tRust Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-039\tSkins.Club\nskins.club\n\t\nskins.club\nDIRECT\n\tSkin Upgrade\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-040\tCSGOHouse\ncsgohouse.org\n\t\ncsgohouse.org\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-041\tSkinRave\nskinrave.net\n\t\nskinrave.net\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-042\tBloodyCase_GG\nbloodycase.gg\n\t\nbloodycase.gg\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-043\tCSGOClicker\ncsgoclicker.com\n\t\ncsgoclicker.com\nDIRECT\n\tClicker/Upgrade\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-044\tRustBet_GG\nrustbet.gg\n\t\nrustbet.gg\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-045\tCS_Drop\ncs-drop.com\n\t\ncs-drop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-046\tHellStore\nhellstore.net\n\t\nhellstore.net\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-047\tRustLoot\nrustloot.com\n\t\nrustloot.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-048\tCSGO_Case\ncsgo-case.com\n\t\ncsgo-case.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-049\tCS2Skin\ncs2skin.com\n\t\ncs2skin.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-050\tJuice_GG\njuice.gg\n\t\nletmeinjuice.com\nSPLIT PROXY\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-051\tGGDrop\nggdrop.com\n\t\nggauth.com\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-052\tCSGOGem\ncsgogem.com\n\t\ncsgogem.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-053\tRainbet\nrainbet.com\n\t\nservices.rainbet.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-054\tHowl_GG\nhowl.gg\n\t\nhowl.uno\nSPLIT PROXY\n\tSkins Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-055\tChicken_GG\nchicken.gg\n\t\nchicken.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-056\tCSGOCasino_GG\ncsgocasino.gg\n\t\napi.csgocasino.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-057\tHunt_GG\nhunt.gg\n\t\napi.hunt.gg\nDIRECT\n\tSkins Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-058\tCSBattle\ncsbattle.com\n\t\ncsbattle.com\nDIRECT\n\tCase Battles\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-059\tSkinRave_GG\nskinrave.gg\n\t\napi.skinrave.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-060\tCSDouble\ncsdouble.gg\n\t\ncsdouble.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-061\tRustChance\nrustchance.com\n\t\nhgfuihd.com\nSPLIT PROXY\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-062\tRustClash\nrustclash.com\n\t\nrustclash.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-063\tCobaltLab\ncobaltlab.tech\n\t\ncobaltauth.com\nSPLIT PROXY\n\tRust Automation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-064\tRaided_GG\nraided.gg\n\t\napi.raided.gg\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-065\tRustNeo\nrustneo.gg\n\t\nrustneo.gg\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-066\tSplits_GG\nsplits.gg\n\t\nsplits.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-067\tUpgrader_Pro\nupgrader.pro\n\t\nupgauth.space\nSPLIT PROXY\n\tSkin Upgrader\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-068\tSkinFans\nskin.fans\n\t\nauth.skinfans.com\nSPLIT PROXY\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-069\tHotPizza\nhotpizza.one\n\t\nhotpizza.one\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-070\tG4Skins\ng4skins.com\n\t\nauth.g4s.to\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-071\t12CS_Fail\n12cs.fail\n\t\n12cs.fail\nDIRECT\n\tCrash Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-072\tTF2Royal\ntf2royal.com\n\t\ntf2auth.com\nSPLIT PROXY\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-073\tTF2Easy\nwww.tf2easy.com\n\t\nwww.tf2easy.com\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-074\tTF2Hunt\ntf2hunt.com\n\t\nrstspcl.com\nSPLIT PROXY\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-075\tTF2Bet\ntf2.bet/coinflip\n\t\ntf2.bet\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-076\tTF2Blaze\ntf2blaze.com\n\t\ntf2blaze.com\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-077\tOpenStars_GG\nopenstars.gg\n\t\nopenstars.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-078\tShuffle_Com\nshuffle.com\n\t\nshuffle.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-079\tSkins.com\nskins.com\n\t\napi.skins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-080\tWhite.Market\nwhite.market\n\t\nwhite.market\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-081\tBuff.Market\nbuff.market\n\t\nbuff.market\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-082\tAvan.Market\navan.market\n\t\navan.market\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-083\tCS.MONEY\ncs.money\n\t\nauth.dota.trade\nSPLIT PROXY\n\tTrading Engine\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-084\tUUSkins\nuuskins.com\n\t\nuuskins.com\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-085\tYouPin898\nyoupin898.com\n\t\nyoupin898.com\nDIRECT\n\tMass Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-086\tMoon.Market\nmoon.market\n\t\nmoon.market\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-087\tCSFloat\ncsfloat.com\n\t\ncsgofloat.com\nSPLIT PROXY\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-088\tSkin.Land\nskin.land\n\t\nauth.skin.land\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-089\tC5Game\nc5game.com\n\t\nc5game.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-090\tHaloSkins\nhaloskins.com\n\t\nhaloskins.com\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-091\tBuff.163\nbuff.163.com\n\t\nbuff.163.com\nDIRECT\n\tCorporate Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-092\tWaxpeer\nwaxpeer.com\n\t\nwaxpeer.com\nDIRECT\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-093\tCS.MONEY Bot\ncs.money\n\t\nauth.dota.trade\nSPLIT PROXY\n\tBot Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-094\tMarket.CSGO\nmarket.csgo.com\n\t\ndota2.net\nSPLIT PROXY\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-095\tSkinport\nskinport.com\n\t\nskinport.app\nSPLIT PROXY\n\tRegulated Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-096\tSkinFlow\nskinflow.gg\n\t\napi.skinflow.gg\nDIRECT\n\tMarketplace/Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-097\tDMarket\ndmarket.com\n\t\ndmarket.com\nDIRECT\n\tUS Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-098\tSkin.place\nskin.place\n\t\napi.skin.place\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-099\tSkinsMonkey\nskinsmonkey.com\n\t\nskinsmonkey.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-100\tSkinBaron\nskinbaron.de\n\t\nskinbaron.com\nSPLIT PROXY\n\tCorporate Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-101\tSteam\nsteamcommunity.com/market\n\t\nsteamcommunity.com/market\nDIRECT\n\tOfficial Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-102\tRustTM\nrust.tm\n\t\ndota2.net\nSPLIT PROXY\n\tRust Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-103\tPirateSwap\npirateswap.com\n\t\nlogin.pirateswap.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-104\tMannco.Store\nmannco.store\n\t\nmannco.store\nDIRECT\n\tTF2 Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-105\tSkinSwap\nskinswap.com\n\t\napi.skinswap.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-106\tLootFarm\nlootfarm.com\n\t\nlootfarm.com\nDIRECT\n\tTrading Platform\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-107\tRustskins\nrustskins.com\n\t\nrustskins.com\nDIRECT\n\tRust Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-108\tExeSkins\nexeskins.com\n\t\nexeskins.com\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-109\tBalticSkins\nbalticskins.com\n\t\nbalticskins.com\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-110\tCS.Trade\ncs.trade\n\t\ncs.trade\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-111\tRapidSkins\nrapidskins.com\n\t\napi.rapidskins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-112\tTradeIt\ntradeit.gg\n\t\nconnect-tradeit.com\nSPLIT PROXY\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-113\tKrakatoa\nkrakatoa.com\n\t\nkrakatoa.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-114\tShadowPay\nshadowpay.com\n\t\nshadowpay.com\nDIRECT\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-115\t49skins\n49skins.com\n\t\napi.49skins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-116\tSkinVault\nskinvault.gg\n\t\napi.skinvault.gg\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-117\tAim Market\naim.market\n\t\naim.market\nDIRECT\n\tSkins Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-118\tSkinout\nskinout.gg\n\t\nauth.skinout.gg\nDIRECT\n\tInstant Sell Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-119\tNTSkins\nntskins.com\n\t\nntskins.com\nDIRECT\n\tSkins Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-120\tIGXE\nigxe.cn\n\t\nigxe.cn\nDIRECT\n\tChinese Powerhouse\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-121\tSwap.gg\nswap.gg\n\t\nswap.gg\nDIRECT\n\tAutomated Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-122\tBitskins\nbitskins.com\n\t\nbitskins.com\nDIRECT\n\tCash-out Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-123\tGamerPay\ngamerpay.gg\n\t\ngamerpay.gg\nDIRECT\n\tP2P Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-124\tTF2Mart\ntf2mart.com\n\t\ntf2mart.com\nDIRECT\n\tTF2 Automation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-125\tSkinBid\nskinbid.com\n\t\nskinbid.com\nDIRECT\n\tSkin Auctions\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-126\tLootBear\nlootbear.com\n\t\nlootbear.com\nDIRECT\n\tSkin Rental\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-127\tBackpack.tf\nbackpack.tf\n\t\nbackpack.tf\nDIRECT\n\tTF2 Valuation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-128\tScrap.tf\nscrap.tf\n\t\nscrap.tf\nDIRECT\n\tTF2 Scrap Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-129\tMarketplace.tf\nmarketplace.tf\n\t\nmarketplace.tf\nDIRECT\n\tTF2 Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-130\tSTNTrading\nstntrading.eu\n\t\nstntrading.eu\nDIRECT\n\tTF2 Botnet\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-131\tSkins.Cash\nskins.cash\n\t\nskinscash.live\nSPLIT PROXY\n\tInstant Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-132\tSkinWallet\nskinwallet.com\n\t\nskinwallet.com\nDIRECT\n\tInstant Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-133\tDota2Market\ndota2market.com\n\t\ndota2market.com\nDIRECT\n\tDota 2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-134\tCSGO.NET\ncsgo.net\n\t\ncn2.easylot.net\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-135\tCybershoke\ncybershoke.net\n\t\nauth.cybershoke.net\nDIRECT\n\tCommunity Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-136\tXPlay_GG\nxplay.gg\n\t\nxplay.gg\nDIRECT\n\tServer Network\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-137\tFastCup\nfastcup.net\n\t\napi.fastcup.net\nDIRECT\n\tMatchmaker Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-138\tEsportal\nesportal.com\n\t\nesportal.com\nDIRECT\n\tMatchmaking Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-139\tGamersClub\ngamersclub.com.br\n\t\ngamersclub.com.br\nDIRECT\n\tLATAM Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-140\tLeetify\nleetify.com\n\t\nleetify.com\nDIRECT\n\tSaaS Analytics\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-141\tScope_GG\nscope.gg\n\t\nscope.gg\nDIRECT\n\tSaaS Analytics\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-142\tTradeUpSpy\ntradeupspy.com\n\t\napi.tradeupspy.com\nDIRECT\n\tSaaS Tools\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-143\tEpidemic_GG\nepidemic.gg\n\t\nepidemic.gg\nDIRECT\n\tSaaS Tools\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-144\tCSDeals\ncs.deals\n\t\napi.cs.deals\nDIRECT\n\tMarketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-145\tPricempire\npricempire.com\n\t\npricempire.com\nDIRECT\n\tSaaS Price DB\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-146\tCS2Stash\ncs2stash.com\n\t\ncs2stash.com\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-147\tCSGOSkins\ncsgoskins.gg\n\t\ncsgoskins.gg\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-148\tSteamAnalyst\nsteamanalyst.com\n\t\nsteamanalyst.com\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-149\tSteamCardExchange\nsteamcardexchange.net\n\t\nsteamcardexchange.net\nDIRECT\n\tTrading Exchange\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-150\tDotaBuff\ndotabuff.com\n\t\ndotabuff.com\nDIRECT\n\tSaaS Tracker\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-151\tTracker_GG\ntracker.gg\n\t\ntracker.gg\nDIRECT\n\tSaaS Tracker\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-152\tFSB Market (an anonymized label; the original name is withheld here)\nFSB Market\n\t\nFSB Market\nDIRECT\n\tMass Blackmarket\tSSA § 2.G, SSA § 4.C, SSA § 1.C\tSee dated evidence\nEX-153\tFunPay\nfunpay.com\n\t\nfunpay.com\nDIRECT\n\tAccount Exchange\tSSA § 2.G, SSA § 4.C, SSA § 1.C\tSee dated evidence\nEX-154\tPlayerAuctions\nplayerauctions.com\n\t\nplayerauctions.com\nDIRECT\n\tGrey Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-155\tEldorado.gg\neldorado.gg\n\t\neldorado.gg\nDIRECT\n\tAccount Portal\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-156\tG2A\ng2a.com\n\t\ng2a.com\nDIRECT\n\tMass Key Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-157\tKinguin\nkinguin.net\n\t\nkinguin.net\nDIRECT\n\tMass Key Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-158\tG2G.com\ng2g.com\n\t\ng2g.com\nDIRECT\n\tVirtual Services\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-159\tPlayerup\nplayerup.com\n\t\nplayerup.com\nDIRECT\n\tAccount Broker\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-160\tZ2U.com\nz2u.com\n\t\nwww.z2u.com\nDIRECT\n\tReady-Account Hub\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-161\tSmurfHub\nsmurfhub.net\n\t\nsmurfhub.net\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-162\tSmurfAccounts\nsmurfaccounts.com\n\t\nsmurfaccounts.com\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-163\tBuyCSGORank\nbuycsgorank.com\n\t\nbuycsgorank.com\nDIRECT\n\tRank Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-164\tCSGOSmurfKings\ncsgosmurfkings.com\n\t\ncsgosmurfkings.com\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-165\tSmurfStore_Co\nsmurfstore.co\n\t\nsmurfstore.co\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-166\tSteamLvlUp\nsteamlvlup.com\n\t\nsteamlvlup.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-167\tSteamLevels\nsteamlevels.com\n\t\nsteamlevels.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-168\tLevelSteam\nlevelsteam.com\n\t\nlevelsteam.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-169\tSteamLevelU\nsteamlevelu.com\n\t\nsteamlevelu.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-170\tEloKing\neloking.com\n\t\neloking.com\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-171\tBoosteria\nboosteria.org\n\t\nboosteria.org\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-172\tOvergear\novergear.com\n\t\novergear.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-173\tBlazingBoost\nblazingboost.com\n\t\nblazingboost.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-174\tDota2Boost\ndota2boost.com\n\t\ndota2boost.com\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-175\tBuyBoost\nbuyboost.com\n\t\nbuyboost.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nCzęść IV: Architektura techniczna i mechanizmy uwierzytelnianiaŹRÓDŁO: TECH-ANALYSIS-01\n\n1. Brak weryfikacji własności domeny w OpenID 2.0: Implementacja protokołu OpenID 2.0 przez Valve (https://steamcommunity.com/openid/login) ocenia openid.return_to oraz openid.realm parametry bez konieczności wcześniejszej rejestracji programisty, weryfikacji hasła kryptograficznego ani potwierdzenia własności domeny. Każdy operator komercyjny może przekierować użytkowników na ekran logowania serwisu Valve i otrzymać kryptograficznie podpisane oświadczenie o tożsamości (zawierające identyfikator SteamID typu „64-”) przekierowane na dowolne domeny.\n\n2. Programowe zapytania o zasoby reklamowe oraz nadużycia związane z kluczem „API”: Po potwierdzeniu uwierzytelnienia użytkownika za pomocą OpenID operatorzy wysyłają zapytania do publicznych i partnerskich punktów końcowych serwisu API (IEconItems_730/GetPlayerItems) w celu indeksowania aktywów zapasowych w czasie rzeczywistym. Zautomatyzowane sieci handlowe wykorzystują programowe tokeny sesji do składania, sprawdzania i przyjmowania ofert handlowych typu peer-to-peer (P2P), co stanowi bezpośrednie naruszenie zakazu interakcji z podmiotami innymi niż ludzie, zawartego w §4.C ustawy SSA.\n\n3. Asymetria filtra łącza: Współistnienie ostrzeżeń dotyczących domen skierowanych do konsumentów oraz w pełni działających punktów końcowych uwierzytelniania powoduje sprzeczność regulacyjną: dane telemetryczne dotyczące bezpieczeństwa serwisu Valve klasyfikują tych operatorów jako „potencjalnie złośliwych”, jednak infrastruktura uwierzytelniająca serwisu Valve nadal uwierzytelnia ich użytkowników.\n\nMetodologia dowodowa i oświadczenie dotyczące łańcucha dowodowego\n\nNiniejszy dokument powstał na podstawie nieautoryzowanych przechwyceń sieciowych, historycznych zapytań do rejestru RDAP oraz zweryfikowanych manifestów skrótów kryptograficznych. Żadne dane logowania użytkowników nie zostały poddane testom na naruszenie bezpieczeństwa ani przetworzone. Wszystkie ustalenia odzwierciedlają obserwowalny stan sieci produkcyjnej na dzień 2026. Niniejszy dokument stanowi bezstronną ekspertyzę techniczną przygotowaną na potrzeby postępowań sądowych, regulacyjnych oraz zapytań publicznych.\n\nPODSUMOWANIE: SHA-256 – ZWERYFIKOWANE\nc507c9025f93da0aadaf395c4d8882f25973211c318ee8e9b6f18a5b3755e050\nARCHIWUM: JAWNE AKTA SPRAWY\nWYDAŁ I PODPISAŁ: phishdestroy.io · Koalicja na rzecz Badań Kryminalistycznych\nSTATUS PRAWNY: WSZYSTKIE PRAWA PRZEKAZANE LUDZKOŚCI · CC0 DOMENA PUBLICZNA UNIVERSAL",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Ustawa o audycie kryminalistycznym i załącznik regulacyjny"
          }
        ],
        "links": []
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/pl/regulatory_act_print.content.json",
      "export_json_sha256": "3430cec83a8de83ef2cc153727aeb7e5b6c14a55ce361f436b5eab44e4b51665"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "pl/security_timeline.html",
      "language": "pl",
      "title": "Kalendarium wydarzeń związanych z bezpieczeństwem — Dokumentacja dotycząca „Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/pl/security_timeline",
      "source_html_sha256": "13c80009a7a4bd50262e4c5bd033330d2a36b931e90b5daac4a5a9532757ca11",
      "exported_at": "2026-09-29T00:19:01.464Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "security_timeline.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/pl/security_timeline.pdf?v=print-20260929-v5",
        "sha256": "844864fc0fced164915adbe2191fc2dba00c35bdc3bc5fa32f7f097bf407e3d6",
        "bytes": 104520,
        "pages": 7
      },
      "integrity": {
        "signed_object": "security_timeline.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "security_timeline.content.json.asc",
        "digest_file": "security_timeline.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify security_timeline.content.json.asc security_timeline.content.json",
          "sha256sum -c security_timeline.content.json.sha256"
        ]
      },
      "content": {
        "text": "HISTORIA BEZPIECZEŃSTWAWYSTAWA / PRACE Z KONKURSU „16”\n\n2018 — 2026\n\nKalendarium zmian w zabezpieczeniach — od „2018” do „2026”\n\nZmiany w zakresie bezpieczeństwa. Postępuj zgodnie z zapisem.\n\nCO WYKAZUJE TA CZĘŚĆ\n\nNiniejszy zapis chronologiczny przedstawia osiem lat zmian w zabezpieczeniach stosu transakcyjnego i uwierzytelniającego serwisu Steam. Obejmuje on wdrożenie 2018 7-mechanizmu blokady dziennej transakcji, 2023 potwierdzeń kluczem mobilnym API oraz 2026 wycofanie tokenów sesyjnych w odpowiedzi na udokumentowane techniki omijania zabezpieczeń. Oś czasu wskazuje, że aktualizacje platformy konsekwentnie pozostawały w tyle za znanymi wektorami ataków, zachowując jednocześnie korzyści strukturalne dla operatorów komercyjnych.\n\n← Powrót do podsumowania dla kadry kierowniczej\n\nBlokady transakcji. Kontrola logowania. Ograniczenia dotyczące „API”. Aktualny zapis tego, co uległo zmianie — oraz tego, co faktycznie wynika ze źródeł.\n\nZapoznaj się z osią czasu ↓\nOSIEM LAT. JEDEN ALBUM.16kamienie milowe, które należy przeanalizować\n\nKażdy wpis zachowuje datę zgłoszenia i źródło. Obok niego wyświetlana jest informacja o weryfikacji.\n\nSPRAWDZONE / 24 09.2026\n10Potwierdzone wydarzenie i data\n06Częściowo zweryfikowane\n00Niezgodność źródła\n00Potrzebne źródło\nJak odczytać ten zapis\n\nZweryfikowane wydarzenie i data: oba poparte wiarygodnym źródłem pierwotnym. Częściowo zweryfikowane: udokumentowano powiązaną zmianę, ale data lub zakres pozostają nieokreślone. Niezgodność źródła: materiał, do którego prowadzi link, nie potwierdza przedstawionego twierdzenia. Potrzebne źródło: W ramach niniejszego przeglądu nie zweryfikowano żadnego pasującego źródła z podaną datą. Brak potwierdzenia danego wpisu nie stanowi dowodu na to, że wydarzenie nie miało miejsca.\n\nDaty przy wpisach nierozstrzygniętych to daty zgłoszenia, a nie zweryfikowane daty publikacji. Oryginalny tekst dochodzenia nie został zmieniony.\n\nChronologia\n01 — 16\nPrzeszukaj wpisTematDowodyZamówienie\n\n16 z wpisów na stronie 16 · najnowsze najpierw\n\n202609-01Data złożenia\nSpołecznośćCzęściowo zweryfikowane\nOstrzeżenia o podejrzanych wiadomościach w czatach grupowych\n\nOficjalne ogłoszenie dotyczące wersji beta potwierdza wprowadzenie tej funkcji w dniu 31 sierpnia. Podana data stabilnej premiery 1 września nadal wymaga szczegółowej notatki dotyczącej wydania.\n\nSteam Wersja beta dla klientów — 1 sierpnia 31 ↗zarchiwizowano 2026-03-13 ↗\nOryginalny wpis i przesłany link\n\nAutomatyczne oznaczanie podejrzanych rozmów\n\nSprawdź przesłany kod źródłowy ↗\n202601-16Data weryfikacji\nAPIPotwierdzone wydarzenie i data\nSzczegółowe uprawnienia i biała lista adresów IP dla kluczy wydawcy (ogłoszenie dotyczące Valve)\n\nW dniu 16 stycznia 2026, Valve opublikowano oficjalne ogłoszenie dotyczące Steamworks („NOWOŚĆ: Ulepszone uprawnienia i opcje kontroli dla kluczy WebAPI”) potwierdzające wprowadzenie nowych narzędzi do precyzyjnego zarządzania uprawnieniami, które umożliwiają programistom podział kluczy „WebAPI” na odrębne grupy (Ogólne informacje, mikrotransakcje, ekonomia i dane dotyczące sprzedaży), ograniczyć klucze do określonych identyfikatorów aplikacji oraz egzekwować stosowanie białej listy adresów IP serwerów.\n\nRażąca podwójna moralność: W niniejszym oficjalnym komunikacie stwierdza się, że serwis Valve w pełni wdrożył infrastrukturę techniczną umożliwiającą precyzyjne zarządzanie uprawnieniami w ramach funkcji „API” oraz stosowanie ograniczeń adresów IP, jednak celowo nie udostępnia ich zwykłym kontom użytkowników (steamcommunity.com/dev/apikey). Standardowe klucze użytkownika typu „API” pozostają monolitycznymi poświadczeniami typu „wszystko albo nic”, bez białej listy adresów IP — a właśnie to techniczne zaniedbanie umożliwia funkcjonowanie wartej wiele milionów dolarów branży zajmującej się przechwytywaniem transakcji typu „API”.\n\nValve Ogłoszenie — NOWOŚĆ: Lepsze uprawnienia i mechanizmy kontroli dla kluczy Web API (16 Jan 2026) ↗· Dokumentacja: Uwierzytelnianie w serwisie Steamworks Web API ↗\nOryginalny wpis i przesłany link\n\nStrona internetowa Steamworks: API – szczegółowe zakresy\n\nZapoznaj się z oficjalnym ogłoszeniem dotyczącym Steamworks w grze „Valve” (493839547938902179) ↗\n202507-15Data weryfikacji\nHandelPotwierdzone wydarzenie i data\nTransakcje na CS2 zyskują siedmiodniowe okno na odwrócenie trendu\n\nW opublikowanym komunikacie Valve ogłoszono cofnięcie transakcji dotyczących przedmiotów w grze Counter-Strike z ostatnich siedmiu dni. Chociaż rozwiązanie to ma na celu ograniczenie przypadków przejęcia kont, zewnętrzne audyty ekonomiczne (CSMarketCap ↗) odnotowała $104M (-25%) zwinąć pod względem kapitalizacji rynkowej w ciągu godzin sesji „24” z powodu zakłóceń w obrocie gotówkowym. Jak wynika z analizy przeprowadzonej przez Skinvault ↗, a uruchomienie funkcji odwrócenia powoduje automatyczne nałożenie na konto blokady na transakcje jednodniowe (30-). Latem 2026, Valve przeszło z globalnego resetowania o północy czasu UTC na indywidualne minutowe liczniki dla poszczególnych pozycji (Skin.land ↗).\n\nValve — 15, lipiec 2025, komunikat prasowy ↗· Analiza CSMarketCap ↗\nOryginalny wpis i przesłany link\n\nOchrona transakcji CS2 / Okno cofnięcia transakcji\n\nSprawdź przesłany kod źródłowy ↗\n202505-14Data weryfikacji\nUwierzytelnianiePotwierdzone wydarzenie i data\nValve opublikował ostrzeżenie dotyczące bezpieczeństwa kont w związku z wyciekami wiadomości SMS\n\nOficjalny komunikat serwisu Valve z 14, 2025, dotyczy bezpieczeństwa kont oraz uwierzytelniania za pomocą wiadomości SMS. Chociaż komunikat skupia się na wyciekach wiadomości SMS i potwierdza, że nie doszło do włamania do systemów Steam, stanowi on oficjalną aktualizację dotyczącą bezpieczeństwa z podanej daty.\n\nValve — Informacja dotycząca bezpieczeństwa Twojego konta Steam ↗\nOryginalny wpis i przesłany link\n\nKomunikat dotyczący bezpieczeństwa konta\n\nSprawdź przesłany kod źródłowy ↗\n202410-02Data weryfikacji\nHandelPotwierdzone wydarzenie i data\nSiedem dni przed ponowną sprzedażą lub wprowadzeniem na rynek\n\nInformacje o aktualizacji obejmują przedmioty nabyte w sklepie w grze, w tym w Zbrojowni, w ramach ofert wymiany oraz na rynku społecznościowym. Zakres opisanych zmian wykracza poza same przedmioty ze Zbrojowni.\n\nValve — Informacje o aktualizacji programu „10/2/2024” ↗\nOryginalny wpis i przesłany link\n\nCS2: The Armory / Dzień zamknięcia „7-”\n\nSprawdź przesłany kod źródłowy ↗\n202409-18Data złożenia\nHandelCzęściowo zweryfikowane\nOgraniczenia dotyczące nowych urządzeń – informacje na stronach pomocy\n\nOficjalna dokumentacja pomocy technicznej serwisu Steam potwierdza ograniczenie dotyczące handlu dziennego (day trading) na stronie 7-w przypadku logowania się z nowego urządzenia, które nie było autoryzowane przez co najmniej 7 dni. Chociaż dokładna data wprowadzenia tej zmiany we wrześniu 18, 2024, nie została odnotowana jako kamień milowy w dzienniku zmian, funkcjonalność ta jest w pełni udokumentowana.\n\nSteam Pomoc — Ograniczenia dotyczące handlu i rynku ↗\nOryginalny wpis i przesłany link\n\nOgraniczenia dotyczące logowania nowych urządzeń\n\nSprawdź przesłany kod źródłowy ↗\n202402-14Data złożenia\nSpołecznośćCzęściowo zweryfikowane\nWprowadzono czas oczekiwania na zmianę nazwy w pliku 2024\n\nZapisy społeczności i deweloperów potwierdzają, że na początku 2024, Valve wprowadzono bez uprzedzenia 2-godzinny okres blokady4 bezpośrednio po zmianie nazwy profilu, aby ograniczyć oszustwa polegające na szybkim podszywaniu się pod inne osoby. Ponieważ Valve nie opublikowało żadnego oficjalnego komunikatu prasowego, listy zmian w kliencie ani artykułu pomocy technicznej dotyczącego tego ograniczenia, podana data z lutego 14 nie została formalnie zweryfikowana; przewodnik Steam Workshop stanowi raczej pośrednie potwierdzenie ze strony społeczności niż oficjalną Valve dokumentację.\n\nSteam Przewodnik po warsztatach (potwierdzenie pośrednie) — Szczegóły dotyczące ograniczeń dotyczących zmiany nazwy ↗\nOryginalny wpis i przesłany link\n\nWstrzymanie zmiany nazwy profilu / awatara\n\nSprawdź przesłany kod źródłowy ↗\n202312-04Data weryfikacji\nAPIPotwierdzone wydarzenie i data\nUtworzenie klucza wymaga potwierdzenia za pomocą telefonu komórkowego\n\nPotwierdzono, że obowiązkowe potwierdzanie za pomocą aplikacji mobilnej Steam Guard podczas generowania kluczy w serwisie API zostało wprowadzone pod koniec 2023,, co potwierdzają biblioteki programistyczne stron trzecich. Dokładna data 4, 2023, odpowiada okresowi wdrażania zaobserwowanemu w środowisku programistów.\n\nDokumentacja opiekuna — marzec 2024 ↗zarchiwizowano 2026-09-24 ↗\nOryginalny wpis i przesłany link\n\nPotwierdzenie na telefonie komórkowym dla kluczy „API”\n\nSprawdź przesłany kod źródłowy ↗\n202310-24Data weryfikacji\nProgramistaPotwierdzone wydarzenie i data\nWchodzi w życie obowiązkowa procedura „2” dotycząca zatwierdzania konfiguracji gry na serwerach live\n\nOficjalny komunikat Valve dotyczący Steamworks z dnia 10, 2023, potwierdza, że od dnia 24, 2023, każde konto, które uruchamia kompilację w gałęzi domyślnej wydanej aplikacji, musi autoryzować tę zmianę za pomocą wiadomości SMS lub aplikacji mobilnej Steam. Zmiana ta spowodowała bezpośrednią aktualizację strony internetowej SetAppBuildLive API.\n\nSteamworks — Ulepszenia w zakresie bezpieczeństwa dotyczące zarządzania kompilacjami i użytkownikami ↗zarchiwizowano 2025-12-03 ↗\nOryginalny wpis i przesłany link\n\nSMS MFA w publikacjach dotyczących kompilacji gier\n\nSprawdź przesłany kod źródłowy ↗\n202307-12Data złożenia\nSpołecznośćCzęściowo zweryfikowane\nOstrzeżenia dotyczące treści w biografiach użytkowników, na które zwraca uwagę społeczność\n\nSteam Zgłoszenia użytkowników społeczności, pojawiające się od lipca 2023, wskazują, że w spersonalizowanych opisach profili zawierających linki zewnętrzne lub słowa wyzwalające zaczęły wyświetlać się automatyczne ostrzeżenia dotyczące treści. Data zgłoszenia z lipca 12, 2023, pokrywa się z pierwszą falą zgłoszeń użytkowników na forach społecznościowych Steam.\n\nSteam Forum społeczności — Zgłoszenia dotyczące ostrzeżeń o treściach związanych z biografiami ↗\nOryginalny wpis i przesłany link\n\nOstrzeżenie dotyczące treści biografii tworzonej na zamówienie\n\nSprawdź przesłany kod źródłowy ↗\n202301-25Data złożenia\nSpołecznośćCzęściowo zweryfikowane\nAktywne są ograniczenia czasu na filtrowanie i edycję linków w profilu\n\nOficjalna dokumentacja pomocy serwisu Steam potwierdza, że linki w niestandardowych biografiach są filtrowane, a nadużycia związane ze zmianą nazwy lub awatara mogą skutkować blokadą możliwości edycji. Chociaż dokładne wprowadzenie godzinnego okresu oczekiwania 4-w dniu 1 stycznia 25, 2023, stanowi obserwowany początek tego zjawiska, sam mechanizm filtrowania linków jest w pełni aktywny, jak wynika z opublikowanej strony pomocy.\n\nSteam Pomoc techniczna — Ograniczenia dotyczące nazwy profilu i awatara ↗\nOryginalny wpis i przesłany link\n\nProfil – LINK USUNIĘTY / Czas odnowienia\n\nSprawdź przesłany kod źródłowy ↗\n202210-24Data weryfikacji\nUwierzytelnianiePotwierdzone wydarzenie i data\nSteam Przejście klienta na tokeny odświeżające i dostępowe OAuth\n\nNajważniejsze aktualizacje serwisu Valve oraz aplikacji mobilnej w październiku 2022 gruntownie przebudowało system uwierzytelniania Steam. Dotychczasową strukturę plików cookie sesji zastąpiono tokenami dostępu i odświeżania opartymi na protokole OAuth, a także wprowadzono listę aktywnych, autoryzowanych urządzeń, umożliwiającą ręczne unieważnianie aktywnych sesji.\n\nValve — Aktualizacja aplikacji mobilnej „Steam” i gruntowna zmiana systemu uwierzytelniania ↗\nOryginalny wpis i przesłany link\n\nSteam Przebudowa systemu logowania / Skracanie plików cookie\n\nZapoznaj się z ogłoszeniem na stronie Valve ↗\n202210-12Data weryfikacji\nUwierzytelnianiePotwierdzone wydarzenie i data\nLogowanie za pomocą kodu QR i zarządzanie autoryzowanymi urządzeniami\n\nW opublikowanym w październiku przez Valve ogłoszeniu dotyczącym usługi „12” opisano logowanie za pomocą kodów QR, zatwierdzanie lub odrzucanie logowań oraz listę urządzeń, z których można cofnąć dostęp do konta.\n\nValve — Zaktualizowana aplikacja mobilna „Steam” jest już dostępna ↗\nOryginalny wpis i przesłany link\n\nSteam Aplikacja mobilna 3.0 / Logowanie za pomocą kodu QR\n\nSprawdź przesłany kod źródłowy ↗\n202205-10Data złożenia\nAPICzęściowo zweryfikowane\nPunkty końcowe dotyczące anulowania transakcji zostały usunięte z publicznej listy API\n\nZ danych deweloperów wynika, że w maju 2022, Valve po cichu usunięto punkty końcowe związane z zarządzaniem transakcjami, takie jak IEconService/CancelTradeOffer i DeclineTradeOffer, z serwisu API (udokumentowano to w wątkach node-steam-tradeoffer-manager #325). Chociaż metody te nadal działają w prywatnych protokołach klienckich, data 5 maja 10, 2022, oznacza ich faktyczne usunięcie z publicznych interfejsów API w celu zwalczania oszukańczych paneli.\n\nDyskusja deweloperów — Problem nr325 (usunięto funkcję „CancelTradeOffer”) ↗· Strona internetowa Steamworks API — Dokumentacja IEconService ↗\nOryginalny wpis i przesłany link\n\nUsunięcie punktów końcowych związanych z anulowaniem transakcji\n\nZobacz zgłoszenie nr325 dotyczące modułu node-steam-tradeoffer-manager ↗\n202005-25Data weryfikacji\nHandelPotwierdzone wydarzenie i data\nPrzedmioty w grze „Dota2” mają siedmiodniowy okres blokady handlu\n\nW dniu 25, 2020,, wraz z premierą przepustki bitewnej turnieju The International 10 (blog.dota2.com/2020/05/the-international-10-battle-pass/), serwis Valve wprowadził 7-jednodniowy blokadę wymiany przedmiotów w grze Dota 2, zgodnie z zasadami obowiązującymi w grze 2018 Counter-Strike. Ograniczenie to dotyczy wszystkich przedmiotów wymienianych oraz zakupionych na rynku.\n\nSpołeczność Dota 2 — blokada wymiany oraz aktualizacja klienta TI10 ↗\nOryginalny wpis i przesłany link\n\nDota 2 / 7-Blokada transakcji dziennych\n\nSprawdź przesłany kod źródłowy ↗\n201803-29Data weryfikacji\nHandelPotwierdzone wydarzenie i data\nPrzedmioty z gry CS:GO, które zostały wymienione, podlegają siedmiodniowemu okresowi blokady\n\nOficjalne informacje o wydaniu potwierdzają datę i ograniczenie. Podany adres URL przekierowywał do aktualizacji mapy pod adresem 2013; adres URL odpowiadający informacjom o wydaniu kończy się na 20309.\n\nValve — Informacje o aktualizacji „3/29/2018” ↗\nOryginalny wpis i przesłany link\n\nCS:GO / Blokada transakcji dziennych w trybie „7-”\n\nSprawdź przesłany kod źródłowy ↗ zarchiwizowano 2025-02-26 ↗\n\nKieruj się dowodami. Sprawdź źródło.\n\nPowrót do śledztwa ↗",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Kalendarium zmian w zabezpieczeniach — od „2018” do „2026”"
          },
          {
            "level": 2,
            "id": null,
            "text": "Chronologia"
          },
          {
            "level": 2,
            "id": null,
            "text": "Ostrzeżenia o podejrzanych wiadomościach w czatach grupowych"
          },
          {
            "level": 2,
            "id": null,
            "text": "Szczegółowe uprawnienia i biała lista adresów IP dla kluczy wydawcy (ogłoszenie dotyczące Valve)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Transakcje na CS2 zyskują siedmiodniowe okno na odwrócenie trendu"
          },
          {
            "level": 2,
            "id": null,
            "text": "Valve opublikował ostrzeżenie dotyczące bezpieczeństwa kont w związku z wyciekami wiadomości SMS"
          },
          {
            "level": 2,
            "id": null,
            "text": "Siedem dni przed ponowną sprzedażą lub wprowadzeniem na rynek"
          },
          {
            "level": 2,
            "id": null,
            "text": "Ograniczenia dotyczące nowych urządzeń – informacje na stronach pomocy"
          },
          {
            "level": 2,
            "id": null,
            "text": "Wprowadzono czas oczekiwania na zmianę nazwy w pliku 2024"
          },
          {
            "level": 2,
            "id": null,
            "text": "Utworzenie klucza wymaga potwierdzenia za pomocą telefonu komórkowego"
          },
          {
            "level": 2,
            "id": null,
            "text": "Wchodzi w życie obowiązkowa procedura „2” dotycząca zatwierdzania konfiguracji gry na serwerach live"
          },
          {
            "level": 2,
            "id": null,
            "text": "Ostrzeżenia dotyczące treści w biografiach użytkowników, na które zwraca uwagę społeczność"
          },
          {
            "level": 2,
            "id": null,
            "text": "Aktywne są ograniczenia czasu na filtrowanie i edycję linków w profilu"
          },
          {
            "level": 2,
            "id": null,
            "text": "Steam Przejście klienta na tokeny odświeżające i dostępowe OAuth"
          },
          {
            "level": 2,
            "id": null,
            "text": "Logowanie za pomocą kodu QR i zarządzanie autoryzowanymi urządzeniami"
          },
          {
            "level": 2,
            "id": null,
            "text": "Punkty końcowe dotyczące anulowania transakcji zostały usunięte z publicznej listy API"
          },
          {
            "level": 2,
            "id": null,
            "text": "Przedmioty w grze „Dota2” mają siedmiodniowy okres blokady handlu"
          },
          {
            "level": 2,
            "id": null,
            "text": "Przedmioty z gry CS:GO, które zostały wymienione, podlegają siedmiodniowemu okresowi blokady"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/pl/#briefing-heading",
          "https://steamcommunity.com/groups/SteamClientBeta?l=english",
          "http://web.archive.org/web/20260313235409/https://steamcommunity.com/groups/SteamClientBeta?l=english",
          "https://store.steampowered.com/news/posts/?enddate=1788390000",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/493839547938902179",
          "https://partner.steamgames.com/doc/webapi_overview/auth",
          "https://csmarketcap.com/blog/market-insights/from-boom-to-bust-cs2s-trade-protection-impact",
          "https://skinvault.gg/blog/cs2-trade-protection-explained/",
          "https://skin.land/blog/steam-changes-cs2-trade-ban-logic-timing/",
          "https://store.steampowered.com/news/posts/?appids=730&amp;enddate=1753924057&amp;feed=steam_announce%2F1000",
          "https://help.steampowered.com/faqs/view/3041-A87A-E5F6-B6AC",
          "https://store.steampowered.com/news/posts/?enddate=1747349559",
          "https://steamcommunity.com/ogg/593110/announcements/detail/533224478739530146",
          "https://store.steampowered.com/news/posts/?appids=730&amp;enddate=1728000977&amp;feed=steam_community_announcements",
          "https://steamcommunity.com/games/CSGO/announcements/detail/4447966961421256740",
          "https://help.steampowered.com/faqs/view/7F77-9E92-31E0-6B8E",
          "https://steamcommunity.com/sharedfiles/filedetails/?id=2926756889",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "http://web.archive.org/web/20260924181824/https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "https://steamcommunity.com/dev/apikey",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3749866608167579206",
          "http://web.archive.org/web/20251203174259/https://steamcommunity.com/groups/steamworks/announcements/detail/3749866608167579206",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3734103130194459461",
          "https://steamcommunity.com/discussions/forum/1/3807266184852932971/",
          "https://help.steampowered.com/faqs/view/225C-C51E-B8F0-55B2",
          "https://store.steampowered.com/news/group/4/view/3314112260640237775",
          "https://store.steampowered.com/news/posts/?appgroupname=Keep+in+touch&amp;enddate=1666122699&amp;feed=steam_blog",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/issues/325",
          "https://partner.steamgames.com/doc/webapi/IEconService",
          "https://steamcommunity.com/app/570/announcements/",
          "https://blog.dota2.com/2020/05/trading-cooldown/",
          "https://blog.counter-strike.net/2018/03/20309/",
          "https://blog.counter-strike.net/index.php/2018/03/20308/",
          "http://web.archive.org/web/20250226114333/https://blog.counter-strike.net/index.php/2018/03/20308/",
          "https://phishdestroy.io/steam_dossier/pl/#vulnerability-profile"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/pl/security_timeline.content.json",
      "export_json_sha256": "71b24717d7a160764e2f1cdf7e2e86041eab13792d19a12a52f0b3eeaff2a9fb"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "pl/skin_atlas.html",
      "language": "pl",
      "title": "Atlas rzeczy, których „Steam” nie może przewozić — Dossier „Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/pl/skin_atlas",
      "source_html_sha256": "afd509dfead188353ce909137032ee506ad943fb3f80566e378861f268d080d8",
      "exported_at": "2026-09-29T00:19:06.311Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "gallery",
            "source": "https://phishdestroy.io/steam_dossier/pl/skin_atlas#gallery"
          }
        ],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "skin_atlas.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/pl/skin_atlas.pdf?v=print-20260929-v5",
        "sha256": "bb9f4b55017ef15ce17295c8f7acd968ea4ed7fe6d3e44f9593e52e73bbce642",
        "bytes": 185857,
        "pages": 14
      },
      "integrity": {
        "signed_object": "skin_atlas.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "skin_atlas.content.json.asc",
        "digest_file": "skin_atlas.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify skin_atlas.content.json.asc skin_atlas.content.json",
          "sha256sum -c skin_atlas.content.json.sha256"
        ]
      },
      "content": {
        "text": "ZAŁĄCZNIK IV-B / SKALA CENOWA / 2026-09-23\nAtlas drabiny cenowej Skin — „Klif płynności”\n\nPunkty sprzedaży Valve skąd biorą się pieniądze.\n\nCO WYKAZUJE TA CZĘŚĆ\n\nW niniejszym atlasie wizualnym przeanalizowano kategorie produktów serwisu 30,266 w pięciu katalogach platform handlowych, oceniając zasięg rynkowy zarówno powyżej, jak i poniżej progu wystawiania ofert określonego przez serwis Valve. Poniżej limitu1,800, Steam obsługuje 95.3% aktywnych kategorii; tuż powyżej tego limitu oficjalny zasięg spada do 1.9% (przy zasięgu 0.0% obejmującym zweryfikowane aktywa). Świadczy to o gwałtownym, strukturalnym spadku płynności, w ramach którego Valve przekazuje wyszukiwanie transakcji o wysokiej wartości platformom zewnętrznym, zachowując jednocześnie pełną kontrolę nad przechowywaniem aktywów bazowych.\n\n← Powrót do podsumowania dla kadry kierowniczej\n\nKażdy przedmiot z gry CS2, którego cena była aktualnie podana na pięciu platformach handlowych, został przypisany do przedziału cenowego na podstawie najniższej ceny sprzedaży, a każdy przedział oceniano pod kątem jednego czynnika: jakiego udziału w nim nadal stanowi własny Rynek Społecznościowy serwisu Valve. Poniżej limitu ofert serwisu Valve odpowiedź brzmi: 95.3%. Powyżej znajduje się odpowiedź: 1.9%. Spadek ten nie jest stopniowy i nie następuje tam, gdzie spada popyt — następuje dokładnie zgodnie z opublikowaną zasadą. Spośród 248 kategorie produktów, w których co najmniej dwa serwisy handlowe niezależnie od siebie ustalają ceny powyżej limitu, 100.0% nie mają w ogóle żadnych ofert na stronie Steam.\n\nZobacz klif ↓Otwórz galerię produktów z serii „419”Metoda i ograniczenia\n30,266zmierzone kategorie produktów\n95.3%pozycji poniżej limitu kapitałowego wykazanych przezSteam\n1.9%pozycji przekraczających limit, w których asortymencie znajduje się firma „Steam”\n$78.6Mwartość dolna zbioru potwierdzonego\n01 / pomiar\nKlif opiera się na zasadzie, a nie na żądaniu\n\nKażda z poniższych kategorii produktów serwisu 30,266 jest przypisana do danego przedziału na podstawie jej najtańszy Dane pochodzą z serwisów BUFF163, CSFloat, Skinport, YouPin 898 oraz C5Game, a uwzględniane są wyłącznie pozycje wymienione w co najmniej dwóch z nich, więc żadna pojedyncza, zawyżona oferta nie może „wymyślić” członka zespołu. Górny wykres przedstawia udział każdego zespołu w rynku serwisu Valve.\n\nUdział poszczególnych przedziałów cenowych oferowanych na targu „Steam”\ngóra: zasięg pary · dół: liczba elementów w każdym paśmie, skala logarytmiczna\n0%\n25%\n50%\n75%\n100%\n100%\n96.9%\n95.9%\n97.3%\n91.1%\n76.8%\n14.5%\n2.9%\n1.5%\n0%\n0%\n0%\n4,632\n1¢–10¢\n7,152\n10¢–$1\n8,568\n$1–10\n5,941\n$10–100\n2,329\n$100–300\n1,292\n$300–1k\n193\n$1k–1.8k\n70\n$1.8k–3k\n67\n$3k–10k\n18\n$10k–30k\n3\n$30k–100k\n1\n$100k+\nitems\nlog\nVALVE’S LISTING CAP\nna poziomie lub poniżej limitu notowań ustalonego przez „Valve”ponad limit — zgodnie z zasadami serwisu „Valve” umieszczanie takich ogłoszeń jest zabronionekategorie produktów w tej grupie\n\n„Zasięg” oznacza, że w momencie pobrania danych w tej kategorii istniało aktywne zapytanie typu „Steam”. Dolny wykres ma skalę logarytmiczną, ponieważ większość pozycji w katalogu jest niezwykle tania: odczyt w skali liniowej spowodowałby spłaszczenie wszystkich przedziałów cenowych powyżej300 do poziomu linii bazowej.\n\nCo wyklucza ten kształt\n\nGdyby drogie produkty były po prostu niepopularne, popyt na nie stopniowo by spadał wraz ze wzrostem ceny. Tak jednak nie jest. Utrzymuje się on na poziomie 76.8% w przedziale cenowym od $300–$1k, a następnie gwałtownie spada do 14.5% w przedziale bezpośrednio poniżej pułapu oraz do 2.9% w przedziale bezpośrednio powyżej niego. Efekt popytu nie uwzględnia tego, gdzie Valve ustalił swój pułap. Zasada natomiast tak.\n\nPrzedział cenowy\tKategorie produktów\tW ramach akcji „Steam” na żywo\tSteam zakres\tWykaz egzemplarzy zamieszczony na stronie Steam\n1¢–10¢\t4,632\t4,632\t100%\t8,223,227\n10¢–$1\t7,152\t6,931\t96.9%\t5,488,315\n$1–10\t8,568\t8,213\t95.9%\t3,939,538\n$10–100\t5,941\t5,780\t97.3%\t1,328,255\n$100–300\t2,329\t2,121\t91.1%\t364,466\n$300–1k\t1,292\t992\t76.8%\t187,504\n$1k–1.8k\t193\t28\t14.5%\t40,281\n$1.8k–3k\t70\t2\t2.9%\t9,592\n$3k–10k\t67\t1\t1.5%\t6,706\n$10k–30k\t18\t0\t0%\t1,366\n$30k–100k\t3\t0\t0%\t21\n$100k+\t1\t0\t0%\t2\n\nW niniejszej klasyfikacji pominięto warianty wzorów i faz: strona Steam nie wymienia poziomu „blue-gem” ani fazy „Ruby” jako odrębnych pozycji rynkowych, więc uwzględnienie ich spowodowałoby zaniżenie zasięgu serwisu Steam. Jeśli pominąć wymóg obecności na dwóch platformach handlowych, ta sama skala przedstawia się następująco: 79.1% poniżej progu i 6.5% powyżej niego w odniesieniu do 37,204 pozycji — jest to wyraźniejsza różnica oparta na słabszych dowodach, dlatego nie jest to podawana wartość.\n\n02 / ocena dowodowa\nCena wywoławcza to nie cena\n\nKażdy może wystawić model P2000 za okrągłe dziesięć milionów juanów. Zanim jakakolwiek kwota podana na tej stronie zostanie wykorzystana w jakikolwiek sposób, jest ona klasyfikowana na podstawie tego, ile platform handlowych niezależnie wycenia dany przedmiot powyżej ustalonego pułapu oraz jak ściśle skupiają się środkowe wartości tych wycen. Podawane są wyłącznie oceny A i B — zarówno tutaj, jak i w pozostałej części niniejszego dossier.\n\nA  Trzy lub więcej półek pasują do siebie\n\nTrzy lub więcej platform handlowych podaje cenę tego produktu powyżej limitu, a ich mediana mieści się w przedziale 25% od najniższej ceny. 197 kategorie, 18,218 egzemplarzy, $76,585,587.\n\nNieobecni w programie „Steam”: 100.0%.\n\nB  Dwie półki pasują do siebie\n\nDwie platformy handlowe uzgadniają cenę powyżej limitu, a trzy – na nieco niższym poziomie. 51 kategorie, 176 egzemplarze, $2,038,814.\n\nNieobecni w programie „Steam”: 100.0%.\n\nC  Jedna półka — nieużywana\n\nJedna platforma handlowa oferuje jedyną ofertę sprzedaży powyżej limitu. 171 kategorie, 247 egzemplarzy. Zostały one umieszczone w galerii dla kompletności i nie są uwzględniane w żadnej z sum podanych na tej stronie.\n\nSą to zapytania o cenę, a nie jej potwierdzenie.\n\nIle kosztowała ta korekta i co dzięki niej uzyskano\n\nUsunięcie oceny „C” powoduje wyeliminowanie z nagłówka kategorii „171” oraz „$3,825,125”. To, co pozostaje, jest krótsze i znacznie trudniejsze do podważenia: 248 kategorie, 18,394 wymienione egzemplarze, $78,624,401, oraz 100.0% z nich — każdy z osobna — nie występują na rynku serwisu Valve. Wiersze klasy C są przyczyną zmiany wartości na wykresie; są one widoczne, a nie ukryte.\n\nWpisy odłożone na bok jako artefakty\n\nKażda oferta, której cena przekracza trzykrotność najniższej ceny sprzedaży tego samego produktu, jest odrzucana. Po przeliczeniu według kursu wynikającego z samych danych większość z nich to okrągłe kwoty w CNY — co wskazuje raczej na symbol zastępczy lub górny limit platformy niż na rzeczywistą ofertę. Ponieważ każda suma na tej stronie opiera się na najtańszy Trzeba przyznać, że żadna z tych osób nie mogłaby nigdy zawyżyć danych; zostały one wykluczone, aby żadna z nich nie mogła również pojawić się w nagłówku.\n\nPozycja\tNajtańsza oferta na żywo\tOdłóż na bok\nSouvenir P2000 | Wicked Sick (Minimal Wear)\t$148,954\t$1,489,543\n★ Specialist Gloves | Crimson Kimono (Minimal Wear) | Phase 1\t$37,239\t$119,163\nSouvenir USP-S | Printstream (Factory New)\t$2,000\t$59,582\n★ Bowie Knife | Crimson Web (Factory New)\t$2,957\t$43,030\n★ Karambit | Marble Fade (Factory New) | 1st\t$11,916\t$38,874\nSticker | Ninjas in Pyjamas (Holo) | Katowice 2014\t$5,000\t$31,748\nSouvenir AWP | Dragon Lore (Battle-Scarred)\t$4,225\t$29,157\n★ Karambit | Doppler (Minimal Wear) | Ruby\t$7,122\t$27,273\nWszystkie kategorie serwisu „419” wraz z przedmiotem, do którego odnosi się każda cena\n\nŹródło: https://phishdestroy.io/steam_dossier/pl/skin_atlas#gallery\n\n04 / dokąd trafił zamiast tego\nPółki, na których znajdują się rzeczy, których nie ma na stronie Steam\n\nTe same pozycje, pogrupowane według platformy, na której się znajdują. Jest to zestawienie miejsc, w których znajdują się egzemplarze wymienione, co nie jest tożsame z miejscem, w którym się znajdują, i nie jest tutaj w ten sposób interpretowane.\n\nWartość minimalna ofert powyżej limitu, według platformy handlowej\nnajniższa cena sprzedaży x egzemplarzy znajdujących się na tej półce\nYouPin 898\n$22,720,252\nBUFF163\n$22,022,606\nC5Game\n$12,560,543\nCSFloat\n$10,871,845\nSkinport\n$1,385,060\n\nJurysdykcje, w podanej powyżej kolejności: YouPin 898 — Chiny · BUFF163 — Chiny · C5Game — Chiny · CSFloat — Stany Zjednoczone · Skinport — Niemcy / Malta. Ten sam produkt fizyczny może być wystawiony na więcej niż jednej z tych półek, dlatego danych tych nie wolno sumować z żadnymi innymi danymi dotyczącymi rynku.\n\nWartość minimalna według przedziału cenowego\nw jaki sposób środki są rozdzielane powyżej limitu\n$1.8k-3k\n$9,842,391\n$3k-10k\n$36,787,269\n$10k-50k\n$20,038,749\nover $50k\n$2,891,897\n05 / niedobór, który można policzyć\nJak niewielka jest w rzeczywistości podaż\n\nKażdy przedmiot w CS2 ma przypisaną wartość zużycia, a platformy handlowe podają, ile egzemplarzy znajduje się w każdym przedziale tej wartości. Dzięki temu „rzadki” przestaje być tylko przymiotnikiem, a staje się liczbą — i to właśnie ta liczba wyjaśnia, dlaczego jedno przejęte konto jest warte wysiłku związanego z przygotowaniem specjalnie dostosowanego zestawu do phishingu.\n\nAWP | Wiedza o smokach\n150 w ofercie · od11,350\n0.00–0.01\n29 · $14,730\n0.01–0.02\n54 · $11,618\n0.02–0.03\n26 · $11,350\n0.03–0.04\n25 · $11,618\n0.04–0.07\n16 · $11,585\n\nAWP | Dragon Lore (nowy, fabrycznie nowy)\n\nM4A4 | Howl\n105 w ofercie · od6,628\n0.00–0.01\n11 · $10,725\n0.01–0.02\n14 · $8,088\n0.02–0.03\n11 · $7,580\n0.03–0.04\n19 · $6,703\n0.04–0.07\n50 · $6,628\n\nM4A4 | Howl (nowy, prosto z fabryki)\n\nAK-47 | Wild Lotus\n113 w ofercie · od14,373\n0.00–0.01\n25 · $22,343\n0.01–0.02\n11 · $19,364\n0.02–0.03\n3 · $19,645\n0.03–0.04\n15 · $15,044\n0.04–0.07\n59 · $14,373\n\nAK-47 | Wild Lotus (nowy, fabrycznie nowy)\n\nAWP | Gungnir\n173 w ofercie · od11,618\n0.00–0.01\n28 · $17,875\n0.01–0.02\n21 · $13,600\n0.02–0.03\n32 · $12,065\n0.03–0.04\n29 · $11,735\n0.04–0.07\n63 · $11,618\n\nAWP | Gungnir (nowy, fabrycznie nowy)\n\nAK-47 | Ognisty Wąż\n278 w ofercie · od663\n0.15–0.18\n87 · $730\n0.18–0.21\n49 · $712\n0.21–0.24\n52 · $703\n0.24–0.27\n18 · $715\n0.27–0.38\n72 · $663\n\nAK-47 | Ognisty Wąż (sprawdzony w terenie)\n\nUtwardzane powierzchniowo (wszystkie poziomy / niebieski klejnot)\n76 w ofercie · od1,638\n0.07–0.08\n1 · $2,516\n0.08–0.09\n4 · $2,482\n0.09–0.10\n6 · $3,856\n0.10–0.11\n7 · $2,797\n0.11–0.15\n58 · $1,638\n\nAK-47 | Utwardzany powierzchniowo (minimalne zużycie) | Poziom1\n\nPrzedziały cenowe stanowią własne segmenty płynności platformy; losowane są wyłącznie te przedziały, w których znajduje się co najmniej jedna aktualna oferta. Cena podana obok każdego słupka odpowiada najniższej aktualnej cenie sprzedaży w danym przedziale, dzięki czemu premia związana z niską płynnością jest bezpośrednio widoczna, a nie tylko deklarowana.\n\n06 / ruch, pomiar przeprowadzony na stronie Steam\nJakie wyniki faktycznie osiągnęły półki z produktami innych marek\n\nValve nie publikuje żadnych przydatnych danych historycznych na tym poziomie, a niniejsze opracowanie również ich nie zawiera. Serwis Skinport publikuje natomiast informacje o własnych zrealizowanych transakcjach sprzedaży z ostatnich 24 godzin, 7, 30 oraz 90 dni, i to właśnie stanowi cały dostępny tutaj wymiar czasowy: medianę ceny zrealizowanej w danym oknie czasowym, zindeksowaną w taki sposób, że 90-dzienna mediana wynosi 100. W żadnym z wykresów nie wykorzystano danych z serwisu „Steam”.\n\nMediana ceny zrealizowanej, okno historyczne\nindeksowane względem mediany dziennej z serwisu 90-· 6,758 pozycje z 20+ sprzedaż\n85\n91\n97\n103\n100\n90d\n94\n30d\n90\n7d\n88\n24h\nLiczba zrealizowanych transakcji sprzedaży dziennie\nte same elementy, te same okna\n7,621\n9,653\n11,684\n13,716\n12,700\n90d\n11,894\n30d\n9,540\n7d\n8,637\n24h\n\nSą to dwa wykresy, a nie jeden z dwiema skalami pionowymi: indeks i dzienna liczba nie mają wspólnej jednostki miary, a narysowanie ich na wspólnej osi skłaniałoby do nieprawidłowego porównania. Okna są zagnieżdżone i typu „trailing” — wartość dzienna z 90-obejmuje wartość godzinową z 24-— więc nie jest to szereg dzienny i nie należy go tak interpretować. To, co wykresy te potwierdzają, jest wąskie i jasno sformułowane: w opublikowanych przez Skinport oknach śledzących mediana ceny zrealizowanej utrzymywała się poniżej własnej mediany 90-z danego dnia, a dzienna liczba transakcji spadała wraz z nią.\n\nSkinport zrealizowana sprzedaż. Okna są zagnieżdżone i przesuwne, więc każdy punkt odpowiada medianie ceny zrealizowanej w bieżącym oknie, zindeksowanej względem mediany z dnia 90-. Nie jest to szereg dzienny i nie wykorzystuje danych z Steam.\n\n07 / z czego jest zrobiony\nSzesnastoletnie naklejki i garść rękawiczek\n\nOferta powyżej limitu nie stanowi szerokiego przekroju rynku. Ogranicza się ona do kilku rzadkich egzemplarzy i kilku kolekcji, z których część nie jest już w ogóle dostępna — i właśnie dlatego podaż nie jest w stanie dostosować się do ceny.\n\nKategorie powyżej limitu, według rzadkości\nliczba kategorii produktów\nCovert\n321\nClassified\n39\nRestricted\n24\nContraband\n12\nMil-Spec Grade\n9\nConsumer Grade\n9\nIndustrial Grade\n5\nKategorie powyżej górnej granicy, według kolekcji\ndziesięć najlepszych kolekcji\nThe St. Marc Collection\n13\nThe Cobblestone Collection\n13\nThe Norse Collection\n12\nThe Arms Deal Collection\n9\nThe Canals Collection\n7\nThe Gods and Monsters Collection\n6\nThe Revolution Collection\n4\nThe 2021 Train Collection\n4\nThe Rising Sun Collection\n4\nThe Chop Shop Collection\n4\n\nWedług kategorii: skin 366, sticker 48, container 3, sticker_slab 2.\n\n08 / najwyższa kwota, jaką ktokolwiek faktycznie zapłacił\nWysokie ceny poparte transakcją, a nie notowaniem giełdowym\n\nKażda inna cena podana na tej stronie to zapytać — czego oczekuje sprzedawca. Są to sprzedaż: najwyższa zrealizowana transakcja Skinport odnotowana dla każdego produktu w ciągu ostatnich 90 dni. Jest to jedyna kwota w niniejszym zestawieniu, którą ktoś faktycznie zapłacił, a każdy wiersz zawiera link do platformy handlowej, dzięki czemu kwotę tę można zweryfikować bezpośrednio u źródła, a nie u nas.\n\n21,216pozycje, których sprzedaż została sfinalizowana w danym okresie\n106sprzedane po cenie równej lub wyższej od górnego limitu wyceny ustalonego przezValve\n$14,192najwyższa wartość pojedynczej zrealizowanej transakcji sprzedaży\n67/419kategorie powyżej limitu, w których odnotowano jakąkolwiek sprzedaż\nTrzydzieści najwyższych zrealizowanych transakcji sprzedaży w tym okresie\nPozycja\tNajwyższa sprzedaż\tMediana ceny sprzedaży\tSprzedaż\tNajniższa cena – zapytaj teraz\tSteam\tZobacz to\nAWP | Gungnir (Factory New)\t$14,192\t$11,343\t5\t$11,490\tabsent\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Factory New)\t$12,387\t$12,387\t1\t$13,836\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Factory New)\t$11,779\t$11,063\t16\t$10,941\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Minimal Wear)\t$11,693\t$11,693\t1\t$9,946\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Minimal Wear)\t$10,437\t$10,437\t1\t$9,610\tabsent\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Blue Laminate (Minimal Wear)\t$9,772\t$37\t76\t$30\t$40\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Minimal Wear)\t$9,463\t$9,463\t1\t$9,500\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Minimal Wear)\t$9,104\t$9,026\t6\t$8,524\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Hedge Maze (Minimal Wear)\t$8,139\t$8,139\t1\t$6,819\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Field-Tested)\t$7,617\t$7,390\t4\t$7,194\tabsent\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Field-Tested)\t$7,615\t$7,615\t1\t$7,100\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Field-Tested)\t$7,149\t$7,006\t2\t$7,165\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Field-Tested)\t$6,711\t$6,194\t15\t$5,988\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Factory New)\t$6,679\t$6,613\t3\t$6,628\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Superconductor (Factory New)\t$6,084\t$6,084\t1\t$7,969\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Battle-Scarred)\t$5,750\t$5,413\t3\t$5,899\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Pandora's Box (Minimal Wear)\t$5,520\t$5,508\t3\t$4,998\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Vice (Factory New)\t$5,385\t$5,158\t2\t$5,700\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Minimal Wear)\t$5,342\t$4,989\t19\t$4,997\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Hedge Maze (Field-Tested)\t$5,334\t$4,862\t5\t$3,724\tabsent\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Vulcan (Factory New)\t$5,275\t$1,418\t12\t$1,280\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Well-Worn)\t$4,978\t$4,978\t1\t$4,942\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Well-Worn)\t$4,931\t$4,931\t1\t$5,445\tabsent\tSkinport CSFloat Steam\nAK-47 | Hydroponic (Factory New)\t$4,802\t$4,351\t2\t$3,648\tabsent\tSkinport CSFloat Steam\n★ Talon Knife | Case Hardened (Minimal Wear)\t$4,588\t$466\t16\t$442\t$630\tSkinport CSFloat Steam\nAWP | Medusa (Factory New)\t$4,484\t$4,484\t1\t$4,171\tabsent\tSkinport CSFloat Steam\n★ Specialist Gloves | Pillow Punchers (Factory New)\t$4,359\t$4,359\t1\t$4,302\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Pandora's Box (Field-Tested)\t$4,359\t$3,666\t11\t$3,245\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Field-Tested)\t$4,289\t$4,225\t8\t$4,022\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Battle-Scarred)\t$4,124\t$4,124\t1\t$4,279\tabsent\tSkinport CSFloat Steam\nTen sam produkt, te same dni promocji „90”, a cena diametralnie różna\n\nOgraniczono do pozycji o medianie $100 i co najmniej pięciu zrealizowanych transakcjach sprzedaży, ponieważ w przypadku taniej skórki jedna nietypowa transakcja znacznie zniekształca ten wskaźnik. Pozostała część jest zdominowana przez Utwardzane powierzchniowo wykończenia, gdzie wzór decyduje o cenie, a platforma handlowa klasyfikuje każdy wzór pod jedną nazwą — ten sam mechanizm opisany za pomocą zmiennej typu float w sekcji 05.\n\nPozycja\tWartość najwyższa a mediana\tNajwyższa sprzedaż\tMediana ceny sprzedaży\tSprzedaż\tZobacz to\n★ Talon Knife | Case Hardened (Minimal Wear)\t+884%\t$4,588\t$466\t16\tSkinport CSFloat Steam\nDesert Eagle | Cobalt Disruption (Factory New)\t+859%\t$1,210\t$126\t115\tSkinport CSFloat Steam\nAWP | BOOM (Minimal Wear)\t+814%\t$1,232\t$135\t89\tSkinport CSFloat Steam\nAK-47 | Case Hardened (Well-Worn)\t+769%\t$1,720\t$198\t70\tSkinport CSFloat Steam\nAWP | Graphite (Factory New)\t+761%\t$1,469\t$171\t124\tSkinport CSFloat Steam\n★ Talon Knife | Case Hardened (Field-Tested)\t+509%\t$2,437\t$400\t48\tSkinport CSFloat Steam\n★ Kukri Knife | Case Hardened (Minimal Wear)\t+448%\t$723\t$132\t69\tSkinport CSFloat Steam\n★ Kukri Knife | Case Hardened (Field-Tested)\t+415%\t$549\t$106\t128\tSkinport CSFloat Steam\n★ Ursus Knife | Case Hardened (Minimal Wear)\t+371%\t$597\t$127\t12\tSkinport CSFloat Steam\nAK-47 | Case Hardened (Field-Tested)\t+369%\t$1,037\t$221\t125\tSkinport CSFloat Steam\nAK-47 | Red Laminate (Minimal Wear)\t+360%\t$552\t$120\t18\tSkinport CSFloat Steam\nAWP | Asiimov (Field-Tested)\t+351%\t$528\t$117\t439\tSkinport CSFloat Steam\nAK-47 | Vulcan (Field-Tested)\t+337%\t$865\t$198\t241\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Nightwish (Factory New)\t+322%\t$625\t$148\t31\tSkinport CSFloat Steam\nAWP | Lightning Strike (Factory New)\t+319%\t$2,065\t$493\t198\tSkinport CSFloat Steam\nStatTrak™ AWP | Redline (Minimal Wear)\t+312%\t$574\t$139\t24\tSkinport CSFloat Steam\nStatTrak™ AWP | Asiimov (Battle-Scarred)\t+287%\t$524\t$135\t37\tSkinport CSFloat Steam\nAK-47 | Redline (Minimal Wear)\t+277%\t$562\t$149\t112\tSkinport CSFloat Steam\nAWP | Crakow! (Factory New)\t+275%\t$379\t$101\t72\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Vulcan (Factory New)\t+272%\t$5,275\t$1,418\t12\tSkinport CSFloat Steam\n\nJest to najwyższy dzienny wynik serwisu 90-, a NIE rekord wszech czasów, i dotyczy on JEDNEGO serwisu aukcyjnego. W niniejszym zestawieniu nigdzie nie podano żadnej wartości rekordowej. Pozycja, która nie ma w oknie sprzedaży na Skinport, jest całkowicie pominięta w niniejszym zestawieniu, dlatego też zbiór ten jest mniejszy niż dane spisu.\n\nLinki weryfikacyjne są tworzone na podstawie identyfikatorów platformy pochodzących z samego katalogu. Prowadzą one do stron poszczególnych serwisów handlowych poświęconych danemu produktowi, dzięki czemu czytelnik może zweryfikować informacje bezpośrednio u źródła, a nie u nas. Linki wychodzące zawierają rel=\"nofollow\": są to jedynie odniesienia, a nie rekomendacje, a kilka z tych serwisów to platformy handlowe, które w niniejszym dochodzeniu zostały poddane krytycznej ocenie.\n\n09 / pochodzenie i ograniczenia\nSkąd to się wzięło i czego nie jest w stanie pokazać\n\nKażda liczba na tej stronie została ponownie obliczona na podstawie dwóch plików z migawkami, których skróty zostały opublikowane obok nich. Żadna z tych informacji nie została zaczerpnięta z artykułu zamieszczonego na innej stronie.\n\nŹródło i dostęp\n\ncs2.sh API, GET /v1/prices/latest oraz GET /v1/schema, pojedynczy zrzut ekranu, zrzut z dnia 2026-09-23T00:44:27.871388581Z, ceny podane w USD.\n\nDane uzyskano w ramach płatnej subskrypcji komercyjnej posiadanej przez osobę składającą wniosek z GDPR, co zostało udokumentowane w archiwum, zgodnie z warunkami dostawcy. Nie przeprowadzono zgrywania danych z żadnej platformy handlowej ani nie wykorzystano danych uwierzytelniających żadnej z nich. Klucz wnioskodawcy jest przechowywany poza tym repozytorium i nie pojawia się w żadnym pliku w tym repozytorium.\n\nJak produkt spełnia wymagania\n\nKażdy przedmiot podstawowy, który ma co najmniej jedną aktywną ofertę sprzedaży na platformach BUFF, CSFloat, Skinport, YouPin lub C5Game, jest przypisywany do przedziału cenowego na podstawie NAJTAŃSZEJ z takich ofert, więc przedział ten nigdy nie zależy od Steam. „Steam coverage” to odsetek przedmiotów w danym przedziale, które w momencie rejestracji mają jakąkolwiek aktywną ofertę sprzedaży na Steam. Warianty wzorów i faz są wykluczone z rankingu, ponieważ Steam nie wymienia ich oddzielnie; uwzględnienie ich spowodowałoby zaniżenie wartości Steam. Rendery to zdjęcia katalogowe tych samych produktów, przechowywane lokalnie.\n\nRendery i prawa do obrazów. Rendery produktów z katalogu to obrazy dostarczane przez dostawcę dla tej samej wartości „market_hash_name”, co wiersze cenowe; są one przechowywane lokalnie w celu wyświetlania w trybie offline oraz za pośrednictwem IPFS. Rendery nie są dziełem serwisu PhishDestroy: wszystkie zdjęcia produktów, logo i zrzuty ekranu pozostają własnością ich odpowiednich właścicieli (cs2.sh, CSFloat, Skinport, BUFF, YouPin, C5Game, Valve i inni). Są one reprodukowane wyłącznie w celu identyfikacji i publikacji w interesie publicznym; nie rości się sobie żadnych praw własności ani licencji.\n\nWhat this means — market_hash_name\n\nThe exact identifier Steam’s own API uses for an item — wear, finish and all. Third-party marketplaces list against the same string, which is what makes their catalogues directly comparable with Steam’s and ties every outside listing back to a record inside Valve’s database.\n\nCzego nie udało nam się zdobyć\n\nWybrany poziom subskrypcji obejmuje wyłącznie aktualne migawki. Punkty końcowe dotyczące danych historycznych i archiwalnych nie były dostępne, a na tej stronie nie podano nigdzie żadnych danych historycznych poza danymi o sprzedaży z okna historycznego – Skinport – publikuje się w sekcji 06.\n\nJedna migawka, a nie szereg czasowy. Brak oferty na stronie Steam w momencie zrzutu ekranu nie jest dowodem na to, że przedmiot nigdy się tam nie pojawi; jest to stan półki w danym momencie, a w przypadku cen powyżej limitu jest to również zgodne z opublikowaną zasadą serwisu Valve: rynek społecznościowy Valve wyraźnie ogranicza oferty do1,800 za sztukę (przy maksymalnym saldzie portfela Steam wynoszącym2,000; zobacz Steam Najczęściej zadawane pytania dotyczące targu lokalnego zarchiwizowano 2026-09-21 ↗ oraz Steam Umowa abonamentowa § 3.C zarchiwizowano 2026-09-24 ↗).\n\nOcenianie\n\nCena danego produktu to zawsze najniższa aktualna cena sprzedaży, więc wysoka wartość odstająca nigdy nie może zawyżyć sumy. Klasyfikacja określa, które wiersze mogą być uwzględnione w wycenie. Każda oferta przekraczająca trzykrotność najniższej ceny sprzedaży tego samego produktu jest odrzucana jako cena nieaktualna. Ocena A: co najmniej trzy platformy handlowe nadal podają ceny powyżej limitu, a ich mediana mieści się w przedziale 25 procent najniższej ceny. Ocena B: dwie platformy są zgodne, lub trzy są zgodne, ale w mniejszym stopniu. Ocena C: pojedyncza oferta – cena wywoławcza, a nie cena rynkowa. W niniejszym opracowaniu podawane są wyłącznie oceny A i B.\n\nZasada dotycząca wartości odstających: notowanie > 3.0pomnożone przez najniższą cenę sprzedaży tego samego instrumentu.\n\nDlaczego wartości sumaryczne stanowią wartość minimalną\n\nDla każdej platformy handlowej produkt najniższy Cena sprzedaży jest mnożona przez liczbę egzemplarzy wymienionych w wykazie. Co drugi egzemplarz ma cenę równą lub wyższą od tej najniższej ceny sprzedaży, więc rzeczywista podana wartość jest wyższa z samej natury rzeczy, a nie na podstawie szacunków. Nie jest to transakcja sprzedaży, nie jest to przepływ gotówki ani wycena gospodarki CS2.\n\nSprawdź sam\n\nZbiory danych, na podstawie których powstały wszystkie wykresy na tej stronie, zostały opublikowane w całości: zbiór danych Atlas, ekran klasyfikacji i artefaktów, spis ludności, na którym opiera się ta analiza oraz manifest zawierający skróty SHA-256ne każdej nieprzetworzonej migawki.\n\nKorekta odnotowana na otwarciu\n\nWcześniejsza wersja rejestru towarzyszącego zawierała na początku pozycję „Souvenir AK-47 | Point Disarray” z ceną wywoławczą $148,954 na jednej z chińskich platform handlowych, podczas gdy Steam wycenił ją na $119. Ta pozycja ma ocenę C: jedna półka, jeden egzemplarz i brak zgodności z ceną na innej platformie. Jest to cena wywoławcza, a nie cena rynkowa, i została obniżona zarówno tutaj, jak i na tej stronie. Potwierdzonym liderem jest naklejka | Titan (Holo) | Katowice 2014 w cenie $66,285, cytowane przez 4, platformy handlowe znajdujące się w odległości 5.2% od siebie — a całkowicie nieobecne na stronie Steam.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Atlas drabiny cenowej Skin — „Klif płynności”"
          },
          {
            "level": 2,
            "id": null,
            "text": "Klif opiera się na zasadzie, a nie na żądaniu"
          },
          {
            "level": 3,
            "id": null,
            "text": "Co wyklucza ten kształt"
          },
          {
            "level": 2,
            "id": null,
            "text": "Cena wywoławcza to nie cena"
          },
          {
            "level": 3,
            "id": null,
            "text": "A  Trzy lub więcej półek pasują do siebie"
          },
          {
            "level": 3,
            "id": null,
            "text": "B  Dwie półki pasują do siebie"
          },
          {
            "level": 3,
            "id": null,
            "text": "C  Jedna półka — nieużywana"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ile kosztowała ta korekta i co dzięki niej uzyskano"
          },
          {
            "level": 3,
            "id": null,
            "text": "Wpisy odłożone na bok jako artefakty"
          },
          {
            "level": 2,
            "id": null,
            "text": "Wszystkie kategorie serwisu „419” wraz z przedmiotem, do którego odnosi się każda cena"
          },
          {
            "level": 2,
            "id": null,
            "text": "Półki, na których znajdują się rzeczy, których nie ma na stronie Steam"
          },
          {
            "level": 2,
            "id": null,
            "text": "Jak niewielka jest w rzeczywistości podaż"
          },
          {
            "level": 2,
            "id": null,
            "text": "Jakie wyniki faktycznie osiągnęły półki z produktami innych marek"
          },
          {
            "level": 2,
            "id": null,
            "text": "Szesnastoletnie naklejki i garść rękawiczek"
          },
          {
            "level": 2,
            "id": null,
            "text": "Wysokie ceny poparte transakcją, a nie notowaniem giełdowym"
          },
          {
            "level": 3,
            "id": null,
            "text": "Trzydzieści najwyższych zrealizowanych transakcji sprzedaży w tym okresie"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ten sam produkt, te same dni promocji „90”, a cena diametralnie różna"
          },
          {
            "level": 2,
            "id": null,
            "text": "Skąd to się wzięło i czego nie jest w stanie pokazać"
          },
          {
            "level": 3,
            "id": null,
            "text": "Źródło i dostęp"
          },
          {
            "level": 3,
            "id": null,
            "text": "Jak produkt spełnia wymagania"
          },
          {
            "level": 3,
            "id": null,
            "text": "Czego nie udało nam się zdobyć"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ocenianie"
          },
          {
            "level": 3,
            "id": null,
            "text": "Dlaczego wartości sumaryczne stanowią wartość minimalną"
          },
          {
            "level": 3,
            "id": null,
            "text": "Sprawdź sam"
          },
          {
            "level": 3,
            "id": null,
            "text": "Korekta odnotowana na otwarciu"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/pl/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/pl/skin_atlas#gallery",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://skinport.com/market?search=AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260924114457/https://store.steampowered.com/subscriber_agreement/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-atlas.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-artefact-screen.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-above-the-ceiling.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/pl/skin_atlas.content.json",
      "export_json_sha256": "16f96b591a95b1f05bd7f5c4d2e43f16c2b21d65d8ff0378bf0d1b2cc2dc0b7a"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "pl/social_graph.html",
      "language": "pl",
      "title": "Śledź udokumentowane powiązania — Dossier „Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/pl/social_graph",
      "source_html_sha256": "2ff6609b60361a1bc56d80f84421e09ecaa4048aa95ae56eae3f6f07ae139ed1",
      "exported_at": "2026-09-29T00:19:07.231Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "social_graph.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/pl/social_graph.pdf?v=print-20260929-v5",
        "sha256": "b5bf07c536546b57a6f9f7bdd4d1b7c770b5608f60df4d3c3f3754a7b8c2e69f",
        "bytes": 121393,
        "pages": 6
      },
      "integrity": {
        "signed_object": "social_graph.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "social_graph.content.json.asc",
        "digest_file": "social_graph.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify social_graph.content.json.asc social_graph.content.json",
          "sha256sum -c social_graph.content.json.sha256"
        ]
      },
      "content": {
        "text": "Podążaj za powiązaniami.Sprawdź każdą relację.\n\nWyszukaj profil. Wybierz rodzaj relacji. Przejrzyj bezpośrednich sąsiadów w pobranych rekordach. Narzędzie badawcze: Krawędzie symbolizują relacje publiczne, a nie dowód bezpośredniego kontaktu, prywatnej koordynacji czy niewłaściwego postępowania między dowolnymi dwoma węzłami. Układ węzłów w sieci typu „3,435-” najlepiej interpretować przy użyciu filtrów.\n\nPoznawaj po jednym związku na raz\n\n💡 Kliknij i przeciągnij węzły, aby zmienić układ wykresu. Najedź kursorem, aby wyświetlić szczegółowe profile. Turkusowe linie ciągłe = przyjaźnie, bursztynowe linie przerywane = wspólne komentarze.\n\nRodzaj związkuProfil i bezpośredni sąsiedzi\n\n3,435 profile · 4,551 zapisane linki\n\nWyszukaj i wybierz profil lub kliknij węzeł. Pozostaną tylko jego bezpośredni, zarejestrowani sąsiedzi. Krawędź odzwierciedla relację; nie powoduje ona nawiązania prywatnej współpracy.\n\nProfile w zebranym zbiorze danych\n\nPełna tabela źródłowa: pobierz wszystkie wiersze z pliku „3,435” (CSV). Poniższa tabela zawiera początkowo pierwsze 25 wierszy; funkcja wyszukiwania i paginacji pozwala przeglądać cały zbiór danych.\n\n1–25 / 3,435 wierszy\nImię postaci\tSteamID64\tPolityka prywatności\tStatus\tCzłonkostwo w grupach\tZapas w stanie zamrożonym (USD)\tLokalizacja\nMahatma Gandhi\t76561198333721623\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tPH\nGalley//갤리🌠🌙\t76561198043416832\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tKP\n$Schlächter\t76561198860277343\tPUBLIC\tClean\tsteambans\t$0.00\tUnknown\n❄r3dsn0w000™❄ [Cristi]🎮\t76561197986767957\tPUBLIC\tClean\tCommunityLegends\t$0.00\tRO\n(2a03) Wolfy\t76561197991671851\tPUBLIC\tCommunity\tsr_public\t$0.00\tUS\nZloy2288\t76561198038578334\tPUBLIC\tClean\tsteambans\t$0.00\tBY\njessy\t76561198039125237\tPUBLIC\tCommunity, VAC (1x)\tCommunityLegends\t$0.00\tJP\nJithraRufure\t76561198071896910\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\n| Níllerdínho |\t76561198003487438\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tDK\nJones is back\t76561198023013026\tPRIVATE\tVAC (1x)\tsteambans\t$0.00\tUnknown\nUNEX | ★✠☠ MoH3st ☠✠\t76561198050763123\tPUBLIC\tClean\tsteambans\t$0.00\tDE\nTrojan\t76561198048457084\tPUBLIC\tClean\tCommunityLegends\t$0.00\tDE\n𝗠𝗮𝘆𝘂 ❤\t76561199377967696\tPUBLIC\tClean\tsr_public\t$0.00\tIS\nbig fucking idiot\t76561198871206397\tPUBLIC\tVAC (1x)\tsteambans\t$0.00\tUnknown\nSOFF Games\t76561198227129276\tPUBLIC\tClean\tcommunitymoderators\t$0.00\tRU\nThijminecraft02\t76561198253895669\tPUBLIC\tClean\tSteamIDcouk SArchive\t$0.00\tNL\nStatic-sama\t76561198289329793\tPUBLIC\tClean\tsteambans\t$0.00\tJP\n𝙸mmortal 𝚂targazer\t76561198142116760\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\nCommander Keen\t76561197987773287\tPUBLIC\tClean\tsteambans\t$0.00\tBE\nS1mX\t76561199648509165\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\nmixwell\t76561199276547472\tPUBLIC\tClean\tsr_public\t$0.00\tJP\nP90_GOD_YyEs™\t76561198285821942\tPUBLIC\tClean\tsteambans\t$0.00\tHK\nhewwo?\t76561199133807546\tPUBLIC\tVAC (1x)\tsteambans\t$0.00\tCH\n♕Kamikaze Atze♕\t76561198002700103\tPUBLIC\tClean\tsteambans\t$0.00\tDE\nPastica\t76561198154655970\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tDZ\nZarejestrowane powiązania przyjacielskie\n\nPełna tabela źródłowa: pobierz wszystkie wiersze z pliku „4,299” (CSV). Poniższa tabela zawiera początkowo pierwsze 25 wierszy; funkcja wyszukiwania i paginacji pozwala przeglądać cały zbiór danych.\n\n1–25 / 4,299 wierszy\nUżytkownik A\tKierunek\tUżytkownik B\tTyp relacji\nMahatma Gandhi\n76561198333721623\t↔\tDeskjet\n76561198272738437\tMutual Friends\nGalley//갤리🌠🌙\n76561198043416832\t↔\tomega\n76561197960274529\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tFisty\n76561198057301486\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tFaalagorn\n76561198001116101\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tMURK\n76561198036995672\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tÅρøᴛʜℯᴛȋᴄÅʟȋℯη ♛👽♛\n76561197984615267\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tsilatrak\n76561197999629462\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tBlack Blade\n76561198083368493\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tAvenger\n76561197978249317\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tRemtar\n76561198124322650\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tCato\n76561197961345984\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t✪ G λ M Ξ ®\n76561197994308495\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tclees42\n76561198030936806\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t𝓜ε𝔰𝔥 | AusLevels\n76561198108828539\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tSgtFopper™\n76561198002555892\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t❥Miss Bee\n76561198046958996\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tTesTy\n76561198032370068\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tskl_andrey\n76561198136881436\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t\"Exekutor\"\n76561198009583947\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tAraripe\n76561198103754372\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tsteve6678\n76561198053200093\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\ttrinner\n76561197970359081\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tSteph S.\n76561198025653291\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tKirito\n76561198154545657\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tDoc. todt\n76561197984492467\tMutual Friends\nLinki do zarejestrowanych komentarzy\n\nPełna tabela źródłowa: pobierz wszystkie wiersze z pliku „252” (CSV). Poniższa tabela zawiera początkowo pierwsze 25 wierszy; funkcja wyszukiwania i paginacji pozwala przeglądać cały zbiór danych.\n\n1–25 / 252 wierszy\nAutor\tKierunek\tProfil docelowy\tData\tTekst komentarza\nDeskjet\n76561198272738437\t→\tMahatma Gandhi\n76561198333721623\t16 September, 2021 @ 11:02:05 pm PDT\t\"𝑵𝒐𝒘 𝒊𝒇 𝑰 𝒇𝒖𝒄𝒌 𝒕𝒉𝒊𝒔 𝒎𝒐𝒅𝒆𝒍𝑨𝒏𝒅 𝒔𝒉𝒆 𝒋𝒖𝒔𝒕 𝒃𝒍𝒆𝒂𝒄𝒉𝒆𝒅 𝒉𝒆𝒓 𝒂𝒔𝒔𝒉𝒐𝒍𝒆𝑨𝒏𝒅 𝑰 𝒈𝒆𝒕 𝒃𝒍𝒆𝒂𝒄𝒉 𝒐𝒏 𝒎𝒚 𝑻-𝒔𝒉𝒊𝒓𝒕𝑰'𝒎𝒎𝒂 𝒇𝒆𝒆𝒍 𝒍𝒊𝒌𝒆 𝒂𝒏 𝒂𝒔𝒔𝒉𝒐𝒍𝒆\" - Nelson Mandela\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t22 November, 2021 @ 4:10:28 pm PDT\thttps://anige.horigiri.net/?cat=22\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t18 November, 2021 @ 12:45:26 am PDT\thttps://gamerch.com/umamusume/entry/250411\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t8 August, 2021 @ 4:13:25 am PDT\thttps://modoocode.com/304\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t6 February, 2021 @ 3:35:05 pm PDT\t▤ ∫︹- -ω⁾ ⁽︹▓▓︺\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t11 December, 2019 @ 1:50:53 am PDT\thttps://blog.naver.com/aksenwlddj12/221369410039\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t2 October, 2019 @ 7:11:59 am PDT\tǤαllєу║︎갤리..۩\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t9 April, 2019 @ 12:51:28 pm PDT\tExplosiveDamage(owner, from, maxrange, minrange, distmultiplier, dmgmultiplier, mindamage, typ, damagetype, ignore)\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 12:22:47 pm PDT\tinfo - sh_titles.lua\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 12:21:46 pm PDT\tlocal nibbas = 1344 init.lua\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 11:31:58 am PDT\thttp://foreign.aladin.co.kr/shop/wproduct.aspx?ItemId=123955531&start=slayer\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t3 April, 2019 @ 1:26:41 am PDT\tǤαllєу\nLei\n76561198982197954\t→\tJithraRufure\n76561198071896910\t29 December, 2024 @ 12:58:08 pm PDT\t+rep he knows how 2 rush B ￣ヘ￣\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t2 September, 2026 @ 5:16:55 am PDT\tlol\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t20 August, 2026 @ 6:11:03 am PDT\t?\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t25 July, 2026 @ 7:20:05 am PDT\thahahahaha\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t30 June, 2026 @ 12:52:42 pm PDT\twow\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t30 June, 2026 @ 12:41:32 pm PDT\txD\nvalorant enjoyer\n76561199112142402\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:26:30 pm PDT\toh no!!\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:26:11 pm PDT\toh no!!\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:22:22 pm PDT\tomg !!! they know my secret, omg!!!\nvalorant enjoyer\n76561199112142402\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:21:39 pm PDT\t+rep good ♥♥♥♥♥ player\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:20:50 pm PDT\tomg! u cant cheat on secure gaben servers, omg dont report me, they ban me for boosted omg\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 8:37:11 pm PDT\txD\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t28 June, 2026 @ 1:58:14 pm PDT\twow",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Podążaj za powiązaniami.Sprawdź każdą relację."
          },
          {
            "level": 2,
            "id": null,
            "text": "Poznawaj po jednym związku na raz"
          },
          {
            "level": 2,
            "id": null,
            "text": "Profile w zebranym zbiorze danych"
          },
          {
            "level": 2,
            "id": null,
            "text": "Zarejestrowane powiązania przyjacielskie"
          },
          {
            "level": 2,
            "id": null,
            "text": "Linki do zarejestrowanych komentarzy"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-profiles.csv",
          "https://steamcommunity.com/profiles/76561198333721623",
          "https://steamcommunity.com/profiles/76561198043416832",
          "https://steamcommunity.com/profiles/76561198860277343",
          "https://steamcommunity.com/profiles/76561197986767957",
          "https://steamcommunity.com/profiles/76561197991671851",
          "https://steamcommunity.com/profiles/76561198038578334",
          "https://steamcommunity.com/profiles/76561198039125237",
          "https://steamcommunity.com/profiles/76561198071896910",
          "https://steamcommunity.com/profiles/76561198003487438",
          "https://steamcommunity.com/profiles/76561198023013026",
          "https://steamcommunity.com/profiles/76561198050763123",
          "https://steamcommunity.com/profiles/76561198048457084",
          "https://steamcommunity.com/profiles/76561199377967696",
          "https://steamcommunity.com/profiles/76561198871206397",
          "https://steamcommunity.com/profiles/76561198227129276",
          "https://steamcommunity.com/profiles/76561198253895669",
          "https://steamcommunity.com/profiles/76561198289329793",
          "https://steamcommunity.com/profiles/76561198142116760",
          "https://steamcommunity.com/profiles/76561197987773287",
          "https://steamcommunity.com/profiles/76561199648509165",
          "https://steamcommunity.com/profiles/76561199276547472",
          "https://steamcommunity.com/profiles/76561198285821942",
          "https://steamcommunity.com/profiles/76561199133807546",
          "https://steamcommunity.com/profiles/76561198002700103",
          "https://steamcommunity.com/profiles/76561198154655970",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-connections.csv",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-comments.csv"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/pl/social_graph.content.json",
      "export_json_sha256": "02de222d6def671f23234580efe88cd3eaaab80ed7400a5788619c6596c74c40"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "pl/steam_enforcement_evidence.html",
      "language": "pl",
      "title": "Zasady a reakcje — Dossier „Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/pl/steam_enforcement_evidence",
      "source_html_sha256": "5799401f6f08937b758571cba00064085d0679e0418b800912fa4dd7a777ef74",
      "exported_at": "2026-09-29T00:19:08.806Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "steam_enforcement_evidence.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/pl/steam_enforcement_evidence.pdf?v=print-20260929-v5",
        "sha256": "dac6892b6dd5a1c7c9afbb9a6f44cdcb77006a00f9ab0163c9c8ce450cde0121",
        "bytes": 380186,
        "pages": 36
      },
      "integrity": {
        "signed_object": "steam_enforcement_evidence.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "steam_enforcement_evidence.content.json.asc",
        "digest_file": "steam_enforcement_evidence.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify steam_enforcement_evidence.content.json.asc steam_enforcement_evidence.content.json",
          "sha256sum -c steam_enforcement_evidence.content.json.sha256"
        ]
      },
      "content": {
        "text": "Uzupełnienie dowodów / zapisy powiązane ze źródłami\nSteam Dowody dotyczące egzekwowania przepisów — dokumentacja pomocnicza i sieć deweloperów\n\nZasada. Odpowiedź.\n\nCO WYKAZUJE TA CZĘŚĆ\n\nW niniejszym zestawieniu dowodów porównano oficjalną umowę abonamentową serwisu „Valve” z datowanymi protokołami działań egzekucyjnych, rozstrzygnięciami sporów dotyczących pomocy technicznej oraz danymi z sieci deweloperów w repozytoriach 252 i profilach 3,320. Wykazano w nim, że zwykli posiadacze kont są narażeni na niepodważalne działania egzekucyjne i zamknięcia kont przez dział pomocy technicznej w następstwie przejęcia kontroli nad sesjami, podczas gdy operacje komercyjne z wykorzystaniem botów o dużej skali działają nieprzerwanie, korzystając z publicznej infrastruktury.\n\n← Powrót do podsumowania dla kadry kierowniczej\n\nZapoznaj się z pisemnym zastrzeżeniem. Otwórz zarejestrowaną odpowiedź. Porównaj treść źródła z tym, na co nie udzielono odpowiedzi.\n\nPomoc i odwołania ↓Infrastruktura publiczna ↓\n252rekordy repozytorium\n3,320profile publiczne\n4,214odrębne pary profili i repozytoriów\n98,902pary profili ze wspólnymi repozytoriami\n01 / Wsparcie, sankcje i odbudowa\nZapoznaj się ze skargą.Proszę dołączyć plik źródłowy.\nGaleria odmów udzielenia wsparcia (wystawy 981) ↗Pobierz wybrane rekordy ↓\nHFB / SPRAWA OUTSOURCINGUPowszechnie uznany kompromis.\nDoniesienia o zwolnieniach.\n\nZapoznaj się z zamieszczoną odpowiedzią działu pomocy technicznej oraz źródłem informacji dotyczącej pracowników podwykonawcy.\n\nOtwórz sprawę i jej źródła →\n\nPoniżej: pięć zachowanych publiczne posty na Reddicie z udostępnionego zbioru danych dotyczących pomocy technicznej. Każdy wpis dokumentuje zgłoszoną interakcję z systemem pomocy technicznej serwisu Valve — wraz z oryginalnym linkiem źródłowym, pozycją zrzutu ekranu i pełną treścią. Są to relacje ofiar. Uwierzytelnione logi pomocy technicznej, które mogłyby je potwierdzić lub zaprzeczyć, znajdują się w posiadaniu serwisu Valve i nie zostały ujawnione.\n\n01\nBan & review2024-12-09\nPermanent sanction & closed appeals\n\nThe author reports a permanent account ban, repeated ticket closures and a planned GDPR access request.\n\nREDDIT / PUBLIC TESTIMONYr/ohnePixelCapture record 294\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 303 words\nPermanently banned Steam account without a clear explanation, need help!\n\nsteam_support_tickets_MEGA.json / record 294\n\nHey everyone,\n\nI’m in a really frustrating situation, and I’m hoping someone here can help me or offer advice. My Steam account was just permanently banned for allegedly violating the Steam Subscriber Agreement, and I have no idea why.\n\n# What Steam Support told me:\n\nThe support message said my account was banned due to:\n\n* Suspicious activities related to transferring or attempting to sell/trade the account.\n* Community reports and other unspecified factors.\n\nThey added that the ban is permanent and that they can't help me further. They also warned that future support requests regarding this ban might be ignored. 😞\n\n# Why I’m contesting this ban:\n\n* I have never sold, traded, or transferred my account. I’ve been the legitimate owner since the beginning.\n* On the day the ban occurred, I did nothing noteworthy that could have triggered such a sanction.\n* I received no prior warning, which feels incredibly unfair.\n\n# What I’ve tried so far:\n\n* Contacting Steam Support: I explained my situation and asked for more details, but they’re sticking to their decision and closing my tickets.\n* I’m preparing a request based on my Right of Access (GDPR) to get all the data related to my account.\n\n# Questions for the community:\n\n1. Has anyone successfully had a permanent ban lifted on Steam?\n2. Are there steps I can take to prove I’m the legitimate owner of the account?\n3. Any advice on how to word my request to convince support to reconsider my case?\n4. Would it be helpful to contact the CNIL (I’m based in France) to force Steam to provide more information?\n\nI’m really desperate at the thought of losing all my games, purchases, and years of playtime. Thanks in advance for any help and advice you can give!\n\nhttps://preview.redd.it/jk9qv0gmhv5e1.png?width=1289&amp;format=png&amp;auto=webp&amp;s=b3a333ebb08ea133e2c8747ba126f5a68283d9f7\n\nhttps://preview.redd.it/4sopt0gmhv5e1.png?width=1022&amp;format=png&amp;auto=webp&amp;s=56195d5336118faf9413f1514ead7e8d24c788c3\n\nhttps://preview.redd.it/eqrxw0gmhv5e1.png?width=996&amp;format=png&amp;auto=webp&amp;s=ff3539d28ab754e513ad471822c5de652920101d\n\nhttps://preview.redd.it/728xz0gmhv5e1.png?width=1034&amp;format=png&amp;auto=webp&amp;s=bc5335673509929669af785aa244bf8d2dc58da8\n\n02\nSupport access2025-05-09\nAccount recovery & a reported $10,000 loss\n\nThe author alleges that support reset credentials and removed account protection following another person’s recovery ticket.\n\nREDDIT / PUBLIC TESTIMONYr/legaladviceCapture record 110\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 193 words\nGot $10k stollen from steam inventory due to steam' support fault.\n\nsteam_support_tickets_MEGA.json / record 110\n\nLocation: Quebec, Canada.\n\nLast year, someone hacked my Steam account and stole items worth about $10,000 USD. I only noticed this last week. When I talked to Steam Support, they admitted that someone submitted a ticket to make changes on the account and Steam Support reset my password and turned off all my account security.\n\nI asked Steam Support about getting my items back, but they said there was nothing they could do. They told me I should follow their security recommendations.\n\nThe problem is, I did everything they \"suggested\" to protect an account:\n\n* I had two-factor authentication.\n* My phone number was connected to my account.\n* I used Steam Guard.\n* I printed recovery codes and kept them in a safe.\n\nEven though I did all these things, Steam Support still gave someone else access to my account. The stolen items had been in my account since around 2016-2017. Also, I had not logged in for a few years, so I didn’t accidentally give my information to a fake website.\n\nIs there anything I can do, or do I just have to accept losing $10,000 USD?\n\nThanks for your help.\n03\nRestoration2022-07-07\nA reported $500+ loss & template replies\n\nThe author describes an account compromise, disputed transactions and a support response that allegedly did not address the submitted evidence.\n\nREDDIT / PUBLIC TESTIMONYr/DotA2Capture record 45\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 410 words\nFunds stolen through steam market. Disappointed with Steam response.(or lackthereof)\n\nsteam_support_tickets_MEGA.json / record 45\n\nOn 6th July 2022, 44 unauthorized transactions were made on the steam market using my steam wallet funds totalling roughly $500+ USD to buy worthless 1 cent Dota 2 items. This happened during the wee hours in the morning and i contacted them first thing when i woke up. \n\nI have 2FA enabled all the time, and always thought this would not happen to me as I do not go on betting sites/click sketchy links. My account password + emails were not changed, nor did they take my inventory, just that my funds were used illicitly. Also when I went to disable other APIs, it says there are no other APIs to disable. Shows that it wasn't through me clicking sketchy links and leaving my account details there. Would have lost the whole account if i did so.\n\nWhat baffles me is how did they bypass my 2FA to login my account? Why doesn't steam market purchases go through 2FA as well? First time in 9 years that this happened to me. My acc was logged in 'BY' 'Vitebsk' during the illicit purchases but I'm based in Asia I gathered all the screenshots and provided in the ticket to steam support. \n\nAll i got was the standard copy paste template reply by Steam Support. Lost $500+ and was not even worthy of having a proper person to look into this. I dont think they even read or take a look at the screenshots cause if they did, they would have come to the realization that what happened was clearly fraud, and with a few clicks, reverse the unauthorized transactions, refund my wallet and ban the hijacker. \n\nOver the years, i've spent quite a fair bit on steam but really, this is the kind of recourse we get when our account is compromised? They just don’t care, sigh. I only expect the bare minimum from Steam and looks like even that is quite far-fetched.\n\nSS: https://imgur.com/a/67frcls \n\nHijacker: https://steamcommunity.com/profiles/76561199141246495\n\nSteam Response: https://imgur.com/a/V6v4maM\n\nI could think of a few ways on how to Improve:\n\n1) Add 2FA to market transactions. (even if its bulk posting or selling of items, just 1 2FA notif is required)\n\n2) Enable accounts to be region locked. (if you are migrating, then have to go through steam support etc)\n\n3) Additional Lock on Steam Wallet. (Another password perhaps?)\n\nEDIT: 2nd ticket in and I have still yet to receive a non robotic copy paste template response from Steam.\n04\nRestoration2021-11-29\nSteam Guard & an item-restoration refusal\n\nA preserved post includes the author’s account of item theft and a support response declining restoration.\n\nREDDIT / PUBLIC TESTIMONYr/DotA2Capture record 58\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 563 words\nMany people are losing item via clicking links where steam guard is enabled and steam support doesn't not restore items.\n\nsteam_support_tickets_MEGA.json / record 58\n\nAccounts are getting compromised and might be their pc as well where Steam market is targeted hence the malicious links . I am assuming these hackers are getting encouraged where steam support is not doing nothing and they are getting away with hacking items.  \nLiterally the guy who is supporting the game which he doesn't get any in game advantage just  cosmetics in game only for the sole purpose of supporting the game so that the game will prosper and become beautiful way  to enjoy weekend. But right now players are getting hacked left right and center and steam support  is copy pasting message where in short they are blaming the guy who clicked link. 1st this is happening because they are not targeting players but they are targeting market since they are selling those stuff for real cash via party website. Steam is a huge company and can eradicate the problem or at least can remove links temporarily  in chat since hackers are targeting .They made us install steam guard by saying we wont help if there is no steam guard now steam guard is not enough to save our inventory now they changed their policy  that they should not click any suspicious links. How would we know if the link is suspicious ? After clicking and getting our inventory stolen right !   \n\"we'd have to duplicate an item to restore it. Duplication lowers the value of all items by reducing their scarcity and inflating the economy, which affects everyone involved in trading and the Market. To maintain the value of everyone’s inventory, we do not restore items. For more information, please see the Steam Item Restoration Policy.\"  \nThey care for millions of people IN STEAM MARKET where as few  are losing items which is going to affect market where the rightful owner bought the items and hacker is going to sell the item via 3rd party website and enjoy ! HOW IRONIC !!  \nThis is the message from support where my frnd got his items stolen via clicking on link  \n   \nHi there,  \n\nThank you for the information and screenshots provided.  \n\nIt appears that the account was compromised, please take the following steps to secure your account and computer:  \n\nScan your computer for viruses, key loggers, spyware, and other malicious code using antivirus software with updated virus definitions.  \nChange the password for the email address that is associated with your Steam account.  \nRegularly reset your Steam account password.  \n\nPlease see our Security Recommendations article.  \n\nIn addition, I’m sorry to hear that your items were removed without your permission. Unfortunately, Steam Support does not restore scammed, lost, or stolen items for any reason.  \n\nSince Steam Support does not remove items from accounts, we'd have to duplicate an item to restore it. Duplication lowers the value of all items by reducing their scarcity and inflating the economy, which affects everyone involved in trading and the Market. To maintain the value of everyone’s inventory, we do not restore items. For more information, please see the Steam Item Restoration Policy.  \n\nTo make sure that a scammer is reported, please report them through the Steam Community. Reporting a scammer through the Steam Community is the best way to prevent them from committing future scams.  \n\nTo learn how to avoid scams or hijackings, please see our Trade Scam article.  \n\nIf you still need assistance, please let us know.\n05\nEnforcement2025-05-11\nSelective enforcement & an unexplained ban\n\nA community member describes a disputed ban and contrasts it with the visibility of commercial gambling promotion.\n\nREDDIT / PUBLIC TESTIMONYr/SteamUncensoredCapture record 107\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 1,208 words\n🚨 Steam Bans Without Reason and Ignores Its Community — What’s Going On?\n\nsteam_support_tickets_MEGA.json / record 107\n\nHey r/Steam,\n\nI’m writing this to share my thoughts and concerns about my friend [moneylead](https://steamcommunity.com/id/moneylead/) and Steam’s policies in general. I spoke with him yesterday about his situation, though I didn’t discuss writing this post with him—I asked last night, but he hasn’t responded yet. I want to highlight that this issue is broader than just his case, and while Steam might make changes in the future (though that’s unlikely), I feel the community needs to understand how far Steam has strayed from its original values. I’m not trying to put moneylead in a tough spot with this thread—all the info I’m sharing is public, nothing secretive. I hope he won’t be upset with me, but the community needs this case to see the bigger picture and how Steam feels completely unaccountable.\n\n**Why Does Steam Ignore Its Community?**  \nWhy does a platform like **Roblox** provide a detailed log of ban reasons, while Steam, which claims to be \"community-driven,\" ignores its community, bans whoever they want, for whatever they want, with no transparency? I looked into Roblox as a popular game—not a direct competitor to Steam—to see how their bans look, and you can check it out yourself: [Roblox Ban Reasons](https://www.google.com/search?q=Roblox+ban). Their bans are clear, detailed, and actually explain what you did wrong. I think most decent gaming communities operate like this—not with support agents named Olga, hired through outsourcing, who only know how to send canned auto-replies. Take cases like St4ck—or my friend **moneylead**. All these unbans, like **St4ck’s** or **Alexanddd’s**, happened behind closed doors with zero comments from Steam. Of course, it’s convenient for Steam to handle everything in secret, so no one knows or sees what’s going on—but this violates Steam’s own community rules and principles.\n\n**Who Is moneylead?**  \nI’ve known [moneylead ](https://steamcommunity.com/id/moneylead/)since around 2021. We played Dota 2 a couple of times, and then I just stayed on his friends list. He’s always been a legit player, bringing revenue to Steam through purchases. He never sold his skins, whether in **Dota or CS2—he wasn’t a trader**. All he did was:\n\n* Buy games and skins.\n* Collect badges to level up his profile.\n\nAccording to [SteamSets](https://steamsets.com/account/76561199080934614), he’s given out 324,000 Steam Points—I think he awarded profile rewards to all his friends in the list (though I’m not 100% sure). I do know he ran contests and gave gifts to friends, always supporting the community.\n\n**Steam’s Unfair Treatment**  \nI’ve seen Steam remove his showcases, avatar, description, and even his country multiple times—just because he’s from **Ukraine**. He has a ton of haters leaving toxic comments on his wall, and Steam seems to favor **Russian** users. Every time he tried to appeal the removal of his showcases or profile description—which didn’t break any rules, just had his Instagram link, and his avatar is the same as it is now—Steam moderators didn’t care. **They don’t care about top players who bring them massive revenue, nor about regular users.**\n\n>*Here’s the worst part: moneylead works in cybersecurity, specifically fighting account theft and phishing. He’s neutralized over 5,000 threats targeting Steam alone. And yet, Steam bans him for \"account hijacking\"?*\n\nIf you roughly calculate moneylead’s contribution to Steam and the community—his profile, level, badges (not skins, you can’t sell those)—is this normal, Steam? Banning people, closing tickets, and ignoring users with a spotless reputation who aren’t involved in any commercial activity, just bringing you profit without taking anything in return?\n\n**Steam’s Double Standards**  \nI’m honestly shocked:\n\n* YouTubers who promote casinos and skin gambling? Steam’s fine with that.\n* A cybersecurity expert who fights scams, doesn’t promote casinos, and openly talks about it on his profile? **Banned with no explanation, ignored, and denied an unban.**\n\nI wonder if Steam deliberately bans a high-level account once a year just because of their impunity—maybe for hype or something. Otherwise, this is just madness. It’s scary to think how many regular players have lost their accounts and skins—not because of scammers, but because of Steam’s desire to ignore, send auto-replies, and do whatever they want.\n\n**How Many Others Are Affected?**  \nHow many others are out there—maybe not as well-known—who just have a few games or skins, get banned for nothing, and receive zero explanation or response? **Is this even legal?** Every other platform provides a detailed log with specific violations, but Steam slaps on the same vague label and sends templated responses.\n\n* How safe is it to buy skins on Steam?\n* What’s the chance Steam will just ban your account for no reason, with no explanation?\n\n**A Message to Valve**  \nI wish moneylead the best in resolving this, but Valve, it’d be great if you remembered what \"community\" means and started following the law. Because right now, it looks like your 30% commission, impunity, and sense of being above the law in the U.S. have given you the idea that you can do whatever you want.\n\nI’m sure there are many others like moneylead and St4ck—people who aren’t public or don’t have the resources to fight back. Let’s unite these cases. **If you’re a U.S. resident who’s been banned by Steam without reason and wants to challenge it, please reach out to me.** I’m finishing my **Juris Doctor (J.D.) program at SMU Dedman School of Law** in Dallas, Texas, and I’m participating in a legal clinical practice under Rule 13 of the Texas Supreme Court.\n\nWhat Steam is doing is absolutely disgusting and illegal, and **I’d be happy to help any gamer (legitimate, with no real violations) who has games or skins with value. This will be beneficial for my practice, and it’s time to put Steam in its place and show them they can’t just dictate their own rules with arbitration**. Let’s take it all the way—not for punishment, but for the sake of the community. Maybe if Steam loses a case, they’ll change their policies and start explaining their actions like most popular gaming communities do. Many of us remember how Steam Support used to recover stolen accounts and ended up “stealing” skins themselves—banning without real reasons is basically the same thing, and that’s a serious accusation.\n\nSo, r/Steam, see you soon. I think you understand what you’re doing and how many people you’ve illegally deprived of their assets. I want to raise this issue—not just for the U.S., but for the entire world. You’ve banned class-action lawsuits? **Welcome to Texas.** I recommend starting to look for licensed attorneys in Texas, because I’d love to discuss your company’s policies, feedback, and support agents named Olga—a name that strongly associates with Russian users. Maybe it’d be easier to move your company to Moscow? But I’d be happy to discuss these critical issues on behalf of the global gaming community.\n\nAlso, I wouldn’t recommend ignoring the lawsuit request that will be sent to your physical address and email address, as the court will proceed without you, and that might upset you—especially since things aren’t going so well for a company with stocks like yours.\n\n**Thanks to everyone who took the time to read this. For those who need real help with an unjust Steam ban without any explanation, I’d be happy to assist. For users from Texas, we can easily file a collective lawsuit against Steam—let’s connect and make it happen.**\n02 / Sieć na rzecz rozwoju „Steam”\nInfrastruktura publiczna.Nagrano na dużą skalę.\nPobierz wszystkie utwory z albumu „252” ↓\n\nDołączony output_steam_network Snapshot rejestruje repozytoria, publiczne powiązania między autorami a forkami oraz nakładające się profile. Są to opublikowane dane — co zostało stworzone, kto miał w tym udział, co zostało rozgałęzione. Dokumentacja publicznych możliwości jest tym, co musi uwzględniać projekt „Valve”.\n\nRepozytorium / opis\tAutorzy\tForkers\tZapisane profile\nalliedmodders/amxmodx\n\nAMX Mod X - Half-Life 1 Scripting and Administration\n\n\t40\t40\t80\nalliedmodders/sourcemod\n\nSourceMod - Source Engine Scripting and Administration\n\n\t40\t40\t80\nDoctorMcKay/node-steam-user\n\nAllows interaction with the Steam network via the Steam client protocol\n\n\t40\t40\t80\nFacepunch/Facepunch.Steamworks\n\nAnother fucking c# Steamworks implementation\n\n\t40\t40\t80\nJustArchiNET/ArchiSteamFarm\n\nC# application with primary purpose of farming Steam cards from multiple accounts simultaneously.\n\n\t40\t40\t80\nodota/core\n\nOpenDota: Open source Dota 2 data platform with automated replay parsing\n\n\t40\t40\t80\nodota/dotaconstants\n\ndotaconstants: Static data for Dota applications\n\n\t40\t40\t80\nodota/web\n\nOpenDota: React web UI for Dota 2 statistics using the OpenDota platform\n\n\t40\t40\t80\nsplewis/get5\n\nCS:GO Sourcemod plugin for competitive matches/scrims\n\n\t40\t40\t80\nSteamDatabase/FileDetectionRuleSets\n\n🔎 Rules to detect game engines and other technologies based on Steam depot file lists\n\n\t40\t40\t80\nSteamRE/SteamKit\n\nSteamKit2 is a .NET library designed to interoperate with Valve's Steam network. It aims to provide a simple, yet extensible, interface to perform various actions on the network.\n\n\t40\t40\t80\nValveSoftware/dxvk\n\ndxvk tree containing branches used by Proton\n\n\t40\t40\t80\nValveSoftware/GameNetworkingSockets\n\nReliable & unreliable messages over UDP. Robust message fragmentation & reassembly. P2P networking / NAT traversal. Encryption.\n\n\t40\t40\t80\nValveSoftware/gamescope\n\nSteamOS session compositing window manager\n\n\t40\t40\t80\nValveSoftware/Proton\n\nCompatibility tool for Steam Play based on Wine and additional components\n\n\t40\t40\t80\nValveSoftware/source-sdk-2013\n\nThe 2013 edition of the Source SDK\n\n\t40\t40\t80\nValveSoftware/wine\n\nWine with a bit of extra spice\n\n\t40\t40\t80\nValveSoftware/steam-devices\n\nList of devices Steam and SteamVR will want read/write permissions on, to help downstream distributions create udev rules/etc\n\n\t39\t40\t79\nValveSoftware/steam-audio\n\nSteam Audio\n\n\t38\t40\t78\nalliedmodders/metamod-source\n\nMetamod:Source - C++ Plugin Environment and Detour Library for the Source Engine\n\n\t37\t40\t77\nalliedmodders/sourcepawn\n\nA small, statically typed scripting language.\n\n\t35\t40\t75\nValveSoftware/Fossilize\n\nA serialization format for various persistent Vulkan object types.\n\n\t31\t40\t71\nrlabrecque/Steamworks.NET\n\nSteamworks wrapper for Unity / C#\n\n\t27\t40\t67\nModDota/moddota.github.io\n\nModDota github pages project.\n\n\t26\t40\t66\nodota/parser\n\nReplay parse server generating JSON log events from Dota 2 replay files\n\n\t26\t40\t66\nValveSoftware/steam-for-linux\n\nIssue tracking for the Steam for Linux beta client\n\n\t26\t40\t66\nSteamRE/DepotDownloader\n\nSteam depot downloader utilizing the SteamKit2 library.\n\n\t24\t40\t64\nJustArchiNET/ASF-ui\n\nThe official web interface for ASF\n\n\t23\t40\t63\nadvancedfx/advancedfx\n\nHalf-Life Advanced Effects (HLAE) is a tool to enrich content creation mainly for the Counter-Strike series.\n\n\t22\t40\t62\nalliedmodders/ambuild\n\nAlliedModders C++ Build System\n\n\t23\t39\t62\nSteamDatabase/BrowserExtension\n\n💻 SteamDB's extension for Steam websites\n\n\t21\t40\t61\nodota/mobile\n\nReact Native apps for viewing Dota 2 data on Android/iOS\n\n\t19\t40\t59\nValvePython/steam\n\n☁️ Python package for interacting with Steam\n\n\t18\t40\t58\nskadistats/clarity\n\nComically fast Dota 2, CSGO, CS2 and Deadlock replay parser written in Java.\n\n\t13\t40\t53\nSteamRE/open-steamworks\n\nOpen Steamworks is a set of reverse engineered headers for the Valve's Steam Client. More or less abandoned now that the Steamworks SDK is publically available.\n\n\t13\t40\t53\nValveSoftware/Source-1-Games\n\nSource 1 based games such as TF2 and Counter-Strike: Source\n\n\t13\t40\t53\nalliedmodders/hl2sdk\n\nHalf-Life 2 SDK Mirrors\n\n\t11\t40\t51\nSteamDatabase/steamdb.info-issues\n\n🚱 Issue tracker for the SteamDB website\n\n\t11\t40\t51\nCSGOFloat/inspect\n\nSource Code that Powers the CSFloat Inspect Link API\n\n\t10\t40\t50\nValveSoftware/SteamOS\n\nSteamOS community tracker\n\n\t10\t40\t50\nalliedmodders/source2mod\n\nExperimental\n\n\t40\t9\t49\nsmiley/steamapi\n\nAn unofficial object-oriented Python library for accessing the Steam Web API.\n\n\t9\t40\t49\nSteamDatabase/GameTracking\n\n🛢 Dumping things, so you don't have to\n\n\t8\t40\t48\nValveSoftware/counter-strike_rules_and_regs\n\nCS:GO\n\n\t7\t40\t47\nValveSoftware/openvr\n\nOpenVR SDK\n\n\t6\t40\t46\nSteamDatabase/easy-markdown-editor\n\nEasyMDE: A simple, beautiful, and embeddable JavaScript Markdown editor. Delightful editing for beginners and experts alike. Features built-in autosaving and spell checking.\n\n\t40\t4\t44\nValveSoftware/Dota-2\n\nTracker for issues specific to Linux and Mac in the Reborn client. If you have a general issue or non-system-specific feature request please go to dev.dota2.com\n\n\t6\t38\t44\nValveSoftware/Dota2-Gameplay\n\nPublic Bug Tracker for Dota 2\n\n\t4\t40\t44\nJustArchiNET/ArchiBot\n\nNo description in the capture.\n\n\t16\t27\t43\nztizzlegaming/CSGOWinBig\n\nOpen-source Counter-Strike: Global Offensive jackpot betting website.\n\n\t1\t40\t41\nJustArchiNET/mantis.justarchi.net\n\nMantis Bug Tracker (MantisBT)\n\n\t40\t0\t40\nodota/node-steam-user\n\nAllows interaction with the Steam network via the Steam client protocol\n\n\t40\t0\t40\nModDota/TypeScriptAddonTemplate\n\nDota 2 addon template with TypeScript Panorama and VScripts.\n\n\t9\t29\t38\nValvePython/vdf\n\n📜 Package for working with Valve's text and binary KeyValue format\n\n\t6\t32\t38\nalliedmodders/amtl\n\nAlliedModders C++ Template Library\n\n\t17\t19\t36\nValvePython/dota2\n\n🐸 Python package for interacting with Dota 2 Game Coordinator\n\n\t5\t30\t35\nalliedmodders/stripper-source\n\nStripper:Source\n\n\t13\t21\t34\nAllyans3/steam-market-api-v2\n\nSteam Market API v2 package\n\n\t3\t31\t34\nModDota/dota-tutorial\n\nCustom game DOTA tutorial.\n\n\t11\t23\t34\nodota/blog\n\nNo description in the capture.\n\n\t29\t3\t32\nOpsecGuy/BetterGo\n\nExternal CS:GO cheat written in python.\n\n\t1\t27\t28\npxvr-official/1\n\n無許諾配信 企業理念剽窃 動物の森収益化 大神ミオ権利者削除 戌神権利侵害発言 常闇トワ炎上 夜空メルストーカー被害 建築王サポーター放置 赤十字マーク 魔乃アロエ卒業 一つの中國支持声明 大空昴3Dライブ 無限延期清掃員職業差別 日清コラボ楽曲 musedash非公開 rog案件取り消し 壁画ライブ 丁真 Ding Zhen 郑爽 Zheng Shuang 防护林 与朵小天使w 伊月猫凛 本主萌埋午休傻 汪峰 重生细胞 壁纸 比利海灵顿 香蕉君 van 田所浩二 抽象带篮子 抗压背锅吧 季子越 蒋明辉 傻逼…\n\n\t0\t28\t28\nRevadike/InternalSteamWebAPI\n\nDocumenting the unofficial and internal Steam Web API\n\n\t1\t27\t28\nJoeSzymkowiczFiveM/qb-lootcrate\n\nA CSGO-style case opening script\n\n\t2\t25\t27\nAbrarKL/MyRoulette.XYZ\n\nCSGO / Steam Roulette Site created with PHP and Node JS, using the Material Design front-end framework.\n\n\t1\t25\t26\nJustArchiNET/ASF-WebConfigGenerator\n\nNo description in the capture.\n\n\t10\t15\t25\nModDota/dota-data\n\nAuto-generated Dota 2 resource dumps\n\n\t11\t14\t25\nModDota/TypeScriptDeclarations\n\nTypeScript declarations for Dota 2.\n\n\t11\t14\t25\nModDota/API\n\nNo description in the capture.\n\n\t12\t12\t24\nalliedmodders/cssdm\n\nCounter-Strike:Source Deathmatch\n\n\t10\t13\t23\nSteamDatabase/steamstat.us\n\n✅ Front-end of Steam services status website\n\n\t4\t18\t22\nc0deina/csgojackpotV2\n\nCSGO Jackpot Source\n\n\t1\t20\t21\nValvePython/steamctl\n\n🤸 Take control of Steam from your terminal\n\n\t2\t19\t21\nValvePython/csgo\n\n🔫 Python package for interacting with CS:GO Game Coordinator\n\n\t3\t17\t20\nBeepIsla/csgo-crash-exploit\n\nAllows you to crash any Windows user\n\n\t3\t16\t19\nValvePython/vpk\n\n📦 Open, Search, Extract and Create VPKs in python\n\n\t4\t15\t19\nalliedmodders/SM-SteamWorks\n\nExposing SteamWorks functions to SourcePawn.\n\n\t14\t3\t17\nSteamRE/Steam4NET\n\nSteam4NET is a .NET wrapper around the Steamworks C++ interfaces\n\n\t2\t15\t17\nalliedmodders/hl2sdk-manifests\n\nInformation about HL2SDKs shared between Metamod:Source and SourceMod.\n\n\t6\t10\t16\nJustArchiNET/ASF-PluginTemplate\n\nTemplate repository that you can use for creating custom plugins for ArchiSteamFarm.\n\n\t8\t7\t15\nModDota/Dota2AIFramework\n\nGeneral Framework for Dota 2 AI Competitions\n\n\t1\t14\t15\nShkyyl/KeyChamp\n\nExtension for joining free case battle on key-drop automatically\n\n\t1\t14\t15\nSteamDatabase/SteamMonitor\n\n😤 Track Steam's connection manager servers status\n\n\t2\t12\t14\nBaterka/cslore.com\n\nCS:GO gambling site - csgo.style\n\n\t1\t12\t13\nSteamDatabase/SteamTokenDumper\n\n🔢 Submit users' PICS access tokens to SteamDB\n\n\t2\t11\t13\nmonoblocker/roulette\n\nRoulette CS:GO made in React and Typescript\n\n\t1\t11\t12\nzsith/launcher.user.js\n\n// ==UserScript== // @name AposLauncher // @namespace AposLauncher // @include http://agar.io/* // @version 3.062 // @grant none // @author http://www.twitch.tv/apostolique // ==/UserScript== var aposLauncherVersion = 3.062; Nu…\n\n\t1\t11\t12\nLincolnIT/CSGODouble-bot-automated\n\nCSGODouble Automated, auto Betting Bot.\n\n\t1\t10\t11\nvladpuz/steam-market\n\nSteam market API client\n\n\t4\t7\t11\nmcgrizzz/Cstrike.bet\n\nCSGO Roulette Website Angular frontend, nodejs backend, and steam trading bots\n\n\t1\t9\t10\nodota/underlords-web\n\nUI for OpenUnderlords\n\n\t5\t5\t10\nSteamDatabase/SteamToTwitter\n\n🕊 Tweets announcements from various Steam groups\n\n\t1\t9\t10\nModDota/AbilityLuaSpellLibrary\n\nThe successor to the Spell Library by Pizzalol\n\n\t4\t4\t8\nalvinl/bitskins\n\nUnofficial BitSkins API client\n\n\t2\t5\t7\nb1naryth1ef/steamy\n\nA Python Steam community and market API interface that will get you all hot and bothered\n\n\t2\t5\t7\nkratos1812/Case-Opening\n\nIn-game case opening system for CSGO servers.\n\n\t2\t5\t7\nodota/docs\n\nOpenDota API documentation\n\n\t4\t3\t7\nSteamDatabase/steam-advanced-access-fetch-players\n\n📈 Simple script to fetch Steam player count\n\n\t1\t6\t7\nTheRioMiner/CsgoBetterExternalRaytrace\n\nOverridden maps pack for better external raytrace\n\n\t1\t6\t7\nalliedmodders/hl2sdk-mock\n\nMock HL2SDK and Server\n\n\t5\t1\t6\nchristophersu/PySteamMarket\n\nPython API for getting prices from the Steam market.\n\n\t1\t5\t6\nExtremelyd1/Strat-Roulette\n\nCS:GO Sourcemod Plugin\n\n\t2\t4\t6\ngiovanni-orciuolo/double-sdk\n\nA simple way to write CS:GO cheats!\n\n\t2\t4\t6\nJustArchiNET/Madness\n\nMadness embraces your project by including compatibility layer for selected APIs normally not available on .NET Framework target.\n\n\t5\t1\t6\nModDota/TypescriptPanoramaDeclarations\n\nNo description in the capture.\n\n\t4\t2\t6\nodota/rapier\n\nA JavaScript Dota 2 (Source 2) replay parsing library\n\n\t1\t5\t6\nVozn1akHero/CSGOCaseOpeningSimulator\n\nCounter-Strike case opening simulator which resembles the good old CS:GO user interface\n\n\t3\t3\t6\nautarc/steam-store\n\nAPI client for the unofficial steam storefront/big picture resource\n\n\t2\t3\t5\nBETTING-CODE/awesome-esports-sites\n\nA curated list of awesome esport betting sites – live, statistics and other resources.\n\n\t1\t4\t5\njonteohr/Better-Warden\n\nAn improved and more advanced warden plugin with a custom menu for CS:GO jailbreak servers!\n\n\t2\t3\t5\nLudzikk/CSGO-Gambling-Site\n\nhttps://ludzikk.github.io/CSGO-Gambling-Site/\n\n\t1\t4\t5\nModDota/find-steam-app\n\nFind location of an installed Steam app\n\n\t3\t2\t5\nmprey/csgocact.us\n\nsource code for csgocact.us\n\n\t1\t4\t5\nnezu-cc/ServerCrasher\n\nCS:GO Server Crasher\n\n\t1\t4\t5\nodota/testfiles\n\nStores test replay files\n\n\t2\t3\t5\nodota/underlordsconstants\n\nConstant data for Dota Underlords\n\n\t3\t2\t5\nSnaBe/node-steam-market-fetcher\n\nA Node.js wrapper for the Steam Community Market API.\n\n\t2\t3\t5\nSteamDatabase/.github\n\n💗 Organization-wide community health files\n\n\t1\t4\t5\nwolfcon/RIP-HLTV-BET\n\nRIP BET AD (For Tampermonkey) https://greasyfork.org/en/scripts/423484-rip-hltv-bet\n\n\t2\t3\t5\nalliedmodders/blaster.net\n\nSource and GoldSrc Query Tool\n\n\t2\t2\t4\ncatears124/CS2-Price-API\n\nsimple python cs2 steam market price API\n\n\t1\t3\t4\nialakey/caseforge\n\nOpen-source CS2 case-opening platform: Steam auth, provably fair openings, RTP-balanced case builder, withdrawals bought on market.csgo.com and an admin CRM.\n\n\t1\t3\t4\nIlusion9/csgo-fix-mapchange-crash-sm\n\nFix players crash on map change.\n\n\t1\t3\t4\nismail0234/Benson-Map-Crash-Fixer\n\nCSGO Map Change Client Crash Fixer\n\n\t1\t3\t4\njaxwilko/steam-market-api\n\nPHP - Composer Compatible - Steam Market API\n\n\t2\t2\t4\nJustArchiNET/ArchiTag\n\nArchiTag is a very small utility based on Python 3 and Mutagen to provide missing functionality in opusenc of writing specific Opus metadata, such as total number of tracks or track number.\n\n\t1\t3\t4\nModDota/DotaUI\n\nNo description in the capture.\n\n\t2\t2\t4\nnode-steam/market-pricing\n\nWrapper for the unofficial Steam Market Pricing API\n\n\t1\t3\t4\nodota/media\n\nStores media files for Dota projects\n\n\t2\t2\t4\nSergeyIvanovDevelop/Crypto-Steam-Platform\n\nThe repository contains the code and configuration to run a platform for creating cryptocurrency stakes for arbitrary ERC20 tokens.\n\n\t1\t3\t4\nAareksio/csgodouble-floatchecker\n\nAdds context menu option to check item's float value\n\n\t1\t2\t3\nchinm4/CSGOdrop\n\nA online csgo gambling casino that includes a variety of mini games that allows you to win csgo skins\n\n\t2\t1\t3\nCruze03/CSGO-Case-Opening-Prank\n\nCommand:- !prank (Admin flag \"n\" required)\n\n\t1\t2\t3\nDhruva-Kapadia/CSGOTrollGG\n\nCSGO Case Opening Simulator\n\n\t2\t1\t3\nErhanCSGO/CSGOPolygon-prediction\n\nCSGOPolygon.com - prediction script, double your coins by using this tool\n\n\t1\t2\t3\nEv-Hoang/Bedrock-Chest-Case-Opening\n\nHypixel Skyblock Dungeon Mod - Bedrock Chest Opening Animation (CSGO Style)\n\n\t1\t2\t3\njmjp/csgo-roulette\n\nA csgo gambling roulette make with VueJS 3\n\n\t2\t1\t3\nJustArchiNET/ArchiCrowdin\n\nNo description in the capture.\n\n\t1\t2\t3\nLeonSK/WearMarketInspector\n\nRetrieve Wear Value (Float Value) and Pattern Index from Steam Community Market using http://csgo.exchange API\n\n\t1\t2\t3\nmaximgeerinck/csgo-gamble\n\nCSGO gambling website\n\n\t1\t2\t3\nModDota/BugTracker\n\nListing bugs for Dota 2 Custom Games\n\n\t2\t1\t3\nplwp/mma-betting\n\nUFC/MMA betting model with Pinnacle steam detection for AU book latency arb\n\n\t2\t1\t3\nSouthsideswag16/Csgo-Gambling-Site\n\nNo description in the capture.\n\n\t2\t1\t3\ntacyarg/csgofiesta-frontend-react\n\nRemastered version a the long time favorite csgo site\n\n\t2\t1\t3\nVelorasse/Mutah-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-csmoney-csgoskins\n\ngambling script for Mutah, Keydrop, csmoney, and csgoskins, featuring hacks, cheats, and predictors. Offers strategies to boost winning odds and optimize performance on these platforms.\n\n\t3\t0\t3\nalliedmodders/am-github-artifact-webhook\n\nNo description in the capture.\n\n\t2\t0\t2\ncharamza/roulette\n\nCSGO like roulette in JS\n\n\t1\t1\t2\nCruze03/CSGO-PugSetup-RoundRestore\n\nSometimes (player dropped/crashed) which would be disadvantage for a team. It would be very handy to restore the match to the previous round.\n\n\t1\t1\t2\ncsgorol/CSGO-ROLL-Crash-Predictor\n\nCSGO-ROLL-Crash-Predictor\n\n\t1\t1\t2\nFoxSerito/FOXWORLD_plugin_DoubleJump_CSGO\n\nПлагин SourceMod (CSGO). Двойной прыжок с эффектом.\n\n\t1\t1\t2\nhkehayovmoonbiz/CS2-Casino-Full-Source-Code\n\nCS2, CS2 betting platforms, Skin Roulette, Case Unboxing, Crash games, Jackpot, purchase CS2 casino source, crypto gambling\n\n\t1\t1\t2\nJustZakary/steamstoreapi\n\nThis NPM module is a API wrapper that makes the steam unofficial API easier to use.\n\n\t2\t0\t2\njzimr/steam-market-api\n\nA java library to easily get Steam Community Market data\n\n\t1\t1\t2\nMomohime/CSGO.Network-Jackpot-Coinflip\n\nNo description in the capture.\n\n\t1\t1\t2\nnnjjswat/moneybot\n\nautomated bots for bustabit (formerly known as moneypot), csgo crash, etc\n\n\t0\t2\t2\nodota/carry\n\nLegacy Application for donations to the OpenDota project\n\n\t1\t1\t2\nodota/PublicMatchDataBot\n\nA Discord bot to remind users to turn on Expose Public Match Data in the Dota 2 client\n\n\t1\t1\t2\nOrillio/CSGOBet.com\n\nCSGO roulette web app\n\n\t2\t0\t2\nripexz/csgo-bet-alert\n\nA Chrome extension to keep track of active CS:GO Lounge matches.\n\n\t1\t1\t2\nrrpvm/lumen_sense-beta-deprecated-\n\nthis is internal csgo cheat written by me(no paste, self reverse structures). start : ~6 August 2020, end : ~ 14 December 2020\n\n\t1\t1\t2\nRuthless222/csgoscore\n\nThis is a Counter Strike Global Offensive Betting Site. You chose the skins you want to bet and try to win jackpots\n\n\t2\t0\t2\ntfburns/CSGO-cases-PL\n\nExpected profit-loss of CS:GO case openings\n\n\t1\t1\t2\nTomDra/CSGO-Case-Data-Analysis\n\nWorks out the most profitable CS:GO case at that current time\n\n\t1\t1\t2\nValvePython/dota2-wrappers\n\nNo description in the capture.\n\n\t1\t1\t2\nValvePython/teamfortress2-closed-captions\n\nThis project aims to provide a set of closed captions for Team Fortress 2\n\n\t1\t1\t2\nVistaNetGTX/Cstrike.bet-\n\nCSGO Roulette Website Angular frontend, nodejs backend, and steam trading bots\n\n\t1\t1\t2\nwafflas/csgo-case-opening-simulator\n\nI created a cs go case opening simulator for a meme coin\n\n\t0\t2\t2\nAdmiral-Enigma/Le_Coinflip\n\nConflip game\n\n\t1\t0\t1\nadryeljuliao/roulette-csgo\n\nNo description in the capture.\n\n\t1\t0\t1\nAndreuTheG/csgo-coinflip-web\n\nCSGO Gambling Coinflip Website\n\n\t1\t0\t1\nasmilen/csgoDouble\n\na b c\n\n\t1\t0\t1\nb1naryth1ef/csgofort\n\nA CSGO portal for trading, betting, analytics, and more!\n\n\t1\t0\t1\nBaterka/PrivateSteamBettingWebsite2024\n\nPrivate Steam (Counter-Strike 2) betting/gambling website - Roulette, Jackpot\n\n\t1\t0\t1\nblackcaer/SteamTradeHandler\n\nAutomation of Steam trading. Helper project for bet automation.\n\n\t1\t0\t1\nBTheCoderr/theRounders\n\nThe Rounders - A professional-grade sports betting analytics platform combining real-time odds tracking, sharp movement detection, and advanced statistical analysis. Features include line shopping, steam move alerts, power rankings, and comprehensive bet t…\n\n\t1\t0\t1\nCallumHemsley/KazeBot\n\nA Twitch chat betting bot for CSGO, simply bet a certain amount of points, and double if you win, lose all if you lose. Simple.\n\n\t1\t0\t1\nchrisjpm/CSGOJackpotTemplate\n\nFront end for a jackpot site\n\n\t1\t0\t1\ncolinsenner/valve-bug-bounty\n\nFor many years CS:GO, Dota 2, and Team Fortress 2 servers had a bug that allowed malicious users to leak crucial server process memory or reliably crash any server.\n\n\t1\t0\t1\ncoryypeters/nrl-odds-intelligence-pipeline\n\nReal-time sports betting odds intelligence — streaming pipeline that detects line movement, steam, and arbitrage across bookmakers. Python · Redis Streams · FastAPI · React.\n\n\t1\t0\t1\ndeissh/dev-csgoduo\n\nCS:GO. Bot for receiving things on the site (Polygon, Duo, Double and etc).\n\n\t1\t0\t1\ndom1torii/even-better-font-manager\n\nSimply even better cross-platform tool for CS2 Font Management\n\n\t1\t0\t1\nDONnicov/CSGO-crash-black-screen-\n\nsolution csgo crash black screen and close csgo\n\n\t1\t0\t1\nDoubleBoters/CsgoDouble\n\nNo description in the capture.\n\n\t1\t0\t1\ndownarowiczd/DoubleBot\n\nAn old CSGO Double Bot written for my friend. - 07.05.2016\n\n\t1\t0\t1\nErayBahar/steammarketscraper\n\nSteam Market Scraper Python-based tool that tracks real-time CS2 skin prices using Steam's hidden API. It fetches the lowest sell and highest buy offers for any item, helping you monitor deals or snipe underpriced listings automatically.\n\n\t1\t0\t1\nfairydarkness/SteamwebmailAPI\n\nUnofficial Python API for steamwebmail.com Fast, lightweight, and browserless library for automating steamwebmail.com. Support for session management, proxy, folder navigation, and message retrieval\n\n\t1\t0\t1\nFAQU2/CSGO-Coinflip-MyJailShop\n\nSourcemod plugin which provides a Coinflip system for MyJailShop.\n\n\t1\t0\t1\nFlamesONE/csgo-case-opening\n\nNo description in the capture.\n\n\t1\t0\t1\nFunnyRain/csgorun-crash-watch\n\n🚀 CsgoRun dump crash. / 🚀 CsgoRun дамп крашей.\n\n\t1\t0\t1\ngeohdgio/Venatus-Autenticator\n\nეს არის Steam Autenticator ქართული Venatus Trade & Betting ისთვის და Valve News Georgia-სთვის.\n\n\t1\t0\t1\nhakanstarlord/steam-bot\n\nSports betting steam-move signal detection with ML pipeline (XGBoost stacking + isotonic calibration), backtesting engine, Flask dashboard, and Telegram alerts.\n\n\t1\t0\t1\nHvH-gg/CSGO-Item-CrashFix\n\nA plugin for Counter-Strike: Global Offensive that fixes an exploit where receiving CS2 Items will cause CS:GO clients to crash\n\n\t1\t0\t1\nHvH-gg/CSGO-NetMsg-CrashFix\n\nA plugin for Counter-Strike: Global Offensive that fixes an exploit where spamming NetMsg_StringCmd packets would result in a server crash.\n\n\t1\t0\t1\nisybycnsmam/SteamLibrary\n\nLegacy Steam Unofficial API\n\n\t1\t0\t1\nItsTangerine/SteamApis.Net\n\nUnofficial https://steamapis.com .NET library, supporting .NET 6.0+\n\n\t1\t0\t1\nJustArchiNET/JustArchi.net\n\nNo description in the capture.\n\n\t1\t0\t1\nkiri-osint/CS2-Info-Hub-Bot\n\nA Telegram bot that acts as a hub for CS2 players, providing real-time skin prices, server stats, and user profile/inventory inspection using official and unofficial Steam APIs.\n\n\t1\t0\t1\nKoshkaj/monte\n\nGamified csgo gambling platform implementation\n\n\t1\t0\t1\nmadsab/CaseOpening\n\nA school project using Java. Simulating the case opening from CSGO and more.\n\n\t1\t0\t1\nman90es/steamcardexchange-api\n\nSteamCardExchange.net unofficial REST API server (scraper).\n\n\t1\t0\t1\nMattPua/steam-unofficial-docs\n\nUnofficial docs for Steam APIs with fumadocs\n\n\t1\t0\t1\nMetallist1/Portfolio.CsgoWinGambleProject\n\nA website that was done in 2017 September. Websites focus was on gambling with Counter-Strike items. Project was largely completed however backups were not done correctly, this resulted in half a year of wasted improvements to the code. The website was test…\n\n\t1\t0\t1\nmikebobadilla/csgo-jackpot\n\nNo description in the capture.\n\n\t0\t1\t1\nmikebobadilla/meteor-csgojackpot\n\nCssgo Jackpot done in meteor\n\n\t1\t0\t1\nModDota/D2VDump\n\nDota 2 Server VScript API Dumper\n\n\t1\t0\t1\nModDota/DotaTracking\n\nNo description in the capture.\n\n\t1\t0\t1\nModDota/eslint-config\n\nESLint config by ark120202\n\n\t1\t0\t1\nmr-codinglv/Casino-script\n\nscript casino - script betting - exchange script - bc casino - casino csgo - script bet - betwin script\n\n\t1\t0\t1\nMrKeelik/MrKeel\n\nCSGO DOUBLE BOT\n\n\t1\t0\t1\nnoahlatzel/CSGORollHelper\n\nLeveraging positive expected value on triple green jackpots on CSGORoll!\n\n\t1\t0\t1\noddsgpt/oddsgpt-market-intelligence\n\nResearch on football betting markets, closing odds, CLV, market efficiency, steam moves, AI betting systems, and sports market intelligence.\n\n\t1\t0\t1\noEXU/csgo-server-crasher\n\nCSGO SERVER CRASHER\n\n\t1\t0\t1\nPrdTTony/CSGO-Roulette\n\n[CSGO] Roulette System. Bet on RED or Black and win x2 credits\n\n\t1\t0\t1\nr-adamski/csgo-jackpot\n\nNo description in the capture.\n\n\t1\t0\t1\nSahotallo/Turan-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-Skinbaron-hellcase\n\ngambling script for Turan, Keydrop, Skinbaron, and Hellcase, providing hacks, cheats, and predictors. Includes strategies to improve winning chances and enhance gameplay on these platforms.\n\n\t1\t0\t1\nsamuelcsouza/steam-marketplace-api\n\nAn unofficial API to get data from the Steam Marketplace.\n\n\t1\t0\t1\nSKINSTRACK/CS2-Price-API\n\nSkinstrack offers a free, limited API endpoint that returns Steam item prices. Paid plans additionally provide access to pricing data from multiple marketplaces, making it possible to compare prices across different markets through a single API.\n\n\t1\t0\t1\nsnmtriet/CSGO-Casino-Full-Source-Code\n\nCSGO, CSGOEmpire, Case Opening, Case Battles, Roulette, Coinflip, buy csgo gambling site, gambling\n\n\t1\t0\t1\nSteamRE/homebrew-tools\n\nRepository for installation of SteamRE tools via Homebrew (http://brew.sh)\n\n\t1\t0\t1\nSteamRE/opensteamworks.org\n\nNo description in the capture.\n\n\t1\t0\t1\nTheQuack45/CsgoCaseOpenProgram\n\nSimple program to parse an XML file with CS:GO case information and \"simulate\" case openings\n\n\t1\t0\t1\nTLClassless/StratRouletteCSGO\n\nA 'Strat Roulette' web app for CS:GO!\n\n\t1\t0\t1\ntomasoom/csgoCaseOpening\n\nNo description in the capture.\n\n\t1\t0\t1\nvitaliy-evsyukov/steamgifts-autobet-bookmarklet\n\nbookmarklet for automatic bets on steamgifts.com\n\n\t1\t0\t1\nXpravdaX/RouletteCSGO\n\nNo description in the capture.\n\n\t1\t0\t1\nYuiKasumii/steam_api_unofficial\n\nUnofficial Steam Game Information Database\n\n\t1\t0\t1\nZexuz/Steam-Betting\n\nA betting website build ontop of STEAM's ecosystem\n\n\t1\t0\t1\nANK-RULZZ/steam-jackpot-site\n\ngetting some errors and would like some one to help me with it thank you!!!\n\n\t0\t0\t0\nasmilen/CsgoDoubleVS\n\nNo description in the capture.\n\n\t0\t0\t0\nCORNOODOSADAS/CSGOWeed\n\nCsgo Jackpot and Coinflip\n\n\t0\t0\t0\nCSGOApple/csgoapple\n\nJackpot Site\n\n\t0\t0\t0\nCSGOFAST/csgofast-api\n\nNo description in the capture.\n\n\t0\t0\t0\nDonakall/csgoDoublebot\n\nAutomated bot for csgodouble\n\n\t0\t0\t0\nfedor-selivanov/csgo-fast-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nfoldageros/csgod\n\ndouble bot\n\n\t0\t0\t0\ngmod-gambling/gmod-gambling\n\nNo description in the capture.\n\n\t0\t0\t0\nierome/CSGOBoss-BackEnd\n\nBack end version of CSGOBoss. This was a CSGO Gambling site named CSGOBoss. Coded by an old friend of mine Dahquan Hinds (https://github.com/dahquan/) Thought I would release this to help out any one who would need it.\n\n\t0\t0\t0\njamienp1/CSGODOUBLE-BOT-AUTO\n\ni got a bot thats is betting on the last winning color except from green and if you lose it will double the coins you set it to bet, pretty good, so when there comes a loooong train you will be gaining a bit of money codepaste_net/ugmt92 remove all the _ an…\n\n\t0\t0\t0\nJEYONER/CSGOTOXIC\n\nPAGINA DE JACKPOT CSGO SKINS\n\n\t0\t0\t0\nkalrish/csgo-jackpot\n\nStressful but funny zombie-like Counter-Strike: Global Offensive game mode.\n\n\t0\t0\t0\nkrys12345/roulettee\n\n// ==UserScript== // @name CSGO Predict Bot // @namespace http://csgodouble.com // @version 1.0 // @description predicts what number its gonna be // @author Meee // @match http://www.csgodouble.com/ // @grant none // ==/…\n\n\t0\t0\t0\nLilDuggiMuffi/CSGODouble-Working-Bot\n\nFixed CSGO Double Bot\n\n\t0\t0\t0\nLyricLy/Steam2Proton\n\nCheck if all your Steam games will work with Proton! Uses the official Steam API and the unofficial Proton API.\n\n\t0\t0\t0\nM0NsTeR77/csgo-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nozanhalis/Hi\n\n// ==UserScript== // @name CS GO LOUNGE BOT-Ozan Halis // @namespace http://csgolounge.com/ // @version 0.6.6 // @description Cs Go Lounge Hızlı BOT // @match http://csgolounge.com/* // @match http://dota2lounge.com/* // @updateURL h…\n\n\t0\t0\t0\nscoobertus/CSGO-DoubleBot\n\nNo description in the capture.\n\n\t0\t0\t0\nTradeal/CSGO-Jackpot-Bot\n\nNo description in the capture.\n\n\t0\t0\t0\nValvePython/artifact\n\nNo description in the capture.\n\n\t0\t0\t0\nVampire/CSGO-Roulette-Bot\n\nNo description in the capture.\n\n\t0\t0\t0\nvdemans/csgo-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nVocoreVideo/CSGODungeon-\n\nCSGO Jackpot\n\n\t0\t0\t0\nwayz-dev/csgofloat\n\nNo description in the capture.\n\n\t0\t0\t0\n\nZrzut ekranu: 17 września 2026, 11:19:11 zgodnie z informacją w źródle; strefa czasowa nieokreślona. Zbiór relacji jest ograniczony w eksporcie (wiele kategorii kończy się na 40). Liczba autorów i osób tworzących rozgałęzienia wynosi łącznie 4,554 wpisów dotyczących ról w 4,214 różnych parach profil–repozytorium; jeden profil może pełnić obie role. Wartość zero oznacza brak rekordów w danej kategorii. Nazwy repozytoriów mogą zawierać aliasy lub warianty wielkości liter; sumy zachowują konwencje liczenia stosowane w źródle.\n\nPochodzenie źródła\nUtworzone na podstawie zebranych przez Ciebie plików.\nZeznania poparcia\n2323/reddit_scams_ultra/steam_support_tickets_MEGA.json · wiersze 45, 58, 107, 110, 294\nMigawka sieciowa\nnetwork-repositories.csv · raw_data.json · overlaps.csv · summary.txt (historyczne ścieżki źródeł zachowane w pliku manifestu)\n\nManifest zawiera ścieżki źródłowe, rozmiary w bajtach, skróty SHA-256owe oraz pozycje wybranych rekordów. Surowe dane z przechwycenia pozostają oddzielone od interpretacji przeprowadzonej w ramach dochodzenia.\n\nPobierz manifest źródłowy ↓",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam Dowody dotyczące egzekwowania przepisów — dokumentacja pomocnicza i sieć deweloperów"
          },
          {
            "level": 2,
            "id": null,
            "text": "Zapoznaj się ze skargą.Proszę dołączyć plik źródłowy."
          },
          {
            "level": 3,
            "id": null,
            "text": "Permanent sanction & closed appeals"
          },
          {
            "level": 4,
            "id": null,
            "text": "Permanently banned Steam account without a clear explanation, need help!"
          },
          {
            "level": 3,
            "id": null,
            "text": "Account recovery & a reported $10,000 loss"
          },
          {
            "level": 4,
            "id": null,
            "text": "Got $10k stollen from steam inventory due to steam' support fault."
          },
          {
            "level": 3,
            "id": null,
            "text": "A reported $500+ loss & template replies"
          },
          {
            "level": 4,
            "id": null,
            "text": "Funds stolen through steam market. Disappointed with Steam response.(or lackthereof)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam Guard & an item-restoration refusal"
          },
          {
            "level": 4,
            "id": null,
            "text": "Many people are losing item via clicking links where steam guard is enabled and steam support doesn't not restore items."
          },
          {
            "level": 3,
            "id": null,
            "text": "Selective enforcement & an unexplained ban"
          },
          {
            "level": 4,
            "id": null,
            "text": "🚨 Steam Bans Without Reason and Ignores Its Community — What’s Going On?"
          },
          {
            "level": 2,
            "id": null,
            "text": "Infrastruktura publiczna.Nagrano na dużą skalę."
          },
          {
            "level": 2,
            "id": null,
            "text": "Utworzone na podstawie zebranych przez Ciebie plików."
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/pl/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/pl/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/selected-support-records.json",
          "https://phishdestroy.io/steam_dossier/pl/investigation_part2.html#outsourcing-case",
          "https://www.reddit.com/r/ohnePixel/comments/1hahqx2/permanently_banned_steam_account_without_a_clear/",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://www.reddit.com/r/DotA2/comments/r55bd7/many_people_are_losing_item_via_clicking_links/",
          "https://www.reddit.com/r/SteamUncensored/comments/1kjt2fa/steam_bans_without_reason_and_ignores_its/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/network-repositories.csv",
          "https://github.com/alliedmodders/amxmodx",
          "https://github.com/alliedmodders/sourcemod",
          "https://github.com/DoctorMcKay/node-steam-user",
          "https://github.com/Facepunch/Facepunch.Steamworks",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://github.com/odota/core",
          "https://github.com/odota/dotaconstants",
          "https://github.com/odota/web",
          "https://github.com/splewis/get5",
          "https://github.com/SteamDatabase/FileDetectionRuleSets",
          "https://github.com/SteamRE/SteamKit",
          "https://github.com/ValveSoftware/dxvk",
          "https://github.com/ValveSoftware/GameNetworkingSockets",
          "https://github.com/ValveSoftware/gamescope",
          "https://github.com/ValveSoftware/Proton",
          "https://github.com/ValveSoftware/source-sdk-2013",
          "https://github.com/ValveSoftware/wine",
          "https://github.com/ValveSoftware/steam-devices",
          "https://github.com/ValveSoftware/steam-audio",
          "https://github.com/alliedmodders/metamod-source",
          "https://github.com/alliedmodders/sourcepawn",
          "https://github.com/ValveSoftware/Fossilize",
          "https://github.com/rlabrecque/Steamworks.NET",
          "https://github.com/ModDota/moddota.github.io",
          "https://github.com/odota/parser",
          "https://github.com/ValveSoftware/steam-for-linux",
          "https://github.com/SteamRE/DepotDownloader",
          "https://github.com/JustArchiNET/ASF-ui",
          "https://github.com/advancedfx/advancedfx",
          "https://github.com/alliedmodders/ambuild",
          "https://github.com/SteamDatabase/BrowserExtension",
          "https://github.com/odota/mobile",
          "https://github.com/ValvePython/steam",
          "https://github.com/skadistats/clarity",
          "https://github.com/SteamRE/open-steamworks",
          "https://github.com/ValveSoftware/Source-1-Games",
          "https://github.com/alliedmodders/hl2sdk",
          "https://github.com/SteamDatabase/steamdb.info-issues",
          "https://github.com/CSGOFloat/inspect",
          "https://github.com/ValveSoftware/SteamOS",
          "https://github.com/alliedmodders/source2mod",
          "https://github.com/smiley/steamapi",
          "https://github.com/SteamDatabase/GameTracking",
          "https://github.com/ValveSoftware/counter-strike_rules_and_regs",
          "https://github.com/ValveSoftware/openvr",
          "https://github.com/SteamDatabase/easy-markdown-editor",
          "https://github.com/ValveSoftware/Dota-2",
          "https://github.com/ValveSoftware/Dota2-Gameplay",
          "https://github.com/JustArchiNET/ArchiBot",
          "https://github.com/ztizzlegaming/CSGOWinBig",
          "https://github.com/JustArchiNET/mantis.justarchi.net",
          "https://github.com/odota/node-steam-user",
          "https://github.com/ModDota/TypeScriptAddonTemplate",
          "https://github.com/ValvePython/vdf",
          "https://github.com/alliedmodders/amtl",
          "https://github.com/ValvePython/dota2",
          "https://github.com/alliedmodders/stripper-source",
          "https://github.com/Allyans3/steam-market-api-v2",
          "https://github.com/ModDota/dota-tutorial",
          "https://github.com/odota/blog",
          "https://github.com/OpsecGuy/BetterGo",
          "https://github.com/pxvr-official/1",
          "https://github.com/Revadike/InternalSteamWebAPI",
          "https://github.com/JoeSzymkowiczFiveM/qb-lootcrate",
          "https://github.com/AbrarKL/MyRoulette.XYZ",
          "https://github.com/JustArchiNET/ASF-WebConfigGenerator",
          "https://github.com/ModDota/dota-data",
          "https://github.com/ModDota/TypeScriptDeclarations",
          "https://github.com/ModDota/API",
          "https://github.com/alliedmodders/cssdm",
          "https://github.com/SteamDatabase/steamstat.us",
          "https://github.com/c0deina/csgojackpotV2",
          "https://github.com/ValvePython/steamctl",
          "https://github.com/ValvePython/csgo",
          "https://github.com/BeepIsla/csgo-crash-exploit",
          "https://github.com/ValvePython/vpk",
          "https://github.com/alliedmodders/SM-SteamWorks",
          "https://github.com/SteamRE/Steam4NET",
          "https://github.com/alliedmodders/hl2sdk-manifests",
          "https://github.com/JustArchiNET/ASF-PluginTemplate",
          "https://github.com/ModDota/Dota2AIFramework",
          "https://github.com/Shkyyl/KeyChamp",
          "https://github.com/SteamDatabase/SteamMonitor",
          "https://github.com/Baterka/cslore.com",
          "https://github.com/SteamDatabase/SteamTokenDumper",
          "https://github.com/monoblocker/roulette",
          "https://github.com/zsith/launcher.user.js",
          "https://github.com/LincolnIT/CSGODouble-bot-automated",
          "https://github.com/vladpuz/steam-market",
          "https://github.com/mcgrizzz/Cstrike.bet",
          "https://github.com/odota/underlords-web",
          "https://github.com/SteamDatabase/SteamToTwitter",
          "https://github.com/ModDota/AbilityLuaSpellLibrary",
          "https://github.com/alvinl/bitskins",
          "https://github.com/b1naryth1ef/steamy",
          "https://github.com/kratos1812/Case-Opening",
          "https://github.com/odota/docs",
          "https://github.com/SteamDatabase/steam-advanced-access-fetch-players",
          "https://github.com/TheRioMiner/CsgoBetterExternalRaytrace",
          "https://github.com/alliedmodders/hl2sdk-mock",
          "https://github.com/christophersu/PySteamMarket",
          "https://github.com/Extremelyd1/Strat-Roulette",
          "https://github.com/giovanni-orciuolo/double-sdk",
          "https://github.com/JustArchiNET/Madness",
          "https://github.com/ModDota/TypescriptPanoramaDeclarations",
          "https://github.com/odota/rapier",
          "https://github.com/Vozn1akHero/CSGOCaseOpeningSimulator",
          "https://github.com/autarc/steam-store",
          "https://github.com/BETTING-CODE/awesome-esports-sites",
          "https://github.com/jonteohr/Better-Warden",
          "https://github.com/Ludzikk/CSGO-Gambling-Site",
          "https://github.com/ModDota/find-steam-app",
          "https://github.com/mprey/csgocact.us",
          "https://github.com/nezu-cc/ServerCrasher",
          "https://github.com/odota/testfiles",
          "https://github.com/odota/underlordsconstants",
          "https://github.com/SnaBe/node-steam-market-fetcher",
          "https://github.com/SteamDatabase/.github",
          "https://github.com/wolfcon/RIP-HLTV-BET",
          "https://github.com/alliedmodders/blaster.net",
          "https://github.com/catears124/CS2-Price-API",
          "https://github.com/ialakey/caseforge",
          "https://github.com/Ilusion9/csgo-fix-mapchange-crash-sm",
          "https://github.com/ismail0234/Benson-Map-Crash-Fixer",
          "https://github.com/jaxwilko/steam-market-api",
          "https://github.com/JustArchiNET/ArchiTag",
          "https://github.com/ModDota/DotaUI",
          "https://github.com/node-steam/market-pricing",
          "https://github.com/odota/media",
          "https://github.com/SergeyIvanovDevelop/Crypto-Steam-Platform",
          "https://github.com/Aareksio/csgodouble-floatchecker",
          "https://github.com/chinm4/CSGOdrop",
          "https://github.com/Cruze03/CSGO-Case-Opening-Prank",
          "https://github.com/Dhruva-Kapadia/CSGOTrollGG",
          "https://github.com/ErhanCSGO/CSGOPolygon-prediction",
          "https://github.com/Ev-Hoang/Bedrock-Chest-Case-Opening",
          "https://github.com/jmjp/csgo-roulette",
          "https://github.com/JustArchiNET/ArchiCrowdin",
          "https://github.com/LeonSK/WearMarketInspector",
          "https://github.com/maximgeerinck/csgo-gamble",
          "https://github.com/ModDota/BugTracker",
          "https://github.com/plwp/mma-betting",
          "https://github.com/Southsideswag16/Csgo-Gambling-Site",
          "https://github.com/tacyarg/csgofiesta-frontend-react",
          "https://github.com/Velorasse/Mutah-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-csmoney-csgoskins",
          "https://github.com/alliedmodders/am-github-artifact-webhook",
          "https://github.com/charamza/roulette",
          "https://github.com/Cruze03/CSGO-PugSetup-RoundRestore",
          "https://github.com/csgorol/CSGO-ROLL-Crash-Predictor",
          "https://github.com/FoxSerito/FOXWORLD_plugin_DoubleJump_CSGO",
          "https://github.com/hkehayovmoonbiz/CS2-Casino-Full-Source-Code",
          "https://github.com/JustZakary/steamstoreapi",
          "https://github.com/jzimr/steam-market-api",
          "https://github.com/Momohime/CSGO.Network-Jackpot-Coinflip",
          "https://github.com/nnjjswat/moneybot",
          "https://github.com/odota/carry",
          "https://github.com/odota/PublicMatchDataBot",
          "https://github.com/Orillio/CSGOBet.com",
          "https://github.com/ripexz/csgo-bet-alert",
          "https://github.com/rrpvm/lumen_sense-beta-deprecated-",
          "https://github.com/Ruthless222/csgoscore",
          "https://github.com/tfburns/CSGO-cases-PL",
          "https://github.com/TomDra/CSGO-Case-Data-Analysis",
          "https://github.com/ValvePython/dota2-wrappers",
          "https://github.com/ValvePython/teamfortress2-closed-captions",
          "https://github.com/VistaNetGTX/Cstrike.bet-",
          "https://github.com/wafflas/csgo-case-opening-simulator",
          "https://github.com/Admiral-Enigma/Le_Coinflip",
          "https://github.com/adryeljuliao/roulette-csgo",
          "https://github.com/AndreuTheG/csgo-coinflip-web",
          "https://github.com/asmilen/csgoDouble",
          "https://github.com/b1naryth1ef/csgofort",
          "https://github.com/Baterka/PrivateSteamBettingWebsite2024",
          "https://github.com/blackcaer/SteamTradeHandler",
          "https://github.com/BTheCoderr/theRounders",
          "https://github.com/CallumHemsley/KazeBot",
          "https://github.com/chrisjpm/CSGOJackpotTemplate",
          "https://github.com/colinsenner/valve-bug-bounty",
          "https://github.com/coryypeters/nrl-odds-intelligence-pipeline",
          "https://github.com/deissh/dev-csgoduo",
          "https://github.com/dom1torii/even-better-font-manager",
          "https://github.com/DONnicov/CSGO-crash-black-screen-",
          "https://github.com/DoubleBoters/CsgoDouble",
          "https://github.com/downarowiczd/DoubleBot",
          "https://github.com/ErayBahar/steammarketscraper",
          "https://github.com/fairydarkness/SteamwebmailAPI",
          "https://github.com/FAQU2/CSGO-Coinflip-MyJailShop",
          "https://github.com/FlamesONE/csgo-case-opening",
          "https://github.com/FunnyRain/csgorun-crash-watch",
          "https://github.com/geohdgio/Venatus-Autenticator",
          "https://github.com/hakanstarlord/steam-bot",
          "https://github.com/HvH-gg/CSGO-Item-CrashFix",
          "https://github.com/HvH-gg/CSGO-NetMsg-CrashFix",
          "https://github.com/isybycnsmam/SteamLibrary",
          "https://github.com/ItsTangerine/SteamApis.Net",
          "https://github.com/JustArchiNET/JustArchi.net",
          "https://github.com/kiri-osint/CS2-Info-Hub-Bot",
          "https://github.com/Koshkaj/monte",
          "https://github.com/madsab/CaseOpening",
          "https://github.com/man90es/steamcardexchange-api",
          "https://github.com/MattPua/steam-unofficial-docs",
          "https://github.com/Metallist1/Portfolio.CsgoWinGambleProject",
          "https://github.com/mikebobadilla/csgo-jackpot",
          "https://github.com/mikebobadilla/meteor-csgojackpot",
          "https://github.com/ModDota/D2VDump",
          "https://github.com/ModDota/DotaTracking",
          "https://github.com/ModDota/eslint-config",
          "https://github.com/mr-codinglv/Casino-script",
          "https://github.com/MrKeelik/MrKeel",
          "https://github.com/noahlatzel/CSGORollHelper",
          "https://github.com/oddsgpt/oddsgpt-market-intelligence",
          "https://github.com/oEXU/csgo-server-crasher",
          "https://github.com/PrdTTony/CSGO-Roulette",
          "https://github.com/r-adamski/csgo-jackpot",
          "https://github.com/Sahotallo/Turan-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-Skinbaron-hellcase",
          "https://github.com/samuelcsouza/steam-marketplace-api",
          "https://github.com/SKINSTRACK/CS2-Price-API",
          "https://github.com/snmtriet/CSGO-Casino-Full-Source-Code",
          "https://github.com/SteamRE/homebrew-tools",
          "https://github.com/SteamRE/opensteamworks.org",
          "https://github.com/TheQuack45/CsgoCaseOpenProgram",
          "https://github.com/TLClassless/StratRouletteCSGO",
          "https://github.com/tomasoom/csgoCaseOpening",
          "https://github.com/vitaliy-evsyukov/steamgifts-autobet-bookmarklet",
          "https://github.com/XpravdaX/RouletteCSGO",
          "https://github.com/YuiKasumii/steam_api_unofficial",
          "https://github.com/Zexuz/Steam-Betting",
          "https://github.com/ANK-RULZZ/steam-jackpot-site",
          "https://github.com/asmilen/CsgoDoubleVS",
          "https://github.com/CORNOODOSADAS/CSGOWeed",
          "https://github.com/CSGOApple/csgoapple",
          "https://github.com/CSGOFAST/csgofast-api",
          "https://github.com/Donakall/csgoDoublebot",
          "https://github.com/fedor-selivanov/csgo-fast-roulette",
          "https://github.com/foldageros/csgod",
          "https://github.com/gmod-gambling/gmod-gambling",
          "https://github.com/ierome/CSGOBoss-BackEnd",
          "https://github.com/jamienp1/CSGODOUBLE-BOT-AUTO",
          "https://github.com/JEYONER/CSGOTOXIC",
          "https://github.com/kalrish/csgo-jackpot",
          "https://github.com/krys12345/roulettee",
          "https://github.com/LilDuggiMuffi/CSGODouble-Working-Bot",
          "https://github.com/LyricLy/Steam2Proton",
          "https://github.com/M0NsTeR77/csgo-roulette",
          "https://github.com/ozanhalis/Hi",
          "https://github.com/scoobertus/CSGO-DoubleBot",
          "https://github.com/Tradeal/CSGO-Jackpot-Bot",
          "https://github.com/ValvePython/artifact",
          "https://github.com/Vampire/CSGO-Roulette-Bot",
          "https://github.com/vdemans/csgo-roulette",
          "https://github.com/VocoreVideo/CSGODungeon-",
          "https://github.com/wayz-dev/csgofloat",
          "https://phishdestroy.io/steam_dossier/output_steam_network/raw_data.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/enforcement-source-manifest.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/pl/steam_enforcement_evidence.content.json",
      "export_json_sha256": "18137b5c54259b62025b46ffbc5b8796ff836947b3180050d18afb13176ce11f"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "pl/steam_evidence_archive.html",
      "language": "pl",
      "title": "Zapoznaj się z źródłami — Raport „Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/pl/steam_evidence_archive",
      "source_html_sha256": "32b17cbb0936e190261e3ed8eb9bb33e4a4b5c9de82697d709262ef3c23af747",
      "exported_at": "2026-09-29T00:19:12.548Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "steam_evidence_archive.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/pl/steam_evidence_archive.pdf?v=print-20260929-v5",
        "sha256": "304d1e9a4730523f94845b2e91043f2e725e649ef78b344e8b6968cd4f80bfb5",
        "bytes": 65112,
        "pages": 4
      },
      "integrity": {
        "signed_object": "steam_evidence_archive.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "steam_evidence_archive.content.json.asc",
        "digest_file": "steam_evidence_archive.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify steam_evidence_archive.content.json.asc steam_evidence_archive.content.json",
          "sha256sum -c steam_evidence_archive.content.json.sha256"
        ]
      },
      "content": {
        "text": "MATERIAŁY ŚLEDCZE / GROMADZENIE ŹRÓDEŁ 002\nSteam Archiwum dowodów — Dokumenty pochodzące z serwisu „16,319”\n\nKażde roszczenie. Powrót do źródła.\n\nCO WYKAZUJE TA CZĘŚĆ\n\nTo archiwum kryminalistyczne indeksuje 16,319 dokumenty źródłowe — obejmujące dokumentację społeczności programistów Valve, publiczne zgłoszenia na stronie GitHub, zweryfikowane skargi na platformie Trustpilot oraz zarchiwizowane zgłoszenia z forów — wraz z skrótami kryptograficznymi i dziennikami pochodzenia. Stanowi ono podlegającą weryfikacji bazę dowodową, wykazującą powtarzające się luki w zabezpieczeniach platformy, nieudokumentowane wycofanie funkcji API oraz uporczywe skargi konsumentów dotyczące przejętych kont.\n\n← Powrót do podsumowania dla kadry kierowniczej\n\nZnajdź wpis, na którym opiera się zgłoszenie. Filtruj według źródła, otwórz pełny tekst i przejdź do oryginalnego linku. Wiersze źródeł mogą się pokrywać; wpis nie oznacza zweryfikowanego zdarzenia.\n\nPowrót do śledztwa ↗\n354TRUSTPILOT / WIERSZE ŹRÓDŁOWE\n208REDDIT / WIERSZE ŹRÓDŁOWE\n705GITHUB / WIERSZE KODU ŹRÓDŁOWEGO\n15,302MASTER CSV / WIERSZE ŹRÓDŁOWE\n16,319 DANE — PODZIAŁ WEDŁUG TYPU PLATFORMY\n\nPochodzenie kategorii w Wikipedii (wpisy w 7,620 · 46.7%): Dane pozyskano ze strony Valve Developer Community (developer.valvesoftware.com), dokumentacji SteamDB/FAQ oraz wiki społeczności graczy (Liquipedia CS/Dota i Fandom Steam) za pomocą automatycznych migawek WARC oraz punktów końcowych MediaWiki API w okresie od sierpnia 2024 do września 2026.. Wszystkie wpisy 7,620 zostały w pełni zintegrowane z głównym eksportem CSV (TOTAL_VALVE_SCANDALS_MASTER_DB.csv).\n\nWiki\n7,620\nReddit\n5,635\nGitHub\n2,395\nTrustpilot\n393\nInternet\n276\n9,116 w bazie danych „16,319” (55.8%) znajdują się odniesienia do stron Steam / Valve\n\nTo archiwum z funkcją wyszukiwania zostało stworzone w oparciu o 2026-09-17 z wymienionych powyżej eksportów źródłowych. Osobny eksport danych podstawowych „40,448-”, wykorzystywany w innych częściach dokumentacji, ma inny zakres. Zobacz utwórz manifest w odniesieniu do statystyk tego archiwum; zapisy mogą się pokrywać i nie odzwierciedlają pojedynczych zdarzeń.\n\nPLATFORMA ŹRÓDŁOWA\nZBIÓR ŹRÓDEŁ\nSteam / Valve wzmianki\nPorównanie tekstu lub repozytorium „Valve”Brakujący / usunięty tekst\n16,569 wiersze źródłowe\n16,319 odrębne rekordy\n249 zduplikowane wiersze zostały połączone\n1 wykluczony wiersz\nZobacz oryginalne pliki ↘\n★TRUSTPILOT2015-10-16#1RATING 1/5\n\nSteam is the biggest PC gaming platform without a doubt. A power which could be abused but Steam for the most part doesn't. Overall a definite download for any moden digital age PC gamer. It mu... See more\n\nMA · 7 source copies\n★TRUSTPILOT2021-06-18#2RATING 1/5\n\nThey scam people for money, dont believe me? Read this Source: Steam Subscribers/User Agreement NO GUARANTEES TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, NEITHER VALVE NOR ITS AFFILIA... See more\n\nWF · 7 source copies\n★TRUSTPILOT2016-10-28#3RATING 1/5\n\nSupport on site is terrible. Refunds not happend yet, despite games not working. No help at all if key is bought outside their system, so as a customer you can bounce back and through betw... See more\n\nPE · 7 source copies\n★TRUSTPILOT2021-09-27#4RATING 1/5\n\nThey are an amazing company!! My boyfriend paid for and downloaded a game without realizing it wasn’t the version he wanted. When he reached out, they gave him a full refund and responded in the same... See more\n\nVH · 7 source copies\n★TRUSTPILOT2026-07-20#5RATING 1/5\n\nI’ve used Steam for years, but lately, their sales have really lost their edge. I was hoping to score some solid discounts, but many games still feel overpriced, even during sales. Plus, the support response times can be frustratingly slow when issues arise.\n\nCR\n★TRUSTPILOT2025-12-10#6RATING 1/5\n\nI new here , but all my firends had great experience with this platform . They can make money\n\nZeinab Nematollahi\n★TRUSTPILOT2025-11-18#7RATING 1/5TEXT UNAVAILABLE\n\nNo text was included in the source record.\n\nEM\n★TRUSTPILOT2025-10-21#8RATING 1/5\n\nusing steam for over a decade and i have no words how good the platform is. some friends recommended it to me back in 2015 when we wanted to play csgo together and since then im loggin on it on a daily basis to check new games\n\nTrustpilot\n★TRUSTPILOT2025-05-09#9RATING 1/5\n\nSupport are never able to help you and only able to redicrect you to public linkBreaking there own TOSNot able to provider a refundNot able to provide a safe place for gamingBase on the game you play you can get scam.\n\nSym Link · 7 source copies\n★TRUSTPILOT2025-05-09#10RATING 1/5TEXT UNAVAILABLE\n\nNo text was included in the source record.\n\nHearnius\n★TRUSTPILOT2024-12-30#11RATING 1/5\n\nThis company allowed a single phishing scammer 76561199443342045 in 100's of its user community chat rooms \"Steam Chat\" the whole week of Winter Sales, 12-23-2024 - 2025 to spam spaceintrader a scam phishing website.Don't support Valve & Steam that support sca…\n\nFR · 7 source copies\n★TRUSTPILOT2024-11-15#12RATING 1/5\n\nVery realiable! Ive never had an issue over the 11 years ive had steam.\n\nJM\nKompilacja i pliki źródłowe\n\nW niniejszym archiwum połączono zduplikowane wiersze z witryny 249 oraz wykluczono jeden wiersz z danych wejściowych z witryny 16,569, pozostawiając 16,319 unikalnych rekordów. Dany rekord może opisywać zdarzenie, które zostało już uwzględnione w innym rekordzie. Wyszukiwanie obejmuje tytuły, autorów, nazwy źródeł oraz wyświetlane fragmenty; pełna treść zapisanych tekstów otwiera się wraz z każdym rekordem.\n\nPobierz cztery pliki eksportowe z kodem źródłowym ↓Liczba plików i skróty SHA-256 ↗Oryginalny manifest kompilacji ↗\n\nPakiet zawiera odzyskane pliki eksportowe, których liczba odpowiada liczbie wierszy w kompilacji, oraz trzy zarejestrowane ścieżki plików JSON. W pierwotnej kompilacji nie zarejestrowano skrótów danych wejściowych ani głównej ścieżki pliku CSV; w załączonym manifeście udokumentowano odzyskane pliki oraz porównanie z opublikowanym indeksem.\n\nTrustpilot · steam_support_reviews.json354 wiersze · eksport do formatu JSON\nReddit · reddit_censored_forensics.json208 wiersze · eksport do formatu JSON\nGitHub · valve_ignored_bugs.json705 wiersze · eksport do formatu JSON; nazwa pliku to etykieta kolektora\nMaster · TOTAL_VALVE_SCANDALS_MASTER_DB.csv15,302 wiersze · eksport do pliku CSV wykorzystany do porównania\nSprawy sądowe · UNSEALED_EXHIBITS_AND_AML_DOSSIER.mdWolfire przeciwko „Valve” – ujawnione e-maile, zeznania Gabe’a Newella, październikowe wyznanie dotyczące AML w grze „2019”\nNajważniejsze fakty · FACTS_AND_CITATIONS_DATABASE.md1,638 poszczególne, zweryfikowane odniesienia dotyczące kwestii antymonopolowych i bezpieczeństwa na stronie 35\nArchiwum pomocy technicznej · support_canned_refusals.html1,505 historia biletów · 137 – zarchiwizowane zrzuty ekranu · Wyszukiwanie na żywo\nPola rekordów, brakujące teksty i nakładające się eksporty\n\nDaty, oceny, kategorie i statusy wpisów są zgodne z danymi ze źródeł eksportu. Brakujący adres URL pozostaje nieobecny. Oznaczenia „[usunięto]” lub „[skasowano]” nie wskazują, kto usunął wpis ani dlaczego. Filtr Steam / Valve opiera się na dopasowaniu tekstowym, a nie na ocenie trafności.\n\nOpcja „Eksportuj dopasowania” pobiera wpisy indeksu wraz z fragmentami; opcja „Pobierz rekord” zawiera pełny zapisany tekst. Osobna 40,448-główny wiersz pliku CSV oraz 1,690-wiersz GitHub CSV W tej wersji liczy się raczej ogólny wolumen eksportu, a nie liczba źródeł.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam Archiwum dowodów — Dokumenty pochodzące z serwisu „16,319”"
          },
          {
            "level": 2,
            "id": null,
            "text": "PLATFORMA ŹRÓDŁOWA"
          },
          {
            "level": 2,
            "id": null,
            "text": "Kompilacja i pliki źródłowe"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/pl/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/pl/",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/TOTAL_VALVE_SCANDALS_MASTER_DB.csv",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive_manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive-inputs.zip",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive-inputs-manifest.json",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/unsealed_legal_and_aml/UNSEALED_EXHIBITS_AND_AML_DOSSIER.md",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/forensic_facts_1000/FACTS_AND_CITATIONS_DATABASE.md",
          "https://phishdestroy.io/steam_dossier/pl/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/github_valve_unpatched_bugs.csv"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/pl/steam_evidence_archive.content.json",
      "export_json_sha256": "064ef71a97989403678894d8f9915dc2b73eb7965cb9c3d4d1f6899d02fd408b"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "pl/support_canned_refusals.html",
      "language": "pl",
      "title": "Steam Archiwum odmów pomocy i szablonowych odpowiedzi — Dokumentacja dotycząca „Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/pl/support_canned_refusals",
      "source_html_sha256": "43e32048603111fdd8e0280ab4f1da49c4c233995284c6b129add870661d8fb0",
      "exported_at": "2026-09-29T00:19:12.367Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "support_canned_refusals.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/pl/support_canned_refusals.pdf?v=print-20260929-v5",
        "sha256": "54164ee6ee2e8df1574c9daaa366c671b052ce261716e3c7cccfb66d96e4b43e",
        "bytes": 62513,
        "pages": 2
      },
      "integrity": {
        "signed_object": "support_canned_refusals.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "support_canned_refusals.content.json.asc",
        "digest_file": "support_canned_refusals.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify support_canned_refusals.content.json.asc support_canned_refusals.content.json",
          "sha256sum -c support_canned_refusals.content.json.sha256"
        ]
      },
      "content": {
        "text": "CO WYKAZUJE TA CZĘŚĆ\n\nW niniejszym repozytorium zgromadzono zrzuty ekranu z serwisu 137 oraz zweryfikowane odwołania ofiar z serwisu 1,505, szczegółowo opisujące sposób automatycznej obsługi zgłoszeń do pomocy technicznej przez serwis Valve. Dowodzi to, że w przypadku przejęcia kontroli nad kontami poprzez przekierowanie OpenID lub nieautoryzowane wygenerowanie klucza API, dział pomocy technicznej Steam systematycznie stosuje standardowe, gotowe wzory odmowy bez przeprowadzania analizy technicznej. Kategorycznie odmawiając przywrócenia przedmiotów lub ujawnienia ścieżki audytu, platforma przenosi pełną odpowiedzialność za strukturalne wady systemu uwierzytelniania na właścicieli przejętych kont.\n\nWszystkie zrzuty ekranu są materiałami pochodzącymi od stron trzecich. Prawa autorskie i treść należą do odpowiednich autorów i platform (użytkowników serwisu Reddit, autorów ze społeczności Steam, recenzentów serwisu Trustpilot, serwisu X oraz autorów filmów na YouTube). Zostały one zamieszczone wyłącznie w celu identyfikacji i przedstawienia informacji leżących w interesie publicznym; nie rości się sobie żadnych praw własności. Każdy zrzut ekranu zawiera link do swojego pierwotnego źródła.\n\nFigures reported on the source page\nMeasure\tReported value\tScope\nUdokumentowane zapisy\t1505\tZweryfikowane odwołania ofiar i wątki dotyczące mandatów\nZachowane zrzuty ekranu\t137\tLokalnie zapisane zrzuty ekranu biletów w wysokiej rozdzielczości\nWspółczynnik odtworzenia\t0.0%\tUchylono wyroki w sprawie przejęć transakcji typu „API”\nPowielanie szablonów\t100%\tPonowne wykorzystanie dosłownego scenariusza przez różnych pracowników (Ilya, Roger, Maverick)\nDowody kryminalistyczne: trzy podstawowe filary odmowy udzielenia wsparcia\nFUNDAMENT 01 · REKRUTACJAZałącznik R –014\nWyznanie Rogera: Potwierdzono atak typu „man-in-the-middle” na konferencję API\n\nW odpowiedzi na zgłoszenie nr1cp582i, Steam pracownik pomocy technicznej o pseudonimie „Roger” przyznaje na piśmie, że osoby atakujące anulują legalne transakcje za pośrednictwem strony API i zastępują je klonowanymi botami w ciągu milisekund, ale odmawia przywrócenia przedmiotów i radzi ofierze, by zwróciła się do „lokalnego technika komputerowego”.\n\nSprawdź pisemne potwierdzenie przyjęcia ↗\nFILAR 02 · ESKALACJAZałącznik R –012\n7-Handel jednodniowy – utrzymywanie pozycji bez podejmowania działań\n\nJedna z ofiar podała identyfikatory SteamID64 kont hakera w trakcie trwania okresu wstrzymania handlu w ramach akcji „7-”. Pracownicy pomocy technicznej „Artem” i „Ilya” odmówili zablokowania skradzionych przedmiotów, powołując się na ich niedostępność, i zamknęli zgłoszenie, wysyłając automatyczną odpowiedź szablonową.\n\nSprawdź wykaz ocen wielu pracowników ↗\nFUNDAMENT 03 · POLITYKAZałącznik R –002\nNiedobór rynkowy a prawa własności\n\nW oficjalnej polityce Valve dotyczącej przywracania przedmiotów wyraźnie stwierdzono, że przedmioty nie są przywracane, ponieważ ich przywrócenie „zmniejszyłoby ich rzadkość i spowodowałoby inflację w gospodarce, obniżając wartość przedmiotów na rynku społecznościowym”.\n\nZrzut ekranu z zasadami kontroli ↗\nPochodzenie historyczne · 22 od marca 2018 do 2026\nZałącznik H –003 · 8-– powierzchnia ataku bez zainstalowanych poprawek w ciągu roku\nNajwcześniejszy odnotowany przypadek substytucji towarowej (22, marzec 2018)\n\nDokładnie tydzień przed tym, jak serwis Valve wprowadził kontrowersyjny okres karencji w handlu przedmiotami z gry „Counter-Strike” (7-), społeczność graczy odkryła pierwsze rzeczywiste przypadki Steam Luka typu „API” w usłudze Web oraz przekierowanie ruchu. Atakujący przejęli sesje internetowe w celu wygenerowania nieautoryzowanego klucza „API” pod adresem steamcommunity.com/dev/apikey bez mobilnego potwierdzenia typu „2” ze strony FA, co umożliwia botom anulowanie i zamianę transakcji w czasie rzeczywistym.\n\nOstrzeżenie w ramach kampanii społecznej „March2018”: „Oszuści potrafią automatycznie wykryć tę ofertę wymiany i odrzucą ją na Twoim koncie, ponieważ posiadają Twój klucz Steam API. Bot oszukańczy wyśle Ci teraz ofertę wymiany tych samych skórek… a Ty nawet nie zauważysz różnicy!”\nSzlak śladów historycznych\n22 mar2018: Pierwsza udokumentowana wymiana silnika typu „API”\n2019: Wsparcie standaryzuje proces blokowania „złośliwego oprogramowania”\n2020: Zabezpieczono skrypt „Zamknij zgłoszenie pomocy”\n2022–2026: Automatyzacja ataków phishingowych z wykorzystaniem kodów BitB i QR\nOtwórz oryginalny wątek na Reddicie „2018” ↗\nPrimary sources\n\n137 gallery cards refer to 78 distinct primary URLs. Images and repeated exhibit captions are omitted from this reading edition.\n\nFull visual archive and original captures",
        "headings": [
          {
            "level": 2,
            "id": null,
            "text": "Figures reported on the source page"
          },
          {
            "level": 2,
            "id": null,
            "text": "Dowody kryminalistyczne: trzy podstawowe filary odmowy udzielenia wsparcia"
          },
          {
            "level": 3,
            "id": null,
            "text": "Wyznanie Rogera: Potwierdzono atak typu „man-in-the-middle” na konferencję API"
          },
          {
            "level": 3,
            "id": null,
            "text": "7-Handel jednodniowy – utrzymywanie pozycji bez podejmowania działań"
          },
          {
            "level": 3,
            "id": null,
            "text": "Niedobór rynkowy a prawa własności"
          },
          {
            "level": 3,
            "id": null,
            "text": "Najwcześniejszy odnotowany przypadek substytucji towarowej (22, marzec 2018)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Primary sources"
          }
        ],
        "links": [
          "https://www.reddit.com/r/csgo/comments/1cp582i/i_got_api_scammed_what_do_i_do_now/",
          "https://www.reddit.com/r/DotA2/comments/1e5ovy4/my_account_was_hacked_and_steam_support_refuse/",
          "https://www.reddit.com/r/Steam/comments/3b2abd/steam_will_no_longer_restore_scammed_items_item/",
          "https://www.reddit.com/r/GlobalOffensiveTrade/comments/863tk1/psa_urgent_huge_scam_happening_read_here_how_to",
          "https://phishdestroy.io/steam_dossier/pl/support_canned_refusals#gallery-grid"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/pl/support_canned_refusals.content.json",
      "export_json_sha256": "db6f5c725eb37d7b25828559bc18de8170f59fad23e36aab35ac3af62b58ddca"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "pl/valve_scandals_registry.html",
      "language": "pl",
      "title": "Valve Rejestr skandali — Dokumentacja dotycząca „Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/pl/valve_scandals_registry",
      "source_html_sha256": "653633089f52628ea0975964cfca99c9090e1c8539b8dc5739aa9ffdbbdf3554",
      "exported_at": "2026-09-29T00:19:15.239Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "valve_scandals_registry.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/pl/valve_scandals_registry.pdf?v=print-20260929-v5",
        "sha256": "4a3b8fe19b16f6c6c1a6d7c4d57f3a845f93806d277606eec516f4fd66f83dae",
        "bytes": 66167,
        "pages": 6
      },
      "integrity": {
        "signed_object": "valve_scandals_registry.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "valve_scandals_registry.content.json.asc",
        "digest_file": "valve_scandals_registry.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify valve_scandals_registry.content.json.asc valve_scandals_registry.content.json",
          "sha256sum -c valve_scandals_registry.content.json.sha256"
        ]
      },
      "content": {
        "text": "Archiwum skandali Master\nValve Główny rejestr skandali — 160 Zgłoszone przypadki\nDANE ŹRÓDŁOWE (W FORMACIE RAW): 11,768\n\nZgłoszono. Źródło podane. Sprawa nadal otwarta.\n\nCO WYKAZUJE TA CZĘŚĆ\n\nTen główny rejestr gromadzi 160 niezależnie zweryfikowane dane źródłowe opisujące trwałe wady platformy, usunięte zgłoszenia społeczności oraz nierozwiązane przypadki zaniedbań w obsłudze klienta w całym ekosystemie Valve. Obejmując zweryfikowane zgłoszenia sporów na Trustpilot, zarchiwizowane zgłoszenia problemów związanych z bezpieczeństwem na GitHub oraz postępowania organów regulacyjnych, rejestr ten wskazuje na powtarzające się, systemowe awarie w zakresie odzyskiwania kont i rozstrzygania sporów z klientami.\n\n← Powrót do podsumowania dla kadry kierowniczej\n\n160 zgromadzone dane: działania wsparcia ocenione przez osoby, które z nich skorzystały, wątki, które przestały być widoczne, zgłoszone i pozostawione bez rozpatrzenia usterki platformy oraz incydenty, za które serwis Valve musiał już odpowiedzieć. Żadna z tych informacji nie jest naszą interpretacją — każdy wiersz zawiera odniesienie do oryginalnego źródła. Otwórz jeden z nich i przeczytaj sam.\n\nŹródła danych\n11,768\nWe wszystkich kategoriach\nWady platformy\n3,372\nUwady platformy zgłoszone przez społeczność\nWątki ocenzurowane\n109\nWpisy z serwisu Reddit usunięte przez moderatora\nSkargi dotyczące pomocy technicznej\n471\nZweryfikowane skargi na platformie Trustpilot\nMożliwość egzekwowania\nBlokowanie domen hostów uwierzytelniających\n\nBlokowanie hostów uwierzytelniających OpenID na poziomie domeny jest technicznie łatwe do wdrożenia: gdy dany zasób zostanie wykluczony z przekierowania logowania Steam, domeny stron trzecich pełniące rolę serwerów proxy uwierzytelniających dla tego samego zasobu mogą być filtrowane na podstawie tego samego zestawu reguł. Szczegółowe omówienie wykonalności wdrożenia znajduje się w głównym dokumencie.\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\nZobacz informacje na temat możliwości egzekwowania przepisów w dokumentacji →\nKategoria: Skargi kierowane do działu pomocy technicznej Trustpilot (przefiltrowane zgłoszenia o negatywnej ocenie)176 pasujące rekordy źródłowe · duplikaty ukryte\nConsumer Complaint2026-07-20\nAuthor: C***\n\nI’ve used Steam for years, but lately, their sales have really lost their edge. I was hoping to score some solid discounts, but many games still feel overpriced, even during sales. Plus, the support response times can be frustratingly slow when issues arise.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2026-07-20\nConsumer Complaint2025-05-09\nAuthor: S*** L***\n\nSupport are never able to help you and only able to redicrect you to public linkBreaking there own TOSNot able to provider a refundNot able to provide a safe place for gamingBase on the game you play you can get scam.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2025-05-09\nConsumer Complaint2024-12-30\nAuthor: F***\n\nThis company allowed a single phishing scammer 7656…2045 in 100's of its user community chat rooms \"Steam Chat\" the whole week of Winter Sales, 12-23-2024 - 2025 to spam spaceintrader a scam phishing website.Don't support Valve & Steam that support scams. Don't give your log in credentials to account hijacking scammers. This company also allows engagements of commercial advertising / spam for gambling in violation of its own Rules and Guidelines / Online Conduct. 7656…5023 proof - groups/deskinsfans key drop advertising, thanks TannerfromKD and Valve!*\"The Consumer Review Fairness Act (CRFA) protects people’s ability to share their honest opinions about a business’s products, services, or conduct, in any forum, including social media. The law protects a broad variety of honest consumer assessments, including online reviews, social media posts, uploaded photos, videos, etc. And it doesn’t just cover product reviews. It also applies to consumer evaluations of a company\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2024-12-30\nConsumer Complaint2024-07-31\nAuthor: A***\n\nhorrible company.randomly you get \"This account may have been accessed by someone else.\"this happened to me 3 times.the 3rd time they wanted a cd key.a spent useless cd key that nobody has any reason to keep laying around.i gave them the paypal bill for my first purchase back in 2015.i gave them a bill for my first phone number ever on the account.i still got the same email attached to the account.this company is literally a scam. nothing but a scam.they randomly claim you been accessed somewhere else and then require you to give them information no reasonable person would ever have, if not your done and have to rebuy everything.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2024-07-31\nConsumer Complaint2023-12-09\nAuthor: K***\n\nHad 288 euros in steam wallet, someone hacked my account even with two step verification, write a steam support for help but only answer was if something is spent in community market they can’t help.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2023-12-09\nConsumer Complaint2023-09-26\nAuthor: J***\n\nI was banned for saying \"Who let grandma on the PC\"and another for simply calling someone ignorant.Power tripping mods, devs who don't care, steam doesn't care. Yet allows racism/trolling/etc Fk steam, its a joke now.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2023-09-26\nConsumer Complaint2022-08-31\nAuthor: Anonymous\n\nSteam community is plain bad for a various reasons:1. Steam forums are a big mess, for example they allow users to post in any language and as result you get jumbled mess with posts in foreign languages together with English language posts. For example, If you check CS GO forums, you'll see half of posts are in Russian and half in English. I don't understand why such a big and international company would leave their forums so unorganized like that. All other normal companies have English only language allowed which is an international language and sometimes subforums for other languages like German, French and etc... so if French people want to post in French they go specifically in that sub-forum. But no, Steam doesn't care about this. Their forums is a one big mess.2. Moderation is biased and joke. I don't understand why such a big company like Steam can't afford to hire people for moderation and pay them. Instead they just recruit random people for moderation who do it for free and\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2022-08-31\nConsumer Complaint2022-05-28\nAuthor: J***\n\nThe login code never arrives. I hate Steam.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2022-05-28\nConsumer Complaint2021-11-08\nAuthor: N***\n\nThe service is terrible, I only signed up because I really like the game I wanted, but the rest is terrible, I hope to get something better soon.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-11-08\nConsumer Complaint2021-06-18\nAuthor: W***\n\nThey scam people for money, dont believe me? Read thisSource: Steam Subscribers/User Agreement NO GUARANTEESTO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, NEITHER VALVE NOR ITS AFFILIATES GUARANTEE CONTINUOUS, ERROR-FREE, VIRUS-FREE OR SECURE OPERATION AND ACCESS TO STEAM, THE CONTENT AND SERVICES, YOUR ACCOUNT AND/OR YOUR SUBSCRIPTION(S) OR ANY INFORMATION AVAILABLE IN CONNECTION THEREWITH.In short: You got a virus or your data leaked because of our software? Whoopsies we dont care, that isnt even legal or the last of their scammy stuff...\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-06-18\nConsumer Complaint2021-05-14\nAuthor: B***\n\nThe support is one of the worst I've ever seen.Useless support team.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-05-14\nConsumer Complaint2020-04-02\nAuthor: J***\n\nSteamcommunity has 15% fees, 15!!!!\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2020-04-02\nConsumer Complaint2020-03-27\nAuthor: H***\n\nWhat can I say? the support is one of the worst I've ever seen maybe the FUNCOM is much worse. If you tell the true on the steam forum you just got a BAN even if what you said did not violated the rules of the forum.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2020-03-27\nConsumer Complaint2018-03-16\nAuthor: B***\n\ndon't sign up will stick on your computer will kill your pc power you can't remove it from your pc even you deleted it will stay woking in the system\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2018-03-16\nConsumer Complaint2016-12-27\nAuthor: J***\n\nIn bloddy hate their page it's tiresome, it's in no way intuitive. I tried reaching out for support, but that is a maze.I'm simply trying to log in and redeem a key of a product I already bought, their search function is a joke. I f*u*c*k*i*n*g hate them. The layout is not like the how to video from the dealer, this can be done much simpler. I don't frigin care aboutn what other titles you have in store or what genre, I just want to redeem my key and install.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-12-27\nConsumer Complaint2016-10-28\nAuthor: P***\n\nSupport on site is terrible.Refunds not happend yet, despite games not working.No help at all if key is bought outside their system, so as a customer you can bounce back and through between bad support systems?? I wait for some other companies to compete in this market, for this can't be the best we as customers can expect.And do put an email up to find, instead of this stuppid website where you spend so long time trying to find a solution on, instead of a simple mail. Often the problem is not there, or if it's there just saying no help here???I need a response\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-10-28\nConsumer Complaint2016-06-26\nAuthor: V*** W***\n\nUseless support as always!\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-06-26\nConsumer Complaint2014-07-01\nAuthor: J***\n\nexpensive, and support team not willing to cooperate\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2014-07-01\nConsumer Complaint2014-04-15\nAuthor: B***\n\nWhen you pay for a program, you expect it too work. cant not buy or anything and have written to valve. but there is not a being done a damn thing abut it..\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2014-04-15\nConsumer Complaint2026-09-03\nAuthor: M***\n\nWorst platform ever wont give me a refund even though a game is unplayable because of bugs I won't ever be using the crap platform again I hope the platform breaks down for good piece fo crao\n\nTarget Domain: steamcommunity.com / steampowered.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2026-09-03\n\nBrak pasujących wpisów\n\nSpróbuj zmodyfikować aktualne zapytanie lub przejść do innej zakładki kategorii.\n\n1 / 9",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Valve Główny rejestr skandali — 160 Zgłoszone przypadki"
          },
          {
            "level": 2,
            "id": null,
            "text": "Blokowanie domen hostów uwierzytelniających"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: C***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: S*** L***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: F***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: A***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: K***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: Anonymous"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: N***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: W***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: H***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: P***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: V*** W***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: M***"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/pl/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/pl/#proxy-bypass-explainer",
          "https://phishdestroy.io/steam_dossier/pl/#autoban-feasibility-section",
          "https://www.trustpilot.com/review/steamcommunity.com"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/pl/valve_scandals_registry.content.json",
      "export_json_sha256": "1e3a95fb5b9fb311aa41bffe3c4a9e263a1b59f67e4157183a79d8a74dcb4a75"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "pl/output_steam_network/index.html",
      "language": "pl",
      "title": "Architektura, a nie luka: Sieć automatyzacji — Raport „Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/pl/output_steam_network/index",
      "source_html_sha256": "15ab2f8d9add1db6641c95b80b8c44064135e7d6983dc0b2f852e4e5b4941c4f",
      "exported_at": "2026-09-29T00:19:16.366Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__index.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/pl/output_steam_network__index.pdf?v=print-20260929-v5",
        "sha256": "e874c6c656ba1999a7ae7ad3ab13263ea8b8cdc4b0d12f026a8ce0608ce0ada3",
        "bytes": 71025,
        "pages": 3
      },
      "integrity": {
        "signed_object": "output_steam_network__index.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__index.content.json.asc",
        "digest_file": "output_steam_network__index.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__index.content.json.asc output_steam_network__index.content.json",
          "sha256sum -c output_steam_network__index.content.json.sha256"
        ]
      },
      "content": {
        "text": "Załącznik VII · Analiza architektury technicznej\nSteam Architektura sieci — zgodność z protokołami i analiza ekosystemu\n\nAutomatyzacja stanowi podstawę architektury firmy „Valve”. To nie jest luka w zabezpieczeniach.\n\nCO WYKAZUJE TA CZĘŚĆ\n\nModuł ten przedstawia topologię techniczną repozytoriów programistów serwisu 252, profili 3,320 GitHub oraz par współpracowników 4,214, stanowiących podstawę ekosystemu automatyzacji Steam. Wykazuje on, że automatyzacja realizowana przez podmioty zewnętrzne opiera się na oficjalnym protokole Connection Manager serwisu Valve, schematach Protobuf oraz interfejsach API bez zawartości kodu wykorzystującego luki w zabezpieczeniach. Poprzez opracowywanie algorytmicznych tokenów potwierdzających Steam Guard oraz pobieranie minimalnych opłat transakcyjnych w wysokości do 66.7%, Valve pełni rolę celowego architekta i głównego beneficjenta komercyjnego zautomatyzowanych operacji ekosystemu.\n\n← Powrót do podsumowania dla kadry kierowniczej\n\nKiedy serwis „Valve” zwraca się do organów regulacyjnych, podmiotów obsługujących płatności lub ofiar oszustw, przypisuje kradzież skinów i manipulacje rynkowe „nieautoryzowanym atakom stron trzecich” oraz „niekontrolowanej, nielegalnej automatyzacji”. Rzeczywistość techniczna tej sieci repozytoriów 252-wskazuje na coś zupełnie przeciwnego: Każdy framework automatyzacji, bot handlowy i flota do farmowania działa ściśle w ramach oficjalnych definicji protokołów, interfejsów API oraz mechanizmów uwierzytelniania opracowanych, udokumentowanych i komercjalizowanych przez firmę Valve Corporation.\n\nWyniki analizy kryminalistycznej: świadome działania architektoniczne a bezprawne naruszenie\n\nOprogramowanie analizowane w tym module — w tym SteamKit, node-steam-user, ValvePython/steam, oraz ArchiSteamFarm — zawiera zero luk w zabezpieczeniach oprogramowania, zero uszkodzeń pamięci i zero exploitów typu zero-day. Są to przejrzyste, solidne implementacje typu open source zastrzeżonego protokołu klienckiego Connection Manager (CM) firmy Valve, biblioteki Google Protocol Buffers (Protobufs) oraz interfejsów API sieci Web. Firma Valve zaprojektowała te interfejsy API tak, aby obsługiwały logowanie programowe, a serwis Steam Guard umożliwiał stosowanie algorytmicznych tokenów potwierdzających (identity_secret), a także pobiera opłatę za usługę „15%”, której wysokość wzrasta do 66.7% na korzyść Valve w zakresie kart o wysokiej wartości oraz towarów, które są sprzedawane przez zautomatyzowane botnety.\n\nFilar 01 · Wierność protokołowi\nOficjalne schematy Protobuf\n\nBiblioteki automatyzacji nie omijają zabezpieczeń. Serializują one oficjalne komunikaty Protobuf (steammessages_clientserver.proto) przez protokół TCP/WebSockets bezpośrednio do oficjalnych klastrów CM serwisu Valve, dokładnie tak samo jak robi to klient Steam.\n\nPillar 02 · Algorithmic 2FA\nUpoważnienie do handlu programowego\n\nCała warta wiele miliardów dolarów branża handlu skórą opiera się na serwisie Valve IEconService API oraz klucze TOTP do uwierzytelniania mobilnego. Firma Valve celowo zaprojektowała rozwiązanie „Steam Guard”, aby umożliwić potwierdzanie transakcji między maszynami.\n\nFilar 03 · Beneficjent komercyjny\nRuch generowany przez automaty z monetyzacją: maksymalnie66.7% – minimalna opłata\n\nValve reklamuje opłatę w wysokości 15%, ale w przypadku popularnych towarów, którymi handlują zautomatyzowane boty — kart kolekcjonerskich, zestawów i tanich przedmiotów w cenach od $0.03 do $0.05 — minimalna opłata Valve wynosząca dwa centy ($0.01 Steam + $0.01 wydawca) wynosi 50% na rzecz 66.7% na korzyść Valve (2¢ pobrane z karty 3¢, co pozostawia sprzedawcy kwotę 1¢). Plus $5.00 na każde konto ($26.8M tylko w przypadku zeskanowanej floty).\n\nModuł „01” · Dane dotyczące repozytorium i protokołu\nPubliczna infrastruktura dla programistów i repozytoriów\n\nSzczegółowy katalog kryminalistyczny repozytoriów open source 252, stanowiących podstawę automatyzacji serwisu Steam. Przedstawia, w jaki sposób standardowe narzędzia inżynierii oprogramowania implementują opublikowane przez Valve punkty końcowe API bez wykorzystywania luk w zabezpieczeniach.\n\n252Repozytoria\n4,554Linki do ról\nSprawdź dowody w repozytorium →Moduł 02 · Demografia ekosystemów\nWskaźniki dotyczące globalnego ekosystemu inżynieryjnego\n\nPodział geograficzny i instytucjonalny inżynierów oprogramowania z serwisu „3,320”, którzy wnoszą wkład w ekosystem automatyzacji Steam, z uwzględnieniem przynależności do głównych pracodawców z branży technologicznej.\n\n3,320Inżynierowie\n98,902Pary połączeń\nSprawdź wskaźniki ekosystemu →Moduł 03 · Interaktywny wykres wizualny\nInteraktywny schemat protokołu i wykres sieci programistów\n\nKompleksowe, interaktywne wykresy sieciowe oparte na technologii Vis.js, przedstawiające repozytoria, biblioteki protokołów (SteamKit, Steamworks, ASF) oraz powiązania między współtwórcami różnych projektów. Wizualnie ilustrują one spójną, wzajemnie powiązaną architekturę oprogramowania open source, stanowiąącą podstawę ekosystemu automatyzacji serwisu Steam.\n\nInteraktywneVis.js Silnik\nIzolacja klastraWyszukiwanie na żywo\nZero luk w zabezpieczeniachStandardowe interfejsy API\nUruchom interaktywny wykres sieciowy →\nKontekst regulacyjny i prawny (artykuł z serwisu GDPR 25 oraz ochrona konsumentów):\nZgodnie z zasadą „ochrony danych w fazie projektowania i domyślnie” architektura platformy, która umożliwia generowanie kluczy „API” bez powiadomienia, anulowanie transakcji bez uprzedzenia oraz automatyczną likwidację aktywów, stanowi wybór architektoniczny operatora platformy. Kiedy Valve systematycznie odrzuca wnioski konsumentów o zwrot środków, twierdząc, że straty zostały spowodowane przez „zewnętrzne cyberataki”, ukrywa fakt, że wektorem ataku jest właśnie celowo zaprojektowana przez Valve architektura serwisu API.\n\nWIDOK INTERAKTYWNY\n\nPełna interaktywna wizualizacja repozytorium „252-” oraz wykres sieci deweloperów „3,320-” są dostępne pod adresem network.html. Wskaźniki zbiorcze znajdują się na stronie Wskaźniki BI strona.\n\nDokumentacja projektu „Steam” · Archiwum architektury technicznej · Publiczne rejestry źródeł · Wszelkie prawa przekazane ludzkości.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam Architektura sieci — zgodność z protokołami i analiza ekosystemu"
          },
          {
            "level": 3,
            "id": null,
            "text": "Oficjalne schematy Protobuf"
          },
          {
            "level": 3,
            "id": null,
            "text": "Upoważnienie do handlu programowego"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ruch generowany przez automaty z monetyzacją: maksymalnie66.7% – minimalna opłata"
          },
          {
            "level": 2,
            "id": null,
            "text": "Publiczna infrastruktura dla programistów i repozytoriów"
          },
          {
            "level": 2,
            "id": null,
            "text": "Wskaźniki dotyczące globalnego ekosystemu inżynieryjnego"
          },
          {
            "level": 2,
            "id": null,
            "text": "Interaktywny schemat protokołu i wykres sieci programistów"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/pl/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/pl/output_steam_network/valve_ru_farming_isolated.html",
          "https://phishdestroy.io/steam_dossier/pl/output_steam_network/steam_ecosystem_dashboard.html",
          "https://phishdestroy.io/steam_dossier/pl/output_steam_network/network.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/pl/output_steam_network__index.content.json",
      "export_json_sha256": "b4f7ebf00a7e1114cba61c6397fff903f3183ffa1d1d0dfd31142e1567d8420b"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "pl/output_steam_network/network.html",
      "language": "pl",
      "title": "Narzędzie dla programistów i przeglądarka repozytoriów — Dossier „Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/pl/output_steam_network/network",
      "source_html_sha256": "836803898fe4f7398282106f13d960809cf3e7608892c049826e597ca1906f69",
      "exported_at": "2026-09-29T00:19:18.914Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__network.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/pl/output_steam_network__network.pdf?v=print-20260929-v5",
        "sha256": "3074b3b8388901773c0088515d7248f5824371626393cd7a344cebd4e368f587",
        "bytes": 37119,
        "pages": 1
      },
      "integrity": {
        "signed_object": "output_steam_network__network.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__network.content.json.asc",
        "digest_file": "output_steam_network__network.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__network.content.json.asc output_steam_network__network.content.json",
          "sha256sum -c output_steam_network__network.content.json.sha256"
        ]
      },
      "content": {
        "text": "Narzędzie dla programistów i przeglądarka repozytoriów\n\nWyszukaj węzeł. Sprawdź zarejestrowaną relację.\n\nREJESTRY PUBLICZNE / ZBIÓR POWIĄZAŃ\nWyszukiwanie na żywo\nWarstwy filtrów\nŁączna liczba programistów3,320\nŁączna liczba repozycji252\nWYŚWIETLANY WYKRES / PODZBIÓR KOLEKCJI468 WĘZŁY • 1103 KRAWĘDZIE\nWybrany wpis profilu\n\n💡 Kliknij dowolny węzeł na wykresie lub wpisz tekst w polu wyszukiwania, aby sprawdzić zebrane połączenia i ścieżki źródłowe tego węzła.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Narzędzie dla programistów i przeglądarka repozytoriów"
          }
        ],
        "links": []
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/pl/output_steam_network__network.content.json",
      "export_json_sha256": "5ef9f5b89cb686895a30968730c6a3d685faa90f1ed3aaf27190d1c4663121ba"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "pl/output_steam_network/steam_ecosystem_dashboard.html",
      "language": "pl",
      "title": "Zebrana sieć w liczbach — Raport „Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/pl/output_steam_network/steam_ecosystem_dashboard",
      "source_html_sha256": "420120604d2008fab9aa9254f534d843ce6e4f7ad1da9616e218bf6117862eff",
      "exported_at": "2026-09-29T00:19:18.162Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__steam_ecosystem_dashboard.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/pl/output_steam_network__steam_ecosystem_dashboard.pdf?v=print-20260929-v5",
        "sha256": "9b75ec900364646e905cb093bc7beca403ffd5d134b1a838ff7d008481250653",
        "bytes": 39417,
        "pages": 1
      },
      "integrity": {
        "signed_object": "output_steam_network__steam_ecosystem_dashboard.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__steam_ecosystem_dashboard.content.json.asc",
        "digest_file": "output_steam_network__steam_ecosystem_dashboard.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__steam_ecosystem_dashboard.content.json.asc output_steam_network__steam_ecosystem_dashboard.content.json",
          "sha256sum -c output_steam_network__steam_ecosystem_dashboard.content.json.sha256"
        ]
      },
      "content": {
        "text": "PRZEGLĄD STATYSTYK // PLIK „02”\nSteam Panel ekosystemu — Sieć w liczbach\n\nSieć w liczbach.\n\nCO WYKAZUJE TA CZĘŚĆ\n\nTen pulpit nawigacyjny gromadzi informacje o strukturze kodu pochodzące od programistów serwisu 3,320 oraz z repozytoriów 252, identyfikując bazy kodu związane z hazardem dostępne na stronie 68 oraz mostki łączące różne platformy. Dane empiryczne wskazują na skupiska geograficzne i nakładanie się grup programistów, co pokazuje, że infrastruktura hazardowa typu „skin” stron trzecich funkcjonuje jako zorganizowana, silnie powiązana branża oprogramowania zintegrowana z platformą Steam.\n\n← Powrót do podsumowania dla kadry kierowniczej\n\nSkonsolidowane dane statystyczne z bazy danych dochodzenia: rozkład geograficzny, czołowe firmy, repozytoria gier hazardowych typu „skins” oraz aktywne mosty łączności.\n\nZespół Scanned Devs3320\nŁączna liczba repozycji252\nRepozytoria dotyczące hazardu68\nŁączna liczba połączeń1,426\nStruktura i sektory automatyki\nSektor I — Rdzeń korporacji „Valve”\n\nOficjalne repozytoria i oprogramowanie systemowe. Potwierdzone środowisko programistyczne pracowników firmy „Valve” – Nephyrin i Joe Ludwig.\n\nSektor II — Silniki autoryzacyjne i emulatory protokołów (SteamKit)\n\nBiblioteki sieciowe opracowane metodą inżynierii odwrotnej, których współautorami są Nephyrin z serwisu Valve oraz DoctorMcKay, twórca gier hazardowych typu „skins”.\n\nSektor III — Klienci zajmujący się farmowaniem kart (ArchiSteamFarm)\n\nWykorzystaj emulatory protokołu SteamKit do uruchamiania w tle milionów fałszywych klientów (w stanie bezczynności) w celu gromadzenia kart kolekcjonerskich.\n\nLokalizacja deweloperów\nNiemcy57\nStany Zjednoczone52\nKanada48\nWielka Brytania44\nPolska30\nFrancja28\nFederacja Rosyjska27\nChiny27\nUSA (stan Waszyngton)23\nAustralia19",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam Panel ekosystemu — Sieć w liczbach"
          },
          {
            "level": 3,
            "id": null,
            "text": "Sektor I — Rdzeń korporacji „Valve”"
          },
          {
            "level": 3,
            "id": null,
            "text": "Sektor II — Silniki autoryzacyjne i emulatory protokołów (SteamKit)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Sektor III — Klienci zajmujący się farmowaniem kart (ArchiSteamFarm)"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/pl/#briefing-heading"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/pl/output_steam_network__steam_ecosystem_dashboard.content.json",
      "export_json_sha256": "b34cbe97aac179e1dedb7a92187330fdebe8d6a366b3a58e6417aced8fb30bb2"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "pl/output_steam_network/valve_ru_farming_isolated.html",
      "language": "pl",
      "title": "Kod, współtwórcy i rozgałęzienia — Dossier „Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/pl/output_steam_network/valve_ru_farming_isolated",
      "source_html_sha256": "7d0badfbec5409e2613d73fe97bb9fc02d7fc3d60f67492644dc870f3297234e",
      "exported_at": "2026-09-29T00:19:19.402Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__valve_ru_farming_isolated.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/pl/output_steam_network__valve_ru_farming_isolated.pdf?v=print-20260929-v5",
        "sha256": "79ddea92fa38fa7c2f441391698104c8b7f1862d1dd478b93811ad1d5fdad53e",
        "bytes": 42558,
        "pages": 2
      },
      "integrity": {
        "signed_object": "output_steam_network__valve_ru_farming_isolated.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__valve_ru_farming_isolated.content.json.asc",
        "digest_file": "output_steam_network__valve_ru_farming_isolated.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__valve_ru_farming_isolated.content.json.asc output_steam_network__valve_ru_farming_isolated.content.json",
          "sha256sum -c output_steam_network__valve_ru_farming_isolated.content.json.sha256"
        ]
      },
      "content": {
        "text": "CZĘŚĆ II / POSTĘPUJ ZGODNIE Z UDOKUMENTOWANĄ RELACJĄ\n\nRozgałęzienia, wkłady i zależności oprogramowania stanowią wyraźne dowody. Pogląd ten uwzględnia zebrane informacje o pełnionych rolach; zatrudnienie, obejście zabezpieczeń i udział w działalności przestępczej wymagają dodatkowych źródeł.\n\nOtwórz interaktywną mapę możliwości ↗\nŹRÓDŁA PUBLICZNE / KONTROLA ROLI\nKod. Autorzy. Rozgałęzienia.\n1. Nephyrin: rozgałęzienia i wkłady\n\nW dostarczonym zrzucie ekranu Nephyrin jest wymieniony jako współtwórca projektu ValveSoftware/Proton oraz autor rozgałęzień projektów SteamRE/SteamKit i SteamRE/open-steamworks. W danych profilowych podano firmę „Valve Software”. Pola te należy traktować oddzielnie.\n\nRozgałęzienie stanowi kopię repozytorium. Ten eksport nie zawiera zatwierdzenia wprowadzającego zmiany w kodzie uwierzytelniania SteamKit.\nOdwołania do repozytorium / przeglądaj historię\nSteamRE/SteamKit ↗ SteamRE/open-steamworks ↗\n2. Funkcje publiczne: automatyzacja bez klienta desktopowego\n\nBiblioteki SteamKit i node-steam-user umożliwiają programową interakcję z serwisem Steam. Projekt ArchiSteamFarm opisuje metodę zdobywania kart przy użyciu wielu kont i deklaruje bibliotekę SteamKit2 jako zależność.\n\nSą to konkretne możliwości automatyzacji. Wykonanie bezinterfejsowe nie oznacza wyłącznego wykorzystania komercyjnego ani obejścia zabezpieczeń „Steam”. Istotne znaczenie mają: żądane poświadczenia, dostępne działania oraz mechanizmy kontroli stosowane przez platformę.\n\nŹródło: pliki README projektów oraz strona ArchiSteamFarm.csproj. Mapa możliwości zawiera linki do wszystkich udokumentowanych zależności.\n3. JoeLudwig: oznaczenie współtwórcy hl2sdk\n\nW podglądzie JoeLudwig figuruje jako współtwórca projektów alliedmodders/hl2sdk, ValveSoftware/openvr oraz ValveSoftware/source-sdk-2013. Jest to widoczny związek między projektami. Eksport nie zawiera dowodów łączących konkretną zmianę w SDK z kradzieżą lub wykorzystaniem w grach hazardowych.\n\nOdwołania do repozytorium / przeglądaj historię\nalliedmodders/hl2sdk ↗ DoctorMcKay/node-steam-user ↗\nSCHEMAT LOGICZNY // ŚCIEŻKI\nSchemat blokowy logiki połączeń:\nPROFIL RELACJI\nNephyrin / zebrane informacje o profilu\nAutor: Proton. Twórcy rozgałęzień: SteamKit i open-steamworks.\n▼ Zestawienie powiązań rozgałęzień\nBIBLIOTEKA SPOŁECZNA\nSteamRE/SteamKit\nPubliczna biblioteka sieciowa Steam prowadzona przez organizację SteamRE.\n▼ Zadeklarowano zależność od SteamKit2\nUDOKUMENTOWANA AUTOMATYZACJA\nJustArchiNET/ArchiSteamFarm\nDokumentacja dotyczy tworzenia kart na wielu kontach oraz zależności od biblioteki SteamKit2.\nPRZEGLĄD DOWODÓW / ZARYS ŹRÓDŁA\nZAPISANO: odrębne etykiety „contributor” i „forker”.\nUDOKUMENTOWANO: biblioteki publiczne wspierają interakcje w ramach programu „Steam”.\nPYTANIE OTWARTE: ustalenie konkretnego autora kodu, zatwierdzenie platformy oraz przypisanie odpowiedzialności za nadużycia wymagają odrębnych dowodów.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Kod. Autorzy. Rozgałęzienia."
          },
          {
            "level": 2,
            "id": null,
            "text": "1. Nephyrin: rozgałęzienia i wkłady"
          },
          {
            "level": 2,
            "id": null,
            "text": "2. Funkcje publiczne: automatyzacja bez klienta desktopowego"
          },
          {
            "level": 2,
            "id": null,
            "text": "3. JoeLudwig: oznaczenie współtwórcy hl2sdk"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/pl/investigation_part2.html#automation-map",
          "https://github.com/SteamRE/SteamKit",
          "https://github.com/SteamRE/open-steamworks",
          "https://github.com/alliedmodders/hl2sdk",
          "https://github.com/DoctorMcKay/node-steam-user"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/pl/output_steam_network__valve_ru_farming_isolated.content.json",
      "export_json_sha256": "78f51b4ae53b2164ff4d65b8383bc57d71e55f3ef41649d3f98bf24e416fb032"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "uk/card_economy.html",
      "language": "uk",
      "title": "Економіка карт — Досьє «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/uk/card_economy",
      "source_html_sha256": "d73008dac25a2c723a84f6c42fbba3aa2a8096c027fe6c46144274acd1cfcfc8",
      "exported_at": "2026-09-29T00:19:24.113Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "card_economy.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/uk/card_economy.pdf?v=print-20260929-v5",
        "sha256": "0fde2590f4ae037a8e881ff77702d6b4b319c057d92fac30bb38396c16756d4b",
        "bytes": 265998,
        "pages": 26
      },
      "integrity": {
        "signed_object": "card_economy.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "card_economy.content.json.asc",
        "digest_file": "card_economy.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify card_economy.content.json.asc card_economy.content.json",
          "sha256sum -c card_economy.content.json.sha256"
        ]
      },
      "content": {
        "text": "ДОДАТОК V — КАРТКОВА ЕКОНОМІКА\n«Ферма ботів» — це не протікання у магазині Valve. Це — клієнт.\n\nРахунок Steam не може отримати жодної колекційної картки, доки не буде витрачено $5.00 у магазині. Вона не може фармити гру, якою не володіє, і не може фармити ту, яку отримала безкоштовно. Тож перш ніж автоматизована система фарму карт почне щось виробляти, вона має оплатити доступ — за кожен обліковий запис, за ціною, яку оприлюднює Valve. Потім пункт про автоматизацію Valve по рядках перелічує, що саме виробляє ця система; її ліцензія забороняє будь-які способи, за допомогою яких фармована картка перетворюється на гроші; а її ринок бере комісію, коли картка все одно продається — рекламована за ціною 15%, але з мінімальною ціною у два центи за продаж, що для картки, ціна якої виражена в центах, становить більшу частину вартості. Цей експонат показує, наскільки великим є цей обіг, скільки коштує у наборах найвищий рівень профілю, та як відділ контролю Valve застосовує те саме положення, коли обліковий запис належить звичайному трейдеру.\n\nЩо фермерське господарство має придбати в першу чергуСкільки коштує один рівень у наборахОбидві сторони столуХто регулює економіку карт\n$5.00Необхідно здійснити покупку в магазині, перш ніж на рахунок можна буде отримати будь-яку картку — сторінка служби підтримки Valve\n13,876Ігри на Steam, які випускають колекційні картки та містять 99,971 різних типів карток\n694,673Повні набори карток, які наразі є в наявності у 91 публічно зареєстрованих торгових ботів\n1,389,346Норми видачі облікових та ігрових карток, які запас вже використав, як мінімум\n$9.99Медіанна ціна на карткову гру — готовий набір такої гри продається за медіанну ціну $0.74\n97,114Учасники групи з обміну картками, у списку модераторів якої зазначено співробітника з позначкою Valve — § 08\n01 — Процес\nЩо таке ферма насправді: покроковий опис\n\nІнформація наведена виключно на основі документації самого інструменту та сторінок служби підтримки Valve. Ніщо в цьому розділі не є висновком, і жодна зі сторін не оскаржує жодного з наведених тут тверджень.\n\nКрок 1\nПриєднатися\n\nАкаунт не повинен бути обмежений. Сторінка підтримки Valve забороняє обліковим записам з обмеженими правами «Участь у ринку Steam», з «Обмін Steam предметами спільноти (колекційні картки, бустер-паки, дорогоцінні камені тощо)» та з «Отримання Steam рівнів профілю (зафіксовано на рівні 0) та колекційних карток». Головне — це гроші: «Вам потрібно буде витратити щонайменше $5.00 доларів США у магазині Steam».\n\nКрок 2\nКупити ігри\n\nКартки можна отримати лише в іграх, які ви маєте у власності. «Щоб мати право на отримання будь-яких карт із цієї гри, ви повинні бути її власником на своєму обліковому записі Steam. Спільний доступ для сім’ї не вважається правом власності і не береться до уваги». Безкоштовні маршрути також закриті: «У платних іграх, які ви отримали безкоштовно в рамках акції, неможливо фармити картки», та «Неможливо отримати карти з безкоштовних ігор, не витративши в них жодних грошей».\n\nКрок 3\nУ режимі очікування\n\nЦей інструмент безінтерфейсно входить в мережу Steam від імені облікового запису, \"аналізує ваші значки\", формує список ігор, у яких можна заробляти ресурси, і запускає «грати у відповідну гру та періодично перевіряти, чи вже повністю пройдено гру». Опис механізму, наданий його розробником: він «не робить нічого іншого, крім як повідомляти Steam, що ми граємо в певну гру».\n\nКрок 4\nКраплі закінчилися\n\nКожен заголовок є скінченним. «У кожній грі передбачена фіксована кількість карт, які можна отримати. Як тільки ви отримаєте їх усі (приблизно половину повного набору), гра більше не є перспективною для фарму». Ферма, яка хоче продовжувати виробництво, мусить постійно купувати картки. Постачання карток обмежується обсягом покупок — це передбачено механізмом гри і грає на користь Valve.\n\nКрок 5\nВиведення коштів\n\nКартка виходить через одні з трьох «дверей»: продається на «Ринку спільноти», обмінюється або переробляється на самоцвіти. Кожен із цих випадків є транзакцією на «Ринку передплатників» або обміном, і у § 3.D передбачено стягнення плати: «Valve може стягувати комісію за транзакції на ринку підписок». Саме цей крок і робить усе це порушенням — див. 05.\n\nДжерела, прочитані та процитовані дослівно на 2026-09-22: Steam Підтримка — Обмежені облікові записи користувачів ↗ · ArchiSteamFarm Поширені запитання ↗ · Valve — Steam Часті запитання щодо колекційних карток ↗ · Steam Угода з абонентом ↗ архів 2026-09-24 ↗. На цій сторінці ArchiSteamFarm використовується як вимірювальний прилад, а не як відповідач; у його власній документації чітко зазначено, що «ASF не має дозволу від Valve».\n\n02 — Шкала\nПерш ніж ферма заробить хоч один цент, вона вже виплатила Valve\n\nОскільки обліковий запис з обмеженим статусом не може отримати картку, кожен обліковий запис у фермі повинен бути переведений з обмеженого статусу, перш ніж він почне давати врожай. Поріг опубліковано, і плата стягується за кожен обліковий запис.\n\nРозмір ферми\tЗвідки взято це число\tМінімальна сума покупок у магазині, необхідна для отримання права на отримання картки\n10 облікових записів\tСтеля, яку рекомендує ASF, — «на основі внутрішніх Valve рекомендацій, а також наших власних пропозицій»\t$50\n100–200 облікових записів\tТехнічна межа в тому ж розділі «Часті запитання»: «За допомогою однієї IP-адреси та одного екземпляра ASF можна запустити до 100–200 ботів»\t$500 – $1,000\n120 облікових записів\tСправа про порушення № 3, наведена нижче — назавжди заблоковано\t$600\n170 облікових записів\tВипадок № 2, описаний нижче, — постійна заборона під час зимового розпродажу 2017 року\t$850\n1,000 рахунків\tСправа про примусове виконання № 1, наведена нижче — заборона торгівлі\t$5,000\n5,000 рахунків неперевірений\tВаги оператора надані в рамках цього розслідування та не перевірені незалежно — див. примітку щодо джерел інформації\t$25,000\n10,000 рахунків неперевірений\tВаги оператора наведені в рамках цього розслідування та не перевірені незалежно — див. примітку щодо джерел інформації\t$50,000\n\nОстанні два рядки — це єдині дані на цій сторінці, що ґрунтуються на неперевіреному звіті, а не на документі — вони позначені в таблиці, пояснення щодо них наведено в примітка щодо джерел інформації, і ніщо інше тут від них не залежить. Правий стовпець відображає арифметичні обчислення, що ґрунтуються виключно на опублікованому Valve порозі в $5.00 доларів США, і ні на чому іншому. Це — підлога, це не оцінка вартості ферми чи суми, яку заробив Valve: ця цифра не враховує ігри, які мають бути у власності гравця і не можуть бути отримані безкоштовно в рамках акції, а також не враховує приблизно 15%, які стягує «Ринок спільноти» під час продажу карт. На цій сторінці не наводяться жодні дані щодо доходів.\n\nА Valve самостійно визначило вартість роздачі карток. У розділі «Часті запитання» щодо колекційних карток вказано коефіцієнт конвертації у грі з безкоштовною моделлю в простих доларах:\n\n«У безкоштовних іграх ігрові картки видаються залежно від ваших покупок у грі». За кожні $9 доларів США, витрачених (приблизно) «З моменту запуску бета-версії колекційних карток Steam ви отримаєте одну картку».\n\n— Valve, Steam Часті запитання щодо колекційних карток ↗ · перевірено дослівно 2026-09-22\n\nКолекційна картка — це не безкоштовний подарунок, на якому платформа зазнає збитків. Це товар, який Valve продає за ціною, опублікованою в Valve, а потім стягує плату вдруге за його подальший продаж. Ось чому чесний опис «карткової ферми» — це не паразит. Це оптовий покупець.\n\nЯкий насправді розмір того, що купується\n\nУсе, що наведено від цього місця до кінця цього розділу, є результатом вимірювань, а не даними зі звітів. Дані щодо кількості карток взято з опублікованого «Card Exchange» прайс-листа Steam; ціни на самі ігри отримано з API власного магазину Valve; дані щодо запасів ботів взято з публічного каталогу ботів, доступ до якого має кожен. Усі три джерела були прочитані на 2026-09-22, а повні розрахунки наведено в розділ 08.\n\n13,876Ігри, в яких роздають карти\n99,971Різні типи карток\n5 · 6 · 15Кількість карток у наборі: мінімум, медіана, максимум\n$0.74Медіанна ціна готового набору\n$23,586.57На ринку є по одному екземпляру з кожного набору\nЯкий розмір має набір\n\n13,876 ігор за картками з набору. Valve переносить приблизно половину з них на будь-який один обліковий запис.\n\n0\n1,250\n2,500\n3,750\n5,000\n5\n6\n7\n8\n9\n10\n11\n12\n13\n14\n15\nСкільки коштує ліцензія\n\nКаталожна ціна тих самих ігор у магазині Steam, у доларах США.\n\n0\n1,000\n2,000\n3,000\n4,000\n<$1\n$1-3\n$3-5\n$5-10\n$10-20\n$20-40\n$40+\nЩо повертає готовий набір\n\nРинкова ціна готового набору для тих самих ігор.\n\n0\n1,500\n3,000\n4,500\n6,000\n<$0.50\n$0.50-1\n$1-2\n$2-5\n$5-10\n$10+\n\nЯкщо порівняти другий і третій графіки, то форма розподілу стає очевидною навіть без математичних розрахунків: ігри зосереджуються в діапазоні десятків доларів, а набори, які вони дають, — в межах одного долара. Обидва графіки відображають кількість одних і тих самих 13,876 ігор з однаковою одиницею виміру на осі, тому порівняння відбувається між двома висотами, а не між двома шкалами.\n\nЦе сторона пропозиції. Сторона попиту — це та частина, яку Valve не потрібно рекламувати, оскільки вона вже є у відкритому доступі: у єдиному відкритому каталозі ботів для обміну картками перелічено На даний момент у наявності 91 бот із повними наборами 694,673. Без авторизації, без збору даних з торгової платформи, без приватних даних — інформація про кількість товару вказана на сторінці поруч із назвою кожного бота.\n\nЗробіть цю акцію єдиною величиною, яка тут має значення. Власне правило Valve: «У більшості ігор випадає кількість карт, що дорівнює приблизно половині кількості карт у наборі цієї гри… Вам доведеться зібрати іншу половину набору у інших учасників спільноти.\" Один акаунт ніколи не зможе завершити сет, граючи. Потрібно щонайменше два акаунти, кожен з яких володіє цією грою і витрачає свою квоту на «дроп» (один раз на гру). Квота на «дроп» не відновлюється.\n\n694,673Набори в наявності, 91 публічний бот\n3,473,365Карти, при мінімальній кількості 5 карт\n1,389,346Витрачені допуски на падіння, мінімальні\n2,602Акаунти, на яких зареєстровано лише одну гру, — найбільша концентрація ботів\nДе розташовані набори 694,673\n\nДванадцять найбільших із 91 публічно зареєстрованих «карткових ботів» за кількістю повних наборів у наявності. Десять найбільших з них разом мають 248,115 наборів — 35.7% від усього, що є на дошці.\n\n0\n11,250\n22,500\n33,750\n45,000\nCard Supply #4 (High)\nN!vq's Leveling (High)\nAlice [BOT] LEVEL-UP RARE SETS\nN!vq's Leveling (Low)\nDisco Lite Level Up\nN!vq's Leveling (Mid)\nbaty131store.net | Level Up\nKitten - Supreme\nArashirn | Level Up\nSH (Junior) Level Up\nDuobot.com - Overstock\nlvlupbot.com - godlike\n\nКожна з цих 1,39 мільйона квот належала обліковому запису, який володів грою, перетнув позначку $5.00 і більше ніколи не зможе отримати ці нагороди. Це нереалізовані запаси на дев’яносто одному боті. Це не показник ринку; це показник того, що залишається після ринку.\n\nОстаннє число відображає розподіл за категоріями, а не загальну кількість користувачів. Один бот вказує 14,310 наборів, отриманих лише з 11 ігор, отже, принаймні одна з цих ігор представлена 1,301 наборами, що відповідає щонайменше 2,602 різним обліковим записам, кожен з яких придбав цю гру. Це найменше число, яке допускає арифметика, і воно стосується одного бота з дев’яноста одного.\n\nЩо цей текст говорить, а що — ні\n\nЦі боти купують картки як у звичайних гравців, так і у «ферм» — опубліковані ними ціни на купівлю і є основною метою цього каталогу. Отже, 1,39 мільйона квот не є кількістю рахунків, що належать фермерським господарствам. Це кількість допусків на отримання предметів — по одному на обліковий запис і по одному на гру — які були використані десь у грі Steam і в підсумку залишилися непроданими у комерційному запасі. Незалежно від того, чи був обліковий запис за кожним із них «фармом», чи підлітком, який розчищав свою сторінку з відзнаками, це не змінює того, що отримала Valve: розблокування $5.00, ліцензію на гру та частку від кожної угоди на Маркеті — не 15%, а 15% або дві мінімальні суми по одному центу, залежно від того, яка з них більша, що на картці, ціна якої вказана в центах, є значно більшою. Розрахунок наведено в наведена нижче шкала тарифів. У цьому і полягає суть цієї сторінки, і це не є наріканням на фермерів: та сама поведінка, за яку Valve стягує плату, — це саме та поведінка, яку вона дослівно наводить як підставу для постійного блокування користувача за «комерційне використання».\n\nЦей показник також є мінімальним рівнем у другому значенні. Він враховує лише акції, які є виставлені на продаж і не продані сьогодні про ботів, які вибрати розміщення у загальнодоступному каталозі. Усе вже продано, усе перебуває у приватній власності, а всі боти, що не входять до каталогу, виключені.\n\nА сільське господарство не окупається за цінами Valve\n\nОчевидне заперечення полягає в тому, що ферма купує дешеві ігри, щоб випускати дорогі картки. Власний API магазину Steam свідчить про інше. З 13,876 ігор, що містять картки, ціни були визначені для 13,713; 12,918 — це платні видання, середня каталожна ціна яких становить $9.99. Медіана ціни готового набору становить $0.74. На кожен комплект потрібно дві ліцензії. Отже, середня вартість комплекту становить приблизно $19.98 ігрових ліцензій на виробництво та повернення $0.74.\n\nВиміряно на 2026-09-22\tЗначення\tЩо це регулює\nМедіанна ціна за каталогом, гра з картками\t$9.99\tЛіцензія — це та частина угоди, яка коштує дорожче, а не сама картка\nІгри вартістю $4.99 або менше\t3,665 (28.4%)\tНавіть найдешевший хвіст коштує дорожче, ніж набір, який з нього виходить\nНайдешевша гра з картами у магазині\t$0.99\tДві ліцензії, $1.98, на набір, який зазвичай продається за ціною нижче $1.30\nІгри, набір яких продається дорожче, ніж сама гра\t323 із 12,918 (2.5%)\tАрбітраж з картками щодо рекомендованих цін Steam зустрічається в 1 грі з 40\nБезкоштовні ігри, включені до переліку\t795\tА Valve оцінює кожну зі своїх колекцій у $9 ігрових витрат\n\nЦе вирішує економічне питання на користь Valve і суперечить загальноприйнятій думці. За цінами, які встановлює сама Valve, «фарм карт» — це збиткова діяльність, яка приносить прибуток лише у разі придбання ліцензій за ціною, нижчою за каталожну ціну Steam — пакети, регіональні ціни, ключова перепродаж. Картки — це лише побічний продукт. Подія — це сама покупка. І покупка відбулася Steam.\n\nЩо насправді підтримує ферма\n\nЯкщо скласти всі ці елементи воєдино, ферма перестає виглядати як щось, що Valve терпить, і починає виглядати як щось, що Valve потребує. Кожен вхідний ресурс, який надає ферма, є вихідним ресурсом, за який Valve звітує або виставляє рахунки. Простежте один акаунт-бота назовні:\n\nОдин підроблений акаунт«оптовий клієнт», а не витік інформації\nПродажі ігор\n\nКупує ігри, які фармить — від карткових ігор 13,876 до «шовелвера» $0.50 — оскільки карти випадають лише з ігор, що знаходяться у власності.\n\n«Онлайн» та ігри\n\nЗмушує їх скидати карти, тим самим поповнюючи показники кількості одночасних гравців та кількості відіграних годин, які Valve наводить як показники залученості — саме ту статистику, яку § 4.C називає «фальсифікацією часу гри».\n\nРеєстрації\n\nПотрібно пройти контроль обмеженого рахунку $5.00, перш ніж можна буде отримати картку — реальні витрати в магазині Valve записів на кожен рахунок.\n\nГроші на гаманці та комісії\n\nКожна продана картка проходить через «Маркет», де комісія за картку з низькою номінальною вартістю досягає 66.7%, а виручка залишається заблокованою у гаманці Steam.\n\nSteam-рівень PR\n\nВітрини з значками та рівнями Valve існують лише тому, що набори були створені вручну — а верхівку цієї ієрархії займають боти (див. § 03).\n\nВилучіть ферму, і всі наведені вище числа зменшаться — гра продалася меншим тиражем, «онлайн»-спільнота була меншою, обліковий запис так і не було зареєстровано, плату так і не стягнули, а рівень так і не було досягнуто. Ось чому правило, що забороняє автоматизацію, співіснує з мільйонами автоматизованих облікових записів: заборона — це лише опція, а активність — це дохід.\n\nА сам вивід коштів — це втрата вартості: Valve — подвійне оподаткування\n\nКартка — це не кінець циклу. Завдяки власній механіці Valve картку можна розчавити до коштовні камені, а дорогоцінні камені витрачаються на виготовлення набори карт — ще три картки — які знову продаються або знищуються. Кожен крок у циклі — це ринкова транзакція або конвертація, і кожна з них оподатковується. Напрямок цього циклу випливає з мінімального розміру комісії, визначеного нижче, і не потребує зовнішньої моделі: кожна картка, продана в межах циклу, віддає щонайменше два центи, на картках, які обмінюються за три-п’ять, тож кожен оберт рукоятки приносить менше, ніж було вкладено. Цей цикл знищує віртуальну вартість і змушує замінювати її новими транзакціями, за які стягується комісія. У цьому тексті не наводиться жодних даних щодо розміру цих збитків — прибуток за один набір залежить від частоти випадання самоцвітів та ймовірності випадання бустерів, які в рамках цього дослідження не вимірювалися.\n\nКолекційна карткапредмети з власної гри\n→\nКоштовне каміннякартка зім'ята, комісія стягнута\n→\nДодатковий набіркоштовні камені, витрачені на виготовлення\n→\n3 нові карткипродано на Market, комісія стягнута\n↶\n\nТут викладено лише механіку гри, і це власна механіка Valve — карти перетворюються на самоцвіти, із самоцвітів виготовляють бустери, а з бустерів отримують карти — кожна з цих операцій описана в розділі «Часті запитання про колекційні карти» Steam, і кожен такий крок є подією на ринку, що оподатковується. Джерело механіки циклу: Valve, Steam Часті запитання щодо колекційних карток ↗.\n\nЦе не просто миттєве явище. Це галузь, що має багаторічну основу.\n\nОдин знімок екрана міг бути випадковістю. Тому публічний каталог карткових ботів переглядали один раз під час кожного сезонного розпродажу Steam, використовуючи Wayback Machine, у період з 2022 по 2026 рік — асортимент товарів, який боти пропонували, та ті самі акаунти, розпродаж за розпродажем. Ця економіка не з’являється і не зникає; вона існує постійно, маючи стабільне ядро операторів, і досягла піку, перевищивши три мільйони комплектів у наявності під час зимової розпродажі 2023 року — близько третини мільйона цінних ключів TF2, що зберігалися одночасно в одному каталозі.\n\nПовні набори карток, що зберігаються у загальнодоступному каталозі ботів, за Steam продажів\n\nОдин знімок з Wayback для steam.supply/CardBots на кожен сезонний розпродаж. Наведіть курсор, щоб побачити вартість ключів TF2 за курсом на момент створення цього знімка.\n\n0.0M\n0.9M\n1.8M\n2.6M\n3.5M\nA’22\nS’23\nW’23\nS’24\nW’24\nS’25\nS’26\n401У процесі продажів було виявлено окремі акаунти-ботів\n59Присутні у 5 або більше з 7 продажів — стабільне ядро\n16Брав участь у кожному з 7 аукціонів у 2022–2026 роках\n3,22 млнНаявність на складі набору Peak (зима 2023 року) ≈ $570k–790k у ключах\nЯк виглядає «драбинка значків» одного відділу продажів, якщо дивитися зверху\n\nПопит відповідає пропозиції. Щодо громадськості Рейтинг значків «Літній розпродаж 2024» архів 2026-07-16 ↗, а обліковий запис № 1 створив значок продажу 1,740,645 разів — 1,74 мільйона наборів із десяти карток, 17,4 мільйона карток об’єднані в єдиний профільний орнамент. За ринковою ціною самого розпродажу ($0.50 за комплект) це становить ~$870,000 вартість картки; якщо купувати так, як це робиться насправді — обмінюючи ключі TF2 на підвищення рівня ботів із розрахунку приблизно 7,6 наборів за один ключ — то це ~229,000 клавіші, приблизно $410,000–$570,000 у реальному вираженні. Рахунок № 2: 552,000 наборів, ~$130,000–181,000. Ніхто з людей не грає за це. Його купують, і кожен етап купівлі є транзакцією, яку Valve зводить до нуля.\n\nМетод та обмеження: загальний обсяг запасів підсумовується за всіма ботами, переліченими у кожному знімку; число Кількість ботів у кожному знімку не можна порівнювати між різними продажами, оскільки в деяких знімках відображаються лише рекомендовані боти, а в інших — повний каталог; отже, дані про кількість ботів слід розглядати як мінімальний показник того, що було видно, а не як повний перелік. Для ключових значень використовується медіанна кількість наборів на ключ, заявлена в кожному знімку, та ключ TF2 з значенням від $1.79 до $2.49. Сталість забезпечується за допомогою SteamID64 у всіх знімках. Знімки за 2021 рік використовували старий макет сторінки і не включені до аналізу. Дані: farm-economy-timeline.json; рівні значків із SteamLadder; ціни, встановлені на Steam Card Exchange (знімки Wayback на момент продажу, $0.05 за картку).\n\nІ цей самий асортимент товарів доступний навіть тоді, коли акції не проводяться\n\nДві фотографії, наведені вище, не зображують дві популяції. Це один флот, сфотографований у різні моменти часу. Каталог, згаданий на початку цього розділу, було прочитано на звичайний день, коли не проводиться сезонний розпродаж — 2026-09-22 — і навіть у стані спокою вона трималася 91 ботів та 694,673 повних наборів: приблизно 186,000 клавіші TF2, $334,000–$464,000 номіналу карти, перебувають у неактивному стані між продажами. Це мінімальний обсяг, який підтримує підприємство, коли нічого не відбувається.\n\nІ це та сама операція. Збіг за SteamID64, 87 із цих 91 неактивних ботів — 96% — також фігурують у семи знімках стану продажів, наведених вище, по шістнадцять у кожному з них. Цей каталог — це не тимчасовий кіоск, який відкривається на час розпродажу, а потім закривається; це постійний комерційний перелік, який завдяки цьому ж автопарку збільшився аж до 3,22 мільйона комплектів на піку зими 2023 року і ніколи не опускається до нуля. Розпродаж — це коли товар продається. Він існує й протягом решти року.\n\nКаталог зберігання, для кожного бота окремо\n\nКожен квадрат відповідає одному боту в каталозі на 2026-09-22; він виділений, якщо також фігурує у семи знімках продажів. Цифра 91 — це те, що було вказано в довіднику того дня, а не чисельність флоту — У знімках продажів фігурує 401 унікальний обліковий запис, а каталог відображає різні набори даних у різні дні.\n\nПоказано в минулих аукціонах (87) Нові зміни з моменту останнього знімка (4)\n\nБазове значення для нерозпродажу дорівнює 2026-09-22 з того самого публічного каталогу, без входу в систему. Для розрахунку базового значення використовується власна заявлена частота наборів на ключ кожного бота та діапазон ключів $1.79–$2.49 вище. Перекриття визначається за SteamID64 у порівнянні з сімома моментальними знімками розпродажу. Оскільки перелік «рекомендованих» та «повних» позицій відрізняється залежно від моментального знімка, тут порівнюються запаси та ідентифікатори, а не кількість користувачів. Арифметика в розділ 08.\n\n03 — Сходи\nІнший елемент — це число, що стоїть поруч із вашим ім’ям\n\nКартки — це сировина. Готова продукція має рівень Steam, а Valve визначає її ціну в наборах.\n\n100Steam Рівень\nЦільовий рівень — перетягніть або скористайтеся клавішами зі стрілками\nЦіна одного повного комплекту, доларів США\n\n$0.20 — найдешевший повний набір у переліку, $0.74 — медіана, $1.70 — середнє значення. Цифра стосується лише карток — вона не включає $5.00 розблокування чи ігрові ліцензії.\n\n55,000Необхідний XP\n550Використані повні комплекти\n110Ігри, які варто придбати, щоб самостійно заробляти в них ресурси\n$407.00Вартість карток за цією ціною\n1,100Зниження дотацій, що були використані, мінімальне\n$5,500.00$5.00 розблоковується, якщо обліковий запис не використовується повторно\nВикористані повні набори, рівень від 1 до 1,000\n\nОдне виготовлення значка = один повний набір = 100 XP. Кожен рівень у межах десятки коштує на 100 XP більше, ніж рівень у наступній десятці нижче.\n\n0\n12,625\n25,250\n37,875\n50,500\n1\n250\n500\n750\n1000\n667\n550 sets\n\nРівень — це не просто прикраса, яку Valve залишає без уваги. Він інтегрований у обліковий запис. З власного розділу «Часті запитання» про торгові картки від Valve, де йдеться про те, що дає виготовлення значка: «100 XP, що може підвищити ваш рівень Steam. Якщо ваш рівень Steam зросте, обмеження на кількість друзів у вашому списку збільшиться на п’ять, і, можливо, ви отримаєте можливість налаштувати свій профіль за допомогою вітрин». А щодо бустер-пакетів: «Ваш рівень Steam підвищує ймовірність отримання бустер-паку: 10-й рівень: +20%… 50-й рівень: ймовірність отримання збільшується на +100% (тобто ймовірність подвоїлася)».\n\nОтже, цей рівень визначає дві речі Valve: скільки людей ви можете додати в друзі та з якою швидкістю безкоштовні картки потрапляють у ваш інвентар. Другий фактор має кумулятивний ефект — чим більше наборів ви використали, тим швидше платформа надає вам новий матеріал. Valve вбудував цикл реінвестицій у продукт.\n\nКурс обміну є фіксованим і оприлюднений. Виготовлення одного значка вимагає одного повного набору і приносить 100 XP; «Набір для однієї гри можна створити не більше п’яти разів». Вартість одного рівня XP зростає кожні десять рівнів. У результаті виходить наступне, і жодні дані тут не є приблизними:\n\nSteam Рівень\tПовні набори, які він використовує\tІгри, які потрібно мати, щоб самостійно їх створювати\tНа найнижчому рівні, що коли-небудь фіксувався ($0.20)\tУ наборі медіан ($0.74)\tМасштаб\n10\t10\t2\t$2.00\t$7.40\t\n50\t150\t30\t$30.00\t$111.00\t\n100\t550\t110\t$110.00\t$407.00\t\n200\t2,100\t420\t$420.00\t$1,554.00\t\n500\t12,750\t2,550\t$2,550.00\t$9,435.00\t\n667\t22,579\t4,516\t$4,515.80\t$16,708.46\t\n\n667 — це не гіпотетичне значення. Це найвищий рівень, до якого, за даними публічного каталогу, може підняти клієнта один бот із 33,359 наборів, які він має у 6,117 іграх. Четвертий стовпець відображає ту саму шкалу цін, порівняну з найдешевшим повним набором у всьому переписі; п’ятий — з медіаною. Обидва показники є ринковими цінами виключно на самі картки і повністю виключають вартість розблокування $5.00 та ліцензії на ігри.\n\nЯк перевірялася крива, оскільки Valve її не публікує\n\nValve вказує коефіцієнт нарахування значків («Кожні 100 XP дають вам додатковий Steam рівень») і потім здійснює хеджування — «(принаймні на початку)» — без оприлюднення інформації про підвищення. Використана вище крива є стандартною, за якою кожен рівень у блоці з десяти коштує на 100 XP більше, ніж у блоці нижче нього. Це було перевірено за каталогом, а не припущено: для кожного бота, чий оголошений максимум обмежується його запасом, а не обмеженням у п’ять суден на гру, рівень, обчислений на основі цієї кривої, точно збігається з рівнем, який вказує бот — 541 проти 541, 494 проти 494, 464 проти 464. У тих випадках, коли обмеження діє, розраховане значення виходить на кілька рівнів вище, що й є нормальним для обмеження, яке також залежить від глибини складу в кожній грі. Щодо кривої вище рівня 667 жодних тверджень не робиться.\n\nПрочитайте таблицю поруч із розділом 02 — і стане зрозуміло, як влаштований цей бізнес. Щоб вивести один акаунт на рівень 500, хтось повинен зібрати 12,750 повних наборів. Кожен із цих наборів вимагав використання квоти на дроп щонайменше двох акаунтів, кожен із цих акаунтів перетнув $5.00-рівень, і кожен із них мав гру. Один декоративний номер у верхній частині профілю базується на щонайменше 25,500 витрачених квотах на скидання, розташованих під ним. Valve не зазнає збитків за цією угодою. Valve є контрагентом за кожним її етапом.\n\n04 — Статистика\nУ цьому пункті сільське господарство не описується в загальних рисах. У ньому наведено його перелік.\n\n§ 4.C не є загальним реченням, спрямованим проти ботів. У перелічених у ньому прикладах по черзі зазначено дві речі, які виробляє «карткова ферма».\n\n«Забороняється використовувати будь-які скрипти, боти, макроси чи інші системи, що не керуються людиною («Автоматизація»), для взаємодії з Контентом та Послугами на Steam будь-яким чином, зокрема, але не обмежуючись:\n\nАвтоматизація процесу створення облікового запису Steam,\nФальсифікація ігрових статистичних даних (наприклад, завищення кількості перемог чи поразок, XP, часу гри),\nОтримання винагород або прогресу без реального внеску користувача,\n«Участь у системах оцінювання (таких як рецензування колегами або «Overwatch») за допомогою автоматизованих засобів, зокрема шляхом впливу на результати або повідомлення про користувачів на основі заздалегідь запрограмованих дій, а не на основі обґрунтованого судження».\n— Steam Угода з абонентом, § 4.C ↗ архівувати 2026-09-24 ↗ · взято та наведено дослівно 2026-09-22\n«…час ігор»\n\nГодини простою — це не «фіктивні» години. У розділі «Часті запитання» ASF дається пряма відповідь на це питання — «Чому час гри в іграх, отриманих через ASF, не збільшується?» — разом із: «Так, але не в режимі реального часу. Steam фіксує час відтворення з фіксованими інтервалами та планує оновлення відповідних даних… зазвичай оновлення відбувається приблизно кожні 30 хвилин».\n\nЦі години відображаються у статистиці Valve, на сторінках магазину Valve, а також у статистиці кількості одночасних гравців, яку Valve публікує самостійно Steam Діаграми ↗ архівувано 2026-09-23 ↗. У цих показниках неактивний обліковий запис неможливо відрізнити від активного. Показники залученості, які платформа оприлюднює, розраховуються на основі сукупності, що, згідно з власними правилами платформи, включає облікові записи, які не використовуються.\n\n«…без реального врахування думки користувачів»\n\nЦе визначення поняття «вилучення неактивної картки», сформульоване Valve. Воно також є визначенням рівня Steam, значка, права на отримання бустер-паків та досвіду профілю, що надаються разом із ним — у FAQ ASF підтверджується, що цей інструмент «зберігає можливість отримувати бустер-паки», оскільки він входить у систему так само, як і офіційний клієнт.\n\nОтже, система винагород і заборонений вчинок — це один і той самий механізм, розглянутий з двох боків. Valve передбачив, що винагорода має надаватися за витрачений час, а не за майстерність, а потім ввів положення, яке забороняє отримання винагороди будь-яким іншим способом, окрім як шляхом витрачання цього часу людиною.\n\n05 — Пастка комерційного використання\nКожен вихід із картки, що використовується в рамках програми, є виходом, який заборонено ліцензією, — і Valve стягує плату на вході\n\nСаме цю проблему неможливо вирішити шляхом «відповідального» фармінгу. Ліцензія призначена для особистого, некомерційного використання, і картка стає привабливою для фармінгу лише в той момент, коли вона перестає бути особистою.\n\n§ 2.A — ліцензія\n\n\"Valve цим надає, а ви приймаєте, невиключну ліцензію та право на використання Контенту та Послуг для ваших особисте, некомерційне використання (за винятком випадків, коли комерційне використання прямо дозволено в цьому документі або у відповідних Умовах передплати).»\n\n§ 2.G — обмеження\n\n«Ви не маєте права: … (iii) використовувати Контент та Послуги або будь-яку їх частину в будь-яких комерційних цілях, за винятком випадків, коли це прямо дозволено в інших розділах цієї Угоди (включно з будь-якими Умовами передплати або Правилами користування).»\n\n§ 3.D — плата\n\n\"Valve може стягувати комісію за транзакції на платформі підписок. «Про будь-які комісії вам буде повідомлено до завершення транзакції».\n\nПрочитайте ці три пункти разом — і позиція закривається\n\nКартка, яку зберігають, не має ніякої цінності для ферми. Картка, яку продають, обмінюють або переробляють на дорогоцінні камені, була використана для створення цінності — і Valve у своєму листі про застосування санкцій сама вказала, як це називається: оператору 170 ботів було повідомлено, що обліковий запис «використовувався для незаконного збору колекційних карток на Steam, а також для пов’язаної з цим діяльності, що не обмежувалася лише комерційною діяльністю». У цьому випадку картки потрапили на ринок. Продаж відбувся. Комісія була стягнута. Заборона була введена вже після цього.\n\nВартість проходу через ці ворота не становить 15%. На карті з фермою вона сягає двох третин.\n\n§ 3.D. Резерви «плата». На картках, які насправді випускає ферма, ця комісія аж ніяк не дорівнює рекламованим ~15%. Community Market бере 5% Steam комісія за транзакцію та 10% комісія за гру, мінімальний розмір кожної з яких становить $0.01 (З власного розділу «Часті запитання» на Community Market від Valve). На картці, виставленій за один цент, ці мінімальні ціни є ціна: покупець сплачує три центи, два з яких — комісія. Завдяки округленню в меншу сторону показник 15% перетворюється на фактичний збір, який зростає до 66.7% саме там, де рухається ринок карток — кілька центів за картку.\n\nФактична комісія за продаж на ринку «Спільнота» залежно від ціни, запропонованої продавцем\n\n5% Steam + 10% ігор, кожна — щонайменше $0.01. У затіненій смузі відбувається фактичний обмін колекційними картками — приблизно $0.03–$0.05 за картку.\n\n0%\n10%\n20%\n30%\n40%\n50%\n60%\n70%\ncards\n$0.01\n$0.10\n$0.20\n$0.30\n$0.40\n$0.50\n66.7%\nПродавець хоче\tSteam 5% (мін. $0.01)\tГра 10% (хв. $0.01)\tОплачує покупець\tСукупна плата\n$0.01\t$0.01\t$0.01\t$0.03\t66.7%\n$0.03\t$0.01\t$0.01\t$0.05\t40.0%\n$0.05\t$0.01\t$0.01\t$0.07\t28.6%\n$0.08\t$0.01\t$0.01\t$0.10\t20.0%\n$1.00\t$0.05\t$0.10\t$1.15\t13.0%\n\nКомісія за гру в розмірі 10% надходить до додатка, який випустив картку; 5% залишається у Valve, а на власних іграх Valve та базових предметах інвентарю вся комісія дістається Valve. У будь-якому разі гроші йдуть від фармера — продаж картки вартістю три центи приносить один цент, а два центи залишаються у розробника. Помножте це на сотні тисяч продажів карток вартістю менше п’яти центів, які генерує ферма, і «плата, яку може стягувати Valve» це бізнес-модель, а не примітка. Джерело: Steam Часті запитання щодо Community Market — Комісії ↗ архів 2026-09-21 ↗, читається як 2026-09-22; крива є арифметичною на основі цих двох опублікованих ставок та їхніх мінімальних значень $0.01.\n\nНе існує такого варіанту налаштування цього інструменту, який би дозволив уникнути цього. Його може використовувати одна людина, з одного облікового запису, дотримуючись суворої стриманості — і в той самий момент, коли ця людина продасть хоча б одну «вирощену» картку за кошти з гаманця, до неї застосовуватиметься те саме речення з § 2.G, що й до оператора, який має десять тисяч таких карток. Отже, Valve залишила за собою право застосувати це порушення фактично до кожного продавця карток на власному ринку, але відмовилася застосовувати його фактично до всіх них. Правило, яке дотримується з такою частотою, не є правилом. Це — варіант. Питання, яке ставить ця виставка, полягає не в тому, чому терплять «фармерів» карток; а в тому, чому така ж міра застосовується до поодинокого користувача, який продає картку, тоді як комерційна економіка карток, яку ці картки живлять — торговельні сервіси, боти для підвищення рівнів, оптові продавці — функціонує відкрито, а одна з її найбільших груп модератується співробітником Valve (§ 08). Порушення застосовується лише до дрібних власників, а для машин від нього відмовляються.\n\n06 — Історія виконання рішень\nБез попередження, хвилями, і це поширюється по номеру телефону\n\nValve включив положення про право на припинення дії угоди без попередження безпосередньо в текст угоди, розмістивши його одразу після пункту про автоматизацію.\n\n«Valve може обмежити або закрити ваш обліковий запис (облікові записи) чи певну підписку у разі будь-якої поведінки чи діяльності, яка є незаконною, становить шахрайство або використання автоматизованих засобів, або порушує Steam Правила поведінки в Інтернеті. Ви визнаєте, що компанія Valve не зобов’язана попереджати вас перед припиненням дії вашої підписки (підписок) та/або облікового запису.\"\n\n— Steam Договір про підписку, § 4.D ↗ архів 2026-09-24 ↗ · перевірено дослівно 2026-09-22\n\n1,000+ боти · заборона на торгівлю. «Схоже, цей обліковий запис використовувався для управління мережею бот-акаунтів. Використання ботів є порушенням Угоди з абонентом Steam».\n\nПонад 170 ботів · назавжди заблоковано, зимовий розпродаж 2017 року. «Цей обліковий запис використовувався для незаконного збору колекційних карток на Steam, а також для пов’язаної з цим діяльності, що не обмежувалася лише комерційною. Обліковий запис було назавжди заблоковано, і служба підтримки Steam не може надати додаткову допомогу з цього питання».\n\nПонад 120 ботів · назавжди заблоковано. «Цей та інші облікові записи використовувалися для перевантаження нашої мережевої інфраструктури, що є порушенням правил поведінки в Інтернеті Steam».\n\n— Steam Повідомлення служби підтримки, наведені в ArchiSteamFarm розділі «Чи когось за це заблокували?» розділу «Часті запитання». Джерело ↗ · перевірено дослівно 2026-09-22\nВипадок 4 — червень 2025 року, VAC заборони на виведення з експлуатації CS2\n\nУ власному трекері проєкту зафіксовано випадок, що стався пізніше за три вищезазначені: акаунти, які лише запускали Counter-Strike 2 у режимі бездіяльності за допомогою цього інструменту, отримали VAC заборони — у сенсі боротьби з шахрайством, а не в адміністративному сенсі. Позиція розробника полягає в тому, що простоювання не може спричинити такого, оскільки воно «не робить нічого іншого, крім як повідомляти Steam, що ми граємо в певну гру». Причина цього є спірною. А ось те, що ці акаунти було заблоковано, — ні.\n\n— ArchiSteamFarm обговорення № 3440, відкрито 26 червня 2025 року ↗ · прочитати 2026-09-22\n\nЯк гине основний обліковий запис\n\nУ цій же гілці обговорення один із учасників проєкту описує правило поширення інформації: акаунти можуть бути заблоковані «по ланцюжку», якщо вони використовують один і той самий номер телефону — «Це може бути лише одна заборона VAC, яка поширюється на «чисті» акаунти, пов’язані із заблокованим».\n\nSteam Guard вимагає введення номера телефону. «Ферми» створюються на основі номера телефону оператора. Тому заходи з боротьби з порушеннями не обмежуються одноразовими обліковими записами: вони простежують спільний ідентифікатор аж до облікового запису, який містить бібліотеку, список друзів та інвентар. Саме так один із учасників проєкту описує механізм, за яким одна дія призводить до видалення основного облікового запису оператора разом із фермою — і саме тому втрати під час хвилі боротьби з порушеннями не вимірюються в $5 облікових записах. (Описано учасником проєкту в обговоренні ASF на GitHub № 3440; офіційного підтвердження Valve чи офіційного прецеденту в архівах немає.)\n\nОдин і той самий абзац, написаний з інтервалом у п’ять років трьома різними агентами\n\nПоложення, згідно з яким ведення сільського господарства вважається порушенням — тобто комерційне використання особистої, некомерційної ліцензії — не стосується виключно фермерських господарств. Це стандартна причина, яку Steam наводить при закритті облікового запису через торгівлю, і ця причина надходить у вигляді шаблону. Нижче наведено три приклади, опубліковані людьми, які отримали їх з інтервалом у п’ять років від трьох різних зазначених агентів.\n\nПовідомлення від служби підтримки Steam 29 вересня о 19:56\n\n«Акаунт, з якого ви пишете, було заблоковано за порушення умов Угоди з користувачем Steam. На підставі даних про торгові операції, повідомлень від спільноти та інших факторів було встановлено, що цей акаунт використовувався в комерційних цілях.\n\nЦя блокування є постійним, і Steam Служба підтримки не може надати вам подальшу допомогу з цього приводу.\n\nОскільки ми надали всю інформацію, якою володіємо, я закриваю цей запит на допомогу. Зверніть увагу, що ви більше не отримаєте відповідей щодо цього питання.\n\nЗ повагою,\n«Хал»\n\nЦей запит на допомогу було закрито.\n29 вересня 2020 року. Опубліковано одержувачем із коментарем «RIP Trading». — @gergelyszabo94 ↗\nПовідомлення служби підтримки Steam 12 липня о 22:41\n\n«Акаунт, з якого ви пишете, було заблоковано за порушення умов Угоди з користувачем Steam. На підставі даних про торгові операції, повідомлень від спільноти та інших факторів було встановлено, що цей акаунт використовувався в комерційних цілях.\n\nЦя блокування є постійним, і Steam Служба підтримки не може надати вам подальшу допомогу з цього питання.\n\nОскільки ми надали всю інформацію, якою володіємо, я закриваю цей запит на допомогу. Зверніть увагу, що майбутні запити на допомогу, подані щодо блокування облікового запису, можуть бути закриті без відповіді.\n\nSteam Підтримка\n«Відео»\n\nЦей запит про допомогу було закрито.\n12 липня 2024 року, португальський інтерфейс. Адресат — професійний гравець у CS2: «Я вже звернувся до служби підтримки Steam, але отримую лише автоматичні відповіді… Не можу грати в Faceit, а також не можу брати участь у професійних матчах». — @prcs25 ↗ архів 2024-07-15 ↗\nЦитата з допису користувача r/steamsupport\n\n«Доброго дня! Акаунт, з якого Ви пишете, було заблоковано за порушення умов Угоди з підписником Steam. На підставі даних про торгові операції, повідомлень від спільноти та інших факторів було встановлено, що цей акаунт використовувався в комерційних цілях.\n\nЦя блокування є постійним, і Steam Служба підтримки не може надати вам подальшої допомоги з цього приводу.\n\nОскільки ми надали всю інформацію, якою володіємо, я закриваю цей запит на допомогу. Зверніть увагу, що майбутні запити на допомогу щодо блокування облікового запису можуть бути закриті без відповіді.\n\nSteam Підтримка\n«Саллі»\n\nОтримано тричі, у відповідь на три окремі запити.\n29 березня 2025 року. Автор не оскаржував блокування — його обліковий запис було викрадено разом з електронною поштою, і він просив надати йому доступ: «Я не запитую про блокування і не оскаржую його, я просто хочу отримати доступ до свого облікового запису Steam… Valve надають мені одну й ту саму відповідь, скопійовану та вставлену, на кожен запит, а потім закривають запит». — r/steamsupport ↗, що містяться у власному корпусі скарг цього розслідування\n\nСлово за словом, кома за комою, протягом п’ятдесяти п’яти місяців, за участю трьох агентів та двох мов взаємодії. Єдина правка в усьому тексті — це уточнення в останньому реченні щодо періоду між 2020 та 2024 роками, з «Ви більше не отримаєте відповідей» до «Майбутні запити про допомогу… можуть бути закриті без відповіді». Яким би не був процес, що призвів до цих рішень, цей лист не є його відображенням. Зазначеними підставами є «торгівля, повідомлення громадськості та інші фактори» — категорія, звіт невідомого походження та невизначена решта.\n\nЩе п’ять випадків, зібраних таким самим чином. Перші три належать до однієї категорії та мають однаковий результат; останні два — це відповіді одного й того самого відділу, що стосуються різних правил, викладені однаковими словами:\n\nДата\tЩо зробив цей акаунт\tЩо сталося\tДжерело\n04.12.2021\tКупівля та продаж на Buff — «Я не робив нічого іншого, крім купівлі та продажу на Buff, тобто P2P-торгівлі»\tЗаборона спільноти: відсутність ринку, відсутність торгівлі, замороження дорогих запасів\tr/csgomarketforum ↗ архів 2025-03-27 ↗\n06.12.2021\tОдносторонні P2P-обміни через Buff та Bitskins для придбання комплектацій та обміну на кращі\tПостійний замок для комерційного використання та замок для загального користування: «Застряг у режимі «псевдоневидимості»… Мій профіль також застряг у приватному режимі»\tr/GlobalOffensiveTrade ↗ архівувати 2021-12-06 ↗\n20.12.2024\tАкаунт існує з 2017 року, тисячі годин; торгує на платформах спільноти, обмінюючи тематичні набори спорядження та покращуючи їх\tПостійна блокування з колективним блокуванням, без попереднього попередження чи зарахування штрафних балів; підтримка «заявляють, що їхнє рішення є остаточним», відповіді надсилаються автоматично\tr/csgomarketforum ↗ архів 2025-06-27 ↗\n23.12.2024\tКористувач, який повернувся, поповнив гаманець після річної перерви, скориставшись VPN «лише для загальної безпеки в Інтернеті»\tПостійна заборона доступу до спільноти з причина взагалі не вказана: «Заборона є постійною, і вони не можуть надати додаткову інформацію, а подальші звернення можуть бути закриті без відповіді». 196 лайків, 340 відповідей\tr/steamsupport ↗\n04.08.2026\tБагаторічні покупки в Ірані; автор заявляє, що ніколи не публікував дописів, ніколи не користувався «Маркетом» і ніколи не відвідував форуми\tДоступ для спільноти заблоковано до 2038 року понад «регіони, щодо яких введено санкції»; заявку закрив оператор на ім’я Азул. Повернення коштів з того самого облікового запису з тієї самої іранської IP-адреси було затверджено роком раніше. Бібліотека та гроші залишаються у Valve.\tr/pcgaming ↗\n\nОстанній рядок відрізняється від решти — йдеться про дотримання санкцій, а не про комерційне використання — і його включено, оскільки форма відповіді ідентична: категорія, відсутність доказів, відсутність можливості оскарження, закритий запит. Крім того, він порушує питання, якого немає в інших випадках. Якщо обслуговування цього рахунку було незаконним, то й прийом платежів протягом багатьох років також був незаконним. Одна з цих двох позицій має бути хибною, і лише одна з них обійшлася клієнту в будь-які витрати.\n\nУсі вісім повідомлень було прочитано на 2026-09-22 — нитки за 2021 рік та грудень 2024 року через знімки з Internet Archive, а решту — через загальнодоступний інтерфейс Reddit, оскільки Reddit відмовився виконувати прямі запити від хостингу, що здійснював збір даних. Два листи за 2020 та 2024 роки транскрибовано зі скріншотів, доданих до оригінальних дописів, які досі доступні. У рамках цього розслідування жоден із цих акаунтів не вважається ані невинним, ані винним у чомусь — саме в цьому й полягає суть. Ні читач, ні регулятор не зможуть це зрозуміти з листа.\n\nПримітка щодо джерел даних — втрати на рівні операторів\n\nОператори, опитані в рамках цього дослідження, повідомляють про збитки в розмірі від п’яти до десяти тисяч облікових записів у кожному під час окремих етапів виконання, при цьому основні рахунки велося разом із господарством. Ця агітаційна кампанія зафіксована тут як звіт від першоджерела, а не як результат. Для цього показника не опубліковано розмір вибірки, не встановлено фіксовану дату збору даних, не передбачено перевірку за кожним рахунком, і жодне інше число на цій сторінці не залежить від нього; два рядки в розділі 02, які базуються на ньому, позначені відповідним чином.\n\nЦе стверджується, а не залишається без уваги, з двох причин. Зазначений вище механізм заборони ланцюгів є задокументованим поясненням саме цієї закономірності. А регулятор може вимагати від Valve надати той єдиний запис, який би вирішив це питання: скільки рахунків було заблоковано в рамках автоматизації, в яких хвилях, і скільки кожен із цих рахунків витратив у магазині до його закриття. Доки цей запис не з’явиться, цифра залишається такою, як є — повідомленою, приписаною та недоведеною.\n\n07 — Асиметрія\nОбидві сторони одного столу\n\nПорівняйте цей стандарт доказування зі стандартом Valve, що застосовується до її власної операції з надання підтримки. У правій колонці наведено реєстр інцидентів із цього досьє, відтворений із тими ж застереженнями, що містяться в оригіналі.\n\nКлієнт, для торгівлі\n\nВісім задокументованих випадків, 2020–2026 рр.\n\nПоведінка\nПродаж або купівля товарів на сторонніх торговельних майданчиках; в одному випадку ніяких дій взагалі не було — обліковий запис було викрадено.\nНаведені докази\nНемає. «На основі даних про торги, повідомлень спільноти та інших факторів».\nПовідомлення\nНемає. Valve зазначено в § 4.D: «Valve не зобов’язана попереджати вас перед припиненням дії договору».\nАпеляція\n«Ця блокування є постійним, і Steam Служба підтримки не може надати вам подальшу допомогу з цього питання».\nКвиток\nСправа закрита після першої відповіді. Подальші запити \"може бути закрито без відповіді\".\nДіапазон\nПрофіль, список друзів, чат, «Маркет», інвентар та всі предмети, придбані за реальні гроші.\nТривалість\nПостійний.\nАвтоматизований парк ботів для обробки великих обсягів\n\n694,673 комплектів у відкритому запасі у 91 ботах\n\nПоведінка\nОдночасне виконання автоматизованих скриптів у режимі «headless» на тисячах облікових записів для виведення карток у неактивний стан, масового створення значків та обміну наборами в промислових масштабах.\nНаведені докази\nВідкриті каталоги ботів (steam.supply, SteamLvlUp) та публічні групи з мільйонами учасників.\nПовідомлення\nЖодного втручання. 88.97% не передбачають жодних заборон; 99.8% із решти заборон мають суто косметичний характер.\nАпеляція\nУ цьому немає потреби. Флоти безперебійно функціонують протягом багаторічного життєвого циклу.\nКвиток\n—\nДіапазон\nНеобмежений обмін інвентарем, прокачування значків та ліквідність ринку.\nВигода до Valve\n$26.8M+ у вигляді мінімальної суми покупок у магазині ($5.00 вхідних воріт на кожен обліковий запис) плюс 15% відрахування за транзакції на «Community Market».\nОтже, питання, яке при цьому виникає, якщо сказати просто:\n\nПриватний користувач, який вручну торгує картками чи предметами, підлягає постійній забороні без права оскарження відповідно до § 4.C (автоматизація) або § 2.G (комерційне використання). Автоматизований флот для фармінгу, що використовує безлюдні боти на тисячах акаунтів, працює відкрито з показником «88.97%» (без порушень). Valve є бенефіціаром обох.\n\nАсиметрія має економічний характер: окремі трейдери отримують прибуток від платформи, тоді як автоматизовані парки карток вливають мільйони в систему обробки витрат у магазині Valve ($5.00 на кожен обліковий запис) та збільшують комісію за транзакції під час кожного перепродажу. Контроль за дотриманням правил не здійснюється згідно з письмовими правилами, а виходить із моделі отримання доходу.\n\n08 — Управління\nХто регулює економіку карт\n\nПовторюваний висновок цього досьє — про те, що рівень сторонніх учасників навколо Steam укомплектований зсередини Steam — справедливий і для карткової економіки, і він призводить до конкретного висновку: жодна незалежна особа не може оцінити, що насправді робить служба Valve з забезпечення дотримання правил, оскільки сторона, здатна це оцінити, перебуває всередині цього рівня. Усі наведені нижче факти були отримані з власних публічних груп та профілів Valve на 2026-09-22 і можуть бути відтворені будь-ким у браузері.\n\nСпівробітник із Valve керує найбільшою групою з обміну картками Valve співробітник\n\nCardTrades ↗ у власному заголовку описує себе як «Steam Офіційна група „Card Exchange“» і несе 97,114 учасників. Модератори, зазначені в списку — акаунти, які керують цією групою, — це Мікмейн, Сержант Фоппер та afarnsworth ↗.\n\nЦей останній профіль у розмітці самого сайту Valve позначений як співробітник Valve — на сторінці вказано class=\"profile_header_valve_employee\" — вказує своє місцезнаходження як Белв'ю, штат Вашингтон, і належить до Valve, Steam та Steam Група колекційних карток групи. SteamID64 76561197960434622, член організації з 12 вересня 2003 року.\n\nЦе зауваження має структурний, а не особистий характер, і воно не щодо автоматизації — модератор групи з обміну картками не використовує бота, і ніщо тут не вказує на протилежне. Справа в тому, що в пункті розділ 07. Steam Card Exchange — це сторонній сервіс з торгівлі картками; торгівля картками через сторонні сервіси є саме тією дією, за яку Valve назавжди блокує звичайні облікові записи згідно з «використовується в комерційних цілях з урахуванням обсягів торгівлі, звітів спільноти та інших факторів». Співробітник Valve обіймає посаду модератора в офіційній спільноті цього сервісу, яка налічує 97 тисяч учасників.\n\nУ даному випадку проти жодної особи не висунуто жодних звинувачень у вчиненні правопорушень, і не робиться жодних висновків щодо того, що саме передбачає ця роль. Асиметрія полягає в наступному: коли звичайний обліковий запис пов’язаний із сторонньою карткою або сервісом «скін», відповіддю є закриття квитка та постійна блокада без надання доказів; коли ж йдеться про цей сервіс, співробітник Valve входить до списку модераторів, і ця домовленість відображається на сторінці, яку публікує сам Valve. Питання полягає в тому ж, що й у всіх інших частинах цього досьє: надайте письмове дозвіл, якщо він існує — а якщо він не потрібен, повідомте про це письмово, оскільки восьми особам у розділі 06 було сказано протилежне.\n\nРівень списку заборонених і хто ним керує Модератор-волонтерСторонній сервіс\n\nГрупа Steambans.com (архів) ↗ (наживо ↗ архів 2025-12-03 ↗) описує своє походження у збереженому описі групи: «Офіційна спільнота Steambans.com Steam. SteamBans.com — це абсолютно новий сервіс, заснований на старій концепції. Глобальні списки банів вже багато років використовуються в старій програмі WONID від VALVe. Коли відбувся перехід на STEAMID, для нас стало цілком природним розробити сервіс, спеціально орієнтований на цю нову систему. Але ми також прагнули більшого. *. Архівна сторінка сайту Steambans, який припинив роботу у 2013 році». До переліку його адміністраторів входять devicenull та killahinstinct_ ↗.\n\nЦей обліковий запис адміністратора — це не працівник з позначкою «a Valve» — у нього немає позначки «працівник». Це волонтер із надзвичайно високим статусом: член Модератори спільноти (414 учасників, описана як група «Створено модераторами спільноти Steam»), з Координатори Вікі, з Steam Громадський ринок, а також групи, пов’язані з програмою Valve та попередніми релізами, зокрема: Valve Трубопровід, Steam Бета-версія для клієнтів, Бета-версія Mobile Auth, Нова бета-версія для спільноти Steam, Steam Лабораторії, Steamworks та Повідомити про шахрайські URL-адреси. SteamID64 76561197960794555.\n\nТакож у межах цього кола та з відображенням Steambans безпосередньо у списку учасників його публічної групи: msart ↗ (список учасників групи ↗), SteamID64 76561197977933359, у профілі якого зазначено такими словами: «Я керую сайтом steamid.uk та багатьма іншими сайтами, пов’язаними та не пов’язаними зі Steam», і який керує об’єднаною мережею з шістнадцяти груп — SteamIDcouk (основна група «Веб-сайт Sid»), SidAdmins, SidBans, steamideu, Steam3ID, s-id та SArchive серед них.\n\nСам сайт steamid.uk вказує ту саму цифру. У розділі «Часті запитання» зазначено: «Хто створив SteamID? Веб-сайт SteamID, мережева інфраструктура та системи безпеки перебувають під управлінням 76561197977933359». У двох наступних відповідях вказано, звідки беруться ці дані: «SteamID для збору даних використовує переважно веб-API Steam.» На цій же сторінці описано низку виділених серверів у різних хостинг-провайдерів, зовнішні сервери для розробки, зберігання даних та текстового пошуку, а також окремий центр резервного копіювання.\n\nПідтверджено на основі збережених записів Інтернет-архіву: Знімок групи «Steambans» від 3 грудня 2025 року ↗, а саме Знімок профілю оператора станом на 14 вересня 2024 року ↗, а також Знімок екрана з розділу «Часті запитання» сайту steamid.uk від 1 квітня 2026 року ↗, збіжні дані, зчитані безпосередньо з 2026-09-22.\n\nЩо з цього випливає, а що — ні\n\nСписки заборон, визначення SteamID та обмін картками — це три сервіси, які визначають, кому можна довіряти, кого можна ідентифікувати та скільки коштує той чи інший предмет. Жоден із цих трьох сервісів не управляється Valve. На кожному з них люди, які керували кораблем, прибули з-за меж орбіти Valve: позначений Valve співробітник у списку модераторів офіційної групи сервісу карток; досвідчений Valve модератор спільноти, який має доступ до програми до її офіційного випуску та адмініструє групу списку заблокованих користувачів; сервіс ідентифікації, яким керує одна приватна особа, що належить до того самого кола. Три сервіси, три площини контролю, три особи Valve, яким вже надано відповідний статус.\n\nЧленство в групі не є працевлаштуванням, і це аж ніяк не є звинуваченням. Це факт у сфері державного управління, і саме це є причиною того, що звичайний аргумент на захист — це сторонні організації, ми не можемо їх контролювати — це потрібно перевірити, а не просто прийняти на віру. Люди, які керують процесом, добре знайомі з Valve. Valve може сказати, чого саме, якщо взагалі чогось, воно від них вимагало; ніхто ззовні не має можливості це з’ясувати.\n\nНіхто не веде підрахунок. Ось який висновок.\n\nПростір ідентифікаторів Steam — це суцільний діапазон цілих чисел. Проходження цього простору та зведення даних про те, скільки облікових записів заблоковано, скільки обмежено та скільки товарів перебуває під торговою забороною, — це не дослідницька програма, а просто цикл і ключ API. Valve сам видає цей ключ на steamcommunity.com/dev/apikey. І все ж Жодна незалежна організація не оприлюднює даних цього перепису. Ні регулятор, ні журналіст, ні науковець, ні організація споживачів. Єдині оприлюднені дані щодо масштабів заходів з забезпечення дотримання законодавства щодо Steam — це ті, про які вирішила згадати Valve.\n\nЦя можливість не відсутня. Вона просто прихована. Сервіс, який обробляє та індексує простір ідентифікаторів у великих обсягах — steamid.uk — у своєму розділі «Часті запитання» зазначає, що він «в першу чергу використовує веб-API Steam для збору даних» і працює на базі декількох виділених серверів, зовнішніх сховищ даних, машин для текстового пошуку та окремого центру резервного копіювання. Цим проектом керує одна приватна особа. Група «побратимів» зі списку заблокованих користувачів спільно адмініструється модератором спільноти Valve, який має багаторічний стаж роботи та доступ до попередніх версій програм Valve. Єдина сторона, яка має можливість оприлюднити результати підрахунку, перебуває в орбіті Valve, але не оприлюднює їх.\n\nТака сама структура спостерігається, як зазначається в досьє, і в усіх інших випадках. Кожна служба, яка приймає рішення, що мають вирішальне значення для економіки Steam — кому довіряти, кого можна ідентифікувати, скільки коштує той чи інший товар, кому заборонено доступ — номінально є сторонньою, але фактично тісно пов’язана з Valve. Steam «Обмін картками» не є винятком із цієї закономірності; це ще один її приклад. Аргумент про те, що це незалежні оператори, може бути використаний для Valve саме тому, що нікому ще не вдалося перевірити його на конкретному числі.\n\nПерепис 10,88 млн облікових записів: 88.97% Непереглянуті\n\nБаза встановлених пристроїв ArchiSteamFarm була перевірена у компаніях Valve GetPlayerBans кінцева точка (10,880,610 облікових записів, 55 хвилин). Сама лише необмежена підмножина становить $26.8M+ щодо мінімальної суми витрат у магазині (поріг входу $5.00). 9,680,599 облікових записів (88.97%) не мають жодних обмежень, а 99.8% із решти мають лише символічні заборони від спільноти, які не заважають роботі автоматизованої торгівлі.\n\n5,360,499Члени ASF без обмежень (кількість, що відображається як Steam)\n10,880,610Загальна кількість перевірених записів API (з обмеженнями та без обмежень)\n9,680,599Ніколи не блокували (88.97%)\n1,200,011Має будь-яку заборону Steam (11.0%) — 99.8% косметичний\n55 хвЩоб провести перепис усього населення, потрібно одне ключове\nКриміналістичні докази та глибокий перепис населення\n\nДетальний демографічний аналіз — включаючи діаграми розподілу за типами блокувань, вік облікових записів на момент застосування санкцій, групи за роком створення (2020–2026) та географічні дані, надані самими користувачами, — опубліковано в спеціальному дослідженні за результатами перепису.\n\nВідкрити повний перелік заборон обсягом 10,88 млн (Додаток VI) →Розділ 4 — Блокування ідентифікатора активу →\n\nОтже, питання, яке слід поставити, і на яке може відповісти лише Valve: який саме ідентифікатор або повноваження було скасовано, в який день, за чиїм рішенням, та який вимірюваний вплив це мало на операторів, на яких воно було спрямовано — на тлі того, як це вплинуло на всіх, хто перебував зовні й намагався провести підрахунок. Зміна, що скасовує незалежний аудит, не стає нейтральною лише тому, що її було оголошено як захід безпеки. Саме це є причиною того, що перепису населення, про який йшлося у попередньому абзаці, не існує.\n\n09 — Метод та обмеження\nЩо було прочитано, а що не стверджується\n\nКожна цитата на цій сторінці була взята з активного джерела на 2026-09-22 і відтворена дослівно. Жодна інформація тут не походить зі скрейпінгу, облікових даних торговельних майданчиків чи приватних наборів даних.\n\nЧотири набори даних та обчислення з ними\n\nКожен із них — це окремий публічний запит, який можна відтворити з терміналу. Не використовувався жоден обліковий запис, не здійснювався вхід на жодний маркетплейс і не викликався жоден кінцевий пункт, що вимагає введення облікових даних.\n\nНабір даних\tЗвідки це взялося\tЩо було обчислено на основі цього\nПерепис карток\n13,876 ігор\tSteam Опублікований Card Exchange прайс-лист на бейджі — той самий канал даних, на основі якого відображаються їхні сторінка з публічними цінами ↗ архів 2026-08-04 ↗\tІгри, в яких випускаються картки, кількість карток у наборі, окремі типи карток та ринкова ціна кожного готового набору. Медіани та загальна сума $23,586.57 є арифметичними показниками цього дослідження.\nЦіни на ігри\n13,713 вирішено\tВласна публічна точка доступу магазину Valve, store.steampowered.com/api/appdetails, копія: США, лише поле ціни, партіями\tМедіана та розподіл рекомендованої ціни на настільну гру; кількість ігор, готовий набір яких продається краще, ніж сама гра.\nЗапас ботів\n91 ботів, 694,673 наборів\tПублічний каталог карт-ботів за адресою steam.supply/CardBots ↗, читається так, як відображається, без входу в систему\tЗагальна кількість наборів на складі, мінімальна кількість карток, мінімальний ліміт вилучення та мінімальний ліміт розподілу між ботами для окремих облікових записів.\nПеревірка\n21 спільних ботів\tsteamlvlup.net/cardbots ↗ архів 2026-02-10 ↗, незалежний каталог цих самих ботів\tТільки для перевірки. Щодо 21 бота, які вказані в обох списках, Aggregate Stock погоджується на 0.03%; найбільша розбіжність, пов’язана з одним ботом, становить 1.36%, що відповідає результатам двох обходів актуального асортименту, проведених з інтервалом у кілька хвилин.\n\nВказівка джерела, як того вимагає другий каталог: дані надані SteamLvlUp, на умовах ліцензії CC BY 4.0 архів 2026-09-23 ↗; використовується тут виключно як незалежна перевірка даних про запаси третьої сторони, причому дані були модифіковані таким чином, що рядки за кожним ботом були зведені та порівняні, а не відтворені. Steam Card Exchange та steam.supply зазначені вище за посиланням. Ціни на ігри вказані Valve. Назви та зображення карт, ігор та наборів належать Valve або видавцям і відтворені без будь-яких претензій чи ліцензій як факти про ринок.\n\nДва заплановані вимірювання не було проведено, і їх не замінено. Власні кінцеві точки «Community Market» від Steam — огляд цін, пошук/відображення, історія цін — не повертають жодних даних хосту-збирачу, а Steam сторінки обговорення спільноти повертають йому код HTTP 403, тому жодні дані на цій сторінці не базуються на актуальних даних Market. Метод підрахунку обсягу продажів, який би враховував кількість отриманих карток під час щоденного оновлення, вимагає сеансу, в якому користувач Steam увійшов у систему; У протоколі цього розслідування зазначено, що жодних облікових даних торговельної платформи не використовувалося, і ця інформація була збережена. Мінімальна ціна акцій — це та ціна, яку можна визначити без урахування впливу ботів.\n\nПершоджерела\n\nSteam Угода з абонентом ↗ архів 2026-09-24 ↗ — § 2.A, § 2.G, § 3.D, § 4.C, § 4.D.\nSteam Підтримка — Обмежені облікові записи користувачів ↗ — поріг $5.00 та перелік обмежених ознак.\nValve — Steam Часті запитання щодо колекційних карток ↗ — відмовитися від механіки випадання предметів та моделі «грай безкоштовно» $9.\nArchiSteamFarm Поширені запитання ↗ та обговорення № 3440 ↗.\nSteam Сторінки груп та профілів у спільноті, для безпосереднього перегляду, для розділу 08.\nЧасті запитання на сайті steamid.uk, знімок з Інтернет-архіву 2026-04-01 ↗.\nВісім Steam повідомлень про блокування підтримки, опублікованих їхніми одержувачами у 2020–2026 роках, перелічені разом із посиланнями на них у розділі 06.\n\nЩо не є предметом заявки\n\nОцінка доходу від «кард-фармінгу» для Valve не наводиться. Кількість активних облікових записів для жодного інструменту не вказується, а 1,39 мільйона дозволів на дроп є не кількість облікових записів, що належать фермі — див. примітку в розділі 02. Жодна особа не звинувачується у правопорушеннях; якщо згадується ім’я особи, то це відбувається під її власним публічним Steam ніком, у її власній публічній ролі, зі сторінки, яку публікує Valve. Жоден із восьми заблокованих акаунтів у розділі 06 не визнається невинним чи винним; висновок стосується листа, а не самого акаунта. Дані щодо втрати операторів у розділі 02 є даними від першоджерела та позначені як такі на примітка щодо джерел постачання. Цитата з розділу «Часті запитання» сайту steamid.uk взята зі знімка Інтернет-архіву, оскільки доступ до активної сторінки обмежений системою перевірки на ботів. Не стверджується, що будь-які спроби проведення перепису заблокованих користувачів були зроблені та придушені — констатується лише те, що жодних даних не опубліковано. Крива рівня Steam вище 667 не моделюється.\n\nЧому інструмент не є предметом\n\nArchiSteamFarm зазначає, що це \"не санкціоновано Valve\" і на цій сторінці їй нічого не закидають. Вона використовується як вимірювальний інструмент, оскільки є єдиною стороною в цій економіці, яка публічно та в письмовій формі документує механізми функціонування. Valve може викласти всю суть у одному абзаці: опублікувати, яку комерційну автоматизацію вона схвалює, та звіт за кожним оператором про те, що було зроблено щодо решти.\n\nЧитайте далі: як формується ціна самого ринку → · цінова шкала та обмеження на кількість пропозицій → · товари з кодом Steam не будуть поставлятися →",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "«Ферма ботів» — це не протікання у магазині Valve. Це — клієнт."
          },
          {
            "level": 2,
            "id": null,
            "text": "Що таке ферма насправді: покроковий опис"
          },
          {
            "level": 3,
            "id": null,
            "text": "Приєднатися"
          },
          {
            "level": 3,
            "id": null,
            "text": "Купити ігри"
          },
          {
            "level": 3,
            "id": null,
            "text": "У режимі очікування\nЦей інструмент безінтерфейсно входить в мережу Steam від імені облікового запису, \"аналізує ваші значки\", формує список ігор, у яких можна заробляти ресурси, і запускає «грати у відповідну гру та періодично перевіряти, чи вже повністю пройдено гру». Опис механізму, наданий його розробником: він «не робить нічого іншого, крім як повідомляти Steam, що ми граємо в певну гру»."
          },
          {
            "level": 3,
            "id": null,
            "text": "Краплі закінчилися\nКожен заголовок є скінченним. «У кожній грі передбачена фіксована кількість карт, які можна отримати. Як тільки ви отримаєте їх усі (приблизно половину повного набору), гра більше не є перспективною для фарму». Ферма, яка хоче продовжувати виробництво, мусить постійно купувати картки. Постачання карток обмежується обсягом покупок — це передбачено механізмом гри і грає на користь Valve."
          },
          {
            "level": 3,
            "id": null,
            "text": "Виведення коштів\nКартка виходить через одні з трьох «дверей»: продається на «Ринку спільноти», обмінюється або переробляється на самоцвіти. Кожен із цих випадків є транзакцією на «Ринку передплатників» або обміном, і у § 3.D передбачено стягнення плати: «Valve може стягувати комісію за транзакції на ринку підписок». Саме цей крок і робить усе це порушенням — див. 05."
          },
          {
            "level": 2,
            "id": null,
            "text": "Перш ніж ферма заробить хоч один цент, вона вже виплатила Valve"
          },
          {
            "level": 3,
            "id": null,
            "text": "Який насправді розмір того, що купується"
          },
          {
            "level": 3,
            "id": null,
            "text": "Який розмір має набір"
          },
          {
            "level": 3,
            "id": null,
            "text": "Скільки коштує ліцензія"
          },
          {
            "level": 3,
            "id": null,
            "text": "Що повертає готовий набір"
          },
          {
            "level": 3,
            "id": null,
            "text": "Де розташовані набори 694,673"
          },
          {
            "level": 3,
            "id": null,
            "text": "Що цей текст говорить, а що — ні"
          },
          {
            "level": 3,
            "id": null,
            "text": "А сільське господарство не окупається за цінами Valve"
          },
          {
            "level": 3,
            "id": null,
            "text": "Що насправді підтримує ферма"
          },
          {
            "level": 4,
            "id": null,
            "text": "Продажі ігор"
          },
          {
            "level": 4,
            "id": null,
            "text": "«Онлайн» та ігри"
          },
          {
            "level": 4,
            "id": null,
            "text": "Реєстрації"
          },
          {
            "level": 4,
            "id": null,
            "text": "Гроші на гаманці та комісії"
          },
          {
            "level": 4,
            "id": null,
            "text": "Steam-рівень PR"
          },
          {
            "level": 3,
            "id": null,
            "text": "А сам вивід коштів — це втрата вартості: Valve — подвійне оподаткування"
          },
          {
            "level": 3,
            "id": null,
            "text": "Це не просто миттєве явище. Це галузь, що має багаторічну основу."
          },
          {
            "level": 3,
            "id": null,
            "text": "Повні набори карток, що зберігаються у загальнодоступному каталозі ботів, за Steam продажів"
          },
          {
            "level": 3,
            "id": null,
            "text": "Як виглядає «драбинка значків» одного відділу продажів, якщо дивитися зверху"
          },
          {
            "level": 3,
            "id": null,
            "text": "І цей самий асортимент товарів доступний навіть тоді, коли акції не проводяться"
          },
          {
            "level": 3,
            "id": null,
            "text": "Каталог зберігання, для кожного бота окремо"
          },
          {
            "level": 2,
            "id": null,
            "text": "Інший елемент — це число, що стоїть поруч із вашим ім’ям"
          },
          {
            "level": 3,
            "id": null,
            "text": "Використані повні набори, рівень від 1 до 1,000"
          },
          {
            "level": 3,
            "id": null,
            "text": "Як перевірялася крива, оскільки Valve її не публікує"
          },
          {
            "level": 2,
            "id": null,
            "text": "У цьому пункті сільське господарство не описується в загальних рисах. У ньому наведено його перелік."
          },
          {
            "level": 3,
            "id": null,
            "text": "«…час ігор»"
          },
          {
            "level": 3,
            "id": null,
            "text": "«…без реального врахування думки користувачів»"
          },
          {
            "level": 2,
            "id": null,
            "text": "Кожен вихід із картки, що використовується в рамках програми, є виходом, який заборонено ліцензією, — і Valve стягує плату на вході"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 2.A — ліцензія"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 2.G — обмеження"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 3.D — плата"
          },
          {
            "level": 3,
            "id": null,
            "text": "Прочитайте ці три пункти разом — і позиція закривається"
          },
          {
            "level": 3,
            "id": "fee-ladder",
            "text": "Вартість проходу через ці ворота не становить 15%. На карті з фермою вона сягає двох третин."
          },
          {
            "level": 3,
            "id": null,
            "text": "Фактична комісія за продаж на ринку «Спільнота» залежно від ціни, запропонованої продавцем"
          },
          {
            "level": 2,
            "id": null,
            "text": "Без попередження, хвилями, і це поширюється по номеру телефону"
          },
          {
            "level": 3,
            "id": null,
            "text": "Випадок 4 — червень 2025 року, VAC заборони на виведення з експлуатації CS2"
          },
          {
            "level": 3,
            "id": null,
            "text": "Як гине основний обліковий запис"
          },
          {
            "level": 3,
            "id": null,
            "text": "Один і той самий абзац, написаний з інтервалом у п’ять років трьома різними агентами"
          },
          {
            "level": 3,
            "id": null,
            "text": "Примітка щодо джерел даних — втрати на рівні операторів"
          },
          {
            "level": 2,
            "id": null,
            "text": "Обидві сторони одного столу"
          },
          {
            "level": 3,
            "id": null,
            "text": "Клієнт, для торгівлі"
          },
          {
            "level": 3,
            "id": null,
            "text": "Автоматизований парк ботів для обробки великих обсягів"
          },
          {
            "level": 3,
            "id": null,
            "text": "Отже, питання, яке при цьому виникає, якщо сказати просто:"
          },
          {
            "level": 2,
            "id": null,
            "text": "Хто регулює економіку карт"
          },
          {
            "level": 3,
            "id": null,
            "text": "Співробітник із Valve керує найбільшою групою з обміну картками Valve співробітник"
          },
          {
            "level": 3,
            "id": null,
            "text": "Рівень списку заборонених і хто ним керує Модератор-волонтер Сторонній сервіс"
          },
          {
            "level": 3,
            "id": null,
            "text": "Що з цього випливає, а що — ні"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ніхто не веде підрахунок. Ось який висновок."
          },
          {
            "level": 3,
            "id": null,
            "text": "Перепис 10,88 млн облікових записів: 88.97% Непереглянуті"
          },
          {
            "level": 3,
            "id": null,
            "text": "Криміналістичні докази та глибокий перепис населення"
          },
          {
            "level": 2,
            "id": null,
            "text": "Що було прочитано, а що не стверджується"
          },
          {
            "level": 3,
            "id": null,
            "text": "Чотири набори даних та обчислення з ними"
          },
          {
            "level": 3,
            "id": null,
            "text": "Першоджерела"
          },
          {
            "level": 3,
            "id": null,
            "text": "Що не є предметом заявки"
          },
          {
            "level": 3,
            "id": null,
            "text": "Чому інструмент не є предметом"
          }
        ],
        "links": [
          "https://help.steampowered.com/en/faqs/view/71D3-35C2-AD96-AA3A",
          "https://github.com/JustArchiNET/ArchiSteamFarm/wiki/FAQ",
          "https://steamcommunity.com/tradingcards/faq/",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260924114457/https://store.steampowered.com/subscriber_agreement/",
          "https://steamladder.com/ladder/badges/2861690/",
          "http://web.archive.org/web/20260716205303/https://steamladder.com/ladder/badges/2861690/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/farm-economy-timeline.json",
          "https://store.steampowered.com/charts/",
          "http://web.archive.org/web/20260923183013/https://store.steampowered.com/charts/",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://github.com/JustArchiNET/ArchiSteamFarm/discussions/3440",
          "https://x.com/gergelyszabo94/status/1311004678633795585",
          "https://x.com/prcs25/status/1811893857253982720",
          "http://web.archive.org/web/20240715122902/https://x.com/prcs25/status/1811893857253982720",
          "https://reddit.com/r/steamsupport/comments/1fjmgc5/what_to_do_when_your_steam_account_gets_hacked/mkelm2y/",
          "https://www.reddit.com/r/csgomarketforum/comments/r87owv/psa_my_steam_account_just_got_banned/",
          "http://web.archive.org/web/20250327203008/https://www.reddit.com/r/csgomarketforum/comments/r87owv/psa_my_steam_account_just_got_banned/",
          "https://www.reddit.com/r/GlobalOffensiveTrade/comments/r9xql9/d_recently_received_commercial_ban_for_what_seems/",
          "http://web.archive.org/web/20211206034804/https://www.reddit.com/r/GlobalOffensiveTrade/comments/r9xql9/d_recently_received_commercial_ban_for_what_seems/",
          "https://www.reddit.com/r/csgomarketforum/comments/1hhxx7m/d_permanently_locked_on_steam_for_commercial_use/",
          "http://web.archive.org/web/20250627014045/https://www.reddit.com/r/csgomarketforum/comments/1hhxx7m/d_permanently_locked_on_steam_for_commercial_use/",
          "https://www.reddit.com/r/steamsupport/comments/1hkctwt/permanent_ban_with_no_explanation/",
          "https://www.reddit.com/r/pcgaming/comments/1vf24lu/warning_to_all_gamersexpats_steam_took_my_money/",
          "https://steamcommunity.com/groups/card-trading-card-trades",
          "https://steamcommunity.com/id/afarnsworth",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/groups/steambans",
          "https://steamcommunity.com/groups/steambans",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/id/killahinstinct_",
          "https://web.archive.org/web/20240914124859/https://steamcommunity.com/id/msart",
          "https://steamcommunity.com/id/msart/groups/",
          "http://web.archive.org/web/20260401154714/https://steamid.uk/faq/",
          "https://phishdestroy.io/steam_dossier/uk/enforcement_audit.html",
          "https://phishdestroy.io/steam_dossier/uk/#evidence-blackout",
          "https://www.steamcardexchange.net/index.php?badgeprices",
          "http://web.archive.org/web/20260804200309/https://www.steamcardexchange.net/index.php?badgeprices",
          "https://steam.supply/CardBots",
          "https://steamlvlup.net/cardbots",
          "http://web.archive.org/web/20260210171205/https://steamlvlup.net/cardbots",
          "https://steamlvlup.net/",
          "https://creativecommons.org/licenses/by/4.0/",
          "http://web.archive.org/web/20260923221628/https://creativecommons.org/licenses/by/4.0/",
          "https://phishdestroy.io/steam_dossier/uk/market_economics.html",
          "https://phishdestroy.io/steam_dossier/uk/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/uk/elite_skins.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/uk/card_economy.content.json",
      "export_json_sha256": "0e8ebac4ce27b8f847818ba4711feef2431e4de391f7258746799fc7216cfc56"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "uk/elite_skins.html",
      "language": "uk",
      "title": "Один товар, дві системи ціноутворення — Досьє «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/uk/elite_skins",
      "source_html_sha256": "c248cabd370eca622f2fad0e69d5aa4efbe314c012b7f970e4ea84ab85efb3af",
      "exported_at": "2026-09-29T00:19:26.904Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "register",
            "source": "https://phishdestroy.io/steam_dossier/uk/elite_skins#register"
          },
          {
            "id": "",
            "source": "https://phishdestroy.io/steam_dossier/uk/elite_skins#selected"
          }
        ],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "elite_skins.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/uk/elite_skins.pdf?v=print-20260929-v5",
        "sha256": "bbb7e9ba0f2bda5119dc02e6b3332da2523cd2aecfd361abab51e5f1e6bee929",
        "bytes": 105474,
        "pages": 8
      },
      "integrity": {
        "signed_object": "elite_skins.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "elite_skins.content.json.asc",
        "digest_file": "elite_skins.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify elite_skins.content.json.asc elite_skins.content.json",
          "sha256sum -c elite_skins.content.json.sha256"
        ]
      },
      "content": {
        "text": "ДОДАТОК IV / АРХІТЕКТУРА РИНКУ / 20 ВЕРЕСНЯ 2026\nРеєстр Elite Skins — Максимальна ринкова вартість $1,800\n\nОдин товар. Дві системи ціноутворення.\n\nЩО ДОКАЗУЄ ЦЕЙ РОЗДІЛ\n\nЦей реєстр містить емпіричний перелік усіх категорій скінів CS2, ціна яких перевищує встановлений «Steam» ліміт розміщення на «Community Market» у розмірі $1,800 на п’яти зовнішніх біржах. Він доводить, що 248 підтверджені категорії високого рівня — які представляють 18,394 активних оголошень та $78.6 млн розміщеної ліквідності — 100% відсутні на офіційному ринку Valve. Продавці, які прагнуть отримати справжні ринкові ціни, структурно змушені звертатися до зовнішніх платформ, водночас покладаючись виключно на базові механізми торгівлі Steam.\n\nWhat this means — the Community Market listing ceiling\n\nSteam’s own market refuses a listing above roughly $1,800. A seller may ask less, never more. Items whose market price sits above that line therefore cannot be sold at that price on Steam at all — which is the mechanism that moves those sales to third-party venues while the item itself never leaves Valve’s inventory system.\n\nSection 13 — the off-Steam price gap →\n\n← Повернутися до огляду для керівництва\n\nSteam максимальна ціна товару на Community Market становить приблизно $1,800. На п’яти сторонніх торгових майданчиках, ціни на яких наведено в цьому огляді, 419 Категорії товарів CS2 мають найнижчу поточну ціну продажу, що перевищує цей ліміт, — і 402 з них, 95.9%, взагалі не мають Steam жодних оголошень. Разом вони володіють примірниками, що внесені до списку «18,641», загальною вартістю щонайменше $82.4 млн. Для того щоб ціна вважалася дійсною, необхідна згода ще однієї торговельної платформи, 248 Усі ці категорії підтверджуються — і в кожній з них сайт 100%, відсутній на сайті Steam. «Найдорожче — це наклейка» | Titan (Holo) | Катовіце 2014 на $66,285, котирується на чотирьох торгових майданчиках, розташованих на відстані 5.2% один від одного, і не котирується на жодному з майданчиків Valve. Повний рейтинг, візуалізації та оцінка наведені в атлас цінової шкали.\n\nПереглянути всі записи на сайті «419» ↓Відкрити атлас ↗Ознайомтеся з методом\n248категорії, в яких на двох або більше торгових майданчиках ціна перевищує встановлений верхній ліміт\n18,394екземпляри, виставлені на п’яти торгових майданчиках\n$78.6Mмінімальна вартість цих об’єктів\n100%з них взагалі відсутні на сайті Steam\n\nВиправлення · раніше на цій сторінці була вказана непідтверджена ціна\n\nУ попередній версії цієї сторінки під заголовком «Souvenir AK-47» | «Point Disarray» ціна на одному з торгових майданчиків становила $148,954, тоді як на Steam вона була вказана як $119.. Цей запис стосується лише однієї полиці та одного екземпляра, і жоден інший торговий майданчик не підтверджує цю ціну, тому це скоріше запропонована ціна, а не ринкова, і вона більше не відображається на сторінці. Кожна цифра у заголовку тут тепер обмежується категоріями 248, для яких щонайменше дві торгові платформи незалежно одна від одної встановлюють ціну вище за верхню межу. Сам рядок не було видалено — він все ще є у реєстрі нижче, а оцінка, через яку його було понижено, викладена повністю у атлас цінової шкали.\n\n01 / кошти в активних заявках на купівлю\nМінімальний поріг у доларах, що піддається вимірюванню\n\nДані перераховано на основі ліцензованого знімка cs2.sh для п’яти торгових майданчиків. Це мінімальна сукупна заявлена вартість у визначеній підгрупі, а не обсяг продажів і не оцінка вартості економіки CS2.\n\n248 ПІДТВЕРДЖЕНІ КАТЕГОРІЇ · 18,394 ПЕРЕЛІК ЕКЗЕМПЛЯРІВ · 5 ТОРГОВІ ПЛАТФОРМИ$78.62M\n\nМінімальна сукупна опублікована ціна продажу кожного товару категорії CS2, яку два або більше торговельних майданчиків незалежно один від одного встановлюють вище межі, дозволеної Valve на своєму власному ринку.\n\nЧому це мінімальний рівень, а не приблизна оцінка\n\nДля кожного торгового майданчика ми множимо його найнижчий запитуйте ціну на товар за кількістю екземплярів, зазначених на торговельному майданчику. Кожен другий екземпляр на цій полиці продається за ціною, що дорівнює або перевищує найнижчу запропоновану ціну, тому справжня опублікована вартість є вищою — це випливає з самої структури системи, а не є результатом припущень. Це не є продажем, грошовим потоком чи ринковою оцінкою, і один і той самий фізичний товар може бути представлений на кількох торговельних майданчиках.\n\nПереглянути всі рядки джерела «419» ↗\n★ Спортивні рукавички | Лабіринт із живоплоту (перевірено в реальних умовах)\n$4.68M\nAWP | Гунгнір (новий, з заводу)\n$4.46M\nAWP | Dragon Lore (абсолютно новий)\n$4.34M\n★ Ніж-метелик | Fade (абсолютно новий)\n$4.17M\nAK-47 | Wild Lotus (абсолютно новий)\n$4.16M\n★ Ніж «Метелик» | Doppler (абсолютно новий)\n$3.64M\n\nСтовпчики відображають шість найбільших внесків на рівні категорій у розрахунок мінімальної ціни, масштабовані відносно найбільшого значення. Високий стовпчик відображає як найнижчу ціну продажу, так і кількість виставлених екземплярів. Один і той самий фізичний товар може бути представлений на кількох торгових майданчиках, тому ці цифри не слід додавати до загальних показників будь-якого іншого ринку.\n\n02 / приклади, які можна перевірити\nЩо не враховується в цьому обмеженні\n\nІлюстрації відповідають точним назвам предметів, якщо такі є. Ціни — це актуальні запитувані ціни з каталогу за вказаною датою, а не дані про укладені угоди.\n\n★ Butterfly Knife | Doppler (Factory New)\n\nДжерело: https://phishdestroy.io/steam_dossier/uk/elite_skins#selected\n\nВимірюваний розрив: Ці пропозиції не можуть зрівнятися з об’єктами, виставленими на сайті Steam за такою ж ціною в доларах США. Власні пропозиції Valve Часті запитання щодо громадського ринку архів 2026-09-21 ↗ вказує приблизну максимальну ціну виставлення на продаж — $1,800. Продавець все одно може виставити товар за ціною нижче цієї суми; чи буде це прийнятно — вирішувати продавцю. Окремий Пошук товарів на CSMarketCap вартістю понад $1,800 ↗ показує, що «Factory New Dragon Lore» представлений на ринках, індексованих на сайті 28, з приблизно 1.1K K опублікованих пропозицій; одна й та сама позиція в асортименті може бути врахована кілька разів.\n\n03 / структурна залежність\nКапіталізація компанії Steam виводить процес формування цін за межі Steam\n\nЦе порівняння має структурний характер. Воно не передбачає, що кожна заявлена ціна є справедливою, і не розглядає непродані об’єкти як дохід.\n\n01 · ПРАВИЛО\nSteam завершує список\n\nValve зазначає, що кількість оголошень на «Community Market» обмежена приблизно $1,800. Крім того, на залишки на гаманцях встановлено обмеження, і кошти з гаманців не можна зняти готівкою.\n\n02 · СПОСТЕРЕЖЕННЯ\nDragon Lore: $10,940.85\n\nУ каталозі торгової платформи «5-» наведено 389 акційні пропозиції для AWP Dragon Lore (Factory New) — від $10,940.85 (на сайті CSFloat). У розширеному реєстрі містяться 248 підтверджені категорії, що перевищують обмеження Steam.\n\n03 · НАСЛІДКИ\nРозподіл ціни та комісії за переказ\n\nПродавець, який прагне отримати вищу ціну не можу опублікувати це на сайті Steam. Зовнішні сервіси можуть встановлювати ціну готівкою, але при доставці все одно застосовується система володіння та передачі товарів, що контролюється Steam.\n\nПротиріччя в політиці: Власний сайт Valve Угода з абонентом архів 2026-09-21 ↗ залишає за собою право на комерційне використання послуг Steam, якщо це не дозволено явно, тоді як її 2016 заява архів 2026-09-21 ↗ Зазначено, що оператори азартних ігор уже використовували Steam OpenID та автоматизовані облікові записи. Це є прямим доказом того, що Valve знало про існування такого типу сторонніх операторів на 2016.. Проте офіційний торговий майданчик не може оприлюднювати ціни, що спостерігаються на ці дорогоцінні товари. Це архітектурна залежність від визначення цін та здійснення транзакцій на позабіржовому ринкуSteam; Статус договору для кожного окремого торговельного майданчика вимагає окремих підтверджуючих документів. Два основні західні торговельні майданчики, на які припадає цей надмірний обсяг транзакцій, діють як офіційні юридичні особи в провідних юрисдикціях — CSFloat Inc. (зареєстрована в штаті Делавер, США) та Skinport GmbH (зареєстрована в Штутгарті, Німеччина, HRB 764879) — відкрито здійснює операції на сотні мільйонів у сфері продажу товарів між приватними особами, безпосередньо використовуючи веб-API та торговельну інфраструктуру Steam.\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\nЧотири рядки з ціною $100,000 відповідають максимальній ціні виставлення, встановленій самою компанією «CSFloat». Вони позначені в реєстрі і не повинні трактуватися як оціночні дані. Архівний знімок списку CSFloat охоплює лише ціни приблизно до $6,999,, тому для перегляду повного реєстру >$1,800 використовується знімок публічного каталогу.\n\n04 / ще одна гра серії «Valve»\nУ топ-листі також опинилася Dota 2\n\nТакий самий суворий тест на найнижчу ціну на сайті Skinport виявляє категорії 166 CS2 та 3 Dota 2. Це окремий знімок ринку; не додавайте їх до списку CSFloat 245.\n\nDOTA 2 · Пропозиція щодо «1»\nГероїчний жорстокий півмісяць\n\nНайнижча ціна на «Skinport»: $14,622.25.\n\nDOTA 2 · Пропозиція щодо «1»\nНакидка «Темне мистецтво»\n\nНайнижча ціна на «Skinport»: $8,255.16.\n\nDOTA 2 · Пропозиція щодо «1»\nЗіпсована Зірка, що живиться енергією\n\nНайнижча ціна на «Skinport»: $2,087.92.\n\nЦе три категорії предметів, перелічених у списку, а не всі існуючі предмети у грі Dota 2. Переглянути записи з датою «Skinport» ↗ та API документація ↗.\n\n05 / стійкість\nЦей результат не залежить від конкретного верхнього обмеження\n\nValve встановлює верхню межу у регіональній валюті покупця, тому після перерахунку в долари США сума не дорівнює цілій цифрі. Тому підрахунок повторюється для кожного ймовірного порогового значення. Частка цих позицій, яких бракує на сайті Steam, ніколи не опускається нижче 95%.\n\nПеревірено на порогове значення\tКатегорії товарів\tПерелік примірників\tМінімальне значення\tВідсутній на сайті Steam\n$1,800\t419\t18,641\t$82,449,526\t95.9%\n$2,000\t382\t15,159\t$75,541,325\t95.5%\n$2,070\t363\t12,336\t$69,560,305\t95.6%\n$2,300\t323\t11,644\t$67,984,432\t95.0%\n$2,500\t299\t10,950\t$66,203,929\t95.0%\n\nЧитайте по одному рядку за раз; ці рядки є вкладеними підмножинами одного й того самого перепису, а не окремими популяціями. «Мінімальне значення» помножує показник кожного ринку на найнижчий у ньому вказано кількість примірників, тому за своєю структурою він занижує кількість примірників на полицях. Відкрити набір даних ↗\n\n06 / дефіцит, який можна підрахувати\nЯк мало таких насправді є у продажу\n\nBUFF ділить асортимент кожного товару на діапазони цін і вказує, скільки екземплярів знаходиться в кожному з них. Таким чином, слово «рідкісний» перетворюється на конкретне число — а ціна на товар визначається окремо від його зовнішнього вигляду.\n\n298 ПЕРЕЛІК КОПІЙ\nAWP | Легенди про драконів\n\n8 різні варіанти з вказаною ціною. Найдорожчий, Сувенірний AWP | Dragon Lore (абсолютно новий), запитує $12,363 на полицях є 20 примірників.\n\nУ найкращому кронштейні для поплавків на полиці (0–0.01) є 2 копії, запитуючи $17,875 — надбавка у розмірі +45% до базової ціни продажу товару, що враховує лише його стан.\n\n607 ПЕРЕЛІК КОПІЙ\nM4A4 | Howl\n\n12 різні варіанти з вказаною ціною. Найдорожчий, Сувенірний M4A4 | Howl (абсолютно новий), запитує $14,895 на полиці лежать примірники книги «2».\n\n213 ПЕРЕЛІК КОПІЙ\nAK-47 | «Дикий лотос»\n\n7 різні варіанти з вказаною ціною. Найдорожчий, Сувенірний АК-47 | Wild Lotus (абсолютно новий), запитує $14,895 на полиці лежать примірники книги «2».\n\n310 ПЕРЕЛІК КОПІЙ\nAWP | Гунгнір\n\n7 різні варіанти з вказаною ціною. Найдорожчий, Сувенірний AWP | Гунгнір (з мінімальними слідами зносу), запитує $14,895 на полиці лежать примірники книги «2».\n\nЧому це має значення для решти матеріалів цього досьє: Це не абстракції. У всьому світі на відкритих полицях зберігається кілька сотень екземплярів кожного трофея, кожен із яких прив’язаний до одного облікового запису Steam і переміщується за допомогою однієї угоди Steam. На такому вузькому ринку викрадення навіть одного предмета з інвентарю є помітною подією, а методи захоплення облікових записів, описані в інших розділах цього розслідування, приносять безпосередню та кількісно вимірювану вигоду.\n\nЦі цифри відображають кількість лотів, доступних на одному торговельному майданчику на момент збору даних, а не загальну кількість існуючих лотів. Екземпляри, що знаходяться в приватних колекціях, тут ніде не враховуються. Відкрити набір даних про поплавки ↗\n\n07 / драбина поза полем зору\nЧим дорожчий товар, тим далі він знаходиться від будь-якого помітного місця продажу\n\nКожен нижній щабель відповідає окремій категорії доказів. Їх навмисно не об’єднано в одне число.\n\nСходинка\tРисунок\tЩо це за факт\nCeiling on Valve's own market\t~$1,800\tPublished rule, stated in the Steam Community Market FAQ.\nDearest ask several marketplaces agree on\t$66,285\tMeasured by us in this snapshot. Sticker | Titan (Holo) | Katowice 2014, quoted by four marketplaces within 5.2% of one another. An ask, not a sale.\nDearest ask seen on any single shelf\t$148,954\tOne marketplace, one copy, no second marketplace agreeing — and equal to a round CNY 1,000,000 at the snapshot rate. Listed here as the outer edge of what sellers ask, and relied on for nothing.\nPublic marketplace sale\t$49,999\tSpecialist Gloves | Crimson Kimono (FN) on CSFloat, as reported by SteamAnalyst. Platform-recorded, third-party reported.\nReported private sale\t$400,000\tAK-47 | Case Hardened, reported by PC Gamer in April 2023. Journalism, not a record we hold.\nReported offer, declined\t$1,500,000\tBlue Gem Karambit, pattern #387. No sale took place and the figure has not been independently confirmed. Included to mark the ceiling of the claims, not to assert a value.\n\nСтруктурна особливість: Ринок Valve зупиняється на рівні приблизно $1,800.. Сторонні торговельні майданчики продовжують торги до рівня близько $66,000, де згодні кілька з них, і до рівня приблизно $150,000, де згоден лише один. Вище цього рівня торговельних майданчиків взагалі немає — найбільші операції з активами, випущеними Valve, відбуваються приватно, між фізичними особами, без розміщення на біржі, без запису на платформі, без перевірки особи та без звітності. Сама операція передачі все ще здійснюється на Steam. Чим вище значення, тим менше його можна побачити, а інфраструктура, що його підтримує, повністю належить компанії «Valve».\n\nОстанні два пункти — це повідомлення інших осіб, на які наводиться відповідне посилання. У рамках цього проєкту їх не перевіряли, і жодні висновки не ґрунтуються на них.\n\nУсі категорії, відстежувані на сайті 419\n\nДжерело: https://phishdestroy.io/steam_dossier/uk/elite_skins#register\n\n09 / походження та межі\nПеревірте розрахунок\n\nМи надаємо доступ до локальних даних та відкритого джерела. Числовий показник стосується веб-сайту CSFloat станом на дату збору даних.\n\nВласні обмеження та умови компанії Valve\n\nSteam Часті запитання щодо ринку спільноти ↗ архів 2026-09-21 ↗ вказує приблизну максимальну ціну $1,800. Ця Угода з абонентом ↗ архів 2026-09-21 ↗ визначає обмеження щодо комерційного використання.\n\nЗвідки беруться ціни\n\nЦіни, кількість акцій у обігу та діапазони ринкової капіталізації взяті з cs2.sh ринкові дані API в рамках платної комерційної передплати з використанням ліцензійного ключа. Не було здійснено скрейпінгу жодного маркетплейсу, а також не використовувалися жодні облікові записи чи облікові дані маркетплейсів. Цей провайдер об’єднує дані з BUFF, Youpin, CSFloat, Skinport, C5Game та Steam Community Market; усі цифри наведені у доларах США у тому вигляді, в якому вони були надані. Відкрити маніфест походження ↗ — у ньому зафіксовані точні кінцеві точки, час створення знімків та хеші SHA-256 необроблених знімків, тож незалежний читач, який має власний ключ, може отримати ті самі дані та перерахувати кожне число на цій сторінці.\n\nТе, чого нам не вдалося отримати\n\nПридбана підписка охоплює лише поточні знімки. Ми не мали доступу до історичних та архівних кінцевих точок, і На цій сторінці не містяться жодні твердження щодо будь-яких тенденцій, будь-яких цін у минулому чи будь-яких змін з плином часу. Усе тут — це окремий момент, з датою.\n\nРаніше зареєстрований на сайті CSFloat\n\nУ першій версії цієї виставки було враховано категорії 245 з одного знімку каталогу CSFloat, датованого 20 вересня 2026: цей знімок залишається тут ↗. Цей реєстр є ширшим, оскільки охоплює п’ять торгових майданчиків, а не один. Ці два показники є окремими даними і їх не слід додавати один до одного.\n\nЗаява компанії Valve щодо конкретного виконання зобов’язань\n\nОновлення щодо торгівлі ігровими предметами в грі «2016» від Valve ↗ архів 2026-09-21 ↗ стосується операторів азартних ігор, які використовують OpenID та автоматизовані облікові записи Steam. Цей захід має більш вузьку сферу застосування, ніж заборона на всі сторонні торговельні майданчики.\n\nМежа інтерпретації\n\nЦе пропозиції, а не продажі. Назва товару на ринку може охоплювати кілька фізичних одиниць з різними деталями щодо плавучості, візерунків або наклейок. Цей реєстр не відображає загальну ринкову вартість або наміри компанії «Valve».",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Реєстр Elite Skins — Максимальна ринкова вартість $1,800"
          },
          {
            "level": 2,
            "id": null,
            "text": "Мінімальний поріг у доларах, що піддається вимірюванню"
          },
          {
            "level": 3,
            "id": null,
            "text": "Чому це мінімальний рівень, а не приблизна оцінка"
          },
          {
            "level": 2,
            "id": null,
            "text": "Що не враховується в цьому обмеженні"
          },
          {
            "level": 3,
            "id": null,
            "text": "★ Butterfly Knife | Doppler (Factory New)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Капіталізація компанії Steam виводить процес формування цін за межі Steam"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam завершує список"
          },
          {
            "level": 3,
            "id": null,
            "text": "Dragon Lore: $10,940.85"
          },
          {
            "level": 3,
            "id": null,
            "text": "Розподіл ціни та комісії за переказ"
          },
          {
            "level": 2,
            "id": null,
            "text": "У топ-листі також опинилася Dota 2"
          },
          {
            "level": 3,
            "id": null,
            "text": "Героїчний жорстокий півмісяць"
          },
          {
            "level": 3,
            "id": null,
            "text": "Накидка «Темне мистецтво»"
          },
          {
            "level": 3,
            "id": null,
            "text": "Зіпсована Зірка, що живиться енергією"
          },
          {
            "level": 2,
            "id": null,
            "text": "Цей результат не залежить від конкретного верхнього обмеження"
          },
          {
            "level": 2,
            "id": null,
            "text": "Як мало таких насправді є у продажу"
          },
          {
            "level": 3,
            "id": null,
            "text": "AWP | Легенди про драконів"
          },
          {
            "level": 3,
            "id": null,
            "text": "M4A4 | Howl"
          },
          {
            "level": 3,
            "id": null,
            "text": "AK-47 | «Дикий лотос»"
          },
          {
            "level": 3,
            "id": null,
            "text": "AWP | Гунгнір"
          },
          {
            "level": 2,
            "id": null,
            "text": "Чим дорожчий товар, тим далі він знаходиться від будь-якого помітного місця продажу"
          },
          {
            "level": 2,
            "id": null,
            "text": "Усі категорії, відстежувані на сайті 419"
          },
          {
            "level": 2,
            "id": null,
            "text": "Перевірте розрахунок"
          },
          {
            "level": 3,
            "id": null,
            "text": "Власні обмеження та умови компанії Valve"
          },
          {
            "level": 3,
            "id": null,
            "text": "Звідки беруться ціни"
          },
          {
            "level": 3,
            "id": null,
            "text": "Те, чого нам не вдалося отримати"
          },
          {
            "level": 3,
            "id": null,
            "text": "Раніше зареєстрований на сайті CSFloat"
          },
          {
            "level": 3,
            "id": null,
            "text": "Заява компанії Valve щодо конкретного виконання зобов’язань"
          },
          {
            "level": 3,
            "id": null,
            "text": "Межа інтерпретації"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/uk/#market-gap-section",
          "https://phishdestroy.io/steam_dossier/uk/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/uk/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/uk/skin_atlas.html#grading",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-above-the-ceiling.json",
          "https://phishdestroy.io/steam_dossier/uk/elite_skins#selected",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://csmarketcap.com/search?minPrice=1800&amp;page=1",
          "https://store.steampowered.com/agreement/?l=english",
          "http://web.archive.org/web/20260921022032/https://store.steampowered.com/agreement/?l=english",
          "https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921021947/https://store.steampowered.com/oldnews/22883",
          "https://phishdestroy.io/steam_dossier/uk/#proxy-bypass-explainer",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/skinport-floor-over-cap.json",
          "https://docs.skinport.com/items",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-float-scarcity.json",
          "https://phishdestroy.io/steam_dossier/uk/elite_skins#register",
          "https://cs2.sh/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/csfloat-catalogue.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/uk/elite_skins.content.json",
      "export_json_sha256": "f0f090585b6194fa5da443d926165a3c9f53bb2b3fc2cb912b6e95481a499baa"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "uk/enforcement_audit.html",
      "language": "uk",
      "title": "Результати перепису населення Valve не будуть оприлюднені — Досьє Steam",
      "source_url": "https://phishdestroy.io/steam_dossier/uk/enforcement_audit",
      "source_html_sha256": "75a180fa2481b5c9045ce850164b98355b7bbd5b4182d7e9993c590cf236e500",
      "exported_at": "2026-09-29T00:19:23.727Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "enforcement_audit.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/uk/enforcement_audit.pdf?v=print-20260929-v5",
        "sha256": "1f1acc9a8fee7ef73257e1281ccde0edbec6f147ce523af964412fce0d2af5d9",
        "bytes": 157871,
        "pages": 14
      },
      "integrity": {
        "signed_object": "enforcement_audit.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "enforcement_audit.content.json.asc",
        "digest_file": "enforcement_audit.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify enforcement_audit.content.json.asc enforcement_audit.content.json",
          "sha256sum -c enforcement_audit.content.json.sha256"
        ]
      },
      "content": {
        "text": "ДОДАТОК VI — РЕЗУЛЬТАТИ ПЕРЕПИСУ НАСЕЛЕННЯ VALVE НЕ БУДУТЬ ОПРИЛЮДНЕНІ\nНаскільки велика ферма в Steam? Ми порахували її самі.\n\nНемає опублікованих даних про те, скільки облікових записів автоматизації працюють на Steam. У цьому немає потреби зберігати таємницю: простір ідентифікаторів Steam є суцільним діапазоном цілих чисел, а Valve видає ключ Web API, який дозволяє пробігати цей діапазон. Тому ми взяли найбільшу групу, яка ідентифікує себе — спільноту ArchiSteamFarm — і один раз прочитали дані про кожного її учасника через власний кінцевий пункт заборони Valve. Вона самоідентифікується, оскільки ASF під час першого запуску автоматично приєднується до групи Steam, якщо користувач явно не відмовиться від цього або не зніме галочку з налаштування приєднання до групи (AutoJoinSteamGroup / Статистика). Оскільки цей параметр увімкнено за замовчуванням, до складу групи входять представники широкого кола користувачів: активні комерційні мережі ботів із кількома акаунтами, випадкові користувачі-любителі, які залишають акаунти в режимі очікування, та звичайні гравці, які запускали програму на своєму особистому акаунті й ніколи не скасовували підписку за замовчуванням. Це робить склад групи фактичним переписом сукупного охоплення програми: 10,880,610 загальна кількість облікових записів (з 5,360,499 підтвердженими користувачами без обмежень, які пройшли через $5.00 вхід до магазину). Потім ми поставили єдине питання, яке має значення, — що ж насправді зробив Valve з ними?\n\nЧим ця сторінка не є. Це не аргумент на користь того, що Valve має заблокувати десять мільйонів людей, і це не скарга на «фармерів» карток. Кожна наведена нижче цифра присутня тут з однієї причини: Valve чи накладає постійну заборону на окремих осіб, а як підставу для цього в письмовій формі вказує комерційне використання Steam та автоматизацію. Це показує, як те саме правило застосовується до тієї самої поведінки у великих масштабах — оператором, який по ходу справи отримує $5.00 за розблокування, ліцензії на ігри та комісійні з Маркетплейсу Valve. Висновок полягає в асиметрії, а не у фармі.\n\nКількість 10,88 млнШахраї, які ходять (53,5 тис.)Платний аудит вартістю 100 тис. проти безкоштовного аудиту\n10,880,610Загальна кількість учасників групи ASF, які ознайомилися з власним API блокування користувача Valve (обмежені та необмежені разом)\n88.97%Мене ніколи не блокували — 9,680,599 акаунтів досі активні\n63.06%З числа заблокованих облікових записів — ті, що оплачені ($5+ витрати) — 100,000 SRSWOR частка (±0.39% похибка)\n67.77%Серед 51,732 шахраїв, щодо яких було винесено судове рішення, немає жодного, на кого було накладено заборону на шахрайство (повний перелік)\n01 — Шкала\nДесять мільйонів облікових записів, і дев’ять із десяти — недоторкані\n\nОдин масив, який підраховує себе, зчитується один раз через власну кінцеву точку Valve.\n\nЧОМУ ВОНО САМО ПІДРАХОВУЄ\nASF приєднується до групи заради вас\n\nПри першому запуску ArchiSteamFarm наборів Статистика за замовчуванням встановлюється значення «true», і він приєднується до групи «SC Farm Steam» Archi. Оператор повинен самостійно відмовитися від участі. Отже, членство є мінімальною межею кількості встановлень, а не максимальною. Оператори, які вимкнули статистику, не враховуються; реальна кількість встановлень щонайменше дорівнює цій цифрі.\n\nЩО МИ ЧИТАЄМО\n10,880,610 загальна кількість записів\n\nСписок учасників API загалом повернув 10,880,610 SteamID64 — як обмежених, так і необмежених. На сторінці групи Steam відображається 5,360,499 (лише необмежені). Кожен запис було пропущено один раз через ISteamUser/GetPlayerBans на 2026-09-23. П’ятдесят п’ять хвилин на одній клавіші.\n\nВІДПОВІДЬ\n88.97% очистити\n\n1,200,011 не підпадає під жодну Steam заборону (11.03%). Інший 9,680,599 у базі даних немає жодних записів — ні заборони в спільноті, ні VAC, нічого. Ферма не ліквідується. Її залишають у дії. Одного лише цього пункту, спрямованого проти однієї особи, достатньо, щоб назавжди її видалити.\n\nСкільки з 10,880,610 рахунків торкнулося Valve\n\nУся просканована популяція, розділена залежно від того, чи застосовував Valve будь-яку заборону. Червоний сегмент відображає всі дії, які Valve коли-небудь здійснював щодо цього флоту.\n\n88.97%ніколи не блокували\n11.03%\nЖодної заборони будь-якого роду — 9,680,599 (88.97%)Має певний Steam заборону — 1,200,011 (11.03%)\n10,880,610Учасники групи ASF просканували\n9,680,599Ніколи не блокували — 88.97%\n1,200,011Мати будь-яку заборону — 11.03%\n55 хвЩоб підрахувати все це за допомогою одного ключа API\nСкільки цей флот вже заплатив Valve за своє існування\n\nЦе не оцінка доходів ферми. Це мінімальна сума, яку вона вже витратила в магазині Valve — отримана на основі власного правила Valve, застосованого до наведеного вище підрахунку.\n\nЗначення 10,880,610 охоплює повний список учасників групи ASF, який повертає API — сюди входять як обмежені, так і необмежені облікові записи. Власне значення Steam Обмежені облікові записи користувачів На цій сторінці зазначено, що облікові записи з обмеженими правами не враховуватися у Steam членство в групі (вони не враховуються при відображенні чисельності групи), але все одно можуть з’являтися у відповідному списку учасників. Необмежена підмножина — акаунти, які витратили щонайменше $5.00 у магазині Steam — дорівнює саме 5,360,499 — на сторінці групи відображається кількість Steam, яка, згідно з власним правилом Steam, не враховує обмежені облікові записи. Розрахунок мінімального порогу $5.00 застосовується лише до цієї необмеженої підгрупи.\n\n5,360,499члени без обмежень\n(кількість груп, що відображаються у Steam)\n×\n$5.00Власний мінімум Valve\nщоб перестати бути обмеженим\n=\n$26,802,495мінімальна сума покупок у магазині\nза допомогою необмеженої підмножини\n\nЦе нижня межа суми коштів, яку Valve вже отримала від необмеженої частини флоту — це не оцінка доходу і не заява про прибуток. Фактичні витрати на один обліковий запис для більшості є вищими; цифра $5.00 є лише мінімальним необхідним порогом.\n\nВторинний збір: комісія у розмірі до 66.7% від обсягу вирощеної продукції. Окрім вступного внеску в розмірі $26.8M, за кожну картку та товар, що реалізуються на Спільнотному ринку, сплачується обов’язкова мінімальна комісія в розмірі Valve ($0.01 Steam комісія + $0.01 комісія видавця). Для типових карток та непотрібних предметів вартістю 3 центи, Valve забирає 2 центи з 3 центів — фактичне скорочення на 66.67% на користь Valve, що значно перевищує заявлений маркетинговий показник 15%.\n\nВажливе застереження щодо чисельності населення: Належність до групи не є доказом того, що кожен окремий обліковий запис є спеціалізованим ботом, а також не охоплює всіх ботів на Steam. ASF за замовчуванням автоматично підписує облікові записи на свою групу спільноти під час запуску; за винятком випадків, коли користувач явно знімає галочку або вимикає цей параметр налаштування (AutoJoinSteamGroup), постійні гравці, ті, хто грає лише час від часу, та члени спільноти залишаються у списку поряд з автоматизованими флотами для фармінгу. Крім того, заборона Steam не супроводжується публічним обґрунтуванням. Цей висновок є емпіричним показником для всієї групи користувачів, пов’язаних із цим програмним забезпеченням, а не індивідуальним рішенням щодо будь-якого окремого облікового запису. Сукупний, відтворюваний: asf-ban-census-2026-09-23.json.\n\n02 — Географія\nДе базується флот\n\nЛише 8.5% із заблокованих акаунтів взагалі вказали країну. Серед тих, хто це зробив, найбільшу частку становлять користувачі зі Сполучених Штатів.\n\nПрофіль Steam містить опціональне поле «Країна». 100,413 із 1,182,811 заблокованих акаунтів заповнили його — 8.5%.† Серед цієї меншості лідирують Сполучені Штати з показником 15.5%, за ними йдуть Україна, Китай і Росія, а решта розтягується довгим хвостом по всій Європі, Латинській Америці та Південно-Східній Азії. Ніхто не перевіряє ці дані: Афганістан входить до першої десятки, що приблизно відповідає його значенню. Інші 91.5% пропущено, а не присвоєно, тож те, що наводиться далі, відображає структуру самовідібраної меншості — це не карта флоту і не підстава для тверджень про те, звідки він керується.\n\nЗаблоковані акаунти за країною, яку вказано\n\n15 країн, що лідирують за кількістю 100,413 заблокованих акаунтів, які розкривають місцезнаходження у публічному просторі. Частка вказана від цієї підгрупи. Наведіть курсор, щоб побачити кількість.\n\n0%\n5%\n10%\n15%\n20%\nUnited States\nUkraine\nChina\nRussia\nCanada\nAustralia\nJapan\nBrazil\nGermany\nAfghanistan\nUnited Kingdom\nRomania\nFrance\nPhilippines\nIndia\n\nМісцезнаходження, зчитане з GetPlayerSummaries для забороненої підмножини. Це поле заповнюється власником облікового запису і ніким не перевіряється, тому вихідний сервер VPN або жартівливий запис враховуються так само, як і справжні.\n\n03 — Свіжість\nОстанні рахунки, а не старі заборгованості\n\nСудячи з дати створення облікових записів, ця група заблокованих користувачів з’явилася нещодавно, а не є залишком епохи колекційних карток.\n\nЯкби це була давня проблема, яку поступово вирішують, то заборонені акаунти переважно стосувалися б перших років існування колекційних карток. Насправді ж все навпаки. З 1,132,852 заборонених акаунтів, у яких вказано дату створення, 70% були створені у 2020 році або пізніше, а майже половина з них — з 2023 року. Цей показник зріс з 59,175, встановленого у 2017 році, до пікового значення 227,030 створено лише у 2024 році. Кожен із них пройшов через ворота магазину $5.00 ще до того, як там встигли прийняти картку, тому з кожного було стягнуто вхідний внесок.\n\nКоли були створені заблоковані акаунти\n\nРік створення облікових записів 1,132,852 заблокованих користувачів, у яких вказано дату створення. Період охоплює 2020–2026 роки, а не епоху колекційних карток 2013–2015 років. Пік: 2024 рік. Наведіть курсор, щоб переглянути кількість.\n\n0k\n63k\n125k\n188k\n250k\n'13\n'14\n'15\n'16\n'17\n'18\n'19\n'20\n'21\n'22\n'23\n'24\n'25\n'26\n70%Серед заблокованих акаунтів, створених у 2020 році або пізніше\n227,030Заблоковані акаунти, створені у 2024 році — році піку активності\n51,701Спад у 2021 році, що припав на період між двома піковими роками, — причина якого залишається нез’ясованою\n2003→2026Діапазон даних наявний, але дані охоплюють лише останні шість років\n\nДата створення — GetPlayerSummaries для підмножини заблокованих акаунтів, очищеної від дублікатів за SteamID64. Датою створення вважається дата реєстрації акаунта, а не дата його блокування чи початку фармінгу; ця інформація використовується тут як доказ того, наскільки недавно з’явилася ця група, а не як доказ намірів. Три речі, яких не відображає діаграма:\n\nТенденція після 2024 року. Акаунт, створений у 2025 або 2026 році, мав менше часу, щоб отримати блокування, а 2026 рік охоплює дев’ять місяців — отже, 227,030 → 121,070 → 16,534 свідчить про цензуру, а не про зниження.\nКоефіцієнт заборони. Дати створення враховувалися лише для заблокованих облікових записів, тому знаменник відсутній. Сама лише зростаюча кількість користувачів могла б зумовити таку динаміку.\nЧому 2021 рік виявився провальним. 51,701 розташоване між 105,821 і 104,641, нижче половини висоти кожного з сусідів. У відкритих джерелах немає пояснень щодо цього; це значення залишено видимим, а не згладжено.\n04 — Графік\nКоли Valve спрацьовує, це відбувається протягом першого року\n\nОчевидним аргументом на користь того, що 88.97% залишається незмінним, є накопичені справи. Однак заборони, що мають дату, свідчать про протилежне.\n\nСкільки часу існував акаунт на момент накладення блокування\n\nВік облікового запису на момент блокування для 293,750 заблокованих облікових записів, для яких вказано як дату створення, так і дату останнього блокування. Більше половини з них було виявлено протягом першого року.\n\n0%\n10%\n20%\n30%\n40%\n<6 mo\n33.7%\n6–12 mo\n21.5%\n1–2 y\n20.6%\n2–5 y\n14.3%\n5 y+\n10.0%\n55.1% inside the first year\nЗаблоковано протягом першого року — 55.1%Пізніше заблоковано — 44.9%\n0,80 р.Медіанний вік облікового запису на момент накладення заборони\n55.1%Заблоковано протягом першого року існування облікового запису\n33.7%Заборонено протягом перших шести місяців\n293,750Облікові записи, в яких вказані обидві дати\n\nОсь відповідь на цей очевидний аргумент на захист. Якщо 88.97% флоту залишається незачепленим через те, що процес виконання просто повільний — накопичені справи поступово опрацьовуються — то заборони, які зробити можна було б припустити, що дані будуть застарілими. Насправді все навпаки: медіанний вік заблокованого облікового запису становив дев'ять з половиною місяців, а третій — 33.7% — був спійманий протягом шести місяців. Коли Valve впливає на цю популяцію, він діє швидко. Дев’ять із десяти, які все ще перебувають на волі, не стоять у черзі.\n\nВік на момент заборони = дата створення від GetPlayerSummaries віднято від дати введення заборони, яка випливає з Кількість днів з моменту останнього блокування, читайте далі 2026-09-23. Це значення обчислюється лише в тих випадках, коли присутні обидва значення: 293,750 із 1,200,011 заблокованих облікових записів. Решта облікових записів не містять значення «кількість днів з моменту», тому їх опущено, а не припущено — тож розглядайте це як форму датованої підмножини, а не кожного окремого блокування.\n\n05 — У чому насправді полягає ця заборона\nКоли Valve спрацьовує, це не зупиняє бота\n\nСеред тих 11%, на яких накладено будь-яку заборону, зверніть увагу, яка саме заборона.\n\nБлокування — це не блокування. З 1,200,011 облікових записів Valve позначив як підозрілі, 99.8% нести спільнота заборона — обмеження на форумах, у профілях та групах, яке жодним чином не впливає на торгового бота. Акаунт як і раніше може отримувати картки, здійснювати обмін та переміщувати запаси. 22.2% мають принаймні один ігровий бан та 3.9% бан категорії VAC; ці категорії перетинаються, тому їх не можна підсумовувати. Єдина санкція, яка фактично унеможливлює торгівлю, — бан на економічну діяльність / торгівлю — накладена на 5,214 акаунтів. Ми не спираємося у цій справі лише на цю цифру — заборони на торгівлю загалом є рідкісними у Steam випадках. Суть цієї діаграми простіша: навіть частка Valve чи Touch продовжує торгувати.\n\nЗа що насправді заблоковані ці 11%\n\nЧастка кожного типу блокування від загальної кількості 10,880,610 перевірених учасників. Один акаунт може мати кілька типів блокування. Наведіть курсор, щоб переглянути кількість.\n\n0%\n4%\n8%\n11%\n15%\nCommunity ban\nGame ban\nVAC ban\nEconomy / trade ban\n\nЗаборона типу Steam не містить поля «причина», тому жодна з цих заборон не пов’язана конкретно з фармінгом карт — це поєднання різних типів заборон, наведених поряд із тим, що фактично обмежує кожен із цих типів. Заборона від спільноти не перешкоджає торгівлі; на відміну від неї, економічна заборона / заборона на торгівлю — перешкоджає. Підсумок: asf-ban-census-2026-09-23.json.\n\n06 — Інша група населення\nШахраї Valve, давайте розберемося: 51,732 Повний перепис населення\n\nДругий, незалежний список — випадки шахрайства, підтверджені спільнотою, — оцінений на основі того самого офіційного API.\n\nГрупу прихильників автоматизації можна було б списати на рахунок нешкідливих ледарів. А от другу групу — ні. SteamRep — це давно діюча база даних про репутацію спільноти; обліковий запис, позначений ЗАБЛОКУВАНО Ця спільнота визнала цю особу шахраєм на підставі задокументованих доказів від потерпілих та логів чатів про транзакції. Ми провели повний перепис усіх 51,732 профілів із статусом «ЗАБЛОКОВАНО» на противагу офіційному веб-API Steam (ISteamUser/GetPlayerBans/v1) — і враховувалися лише ті санкції, які стосуються шахрайства. Заборона категорії VAC застосовується за використання програмного забезпечення для обману в грі (аймботи, хаки для бачення крізь стіни); вона не має жодного впливу на трейдера і не є доказом Valve, що вчинив шахрайство, тому не враховується як захід щодо боротьби з шахрайством.\n\nУ рамках повного переліку облікових записів 51,732 67.77% — 35,059 шахраїв, щодо яких було винесено рішення, — не мають ЖОДНИХ заборон, пов’язаних із шахрайством, від Valve: вони все ще можуть здійснювати обмін, надсилати запити на додавання в друзі новим жертвам та обмінюватися повідомленнями. Лише 32.23% отримали заборону на участь у спільноті або на обмін, причому заборона на обмін — єдиний захід, який фактично унеможливлює передачу предметів з інвентарю — накладена лише на 18.81% (9,731 акаунтів). Ще 12.81% (6,627 облікових записів) мають VAC або ігрові заборони виключно за шахрайство в грі, при цьому залишаючись повністю необмеженими в Steam торгівлі.\n\nПідтверджені шахраї, залежно від того, чи застосував Valve заборону, пов’язану з шахрайством (Повний перепис)\n\nУсі 51,732 SteamRep-заблоковані профілі, згруповані залежно від того, чи Valve було застосовано заборону на участь у спільноті чи на торгівлю. VAC та ігрові заборони не враховуються — вони не стосуються випадків шахрайства. Наведіть курсор, щоб переглянути кількість.\n\n0%\n18%\n35%\n53%\n70%\nNo scam-relevant ban\nCommunity or trade ban\n0%\n6%\n13%\n19%\n25%\nCommunity ban\nTrade / economy ban\nVAC (not fraud)\nGame ban\n51,732SteamRep — перевірено заблокованих профілів — 100% повний перепис\n35,059Не має заборони, пов’язаної з шахрайством (67.77%)\n18.81%Впровадьте торговельну заборону, яка покладе край шахрайству (9,731)\n32.23%Пост Valve зазнав заборони з боку спільноти або адміністрації (16,673)\n\nSteamRep — це стороння база даних про репутацію, оцінка якої здійснюється спільнотою, а не Valve — і в цьому суть: зовнішні докази, що порівнюються з тим, що зробила сама Valve. Усі 51,732 заблоковані профілі з канонічного експорту були безпосередньо зіставлені з ISteamUser/GetPlayerBans/v1. Термін «пов’язаний із шахрайством» означає заборону доступу до спільноти або заборону участі в економіці/торгівлі; VAC (12.81%) та ігрові заборони (3.86%) обліковуються окремо, оскільки вони стосуються обману, а не шахрайства. Повний набір даних аудиту: steamrep_steam_bans.csv.\n\nДві популяції, один результат\n\nЦе не ті самі люди і не та сама поведінка. В одному випадку йдеться про десять мільйонів автоматизованих акаунтів, в іншому — про п’ятдесят три тисячі шахраїв, щодо яких було винесено судове рішення. Спільним для них є лише форма результату: дев’ять із десяти сільськогосподарських рахунків ніколи не використовуються, а понад дві третини (67.77%) підтверджених шахраїв не зазнають жодних санкцій, пов’язаних із шахрайством. Блокування в спільноті Valve дійсно вільно застосовується для обмеження доступу до форумів та профілів, але не стосується торгівлі. Кнопка «Повідомити», база даних репутації, блокування, що запобігає шахрайству: все це є, але використовується недостатньо. Порівняйте це з архівними відмовами в основному досьє, де та сама компанія назавжди видаляє окремий обліковий запис, посилаючись на комерційне використання та автоматизацію як причину — це положення не є мертвим, воно є цілеспрямованим.\n\n07 — Проблема з обліковим записом $5.00 та захоплення облікового запису\nЕмпіричний аналіз облікових записів 100,000: ботнети — це не одноразові безкоштовні облікові записи\n\nЛогіка статистичної вибірки та математичний доказ: чому вибір будь-якого іншого значення 100,000 дає абсолютно той самий результат.\n\nОсновним аргументом Valve у відповідь на зауваження регуляторних органів та органів захисту прав споживачів було те, що автоматизовані шахрайські дії та фармінг здійснюються за допомогою тимчасових безкоштовних «одноразових» акаунтів, які швидко блокуються. Згідно з опублікованими правилами Valve, акаунт є Обмежена кількість доки вона не витратить щонайменше $5.00 доларів США у магазині Steam, що унеможливлює для нього торгівлю, надсилання запитів на додавання в друзі та використання функцій API. Ми перевірили це твердження безпосередньо, протестувавши статус монетизації репрезентативної, математично обґрунтованої вибірки 100,000 заблоковано Steam облікових записів взяті з нашого корпусу метаданих профілів 1,182,811.\n\nПРОТОКОЛ ВІДБІРУ ПРОБ (SRSWOR)\n100,000 Неупереджений зріз\n\nЗа матеріалами N = 1,182,811 унікальних заблокованих Steam облікових записів, відібраних методом простої випадкової вибірки без заміщення за допомогою криптографічно однорідного генератора випадкових чисел (PRNG). Кожен обліковий запис мав однакову ймовірність включення, що становила P = n / N ≈ 8.45%, що повністю усуває спотворення, пов’язані з виживанням та активністю.\n\nМАТЕМАТИЧНИЙ ДОКАЗ\nПохибка < ±0.4%\n\nЗастосування формули поправки на скінченну сукупність (FPC) при 99% Довірчий інтервал (Z = 2,576):\nMoE = Z × √[p(1-p)/n] × √[(N-n)/(N-1)] ≈ ±0.39%\n\nВІДТВОРЮВАНІСТЬ\nЧому будь-яка цифра 100 тис. дає однаковий результат\n\nОскільки межа похибки обмежена значенням ±0.4% при рівні достовірності 99%, математично гарантовано, що будь-яка інша незалежна вибірка з 100,000-рахунку потрапить у діапазон 63.06% ± 0.39% (від 62.67% до 63.45%). Ця вибірка відображає всю сукупність із 1,18 мільйона заблокованих користувачів.\n\nРезультати аудиту повністю спростовують аргумент про «одноразові боти». З 100,000 облікових записів, перевірених за допомогою застарілого XML-інтерфейсу профілю Steam: 61,490 облікових записів (63.06% із класифікованих облікових записів) — це облікові записи без обмежень (платні), на які було витрачено щонайменше $5.00 на Steam. Тільки 36,021 (36.94%) є обмеженими безкоштовними обліковими записами, тоді як 2,489 були не налаштованими або приватними.\n\n100,000 Заблоковані акаунти: платні ($5+ витрати в магазині) проти безкоштовних акаунтів з обмеженим статусом\n\nЕмпірична перевірка 100,000 випадково відібраних заблокованих облікових записів. Понад 63% з них пройшли платну фінансову перевірку Valve. Наведіть курсор, щоб переглянути статистику.\n\n0%\n16%\n33%\n49%\n65%\nNon-limited (Paid ≥ $5.00)\nLimited (Free < $5.00)\n100,000Вибіркова сукупність (SRSWOR, N = 1,18 млн)\n63.06%Платні акаунти без обмежень (акаунти 61,490)\n±0.39%Похибка при довірчому інтервалі 99%\n~745,800Екстрапольована кількість платних акаунтів у корпусі з 1,18 млн заблокованих акаунтів\nСтруктурна реальність: ліквідація рахунків у промислових масштабах\n\nЧому 63% від загальної кількості відібраних заблокованих акаунтів мають бути платними акаунтами, власники яких витрачали реальні гроші в магазині Valve? Оператори ботнетів не витрачають мільйони зі своєї кишені на одноразові акаунти. Цей показник підкреслює обсяг зламані та захоплені акаунти що циркулює в екосистемі.\n\nЦю шкалу можна безпосередньо спостерігати на підземних платформах: на таких торгових майданчиках, як FSB Market (анонімізована назва; оригінальну назву тут не вказано), на 550,000 Steam рахунки (журнали даних про крадіжки, матеріали фішингових атак, атаки методом підстановки облікових даних) у будь-який момент активно виставляються на продаж (phishdestroy.io/live-intel). Маркетплейс перевіряє автентичність покупців і продавців за допомогою власного OpenID Valve Steam, і жоден із них FSB Market ані пов’язаний форум блокується фільтром посилань Valve.\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\nЯк зазначено в розділі 06, Valve не вживає активних заходів для припинення цієї шахрайської діяльності: 67.77% шахраїв, підтверджених спільнотою, не мають жодних заборон за шахрайство на Steam, а 88.97% з парку автоматизованих облікових записів залишається абсолютно недоторканим. Ці облікові записи вільно переміщуються, проходять автентифікацію через офіційні API та здійснюють торгові операції в межах екосистеми, практично не несучи жодної відповідальності.\n\nСхема архітектури судово-криміналістичних доказів та правозастосування\nІнтерактивна діаграма, що відображає дані з 10,88 млн просканованих облікових записів, 100 тис. емпіричних зрізів та 53,5 тис. підтверджених шахраїв · Натисніть на посилання, щоб переглянути вихідні дані\nРівень 01 · 10,88 млн — перепис парку засобів автоматизації\nНайбільша група користувачів, які самостійно ідентифікують себе як автоматизовані об’єкти на Steam, послідовно пройшла через офіційний API заборони Valve. Це доводить, що комерційні флоти ботів працюють на 88.97% безкарно, сплачуючи при цьому десятки мільйонів у вигляді вступних внесків.\n9,680,599 88.97% Активні та незаймані\nАкаунти, на яких використовується автоматизоване програмне забезпечення та які не мають у своєму історії жодних заборон будь-якого роду.\nНеоброблені дані перепису у форматі JSON (1,2 КБ) ↗Переглянути розділ 01 ↗\n$26,802,495 Мінімальний рівень доходу від прямих продажів у магазинах\nЗібрано Valve від 5,360,499 членів без обмежень, які перевищили мінімальний поріг вступу $5.00.\nАудит карткової економіки ↗Valve $5 Часті запитання щодо правил ↗\n1,200,011 11.03% Підмножина з позначками\n99.8% — застосовуються лише косметичні обмеження для спільноти; торгівля залишається відкритою на 99.95% рахунках.\nРозподіл за типами заборон ↗Заблокована база даних (60,4 МБ) ↓\nРівень 02 · 100,000 — Аудит на основі емпіричної вибірки за рахунками (N = 1,182,811)\nРепрезентативна вибірка розміром SRSWOR, оцінена за допомогою застарілих XML-кінцевих точок. Математично доведений рівень похибки < ±0.4% при довірчому інтервалі 99%. Це спростовує твердження про те, що заблоковані боти є безкоштовними одноразовими акаунтами.\n61,490 (63.06%) Платні акаунти без обмежень (витрати $5+)\nПонад 63% заблокованих акаунтів припадає на платні транзакції. Це дозволяє екстраполювати, що у пулі заблокованих акаунтів налічується приблизно 745,800 платних акаунтів (мінімальний поріг входу — $3.73 млн).\nОбмежені результати у форматі CSV (2,1 МБ) ↓Експертний звіт щодо 100 тис. ↗\n36,021 (36.94%) Обмежені безкоштовні облікові записи (< $5.00)\nНезначна частина заблокованих профілів відповідає опису «одноразового бота» від Valve. Акаунти 2,489 були неналаштовані або приватні.\nЗразок набору даних у форматі CSV (100 тис. записів) (8,5 МБ) ↓Аналіз витрат MD ↗\n34.67% проти 63.93% Аудит очищення профілів\nValve видалив псевдоніми, замінивши їх на необроблені SteamID64 на 34,673 облікових записах, але залишив власні імена та аватари повністю без змін на 63,928 заблокованих облікових записах.\nВідділ дезінфекції ↗Загальний огляд дорожньої карти ↗\n34.59% Спадщина Старі облікові записи (створені у 2003–2019 рр.)\nПонад третина заблокованих акаунтів була зареєстрована від 5 до 20 і більше років тому, що свідчить про викрадення акаунтів довгострокових гравців Steam у промислових масштабах.\nХронологія вікових періодів ↗Відмови у наданні підтримки ↗\nРівень 03 · 51,732 SteamRep Перепис підтверджених шахраїв\nПовний 100% перелік шахраїв, визнаних винними спільнотою, із логами чатів жертв та доказами торгових операцій, зіставлений з офіційними Steam API-інтерфейсами списків заблокованих користувачів. Доводить системну неспроможність правоохоронних органів.\n35,059 (67.77%) Відсутність заборон за шахрайство (повна безкарність)\nПонад дві третини перевірених шахраїв не мають жодних заборон на участь у спільноті чи на торгівлю від Valve. Вони можуть повноцінно здійснювати торгівлю та залучати нових жертв.\nSteamRep Список заборонених API (2,6 МБ) ↓SteamRep Аудиторський звіт ↗\n9,731 (18.81%) Економіка / Торговельні заборони\nЄдина санкція, яка припиняє реалізацію запасів. Застосовується до менше ніж п’ятої частини підтверджених шахраїв.\nSteamRep Джерело (2,1 МБ) ↓Ознайомтеся з розділом 06 ↗\n6,627 (12.81%) Недоречні заборони за шахрайство (лише VAC)\nЇх заблокували за використання аймботів та воллахів у іграх, тоді як їхні можливості з торгівлі Steam та фішингу залишаються 100% активними.\nVAC Аналіз нерелевантності ↗Хронологія подій у сфері безпеки ↗\nРівень 04 · Втручання у вікі-сайти та порушення безпеки інфраструктури в серпні 2026 року\nУ пакеті доказів зафіксовано випадки несанкціонованого втручання у внутрішню документацію розробників, обмеження доступу до редактора спільноти та порушення безпеки незахищених периметрів.\n1,200+ Редактори Журнали конфліктів VDC Wiki\nРедактори спільноти, які намагалися виправити фішингові посилання та шаблони спаму, систематично блокувалися автоматичними фільтрами, тоді як співробітники Valve ігнорували попередження.\nЗвіт про конфлікти в Росії (127 КБ) ↗Звіт про класифікацію (66 КБ) ↗\n12 ТБ без аутентифікації Серпень 2026 р. Втеча активів (CWE-284)\nValve протягом кількох тижнів розміщував 12 терабайтів внутрішнього коду та прототипних збірок на відкритій публічній точці доступу без аутентифікації.\nValve Досьє про некомпетентність (43 КБ) ↗Архів доказів ↗\nВитік даних у компанії CEVA Logistics Серпень 2026 року: витік персональних даних клієнтів\nІмена, адреси та номери телефонів європейських покупців Steam Deck витекли від логістичного партнера компанії Valve, що спричинило хвилю фішингових атак.\nЗапис про інцидент ↗Історія виконання ↗\n\nАртефакт вибірки: banned_100k_slice.csv (100,000 рахунків). Результати аудиту: slice_100k_limited_results.csv. Повний аналітичний звіт: BANNED_100K_FORENSIC_ANALYSIS.md.\n\n08 — Метод та обмеження\nЯк це було сприйнято і чого в цьому не стверджується\n\nТри відкриті вибірки, один відкритий API, ретельна статистична вибірка.\n\nВИКОНАННЯ ТА ПОВНОВАЖЕННЯ\n\nПерепис ASF, 100,000-акаунт SRSWOR фрагмент та SteamRep перехресна перевірка були виконані PhishDestroy учасниками під їхніми власними Steam акаунтами та ключами Web API в рамках публічної роботи Коаліції з боротьби з фішингом та шахрайством. Автор досьє не володіє жодним Steam ключем Web API і особисто не проводив сканування в режимі реального часу. Агрегація, хешування, верифікація та публікація були здійснені на основі результатів, отриманих учасниками.\n\nНаселення\tЗвідки це взялося\tЩо було прочитано\nЧлени ASF\n10,880,610\tПублічний список учасників групи спільноти ArchiSteamFarm Steam. На сторінці групи Steam відображається 5,360,499 учасників (лише без обмежень); список учасників, отриманий через API, містить загалом 10,880,610 записів, включаючи облікові записи з обмеженнями. При першому запуску користувач автоматично приєднується до групи, якщо він явно не вимкнув налаштування приєднання до групи за замовчуванням у конфігурації (AutoJoinSteamGroup / Статистика), тобто список учасників включає комерційні кластери ботів, окремих користувачів, які використовують картки для пасивного заробітку, та звичайних гравців, які залишили увімкненим стандартний параметр.\tGetPlayerBans для кожного учасника (позначки про блокування); GetPlayerSummaries за датами створення та країною. Зібрано у пакети по 100 ідентифікаторів, з видаленням дублікатів за SteamID64.\n100 тис. заблокованих акаунтів SRSWOR Частина\n100,000\tРепрезентативна вибірка, сформована рівномірним випадковим відбором без повернення з корпусу 1,182,811 заблокованих акаунтів ($P = 8,45\\%$). Корекція на скінченну сукупність дає похибку $\\pm 0,39\\%$ при рівні достовірності 99% ($Z = 2,576$).\tМонетизація та статус обмеженого облікового запису (isLimitedAccount) перевірено за допомогою застарілого інтерфейсу XML-профілю Steam (?xml=1) через розподілені проксі-конвеєри. Підтверджує статус «63.06%» (оплачено).\nSteamRep шахраї\n51,732\tПроведено 100% повний перелік усіх профілів, позначених як «ЗАБЛОКОВАНІ», у SteamRep базі даних репутації спільноти (загалом 51,732 профілів). Вибірка чи фільтрування не застосовувалися.\tISteamUser/GetPlayerBans/v1 для всіх облікових записів 51,732, у перехресному аналізі за статусом SteamRep. Підтверджує, що 67.77% не має жодних заборон, пов’язаних із шахрайством.\nПредмет формули винайдення\n\nЛише емпіричні показники та статистично обмежені оцінки. У сукупності автоматизованих облікових записів 88.97% не мають заборони; підмножина заблокованих облікових записів має перекіс у бік останніх даних (70% з 2020 року). Під час емпіричної перевірки акаунтів 100,000 63.06% заблокованих акаунтів є платними (без обмежень), при цьому математично доведено, що похибка не перевищує ±0.4%. Серед 51,732 підтверджених шахраїв 67.77% не мають заборони, пов’язаної з шахрайством. Кожна цифра може бути відтворена за допомогою власного веб-API Valve.\n\nЩо не є предметом заявки\n\nЗаборона типу Steam не містить поля «причина», тому жодна з таких заборон не пов’язана з конкретною причиною. Належність до групи не є доказом того, що акаунт є автоматизованим ботом: оскільки ASF за замовчуванням дозволяє приєднуватися до груп, якщо цю опцію не відмітити вручну, у цій популяції змішані комерційні ферми з декількома акаунтами та особисті акаунти звичайних гравців і любителів. Інформація про країну надається самими користувачами, а позначка SteamRep є рішенням спільноти, а не судовим вироком. Імена окремих осіб не вказуються.\n\nЧому це важливо\n\nValve використовує той самий API, має власну базу даних та зберігає причини блокування, які цей сканер не може побачити. Він може виконати цей запит по всьому простору ідентифікаторів за лічені секунди. Показник, який дозволяє сторонній організації перевірити заяву про застосування санкцій щодо певного номера, ніколи не публікувався тією стороною, яка може надати його з повною точністю. Це зовнішня оцінка, наведена для того, щоб питання можна було поставити з наведенням конкретної цифри.\n\nЧитайте далі: економіка карт, якою керує ця група населення → · захист від несанкціонованого доступу та крадіжки → · повне досьє →",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Наскільки велика ферма в Steam? Ми порахували її самі."
          },
          {
            "level": 2,
            "id": null,
            "text": "Десять мільйонів облікових записів, і дев’ять із десяти — недоторкані"
          },
          {
            "level": 3,
            "id": null,
            "text": "ASF приєднується до групи заради вас"
          },
          {
            "level": 3,
            "id": null,
            "text": "10,880,610 загальна кількість записів"
          },
          {
            "level": 3,
            "id": null,
            "text": "88.97% очистити"
          },
          {
            "level": 3,
            "id": null,
            "text": "Скільки з 10,880,610 рахунків торкнулося Valve"
          },
          {
            "level": 3,
            "id": null,
            "text": "Скільки цей флот вже заплатив Valve за своє існування"
          },
          {
            "level": 2,
            "id": null,
            "text": "Де базується флот"
          },
          {
            "level": 3,
            "id": null,
            "text": "Заблоковані акаунти за країною, яку вказано"
          },
          {
            "level": 2,
            "id": null,
            "text": "Останні рахунки, а не старі заборгованості"
          },
          {
            "level": 3,
            "id": null,
            "text": "Коли були створені заблоковані акаунти"
          },
          {
            "level": 2,
            "id": null,
            "text": "Коли Valve спрацьовує, це відбувається протягом першого року"
          },
          {
            "level": 3,
            "id": null,
            "text": "Скільки часу існував акаунт на момент накладення блокування"
          },
          {
            "level": 2,
            "id": null,
            "text": "Коли Valve спрацьовує, це не зупиняє бота"
          },
          {
            "level": 3,
            "id": null,
            "text": "За що насправді заблоковані ці 11%"
          },
          {
            "level": 2,
            "id": null,
            "text": "Шахраї Valve, давайте розберемося: 51,732 Повний перепис населення"
          },
          {
            "level": 3,
            "id": null,
            "text": "Підтверджені шахраї, залежно від того, чи застосував Valve заборону, пов’язану з шахрайством (Повний перепис)"
          },
          {
            "level": 4,
            "id": null,
            "text": "Дві популяції, один результат"
          },
          {
            "level": 2,
            "id": null,
            "text": "Емпіричний аналіз облікових записів 100,000: ботнети — це не одноразові безкоштовні облікові записи"
          },
          {
            "level": 3,
            "id": null,
            "text": "100,000 Неупереджений зріз"
          },
          {
            "level": 3,
            "id": null,
            "text": "Похибка < ±0.4%"
          },
          {
            "level": 3,
            "id": null,
            "text": "Чому будь-яка цифра 100 тис. дає однаковий результат"
          },
          {
            "level": 3,
            "id": null,
            "text": "100,000 Заблоковані акаунти: платні ($5+ витрати в магазині) проти безкоштовних акаунтів з обмеженим статусом"
          },
          {
            "level": 3,
            "id": null,
            "text": "Структурна реальність: ліквідація рахунків у промислових масштабах"
          },
          {
            "level": 2,
            "id": null,
            "text": "Як це було сприйнято і чого в цьому не стверджується"
          },
          {
            "level": 3,
            "id": null,
            "text": "Предмет формули винайдення"
          },
          {
            "level": 3,
            "id": null,
            "text": "Що не є предметом заявки"
          },
          {
            "level": 3,
            "id": null,
            "text": "Чому це важливо"
          }
        ],
        "links": [
          "https://help.steampowered.com/en/faqs/view/71D3-35C2-AD96-AA3A",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/asf-ban-census-2026-09-23.json",
          "https://phishdestroy.io/steam_dossier/uk/VALVE_EVIDENCE_PACK/databases/steamrep_steam_bans.csv",
          "https://phishdestroy.io/live-intel/?category=steam",
          "https://phishdestroy.io/steam_dossier/uk/#proxy-bypass-explainer",
          "https://phishdestroy.io/steam_dossier/uk/card_economy.html",
          "https://phishdestroy.io/steam_dossier/uk/VALVE_EVIDENCE_PACK/databases/banned_archiasf_massive.csv",
          "https://phishdestroy.io/steam_dossier/uk/VALVE_EVIDENCE_PACK/databases/slice_100k_limited_results.csv",
          "https://phishdestroy.io/steam_dossier/uk/VALVE_EVIDENCE_PACK/reports/BANNED_100K_FORENSIC_ANALYSIS.md",
          "https://phishdestroy.io/steam_dossier/uk/VALVE_EVIDENCE_PACK/databases/banned_100k_slice.csv",
          "https://phishdestroy.io/steam_dossier/uk/VALVE_EVIDENCE_PACK/reports/STEAM_BANNED_LIMIT_ANALYSIS.md",
          "https://phishdestroy.io/steam_dossier/uk/VALVE_EVIDENCE_PACK/INVESTIGATION_OVERVIEW.md",
          "https://phishdestroy.io/steam_dossier/uk/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/uk/VALVE_EVIDENCE_PACK/reports/STEAMREP_VS_STEAM_AUDIT.md",
          "https://phishdestroy.io/steam_dossier/uk/VALVE_EVIDENCE_PACK/databases/SteamRep_Profiles_BannedCaution_2024.csv",
          "https://phishdestroy.io/steam_dossier/uk/security_timeline.html",
          "https://phishdestroy.io/steam_dossier/uk/VALVE_EVIDENCE_PACK/reports/russian_conflicts_report.json",
          "https://phishdestroy.io/steam_dossier/uk/VALVE_EVIDENCE_PACK/reports/classification_report.json",
          "https://phishdestroy.io/steam_dossier/uk/VALVE_EVIDENCE_PACK/reports/VALVE_INCOMPETENCE_REPORT.md",
          "https://phishdestroy.io/steam_dossier/uk/steam_evidence_archive.html",
          "https://phishdestroy.io/steam_dossier/uk/steam_enforcement_evidence.html",
          "https://phishdestroy.io/steam_dossier/uk/#insider-threat",
          "https://phishdestroy.io/steam_dossier/uk/"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/uk/enforcement_audit.content.json",
      "export_json_sha256": "edf1824ca7881a83372f1615bcb110b608819e58d8a284eedcada262358259a4"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "uk/index.html",
      "language": "uk",
      "title": "Досьє «Steam»: правила, маршрути та підзвітність",
      "source_url": "https://phishdestroy.io/steam_dossier/uk/index",
      "source_html_sha256": "7fa1d6e778a671e30024639bd43095e37ce852f9c3c07832b2d6f2c460fca55e",
      "exported_at": "2026-09-29T00:19:34.164Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "exhibit-gallery-section",
            "source": "https://phishdestroy.io/steam_dossier/uk/index#exhibit-gallery-section"
          }
        ],
        "raster_images_replaced": 2
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "index.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/uk/index.pdf?v=print-20260929-v5",
        "sha256": "246b3db90ad79833f24e6e20fd7a31665ee853fd254d5250f30fd0d1dcf70ed6",
        "bytes": 977289,
        "pages": 112
      },
      "integrity": {
        "signed_object": "index.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "index.content.json.asc",
        "digest_file": "index.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify index.content.json.asc index.content.json",
          "sha256sum -c index.content.json.sha256"
        ]
      },
      "content": {
        "text": "Розділ 1 — Короткий виклад справи\nПравило. Рекорд. Питання, на які немає відповіді.\nКонтекст та обмеження джерел\n\nШість висновків, кожен із яких пов’язаний із датованим публічним документом. Детальні розділи розташовані в такому порядку: технічна документація (Частина А), правила та документація щодо їх виконання (Частина Б), правові рамки (Частина С), а потім — додатки з основними доказами.\n\nШість висновків. Кожен із них пов’язує письмове правило з датованим документом та питанням, яке можна перевірити за допомогою доказів.\n\n1. Хости автентифікації з окремими доменами — 44 маршрути · 26 пар з розділенням\n\nЗаписи в реєстрі безробітних 44 платформи, що проходять автентифікацію через окремий домен, який можна зареєструвати. Ще п’ять маршрутів перебувають на стадії перевірки й очікують на дату RDAP; після їх затвердження загальна кількість маршрутів становитиме 47. Вони не включені до списку 44 маршрутів та до таблиці за віком. — 27 із опублікованим файлом доказів для кожного маршруту та 17, доданих у результаті ручного збору, перелічених окремо. У 26 пар фільтрів-роздільників головний домен — це ЗАБЛОКОВАНО у фільтрі посилань Steam, тоді як проксі-сервер, що використовує ці дані для входу, не потрапляє під блокування. Це не одноразові домени: csgogem.com заблоковано, тоді як api.csgem.com, хост із логіном Steam зареєстрований з березня 2014 року — 12 років 6 місяців. Valve отримує це ім’я хосту в кожному запиті OpenID і відображає його користувачеві на власній сторінці входу. Повна таблиця, терміни дії для кожного маршруту та джерела наведено в розділі 3.\n\nСлідуйте маршрутом →\n2. 2016 рік: механізм отримав назву, було встановлено кінцевий термін\n\n13 липня 2016 року Valve публічно описав, як сайти азартних ігор використовували Steam OpenID та автоматизовані торгові рахунки, а в повідомленнях його юридичного представника від 20 липня 2016 року було встановлено десятиденний термін. З того часу не було опубліковано жодних даних щодо заходів примусу щодо окремих операторів. Через десять років після встановлення цього терміну той самий механізм використовується на хостах автентифікації з окремими доменами, які не повернули жодного блокування за допомогою фільтра посилань на 2026-09-21.\n\nПрочитати відкритий лист до WSGC →\n3. Відповідність пристроїв, на бланку адвоката\n\nУ наведеному тут листуванні адвокат Valve описав кореляцію на рівні пристроїв, що пов’язує один пристрій із кількома обліковими записами — про те, що така можливість, як раніше заявляла служба підтримки Steam, технічно неможлива. Залишається відкритим питання, якими даними на рівні пристроїв володіє Valve і на якій підставі власникам облікових записів відмовляють у доступі до них.\n\nОзнайомитися з меморандумом →\n4. Дві відповіді щодо доступу. В одній випадку дані не були надані, в іншій — стався витік даних.\n\nЖовтень 2025 року: Адвокат Valve відповів на запит згідно зі ст. 15, надавши додаток обсягом 830 сторінок, у якому вилучені фрагменти тексту були зафарбовані, а не видалені — 902,270 символів надати стандартний інструмент для вилучення даних, включаючи ідентифікатори сторонніх джерел, які мали приховувати ці обмежувальні елементи. Стаття 15(4) є підставою для існування цих обмежувальних елементів. Вересень 2026 року: Заявка HT-2YBP-F7JP-D4VB була закрита через три дні з посиланням на сторінку самообслуговування «Дані облікового запису» — без надання даних та зазначення правової підстави. На момент публікації місячний термін, передбачений ст. 12(3), ще не закінчився; заперечення стосується суті справи.\n\nПереглянути перевірку редагування →Переглянути запис про квиток →\n5. Ринок перевищив верхню межу Steam\n\nSteam обмежує ринкову капіталізацію приблизно до $1,800. На п’яти торгових майданчиках за даними з моменту створення знімка (23 вересня 2026 року), 248 категорій товарів CS2 ціна на них перевищує зазначений верхній поріг у двох або більше випадках незалежно один від одного, і усі 248 відсутні в Steam; ціна на абсолютно новий набір «Dragon Lore» починається від $10,941 за 389 екземплярів, зазначених у всіх п’яти (показник лише для CSFloat у розділі 13, за даними знімку від 20 вересня, становить $10,623.95 за 62 пропозиціями). Продаж за цими цінами вимагає використання сторонньої платформи, тоді як передача предметів все ще здійснюється за ціною Steam.\n\nСлідкуйте за ціною та переказом →\n6. Правило сформульовано чітко; ланцюжок аудиту — ні\n\nУгода з абонентом передбачає, що Steam призначено для особистого, некомерційного використання, забороняє комерційне використання, за винятком випадків, коли це прямо дозволено, забороняє використання скриптів та ботів, а також передбачає можливість закриття облікового запису. У 2016 році Valve застосувало ці положення до операторів азартних ігор. Окремо, згідно з інженерним акаунтом CSFloat, Valve закрив IEconItems_730/GetPlayerItems у 2017 році було скасовано публічний доступ до ідентифікаторів оригінальних елементів (журнал змін Valve не знайдено).\n\nРозмістіть правило поруч із мережею →\n2016 / Письмовий запит 10 днів\nКінцевий термін, зазначений у повідомленнях Valve від липня 2016 року, надісланих юридичним представником сайтам, що займаються азартними іграми. Відкритий лист до WSGC: Розділ 2.\n2017 / Публічний аудиторський слід Доступ за ідентифікатором закрито\nCSFloat фіксує втрату оригінальних ідентифікаторів елементів.\nЛистування з адвокатом Кореляція пристроїв\nОдин пристрій пов’язаний із десятками викрадених облікових записів.\nРеєстр маршрутів Акаунт заблоковано, але я все одно намагаюся увійти\nПравило: Згідно із заявою Valve від 2016 року, заборонено вести гральний бізнес на Steam OpenID. Запис: У фільтрі посилань міститься 26 основних доменів, а хост, на якому розміщено обліковий запис Steam для кожного з них, працює вже — хост csgogem.com працює вже 12 років і 6 місяців.\nРозділ 2 — Відкритий лист\nВідкритий лист до Комісії з питань азартних ігор штату Вашингтон\n\nДесять днів перетворилися на десять років. На запит Комісії від 2016 року, адресований Valve, не було надано відповіді у вигляді даних щодо кожного оператора окремо; у цьому листі Комісію просять поновити розгляд справи.\n\nПУБЛІЧНЕ ЗВЕРНЕННЯ · КОМІСІЯ З ПИТАНЬ АЗАРТНИХ ІГОР ШТАТУ ВАШИНГТОН\n\nДесять днів перетворилися на десять років.Відкрийте запис знову.\n\nДо Комісії з питань азартних ігор штату Вашингтон:\n\nУ 2016 році директор Девід Трухільйо попросив компанію Valve продемонструвати, що вона зробила для припинення використання скінів Steam у цілях азартних ігор. Тодішній голова Кріс Стернс та Комісія зіткнулися з індустрією, що базувалася на предметах, випущених Valve, та переказах Steam. З того часу обидва чоловіки залишили свої посади в Комісії. Питання, яке вони поставили Valve, досі залишається актуальним.\n\nГоловний юрисконсульт Valve Карл Квакенбуш надав операторам азартних ігор десять днів на припинення комерційного використання облікових записів Steam. У своїй жовтневій відповіді на запит вашої Комісії компанія Valve заперечила, що сприяє азартним іграм, заявила, що надіслала листи з вимогою припинити діяльність понад сорока веб-сайтам, а також зазначила, що заблокувала пов’язані з ними облікові записи. Вона також виступила на захист збереження торговельної платформи Steam та OpenID, оскільки ці послуги приносять користь клієнтам та розробникам ігор. Це було проявом контролю. Це заслуговує на перевірку, а не на покірність.\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\nНа нашу думку, відповідь компанії Valve не довела, що обрані нею заходи щодо забезпечення дотримання вимог відповідали масштабам мережі, яку вона описала. Лист із погрозами на адресу оператора — це не те саме, що тривале блокування облікових записів Steam, торговельної інфраструктури та маршрутів автентифікації, які забезпечують функціонування бізнесу. За оприлюдненими оцінками, Тільки CS:GO Lounge у 2016 році зафіксував обсяг ставок понад $1 мільярда; це зовнішня оцінка суми ставок, а не доходу Valve, а оригінальна діяльність сайту, пов’язана зі ставками на шкіру, згодом була припинена. Такі масштаби зробили необхідним вжиття заходів, що піддаються перевірці.\n\nСьогодні, власний Valve's Угода з абонентом архів 2026-09-21 ↗ обмежує комерційне використання, за винятком випадків, коли це прямо дозволено, та окремо забороняє певні форми автоматизації. Наш реєстр маршрутів за датами записи, які вказують хости повернення OpenID для зовнішніх служб; openid.realm та openid.return_to це поля, що надсилаються до Steam, а не таємниці, приховані від нього. Наші Перевірка фільтрів посилань показує випадки, коли щодо основної адреси було винесено попередження, але щодо пов’язаного з нею хосту для входу — ні. Сам по собі результат фільтрації не може довести, що Valve дозволив вхід або що конкретний бот обійшов блокування облікового запису. Це дійсно доводить, що попередження на головній сторінці не може слугувати вичерпною відповіддю щодо доступу.\n\nНаявність корисних, законних Steam торговельних функцій та функцій OpenID також не дає відповіді на питання, чи дійсно були виключені оператори, діяльність яких заборонена. Власні правила Valve допускають явні винятки. Якщо Valve спирається на це розрізнення, Комісія повинна попросити його визначити критерії авторизації, контролю облікових записів та забезпечення дотримання вимог, що застосовуються до комерційних підприємств, які займаються «скінами», а також конкретні види використання, не пов’язані з азартними іграми, на які він посилався у 2016 році. Сама лише можливість законного використання не є відповіддю на задокументоване заборонене використання.\n\nМи просимо Комісію переглянути свою справу за 2016 рік та вимагаємо надати звіт щодо кожного оператора окремо: які Steam облікові записи та торгові боти були заблоковані після десятиденних попереджень; чи здійснювався моніторинг пов’язаних облікових записів або хостів, з яких здійснювалися повторні спроби; які оператори згодом відновили доступ; які винятки були надані; та які записи підтверджують заяву Valve перед Комісією. Опублікуйте те, що згідно із законом може бути доступним для громадськості. Порівняйте ці записи з поточними маршрутами та з подальшими втручаннями Valve, включаючи OPSkins у 2018 році архів 2026-03-07 ↗.\n\nУ повідомленні було встановлено десятиденний термін у липні 2016 року; десяти років цілком достатньо, щоб з’ясувати, чи було це виконано. Комісія повинна перевірити звіт Valve за 2016 рік на відповідність інфраструктурі, яка зберігається донині.\n\nРозслідування «Досьє Steam» · Публічна заява, 20 вересня 2026 року\n\nПовідомлення Комісії за 2016 рік ↗ архівується 2026-05-20 ↗ · Відповідь Valve за 2016 рік (копія документа) ↗ · Заява Valve щодо OpenID за 2016 рік ↗ архів 2026-09-21 ↗ · Поточна угода Steam ↗ архів 2026-09-21 ↗ · Хронологія обміну 2016 року: Розділ 11 →\n\nЧастина А — Технічна документація · Розділ 3\nСайт заблоковано. Маршрут входу в систему — ні.\n\n26 заблокованих основних доменів. Проксі-сервер автентифікації, що працює за кожним із них, та час його функціонування. Ці окремі хости для автентифікації не є випадковими додатковими адресами — кожен із них є проксі-сервер аутентифікації для Steam, що стоїть між платформою та кінцевою точкою OpenID Valve і передає дані для входу, які заблокований домен більше не може відкрито передавати. Valve встановив «головні ворота» на фільтр посилань. Вхід продовжував здійснюватися через проксі: csgogem.com заблоковано, і api.csgem.com зареєстрована з березня 2014 року — дванадцять з половиною років. Кожного з цих днів цей хост надсилав своє ім’я хосту на кінцеву точку OpenID користувача Valve, а Steam одразу ж відображав його користувачеві на сторінці входу. Valve — це магістраль, через яку проходять усі ці маршрути; їй не потрібно їх шукати. Саме це й вимірює цей розділ: не те, чи існує попередження, а скільки років залишається відкритим маршрут, що знаходиться за попередженням. У реєстрі налічується 44 маршрути з окремими доменами, 27 із яких мають опублікований файл доказів для кожного маршруту — див. таблицю нижче. Розгляньте один приклад, а потім проаналізуйте всі.\n\nРисунок 3.1 — Два маршрути на карті.\n\nОдна платформа, один користувач, два запити, що надходять з одного й того самого браузера. Фільтр посилань Valve діє на обидва запити. Він блокує той, що містить посилання, і пропускає той, що містить дані для входу. Усі показники, наведені в цьому розділі, відображають час, протягом якого нижній маршрут залишається відкритим.\n\nThe player\none browser, one session\nrollbit.com\nthe platform's main domain\nrbsnin.com\nseparate authentication host\nLINK FILTER\n✕ BLOCKED\nLINK FILTER\n✓ CLEAN\nsteamcommunity.com\nOpenID endpoint · signs in\nno route\nПосилання опубліковано в Steam — призупиненоЗапит на вхід — пропускиЗбережені чеки від 19 та 21 вересня 2026 року\n\nОбидва запити видимі для Valve, але виконується лише один із них. Фільтр посилань — це список Valve, який перевіряється службою Valve. Запит OpenID передає власне ім’я хосту автентифікації на кінцеву точку Valve, яка відразу ж відображає його на сторінці входу. Ім’я хосту в будь-якому випадку міститься у запиті — різниця полягає в тому, чи виконується з ним якась дія.\n\nОдна платформа. Два різних маршрути.ROLLBIT / ЗБЕРЕЖЕНІ СПОСТЕРЕЖЕННЯ\nКрок 5 / 5\n\nЗапит досягає Steam. Виявлений маршрут привів до форми входу користувача Steam. Автори не завершили процес входу. Блокування посилання на основний домен не заблокувало цей виявлений маршрут до форми.\n\n01 ПЕРЕВІРКА ФІЛЬТРА З’ЄДНАННЯ\nПункт призначенняrollbit.comОсновний домен платформи\nФІЛЬТР STEAM LINKПеревіряє посиланняОкрема система попередження про пункт призначення\nЗБЕРЕЖЕНИЙ РЕЗУЛЬТАТПосилання заблоковано19 та 21 вересня 2026 року\n02 ВІДМІЧЕНИЙ МАРШРУТ ВХОДУ\nНА ПЕРОНІУвійти за допомогою SteamПлатформа ініціює запит OpenID\nОКРЕМИЙ ХОСТ АВТЕНТИФІКАЦІЇrbsnin.comУ збереженому контролі відсутній блок «Фільтр посилань»\nSTEAMФорма входу відображенаЗапитаний хост згадується у повідомленні Steam\nПеревірте оригінальні записи про забір зразків, дату реєстрації та деталі протоколу\nЯк виглядає забезпечення дотримання Valve\nОсновний домен: заблоковано\nКористувач\n→\nrollbit.com\n(основний домен)\n↓\nФІЛЬТР STEAM LINK — ЗАБЛОКОВАНО\n«Посилання заблоковано!» — позначено як потенційно шкідливе\nСайт rollbit.com повернув повідомлення про блокування фільтром посилань для 2026-09-19 та 2026-09-21 (перевірка без автентифікації; збережено вихідний HTML-код та SHA-256). Видимий запис, що підлягає аудиту.\nЩо насправді відбувається — аутентифікація\nХост-автор: не заблоковано\nКористувач\n→\nrollbit.com\n«Увійти за допомогою Steam»\n↓\nПеренаправлення через окремий хост автентифікації:\nrbsnin.comФільтр посилань: CLEAN\nзареєстровано 2026-09-18T09:34:52Z (Verisign RDAP)\n↓\nSteam повідомлення на сторінці входу (2026-09-20):\n\"Note that rbsnin.com is not affiliated with Steam or Valve\"\nSteam відображає це повідомлення з домену OpenID (openid.realm) отриманого запиту.\n↓\nSteam форма входу, що обслуговується окремим хостом\nАвтори не завершили процес входу в систему; процес було простежено аж до форми Steam.\nValve отримує ім’я хосту return_to / realm при кожному такому запиті. rbsnin.com не повернув жодного блокування за фільтром посилань для 2026-09-21.\nНа запит\nЯк провайдер OpenID, Steam отримує ім’я хосту автентифікації з кожним запитом на автентифікацію: воно надходить на власні сервери Valve у вигляді openid.return_to та openid.realm параметри.\nНадіслано сайтом\nХост автентифікації не виявляється під час сканування — платформа вказує його як Steam у кожному запиті. Згідно з OpenID 2.0, §9.1 return_to формально є необов’язковим, але без нього Steam не може надати результат входу, тому для успішного входу за допомогою Steam він фактично є обов’язковим. Steam навіть відображає ім’я хоста користувачеві («<host> не пов’язаний із Steam або Valve\").\n14 років\n— це вік найстарішого хосту-аутентифікатора, який під час перевірки 2026-09-21 все ще має Steam входи (dota2.net, зареєстрований 2011-10-29); найновіший існує три дні (rbsnin.com). Не слід трактувати цифру «0 заблокованих хостів автентифікації» як результат дослідження. Заблокований хост автентифікації повністю виведе з ладу функцію платформи «Увійти за допомогою Steam», тому реєстр, створений на основі діючих облікових записів, може містити лише ті хости, які ніколи не блокувалися. Значущим є не кількість блокувань, а те, скільки років основний домен перебував у фільтрі посилань, тоді як логін поруч із ним продовжував працювати.\nХости з авторизацією в окремому домені: дата реєстрації порівняно з основним доменом (30 маршрутів: 25, які було визначено під час аудиту браузера 2026-09-21, плюс 5, доданих 2026-09-22)\nПлатформа\tФільтр посилань: головна\tХост-сервер автентифікації\tФільтр посилань: хост автентифікації\tЗареєстровано авторитетний хост\tДжерело спостереження\tДосьє з доказами\nRollbit\nrollbit.com · реєстрація 2014-11-08\n\tЗАБЛОКОВАНО\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\trbsnin.com\tОЧИСТИТИ\n2026-09-21 · необроблений HTML-код (знімка з Wayback немає)\n\t2026-09-18\n09:34:52Z, Verisign RDAP\n\tSteam повідомлення на сторінці входу, 2026-09-20\trollbit.com.json\nSkin.Club\nskin.club · реєстрація 2017-09-04\n\tЗАБЛОКОВАНО\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\tsc-auth.net\tОЧИСТИТИ\n2026-09-21 · Wayback 2026-09-21\n\t2019-04-02\nRDAP\n\tSteam повідомлення на сторінці входу\tskin.club.json\nHowl.GG\nhowl.gg · реєстрація 2017-03-16\n\tЗАБЛОКОВАНО\n2026-09-18, 19 вересня, 21 вересня · Wayback 2026-09-21\n\thowl.uno\tОЧИСТИТИ\n2026-09-21 · Wayback 2026-09-21\n\t2026-08-11\nRDAP\n\tЗйомка екрану браузера в режимі реального часу + надана URL-адреса OpenID\thowl.gg.json\nDuelbits\nduelbits.com · реєстрація 2020-02-03\n\tЗАБЛОКОВАНО\n2026-09-21 · Wayback 2026-09-21\n\tswitchflips.com\tОЧИСТИТИ\n2026-09-21 · Wayback 2026-09-21\n\t2020-04-21\nRDAP\n\tНадана URL-адреса OpenID\tduelbits.com.json\nCSGOFast\ncsgofast.com · реєстрація 2015-03-27\n\tЗАБЛОКОВАНО\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\tsteam-login.authtofast.com\tОЧИСТИТИ\nauthtofast.com, 2026-09-21 · Wayback 2026-09-21\n\t2026-06-30\nauthtofast.com, RDAP\n\tЗйомка екрана браузера в режимі реального часу + надана URL-адреса OpenID\tcsgofast.com.json\nFarmskins\nfarmskins.com · реєстрація 2016-03-23\n\tЗАБЛОКОВАНО\n2026-09-19, 2026-09-21 · необроблений HTML-код\n\tsteam.kobal.cc\tОЧИСТИТИ\n2026-09-19, 2026-09-21 · необроблений HTML-код\n\t2017-01-07\nkobal.cc, RDAP\n\tЗйомка екрану браузера в режимі реального часу + надана URL-адреса OpenID\tfarmskins.com.json\nCobaltLab\ncobaltlab.tech\n\tЗАБЛОКОВАНО\n2026-09-21 · необроблений HTML-код\n\tcobaltauth.com\tОЧИСТИТИ\n2026-09-21 · необроблений HTML-код\n\t2025-01-07\nRDAP\n\tНадана URL-адреса OpenID\tcobaltlab.tech.json\nCSGO.NET\ncsgo.net · зареєст. 2012-07-22\n\tЗАБЛОКОВАНО\n2026-09-21 · необроблений HTML-код\n\tcn2.easylot.net\tОЧИСТИТИ\n2026-09-21 · необроблений HTML-код\n\t2016-09-03\neasylot.net, RDAP\n\tЗапис екрану браузера в режимі реального часу\tcsgo.net.json\nGGDrop\nggdrop.com\n\tЗАБЛОКОВАНО\n2026-09-21 · необроблений HTML-код\n\tggauth.com\tОЧИСТИТИ\n2026-09-21 · необроблений HTML-код\n\t2023-05-03\nRDAP\n\tНадана URL-адреса OpenID\tggdrop.com.json\nRustChance\nrustchance.com\n\tЗАБЛОКОВАНО\n2026-09-21 · неоформований HTML-код\n\thgfuihd.com\tОЧИСТИТИ\n2026-09-21 · необроблений HTML-код\n\t2019-01-27\nRDAP\n\tНадана URL-адреса OpenID\trustchance.com.json\nSkin.Fans\nskin.fans\n\tЗАБЛОКОВАНО\n2026-09-21 · необроблений HTML-код\n\tauth.skinfans.com\tОЧИСТИТИ\n2026-09-21 · необроблений HTML-код\n\t2018-07-16\nskinfans.com, RDAP\n\tНадана URL-адреса OpenID\tskin.fans.json\nSkinport\nskinport.com · реєстрація 2018-09-05\n\tЗАБЛОКОВАНО\n2026-09-21 · необроблений HTML-код\n\tskinport.app\tОЧИСТИТИ\n2026-09-21 · необроблений HTML-код\n\t2020-06-20\nRDAP\n\tЗйомка екрану браузера в режимі реального часу + надана URL-адреса OpenID\tskinport.com.json\nSkins.Cash\nskins.cash\n\tЗАБЛОКОВАНО\n2026-09-21 · необроблений HTML-код\n\tskinscash.live\tОЧИСТИТИ\n2026-09-21 · необроблений HTML-код\n\t2019-12-05\nRDAP\n\tНадана URL-адреса OpenID\tskins.cash.json\nTF2Hunt\ntf2hunt.com · реєстрація 2018-01-13\n\tЗАБЛОКОВАНО\n2026-09-21 · необроблений HTML-код\n\trstspcl.com\tОЧИСТИТИ\n2026-09-21 · необроблений HTML-код\n\t2020-08-08\nRDAP\n\tЗйомка екрану браузера в режимі реального часу + надана URL-адреса OpenID\ttf2hunt.com.json\nCSGOGem\ncsgogem.com · рег. 2016-10-16\n\tЗАБЛОКОВАНО\n2026-09-22 · необроблений HTML-код\n\tapi.csgem.com\ncsgem.com — окремий домен, який можна зареєструвати\n\tОЧИСТИТИ\n2026-09-22 · необроблений HTML-код\n\t2014-03-08\ncsgem.com, RDAP — найстаріший у реєстрі\n\tРучне збирання + фіксація за допомогою фільтра посилань\tlinkfilter-2026-09-22.json\nGamdom\ngamdom.com · рег. 2016-07-29\n\tЗАБЛОКОВАНО\n2026-09-22 · необроблений HTML-код\n\tlogin.gambldom.com\ngambldom.com — лише одна літера відрізняється від назви бренду\n\tОЧИСТИТИ\n2026-09-22 · необроблений HTML-код\n\t2017-09-24\ngambldom.com, RDAP\n\tРучне збирання + Збір даних за допомогою фільтра посилань\tlinkfilter-2026-09-22.json\n12CS\n12cs.fail · reg. 2026-03-24\n\tЗАБЛОКОВАНО\n2026-09-22 · необроблений HTML-код\n\tfail.games\tОЧИСТИТИ\n2026-09-22 · необроблений HTML-код\n\t2021-08-24\nfail.games, RDAP\n\tРучне збирання + зчитування за допомогою фільтра посилань\tlinkfilter-2026-09-22.json\nCSGOEmpire\ncsgoempire.com · регістр. 2015-06-10\n\tОЧИСТИТИ\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\tcsgoempirelogin4.com\nодин із десяти пронумерованих доменів login1–10\n\tОЧИСТИТИ\n2026-09-21 · Wayback 2026-09-21\n\t2020-07-20\n05:49:17Z, Verisign RDAP\n\tЗапис екрану браузера в режимі реального часу\tcsgoempire.com.json\nCS.MONEY\ncs.money\n\tОЧИСТИТИ\n2026-09-21 · необроблений HTML-код\n\tauth.dota.trade\tОЧИСТИТИ\n2026-09-21 · необроблений HTML-код\n\t2016-07-15\ndota.trade, RDAP\n\tSteam повідомлення на сторінці входу\tcs.money.json\nCSFloat\ncsfloat.com · реєстрація 2021-07-11\n\tОЧИСТИТИ\n2026-09-21 · неоформлений HTML-код\n\tcsgofloat.com\nколишній домен бренду оператора; окремий домен, який можна зареєструвати, що не є ознакою спроби ухилення\n\tОЧИСТИТИ\n2026-09-21 · необроблений HTML-код\n\t2015-09-29\nRDAP\n\tЗапис екрану браузера в режимі реального часу\tcsfloat.com.json\nG4Skins\ng4skins.com\n\tОЧИСТИТИ\n2026-09-21 · необроблений HTML-код\n\tauth.g4s.to\tОЧИСТИТИ\n2026-09-21 · необроблений HTML-код\n\t2021-05-30\ng4s.to, RDAP\n\tНадана URL-адреса OpenID\tg4skins.com.json\nJuice.GG\njuice.gg\n\tОЧИСТИТИ\n2026-09-21 · необроблений HTML-код\n\tletmeinjuice.com\tОЧИСТИТИ\n2026-09-21 · необроблений HTML-код\n\t2024-04-15\nRDAP\n\tНадана URL-адреса OpenID\tjuice.gg.json\nMarket.CSGO\nmarket.csgo.com\n\tОЧИСТИТИ\n2026-09-21 · необроблений HTML-код\n\tdota2.net\tОЧИСТИТИ\n2026-09-21 · необроблений HTML-код\n\t2011-10-29\nRDAP\n\tЗйомка екрана браузера в режимі реального часу + надана URL-адреса OpenID\tmarket.csgo.com.json\nRust.TM\nrust.tm\n\tОЧИСТИТИ\n2026-09-21 · неоформлений HTML-код\n\tdota2.net\tОЧИСТИТИ\n2026-09-21 · необроблений HTML-код\n\t2011-10-29\nRDAP\n\tНадана URL-адреса OpenID\trust.tm.json\nCSGOLounge\ncsgolounge.com · регістр. 2013-08-14\n\tОЧИСТИТИ\n2026-09-22 · необроблений HTML-код\n\tdota2.net\nтретій інтерфейс на цьому хості автентифікації\n\tОЧИСТИТИ\n2026-09-22 · необроблений HTML-код\n\t2011-10-29\ndota2.net, RDAP\n\tРучне збирання даних + Збір даних за допомогою фільтра посилань\tlinkfilter-2026-09-22.json\nDota2Lounge\ndota2lounge.com · зареєстровано 2012-08-10\n\tОЧИСТИТИ\n2026-09-22 · необроблений HTML-код\n\tdota2.net\nчетвертий інтерфейс на цьому хості автентифікації\n\tОЧИСТИТИ\n2026-09-22 · необроблений HTML-код\n\t2011-10-29\ndota2.net, RDAP\n\tРучне збирання + збір даних за допомогою фільтра посилань\tlinkfilter-2026-09-22.json\nSkinBaron\nskinbaron.de\n\tОЧИСТИТИ\n2026-09-21 · необроблений HTML-код\n\tskinbaron.com\nодна й та сама марка, різні домени верхнього рівня\n\tОЧИСТИТИ\n2026-09-21 · необроблений HTML-код\n\t2015-12-22\nRDAP\n\tНадана URL-адреса OpenID\tskinbaron.de.json\nTF2Royal\ntf2royal.com · регістр. 2022-08-17\n\tОЧИСТИТИ\n2026-09-21 · необроблений HTML-код\n\ttf2auth.com\tОЧИСТИТИ\n2026-09-21 · необроблений HTML-код\n\t2021-07-27\nRDAP\n\tЗйомка екрану браузера в режимі реального часу + надана URL-адреса OpenID\ttf2royal.com.json\nTradeit\ntradeit.gg\n\tОЧИСТИТИ\n2026-09-21 · необроблений HTML-код\n\tconnect-tradeit.com\tОЧИСТИТИ\n2026-09-21 · необроблений HTML-код\n\t2022-02-23\nRDAP\n\tНадана URL-адреса OpenID\ttradeit.gg.json\nМодернізатор\nupgrader.pro\n\tОЧИСТИТИ\n2026-09-21 · необроблений HTML-код\n\tupgauth.space\tОЧИСТИТИ\n2026-09-21 · необроблений HTML-код\n\t2026-08-14\nRDAP\n\tНадана URL-адреса OpenID\tupgrader.pro.json\nДжерело: steamcommunity.com/linkfilter, GET без автентифікації, 2026-09-21, 53 хости, інтервал 3 с; steam_tos_assets/linkfilter-recheck-2026-09-21.json; необроблений HTML у steam_tos_assets/linkfilter-raw/. Терміни реєстрації: RDAP, steam_tos_assets/domain-registration.json. · Попередня перевірка значення 2026-09-19 у linkfilter-all-results.json · записи маршрутів у auth-route-audit.json · Знімки сторінок «Link Filter», 2026-09-21, збережені в Wayback Machine, перелічені в wayback-snapshots.json (знімка для rbsnin.com не існує; єдиним записом є локальний файл у вихідному форматі).\n\nТерміни реєстрації: RDAP (steam_tos_assets/domain-registry/). «Вказана URL-адреса OpenID» визначає параметри запиту, а не завершений процес входу. Автори не здійснювали входу на жодній платформі. Наявність окремого домену сама по собі не є доказом обходу. Так само «0 заблокованих хостів автентифікації» не є самостійним висновком: блокування одного з них порушило б процес входу на цій платформі, тому реєстр, складений на основі успішних входів, не може містити заблокований хост автентифікації. Вагомим є саме спостереження щодо сполучення та його тривалості — головний домен у фільтрі посилань поруч із доменом для входу, що функціонує вже роками. Ця таблиця містить 30 рядків: 25 із 27 маршрутів із файлом доказів для кожного маршруту, а також п’ять, доданих у 2026-09-22, розподіл яких у фільтрі посилань зафіксовано в linkfilter-2026-09-22.json хоча самі домени були зібрані вручну — про це свідчать рядки у стовпці «джерело». Два маршрути з файлів доказів, які не показано, — це skinsnipe.com (авторизований хост pricing.tradeupspy.com, зареєстрований 2020-03-11) та csgobig.com (авторизований хост letmeinbig.com, зареєстрований 2023-01-20); обидва повернули результат «BLOCKED main / CLEAN auth host» під час перевірки 2026-09-22, записаний з використанням SHA-256 у linkfilter-2026-09-22c.json, але вихідний HTML-код для цього пакету відсутній у опублікованому наборі, тому вони тут лише названі, а не представлені у вигляді рядка, як це зроблено для всіх інших рядків у цій таблиці. Решта 12 маршрутів у реєстрі, зібраних вручну, позначені як такі в master_registry.json під realm_src: user.\n\nПервинний емпіричний аудит · Багаторічний діапазон дат\nПастка «загальної картини»: фільтр посилань — це лише імітація дотримання вимог, а не захист\n\nУ настільних браузерах користувачі захищені зовнішніми засобами безпеки: функції Google Safe Browsing та Microsoft SmartScreen перехоплюють відомі фішингові атаки, відображаючи повноекранні червоні попередження. У режимі «Big Picture» Steam, ігровому оверлейі (Shift+Tab) та на панелі Steam (SteamOS) ці засоби захисту відсутні. Вбудований браузер не підтримує жодних розширень, вимикає зовнішні механізми «Безпечного перегляду» і залишає користувачеві лише один захисний бар’єр: Valve's linkfilter інтерстиціальний.\n\nГортайте, щоб порівняти всі чотири результати →\n\n92.5%\n2025–2026: сучасні методи фішингу пройшов без зауважень (37/40)\n77.5%\nФішинг у період CS2 (2023–2024) пройшов без зауважень (31/40)\n70.0%\nФішинг, пов’язаний із 2021–2022 роками пройшов без зауважень (28/40)\n7 / 7\nблокування мереж азартних ігор (позитивний контроль)\nБагаторічний лонгітудінальний аудит: 120 доменів, що є чистими Steam фішинговими, перевірено в режимі реального часу (24 вересня 2026 р.)\n\nЩоб перевірити, чи фільтр Valve просто повільно реагує на нові загрози, чи принципово не здатний їх виявляти, ми провели перевірку 120 підтверджених фішингових доменів, пов’язаних із Steam у трьох історичних когортах порівняно з steamcommunity.com/linkfilter:\n\n1-й набір: 2021–2022 (класичні пропозиції обміну та випадання предметів) — 70.0% Без помилок (28/40). Навіть через 4–5 років після того, як їх було занесено до реєстру громадськими організаціями з моніторингу, 7 із 10 старих фішингових хостів досі працюють без будь-яких обмежень.\n2-й набір: 2023–2024 (CS2 Beta Hype & Fake Support Appeals) — 77.5% Без помилок (31/40). Кампанії, що видають себе за анонси виходу Counter-Strike 2, та фальшиві звернення до спільноти (наприклад, cs2-steam.com, appealsteamcommunity.help) проходять наскрізь.\n3-я група: 2025–2026 (безсерверні розгортання на периферії та клонування фавіконів) — 92.5% Повністю успішно (37/40). Сучасні фішингові набори, що розгортаються на EdgeOne, Vercel та Cloudflare Pages (наприклад, steamgifter.online, steam-dp4lt5b8fnez.edgeone.dev) проходять практично без перешкод.\n\nТелеметрія та захист від відповідальності, а не захист. Навіщо взагалі існує фільтр посилань, якщо він пропускає 70% до 92.5% випадків явного фішингу Steam? Він виконує функцію корпоративного застереження щодо відповідальності та датчика телеметрії вихідних кліків. Представляючи ввічливе «Ви залишаєте Steam» повідомлення з зеленою кнопкою «Продовжити», на яку можна натиснути, Valve перекладає юридичну відповідальність на жертву відповідно до Steam Угоди з абонентом (*«користувач добровільно перейшов за межі Steam»*). Valve збирає телеметричні дані про клік, але не блокує крадіжку.\n\nДоказ безпеки Favicon Hash: повна відсутність обробки даних про загрози. Незалежні платформи аналізу загроз (urlscan.io, Shodan, Censys) виявляють активні Steam фішингові набори за допомогою простого пошуку за офіційним хешем фавікону Steam (page.favicon.hash:9f890a9debcdfccc339149a7943be9aff9e4c9203c2fa37d5671a5b2c88503ad NOT domain:*.steampowered.com). Ця базова автоматизована перевірка виявляє активні фішингові кластери за лічені секунди. Valve не синхронізується із зовнішніми джерелами даних, не здійснює пошук загроз на основі хеш-значень і втручається вручну лише у випадках, коли це вимагають регуляторні органи (наприклад, постанова WSGC щодо азартних ігор від 2016 року) або з метою захисту своїх доменних імен, що є торговими марками.\n\nОсновні артефакти, що є аудиторськими доказами: Багаторічний подовжній аудит із 120 доменами: longitudinal-steam-phishing-audit.json · 100 спеціалізованих зразків фішингових атак Steam: linkfilter-steam-phishing-100.json · Комплексний аудит кормів (n=250): linkfilter-coverage-2026-09-22.json.\n\nCSGOEmpire — пакетна реєстрація десяти пронумерованих доменів для авторизації\n\nПро 2020-07-20 десять пронумерованих доменів, csgoempirelogin1.com через csgoempirelogin10.com, були зареєстровані. Для всіх десяти збережено мітки часу RDAP від Verisign: login1 05:49:06Z, login5 05:49:08Z, login2 05:49:11Z, login3 05:49:14Z, login4 05:49:17Z, login6 05:49:20Z, login7 05:49:23Z, login8 05:49:26Z, login9 05:49:28Z — дев'ять доменів за 22 секунди — а також login10 о 05:56:03Z, через сім хвилин. Інтервал між записом відповідає одній масовій операції реєстратора.\n\nЦя схема відповідає заздалегідь підготовленим резервним хостам; лише login4 це було виявлено в реальному запиті OpenID. Сайти csgoempire.com та csgoempirelogin4.com обидва отримали статус «CLEAN» у фільтрі посилань на 2026-09-21; CSGOEmpire не входив до переліку сайтів, згаданих у пресі у зв’язку з повідомленнями від липня 2016 року.\n\n# DNS — усі 10 активні (вересень 2026 року)\nГаразд csgoempirelogin1.com 172.67.129.43\nГаразд csgoempirelogin2.com 172.67.175.168\nГаразд csgoempirelogin3.com 188.114.96.3\nГаразд csgoempirelogin4.com 188.114.96.11 ← у трафіку OpenID\nГаразд csgoempirelogin5.com 172.67.160.194\nГаразд csgoempirelogin6–10.com IP-адреси Cloudflare\nNXDOMAIN: csgoempirelogin11.com\nУсі 10 зареєстровані 2020-07-20; усі 10 мають мітку часу RDAP (steam_tos_assets/domain-registry/csgoempireloginN.com.rdap.json)\nВисновок для регуляторних органів\nЗаблокований основний домен у поєднанні з розблокованим хостом автентифікації залишає маршрут входу відкритим — і він залишається відкритим роками.\n\nБлок «Link Filter» на головному домені є перевіреним публічним записом. Хост автентифікації передає трафік «Увійти за допомогою Steam» і з’являється у параметрах запиту OpenID самого Valve. Під час перевірок 2026-09-21 та 2026-09-22 у 26 парах, розділених фільтром, головний домен повернув блок «Link Filter», тоді як проксі-сервер, що передавав дані для входу, не повернув жодного. Наведений вище реєстр фіксує іншу половину цього: ці хости не є короткочасними одноразовими доменами. Деякі з них на момент перевірки були зареєстровані вже понад десять років, і кожен із цих днів — це день, коли Valve отримував ім’я хосту у власних параметрах запиту. Valve не опублікував жодних даних щодо заходів щодо дотримання правил за операторами, тому на основі відкритих даних неможливо встановити, чи застосовувалися до цих хостів якісь інші заходи.\n\nWhat this means — the Steam Link Filter\n\nValve’s own blocklist for links leaving Steam. Click a listed address inside the client and an interstitial appears instead of the page. It acts on the link that is posted, not on the login a site performs, and it is the only such check that runs inside the Steam client.\n\nSection 3.1 — why it is the only layer →\n\n12 років 6 місяців\nСайт csgogem.com заблоковано у фільтрі посилань.\nЙого хост для входу api.csgem.com був\nзареєстрований з 2014-03-08, але це не так.\nКороткий виклад простою мовою — для регуляторних органів та судів (розгорнути)\nКороткий виклад простою мовою — для регуляторних органів\nВступ: Що таке Steam і чому це має значення в даному контексті\n\nSteam — це програмна платформа, яку експлуатує корпорація Valve (Белв’ю, Вашингтон, США). Steam виконує функції постачальника цифрової ідентифікації: веб-сайти, присвячені азартним іграм та іграм в Інтернеті, використовують систему під назвою «Увійти через Steam» — кнопку, яка дозволяє веб-сайту перевірити, чи має відвідувач справжній обліковий запис Steam. Це схоже на функцію «Увійти через Google» або перевірку посвідчення особи, виданого державою: веб-сайт перенаправляє користувача на сервери Steam, Steam підтверджує його особу, а Steam повертає його на веб-сайт. Valve забезпечує роботу системи автентифікації. Кожен вхід за допомогою функції «Увійти через Steam» проходить через власні сервери Valve.\n\nЩо зробив Valve: Блокування домену\n\nУ липні 2016 року, у відповідь на тиск з боку ЗМІ та юридичних органів щодо азартних ігор із ставками у вигляді «скінів», юридичний представник компанії Valve надіслав повідомлення приблизно 23 конкретним азартним сайтам (згідно з повідомленнями преси від 21 липня 2016 року); у жовтні 2016 року Valve повідомила Комісії з азартних ігор штату Вашингтон, що зв’язалася з понад сорока сайтами. Деякі домени азартних ігор з’являються в Steam Фільтр посилань — список, завдяки якому при будь-якому розміщенні посилання на них у Steam (у чаті, на сторінці профілю, у магазині) відображається сторінка з попередженням: «Посилання заблоковано!» Фільтр зв’язків — це єдиний засіб контролю, ефект якого можна спостерігати ззовні Valve.\n\nПриклад: Посилання на rollbit.com всередині Steam відображається сторінка з попередженням «Link Filter» (відмічено 2026-09-19 та 2026-09-21). Теоретично сайт з азартними іграми заблоковано.\nЩо таке проксі-домен\n\nА Хост автентифікації з окремим доменом є проксі-сервером автентифікації: друга адреса веб-сайту, розташована на іншому домені, що підлягає реєстрації, яку той самий оператор розміщує між своїми користувачами та Steam виключно з метою реалізації кроку «Увійти за допомогою Steam». Вона виконує роль проксі-сервера для входу. Користувач вважає, що входить на платформу; запит, який надходить до Valve, містить ім’я хосту проксі-сервера, а не платформи. Зазвичай він не має публічно помітного зв’язку з сайтом азартних ігор, і саме на цю адресу повертаються користувачі після того, як Steam підтверджує їхню особу.\n\nПриклад: Rollbit працює на основі rollbit.com, яку блокує фільтр Link Filter. Для аутентифікації Steam потік, зафіксований на 2026-09-20, використовував окрему адресу: rbsnin.com, зареєстрована 2026-09-18. Ця адреса повернула блок «Фільтр посилань» відсутній на 2026-09-21. Сайт азартних ігор продовжував працювати, а його Steam процес входу здійснювався через розблокований хост.\nКритична точка: у кожному запиті хост автентифікації передається як Steam\n\nValve не потребує сканування чи обходу, щоб дізнатися, які хости автентифікації використовуються. Steam — це Постачальник ідентифікаційних даних OpenID для цих сайтів, і кожне натискання кнопки «Увійти за допомогою Steam» надсилає GET-запит на власні сервери Valve, що містить ім’я хосту автентифікації у вигляді відкритого тексту. Відповідно до OpenID 2.0 §9.1, return_to Це поле формально є необов’язковим, але без нього Steam не може надати результат входу, тому для успішного входу Steam воно фактично є обов’язковим. Сам Steam відображає ім’я хоста на сторінці входу («<host> не пов’язаний із Steam або Valve\").\n\n— Формат запиту, який отримує Steam (хост, як зафіксовано для Rollbit на 2026-09-20): —\nОТРИМАТИ steamcommunity.com/openid/login\n&openid.mode=checkid_setup\n&openid.return_to=https://rbsnin.com/… ← фактично обов’язкове; потрапляє до журналу Valve\n&openid.realm=https://rbsnin.com ← зазначено самим сайтом; відображається на сторінці входу користувача Steam\nЯкщо сайт використовує перевірку «сервер-сервер» (check_authentication), у журналі Valve також фіксуються IP-адреса сервера платформи та мережа хостингу.\n\nВитягнення імені хоста з цього запиту є стандартною операцією. Запис про застосування заходів — щодо яких хостів були вжиті заходи, щодо яких ні, та за якими критеріями — існує лише в інфраструктурі Valve і не оприлюднювався.\n\nЩо це доводить\n\n1. Блок «Фільтр посилань» діє на посилання, а не на логіни. Блокування основного домену (наприклад, rollbit.com) відображає попередження для користувачів, які натискають на посилання на нього всередині Steam. Це не заважає роботі сайту, а також не перешкоджає використанню власного сервісу OpenID Valve через іншу адресу.\n\n2. Перевірені хости автентифікації не були заблоковані. У таблиці вище наведено хости з авторизацією в окремих доменах, зареєстровані в період з 2011 року по вересень 2026 року; деякі з них — через кілька років після повідомлень, надісланих у липні 2016 року. У 26 парах основний домен повернув блокування Link Filter, а проксі-сервер, що передавав дані для входу, — ні (перевірки без автентифікації, 2026-09-21 та 2026-09-22; збережено необроблені відповіді та SHA-256). Цей проксі-сервер припиняв роботу в той день, коли Valve відхилив його запит, тому критерієм тут є тривалість його роботи, а не те, чи є він у списку. Valve отримує ці імена хостів у своїх власних запитах OpenID. Чи застосовувалися якісь інші заходи, крім фільтра посилань, неможливо визначити на основі публічних даних, оскільки Valve не опублікував жодних записів про застосування заходів щодо окремих операторів.\n\n3. Сайти продовжували проходити аутентифікацію через інфраструктуру Valve. «Увійти за допомогою Steam» — це сервіс Valve; кожна аутентифікація через нього є запитом, який Valve отримує та обробляє. Valve також отримує дохід від ключів кейсів, а ринок спільноти Steam стягує сукупну комісію в розмірі приблизно 15% за транзакції, здійснені всередині ринку (але не за зовнішні угоди). Дія «Фільтр посилань» створила публічний запис; вона не перервала відносини аутентифікації.\n\nЧи допомогло б блокування?\n\nЗа аналогією: коли у 2023 році припинив свою діяльність реєстратор безкоштовних доменів Freenom, фішингові кампанії, що базувалися на його доменах, були зведені нанівець. Безперебійність роботи залежить від стабільності інфраструктури.\n\nТут діє та сама логіка. Якщо хост автентифікації було відхилено під час обробки OpenID Steam, функція платформи «Увійти за допомогою Steam» не працюватиме доти, доки не буде зареєстровано новий хост, видано сертифікати та оновлено DNS. Протягом цього періоду відбуватиметься простой.\n\nРотація не робить блокування марним. Це перетворює блокування на операційні витрати. Оскільки під час першого використання нові хости з’являються у власних журналах запитів Valve, швидкість обробки відповіді може залежати від швидкості цього першого використання.\n\nСама по собі пакетна реєстрація є сигналом: Користувачі CSGOEmpire з іменами login1–login10 були зареєстровані на 2020-07-20, причому дев’ять із них — протягом 22 секунд (Verisign RDAP). Відповідь не обов’язково має надаватися для кожного домену окремо; послідовну серію запитів з одного сеансу реєстратора можна розглядати як єдину серію.\n\nУ відкритих даних не зафіксовано випадків спроб блокування авторизаційних хостів, які були нейтралізовані завдяки ротації.\nТут показано основні домени, заблоковані, хоча проксі-сервери, що обслуговували кожен вхід, продовжували працювати — 26 пар станом на 2026-09-22, найстаріший хост автентифікації зареєстрований 12 років і 6 місяців тому — і жодних опублікованих даних про застосування санкцій щодо будь-якого оператора.\nОтже, перед регулятором постає таке питання: які заходи щодо забезпечення дотримання вимог, якщо такі взагалі існують, застосовував Valve до авторизованих хостів, інформацію про які він отримує у своїх власних запитах OpenID?\nЩо зробив Valve — і чому це не перервало шлях автентифікації\n\nУ таблиці нижче наведено відповідність кожної публічно задокументованої дії Valve щодо того, чи вплинула вона на точку входу для автентифікації OpenID. Висновок полягає не в тому, що «Valve нічого не зробив», а в тому, що жодна з публічно задокументованих дій не торкнулася точки, через яку вхід на ігрові платформи проходить через сервери Valve.\n\nДата\tValve Дія\tУражені openid.return_to шлях?\nЛипень 2016 року\tПублічна заява від 13 липня 2016 року; повідомлення адвоката, надіслані приблизно 23 зазначеним ресурсам (преса, 21 липня 2016 року); зв’язано з понад 40 ресурсами відповідно до листа Valve від жовтня 2016 року на адресу WSGC\tНі. Повідомлення та фільтр посилань діють на оператори та посилання; шлях запиту OpenID не змінився.\n2017\tЗакриття IEconItems_730/GetPlayerItems (за даними інженерного акаунта CSFloat; журнал змін Valve не знайдено)\tНі. Це вплинуло на видимість історії публічних елементів. Аутентифікація за допомогою OpenID не зазнала змін.\n2018-03-29\tОголошено про 7-денну блокування торгівлі в CS:GO (blog.counter-strike.net)\tНі. Сповільнено переміщення елементів; шлях запиту OpenID не змінився.\n2022-05-10\tКінцеві точки скасування угод видалено з публічного веб-API (виявлено користувачем; у журналі змін немає запису Valve — node-steam-tradeoffer-manager #325)\tНі. Функціонал обміну пропозиціями було вимкнено; система автентифікації OpenID не зазнала змін.\n2023-12-04\tДля створення API-ключа тепер потрібне підтвердження через мобільний телефон (steamcommunity.com/dev/apikey; без журналу змін)\tНі. Ключова кінцева точка була захищена; описані тут хости автентифікації не зазнали впливу.\n2026-09-19 / 21 вересня\tSteam Стан фільтра «Link», за даними авторів\tУ 14 основних доменах під час повторної перевірки збереженого 2026-09-21 було виявлено блокування — 26 розділених пар у реєстрі за 2026-09-22 — тоді як проксі-сервер, що обробляв кожен вхід, продовжував працювати.\nДжерела: Valve заява від 13 липня 2016 року (store.steampowered.com/oldnews/22883, архів 2026-09-21) · Технічний звіт компанії CSFloat щодо закриття у 2017 році (blog.csfloat.com, архів 2026-09-21) · Стан фільтра посилань: linkfilter-recheck-2026-09-21.json.\nЦей висновок можна спростувати, якщо опублікувати хоча б один випадок, коли Valve відхилив запит OpenID через те, що openid.return_to вказував на хост, що має ліцензію на азартні ігри. У відкритих джерелах такий екземпляр не було виявлено.\nДві останні реєстрації авторизаційних хостів\nhowl.unoбув зареєстрований 2026-08-11 (RDAP) за 41 день до 2026-09-21; сервіс howl.gg повернув повідомлення про блокування фільтром посилань для 2026-09-18, 2026-09-19 та 2026-09-21. Чи відбулося блокування до реєстрації, встановити не вдалося.\nrbsnin.comбуло зареєстровано 2026-09-18T09:34:52Z (Verisign RDAP) і було виявлено в процесі входу на сайт Rollbit Steam 2026-09-20 через повідомлення на власній сторінці входу Steam; rollbit.com повернув блокування фільтра посилань 2026-09-19 та 2026-09-21, а rbsnin.com — ні.\nКожен хост із наведеної вище таблиці надсилається на сервери автентифікації Valve у вигляді openid.realm при кожній спробі входу в систему.\nПовні дані щодо кожного маршруту та висновки фільтра Link Filter: таблиця у розділі 3 вище; необроблені результати наведено в linkfilter-recheck-2026-09-21.json та linkfilter-all-results.json.\nМетодологія — Як було визначено показники фільтрації маршрутів та зв’язків\n1. Розпізнавання доменів\nУ ході аудиту 2026-09-21 було перевірено 78 із 189 заявлених платформ: 33 проходять автентифікацію за власним іменем хоста, а 20 — за власним піддоменом — це пряма автентифікація, і жоден із них не враховується як маршрут окремого домену. Решта 25. Пройти аутентифікацію через окремий домен, який можна зареєструвати, розподілені між 24 різними іменами хостів (dota2.net використовується спільно з market.csgo.com та rust.tm): 10 — виявлено за допомогою знімків екрана браузера в режимі реального часу, 3 — завдяки повідомленню на сторінці входу від Steam, 12 — за наданим URL-адресою OpenID. Реєстр у режимі реального часу (master_registry.json, 2026-09-22) розширює це до 44 маршрути з окремими доменами: 26 пар з розділенням за фільтром (головний домен — BLOCKED, хост автентифікації — CLEAN) плюс 18 додаткових маршрутів без розділення за головним доменом. З цих 44, 27. мати при собі досьє з доказами для кожного маршруту; решту 17 було зібрано вручну, і вони мають відповідні позначки realm_src: user у реєстрі. П’ять із цих сімнадцяти — csgogem.com, gamdom.com, 12cs.fail, csgolounge.com та dota2lounge.com — були додані 2026-09-22 із фіксацією обох хостів за допомогою Link Filter (необроблений HTML + SHA-256 у linkfilter-2026-09-22.json), тож сам факт поділу підтверджується, незважаючи на те, що дані про домени зібрано вручну; вони наведені у таблиці вище поряд із маршрутами з файлу доказів. tfauth.com (tf2easy.com) було вилучено з реєстру о 2026-09-22: як і у випадку з arena.fragnet.net, немає жодних підтверджених даних, що пов’язують його з вихідним сайтом. Кількість можна знову обчислити на основі опублікованих auth-route-audit.json (послідовність 2026-09-21) за одним правилом: платформа враховується лише в тому випадку, якщо її спостережуваний хост OpenID Steam розміщений у домені, що підлягає реєстрації, відмінному від домену самої платформи.\n2. Steam Стан фільтра посилань\nПеревірено за допомогою steamcommunity.com/linkfilter/?url=https://[domain], без автентифікації, на 2026-09-19 та 2026-09-21; необроблений HTML збережено з використанням SHA-256. Статус фіксується окремо для основного домену та хосту автентифікації. Класифікатор розрізняє загальне повідомлення «Ви залишаєте Steam» (CLEAN) та сторінку «Посилання заблоковано! ... позначено як потенційно шкідливе» (BLOCKED); контрольний домен google.com підтверджує, що ці два варіанти не змішуються. Раніший варіант цього тесту з автентифікацією було відхилено після того, як він повертав результат «заблоковано» для кожного домену, включаючи цей контрольний — причиною виявився недійсний сесійний файл cookie у скрипті тесту, а не реальний результат.\n3. Спостереження за хостом-автором\nЗапис у реальному часі: браузер Playwright переходив до процедури входу на кожній платформі, а openid.return_to Ім'я хосту було отримано з перехопленого запиту. Повідомлення на сторінці входу: ім'я хосту було отримано з власного файлу Steam \"<host> не пов’язаний із Steam або Valve\" текст, який Steam відображає з openid.realm (rbsnin.com, sc-auth.net, auth.dota.trade). Наданий URL-адресу: a Steam — URL-адреса форми входу, надана авторам; вона визначає параметри запиту, а не завершену процедуру входу. На жодній платформі процедура входу не була завершена.\n4. Огляд — що залишилося невирішеним і чому це має значення\nЗ 189 платформ, 110 не мав визначеного маршруту а один випадок не підпадав під критерії (189 − 78 − 1). У цьому досьє жоден із них не враховано. Розподіл цих 110 випадків, згідно з аудиторським файлом: 22 випадки перевірки на ботів, 14 випадків перевищення часу очікування, 12 випадків помилок HTTP та 10 випадків помилок навігації — спостерігач не зміг дістатися до процесу входу, хоча більшість цих сайтів нормально відкриваються у звичайному браузері; 20 не мали Steam елемента контролю входу на цільовій сторінці; 16 дійшли до процесу входу, який не вдалося вирішити на рівні хосту; 11 доменів не вирішувалися в DNS; 5 зупинилися на сторінці з проханням про згоду. У наведеному нижче реєстрі ці 110 випадків розподілено інакше: 11, які не розпізнавалися в системі DNS, наведено окремо як Видалено · NXDOMAIN, і той запис, до якого це не стосується, приєднується до решти. Перевірено 189 платформ, 11 видалено через остаточний результат NXDOMAIN з обох резолверів, 178 збережено (platform-audit.json, platforms-removed.json). 137 доменів автентифікації, які реєстр впізнав за шаблоном імен, було видалено з даних на 2026-09-19 — їх ніколи не спостерігали, отже, вони ніколи не були доказами. Три з цих припущень суперечили наданим URL-адресам OpenID: buff.163.com, gamerpay.gg та csgoluck.com здійснюють автентифікацію безпосередньо, на відміну від припущень щодо buffauthproxy.163.com, gamerpayredirect.io та lucklogin.app. Вилучені записи наведено в опублікованому файлі аудиту.\nЦифра 25 є мінімальним показником, а не максимальним. Серед 78 платформ, для яких вдалося встановити ідентифікацію, 25 використовували окремий домен, а 53 — ні. Цей співвідношення не дає підстав для будь-яких припущень щодо 110 платформ, для яких ідентифікацію встановити не вдалося, і жодних прогнозів на його основі в цьому досьє не наводиться. Кожну з них можна вирішити, якщо відкрити сайт і натиснути «Увійти за допомогою Steam»: ім’я хосту для автентифікації міститься в URL-адресі сторінки Steam, що завантажується.\nСуть цього розділу: Незалежному спостерігачеві знадобився браузер і чимало терпіння, щоб визначити 189 платформ, але він виявив лише 78. Для Valve потрібен запит до бази даних. Кожна платформа, яка використовує функцію «Увійти через Steam» — як визначені, так і невизначені — надсилає openid.realm до точки кінцевої аутентифікації Valve під час кожного входу в систему. Прогалина в цій таблиці пояснюється тим, що автори перебувають поза системою. Для Valve такої прогалини немає.\nВиявлені імена хостів-проксі знаходяться у auth-route-audit.json. Дати реєстрації доменів за даними RDAP (Verisign) / IP2WHOIS. Результати фільтрації за посиланнями: linkfilter-all-results.json.\nАналогія для наочності\n\nУявіть, що регуляторні органи повідомляють ліцензованій таксомоторній компанії, що вона більше не може здійснювати діяльність за своєю зареєстрованою адресою на Мейн-стріт. Компанія знімає вивіску з Мейн-стріт. Факт зняття вивіски фіксується. Однак ця ж компанія відкриває офіс за адресою на Сайд-стріт — зареєстрований під іншим ім’ям — і продовжує працювати звідти. Регулюючі органи керують централізованою диспетчерською системою, якою користуються всі таксі з обох адрес. У кожному запиті на поїздку вказано «забір з Сайд-стріт». Регулюючі органи ніколи не анулюють ліцензію на Сайд-стріт. Єдиним заходом з боку правоохоронних органів стало зняття вивіски «Main Street». Таксі-компанія ніколи не припиняла свою діяльність.\n\nЧастина А — Технічна документація · Розділ 3.1\nУ Steam список Valve є єдиним списком.\n\nПосилання, на яке натиснули в клієнті Steam, ігровому оверлеї або режимі Big Picture, не відкривається в браузері користувача. Воно відображається у вбудованому браузері Steam, де відсутні попереджувальні шари, які зазвичай застосовує браузер. Фільтр посилань — це не просто один із багатьох заходів безпеки. Це і є весь захід безпеки.\n\nУ звичайному браузеріТри незалежні шари\nБезпечний перегляд від GoogleПовносторінкове проміжне вікно для хостів, що знаходяться у списках Google щодо фішингу та шкідливого програмного забезпечення, яке постійно оновлюється незалежно від того, який саме сайт відвідується.\nАнтивірусне розширення для браузераБільшість кінцевих продуктів для споживачів постачаються з розширенням для браузера, яке перевіряє адресата на відповідність власному списку репутації виробника.\nПеревірка HTTPS на кінцевих точкахЯкщо продукт здійснює перевірку за протоколом TLS, вміст сторінки сканується до того, як він потрапить до користувача.\nУ клієнті Steam: накладення та режим Big PictureОдин шар\nБезпечний перегляд від GoogleВідсутні. Для виконання перевірки потрібні ключі API Google, які не надаються у вбудованих збірках Chromium; у разі їх відсутності, згідно з власною проектною документацією Chromium, обробник «Безпечного перегляду» просто ніколи не додається до ланцюжка запитів.\nАнтивірусне розширення для браузераВідсутній. Рендерер Steam не є браузером користувача і не завантажує жодних розширень із профілю браузера користувача, тому на цій сторінці не працює жодне доповнення.\nПеревірка HTTPS на кінцевих точкахЗалежить від продукту. Трафік завершується всередині процесу Valve із цифровим підписом, а не у впізнаваному браузері, і низка кінцевих продуктів не піддають підписані додатки перевірці TLS.\nФільтр посилань SteamВласний список заблокованих адрес Valve, до якого звертаються, коли посилання виходить за межі екосистеми Steam. Це єдина перевірка, яка виконується — і в таблиці вище зафіксовано результати, які вона повертає для хостів автентифікації, описаних у цьому розділі.\nЦе перевірка, яку може провести будь-який читач, і якщо вона не пройде, висновок втрачає свою силу\n\nВідкрийте одну з опублікованих компанією Google тестових URL-адрес для перевірки «Безпечного перегляду» (testsafebrowsing.appspot.com) у Chrome: з’являється повноекранне червоне проміжне вікно. Відкрийте той самий URL-адресу з повідомлення чату Steam так, щоб вона відображалася в клієнті Steam або у накладному вікні: проміжне вікно не з’являється. Єдиним попередженням, яке може з’явитися у Steam, є власна сторінка фільтрації посилань, і лише для хостів зі списку Valve.\n\nРекорд Valve у програмі винагород за виявлення помилокЦей трек вже звучав раніше — на альбомі самого Valve\n\nЯкщо фільтр посилань є єдиною перевіркою, що виконується всередині клієнта, то його власні режими відмови не є другорядним питанням. Два звіти в рамках програми HackerOne від Valve: обидва прийняті, обидва вирішені, обидва згодом оприлюднені в повному обсязі:\n\n#291750архів 2025-11-16 ↗Open Redirect · Medium\nОбхід захисту фільтра посилань\n\nПовідомлено 19 листопада 2017 року, усунуто, оприлюднено 9 травня 2018 року. Власний приклад підтвердження концепції, наведений у звіті: заміна ідеографічної крапки 。 (%E3%80%82) для крапки в імені хоста — блокування можна обійти. Інтерстиціальний елемент, про який йдеться в цьому розділі, не з’явився.\n\n#1079561архів 2026-09-24 ↗Розкриття інформації · високий рівень\nВеб-браузер Big Picture розкриває файли cookie для входу та конфіденційну інформацію (що може призвести до захоплення облікового запису)\n\nПовідомлено 15 січня 2021 року, вирішено, оприлюднено 21 вересня 2021 року. Власна оцінка серйозності Valve є високою, а в заголовку вказано наслідки. Оприлюднений запис містить назву, оцінку та дати; технічний опис не входить до опублікованого вмісту, тому з нього тут більше нічого не наводиться.\n\nЦе — власна інтерпретація авторів, а не висновок жодного з цих звітів: обидва вони розташовані по обидва боки одних і тих самих воріт. Одне з них — це попередження, яке не з’являється до того, як відкриється сторінка призначення; інше — це сесія, яка залишає клієнтський пристрій після відкриття сторінки всередині неї. Послідовність подій, що настає після викрадення сесії — реєстрація ключа без запиту, скасування справжньої операції, надсилання дубліката на клонований пристрій — є схемою, викладеною в Розділ 5 до Розділ 8. Обидва звіти закрито; жоден із них не розглядається як актуальна вразливість. Висновки, зроблені в них, є більш вузькими, але достатніми: єдиний шар, що залишився, має задокументовану історію обходу, про що свідчать власні записи Valve.\n\nДжерело: запис про оприлюднення на платформі HackerOne для кожного повідомлення, отримано 2026-09-22 — номер, назва, команда, вразливість, рівень серйозності, дати подання та оприлюднення повідомлення, а також статус, як опубліковано HackerOne. Запис про отримання: hackerone-reports.json. Сума винагороди тут не вказана; її також немає в оприлюднених документах, які вдалося знайти.\n\nПольові спостереження · PhishDestroyВиявлення, які зазвичай призводять до припинення кампанії, у цьому випадку не призвели до її припинення\n\nМи спостерігали, як фішингові хости продовжували залучати трафік, при цьому перенаправляючи 20 або більше виявлених постачальників. Якщо така кампанія реалізується через веб або електронну пошту, вона в цьому стані припиняє дію за лічені дні — і браузер, і антивірус реагують на ці висновки. У Steam ж ні той, ні інший цього не робить. Ці висновки існували весь час. Клієнт ніколи про це не запитував.\n\nЩо це означає для неповнолітнього, у якого встановлено антивірус\n\nВін не ігнорує жодного попередження і нічого не вимикає. У Steam з’являється повідомлення — безкоштовний ніж, голос за команду друга — і сторінка відкривається в Steam. Він ніколи не відкриває браузер, тому браузер ніколи його не захищає. Його антивірус працює і, можливо, вже визначив цей домен як шкідливий; але його ніхто не запитує. Усі застереження, які могли б його зупинити, вже існують. Але жодне з них до нього не доходить. Він вважає, що ніколи не залишав Steam, і це справді так.\n\nЦя акція — не вигадка фішера: сайти зі скінами та азартними іграми рекламують себе саме так — пропонують безкоштовні Valve предмети, і саме тому це повідомлення виглядає цілком звичайним. Скарги: архів виконавчих справ. Дані про вік та дітей: Розділ 17.\n\nДжерела: Steam відображає веб-вміст за допомогою Chromium Embedded Framework у steamwebhelper процес — див. Технічний аналіз DARKNAVY від 27 червня 2024 року ↗ та власний Valve Steam Форум «Client Beta» ↗ архів 2025-08-04 ↗. Не використовується жодна версія CEF: вбудований Chromium — це не Chrome, і він не містить жодних сервісів Google, що є в Chrome. Безпечний перегляд без API-ключів: Документ з описом дизайну Chromium ↗ архів 2026-08-21 ↗, Ключі API Chromium ↗ архів 2026-08-30 ↗ («Багато API-інтерфейсів Google, які використовує Chrome, є специфічними для Google і не призначені для використання у похідних продуктах»), і той самий ефект спостерігається в інших збірках без ключа — Домашнє пиво з бочки № 193814 ↗. URL-адреси для тестування: testsafebrowsing.appspot.com ↗.\n\nДва різних годинники\nВік домену.Дата спостереження.\n\nДата створення реєстру визначає, коли було зареєстровано домен. Запис OpenID із датою визначає хост-сервер, що повертає цей запис. Перше не може охоплювати роки, що передують другому.\n\nПовний реєстр розрізняє окремий домен, що підлягає реєстрації, власний субдомен сайту та прямий маршрут. Кожен рядок містить посилання на джерело та результат DNS.\n\nПереглянути реєстр доменів →· Завантажити дати реєстрації ↗· Повторити спостереження ↗\n\nЧастина А — Технічна документація · Розділ 4\nКінцева точка закрита. У публічному трасуванні втрачено ключ.\nКонтекст та обмеження щодо джерел\n\nSteam було впроваджено зміни, які прибрали публічну видимість ідентифікаторів активів (Asset ID) та обмежили доступ до інвентарю через API. Наслідок: відстежити конкретний предмет за його оригінальним ідентифікатором активу стало неможливо на основі публічних даних. Далі йдеться про те, що було можливим раніше, що стало неможливим після цього, і чого це коштує жертві, яка намагається довести, куди поділося її майно. Згідно з інженерним обліковим записом CSFloat, це сталося у 2017 році; журналу змін Valve виявлено не було. Ця послідовність подій — приблизно через рік після заяви про азартні ігри від липня 2016 року — є предметом розслідування, а не висновком. Самі записи про предмети залишаються в системах Valve; зовнішні дослідники втратили доступ до ланцюжка оригінальних ідентифікаторів, тоді як ідентифікатори float, seed та paint дозволяють лише часткове зіставлення.\n\nДіє правило Valve: Steam Служба підтримки не відновлює елементи, які були видалені з вашого облікового запису, і обов’язок довести, що саме сталося, лежить на вас. Запис: У 2017 році Valve закрив кінцеву точку, яка передавала оригінальні ідентифікатори предметів. До цього будь-хто міг відстежити викрадений скін з облікового запису жертви аж до бота на торговому майданчику. Після цього ніхто за межами Valve не може цього зробити. Доказ, який вимагають від потерпілого, — це той самий доказ, який було підмінено — і вона досі існує, всередині Valve.\n\nЕпоха до відключення електроенергії\n\nІсторично кожен віртуальний об’єкт, створений на Steam, мав глобально унікальний, незмінний Ідентифікатор активу. Сторонні бази даних OSINT можуть індексувати ці ідентифікатори. Якщо у користувача викрали товар, слідчі зможуть простежити шлях руху цього конкретного активу від проміжного рахунку зловмисника до рахунків зберігання на торговельному майданчику або сайті азартних ігор.\n\nРАНІШЕ: будь-хто міг простежити шлях переказу коштів з рахунку жертви через проміжні рахунки аж до торговельного майданчика або бота-сховища казино, використовуючи загальнодоступні дані.\nПісля зміни\n\nЗгідно з інформацією з технічного профілю CSFloat, у 2017 році Valve закрив кінцеву точку, і оригінальні ідентифікатори предметів перестали бути доступними для сторонніх осіб. Не було знайдено жодної заяви Valve щодо причини таких змін. У той самий період також не було виявлено жодних оприлюднених заходів проти комерційних бот-акаунтів, які здійснювали масові операції з товарами.\n\nНезалежно від причини, ця зміна порушила публічний ланцюжок відстеження. Потерпілий більше не може відтворити ланцюжок оригінальних ідентифікаторів на основі публічних даних, щоб довести, що конкретний викрадений предмет був реалізований через певний торговий майданчик або казино. Записи про ці предмети все ще існують у системах Valve; громадськість, дослідники та правоохоронні органи, які працюють з публічними даними, не мають до них доступу.\n\nПІСЛЯ: відстежити конкретний об’єкт за його оригінальним ідентифікатором активу (Asset ID) на основі загальнодоступних даних більше неможливо. Ланцюг відповідальності за оригінальним ідентифікатором для об’єкта, переміщеного після 2017 року, існує лише в інфраструктурі Valve; жодних таких записів публічно не оприлюднено. Ідентифікатори Float, seed та paint дозволяють лише часткове, ймовірнісне зіставлення.\nIEconItems_730\nОТРИМАТИ/IEconItems_730/GetPlayerItems/v1/\nВідстежуваний корисний вантаж (до випуску виправлення)\n\"id\": \"14892281934\",\n\"original_id\": \"11829910211\",\nСтатус: Потерпілий може відстежувати шлях переміщення предмета між акаунтами-ботами.\nЗашифрований корисний вантаж (після застосування виправлення)\nПоточний\n\"id\": \"HIDDEN_BY_PRIVACY_SETTINGS\",\n\"original_id\": \"NULL\",\nСтатус: сторонні особи більше не можуть відстежувати історію об’єкта за оригінальним ідентифікатором активу на основі загальнодоступних даних.\nВплив на докази: Після внесення змін публічні дані, необхідні для відстеження конкретного об’єкта за його оригінальним ідентифікатором активу (Asset ID) від облікового запису потерпілого до бота на торговельному майданчику чи в казино, стали недоступними. Внутрішні записи все ще існують у Valve; жертва, дослідник або слідчий, які працюють на основі публічних даних, не можуть відтворити ланцюжок оригінальних ідентифікаторів (ідентифікатори float, seed та paint дозволяють лише часткове зіставлення).\n\nДжерело: Звіт інженерної компанії CSFloat про закриття у 2017 році IEconItems_730/GetPlayerItems — blog.csfloat.com/how-floatdb-tracks-items (архів 2026-09-21) · наведені дані є ілюстрацією форми поля, а не записаними відповідями · журнал змін Valve для цього закриття не знайдено.\n\nЧастина А — Технічна документація · Розділ 5\nОдин сеанс. Більше прав доступу, ніж бачить користувач.\nКонтекст та обмеження джерел\n\nАрхітектура API-ключів Valve у тому вигляді, в якому вона існувала до змін 2023 року, відхилялася від базових галузевих стандартів (OWASP ASVS, NIST SP 800-63B) і є тим механізмом, який описано в автоматизованих скаргах щодо крадіжки інвентарю, що зберігаються в архіві доказів (розділи 6–8).\n\nЗастосовано правило Valve: власник рахунку створив ключ, погодився з умовами та несе відповідальність за збитки — саме така відповідь міститься в архіві відмов. Запис: До грудня 2023 року для реєстрації цього ключа достатньо було лише викраденого сесійного кукі. Без пароля. Без Steam Guard. Без повідомлення власника цього облікового запису. Користувач не створював цей ключ, не бачив його, але йому сказали, що він це зробив. Функція підтвердження через мобільний телефон була додана 2023-12-04 — приблизно через сім років після заяви 2016 року та приблизно через шість років після створення шахрайських панелей, які зберігаються в архіві. Ці роки не оплачувалися Valve. Їх оплачували рахунки, які за цей час були спустошені, частина з яких належала дітям.\n\nOWASP ASVS 2.8 / NIST SP 800-63BРІВЕНЬ СЕРЙОЗНОСТІ: КРИТИЧНИЙ\n1. Недостатній рівень посиленої аутентифікації\n\nSteam дозволяло створювати API-ключі з високим рівнем привілеїв і тривалим терміном дії, використовуючи лише сесійний файл cookie. Під час налаштування або зміни ключа API для розробників не вимагалося двофакторної автентифікації (Steam Guard) або додаткового запиту на підтвердження, тому мобільне підтвердження Steam Guard — єдиний другий фактор, який пропонує Steam — не забезпечувало захист цього етапу. (У 2016 році у власному трекері Valve було запропоновано впровадити апаратний другий фактор, і це питання досі залишається відкритим: Додаток D, GH-01.)\n\nСтатус: не виправлено до 2023 року. Дозволяло скрипту, що містив викрадене cookie, зареєструвати ключ без будь-якої взаємодії з користувачем.\nOWASP A01:2021 / Принцип мінімальних привілеївРІВЕНЬ СЕРЙОЗНОСТІ: КРИТИЧНИЙ\n2. Відсутність принципу мінімальних привілеїв\n\nУ веб-API Steam були відсутні будь-які області авторизації на основі ролей. Ключ API розробника, виданий для перегляду стану запасів у режимі «тільки для читання», мав повні права на «запис» — зокрема, можливість вносити зміни в існуючі угоди, ініціювати нові, реєструвати веб-хуки та відхиляти дійсні угоди, що перебувають на розгляді.\n\nСтатус: системний конструктивний недолік. Один ключ = повний контроль над запасами та операціями на рахунку (читання/запис).\nOWASP A07:2021 / СесіїРІВЕНЬ НЕБЕЗПЕКИ: ВИСОКИЙ\n3. Порушення управління сесіями\n\nКористувачі повідомляли про випадки, коли викрадені веб-сесії, що походили з IP-діапазонів, на яких розміщувалися сервери, продовжували існувати. Згідно зі стандартною практикою, сесії припиняються у разі виявлення географічних аномалій та після зміни пароля; у звітах користувачів, зібраних в архіві, описано випадки, коли сесії залишалися активними після зміни пароля.\n\nСтатус: зафіксована проблема (скарги користувачів в архіві). Під час сеансів можна було генерувати API-ключі без повторної автентифікації.\nБлокування на рівні домену було технічно можливимМОЖЛИВІСТЬ ЗАБЕЗПЕЧЕННЯ ВИКОНАННЯ\n4. Блокування хостів автентифікації на рівні домену було технічно можливим\n\nValve вже використовує список доменів (фільтр посилань) і отримує кожне ім’я хоста для авторизації у своїх власних запитах OpenID. Ці два механізми жодним чином не пов’язані між собою, що помітно ззовні: станом на 2026-09-22 у 26 парах основний домен був у фільтрі, тоді як проксі-сервер, що здійснював вхід, — ні.\n\nЗ'єднати їх — це невелике інженерне завдання: прочитайте openid.realm визначати ім'я хоста з кожного вхідного запиту, порівнювати його зі списком та відхиляти або позначати такий запит. На ілюстрації праворуч показано схему роботи такої процедури. Відхилення хоста, що здійснює автентифікацію, — а не лише загальнодоступної цільової сторінки — призведе до переривання етапу «Увійти за допомогою Steam», від якого залежать ці платформи.\n\nНемає жодних публічних доказів того, що Valve проводить таку перевірку. Сукупна комісія Steam Community Market у розмірі приблизно 15% застосовується до угод, укладених на цій платформі; вона не стягується з угод, укладених за межами цих платформ.\n\nblock_auth_hosts.pyІЛЮСТРАЦІЯ\n// Зчитати, що хост Steam вже отримує — сканування не проводити\ndef on_openid_request(request):\nhost = parse_openid_realm(request)\nякщо господар в заблоковані_домени:\nвідхилити (запит)\nПримітка: псевдокод наведено лише для ілюстрації. Обидві частини вже існують на Valve — ім’я хоста авторизації надходить у запиті, а список доменів є фільтром посилань. Жоден загальнодоступний запис не пояснює, чому вони не пов’язані між собою.\nРозділ 5.1 — Ці стандарти не були опубліковані\nValve щодня компілюється з дотриманням цих правил. У цьому випадку компіляція не пройшла з дотриманням цих правил.\n\nSteam реалізується в App Store та Google Play, здійснює продажі через основні платіжні системи та використовує сторонні API, як і будь-яка інша велика платформа. Кожен із цих взаємозв’язків передбачає опубліковані вимоги щодо безпеки з зазначеними датами, яким Valve має відповідати, щоб продовжувати свою діяльність. Порівняйте дати цих вимог із датами, коли власний веб-API Steam отримав такі самі заходи захисту. Ніщо з наведеного нижче не є внутрішнім стандартом, службовою запискою чи комерційною таємницею: кожен рядок — це публічний документ із зазначеною датою оприлюднення.\n\nОпубліковані зовнішні вимоги до безпеки із зазначенням їхніх дат у порівнянні з датою, коли веб-API Steam запровадив еквівалентні заходи контролю\nОпублікований стандарт та дата його вступу в силу\tВеб-API Steam щодо того самого питання\nАвторизація з обмеженим обсягом повноваженьOAuth 2.0 — RFC 6749, Жовтень 2012 року. У розділі 3.3 наведено визначення scope Таким чином, клієнт отримує лише той доступ, про який він просить. Відтоді це стало стандартом для API всіх основних платформ.\tЗ’явилися детальні сфери застосування 16 січня 2026 року.До цього один ключ Web API типу Steam надавав повні права на читання та запис щодо всіх торгових операцій облікового запису, незалежно від мети його видачі. Тринадцять років і три місяці після специфікації, що визначає елемент управління.\nКлюч — це не дозвілОфіційна документація Google щодо хмарних сервісів: Стандартний ключ API не забезпечує автентифікацію суб’єкта, а також для API, які створюють ресурси або керують ними, Не використовуйте ключі авторизації в виробничому середовищі.\tКлюч Web API Steam був саме таким.Строка-номінка, видана для рахунку, яка сама по собі дає право переглянути стан рахунку, скасувати очікуване торговельне операцію та надіслати нову. На момент використання ідентифікація власника не проводилася.\nБагатофакторна автентифікація при привілейованому доступіPCI DSS 3.2, вимога 8.3 — обов’язкова з 1 лютого 2018 року для всіх випадків адміністрування, що не здійснюється через консоль, та для всіх випадків віддаленого доступу до середовища зберігання даних власників карток. Згодом компанія Apple запровадила вимогу щодо двофакторної автентифікації для кожного власника облікового запису в програмі для розробників, починаючи з 27 лютого 2019 року: Розробники, які мають роль «Власник облікового запису» у програмі для розробників, повинні увімкнути двофакторну автентифікацію, щоб увійти в систему.\tДля створення API-ключа з було потрібно ще одне 4 грудня 2023 року.До цього часу викраденого сесійного файлу cookie було достатньо: на телефоні власника облікового запису не з’являлося жодного запиту, і після цього не надходило жодного повідомлення. Чотири роки та дев’ять місяців після того, як компанія Apple змусила Valve використовувати другий фактор автентифікації навіть для простого входу на портал для розробників.\nЖиттєвий цикл та анулювання посвідченьTwitch висуває такі вимоги до кожного стороннього додатка: Ваш додаток повинен перевіряти токен OAuth під час запуску, а потім — щогодини, і зазначає, що проводить аудит додатків, які цього не роблять. Його застарілий API версії 5 було остаточно виведено з експлуатації 28 лютого 2022 року згідно з опублікованим розкладом.\tНе опубліковано жодних даних щодо життєвого циклу ключа.Зміна 2023 року забезпечила захист кінцевої точки створення. Жодна з пов’язаних із нею інструкцій Valve не стосується вже зареєстрованих ключів, а до цієї зміни взагалі не було додано журналу змін. На основі відкритих даних неможливо встановити, чи були ключі, створені до цього, визнані недійсними — а саме на це питання суб’єкту даних потрібно отримати відповідь, щоб дізнатися, чи ключ, створений на його обліковому записі кілька років тому, все ще діє.\nАрхітектурний еталон // Token Architecture\nДрібні області дії GitHub проти Valve Steam Web API\n\nValve розробників щодня керують програмним забезпеченням з відкритим кодом на GitHub, використовуючи токени з деталізованими правами доступу за принципом «мінімальних привілеїв». Порівняйте це з монолітною ключовою парою, виданою 130 млн Steam гравців.\n\nТокен GitHub з високим рівнем деталізації\nВикористовується користувачем Valve на GitHub\n\nТокен з дрібною структурою, що забезпечує ізоляцію в межах області дії та обов’язкове дотримання життєвого циклу.\n\nДоступ до репозиторію:Тільки вибрані репозиторії (1 репозиторій)\nНадання дозволів:Тільки для читання [✓]\nКод і секрети:Доступ відсутній [✕]\nТермін дії:30 днів (обов’язковий TTL)\nРеєстрація аудиту:IP-адреса, User-Agent та час запису\nСтан безпеки: Токен з мінімальними привілеями обмежує збитки лише одним ресурсом, доступним лише для читання.\n!Valve Steam Ключ веб-API\nВидано 130 млн користувачів\n\nЄдиний головний рядок довжиною 32 символи, що містить повноваження щодо торгівлі та управління запасами за принципом «все або нічого».\n\nДоступ до облікового запису:ПОВНА ВЕРСІЯ (Монолітна)\nУправління торгівлею:Прочитати, Скасувати, Відхилити [!]\nРівні деталізації:НІ (Прибуло у 2026 році, із запізненням на 13 років)\nТермін дії:НІКОЛИ (Дійсно безстроково)\nРеєстрація аудиту:НІ (Історія IP-адрес користувача відсутня)\nУразливість: Викрадений ключ дає змогу непомітно перехоплювати всі вихідні торгові пропозиції.\nСтандарт, що застосовується в одному напрямку\n\nПрипустимо, що постачальник Valve — хмарний провайдер, платіжна система чи CDN — залишив кінцеву точку для введення облікових даних без другого фактора аутентифікації, і через кілька місяців власні корпоративні дані Valve витекли через ключ, згенерований на цій кінцевій точці. Чи погодився б Valve з тим, що вина лежить на тому, хто натиснув на посилання? Архівні відмови, збережені в цьому досьє, дають відповідь на дзеркальне запитання для користувача: займається позиція, що власник облікового запису створив ключ і несе відповідальність за втрату. Цю саму архітектуру описують як «відсутність відповідальності постачальника в одному напрямку та відповідальність користувача — в іншому». Те, що це саме так, не є технічним питанням, і це питання не може бути вирішене в рамках цього розслідування — рішення щодо цього приймає суд або наглядовий орган.\n\nІлюстрація, а не доказ — стандарт, прочитаний навпаки\nПлатіжна система, яка дозволяла сторонньому скрипту генерувати облікові дані для транзакції з повними правами доступу виключно на основі файлу cookie браузера, без будь-якого попередження власника облікового запису.\nПровайдер ідентифікації, який усунув вразливість, через яку було випущено його токени, і не опублікував жодної інформації про вже випущені токени.\nБанк, який у відповідь на оскарження переказу зазначив, що використані облікові дані були зареєстровані на власному рахунку клієнта, і закрив заявку.\n\nЖодне з цих тверджень не подається як висновок щодо будь-якої конкретної компанії. Це ті самі проектні рішення, перенесені в контекст, де реакція наглядових органів добре задокументована — саме таке порівняння і пропонується зробити регуляторному органу.\n\nЩо встановлено матеріалами справи: контрольні механізми, яких не було у веб-API Steam, були загальнодоступними, застарілими, а в деяких випадках — умовами, Valve які компанія мала дотримуватися, щоб продовжувати постачання власної продукції. Інтервал між кожним стандартом та відповідною зміною Steam є вимірюваним і наведено вище. Однак це не пояснює, чому саме. Жодного Valve обґрунтування щодо жодного з цих проміжків часу виявлено не було, і тут воно не припускається; цей запис міститься в Valve і не опублікований.\n\nДжерела, кожне з яких є публічним документом: OAuth 2.0 — RFC 6749, жовтень 2012 року ↗ · Google Cloud — Документація щодо ключів API ↗ · Вимога 8.3 стандарту PCI DSS 3.2 — Довідник ресурсів PCI SSC ↗ · Apple — Майбутня вимога щодо двофакторної автентифікації для власників рахунків, 20 лютого 2019 року ↗ архів 2025-05-06 ↗ · Twitch — вимога щодо перевірки дійсності токена ↗ та Повідомлення про припинення роботи версії 5 ↗ архів 2025-01-27 ↗. Дати, вказані Steam, — це дати із запису про оновлення в цьому розділі; записи за 2023 та 2026 роки — це ті, які Valve випустив без журналу змін. Отримано 2026-09-22.\n\nВласний запис про оновлення Valve — із зазначенням дати, взятий із відкритих джерел\nДата\tValve змінити\tОголошено?\tЩо було закрито\tЗатримка: механізм «public» → виправлено\tДжерело\n2026-09-01\tАвтоматичне позначення підозрілих чатів\tТак\tНебезпечні посилання / шаблони у групових чатах\t—\tновини ↗\n2026-01-16\tДетальні області дії веб-API Steamworks\tТак\tОбласті дії з мінімальними правами для ключів розробників\t—\tоголошення ↗\n2025-07-15\tCS2: Захист від ринкових коливань та вікно розвороту\tТак\tНічого. Це не є виправленням, що усуває першопричину проблеми безпеки. Доступ служби підтримки до відновлення облікового запису залишається незмінним. Запуск операції скасування призводить до автоматичного 30-денного блокування торгівлі (Skinvault ↗), тоді як шок на ринку готівкових торгів спричинив падіння ринкової капіталізації за 24 години на $104M (-25%) (CSMarketCap ↗). У 2026 році таймери стали індивідуальними для кожного товару (Skin.land ↗).\t—\tЧасті запитання ↗\n2025-05-14\tПовідомлення щодо безпеки облікового запису\tТак\tІнструкції щодо програм-викрадачів / перехоплення сеансів\t—\tоголошення ↗\n2024-10-02\tCS2 «The Armory» — 7-денна затримка\tТак\tТоргівля/ринок предметів «Зброярні» тимчасово призупинено\t—\tоголошення ↗\n2024-09-18\tОбмеження щодо реєстрації нових пристроїв\tТак\tБлокування торгівлі на 2–7 днів на нових пристроях\t—\tЧасті запитання ↗\n2024-02-14\tПризупинення зміни імені профілю та аватара\tТак\tПісля зміни імені діє 2–4-годинний період очікування для здійснення угод\t—\tпублікація ↗\n2023-12-04\tМобільне підтвердження ключів API\tЖодних змін\tТиха реєстрація ключа виключно за допомогою файлів cookie\t≈6 років після випуску панелей 2017 року\tсторінка розробника ↗\n2023-10-24\tSMS MFA для публікації версій ігор\tТак\tПублікація збірки Steamworks\t—\tоголошення ↗\n2023-07-12\tПопередження щодо вмісту біографії, створеної на замовлення\tТак\tФішингові посилання в біографіях\t—\tфорум ↗\n2023-01-25\tПрофіль {ПОСИЛАННЯ ВИДАЛЕНО} та час відновлення\tТак\tПосилання в тексті профілю\t—\tЧасті запитання ↗\n2022-10-24\tОновлення системи входу та скорочення файлів cookie\tЖодних змін\tНескінченна кількість викрадених сеансів\t— (Міграція токенів служби IAuthenticationService)\tновини ↗\n2022-10-12\tМобільний додаток 3.0: вхід за допомогою QR-коду\tТак\tПанель скасування авторизації сеансу\t—\tновини ↗\n2022-05-10\tВидалено кінцеві точки скасування угод\tЖодних змін\tОбмін пропозиціями (скасування та повторне надсилання)\tприблизно через 5 років після випуску панелей 2017 року\tвипуск № 325 ↗\n2020-05-25\t7-денна блокування торгівлі в Dota 2\tТак\tШвидка перепродаж товарів\t—\tблог ↗\n2018-03-29\t7-денна блокування торгівлі в CS:GO\tТак\tМиттєве «відмивання» ботів\t≈20 місяців після заяви, зробленої в липні 2016 року\tблог ↗ архів 2025-02-26 ↗\nДжерела: публікації за посиланням Valve, сторінки довідки та запити на GitHub із зазначеними датами. Три вирішальні виправлення, випущені без журналу змін (травень 2022 р., жовтень 2022 р., грудень 2023 р.), були виявлені користувачами, а не оголошені Valve — ця асиметрія є частиною історії впровадження. Затримки обчислюються лише в тих випадках, коли власна дата досьє (заява від липня 2016 року; шахрайські панелі 2017 року) надає початкову точку; «—» означає, що така початкова точка тут не встановлена.\nЧастина А — Технічна документація · Розділ 6\nІнтерактивний симулятор експлойтів та захоплення контролю\nКонтекст та обмеження джерел\n\nРеконструкція ланцюжка подій від фішингового повідомлення до реєстрації ключа на стороні сервера та обміну. До 2023 року ключ Web API, зареєстрований на обліковому записі, міг зчитувати його запаси, скасовувати пропозицію про угоду, що перебувала на розгляді, та створювати нову, причому під час жодної з цих дій власнику облікового запису не відображався екран підтвердження угоди. Це є порушенням принципу «найменших привілеїв» (OWASP A01:2021). Часові показники в цій симуляції наведені для ілюстрації та не є реальними вимірами поточної роботи платформи.\n\nПройдіть крок за кроком відтворений процес викрадення облікового запису. На кожному етапі показано, що бачить власник облікового запису, а поруч — дзвінок, який отримує номер Steam у той самий момент. Кожен із цих дзвінків проходить належну аутентифікацію. Жоден елемент у цій послідовності не повинен вимагати, щоб аутентифікація Steam завершилася невдачею — важливо, щоб ключ, який вона видає, не мав жодної сфери дії (OWASP A01:2021).\n\nЩо бачить гравець. Що змінюється за його спиною.СИМУЛЯТОР ПРОХОДЖЕННЯ ГРИ\nКрок 5 / 5\n\nЕксплойт виконано. Очікуючи на мобільне сповіщення щодо своєї початкової операції, жертва затверджує заміну операції. Це інтегрований криміналістичний покроковий аналіз, який демонструє, як відсутність принципу «мінімальних привілеїв» (OWASP A01:2021) уможливлює автоматизоване викрадення активів за частку секунди.\n\n01 / ПРИМАНКА ДЛЯ ЧАТУДруг просить проголосуватиЖертва отримує повідомлення з посиланням.\n02 / ВХІДПортал-двійникЖертва вводить дані для входу.\n03 / ДОСТУПСтворення API «Silent Web»Зловмисник реєструє ключ розробника.\n04 / ПЕРЕКЛЮЧЕННЯЗамінено законну торгівлюБот «Clone» створює дублікат цільового одержувача.\n05 / ПІДТВЕРДЖЕННЯПідробка затвердженаНа мобільному пристрої було затверджено неправильну пропозицію.\nТой самий крок, якщо дивитися з точки зору мережіВідтворення структури до 2023 року · ілюстративні форми дзвінків\nПотерпілийЗатверджує мобільне запит, який передбачався для початкової угоди.\nНападникОтримує товари на рахунок-клон.\nSteam переглядівПереказ, підтверджений власником рахунку на зареєстрованому пристрої.\nConfirmation genuine — made by the account holder\nRecipient the clone bot, not the intended counterparty\nThe confirmation is authentic. The offer it confirms is not the one the user initiated.\n\nЗалишений слід: операція, яку користувач затвердив. Саме цей запис Steam служба підтримки переглядає при надходженні скарги, і саме це є причиною, чому архівні скарги були закриті як «помилка користувача». Скарги знаходяться в архів виконавчих справ.\n\nЧастина А — Технічна документація · Розділ 7\nКінцеві точки, що лежать в основі послідовності.\nКонтекст та обмеження джерел\n\nЦе — Steam кінцеві точки веб-API, які, як повідомляється, використовували скрипти для перехоплення операцій без проходження етапів підтвердження на стороні браузера.\n\nЧотири задокументовані кінцеві точки виконують усю роботу. Жодна з них не є вразливістю, жодну з них не потрібно експлуатувати — їх викликає дійсний ключ, і Steam відповідає. Ключ — це єдине, що зловмиснику потрібно було викрасти.\n\nIEconService / GetTradeOffers / v1ОПИТУВАННЯ\n\nВикористовується для моніторингу торгових пропозицій облікового запису. Скрипти періодично надсилають запити на цей кінцевий пункт, використовуючи викрадений ключ API; він повертає детальну інформацію про новостворені, очікувані або змінені торгові пропозиції. Інтервали запитів тут не вимірюються.\n\nВектор загрози: Відображає ідентифікатори очікуючих торгових пропозицій та дані профілю одержувача.\nIEconService / CancelTradeOffer / v1ВЗАЄМОДІЯ\n\nВикористовується для програмного скасування законної торгової пропозиції користувача. До 2023 року ключ не захищався додатковою автентифікацією, тому автоматизований сервер міг скасувати пропозицію одразу після її виявлення, без будь-якого попередження власника облікового запису.\n\nВектор загрози: Скасовує операцію до того, як власник рахунку завершить підтвердження через мобільний телефон.\nISteamUser / GetPlayerSummaries / v2RECON\n\nЗдійснено запит для отримання імені профілю, URL-адреси зображення аватара та рівня легітимного одержувача торгової операції. Це дозволяє скрипту налаштувати підготовлений клонований обліковий запис відповідно до цих даних. Час виконання тут не вимірюється.\n\nВектор загрози: Надає дані, необхідні для того, щоб видати себе за передбачуваного одержувача.\n/dev/ajaxregisterkeyСТВОРЕННЯ\n\nSteam — кінцева точка реєстрації ключів. Раніше будь-яка активна сесія файлів cookie браузера (`steamLoginSecure`) могла зареєструвати ключ без підтвердження Steam Guard на мобільному пристрої та без будь-якого повідомлення власника облікового запису.\n\nВектор загрози: Постійні облікові дані, створені за допомогою скрипта, про що власник облікового запису не знає.\nЧастина А — Технічний звіт · Розділ 8 · Стаття 7 GDPR\nПозначка у полі. Чия дія?\nКонтекст та обмеження джерел\n\nУ разі відмови у відшкодуванні Steam у відповідях служби підтримки, збережених в архіві, висловлюється думка, що власник облікового запису створив API-ключ і, поставивши галочку, погодився з умовами.\n\nУ відповіді служби підтримки вказано, що ключ належить власнику облікового запису. Питання полягає в тому, чи дозволяє цей запис встановити, хто насправді його створив.\n\nОднак у виявленому випадку викрадення API-ключа жертва ніколи не бачила сторінку створення API-ключа і не переходила на неї. Поле згоди відправляється скриптом, який виконує POST-запит у режимі «headless» із використанням викраденого сесійного кукі.\n\nВідповідно до статті 7 та статті 4(11) GDPR, згода має бути добровільним, конкретним, усвідомленим та однозначним вираженням волі суб’єкта даних. На думку авторів, поле для прийняття умов, яке відправляється шкідливим скриптом із викраденим файлом cookie, без відображення сторінки для власника облікового запису, не може відповідати цьому визначенню. Визначення того, чи відповідає воно цьому визначенню, належить до компетенції наглядового органу.\n\nКриміналістичний аналіз корисного навантаження: реєстрація ключів\nПУБЛІКАЦІЯ https://steamcommunity.com/dev/ajaxregisterkey\n// Дані запиту (введені за допомогою скрипта для перехоплення)\n{\n\"agreeToTerms\": \"погоджуюся\", <-- введено машиною, без участі людини\n\"домен\": «localhost», ← не перевірено — приймається будь-яке значення, включаючи localhost\n\"sessionid\": \"8f0d8ef763ab2140bf89de2a\"\n}\nПитання до наглядового органу: якщо власник рахунку ніколи не натискав на поле згоди, чи відповідає зафіксоване для цього рахунку підтвердження згоди з умовами вимогам статті 7 щодо добровільного, конкретного, обізнаного та однозначного вираження волі суб’єкта даних, а також чи може служба підтримки Steam посилатися на це для відхилення претензії.\n\nДжерело: форма запиту на реєстрацію ключа, відтворена на основі публічної кінцевої точки та звітів про викрадення, що зберігаються в архіві доказів (версія 2026-09-17 з можливістю пошуку) · показаний ідентифікатор сеансу є заповнювачем місця, а не записаним значенням.\n\nСудово-медична експертиза · Вектор заміщення товарів\nЯк Valve нарешті подолав проблему «заміщення товарів» — і чому на це знадобилося 7 років обхідних рішень\n\nПротягом майже десятиліття «Підміна API-ключа» (або шахрайство типу «Man-in-the-Middle» з використанням API) була найприбутковішою моделлю крадіжки акаунтів на Steam, завдяки якій з нічого не підозрюючих гравців було викрадено скіни на сотні мільйонів доларів. Valve не усунула цю вразливість шляхом виправлення вразливої архітектури API; натомість Valve протягом семи років наклала чотири рівні бар’єрів на всій платформі, що паралізували ліквідність торгівлі в спільноті, не вирішивши при цьому першопричину проблеми.\n\n1. «Смерть мімікрії»\nЧас відновлення аватара та імені (лютий 2024 р.)\n\nЦей зловмисний код вимагав миттєвої імітації: шахрайський бот перехоплював вихідний торговий запит і зчитував аватар та ім’я одержувача за допомогою ISteamUser, і скопіював профіль за 200 мс. 14 лютого 2024 року Valve непомітно запровадив обов’язкове Час відновлення торгівлі — від 2 до 4 годин (Помилка 34) відразу після будь-якої зміни імені профілю або аватара. Бот більше не може миттєво клонувати одержувача, не блокуючи при цьому свою можливість здійснювати торги.\n\n2. Економічна смерть\n7-денне розворотне відхилення CS2 (липень 2025 р.)\n\nValve запроваджено односторонні Зміни тренду для предметів у грі Counter-Strike. Будь-який обміняний скін отримує позначку «Захищений від обміну» на сім днів. Якщо жертва виявляє підміну, вона натискає «Скасувати обмін» у розділі «Підтримка» Steam, і скін миттєво повертається до її інвентарю, а одержувач блокується. Оскільки 7-денна блокада обміну не дозволяє шахраям перенести предмет на сайт для обміну на гроші, крадіжка стає невигідною.\n\n3. Смерть «Silent Key»\nОбов’язкове впровадження мобільних push-повідомлень для API (грудень 2023 р.)\n\nРаніше викрадений сесійний файл cookie дозволяв зловмисним скриптам виконувати фоновий POST-запит без інтерфейсу користувача до /dev/ajaxregisterkey без попередження жертви. 4 грудня 2023 року Valve запровадило обов’язкове явне підтвердження push-повідомлення в мобільному додатку Steam для генерації ключа Web API, що усунуло можливість прихованого фонового надання ключів.\n\n4. Мобільні сповіщення у додатку\nБанери з датою створення та назвою облікового запису (2022–2024)\n\nValve було оновлено модальне вікно підтвердження на мобільних пристроях, щоб відображати дані торгового партнера Steam термін існування рахунку (дата відкриття), рівень Steam та явне попередження жовтого кольору: «Цей користувач нещодавно змінив ім’я у своєму профілі», що розвіює візуальну ілюзію для уважних жертв.\n\nТри недоліки «клаптикової ковдри» Valve: чому шахраї просто змінили свої цілі\n1. Лазівка, пов’язана з виключенням ігор (Dota 2 та TF2)\n\nФункція «Trade Reversals» була впроваджена виключно для Counter-Strike 2. Предмети в іграх Dota 2 та Team Fortress 2 залишаються абсолютно незахищеними через складність процесу виготовлення та вставлення самоцвітів. Предмети високого рівня, вартість яких сягає тисяч доларів (гаки «Драконовий кіготь», «Золоті малі Рошани», «Незвичайні палаючі полум’я TF2»), не мають жодного періоду для скасування угоди. Шахраї просто перенаправили автоматичне перехоплення API на трейдерів Dota 2 та TF2, де служба підтримки Steam суворо дотримується своєї політики 2016 року щодо «відсутності відновлення предметів».\n\n2. Резервуар «Zombie Key» (без терміну дії)\n\nУ той час як Valve додало мобільну двофакторну аутентифікацію (2FA) у вигляді push-повідомлень для генерації новий ключі у грудні 2023 року, Valve існуючі старі ключі API ніколи не скасовувалися, не втрачали чинності та не видалялися. Мільйони активних облікових записів, які генерували ключі (або в яких ключі були створені непомітно за допомогою фішингу чи шкідливого програмного забезпечення до грудня 2023 року), досі містять активні облікові дані з нульовий термін дії (без TTL) та нульовий час очікування у разі бездіяльності. Зловмисники ведуть величезні бази даних, що містять ці постійні ключі, і продовжують здійснювати запити IEconService без перешкод.\n\n3. Штраф для потерпілого: 30-денна заборона на торгівлю\n\nНавіть у CS2, Valve накладає штраф на гравця, якого обдурили: натискання кнопки «Скасувати обмін» у Steam «Підтримка» автоматично накладає обов’язкова 30-денна заборона на торгівлю та доступ до «Community Market» на рахунку потерпілого. Valve карає користувача місячним відстороненням від платформи як засіб запобігання «безпідставним» скасуванням угод, що має на меті відрадити жертв від скасування угод щодо ліквідних товарів з низькою вартістю.\n\nГоловний скандал у сфері регулювання: сім років обхідних шляхів проти однієї сфери застосування API\n\nЧому Valve витратив сім років на розробку механізмів блокування торгів, періодів очікування для облікових записів та оборотних блокувань торгів — що призвело до порушення роботи всієї ігрової економіки та втрати $104 млн ринкової капіталізації — замість того, щоб застосувати стандартне для галузі рішення?\n\nПро що свідчить офіційний реліз гри Valve у Steamworks 16 січня 2026 року (Оголошення #493839547938902179 ↗), Valve вже побудовано Групи детальних прав доступу (Загальні, Мікротранзакції, Економіка, Дані про продажі) та Білий список IP-адрес для корпоративних ключів видавця. Valve вже роками мала готове технічне рішення. Один-єдиний прапорець для користувача —«Заборонити цьому ключу веб-API доступ до IEconService (Управління торгівлею)» або список дозволених домашніх IP-адрес — дозволив би повністю покінчити з шахрайством, пов’язаним із заміною товарів, у 2018 році без жодних побічних економічних наслідків. Valve відмовилася надати звичайним гравцям той захист, який вона розробила для корпоративних партнерів.\n\nЧастина Б — Правила та історія їх виконання · Розділ 9\nЇхні правила. Зареєстровані платформи.\nКонтекст та обмеження щодо джерел\n\nЦей реєстр зіставляє явні положення з Steam Угода з абонентом (SSA) та Steam Поведінка в Інтернеті (SOC) рекомендації, спрямовані безпосередньо проти активних, великих комерційних суб’єктів господарювання.\n\nПравило: жодного комерційного використання, жодних азартних ігор, жодних ботів — і служба підтримки Steam посилається на ці пункти, коли відмовляється повернути речі потерпілому. Запис: на перший погляд, ці самі положення поширюються на комерційні платформи, занесені до цього реєстру, які працюють на основі Steam облікових записів, Steam ботів та Steam переказів. Ця умова застосовується до особи, яка втратила шкури, а не — згідно з жодними опублікованими даними — до підприємств, які їх транспортують.\n\nУ заархівованих скаргах служба підтримки Steam посилається на «Заборонено використовувати в комерційних цілях» та «Без автоматизації та ботів» пункти, на які посилаються при відмові у відновленні активів жертвам шахрайства з використанням API-ключів. Ці самі пункти, судячи з їхнього тексту, застосовуються до комерційних платформ, зазначених у цьому досьє, які здійснюють аутентифікацію через Steam OpenID та переміщують активи через автоматизовані Steam облікові записи. У цьому документі не наводяться оціночні показники доходів у масштабах усього ринку (див. статистику щодо забезпечення дотримання вимог нижче). Дані показують застосування правил до окремих облікових записів у заархівованих справах, але не містять опублікованих даних щодо забезпечення дотримання вимог для платформ у розрізі окремих операторів. Саме цю асиметрію й документує цей розділ.\n\nГоловне питання / вибіркове застосування законодавстваПравила → Масштаб → Відповідальність\nОдин звід правил. Нерівне застосування.\n\nУ реєстрі зазначено, що комерційні сервіси використовують ідентифікатори Steam, інвентарі, боти та перекази як операційну інфраструктуру. Закон про безпеку даних (SSA) забороняє комерційне використання та автоматизацію без дозволу. Архівні скарги свідчать, що це правило застосовувалося до окремих облікових записів, тоді як у публічному реєстрі немає відповідних даних щодо кожного оператора окремо для платформ, про які йдеться в цьому документі. Опублікуйте правило, докази та рішення про застосування заходів щодо кожного з них.\n\n189веб-сайти, що підпадають під аудит\n44маршрути з окремими доменами в реєстрі Live — 27 із опублікованим файлом доказів, 17 зібраних вручну. Лише завдяки аудиту 189 веб-сайтів було виявлено 25 з них; до реєстру додано маршрути, зібрані вручну.\n12 років 6 місяцівcsgogem.com заблоковано у фільтрі посилань; api.csgem.com зареєстрована 2014-03-08 і ніколи не блокувалася — одна з 26 таких пар станом на 2026-09-22\nЗагальна сума не підтвердженаоцінка доходів у цілому по ринку не врахована\nSteam Поведінка в Інтернеті\n«…ви не повинні здійснювати або намагатися здійснювати будь-яку з наведених нижче дій на Steam: […] Займатися комерційною діяльністю. Приклади такої забороненої поведінки включають: розміщення реклами; проведення конкурсів; азартні ігри; купівля або продаж акаунтів Steam; продаж контенту, подарункових карток чи інших товарів; а також жебрацтво».\n\nstore.steampowered.com/online_conduct ↗ архів 2026-09-21 ↗\n\nSSA § 2.G — Комерційне використання\n«…[ви не маєте права] використовувати Контент та Послуги або будь-яку їх частину в комерційних цілях, за винятком випадків, прямо дозволених в інших положеннях цієї Угоди…»\n\nЯк повідомлялося, у повідомленнях Valve за 2016 рік посилалися на особисту некомерційну ліцензію. Жоден оператор офіційно не надав дозвіл Valve. store.steampowered.com/subscriber_agreement ↗ архівується 2026-09-18 ↗\n\nSteam Умови використання веб-API\n«Ви не маєте права використовувати Steam веб-API або Steam дані будь-яким чином, що порушує Steam Угоду з абонентом».\n\nСторонні маркетплейси скінів працюють за допомогою автоматизованих облікових записів, які використовують API Steam. У тексті правила не передбачено жодних винятків щодо комерційного масштабу. steamcommunity.com/dev/apiterms ↗ архівується 2026-09-21 ↗\n\nSSA § 4.C\nАвтоматизація\n\nСкрипти, боти та взаємодія, що не здійснюється людьми, обмежені. У реєстрі фіксуються операції з використанням ботів, мережі акаунтів та автоматизована маршрутизація в комерційних масштабах.\n\nПеревірити 153записи, позначені за цією категорією ↗\nЩо передбачено цим пунктом153 позначені платформи\nВідкриття справи15\nSkin Casino13\nРинок CS29\n«Шкірна рулетка»8\ncsgoempire.com→csgoempirelogin4.comКазино\nrollbit.com→rbsnin.comКриптоказино\n500.casino→fivezerozero.coКазино з ліцензією\n\nЗ них, 153 також позначені за статтею §2.G Закону про соціальне забезпечення (SSA) та 2 також позначені за статтею SSA § 1.C — одні й ті самі послуги підпадають під дію кількох пунктів, тому приклади повторюються.\n\n28 було виявлено, що сайт 153 проходить аутентифікацію через окремий домен, який підлягає реєстрації. Мітка фіксує датоване спостереження, яке, на перший погляд, підпадає під дію відповідного положення; це не є визнаним судом порушенням, і щодо жодного з них не було надано дозвіл від Valve.\n\nSSA § 2.G\nКомерційне використання\n\nДля комерційного використання необхідний прямий дозвіл. Порівняйте описані бізнес-моделі, їхній масштаб та будь-які оприлюднені відомості щодо дозволів або заходів з забезпечення дотримання вимог.\n\nПеревірити 175записи, позначені цим тегом ↗\nЩо передбачено цим пунктом175 позначені платформи\nВідкриття справи15\nSkin Casino13\nРинок CS29\n«Шкірна рулетка»8\ncsgoempire.com→csgoempirelogin4.comКазино\nrollbit.com→rbsnin.comКриптоказино\n500.casino→fivezerozero.coКазино з ліцензією\n\nЗ них, 153 також позначені за статтею §4.C Закону про соціальне забезпечення (SSA) та 24 також позначені за статтею SSA § 1.C — одні й ті самі послуги підпадають під дію кількох пунктів, тому приклади повторюються.\n\n28 було виявлено, що сайт 175 проходить аутентифікацію через окремий домен, який підлягає реєстрації. Мітка фіксує датоване спостереження, яке, на перший погляд, підпадає під дію відповідного положення; це не є визнаним судом порушенням, і щодо жодного з них не було надано дозволу від Valve.\n\nSSA § 3.A\nVPN та маскування місцезнаходження\n\nПриховування місця перебування за допомогою проксі-серверів IP може призвести до припинення доступу. Хости автентифікації з окремими доменами потребують окремого аналізу: необхідно встановити, що саме приховується та яке правило застосовується.\n\nПеревірити дані про хост автентифікації ↗\nSteam Довідка / Політика щодо URL-адрес\nЗашифрування посилань\n\nSteam забороняє використання сервісів для скорочення посилань та інструментів, що приховують кінцеві адреси посилань. Окремий домен авторизації — rbsnin.com у процесі входу в систему Rollbit, auth.dota.trade у CS.MONEY — виникає аналогічне питання: чи вказує адреса призначення, яка відображається верифікатору OpenID користувача Steam, на сайт, що працює.\n\nПолітика щодо URL-адрес Valve ↗\n\nПосилання на правила: Steam Угода з абонентом, редакція від 10 вересня 2026 року архів 2026-09-18 ↗ · Steam Умови використання веб-API архівується 2026-09-21 ↗ · Steam Політика щодо URL-адрес (зашифрування посилань). Ці цифри відображають кількість записів та тегів у цьому досьє; вони не є кількістю порушень, щодо яких було винесено рішення.\n\nДефіцит довіри\nХто переглядає рішення, коли служба підтримки закриває справу?\n\nУ збережених скаргах йдеться про постійні санкції, залишені без відповіді звернення та відмови у поверненні викрадених речей. Порівняйте ці відомості з фактичною історією квитків, доступними засобами правового захисту та журналами доступу до облікового запису. Загальне пояснення про фішинг не дозволяє встановити, хто ініціював скидання налаштувань або створив ключ API.\n\nОзнайомтеся зі зібраними скаргами ↗Запросити відповідні записи →Графік взаємозв’язків модераторів →\nЧастина Б — Правила та дані про їх виконання · Розділ 10\nAPI для автоматизації. Правило, що забороняє автоматизацію.\nКонтекст та обмеження джерел\n\nУ цьому розділі ставиться питання про те, як узгодити ці два аспекти: які види використання API є дозволеними, ким вони санкціоновані та за якими оприлюдненими критеріями. Тут не наводиться жодних оцінок щодо кількості дозволених комерційних користувачів API, і відсутність оприлюдненого списку не означає, що таких користувачів немає — саме ця відсутність є висновком, а не цифрою, що стоїть за нею. Наведені вище повідомлення служби підтримки Steam відтворені проектом ArchiSteamFarm у його власному розділі «Часті запитання» (перевірено дослівно 2026-09-22); вони не є Valve публікаціями, а облікові записи, на які їх було надіслано, не ідентифіковано.\n\nПоложення (SSA § 4.C): На Steam заборонено використовувати скрипти, боти та нелюдські системи. Запис: Valve надає безінтерфейсний REST API, єдиною метою якого є автоматизація взаємодії між серверами, і надає доступ до нього будь-якому обліковому запису. Користувачів блокують за використання засобів автоматизації; інтерфейс для автоматизації є власним продуктом Valve. Інформація про те, які види комерційного використання дозволені, ніколи не оприлюднювалася.\n\nХибне уявлення про «розробника ігор»\nSteamworks SDK (ліцензійна версія)\n\nВикористовується офіційними ігровими студіями для інтеграції досягнень, системи підбору гравців та таблиць лідерів у свої ігрові клієнти. Вимагає складної інтеграції на C++ та офіційного підключення партнера.\n\nSteam Веб-API (Лазівка)\n\nАрхітектура JSON/REST без «голови», призначена для зовнішніх веб-серверів. У описаному тут сценарії «викрадення» вона використовується для зчитування даних про запаси та управління одноранговими операціями з віддалених серверів; її законні сфери застосування не описані в цьому досьє.\n\nДля кого призначений цей ключЗвичайному користувачеві Steam не потрібен ключ Web API для роботи в клієнті; сторінка з ключами розміщена за URL-адресою для розробників, і, згідно з документацією, призначена для зовнішнього доступу на стороні сервера. В архіві скарг на викрадення облікових записів описані випадки, коли жертви не знали про існування цієї сторінки, доки на їхньому обліковому записі не було зареєстровано ключ.\nПротиріччя автоматизації\n\nУ § 4.C Закону про соціальне забезпечення (SSA) передбачено: «Забороняється будь-яким чином використовувати скрипти, боти, макроси чи інші системи, що не керуються людиною («Автоматизація»), для взаємодії з Контентом та Послугами на Steam». Проте кінцеві точки Web API (наприклад, CancelTradeOffer) не потребують інтерфейсу користувача та капчі й повністю обходять клієнт Steam. API призначений для автоматизації взаємодії між серверами; правило забороняє автоматизацію з боку користувачів; межа між цими двома випадками не оприлюднюється.\n\nПозиція на стороні сервера в торговому потоці\n\nКлюч веб-API дозволяє сторонньому серверу здійснювати операції з рахунком без участі клієнта Steam. У сценарії «викрадення» цей сервер розташовується між власником рахунку та сервером торгівлі.\n\n→Екран підтвердження операції не відображається при виконанні дій за допомогою клавіші.\n→Дозволяє виконувати фонове опитування (GetTradeOffers).\n→Скасовує та повторно формує пропозиції без участі користувача.\nValve створила інтерфейс, у своїх правилах заборонила використання автоматизованих засобів користувачами та не опублікувала критеріїв, за якими дозволяється комерційне використання.\nЧастина Б — Правила та історія їх виконання · Розділ 11\nПотрібно було десять днів. А відзвітувати — за десять років.\nКонтекст та обмеження щодо джерел\n\n20 липня 2016 року головний юрисконсульт компанії Valve поставив операторам азартних ігор 10-денний термін. Через десять років (станом на момент створення знімка досьє, 2026-09-21) принаймні одна платформа, згадана в пресових повідомленнях про це повідомлення, — CSGOFast — досі функціонує з авторизаційним хостом на окремому домені. Текст повідомлення відтворено нижче на основі пресових повідомлень від 21 липня 2016 року; це відтворення не є сканованою копією. Протокол про примусове виконання, на який натякало це повідомлення, не було опубліковано. Відкритий лист до Комісії є Розділ 2.\n\nОзнайомтеся з повідомленням від липня 2016 року, розміщеним поруч із пізнішими зауваженнями. Наразі залишається невирішеним питання щодо звіту про виконання вимог кожним оператором окремо.\n\nЗа тиждень до того — 13 липня 2016 року, на публіці\n\nПро 13 липня 2016 року архів 2026-09-21 ↗, Valve описав, як сайти азартних ігор використовували Steam: OpenID для ідентифікації облікових записів та автоматизовані облікові записи для торгівлі. Valve зазначив, що використання цих механізмів для ведення бізнесу в сфері азартних ігор порушувало умови використання API та угоди з користувачами. Як опис механізму, так і заборона містяться у власній датованій заяві Valve. На 2026-09-21 тестовані хости авторизації з окремими доменами не повернули жодного блокування за фільтром посилань, а Valve не опублікував жодного запису про застосування обмежень для окремих операторів.\n\nДОДАТОК А / ЛИПЕНЬ 2016ВІДТВОРЕННЯ НАБОРУ ТЕКСТУ\nКОРПОРАЦІЯ «VALVE»\n\nБелв'ю, штат Вашингтон\n\nДАТА:Липень 2016 року (повідомлення в пресі від 21 липня 2016 року)\nВІД:Карл Квакенбуш, головний юрисконсульт\nRE:Вимога про припинення — комерційне використання облікових записів Steam\nПРИМІТКА:Відтворення тексту з джерела; це не сканована копія\n\n«Нам відомо, що ви керуєте одним із перелічених нижче сайтів, пов’язаних з азартними іграми. Ви використовуєте Steam облікових записів для ведення цієї діяльності. Згідно з Угодою про надання послуг Steam, послуги Steam та Steam ліцензовані виключно для особистого, некомерційного використання».\n\n«Ви повинні негайно припинити подальше використання своїх облікових записів Steam у будь-яких комерційних цілях. Якщо ви цього не зробите, протягом десяти (10) днів, Valve вживатиме всіх доступних заходів, включаючи, серед іншого, закриття ваших облікових записів».\n\nВідновлення досьє · ознайомитися з первинним записом\nКарл Квакенбуш\nГоловний юрисконсульт, Valve Corp.\nНА ПОЛЯХ / РЕДАКЦІЙНА СТАТТЯ\nДесять днів.То що ж тоді?\n\nТермін був чітко визначений. Так само має бути і з подальшими діями з боку громадськості.\n\nОпублікована позиція компанії «Valve» щодо «2016» ↗\nПримітка щодо кінцевого терміну +\nСАТИРА / НЕ ЛИСТОВА КОРЕСПОНДЕНЦІЯ\n\nШановний дедлайн,\n\nТобі дали десять днів. Якимось чином календар був єдиною річчю, що продовжувала працювати.\n\nБудь ласка, надішліть будь-яку відповідь до публічного реєстру.\n\nХронологія подійЛипень 2016 р. – вересень 2026 р.\nТермін, зазначений у повідомленні:\n10 днів\nЛипень 2016 року\nЧас, що минув з моменту повідомлення:\n3,715 днів\nДані зафіксовано за період з 20 липня 2016 року до моменту створення знімка досьє 21 вересня 2026 року; це не актуальні дані\nОпубліковані дані про виконання:\nНемає\nНе знайдено даних про завершення дзвінків або блокування для кожного оператора\n\n◀ Дні 0–10 — кінцевий термін, у масштабі3715-й день — знімок ▶\n\n20 липня 2016 рокуОпубліковано десятиденне оголошення про запитДень 0\n17 лютого 2024 рокуДіють зобов’язання DSAДень 2,768\n25 лютого 2026 рокуОголошено про подання скарги Генеральним прокурором штату Нью-ЙоркДень 3,507\n21 вересня 2026 рокуКороткий огляд досьє3715-й день\n\nЧерез десять років, CSGOFast — згаданий у ЗМІ у повідомленнях 2016 року — працює: сайт csgofast.com повернув повідомлення про блокування фільтром посилань для 2026-09-19 та 2026-09-21, тоді як його хост автентифікації steam-login.authtofast.com (зареєстрований 2026-06-30) цього не зробив.\n\nПовний хронологічний звіт про зміни в налаштуваннях безпеки Valve: Хронологія подій у сфері безпеки → · Судова практика Вашингтона та критерії застосування: нижче\n\nЩо свідчать матеріали справи: У повідомленні 2016 року було встановлено 10-денний термін; Valve вже використовував список доменів («Link Filter») та отримував імена авторизованих хостів у своїх запитах OpenID; жодних даних щодо заходів щодо виконання вимог окремими операторами опубліковано не було. У звітах спільноти згадується захід 2018 року проти торговельного майданчика (SkinJar), але ці звіти не перевірені і в даному документі на них не посилаються.\nCSGOFAST / ШЛЯХ ЗБЕРЕЖЕНОЇ АВТЕНТИФІКАЦІЇ\nПерейдіть на вказаний хост для повернення.\n\nПосилання на збережені записи маршрутів csgofast.com до steam-login.authtofast.com. Окреме ім'я хоста передається у запиті OpenID Steam. Це дає слідчим конкретну адресу для порівняння із записами про фільтрування та застосування заходів, що містяться в запиті Valve.\n\nОзнайомтеся з маршрутом CSGOFast та його джерелом ↗ · Порівняти збережені Steam Результати фільтрації посилань ↗\n\nПУБЛІЧНИЙ РЕЄСТР / ВАШИНГТОН · 2016 → 2026\nДва терміни. Один невизначений стандарт виконання.\n20 липня\nValve надає сайтам, що пропонують азартні ігри, 10 днів\n\nУ вимозі її юридичного представника містилося попередження, що подальше комерційне використання облікових записів Steam може призвести до припинення дії облікового запису.\n\n27 вересня\nВашингтон тисне Valve\n\nДержавна комісія з азартних ігор вимагає надати докази вжиття заходів щодо припинення використання «скін-переказів» для азартних ігор та встановила термін для надання відповіді до 14 жовтня.\n\n17 жовтня\nValve відхиляє звинувачення\n\nValve відповіла після закінчення встановленого терміну, заперечила, що сприяла азартним іграм, заявила, що заблокувала пов’язані акаунти, та зазначила, що не хоче вимикати торгівлю та OpenID для всіх користувачів. Принаймні одна платформа, згадана в пресі у зв’язку з липневими повідомленнями (CSGOFast), продовжувала працювати через десять років. Обидва факти можуть бути правдивими лише в тому випадку, якщо оператор замінив заблоковані облікові записи; даних, які б це підтверджували, опубліковано не було. WSGC має звернутися до Valve із проханням узгодити ці дві інформації.\n\n2026\nМаршрути, зафіксовані у вересні 2026 року\n\nУ реєстрі маршрутів зафіксовано 44 платформи, що проходять аутентифікацію через хости аутентифікації в окремих доменах, зокрема CSGOFast, з використанням механізмів OpenID та торгівлі Valve, описаних у 2016 році. Запис про заходи, який би показав, яким операторам було відключено доступ, не було оприлюднено.\n\nВЛАСНИЙ БРИФІНГ КОМІСІЇ · 30 СІЧНЯ 2018 РОКУ\nЧерез вісімнадцять місяців після відповіді Valve регуляторний орган все ще називав це «наміром».\n\nПід час брифінгу для членів власного законодавчого органу на публічних слуханнях щодо законопроекту HB 2881 Комісія описала заяву від липня 2016 року своїми словами: Valve \"оголосила про намір вжити жорстких заходів проти використання своєї платформи для організації азартних ігор зі скінами\". На цій же сторінці наведено інформацію про те, як це оголошення вплинуло на прогнози щодо розвитку галузі — «як наслідок», прогноз щодо ринку азартних ігор у 2020 році було переглянуто з $19.7 мільярд до $670 мільйон, що становить зниження приблизно на 97 відсотків, лише на тлі самого оголошення. Прогноз змінився. Дані щодо кількості випадків порушення на одного оператора, які б це обґрунтували, досі не опубліковано.\n\nРинкові показники — це оцінки компаній Narus Advisors та Eilers & Krejcik Gaming, наведені в брифінгу Комісії, а не висновки самої Комісії; у тому ж документі обсяг ставок на скіни у 2016 році оцінюється приблизно в $5 мільярда, з яких близько $3 мільярдів припадає на сайти, що працюють за принципом казино. Отримано 2026-09-22, SHA-256 c507c9025f93da0aadaf395c4d8882f25973211c318ee8e9b6f18a5b3755e050.\n\nПублічну позицію Valve від 2016 року та сучасну інфраструктуру, яку можна спостерігати, можна порівняти між собою. Питання полягає в тому, чи поширилися заходи щодо забезпечення дотримання вимог на рахунки та маршрути, якими користуються заборонені оператори. Десятиденний термін попередження не є доказом того, що попередження було доведено до відома всіх операторів, зазначених у ньому. Захід щодо OPSkins у 2018 році є єдиним задокументованим випадком втручання проти конкретного оператора; з огляду на те, що було перевірено 189 платформ і не опубліковано жодних даних щодо окремих операторів, один задокументований випадок не свідчить про наявність певної тенденції у застосуванні заходів.\n\nПовідомлення Комісії з питань азартних ігор штату Вашингтон за 2016 рік ↗ архів 2026-05-20 ↗ · Відповідь Valve від 17 жовтня 2016 року (копія документа) ↗ · Інформаційна доповідь WSGC для законодавчого органу, 30 січня 2018 року (місцева копія, 4 стор.) ↗ · той самий файл на сайті wsgc.wa.gov ↗ · запис пошуку та хеш ↗ · Події Valve на OPSkins у 2018 році ↗ архів 2026-03-07 ↗ · Перевірка поточного маршруту ↗\n\nСудово-експертний довгостроковий аудит · Об’єкти, щодо яких у 2016 році було винесено вимоги про припинення діяльності\n«Десятиліття 10-денного попередження»: криміналістичний аудит стану збереженості 23 зазначених об’єктів\n\n19–20 липня 2016 року Valve головний юрисконсульт Карл Квакенбуш надіслав офіційні повідомлення про припинення діяльності 23 платформам азартних ігор зі «шкірами», наказавши їм припинити комерційне використання Steam облікових записів у межах 10 днів під загрозою закриття облікового запису та судових позовів. Через 3,700 днів емпіричний аудит виявив справжню картину дотримання вимог: численні оператори так і не припинили свою діяльність, інші продовжували працювати ще до шести років після закінчення терміну, а багатомільярдна екосистема й надалі використовувала архітектуру OpenID від Valve.\n\n5+ НАЖИВО\nБезумовно працюватимуть у 2026 році (CSGOBig, CSGO500, CSGOFast тощо)\n6 РОКІВ\nНайдовший період роботи після оприлюднення повідомлення до закриття (CSGOatse працював до 2022 року)\n$5.01B\nОбсяг ставок на шкіру у 2016 році (Narus / Eilers & Krejcik)\n200+\nАктивні сайти азартних ігор, що працюють у період піку ринку\n«Титани, що вижили» · План розвитку фінансів та відвідуваності на 2024–2026 роки\nВід 10-денних попереджень до офшорних конгломератів: оборот у кілька мільярдів доларів\n\nЗамість того, щоб покласти край азартним іграм зі шкірою, повідомлення Valve від 2016 року стали каталізатором еволюції галузі. Оператори, що вижили, реорганізувалися в офшорні юридичні особи (Кюрасао, Беліз, Кіпр), стали піонерами торгівлі за принципом «рівний-рівному» (P2P) для обходу заборон на використання ботів і зараз обробляють понад 10 мільйонів відвідувань веб-сайту щомісяця та мільярди доларів щорічного обсягу ставок продовжуючи при цьому аутентифікацію через Steam:\n\nПлатформа / Домен\tПовідомлення за липень 2016 року\tРезультати виконання рішення та статус виживання\tЗареєстрована перевірка / Основні посилання\nCSGOBig\ncsgobig.com\tПовідомлення за 10 днів (липень 2016 р.)\tУ 2026 РОЦІ ВСЕ ЩЕ ЖИВУТЬ\nТимчасово призупинено, відновлено; авторизація здійснюється через letmeinbig.com та csgobiglogin.com\tX: @csgobig ↗ · FB: csgobigofficial ↗\nCSGO500\ncsgo500.com / 500.casino\tПовідомлення за 10 днів (липень 2016 р.)\tУ 2026 РОЦІ ВСЕ ЩЕ ЖИВУТЬ\nПерейменовано на 500 Casino (ліцензія Кюрасао № 8048/JAZ2014-037), щомісячний оборот у кілька мільйонів\tПлатформа Live (500.casino) ↗\nCSGOFast\ncsgofast.com\tПовідомлення за 10 днів (липень 2016 р.)\tУ 2026 році все ще живий\nАктивно працюють рулетка, «краш» та джекпот через steam-login.authtofast.com\tАудит автентичності досьє ↗\nCSGOLounge / Dota2Lounge\ncsgolounge.com / dota2lounge.com\tПовідомлення за 10 днів (липень 2016 р.)\tУ 2026 році все ще живі\nОрієнтована на ставки на кіберспортивні монети та криптовалютні ставки; забезпечує безперебійну роботу\tПлатформа в режимі реального часу ↗\nCSGOCasino\ncsgocasino.net / csgocasino.gg\tПовідомлення за 10 днів (липень 2016 р.)\tПРЯМА ТРАНСЛЯЦІЯ ЧЕРЕЗ SUCCESSOR (2026)\nДомен перенаправлено; активний портал-наступник працює за адресою csgocasino.gg\tДомен-наступник ↗\nCSGOatse\ncsgoatse.com\tПовідомлення за 10 днів (липень 2016 р.)\tПРОІСНУВАВ 6 РОКІВ (ДІЯВ ДО 2022 РОКУ)\nПродовження повномасштабної діяльності у сфері азартних ігор протягом шести років після 10-денного ультиматуму від Valve\tX: @CSGOatsecom (активний до 2022 року) ↗\nCSGOSweep\ncsgosweep.com\tПовідомлення за 10 днів (липень 2016 р.)\tПРОІСНУВАВ ДО ГРУДНЯ 2017 РОКУ\nПродовжувала працювати у відкритому режимі протягом 17 місяців після закінчення терміну\tX: Статус CSGOSweep, грудень 2017 р. ↗\nCSGOWild\ncsgowild.com\tПовідомлення за 10 днів (липень 2016 р.)\tПРОІСНУВАВ ДО ГРУДНЯ 2017 РОКУ\nПросувався провідними інфлюенсерами; працював протягом 1,5 року після отримання попередження про припинення діяльності (C&D) до переходу на криптовалюту\tX: @Wild (Активний з грудня 2017 р.) ↗\nCSGOPot\ncsgopot.com\tПовідомлення за 10 днів (липень 2016 р.)\tПРОЖИВ ДО ВЕРЕСНЯ 2017 РОКУ\nПродовжував приймати ставки на джекпот із високими ставками протягом 14 місяців після отримання попередження\tX: @csgopot (Активний з вересня 2017 р.) ↗\nCSGODiamonds\ncsgodiamonds.com\tПовідомлення за 10 днів (липень 2016 р.)\tПРОІСНУВАВ ДО СЕРЕДИНИ 2017 РОКУ\nПройшов у 2017 році, незважаючи на визнані факти фальсифікації результатів для стримерів, що отримували спонсорську підтримку\tX: @csgodiamondscom (2017) ↗\nCSGOLotto\ncsgolotto.com\tПовідомлення за 10 днів (липень 2016 р.)\tЗАКРИТО У ЛИПНІ 2016 РОКУ\nЗакрито через громадський скандал; стало об’єктом угоди про дотримання вимог, укладеної з Федеральною торговою комісією (FTC)\tПостанова Федеральної торгової комісії (справа № C-4632) ↗\nCSGODouble\ncsgodouble.com\tПовідомлення за 10 днів (липень 2016 р.)\tЗАКРИТО У ЛИПНІ 2016 РОКУ\nДобровільно припиніть діяльність одразу після опублікування вимоги про припинення діяльності\tX: @CSGODouble (закрито в липні 2016 р.) ↗\nCSGOMassive\ncsgomassive.com\tПовідомлення за 10 днів (липень 2016 р.)\tЗАКРИТО 2016\nПрипинила свою діяльність наприкінці 2016 року\tX: @csgo_massive ↗\nCSGOStrong\ncsgostrong.com\tПовідомлення за 10 днів (липень 2016 р.)\tЗАКРИТО 2016\nПрипинила свою діяльність у 2016 році\tFB: csgostrongfree ↗\nSkins2\nskins2.com\tПовідомлення за 10 днів (липень 2016 р.)\tЗАКРИТО 2016\nПрипинила свою діяльність у 2016 році\tFB: CSNCOM ↗\n\nПлатформа\tЩомісячний трафік (відвідування)\tОрієнтовний оборот / обсяг\tЮридична особа та юрисдикція\tОсновні регуляторні заходи та модель\nCSGOEmpire\ncsgoempire.com\t2,3 млн — 9,0 млн на місяць\nСередня тривалість — 6+ хвилин; 80% прямий\t$1.5B — $2.5B Річний обсяг продажів\n>1,000,000 операції з обміну скінами P2P на місяць; $6.4 млн активних ліквідних ордерів\tMoonrail Limited B.V. (Кюрасао № 148182)\nПлатежі: JHOLT LTD (Кіпр); Засновник: «Monarch» (Оссі Кетола)\tПерша компанія, що запровадила безкоштовну P2P-торгівлю товарами; ліцензія Кюрасао OGL/2024/1183/0869\nCSGORoll\ncsgoroll.com\t2,74 млн — 3,5 млн на місяць\nСередня тривалість — 9 хв 23 с; 16% коефіцієнт відмов\t$1.0B — $2.0B Річний обсяг операцій\nОрієнтовний річний дохід компанії від переваги казино: $100M–$200M\tFeral Holdings Limited\nШтаб-квартира розташована в місті Беліз, Беліз (реєстраційний номер № 171519)\tЗаборонена австралійською комісією ACMA (травень 2023 року); спонсорувала команду першого рівня G2 Esports, у складі якої були неповнолітні гравці\n500 Casino (CSGO500)\n500.casino / csgo500.com\t220 тис. — 425 тис. на місяць\n~105 тис. унікальних відвідувачів щомісяця\t$100к / тиждень ($5.2М/рік) у Роялесі\nВимоги щодо ставок для гравців з високими ставками: $400 ставка на кожні $1 рейкбеку\tPerfect Storm B.V. (Кюрасао № 150536)\nЛіцензія Комісії з контролю за азартними іграми Кюрасао № OGL/2024/1354/0882\tЗаборонено шведським органом Spelinspektionen (листопад 2023 р.) за неліцензовану орієнтацію на шведських гравців\nCSGOBig\ncsgobig.com\t~169,600 / місяць\nСередня тривалість — 19 хв 12 с; первинні вибори у США\tЩорічний обсяг у кілька мільйонів\nТаємничі скриньки, рулетка та битви за скриньки\tПрацює за допомогою допоміжної проксі-маршрутизації\nletmeinbig.com (зареєстровано у 2023 році) та csgobiglogin.com\tTarget версії C&D за липень 2016 року; перезапущено з архітектурою проксі-аутентифікації\nCSGOFast\ncsgofast.com\t~150 тис. — 250 тис. на місяць\nГлобальна багатомовна аудиторія\tЩорічний обсяг у кілька мільйонів\nШвидкісні ігри в рулетку та «краш»\tОфшорні операційні структури\nМаршрути Steam автентифікація через steam-login.authtofast.com\tОб’єкт, щодо якого у липні 2016 року було винесено попередження про припинення діяльності (C&D); діяльність ніколи не припинялася; працює у 2026 році\nCSGO Polygon\ncsgopolygon.com / plg.bet\t~300 тис. — 500 тис. на місяць\nДомінування країн СНГ та Східної Європи\tЩорічний обсяг у кілька мільйонів\nКриптовалюта та «рулетка зі скінами», ставки на матчі\tЦіль другої хвилі (жовтень 2016 р.)\nПереорієнтувався на криптовалюту з дзеркальним доменом plg.bet\tПроіснував ціле десятиліття; продовжує ліквідацію інтерфейсів через сторонні API\n«Друга хвиля»: чому у вимозі про припинення порушень від Valve загалом було зазначено понад 43 сайти\n\n17 жовтня 2016 року юридичний радник компанії Valve офіційно повідомив Комісії з питань азартних ігор штату Вашингтон, що після перших 23 повідомлень, надісланих 19 липня, компанія Valve надіслала листи з вимогою припинити діяльність до понад 20 додаткових сайтів, де можна грати на скіни (в результаті чого офіційна загальна кількість перевищила 43). Ця друга хвиля стала необхідною через те, що в первинному списку з незрозумілих причин були пропущені найбільші та найвідоміші ігрові центри світу:\n\nCSGOJackpot.com: Історичний засновник «шкірних джекпотів», який обробляв сотні мільйонів, перш ніж згорнути діяльність під загрозою федерального звинувачення.\nCSGOShuffle.com: Сайт, який опинився в центрі скандалу з стримінгом у липні 2016 року, коли виявилося, що стрімер Twitch PhantomL0rd таємно володів 33% акцій компанії та фальсифікував результати ставок за рахунок коштів компанії.\nМакроекосистема (понад 200 операторів): Згідно з галузевим дослідженням, проведеним компаніями Narus Advisors та Eilers & Krejcik Gaming, у 2016 році діяло понад 200 окремих сайтів азартних ігор зі «скінами», які забезпечили обсяг ставок у розмірі $5.01 мільярда від 3,03 мільйона активних гравців. 43 листи компанії Valve охопили менше ніж 20% активного ринку.\nОфіційні урядові та регуляторні розслідування щодо азартних ігор «Steam Skin Gambling»\n\nФеномен азартних ігор під прикриттям задокументований у численних офіційних законодавчих розслідуваннях, заходах щодо забезпечення дотримання законодавства та офіційних документах уряду:\n\n1. Комісія з питань азартних ігор штату Вашингтон (WSGC) (2016–2018)\n\n5 жовтня 2016 року було надіслано офіційну вимогу про припинення діяльності; 30 січня 2018 року опубліковано законодавчий огляд, у якому зазначається, що скіни є еквівалентами готівки, та наводиться інформація про обсяг ставок у скінах у розмірі $5.0B.\n\nЗвіт WSGC про законодавчу діяльність у форматі PDF (локальна копія) ↗\n2. Федеральна торгова комісія США (FTC) (вересень 2017 р., справа № C-4632)\n\nПерший випадок застосування федеральних регуляторних заходів щодо азартних ігор, пов’язаних зі «шкірами», проти власників CSGOLotto Тревора Мартіна та Томаса Касселла за оманливі практики та приховування інформації про контроль над платформою.\n\nРішення та угода про врегулювання справи Федеральної торгової комісії (FTC) ↗\n3. Документ із викладенням позиції Британської комісії з азартних ігор (UKGC) та перевірки щодо молоді\n\nВідповідно до Закону про азартні ігри 2005 року ігрові скіни офіційно класифікувалися як «гроші або те, що має грошову цінність». Наступні опитування показали, що понад 11% дітей віком 11–16 років робили ставки скінами у відеоіграх.\n\nРепозитарій досліджень UKGC ↗\n4. Розслідування Сенату Австралії з питань навколишнього середовища та комунікацій (2018)\n\nЗвіт Федерального парламенту щодо «Ігрові мікротранзакції за предмети, що отримуються за принципом випадковості», аналізуючи механіку «лут-боксів» у грі Valve, виведення коштів на вторинному ринку та обхід нормативних вимог.\n\nРозслідування парламенту Австралії ↗\nНепогашений попит\n\nОпублікуйте звіт про заходи щодо забезпечення дотримання вимог: які ігрові акаунти та боти було заблоковано, яким хостам-резервам було накладено обмеження, а яким комерційним сервісам було надано дозвіл. Публічне оголошення про заборону та попередження на головній сторінці не свідчать про те, що відповідна діяльність була припинена.\n\nЧастина Б — Правила та історія їх виконання · Розділ 12\nІм'я хоста вже вказано у запиті.\nКонтекст та обмеження джерел\n\nValve вже веде список доменів (фільтр посилань) і отримує ім’я хоста автентифікації в кожному запиті OpenID. Наведений нижче псевдокод ілюструє логічну схему зв’язку між цими двома елементами. Немає жодних публічних доказів того, що Valve робить це.\n\nValve вже використовує чорний список доменів. Valve вже отримує хост, з якого здійснюється вхід, у кожному запиті OpenID. Нічого будувати не треба — їх просто треба з’єднати. Це пошук імені хоста за списком, який Valve веде самостійно. Наведений нижче псевдокод є ілюстрацією, а не реалізацією Valve.\n\nforensic_autoban.py\n# ІЛЮСТРАТИВНИЙ ПСЕВДОКОД — Valve.block_domain() та flag_session_as_mitm() не є реальними викликами API. Це демонструє логічну структуру заходів захисту, які Valve може реалізувати проти доменів проксі-аутентифікації, а не фактичну внутрішню структуру Valve.\n# Ілюстрація: логічна структура перевірки вхідного запиту OpenID\ndef audit_openid_request(запит):\nblocked_origins = database.отримати_платформи_у_чорному_списку()\nproxy_domain = request.params.отримати(«openid.realm»)\ntarget_redirect = request.params.отримати(«openid.return_to»)\n\n# Логіка: Якщо проксі-сервер перенаправляє на заблокований сайт, заблокуйте цей проксі-сервер.\nдля сайт в blocked_origins:\nякщо сайт в target_redirect:\nValve.block_domain(proxy_domain)\nValve.позначити_сесію_як_MITM(request.session)\n# Результат: запит на вхід для цього хосту відхилено\n\nСпостереження:\nЯкщо основний домен уже внесено до фільтра посилань (наприклад, howl.gg, заблоковано 2026-09-18/19/21), а його хост автентифікації (howl.uno) з’являється у запиті OpenID, що надсилається з кнопки входу на цьому сайті, то Valve може виявити цю асоціацію на основі даних власного запиту. Перевірку можна автоматизувати, але її виконання — ні.\nЗадокументовані та оприлюднені прецеденти\n\nValve, як свідчать офіційні дані, принаймні один раз вживав заходів щодо стороннього оператора: у 2018 році він позбавив компанію OPSkins доступу до системи ExpressTrade (Оголошення Valve ↗ архів 2026-03-07 ↗). У повідомленнях спільноти за 2018 рік також йдеться про те, що один із маркетплейсів (SkinJar) втратив доступ; ці повідомлення не підтверджені, а механізм випливає з результату, а не з оприлюдненого процесу.\n\nЩо встановлює цей прецедент:\n\nValve може заблокувати доступ стороннього оператора, коли вважатиме за потрібне. CSGOFast, згаданий у пресових повідомленнях про попередження від липня 2016 року, працював на 2026-09-21 із зареєстрованим хостом авторизації 2026-06-30, який не повертав блокування за фільтром посилань. Чому одного оператора було відключено, а інших — ні, не пояснюється жодними опублікованими критеріями.\n\nЩо відображає дата реєстрації, а що — ні\n\nДата реєстрації авторизаційного хосту є нижньою межею часу, коли цей хост міг вперше з’явитися у запиті OpenID; вона не свідчить про безперервне використання. sc-auth.net, наприклад, було зареєстровано як 2019-04-02 (RDAP) і було виявлено в процесі входу на сайт Skin.Club під номером Steam у вересні 2026 року; про те, що відбувалося між цими двома датами, у відкритих джерелах інформації немає даних.\n\nПорівняльний аудит: стандарти відповідності API\nАспект правозастосування\tПравила використання API GitHub\tSteam Веб-API (Valve)\n1. Нейтральність щодо дотримання вимог\tОпубліковані, уніфіковані правила. До кожного облікового запису застосовуються задокументовані обмеження частоти звернень (наприклад, 5,000 запитів на годину для авторизованих користувачів, 15,000 на годину для організацій GitHub Enterprise Cloud) та опубліковані правила допустимого використання.\tОпублікованих критеріїв немає. Окремі акаунти блокуються на підставі положень про автоматизацію та комерційне використання (архівні скарги), при цьому дані щодо заходів, вжитих щодо окремих операторів комерційних платформ, не оприлюднюються.\n2. Зловживання OpenID / проксі-сервером автентифікації\tЗгідно з опублікованими правилами GitHub, додатки та токени OAuth можуть бути призупинені або анульовані у разі зловживання, а в документації описано процедуру автоматичного анулювання токенів, що потрапили у відкритий доступ (підсумок авторів на основі документації GitHub).\tХости автентифікації з окремими доменами, виявлені в потоках OpenID Steam (наприклад, rbsnin.com, howl.uno, sc-auth.net), не викликали блокування фільтром посилань у 2026-09-21, на відміну від їхніх основних доменів.\n3. Отримання прибутку від зловживань\tGitHub не стягує комісію за транзакції щодо товарів, переміщених за допомогою сторонніх засобів автоматизації; його модель отримання доходу базується на передплатах та розміщенні оголошень на торговельному майданчику.\tValve продає ключі від скриньок, за допомогою яких можна отримати ці предмети, а «Community Market» стягує сукупну комісію в розмірі приблизно 15% з продажів, здійснених на цій платформі. У цьому звіті не наводяться оціночні дані щодо доходів, отриманих за рахунок сторонніх платформ.\n4. Термін служби циклів ухилення\tПри блокуванні ідентифікатори клієнтів OAuth перестають працювати на всій платформі; у документації не вказано термін, протягом якого відбуваються такі дії, і в даному випадку він не враховується.\tХости автентифікації з окремими доменами, дата реєстрації яких припадає на період з 2011 року по вересень 2026 року, не виявили жодних блокувань за фільтром посилань під час перевірок 2026-09-19 та 2026-09-21. Дата реєстрації є нижньою межею можливого використання, а не доказом безперервного використання.\nДжерела: стаття на GitHub — опублікована GitHub документація щодо обмежень швидкості використання API та політики платформи (підсумок авторів, цитати відсутні) · стаття Steam — перевірки фільтра посилань у 2026-09-19 та 2026-09-21 (linkfilter-recheck-2026-09-21.json), реєстр RDAP (domain-registration.json) та архівні звернення до служби підтримки (архів доказів).\nЧастина Б — Правила та інформація про їх виконання · Розділ 13\nЦінова різниця «off-Steam»\n\nЦей товар знаходиться в запасі Steam; продаж відбувається в іншому місці. Новий, прямо з заводу, AWP Dragon Lore мав 62 актуальні пропозиції на CSFloat; найнижча запропонована ціна $10,623.95. На власному ринку Steam неможливо встановити ціну продажу, вищу за приблизно $1,800. Щоб продати товар за вищу спостережувану ціну, власнику потрібен покупець або торговельна платформа поза межами Steam. Товар та його передача все ще залежать від Steam.\n\nWhat this means — the Community Market listing ceiling\n\nSteam’s own market refuses a listing above roughly $1,800. A seller may ask less, never more. Items whose market price sits above that line therefore cannot be sold at that price on Steam at all — which is the mechanism that moves those sales to third-party venues while the item itself never leaves Valve’s inventory system.\n\nSection 13 — the off-Steam price gap →\n\nКонтекст та обмеження джерел\n\nУ цьому розділі наведено три різні види підрахунку, і вони не є взаємозамінними. 245 — це кількість категорій товарів CS2, найдешевша діюча пропозиція в яких перевищувала $1,800 виключно на CSFloat, 20 вересня 2026 року. 241 це той самий набір за вирахуванням чотирьох категорій, закріплених на верхній межі CSFloat $100,000, яка є панеллю, на основі якої обчислюється нижня межа $13.63M. 248 Це інший зріз ситуації: категорії, ціна на які 23 вересня 2026 року перевищувала верхню межу на двох або більше з п’яти торгових майданчиків. Торгові майданчики перетинаються, тому показники з різних майданчиків ні в якому разі не можна додавати. Кожна цифра тут є ціною, за яку пропонується товар, а не ціною укладеної угоди, і жодна з них не є доходом, оборотом чи прибутком — ні для Valve, ні для будь-кого іншого. Значення, наведені на сайті PriceEmpire, є округленими оцінками, опублікованими цим сайтом, а його картка Steam охоплює предмети з інших Steam ігор, тому обсяги порівняння не є ідентичними.\n\nОдин товар. Дві системи ціноутворення.СЛІДКУЙТЕ ЗА РЕЗУЛЬТАТАМИ\nКрок 3 / 3\n\nЗа таких умов продавцю потрібна альтернативна Steam платформа або покупець. Товар, як і раніше, залежить від запасів та системи передачі Steam.\n\nSTEAMПро $1,800Опублікований ліміт розміщення на ринку спільноти\nЗБЕРЕЖЕНИЙ КАТАЛОГ$10,623.95Новий, прямо з заводу, AWP Dragon Lore — запитуйте ціну\nЗАЛЕЖНІСТЬЦе все ще товар із позначкою SteamЗалишок та переміщення залишаються на рівні Steam\n01 / ТОВАРValve інвентар гриПредмет із CS2 або Dota 2, що знаходиться в Steam\n02 / СТЕЛЯПро $1,800 на SteamМаксимальна ціна за одне оголошення на ринку\n03 / ЗАПИТ ЗЗОВНІ$10,623.95 для «Dragon Lore»Найнижча пропозиція CSFloat у знімку на зазначену дату\n04 / ДОСТАВКАSteam залишається в ланцюжкуПраво власності та передача предметів залежать від цієї системи\nАРХІТЕКТУРА РИНКУ · МОМЕНТНИЙ ЗНІМОК, 20 ВЕРЕСЕНЬ 2026\nРізниця в ціні є відчутною.\n\nМи підрахували категорії товарів, найдешевша діюча пропозиція в яких була трохи вище $1,800.. Сайти CSFloat та Skinport — це окремі платформи з частково збіжними асортиментами CS2; їхні показники не можна підсумовувати. Зовнішні пропозиції показують, де виставлені вищі ціни, тоді як Steam як і раніше контролює право власності на товари та їх передачу.\n\n245КАТЕГОРІЇ CS2 · CSFLOAT\n166КАТЕГОРІЇ CS2 · SKINPORT\n3DOTA2: КАТЕГОРІЇ · SKINPORT\n$10,623.95ПИТАННЯ ЩОДО ПОВЕРХУ «ДРАКОНСЬКА МІФОЛОГІЯ»\n\nDragon Lore: 62 — активна пропозиція CSFloat у категорії «Factory New»; вказана мінімальна ціна є запитуваною ціною, а не підтвердженою ціною продажу. Steam дозволяє виставляти товар за нижчою ціною, але не дозволяє публікувати вищу ціну, яку було зафіксовано. У заяві Valve на сторінці 2016 підтверджується, що компанія знає про використання операторами азартних ігор OpenID та торговельної інфраструктури Steam. Питання про те, чи порушує конкретний сторонній торговий майданчик правила Valve, має вирішуватися окремо.\n\nПереглянути повний реєстр →CSFloat JSON ↗Skinport JSON ↗Заява компанії «Valve» щодо «2016» ↗\nПРЯМИЙ API CSFLOAT / ЗНІМОК З ВКАЗАНОЮ ДАТОЮ$13.63М\n\nМінімальна сукупна заявлена вартість у 241 категорій товарів та 3,395 активних пропозицій. Розраховується як найнижча ціна продажу в кожній категорії, помножена на кількість пропозицій у ній. Чотири категорії, зафіксовані на верхній межі CSFloat $100,000, виключені з цієї консервативної вибірки.\n\nЩо показує ця сума в доларах\n\nЦі пропозиції становлять щонайменше $13,631,888.25 у заявлених цінах на цю обмежену підгрупу CSFloat. Якщо врахувати чотири категорії з максимальними цінами, то отримаємо $14,231,888.25. Це — мінімальна ціна на активні заявки на купівлю, а не кількість здійснених продажів, грошовий оборот, прибуток чи весь ринок CS2.\n\nПерерахувати на основі знімка CSFloat із 245 рядками ↗\nPRICEEMPIRE / ВКАЗАНА ВАРТІСТЬSteam: № 15 із 39\nБагато закладів вказують суму, що перевищує Steam доларів.\nUUSkins\n$133.8М\nYouPin898\n$127.5M\nBuff.163\n$104М\nMoon.Market\n$100.3М\nWhite.Market\n$89.6М\nBuff.Market\n$86.7М\nSteam\n$31М\n\nШість найбільших значень, що відображаються, та Steam. PriceEmpire округлює ці цифри; Steam показує $31М. За вказаною вартістю у доларах попереду нього знаходяться чотирнадцять об’єктів зі списку.\n\nPRICEEMPIRE / КІЛЬКІСТЬ ПРОПОЗИЦІЙSteam: № 1 із 39\nSteam як і раніше лідирує за кількістю пропозицій.\nSteam\n32,2 млн\nYouPin898\n5,9 млн\nC5Game\n4,6 млн\nHaloSkins\n4,4 млн\nSkinport\n3,8 млн\n\nSteam показує 32,2 млн пропозиції. Кількість пропозицій та загальна заявлена вартість дають відповіді на різні питання; у загальній кількості можуть переважати оголошення з низькою ціною.\n\nДжерело: Публічне порівняння від PriceEmpire ↗ архів 2026-09-21 ↗, зафіксовано 2026-09-20 о 19:03 за UTC; витяг за 39 рядків ↗. Наведені цифри є округленими оцінками, а асортимент товарів може частково збігатися між різними майданчиками. На картці Steam також описані предмети з інших ігор Steam, тому обсяги не збігаються. Вказана вартість відображає запитувану ціну, а не обсяг продажів чи виручку.\n42\nІНШЕ ДЖЕРЕЛО / STEAMANALYST\nКомерційна екосистема лежить на поверхні.\n\nКаталог ринків від SteamAnalyst архів 2026-07-19 ↗ містить перелік із 42 сторонніх торгових майданчиків CS2, а також Steam, із актуальними даними про ціни для 32 із 43 позицій. PriceEmpire наводить перелік із 39 торгових майданчиків, відібраних за власними критеріями. Названі компанії, публічні пропозиції, видимі ціни: ця економіка відкрита для перевірки.\n\nМЕЖА — ЦЕ МЕХАНІЗМ: ПРОДАЖ ВИЧЕРПУЄТЬСЯ, А ТОВАР — НІ.\n\nНа п’яти торгових майданчиках, відображених на одному ліцензованому знімку, Ціни на 248 категорій товарів CS2 окремо перевищують встановлений Steam верхній межу вартості, що становить приблизно $1,800, на суму, що дорівнює двом або більше таких меж — і жодна з них не представлена в Steam. Цей самий знімок розподілив весь каталог за ціною: на ринку Valve представлено 95.3% категорій товарів, ціна яких нижча за встановлений ліміт, та 1.9% категорій, ціна яких вища за нього. Таке скорочення асортименту не пов’язане зі зниженням попиту; воно повністю відповідає опублікованим правилам. Продаж за цими цінами вимагає залучення зовнішнього покупця або торговельної платформи, тоді як Steam як і раніше контролює запаси та передачу — операція залишає касу Valve, а доставка здійснюється на інфраструктурі Valve.\n\nSteam Поширені запитання про ринок ↗архівувати 2026-09-21 ↗Steam Угода з абонентом ↗архів 2026-09-21 ↗Набір даних атласу «Five-marketplace» ↗Декларація походження ↗Попередній знімок CSFloat ↗Короткий огляд Skinport ↗PriceEmpire ↗архів 2026-09-21 ↗SteamAnalyst ↗архів 2026-07-19 ↗Реєстр цінових розбіжностей ↗Атлас цінової шкали ↗\n\nЧастина С — Правові рамки\nЧастина С — Правові рамки · Розділ 14 · Доступ персоналу\nХто може скинути захисні заходи?\nКонтекст та обмеження джерел\n\nБезпека облікового запису також залежить від осіб, які можуть відновити доступ до нього, переглянути приватні дані або скинути налаштування захисту. Під час розслідування слід так само ретельно відстежувати ці дії з привілейованим доступом, як і випадки зловживання API.\n\nПроцедура відновлення облікового запису надає співробітнику служби підтримки право перевести обліковий запис з-під контролю його власника. Valve двічі — у лютому 2023 року та в листопаді 2025 року — письмово підтвердило, що ці повноваження використовувалися для передачі облікових записів не тим особам. З інтервалом у тридцять три місяці, через один і той самий канал. Нижче: про те, чого вартий цей доступ, шість підтверджених випадків, а також те, що журнал Valve зберігає дані про кожен із них, але нікому їх не надавав.\n\nЗбережені свідчення / 9 травня 2025 року\nКвиток на відновлення, який призвів до вимкнення системи безпеки облікового запису, та заявлена втрата у розмірі $10,000\n\nКористувач у архіві звернень до служби підтримки повідомляє, що Steam служба підтримки скинула пароль та вимкнула захист облікового запису після того, як інша особа подала заявку на відновлення. Автор зазначає, що обліковий запис був неактивним протягом багатьох років, містив елементи з 2016–2017 років і мав Steam Guard, прив’язаний номер телефону та збережені коди відновлення.\n\n\"Steam Служба підтримки все одно надала комусь іншому доступ до мого облікового запису.\"\n\nЗаява від першої особи, збережена в steam_support_tickets_MEGA.json, запис № 110. Прочитати повний текст збереженого допису ↗\n\nЦе не просто невдача одного користувача. Той самий механізм — запит на допомогу, в результаті якого обліковий запис передається тому, хто надає давніші дані, — є офіційно задокументованим способом вирішення кожного випадку, наведеного в таблиці нижче, і Valve двічі зафіксував це в письмовій формі.\n\nВласник не може виграти цю суперечку. Система відновлення запитує перший CD-ключ, першу електронну адресу, першу картку, перший номер телефону. Ці дані містяться в базі даних Valve, і служба підтримки отримує до них доступ — за повідомленнями, дані сягають п’ятнадцятирічної давнини. Людина, яка має копію вашого файлу, завжди зможе надати більше інформації про вашу історію, ніж ви самі. Цілі підбиралися відповідно до критеріїв: неактивні протягом років, високої цінності та часто придбані з других рук, тому власник ніколи не знав оригінального ключа. Згодом облікові записи були повністю видалені, що перервало ланцюжок історії об’єктів, який спільнота використовує для відстеження скіну — видалення, яке звичайний користувач не може виконати без стандартного періоду очікування.\n\nПринцип мінімальних привілеїв / OWASP A01\n\nПрава на відновлення повинні обмежуватися конкретним завданням, підлягати незалежному контролю та реєструватися. Необхідно провести аудит щодо того, хто може скинути облікові дані, видалити Steam Guard, переглядати рахунки або експортувати дані облікового запису. Рекомендації OWASP щодо контролю доступу ↗ архів 2026-09-20 ↗\n\nШирокі можливості доступуРизик, пов’язаний із сферою доступу\nЗа межами інвентаризації.\n\nУ разі зловживання широким доступом до підтримки приватні телеметричні дані можуть стати інструментом для створення профілів, цільового фішингу та стеження. Серед потенційних жертв — звичайні користувачі, військовослужбовці, громадські діячі та їхні родини. Це модель загрози; для визначення точних дозволів необхідні записи про контроль доступу.\n\n01 Історія IP-адреси та місцезнаходження\nЖурнали IP-адрес можуть розкривати історію мережевих з'єднань та приблизне місцезнаходження. Самі по собі вони не дозволяють встановити точні фізичні переміщення.\n02 Ідентифікація пристроїв за допомогою відбитків\nІдентифікатори пристроїв, якщо вони зібрані та доступні, можуть пов’язувати сесії та облікові записи.\n03 Телеметрія активності\nЧасові мітки входу в систему та записи про сесії можуть розкрити звичні дії користувача, зокрема ті, що не відображаються у публічному профілі.\n04 Зв’язки та контакти\nДоступ до збережених повідомлень або контактної інформації розширив би можливості для створення профілів та застосування методів соціальної інженерії.\n05 Розкриття особи\nОригінальні записи електронної пошти, телефонних дзвінків та платежів можуть пов’язати анонімний обліковий запис із конкретною особою.\n06 Перепродаж даних та відповідальність\nЕкспортовані списки цільових осіб можуть використовуватися для здійснення цілеспрямованих шахрайських дій. Необхідно встановити особу зловмисника, місце доступу, одержувачів та перекази; саме по собі місцезнаходження не є підставою ані для доступу, ані для юридичного імунітету.\n\nValve описує в своєму документі ведення журналів IP-адрес, інформацію про пристрої, записи про платежі та сторонніх постачальників послуг підтримки Політика конфіденційності, §§ 3, 5.2 архів 2026-09-21 ↗. Ця політика дозволяє стороннім особам отримувати доступ для надання підтримки — проте ж аудиторський слід, який би показував, який підрядник отримав доступ до якої категорії, коли та на підставі яких повноважень, не був оприлюднений.\n\nРозділ 14.1 · реєстр · червень 2022 р. → листопад 2025 р. · всі цифри наведені з джерел\nValve двічі відчинив двері з інтервалом у тридцять три місяці. Вони так і не зачинилися.\n\nЗафіксовано шість випадків, коли облікові записи були викрадені через власний канал запитів про допомогу Steam або за допомогою облікових даних, які цей канал захищає. Кожна сума відповідає цифрі, опублікованій у зазначеному джерелі, і кожне джерело вказано. У двох із шести випадків збитки були повністю відшкодовані. Відмінність між цими випадками та рештою полягала не в тому, що сталося, а в тому, хто за цим спостерігав.\n\nValve, у письмовій формі — лютий 2023 року«Згадані предмети були видалені з вашого облікового запису, оскільки вони були отримані з облікового запису, який було зламано в результаті звернення до служби підтримки, відповідальність за що бере на себе команда CS:GO. Ми скасували ці обміни та видалили ці предмети з усіх облікових записів, на які вони надійшли».Steam Відповідь на повідомлення, надіслане одержувачу товарів HFB, опублікована Dexerto, 21 лютого 2023 року ↗ архів 2025-08-18 ↗\nValve, знову на папері — листопад 2025 року · через 33 місяці«Спеціаліст служби підтримки, який розглядав ваш запит, не дотримався встановленої процедури, внаслідок чого ваш обліковий запис було відновлено на ім’я іншої особи. Приношу свої вибачення за цю помилку».Steam Відповідь на коментар користувача Hawkeye337, цитований у Dexerto, 14 листопада 2025 року ↗\n21 червня 2022 року\nHFB — найбільший асортимент у грі$2,000,000+ · підвищено до $3,000,000+ під час повторного обстеження у лютому 2023 року\n\nСім сувенірних AWP Dragon Lores та №1 Blue Gem Karambit — вартість лише цього ножа становить приблизно $1.26 мільйонів. Акаунт не використовувався протягом трьох років, хоча мобільний аутентифікатор залишався активним; електронну адресу та пароль все одно було змінено за допомогою процедури відновлення через службу підтримки.\n\nГроші закінчилися раніше, ніж товари. За повідомленнями $200,000+ Частина коштів від продажу вже була знята через market.csgo.com — торговельну платформу, яка здійснює розрахунки як готівкою, так і криптовалютою. Скасування угоди передбачає повернення скіна. Готівка, яку хтось уже переказав на свій рахунок, не повертається.\n\nІ виправлення не спрацювало. Один покупець перемістив свій «Souvenir Dragon Lore» у внутрішньоігрове сховище. Скрипт відкоту Valve не міг побачити вміст власного контейнера, тому він видав власнику нову копію, а приховану залишив на місці — Valve продублював $130,000 предмет під час спроби скасувати крадіжку. Його було виявлено завдяки зіставленню ідентифікаторів предметів та повідомленням користувачів, і видалено через місяць, у липні 2022 року. Покупцеві було повернено кошти компанією BUFF, а не Valve. Настільки хаотичне усунення наслідків не є заходом контролю; це те, що робить платформа, коли не має контролю.\n\nDexerto, 21 червня 2022 р. ↗ архів 2022-07-02 ↗ · «Касперський» ↗ · сума виплати за Esportfire, 22 червня 2022 р. ↗ архів 2026-05-15 ↗, що, як там зазначається, походить із кількох джерел у Twitter · дублювання та видалення згідно з Esportsbetting, 14 липня 2022 р. ↗\n\nВідновленоУгоди були скасовані. Товари вилучили з запасів тих, хто заплатив за них повну ціну.\n14 серпня 2022 року\nCS.Money — власні боти платформи$6,300,000 · 19,000+ скіни · перша оцінка $1.6М\n\nЗловмисники викрали файли мобільних аутентифікаторів торгових ботів торговельної платформи та очистили їх, а потім надіслали частину викраденого відомим трейдерам, щоб заплутати сліди. Дослідники спільноти проаналізували 55 облікових записів зловмисників за кілька годин і опублікував їх.\n\nValve нічого не змінило. Причиною цього стало те, що сторонній сайт знаходиться поза межами Steam — того самого Steam, чиї рекламні ресурси, торговий API та система облікових записів були повністю задіяні в процесі крадіжки.\n\nEsportfire, 14 серпня 2022 р. ↗ архівувати 2025-11-15 ↗\n\nВідхиленоЗворотного перегляду не відбулося. Збитки залишилися за платформою та її користувачами.\nПовідомлено\n21 лютого 2023 року\nQkss — ті самі двері, той самий актор$1,000,000+\n\nЗа повідомленням, це було зроблено так само, як і у випадку з HFB: тим самим актором, через той самий запит на технічну підтримку. Проблема з HFB була повністю вирішена вісім місяців тому. А з Qkss — ні.\n\nОдин шлях. Дві відповіді. У опублікованих матеріалах немає нічого, що відрізняло б ці два випадки, окрім чисельності аудиторії.\n\nDexerto, 21 лютого 2023 р. ↗ архів 2025-08-18 ↗\n\nВідхиленоНе відновлено.\nПовідомлено\nЛютий 2023 року\nСама інсайдерська торгівля — цілий рік такої діяльності≈ $320,000 · розраховується за період приблизно в один рік, а не на основі оцінки запасів\n\nДоступ зі сторони підтримки дозволив переглянути історію рахунку за період до 15 років — перший CD-ключ, перший електронний лист, перша картка. Саме таких доказів вимагає процедура відновлення, і саме тому той, хто володіє базою даних, завжди виграє суперечку з тим, хто володіє обліковим записом.\n\nБлогер Mzkshow викрив, як оператор-інсайдер «Steam Help» та його спільник «Alexander» націлилися на неактивні акаунти, на яких зберігалося понад $100k скінів. Один викрадений M4A4 Howl з голограмами iBUYPOWER та Titan Katowice 2014 був проданий за $35,000 і справа дійшла до Валерія «b1t» Ваховського з команди NAVI, який не міг про це знати. Після втручання Valve підрядник звільнив весь свій Steam відділ технічної підтримки.\n\nVKPlay ↗ · Lis-Skins ↗ · Escorenews (RU) ↗ · Dexerto (англ.) ↗\n\nРеєстр відсутнійValve ніколи не оприлюднювала інформацію про те, скільки облікових записів це торкнулося, і не повідомляла про це самим користувачам.\nПовідомлено\n2 грудня 2024 року\n«Матвій» — після звільнень$13,000\n\nВідновлення доступу було надано особі, яка надала дані облікового запису, які сам власник не зміг підтвердити. Через два роки після того, як підрядник ліквідував свою службу підтримки Steam, той самий спосіб дав той самий результат.\n\nЗбережений допис, 2 грудня 2024 р. ↗ архів 2025-08-05 ↗ · вихідні рядки та хеші ↓\n\nВідхиленоНе відновлено.\n13 листопада 2025 року\nHawkeye337 (Марк Спурлок) — і друге зізнання≈ $300,000–$500,000 · повна колекція голографічних наклейок «Катовіце 2014»\n\nНападник вимагав 1 біткойн і почали переносити колекцію на Negevs, щоб знищити її. Steam Письмова відповідь служби підтримки є другим зізнанням, наведеним вище: технічний спеціаліст, який розглядав запит на допомогу, не дотримався встановленої процедури та передав обліковий запис іншій особі.\n\nПричиною виправлення став канал. Через кілька годин після того, як у мережі X з’явилися дописи з тегом Valve, акаунт було повернено, а всі стікери відновлено. У Qkss не було такої аудиторії.\n\nSkin.club ↗ · Dexerto ↗ · Esportfire ↗ архів 2025-12-17 ↗\n\nВідновленоПовідомлення було видалено через кілька годин після того, як ця новина стала популярною.\nТе, що випливає з бухгалтерської книги, чого не можна сказати про жодний окремий випадок.\n\nМаршрут ніколи не закривався. Перше зарахування відбулося в лютому 2023 року, а друге — в листопаді 2025 року — з різницею в тридцять три місяці, з масовим звільненням підрядника, задокументованим повторним випадком та порушенням безпеки платформи на суму $6.3 мільйонів, що сталося в проміжку між цими подіями. Якщо рахувати від першої крадіжки, зафіксованої в цьому реєстрі, канал залишався відкритим протягом три роки та п’ять місяців. Незалежно від того, що було виправлено у 2023 році, у листопаді 2025 року запит на допомогу все одно був перенаправлений не тій особі — це слова самого Valve.\n\nПри відшкодуванні збитків враховувалася ступінь уваги, а не ступінь шкоди. Відновлено: найбільший інвентар у грі та колекціонер, чий пост став популярним. Відхилено: $1,000,000, $6,300,000, $13,000. Valve ніколи не оприлюднював правило, яке застосовує, оскільки оприлюднене правило мало б пояснювати ці три випадки.\n\nНікому про це не повідомили. Ні користувачі, чиї історії облікових записів були вилучені з бази даних, ні наглядовий орган, ні ринок, який придбав ці товари в добросовісній вірі і був змушений їх повернути. Немає жодного повідомлення про порушення, жодного звіту про інцидент, жодних даних про кількість постраждалих облікових записів — а виручка залишилася у вигляді грошей, через торговельні майданчики, які здійснюють розрахунки готівкою та криптовалютою. Зворотна операція не може відбутися після виведення коштів із Steam.\n\nValve містить журнал аудиту підтримки, журнал запитів на відновлення та записи про транзакції для кожного рядка вище. Жоден із цих документів не було надано. Замовте свій примірник →\n\nПитання щодо NDA\nКонфіденційність має супроводжуватися технічною підзвітністю.\n\nПорівняйте угоди про конфіденційність із фактичними дозволами, заходами експортного контролю, дозволами на скидання налаштувань та журналами доступу. Шаблонна відповідь не може спростувати звинувачення в тому, що сам процес відновлення даних був використаний зловмисно.\n\nСтатті 28, 32–34 Загального регламенту про захист даних (GDPR)\n\nСтаття 33 надає контролеру 72 години на те, щоб повідомити наглядовий орган про витік персональних даних; стаття 34 вимагає інформувати постраждалих осіб, якщо ризик для них є високим. Компанія Valve двічі письмово підтвердила, що її служба підтримки передала облікові записи не тим особам — разом з історією облікових записів, даними про оплату та іншою інформацією. Жодного повідомлення відповідно до жодної з цих статей опубліковано не було, і жоден з користувачів, яких це стосується, не повідомив про його отримання. Ознайомтеся з правилами ↗ архівується 2026-09-20 ↗\n\nВкажіть у своєму запиті, що вам потрібна технічна підтримка →\nЧастина С — Правові рамки · Розділ 15 · Комерційний масштаб\nСлідкуйте за грошима. Розділяйте транзакції.\nКонтекст та обмеження щодо джерел\n\nПитання щодо комерційного використання стає ще гострішим, коли грошові потоки розділяються. Передача товарів третім особам, основні продажі Valve та зовнішні виведення коштів — це різні операції.\n\nЦей товар належить Valve. На складі є Valve. Передача здійснюється на серверах Valve. Лише оплата здійснюється десь інде — саме цей крок визначає, чи є особа оператором з переказу коштів, і саме цей крок Valve не виконується.\n\nМеханізм формування доходів\nДе насправді рухаються гроші.\nТри шляхи / економіка з одним предметом\n01 / Обліковий записПерелік користувачів\n\nКількість одиниць у запасі — Steam\n\n02 / ПередачаP2P-торгівля\n\nКористувач ↔ бот або користувач ↔ користувач\n\n03 / РозрахунокЗовнішня платформа\n\nЗакриття рахунку або погашення заборгованості Steam\n\nТиражЕкономічний ефект виходить за межі суми трансферного внеску\n\nSteam забезпечує інфраструктуру управління запасами та передачі, яку використовують зовнішні ринки. Економічна аргументація розслідування полягає в тому, що ліквідність при перепродажу та постійний попит підтримують витрати на кейси, ключі та запасні частини, а також забезпечують комісійні від подальших продажів на «Community Market». Прямий P2P-переказ не передбачає комісії «Community Market»; цей бухгалтерський факт не вирішує питання про більш широку вигоду. Valve зберігає контроль над доступом до рахунків та обмеженнями на торгівлю протягом усього процесу.\n\n01 / Вторинний попитЛіквідність та вартість при перепродажу\n\nЗовнішній попит на азартні ігри та азартні ігри\n\n02 / Основні видаткиКлючі, футляри та капсули\n\nПокупки з Valve, якщо така можливість передбачена\n\n03 / ДохідДохід від первинного продажу\n\nПлюс комісія з фактичних продажів на ринку\n\n5% + 10%Steam + комісія CS2 з продажів на Community Market\n\nЕкономічний висновок дослідження: ліквідні ринки перепродажу можуть стимулювати витрати на нові товари. Звичний показник 15% враховує ринкові ставки комісій, з урахуванням мінімальних значень та округлення; це не збір, що стягується з кожної зовнішньої угоди.\n\nТарифи на послуги «Community Market» від Valve ↗ архів 2026-09-21 ↗. 25 лютого 2026 року Генеральний прокурор штату Нью-Йорк подав позов архів 2026-09-01 ↗ у якому стверджується, що платні «лут-бокси» пов’язані з перепродажем за готівку та шкодою від азартних ігор — саме цей зв’язок і задокументовано в цьому досьє з точки зору технічної інфраструктури. Ця скарга є лише твердженням, а не встановленим фактом; вона наводиться тут тому, що державний правоохоронний орган поставив питання, пов’язане з тим, яке порушує це досьє: де ж дані про заходи з дотримання законодавства, що відповідають публічним заявам?\n\n01 / ВступКриптовалютний депозит\n\nЗаписи про зовнішні сервіси та гаманці\n\n02 / ПеретворенняБаланс → скіни\n\nТовари, доставлені в результаті Steam угод\n\n03 / ВихідЗовнішній продаж фіатних валют\n\nПродавець, покупець та постачальник послуг з виплати коштів\n\nKYC?Визначайте елемент управління під час кожного переходу\n\nСаме цей шлях слід розглянути, а не вбудовану службу конвертації готівки через API Steam. Перед тим, як підтвердити можливість виведення коштів без KYC, слід задокументувати перевірку особи, умови зберігання, ідентифікатори транзакцій та одержувачів виплат у кожного зовнішнього оператора.\n\nСполучені Штати Америки / Закон про банківську таємницю\nСпочатку класифікуйте діяльність, а потім — зобов’язання.\n\nFinCEN оцінює операції з переказу коштів виходячи з діяльності підприємства. Прийняття та переказ конвертованої віртуальної валюти може спричинити виникнення зобов’язань щодо надання грошових послуг, з урахуванням відповідних визначень та винятків. Гаманець Steam компанії Valve приймає кошти та конвертує їх на ігрові предмети; потім ці предмети реалізуються через сторонніх операторів в обмін на реальну валюту. Предмет та його передача здійснюються на інфраструктурі Valve; виведення коштів — ні, і те, чи відповідає якась частина цього циклу визначенням грошових переказів, є питанням класифікації для FinCEN, а не висновком, зробленим у цьому документі.\n\nFinCEN FIN-2019-G001, §§ 1–2, 5.1 ↗ архів 2025-07-11 ↗\n\nЄвропейський Союз / відмивання грошей\nВідстежуйте надходження коштів, отримуйте інформацію та допомогу.\n\nДиректива (ЄС) 2018/1673 стосується умисного відмивання коштів та участі у операціях із доходами від злочинної діяльності. Питання, яке стоїть перед слідством, полягає в тому, що саме знала компанія Valve про операторів, які використовували її торговельну інфраструктуру та інфраструктуру OpenID після 13 липня 2016 року, коли вона публічно описала таке використання, та які заходи вона вжила щодо них. Valve не опублікувала жодних даних про заходи щодо кожного оператора окремо; саме ці дані, а не дане досьє, дали б відповідь на це питання.\n\nСистема кримінального права ЄС ↗\n\nТермінологія AMLD6: Зазначена вище директива у сфері кримінального права відрізняється від Директиви (ЄС) 2024/1640, яка також називається AMLD6. Загальний термін транспонування останньої — 10 липня 2027 року, з урахуванням визначених винятків. Стаття 78 ↗ архівувано 2026-08-30 ↗\n\nЧастина С — Правові рамки · Розділ 16 · Повідомлення, відповідь, відповідальність\nЗакон про цифрові послуги: зафіксувати інформацію офіційно\nКонтекст та обмеження щодо джерел\n\nДва елементи повідомлення згідно зі статтею 16 належать до заявника, а не до цього досьє: власні реквізити заявника та заява про добросовісність щодо точності наданої інформації. Усе інше, що вимагає ця стаття — обґрунтоване пояснення та точне електронне місцезнаходження — викладено в Розділі 3 та в реєстрі маршрутів разом із збереженими відповідями та хеш-сумами, щоб будь-яка сторона могла подати відповідне повідомлення. Ще два обмеження самого закону: втрата звільнення від відповідальності за хостинг сама по собі не встановлює відповідальності за будь-яким іншим законом, а 6% у статті 52(3) є встановленою законом верхньою межею, а не призначеним штрафом у розмірі Valve.\n\nВідповідно до Закону про цифрові послуги (DSA) хостинг-провайдер зберігає імунітет від відповідальності лише до того моменту, поки він не отримає конкретну інформацію і не вживе відповідних заходів. Це досьє і є таким повідомленням. У ньому вказано хости, дати, збережені відповіді та хеші. З моменту публікації питання вже не полягає в тому, чи знав Valve, а в тому, що зробив Valve далі.\n\n01Липень 2016 року / виставка «Досьє»\nДесятиденний термін виконання вимоги.\n\nНаведене вище повідомлення є історичною відправною точкою для порівняння заходів щодо забезпечення виконання в рамках розслідування.\n\n0217 лютого 2024 року / загальна заявка\nЧасове вікно DSA.\n\nРозрізняйте поведінку в минулому та поведінку в період, коли діють відповідні зобов’язання згідно з Законом про цифрові послуги (DSA).\n\n03Десять років / знімок оригінального досьє\nДля тривалості потрібно створити ланцюжок повідомлень.\n\nЧас, що минув з липня 2016 року (див. розділ 11), є показником досьє. Це не десять років доведених порушень Закону про захист даних (DSA). Кожне повідомлення слід пов’язати з конкретним пунктом, відповідним законодавством, підтвердженням доставки та відповіддю.\n\nСтаття 52(3) / встановлений законом верхній межа6%\nщорічного світового обороту\n\nМаксимальний розмір штрафу за порушення зобов’язань згідно з Законом про цифрові послуги (DSA), розрахований на основі попереднього фінансового року постачальника. Це встановлений законом верхня межа, а не розмір штрафу, накладеного на Valve.\n\nСтатті 6, 8 та 16 / правовий критерій\n\nУ випадку відповідних послуг хостингу наявність конкретних знань та несвоєчасне вжиття заходів можуть призвести до втрати права на звільнення від відповідальності за хостинг. Достатньо чітке повідомлення може підтвердити обізнаність щодо конкретного контенту. Закон про цифрові послуги (DSA) не встановлює загального обов’язку моніторингу; втрата права на звільнення від відповідальності сама по собі не тягне за собою відповідальності згідно з іншим законодавством.\n\nDSA: статті 6, 8, 16, 52, 53, 93 та преамбула 17 ↗ архів 2026-09-20 ↗\n\nПереглянути збережені скарги ↗Створити хронологію облікового запису →Повний юридичний та економічний аналіз →\nЧастина C — Правові рамки · Розділ 17 · Ідентифікація, вік, доступ до комерційних послуг\nНеповнолітні: вхід із кодом Steam не є перевіркою віку\nКонтекст та обмеження джерел\n\nУ цьому досьє ніде не згадуються дані неповнолітніх, і жодних таких даних не збиралося: автори не реєструвалися, не розміщували інформацію та не входили в систему на жодній із згаданих платформ. Кожен, хто використовує інформацію з цього розділу, повинен зберігати конфіденційність доказів, що стосуються дітей, та вилучати ідентифікуючі деталі з публічних матеріалів. Закон COPPA згадується тут як законодавство про захист приватних даних дітей із власними умовами сфери застосування — аудиторія, фактична обізнаність, зібрані персональні дані — а не як загальне правило щодо віку для участі в азартних іграх; скарга, подана у 2026 році в штаті Нью-Йорк, є звинуваченням з боку державного органу, а не офіційним висновком.\n\n«Увійти за допомогою Steam» підтверджує наявність облікового запису. Це ніяк не свідчить про вік — і на цих сайтах це єдиний бар’єр між дитиною та поповненням рахунку. Прочитайте це разом із Розділ 3.1: у клієнті Steam попередження, яке зазвичай відображає браузер, ніколи не спрацьовує, тому дитина його ніколи не бачить.\n\nЩо пропонує Steam OpenIDІдентифікаційні дані облікового запису\n\nПеревірений SteamID, який використовується для входу в систему або прив’язки облікового запису.\n\n≠\nЩо повинен встановити операторПраво на участь\n\nВік, юрисдикція та будь-які необхідні перевірки особи.\n\nТехнічна основа: Документація Steamworks OpenID ↗ архів 2026-09-21 ↗. Задокументоване підтвердження особи не є свідченням того, що користувач має право брати участь у азартних іграх.\n\nCOPPA / діти віком до 13 років\nВизначте оператор та дані.\n\nЗакон COPPA поширюється на відповідні послуги, орієнтовані на дітей, а також на послуги, про які є фактична інформація про те, що вони збирають персональні дані дітей віком до 13 років. Це закон про захист приватного життя дітей, а не загальне правило щодо віку, з якого дозволено грати в азартні ігри. Необхідно визначити цільову аудиторію, персональні дані, що збираються, наявність інформації про це та процедуру отримання згоди батьків.\n\nFTC: Вимоги COPPA ↗ архів 2026-09-21 ↗\n\nДокази, які слід зберегти\nЗафіксуйте весь процес — від входу в систему до внесення депозиту.\n\nЗбережіть вікові обмеження сайту, формулювання умов реєстрації, вимоги до учасників, алгоритм здійснення платежів та історію скарг. Оцінюйте кожного оператора окремо. Забезпечте конфіденційність будь-яких доказів, що стосуються дітей, та вилучіть з публічних матеріалів відомості, що дозволяють ідентифікувати особу.\n\nВідповідним документом про примусове виконання у сфері громадського правопорядку є Оголошення про подання позову у Нью-Йорку у 2026 році архів 2026-09-01 ↗, в якому стверджується, що платні «лут-бокси» завдають шкоди молодим користувачам. Це не є висновком, зробленим на підставі закону COPPA.\n\nЧастина C — Нормативно-правова база · Розділ 18 · Запит відповідно до статті 15 GDPR\nЗапит. Відповідь. Відсутнє порівняння.\n\nВін попросив чотири речі, одна з яких — журнал, що дозволить встановити особу, яка додала API-ключ до його облікового запису. Через три дні заявку було закрито, додавши посилання на сторінку, на якій немає жодного з них — а твердження, яким завершується цей документ, спростовується самими адвокатами Valve.\n\nЧий це обліковий запис · Походження та обмеження\n\nЦі скріншоти не належать PhishDestroy. Вони надійшли від звичайного власника облікового запису Steam — одного з респондентів короткого опитування, проведеного в рамках цього проєкту, який самостійно подав запит і надав скріншоти. Рахунок належить йому, запит — його, а листування ведеться між ним та службою підтримки Steam. Цей проєкт не подавав запиту, не має рахунку на платформі та не є стороною цього запиту.\n\n16 вересня 2026 року він подав запит на доступ до даних відповідно до статті 15 GDPR/CCPA, в якому конкретно вимагав надати журнали реєстрації API-ключів, історію входів із зазначенням IP-адрес, історію авторизації пристроїв та історію торгових операцій. 17 вересня оператор «Logen» перенаправив його на сторінку самообслуговування «Дані облікового запису». 18 вересня він зазначив, що запитувані категорії даних на цій сторінці відсутні, та попросив передати його звернення до команди з питань конфіденційності або відповідального за захист даних (DPO). 19 вересня оператор «Kal» закрив запит, надавши ту саму рекомендацію. Обидва знімки екрана наведено нижче (адреса електронної пошти заявника приховано; SHA-256 у steam_tos_assets/screenshot-manifest.json).\n\nВін є гідним замовником з цілком звичайної причини: його обліковий запис містить ключ Web API Steam, який він не створював і який зареєстровано на localhost. Невідомо, коли вона була створена — не йому і не з того, що Valve надав йому, оскільки єдиним записом, який міг би підтвердити дату, є журнал реєстрації API-ключів, а саме цю категорію даних суд ухвалив не розкривати. Ключ не є новим: він існував ще до того, як він про нього дізнався, і цей проміжок часу він не може визначити саме з тієї ж причини.\n\nІнші власники облікових записів подають такий самий запит. Будь-яка отримана відповідь буде додана сюди на тих самих умовах, що й ці дві — номер квитка, дата отримання, SHA-256, ім’я заявника приховано — незалежно від того, чи надаються категорії, чи відмовляють у їх наданні.\n\nЦей проєкт не висловлює жодної думки щодо причин закриття квитка. У ньому не було вказано жодної причини, і тут також не робиться жодних припущень з цього приводу.\n\nЗапит. Відповідь. Порівняння.СЛІДКУЙТЕ ЗА РЕЗУЛЬТАТАМИ\nКрок 3 / 3\n\nВін попросив надати чотири конкретні категорії. Сторінка «Дані облікового запису», на яку його скерували, — це власна функція самообслуговування Valve для експорту даних, і цей проєкт не може перелічити її вміст для чужого облікового запису — тому повне порівняння за категоріями тут не опубліковано. У протоколі зафіксовано його заяву від 18 вересня про те, що цих категорій там не було, а також рішення про закриття справи від 19 вересня, в якому повторно наводилося посилання, але без розгляду цього питання.\n\nЗАПИТКонкретні категоріїAPI-ключ, логін, дані про пристрої та операції\nВІДПОВІДЬДовідка щодо даних облікового записуПеревірте обмін опор\nТЕСТЩо було поставлено?Порівняйте кожну з обраних категорій\nЕкран 1/2 — Запит (16 вересня) та перша відповідь, агент «Logen» (17 вересня)\nGDPR ticket HT-2YBP-F7JP-D4VB — request and first response\nДжерело: help.steampowered.com, запит HT-2YBP-F7JP-D4VB · зафіксовано 16–17 вересня 2026 року · електронна адреса заявника прихована 2026-09-21 · Файл: gdpr-ticket-1.png · SHA-256 da940c731ab9869d226e9d06ccc8a1b393738766b7b0c445a56662623e025a66 (screenshot-manifest.json).\nЕкран 2/2 — Запит на ескалацію (18 вересня) та закриття справи, оператор «Кал» (19 вересня)\nGDPR ticket HT-2YBP-F7JP-D4VB — escalation request and closure\nДжерело: help.steampowered.com, запит HT-2YBP-F7JP-D4VB · зафіксовано 18–19 вересня 2026 року · Файл: gdpr-ticket-2.png · SHA-256 44844ea7b251f7fd7d79f87ee1578a846606a97b9659d3a53b322120c422219b (screenshot-manifest.json).\nЗаключна відповідь, 19 вересня (дослівно):\n«Дані Steam, які зберігаються, вже можна переглянути на сторінці «Дані облікового запису». Оскільки служба підтримки не може надати Steam додаткової інформації, Цей запит буде закрито.\"\nДані не надано · правові підстави для відмови не вказано · результат розгляду не вказано\nЦе твердження є неправдивим, і це підтверджують самі адвокати Valve. У листі адвоката від 1 жовтня 2025 року, у пункті 1.9, описано кореляцію на рівні пристроїв, що пов’язує один пристрій із десятками облікових записів (Додаток А). Ця ж відповідь містила 830 сторінок збережених документів (Додаток Б). На сторінці «Дані облікового запису» цього немає.\nЧому цей обліковий запис запросив журнал API-ключів\n\nВін не вибрав ці чотири категорії навмання. Цей localhost ключовим моментом у його справі є ознака скрипта, а не людини, яка вводить реальний домен на сторінці розробника (Розділ 5, Розділ 6). Єдиний запис, з якого видно, хто його створив і звідки, — це журнал реєстрації API-ключів. Це було перше, про що він попросив. Саме цю інформацію компанія «Closure» приховала.\n\nДжерело: власник облікового запису під час опитування в рамках цього проєкту. Наведені вище скріншоти квитків мають хеш-код; сторінка з ключем не опублікована.\n\nОцінка · PhishDestroy\n\nЗакриття квитка, коли питання залишається відкритим, тут не є випадковістю. Це цілком нормальний результат. Ми дотримуємося 16,319 збережені записи про скарги та звернення за допомогою та 354 обміни зверненнями до служби підтримки з усуненням дублікатів отриманих з них. Цей квиток є одним із датованих, повністю збережених прикладів їхньої форми.\n\nЗапит на підтримку — ЗбереженоHT-2YBP-F7JP-D4VB\nТип запитуСтаття 15 GDPR (запит на доступ до даних)\nСтатус квиткаЗАКРИТО 19 ВЕРЕСНЯ 2026 Р. — ДАНІ НЕ НАВЕДЕНО\nАгенти на біржі«Логен» (17 вересня), «Кал» (19 вересня)\nПодано16 вересня 2026 року\nНеобхідні даніХто зареєстрував ключ веб-API, пов’язаний із цим обліковим записом, та з якої IP-адреси / пристрою / у який момент часу\nПосилання на правові підставиСтаття 15 Загального регламенту про захист даних (GDPR) — право на доступ до персональних даних\nПравові засади:Стаття 12(3) надає контролеру один місяць з моменту отримання (з можливістю продовження за наявності обґрунтованих підстав). На момент публікації цей строк ще не закінчився, і в цьому досьє не стверджується про порушення строку. Заперечення стосується суті справи: у заключній відповіді наведено посилання на сторінку самообслуговування, але не показано, що було надано чотири зазначені категорії даних, а якщо контролер відмовляється вживати заходів, стаття 12(4) вимагає від нього вказати причини та шляхи подання скарги. Ні того, ні іншого у заключній відповіді не міститься.\nЧому саме ці дані мають значення\n\nЖурнал подій ключів Web API — це запис, який показує, чи зареєструвала третя сторона ключ із використанням викраденого сесійного файлу cookie — механізм, описаний у скаргах щодо крадіжки інвентарю, що зберігаються в архіві цього досьє. Розкриття інформації про те, хто зареєстрував ключ API, з якої IP-адреси та в який момент часу, дозволило б:\n\nНадайте потерпілому можливість порівняти IP-адресу, з якої було створено API, зі своєю історією входу в систему\nВиявити IP-адреси центрів обробки даних, пов’язані з відомою інфраструктурою фішингових та азартних ігор\nНадати докази, які можуть бути використані в цивільному або кримінальному провадженні проти винуватця\nПоказати, чи було повідомлено власника облікового запису про створення ключа\nЩо свідчать матеріали справи: Valve зберігає записи на рівні пристроїв та записи про взаємозв’язки між обліковими записами — про це йдеться у листі її юридичного представника від 1 жовтня 2025 року (див. Додаток А, Меморандум щодо доказів — Джерело 1). У запиті HT-2YBP-F7JP-D4VB суб’єкт даних вимагав записів того самого класу, і цей запит було закрито з посиланням на сторінку самообслуговування, яка, за повідомленням суб’єкта даних, не містила цих записів. Чи є така відмова законною — це питання, яке має вирішувати наглядовий орган; наслідком цього є те, що особа, якої стосуються дані, не отримує їх.\nЛистування — чотири повідомлення, три дні\n\nДвоє співробітників служби підтримки Steam відповіли, вказавши імена, зазначені в запиті: «Logen» — 17 вересня та «Kal» — 19 вересня. Обидва скерували заявника на сторінку «Дані облікового запису». У запиті немає жодних відомостей про те, чи надійшов він до команди з питань конфіденційності або до відповідального за захист даних компанії Valve, а в матеріалах справи не вказано, хто саме є цими співробітниками, які посади вони обіймають та яким чином було спрямовано цей запит.\n\n16 вересня\nСтаття 15: запит, поданий щодо чотирьох зазначених категорій даних\n17–18 вересня\nПосилання на дані облікового запису; заявник просить передати питання на розгляд відповідальному за захист даних\n19 вересня\nЗаявка закрита з тим самим посиланням; даних немає, підстави не вказано\nНа що, згідно зі статтею 15 Загального регламенту про захист даних (GDPR), суб’єкт даних має чітко визначене право\nСтаття 15, пункт 1, підпункт а)Цілі обробки — чому компанія Valve зберігає дані\nСтаття 15, пункт 1, підпункт b)Категорії даних — що містить Valve\nСтаття 15, пункт 1, підпункт (c)Одержувачі або категорії одержувачів — хто отримав ці дані (наприклад, власник ключа API)\nСтаття 15, пункт 1, підпункт d)Термін зберігання або критерії його визначення\nСтаття 15, пункт 3Копія персональних даних, що підлягають обробці, — тобто сам журнал API-ключів\nСТ. 12(3)Необхідно надати відповідь протягом один місяць з моменту отримання; про продовження строку необхідно повідомити протягом цього місяця. На момент публікації цей строк ще не закінчився. Стаття 12, пункт 4: якщо контролер не вживає заходів, він повинен пояснити причини цього та повідомити суб’єкта про способи подання скарги.\nПроцедура подання скарги щодо дотримання нормативних вимог — для будь-якого користувача\n\nБудь-який користувач, який надіслав запит відповідно до статті 15 GDPR на адресу Valve і не отримав відповіді, що відповідає вимогам (або отримав шаблонну відмову без зазначення даних), може подати скаргу до наглядового органу у своїй країні-члені ЄС/ЄЕЗ. Представництвом Valve в ЄС є компанія Valve GmbH у Гамбурзі, тому головним наглядовим органом для розгляду транскордонних скарг є Гамбурський уповноважений з питань захисту даних та свободи інформації (HmbBfDI). (Представник згідно зі статтею 27 Valve також знаходиться в Гамбурзі; сама по собі адреса представника не визначає компетентний орган.) Скаргу також можна подати до органу у власній державі-члені скаржника відповідно до статті 77.\n\nФорма подання скарги до HmbBfDI ↗ Текст GDPR (ст. 12, 15, 77) ↗ архів 2026-09-20 ↗Рекомендації Європейської ради з захисту даних (EDPB) ↗\n\nНомер квитка для подання скарги: HT-2YBP-F7JP-D4VB — зафіксовано в цьому досьє як задокументований випадок.\n\nОдин задокументований випадок\nЗаписи існують; суб’єкт даних їх не отримав.\n\nАдвокат Valve описав записи про кореляцію на рівні пристроїв у листі від 1 жовтня 2025 року. 19 вересня 2026 року запит відповідно до статті 15 щодо записів того самого класу було закрито з перенаправленням на сторінку самообслуговування, яка, за повідомленням заявника, не містила цих записів, без зазначення правової підстави. Заявка HT-2YBP-F7JP-D4VB є одним із задокументованих випадків; чи відображає вона більш поширену практику — це питання до наглядового органу, який може звернутися до Valve із запитом щодо записів про обробку даних.\n\nСтатті 12, 15, 77 GDPR / Наглядовий орган\n\nСкаргу відповідно до статей 12 та 15 можна подати безпосередньо до відповідного наглядового органу без сплати збору (стаття 77). Орган може вжити виправних заходів, зокрема видати розпорядження про виконання запиту на доступ, а також накласти штрафи відповідно до статті 83(5)(b) за порушення прав суб’єктів даних. Збереження оригінального номера квитка та будь-якої відповіді Valve (або її відсутності) посилює аргументи скарги.\n\nПереглянути шаблон запиту на доступ до даних (DSAR) →\nЧастина С — Правові рамки · Розділ 19 · Договірне право\nУгода з абонентом, що суперечить власній архітектурі платформи\nКонтекст та обмеження джерел\n\nАвтори не є юристами, і жодна з наведених тут інформації не є юридичною консультацією. Цитування з SSA взято з редакції від 10 вересня 2026 року; в іншій редакції формулювання може відрізнятися, а нумерація пунктів змінювалася від редакції до редакції — слід звіряти номер пункту з тією версією, яка регулювала відповідну поведінку. Аргументи, наведені у статтях 25 та 32, визначають вимоги нормативного акту, а не те, що наглядовий орган встановив факт порушення. Цифри в аргументі 1 містять обмеження сфери застосування, визначені у розділі 13.\n\nТри основні положення SSA суперечать архітектурі платформи: заборона комерційного використання на тлі встановленого для ринку цінового обмеження, що витісняє угоди з високою вартістю за межі платформи; пункт про відповідальність користувачів за API-ключі суперечить кінцевій точці доступу, яка до 2023 року не вимагала двофакторної аутентифікації; а також формулювання щодо забезпечення дотримання вимог суперечить публічним даним, які свідчать про відсутність заходів щодо забезпечення дотримання вимог окремими операторами. Чи впливають ці суперечності на можливість забезпечення дотримання вимог — це питання, яке має вирішувати суд; у цьому розділі викладено факти, які будуть представлені на розгляд суду.\n\nАргумент 1 / Архітектура ринкової капіталізації\nМаксимальна ринкова ціна та заборона використання в комерційних цілях\n\nНа ринку «Steam Community Market» встановлено верхню межу цін на рівні приблизно $1,800. За даними знімку стану на певну дату (23 вересня 2026 року) на п’яти торгових майданчиках ціни на 248 категорій товарів CS2 на двох або більше з них перевищують цю верхню межу; такі товари не можна продавати за цими цінами на власній платформі Valve. Власники, які бажають встановлювати такі ціни, користуються сторонніми торговими майданчиками, що працюють на рахунках Steam та через API Steam — SSA класифікує їх як комерційні, якщо це прямо не дозволено.\n\nТовари перевищують ліміт ринку → цю прогалину заповнюють сторонні ринки → ці ринки використовують облікові записи Steam та API Steam → SSA забороняє комерційне використання без дозволу → реєстр дозволів не опубліковано. Сукупна комісія Community Market у розмірі приблизно 15% застосовується лише до продажів, здійснених у межах ринку, а не до цих зовнішніх угод.\nАргумент 2 / Архітектура безпеки API-ключів\nУразливість API-ключа — це проблема, пов’язана з архітектурою платформи, а не з недбалістю користувачів\n\nДо 2023 року кінцева точка створення API-ключів у Steam приймала запит POST із викраденим ідентифікатором сеансу та генерувала облікові дані з високим рівнем привілеїв без підтвердження електронною поштою, другого фактора або перевірки пристрою. Скарги щодо викрадення API, зібрані в ході цього розслідування, мають однакову схему: скрипт зловмисника, викрадене сесійне cookie, приховане створення ключа, перехоплення транзакції (вміст запиту наведено в розділі 8).\n\nСтаття 25 GDPR (захист даних на етапі проектування) та стаття 32 (безпека обробки) вимагають вжиття технічних заходів, що відповідають рівню ризику. Видача облікових даних, які можуть бути перехоплені під час передачі, без застосування другого фактора аутентифікації або повідомлення власника є питанням проектування, яке належить вирішувати контролеру. Чи можна в таких умовах покладатися на положення SSA, що покладає відповідальність на користувача, — це питання, яке має вирішувати суд та наглядовий орган.\n\nАргумент 3 / Можливість відстеження в режимі реального часу\nValve отримує ім’я хоста для автентифікації під час кожного входу в систему\n\nІм’я хоста автентифікації надходить на кінцеву точку OpenID користувача Valve у вигляді відкритого тексту у openid.return_to та openid.realm (форма запиту наведена в розділі 3). Витягнення цієї інформації є стандартною операцією. Станом на 2026-09-22 у 26 парах основний домен перебував у фільтрі посилань, тоді як хост, що містив його Steam логін, — ні. Valve не опублікував жодних даних щодо заходів, вжитих щодо окремих операторів, тому на основі відкритих даних неможливо встановити, чи застосовувалися до цих хостів якісь інші заходи, окрім фільтрації каналів зв’язку.\n\nХто несе витрати\nЗакономірність у заархівованих скаргах\n\nУ розглянутих скаргах відповідь служби підтримки Steam на заяву про викрадення API-ключа має однаковий формат: відмова у відновленні, посилання на відповідальність користувача за обліковий запис та його API-ключ, закриття запиту. У цьому досьє не наведено загальних даних щодо кількості постраждалих облікових записів або суми втрат; джерела таких даних виявлено не було.\n\nПитання полягає не в тому, чи припускалися окремі користувачі помилок. Питання полягає в тому, хто несе відповідальність за архітектуру, яка аж до 2023 року дозволяла за допомогою POST-запиту зі вкраденим файлом cookie створювати облікові дані для торгівлі з високим рівнем привілеїв без будь-якого сповіщення та без другого фактора аутентифікації.\nSSA як документ проти SSA як договору\nСуд, який розглядатиме цю справу, не буде тлумачити Закон про соціальне забезпечення (SSA) у відриві від контексту.\n\nЦей документ слід розглядати разом із листом адвоката від жовтня 2025 року, в якому описано кореляцію на рівні пристроїв, дати реєстрації авторизаційних хостів, часові мітки реєстрації партій, дані запиту на API-ключ, а також десятирічний проміжок між повідомленнями від липня 2016 року та платформами, що все ще функціонували у вересні 2026 року. Саме на ці дані Valve мав би звернути увагу.\n\nSSA у порівнянні з даними справи / основні моменти\n«Без комерційного використання» — обмеження ринку змушує продавців дорогих товарів звертатися до комерційних ринків третіх сторін\n«Користувачі несуть відповідальність за API-ключі» — до 2023 року на кінцевій точці ключа не буде застосовуватися двофакторна автентифікація\n«Ми вживаємо заходів щодо порушників» — з липня 2016 року не опубліковано жодних даних про заходи щодо окремих операторів\n«Ви погодилися з умовами» — у схемі «викрадення» підтвердження надсилається скриптом, а не власником облікового запису\nВисновок · Що підтверджують матеріали справи та про що ми просимо\nРезультати. Документи, які ми просимо надати.\nКонтекст та обмеження джерел\n\nКожен наведений нижче висновок пов’язаний із датованим публічним документом у розділах вище. Запити адресовані органам влади, які можуть забезпечити те, чого не вдається досягти в рамках цього розслідування: власні записи Valve щодо виконання, доступу та обробки даних.\n\nКожен запит ґрунтується на висновку з зазначенням дати. Влада може вимагати документи, які в рамках цього розслідування на основі відкритих джерел отримати неможливо.\n\nЩо підтверджують офіційні дані\n44 активні платформи проходять аутентифікацію через окремий домен, який підлягає реєстрації — 27 із опублікованим файлом доказів для кожного маршруту, 17 — зібрані вручну та перелічені окремо. Станом на 2026-09-22 у Steam Link Filter було заблоковано головний домен 26 пар, тоді як хост, на якому розміщувався їхній логін, не був заблокований — csgogem.com заблоковано, api.csgem.com зареєстрований з березня 2014 року. Steam отримує це ім’я хоста в openid.realm та openid.return_to при кожному вході в систему. Розділ 3\n13 липня 2016 року Valve офіційно назвав цей механізм і заборонив його, а в повідомленнях його юристів від 20 липня 2016 року було встановлено десятиденний термін. За десять років, що минули з моменту закінчення цього терміну, не було опубліковано жодних даних щодо заходів щодо виконання вимог щодо кожного оператора окремо. Розділ 11\nКінцева точка ключа веб-API Steam видавала облікові дані з високим рівнем привілеїв, що дозволяли здійснювати торгові операції, лише на основі сесійного файлу cookie, без додаткової аутентифікації до 2023 року. Розділ 5\nЗапит відповідно до статті 15 GDPR (номер квитка HT-2YBP-F7JP-D4VB) було закрито через три дні з посиланням на сервіс самообслуговування та без надання даних. Розділ 18\nЩо ми просимо від кожного органу влади\nКомісія з питань азартних ігор штату Вашингтон\nВідкрийте файл за 2016 рік. Запросіть детальний звіт по кожному оператору, в якому вказано, які облікові записи, боти та хости-відправники були заблоковані після десятиденних попереджень, а також які оператори згодом відновили доступ. Розділ 2\nHmbBfDI (Гамбург; Valve GmbH)\nПеревірити, чи відповідала відповідь, надана відповідно до статті 15, обов’язку контролера, та вимагати розкриття записів про реєстрацію API-ключа та записів про доступ, що мають значення для ідентифікації суб’єкта. Розділ 18\nКоординатори цифрових послуг DSA\nВнесіть маршрутизацію auth-host до запису як зауваження, а потім, після документування отриманої інформації, оцініть, чи відповідає відповідь Valve встановленим вимогам. Розділ 16\nБудь-яка особа, якої стосуються дані\nСкористайтеся шаблоном, передбаченим статтею 15, щоб подати запит на отримання тих самих записів щодо вашого власного облікового запису; збережений запис може допомогти встановити, хто ініціював скидання налаштувань або створив ключ. Додаток G\n\nЄдина вимога, що лежить в основі всіх чотирьох випадків, однакова: оприлюднити записи щодо забезпечення дотримання вимог, доступу та обробки даних, які зберігає виключно Valve. Попередження на головній сторінці, десятиденний лист та сторінка самообслуговування є проявами контролю. Чи здійснювався цей контроль — це питання, на яке не можуть відповісти публічні записи, але на яке може відповісти регуляторний орган.\n\nДодатки — основні докази та робочі матеріали\nДодаток А — Листування з адвокатами\nМеморандум щодо доказів — матеріали, надані джерелом № 1\n\nДоказова база та статус джерел, на які посилається адвокатська кореспонденція, наведена в розділах 1, 18 та 19.\n\nДоказова база та статус джерела — документи, надані джерелом № 1\nКористувач, постійна блокада якого стала приводом для проведення цієї перевірки, не є її об’єктом. Питання про те, чи була ця блокада виправданою, тут не розглядається, і в цьому досьє її не обстоюють і не заперечують. Справа не в обліковому записі. Важливе значення має саме матеріал: Джерело 1 — власник заблокованого облікового запису, який отримав наведене нижче листування від адвоката Valve як суб’єкт даних у рамках власного запиту відповідно до GDPR, — надав це листування та супровідні матеріали справи, а також право на їх публічний перегляд. Ім’я не розголошується; документи описано за датою, метаданими про автора та хешем.\n\nЦя переписка була надіслана у відповідь на запит згідно з GDPR/DSAR. У ході цієї переписки адвокат Valve вніс до протоколу підписану заяву, в якій описувалася функція, про яку служба підтримки Steam раніше повідомляла користувачам, що вона технічно неможлива. Наведений нижче абзац є цією заявою.\n\nПодальший аналіз авторами отриманого витягу з журналу полягає в не включено до цього досьє до проведення незалежної експертизи. Жодна інша частина цього розслідування не спирається на ці дані.\n\nОфіційне визнання: постійний збір телеметричних даних на рівні пристрою\n\nУ пункті 1.9 листа, який, як вважається, надіслав адвокат Valve, адвокати Valve зазначають: «У період з 2019 по 2023 рік цей обліковий запис використовувався переважно з пристрою, з якого також здійснювався вхід у десятки викрадених облікових записів Steam».\n\nФакт: Адвокат Valve описує тут кореляцію на рівні пристроїв між обліковими записами за чотирирічний період. Служба підтримки Steam повідомляла жертвам крадіжок, що відстеження викрадених предметів або прив’язування облікових записів до пристроїв технічно неможливе. Steam Guard Процедура авторизації пристроїв є загальнодоступною інформацією, тому сам факт існування записів щодо окремих пристроїв не є новим; новим є письмове підтвердження адвоката про те, що ці записи зберігаються та корелюються між обліковими записами протягом багаторічних періодів.\n\nЧому це важливо: Кореляція, яка дозволяє пов’язати один пристрій із десятками викрадених облікових записів за чотири роки, належить до того самого класу записів, які, за словами Служби підтримки, не можна використовувати для допомоги потерпілим. Записи цього класу дозволили б ідентифікувати облікові записи та пристрої в ланцюжку крадіжок та перепродажу. Які саме записи існують, як довго вони зберігаються та на якій підставі вони не надаються суб’єктам даних — це питання, які має вирішувати наглядовий орган.\n\nДжерело: лист адвоката Valve від 1 жовтня 2025 року, пункт 1.9, та додаток у форматі PDF обсягом 830 сторінок · отриманий Джерелом 1 у відповідь на запит згідно зі ст. 15 GDPR · SHA-256 цього додатка зафіксовано в disclosure-audit.json · Сам лист не наводиться; назви рахунків та дані третіх осіб опущені.\n\nСтатус: відкрити\nЗ вихідними матеріалами можна ознайомитися в архіві доказів.\nДодаток Б — Створений PDF-файл · перевірка редагування\nРедагування у створеному PDF-файлі має суто косметичний характер: прихований текст залишається доступним для вилучення\n\nЮрист компанії Valve відповів на запит про доступ відповідно до GDPR, надавши додаток обсягом 830 сторінок, у якому вилучені фрагменти тексту були зафарбовані, а не видалені. 902,270 символів розташовані під чорними смугами і відразу виводяться за допомогою інструменту для вилучення тексту — включаючи ідентифікатори сторонніх джерел, які ці стовпчики мали приховати. Тут опубліковано лише зведені дані; жоден з конфіденційних матеріалів не наводиться, а сам додаток не публікується.\n\n1. Що виявила перевірка геометрії\n\nВідповідь відповідно до статті 15 Загального регламенту про захист даних (GDPR) від 1 жовтня 2025 року до нього було додано додаток у форматі PDF обсягом 830 сторінок (метадані виробника Aspose.PDF для .NET, створені та змінені того ж дня). Автори провели перевірку геометрії на рівні сторінок: для кожної сторінки виявляли непрозорі, майже чорні прямокутники, нанесені поверх шару тексту, та підраховували символи, які можна було виокремити з-під них.\n\nВиміряно на основі створеного файлу\n902,270\nСимволи, які все ще можна витягти з-під чорних смуг\nПідраховано, а не оцінено. Це кількість персонажів, про яких йдеться у матеріалі, — а не жертв, випадків повторної ідентифікації чи інцидентів.\n830 / 830\nСторінки, яких це стосується — усі сторінки\n986\nПрямокутники над текстом, який можна виділити\n1,329\nЗагальна кількість непрозорих чорних прямокутників\nЧорні смуги накладені на шар з текстом; вони не видаляють його. Текст, що знаходиться під смугами, можна витягти за допомогою стандартних інструментів для роботи з PDF-файлами. Публікуються лише загальні статистичні дані; прихований вміст тут не наводиться.\nКриміналістична демонстрація: розділення шарів\nМАКЕТ ВЕКТОРНОГО НАКЛАДАННЯ ДЛЯ ASPOSE.PDF ДЛЯ .NET (ДОДАТОК, С. 412)\n\nПодано скаргу щодо цього облікового запису: [ЛОГІН: redacted_user_667]\n\nПричина, вказана користувачем: [ТЕКСТ: «Користувач повідомляє про дублікати предметів у інвентарі та недобросовісну торговельну поведінку...»]\n\nНа передньому плані: <path fill=\"#000\" />Недолік: Базовий потік UTF-8 залишається незмінним\nДжерело: додаток у форматі PDF до листа юридичної фірми від 1 жовтня 2025 року (830 сторінок, метадані виробника Aspose.PDF для .NET) · підрахунок здійснено авторами, метод та кількість сторінок у disclosure-audit.json · SHA-256 додатка, записаного в тому самому файлі · сам додаток не опубліковано.\n2. Чому це важливо для відповіді суб’єкта даних\n\nАдвокат Valve надіслав цей файл суб’єкту даних у відповідь на запит щодо його власних даних. Ці смуги мають суто косметичний характер: текст під ними так і не було видалено, тому сторонні ідентифікатори, які ці смуги мали приховати, надійшли одержувачу разом із файлом. Редагування, яке можна видалити за допомогою інструменту для вилучення тексту, нічого не приховує, а також не дає одержувачу можливості встановити, що саме було розкрито, а що — ні.\n\nСаме пункт 4 статті 15 є причиною існування цих обмежень: право на отримання копії не повинно негативно впливати на права та свободи інших осіб. Саме цього зобов’язання не дотримався даний виробник. Чи можна це кваліфікувати як порушення захисту персональних даних відповідно до статті 4(12), має визначити наглядовий орган; саме розкриття інформації можна виміряти у файлі, і його може відтворити будь-хто, хто має ті самі байти — SHA-256 опубліковано, а додаток — ні.\n\nТе, що було під решітками, — це не номери рахунків. Це був перелік скарг користувачів, поданих проти заявника, із зазначенням їхніх авторів: Steam логінів, які, оскільки логін рідко використовується лише на Steam, дозволяють ідентифікувати особу, що стоїть за ними — за підрахунками авторів, понад 60% користувачів, згаданих у документі, можна повністю ідентифікувати — разом із необробленим, неотредагованим текстом їхніх дописів. Цей текст містить побажання смерті та образи на адресу національності заявника. Деякі з цих осіб є неповнолітніми. Виробництво передало іменний список журналістів тій особі, про яку вони повідомили, саме такої шкоди і покликана запобігти стаття 15(4).\n\nПорядок символів у файлі має таке ж значення, як і його зміст. На цей запит спочатку було надано відповідь із вимогою надати додаткові докази особи, мотивуючи це тим, що псевдонім у електронній адресі заявника не містив його імені; під час затримки, що настала після цього, обліковий запис було назавжди заблоковано. У листі, яким нарешті були надані дані — більш ніж через шість тижнів після закінчення місячного терміну, передбаченого ст. 12(3) — одержувачу погрожували кримінальним переслідуванням і утримували решту його власних даних доти, доки він не пояснив активність свого облікового запису адвокату. Цей розкриття інформації також дає відповідь на два питання, на які Valve не відповідав публічно: надані записи показують, що зв’язування облікових записів сягає 2019 року, а також внутрішню телеметрію такої глибини, яку Valve ніколи не описував.\n\nСфера застосування цього розділу: У даному випадку розгляд обмежується механізмами редагування, виявленими у готовому файлі. Подальший аналіз авторами отриманих журналів відкладено до проведення незалежної експертизи, і на нього не посилаються в інших частинах цього досьє.\n\nДокази: лист адвоката від 1 жовтня 2025 року та його додаток у форматі PDF (SHA-256 зафіксовано в аудиторському файлі); Вимірювання PDF на рівні сторінки та методика ↗. Послідовність подій, пов’язаних із запитом, відмовою (сторінка 8) та описом оприлюднених записів, викладена в повному обсязі у звіті PhishDestroy, «Мій пес проти елітних юристів з питань GDPR», 17 серпня 2026 року ↗ архівувати 2026-08-21 ↗. Назви облікових записів та дані третіх сторін тут не наводяться; інформація, що прихована смугами, не відтворюється.\n\nНа сторінці 8 супровідного листа частина запиту відхиляється, при цьому письмово зазначається причина: Надати більш детальну інформацію неможливо з міркувань захисту персональних даних інших користувачів платформи Steam… — надати більш детальну відповідь неможливо, оскільки необхідно захистити персональні дані інших Steam користувачів. Додатк на 830 сторінок містився в тому самому пакеті. Зачорнені фрагменти не стосувалися номерів рахунків: це були скарги, подані проти заявника, із зазначенням імен їхніх авторів та доданими необробленими, нередагованими повідомленнями. Власник рахунку через свого адвоката звернувся до Valve із проханням надати його власну справу; те, що він зміг з неї витягти, стосувалося інших осіб. Ніщо в цьому додатку не залежить від того, хто намалював ці рамки. Він лише доводить, що захист Valve, на який посилалися як на підставу для відмови у наданні інформації, — це той самий захист, якого не дотрималися при наданні саме цих матеріалів, у тому самому конверті, того самого дня.\nДокументи щодо підтримки та юридичної кореспонденції\n\nДжерело: https://phishdestroy.io/steam_dossier/uk/index#exhibit-gallery-section\n\nДодаток D — Збір вихідних даних\nВибрані первинні документи\n\nШість записів з архіву — три записи в системах відстеження Valve на GitHub та три дописи на Reddit щодо спірних результатів надання підтримки. Кожне джерело залишається прикріпленим до заяви, збереженого тексту та питання, яке воно порушує.\n\n1 / 6 вибрані записи\nВиберіть вихідний запис\nGH-01 / GITHUBВідкрити у збереженій збірці\nАпаратні ключі, замовлені у 2016 році\n\nValveSoftware / steam-for-linux · № 4521 · 2016-06-27\n\nКористувач звернувся до Valve із проханням забезпечити підтримку апаратних ключів U2F як альтернативного другого фактора аутентифікації. Ця збережена заявка має мітки «Запит на функцію» та «Переглянуто», а її статус зазначено як «відкрита».\n\nЯ прошу додати підтримку USB-ключів U2F у Steam як альтернативу.\n\nВитяг із запису на GitHub ↗\nДокументально підтверджений запис\nЗастарілий запит на додатковий захід захисту облікового запису, опублікований у власній системі відстеження проблем Valve та позначений як «переглянутий».\nВимога щодо підзвітності\nОпублікуйте рішення щодо продукту, дату надання відповіді та заходи захисту, вжиті після розгляду.\nПрочитати збережений запис →Відкрити GitHub ↗\nУ досьє: Заходи безпеки облікового запису →Архів № 484 · збірка 2026-09-17\nGH-02 / GITHUBВідкрити у збереженій збірці\nЗвіти про збої без ефективної можливості відмови від отримання\n\nValveSoftware / steam-for-linux · № 6459 · 2019-08-18\n\nАвтор повідомлення описує проблему з клієнтом Steam від 12 серпня 2019 року на Ubuntu 16. Він зазначає, що відключення пункту призначення для завантаження даних у разі збою не збереглося після перезапуску, та наводить відповідні налаштування.\n\nЯкщо я вимкну параметр `ServerURL`, його значення перезаписується після кожного перезавантаження.\n\nВитяг із завдання на GitHub ↗ архів 2026-04-19 ↗\nДокументальний запис\nКонкретна скарга щодо порушення конфіденційності, що містить дату звернення клієнта, інформацію про операційну систему та витяг з налаштувань. Зареєстрована проблема залишається відкритою.\nВимога щодо підзвітності\nВкажіть, про яке розслідування йдеться, які збірки були зачеплені та яку зміну було внесено, щоб увімкнути можливість відмови.\nПрочитати збережений запис →Відкрити GitHub ↗архів 2026-04-19 ↗\nУ досьє: Запросити відповідні документи →Архів № 467 · збірка 2026-09-17\nGH-03 / GITHUBВідкрити у збереженій збірці\nПро зловживання авторизаційними квитками повідомлено на Valve\n\nValveSoftware / Source-1-Games · № 3857 · 2022-02-26\n\nАвтор стверджує, що адміністрація сервера зберігала Steam квитки автентифікації після того, як гравці відключилися, та використовувала оманливі списки серверів. У дописі Valve просять вирішити це питання.\n\nСтворюють враження, ніби їхні сервери переповнені.\n\nВитяг із запису на GitHub ↗\nДокументально підтверджений запис\nЗвіт про зловживання, поданий у трекері Valve 26 лютого 2022 року. Його збережений статус — «відкритий»; звіт містить посилання на скріншоти.\nВимога щодо підзвітності\nНадайте результати розслідування та звіт про вжиті заходи щодо усунення наслідків повідомленого випадку зловживання квитком автентифікації.\nПрочитати збережений запис →Відкрити GitHub ↗\nУ досьє: Обсяг набору даних →Архів № 768 · збірка 2026-09-17\nRD-01 / REDDITПрофіль автора\n44 спірні покупки на ринку\n\nr/DotA2 · ім’я автора не вказано · 2022-07-07\n\nАвтор повідомляє про 44 несанкціоновані покупки на Market 6 липня 2022 року та збитки у розмірі приблизно $500+. Він зазначає, що двофакторна аутентифікація була увімкнена, та описує повторювані шаблонні відповіді від служби підтримки.\n\nЦе вже другий запит, а я досі не отримав від Steam жодної відповіді, яка б не була автоматичним копіюванням-вставкою шаблону.\n\nУривок із допису на Reddit ↗ архів 2025-03-20 ↗\nДокументальне підтвердження\nХронологічний звіт про спірні покупки, що містить посилання на скріншоти транзакцій та відповідь служби підтримки. Суми та події наведені за даними автора.\nВимога щодо підзвітності\nЗвірте спірні покупки з журналами транзакцій та сеансів. Поясніть, на яких доказах ґрунтується рішення служби підтримки.\nПрочитати збережений запис →Відкрити Reddit ↗архів 2025-03-20 ↗\nУ досьє: Підтримка та забезпечення дотримання →Архів № 4,533 · збірка 2026-09-17\nRD-02 / REDDITПрофіль автора\nПостійна заборона та закриті апеляції\n\nr/ohnePixel · ім’я автора не вказано · 2024-12-09\n\nАвтор заперечує постійну блокування та зазначає, що служба підтримки посилалася на підозру щодо переведення облікового запису та повідомлення від спільноти. Він описує закриті звернення та плани щодо запиту своїх персональних даних.\n\nЯ пояснив свою ситуацію та попросив надати додаткову інформацію, але вони залишаються при своєму рішенні і закривають мої запити.\n\nУривок із допису на Reddit ↗\nДокументально підтверджений запис\nЗбережений звіт про звернення, що містить аргументи, які, на думку автора, підтверджують надану підтримку, а також посилання на чотири зображення. Дата публікації взята з експортованого списку обраних прихильників.\nВимога щодо підзвітності\nВизначте докази, що обґрунтовують постійну заборону, та процедуру перегляду, за допомогою якої можна оскаржити це рішення. Ухвала про закриття апеляції не містить обґрунтування рішення.\nПрочитати збережений запис →Відкрити Reddit ↗\nУ досьє: Запросити відповідні документи →Архів № 4,766 · збірка 2026-09-17\nRD-03 / REDDITПрофіль автора\nСкидання процесу відновлення та зафіксовані збитки у розмірі $10,000\n\nr/legaladvice · ім’я автора не розголошується · 2025-05-09\n\nАвтор стверджує, що служба підтримки скинула облікові дані та вимкнула засоби захисту облікового запису після того, як хтось інший надіслав запит на відновлення. Він повідомляє про втрату близько US$10,000 з неактивного облікового запису.\n\nSteam Служба підтримки скинула мій пароль і вимкнула всі засоби захисту мого облікового запису.\n\nУривок із допису на Reddit ↗\nДокументально підтверджений запис\nЗбережене твердження про те, що процес відновлення даних має пріоритет над заходами безпеки облікового запису. У збереженому дописі наведено те, що, за словами автора, йому повідомила служба підтримки.\nВимога щодо підзвітності\nВкажіть, хто санкціонував скидання, які докази права власності були прийняті, а також журнал доступу. Відновлення доступу до облікового запису є частиною заходів безпеки Valve.\nПрочитати збережений запис →Відкрити Reddit ↗\nУ досьє: Запросити відповідні документи →Архів № 4,592 · версія 2026-09-17\n\nШість вибраних записів. Описи на GitHub містять інформацію про збережену збірку. Публікації на Reddit зберігають акаунти авторів.\n\nЗавантажте шість записів ↓\n\nЗбірка з можливістю пошуку містить 16,319 унікальних записів: 393 записи на Trustpilot, 5,635 на Reddit, 2,395 на GitHub, 276 веб-записів та 7,620 записів у вікі. Кілька записів можуть стосуватися однієї й тієї ж події. Окремий основний експорт, що складається з 40,448 рядків, має інший обсяг даних.\n\nПошук у повному архіві ↗ · Створити маніфест ↗ · Обсяг набору даних та кількість записів →\n\nДодаток Е — Приклад з практики\nArchiSteamFarm та положення про автоматизацію\n\nІнструмент для фармінгу карток з відкритим кодом, у власному розділі «Часті запитання» якого зазначено, що він працює на мільйонах облікових записів, що суперечить пункту Угоди з абонентом (§ 4.C), який забороняє автоматизацію. Механізм роботи — що ферма повинна придбати у Valve, перш ніж зможе щось виробляти; чому кожен спосіб виведення коштів з картки порушує умови ліцензії; історія застосування санкцій та хто контролює економіку карток — викладено в повному обсязі в Додаток V ↗.\n\nУ § 4.C Угоди з абонентом № Steam зазначено:\n\n«Забороняється будь-яким чином використовувати скрипти, боти, макроси чи інші системи, що не керуються людиною («Автоматизація»), для взаємодії з Контентом та Послугами на Steam». — Steam Угода з абонентом, § 4.C (чинна редакція) ↗ архів 2026-09-18 ↗\n\nValve забезпечує виконання цього пункту. І робить це дуже добре. Розділ «Часті запитання» на сайті ArchiSteamFarm (ASF) — інструмент з відкритим кодом, який, згідно з його власною документацією, працює на понад кілька мільйонів Steam облікових записів з моменту першого випуску понад 11 років тому — відтворює три Steam повідомлення служби підтримки про постійне блокування користувачів, які керували мережами ботів. Valve виявили ці мережі, назвали їх і ліквідували. Тому головне питання полягає не в тому, чи здатний Valve виявляти автоматизацію у великих масштабах.\n\nОфіційний сайт проєкту ArchiSteamFarm Поширені запитання безпосередньо розглядає ризик введення заборони:\n\n«Це вкрай малоймовірно, зважаючи на те, що ASF використовується на понад кількох мільйонах Steam облікових записів з моменту його першого випуску, який відбувся понад 11 років тому, — але така можливість все ж існує, незалежно від фактичної ймовірності».\n\n\"Valve чітко визнає існування «Steam ледарів», як зазначено тут, тож, якщо мене запитати, я цілком впевнений, що якби вони не сприймали їх нормально, то вже вжили б якісь заходи, а не просто вказували на те, що вони можуть спричинити проблеми VAC. Ключовим словом тут є «ідлери» (наприклад, ASF), а не «ігрові ідлери».\"\n\n— ArchiSteamFarm Поширені запитання, JustArchiNET. Джерело: Вікі GitHub ↗ · перевірено дослівно 2026-09-22\n\nУ тому ж розділі «Часті запитання» на запитання «Чи когось за це заблокували?» дається така відповідь: Так, і наводить те, що Steam Support написав трьом із них:\n\n1,000+ боти · заборонено торгувати\n«Схоже, цей обліковий запис використовувався для управління мережею бот-акаунтів. Використання ботів є порушенням Угоди з абонентом Steam».\n\nПонад 170 ботів · назавжди заблоковано, Зимовий розпродаж 2017 року\n«Цей обліковий запис використовувався для незаконного збирання колекційних карток на Steam, а також для пов’язаної з цим діяльності, яка не обмежувалася лише комерційною діяльністю. Обліковий запис було назавжди заблоковано, і служба підтримки Steam не може надати додаткову допомогу з цього питання».\n\nПонад 120 ботів · назавжди заблоковано\n«Цей та інші акаунти використовувалися для перевантаження нашої мережевої інфраструктури, що є порушенням правил поведінки в Інтернеті Steam».\n\n— Steam Повідомлення служби підтримки, наведені в розділі «Чи когось за це заблокували?» у ArchiSteamFarm розділі «Поширені запитання». Джерело ↗ · перевірено дослівно 2026-09-22\n\nРозмістіть ці два записи поруч. Приватного користувача, який використовував 1,000 ботів для фармінгу, було виявлено, йому повідомили, що «використання ботів є порушенням Steam Угоди з абонентом», і його було назавжди заблоковано. Комерційні платформи, описані в цьому досьє, використовують автоматизовані Steam акаунти як основний напрямок своєї діяльності в набагато більших масштабах і здійснюють аутентифікацію через власний OpenID Valve під час кожного входу — при цьому щодо жодної з них не було опубліковано жодних даних про заходи щодо дотримання правил, вжиті окремими операторами. Ця умова діє. Питання в тому, на кого вона спрямована.\n\nASF тут ні в чому не звинувачується, а його тлумачення позиції Valve є власною думкою — автор чітко зазначає, що «ASF не уповноважений Valve». Цей інструмент тут використовується як вимірювальний прилад: він показує, що Valve виявляє бот-мережі, називає їх у своїх повідомленнях та назавжди блокує. Valve може закрити це питання одним реченням, опублікувавши інформацію про те, яку комерційну автоматизацію він схвалює, а також звіт за кожним оператором про те, що було зроблено щодо решти.\n\nЯк фарм карт впливає на дохід Valve\n\nТоргові картки, отримані в грі, продаються на ринку спільноти Steam, який стягує сукупну комісію в розмірі приблизно 15% з кожної угоди, укладеної на цьому ринку; акаунт повинен витратити $5.00 доларів США на Steam, перш ніж він зможе взагалі отримати картку; а для отримання карток необхідно володіти грою або здійснювати внутрішньоігрові покупки. У цьому розділі не наводиться загальна оцінка доходу — масштаб діяльності вказано лише відповідно до інформації, наведеної у розділі «Часті запитання» ASF. У цьому розділі також зазначено Valve відмінні риси \"Steam холостоходових коліс\" (фарм карт) з «ті, хто просто бавиться в ігри»; див. Часті запитання щодо АСФ ↗. Механізм дії викладено в повному обсязі в Додаток V — шкала та пастка комерційного використання.\n\nТемаArchiSteamFarm — автоматизований фарм карт\nЗазначений масштабМільйони облікових записів (згідно з розділом «Часті запитання» на сайті ASF — точна кількість активних облікових записів не підтверджена)\nПідраховано, а не наведено10,880,610 загальна кількість записів API у власній Steam групі ASF (5,360,499 без обмежень, як показано в Steam) — «мільйони» у розділі «Часті запитання» — це не вигадка, а фактична кількість. 88.97% не передбачають жодної Steam заборони будь-якого роду. Повний перелік заборон ↗\nІнформація, наведена у власній документації до інструменту\nASF автоматично входить в акаунти в режимі без графічного інтерфейсу та залишає ігри в режимі очікування для отримання карт, не запускаючи клієнт Steam (відповідно до документації проєкту).\nУ розділі «Часті запитання» наводиться аргумент, що Valve знає про «Steam ледарів» і що «якби вони не були з цим згодні, то вже б щось зробили».\nПротягом понад 11 років не повідомлялося про жодні цілеспрямовані заходи з контролю за дотриманням законодавства (згідно з розділом «Часті запитання»); у результаті продаж карток на «Community Market» приносить Steam сукупний комісійний дохід у розмірі приблизно 15%.\nУ розділі «Часті запитання» вказано рекомендовану граничну кількість — десять облікових записів на одного оператора — і посилання на Valve: «Ця рекомендація ґрунтується на внутрішніх Valve настановках, а також на наших власних пропозиціях». Компанія Valve не опублікувала жодних таких настанов.\nТехнічне обмеження, згідно з тим самим розділом «Часті запитання»: «Ви можете запускати до 100–200 ботів з однієї IP-адреси та одного екземпляра ASF».\nЧас гри, набраний штучним шляхом, фіксується Valve — «зазвичай дані оновлюються приблизно кожні 30 хвилин» — а в § 4.C «фальсифікація ігрових статистичних даних (наприклад, завищення кількості перемог чи поразок, XP, часу гри)» зазначена як заборонена дія.\nДжерела\nОфіційна вікі-сторінка з часто задаваними питаннями про JustArchi ASF ↗ ArchiSteamFarm репозиторій ↗ архівувати 2026-09-24 ↗\nПоложення щодо автоматизації є чітким; у розділі «Часті запитання» ASF вже протягом багатьох років зазначається, що цей інструмент використовується на мільйонах облікових записів; про жодні цілеспрямовані заходи щодо його заборони не повідомлялося. Розбіжність між правилом та його застосуванням є фактом; причина цього тут не встановлена.\nПовна експозиціяЕкономіка карток: процес, масштаби, ліцензія та хто її регулює ↗Що ферма повинна придбати у Valve, перш ніж зможе виготовити хоча б одну картку; два рядки § 4.C, які визначають фарм карт за його наслідками; чому кожен спосіб обміну карти на гроші порушує ліцензію Valve, тоді як Valve стягує плату на вході; історія заходів щодо забезпечення дотримання правил, включаючи хвилю VAC у червні 2025 року та ланцюгові блокування за спільним номером телефону; а також співробітник Valve та модератори спільноти, яких було виявлено під час управління послугами з обміну картками та списками заблокованих користувачів навколо Steam.Перепис заборонМи не запитували Valve, якої площі ця ферма. Ми її виміряли. ↗10,880,610 загальна кількість облікових записів (з обмеженнями та без них), зчитаних із власної групи Steam користувача ArchiSteamFarm, до якої програма автоматично приєднується за замовчуванням під час першого запуску, якщо користувач не зніме галочку з налаштування приєднання до групи (що охоплює як комерційні бот-ферми, так і звичайних гравців, які залишили налаштування за замовчуванням увімкненим). 88.97% не мають жодних заборон Steam; із тих 11%, які їх мають, 99.8% — це косметичні заборони від спільноти, які ніколи не зупиняють торгівлю. Після перехресної перевірки з SteamRep, 67.77% із перелічених шахраїв залишаються на свободі після скасування заборон античіт-системи. З розбивкою за датою реєстрації, географією та виживанням — реальні масштаби, виміряні, а не описані.\n\nAppendix F — Working ledger\n\nRules ledger: clauses against recorded platforms\n\nВиберіть правило; у реєстрі відображаються зареєстровані платформи, позначені цим правилом, із зазначенням їхнього основного домену, вказаного хосту автентифікації та збереженого результату фільтрації посилань. Заблокований веб-сайт, інший домен для входу: дотримуйтесь цього правила аж до кінцевої точки маршруту.\n\n175пов’язані записи\nвідповідно до цього правила\n174 основні домени0 Згадки про C&D\nВИРІЗКА З ПРАВИЛ / SSA § 2.G\nКомерційне використання та нарахування коштів на рахунок\n“…exploit the Content and Services or any of its parts for any commercial purpose, except as expressly permitted elsewhere in this Agreement (including any Subscription Terms or Rules of Use).”\nСЛІДКУЙТЕ ЗА РЕЗУЛЬТАТАМИ\nРеєстр платформ 175\nЦифри у масштабі є оцінками джерел\n\n175 з записів «175»\n\nСлужба / батьківська група\tГоловний домен / реєстр\tСпостережуваний домен автентифікації / вік\tШкала / зареєстрована реакція\n\nCasino\n\tcsgoempire.com\n11.3 yearsRegistered 2015-06-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgoempirelogin4.com\n6.2 yearsRegistered 2020-07-20\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustreaper.com\n23.2 yearsRegistered 2003-06-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustreaper.com\n23.2 yearsRegistered 2003-06-24\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustly.com\n12.4 yearsRegistered 2014-05-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustly.com\n12.4 yearsRegistered 2014-05-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette Casino\n\tcsgofast.com\n11.5 yearsRegistered 2015-03-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsteam-login.authtofast.com\n83 daysRegistered 2026-06-30\nRDAP ↗ · authtofast.com (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tduelbits.com\n6.6 yearsRegistered 2020-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nswitchflips.com\n6.4 yearsRegistered 2020-04-21\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opener\n\tfarmskins.com\n10.5 yearsRegistered 2016-03-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsteam.kobal.cc\n9.7 yearsRegistered 2017-01-07\nRDAP ↗ · kobal.cc (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgoluck.com\n9.3 yearsRegistered 2017-05-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgoluck.com\n9.3 yearsRegistered 2017-05-18\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tinsane.gg\n7.5 yearsRegistered 2019-04-02\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.insane.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcs2skin.com\n3.5 yearsRegistered 2023-03-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncs2skin.com\n3.5 yearsRegistered 2023-03-06\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tjuice.gg\n7.9 yearsRegistered 2018-10-19\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nletmeinjuice.com\n2.4 yearsRegistered 2024-04-15\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tggdrop.com\n8.6 yearsRegistered 2018-02-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nggauth.com\n3.4 yearsRegistered 2023-05-03\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Casino\n\thowl.gg\n9.5 yearsRegistered 2017-03-16\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhowl.uno\n41 daysRegistered 2026-08-11\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tchicken.gg\n5.7 yearsRegistered 2021-01-11\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nchicken.gg\n5.7 yearsRegistered 2021-01-11\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgocasino.gg\n2.6 yearsRegistered 2024-02-17\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.csgocasino.gg\n2.6 yearsRegistered 2024-02-17\nWHOISFREAKS ↗ · csgocasino.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Casino\n\thunt.gg\n6.9 yearsRegistered 2019-11-04\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.hunt.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Battles\n\tcsbattle.com\n9.8 yearsRegistered 2016-12-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsbattle.com\n9.8 yearsRegistered 2016-12-10\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskinrave.gg\n3.1 yearsRegistered 2023-08-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinrave.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsdouble.gg\n261 daysRegistered 2026-01-03\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsdouble.gg\n261 daysRegistered 2026-01-03\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustchance.com\n8.0 yearsRegistered 2018-10-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhgfuihd.com\n7.6 yearsRegistered 2019-01-27\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Automation\n\tcobaltlab.tech\n3.5 yearsRegistered 2023-03-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncobaltauth.com\n1.7 yearsRegistered 2025-01-07\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\traided.gg\n171 daysRegistered 2026-04-03\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.raided.gg\n171 daysRegistered 2026-04-03\nIP2WHOIS ↗ · raided.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustneo.gg\n1.3 yearsRegistered 2025-06-20\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustneo.gg\n1.3 yearsRegistered 2025-06-20\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tsplits.gg\n3.7 yearsRegistered 2023-01-23\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsplits.gg\n3.7 yearsRegistered 2023-01-23\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Upgrader\n\tupgrader.pro\n1.2 yearsRegistered 2025-07-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nupgauth.space\n38 daysRegistered 2026-08-14\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskin.fans\n8.2 yearsRegistered 2018-07-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skinfans.com\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\thotpizza.one\n1.8 yearsRegistered 2024-12-07\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhotpizza.one\n1.8 yearsRegistered 2024-12-07\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tg4skins.com\n10.1 yearsRegistered 2016-08-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.g4s.to\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2royal.com\n4.1 yearsRegistered 2022-08-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ntf2auth.com\n5.2 yearsRegistered 2021-07-27\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2hunt.com\n8.7 yearsRegistered 2018-01-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrstspcl.com\n6.1 yearsRegistered 2020-08-08\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2.bet/coinflip\n8.4 yearsRegistered 2018-05-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ntf2.bet\n8.4 yearsRegistered 2018-05-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\topenstars.gg\n131 daysRegistered 2026-05-13\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nopenstars.gg\n131 daysRegistered 2026-05-13\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tskins.com\n25.1 yearsRegistered 2001-08-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skins.com\n25.1 yearsRegistered 2001-08-08\nRDAP ↗ · skins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\twhite.market\n9.6 yearsRegistered 2017-03-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwhite.market\n9.6 yearsRegistered 2017-03-01\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tmoon.market\n7.6 yearsRegistered 2019-02-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmoon.market\n7.6 yearsRegistered 2019-02-27\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tcsfloat.com\n5.2 yearsRegistered 2021-07-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgofloat.com\n11.0 yearsRegistered 2015-09-29\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tskin.land\n4.7 yearsRegistered 2022-01-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skin.land\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\thaloskins.com\n2.8 yearsRegistered 2023-12-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhaloskins.com\n2.8 yearsRegistered 2023-12-10\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCorporate Market\n\tbuff.163.com\n29.0 yearsRegistered 1997-09-15\nRDAP ↗ · 163.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\nbuff.163.com\n29.0 yearsRegistered 1997-09-15\nRDAP ↗ · 163.com (parent)\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\tmarket.csgo.com\n26.6 yearsRegistered 2000-02-07\nRDAP ↗ · csgo.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\ndota2.net\n14.9 yearsRegistered 2011-10-29\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRegulated Market\n\tskinport.com\n8.0 yearsRegistered 2018-09-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinport.app\n6.3 yearsRegistered 2020-06-20\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMarketplace/Swap\n\tskinflow.gg\n3.8 yearsRegistered 2022-11-26\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinflow.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tskin.place\n6.0 yearsRegistered 2020-09-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skin.place\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tskinsmonkey.com\n5.7 yearsRegistered 2021-01-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinsmonkey.com\n5.7 yearsRegistered 2021-01-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCorporate Market\n\tskinbaron.de\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinbaron.com\n10.7 yearsRegistered 2015-12-22\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Market\n\trust.tm\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\ndota2.net\n14.9 yearsRegistered 2011-10-29\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tpirateswap.com\n6.0 yearsRegistered 2020-09-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nlogin.pirateswap.com\n6.0 yearsRegistered 2020-09-22\nRDAP ↗ · pirateswap.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Marketplace\n\tmannco.store\n8.6 yearsRegistered 2018-03-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmannco.store\n8.6 yearsRegistered 2018-03-02\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tskinswap.com\n9.9 yearsRegistered 2016-11-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinswap.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\texeskins.com\n2.1 yearsRegistered 2024-08-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nexeskins.com\n2.1 yearsRegistered 2024-08-14\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tbalticskins.com\n153 daysRegistered 2026-04-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nbalticskins.com\n153 daysRegistered 2026-04-21\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tcs.trade\n8.9 yearsRegistered 2017-11-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncs.trade\n8.9 yearsRegistered 2017-11-14\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\trapidskins.com\n4.5 yearsRegistered 2022-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.rapidskins.com\n4.5 yearsRegistered 2022-03-11\nRDAP ↗ · rapidskins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\ttradeit.gg\n9.1 yearsRegistered 2017-08-21\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nconnect-tradeit.com\n4.6 yearsRegistered 2022-02-23\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\t49skins.com\n3.4 yearsRegistered 2023-04-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.49skins.com\n3.4 yearsRegistered 2023-04-19\nRDAP ↗ · 49skins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tskinvault.gg\n3.4 yearsRegistered 2023-05-06\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinvault.gg\n3.4 yearsRegistered 2023-05-06\nIP2WHOIS ↗ · skinvault.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Trading\n\taim.market\n3.3 yearsRegistered 2023-05-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\naim.market\n3.3 yearsRegistered 2023-05-22\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Sell Portal\n\tskinout.gg\n5.6 yearsRegistered 2021-02-27\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skinout.gg\n5.6 yearsRegistered 2021-02-27\nIP2WHOIS ↗ · skinout.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Trading\n\tntskins.com\n230 daysRegistered 2026-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nntskins.com\n230 daysRegistered 2026-02-03\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Portal\n\tgamerpay.gg\n6.0 yearsRegistered 2020-10-02\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ngamerpay.gg\n6.0 yearsRegistered 2020-10-02\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Scrap Swap\n\tscrap.tf\n14.0 yearsRegistered 2012-09-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nscrap.tf\n14.0 yearsRegistered 2012-09-03\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Cashout\n\tmarketplace.tf\n14.0 yearsRegistered 2012-09-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmarketplace.tf\n14.0 yearsRegistered 2012-09-19\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Cashout\n\tskins.cash\n10.5 yearsRegistered 2016-03-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinscash.live\n6.8 yearsRegistered 2019-12-05\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgo.net\n14.2 yearsRegistered 2012-07-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncn2.easylot.net\n10.0 yearsRegistered 2016-09-03\nRDAP ↗ · easylot.net (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCommunity Hub\n\tcybershoke.net\n6.8 yearsRegistered 2019-11-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.cybershoke.net\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMatchmaker Hub\n\tfastcup.net\n14.6 yearsRegistered 2012-02-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.fastcup.net\n14.6 yearsRegistered 2012-02-16\nRDAP ↗ · fastcup.net (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Analytics\n\tleetify.com\n7.6 yearsRegistered 2019-03-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nleetify.com\n7.6 yearsRegistered 2019-03-01\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Analytics\n\tscope.gg\n7.8 yearsRegistered 2018-12-10\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nscope.gg\n7.8 yearsRegistered 2018-12-10\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tools\n\ttradeupspy.com\n6.5 yearsRegistered 2020-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.tradeupspy.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMarketplace\n\tcs.deals\n9.8 yearsRegistered 2016-12-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.cs.deals\n9.8 yearsRegistered 2016-12-03\nRDAP ↗ · cs.deals (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Price DB\n\tpricempire.com\n6.6 yearsRegistered 2020-01-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\npricempire.com\n6.6 yearsRegistered 2020-01-30\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Blackmarket\n\tFSB Market\n7.2 yearsRegistered 2019-07-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nFSB Market\n7.2 yearsRegistered 2019-07-27\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nReady-Account Hub\n\tz2u.com\n26.9 yearsRegistered 1999-11-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwww.z2u.com\n26.9 yearsRegistered 1999-11-10\nRDAP ↗ · z2u.com (parent)\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Gambling\n\tcsgoroll.com\n11.6 yearsRegistered 2015-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwww.csgoroll.com\nRegistry date unavailableRegistry date unavailable\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\trollbit.com\n11.9 yearsRegistered 2014-11-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrbsnin.com\n3 daysRegistered 2026-09-18\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nLicenced Casino\n\t500.casino\n5.9 yearsRegistered 2020-11-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette/Slots\n\tcsgobig.com\n11.4 yearsRegistered 2015-04-12\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcasedrop.com\n14.8 yearsRegistered 2011-12-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\tbanditcamp.com\n12.2 yearsRegistered 2014-06-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tskinbox.com\n18.8 yearsRegistered 2007-12-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\ttastydrop.com\n6.1 yearsRegistered 2020-08-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette Casino\n\tcsgopolygon.gg\n6.5 yearsRegistered 2020-03-28\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tmagicdrop.ru\n10.3 yearsRegistered 2016-05-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nDice Casino\n\tcsdice.com\n3.8 yearsRegistered 2022-11-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUpgrader Casino\n\tskinodds.com\n1.2 yearsRegistered 2025-06-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgowin.com\n12.0 yearsRegistered 2014-09-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrash Casino\n\tcsgorun.net\n7.3 yearsRegistered 2019-06-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\topenskins.com\n3.6 yearsRegistered 2023-02-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Gambling\n\trustbet.com\n7.6 yearsRegistered 2019-02-07\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgomagic.com\n9.4 yearsRegistered 2017-05-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUpgrader/Contract\n\tcsgobounty.com\n11.5 yearsRegistered 2015-03-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tezskins.com\n27.5 yearsRegistered 1999-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\trustcases.com\n7.2 yearsRegistered 2019-06-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgoreaper.com\n11.1 yearsRegistered 2015-08-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgocases.com\n12.3 yearsRegistered 2014-06-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Upgrader\n\tcsgo-skins.com\n11.2 yearsRegistered 2015-07-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgonet.com\n8.8 yearsRegistered 2017-12-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\twtfskins.com\n9.0 yearsRegistered 2017-10-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Casino\n\tflamecases.com\n10.0 yearsRegistered 2016-09-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tgamedom.com\n11.7 yearsRegistered 2015-01-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Battles\n\tskin.club\n9.0 yearsRegistered 2017-09-04\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsc-auth.net\n7.5 yearsRegistered 2019-04-02\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tdaddyskins.com\n9.9 yearsRegistered 2016-10-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Gambling\n\trustix.gg\n1.7 yearsRegistered 2025-01-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Upgrade\n\tskins.club\n4.2 yearsRegistered 2022-07-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgohouse.org\n146 daysRegistered 2026-04-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskinrave.net\n216 daysRegistered 2026-02-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tbloodycase.gg\n19 daysRegistered 2026-09-02\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nClicker/Upgrade\n\tcsgoclicker.com\n8.3 yearsRegistered 2018-05-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustbet.gg\n4.0 yearsRegistered 2022-09-30\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcs-drop.com\n262 daysRegistered 2026-01-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\thellstore.net\n11.7 yearsRegistered 2015-01-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustloot.com\n354 daysRegistered 2025-10-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgo-case.com\n10.3 yearsRegistered 2016-05-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgogem.com\n9.9 yearsRegistered 2016-10-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\trainbet.com\n8.8 yearsRegistered 2017-11-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nservices.rainbet.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustclash.com\n5.4 yearsRegistered 2021-05-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrash Casino\n\t12cs.fail\n181 daysRegistered 2026-03-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\twww.tf2easy.com\n6.3 yearsRegistered 2020-06-02\nRDAP ↗ · tf2easy.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2blaze.com\n7.6 yearsRegistered 2019-01-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tshuffle.com\n30.1 yearsRegistered 1996-07-31\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tbuff.market\n5.9 yearsRegistered 2020-10-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tavan.market\n8.3 yearsRegistered 2018-05-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Engine\n\tcs.money\n11.0 yearsRegistered 2015-09-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.dota.trade\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tuuskins.com\n2.6 yearsRegistered 2024-01-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Market\n\tyoupin898.com\n6.1 yearsRegistered 2020-08-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tc5game.com\n10.5 yearsRegistered 2016-03-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\twaxpeer.com\n7.3 yearsRegistered 2019-05-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwaxpeer.com\n7.3 yearsRegistered 2019-05-20\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBot Trading\n\tcs.money\n11.0 yearsRegistered 2015-09-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.dota.trade\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUS Marketplace\n\tdmarket.com\n30.2 yearsRegistered 1996-07-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nOfficial Market\n\tsteamcommunity.com/market\n20.3 yearsRegistered 2006-05-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNot an external login site2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Platform\n\tlootfarm.com\n11.9 yearsRegistered 2014-10-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Market\n\trustskins.com\n7.6 yearsRegistered 2019-01-31\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tkrakatoa.com\n26.4 yearsRegistered 2000-05-15\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\tshadowpay.com\n10.1 yearsRegistered 2016-08-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nChinese Powerhouse\n\tigxe.cn\n15.0 yearsRegistered 2011-09-06\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAutomated Swap\n\tswap.gg\n9.6 yearsRegistered 2017-01-29\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCash-out Portal\n\tbitskins.com\n11.2 yearsRegistered 2015-07-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Automation\n\ttf2mart.com\n1.1 yearsRegistered 2025-08-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Auctions\n\tskinbid.com\n10.2 yearsRegistered 2016-06-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Rental\n\tlootbear.com\n8.7 yearsRegistered 2018-01-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Valuation\n\tbackpack.tf\n14.4 yearsRegistered 2012-05-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Botnet\n\tstntrading.eu\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Cashout\n\tskinwallet.com\n18.0 yearsRegistered 2008-09-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nDota 2 Market\n\tdota2market.com\n12.2 yearsRegistered 2014-07-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nServer Network\n\txplay.gg\n5.3 yearsRegistered 2021-06-13\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMatchmaking Portal\n\tesportal.com\n26.8 yearsRegistered 1999-12-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nLATAM Hub\n\tgamersclub.com.br\n11.2 yearsRegistered 2015-06-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tools\n\tepidemic.gg\n4.9 yearsRegistered 2021-11-03\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tcs2stash.com\n3.5 yearsRegistered 2023-03-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tcsgoskins.gg\n6.8 yearsRegistered 2019-12-21\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tsteamanalyst.com\n12.6 yearsRegistered 2014-02-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Exchange\n\tsteamcardexchange.net\n13.3 yearsRegistered 2013-05-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tracker\n\tdotabuff.com\n14.2 yearsRegistered 2012-06-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tracker\n\ttracker.gg\n8.9 yearsRegistered 2017-10-12\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Exchange\n\tfunpay.com\n17.0 yearsRegistered 2009-09-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nGrey Market\n\tplayerauctions.com\n26.3 yearsRegistered 2000-06-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Portal\n\teldorado.gg\n8.0 yearsRegistered 2018-09-12\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Key Market\n\tg2a.com\n24.8 yearsRegistered 2001-12-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Key Market\n\tkinguin.net\n16.8 yearsRegistered 2009-12-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nVirtual Services\n\tg2g.com\n31.1 yearsRegistered 1995-08-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Broker\n\tplayerup.com\n19.3 yearsRegistered 2007-05-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfhub.net\n2.7 yearsRegistered 2023-12-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfaccounts.com\n5.3 yearsRegistered 2021-05-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Shop\n\tbuycsgorank.com\n6.2 yearsRegistered 2020-07-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tcsgosmurfkings.com\n9.3 yearsRegistered 2017-06-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfstore.co\n8.6 yearsRegistered 2018-03-03\nWHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlvlup.com\n9.9 yearsRegistered 2016-11-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlevels.com\n10.6 yearsRegistered 2016-02-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tlevelsteam.com\n79 daysRegistered 2026-07-04\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlevelu.com\n6.0 yearsRegistered 2020-09-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\teloking.com\n12.2 yearsRegistered 2014-07-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\tboosteria.org\n11.9 yearsRegistered 2014-10-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tovergear.com\n14.4 yearsRegistered 2012-04-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tblazingboost.com\n14.2 yearsRegistered 2012-06-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\tdota2boost.com\n2.9 yearsRegistered 2023-10-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tbuyboost.com\n22.4 yearsRegistered 2004-04-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\nАргументація слідстваВибране правило / аналіз та коментар+\nТягар доказування\n\nУ ході розслідування розглядається розбіжність між обмеженнями щодо комерційного використання та послугами, зазначеними в цьому документі. Слід класифікувати кожен вид діяльності та перевірити наявність явного дозволу, перш ніж визнати це порушенням умов договору. Комісійні збори Community Market не поширюються на всі види зовнішньої торгівлі.\n\nЩо таке запис із тегами, а що — ні\n\nЗапис позначається, коли в досьє міститься датоване спостереження, яке, судячи з його змісту, підпадає під дію відповідного пункту. Позначка не є офіційно визнаним порушенням, і щодо жодної з перелічених тут платформ у записі не наведено прямого дозволу Valve. Якщо платформа має дозвіл, публікація цієї інформації вирішує питання щодо цього запису.\n\nДжерела та методологіяОцінки, визначення та сфера застосування+\n\nНаведені вище показники стосуються вибраного правила. Типи записів об’єднують кожну платформу в одну групу; повні теги відображаються у деталях платформи. Пошук і фільтри застосовуються в межах цього правила. Дати реєстрації взяті зі збереженого знімка RDAP / WHOIS. Для субдоменів використовується дата створення батьківського домену. Сам по собі вік не свідчить про безперервну роботу або маршрут автентифікації. Поточні імена хостів автентифікації взяті зі збережених запитів OpenID із міткою часу UTC; при перевірці невирішених запитів не використовуються старі мітки. Спостерігач зупиняється перед входом на Steam і не перевіряє стан фільтра посилань Steam. Завантажити спостереження за маршрутом ↗ Завантажити результати перевірки реєстру ↗\n\nОзнайомтеся з архівом вихідного коду ↗\nДодаток G — Від шаблону відмови до відповідного запису\nПосібник з DSAR: запит на надання доказів\n\nСкористайтеся статтею 15 Загального регламенту про захист даних (GDPR), щоб отримати доступ до персональних даних, пов’язаних зі створенням API-ключа, відновленням облікового запису та доступом до служби підтримки. Збережений запис дозволяє перевірити, хто ініціював дію та на що спиралася платформа.\n\n01\nЗбережіть свою хронологію.\n\nЗбережіть повідомлення щодо облікового запису, квитки, ідентифікатори транзакцій та дати у форматі UTC. Захистіть обліковий запис та ознайомтеся з варіантами відновлення, що застосовуються до гри та транзакції.\n\nSteam Інформація про заходи торговельного захисту ↗\n02\nЗапитайте свої збережені дані.\n\nЗапитайте про часові мітки, IP-адреси джерел, ключові події життєвого циклу, підтвердження безпеки та дії з відновлення, пов’язані з обліковим записом. Вкажіть події, пов’язані з доступом служби підтримки, та одержувачів, якщо ці дані стосуються вас.\n\n03\nЗберігайте квитанцію про доставку.\n\nСкористайтеся каналом зв’язку з Valve щодо питань конфіденційності. Зазвичай відповідь надається протягом одного місяця; у разі необхідності продовження терміну ще на два місяці про це слід повідомити протягом першого місяця.\n\nValve шлях зв’язку щодо питань конфіденційності ↗ архів 2026-09-21 ↗\n04\nПорівняйте відповіді.\n\nЗвірте журнали з вашою хронологією подій. З’ясуйте причини пропусків, а потім, якщо це необхідно, скористайтеся процедурою подання скарги через керівництво. Збережіть відповідь у тому вигляді, в якому її отримали.\n\nСфера застосування / Стаття 15\n\nДоступ поширюється на збережені персональні дані, включаючи дані в журналах. Він не гарантує доступ до всіх внутрішніх документів, відтворених записів або даних про інших осіб без редагування. Попросіть надати зрозумілу копію та обґрунтування будь-яких обмежень.\n\nРекомендації Європейського комітету з захисту даних (EDPB) щодо доступу, §§ 2, 4–6 ↗ · Статті 12, 15, 77 Загального регламенту про захист даних (GDPR) ↗ архів 2026-09-20 ↗\n\nЗапит суб’єкта даних щодо доступу до данихGDPR / Стаття 15\nБезпека облікового запису та записи про доступ\n\nПеред відправкою замініть поля, взяті в дужки.\n\nTo: Valve Privacy Team\nSubject: Article 15 GDPR request — account security records\n\nAccount / SteamID: [YOUR ACCOUNT IDENTIFIER]\nRelevant period (UTC): [START] to [END]\nRelated support tickets: [TICKET REFERENCES]\n\nI request a copy of the personal data concerning me that you retain for this period, including:\n\n1. API-key registration, confirmation, use and revocation events, with available timestamps, source IP addresses, registered domains, device or user-agent information and non-secret key identifiers.\n\n2. Recorded account-recovery actions, password/email/phone changes, Steam Guard removals or resets, confirmation events and the account-related evidence relied on to authorize those actions.\n\n3. Personal data in support-access and administrative-action logs concerning my account, including available dates, purposes, actions and the support entity involved, subject to applicable rights of others.\n\n4. Account-related records used to determine any sanction, and available records of my complaints, reviews and responses.\n\nPlease also provide the applicable processing purposes, categories, recipients, retention periods or criteria, and available information about sources where data were not obtained from me.\n\nWhere processing relies on my consent, please provide the retained record of the consent relied upon and the wording presented at that time.\n\nPlease provide an intelligible electronic copy with time zones and field definitions. Please do not include active credentials or secret tokens. If any requested data are not held, please say so. For any withheld data, please identify the scope and legal basis of the restriction and provide the remainder.\n\nPlease acknowledge receipt and respond within the applicable Article 12 period, explaining any necessary extension. I also ask you to preserve relevant existing records while this request is handled.\n\nName: [YOUR NAME]\nDate: [DATE]\nЩо можна реалізувати за допомогою IP-адреси центру обробки даних\nРозбіжність є підставою для проведення розслідування.\n\nЗапит на отримання API-ключа, що надходить із мережі центру обробки даних, як у прикладі з хостинг-провайдером, наведеному в цьому розслідуванні, може мати значення при порівнянні з записами про вхід у систему, підтвердженнями та хронологією дій користувача. Сама лише IP-адреса не дозволяє ідентифікувати суб’єкта або автоматично подолати всі засоби захисту. Докази того, що ворожий суб’єкт надав зафіксовану згоду, можуть поставити під сумнів обґрунтованість покладання на цю згоду; інші правові підстави та питання відповідальності вимагають окремого аналізу.\n\nПереглянути збережену скаргу щодо заборони та GDPR →\nДодаток H — Аналіз архіву Wayback Machine · опубліковані статистичні дані щодо підтримки\nОбсяг підтримки. Опубліковані показники часу реагування.\nКонтекст та обмеження джерел\n\nValve щодня публікує статистику підтримки за адресою store.steampowered.com/stats/support. В архівах Wayback Machine збережені історичні знімки цієї сторінки за період з 2018 по 2026 рік. Співвідношення обсягу роботи до кількості співробітників, яке випливає з цих даних, не відповідає рівню ручної перевірки кожного запиту з опублікованими показниками часу відповіді.\n\nПорівняйте архівні показники підтримки Valve у збережених знімках. У методології пояснюється, що саме ці показники дозволяють виміряти, а що — ні.\n\nОбсяг у порівнянні з опублікованим часом реагування (2018 → 2026)\nДві черги біля одного пункту обслуговування — про це йдеться у 21 архівних знімках екрана.\n\nValve оприлюднює дані щодо кількості звернень до служби підтримки в режимі реального часу на store.steampowered.com/stats/support. Кожен пункт, наведений нижче, — це саме нижня межа Valve, яка була надрукована на цій сторінці в день, коли «Інтернет-архів» зробив її знімок, — а не наша оцінка. Обидва ряди даних представляють одну й ту саму величину в одних і тих самих одиницях виміру, тому вони розміщені на одній осі й їх можна порівнювати безпосередньо між собою.\n\nЗапити на повернення коштів — у Valve є грошіБезпека та відновлення облікового запису — обліковий запис, який ви втратили\n0 h\n2 h\n4 h\n6 h\n8 h\n10 h\nno captures · 38 months\n2019\n2020\n2021\n2022\n2023\n2024\n2025\n2026\n8 h 44 m\naccount recovery\n52 m\nrefunds\n15 m — one capture only\n49–55 хвНижня межа рефунду в кожному періоді з лютого 2018 року по серпень 2026 року. Протягом восьми з половиною років вона змінюється менше ніж на шість хвилин, тоді як щоденний обсяг рефунду змінюється в дев’ять разів.\n2,4 год → 8,7 годНижня межа часу відновлення облікового запису у всіх знімках до грудня 2022 року, за винятком одного, становить близько 2,4 години. У трьох знімках за 2026 рік Valve показує значення 10,9 год, 5,8 год та 8,7 год.\n×2,8 → ×13Наскільки повільніше відбувається відшкодування, ніж повернення коштів, згідно з опублікованими даними самого Valve. Протягом п’яти років ситуація залишається стабільною, а потім розрив збільшується — черга, яка стала повільнішою, — це та, в якій збитків зазнає користувач, а не Valve.\n\nДжерело: 21 знімок веб-сторінки, зроблений за допомогою Wayback Machine, store.steampowered.com/stats/support, від 2018-02-03 до 2026-08-10; витяг у VALVE_EVIDENCE_PACK/databases/steam_support_stats_history.json. Зверніть увагу на межі, позначені цифрами: на графіку зображено нижче межа діапазону Valve випадків. Опублікована верхня межа є гіршою за обома показниками — час повернення коштів становив від 1,5 години до 1,5 дня, а час відновлення — від 7,0 годин до 3,6 дня. Два знімки були заархівовані в локалізованих версіях тієї самої Valve сторінки — 2018-11-03 чеською, 2020-03-25 французькою — і позначені в таблиці як (cs) та (fr); їхні дані наводяться тут із перекладеними назвами одиниць виміру та цифрами, як вони були опубліковані, а дослівні рядки джерела зберігаються у файлі витягу. У кожному знімку опубліковано час відгуку для обох черг, і жодна точка на жодній з ліній не є інтерпольованою. Єдине значення часу відновлення за 15 хвилин — 2020-10-21 — позначено на графіку та залишено: воно з’являється лише в одному знімку, і жоден інший знімок не знаходиться в межах одного порядку величини від нього. Між 2022-12-08 та 2026-02-01 немає жодного запису; ця 38-місячна прогалина у записі зафарбована, і через неї нічого не намальовано. Ці показники описують опубліковані часи реагування. Вони не показують, що відбувається всередині квитка, а Valve не опублікувала даних про чисельність персоналу, з якими можна було б їх порівняти.\n\nВідкривати кожну зняту фотографію у вигляді таблиці\nКожен архівний знімок, у тому вигляді, в якому він був опублікований\nЗнімок\tПовернення коштів / день\tВідповідь щодо повернення коштів\tВідновлення / день\tЗаходи з відновлення\n2018-02-03\t98,788\tвід 50,12 хвилин до 1,52 години\t25,662\tвід 2,51 години до 1,80 дня\n2018-05-07\t60,494\tвід 53,83 хвилин до 1,47 дня\t24,226\tвід 2,45 годин до 2,22 днів\n2018-08-02\t69,084\tвід 50,27 хвилин до 1,59 години\t28,953\tвід 2,44 години до 22,17 години\n2018-11-03 (cs)\t63,410\tвід 49,28 хвилин до 1,54 години\t33,910\tвід 2,42 години до 1,31 дня\n2019-02-01\t76,305\tвід 50,13 хвилин до 1,52 години\t35,164\tвід 2,44 години до 2,04 днів\n2019-05-18\t78,951\tвід 51,03 хвилини до 3,12 годин\t27,514\tвід 2,46 години до 20,39 години\n2019-09-07\t78,941\tвід 50,65 хвилин до 1,66 години\t28,812\tвід 2,42 години до 13,59 годин\n2019-12-13\t69,589\tвід 50,77 хвилин до 1,55 години\t25,322\tвід 2,45 години до 1,13 дня\n2020-03-25 (fr)\t139,278\tвід 49,45 хвилин до 1,53 години\t32,302\tвід 2,48 години до 3,62 днів\n2020-06-26\t278,504\tвід 48,98 хвилин до 2,29 годин\t20,343\tвід 2,39 години до 6,99 години\n2020-10-21\t107,633\tвід 50,80 хвилин до 1,54 години\t20,688\tвід 15,33 хвилин до 8,62 годин\n2021-03-20\t158,956\tвід 50,80 хвилин до 1,64 години\t25,760\tвід 2,34 години до 11,62 години\n2021-06-26\t547,907\tвід 51,93 хвилини до 6,73 годин\t29,728\tвід 2,40 годин до 15,63 годин\n2021-10-10\t170,103\tвід 51,88 хвилин до 3,25 годин\t23,989\tвід 2,39 години до 13,05 години\n2022-01-31\t354,386\tвід 53,65 хвилин до 8,09 годин\t24,391\tвід 2,42 години до 15,29 годин\n2022-05-09\t172,555\tвід 51,83 хвилини до 1,65 години\t23,289\tвід 2,41 години до 16,90 годин\n2022-09-05\t153,453\tвід 53,67 хвилин до 4,15 годин\t23,594\tвід 2,45 години до 1,22 дня\n2022-12-08\t181,075\tвід 54,83 хвилини до 6,67 години\t27,111\tвід 2,46 години до 18,89 години\n2026-02-01\t317,762\tвід 50,30 хвилин до 1,52 години\t47,197\tз 10:91 до 21:30\n2026-05-09\t246,776\tвід 50,12 хвилин до 1,52 години\t35,264\tвід 5,81 години до 15,60 годин\n2026-08-10\t373,244\tвід 52,05 хвилин до 2,07 годин\t45,319\tвід 8,73 години до 16,52 години\nКЛЮЧОВЕ СПОСТЕРЕЖЕННЯ:\nПо всій 21 знімок з Wayback у діапазоні від 2018-02-03 до 2026-08-10 щоденні заявки на відшкодування коливалися від 60,494 (травень 2018 р.) до 547,907 (червень 2021 р.) — а Спред 9,1×. Показник за 2026 рік становить 373,244 (+278% порівняно з даними за лютий 2018 року).\nПротягом тих самих дев’яти років опублікована нижня межа часу реагування на запит про відшкодування ніколи не виходила за межі 49–55 хвилин діапазон: загальний рух тривалістю менше шести хвилин, тоді як навантаження, що його зумовило, змінилося в дев’ять разів.\nЯкщо людина буде читати кожен квиток хоча б 5 секунд, то обробка 373,244 квитків на день (наразі) займе 22 агенти, які працюють цілодобово без вихідних лише для того, щоб їх відкривати й закривати; у піковий період (547,907, червень 2021 року) цей показник зростає до 32.\nЯкби опублікований час відповіді відображав час обробки кожного запиту (~52 хв/запит), то необхідна кількість персоналу, що працює одночасно, становила б близько 13,500 агентів при поточній чисельності та ~20,000 у піковий період. Даних щодо чисельності персоналу, що забезпечує підтримку Valve, знайдено не було; у даному випадку ці показники не враховуються.\nВисновок: співвідношення обсягу до чисельності персоналу не узгоджується з ручною перевіркою кожного запиту за опублікованими показниками часу реагування. Наведені цифри відповідають переважно автоматизованому першому етапу обробки; інформація про те, яка частка запитів проходить ручну перевірку, не оприлюднена.\nЧому це важливо для дотримання вимог GDPR\n\nСтаття 22 GDPR забороняє виключно автоматизоване прийняття індивідуальних рішень, що має істотні правові наслідки, без надання права на перевірку людиною за запитом. Якщо рішення служби підтримки (закриття звернень, дії з обліковими записами, відмова у задоволенні запитів щодо даних) приймаються виключно за допомогою автоматизованих скриптів, кожне таке рішення, яке «істотно впливає» на користувача, може порушувати статтю 22.\n\nКвиток HT-2YBP-F7JP-D4VB (Розділ 18) було закрито через три дні з використанням шаблонного повідомлення про передачу справи, без розгляду зазначеної правової основи. На підставі запису неможливо встановити, чи хтось його переглядав; це питання, яке наглядовий орган може поставити Valve відповідно до статті 22 та статті 15(1)(h).\n\nДжерело: знімки сайту store.steampowered.com/stats/support, збережені в Wayback Machine (2018-02-03, 2021-06-26, 2026-08-10) — дані витягнуто у файл VALVE_EVIDENCE_PACK/databases/steam_support_stats_history.json (21 знімок, 2018–2026). Примітка: час відповіді «~52 хв» є нижньою межею для категорії повернення коштів; час відповіді щодо безпеки облікового запису становив 2,4–16,5 годин у тих самих знімках. 2021-06-26 — це історичний пік (547,907 запитів на повернення коштів), а не монотонна середня точка — обсяг зріс приблизно в 6 разів у 2020–2021 роках, потім частково знизився, а потім відновився до 373 тис. у 2026 році.\nДодаток I — Обсяг набору даних · показники, які можна відтворити\nПідрахуйте записи. Перевірте область дії.\nКонтекст та обмеження джерел\n\nПорахуйте записи, а потім перевірте наведені твердження: кожну цифру, наведену нижче, можна повторно обчислити на основі опублікованих файлів.\n\nПеревірте вихідні набори даних, відтворіть результати підрахунку та відокремте рядки-джерела від окремих випадків.\n\nГоловний файл CSV містить 40,448 рядків. З них, 36,516 походять із каналів Discord-AntiScam, присвячених фішингу. Решта 3,932 Ці рядки охоплюють GitHub, огляди, результати пошуку, матеріали форумів та інші джерела, забезпечуючи вичерпний перелік тем, що обговорюються в спільноті, та звітів про безпеку.\n\nУ цьому CSV-файлі 1,690 рядків віднесені до категорії «Невиправлені уразливості безпеки», що відображає історичні проблеми користувачів та оприлюднені відомості про уразливості. Аналіз цих повідомлень передбачає вивчення конкретної хронології збірок та публічної історії випуску виправлень для кожної гілки.\n\nАрхів із можливістю пошуку за записом 16,319 — це окрема, ретельно підібрана збірка з власним маніфестом, призначена для точного локального аналізу конкретних заяв користувачів та повідомлень про інциденти.\n\nЩоб створити надійний аудиторський слід, кожен запис, внесений користувачем, має бути перевірений на відповідність задокументованим графікам збірки та історичним журналам випуску виправлень.\n\nОкремі записи колекції, що входять до частини II 231,829 унікальних ідентифікаторів оголошень, у тому числі 33,509 у категорії автоматизованої реєстрації та 198,320, позначених як неперевірені перекази. Значення SHA-256 вхідного файлу збігається із збереженими даними вимірювання. Ці показники описують спроби розміщення оголошень та зафіксовані перекази, а не остаточні суми транзакцій чи підтверджені загальні суми крадіжок, що підкреслює необхідність використання первинних записів платформ для вимірювання точного економічного впливу. Перелік розмірів та хеш-значень ↗\n\nОпанувати CSV ↗ · Архівний маніфест з можливістю пошуку ↗ · Переглянути вихідні записи ↗\n\nДодаток J — Про це розслідування\nValve не публікує даних про заходи примусового виконання. Ми створили такий.\n\nНезалежний. Некомерційний. Створено виключно на основі відкритих даних. Подано до регулюючих органів.\n\n88.97%парк засобів автоматизації залишається без змін — жодних заборон\n67.77%з 51,732 шахраїв, щодо яких було винесено судове рішення, залишаються на свободі\n$26.8M+мінімальний рівень витрат на заправку для автопарку, що не підпадає під обмеження\n3.6%домени, пов’язані з азартними іграми, заблоковані фільтром посилань Valve\n8 роківзафіксованих інцидентів безпеки\n\nЩо це таке. Криміналістичне досьє щодо платформи Steam корпорації Valve — її історія правозастосування, економіка «кард-фармінгу», правова база та інфраструктура автентифікації, яку оператори азартних ігор використовують через власний ретранслятор OpenID компанії Steam. Кожен показник можна відтворити з двох джерел: власного публічного API компанії Valve та наборів даних, опублікованих разом із цим розслідуванням.\n\nДля кого це призначено. Регулюючі органи, до юрисдикції яких належить Valve — наглядовий орган з питань GDPR у Нідерландах, FinCEN, SEC, координатор з цифрових послуг DSA, UOKiK, а також будь-які правоохоронні органи, що розслідують фінансові потоки, пов’язані з Steam. А також для журналістів, дослідників та кожного користувача, якому було накладено постійну заборону на використання облікового запису, відмовлено у поверненні коштів або викрадено інвентар, і якому було повідомлено, що оскаржити це рішення неможливо.\n\nЄдина вимога. Valve зберігає ці дані з повною точністю — із зазначенням причин заборони, повним простором ідентифікаторів та в режимі реального часу. Система може обробити будь-який запит у цьому досьє за лічені секунди, але вирішила не оприлюднювати жодної з цих даних. Питання до будь-якого компетентного органу є простим: а чому б і ні?\n\nЧого автори не стверджують. Під час цієї роботи на жодній сторонній платформі не було здійснено входу в систему Steam. Надана URL-адреса OpenID визначає параметри запиту, а не факт завершення входу в систему. Наявність окремого домену, що підлягає реєстрації, сама по собі не є доказом ухилення. Дати реєстрації є нижньою межею того, коли хост міг вперше з’явитися у запиті OpenID; вони не свідчать про безперервне використання. Автори не роблять тверджень щодо того, що знав або мав на меті Valve: кожне твердження щодо Valve пов’язане з датованим публічним документом або датованим спостереженням. У випадках, коли твердження не можна було підкріпити вихідним документом, його було вилучено.\n\nХто ми\n\nPhishDestroy — незалежні дослідники. Не мають жодного відношення до корпорації Valve або будь-якої з платформ, згаданих тут. Один обліковий запис Steam використовувався виключно для документування запиту відповідно до GDPR, про який йдеться в розділі 18.\n\nЮридичне застереження\n\nНекомерційне, децентралізоване розслідування в інтересах суспільства. Усі дані надаються «як є», без жодних гарантій. Ця публікація не є судовим висновком.\n\nПУБЛІЧНИЙ ДОМЕН\nЛіцензування\n\nУсі права передано людству. Дозволено відтворювати, адаптувати, публікувати — вказівка авторства не потрібна. Доступ у регіоні, що підпадає під дію OFAC: заборонено. Повна ліцензія та відмова від відповідальності →",
        "headings": [
          {
            "level": 2,
            "id": "briefing-heading",
            "text": "Правило. Рекорд. Питання, на які немає відповіді."
          },
          {
            "level": 2,
            "id": null,
            "text": "Відкритий лист до Комісії з питань азартних ігор штату Вашингтон"
          },
          {
            "level": 3,
            "id": "wsgc-public-address-title",
            "text": "Десять днів перетворилися на десять років.Відкрийте запис знову."
          },
          {
            "level": 2,
            "id": null,
            "text": "Сайт заблоковано. Маршрут входу в систему — ні."
          },
          {
            "level": 3,
            "id": null,
            "text": "Рисунок 3.1 — Два маршрути на карті."
          },
          {
            "level": 3,
            "id": null,
            "text": "Пастка «загальної картини»: фільтр посилань — це лише імітація дотримання вимог, а не захист"
          },
          {
            "level": 3,
            "id": null,
            "text": "Заблокований основний домен у поєднанні з розблокованим хостом автентифікації залишає маршрут входу відкритим — і він залишається відкритим роками."
          },
          {
            "level": 3,
            "id": null,
            "text": "Вступ: Що таке Steam і чому це має значення в даному контексті"
          },
          {
            "level": 3,
            "id": null,
            "text": "Що зробив Valve: Блокування домену"
          },
          {
            "level": 3,
            "id": null,
            "text": "Що таке проксі-домен"
          },
          {
            "level": 3,
            "id": null,
            "text": "Критична точка: у кожному запиті хост автентифікації передається як Steam"
          },
          {
            "level": 3,
            "id": null,
            "text": "Що це доводить"
          },
          {
            "level": 3,
            "id": null,
            "text": "У Steam список Valve є єдиним списком."
          },
          {
            "level": 3,
            "id": null,
            "text": "Обхід захисту фільтра посилань"
          },
          {
            "level": 3,
            "id": null,
            "text": "Веб-браузер Big Picture розкриває файли cookie для входу та конфіденційну інформацію (що може призвести до захоплення облікового запису)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Що це означає для неповнолітнього, у якого встановлено антивірус"
          },
          {
            "level": 3,
            "id": null,
            "text": "Вік домену.Дата спостереження."
          },
          {
            "level": 2,
            "id": null,
            "text": "Кінцева точка закрита. У публічному трасуванні втрачено ключ."
          },
          {
            "level": 3,
            "id": null,
            "text": "Епоха до відключення електроенергії"
          },
          {
            "level": 3,
            "id": null,
            "text": "Після зміни"
          },
          {
            "level": 2,
            "id": null,
            "text": "Один сеанс. Більше прав доступу, ніж бачить користувач."
          },
          {
            "level": 3,
            "id": null,
            "text": "1. Недостатній рівень посиленої аутентифікації"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. Відсутність принципу мінімальних привілеїв"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. Порушення управління сесіями"
          },
          {
            "level": 3,
            "id": null,
            "text": "4. Блокування хостів автентифікації на рівні домену було технічно можливим"
          },
          {
            "level": 3,
            "id": "integration-paradox-title",
            "text": "Valve щодня компілюється з дотриманням цих правил. У цьому випадку компіляція не пройшла з дотриманням цих правил."
          },
          {
            "level": 4,
            "id": null,
            "text": "Дрібні області дії GitHub проти Valve Steam Web API"
          },
          {
            "level": 2,
            "id": null,
            "text": "Інтерактивний симулятор експлойтів та захоплення контролю"
          },
          {
            "level": 2,
            "id": null,
            "text": "Кінцеві точки, що лежать в основі послідовності."
          },
          {
            "level": 2,
            "id": null,
            "text": "Позначка у полі. Чия дія?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Як Valve нарешті подолав проблему «заміщення товарів» — і чому на це знадобилося 7 років обхідних рішень"
          },
          {
            "level": 4,
            "id": null,
            "text": "Час відновлення аватара та імені (лютий 2024 р.)"
          },
          {
            "level": 4,
            "id": null,
            "text": "7-денне розворотне відхилення CS2 (липень 2025 р.)"
          },
          {
            "level": 4,
            "id": null,
            "text": "Обов’язкове впровадження мобільних push-повідомлень для API (грудень 2023 р.)"
          },
          {
            "level": 4,
            "id": null,
            "text": "Банери з датою створення та назвою облікового запису (2022–2024)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Їхні правила. Зареєстровані платформи."
          },
          {
            "level": 3,
            "id": "enforcement-focus-title",
            "text": "Один звід правил. Нерівне застосування."
          },
          {
            "level": 4,
            "id": null,
            "text": "Автоматизація"
          },
          {
            "level": 4,
            "id": null,
            "text": "Комерційне використання"
          },
          {
            "level": 4,
            "id": null,
            "text": "VPN та маскування місцезнаходження"
          },
          {
            "level": 4,
            "id": null,
            "text": "Зашифрування посилань"
          },
          {
            "level": 4,
            "id": null,
            "text": "Хто переглядає рішення, коли служба підтримки закриває справу?"
          },
          {
            "level": 2,
            "id": null,
            "text": "API для автоматизації. Правило, що забороняє автоматизацію."
          },
          {
            "level": 3,
            "id": null,
            "text": "Хибне уявлення про «розробника ігор»"
          },
          {
            "level": 4,
            "id": null,
            "text": "Протиріччя автоматизації"
          },
          {
            "level": 4,
            "id": null,
            "text": "Позиція на стороні сервера в торговому потоці"
          },
          {
            "level": 2,
            "id": null,
            "text": "Потрібно було десять днів. А відзвітувати — за десять років."
          },
          {
            "level": 3,
            "id": "letter-company",
            "text": "КОРПОРАЦІЯ «VALVE»"
          },
          {
            "level": 3,
            "id": null,
            "text": "Десять днів.То що ж тоді?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Перейдіть на вказаний хост для повернення."
          },
          {
            "level": 3,
            "id": "washington-record-heading",
            "text": "Два терміни. Один невизначений стандарт виконання."
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve надає сайтам, що пропонують азартні ігри, 10 днів"
          },
          {
            "level": 4,
            "id": null,
            "text": "Вашингтон тисне Valve"
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve відхиляє звинувачення"
          },
          {
            "level": 4,
            "id": null,
            "text": "Маршрути, зафіксовані у вересні 2026 року"
          },
          {
            "level": 4,
            "id": null,
            "text": "Через вісімнадцять місяців після відповіді Valve регуляторний орган все ще називав це «наміром»."
          },
          {
            "level": 3,
            "id": null,
            "text": "«Десятиліття 10-денного попередження»: криміналістичний аудит стану збереженості 23 зазначених об’єктів"
          },
          {
            "level": 4,
            "id": null,
            "text": "Від 10-денних попереджень до офшорних конгломератів: оборот у кілька мільярдів доларів"
          },
          {
            "level": 2,
            "id": null,
            "text": "Ім'я хоста вже вказано у запиті."
          },
          {
            "level": 3,
            "id": null,
            "text": "Задокументовані та оприлюднені прецеденти"
          },
          {
            "level": 3,
            "id": null,
            "text": "Що відображає дата реєстрації, а що — ні"
          },
          {
            "level": 3,
            "id": null,
            "text": "Порівняльний аудит: стандарти відповідності API"
          },
          {
            "level": 2,
            "id": "market-thesis-heading",
            "text": "Цінова різниця «off-Steam»"
          },
          {
            "level": 2,
            "id": null,
            "text": "Різниця в ціні є відчутною."
          },
          {
            "level": 3,
            "id": null,
            "text": "Що показує ця сума в доларах"
          },
          {
            "level": 3,
            "id": null,
            "text": "Багато закладів вказують суму, що перевищує Steam доларів."
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam як і раніше лідирує за кількістю пропозицій."
          },
          {
            "level": 3,
            "id": null,
            "text": "Комерційна екосистема лежить на поверхні."
          },
          {
            "level": 2,
            "id": null,
            "text": "Хто може скинути захисні заходи?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Квиток на відновлення, який призвів до вимкнення системи безпеки облікового запису, та заявлена втрата у розмірі $10,000"
          },
          {
            "level": 3,
            "id": null,
            "text": "За межами інвентаризації."
          },
          {
            "level": 3,
            "id": "theft-ledger-title",
            "text": "Valve двічі відчинив двері з інтервалом у тридцять три місяці. Вони так і не зачинилися."
          },
          {
            "level": 4,
            "id": null,
            "text": "Те, що випливає з бухгалтерської книги, чого не можна сказати про жодний окремий випадок."
          },
          {
            "level": 3,
            "id": null,
            "text": "Конфіденційність має супроводжуватися технічною підзвітністю."
          },
          {
            "level": 2,
            "id": null,
            "text": "Слідкуйте за грошима. Розділяйте транзакції."
          },
          {
            "level": 3,
            "id": null,
            "text": "Де насправді рухаються гроші."
          },
          {
            "level": 3,
            "id": null,
            "text": "Спочатку класифікуйте діяльність, а потім — зобов’язання."
          },
          {
            "level": 3,
            "id": null,
            "text": "Відстежуйте надходження коштів, отримуйте інформацію та допомогу."
          },
          {
            "level": 2,
            "id": null,
            "text": "Закон про цифрові послуги: зафіксувати інформацію офіційно"
          },
          {
            "level": 3,
            "id": null,
            "text": "Десятиденний термін виконання вимоги."
          },
          {
            "level": 3,
            "id": null,
            "text": "Часове вікно DSA."
          },
          {
            "level": 3,
            "id": null,
            "text": "Для тривалості потрібно створити ланцюжок повідомлень."
          },
          {
            "level": 3,
            "id": null,
            "text": "щорічного світового обороту"
          },
          {
            "level": 2,
            "id": null,
            "text": "Неповнолітні: вхід із кодом Steam не є перевіркою віку"
          },
          {
            "level": 3,
            "id": null,
            "text": "Визначте оператор та дані."
          },
          {
            "level": 3,
            "id": null,
            "text": "Зафіксуйте весь процес — від входу в систему до внесення депозиту."
          },
          {
            "level": 2,
            "id": null,
            "text": "Запит. Відповідь. Відсутнє порівняння."
          },
          {
            "level": 3,
            "id": null,
            "text": "Записи існують; суб’єкт даних їх не отримав."
          },
          {
            "level": 2,
            "id": null,
            "text": "Угода з абонентом, що суперечить власній архітектурі платформи"
          },
          {
            "level": 3,
            "id": null,
            "text": "Максимальна ринкова ціна та заборона використання в комерційних цілях"
          },
          {
            "level": 3,
            "id": null,
            "text": "Уразливість API-ключа — це проблема, пов’язана з архітектурою платформи, а не з недбалістю користувачів"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve отримує ім’я хоста для автентифікації під час кожного входу в систему"
          },
          {
            "level": 3,
            "id": null,
            "text": "Закономірність у заархівованих скаргах"
          },
          {
            "level": 3,
            "id": null,
            "text": "Суд, який розглядатиме цю справу, не буде тлумачити Закон про соціальне забезпечення (SSA) у відриві від контексту."
          },
          {
            "level": 2,
            "id": null,
            "text": "Результати. Документи, які ми просимо надати."
          },
          {
            "level": 2,
            "id": null,
            "text": "Меморандум щодо доказів — матеріали, надані джерелом № 1"
          },
          {
            "level": 2,
            "id": null,
            "text": "Редагування у створеному PDF-файлі має суто косметичний характер: прихований текст залишається доступним для вилучення"
          },
          {
            "level": 2,
            "id": null,
            "text": "Документи щодо підтримки та юридичної кореспонденції"
          },
          {
            "level": 2,
            "id": null,
            "text": "Вибрані первинні документи"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-01",
            "text": "Апаратні ключі, замовлені у 2016 році"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-02",
            "text": "Звіти про збої без ефективної можливості відмови від отримання"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-03",
            "text": "Про зловживання авторизаційними квитками повідомлено на Valve"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-01",
            "text": "44 спірні покупки на ринку"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-02",
            "text": "Постійна заборона та закриті апеляції"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-03",
            "text": "Скидання процесу відновлення та зафіксовані збитки у розмірі $10,000"
          },
          {
            "level": 2,
            "id": null,
            "text": "ArchiSteamFarm та положення про автоматизацію"
          },
          {
            "level": 2,
            "id": null,
            "text": "Rules ledger: clauses against recorded platforms"
          },
          {
            "level": 3,
            "id": "ledger-title",
            "text": "Комерційне використання та нарахування коштів на рахунок"
          },
          {
            "level": 3,
            "id": "lw-register-title",
            "text": "Реєстр платформ 175"
          },
          {
            "level": 4,
            "id": null,
            "text": "Тягар доказування"
          },
          {
            "level": 4,
            "id": null,
            "text": "Що таке запис із тегами, а що — ні"
          },
          {
            "level": 2,
            "id": null,
            "text": "Посібник з DSAR: запит на надання доказів"
          },
          {
            "level": 3,
            "id": null,
            "text": "Збережіть свою хронологію."
          },
          {
            "level": 3,
            "id": null,
            "text": "Запитайте свої збережені дані."
          },
          {
            "level": 3,
            "id": null,
            "text": "Зберігайте квитанцію про доставку."
          },
          {
            "level": 3,
            "id": null,
            "text": "Порівняйте відповіді."
          },
          {
            "level": 3,
            "id": null,
            "text": "Безпека облікового запису та записи про доступ"
          },
          {
            "level": 3,
            "id": null,
            "text": "Розбіжність є підставою для проведення розслідування."
          },
          {
            "level": 2,
            "id": null,
            "text": "Обсяг підтримки. Опубліковані показники часу реагування."
          },
          {
            "level": 3,
            "id": null,
            "text": "Дві черги біля одного пункту обслуговування — про це йдеться у 21 архівних знімках екрана."
          },
          {
            "level": 2,
            "id": null,
            "text": "Підрахуйте записи. Перевірте область дії."
          },
          {
            "level": 2,
            "id": null,
            "text": "Valve не публікує даних про заходи примусового виконання.\nМи створили такий."
          }
        ],
        "links": [
          "https://dotesports.com/counter-strike/news/csgo-lounge-billion-bets-3896",
          "https://store.steampowered.com/agreement/?l=english",
          "http://web.archive.org/web/20260921022032/https://store.steampowered.com/agreement/?l=english",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-all-results.json",
          "https://blog.counter-strike.net/expresstrade/",
          "http://web.archive.org/web/20260307161538/https://blog.counter-strike.net/expresstrade/",
          "https://wsgc.wa.gov/news/2016/washington-state-gambling-commission-orders-valve-stop-skins-gambling",
          "http://web.archive.org/web/20260520012601/https://wsgc.wa.gov/news/2016/washington-state-gambling-commission-orders-valve-stop-skins-gambling",
          "https://fr.scribd.com/document/328063293/Valve-s-Oct-18th-response-to-Washington-State-Gambling-Commission-s-cease-and-desist",
          "https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921021947/https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921022628/https://steamcommunity.com/linkfilter/?url=https:%2F%2Frollbit.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rbsnin.com.20260921T021120Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rollbit.com.json",
          "http://web.archive.org/web/20260921022740/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fskin.club",
          "http://web.archive.org/web/20260921022842/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fsc-auth.net",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skin.club.json",
          "http://web.archive.org/web/20260921022603/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fhowl.gg",
          "http://web.archive.org/web/20260921022636/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fhowl.uno",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/howl.gg.json",
          "http://web.archive.org/web/20260921022840/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fduelbits.com",
          "http://web.archive.org/web/20260921022901/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fswitchflips.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/duelbits.com.json",
          "http://web.archive.org/web/20260921022758/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgofast.com",
          "http://web.archive.org/web/20260921022847/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fauthtofast.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgofast.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/farmskins.com.20260921T025840Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/steam.kobal.cc.20260921T025844Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/farmskins.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cobaltlab.tech.20260921T041604Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cobaltauth.com.20260921T041608Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/cobaltlab.tech.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgo.net.20260921T041619Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cn2.easylot.net.20260921T041623Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgo.net.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/ggdrop.com.20260921T041637Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/ggauth.com.20260921T041641Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/ggdrop.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rustchance.com.20260921T041703Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/hgfuihd.com.20260921T041706Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rustchance.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skin.fans.20260921T041710Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.skinfans.com.20260921T041713Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skin.fans.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinport.com.20260921T041724Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinport.app.20260921T041728Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skinport.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skins.cash.20260921T041731Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinscash.live.20260921T041735Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skins.cash.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2hunt.com.20260921T041739Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rstspcl.com.20260921T041742Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tf2hunt.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgogem.com.20260922T192355Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/api.csgem.com.20260922T192358Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-2026-09-22.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/gamdom.com.20260922T192326Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/login.gambldom.com.20260922T192330Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/12cs.fail.20260922T192347Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/fail.games.20260922T192351Z.html",
          "http://web.archive.org/web/20260921022953/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgoempire.com",
          "http://web.archive.org/web/20260921022947/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgoempirelogin4.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgoempire.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cs.money.20260921T021131Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.dota.trade.20260921T021134Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/cs.money.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csfloat.com.20260921T041612Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgofloat.com.20260921T041615Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csfloat.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/g4skins.com.20260921T041630Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.g4s.to.20260921T041634Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/g4skins.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/juice.gg.20260921T041644Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/letmeinjuice.com.20260921T041648Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/juice.gg.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/market.csgo.com.20260921T041652Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2.net.20260921T041655Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/market.csgo.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rust.tm.20260921T041659Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rust.tm.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgolounge.com.20260922T192333Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2.net.20260922T192340Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2lounge.com.20260922T192337Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinbaron.de.20260921T041717Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinbaron.com.20260921T041721Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skinbaron.de.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2royal.com.20260921T041746Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2auth.com.20260921T041750Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tf2royal.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tradeit.gg.20260921T041753Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/connect-tradeit.com.20260921T041757Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tradeit.gg.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/upgrader.pro.20260921T041801Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/upgauth.space.20260921T041804Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/upgrader.pro.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-recheck-2026-09-21.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/domain-registration.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wayback-snapshots.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-2026-09-22c.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/master_registry.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/longitudinal-steam-phishing-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-steam-phishing-100.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-coverage-2026-09-22.json",
          "https://blog.csfloat.com/how-floatdb-tracks-items/",
          "http://web.archive.org/web/20260921022415/https://blog.csfloat.com/how-floatdb-tracks-items/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/platform-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/platforms-removed.json",
          "https://hackerone.com/reports/291750",
          "http://web.archive.org/web/20251116185046/https://hackerone.com/reports/291750",
          "https://hackerone.com/reports/1079561",
          "http://web.archive.org/web/20260924181830/https://hackerone.com/reports/1079561",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/hackerone-reports.json",
          "https://phishdestroy.io/steam_dossier/uk/steam_enforcement_evidence.html#support-records",
          "https://www.darknavy.org/blog/exploiting_steam_usual_and_unusual_ways_in_the_cef_framework/",
          "https://steamcommunity.com/groups/SteamClientBeta/discussions/0/3365901765276206401/",
          "http://web.archive.org/web/20250804051514/https://steamcommunity.com/groups/SteamClientBeta/discussions/0/3365901765276206401/",
          "https://www.chromium.org/developers/design-documents/safebrowsing/",
          "http://web.archive.org/web/20260821101616/https://www.chromium.org/developers/design-documents/safebrowsing/",
          "https://www.chromium.org/developers/how-tos/api-keys/",
          "http://web.archive.org/web/20260830122831/https://www.chromium.org/developers/how-tos/api-keys/",
          "https://github.com/Homebrew/homebrew-cask/issues/193814",
          "https://testsafebrowsing.appspot.com/",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/domain-registration.json",
          "https://phishdestroy.io/steam_dossier/uk/AUTH_AUDIT.md",
          "https://datatracker.ietf.org/doc/rfc6749/",
          "https://docs.cloud.google.com/docs/authentication/api-keys",
          "https://listings.pcisecuritystandards.org/pdfs/PCI_DSS_Resource_Guide_(003).pdf",
          "https://developer.apple.com/news/?id=02202019a",
          "http://web.archive.org/web/20250506070026/https://developer.apple.com/news/?id=02202019a",
          "https://dev.twitch.tv/docs/authentication/validate-tokens/",
          "https://discuss.dev.twitch.com/t/legacy-twitch-api-v5-i-e-kraken-shutdown-reminder-february-28-2022/36589",
          "http://web.archive.org/web/20250127085635/https://discuss.dev.twitch.com/t/legacy-twitch-api-v5-i-e-kraken-shutdown-reminder-february-28-2022/36589",
          "https://store.steampowered.com/news/posts/?enddate=1788390000",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/4123547285514022851",
          "https://skinvault.gg/blog/cs2-trade-protection-explained/",
          "https://csmarketcap.com/blog/market-insights/from-boom-to-bust-cs2s-trade-protection-impact",
          "https://skin.land/blog/steam-changes-cs2-trade-ban-logic-timing/",
          "https://help.steampowered.com/faqs/view/3041-A87A-E5F6-B6AC",
          "https://steamcommunity.com/ogg/593110/announcements/detail/533224478739530146",
          "https://steamcommunity.com/games/CSGO/announcements/detail/4447966961421256740",
          "https://steamcommunity.com/sharedfiles/filedetails/?id=2926756889",
          "https://steamcommunity.com/dev/apikey",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3734103130194459461",
          "https://steamcommunity.com/discussions/forum/1/3807266184852932971/",
          "https://help.steampowered.com/faqs/view/225C-C51E-B8F0-55B2",
          "https://store.steampowered.com/news/group/4/view/3314112260640237775",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/issues/325",
          "https://blog.dota2.com/2020/05/trading-cooldown/",
          "https://blog.counter-strike.net/index.php/2018/03/20308/",
          "http://web.archive.org/web/20250226114333/https://blog.counter-strike.net/index.php/2018/03/20308/",
          "https://phishdestroy.io/steam_dossier/uk/steam_evidence_archive.html",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/493839547938902179",
          "https://store.steampowered.com/online_conduct",
          "http://web.archive.org/web/20260921022120/https://store.steampowered.com/online_conduct",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260918014700/https://store.steampowered.com/subscriber_agreement/",
          "https://steamcommunity.com/dev/apiterms",
          "http://web.archive.org/web/20260921022210/https://steamcommunity.com/dev/apiterms",
          "https://help.steampowered.com/en/faqs/view/628C-E332-BD8C-4D36",
          "https://phishdestroy.io/steam_dossier/uk/social_graph.html",
          "https://phishdestroy.io/steam_dossier/uk/security_timeline.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wsgc-skins-gambling-briefing-2018.pdf",
          "https://wsgc.wa.gov/sites/default/files/2023-10/Skins%20Gambling.pdf",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wsgc-briefing-manifest.json",
          "https://x.com/csgobig",
          "https://www.facebook.com/csgobigofficial/",
          "https://500.casino/",
          "https://csgolounge.com/",
          "https://csgocasino.gg/",
          "https://x.com/CSGOatsecom",
          "https://x.com/CSGOSweep/status/937420902538543106",
          "https://x.com/Wild",
          "https://x.com/csgopot",
          "https://x.com/csgodiamondscom",
          "https://www.ftc.gov/legal-library/browse/cases-proceedings/162-3184-csgo-lotto-matter",
          "https://x.com/CSGODouble",
          "https://x.com/csgo_massive",
          "https://www.facebook.com/csgostrongfree/",
          "https://www.facebook.com/CSNCOM/",
          "https://www.gamblingcommission.gov.uk/report/young-people-and-gambling",
          "https://www.aph.gov.au/Parliamentary_Business/Committees/Senate/Environment_and_Communications/Gamingmicro-transactions",
          "https://phishdestroy.io/steam_dossier/uk/elite_skins.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/csfloat-catalogue.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/skinport-floor-over-cap.json",
          "https://pricempire.com/cs2-marketplaces",
          "http://web.archive.org/web/20260921022459/https://pricempire.com/cs2-marketplaces",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/priceempire-marketplaces.json",
          "https://www.steamanalyst.com/marketplace",
          "http://web.archive.org/web/20260719014552/https://www.steamanalyst.com/marketplace",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-atlas.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json",
          "https://phishdestroy.io/steam_dossier/uk/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/uk/steam_enforcement_evidence.html#case-support-recovery",
          "https://top10.owasp.org/2025/A01_2025-Broken_Access_Control/",
          "http://web.archive.org/web/20260920212535/https://top10.owasp.org/2025/A01_2025-Broken_Access_Control/",
          "https://store.steampowered.com/privacy_agreement/",
          "http://web.archive.org/web/20260921021648/https://store.steampowered.com/privacy_agreement/",
          "https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "http://web.archive.org/web/20250818113925/https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "https://www.dexerto.com/counter-strike-2/valve-saves-hacked-cs2-player-threatened-with-ransom-over-300000-of-rare-stickers-3283135/",
          "https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "http://web.archive.org/web/20220702042821/https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "https://www.kaspersky.com/blog/cs-go-two-million-usd-inventory-hack/44697/",
          "https://esportfire.com/article/the-2-million-usd-csgo-hack-22062022",
          "http://web.archive.org/web/20260515110250/https://esportfire.com/article/the-2-million-usd-csgo-hack-22062022",
          "https://esportsbetting.com/valve-deletes-130000-stolen-dragon-lore/",
          "https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "http://web.archive.org/web/20251115173120/https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "https://vkplay.ru/media/news/bloger-rasskazal-kak-podderzhka-steam-vorovala-akkaunty-igrokov/",
          "https://lis-skins.com/ru/blog/krupneisaia-mosenniceskaia-sxema-v-istorii-steam/",
          "https://escorenews.com/ru/csgo/news/44056-sotrudniki-podderjki-steam-zanimalis-krajey-skinov-s-akkauntov-za-god-oni-zarabotali-svyshe-300-tysyach-dollarov",
          "https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "http://web.archive.org/web/20250805141942/https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/outsourcing-archive-records.json",
          "https://community.skin.club/en/news/collector-has-steam-inventory-returned-after-bold-hack",
          "https://esportfire.com/article/300k-scam-full-katowice-2014-holo-collection-hacked",
          "http://web.archive.org/web/20251217072445/https://esportfire.com/article/300k-scam-full-katowice-2014-holo-collection-hacked",
          "https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng",
          "http://web.archive.org/web/20260920024236/https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng",
          "https://ag.ny.gov/press-release/2026/attorney-general-james-sues-game-developer-promoting-illegal-gambling-through",
          "http://web.archive.org/web/20260901015430/https://ag.ny.gov/press-release/2026/attorney-general-james-sues-game-developer-promoting-illegal-gambling-through",
          "https://www.fincen.gov/sites/default/files/2019-05/FinCEN%20CVC%20Guidance%20FINAL.pdf",
          "http://web.archive.org/web/20250711185007/https://www.fincen.gov/sites/default/files/2019-05/FinCEN%20CVC%20Guidance%20FINAL.pdf",
          "https://eur-lex.europa.eu/legal-content/EN/LSU/?uri=CELEX:32018L1673",
          "https://eur-lex.europa.eu/eli/dir/2024/1640/oj/eng",
          "http://web.archive.org/web/20260830153004/https://eur-lex.europa.eu/eli/dir/2024/1640/oj/eng",
          "https://eur-lex.europa.eu/eli/reg/2022/2065/oj/eng",
          "http://web.archive.org/web/20260920080125/https://eur-lex.europa.eu/eli/reg/2022/2065/oj/eng",
          "https://phishdestroy.io/steam_dossier/uk/legal_analysis.html",
          "https://partner.steamgames.com/doc/features/auth#website",
          "http://web.archive.org/web/20260921022335/https://partner.steamgames.com/doc/features/auth",
          "https://www.ftc.gov/legal-library/browse/rules/childrens-online-privacy-protection-rule-coppa",
          "http://web.archive.org/web/20260921070051/https://www.ftc.gov/legal-library/browse/rules/childrens-online-privacy-protection-rule-coppa",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/gdpr-ticket-1.png",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/screenshot-manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/gdpr-ticket-2.png",
          "https://datenschutz.hamburg.de/beschwerde",
          "https://edpb.europa.eu/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/regulatory-review/disclosure-audit.json",
          "https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "http://web.archive.org/web/20260821155801/https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "https://phishdestroy.io/steam_dossier/uk/index#exhibit-gallery-section",
          "https://github.com/ValveSoftware/steam-for-linux/issues/4521",
          "https://phishdestroy.io/steam_dossier/uk/steam_evidence_archive.html?source=GitHub&record=484",
          "https://github.com/ValveSoftware/steam-for-linux/issues/6459",
          "http://web.archive.org/web/20260419051343/https://github.com/ValveSoftware/steam-for-linux/issues/6459",
          "https://phishdestroy.io/steam_dossier/uk/steam_evidence_archive.html?source=GitHub&record=467",
          "https://github.com/ValveSoftware/Source-1-Games/issues/3857",
          "https://phishdestroy.io/steam_dossier/uk/steam_evidence_archive.html?source=GitHub&record=768",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "http://web.archive.org/web/20250320082450/https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://phishdestroy.io/steam_dossier/uk/steam_evidence_archive.html?source=Reddit&record=4533",
          "https://www.reddit.com/r/ohnePixel/comments/1hahqx2/permanently_banned_steam_account_without_a_clear/",
          "https://phishdestroy.io/steam_dossier/uk/steam_evidence_archive.html?source=Reddit&record=4766",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://phishdestroy.io/steam_dossier/uk/steam_evidence_archive.html?source=Reddit&record=4592",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/selected-evidence-records.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive_manifest.json",
          "https://phishdestroy.io/steam_dossier/uk/card_economy.html",
          "https://github.com/JustArchiNET/ArchiSteamFarm/wiki/FAQ",
          "https://phishdestroy.io/steam_dossier/uk/card_economy.html#scale",
          "https://phishdestroy.io/steam_dossier/uk/card_economy.html#licence",
          "https://phishdestroy.io/steam_dossier/uk/enforcement_audit.html",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "http://web.archive.org/web/20260924181709/https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://rdap.verisign.com/com/v1/domain/csgoempire.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoempire.com",
          "https://rdap.verisign.com/com/v1/domain/csgoempirelogin4.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/csgoempire.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustreaper.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustreaper.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/rustreaper.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustly.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustly.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/rustly.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgofast.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgofast.com",
          "https://rdap.verisign.com/com/v1/domain/authtofast.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/csgofast.com.json",
          "https://rdap.verisign.com/com/v1/domain/duelbits.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fduelbits.com",
          "https://rdap.verisign.com/com/v1/domain/switchflips.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/duelbits.com.json",
          "https://rdap.verisign.com/com/v1/domain/farmskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffarmskins.com",
          "https://tld-rdap.verisign.com/cc/v1/domain/kobal.cc",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/farmskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoluck.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoluck.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/csgoluck.com.json",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/domain-registry/insane.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Finsane.gg",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/insane.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs2skin.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs2skin.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/cs2skin.com.json",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/domain-registry/juice.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fjuice.gg",
          "https://rdap.verisign.com/com/v1/domain/letmeinjuice.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/juice.gg.json",
          "https://rdap.verisign.com/com/v1/domain/ggdrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fggdrop.com",
          "https://rdap.verisign.com/com/v1/domain/ggauth.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/ggdrop.com.json",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/domain-registry/howl.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhowl.gg",
          "https://rdap.radix.host/rdap/domain/howl.uno",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/howl.gg.json",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/domain-registry/chicken.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fchicken.gg",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/chicken.gg.json",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/domain-registry/csgocasino.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgocasino.gg",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/csgocasino.gg.json",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/domain-registry/hunt.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhunt.gg",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/hunt.gg.json",
          "https://rdap.verisign.com/com/v1/domain/csbattle.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsbattle.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/csbattle.com.json",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/domain-registry/skinrave.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinrave.gg",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/skinrave.gg.json",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/domain-registry/csdouble.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsdouble.gg",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/csdouble.gg.json",
          "https://rdap.verisign.com/com/v1/domain/rustchance.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustchance.com",
          "https://rdap.verisign.com/com/v1/domain/hgfuihd.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/rustchance.com.json",
          "https://rdap.radix.host/rdap/domain/cobaltlab.tech",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcobaltlab.tech",
          "https://rdap.verisign.com/com/v1/domain/cobaltauth.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/cobaltlab.tech.json",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/domain-registry/raided.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fraided.gg",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/raided.gg.json",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/domain-registry/rustneo.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustneo.gg",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/rustneo.gg.json",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/domain-registry/splits.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsplits.gg",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/splits.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/upgrader.pro",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fupgrader.pro",
          "https://rdap.radix.host/rdap/domain/upgauth.space",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/upgrader.pro.json",
          "https://rdap.centralnic.com/fans/domain/skin.fans",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.fans",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/skin.fans.json",
          "https://rdap.nic.one/domain/hotpizza.one",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhotpizza.one",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/hotpizza.one.json",
          "https://rdap.verisign.com/com/v1/domain/g4skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg4skins.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/g4skins.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2royal.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2royal.com",
          "https://rdap.verisign.com/com/v1/domain/tf2auth.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/tf2royal.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2hunt.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2hunt.com",
          "https://rdap.verisign.com/com/v1/domain/rstspcl.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/tf2hunt.com.json",
          "https://rdap.identitydigital.services/rdap/domain/tf2.bet",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2.bet",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/tf2.bet.json",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/domain-registry/openstars.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fopenstars.gg",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/openstars.gg.json",
          "https://rdap.verisign.com/com/v1/domain/skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/skins.com.json",
          "https://rdap.identitydigital.services/rdap/domain/white.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwhite.market",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/white.market.json",
          "https://rdap.identitydigital.services/rdap/domain/moon.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmoon.market",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/moon.market.json",
          "https://rdap.verisign.com/com/v1/domain/csfloat.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsfloat.com",
          "https://rdap.verisign.com/com/v1/domain/csgofloat.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/csfloat.com.json",
          "https://rdap.identitydigital.services/rdap/domain/skin.land",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.land",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/skin.land.json",
          "https://rdap.verisign.com/com/v1/domain/haloskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhaloskins.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/haloskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/163.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuff.163.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/buff.163.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmarket.csgo.com",
          "https://rdap.verisign.com/net/v1/domain/dota2.net",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/market.csgo.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinport.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinport.com",
          "https://pubapi.registry.google/rdap/domain/skinport.app",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/skinport.com.json",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/domain-registry/skinflow.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinflow.gg",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/skinflow.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/skin.place",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.place",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/skin.place.json",
          "https://rdap.verisign.com/com/v1/domain/skinsmonkey.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinsmonkey.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/skinsmonkey.com.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbaron.de",
          "https://rdap.verisign.com/com/v1/domain/skinbaron.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/skinbaron.de.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frust.tm",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/rust.tm.json",
          "https://rdap.verisign.com/com/v1/domain/pirateswap.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fpirateswap.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/pirateswap.com.json",
          "https://rdap.radix.host/rdap/domain/mannco.store",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmannco.store",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/mannco.store.json",
          "https://rdap.verisign.com/com/v1/domain/skinswap.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinswap.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/skinswap.com.json",
          "https://rdap.verisign.com/com/v1/domain/exeskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fexeskins.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/exeskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/balticskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbalticskins.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/balticskins.com.json",
          "https://rdap.nic.trade/domain/cs.trade",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.trade",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/cs.trade.json",
          "https://rdap.verisign.com/com/v1/domain/rapidskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frapidskins.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/rapidskins.com.json",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/domain-registry/tradeit.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftradeit.gg",
          "https://rdap.verisign.com/com/v1/domain/connect-tradeit.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/tradeit.gg.json",
          "https://rdap.verisign.com/com/v1/domain/49skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F49skins.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/49skins.com.json",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/domain-registry/skinvault.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinvault.gg",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/skinvault.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/aim.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Faim.market",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/aim.market.json",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/domain-registry/skinout.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinout.gg",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/skinout.gg.json",
          "https://rdap.verisign.com/com/v1/domain/ntskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fntskins.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/ntskins.com.json",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/domain-registry/gamerpay.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamerpay.gg",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/gamerpay.gg.json",
          "https://rdap.nic.tf/domain/scrap.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fscrap.tf",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/scrap.tf.json",
          "https://rdap.nic.tf/domain/marketplace.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmarketplace.tf",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/marketplace.tf.json",
          "https://rdap.identitydigital.services/rdap/domain/skins.cash",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.cash",
          "https://rdap.identitydigital.services/rdap/domain/skinscash.live",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/skins.cash.json",
          "https://rdap.verisign.com/net/v1/domain/csgo.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo.net",
          "https://rdap.verisign.com/net/v1/domain/easylot.net",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/csgo.net.json",
          "https://rdap.verisign.com/net/v1/domain/cybershoke.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcybershoke.net",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/cybershoke.net.json",
          "https://rdap.verisign.com/net/v1/domain/fastcup.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffastcup.net",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/fastcup.net.json",
          "https://rdap.verisign.com/com/v1/domain/leetify.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fleetify.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/leetify.com.json",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/domain-registry/scope.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fscope.gg",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/scope.gg.json",
          "https://rdap.verisign.com/com/v1/domain/tradeupspy.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftradeupspy.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/tradeupspy.com.json",
          "https://rdap.identitydigital.services/rdap/domain/cs.deals",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.deals",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/cs.deals.json",
          "https://rdap.verisign.com/com/v1/domain/pricempire.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fpricempire.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/pricempire.com.json",
          "https://rdap.identitydigital.services/rdap/domain/lzt.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flzt.market",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/lzt.market.json",
          "https://rdap.verisign.com/com/v1/domain/z2u.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fz2u.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/z2u.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoroll.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoroll.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/csgoroll.com.json",
          "https://rdap.verisign.com/com/v1/domain/rollbit.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frollbit.com",
          "https://rdap.verisign.com/com/v1/domain/rbsnin.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/rollbit.com.json",
          "https://rdap.identitydigital.services/rdap/domain/500.casino",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F500.casino",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/500.casino.json",
          "https://rdap.verisign.com/com/v1/domain/csgobig.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgobig.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/csgobig.com.json",
          "https://rdap.verisign.com/com/v1/domain/casedrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcasedrop.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/casedrop.com.json",
          "https://rdap.verisign.com/com/v1/domain/banditcamp.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbanditcamp.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/banditcamp.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinbox.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbox.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/skinbox.com.json",
          "https://rdap.verisign.com/com/v1/domain/tastydrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftastydrop.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/tastydrop.com.json",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/domain-registry/csgopolygon.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgopolygon.gg",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/csgopolygon.gg.json",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/domain-registry/magicdrop.ru.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmagicdrop.ru",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/magicdrop.ru.json",
          "https://rdap.verisign.com/com/v1/domain/csdice.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsdice.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/csdice.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinodds.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinodds.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/skinodds.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgowin.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgowin.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/csgowin.com.json",
          "https://rdap.verisign.com/net/v1/domain/csgorun.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgorun.net",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/csgorun.net.json",
          "https://rdap.verisign.com/com/v1/domain/openskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fopenskins.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/openskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustbet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustbet.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/rustbet.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgomagic.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgomagic.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/csgomagic.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgobounty.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgobounty.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/csgobounty.com.json",
          "https://rdap.verisign.com/com/v1/domain/ezskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fezskins.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/ezskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustcases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustcases.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/rustcases.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoreaper.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoreaper.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/csgoreaper.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgocases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgocases.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/csgocases.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo-skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo-skins.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/csgo-skins.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgonet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgonet.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/csgonet.com.json",
          "https://rdap.verisign.com/com/v1/domain/wtfskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwtfskins.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/wtfskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/flamecases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fflamecases.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/flamecases.com.json",
          "https://rdap.verisign.com/com/v1/domain/gamedom.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamedom.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/gamedom.com.json",
          "https://rdap.nic.club/domain/skin.club",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.club",
          "https://rdap.verisign.com/net/v1/domain/sc-auth.net",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/skin.club.json",
          "https://rdap.verisign.com/com/v1/domain/daddyskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdaddyskins.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/daddyskins.com.json",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/domain-registry/rustix.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustix.gg",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/rustix.gg.json",
          "https://rdap.nic.club/domain/skins.club",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.club",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/skins.club.json",
          "https://rdap.publicinterestregistry.org/rdap/domain/csgohouse.org",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgohouse.org",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/csgohouse.org.json",
          "https://rdap.verisign.com/net/v1/domain/skinrave.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinrave.net",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/skinrave.net.json",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/domain-registry/bloodycase.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbloodycase.gg",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/bloodycase.gg.json",
          "https://rdap.verisign.com/com/v1/domain/csgoclicker.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoclicker.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/csgoclicker.com.json",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/domain-registry/rustbet.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustbet.gg",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/rustbet.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs-drop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs-drop.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/cs-drop.com.json",
          "https://rdap.verisign.com/net/v1/domain/hellstore.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhellstore.net",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/hellstore.net.json",
          "https://rdap.verisign.com/com/v1/domain/rustloot.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustloot.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/rustloot.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo-case.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo-case.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/csgo-case.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgogem.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgogem.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/csgogem.com.json",
          "https://rdap.verisign.com/com/v1/domain/rainbet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frainbet.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/rainbet.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustclash.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustclash.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/rustclash.com.json",
          "https://rdap.identitydigital.services/rdap/domain/12cs.fail",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F12cs.fail",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/12cs.fail.json",
          "https://rdap.verisign.com/com/v1/domain/tf2easy.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwww.tf2easy.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/tf2easy.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2blaze.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2blaze.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/tf2blaze.com.json",
          "https://rdap.verisign.com/com/v1/domain/shuffle.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fshuffle.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/shuffle.com.json",
          "https://rdap.identitydigital.services/rdap/domain/buff.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuff.market",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/buff.market.json",
          "https://rdap.identitydigital.services/rdap/domain/avan.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Favan.market",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/avan.market.json",
          "https://rdap.identitydigital.services/rdap/domain/cs.money",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.money",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/cs.money.json",
          "https://rdap.verisign.com/com/v1/domain/uuskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fuuskins.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/uuskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/youpin898.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fyoupin898.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/youpin898.com.json",
          "https://rdap.verisign.com/com/v1/domain/c5game.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fc5game.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/c5game.com.json",
          "https://rdap.verisign.com/com/v1/domain/waxpeer.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwaxpeer.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/waxpeer.com.json",
          "https://rdap.verisign.com/com/v1/domain/dmarket.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdmarket.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/dmarket.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamcommunity.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamcommunity.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/steamcommunity.com.json",
          "https://rdap.verisign.com/com/v1/domain/lootfarm.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flootfarm.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/lootfarm.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustskins.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/rustskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/krakatoa.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fkrakatoa.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/krakatoa.com.json",
          "https://rdap.verisign.com/com/v1/domain/shadowpay.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fshadowpay.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/shadowpay.com.json",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/domain-registry/igxe.cn.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Figxe.cn",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/igxe.cn.json",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/domain-registry/swap.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fswap.gg",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/swap.gg.json",
          "https://rdap.verisign.com/com/v1/domain/bitskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbitskins.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/bitskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2mart.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2mart.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/tf2mart.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinbid.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbid.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/skinbid.com.json",
          "https://rdap.verisign.com/com/v1/domain/lootbear.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flootbear.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/lootbear.com.json",
          "https://rdap.nic.tf/domain/backpack.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbackpack.tf",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/backpack.tf.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fstntrading.eu",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/stntrading.eu.json",
          "https://rdap.verisign.com/com/v1/domain/skinwallet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinwallet.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/skinwallet.com.json",
          "https://rdap.verisign.com/com/v1/domain/dota2market.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdota2market.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/dota2market.com.json",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/domain-registry/xplay.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fxplay.gg",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/xplay.gg.json",
          "https://rdap.verisign.com/com/v1/domain/esportal.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fesportal.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/esportal.com.json",
          "https://rdap.registro.br/domain/gamersclub.com.br",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamersclub.com.br",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/gamersclub.com.br.json",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/domain-registry/epidemic.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fepidemic.gg",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/epidemic.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs2stash.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs2stash.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/cs2stash.com.json",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/domain-registry/csgoskins.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoskins.gg",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/csgoskins.gg.json",
          "https://rdap.verisign.com/com/v1/domain/steamanalyst.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamanalyst.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/steamanalyst.com.json",
          "https://rdap.verisign.com/net/v1/domain/steamcardexchange.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamcardexchange.net",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/steamcardexchange.net.json",
          "https://rdap.verisign.com/com/v1/domain/dotabuff.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdotabuff.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/dotabuff.com.json",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/domain-registry/tracker.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftracker.gg",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/tracker.gg.json",
          "https://rdap.verisign.com/com/v1/domain/funpay.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffunpay.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/funpay.com.json",
          "https://rdap.verisign.com/com/v1/domain/playerauctions.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fplayerauctions.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/playerauctions.com.json",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/domain-registry/eldorado.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Feldorado.gg",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/eldorado.gg.json",
          "https://rdap.verisign.com/com/v1/domain/g2a.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg2a.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/g2a.com.json",
          "https://rdap.verisign.com/net/v1/domain/kinguin.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fkinguin.net",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/kinguin.net.json",
          "https://rdap.verisign.com/com/v1/domain/g2g.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg2g.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/g2g.com.json",
          "https://rdap.verisign.com/com/v1/domain/playerup.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fplayerup.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/playerup.com.json",
          "https://rdap.verisign.com/net/v1/domain/smurfhub.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfhub.net",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/smurfhub.net.json",
          "https://rdap.verisign.com/com/v1/domain/smurfaccounts.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfaccounts.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/smurfaccounts.com.json",
          "https://rdap.verisign.com/com/v1/domain/buycsgorank.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuycsgorank.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/buycsgorank.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgosmurfkings.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgosmurfkings.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/csgosmurfkings.com.json",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/domain-registry/smurfstore.co.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfstore.co",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/smurfstore.co.json",
          "https://rdap.verisign.com/com/v1/domain/steamlvlup.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlvlup.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/steamlvlup.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamlevels.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlevels.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/steamlevels.com.json",
          "https://rdap.verisign.com/com/v1/domain/levelsteam.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flevelsteam.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/levelsteam.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamlevelu.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlevelu.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/steamlevelu.com.json",
          "https://rdap.verisign.com/com/v1/domain/eloking.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Feloking.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/eloking.com.json",
          "https://rdap.publicinterestregistry.org/rdap/domain/boosteria.org",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fboosteria.org",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/boosteria.org.json",
          "https://rdap.verisign.com/com/v1/domain/overgear.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fovergear.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/overgear.com.json",
          "https://rdap.verisign.com/com/v1/domain/blazingboost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fblazingboost.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/blazingboost.com.json",
          "https://rdap.verisign.com/com/v1/domain/dota2boost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdota2boost.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/dota2boost.com.json",
          "https://rdap.verisign.com/com/v1/domain/buyboost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuyboost.com",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit/buyboost.com.json",
          "https://phishdestroy.io/steam_dossier/uk/steam_tos_assets/auth-route-audit.json",
          "https://help.steampowered.com/en/faqs/view/365F-4BEE-2AE2-7BDD",
          "https://store.steampowered.com/privacy_agreement/#8",
          "https://www.edpb.europa.eu/system/files/2023-04/edpb_guidelines_202201_data_subject_rights_access_v2_en.pdf",
          "https://web.archive.org/web/20260810154631/https://store.steampowered.com/stats/support",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/design-review/part2/measurements.json",
          "https://phishdestroy.io/steam_dossier/uk/VALVE_EVIDENCE_PACK/databases/TOTAL_VALVE_SCANDALS_MASTER_DB.csv",
          "https://phishdestroy.io/steam_dossier/uk/license_disclaimer.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/uk/index.content.json",
      "export_json_sha256": "bc3ea3963836f16d187b92c7ff2f64da571193449f9c68a738db58c86b2b10ed"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "uk/investigation_part2.html",
      "language": "uk",
      "title": "Доступ до облікового запису та підзвітність — Досьє Steam",
      "source_url": "https://phishdestroy.io/steam_dossier/uk/investigation_part2",
      "source_html_sha256": "7c0e03f9c430ac28b9f74ee967759c2543d22fb50f17c7bfbb17c2be0faf8c51",
      "exported_at": "2026-09-29T00:19:29.259Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "investigation_part2.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/uk/investigation_part2.pdf?v=print-20260929-v5",
        "sha256": "11d33353871360c76a34acd6b80ad7e43114d173341a4f2a126c5712698504c2",
        "bytes": 136847,
        "pages": 9
      },
      "integrity": {
        "signed_object": "investigation_part2.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "investigation_part2.content.json.asc",
        "digest_file": "investigation_part2.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify investigation_part2.content.json.asc investigation_part2.content.json",
          "sha256sum -c investigation_part2.content.json.sha256"
        ]
      },
      "content": {
        "text": "ДОСЬЄ «STEAM» / II\n\nВаш обліковий запис.Їхній доступ.Хто відповідає?\n\nАвтоматизація державних послуг. Аутсорсингова підтримка. А люди змушені розраховуватися за це.\n\nСлідкуйте за станом інфраструктури, повідомленнями про збитки та документами, на яких ґрунтуються ці заяви.\n\nПростежте інфраструктуру ↘\nДОДАТОК 01 / МОНІТОРИНГ РИНКУ «ЖИВИХ ТІНЕЙ»550,000+\n\nSteam облікових записів, які активно виставлені на продаж на FSB Market (анонімізована назва; оригінальну назву тут не вказано)\nсаме в цю мить\n\n550,000+ НАЯВНІСТЬ У РЕАЛЬНОМУ ЧАСІ · 231,829 В ІСТОРИЧНОМУ КОРПУСІ, ЗІБРАНОМУ ШЛЯХОМ СКРЕЙПІНГУ (198,320 ЛОГИ STEALER)\n\nГоловний підпільний центр обміну викраденими Steam-рахунками, FSB Market (інші пов’язані назви не вказано) здійснює аутентифікацію як покупців, так і продавців за допомогою офіційного OpenID Valve Steam (openid.realm = https://FSB Market). У будь-яку хвилину понад півмільйона вкрадених та зламаних облікових записів (журнали зломщиків із RedLine/Lumma, дані, отримані в результаті фішингу, атаки методом «credential stuffing») активно виставляються на продаж за копійки ($0.50–$2.00). Ні той, ні інший FSB Market ані пов’язаний форум блокується фільтром посилань Valve. Це промисловий резервуар, що постачає 63.06% платних акаунтів-ботів, які Valve блокує, не надаючи допомоги потерпілому.\n\nLive Intel: Моніторинг тіньового ринку (понад 550 тис. користувачів у режимі реального часу) ↗ · Відкрити запис про захоплення ↗ · Відкрити трасування фільтра посилань ↗Понад 550 тис. у прямому ефірі\n\n01 / ЕКОСИСТЕМА З АВТОРАМИ\n\nАвтоматизація маєдокументальний ланцюжок.\n\nНазвані проєкти. Опубліковані можливості. Відстежте інструмент за його документацією, а потім проаналізуйте зібрані взаємозв’язки розробників.\n\n252ЗБІРНИКИ МАТЕРІАЛІВ\n3,320ПРОФІЛІ НА GITHUB\n4,214ПРОФІЛЬ — ПАРИ РЕПОЗИТОРІВ\nValve інфраструктураГромадські бібліотекиДодатки багаторазового використання\nЛінії позначають задокументовані інтеграції або залежності. Виберіть вузол, щоб переглянути відповідні дані.\n\nАвтоматизація роботи з декількома обліковими записами / JustArchiNET\n\nArchiSteamFarm\n\nПроєкт відкрито рекламує можливість одночасного фарму карт на різних облікових записах Steam. У файлі проєкту вказано залежність від SteamKit2.\n\nОзнайомтеся з документацією самого проєкту ↗\n\nSteamKit → ArchiSteamFarm\nзаявлена залежність ↗\n\nЗБІРКА ВІДНОСИН\n\n40 мітки авторів · 40 етикетки «Forker»\n\nНижче наведено приклад від автора. Ці позначки описують зв’язок із репозиторієм, а не трудові відносини чи затвердження.\n\n@JustArchi@renovate[бот]@JustArchi-ArchiBot@dependabot-preview[бот]@renovate-bot@actions-user@dependabot-support@Abrynos\nЩо показує графік розробника\n\nНа графіку відображено опубліковані дані про взаємозв’язки між авторами та розробниками, які створювали форки, у рамках зазначених проєктів та профілів GitHub. Це публічні дані — форки репозиторіїв, списки внесків, зв’язки між профілями. Питання полягає в тому, на що саме вимагає відповіді Valve на основі документальних доказів щодо опублікованих можливостей та взаємозв’язків розробників, а не в тому, що було вигадано в ході цього розслідування. Хеші вихідного коду зберігаються в походження карти.\n\nОзнайомтеся з усією мережею ↗Джерельні дані репозиторію ↓\n\n02 / РІЗНІ ПОВНОВАЖЕННЯ. РІЗНІ ПОВНОВАЖЕННЯ.\n\nЯка клавішаПро що саме йдеться?\n\nДля гри гравцеві не потрібно надавати особистий ключ веб-API. Саме в цьому полягає головна відмінність, що лежить в основі даного розслідування.\n\n01 / ОБЛІКОВИЙ ЗАПИС КОРИСТУВАЧА\nОсобистий ключ Web API\nsteamcommunity.com/dev/apikey\n\nВидається з облікового запису користувача для дозволених викликів API. Створення ключів, їхня видимість, скасування та виявлення зловживань — це питання безпеки облікового запису.\n\n02 / БЕКЕНД ІГРИ\nКлюч Web API видавця\n\nПартнери Steamworks використовують облікові дані видавця для виконання підтримуваних операцій на серверній стороні, зокрема для надання послуг, пов’язаних з іграми. Особистий ключ гравця є окремим обліковим елементом.\n\n03 / ІДЕНТИФІКАЦІЯ ТА СЕСІЯ\nOpenID / токени сеансу\n\nOpenID підтверджує особу на веб-сайті. Сесійний або токен оновлення Steam має інше призначення. Ці механізми не слід подавати як один взаємозамінний «ключ API».\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\nValve містить ключі Web API як для користувачів, так і для видавців. Отже, Web API в цілому не є окремим від Steamworks. Документація щодо ключів API ↗ архів 2026-09-15 ↗ · Аутентифікація під час ігрової сесії ↗ архів 2026-08-29 ↗\n\nСКЛАДЕНО АВТОРОМ ІНСТРУМЕНТУ / БЕРЕЗЕНЬ 2024 РОКУ\n\nДля автоматизації можна використовувати не лише ключ API.\n\nУ вікі-сторінці «Trade Offer Manager» описано використання токена доступу сесії для окремих частин веб-API у випадках, коли окремого ключа API немає. Там також зазначено, що з кінця 2023 року для створення ключа потрібно підтвердження з мобільного пристрою. Розробник зазначає, що таке використання токена не підтримується версією Valve; це застаріла інформація з документації, а не результат реального тесту на обхід обмежень.\n\nОзнайомтеся з поясненням відповідального за підтримку ↗ архів 2026-09-24 ↗\n\nЛЮДСЬКА СТОРОНА / ІЛЮСТРАТИВНИЙ ПРИКЛАД ФІШИНГУ\n\nВсе ще граю.Вже викрито.\n\nПовідомлення від друга. Прохання проголосувати. Сторінка з подякою. Для гравця завдання виконано. Але зламаний сеанс може тривати й після цього моменту.\n\nНА ЕКРАНІ ПЛЕЄРА\n\nF\nРозповідь друга\n\n«Чи можете ви проголосувати за нашу команду?»\n\nЗапит надходить через чат Steam від знайомого акаунта. У цьому випадку пов’язана сторінка відкривається в браузері клієнта.\n\nПОЗА ПОЛЕМ ЗОРУ\n\nДовіра виникає ще до появи веб-сайту.\n\nЗламаний акаунт друга може додати довіри до фішингового посилання. Інтерфейс Steam, що оточує посилання, не підтверджує достовірність веб-сайту, на який веде посилання.\n\nЗНАЙОМИЙ ВІДПРАВНИК / ЗОВНІШНЄ МІСЦЕ ПРИЗНАЧЕННЯ\nБезпека облікового запису — це питання, яке слід вирішити перед продажем будь-якого товару.\n\nГравець не мав наміру створювати облікові дані для автоматизації або делегувати контроль. Повернення до гри не є доказом того, що обліковий запис є безпечним. Valve зберігає журнали сеансів, записи про створення API-ключів та дані про кореляцію пристроїв. А жертва — ні. Саме ця асиметрія і є проблемою відповідальності.\n\nДоступ до сеансів та типи облікових даних\n\nКлюч API та сесія входу — це окремі облікові дані з різними можливостями. Скасування ключа не призводить до припинення активної сесії. У власній документації Valve описано обидва ці елементи; Valve зберігає журнали, які покажуть, які саме облікові дані були активними на момент будь-якої спірної дії. Вимога полягає у розкритті саме цього запису — а не у висновках, вигаданих у ході розслідування. Документація розробника щодо роботи з токенами ↗ архів 2026-09-24 ↗ · Valve ключова документація ↗ архів 2026-09-15 ↗\n\n03 / ОФІЦІЙНИЙ РИНОК МАЄ СВОЮ ГРАНІЦЮ\n\nЦей предмет може бути рідкісним.Обмеження залишається в силі.\n\nЦіну, що перевищує встановлений ліміт, неможливо реалізувати шляхом розміщення одного оголошення на «Community Market» за цією повною ціною.\n\nОрієнтовна ціна продажу$5,000Змінити ціну, за яку виставлено товар\n$100$20,000\n\nІлюстрація опублікованого ліміту, а не оцінка або рекомендація щодо торгівлі.\n\nЛІМІТ РОЗМІЩЕННЯ≈ $1,800\nКРИШКА ГАМАНЦЯ≈ $2,000\n\nВище встановленого ліміту розміщення.\n\nКошти з гаманця не можна вивести на банківський рахунок. Ці обмеження породжують попит, який задовольняють сторонні ринки скінів: попит, що виникає внаслідок обмежень на розміщення оголошень та лімітів гаманців, тоді як власні правила Valve забороняють комерційним операторам його задовольняти.\n\nРинкові обмеження Steam ↗ архів 2026-09-21 ↗\n\n04 / В МЕЖАХ ЗОНИ ПІДТРИМКИ\n\nНам довірено дані.Відповідає за доступ.\n\nПолітика конфіденційності компанії Valve прямо передбачає передачу персональних даних стороннім постачальникам послуг технічної підтримки, якщо це необхідно для надання такої підтримки.\n\nГРАВЕЦЬРахунок та підтверджуючі документи\n→\nКЛАПАНПроцес відновлення\n→\nНАДАВЕЦЬ ПОСЛУГДелегований доступ\n\nПолітика конфіденційності, §5.2 ↗ · Згідно з власною політикою компанії Valve, стороннім особам надається доступ для технічної підтримки. Залишаються відкритими такі питання: які саме дозволи були надані, які існують журнали аудиту та що сталося, коли, як стверджується, цим доступом було зловжито.\n\n2015\nШкала була загальнодоступною\n\nValve визнала факт масового викрадення облікових записів та описала заходи захисту.\n\nValve публікація ↗архів 2026-08-09 ↗\n2015\nValve передала цю роботу на аутсорсинг — і про це заявила\n\nValve має невелику внутрішню команду керівників служби підтримки Steam і заявила про це «залучив кілька різних компаній» для забезпечення технічної підтримки (Erik Johnson, Valve, для Kotaku); пункт 5.2 її політики конфіденційності надає цим третім сторонам право доступу до даних користувачів. Який підрядник має доступ до відновлення облікового запису, Valve ніколи не розкривав — У дискусіях у спільноті згадуються такі постачальники, як Concentrix, але жоден із них не Valve-підтверджений. Відділ, робота якого була передана на аутсорсинг, існував ще за кілька років до будь-якого з наведених нижче визнань.\n\nKotaku: Valve щодо підтримки ↗архівувати 2025-07-11 ↗\n2023\nПерше зарахування\n\nКоманда Valve з CS:GO письмово бере на себе відповідальність за злом облікового запису, що стався через її власну процедуру звернення за допомогою, та скасовує обміни.\n\nВідкрити справу щодо аутсорсингу ↓\n2025\nДруге зарахування\n\nЧерез 33 місяці служба підтримки Steam повідомляє, що технічний спеціаліст «не дотримався нашої процедури, внаслідок чого ваш обліковий запис було відновлено на ім’я іншої особи». Той самий канал. Той самий результат.\n\nDexerto, 14 листопада 2025 р. ↗\n\nМАТЕРІАЛИ СПРАВИ / HFB ТА ЗВИНУВАЧЕННЯ У ВИКОРИСТАННІ АУТСОРСИНГУ\n\nШлях до входу — це сама підтримка Steam.Valve зазначив це в письмовій формі.\n\nУ відповіді служби підтримки, опублікованій на сайті Dexerto, команда Valve з CS:GO бере на себе відповідальність за злам облікового запису у процесі подання запиту на допомогу — через власний канал, а не через фішингову сторінку чи користувача. Активи було відновлено, а операції скасовано, що, як зазначає Valve, є засобом захисту, якого, за його словами, у інших жертв немає. За повідомленнями, запаси HFB становили $2,000,000+ в той день і $3,000,000+ у подальшому; Qkss програв $1,000,000+ таким самим чином і нічого не отримав.\n\nВІДПОВІДЬ СЛУЖБИ ПІДТРИМКИ / Опубліковано DEXERTO · 21 лютого 2023 року\n«зламано через запит на технічну підтримку, відповідальність за що бере на себе команда CS:GO»\nОзнайомтеся зі звітом та наведеним повідомленням ↗ архів 2025-08-18 ↗\n01 / ЯКИЙ КЛАПАН ВСТАНОВЛЕНО\nСаме власний канал підтримки став тим самим шляхом\n\nУ відповіді йдеться про зламаний обліковий запис та скасування пов’язаних з ним операцій. Valve скасував їх — отже, ці операції можна було скасувати. Оригінальний автентифікований квиток у цій колекції відсутній.\n\n02 / ЧОГО НЕ ВДАЛОСЯ ВИРІШИТИ ЗВІЛЬНЕННЯМИ\nЦі самі двері знову відчинилися в листопаді 2025 року\n\nПідрядник звільнив весь свій персонал служби підтримки Steam — про це повідомило видання Mzkshow з посиланням на Dexerto; це не було офіційним повідомленням Valve від компанії. Через тридцять три місяці Steam Support написав іншому колектору, що «технічний спеціаліст служби підтримки, який обробляв запит на допомогу, не дотримався нашої процедури, що призвело до відновлення вашого облікового запису на ім’я іншої особи». Це цитата з повідомлення Valve щодо того самого каналу.\n\nДруга госпіталізація, 14 листопада 2025 року ↗\n03 / ЩО ТАКЕ «ВІДКРИТЕ»\nValve ніколи не називав підрядника\n\nЦі джерела не вказують ані підрядника, ані місцезнаходження. Це не прогалина у звітності — це інформація, яку Valve не оприлюднила щодо того, хто мав доступ до облікових записів користувачів.\n\nСучасний опис цієї справи ↗\n\nТри питання, на які Valve не відповів: хто міг скасувати відновлення облікового запису, що виявив аудит доступу та що змінилося після цього.\n\nПізніші звинувачення, що містяться в збереженому архіві доказів\n\nДва дописи на Reddit за 2024 рік містять інформацію про подальші розслідування Mzkshow — випадок скасування блокування VAC у липні 2024 року та випадок з інвентаризацією $13,000 у грудні 2024 року. Це окремі інциденти, про які повідомляється окремо. Питання відповідальності в кожному з них однакове: хто мав права на обхід обмежень, що виявив аудит і що змінилося.\n\n14 липня 2024 року · повідомлено про одужання / VAC-випадок заборони ↗2 грудня 2024 року · зареєстровано $13,000 випадків з запасами ↗архів 2025-08-05 ↗Два збережені пости, рядки джерел та хеші ↓\n\n05 / СЛІДКУЙ ЗА ВТРАТОЮ\n\nБудь-яка сумапотрібен футляр.\n\nДесять випадків, червень 2022 року — березень 2026 року. Кожна цифра відповідає даним, опублікованим у зазначеному джерелі — $6,300,000, $2,000,000+, $1,000,000+, ≈$320,000, ≈$300,000, і аж до 288 євро. Valve зберігає журнал транзакцій, запис сеансу та аудиторський слід підтримки для кожної з них, але не надав жодного з них.\n\nКАНАЛ ПІДТРИМКИ21 червень 2022\n$2,000,000+\nHFB — the largest inventory in the game\n\nЗВІТ ПРО ОЦІНКУ ВАРТОСТІ ЗАПАСІВ · ЗБІЛЬШЕННЯ ДО $3M+ У ЛЮТОМУ 2023 ПІДСУМКИ\n\nСім сувенірних «Dragon Lores» та «Blue Gem Karambit» з номером #1; лише цей ніж коштує приблизно $1.26. Акаунт не використовувався три роки, автентифікатор залишався увімкненим; електронну адресу та пароль було змінено через процедуру відновлення, надану службою підтримки. Компанія «Valve» скасувала транзакції — та письмово підтвердила свою відповідальність. До скасування транзакції, за повідомленнями, вже було знято понад $200,000через market.csgo.com, який здійснює розрахунки готівкою та криптовалютою. Скасування повертає скін, а не гроші, які хтось уже переказав на рахунок. Відміна угоди також призвела до збою: покупець сховав свій «Souvenir Dragon Lore» у внутрішньоігровому сховищі, скрипт не зміг заглянути всередину цього контейнера, а Valve продублював предмет вартістю $130,000 під час скасування крадіжки — це було виявлено за ідентифікаторами предметів та повідомленнями спільноти, а в липні 2022, покупець отримав відшкодування від BUFF, а не від Valve.\n\nDexerto, день крадіжки ↗\nГАМАНЕЦЬ ТА ПОКУПКИ07 ЛИПНЯ 2022\n>$500\n44 disputed Market purchases\n\nЗАДЕКЛАРОВАНІ ВИТРАТИ З ГАМАНЦЯ · USD\n\nКористувач повідомляє про несанкціоновані покупки недорогих предметів у грі Dota 2 та незадовільну реакцію служби підтримки.\n\nОзнайомтеся зі скаргою та скріншотами за посиланням ↗\nВТРУЧАННЯ У РОБОТУ ПЛАТФОРМИ14 2022 серпня\n$6,300,000\nCS.Money — 19,000+ скіни з ботів\n\nОЦІНКА ВАРТОСТІ · ПЕРША ОЦІНКА $1.6M\n\nЗловмисники викрали файли мобільних аутентифікаторів торгових ботів торговельної платформи та очистили їх, переказавши частину викрадених коштів відомим трейдерам, щоб заплутати сліди. Дослідники з спільноти за лічені години склали карту акаунтів зловмисників 55. Valve нічого не скасував — сторонній сайт знаходиться поза межами Steam, повідомив той самий Steam, чиї запаси, торгова платформа API та система обліку стали об’єктом крадіжки від початку до кінця.\n\nПрочитайте сучасний опис подій ↗\nКАНАЛ ПІДТРИМКИПublikація: 21 ФЕВРАЛЬ 2023\n$1,000,000+\nQkss — ті самі двері, той самий актор, протилежна відповідь\n\nЗАДЕКЛАРОВАНА ВАРТІСТЬ ЗАПАСІВ\n\nЦе відбулося так само, як і у випадку з HFB: тим самим актором, через той самий запит до служби підтримки. Проблема з HFB була повністю вирішена за вісім місяців до цього. А з Qkss — ні. У опублікованих даних немає нічого, що відрізняло б ці два випадки, окрім чисельності аудиторії.\n\nDexerto про розслідування Mzkshow ↗\nКАНАЛ ПІДТРИМКИОПУБЛІКОВАНО 2023\n≈ $320,000\nСама інсайдерська торгівля — один рік такої діяльності\n\nРЕЗУЛЬТАТИ ДІЯЛЬНОСТІ ЗА ПРИБЛИЗНО ОДИН РІК · ЦЕ НЕ ОЦІНКА ВАРТОСТІ ЗАПАСІВ\n\nСлужба підтримки отримала доступ до історії облікового запису за останні 15 років: перший CD-ключ, перший електронний лист, перша картка — саме ті докази, яких вимагає процедура відновлення. Той, хто володіє базою даних, завжди виграє суперечку з тим, хто володіє обліковим записом. Один вкрадений M4A4 Howl з голограмами iBUYPOWER та Titan Katowice 2014 був проданий за $35,000 і в підсумку опинився у b1t з команди NAVI, який не мав можливості про це дізнатися. Відповіддю підрядника стало звільнення всіх співробітників, які працювали в службі підтримки Steam.\n\nEscorenews про це ж розслідування ↗\nГАМАНЕЦЬ ТА ПОКУПКИ09 DEC 2023\n€288\nВтрата гаманця попри двоступеневий захист\n\nTRUSTPILOT · ІНДЕКС ДЖЕРЕЛ 16\n\nРецензент повідомляє про злом облікового запису та відмову надати допомогу щодо витрат у Market. У експортованому файлі немає індивідуальної URL-адреси відгуку.\n\nПеревірити походження джерела ↗\nВІДНОВЛЕННЯ ОБЛІКОВОГО ЗАПИСУ02 DEC 2024\n$13,000\n«Матвій» — через два роки після звільнень\n\nОЦІНКА ЗАПАСІВ АВТОРА\n\nВідновлення доступу було надано особі, яка надала дані облікового запису, які сам власник не зміг підтвердити. Той самий шлях, той самий результат — після того, як підрядник ліквідував свою службу підтримки Steam.\n\nОзнайомтеся зі збереженим звинуваченням ↗\nВІДНОВЛЕННЯ ОБЛІКОВОГО ЗАПИСУ09 ТРАВЕНЬ 2025\n≈ $10,000\nВідновлення за допомогою чужого квитка\n\nЗАЯВЛЕНА ВТРАТА ТОВАРУ · Долари США\n\nКористувач із Квебеку стверджує, що служба підтримки скинула пароль і скасувала захист облікового запису на прохання іншої особи.\n\nПрочитайте скаргу, написану від першої особи ↗\nКАНАЛ ПІДТРИМКИ13 112025\n≈ $300,000\nHawkeye337 — і друге письмове зізнання від «Valve»\n\nПОВНА КОЛЕКЦІЯ HOLO «2014» З КАТОВИЦЬ\n\nЗловмисник вимагав 1 біткойна і почав переносити колекцію на Negevs, щоб знищити її. Steam Відповідь служби підтримки: «Технічний спеціаліст, який обробляв запит на допомогу, не дотримався нашої процедури, що призвело до відновлення вашого облікового запису на ім’я іншої особи». Через тридцять три місяці після першого визнання — та сама ситуація. Акаунт було відновлено за кілька годин після того, як ця тема стала популярною на X. У Qkss не було такої аудиторії.\n\nDexerto, 14 Nov 2025 ↗\nГАМАНЕЦЬ ТА ПОКУПКИ29 MAR 2026\n$50\nНесанкціоноване поповнення рахунку та ігри, отримані в подарунок\n\nTRUSTPILOT · ІНДЕКС ДЖЕРЕЛ 290\n\nРецензент заявляє про несанкціоновані витрати та відхилені запити на повернення коштів. У файлі експорту відсутня URL-адреса окремого відгуку.\n\nПеревірити походження джерела ↗\n\nДжерела та суми залишаються такими, як зазначено в кожному джерелі. Valve зберігає журнали транзакцій, записи сеансів та аудиторський слід підтримки для кожного з цих випадків. Надайте їх. Збережений допис на Reddit не вирішує питання — вирішують власні записи Valve.\n\nКОЛЕКЦІЯ / ПІСЛЯ ПЕРЕВІРКИ\n\n231,829 облікових записів на продаж.Valve містить журнали для кожного з них.\n354 → 201\nВідгуки на Trustpilot\n\nВидалено 153 дублікати рядків. URL-адреси окремих оглядів не були збережені під час експорту.\n\n231,829\nSteam перелік облікових записів\n\n33,509 класифікується як «самостійно зареєстрований»; 198,320 під маркою «колекціонер-крадій». Оголошення не є завершеними угодами.\n\nАудит колекції ↓Пошук у архіві вихідного коду ↗",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Ваш обліковий запис.Їхній доступ.Хто відповідає?"
          },
          {
            "level": 2,
            "id": null,
            "text": "Автоматизація маєдокументальний ланцюжок."
          },
          {
            "level": 3,
            "id": null,
            "text": "ArchiSteamFarm"
          },
          {
            "level": 2,
            "id": null,
            "text": "Яка клавішаПро що саме йдеться?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Особистий ключ Web API"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ключ Web API видавця"
          },
          {
            "level": 3,
            "id": null,
            "text": "OpenID / токени сеансу"
          },
          {
            "level": 3,
            "id": null,
            "text": "Для автоматизації можна використовувати не лише ключ API."
          },
          {
            "level": 2,
            "id": null,
            "text": "Все ще граю.Вже викрито."
          },
          {
            "level": 3,
            "id": "session-hidden-title",
            "text": "Довіра виникає ще до появи веб-сайту."
          },
          {
            "level": 2,
            "id": null,
            "text": "Цей предмет може бути рідкісним.Обмеження залишається в силі."
          },
          {
            "level": 2,
            "id": null,
            "text": "Нам довірено дані.Відповідає за доступ."
          },
          {
            "level": 3,
            "id": null,
            "text": "Шкала була загальнодоступною"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve передала цю роботу на аутсорсинг — і про це заявила"
          },
          {
            "level": 3,
            "id": null,
            "text": "Перше зарахування"
          },
          {
            "level": 3,
            "id": null,
            "text": "Друге зарахування"
          },
          {
            "level": 3,
            "id": null,
            "text": "Шлях до входу — це сама підтримка Steam.Valve зазначив це в письмовій формі."
          },
          {
            "level": 4,
            "id": null,
            "text": "Саме власний канал підтримки став тим самим шляхом"
          },
          {
            "level": 4,
            "id": null,
            "text": "Ці самі двері знову відчинилися в листопаді 2025 року"
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve ніколи не називав підрядника"
          },
          {
            "level": 2,
            "id": null,
            "text": "Будь-яка сумапотрібен футляр."
          },
          {
            "level": 3,
            "id": null,
            "text": "HFB — the largest inventory in the game"
          },
          {
            "level": 3,
            "id": null,
            "text": "44 disputed Market purchases"
          },
          {
            "level": 3,
            "id": null,
            "text": "CS.Money — 19,000+ скіни з ботів"
          },
          {
            "level": 3,
            "id": null,
            "text": "Qkss — ті самі двері, той самий актор, протилежна відповідь"
          },
          {
            "level": 3,
            "id": null,
            "text": "Сама інсайдерська торгівля — один рік такої діяльності"
          },
          {
            "level": 3,
            "id": null,
            "text": "Втрата гаманця попри двоступеневий захист"
          },
          {
            "level": 3,
            "id": null,
            "text": "«Матвій» — через два роки після звільнень"
          },
          {
            "level": 3,
            "id": null,
            "text": "Відновлення за допомогою чужого квитка"
          },
          {
            "level": 3,
            "id": null,
            "text": "Hawkeye337 — і друге письмове зізнання від «Valve»"
          },
          {
            "level": 3,
            "id": null,
            "text": "Несанкціоноване поповнення рахунку та ігри, отримані в подарунок"
          },
          {
            "level": 2,
            "id": null,
            "text": "231,829 облікових записів на продаж.Valve містить журнали для кожного з них."
          },
          {
            "level": 3,
            "id": null,
            "text": "Відгуки на Trustpilot"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam перелік облікових записів"
          }
        ],
        "links": [
          "https://phishdestroy.io/live-intel/?category=steam",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/lzt.market.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-evidence-lzt.json",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://github.com/JustArchiNET/ArchiSteamFarm/blob/main/ArchiSteamFarm/ArchiSteamFarm.csproj",
          "https://github.com/JustArchi",
          "https://github.com/renovate[bot]",
          "https://github.com/JustArchi-ArchiBot",
          "https://github.com/dependabot-preview[bot]",
          "https://github.com/renovate-bot",
          "https://github.com/actions-user",
          "https://github.com/dependabot-support",
          "https://github.com/Abrynos",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/automation-map.json",
          "https://phishdestroy.io/steam_dossier/uk/output_steam_network/network.html",
          "https://phishdestroy.io/steam_dossier/uk/output_steam_network/raw_data.json",
          "https://phishdestroy.io/steam_dossier/uk/#proxy-bypass-explainer",
          "https://partner.steamgames.com/doc/webapi_overview/auth",
          "http://web.archive.org/web/20260915025812/https://partner.steamgames.com/doc/webapi_overview/auth",
          "https://partner.steamgames.com/doc/webapi/ISteamUserAuth",
          "http://web.archive.org/web/20260829124950/https://partner.steamgames.com/doc/webapi/ISteamUserAuth",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "http://web.archive.org/web/20260924181824/https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://store.steampowered.com/privacy_agreement/",
          "https://store.steampowered.com/oldnews/19618",
          "http://web.archive.org/web/20260809125516/https://store.steampowered.com/oldnews/19618",
          "https://kotaku.com/valve-explains-why-steam-customer-service-is-still-terr-1736988223",
          "http://web.archive.org/web/20250711004653/https://kotaku.com/valve-explains-why-steam-customer-service-is-still-terr-1736988223",
          "https://www.dexerto.com/counter-strike-2/valve-saves-hacked-cs2-player-threatened-with-ransom-over-300000-of-rare-stickers-3283135/",
          "https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "http://web.archive.org/web/20250818113925/https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "https://lis-skins.com/ru/blog/krupneisaia-mosenniceskaia-sxema-v-istorii-steam/",
          "https://www.reddit.com/r/cs2/comments/1e38jo4/stealing_accounts_and_removing_vac_bans_a_new/",
          "https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "http://web.archive.org/web/20250805141942/https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/outsourcing-archive-records.json",
          "https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "https://escorenews.com/en/csgo/news/44087-valve-steam-support-employee-accused-of-selling-inactive-accounts-inventories-worth-six-figures-b1t-has-one-of-these-skins",
          "https://phishdestroy.io/steam_dossier/uk/PART2_RESEARCH.md",
          "https://www.reddit.com/r/GlobalOffensive/comments/1h56shi/steam_support_is_stealing_accounts/",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/design-review/part2/quality-review.json",
          "https://phishdestroy.io/steam_dossier/uk/steam_evidence_archive.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/uk/investigation_part2.content.json",
      "export_json_sha256": "45f7fe44daa9a96b819820f971c44ce30fba7c0bb886927b5dec3d94c388faf1"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "uk/legal_analysis.html",
      "language": "uk",
      "title": "Їхні умови, ваші права — Досьє «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/uk/legal_analysis",
      "source_html_sha256": "bde0139cd0cfeaa775222bf2575343f73a7e5daed07c4462e07de2fcd65dfa31",
      "exported_at": "2026-09-29T00:19:30.102Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "legal_analysis.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/uk/legal_analysis.pdf?v=print-20260929-v5",
        "sha256": "b6904b78afb49c1aabf39b98d0c7cb66ae35385617ed237d0988e5863974ca01",
        "bytes": 114159,
        "pages": 8
      },
      "integrity": {
        "signed_object": "legal_analysis.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "legal_analysis.content.json.asc",
        "digest_file": "legal_analysis.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify legal_analysis.content.json.asc legal_analysis.content.json",
          "sha256sum -c legal_analysis.content.json.sha256"
        ]
      },
      "content": {
        "text": "Юридичний та економічний звіт\nЮридичний аналіз — Умови надання послуг та дотримання нормативних вимог\n\nЇхні умови. Ваші права.\n\nЩО ДОКАЗУЄ ЦЕЙ РОЗДІЛ\n\nЦей судово-правовий аудит оцінює договірну асиметрію між корпорацією «Valve» та користувачами Steam у ключових юрисдикціях. У ньому встановлюється, як відклична ліцензія на підписку позбавляє споживачів передбаченого законом права власності, аналізується судова практика Європейського суду щодо вичерпання прав на перепродаж цифрових об’єктів, а також досліджується дотримання вимог Закону про цифрові послуги (DSA) та статті 15. Закону про захист прав споживачів у цифровій економіці (GDPR). Аналіз демонструє, як автоматизовані механізми забезпечення дотримання вимог діють без можливості ефективного оскарження, тоді як ринкові комісії платформ систематично вилучають економічну цінність з кожної транзакції між користувачами.\n\n← Повернутися до огляду для керівництва\n\nУ цьому звіті наведено правовий, економічний та технічний аналіз розбіжностей між заявленими правилами платформи «Steam» та позицією споживача: автоматизоване забезпечення дотримання правил із обмеженими можливостями оскарження та всеосяжний корпоративний контроль над цифровими активами. Дані наводяться із зазначенням джерела; у випадках, коли джерело даних не вдалося встановити, такі дані було опущено.\n\nВектор 1\n\nЗаміна поняття «право власності» на відкличну ліцензію, щоб цифрові активи можна було вилучити відповідно до угоди.\n\nВектор 2\n\nСистема автоматичного застосування санкцій (VACNet), щодо заборон якої, як зазначено на сайті Steam, адміністрація не може скасувати.\n\nВектор 3\n\nКонтроль за рахунками та активами у поєднанні з ринковою комісією CS2 від «15%» (5%, Steam та 10% — комісія видавця), яка при кожному перепродажу зменшує загальну вартість екосистеми.\n\nАсиметрія термінів\nВідмова від відповідальності та відклична ліцензія\n2.1 Модель «передплати» проти прав власності\n\nУ розділі «2» Угоди про підписку на «Steam» користувачам надається лише особиста, невиключна, непередавальна та відклична ліцензія. Згідно з умовами угоди, компанія «Valve» має право в будь-який час закрити облікові записи, а невикористані залишки на гаманцях Steam можуть бути анульовані.\n\n2.2 Ілюзія повернення коштів проти Директиви ЄС про права споживачів\nНормативно-правова база\tМеханізм повернення коштів\tОбмеження\nEU Consumer Rights Directive\tUnconditional 14-day right of withdrawal on digital content\tWaived if download begins with explicit consumer consent\nSteam SSA\t14 days / under 2 hours played\tValve may deny at its discretion for \"abuse\"\nОцінка\n\nValve ЄС встановлює для права на відмову від угоди, передбаченого законом про захист прав споживачів (14-), обмеження у вигляді власного «14 днів / 2 годин», яке приймається в момент завантаження, перш ніж товар можна буде оцінити. Ця політика звужує — а не розширює — передбачене законом право; чи є це законним — це питання, яке має вирішувати компетентний орган, а не висновок, який тут стверджується.\n\nСудові спори\nВторинний ринок та антимонопольне законодавство\nUFC Que Choisir проти «Valve» — Франція\n2019\nСуд у Парижі: доктрина вичерпання прав поширюється на цифрові ігри — перепродаж є законним\n2022 жовтня\nАпеляційний суд Парижа скасував рішення\n23 2024 жовтня\nКасаційний суд (Верховний суд): відеоігри є «складними творами» відповідно до Директиви про інформаційне суспільство, а не програмним забезпеченням. Цифровий перепродаж заборонено. Переважає «Valve».\nАнтимонопольна справа щодо Wolfire Games — Сполучені Штати (У справі «Valve», № 2:21-cv-00563)\n\nПоложення про режим найбільшого сприяння (PMFN) платформи Valve забороняє розробникам продавати ключі Steam дешевше на будь-якій іншій платформі. Конкуруючі магазини — навіть ті, що стягують комісію 12% на відміну від Valve, яка застосовує ставку 30% — не можуть передавати цю економію споживачам.\n\n336загальна кількість співробітників компанії «Valve» (2021). Джерело: розсекречені матеріали досудового розслідування.\n79співробітники, які керують усією платформою Steam. Джерело: розсекречені матеріали досудового розслідування.\n$3.5Mчистий прибуток на одного працівника. Джерело: розсекречені матеріали досудового розслідування.\n\nЗгідно з оприлюдненими матеріалами досудового розслідування $8.5B валового доходу за 2021 щодо співробітників компанії «336». Це 79-команда «Steam» обробляли запити на підтримку 373,000та щоденні запити на підтримку, перенаправляючи їх через аутсорсовані автоматизовані кол-центри.\n\nДОКАЗОВИЙ МАТЕРІАЛ, ЩО НЕ ПІДЛЯГАЄ ЗАСЕКРЕЧЕННЮ · W.D. ШТАТ ВАШИНГТОН. СПРАВА № 2:21-CV-00563Внутрішня інформаційна записка\n\nТім Свіні (генеральний директор Epic Games) до Геба Ньюелла: «Чому Steam досі забирає 30% від валового доходу, якщо обробка платежів коштує 2–5%, а пропускна здатність CDN — $0.002/за ГБ? Якщо відняти найпопулярніші ігри 25 на Steam, я готовий побитися об заклад, що Valve отримав більше прибутку від більшості наступних ігор 1,000, ніж самі розробники».\n\nВнутрішній лист Скотта Лінча (операційний директор корпорації «Valve») на ім’я Геба Ньюелла: «Ти злишся, брате?»\n\nЗаперечення щодо показань під присягою (Bloomberg, 2026): Відповідно до правила 30(b)(1) під час дачі показань під присягою Гейб Ньюелл заявив, що «Компанія „Valve“ не має політики чи практики, згідно з якими вона диктує ціни стороннім розробникам програмного забезпечення на інших платформах». Позивачі пред’явили Ньюелу внутрішні службові записки Valve, які свідчили про активне регулювання цін та погрози виключення з каталогу розробникам, які встановлювали нижчі ціни в магазинах-конкурентах. Наприкінці березня 2026, Федеральний суд відхилив клопотання Valve про винесення рішення без розгляду справи по суті, направивши колективний позов розробників 32,000-на розгляд присяжних.\nЛистопад 2024\n\nЗатверджено колективний позов щодо ~ Розробники32,000 які сплачували комісійні з січня 2017,, а також паралельний колективний позов споживачів.\n\nЗаявлена сума збитків\n\n$3.1B\nПотрійне покарання згідно з антимонопольним законодавством США = $9.3B можливе опромінення.\n\nЧервень 2026: У новому позові стверджується, що компанії «Microsoft» та «Valve» уклали картельну угоду, спрямовану на обмеження конкуренції у сфері розповсюдження комп’ютерних ігор.\n\nФінансові злочини та протидія відмиванню грошей: офіційне зарахування\nValve Офіційне зізнання: Worldwide Fraud Liquidations (28 жовтня 2019)\n\n28 жовтня 2019, Valve офіційно припинив торгівлю та перепродаж на торговельних майданчиках щойно придбаних ключів від контейнерів у грі Counter-Strike. У своєму офіційному публічному повідомленні (blog.counter-strike.net/2019/10/26113), компанія «Valve» письмово визнала, що створена нею віртуальна економіка перетворилася на міжнародний центр відмивання грошей:\n\n«Раніше більшість угод з ключами, які ми спостерігали, відбувалися між законними клієнтами. Однак останнім часом міжнародні шахрайські мережі почали використовувати ключі CS:GO для реалізації своїх доходів. На даний момент вважається, що майже всі покупки ключів, які згодом стають предметом торгівлі або продажу на торговельних майданчиках, мають шахрайське походження».\n\nНормативно-правові рамки: Це зізнання стало наслідком офіційного ультиматуму, висунутого Комісією з азартних ігор штату Вашингтон (WSGC) компанії «Valve», а також липневих наказів про припинення діяльності (2016), виданих головним юрисконсультом компанії «Valve» Карлом Квакенбушем (Karl Quackenbush) щодо доменів, пов’язаних з азартними іграми на сайті 23 (зокрема CSGO Lotto, CSGOLounge та OPSkins) — лише після того, як кримінальне розслідування щодо азартних ігор поставило під загрозу діяльність платформи.\n\nЮрисдикція\nПравовласник у Росії, з яким користувач не може зв’язатися\n\nУ Договорі про підписку компанія «Valve» постає як сторона, яка майже нічого не зобов’язана і до якої ніхто не може звернутися: обмеження є постійними, апеляції відхиляються, а доступ до цілих територій блокується одним реченням про «регіони, що підпадають під санкції». На противагу такій позиції — дії компанії «Valve», коли на кону стоять її власні комерційні інтереси в юрисдикції, яку вона в інших випадках вважає складною.\n\nValve v. Touch Skins — досудова претензія щодо прав інтелектуальної власності, Росія\n1 Вересень 2026\nКомпанія «Valve» через російську юридичну фірму «Меллінг, Войтішкін і партнери», надсилає попередню вимогу до операторів Скіни для сенсорних екранів, великий набір скінів для CS2, поштою «Роспошта» та електронною поштою.\nПідстави\nТри групи ймовірних порушень: виключні права на програмне забезпечення; права на зовнішній вигляд скінів зброї, ножів та рукавичок; а також торговельні марки компанії «Valve». Поведінка операторів характеризується як умисна та тривала.\nПопит\nНегайно припиніть роботу та видаліть усю інфраструктуру — програмне забезпечення вихідний код, веб-сайти та сторінки в соціальних мережах — у разі невиконання цієї умови компанія «Valve» залишає за собою право звернутися до російського суду з позовом щодо значна грошова компенсація та передати це питання на розгляд правоохоронні органи для проведення кримінальної експертизи.\nРезультат\nОтримавши лист, платформа оголосила про припинення своєї діяльності. Як повідомляється, це перший випадок, коли організація «Valve» застосувала правові заходи проти розробника програм для зміни зовнішності в Росії.\n\nПро це повідомили аналітик даних Максим «GabeFollower» Полетаєв (X, ~11 вересня 2026) та російська ігрова преса. Йдеться про досудову претензію, а не про поданий позов; номер справи не оприлюднено. У цій статті інформація подається так, як її навели джерела, а не як офіційний судовий документ. Джерела: dota2.ru архів 2026-09-24 ↗ · Шазу.\n\nТа сама юрисдикція, інший напрямок\n\nValve добре знайома з російською правовою та нормативною системою. Вона відповідає вимогам Роскомнадзору: на вимогу регулятора було видалено сторінки спільнот 260та Steam, що містили заборонені матеріали, а «Роскомнадзор» публічно заявив, що сайт Steam відповідає вимогам законодавства. Російський закон про «посадкові сторінки» (Федеральний закон 236-FZ, що діє з 2022), вимагає від великих іноземних інтернет-платформ, які обслуговують російських користувачів, відкрити представництво в Росії та створити обліковий запис для зв’язку з «Роскомнадзором». Valve не тільки виконує розпорядження регулятора про видалення контенту, а й, відтепер, залучає російських юристів та використовує загрозу звернення до російських судів для захисту своїх скінів як об’єктів інтелектуальної власності.\n\nОтже, платформа є доступною, дієвою та відстоює свої права саме в тому, що стосується її доходів. На противагу цьому — ситуація з користувачем: платному клієнту з регіону, на який накладено санкції, повідомляють, що співпраця припинена, доступ до спільноти заблоковано доти, доки 2038, квиток не буде закрито, і не існує жодного форуму, де це рішення можна було б оскаржити — «Вони з радістю брали мої гроші та обробляли мої транзакції», при цьому повернення коштів з того самого облікового запису з тієї самої іранської IP-адреси було схвалено роком раніше (r/pcgaming, 4 2026 серпня; більше листів із вимогою дотримання законодавства у виставка «Карткова економіка»). «Valve» задіює весь механізм національної правової системи для захисту скіна; при цьому користувачеві, який придбав скіни, не надається жодної можливості оскарження.\n\nValve розглядає цю юрисдикцію як таку, в межах якої вона може діяти та дотримуватися її вимог, коли йдеться про інтереси компанії «Valve» — залучення російських юристів, загроза судових рішень російських судів, виконання наказів «Роскомнадзору» про видалення контенту — водночас вважаючи свої зобов’язання перед користувачами цього ринку, як і будь-якого іншого, такими, що взагалі не підпадають під жодну процедуру. Вона виступає правовласником, коли йдеться про її доходи, і недосяжною стороною, коли йдеться про права користувачів.\n\nДжерела: ТАСС (RKN: відповідає вимогам Steam) · Федеральний закон «236-» ФЗ.\n\nПравовий опортунізм\nКапітуляція щодо арбітражної клаузули\n2023 — напад\n\nЮридичні фірми («Zaiger LLC», «Mason LLP») залучили тисячі користувачів через соціальні мережі та одночасно подали десятки тисяч індивідуальних арбітражних позовів.\n\nРозкриття інформації про компанію Valve\n\n$225M+\nу вигляді арбітражних реєстраційних зборів, що не підлягають поверненню, ще до розгляду справи по суті. Розраховано відповідно до Правил споживчого арбітражу Американської арбітражної асоціації (AAA) та Додаткових додатків щодо масового арбітражу. Позивачі, яких представляють компанії Zaiger LLC та Mason LLP, подали близько75,000 індивідуальних арбітражних позовів проти корпорації «Valve» (паралельно з антимонопольними позовами у справі Wolfire Games LLC та ін. проти корпорації «Valve», Справа № 2:21-cv-00563-JCC, W.D. (Вашингтон). Згідно з тарифами ААА на споживчі послуги, відповідач-підприємець сплачує неповернуті адміністративні збори за розгляд справи та застави за призначення арбітра в розмірі приблизно $3,000+ за кожну окрему справу (75,000 подань × $3,000 = приблизно $225млн у вигляді попередніх процесуальних зобов’язань). Див. юридичні звіти Bloomberg Law та Reuters щодо ризиків масового арбітражу у сфері технологій (2023–2024).\n\nПеріод\tМеханізм вирішення спорів у SSA\tСпостережуваний ефект\tРезультат\nBefore Sep 2024\tMandatory individual arbitration + class-action waiver\tIndividual litigation becomes economically irrational for users\tMass arbitration → $225M fee threat\nAfter Sep 2024\tDisputes in King County, WA courts only\tArbitration costs are avoided; cases consolidate in a single forum\tClass actions now possible\nВисновок\n\nПротягом понад десяти років SSA вимагала від користувачів відмовитися від права на розгляд справи судом присяжних на користь індивідуального арбітражу. Після того як масові звернення до арбітражу зробили цей механізм фінансово обтяжливим для компанії «Valve», до SSA були внесені поправки, які передбачали передачу спорів до судів округу Кінг. Ця зміна була запроваджена без надання користувачам реальної можливості відмовитися від неї; альтернативою згоді було втратити доступ до придбаних цифрових активів через видалення облікового запису.\n\nАлгоритмічне забезпечення дотримання вимог\nVACNet, презумпція вини та помилкові позитивні результати\n«2023» за жовтень — AMD Anti-Lag+\n\nОновлення драйвера AMD (версія 23.10.1) активувало функцію Anti-Lag+ у грі CS2, яка перехоплювала функції ігрових DLL-файлів. Система VAC розцінила це як введення чіт-коду та наклала довічні блокування на тисячі законних користувачів, перш ніж втрутилася компанія Valve.\n\n2023, грудень — висока роздільна здатність (DPI)\n\nГравці з показником DPI понад 10,000, які швидко обертали камеру, отримали довічні бани. Система VACNet не змогла відрізнити фізичний рух миші від чіту «spinbot».\n\nКатегорія підтримки\tЗаявлений час відгуку\tФактичний результат\nRefund requests\t50 min – 1.5 hr\tAutomatic approval (<14 days, <2 hours played)\nAccount security / recovery\t3–12 hours\tDepends on documentation provided\nContesting a VAC ban\tForm response\tComplete refusal. Support cannot reverse VAC decisions. The ban is permanent.\nОфіційна політика компанії «Valve»\n\n«Заборони VAC є постійними, не підлягають обговоренню і не можуть бути скасовані службою підтримки Steam».\n\nЧерез той самий канал підтримки, через який було накладено заборону, надходить і відмова у перегляді рішення: Steam. Служба підтримки заявляє, що не може скасувати рішення VAC. Для користувача вердикт алгоритму є остаточним результатом.\n\nЕкономіка перепродажу\nКонтроль над віртуальними активами та комісія за перепродаж\nКомісія за продаж на ринку «15%» CS2 — сума, що вираховується при кожному повторному продажу\nІтерація\tЗалишок коштів покупця\tПродавець отримує\t«Burned» (15%)\n1\t$100.00\t$85.00\t$15.00\n2\t$85.00\t$72.25\t$12.75\n3\t$72.25\t$61.41\t$10.84\n10\t$23.16\t$19.68\t~$3.47\nTotal\t$100 → dust\tValve collects the 15% fee on each resale. Users must add new money to keep trading.\nЗміна правил обміну CS2 — жовтень 2025\n\nБез попереднього повідомлення компанія «Valve» змінила правила контракту на обмін у CS2, щоб забезпечити гарантоване отримання рідкісних ножів та рукавичок в обмін на предмети якості «Covert». Ціни на ножі впали, ціни на предмети якості «Covert» різко зросли, після чого на ринку почалися панічні розпродажі.\n\nКомпанія Valve посилається на статтю 7 Закону про соціальне страхування (SSA) — вона не несе відповідальності за зміни в правилах платформи. Користувачі беруть на себе ризик у економіці, правила якої Valve можуть змінюватися без попередження та без компенсації. Розмір заявлених збитків у масштабах ринку є предметом суперечок і не наводиться тут без посилання на першоджерело.\n\nРеакція європейських регуляторних органів\nUOKiK, DSA та Закон про цифрову справедливість\nUOKiK — Польща, 2024 травня\n\nАнтимонопольний орган Польщі (UOKiK) розпочав офіційне антимонопольне провадження проти корпорації «Valve» та п’яти вітчизняних видавців і дистриб’юторів ігор щодо ймовірного узгодження цін, обмежувальних положень про цінову рівність та практики геоблокування, що змушували польських споживачів платити за цифрові ігри на 20% більше, ніж на сусідніх ринках ЄЕЗ. У рамках антимонопольного розслідування інспектори UOKiK та поліція провели раптові обшуки та огляди доказів у польських офісах місцевих видавців та дистриб’юторів-партнерів (а не у філіях «Valve», оскільки «Valve» не має юридичної особи в Польщі). Потенційний штраф, передбачений законодавством: до 10% річного обороту. Джерело: Офіційне повідомлення UOKiK: «Голова UOKiK порушив провадження проти компанії «Valve» та розробників ігор», травень 2024.\n\nЗакон про цифрові послуги (DSA)\n\nВимагає прозорості в процесі автоматизованої модерації. На сайті Steam не оприлюднюються дані щодо помилкових спрацьовувань (false-positive) та пропущених спрацьовувань (false-negative) для VACNet, а в каналі підтримки зазначено, що рішення VAC не підлягають скасуванню.\n\nЗакон про цифрову справедливість — 2026\n\nОчікувані положення: стабільний доступ до платного контенту, заборона використання «темних шаблонів» під час відмови від прав, визнання прав власності на цифрові активи та захист від остаточної конфіскації майна.\n\nВисновок\nВиявлені розбіжності між правилами та записами\n1\n\nРозрив у рівні власності. Користувачі сплачують повну вартість ліцензії, яку, згідно з угодою, компанія «Valve» має право анулювати. Верховний суд Франції (жовтень 2024) постановив, що перепродаж цифрових продуктів не підлягає захисту, закріпивши цю позицію в законодавстві.\n\n2\n\nАлгоритмічне забезпечення дотримання вимог. Система VACNet наклала необґрунтовані заборони (драйвери AMD, випадки з високим DPI). Служба підтримки Steam заявляє, що не може скасувати рішення VAC, отже, остаточне слово залишається за алгоритмом.\n\n3\n\nЕкономія на комісіях. Комісія за продаж на ринку «15%» CS2 (5% Steam + 10% — комісія видавця) знижує вартість товару при кожному повторному продажу, а правила платформи можуть змінюватися без попередження; відповідно до Угоди про надання послуг (SSA) компанія «Valve» не несе відповідальності за такі зміни.\n\n4\n\nАрбітражна клаузула вилучена. У вересні SSA скасувала обов’язковий арбітраж 2024, після того, як внаслідок масового подання позовів компанія Valve зазнала витрат у розмірі приблизно225млн доларів. Користувачам не було надано жодної реальної можливості відмовитися від цих змін.\n\n5\n\nВибіркова юрисдикція. Valve залучила російських юристів (Melling, Voitishkin & Partners) і погрожувала судовим розглядом у Росії проти компанії Touch Skins, водночас вважаючи свої зобов’язання перед користувачами того самого ринку такими, що виходять за межі будь-якого судового розгляду. Компанія «Valve» виступає правовласником, коли йдеться про її комерційні інтереси, і стає недосяжною стороною, коли йдеться про права користувачів.\n\n← Частина I: Обхід проксі-серверів та азартні ігриЧастина II: Доступ та підзвітність →\n\nЮридичні джерела та матеріали судових справ цитуються із посиланням на їхніх оригінальних видавців та репозитарії. Права власності на вихідні документи не заявляються.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Юридичний аналіз — Умови надання послуг та дотримання нормативних вимог"
          },
          {
            "level": 2,
            "id": null,
            "text": "Відмова від відповідальності та відклична ліцензія"
          },
          {
            "level": 3,
            "id": null,
            "text": "2.1 Модель «передплати» проти прав власності"
          },
          {
            "level": 3,
            "id": null,
            "text": "2.2 Ілюзія повернення коштів проти Директиви ЄС про права споживачів"
          },
          {
            "level": 2,
            "id": null,
            "text": "Вторинний ринок та антимонопольне законодавство"
          },
          {
            "level": 3,
            "id": null,
            "text": "UFC Que Choisir проти «Valve» — Франція"
          },
          {
            "level": 3,
            "id": null,
            "text": "Антимонопольна справа щодо Wolfire Games — Сполучені Штати (У справі «Valve», № 2:21-cv-00563)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve Офіційне зізнання: Worldwide Fraud Liquidations (28 жовтня 2019)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Правовласник у Росії, з яким користувач не може зв’язатися"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve v. Touch Skins — досудова претензія щодо прав інтелектуальної власності, Росія"
          },
          {
            "level": 3,
            "id": null,
            "text": "Та сама юрисдикція, інший напрямок"
          },
          {
            "level": 2,
            "id": null,
            "text": "Капітуляція щодо арбітражної клаузули"
          },
          {
            "level": 2,
            "id": null,
            "text": "VACNet, презумпція вини та помилкові позитивні результати"
          },
          {
            "level": 2,
            "id": null,
            "text": "Контроль над віртуальними активами та комісія за перепродаж"
          },
          {
            "level": 3,
            "id": null,
            "text": "Комісія за продаж на ринку «15%» CS2 — сума, що вираховується при кожному повторному продажу"
          },
          {
            "level": 3,
            "id": null,
            "text": "Зміна правил обміну CS2 — жовтень 2025"
          },
          {
            "level": 2,
            "id": null,
            "text": "UOKiK, DSA та Закон про цифрову справедливість"
          },
          {
            "level": 2,
            "id": null,
            "text": "Виявлені розбіжності між правилами та записами"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/uk/#briefing-heading",
          "https://dota2.ru/news/67707-valve-cerez-uristov-napravila-krupnoj-rossijskoj-skincendzer-platforme-trebovanie-o-prekrasenii-deatelnosti/",
          "http://web.archive.org/web/20260924181657/https://dota2.ru/news/67707-valve-cerez-uristov-napravila-krupnoj-rossijskoj-skincendzer-platforme-trebovanie-o-prekrasenii-deatelnosti/",
          "https://shazoo.ru/2026/09/12/190508/valve-cerez-rossiiskix-iuristov-dobilas-zakrytiia-krupnogo-skinceindzera-dlia-cs2",
          "https://www.reddit.com/r/pcgaming/comments/1vf24lu/warning_to_all_gamersexpats_steam_took_my_money/",
          "https://phishdestroy.io/steam_dossier/uk/card_economy.html#asymmetry",
          "https://tass.ru/obschestvo/23235387",
          "https://base.garant.ru/401414628/",
          "https://uokik.gov.pl/postepowanie-wyjasniajace-w-sprawie-valve-i-dystrybutorow-gier",
          "https://phishdestroy.io/steam_dossier/uk/",
          "https://phishdestroy.io/steam_dossier/uk/investigation_part2.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/uk/legal_analysis.content.json",
      "export_json_sha256": "221268de3b7e4c9d827b0575bd6f8270e1892d25cc066a7c00c5e7124146fd83"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "uk/license_disclaimer.html",
      "language": "uk",
      "title": "Ліцензія · Права · Відмова від відповідальності — PhishDestroy",
      "source_url": "https://phishdestroy.io/steam_dossier/uk/license_disclaimer",
      "source_html_sha256": "9cbf3239e0a4dac6d4c7d1bf82a2aeeede96899655c2eb4bd4eb7986d2043956",
      "exported_at": "2026-09-29T00:19:31.946Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "license_disclaimer.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/uk/license_disclaimer.pdf?v=print-20260929-v5",
        "sha256": "3e9d73961de6da790d4b479eec9e8251e83d87870e0c5dad26001d7cee265ca0",
        "bytes": 121369,
        "pages": 11
      },
      "integrity": {
        "signed_object": "license_disclaimer.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "license_disclaimer.content.json.asc",
        "digest_file": "license_disclaimer.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify license_disclaimer.content.json.asc license_disclaimer.content.json",
          "sha256sum -c license_disclaimer.content.json.sha256"
        ]
      },
      "content": {
        "text": "PHISHDESTROYСудово-медична експертиза · Valve / Steam\nЛіцензія · Права · Відмова від відповідальності\nЛіцензія та юридичне застереження — Передача у суспільний надбання\n\nУсі права віддався людству.\n\nЩО ДОКАЗУЄ ЦЕЙ РОЗДІЛ\n\nЦей документ встановлює умови беззастережного переведення до публічного домену (CC0 1.0 Universal) та умови ліцензування програмного забезпечення за ліцензією MIT, що регулюють роботу досьє PhishDestroy Steam. Усі результати криміналістичної експертизи, набори даних, що мають доказове значення, мережеві графіки та аналітичні методики безповоротно передаються у публічний домен для необмеженого використання в регуляторних, юридичних та наукових цілях у всьому світі.\n\n← Повернутися до огляду для керівництва\n\nPhishDestroy відмовляється від усіх прав на цей матеріал — від права на його відтворення, продаж та зазначення свого імені. Далі наводяться два документи, викладені в єдиному стилі: відкритий лист до Valve, написаний так, як ми зазвичай пишемо, та офіційна відмова від прав, складена для органу, який займатиметься подальшою реалізацією цієї ініціативи.\n\nРозслідування · Корпорація «Valve» / SteamПублічна версія — без терміну дії, без можливості скасування\nВІДМІНЕНО\nРозділ IЛіцензія — власне юридична частина, але з людським підходом\n\nPhishDestroy відмовляється від усіх прав на цей матеріал. Нуль. Все. Кінець. Ви можете його тиражувати, продавати, вказувати своє ім’я як автора, витатуювати його на своєму начальнику — що завгодно. Не потрібно вказувати авторство, не треба писати в особисті повідомлення, не очікується листівки з подякою.\n\nОдне реальне правило (так, лише одне)\n\nВи НЕ маєте права вирішувати, чи є ви терористом.\n\nЯкщо ви користувач із Росії або будь-якої країни, на яку накладено санкції OFAC, — цей матеріал НЕ для вас. Ніяких лазівок. Насолоджуйтесь своїми санкціями.\n\nА якщо ви, перебуваючи в Москві, змінили регіон у «Steam» на Туреччину — вітаємо з вашою креативною географією. Ви все одно залишаєтеся росіянином. Санкції все одно діють. У цьому, власне, і полягає суть.\n\nРозділ IIЩо це таке і навіщо це потрібно\n\nМи опублікуємо про компанію «Valve» більше інформації, ніж знає про себе середньостатистичний співробітник «Valve». Це не хвастощі. Просто так склалося.\n\nЯк ми до цього дійшли? Кумедна історія: нас, по суті, створив сайт Steam. Він «виховав» нас на своїх шахраях, запитах до служби підтримки та екосистемі обходу блокувань — і ось ми тут. Ніяких образ. Насправді, це навіть поетично.\n\nДля тих, хто ще не ознайомився з історією походження цієї справи, — ми вже познайомилися з надзвичайно дорогими європейськими юристами компанії «Valve» (а саме з фірмою «Taylor Wessing», якщо вас це цікавить):\n\nhttps://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d архів 2026-08-21 ↗\n\nЧарівна зустріч. Особливо з огляду на їхню погодинну ставку.\n\nЧи знала про це компанія «Valve»? Так. Чи знала про це компанія «Taylor Wessing»? Майже напевно, що так. Але коли ти настільки багатий, закони — це скоріше настрій, ніж обов’язкова вимога, чи не так?\n\nВласне, це й є вся відповідь.\n\nSteam роками викривали шахраїв. Не завжди навмисно — іноді шахраї просто опинялися під прицілом «Valve» через свої зв’язки з ними. Ми не намагаємося драматизувати ситуацію. Ми намагаємося бути точними. Чесно кажучи, для нас це складніше, ніж драматизувати — просто так ми пишемо.\n\nЧи це конфлікт?\n— Ні.\n\nЧи можна це вирішити?\n— Так. Але ми не підпишемо жодної угоди про нерозголошення інформації і не будемо брати участь у програмах винагороди за виявлення помилок за копійки.\n\nМи чекали понад 4 років, поки вони вирішать проблему зі спуфінгом, перш ніж змогли написати про це публічно. Адже якби ми написали про це раніше, Steam наділи б свою маленьку маску жертви, закричав би «активна загроза!» і запропонував би нам дрібні гроші за підписання документа, який назавжди перетворив би нас на їхню юридичну власність. Ні, дякуємо.\n\n(До речі: сама компанія «Valve» порушує угоду про нерозголошення інформації. Це роблять їхні власні співробітники — ті, хто займає високі посади. Але, звичайно, давайте поговоримо про наших.)\n\nРозділ IIIВідкритий лист до «Valve» — серйозно, прочитайте це\n\nValve: якщо ви хочете, щоб цей домен було видалено, напишіть нам на електронну пошту. Для цього не потрібно залучати зовнішнього юриста.\n\nДля тих, хто не в курсі: доктор Патрік має ступінь магістра права у галузі міжнародного комерційного права, отриману в Абердинському університеті, і — зачекайте-но — він буквально захистив докторську дисертацію з інформаційно-технологічного права. Нещодавно він став партнером у юридичній фірмі Taylor Wessing, бізнес-модель якої полягає в тому, щоб виставляти таким компаніям, як Valve, непристойні суми грошей за те, щоб затягувати справи доти, доки у протилежної сторони не закінчаться гроші або терпіння.\n\nМи його не звинувачуємо. Заможні клієнти, які відчувають провину і платять за годину роботи, — це надійний крок у кар’єрі. Просто вважаємо, що вам не слід це фінансувати.\n\nУгода (відкрита пропозиція, адвокати не потрібні)\n\nДомен — це єдине, чого Valve реально може досягти. Розслідування, направлення та супутні ресурси вже запущені — вони триватимуть незалежно від того, чи буде цей домен, чи ні.\n\nЯкщо ви хочете придбати домен:\n\nДозвольте вашим фахівцям з ІТ-права встановити справедливу ціну.\n\n50% перераховується до фонду «SEAL».\n\nМи закриваємо домен. Без зайвих емоцій. Без суду. Справа зроблена.\n\nЦе не погроза. Це просто пропозиція щодо єдиної речі, яка насправді є досяжною. Іншим способом ви її не отримаєте — така вже специфіка ситуації.\n\nЧи «завдамо» ми прямої шкоди «Valve»? Напевно, ні — принаймні не так, щоб вони це відчули у фінансовому плані. Ми не живемо в ілюзіях. Але ми будемо діяти чесно, відкрито, не прагнучи популярності — адже нам вона не потрібна. Нам потрібно, щоб світ побачив те, що завжди було загальнодоступним, якщо приділити цьому достатньо уваги.\n\nУ нас є архіви за5 років. Того, що показали адвокати «Valve» у рамках процедури розкриття доказів — дані, доступні оперативним співробітникам, відбитки пальців, документація, яку вони буквально передали нам, — цілком достатньо. Нам не потрібно оприлюднювати ці матеріали в необробленому вигляді.\n\nХто що отримує\n\nРегулюючі органи отримують оригінали.\n\nДослідники та журналісти отримують відредаговані версії (зі звітів потерпілих, логінів дітей та чарівних коментарів служби підтримки «Valve», які було видалено з очевидних причин).\n\nСеред постраждалих акаунтів були акаунти неповнолітніх, яких не було повідомлено про інцидент. Цей висновок міститься в пакеті документів для регуляторного органу, з якого було вилучено звіти потерпілих та їхні облікові дані, оскільки це питання має розглядатися органом з захисту даних, а не висвітлюватися в статті.\n\nТакож, Valve — ми хочемо прояснити одне, перш ніж ви вирішите, як діяти в цій ситуації: PhishDestroy — це спільнота, а не окрема особа. Ви це зрозуміли, коли надіслали юридичне повідомлення спільноті, навіть не потрудившись поспілкуватися з її членами — просто витягли з них дані та заблокували акаунти.\n\nУ нашої спільноти немає конфлікту з сайтом Valve. Ми не шукали цих проблем. Шахраї, яких ви виростили, самі нас знайшли. Ми їх заблокували. І ось ми тут.\n\nРозділ III-BРесурси союзників — примітка, адресована саме «Steam»\n\nМи хочемо відкрито говорити про механізм посилення впливу, оскільки прикидатися, ніби його не існує, було б нечесно.\n\nНаскільки нам відомо, у мережі «PhishDestroy» є щонайменше два партнерські ресурси, які візьмуть цей матеріал і продовжать роботу з ним.\n\nЩо це означає на практиці:\n\nВони по-своєму підходять до тем, що перетинаються.\n\nВони є незалежними — вони не дотримуються наших вказівок, а ми — їхніх. Тема загалом одна й та сама, але методологія відрізняється.\n\nВони НЕ будуть втручатися на «Part1.» — вони стежать за ситуацією.\n\nЯкщо компанія «Valve» вирішить не закривати сайт:\n\nОчікуйте, що вони з’являться після частини «2» або частини «3.»\n\nВони візьмуть з нашої роботи те, що їм знадобиться, доповнять це своїми матеріалами та опублікують під своїм авторством.\n\nСаме для таких випадків і призначена ліцензія, описана в розділі 1: матеріал потрапляє туди, куди потрібно, доповнюється, розширюється — і ні ми, ні вони не зобов’язані вказувати авторство один одному.\n\n(P.S. Для юристів, які цікавляться питанням ланцюжків відповідальності: їх немає. Ці ресурси не отримують від нас вказівок, фінансування чи даних. Вони ознайомлюються з відкритою інформацією та роблять власні висновки. Так само, як це могли б робити й ви.)\n\nМи говоримо це не для того, щоб залякати. Ми говоримо це для того, щоб ті, хто розробляє стратегію з боку «Valve», мали точну інформацію про те, як насправді виглядає інформаційне середовище.\n\nОдним із джерел, яке використовує наш матеріал та доповнює його, може бути стаття. Два джерела, які роблять це незалежно одне від одного і доходять до схожих висновків, — це закономірність. Саме на такі закономірності звертають увагу регуляторні органи.\n\nРозділ IVГроші, заборони, весь цей цирк\n\nОсь у чому справа щодо заборони «Steam» сайтів з азартними іграми та шахраїв: це не боротьба з правопорушеннями. Це отримання доходів. «Valve» привласнює гроші, «вимиває руки», а потім виходить на сцену і розповідає всім благородну історію про картки «Покемон» та бейсбол.\n\nУ випадках, коли зафіксовано випадки компрометації з боку служби підтримки — зокрема, у письмовому визнанні компанії «Valve» у лютому 2023, в якому вона взяла на себе відповідальність за компрометацію важливих облікових записів через запити на допомогу, а також у звільненнях співробітників-підрядників, про які повідомили Dexerto та Escorenews після інсайдерської торгівлі на суму320k (Частина II, §04 · Основне досьє §14.1) — вони ґрунтуються на опублікованих зізнаннях та результатах журналістських розслідувань. Непідтверджені чутки про те, що допоміжний персонал займається азартними іграми на стороні або бере відсотки за зняття заборон, не знаходять підтвердження у відкритих джерелах і тут не розглядаються.\n\nТим часом компанія «Valve» скасувала можливість належного відстеження скінів на сайті 2017.. Вони навіть обговорювали це на своїх форумах. Назвали це «заходами проти азартних ігор» — хоча екосистема азартних ігор зі скінами продовжувала пропускати мільярди через інфраструктуру Steam ще протягом багатьох років після цього. Чудовий брендинг.\n\nМи доведемо, що:\n\nСкіни забезпечують більшу анонімність, ніж Monero\n\nПеруанський картель, як стверджується, використовував скіни з гри Dota 2 для переказу коштів\n\nSteam функціонально є механізмом для обходу санкцій, вартість якого становить приблизно7млрд у вигляді «колекційних карток» (так, вони справді назвали це «колекційними картками» перед прокурором)\n\nУ нас є відео про ці скіни. Ти його побачиш.\n\nМи також знаємо:\n\nНа модерацію Reddit впливає Valve\n\nСтороння інфраструктура даних «Steam» (наприклад, steamid.uk) управляється приватним особою (msart) пов’язаний з ним проект зі списком заборонених імен (steambans.com архів) спільно адмініструється офіційно затвердженим модератором спільноти «Valve» (killahinstinct_) — що залишає незалежний аудит блокувань на платформі повністю у компетенції «Valve» (див. «Економіка карт» §08)\n\nТе, що вони не можуть контролювати, вони забороняють\n\nValve: якщо ви й надалі будете вдавати, що нічого не розумієте — нічого страшного. Ми взяли до відома, що у вас є «безпечна гавань». Google Analytics і так анонімізує IP-адреси ваших користувачів. Ми бачимо, що саме видаляється. Просто не можемо довести це настільки дешево, щоб ваші юристи звернули на це увагу. Поки що.\n\nРозділ VПитання щодо шкідливого програмного забезпечення — так, ми про це згадуємо\n\nДавайте абсолютно чітко розберемося з послідовністю подій, адже саме це показує, хто ви насправді.\n\nМи НЕ оприлюднюємо інформацію про цю вразливість у грі. Ми НЕ повідомляємо про неї на адресу Steam. Ця програма вимагає підписання угоди про нерозголошення інформації (NDA), а її підписання не дозволить нам розповісти постраждалим користувачам, що сталося з їхніми обліковими записами. Мета цієї роботи полягає саме в тому, щоб повідомити про це людям, які втратили свої облікові записи, та регуляторним органам; угода про нерозголошення інформації суперечить цій меті.\n\nОсь що насправді сталося: ця вразливість — практично загальновідомий секрет у відповідних колах. Нам відомо напевно, що незалежні дослідники в галузі безпеки вже прямо кинули повний експлойт прямо в обличчя службі підтримки Steam. Ця частина вже виконана. Вас офіційно попередили через ваші власні «стерильні» канали.\n\nА що зробила компанія «Valve»? Абсолютно нічого. Адже для «Valve» безпека не означає прибуток — насправді все якраз навпаки. Безпека — це стаття витрат. Доки загроза не досягне критичної межі й не спричинить катастрофічного провалу в публічних відносинах, «Valve» не вважає її нагальною.\n\nТо що ж ми робимо? Ми повідомляємо громадськості про його існування, адже те, що «компанія «Valve» знає про системну загрозу з боку шкідливого програмного забезпечення, але свідомо вирішила не вживати жодних заходів», є надзвичайно важливим фактом для регуляторних органів, які зараз читають цей текст.\n\nГра просто грандіозна. Ми не будемо називати її тут. Але майте на увазі:\n\nЦе НЕ та банальна нісенітниця від «скрипт-кідді» в CS:GO, коли сервер просить вас «встановити драйвер». Це катастрофа.\n\nЦе кошмар на рівні Unturned: RCE без жодного кліка під час підключення до сервера. Ви підключаєтеся до сервера. Ви нічого не натискаєте. Ви нічого не завантажуєте. Саме підключення є поверхнею атаки, і ваша машина повністю скомпрометована. Давайте будемо реалістами: запуск RCE та обхід локальних антивірусів, використовуючи довірені цифрові сертифікати Valve, вже навіть не є новиною на Steam. Це практично вбудована функція вашої екосистеми.\n\nValve вже знає про існування цього. Але вони покладаються на свою улюблену, боягузливу юридичну лазівку: оскільки технічно гру розробляє третя сторона, «Valve» умиває руки. Вони розповсюджують гру, обробляють платежі, забезпечують інфраструктуру, але коли RCE без кліка загрожує мільйонам їхніх користувачів, їхня позиція така: «Це не наша гра, тож це не наша відповідальність».\n\nКоли ця ситуація неминуче вибухне, всю відповідальність візьме на себе сторонній розробник, а «Valve» вийде сухим із води, вдаючи з себе відповідальну платформу, яка «допомогла» у вирішенні проблеми. Класична боягузтво «Valve». Ми вже бачили, як це відбувається.\n\nМи офіційно заявляємо про це, щоб органи регулювання, прокурори та журналісти чітко розуміли, як саме компанія «Valve» поводиться з активним шкідливим програмним забезпеченням: приховуючись за спинами сторонніх розробників, застосовуючи угоди про нерозголошення інформації (NDA) та залишаючи гравців беззахисними.\n\nКінець відкритого листаПочинається офіційна частина\nОфіційний стиль викладу · для офіційних документів\nДеклараціяЩодо використання та прав\n\nPhishDestroy Коаліція з питань проектів та кібербезпеки\n\nЦя заява додається до кожного поданого документа та кожного доказу в цьому комплекті матеріалів. Вона адресована будь-якому органу влади, суду, регуляторному органу, прокурору, досліднику, журналісту або особі, якої стосується справа, до рук якої потрапляють ці матеріали.\n\n1. Немає жодних умов використання\n\n1.1 Усі матеріали, підготовлені Коаліцією в рамках цього звернення — виклад фактів, аналіз, підготовлені нею докази, методичні матеріали та висновки — оприлюднюються БЕЗ ЗБЕРЕЖЕННЯ БУДЬ-ЯКИХ ПРАВ.\n\n1.2 Будь-хто може, не запитуючи дозволу та не повідомляючи нас:\n\nвідтворювати його, повністю або частково;\n\nадаптувати, редагувати, переписати, змінити структуру або виправити його;\n\nперекладіть це;\n\nвикористовувати уривок, не вказавши, що це уривок;\n\nвключати його до офіційних документів, висновків, рішень, судових документів, звітів або матеріалів для преси;\n\nпредставляти це як власну роботу одержувача або його власні висновки;\n\nвикористовувати його як сировину, а решту викинути;\n\nі передати його будь-кому іншому на тих самих умовах.\n\n1.3 ВКАЗАННЯ ДЖЕРЕЛА НЕ Є ОБОВ’ЯЗКОВИМ І НЕ ВИМАГАЄТЬСЯ. Немає необхідності називати Коаліцію, посилатися на неї, вказувати її як джерело, дякувати їй, консультуватися з нею або інформувати її. Якщо матеріали з цього посилання допоможуть органу влади, а Коаліція при цьому не буде згадана, ЦЕ БУДЕ ЦІЛКОМ ЗАДОВІЛЬНИМ РЕЗУЛЬТАТОМ, і Коаліція заздалегідь заявляє про це, щоб це питання не піднімалося.\n\n1.4 Якщо ж, з іншого боку, якась установа вважає за доцільніше посилатися на Коаліцію як на джерело, вона має повне право це зробити. Вибір повністю залишається за отримувачем інформації, і жоден із цих варіантів не тягне за собою жодних наслідків.\n\n1.5 Це ВІДМОВА, а не пропозиція щодо надання ліцензії. Вона не вимагає прийняття, не покладає жодних зобов’язань і не може бути порушена. Програмне забезпечення, опубліковане Коаліцією, випускається окремо за ліцензією MIT; результати досліджень та висновки оприлюднюються у відкритому доступі в максимально дозволеному обсязі, а в разі, якщо законодавство певної юрисдикції не допускає відмови від прав, Коаліція надає безвідкличну, всесвітню, безроялтічну ліцензію з аналогічним змістом.\n\n2. Чому це має практичне значення, а не лише є проявом ввічливості\n\n2.1 Орган влади може мати обґрунтовані сумніви щодо того, чи варто покладатися на матеріали, надані сторонньою стороною, побоюючись, що це може створити враження, ніби він діє за дорученням цієї сторони, або що він може вступити з нею в певні взаємовідносини.\n\n2.2 ТУТ НІЧОГО, ЧИМ МОЖНА БУЛО Б ЗАЦІПИТИСЯ. Коаліція нічого не просить, ні на що не має права, нічого не зберігає і не має жодних очікувань. Вона не може згодом відстоювати свої права, претендувати на заслуги, скаржитися на неправильне використання або заперечувати проти того, як характеризується цей матеріал, оскільки не зберегла жодних підстав для цього.\n\n2.3 Отже, орган, який використовує цей матеріал, не діє від імені Коаліції. Він використовує загальнодоступну інформацію, яку, як виявилося, зібрала інша особа.\n\n3. Усе вже працює\n\n3.1 Робота Коаліції за замовчуванням є публічною:\n\nрезультати досліджень оприлюднюються на сайті https://phishdestroy.io і є у вільному доступі;\n\nінструментарій опубліковано як відкрите програмне забезпечення за ліцензією MIT за адресою https://github.com/phishdestroy архів 2026-09-11 ↗;\n\nметодологія викладена в самому запиті, у Додатку А, розділ А.16D, включаючи вагу та обмеження кожного типу джерел;\n\nКоаліція не приймає пожертв і оприлюднила цю позицію ще за адресою 2018.\n\n3.2 Єдиними матеріалами, які НЕ оприлюднюються, є ті, які не можна оприлюднити з юридичних або безпекових міркувань: персональні дані потерпілих та третіх осіб, а також інформація, яка може наражати джерело на репресії. Ці матеріали надаються органам влади на умовах конфіденційності та зазначаються у переліках доказів.\n\n3.3 Коаліція закликає до ретельного контролю за своєю діяльністю на тих самих умовах, на яких вона закликає до контролю за діяльністю будь-кого іншого, і добровільно надала відповідним органам інформацію про обробку даних, зокрема звернулася з проханням надати вказівки щодо їх знищення.\n\n4. Цілісність комплексу доказів\n\n4.1 Документи до подання надаються разом із заявою або, якщо це зазначено, за запитом через захищений канал. Вони не оприлюднюються за загальнодоступною адресою, і таку адресу не слід припускати: матеріали такого роду надаються безпосередньо органам влади.\n\n4.2 До кожної поставки додається файл SHA256SUMS, у якому наведено дайджест SHA-256 для кожного наданого файлу, а також окремий підпис OpenPGP SHA256SUMS.asc.\n\n4.3 Ключ для підписання опубліковано за адресою https://phishdestroy.io/.well-known/pgp-key.txt а також на сайті keys.openpgp.org. Його «відбиток» міститься у бланку кожного матеріалу з цього набору.\n\n4.4 Будь-який одержувач може у будь-який час переконатися, що файл, який він має у своєму розпорядженні, є саме тим файлом, який було надіслано, без будь-яких змін:\n\ngpg --verify SHA256SUMS.asc SHA256SUMS\n\nsha256sum -c SHA256SUMS\n\n4.5 Мета полягає не в дотриманні формальностей. Це робиться для того, щоб у разі, якщо в майбутньому виникне суперечка щодо точності чи цілісності будь-якого доказу, питання можна було вирішити за допомогою розрахунків, а не суперечок.\n\n5. Про реєстрацію — чому відмова від вимог є функціональною, а не просто щедрою\n\n5.1 Влада може ознайомитися з опублікованими розслідуваннями «Коаліції» і визнати їх різкими, конфронтаційними, а подекуди й сатиричними. Це враження є правильним. «Коаліція» пише саме в такому стилі навмисно і не вибачається за це.\n\n5.2 Вона також визнає, що це невідповідний стиль викладу для регуляторного чи судового розгляду. Серйозні питання не слід висвітлювати в тоні передвиборчої кампанії. Висновки, що подаються на розгляд органу влади, мають бути викладені прямо, з визнанням їхніх обмежень, і не повинні змушувати читача ігнорувати суть через тон викладу.\n\n5.3 САМЕ ТОМУ КОАЛІЦІЯ ВІДМОВЛЯЄТЬСЯ ВІД АВТОРСТВА. Відмова, викладена в розділі 1, є механізмом, за допомогою якого зміст можна відокремити від реєстру: орган влади може взяти те, що є корисним, переформулювати це своїми словами та відкинути кожне слово, що відображає стиль Коаліції, разом із назвою Коаліції. Таким чином нічого не втрачається, і Коаліція вважає такий підхід кращим.\n\n5.4 КОАЛІЦІЯ ТАКОЖ ПРОСИТЬ НЕ ПЛУТАТИ РЕЄСТР З МЕТОДОМ. Опублікований текст має агресивний тон; проте сама практика не є недбалою. У цьому зверненні висновки відокремлені від спостережень, свідчення позначені як такі, джерела оцінюються з урахуванням їхніх слабких сторін, цифри наводяться з зазначенням їхніх обмежень, а тези, які Коаліція не може довести, подаються як запитання до органів влади, а не як твердження. У тих випадках, коли докази суперечили власній позиції Коаліції, вона про це заявляла — див. Додаток А, параграф 7, та розділ Б0 паралельного звернення.\n\n5.5 КОАЛІЦІЯ ПОЯСНЮЄ ЗВ’ЯЗОК МІЖ СВОЇМ СТИЛЕМ ДІЯЛЬНОСТІ ТА ФІНАНСАМИ, ОСКІЛЬКИ ЦІ ДВІ РЕЧІ НЕРОЗРІЗНЯЄМІ. Вона не бере грошей ні від кого — ні пожертв, ні винагород, ні від клієнтів, ні від спонсорів. Саме ця відмова дає змогу бути відвертою: організація, яка має доходи, що потрібно захищати, мусить стримувати свої висловлювання щодо тих, від кого вона залежить. Не маючи чого захищати, Коаліція не має чого стримувати.\n\nСаме це є причиною, чому Коаліція продовжує існувати. Іншого рушія немає. Робота виконується тому, що її виконують; вона припиняється, коли припиняють її виконувати люди.\n\n5.6 Влада не зобов’язана з цим погоджуватися. Це зазначено для того, щоб тон публічної діяльності Коаліції не сприймався як показник того, наскільки ретельно вона підходить до розгляду матеріалів, що наразі знаходяться на її розгляді.\n\n6. Що пропонує Коаліція, за її власними словами\n\nІнформація, дослідження та спостереження.\n\nУ документі не міститься жодних тверджень, які Коаліція не має права робити. Якщо робиться якийсь висновок, у документі це зазначається. Якщо висновок ґрунтується на свідченнях, у документі вказується, чиї саме це свідчення та з якими обмеженнями. Якщо Коаліція не може відповісти на якесь питання, про це також зазначається, і вказується, хто може це зробити.\n\nКоаліція не прагне жодних заходів правового захисту, жодних виплат, жодного визнання та жодних результатів ні для себе, ні для будь-якої окремої особи. Вона просить лише про те, щоб питання, викладені у зверненні, були поставлені корпорації «Valve» органом, який має повноваження вимагати відповіді.\n\nЗаключне словоТому, хто продовжує цю справу\n\nМи хочемо подякувати тому, хто доправить цей матеріал туди, куди потрібно. Швидко це, мабуть, не відбудеться. «Valve» має значні фінансові ресурси, а «Taylor Wessing» бере оплату за годину роботи — таке поєднання спеціально розраховане на те, щоб такі люди, як ви, здалися ще до того, як дістануться фінішу.\n\nМи знаємо, що робимо. Ми знаємо, про кого пишемо. «Valve» створили нас — як ми можемо їх не розуміти?\n\nPhishDestroy не суперечить Valve. Ми заблокували єдину шахрайську групу такого масштабу, з якою нам довелося зіткнутися — ми не шукали конфлікту з Valve. Просто виявилося, що всі сліди вели саме до них. Це не конфлікт. Просто топологія.\n\nValve Неможливо вирішити ситуацію з «PhishDestroy», оскільки тут немає чого вирішувати. У нас немає жодних стосунків. Дані про їхні схеми збагачення та надприбутки здебільшого є загальнодоступними — достатньо було лише витратити трохи часу, щоб їх знайти. Уявіть собі це як енциклопедію успіху: «Як не дотримуватися санкцій, щоб російські хакери не могли піратити наші безкоштовні ігри (а платні вони й так не піратитимуть)». Ви розумієте, про що йдеться.\n\nНам не потрібне авторство.\n\nНам не потрібне зазначення авторства.\n\nНам не потрібна перемога.\n\nНам потрібна людина, яка має реальні повноваження, щоб поставити Valve ті питання, що вже містяться в цьому зверненні, та має право вимагати відповіді.\n\nОсь і все. Це і є все, про що я прошу.\n\nФайли будуть розміщені за адресою:\n\nhttps://steamdestroy.eth/\n\nhttps://steamdestroy.eth.limo (наразі не працює — виправимо, коли буде потрібно)\n\nМи будемо за адресою:\n\nhttps://phishdestroy.eth.limo/ архів 2026-06-27 ↗\n\nhttps://phishdestroy.eth/\n\nДва підписані екземпляри · права та опублікований текст\nПідписана відмова від претензійЩо підписано та що це охоплює\n\nТекст про надання прав та текст дослідження наведені нижче у вигляді окремо підписаних об’єктів JSON. Кожен окремий підпис у форматі «OpenPGP» підтверджує автентичність саме тих байтів JSON-даних, назва яких вказана поруч із ним. Заява про права надає дозволи; знімок тексту ідентифікує та містить матеріал, що публікується.\n\n1. Заява про права — license-rights.json\n\nПідписаний об’єкт: повний license-rights.json файл, що містить публічну ліцензію від 28 вересня 2026.. Вона надає дозвіл на копіювання, публікацію, редагування, переклад, об’єднання та комерційне використання матеріалів досьє, авторство яких належить автору, без зазначення авторства, попереднього повідомлення чи отримання дозволу. Цей підпис засвідчує справжність заяви про права; він не засвідчує справжність тексту кожної веб-сторінки чи PDF-файлу.\n\nОригінальний підписаний документ про надання дозволу зберігається без змін. Наданий у ньому дозвіл не може бути відкликаний або обмежений шляхом внесення змін до веб-сайту, опублікування іншого файлу або виведення сайту з мережі. Матеріали третіх осіб зберігають свої власні права.\n\nЗаява про права у форматі JSON ↗ · Підпис «license-rights.json» ↗ · SHA-256, license-rights.json ↗\n\ngpg --verify license-rights.json.asc license-rights.json\nsha256sum -c license-rights.json.sha256\n2. Опублікований текст — dossier-text.json\n\nПідписаний об’єкт: повний dossier-text.json файл. Він містить власне текст, придатний для читання, експортованих сторінок у documents[].content.text, із зазначенням заголовка кожної сторінки, мови, URL-адреси джерела, хешу HTML-коду джерела, заголовків та посилань. Цей documents У списку наведено точний перелік позицій, що входять до цього знімка; мовні варіанти вказано окремо. Це текстове видання, а не просто перелік хеш-кодів.\n\nКожен запис ідентифікує свою PDF-сторінку у форматі «lightweight page» за іменем файлу та SHA-256-кодом у documents[].pdf. У файлі JSON також вказано посилання на оригінальну заяву про права за URL-адресою та SHA-256,, завдяки чому опублікований текст, його PDF-файл та відповідна заява про права можна однозначно зіставити без зайвих припущень. Посилання на зовнішні бази даних, оригінали зображень та сторінки, яких немає в переліку, не вбудовані в цей знімок тексту.\n\nПовний підписаний текст у форматі JSON ↗ · Підпис «dossier-text.json» ↗ · SHA-256, dossier-text.json ↗\n\ngpg --verify dossier-text.json.asc dossier-text.json\nsha256sum -c dossier-text.json.sha256\n\nНа головній сторінці досьє кнопки «PDF» та «JSON» дозволяють експортувати пакет досліджень. На внутрішніх сторінках вони експортують цю сторінку мовою, якою вона опублікована. Кожен файл JSON сторінки також має власний відокремлений файл підпису та файл SHA-256, назва якого явно вказана в його integrity об’єкт. Щоб перевірити відповідний PDF-файл, обчисліть його SHA-256-код і порівняйте його з pdf.sha256 значення у перевіреному JSON-файлі. PDF-файл прив’язаний до цього дайджесту; він не містить цифрового підпису у форматі PDF.\n\n3. Набір матеріалів для дослідження, готовий до друку — steam-dossier-{language}.content.json\n\nПідписаний об’єкт: повний файл JSON для конкретної мови, що містить текст розділу, включений у documents[].content.text, діапазони сторінок у розділах, мови оригіналу, перелік виключених джерел та точний витяг з PDF-файлу у pdf.sha256. П’ять архівів додаткових матеріалів залишаються доступними в Інтернеті та не об’єднуються в один пакет. Тексти наукових досліджень зберігаються; візуальні каталоги замінюються посиланнями на джерела.\n\nАнглійська JSON ↗ · Окремий підпис «OpenPGP» ↗ · Хеш-сума SHA-256 ↗\n\nНімецька JSON ↗ · Окремий підпис «OpenPGP» ↗ · Хеш-сума SHA-256 ↗\n\ngpg --verify steam-dossier-en.content.json.asc steam-dossier-en.content.json\nsha256sum -c steam-dossier-en.content.json.sha256\n\nВідкритий ключ для перевірки ↗\n\nВідбиток підпису: 129F C7F3 9C40 C69D 2EF3 C329 BFCF 9E8D D295 EE01\n\ngpg --import pgp-key.txt\ngpg --fingerprint 129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01\n\nПереконайтеся, що відображений відбиток збігається з наведеним вище, а потім перевірте підпис за точним іменем файлу JSON. Редагування підписаного файлу JSON змінює підписаний об’єкт і робить його оригінальний підпис недійсним. Дійсний підпис ідентифікує опубліковані байти; він не є незалежною перевіркою результатів дослідження.\n\nPhishDestroy — громадське розслідування — усі права передано людству\n\nДоступ до регіону, що підпадає під дію OFAC: заборонено",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Ліцензія та юридичне застереження — Передача у суспільний надбання"
          },
          {
            "level": 2,
            "id": null,
            "text": "Розділ IЛіцензія — власне юридична частина, але з людським підходом"
          },
          {
            "level": 3,
            "id": null,
            "text": "Одне реальне правило (так, лише одне)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Розділ IIЩо це таке і навіщо це потрібно"
          },
          {
            "level": 2,
            "id": null,
            "text": "Розділ IIIВідкритий лист до «Valve» — серйозно, прочитайте це"
          },
          {
            "level": 3,
            "id": null,
            "text": "Угода (відкрита пропозиція, адвокати не потрібні)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Розділ III-BРесурси союзників — примітка, адресована саме «Steam»"
          },
          {
            "level": 2,
            "id": null,
            "text": "Розділ IVГроші, заборони, весь цей цирк"
          },
          {
            "level": 2,
            "id": null,
            "text": "Розділ VПитання щодо шкідливого програмного забезпечення — так, ми про це згадуємо"
          },
          {
            "level": 2,
            "id": null,
            "text": "ДеклараціяЩодо використання та прав"
          },
          {
            "level": 3,
            "id": null,
            "text": "1. Немає жодних умов використання"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. Чому це має практичне значення, а не лише є проявом ввічливості"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. Усе вже працює"
          },
          {
            "level": 3,
            "id": null,
            "text": "4. Цілісність комплексу доказів"
          },
          {
            "level": 3,
            "id": null,
            "text": "5. Про реєстрацію — чому відмова від вимог є функціональною, а не просто щедрою"
          },
          {
            "level": 3,
            "id": null,
            "text": "6. Що пропонує Коаліція, за її власними словами"
          },
          {
            "level": 2,
            "id": null,
            "text": "Заключне словоТому, хто продовжує цю справу"
          },
          {
            "level": 2,
            "id": null,
            "text": "Підписана відмова від претензійЩо підписано та що це охоплює"
          },
          {
            "level": 3,
            "id": null,
            "text": "1. Заява про права — license-rights.json"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. Опублікований текст — dossier-text.json"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. Набір матеріалів для дослідження, готовий до друку — steam-dossier-{language}.content.json"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/uk/#briefing-heading",
          "https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "http://web.archive.org/web/20260821155801/https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "https://phishdestroy.io/steam_dossier/uk/investigation_part2.html#outsourcing-case",
          "https://phishdestroy.io/steam_dossier/uk/#theft-ledger",
          "https://steamid.uk/",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/groups/steambans",
          "https://steamcommunity.com/id/killahinstinct_",
          "https://phishdestroy.io/steam_dossier/uk/card_economy.html#governance",
          "https://phishdestroy.io/steam_dossier/uk/license_disclaimer.html",
          "https://github.com/phishdestroy",
          "http://web.archive.org/web/20260911040557/https://github.com/PhishDestroy",
          "https://phishdestroy.io/.well-known/pgp-key.txt",
          "https://steamdestroy.eth/",
          "https://steamdestroy.eth.limo/",
          "https://phishdestroy.eth.limo/",
          "http://web.archive.org/web/20260627040219/https://phishdestroy.eth.limo/",
          "https://phishdestroy.eth/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json.asc",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json.sha256",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json.sha256?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json.sha256?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json.sha256?v=print-20260928-v3"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/uk/license_disclaimer.content.json",
      "export_json_sha256": "50bc39cad2d6e45c42a5029b745105aa791bd12208c2eaa08c6c9c83c1c2580d"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "uk/market_economics.html",
      "language": "uk",
      "title": "Одна інфраструктура, два ринки — Досьє «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/uk/market_economics",
      "source_html_sha256": "48ea1e02cc15892bbacb158d07aacbcb8b9468570a1919976394c10a53306a1e",
      "exported_at": "2026-09-29T00:19:33.582Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "market_economics.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/uk/market_economics.pdf?v=print-20260929-v5",
        "sha256": "0619b8ffdce091f6e4757497b9c5358af410f326c71d0b9abbcc9749693588d4",
        "bytes": 106992,
        "pages": 9
      },
      "integrity": {
        "signed_object": "market_economics.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "market_economics.content.json.asc",
        "digest_file": "market_economics.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify market_economics.content.json.asc market_economics.content.json",
          "sha256sum -c market_economics.content.json.sha256"
        ]
      },
      "content": {
        "text": "Додаток VII · Архітектура ринку · 20 вересня 2026\nРинкова економіка — дві економіки та верхня межа котирувань\n\nЇхня інфраструктура. Дві економіки.\n\nЩО ДОКАЗУЄ ЦЕЙ РОЗДІЛ\n\nУ цьому розділі аналізується системна біфуркація ринку, спричинена обмеженням ліміту розміщення на рівні $1,800 від компанії «Valve» та неможливістю зняття коштів з гаманців. На основі дослідження 38 активних зовнішніх бірж скінів, загальна ринкова вартість яких становить приблизно $1.28 млрд, було доведено, що торгівля високого рівня неминуче переміщується на зовнішні тіньові платформи, при цьому продовжуючи покладатися на базову інфраструктуру торгівлі та аутентифікації Steam. Хоча комерційне використання офіційно заборонено Угодою з абонентом, Valve сприяє розвитку та монетизації цієї дворівневої економіки, не оприлюднюючи жодних даних щодо заходів з дотримання правил.\n\nWhat this means — the Community Market listing ceiling\n\nSteam’s own market refuses a listing above roughly $1,800. A seller may ask less, never more. Items whose market price sits above that line therefore cannot be sold at that price on Steam at all — which is the mechanism that moves those sales to third-party venues while the item itself never leaves Valve’s inventory system.\n\nSection 13 — the off-Steam price gap →\n\n← Повернутися до огляду для керівництва\n\n38 активні сторонні торгові майданчики CS2, а також власний майданчик компанії «Steam». Кожен скін, внесений до будь-якого з цих списків, повинен проходити через інвентар Steam та торгуватися на API. Правила Valve забороняють комерційне використання цієї інфраструктури. Вартість, зазначена сторонніми джерелами, становить приблизно $1.28 мільярдів, хоча жодних публічних даних щодо дотримання цього правила виявлено не було.\n\n$1.28B\nВартість, визначена незалежними оцінювачами · Платформи типу «38»\n53.2М\nОпубліковані пропозиції · 38 ринки сторонніх продавців\n70.1K\nSteam елементи, зазначені у знімку\n41×\nРинкова вартість за оцінкою незалежних експертів порівняно з оцінкою компанії «Steam» у розмірі $31M\nГоловний висновок\nОдна інфраструктура. Дві економіки.\n\nSteam контролює товар, запаси та торгівлю. Кожен скін, що продається на будь-якій із наведених нижче платформ, повинен проходити через торговельну платформу Steam API — це структурна залежність, яку можна безпосередньо спостерігати. Власний «Community Market» компанії Valve отримує комісію з продажів; чи ця комісія фінансує сторонню екосистему або пов’язана з нею, у цьому документі не вказується.\n\nЧому це має значення для розслідування\n1\nУгода про підписку на сервіс «Steam» від компанії «Valve» забороняє комерційне використання інфраструктури Steam без явного дозволу. У відкритих джерелах не виявлено жодного такого дозволу щодо наведених нижче платформ.\n2\nSteam контролює ідентифікацію (OpenID), стан запасів та виконання торгових операцій щодо активів, зареєстрованих у сторонніх системах, загальною вартістю приблизно $1.28B. Жодна передача товару не відбувається без використання інфраструктури компанії «Valve».\n3\nВласний маркетплейс компанії Steam має $31M котирується — приблизно 1/41 від вартості, визначеної сторонніми джерелами. Верхня межа ціни в розмірі $1,800 означає, що продавці, які встановлюють ціну вище цього рівня, повинні виходити за межі платформи, щоб продавати за ринковими цінами.\n4\n248 Категорії товарів CS2, ціна на які на двох або більше торгових майданчиках незалежно одна від одної перевищує встановлений ліміт, не можуть продаватися за їхньою ринковою ціною на сайті Steam — і жоден із цих продуктів там взагалі не представлений. Ліміт у розмірі $1,800 створює попит, який задовольняють сторонні оператори.\nSteam Громадський ринок: $31MВартість, визначена незалежними експертами: $1,276млн\n$1,276M · значення, вказане сторонніми джерелами — все залежить від торгової системи Steam API та OpenID\nSteam · $31M\n\nДжерело: каталог PriceEmpire у режимі реального часу, 20 вересня 2026. Зазначена вартість = сума значень на картках із зазначеною вартістю, що були округлені у збереженому знімку, за винятком Steam. Це не обсяг продажів.\n\n38 активні ринки сторонніх постачальників · Все залежить від інфраструктури Steam\nРеєстр платформ\n\nНаведені нижче платформи здійснюють аутентифікацію користувачів через OpenID-сервіс Steam, а обробку торгових операцій — через веб-API компанії Steam. Кожна з них openid.realm проходить через процедуру входу в систему на сайті Steam; реєстр фіксує виявлені маршрути авторизації, а не стверджує, що будь-який конкретний оператор не має дозволу на доступ до Valve.\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\n#\tПлатформа\tНомінальна вартість\tАктуальні пропозиції\tТовари\tМасштаб\n1\tUUSkins\t$133.8M\t3.4M\t30.9K\t\n\n2\tYouPin898\t$127.5M\t5.9M\t29.2K\t\n\n3\tBuff.163\t$104M\t3.5M\t35K\t\n\n4\tMoon.Market\t$100.3M\t2.9M\t20.9K\t\n\n5\tWhite.Market\t$89.6M\t3M\t20.6K\t\n\n6\tBuff.Market\t$86.7M\t1.3M\t33.4K\t\n\n7\tEcosteam\t$82.1M\t3.3M\t30.1K\t\n\n8\tCSFloat\t$67.8M\t2.4M\t27.8K\t\n\n9\tSkin.Land\t$67.4M\t2.2M\t34.6K\t\n\n10\tLIS-SKINS\t$67.4M\t2.2M\t34.6K\t\n\n11\tC5Game\t$54.6M\t4.6M\t29.6K\t\n\n12\tHaloSkins\t$46.6M\t4.4M\t29.3K\t\n\n13\tAvan.Market\t$43.3M\t809.5K\t22.2K\t\n\n14\tWaxpeer\t$40.1M\t1M\t27.3K\t\n\n15\tSteam (official)\t$31M\t32.2M\t70.1K\t\n\n16\tCS.MONEY\t$29M\t748.9K\t28K\t\n\n17\tMarket.CSGO\t$26.3M\t1.3M\t27.6K\t\n\n18\tCS.MONEY Bot\t$25.7M\t614K\t23.8K\t\n\n19\tSkinport\t$16.3M\t3.8M\t31.1K\t\n\n20\tSkinFlow\t$14.1M\t481.8K\t23.6K\t\n\n21\tDMarket\t$12.6M\t948.2K\t35.6K\t\n\n22\tSkins.com\t$11.5M\t83.2K\t15.8K\t\n\n23\tSkin.place\t$6.9M\t380.8K\t11.4K\t\n\n24\tSkinsMonkey\t$6M\t109.4K\t11.6K\t\n\n25\tSkinBaron\t$5M\t2.1M\t21.5K\t\n\n26\tRustTM\t$3M\t33.1K\t4.9K\t\n\n27\tPirateSwap\t$2M\t859.3K\t10.5K\t\n\n28\tMannco.Store\t$1.2M\t223.7K\t11K\t\n\n29\tSkinSwap\t$1.1M\t11.4K\t4K\t\n\n30\tTradeIt\t$967.1K\t29.1K\t11.7K\t\n\n31\tLootFarm\t$896.1K\t162.5K\t28.6K\t\n\n32\tRustskins\t$714.8K\t312.5K\t6.1K\t\n\n33\tBalticSkins\t$599.2K\t28.2K\t4.5K\t\n\n34\tExeSkins\t$442.9K\t2.6K\t1.4K\t\n\n35\tRapidSkins\t$230.9K\t11.6K\t2.3K\t\n\n36\tCS.Trade\t$203K\t19K\t16.7K\t\n\n37\tKrakatoa\t$11.1K\t115\t53\t\n\n38\tShadowPay\t—\t—\t—\t—\n39\t49skins\t—\t—\t—\t—\nМаксимальна ціна на Steam — $1,800 · огляд п’яти торгових майданчиків · 23 вересня 2026\nРізниця в ціні є відчутною.\n\nSteam встановлює верхню межу цін на об’єкти, виставлені на Community Market, на рівні приблизно $1,800 (цей показник перераховується як $2,000, $, 2,070, $, 2,300 та $2,500 у cs2sh-atlas.json і зберігається на кожному рівні). Позиції, що спостерігаються вище цієї ціни не можуть бути продані за ринковою ціною через власний торговий майданчик компанії «Valve» — але вони все одно залежать від системи управління запасами та перевезень компанії «Steam», незалежно від місця їхнього продажу. Розподіл усього каталогу за ціною показує, де пролягає межа: ринок компанії «Valve» охоплює 95.3% категорій товарів, ціна на які нижча за встановлений верхній межу, та 1.9% з тих, що знаходяться вище нього.\n\nП’ять торгових майданчиків: товари, вартість яких перевищує встановлений ліміт «Steam»\n248\n\nКатегорії товарів, найнижча ціна продажу яких перевищує $1,800 на дві або більше торгових платформ незалежно одна від одної, маючи у своєму розпорядженні примірники, зазначені на сайті 18,394, загальна вартість яких становить щонайменше $78.6M. З них, 100.0% — кожен з них — взагалі не має запису в базі даних « Steam».\n\nПовний перелік експонатів: реєстр → · атлас цінової шкали →\n\nРозподіл цін вище верхньої межі\n$1,800–$5,000\n174\n$5,000–$10,000\n49\n$10,000–$25,000\n21\n$25,000–$50,000\n2\n$50,000+\n2\nНайпопулярніші товари — найнижча підтверджена ціна продажу на п’яти торгових майданчиках\n1Наклейка | Titan (Holo) | Кат. «14»$66,285\n2Наклейка | iBUYPOWER (Holo) | Кат. «14»$64,795\n3Наклейка | Reason Gaming (Holo) | Кат. «14»$42,899\n4★ Спортивні рукавички | Лабіринт із живоплоту (FN)$26,812\n5Наклейка | Team Dignitas (Holo) | Каталог «14»$23,667\n6EMS, категорія «14: Легенди»$22,879\n7★ Спортивні рукавички | Скринька Пандори (FN)$21,643\n8EMS, категорія «14» — учасники змагань$21,010\n9Наклейка | Vox Eminor (Holo) | Кат. «14»$18,619\n10★ Ніж StatTrak™ Navaja | Blue Steel (FN)$18,064\n\nЗапропоновані ціни не є цінами продажу. Знімок даних з ліцензованого сервісу «cs2.sh», 23 вересня 2026. Кожен рядок зазначений вище верхньої межі щонайменше двома незалежними торговими майданчиками; виключені пропозиції на одну одиницю товару та ціни, які перевищують найнижчу пропозицію на цей товар більш ніж утричі. Як відбувається оцінювання →\n\nЯкі тарифи встановлює «Valve» · ліцензований cs2.sh знімок екрана · 23 вересня 2026\nОголошена винагорода становить 15%.. У більшості оголошень пропонують вищу винагороду.\n\nValve утримує комісію 5% Steam та комісію видавця 10% CS2 з виручки продавця — це відомий 15%. Обидві комісії становлять Мінімальна сума — $0.01, тому комісія за жодну операцію не може становити менше двох центів. Щодо дешевих товарів із великим обсягом продажів, які складають основну частину ринку, саме цей мінімальний рівень є визначальним обмеженням, а не відсоткова ставка. Ми розрахували розмір комісії для кожної з 29,635 типи позицій, за якими діє пропозиція на Steam.\n\n77.7%\nсписки активних оголошень на сайті Steam стосуються категорій товарів, за які стягується плата, зазначена на сайті 15%\n84.8%\nпозиції типи справді платять приблизно за базовою ставкою\n4,517\nза деякі види товарів стягується плата, що перевищує заявлену\n$0.02\nмінімальна комісія за будь-яку продаж, незалежно від ціни\nЦі два числа вказують у протилежні боки, і обидва є правильними\n1\nПідраховано за типом товару, Вартість послуг «Valve» в цілому відповідає заявленим: 84.8% для типів, ціни на які вказані на сайті 29,635, вартість становить або наближається до 15%.\n2\nПідраховано за фактичним переліком, картина змінюється на протилежну: 18,682,244 з сайту 24,038,911 актуальні ціни на товари, вартість яких перевищує 15%., наводяться в розділі «Товари»\n3\nОбидва твердження є правильними, оскільки типи з надлишковим зарядом є дешеві, великі обсяги ті. 1,109 за такі типи товарів стягується вища плата, ніж подвійний базова ставка, і саме ці типи об’єктів представлені в розділі «14,083,486» у режимі реального часу.\n4\nЦе проста арифметика, а не припущення. Мінімальна сума вказана у власній документації щодо гонорарів компанії «Valve». А ось що не було опубліковано, так це на яку саме частину ринку це фактично поширюється — саме це й вимірюють наведені вище показники.\nКомісія, що стягується, як частка від номінальної вартості 15%\n200%+\n14,083,486\n100-200%\n1,028,438\n50-100%\n700,804\n30-50%\n317,031\n20-30%\n2,258,254\n17.6-20%\n294,231\n\nДовжина смуги — це кількість активних оголошень у кожній смузі. Смуга «200%+» означає, що комісія перевищує удвічі суму 15% від виручки продавця.\n\nПриклад із розв’язком\n67%\n\nПри розміщенні оголошення покупець сплачує $0.03 адже продавець отримує $0.01 а сайт Valve містить $0.02 — два мінімальні розміри в один цент. Як частка від суми, яку заплатив покупець, це 67%; як частка від виручки продавця — 200%.\n\nПовний набір даних: cs2sh-steam-fee-census.json →\n\nОдин і той самий предмет: у саду та поза ним\nПокупки на сайті Steam обходяться дорожче. Майже завжди.\n\nДля кожного товару, ціна на який вказана як на сайті Steam, так і принаймні на одній сторонній торговельній платформі, ми порівняли найнижчу ціну продажу на сайті Steam з найнижчою ціною продажу поза ним. По всьому 28,700 щодо закладів, «Steam» є дорожчим 86.4% у більшості випадків, за медіаною +35.7%.\n\nМедіана страхового внеску за програмою «Steam» за ціновими діапазонами\nменше $0.50\n+48.3%\n$0.50-2\n+36.5%\n$2-10\n+29.6%\n$10-50\n+28.6%\n$50-250\n+36.3%\n$250-1k\n+51.1%\nпонад $1,000\n+67.9%\n\nКрива має U-подібну форму. Найдешевше купувати на сайті Steam у $10–$50 стрічкою та найдорожчими на обох кінцях.\n\nЧому важливий дорогий сегмент\n+67.9%\n\nВище $1,000, медіана вартості об’єктів у списку «Steam» 67.9% перевищує найдешевшу пропозицію поза цим списком — і лише 1,040 таких об’єктів взагалі є на сайті Steam.\n\nПочинаючи приблизно з суми в $1,800, порівняння стає неможливим, оскільки правила Valve повністю забороняють розміщення таких оголошень. Покриття Steam щодо товарів, вартість яких перевищує встановлений ліміт, становить 1.9%. Переглянути весь рейтинг →\n\nПовний набір даних: cs2sh-walled-garden-premium.json →\n\nПремія сама по собі не є висновком: сервіс «Steam» пропонує миттєву доставку та відсутність ризику контрагента, і покупці цілком можуть платити за це. Що можна виміряти, так це розмір розриву та той факт, що гроші, які його долають, не можуть повернутися назад — про це йтиметься в наступному розділі.\n\nГроші надходять, але не витрачаються\n128.1 мільйонів доларів виділено на замовлення, які не можна скасувати.\n\nЗамовлення на купівлю на Steam є попередньо оплаченим: гроші виходять з гаманця покупця в той самий момент, коли замовлення оформлено. Кошти в гаманці Steam не можна відкликати — їх можна витратити лише на платформі Steam. Підсумувавши всі рівні цін у книзі покупок кожного відстежуваного товару, можна отримати загальну суму зафіксованих, невилучних коштів.\n\n$128.1M\nзобов'язується виконати замовлення на купівлю Steam\n170.6М\nдіючі індивідуальні замовлення на купівлю з власним фінансуванням\n$105.8M\nринкова вартість об’єктів нерухомості, розташованих навпроти них\n$15.9M\nЧастка компанії Valve у разі, якщо всі об’єкти нерухомості будуть продані за заявленою ціною\nЩо являє собою цей показник, а що — ні\n1\nЦе реальні кошти, які вже були внесені. Кожен врахований долар був списаний з гаманця і наразі зарахований на відкрите замовлення за різними типами товарів на сайті 31,253.\n2\nЦе а не дохід а не твердження щодо балансу компанії «Valve». Де саме зберігаються акції в обігу та в чиїх бухгалтерських книгах вони відображаються, тут не вказується.\n3\nЦе — моментальний знімок, а не потік. Покупець може скасувати замовлення, після чого кошти повертаються на гаманець — але все ще залишаються на сайті Steam.\n4\nСуть саме в цих «дверях в один бік». Ринок, валюту якого неможливо обміняти на готівку, є причиною того, що вкрадені товари реалізуються вимкнути Steam а не на ньому.\n\nМетод: кожен рівень ціни кожного відстежуваного списку заявок на купівлю, помножений на кількість заявок, що знаходяться на цьому рівні. Повний набір даних: cs2sh-steam-locked-capital.json →\n\nФактичні ціни продажу, а не запитувані ціни · одна торговельна платформа · за останні 90 днів\n30.9 мільйонів доларів насправді перейшли з рук в руки — на найменшій із п’яти полиць.\n\nОдноразова угода за високою ціною може стосуватися рідкісного виробу ручної роботи або варіанту дешевого базового товару з наклейкою (наприклад, e.g — товар за $30, який було продано за $9,772). «Висока» — це найвища ціна завершеної угоди, а не звичайна ціна товару.\n\nКожна друга цифра на цій сторінці відображає те, що перелічені. Цей прилад вимірює те, що було продано. Компанія «Skinport» оприлюднює дані про власні укладені угоди, і за останні 90 днів їхня загальна кількість склала 1,219,143 продажі вартість $30,927,032, у середньому по $25.37 за штуку.\n\n1.22М\nреалізовані продажі за 90 днів, один торговий майданчик\n$30.9M\nоборот за той самий період\n$125M\nрічний темп зростання — мінімальний рівень, а не прогноз\n~2%\nЧастка компанії Skinport у сегменті акцій, що перевищують ліміт, за ринковою вартістю\nЗвідки взявся оборот\nменше $1\n0.5%\n$1-10\n5.8%\n$10-100\n22.2%\n$100-1k\n59.4%\n$1k-1.8k\n6.9%\nвище межі, встановленої програмою «Steam»\n5.3%\n\nДовжина стовпчика відображає оборот; цифра показує частку цього рівня в загальному обсязі. 59.4% з коштів, що були перераховані в категорії $100–$1k, на 71,437 продажів.\n\nНад кепкою «Valve» продажі все ще тривають\n492\n\nзавершені продажі товарів, ціна яких перевищує встановлений ліміт «Steam», на суму $1,643,938, серед різних типів товарів 76 — на торговельному майданчику, який займає приблизно 2% цієї полиці. Жодна з цих продажів не могла відбутися на сайті Steam.\n\nПовний набір даних: cs2sh-offsteam-90d-dynamics.json → · максимальні значення →\n\nSkinport є ОДНИМ із ринків сторонніх розробників, які тут відстежуються, і, з огляду на те, що його ринкова капіталізація перевищує поріг «Steam», він є найменшим із п’яти (приблизно 2% цієї групи). Кожен загальний показник тут є мінімальним рівнем позаігровоїSteam економіки, а не її оцінкою. Дані з Steam не використовуються.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Ринкова економіка — дві економіки та верхня межа котирувань"
          },
          {
            "level": 2,
            "id": null,
            "text": "Одна інфраструктура. Дві економіки."
          },
          {
            "level": 2,
            "id": null,
            "text": "Реєстр платформ"
          },
          {
            "level": 2,
            "id": null,
            "text": "Різниця в ціні є відчутною."
          },
          {
            "level": 3,
            "id": null,
            "text": "П’ять торгових майданчиків: товари, вартість яких перевищує встановлений ліміт «Steam»"
          },
          {
            "level": 3,
            "id": null,
            "text": "Розподіл цін вище верхньої межі"
          },
          {
            "level": 3,
            "id": null,
            "text": "Найпопулярніші товари — найнижча підтверджена ціна продажу на п’яти торгових майданчиках"
          },
          {
            "level": 2,
            "id": null,
            "text": "Оголошена винагорода становить 15%.. У більшості оголошень пропонують вищу винагороду."
          },
          {
            "level": 3,
            "id": null,
            "text": "Комісія, що стягується, як частка від номінальної вартості 15%"
          },
          {
            "level": 3,
            "id": null,
            "text": "Приклад із розв’язком"
          },
          {
            "level": 2,
            "id": null,
            "text": "Покупки на сайті Steam обходяться дорожче. Майже завжди."
          },
          {
            "level": 3,
            "id": null,
            "text": "Медіана страхового внеску за програмою «Steam» за ціновими діапазонами"
          },
          {
            "level": 3,
            "id": null,
            "text": "Чому важливий дорогий сегмент"
          },
          {
            "level": 2,
            "id": null,
            "text": "128.1 мільйонів доларів виділено на замовлення, які не можна скасувати."
          },
          {
            "level": 2,
            "id": null,
            "text": "30.9 мільйонів доларів насправді перейшли з рук в руки — на найменшій із п’яти полиць."
          },
          {
            "level": 3,
            "id": null,
            "text": "Звідки взявся оборот"
          },
          {
            "level": 3,
            "id": null,
            "text": "Над кепкою «Valve» продажі все ще тривають"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/uk/#market-gap-section",
          "https://phishdestroy.io/steam_dossier/uk/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/uk/#proxy-bypass-explainer",
          "https://phishdestroy.io/steam_dossier/uk/elite_skins.html",
          "https://phishdestroy.io/steam_dossier/uk/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/uk/skin_atlas.html#grading",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-steam-fee-census.json",
          "https://phishdestroy.io/steam_dossier/uk/skin_atlas.html#cliff",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-walled-garden-premium.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-steam-locked-capital.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-offsteam-90d-dynamics.json",
          "https://phishdestroy.io/steam_dossier/uk/skin_atlas.html#highs"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/uk/market_economics.content.json",
      "export_json_sha256": "1747d2745fd8096efca4954ba56a56f94d88446c8f74a7a177a59179fc9809a5"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "uk/regulatory_act_print.html",
      "language": "uk",
      "title": "ЗАКОН ПРО СУДОВИЙ АУДИТ: Valve Steam Веб-сайт API Екосистема та комерційне використання (Посилання: VAL-REG-2026-09)",
      "source_url": "https://phishdestroy.io/steam_dossier/uk/regulatory_act_print",
      "source_html_sha256": "8a5498b7e5eafe5b1b8fb6a9b7eed0806d572dba23e21f6af42aca766fc3c0b6",
      "exported_at": "2026-09-29T00:19:34.621Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "regulatory_act_print.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/uk/regulatory_act_print.pdf?v=print-20260929-v5",
        "sha256": "af5a702106fdb90ce53e9f739a26879da4f6dfa5a043caa966200e9f43619086",
        "bytes": 193991,
        "pages": 14
      },
      "integrity": {
        "signed_object": "regulatory_act_print.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "regulatory_act_print.content.json.asc",
        "digest_file": "regulatory_act_print.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify regulatory_act_print.content.json.asc regulatory_act_print.content.json",
          "sha256sum -c regulatory_act_print.content.json.sha256"
        ]
      },
      "content": {
        "text": "phishdestroy.io · Коаліція з криміналістичних досліджень · Універсальний реєстр публічних даних\nСПРАВА: VAL-REG-2026-09-EVID\nПРОІСХОДЖЕННЯ: phishdestroy.io/steam_dossier/\nПРАВА: УСІ ПРАВА ПЕРЕДАЮТЬСЯ ЛЮДСТВУ\nЗакон про судово-бухгалтерський аудит та нормативний додаток\nСистематичне надання послуг «API» сторонніми організаціями, архітектура автоматизованого обходу та невиконання договірних зобов’язань в екосистемі «Valve» Steam\nДомен-видавецьphishdestroy.io\nЦільова платформаValve Steam / Steamworks\nОсновний вектор автентифікаціїSteam OpenID 2.0 / Веб-сайт API\nЮридична присвята«Усі права на людство» (CC0)\nРозділ I: Меморандум керівництва та висновки щодо фактівПОСИЛАННЯ: MEMO-SUMMARY-01\n\nЦей документ є офіційним актом судово-експертного аудиту, в якому аналізується взаємодія між опублікованими комерційними умовами корпорації «Valve», її технічними кінцевими точками аутентифікації та виявленими комерційними платформами третіх сторін. Аудит було проведено за допомогою пасивного спостереження за мережею без аутентифікації, перевірки реєстрації на сайті RDAP та аналізу загальнодоступних телеметричних даних Link Filter.\n\nОсновна інформація: Емпіричні спостереження свідчать про систематичну невідповідність між публічними договірними запевненнями компанії «Valve» та її виробничою інфраструктурою. Хоча Угода з абонентами «Steam» (SSA) суворо забороняє несанкціоноване комерційне використання (§ 2.G), автоматизовану взаємодію за допомогою ботів/скриптів (§ 4.C) та передачу облікових записів (§ 1.C), корпорація «Valve» продовжує надавати інфраструктуру для оперативної програмної аутентифікації за OpenID та запитів щодо наявності товарів щонайменше 175 комерційним суб’єктам, які генерують обсяги вторинних транзакцій у розмірі кількох мільярдів доларів.\n\n175\nКомерційні оператори, що пройшли аудит\n44\nХости автентифікації з окремими доменами\n26\nПари проксі-серверів з розділенням фільтрів\n100%\nНезастосовані положення § 2.G / § 4.C Закону про соціальне забезпечення (SSA)\n0\nПримусові скасування авторизацій\nВідповідні договірні та законодавчі норми\nSSA § 2.G\nЗаборона комерційного використання: Категорично забороняється використання Контенту та Послуг у комерційних цілях без попереднього письмового дозволу корпорації «Valve».\nSSA § 4.C\nОбмеження щодо автоматизації: Категорично забороняється використання скриптів, торгових ботів, макросів або систем, що не керуються людиною, для взаємодії зі службами та ринками Steam.\nSSA § 1.C\nВимоги щодо особистого використання: Обмежує використання облікових записів виключно особистими цілями; категорично забороняє продаж, оренду, передачу або обмін обліковими записами користувачів Steam.\nЗакон ЄС про безпеку даних (DSA) (2022/2065)\nОцінка системного ризику (ст. 34/35): Дуже великі онлайн-платформи (VLOP) повинні активно виявляти, оцінювати та мінімізувати системні ризики, що виникають внаслідок автоматизованого зловживання та несанкціонованого комерційного використання.\nРозділ II: Реєстр доказів А — Задокументовані пари з розділеними фільтрами зв’язків (маршрути 26)ПОСИЛАННЯ: EX-SPLIT-LEDGER\n\nКриміналістичний аналіз методів ухилення від виявлення з використанням розділених доменів: У рамках системи фільтрації посилань «Steam» від компанії «Valve» (steamcommunity.com/linkfilter/?url=...), коли кінцевий користувач натискає на посилання, що веде на платформу, позначену як азартна або чорнорингова, на сайті Valve з’являється помітне попередження («Посилання заблоковано! ... позначено як потенційно шкідливе»). Однак криміналістичне відстеження маршруту показує, що комерційні платформи 26 працюють на архітектура з розділеними доменами: хоча основний комерційний домен БЛОКУЄТЬСЯ у фільтрі посилань, другорядний домен, на якому розміщено кінцеву точку повернення OpenID сайту Valve, позначений як «ЧИСТИЙ». Сервери OpenID сайту Valve без перебоїв приймають запити на автентифікацію від цих проксі-хостів, що дозволяє зняти попередження про небезпеку для користувачів і водночас продовжувати обробку входів у систему.\n\n#\tОсновний комерційний домен\tГоловний фільтр\tДомен проксі-сервера аутентифікації OpenID\tФільтр автентифікації\tRDAP Зареєстровано\tОснова обліку\n01\trollbit.com\tBLOCKED\trbsnin.com\tCLEAN\t2026-09-18\tPASSIVE_CAPTURE\n02\tskin.club\tBLOCKED\tsc-auth.net\tCLEAN\t2019-04-02\tPASSIVE_CAPTURE\n03\thowl.gg\tBLOCKED\thowl.uno\tCLEAN\t2026-08-11\tPASSIVE_CAPTURE\n04\tduelbits.com\tBLOCKED\tswitchflips.com\tCLEAN\t2020-04-21\tPASSIVE_CAPTURE\n05\tcsgofast.com\tBLOCKED\tsteam-login.authtofast.com\tCLEAN\t2026-06-30\tPASSIVE_CAPTURE\n06\tfarmskins.com\tBLOCKED\tsteam.kobal.cc\tCLEAN\t2017-01-07\tPASSIVE_CAPTURE\n07\tcobaltlab.tech\tBLOCKED\tcobaltauth.com\tCLEAN\t2025-01-07\tPASSIVE_CAPTURE\n08\tcsgo.net\tBLOCKED\tcn2.easylot.net\tCLEAN\t2016-09-03\tPASSIVE_CAPTURE\n09\tggdrop.com\tBLOCKED\tggauth.com\tCLEAN\t2023-05-03\tPASSIVE_CAPTURE\n10\trustchance.com\tBLOCKED\thgfuihd.com\tCLEAN\t2019-01-27\tPASSIVE_CAPTURE\n11\tskin.fans\tBLOCKED\tauth.skinfans.com\tCLEAN\t2018-07-16\tPASSIVE_CAPTURE\n12\tskinport.com\tBLOCKED\tskinport.app\tCLEAN\t2020-06-20\tPASSIVE_CAPTURE\n13\tskins.cash\tBLOCKED\tskinscash.live\tCLEAN\t2019-12-05\tPASSIVE_CAPTURE\n14\ttf2hunt.com\tBLOCKED\trstspcl.com\tCLEAN\t2020-08-08\tPASSIVE_CAPTURE\n15\tdaddyskins.com\tBLOCKED\tgo-go-daddy.com\tCLEAN\t2019-01-26\tPASSIVE_CAPTURE\n16\tkey-drop.com\tBLOCKED\tkdauth.com\tCLEAN\t2026-05-13\tPASSIVE_CAPTURE\n17\tclash.gg\tBLOCKED\tclggauth.com\tCLEAN\t2024-09-16\tPASSIVE_CAPTURE\n18\tc5game.com\tBLOCKED\twww.imbastar.com\tCLEAN\t2016-02-27\tPASSIVE_CAPTURE\n19\tswap.gg\tBLOCKED\tswapauth.com\tCLEAN\t2018-10-06\tPASSIVE_CAPTURE\n20\tshadowpay.com\tBLOCKED\tthelogins.com\tCLEAN\t2018-01-22\tPASSIVE_CAPTURE\n21\tcsgocases.com\tBLOCKED\tlog-1n.com\tCLEAN\t2017-11-27\tPASSIVE_CAPTURE\n22\tcsgogem.com\tBLOCKED\tapi.csgem.com\tCLEAN\t2014-03-08\tPASSIVE_CAPTURE\n23\tgamdom.com\tBLOCKED\tlogin.gambldom.com\tCLEAN\t2017-09-24\tPASSIVE_CAPTURE\n24\t12cs.fail\tBLOCKED\tfail.games\tCLEAN\t2021-08-24\tPASSIVE_CAPTURE\n25\tskinsnipe.com\tBLOCKED\tpricing.tradeupspy.com\tCLEAN\t2020-03-11\tPASSIVE_CAPTURE\n26\tcsgobig.com\tBLOCKED\tletmeinbig.com\tCLEAN\t2023-01-20\tPASSIVE_CAPTURE\n\n* Примітка: Пасивні перевірки, виконані щодо неавтентифікованих кінцевих точок фільтра посилань Steam на сайтах 2026-09-19 та 2026-09-21.. Необроблені тіла відповідей HTTP та дайджести SHA-256 зберігаються у наборі даних репозиторію (steam_tos_assets/linkfilter-2026-09-22.json).\n\nРозділ III: Реєстр B — Повний перелік комерційних суб’єктів господарювання, що пройшли аудит за програмою «175»ПОСИЛАННЯ: EX-175-, MASTER-CENSUS\n\nУ наведеному нижче реєстрі детально описано всі сторонні комерційні платформи 175, які активно перевірено в базі даних аудиту. Кожен запис містить назву суб’єкта господарювання, основний комерційний домен, виявлений маршрут аутентифікації OpenID Steam, класифікацію діяльності, відповідності щодо порушень договірних зобов’язань (SSA § 2.G, SSA § 4.C, SSA § 1.C) та поле «Дія», зафіксоване у вихідному наборі даних. Позначка «Див. датовані докази» вказує читачеві на підтверджуючі записи; вона не свідчить про те, що «Valve» не вживала жодних заходів. Відсутність поля «дії» позначається як «не встановлено».\n\nДодаток\tНазва організації та основний домен\tСпостережуваний маршрут автентифікації / проксі-сервер\tКласифікація\tПорушення умов договору\tValve Дія\nEX-001\tCSGORoll\ncsgoroll.com\n\t\nwww.csgoroll.com\nDIRECT\n\tSkin Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-002\tCSGOEmpire\ncsgoempire.com\n\t\ncsgoempirelogin4.com\nSPLIT PROXY\n\tCasino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-003\tRollbit\nrollbit.com\n\t\nrbsnin.com\nSPLIT PROXY\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-004\t500 Casino\n500.casino\n\t\nfivezerozero.co\nSPLIT PROXY\n\tLicenced Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-005\tCSGOBig\ncsgobig.com\n\t\ncsgobig.com\nDIRECT\n\tRoulette/Slots\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-006\tCaseDrop\ncasedrop.com\n\t\ncasedrop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-007\tRustReaper\nrustreaper.com\n\t\nrustreaper.com\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-008\tBanditCamp\nbanditcamp.com\n\t\nbanditcamp.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-009\tSkinBox\nskinbox.com\n\t\nskinbox.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-010\tTastyDrop\ntastydrop.com\n\t\ntastydrop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-011\tCSGOPolygon\ncsgopolygon.gg\n\t\ncsgopolygon.gg\nDIRECT\n\tRoulette Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-012\tMagicDrop\nmagicdrop.ru\n\t\nmagicdrop.ru\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-013\tCSDice\ncsdice.com\n\t\ncsdice.com\nDIRECT\n\tDice Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-014\tRustly\nrustly.com\n\t\nrustly.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-015\tSkinOdds\nskinodds.com\n\t\nskinodds.com\nDIRECT\n\tUpgrader Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-016\tCSGOWin\ncsgowin.com\n\t\ncsgowin.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-017\tCSGORun\ncsgorun.net\n\t\ncsgorun.net\nDIRECT\n\tCrash Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-018\tOpenSkins\nopenskins.com\n\t\nopenskins.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-019\tRustBet\nrustbet.com\n\t\nrustbet.com\nDIRECT\n\tRust Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-020\tCSGOMagic\ncsgomagic.com\n\t\ncsgomagic.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-021\tCSGOBounty\ncsgobounty.com\n\t\ncsgobounty.com\nDIRECT\n\tUpgrader/Contract\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-022\tEZSkins\nezskins.com\n\t\nezskins.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-023\tRustCases\nrustcases.com\n\t\nrustcases.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-024\tCSGOReaper\ncsgoreaper.com\n\t\ncsgoreaper.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-025\tCSGOCases\ncsgocases.com\n\t\ncsgocases.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-026\tCSGO-Skins\ncsgo-skins.com\n\t\ncsgo-skins.com\nDIRECT\n\tCase Upgrader\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-027\tCSGONet\ncsgonet.com\n\t\ncsgonet.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-028\tWTFSkins\nwtfskins.com\n\t\nwtfskins.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-029\tCSGOFast\ncsgofast.com\n\t\nsteam-login.authtofast.com\nSPLIT PROXY\n\tRoulette Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-030\tDuelbits\nduelbits.com\n\t\nswitchflips.com\nSPLIT PROXY\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-031\tFlameCases\nflamecases.com\n\t\nflamecases.com\nDIRECT\n\tCase Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-032\tFarmskins\nfarmskins.com\n\t\nsteam.kobal.cc\nSPLIT PROXY\n\tCase Opener\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-033\tCSGOLuck\ncsgoluck.com\n\t\ncsgoluck.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-034\tGamedom\ngamedom.com\n\t\ngamedom.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-035\tSkin.Club\nskin.club\n\t\nsc-auth.net\nSPLIT PROXY\n\tCase Battles\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-036\tDaddySkins\ndaddyskins.com\n\t\ndaddyskins.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-037\tInsane.gg\ninsane.gg\n\t\napi.insane.gg\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-038\tRustix\nrustix.gg\n\t\nrustix.gg\nDIRECT\n\tRust Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-039\tSkins.Club\nskins.club\n\t\nskins.club\nDIRECT\n\tSkin Upgrade\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-040\tCSGOHouse\ncsgohouse.org\n\t\ncsgohouse.org\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-041\tSkinRave\nskinrave.net\n\t\nskinrave.net\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-042\tBloodyCase_GG\nbloodycase.gg\n\t\nbloodycase.gg\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-043\tCSGOClicker\ncsgoclicker.com\n\t\ncsgoclicker.com\nDIRECT\n\tClicker/Upgrade\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-044\tRustBet_GG\nrustbet.gg\n\t\nrustbet.gg\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-045\tCS_Drop\ncs-drop.com\n\t\ncs-drop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-046\tHellStore\nhellstore.net\n\t\nhellstore.net\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-047\tRustLoot\nrustloot.com\n\t\nrustloot.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-048\tCSGO_Case\ncsgo-case.com\n\t\ncsgo-case.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-049\tCS2Skin\ncs2skin.com\n\t\ncs2skin.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-050\tJuice_GG\njuice.gg\n\t\nletmeinjuice.com\nSPLIT PROXY\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-051\tGGDrop\nggdrop.com\n\t\nggauth.com\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-052\tCSGOGem\ncsgogem.com\n\t\ncsgogem.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-053\tRainbet\nrainbet.com\n\t\nservices.rainbet.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-054\tHowl_GG\nhowl.gg\n\t\nhowl.uno\nSPLIT PROXY\n\tSkins Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-055\tChicken_GG\nchicken.gg\n\t\nchicken.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-056\tCSGOCasino_GG\ncsgocasino.gg\n\t\napi.csgocasino.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-057\tHunt_GG\nhunt.gg\n\t\napi.hunt.gg\nDIRECT\n\tSkins Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-058\tCSBattle\ncsbattle.com\n\t\ncsbattle.com\nDIRECT\n\tCase Battles\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-059\tSkinRave_GG\nskinrave.gg\n\t\napi.skinrave.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-060\tCSDouble\ncsdouble.gg\n\t\ncsdouble.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-061\tRustChance\nrustchance.com\n\t\nhgfuihd.com\nSPLIT PROXY\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-062\tRustClash\nrustclash.com\n\t\nrustclash.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-063\tCobaltLab\ncobaltlab.tech\n\t\ncobaltauth.com\nSPLIT PROXY\n\tRust Automation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-064\tRaided_GG\nraided.gg\n\t\napi.raided.gg\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-065\tRustNeo\nrustneo.gg\n\t\nrustneo.gg\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-066\tSplits_GG\nsplits.gg\n\t\nsplits.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-067\tUpgrader_Pro\nupgrader.pro\n\t\nupgauth.space\nSPLIT PROXY\n\tSkin Upgrader\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-068\tSkinFans\nskin.fans\n\t\nauth.skinfans.com\nSPLIT PROXY\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-069\tHotPizza\nhotpizza.one\n\t\nhotpizza.one\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-070\tG4Skins\ng4skins.com\n\t\nauth.g4s.to\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-071\t12CS_Fail\n12cs.fail\n\t\n12cs.fail\nDIRECT\n\tCrash Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-072\tTF2Royal\ntf2royal.com\n\t\ntf2auth.com\nSPLIT PROXY\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-073\tTF2Easy\nwww.tf2easy.com\n\t\nwww.tf2easy.com\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-074\tTF2Hunt\ntf2hunt.com\n\t\nrstspcl.com\nSPLIT PROXY\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-075\tTF2Bet\ntf2.bet/coinflip\n\t\ntf2.bet\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-076\tTF2Blaze\ntf2blaze.com\n\t\ntf2blaze.com\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-077\tOpenStars_GG\nopenstars.gg\n\t\nopenstars.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-078\tShuffle_Com\nshuffle.com\n\t\nshuffle.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-079\tSkins.com\nskins.com\n\t\napi.skins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-080\tWhite.Market\nwhite.market\n\t\nwhite.market\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-081\tBuff.Market\nbuff.market\n\t\nbuff.market\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-082\tAvan.Market\navan.market\n\t\navan.market\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-083\tCS.MONEY\ncs.money\n\t\nauth.dota.trade\nSPLIT PROXY\n\tTrading Engine\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-084\tUUSkins\nuuskins.com\n\t\nuuskins.com\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-085\tYouPin898\nyoupin898.com\n\t\nyoupin898.com\nDIRECT\n\tMass Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-086\tMoon.Market\nmoon.market\n\t\nmoon.market\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-087\tCSFloat\ncsfloat.com\n\t\ncsgofloat.com\nSPLIT PROXY\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-088\tSkin.Land\nskin.land\n\t\nauth.skin.land\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-089\tC5Game\nc5game.com\n\t\nc5game.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-090\tHaloSkins\nhaloskins.com\n\t\nhaloskins.com\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-091\tBuff.163\nbuff.163.com\n\t\nbuff.163.com\nDIRECT\n\tCorporate Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-092\tWaxpeer\nwaxpeer.com\n\t\nwaxpeer.com\nDIRECT\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-093\tCS.MONEY Bot\ncs.money\n\t\nauth.dota.trade\nSPLIT PROXY\n\tBot Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-094\tMarket.CSGO\nmarket.csgo.com\n\t\ndota2.net\nSPLIT PROXY\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-095\tSkinport\nskinport.com\n\t\nskinport.app\nSPLIT PROXY\n\tRegulated Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-096\tSkinFlow\nskinflow.gg\n\t\napi.skinflow.gg\nDIRECT\n\tMarketplace/Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-097\tDMarket\ndmarket.com\n\t\ndmarket.com\nDIRECT\n\tUS Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-098\tSkin.place\nskin.place\n\t\napi.skin.place\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-099\tSkinsMonkey\nskinsmonkey.com\n\t\nskinsmonkey.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-100\tSkinBaron\nskinbaron.de\n\t\nskinbaron.com\nSPLIT PROXY\n\tCorporate Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-101\tSteam\nsteamcommunity.com/market\n\t\nsteamcommunity.com/market\nDIRECT\n\tOfficial Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-102\tRustTM\nrust.tm\n\t\ndota2.net\nSPLIT PROXY\n\tRust Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-103\tPirateSwap\npirateswap.com\n\t\nlogin.pirateswap.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-104\tMannco.Store\nmannco.store\n\t\nmannco.store\nDIRECT\n\tTF2 Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-105\tSkinSwap\nskinswap.com\n\t\napi.skinswap.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-106\tLootFarm\nlootfarm.com\n\t\nlootfarm.com\nDIRECT\n\tTrading Platform\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-107\tRustskins\nrustskins.com\n\t\nrustskins.com\nDIRECT\n\tRust Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-108\tExeSkins\nexeskins.com\n\t\nexeskins.com\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-109\tBalticSkins\nbalticskins.com\n\t\nbalticskins.com\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-110\tCS.Trade\ncs.trade\n\t\ncs.trade\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-111\tRapidSkins\nrapidskins.com\n\t\napi.rapidskins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-112\tTradeIt\ntradeit.gg\n\t\nconnect-tradeit.com\nSPLIT PROXY\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-113\tKrakatoa\nkrakatoa.com\n\t\nkrakatoa.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-114\tShadowPay\nshadowpay.com\n\t\nshadowpay.com\nDIRECT\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-115\t49skins\n49skins.com\n\t\napi.49skins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-116\tSkinVault\nskinvault.gg\n\t\napi.skinvault.gg\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-117\tAim Market\naim.market\n\t\naim.market\nDIRECT\n\tSkins Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-118\tSkinout\nskinout.gg\n\t\nauth.skinout.gg\nDIRECT\n\tInstant Sell Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-119\tNTSkins\nntskins.com\n\t\nntskins.com\nDIRECT\n\tSkins Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-120\tIGXE\nigxe.cn\n\t\nigxe.cn\nDIRECT\n\tChinese Powerhouse\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-121\tSwap.gg\nswap.gg\n\t\nswap.gg\nDIRECT\n\tAutomated Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-122\tBitskins\nbitskins.com\n\t\nbitskins.com\nDIRECT\n\tCash-out Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-123\tGamerPay\ngamerpay.gg\n\t\ngamerpay.gg\nDIRECT\n\tP2P Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-124\tTF2Mart\ntf2mart.com\n\t\ntf2mart.com\nDIRECT\n\tTF2 Automation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-125\tSkinBid\nskinbid.com\n\t\nskinbid.com\nDIRECT\n\tSkin Auctions\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-126\tLootBear\nlootbear.com\n\t\nlootbear.com\nDIRECT\n\tSkin Rental\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-127\tBackpack.tf\nbackpack.tf\n\t\nbackpack.tf\nDIRECT\n\tTF2 Valuation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-128\tScrap.tf\nscrap.tf\n\t\nscrap.tf\nDIRECT\n\tTF2 Scrap Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-129\tMarketplace.tf\nmarketplace.tf\n\t\nmarketplace.tf\nDIRECT\n\tTF2 Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-130\tSTNTrading\nstntrading.eu\n\t\nstntrading.eu\nDIRECT\n\tTF2 Botnet\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-131\tSkins.Cash\nskins.cash\n\t\nskinscash.live\nSPLIT PROXY\n\tInstant Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-132\tSkinWallet\nskinwallet.com\n\t\nskinwallet.com\nDIRECT\n\tInstant Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-133\tDota2Market\ndota2market.com\n\t\ndota2market.com\nDIRECT\n\tDota 2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-134\tCSGO.NET\ncsgo.net\n\t\ncn2.easylot.net\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-135\tCybershoke\ncybershoke.net\n\t\nauth.cybershoke.net\nDIRECT\n\tCommunity Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-136\tXPlay_GG\nxplay.gg\n\t\nxplay.gg\nDIRECT\n\tServer Network\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-137\tFastCup\nfastcup.net\n\t\napi.fastcup.net\nDIRECT\n\tMatchmaker Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-138\tEsportal\nesportal.com\n\t\nesportal.com\nDIRECT\n\tMatchmaking Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-139\tGamersClub\ngamersclub.com.br\n\t\ngamersclub.com.br\nDIRECT\n\tLATAM Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-140\tLeetify\nleetify.com\n\t\nleetify.com\nDIRECT\n\tSaaS Analytics\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-141\tScope_GG\nscope.gg\n\t\nscope.gg\nDIRECT\n\tSaaS Analytics\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-142\tTradeUpSpy\ntradeupspy.com\n\t\napi.tradeupspy.com\nDIRECT\n\tSaaS Tools\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-143\tEpidemic_GG\nepidemic.gg\n\t\nepidemic.gg\nDIRECT\n\tSaaS Tools\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-144\tCSDeals\ncs.deals\n\t\napi.cs.deals\nDIRECT\n\tMarketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-145\tPricempire\npricempire.com\n\t\npricempire.com\nDIRECT\n\tSaaS Price DB\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-146\tCS2Stash\ncs2stash.com\n\t\ncs2stash.com\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-147\tCSGOSkins\ncsgoskins.gg\n\t\ncsgoskins.gg\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-148\tSteamAnalyst\nsteamanalyst.com\n\t\nsteamanalyst.com\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-149\tSteamCardExchange\nsteamcardexchange.net\n\t\nsteamcardexchange.net\nDIRECT\n\tTrading Exchange\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-150\tDotaBuff\ndotabuff.com\n\t\ndotabuff.com\nDIRECT\n\tSaaS Tracker\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-151\tTracker_GG\ntracker.gg\n\t\ntracker.gg\nDIRECT\n\tSaaS Tracker\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-152\tFSB Market (an anonymized label; the original name is withheld here)\nFSB Market\n\t\nFSB Market\nDIRECT\n\tMass Blackmarket\tSSA § 2.G, SSA § 4.C, SSA § 1.C\tSee dated evidence\nEX-153\tFunPay\nfunpay.com\n\t\nfunpay.com\nDIRECT\n\tAccount Exchange\tSSA § 2.G, SSA § 4.C, SSA § 1.C\tSee dated evidence\nEX-154\tPlayerAuctions\nplayerauctions.com\n\t\nplayerauctions.com\nDIRECT\n\tGrey Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-155\tEldorado.gg\neldorado.gg\n\t\neldorado.gg\nDIRECT\n\tAccount Portal\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-156\tG2A\ng2a.com\n\t\ng2a.com\nDIRECT\n\tMass Key Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-157\tKinguin\nkinguin.net\n\t\nkinguin.net\nDIRECT\n\tMass Key Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-158\tG2G.com\ng2g.com\n\t\ng2g.com\nDIRECT\n\tVirtual Services\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-159\tPlayerup\nplayerup.com\n\t\nplayerup.com\nDIRECT\n\tAccount Broker\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-160\tZ2U.com\nz2u.com\n\t\nwww.z2u.com\nDIRECT\n\tReady-Account Hub\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-161\tSmurfHub\nsmurfhub.net\n\t\nsmurfhub.net\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-162\tSmurfAccounts\nsmurfaccounts.com\n\t\nsmurfaccounts.com\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-163\tBuyCSGORank\nbuycsgorank.com\n\t\nbuycsgorank.com\nDIRECT\n\tRank Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-164\tCSGOSmurfKings\ncsgosmurfkings.com\n\t\ncsgosmurfkings.com\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-165\tSmurfStore_Co\nsmurfstore.co\n\t\nsmurfstore.co\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-166\tSteamLvlUp\nsteamlvlup.com\n\t\nsteamlvlup.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-167\tSteamLevels\nsteamlevels.com\n\t\nsteamlevels.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-168\tLevelSteam\nlevelsteam.com\n\t\nlevelsteam.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-169\tSteamLevelU\nsteamlevelu.com\n\t\nsteamlevelu.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-170\tEloKing\neloking.com\n\t\neloking.com\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-171\tBoosteria\nboosteria.org\n\t\nboosteria.org\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-172\tOvergear\novergear.com\n\t\novergear.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-173\tBlazingBoost\nblazingboost.com\n\t\nblazingboost.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-174\tDota2Boost\ndota2boost.com\n\t\ndota2boost.com\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-175\tBuyBoost\nbuyboost.com\n\t\nbuyboost.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nРозділ IV: Технічна архітектура та механізми аутентифікаціїПосилання: TECH-ANALYSIS-01\n\n1. Відсутність перевірки права власності на домен у OpenID 2.0: Реалізація протоколу OpenID 2.0 у Valve (https://steamcommunity.com/openid/login) аналізує openid.return_to та openid.realm параметри без необхідності попередньої реєстрації розробника, криптографічної перевірки автентичності або підтвердження права власності на домен. Будь-який комерційний оператор може перенаправити користувачів на екран входу на сайті Valve і отримати криптографічно підписане підтвердження ідентичності (що містить SteamID у форматі 64-), перенаправлене на довільні домени.\n\n2. Програмний запит щодо рекламного інвентарю та зловживання ключами «API»: Після підтвердження автентифікації користувача через OpenID оператори надсилають запити до публічних та партнерських веб-кінцевих точок API (IEconItems_730/GetPlayerItems) для індексації товарних запасів у режимі реального часу. Мережі автоматизованої торгівлі використовують програмні сесійні токени для надсилання, запитування та прийняття пропозицій про угоди за принципом «рівний-рівному» (P2P), що прямо суперечить забороні на взаємодію з нелюдськими суб’єктами, передбаченій у §4.C Закону про безпеку (SSA).\n\n3. Асиметрія фільтра посилань: Співіснування попереджень про домени, спрямованих на споживачів, та повністю функціональних точок автентифікації створює нормативну суперечність: система телеметрії безпеки Valve класифікує цих операторів як «потенційно шкідливих», проте інфраструктура автентифікації Valve продовжує здійснювати автентифікацію їхніх користувачів.\n\nМетодологія доказового збору та декларація щодо ланцюга відповідальності\n\nЦей документ було створено на основі даних, отриманих із неавтентифікованих мережевих зчитувань, історичних запитів до реєстру RDAP та перевірених криптографічних хеш-маніфестів. Жодні облікові дані користувачів не піддавалися тестуванню на компрометацію та не оброблялися. Усі висновки відображають спостережуваний стан виробничої мережі станом на вересень 2026. Цей документ є незаангажованим технічним доказом, підготовленим для судових, регуляторних та громадських розслідувань.\n\nПІДСУМОК: SHA-256: ПЕРЕВІРЕНО\nc507c9025f93da0aadaf395c4d8882f25973211c318ee8e9b6f18a5b3755e050\nАРХІВ: ВІДКРИТА СУДОВА СПРАВА\nВИДАНО ТА ПІДПИСАНО: phishdestroy.io · Коаліція з криміналістичних досліджень\nПРАВОВИЙ СТАТУС: УСІ ПРАВА ПЕРЕДАЮТЬСЯ ЛЮДСТВУ · CC0 УНІВЕРСАЛЬНИЙ ПУБЛІЧНИЙ ДОМЕН",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Закон про судово-бухгалтерський аудит та нормативний додаток"
          }
        ],
        "links": []
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/uk/regulatory_act_print.content.json",
      "export_json_sha256": "c418fcad77037f206bcb40cef92227c6acffd6a215bd3b5af4cecc03fa9bca5b"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "uk/security_timeline.html",
      "language": "uk",
      "title": "Хронологія подій у сфері безпеки — Досьє «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/uk/security_timeline",
      "source_html_sha256": "334d1faaaa3430694f50d1af111ceced630db507f39f80d791d1ee602caa54fb",
      "exported_at": "2026-09-29T00:19:36.852Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "security_timeline.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/uk/security_timeline.pdf?v=print-20260929-v5",
        "sha256": "497e8f75b5d9d092ee6e52de2ef8ccb8a4f441cc11d9403d70d692cd002f3e53",
        "bytes": 104848,
        "pages": 7
      },
      "integrity": {
        "signed_object": "security_timeline.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "security_timeline.content.json.asc",
        "digest_file": "security_timeline.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify security_timeline.content.json.asc security_timeline.content.json",
          "sha256sum -c security_timeline.content.json.sha256"
        ]
      },
      "content": {
        "text": "ІСТОРІЯ БЕЗПЕКИВИСТАВКА / РОБОТИ, ПОДАНІ НА КОНКУРС «16»\n\n2018 — 2026\n\nХронологія заходів з безпеки — від «2018» до «2026»\n\nЗмінилися заходи безпеки. Слідкуйте за ходом подій.\n\nЩО ДОКАЗУЄ ЦЕЙ РОЗДІЛ\n\nЦей хронологічний звіт відтворює вісім років змін у системі безпеки торгового та аутентифікаційного стеку платформи «Steam». У ньому простежуються: 2018 — впровадження денного блокування торгів; 7-— 2023 — підтвердження ключових операцій через мобільні пристрої; API — 2026 — виведення з обігу сесійних токенів у відповідь на задокументовані методи обходу. Хронологія показує, що оновлення платформи постійно відставали від відомих векторів атак, водночас зберігаючи структурні переваги для комерційних операторів.\n\n← Повернутися до огляду для керівництва\n\nТоргові блокування. Контроль входу. Обмеження «API». Хронологічний звіт про те, що змінилося — і що насправді підтверджують джерела.\n\nОзнайомтеся з хронологією подій ↓\nВІСІМ РОКІВ. ОДИН АЛЬБОМ.16ключові етапи, які слід проаналізувати\n\nКожен запис зберігає дату подання та джерело. Результати перевірки відображаються поруч із ним.\n\nПЕРЕВІРЕНО / 24 09.2026\n10Підтверджена подія та дата\n06Частково підтверджено\n00Невідповідність джерел\n00Потрібне джерело\nЯк читати цей запис\n\nПідтверджена подія та дата: обидва підтверджуються достовірним першоджерелом. Частково підтверджено: відповідна зміна задокументована, але дата або обсяг її застосування залишаються невизначеними. Невідповідність джерел: матеріал, на який наведено посилання, не підтверджує висунуте твердження. Потрібне джерело: У ході цього огляду не було перевірено жодного відповідного джерела з датою. Відсутність підтверджених даних не є доказом того, що подія не відбулася.\n\nДати у невирішених записах — це дати подання, а не підтверджені дати випуску. Оригінальний текст розслідування не переписувався.\n\nХронологія\n01 — 16\nПошук у записіТемаДоказиЗамовлення\n\n16 з публікацій «16» · спочатку найновіші\n\n202609-01Дата подання\nСпільнотаЧастково підтверджено\nПопередження про підозрілі повідомлення в групових чатах\n\nОфіційне повідомлення про бета-версію підтверджує наявність цієї функції на сайті 31 у серпні. Щодо зазначеної на сайті 1 дати випуску стабільної версії у вересні, поки що відсутні конкретні примітки до випуску.\n\nSteam Бета-версія клієнта — 31серпня ↗архів 2026-03-13 ↗\nОригінальний запис та надіслане посилання\n\nАвтоматичне позначення підозрілих чатів\n\nПереглянути наданий вихідний код ↗\n202601-16Дата підтвердження\nAPIПідтверджена подія та дата\nДетальні права доступу та білі списки IP-адрес для ключів видавців (оголошення Valve)\n\n16 січня 2026, Valve опублікували офіційне оголошення щодо Steamworks («НОВИНКА: Покращені права доступу та засоби керування для ключів веб-API») що підтверджує наявність нових інструментів для детального налаштування прав доступу, які дозволяють розробникам розділяти ключі веб-APIів на окремі групи (Загальні відомості, мікротранзакції, економіка та дані про продажі), обмежити використання ключів певними ідентифікаторами додатків та забезпечити дотримання білого списку IP-адрес серверів.\n\nЯвний подвійний стандарт: У цьому офіційному повідомленні зазначається, що компанія «Valve» повністю розбудувала технічну інфраструктуру для детального налаштування прав доступу API та обмежень за IP-адресами, однак навмисно не надає їх звичайним обліковим записам користувачів (steamcommunity.com/dev/apikey). Звичайні ключі користувача API залишаються монолітними, «все або нічого» обліковими даними без білих списків IP-адрес — і саме це технічне упущення робить можливим існування багатомільйонної індустрії перехоплення торгових операцій API.\n\nValve Оголошення — НОВИНКА: Покращені права доступу та засоби керування для ключів веб-API (16 Jan 2026) ↗· Документація: Аутентифікація через веб-APIу Steamworks ↗\nОригінальний запис та надіслане посилання\n\nВеб-сайт Steamworks API Детальні описи\n\nОзнайомтеся з офіційним оголошенням про підтримку Steamworks у грі «Valve» (493839547938902179) ↗\n202507-15Дата підтвердження\nТоргівляПідтверджена подія та дата\nУгоди з CS2 отримують семиденне вікно розвороту\n\nУ опублікованому сьогодні повідомленні Valve оголошено про скасування обмінів предметами в Counter-Strike, здійснених протягом попередніх семи днів. Хоча ця міра була запроваджена з метою запобігання викраденню акаунтів, незалежні економічні аудити (CSMarketCap ↗) зафіксувала $104M (-25%) згорнути за ринковою капіталізацією протягом 24 годин через перебої в роботі системи готівкових розрахунків. Згідно з аналізом Skinvault ↗, у разі спрацьовування механізму розвороту на рахунок автоматично накладається обмеження на денну торгівлю 30-. Влітку 2026, Valve перейшли від глобального обнулення о півночі за UTC до індивідуальних хвилинних таймерів для кожного окремого інструменту (Skin.land ↗).\n\nValve — 15, липень, оголошення про випуск «2025» ↗· Аналіз CSMarketCap ↗\nОригінальний запис та надіслане посилання\n\nЗахист від спекуляцій CS2 / Вікно скасування\n\nПереглянути наданий вихідний код ↗\n202505-14Дата підтвердження\nАутентифікаціяПідтверджена подія та дата\nValve публікує попередження щодо безпеки облікових записів у зв’язку з витоком SMS-повідомлень\n\nОфіційне повідомлення Valve від 14, 2025, стосується безпеки облікових записів та засобів аутентифікації на основі SMS. Хоча в повідомленні основна увага приділяється витоку SMS-повідомлень і підтверджується, що системи Steam не зазнали зломів, воно є офіційним оновленням щодо безпеки станом на зазначену дату.\n\nValve — Примітка щодо безпеки вашого облікового запису Steam ↗\nОригінальний запис та надіслане посилання\n\nПовідомлення щодо безпеки облікового запису\n\nПереглянути наданий вихідний код ↗\n202410-02Дата підтвердження\nТоргівляПідтверджена подія та дата\nЗа сім днів до повторного продажу або повторного виставлення на продаж\n\nУ примітках до оновлення розглядаються предмети, придбані через ігровий магазин, зокрема в «Зброярні», у рамках торгових пропозицій та на «Ринку спільноти». Описаний обсяг охоплює не лише предмети зі «Зброярні».\n\nValve — Інформація про оновлення для10/2/2024 ↗\nОригінальний запис та надіслане посилання\n\nCS2 «The Armory» / «7-» — одноденний турнір\n\nПереглянути наданий вихідний код ↗\n202409-18Дата подання\nТоргівляЧастково підтверджено\nОбмеження щодо нових пристроїв перевірено на сторінках довідки\n\nВ офіційній документації служби підтримки Steam підтверджується обмеження на денну торгівлю (7-) у разі входу з нового пристрою, який не був авторизований щонайменше протягом 7 днів. Хоча точна дата впровадження цієї функції — 18, 2024, — не зазначена як віха в журналі змін, сама функція повністю задокументована.\n\nSteam Підтримка — Обмеження щодо торгівлі та ринку ↗\nОригінальний запис та надіслане посилання\n\nОбмеження щодо реєстрації нових пристроїв у системі Trade\n\nПереглянути наданий вихідний код ↗\n202402-14Дата подання\nСпільнотаЧастково підтверджено\nУ версії «2024» реалізовано час очікування після зміни імені\n\nЗаписи спільноти та розробників підтверджують, що на початку 2024, Valve було запроваджено неанонсоване 2-обмеження у вигляді4-годинного періоду очікування одразу після зміни імені профілю, щоб запобігти шахрайству у вигляді швидкого підроблення особи. Оскільки Valve не опублікувало жодного офіційного прес-релізу, списку змін у клієнті чи статті служби підтримки щодо цього обмеження, зазначена дата лютого 14 не має офіційного підтвердження; посібник Steam Workshop слугує скоріше непрямим підтвердженням з боку спільноти, а не офіційною Valve документацією.\n\nSteam Посібник для семінару (непряме підтвердження) — Детальна інформація щодо обмежень на зміну імені ↗\nОригінальний запис та надіслане посилання\n\nЗатримка зміни імені профілю / аватара\n\nПереглянути наданий вихідний код ↗\n202312-04Дата підтвердження\nAPIПідтверджена подія та дата\nДля створення ключа необхідне підтвердження за допомогою мобільного телефону\n\nЗгідно з даними сторонніх бібліотек для розробників, введення обов’язкового мобільного підтвердження через додаток «Steam Guard» для створення ключів у веб-додатку API відбулося, як було підтверджено, наприкінці 2023,. Точна дата — 4, 2023, — відповідає періоду впровадження, зафіксованому в спільноті розробників.\n\nДокументація щодо супроводу — березень 2024 ↗архів 2026-09-24 ↗\nОригінальний запис та надіслане посилання\n\nПідтвердження через мобільний телефон для ключів API\n\nПереглянути наданий вихідний код ↗\n202310-24Дата підтвердження\nРозробникПідтверджена подія та дата\nНабуває чинності обов’язкова політика «2» щодо публікації ігрових збірок\n\nОфіційне оголошення Valve щодо Steamworks від 10 жовтня 10, 2023, підтверджує, що починаючи з 10 жовтня 24, 2023, будь-який обліковий запис, який публікує збірку в гілці за замовчуванням випущеного додатка, повинен підтвердити цю зміну за допомогою SMS або мобільного додатку Steam. Ця зміна безпосередньо вплинула на веб-сторінку SetAppBuildLive API.\n\nSteamworks — Покращення безпеки в управлінні збірками та користувачами ↗архів 2025-12-03 ↗\nОригінальний запис та надіслане посилання\n\nSMS MFA для публікацій про версії ігор\n\nПереглянути наданий вихідний код ↗\n202307-12Дата подання\nСпільнотаЧастково підтверджено\nПопередження щодо змісту біографій, складених на замовлення, на які звертає увагу спільнота\n\nSteam З липня у повідомленнях спільноти 2023 зазначається, що в біографіях профілів, які містять зовнішні посилання або «тригерні» слова, почали з’являтися автоматичні попередження про вміст. Дата публікації 12, 2023, збігається з першою хвилею повідомлень користувачів на форумах спільноти Steam.\n\nSteam Форум спільноти — Повідомлення про вміст біографічних даних ↗\nОригінальний запис та надіслане посилання\n\nПопередження щодо вмісту біографії, створеної на замовлення\n\nПереглянути наданий вихідний код ↗\n202301-25Дата подання\nСпільнотаЧастково підтверджено\nАктивні періоди очікування для фільтрування та редагування посилань у профілі\n\nОфіційна документація служби підтримки Steam підтверджує, що посилання у власних біографіях фільтруються, а зловживання при зміні імені чи аватара може призвести до заборони на редагування. Хоча точним початком впровадження є введення годинного періоду очікування 4-1 січня 25, 2023,, сам механізм фільтрування посилань, як зазначено на сторінці довідки, вже повністю діє.\n\nSteam Підтримка — Обмеження щодо імені профілю та аватара ↗\nОригінальний запис та надіслане посилання\n\nПрофіль — ПОСИЛАННЯ ВИДАЛЕНО / Час відновлення\n\nПереглянути наданий вихідний код ↗\n202210-24Дата підтвердження\nАутентифікаціяПідтверджена подія та дата\nSteam Перехід клієнта на токени оновлення та доступу OAuth\n\nОсновні оновлення клієнтських програм та мобільних додатків Valve у жовтні 2022 повністю переробили систему автентифікації Steam. Стару структуру сесійних файлів cookie замінили на токени доступу та оновлення на основі OAuth, а також запровадили список активних авторизованих пристроїв, що дозволяє вручну скасовувати активні сесії.\n\nValve — Оновлення мобільного додатка «Steam» та реорганізація системи автентифікації ↗\nОригінальний запис та надіслане посилання\n\nSteam Переробка системи входу / Скорочення файлів cookie\n\nОзнайомтеся з оголошенням «Valve» ↗\n202210-12Дата підтвердження\nАутентифікаціяПідтверджена подія та дата\nВхід за допомогою QR-коду та управління авторизованими пристроями\n\nУ жовтневому оголошенні компанії Valve щодо «12» йдеться про вхід за допомогою QR-коду, затвердження або відхилення входів, а також про список пристроїв, за допомогою яких можна скасувати доступ до облікового запису.\n\nValve — Оновлений мобільний додаток «Steam» вже доступний ↗\nОригінальний запис та надіслане посилання\n\nSteam Мобільний додаток 3.0 / Вхід за QR-кодом\n\nПереглянути наданий вихідний код ↗\n202205-10Дата подання\nAPIЧастково підтверджено\nКінцеві точки скасування угод вилучено з публічного списку API\n\nЗаписи розробників підтверджують, що в травні 2022, Valve без попередження було видалено кінцеві точки управління обміном, такі як IEconService/CancelTradeOffer та DeclineTradeOffer, з веб-інтерфейсу API (задокументовано в node-steam-tradeoffer-manager #325). Хоча ці методи й надалі працюють у приватних клієнтських протоколах, дата 10, 2022, свідчить про їхнє фактичне видалення з публічних веб-API з метою боротьби з шахрайськими панелями.\n\nОбговорення розробників — Проблема №325 (вилучено функцію CancelTradeOffer) ↗· Веб-сайт Steamworks API — Документація IEconService ↗\nОригінальний запис та надіслане посилання\n\nВидалення кінцевих точок скасування торгових операцій\n\nПереглянути проблему #325 у проекті node-steam-tradeoffer-manager ↗\n202005-25Дата підтвердження\nТоргівляПідтверджена подія та дата\nНа предмети в Dota 2 встановлюється семиденний період очікування перед можливістю обміну\n\n25,, 2020,, у зв’язку з випуском «Battle Pass» для турніру «The International» 10 (blog.dota2.com/2020/05/the-international-10-battle-pass/), Valve запровадив 7-одноденну заборону на обмін предметами Dota 2, що відповідає 2018 політиці щодо Counter-Strike. Це обмеження поширюється на всі обмінені предмети та покупки на ринку.\n\nСпільнота Dota 2 — блокування обміну та оновлення клієнта TI10 ↗\nОригінальний запис та надіслане посилання\n\nDota 2 / 7-Блокування денних торгів\n\nПереглянути наданий вихідний код ↗\n201803-29Дата підтвердження\nТоргівляПідтверджена подія та дата\nОбмінені предмети CS:GO мають семиденний період очікування\n\nОфіційні примітки до випуску підтверджують дату та обмеження. Наведена URL-адреса перенаправляла на оновлення карти за адресою 2013; відповідна URL-адреса приміток до випуску закінчується на 20309.\n\nValve — Інформація про оновлення для3/29/2018 ↗\nОригінальний запис та надіслане посилання\n\nCS:GO / «7-» — блокування денної торгівлі\n\nПереглянути наданий вихідний код ↗ архів 2025-02-26 ↗\n\nДовіряйте фактам. Перевіряйте джерело.\n\nПовернутися до розслідування ↗",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Хронологія заходів з безпеки — від «2018» до «2026»"
          },
          {
            "level": 2,
            "id": null,
            "text": "Хронологія"
          },
          {
            "level": 2,
            "id": null,
            "text": "Попередження про підозрілі повідомлення в групових чатах"
          },
          {
            "level": 2,
            "id": null,
            "text": "Детальні права доступу та білі списки IP-адрес для ключів видавців (оголошення Valve)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Угоди з CS2 отримують семиденне вікно розвороту"
          },
          {
            "level": 2,
            "id": null,
            "text": "Valve публікує попередження щодо безпеки облікових записів у зв’язку з витоком SMS-повідомлень"
          },
          {
            "level": 2,
            "id": null,
            "text": "За сім днів до повторного продажу або повторного виставлення на продаж"
          },
          {
            "level": 2,
            "id": null,
            "text": "Обмеження щодо нових пристроїв перевірено на сторінках довідки"
          },
          {
            "level": 2,
            "id": null,
            "text": "У версії «2024» реалізовано час очікування після зміни імені"
          },
          {
            "level": 2,
            "id": null,
            "text": "Для створення ключа необхідне підтвердження за допомогою мобільного телефону"
          },
          {
            "level": 2,
            "id": null,
            "text": "Набуває чинності обов’язкова політика «2» щодо публікації ігрових збірок"
          },
          {
            "level": 2,
            "id": null,
            "text": "Попередження щодо змісту біографій, складених на замовлення, на які звертає увагу спільнота"
          },
          {
            "level": 2,
            "id": null,
            "text": "Активні періоди очікування для фільтрування та редагування посилань у профілі"
          },
          {
            "level": 2,
            "id": null,
            "text": "Steam Перехід клієнта на токени оновлення та доступу OAuth"
          },
          {
            "level": 2,
            "id": null,
            "text": "Вхід за допомогою QR-коду та управління авторизованими пристроями"
          },
          {
            "level": 2,
            "id": null,
            "text": "Кінцеві точки скасування угод вилучено з публічного списку API"
          },
          {
            "level": 2,
            "id": null,
            "text": "На предмети в Dota 2 встановлюється семиденний період очікування перед можливістю обміну"
          },
          {
            "level": 2,
            "id": null,
            "text": "Обмінені предмети CS:GO мають семиденний період очікування"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/uk/#briefing-heading",
          "https://steamcommunity.com/groups/SteamClientBeta?l=english",
          "http://web.archive.org/web/20260313235409/https://steamcommunity.com/groups/SteamClientBeta?l=english",
          "https://store.steampowered.com/news/posts/?enddate=1788390000",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/493839547938902179",
          "https://partner.steamgames.com/doc/webapi_overview/auth",
          "https://csmarketcap.com/blog/market-insights/from-boom-to-bust-cs2s-trade-protection-impact",
          "https://skinvault.gg/blog/cs2-trade-protection-explained/",
          "https://skin.land/blog/steam-changes-cs2-trade-ban-logic-timing/",
          "https://store.steampowered.com/news/posts/?appids=730&amp;enddate=1753924057&amp;feed=steam_announce%2F1000",
          "https://help.steampowered.com/faqs/view/3041-A87A-E5F6-B6AC",
          "https://store.steampowered.com/news/posts/?enddate=1747349559",
          "https://steamcommunity.com/ogg/593110/announcements/detail/533224478739530146",
          "https://store.steampowered.com/news/posts/?appids=730&amp;enddate=1728000977&amp;feed=steam_community_announcements",
          "https://steamcommunity.com/games/CSGO/announcements/detail/4447966961421256740",
          "https://help.steampowered.com/faqs/view/7F77-9E92-31E0-6B8E",
          "https://steamcommunity.com/sharedfiles/filedetails/?id=2926756889",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "http://web.archive.org/web/20260924181824/https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "https://steamcommunity.com/dev/apikey",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3749866608167579206",
          "http://web.archive.org/web/20251203174259/https://steamcommunity.com/groups/steamworks/announcements/detail/3749866608167579206",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3734103130194459461",
          "https://steamcommunity.com/discussions/forum/1/3807266184852932971/",
          "https://help.steampowered.com/faqs/view/225C-C51E-B8F0-55B2",
          "https://store.steampowered.com/news/group/4/view/3314112260640237775",
          "https://store.steampowered.com/news/posts/?appgroupname=Keep+in+touch&amp;enddate=1666122699&amp;feed=steam_blog",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/issues/325",
          "https://partner.steamgames.com/doc/webapi/IEconService",
          "https://steamcommunity.com/app/570/announcements/",
          "https://blog.dota2.com/2020/05/trading-cooldown/",
          "https://blog.counter-strike.net/2018/03/20309/",
          "https://blog.counter-strike.net/index.php/2018/03/20308/",
          "http://web.archive.org/web/20250226114333/https://blog.counter-strike.net/index.php/2018/03/20308/",
          "https://phishdestroy.io/steam_dossier/uk/#vulnerability-profile"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/uk/security_timeline.content.json",
      "export_json_sha256": "ada1cc5f6a3314127918f7a9ce535dddbcd16226ab2dc8f46fa80dc9406909e2"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "uk/skin_atlas.html",
      "language": "uk",
      "title": "Атлас того, що не може перевозити «Steam» — Досьє «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/uk/skin_atlas",
      "source_html_sha256": "52dd3bcaa349ecd5db9f390eff718d66e2f4eb3a5a73fbc8ed570718226faf19",
      "exported_at": "2026-09-29T00:19:42.971Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "gallery",
            "source": "https://phishdestroy.io/steam_dossier/uk/skin_atlas#gallery"
          }
        ],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "skin_atlas.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/uk/skin_atlas.pdf?v=print-20260929-v5",
        "sha256": "882ad914a9604ac96ff37da4e4f5d42ff7900402b091bd639baf8a5bbc081209",
        "bytes": 188255,
        "pages": 14
      },
      "integrity": {
        "signed_object": "skin_atlas.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "skin_atlas.content.json.asc",
        "digest_file": "skin_atlas.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify skin_atlas.content.json.asc skin_atlas.content.json",
          "sha256sum -c skin_atlas.content.json.sha256"
        ]
      },
      "content": {
        "text": "ДОДАТОК IV-B / «ЦІНОВА ДРАБИНА» / 2026-09-23\nАтлас «Цінова драбина» ринку цінних паперів — «Обрив ліквідності»\n\nЗупинки на ринку Valve звідки беруться гроші.\n\nЩО ДОКАЗУЄ ЦЕЙ РОЗДІЛ\n\nЦей візуальний атлас аналізує категорії товарів із сервісу «30,266» у п’яти каталогах торгових майданчиків, оцінюючи охоплення ринку як вище, так і нижче порогового значення для розміщення оголошень, встановленого компанією «Valve». Нижче межі в $1,800, Steam містить 95.3% активних категорій; одразу вище цієї межі офіційне охоплення різко скорочується до 1.9% (з охопленням 0.0% серед підтверджених активів). Це демонструє різкий структурний «обрив ліквідності», за якого Valve делегує пошук високоцінних транзакцій зовнішнім платформам, зберігаючи при цьому повний контроль над зберіганням базових активів.\n\n← Повернутися до огляду для керівництва\n\nКожен товар CS2, ціна якого відображається на п’яти торгових майданчиках, було віднесено до певного цінового діапазону за найнижчою ціною продажу, і кожен діапазон оцінювався за одним критерієм: яку частку в ньому все ще займає власний «Community Market» Valve. У межах обмеження на кількість оголошень, встановленого Valve, відповідь така: 95.3%. Вище наведено відповідь: 1.9%. Падіння не є поступовим і не відбувається там, де знижується попит, — воно відбувається саме відповідно до опублікованого правила. З 248 категорії товарів, для яких дві або більше торгових платформ самостійно встановлюють ціни, що перевищують верхню межу, 100.0% взагалі не мають Steam жодних пропозицій.\n\nПодивіться на скелю ↓Відкрити галерею товарів «419»Метод та обмеження\n30,266категорії вимірюваних елементів\n95.3%статей, що не входять до капіталу, які відображаються у звітності компанії «Steam»\n1.9%товарів, вартість яких перевищує встановлений ліміт, що продаються на сайті Steam\n$78.6Mмінімальне значення підтвердженої множини\n01 / вимірювання\nСкеля припадає на правило, а не на вимогу\n\nКожна з наведених нижче категорій товарів «30,266» віднесена до певного діапазону за своїм найдешевший результати опитування, проведеного на платформах BUFF163, CSFloat, Skinport, YouPin 898 та C5Game; враховуються лише позиції, зазначені щонайменше на двох із цих платформ, тому жодна окрема завищена оцінка не може «вигадати» учасника гурту. У верхній частині діаграми показано частку кожного гурту, яку досі займає власний ринок Valve.\n\nЧастка кожного цінового діапазону, представленого на ринку «Steam Community Market»\nу верхній частині: покриття парою · у нижній частині: кількість елементів у кожному діапазоні, логарифмічна шкала\n0%\n25%\n50%\n75%\n100%\n100%\n96.9%\n95.9%\n97.3%\n91.1%\n76.8%\n14.5%\n2.9%\n1.5%\n0%\n0%\n0%\n4,632\n1¢–10¢\n7,152\n10¢–$1\n8,568\n$1–10\n5,941\n$10–100\n2,329\n$100–300\n1,292\n$300–1k\n193\n$1k–1.8k\n70\n$1.8k–3k\n67\n$3k–10k\n18\n$10k–30k\n3\n$30k–100k\n1\n$100k+\nitems\nlog\nVALVE’S LISTING CAP\nна рівні або нижче граничного рівня лістингу компанії «Valve»понад ліміт — згідно з правилами «Valve» розміщення оголошень забороненокатегорії товарів у діапазоні\n\nПід «покриттям» мається на увазі, що на момент збору даних для цієї категорії існував активний запит на сайті Steam. Нижня панель має логарифмічний масштаб, оскільки більшість позицій у каталозі є надзвичайно дешевими: лінійне відображення зрівняло б усі діапазони цін вище $300 з базовою лінією.\n\nЩо виключає ця форма\n\nЯкби дорогі товари були просто непопулярними, попит на них поступово знижувався б у міру зростання ціни. Але це не так. Він утримується на рівні 76.8% у діапазоні від $300–$1k, а потім різко падає до 14.5% у діапазоні безпосередньо нижче верхньої межі та до 2.9% у діапазоні безпосередньо вище неї. Ефект попиту не знає, де Valve встановлює свою верхню межу. А правило — знає.\n\nЦіновий діапазон\tКатегорії товарів\tЗа допомогою запиту в прямому ефірі «Steam»\tSteam охоплення\tПерелік примірників наведено на сайті Steam\n1¢–10¢\t4,632\t4,632\t100%\t8,223,227\n10¢–$1\t7,152\t6,931\t96.9%\t5,488,315\n$1–10\t8,568\t8,213\t95.9%\t3,939,538\n$10–100\t5,941\t5,780\t97.3%\t1,328,255\n$100–300\t2,329\t2,121\t91.1%\t364,466\n$300–1k\t1,292\t992\t76.8%\t187,504\n$1k–1.8k\t193\t28\t14.5%\t40,281\n$1.8k–3k\t70\t2\t2.9%\t9,592\n$3k–10k\t67\t1\t1.5%\t6,706\n$10k–30k\t18\t0\t0%\t1,366\n$30k–100k\t3\t0\t0%\t21\n$100k+\t1\t0\t0%\t2\n\nВаріанти «Pattern» і «Phase» не включені до цього рейтингу: у «Steam» рівень «Blue Gem» та фаза «Ruby» не вказані як окремі позиції на ринку, тому їх врахування призвело б до заниження охоплення «Steam». Якщо не враховувати вимогу щодо двох торгових майданчиків, ця ж шкала показує 79.1% нижче верхньої межі та 6.5% вище неї серед товарів 37,204 — це більш різкий розрив, що ґрунтується на слабкіших доказах, саме тому ця цифра не наводиться.\n\n02 / оцінювання доказів\nЗапропонована ціна — це не ціна\n\nБудь-хто може виставити P2000 на продаж за десять мільйонів юанів. Перш ніж цифра на цій сторінці буде використана в будь-яких цілях, її оцінюють за тим, скільки торгових майданчиків незалежно один від одного пропонують ціну, що перевищує встановлений верхній поріг, та наскільки тісно зосереджені середні значення цих пропозицій. Враховуються лише оцінки A та B — як тут, так і в будь-якій іншій частині цього досьє.\n\nA  Три або більше полиць збігаються\n\nНа трьох або більше торгових майданчиках ціна на цей товар перевищує встановлений верхній ліміт, а їхня медіана знаходиться в межах 25% від найнижчої ціни. 197 категорії, 18,218 примірників, $76,585,587.\n\nНе з’явилися на «Steam»: 100.0%.\n\nB  Дві полиці збігаються\n\nДва торгові майданчики домовилися про ціну, що перевищує верхню межу, а три — про ціну, яка не настільки жорстко обмежена. 51 категорії, 176 примірників, $2,038,814.\n\nНе з’явилися на «Steam»: 100.0%.\n\nC  Одна полиця — не використовується\n\nЛише на одній торговельній платформі спостерігається пропозиція, що перевищує верхню межу. 171 категорії, 247 копії. Показано в галереї для повноти картини та не враховано в жодних підсумках на цій сторінці.\n\nЦе запити щодо ціни, а не підтвердження її.\n\nСкільки коштувала ця корекція і що вона дала\n\nВилучення оцінки «C» призводить до видалення категорій «171» та посилання «$3,825,125» із заголовка. Те, що залишається, є меншим за обсягом і набагато важче піддається критиці: 248 категорії, 18,394 перелік екземплярів, $78,624,401, та 100.0% — усі вони, без винятку, відсутні на ринку Valve. Саме рядки класу C стали причиною зміни показника; вони відображаються, а не приховані.\n\nОб’єкти, віднесені до категорії артефактів\n\nБудь-яка пропозиція, яка перевищує найнижчу ціну продажу на той самий товар утричі, відкидається. При перерахунку за курсом, який випливає з самих даних, більшість із них є округленими сумами в юанях — це ознака тимчасового значення або верхньої межі платформи, а не реальної пропозиції. Оскільки кожна загальна сума на цій сторінці розраховується за найдешевший Зауважимо, що жодна з цих осіб ніколи не могла б завищити цифру; їх виключено з переліку саме для того, щоб жодну з них не можна було навести як заголовок.\n\nПозиція\tНайдешевша ціна на покупку в режимі реального часу\tВідкласти\nSouvenir P2000 | Wicked Sick (Minimal Wear)\t$148,954\t$1,489,543\n★ Specialist Gloves | Crimson Kimono (Minimal Wear) | Phase 1\t$37,239\t$119,163\nSouvenir USP-S | Printstream (Factory New)\t$2,000\t$59,582\n★ Bowie Knife | Crimson Web (Factory New)\t$2,957\t$43,030\n★ Karambit | Marble Fade (Factory New) | 1st\t$11,916\t$38,874\nSticker | Ninjas in Pyjamas (Holo) | Katowice 2014\t$5,000\t$31,748\nSouvenir AWP | Dragon Lore (Battle-Scarred)\t$4,225\t$29,157\n★ Karambit | Doppler (Minimal Wear) | Ruby\t$7,122\t$27,273\nУсі категорії «419» із зазначенням об’єкта, до якого відноситься кожна ціна\n\nДжерело: https://phishdestroy.io/steam_dossier/uk/skin_atlas#gallery\n\n04 / куди ж воно насправді потрапило\nПолиці, на яких розміщується те, чого немає на сайті Steam\n\nТі самі оголошення, згруповані за торговими майданчиками, на яких вони розміщені. Це перелік місць, де знаходяться екземпляри перелічені, що не збігається з місцем їхнього володіння і тут не трактується саме так.\n\nМінімальна ціна об’єктів, виставлених на продаж вище встановленого ліміту, за торговими майданчиками\nнайнижча ціна продажу × кількість примірників, виставлених на цій полиці\nYouPin 898\n$22,720,252\nBUFF163\n$22,022,606\nC5Game\n$12,560,543\nCSFloat\n$10,871,845\nSkinport\n$1,385,060\n\nЮрисдикції, у наведеному вище порядку: YouPin 898 — Китай · BUFF163 — Китай · C5Game — Китай · CSFloat — США · Skinport — Німеччина / Мальта. Один і той самий фізичний товар може бути розміщений на кількох із цих полиць, тому ці показники не слід додавати до загальних показників будь-якого іншого ринку.\n\nМінімальна вартість за ціновим діапазоном\nяк розподіляються кошти, що перевищують встановлений ліміт\n$1.8k-3k\n$9,842,391\n$3k-10k\n$36,787,269\n$10k-50k\n$20,038,749\nover $50k\n$2,891,897\n05 / дефіцит, який можна підрахувати\nНаскільки насправді обмежена пропозиція\n\nКожен предмет у CS2 має показник зношеності, і торгові майданчики оприлюднюють інформацію про те, скільки екземплярів знаходиться в кожному діапазоні цього показника. Таким чином, слово «рідкісний» перетворюється з прикметника на число — і саме це число пояснює, чому один зламаний акаунт вартий зусиль, необхідних для створення індивідуального фішингового набору.\n\nAWP | Легенди про драконів\n150 у списку · від $11,350\n0.00–0.01\n29 · $14,730\n0.01–0.02\n54 · $11,618\n0.02–0.03\n26 · $11,350\n0.03–0.04\n25 · $11,618\n0.04–0.07\n16 · $11,585\n\nAWP | Dragon Lore (абсолютно новий)\n\nM4A4 | Howl\n105 у списку · від $6,628\n0.00–0.01\n11 · $10,725\n0.01–0.02\n14 · $8,088\n0.02–0.03\n11 · $7,580\n0.03–0.04\n19 · $6,703\n0.04–0.07\n50 · $6,628\n\nM4A4 | Howl (абсолютно новий)\n\nAK-47 | «Дикий лотос»\n113 у списку · від $14,373\n0.00–0.01\n25 · $22,343\n0.01–0.02\n11 · $19,364\n0.02–0.03\n3 · $19,645\n0.03–0.04\n15 · $15,044\n0.04–0.07\n59 · $14,373\n\nAK-47 | Wild Lotus (абсолютно новий)\n\nAWP | Гунгнір\n173 у списку · від $11,618\n0.00–0.01\n28 · $17,875\n0.01–0.02\n21 · $13,600\n0.02–0.03\n32 · $12,065\n0.03–0.04\n29 · $11,735\n0.04–0.07\n63 · $11,618\n\nAWP | Гунгнір (новий, з заводу)\n\nAK-47 | Вогняний Змій\n278 у списку · від $663\n0.15–0.18\n87 · $730\n0.18–0.21\n49 · $712\n0.21–0.24\n52 · $703\n0.24–0.27\n18 · $715\n0.27–0.38\n72 · $663\n\nAK-47 | «Вогняний змій» (випробувано в польових умовах)\n\nЗміцнене поверхневе гартування (усі рівні / синій самоцвіт)\n76 у списку · від $1,638\n0.07–0.08\n1 · $2,516\n0.08–0.09\n4 · $2,482\n0.09–0.10\n6 · $3,856\n0.10–0.11\n7 · $2,797\n0.11–0.15\n58 · $1,638\n\nAK-47 | З поверхневим загартуванням (мінімальний знос) | Рівень1\n\nДіапазони — це власні групи ліквідності торгових майданчиків; враховуються лише ті діапазони, у яких є хоча б одна активна пропозиція. Ціна, вказана поруч із кожним стовпчиком, є найнижчою актуальною ціною продажу в цьому діапазоні, тому премія, пов’язана з низькою ліквідністю, є безпосередньо видимою, а не вказується окремо.\n\n06 / рух, виміряний за даними сайту Steam\nЩо насправді було реалізовано на полицях сторонніх виробників\n\nValve на цьому рівні не публікує жодних корисних історичних даних, і в цьому досьє про це не згадується. Skinport публікує дані про власні укладені угоди за останні 24 годин, 7, 30 та 90 днів, і це весь часовий діапазон, доступний на цьому ресурсі: медіанна реалізована ціна за кожне вікно, індексована таким чином, що 90-денна медіана становить 100. У жодній з діаграм не використовуються дані з сервісу «Steam».\n\nМедіана реалізованої ціни, ковзне вікно\nіндексовано до медіани за день на сайті 90-· 6,758 товари з 20+ продажі\n85\n91\n97\n103\n100\n90d\n94\n30d\n90\n7d\n88\n24h\nОбсяг продажів за день\nті самі товари, ті самі вітрини\n7,621\n9,653\n11,684\n13,716\n12,700\n90d\n11,894\n30d\n9,540\n7d\n8,637\n24h\n\nЦе два графіки, а не один із двома вертикальними шкалами: індекс і щоденний обсяг торгів не мають спільної одиниці виміру, і відображення їх на спільній осі могло б спонукати до некоректного порівняння. Вікна є вкладеними та зсунутими в часі — показник за 90-день включає показник за 24-годину — тому це не щоденний ряд даних, і його не слід трактувати як такий. Те, що це підтверджує, є вузьким і чітко сформульованим: протягом опублікованих «Skinport» ковзних вікон медіана реалізованої ціни залишалася нижчою за власну медіану за 90-днів, а щоденна кількість продажів знижувалася разом з нею.\n\nSkinport реалізований обсяг продажів. Вікна є вкладеними та ковзаючими, тому кожна точка відповідає медіані реалізованої ціни за ковзаюче вікно, індексованій до медіани за день 90-. Це не щоденний ряд даних, і дані Steam тут не використовуються.\n\n07 / з чого це зроблено\nШістнадцятирічні наклейки та жменька рукавичок\n\nНаведений вище набір не відображає загальної картини ринку. Він зосереджується на кількох рідкісних екземплярах та кількох колекціях, деякі з яких вже взагалі неможливо придбати — саме тому пропозиція не може реагувати на ціну.\n\nКатегорії, що виходять за межі ліміту, за рідкісністю\nкількість категорій товарів\nCovert\n321\nClassified\n39\nRestricted\n24\nContraband\n12\nMil-Spec Grade\n9\nConsumer Grade\n9\nIndustrial Grade\n5\nКатегорії, що виходять за межі обмеження, за колекціями\nдесятка найкращих колекцій\nThe St. Marc Collection\n13\nThe Cobblestone Collection\n13\nThe Norse Collection\n12\nThe Arms Deal Collection\n9\nThe Canals Collection\n7\nThe Gods and Monsters Collection\n6\nThe Revolution Collection\n4\nThe 2021 Train Collection\n4\nThe Rising Sun Collection\n4\nThe Chop Shop Collection\n4\n\nЗа категоріями: skin 366, sticker 48, container 3, sticker_slab 2.\n\n08 / найбільша сума, яку хтось насправді заплатив\nМаксимуми, що базуються на угоді, а не на лістингу\n\nУсі інші ціни на цій сторінці є запитати — що хоче продавець. Це продажі: найвища ціна, за якою було укладено угоду Skinport для кожного товару, за останні 90 днів. Це єдиний показник у цьому досьє, за який хтось насправді заплатив, і кожен рядок містить посилання на торговельну платформу, тож цю цифру можна перевірити безпосередньо у джерелі, а не у нас.\n\n21,216товари, продаж яких вже завершено, у вітрині\n106продані за ціною, що дорівнює або перевищує встановлений компанією «Valve» верхній ліміт котирування\n$14,192найбільша сума за одну завершену угоду\n67/419категорії, що перевищують ліміт, з будь-якими зафіксованими продажами\nТридцять найбільших угод, укладених за цей період\nПозиція\tНайвищий обсяг продажів\tМедіанна ціна продажу\tПродажі\tНайнижча ціна — запитайте зараз\tSteam\tПеревірте це\nAWP | Gungnir (Factory New)\t$14,192\t$11,343\t5\t$11,490\tabsent\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Factory New)\t$12,387\t$12,387\t1\t$13,836\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Factory New)\t$11,779\t$11,063\t16\t$10,941\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Minimal Wear)\t$11,693\t$11,693\t1\t$9,946\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Minimal Wear)\t$10,437\t$10,437\t1\t$9,610\tabsent\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Blue Laminate (Minimal Wear)\t$9,772\t$37\t76\t$30\t$40\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Minimal Wear)\t$9,463\t$9,463\t1\t$9,500\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Minimal Wear)\t$9,104\t$9,026\t6\t$8,524\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Hedge Maze (Minimal Wear)\t$8,139\t$8,139\t1\t$6,819\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Field-Tested)\t$7,617\t$7,390\t4\t$7,194\tabsent\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Field-Tested)\t$7,615\t$7,615\t1\t$7,100\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Field-Tested)\t$7,149\t$7,006\t2\t$7,165\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Field-Tested)\t$6,711\t$6,194\t15\t$5,988\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Factory New)\t$6,679\t$6,613\t3\t$6,628\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Superconductor (Factory New)\t$6,084\t$6,084\t1\t$7,969\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Battle-Scarred)\t$5,750\t$5,413\t3\t$5,899\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Pandora's Box (Minimal Wear)\t$5,520\t$5,508\t3\t$4,998\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Vice (Factory New)\t$5,385\t$5,158\t2\t$5,700\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Minimal Wear)\t$5,342\t$4,989\t19\t$4,997\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Hedge Maze (Field-Tested)\t$5,334\t$4,862\t5\t$3,724\tabsent\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Vulcan (Factory New)\t$5,275\t$1,418\t12\t$1,280\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Well-Worn)\t$4,978\t$4,978\t1\t$4,942\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Well-Worn)\t$4,931\t$4,931\t1\t$5,445\tabsent\tSkinport CSFloat Steam\nAK-47 | Hydroponic (Factory New)\t$4,802\t$4,351\t2\t$3,648\tabsent\tSkinport CSFloat Steam\n★ Talon Knife | Case Hardened (Minimal Wear)\t$4,588\t$466\t16\t$442\t$630\tSkinport CSFloat Steam\nAWP | Medusa (Factory New)\t$4,484\t$4,484\t1\t$4,171\tabsent\tSkinport CSFloat Steam\n★ Specialist Gloves | Pillow Punchers (Factory New)\t$4,359\t$4,359\t1\t$4,302\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Pandora's Box (Field-Tested)\t$4,359\t$3,666\t11\t$3,245\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Field-Tested)\t$4,289\t$4,225\t8\t$4,022\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Battle-Scarred)\t$4,124\t$4,124\t1\t$4,279\tabsent\tSkinport CSFloat Steam\nОдин і той самий товар, ті самі дні акції «90», але ціна кардинально відрізняється\n\nОбмежено товарами з медіаною $100 та щонайменше п’ятьма завершеними продажами, оскільки у випадку дешевого скіна один винятковий продаж спотворює цей показник. Серед решти товарів переважають З ціментованою поверхнею варіанти обробки, де саме візерунок визначає ціну, а торговельна платформа класифікує всі візерунки під однією назвою — той самий механізм, що оцінюється за допомогою змінної float у розділі 05.\n\nПозиція\tМаксимальне значення проти медіани\tНайвищий обсяг продажів\tМедіанна ціна продажу\tПродажі\tПеревірте це\n★ Talon Knife | Case Hardened (Minimal Wear)\t+884%\t$4,588\t$466\t16\tSkinport CSFloat Steam\nDesert Eagle | Cobalt Disruption (Factory New)\t+859%\t$1,210\t$126\t115\tSkinport CSFloat Steam\nAWP | BOOM (Minimal Wear)\t+814%\t$1,232\t$135\t89\tSkinport CSFloat Steam\nAK-47 | Case Hardened (Well-Worn)\t+769%\t$1,720\t$198\t70\tSkinport CSFloat Steam\nAWP | Graphite (Factory New)\t+761%\t$1,469\t$171\t124\tSkinport CSFloat Steam\n★ Talon Knife | Case Hardened (Field-Tested)\t+509%\t$2,437\t$400\t48\tSkinport CSFloat Steam\n★ Kukri Knife | Case Hardened (Minimal Wear)\t+448%\t$723\t$132\t69\tSkinport CSFloat Steam\n★ Kukri Knife | Case Hardened (Field-Tested)\t+415%\t$549\t$106\t128\tSkinport CSFloat Steam\n★ Ursus Knife | Case Hardened (Minimal Wear)\t+371%\t$597\t$127\t12\tSkinport CSFloat Steam\nAK-47 | Case Hardened (Field-Tested)\t+369%\t$1,037\t$221\t125\tSkinport CSFloat Steam\nAK-47 | Red Laminate (Minimal Wear)\t+360%\t$552\t$120\t18\tSkinport CSFloat Steam\nAWP | Asiimov (Field-Tested)\t+351%\t$528\t$117\t439\tSkinport CSFloat Steam\nAK-47 | Vulcan (Field-Tested)\t+337%\t$865\t$198\t241\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Nightwish (Factory New)\t+322%\t$625\t$148\t31\tSkinport CSFloat Steam\nAWP | Lightning Strike (Factory New)\t+319%\t$2,065\t$493\t198\tSkinport CSFloat Steam\nStatTrak™ AWP | Redline (Minimal Wear)\t+312%\t$574\t$139\t24\tSkinport CSFloat Steam\nStatTrak™ AWP | Asiimov (Battle-Scarred)\t+287%\t$524\t$135\t37\tSkinport CSFloat Steam\nAK-47 | Redline (Minimal Wear)\t+277%\t$562\t$149\t112\tSkinport CSFloat Steam\nAWP | Crakow! (Factory New)\t+275%\t$379\t$101\t72\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Vulcan (Factory New)\t+272%\t$5,275\t$1,418\t12\tSkinport CSFloat Steam\n\nЦе рекордний показник за день на сайті 90-, а НЕ історичний максимум, і він стосується ЛИШЕ ОДНОГО торговельного майданчика. У цьому досьє ніде не наводиться жодних даних про історичні максимуми. Товари, для яких у вікні не вказано ціну продажу на сайті Skinport, у цій експозиції взагалі відсутні, саме тому набір є меншим за загальну кількість.\n\nПосилання для перевірки створюються на основі власних ідентифікаторів платформи каталогу. Вони ведуть на сторінку товару на відповідному маркетплейсі, щоб читач міг порівняти зображення з оригіналом, а не з нашими даними. Вихідні посилання містять rel=\"nofollow\": це посилання, а не рекомендації, і деякі з цих ресурсів є торговими майданчиками, до яких це розслідування ставиться критично.\n\n09 / походження та межі\nЗвідки це взялося і що воно не може показати\n\nКожен показник на цій сторінці перераховано на основі двох файлів з моментальними знімками, хеші яких опубліковано поруч із ними. Жодна інформація тут не переписана зі статті іншого сайту.\n\nДжерело та доступ\n\ncs2.sh API, GET /v1/prices/latest та GET /v1/schema, окремий знімок, зроблений 2026-09-23T00:44:27.871388581Z, ціни вказані в доларах США.\n\nДані були отримані в рамках платної комерційної передплати, яку має заявник з організації «GDPR» (інформація про якого міститься в архіві), відповідно до умов, встановлених самим постачальником. Не було здійснено скрейпінгу жодного торгового майданчика, а також не використовувалися жодні облікові дані жодного торгового майданчика. Ключ запитувача зберігається поза цим репозиторієм і не згадується тут у жодному файлі.\n\nЯкі критерії повинен відповідати товар\n\nКожен базовий товар, для якого на BUFF, CSFloat, Skinport, YouPin або C5Game є хоча б одна активна пропозиція на продаж, розміщується в ціновому діапазоні відповідно до його НАЙДЕШЕВШОЇ такої пропозиції, тому діапазон ніколи не залежить від Steam. «Steam coverage» — це частка товарів у цьому діапазоні, для яких на момент збору даних існує будь-яка активна пропозиція на продаж Steam. Варіанти шаблонів та фаз виключаються з рейтингу, оскільки Steam не перелічує їх окремо; їхнє включення призвело б до заниження показника Steam. Рендери — це каталожні зображення тих самих товарів, що зберігаються локально.\n\nВізуалізації та права на зображення. Візуалізації товарів у каталозі — це зображення постачальника, що надаються для того самого параметра `market_hash_name`, що й рядки з цінами, і зберігаються локально для відображення в автономному режимі та через IPFS. Ці зображення не є творами PhishDestroy: усі зображення товарів, логотипи та скріншоти залишаються власністю відповідних власників (cs2.sh, CSFloat, Skinport, BUFF, YouPin, C5Game, Valve та інших). Вони відтворюються виключно з метою ідентифікації та висвітлення в інтересах громадськості; жодних прав власності чи ліцензій не претендується.\n\nТе, чого нам не вдалося отримати\n\nВикористовуваний рівень підписки надає доступ лише до поточних знімків. Історичні та архівні кінцеві точки були недоступні, і на цій сторінці ніде не наводиться жодного історичного ряду даних інформація про продажі за попередній період, опублікована на сайті Skinport, розміщена в розділі 06.\n\nОдин знімок, а не часовий ряд. Відсутність оголошення на «Steam» на момент знімка не є доказом того, що товар ніколи не з’явиться там; це лише стан полиці на той момент, а для цін, що перевищують обмеження, це також відповідає опублікованим правилам «Valve»: «Community Market» на «Valve» чітко обмежує ціну оголошень до $1,800 за одиницю товару (при максимальному балансі гаманця «Steam» у розмірі $2,000; див. Steam Часті запитання щодо громадського ринку архів 2026-09-21 ↗ та Steam Угода з абонентом, § 3.C архів 2026-09-24 ↗).\n\nОцінювання\n\nЦіна товару завжди дорівнює найнижчій актуальній ціні продажу, тому високе відхилення ніколи не може завищити загальну суму. Система класифікації визначає, які рядки можуть бути включені до котирування. Будь-яке котирування, яке перевищує найнижчу ціну продажу того самого товару більш ніж утричі, відкидається як неактуальна ціна. Рівень A: три або більше торгових майданчиків все ще пропонують ціни, що перевищують верхню межу, а їхня медіана знаходиться в межах 25 від найнижчої ціни. Рівень B: два торгові майданчики збігаються, або три збігаються, але з меншою точністю. Рівень C: єдиний показник — ціна продавця, а не ринкова ціна. У цьому досьє наводяться лише ціни рівнів A та B.\n\nПравило щодо відхилень: котирування > 3.0, помножене на найнижчу ціну продажу того самого товару.\n\nЧому ці суми є мінімальними\n\nДля кожної торгової платформи товар найнижчий Ціна продажу множиться на кількість примірників, зазначених у списку. Кожен другий примірник у цьому списку має ціну, що дорівнює або перевищує цю найнижчу ціну продажу, тому фактична опублікована вартість є вищою за своєю суттю, а не за оцінкою. Це не продаж, не грошовий потік і не оцінка економіки CS2.\n\nПеревірте самі\n\nПовні набори даних, на основі яких створено кожну діаграму на цій сторінці, опубліковано в повному обсязі: набір даних «Атлас», екран оцінювання та виявлення артефактів, базовий перепис населення та маніфест із SHA-256-кодом кожного необробленого знімка.\n\nКорекція, зафіксована на відкритті торгів\n\nУ попередньому варіанті супутнього реєстру на першому місці був сувенірний АК —47 | Point Disarray, запропонований за ціною $148,954 на одному з китайських торгових майданчиків, тоді як Steam оцінив його в $119. Цей запис має рейтинг C: лише одна полиця, лише один екземпляр, і жодного іншого торгового майданчика, що підтверджує ціну. Це лише запропонована ціна, а не ринкова, і її було понижено як тут, так і на тій сторінці. Підтвердженим лідером є наклейка | Titan (Holo) | Катовіце 2014 за ціною $66,285, як зазначено на сайті 4, ці торгові майданчики розташовані на відстані 5.2% один від одного — і взагалі відсутні на сайті Steam.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Атлас «Цінова драбина» ринку цінних паперів — «Обрив ліквідності»"
          },
          {
            "level": 2,
            "id": null,
            "text": "Скеля припадає на правило, а не на вимогу"
          },
          {
            "level": 3,
            "id": null,
            "text": "Що виключає ця форма"
          },
          {
            "level": 2,
            "id": null,
            "text": "Запропонована ціна — це не ціна"
          },
          {
            "level": 3,
            "id": null,
            "text": "A  Три або більше полиць збігаються"
          },
          {
            "level": 3,
            "id": null,
            "text": "B  Дві полиці збігаються"
          },
          {
            "level": 3,
            "id": null,
            "text": "C  Одна полиця — не використовується"
          },
          {
            "level": 3,
            "id": null,
            "text": "Скільки коштувала ця корекція і що вона дала"
          },
          {
            "level": 3,
            "id": null,
            "text": "Об’єкти, віднесені до категорії артефактів"
          },
          {
            "level": 2,
            "id": null,
            "text": "Усі категорії «419» із зазначенням об’єкта, до якого відноситься кожна ціна"
          },
          {
            "level": 2,
            "id": null,
            "text": "Полиці, на яких розміщується те, чого немає на сайті Steam"
          },
          {
            "level": 2,
            "id": null,
            "text": "Наскільки насправді обмежена пропозиція"
          },
          {
            "level": 2,
            "id": null,
            "text": "Що насправді було реалізовано на полицях сторонніх виробників"
          },
          {
            "level": 2,
            "id": null,
            "text": "Шістнадцятирічні наклейки та жменька рукавичок"
          },
          {
            "level": 2,
            "id": null,
            "text": "Максимуми, що базуються на угоді, а не на лістингу"
          },
          {
            "level": 3,
            "id": null,
            "text": "Тридцять найбільших угод, укладених за цей період"
          },
          {
            "level": 3,
            "id": null,
            "text": "Один і той самий товар, ті самі дні акції «90», але ціна кардинально відрізняється"
          },
          {
            "level": 2,
            "id": null,
            "text": "Звідки це взялося і що воно не може показати"
          },
          {
            "level": 3,
            "id": null,
            "text": "Джерело та доступ"
          },
          {
            "level": 3,
            "id": null,
            "text": "Які критерії повинен відповідати товар"
          },
          {
            "level": 3,
            "id": null,
            "text": "Те, чого нам не вдалося отримати"
          },
          {
            "level": 3,
            "id": null,
            "text": "Оцінювання"
          },
          {
            "level": 3,
            "id": null,
            "text": "Чому ці суми є мінімальними"
          },
          {
            "level": 3,
            "id": null,
            "text": "Перевірте самі"
          },
          {
            "level": 3,
            "id": null,
            "text": "Корекція, зафіксована на відкритті торгів"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/uk/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/uk/skin_atlas#gallery",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://skinport.com/market?search=AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260924114457/https://store.steampowered.com/subscriber_agreement/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-atlas.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-artefact-screen.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-above-the-ceiling.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/uk/skin_atlas.content.json",
      "export_json_sha256": "8ce00ff4949cadcd40b53269e8a1ef7f67e9add9df2c3a8a433060849fc7e8dc"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "uk/social_graph.html",
      "language": "uk",
      "title": "Простежте за зафіксованими зв’язками — Досьє «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/uk/social_graph",
      "source_html_sha256": "1a543deff95e75006e9ae08f2c2a98f6b91a469de1c42b74b62562d532f7994d",
      "exported_at": "2026-09-29T00:19:41.815Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "social_graph.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/uk/social_graph.pdf?v=print-20260929-v5",
        "sha256": "6c63c168ba37e39b8b0a70d40e1b9a6b85866b3004e8fc058b16405b2a7e44b1",
        "bytes": 126854,
        "pages": 6
      },
      "integrity": {
        "signed_object": "social_graph.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "social_graph.content.json.asc",
        "digest_file": "social_graph.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify social_graph.content.json.asc social_graph.content.json",
          "sha256sum -c social_graph.content.json.sha256"
        ]
      },
      "content": {
        "text": "Простежте зв’язки.Перевірте кожну взаємодію.\n\nЗдійсніть пошук профілю. Оберіть тип стосунків. Перегляньте його безпосередніх сусідів у витягнутих записах. Інструмент для досліджень: ребра відображають публічні зв’язки, а не є доказом прямого контакту, прихованої змови чи неправомірних дій між будь-якими двома вузлами. Схему розташування вузлів «3,435-» найкраще розглядати з використанням фільтрів.\n\nДосліджуйте стосунки по одному\n\n💡 Клацніть і перетягніть вузли, щоб змінити структуру графіка. Наведіть курсор, щоб переглянути детальні профілі. Суцільні лінії блакитного кольору = дружні зв’язки, пунктирні лінії бурштинового кольору = взаємні коментарі.\n\nТип стосунківПрофіль та безпосередні сусіди\n\n3,435 профілі · 4,551 збережені посилання\n\nЗнайдіть і виберіть профіль або натисніть на вузол. Залишаються лише його безпосередні зафіксовані сусіди. Ребро фіксує взаємозв’язок; воно не встановлює приватної координації.\n\nПрофілі у зібраному наборі даних\n\nПовна таблиця джерел: завантажити всі рядки з файлу «3,435» (у форматі CSV). У таблиці нижче спочатку наведено перші 25 рядків; за допомогою пошуку та пагінації можна переглянути повний набір даних.\n\n1–25 / 3,435 рядків\nІм'я персонажа\tSteamID64\tПолітика конфіденційності\tСтатус\tЧленство в групах\tЗаморожені запаси (у доларах США)\tМісцезнаходження\nMahatma Gandhi\t76561198333721623\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tPH\nGalley//갤리🌠🌙\t76561198043416832\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tKP\n$Schlächter\t76561198860277343\tPUBLIC\tClean\tsteambans\t$0.00\tUnknown\n❄r3dsn0w000™❄ [Cristi]🎮\t76561197986767957\tPUBLIC\tClean\tCommunityLegends\t$0.00\tRO\n(2a03) Wolfy\t76561197991671851\tPUBLIC\tCommunity\tsr_public\t$0.00\tUS\nZloy2288\t76561198038578334\tPUBLIC\tClean\tsteambans\t$0.00\tBY\njessy\t76561198039125237\tPUBLIC\tCommunity, VAC (1x)\tCommunityLegends\t$0.00\tJP\nJithraRufure\t76561198071896910\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\n| Níllerdínho |\t76561198003487438\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tDK\nJones is back\t76561198023013026\tPRIVATE\tVAC (1x)\tsteambans\t$0.00\tUnknown\nUNEX | ★✠☠ MoH3st ☠✠\t76561198050763123\tPUBLIC\tClean\tsteambans\t$0.00\tDE\nTrojan\t76561198048457084\tPUBLIC\tClean\tCommunityLegends\t$0.00\tDE\n𝗠𝗮𝘆𝘂 ❤\t76561199377967696\tPUBLIC\tClean\tsr_public\t$0.00\tIS\nbig fucking idiot\t76561198871206397\tPUBLIC\tVAC (1x)\tsteambans\t$0.00\tUnknown\nSOFF Games\t76561198227129276\tPUBLIC\tClean\tcommunitymoderators\t$0.00\tRU\nThijminecraft02\t76561198253895669\tPUBLIC\tClean\tSteamIDcouk SArchive\t$0.00\tNL\nStatic-sama\t76561198289329793\tPUBLIC\tClean\tsteambans\t$0.00\tJP\n𝙸mmortal 𝚂targazer\t76561198142116760\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\nCommander Keen\t76561197987773287\tPUBLIC\tClean\tsteambans\t$0.00\tBE\nS1mX\t76561199648509165\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\nmixwell\t76561199276547472\tPUBLIC\tClean\tsr_public\t$0.00\tJP\nP90_GOD_YyEs™\t76561198285821942\tPUBLIC\tClean\tsteambans\t$0.00\tHK\nhewwo?\t76561199133807546\tPUBLIC\tVAC (1x)\tsteambans\t$0.00\tCH\n♕Kamikaze Atze♕\t76561198002700103\tPUBLIC\tClean\tsteambans\t$0.00\tDE\nPastica\t76561198154655970\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tDZ\nЗареєстровані дружні зв’язки\n\nПовна таблиця джерел: завантажити всі рядки з файлу «4,299» (CSV). У таблиці нижче спочатку наведено перші 25 рядків; за допомогою пошуку та пагінації можна переглянути повний набір даних.\n\n1–25 / 4,299 рядків\nКористувач А\tНапрямок\tКористувач B\tТип відношення\nMahatma Gandhi\n76561198333721623\t↔\tDeskjet\n76561198272738437\tMutual Friends\nGalley//갤리🌠🌙\n76561198043416832\t↔\tomega\n76561197960274529\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tFisty\n76561198057301486\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tFaalagorn\n76561198001116101\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tMURK\n76561198036995672\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tÅρøᴛʜℯᴛȋᴄÅʟȋℯη ♛👽♛\n76561197984615267\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tsilatrak\n76561197999629462\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tBlack Blade\n76561198083368493\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tAvenger\n76561197978249317\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tRemtar\n76561198124322650\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tCato\n76561197961345984\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t✪ G λ M Ξ ®\n76561197994308495\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tclees42\n76561198030936806\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t𝓜ε𝔰𝔥 | AusLevels\n76561198108828539\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tSgtFopper™\n76561198002555892\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t❥Miss Bee\n76561198046958996\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tTesTy\n76561198032370068\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tskl_andrey\n76561198136881436\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t\"Exekutor\"\n76561198009583947\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tAraripe\n76561198103754372\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tsteve6678\n76561198053200093\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\ttrinner\n76561197970359081\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tSteph S.\n76561198025653291\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tKirito\n76561198154545657\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tDoc. todt\n76561197984492467\tMutual Friends\nПосилання на записані коментарі\n\nПовна таблиця джерел: завантажити всі рядки з файлу «252» (CSV). У таблиці нижче спочатку наведено перші 25 рядків; за допомогою пошуку та пагінації можна переглянути повний набір даних.\n\n1–25 / 252 рядків\nАвтор\tНапрямок\tПрофіль цільової аудиторії\tДата\tТекст коментаря\nDeskjet\n76561198272738437\t→\tMahatma Gandhi\n76561198333721623\t16 September, 2021 @ 11:02:05 pm PDT\t\"𝑵𝒐𝒘 𝒊𝒇 𝑰 𝒇𝒖𝒄𝒌 𝒕𝒉𝒊𝒔 𝒎𝒐𝒅𝒆𝒍𝑨𝒏𝒅 𝒔𝒉𝒆 𝒋𝒖𝒔𝒕 𝒃𝒍𝒆𝒂𝒄𝒉𝒆𝒅 𝒉𝒆𝒓 𝒂𝒔𝒔𝒉𝒐𝒍𝒆𝑨𝒏𝒅 𝑰 𝒈𝒆𝒕 𝒃𝒍𝒆𝒂𝒄𝒉 𝒐𝒏 𝒎𝒚 𝑻-𝒔𝒉𝒊𝒓𝒕𝑰'𝒎𝒎𝒂 𝒇𝒆𝒆𝒍 𝒍𝒊𝒌𝒆 𝒂𝒏 𝒂𝒔𝒔𝒉𝒐𝒍𝒆\" - Nelson Mandela\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t22 November, 2021 @ 4:10:28 pm PDT\thttps://anige.horigiri.net/?cat=22\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t18 November, 2021 @ 12:45:26 am PDT\thttps://gamerch.com/umamusume/entry/250411\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t8 August, 2021 @ 4:13:25 am PDT\thttps://modoocode.com/304\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t6 February, 2021 @ 3:35:05 pm PDT\t▤ ∫︹- -ω⁾ ⁽︹▓▓︺\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t11 December, 2019 @ 1:50:53 am PDT\thttps://blog.naver.com/aksenwlddj12/221369410039\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t2 October, 2019 @ 7:11:59 am PDT\tǤαllєу║︎갤리..۩\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t9 April, 2019 @ 12:51:28 pm PDT\tExplosiveDamage(owner, from, maxrange, minrange, distmultiplier, dmgmultiplier, mindamage, typ, damagetype, ignore)\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 12:22:47 pm PDT\tinfo - sh_titles.lua\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 12:21:46 pm PDT\tlocal nibbas = 1344 init.lua\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 11:31:58 am PDT\thttp://foreign.aladin.co.kr/shop/wproduct.aspx?ItemId=123955531&start=slayer\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t3 April, 2019 @ 1:26:41 am PDT\tǤαllєу\nLei\n76561198982197954\t→\tJithraRufure\n76561198071896910\t29 December, 2024 @ 12:58:08 pm PDT\t+rep he knows how 2 rush B ￣ヘ￣\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t2 September, 2026 @ 5:16:55 am PDT\tlol\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t20 August, 2026 @ 6:11:03 am PDT\t?\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t25 July, 2026 @ 7:20:05 am PDT\thahahahaha\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t30 June, 2026 @ 12:52:42 pm PDT\twow\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t30 June, 2026 @ 12:41:32 pm PDT\txD\nvalorant enjoyer\n76561199112142402\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:26:30 pm PDT\toh no!!\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:26:11 pm PDT\toh no!!\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:22:22 pm PDT\tomg !!! they know my secret, omg!!!\nvalorant enjoyer\n76561199112142402\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:21:39 pm PDT\t+rep good ♥♥♥♥♥ player\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:20:50 pm PDT\tomg! u cant cheat on secure gaben servers, omg dont report me, they ban me for boosted omg\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 8:37:11 pm PDT\txD\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t28 June, 2026 @ 1:58:14 pm PDT\twow",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Простежте зв’язки.Перевірте кожну взаємодію."
          },
          {
            "level": 2,
            "id": null,
            "text": "Досліджуйте стосунки по одному"
          },
          {
            "level": 2,
            "id": null,
            "text": "Профілі у зібраному наборі даних"
          },
          {
            "level": 2,
            "id": null,
            "text": "Зареєстровані дружні зв’язки"
          },
          {
            "level": 2,
            "id": null,
            "text": "Посилання на записані коментарі"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-profiles.csv",
          "https://steamcommunity.com/profiles/76561198333721623",
          "https://steamcommunity.com/profiles/76561198043416832",
          "https://steamcommunity.com/profiles/76561198860277343",
          "https://steamcommunity.com/profiles/76561197986767957",
          "https://steamcommunity.com/profiles/76561197991671851",
          "https://steamcommunity.com/profiles/76561198038578334",
          "https://steamcommunity.com/profiles/76561198039125237",
          "https://steamcommunity.com/profiles/76561198071896910",
          "https://steamcommunity.com/profiles/76561198003487438",
          "https://steamcommunity.com/profiles/76561198023013026",
          "https://steamcommunity.com/profiles/76561198050763123",
          "https://steamcommunity.com/profiles/76561198048457084",
          "https://steamcommunity.com/profiles/76561199377967696",
          "https://steamcommunity.com/profiles/76561198871206397",
          "https://steamcommunity.com/profiles/76561198227129276",
          "https://steamcommunity.com/profiles/76561198253895669",
          "https://steamcommunity.com/profiles/76561198289329793",
          "https://steamcommunity.com/profiles/76561198142116760",
          "https://steamcommunity.com/profiles/76561197987773287",
          "https://steamcommunity.com/profiles/76561199648509165",
          "https://steamcommunity.com/profiles/76561199276547472",
          "https://steamcommunity.com/profiles/76561198285821942",
          "https://steamcommunity.com/profiles/76561199133807546",
          "https://steamcommunity.com/profiles/76561198002700103",
          "https://steamcommunity.com/profiles/76561198154655970",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-connections.csv",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-comments.csv"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/uk/social_graph.content.json",
      "export_json_sha256": "b96f9d15ca98d3ca86de3d979f9bae82e4ccfe91e0e4eeb1e6d51bc07d47cf8c"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "uk/steam_enforcement_evidence.html",
      "language": "uk",
      "title": "Правила проти реакцій — Досьє «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/uk/steam_enforcement_evidence",
      "source_html_sha256": "2ef0d79910cfef22110ea2bf8111d32821d717a803b009911ac9d7ed964122f4",
      "exported_at": "2026-09-29T00:19:44.078Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "steam_enforcement_evidence.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/uk/steam_enforcement_evidence.pdf?v=print-20260929-v5",
        "sha256": "330e44892f7a1a242aeee2b89a9e542c92e206a3c79436594fce12e463a43d4a",
        "bytes": 383421,
        "pages": 36
      },
      "integrity": {
        "signed_object": "steam_enforcement_evidence.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "steam_enforcement_evidence.content.json.asc",
        "digest_file": "steam_enforcement_evidence.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify steam_enforcement_evidence.content.json.asc steam_enforcement_evidence.content.json",
          "sha256sum -c steam_enforcement_evidence.content.json.sha256"
        ]
      },
      "content": {
        "text": "Додаткові докази / записи з посиланнями на джерела\nSteam Докази щодо виконання зобов’язань — супровідна документація та мережа розробників\n\nПравило. Відповідь.\n\nЩО ДОКАЗУЄ ЦЕЙ РОЗДІЛ\n\nУ цьому розділі, присвяченому аналізу доказів, проводиться порівняння офіційного Договору з абонентом компанії «Valve» з датованими журналами заходів щодо забезпечення дотримання правил, рішеннями щодо врегулювання спорів у службі підтримки та записами мережі розробників у репозиторіях 252 та профілях 3,320. Це демонструє, що звичайні власники облікових записів стикаються з беззаперечними заходами щодо забезпечення дотримання правил та закриттям облікових записів службою підтримки після компрометації сеансів, тоді як великомасштабні комерційні бот-операції безперервно функціонують, маючи доступ до публічної інфраструктури.\n\n← Повернутися до огляду для керівництва\n\nОзнайомтеся з письмовим обмеженням. Відкрийте записану відповідь. Порівняйте те, що вказано у джерелі, з тим, на що не надано відповіді.\n\nПідтримка та апеляції ↓Громадська інфраструктура ↓\n252записи репозиторію\n3,320публічні профілі\n4,214окремі пари «профіль–репозиторій»\n98,902пари профілів зі спільними репозиторіями\n01 / Підтримка, санкції та відновлення\nОзнайомтеся зі скаргою.Додайте вихідний код.\nГалерея відмов у наданні підтримки (експонати 981) ↗Завантажити вибрані записи ↓\nHFB / Справа про аутсорсингЗагальновизнаний компроміс.\nПовідомлення про звільнення.\n\nОзнайомтеся з наведеною відповіддю служби підтримки та джерелом твердження щодо персоналу підрядника.\n\nВідкрити справу та її джерела →\n\nНижче: п’ять збережених публічні дописи на Reddit з наданої колекції запитів до служби підтримки. Кожен запис містить інформацію про зареєстровану взаємодію з системою підтримки Valve — із збереженням оригінального посилання на джерело, місця збору даних та повного тексту. Це розповіді потерпілих. Аутентифіковані журнали служби підтримки, які могли б підтвердити або спростувати ці розповіді, зберігаються на сайті Valve і не були оприлюднені.\n\n01\nBan & review2024-12-09\nPermanent sanction & closed appeals\n\nThe author reports a permanent account ban, repeated ticket closures and a planned GDPR access request.\n\nREDDIT / PUBLIC TESTIMONYr/ohnePixelCapture record 294\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 303 words\nPermanently banned Steam account without a clear explanation, need help!\n\nsteam_support_tickets_MEGA.json / record 294\n\nHey everyone,\n\nI’m in a really frustrating situation, and I’m hoping someone here can help me or offer advice. My Steam account was just permanently banned for allegedly violating the Steam Subscriber Agreement, and I have no idea why.\n\n# What Steam Support told me:\n\nThe support message said my account was banned due to:\n\n* Suspicious activities related to transferring or attempting to sell/trade the account.\n* Community reports and other unspecified factors.\n\nThey added that the ban is permanent and that they can't help me further. They also warned that future support requests regarding this ban might be ignored. 😞\n\n# Why I’m contesting this ban:\n\n* I have never sold, traded, or transferred my account. I’ve been the legitimate owner since the beginning.\n* On the day the ban occurred, I did nothing noteworthy that could have triggered such a sanction.\n* I received no prior warning, which feels incredibly unfair.\n\n# What I’ve tried so far:\n\n* Contacting Steam Support: I explained my situation and asked for more details, but they’re sticking to their decision and closing my tickets.\n* I’m preparing a request based on my Right of Access (GDPR) to get all the data related to my account.\n\n# Questions for the community:\n\n1. Has anyone successfully had a permanent ban lifted on Steam?\n2. Are there steps I can take to prove I’m the legitimate owner of the account?\n3. Any advice on how to word my request to convince support to reconsider my case?\n4. Would it be helpful to contact the CNIL (I’m based in France) to force Steam to provide more information?\n\nI’m really desperate at the thought of losing all my games, purchases, and years of playtime. Thanks in advance for any help and advice you can give!\n\nhttps://preview.redd.it/jk9qv0gmhv5e1.png?width=1289&amp;format=png&amp;auto=webp&amp;s=b3a333ebb08ea133e2c8747ba126f5a68283d9f7\n\nhttps://preview.redd.it/4sopt0gmhv5e1.png?width=1022&amp;format=png&amp;auto=webp&amp;s=56195d5336118faf9413f1514ead7e8d24c788c3\n\nhttps://preview.redd.it/eqrxw0gmhv5e1.png?width=996&amp;format=png&amp;auto=webp&amp;s=ff3539d28ab754e513ad471822c5de652920101d\n\nhttps://preview.redd.it/728xz0gmhv5e1.png?width=1034&amp;format=png&amp;auto=webp&amp;s=bc5335673509929669af785aa244bf8d2dc58da8\n\n02\nSupport access2025-05-09\nAccount recovery & a reported $10,000 loss\n\nThe author alleges that support reset credentials and removed account protection following another person’s recovery ticket.\n\nREDDIT / PUBLIC TESTIMONYr/legaladviceCapture record 110\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 193 words\nGot $10k stollen from steam inventory due to steam' support fault.\n\nsteam_support_tickets_MEGA.json / record 110\n\nLocation: Quebec, Canada.\n\nLast year, someone hacked my Steam account and stole items worth about $10,000 USD. I only noticed this last week. When I talked to Steam Support, they admitted that someone submitted a ticket to make changes on the account and Steam Support reset my password and turned off all my account security.\n\nI asked Steam Support about getting my items back, but they said there was nothing they could do. They told me I should follow their security recommendations.\n\nThe problem is, I did everything they \"suggested\" to protect an account:\n\n* I had two-factor authentication.\n* My phone number was connected to my account.\n* I used Steam Guard.\n* I printed recovery codes and kept them in a safe.\n\nEven though I did all these things, Steam Support still gave someone else access to my account. The stolen items had been in my account since around 2016-2017. Also, I had not logged in for a few years, so I didn’t accidentally give my information to a fake website.\n\nIs there anything I can do, or do I just have to accept losing $10,000 USD?\n\nThanks for your help.\n03\nRestoration2022-07-07\nA reported $500+ loss & template replies\n\nThe author describes an account compromise, disputed transactions and a support response that allegedly did not address the submitted evidence.\n\nREDDIT / PUBLIC TESTIMONYr/DotA2Capture record 45\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 410 words\nFunds stolen through steam market. Disappointed with Steam response.(or lackthereof)\n\nsteam_support_tickets_MEGA.json / record 45\n\nOn 6th July 2022, 44 unauthorized transactions were made on the steam market using my steam wallet funds totalling roughly $500+ USD to buy worthless 1 cent Dota 2 items. This happened during the wee hours in the morning and i contacted them first thing when i woke up. \n\nI have 2FA enabled all the time, and always thought this would not happen to me as I do not go on betting sites/click sketchy links. My account password + emails were not changed, nor did they take my inventory, just that my funds were used illicitly. Also when I went to disable other APIs, it says there are no other APIs to disable. Shows that it wasn't through me clicking sketchy links and leaving my account details there. Would have lost the whole account if i did so.\n\nWhat baffles me is how did they bypass my 2FA to login my account? Why doesn't steam market purchases go through 2FA as well? First time in 9 years that this happened to me. My acc was logged in 'BY' 'Vitebsk' during the illicit purchases but I'm based in Asia I gathered all the screenshots and provided in the ticket to steam support. \n\nAll i got was the standard copy paste template reply by Steam Support. Lost $500+ and was not even worthy of having a proper person to look into this. I dont think they even read or take a look at the screenshots cause if they did, they would have come to the realization that what happened was clearly fraud, and with a few clicks, reverse the unauthorized transactions, refund my wallet and ban the hijacker. \n\nOver the years, i've spent quite a fair bit on steam but really, this is the kind of recourse we get when our account is compromised? They just don’t care, sigh. I only expect the bare minimum from Steam and looks like even that is quite far-fetched.\n\nSS: https://imgur.com/a/67frcls \n\nHijacker: https://steamcommunity.com/profiles/76561199141246495\n\nSteam Response: https://imgur.com/a/V6v4maM\n\nI could think of a few ways on how to Improve:\n\n1) Add 2FA to market transactions. (even if its bulk posting or selling of items, just 1 2FA notif is required)\n\n2) Enable accounts to be region locked. (if you are migrating, then have to go through steam support etc)\n\n3) Additional Lock on Steam Wallet. (Another password perhaps?)\n\nEDIT: 2nd ticket in and I have still yet to receive a non robotic copy paste template response from Steam.\n04\nRestoration2021-11-29\nSteam Guard & an item-restoration refusal\n\nA preserved post includes the author’s account of item theft and a support response declining restoration.\n\nREDDIT / PUBLIC TESTIMONYr/DotA2Capture record 58\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 563 words\nMany people are losing item via clicking links where steam guard is enabled and steam support doesn't not restore items.\n\nsteam_support_tickets_MEGA.json / record 58\n\nAccounts are getting compromised and might be their pc as well where Steam market is targeted hence the malicious links . I am assuming these hackers are getting encouraged where steam support is not doing nothing and they are getting away with hacking items.  \nLiterally the guy who is supporting the game which he doesn't get any in game advantage just  cosmetics in game only for the sole purpose of supporting the game so that the game will prosper and become beautiful way  to enjoy weekend. But right now players are getting hacked left right and center and steam support  is copy pasting message where in short they are blaming the guy who clicked link. 1st this is happening because they are not targeting players but they are targeting market since they are selling those stuff for real cash via party website. Steam is a huge company and can eradicate the problem or at least can remove links temporarily  in chat since hackers are targeting .They made us install steam guard by saying we wont help if there is no steam guard now steam guard is not enough to save our inventory now they changed their policy  that they should not click any suspicious links. How would we know if the link is suspicious ? After clicking and getting our inventory stolen right !   \n\"we'd have to duplicate an item to restore it. Duplication lowers the value of all items by reducing their scarcity and inflating the economy, which affects everyone involved in trading and the Market. To maintain the value of everyone’s inventory, we do not restore items. For more information, please see the Steam Item Restoration Policy.\"  \nThey care for millions of people IN STEAM MARKET where as few  are losing items which is going to affect market where the rightful owner bought the items and hacker is going to sell the item via 3rd party website and enjoy ! HOW IRONIC !!  \nThis is the message from support where my frnd got his items stolen via clicking on link  \n   \nHi there,  \n\nThank you for the information and screenshots provided.  \n\nIt appears that the account was compromised, please take the following steps to secure your account and computer:  \n\nScan your computer for viruses, key loggers, spyware, and other malicious code using antivirus software with updated virus definitions.  \nChange the password for the email address that is associated with your Steam account.  \nRegularly reset your Steam account password.  \n\nPlease see our Security Recommendations article.  \n\nIn addition, I’m sorry to hear that your items were removed without your permission. Unfortunately, Steam Support does not restore scammed, lost, or stolen items for any reason.  \n\nSince Steam Support does not remove items from accounts, we'd have to duplicate an item to restore it. Duplication lowers the value of all items by reducing their scarcity and inflating the economy, which affects everyone involved in trading and the Market. To maintain the value of everyone’s inventory, we do not restore items. For more information, please see the Steam Item Restoration Policy.  \n\nTo make sure that a scammer is reported, please report them through the Steam Community. Reporting a scammer through the Steam Community is the best way to prevent them from committing future scams.  \n\nTo learn how to avoid scams or hijackings, please see our Trade Scam article.  \n\nIf you still need assistance, please let us know.\n05\nEnforcement2025-05-11\nSelective enforcement & an unexplained ban\n\nA community member describes a disputed ban and contrasts it with the visibility of commercial gambling promotion.\n\nREDDIT / PUBLIC TESTIMONYr/SteamUncensoredCapture record 107\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 1,208 words\n🚨 Steam Bans Without Reason and Ignores Its Community — What’s Going On?\n\nsteam_support_tickets_MEGA.json / record 107\n\nHey r/Steam,\n\nI’m writing this to share my thoughts and concerns about my friend [moneylead](https://steamcommunity.com/id/moneylead/) and Steam’s policies in general. I spoke with him yesterday about his situation, though I didn’t discuss writing this post with him—I asked last night, but he hasn’t responded yet. I want to highlight that this issue is broader than just his case, and while Steam might make changes in the future (though that’s unlikely), I feel the community needs to understand how far Steam has strayed from its original values. I’m not trying to put moneylead in a tough spot with this thread—all the info I’m sharing is public, nothing secretive. I hope he won’t be upset with me, but the community needs this case to see the bigger picture and how Steam feels completely unaccountable.\n\n**Why Does Steam Ignore Its Community?**  \nWhy does a platform like **Roblox** provide a detailed log of ban reasons, while Steam, which claims to be \"community-driven,\" ignores its community, bans whoever they want, for whatever they want, with no transparency? I looked into Roblox as a popular game—not a direct competitor to Steam—to see how their bans look, and you can check it out yourself: [Roblox Ban Reasons](https://www.google.com/search?q=Roblox+ban). Their bans are clear, detailed, and actually explain what you did wrong. I think most decent gaming communities operate like this—not with support agents named Olga, hired through outsourcing, who only know how to send canned auto-replies. Take cases like St4ck—or my friend **moneylead**. All these unbans, like **St4ck’s** or **Alexanddd’s**, happened behind closed doors with zero comments from Steam. Of course, it’s convenient for Steam to handle everything in secret, so no one knows or sees what’s going on—but this violates Steam’s own community rules and principles.\n\n**Who Is moneylead?**  \nI’ve known [moneylead ](https://steamcommunity.com/id/moneylead/)since around 2021. We played Dota 2 a couple of times, and then I just stayed on his friends list. He’s always been a legit player, bringing revenue to Steam through purchases. He never sold his skins, whether in **Dota or CS2—he wasn’t a trader**. All he did was:\n\n* Buy games and skins.\n* Collect badges to level up his profile.\n\nAccording to [SteamSets](https://steamsets.com/account/76561199080934614), he’s given out 324,000 Steam Points—I think he awarded profile rewards to all his friends in the list (though I’m not 100% sure). I do know he ran contests and gave gifts to friends, always supporting the community.\n\n**Steam’s Unfair Treatment**  \nI’ve seen Steam remove his showcases, avatar, description, and even his country multiple times—just because he’s from **Ukraine**. He has a ton of haters leaving toxic comments on his wall, and Steam seems to favor **Russian** users. Every time he tried to appeal the removal of his showcases or profile description—which didn’t break any rules, just had his Instagram link, and his avatar is the same as it is now—Steam moderators didn’t care. **They don’t care about top players who bring them massive revenue, nor about regular users.**\n\n>*Here’s the worst part: moneylead works in cybersecurity, specifically fighting account theft and phishing. He’s neutralized over 5,000 threats targeting Steam alone. And yet, Steam bans him for \"account hijacking\"?*\n\nIf you roughly calculate moneylead’s contribution to Steam and the community—his profile, level, badges (not skins, you can’t sell those)—is this normal, Steam? Banning people, closing tickets, and ignoring users with a spotless reputation who aren’t involved in any commercial activity, just bringing you profit without taking anything in return?\n\n**Steam’s Double Standards**  \nI’m honestly shocked:\n\n* YouTubers who promote casinos and skin gambling? Steam’s fine with that.\n* A cybersecurity expert who fights scams, doesn’t promote casinos, and openly talks about it on his profile? **Banned with no explanation, ignored, and denied an unban.**\n\nI wonder if Steam deliberately bans a high-level account once a year just because of their impunity—maybe for hype or something. Otherwise, this is just madness. It’s scary to think how many regular players have lost their accounts and skins—not because of scammers, but because of Steam’s desire to ignore, send auto-replies, and do whatever they want.\n\n**How Many Others Are Affected?**  \nHow many others are out there—maybe not as well-known—who just have a few games or skins, get banned for nothing, and receive zero explanation or response? **Is this even legal?** Every other platform provides a detailed log with specific violations, but Steam slaps on the same vague label and sends templated responses.\n\n* How safe is it to buy skins on Steam?\n* What’s the chance Steam will just ban your account for no reason, with no explanation?\n\n**A Message to Valve**  \nI wish moneylead the best in resolving this, but Valve, it’d be great if you remembered what \"community\" means and started following the law. Because right now, it looks like your 30% commission, impunity, and sense of being above the law in the U.S. have given you the idea that you can do whatever you want.\n\nI’m sure there are many others like moneylead and St4ck—people who aren’t public or don’t have the resources to fight back. Let’s unite these cases. **If you’re a U.S. resident who’s been banned by Steam without reason and wants to challenge it, please reach out to me.** I’m finishing my **Juris Doctor (J.D.) program at SMU Dedman School of Law** in Dallas, Texas, and I’m participating in a legal clinical practice under Rule 13 of the Texas Supreme Court.\n\nWhat Steam is doing is absolutely disgusting and illegal, and **I’d be happy to help any gamer (legitimate, with no real violations) who has games or skins with value. This will be beneficial for my practice, and it’s time to put Steam in its place and show them they can’t just dictate their own rules with arbitration**. Let’s take it all the way—not for punishment, but for the sake of the community. Maybe if Steam loses a case, they’ll change their policies and start explaining their actions like most popular gaming communities do. Many of us remember how Steam Support used to recover stolen accounts and ended up “stealing” skins themselves—banning without real reasons is basically the same thing, and that’s a serious accusation.\n\nSo, r/Steam, see you soon. I think you understand what you’re doing and how many people you’ve illegally deprived of their assets. I want to raise this issue—not just for the U.S., but for the entire world. You’ve banned class-action lawsuits? **Welcome to Texas.** I recommend starting to look for licensed attorneys in Texas, because I’d love to discuss your company’s policies, feedback, and support agents named Olga—a name that strongly associates with Russian users. Maybe it’d be easier to move your company to Moscow? But I’d be happy to discuss these critical issues on behalf of the global gaming community.\n\nAlso, I wouldn’t recommend ignoring the lawsuit request that will be sent to your physical address and email address, as the court will proceed without you, and that might upset you—especially since things aren’t going so well for a company with stocks like yours.\n\n**Thanks to everyone who took the time to read this. For those who need real help with an unjust Steam ban without any explanation, I’d be happy to assist. For users from Texas, we can easily file a collective lawsuit against Steam—let’s connect and make it happen.**\n02 / Мережа розвитку «Steam»\nГромадська інфраструктура.Записано у повному масштабі.\nЗавантажити всі записи «252» ↓\n\nУ комплекті output_steam_network «Snapshot» фіксує репозиторії, публічні зв’язки між учасниками та форками, а також перетини профілів. Це оприлюднені дані — що було створено, хто брав участь у розробці, що було форковано. Саме ці документальні свідчення публічних можливостей має враховувати система «Valve».\n\nРепозиторій / опис\tАвтори\tФоркери\tЗбережені профілі\nalliedmodders/amxmodx\n\nAMX Mod X - Half-Life 1 Scripting and Administration\n\n\t40\t40\t80\nalliedmodders/sourcemod\n\nSourceMod - Source Engine Scripting and Administration\n\n\t40\t40\t80\nDoctorMcKay/node-steam-user\n\nAllows interaction with the Steam network via the Steam client protocol\n\n\t40\t40\t80\nFacepunch/Facepunch.Steamworks\n\nAnother fucking c# Steamworks implementation\n\n\t40\t40\t80\nJustArchiNET/ArchiSteamFarm\n\nC# application with primary purpose of farming Steam cards from multiple accounts simultaneously.\n\n\t40\t40\t80\nodota/core\n\nOpenDota: Open source Dota 2 data platform with automated replay parsing\n\n\t40\t40\t80\nodota/dotaconstants\n\ndotaconstants: Static data for Dota applications\n\n\t40\t40\t80\nodota/web\n\nOpenDota: React web UI for Dota 2 statistics using the OpenDota platform\n\n\t40\t40\t80\nsplewis/get5\n\nCS:GO Sourcemod plugin for competitive matches/scrims\n\n\t40\t40\t80\nSteamDatabase/FileDetectionRuleSets\n\n🔎 Rules to detect game engines and other technologies based on Steam depot file lists\n\n\t40\t40\t80\nSteamRE/SteamKit\n\nSteamKit2 is a .NET library designed to interoperate with Valve's Steam network. It aims to provide a simple, yet extensible, interface to perform various actions on the network.\n\n\t40\t40\t80\nValveSoftware/dxvk\n\ndxvk tree containing branches used by Proton\n\n\t40\t40\t80\nValveSoftware/GameNetworkingSockets\n\nReliable & unreliable messages over UDP. Robust message fragmentation & reassembly. P2P networking / NAT traversal. Encryption.\n\n\t40\t40\t80\nValveSoftware/gamescope\n\nSteamOS session compositing window manager\n\n\t40\t40\t80\nValveSoftware/Proton\n\nCompatibility tool for Steam Play based on Wine and additional components\n\n\t40\t40\t80\nValveSoftware/source-sdk-2013\n\nThe 2013 edition of the Source SDK\n\n\t40\t40\t80\nValveSoftware/wine\n\nWine with a bit of extra spice\n\n\t40\t40\t80\nValveSoftware/steam-devices\n\nList of devices Steam and SteamVR will want read/write permissions on, to help downstream distributions create udev rules/etc\n\n\t39\t40\t79\nValveSoftware/steam-audio\n\nSteam Audio\n\n\t38\t40\t78\nalliedmodders/metamod-source\n\nMetamod:Source - C++ Plugin Environment and Detour Library for the Source Engine\n\n\t37\t40\t77\nalliedmodders/sourcepawn\n\nA small, statically typed scripting language.\n\n\t35\t40\t75\nValveSoftware/Fossilize\n\nA serialization format for various persistent Vulkan object types.\n\n\t31\t40\t71\nrlabrecque/Steamworks.NET\n\nSteamworks wrapper for Unity / C#\n\n\t27\t40\t67\nModDota/moddota.github.io\n\nModDota github pages project.\n\n\t26\t40\t66\nodota/parser\n\nReplay parse server generating JSON log events from Dota 2 replay files\n\n\t26\t40\t66\nValveSoftware/steam-for-linux\n\nIssue tracking for the Steam for Linux beta client\n\n\t26\t40\t66\nSteamRE/DepotDownloader\n\nSteam depot downloader utilizing the SteamKit2 library.\n\n\t24\t40\t64\nJustArchiNET/ASF-ui\n\nThe official web interface for ASF\n\n\t23\t40\t63\nadvancedfx/advancedfx\n\nHalf-Life Advanced Effects (HLAE) is a tool to enrich content creation mainly for the Counter-Strike series.\n\n\t22\t40\t62\nalliedmodders/ambuild\n\nAlliedModders C++ Build System\n\n\t23\t39\t62\nSteamDatabase/BrowserExtension\n\n💻 SteamDB's extension for Steam websites\n\n\t21\t40\t61\nodota/mobile\n\nReact Native apps for viewing Dota 2 data on Android/iOS\n\n\t19\t40\t59\nValvePython/steam\n\n☁️ Python package for interacting with Steam\n\n\t18\t40\t58\nskadistats/clarity\n\nComically fast Dota 2, CSGO, CS2 and Deadlock replay parser written in Java.\n\n\t13\t40\t53\nSteamRE/open-steamworks\n\nOpen Steamworks is a set of reverse engineered headers for the Valve's Steam Client. More or less abandoned now that the Steamworks SDK is publically available.\n\n\t13\t40\t53\nValveSoftware/Source-1-Games\n\nSource 1 based games such as TF2 and Counter-Strike: Source\n\n\t13\t40\t53\nalliedmodders/hl2sdk\n\nHalf-Life 2 SDK Mirrors\n\n\t11\t40\t51\nSteamDatabase/steamdb.info-issues\n\n🚱 Issue tracker for the SteamDB website\n\n\t11\t40\t51\nCSGOFloat/inspect\n\nSource Code that Powers the CSFloat Inspect Link API\n\n\t10\t40\t50\nValveSoftware/SteamOS\n\nSteamOS community tracker\n\n\t10\t40\t50\nalliedmodders/source2mod\n\nExperimental\n\n\t40\t9\t49\nsmiley/steamapi\n\nAn unofficial object-oriented Python library for accessing the Steam Web API.\n\n\t9\t40\t49\nSteamDatabase/GameTracking\n\n🛢 Dumping things, so you don't have to\n\n\t8\t40\t48\nValveSoftware/counter-strike_rules_and_regs\n\nCS:GO\n\n\t7\t40\t47\nValveSoftware/openvr\n\nOpenVR SDK\n\n\t6\t40\t46\nSteamDatabase/easy-markdown-editor\n\nEasyMDE: A simple, beautiful, and embeddable JavaScript Markdown editor. Delightful editing for beginners and experts alike. Features built-in autosaving and spell checking.\n\n\t40\t4\t44\nValveSoftware/Dota-2\n\nTracker for issues specific to Linux and Mac in the Reborn client. If you have a general issue or non-system-specific feature request please go to dev.dota2.com\n\n\t6\t38\t44\nValveSoftware/Dota2-Gameplay\n\nPublic Bug Tracker for Dota 2\n\n\t4\t40\t44\nJustArchiNET/ArchiBot\n\nNo description in the capture.\n\n\t16\t27\t43\nztizzlegaming/CSGOWinBig\n\nOpen-source Counter-Strike: Global Offensive jackpot betting website.\n\n\t1\t40\t41\nJustArchiNET/mantis.justarchi.net\n\nMantis Bug Tracker (MantisBT)\n\n\t40\t0\t40\nodota/node-steam-user\n\nAllows interaction with the Steam network via the Steam client protocol\n\n\t40\t0\t40\nModDota/TypeScriptAddonTemplate\n\nDota 2 addon template with TypeScript Panorama and VScripts.\n\n\t9\t29\t38\nValvePython/vdf\n\n📜 Package for working with Valve's text and binary KeyValue format\n\n\t6\t32\t38\nalliedmodders/amtl\n\nAlliedModders C++ Template Library\n\n\t17\t19\t36\nValvePython/dota2\n\n🐸 Python package for interacting with Dota 2 Game Coordinator\n\n\t5\t30\t35\nalliedmodders/stripper-source\n\nStripper:Source\n\n\t13\t21\t34\nAllyans3/steam-market-api-v2\n\nSteam Market API v2 package\n\n\t3\t31\t34\nModDota/dota-tutorial\n\nCustom game DOTA tutorial.\n\n\t11\t23\t34\nodota/blog\n\nNo description in the capture.\n\n\t29\t3\t32\nOpsecGuy/BetterGo\n\nExternal CS:GO cheat written in python.\n\n\t1\t27\t28\npxvr-official/1\n\n無許諾配信 企業理念剽窃 動物の森収益化 大神ミオ権利者削除 戌神権利侵害発言 常闇トワ炎上 夜空メルストーカー被害 建築王サポーター放置 赤十字マーク 魔乃アロエ卒業 一つの中國支持声明 大空昴3Dライブ 無限延期清掃員職業差別 日清コラボ楽曲 musedash非公開 rog案件取り消し 壁画ライブ 丁真 Ding Zhen 郑爽 Zheng Shuang 防护林 与朵小天使w 伊月猫凛 本主萌埋午休傻 汪峰 重生细胞 壁纸 比利海灵顿 香蕉君 van 田所浩二 抽象带篮子 抗压背锅吧 季子越 蒋明辉 傻逼…\n\n\t0\t28\t28\nRevadike/InternalSteamWebAPI\n\nDocumenting the unofficial and internal Steam Web API\n\n\t1\t27\t28\nJoeSzymkowiczFiveM/qb-lootcrate\n\nA CSGO-style case opening script\n\n\t2\t25\t27\nAbrarKL/MyRoulette.XYZ\n\nCSGO / Steam Roulette Site created with PHP and Node JS, using the Material Design front-end framework.\n\n\t1\t25\t26\nJustArchiNET/ASF-WebConfigGenerator\n\nNo description in the capture.\n\n\t10\t15\t25\nModDota/dota-data\n\nAuto-generated Dota 2 resource dumps\n\n\t11\t14\t25\nModDota/TypeScriptDeclarations\n\nTypeScript declarations for Dota 2.\n\n\t11\t14\t25\nModDota/API\n\nNo description in the capture.\n\n\t12\t12\t24\nalliedmodders/cssdm\n\nCounter-Strike:Source Deathmatch\n\n\t10\t13\t23\nSteamDatabase/steamstat.us\n\n✅ Front-end of Steam services status website\n\n\t4\t18\t22\nc0deina/csgojackpotV2\n\nCSGO Jackpot Source\n\n\t1\t20\t21\nValvePython/steamctl\n\n🤸 Take control of Steam from your terminal\n\n\t2\t19\t21\nValvePython/csgo\n\n🔫 Python package for interacting with CS:GO Game Coordinator\n\n\t3\t17\t20\nBeepIsla/csgo-crash-exploit\n\nAllows you to crash any Windows user\n\n\t3\t16\t19\nValvePython/vpk\n\n📦 Open, Search, Extract and Create VPKs in python\n\n\t4\t15\t19\nalliedmodders/SM-SteamWorks\n\nExposing SteamWorks functions to SourcePawn.\n\n\t14\t3\t17\nSteamRE/Steam4NET\n\nSteam4NET is a .NET wrapper around the Steamworks C++ interfaces\n\n\t2\t15\t17\nalliedmodders/hl2sdk-manifests\n\nInformation about HL2SDKs shared between Metamod:Source and SourceMod.\n\n\t6\t10\t16\nJustArchiNET/ASF-PluginTemplate\n\nTemplate repository that you can use for creating custom plugins for ArchiSteamFarm.\n\n\t8\t7\t15\nModDota/Dota2AIFramework\n\nGeneral Framework for Dota 2 AI Competitions\n\n\t1\t14\t15\nShkyyl/KeyChamp\n\nExtension for joining free case battle on key-drop automatically\n\n\t1\t14\t15\nSteamDatabase/SteamMonitor\n\n😤 Track Steam's connection manager servers status\n\n\t2\t12\t14\nBaterka/cslore.com\n\nCS:GO gambling site - csgo.style\n\n\t1\t12\t13\nSteamDatabase/SteamTokenDumper\n\n🔢 Submit users' PICS access tokens to SteamDB\n\n\t2\t11\t13\nmonoblocker/roulette\n\nRoulette CS:GO made in React and Typescript\n\n\t1\t11\t12\nzsith/launcher.user.js\n\n// ==UserScript== // @name AposLauncher // @namespace AposLauncher // @include http://agar.io/* // @version 3.062 // @grant none // @author http://www.twitch.tv/apostolique // ==/UserScript== var aposLauncherVersion = 3.062; Nu…\n\n\t1\t11\t12\nLincolnIT/CSGODouble-bot-automated\n\nCSGODouble Automated, auto Betting Bot.\n\n\t1\t10\t11\nvladpuz/steam-market\n\nSteam market API client\n\n\t4\t7\t11\nmcgrizzz/Cstrike.bet\n\nCSGO Roulette Website Angular frontend, nodejs backend, and steam trading bots\n\n\t1\t9\t10\nodota/underlords-web\n\nUI for OpenUnderlords\n\n\t5\t5\t10\nSteamDatabase/SteamToTwitter\n\n🕊 Tweets announcements from various Steam groups\n\n\t1\t9\t10\nModDota/AbilityLuaSpellLibrary\n\nThe successor to the Spell Library by Pizzalol\n\n\t4\t4\t8\nalvinl/bitskins\n\nUnofficial BitSkins API client\n\n\t2\t5\t7\nb1naryth1ef/steamy\n\nA Python Steam community and market API interface that will get you all hot and bothered\n\n\t2\t5\t7\nkratos1812/Case-Opening\n\nIn-game case opening system for CSGO servers.\n\n\t2\t5\t7\nodota/docs\n\nOpenDota API documentation\n\n\t4\t3\t7\nSteamDatabase/steam-advanced-access-fetch-players\n\n📈 Simple script to fetch Steam player count\n\n\t1\t6\t7\nTheRioMiner/CsgoBetterExternalRaytrace\n\nOverridden maps pack for better external raytrace\n\n\t1\t6\t7\nalliedmodders/hl2sdk-mock\n\nMock HL2SDK and Server\n\n\t5\t1\t6\nchristophersu/PySteamMarket\n\nPython API for getting prices from the Steam market.\n\n\t1\t5\t6\nExtremelyd1/Strat-Roulette\n\nCS:GO Sourcemod Plugin\n\n\t2\t4\t6\ngiovanni-orciuolo/double-sdk\n\nA simple way to write CS:GO cheats!\n\n\t2\t4\t6\nJustArchiNET/Madness\n\nMadness embraces your project by including compatibility layer for selected APIs normally not available on .NET Framework target.\n\n\t5\t1\t6\nModDota/TypescriptPanoramaDeclarations\n\nNo description in the capture.\n\n\t4\t2\t6\nodota/rapier\n\nA JavaScript Dota 2 (Source 2) replay parsing library\n\n\t1\t5\t6\nVozn1akHero/CSGOCaseOpeningSimulator\n\nCounter-Strike case opening simulator which resembles the good old CS:GO user interface\n\n\t3\t3\t6\nautarc/steam-store\n\nAPI client for the unofficial steam storefront/big picture resource\n\n\t2\t3\t5\nBETTING-CODE/awesome-esports-sites\n\nA curated list of awesome esport betting sites – live, statistics and other resources.\n\n\t1\t4\t5\njonteohr/Better-Warden\n\nAn improved and more advanced warden plugin with a custom menu for CS:GO jailbreak servers!\n\n\t2\t3\t5\nLudzikk/CSGO-Gambling-Site\n\nhttps://ludzikk.github.io/CSGO-Gambling-Site/\n\n\t1\t4\t5\nModDota/find-steam-app\n\nFind location of an installed Steam app\n\n\t3\t2\t5\nmprey/csgocact.us\n\nsource code for csgocact.us\n\n\t1\t4\t5\nnezu-cc/ServerCrasher\n\nCS:GO Server Crasher\n\n\t1\t4\t5\nodota/testfiles\n\nStores test replay files\n\n\t2\t3\t5\nodota/underlordsconstants\n\nConstant data for Dota Underlords\n\n\t3\t2\t5\nSnaBe/node-steam-market-fetcher\n\nA Node.js wrapper for the Steam Community Market API.\n\n\t2\t3\t5\nSteamDatabase/.github\n\n💗 Organization-wide community health files\n\n\t1\t4\t5\nwolfcon/RIP-HLTV-BET\n\nRIP BET AD (For Tampermonkey) https://greasyfork.org/en/scripts/423484-rip-hltv-bet\n\n\t2\t3\t5\nalliedmodders/blaster.net\n\nSource and GoldSrc Query Tool\n\n\t2\t2\t4\ncatears124/CS2-Price-API\n\nsimple python cs2 steam market price API\n\n\t1\t3\t4\nialakey/caseforge\n\nOpen-source CS2 case-opening platform: Steam auth, provably fair openings, RTP-balanced case builder, withdrawals bought on market.csgo.com and an admin CRM.\n\n\t1\t3\t4\nIlusion9/csgo-fix-mapchange-crash-sm\n\nFix players crash on map change.\n\n\t1\t3\t4\nismail0234/Benson-Map-Crash-Fixer\n\nCSGO Map Change Client Crash Fixer\n\n\t1\t3\t4\njaxwilko/steam-market-api\n\nPHP - Composer Compatible - Steam Market API\n\n\t2\t2\t4\nJustArchiNET/ArchiTag\n\nArchiTag is a very small utility based on Python 3 and Mutagen to provide missing functionality in opusenc of writing specific Opus metadata, such as total number of tracks or track number.\n\n\t1\t3\t4\nModDota/DotaUI\n\nNo description in the capture.\n\n\t2\t2\t4\nnode-steam/market-pricing\n\nWrapper for the unofficial Steam Market Pricing API\n\n\t1\t3\t4\nodota/media\n\nStores media files for Dota projects\n\n\t2\t2\t4\nSergeyIvanovDevelop/Crypto-Steam-Platform\n\nThe repository contains the code and configuration to run a platform for creating cryptocurrency stakes for arbitrary ERC20 tokens.\n\n\t1\t3\t4\nAareksio/csgodouble-floatchecker\n\nAdds context menu option to check item's float value\n\n\t1\t2\t3\nchinm4/CSGOdrop\n\nA online csgo gambling casino that includes a variety of mini games that allows you to win csgo skins\n\n\t2\t1\t3\nCruze03/CSGO-Case-Opening-Prank\n\nCommand:- !prank (Admin flag \"n\" required)\n\n\t1\t2\t3\nDhruva-Kapadia/CSGOTrollGG\n\nCSGO Case Opening Simulator\n\n\t2\t1\t3\nErhanCSGO/CSGOPolygon-prediction\n\nCSGOPolygon.com - prediction script, double your coins by using this tool\n\n\t1\t2\t3\nEv-Hoang/Bedrock-Chest-Case-Opening\n\nHypixel Skyblock Dungeon Mod - Bedrock Chest Opening Animation (CSGO Style)\n\n\t1\t2\t3\njmjp/csgo-roulette\n\nA csgo gambling roulette make with VueJS 3\n\n\t2\t1\t3\nJustArchiNET/ArchiCrowdin\n\nNo description in the capture.\n\n\t1\t2\t3\nLeonSK/WearMarketInspector\n\nRetrieve Wear Value (Float Value) and Pattern Index from Steam Community Market using http://csgo.exchange API\n\n\t1\t2\t3\nmaximgeerinck/csgo-gamble\n\nCSGO gambling website\n\n\t1\t2\t3\nModDota/BugTracker\n\nListing bugs for Dota 2 Custom Games\n\n\t2\t1\t3\nplwp/mma-betting\n\nUFC/MMA betting model with Pinnacle steam detection for AU book latency arb\n\n\t2\t1\t3\nSouthsideswag16/Csgo-Gambling-Site\n\nNo description in the capture.\n\n\t2\t1\t3\ntacyarg/csgofiesta-frontend-react\n\nRemastered version a the long time favorite csgo site\n\n\t2\t1\t3\nVelorasse/Mutah-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-csmoney-csgoskins\n\ngambling script for Mutah, Keydrop, csmoney, and csgoskins, featuring hacks, cheats, and predictors. Offers strategies to boost winning odds and optimize performance on these platforms.\n\n\t3\t0\t3\nalliedmodders/am-github-artifact-webhook\n\nNo description in the capture.\n\n\t2\t0\t2\ncharamza/roulette\n\nCSGO like roulette in JS\n\n\t1\t1\t2\nCruze03/CSGO-PugSetup-RoundRestore\n\nSometimes (player dropped/crashed) which would be disadvantage for a team. It would be very handy to restore the match to the previous round.\n\n\t1\t1\t2\ncsgorol/CSGO-ROLL-Crash-Predictor\n\nCSGO-ROLL-Crash-Predictor\n\n\t1\t1\t2\nFoxSerito/FOXWORLD_plugin_DoubleJump_CSGO\n\nПлагин SourceMod (CSGO). Двойной прыжок с эффектом.\n\n\t1\t1\t2\nhkehayovmoonbiz/CS2-Casino-Full-Source-Code\n\nCS2, CS2 betting platforms, Skin Roulette, Case Unboxing, Crash games, Jackpot, purchase CS2 casino source, crypto gambling\n\n\t1\t1\t2\nJustZakary/steamstoreapi\n\nThis NPM module is a API wrapper that makes the steam unofficial API easier to use.\n\n\t2\t0\t2\njzimr/steam-market-api\n\nA java library to easily get Steam Community Market data\n\n\t1\t1\t2\nMomohime/CSGO.Network-Jackpot-Coinflip\n\nNo description in the capture.\n\n\t1\t1\t2\nnnjjswat/moneybot\n\nautomated bots for bustabit (formerly known as moneypot), csgo crash, etc\n\n\t0\t2\t2\nodota/carry\n\nLegacy Application for donations to the OpenDota project\n\n\t1\t1\t2\nodota/PublicMatchDataBot\n\nA Discord bot to remind users to turn on Expose Public Match Data in the Dota 2 client\n\n\t1\t1\t2\nOrillio/CSGOBet.com\n\nCSGO roulette web app\n\n\t2\t0\t2\nripexz/csgo-bet-alert\n\nA Chrome extension to keep track of active CS:GO Lounge matches.\n\n\t1\t1\t2\nrrpvm/lumen_sense-beta-deprecated-\n\nthis is internal csgo cheat written by me(no paste, self reverse structures). start : ~6 August 2020, end : ~ 14 December 2020\n\n\t1\t1\t2\nRuthless222/csgoscore\n\nThis is a Counter Strike Global Offensive Betting Site. You chose the skins you want to bet and try to win jackpots\n\n\t2\t0\t2\ntfburns/CSGO-cases-PL\n\nExpected profit-loss of CS:GO case openings\n\n\t1\t1\t2\nTomDra/CSGO-Case-Data-Analysis\n\nWorks out the most profitable CS:GO case at that current time\n\n\t1\t1\t2\nValvePython/dota2-wrappers\n\nNo description in the capture.\n\n\t1\t1\t2\nValvePython/teamfortress2-closed-captions\n\nThis project aims to provide a set of closed captions for Team Fortress 2\n\n\t1\t1\t2\nVistaNetGTX/Cstrike.bet-\n\nCSGO Roulette Website Angular frontend, nodejs backend, and steam trading bots\n\n\t1\t1\t2\nwafflas/csgo-case-opening-simulator\n\nI created a cs go case opening simulator for a meme coin\n\n\t0\t2\t2\nAdmiral-Enigma/Le_Coinflip\n\nConflip game\n\n\t1\t0\t1\nadryeljuliao/roulette-csgo\n\nNo description in the capture.\n\n\t1\t0\t1\nAndreuTheG/csgo-coinflip-web\n\nCSGO Gambling Coinflip Website\n\n\t1\t0\t1\nasmilen/csgoDouble\n\na b c\n\n\t1\t0\t1\nb1naryth1ef/csgofort\n\nA CSGO portal for trading, betting, analytics, and more!\n\n\t1\t0\t1\nBaterka/PrivateSteamBettingWebsite2024\n\nPrivate Steam (Counter-Strike 2) betting/gambling website - Roulette, Jackpot\n\n\t1\t0\t1\nblackcaer/SteamTradeHandler\n\nAutomation of Steam trading. Helper project for bet automation.\n\n\t1\t0\t1\nBTheCoderr/theRounders\n\nThe Rounders - A professional-grade sports betting analytics platform combining real-time odds tracking, sharp movement detection, and advanced statistical analysis. Features include line shopping, steam move alerts, power rankings, and comprehensive bet t…\n\n\t1\t0\t1\nCallumHemsley/KazeBot\n\nA Twitch chat betting bot for CSGO, simply bet a certain amount of points, and double if you win, lose all if you lose. Simple.\n\n\t1\t0\t1\nchrisjpm/CSGOJackpotTemplate\n\nFront end for a jackpot site\n\n\t1\t0\t1\ncolinsenner/valve-bug-bounty\n\nFor many years CS:GO, Dota 2, and Team Fortress 2 servers had a bug that allowed malicious users to leak crucial server process memory or reliably crash any server.\n\n\t1\t0\t1\ncoryypeters/nrl-odds-intelligence-pipeline\n\nReal-time sports betting odds intelligence — streaming pipeline that detects line movement, steam, and arbitrage across bookmakers. Python · Redis Streams · FastAPI · React.\n\n\t1\t0\t1\ndeissh/dev-csgoduo\n\nCS:GO. Bot for receiving things on the site (Polygon, Duo, Double and etc).\n\n\t1\t0\t1\ndom1torii/even-better-font-manager\n\nSimply even better cross-platform tool for CS2 Font Management\n\n\t1\t0\t1\nDONnicov/CSGO-crash-black-screen-\n\nsolution csgo crash black screen and close csgo\n\n\t1\t0\t1\nDoubleBoters/CsgoDouble\n\nNo description in the capture.\n\n\t1\t0\t1\ndownarowiczd/DoubleBot\n\nAn old CSGO Double Bot written for my friend. - 07.05.2016\n\n\t1\t0\t1\nErayBahar/steammarketscraper\n\nSteam Market Scraper Python-based tool that tracks real-time CS2 skin prices using Steam's hidden API. It fetches the lowest sell and highest buy offers for any item, helping you monitor deals or snipe underpriced listings automatically.\n\n\t1\t0\t1\nfairydarkness/SteamwebmailAPI\n\nUnofficial Python API for steamwebmail.com Fast, lightweight, and browserless library for automating steamwebmail.com. Support for session management, proxy, folder navigation, and message retrieval\n\n\t1\t0\t1\nFAQU2/CSGO-Coinflip-MyJailShop\n\nSourcemod plugin which provides a Coinflip system for MyJailShop.\n\n\t1\t0\t1\nFlamesONE/csgo-case-opening\n\nNo description in the capture.\n\n\t1\t0\t1\nFunnyRain/csgorun-crash-watch\n\n🚀 CsgoRun dump crash. / 🚀 CsgoRun дамп крашей.\n\n\t1\t0\t1\ngeohdgio/Venatus-Autenticator\n\nეს არის Steam Autenticator ქართული Venatus Trade & Betting ისთვის და Valve News Georgia-სთვის.\n\n\t1\t0\t1\nhakanstarlord/steam-bot\n\nSports betting steam-move signal detection with ML pipeline (XGBoost stacking + isotonic calibration), backtesting engine, Flask dashboard, and Telegram alerts.\n\n\t1\t0\t1\nHvH-gg/CSGO-Item-CrashFix\n\nA plugin for Counter-Strike: Global Offensive that fixes an exploit where receiving CS2 Items will cause CS:GO clients to crash\n\n\t1\t0\t1\nHvH-gg/CSGO-NetMsg-CrashFix\n\nA plugin for Counter-Strike: Global Offensive that fixes an exploit where spamming NetMsg_StringCmd packets would result in a server crash.\n\n\t1\t0\t1\nisybycnsmam/SteamLibrary\n\nLegacy Steam Unofficial API\n\n\t1\t0\t1\nItsTangerine/SteamApis.Net\n\nUnofficial https://steamapis.com .NET library, supporting .NET 6.0+\n\n\t1\t0\t1\nJustArchiNET/JustArchi.net\n\nNo description in the capture.\n\n\t1\t0\t1\nkiri-osint/CS2-Info-Hub-Bot\n\nA Telegram bot that acts as a hub for CS2 players, providing real-time skin prices, server stats, and user profile/inventory inspection using official and unofficial Steam APIs.\n\n\t1\t0\t1\nKoshkaj/monte\n\nGamified csgo gambling platform implementation\n\n\t1\t0\t1\nmadsab/CaseOpening\n\nA school project using Java. Simulating the case opening from CSGO and more.\n\n\t1\t0\t1\nman90es/steamcardexchange-api\n\nSteamCardExchange.net unofficial REST API server (scraper).\n\n\t1\t0\t1\nMattPua/steam-unofficial-docs\n\nUnofficial docs for Steam APIs with fumadocs\n\n\t1\t0\t1\nMetallist1/Portfolio.CsgoWinGambleProject\n\nA website that was done in 2017 September. Websites focus was on gambling with Counter-Strike items. Project was largely completed however backups were not done correctly, this resulted in half a year of wasted improvements to the code. The website was test…\n\n\t1\t0\t1\nmikebobadilla/csgo-jackpot\n\nNo description in the capture.\n\n\t0\t1\t1\nmikebobadilla/meteor-csgojackpot\n\nCssgo Jackpot done in meteor\n\n\t1\t0\t1\nModDota/D2VDump\n\nDota 2 Server VScript API Dumper\n\n\t1\t0\t1\nModDota/DotaTracking\n\nNo description in the capture.\n\n\t1\t0\t1\nModDota/eslint-config\n\nESLint config by ark120202\n\n\t1\t0\t1\nmr-codinglv/Casino-script\n\nscript casino - script betting - exchange script - bc casino - casino csgo - script bet - betwin script\n\n\t1\t0\t1\nMrKeelik/MrKeel\n\nCSGO DOUBLE BOT\n\n\t1\t0\t1\nnoahlatzel/CSGORollHelper\n\nLeveraging positive expected value on triple green jackpots on CSGORoll!\n\n\t1\t0\t1\noddsgpt/oddsgpt-market-intelligence\n\nResearch on football betting markets, closing odds, CLV, market efficiency, steam moves, AI betting systems, and sports market intelligence.\n\n\t1\t0\t1\noEXU/csgo-server-crasher\n\nCSGO SERVER CRASHER\n\n\t1\t0\t1\nPrdTTony/CSGO-Roulette\n\n[CSGO] Roulette System. Bet on RED or Black and win x2 credits\n\n\t1\t0\t1\nr-adamski/csgo-jackpot\n\nNo description in the capture.\n\n\t1\t0\t1\nSahotallo/Turan-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-Skinbaron-hellcase\n\ngambling script for Turan, Keydrop, Skinbaron, and Hellcase, providing hacks, cheats, and predictors. Includes strategies to improve winning chances and enhance gameplay on these platforms.\n\n\t1\t0\t1\nsamuelcsouza/steam-marketplace-api\n\nAn unofficial API to get data from the Steam Marketplace.\n\n\t1\t0\t1\nSKINSTRACK/CS2-Price-API\n\nSkinstrack offers a free, limited API endpoint that returns Steam item prices. Paid plans additionally provide access to pricing data from multiple marketplaces, making it possible to compare prices across different markets through a single API.\n\n\t1\t0\t1\nsnmtriet/CSGO-Casino-Full-Source-Code\n\nCSGO, CSGOEmpire, Case Opening, Case Battles, Roulette, Coinflip, buy csgo gambling site, gambling\n\n\t1\t0\t1\nSteamRE/homebrew-tools\n\nRepository for installation of SteamRE tools via Homebrew (http://brew.sh)\n\n\t1\t0\t1\nSteamRE/opensteamworks.org\n\nNo description in the capture.\n\n\t1\t0\t1\nTheQuack45/CsgoCaseOpenProgram\n\nSimple program to parse an XML file with CS:GO case information and \"simulate\" case openings\n\n\t1\t0\t1\nTLClassless/StratRouletteCSGO\n\nA 'Strat Roulette' web app for CS:GO!\n\n\t1\t0\t1\ntomasoom/csgoCaseOpening\n\nNo description in the capture.\n\n\t1\t0\t1\nvitaliy-evsyukov/steamgifts-autobet-bookmarklet\n\nbookmarklet for automatic bets on steamgifts.com\n\n\t1\t0\t1\nXpravdaX/RouletteCSGO\n\nNo description in the capture.\n\n\t1\t0\t1\nYuiKasumii/steam_api_unofficial\n\nUnofficial Steam Game Information Database\n\n\t1\t0\t1\nZexuz/Steam-Betting\n\nA betting website build ontop of STEAM's ecosystem\n\n\t1\t0\t1\nANK-RULZZ/steam-jackpot-site\n\ngetting some errors and would like some one to help me with it thank you!!!\n\n\t0\t0\t0\nasmilen/CsgoDoubleVS\n\nNo description in the capture.\n\n\t0\t0\t0\nCORNOODOSADAS/CSGOWeed\n\nCsgo Jackpot and Coinflip\n\n\t0\t0\t0\nCSGOApple/csgoapple\n\nJackpot Site\n\n\t0\t0\t0\nCSGOFAST/csgofast-api\n\nNo description in the capture.\n\n\t0\t0\t0\nDonakall/csgoDoublebot\n\nAutomated bot for csgodouble\n\n\t0\t0\t0\nfedor-selivanov/csgo-fast-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nfoldageros/csgod\n\ndouble bot\n\n\t0\t0\t0\ngmod-gambling/gmod-gambling\n\nNo description in the capture.\n\n\t0\t0\t0\nierome/CSGOBoss-BackEnd\n\nBack end version of CSGOBoss. This was a CSGO Gambling site named CSGOBoss. Coded by an old friend of mine Dahquan Hinds (https://github.com/dahquan/) Thought I would release this to help out any one who would need it.\n\n\t0\t0\t0\njamienp1/CSGODOUBLE-BOT-AUTO\n\ni got a bot thats is betting on the last winning color except from green and if you lose it will double the coins you set it to bet, pretty good, so when there comes a loooong train you will be gaining a bit of money codepaste_net/ugmt92 remove all the _ an…\n\n\t0\t0\t0\nJEYONER/CSGOTOXIC\n\nPAGINA DE JACKPOT CSGO SKINS\n\n\t0\t0\t0\nkalrish/csgo-jackpot\n\nStressful but funny zombie-like Counter-Strike: Global Offensive game mode.\n\n\t0\t0\t0\nkrys12345/roulettee\n\n// ==UserScript== // @name CSGO Predict Bot // @namespace http://csgodouble.com // @version 1.0 // @description predicts what number its gonna be // @author Meee // @match http://www.csgodouble.com/ // @grant none // ==/…\n\n\t0\t0\t0\nLilDuggiMuffi/CSGODouble-Working-Bot\n\nFixed CSGO Double Bot\n\n\t0\t0\t0\nLyricLy/Steam2Proton\n\nCheck if all your Steam games will work with Proton! Uses the official Steam API and the unofficial Proton API.\n\n\t0\t0\t0\nM0NsTeR77/csgo-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nozanhalis/Hi\n\n// ==UserScript== // @name CS GO LOUNGE BOT-Ozan Halis // @namespace http://csgolounge.com/ // @version 0.6.6 // @description Cs Go Lounge Hızlı BOT // @match http://csgolounge.com/* // @match http://dota2lounge.com/* // @updateURL h…\n\n\t0\t0\t0\nscoobertus/CSGO-DoubleBot\n\nNo description in the capture.\n\n\t0\t0\t0\nTradeal/CSGO-Jackpot-Bot\n\nNo description in the capture.\n\n\t0\t0\t0\nValvePython/artifact\n\nNo description in the capture.\n\n\t0\t0\t0\nVampire/CSGO-Roulette-Bot\n\nNo description in the capture.\n\n\t0\t0\t0\nvdemans/csgo-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nVocoreVideo/CSGODungeon-\n\nCSGO Jackpot\n\n\t0\t0\t0\nwayz-dev/csgofloat\n\nNo description in the capture.\n\n\t0\t0\t0\n\nЗнімок: 17 вересня 2026, 11:19:11, як зазначено у джерелі; часовий пояс не вказано. У експорті наведено обмежену кількість даних про взаємозв’язки (багато категорій закінчуються на 40). Кількість авторів та розробників, які створили форки, становить 4,554 записів про ролі у 4,214 різних пар «профіль–репозиторій»; один профіль може мати обидві ролі. Нуль означає відсутність записів у цій категорії. Назви репозиторіїв можуть містити псевдоніми або варіанти з різним регістром; у підсумках дотримано правил підрахунку, що використовуються у вихідному коді.\n\nПоходження джерела\nСтворено на основі ваших зібраних файлів.\nСвідчення на підтримку\n2323/reddit_scams_ultra/steam_support_tickets_MEGA.json · рядки 45, 58, 107, 110, 294\nЗнімок мережі\nnetwork-repositories.csv · raw_data.json · overlaps.csv · summary.txt (історичні шляхи до джерел збережено в маніфесті)\n\nУ маніфесті зазначаються шляхи до джерел, розміри у байтах, хеш-значення SHA-256, а також позиції вибраних записів. Необроблені дані зберігаються окремо від результатів аналізу, проведеного в рамках розслідування.\n\nЗавантажити маніфест вихідного коду ↓",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam Докази щодо виконання зобов’язань — супровідна документація та мережа розробників"
          },
          {
            "level": 2,
            "id": null,
            "text": "Ознайомтеся зі скаргою.Додайте вихідний код."
          },
          {
            "level": 3,
            "id": null,
            "text": "Permanent sanction & closed appeals"
          },
          {
            "level": 4,
            "id": null,
            "text": "Permanently banned Steam account without a clear explanation, need help!"
          },
          {
            "level": 3,
            "id": null,
            "text": "Account recovery & a reported $10,000 loss"
          },
          {
            "level": 4,
            "id": null,
            "text": "Got $10k stollen from steam inventory due to steam' support fault."
          },
          {
            "level": 3,
            "id": null,
            "text": "A reported $500+ loss & template replies"
          },
          {
            "level": 4,
            "id": null,
            "text": "Funds stolen through steam market. Disappointed with Steam response.(or lackthereof)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam Guard & an item-restoration refusal"
          },
          {
            "level": 4,
            "id": null,
            "text": "Many people are losing item via clicking links where steam guard is enabled and steam support doesn't not restore items."
          },
          {
            "level": 3,
            "id": null,
            "text": "Selective enforcement & an unexplained ban"
          },
          {
            "level": 4,
            "id": null,
            "text": "🚨 Steam Bans Without Reason and Ignores Its Community — What’s Going On?"
          },
          {
            "level": 2,
            "id": null,
            "text": "Громадська інфраструктура.Записано у повному масштабі."
          },
          {
            "level": 2,
            "id": null,
            "text": "Створено на основі ваших зібраних файлів."
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/uk/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/uk/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/selected-support-records.json",
          "https://phishdestroy.io/steam_dossier/uk/investigation_part2.html#outsourcing-case",
          "https://www.reddit.com/r/ohnePixel/comments/1hahqx2/permanently_banned_steam_account_without_a_clear/",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://www.reddit.com/r/DotA2/comments/r55bd7/many_people_are_losing_item_via_clicking_links/",
          "https://www.reddit.com/r/SteamUncensored/comments/1kjt2fa/steam_bans_without_reason_and_ignores_its/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/network-repositories.csv",
          "https://github.com/alliedmodders/amxmodx",
          "https://github.com/alliedmodders/sourcemod",
          "https://github.com/DoctorMcKay/node-steam-user",
          "https://github.com/Facepunch/Facepunch.Steamworks",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://github.com/odota/core",
          "https://github.com/odota/dotaconstants",
          "https://github.com/odota/web",
          "https://github.com/splewis/get5",
          "https://github.com/SteamDatabase/FileDetectionRuleSets",
          "https://github.com/SteamRE/SteamKit",
          "https://github.com/ValveSoftware/dxvk",
          "https://github.com/ValveSoftware/GameNetworkingSockets",
          "https://github.com/ValveSoftware/gamescope",
          "https://github.com/ValveSoftware/Proton",
          "https://github.com/ValveSoftware/source-sdk-2013",
          "https://github.com/ValveSoftware/wine",
          "https://github.com/ValveSoftware/steam-devices",
          "https://github.com/ValveSoftware/steam-audio",
          "https://github.com/alliedmodders/metamod-source",
          "https://github.com/alliedmodders/sourcepawn",
          "https://github.com/ValveSoftware/Fossilize",
          "https://github.com/rlabrecque/Steamworks.NET",
          "https://github.com/ModDota/moddota.github.io",
          "https://github.com/odota/parser",
          "https://github.com/ValveSoftware/steam-for-linux",
          "https://github.com/SteamRE/DepotDownloader",
          "https://github.com/JustArchiNET/ASF-ui",
          "https://github.com/advancedfx/advancedfx",
          "https://github.com/alliedmodders/ambuild",
          "https://github.com/SteamDatabase/BrowserExtension",
          "https://github.com/odota/mobile",
          "https://github.com/ValvePython/steam",
          "https://github.com/skadistats/clarity",
          "https://github.com/SteamRE/open-steamworks",
          "https://github.com/ValveSoftware/Source-1-Games",
          "https://github.com/alliedmodders/hl2sdk",
          "https://github.com/SteamDatabase/steamdb.info-issues",
          "https://github.com/CSGOFloat/inspect",
          "https://github.com/ValveSoftware/SteamOS",
          "https://github.com/alliedmodders/source2mod",
          "https://github.com/smiley/steamapi",
          "https://github.com/SteamDatabase/GameTracking",
          "https://github.com/ValveSoftware/counter-strike_rules_and_regs",
          "https://github.com/ValveSoftware/openvr",
          "https://github.com/SteamDatabase/easy-markdown-editor",
          "https://github.com/ValveSoftware/Dota-2",
          "https://github.com/ValveSoftware/Dota2-Gameplay",
          "https://github.com/JustArchiNET/ArchiBot",
          "https://github.com/ztizzlegaming/CSGOWinBig",
          "https://github.com/JustArchiNET/mantis.justarchi.net",
          "https://github.com/odota/node-steam-user",
          "https://github.com/ModDota/TypeScriptAddonTemplate",
          "https://github.com/ValvePython/vdf",
          "https://github.com/alliedmodders/amtl",
          "https://github.com/ValvePython/dota2",
          "https://github.com/alliedmodders/stripper-source",
          "https://github.com/Allyans3/steam-market-api-v2",
          "https://github.com/ModDota/dota-tutorial",
          "https://github.com/odota/blog",
          "https://github.com/OpsecGuy/BetterGo",
          "https://github.com/pxvr-official/1",
          "https://github.com/Revadike/InternalSteamWebAPI",
          "https://github.com/JoeSzymkowiczFiveM/qb-lootcrate",
          "https://github.com/AbrarKL/MyRoulette.XYZ",
          "https://github.com/JustArchiNET/ASF-WebConfigGenerator",
          "https://github.com/ModDota/dota-data",
          "https://github.com/ModDota/TypeScriptDeclarations",
          "https://github.com/ModDota/API",
          "https://github.com/alliedmodders/cssdm",
          "https://github.com/SteamDatabase/steamstat.us",
          "https://github.com/c0deina/csgojackpotV2",
          "https://github.com/ValvePython/steamctl",
          "https://github.com/ValvePython/csgo",
          "https://github.com/BeepIsla/csgo-crash-exploit",
          "https://github.com/ValvePython/vpk",
          "https://github.com/alliedmodders/SM-SteamWorks",
          "https://github.com/SteamRE/Steam4NET",
          "https://github.com/alliedmodders/hl2sdk-manifests",
          "https://github.com/JustArchiNET/ASF-PluginTemplate",
          "https://github.com/ModDota/Dota2AIFramework",
          "https://github.com/Shkyyl/KeyChamp",
          "https://github.com/SteamDatabase/SteamMonitor",
          "https://github.com/Baterka/cslore.com",
          "https://github.com/SteamDatabase/SteamTokenDumper",
          "https://github.com/monoblocker/roulette",
          "https://github.com/zsith/launcher.user.js",
          "https://github.com/LincolnIT/CSGODouble-bot-automated",
          "https://github.com/vladpuz/steam-market",
          "https://github.com/mcgrizzz/Cstrike.bet",
          "https://github.com/odota/underlords-web",
          "https://github.com/SteamDatabase/SteamToTwitter",
          "https://github.com/ModDota/AbilityLuaSpellLibrary",
          "https://github.com/alvinl/bitskins",
          "https://github.com/b1naryth1ef/steamy",
          "https://github.com/kratos1812/Case-Opening",
          "https://github.com/odota/docs",
          "https://github.com/SteamDatabase/steam-advanced-access-fetch-players",
          "https://github.com/TheRioMiner/CsgoBetterExternalRaytrace",
          "https://github.com/alliedmodders/hl2sdk-mock",
          "https://github.com/christophersu/PySteamMarket",
          "https://github.com/Extremelyd1/Strat-Roulette",
          "https://github.com/giovanni-orciuolo/double-sdk",
          "https://github.com/JustArchiNET/Madness",
          "https://github.com/ModDota/TypescriptPanoramaDeclarations",
          "https://github.com/odota/rapier",
          "https://github.com/Vozn1akHero/CSGOCaseOpeningSimulator",
          "https://github.com/autarc/steam-store",
          "https://github.com/BETTING-CODE/awesome-esports-sites",
          "https://github.com/jonteohr/Better-Warden",
          "https://github.com/Ludzikk/CSGO-Gambling-Site",
          "https://github.com/ModDota/find-steam-app",
          "https://github.com/mprey/csgocact.us",
          "https://github.com/nezu-cc/ServerCrasher",
          "https://github.com/odota/testfiles",
          "https://github.com/odota/underlordsconstants",
          "https://github.com/SnaBe/node-steam-market-fetcher",
          "https://github.com/SteamDatabase/.github",
          "https://github.com/wolfcon/RIP-HLTV-BET",
          "https://github.com/alliedmodders/blaster.net",
          "https://github.com/catears124/CS2-Price-API",
          "https://github.com/ialakey/caseforge",
          "https://github.com/Ilusion9/csgo-fix-mapchange-crash-sm",
          "https://github.com/ismail0234/Benson-Map-Crash-Fixer",
          "https://github.com/jaxwilko/steam-market-api",
          "https://github.com/JustArchiNET/ArchiTag",
          "https://github.com/ModDota/DotaUI",
          "https://github.com/node-steam/market-pricing",
          "https://github.com/odota/media",
          "https://github.com/SergeyIvanovDevelop/Crypto-Steam-Platform",
          "https://github.com/Aareksio/csgodouble-floatchecker",
          "https://github.com/chinm4/CSGOdrop",
          "https://github.com/Cruze03/CSGO-Case-Opening-Prank",
          "https://github.com/Dhruva-Kapadia/CSGOTrollGG",
          "https://github.com/ErhanCSGO/CSGOPolygon-prediction",
          "https://github.com/Ev-Hoang/Bedrock-Chest-Case-Opening",
          "https://github.com/jmjp/csgo-roulette",
          "https://github.com/JustArchiNET/ArchiCrowdin",
          "https://github.com/LeonSK/WearMarketInspector",
          "https://github.com/maximgeerinck/csgo-gamble",
          "https://github.com/ModDota/BugTracker",
          "https://github.com/plwp/mma-betting",
          "https://github.com/Southsideswag16/Csgo-Gambling-Site",
          "https://github.com/tacyarg/csgofiesta-frontend-react",
          "https://github.com/Velorasse/Mutah-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-csmoney-csgoskins",
          "https://github.com/alliedmodders/am-github-artifact-webhook",
          "https://github.com/charamza/roulette",
          "https://github.com/Cruze03/CSGO-PugSetup-RoundRestore",
          "https://github.com/csgorol/CSGO-ROLL-Crash-Predictor",
          "https://github.com/FoxSerito/FOXWORLD_plugin_DoubleJump_CSGO",
          "https://github.com/hkehayovmoonbiz/CS2-Casino-Full-Source-Code",
          "https://github.com/JustZakary/steamstoreapi",
          "https://github.com/jzimr/steam-market-api",
          "https://github.com/Momohime/CSGO.Network-Jackpot-Coinflip",
          "https://github.com/nnjjswat/moneybot",
          "https://github.com/odota/carry",
          "https://github.com/odota/PublicMatchDataBot",
          "https://github.com/Orillio/CSGOBet.com",
          "https://github.com/ripexz/csgo-bet-alert",
          "https://github.com/rrpvm/lumen_sense-beta-deprecated-",
          "https://github.com/Ruthless222/csgoscore",
          "https://github.com/tfburns/CSGO-cases-PL",
          "https://github.com/TomDra/CSGO-Case-Data-Analysis",
          "https://github.com/ValvePython/dota2-wrappers",
          "https://github.com/ValvePython/teamfortress2-closed-captions",
          "https://github.com/VistaNetGTX/Cstrike.bet-",
          "https://github.com/wafflas/csgo-case-opening-simulator",
          "https://github.com/Admiral-Enigma/Le_Coinflip",
          "https://github.com/adryeljuliao/roulette-csgo",
          "https://github.com/AndreuTheG/csgo-coinflip-web",
          "https://github.com/asmilen/csgoDouble",
          "https://github.com/b1naryth1ef/csgofort",
          "https://github.com/Baterka/PrivateSteamBettingWebsite2024",
          "https://github.com/blackcaer/SteamTradeHandler",
          "https://github.com/BTheCoderr/theRounders",
          "https://github.com/CallumHemsley/KazeBot",
          "https://github.com/chrisjpm/CSGOJackpotTemplate",
          "https://github.com/colinsenner/valve-bug-bounty",
          "https://github.com/coryypeters/nrl-odds-intelligence-pipeline",
          "https://github.com/deissh/dev-csgoduo",
          "https://github.com/dom1torii/even-better-font-manager",
          "https://github.com/DONnicov/CSGO-crash-black-screen-",
          "https://github.com/DoubleBoters/CsgoDouble",
          "https://github.com/downarowiczd/DoubleBot",
          "https://github.com/ErayBahar/steammarketscraper",
          "https://github.com/fairydarkness/SteamwebmailAPI",
          "https://github.com/FAQU2/CSGO-Coinflip-MyJailShop",
          "https://github.com/FlamesONE/csgo-case-opening",
          "https://github.com/FunnyRain/csgorun-crash-watch",
          "https://github.com/geohdgio/Venatus-Autenticator",
          "https://github.com/hakanstarlord/steam-bot",
          "https://github.com/HvH-gg/CSGO-Item-CrashFix",
          "https://github.com/HvH-gg/CSGO-NetMsg-CrashFix",
          "https://github.com/isybycnsmam/SteamLibrary",
          "https://github.com/ItsTangerine/SteamApis.Net",
          "https://github.com/JustArchiNET/JustArchi.net",
          "https://github.com/kiri-osint/CS2-Info-Hub-Bot",
          "https://github.com/Koshkaj/monte",
          "https://github.com/madsab/CaseOpening",
          "https://github.com/man90es/steamcardexchange-api",
          "https://github.com/MattPua/steam-unofficial-docs",
          "https://github.com/Metallist1/Portfolio.CsgoWinGambleProject",
          "https://github.com/mikebobadilla/csgo-jackpot",
          "https://github.com/mikebobadilla/meteor-csgojackpot",
          "https://github.com/ModDota/D2VDump",
          "https://github.com/ModDota/DotaTracking",
          "https://github.com/ModDota/eslint-config",
          "https://github.com/mr-codinglv/Casino-script",
          "https://github.com/MrKeelik/MrKeel",
          "https://github.com/noahlatzel/CSGORollHelper",
          "https://github.com/oddsgpt/oddsgpt-market-intelligence",
          "https://github.com/oEXU/csgo-server-crasher",
          "https://github.com/PrdTTony/CSGO-Roulette",
          "https://github.com/r-adamski/csgo-jackpot",
          "https://github.com/Sahotallo/Turan-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-Skinbaron-hellcase",
          "https://github.com/samuelcsouza/steam-marketplace-api",
          "https://github.com/SKINSTRACK/CS2-Price-API",
          "https://github.com/snmtriet/CSGO-Casino-Full-Source-Code",
          "https://github.com/SteamRE/homebrew-tools",
          "https://github.com/SteamRE/opensteamworks.org",
          "https://github.com/TheQuack45/CsgoCaseOpenProgram",
          "https://github.com/TLClassless/StratRouletteCSGO",
          "https://github.com/tomasoom/csgoCaseOpening",
          "https://github.com/vitaliy-evsyukov/steamgifts-autobet-bookmarklet",
          "https://github.com/XpravdaX/RouletteCSGO",
          "https://github.com/YuiKasumii/steam_api_unofficial",
          "https://github.com/Zexuz/Steam-Betting",
          "https://github.com/ANK-RULZZ/steam-jackpot-site",
          "https://github.com/asmilen/CsgoDoubleVS",
          "https://github.com/CORNOODOSADAS/CSGOWeed",
          "https://github.com/CSGOApple/csgoapple",
          "https://github.com/CSGOFAST/csgofast-api",
          "https://github.com/Donakall/csgoDoublebot",
          "https://github.com/fedor-selivanov/csgo-fast-roulette",
          "https://github.com/foldageros/csgod",
          "https://github.com/gmod-gambling/gmod-gambling",
          "https://github.com/ierome/CSGOBoss-BackEnd",
          "https://github.com/jamienp1/CSGODOUBLE-BOT-AUTO",
          "https://github.com/JEYONER/CSGOTOXIC",
          "https://github.com/kalrish/csgo-jackpot",
          "https://github.com/krys12345/roulettee",
          "https://github.com/LilDuggiMuffi/CSGODouble-Working-Bot",
          "https://github.com/LyricLy/Steam2Proton",
          "https://github.com/M0NsTeR77/csgo-roulette",
          "https://github.com/ozanhalis/Hi",
          "https://github.com/scoobertus/CSGO-DoubleBot",
          "https://github.com/Tradeal/CSGO-Jackpot-Bot",
          "https://github.com/ValvePython/artifact",
          "https://github.com/Vampire/CSGO-Roulette-Bot",
          "https://github.com/vdemans/csgo-roulette",
          "https://github.com/VocoreVideo/CSGODungeon-",
          "https://github.com/wayz-dev/csgofloat",
          "https://phishdestroy.io/steam_dossier/output_steam_network/raw_data.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/enforcement-source-manifest.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/uk/steam_enforcement_evidence.content.json",
      "export_json_sha256": "1f07933e5db3681da6f102f6176045dae9df4c742a6c2a34b9cb4df73df60e06"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "uk/steam_evidence_archive.html",
      "language": "uk",
      "title": "Ознайомтеся з джерелами — Досьє «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/uk/steam_evidence_archive",
      "source_html_sha256": "ed60c0e1e426bf9139a63027646ec00cec6337b4df9d3e7255dcf77341a5740e",
      "exported_at": "2026-09-29T00:19:47.004Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "steam_evidence_archive.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/uk/steam_evidence_archive.pdf?v=print-20260929-v5",
        "sha256": "a8091e5e99fb387a406634e1f936915db7c5b7375cae2478db3de63eaadd2b1f",
        "bytes": 69450,
        "pages": 4
      },
      "integrity": {
        "signed_object": "steam_evidence_archive.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "steam_evidence_archive.content.json.asc",
        "digest_file": "steam_evidence_archive.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify steam_evidence_archive.content.json.asc steam_evidence_archive.content.json",
          "sha256sum -c steam_evidence_archive.content.json.sha256"
        ]
      },
      "content": {
        "text": "МАТЕРІАЛИ РОЗСЛІДУВАННЯ / ЗБІР ДЖЕРЕЛ 002\nSteam Архів доказів — Документи з сайту «16,319»\n\nКожна претензія. Повернутися до джерела.\n\nЩО ДОКАЗУЄ ЦЕЙ РОЗДІЛ\n\nЦей криміналістичний архів індексує записи першоджерел 16,319 — включаючи документацію спільноти розробників Valve, публічні звернення на GitHub, перевірені скарги на Trustpilot та архівні повідомлення з форумів — із використанням криптографічних хеш-сум та журналів походження. Він надає базу доказів, яку можна перевірити, що демонструє повторювані вразливості платформи, недокументовані випадки припинення підтримки API та постійні скарги споживачів щодо викрадених облікових записів.\n\n← Повернутися до огляду для керівництва\n\nЗнайдіть запис, на якому ґрунтується твердження. Відфільтруйте за джерелом, відкрийте повний текст і перейдіть за оригінальним посиланням. Рядки джерел можуть перетинатися; запис не є підтвердженим випадком.\n\nПовернутися до розслідування ↗\n354TRUSTPILOT / РЯДКИ ДЖЕРЕЛ\n208REDDIT / РЯДКИ ДЖЕРЕЛ\n705GITHUB / РЯДКИ КОДУ\n15,302MASTER CSV / РЯДКИ ДЖЕРЕЛА\n16,319 ЗАПИСИ — РОЗПОДІЛ ЗА ТИПОМ ПЛАТФОРМИ\n\nКатегорія «Провенанс» у Вікі (записи за адресою 7,620 · 46.7%): Дані отримано з «Спільноти розробників Valve» (developer.valvesoftware.com), документації та розділу «Часті запитання» SteamDB, а також вікі-сторінок ігрових спільнот (Liquipedia CS/Dota та Fandom Steam) за допомогою автоматичних знімків WARC та кінцевих точок MediaWiki API у період з серпня 2024 по вересень 2026.. Усі записи 7,620 повністю інтегровані в головний CSV-експорт (TOTAL_VALVE_SCANDALS_MASTER_DB.csv).\n\nВікі\n7,620\nReddit\n5,635\nGitHub\n2,395\nTrustpilot\n393\nВеб\n276\n9,116 у записах 16,319 (55.8%) містяться посилання на Steam / Valve\n\nЦей архів із можливістю пошуку було створено на основі 2026-09-17 з перелічених вище експортних даних. Окремий основний експорт рядків 40,448-, який використовується в інших частинах досьє, має інший обсяг. Див. створити маніфест щодо статистичних даних цього архіву; записи можуть дублюватися і не відображають окремих випадків.\n\nПЛАТФОРМА-ДЖЕРЕЛО\nЗБІР ДЖЕРЕЛ\nSteam / Valve згадки\nЗбіг тексту або репозиторій «Valve»Відсутній / видалений текст\n16,569 рядки джерела\n16,319 окремі записи\n249 дублікати рядків об’єднано\n1 рядок виключено\nПереглянути оригінальні файли ↘\n★TRUSTPILOT2015-10-16#1RATING 1/5\n\nSteam is the biggest PC gaming platform without a doubt. A power which could be abused but Steam for the most part doesn't. Overall a definite download for any moden digital age PC gamer. It mu... See more\n\nMA · 7 source copies\n★TRUSTPILOT2021-06-18#2RATING 1/5\n\nThey scam people for money, dont believe me? Read this Source: Steam Subscribers/User Agreement NO GUARANTEES TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, NEITHER VALVE NOR ITS AFFILIA... See more\n\nWF · 7 source copies\n★TRUSTPILOT2016-10-28#3RATING 1/5\n\nSupport on site is terrible. Refunds not happend yet, despite games not working. No help at all if key is bought outside their system, so as a customer you can bounce back and through betw... See more\n\nPE · 7 source copies\n★TRUSTPILOT2021-09-27#4RATING 1/5\n\nThey are an amazing company!! My boyfriend paid for and downloaded a game without realizing it wasn’t the version he wanted. When he reached out, they gave him a full refund and responded in the same... See more\n\nVH · 7 source copies\n★TRUSTPILOT2026-07-20#5RATING 1/5\n\nI’ve used Steam for years, but lately, their sales have really lost their edge. I was hoping to score some solid discounts, but many games still feel overpriced, even during sales. Plus, the support response times can be frustratingly slow when issues arise.\n\nCR\n★TRUSTPILOT2025-12-10#6RATING 1/5\n\nI new here , but all my firends had great experience with this platform . They can make money\n\nZeinab Nematollahi\n★TRUSTPILOT2025-11-18#7RATING 1/5TEXT UNAVAILABLE\n\nNo text was included in the source record.\n\nEM\n★TRUSTPILOT2025-10-21#8RATING 1/5\n\nusing steam for over a decade and i have no words how good the platform is. some friends recommended it to me back in 2015 when we wanted to play csgo together and since then im loggin on it on a daily basis to check new games\n\nTrustpilot\n★TRUSTPILOT2025-05-09#9RATING 1/5\n\nSupport are never able to help you and only able to redicrect you to public linkBreaking there own TOSNot able to provider a refundNot able to provide a safe place for gamingBase on the game you play you can get scam.\n\nSym Link · 7 source copies\n★TRUSTPILOT2025-05-09#10RATING 1/5TEXT UNAVAILABLE\n\nNo text was included in the source record.\n\nHearnius\n★TRUSTPILOT2024-12-30#11RATING 1/5\n\nThis company allowed a single phishing scammer 76561199443342045 in 100's of its user community chat rooms \"Steam Chat\" the whole week of Winter Sales, 12-23-2024 - 2025 to spam spaceintrader a scam phishing website.Don't support Valve & Steam that support sca…\n\nFR · 7 source copies\n★TRUSTPILOT2024-11-15#12RATING 1/5\n\nVery realiable! Ive never had an issue over the 11 years ive had steam.\n\nJM\nЗбірка та її вихідні файли\n\nЦей архів об’єднує дубльовані записи з 249 та виключає один запис із вхідних даних 16,569, залишаючи 16,319 унікальних записів. Один запис може описувати подію, яка вже висвітлена в іншому записі. Пошук охоплює назви, авторів, назви джерел та відображені уривки; повний збережений текст відкривається разом із кожним записом.\n\nЗавантажити чотири файли з вихідним кодом ↓Кількість файлів та хеші SHA-256 ↗Оригінальний маніфест збірки ↗\n\nПакет містить відновлені експортні дані, кількість рядків яких відповідає кількості рядків у збірці, а також три зафіксовані шляхи до файлів JSON. У вихідній збірці не було зафіксовано хеш-кодів вхідних даних або шляху до головного CSV-файлу; у супровідному маніфесті наведено перелік відновлених файлів та результати порівняння з опублікованим індексом.\n\nTrustpilot · steam_support_reviews.json354 рядки · експорт у форматі JSON\nReddit · reddit_censored_forensics.json208 рядки · експорт у форматі JSON\nGitHub · valve_ignored_bugs.json705 рядки · експорт у форматі JSON; ім’я файлу — це мітка колектора\nМайстер · TOTAL_VALVE_SCANDALS_MASTER_DB.csv15,302 рядки · Експорт у форматі CSV для порівняння\nСудові справи · UNSEALED_EXHIBITS_AND_AML_DOSSIER.mdСправа «Wolfire проти Valve»: оприлюднені електронні листи, показання Геба Ньюелла, жовтень 2019 зізнання щодо боротьби з відмиванням грошей\nОсновні факти · FACTS_AND_CITATIONS_DATABASE.md1,638 окремі перевірені посилання на 35 щодо питань антимонопольного законодавства та безпеки\nАрхів підтримки · support_canned_refusals.html1,505 записи про квитки · 137 збережені знімки екрана · Миттєвий пошук у реальному часі\nПоля записів, відсутній текст та дублювання експортованих даних\n\nДати, рейтинги, категорії та статус публікацій відповідають вихідним експортним даним. Відсутня URL-адреса залишається відсутньою. Позначки «[видалено]» або «[вилучено]» не вказують, хто видалив публікацію та з якої причини. Фільтр Steam / Valve працює за принципом текстового збігу, а не оцінки релевантності.\n\nФункція «Експорт збігів» завантажує записи індексу разом із уривками; функція «Завантажити запис» містить повний текст, що було збережено. Окремий 40,448-головний рядок CSV та 1,690-рядок GitHub у форматі CSV У цій збірці вирішальне значення має обсяг експорту, а не кількість джерел.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam Архів доказів — Документи з сайту «16,319»"
          },
          {
            "level": 2,
            "id": null,
            "text": "ПЛАТФОРМА-ДЖЕРЕЛО"
          },
          {
            "level": 2,
            "id": null,
            "text": "Збірка та її вихідні файли"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/uk/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/uk/",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/TOTAL_VALVE_SCANDALS_MASTER_DB.csv",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive_manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive-inputs.zip",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive-inputs-manifest.json",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/unsealed_legal_and_aml/UNSEALED_EXHIBITS_AND_AML_DOSSIER.md",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/forensic_facts_1000/FACTS_AND_CITATIONS_DATABASE.md",
          "https://phishdestroy.io/steam_dossier/uk/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/github_valve_unpatched_bugs.csv"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/uk/steam_evidence_archive.content.json",
      "export_json_sha256": "057ee360b3d8fa0dd82902dabb1cfaf412bcceb35481dc630e3babfc4684b833"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "uk/support_canned_refusals.html",
      "language": "uk",
      "title": "Steam Архів відмов у наданні підтримки та стандартних відповідей — Досьє «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/uk/support_canned_refusals",
      "source_html_sha256": "d708d6847223b8ccd321f83366186f0134eeba0fa003589e295b3eeb8151429a",
      "exported_at": "2026-09-29T00:19:49.491Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "support_canned_refusals.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/uk/support_canned_refusals.pdf?v=print-20260929-v5",
        "sha256": "24bc3408f48ec9f9ab4db2bd224813e42e3beef1415c16a27525307fd14e8be8",
        "bytes": 66417,
        "pages": 2
      },
      "integrity": {
        "signed_object": "support_canned_refusals.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "support_canned_refusals.content.json.asc",
        "digest_file": "support_canned_refusals.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify support_canned_refusals.content.json.asc support_canned_refusals.content.json",
          "sha256sum -c support_canned_refusals.content.json.sha256"
        ]
      },
      "content": {
        "text": "ЩО ДОКАЗУЄ ЦЕЙ РОЗДІЛ\n\nУ цьому репозиторії містяться збережені оригінальні скріншоти з сайту 137 та перевірені звернення потерпілих з сайту 1,505, в яких детально описано процес автоматизованої обробки запитів до служби підтримки на сайті Valve. Це доводить, що у випадках, коли облікові записи зламують через перенаправлення OpenID або несанкціоноване генерування ключів API, служба підтримки Steam систематично використовує стандартні шаблонні відмови без проведення технічного розслідування. Категорично відмовляючи у відновленні предметів або наданні даних аудиторського сліду, платформа перекладає повну відповідальність за системні недоліки аутентифікації на власників зламаних облікових записів.\n\nУсі скріншоти є знімками, зробленими сторонніми особами. Авторські права та зміст належать відповідним авторам та платформам (користувачам Reddit, авторам спільноти «Steam», рецензентам Trustpilot, авторам публікацій на сайтах X та YouTube). Вони відтворені виключно з метою ідентифікації та висвітлення питань, що становлять суспільний інтерес; жодних прав власності на них не заявляється. Кожен матеріал містить посилання на першоджерело.\n\nFigures reported on the source page\nMeasure\tReported value\tScope\nДокументальні записи\t1505\tПеревірені звернення потерпілих та теми про штрафи\nЗбережені знімки екрана\t137\tЗнімки квитків у високій роздільній здатності, збережені локально\nКоефіцієнт відновлення\t0.0%\tСкасування рішень у справі «API» — викрадення літаків\nДублювання шаблонів\t100%\tПовторне використання дослівних сценаріїв різними співробітниками (Ілля, Роджер, Маверік)\nСудово-медичні докази: три основні підстави для відмови у наданні допомоги\nПІЛАР 01 · ВСТУПДодаток R —014\nThe Roger Admission: Підтверджено атаку «людина посередині» (MitM) на API\n\nУ відповіді на звернення №1cp582i співробітник служби підтримки Steam на ім’я «Роджер» письмово визнає, що зловмисники скасовують законні угоди через сайт API і замінюють їх на клоновані боти за мілісекунди, але відмовляється відновити предмети та радить потерпілому звернутися до «місцевого комп’ютерного фахівця».\n\nПереглянути письмове підтвердження зарахування ↗\nПІЛАР 02 · ЕСКАЛАЦІЯДодаток R —012\n7-Денна торгівля: утримання позиції, відсутність дій\n\nОдна з жертв надала SteamID64 акаунтів хакера під час періоду блокування торгівлі в рамках акції «7-». Співробітники служби підтримки «Артем» та «Ілля» відмовилися заблокувати вкрадені предмети, посилаючись на їхню рідкість, і закрили запит, використавши автоматичний шаблон.\n\nПереглянути виписку з даних про персонал ↗\nПІЛАР 03 · ПОЛІТИКАДодаток R —002\nДефіцит на ринку у зв’язку з правами власності\n\nВ офіційній Політиці повернення предметів Valve чітко зазначено, що предмети не підлягають поверненню, оскільки їхнє повернення «зменшило б їхню рідкість та спричинило б інфляцію в економіці, що призвело б до зниження вартості предметів на Спільнотному ринку».\n\nПереглянути знімок екрана з умовами політики ↗\nІсторичне походження · 22 Березень 2018 на 2026\nДодаток H —003 · 8-: Площа атаки без виправлень за рік\nНайдавніший зафіксований випадок заміщення товарів (22 березня 2018)\n\nРівно за тиждень до того, як компанія «Valve» запровадила суперечливе обмеження на денну торгівлю предметами в грі «Counter-Strike» — так зване «7-», — торговельна спільнота виявила перші реальні випадки Steam Експлойт, пов’язаний з перенаправленням у веб-API. Зловмисники перехопили веб-сесії, щоб згенерувати несанкціонований ключ API на steamcommunity.com/dev/apikey без підтвердження з боку мобільного додатка 2FA, що дозволяє ботам скасовувати та обмінювати угоди в режимі реального часу.\n\nПопередження від громадської організації «2018» за березень: «Шахраї можуть автоматично виявити цю пропозицію обміну й відхилити її у вашому акаунті, оскільки у них є ваш ключ Steam API. Тепер шахрайський бот надішле вам пропозицію обміну тими самими скінами... і ви навіть не помітите різниці!»\nІсторичний маршрут\n22 Березень 2018: Перший задокументований випадок заміни двигуна «API»\n2019: Підтримка стандартизує відбивання «шкідливого програмного забезпечення»\n2020: Посилено захист скрипта «Закрити запит на допомогу»\n2022–2026: Автоматизація фішингових атак з використанням BitB та QR-кодів\nВідкрити оригінальну гілку на Reddit «2018» ↗\nPrimary sources\n\n137 gallery cards refer to 78 distinct primary URLs. Images and repeated exhibit captions are omitted from this reading edition.\n\nFull visual archive and original captures",
        "headings": [
          {
            "level": 2,
            "id": null,
            "text": "Figures reported on the source page"
          },
          {
            "level": 2,
            "id": null,
            "text": "Судово-медичні докази: три основні підстави для відмови у наданні допомоги"
          },
          {
            "level": 3,
            "id": null,
            "text": "The Roger Admission: Підтверджено атаку «людина посередині» (MitM) на API"
          },
          {
            "level": 3,
            "id": null,
            "text": "7-Денна торгівля: утримання позиції, відсутність дій"
          },
          {
            "level": 3,
            "id": null,
            "text": "Дефіцит на ринку у зв’язку з правами власності"
          },
          {
            "level": 3,
            "id": null,
            "text": "Найдавніший зафіксований випадок заміщення товарів (22 березня 2018)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Primary sources"
          }
        ],
        "links": [
          "https://www.reddit.com/r/csgo/comments/1cp582i/i_got_api_scammed_what_do_i_do_now/",
          "https://www.reddit.com/r/DotA2/comments/1e5ovy4/my_account_was_hacked_and_steam_support_refuse/",
          "https://www.reddit.com/r/Steam/comments/3b2abd/steam_will_no_longer_restore_scammed_items_item/",
          "https://www.reddit.com/r/GlobalOffensiveTrade/comments/863tk1/psa_urgent_huge_scam_happening_read_here_how_to",
          "https://phishdestroy.io/steam_dossier/uk/support_canned_refusals#gallery-grid"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/uk/support_canned_refusals.content.json",
      "export_json_sha256": "c3ccca794c0379c32b97be3dede6149a0d8e8a6dc7906d24a29f8c7fffd57345"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "uk/valve_scandals_registry.html",
      "language": "uk",
      "title": "Valve Реєстр скандалів — Досьє «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/uk/valve_scandals_registry",
      "source_html_sha256": "cddb3477ad9e502ce73a8288c8950a2f4f052fe0bcd1a0973c61ffd80eb4f697",
      "exported_at": "2026-09-29T00:19:49.812Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "valve_scandals_registry.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/uk/valve_scandals_registry.pdf?v=print-20260929-v5",
        "sha256": "ac9920d4f3f634c571b43e75c0b259dfafcd2dd4149c14706b295358112dd18b",
        "bytes": 70096,
        "pages": 6
      },
      "integrity": {
        "signed_object": "valve_scandals_registry.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "valve_scandals_registry.content.json.asc",
        "digest_file": "valve_scandals_registry.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify valve_scandals_registry.content.json.asc valve_scandals_registry.content.json",
          "sha256sum -c valve_scandals_registry.content.json.sha256"
        ]
      },
      "content": {
        "text": "Архів головних скандалів\nValve Головний реєстр скандалів — 160 Інциденти за джерелами\nДЖЕРЕЛО (СИРОВІ ДАНІ): 11,768\n\nПовідомлено. Джерело підтверджено. Справа залишається відкритою.\n\nЩО ДОКАЗУЄ ЦЕЙ РОЗДІЛ\n\nЦей головний реєстр об’єднує первинні записи, що пройшли незалежну перевірку на сайті 160, у яких детально описано постійні недоліки платформи, видалені повідомлення від спільноти та невирішені випадки неналежного обслуговування споживачів у всій екосистемі Valve. Він охоплює перевірені заяви про спори на Trustpilot, архівні запити щодо проблем безпеки на GitHub та матеріали регуляторних проваджень і свідчить про систематичні системні збої у процесі відновлення облікових записів та вирішення спорів із клієнтами.\n\n← Повернутися до огляду для керівництва\n\n160 зібрані записи: операції з технічної підтримки, оцінені користувачами, теми, які перестали бути видимими, повідомлення про недоліки платформи, які були зареєстровані та залишені без уваги, а також інциденти, за які Valve вже довелося відповідати. Ніщо з цього не є нашою оцінкою — кожен рядок містить посилання на оригінальне джерело. Відкрийте будь-який із них і прочитайте самі.\n\nДжерела записів\n11,768\nУ всіх категоріях\nНедоліки платформи\n3,372\nПовідомлення користувачів про недоліки платформи\nТеми, що піддалися цензурі\n109\nДописи на Reddit, видалені модератором\nСкарги щодо технічної підтримки\n471\nПеревірені скарги на Trustpilot\nМожливість забезпечення виконання\nБлокування доменів авторизаційних серверів\n\nБлокування хостів автентифікації OpenID на рівні домену технічно нескладно реалізувати: щойно ресурс буде виключений із перенаправлення на вхід через Steam, сторонні домени, які виступають проксі-серверами автентифікації для цього самого ресурсу, можна відфільтрувати за допомогою того самого набору правил. Детальний аналіз можливості реалізації наведено в основному досьє.\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\nПереглянути інформацію щодо можливості забезпечення дотримання вимог у досьє →\nКатегорія: Скарги до служби підтримки Trustpilot (відфільтровані негативні звернення, що потребують ескалації)176 відповідні записи джерела · дублікати приховані\nConsumer Complaint2026-07-20\nAuthor: C***\n\nI’ve used Steam for years, but lately, their sales have really lost their edge. I was hoping to score some solid discounts, but many games still feel overpriced, even during sales. Plus, the support response times can be frustratingly slow when issues arise.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2026-07-20\nConsumer Complaint2025-05-09\nAuthor: S*** L***\n\nSupport are never able to help you and only able to redicrect you to public linkBreaking there own TOSNot able to provider a refundNot able to provide a safe place for gamingBase on the game you play you can get scam.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2025-05-09\nConsumer Complaint2024-12-30\nAuthor: F***\n\nThis company allowed a single phishing scammer 7656…2045 in 100's of its user community chat rooms \"Steam Chat\" the whole week of Winter Sales, 12-23-2024 - 2025 to spam spaceintrader a scam phishing website.Don't support Valve & Steam that support scams. Don't give your log in credentials to account hijacking scammers. This company also allows engagements of commercial advertising / spam for gambling in violation of its own Rules and Guidelines / Online Conduct. 7656…5023 proof - groups/deskinsfans key drop advertising, thanks TannerfromKD and Valve!*\"The Consumer Review Fairness Act (CRFA) protects people’s ability to share their honest opinions about a business’s products, services, or conduct, in any forum, including social media. The law protects a broad variety of honest consumer assessments, including online reviews, social media posts, uploaded photos, videos, etc. And it doesn’t just cover product reviews. It also applies to consumer evaluations of a company\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2024-12-30\nConsumer Complaint2024-07-31\nAuthor: A***\n\nhorrible company.randomly you get \"This account may have been accessed by someone else.\"this happened to me 3 times.the 3rd time they wanted a cd key.a spent useless cd key that nobody has any reason to keep laying around.i gave them the paypal bill for my first purchase back in 2015.i gave them a bill for my first phone number ever on the account.i still got the same email attached to the account.this company is literally a scam. nothing but a scam.they randomly claim you been accessed somewhere else and then require you to give them information no reasonable person would ever have, if not your done and have to rebuy everything.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2024-07-31\nConsumer Complaint2023-12-09\nAuthor: K***\n\nHad 288 euros in steam wallet, someone hacked my account even with two step verification, write a steam support for help but only answer was if something is spent in community market they can’t help.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2023-12-09\nConsumer Complaint2023-09-26\nAuthor: J***\n\nI was banned for saying \"Who let grandma on the PC\"and another for simply calling someone ignorant.Power tripping mods, devs who don't care, steam doesn't care. Yet allows racism/trolling/etc Fk steam, its a joke now.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2023-09-26\nConsumer Complaint2022-08-31\nAuthor: Anonymous\n\nSteam community is plain bad for a various reasons:1. Steam forums are a big mess, for example they allow users to post in any language and as result you get jumbled mess with posts in foreign languages together with English language posts. For example, If you check CS GO forums, you'll see half of posts are in Russian and half in English. I don't understand why such a big and international company would leave their forums so unorganized like that. All other normal companies have English only language allowed which is an international language and sometimes subforums for other languages like German, French and etc... so if French people want to post in French they go specifically in that sub-forum. But no, Steam doesn't care about this. Their forums is a one big mess.2. Moderation is biased and joke. I don't understand why such a big company like Steam can't afford to hire people for moderation and pay them. Instead they just recruit random people for moderation who do it for free and\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2022-08-31\nConsumer Complaint2022-05-28\nAuthor: J***\n\nThe login code never arrives. I hate Steam.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2022-05-28\nConsumer Complaint2021-11-08\nAuthor: N***\n\nThe service is terrible, I only signed up because I really like the game I wanted, but the rest is terrible, I hope to get something better soon.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-11-08\nConsumer Complaint2021-06-18\nAuthor: W***\n\nThey scam people for money, dont believe me? Read thisSource: Steam Subscribers/User Agreement NO GUARANTEESTO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, NEITHER VALVE NOR ITS AFFILIATES GUARANTEE CONTINUOUS, ERROR-FREE, VIRUS-FREE OR SECURE OPERATION AND ACCESS TO STEAM, THE CONTENT AND SERVICES, YOUR ACCOUNT AND/OR YOUR SUBSCRIPTION(S) OR ANY INFORMATION AVAILABLE IN CONNECTION THEREWITH.In short: You got a virus or your data leaked because of our software? Whoopsies we dont care, that isnt even legal or the last of their scammy stuff...\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-06-18\nConsumer Complaint2021-05-14\nAuthor: B***\n\nThe support is one of the worst I've ever seen.Useless support team.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-05-14\nConsumer Complaint2020-04-02\nAuthor: J***\n\nSteamcommunity has 15% fees, 15!!!!\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2020-04-02\nConsumer Complaint2020-03-27\nAuthor: H***\n\nWhat can I say? the support is one of the worst I've ever seen maybe the FUNCOM is much worse. If you tell the true on the steam forum you just got a BAN even if what you said did not violated the rules of the forum.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2020-03-27\nConsumer Complaint2018-03-16\nAuthor: B***\n\ndon't sign up will stick on your computer will kill your pc power you can't remove it from your pc even you deleted it will stay woking in the system\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2018-03-16\nConsumer Complaint2016-12-27\nAuthor: J***\n\nIn bloddy hate their page it's tiresome, it's in no way intuitive. I tried reaching out for support, but that is a maze.I'm simply trying to log in and redeem a key of a product I already bought, their search function is a joke. I f*u*c*k*i*n*g hate them. The layout is not like the how to video from the dealer, this can be done much simpler. I don't frigin care aboutn what other titles you have in store or what genre, I just want to redeem my key and install.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-12-27\nConsumer Complaint2016-10-28\nAuthor: P***\n\nSupport on site is terrible.Refunds not happend yet, despite games not working.No help at all if key is bought outside their system, so as a customer you can bounce back and through between bad support systems?? I wait for some other companies to compete in this market, for this can't be the best we as customers can expect.And do put an email up to find, instead of this stuppid website where you spend so long time trying to find a solution on, instead of a simple mail. Often the problem is not there, or if it's there just saying no help here???I need a response\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-10-28\nConsumer Complaint2016-06-26\nAuthor: V*** W***\n\nUseless support as always!\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-06-26\nConsumer Complaint2014-07-01\nAuthor: J***\n\nexpensive, and support team not willing to cooperate\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2014-07-01\nConsumer Complaint2014-04-15\nAuthor: B***\n\nWhen you pay for a program, you expect it too work. cant not buy or anything and have written to valve. but there is not a being done a damn thing abut it..\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2014-04-15\nConsumer Complaint2026-09-03\nAuthor: M***\n\nWorst platform ever wont give me a refund even though a game is unplayable because of bugs I won't ever be using the crap platform again I hope the platform breaks down for good piece fo crao\n\nTarget Domain: steamcommunity.com / steampowered.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2026-09-03\n\nВідповідних записів не знайдено\n\nСпробуйте змінити параметри поточного запиту або перейти на вкладку іншої категорії.\n\n1 / 9",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Valve Головний реєстр скандалів — 160 Інциденти за джерелами"
          },
          {
            "level": 2,
            "id": null,
            "text": "Блокування доменів авторизаційних серверів"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: C***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: S*** L***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: F***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: A***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: K***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: Anonymous"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: N***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: W***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: H***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: P***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: V*** W***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: M***"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/uk/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/uk/#proxy-bypass-explainer",
          "https://phishdestroy.io/steam_dossier/uk/#autoban-feasibility-section",
          "https://www.trustpilot.com/review/steamcommunity.com"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/uk/valve_scandals_registry.content.json",
      "export_json_sha256": "738757163cc69d45147545408c7e3a419961b556a11a78c9820f39d621f244eb"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "uk/output_steam_network/index.html",
      "language": "uk",
      "title": "Архітектура, а не експлойт: мережа «Automation Network» — досьє «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/uk/output_steam_network/index",
      "source_html_sha256": "5fad8114f9fc38630a9e063a1518d296f45ef01b5f79c40dd23824f59b6aa2f3",
      "exported_at": "2026-09-29T00:19:50.690Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__index.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/uk/output_steam_network__index.pdf?v=print-20260929-v5",
        "sha256": "1a836cf05eed3a48e04e193d041885bd72964696edf77a1e0e824067165be574",
        "bytes": 72407,
        "pages": 3
      },
      "integrity": {
        "signed_object": "output_steam_network__index.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__index.content.json.asc",
        "digest_file": "output_steam_network__index.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__index.content.json.asc output_steam_network__index.content.json",
          "sha256sum -c output_steam_network__index.content.json.sha256"
        ]
      },
      "content": {
        "text": "Додаток VII · Аналіз технічної архітектури\nSteam Архітектура мережі — відповідність протоколам та аналіз екосистеми\n\nАвтоматизація — це архітектура компанії «Valve». Це не експлойт.\n\nЩО ДОКАЗУЄ ЦЕЙ РОЗДІЛ\n\nЦей модуль відображає технічну топологію репозиторіїв розробників 252, профілів 3,320 GitHub та пар учасників 4,214, що лежать в основі екосистеми автоматизації Steam. Він доводить, що сторонні засоби автоматизації спираються на офіційний протокол Connection Manager Valve, схеми Protobuf та веб-API без експлойт-коду. Завдяки розробці алгоритмічних токенів підтвердження Steam Guard та стягуванню мінімальних комісій за транзакції, що не перевищують 66.7%,, Valve виступає як цілеспрямований архітектор та основний комерційний бенефіціар автоматизованих операцій екосистеми.\n\n← Повернутися до огляду для керівництва\n\nКоли компанія «Valve» звертається до регуляторних органів, платіжних систем або жертв шахрайства, вона пояснює крадіжки скінів та маніпуляції на ринку «несанкціонованими зловживаннями з боку третіх осіб» та «незаконною автоматизацією зловмисників». Технічна реальність цієї мережі репозиторіїв 252-свідчить про прямо протилежне: Кожен фреймворк автоматизації, торговий бот та флот для фармінгу функціонують суворо в межах офіційних визначень протоколів, веб-API та механізмів автентифікації, розроблених, задокументованих та комерціалізованих корпорацією «Valve».\n\nВисновок експертизи: «Свідома архітектура» проти «незаконного вторгнення»\n\nПрограмне забезпечення, яке аналізується в цьому модулі, — зокрема SteamKit, node-steam-user, ValvePython/steam, та ArchiSteamFarm — містить нуль вразливостей у програмному забезпеченні, нуль випадків пошкодження пам’яті та нуль експлойтів «нульового дня». Це чисті та надійні реалізації з відкритим кодом пропрієтарного клієнтського протоколу «Connection Manager» (CM) компанії «Valve», Google Protocol Buffers (Protobufs) та веб-API. Компанія «Valve» розробила ці API для підтримки програмного входу, а також створила «Steam Guard», щоб забезпечити підтримку алгоритмічних токенів підтвердження (identity_secret), а також стягує заявлений комісійний збір 15%, який зростає до до 66.7% на користь Valve щодо високошвидкісних карт та товарних розпродажів, які реалізують автоматизовані ботнети.\n\nНапрям «01» · «Protocol Fidelity»\nОфіційні схеми Protobuf\n\nБібліотеки автоматизації не обходять засоби безпеки. Вони серіалізують офіційні повідомлення Protobuf (steammessages_clientserver.proto) через TCP/WebSockets безпосередньо до офіційних кластерів CM сервісу «Valve», точно так само, як це робить клієнт Steam.\n\nPillar 02 · Algorithmic 2FA\nДозвіл на програмну торгівлю\n\nУся багатомільярдна економіка торгівлі шкірою залежить від Valve IEconService API та ключі мобільного аутентифікатора TOTP. Компанія «Valve» спеціально розробила систему «Steam Guard» для забезпечення підтвердження транзакцій між машинами.\n\nНапрям 03 · Комерційний бенефіціар\nТрафік з монетизованих машин: до мінімальної комісії66.7%\n\nValve рекламує комісію у розмірі 15%, але на товарах з великим обсягом торгів, якими торгують автоматизовані боти — колекційні картки, набори та дешеві лоти вартістю від $0.03 до $0.05 — мінімальна комісія Valve у розмірі двох центів ($0.01 Steam + $0.01 видавця) становить 50% на адресу 66.7% на користь Valve (2¢ знято з картки 3¢, у результаті чого продавцю залишилося 1¢). Плюс $5.00 за кожен рахунок ($26.8M лише за сканований автопарк).\n\nМодуль «01» · Дані про репозиторії та протоколи\nГромадська інфраструктура для розробників та репозиторіїв\n\nДетальний криміналістичний каталог репозиторіїв з відкритим кодом 252, на яких базується автоматизація Steam. У ньому простежується, як стандартні інструменти розробки програмного забезпечення реалізують опубліковані на сайті Valve кінцеві точки API без використання експлойтів.\n\n252Репозиторії\n4,554Посилання на ролі\nПереглянути докази з репозиторію →Модуль «02» · Демографія екосистем\nПоказники глобальної інженерної екосистеми\n\nГеографічний та інституційний розподіл інженерів-програмістів з компанії «3,320», які беруть участь у розвитку екосистеми автоматизації «Steam», включаючи їхню приналежність до провідних технологічних компаній-роботодавців.\n\n3,320Інженери\n98,902Пари з'єднань\nПереглянути показники екосистеми →Модуль «03» · Інтерактивний візуальний графік\nІнтерактивний графік протоколу та мережі розробників\n\nКомплексна інтерактивна діаграма мережі Vis.js, що відображає репозиторії, бібліотеки протоколів (SteamKit, Steamworks, ASF) та перехресні зв’язки між учасниками різних проєктів. Візуально демонструє легітимну, взаємопов’язану архітектуру програмного забезпечення з відкритим кодом, на якій базується екосистема автоматизації Steam.\n\nІнтерактивнийVis.js Двигун\nІзоляція кластерівПошук у реальному часі\nВідсутність вразливостейСтандартні API\nВідкрити інтерактивну мережеву діаграму →\nНормативно-правовий контекст (стаття на сайті GDPR 25 та захист прав споживачів):\nВідповідно до принципу «захисту даних ще на етапі проектування та за замовчуванням» (Data Protection by Design and by Default), архітектура платформи, яка дозволяє автоматичне ( API) генерування ключів, скасування торгових операцій без попередження та автоматизовану ліквідацію активів, є архітектурним рішенням оператора платформи. Коли Valve систематично відхиляє вимоги споживачів про відшкодування, стверджуючи, що збитки були спричинені «зовнішніми кібератаками», це приховує той факт, що вектором атаки є власна, навмисно розроблена архітектура веб- API Valve .\n\nІНТЕРАКТИВНИЙ ВИД\n\nПовна інтерактивна візуалізація репозиторію «252-», 3,320-, — граф мережі розробників — доступна за адресою network.html. Зведені показники наведені на Показники BI сторінка.\n\nДосьє «Steam» · Архів технічної архітектури · Публічні джерела · Усі права передані людству.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam Архітектура мережі — відповідність протоколам та аналіз екосистеми"
          },
          {
            "level": 3,
            "id": null,
            "text": "Офіційні схеми Protobuf"
          },
          {
            "level": 3,
            "id": null,
            "text": "Дозвіл на програмну торгівлю"
          },
          {
            "level": 3,
            "id": null,
            "text": "Трафік з монетизованих машин: до мінімальної комісії66.7%"
          },
          {
            "level": 2,
            "id": null,
            "text": "Громадська інфраструктура для розробників та репозиторіїв"
          },
          {
            "level": 2,
            "id": null,
            "text": "Показники глобальної інженерної екосистеми"
          },
          {
            "level": 2,
            "id": null,
            "text": "Інтерактивний графік протоколу та мережі розробників"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/uk/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/uk/output_steam_network/valve_ru_farming_isolated.html",
          "https://phishdestroy.io/steam_dossier/uk/output_steam_network/steam_ecosystem_dashboard.html",
          "https://phishdestroy.io/steam_dossier/uk/output_steam_network/network.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/uk/output_steam_network__index.content.json",
      "export_json_sha256": "1c6c2f6f3002e4de28ef6d6e619ba36db1af9456ab1c073f3fe16dd177ad9ee4"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "uk/output_steam_network/network.html",
      "language": "uk",
      "title": "Інструмент для розробників та перегляду репозиторіїв — Досьє «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/uk/output_steam_network/network",
      "source_html_sha256": "eb79782e5e5c4c48c8eb09b66814d333f0ccca2014e884093bd5eca387271ef1",
      "exported_at": "2026-09-29T00:19:52.212Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__network.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/uk/output_steam_network__network.pdf?v=print-20260929-v5",
        "sha256": "1b4ef90c5578b7837ad676f0474533a0972ba56f9d747302e78cbbb958a68651",
        "bytes": 40358,
        "pages": 1
      },
      "integrity": {
        "signed_object": "output_steam_network__network.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__network.content.json.asc",
        "digest_file": "output_steam_network__network.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__network.content.json.asc output_steam_network__network.content.json",
          "sha256sum -c output_steam_network__network.content.json.sha256"
        ]
      },
      "content": {
        "text": "Інструмент для розробників та перегляду репозиторіїв\n\nЗдійснити пошук вузла. Переглянути зафіксовані зв’язки.\n\nПУБЛІЧНІ АРХІВИ / ЗІБРАНІ ЗВ’ЯЗКИ\nПошук у реальному часі\nШари фільтрів\nВсього розробників3,320\nЗагальна кількість репо-операцій252\nВІДОБРАЖЕНИЙ ГРАФІК / ПІДМНОЖИНА КОЛЕКЦІЇ468 ВУЗЛИ • 1103 ГРАНІ\nВибраний запис профілю\n\n💡 Клацніть на будь-якому вузлі на графіку або введіть текст у поле пошуку, щоб переглянути зібрані зв’язки та шляхи до джерел.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Інструмент для розробників та перегляду репозиторіїв"
          }
        ],
        "links": []
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/uk/output_steam_network__network.content.json",
      "export_json_sha256": "a3adaabbe10027d3ca853b6281389761d309e6b3ec4bc9b1667b10f3794a7087"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "uk/output_steam_network/steam_ecosystem_dashboard.html",
      "language": "uk",
      "title": "Зібрана мережа в цифрах — Досьє «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/uk/output_steam_network/steam_ecosystem_dashboard",
      "source_html_sha256": "f1c95e05eb821cdc843f0d98a3d4a102c96150dbc3d499050cdf6065c27eb5e9",
      "exported_at": "2026-09-29T00:19:53.703Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__steam_ecosystem_dashboard.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/uk/output_steam_network__steam_ecosystem_dashboard.pdf?v=print-20260929-v5",
        "sha256": "1050a4381c07c3548ebf446218f6ae6b22b7b748ed1c2d5f3c3c7dffebc3d304",
        "bytes": 44846,
        "pages": 2
      },
      "integrity": {
        "signed_object": "output_steam_network__steam_ecosystem_dashboard.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__steam_ecosystem_dashboard.content.json.asc",
        "digest_file": "output_steam_network__steam_ecosystem_dashboard.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__steam_ecosystem_dashboard.content.json.asc output_steam_network__steam_ecosystem_dashboard.content.json",
          "sha256sum -c output_steam_network__steam_ecosystem_dashboard.content.json.sha256"
        ]
      },
      "content": {
        "text": "ОГЛЯД СТАТИСТИКИ // ФАЙЛ 02\nSteam Панель моніторингу екосистеми — Мережа в цифрах\n\nМережа в цифрах.\n\nЩО ДОКАЗУЄ ЦЕЙ РОЗДІЛ\n\nЦя інформаційна панель узагальнює структурні дані про розробників 3,320 та репозиторії 252, виявляючи 68 кодові бази, пов’язані з азартними іграми, та міжплатформові мости зв’язку. Емпіричні дані висвітлюють географічні скупчення та перетини між розробниками, що свідчить про те, що інфраструктура азартних ігор із використанням сторонніх скінів функціонує як організована, тісно взаємопов’язана галузь програмного забезпечення, інтегрована з платформою Steam.\n\n← Повернутися до огляду для керівництва\n\nЗведені статистичні дані з бази даних розслідування: географічний розподіл, провідні компанії, сховища азартних ігор та мости активних підключень.\n\nScanned Devs3320\nЗагальна кількість репо-операцій252\nРепо-операції, пов’язані з азартними іграми68\nЗагальна кількість підключень1,426\nСтруктура та галузі автоматизації\nСектор I — Корпорація «Valve» — Основна частина\n\nОфіційні репозиторії та системне програмне забезпечення. Підтверджене робоче середовище співробітників компанії «Valve» — Нефіріна та Джо Людвіга.\n\nСектор II — Механізми авторизації та емулятори протоколів (SteamKit)\n\nБібліотеки мережевих функцій, створені методом зворотного інжинірингу, у співавторстві з Nephyrin із Valve та розробником азартних ігор DoctorMcKay.\n\nСектор III — Клієнти, що займаються фармінгом карток (ArchiSteamFarm)\n\nВикористовуйте емулятори протоколу SteamKit для запуску мільйонів фейкових клієнтів (у режимі очікування) у фоновому режимі з метою фарму колекційних карток.\n\nГеографія розробників\nНімеччина57\nСполучені Штати Америки52\nКанада48\nВелика Британія44\nПольща30\nФранція28\nРосійська Федерація27\nКитай27\nСША (штат Вашингтон)23\nАвстралія19",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam Панель моніторингу екосистеми — Мережа в цифрах"
          },
          {
            "level": 3,
            "id": null,
            "text": "Сектор I — Корпорація «Valve» — Основна частина"
          },
          {
            "level": 3,
            "id": null,
            "text": "Сектор II — Механізми авторизації та емулятори протоколів (SteamKit)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Сектор III — Клієнти, що займаються фармінгом карток (ArchiSteamFarm)"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/uk/#briefing-heading"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/uk/output_steam_network__steam_ecosystem_dashboard.content.json",
      "export_json_sha256": "eed7203566d64e97da1776a389c3efd03f48c2d1f6ac73af883e1ae3b8bb3ba9"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "uk/output_steam_network/valve_ru_farming_isolated.html",
      "language": "uk",
      "title": "Код, учасники та форки — Досьє «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/uk/output_steam_network/valve_ru_farming_isolated",
      "source_html_sha256": "e344175e13ef462d868b0d3742b3c46aa10638dd67f78e5ee10ef35ad3e1a824",
      "exported_at": "2026-09-29T00:19:54.003Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__valve_ru_farming_isolated.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/uk/output_steam_network__valve_ru_farming_isolated.pdf?v=print-20260929-v5",
        "sha256": "41328e6f5aa3d21130c5a5fd8874741c303927bf638e87eedada19b72c95155c",
        "bytes": 47314,
        "pages": 2
      },
      "integrity": {
        "signed_object": "output_steam_network__valve_ru_farming_isolated.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__valve_ru_farming_isolated.content.json.asc",
        "digest_file": "output_steam_network__valve_ru_farming_isolated.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__valve_ru_farming_isolated.content.json.asc output_steam_network__valve_ru_farming_isolated.content.json",
          "sha256sum -c output_steam_network__valve_ru_farming_isolated.content.json.sha256"
        ]
      },
      "content": {
        "text": "ЧАСТИНА II / СЛІДУЙТЕ ЗА ДОКУМЕНТОВАНИМИ ВІДНОСИНАМИ\n\nФорки, внески та програмні залежності є очевидними доказами. Ця точка зору враховує зафіксовані ролі; що стосується зайнятості, обходу систем безпеки та причетності до злочинної діяльності, то для підтвердження цих фактів потрібні додаткові джерела.\n\nВідкрити інтерактивну карту можливостей ↗\nВІДКРИТІ ДЖЕРЕЛА / АУДИТ РОЛІ\nКод. Учасники проекту. Форки.\n1. Nephyrin: форки та внески\n\nУ наданому знімку Nephyrin зазначений як учасник проєкту ValveSoftware/Proton та автор форків проєктів SteamRE/SteamKit і SteamRE/open-steamworks. У даних його профілю вказано компанію «Valve Software». Ці поля слід розглядати окремо.\n\nФорк фіксує копію репозиторію. Цей експорт не містить коміту, що фіксує зміни в коді аутентифікації SteamKit.\nПосилання на репозиторій / перегляд історії\nSteamRE/SteamKit ↗ SteamRE/open-steamworks ↗\n2. Публічні можливості: автоматизація без настільного клієнта\n\nSteamKit та node-steam-user забезпечують програмний доступ до Steam. ArchiSteamFarm описує методи фармінгу карток з використанням декількох облікових записів і вказує SteamKit2 як залежність.\n\nЦе конкретні можливості автоматизації. Виконання без інтерфейсу користувача не означає виключно комерційного використання або обходу системи захисту «Steam Guard». Важливими аспектами є запитувані облікові дані, доступні дії та заходи контролю, що застосовуються платформою.\n\nДжерело: файли README проектів та ArchiSteamFarm.csproj. На карті можливостей наведено посилання на кожну задокументовану залежність.\n3. JoeLudwig: позначка «учасник проекту hl2sdk»\n\nУ знімку перелічено Джо Людвіга як учасника проектів alliedmodders/hl2sdk, ValveSoftware/openvr та ValveSoftware/source-sdk-2013. Це є очевидним зв’язком між проектами. Експортні дані не містять доказів, які б пов’язували конкретну зміну в SDK із крадіжкою або використанням у цілях азартних ігор.\n\nПосилання на репозиторій / перегляд історії\nalliedmodders/hl2sdk ↗ DoctorMcKay/node-steam-user ↗\nЛОГІЧНА СХЕМА // ТРАКТИ\nБлок-схема логіки підключення:\nПРОФІЛЬ ВЗАЄМОВІДНОСІНЬ\nNephyrin / зібрана інформація про профіль\nАвтор: Proton. Розробники форків: SteamKit та open-steamworks.\n▼ Зібрані зв’язки розгалужень\nГРОМАДСЬКА БІБЛІОТЕКА\nSteamRE/SteamKit\nПублічна мережева бібліотека «Steam», яка підтримується організацією SteamRE.\n▼ Заявлена залежність від SteamKit2\nДОКУМЕНТОВАНА АВТОМАТИЗАЦІЯ\nJustArchiNET/ArchiSteamFarm\nДокументи, що стосуються фармінгу карток на декількох облікових записах та залежності від SteamKit2.\nАНАЛІЗ ДОКАЗІВ / КОРОТКИЙ ОГЛЯД ДЖЕРЕЛ\nЗАФІКСОВАНО: окремі позначки для авторів та авторів форків.\nДОКУМЕНТОВАНО: публічні бібліотеки підтримують програмні взаємодії з мережею «Steam».\nВІДКРИТЕ ПИТАННЯ: для встановлення конкретного авторства коду, підтвердження відповідності платформі та визначення відповідальності за зловживання необхідні окремі докази.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Код. Учасники проекту. Форки."
          },
          {
            "level": 2,
            "id": null,
            "text": "1. Nephyrin: форки та внески"
          },
          {
            "level": 2,
            "id": null,
            "text": "2. Публічні можливості: автоматизація без настільного клієнта"
          },
          {
            "level": 2,
            "id": null,
            "text": "3. JoeLudwig: позначка «учасник проекту hl2sdk»"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/uk/investigation_part2.html#automation-map",
          "https://github.com/SteamRE/SteamKit",
          "https://github.com/SteamRE/open-steamworks",
          "https://github.com/alliedmodders/hl2sdk",
          "https://github.com/DoctorMcKay/node-steam-user"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/uk/output_steam_network__valve_ru_farming_isolated.content.json",
      "export_json_sha256": "f01609ddc3b4e61807e9f4571b4bbcaf19d059b748548ef1ba0b4ce478057f90"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ar/card_economy.html",
      "language": "ar",
      "title": "اقتصاد البطاقات — ملف Steam",
      "source_url": "https://phishdestroy.io/steam_dossier/ar/card_economy",
      "source_html_sha256": "f849e8644bc29a61135fd09559659506465e0b24062e17fb91a8b55ebfe88aa9",
      "exported_at": "2026-09-29T00:19:57.089Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "card_economy.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ar/card_economy.pdf?v=print-20260929-v5",
        "sha256": "e8725f3101b6bf18e0f487e4fe2fc94b66421889b4037d19c5ed598a98002999",
        "bytes": 358119,
        "pages": 21
      },
      "integrity": {
        "signed_object": "card_economy.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "card_economy.content.json.asc",
        "digest_file": "card_economy.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify card_economy.content.json.asc card_economy.content.json",
          "sha256sum -c card_economy.content.json.sha256"
        ]
      },
      "content": {
        "text": "الملحق الخامس — اقتصاد البطاقات\nمزرعة البوتات ليست تسربًا في متجر Valve. إنها العميل.\n\nلا يمكن لحساب Steam استلام أي بطاقة تداول واحدة حتى يقوم بالإنفاق $5.00 في المتجر. لا يمكنها جمع عملات من لعبة لا تملكها، ولا يمكنها جمع عملات من لعبة حصلت عليها مجانًا. لذا، قبل أن تنتج آلة جمع العملات الآلية أي شيء على الإطلاق، يجب أن تكون قد دفعت ثمن دخولها — لكل حساب، بالسعر الذي تنشره Valve. ثم تحدد بند الأتمتة الخاص بـ Valve، سطراً سطراً، ما تنتجه تلك المنشأة بالضبط؛ ويحظر ترخيصها كل الطرق التي يمكن من خلالها تحويل البطاقة التي تم جمعها إلى نقود؛ ويأخذ سوقها حصة عندما تُباع البطاقة بأي حال — يُعلن عنها بسعر 15%، لكن الحد الأدنى هو سنتان لكل عملية بيع، وهو ما يمثل معظم السعر في حالة البطاقة التي يُحدد سعرها بالسنتات. يقيس هذا العرض حجم تلك التجارة، وتكلفة المستوى الأعلى في الملف الشخصي بالطقم، وما يفعله مكتب الإنفاذ التابع لـ Valve بنفس البند عندما يكون الحساب مملوكًا لتاجر عادي.\n\nما الذي يجب على المزرعة شراؤه أولاًتكلفة المستوى الواحد في المجموعاتجانبا المكتبمن الذي ينظم اقتصاد البطاقات؟\n$5.00الإنفاق في المتجر قبل أن يتمكن الحساب من استلام أي بطاقة — صفحة الدعم الخاصة بـ Valve\n13,876الألعاب الموجودة في Steam التي تصدر بطاقات تداول، وتضم 99,971 أنواعًا مختلفة من البطاقات\n694,673مجموعات البطاقات الكاملة المتوفرة حاليًا في المخزون لدى 91 روبوت تداول مدرج في البورصة\n1,389,346الحد الأدنى لمخصصات بطاقات الحساب واللعبة التي استهلكتها المخزون بالفعل\n$9.99السعر المتوسط لأي لعبة تستخدم البطاقات — تُباع المجموعة الكاملة منها بسعر متوسط يبلغ $0.74\n97,114أعضاء مجموعة تبادل البطاقات التي تضم قائمة المشرفين فيها موظفًا يحمل الرمز Valve — § 08\n01 — العملية\nما هي المزرعة في الواقع، خطوة بخطوة\n\nتم وصفها استنادًا إلى الوثائق الخاصة بالأداة وصفحات الدعم الخاصة بـ Valve فقط. ولا يوجد في هذا القسم أي استنتاجات، كما لا يوجد فيه أي أمر متنازع عليه من قبل أي من الطرفين.\n\nالخطوة 1\nالشراء\n\nيجب ألا يكون الحساب محدود. تمنع صفحة الدعم الخاصة بـ Valve الحسابات المقيدة من \"المشاركة في سوق Steam\"، من \"تداول Steam العناصر الخاصة بالمجتمع (بطاقات التداول، حزم التعزيز، الأحجار الكريمة، إلخ)\" ومن \"الحصول على Steam من مستويات الملف الشخصي (مقيدة بالمستوى 0) وبطاقات التداول\". البوابة هي المال: \"سيتعين عليك إنفاق ما لا يقل عن $5.00 دولار أمريكي داخل المتجر Steam.\"\n\nالخطوة 2\nشراء الألعاب\n\nلا تُحصل على البطاقات إلا من الألعاب التي تمتلكها. \"يجب أن تكون اللعبة مملوكة لحسابك Steam حتى تكون مؤهلاً للحصول على أي بطاقات تُمنح من خلالها. ولا يُعتبر \"المشاركة العائلية\" ملكية، ولذلك لا تُحتسب.\" كما تم إغلاق المسارات المجانية أيضًا: \"لا يمكن الحصول على بطاقات من الألعاب المدفوعة التي حصلت عليها مجانًا خلال عرض ترويجي\"، و \"لا يمكنك الحصول على بطاقات من الألعاب المجانية دون إنفاق أي أموال فيها.\"\n\nالخطوة 3\nخامل\n\nتقوم الأداة بتسجيل دخول الحساب إلى شبكة Steam دون واجهة مستخدم، \"يقوم بتحليل شاراتك\"، ويقوم بإنشاء قائمة بالألقاب التي يمكن زراعتها ويبدأ \"لعب اللعبة المؤهلة والتحقق بشكل دوري مما إذا كانت اللعبة قد تم استغلالها بالكامل بالفعل.\" وصف المسؤول عن المشروع لهذه الآلية: إنها \"لا يفعل شيئًا سوى إخبار Steam بأننا نلعب لعبة معينة.\"\n\nالخطوة 4\nنفد عدد القطرات\n\nكل عنوان له حد معين. \"تحتوي كل لعبة على عدد محدد من البطاقات التي يمكن الحصول عليها. وبمجرد حصولك على جميع هذه البطاقات (حوالي نصف المجموعة الكاملة)، تصبح اللعبة غير مجدية من حيث جمع الموارد.\" على المزرعة التي ترغب في مواصلة الإنتاج أن تستمر في شراء البطاقات. ويتم تقييد إمدادات البطاقات من خلال عمليات الشراء — وهذا أمر مقصود، ويصب في صالح Valve.\n\nالخطوة 5\nسحب النقد\n\nتُصرف البطاقة عبر أحد الأبواب الثلاثة التالية: بيعها في «سوق المجتمع»، أو مبادلتها، أو سحقها لتحويلها إلى جواهر. وتُعد كل عملية من هذه العمليات معاملة في «سوق الاشتراكات» أو عملية مبادلة، وتنص الفقرة § 3.D على الرسوم التالية: \"Valve يجوز لها فرض رسوم على المعاملات التي تتم في سوق الاشتراكات.\" هذه هي الخطوة التي تجعل الأمر برمته انتهاكًا — انظر 05.\n\nالمصادر، التي تمت قراءتها واقتباسها حرفياً في 2026-09-22: Steam الدعم — حسابات المستخدمين المحدودة ↗ · ArchiSteamFarm الأسئلة الشائعة ↗ · Valve — Steam الأسئلة الشائعة حول بطاقات التداول ↗ · Steam اتفاقية الاشتراك ↗ محفوظ 2026-09-24 ↗. يُستخدم الرمز ArchiSteamFarm في هذه الصفحة بأكملها كأداة قياس، وليس كمتهم؛ حيث تنص الوثائق الخاصة به بوضوح على أن \"ASF غير مرخصة من قبل Valve\".\n\n02 — المقياس\nقبل أن تحقق المزرعة أي ربح، تكون قد دفعت بالفعل Valve\n\nنظرًا لأن الحساب المحدود لا يمكنه الحصول على بطاقة، يجب رفع حالة «محدود» عن كل حساب في المزرعة قبل أن يبدأ في إنتاج أي شيء. يتم الإعلان عن الحد الأدنى، ويتم احتسابه لكل حساب.\n\nحجم المزرعة\tمن أين يأتي هذا الرقم\tالحد الأدنى للإنفاق في المتجر ليصبحوا مؤهلين للحصول على البطاقة\n10 حسابات\tالسقف الذي توصي به منظمة ASF — \"استنادًا إلى المبادئ التوجيهية الداخلية Valve، بالإضافة إلى اقتراحاتنا الخاصة\"\t$50\n100–200 حساب\tالحد الأقصى الفني الوارد في نفس قسم الأسئلة الشائعة: \"يمكنك تشغيل ما يصل إلى 100-200 روبوت باستخدام عنوان IP واحد ومثيل واحد من ASF\"\t$500 – $1,000\n120 حسابًا\tقضية الإنفاذ رقم 3 أدناه — حظر دائم\t$600\n170 حسابًا\tقضية الإنفاذ رقم 2 أدناه — تم حظره بشكل دائم خلال «تخفيضات الشتاء 2017»\t$850\n1,000 حسابات\tقضية الإنفاذ رقم 1 أدناه — حظر التجارة\t$5,000\n5,000 حسابات غير مؤكد\tمقياس المشغل تم الإبلاغ عنها في إطار هذا التحقيق ولم يتم التحقق منها بشكل مستقل — انظر الملاحظة المتعلقة بمصادر المعلومات\t$25,000\n10,000 حسابات غير مؤكد\tمقياس المشغل تم الإبلاغ عنها في إطار هذا التحقيق ولم يتم التحقق منها بشكل مستقل — انظر الملاحظة المتعلقة بمصادر المعلومات\t$50,000\n\nالصفان الأخيران هما الرقمان الوحيدان في هذه الصفحة اللذان يستندان إلى تقرير غير مؤكد بدلاً من وثيقة — وقد تم تمييزهما في الجدول، وشرحهما في ملاحظة بشأن مصادر المعلومات، ولا يعتمد أي شيء آخر هنا عليها. أما العمود الأيمن فيتعلق بالحسابات المستندة إلى عتبة $5.00 دولار أمريكي التي نشرتها Valve، ولا شيء غير ذلك. إنه الأرضية، وليس تقديرًا لتكلفة المزرعة أو لما حققه Valve من أرباح: فهو يستبعد الألعاب، التي يجب أن تكون مملوكة ولا يمكن أن تكون قد تم الحصول عليها مجانًا في إطار عرض ترويجي، كما يستبعد المبلغ الذي يبلغ حوالي 15% الذي يستحوذ عليه «سوق المجتمع» عند بيع البطاقات. ولا يرد في هذه الصفحة أي رقم يتعلق بالإيرادات.\n\nكما حددت Valve سعر مجموعة البطاقات هذه بنفسها. تحدد «الأسئلة الشائعة» الخاصة ببطاقات التداول الخاصة بها معدل التحويل في لعبة «اللعب المجاني» بالدولار الأمريكي:\n\n\"تقدم الألعاب المجانية بطاقات ألعاب بناءً على مشترياتك داخل اللعبة.\" مقابل كل $9 دولار أمريكي يتم إنفاقه (تقريبًا) \"منذ بدء الإصدار التجريبي لبطاقات التداول Steam، ستحصل على بطاقة واحدة.\"\n\n— Valve، Steam الأسئلة الشائعة حول بطاقات التداول ↗ · تم التحقق من نصه حرفيًا 2026-09-22\n\nبطاقة التداول ليست هدية تسبب خسارة مالية للمنصة. إنها شيء تبيعه Valve، بالسعر الذي تنشره Valve — ثم تفرض رسومًا مرة أخرى عند إعادة بيعها. ولهذا السبب، فإن الوصف الصحيح لمزرعة البطاقات ليس طفيلي. إنه مشتري بالجملة.\n\nما هو الحجم الفعلي للشيء الذي يتم شراؤه\n\nكل ما يلي من هنا وحتى نهاية هذا القسم هو بيانات تم قياسها، وليس مجرد أرقام مُبلغ عنها. إحصاء البطاقات مستمد من Steam، وهي قائمة أسعار الشارات التي نشرتها «Card Exchange»؛ أما أسعار الألعاب نفسها فهي مستمدة من واجهة برمجة التطبيقات (API) الخاصة بمتجر Valve؛ أما مخزون الروبوتات فهو مستمد من دليل عام للروبوتات يمكن لأي شخص الوصول إليه. تم قراءة هذه المصادر الثلاثة جميعها على 2026-09-22، وترد العمليات الحسابية بالكامل في القسم 08.\n\n13,876الألعاب التي تُصدر بطاقات\n99,971أنواع البطاقات المختلفة\n5 · 6 · 15عدد البطاقات في كل مجموعة: الحد الأدنى، الوسيط، الحد الأقصى\n$0.74متوسط سعر المجموعة الجاهزة\n$23,586.57قطعة واحدة من كل مجموعة معروضة في السوق\nما حجم هذه المجموعة؟\n\n13,876 لعبة من البطاقات الموجودة في المجموعة. Valve توزع حوالي نصفها على حساب واحد.\n\n0\n1,250\n2,500\n3,750\n5,000\n5\n6\n7\n8\n9\n10\n11\n12\n13\n14\n15\nتكلفة الترخيص\n\nالسعر المعلن لنفس الألعاب في متجر Steam، بالدولار الأمريكي.\n\n0\n1,000\n2,000\n3,000\n4,000\n<$1\n$1-3\n$3-5\n$5-10\n$10-20\n$20-40\n$40+\nما الذي تعرضه المجموعة النهائية\n\nالسعر السوقي للمجموعة الكاملة من الألعاب نفسها.\n\n0\n1,500\n3,000\n4,500\n6,000\n<$0.50\n$0.50-1\n$1-2\n$2-5\n$5-10\n$10+\n\nقارن بين الرسمين البيانيين الثاني والثالث، وستتضح لك صورة التوزيع دون الحاجة إلى إجراء أي حسابات: فالألعاب تتجمع في نطاق العشرات من الدولارات، بينما تتجمع المجموعات التي تنتجها تحت دولار واحد. وكلاهما يمثلان إحصاءات لنفس الألعاب 13,876، على نفس وحدة المحور، لذا فإن المقارنة تتم بين ارتفاعين وليس بين مقياسين.\n\nهذا هو جانب العرض. أما جانب الطلب فهو الجزء الذي لا يحتاج Valve إلى الإعلان عنه، لأنه متاح للجمهور بالفعل: فهناك دليل واحد مفتوح يضم روبوتات تبادل البطاقات، ويضم يوجد حالياً في المخزون 91 روبوتًا تحتوي على مجموعات كاملة من طراز 694,673. لا حاجة لتسجيل الدخول، ولا استخراج بيانات من منصة بيع، ولا بيانات خاصة — الرقم المخزون مطبوع على الصفحة بجوار اسم كل روبوت.\n\nاجعل هذا السهم هو الوحدة الوحيدة التي تهمنا هنا. قاعدة Valve الخاصة: \"ستوزع معظم الألعاب عددًا من البطاقات يعادل حوالي نصف عدد البطاقات الموجودة في مجموعة بطاقات تلك اللعبة… ستحتاج إلى جمع النصف الآخر من المجموعة من أعضاء المجتمع الآخرين.\" لا يمكن لحساب واحد أن يُنهي مجموعة ما عن طريق اللعب. بل يجب أن يكون هناك حسابان على الأقل، كل منهما يمتلك تلك اللعبة، ويستهلك كل منهما حصته المسموح بها من «الدروب» التي تُمنح مرة واحدة في كل لعبة. ولا تتجدد حصص «الدروب».\n\n694,673مجموعات متوفرة في المخزون، 91 روبوتًا عامًا\n3,473,365البطاقات، بحد أدنى 5 بطاقات\n1,389,346الحد الأدنى لمخصصات السحب المستهلكة\n2,602الحسابات التي تمتلك لعبة واحدة فقط، وأكبر عدد من الروبوتات\nأين توجد مجموعات 694,673\n\nأكبر اثني عشر من بين 91 روبوتًا متخصصًا في بطاقات الألعاب مدرجًا في البورصة، من حيث عدد المجموعات الكاملة المتوفرة في المخزون. وتمتلك أكبر عشرة روبوتات منها 248,115 مجموعة — أي 35.7% من كل ما هو موجود على اللوحة.\n\n0\n11,250\n22,500\n33,750\n45,000\nCard Supply #4 (High)\nN!vq's Leveling (High)\nAlice [BOT] LEVEL-UP RARE SETS\nN!vq's Leveling (Low)\nDisco Lite Level Up\nN!vq's Leveling (Mid)\nbaty131store.net | Level Up\nKitten - Supreme\nArashirn | Level Up\nSH (Junior) Level Up\nDuobot.com - Overstock\nlvlupbot.com - godlike\n\nكل واحدة من تلك المخصصات البالغ عددها 1.39 مليون كانت تابعة لحساب يمتلك اللعبة، وتجاوزت عتبة $5.00، ولن تتمكن أبدًا من إنتاج تلك المخصصات مرة أخرى. وهذا هو المخزون غير المباع على 91 روبوتًا. وهذا ليس مقياسًا للسوق؛ بل هو مقياس لما يتبقى بعد السوق.\n\nالرقم الأخير يمثل توزيعًا تصنيفيًّا، وليس إحصاءً لعدد الأشخاص. يذكر أحد الروبوتات 14,310 مجموعات مستمدة من 11 لعبة فقط، لذا فإن إحدى هذه الألعاب على الأقل ممثلة بـ 1,301 مجموعة، وهو ما يعادل على الأقل 2,602 حسابات مختلفة اشترت كل منها تلك اللعبة. وهذا هو أقل رقم تسمح به الحسابات، وهو يتعلق بروبوت واحد من أصل واحد وتسعين.\n\nما الذي تقوله هذه الأرضية وما الذي لا تقوله\n\nتقوم هذه الروبوتات بشراء البطاقات من اللاعبين العاديين وكذلك من «المزارع» — وتشكل أسعار الشراء التي تنشرها هذه الروبوتات جوهر هذا الدليل. وبالتالي، فإن الـ 1.39 مليون حصة ليست إحصاءً للحسابات المملوكة للمزارع. وهي عبارة عن حصص من العناصر التي تُمنح مرة واحدة لكل حساب ومرة واحدة لكل لعبة، وقد تم إنفاقها في مكان ما على Steam، ثم انتهى بها المطاف، دون بيع، في المخزون التجاري. وسواء كان الحساب وراء كل منها حسابًا مخصصًا لجمع العملات (فارم) أو حسابًا لمراهق يسعى لإكمال صفحة الشارات، فإن ذلك لا يغير ما جمعته Valve: فتح $5.00، ورخصة اللعبة، وحصة من السوق على كل عملية بيع — ليس 15%، بل 15% أو الحد الأدنى لكل من السنتين، أيهما أكبر، وهو المبلغ الأكبر بكثير على البطاقة التي يُحدد سعرها بالسنتات. الحساب موجود في جدول الرسوم أدناه. هذا هو الهدف من هذه الصفحة، وهي ليست شكوى ضد المزارعين: فالسلوك نفسه الذي تفرض Valve رسومًا عليه هو السلوك الذي تستشهد به، حرفياً، عندما تحظر شخصاً ما بشكل دائم بسبب «الاستخدام التجاري».\n\nويُعتبر هذا الرقم أيضًا حدًا أدنى بمعنى آخر؛ فهو لا يشمل سوى الأسهم التي المعروضة للبيع ولم تُباع اليوم بشأن الروبوتات التي اختيار الظهور في دليل عام. تم بيع كل شيء بالفعل، وكل شيء محفوظ بشكل خاص، ويتم استبعاد كل بوت خارج الدليل.\n\nوالزراعة لا تغطي تكاليفها عند الأسعار التي يحددها Valve\n\nالاعتراض الواضح هو أن المزرعة تشتري ألعابًا رخيصة لإنتاج بطاقات باهظة الثمن. لكن واجهة برمجة تطبيقات المتجر الخاصة بـ Steam تشير إلى عكس ذلك. من بين 13,876 لعبة تحتوي على بطاقات، تم تحديد الأسعار لـ 13,713؛ 12,918 هي عناوين مدفوعة الثمن يبلغ متوسط سعرها المعلن $9.99. يُباع متوسط سعر المجموعة الجاهزة بمبلغ $0.74. يلزم ترخيصان لكل مجموعة. لذا، يبلغ متوسط تكلفة المجموعة تقريبًا $19.98 من تراخيص الألعاب الخاصة بالإنتاج والعائدات $0.74.\n\nتم القياس عند 2026-09-22\tالقيمة\tما الذي ينص عليه\nمتوسط السعر المعلن، لعبة تعتمد على البطاقات\t$9.99\tالترخيص هو الجزء الأغلى من الصفقة، وليس البطاقة\nالألعاب التي يبلغ سعرها $4.99 أو أقل\t3,665 (28.4%)\tحتى الذيل الرخيص أغلى من المجموعة التي ينتجها\nأرخص لعبة بطاقات متوفرة في المتجر\t$0.99\tترخيصان، $1.98، لمجموعة تُباع عادةً بسعر أقل من $1.30\nالألعاب التي يُباع طقمها بسعر أعلى من سعر اللعبة نفسها\t323 من 12,918 (2.5%)\tتوجد عمليات المضاربة على بطاقات الألعاب مقابل الأسعار المعلنة لـ Steam في لعبة واحدة من كل 40 لعبة\nالألعاب المجانية في الإحصاء\t795\tكما أن Valve يحدد سعر كل عملية توزيع له بـ $9 من الإنفاق داخل اللعبة\n\nوهذا يحسم المسألة الاقتصادية لصالح Valve وضد الرواية المعتادة. وبالأسعار التي يفرضها Valve نفسه، تعد «زراعة البطاقات» نشاطًا خاسرًا لا ينجح إلا في حالة الحصول على التراخيص بسعر أقل من السعر المحدد في قائمة Steam — الحزم، والتسعير الإقليمي، وإعادة البيع الرئيسية. البطاقات هي مجرد بقايا. عملية الشراء هي الحدث. وقد تمت عملية الشراء في Steam.\n\nما الذي تدعمه المزرعة فعليًّا\n\nإذا جمعنا القطع معًا، فإن المزرعة تتوقف عن الظهور كشيء Valve تتسامح معه، وتبدأ في الظهور كشيء Valve تحتاجه. كل مدخل توفره المزرعة هو ناتج Valve يُبلغ عنه أو يُصدر فاتورة به. تابع حساب روبوت واحد إلى الخارج:\n\nحساب واحد تم إنشاؤه بشكل مصطنع\"عميل بالجملة\"، وليس تسريبًا\nمبيعات الألعاب\n\nتشتري الألعاب التي تجمع منها العناصر — بدءًا من ألعاب الورق التي تحمل الرمز 13,876 وصولًا إلى الألعاب الرديئة التي تحمل الرمز $0.50 — لأن البطاقات لا تُحصل عليها إلا من الألعاب المملوكة.\n\n\"عبر الإنترنت\" ووقت اللعب\n\nتجعلهم يتركون اللعبة لإسقاط البطاقات، مما يساهم في إثراء أرقام «عدد اللاعبين المتزامنين» و«عدد ساعات اللعب» التي يُشير إليها Valve على أنها مؤشرات تفاعل — وهي الإحصائية ذاتها التي يصفها § 4.C بـ«تزوير وقت اللعب».\n\nالتسجيلات\n\nيجب تجاوز بوابة الحساب المحدود $5.00 قبل أن يتمكن الحساب من استلام البطاقة — حيث يُسجل كل حساب Valve عملية إنفاق في متجر حقيقي.\n\nأموال المحفظة والرسوم\n\nكل بطاقة تبيعها تمر عبر «الماركت»، حيث تصل الرسوم إلى 66.7% للبطاقات ذات القيمة المنخفضة، وتبقى العائدات مجمدة في محفظة Steam.\n\nSteam-المستوى العلاقات العامة\n\nإن عروض الشارات والمستويات Valve موجودة فقط لأن المجموعات قد صُنعت — وقمة هذا السلم تسيطر عليها الروبوتات (انظر الفقرة 03).\n\nقم بإزالة المزرعة، وستنخفض جميع الأرقام المذكورة أعلاه — بيعت اللعبة بعدد أقل من النسخ، وكان عدد المستخدمين «عبر الإنترنت» أقل، ولم يتم تسجيل الحساب أبدًا، ولم يتم تحصيل الرسوم أبدًا، ولم يتم الوصول إلى المستوى المطلوب أبدًا. ولهذا السبب تتعايش القاعدة التي تحظر الأتمتة مع وجود ملايين الحسابات الآلية: فالحظر هو الخيار، والنشاط هو مصدر الإيرادات.\n\nوالسحب النقدي بحد ذاته يمثل استنزافًا للقيمة Valve ضرائب مرتين\n\nالبطاقة ليست نهاية الحلقة. تتيح آليات Valve الخاصة سحق البطاقة لتصبح الأحجار الكريمة، ويجب إنفاق الأحجار الكريمة لصنع حزم التعزيز — ثلاث بطاقات أخرى — تُباع أو تُسحق مرة أخرى. كل خطوة تمثل معاملة في «السوق» أو عملية تحويل، وتخضع كل منها للضريبة. ويتحدد اتجاه تلك الحلقة بناءً على الحد الأدنى للرسوم المحدد أدناه، ولا تحتاج إلى نموذج خارجي: فكل بطاقة تُباع داخلها تتنازل عن سنتان على الأقل، في البطاقات التي يتم تداولها مقابل ثلاثة إلى خمسة، لذا فإن كل دورة للكرنك تُدر عائدًا أقل مما تم استثماره فيها. وتؤدي هذه الحلقة إلى تدمير القيمة الافتراضية وتفرض إجراء معاملات جديدة خاضعة للرسوم لتعويضها. لم يُذكر هنا أي رقم يحدد حجم تلك الخسارة — يعتمد العائد لكل مجموعة على أسعار الأحجار الكريمة واحتمالات الحصول على حزم التعزيز، وهي عوامل لم تقم هذه الدراسة بقياسها.\n\nبطاقة تداولقطع من لعبة مملوكة\n→\nالأحجار الكريمةتم إتلاف البطاقة، وتم تحصيل الرسوم\n→\nحزمة التعزيزالأحجار الكريمة التي تم إنفاقها على الصناعة\n→\n3 بطاقات جديدةتم بيعها على «ماركت»، وتم اقتطاع العمولة\n↶\n\nلا يُشار هنا إلا إلى الآليات نفسها، وهي آليات خاصة بـ Valve — حيث تتحول البطاقات إلى جواهر، وتُستخدم الجواهر في صناعة حزم البطاقات، وتُنتج حزم البطاقات بطاقات — وكل منها موثَّق في «الأسئلة الشائعة حول بطاقات التداول» لـ Steam، وتُعتبر كل خطوة حدثًا سوقيًا خاضعًا للضريبة. مصدر آليات الحلقة: Valve، Steam الأسئلة الشائعة حول بطاقات التداول ↗.\n\nهذه ليست مجرد لحظة عابرة. إنها صناعة تتمتع ببنية أساسية راسخة تمتد لعدة سنوات.\n\nقد تكون اللقطة الفردية مجرد صدفة. لذا تم الاطلاع على الدليل العام لروبوتات البطاقات مرة واحدة في كل موسم من مواسم التخفيضات Steam، بالرجوع إلى أرشيف «وايباك ماشين»، من عام 2022 إلى عام 2026 — حيث تبين أن الروبوتات كانت تحمل نفس المخزون، ونفس الحسابات، في كل موسم تخفيضات. لا يظهر الاقتصاد ثم يختفي؛ بل يستمر، مع نواة مستقرة من المشغلين، وقد بلغ ذروته عند أكثر من ثلاثة ملايين مجموعة كاملة متوفرة في المخزون خلال تخفيضات شتاء 2023 — ما يقارب ثلث مليون مفتاح TF2 ذي قيمة تم الاحتفاظ بها في وقت واحد، في دليل واحد.\n\nمجموعات البطاقات الكاملة الموجودة في دليل الروبوتات العامة، حسب Steam للبيع\n\nلقطة واحدة من Wayback لموقع steam.supply/CardBots لكل تخفيضات موسمية. مرر المؤشر فوق الصورة لمعرفة قيمة مفاتيح TF2 وفقًا لسعر تلك اللقطة.\n\n0.0M\n0.9M\n1.8M\n2.6M\n3.5M\nA’22\nS’23\nW’23\nS’24\nW’24\nS’25\nS’26\n401تم رصد حسابات بوتات مميزة في مختلف عمليات البيع\n59موجود في 5 عمليات بيع أو أكثر من أصل 7 — النواة الثابتة\n16شارك في جميع المزادات السبعة، 2022–2026\n3.22 مليونأقصى عدد للمجموعات المتوفرة في المخزون (شتاء 2023) ≈ $570k–790k من المفاتيح\nكيف يبدو سلم شارات المبيعات من القمة\n\nيتوافق جانب الطلب مع جانب العرض. على الصعيد العام سلم شارات تخفيضات الصيف 2024 محفوظ 2026-07-16 ↗، وكان الحساب الذي يحتل المرتبة الأولى قد حصل على شارة البائع 1,740,645 مرة — 1.74 مليون مجموعة مكونة من عشر بطاقات، 17.4 مليون بطاقة تم دمجها في زخرفة ذات شكل واحد. وبسعر السوق الخاص بالبيع ($0.50 للمجموعة) فإن ذلك يساوي ~$870,000 من قيمة البطاقة؛ إذا تم شراؤها بالطريقة التي تُشترى بها فعليًّا — أي من خلال مبادلة مفاتيح TF2 لرفع مستوى الروبوتات بمعدل يبلغ حوالي 7.6 مجموعة لكل مفتاح — فإنها ~229,000 مفتاح، حوالي $410,000–$570,000 بالقيمة الحقيقية. الحساب الثاني: 552,000 مجموعة، ~$130,000–181,000. لا أحد يلعب من أجل هذا. يتم شراؤه، وكل مرحلة من مراحل الشراء تمثل معاملة يقوم Valve بتسويتها.\n\nالطريقة والحدود: يتم جمع رصيد «set-stock» عبر جميع الروبوتات التي تدرجها كل لقطة؛ و الرقم لا يمكن مقارنة عدد الروبوتات في كل لقطة عبر عمليات البيع، لأن بعض اللقطات تعرض الروبوتات المميزة فقط، بينما تعرض بعضها الآخر الدليل الكامل؛ لذا يُنظر إلى المخزون على أنه الحد الأدنى لما كان مرئيًا، وليس إحصاءً شاملاً. تستخدم القيم الرئيسية متوسط معدل المجموعات المعلن عنها لكل مفتاح في كل لقطة، ومفتاح TF2 من $1.79 إلى $2.49. يتم الحفاظ على الاستمرارية عبر اللقطات باستخدام SteamID64. استخدمت لقطات عام 2021 تخطيطًا قديمًا للصفحة ولم يتم تضمينها. البيانات: farm-economy-timeline.json؛ مستويات الشارات من SteamLadder؛ الأسعار المحددة من Steam Card Exchange (لقطات Wayback في وقت البيع، $0.05 لكل بطاقة).\n\nويكون هذا الأسطول موجودًا هناك حتى في الأوقات التي لا تُجرى فيها أي عروض ترويجية\n\nالصورتان أعلاه لا تمثلان مجموعتين مختلفتين. إنهما أسطول واحد، تم تصويره في لحظات مختلفة. وقد تمت قراءة الدليل المذكور في أعلى هذا القسم على يوم عادي لا تُقام فيه أي تخفيضات موسمية — 2026-09-22 — وحتى في حالة السكون ظلت ثابتة 91 روبوتًا و694,673 مجموعة كاملة: في حدود 186,000 مفتاحان من TF2، $334,000–$464,000 من قيمة البطاقة، في وضع الخمول بين عمليات البيع. وهذا هو الحد الأدنى الذي تتحمله العملية عندما لا يحدث أي شيء.\n\nوهي العملية نفسها. تمت مطابقتها باستخدام SteamID64، 87 من تلك الروبوتات الـ91 غير النشطة — 96% — تظهر أيضًا في اللقطات السبع للبيع المذكورة أعلاه، ستة عشر منها في كل واحدة. الدليل ليس كشكًا يُفتح للبيع ثم يُغلق بعده؛ بل هو مخزون تجاري دائم زاد حجمه بفضل هذا الأسطول نفسه ليصل إلى 3.22 مليون مجموعة في ذروة شتاء 2023 ولا يسمح أبدًا بانخفاضها إلى الصفر. التخفيضات هي عندما يتم البيع. وهي موجودة أيضًا خلال بقية العام.\n\nالدليل الافتراضي، لكل بوت على حدة\n\nيمثل كل مربع روبوتًا واحدًا في الدليل الموجود في 2026-09-22، ويتم تمييزه إذا كان يظهر أيضًا في اللقطات السبع الخاصة بالمبيعات. الرقم 91 هو ما ورد في الدليل في ذلك اليوم، وليس حجم الأسطول — تظهر 401 حسابًا مختلفًا في لقطات المبيعات، ويُظهر الدليل شريحة مختلفة في أيام مختلفة.\n\nشوهدت في مزادات سابقة (87) التحديثات الجديدة منذ آخر لقطة (4)\n\nقراءة خط الأساس لغير المعروضين للبيع 2026-09-22 من نفس الدليل العام، دون تسجيل دخول. تستخدم القيمة الافتراضية معدل «مجموعات لكل مفتاح» المعلن الخاص بكل بوت ونطاق المفاتيح $1.79–$2.49 أعلاه. يتم التداخل باستخدام SteamID64 مقابل اللقطات السبع الخاصة بالبيع. ونظرًا لاختلاف القوائم المميزة عن القوائم الكاملة باختلاف اللقطة، فإن هذا المقارنة تتم بين المخزون والهوية، وليس عدد المستخدمين. الحسابات في القسم 08.\n\n03 — السلم\nالمنتج الآخر هو الرقم الموجود بجانب اسمك\n\nالبطاقات هي المادة الخام. المنتج النهائي هو من المستوى Steam، ويحدد Valve سعره بالمجموعات.\n\n100Steam المستوى\nالمستوى المستهدف — اسحب أو استخدم مفاتيح الأسهم\nسعر المجموعة الكاملة الواحدة، بالدولار الأمريكي\n\n$0.20 هي المجموعة الكاملة الأرخص في الإحصاء، و$0.74 هي القيمة الوسيطة، و$1.70 هي المتوسط الحسابي. ويشمل الرقم البطاقات فقط — ولا يشمل أبدًا عمليات $5.00 فتح المحتوى أو تراخيص اللعبة.\n\n55,000يلزم وجود نظام التشغيل XP\n550المجموعات الكاملة المستهلكة\n110ألعاب تستحق اقتناءها، وزراعتها بنفسك\n$407.00تكلفة البطاقات بهذا السعر\n1,100بدلات الإسقاط المحروقة، الحد الأدنى\n$5,500.00$5.00 يتم إلغاء القفل، في حالة عدم إعادة استخدام أي حساب\nالمجموعات الكاملة التي تم استهلاكها، من المستوى 1 إلى 1,000\n\nصناعة شارة واحدة = مجموعة كاملة واحدة = 100 نقطة خبرة. كل مستوى داخل مجموعة من عشرة مستويات يكلف 100 نقطة خبرة أكثر من المجموعة التي تليها.\n\n0\n12,625\n25,250\n37,875\n50,500\n1\n250\n500\n750\n1000\n667\n550 sets\n\nالمستوى ليس زينة يمكن لـ Valve تجاهلها. إنه مرتبط بالحساب. من قسم «الأسئلة الشائعة» الخاص بـ Valve حول بطاقات التداول، فيما يتعلق بما تمنحك إياه صناعة الشارة: \"100 نقطة خبرة، مما قد يرفع مستواك إلى Steam. إذا ارتفع مستواك Steam، فسيتم زيادة الحد الأقصى لحجم قائمة أصدقائك بمقدار خمسة، وربما ستتمكن من فتح ميزة تخصيص ملفك الشخصي باستخدام «العروض». وبشأن حزم التوسعة: \"كلما ارتفع مستواك بمقدار Steam، زاد معدل حصولك على حزمة تعزيز: المستوى 10: +20%… المستوى 50: زيادة بمقدار +100% في معدل الحصول (أي أن المعدل قد تضاعف).\"\n\nإذن، يتيح هذا المستوى التحكم في أمرين: عدد الأشخاص الذين يُسمح لك بإضافتهم كأصدقاء، ومدى سرعة وصول البطاقات المجانية إلى مخزونك. والعامل الثاني يتراكم — فكلما زاد عدد المجموعات التي استهلكتها، زادت سرعة المنصة في تزويدك بالمزيد من المواد. Valve قام بدمج حلقة إعادة الاستثمار في المنتج.\n\nسعر الصرف ثابت ويتم الإعلان عنه. تستهلك صناعة شارة واحدة مجموعة كاملة وتمنح 100 نقطة خبرة؛ \"يمكنك تكوين مجموعة لنفس اللعبة خمس مرات كحد أقصى.\" ترتفع تكلفة كل مستوى من مستويات XP كل عشرة مستويات. وينتج عن ذلك ما يلي، ولا يوجد هنا أي تقدير:\n\nSteam المستوى\tالمجموعات الكاملة التي يستهلكها\tالألعاب التي يجب أن تمتلكها لتتمكن من صنعها بنفسك\tعند أدنى مستوى مسجل ($0.20)\tعند المجموعة الوسيطة ($0.74)\tالمقياس\n10\t10\t2\t$2.00\t$7.40\t\n50\t150\t30\t$30.00\t$111.00\t\n100\t550\t110\t$110.00\t$407.00\t\n200\t2,100\t420\t$420.00\t$1,554.00\t\n500\t12,750\t2,550\t$2,550.00\t$9,435.00\t\n667\t22,579\t4,516\t$4,515.80\t$16,708.46\t\n\nالرقم 667 ليس افتراضياً. إنه أعلى مستوى يُعلن عنه روبوت واحد في الدليل العام أنه قادر على الوصول به إلى العميل، من بين مجموعات 33,359 التي يمتلكها عبر 6,117 لعبة. العمود الرابع يمثل نفس السلم السعري مقارنة بأرخص مجموعة كاملة في أي مكان في التعداد؛ أما العمود الخامس فيقارنه بالمتوسط. وكلاهما يمثلان أسعار السوق للبطاقات وحدها، ويستبعدان تمامًا $5.00 فتح المحتوى وتراخيص الألعاب.\n\nكيف تم التحقق من المنحنى، لأن Valve لا ينشره\n\nValve يشير إلى معدل الشارة (\"كل 100 نقطة خبرة تمنحك مستوى إضافي Steam\") ثم يقوم بالتحوط ضدها — \"(على الأقل في البداية)\" — دون الإعلان عن التصعيد. المنحنى المستخدم أعلاه هو المنحنى القياسي، حيث يكلف كل مستوى داخل مجموعة من عشرة مستويات 100 نقطة خبرة أكثر من المجموعة التي تليها. وقد تم التحقق من صحة هذا المنحنى بالرجوع إلى الدليل بدلاً من الافتراض: بالنسبة لكل روبوت يكون الحد الأقصى المعلن عنه مقيدًا بمخزونه بدلاً من الحد الأقصى المسموح به وهو خمس مركبات لكل لعبة، المستوى المحسوب من هذا المنحنى يتطابق تمامًا مع المستوى الذي يعلنه البوت — 541 مقابل 541، و494 مقابل 494، و464 مقابل 464. وفي الحالات التي يُطبق فيها الحد الأقصى، يكون الرقم المحسوب أعلى ببضعة مستويات، وهو ما ينبغي أن يحدث مع حد أقصى يعتمد أيضًا على عمق المخزون لكل مباراة. لا توجد أي ادعاءات بشأن المنحنى فوق المستوى 667.\n\nاقرأ السلم الموجود بجوار القسم 02 وستتضح لك طبيعة العمل. لوضع حساب واحد في المستوى 500، يجب على شخص ما تجميع 12,750 مجموعة كاملة. استهلكت كل مجموعة من هذه المجموعات حصص الغنائم الخاصة بحسابين على الأقل، وكان كل حساب من هذين الحسابين قد تجاوز بوابة $5.00، وكان كل منهما يمتلك اللعبة. يوجد رقم تفاخر واحد في أعلى أحد الملفات الشخصية، ويستند إلى ما لا يقل عن 25,500 من حصص الإسقاط المستهلكة الموجودة أسفله. Valve لن يخسر تلك الصفقة. Valve هو الطرف المقابل في كل جزء منها.\n\n04 — الإحصاءات\nلا تتناول هذه الفقرة الزراعة بشكل عام، بل تذكرها بالتفصيل.\n\n§ 4.C ليست جملة عامة لمكافحة الروبوتات. فالأمثلة المذكورة فيها تذكر، واحدة تلو الأخرى، الأمرين اللذين تنتجهما «مزرعة البطاقات».\n\n\"لا يجوز لك استخدام أي شكل من أشكال البرامج النصية أو الروبوتات أو الماكرو أو أي أنظمة أخرى لا يتحكم فيها الإنسان (يُشار إليها فيما يلي بـ «الأتمتة») للتفاعل مع المحتوى والخدمات على Steam بأي شكل من الأشكال، بما في ذلك على سبيل المثال لا الحصر:\n\nأتمتة عملية إنشاء الحساب Steam،\nتزوير إحصائيات اللعب (مثل تضخيم عدد الانتصارات أو الهزائم، أو نقاط الخبرة، أو مدة اللعب)،\nالحصول على مكافآت أو إحراز تقدم دون مساهمة حقيقية من المستخدم،\n\"المشاركة في أنظمة التحكيم (مثل المراجعات النظيرة أو \"الإشراف\") عبر وسائل آلية، بما في ذلك التأثير على النتائج أو الإبلاغ عن المستخدمين من خلال إجراءات محددة مسبقًا بدلاً من الحكم المستنير.\"\n— Steam اتفاقية الاشتراك، البند 4.ج ↗ محفوظ 2026-09-24 ↗ · تم استرجاعه واقتباسه حرفياً 2026-09-22\n\"…وقت اللعب\"\n\nساعات التوقف عن العمل ليست ساعات وهمية. تجيب «الأسئلة الشائعة» الخاصة بـ ASF على هذا السؤال بشكل مباشر — \"لماذا لا يزداد وقت اللعب في الألعاب التي تم الحصول عليها عبر ASF؟\" — مع: \"نعم، ولكن ليس في الوقت الفعلي. يقوم تطبيق Steam بتسجيل مدة اللعب على فترات زمنية محددة ويحدد مواعيد التحديث وفقًا لذلك... وعادةً ما يتم التحديث كل 30 دقيقة تقريبًا.\"\n\nيتم تسجيل تلك الساعات في سجلات Valve، وعلى صفحات متجر Valve، وفي إحصائيات عدد اللاعبين المتزامنين التي تنشرها Valve بنفسها Steam الرسوم البيانية ↗ محفوظ 2026-09-23 ↗. في تلك الأرقام، لا يمكن التمييز بين الحسابات الخاملة والحسابات النشطة. ويتم حساب أرقام التفاعل التي تعلن عنها المنصة استنادًا إلى مجموعة تشمل، وفقًا لقواعد المنصة نفسها، حسابات غير نشطة.\n\n\"…دون مشاركة حقيقية من المستخدمين\"\n\nهذا تعريف لـ«إسقاط البطاقة غير المستخدمة»، كتبه Valve. وهو أيضًا تعريف للمستوى Steam، والشارة، وشروط الحصول على حزمة التعزيز، ونقاط الخبرة (XP) الخاصة بالملف الشخصي التي تأتي معها — وتؤكد الأسئلة الشائعة الخاصة بـ ASF صحة هذه الأداة \"يحافظ على القدرة على تلقي حزم التعزيز\"، لأنه يقوم بتسجيل الدخول بنفس الطريقة التي يتبعها التطبيق الرسمي.\n\nإذن، فإن نظام المكافأة والفعل المحظور هما آلية واحدة يُنظر إليها من جانبين. Valve صمم نظام المكافأة بحيث تُمنح المكافأة بناءً على الوقت وليس على المهارة، ثم أدرج بندًا يحظر منح المكافآت بأي وسيلة أخرى غير قضاء الشخص لهذا الوقت.\n\n05 — فخ الاستخدام التجاري\nكل خروج من بطاقة مزروعة يُعد خروجًا محظورًا بموجب الترخيص — وتُفرض رسوم عند المدخل بمقدار Valve\n\nهذا هو الجانب الذي لا يمكن حله من خلال «الزراعة المسؤولة». فالترخيص مخصص للاستخدام الشخصي غير التجاري، ولا تصبح البطاقة جديرة بالزراعة إلا في اللحظة التي تتوقف فيها عن كونها شخصية.\n\n§ 2.A — الترخيص\n\n\"Valve تمنحك بموجب هذا، وأنت تقبل، ترخيصًا وحقًّا غير حصريين لاستخدام المحتوى والخدمات من أجل الاستخدام الشخصي غير التجاري (باستثناء الحالات التي يُسمح فيها صراحةً بالاستخدام التجاري في هذه الوثيقة أو في شروط الاشتراك المعمول بها).\"\n\n§ 2.G — القيد\n\n\"لا يحق لك: … (iii) استغلال المحتوى والخدمات أو أي جزء منها لأي غرض تجاري، باستثناء ما يُسمح به صراحةً في أي مكان آخر من هذه الاتفاقية (بما في ذلك أي شروط اشتراك أو قواعد استخدام).\"\n\n§ 3.D — الرسوم\n\n\"Valve قد تفرض رسومًا على المعاملات التي تتم في سوق الاشتراكات. \"سيتم إطلاعك على أي رسوم قبل إتمام المعاملة.\"\n\nاقرأ العناصر الثلاثة معًا، وعندها يُغلق المركز\n\nالبطاقة التي يتم الاحتفاظ بها لا قيمة لها بالنسبة للمزرعة. أما البطاقة التي يتم بيعها أو مبادلتها أو تحويلها إلى جواهر، فقد استُخدمت لإنتاج قيمة — وقد ذكرت شركة Valve في خطاب الإنفاذ الخاص بها ما تسميه بذلك: فقد أُبلغ مشغل 170 روبوتًا بأن الحساب \"كان يُستخدم لجمع البطاقات التذكارية بشكل غير قانوني على موقع Steam، بالإضافة إلى أنشطة أخرى ذات صلة، ولم تقتصر على الأنشطة التجارية فقط.\" في تلك الحالة، وصلت البطاقات إلى السوق. وتم إتمام المبيعات. وتم تحصيل الرسوم. ثم صدر الحظر بعد ذلك.\n\nالرسوم عند ذلك المدخل لا تبلغ 15%. أما في البطاقة المُستأجرة، فتصل إلى ثلثي المبلغ.\n\n§ 3.D الاحتياطيات \"رسوم\". أما بالنسبة للبطاقات التي تنتجها المزرعة فعليًّا، فإن تلك الرسوم لا تشبه أبدًا المبلغ المعلن عنه ~15%. ويأخذ «السوق المجتمعي» 5% Steam رسوم المعاملة و10% رسوم اللعبة، مع حد أدنى يبلغ $0.01 لكل منهما (الأسئلة الشائعة الخاصة بـ «Community Market» لـ Valve). في البطاقة المعروضة بسعر سنت واحد، تلك المستويات هي السعر: يدفع المشتري ثلاثة سنتات، اثنان منها رسوم. ويؤدي تقريب الرقم لأدنى عدد صحيح إلى تحويل العنوان 15% إلى ضريبة فعلية ترتفع إلى 66.7% هذا هو بالضبط مجال عمل سوق البطاقات — بضعة سنتات لكل بطاقة.\n\nالرسوم الفعلية على عملية بيع في سوق «كوميونيتي ماركت»، بناءً على السعر المطلوب من البائع\n\n5% Steam + 10% لعبة، بحد أدنى $0.01 لكل منها. الشريط المظلل هو النطاق الذي يتم فيه تبادل بطاقات التداول فعليًّا — ما يقارب $0.03–$0.05 لكل بطاقة.\n\n0%\n10%\n20%\n30%\n40%\n50%\n60%\n70%\ncards\n$0.01\n$0.10\n$0.20\n$0.30\n$0.40\n$0.50\n66.7%\nالبائع يطلب\tSteam 5% (الحد الأدنى $0.01)\tالمباراة 10% (الدقيقة $0.01)\tيتحمل المشتري التكاليف\tالرسوم المجمعة\n$0.01\t$0.01\t$0.01\t$0.03\t66.7%\n$0.03\t$0.01\t$0.01\t$0.05\t40.0%\n$0.05\t$0.01\t$0.01\t$0.07\t28.6%\n$0.08\t$0.01\t$0.01\t$0.10\t20.0%\n$1.00\t$0.05\t$0.10\t$1.15\t13.0%\n\nتُخصص رسوم اللعبة البالغة 10% للتطبيق الذي أصدر البطاقة؛ أما المبلغ 5% فيعود إلى Valve، وبالنسبة للألعاب الخاصة بـ Valve وعناصر المخزون الأساسية، فإن الرسوم بالكامل تذهب إلى Valve. وفي كلتا الحالتين، فإن المال يغادر المزارع — فبيع بطاقة بقيمة ثلاثة سنتات يدر سنتًا واحدًا ويخسر اثنين. ضاعف ذلك بمئات الآلاف من مبيعات البطاقات التي تقل قيمتها عن خمسة سنتات التي يحققها المزارع و \"الرسوم التي يجوز لـ Valve تحصيلها\" إنه نموذج العمل، وليس مجرد حاشية. المصدر: Steam الأسئلة الشائعة حول سوق المجتمع — الرسوم ↗ محفوظ 2026-09-21 ↗، يُقرأ 2026-09-22؛ ويُعتبر المنحنى منحنىً حسابيًّا استنادًا إلى هذين السعرين المنشورين والحد الأدنى $0.01 لكل منهما.\n\nلا توجد أي طريقة لإعداد هذه الأداة يمكنها تجنب ذلك. فمن الممكن أن يديرها شخص واحد، عبر حساب واحد، مع التزام تام بضبط النفس — ولكن بمجرد أن يبيع هذا الشخص بطاقة واحدة تم الحصول عليها عن طريق «الزراعة» مقابل أموال من محفظته، فإن العقوبة المنصوص عليها في الفقرة § 2.G تنطبق عليه تمامًا كما تنطبق على مشغل عشرة آلاف بطاقة. وبالتالي، فقد احتفظت Valve بحقها في التذرع بخرق يمكنها استخدامه ضد كل بائع للبطاقات فعليًّا في سوقها، ورفضت التذرع به ضد جميعهم فعليًّا. القاعدة التي تُطبق بهذه المرونة لا تُعتبر قاعدة. إنها مجرد خيار. السؤال الذي يطرحه هذا المعرض ليس لماذا يتم التسامح مع مزارعي البطاقات؛ بل لماذا يُمارس هذا الخيار ضد مستخدم منفرد يبيع بطاقة، في حين أن الاقتصاد التجاري للبطاقات الذي تغذيها تلك البطاقات — خدمات التداول، وبرامج الروبوتات لرفع المستويات، والبائعون بالجملة — يستمر في العمل علنًا، حيث يدير إحدى أكبر مجموعاته موظف Valve (§ 08). يُفرض هذا الانتهاك على صغار المالكين، بينما يُستثنى منه الآليون.\n\n06 — سجل الإنفاذ\nدون سابق إنذار، على شكل موجات، وتنتقل عبر رقم الهاتف\n\nValve أدرج بند الصلاحية دون إشعار مسبق في الاتفاقية نفسها، في فقرة تلي فقرة الأتمتة مباشرةً.\n\n\"Valve يجوز لها تقييد أو إنهاء حسابك (حساباتك) أو اشتراك معين بسبب أي سلوك أو نشاط غير قانوني، أو يشكل غشًّا أو استخدامًا آليًّا، أو ينتهك قواعد السلوك عبر الإنترنت الواردة في Steam. أنت تقر بأن Valve ليست ملزمة بإخطارك قبل إنهاء اشتراكك (اشتراكاتك) و/أو حسابك.\"\n\n— Steam اتفاقية الاشتراك، البند 4.د ↗ محفوظ 2026-09-24 ↗ · تم التحقق من نصه حرفياً 2026-09-22\n\n1,000+ روبوتات · تم حظر التداول. \"يبدو أن هذا الحساب قد استُخدم لإدارة شبكة من حسابات الروبوتات. ويُعد استخدام الروبوتات انتهاكًا لاتفاقية المشترك Steam.\"\n\nأكثر من 170 روبوتًا · تم حظرهم نهائيًا، تخفيضات شتاء 2017. \"تم استخدام هذا الحساب لجمع بطاقات تذكارية بشكل غير قانوني على Steam، بالإضافة إلى أنشطة أخرى ذات صلة، وليس فقط الأنشطة التجارية. وقد تم حظر الحساب بشكل دائم، ولا يمكن لفريق الدعم Steam تقديم أي دعم إضافي بشأن هذه المسألة.\"\n\nأكثر من 120 روبوتًا · تم حظرهم نهائيًا. \"استُخدمت هذه الحسابات وغيرها لإغراق البنية التحتية لشبكتنا، وهو ما يمثل انتهاكًا لقواعد السلوك عبر الإنترنت Steam.\"\n\n— Steam رسائل الدعم المنشورة في ArchiSteamFarm قسم الأسئلة الشائعة، تحت عنوان «هل تم حظر أي شخص بسبب ذلك؟». المصدر ↗ · تم التحقق من نصه حرفياً 2026-09-22\nالحالة 4 — يونيو 2025، VAC حظر على ثاني أكسيد الكربون (CS2) غير المستخدم\n\nهناك حادثة لاحقة عن الحوادث الثلاث المذكورة أعلاه مسجلة في نظام التتبع الخاص بالمشروع: فقد تلقت الحسابات التي اكتفت بتشغيل لعبة «Counter-Strike 2» في وضع الخمول عبر الأداة VAC حظر — من النوع الذي يهدف إلى مكافحة الغش، وليس من النوع الإداري. ويرى المسؤول عن الصيانة أن وضع التباطؤ لا يمكن أن يتسبب في حدوث ذلك، لأن \"لا يفعل شيئًا سوى إخبار Steam بأننا نلعب لعبة معينة.\" هناك خلاف حول السبب. أما حقيقة حظر تلك الحسابات فهي أمر لا جدال فيه.\n\n— ArchiSteamFarm مناقشة رقم 3440، افتتحت في 26 يونيو 2025 ↗ · اقرأ 2026-09-22\n\nكيف ينتهي أمر الحساب الرئيسي\n\nوفي نفس سلسلة المشاركات، يصف أحد المشاركين في المشروع قاعدة الحظر: يمكن حظر الحسابات \"عن طريق السلسلة\"، إذا كانوا يستخدمون رقم هاتف واحد — \"قد يكون الأمر مجرد حظر واحد VAC، يمتد ليشمل الحسابات «النظيفة» المرتبطة بالحساب المحظور.\"\n\nSteam Guard يتطلب رقم هاتف. تُنشأ المزارات استنادًا إلى رقم هاتف المشغل. لذا، فإن إجراءات الإنفاذ لا تقتصر على الحسابات المؤقتة فحسب: بل تتتبع المعرّف المشترك حتى تصل إلى الحساب الذي يحتوي على المكتبة وقائمة الأصدقاء والمخزون. هذه هي الآلية التي يصفها أحد المشاركين في المشروع لكيفية قيام إجراء واحد بإزالة الحساب الرئيسي للمشغل مع المزرعة — وهذا هو السبب في أن الخسارة في موجة الإنفاذ لا تُقاس بعدد $5 من الحسابات. (وصفها أحد المساهمين في المشروع في مناقشة ASF GitHub رقم #3440؛ ولا يوجد تأكيد رسمي لـ Valve أو سابقة رسمية مسجلة.)\n\nالفقرة نفسها، بفارق خمس سنوات، من ثلاثة وكلاء مختلفين\n\nالشرط الذي يجعل الزراعة تشكل مخالفة — أي الاستخدام التجاري لترخيص شخصي غير تجاري — لا يقتصر على المزارع. إنه السبب المعتاد الذي تقدمه Steam عند إغلاق حساب ما بسبب الأنشطة التجارية، ويأتي هذا السبب في شكل نموذج جاهز. فيما يلي ثلاث حالات، نشرها الأشخاص الذين تلقوها، بفارق خمس سنوات، من ثلاثة وكلاء مختلفين تم ذكر أسمائهم.\n\nرسالة من فريق الدعم Steam في 29 سبتمبر الساعة 7:56 مساءً\n\n\"تم حظر الحساب الذي تكتب منه بسبب انتهاكه لشروط اتفاقية المشترك Steam. وقد تم تحديد أن هذا الحساب يُستخدم لأغراض تجارية استنادًا إلى أنشطة التداول والبلاغات الواردة من المجتمع وعوامل أخرى.\"\n\nهذا القفل دائم، ولا يمكن لفريق الدعم تقديم المزيد من المساعدة لك في هذا الشأن.\n\nنظرًا لأننا قد قدمنا جميع المعلومات المتوفرة لدينا، فإنني سأقوم بإغلاق طلب المساعدة هذا. يرجى ملاحظة أنك لن تتلقى أي ردود أخرى بخصوص هذه المشكلة.\n\nمع تحياتي،\n«هال»\n\nتم إغلاق طلب المساعدة هذا.\n29 سبتمبر 2020. نشره المستلم مع التعليق التالي \"RIP Trading.\" — @gergelyszabo94 ↗\nرسالة من فريق الدعم Steam في 12 يوليو الساعة 22:41\n\n\"تم حظر الحساب الذي تكتب منه بسبب انتهاكه لشروط اتفاقية المشترك Steam. وقد تم تحديد أن هذا الحساب يُستخدم لأغراض تجارية استنادًا إلى أنشطة التداول والبلاغات الواردة من المجتمع وعوامل أخرى.\n\nهذا القفل دائم، ولا يمكن لـ Steam Support تقديم المزيد من المساعدة لك في هذا الشأن.\n\nنظرًا لأننا قد قدمنا جميع المعلومات المتوفرة لدينا، فإنني سأقوم بإغلاق طلب المساعدة هذا. يرجى ملاحظة أن طلبات المساعدة المستقبلية التي يتم تقديمها بخصوص قفل الحساب قد يتم إغلاقها دون رد.\n\nSteam الدعم\n\"فيدو\"\n\nتم إغلاق طلب المساعدة هذا.\n12 يوليو 2024، واجهة باللغة البرتغالية. المستلم هو لاعب محترف في لعبة CS2: \"لقد اتصلت بالفعل بدعم ستيم، لكنني لا أتلقى سوى ردود آلية... لا أستطيع لعب Faceit، كما لا أستطيع خوض المباريات الاحترافية.\" — @prcs25 ↗ محفوظ 2024-07-15 ↗\nنقلها المستلم، r/steamsupport\n\n\"مرحبًا، تم حظر الحساب الذي تكتب منه بسبب انتهاكه لشروط اتفاقية المشترك Steam. وقد تم تحديد أن هذا الحساب يُستخدم لأغراض تجارية استنادًا إلى أنشطة التداول والبلاغات الواردة من المجتمع وعوامل أخرى.\"\n\nهذا القفل دائم، ولا يمكن لـ Steam Support تقديم المزيد من المساعدة لك في هذا الشأن.\n\nنظرًا لأننا قد قدمنا جميع المعلومات المتوفرة لدينا، فإنني سأقوم بإغلاق طلب المساعدة هذا. يرجى ملاحظة أن طلبات المساعدة المستقبلية التي يتم تقديمها بخصوص قفل الحساب قد يتم إغلاقها دون الرد عليها.\n\nSteam الدعم\n\"سالي\"\n\nتم استلامها ثلاث مرات، بناءً على ثلاثة طلبات منفصلة.\n29 مارس 2025. لم يكن الكاتب يستأنف قرار الحظر — فقد تعرض حسابه للسرقة مع بريده الإلكتروني، وكان يطلب استعادة حق الوصول إليه: \"أنا لا أسأل عن الحظر ولا أعترض عليه، بل أريد فقط الوصول إلى حسابي على Steam… Valve يردون عليّ بنفس الإجابة بالضبط، التي يتم نسخها ولصقها في كل طلب، ثم يغلقون الطلب.\" — r/steamsupport ↗، الواردة في مجموعة الشكاوى الخاصة بهذا التحقيق\n\nكلمة بكلمة، وفاصلة بفاصلة، على مدار خمسة وخمسين شهراً، وثلاثة وكلاء، ولغتين للتواصل. التعديل الوحيد في النص بأكمله هو تغيير الجملة الأخيرة لتشير إلى الفترة بين عامي 2020 و2024، من \"لن تتلقى أي ردود أخرى\" إلى \"طلبات المساعدة المستقبلية… قد يتم إغلاقها دون رد.\" أياً كانت العملية التي أدت إلى اتخاذ هذه القرارات، فإن الرسالة لا تُعد سجلًا لها. الأسباب المذكورة هي «الأنشطة التجارية، والتقارير المجتمعية، وعوامل أخرى» — وهي فئة، وتقرير مجهول المصدر، وباقي العوامل التي لم يتم تحديدها.\n\nخمس حالات أخرى، تم جمعها بالطريقة نفسها. الحالات الثلاث الأولى تنتمي إلى الفئة نفسها وتصل إلى النتيجة نفسها؛ أما الحالتان الأخيرتان فهما من نفس المكتب، لكنهما تتناولان قاعدة مختلفة بنفس الصياغة:\n\nالتاريخ\tما فعله الحساب\tماذا حدث؟\tالمصدر\n4 ديسمبر 2021\tالشراء والبيع على Buff — \"لم أفعل شيئًا سوى بعض عمليات الشراء والبيع على منصة Buff، المعروفة أيضًا باسم التداول بين الأقران (P2P)\"\tحظر مجتمعي: لا أسواق، ولا تداول، ومخزون باهظ الثمن مجمد\tr/csgomarketforum ↗ محفوظ 2025-03-27 ↗\n06/12/2021\tصفقات P2P أحادية الاتجاه عبر Buff وBitskins لشراء التجهيزات وترقية المعدات\tقفل دائم للاستخدام التجاري بالإضافة إلى قفل مجتمعي: \"عالق في وضع شبه غير مرئي… كما أن حسابي الشخصي عالق في الوضع الخاص\"\tr/GlobalOffensiveTrade ↗ محفوظ 2021-12-06 ↗\n20 ديسمبر 2024\tحساب مفتوح منذ عام 2017، وآلاف الساعات؛ ويقوم بإجراء عمليات تبادل في الأسواق المجتمعية للحصول على مجموعات معدات ذات مواضيع محددة واستبدال المعدات القديمة بأخرى جديدة\tقفل دائم مع قفل جماعي، دون إنذار مسبق أو إخطار؛ الدعم \"يقولون إن قرارهم نهائي\"، الردود آلية\tr/csgomarketforum ↗ محفوظ 2025-06-27 ↗\n23/12/2024\tمستخدم عائد يضيف أموالاً إلى محفظته بعد غياب دام عامًا، مستخدمًا شبكة VPN \"للأغراض العامة المتعلقة بأمن الإنترنت فقط\"\tحظر دائم من المجتمع مع لم يُذكر أي سبب على الإطلاق: \"الحظر دائم، ولا يمكنهم تقديم مزيد من المعلومات، وقد يتم إغلاق المزيد من التذاكر دون رد.\" 196 تصويت إيجابي، 340 ردًا\tr/steamsupport ↗\n4 أغسطس 2026\tسنوات من عمليات الشراء من إيران؛ ويذكر الكاتب أنه لم يقم أبدًا بنشر أي مشاركات، ولم يستخدم «الماركت» قط، ولم يستخدم المنتديات قط\tالوصول للمجتمع مغلق حتى عام 2038 أكثر من \"المناطق الخاضعة للعقوبات\"؛ تم إغلاق التذكرة من قِبل موظف يُدعى «أزول». وكان قد تمت الموافقة على طلب استرداد الأموال الخاص بنفس الحساب، والذي تم تقديمه من نفس عنوان IP الإيراني، قبل عام. تظل المكتبة والأموال في حوزة Valve.\tr/pcgaming ↗\n\nالسطر الأخير يمثل قاعدة مختلفة عن البقية — الامتثال للعقوبات، وليس الاستخدام التجاري — وقد أُدرج لأن شكل الإجابة مطابق تمامًا: فئة، لا دليل، لا استئناف، تذكرة مغلقة. كما أنه يطرح سؤالًا لا تطرحه الحالات الأخرى. فإذا كان تقديم الخدمة لهذا الحساب غير قانوني، فإن قبول المدفوعات على مدى سنوات كان غير قانوني أيضًا. لا بد أن يكون أحد هذين الموقفين خاطئًا، وواحد منهما فقط هو الذي كلف العميل أي شيء.\n\nتمت قراءة الرسائل الثماني جميعها في 2026-09-22 — حيث تمت قراءة سلاسل الرسائل الخاصة بعامي 2021 وديسمبر 2024 من خلال لقطات من «أرشيف الإنترنت»، أما البقية فقد تمت قراءتها عبر واجهة «ريديت» العامة، وذلك لأن «ريديت» رفضت الطلبات المباشرة المقدمة من المضيف المسؤول عن جمع البيانات. أما الرسالتان اللتان تعودان إلى عامي 2020 و2024 فقد تم نسخهما من لقطات الشاشة المرفقة بالمنشورات الأصلية، التي لا تزال منشورة حتى الآن. ولا يزعم هذا التحقيق أن أيًا من هذه الحسابات بريء أو مذنب بأي شيء — وهذا هو بيت القصيد بالضبط. لا يمكن لأي قارئ، ولا لأي جهة رقابية، أن يستنتج ذلك من الرسالة.\n\nملاحظة بشأن تحديد المصادر — الخسائر على مستوى المشغلين\n\nأفاد المشغلون الذين شملهم هذا التحقيق بخسائر تبلغ حوالي من خمسة آلاف إلى عشرة آلاف حساب لكل منها في حملات إنفاذ فردية، مع إجراء عمليات الجرد الرئيسية جنبًا إلى جنب مع المزرعة. تم تسجيل هذا الاستطلاع هنا باعتباره تقريرًا صادرًا عن الطرف المعني نفسه، وليس باعتباره نتيجة. لا يوجد حجم عينة منشور له، ولا تاريخ جمع محدد، ولا يتم التحقق منه لكل حساب على حدة، ولا يعتمد عليه أي رقم آخر في هذه الصفحة؛ وقد تم تمييز الصفين في القسم 02 اللذين يعتمدان عليه على هذا النحو.\n\nتم ذكر ذلك صراحةً بدلاً من إغفاله لسببين. آلية حظر السلسلة المذكورة أعلاه هي التفسير الموثق لهذا النمط بالذات. ويمكن للجهة التنظيمية أن تفرض من Valve السجل الوحيد الذي من شأنه حسم الأمر: كم عدد الحسابات التي تم اتخاذ إجراءات بشأنها في إطار الأتمتة، وفي أي موجات، وكم أنفق كل من تلك الحسابات في المتجر قبل إغلاقه. وإلى أن يتوفر هذا السجل، يظل الرقم على حاله — مُبلغًا عنه، ومنسوبًا، وغير مثبت.\n\n07 — عدم التماثل\nجانبا المكتب نفسه\n\nقارن معيار الإثبات هذا بالمعيار Valve المطبق على عملية الدعم الخاصة بها. العمود الأيمن هو سجل الحوادث الخاص بهذا الملف، وقد أُعيد نسخه مع التحفظات الواردة فيه.\n\nعميل، لأغراض التداول\n\nثماني حالات موثقة، 2020–2026\n\nالسلوك\nبيع أو شراء سلع على منصات بيع تابعة لأطراف ثالثة؛ وفي إحدى الحالات، لم يكن هناك أي تصرف على الإطلاق — فقد تم اختراق الحساب.\nالأدلة المعروضة\nلا شيء. \"استنادًا إلى أنشطة التداول وتقارير المجتمع وعوامل أخرى.\"\nإشعار\nلا شيء. Valve تم الاحتفاظ بذلك في الفقرة 4.د: \"Valve ليست ملزمة بإخطارك قبل إنهاء العقد.\"\nالاستئناف\n\"هذا الحظر دائم، ولا يمكن لـ Steam Support تقديم المزيد من المساعدة لك في هذا الشأن.\"\nتذكرة\nتم إغلاق الموضوع عند الرد الأول. أي طلبات أخرى \"قد يتم إغلاقه دون رد.\"\nالوصول\nالملف الشخصي، وقائمة الأصدقاء، والدردشة، والمتجر، والمخزون، وجميع العناصر التي تم شراؤها بأموال حقيقية.\nالمدة\nدائم.\nأسطول روبوتات آلي، لتلبية الحجم الكبير من الطلبات\n\n694,673 مجموعات كاملة متوفرة في المخزون العام عبر 91 روبوتًا\n\nالسلوك\nتشغيل نصوص برمجية آلية بدون واجهة مستخدم عبر آلاف الحسابات في آن واحد لتجميد البطاقات، وإنشاء شارات بكميات كبيرة، وتداول المجموعات على نطاق صناعي.\nالأدلة المعروضة\nأدلة البوتات المنشورة علنًا (steam.supply، SteamLvlUp) والمجموعات العامة التي تضم ملايين الأعضاء.\nإشعار\nعدم التدخل مطلقًا. 88.97% لا يخضع لأي نوع من الحظر; 99.8% من الحظر المتبقي هي مجرد إجراءات شكلية.\nالاستئناف\nليس ضروريًا. تعمل الأساطيل بشكل مستمر على مدار دورات حياة تمتد لعدة سنوات دون أي انقطاع.\nتذكرة\n—\nالوصول\nتبادل غير مقيد للمخزون، ورفع مستوى الشارات، وسيولة السوق.\nالربح يبلغ Valve\n$26.8M+ في الحد الأدنى للإنفاق في المتجر ($5.00 بوابة دخول لكل حساب) بالإضافة إلى 15% خصم على معاملات سوق المجتمع.\nوالسؤال الذي يطرح نفسه هنا، بعبارة واضحة\n\nيواجه أي عميل فردي يقوم بتداول البطاقات أو العناصر يدويًّا حظرًا دائمًا وغير قابل للاستئناف بموجب الفقرة § 4.C (الأتمتة) أو الفقرة § 2.G (الاستخدام التجاري). أما أسطول «الفارمينغ» الآلي الذي يشغّل روبوتات تعمل دون تدخل بشري عبر آلاف الحسابات، فيعمل علنًا بمعدل عدم تدخل يبلغ 88.97%. Valve هو المستفيد من كليهما.\n\nهذا التباين اقتصادي بطبيعته: فالمتداولون الأفراد يستفيدون من المنصة، في حين أن أساطيل البطاقات الآلية تضخ الملايين في بوابة الإنفاق في متجر Valve ($5.00 لكل حساب) وتغذي رسوم المعاملات في كل عملية إعادة بيع. ولا يتم تطبيق القواعد وفقًا للوائح المكتوبة، بل وفقًا لنموذج الإيرادات.\n\n08 — الحوكمة\nمن الذي ينظم اقتصاد البطاقات؟\n\nالاستنتاج المتكرر في هذا الملف — وهو أن الطبقة الخارجية المحيطة بـ Steam تُشغَّل من داخل Steam — ينطبق أيضًا على اقتصاد البطاقات، ويؤدي إلى نتيجة محددة: لا يمكن لأي جهة مستقلة أن تحدد ما تفعله إجراءات Valve فعليًا، لأن الطرف القادر على تحديد ذلك يقع داخل تلك الطبقة. تم استخلاص كل الحقائق الواردة أدناه من المجموعة العامة الخاصة بـ Valve وصفحات ملفه الشخصي على 2026-09-22، ويمكن لأي شخص إعادة عرضها عبر متصفح الويب.\n\nيقوم موظف Valve بإدارة أكبر مجموعة لتبادل البطاقات Valve موظف\n\nCardTrades ↗ تصف نفسها في عنوانها بأنها \"Steam المجموعة الرسمية لتبادل البطاقات\" ويحمل 97,114 عضو. المشرفون المسجلون فيها — أي الحسابات التي تتولى إدارة تلك المجموعة — هم ميكمان، الرقيب فوبر و afarnsworth ↗.\n\nيُشار إلى الملف الشخصي الأخير في علامات موقع Valve نفسه على أنه موظف Valve — حيث تتضمن الصفحة class=\"profile_header_valve_employee\" — يحدد موقعه على النحو التالي: بلفيو، واشنطن، وهو ينتمي إلى Valve، Steam و Steam مجموعة بطاقات التداول المجموعات. SteamID64 76561197960434622، عضو منذ 12 سبتمبر 2003.\n\nهذه الملاحظة ذات طابع هيكلي وليست شخصية، وهي لا نقطة تتعلق بالأتمتة — لا يقوم مشرف مجموعة تبادل البطاقات بتشغيل روبوت، ولا يوجد ما يشير هنا إلى عكس ذلك. المقصود هو البند الوارد في القسم 07. Steam «Card Exchange» هي خدمة بطاقات تجارية تابعة لجهة خارجية؛ ويُعد تداول البطاقات عبر خدمات الجهات الخارجية هو السلوك نفسه الذي يؤدي إلى قيام Valve بحظر الحسابات العادية بشكل دائم بموجب \"تُستخدم لأغراض تجارية استنادًا إلى الأنشطة التجارية والتقارير المجتمعية وعوامل أخرى.\" يُشغل موظف Valve منصب مشرف مُدرج في المجموعة المجتمعية الرسمية لتلك الخدمة، التي تضم 97 ألف عضو.\n\nلم تُوجه هنا أي تهمة بارتكاب مخالفة ضد أي فرد، ولا يُستنتج أي شيء بشأن ما ينطوي عليه هذا الدور. والتباين هو النتيجة: عندما يتعلق حساب عادي بخدمة بطاقة أو سكين تابعة لطرف ثالث، تكون النتيجة إغلاق التذكرة وحظر دائم دون إظهار أي دليل؛ أما عندما تكون الخدمة هي هذه الخدمة، فإن موظفًا Valve يُدرج في قائمة المشرفين ويكون الترتيب مرئيًا على الصفحة Valve التي تنشرها الخدمة نفسها. والسؤال المطروح هو نفسه المطروح في كل مكان آخر في هذا الملف: أظهروا التفويض المكتوب، إن وُجد — وإذا لم تكن هناك حاجة إليه، فاذكروا ذلك كتابةً، لأن ثمانية أشخاص في القسم 06 أُبلغوا بالعكس.\n\nطبقة قائمة الحظر، ومن يتولى إدارتها مشرف متطوعخدمة مقدمة من طرف ثالث\n\nمجموعة Steambans.com (محفوظة) ↗ (بث مباشر ↗ محفوظ 2025-12-03 ↗) تسجل نسبها في الوصف الجماعي المحفوظ لها: \"المجموعة المجتمعية الرسمية لـ Steambans.com Steam. SteamBans.com هي خدمة جديدة تمامًا تستند إلى مفهوم قديم. لقد ظلت قوائم الحظر العالمية نشطة لسنوات على برنامج WONID القديم من VALVe. وعندما حدث التغيير إلى STEAMID، كان من الطبيعي بالنسبة لنا أن نطور خدمة مصممة خصيصًا لهذا النظام الجديد. لكننا أردنا أيضًا المزيد. *. صفحة أرشيف لموقع Steambans الذي توقف عن العمل في عام 2013.\" ومن بين إدارييها المسجلين: جهاز فارغ و killahinstinct_ ↗.\n\nحساب المسؤول هذا هو لا موظف من فئة «a Valve» — لا يحمل علامة «موظف». إنه متطوع يتمتع بمكانة استثنائية: عضو في مشرفو المجتمع (414 عضوًا، توصف بأنها مجموعة \"من إعداد مشرفي مجتمع Steam\")، من منسقو ويكي، من Steam سوق المجتمع، بالإضافة إلى مجموعة Valve ومجموعات العرض المسبق، بما في ذلك Valve خط الأنابيب، Steam إصدار بيتا للعملاء، الإصدار التجريبي لتطبيق المصادقة عبر الهاتف المحمول، الإصدار التجريبي الجديد للمجتمع Steam، Steam المختبرات، ستيمووركس و الإبلاغ عن عناوين URL الاحتيالية. SteamID64 76561197960794555.\n\nكما يوجد داخل تلك الدائرة شخص يعرض «Steambans» مباشرةً في قائمة أعضاء مجموعته العامة: msart ↗ (قائمة المجموعات ↗)، SteamID64 76561197977933359، والتي يذكر ملفها التعريفي، بعباراتها الخاصة، ما يلي: \"أدير موقع steamid.uk والعديد من المواقع الأخرى المتعلقة بـ Steam وغير المتعلقة بها\"، والذي يدير شبكة مترابطة تضم ستة عشر مجموعة — SteamIDcouk (المجموعة الرئيسية «موقع Sid»)، SidAdmins، SidBans، steamideu، Steam3ID، s-id و SArchive من بينهم.\n\nيذكر موقع steamid.uk الرقم نفسه. وفي قسم «الأسئلة الشائعة» الخاص به: \"من الذي أنشأ SteamID؟ يتولى 76561197977933359 إدارة موقع SteamID والبنية التحتية للشبكة وأنظمة الأمان.\" يوجد في إجابتين أدناه توضيح لمصدر البيانات: \"يستخدم SteamID بشكل أساسي واجهة برمجة التطبيقات الويب Steam لجمع البيانات.\" تصف هذه الصفحة نفسها العديد من الخوادم المخصصة لدى مزودي خدمات استضافة مختلفين، بالإضافة إلى خوادم التطوير والتخزين وخوادم البحث النصي خارج الموقع، ومنشأة منفصلة للنسخ الاحتياطي.\n\nتم التحقق من ذلك من خلال السجلات المحفوظة في «أرشيف الإنترنت»: الـ لمحة عامة عن مجموعة Steambans بتاريخ 3 ديسمبر 2025 ↗، الـ لمحة موجزة عن ملف تعريف المشغل بتاريخ 14 سبتمبر 2024 ↗، و لمحة عن الأسئلة الشائعة لموقع steamid.uk بتاريخ 1 أبريل 2026 ↗، مع مطابقة البيانات التي تمت قراءتها مباشرةً من 2026-09-22.\n\nما الذي ينجم عن ذلك، وما الذي لا ينجم عنه\n\nقوائم الحظر، وتحديد معرّف SteamID، وتداول البطاقات هي الخدمات الثلاث التي تحدد من هو الجدير بالثقة، ومن يمكن تحديد هويته، وما هي قيمة أي عنصر. ولا تدير Valve أيًا من هذه الخدمات الثلاث. في كل حالة من هذه الحالات، كان الأشخاص الذين يتولون زمام الأمور ينتمون إلى داخل مدار Valve: موظف تم الإبلاغ عنه Valve مدرج في قائمة المشرفين على المجموعة الرسمية لخدمة البطاقات؛ ومشرف مجتمع Valve ذو خبرة طويلة يتمتع بإمكانية الوصول إلى البرنامج قبل الإصدار، ويقوم بإدارة مجموعة قائمة الحظر؛ وخدمة تحديد الهوية التي يديرها فرد واحد ينتمي إلى نفس الدائرة. ثلاث خدمات، وثلاث واجهات تحكم، وثلاثة أشخاص Valve كانوا قد منحوا هذه الصلاحيات بالفعل.\n\nالعضوية في المجموعة لا تعني التوظيف، ولا يُعتبر أي من هذا اتهامًا. هذه حقيقة في مجال الحوكمة، وهي السبب وراء الحجة المعتادة — هؤلاء أطراف ثالثة، ولا يمكننا التحكم فيهم — يجب اختباره بدلاً من قبوله. فالأشخاص الذين يتولون زمام الأمور ليسوا غرباء عن Valve. وValve هي الجهة الوحيدة التي يمكنها تحديد ما طلبته منهم، إن كان هناك ما طلبته أصلاً؛ ولا أحد من الخارج في وضع يسمح له بمعرفة ذلك.\n\nلا أحد يُحسب. هذه هي النتيجة.\n\nمساحة المعرفات Steam هي نطاق متواصل من الأعداد الصحيحة. إن مسحها والإبلاغ عن عدد الحسابات المحظورة، وعدد الحسابات المقيدة، وحجم المخزون الخاضع لحظر التداول لا يُعد برنامجًا بحثيًّا — بل هو مجرد حلقة تكرار ومفتاح واجهة برمجة التطبيقات (API). ويقوم Valve بتوزيع هذا المفتاح بنفسه، في steamcommunity.com/dev/apikey. ومع ذلك لا توجد جهة مستقلة تنشر نتائج ذلك التعداد السكاني. ليست هيئة تنظيمية، ولا صحفيًّا، ولا أكاديميًّا، ولا منظمةً للمستهلكين. والأرقام العامة الوحيدة المتاحة حول حجم إجراءات الإنفاذ بشأن Steam هي تلك التي يختار Valve ذكرها.\n\nالقدرة موجودة بالفعل. إنها محجوبة. الخدمة التي تعمل على تحليل وفهرسة مساحة المعرّفات على نطاق واسع — steamid.uk — تذكر في قسم «الأسئلة الشائعة» الخاص بها أنها \"تستخدم بشكل أساسي واجهة برمجة تطبيقات الويب Steam لجمع البيانات\" ويتم تشغيله عبر عدة خوادم مخصصة، ومساحات تخزين خارجية، وآلات للبحث النصي، ومنشأة نسخ احتياطي منفصلة. ويديرها فرد واحد. أما مجموعة الأشقاء الخاصة بقائمة الحظر التابعة له، فيشارك في إدارتها أحد مشرفي المجتمع ذوي الخبرة الطويلة الذي يتمتع بإمكانية الوصول إلى برامج Valve قبل إصدارها. الطرف الوحيد الذي لديه القدرة على نشر نتائج الفرز يقع ضمن مدار Valve، لكنه لا ينشرها.\n\nوهذا هو النمط نفسه الذي يرد في الملف في كل مكان آخر. فكل جهة تتخذ قرارات ذات تأثير جوهري على اقتصاد Steam — من هو الجدير بالثقة، ومن يمكن تحديد هويته، وما هي قيمة أي سلعة، ومن هو المحظور — تُعتبر اسمياً جهة خارجية، لكنها عملياً متاخمة لـ Valve. Steam لعبة «تبادل البطاقات» ليست استثناءً من هذا النمط؛ بل هي مثال آخر عليه. يمكن التذرع بحجة أن هؤلاء مشغلون مستقلون في حالة Valve، وذلك تحديدًا لأن أحدًا لم يتمكن قط من اختبار هذه الحجة باستخدام رقم ما.\n\nإحصاء الحسابات البالغ عددها 10.88 مليون: 88.97% لم يتم الاطلاع عليها\n\nتم تدقيق قاعدة التثبيت ArchiSteamFarm عبر Valve GetPlayerBans نقطة النهاية (10,880,610 حساب، 55 دقيقة). وتمثل المجموعة الفرعية غير المحدودة وحدها $26.8M+ في الحد الأدنى للإنفاق في المتجر (عتبة الدخول $5.00). الحسابات ذات الرقم 9,680,599 (88.97%) لا تخضع لأي نوع من الحظر، أما 99.8% من البقية فلا تُفرض عليهم سوى حظر شكلي من المجتمع، مما يتيح استمرار التداول الآلي.\n\n5,360,499أعضاء ASF غير المحدودين (العدد المعروض لـ Steam)\n10,880,610إجمالي عدد إدخالات واجهة برمجة التطبيقات (API) التي تم فحصها (المحدودة + غير المحدودة)\n9,680,599لم يتم حظره مطلقًا (88.97%)\n1,200,011تحمل أي حظر من نوع Steam (11.0%) — 99.8% تجميلي\n55 دقيقةلإجراء تعداد سكاني شامل، هناك عامل رئيسي واحد\nالأدلة الجنائية والتعداد الشامل\n\nيتم نشر التحليل الديموغرافي التفصيلي — بما في ذلك الرسوم البيانية لتوزيع أنواع الحظر، وعمر الحسابات عند تطبيق الحظر، ومجموعات سنوات إنشاء الحسابات (2020–2026)، والمعلومات الجغرافية المبلغ عنها ذاتيًا — في التحقيق الخاص بالتعداد السكاني.\n\nافتح «التعداد الكامل للحظر البالغ 10.88 مليون» (الملحق السادس) →القسم 4 — حجب معرّف الأصل →\n\nإذن، السؤال الذي يجب طرحه، والذي لا يمكن الإجابة عليه إلا بواسطة Valve: ما هو المعرّف أو الإمكانية التي تم سحبها، وفي أي تاريخ، وبناءً على قرار من، وما هو الأثر الملموس الذي أحدثته على المشغلين الذين استهدفتهم؟ — مقارنةً بتأثيره على كل من كان يحاول إجراء الإحصاء من الخارج. فالتغيير الذي ينهي عملية التدقيق المستقل لا يصبح محايدًا لمجرد أنه أُعلن عنه باعتباره إجراءً أمنيًا. وهذا هو السبب في أن التعداد السكاني المذكور في الفقرة أعلاه لم يُجرَ.\n\n09 — الطريقة والقيود\nما تمت قراءته، وما لم يُدّعى\n\nكل الاقتباسات الواردة في هذه الصفحة مأخوذة من المصدر المباشر على 2026-09-22 وقد تم نقلها حرفياً. ولا يوجد هنا أي شيء مستمد من عملية استخراج البيانات أو بيانات اعتماد من سوق البيانات أو مجموعة بيانات خاصة.\n\nمجموعات البيانات الأربع، والعمليات الحسابية التي أجريت عليها\n\nكل منها يمثل طلبًا عامًا واحدًا، يمكن إعادة تنفيذه من محطة طرفية. لم يتم استخدام أي حساب، ولم يتم تسجيل الدخول إلى أي سوق، ولم يتم استدعاء أي نقطة نهاية تتطلب بيانات اعتماد.\n\nمجموعة البيانات\tمن أين جاءت\tما الذي تم حسابه بناءً على ذلك\nإحصاء البطاقات\n13,876 مباراة\tSteam قائمة أسعار الشارات المنشورة من قبل «Card Exchange»، وهي نفس الخلاصة التي تُعرض صفحة الأسعار العامة ↗ محفوظ 2026-08-04 ↗\tالألعاب التي تصدر بطاقات، وعدد البطاقات في كل مجموعة، وأنواع البطاقات المختلفة، والسعر السوقي لكل مجموعة كاملة. وتُشكل القيم الوسيطة والمجموع $23,586.57 الأساس الحسابي لهذا البحث.\nأسعار الألعاب\n13,713 تم حلها\tنقطة نهاية المتجر العام الخاصة بـ Valve، store.steampowered.com/api/appdetails، نسخة إلى: الولايات المتحدة، حقل السعر فقط، على دفعات\tالوسيط والتوزيع الإحصائي لسعر التجزئة المعلن لأحد الألعاب التي تستخدم البطاقات؛ وعدد الألعاب التي يتجاوز مبيعات مجموعتها الكاملة مبيعات اللعبة نفسها.\nمخزون الروبوتات\n91 روبوتًا، 694,673 مجموعة\tالدليل العام لبرامج «كارد-بوت» الموجود على steam.supply/CardBots ↗، تُقرأ كما هي، دون تسجيل الدخول\tإجمالي المجموعات المتوفرة في المخزون، والحد الأدنى لعدد البطاقات، والحد الأدنى المسموح به للسحب، والحد الأدنى المخصص لكل روبوت في الحسابات المنفصلة.\nالتحقق المزدوج\n21 روبوتًا مشتركًا\tsteamlvlup.net/cardbots ↗ محفوظ 2026-02-10 ↗، وهو دليل مستقل يضم نفس الروبوتات\tلأغراض التحقق فقط. فيما يتعلق بالـ 21 روبوتًا المدرجة في كلتا القائمتين، توافق شركة Aggregate Stock على 0.03%؛ وأكبر تباين ناتج عن روبوت واحد هو 1.36%، وهو ما يتوافق مع عمليتي مسح للمخزون الفعلي أجريتا بفارق دقائق قليلة بينهما.\n\nالإشارة إلى المصدر، وفقًا لما ينص عليه الدليل الثاني: البيانات مقدمة من SteamLvlUp، مرخص بموجب CC BY 4.0 محفوظ 2026-09-23 ↗؛ وقد استُخدمت هنا فقط كوسيلة تحقق مستقلة لأرقام المخزون الخاصة بطرف ثالث، مع تعديل يتمثل في تجميع الصفوف الخاصة بكل روبوت ومقارنتها بدلاً من إعادة عرضها. Steam تم الإشارة إلى «Card Exchange» و«steam.supply» أعلاه عبر الرابط. أسعار الألعاب هي ملك لـ Valve. أسماء وصور البطاقات والألعاب والمجموعات هي ملك لـ Valve أو للناشرين، وقد أُعيد نشرها دون أي ادعاء أو ترخيص، باعتبارها حقائق تتعلق بالسوق.\n\nلم يتم إجراء قياسين كان من المقرر إجراؤهما، ولم يتم استبدالهما بأي قياسات أخرى. نقاط النهاية الخاصة بـ Steam في «Community Market» — نظرة عامة على الأسعار، البحث/العرض، تاريخ الأسعار — لا ترسل أي بيانات إلى المضيف الذي يقوم بجمع البيانات، بينما تُرجع صفحات مناقشة المجتمع Steam رمز حالة HTTP 403 إليه، لذا فإن الأرقام الواردة في هذه الصفحة لا تستمد من بيانات السوق الحية. أما طريقة حساب حجم المبيعات، التي كانت ستحسب عدد البطاقات التي تم الحصول عليها عند إعادة الضبط اليومية، فتتطلب جلسة تسجيل دخول Steam؛ يذكر سجل هذا التحقيق أنه لم يتم استخدام أي بيانات اعتماد خاصة بالمنصة، وقد تم الاحتفاظ بهذا البيان. الحد الأدنى لسعر السهم هو السعر الذي يمكن قياسه دون الحاجة إلى الروبوت.\n\nالمصادر الأولية\n\nSteam اتفاقية الاشتراك ↗ محفوظ 2026-09-24 ↗ — الفقرة 2.أ، الفقرة 2.ز، الفقرة 3.د، الفقرة 4.ج، الفقرة 4.د.\nSteam الدعم — حسابات المستخدمين المحدودة ↗ — عتبة $5.00 وقائمة الميزات المقيدة.\nValve — Steam الأسئلة الشائعة حول بطاقات التداول ↗ — آليات الحصول على العناصر ونظام اللعب المجاني $9.\nArchiSteamFarm الأسئلة الشائعة ↗ و المناقشة رقم 3440 ↗.\nSteam صفحات المجموعات والملفات الشخصية للمجتمع، تُقرأ مباشرةً، في القسم 08.\nالأسئلة الشائعة حول site.uk، لقطة من أرشيف الإنترنت 2026-04-01 ↗.\nثمانية Steam إخطارات بشأن قفل الدعم نشرها المستفيدون منها، 2020–2026، مدرجة مع روابطها في القسم 06.\n\nما لم يُدّعى\n\nلم يتم تقدير أي رقم للإيرادات المتأتية من «Valve» من «زراعة البطاقات». ولم يتم الإعلان عن عدد الحسابات النشطة لأي أداة، أما حصص التوزيع البالغة 1.39 مليون فهي لا إحصاء للحسابات المملوكة للمزرعة — انظر الملاحظة في القسم 02. لم يُتهم أي فرد بارتكاب مخالفة؛ وفي الحالات التي يُذكر فيها اسم شخص ما، يكون ذلك باستخدام اسمه المستعار العام Steam، في إطار دوره العام، من صفحة ينشرها Valve. لم يُؤكد أن أيًا من الحسابات الثمانية المقفلة في القسم 06 بريء أو مذنب؛ فالنتيجة تتعلق بالرسالة، وليس بالحساب. أرقام الخسائر المتعلقة بالمشغلين الواردة في القسم 02 هي تقارير من الطرف الأول ومُصنَّفة على هذا النحو في مذكرة التوريد. تم اقتباس الأسئلة الشائعة لموقع steamid.uk من لقطة أرشيف الإنترنت لأن الصفحة الحالية محمية بتحدي الروبوتات. ولا يُدعى هنا أنه تمت محاولة إجراء أي إحصاء للحظر وتم إخفاؤه — بل إن النتيجة تشير فقط إلى عدم نشر أي إحصاء من هذا القبيل. ولم يتم نمذجة المنحنى من المستوى Steam فوق الرقم 667.\n\nلماذا لا تُعتبر الأداة هي الموضوع\n\nArchiSteamFarm تنص على أن ذلك \"غير مصرح به من قبل Valve\" ولا يُوجه إليها أي اتهام في هذه الصفحة. وهي تُستخدم كأداة قياس، لأنها الجهة الوحيدة في هذا الاقتصاد التي توثق الآليات علنًا وكتابيًا. يمكن لـ Valve أن تلخص الأمر برمته في فقرة واحدة: تنشر الأتمتة التجارية التي تصرح بها، والسجل الخاص بكل مشغل فيما يتعلق بما فعله بشأن الباقي.\n\nاقرأ بعد ذلك: كيف يتم تحديد سعر السوق نفسه → · سلم الأسعار والحد الأقصى للإدراج → · البنود Steam لن يتم تضمينها →",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "مزرعة البوتات ليست تسربًا في متجر Valve. إنها العميل."
          },
          {
            "level": 2,
            "id": null,
            "text": "ما هي المزرعة في الواقع، خطوة بخطوة"
          },
          {
            "level": 3,
            "id": null,
            "text": "الشراء"
          },
          {
            "level": 3,
            "id": null,
            "text": "شراء الألعاب"
          },
          {
            "level": 3,
            "id": null,
            "text": "خامل\nتقوم الأداة بتسجيل دخول الحساب إلى شبكة Steam دون واجهة مستخدم، \"يقوم بتحليل شاراتك\"، ويقوم بإنشاء قائمة بالألقاب التي يمكن زراعتها ويبدأ \"لعب اللعبة المؤهلة والتحقق بشكل دوري مما إذا كانت اللعبة قد تم استغلالها بالكامل بالفعل.\" وصف المسؤول عن المشروع لهذه الآلية: إنها \"لا يفعل شيئًا سوى إخبار Steam بأننا نلعب لعبة معينة.\""
          },
          {
            "level": 3,
            "id": null,
            "text": "نفد عدد القطرات\nكل عنوان له حد معين. \"تحتوي كل لعبة على عدد محدد من البطاقات التي يمكن الحصول عليها. وبمجرد حصولك على جميع هذه البطاقات (حوالي نصف المجموعة الكاملة)، تصبح اللعبة غير مجدية من حيث جمع الموارد.\" على المزرعة التي ترغب في مواصلة الإنتاج أن تستمر في شراء البطاقات. ويتم تقييد إمدادات البطاقات من خلال عمليات الشراء — وهذا أمر مقصود، ويصب في صالح Valve."
          },
          {
            "level": 3,
            "id": null,
            "text": "سحب النقد\nتُصرف البطاقة عبر أحد الأبواب الثلاثة التالية: بيعها في «سوق المجتمع»، أو مبادلتها، أو سحقها لتحويلها إلى جواهر. وتُعد كل عملية من هذه العمليات معاملة في «سوق الاشتراكات» أو عملية مبادلة، وتنص الفقرة § 3.D على الرسوم التالية: \"Valve يجوز لها فرض رسوم على المعاملات التي تتم في سوق الاشتراكات.\" هذه هي الخطوة التي تجعل الأمر برمته انتهاكًا — انظر 05."
          },
          {
            "level": 2,
            "id": null,
            "text": "قبل أن تحقق المزرعة أي ربح، تكون قد دفعت بالفعل Valve"
          },
          {
            "level": 3,
            "id": null,
            "text": "ما هو الحجم الفعلي للشيء الذي يتم شراؤه"
          },
          {
            "level": 3,
            "id": null,
            "text": "ما حجم هذه المجموعة؟"
          },
          {
            "level": 3,
            "id": null,
            "text": "تكلفة الترخيص"
          },
          {
            "level": 3,
            "id": null,
            "text": "ما الذي تعرضه المجموعة النهائية"
          },
          {
            "level": 3,
            "id": null,
            "text": "أين توجد مجموعات 694,673"
          },
          {
            "level": 3,
            "id": null,
            "text": "ما الذي تقوله هذه الأرضية وما الذي لا تقوله"
          },
          {
            "level": 3,
            "id": null,
            "text": "والزراعة لا تغطي تكاليفها عند الأسعار التي يحددها Valve"
          },
          {
            "level": 3,
            "id": null,
            "text": "ما الذي تدعمه المزرعة فعليًّا"
          },
          {
            "level": 4,
            "id": null,
            "text": "مبيعات الألعاب"
          },
          {
            "level": 4,
            "id": null,
            "text": "\"عبر الإنترنت\" ووقت اللعب"
          },
          {
            "level": 4,
            "id": null,
            "text": "التسجيلات"
          },
          {
            "level": 4,
            "id": null,
            "text": "أموال المحفظة والرسوم"
          },
          {
            "level": 4,
            "id": null,
            "text": "Steam-المستوى العلاقات العامة"
          },
          {
            "level": 3,
            "id": null,
            "text": "والسحب النقدي بحد ذاته يمثل استنزافًا للقيمة Valve ضرائب مرتين"
          },
          {
            "level": 3,
            "id": null,
            "text": "هذه ليست مجرد لحظة عابرة. إنها صناعة تتمتع ببنية أساسية راسخة تمتد لعدة سنوات."
          },
          {
            "level": 3,
            "id": null,
            "text": "مجموعات البطاقات الكاملة الموجودة في دليل الروبوتات العامة، حسب Steam للبيع"
          },
          {
            "level": 3,
            "id": null,
            "text": "كيف يبدو سلم شارات المبيعات من القمة"
          },
          {
            "level": 3,
            "id": null,
            "text": "ويكون هذا الأسطول موجودًا هناك حتى في الأوقات التي لا تُجرى فيها أي عروض ترويجية"
          },
          {
            "level": 3,
            "id": null,
            "text": "الدليل الافتراضي، لكل بوت على حدة"
          },
          {
            "level": 2,
            "id": null,
            "text": "المنتج الآخر هو الرقم الموجود بجانب اسمك"
          },
          {
            "level": 3,
            "id": null,
            "text": "المجموعات الكاملة التي تم استهلاكها، من المستوى 1 إلى 1,000"
          },
          {
            "level": 3,
            "id": null,
            "text": "كيف تم التحقق من المنحنى، لأن Valve لا ينشره"
          },
          {
            "level": 2,
            "id": null,
            "text": "لا تتناول هذه الفقرة الزراعة بشكل عام، بل تذكرها بالتفصيل."
          },
          {
            "level": 3,
            "id": null,
            "text": "\"…وقت اللعب\""
          },
          {
            "level": 3,
            "id": null,
            "text": "\"…دون مشاركة حقيقية من المستخدمين\""
          },
          {
            "level": 2,
            "id": null,
            "text": "كل خروج من بطاقة مزروعة يُعد خروجًا محظورًا بموجب الترخيص — وتُفرض رسوم عند المدخل بمقدار Valve"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 2.A — الترخيص"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 2.G — القيد"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 3.D — الرسوم"
          },
          {
            "level": 3,
            "id": null,
            "text": "اقرأ العناصر الثلاثة معًا، وعندها يُغلق المركز"
          },
          {
            "level": 3,
            "id": "fee-ladder",
            "text": "الرسوم عند ذلك المدخل لا تبلغ 15%. أما في البطاقة المُستأجرة، فتصل إلى ثلثي المبلغ."
          },
          {
            "level": 3,
            "id": null,
            "text": "الرسوم الفعلية على عملية بيع في سوق «كوميونيتي ماركت»، بناءً على السعر المطلوب من البائع"
          },
          {
            "level": 2,
            "id": null,
            "text": "دون سابق إنذار، على شكل موجات، وتنتقل عبر رقم الهاتف"
          },
          {
            "level": 3,
            "id": null,
            "text": "الحالة 4 — يونيو 2025، VAC حظر على ثاني أكسيد الكربون (CS2) غير المستخدم"
          },
          {
            "level": 3,
            "id": null,
            "text": "كيف ينتهي أمر الحساب الرئيسي"
          },
          {
            "level": 3,
            "id": null,
            "text": "الفقرة نفسها، بفارق خمس سنوات، من ثلاثة وكلاء مختلفين"
          },
          {
            "level": 3,
            "id": null,
            "text": "ملاحظة بشأن تحديد المصادر — الخسائر على مستوى المشغلين"
          },
          {
            "level": 2,
            "id": null,
            "text": "جانبا المكتب نفسه"
          },
          {
            "level": 3,
            "id": null,
            "text": "عميل، لأغراض التداول"
          },
          {
            "level": 3,
            "id": null,
            "text": "أسطول روبوتات آلي، لتلبية الحجم الكبير من الطلبات"
          },
          {
            "level": 3,
            "id": null,
            "text": "والسؤال الذي يطرح نفسه هنا، بعبارة واضحة"
          },
          {
            "level": 2,
            "id": null,
            "text": "من الذي ينظم اقتصاد البطاقات؟"
          },
          {
            "level": 3,
            "id": null,
            "text": "يقوم موظف Valve بإدارة أكبر مجموعة لتبادل البطاقات Valve موظف"
          },
          {
            "level": 3,
            "id": null,
            "text": "طبقة قائمة الحظر، ومن يتولى إدارتها مشرف متطوع خدمة مقدمة من طرف ثالث"
          },
          {
            "level": 3,
            "id": null,
            "text": "ما الذي ينجم عن ذلك، وما الذي لا ينجم عنه"
          },
          {
            "level": 3,
            "id": null,
            "text": "لا أحد يُحسب. هذه هي النتيجة."
          },
          {
            "level": 3,
            "id": null,
            "text": "إحصاء الحسابات البالغ عددها 10.88 مليون: 88.97% لم يتم الاطلاع عليها"
          },
          {
            "level": 3,
            "id": null,
            "text": "الأدلة الجنائية والتعداد الشامل"
          },
          {
            "level": 2,
            "id": null,
            "text": "ما تمت قراءته، وما لم يُدّعى"
          },
          {
            "level": 3,
            "id": null,
            "text": "مجموعات البيانات الأربع، والعمليات الحسابية التي أجريت عليها"
          },
          {
            "level": 3,
            "id": null,
            "text": "المصادر الأولية"
          },
          {
            "level": 3,
            "id": null,
            "text": "ما لم يُدّعى"
          },
          {
            "level": 3,
            "id": null,
            "text": "لماذا لا تُعتبر الأداة هي الموضوع"
          }
        ],
        "links": [
          "https://help.steampowered.com/en/faqs/view/71D3-35C2-AD96-AA3A",
          "https://github.com/JustArchiNET/ArchiSteamFarm/wiki/FAQ",
          "https://steamcommunity.com/tradingcards/faq/",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260924114457/https://store.steampowered.com/subscriber_agreement/",
          "https://steamladder.com/ladder/badges/2861690/",
          "http://web.archive.org/web/20260716205303/https://steamladder.com/ladder/badges/2861690/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/farm-economy-timeline.json",
          "https://store.steampowered.com/charts/",
          "http://web.archive.org/web/20260923183013/https://store.steampowered.com/charts/",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://github.com/JustArchiNET/ArchiSteamFarm/discussions/3440",
          "https://x.com/gergelyszabo94/status/1311004678633795585",
          "https://x.com/prcs25/status/1811893857253982720",
          "http://web.archive.org/web/20240715122902/https://x.com/prcs25/status/1811893857253982720",
          "https://reddit.com/r/steamsupport/comments/1fjmgc5/what_to_do_when_your_steam_account_gets_hacked/mkelm2y/",
          "https://www.reddit.com/r/csgomarketforum/comments/r87owv/psa_my_steam_account_just_got_banned/",
          "http://web.archive.org/web/20250327203008/https://www.reddit.com/r/csgomarketforum/comments/r87owv/psa_my_steam_account_just_got_banned/",
          "https://www.reddit.com/r/GlobalOffensiveTrade/comments/r9xql9/d_recently_received_commercial_ban_for_what_seems/",
          "http://web.archive.org/web/20211206034804/https://www.reddit.com/r/GlobalOffensiveTrade/comments/r9xql9/d_recently_received_commercial_ban_for_what_seems/",
          "https://www.reddit.com/r/csgomarketforum/comments/1hhxx7m/d_permanently_locked_on_steam_for_commercial_use/",
          "http://web.archive.org/web/20250627014045/https://www.reddit.com/r/csgomarketforum/comments/1hhxx7m/d_permanently_locked_on_steam_for_commercial_use/",
          "https://www.reddit.com/r/steamsupport/comments/1hkctwt/permanent_ban_with_no_explanation/",
          "https://www.reddit.com/r/pcgaming/comments/1vf24lu/warning_to_all_gamersexpats_steam_took_my_money/",
          "https://steamcommunity.com/groups/card-trading-card-trades",
          "https://steamcommunity.com/id/afarnsworth",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/groups/steambans",
          "https://steamcommunity.com/groups/steambans",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/id/killahinstinct_",
          "https://web.archive.org/web/20240914124859/https://steamcommunity.com/id/msart",
          "https://steamcommunity.com/id/msart/groups/",
          "http://web.archive.org/web/20260401154714/https://steamid.uk/faq/",
          "https://phishdestroy.io/steam_dossier/ar/enforcement_audit.html",
          "https://phishdestroy.io/steam_dossier/ar/#evidence-blackout",
          "https://www.steamcardexchange.net/index.php?badgeprices",
          "http://web.archive.org/web/20260804200309/https://www.steamcardexchange.net/index.php?badgeprices",
          "https://steam.supply/CardBots",
          "https://steamlvlup.net/cardbots",
          "http://web.archive.org/web/20260210171205/https://steamlvlup.net/cardbots",
          "https://steamlvlup.net/",
          "https://creativecommons.org/licenses/by/4.0/",
          "http://web.archive.org/web/20260923221628/https://creativecommons.org/licenses/by/4.0/",
          "https://phishdestroy.io/steam_dossier/ar/market_economics.html",
          "https://phishdestroy.io/steam_dossier/ar/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/ar/elite_skins.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ar/card_economy.content.json",
      "export_json_sha256": "b64fbc94a54a639706611c18eadb1af37a56a1053029ff5901991f6fc02b33a3"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ar/elite_skins.html",
      "language": "ar",
      "title": "سلعة واحدة، نظامان للسعر — ملف «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/ar/elite_skins",
      "source_html_sha256": "2f3d25efd417dfd52026ef764e225461f2d1fad5012b65a1ea5aa6cf46d336f7",
      "exported_at": "2026-09-29T00:20:01.602Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "register",
            "source": "https://phishdestroy.io/steam_dossier/ar/elite_skins#register"
          },
          {
            "id": "",
            "source": "https://phishdestroy.io/steam_dossier/ar/elite_skins#selected"
          }
        ],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "elite_skins.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ar/elite_skins.pdf?v=print-20260929-v5",
        "sha256": "5eb473c4d5a97a6d11afabe9b9ca8c793d4dc5a398157ae9856c7a394391637f",
        "bytes": 129458,
        "pages": 6
      },
      "integrity": {
        "signed_object": "elite_skins.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "elite_skins.content.json.asc",
        "digest_file": "elite_skins.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify elite_skins.content.json.asc elite_skins.content.json",
          "sha256sum -c elite_skins.content.json.sha256"
        ]
      },
      "content": {
        "text": "الملحق الرابع / هيكل السوق / 20 سبتمبر 2026\nتسجيل Elite Skins — سقف سوق «1,800» البالغ 1 دولار\n\nعنصر واحد. نظامان للتسعير.\n\nما يثبته هذا القسم\n\nيقدم هذا السجل إحصاءً تجريبيًّا لجميع فئات سكنز CS2 التي يتجاوز سعرها الحد الأقصى المسموح به في سوق المجتمع (Community Market) التابع لـ «Steam» البالغ1,800 دولارًا أمريكيًّا، وذلك عبر خمس بورصات خارجية. ويثبت أن 248 الفئات عالية المستوى التي تم تأكيدها — والتي تمثل 18,394 عروضًا نشطة و78.6 مليون دولار أمريكي من السيولة المعروضة — هي 100% غائبة عن السوق الرسمي لـ Valve. ويُجبر البائعون الباحثون عن أسعار سوقية حقيقية بشكل هيكلي على اللجوء إلى منصات خارجية، مع الاعتماد حصريًّا على آليات التداول الأساسية لـ Steam.\n\n← العودة إلى ملخص الإدارة التنفيذية\n\nSteam يبلغ الحد الأقصى لسعر أحد العروض في «Community Market» حوالي1,800. دولار. وفي جميع المنصات الخمس التابعة لأطراف ثالثة التي تم تحديد أسعارها في هذه اللمحة، 419 تتجاوز أسعار الطلب الحالية الأرخص لفئات منتجات CS2 هذا الحد — و402 منها، 95.9%,، لا توجد لها أي قائمة Steam على الإطلاق. ويمتلكون معًا نسخًا مدرجة في قائمة «18,641» تبلغ قيمتها ما لا يقل عن $82.4 مليون. ويشترط الحصول على موافقة سوق ثانية قبل أن يُعتبر السعر ساريًا، 248 من بين تلك الفئات التي تم تأكيدها — وجميعها دون استثناء، 100%, غير موجودة على Steam. \"الأعز\" هو ملصق | تيتان (هولو) | كاتوفيتسه 2014 في $66,285، وقد تم إدراجها في أربعة أسواق بفارق 5.2% عن بعضها البعض، ولم تدرجها أي من أسواق Valve. ويوجد الترتيب الكامل، والصور، والتصنيف في أطلس سلم الأسعار.\n\nتفقد جميع إدخالات 419 ↓افتح الأطلس ↗اقرأ الطريقة\n248الفئات التي يتجاوز سعرها في سوقين أو أكثر الحد الأقصى المحدد\n18,394النسخ المعروضة في خمسة أسواق\n$78.6Mالقيمة الدنيا لتلك العروض\n100%منهم من غابوا تمامًا عن موقع Steam\n\nتصحيح · كانت هذه الصفحة تتضمن في البداية سعرًا لم يتم تأكيده\n\nكانت نسخة سابقة من هذه الصفحة تتضمن عنوانًا لـ «Souvenir AK-47» | «Point Disarray» مع سعر مطلوب يبلغ $148,954 في إحدى المنصات، بينما حددت منصة Steam سعره بـ $119.. ويقتصر هذا العرض على رف واحد ونسخة واحدة دون أن تتفق أي منصة أخرى على السعر، لذا فهو سعر مطلوب وليس سعرًا فعليًّا، ولم يعد موجودًا على الصفحة. يقتصر كل رقم رئيسي هنا الآن على فئات 248 التي يحدد سعرها سوقان على الأقل بشكل مستقل فوق الحد الأقصى. لم يتم حذف الصف نفسه — فهو لا يزال موجودًا في السجل أدناه، والتصنيف الذي أدى إلى خفض رتبته موضح بالكامل في أطلس سلم الأسعار.\n\n01 / الأموال الموجودة في عروض البيع النشطة\nالحد الأدنى القابل للقياس بالدولار\n\nأُعيد حسابها استنادًا إلى لقطة «cs2.sh» المرخصة عبر خمسة أسواق. ويُعد هذا الحد الأدنى للقيمة الإجمالية المعروضة للبيع في مجموعة فرعية محددة، وليس حجم المبيعات ولا تقييمًا لاقتصاد لعبة CS2.\n\n248 الفئات المؤكدة · 18,394 النسخ المدرجة · 5 منصات البيع$78.62M\n\nالحد الأدنى الإجمالي لسعر العرض المعلن لكل منتج من فئة CS2، الذي تحدد له سوقان أو أكثر، بشكل مستقل، سعرًا يتجاوز الحد الأقصى الذي تسمح به منصة Valve في سوقها الخاص.\n\nلماذا يُعتبر هذا رقمًا أدنى وليس تقديرًا؟\n\nبالنسبة لكل سوق، نقوم بضرب الأدنى اطلب شراء سلعة بالعدد الذي يحدده السوق. كل نسخة أخرى على ذلك الرف يُحدد سعرها عند مستوى السعر الأدنى المطلب أو أعلى منه، لذا فإن القيمة المعلنة الفعلية تكون أعلى — بحكم طبيعة النظام، وليس بناءً على التخمين. ولا يُعد ذلك عملية بيع، ولا تدفقًا نقديًّا، ولا تقييمًا على نطاق السوق بأكمله، وقد تظهر نفس السلعة المادية في أكثر من سوق واحد.\n\nتحقق من جميع صفوف مصدر 419 ↗\n★ قفازات رياضية | متاهة الشجيرات (تم اختبارها ميدانيًّا)\n$4.68M\nAWP | غونغنير (جديد من المصنع)\n$4.46M\nAWP | Dragon Lore (جديد من المصنع)\n$4.34M\n★ سكين الفراشة | فاد (جديد من المصنع)\n$4.17M\nAK-47| Wild Lotus (جديد من المصنع)\n$4.16M\n★ سكين الفراشة | دوبلر (جديد من المصنع)\n$3.64M\n\nتُظهر الأعمدة أكبر ستة عوامل مساهمة على مستوى الفئة في حساب الحد الأدنى للسعر، مقاسةً مقارنةً بالأكبر منها. ويعكس ارتفاع العمود كلاً من أرخص سعر عرض وعدد النسخ المعروضة. وقد يظهر نفس المنتج المادي في أكثر من سوق واحد، لذا يجب عدم إضافة هذه الأرقام إلى إجمالي أي سوق آخر.\n\n02 / أمثلة قابلة للفحص\nما لم يتناوله الحد الأقصى\n\nتتطابق الصور التوضيحية مع الأسماء الدقيقة للقطع، حيثما أمكن ذلك. والأسعار هي الأسعار المعروضة السارية الواردة في الكتالوج المؤرخ، وليست سجلات معاملات.\n\n★ Butterfly Knife | Doppler (Factory New)\n\nالمصدر: https://phishdestroy.io/steam_dossier/ar/elite_skins#selected\n\nالفجوة القابلة للقياس: لا يمكن أن تضاهي هذه العروض أي عرض من موقع Steam بنفس المبلغ بالدولار الأمريكي. موقع Valve نفسه الأسئلة الشائعة حول سوق المجتمع محفوظ على 2026-09-21 ↗ ينص على سعر عرض أقصى يبلغ حوالي1,800 دولار. ولا يزال بإمكان البائع عرض السعر بأقل من ذلك؛ أما ما إذا كان ذلك مقبولاً أم لا، فهذا خيار البائع. وهناك البحث في CSMarketCap عن العناصر التي تزيد قيمتها عن $1,800↗ يُظهر موقع «Factory New Dragon Lore» عبر الأسواق المفهرسة في «28» ما يقارب 1.1ألف عرض معروض؛ وقد يتم احتساب المخزون المكرر أكثر من مرة واحدة.\n\n03 / التبعية الهيكلية\nالحد الأقصى الذي فرضته شركة Steam يدفع عملية تحديد الأسعار خارج نطاق Steam\n\nهذه المقارنة هي مقارنة هيكلية. فهي لا تفترض أن كل سعر معروض هو سعر عادل، ولا تعامل العقارات المعروضة للبيع التي لم تُباع على أنها إيرادات.\n\n01 · القاعدة\nSteam يختتم القائمة\n\nValve يقول إن الحد الأقصى لقوائم «كوميونيتي ماركت» يبلغ حوالي $1,800. كما أن أرصدة المحافظ محددة بحد أقصى، ولا يمكن سحب أموال المحفظة نقدًا.\n\n02 · الملاحظة\nDragon Lore:10,940.85 دولار\n\nيُظهر كتالوج منصة \"5-\" ما يلي: 389 العروض الحية بالنسبة لـ AWP Dragon Lore (جديد من المصنع)، تبدأ الأسعار من10,940.85 دولار (الحد الأدنى المحدد في موقع CSFloat). ويحتوي السجل الأوسع نطاقًا على 248 فئات مؤكدة تتجاوز الحد الأقصى المحدد في موقع Steam.\n\n03 · النتيجة\nالسعر وتقسيم رسوم التحويل\n\nبائع يسعى إلى الحصول على هذا السعر الأعلى لا يمكن نشرها على موقع Steam. يمكن للخدمات الخارجية تحديد السعر النقدي، لكن عملية التسليم لا تزال تعتمد على نظام ملكية البضائع ونقلها الذي تديره شركة «Steam».\n\nالتناقض في السياسة: من إنتاج Valve اتفاقية المشترك محفوظ على 2026-09-21 ↗ تحتفظ بحقها في الاستغلال التجاري لخدمات موقع Steam ما لم يُسمح بذلك صراحةً، في حين أن 2016 بيان محفوظ على 2026-09-21 ↗ وقد ذكر أن مشغلي المقامرة كانوا يستخدمون بالفعل Steam OpenID والحسابات الآلية. وهذا دليل مباشر على أن Valve كانت على علم بوجود هذه الفئة من المشغلين الخارجيين في 2016. ومع ذلك، لا يمكن للسوق الرسمي نشر الأسعار الملحوظة لهذه السلع عالية القيمة. وهذا هو الاعتماد المعماري على عمليات تحديد الأسعار والمعاملات التي تتم خارجSteam؛ يتطلب تحديد حالة العقد لكل سوق على حدة تقديم أدلة منفصلة. ويعمل السوقان الغربيان الرئيسيان اللذان يستحوذان على حجم المعاملات الذي يتجاوز السعة المحددة ككيانات مؤسسية رسمية في ولايات قضائية رئيسية — CSFloat شركة (مسجلة في ولاية ديلاوير، الولايات المتحدة الأمريكية) و Skinport شركة ذات مسؤولية محدودة (مسجلة في شتوتغارت، ألمانيا، رقم السجل التجاري 764879) — تُجري معاملات علنية بقيمة مئات الملايين في مبيعات السلع بين الأفراد، معتمدةً بشكل مباشر على واجهات برمجة التطبيقات (Web APIs) والبنية التحتية التجارية لموقع Steam.\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\nتقع الصفوف الأربعة التي تبلغ قيمتها $100,000 عند الحد الأقصى لسعر الإدراج الخاص بـ «CSFloat». وقد تم تمييزها في السجل، ولا يجب اعتبارها تقييمات. لم يصل سجل العروض المؤرشفة على موقع CSFloat إلا إلى حوالي $6,999,، لذا يتم استخدام لقطة الكتالوج العام للسجل الكامل الذي يتجاوز $1,800.\n\n04 / لعبة أخرى من سلسلة «Valve»\nكما يتصدر السقف قائمة «Dota» 2\n\nوباستخدام نفس معيار «أرخص عرض» الصارم على موقع Skinport، تظهر فئات 166 CS2 وفئات 3 Dota 2. وهي تمثل لقطة منفصلة للسوق؛ فلا تضفها إلى CSFloat’s 245.\n\nعرض DOTA 2 · 1\nالهلال البطولي الوحشي\n\nأرخص سعر لـ «Skinport» هو: $14,622.25.\n\nعرض DOTA 2 · 1\nعباءة «الفن المظلم»\n\nأرخص سعر لـ «Skinport» هو: $8,255.16.\n\nعرض DOTA 2 · 1\nنجم مُشع تالف\n\nأرخص سعر لـ «Skinport» هو: $2,087.92.\n\nهذه ثلاث فئات من العناصر المدرجة، وليست كل عناصر لعبة Dota 2 الموجودة. افحص الصفوف التي تحتوي على الرابط Skinport المؤرخة ↗ و API الوثائق ↗.\n\n05 / المتانة\nلا تعتمد هذه النتيجة على الحد الأقصى المحدد\n\nValve يحدد السقف بعملة المنطقة التي ينتمي إليها المشتري، لذا فإن تحويله إلى الدولار الأمريكي لا ينتج عنه رقمًا دقيقًا واحدًا. ولذلك، يتم تكرار عملية الجرد عند كل عتبة محتملة. ولا تنخفض نسبة هذه العناصر المفقودة من Steam أبدًا عن 95%.\n\nتم اختبار العتبة\tفئات المنتجات\tالنسخ المدرجة\tالقيمة الدنيا\tغير موجود في Steam\n$1,800\t419\t18,641\t$82,449,526\t95.9%\n$2,000\t382\t15,159\t$75,541,325\t95.5%\n$2,070\t363\t12,336\t$69,560,305\t95.6%\n$2,300\t323\t11,644\t$67,984,432\t95.0%\n$2,500\t299\t10,950\t$66,203,929\t95.0%\n\nاقرأ صفًا واحدًا في كل مرة؛ فالصفوف هي مجموعات فرعية متداخلة من نفس التعداد السكاني، وليست مجموعات سكانية منفصلة. «القيمة الدنيا» تضاعف قيمة كل سوق الأدنى يُحسب العدد بناءً على عدد النسخ المدرجة فيه، لذا فإنه يُقلل من عدد الكتب الموجودة على الرف بحكم طبيعته. افتح مجموعة البيانات ↗\n\n06 / الندرة التي يمكنك حسابها\nكم هو قليل عدد هذه المنتجات المعروضة للبيع فعليًّا\n\nيقسم نظام «BUFF» الرف الخاص بكل قطعة إلى نطاقات متغيرة، ويُعلن عن عدد النسخ الموجودة في كل نطاق. وبذلك يتحول مصطلح «نادر» من مجرد كلمة إلى رقم محدد — ويتم تحديد سعر الحالة بشكل منفصل عن شكل القطعة.\n\n298 النسخ المدرجة\nAWP | أساطير التنين\n\n8 أصناف مختلفة محددة الأسعار. وأغلىها، بندقية AWP التذكارية | Dragon Lore (جديدة من المصنع)، يسأل $12,363 مع وجود نسخ من كتاب «20» على الرف.\n\nفي قسم أفضل العوامات الموجود على الرف (0–0.01) يوجد 2 نسخ، متسائلاً $17,875 — علاوة \"+45%\" على السعر الأساسي المطلوب للبند بناءً على حالته فقط.\n\n607 النسخ المدرجة\nM4A4 | هاول\n\n12 أصناف مختلفة بأسعار مختلفة. وأغلىها، تذكار M4A4 | Howl (جديد من المصنع)، يسأل $14,895 مع وجود نسخ من كتاب «2» على الرف.\n\n213 النسخ المدرجة\nAK-47 | Wild Lotus\n\n7 أصناف مختلفة بأسعار مختلفة. وأغلىها، بندقية AK-47 التذكارية | Wild Lotus (جديدة من المصنع)، يسأل $14,895 مع وجود نسخ من كتاب «2» على الرف.\n\n310 النسخ المدرجة\nAWP | غونغنير\n\n7 أصناف مختلفة بأسعار مختلفة. وأغلىها، تذكار AWP | غونغنير (بأثر تآكل طفيف)، يسأل $14,895 مع وجود نسخ من كتاب «2» على الرف.\n\nلماذا يُعد هذا الأمر مهمًا بالنسبة لبقية هذا الملف: هذه ليست مجرد مفاهيم مجردة. فهناك بضع مئات من النسخ لكل جائزة متوفرة على الرف المفتوح في جميع أنحاء العالم، وكل منها مرتبط بحساب واحد على موقع Steam ويتم نقلها عبر صفقة واحدة على موقع Steam. وفي سوق ضئيل كهذا، يُعد سرقة عنصر واحد من المخزون حدثًا يمكن قياسه، كما أن تقنيات الاستيلاء على الحسابات الموثقة في أجزاء أخرى من هذا التحقيق تحقق مكاسب مباشرة وقابلة للقياس.\n\nالأرقام المذكورة تمثل العروض المتاحة حاليًا في إحدى منصات البيع في وقت تسجيل البيانات، وليست العدد الإجمالي الموجود. ولا يتم احتساب النسخ الموجودة في المخزونات الخاصة في أي مكان هنا. افتح مجموعة بيانات «float» ↗\n\n07 / السلم بعيد عن الأنظار\nكلما ارتفع سعر السلعة، كلما ابتعدت عن أي مكان يمكن رؤيتها فيه\n\nكل درجة أدناه تمثل فئة أدلة مختلفة. وقد تم تعمد عدم دمجها في رقم واحد.\n\nدرجة\tالشكل\tما نوع هذه الحقيقة؟\nCeiling on Valve's own market\t~$1,800\tPublished rule, stated in the Steam Community Market FAQ.\nDearest ask several marketplaces agree on\t$66,285\tMeasured by us in this snapshot. Sticker | Titan (Holo) | Katowice 2014, quoted by four marketplaces within 5.2% of one another. An ask, not a sale.\nDearest ask seen on any single shelf\t$148,954\tOne marketplace, one copy, no second marketplace agreeing — and equal to a round CNY 1,000,000 at the snapshot rate. Listed here as the outer edge of what sellers ask, and relied on for nothing.\nPublic marketplace sale\t$49,999\tSpecialist Gloves | Crimson Kimono (FN) on CSFloat, as reported by SteamAnalyst. Platform-recorded, third-party reported.\nReported private sale\t$400,000\tAK-47 | Case Hardened, reported by PC Gamer in April 2023. Journalism, not a record we hold.\nReported offer, declined\t$1,500,000\tBlue Gem Karambit, pattern #387. No sale took place and the figure has not been independently confirmed. Included to mark the ceiling of the claims, not to assert a value.\n\nالنقطة الهيكلية: تتوقف أسعار سوق «Valve» عند حوالي $1,800.، بينما تصل الأسعار في الأسواق الخارجية إلى حوالي $66,000 — حيث تتفق عدة جهات على هذا السعر — وإلى حوالي $150,000 — حيث تتفق جهة واحدة فقط. فوق هذا المستوى، لا توجد أي منصة على الإطلاق — حيث تتم أكبر عمليات نقل الأصول الصادرة عن Valveبشكل خاص، بين الأفراد، دون إدراج في قائمة، ودون سجل على المنصة، ودون التحقق من الهوية، ودون إبلاغ. ولا تزال عملية النقل نفسها تتم عبر Steam. كلما ارتفعت القيمة، قلّت إمكانية رؤيتها من قبل أي شخص، وتكون البنية التحتية التي تنقلها تابعة بالكامل لشركة «Valve».\n\nأما الدرجتان الأخيرتان فهما تقارير صادرة عن جهات أخرى، وقد تم الإشارة إليها على هذا النحو. ولم يقم هذا المشروع بالتحقق من صحتها، ولا يعتمد عليها في التوصل إلى أي استنتاج.\n\nجميع الفئات التي تمت ملاحظتها في موقع 419\n\nالمصدر: https://phishdestroy.io/steam_dossier/ar/elite_skins#register\n\n09 / المصدر والحدود\nتحقق من الحساب\n\nنقوم بعرض البيانات المحلية والمصدر العام. ويقتصر نطاق العنوان الرقمي على موقع CSFloat في تاريخ التقاط البيانات.\n\nالحد الأقصى والشروط الخاصة بـ Valve\n\nSteam الأسئلة الشائعة حول سوق المجتمع ↗ محفوظ على 2026-09-21 ↗ يحدد الحد الأقصى التقريبي لسعر العرض البالغ1,800 دولارًا أمريكيًّا. و اتفاقية المشترك ↗ محفوظ على 2026-09-21 ↗ يحدد القيود المفروضة على الاستخدام التجاري.\n\nمن أين تأتي الأسعار\n\nتم استخلاص الأسعار وعدد الأسهم المدرجة ونطاقات الأسهم المتداولة من cs2.sh بيانات السوق API في إطار اشتراك تجاري مدفوع، باستخدام مفتاح ترخيص. لم يتم استخراج بيانات من أي منصة تجارية، ولم يتم استخدام أي حساب أو بيانات اعتماد تابعة لأي منصة تجارية. يجمع هذا المزود بيانات كل من BUFF وYoupin وCSFloat وSkinport وC5Game وسوق مجتمع Steam؛ وجميع الأرقام مقدمة بالدولار الأمريكي كما وردت. افتح بيان المنشأ ↗ — فهو يسجل النقاط النهائية الدقيقة، وأوقات الالتقاط، وتجزئات SHA-256 للقطات الأولية، بحيث يمكن لأي قارئ مستقل يمتلك مفتاحه الخاص استخراج البيانات نفسها وإعادة حساب كل رقم وارد في هذه الصفحة.\n\nما لم نتمكن من الحصول عليه\n\nالاشتراك الذي تم شراؤه يغطي اللقطات الحالية فقط. لم تكن نقاط النهاية التاريخية والمحفوظة متاحة لنا، و لا تُقدم في هذه الصفحة أي ادعاءات بشأن أي اتجاه، أو أي سعر سابق، أو أي تغير بمرور الوقت. كل شيء هنا هو لحظة واحدة، مؤرخة.\n\nسجل «CSFloat» السابق\n\nتضمنت النسخة الأولى من هذا المعرض 245 فئة من لقطة واحدة لكتالوج CSFloat بتاريخ 20 سبتمبر 2026: تلك اللقطة لا تزال هنا ↗. ويُعد السجل الحالي أوسع نطاقًا لأنه يشمل خمسة أسواق بدلاً من سوق واحد. وهذان السجلان يمثلان عمليتي تسجيل منفصلتين ولا يجب جمعهما معًا.\n\nبيان التنفيذ المحدد الخاص بـ Valve\n\nتحديث Valve بشأن تداول العناصر داخل اللعبة في لعبة «2016» ↗ محفوظ على 2026-09-21 ↗ يستهدف مشغلي المقامرة الذين يستخدمون OpenID وحسابات «Steam» الآلية. وهو أضيق نطاقًا من الحظر المفروض على جميع الأسواق الخارجية.\n\nحدود التفسير\n\nهذه عروض وليست عمليات بيع. قد يشمل اسم المنتج في السوق عدة قطع مادية تختلف في تفاصيل الألوان المتوفرة أو النقوش أو الملصقات. ولا يقيس هذا السجل القيمة السوقية الإجمالية أو نية شركة «Valve».",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "تسجيل Elite Skins — سقف سوق «1,800» البالغ 1 دولار"
          },
          {
            "level": 2,
            "id": null,
            "text": "الحد الأدنى القابل للقياس بالدولار"
          },
          {
            "level": 3,
            "id": null,
            "text": "لماذا يُعتبر هذا رقمًا أدنى وليس تقديرًا؟"
          },
          {
            "level": 2,
            "id": null,
            "text": "ما لم يتناوله الحد الأقصى"
          },
          {
            "level": 3,
            "id": null,
            "text": "★ Butterfly Knife | Doppler (Factory New)"
          },
          {
            "level": 2,
            "id": null,
            "text": "الحد الأقصى الذي فرضته شركة Steam يدفع عملية تحديد الأسعار خارج نطاق Steam"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam يختتم القائمة"
          },
          {
            "level": 3,
            "id": null,
            "text": "Dragon Lore:10,940.85 دولار"
          },
          {
            "level": 3,
            "id": null,
            "text": "السعر وتقسيم رسوم التحويل"
          },
          {
            "level": 2,
            "id": null,
            "text": "كما يتصدر السقف قائمة «Dota» 2"
          },
          {
            "level": 3,
            "id": null,
            "text": "الهلال البطولي الوحشي"
          },
          {
            "level": 3,
            "id": null,
            "text": "عباءة «الفن المظلم»"
          },
          {
            "level": 3,
            "id": null,
            "text": "نجم مُشع تالف"
          },
          {
            "level": 2,
            "id": null,
            "text": "لا تعتمد هذه النتيجة على الحد الأقصى المحدد"
          },
          {
            "level": 2,
            "id": null,
            "text": "كم هو قليل عدد هذه المنتجات المعروضة للبيع فعليًّا"
          },
          {
            "level": 3,
            "id": null,
            "text": "AWP | أساطير التنين"
          },
          {
            "level": 3,
            "id": null,
            "text": "M4A4 | هاول"
          },
          {
            "level": 3,
            "id": null,
            "text": "AK-47 | Wild Lotus"
          },
          {
            "level": 3,
            "id": null,
            "text": "AWP | غونغنير"
          },
          {
            "level": 2,
            "id": null,
            "text": "كلما ارتفع سعر السلعة، كلما ابتعدت عن أي مكان يمكن رؤيتها فيه"
          },
          {
            "level": 2,
            "id": null,
            "text": "جميع الفئات التي تمت ملاحظتها في موقع 419"
          },
          {
            "level": 2,
            "id": null,
            "text": "تحقق من الحساب"
          },
          {
            "level": 3,
            "id": null,
            "text": "الحد الأقصى والشروط الخاصة بـ Valve"
          },
          {
            "level": 3,
            "id": null,
            "text": "من أين تأتي الأسعار"
          },
          {
            "level": 3,
            "id": null,
            "text": "ما لم نتمكن من الحصول عليه"
          },
          {
            "level": 3,
            "id": null,
            "text": "سجل «CSFloat» السابق"
          },
          {
            "level": 3,
            "id": null,
            "text": "بيان التنفيذ المحدد الخاص بـ Valve"
          },
          {
            "level": 3,
            "id": null,
            "text": "حدود التفسير"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/ar/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/ar/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/ar/skin_atlas.html#grading",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-above-the-ceiling.json",
          "https://phishdestroy.io/steam_dossier/ar/elite_skins#selected",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://csmarketcap.com/search?minPrice=1800&amp;page=1",
          "https://store.steampowered.com/agreement/?l=english",
          "http://web.archive.org/web/20260921022032/https://store.steampowered.com/agreement/?l=english",
          "https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921021947/https://store.steampowered.com/oldnews/22883",
          "https://phishdestroy.io/steam_dossier/ar/#proxy-bypass-explainer",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/skinport-floor-over-cap.json",
          "https://docs.skinport.com/items",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-float-scarcity.json",
          "https://phishdestroy.io/steam_dossier/ar/elite_skins#register",
          "https://cs2.sh/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/csfloat-catalogue.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ar/elite_skins.content.json",
      "export_json_sha256": "56d7c83879086f4138bad34ebd8c8fc4174b1b64fc4d612fbb668265e13d0bbf"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ar/enforcement_audit.html",
      "language": "ar",
      "title": "لن يتم نشر نتائج التعداد السكاني Valve — الملف Steam",
      "source_url": "https://phishdestroy.io/steam_dossier/ar/enforcement_audit",
      "source_html_sha256": "8c730cedb96d8734785b11588099ba0e58939905a6d2eb404e4115855fb0eb7a",
      "exported_at": "2026-09-29T00:19:58.237Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "enforcement_audit.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ar/enforcement_audit.pdf?v=print-20260929-v5",
        "sha256": "313e918705ba7172287d3238dba3f04187ec9f453716a63b2871e73e360f6209",
        "bytes": 196443,
        "pages": 11
      },
      "integrity": {
        "signed_object": "enforcement_audit.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "enforcement_audit.content.json.asc",
        "digest_file": "enforcement_audit.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify enforcement_audit.content.json.asc enforcement_audit.content.json",
          "sha256sum -c enforcement_audit.content.json.sha256"
        ]
      },
      "content": {
        "text": "الملحق السادس — لن يتم نشر نتائج التعداد السكاني VALVE\nما حجم شبكة الحسابات على Steam؟ أحصيناها بأنفسنا.\n\nلا توجد أرقام منشورة عن عدد حسابات الأتمتة التي تعمل على Steam. ولا داعي لأن يكون هذا الأمر سريًّا: فمساحة معرّفات Steam هي نطاق أعداد صحيحة متجاورة، وتقوم Valve بتوزيع مفتاح واجهة برمجة التطبيقات (Web API) الذي يتنقل عبر هذا النطاق. لذلك أخذنا أكبر مجموعة تعرّف عن نفسها — مجتمع ArchiSteamFarm — وقمنا بقراءة كل عضو مرة واحدة عبر نقطة نهاية الحظر الخاصة بـ Valve. وهي تعلن عن نفسها تلقائيًا لأن ASF، عند التشغيل لأول مرة، تنضم تلقائيًا إلى المجموعة Steam ما لم يختر المستخدم صراحةً الانسحاب أو يلغي تحديد إعداد الانضمام إلى المجموعة (AutoJoinSteamGroup / الإحصائيات). ونظرًا لأن هذا الإعداد نشط بشكل افتراضي، فإن عضوية المجموعة تشمل شريحة واسعة من المستخدمين: شبكات الروبوتات التجارية النشطة التي تمتلك حسابات متعددة، وهواة العاب العاديين الذين يتركون حساباتهم في وضع الخمول، واللاعبين العاديين الذين شغّلوا البرنامج على حساباتهم الشخصية ولم يقوموا أبدًا بإلغاء الاشتراك الافتراضي. وهذا يجعل عضوية المجموعة بمثابة إحصاء فعلي للانتشار التراكمي للبرنامج: 10,880,610 إجمالي عدد الحسابات (مع 5,360,499 عضوًا مؤكدًا غير محدود تجاوز بوابة المتجر $5.00). ثم طرحنا السؤال الوحيد الذي يهم — ما الذي فعله Valve بهم فعليًّا؟\n\nما لا تتضمنه هذه الصفحة. هذا ليس حجة تدعو إلى أن يحظر Valve عشرة ملايين شخص، كما أنه ليس شكوى ضد مزارعي البطاقات. كل رقم وارد أدناه موجود هنا لسبب واحد: Valve هل حظر الأفراد بشكل دائم، والسبب الذي تذكره كتابةً هو الاستخدام التجاري لـ Steam والأتمتة. يقيس هذا كيف يتم تطبيق تلك القاعدة نفسها على السلوك نفسه على نطاق واسع — من قبل مشغل يقوم بجمع رسوم فتح $5.00 وتراخيص الألعاب ورسوم السوق Valve أثناء العملية. النتيجة هي عدم التناسق، وليس «المزرعة».\n\nالعدد البالغ 10.88 مليونالمحتالون الذين يتجولون (53.5 ألف)100 ألف تدقيق مدفوع مقابل تدقيق مجاني\n10,880,610إجمالي عدد أعضاء مجموعة ASF الذين استخدموا واجهة برمجة التطبيقات (API) الخاصة بـ Valve (المحدودة وغير المحدودة مجتمعة)\n88.97%لم يتم حظرها مطلقًا — لا تزال 9,680,599 حسابًا نشطًا\n63.06%من الحسابات المحظورة، هناك حسابات مدفوعة ($5+ الإنفاق) — شريحة 100,000 SRSWOR (±0.39% هامش الخطأ)\n67.77%من بين 51,732 من المحتالين الذين صدرت بحقهم أحكام قضائية، لا يوجد أي منهم خاضع لحظر ممارسة الاحتيال (إحصاء شامل)\n01 — المقياس\nعشرة ملايين حساب، وتسعة من كل عشرة لم يتم المساس بها\n\nمجموعة واحدة تُجري إحصاءً ذاتيًا، تُقرأ مرة واحدة عبر نقطة النهاية الخاصة بـ Valve.\n\nلماذا يتم العد التلقائي؟\nتنضم ASF إلى المجموعة من أجلك\n\nعند التشغيل الأول، يتم تعيين ArchiSteamFarm الإحصاءات يتم تعيينها على «صحيح» افتراضيًا، ويتم إضافة المشغل إلى مجموعة «SC Farm Steam» التابعة لـ Archi. ويتعين على المشغل أن يختار بنفسه الانسحاب من المجموعة. لذا فإن العضوية تمثل الحد الأدنى لعدد عمليات التثبيت — وليست الحد الأقصى. أما المشغلون الذين عطلوا ميزة «الإحصائيات» فهم غير مدرجين في الإحصاء؛ لذا فإن العدد الفعلي لعمليات التثبيت لا يقل عن هذا العدد.\n\nما نقرأه\n10,880,610 إجمالي عدد المشاركات\n\nأظهرت قائمة أعضاء واجهة برمجة التطبيقات (API) ما مجموعه 10,880,610 SteamID64 — سواء المحدودة أو غير المحدودة. وتُظهر صفحة مجموعة Steam عددًا يبلغ 5,360,499 (غير المحدودة فقط). وقد تم تمرير كل إدخال مرة واحدة عبر ISteamUser/GetPlayerBans على 2026-09-23. خمس وخمسون دقيقة على مفتاح واحد.\n\nالإجابة\n88.97% نظيف\n\n1,200,011 لا يخضع لأي Steam حظر (11.03%). أما الآخر 9,680,599 لا يوجد أي سجل على الإطلاق — ليس حظرًا مجتمعيًّا، ولا VAC، ولا أي شيء. المزرعة لم يتم إغلاقها. بل تُترك لتعمل. ويكفي هذا البند نفسه، الموجه إلى شخص واحد، لإزالته بشكل دائم.\n\nمن بين 10,880,610 حسابًا، كم عدد الحسابات التي تم استخدامها Valve\n\nمجموع السكان الذين تم مسحهم، مقسمين حسب ما إذا كان Valve قد فرض أي حظر على الإطلاق. الشريحة الحمراء تمثل كل ما فعله Valve تجاه هذا الأسطول على الإطلاق.\n\n88.97%لم يتم حظره قط\n11.03%\nلا يوجد حظر من أي نوع — 9,680,599 (88.97%)تتضمن حظرًا بقيمة Steam — 1,200,011 (11.03%)\n10,880,610تم مسح أعضاء مجموعة ASF ضوئيًا\n9,680,599لم يتم حظره مطلقًا — 88.97%\n1,200,011تطبيق أي حظر — 11.03%\n55 دقيقةلحساب كل ذلك، باستخدام مفتاح API واحد\nما دفعه هذا الأسطول بالفعل Valve لكي يكون موجودًا\n\nليس تقديرًا لما تجنيه المزرعة. بل هو الحد الأدنى لما أنفقته بالفعل في متجر Valve — مستمدًا من القاعدة الخاصة بـ Valve، المطبقة على الحساب الوارد أعلاه.\n\nيشمل العدد 10,880,610 قائمة أعضاء مجموعة ASF الكاملة كما تعرضها واجهة برمجة التطبيقات (API) — وهذا يشمل الحسابات المحدودة وغير المحدودة على حد سواء. أما العدد Steam فهو خاص بـ حسابات المستخدمين المحدودة تنص الصفحة على أن الحسابات المحدودة لا يُحتسب ضمن Steam عضوية المجموعة (يتم استبعادهم من حجم المجموعة المعروض)، لكن يمكن أن يظهروا مع ذلك في قائمة الأعضاء الأساسية. المجموعة الفرعية غير المحدودة — الحسابات التي أنفقت ما لا يقل عن $5.00 في المتجر Steam — هي بالضبط 5,360,499 — يظهر العدد Steam على صفحة المجموعة، والتي — وفقًا للقاعدة الخاصة بـ Steam — تستبعد الحسابات المقيدة. ويُطبق حساب الحد الأدنى $5.00 على تلك المجموعة الفرعية غير المقيدة فقط.\n\n5,360,499الأعضاء غير المحدودي العضوية\n(عدد المجموعات المعروضة لـ Steam)\n×\n$5.00الحد الأدنى الخاص بـ Valve\nللتحرر من القيود\n=\n$26,802,495الحد الأدنى للإنفاق في المتجر\nبواسطة المجموعة الفرعية غير المحدودة\n\nهذا يمثل الحد الأدنى للمبالغ التي استلمتها Valve بالفعل من الجزء غير المقيد من الأسطول — وهو ليس تقديرًا للإيرادات، ولا ادعاءً بتحقيق أرباح. فالإنفاق الفعلي لكل حساب أعلى بالنسبة لمعظم الحسابات؛ أما الرقم $5.00 فهو الحد الأدنى المطلوب فقط.\n\nالعائد الثانوي: رسوم تصل إلى 66.7% على حجم السلع المزروعة. بالإضافة إلى رسوم الدخول البالغة $26.8M، تُدفع عن كل بطاقة وسلعة يتم بيعها في سوق المجتمع رسوم إلزامية بحد أدنى قدره Valve ($0.01 Steam رسوم + $0.01 رسوم الناشر). بالنسبة للبطاقات العادية التي تبلغ قيمتها 3 سنتات والسلع غير المرغوب فيها، Valve يأخذ 2 سنتًا من أصل 3 سنتات — وهو ما يمثل خفضًا فعليًّا بمقدار 66.67% لصالح Valve، وهو ما يتجاوز بكثير معدل التسويق المعلن عنه 15%.\n\nتحذير هام يتعلق بالسكان: الانتماء إلى المجموعة لا يُعد دليلاً على أن كل حساب على حدة هو بوت مخصص، كما أنه لا يشمل كل البوتات الموجودة على Steam. تقوم ASF تلقائيًّا باشتراك الحسابات في مجموعة مجتمعها عند إطلاقها بشكل افتراضي؛ ما لم يقم المستخدم صراحةً بإلغاء تحديد أو تعطيل علامة الإعداد تلك (AutoJoinSteamGroup)، ويظل اللاعبون المنتظمون، واللاعبون الذين يشاركون لمرة واحدة فقط، وأعضاء المجتمع مدرجين في القائمة جنبًا إلى جنب مع أساطيل التجميع الآلية. علاوة على ذلك، لا يتضمن الحظر Steam حقلًا لإبداء الأسباب علنًا. وتعد هذه النتيجة معدلًا تجريبيًّا يشمل هذه المجموعة المرتبطة بالبرنامج، وليست حكمًا فرديًّا على أي حساب بمفرده. إجمالي، وقابل للتكرار: asf-ban-census-2026-09-23.json.\n\n02 — الجغرافيا\nأين يقع مقر الأسطول\n\nلم يذكر سوى 8.5% من الحسابات المحظورة بلدًا على الإطلاق. ومن بين الحسابات التي ذكرت بلدًا، تستحوذ الولايات المتحدة على الحصة الأكبر.\n\nيحتوي ملف التعريف Steam على حقل اختياري خاص بالبلد. 100,413 من أصل 1,182,811 حسابًا محظورًا قام بملء هذا الحقل — 8.5%.† ومن بين تلك الأقلية، تتصدر الولايات المتحدة القائمة بـ 15.5%، تليها أوكرانيا والصين وروسيا، بينما تمتد بقية الدول في شكل ذيل طويل عبر أوروبا وأمريكا اللاتينية وجنوب شرق آسيا. لا أحد يتحقق من صحة هذه البيانات: أفغانستان تقع ضمن المراكز العشرة الأولى، وهو ما يعكس تقريبًا قيمتها الحقيقية. أما الـ 91.5% الأخرى فقد تم حذفها بدلًا من تخصيصها، لذا فإن ما يلي يمثل شكل أقلية اختارت نفسها بنفسها — وليس خريطة للأسطول، ولا أساسًا للقول من أين يتم تشغيله.\n\nالحسابات المحظورة حسب البلد المحدد\n\nأبرز 15 دولة من بين 100,413 الحسابات المحظورة التي تكشف عن موقع عام. النسبة المئوية تمثل حصة تلك المجموعة الفرعية. مرر المؤشر فوقها للاطلاع على الأعداد.\n\n0%\n5%\n10%\n15%\n20%\nUnited States\nUkraine\nChina\nRussia\nCanada\nAustralia\nJapan\nBrazil\nGermany\nAfghanistan\nUnited Kingdom\nRomania\nFrance\nPhilippines\nIndia\n\nالموقع الذي تمت قراءته من GetPlayerSummaries بالنسبة للمجموعة الفرعية المحظورة. يتم تعيين هذا الحقل من قِبل صاحب الحساب ولا يخضع للتحقق من قِبل أي جهة، لذا فإن نقطة خروج شبكة VPN أو إدخالًا مزاحًا يُعتبران بنفس قيمة الإدخال الحقيقي.\n\n03 — النضارة\nحسابات حديثة، وليست متأخرات قديمة\n\nوبناءً على تاريخ إنشاء الحسابات، فإن هذه المجموعة المحظورة حديثة العهد، وليست من بقايا عصر بطاقات التداول.\n\nلو كانت هذه فوضى قديمة يجري إصلاحها ببطء، لكان معظم الحسابات المحظورة تتركز في السنوات الأولى لظهور بطاقات التداول. لكن الأمر عكس ذلك تمامًا. فمن بين 1,132,852 الحسابات المحظورة التي يُعرف تاريخ إنشائها، 70% تم إنشاؤها في عام 2020 أو بعده، ونحو نصفها منذ عام 2023. يرتفع العدد من 59,175 الذي تم إنشاؤه في عام 2017 ليصل إلى ذروة تبلغ 227,030 تم إنشاؤها في عام 2024 وحده. وقد غادر كل واحد منهم بوابة المتجر $5.00 قبل أن يتمكن من تسليم البطاقة، لذا تم تحصيل رسوم الدخول من كل واحد منهم.\n\nمتى تم إنشاء الحسابات المحظورة\n\nسنة إنشاء حسابات الأعضاء المحظورين 1,132,852 الذين يكشفون عن تاريخ إنشاء حساباتهم. تتراوح الفترة بين 2020 و2026، وليست فترة بطاقات التداول التي امتدت بين 2013 و2015. الذروة: 2024. مرر المؤشر فوق الأرقام لمعرفة العدد.\n\n0k\n63k\n125k\n188k\n250k\n'13\n'14\n'15\n'16\n'17\n'18\n'19\n'20\n'21\n'22\n'23\n'24\n'25\n'26\n70%من الحسابات المحظورة التي تم إنشاؤها في عام 2020 أو بعده\n227,030الحسابات المحظورة التي تم إنشاؤها في عام 2024 — العام الذي شهد ذروة هذه الظاهرة\n51,701الانخفاض الذي حدث في عام 2021، بين عامين شهدا ذروة — دون تفسير\n2003→2026النطاق موجود، لكن البيانات تغطي السنوات الست الأخيرة\n\nيعود تاريخ إنشائه إلى GetPlayerSummaries بالنسبة للمجموعة الفرعية المحظورة، بعد إزالة التكرارات باستخدام SteamID64. تاريخ الإنشاء هو تاريخ إنشاء الحساب، وليس تاريخ حظره أو بدء ممارسته لـ«الفارمينغ»؛ ويُستخدم هنا كدليل على مدى حداثة هذه المجموعة، وليس كدليل على النية. هناك ثلاثة أمور لا يظهرها الرسم البياني:\n\nاتجاه سيظهر بعد عام 2024. الحساب الذي تم إنشاؤه في عام 2025 أو 2026 لم يمر عليه وقت كافٍ لتلقي حظر، كما أن عام 2026 يشمل تسعة أشهر — لذا فإن التسلسل 227,030 → 121,070 → 16,534 يُعد رقابةً، وليس انخفاضًا.\nمعدل الحظر. تم قراءة سنوات الإنشاء للحسابات المحظورة فقط، لذا لا يوجد مقام. فمجرد تزايد عدد المستخدمين الحاليين كفيل بإنشاء هذا المنحنى.\nلماذا انهار عام 2021. يقع 51,701 بين 105,821 و104,641، تحت نصف كل من الجارين. ولا يوجد تفسير علني لذلك؛ فقد تُرك مرئيًا بدلًا من تنعيمه.\n04 — التوقيت\nعندما يتم تنفيذ Valve، فإن ذلك يتم خلال السنة الأولى\n\nالحجة الواضحة لتبرير عدم المساس بـ 88.97% هي تراكم الأعمال المتأخرة. لكن الحظر الذي تم تحديده بتاريخ محدد يشير إلى عكس ذلك.\n\nكم كان عمر الحساب عندما تم فرض الحظر عليه\n\nعمر الحساب في لحظة الحظر، بالنسبة لـ 293,750 حسابات محظورة تحتوي على كل من تاريخ الإنشاء وتاريخ آخر حظر. وقد تم اكتشاف أكثر من نصفها خلال السنة الأولى.\n\n0%\n10%\n20%\n30%\n40%\n<6 mo\n33.7%\n6–12 mo\n21.5%\n1–2 y\n20.6%\n2–5 y\n14.3%\n5 y+\n10.0%\n55.1% inside the first year\nتم حظره خلال السنة الأولى — 55.1%تم حظره لاحقًا — 44.9%\n0.80 سنةمتوسط عمر الحساب عند فرض الحظر\n55.1%تم حظره خلال السنة الأولى من إنشاء الحساب\n33.7%تم حظره خلال الأشهر الستة الأولى\n293,750الحسابات التي تحتوي على كلا التاريخين\n\nهذا هو الرد على الحجة الدفاعية البديهية. إذا كان 88.97% من الأسطول لم يُمسّ بسبب بطء عملية الإنفاذ — أي أن هناك تراكمًا في القضايا يجري البت فيه تدريجيًّا — فإن الحظر الذي افعل قد يُفترض أن البيانات ستكون قديمة. لكن الحقيقة عكس ذلك تمامًا: كان متوسط عمر الحساب المحظور تبلغ من العمر تسعة أشهر ونصف، وتم القبض على ثالث — 33.7% — في غضون ستة أشهر. وعندما يتدخل Valve في هذه المجموعة، فإنه يتصرف بسرعة. أما التسعة من كل عشرة الذين ما زالوا طلقاء، فهم لا ينتظرون في طابور.\n\nالعمر عند الحظر = تاريخ الإنشاء اعتبارًا من GetPlayerSummaries طُرح من تاريخ الحظر الذي ينص عليه عدد الأيام منذ آخر حظر، تابع القراءة 2026-09-23. يتم حسابه فقط في الحالات التي تتوفر فيها القيمتان معًا: 293,750 من 1,200,011 حسابًا محظورًا. أما الحسابات المتبقية فلا تبلغ عن قيمة «عدد الأيام منذ»، ويتم استبعادها، ولا يتم افتراضها — لذا اقرأ هذا على أنه شكل المجموعة الفرعية المؤرخة، وليس لكل حظر.\n\n05 — ما هو الحظر بالضبط؟\nعندما يعمل Valve، فإنه لا يوقف البوت\n\nمن بين الـ 11% التي تخضع لأي حظر، انظر أي حظر هو.\n\nالحظر ليس حظرًا. من بين 1,200,011 حسابًا، قام Valve بالإبلاغ عن، 99.8% يحمل المجتمع حظر — قيود مفروضة على المنتديات والملفات الشخصية والمجموعات لا تؤثر بأي شكل على روبوت التداول. فلا يزال بإمكان الحساب استلام البطاقات، ومواصلة التداول، ونقل المخزون. 22.2% تحمل حظرًا واحدًا على الأقل من حظر الألعاب و3.9% حظرًا من فئة VAC؛ وتتداخل الفئات، لذا لا يتم جمعها. أما العقوبة الوحيدة التي توقف التداول فعليًّا، وهي حظر الاقتصاد/التداول، فهي مفروضة على 5,214 حسابًا. نحن لا نبني حجتنا على هذا الرقم — فحالات الحظر التجاري نادرة بشكل عام في Steam. المغزى من هذا الرسم البياني أبسط: حتى النسبة الضئيلة Valve هل تستمر شركة «تاتش» في ممارسة أنشطة التداول.\n\nما هي الأسباب الحقيقية وراء حظر الأشخاص الذين يحملون الرمز 11%؟\n\nنسبة كل نوع من أنواع الحظر مقارنةً بإجمالي 10,880,610 الأعضاء الذين تم فحصهم. قد تتضمن الحسابات أكثر من نوع واحد. مرر مؤشر الفأرة فوق العنصر لمعرفة الأعداد.\n\n0%\n4%\n8%\n11%\n15%\nCommunity ban\nGame ban\nVAC ban\nEconomy / trade ban\n\nلا يحتوي الحظر من النوع Steam على حقل «السبب»، لذا لا يُنسب أي من هذه الحظر إلى «تجميع البطاقات» على وجه التحديد — وهذا هو مزيج أنواع الحظر الموجودة، إلى جانب ما يقيد كل نوع فعليًّا. الحظر المجتمعي لا يمنع التداول؛ أما الحظر الاقتصادي/التجاري فيمنعه. المجموع: asf-ban-census-2026-09-23.json.\n\n06 — الفئة السكانية الأخرى\nالمحتالون Valve دعونا ننتقل إلى: التعداد السكاني الكامل 51,732\n\nقائمة ثانية مستقلة — حالات الاحتيال التي تم تأكيدها من قبل المجتمع — تمت مقارنتها بنفس واجهة برمجة التطبيقات (API) الرسمية.\n\nيمكن القول إن فئة «المتفرغين» في عالم الأتمتة مجرد أشخاص عاطلين عن العمل وغير مؤذيين. أما الفئة الثانية فلا يمكن وصفها بذلك. SteamRep هي قاعدة بيانات قديمة لتقييم سمعة الأعضاء في المجتمع؛ فالحساب الذي تم وضع علامة عليه محظور تم إثبات أنه محتال من قبل ذلك المجتمع، مع وجود أدلة موثقة من الضحايا وسجلات محادثات المعاملات. وقد أجرينا إحصاءً لـ 100% جميع 51,732 ملفات تعريف تحمل حالة «محظور» مقابل واجهة برمجة التطبيقات (API) الرسمية لموقع Steam (ISteamUser/GetPlayerBans/الإصدار 1) — ولم يتم احتساب سوى العقوبات التي تتناول عمليات الاحتيال. فالحظر VAC يُفرض على برامج الغش في الألعاب (برامج توجيه التصويب، وبرامج اختراق الجدران)؛ وهو لا يؤثر بأي شكل على المتداول ولا يُعد دليلاً Valve يُستند إليه في اتخاذ إجراءات بشأن الاحتيال، لذا لا يُحتسب ضمن إجراءات مكافحة الاحتيال.\n\nعلى مستوى إحصاء الحسابات 51,732 بأكمله، فإن 67.77% — 35,059 من المحتالين الذين تمت إدانتهم — لا يحملون أي حظر متعلق بالاحتيال من Valve: لا يزال بإمكانهم إجراء المعاملات، وإرسال طلبات الصداقة إلى ضحايا جدد، وإرسال الرسائل. ولم يُفرض حظر على التداول أو حظر من المجتمع إلا على 32.23% حسابًا فقط، أما حظر التداول — وهو الإجراء الوحيد الذي يمنع فعليًّا نقل المخزون — فيُطبق على 18.81% حسابات فقط (9,731 حساب). كما أن 12.81% آخرين (6,627 حساب) خضعوا لـ VAC حظرًا أو حظرًا من اللعبة بسبب الغش داخل اللعبة فقط، في حين ظلوا خالين تمامًا من أي قيود في Steam عمليات التداول.\n\nالمحتالون المؤكدون، بناءً على ما إذا كان Valve قد فرض حظرًا متعلقًا بالاحتيال (إحصاء شامل)\n\nجميع 51,732 SteamRep-الحسابات المحظورة، مصنفة حسب ما إذا كان Valve قد فرض حظرًا متعلقًا بالمجتمع أو بالتجارة. تم استبعاد VAC وحالات الحظر المتعلقة بالألعاب — فهي لا تتعلق بالاحتيال. مرر المؤشر فوق العناوين لمعرفة الأعداد.\n\n0%\n18%\n35%\n53%\n70%\nNo scam-relevant ban\nCommunity or trade ban\n0%\n6%\n13%\n19%\n25%\nCommunity ban\nTrade / economy ban\nVAC (not fraud)\nGame ban\n51,732SteamRep — تم تدقيق الملفات الشخصية المحظورة — 100% إحصاء شامل\n35,059لا يوجد حظر متعلق بالاحتيال (67.77%)\n18.81%تطبيق الحظر التجاري الذي يضع حداً لعمليات الاحتيال (9,731)\n32.23%واجهت الحصة Valve حظرًا مجتمعيًّا أو تجاريًّا (16,673)\n\nSteamRep هي قاعدة بيانات للسمعة تابعة لجهة خارجية ويتم تقييمها من قبل المجتمع، وليست قرارًا صادرًا عن Valve — وهذا هو بيت القصيد: أدلة خارجية، تُقاس مقارنةً بما فعلته Valve نفسها. تمت مقارنة جميع الملفات الشخصية 51,732 المحظورة من التصدير القياسي مباشرةً مع ISteamUser/GetPlayerBans/v1. يُقصد بعبارة «ذات صلة بالاحتيال» الحظر المفروض على المشاركة في المجتمع أو على الأنشطة الاقتصادية/التجارية؛ ويُحسب كل من الحظر VAC (12.81%) وحظر اللعب (3.86%) بشكل منفصل لأنهما يتعلقان بالغش وليس بالاحتيال. مجموعة بيانات التدقيق الكاملة: steamrep_steam_bans.csv.\n\nمجموعتان، نتيجة واحدة\n\nهؤلاء ليسوا نفس الأشخاص، ولا يتعلق الأمر بنفس السلوك. ففي الحالة الأولى، هناك عشرة ملايين حساب آلي؛ أما في الحالة الثانية، فهناك ثلاثة وخمسون ألف محتال تم البت في قضاياهم. وما يجمع بينهما هو شكل النتيجة: تُترك تسعة من كل عشرة حسابات زراعية دون أن يُمسّ بها، ولا يتعرض أكثر من ثلثي (67.77%) المحتالين المؤكدين لأي عقوبة تتعلق بالاحتيال. إن الحظر المجتمعي Valve يُفرض بحرية ويقيد الوصول إلى المنتديات والملفات الشخصية، وليس التداول. زر الإبلاغ، وقاعدة بيانات السمعة، والحظر الذي يوقف عمليات الاحتيال: كلها موجودة، لكنها لا تُستخدم بالشكل الكافي. ضع ذلك جنبًا إلى جنب مع حالات الرفض المؤرشفة في الملف الرئيسي، حيث تقوم الشركة نفسها بحذف حساب واحد نهائيًّا وتستشهد بالاستخدام التجاري والأتمتة كسبب — فهذه الفقرة ليست خاملة، بل هي موجهة بشكل واضح.\n\n07 — ثغرة الحساب $5.00 واختطاف الحسابات\nالتدقيق التجريبي لحسابات «100,000»: شبكات الروبوتات ليست حسابات مجانية يمكن التخلص منها\n\nمنطق أخذ العينات الإحصائية والإثبات الرياضي: لماذا يؤدي أخذ أي قيمة أخرى لـ 100,000 إلى الحصول على النتيجة نفسها تمامًا.\n\nكان الدفاع الرئيسي الذي ساقه Valve أمام الهيئات التنظيمية وهيئات حماية المستهلك هو أن عمليات الاحتيال الآلية و«الزراعة» تتم عبر حسابات مؤقتة ومجانية «يمكن التخلص منها» يتم حظرها بسرعة. وبموجب القواعد المنشورة لـ Valve، فإن الحساب هو محدود إلى أن تنفق ما لا يقل عن $5.00 دولار أمريكي في متجر Steam، مما يمنعه من إجراء المعاملات، وتلقي طلبات الصداقة، والاستفادة من ميزات واجهة برمجة التطبيقات (API). وقد قمنا بالتحقق من صحة هذا الادعاء مباشرةً من خلال اختبار حالة تحقيق الدخل لعينة تمثيلية ودقيقة رياضيًا من 100,000 تم حظر Steam حسابًا مستمدة من مجموعة بيانات التعريف الخاصة بملفنا 1,182,811.\n\nبروتوكول أخذ العينات (SRSWOR)\n100,000 شريحة غير متحيزة\n\nمستمد من ن = 1,182,811 حسابًا فريدًا محظورًا Steam باستخدام «العينة العشوائية البسيطة دون إعادة» عبر مولد أرقام عشوائية (PRNG) متجانس تشفيرياً. وكان لكل حساب احتمال إدراج متطابق يبلغ P = n / ن ≈ 8.45%، مما يؤدي إلى القضاء التام على تحيز البقاء على قيد الحياة وتحيز النشاط.\n\nالبرهان الرياضي\nهامش الخطأ < ±0.4%\n\nتطبيق صيغة تصحيح العدد المحدود للسكان (FPC) عند 99% فترة الثقة (Z = 2.576):\nMoE = Z × √[p(1-p)/n] × √[(N-n)/(N-1)] ≈ ±0.39%\n\nقابلية التكرار\nلماذا أي رقم يبلغ 100 ألف يعطي نفس النتيجة\n\nنظرًا لأن هامش الخطأ يقع ضمن ±0.4% عند مستوى ثقة 99%، من المؤكد رياضيًا أن أي عينة أخرى تُؤخذ بشكل مستقل من الحساب 100,000 ستقع ضمن النطاق 63.06% ± 0.39% (من 62.67% إلى 63.45%). تعكس العينة مجمل السكان المحظورين البالغ عددهم 1.18 مليون نسمة.\n\nتدحض نتائج التدقيق تمامًا حجة «الروبوتات التي تُستخدم لمرة واحدة». ومن بين 100,000 حسابًا خضعت للتدقيق عبر واجهة ملف تعريف XML القديمة الخاصة بـ Steam: الحسابات 61,490 (63.06% من الحسابات المصنفة) هي حسابات غير محدودة (مدفوعة) أنفقت ما لا يقل عن $5.00 على Steam. فقط 36,021 (36.94%) هي حسابات مجانية محدودة، في حين أن 2,489 كانت حسابات غير مُهيأة أو خاصة.\n\n100,000 الحسابات المحظورة: المدفوعة ($5+ الإنفاق في المتجر) مقابل الحسابات المجانية ذات الوضع المحدود\n\nتدقيق تجريبي لـ 100,000 حسابات محظورة تم اختيارها عشوائيًا. وقد اجتاز أكثر من 63% منها بوابة Valve المالية المدفوعة. مرر المؤشر فوق الأرقام لمعرفة العدد.\n\n0%\n16%\n33%\n49%\n65%\nNon-limited (Paid ≥ $5.00)\nLimited (Free < $5.00)\n100,000العينة السكانية (SRSWOR، N=1.18 مليون)\n63.06%الحسابات المدفوعة غير المحدودة (حسابات 61,490)\n±0.39%هامش الخطأ في فترة الثقة 99%\n~745,800عدد الحسابات المدفوعة المستنتجة من مجموعة البيانات المحظورة البالغ عددها 1.18 مليون\nالواقع الهيكلي: تصفية الحسابات على نطاق صناعي\n\nلماذا قد يكون 63% من الحسابات المحظورة التي شملتها العينة حسابات مدفوعة أنفقت أموالاً حقيقية في متجر Valve؟ فمشغلو شبكات الروبوتات لا ينفقون الملايين من أموالهم الخاصة على حسابات يمكن التخلص منها. وتسلط هذه النسبة الضوء على حجم الحسابات المخترقة والمستولى عليها تتدفق عبر النظام البيئي.\n\nيمكن ملاحظة هذا المقياس بشكل مباشر على المنصات غير الرسمية: في أسواق مثل FSB Market (اسم مستعار؛ الاسم الأصلي غير مذكور هنا)، عبر 550,000 Steam حسابات (سجلات الاختراق، عمليات التصيد الاحتيالي، هجمات \"تعبئة بيانات الاعتماد\") معروضة للبيع بشكل نشط في أي لحظة (phishdestroy.io/live-intel). يقوم السوق بالتحقق من هوية المشترين والبائعين باستخدام معرّف OpenID الخاص بـ Valve، وهو Steam، ولا يقوم أي من FSB Market ولا المنتدى المرتبط تم حظره بواسطة مرشح الروابط الخاص بـ Valve.\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\nوفقًا لما هو منصوص عليه في القسم 06، لا تقوم Valve بإزالة هذا النشاط الاحتيالي بشكل استباقي: 67.77% من المحتالين الذين تم تأكيدهم من قبل المجتمع لا يواجهون أي حظر بسبب الاحتيال على Steam، ويظل 88.97% من أسطول الأتمتة بمنأى تمامًا عن أي تدخل. فالحسابات تتحرك بحرية، وتقوم بالمصادقة عبر واجهات برمجة التطبيقات (API) الرسمية، وتقوم بالتداول عبر النظام البيئي دون أي عقاب يذكر.\n\nرسم تخطيطي لأدلة الطب الشرعي وبنية إنفاذ القانون\nتدفق تفاعلي من 10.88 مليون حساب تم مسحها ضوئيًا إلى 100 ألف شريحة تجريبية و53.5 ألف محتال مؤكد · انقر على الروابط لفحص الأدلة الأولية\nالمستوى 01 · 10.88 مليون جرد لأسطول المركبات الآلية\nأكبر مجموعة من الروبوتات التي تعرّف عن نفسها على Steam، مرت تباعًا عبر واجهة برمجة التطبيقات (API) الرسمية للحظر الخاصة بـ Valve. وهذا يثبت أن أساطيل الروبوتات التجارية تعمل بحرية تامة على 88.97%، في حين تدفع عشرات الملايين كرسوم دخول.\n9,680,599 88.97% نشط ولم يُمسّ\nالحسابات التي تستخدم برامج آلية ولا يوجد في سجلها أي حظر من أي نوع.\nملف JSON الخام لبيانات التعداد (1.2 كيلوبايت) ↗راجع القسم 01 ↗\n$26,802,495 الحد الأدنى لإيرادات المتاجر المباشرة\nتم جمعها بواسطة Valve من 5,360,499 عضو غير محدود بعد تجاوز الحد الأدنى $5.00 للدخول.\nتدقيق اقتصاديات البطاقات ↗Valve $5 الأسئلة الشائعة حول القواعد ↗\n1,200,011 11.03% المجموعة الفرعية المُعلَّمة\n99.8% لا تُفرض عليها سوى قيود تجميلية على مستوى المجتمع؛ بينما تظل التداولات مفتوحة على 99.95% من الحسابات.\nتفصيل أنواع الحظر ↗قاعدة البيانات المحظورة (60.4 ميغابايت) ↓\nالمستوى 02 · 100,000-تدقيق العينات التجريبية للحسابات (N = 1,182,811)\nشريحة تمثيلية SRSWOR تم تقييمها عبر نقاط نهاية XML قديمة. هامش الخطأ المثبت رياضيًا < ±0.4% عند فاصل ثقة 99%. وهذا يدحض الادعاء القائل بأن الروبوتات المحظورة هي حسابات مجانية يمكن التخلص منها.\n61,490 (63.06%) الحسابات المدفوعة غير المحدودة ($5+ الإنفاق)\nتمثل أكثر من 63% من الحسابات المحظورة معاملات مدفوعة. ويُقدَّر عدد الحسابات المدفوعة في مجموعة الحسابات المحظورة بنحو 745,800 (مع حد أدنى للدخول يبلغ $3.73M+).\nنتائج محدودة بتنسيق CSV (2.1 ميغابايت) ↓تقرير الطب الشرعي الخاص بقضية 100 ألف ↗\n36,021 (36.94%) الحسابات المجانية المحدودة (< $5.00)\nالأقلية من الحسابات المحظورة التي تنطبق عليها مواصفات «الروبوت القابل للتخلص منه» التي حددها Valve. أما حسابات 2,489 فكانت غير مهيأة أو خاصة.\nعينة من 100 ألف شريحة بتنسيق CSV (8.5 ميغابايت) ↓تحليل الإنفاق MD ↗\n34.67% مقابل 63.93% تدقيق تعقيم الملفات الشخصية\nValve قام بمسح الأسماء المستعارة واستبدالها بـ SteamID64 الأصلي في 34,673 حسابًا، لكنه ترك الأسماء المخصصة والصور الرمزية كما هي تمامًا في 63,928 حسابًا محظورًا.\nقسم التعقيم ↗نظرة عامة على خارطة الطريق ↗\n34.59% الإرث الحسابات القديمة (التي تم إنشاؤها في الفترة 2003–2019)\nتم تسجيل أكثر من ثلث الحسابات المحظورة منذ ما بين 5 إلى 20+ سنة، مما يثبت حدوث عمليات اختطاف حسابات على نطاق صناعي استهدفت لاعبين قدامى.\nالتسلسل الزمني للأعمار ↗حالات رفض الدعم ↗\nالمستوى 03 · 51,732 SteamRep إحصاء المحتالين المؤكدين\nإحصاء شامل 100% للمحتالين الذين تم البت في قضاياهم من قبل المجتمع، مع سجلات الدردشة الخاصة بالضحايا وأدلة المعاملات، تمت مقارنتها مع واجهات برمجة التطبيقات (API) الرسمية Steam الخاصة بالحظر. يثبت فشلًا منهجيًّا في إنفاذ القوانين.\n35,059 (67.77%) عدم فرض أي حظر بسبب الاحتيال (إفلات تام من العقاب)\nأكثر من ثلثي المحتالين الذين تم التحقق منهم لا يخضعون لأي حظر على المشاركة في المجموعة أو على التداول من Valve. وهم قادرون تمامًا على التداول وإضافة ضحايا.\nSteamRep حظر واجهات برمجة التطبيقات (2.6 ميغابايت) ↓SteamRep تقرير التدقيق ↗\n9,731 (18.81%) الاقتصاد / الحظر التجاري\nالعقوبة الوحيدة التي توقف تصفية المخزون. وهي موجودة لدى أقل من خمس المحتالين المؤكدين.\nSteamRep المصدر (2.1 ميغابايت) ↓راجع القسم 06 ↗\n6,627 (12.81%) حالات حظر الغش غير ذات الصلة (VAC فقط)\nتم حظرهم بسبب استخدام برامج التصويب الآلي (aimbots) وبرامج اختراق الجدران (wallhacks) في الألعاب، في حين تظل قدراتهم في مجال التداول Steam والتصيد الاحتيالي 100% نشطة.\nVAC تحليل عدم الصلة ↗الجدول الزمني للأمن ↗\nالمستوى 04 · تشويه مواقع الويكي واختراقات البنية التحتية في أغسطس 2026\nتشمل حزمة الأدلة حالات تشويه الوثائق الداخلية الخاصة بالمطورين، وقمع محرري المجتمع، وفشل الإجراءات الأمنية المحيطة غير المُحكمة.\n1,200+ المحررون سجلات تعارضات ويكي VDC\nتم حظر محرري المجتمع الذين كانوا يحاولون إصلاح روابط التصيد الاحتيالي وقوالب الرسائل غير المرغوب فيها بشكل منهجي بواسطة المرشحات الآلية، في حين تجاهل الموظفون Valve التحذيرات.\nتقرير النزاعات الروسية (127 كيلوبايت) ↗تقرير التصنيف (66 كيلوبايت) ↗\n12 تيرابايت غير مصدق تسرب الأصول في أغسطس 2026 (CWE-284)\nValve استضافت 12 تيرابايت من الكود الداخلي وإصدارات النماذج الأولية على نقطة نهاية عامة مفتوحة دون مصادقة لمدة أسابيع.\nValve ملف عدم الكفاءة (43 كيلوبايت) ↗أرشيف الأدلة ↗\nاختراق أمني في شركة «سيفا لوجيستيكس» أغسطس 2026: تسرب البيانات الشخصية للعملاء\nتسربت أسماء وعناوين وأرقام هواتف مشتري «Steam Deck» الأوروبيين من الشريك اللوجستي لـ «Valve»، مما أدى إلى اندلاع موجات من عمليات التصيد الاحتيالي.\nسجل الحادث ↗سجل الإنفاذ ↗\n\nتشويه عينة: banned_100k_slice.csv (100,000 حسابات). نتائج المراجعة: slice_100k_limited_results.csv. التقرير التحليلي الكامل: BANNED_100K_FORENSIC_ANALYSIS.md.\n\n08 — الطريقة والحدود\nكيف فُهم هذا، وما الذي لا يدعيه\n\nثلاث مجموعات سكانية عامة، وواجهة برمجة تطبيقات (API) عامة واحدة، وعملية أخذ عينات إحصائية دقيقة.\n\nالتنفيذ وبيانات الاعتماد\n\nتم تنفيذ تعداد ASF، أي 100,000-حساب SRSWOR شريحة وSteamRep عملية التحقق المزدوج تم تنفيذهما بواسطة PhishDestroy مشاركًا باستخدام حساباتهم الخاصة Steam ومفاتيح واجهة برمجة التطبيقات (Web API) الخاصة بهم، كجزء من عمل التحالف العام لحظر التصيد الاحتيالي والخداع. لا يمتلك مؤلف هذا التقرير أي مفتاح واجهة برمجة تطبيقات الويب (Steam) ولم يقم شخصيًا بإجراء أي مسح مباشر. وقد تمت عمليات التجميع والتجزئة والتحقق والنشر بناءً على النتائج التي توصل إليها المشاركون.\n\nالسكان\tمن أين جاءت\tما تمت قراءته\nأعضاء ASF\n10,880,610\tقائمة الأعضاء العامة لمجموعة المجتمع ArchiSteamFarm Steam. تُظهر صفحة مجموعة Steam وجود 5,360,499 عضوًا (الحسابات غير المقيدة فقط)؛ أما قائمة الأعضاء التي أعادتها واجهة برمجة التطبيقات (API) فقد أظهرت 10,880,610 سجلًا إجماليًّا، بما في ذلك الحسابات المقيدة. يتم الانضمام إلى المجموعة تلقائيًا عند التشغيل لأول مرة ما لم يقم المستخدم بتعطيل إعداد الانضمام الافتراضي إلى المجموعة صراحةً في التكوين (AutoJoinSteamGroup / الإحصائيات)، مما يعني أن قائمة الأعضاء تضم مجموعات الروبوتات التجارية، ومستخدمي البطاقات غير النشطين، واللاعبين العاديين الذين تركوا الخيار الافتراضي مفعَّلاً.\tGetPlayerBans لكل عضو (إشارات الحظر)؛ GetPlayerSummaries حسب تواريخ الإنشاء والبلد. تم تجميعها في مجموعات مكونة من 100 معرّف، مع إزالة التكرارات باستخدام SteamID64.\n100 ألف حساب محظور SRSWOR شريحة\n100,000\tعينة تمثيلية تم سحبها عشوائيًا بشكل متجانس دون إعادة من مجموعة الحسابات المحظورة 1,182,811 ($P = 8.45\\%$). يؤدي تصحيح العينة المحدودة إلى هامش خطأ يبلغ $\\pm 0.39\\%$ عند مستوى ثقة 99% ($Z = 2.576$).\tتحقيق الدخل وحالة الحساب المحدود (isLimitedAccount) تم تدقيقها عبر واجهة ملف تعريف XML القديمة لـ Steam (?xml=1) عبر مسارات وكيلة موزعة. يؤكد حالة الدفع 63.06%.\nSteamRep محتالون\n51,732\tإجراء إحصاء شامل لـ 100% لجميع الملفات الشخصية التي تحمل علامة «محظور» في قاعدة بيانات سمعة المجتمع SteamRep (إجمالي 51,732 ملف شخصي). لم يتم تطبيق أي عينة أو تصفية.\tISteamUser/GetPlayerBans/v1 بالنسبة لجميع الحسابات 51,732، بعد إجراء مقارنة تقاطعية مع الحالة SteamRep. يؤكد أن 67.77% خالٍ من أي حظر متعلق بالاحتيال.\nما يُدّعى\n\nالمعدلات التجريبية والتقديرات المحددة إحصائيًا فقط. ضمن مجموعة الحسابات الآلية، لا يخضع 88.97% لأي حظر؛ أما المجموعة الفرعية المحظورة فتتركز في الفترة الأخيرة (70% منذ عام 2020). في التدقيق التجريبي لحسابات 100,000، هناك 63.06% من الحسابات المحظورة مدفوعة (غير محدودة)، مع هامش خطأ مثبت رياضيًا أقل من ±0.4%. من بين 51,732 من المحتالين المؤكدين، لا يخضع 67.77% لأي حظر متعلق بالاحتيال. كل رقم قابل للتكرار من واجهة برمجة تطبيقات الويب الخاصة بـ Valve.\n\nما لم يُدّعى\n\nلا يحتوي الحظر من النوع Steam على حقل «السبب»، لذا لا يُعزى أي حظر هنا إلى سبب محدد. ولا تُعد عضوية المجموعة دليلاً على أن الحساب هو روبوت آلي: نظرًا لأن ASF تتيح الانضمام إلى المجموعات بشكل افتراضي ما لم يتم إلغاء تحديد الخيار يدويًّا، فإن المجموعة تضم مزرعات حسابات تجارية متعددة إلى جانب حسابات شخصية للاعبين العاديين وهواة اللعبة. يتم الإبلاغ عن البلد من قبل المستخدم نفسه، ويُعد الإدراج تحت الرمز SteamRep قرارًا من المجتمع، وليس حكمًا قضائيًّا. ولا يتم ذكر اسم أي فرد.\n\nلماذا هذا مهم\n\nيحتوي Valve على نفس واجهة برمجة التطبيقات (API)، وقاعدة بيانات خاصة به، بالإضافة إلى أسباب الحظر التي لا يمكن لهذا الفحص رؤيتها. ويمكنه تشغيل هذا الاستعلام عبر كامل نطاق المعرّفات في غضون ثوانٍ. لم يسبق أن نشرت الجهة الوحيدة القادرة على إنتاج القياس الذي يتيح لطرف خارجي التحقق من ادعاء تطبيق الإجراء ضد رقم معين هذا القياس بدقة كاملة. هذا هو التقدير الخارجي، الذي يتم تقديمه حتى يمكن طرح السؤال مصحوبًا برقم محدد.\n\nاقرأ التالي: الاقتصاد القائم على البطاقات الذي تديره هذه الفئة السكانية → · دعم الوصول والسرقة → · الملف الكامل →",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "ما حجم شبكة الحسابات على Steam؟ أحصيناها بأنفسنا."
          },
          {
            "level": 2,
            "id": null,
            "text": "عشرة ملايين حساب، وتسعة من كل عشرة لم يتم المساس بها"
          },
          {
            "level": 3,
            "id": null,
            "text": "تنضم ASF إلى المجموعة من أجلك"
          },
          {
            "level": 3,
            "id": null,
            "text": "10,880,610 إجمالي عدد المشاركات"
          },
          {
            "level": 3,
            "id": null,
            "text": "88.97% نظيف"
          },
          {
            "level": 3,
            "id": null,
            "text": "من بين 10,880,610 حسابًا، كم عدد الحسابات التي تم استخدامها Valve"
          },
          {
            "level": 3,
            "id": null,
            "text": "ما دفعه هذا الأسطول بالفعل Valve لكي يكون موجودًا"
          },
          {
            "level": 2,
            "id": null,
            "text": "أين يقع مقر الأسطول"
          },
          {
            "level": 3,
            "id": null,
            "text": "الحسابات المحظورة حسب البلد المحدد"
          },
          {
            "level": 2,
            "id": null,
            "text": "حسابات حديثة، وليست متأخرات قديمة"
          },
          {
            "level": 3,
            "id": null,
            "text": "متى تم إنشاء الحسابات المحظورة"
          },
          {
            "level": 2,
            "id": null,
            "text": "عندما يتم تنفيذ Valve، فإن ذلك يتم خلال السنة الأولى"
          },
          {
            "level": 3,
            "id": null,
            "text": "كم كان عمر الحساب عندما تم فرض الحظر عليه"
          },
          {
            "level": 2,
            "id": null,
            "text": "عندما يعمل Valve، فإنه لا يوقف البوت"
          },
          {
            "level": 3,
            "id": null,
            "text": "ما هي الأسباب الحقيقية وراء حظر الأشخاص الذين يحملون الرمز 11%؟"
          },
          {
            "level": 2,
            "id": null,
            "text": "المحتالون Valve دعونا ننتقل إلى: التعداد السكاني الكامل 51,732"
          },
          {
            "level": 3,
            "id": null,
            "text": "المحتالون المؤكدون، بناءً على ما إذا كان Valve قد فرض حظرًا متعلقًا بالاحتيال (إحصاء شامل)"
          },
          {
            "level": 4,
            "id": null,
            "text": "مجموعتان، نتيجة واحدة"
          },
          {
            "level": 2,
            "id": null,
            "text": "التدقيق التجريبي لحسابات «100,000»: شبكات الروبوتات ليست حسابات مجانية يمكن التخلص منها"
          },
          {
            "level": 3,
            "id": null,
            "text": "100,000 شريحة غير متحيزة"
          },
          {
            "level": 3,
            "id": null,
            "text": "هامش الخطأ < ±0.4%"
          },
          {
            "level": 3,
            "id": null,
            "text": "لماذا أي رقم يبلغ 100 ألف يعطي نفس النتيجة"
          },
          {
            "level": 3,
            "id": null,
            "text": "100,000 الحسابات المحظورة: المدفوعة ($5+ الإنفاق في المتجر) مقابل الحسابات المجانية ذات الوضع المحدود"
          },
          {
            "level": 3,
            "id": null,
            "text": "الواقع الهيكلي: تصفية الحسابات على نطاق صناعي"
          },
          {
            "level": 2,
            "id": null,
            "text": "كيف فُهم هذا، وما الذي لا يدعيه"
          },
          {
            "level": 3,
            "id": null,
            "text": "ما يُدّعى"
          },
          {
            "level": 3,
            "id": null,
            "text": "ما لم يُدّعى"
          },
          {
            "level": 3,
            "id": null,
            "text": "لماذا هذا مهم"
          }
        ],
        "links": [
          "https://help.steampowered.com/en/faqs/view/71D3-35C2-AD96-AA3A",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/asf-ban-census-2026-09-23.json",
          "https://phishdestroy.io/steam_dossier/ar/VALVE_EVIDENCE_PACK/databases/steamrep_steam_bans.csv",
          "https://phishdestroy.io/live-intel/?category=steam",
          "https://phishdestroy.io/steam_dossier/ar/#proxy-bypass-explainer",
          "https://phishdestroy.io/steam_dossier/ar/card_economy.html",
          "https://phishdestroy.io/steam_dossier/ar/VALVE_EVIDENCE_PACK/databases/banned_archiasf_massive.csv",
          "https://phishdestroy.io/steam_dossier/ar/VALVE_EVIDENCE_PACK/databases/slice_100k_limited_results.csv",
          "https://phishdestroy.io/steam_dossier/ar/VALVE_EVIDENCE_PACK/reports/BANNED_100K_FORENSIC_ANALYSIS.md",
          "https://phishdestroy.io/steam_dossier/ar/VALVE_EVIDENCE_PACK/databases/banned_100k_slice.csv",
          "https://phishdestroy.io/steam_dossier/ar/VALVE_EVIDENCE_PACK/reports/STEAM_BANNED_LIMIT_ANALYSIS.md",
          "https://phishdestroy.io/steam_dossier/ar/VALVE_EVIDENCE_PACK/INVESTIGATION_OVERVIEW.md",
          "https://phishdestroy.io/steam_dossier/ar/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/ar/VALVE_EVIDENCE_PACK/reports/STEAMREP_VS_STEAM_AUDIT.md",
          "https://phishdestroy.io/steam_dossier/ar/VALVE_EVIDENCE_PACK/databases/SteamRep_Profiles_BannedCaution_2024.csv",
          "https://phishdestroy.io/steam_dossier/ar/security_timeline.html",
          "https://phishdestroy.io/steam_dossier/ar/VALVE_EVIDENCE_PACK/reports/russian_conflicts_report.json",
          "https://phishdestroy.io/steam_dossier/ar/VALVE_EVIDENCE_PACK/reports/classification_report.json",
          "https://phishdestroy.io/steam_dossier/ar/VALVE_EVIDENCE_PACK/reports/VALVE_INCOMPETENCE_REPORT.md",
          "https://phishdestroy.io/steam_dossier/ar/steam_evidence_archive.html",
          "https://phishdestroy.io/steam_dossier/ar/steam_enforcement_evidence.html",
          "https://phishdestroy.io/steam_dossier/ar/#insider-threat",
          "https://phishdestroy.io/steam_dossier/ar/"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ar/enforcement_audit.content.json",
      "export_json_sha256": "957fddab39b13dd090581fa637ce490cbcc4b5c848e70dcdbcd00e47fade8498"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ar/index.html",
      "language": "ar",
      "title": "ملف Steam: القواعد والمسارات والمساءلة",
      "source_url": "https://phishdestroy.io/steam_dossier/ar/index",
      "source_html_sha256": "1d9d76f5d383178c37d4ee7de0e0f7cad1ebd9681eaf8bfa4420addf10f6afc1",
      "exported_at": "2026-09-29T00:20:12.029Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "exhibit-gallery-section",
            "source": "https://phishdestroy.io/steam_dossier/ar/index#exhibit-gallery-section"
          }
        ],
        "raster_images_replaced": 2
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "index.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ar/index.pdf?v=print-20260929-v5",
        "sha256": "e772bdea229d1bb242cd38271af4d97c0547df5860c8f92061d7989914821408",
        "bytes": 1354834,
        "pages": 93
      },
      "integrity": {
        "signed_object": "index.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "index.content.json.asc",
        "digest_file": "index.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify index.content.json.asc index.content.json",
          "sha256sum -c index.content.json.sha256"
        ]
      },
      "content": {
        "text": "القسم 1 — موجز القضية\nالقاعدة. الرقم القياسي. الأسئلة التي لم تُجب عليها.\nالسياق وحدود المصدر\n\nستة استنتاجات، يرتبط كل منها بسجل عام مؤرخ. وتتبع الأقسام التفصيلية الترتيب نفسه: السجل الفني (الجزء أ)، وسجل القواعد والإنفاذ (الجزء ب)، والأطر القانونية (الجزء ج)، ثم الملاحق التي تتضمن المستندات الأساسية.\n\nستة استنتاجات. يربط كل منها قاعدة مكتوبة بسجل مؤرخ وبسؤال يمكن للأدلة أن تختبره.\n\n1. مضيفات المصادقة ذات المجالات المنفصلة — 44 مسارًا · 26 زوجًا مقسّمًا\n\nسجلات المسجلين في برنامج المساعدة المباشرة 44 منصة تُجري عملية المصادقة عبر نطاق منفصل قابل للتسجيل. وهناك خمسة مسارات أخرى قيد التحقق، في انتظار تحديد موعد لبرنامج RDAP؛ ومن شأن ترقيتها أن يرفع العدد الإجمالي إلى 47. وقد تم استبعادها من العدد 44 ومن جدول الأعمار. — 27 مع ملف أدلة منشور لكل مسار و17 حالة أُضيفت من عملية الجمع اليدوي، وهي مدرجة بشكل منفصل. في 26 زوجًا من المرشحات المقسمة النطاق الرئيسي هو محجوب في مرشح الروابط Steam، في حين أن الخادم الوكيل الذي يحمل معلومات تسجيل الدخول الخاصة به غير محظور. هذه ليست نطاقات مؤقتة: موقع csgogem.com محظور بينما api.csgem.com، وقد تم تسجيل الخادم الذي يحمل اسم المستخدم Steam منذ مارس 2014 — 12 سنة و6 أشهر. Valve يتلقى اسم المضيف هذا في كل طلب OpenID، ويعرضه للمستخدم على صفحة تسجيل الدخول الخاصة به. يرد الجدول الكامل، مع أعمار كل مسار ومصدره، في القسم 3.\n\nاتبع المسار →\n2. عام 2016: تم تسمية الآلية، وتحديد الموعد النهائي\n\nفي 13 يوليو 2016، أوضح Valve علنًا كيف استخدمت مواقع المقامرة Steam OpenID وحسابات التداول الآلية، وحددت إخطارات محاميه المؤرخة في 20 يوليو 2016 مهلة مدتها عشرة أيام. ولم يتم نشر أي سجل إنفاذ خاص بكل مشغل منذ ذلك الحين. وبعد مرور عشر سنوات على إصدار ذلك الموعد النهائي، لا تزال الآلية المذكورة نفسها قيد الاستخدام على مضيفات المصادقة ذات النطاقات المنفصلة التي لم تُرجع أي حظر من «Link Filter» على 2026-09-21.\n\nاقرأ الرسالة المفتوحة الموجهة إلى WSGC →\n3. الترابط بين الأجهزة، على ورق رسمي يحمل شعار مكتب المحاماة\n\nفي المراسلات الواردة هنا، وصف محامي Valve وجود ارتباط على مستوى الجهاز يربط جهازًا واحدًا بحسابات متعددة — وهي إمكانية كان فريق الدعم Steam قد أخبر المستخدمين سابقًا أنها غير ممكنة من الناحية التقنية. والسؤال الذي لا يزال مطروحًا هو: ما هي السجلات المتعلقة بالأجهزة التي تحتفظ بها Valve، وعلى أي أساس يُرفض السماح لأصحاب الحسابات بالوصول إليها؟\n\nاقرأ المذكرة →\n4. ردان بشأن الوصول إلى البيانات. أحدهما حجب البيانات، والآخر سربها.\n\nأكتوبر 2025: رد محامي Valve على طلب بموجب المادة 15 بملحق من 830 صفحة، حيث تم طمس الأجزاء المحجوبة بالطلاء فوق النص بدلاً من حذفها — 902,270 حرفًا العودة باستخدام أداة استخراج قياسية، بما في ذلك معرّفات الجهات الخارجية التي كانت تلك الأشرطة موجودة لحجبها. والمادة 15(4) هي السبب وراء وجود تلك الأشرطة. سبتمبر 2026: تم إغلاق التذكرة رقم HT-2YBP-F7JP-D4VB بعد ثلاثة أيام مع تضمين رابط إلى صفحة «بيانات الحساب» في خدمة العملاء الذاتية — دون تقديم أي بيانات أو ذكر أي أساس قانوني. ولم تكن المدة المحددة بشهر واحد بموجب المادة 12(3) قد انقضت حتى وقت النشر؛ والاعتراض هو على جوهر الموضوع.\n\nاقرأ فحص التنقيح →اقرأ سجل التذكرة →\n5. السوق فوق سقف Steam\n\nSteam يحدد سقف الإدراج في البورصة عند حوالي $1,800. عبر خمسة أسواق في لقطة قديمة (23 سبتمبر 2026)، 248 فئة من عناصر CS2 تم تسعيرها فوق ذلك الحد الأقصى من قِبل اثنين أو أكثر منهم بشكل مستقل، و جميع الـ248 غائبون عن Steam؛ يبدأ سعر كتاب «Dragon Lore» الجديد من المصنع من $10,941 عبر 389 نسخة مدرجة في جميع البورصات الخمس (الرقم الخاص بـ CSFloat فقط في القسم 13، من لقطة 20 سبتمبر، هو $10,623.95 عبر 62 عرضًا). يتطلب البيع بهذه الأسعار منصة خارجية، في حين أن نقل العناصر لا يزال يتم عبر Steam.\n\nتابع السعر والتحويل →\n6. القاعدة واضحة؛ أما سجل التدقيق فليس كذلك\n\nتنص اتفاقية الاشتراك على أن Steam مخصصة للاستخدام الشخصي غير التجاري، وتمنع الاستغلال التجاري باستثناء ما يُسمح به صراحةً، وتحظر استخدام البرامج النصية والروبوتات، وتسمح بإنهاء الحساب. وقد طبّق Valve هذه الصيغة على مشغلي مواقع المقامرة في عام 2016. بشكل منفصل، وفقًا لحساب CSFloat الهندسي، تم إغلاق Valve IEconItems_730/GetPlayerItems في عام 2017، تم حجب الوصول العام إلى معرّفات العناصر الأصلية (لم يتم العثور على سجل التغييرات Valve).\n\nضع القاعدة بجانب الشبكة →\n2016 / طلب خطي 10 أيام\nالموعد النهائي الوارد في إخطارات المحامي الصادرة في يوليو 2016 إلى مواقع المقامرة. رسالة مفتوحة إلى لجنة المقامرة في ولاية واشنطن (WSGC): البند 2.\n2017 / سجل التدقيق العام تم إغلاق حق الوصول إلى معرّف الهوية\nيسجل CSFloat فقدان معرّفات العناصر الأصلية.\nالمراسلات القانونية الترابط بين الأجهزة\nجهاز واحد مرتبط بعشرات الحسابات المسروقة.\nسجل المسارات تم حظره، ولا يزال يحاول تسجيل الدخول\nالقاعدة: يحظر بيان Valve الصادر عام 2016 إدارة أي نشاط متعلق بالمقامرة على Steam OpenID. السجل: يضم «Link Filter» 26 نطاقًا رئيسيًّا، في حين أن الخادم الذي يستضيف حساب تسجيل الدخول Steam لكل منها لا يزال قيد التشغيل — وقد استمر تشغيل خادم موقع csgogem.com لمدة 12 سنة و6 أشهر.\nالقسم 2 — رسالة مفتوحة\nرسالة مفتوحة إلى لجنة المقامرة بولاية واشنطن\n\nتحولت العشرة أيام إلى عشر سنوات. لم يتم الرد على السؤال الذي وجهته اللجنة في عام 2016 إلى Valve بتقديم سجل تفصيلي لكل مشغل على حدة؛ وتطلب هذه الرسالة إعادة فتح الملف.\n\nنظام الإذاعة الداخلية · لجنة المقامرة بولاية واشنطن\n\nتحولت العشرة أيام إلى عشر سنوات.أعد فتح السجل.\n\nإلى لجنة المقامرة بولاية واشنطن:\n\nفي عام 2016، طلب المدير ديفيد تروجيلو من شركة Valve أن توضح الإجراءات التي اتخذتها لوقف استخدام «السكينز» Steam في المقامرة. واجه كريس ستيرنز، الذي كان رئيسًا للجنة آنذاك، واللجنة نفسها صناعة قائمة على العناصر الصادرة عن Valve وعمليات التحويل Steam. وقد ترك كلا الرجلين مناصبهما في اللجنة منذ ذلك الحين. ولم تنتهِ صلاحية السؤال الذي طرحاه على Valve.\n\nأمهل المستشار القانوني العام لـ Valve، كارل كواكينبوش، مشغلي المقامرة بعشرة أيام لوقف الاستخدام التجاري لحسابات Steam. وفي ردها الموجه إلى لجنتكم في أكتوبر، نفت شركة Valve تيسير أنشطة المقامرة، وأفادت بأنها أرسلت خطابات إنذار إلى أكثر من أربعين موقعًا، وأنها عطلت الحسابات المرتبطة بها. كما دافعت عن الحفاظ على خدمة التداول Steam وخدمة OpenID، بحجة أن هاتين الخدمتين تعودان بالنفع على العملاء ومطوري الألعاب. كان ذلك إعلانًا عن السيطرة. وهو يستحق أن يُختبر، لا أن يُقابل بالخضوع.\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\nفي تقييمنا، لم تثبت إجابة Valve أن الإجراءات التنفيذية التي اختارتها تتناسب مع حجم الشبكة التي وصفتها. فالرسالة التهديدية الموجهة إلى أحد المشغلين تختلف تمامًا عن الحظر الدائم لحسابات Steam، والبنية التحتية للتداول، ومسارات المصادقة التي تتيح سير العمل. وتشير التقديرات المعلنة إلى أن حققت «CS:GO Lounge» وحدها حجم رهانات تجاوز $1 مليار خلال عام 2016؛ وهذا تقدير خارجي لحجم الرهانات، وليس إيرادات Valve، وقد تم لاحقًا إغلاق نشاط المراهنات على الجلد الذي كان يقدمه الموقع في الأصل. وقد جعل حجم هذه الأنشطة من الضروري اتخاذ إجراءات إنفاذ يمكن التحقق منها.\n\nاليوم، من إنتاج Valve اتفاقية المشترك محفوظ 2026-09-21 ↗ يفرض قيودًا على الاستغلال التجاري باستثناء الحالات التي يُسمح فيها بذلك صراحةً، ويحظر بشكل منفصل أشكالًا محددة من الأتمتة. إن سجل المسارات القديم السجلات التي تُعلن عن مضيفي OpenID للخدمات الخارجية؛ openid.realm و openid.return_to هي حقول تُرسل إلى Steam، وليست أسرارًا تُخفى عنها. إن فحوصات تصفية الروابط تُظهر الحالات التي تم فيها تحذير عنوان رئيسي دون تحذير مضيف تسجيل الدخول المرتبط به. ولا يمكن لنتيجة التصفية وحدها أن تثبت أن Valve قد سمح بتسجيل الدخول أو أن روبوتًا معينًا قد تجنب حظر الحساب. وهذا يثبت أن التحذير الذي يظهر على الصفحة الرئيسية لا يمكن اعتباره حلاً شاملاً لمسألة الوصول.\n\nكما أن وجود وظائف تداول ووظائف OpenID مفيدة وقانونية Steam لا يمكن أن يجيب عما إذا كان المشغلون المحظورون قد استُبعدوا فعليًّا أم لا. فقواعد Valve نفسها تسمح باستثناءات صريحة. وإذا اعتمدت Valve على هذا التمييز، فينبغي للجنة أن تطلب منها تحديد الترخيص، وضوابط الحسابات، ومعايير الإنفاذ المطبقة على الأعمال التجارية المتعلقة بـ«السكين»، والاستخدامات المحددة غير المتعلقة بالمقامرة التي استندت إليها في عام 2016. فمجرد احتمال وجود استخدام قانوني لا يُعد ردًا على الاستخدام المحظور الموثق.\n\nنطلب من اللجنة إعادة النظر في ملف عام 2016 وطلب تقرير مفصل لكل مشغل على حدة: ما هي الحسابات وروبوتات التداول التي تم تعطيلها بعد إرسال إشعارات العشرة أيام؛ وما إذا كانت الحسابات ذات الصلة أو مضيفي العودة قد خُصِّصت للمراقبة؛ وما هي الحسابات التي استعاد مشغلوها حق الوصول لاحقًا؛ ما هي الاستثناءات التي تم منحها؛ وما هي السجلات التي تدعم بيان Valve أمام اللجنة. نشر ما يسمح القانون للجمهور بالاطلاع عليه. مقارنة تلك السجلات بالمسارات الحالية وبتدخلات Valve اللاحقة، بما في ذلك OPSkins في عام 2018 محفوظ 2026-03-07 ↗.\n\nحدد الإشعار مهلة مدتها عشرة أيام في يوليو 2016؛ وتُعد مدة عشر سنوات فترة كافية للتأكد مما إذا كان قد تم تنفيذ ذلك أم لا. ينبغي أن تقارن اللجنة حسابات Valve لعام 2016 بالبنية التحتية التي لا تزال قابلة للملاحظة حتى اليوم.\n\nتحقيق \"ملف Steam\" · بيان عام، 20 سبتمبر 2026\n\nإشعار اللجنة لعام 2016 ↗ محفوظ 2026-05-20 ↗ · رد Valve لعام 2016 (نسخة من الوثيقة) ↗ · بيان OpenID الصادر عن Valve لعام 2016 ↗ محفوظ 2026-09-21 ↗ · الاتفاق الحالي Steam ↗ محفوظ 2026-09-21 ↗ · الجدول الزمني لبرنامج التبادل لعام 2016: القسم 11 →\n\nالجزء أ — السجل الفني · القسم 3\nالموقع محجوب. أما مسار تسجيل الدخول فليس كذلك.\n\n26 نطاقًا رئيسيًّا محجوبًا. وكيل المصادقة المرتبط بكل نطاق، ومدة تشغيله. هذه المضيفات المنفصلة الخاصة بالمصادقة ليست عناوين ثانوية عرضية — فكل واحدة منها هي وكيل المصادقة لـ Steam، حيث يقف بين المنصة ونقطة نهاية OpenID الخاصة بـ Valve، ويقوم بنقل عملية تسجيل الدخول التي لم يعد بإمكان النطاق المحظور نقلها علنًا. قام Valve بوضع «البوابة الأمامية» على «مرشح الارتباط». واستمرت عملية تسجيل الدخول في المرور عبر الوكيل: موقع csgogem.com محظور، و api.csgem.com تم تسجيله منذ مارس 2014 — اثنا عشر عامًا ونصف. في كل يوم من تلك الأيام، كان ذلك المضيف يرسل اسم المضيف الخاص به إلى نقطة نهاية OpenID الخاصة بـ Valve، وكان Steam يعرضه مباشرةً للمستخدم على صفحة تسجيل الدخول. Valve هو الجذع الذي تمر عبره كل واحدة من هذه المسارات؛ ولا يتعين عليه العثور عليها. هذا هو ما يقيسه هذا القسم: ليس ما إذا كان هناك تحذير أم لا، بل عدد السنوات التي يظل فيها المسار الواقع خلف التحذير مفتوحًا. يوجد في السجل 44 مسارًا ذات نطاقات منفصلة، 27 منها مصحوبة بملف أدلة منشور لكل مسار — كما هو موضح في الجدول أدناه. تابع مثالًا واحدًا، ثم قم بقياسها جميعًا.\n\nالشكل 3.1 — المساران، مرسومان.\n\nمنصة واحدة، لاعب واحد، طلبان يُرسَلان من نفس المتصفح. يعمل «Link Filter» الخاص بـ Valve على كلا الطلبين. فهو يوقف الطلب الذي يحتوي على رابط، ويسمح بمرور الطلب الذي يحتوي على معلومات تسجيل الدخول. كل ما يتم قياسه في هذا القسم هو عدد المرات التي يظل فيها المسار السفلي مفتوحًا.\n\nThe player\none browser, one session\nrollbit.com\nthe platform's main domain\nrbsnin.com\nseparate authentication host\nLINK FILTER\n✕ BLOCKED\nLINK FILTER\n✓ CLEAN\nsteamcommunity.com\nOpenID endpoint · signs in\nno route\nتم نشر الرابط في Steam — توقفطلب تسجيل الدخول — التذاكرالشيكات المحفوظة بتاريخ 19 و21 سبتمبر 2626\n\nكلا الطلبين مرئيان لـ Valve، ولا يتم تنفيذ سوى طلب واحد فقط. «مرشح الروابط» هو قائمة Valve، تتولى خدمة Valve التحقق منها. يحمل طلب OpenID اسم مضيف المصادقة نفسه إلى نقطة نهاية Valve، التي تعرضه مباشرةً على صفحة تسجيل الدخول. يظهر اسم المضيف في الطلب في كلتا الحالتين — والفرق يكمن في ما إذا كان يتم التعامل معه أم لا.\n\nمنصة واحدة. مساران مختلفان.ROLLBIT / الملاحظات المحفوظة\nالخطوة 5 / 5\n\nوصل الطلب إلى Steam. وصل المسار الذي تم رصده إلى نموذج تسجيل الدخول الخاص بـ Steam. ولم يكمل المؤلفون عملية تسجيل الدخول. ولم يؤد حجب الرابط الخاص بالنطاق الرئيسي إلى حجب هذا المسار الذي تم رصده المؤدي إلى النموذج.\n\n01 فحص مرشح الروابط\nالوجهةrollbit.comالنطاق الرئيسي للمنصة\nمرشح وصلة البخارالتحقق من الرابطنظام منفصل للتحذير من المخاطر في الوجهة\nالنتيجة المحفوظةالرابط محظور19 و21 سبتمبر 2026\n02 مسار تسجيل الدخول الذي تمت ملاحظته\nعلى الرصيفتسجيل الدخول باستخدام Steamتقوم المنصة بإرسال طلب OpenID\nخادم مصادقة منفصلrbsnin.comلا يوجد كتلة «تصفية الروابط» في الفحص المحفوظ\nSTEAMتم عرض نموذج تسجيل الدخوليظهر المضيف المطلوب في إشعار Steam\nافحص الملاحظات الأصلية المتعلقة بالالتقاط، وتاريخ التسجيل، وتفاصيل البروتوكول\nكيف يتم تطبيق Valve\nالنطاق الرئيسي: محظور\nالمستخدم\n→\nrollbit.com\n(النطاق الرئيسي)\n↓\nمرشح رابط STEAM — محجوب\n\"الرابط محظور!\" — تم الإبلاغ عنه باعتباره محتملًا أن يكون ضارًا\nأظهر موقع rollbit.com حجبًا بواسطة «Link Filter» عند 2026-09-19 و2026-09-21 (فحص غير مصدق؛ تم حفظ HTML الخام و SHA-256). سجل مرئي وقابل للتدقيق.\nما يحدث فعليًّا — المصادقة\nمضيف Auth: غير محظور\nالمستخدم\n→\nrollbit.com\n\"تسجيل الدخول باستخدام Steam\"\n↓\nإعادة التوجيه عبر مضيف مصادقة منفصل:\nrbsnin.comمرشح الروابط: نظيف\nمسجل 2026-09-18T09:34:52Z (Verisign RDAP)\n↓\nSteam إشعار صفحة تسجيل الدخول (2026-09-20):\n\"Note that rbsnin.com is not affiliated with Steam or Valve\"\nSteam يعرض هذا الإشعار من نطاق OpenID الخاص بالطلب الذي تلقاه.\n↓\nSteam نموذج تسجيل الدخول المُقدَّم للمضيف المنفصل\nلم يكمل المؤلفون عملية تسجيل الدخول؛ وقد تمت ملاحظة سير العملية حتى نموذج Steam.\nيتلقى Valve اسم مضيف return_to / realm في كل طلب من هذا النوع. ولم يُرجع موقع rbsnin.com أي حظر من «Link Filter» على 2026-09-21.\nحسب الطلب\nبصفته مزود خدمة OpenID، يتلقى Steam اسم مضيف المصادقة مع كل طلب مصادقة: حيث يصل هذا الاسم إلى خوادم Valve الخاصة في openid.return_to و openid.realm المعلمات.\nمرسل من الموقع\nلا يتم اكتشاف مضيف المصادقة عن طريق المسح — حيث ترسل المنصة القيمة Steam في كل طلب. وفقًا لـ OpenID 2.0 §9.1 return_to وهو اختياري من الناحية الشكلية، لكن بدونه لا يمكن لـ Steam تقديم نتيجة تسجيل الدخول، لذا فهو مطلوب فعليًّا لضمان نجاح عملية تسجيل الدخول Steam. بل إن Steam يعرض اسم المضيف للمستخدم (\"<host> ليس تابعًا لـ Steam أو Valve\").\n14 سنة\nهو عمر أقدم خادم مصادقة لا يزال يحمل Steam عمليات تسجيل دخول عند الفحص رقم 2026-09-21 (dota2.net، مسجل منذ 2011-10-29)؛ أما أحدث خادم فيبلغ عمره ثلاثة أيام (rbsnin.com). لا تعتبر الرقم «0 مضيف مصادقة محظور» بمثابة النتيجة. من شأن حجب مضيف المصادقة أن يعطل ميزة «تسجيل الدخول باستخدام Steam» في المنصة تمامًا، لذا فإن السجل الذي يتم إنشاؤه استنادًا إلى عمليات تسجيل الدخول الناجحة لا يمكن أن يحتوي إلا على المضيفات التي لم يتم حجبها مطلقًا. الرقم الذي يحمل معنىً ليس عدد حالات الحظر — بل هو عدد السنوات التي ظل فيها النطاق الرئيسي مدرجًا في «مرشح الروابط» (Link Filter) بينما استمرت عملية تسجيل الدخول المرتبطة به في العمل.\nمضيفات المصادقة ذات النطاقات المنفصلة: تاريخ التسجيل مقابل النطاق الرئيسي (30 مسارًا: الـ25 التي تم تحديدها في تدقيق المتصفح 2026-09-21، بالإضافة إلى 5 تمت إضافتها في 2026-09-22)\nالمنصة\tمرشح الروابط: الرئيسي\tمضيف Auth\tمرشح الارتباط: مضيف المصادقة\tتم تسجيل مضيف Auth\tمصدر الملاحظة\tملف الأدلة\nرولبيت\nrollbit.com · رقم التسجيل 2014-11-08\n\tمحجوب\n2026-09-19، 2026-09-21 · Wayback 2026-09-21\n\trbsnin.com\tتنظيف\n2026-09-21 · HTML الخام (لا توجد لقطة من Wayback)\n\t2026-09-18\n09:34:52Z، Verisign RDAP\n\tSteam إشعار صفحة تسجيل الدخول، 2026-09-20\trollbit.com.json\nSkin.Club\nskin.club · التسجيل 2017-09-04\n\tمحجوب\n2026-09-19، 2026-09-21 · Wayback 2026-09-21\n\tsc-auth.net\tتنظيف\n2026-09-21 · Wayback 2026-09-21\n\t2019-04-02\nRDAP\n\tSteam إشعار صفحة تسجيل الدخول\tskin.club.json\nHowl.GG\nhowl.gg · التسجيل 2017-03-16\n\tمحظور\n2026-09-18، 19 سبتمبر، 21 سبتمبر · Wayback 2026-09-21\n\thowl.uno\tتنظيف\n2026-09-21 · Wayback 2026-09-21\n\t2026-08-11\nRDAP\n\tالتقاط مباشر من المتصفح + رابط OpenID المُرفق\thowl.gg.json\nDuelbits\nduelbits.com · رقم التسجيل 2020-02-03\n\tمحجوب\n2026-09-21 · Wayback 2026-09-21\n\tswitchflips.com\tتنظيف\n2026-09-21 · Wayback 2026-09-21\n\t2020-04-21\nRDAP\n\tعنوان URL الخاص بـ OpenID المُقدَّم\tduelbits.com.json\nCSGOFast\ncsgofast.com · رقم التسجيل 2015-03-27\n\tمحجوب\n2026-09-19، 2026-09-21 · Wayback 2026-09-21\n\tsteam-login.authtofast.com\tتنظيف\nauthtofast.com، 2026-09-21 · Wayback 2026-09-21\n\t2026-06-30\nauthtofast.com، RDAP\n\tالتقاط مباشر من المتصفح + رابط OpenID المقدم\tcsgofast.com.json\nفارمسكينز\nfarmskins.com · رقم التسجيل 2016-03-23\n\tمحجوب\n2026-09-19، 2026-09-21 · HTML الخام\n\tsteam.kobal.cc\tتنظيف\n2026-09-19، 2026-09-21 · HTML الخام\n\t2017-01-07\nkobal.cc، RDAP\n\tالتقاط مباشر من المتصفح + رابط OpenID المُقدم\tfarmskins.com.json\nCobaltLab\ncobaltlab.tech\n\tمحظور\n2026-09-21 · HTML الخام\n\tcobaltauth.com\tتنظيف\n2026-09-21 · HTML الخام\n\t2025-01-07\nRDAP\n\tعنوان URL الخاص بـ OpenID المُقدَّم\tcobaltlab.tech.json\nCSGO.NET\ncsgo.net · reg. 2012-07-22\n\tمحجوب\n2026-09-21 · HTML الخام\n\tcn2.easylot.net\tتنظيف\n2026-09-21 · HTML الخام\n\t2016-09-03\neasylot.net، RDAP\n\tالتسجيل المباشر لشاشة المتصفح\tcsgo.net.json\nGGDrop\nggdrop.com\n\tمحجوب\n2026-09-21 · HTML الخام\n\tggauth.com\tتنظيف\n2026-09-21 · HTML الخام\n\t2023-05-03\nRDAP\n\tعنوان URL الخاص بـ OpenID المُقدم\tggdrop.com.json\nRustChance\nrustchance.com\n\tمحجوب\n2026-09-21 · HTML الخام\n\thgfuihd.com\tتنظيف\n2026-09-21 · HTML الخام\n\t2019-01-27\nRDAP\n\tعنوان URL الخاص بـ OpenID المُقدم\trustchance.com.json\nSkin.Fans\nskin.fans\n\tمحجوب\n2026-09-21 · HTML الخام\n\tauth.skinfans.com\tتنظيف\n2026-09-21 · HTML الخام\n\t2018-07-16\nskinfans.com، RDAP\n\tعنوان URL الخاص بـ OpenID المُقدم\tskin.fans.json\nسكينبورت\nskinport.com · رقم التسجيل 2018-09-05\n\tمحجوب\n2026-09-21 · HTML الخام\n\tskinport.app\tتنظيف\n2026-09-21 · HTML الخام\n\t2020-06-20\nRDAP\n\tالتقاط مباشر من المتصفح + رابط OpenID المُرفق\tskinport.com.json\nSkins.Cash\nskins.cash\n\tمحجوب\n2026-09-21 · HTML الخام\n\tskinscash.live\tتنظيف\n2026-09-21 · HTML الخام\n\t2019-12-05\nRDAP\n\tعنوان URL الخاص بـ OpenID المُقدم\tskins.cash.json\nTF2Hunt\ntf2hunt.com · رقم التسجيل 2018-01-13\n\tمحجوب\n2026-09-21 · HTML الخام\n\trstspcl.com\tتنظيف\n2026-09-21 · HTML الخام\n\t2020-08-08\nRDAP\n\tالتقاط مباشر من المتصفح + رابط OpenID المُرفق\ttf2hunt.com.json\nCSGOGem\ncsgogem.com · رقم التسجيل 2016-10-16\n\tمحجوب\n2026-09-22 · HTML الخام\n\tapi.csgem.com\ncsgem.com — نطاق مستقل قابل للتسجيل\n\tتنظيف\n2026-09-22 · HTML الخام\n\t2014-03-08\ncsgem.com، RDAP — الأقدم في السجل\n\tالجمع اليدوي + التقاط «Link Filter»\tlinkfilter-2026-09-22.json\nGamdom\ngamdom.com · التسجيل 2016-07-29\n\tمحجوب\n2026-09-22 · HTML الخام\n\tlogin.gambldom.com\ngambldom.com — يختلف عن الاسم التجاري بحرف واحد فقط\n\tتنظيف\n2026-09-22 · HTML الخام\n\t2017-09-24\ngambldom.com، RDAP\n\tالجمع اليدوي + التقاط «Link Filter»\tlinkfilter-2026-09-22.json\n12CS\n12cs.fail · reg. 2026-03-24\n\tمحجوب\n2026-09-22 · HTML الخام\n\tfail.games\tتنظيف\n2026-09-22 · HTML الخام\n\t2021-08-24\nfail.games، RDAP\n\tالجمع اليدوي + التقاط مرشح الروابط\tlinkfilter-2026-09-22.json\nCSGOEmpire\ncsgoempire.com · مسجل 2015-06-10\n\tتنظيف\n2026-09-19، 2026-09-21 · Wayback 2026-09-21\n\tcsgoempirelogin4.com\nأحد المجالات العشرة المرقمة من login1 إلى login10\n\tتنظيف\n2026-09-21 · Wayback 2026-09-21\n\t2020-07-20\n05:49:17Z، Verisign RDAP\n\tالتقاط مباشر لشاشة المتصفح\tcsgoempire.com.json\nCS.MONEY\ncs.money\n\tتنظيف\n2026-09-21 · HTML الخام\n\tauth.dota.trade\tتنظيف\n2026-09-21 · HTML الخام\n\t2016-07-15\ndota.trade، RDAP\n\tSteam إشعار صفحة تسجيل الدخول\tcs.money.json\nCSFloat\ncsfloat.com · reg. 2021-07-11\n\tتنظيف\n2026-09-21 · HTML الخام\n\tcsgofloat.com\nنطاق العلامة التجارية السابق للمشغل؛ نطاق قابل للتسجيل بحد ذاته، ولا يُعد مؤشراً على التهرب\n\tتنظيف\n2026-09-21 · HTML الخام\n\t2015-09-29\nRDAP\n\tالتسجيل المباشر لشاشة المتصفح\tcsfloat.com.json\nG4Skins\ng4skins.com\n\tتنظيف\n2026-09-21 · HTML الخام\n\tauth.g4s.to\tتنظيف\n2026-09-21 · HTML الخام\n\t2021-05-30\ng4s.to، RDAP\n\tعنوان URL الخاص بـ OpenID المُقدم\tg4skins.com.json\nJuice.GG\njuice.gg\n\tتنظيف\n2026-09-21 · HTML الخام\n\tletmeinjuice.com\tتنظيف\n2026-09-21 · HTML الخام\n\t2024-04-15\nRDAP\n\tعنوان URL الخاص بـ OpenID المُقدم\tjuice.gg.json\nMarket.CSGO\nmarket.csgo.com\n\tتنظيف\n2026-09-21 · HTML الخام\n\tdota2.net\tتنظيف\n2026-09-21 · HTML الخام\n\t2011-10-29\nRDAP\n\tالتقاط مباشر لشاشة المتصفح + رابط OpenID المُرفق\tmarket.csgo.com.json\nRust.TM\nrust.tm\n\tتنظيف\n2026-09-21 · HTML الخام\n\tdota2.net\tتنظيف\n2026-09-21 · HTML الخام\n\t2011-10-29\nRDAP\n\tعنوان URL الخاص بـ OpenID المُقدم\trust.tm.json\nCSGOLounge\ncsgolounge.com · رقم التسجيل 2013-08-14\n\tتنظيف\n2026-09-22 · HTML الخام\n\tdota2.net\nواجهة مستخدم ثالثة على مضيف المصادقة هذا\n\tتنظيف\n2026-09-22 · HTML الخام\n\t2011-10-29\ndota2.net، RDAP\n\tالجمع اليدوي + التقاط «Link Filter»\tlinkfilter-2026-09-22.json\nDota2Lounge\ndota2lounge.com · رقم التسجيل 2012-08-10\n\tتنظيف\n2026-09-22 · HTML الخام\n\tdota2.net\nواجهة المستخدم الرابعة على مضيف المصادقة هذا\n\tتنظيف\n2026-09-22 · HTML الخام\n\t2011-10-29\ndota2.net، RDAP\n\tالجمع اليدوي + التقاط «Link Filter»\tlinkfilter-2026-09-22.json\nسكينبارون\nskinbaron.de\n\tتنظيف\n2026-09-21 · HTML الخام\n\tskinbaron.com\nنفس العلامة التجارية، نطاق مستوى أعلى مختلف\n\tتنظيف\n2026-09-21 · HTML الخام\n\t2015-12-22\nRDAP\n\tعنوان URL الخاص بـ OpenID المُقدم\tskinbaron.de.json\nTF2Royal\ntf2royal.com · عدد المسجلين: 2022-08-17\n\tتنظيف\n2026-09-21 · HTML الخام\n\ttf2auth.com\tتنظيف\n2026-09-21 · HTML الخام\n\t2021-07-27\nRDAP\n\tالتقاط مباشر من المتصفح + رابط OpenID المُرفق\ttf2royal.com.json\nTradeit\ntradeit.gg\n\tتنظيف\n2026-09-21 · HTML الخام\n\tconnect-tradeit.com\tتنظيف\n2026-09-21 · HTML الخام\n\t2022-02-23\nRDAP\n\tعنوان URL الخاص بـ OpenID المُقدَّم\ttradeit.gg.json\nجهاز التحسين\nupgrader.pro\n\tتنظيف\n2026-09-21 · HTML الخام\n\tupgauth.space\tتنظيف\n2026-09-21 · HTML الخام\n\t2026-08-14\nRDAP\n\tعنوان URL الخاص بـ OpenID المُقدم\tupgrader.pro.json\nالمصدر: steamcommunity.com/linkfilter، طلب GET غير مصدق، 2026-09-21، 53 مضيفًا، فاصل زمني 3 ثوانٍ؛ steam_tos_assets/linkfilter-recheck-2026-09-21.json؛ كود HTML الخام في steam_tos_assets/linkfilter-raw/. مواعيد التسجيل: RDAP، steam_tos_assets/domain-registration.json. · فحص مسبق لـ 2026-09-19 في linkfilter-all-results.json · إدخال سجلات المسارات في auth-route-audit.json · لقطات من «Wayback Machine» لصفحات «Link Filter»، 2026-09-21، المدرجة في wayback-snapshots.json (لا توجد لقطة لموقع rbsnin.com؛ والملف الخام المحلي هو السجل الوحيد).\n\nمواعيد التسجيل: RDAP (steam_tos_assets/domain-registry/). «عنوان URL الخاص بـ OpenID المُقدَّم» يحدد معلمات الطلب، ولا يُعد تسجيل دخول مكتملًا. لم يقم المؤلفون بإتمام عملية تسجيل دخول على أي منصة. لا يُعد وجود نطاق منفصل بحد ذاته دليلاً على التهرب. كما أن عبارة «تم حظر 0 مضيفات مصادقة» ليست نتيجة مستقلة: فحظر مضيف واحد من شأنه تعطيل عملية تسجيل الدخول Steam لتلك المنصة، لذا لا يمكن أن يحتوي السجل المُجمَّع من عمليات تسجيل الدخول الناجحة على مضيف مصادقة محظور. الملاحظة التي تحمل وزنًا هي الاقتران ومدته — نطاق رئيسي في «مرشح الروابط» بجانب نطاق تسجيل دخول ظل يعمل لسنوات. يحتوي هذا الجدول على 30 صفًا: 25 من أصل 27 مسارًا مع ملف أدلة لكل مسار، بالإضافة إلى خمسة تمت إضافتها في 2026-09-22 حيث تم تسجيل تقسيم «مرشح الروابط» الخاص بها في linkfilter-2026-09-22.json على الرغم من أن المجموعة نفسها تم جمعها يدويًّا — كما يتضح من الصفوف الموجودة في عمود «المصدر». أما مسارا ملفَي الأدلة اللذان لم يظهران فهما skinsnipe.com (مضيف المصادقة pricing.tradeupspy.com، المسجل بـ 2020-03-11) وموقع csgobig.com (مضيف مصادق عليه letmeinbig.com، مسجلة بـ 2023-01-20)؛ وقد أظهر كلاهما أن المضيف الرئيسي «محظور» / «سليم» في عملية التحقق من 2026-09-22، المسجلة باستخدام خوارزمية SHA-256 في linkfilter-2026-09-22c.json، لكن كود HTML الخام لتلك الدفعة غير موجود في المجموعة المنشورة، لذا تم ذكر أسمائها هنا بدلاً من تخصيص صف لها، وهو ما يتضح من كل سطر آخر في هذا الجدول. أما المسارات الـ 12 المتبقية التي تم جمعها يدويًّا في السجل، فقد تم تحديدها على هذا النحو في master_registry.json تحت realm_src: user.\n\nالتدقيق التجريبي الأولي · نطاق زمني متعدد السنوات\nفخ «الصورة الكبيرة»: «مرشح الروابط» مجرد مسرحية للامتثال، وليس درعًا واقيًا\n\nفي متصفحات أجهزة الكمبيوتر المكتبية، يتم حماية المستخدمين بواسطة آليات دفاع خارجية: حيث تعمل ميزة «التصفح الآمن» من جوجل و«سمارت سكرين» من مايكروسوفت على اعتراض محاولات التصيد الاحتيالي المعروفة من خلال عرض تحذيرات حمراء تشغل الشاشة بالكامل. في وضع «Big Picture» في Steam، والطبقة التراكبية داخل اللعبة (Shift+Tab)، ومجموعة Steam (SteamOS)، لا توجد هذه الدفاعات. لا يدعم المتصفح المدمج أي ملحقات، ويقوم بتعطيل محركات «التصفح الآمن» الخارجية، ولا يترك للمستخدم سوى حاجز وقائي واحد فقط: Valve's linkfilter بين الخلايا.\n\nاسحب لمقارنة النتائج الأربع ←\n\n92.5%\n2025–2026: هجمات التصيد الاحتيالي المتطورة تمت الموافقة عليه دون أي ملاحظات (37/40)\n77.5%\n2023–2024: حقبة التصيد الاحتيالي CS2 تمت الموافقة عليها دون أي ملاحظات (31/40)\n70.0%\nحالات التصيد الاحتيالي القديمة للفترة 2021–2022 تمت الموافقة عليها دون أي ملاحظات (28/40)\n7 / 7\nتم حجب مواقع المقامرة (عينة مرجعية إيجابية)\nتدقيق طولي متعدد السنوات: اختبار 120 نطاقًا خالصًا Steam مخصصًا للتصيد الاحتيالي في الوقت الفعلي (24 سبتمبر 2026)\n\nولتحديد ما إذا كان مرشح Valve يعاني ببساطة من بطء في استيعاب التهديدات الجديدة أم أنه يعاني من عمى تام تجاهها، قمنا بتدقيق 120 نطاقًا مؤكدًا للتصيد الاحتيالي يستهدف Steam عبر ثلاث مجموعات تاريخية مقارنة بـ steamcommunity.com/linkfilter:\n\nالدفعة الأولى: 2021–2022 (العروض التجارية الكلاسيكية وإسقاط العناصر) — 70.0% اجتياز كامل (28/40). حتى بعد مرور 4 إلى 5 سنوات على إدراجها في قوائم المراقبين المجتمعيين، لا تزال 7 من كل 10 خوادم قديمة تُستخدم في عمليات التصيد الإلكتروني تعمل دون أي حظر.\nالدفعة الثانية: 2023–2024 (حملة الترويج لـ CS2 Beta وطلبات الدعم المزيفة) — 77.5% اجتياز نظيف (31/40). الحملات التي تنتحل صفة إصدارات «Counter-Strike 2» والنداءات المزيفة الموجهة إلى المجتمع (على سبيل المثال: cs2-steam.com، appealsteamcommunity.help) تمر مباشرة من خلالها.\nالدفعة الثالثة: 2025–2026 (عمليات النشر على الحافة بدون خادم ونسخ أيقونة الموقع) — 92.5% اجتياز كامل (37/40). مجموعات أدوات التصيد الاحتيالي الحديثة التي يتم نشرها على EdgeOne وVercel وCloudflare Pages (على سبيل المثال: steamgifter.online، steam-dp4lt5b8fnez.edgeone.dev) يمرون دون أي عوائق تذكر.\n\nالقياس عن بُعد و«درع المسؤولية»، وليس الحماية. لماذا يوجد «مرشح الروابط» إذا كان يسمح بمرور 70% إلى 92.5% من حالات التصيد الاحتيالي الخالصة من النوع Steam؟ إنه يعمل كإخلاء مسؤولية للشركة وكمستشعر لقياس أداء النقرات الصادرة. من خلال تقديم طلب مهذب \"أنت تغادر Steam\" إشعار يحتوي على زر أخضر قابل للنقر عليه بعنوان «متابعة»، حيث يُلقي Valve بالمسؤولية القانونية على عاتق الضحية بموجب Steam اتفاقية الاشتراك (*«قام المستخدم طواعيةً بالتصفح خارج Steam»*). Valve يجمع بيانات القياس عن بُعد الخاصة بالنقرة، لكنه لا يمنع السرقة.\n\nدليل \"Favicon Hash\": عدم استيعاب أي موجزات للتهديدات. تقوم منصات استخبارات التهديدات المستقلة (urlscan.io، Shodan، Censys) بتحديد مجموعات التصيد الاحتيالي النشطة Steam من خلال إجراء بحث بسيط عن التجزئة الرسمية لرمز المفضلة الخاص بـ Steam (page.favicon.hash:9f890a9debcdfccc339149a7943be9aff9e4c9203c2fa37d5671a5b2c88503ad NOT domain:*.steampowered.com). يكشف هذا الفحص الآلي الأساسي عن مجموعات التصيد النشطة في غضون ثوانٍ. لا يقوم Valve بالمزامنة مع مصادر البيانات الخارجية، ولا يُجري عمليات تعقب التهديدات القائمة على التجزئة، ولا يتدخل يدويًّا إلا عندما يُجبر على ذلك من قبل الجهات التنظيمية (أمر WSGC لعام 2016 المتعلق بالمقامرة) أو لحماية سلاسل نطاقاته المسجلة كعلامات تجارية.\n\nأدلة المراجعة الأولية المادية: تدقيق طولي متعدد السنوات يشمل 120 مجالًا: تقرير-التدقيق-الطولي-لعمليات-التصيد-الخادع-عبر-البخار.json · 100 عينة مخصصة من Steam للتصيد الاحتيالي: linkfilter-steam-phishing-100.json · تدقيق شامل لبيانات التغذية (n=250): linkfilter-coverage-2026-09-22.json.\n\nCSGOEmpire — التسجيل الجماعي لعشرة نطاقات مصرح بها ومرقمة\n\nفي 2020-07-20 عشرة نطاقات مرقمة، csgoempirelogin1.com من خلال csgoempirelogin10.com، تم تسجيلها. وتوجد طوابع زمنية من Verisign RDAP مسجلة لجميع الحالات العشر: login1 05:49:06Z، login5 05:49:08Z، login2 05:49:11Z، login3 05:49:14Z، login4 05:49:17Z، login6 05:49:20Z، login7 05:49:23Z، login8 05:49:26Z، login9 05:49:28Z — تسعة نطاقات في 22 ثانية — و«login10» في الساعة 05:56:03Z، بعد سبع دقائق. ويتوافق التباعد الزمني بينهما مع عملية جماعية واحدة من جانب مسجل النطاقات.\n\nيتوافق هذا النمط مع المضيفات الاحتياطية التي تم تجهيزها مسبقًا؛ فقط login4 وقد لوحظ ذلك في طلب OpenID فعلي. أظهر كل من csgoempire.com و csgoempirelogin4.com نتيجة «CLEAN» في «Link Filter» عند 2026-09-21؛ ولم يكن موقع CSGOEmpire من بين المواقع المذكورة في التقارير الصحفية المتعلقة بالإشعارات الصادرة في يوليو 2016.\n\n# DNS — جميعها الـ10 نشطة (سبتمبر 2026)\nحسنًا csgoempirelogin1.com 172.67.129.43\nحسنًا csgoempirelogin2.com 172.67.175.168\nحسنًا csgoempirelogin3.com 188.114.96.3\nحسنًا csgoempirelogin4.com 188.114.96.11 ← في حركة مرور OpenID\nحسنًا csgoempirelogin5.com 172.67.160.194\nحسنًا csgoempirelogin6–10.com عناوين IP الخاصة بـ Cloudflare\nNXDOMAIN: csgoempirelogin11.com\nتم تسجيل جميع العناصر العشرة 2020-07-20؛ وتم توقيت جميع العناصر العشرة بواسطة RDAP (steam_tos_assets/domain-registry/csgoempireloginN.com.rdap.json)\nخلاصة موجهة للجهات التنظيمية\nإن وجود نطاق رئيسي محجوب مقترن بمضيف مصادقة غير محجوب يترك مسار تسجيل الدخول مفتوحًا — ويظل مفتوحًا لسنوات.\n\nيُعد كتلة «Link Filter» في المجال الرئيسي سجلاً عاماً قابلاً للتحقق. ويقوم مضيف المصادقة بنقل حركة المرور الخاصة بـ «تسجيل الدخول باستخدام Steam»، ويظهر في معلمات طلب OpenID الخاصة بـ Valve. عند إجراء عمليات التحقق على 2026-09-21 و2026-09-22، في 26 زوجًا من الأزواج المقسمة بواسطة التصفية، أرجع النطاق الرئيسي كتلة تصفية الارتباط بينما لم يرجع الوكيل الذي يحمل عملية تسجيل الدخول الخاصة به أي شيء. يسجل السجل أعلاه النصف الآخر من ذلك: هذه المضيفات ليست نطاقات مؤقتة قصيرة العمر. كان العديد منها مسجلاً منذ أكثر من عقد من الزمن حتى تاريخ الفحص، وكل يوم من تلك الأيام هو يوم تلقى فيه Valve اسم المضيف في معلمات طلبه الخاصة. لم تنشر Valve أي سجل إنفاذ لكل مشغل، لذا لا يمكن تحديد ما إذا كانت أي إجراءات أخرى قد طُبقت على هذه المضيفات من البيانات العامة.\n\n12 سنة و6 أشهر\nتم حظر موقع csgogem.com في «مرشح الروابط».\nمضيف تسجيل الدخول الخاص به api.csgem.com كان\nمسجل منذ 2014-03-08، وهو ليس كذلك.\nملخص بلغة بسيطة — للجهات التنظيمية والمحاكم (توسيع)\nملخص بلغة بسيطة — للجهات التنظيمية\nالخلفية: ما هو Steam ولماذا يكتسب أهمية في هذا السياق\n\nSteam هي منصة برمجية تديرها شركة Valve (بيلفيو، واشنطن، الولايات المتحدة الأمريكية). Steam تعمل كمزود للهوية الرقمية: تستخدم مواقع المقامرة والألعاب عبر الإنترنت نظامًا يُسمى «تسجيل الدخول باستخدام Steam» — وهو زر يتيح للموقع التحقق من أن الزائر يمتلك حسابًا حقيقيًّا على Steam. وهذا مشابه لـ «تسجيل الدخول باستخدام Google» أو التحقق من بطاقة الهوية الصادرة عن الحكومة: حيث يُحيل الموقع الإلكتروني المستخدم إلى خوادم Steam، وتقوم Steam بالتحقق من هويته، ثم تعيده Steam إلى الموقع الإلكتروني. تقوم Valve بتشغيل نظام المصادقة. وتمر كل عملية تسجيل دخول تتم عبر خيار «تسجيل الدخول باستخدام Steam» عبر خوادم Valve الخاصة.\n\nما فعله Valve: حجب النطاق\n\nفي يوليو 2016، في أعقاب الضغوط الإعلامية والقانونية بشأن المقامرة باستخدام «السكين»، أرسل محامي Valve إخطارات إلى ما يقرب من 23 موقعًا للمقامرة تم تحديدها (وفقًا لتقارير صحفية صادرة في 21 يوليو 2016)؛ وفي أكتوبر 2016، أبلغت شركة Valve لجنة المقامرة بولاية واشنطن أنها اتصلت بأكثر من أربعين موقعًا. وتظهر بعض نطاقات المقامرة في Steam مرشح الروابط — قائمة تجعل أي رابط يؤدي إليهم يتم نشره داخل Steam (في الدردشة، أو على صفحة الملف الشخصي، أو في المتجر) يعرض صفحة تحذير: \"الرابط محظور!\" يُعد «مرشح الارتباط» الإجراء التنفيذي الوحيد الذي يمكن ملاحظة تأثيره من خارج Valve.\n\nمثال: رابط إلى rollbit.com يؤدي الخيار Steam إلى عرض صفحة تحذير «Link Filter» (تم تحديد الخيارين 2026-09-19 و2026-09-21). من الناحية النظرية، يتم حظر موقع المقامرة.\nما هو نطاق الوكيل؟\n\nأ مضيف المصادقة ذو النطاق المنفصل هو وكيل مصادقة: عنوان موقع إلكتروني ثانٍ، على نطاق قابل للتسجيل مختلف، يضعه المشغل نفسه بين مستخدميه وSteam لغرض وحيد هو تنفيذ خطوة «تسجيل الدخول باستخدام Steam». وهو يعمل كوسيط لعملية تسجيل الدخول. يعتقد المستخدم أنه يقوم بتسجيل الدخول إلى المنصة؛ لكن الطلب الذي يصل إلى Valve يحمل اسم مضيف الوكيل، وليس اسم مضيف المنصة. وعادةً ما لا يكون له أي ارتباط ظاهر للعيان بموقع المقامرة، وهو العنوان الذي يستقبل المستخدمين مرة أخرى بعد أن يؤكد Steam هويتهم.\n\nمثال: تعمل Rollbit بموجب rollbit.com، وهو ما يحجبه مرشح الارتباط. بالنسبة لعملية المصادقة Steam، استخدم التدفق الذي لوحظ على 2026-09-20 عنوانًا منفصلاً: rbsnin.com، المسجل بـ 2026-09-18. وقد أرجع هذا العنوان لا توجد كتلة «تصفية الروابط» في 2026-09-21. استمر موقع المقامرة في العمل، ومرت عملية تسجيل الدخول Steam عبر المضيف غير المحظور.\nالنقطة الحاسمة: يتم إرسال معرّف المضيف إلى Steam في كل طلب\n\nValve لا يحتاج إلى إجراء مسح أو زحف لمعرفة مضيفي المصادقة قيد الاستخدام. Steam هو مزود الهوية OpenID بالنسبة لهذه المواقع، فإن كل نقرة على زر «تسجيل الدخول باستخدام Steam» ترسل طلب GET إلى خوادم Valve نفسها، متضمنةً اسم مضيف المصادقة في نص عادي. بموجب OpenID 2.0 §9.1، فإن return_to هذا الحقل اختياري من الناحية الشكلية، ولكن بدونه لا يمكن لـ Steam تقديم نتيجة تسجيل الدخول، لذا فهو مطلوب فعليًّا لضمان نجاح عملية تسجيل الدخول Steam. أما Steam نفسه فيعرض اسم المضيف على صفحة تسجيل الدخول (\"<host> ليس تابعًا لـ Steam أو Valve\").\n\n— شكل الطلب Steam الذي يتم استلامه (المضيف كما لوحظ في حالة Rollbit في 2026-09-20): —\nاحصل على steamcommunity.com/openid/login\n&openid.mode=checkid_setup\n&openid.return_to=https://rbsnin.com/… ← مطلوب فعليًّا؛ يظهر في سجل Valve\n&openid.realm=https://rbsnin.com ← وفقًا لما أعلنه الموقع نفسه؛ يتم عرضه على صفحة تسجيل الدخول الخاصة بـ Steam\nإذا كان الموقع يستخدم التحقق من خادم إلى خادم (check_authentication)، فإن سجل Valve يسجل أيضًا عنوان IP لخادم المنصة وشبكة الاستضافة.\n\nيُعد استخراج اسم المضيف من هذا الطلب عملية قياسية. أما سجل التنفيذ — الذي يوضح المضيفات التي تم اتخاذ إجراء بشأنها، وتلك التي لم يتم اتخاذ إجراء بشأنها، والمعايير التي استند إليها ذلك — فهو موجود فقط في البنية التحتية لـ Valve ولم يتم نشره.\n\nما الذي يثبته هذا؟\n\n1. تعمل وحدة «تصفية الروابط» على الروابط، وليس على عمليات تسجيل الدخول. حجب النطاق الرئيسي (على سبيل المثال rollbit.com) يعرض تحذيرًا للمستخدمين الذين ينقرون على الروابط المؤدية إليه داخل Steam. وهذا لا يمنع الموقع من العمل، ولا يمنع استخدام خدمة OpenID الخاصة بـ Valve عبر عنوان مختلف.\n\n2. لم يتم حظر مضيفي المصادقة الذين تم اختبارهم. يُظهر الجدول أعلاه مضيفات المصادقة ذات المجالات المنفصلة التي تم تسجيلها بين عام 2011 وسبتمبر 2026، وقد تم تسجيل العديد منها بعد مرور سنوات على الإشعارات الصادرة في يوليو 2016. في 26 زوجًا، أرجع النطاق الرئيسي حظرًا من «Link Filter» بينما لم يفعل الوكيل الذي يحمل معلومات تسجيل الدخول الخاصة به ذلك (عمليات فحص غير مصدقة، 2026-09-21 و2026-09-22؛ تم حفظ الردود الأولية و SHA-256). كان ذلك الوكيل سيتوقف عن العمل في اليوم الذي رفضه فيه Valve، ولهذا السبب فإن المقياس هنا هو المدة التي استمر فيها العمل، وليس ما إذا كان مدرجًا في القائمة أم لا. يتلقى Valve أسماء المضيفين هذه في طلبات OpenID الخاصة به. لا يمكن تحديد ما إذا تم تطبيق أي إجراء آخر بخلاف «Link Filter» من البيانات العامة، لأن Valve لم ينشر أي سجل إنفاذ لكل مشغل.\n\n3. استمرت المواقع في إجراء عملية المصادقة عبر البنية التحتية لـ Valve. \"تسجيل الدخول باستخدام Steam\" هي خدمة تقدمها Valve؛ وكل عملية مصادقة تتم من خلالها هي طلب تتلقاه Valve وتقوم بمعالجته. كما يحقق Valve إيرادات من مفاتيح الحالات، ويفرض سوق المجتمع Steam رسومًا إجمالية تبلغ حوالي 15% على المعاملات التي تتم داخل السوق (وليس على المعاملات الخارجية). أدى إجراء «Link Filter» إلى إنشاء سجل عام؛ ولم يقطع علاقة المصادقة.\n\nهل كان الحظر سيؤتي ثماره؟\n\nوبالمثل: عندما أوقفت شركة «فريينوم» (Freenom) — وهي شركة تسجيل النطاقات المجانية — نشاطها في عام 2023، توقفت حملات التصيد الاحتيالي التي كانت تعتمد على نطاقاتها. وتعتمد استمرارية التشغيل على استقرار البنية التحتية.\n\nوينطبق المنطق نفسه هنا. فإذا تم رفض مضيف المصادقة أثناء معالجة OpenID في Steam، فإن وظيفة «تسجيل الدخول باستخدام Steam» في المنصة ستتوقف عن العمل إلى أن يتم تسجيل مضيف جديد وإصدار الشهادات وانتشار التغييرات في نظام أسماء النطاقات (DNS). وخلال تلك الفترة: سيحدث تعطل في الخدمة.\n\nالتناوب لا يجعل عملية الحجب عديمة الجدوى. وهذا يجعل عملية الحظر تكلفة تشغيلية. ونظرًا لأن المضيفات الجديدة تظهر في سجلات الطلبات الخاصة بـ Valve عند الاستخدام الأول، فقد يتم تنفيذ الاستجابة بنفس سرعة ذلك الاستخدام الأول.\n\nيُعد التسجيل الجماعي في حد ذاته إشارةً: تم تسجيل حسابات «login1» إلى «login10» التابعة لموقع CSGOEmpire على 2020-07-20، تسعة منها في غضون 22 ثانية (Verisign RDAP). ولا يشترط أن تكون الاستجابة لكل نطاق على حدة؛ فمن الممكن اعتبار سلسلة متتالية من جلسة واحدة لدى المسجل سلسلة واحدة.\n\nلا يظهر في السجل العام أي محاولة لحظر مضيفي المصادقة تم إحباطها عن طريق التناوب.\nويُظهر التقرير النطاقات الرئيسية المحجوبة في الوقت الذي ظل فيه الوكيل الذي يحمل كل عملية تسجيل دخول قيد التشغيل — 26 زوجًا حتى تاريخ 2026-09-22، وأقدم مضيف مصادقة مسجل منذ 12 عامًا و6 أشهر — ولا توجد سجلات منشورة تتعلق بتطبيق الإجراءات على أي مشغل.\nوبالتالي، فإن السؤال المطروح على الجهة التنظيمية هو: ما هي إجراءات الإنفاذ، إن وجدت، التي طبقتها Valve على مضيفي التوثيق الذين تتلقى معلوماتهم في طلبات OpenID الخاصة بها؟\nما الذي فعله Valve — ولماذا لم يقطع مسار المصادقة\n\nيوضح الجدول أدناه كل إجراء Valve موثق علنًا، مع تحديد ما إذا كان قد أثر على نقطة دخول المصادقة عبر OpenID أم لا. والنتيجة ليست أن «Valve لم يفعل شيئًا» — بل هي أن أياً من الإجراءات الموثقة علنًا لم تمس النقطة التي تمر عبرها عمليات تسجيل الدخول إلى منصات المقامرة عبر خوادم Valve.\n\nالتاريخ\tValve الإجراء\tالمتضررون openid.return_to المسار؟\nيوليو 2016\tبيان عام صادر في 13 يوليو 2016؛ إخطارات من المحامي إلى حوالي 23 موقعًا محددًا (الصحافة، 21 يوليو 2016)؛ تم الاتصال بأكثر من 40 موقعًا بموجب رسالة Valve الموجهة إلى WSGC في أكتوبر 2016\tلا. تعمل الإشعارات و«مرشح الروابط» على العوامل والروابط؛ ولم يتغير مسار طلب OpenID.\n2017\tإغلاق IEconItems_730/GetPlayerItems (وفقًا لحساب CSFloat الهندسي؛ لم يتم العثور على سجل التغييرات Valve)\tلا. تأثرت إمكانية الاطلاع على سجل العناصر العامة. لم يتم تعديل عملية المصادقة عبر OpenID.\n2018-03-29\tالإعلان عن تجميد تداول الأغراض في CS:GO لمدة 7 أيام (blog.counter-strike.net)\tلا. تباطؤ في حركة العناصر؛ لم يتم تغيير مسار طلب OpenID.\n2022-05-10\tتمت إزالة نقاط نهاية إلغاء الصفقات من واجهة برمجة التطبيقات العامة على الويب (اكتشفها المستخدم؛ لا يوجد سجل تغييرات Valve — node-steam-tradeoffer-manager #325)\tلا. تم إغلاق أداة تبادل العروض؛ ولم يتم تعديل عملية المصادقة عبر OpenID.\n2023-12-04\tأصبح إنشاء مفتاح API يتطلب الآن تأكيدًا عبر الهاتف المحمول (steamcommunity.com/dev/apikey؛ لا توجد قائمة بالتغييرات)\tلا. تمت حماية نقطة النهاية الرئيسية؛ ولم تتأثر أجهزة المصادقة المذكورة هنا.\n2026-09-19 / 21-09\tSteam حالة مرشح الارتباط كما لاحظها المؤلفون\tأظهرت المجالات الرئيسية رقم 14 حظرًا في عملية إعادة الفحص 2026-09-21 المحفوظة — 26 زوجًا مقسّمًا في السجل بمقدار 2026-09-22 — في حين استمر الوكيل الذي يحمل كل عملية تسجيل دخول في العمل.\nالمصادر: Valve بيان بتاريخ 13 يوليو 2016 (store.steampowered.com/oldnews/22883، محفوظ 2026-09-21) · تقرير شركة CSFloat الهندسية عن الإغلاق الذي حدث عام 2017 (blog.csfloat.com، محفوظ 2026-09-21) · حالة مرشح الروابط: linkfilter-recheck-2026-09-21.json.\nيمكن دحض هذه النتيجة من خلال مثال واحد منشور، حيث رفض Valve طلب OpenID لأن openid.return_to تشير إلى مضيف مرخص لممارسة القمار. ولم يتم العثور على أي مثيل من هذا القبيل في السجلات العامة.\nأحدث تسجيلين لمضيف المصادقة\nhowl.unoتم تسجيله في 2026-08-11 (RDAP)، قبل 2026-09-21 بـ 41 يومًا؛ وأظهر موقع howl.gg حظرًا بواسطة «Link Filter» في 2026-09-18 و2026-09-19 و2026-09-21. ولم يتأكد بعد ما إذا كان الحظر قد سبق التسجيل أم لا.\nrbsnin.comتم تسجيله في 2026-09-18T09:34:52Z (Verisign RDAP) ولوحظ في مسار تسجيل الدخول Steam الخاص بـ Rollbit في 2026-09-20 من خلال إشعار صفحة تسجيل الدخول الخاصة بـ Steam؛ أرجع موقع rollbit.com حظرًا من «Link Filter» في 2026-09-19 و2026-09-21، بينما لم يفعل موقع rbsnin.com ذلك.\nيتم إرسال كل مضيف وارد في الجدول أعلاه إلى خوادم المصادقة الخاصة بـ Valve على النحو التالي: openid.realm عند كل محاولة تسجيل دخول.\nالبيانات الكاملة لكل مسار وقرارات «Link Filter»: الجدول الوارد في القسم 3 أعلاه؛ النتائج الأولية في linkfilter-recheck-2026-09-21.json و linkfilter-all-results.json.\nالمنهجية — كيفية تحديد أعداد المرشحات الخاصة بالمسارات والوصلات\n1. تحويل عناوين النطاقات\nأدى تدقيق 2026-09-21 إلى حل 78 من أصل 189 منصة مطلوبة: 33 منها تُجرى المصادقة على اسم المضيف الخاص بها و20 على النطاق الفرعي الخاص بها — وهي مصادقة مباشرة، ولا يُحسب أي منها كمسار لنطاق منفصل. الباقي 25 المصادقة من خلال نطاق منفصل قابل للتسجيل، موزعة على 24 اسم مضيفًا مختلفًا (يُشترك في dota2.net كل من market.csgo.com و rust.tm): 10 منها تم تحديدها من خلال التقاط مباشر لصفحة المتصفح، و3 من خلال إشعار صفحة تسجيل الدخول الخاصة بـ Steam، و12 من خلال عنوان URL لـ OpenID تم توفيره. السجل المباشر (master_registry.json، 2026-09-22) يوسع ذلك ليشمل 44 مسارًا لنطاقات منفصلة: 26 زوجًا من المسارات المقسمة حسب المرشح (النطاق الرئيسي «محظور»، مضيف المصادقة «سليم») بالإضافة إلى 18 مسارًا آخر دون تقسيم حسب النطاق الرئيسي. ومن بين الـ 44، 27 الاحتفاظ بملف أدلة لكل مسار؛ أما الـ17 الأخرى فقد تم جمعها يدويًّا وهي مُعلَّمة realm_src: user في السجل. تمت إضافة خمسة من هذه المواقع السبعة عشر — csgogem.com، وgamdom.com، و12cs.fail، وcsgolounge.com، وdota2lounge.com — في 2026-09-22 مع تسجيل من «Link Filter» لكلا المضيفين (HTML الخام + SHA-256 في linkfilter-2026-09-22.json)، لذا فإن الانقسام نفسه واضح على الرغم من أن المجال تم جمعه يدويًّا؛ وهي تظهر في الجدول أعلاه جنبًا إلى جنب مع مسارات ملفات الأدلة. tfauth.com (tf2easy.com) تم حذفه من السجل في 2026-09-22: ومثل موقع arena.fragnet.net، لا توجد أي روابط يمكن التحقق منها تربطه بموقعه الأصلي. ويمكن إعادة حساب العدد من البيانات المنشورة auth-route-audit.json (سلسلة 2026-09-21) وفقًا لقاعدة واحدة: لا تُحتسب المنصة إلا إذا كان مضيف OpenID الملحوظ Steam الخاص بها يقع على نطاق قابل للتسجيل يختلف عن نطاق المنصة نفسها.\n2. Steam حالة مرشح الروابط\nتم اختباره عبر steamcommunity.com/linkfilter/?url=https://[domain]، غير مصدق، على 2026-09-19 و2026-09-21؛ تم حفظ HTML الخام باستخدام SHA-256. تم تسجيل الحالة للنطاق الرئيسي ومضيف المصادقة بشكل منفصل. يقوم مصنف بالتمييز بين الإشعار العام «أنت تغادر Steam» (CLEAN) والصفحة «الرابط محظور! ... تم الإبلاغ عنه باعتباره خبيثًا محتملًا» (BLOCKED)؛ ويؤكد عنصر تحكم google.com عدم الخلط بين الاثنين. تم استبعاد نسخة سابقة تم توثيقها من هذا الاختبار بعد أن أظهرت نتيجة «محظور» لكل نطاق بما في ذلك عنصر التحكم المذكور — وتبين أن السبب هو ملف تعريف ارتباط جلسة غير صالح في البرنامج النصي للاختبار، وليس نتيجة حقيقية.\n3. مراقبة مضيف المصادقة\nالتسجيل المباشر: قام متصفح Playwright بالانتقال إلى عملية تسجيل الدخول الخاصة بكل منصة وـ openid.return_to تم قراءة اسم المضيف من الطلب الذي تم اعتراضه. ملاحظة بشأن صفحة تسجيل الدخول: تم قراءة اسم المضيف من صفحة \" الخاصة بـ Steam\"<host> ليس تابعاً لـ Steam أو Valve\" النص، الذي يُعرض بواسطة Steam من openid.realm (rbsnin.com، sc-auth.net، auth.dota.trade). رابط URL المُقدم: رابط URL لتسجيل الدخول a Steam تم تزويد المؤلفين به؛ ويحدد هذا الرابط معلمات الطلب، ولا يمثل عملية تسجيل دخول مكتملة. لم تتم عملية تسجيل دخول مكتملة على أي منصة.\n4. التغطية — ما لم يتم حله، وأهمية ذلك\nمن بين 189 منصة، 110 لم تسفر عن مسار محدد وكان هناك حالة واحدة غير قابلة للتطبيق (189 − 78 − 1). ولم يُدرج هذا الملف أيًّا منها. تفصيل الـ 110 حالة، من ملف التدقيق: 22 تحديًا للروبوتات، و14 حالة انتهاء المهلة، و12 خطأ HTTP، و10 أخطاء تنقل — لم يتمكن المراقب من الوصول إلى مسار تسجيل الدخول، على الرغم من أن معظم هذه المواقع تفتح بشكل طبيعي في متصفح عادي؛ 20 موقعًا لم تظهر فيها أي آلية تحكم في تسجيل الدخول على الصفحة المقصودة؛ و16 موقعًا وصلت إلى مسار تسجيل الدخول الذي تعذر تحويله إلى مضيف؛ و11 نطاقًا لم يتم تحويلها في نظام أسماء النطاقات (DNS)؛ و5 مواقع توقفت عند حاجز الموافقة. السجل أدناه يقسم نفس الـ110 بشكل مختلف: الـ11 التي لم يتم تحويلها في نظام أسماء النطاقات (DNS) مدرجة بشكل منفصل على النحو التالي: تمت إزالته · NXDOMAIN، والمدخلة الوحيدة غير القابلة للتطبيق تنضم إلى البقية. تم تدقيق 189 منصة، وتم حذف 11 منها نتيجة لرد NXDOMAIN نهائي من كلا المحللين، 178 تم الاحتفاظ بهم (platform-audit.json، platforms-removed.json). تم حذف 137 نطاقًا للتوثيق كان السجل قد خمّنها استنادًا إلى نمط التسمية من البيانات الموجودة في 2026-09-19 — لم يتم رصدها قط، وبالتالي لم تكن هناك أدلة عليها. تعارضت ثلاثة من التخمينات مع عناوين URL الخاصة بـ OpenID التي تم توفيرها: حيث يتم المصادقة مباشرةً عبر buff.163.com وgamerpay.gg وcsgoluck.com، في حين كانت التخمينات تشير إلى buffauthproxy.163.com وgamerpayredirect.io وlucklogin.app. وترد قائمة بحالات الحذف في ملف التدقيق المنشور.\nالرقم 25 يمثل الحد الأدنى، وليس الحد الأقصى. ومن بين المنصات الـ78 التي تم حل مشكلتها، استخدمت 25 منها نطاقًا منفصلاً، بينما لم تستخدم 53 منها نطاقًا منفصلاً. ولا يُستنتج أي شيء بشأن المنصات الـ110 التي لم يتم حل مشكلتها من هذه النسبة، كما لا يرد أي توقع مستمد منها في أي مكان في هذا الملف. يمكن حل كل حالة منها عن طريق قيام شخص بفتح الموقع والضغط على «تسجيل الدخول باستخدام Steam»: حيث يظهر اسم مضيف المصادقة في عنوان URL للصفحة Steam التي يتم تحميلها.\nالهدف من هذا القسم: يحتاج المراقب المستقل إلى متصفح وكثير من الصبر لتحديد 189 منصة، وقد تمكن من تحديد 78 منها. يتطلب Valve استعلامًا عن قاعدة البيانات. كل منصة تستخدم خيار «تسجيل الدخول باستخدام Steam» — سواء تم تحديدها أم لا — ترسل openid.realm إلى نقطة نهاية المصادقة الخاصة بـ Valve عند كل عملية تسجيل دخول. وتوجد فجوة في هذا الجدول لأن المؤلفين خارج النظام. ولا توجد هذه الفجوة بالنسبة لـ Valve.\nتوجد أسماء المضيفين البديلة التي تم رصدها في auth-route-audit.json. تواريخ تسجيل النطاق من RDAP (Verisign) / IP2WHOIS. نتائج تصفية الروابط في linkfilter-all-results.json.\nمثال توضيحي\n\nتخيل أن الجهات التنظيمية أبلغت شركة سيارات أجرة مرخصة بأنها لم تعد مسموحة بالعمل من عنوانها المسجل في «الشارع الرئيسي». فقامت الشركة بإزالة اللافتة من «الشارع الرئيسي». وتم توثيق عملية إزالة تلك اللافتة. ومع ذلك، فتحت الشركة نفسها عنوانًا في «الشارع الجانبي» — مسجلاً باسم مختلف — وواصلت العمل من هناك. تدير الجهات التنظيمية نظام التوزيع المركزي الذي تستخدمه جميع سيارات الأجرة من كلا العنوانين. ويظهر في كل طلب توصيلة «الاستقبال من شارع سايد ستريت». ولم تقم الجهات التنظيمية أبدًا بإلغاء ترخيص شارع سايد ستريت. كان إزالة لافتة «ماين ستريت» الإجراء التنفيذي الوحيد الذي تم اتخاذه. ولم تتوقف شركة سيارات الأجرة عن العمل مطلقًا.\n\nالجزء أ — السجل الفني · القسم 3.1\nداخل Steam، قائمة Valve هي القائمة الوحيدة.\n\nالرابط الذي يتم النقر عليه في عميل Steam، أو في واجهة العرض المدمجة داخل اللعبة، أو في وضع Big Picture، لا يُفتح في متصفح المستخدم. بل يتم عرضه داخل المتصفح المدمج الخاص بـ Steam — حيث لا توجد طبقات التحذير التي عادةً ما يطبقها المتصفح. «مرشح الارتباط» ليس مجرد إجراء وقائي واحد من بين عدة إجراءات، بل هو الإجراء الوقائي بأكمله.\n\nفي متصفح عاديثلاث طبقات مستقلة\nالتصفح الآمن من جوجلصفحة فاصلة تشغل المساحة الكاملة للمضيفات المدرجة في قوائم جوجل الخاصة بالتصيد الاحتيالي والبرامج الضارة، ويتم تحديثها باستمرار وبشكل مستقل عن الموقع الذي تتم زيارته.\nملحق المتصفح المضاد للفيروساتتأتي معظم منتجات النقاط الطرفية المخصصة للمستهلكين مزودة بملحق متصفح يقوم بمقارنة الوجهة بقائمة السمعة الخاصة بالشركة المصنعة.\nفحص HTTPS لنقاط النهايةعندما يقوم المنتج بفحص TLS، يتم فحص محتوى الصفحة قبل وصوله إلى المستخدم.\nفي عميل Steam، ميزة التراكب و«Big Picture»طبقة واحدة\nالتصفح الآمن من Googleغير موجود. يتطلب هذا الفحص مفاتيح واجهة برمجة تطبيقات Google التي لم يتم توفيرها في إصدارات Chromium المدمجة؛ وفي حالة عدم وجودها، تشير وثائق تصميم Chromium نفسها إلى أن معالج «التصفح الآمن» لا يُضاف أبدًا إلى سلسلة الطلبات.\nملحق المتصفح المضاد للفيروساتغير موجود. برنامج العرض الخاص بـ Steam ليس متصفح المستخدم ولا يقوم بتحميل أي ملحق من ملف تعريف متصفح المستخدم، لذا لا يتم تشغيل أي ملحق على الصفحة.\nفحص HTTPS لنقاط النهايةيعتمد ذلك على المنتج. حيث تنتهي حركة المرور داخل عملية موقعة برمز Valve بدلاً من متصفح معروف، كما أن عددًا من منتجات نقاط النهاية تستثني التطبيقات الموقعة من فحص TLS.\nمرشح الروابط Steamقائمة الحظر الخاصة بـ Valve، والتي يتم الرجوع إليها عندما يغادر رابط ما نظام Steam. هذه هي الفحص الوحيد الذي يتم إجراؤه — ويوثق الجدول أعلاه النتائج التي يعرضها هذا الفحص بالنسبة لمضيفي المصادقة المذكورين في هذا القسم.\nاختبار يمكن لأي قارئ إجراؤه، وتُستبعد النتيجة في حالة فشله\n\nافتح أحد عناوين URL الخاصة باختبار «التصفح الآمن» التي نشرتها Google (testsafebrowsing.appspot.com) في متصفح Chrome: تظهر نافذة منبثقة حمراء تشغل الصفحة بأكملها. افتح نفس عنوان URL من رسالة دردشة Steam، بحيث يتم عرضها في عميل Steam أو في الطبقة التراكبية: لا تظهر أي نافذة منبثقة. التحذير الوحيد الذي يمكن أن يصدره Steam هو صفحة «تصفية الروابط» الخاصة به، ويقتصر ذلك على المضيفين المدرجين في قائمة Valve.\n\nرقم Valve القياسي في برنامج مكافآت اكتشاف الأخطاءوقد تم التغلب على مسألة الطبقة الواحدة من قبل — في ألبوم Valve نفسه\n\nإذا كان «مرشح الارتباط» هو الفحص الوحيد الذي يتم تنفيذه داخل العميل، فإن أوجه الفشل الخاصة به لا تُعد مسألة ثانوية. وهناك تقريران على برنامج «HackerOne» الخاص بـ Valve، وقد تم قبول كلاهما وحلّهما، وتم الكشف عن تفاصيلهما بالكامل منذ ذلك الحين:\n\n#291750محفوظ 2025-11-16 ↗إعادة التوجيه المفتوح · medium\nتجاوز حماية مرشح الارتباط\n\nتم الإبلاغ عنها في 19 نوفمبر 2017، وتم حلها، وتم الكشف عنها في 9 مايو 2018. دليل صحة المفهوم الوارد في التقرير نفسه: استبدال النقطة الأيديوغرافية 。 (%E3%80%82) للإشارة إلى النقطة في اسم المضيف — من الممكن تجاوز الحظر. لم يظهر المحتوى الفاصل الذي يتناوله هذا القسم.\n\n#1079561محفوظ 2026-09-24 ↗الإفصاح عن المعلومات · مرتفع\nمتصفح الويب «Big Picture» يتسبب في تسرب ملفات تعريف الارتباط الخاصة بتسجيل الدخول ويكشف معلومات حساسة (مما قد يؤدي إلى الاستيلاء على الحساب)\n\nتم الإبلاغ عنها في 15 يناير 2021، وتم حلها، وتم الكشف عنها في 21 سبتمبر 2021. تصنيف خطورة Valve نفسه مرتفع، ويشير العنوان إلى العواقب. يحتوي السجل الذي تم الكشف عنه على العنوان والتصنيف والتواريخ؛ ولا يتضمن المحتوى المنشور التقرير الفني، لذا لم يتم اقتباس أي شيء آخر منه هنا.\n\nهذا هو تفسير المؤلفين، وليس استنتاجًا واردًا في أي من التقريرين: يقع الاثنان على جانبي البوابة نفسها. الأول هو التحذير الذي لا يظهر قبل فتح الوجهة؛ والثاني هو خروج الجلسة من العميل بمجرد فتح صفحة داخلها. التسلسل الذي يتبع سرقة الجلسة — تسجيل المفتاح دون مطالبة، وإلغاء الصفقة الحقيقية، وإرسال نسخة مكررة إلى نسخة مقلدة — هو النمط المبين في القسم 5 إلى القسم 8. تم إغلاق كلا التقريرين؛ ولم يُصنف أي منهما على أنه ثغرة أمنية نشطة. وما يثبتانه هو أمر أضيق نطاقًا ولكنه كافٍ: فالطبقة الوحيدة المتبقية لها سجل موثق بالتحايل عليها، وفقًا لسجل Valve نفسه.\n\nالمصدر: سجل الإفصاح الخاص بـ HackerOne لكل تقرير، تم استرجاعه 2026-09-22 — الرقم، العنوان، الفريق، الثغرة الأمنية، درجة الخطورة، تواريخ التقرير والإفصاح، والحالة كما نشرتها HackerOne. سجل الاسترجاع: hackerone-reports.json. لم يُذكر هنا أي مبلغ للمكافأة؛ ولا يرد أي مبلغ في السجل المُفصح عنه الذي تم استرجاعه.\n\nالمراقبة الميدانية · PhishDestroyعمليات الكشف التي عادةً ما تنهي الحملة لم تنه هذه الحملات\n\nشاهدنا خوادم التصيد الاحتيالي وهي تواصل جذب حركة المرور بينما تحمل 20 حالة اكتشاف مورد أو أكثر. عندما يتم إرسال حملة من هذا النوع عبر الويب أو البريد الإلكتروني، فإنها تفشل في غضون أيام — حيث يتصرف كل من المتصفح وبرنامج مكافحة الفيروسات بناءً على تلك الأحكام. أما داخل Steam، فلا يحدث أي منهما. فقد كانت تلك الأحكام موجودة طوال الوقت. ولم يطلب العميل أي شيء على الإطلاق.\n\nماذا يعني ذلك بالنسبة للقاصر الذي لديه برنامج مكافحة فيروسات مثبت على جهازه\n\nلا يتجاهل أي تحذير ولا يعطل أي شيء. تصل رسالة داخل Steam — سكين مجاني، تصويت لصالح فريق أحد الأصدقاء — وتُفتح الصفحة داخل Steam. إنه لا يفتح متصفحًا أبدًا، لذا لا يحميه المتصفح أبدًا. برنامج مكافحة الفيروسات الخاص به قيد التشغيل وربما يكون قد صنف هذا النطاق بالفعل على أنه ضار؛ لكنه لم يُطلب منه ذلك أبدًا. كل التحذيرات التي كان من الممكن أن تمنعه موجودة بالفعل. لكن لا شيء منها يصل إليه. إنه يعتقد أنه لم يغادر Steam قط، وهو بالفعل لم يغادرها.\n\nهذه العروض المجانية ليست من ابتكار المخادع — فـ«0» من العناصر المجانية هي الطريقة التي تستخدمها مواقع الأزياء والمقامرة في الإعلان عن نفسها، وهذا بالضبط هو السبب في أن الرسالة تبدو عادية. الشكاوى: أرشيف الإجراءات التنفيذية. بيانات العمر والأطفال: المادة 17.\n\nالمصادر: Steam يعرض محتوى الويب من خلال «إطار عمل كروميوم المدمج» في steamwebhelper العملية — انظر التحليل الفني لـ DARKNAVY بتاريخ 27 يونيو 2024 ↗ والمسؤولية تقع على عاتق Valve Steam منتدى إصدار بيتا للعملاء ↗ محفوظ 2025-08-04 ↗. لا يتم الاعتماد على أي إصدار من CEF: فـ Chromium المدمج ليس Chrome ولا يتضمن أيًا من خدمات Google الخاصة بـ Chrome. التصفح الآمن بدون مفاتيح API: وثيقة تصميم Chromium ↗ محفوظ 2026-08-21 ↗، مفاتيح واجهة برمجة التطبيقات (API) لـ Chromium ↗ محفوظ 2026-08-30 ↗ (“العديد من واجهات برمجة التطبيقات (API) الخاصة بـ Google التي يستخدمها متصفح Chrome هي واجهات خاصة بـ Google وليست مخصصة للاستخدام في المنتجات المشتقة منها”)، ونفس التأثير في الإصدارات الأخرى غير المُشفَّرة — برميل من إنتاج محلي رقم #193814 ↗. عناوين URL للاختبار: testsafebrowsing.appspot.com ↗.\n\nساعتان مختلفتان\nعمر النطاق.تاريخ الملاحظة.\n\nيحدد تاريخ إنشاء السجل الوقت الذي تم فيه تسجيل النطاق. ويحدد سجل OpenID المؤرخ المضيف المرتبط بذلك السجل. ولا يمكن للأول أن يغطي السنوات التي سبقت الثاني.\n\nيميز السجل الكامل بين النطاق القابل للتسجيل المستقل، والنطاق الفرعي الخاص بالموقع، والمسار المباشر. ويرتبط كل صف بمصدره ونتيجة DNS.\n\nافحص سجل النطاق →· تنزيل تواريخ التسجيل ↗· إعادة إجراء الملاحظة ↗\n\nالجزء أ — السجل الفني · القسم 4\nتم إغلاق نقطة نهاية. فقد نظام التتبع العام مفتاحًا.\nالسياق وحدود المصدر\n\nSteam تم إصدار تحديثات أزالت إمكانية الاطلاع العام على معرّفات الأصول (Asset IDs) وقيدت الوصول إلى المخزون عبر واجهة برمجة التطبيقات (API). النتيجة: أصبح من المستحيل تتبع عنصر معين باستخدام معرّف الأصول الأصلي الخاص به من خلال البيانات العامة. فيما يلي ما كان ممكنًا من قبل، وما لم يعد ممكنًا بعد ذلك، وما يكلفه ذلك للضحية التي تحاول إثبات أين ذهبت ممتلكاتها. التاريخ هو عام 2017 وفقًا لحساب الهندسة الخاص بـ CSFloat؛ ولم يتم العثور على سجل تغييرات لـ Valve. هذا التسلسل — الذي حدث بعد حوالي عام من بيان المقامرة الصادر في يوليو 2016 — يمثل السؤال التحقيقي، وليس استنتاجًا. تظل سجلات العناصر نفسها داخل أنظمة Valve؛ فقد المحققون الخارجيون إمكانية الوصول إلى سلسلة المعرّفات الأصلية، في حين أن معرّفات float و seed و paint لا تسمح إلا بمطابقة جزئية.\n\nتنطبق القاعدة Valve: Steam لا يقوم قسم الدعم باستعادة العناصر التي غادرت حسابك، ويقع على عاتقك عبء إثبات ما حدث. السجل: في عام 2017، أغلقت Valve النقطة الطرفية التي كانت تنقل معرّفات العناصر الأصلية. وقبل ذلك، كان بإمكان أي شخص تتبع مسكن مسروق من حساب الضحية وصولاً إلى روبوت في السوق. وبعد ذلك، لم يعد بإمكان أي شخص خارج Valve القيام بذلك. الوثيقة المطلوبة من الضحية هي تلك التي تم إيقاف تشغيلها — وما زال موجودًا، داخل Valve.\n\nحقبة ما قبل انقطاع التيار الكهربائي\n\nتاريخياً، كان كل عنصر افتراضي يتم إنشاؤه على Steam يتمتع برقم فريد عالمي وغير قابل للتغيير معرّف الأصل. يمكن لقواعد بيانات OSINT التابعة لأطراف ثالثة فهرسة هذه المعرّفات. فإذا تعرض أحد المستخدمين لسرقة أحد أصوله، يمكن للمحققين تتبع مسار ذلك الأصل المحدد أثناء انتقاله من الحساب الوسيط الخاص بالخاطف إلى حسابات التخزين التابعة لإحدى المنصات التجارية أو مواقع المقامرة.\n\nفي السابق: كان بإمكان أي شخص، باستخدام البيانات العامة، تتبع مسار أحد العناصر من حساب الضحية مروراً بحسابات وسيطة وصولاً إلى منصة تداول أو روبوت تخزين في كازينو.\nبعد التغيير\n\nوفقًا لحساب CSFloat الهندسي، أغلقت Valve نقطة النهاية في عام 2017، وتوقف إتاحة معرّفات العناصر الأصلية للأطراف الخارجية. ولم يتم العثور على أي بيان Valve يوضح سبب هذا التغيير. وفي الفترة نفسها، لم يتم العثور أيضًا على أي إجراء منشور ضد حسابات الروبوتات التجارية التي كانت تنقل العناصر على نطاق واسع.\n\nأياً كان السبب وراء ذلك، فقد أدى هذا التغيير إلى قطع سلسلة الحراسة العامة. لم يعد بإمكان الضحية إعادة تكوين سلسلة المعرّفات الأصلية من البيانات العامة لإثبات أن سلعة مسروقة معينة تم بيعها عبر سوق أو كازينو معين. لا تزال سجلات هذه السلعة موجودة داخل أنظمة Valve؛ لكن الجمهور والباحثين وسلطات إنفاذ القانون الذين يعملون انطلاقًا من البيانات العامة لا يمكنهم الوصول إليها.\n\nبعد ذلك: لم يعد من الممكن تتبع عنصر معين باستخدام معرّف الأصل الأصلي الخاص به من خلال البيانات العامة. ولا توجد سلسلة حيازة المعرّف الأصلي لأي عنصر تم نقله بعد عام 2017 إلا داخل البنية التحتية لـ Valve؛ ولم يتم نشر أي سجل من هذا القبيل علنًا. لا تسمح معرّفات «فلات» و«سييد» و«بينت» إلا بمطابقة جزئية واحتمالية.\nIEconItems_730\nاحصل على/IEconItems_730/GetPlayerItems/v1/\nحمولة قابلة للتتبع (قبل إصدار التصحيح)\n\"id\": \"14892281934\",\n\"original_id\": \"11829910211\",\nالحالة: يمكن للضحية تتبع مسار العنصر عبر حسابات الروبوتات.\nحمولة مشوشة (بعد التحديث)\nالحالي\n\"id\": \"HIDDEN_BY_PRIVACY_SETTINGS\",\n\"original_id\": \"NULL\",\nالحالة: لم يعد بإمكان الأطراف الخارجية تتبع مسار العنصر باستخدام معرّف الأصل الأصلي من البيانات العامة.\nالتأثير على الأدلة: بعد التغيير، لم تعد البيانات العامة اللازمة لتتبع عنصر معين باستخدام معرّف الأصل (Asset ID) الأصلي الخاص به من حساب الضحية إلى روبوت في سوق أو كازينو متاحة. لا تزال السجلات الداخلية موجودة في Valve؛ ولا يمكن للضحية أو الباحث أو المحقق الذي يعمل استنادًا إلى البيانات العامة إعادة إنشاء سلسلة معرّف الأصل (حيث لا تسمح معرّفات float و seed و paint إلا بمطابقة جزئية).\n\nالمصدر: تقرير شركة CSFloat الهندسية حول إغلاق عام 2017 لـ IEconItems_730/GetPlayerItems — blog.csfloat.com/how-floatdb-tracks-items (محفوظ 2026-09-21) · الحمولات المعروضة هي مجرد توضيح لشكل الحقل، وليست استجابات تم تسجيلها · لم يتم العثور على سجل تغييرات Valve خاص بهذا الإغلاق.\n\nالجزء أ — السجل الفني · القسم 5\nجلسة واحدة. إمكانية وصول أكبر مما يراه المستخدم.\nالسياق وحدود المصدر\n\nكانت بنية مفتاح واجهة برمجة التطبيقات (API-key) الخاصة بـ Valve، كما كانت قبل التغييرات التي أُجريت في عام 2023، تختلف عن المعايير الأساسية للصناعة (OWASP ASVS، NIST SP 800-63B)، وهي الآلية الموصوفة في الشكاوى الآلية المتعلقة بسرقة المخزون المحفوظة في أرشيف الأدلة (الأقسام 6–8).\n\nتم تطبيق القاعدة Valve: قام صاحب الحساب بإنشاء المفتاح، ووافق على الشروط، ويتحمل الخسارة — هذا هو الجواب الوارد في حالات الرفض المؤرشفة. السجل: حتى ديسمبر 2023، كان من الممكن تسجيل هذا المفتاح بمجرد ملف تعريف ارتباط الجلسة المسروق وحده. بدون كلمة مرور. بدون Steam Guard. وبدون إخطار صاحب الحساب. لم يقم المستخدم بإنشاء المفتاح، ولم يتمكن من رؤيته، ومع ذلك قيل له إنه فعل ذلك. أُضيفت ميزة التأكيد عبر الهاتف المحمول في 2023-12-04 — أي بعد حوالي سبع سنوات من بيان عام 2016، وحوالي ست سنوات بعد لوحات الاحتيال التي يحتفظ بها الأرشيف. ولم يتم دفع تكاليف تلك السنوات من قبل Valve، بل تم دفعها من الحسابات التي أُفرغت في تلك الأثناء، وكان جزء منها يخص أطفالًا.\n\nOWASP ASVS 2.8 / NIST SP 800-63Bدرجة الخطورة: حرجة\n1. عدم كفاية المصادقة المتدرجة\n\nSteam سمح بإنشاء مفاتيح API ذات امتيازات عالية وذات صلاحية طويلة باستخدام ملف تعريف ارتباط الجلسة فقط. لم يكن هناك حاجة إلى المصادقة الثنائية (Steam Guard) أو تحدي المصادقة المعززة عند إعداد مفتاح واجهة برمجة التطبيقات للمطور أو تعديله، لذا فإن التأكيد عبر الهاتف المحمول Steam Guard — وهو العامل الثاني الوحيد الذي يقدمه Steam — لم يحمِ هذه الخطوة. (تم طلب عامل ثانٍ عبر جهاز في أداة التتبع الخاصة بـ Valve في عام 2016، ولا تزال المشكلة قائمة: الملحق د، GH-01.)\n\nالحالة: لم يتم إصلاح الثغرة قبل عام 2023. كانت تسمح لبرنامج نصي يحتوي على ملف تعريف ارتباط مسروق بتسجيل مفتاح دون أي تفاعل من المستخدم.\nOWASP A01:2021 / مبدأ الحد الأدنى من الصلاحياتدرجة الخطورة: حرجة\n2. عدم تطبيق مبدأ «أدنى مستوى من الصلاحيات»\n\nكانت واجهة برمجة التطبيقات (API) Steam تفتقر إلى أي نطاقات تفويض قائمة على الأدوار. فقد كان مفتاح API الخاص بالمطور، الذي تم إصداره لحالة المخزون «للقراءة فقط»، يتمتع بأذونات «كتابة» كاملة — بما في ذلك القدرة على تعديل الصفقات القائمة، وبدء صفقات جديدة، وتسجيل «webhooks»، ورفض عمليات التبادل المعلقة الصالحة.\n\nالحالة: عيب تصميمي نظامي. مفتاح واحد = تحكم كامل في القراءة والكتابة على مخزون الحساب ومعاملاته.\nOWASP A07:2021 / الجلساتدرجة الخطورة: عالية\n3. خلل في إدارة الجلسات\n\nأبلغ المستخدمون عن استمرار جلسات الويب المخترقة التي تنشأ من نطاقات عناوين IP الخاصة باستضافة الخوادم. وتتمثل الممارسة المعتادة في إنهاء الجلسات عند حدوث حالات شذوذ جغرافي وعند تغيير كلمة المرور؛ وتصف تقارير المستخدمين المجمعة في الأرشيف جلسات ظلت نشطة بعد تغيير كلمة المرور.\n\nالحالة: سلوك تم الإبلاغ عنه (شكاوى المستخدمين في الأرشيف). كان من الممكن إنشاء مفاتيح واجهة برمجة التطبيقات (API) خلال الجلسات دون الحاجة إلى إعادة المصادقة.\nكان الحجب على مستوى النطاق ممكنًا من الناحية التقنيةجدوى التنفيذ\n4. كان حجب مضيفي المصادقة على مستوى النطاق أمراً ممكناً من الناحية التقنية\n\nValve تُشغّل بالفعل قائمة نطاقات (تُعرف باسم «Link Filter») وتتلقى بالفعل كل اسم مضيف مصادق عليه في طلبات OpenID الخاصة بها. ولا توجد أي صلة بين الآليتين يمكن ملاحظتها من الخارج: اعتبارًا من 2026-09-22، كان النطاق الرئيسي مدرجًا في المرشح في 26 زوجًا، في حين أن الوكيل الذي يحمل معلومات تسجيل الدخول الخاصة به لم يكن مدرجًا فيه.\n\nيُعد ربطهما مهمة هندسية بسيطة: اقرأ openid.realm اسم المضيف من كل طلب وارد، ومقارنته بقائمة، ثم رفض الطلب أو وضع علامة عليه. يوضح الرسم التوضيحي على اليمين شكل هذا الإجراء. إن رفض مضيف المصادقة — بدلاً من الاكتفاء برفض الصفحة الرئيسية العامة — من شأنه أن يعيق خطوة «تسجيل الدخول باستخدام Steam» التي تعتمد عليها هذه المنصات.\n\nلا توجد أدلة علنية تُشير إلى أن Valve تجري مثل هذا الفحص. وتُطبق الرسوم الإجمالية لسوق Steam المجتمعي، والتي تبلغ حوالي 15%، على المبيعات التي تتم داخل السوق؛ ولا يتم تحصيلها على الصفقات الخارجية لهذه المنصات.\n\nblock_auth_hosts.pyرسم توضيحي\n// قراءة المضيف Steam الذي يتلقى بالفعل — لا حاجة للمسح\ndef on_openid_request(request):\nhost = parse_openid_realm(request)\nإذا المضيف في المجالات المحظورة:\nرفض (الطلب)\nملاحظة: كود زائف لأغراض التوضيح فقط. كلا النصفين موجودان بالفعل في Valve — حيث يصل اسم مضيف المصادقة في الطلب، وقائمة النطاقات هي «مرشح الارتباط». ولا يوجد أي سجل عام يفسر سبب عدم ارتباطهما ببعضهما.\nالقسم 5.1 — لم يتم سحب المعايير من النشر\nValve يتم تجميعه وفقًا لهذه القواعد يوميًا. لكنه لم يتم تجميعه وفقًا لها هنا.\n\nSteam متوفرة على متجر «App Store» و«Google Play»، وتبيع منتجاتها عبر كبرى شركات معالجة المدفوعات بالبطاقات، وتستخدم واجهات برمجة التطبيقات (API) الخاصة بأطراف ثالثة مثل أي منصة كبيرة أخرى. وترتبط كل علاقة من هذه العلاقات بمتطلبات أمنية منشورة ومحددة التاريخ يجب على Valve الوفاء بها لمواصلة عملها. قارن تواريخ تلك المتطلبات بالتواريخ التي حصلت فيها واجهة برمجة تطبيقات الويب الخاصة بـ Steam على نفس الحماية. لا يوجد في ما يلي أي معيار خاص أو مذكرة داخلية أو سر تجاري: فكل صف هو وثيقة عامة لها تاريخ نشر.\n\nمتطلبات الأمان الخارجية المنشورة، مع تواريخها، مقارنةً بتاريخ حصول واجهة برمجة تطبيقات الويب Steam على التدبير المكافئ\nالمعيار المنشور، وتاريخ دخوله حيز التنفيذ\tواجهة برمجة تطبيقات الويب Steam حول السؤال نفسه\nالتفويض المحدد النطاقOAuth 2.0 — RFC 6749، أكتوبر 2012. يحدد القسم 3.3 scope وبالتالي، لا يحصل العميل إلا على صلاحيات الوصول التي يطلبها. وقد أصبح هذا هو الإعداد الافتراضي لكل واجهة برمجة تطبيقات (API) للمنصات الكبرى منذ ذلك الحين.\tظهرت نطاقات الحبيبات في 16 يناير 2026.وقبل ذلك، كان مفتاح واجهة برمجة التطبيقات (Web API) الفردي Steam يمنح صلاحيات القراءة والكتابة الكاملة على صفقات الحساب، بغض النظر عن سبب إصداره. ثلاثة عشر عامًا وثلاثة أشهر بعد المواصفات التي تحدد عنصر التحكم.\nالمفتاح ليس ترخيصًاوثائق «Cloud» الخاصة بشركة «Google»: مفتاح واجهة برمجة التطبيقات (API) القياسي لا يقوم بمصادقة الكيان، وبالنسبة لواجهات برمجة التطبيقات (API) التي تقوم بإنشاء الموارد أو إدارتها، لا تستخدم مفاتيح التفويض في بيئة الإنتاج.\tكان مفتاح واجهة برمجة التطبيقات (Web API) Steam هو ذلك بالضبط.سلسلة حامل، صادرة لحساب ما، تكفي بحد ذاتها لقراءة رصيد الحساب، وإلغاء صفقة معلقة، وإرسال صفقة جديدة. ولم يتم التحقق من هوية صاحب الحساب عند نقطة الاستخدام.\nالمصادقة متعددة العوامل على الوصول ذي الامتيازاتمعيار PCI DSS 3.2، الشرط 8.3 — إلزامي اعتبارًا من 1 فبراير 2018 لجميع عمليات الإدارة التي لا تتم عبر وحدة التحكم وجميع عمليات الوصول عن بُعد إلى بيئة بيانات حاملي البطاقات. ثم اشترطت شركة آبل تطبيق المصادقة الثنائية على كل صاحب حساب في برنامج المطورين بدءًا من 27 فبراير 2019: سيتعين على المطورين الذين يحملون دور «صاحب الحساب» في أحد برامج المطورين تفعيل المصادقة الثنائية لتسجيل الدخول.\tكان هناك عامل ثانٍ ضروري لإنشاء مفتاح واجهة برمجة التطبيقات (API) من 4 ديسمبر 2023.وحتى ذلك الحين، كان يكفي وجود ملف تعريف ارتباط جلسة مسروق، دون ظهور أي رسالة على هاتف صاحب الحساب ودون إرسال أي إشعار لاحقًا. أربع سنوات وتسعة أشهر بعد أن فرضت شركة آبل على نفسها استخدام عامل تأكيد ثانٍ لمجرد تسجيل الدخول إلى بوابة المطورين.\nدورة حياة بيانات الاعتماد وإلغاؤهاتشترط منصة Twitch على كل تطبيق تابع لجهة خارجية ما يلي: يجب أن يقوم تطبيقك بالتحقق من صحة رمز OAuth عند بدء تشغيله، ثم كل ساعة بعد ذلك، وتشير إلى أنها تقوم بمراجعة التطبيقات التي لا تلتزم بذلك. وقد تم إيقاف تشغيل واجهة برمجة التطبيقات (API) القديمة من الإصدار 5 بشكل نهائي في 28 فبراير 2022 وفقًا لجدول زمني منشور.\tلا توجد سجلات منشورة عن دورة حياة المفتاح.أدى التغيير الذي أُجري في عام 2023 إلى حماية نقطة نهاية الإنشاء. لم يتم العثور على أي بيان Valve يتعلق بها يتناول المفاتيح المسجلة مسبقًا، ولم يرافق هذا التغيير أي سجل تغييرات على الإطلاق. ولا يمكن تحديد ما إذا كانت المفاتيح التي تم إنشاؤها قبله قد أصبحت غير صالحة من خلال البيانات العامة — وهو السؤال الذي يحتاج صاحب البيانات إلى إجابة عليه لمعرفة ما إذا كان المفتاح الذي تم إنشاؤه على حسابه منذ سنوات لا يزال ساريًا.\nمعيار معماري // توكن أركيتكتشر\nنطاقات GitHub الدقيقة مقابل Valve Steam واجهة برمجة تطبيقات الويب\n\nValve مطورًا يديرون برامج مفتوحة المصدر على GitHub يوميًا باستخدام رموز وصول دقيقة تعتمد على مبدأ «أدنى امتياز ممكن». قارن ذلك بالمفتاح الموحد الذي تم إصداره لـ 130 مليون Steam لاعب.\n\nرمز GitHub الدقيق\nيستخدمه Valve على GitHub\n\nرمز ذو تفاصيل دقيقة مع عزل محدد النطاق وفرض إلزامي لدورة الحياة.\n\nالوصول إلى المستودع:مستودعات مختارة فقط (مستودع واحد)\nإصدار الأذونات:للقراءة فقط [✓]\nالكود والأسرار:لا يمكن الوصول [✕]\nتاريخ انتهاء الصلاحية:30 يومًا (مدة صلاحية إلزامية)\nتسجيل عمليات التدقيق:عنوان IP، وكيل المستخدم، والطابع الزمني\nالوضع الأمني: يحد رمز «أدنى مستوى من الامتيازات» من الضرر ليقتصر على مورد واحد للقراءة فقط.\n!Valve Steam مفتاح واجهة برمجة التطبيقات (Web API)\nتم إصدارها لـ 130 مليون مستخدم\n\nسلسلة رئيسية واحدة مكونة من 32 حرفًا تمنح صلاحية التداول والمخزون بشكل كلي أو لا شيء.\n\nالوصول إلى الحساب:التقرير الكامل (متكامل)\nإدارة التجارة:قراءة، إلغاء، رفض [!]\nنطاقات الحبيبات:لا شيء (وصل عام 2026، متأخرًا 13 عامًا)\nتاريخ انتهاء الصلاحية:أبدًا (صالح إلى أجل غير مسمى)\nتسجيل عمليات التدقيق:لا شيء (لا يوجد سجل عناوين IP للمستخدم)\nنقطة الضعف: يتيح المفتاح المسروق اعتراض جميع عروض التداول الصادرة دون أن يُلاحظ أحد.\nالمعيار المطبق في اتجاه واحد\n\nلنفترض أن مزودًا Valve — سواء كان مزود خدمة سحابية، أو معالج مدفوعات، أو شبكة توزيع المحتوى (CDN) — ترك نقطة نهاية لبيانات الاعتماد دون عامل تأكيد ثانٍ، وبعد أشهر تسربت بيانات شركة Valve نفسها عبر مفتاح تم إنشاؤه في تلك النقطة. هل سيقبل Valve أن الخطأ يقع على عاتق من نقر على الرابط؟ إن حالات الرفض المؤرشفة والمحفوظة في هذا الملف تجيب على السؤال المطابق بالنسبة للمستخدم: الموقف المتخذ هو أن صاحب الحساب هو من أنشأ المفتاح ويتحمل الخسارة. يُوصف هذا النموذج المعماري بأنه فشل المورد من جهة، ومسؤولية المستخدم من جهة أخرى. وكون الأمر كذلك ليس مسألة فنية، كما أنه ليس من الأمور التي يمكن لهذا التحقيق أن يحسمها — بل هو ما تقرره المحكمة أو السلطة الإشرافية.\n\nرسم توضيحي، وليس دليلاً — المعيار يُفهم على العكس\nنظام معالجة مدفوعات سمح لبرنامج نصي تابع لجهة خارجية بإنشاء بيانات اعتماد معاملة ذات صلاحيات كاملة استنادًا إلى ملف تعريف ارتباط المتصفح وحده، دون إخطار صاحب الحساب.\nمزود هوية قام بسد الثغرة التي تم من خلالها إصدار الرموز الخاصة به، ولم ينشر أي معلومات عن الرموز التي تم إصدارها بالفعل.\nقام أحد البنوك بالرد على عملية تحويل متنازع عليها بالإشارة إلى أن بيانات الاعتماد المستخدمة كانت مسجلة في حساب العميل نفسه، ثم أغلق القضية.\n\nولا يُقصد بأي من هذه الأمور أن يكون استنتاجًا بشأن أي شركة محددة. إنها نفس القرارات التصميمية، ولكن في سياق تكون فيه استجابة الجهة الإشرافية موثقة جيدًا — وهذه هي المقارنة التي يُطلب من الجهة التنظيمية إجراؤها.\n\nما يثبته السجل: كانت الضوابط الغائبة عن واجهة برمجة التطبيقات الويب Steam علنية وقديمة، وفي عدة حالات، كانت هناك شروط Valve كان على الشركة الوفاء بها لمواصلة شحن منتجاتها. والفاصل الزمني بين كل معيار والتغيير المكافئ Steam قابل للقياس ومبين أعلاه. ما لا يثبته هو السبب. لم يتم العثور على أي تفسير لأي من هذه الفترات الزمنية Valve، ولا يُفترض وجود أي تفسير هنا؛ فهذا السجل موجود داخل Valve ولم يتم نشره.\n\nالمصادر، وكل منها وثيقة عامة: OAuth 2.0 — RFC 6749، أكتوبر 2012 ↗ · Google Cloud — وثائق مفاتيح واجهة برمجة التطبيقات (API) ↗ · الشرط 8.3 من معيار PCI DSS 3.2 — دليل موارد PCI SSC ↗ · آبل — الشرط المرتقب للمصادقة الثنائية لأصحاب الحسابات، 20 فبراير 2019 ↗ محفوظ 2025-05-06 ↗ · تويتش — متطلبات التحقق من صحة الرمز ↗ وـ إشعار بإيقاف تشغيل الإصدار 5 ↗ محفوظ 2025-01-27 ↗. التواريخ الخاصة بـ Steam هي تلك الواردة في سجل التحديثات في هذا القسم؛ أما الإدخالات الخاصة بعامي 2023 و2026 فهي تلك التي أرسلها Valve دون سجل تغييرات. تم استرجاعها في 2026-09-22.\n\nسجل التحديثات الخاص بـ Valve — مؤرخ، من مصادر عامة\nالتاريخ\tValve تغيير\tهل تم الإعلان عن ذلك؟\tما الذي تم إغلاقه\tالتأخير: آلية عامة → تم الإصلاح\tالمصدر\n2026-09-01\tالإبلاغ الآلي عن المحادثات المشبوهة\tنعم\tروابط/أنماط خطيرة في الدردشات الجماعية\t—\tالأخبار ↗\n2026-01-16\tالنطاقات التفصيلية لواجهة برمجة تطبيقات الويب (Web API) لـ Steamworks\tنعم\tنطاقات \"أدنى مستوى من الامتيازات\" لمفاتيح المطورين\t—\tإعلان ↗\n2025-07-15\tCS2: الحماية التجارية ونافذة التراجع\tنعم\tلا شيء. هذا ليس إصلاحًا أمنيًا يعالج السبب الجذري. ولا يزال الوصول إلى استعادة الحساب من جانب الدعم دون تغيير. ويؤدي تشغيل عملية التراجع إلى فرض حظر تلقائي على التداول لمدة 30 يومًا (Skinvault ↗)، في حين تسببت صدمة التداول النقدي في انخفاض القيمة السوقية بمقدار $104M (-25%) خلال 24 ساعة (CSMarketCap ↗). في عام 2026، أصبحت المؤقتات تُحسب لكل عنصر على حدة (Skin.land ↗).\t—\tالأسئلة الشائعة ↗\n2025-05-14\tإعلان بشأن أمان الحساب\tنعم\tإرشادات بشأن برامج السرقة / اختطاف الجلسات\t—\tإعلان ↗\n2024-10-02\tCS2 «The Armory» — فترة حجز مدتها 7 أيام\tنعم\tتوقف التداول/السوق بالنسبة لمواد «أرموري»\t—\tإعلان ↗\n2024-09-18\tقيود التداول المتعلقة بتسجيل الدخول من جهاز جديد\tنعم\tتجميد التداول لمدة 2–7 أيام على الأجهزة الجديدة\t—\tالأسئلة الشائعة ↗\n2024-02-14\tتعليق تغيير اسم الملف الشخصي والصورة الرمزية\tنعم\tفترة انتظار مدتها 2–4 ساعات على المعاملات بعد تغيير الاسم\t—\tنشر ↗\n2023-12-04\tالتحقق عبر الهاتف المحمول لمفاتيح واجهة برمجة التطبيقات (API)\tلا يوجد سجل التغييرات\tتسجيل مفتاح صامت يعتمد على ملفات تعريف الارتباط فقط\tحوالي 6 سنوات بعد الألواح التي تعود إلى عام 2017\tصفحة المطورين ↗\n2023-10-24\tالرسائل القصيرة (SMS) MFA لنشر إصدارات الألعاب\tنعم\tنشر إصدارات Steamworks\t—\tإعلان ↗\n2023-07-12\tتحذير بشأن محتوى السيرة الذاتية المخصصة\tنعم\tروابط التصيد الاحتيالي في السير الذاتية\t—\tالمنتدى ↗\n2023-01-25\tالملف الشخصي {تم حذف الرابط} وفترة الانتظار\tنعم\tالروابط في نص الملف الشخصي\t—\tالأسئلة الشائعة ↗\n2022-10-24\tتجديد نظام تسجيل الدخول واقتطاع ملفات تعريف الارتباط\tلا يوجد سجل التغييرات\tعدد غير محدود من الجلسات المسروقة\t— (ترحيل الرمز المميز لـ IAuthenticationService)\tالأخبار ↗\n2022-10-12\tتطبيق الهاتف المحمول 3.0: تسجيل الدخول عبر رمز الاستجابة السريعة (QR)\tنعم\tلوحة إلغاء تفويض الجلسة\t—\tالأخبار ↗\n2022-05-10\tتمت إزالة نقاط النهاية الخاصة بإلغاء الصفقات\tلا يوجد سجل التغييرات\tتبادل العروض (الإلغاء وإعادة الإرسال)\tحوالي 5 سنوات بعد الألواح التي تعود إلى عام 2017\tالعدد رقم 325 ↗\n2020-05-25\tحظر التداول لمدة 7 أيام في Dota 2\tنعم\tالتداول السريع للسلع\t—\tمدونة ↗\n2018-03-29\tCS:GO: فترة حظر التداول لمدة 7 أيام\tنعم\tغسل أموال الروبوتات الفوري\tحوالي 20 شهرًا بعد البيان الصادر في يوليو 2016\tمدونة ↗ محفوظ 2025-02-26 ↗\nالمصادر: المنشورات المرتبطة Valve، وصفحات المساعدة، ومشكلات GitHub، حسب التواريخ المذكورة. ثلاثة إصلاحات حاسمة تم إصدارها دون سجل تغييرات (مايو 2022، أكتوبر 2022، ديسمبر 2023) واكتشفها المستخدمون، ولم تعلن عنها Valve — وهذا التباين جزء من سجل التنفيذ. يتم حساب فترات التأخير فقط عندما توفر التواريخ الواردة في الملف نفسه (بيان يوليو 2016؛ لجان الاحتيال في عام 2017) نقطة البداية؛ وتعني علامة «—» عدم تحديد نقطة بداية هنا.\nالجزء أ — السجل الفني · القسم 6\nمحاكي تفاعلي للاستغلال واختطاف الأنظمة\nالسياق وحدود المصدر\n\nإعادة بناء المسار بدءًا من رسالة التصيد الاحتيالي وصولاً إلى تسجيل المفتاح على جانب الخادم وإجراء عملية المقايضة. قبل عام 2023، كان بإمكان مفتاح واجهة برمجة التطبيقات (Web API) المسجل على حساب ما قراءة مخزونه، وإلغاء عرض تداول معلق وإنشاء عرض جديد، ولم تُعرض شاشة تأكيد التداول لصاحب الحساب لأي من هذه الإجراءات. وهذا يمثل غياب مبدأ «أدنى امتياز» (OWASP A01:2021). التوقيتات الواردة في هذه المحاكاة هي توضيحية وليست قياسات حية للمنصة الحالية.\n\nتتبع خطوات عملية الاختراق المُعادة تمثيلها. تُظهر كل مرحلة ما يراه صاحب الحساب، وبجانبها المكالمة التي يتلقاها الرقم Steam في نفس اللحظة. يتم التحقق من صحة كل مكالمة من تلك المكالمات بشكل صحيح. لا يوجد في هذه السلسلة ما يتطلب فشل مصادقة Steam — بل يتطلب ألا يكون للمفتاح الذي تصدره أي نطاق (OWASP A01:2021).\n\nما يراه اللاعب. وما يحدث خلفه.محاكي خطوة بخطوة\nالخطوة 5 / 5\n\nاكتملت عملية الاستغلال. توقعًا لوصول إشعار عبر الهاتف المحمول بشأن صفقتها الأصلية، وافقت الضحية على الصفقة البديلة. هذا عرض تفصيلي متكامل للتحليل الجنائي يوضح كيف أن عدم تطبيق مبدأ «أدنى مستوى من الصلاحيات» (OWASP A01:2021) يتيح اختطاف الأصول آليًّا في أقل من ثانية.\n\n01 / طُعم «ذا تشات»صديق يطلب مني التصويتتتلقى الضحية رسالة تحتوي على رابط.\n02 / تسجيل الدخولبوابة تشبههايقوم الضحية بإدخال بيانات تسجيل الدخول.\n03 / الوصولإنشاء واجهة برمجة تطبيقات الويب الصامتةيقوم المهاجم بتسجيل مفتاح مطور.\n04 / التغييرتم تبادل التجارة المشروعةيقوم «Clone bot» بنسخ المستلم المستهدف.\n05 / التأكيدتمت الموافقة على المنتج المقلدتمت الموافقة على عرض خاطئ عبر الهاتف المحمول.\nنفس الخطوة، كما تظهر من منظور الشبكةإعادة بناء النمط السائد قبل عام 2023 · أشكال تداول توضيحية\nالضحيةيوافق على الرسالة المنبثقة على الهاتف المحمول التي كان من المتوقع ظهورها بالنسبة للصفقة الأصلية.\nالمهاجميستلم العناصر في الحساب المستنسخ.\nSteam مشاهدةعملية تحويل تم تأكيدها من قِبل صاحب الحساب على جهاز مسجل.\nConfirmation genuine — made by the account holder\nRecipient the clone bot, not the intended counterparty\nThe confirmation is authentic. The offer it confirms is not the one the user initiated.\n\nالسجل الذي تركه وراءه: صفقة وافق عليها المستخدم. وهذا هو السجل الذي يقرأه فريق الدعم عند وصول الشكوى، وهو السبب وراء إغلاق الشكاوى المؤرشفة باعتبارها «خطأ من جانب المستخدم». وتوجد الشكاوى في أرشيف الإجراءات التنفيذية.\n\nالجزء أ — السجل الفني · القسم 7\nنقاط النهاية الكامنة وراء التسلسل.\nالسياق وحدود المصدر\n\nهذه هي نقاط نهاية واجهة برمجة التطبيقات (Web API) ذات الرمز Steam التي استخدمتها البرامج النصية المخترقة المبلغ عنها لاعتراض الصفقات دون المرور بخطوات التأكيد من جانب المتصفح.\n\nأربع نقاط نهاية موثقة تكفي لإنجاز المهمة بأكملها. ولا توجد أي عيوب في أي منها، ولا حاجة لاستغلال أي منها — فالمفتاح الصحيح يستدعيها، وترد عليها بـ Steam. المفتاح هو الشيء الوحيد الذي كان على المهاجم سرقته.\n\nIEconService / GetTradeOffers / الإصدار 1استطلاع الرأي\n\nيُستخدم لمراقبة عروض التداول الخاصة بالحساب. تقوم البرامج النصية باستقصاء هذه النقطة النهائية بشكل متكرر باستخدام مفتاح واجهة برمجة التطبيقات (API) المخترق؛ حيث تعرض تفاصيل عروض التداول التي تم إنشاؤها حديثًا أو المعلقة أو التي تم تعديلها. لا يتم قياس فترات الاستقصاء هنا.\n\nمصدر التهديد: يكشف عن معرّفات عروض التداول المعلقة وتفاصيل الملف الشخصي للمستلم.\nIEconService / CancelTradeOffer / الإصدار 1التفاعل\n\nيُستخدم لإبطال عرض التداول الشرعي للمستخدم برمجيًّا. قبل عام 2023، لم تكن هناك مصادقة معززة تحمي المفتاح، لذا كان بإمكان الخادم الآلي إلغاء العرض فور اكتشافه، دون إرسال أي إشعار إلى صاحب الحساب.\n\nمصدر التهديد: يُلغي الصفقة قبل أن يكمل صاحب الحساب عملية التأكيد عبر الهاتف المحمول.\nISteamUser / GetPlayerSummaries / الإصدار 2RECON\n\nيتم إجراء استعلام لاسترداد اسم الملف الشخصي وعنوان URL لصورة الصورة الرمزية ومستوى المستلم الشرعي للصفقة. وهذا يتيح للنص البرمجي تهيئة حساب مقلد جاهز ليتطابق مع تلك البيانات. ولا يتم قياس أي وقت هنا.\n\nمصدر التهديد: يوفر البيانات اللازمة لانتحال صفة المستلم المقصود.\n/dev/ajaxregisterkeyالإنشاء\n\nنقطة نهاية التسجيل الخاصة بـ Steam للمفاتيح. في الماضي، كان بإمكان أي جلسة نشطة لملفات تعريف الارتباط في المتصفح (`steamLoginSecure`) تسجيل مفتاح دون الحاجة إلى تأكيد من Steam Guard على الجهاز المحمول، ودون إرسال أي إشعار إلى صاحب الحساب.\n\nمصدر التهديد: بيانات اعتماد دائمة تم إنشاؤها بواسطة برنامج نصي، دون علم صاحب الحساب.\nالجزء أ — السجل الفني · القسم 8 · المادة 7 من اللائحة العامة لحماية البيانات (GDPR)\nمربع محدد. من قام بهذا الإجراء؟\nالسياق وحدود المصدر\n\nعند رفض السداد، Steam تشير ردود فريق الدعم المحفوظة في الأرشيف إلى أن صاحب الحساب هو من أنشأ مفتاح واجهة برمجة التطبيقات (API)، وأنه بمجرد تحديد المربع، فقد وافق على الشروط.\n\nتُعزو استجابة الدعم هذه إلى صاحب الحساب. والسؤال المطروح هو: هل يثبت السجل هوية الشخص الذي أنشأه فعليًّا؟\n\nإلا أنه في نمط اختطاف مفتاح واجهة برمجة التطبيقات (API) الذي تمت ملاحظته، لم يقم الضحية مطلقًا برؤية صفحة إنشاء مفتاح واجهة برمجة التطبيقات أو الانتقال إليها. ويتم إرسال حقل الموافقة بواسطة برنامج نصي يقوم بتنفيذ طلب POST بدون واجهة مستخدم باستخدام ملف تعريف الارتباط الخاص بالجلسة المسروق.\n\nبموجب المادة 7 والمادة 4(11) من اللائحة العامة لحماية البيانات (GDPR)، يجب أن تكون الموافقة إشارة حرة ومحددة ومستنيرة ولا لبس فيها تعبر عن رغبة صاحب البيانات. ويرى المؤلفون أن حقل قبول الشروط الذي يتم إرساله بواسطة برنامج نصي ضار باستخدام ملف تعريف ارتباط مسروق، دون عرض أي صفحة على صاحب الحساب، لا يمكن أن يستوفي هذا التعريف. أما ما إذا كان يستوفيه أم لا، فهذا أمر يرجع إلى السلطة الإشرافية.\n\nتحليل الحمولة الجنائية: تسجيل المفاتيح\nمنشور https://steamcommunity.com/dev/ajaxregisterkey\n// حمولة الطلب (تم إدخالها عبر برنامج نصي للاختراق)\n{\n\"agreeToTerms\": \"متفق عليه\"، <-- تم إدخالها آليًّا، دون تدخل بشري\n\"المجال\": \"localhost\"، ← لم يتم التحقق من صحة القيمة — يُقبل أي قيمة، بما في ذلك localhost\n\"sessionid\": \"8f0d8ef763ab2140bf89de2a\"\n}\nالسؤال الموجه إلى السلطة الإشرافية: في الحالات التي لم ينقر فيها صاحب الحساب مطلقًا على خانة الموافقة، ما إذا كان قبول الشروط المسجل في سجل الحساب يستوفي متطلبات المادة 7 المتعلقة بإبداء رغبة صاحب البيانات بشكل طوعي ومحدد ومستنير ولا لبس فيه، وما إذا كان بإمكان خدمة الدعم Steam الاعتماد على ذلك لرفض المطالبة.\n\nالمصدر: شكل طلب تسجيل المفتاح كما تم إعادة بنائه استنادًا إلى نقطة النهاية العامة وتقارير الاختراق المحفوظة في أرشيف الأدلة (نسخة قابلة للبحث من 2026-09-17) · معرّف الجلسة الموضح هو عنصر بديل، وليس قيمة تم تسجيلها.\n\nالتشريح الجنائي · متجه استبدال السلع\nكيف تمكنت Valve أخيرًا من إبطال مفعول «الاستبدال التجاري» — ولماذا استغرق الأمر 7 سنوات من الحلول البديلة\n\nعلى مدى ما يقرب من عقد من الزمن، فإن \"الاستبدال الاحتيالي لمفتاح واجهة برمجة التطبيقات\" (أو احتيال \"الوسيط بين الطرفين\" لواجهة برمجة التطبيقات) كان هذا النموذج الأكثر ربحية لسرقة الحسابات على Steam، حيث استنزف مئات الملايين من الدولارات من «السكينز» من لاعبين لم يكونوا على علم بذلك. لم تقم Valve بالقضاء على هذه الثغرة الأمنية من خلال إصلاح بنية واجهة برمجة التطبيقات (API) المعرضة للخطر؛ بل قضت Valve سبع سنوات في وضع أربعة حواجز معوقة على مستوى المنصة بأكملها، مما أدى إلى شل سيولة التداول داخل المجتمع دون معالجة السبب الجذري للمشكلة.\n\n1. الموت بالتقليد\nفترة انتظار تغيير الصورة الرمزية والاسم (فبراير 2024)\n\nتطلبت هذه الهجمة تقليدًا في أقل من ثانية: فقد اعترض روبوت الاحتيال صفقة تداول صادرة، واستخرج الصورة الرمزية/الاسم الخاص بالمستلم عبر ISteamUser، وقام بنسخ الملف الشخصي في غضون 200 مللي ثانية. وفي 14 فبراير 2024، قام Valve بهدوء بتنفيذ إجراء إلزامي فترة انتظار للتداول تتراوح بين ساعتين و4 ساعات (الخطأ 34) فور إجراء أي تغيير في اسم الملف الشخصي أو الصورة الرمزية. لم يعد بإمكان الروبوت استنساخ مستلم ما على الفور دون أن يُمنع من إجراء عمليات التداول.\n\n2. الموت الاقتصادي\nانعكاس الاتجاه في تداول CS2 لمدة 7 أيام (يوليو 2025)\n\nValve تم تقديمه من جانب واحد انعكاسات الاتجاه في التداول بالنسبة لعناصر لعبة Counter-Strike. يتم وضع علامة «محمية من التبادل» على أي سكن يتم تبادله لمدة سبعة أيام. إذا اكتشفت الضحية حدوث استبدال، فما عليها سوى النقر على «إلغاء التبادل» في قسم الدعم Steam، ليتم إعادة السكن على الفور إلى مخزونها مع تجميد حساب المستلم. ونظرًا لأن قفل التبادل لمدة 7 أيام يمنع المحتالين من نقل العنصر إلى موقع صرف نقدي، فإن السرقة تصبح غير مربحة.\n\n3. وفاة «الصامت»\nالتحديث الإلزامي للرسائل الفورية عبر الهاتف المحمول لواجهة برمجة التطبيقات (ديسمبر 2023)\n\nتاريخياً، كان ملف تعريف الارتباط الخاص بالجلسة المسروق يسمح للبرامج النصية الخبيثة بتنفيذ طلب POST في الخلفية دون واجهة مستخدم إلى /dev/ajaxregisterkey دون إخطار الضحية. في 4 ديسمبر 2023، فرضت Valve ضرورة الحصول على تأكيد صريح عند إرسال إشعار دفع عبر تطبيق الهاتف المحمول Steam لإنشاء مفتاح واجهة برمجة تطبيقات الويب (Web API)، مما أدى إلى إلغاء عملية توفير المفاتيح الصامتة في الخلفية.\n\n4. التنبيهات داخل التطبيق على الأجهزة المحمولة\nلافتات عمر الحساب واسمه (2022–2024)\n\nValve تم تحديث نافذة التأكيد المنبثقة على الهاتف المحمول لعرض بيانات الشريك التجاري Steam مدة الحساب (تاريخ الإنشاء)، مستوى Steam، وتحذير صريح باللون الكهرماني: \"قام هذا المستخدم مؤخرًا بتغيير اسم ملفه الشخصي\"، مما يكسر الوهم البصري بالنسبة للضحايا اليقظين.\n\nالعيوب الثلاثة في «مخطط Valve»: لماذا اكتفى المحتالون بتغيير أهدافهم\n1. ثغرة استثناء الألعاب (Dota 2 و TF2)\n\nتم استخدام ميزة «Trade Reversals» حصريًّا في لعبة Counter-Strike 2. لا تزال عناصر ألعاب «Dota 2» و«Team Fortress 2» غير محمية على الإطلاق بسبب تعقيدات الصناعة وتركيب الأحجار. العناصر عالية المستوى التي تبلغ قيمتها آلاف الدولارات (مخالب مخلب التنين، و«بيبي روشان» الذهبية، و«TF2» غير العادية ذات اللهب المشتعل) لا تتوفر لها أي فترة لإلغاء الصفقة. قام المحتالون ببساطة بإعادة توجيه عمليات الاعتراض الآلية عبر واجهة برمجة التطبيقات (API) إلى تجار Dota 2 وTF2، حيث يطبق فريق الدعم Steam بصرامة سياسته لعام 2016 التي تنص على «عدم استعادة العناصر».\n\n2. خزان «مفتاح الزومبي» (بدون تاريخ انتهاء الصلاحية)\n\nبينما أضاف Valve ميزة المصادقة الثنائية (2FA) عبر إشعارات الهاتف المحمول لإنشاء جديد المفاتيح في ديسمبر 2023، Valve لم يتم إلغاء أو انتهاء صلاحية أو مسح أي مفاتيح API قديمة موجودة. لا تزال ملايين الحسابات النشطة التي أنشأت مفاتيح (أو التي تم إنشاء مفاتيح لها بشكل خفي عن طريق التصيد الاحتيالي/البرامج الضارة قبل ديسمبر 2023) تحتفظ ببيانات اعتماد نشطة مع انتهاء صلاحية صفر (بدون TTL) ووقت انتظار عدم النشاط صفر. تحتفظ الجهات الخبيثة بقاعدة بيانات تاريخية ضخمة تضم هذه المفاتيح الدائمة، وتواصل استقصاءها IEconService دون أي عائق.\n\n3. عقوبة الضحية: تجميد التداول لمدة 30 يومًا\n\nحتى في CS2، يُعاقب Valve اللاعب الذي تعرض للخداع: فالنقر على «إلغاء الصفقة» في قسم الدعم Steam يؤدي تلقائيًا إلى فرض حظر تداول وحظر دخول «السوق المجتمعي» لمدة 30 يومًا على حساب الضحية. Valve تُفرض على المستخدم عقوبة تتمثل في حظره من استخدام المنصة لمدة شهر كإجراء رادع ضد عمليات التراجع «التافهة»، مما يثني الضحايا عن التراجع عن الصفقات المتعلقة بالأصول السائلة ذات القيمة المنخفضة.\n\nفضيحة اللوائح الأساسية: سبع سنوات من الحلول الالتفافية مقابل نطاق واجهة برمجة تطبيقات واحدة\n\nلماذا أمضى Valve سبع سنوات في ابتكار آليات تجميد الصفقات، وفترات الانتظار للحسابات، وأقفال التداول القابلة للإلغاء — مما أدى إلى زعزعة اقتصاد الألعاب برمته وإهدار $104 مليون من القيمة السوقية — بدلاً من تطبيق الحل القياسي المتبع في القطاع؟\n\nكما يتضح من الإصدار الرسمي للعبة Valve على منصة Steamworks في 16 يناير 2026 (إعلان #493839547938902179 ↗)، Valve تم بناؤها بالفعل مجموعات الأذونات التفصيلية (عام، المعاملات الصغيرة، الاقتصاد، بيانات المبيعات) و قائمة العناوين المسموح بها لبروتوكول الإنترنت بالنسبة لمفاتيح الناشر الخاصة بالشركات. كان لدى Valve الحل الهندسي جاهزًا منذ سنوات. مربع اختيار واحد يظهر للمستخدم—\"منع مفتاح واجهة برمجة التطبيقات (Web API) هذا من الوصول إلى IEconService (إدارة التداول)\" أو قائمة بيضاء لعناوين IP المنزلية — كان من شأنها القضاء على عملية الاحتيال المتعلقة باستبدال البضائع في عام 2018 دون أي أضرار اقتصادية جانبية. ورفضت Valve منح اللاعبين العاديين الحماية التي صممتها لشركائها من الشركات.\n\nالجزء باء — القواعد وسجل الإنفاذ · المادة 9\nقواعدهم. البرامج الانتخابية المعلنة.\nالسياق وحدود المصدر\n\nيُبيّن هذا السجل البنود الصريحة الواردة في Steam اتفاقية الاشتراك (SSA) و Steam السلوك عبر الإنترنت (SOC) إرشادات تستهدف بشكل مباشر الكيانات التجارية النشطة والكبيرة الحجم.\n\nالقاعدة: ممنوع الاستخدام التجاري، وممنوع المقامرة، وممنوع استخدام الروبوتات — وتستشهد Steam Support بهذه الشروط عندما ترفض إعادة أغراض الضحية. السجل: تشمل هذه البنود، ظاهريًّا، المنصات التجارية المدرجة في هذا السجل، والتي تعمل على Steam هويات، وSteam روبوتات، وSteam عمليات تحويل. يُطبق هذا البند على الشخص الذي فقد الجلود، وليس — وفقًا لأي سجل منشور — على الشركات التي تقوم بنقلها.\n\nفي الشكاوى المحفوظة، تشير خدمة الدعم Steam إلى \"ممنوع الاستخدام التجاري\" و \"لا للأتمتة/الروبوتات\" البنود التي تستند إليها المنصات عند رفض إعادة الأصول إلى ضحايا الاحتيال باستخدام مفاتيح واجهة برمجة التطبيقات (API). وتنطبق هذه البنود ظاهريًّا على المنصات التجارية الواردة في هذا الملف، والتي تقوم بالمصادقة عبر Steam OpenID وتنقل الأصول عبر حسابات Steam آلية. لم يتم تقدير أي رقم لإيرادات السوق ككل هنا (انظر إحصائيات الإنفاذ أدناه). ما يظهره السجل هو القاعدة المطبقة على الحسابات الفردية في الحالات المؤرشفة، ولا يوجد سجل منشور لإنفاذ القانون لكل مشغل من مشغلي المنصات. وهذا التباين هو ما يوثقه هذا القسم.\n\nالسؤال الأساسي / الإنفاذ الانتقائيالقواعد → النطاق → المساءلة\nكتاب قواعد واحد. تطبيق غير متكافئ.\n\nيُظهر السجل أن الخدمات التجارية تستخدم الهويات Steam، وقوائم الجرد، والروبوتات، وعمليات النقل كبنية تحتية تشغيلية. وتحظر اتفاقية الخدمات الاجتماعية (SSA) الاستغلال التجاري والأتمتة دون إذن. وتُظهر الشكاوى المؤرشفة أن هذه القاعدة طُبقت على الحسابات الفردية، في حين أن السجل العام لا يُظهر حسابًا مكافئًا لكل مشغل على حدة بالنسبة للمنصات الموثقة هنا. ينبغي نشر القاعدة والأدلة وقرار الإنفاذ الخاص بكل منها.\n\n189المواقع الإلكترونية المشمولة بنطاق التدقيق\n44مسارات النطاقات المنفصلة في السجل النشط — 27 منها مع ملف أدلة منشور، و17 تم جمعها يدويًّا. وقد أسفرت عملية تدقيق المتصفح التي شملت 189 موقعًا إلكترونيًّا وحدها عن حل 25 منها؛ ويضيف السجل المسارات التي تم جمعها يدويًّا.\n12 سنة و6 أشهرتم حظر موقع csgogem.com في «مرشح الروابط»؛ api.csgem.com مسجلة في 2014-03-08 ولم تُحظر قط — واحدة من 26 زوجًا من هذا النوع حتى 2026-09-22\nلا يوجد إجمالي مؤكداستثناء تقديرات الإيرادات على مستوى السوق\nSteam السلوك عبر الإنترنت\n\"…يُحظر عليك القيام بأي من الأمور التالية على Steam أو محاولة القيام بها: […] الانخراط في نشاط تجاري. ومن أمثلة هذه السلوكيات المحظورة: نشر الإعلانات؛ وإجراء المسابقات؛ المقامرة؛ شراء أو بيع حسابات Steam؛ بيع المحتوى أو بطاقات الهدايا أو أي عناصر أخرى؛ والتسول.\"\n\nstore.steampowered.com/online_conduct ↗ محفوظ 2026-09-21 ↗\n\nالمادة 2.G من قانون الضمان الاجتماعي — الاستخدام التجاري\n\"…[لا يجوز لك] استغلال المحتوى والخدمات أو أي جزء منها لأي غرض تجاري، باستثناء ما يُسمح به صراحةً في أي موضع آخر من هذه الاتفاقية…\"\n\nاستندت إخطارات Valve لعام 2016، كما ورد في التقارير، إلى الترخيص الشخصي غير التجاري. ولم يقدم أي مشغل ترخيصًا من نوع Valve في السجلات. store.steampowered.com/subscriber_agreement ↗ محفوظ 2026-09-18 ↗\n\nSteam شروط استخدام واجهة برمجة التطبيقات (Web API)\n\"لا يجوز لك استخدام واجهة برمجة تطبيقات الويب Steam أو البيانات Steam بأي طريقة تنتهك اتفاقية المشترك Steam.\"\n\nتعمل منصات بيع الأسطح الخارجية من خلال حسابات آلية تستخدم واجهة برمجة التطبيقات (API) Steam. ولا ينص نص القاعدة على أي استثناءات فيما يتعلق بالنطاق التجاري. steamcommunity.com/dev/apiterms ↗ محفوظ 2026-09-21 ↗\n\nالمادة 4.C من قانون الضمان الاجتماعي (SSA)\nالأتمتة\n\nيُحظر استخدام البرامج النصية والروبوتات والتفاعلات غير البشرية. ويسجل دفتر الأستاذ عمليات التداول التي يقوم بها الروبوتات، ومزارع الحسابات، والتوجيه الآلي على نطاق تجاري.\n\nفحص 153السجلات المصنفة تحت هذا البند ↗\nما ينص عليه السجل بموجب هذا البند153 المنصات المُصنَّفة\nفتح القضية15\nكازينو سكين13\nسوق CS29\nروليت البشرة8\ncsgoempire.com→csgoempirelogin4.comالكازينو\nrollbit.com→rbsnin.comكازينو العملات المشفرة\n500.casino→fivezerozero.coكازينو مرخص\n\nومن بين هؤلاء، 153 كما تم تصنيفها تحت المادة 2.G من قانون الضمان الاجتماعي (SSA) و 2 كما أنها مصنفة بموجب المادة 1.C من قانون الضمان الاجتماعي (SSA) — حيث تندرج الخدمات نفسها تحت أكثر من بند واحد، ولهذا السبب تتكرر الأمثلة.\n\n28 تم رصد مواقع تابعة لـ «153» تقوم بالتوثيق عبر نطاق منفصل قابل للتسجيل. وتسجل العلامة ملاحظة مؤرخة تجعل المنصة تندرج ضمن نطاق البند ظاهريًّا؛ وهي ليست مخالفة تم البت فيها قضائيًّا، ولم يتم تقديم أي ترخيص من «Valve» لأي منها.\n\nالمادة 2.G من قانون الضمان الاجتماعي (SSA)\nالاستخدام التجاري\n\nيتطلب الاستغلال التجاري الحصول على إذن صريح. قارن بين نماذج الأعمال الموثقة، وحجمها، وأي تفويض أو إجراءات إنفاذ تم الكشف عنها.\n\nفحص 175السجلات المصنفة تحت هذا البند ↗\nما ينص عليه السجل بموجب هذا البند175 المنصات المُصنَّفة\nفتح القضية15\nكازينو سكين13\nسوق CS29\nروليت البشرة8\ncsgoempire.com→csgoempirelogin4.comالكازينو\nrollbit.com→rbsnin.comكازينو العملات المشفرة\n500.casino→fivezerozero.coكازينو مرخص\n\nومن بين هؤلاء، 153 كما تم تصنيفها تحت المادة 4.C من قانون الضمان الاجتماعي (SSA) و 24 كما أنها مصنفة بموجب المادة 1.C من قانون الضمان الاجتماعي (SSA) — حيث تندرج الخدمات نفسها تحت أكثر من بند واحد، ولهذا السبب تتكرر الأمثلة.\n\n28 تم رصد مواقع تابعة لـ «175» تقوم بالتوثيق عبر نطاق منفصل قابل للتسجيل. وتسجل العلامة ملاحظة مؤرخة تجعل المنصة خاضعة لأحكام البند ظاهريًّا؛ وهي ليست مخالفة تم البت فيها قضائيًّا، ولم يتم تقديم أي ترخيص من «Valve» لأي منها.\n\nالمادة 3.أ من قانون الضمان الاجتماعي (SSA)\nشبكة VPN وإخفاء الموقع\n\nقد يؤدي إخفاء عنوان الإقامة باستخدام بروكسي IP إلى إنهاء الخدمة. أما مضيفات المصادقة ذات النطاقات المنفصلة فتتطلب تحليلاً منفصلاً: تحديد ما الذي تم إخفاؤه والقاعدة التي تنطبق عليه.\n\nافحص دليل «auth-host» ↗\nSteam المساعدة / سياسة عناوين URL\nإخفاء الروابط\n\nSteam يحظر استخدام أدوات تقصير الروابط والأدوات التي تخفي وجهات الروابط. نطاق مصادقة منفصل — rbsnin.com في عملية تسجيل الدخول إلى Rollbit، auth.dota.trade في CS.MONEY — يُثير السؤال المماثل حول ما إذا كانت الوجهة التي تُعرض على أداة التحقق من OpenID الخاصة بـ Steam تحدد موقع التشغيل.\n\nسياسة عناوين URL الخاصة بـ Valve ↗\n\nمراجع القواعد: Steam اتفاقية الاشتراك، النسخة المعدلة بتاريخ 10 سبتمبر 2026 محفوظ 2026-09-18 ↗ · Steam شروط استخدام واجهة برمجة التطبيقات (Web API) محفوظ 2026-09-21 ↗ · Steam سياسة عناوين URL (إخفاء الروابط). تشير الأرقام إلى سجلات هذا الملف وعلاماته؛ وهي لا تمثل عدد المخالفات التي تم البت فيها.\n\nعجز الثقة\nمن الذي يراجع القرار عندما تقوم إدارة الدعم بإغلاق القضية؟\n\nتصف الشكاوى المحفوظة العقوبات الدائمة، والتحديات التي لم يتم الرد عليها، ورفض إعادة الأصول المسروقة. قارن هذه الروايات بسجل التذاكر الفعلي، وسبل الانتصاف المتاحة، وسجلات الوصول إلى الحساب. لا يمكن لتفسير عام يتعلق بالتصيد الاحتيالي أن يثبت من الذي بدأ عملية إعادة الضبط أو أنشأ مفتاح واجهة برمجة التطبيقات (API).\n\nاقرأ الشكاوى التي تم تسجيلها ↗طلب السجلات الأصلية →رسم بياني لعلاقات المشرف →\nالجزء باء — القواعد وسجل الإنفاذ · المادة 10\nواجهة برمجة تطبيقات (API) للأتمتة. قاعدة تمنع الأتمتة.\nالسياق وحدود المصدر\n\nالسؤال الذي يطرحه هذا القسم هو كيفية التوفيق بين الأمرين: ما هي استخدامات واجهة برمجة التطبيقات (API) المسموح بها، ومن الذي يصرح بها، وبناءً على أي معايير منشورة. لم يتم تقدير عدد مستخدمي واجهة برمجة التطبيقات (API) التجاريين المصرح لهم هنا، ولا يُستنتج أي رقم من غياب قائمة منشورة — فالغياب هو النتيجة، وليس الرقم الكامن وراءه. تم إعادة نشر رسائل الدعم Steam المقتبسة أعلاه من قِبل المشروع ArchiSteamFarm في قسم الأسئلة الشائعة الخاص به (تم التحقق من نصها حرفيًا 2026-09-22)؛ وهي ليست Valve منشورات، ولم يتم تحديد الحسابات التي أُرسلت إليها.\n\nالقاعدة (المادة 4.C من قانون الضمان الاجتماعي): لا نصوص برمجية، ولا روبوتات، ولا أنظمة غير بشرية على Steam. السجل: Valve توفر واجهة برمجة تطبيقات REST بدون واجهة مستخدم، والغرض الوحيد منها هو أتمتة العمليات بين الخوادم، وتمنح مفتاح الوصول لأي حساب. يتم حظر المستخدمين بسبب استخدام الأتمتة؛ وواجهة الأتمتة هي منتج خاص بـ Valve. لم يتم الإعلان قط عن الاستخدامات التجارية المسموح بها.\n\nمغالطة «مطور الألعاب»\nحزمة أدوات تطوير التطبيقات Steamworks (أصلية)\n\nتستخدمها استوديوهات الألعاب المعتمدة لدمج الإنجازات، ونظام إيجاد اللاعبين المناسبين، وقوائم المتصدرين في برامج عملاء ألعابها. ويتطلب ذلك عملية دمج معقدة بلغة C++ وإجراء عملية انضمام رسمية للشركاء.\n\nSteam واجهة برمجة تطبيقات الويب (الثغرة)\n\nبنية JSON/REST بدون رأس مصممة لخوادم الويب الخارجية. في نمط «الاختطاف» الموثق هنا، تُستخدم هذه البنية لقراءة قوائم المخزون والتلاعب بعمليات التداول بين الأقران من خوادم بعيدة؛ ولا ترد الاستخدامات المشروعة لهذه البنية في هذا الملف.\n\nلمن هذه المفتاح؟لا يحتاج المستخدم العادي Steam إلى مفتاح واجهة برمجة تطبيقات الويب (Web API) داخل التطبيق؛ حيث توجد صفحة المفتاح ضمن رابط مخصص للمطورين، والغرض الموثق منها هو الوصول الخارجي من جانب الخادم. وتصف الشكاوى المُحفَظة المتعلقة بعمليات الاختراق ضحايا لم يكونوا على علم بوجود هذه الصفحة حتى تم تسجيل مفتاح في حساباتهم.\nتناقض الأتمتة\n\nينص البند 4.C من قانون الضمان الاجتماعي (SSA) على ما يلي: \"لا يجوز لك استخدام أي شكل من أشكال البرامج النصية أو الروبوتات أو الماكرو أو أي أنظمة أخرى لا يتحكم فيها الإنسان («الأتمتة») للتفاعل مع المحتوى والخدمات على Steam بأي شكل من الأشكال.\" ومع ذلك، فإن نقاط نهاية واجهة برمجة تطبيقات الويب (مثل CancelTradeOffer) لا تتطلب واجهة مستخدم بشرية ولا اختبار كابتشا، وتتجاوز عميل Steam تمامًا. تم تصميم واجهة برمجة التطبيقات (API) لأغراض الأتمتة بين الخوادم؛ وتحظر القاعدة الأتمتة من قِبل المستخدمين؛ ولم يتم الإعلان عن الحد الفاصل بين الاثنين.\n\nموقع من جانب الخادم في تدفق المعاملات التجارية\n\nيتيح مفتاح واجهة برمجة التطبيقات (Web API) لخادم تابع لجهة خارجية تنفيذ عمليات التداول الخاصة بالحساب دون الحاجة إلى العميل Steam. وفي نمط «الاختطاف»، يقع هذا الخادم بين صاحب الحساب وخادم التداول.\n\n→لا تظهر شاشة تأكيد الصفقة بالنسبة لإجراءات المفتاح.\n→يسمح بإجراء الاستقصاء في الخلفية (GetTradeOffers).\n→يلغي العروض ويعيد إصدارها دون تدخل من المستخدم.\nValve قامت بتصميم الواجهة، وحظرت في قواعدها استخدام الأتمتة من قِبل المستخدمين، ولم تنشر أي معايير تحدد الاستخدامات التجارية المسموح بها.\nالجزء باء — القواعد وسجل الإنفاذ · المادة 11\nعشرة أيام مطلوبة. وعشر سنوات يجب تقديم حساب عنها.\nالسياق وحدود المصدر\n\nفي 20 يوليو 2016، حدد المستشار القانوني لـ Valve مهلة مدتها 10 أيام لمشغلي المقامرة. وبعد مرور عشر سنوات (حسب لقطة الملف، 2026-09-21)، لا تزال منصة واحدة على الأقل ورد ذكرها في التقارير الصحفية المتعلقة بهذا الإشعار، وهي CSGOFast، تعمل عبر مضيف مصادقة بنطاق منفصل. وقد أُعيدت صياغة النص أدناه استنادًا إلى التقارير الصحفية الصادرة في 21 يوليو 2016؛ ولا يُعد هذا النص نسخة ممسوحة ضوئيًا. لم يتم نشر سجل الإجراءات التنفيذية الذي أشار إليه الإشعار. الرسالة المفتوحة الموجهة إلى اللجنة هي القسم 2.\n\nيرجى الاطلاع على الإشعار الصادر في يوليو 2016 الموجود بجانب الملاحظات اللاحقة. والمطلب الذي لم يتم الوفاء به بعد هو توفير سجل إنفاذ خاص بكل مشغل على حدة.\n\nقبل أسبوع من ذلك — في 13 يوليو 2016، في مكان عام\n\nفي 13 يوليو 2016 محفوظ 2026-09-21 ↗، Valve أوضح كيف تستخدم مواقع المقامرة Steam: OpenID لتحديد هوية الحسابات، والحسابات الآلية لأغراض التداول. Valve أشار إلى أن استخدام تلك الآليات لإدارة نشاط المقامرة يشكل انتهاكًا لاتفاقيات واجهة برمجة التطبيقات (API) واتفاقيات المستخدم الخاصة به. يرد كل من وصف الآلية والحظر في البيان المؤرخ الصادر عن Valve نفسه. في 2026-09-21، لم تُسجل أي حالات حظر عبر «تصفية الروابط» (Link Filter) في مضيفات المصادقة ذات المجالات المنفصلة التي تم اختبارها، ولم ينشر Valve أي سجلات فرض قيود خاصة بكل مشغل.\n\nالملحق (أ) / يوليو 2016إعادة بناء النص المطبوع\nشركة فالف\n\nبلفيو، واشنطن\n\nالتاريخ:يوليو 2016 (وفقًا لما أوردته الصحافة في 21 يوليو 2016)\nمن:كارل كواكينبوش، المستشار القانوني العام\nبشأن:إنذار بالكف عن — الاستخدام التجاري لحسابات Steam\nملاحظة:إعادة صياغة النص المبلغ عنه؛ وليس نسخة ممسوحة ضوئيًا\n\n\"نحن على علم بأنك تدير أحد مواقع المقامرة المذكورة أدناه. أنت تستخدم Steam حسابًا لممارسة هذه النشاط التجاري. وبموجب Steam اتفاقية المشترك، فإن خدمات Steam وSteam مرخصة للاستخدام الشخصي غير التجاري فقط.\"\n\n\"يجب عليك التوقف فوراً عن استخدام حساباتك Steam لأي أغراض تجارية. وإذا لم تقم بذلك،\" في غضون عشرة (10) أيام، Valve ستتخذ جميع الإجراءات القانونية المتاحة، بما في ذلك على سبيل المثال لا الحصر إنهاء حساباتك.\"\n\nإعادة بناء الملف · الرجوع إلى السجل الأصلي\nكارل كواكينبوش\nالمستشار القانوني العام لشركة Valve Corp.\nفي الهامش / افتتاحية\nعشرة أيام.ثم ماذا؟\n\nكان الموعد النهائي محددًا. وينبغي أن يكون التفاعل العام مع هذا الأمر محددًا أيضًا.\n\nالموقف الذي نشرته شركة «Valve» بشأن «2016» ↗\nملاحظة بشأن الموعد النهائي +\nسخرية / ليست مراسلات من «فالفي»\n\nعزيزي الموعد النهائي،\n\nلقد مُنحت عشرة أيام. وبطريقة ما، كان التقويم هو الشيء الوحيد الذي ظل يعمل.\n\nيرجى إرسال أي رد إلى السجل العام.\n\nالجدول الزمنييوليو 2016 – سبتمبر 2026\nالموعد النهائي الوارد في الإشعار:\n10 أيام\nيوليو 2016\nالمدة المنقضية منذ تاريخ الإشعار:\n3,715 يومًا\nرقم ثابت من 20 يوليو 2016 حتى تاريخ لقطة الملف في 21 سبتمبر 2026، وليس رقمًا محدثًا\nسجل الإنفاذ المنشور:\nلا شيء\nلم يتم العثور على سجلات خاصة بكل مشغل بشأن قطع الخدمة أو عمليات الحظر\n\n◀ الأيام من 0 إلى 10 — الموعد النهائي، حسب الحجماليوم 3715 — اللقطة ▶\n\n20 يوليو 2016صدور أمر مدته عشرة أياماليوم 0\n17 فبراير 2024تسري التزامات DSAاليوم 2,768\n25 فبراير 2026الإعلان عن الشكوى المقدمة من المدعي العام لولاية نيويوركاليوم 3,507\n21 سبتمبر 2026لمحة عامة عن الملفاليوم 3715\n\nبعد عشر سنوات، CSGOFast — المذكور في التقارير الصحفية المتعلقة بالإشعارات الصادرة عام 2016 — يعمل حالياً: أظهر موقع csgofast.com حجبًا من «Link Filter» عند 2026-09-19 و2026-09-21، في حين أن مضيف المصادقة الخاص به steam-login.authtofast.com (المسجل برقم 2026-06-30) لم يفعل ذلك.\n\nسجل كامل ومؤرخ لتغييرات الأمان الخاصة بـ Valve: الجدول الزمني للأحداث الأمنية → · سجل واشنطن ومعيار الإنفاذ: أدناه\n\nما يظهر من السجل: حدد الإشعار الصادر عام 2016 مهلة مدتها 10 أيام؛ وكانت Valve تدير بالفعل قائمة نطاقات (تسمى «Link Filter») وتستقبل أسماء المضيفين المعتمدة في طلبات OpenID الخاصة بها؛ ولم يتم نشر أي سجل لتنفيذ الإجراءات لكل مشغل على حدة. تصف تقارير المجتمع إجراءً اتُخذ في عام 2018 ضد سوق إلكتروني (SkinJar)، لكن هذه التقارير لم يتم التحقق منها ولا يُعتمد عليها هنا.\nCSGOFAST / مسار المصادقة المحفوظ\nاتبع المضيف المُعلن عنه.\n\nروابط سجلات المسارات المحفوظة csgofast.com إلى steam-login.authtofast.com. يتم تضمين اسم المضيف المنفصل في طلب OpenID Steam. وهو يوفر للمحققين عنوانًا محددًا لمقارنته بسجلات التصفية والإنفاذ الخاصة بـ Valve.\n\nافحص مسار CSGOFast ومصدره ↗ · مقارنة النتائج المحفوظة Steam تصفية الروابط ↗\n\nالسجل العام / واشنطن · 2016 → 2026\nموعدان نهائيان. معيار إنفاذ واحد لم يتم الرد عليه.\n20 يوليو\nValve تمنح مواقع المقامرة مهلة 10 أيام\n\nوحذر طلب محامي الشركة من أن الاستمرار في الاستخدام التجاري لحسابات Steam قد يؤدي إلى إنهاء الخدمة.\n\n27 سبتمبر\nواشنطن تضغط Valve\n\nطالبت لجنة المقامرة التابعة للولاية بتقديم أدلة على الإجراءات المتخذة لوقف عمليات تحويل الأموال عبر «السكين» لأغراض المقامرة، وحددت 14 أكتوبر موعدًا نهائيًا لتقديم الرد.\n\n17 أكتوبر\nValve ينفي التهمة\n\nValve ردت بعد انقضاء الموعد النهائي، واعترضت على الادعاء بأنها تيسر المقامرة، وأفادت بأنها عطلت الحسابات المرتبطة، وأوضحت أنها لا ترغب في إيقاف التداول وخدمة OpenID للجميع. كانت هناك منصة واحدة على الأقل ورد ذكرها في التقارير الصحفية المتعلقة بالإشعارات الصادرة في يوليو (CSGOFast) لا تزال تعمل بعد مرور عقد من الزمن. ولا يمكن أن يكون هذان الواقعان صحيحين إلا إذا كان المشغل قد استبدل الحسابات المعطلة؛ ولم يتم نشر السجل الذي من شأنه إثبات ذلك. وينبغي على لجنة WSGC أن تطلب من Valve التوفيق بين هذين الأمرين.\n\n2026\nالمسارات التي تم رصدها في سبتمبر 2026\n\nيسجل سجل المسار 44 منصة تقوم بالمصادقة عبر مضيفي مصادقة تابعين لنطاقات منفصلة، بما في ذلك CSGOFast، باستخدام OpenID وآليات التداول Valve الموصوفة في عام 2016. ولم يتم تقديم سجل التنفيذ الذي من شأنه أن يوضح أي المشغلين تم قطع الخدمة عنهم.\n\nتقرير اللجنة · 30 يناير 2018\nبعد مرور ثمانية عشر شهراً على رد Valve، لا تزال الهيئة التنظيمية تصف ذلك بأنه «نية».\n\nوفي معرض إحاطة مجلسها التشريعي خلال الجلسة العامة الخاصة بمشروع القانون HB 2881، وصفت اللجنة البيان الصادر في يوليو 2016 بعباراتها الخاصة: Valve \"أعلنت عن عزمها على اتخاذ إجراءات صارمة ضد استخدام منصتها لتسهيل المقامرة على \"السكينز\".\" وتسجل الصفحة نفسها تأثير ذلك الإعلان على توقعات القطاع — \"ونتيجة لذلك،\" تم تعديل التوقعات المتعلقة بسوق المقامرة عبر الإنترنت لعام 2020 من $19.7 مليار إلى $670 مليون، وهو انخفاض بنسبة 97 في المائة تقريبًا، بناءً على الإعلان وحده. وقد تغيرت التوقعات. أما سجل الإنفاذ لكل مشغل الذي من شأنه تبرير ذلك، فلم يُنشر بعد.\n\nأرقام السوق هي تقديرات صادرة عن Narus Advisors / Eilers & Krejcik Gaming تم إعادة نشرها في تقرير اللجنة، وليست نتائج توصلت إليها اللجنة؛ ويشير الوثيقة نفسها إلى أن حجم الرهانات على «السكين» في عام 2016 بلغ حوالي $5 مليار، منها ما يقارب $3 مليار على مواقع على غرار الكازينوهات. تم استرجاعه في 2026-09-22، SHA-256 c507c9025f93da0aadaf395c4d8882f25973211c318ee8e9b6f18a5b3755e050.\n\nيمكن مقارنة الموقف الرسمي الذي أعلنه Valve في عام 2016 بالبنية التحتية الملحوظة اليوم. والسؤال المطروح هو ما إذا كان التطبيق قد شمل الحسابات والمسارات التي يستخدمها المشغلون المحظورون. إن إصدار إشعار مدته عشرة أيام لا يُعد دليلاً على أن الإشعار قد تم تنفيذه لدى جميع المشغلين المذكورين فيه. تُعد الإجراء الذي اتخذته OPSkins في عام 2018 هو التدخل الوحيد الموثق ضد مشغل محدد؛ وبالنظر إلى أن الفحص شمل 189 منصة ولم يتم نشر أي سجل خاص بكل مشغل على حدة، فإن إجراءً موثقًا واحدًا لا يُشير إلى وجود نمط محدد في تطبيق الإجراءات.\n\nإشعار لجنة المقامرة في واشنطن لعام 2016 ↗ محفوظ 2026-05-20 ↗ · رد Valve بتاريخ 17 أكتوبر 2016 (نسخة من الوثيقة) ↗ · عرض إعلامي قدمته لجنة WSGC إلى الهيئة التشريعية، 30 يناير 2018 (نسخة محلية، 4 صفحات) ↗ · الملف نفسه على موقع wsgc.wa.gov ↗ · سجل الاسترجاع والهاش ↗ · حركة Valve على OPSkins لعام 2018 ↗ محفوظ 2026-03-07 ↗ · تدقيق المسار الحالي ↗\n\nالتدقيق الجنائي الطولي · الأهداف التي شملتها أوامر التوقف والكف لعام 2016\n«عقد الإشعار قبل 10 أيام»: تدقيق جنائي لتقييم مدى الصمود في المواقع الـ23 المحددة\n\nفي 19 و20 يوليو 2016، أصدر المستشار القانوني العام كارل كواكينبوش إخطارات رسمية بوقف النشاط إلى 23 منصة مقامرة تعتمد على «السكين»، وأمرها بوقف الاستخدام التجاري لـSteam حسابًا ضمن 10 أيام تحت تهديد إغلاق الحساب واتخاذ إجراءات قانونية. وبعد مرور 3,700 أيام، كشفت عملية تدقيق تجريبية عن النمط الحقيقي لتطبيق الإجراءات: فعدد من المشغلين لم يتوقفوا أبدًا عن العمل، بينما استمر آخرون في العمل لمدة تصل إلى ست سنوات بعد الموعد النهائي، وواصل النظام البيئي الذي تبلغ قيمته عدة مليارات من الدولارات الاستفادة من بنية OpenID الخاصة بـ Valve.\n\n5+ مباشر\nستكون قيد التشغيل بالتأكيد في عام 2026 (CSGOBig، CSGO500، CSGOFast، إلخ)\n6 سنوات\nأطول فترة تشغيل بعد الإعلان عن الإغلاق (ظل موقع CSGOatse نشطًا حتى عام 2022)\n$5.01B\nحجم الرهانات في سوق «سكين» لعام 2016 (Narus / Eilers & Krejcik)\n200+\nمواقع المقامرة عبر الإنترنت النشطة التي تعمل في ذروة السوق\n«العمالقة الباقون» · الخطة المالية وخطة حركة المرور للفترة 2024–2026\nمن الإنذارات التي تُصدر قبل 10 أيام إلى التكتلات الخارجية: معدل دوران بمليارات الدولارات\n\nبدلاً من القضاء على المقامرة بالـ«سكين»، شكّلت إخطارات Valve الصادرة عام 2016 حافزًا لتطور الصناعة. وقام المشغلون الباقون على قيد الحياة بإعادة هيكلة أعمالهم ككيانات تجارية خارجية (كوراساو، بليز، قبرص)، وابتكروا التداول من نظير إلى نظير (P2P) لتجاوز حظر الروبوتات، ويقومون الآن بمعالجة أكثر من 10 ملايين زيارة شهريًّا للموقع الإلكتروني و مليارات الدولارات من حجم الرهانات السنوي مع الاستمرار في المصادقة عبر Steam:\n\nالمنصة / النطاق\tإشعار يوليو 2016\tنتائج التنفيذ وحالة البقاء\tالتحقق المسجل / الروابط الأساسية\nCSGOBig\ncsgobig.com\tإشعار مدته 10 أيام (يوليو 2016)\tما زال على قيد الحياة في عام 2026\nتم إيقافه مؤقتًا، ثم أُعيد تشغيله؛ تتم عملية المصادقة عبر letmeinbig.com و csgobiglogin.com\tX: @csgobig ↗ · فيسبوك: csgobigofficial ↗\nCSGO500\ncsgo500.com / 500.casino\tإشعار مدته 10 أيام (يوليو 2016)\tما زال على قيد الحياة في عام 2026\nتم تغيير اسمها إلى 500 Casino (ترخيص كوراكاو رقم 8048/JAZ2014-037)، ويبلغ حجم مبيعاتها الشهرية عدة ملايين\tمنصة البث المباشر (500.casino) ↗\nCSGOFast\ncsgofast.com\tإشعار مدته 10 أيام (يوليو 2016)\tما زال على قيد الحياة في عام 2026\nتعمل حاليًا ألعاب الروليت و«كراش» و«الجائزة الكبرى» عبر الموقع steam-login.authtofast.com\tتدقيق صحة الملف ↗\nCSGOLounge / Dota2Lounge\ncsgolounge.com / dota2lounge.com\tإشعار مدته 10 أيام (يوليو 2016)\tما زلت على قيد الحياة في عام 2026\nتركزت أنشطتها على المراهنات باستخدام عملات الرياضات الإلكترونية والعملات المشفرة؛ وحافظت على استمرارية عملياتها\tمنصة البث المباشر ↗\nCSGOCasino\ncsgocasino.net / csgocasino.gg\tإشعار مدته 10 أيام (يوليو 2016)\tبث مباشر عبر «سوكسيسور» (2026)\nتم إعادة توجيه النطاق؛ ويعمل البوابة الخلفية النشطة تحت عنوان csgocasino.gg\tنطاق الخلف ↗\nCSGOatse\ncsgoatse.com\tإشعار مدته 10 أيام (يوليو 2016)\tاستمرت لمدة 6 سنوات (كانت نشطة حتى عام 2022)\nاستمرت عمليات المقامرة بكامل طاقتها لمدة ست سنوات عقب الإنذار النهائي الذي مدته 10 أيام الذي أصدره Valve\tX: @CSGOatsecom (نشط حتى عام 2022) ↗\nCSGOSweep\ncsgosweep.com\tإشعار مدته 10 أيام (يوليو 2016)\tاستمر حتى ديسمبر 2017\nاستمرت في العمل بشكل علني لمدة 17 شهراً بعد انتهاء المهلة\tX: حالة CSGOSweep في ديسمبر 2017 ↗\nCSGOWild\ncsgowild.com\tإشعار مدته 10 أيام (يوليو 2016)\tاستمر حتى ديسمبر 2017\nتم الترويج لها من قِبل مؤثرين بارزين؛ واستمرت لمدة عام ونصف بعد تلقي إنذار التوقف والكف قبل الانتقال إلى العملات المشفرة\tX: @Wild (نشط منذ ديسمبر 2017) ↗\nCSGOPot\ncsgopot.com\tإشعار مدته 10 أيام (يوليو 2016)\tاستمر حتى سبتمبر 2017\nاستمرت عمليات المراهنة على الجائزة الكبرى ذات الرهانات العالية لمدة 14 شهراً بعد صدور الإشعار\tX: @csgopot (نشط في سبتمبر 2017) ↗\nCSGODiamonds\ncsgodiamonds.com\tإشعار مدته 10 أيام (يوليو 2016)\tاستمرت حتى منتصف عام 2017\nاستمر البرنامج حتى عام 2017 على الرغم من الاعتراف بالتلاعب بنتائج البث المباشر للمؤثرين المدعومين\tX: @csgodiamondscom (2017) ↗\nCSGOLotto\ncsgolotto.com\tإشعار مدته 10 أيام (يوليو 2016)\tأُغلق في يوليو 2016\nأُغلق بسبب فضيحة عامة؛ وكان موضوع أمر موافقة صادر عن لجنة التجارة الفيدرالية (FTC)\tأمر التوافق الصادر عن لجنة التجارة الفيدرالية (القضية رقم C-4632) ↗\nCSGODouble\ncsgodouble.com\tإشعار مدته 10 أيام (يوليو 2016)\tأُغلق في يوليو 2016\nالإغلاق الطوعي فور نشر إنذار التوقف والكف\tX: @CSGODouble (تم إغلاقه في يوليو 2016) ↗\nCSGOMassive\ncsgomassive.com\tإشعار مدته 10 أيام (يوليو 2016)\tمغلق عام 2016\nأوقفت عملياتها العامة في أواخر عام 2016\tX: @csgo_massive ↗\nCSGOStrong\ncsgostrong.com\tإشعار مدته 10 أيام (يوليو 2016)\tمغلق عام 2016\nتوقفت عن تقديم خدماتها للجمهور في عام 2016\tفيسبوك: csgostrongfree ↗\nSkins2\nskins2.com\tإشعار مدته 10 أيام (يوليو 2016)\tمغلق عام 2016\nتوقفت عن تقديم خدماتها للجمهور في عام 2016\tفيسبوك: CSNCOM ↗\n\nالمنصة\tحركة المرور الشهرية (الزيارات)\tحجم المبيعات/الحجم التقديري\tالكيان القانوني والولاية القضائية\tالإجراءات التنظيمية الرئيسية والنموذج\nCSGOEmpire\ncsgoempire.com\t2.3 مليون — 9.0 مليون / شهريًا\nمتوسط المدة 6 دقائق أو أكثر؛ 80% مباشر\t$1.5B — $2.5B الحجم السنوي\n>1,000,000 صفقة تداول للجلود عبر نظام P2P شهريًّا؛ $6.4 مليون أمر تداول نشط في قاعة التداول\tشركة «مونريل ليميتد بي.في.» (كوراساو رقم 148182)\nالمدفوعات: JHOLT LTD (قبرص)؛ المؤسس: «Monarch» (أوسي كيتولا)\tرائدة في مجال تداول السلع بين الأقران (P2P) بدون رسوم؛ مرخصة من كوراساو برقم OGL/2024/1183/0869\nCSGORoll\ncsgoroll.com\t2.74 مليون — 3.5 مليون / شهريًّا\nمتوسط المدة: 9 دقائق و23 ثانية؛ معدل الارتداد: 16%\t$1.0B — $2.0B الحجم السنوي\nتقدر الإيرادات السنوية للشركة من «ميزة الكازينو» بما يتراوح بين $100M و$200M\tشركة فيرال هولدينغز المحدودة\nيقع مقرها الرئيسي في مدينة بليز، بليز (رقم التسجيل 171519)\tتم حظرها من قبل هيئة ACMA الأسترالية (مايو 2023)؛ وكانت ترعى فريق G2 Esports من الفئة الأولى الذي يضم لاعبين دون السن القانونية\nكازينو 500 (CSGO500)\n500.casino / csgo500.com\t220 ألف — 425 ألف / شهريًا\nحوالي 105 آلاف زائر فريد شهريًّا\t$100ك / أسبوع ($5.2م/سنة) في روياليس\nمتطلبات الرهان لللاعبين الكبار: $400 رهان مقابل كل $1 راكباك\tشركة Perfect Storm B.V. (كوراساو رقم 150536)\nترخيص هيئة مراقبة الألعاب في كوراساو رقم OGL/2024/1354/0882\tتم حظرها من قبل هيئة الرقابة على الألعاب السويدية (سبيلينسبكتسيون) (نوفمبر 2023) بسبب استهدافها للاعبين السويديين دون ترخيص\nCSGOBig\ncsgobig.com\t~169,600 / شهريًّا\nمتوسط المدة: 19 دقيقة و12 ثانية؛ الانتخابات التمهيدية الأمريكية\tحجم مبيعات سنوي يبلغ عدة ملايين\nالصناديق الغامضة، والروليت، ومعارك الصناديق\tيعمل عبر توجيه الوكيل الإضافي\nletmeinbig.com (مسجل في عام 2023) و csgobiglogin.com\tتم إعادة إطلاق \"Target of July 2016 C&D\" باستخدام بنية مصادقة بالوكالة\nCSGOFast\ncsgofast.com\tحوالي 150 ألف — 250 ألف شهريًّا\nجمهور عالمي متعدد اللغات\tحجم مبيعات سنوي يبلغ عدة ملايين\nألعاب الروليت وألعاب «كراش» عالية السرعة\tالكيانات التشغيلية الخارجية\nالمسارات Steam المصادقة عبر steam-login.authtofast.com\tكانت الشركة هدفًا لإخطار التوقف عن العمل (C&D) في يوليو 2016؛ ولم توقف عملياتها قط؛ وما زالت نشطة في عام 2026\nCSGO Polygon\ncsgopolygon.com / plg.bet\tحوالي 300 ألف — 500 ألف شهريًّا\nهيمنة دول رابطة الدول المستقلة وأوروبا الشرقية\tحجم مبيعات سنوي يبلغ عدة ملايين\nالعملات المشفرة وروليت السكين، والمراهنات على المباريات\tهدف الموجة الثانية (أكتوبر 2016)\nتركيز على العملات المشفرة باستخدام النطاق المطابق plg.bet\tاستمرت لمدة عقد كامل؛ وتواصل تصفية الأصول عبر واجهات برمجة التطبيقات (API) التابعة لأطراف ثالثة\nالموجة الثانية: لماذا استهدفت إنذارات التوقف والكف الصادرة عن Valve ما يزيد عن 43 موقعًا في المجموع\n\nفي 17 أكتوبر 2016، أبلغ المستشار القانوني لشركة Valve لجنة المقامرة بولاية واشنطن رسميًا أنه عقب الإخطارات الـ23 الأولى التي صدرت في 19 يوليو، كانت شركة Valve قد أرسلت خطابات إنذار بالكف عن الممارسة إلى أكثر من 20 موقعًا إضافيًا للمقامرة بالسكين (مما رفع العدد الإجمالي الرسمي إلى ما يزيد عن 43). وقد استدعت هذه الموجة الثانية ذلك لأن القائمة الأولية أغفلت، لسبب غير مفهوم، أكبر مراكز المقامرة وأكثرها شهرة في العالم:\n\nCSGOJackpot.com: الشركة الرائدة تاريخياً في مجال «جوائز اليانصيب الجلدية»، والتي تعاملت مع مئات الملايين من حيث الحجم قبل أن تغلق أبوابها تحت تهديد توجيه اتهامات فيدرالية.\nCSGOShuffle.com: الموقع الذي كان في قلب فضيحة البث المباشر التي اندلعت في يوليو 2016، حيث تبين أن مقدم البث على منصة «تويتش» PhantomL0rd كان يمتلك سراً حصة تبلغ 33% من الشركة، وكُشف عن تورطه في التلاعب بالنتائج باستخدام أموال الشركة.\nالنظام البيئي الكلي (أكثر من 200 مشغل): وفقًا لدراسة استقصائية أجرتها شركتا «ناروس أدفايزرز» و«إيلرز آند كريجيك جيمنج»، كان هناك أكثر من 200 موقع مختلف للمقامرة بالـ«سكينز» يعمل في عام 2016، حيث حققت حجم رهانات بلغ $5.01 مليار من 3.03 مليون لاعب نشط. وقد استهدفت الرسائل الـ43 التي أرسلتها شركة Valve أقل من 20% من السوق النشطة.\nالتحقيقات الحكومية والرقابية الرسمية بشأن المقامرة عبر تطبيق «Steam Skin»\n\nتم توثيق ظاهرة المقامرة عبر الإنترنت في العديد من التحقيقات القانونية الرسمية، وإجراءات الإنفاذ، وورقات المواقف الحكومية:\n\n1. لجنة المقامرة بولاية واشنطن (WSGC) (2016–2018)\n\nصدرت مطالبة رسمية بـ«الكف والامتناع» في 5 أكتوبر 2016؛ ونُشرت مذكرة تشريعية في 30 يناير 2018 توثق أن «السكينز» تعتبر معادلات نقدية، وتشير إلى حجم المراهنات على «السكينز» البالغ $5.0B.\n\nالتقرير التشريعي لمجلس ولاية ويست فرجينيا (WSGC) بصيغة PDF (نسخة محلية) ↗\n2. لجنة التجارة الفيدرالية الأمريكية (FTC) (سبتمبر 2017، الملف رقم C-4632)\n\nأول إجراء إنفاذ تنظيمي اتحادي يتعلق بالمقامرة عبر الإنترنت، موجه ضد مالكي موقع CSGOLotto، تريفور مارتن وتوماس كاسيل، بتهمة الممارسات الخادعة والتحكم غير المعلن في المنصة.\n\nقرار لجنة التجارة الفيدرالية (FTC) وأمر الموافقة ↗\n3. ورقة موقف لجنة المقامرة في المملكة المتحدة (UKGC) والتدقيقات المتعلقة بالشباب\n\nصُنفت «السكينات» داخل الألعاب رسميًا على أنها «أموال أو ما يعادلها» بموجب قانون المقامرة لعام 2005. وأظهرت استطلاعات لاحقة أن أكثر من 11% من الأطفال الذين تتراوح أعمارهم بين 11 و16 عامًا قد راهنوا بـ«السكينات» في ألعاب الفيديو.\n\nمستودع أبحاث هيئة المقامرة في المملكة المتحدة ↗\n4. لجنة التحقيق المعنية بالبيئة والاتصالات التابعة لمجلس الشيوخ الأسترالي (2018)\n\nتقرير البرلمان الفيدرالي بشأن \"المعاملات الصغيرة في الألعاب للحصول على عناصر تعتمد على الحظ\"، وتقييم آليات صناديق الغنائم في لعبة Valve، وعمليات السحب النقدي في السوق الثانوية، والتحايل على اللوائح التنظيمية.\n\nتحقيق برلمان أستراليا ↗\nالطلب المعلق\n\nنشر سجل الإجراءات التنفيذية: تحديد حسابات المقامرة والروبوتات التي تم تعطيلها، وخوادم الاستجابة التي تم تقييدها، والخدمات التجارية التي حصلت على إذن. ولا يُثبت الحظر العلني والتحذير المنشور على الصفحة الرئيسية أن العملية الأساسية قد توقفت.\n\nالجزء باء — القواعد وسجل الإنفاذ · المادة 12\nاسم المضيف موجود بالفعل في الطلب.\nالسياق وحدود المصدر\n\nيحتفظ Valve بالفعل بقائمة نطاقات (ما يُعرف بـ «مرشح الروابط») ويتلقى بالفعل اسم مضيف المصادقة في كل طلب OpenID. يوضح الكود الوهمي أدناه الشكل المنطقي لربط هذين العنصرين. ولا توجد أدلة علنية تشير إلى أن Valve يقوم بذلك.\n\nValve يُشغّل بالفعل قائمة حظر للنطاقات. Valve يتلقى بالفعل عنوان المضيف الذي يتم تسجيل الدخول منه في كل طلب OpenID. لا حاجة إلى بناء أي شيء — ما عليك سوى ربط الاثنين معًا. هذا هو عملية البحث عن اسم المضيف في قائمة يقوم Valve بتحديثها بنفسه. الكود الوهمي أدناه هو مجرد توضيح، وليس التنفيذ الخاص بـ Valve.\n\nforensic_autoban.py\n# كود زائف توضيحي — Valve.block_domain() و flag_session_as_mitm() ليستا استدعاءات حقيقية لواجهة برمجة التطبيقات (API). وهذا يوضح البنية المنطقية لإجراء التخفيف Valve الذي يمكن تنفيذه ضد نطاقات مصادقة الوكيل، وليس التفاصيل الداخلية الفعلية لـ Valve.\n# توضيح: الشكل المنطقي لعملية التحقق من طلب OpenID الوارد\ndef audit_openid_request(طلب):\nblocked_origins = database.الحصول على قائمة المنصات المدرجة في القائمة السوداء()\nproxy_domain = request.params.احصل على(«openid.realm»)\ntarget_redirect = request.params.الحصول على('openid.return_to')\n\n# المنطق: إذا قام الوكيل بإعادة التوجيه إلى موقع محظور، فيجب حظر هذا الوكيل.\nمن أجل الموقع في blocked_origins:\nإذا الموقع في target_redirect:\nValve.حظر النطاق(proxy_domain)\nValve.flag_session_as_mitm(request.session)\n# النتيجة: تم رفض طلب تسجيل الدخول الخاص بهذا المضيف\n\nملاحظة:\nعندما يكون النطاق الرئيسي موجودًا بالفعل في «مرشح الروابط» (على سبيل المثال: howl.gg، محظور 2026-09-18/19/21) ويظهر مضيف المصادقة الخاص به (howl.uno) في طلب OpenID الصادر من زر تسجيل الدخول الخاص بذلك الموقع، فإن الارتباط يمكن ملاحظته في Valve من بيانات الطلب الخاصة به. يمكن أتمتة عملية الفحص؛ لكن تنفيذها ليس كذلك.\nالسوابق الموثقة والمبلغ عنها\n\nValve تدخلت ضد مشغل خارجي مرة واحدة على الأقل وفقًا للسجلات: ففي عام 2018، ألغت حق وصول شركة OPSkins إلى نظام ExpressTrade (إعلان Valve ↗ محفوظ 2026-03-07 ↗). كما تشير تقارير المجتمع الصادرة في عام 2018 إلى فقدان إحدى المنصات التجارية (SkinJar) لإمكانية الوصول؛ وهذه التقارير لم يتم التحقق منها، وقد تم استنتاج الآلية من النتيجة، وليس من عملية تم الكشف عنها.\n\nما تثبتُه هذه السابقة:\n\nValve يمكنها قطع وصول مشغل تابع لجهة خارجية متى شاءت. وكان موقع CSGOFast، الذي ورد ذكره في التقارير الصحفية المتعلقة بالإشعارات الصادرة في يوليو 2016، يعمل على 2026-09-21 باستخدام مضيف مصادقة مسجل في 2026-06-30 لم يُسفر عن أي حظر من «Link Filter». ولم يتم توضيح سبب قطع الخدمة عن مشغل واحد دون غيره في أي معايير منشورة.\n\nما الذي يظهره تاريخ التسجيل وما الذي لا يظهره\n\nيُعد تاريخ تسجيل مضيف المصادقة الحد الأدنى للوقت الذي يمكن أن يكون فيه المضيف قد ظهر لأول مرة في طلب OpenID؛ وهو لا يُثبت الاستخدام المستمر. sc-auth.net، على سبيل المثال، تم تسجيله تحت الرمز 2019-04-02 (RDAP) ولوحظ في مسار تسجيل الدخول Steam لموقع Skin.Club في سبتمبر 2026؛ وما حدث بين هذين التاريخين غير متوفر في السجلات العامة.\n\nالتدقيق المقارن: معايير الامتثال لواجهة برمجة التطبيقات (API)\nالبعد التنفيذي\tقواعد واجهة برمجة تطبيقات GitHub\tSteam واجهة برمجة تطبيقات الويب (Valve)\n1. الحياد في مسألة الامتثال\tتنطبق على كل حساب القواعد المنشورة والموحدة، وحدود المعدل الموثقة (على سبيل المثال: 5,000 مكالمة/ساعة للمستخدمين المصادق عليهم، و15,000/ساعة لمنظمات GitHub Enterprise Cloud)، وسياسات الاستخدام المقبول المنشورة.\tلا توجد معايير منشورة. يتم إنهاء الحسابات الفردية بموجب بنود الأتمتة والاستخدام التجاري (الشكاوى المؤرشفة)، في حين لم يتم نشر أي سجل إنفاذ لكل مشغل على حدة فيما يتعلق بالمنصات التجارية.\n2. إساءة استخدام OpenID / وكيل المصادقة\tتسمح السياسات المنشورة على GitHub بتعليق أو إلغاء تطبيقات OAuth ورموزها في حالة إساءة الاستخدام، وتصف وثائقها عملية الإلغاء التلقائي للرموز المكشوفة (ملخص المؤلفين لوثائق GitHub).\tلم تسجل مضيفي المصادقة ذوي المجالات المنفصلة التي لوحظت في Steam من تدفقات OpenID (مثل rbsnin.com و howl.uno و sc-auth.net) أي حظر من «Link Filter» في 2026-09-21، في حين أن مجالاتهم الرئيسية تعرضت للحظر.\n3. تحقيق الأرباح من الإساءة\tلا تتقاضى GitHub أي رسوم معاملات على العناصر التي يتم نقلها بواسطة أنظمة أتمتة تابعة لأطراف ثالثة؛ حيث يعتمد نموذج إيراداتها على الاشتراكات وعروض السوق.\tValve يبيع مفاتيح الصناديق التي تنتج العناصر، ويفرض «سوق المجتمع» رسومًا إجمالية تبلغ حوالي 15% على المبيعات التي تتم داخل السوق. ولم يتم تقدير أي رقم هنا للإيرادات المنسوبة إلى منصات الطرف الثالث.\n4. مدة بقاء حلقات التهرب\tتتوقف معرّفات عملاء OAuth الموقوفة عن العمل على مستوى المنصة بأكملها فور إيقافها؛ ولا تذكر الوثائق مدة محددة لاتخاذ الإجراء، ولا يُفترض وجود مدة محددة هنا.\tلم تسفر عمليات الفحص الخاصة بـ 2026-09-19 و2026-09-21 عن أي حجب بواسطة «Link Filter» بالنسبة لمضيفي المصادقة ذوي النطاقات المنفصلة التي تتراوح تواريخ تسجيلها بين عام 2011 وسبتمبر 2026. وتُعد تاريخ التسجيل الحد الأدنى للاستخدام المحتمل، وليس دليلاً على الاستخدام المستمر.\nالمصادر: عمود GitHub — الوثائق المنشورة من GitHub بشأن حدود استخدام واجهة برمجة التطبيقات (API) وسياسات المنصة (ملخص من إعداد المؤلفين، لم يتم الاقتباس منه) · عمود Steam — عمليات فحص مرشح الروابط لـ 2026-09-19 و2026-09-21 (linkfilter-recheck-2026-09-21.json)، سجل RDAP (domain-registration.json) وشكاوى الدعم المؤرشفة (أرشيف الأدلة).\nالجزء ب — القواعد وسجل الإنفاذ · المادة 13\nفجوة السعر «off-Steam»\n\nتوجد هذه القطعة في مخزون Steam؛ بينما تتم عملية البيع في مكان آخر. وكان هناك سلاح AWP Dragon Lore جديد من المصنع 62 عرضًا حاليًا على CSFloat؛ أرخص سعر معروض $10,623.95. لا يمكن للسوق الخاصة بـ Steam عرض سعر طلب أعلى من $1,800 تقريبًا. وللبيع بالسعر الأعلى الملحوظ، يحتاج المالك إلى مشترٍ أو سوق خارج Steam. ولا يزال العنصر ونقله يعتمدان على Steam.\n\nWhat this means — the Community Market listing ceiling\n\nSteam’s own market refuses a listing above roughly $1,800. A seller may ask less, never more. Items whose market price sits above that line therefore cannot be sold at that price on Steam at all — which is the mechanism that moves those sales to third-party venues while the item itself never leaves Valve’s inventory system.\n\nSection 13 — the off-Steam price gap →\n\nالسياق وحدود المصدر\n\nترد في هذا القسم ثلاث تهم مختلفة، وهي غير قابلة للتبادل. 245 هو عدد فئات أسماء العناصر في CS2 التي تجاوز أرخص عرض نشط لها قيمة $1,800 في CSFloat وحدها، في 20 سبتمبر 2026. 241 وهي نفس المجموعة مطروحًا منها الفئات الأربع المثبتة عند السقف $100,000 في CSFloat، وهي اللوحة التي يُحسب على أساسها الحد الأدنى $13.63M. 248 هذه لقطة مختلفة: الفئات التي تجاوز سعرها الحد الأقصى في اثنين أو أكثر من خمسة أسواق في 23 سبتمبر 2026. تتداخل هذه الأسواق، لذا يجب ألا تُجمع أبدًا الأرقام الواردة من منصات مختلفة. كل رقم هنا يمثل سعر العرض، وليس صفقة بيع مكتملة، ولا يمثل أي منها إيرادات أو مبيعات أو أرباحًا — سواء بالنسبة لـ Valve أو لأي جهة أخرى. القيم المدرجة في موقع PriceEmpire هي تقديرات مقربة ينشرها ذلك الموقع، كما أن بطاقة Steam الخاصة به تغطي عناصر من ألعاب Steam أخرى، لذا فإن نطاقات المقارنة ليست متطابقة.\n\nسلعة واحدة. نظامان للتسعير.تابع السجل\nالخطوة 3 / 3\n\nعند هذا الطلب، يحتاج البائع إلى منصة أو مشترٍ خارج Steam. ولا يزال هذا المنتج خاضعًا لنظام المخزون والنقل الخاص بـ Steam.\n\nSTEAMحول $1,800الحد الأقصى المعلن لإدراج المنتجات في سوق المجتمع\nالكتالوج المحفوظ$10,623.95جديد من المصنع، AWP Dragon Lore، يرجى تحديد السعر\nالتابعيةلا يزال العنصر Steamلا يزال الرصيد والتحويل عند Steam\n01 / العنصرValve قائمة الألعابعنصر من لعبة CS2 أو Dota 2 موجود في Steam\n02 / السقفحول $1,800 في Steamالسعر الأقصى لإدراج واحد في السوق\n03 / الاستفسار الخارجي$10,623.95 لـ «Dragon Lore»أرخص عرض لـ CSFloat في اللقطة المؤرخة\n04 / التسليمSteam لا يزال موجودًا في السلسلةتعتمد الملكية ونقل الملكية على نظامه\nبنية السوق · لقطة تاريخية، 20 سبتمبر 2026\nالفارق في الأسعار قابل للقياس.\n\nقمنا بحساب فئات أسماء العناصر التي كان أرخص عرض ساري المفعول لها أعلى بقليل من $1,800.، وCSFloat، وSkinport هي لقطات منفصلة تحتوي على مخزونات متداخلة من CS2؛ ولا يمكن جمع أعدادها. تُظهر العروض الخارجية الأماكن التي يتم فيها نشر أسعار طلب أعلى، في حين أن Steam لا يزال يتحكم في ملكية العناصر ونقلها.\n\n245فئات CS2 · CSFLOAT\n166فئات CS2 · SKINPORT\n3فئات DOTA2 · SKINPORT\n$10,623.95أسئلة حول طابق «دراغون لور»\n\nDragon Lore: 62 يضم موقع CSFloat عروضًا في فئة «Factory New»؛ والسعر المعروض هو السعر المطلوب، وليس سعر بيع مؤكد. Steam يسمح بعرض السلعة بسعر أقل، لكنه لا يسمح بنشر السعر المطلوب الأعلى الذي تمت ملاحظته. ويؤكد بيان Valve الوارد في الرابط 2016 علمه باستخدام مشغلي المقامرة لـ OpenID والبنية التحتية التجارية لـ Steam. ويجب تحديد ما إذا كان سوق طرف ثالث معين ينتهك قواعد Valve بشكل منفصل.\n\nاطلع على السجل الكامل →CSFloat JSON ↗Skinport JSON ↗بيان \"2016\" الصادر عن منظمة Valve ↗\nواجهة برمجة تطبيقات CSFLOAT المباشرة / لقطة مؤرخة$13.63م\n\nالحد الأدنى للقيمة الإجمالية المطلوبة في 241 فئة من المنتجات و 3,395 عروض سارية. تُحسب هذه القيمة بضرب أرخص سعر عرض في كل فئة × عدد عروض البيع الخاصة بها. وقد استُثنيت من هذه اللوحة المتحفظة أربع فئات مثبتة عند الحد الأقصى $100,000 الخاص بـ CSFloat.\n\nما الذي يُوضِّحه هذا الرقم بالدولار\n\nتمثل هذه العروض ما لا يقل عن $13,631,888.25 في الأسعار المعروضة للبيع لهذه المجموعة الفرعية المحدودة من CSFloat. وعند إدراج الفئات الأربع ذات الأسعار القصوى، نحصل على $14,231,888.25. هذا هو الحد الأدنى لطلبات الشراء النشطة، وليس المبيعات المنجزة، أو حجم المبيعات النقدية، أو الأرباح، أو سوق CS2 بأكمله.\n\nإعادة الحساب استنادًا إلى لقطة CSFloat المكونة من 245 صفًا ↗\nPRICEEMPIRE / القيمة المدرجةSteam: رقم 15 من أصل 39\nتُدرج العديد من الأماكن قيمة بالدولار تزيد عن Steam.\nUUSkins\n$133.8م\nYouPin898\n$127.5M\nBuff.163\n$104م\nMoon.Market\n$100.3م\nوايت ماركت\n$89.6م\nBuff.Market\n$86.7م\nSteam\n$31م\n\nأكبر ستة قيم معروضة وSteam. يقوم برنامج PriceEmpire بتقريب هذه الأرقام؛ ويُظهر Steam $31م. وهناك 14 مكانًا مدرجًا في القائمة يتفوق عليها من حيث القيم المعروضة بالدولار.\n\nPRICEEMPIRE / عدد العروضSteam: رقم 1 من 39\nSteam لا تزال تتصدر من حيث عدد العروض.\nSteam\n32.2 مليون\nYouPin898\n5.9 مليون\nC5Game\n4.6 مليون\nHaloSkins\n4.4 مليون\nسكينبورت\n3.8 مليون\n\nSteam يُظهر 32.2 مليون العروض. يختلف عدد العروض عن إجمالي القيمة المطلوبة؛ فقد تهيمن العديد من العقارات المعروضة بأسعار منخفضة على العدد الإجمالي.\n\nالمصدر: المقارنة العامة على موقع PriceEmpire ↗ محفوظ 2026-09-21 ↗، تم التقاطه في 2026-09-20 الساعة 19:03 بالتوقيت العالمي المنسق؛ استخراج مؤرخ من الصف 39 ↗. الأرقام الواردة هي تقديرات تقريبية، وقد تتداخل المخزونات بين المواقع المختلفة. كما تتضمن بطاقة Steam وصفًا لعناصر من ألعاب Steam أخرى، لذا فإن نطاقات هذه الألعاب ليست متطابقة. وتُعبِّر القيمة المدرجة عن أسعار الطلب، وليس عن المبيعات أو الإيرادات.\n42\nمصدر آخر / ستياماناليست\nالنظام البيئي التجاري واضح للعيان.\n\nدليل السوق الخاص بـ SteamAnalyst محفوظ 2026-07-19 ↗ تضم القائمة 42 منصة بيع تابعة لأطراف ثالثة لـ CS2 إلى جانب Steam، مع بيانات أسعار حديثة لـ 32 من أصل 43 منصة مدرجة. أما موقع PriceEmpire فيدرج 39 منصة بيع وفقًا لمعايير الاختيار الخاصة به. شركات محددة، وعروض عامة، وأسعار مرئية: هذا الاقتصاد مفتوح للتدقيق.\n\nالآلية هي الحد الأقصى: عملية البيع تترك «ستيم»، أما المنتج فلا.\n\nعبر خمسة أسواق تم توثيقها في لقطة واحدة مرخصة، يتم تسعير 248 فئة من منتجات CS2 بشكل مستقل بسعر يتجاوز الحد الأقصى للإدراج في Steam البالغ $1,800 تقريبًا بمقدار وحدة واحدة أو أكثر — وكل فئة منها غير موجودة في Steam. وقد صنفت اللقطة نفسها الكتالوج بأكمله حسب السعر: حيث يضم سوق Valve فئة 95.3% من فئات المنتجات التي تقع تحت الحد الأقصى، وفئة 1.9% من تلك التي تقع فوقه. ولا يعكس هذا الانخفاض تراجعًا في الطلب؛ بل يتوافق تمامًا مع القاعدة المنشورة. يتطلب البيع بهذه الأسعار وجود مشترٍ خارجي أو سوق خارجي، في حين أن Steam لا تزال تتحكم في المخزون وعملية النقل — حيث تغادر الصفقة نقطة الدفع الخاصة بـ Valve، بينما تظل عملية التسليم على البنية التحتية الخاصة بـ Valve.\n\nSteam الأسئلة الشائعة حول السوق ↗محفوظ 2026-09-21 ↗Steam اتفاقية الاشتراك ↗محفوظ 2026-09-21 ↗مجموعة بيانات أطلس الأسواق الخمسة ↗بيان المنشأ ↗لقطة سابقة لـ CSFloat ↗لمحة سريعة عن Skinport ↗PriceEmpire ↗محفوظ 2026-09-21 ↗SteamAnalyst ↗محفوظ 2026-07-19 ↗سجل الفجوة السعرية ↗أطلس سلم الأسعار ↗\n\nالجزء ج — الأطر القانونية\nالجزء ج — الأطر القانونية · المادة 14 · وصول الموظفين\nمن يمكنه إعادة ضبط الضمانات؟\nالسياق وحدود المصدر\n\nكما يعتمد أمان الحساب على الأشخاص الذين يمكنهم استعادة الحساب، أو الاطلاع على السجلات الخاصة، أو إعادة ضبط إجراءات الحماية الخاصة به. ويجب أن يتتبع التحقيق هذه الإجراءات التي تتمتع بامتيازات بنفس الدرجة من الدقة التي يتتبع بها إساءة استخدام واجهة برمجة التطبيقات (API).\n\nتمنح عملية استعادة الحساب موظف الدعم صلاحية نقل الحساب بعيدًا عن مالكه. وقد أكد Valve كتابةً، مرتين — في فبراير 2023 ونوفمبر 2025 — أن هذه الصلاحية استُخدمت لتسليم الحسابات إلى الأشخاص الخطأ. بفارق ثلاثة وثلاثين شهراً، عبر القناة نفسها. أدناه: قيمة هذا الوصول، وست حالات موثقة، والسجل Valve الذي يحتفظ به لكل حالة منها ولم يُكشف عن محتواه لأحد.\n\nشهادة محفوظة / 9 مايو 2025\nتذكرة استرداد أدت إلى تعطيل إجراءات الأمان الخاصة بالحساب، وخسارة مُبلغ عنها قدرها $10,000\n\nأفاد أحد المستخدمين في أرشيف الدعم المُجمع بأن فريق الدعم Steam قام بإعادة تعيين كلمة المرور وتعطيل حماية الحساب بعد أن قدم شخص آخر تذكرة استرداد. ويقول صاحب التقرير إن الحساب كان غير نشط منذ سنوات، ويحتوي على عناصر تعود إلى الفترة بين 2016 و2017، وكان يحتوي على Steam Guard، وهاتف مرتبط به، ورموز استرداد مخزنة.\n\n\"Steam على الرغم من ذلك، فقد سمح فريق الدعم لشخص آخر بالوصول إلى حسابي.\"\n\nادعاء من منظور الشخص الأول، محفوظ في steam_support_tickets_MEGA.json، السجل رقم 110. اقرأ المنشور الكامل الذي تم التقاطه ↗\n\nهذا ليس مجرد حظ سيئ لمستخدم واحد. فـ«الباب نفسه» — وهو طلب مساعدة يؤدي إلى نقل الحساب إلى من يقدم البيانات الأقدم — هو الطريقة الموثقة المتبعة في كل حالة من الحالات الواردة في السجل أدناه، وقد أشار Valve إلى ذلك كتابةً مرتين.\n\nلا يمكن للمالك أن يخرج فائزاً من هذا الجدال. يطلب نظام الاستعادة إدخال مفتاح القرص المضغوط الأول، والبريد الإلكتروني الأول، والبطاقة الأولى، ورقم الهاتف الأول. هذه البيانات موجودة في قاعدة بيانات Valve، ويقوم فريق الدعم بالوصول إليها وقراءتها — ويُذكر أن سجلها يمتد إلى خمسة عشر عامًا. أي شخص يمتلك نسخة من ملفك سيُظهر دائمًا تاريخًا عنك أكثر مما يمكنك أنت تقديمه. تم اختيار الأهداف لتتناسب مع المعايير: حسابات خاملة لسنوات، وذات قيمة عالية، وغالبًا ما تم شراؤها مستعملة، بحيث لم يعرف حاملها المفتاح الأصلي أبدًا. بعد ذلك، تم حذف الحسابات نهائيًا، مما قطع أثر سجل العناصر الذي يستخدمه المجتمع لتتبع مظهر ما — وهو حذف لا يمكن للمستخدم العادي إجراؤه دون فترة الانتظار القياسية.\n\nأقل الامتيازات / OWASP A01\n\nيجب أن تقتصر امتيازات الاسترداد على المهمة المعنية، وأن تخضع لمراجعة مستقلة وتسجيل. قم بمراجعة من يمكنه إعادة تعيين بيانات الاعتماد، أو إزالة Steam Guard، أو قراءة سجلات الفوترة، أو تصدير بيانات الحساب. إرشادات OWASP بشأن التحكم في الوصول ↗ محفوظ 2026-09-20 ↗\n\nتوفير إمكانية الوصول على نطاق واسعمخاطر نطاق الوصول\nما وراء المخزون.\n\nفي حال إساءة استخدام الوصول الواسع النطاق، يمكن أن تتحول تقنية القياس عن بُعد الخاصة إلى أداة لتصنيف المستخدمين، والتصيد الاحتيالي الموجه، والمراقبة. وتشمل الضحايا المحتملين المستخدمين العاديين، والعسكريين، والشخصيات العامة، وأسرهم. وهذا نموذج تهديد؛ أما الأذونات الدقيقة فتتطلب سجلات التحكم في الوصول.\n\n01 سجل عناوين IP والموقع\nيمكن أن تكشف سجلات عناوين بروتوكول الإنترنت (IP) عن سجل الاستخدام للشبكة والموقع التقريبي. وهي لا تُثبت، في حد ذاتها، التحركات المادية الدقيقة.\n02 بصمة الجهاز\nيمكن لمعرّفات الأجهزة، في حال جمعها وإمكانية الوصول إليها، ربط الجلسات بالحسابات.\n03 قياس الأداء عن بُعد\nيمكن أن تكشف الطوابع الزمنية لتسجيلات الدخول وسجلات الجلسات عن أنماط السلوك المعتادة، بما في ذلك الأنشطة التي لا تظهر في الملف الشخصي العام.\n04 الاتصالات وجهات الاتصال\nمن شأن الوصول إلى الرسائل المحفوظة أو معلومات الاتصال أن يوسع نطاق عمليات تحديد سمات الأفراد والهندسة الاجتماعية.\n05 كشف الهوية\nيمكن أن تربط السجلات الأصلية للبريد الإلكتروني والهاتف والدفع بين حساب مستعار وشخص ما.\n06 إعادة بيع البيانات والمساءلة\nقد تُستخدم قوائم الأهداف التي تم تصديرها في عمليات الاحتيال الموجهة. يجب تحديد الجهة الفاعلة وموقع الوصول والمستلمين والتحويلات؛ فالموقع وحده لا يثبت لا حق الوصول ولا الحصانة القانونية.\n\nValve يصف تسجيل عناوين IP ومعلومات الأجهزة وسجلات الدفع ومقدمي الدعم من الأطراف الثالثة في سياسة الخصوصية، الفقرتان 3 و5.2 محفوظ 2026-09-21 ↗. تسمح هذه السياسة بالوصول إلى الدعم من طرف ثالث — إلا أن سجل التتبع الذي من شأنه أن يوضح أي مقاول قام بالوصول إلى أي فئة، ومتى، وبموجب أي تفويض، لم يتم الكشف عنه.\n\nالقسم 14.1 · السجل · يونيو 2022 → نوفمبر 2025 · كل رقم مذكور مصدره\nValve فتح الباب مرتين، بفارق ثلاثة وثلاثين شهراً بينهما. ولم يُغلق أبداً.\n\nتم الإبلاغ عن ست حالات تم فيها الاستيلاء على الحسابات عبر قناة طلب المساعدة الخاصة بـ Steam، أو من خلال بيانات الاعتماد التي تحميها تلك القناة. كل مبلغ هو الرقم الذي نشره المصدر المذكور، وقد تم ذكر اسم كل مصدر. تم تعويض اثنين من أصل الستة عن خسائرهم بالكامل. لم يكن الفرق بين هذه الحالات والباقي هو ما حدث، بل من كان يراقب.\n\nValve، خطيًا — فبراير 2023\"تمت إزالة العناصر المعنية من حسابك لأنها وردت من حساب تعرض للاختراق من خلال طلب مساعدة فني، وهو أمر يتحمل فريق CS:GO مسؤوليته. وقد قمنا بإلغاء عمليات التبادل وإزالة هذه العناصر من أي حساب استلمها.\"Steam دعم الرد على أحد مستلمي منتجات HFB، الذي أعاد نشره Dexerto، 21 فبراير 2023 ↗ محفوظ 2025-08-18 ↗\nValve، في رسالة أخرى — نوفمبر 2025 · بعد 33 شهرًا\"فشل أحد فنيي الدعم الذي تولى طلب المساعدة في اتباع إجراءاتنا، مما أدى إلى إعادة تفعيل حسابك لصالح شخص آخر. أعتذر عن هذا الخطأ.\"Steam رد الداعم على Hawkeye337، كما ورد في Dexerto، 14 نوفمبر 2025 ↗\n21 يونيو 2022\nHFB — أكبر مخزون في اللعبة$2,000,000+ · تم رفعه إلى $3,000,000+ في المتابعة التي أُجريت في فبراير 2023\n\nسبعة نسخ تذكارية من «AWP Dragon Lores» وسكين «Karambit» رقم 1 ذي الجوهرة الزرقاء، وتبلغ قيمة هذا السكين وحده حوالي $1.26 مليون. كان الحساب خاملاً لمدة ثلاث سنوات مع بقاء تطبيق المصادقة عبر الهاتف المحمول نشطاً؛ وقد تم تغيير عنوان البريد الإلكتروني وكلمة المرور على أي حال، من خلال إجراءات استعادة الحساب عبر قسم الدعم.\n\nنفد المال قبل أن تنفد البضائع. أفادت التقارير بأن $200,000+ وقد تم بالفعل سحب جزء من عائدات البيع عبر موقع market.csgo.com — وهو سوق يُجري المعاملات نقدًا وعبر العملات المشفرة. ويؤدي إلغاء الصفقة إلى استرداد السكن. لكنه لا يُعيد المبلغ النقدي الذي سبق أن سحبه أحد الأطراف.\n\nثم تعطل الإصلاح. قام أحد المشترين بنقل قطعة «Souvenir Dragon Lore» الخاصة به إلى وحدة تخزين داخل اللعبة. لم يتمكن برنامج التراجع الخاص بـ Valve من رؤية ما بداخل الحاوية الخاصة به، لذا قام بإصدار نسخة جديدة للمالك وترك النسخة المخفية كما هي — قام Valve بتكرار $130,000 العنصر أثناء محاولة التراجع عن عملية سرقة. تم الكشف عن الأمر من خلال مطابقة معرّفات العناصر والبلاغات الواردة من المجتمع، وتم حذفه بعد شهر، في يوليو 2022. تم رد المبلغ إلى المشتري من قِبل BUFF، وليس من قِبل Valve. إن الإصلاح الطارئ بهذه الهشاشة ليس إجراءً رقابيًا؛ بل هو ما تفعله المنصة عندما لا يكون لديها أي سيطرة.\n\nDexerto، 21 يونيو 2022 ↗ محفوظ 2022-07-02 ↗ · كاسبرسكي ↗ · مبلغ السحب لكل Esportfire، 22 يونيو 2022 ↗ محفوظ 2026-05-15 ↗، ونُسب ذلك هناك إلى مصادر متعددة على تويتر · التكرار والحذف وفقًا لـ Esportsbetting، 14 يوليو 2022 ↗\n\nتم ترميمهانعكست اتجاهات التداول. وتم سحب السلع من مخزونات الأشخاص الذين دفعوا ثمنها بالكامل.\n14 أغسطس 2022\nCS.Money — الروبوتات الخاصة بالمنصة$6,300,000 · 19,000+ قشرة · التقدير الأولي $1.6M\n\nاستولى المهاجمون على ملفات المصادقة عبر الهاتف المحمول الخاصة بروبوتات التداول في المنصة وأفرغوها من محتواها، ثم أرسلوا جزءًا من الغنيمة إلى متداولين معروفين لإخفاء آثارهم. وقام باحثون من المجتمع بتحديد 55 حسابًا للمهاجمين في غضون ساعات ونشرها.\n\nلم يؤدِ Valve إلى أي تغيير. وكان السبب المقدم هو أن موقعًا تابعًا لطرف ثالث يقع خارج نطاق Steam — وهو نفس Steam الذي جرت عملية السرقة من بدايتها إلى نهايتها عبر مخزونه وواجهة برمجة التطبيقات (API) الخاصة بالتداول ونظام الحسابات الخاص به.\n\nEsportfire، 14 أغسطس 2022 ↗ محفوظ 2025-11-15 ↗\n\nمرفوضلم يحدث أي تغيير في الوضع. وظلت الخسارة على عاتق المنصة ومستخدميها.\nتم الإبلاغ عن\n21 فبراير 2023\nQkss — نفس الباب، نفس الممثل$1,000,000+\n\nتم الإبلاغ عن هذه الحالة على أنها تمت بنفس الطريقة التي تمت بها حالة HFB، من قبل نفس الممثل، ومن خلال نفس طلب المساعدة الفنية. وقد تمت تسوية حالة HFB بالكامل قبل ثمانية أشهر. أما حالة Qkss فلم يتم تسويتها.\n\nطريق واحد. إجابتان. لا يوجد في السجل المنشور ما يميز بين الحالتين سوى حجم الحضور.\n\nDexerto، 21 فبراير 2023 ↗ محفوظ 2025-08-18 ↗\n\nمرفوضلم يتم ترميمه.\nتم الإبلاغ عن\nفبراير 2023\nالتداول بناءً على معلومات داخلية بحد ذاته — عام كامل من ذلك≈ $320,000 · تتضمن الإيرادات على مدار عام تقريبًا، وليست تقييمًا للمخزون\n\nتم الوصول من جانب الدعم إلى سجل الحساب حتى 15 عامًا — مفتاح القرص المضغوط الأول، والرسالة الإلكترونية الأولى، والبطاقة الأولى. هذه هي بالضبط الأدلة التي تطلبها عملية استعادة البيانات، ولهذا السبب يكون صاحب قاعدة البيانات هو دائمًا الطرف الفائز في النزاع مع صاحب الحساب.\n\nكشفت المدونة Mzkshow كيف استهدف المشغل الداخلي «Steam Help» والمتعاون معه «Alexander» الحسابات الخاملة التي تحتوي على ما يزيد عن $100k من السكينز. وقد بيعت بندقية M4A4 Howl مسروقة تحمل هولوغرامات iBUYPOWER وTitan Katowice 2014 بمبلغ $35,000 وانتهى الأمر بفاليري \"b1t\" فاخوفسكي من فريق NAVI، الذي لم يكن لديه أي وسيلة لمعرفة ذلك. وبعد تدخل Valve، قام المقاول بفصل جميع موظفي مكتب الدعم Steam.\n\nVKPlay ↗ · Lis-Skins ↗ · Escorenews (RU) ↗ · Dexerto (الإنجليزية) ↗\n\nلا يوجد سجلValve لم تنشر قط عدد الحسابات التي تأثرت بذلك، ولم تُبلغ الأشخاص المعنيين.\nتم الإبلاغ عن\n2 ديسمبر 2024\n\"ماتفي\" — بعد موجة التسريحات$13,000\n\nتمت الموافقة على استرداد الحساب لشخص قدم بيانات حسابية لم يتمكن المالك نفسه من مطابقتها. وبعد مرور عامين على قيام المقاول بإغلاق مكتب الدعم الخاص به Steam، أسفر اتباع نفس الإجراء عن نفس النتيجة.\n\nمنشور محفوظ، 2 ديسمبر 2024 ↗ محفوظ 2025-08-05 ↗ · صفوف المصدر وعمليات التجزئة ↓\n\nمرفوضلم يتم ترميمها.\n13 نوفمبر 2025\nHawkeye337 (مارك سبورلوك) — والاعتراف الثاني≈ $300,000–$500,000 · المجموعة الكاملة من هولوغرامات كاتوفيتسه 2014\n\nطالب المهاجم بـ 1 بيتكوين وبدأوا في نقل المحتوى إلى حسابات «نيجيف» لتدميره. Steam الرد الكتابي من قسم الدعم هو الاعتراف الثاني المذكور أعلاه: فقد تولى أحد الفنيين معالجة طلب المساعدة، ولم يتبع الإجراءات المتبعة، وقام بتحويل الحساب إلى شخص آخر.\n\nما أدى إلى حل المشكلة هو البث المباشر. بعد ساعات من نشر المنشورات التي وُسمت بـ Valve على منصة X، تمت استعادة الحساب وإعادة جميع الملصقات. لم يكن لدى Qkss هذا العدد من المتابعين.\n\nSkin.club ↗ · Dexerto ↗ · Esportfire ↗ محفوظ 2025-12-17 ↗\n\nتم ترميمهتم التراجع عن الخبر في غضون ساعات من تصدره قائمة الموضوعات الشائعة.\nما يوضحه السجل بشكل لا توضحه أي حالة بمفردها.\n\nلم يُغلق هذا الطريق قط. يعود تاريخ القبول الأول إلى فبراير 2023، والثاني إلى نوفمبر 2025 — بفارق ثلاثة وثلاثين شهراً، مع قيام المقاول بفصل عدد كبير من الموظفين، وتكرار حادثة مسجلة، ووقوع خرق في المنصة تبلغ قيمته $6.3 مليون بين الحادثتين. وبحساب المدة منذ أول سرقة في هذا السجل، ظلت القناة مفتوحة لمدة ثلاث سنوات وخمسة أشهر. وبغض النظر عما تم إصلاحه في عام 2023، فإن طلب المساعدة لا يزال يُوجه إلى الشخص الخطأ في نوفمبر 2025 — حسب ما ذكره Valve بنفسه.\n\nكان مبدأ التعويض يركز على الانتباه، وليس على الضرر. تم استعادته: أكبر مخزون في اللعبة، والمجمع الذي تصدرت مناقشته قائمة الموضوعات الأكثر تداولًا. تم رفض: $1,000,000, $6,300,000, $13,000. أما Valve فلم ينشر قط القاعدة التي يطبقها، لأن أي قاعدة منشورة سيتعين عليها تفسير تلك الثلاثة.\n\nلم يُخبر أحد بذلك. ليس المستخدمون الذين تم استخراج سجلات حساباتهم من قاعدة البيانات، ولا السلطة الإشرافية، ولا السوق التي اشترت هذه العناصر بحسن نية ثم تم استردادها منها. لا يوجد إخطار بحدوث خرق، ولا تقرير عن الحادث، ولا إحصاء للحسابات المتضررة — والعائدات التي تُترك في شكل أموال، من خلال منصات التداول التي تدفع نقدًا وعملات مشفرة. ولا يمكن أن يتبع انعكاس الصفقة الأموال الخارجة من Steam.\n\nيحتوي Valve على سجل تدقيق الدعم، وسجل تذاكر الاسترداد، وسجل المعاملات لكل سطر أعلاه. ولم يتم تقديم أي منها. اطلب نسختك الخاصة →\n\nمسألة NDA\nيجب أن تقترن السرية بالمساءلة الفنية.\n\nقارن بين اتفاقيات السرية والأذونات الفعلية، وضوابط التصدير، وموافقات إعادة التعيين، وسجلات الوصول. لا يمكن للرد النموذجي أن يحل مشكلة الادعاء بأن عملية الاسترداد نفسها قد أسيء استخدامها.\n\nالمواد 28 و32–34 من اللائحة العامة لحماية البيانات (GDPR)\n\nتمنح المادة 33 المسؤول عن معالجة البيانات مهلة 72 ساعة لإخطار السلطة الإشرافية بحدوث خرق للبيانات الشخصية؛ بينما تنص المادة 34 على ضرورة إخطار الأشخاص المتضررين عندما يكون الخطر المحدق بهم كبيرًا. وقد أكدت شركة Valve كتابةً، مرتين، أن قناة الدعم التابعة لها قد سلمت الحسابات إلى أشخاص غير مصرح لهم — بما في ذلك سجلات الحساب وسجلات الفواتير وكل ما يتعلق بها. لم يتم نشر أي إخطار بموجب أي من المادتين، ولم يبلغ أي مستخدم متأثر بتلقيه إخطاراً من هذا القبيل. اقرأ اللائحة ↗ محفوظ 2026-09-20 ↗\n\nأضف طلب الدعم إلى طلبك →\nالجزء ج — الأطر القانونية · المادة 15 · النطاق التجاري\nتتبع مسار الأموال. افصل بين المعاملات.\nالسياق وحدود المصدر\n\nتصبح مسألة الاستخدام التجاري أكثر حدة عندما يتم فصل التدفقات النقدية. فعمليات نقل الأصول إلى أطراف ثالثة، والمبيعات الأساسية لـ Valve، وعمليات السحب النقدي الخارجية، هي معاملات مختلفة.\n\nالمنتج مملوك لـ Valve. والمخزون يبلغ Valve. ويتم إجراء عملية النقل على خوادم Valve. الشيء الوحيد هو أن عملية الدفع تتم في مكان آخر — وهي الخطوة التي تحدد ما إذا كان أي شخص يُعتبر مُرسِل أموال، وهي الخطوة الوحيدة التي لا تقوم بها شركة Valve.\n\nآلية الإيرادات\nالمكان الذي تتحرك فيه الأموال فعليًّا.\nثلاثة مسارات / اقتصاد عنصر واحد\n01 / الحسابقائمة المستخدمين\n\nالبنود الموجودة في Steam\n\n02 / التحويلالتجارة بين الأقران (P2P)\n\nمستخدم ↔ روبوت أو مستخدم ↔ مستخدم\n\n03 / التسويةمنصة خارجية\n\nرصيد الموقع أو السداد Steam\n\nالتوزيعلا يقتصر دور المحرك الاقتصادي على رسوم الانتقال فحسب\n\nSteam توفر البنية التحتية الخاصة بالمخزون والتحويل التي تستخدمها الأسواق الخارجية. ويتمثل الحجة الاقتصادية للتحقيق في أن سيولة إعادة البيع والطلب المتكرر يدعمان الإنفاق على العلب والمفاتيح وقطع الغيار، مع فرض رسوم على المبيعات اللاحقة في «سوق المجتمع». لا تخضع عمليات التحويل المباشر بين الأطراف (P2P) لأي عمولة من «السوق المجتمعية»؛ لكن هذه الحقيقة المحاسبية لا تحسم مسألة الفائدة الأوسع نطاقاً. Valve تحتفظ بالسيطرة على الوصول إلى الحسابات وقيود التداول طوال الوقت.\n\n01 / الطلب الثانويالسيولة وقيمة إعادة البيع\n\nالتجارة الخارجية والطلب على المقامرة\n\n02 / الإنفاق الأساسيالمفاتيح، والحافظات، والكبسولات\n\nالمشتريات من Valve حيثما كانت متوفرة\n\n03 / الإيراداتإيرادات البيع الأولي\n\nبالإضافة إلى الرسوم المفروضة على المبيعات الفعلية في السوق\n\n5% + 10%Steam + رسوم CS2 على مبيعات «Community Market»\n\nالاستنتاج الاقتصادي الذي توصلت إليه الدراسة: يمكن لأسواق إعادة البيع السائلة أن تشجع الإنفاق على السلع الجديدة. ويجمع الرمز المألوف 15% بين معدلات رسوم السوق، مع مراعاة الحدود الدنيا والتقريب؛ وهو ليس ضريبة تُفرض على كل معاملة تجارية خارجية.\n\nجدول رسوم «Valve» لسوق المجتمع ↗ محفوظ 2026-09-21 ↗. في 25 فبراير 2026 رفع المدعي العام لولاية نيويورك دعوى قضائية محفوظ 2026-09-01 ↗ مدعين أن صناديق الغنائم المدفوعة مرتبطة بإعادة البيع النقدي الخارجي وأضرار المقامرة — وهي نفس الصلة التي يوثقها هذا الملف من جانب البنية التحتية التقنية. هذه الشكوى هي مجرد ادعاء، وليست استنتاجًا؛ وقد تم الاستشهاد بها هنا لأن إحدى وكالات إنفاذ القانون التابعة للولاية طرحت سؤالًا مشابهًا للسؤال الذي يطرحه هذا الملف: أين هو سجل الإنفاذ الذي يتطابق مع التصريحات العامة؟\n\n01 / المدخلالإيداع بالعملات المشفرة\n\nسجلات الخدمات الخارجية والمحافظ\n\n02 / التحويلالتوازن → الأسطح\n\nالسلع التي تم تسليمها من خلال Steam صفقة\n\n03 / الخروجبيع العملات النقدية الخارجية\n\nالبائع والمشتري ومزود خدمة الدفع\n\n\"اعرف عميلك\"؟تحديد عنصر التحكم عند كل عملية تسليم\n\nهذا هو المسار الذي يجب اتباعه للتحقيق، وليس خدمة تحويل نقدي تعتمد على واجهة برمجة تطبيقات (API) أصلية Steam. يجب توثيق إجراءات التحقق من الهوية، وعمليات الحفظ، ومعرّفات المعاملات، ومستلمي المدفوعات لدى كل مشغل خارجي قبل التأكيد على إمكانية السحب النقدي دون الحاجة إلى إجراءات «اعرف عميلك» (KYC).\n\nالولايات المتحدة / قانون السرية المصرفية\nصنف النشاط أولاً، ثم الالتزام.\n\nتقوم «فينسين» (FinCEN) بتقييم عمليات تحويل الأموال بناءً على طبيعة نشاط الشركة. يمكن أن يؤدي قبول وتحويل العملة الافتراضية القابلة للتحويل إلى فرض التزامات خدمات مالية، وفقًا للتعريفات والاستثناءات المعمول بها. تقبل محفظة Steam التابعة لـ Valve الأموال وتحوّلها إلى عناصر داخل اللعبة؛ ثم يتم تسييل تلك العناصر من خلال مشغلين خارجيين مقابل عملة حقيقية. تتم معالجة العنصر ونقله عبر البنية التحتية الخاصة بـ Valve؛ أما عملية السحب النقدي فلا تتم عبرها، وما إذا كان أي جزء من تلك الدورة يستوفي تعريفات تحويل الأموال أم لا، فهذه مسألة تصنيف تخص FinCEN، وليست استنتاجًا مستخلصًا هنا.\n\nFinCEN FIN-2019-G001، الفقرات 1–2 و5.1 ↗ محفوظ 2025-07-11 ↗\n\nالاتحاد الأوروبي / غسل الأموال\nتتبع العائدات والمعلومات والمساعدة.\n\nيغطي التوجيه (EU) 2018/1673 غسل الأموال المتعمد والمشاركة في عمليات تتعلق بعائدات جنائية. ويتمثل السؤال التحقيقي في معرفة ما الذي كانت تعرفه شركة Valve عن المشغلين الذين يستخدمون بنيتها التحتية للتداول و«OpenID» بعد 13 يوليو 2016، عندما وصفت ذلك الاستخدام علنًا، وما هي الإجراءات التي اتخذتها تجاههم. لم تنشر Valve أي سجل إنفاذ خاص بكل مشغل على حدة؛ وهذا السجل، وليس هذا الملف، هو الذي سيجيب على السؤال.\n\nالإطار القانوني للاتحاد الأوروبي في مجال القانون الجنائي ↗\n\nمصطلحات قانون مكافحة غسل الأموال السادس (AMLD6): يختلف التوجيه المتعلق بالقانون الجنائي المذكور أعلاه عن التوجيه (EU) 2024/1640، المعروف أيضًا باسم AMLD6. ويحدد هذا الأخير موعدًا نهائيًّا عامًّا لتطبيقه في 10 يوليو 2027، مع استثناءات محددة. المادة 78 ↗ محفوظ 2026-08-30 ↗\n\nالجزء ج — الأطر القانونية · المادة 16 · الإخطار، الرد، المسؤولية\nقانون الخدمات الرقمية: توثيق المعرفة\nالسياق وحدود المصدر\n\nهناك عنصران من عناصر الإخطار بموجب المادة 16 يقعان على عاتق مقدم الطلب وليس ضمن هذا الملف: البيانات الشخصية لمقدم الطلب، وإقرار بحسن النية يفيد بدقة المعلومات. أما كل ما تتطلبه المادة من عناصر أخرى — مثل التفسير المدعوم بالأدلة والموقع الإلكتروني الدقيق — فهي موضحة في القسم 3 وفي سجل المسار، مع الردود المحفوظة ورموز التجزئة، بحيث يمكن لأي طرف تقديمها. وهناك قيدان إضافيان على القانون نفسه: فقدان الإعفاء الخاص بالاستضافة لا يؤدي في حد ذاته إلى إثبات المسؤولية بموجب أي قانون آخر، والرقم 6% الوارد في المادة 52(3) هو سقف قانوني، وليس عقوبة محددة ضد Valve.\n\nبموجب قانون خدمات الرقمية (DSA)، لا يحتفظ مزود خدمات الاستضافة بحصانته من المسؤولية إلا إلى أن تكون لديه معرفة محددة بالمخالفة ويتقاعس عن اتخاذ الإجراء اللازم. هذا الملف هو ذلك الإشعار. وهي تذكر أسماء المضيفين والتواريخ والردود المحفوظة والقيم التجزئية. ومنذ نشر هذا التقرير، لم يعد السؤال هو ما إذا كان Valve على علم بالأمر — بل ما فعله Valve بعد ذلك.\n\n01يوليو 2016 / معرض الملفات\nمطالبة مدتها عشرة أيام.\n\nيُعد الإشعار الذي أُعيد صياغته أعلاه النقطة الانطلاقية التاريخية لمقارنة الإجراءات التنفيذية في إطار التحقيق.\n\n0217 فبراير 2024 / طلب عام\nالنافذة الزمنية لنظام DSA.\n\nافصل بين السلوك التاريخي والسلوك خلال الفترة التي تسري فيها الالتزامات ذات الصلة بموجب قانون الخدمات الرقمية (DSA).\n\n03عشر سنوات / لقطة من الملف الأصلي\nتحتاج المدة إلى سجل للإشعارات.\n\nالوقت المنقضي منذ يوليو 2016 (انظر القسم 11) هو مؤشر خاص بالملف. وهو لا يمثل عشر سنوات من الانتهاكات الثابتة لقانون DSA. يجب ربط كل إشعار ببند محدد، والقانون المعمول به، ودليل التسليم، والرد.\n\nالمادة 52(3) / الحد الأقصى المنصوص عليه في القانون6%\nمن إجمالي المبيعات السنوية على مستوى العالم\n\nالغرامة القصوى في حالة الإخلال بالالتزامات المنصوص عليها في قانون الخدمات الرقمية (DSA)، على أساس السنة المالية السابقة للمزود. ويُعد هذا الحد الأقصى القانوني، وليس غرامة محددة ضد Valve.\n\nالمواد 6 و8 و16 / المعيار القانوني\n\nفيما يتعلق بخدمات الاستضافة ذات الصلة، يمكن أن تؤدي المعرفة المحددة بعدم اتخاذ إجراءات سريعة إلى إلغاء الإعفاء المتعلق بالاستضافة. ويمكن أن يُثبت الإخطار الدقيق بما فيه الكفاية معرفة المحتوى المعني. ولا تفرض قانون خدمات الرقمية (DSA) أي واجب عام للمراقبة؛ كما أن فقدان الإعفاء لا يُثبت بحد ذاته المسؤولية بموجب قانون آخر.\n\nقانون DSA: المواد 6 و8 و16 و52 و53 و93 والاعتبار 17 ↗ محفوظ 2026-09-20 ↗\n\nمراجعة الشكاوى المحفوظة ↗إنشاء الخط الزمني للحساب →تحليل قانوني واقتصادي شامل →\nالجزء ج — الأطر القانونية · المادة 17 · الهوية، والعمر، والوصول التجاري\nالقاصرون: تسجيل الدخول بـ Steam لا يُعتبر تحققًا من العمر\nالسياق وحدود المصدر\n\nلا تظهر بيانات أي قاصر في أي مكان في هذا الملف ولم يتم جمع أي منها: لم يقم المؤلفون بالتسجيل في أي من المنصات المذكورة أو إيداع معلومات فيها أو إتمام عملية تسجيل الدخول إليها. يجب على أي شخص يستند إلى هذا القسم الحفاظ على سرية الأدلة المتعلقة بالأطفال وحجب التفاصيل التي تكشف عن هويتهم من المستندات العامة. يُستشهد هنا بقانون حماية خصوصية الأطفال (COPPA) باعتباره قانونًا خاصًا بخصوصية الأطفال له شروط نطاقه الخاصة — مثل الجمهور المستهدف، والمعرفة الفعلية، والبيانات الشخصية التي تم جمعها — وليس كقاعدة عامة تتعلق بسن المقامرة؛ والشكوى المرفوعة في نيويورك عام 2026 هي ادعاء من قبل سلطة حكومية، وليست حكمًا قضائيًا.\n\n\"تسجيل الدخول باستخدام Steam\" يثبت وجود الحساب. هذا لا يثبت شيئًا بشأن العمر — وفي هذه المواقع، يُعد هذا البوابة الوحيدة الفاصلة بين الطفل والحساب المصرفي. اقرأها مع القسم 3.1: داخل عميل Steam، لا يتم إطلاق التحذير الذي عادةً ما يعرضه المتصفح، لذا لا يراه الطفل أبدًا.\n\nما الذي يوفره OpenID Steamهوية الحساب\n\nمعرّف SteamID مُثبت يُستخدم لتسجيل الدخول أو ربط حساب.\n\n≠\nما يجب على المشغل إثباتهشروط الأهلية للمشاركة\n\nالعمر، والولاية القضائية، وأي إجراءات تحقق من الهوية مطلوبة.\n\nالأساس الفني: وثائق Steamworks OpenID ↗ محفوظ 2026-09-21 ↗. إن إثبات الهوية الموثق لا يُعدّ شهادةً تفيد بأن المستخدم يُسمح له قانونياً بالمقامرة.\n\nقانون حماية خصوصية الأطفال على الإنترنت (COPPA) / الأطفال دون سن 13 عامًا\nحدد المشغل والبيانات.\n\nينطبق قانون COPPA على الخدمات المشمولة الموجهة للأطفال، وكذلك على الخدمات التي لديها علم فعلي بأنها تجمع معلومات شخصية من أطفال تقل أعمارهم عن 13 عامًا. وهو قانون خاص بخصوصية الأطفال، وليس قاعدة عامة تتعلق بسن المراهنة. يجب تحديد الفئة المستهدفة، والبيانات الشخصية التي يتم جمعها، ومدى العلم بذلك، وإجراءات الحصول على موافقة الوالدين.\n\nلجنة التجارة الفيدرالية (FTC): متطلبات قانون حماية خصوصية الأطفال على الإنترنت (COPPA) ↗ محفوظ 2026-09-21 ↗\n\nالأدلة التي يجب الحفاظ عليها\nتسجيل مسار العملية بدءًا من تسجيل الدخول وحتى إجراء الإيداع.\n\nالحفاظ على نظام التحقق من السن في الموقع، وصيغة التسجيل، وشروط الأهلية، وعملية الدفع، وسجل الشكاوى. تقييم كل مشغل على حدة. الحفاظ على سرية أي أدلة تتعلق بطفل، وحجب التفاصيل التي تكشف عن هويته من المستندات المعروضة للجمهور.\n\nومن السجلات ذات الصلة المتعلقة بإنفاذ القانون من قبل الجهات العامة ما يلي: إعلان عن دعوى قضائية في نيويورك لعام 2026 محفوظ 2026-09-01 ↗، التي تزعم وجود ضرر يلحق بالمستخدمين الصغار جراء صناديق الغنائم المدفوعة. ولا يُعد هذا استنتاجاً بموجب قانون حماية خصوصية الأطفال على الإنترنت (COPPA).\n\nالجزء ج — الأطر القانونية · القسم 18 · الطلب بموجب المادة 15 من اللائحة العامة لحماية البيانات (GDPR)\nالطلب. الرد. المقارنة المفقودة.\n\nطلب أربعة أشياء، أحدها السجل الذي سيكشف عن هوية الشخص الذي أضاف مفتاح واجهة برمجة التطبيقات (API) إلى حسابه. بعد ثلاثة أيام، تم إغلاق التذكرة مع رابط إلى صفحة لا تحتوي على أي منها — كما أن الجملة التي اختتم بها ذلك يتعارض معها محامو Valve أنفسهم.\n\nلمن هذا الحساب · المصدر والحدود\n\nهذه اللقطات ليست لـ PhishDestroy. هذه المعلومات مصدرها صاحب حساب عادي Steam — وهو أحد المشاركين في استطلاع قصير أجراه هذا المشروع، وقد قدم الطلب بنفسه وقدم لقطات الشاشة. الحساب ملكه، والتذكرة ملكه، والمراسلات جرت بينه وبين فريق الدعم Steam. لم يقم هذا المشروع بتقديم الطلب، ولا يمتلك أي حساب على المنصة، وليس طرفًا في هذه التذكرة.\n\nفي 16 سبتمبر 2026، قدم طلبًا للوصول إلى البيانات بموجب المادة 15 من اللائحة العامة لحماية البيانات (GDPR) وقانون خصوصية المستهلك في كاليفورنيا (CCPA)، طالبًا على وجه التحديد سجلات تسجيل مفاتيح واجهة برمجة التطبيقات (API)، وسجلات تسجيل الدخول مع عناوين IP، وسجلات تفويض الأجهزة، وسجلات المعاملات. وفي 17 سبتمبر، أحاله الموظف «Logen» إلى صفحة «بيانات الحساب» الخاصة بالخدمة الذاتية. في 18 سبتمبر، أشار إلى أن الفئات المطلوبة لم تكن موجودة في تلك الصفحة وطلب إحالة الأمر إلى فريق الخصوصية أو مسؤول حماية البيانات (DPO). وفي 19 سبتمبر، أغلق الموظف «كال» التذكرة بنفس الإحالة. تم الاحتفاظ بكلتا لقطتي الشاشة أدناه (تم حجب عنوان البريد الإلكتروني لمقدم الطلب؛ SHA-256 في steam_tos_assets/screenshot-manifest.json).\n\nإنه الشخص المناسب لتقديم الطلب لسبب بسيط: يحتوي حسابه على مفتاح واجهة برمجة تطبيقات الويب (Web API) Steam لم يقم بإنشائه، وهو مسجل باسم localhost. لا يُعرف متى تم إنشاؤه — ليس بالنسبة له، ولا من أي شيء Valve قد أتاحه له، لأن السجل الوحيد الذي يمكن أن يحدد تاريخه هو سجل تسجيل مفتاح واجهة برمجة التطبيقات (API)، وهو بالضبط الفئة التي حجبها الإغلاق. والمفتاح ليس جديدًا: فهو يسبق علمه به بفترة لا يستطيع قياسها، لنفس السبب.\n\nويقدم أصحاب حسابات آخرون الطلب نفسه. وسيتم إضافة أي رد يصل إلينا هنا وفقًا للشروط نفسها التي تنطبق على هذين الطلبين — رقم التذكرة، وتاريخ التسجيل، ورمز SHA-256، مع حجب هوية مقدم الطلب — سواء تضمن الرد الفئات المطلوبة أو رفضها.\n\nلا يتخذ هذا المشروع أي موقف بشأن سبب إغلاق التذكرة. لم يُذكر أي سبب في التذكرة نفسها، ولا يُستنتج أي سبب هنا.\n\nالطلب. الرد. المقارنة.تابع السجل\nالخطوة 3 / 3\n\nوقد طلب أربع فئات محددة. صفحة «بيانات الحساب» التي أُحيل إليها هي أداة التصدير الذاتي الخاصة بـ Valve، ولا يمكن لهذا المشروع سرد محتوياتها لحساب شخص آخر — لذا لم يتم نشر مقارنة كاملة فئةً فئةً هنا. ما هو مسجل هو تصريحه الصادر في 18 سبتمبر بأن الفئات لم تكن موجودة، وقرار إغلاق الملف الصادر في 19 سبتمبر الذي كرر الإحالة دون معالجة هذه الفئات.\n\nالطلبفئات محددةمفتاح واجهة برمجة التطبيقات (API)، وتسجيلات تسجيل الدخول، وتسجيلات الأجهزة، وتسجيلات الصفقات\nالردمرجع بيانات الحسابافحص عملية استبدال الدعم\nالاختبارما الذي تم توفيره؟قارن بين كل فئة من الفئات المطلوبة\nالشاشة 1/2 — الطلب (16 سبتمبر) والرد الأول من الوكيل «لوجن» (17 سبتمبر)\nGDPR ticket HT-2YBP-F7JP-D4VB — request and first response\nالمصدر: help.steampowered.com، التذكرة رقم HT-2YBP-F7JP-D4VB · تم تسجيلها في 16–17 سبتمبر 2026 · تم حجب عنوان البريد الإلكتروني لمقدم الطلب 2026-09-21 · الملف: gdpr-ticket-1.png · SHA-256 da940c731ab9869d226e9d06ccc8a1b393738766b7b0c445a56662623e025a66 (screenshot-manifest.json).\nالشاشة 2/2 — طلب تصعيد (18 سبتمبر) وإغلاق الملف، الموظف \"كال\" (19 سبتمبر)\nGDPR ticket HT-2YBP-F7JP-D4VB — escalation request and closure\nالمصدر: help.steampowered.com، التذكرة رقم HT-2YBP-F7JP-D4VB · تم تسجيلها في 18–19 سبتمبر 2026 · الملف: gdpr-ticket-2.png · SHA-256 44844ea7b251f7fd7d79f87ee1578a846606a97b9659d3a53b322120c422219b (screenshot-manifest.json).\nالرد الختامي، 19 سبتمبر (نص حرفي):\n\"يمكنك الاطلاع على البيانات Steam المحفوظة بالفعل في صفحة \"بيانات حسابك\". ونظرًا لعدم وجود أي معلومات إضافية Steam يمكن لفريق الدعم تقديمها، سيتم إغلاق هذا الطلب.\"\nلم تُقدَّم أي بيانات · لم يُذكر أي أساس قانوني للرفض · لم تُعرض نتيجة التصعيد\nهذه الجملة خاطئة، ومحامو Valve أنفسهم هم من يثبتون ذلك. تصف الفقرة 1.9 من رسالة المحامي المؤرخة في 1 أكتوبر 2025 الارتباط على مستوى الجهاز الذي يربط جهازًا واحدًا بعشرات الحسابات (الملحق أ). وتضمنت نفس الردود 830 صفحة من السجلات المحفوظة (الملحق ب). ولا يظهر أي من هذه المعلومات في صفحة «بيانات الحساب».\nلماذا طلب هذا الحساب سجل مفتاح واجهة برمجة التطبيقات (API)؟\n\nلم يختر تلك الفئات الأربع عشوائياً. إن localhost المفتاح في حسابه هو علامة تشير إلى نص برمجي، وليست دلالة على أن شخصًا ما يقوم بكتابة نطاق حقيقي في صفحة المطور (القسم 5، القسم 6). السجل الوحيد الذي يوضح من أنشأه ومن أين هو سجل تسجيل مفتاح واجهة برمجة التطبيقات (API). وكان ذلك أول ما طلبه. وهذا ما حجبت الشركة الإفصاح عنه.\n\nالمصدر: صاحب الحساب، خلال الاستبيان الخاص بهذا المشروع. تم تشفير لقطات شاشة التذاكر الواردة أعلاه؛ ولم يتم نشر صفحة المفتاح.\n\nالتقييم · PhishDestroy\n\nإن إغلاق التذكرة مع بقاء السؤال دون إجابة ليس أمراً عارضاً هنا. بل هو النتيجة الطبيعية. ونحن نتمسك 16,319 سجلات الشكاوى وطلبات الدعم المحفوظة و 354 عملية تبادل دعم بعد إزالة التكرارات مستمدة منها. هذه التذكرة هي مثال واحد مؤرخ ومستكمل تمامًا على الشكل الذي تتخذه.\n\nتذكرة الدعم — محفوظةHT-2YBP-F7JP-D4VB\nنوع الطلبالمادة 15 من اللائحة العامة لحماية البيانات (GDPR) - طلب الوصول إلى البيانات الشخصية (DSAR)\nحالة التذكرةمغلق في 19 سبتمبر 2026 — لم تُقدَّم أي بيانات\nالوكلاء في البورصة\"لوجن\" (17 سبتمبر)، \"كال\" (19 سبتمبر)\nتم التسجيل16 سبتمبر 2026\nالبيانات المطلوبةمن الذي سجل مفتاح واجهة برمجة التطبيقات (Web API) المرتبط بهذا الحساب، ومن أي عنوان IP / جهاز / طابع زمني؟\nالأساس القانوني المذكورالمادة 15 من اللائحة العامة لحماية البيانات (GDPR) — الحق في الاطلاع على البيانات الشخصية\nالإطار القانوني:تمنح المادة 12(3) المسؤول عن معالجة البيانات مهلة شهر واحد من تاريخ الاستلام (قابلة للتمديد مع تقديم الأسباب). ولم تكن تلك المهلة قد انقضت حتى وقت النشر، ولا يشير هذا الملف إلى حدوث أي مخالفة للموعد النهائي. ويتمثل الاعتراض في جوهر الموضوع: فالرد الختامي يتضمن رابطًا إلى صفحة الخدمة الذاتية، لكنه لا يبيّن أن فئات البيانات الأربع المذكورة قد تم تقديمها، وإذا رفض المسؤول عن معالجة البيانات اتخاذ إجراء، فإن المادة 12(4) تقتضي منه بيان الأسباب وقنوات تقديم الشكاوى. ولا يرد أي منهما في الرد الختامي.\nلماذا تعتبر هذه البيانات بالتحديد مهمة؟\n\nسجل أحداث مفاتيح واجهة برمجة التطبيقات (Web API) هو السجل الذي يوضح ما إذا كان طرف ثالث قد سجل مفتاحًا باستخدام ملف تعريف ارتباط جلسة مسروق — وهي الآلية الموصوفة في شكاوى سرقة المخزون المحفوظة في أرشيف هذا الملف. إن الكشف عن هوية الشخص الذي سجل مفتاح واجهة برمجة التطبيقات (API)، وعنوان IP الذي استخدمه، والتوقيت الذي تم فيه التسجيل، من شأنه أن:\n\nاسمح للضحية بمقارنة عنوان IP المستخدم في إنشاء واجهة برمجة التطبيقات (API) بسجل عمليات تسجيل الدخول الخاصة به\nالكشف عن عناوين IP لمراكز البيانات المرتبطة ببنية تحتية معروفة تستخدم في عمليات التصيد الاحتيالي والمقامرة الآلية\nتقديم أدلة يمكن استخدامها في الدعاوى المدنية أو الجنائية ضد الفاعل\nأظهر ما إذا كان صاحب الحساب قد تلقى إشعارًا عند إنشاء المفتاح\nما يظهر من السجل: تحتفظ شركة Valve بسجلات على مستوى الجهاز وسجلات ربط الحسابات — وتصفها رسالة محاميها المؤرخة في 1 أكتوبر 2025 (انظر الملحق أ، مذكرة الأدلة — المصدر 1). في التذكرة رقم HT-2YBP-F7JP-D4VB، طلب صاحب البيانات نفس فئة السجلات، وأُغلقت التذكرة بإحالة إلى صفحة الخدمة الذاتية التي أفاد صاحب البيانات أنها لا تحتوي على تلك السجلات. أما مسألة ما إذا كان هذا الرفض قانونياً فهي من اختصاص السلطة الإشرافية؛ والنتيجة هي أن الشخص المعني بالبيانات لا يحصل عليها.\nالمراسلات — أربع رسائل، ثلاثة أيام\n\nرد اثنان من موظفي الدعم Steam مستخدمين الأسماء الأولى الواردة في التذكرة: «لوجن» في 17 سبتمبر و«كال» في 19 سبتمبر. وقد أحال كلاهما مقدم الطلب إلى صفحة «بيانات الحساب». لا يوجد في التذكرة ما يشير إلى ما إذا كان الطلب قد وصل إلى فريق الخصوصية أو مسؤول حماية البيانات التابع لـ Valve، ولا يحدد الملف هوية الموظفين أو أدوارهم أو كيفية توجيه التذكرة.\n\n16 سبتمبر\nتم تقديم طلب بموجب المادة 15 يشمل أربع فئات محددة من البيانات\n17–18 سبتمبر\nالإحالة إلى بيانات الحساب؛ يطلب مقدم الطلب رفع الأمر إلى مسؤول حماية البيانات\n19 سبتمبر\nتم إغلاق التذكرة بنفس الإحالة؛ لا توجد بيانات، ولا يوجد أساس محدد\nما الذي تمنحه المادة 15 من اللائحة العامة لحماية البيانات (GDPR) صراحةً للشخص المعني؟\nالمادة 15(1)(أ)أغراض المعالجة — لماذا تحتفظ Valve بالبيانات\nالمادة 15(1)(ب)فئات البيانات — ما الذي يحتوي عليه Valve\nالمادة 15(1)(ج)المستفيدون أو فئات المستفيدين — من تلقى البيانات (مثل: صاحب مفتاح واجهة برمجة التطبيقات)\nالمادة 15(1)(د)فترة الاحتفاظ أو معايير تحديدها\nالمادة 15(3)نسخة من البيانات الشخصية قيد المعالجة — أي سجل مفتاح واجهة برمجة التطبيقات (API) نفسه\nالمادة 12(3)يرجى الرد في غضون شهر واحد من تاريخ الاستلام؛ ويجب الإبلاغ عن أي تمديد خلال ذلك الشهر. ولم تكن المهلة قد انقضت حتى وقت النشر. المادة 12(4): وإذا لم يتخذ المسؤول عن المراقبة أي إجراء، فيجب عليه توضيح الأسباب وإبلاغ صاحب الشكوى بقنوات تقديم الشكاوى.\nمسار تقديم الشكاوى التنظيمية — لأي مستخدم\n\nيجوز لأي مستخدم قدم طلبًا بموجب المادة 15 من اللائحة العامة لحماية البيانات (GDPR) إلى Valve ولم يتلقَ ردًّا متوافقًا (أو رفضًا نموذجيًّا خالٍ من البيانات) أن يقدم شكوى إلى السلطة الإشرافية في الدولة العضو في الاتحاد الأوروبي/المنطقة الاقتصادية الأوروبية التي ينتمي إليها. إن فرع شركة Valve في الاتحاد الأوروبي هو شركة Valve GmbH في هامبورغ، لذا فإن السلطة الإشرافية الرئيسية المعنية بالشكاوى العابرة للحدود هي المفوضة المعنية بحماية البيانات وحرية المعلومات في هامبورغ (HmbBfDI). (يقع مقر ممثل المادة 27 التابع لـ (Valve) أيضًا في هامبورغ؛ ولا يُحدد عنوان الممثل بحد ذاته السلطة المختصة.) كما يجوز تقديم شكوى إلى السلطة المختصة في الدولة العضو التي ينتمي إليها مقدم الشكوى بموجب المادة 77.\n\nنموذج شكوى HmbBfDI ↗ نص اللائحة العامة لحماية البيانات (المواد 12 و15 و77) ↗ محفوظ 2026-09-20 ↗إرشادات المجلس الأوروبي لحماية البيانات (EDPB) ↗\n\nرقم مرجع التذكرة لأي شكوى: HT-2YBP-F7JP-D4VB — تم الاحتفاظ بها في هذا الملف كحالة موثقة.\n\nمثال واحد موثق\nالسجلات موجودة؛ لكن صاحب البيانات لم يتسلمها.\n\nوصف محامي Valve سجلات الترابط على مستوى الجهاز في رسالة مؤرخة في 1 أكتوبر 2025. في 19 سبتمبر 2026، أُغلق طلب بموجب المادة 15 يتعلق بنفس فئة السجلات بإحالة إلى صفحة الخدمة الذاتية التي أفاد مقدم الطلب بأنها لا تحتوي على تلك السجلات، دون ذكر أساس قانوني. ويُعد التذكرة رقم HT-2YBP-F7JP-D4VB إحدى الحالات الموثقة؛ أما ما إذا كانت تعكس ممارسة أوسع نطاقًا، فهذا سؤال يخص السلطة الإشرافية، التي يمكنها أن تطلب من Valve تقديم سجلات معالجتها.\n\nالمواد 12 و15 و77 من اللائحة العامة لحماية البيانات (GDPR) / السلطة الإشرافية\n\nيمكن تقديم شكوى بموجب المادتين 12 و15 مباشرةً إلى السلطة الإشرافية المختصة دون أي تكلفة (المادة 77). ويجوز للسلطة فرض تدابير تصحيحية، بما في ذلك إصدار أوامر بالامتثال لطلب الوصول إلى البيانات، وفرض غرامات بموجب المادة 83(5)(ب) في حالة انتهاك حقوق أصحاب البيانات. ويؤدي الاحتفاظ برقم التذكرة الأصلي وأي رد Valve (أو عدم وجوده) إلى تعزيز الشكوى.\n\nاطلع على نموذج طلب الوصول إلى البيانات الشخصية (DSAR) →\nالجزء ج — الأطر القانونية · المادة 19 · قانون العقود\nاتفاقية الاشتراك مقابل البنية الأساسية الخاصة بالمنصة\nالسياق وحدود المصدر\n\nالمؤلفون ليسوا محامين، ولا يُعد أي من هذا نصيحة قانونية. تم اقتباس قانون الضمان الاجتماعي (SSA) من الصيغة المعدلة بتاريخ 10 سبتمبر 2026؛ وقد تختلف الصياغة في صيغة معدلة أخرى، كما أن ترقيم البنود قد تغير عبر الصيغ المختلفة — لذا يجب مراجعة البند في النسخة التي كانت تسري على السلوك المعني. توضح الحجج الواردة في المادتين 25 و32 ما تتطلبه اللائحة، وليس أن سلطة إشرافية قد وجدت مخالفة. وتخضع الأرقام الواردة في الحجة 1 لحدود النطاق المنصوص عليها في القسم 13.\n\nهناك ثلاثة أحكام أساسية في اتفاقية خدمة المستخدم (SSA) تتعارض بشكل غير ملائم مع طريقة بناء المنصة: حظر الاستخدام التجاري مقابل وجود سقف سعري في «الماركت» يدفع المبيعات عالية القيمة إلى خارج المنصة؛ بند مسؤولية المستخدم عن مفاتيح واجهة برمجة التطبيقات (API) في مقابل نقطة نهاية للمفاتيح لم تكن تتطلب، قبل عام 2023، أي عامل مصادقة ثانٍ؛ ولغة الإنفاذ في مقابل سجل عام لا يُظهر أي إجراءات إنفاذ لكل مشغل على حدة. وما إذا كانت هذه التناقضات تؤثر على قابلية الإنفاذ أم لا هو مسألة تخص المحكمة؛ ويحدد هذا القسم الحقائق التي ستُعرض على المحكمة.\n\nالحجة الأولى / هيكل القيمة السوقية\nالسقف الأقصى للسوق وحظر الاستخدام التجاري\n\nيبلغ الحد الأقصى لعدد العروض في سوق المجتمع Steam حوالي $1,800. وفي خمسة أسواق، وفقًا لمعلومات محدثة (23 سبتمبر 2026)، هناك 248 فئة من منتجات CS2 التي تم تسعيرها بشكل مستقل بأسعار تتجاوز هذا الحد الأقصى في اثنين أو أكثر من هذه الأسواق؛ وهذه المنتجات لا يمكن بيعها بتلك الأسعار على منصة Valve الخاصة. يلجأ المالكون الراغبون في الحصول على تلك الأسعار إلى أسواق الجهات الخارجية، التي تعمل عبر حسابات Steam وواجهة برمجة التطبيقات Steam — ويُعتبر استخدامها من قبل إدارة الضمان الاجتماعي (SSA) نشاطًا تجاريًا ما لم يُسمح بذلك صراحةً.\n\nتتجاوز العناصر الحد الأقصى المسموح به في السوق → تسد الأسواق الخارجية هذه الفجوة → تستخدم تلك الأسواق حسابات Steam وواجهة برمجة التطبيقات Steam → تحظر SSA الاستخدام التجاري دون إذن → لم يتم نشر أي سجل للأذونات. لا تنطبق الرسوم المجمعة للسوق المجتمعي البالغة حوالي 15% إلا على المبيعات التي تتم داخل السوق، ولا تنطبق على هذه المعاملات الخارجية.\nالحجة الثانية / بنية أمان مفتاح واجهة برمجة التطبيقات (API)\nتُعد ثغرة مفتاح واجهة برمجة التطبيقات (API) مسألة تتعلق بتصميم المنصة، وليست نتيجة لإهمال المستخدم\n\nقبل عام 2023، كانت نقطة نهاية إنشاء مفتاح واجهة برمجة التطبيقات (API) لـ Steam تقبل طلب POST يحتوي على معرّف جلسة مسروق، وتقوم بإنشاء بيانات اعتماد ذات صلاحيات عالية دون تأكيد عبر البريد الإلكتروني، أو عامل تأكيد ثانٍ، أو التحقق من الجهاز. تتبع الشكاوى المتعلقة باختطاف واجهة برمجة التطبيقات (API) التي تم جمعها في هذا التحقيق نمطًا واحدًا: برنامج نصي للمهاجم، وملف تعريف ارتباط جلسة مسروق، وإنشاء مفتاح خفي، واعتراض المعاملات (يتم عرض حمولة الطلب في القسم 8).\n\nتنص المادة 25 من اللائحة العامة لحماية البيانات (GDPR) (حماية البيانات منذ مرحلة التصميم) والمادة 32 (أمن المعالجة) على اتخاذ تدابير تقنية تتناسب مع المخاطر. ويُعد إصدار بيانات اعتماد قابلة للاعتراض التجاري دون عامل ثانٍ أو إخطار المالك مسألة تتعلق بالتصميم تقع على عاتق الجهة المسؤولة عن المعالجة. أما مسألة ما إذا كان يمكن الاعتماد على بند اتفاقية خدمة الأمان (SSA) الذي يُلقي بالمسؤولية على عاتق المستخدم في ظل هذه الخلفية، فهي مسألة تُحال إلى المحكمة والسلطة الإشرافية.\n\nالحجة الثالثة / الرؤية في الوقت الفعلي\nValve يتلقى اسم مضيف المصادقة عند كل عملية تسجيل دخول\n\nيصل اسم مضيف المصادقة إلى نقطة نهاية OpenID الخاصة بـ Valve في شكل نص عادي في openid.return_to و openid.realm (يظهر شكل الطلب في القسم 3). ويُعد استخراجه عملية قياسية. اعتبارًا من 2026-09-22، كان النطاق الرئيسي مدرجًا في «مرشح الارتباط» (Link Filter) في 26 زوجًا، في حين أن المضيف الذي يحمل تسجيل الدخول Steam الخاص به لم يكن مدرجًا فيه. لم تنشر Valve أي سجلات تتعلق بالتنفيذ لكل مشغل على حدة، لذا لا يمكن تحديد ما إذا كانت أي إجراءات أخرى بخلاف «Link Filter» قد طُبقت على هذه المضيفات استنادًا إلى البيانات العامة.\n\nمن يتحمل التكلفة؟\nالنمط السائد في الشكاوى المؤرشفة\n\nفي الشكاوى التي تم استعراضها، يتبع رد فريق الدعم على ادعاءات اختطاف مفتاح واجهة برمجة التطبيقات (API) نمطًا واحدًا: رفض استعادة الحساب، والإشارة إلى مسؤولية المستخدم عن الحساب ومفتاح واجهة برمجة التطبيقات الخاص به، وإغلاق التذكرة. لم يتم تقدير أي رقم إجمالي للحسابات المتضررة أو القيمة المفقودة في هذا الملف؛ ولم يتم العثور على أي مصدر لمثل هذا الرقم.\n\nالسؤال ليس ما إذا كان المستخدمون الأفراد قد ارتكبوا أخطاء أم لا. بل السؤال هو: من المسؤول عن بنية نظام سمحت، حتى عام 2023، لطلب POST مصحوب بملف تعريف ارتباط مسروق بإنشاء بيانات اعتماد تداول ذات صلاحيات عالية دون إخطار ودون عامل تأكيد ثانٍ؟\nوثيقة SSA مقابل عقد SSA\nإن المحكمة التي تنظر في هذا الملف لن تقرأ قانون الضمان الاجتماعي (SSA) بمعزل عن السياق.\n\nوستقرأه جنبًا إلى جنب مع رسالة المحامي المؤرخة في أكتوبر 2025 التي تصف الترابط على مستوى الأجهزة، وتواريخ تسجيل مضيفي المصادقة، والطوابع الزمنية لتسجيل الدُفعات، وحمولة طلب مفتاح واجهة برمجة التطبيقات (API)، والفترة التي تبلغ عشر سنوات بين إخطارات يوليو 2016 والمنصات التي كانت لا تزال تعمل في سبتمبر 2026. وهذا هو السجل الذي سيتعين على Valve معالجته.\n\nSSA مقارنةً بالسجل / النقاط الرئيسية\n\"ممنوع الاستخدام التجاري\" — يؤدي الحد الأقصى المحدد في السوق إلى توجيه المبيعات عالية القيمة إلى أسواق تجارية تابعة لأطراف ثالثة\n\"المستخدمون مسؤولون عن مفاتيح واجهة برمجة التطبيقات\" — لن يتم تطبيق المصادقة الثنائية على نقطة نهاية المفتاح قبل عام 2023\n\"نحن نطبق الإجراءات ضد المخالفين\" — لم يتم نشر أي سجل لتنفيذ الإجراءات بحق كل مشغل على حدة منذ يوليو 2016\n\"لقد وافقت على الشروط\" — في نمط الاختراق، يتم إرسال القبول بواسطة برنامج نصي، وليس من قِبل صاحب الحساب\nالخلاصة · ما يثبته السجل وما نطلبه\nالنتائج. السجلات التي نطلبها.\nالسياق وحدود المصدر\n\nيرتبط كل استنتاج من الاستنتاجات الواردة أدناه بسجل عام مؤرخ في الأقسام أعلاه. وقد وُجِّهت الطلبات إلى السلطات التي يمكنها الحصول على الشيء الوحيد الذي لا يستطيع هذا التحقيق الوصول إليه: سجلات Valve الخاصة بالتنفيذ والوصول والمعالجة.\n\nيأتي كل طلب في أعقاب استنتاج مؤرخ. ويمكن للسلطات أن تطلب الحصول على سجلات لا يمكن لهذا التحقيق المستند إلى مصادر عامة أن يُجبر على الكشف عنها.\n\nما يثبته السجل العام\nيتم توثيق 44 منصة نشطة عبر نطاق منفصل قابل للتسجيل — 27 منها مع ملف أدلة منشور لكل مسار، و17 من خلال جمع يدوي ومدرجة بشكل منفصل. اعتبارًا من 2026-09-22، تم حظر النطاق الرئيسي لـ 26 زوجًا في مرشح الروابط Steam، في حين لم يتم حظر المضيف الذي يحمل معلومات تسجيل الدخول الخاصة بها — تم حظر csgogem.com، api.csgem.com مسجل منذ مارس 2014. Steam يتلقى اسم المضيف هذا في openid.realm و openid.return_to عند كل عملية تسجيل دخول. القسم 3\nفي 13 يوليو 2016، أعلنت Valve عن اسم الآلية وحظرتها، وحددت إخطارات محاميها المؤرخة في 20 يوليو 2016 مهلة مدتها عشرة أيام. ولم يُنشر أي سجل إنفاذ خاص بكل مشغل على حدة خلال السنوات العشر التي تلت تلك المهلة. المادة 11\nكانت نقطة نهاية مفتاح واجهة برمجة التطبيقات (Web API) Steam تصدر بيانات اعتماد ذات امتيازات عالية وقادرة على إجراء المعاملات استنادًا إلى ملف تعريف ارتباط الجلسة وحده، دون أي عامل تأكيد ثانٍ قبل عام 2023. القسم 5\nتم إغلاق طلب بموجب المادة 15 من اللائحة العامة لحماية البيانات (GDPR) (رقم التذكرة HT-2YBP-F7JP-D4VB) بعد ثلاثة أيام، مع تضمين رابط إلى خدمة المساعدة الذاتية ودون تقديم أي بيانات. المادة 18\nما نطلبه من كل سلطة\nلجنة المقامرة بولاية واشنطن\nأعد فتح ملف عام 2016. واطلب تقريرًا مفصلاً لكل مشغل على حدة يوضح الحسابات والروبوتات ومضيفي العودة التي تم تعطيلها بعد إرسال الإشعارات التي مدتها عشرة أيام، وأي المشغلين استعادوا حق الوصول لاحقًا. القسم 2\nHmbBfDI (هامبورغ؛ Valve GmbH)\nالتحقق مما إذا كان الرد بموجب المادة 15 قد استوفى واجب الجهة المسؤولة عن معالجة البيانات، والمطالبة بالإفصاح عن سجلات تسجيل مفتاح واجهة برمجة التطبيقات (API) وسجلات الوصول ذات الصلة بتحديد هوية الفاعل. المادة 18\nمنسقو الخدمات الرقمية (DSA)\nضع توجيه «auth-host» في السجل باعتباره ملاحظة، ثم قم بتقييم ما إذا كان رد Valve يفي بالتزاماته بمجرد توثيق المعلومات. المادة 16\nأي شخص معني بالبيانات\nاستخدم نموذج المادة 15 لطلب الحصول على نفس السجلات لحسابك الخاص؛ حيث يمكن للسجل المحفوظ أن يحدد من الذي بدأ عملية إعادة الضبط أو أنشأ مفتاحًا. الملحق (ز)\n\nالطلب الوحيد الكامن وراء هذه الحالات الأربع هو نفسه: نشر سجلات الإنفاذ والوصول والمعالجة التي لا يمتلكها سوى Valve. فالتحذير على الصفحة الرئيسية، والرسالة التي تمنح مهلة عشرة أيام، وصفحة الخدمة الذاتية، كلها تمثل تأكيدات على ممارسة السيطرة. أما مسألة ما إذا كانت السيطرة قد مورست أم لا، فهي سؤال لا يمكن للسجلات العامة الإجابة عليه، في حين أن الجهة التنظيمية قادرة على ذلك.\n\nالملاحق — المستندات الرئيسية ومواد العمل\nالملحق أ — المراسلات مع المحامين\nمذكرة الأدلة — المواد المقدمة من المصدر 1\n\nالأساس الاستدلالي وحالة المصادر الخاصة بالمراسلات القانونية التي استند إليها في المواد 1 و18 و19.\n\nقاعدة الأدلة وحالة المصدر — الوثائق المقدمة من المصدر 1\nالمستخدم الذي أدى حظره الدائم إلى إجراء هذا التدقيق ليس موضوعه. ولا يتم هنا النظر في ما إذا كان ذلك الحظر مبررًا أم لا، ولا يدافع هذا الملف عنه ولا يعارضه. فالحساب ليس هو بيت القصيد. ما يهم هو المحتوى: المصدر 1 — صاحب الحساب المحظور، الذي تلقى المراسلات الواردة أدناه من محامي Valve بصفته صاحب البيانات في طلبه الخاص بموجب اللائحة العامة لحماية البيانات (GDPR) — قام بإحالة تلك المراسلات وملفات القضية المرفقة، إلى جانب حق الاطلاع عليها علنًا. تم حجب الاسم؛ ويتم وصف الوثائق حسب التاريخ وبيانات التعريف الخاصة بالمنتج ورمز التجزئة.\n\nتم إرسال تلك المراسلات استجابةً لطلب مقدم بموجب اللائحة العامة لحماية البيانات (GDPR) أو طلب الوصول إلى البيانات (DSAR). وفي سياق تلك المراسلات، أدرج محامي Valve بيانًا في المحضر، موقّعًا عليه، يصف فيه إمكانيةً كان قسم الدعم Steam قد أخبر المستخدمين سابقًا أنها غير ممكنة من الناحية التقنية. والفقرة المقتبسة أدناه هي ذلك البيان.\n\nويتمثل التحليل الإضافي الذي أجراه المؤلفون للمقتطف المستخرج من السجل في تم استبعادها من هذا الملف في انتظار إجراء مراجعة مستقلة. ولا يُعتمد عليها في أي جزء آخر من هذا التحقيق.\n\nالاعتراف المسجل في السجل: القياس عن بُعد المستمر على مستوى الجهاز\n\nفي الفقرة 1.9 من الرسالة المنسوبة إلى محامي Valve، يذكر محامو Valve ما يلي: \"في الفترة ما بين عامي 2019 و2023، تم استخدام هذا الحساب بشكل أساسي من جهاز استُخدم أيضًا لتسجيل الدخول إلى عشرات الحسابات المسروقة Steam.\"\n\nالحقيقة: يصف محامي Valve هنا الارتباط على مستوى الأجهزة عبر الحسابات على مدى أربع سنوات. وقد أبلغت خدمة الدعم ضحايا السرقة بأن تتبع الأغراض المسروقة أو ربط الحسابات بالأجهزة أمر غير ممكن من الناحية التقنية. Steam Guard إن عملية تفويض الأجهزة موثقة علنًا، لذا فإن وجود سجلات لكل جهاز ليس أمرًا جديدًا في حد ذاته؛ أما الجديد فهو التأكيد الكتابي من المحامي بأن تلك السجلات يتم الاحتفاظ بها وربطها عبر الحسابات على مدى فترات تمتد لعدة سنوات.\n\nلماذا يُعد هذا الأمر مهمًا: إن الارتباط الذي يمكن أن يربط جهازًا واحدًا بعشرات الحسابات المخترقة على مدار أربع سنوات ينتمي إلى نفس فئة السجلات التي ذكرت «دعم» أنها لا تستطيع استخدامها لصالح الضحايا. ومن شأن السجلات من تلك الفئة أن تسمح بتحديد الحسابات والأجهزة في سلسلة السرقة وإعادة البيع. أما الأسئلة التي يتعين على السلطة الإشرافية الإجابة عليها فهي: ما هي السجلات الموجودة، ومدة الاحتفاظ بها، والأسس التي تستند إليها منع إطلاع أصحاب البيانات عليها.\n\nالمصدر: رسالة محامي Valve المؤرخة في 1 أكتوبر 2025، الفقرة 1.9، وملحقها بصيغة PDF المكون من 830 صفحة · الذي تلقّاه المصدر 1 استجابةً لطلب مقدم بموجب المادة 15 من اللائحة العامة لحماية البيانات (GDPR) · تم تسجيل قيمة SHA-256 للملحق في disclosure-audit.json · لم يتم نشر نص الرسالة نفسها؛ كما تم حذف أسماء الحسابات وبيانات الأطراف الثالثة.\n\nالحالة: فتح\nالمواد المصدرية متاحة عبر أرشيف الأدلة.\nالملحق ب — ملف PDF الناتج · فحص عملية حجب المعلومات\nالتعديل الذي أُجري على ملف PDF المُقدَّم هو تعديل شكلي: فالنص المُغطَّى لا يزال قابلاً للاستخراج\n\nرد محامي Valve على طلب الاطلاع بموجب اللائحة العامة لحماية البيانات (GDPR) بملحق من 830 صفحة، حيث تم تغطية الأجزاء المحجوبة بالطلاء فوق النص بدلاً من حذفها. 902,270 أحرف تقع أسفل الأشرطة السوداء وتظهر مباشرةً باستخدام أداة استخراج النص — بما في ذلك معرّفات الأطراف الثالثة التي كان الغرض من الأشرطة هو إخفاءها. ولا يُنشر هنا سوى الأرقام الإجمالية؛ ولا يتم إعادة نشر أي محتوى مشمول، كما لا يُنشر الملحق نفسه.\n\n1. ما توصلت إليه عملية فحص الهندسة\n\nالرد بموجب المادة 15 من اللائحة العامة لحماية البيانات (GDPR) المؤرخ في 1 أكتوبر 2025 وقد رافق ذلك ملحق بصيغة PDF من 830 صفحة (بيانات تعريف منتج Aspose.PDF لـ .NET، تم إنشاؤها وتعديلها في نفس التاريخ). وأجرى المؤلفون فحصًا هندسيًّا على مستوى الصفحة: ففي كل صفحة، تم تحديد المستطيلات غير الشفافة شبه السوداء التي تم رسمها بعد طبقة النص، وتم عد الأحرف القابلة للاستخراج الموجودة تحتها.\n\nتم القياس على الملف الناتج\n902,270\nلا يزال من الممكن استخراج الأحرف الموجودة أسفل الأشرطة السوداء\nأرقام محصورة، وليست تقديرية. هذا هو العدد الإجمالي للشخصيات المشمولة — وليس عدد الضحايا أو حالات إعادة تحديد الهوية أو الحوادث.\n830 / 830\nالصفحات المتأثرة — كل الصفحات\n986\nمستطيلات فوق نص قابل للاستخراج\n1,329\nإجمالي عدد المستطيلات السوداء غير الشفافة\nيتم رسم الأشرطة السوداء فوق طبقة النص؛ وهي لا تحذف النص. ويمكن استخراج النص الموجود أسفل الأشرطة باستخدام أدوات PDF القياسية. ولا يتم نشر سوى الأرقام الإجمالية؛ ولا يتم هنا إعادة نشر أي محتوى مغطى.\nعرض تجريبي جنائي: فصل الطبقات\nنموذج تراكب متجه لبرنامج ASPOSE.PDF لـ .NET (الملحق، ص. 412)\n\nتم تقديم بلاغ ضد الحساب: [تسجيل الدخول: redacted_user_667]\n\nالسبب الذي قدمه المستخدم: [نص: \"أبلغ المستخدم عن وجود عناصر مكررة في المخزون وسلوك تجاري غير لائق...\"]\n\nالخلفية: <path fill=\"#000\" />عيب: بقاء دفق UTF-8 الأساسي سليمًا\nالمصدر: الملحق بصيغة PDF المرفق برسالة المحامي المؤرخة في 1 أكتوبر 2025 (830 صفحة، بيانات تعريف المنتج من Aspose.PDF لـ .NET) · تم حساب العدد بواسطة المؤلفين، باستخدام الطريقة وعدد الصفحات في disclosure-audit.json · قيمة SHA-256 للملحق المسجل في الملف نفسه · الملحق نفسه غير منشور.\n2. لماذا يعد هذا الأمر مهمًا بالنسبة لرد صاحب البيانات\n\nأرسل محامي Valve هذا الملف إلى صاحب البيانات ردًا على طلبه الهام بالاطلاع على سجلاته الخاصة. الشرائط الموضوعة عليها هي مجرد إجراء تجميلي: فالنص الموجود تحتها لم يُحذف أبدًا، لذا فإن معرّفات الجهات الخارجية التي فُرضت عليها تلك الشرائط لإخفائها قد وصلت إلى المستلم مع الملف. إن عملية الحجب التي يمكن إزالتها باستخدام أداة استخراج النص لا تحجب أي شيء، كما أنها تجعل المستلم غير قادر على تحديد ما تم الكشف عنه وما لم يتم الكشف عنه.\n\nالمادة 15(4) هي السبب وراء وجود تلك القيود أصلاً: فلا يجوز أن يؤثر الحق في الحصول على نسخة سلباً على حقوق وحريات الآخرين. وهذا هو الالتزام الذي لم تلتزم به هذه العملية. أما ما إذا كان يمكن وصف ذلك بأنه انتهاك للبيانات الشخصية بموجب المادة 4(12)، فهذا أمر تقرره السلطة الإشرافية؛ فالكشف نفسه قابل للقياس في الملف، ويمكن لأي شخص يمتلك نفس البايتات إعادة إنتاجه — فقد نُشرت قيمة SHA-256، بينما لم يُنشر الملحق.\n\nما كان موجودًا تحت القضبان لم يكن أرقام حسابات. كانت تلك هي مجموعة تقارير المستخدمين المرفوعة ضد مقدم الطلب، مع ذكر أسماء مؤلفيها: Steam عملية تسجيل دخول، والتي — نظرًا لأن عملية تسجيل الدخول نادرًا ما تُستخدم في Steam فقط — تحدد هوية الشخص الذي يقف وراءها — وفقًا لتقديرات المؤلفين، يمكن تحديد هوية أكثر من 60% من المستخدمين المذكورين في الوثيقة بشكل كامل — إلى جانب النص الأصلي غير المحجوب لما كتبوه. ويتضمن هذا النص تمنيات بالموت وإهانات موجهة إلى جنسية مقدم الطلب. وبعض الأشخاص الذين تم تحديد هويتهم على هذا النحو هم من القاصرين. وقد سلمت الجهة المنتجة قائمة بأسماء الصحفيين إلى الشخص الذي أبلغوا عنه، وهو بالضبط الضرر الذي صيغت المادة 15(4) لمنعه.\n\nترتيب الأحرف في الملف لا يقل أهمية عن محتواه. قوبل الطلب في البداية بمطالبة بتقديم مزيد من إثباتات الهوية، بحجة أن عنوان البريد الإلكتروني المستعار الخاص بطالب المعلومات لم يتضمن اسمه؛ وتم حظر الحساب نهائيًا خلال فترة التأخير التي تلت ذلك. أما الرسالة التي سلمت البيانات أخيرًا، بعد مرور أكثر من ستة أسابيع على انتهاء المهلة المنصوص عليها في المادة 12(3)، فقد هددت المستلم بالملاحقة الجنائية وحجبت بقية بياناته الخاصة حتى يشرح نشاط حسابه للمحامي. كما يوضح الكشف عن هذه المعلومات مسألتين لم تجب عليهما Valve علنًا: تُظهر السجلات المقدمة أن ربط الحسابات يعود إلى عام 2019، بالإضافة إلى بيانات قياس عن بُعد داخلية لم يسبق لـ Valve أن وصف عمقها.\n\nنطاق هذا القسم: تقتصر الملاحظة الواردة هنا على آليات عملية التحرير، وفقًا لما تم قياسه في الملف بصيغته النهائية. أما التحليل الإضافي الذي أجراه المؤلفون للسجلات النهائية، فقد تم حجبها في انتظار إجراء مراجعة مستقلة، ولا يُعتمد عليها في أي جزء آخر من هذا الملف.\n\nالدليل: رسالة المحامي المؤرخة في 1 أكتوبر 2025 وملحقها بصيغة PDF (تم تسجيل رمز SHA-256 في ملف التدقيق)؛ قياسات ملفات PDF على مستوى الصفحة والطريقة ↗. وقد وردت بالتفصيل تسلسل الأحداث المتعلقة بالطلب، ورفض الطلب المذكور في الصفحة 8، ووصف السجلات التي تم الكشف عنها، في رواية PhishDestroy، «كلبي في مواجهة نخبة محاميي اللائحة العامة لحماية البيانات»، 17 أغسطس 2026 ↗ محفوظ 2026-08-21 ↗. تم حذف أسماء الحسابات وبيانات الأطراف الثالثة هنا؛ ولم يتم إعادة نشر أي شيء يقع ضمن نطاق الأعمدة.\n\nفي الصفحة 8 من خطاب التغطية، تم رفض جزء من الطلب، مع توضيح السبب كتابةً: لا يمكن تقديم معلومات أكثر تفصيلاً بسبب الحماية التي تحظى بها البيانات الشخصية للمستخدمين الآخرين لمنصة Steam… — لا يمكن تقديم إجابة أكثر تفصيلاً، لأنه يجب حماية البيانات الشخصية لمستخدمين آخرين Steam. وكان الملحق المكون من 830 صفحة ضمن الحزمة نفسها. ما كانت تخفيه الأشرطة السوداء لم يكن أرقام الحسابات: بل كانت البلاغات المرفوعة ضد مقدم الطلب، مع ذكر أسماء مقدميها، ومرفقة بالرسائل الأولية غير المحجوبة. كان صاحب الحساب قد طلب من Valve، من خلال محاميه، الحصول على ملفه الخاص؛ لكن ما استطاع استخلاصه منه كان ملفات أشخاص آخرين. لا يوجد في هذا الملحق ما يوضح من قام برسم المربعات. ما يثبته هو أن الحماية Valve التي تم التذرع بها كأساس لحجب المعلومات هي نفس الحماية التي فشلت هذه الوثيقة نفسها في توفيرها، في نفس المغلف، وفي نفس اليوم.\nمستندات الدعم والمراسلات القانونية\n\nالمصدر: https://phishdestroy.io/steam_dossier/ar/index#exhibit-gallery-section\n\nالملحق د — جمع المصادر\nسجلات أولية مختارة\n\nستة سجلات من الأرشيف — ثلاث مشكلات على GitHub في أنظمة التتبع الخاصة بـ Valve وثلاثة حسابات على Reddit تتعلق بنتائج دعم مثيرة للجدل. ويظل كل مصدر مرفقًا بالادعاء والنص المحفوظ والسؤال الذي يثيره.\n\n1 / 6 السجلات المحددة\nاختر سجلًا مصدرًا\nGH-01 / GITHUBفتح في الإصدار المحفوظ\nمفاتيح الأجهزة، التي طُلبت في عام 2016\n\nValveSoftware / steam-for-linux · #4521 · 2016-06-27\n\nطلب أحد المستخدمين من Valve دعم مفاتيح U2F المادية كعامل ثانٍ بديل. وتحمل المشكلة المحفوظة كل من علامتي «طلب ميزة» و«تمت المراجعة»، مع تسجيل حالتها على أنها «مفتوحة».\n\nأطلب توفير دعم جهاز U2F USB كبديل في منصة Steam.\n\nمقتطف من المشكلة المطروحة على GitHub ↗\nسجل موثق\nطلب مؤرخ للحصول على إجراء حماية إضافي للحساب، نُشر في نظام تتبع المشكلات الخاص بـ Valve وحُددت حالته بـ «تمت مراجعته».\nالمطالبة بالمساءلة\nنشر قرار المنتج وتاريخ الرد والحماية الممنوحة بعد المراجعة.\nقراءة السجل المحفوظ →افتح GitHub ↗\nفي الملف: إجراءات حماية الحساب →الأرشيف رقم 484 · الإصدار 2026-09-17\nGH-02 / GITHUBفتح في الإصدار المحفوظ\nتقارير الأعطال التي لا تتضمن خيارًا فعّالًا لرفض الاشتراك\n\nValveSoftware / steam-for-linux · #6459 · 2019-08-18\n\nيصف المبلغ مشكلة في عميل Steam بتاريخ 12 أغسطس 2019 على نظام أوبونتو 16. ويذكر أن تعطيل وجهة التحميل التلقائي عند التعطل لم يستمر بعد إعادة التشغيل، وقد أرفق التكوين ذي الصلة.\n\nإذا قمت بتعطيل `ServerURL`، فإنه يتم استبداله بعد كل عملية إعادة تشغيل.\n\nمقتطف من المشكلة على GitHub ↗ محفوظ 2026-04-19 ↗\nسجل موثق\nشكوى محددة تتعلق بالخصوصية تتضمن تاريخ العميل ونظام التشغيل ومقتطفًا من الإعدادات. المشكلة المحفوظة لا تزال مفتوحة.\nالمطالبة بالمساءلة\nحدد التحقيق، والإصدارات المتأثرة، والتغيير الذي أدى إلى تفعيل خيار الانسحاب.\nقراءة السجل المحفوظ →افتح GitHub ↗محفوظ 2026-04-19 ↗\nفي الملف: طلب السجلات ذات الصلة →الأرشيف رقم 467 · الإصدار 2026-09-17\nGH-03 / GITHUBفتح في النسخة المحفوظة\nتم الإبلاغ عن إساءة استخدام تذكرة المصادقة إلى Valve\n\nValveSoftware / Source-1-Games · #3857 · 2022-02-26\n\nيدعي المؤلف أن إدارة الخادم احتفظت بـ Steam تذاكر مصادقة بعد انقطاع اتصال اللاعبين، واستخدمت قوائم خادم مضللة. ويطالب المنشور Valve بالتعامل مع هذا السلوك.\n\nلجعل خوادمهم تبدو مزدحمة.\n\nمقتطف من مشكلة GitHub ↗\nسجل موثق\nتم تقديم تقرير عام عن إساءة الاستخدام عبر أداة التتبع الخاصة بـ Valve في 26 فبراير 2022. وحالته المحفوظة هي «مفتوح»؛ ويتضمن التقرير روابط إلى لقطات شاشة.\nالمطالبة بالمساءلة\nتقديم نتائج التحقيق وسجل الإجراءات التصحيحية المتعلقة بحالة إساءة استخدام تذكرة المصادقة التي تم الإبلاغ عنها.\nقراءة السجل المحفوظ →افتح GitHub ↗\nفي الملف: نطاق مجموعة البيانات →الأرشيف رقم 768 · الإصدار 2026-09-17\nRD-01 / REDDITسيرة المؤلف\n44 عملية شراء متنازع عليها في السوق\n\nr/DotA2 · لم يُكشف عن اسم المستخدم · 2022-07-07\n\nأفاد المؤلف بوقوع 44 عملية شراء غير مصرح بها على منصة «ماركت» في 6 يوليو 2022، وخسائر بلغت حوالي $500+. ويشير إلى أن المصادقة الثنائية كانت مفعَّلة، ويصف الردود النمطية المتكررة التي تلقاها من فريق الدعم.\n\nهذه هي المذكرة الثانية التي أرسلتها، وما زلت لم أتلقَ ردًا من Steam لا يكون مجرد نسخ ولصق لنموذج آلي.\n\nمقتطف من المنشور على موقع Reddit ↗ محفوظ 2025-03-20 ↗\nسجل موثق\nتقرير مؤرخ عن عمليات شراء متنازع عليها، يتضمن روابط إلى لقطات شاشة للمعاملات ورداً من فريق الدعم. المبالغ والأحداث الواردة في التقرير هي وفقاً لما ذكره المؤلف.\nالمطالبة بالمساءلة\nقم بمطابقة عمليات الشراء المتنازع عليها مع سجلات المعاملات والجلسات. اشرح الأسباب التي استند إليها فريق الدعم في اتخاذ قراره.\nقراءة السجل المحفوظ →افتح Reddit ↗محفوظ 2025-03-20 ↗\nفي الملف: الدعم والإنفاذ →الأرشيف رقم #4,533 · الإصدار 2026-09-17\nRD-02 / ريديتسيرة المؤلف\nحظر دائم وإغلاق باب الاستئناف\n\nr/ohnePixel · لم يُكشف عن اسم المستخدم · 2024-12-09\n\nيعترض المؤلف على الحظر الدائم، ويقول إن الدعم استند إلى شكوى بشأن تحويل مشبوه للحساب وإبلاغات من أعضاء المجتمع. ويذكر المؤلف التذاكر التي تم إغلاقها وخططه لطلب بياناته الشخصية.\n\nشرحت لهم موقفي وطلبت مزيدًا من التفاصيل، لكنهم مصممون على قرارهم ويقومون بإغلاق التذاكر الخاصة بي.\n\nمقتطف من المنشور على موقع Reddit ↗\nسجل موثق\nحساب طلب دعم محفوظ، يتضمن الأسباب التي يذكرها المؤلف لدعم الطلب، بالإضافة إلى روابط لأربع صور. ويُستمد تاريخ النشر من ملف التصدير المحدد الخاص بالطلب.\nالمطالبة بالمساءلة\nحدد الأدلة التي تدعم الحظر الدائم، وإجراءات المراجعة المتاحة للطعن فيه. إن إغلاق ملف الاستئناف لا يشكل تبريرًا للقرار.\nقراءة السجل المحفوظ →افتح Reddit ↗\nفي الملف: طلب السجلات ذات الصلة →الأرشيف رقم #4,766 · الإصدار 2026-09-17\nRD-03 / ريديتسيرة المؤلف\nإعادة تعيين عملية الاسترداد وخسارة مُبلغ عنها بقيمة $10,000\n\nr/legaladvice · تم حجب اسم المستخدم · 2025-05-09\n\nيدعي المؤلف أن فريق الدعم أعاد تعيين بيانات اعتماد الحساب وأوقف إجراءات حماية الحساب بعد أن قدم شخص آخر طلب استعادة. ويشير إلى خسارة مبلغ يقدر بحوالي 0 دولار أمريكي من حساب غير نشط.\n\nSteam قام فريق الدعم بإعادة تعيين كلمة المرور الخاصة بي وأوقف جميع إجراءات الأمان الخاصة بحسابي.\n\nمقتطف من المنشور على موقع Reddit ↗\nسجل موثق\nادعاء محفوظ بشأن تجاوز عملية الاسترداد لإجراءات حماية الحساب. تسجل المشاركة المحفوظة ما قاله كاتبها إن فريق الدعم أبلغه به.\nالمطالبة بالمساءلة\nحدد هوية الشخص الذي أذن بإعادة الضبط، وأدلة الملكية التي تم قبولها، وسجل الوصول. تُعد استعادة الحساب جزءًا من ضوابط نظام الأمان Valve.\nقراءة السجل المحفوظ →افتح Reddit ↗\nفي الملف: طلب السجلات ذات الصلة →الأرشيف رقم #4,592 · الإصدار 2026-09-17\n\nستة سجلات مختارة. تصف أوصاف GitHub عملية البناء المحفوظة. وتحفظ منشورات Reddit روايات المؤلفين.\n\nقم بتنزيل الألبومات الستة ↓\n\nتتضمن النسخة القابلة للبحث ما يلي: 16,319 سجلات منفصلة: 393 سجلاً على Trustpilot، و5,635 سجلاً على Reddit، و2,395 سجلاً على GitHub، و276 سجلاً على مواقع الويب، و7,620 سجلاً على الويكي. قد تتعلق عدة سجلات بنفس الحدث. أما ملف التصدير الرئيسي المنفصل المكون من 40,448 أسطر، فيتميز بنطاق مختلف.\n\nالبحث في الأرشيف الكامل ↗ · إنشاء ملف البيان ↗ · نطاق مجموعة البيانات وأعدادها →\n\nالملحق (هـ) — دراسة حالة\nArchiSteamFarm وبند الأتمتة\n\nأداة مفتوحة المصدر لجمع نقاط البطاقات، تذكر في قسم «الأسئلة الشائعة» الخاص بها أنها تعمل على ملايين الحسابات، وهو ما يتعارض مع بند اتفاقية الاشتراك (§ 4.C) الذي يحظر استخدام الأتمتة. الآليات — ما يتعين على مزرعة البطاقات شراؤه من Valve قبل أن تتمكن من إنتاج أي شيء، ولماذا تشكل كل طريقة لسحب الأموال من البطاقة انتهاكًا للترخيص، وسجل الإنفاذ، ومن يتولى الإشراف على اقتصاد البطاقات — موضحة بالكامل في الملحق الخامس ↗.\n\nتنص المادة 4.C من اتفاقية الاشتراك Steam على ما يلي:\n\n\"لا يجوز لك استخدام أي شكل من أشكال البرامج النصية أو الروبوتات أو الماكرو أو أي أنظمة أخرى لا يتحكم فيها الإنسان (يُشار إليها فيما يلي بـ «الأتمتة») للتفاعل مع المحتوى والخدمات على Steam بأي شكل من الأشكال.\" — Steam اتفاقية الاشتراك، المادة 4.ج (الحالية) ↗ محفوظ 2026-09-18 ↗\n\nValve يطبق هذا البند. وهو بارع جدًّا في ذلك. الأسئلة الشائعة حول ArchiSteamFarm (ASF) — أداة مفتوحة المصدر تصفها وثائقها بأنها تعمل على أكثر من بضعة ملايين من الحسابات Steam منذ الإصدار الأول قبل أكثر من 11 عامًا — يعيد عرض ثلاث رسائل من فريق الدعم Steam التي فرضت حظرًا دائمًا على المستخدمين الذين أداروا شبكات روبوتات. Valve اكتشف هذه الشبكات، وسمّاها، وقام بإيقافها. ولذلك، فإن السؤال المهم هنا ليس ما إذا كان Valve قادرًا على كشف الأنشطة الآلية على نطاق واسع.\n\nالمسؤول عن المشروع ArchiSteamFarm الأسئلة الشائعة يتناول خطر فرض الحظر بشكل مباشر:\n\n\"هذا أمر مستبعد للغاية بالنظر إلى أن ASF تُستخدم في أكثر من بضعة ملايين من حسابات Steam، منذ إصدارها الأول الذي حدث قبل أكثر من 11 عامًا — لكنه يظل احتمالاً واردًا، بغض النظر عن احتمالية حدوثه الفعلية.\"\n\n\"Valve يعترف بوضوح بوجود 'Steam المتسكعين'، كما هو مذكور هنا، لذا إذا سألتني، فأنا متأكد تمامًا من أنه لو لم يكونوا راضين عن وجودهم، لكانوا قد اتخذوا إجراءً ما بالفعل بدلاً من الإشارة إلى أنهم قد يتسببون في مشاكل من ناحية VAC. الكلمة المفتاحية هنا هي «ألعاب التسكع» (idlers)، مثل ASF، وليس «ألعاب التسكع» (game idlers).\"\n\n— ArchiSteamFarm الأسئلة الشائعة، JustArchiNET. المصدر: ويكي GitHub ↗ · تم التحقق من نصه حرفياً 2026-09-22\n\nوترد نفس الأسئلة الشائعة على السؤال «هل تم حظر أي شخص بسبب ذلك؟» بقولها: نعم، ويورد ما كتبه Steam Support إلى ثلاثة منهم:\n\n1,000+ روبوتات · تم حظر التداول\n\"يبدو أن هذا الحساب قد استُخدم لإدارة شبكة من حسابات الروبوتات. ويُعد استخدام الروبوتات انتهاكًا لاتفاقية المشترك Steam.\"\n\nأكثر من 170 روبوتًا · تم حظرهم نهائيًا، تخفيضات شتاء 2017\n\"تم استخدام هذا الحساب لجمع بطاقات قابلة للتداول بشكل غير قانوني على Steam، بالإضافة إلى أنشطة أخرى ذات صلة، وليس فقط الأنشطة التجارية. وقد تم حظر الحساب بشكل دائم، ولا يمكن لفريق الدعم Steam تقديم أي دعم إضافي بخصوص هذه المسألة.\"\n\nأكثر من 120 روبوتًا · تم حظرهم نهائيًا\n\"تم استخدام هذا الحساب وحسابات أخرى لإغراق البنية التحتية لشبكتنا، وهو ما يشكل انتهاكًا لقواعد السلوك عبر الإنترنت Steam.\"\n\n— Steam رسائل الدعم المنشورة في قسم الأسئلة الشائعة ArchiSteamFarm، تحت عنوان «هل تم حظر أي شخص بسبب ذلك؟». المصدر ↗ · تم التحقق من صحة النص حرفياً 2026-09-22\n\nضع السجلين جنبًا إلى جنب. تم تحديد مستخدم خاص يمتلك 1,000 روبوتات تجميع النقاط، وأُبلغ بأن «استخدام الروبوتات يُعد انتهاكًا لاتفاقية المشترك Steam»، وتم حذفه نهائيًّا. أما المنصات التجارية الواردة في هذا الملف، فتدير حسابات آلية Steam كنشاط أساسي لها، على نطاق أوسع بكثير، وتقوم بالمصادقة من خلال OpenID الخاص بـ Valve عند كل عملية تسجيل دخول — ولم يتم نشر أي سجل إنفاذ لكل مشغل على حدة بالنسبة لأي منها. هذه الفقرة صالحة. والسؤال هو: إلى من تستهدف؟\n\nلا تُوجه إلى ASF أي تهمة هنا، وتفسيرها لموقف Valve هو تفسيرها الخاص — حيث يذكر مؤلفه بوضوح أن «ASF غير مخولة من قبل Valve». تُستخدم الأداة هنا كأداة قياس: فهي تُظهر أن Valve تكشف شبكات الروبوتات، وتسميها كتابةً، وتحظرها بشكل دائم. ويمكن لـ Valve أن ينهي الجدل بجملة واحدة من خلال نشر قائمة بالأتمتة التجارية التي يصرح بها، والسجل الخاص بكل مشغل حول الإجراءات التي اتخذها تجاه البقية.\n\nأين يؤثر «تجميع البطاقات» على إيرادات Valve\n\nتُباع بطاقات التداول المُنتجة في سوق المجتمع Steam، الذي يفرض رسومًا إجمالية تبلغ حوالي 15% على كل عملية بيع تتم داخل السوق؛ يجب أن يكون الحساب قد أنفق $5.00 دولار أمريكي على Steam قبل أن يتمكن من الحصول على أي بطاقة على الإطلاق؛ كما تتطلب الحصول على البطاقات امتلاك اللعبة أو إجراء مشتريات داخل اللعبة. لم يتم تقدير أي رقم إجمالي للإيرادات هنا — حيث يتم ذكر حجم التشغيل فقط كما هو موضح في الأسئلة الشائعة الخاصة بـ ASF. كما تسجل الأسئلة الشائعة Valve من السمات المميزة \"Steam العاطلون\" (تجميع البطاقات) من \"المتسكعون في الألعاب\"؛ انظر الأسئلة الشائعة حول ASF ↗. وترد التفاصيل الكاملة لهذه الآليات في الملحق الخامس — المقياس و فخ الاستخدام التجاري.\n\nالموضوعArchiSteamFarm — تجميع البطاقات آليًّا\nالمقياس المحددملايين الحسابات (وفقًا للأسئلة الشائعة الخاصة بـ ASF — لم يتم التحقق من العدد الدقيق للحسابات النشطة)\nمحسوبة، وليست مقتبسة10,880,610 إجمالي عدد إدخالات واجهة برمجة التطبيقات (API) في المجموعة Steam الخاصة بـ ASF (5,360,499 غير محدودة، كما يوضح Steam) — إن كلمة «الملايين» الواردة في الأسئلة الشائعة ليست قصة، بل هي إحصاء للأعداد. 88.97% لا تنطوي على Steam أي نوع من الحظر. إحصاء الحظر الكامل ↗\nالمعلومات الواردة في الوثائق الخاصة بالأداة\nيقوم برنامج ASF بتسجيل الدخول إلى الحسابات في وضع «headless» ويبقي الألعاب في وضع الخمول لانتظار ظهور البطاقات دون تشغيل عميل Steam (وفقًا لوثائق المشروع).\nتشير «الأسئلة الشائعة» إلى أن «Valve» على علم بوجود «Steam» من المتسكعين، وأنه «لو لم يكونوا راضين عنهم، لكانوا قد اتخذوا إجراءً ما بالفعل».\nلم يتم الإبلاغ عن أي إجراءات إنفاذ موجهة منذ أكثر من 11 عامًا (وفقًا للأسئلة الشائعة)؛ وتبلغ الرسوم الإجمالية لمبيعات البطاقات الناتجة داخل «Community Market» حوالي 15% وفقًا لـ Steam.\nتنص «الأسئلة الشائعة» على حد أقصى موصى به يبلغ عشرة حسابات لكل مشغل، وتُعزى هذه التوصية إلى Valve: «تستند هذه التوصية إلى إرشادات داخلية Valve، بالإضافة إلى اقتراحاتنا الخاصة.» ولم تنشر Valve أي إرشادات من هذا القبيل.\nالحد الأقصى التقني، وفقًا لنفس الأسئلة الشائعة: «يمكنك تشغيل ما يصل إلى 100-200 روبوت باستخدام عنوان IP واحد ومثيل واحد من ASF.»\nيتم تسجيل وقت اللعب المزيف بواسطة Valve — «يتم تحديثه عادةً كل 30 دقيقة تقريبًا» — وتُدرج الفقرة § 4.C «تزوير إحصائيات اللعب (مثل تضخيم عدد الانتصارات أو الهزائم، أو نقاط الخبرة، أو وقت اللعب)» ضمن الأفعال المحظورة.\nالمصادر\nويكي الأسئلة الشائعة الرسمي لـ JustArchi ASF ↗ ArchiSteamFarm مستودع ↗ محفوظ 2026-09-24 ↗\nبند الأتمتة واضح وصريح؛ فقد ذكرت الأسئلة الشائعة الخاصة بـ ASF منذ سنوات أن الأداة تعمل على ملايين الحسابات؛ ولم يتم الإبلاغ عن أي إجراءات إنفاذ موجهة ضدها. والفجوة بين القاعدة وتطبيقها هي ما يظهر في السجلات؛ ولم يتم تحديد سببها هنا.\nالمعرض الكاملاقتصاد البطاقات: العملية، والنطاق، والترخيص، والجهة التي تشرف عليه ↗ما الذي يتعين على المزرعة شراؤه من Valve قبل أن تتمكن من إنتاج بطاقة واحدة؛ السطران من الفقرة § 4.C اللذان يصفان زراعة البطاقات من خلال آثارها؛ لماذا كل طريقة لصرف قيمة البطاقة تشكل خرقًا للترخيص الذي كتبه Valve بينما يفرض Valve رسومًا عند المدخل؛ سجل الإنفاذ بما في ذلك موجة VAC في يونيو 2025 وحظر السلسلة عن طريق رقم الهاتف المشترك؛ والموظف Valve ومشرفو المجتمع الذين تم العثور عليهم وهم يديرون خدمات تداول البطاقات وقوائم الحظر حول Steam.إحصاء الحظرلم نسأل Valve عن مساحة المزرعة. بل قمنا بحسابها. ↗10,880,610 إجمالي الحسابات (المحدودة وغير المحدودة) التي تمت قراءتها من مجموعة Steam الخاصة بـ ArchiSteamFarm، والتي ينضم إليها البرنامج تلقائيًّا بشكل افتراضي عند التشغيل الأول ما لم يقم المستخدم بإلغاء تحديد إعداد الانضمام إلى المجموعة (بما يشمل كلاً من مزارع الروبوتات التجارية واللاعبين العاديين الذين تركوا الإعداد الافتراضي كما هو). 88.97% لا يخضعون لأي نوع من حظر Steam؛ ومن بين الـ 11% الذين يخضعون للحظر، فإن 99.8% منها عبارة عن حظر تجميلي من المجتمع لا يمنع التداول أبدًا. بعد المقارنة مع SteamRep، يتضح أن 67.77% من المحتالين المدرجين في القائمة يظلون أحرارًا بمجرد رفع الحظر المفروض بموجب نظام مكافحة الغش. مع تحليلات حسب تاريخ التسجيل والموقع الجغرافي ومدة البقاء — الحجم الحقيقي، مقاسًا وليس مجرد سرد.\n\nAppendix F — Working ledger\n\nRules ledger: clauses against recorded platforms\n\nاختر قاعدةً ما؛ حيث يعرض السجل المنصات المسجلة والمصنفة تحتها، مع ذكر نطاقها الرئيسي، ومضيف المصادقة المُعلن، ونتيجة «تصفية الروابط» المحفوظة. موقع ويب محظور، أو نطاق آخر لتسجيل الدخول: اتبع القاعدة حتى تصل إلى المسار المتبقي.\n\n175السجلات المرتبطة\nبشأن هذه القاعدة\n174 المجالات الأساسية0 الإشارات إلى C&D\nمقتطف من اللائحة / المادة 2.G من قانون الضمان الاجتماعي (SSA)\nالاستخدام التجاري وفرض الرسوم على الحساب\n“…exploit the Content and Services or any of its parts for any commercial purpose, except as expressly permitted elsewhere in this Agreement (including any Subscription Terms or Rules of Use).”\nتابعوا الأرقام القياسية\nسجل المنصة 175\nالأرقام الموضحة بالمقياس هي تقديرات مستمدة من المصادر\n\n175 من سجلات «175»\n\nالخدمة / المجموعة الأم\tالنطاق الرئيسي / السجل\tنطاق المصادقة الملحوظ / العمر\tالمقياس / الاستجابة المسجلة\n\nCasino\n\tcsgoempire.com\n11.3 yearsRegistered 2015-06-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgoempirelogin4.com\n6.2 yearsRegistered 2020-07-20\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustreaper.com\n23.2 yearsRegistered 2003-06-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustreaper.com\n23.2 yearsRegistered 2003-06-24\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustly.com\n12.4 yearsRegistered 2014-05-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustly.com\n12.4 yearsRegistered 2014-05-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette Casino\n\tcsgofast.com\n11.5 yearsRegistered 2015-03-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsteam-login.authtofast.com\n83 daysRegistered 2026-06-30\nRDAP ↗ · authtofast.com (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tduelbits.com\n6.6 yearsRegistered 2020-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nswitchflips.com\n6.4 yearsRegistered 2020-04-21\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opener\n\tfarmskins.com\n10.5 yearsRegistered 2016-03-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsteam.kobal.cc\n9.7 yearsRegistered 2017-01-07\nRDAP ↗ · kobal.cc (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgoluck.com\n9.3 yearsRegistered 2017-05-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgoluck.com\n9.3 yearsRegistered 2017-05-18\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tinsane.gg\n7.5 yearsRegistered 2019-04-02\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.insane.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcs2skin.com\n3.5 yearsRegistered 2023-03-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncs2skin.com\n3.5 yearsRegistered 2023-03-06\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tjuice.gg\n7.9 yearsRegistered 2018-10-19\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nletmeinjuice.com\n2.4 yearsRegistered 2024-04-15\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tggdrop.com\n8.6 yearsRegistered 2018-02-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nggauth.com\n3.4 yearsRegistered 2023-05-03\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Casino\n\thowl.gg\n9.5 yearsRegistered 2017-03-16\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhowl.uno\n41 daysRegistered 2026-08-11\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tchicken.gg\n5.7 yearsRegistered 2021-01-11\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nchicken.gg\n5.7 yearsRegistered 2021-01-11\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgocasino.gg\n2.6 yearsRegistered 2024-02-17\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.csgocasino.gg\n2.6 yearsRegistered 2024-02-17\nWHOISFREAKS ↗ · csgocasino.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Casino\n\thunt.gg\n6.9 yearsRegistered 2019-11-04\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.hunt.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Battles\n\tcsbattle.com\n9.8 yearsRegistered 2016-12-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsbattle.com\n9.8 yearsRegistered 2016-12-10\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskinrave.gg\n3.1 yearsRegistered 2023-08-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinrave.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsdouble.gg\n261 daysRegistered 2026-01-03\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsdouble.gg\n261 daysRegistered 2026-01-03\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustchance.com\n8.0 yearsRegistered 2018-10-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhgfuihd.com\n7.6 yearsRegistered 2019-01-27\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Automation\n\tcobaltlab.tech\n3.5 yearsRegistered 2023-03-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncobaltauth.com\n1.7 yearsRegistered 2025-01-07\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\traided.gg\n171 daysRegistered 2026-04-03\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.raided.gg\n171 daysRegistered 2026-04-03\nIP2WHOIS ↗ · raided.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustneo.gg\n1.3 yearsRegistered 2025-06-20\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustneo.gg\n1.3 yearsRegistered 2025-06-20\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tsplits.gg\n3.7 yearsRegistered 2023-01-23\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsplits.gg\n3.7 yearsRegistered 2023-01-23\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Upgrader\n\tupgrader.pro\n1.2 yearsRegistered 2025-07-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nupgauth.space\n38 daysRegistered 2026-08-14\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskin.fans\n8.2 yearsRegistered 2018-07-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skinfans.com\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\thotpizza.one\n1.8 yearsRegistered 2024-12-07\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhotpizza.one\n1.8 yearsRegistered 2024-12-07\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tg4skins.com\n10.1 yearsRegistered 2016-08-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.g4s.to\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2royal.com\n4.1 yearsRegistered 2022-08-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ntf2auth.com\n5.2 yearsRegistered 2021-07-27\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2hunt.com\n8.7 yearsRegistered 2018-01-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrstspcl.com\n6.1 yearsRegistered 2020-08-08\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2.bet/coinflip\n8.4 yearsRegistered 2018-05-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ntf2.bet\n8.4 yearsRegistered 2018-05-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\topenstars.gg\n131 daysRegistered 2026-05-13\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nopenstars.gg\n131 daysRegistered 2026-05-13\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tskins.com\n25.1 yearsRegistered 2001-08-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skins.com\n25.1 yearsRegistered 2001-08-08\nRDAP ↗ · skins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\twhite.market\n9.6 yearsRegistered 2017-03-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwhite.market\n9.6 yearsRegistered 2017-03-01\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tmoon.market\n7.6 yearsRegistered 2019-02-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmoon.market\n7.6 yearsRegistered 2019-02-27\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tcsfloat.com\n5.2 yearsRegistered 2021-07-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgofloat.com\n11.0 yearsRegistered 2015-09-29\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tskin.land\n4.7 yearsRegistered 2022-01-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skin.land\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\thaloskins.com\n2.8 yearsRegistered 2023-12-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhaloskins.com\n2.8 yearsRegistered 2023-12-10\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCorporate Market\n\tbuff.163.com\n29.0 yearsRegistered 1997-09-15\nRDAP ↗ · 163.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\nbuff.163.com\n29.0 yearsRegistered 1997-09-15\nRDAP ↗ · 163.com (parent)\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\tmarket.csgo.com\n26.6 yearsRegistered 2000-02-07\nRDAP ↗ · csgo.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\ndota2.net\n14.9 yearsRegistered 2011-10-29\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRegulated Market\n\tskinport.com\n8.0 yearsRegistered 2018-09-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinport.app\n6.3 yearsRegistered 2020-06-20\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMarketplace/Swap\n\tskinflow.gg\n3.8 yearsRegistered 2022-11-26\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinflow.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tskin.place\n6.0 yearsRegistered 2020-09-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skin.place\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tskinsmonkey.com\n5.7 yearsRegistered 2021-01-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinsmonkey.com\n5.7 yearsRegistered 2021-01-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCorporate Market\n\tskinbaron.de\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinbaron.com\n10.7 yearsRegistered 2015-12-22\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Market\n\trust.tm\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\ndota2.net\n14.9 yearsRegistered 2011-10-29\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tpirateswap.com\n6.0 yearsRegistered 2020-09-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nlogin.pirateswap.com\n6.0 yearsRegistered 2020-09-22\nRDAP ↗ · pirateswap.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Marketplace\n\tmannco.store\n8.6 yearsRegistered 2018-03-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmannco.store\n8.6 yearsRegistered 2018-03-02\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tskinswap.com\n9.9 yearsRegistered 2016-11-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinswap.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\texeskins.com\n2.1 yearsRegistered 2024-08-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nexeskins.com\n2.1 yearsRegistered 2024-08-14\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tbalticskins.com\n153 daysRegistered 2026-04-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nbalticskins.com\n153 daysRegistered 2026-04-21\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tcs.trade\n8.9 yearsRegistered 2017-11-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncs.trade\n8.9 yearsRegistered 2017-11-14\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\trapidskins.com\n4.5 yearsRegistered 2022-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.rapidskins.com\n4.5 yearsRegistered 2022-03-11\nRDAP ↗ · rapidskins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\ttradeit.gg\n9.1 yearsRegistered 2017-08-21\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nconnect-tradeit.com\n4.6 yearsRegistered 2022-02-23\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\t49skins.com\n3.4 yearsRegistered 2023-04-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.49skins.com\n3.4 yearsRegistered 2023-04-19\nRDAP ↗ · 49skins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tskinvault.gg\n3.4 yearsRegistered 2023-05-06\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinvault.gg\n3.4 yearsRegistered 2023-05-06\nIP2WHOIS ↗ · skinvault.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Trading\n\taim.market\n3.3 yearsRegistered 2023-05-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\naim.market\n3.3 yearsRegistered 2023-05-22\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Sell Portal\n\tskinout.gg\n5.6 yearsRegistered 2021-02-27\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skinout.gg\n5.6 yearsRegistered 2021-02-27\nIP2WHOIS ↗ · skinout.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Trading\n\tntskins.com\n230 daysRegistered 2026-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nntskins.com\n230 daysRegistered 2026-02-03\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Portal\n\tgamerpay.gg\n6.0 yearsRegistered 2020-10-02\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ngamerpay.gg\n6.0 yearsRegistered 2020-10-02\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Scrap Swap\n\tscrap.tf\n14.0 yearsRegistered 2012-09-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nscrap.tf\n14.0 yearsRegistered 2012-09-03\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Cashout\n\tmarketplace.tf\n14.0 yearsRegistered 2012-09-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmarketplace.tf\n14.0 yearsRegistered 2012-09-19\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Cashout\n\tskins.cash\n10.5 yearsRegistered 2016-03-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinscash.live\n6.8 yearsRegistered 2019-12-05\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgo.net\n14.2 yearsRegistered 2012-07-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncn2.easylot.net\n10.0 yearsRegistered 2016-09-03\nRDAP ↗ · easylot.net (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCommunity Hub\n\tcybershoke.net\n6.8 yearsRegistered 2019-11-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.cybershoke.net\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMatchmaker Hub\n\tfastcup.net\n14.6 yearsRegistered 2012-02-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.fastcup.net\n14.6 yearsRegistered 2012-02-16\nRDAP ↗ · fastcup.net (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Analytics\n\tleetify.com\n7.6 yearsRegistered 2019-03-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nleetify.com\n7.6 yearsRegistered 2019-03-01\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Analytics\n\tscope.gg\n7.8 yearsRegistered 2018-12-10\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nscope.gg\n7.8 yearsRegistered 2018-12-10\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tools\n\ttradeupspy.com\n6.5 yearsRegistered 2020-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.tradeupspy.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMarketplace\n\tcs.deals\n9.8 yearsRegistered 2016-12-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.cs.deals\n9.8 yearsRegistered 2016-12-03\nRDAP ↗ · cs.deals (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Price DB\n\tpricempire.com\n6.6 yearsRegistered 2020-01-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\npricempire.com\n6.6 yearsRegistered 2020-01-30\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Blackmarket\n\tFSB Market\n7.2 yearsRegistered 2019-07-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nFSB Market\n7.2 yearsRegistered 2019-07-27\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nReady-Account Hub\n\tz2u.com\n26.9 yearsRegistered 1999-11-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwww.z2u.com\n26.9 yearsRegistered 1999-11-10\nRDAP ↗ · z2u.com (parent)\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Gambling\n\tcsgoroll.com\n11.6 yearsRegistered 2015-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwww.csgoroll.com\nRegistry date unavailableRegistry date unavailable\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\trollbit.com\n11.9 yearsRegistered 2014-11-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrbsnin.com\n3 daysRegistered 2026-09-18\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nLicenced Casino\n\t500.casino\n5.9 yearsRegistered 2020-11-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette/Slots\n\tcsgobig.com\n11.4 yearsRegistered 2015-04-12\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcasedrop.com\n14.8 yearsRegistered 2011-12-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\tbanditcamp.com\n12.2 yearsRegistered 2014-06-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tskinbox.com\n18.8 yearsRegistered 2007-12-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\ttastydrop.com\n6.1 yearsRegistered 2020-08-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette Casino\n\tcsgopolygon.gg\n6.5 yearsRegistered 2020-03-28\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tmagicdrop.ru\n10.3 yearsRegistered 2016-05-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nDice Casino\n\tcsdice.com\n3.8 yearsRegistered 2022-11-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUpgrader Casino\n\tskinodds.com\n1.2 yearsRegistered 2025-06-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgowin.com\n12.0 yearsRegistered 2014-09-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrash Casino\n\tcsgorun.net\n7.3 yearsRegistered 2019-06-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\topenskins.com\n3.6 yearsRegistered 2023-02-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Gambling\n\trustbet.com\n7.6 yearsRegistered 2019-02-07\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgomagic.com\n9.4 yearsRegistered 2017-05-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUpgrader/Contract\n\tcsgobounty.com\n11.5 yearsRegistered 2015-03-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tezskins.com\n27.5 yearsRegistered 1999-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\trustcases.com\n7.2 yearsRegistered 2019-06-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgoreaper.com\n11.1 yearsRegistered 2015-08-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgocases.com\n12.3 yearsRegistered 2014-06-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Upgrader\n\tcsgo-skins.com\n11.2 yearsRegistered 2015-07-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgonet.com\n8.8 yearsRegistered 2017-12-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\twtfskins.com\n9.0 yearsRegistered 2017-10-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Casino\n\tflamecases.com\n10.0 yearsRegistered 2016-09-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tgamedom.com\n11.7 yearsRegistered 2015-01-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Battles\n\tskin.club\n9.0 yearsRegistered 2017-09-04\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsc-auth.net\n7.5 yearsRegistered 2019-04-02\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tdaddyskins.com\n9.9 yearsRegistered 2016-10-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Gambling\n\trustix.gg\n1.7 yearsRegistered 2025-01-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Upgrade\n\tskins.club\n4.2 yearsRegistered 2022-07-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgohouse.org\n146 daysRegistered 2026-04-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskinrave.net\n216 daysRegistered 2026-02-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tbloodycase.gg\n19 daysRegistered 2026-09-02\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nClicker/Upgrade\n\tcsgoclicker.com\n8.3 yearsRegistered 2018-05-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustbet.gg\n4.0 yearsRegistered 2022-09-30\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcs-drop.com\n262 daysRegistered 2026-01-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\thellstore.net\n11.7 yearsRegistered 2015-01-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustloot.com\n354 daysRegistered 2025-10-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgo-case.com\n10.3 yearsRegistered 2016-05-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgogem.com\n9.9 yearsRegistered 2016-10-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\trainbet.com\n8.8 yearsRegistered 2017-11-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nservices.rainbet.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustclash.com\n5.4 yearsRegistered 2021-05-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrash Casino\n\t12cs.fail\n181 daysRegistered 2026-03-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\twww.tf2easy.com\n6.3 yearsRegistered 2020-06-02\nRDAP ↗ · tf2easy.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2blaze.com\n7.6 yearsRegistered 2019-01-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tshuffle.com\n30.1 yearsRegistered 1996-07-31\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tbuff.market\n5.9 yearsRegistered 2020-10-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tavan.market\n8.3 yearsRegistered 2018-05-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Engine\n\tcs.money\n11.0 yearsRegistered 2015-09-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.dota.trade\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tuuskins.com\n2.6 yearsRegistered 2024-01-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Market\n\tyoupin898.com\n6.1 yearsRegistered 2020-08-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tc5game.com\n10.5 yearsRegistered 2016-03-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\twaxpeer.com\n7.3 yearsRegistered 2019-05-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwaxpeer.com\n7.3 yearsRegistered 2019-05-20\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBot Trading\n\tcs.money\n11.0 yearsRegistered 2015-09-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.dota.trade\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUS Marketplace\n\tdmarket.com\n30.2 yearsRegistered 1996-07-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nOfficial Market\n\tsteamcommunity.com/market\n20.3 yearsRegistered 2006-05-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNot an external login site2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Platform\n\tlootfarm.com\n11.9 yearsRegistered 2014-10-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Market\n\trustskins.com\n7.6 yearsRegistered 2019-01-31\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tkrakatoa.com\n26.4 yearsRegistered 2000-05-15\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\tshadowpay.com\n10.1 yearsRegistered 2016-08-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nChinese Powerhouse\n\tigxe.cn\n15.0 yearsRegistered 2011-09-06\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAutomated Swap\n\tswap.gg\n9.6 yearsRegistered 2017-01-29\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCash-out Portal\n\tbitskins.com\n11.2 yearsRegistered 2015-07-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Automation\n\ttf2mart.com\n1.1 yearsRegistered 2025-08-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Auctions\n\tskinbid.com\n10.2 yearsRegistered 2016-06-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Rental\n\tlootbear.com\n8.7 yearsRegistered 2018-01-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Valuation\n\tbackpack.tf\n14.4 yearsRegistered 2012-05-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Botnet\n\tstntrading.eu\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Cashout\n\tskinwallet.com\n18.0 yearsRegistered 2008-09-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nDota 2 Market\n\tdota2market.com\n12.2 yearsRegistered 2014-07-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nServer Network\n\txplay.gg\n5.3 yearsRegistered 2021-06-13\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMatchmaking Portal\n\tesportal.com\n26.8 yearsRegistered 1999-12-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nLATAM Hub\n\tgamersclub.com.br\n11.2 yearsRegistered 2015-06-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tools\n\tepidemic.gg\n4.9 yearsRegistered 2021-11-03\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tcs2stash.com\n3.5 yearsRegistered 2023-03-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tcsgoskins.gg\n6.8 yearsRegistered 2019-12-21\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tsteamanalyst.com\n12.6 yearsRegistered 2014-02-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Exchange\n\tsteamcardexchange.net\n13.3 yearsRegistered 2013-05-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tracker\n\tdotabuff.com\n14.2 yearsRegistered 2012-06-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tracker\n\ttracker.gg\n8.9 yearsRegistered 2017-10-12\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Exchange\n\tfunpay.com\n17.0 yearsRegistered 2009-09-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nGrey Market\n\tplayerauctions.com\n26.3 yearsRegistered 2000-06-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Portal\n\teldorado.gg\n8.0 yearsRegistered 2018-09-12\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Key Market\n\tg2a.com\n24.8 yearsRegistered 2001-12-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Key Market\n\tkinguin.net\n16.8 yearsRegistered 2009-12-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nVirtual Services\n\tg2g.com\n31.1 yearsRegistered 1995-08-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Broker\n\tplayerup.com\n19.3 yearsRegistered 2007-05-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfhub.net\n2.7 yearsRegistered 2023-12-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfaccounts.com\n5.3 yearsRegistered 2021-05-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Shop\n\tbuycsgorank.com\n6.2 yearsRegistered 2020-07-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tcsgosmurfkings.com\n9.3 yearsRegistered 2017-06-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfstore.co\n8.6 yearsRegistered 2018-03-03\nWHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlvlup.com\n9.9 yearsRegistered 2016-11-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlevels.com\n10.6 yearsRegistered 2016-02-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tlevelsteam.com\n79 daysRegistered 2026-07-04\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlevelu.com\n6.0 yearsRegistered 2020-09-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\teloking.com\n12.2 yearsRegistered 2014-07-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\tboosteria.org\n11.9 yearsRegistered 2014-10-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tovergear.com\n14.4 yearsRegistered 2012-04-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tblazingboost.com\n14.2 yearsRegistered 2012-06-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\tdota2boost.com\n2.9 yearsRegistered 2023-10-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tbuyboost.com\n22.4 yearsRegistered 2004-04-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\nحجة التحقيقالقاعدة المختارة / التحليل والتعليق+\nعبء الإثبات\n\nيتناول التحقيق التباين بين القيود المفروضة على الاستخدام التجاري والخدمات المذكورة هنا. قم بتصنيف كل نشاط والتأكد من وجود أي إذن صريح قبل اعتباره انتهاكًا للعقد. لا تنطبق رسوم «Community Market» على جميع المعاملات التجارية الخارجية.\n\nما هو السجل المُعلَّم، وما ليس به\n\nيتم وضع علامة على السجل عندما يتضمن الملف ملاحظة مؤرخة تجعل المنصة تندرج ضمن نطاق البند من حيث نصه. ولا تعتبر العلامة مخالفة تم البت فيها، ولم يتم تقديم أي إذن صريح Valve في السجل لأي من المنصات المدرجة هنا. وفي حالة حصول المنصة على ترخيص، فإن نشر ذلك يؤدي إلى حل المشكلة المتعلقة بالبند.\n\nالمصادر والمنهجيةالتقديرات والتعاريف والنطاق+\n\nتشير الأرقام المذكورة أعلاه إلى القاعدة المحددة. يتم تجميع أنواع السجلات لكل منصة مرة واحدة؛ وتظهر العلامات الكاملة في تفاصيل المنصة. يتم تطبيق البحث والمرشحات ضمن تلك القاعدة. تأتي تواريخ التسجيل من اللقطة المحفوظة لـ RDAP / WHOIS. تستخدم النطاقات الفرعية تاريخ إنشاء النطاق الأصلي. لا يُثبت العمر وحده استمرارية التشغيل أو مسار المصادقة. تأتي أسماء مضيفات المصادقة الحالية من طلبات OpenID المحفوظة، مع طابع زمني بتوقيت UTC؛ ولا تعيد عمليات الفحص غير المحلولة استخدام التسميات القديمة. يتوقف المراقب قبل تسجيل الدخول عبر Steam ولا يختبر حالة مرشح الارتباط Steam. تنزيل ملاحظات المسار ↗ تنزيل نتائج التسجيل ↗\n\nاستكشف أرشيف المصدر ↗\nالملحق (ز) — من نموذج الرفض إلى السجل الأصلي\nدليل إجراءات DSAR: طلب الأدلة\n\nاستخدم المادة 15 من اللائحة العامة لحماية البيانات (GDPR) لطلب البيانات الشخصية المتعلقة بإنشاء مفتاح واجهة برمجة التطبيقات (API)، واستعادة الحساب، والوصول إلى خدمات الدعم. ويمكن أن يساعد السجل المحفوظ في تحديد من قام بإجراء ما، وما الذي اعتمدت عليه المنصة في ذلك.\n\n01\nاحتفظ بخطك الزمني.\n\nاحفظ إشعارات الحساب والتذاكر ومعرّفات المعاملات وتواريخها بتوقيت UTC. قم بتأمين الحساب وراجع خيارات الاسترداد المتاحة للعبة والمعاملة.\n\nSteam معلومات حول الحماية التجارية ↗\n02\nاطلب الحصول على بياناتك المحفوظة.\n\nاطلب الحصول على الطوابع الزمنية، وعناوين IP للمصدر، والأحداث الرئيسية في دورة حياة المفتاح، وتأكيدات الأمان، وإجراءات الاسترداد المتعلقة بالحساب. وقم بتضمين أحداث الوصول إلى الدعم والمستلمين عندما تكون تلك البيانات ذات صلة بك.\n\n03\nاحتفظ بسجل التسليم.\n\nاستخدم مسار الاتصال الخاص بالخصوصية الخاص بـ Valve. وتبلغ المدة المعتادة للرد شهرًا واحدًا؛ ويجب توضيح أسباب أي تمديد ضروري لمدة تصل إلى شهرين إضافيين خلال ذلك الشهر الأول.\n\nValve مسار الاتصال الخاص بالخصوصية ↗ محفوظ 2026-09-21 ↗\n04\nقارن بين الردود.\n\nقم بمطابقة السجلات مع الجدول الزمني الخاص بك. اطلب توضيح أسباب أي إغفالات، ثم استخدم مسار الشكوى عبر السلطة الإشرافية إذا لزم الأمر. احتفظ بالرد تمامًا كما ورد إليك.\n\nنطاق التطبيق / المادة 15\n\nيشمل حق الوصول البيانات الشخصية المحفوظة، بما في ذلك البيانات الموجودة في سجلات التسجيل. ولا يضمن هذا الحق الحصول على كل وثيقة داخلية أو سجلات أعيد تجميعها أو بيانات غير محجوبة تتعلق بأشخاص آخرين. اطلب نسخة واضحة وأسباب أي قيود مفروضة.\n\nإرشادات مجلس أوروبا لحماية البيانات (EDPB) بشأن الوصول، الفقرات 2 و4–6 ↗ · المواد 12 و15 و77 من اللائحة العامة لحماية البيانات (GDPR) ↗ محفوظ 2026-09-20 ↗\n\nطلب الوصول إلى البيانات الخاصة بالشخص المعنياللائحة العامة لحماية البيانات (GDPR) / المادة 15\nأمان الحساب وسجلات الوصول\n\nيرجى استبدال الحقول الموضوعة بين الأقواس قبل الإرسال.\n\nTo: Valve Privacy Team\nSubject: Article 15 GDPR request — account security records\n\nAccount / SteamID: [YOUR ACCOUNT IDENTIFIER]\nRelevant period (UTC): [START] to [END]\nRelated support tickets: [TICKET REFERENCES]\n\nI request a copy of the personal data concerning me that you retain for this period, including:\n\n1. API-key registration, confirmation, use and revocation events, with available timestamps, source IP addresses, registered domains, device or user-agent information and non-secret key identifiers.\n\n2. Recorded account-recovery actions, password/email/phone changes, Steam Guard removals or resets, confirmation events and the account-related evidence relied on to authorize those actions.\n\n3. Personal data in support-access and administrative-action logs concerning my account, including available dates, purposes, actions and the support entity involved, subject to applicable rights of others.\n\n4. Account-related records used to determine any sanction, and available records of my complaints, reviews and responses.\n\nPlease also provide the applicable processing purposes, categories, recipients, retention periods or criteria, and available information about sources where data were not obtained from me.\n\nWhere processing relies on my consent, please provide the retained record of the consent relied upon and the wording presented at that time.\n\nPlease provide an intelligible electronic copy with time zones and field definitions. Please do not include active credentials or secret tokens. If any requested data are not held, please say so. For any withheld data, please identify the scope and legal basis of the restriction and provide the remainder.\n\nPlease acknowledge receipt and respond within the applicable Article 12 period, explaining any necessary extension. I also ask you to preserve relevant existing records while this request is handled.\n\nName: [YOUR NAME]\nDate: [DATE]\nما الذي يمكن أن يوفره عنوان IP لمركز البيانات\nأي تباين يُعد دليلاً يستدعي التحقيق.\n\nيمكن أن يكون طلب مفتاح واجهة برمجة التطبيقات (API) الصادر من شبكة مركز بيانات، كما في مثال مزود خدمات الاستضافة الذي أُثير في هذا التحقيق، ذا صلة عند مقارنته بسجلات تسجيل الدخول والتأكيدات والخط الزمني للمستخدم. ولا يكفي عنوان IP وحده لتحديد هوية الفاعل أو لإبطال كل تدابير الحماية تلقائيًا. وقد تؤدي الأدلة التي تشير إلى أن جهة معادية هي التي قدمت الموافقة المسجلة إلى الطعن في الاعتماد على تلك الموافقة؛ أما الأسس القانونية الأخرى ومسائل المسؤولية فتتطلب تحليلًا منفصلاً.\n\nاطلع على الشكوى المحفوظة المتعلقة بالحظر واللائحة العامة لحماية البيانات (GDPR) →\nالملحق ح — تحليل أرشيف «وايباك ماشين» · إحصاءات الدعم المنشورة\nحجم الدعم. أوقات الاستجابة المنشورة.\nالسياق وحدود المصدر\n\nValve تنشر إحصاءات الدعم اليومية على store.steampowered.com/stats/support. تحتفظ أرشيفات «Wayback Machine» بلقطات تاريخية لهذه الصفحة من عام 2018 إلى عام 2026. ولا تتوافق نسبة الحجم إلى عدد الموظفين التي تشير إليها هذه الأرقام مع المراجعة البشرية لكل تذكرة في أوقات الاستجابة المنشورة.\n\nقارن أرقام الدعم المؤرشفة لـ Valve عبر اللقطات المحفوظة. توضح المنهجية ما يمكن لهذه الأرقام قياسه وما لا يمكنها قياسه.\n\nحجم الأعمال مقابل وقت الاستجابة المنشور (2018 → 2026)\nطابوران أمام مكتب الدعم الواحد، كما يتضح من 21 لقطة شاشة محفوظة.\n\nValve تنشر أرقام الدعم المباشر على store.steampowered.com/stats/support. كل نقطة من النقاط الواردة أدناه تمثل الحد الأدنى Valve نفسه، كما ورد في تلك الصفحة في اليوم الذي قام فيه «أرشيف الإنترنت» بتسجيلها — وليست تقديرًا من جانبنا. وكلا السلسلتين تمثلان نفس القياس بنفس الوحدة، لذا فإنهما تنتميان إلى محور واحد ويمكن مقارنة كل منهما بالأخرى مباشرةً.\n\nطلبات استرداد الأموال — المبلغ Valve محتفظ بهأمان الحساب واستعادته — الحساب الذي فقدته\n0 h\n2 h\n4 h\n6 h\n8 h\n10 h\nno captures · 38 months\n2019\n2020\n2021\n2022\n2023\n2024\n2025\n2026\n8 h 44 m\naccount recovery\n52 m\nrefunds\n15 m — one capture only\n49–55 دقيقةالحد الأدنى لمعدل الاسترداد في كل عملية تسجيل في الفترة من فبراير 2018 إلى أغسطس 2026. وعلى مدار ثماني سنوات ونصف، يتغير هذا الحد بأقل من ست دقائق، في حين يتغير حجم الاسترداد اليومي بمقدار تسعة أضعاف.\n2.4 ساعة → 8.7 ساعةيبلغ الحد الأدنى لوقت استعادة الحساب حوالي 2.4 ساعة في كل قراءة حتى ديسمبر 2022، باستثناء قراءة واحدة. أما في القراءات الثلاث لعام 2026، فقد سجل Valve أوقاتًا تبلغ 10.9 ساعة و5.8 ساعة و8.7 ساعة.\n×2.8 → ×13إلى أي مدى يكون استرداد الأموال أبطأ من عمليات رد المبالغ، وفقًا للأرقام التي نشرها Valve نفسه. ظل الوضع ثابتًا لمدة خمس سنوات، ثم اتسعت الفجوة — والطابور الذي أصبح أبطأ هو ذلك الذي يتحمل فيه المستخدم، وليس Valve، التكاليف من جيبه الخاص.\n\nالمصدر: 21 نسخة محفوظة على موقع Wayback Machine لـ store.steampowered.com/stats/support، من 2018-02-03 إلى 2026-08-10؛ الاستخراج في VALVE_EVIDENCE_PACK/databases/steam_support_stats_history.json. اقرأ القيم الحدية مع الأرقام: يوضح الرسم البياني أدنى الحد الأعلى للنطاق Valve نسخ. ويُعد الحد الأعلى المنشور أسوأ في كلا الخطين — حيث تراوحت مدة استرداد الأموال بين 1.5 ساعة و1.5 يوم، وتراوحت مدة استعادة الخدمة بين 7.0 ساعات و3.6 أيام. تم أرشفة لقطتين في نسخة مترجمة من نفس الصفحة Valve — 2018-11-03 باللغة التشيكية، و2020-03-25 باللغة الفرنسية — وتم تمييزهما بـ (cs) و(fr) في الجدول؛ وتظهر أرقامهما هنا مع ترجمة كلمات الوحدات والرقم كما نُشرت، بينما تُحفظ سلاسل النص الأصلية حرفياً في ملف الاستخراج. نشرت كل لقطة وقت استجابة لكلتا قائمتي الانتظار، ولم يتم استيفاء أي نقطة على أي من الخطين. تم تمييز الرقم الوحيد لاستعادة البيانات لمدة 15 دقيقة البالغ 2020-10-21 على الرسم البياني وتركه كما هو: فهو يظهر في لقطة واحدة فقط ولا توجد أي لقطة أخرى تقترب منه بأي درجة من الدرجات. لا توجد أي قراءة بين 2022-12-08 و2026-02-01؛ وقد تم تظليل تلك الفجوة التي تبلغ 38 شهرًا في السجل، ولم يتم رسم أي خط عبرها. تصف هذه الأرقام أوقات الاستجابة المنشورة. وهي لا تُظهر ما يحدث داخل التذكرة، ولم تنشر Valve أي أرقام تتعلق بعدد الموظفين يمكن مقارنة هذه الأرقام بها.\n\nفتح كل لقطة في شكل جدول\nكل لقطة محفوظة، كما نُشرت\nالتقاط\tالمبالغ المستردة / اليوم\tالرد بشأن استرداد المبلغ\tمعدل الاسترداد في اليوم\tاستجابة الإنقاذ\n2018-02-03\t98,788\t50.12 دقيقة إلى 1.52 ساعة\t25,662\t2.51 ساعة إلى 1.80 يوم\n2018-05-07\t60,494\t53.83 دقيقة إلى 1.47 يوم\t24,226\tمن 2.45 ساعة إلى 2.22 يومًا\n2018-08-02\t69,084\t50.27 دقيقة إلى 1.59 ساعة\t28,953\tمن 2.44 ساعة إلى 22.17 ساعة\n2018-11-03 (cs)\t63,410\t49.28 دقيقة إلى 1.54 ساعة\t33,910\t2.42 ساعة إلى 1.31 يومًا\n2019-02-01\t76,305\t50.13 دقيقة إلى 1.52 ساعة\t35,164\tمن 2.44 ساعة إلى 2.04 يوم\n2019-05-18\t78,951\t51.03 دقيقة إلى 3.12 ساعة\t27,514\tمن 2.46 ساعة إلى 20.39 ساعة\n2019-09-07\t78,941\t50.65 دقيقة إلى 1.66 ساعة\t28,812\tمن 2.42 ساعة إلى 13.59 ساعة\n2019-12-13\t69,589\t50.77 دقيقة إلى 1.55 ساعة\t25,322\tمن 2.45 ساعة إلى 1.13 يوم\n2020-03-25 (fr)\t139,278\t49.45 دقيقة إلى 1.53 ساعة\t32,302\tمن 2.48 ساعة إلى 3.62 يومًا\n2020-06-26\t278,504\t48.98 دقيقة إلى 2.29 ساعة\t20,343\tمن 2.39 ساعة إلى 6.99 ساعة\n2020-10-21\t107,633\tمن 50.80 دقيقة إلى 1.54 ساعة\t20,688\t15.33 دقيقة إلى 8.62 ساعة\n2021-03-20\t158,956\t50.80 دقيقة إلى 1.64 ساعة\t25,760\tمن 2.34 ساعة إلى 11.62 ساعة\n2021-06-26\t547,907\t51.93 دقيقة إلى 6.73 ساعات\t29,728\tمن 2.40 ساعة إلى 15.63 ساعة\n2021-10-10\t170,103\t51.88 دقيقة إلى 3.25 ساعات\t23,989\tمن 2.39 ساعة إلى 13.05 ساعة\n2022-01-31\t354,386\t53.65 دقيقة إلى 8.09 ساعات\t24,391\tمن 2.42 ساعة إلى 15.29 ساعة\n2022-05-09\t172,555\t51.83 دقيقة إلى 1.65 ساعة\t23,289\tمن 2.41 ساعة إلى 16.90 ساعة\n2022-09-05\t153,453\t53.67 دقيقة إلى 4.15 ساعات\t23,594\tمن 2.45 ساعة إلى 1.22 يومًا\n2022-12-08\t181,075\t54.83 دقيقة إلى 6.67 ساعات\t27,111\tمن 2.46 ساعة إلى 18.89 ساعة\n2026-02-01\t317,762\tمن 50.30 دقيقة إلى 1.52 ساعة\t47,197\tمن الساعة 10:91 إلى الساعة 21:30\n2026-05-09\t246,776\t50.12 دقيقة إلى 1.52 ساعة\t35,264\tمن 5.81 ساعة إلى 15.60 ساعة\n2026-08-10\t373,244\t52.05 دقيقة إلى 2.07 ساعة\t45,319\tمن 8.73 ساعة إلى 16.52 ساعة\nالملاحظة الرئيسية:\nعبر 21 نسخة محفوظة على موقع Wayback في الفترة من 2018-02-03 إلى 2026-08-10، تراوحت طلبات الاسترداد اليومية بين 60,494 (مايو 2018) إلى 547,907 (يونيو 2021) — أ 9.1× الفارق. يبلغ الرقم لعام 2026 373,244 (+278% مقارنةً ببيانات فبراير 2018).\nخلال تلك السنوات التسع نفسها، لم يخرج الحد الأدنى المعلن لوقت الاستجابة لطلبات الاسترداد عن 49–55 دقيقة النطاق: حركة إجمالية استغرقت أقل من ست دقائق، في حين تضاعف حجم العمل الكامن وراءها تسع مرات.\nإذا قرأ الشخص كل تذكرة لمدة 5 ثوانٍ فقط، فإن معالجة 373,244 تذكرة يوميًا (حسب الوضع الحالي) ستستغرق 22 موظفًا يعملون على مدار الساعة طوال أيام الأسبوع فقط لفتحها وإغلاقها؛ وفي ذروتها (547,907، يونيو 2021) يرتفع هذا الرقم إلى 32.\nإذا كان وقت الاستجابة المنشور يعكس وقت معالجة كل تذكرة (حوالي 52 دقيقة لكل تذكرة)، فإن العدد الضمني للموظفين العاملين في الوقت نفسه سيكون في حدود 13,500 وكلاء عند الحجم الحالي و~20,000 عند الذروة. لم يتم العثور على أي رقم موثق بشأن عدد الموظفين الداعمين لـ Valve؛ ولم يتم افتراض أي رقم هنا.\nما يلي: لا تتوافق نسبة الحجم إلى عدد الموظفين مع المراجعة البشرية لكل تذكرة في أوقات الاستجابة المعلنة. وتتوافق الأرقام مع عملية مراجعة أولية مؤتمتة إلى حد كبير؛ ولم يتم الإعلان عن النسبة التي تخضع للمراجعة البشرية.\nلماذا يعد هذا الأمر مهمًا للامتثال للائحة العامة لحماية البيانات (GDPR)\n\nتحظر المادة 22 من اللائحة العامة لحماية البيانات (GDPR) اتخاذ القرارات الفردية الآلية حصريًّا التي تنطوي على آثار قانونية جوهرية، دون توفير الحق في المراجعة البشرية عند الطلب. وإذا كانت قرارات الدعم (إغلاق التذاكر، وإجراءات الحساب، ورفض طلبات الحصول على البيانات) تُتخذ بالكامل بواسطة برامج آلية، فإن كل قرار من هذا القبيل «يؤثر بشكل كبير» على المستخدم قد يشكل انتهاكًا للمادة 22.\n\nتذكرة HT-2YBP-F7JP-D4VB (القسم 18) أُغلق بعد ثلاثة أيام بإحالة نموذجية دون الخوض في الأساس القانوني المذكور. ولا يمكن تحديد ما إذا كان شخص ما قد راجعه أم لا من خلال التذكرة؛ وهذا سؤال يمكن للسلطة الإشرافية أن توجهه إلى Valve بموجب المادة 22 والمادة 15(1)(ح).\n\nالمصدر: لقطات من Wayback Machine لموقع store.steampowered.com/stats/support (2018-02-03، 2021-06-26، 2026-08-10) — البيانات المستخرجة إلى VALVE_EVIDENCE_PACK/databases/steam_support_stats_history.json (21 لقطة، 2018–2026). ملاحظة: وقت الاستجابة «~52 دقيقة» هو الحد الأدنى لفئة استرداد الأموال؛ أما وقت الاستجابة المتعلق بأمن الحساب فكان يتراوح بين 2.4 و16.5 ساعة عبر نفس اللقطات. 2021-06-26 هو الذروة على الإطلاق (547,907 طلبات استرداد الأموال)، وليس نقطة وسط ثابتة — فقد ارتفع الحجم ~6 أضعاف في الفترة 2020–2021 ثم انخفض جزئيًا قبل أن يتعافى ليصل إلى 373 ألفًا في عام 2026.\nالملحق الأول — نطاق مجموعة البيانات · الأعداد التي يمكن إعادة إنتاجها\nاحسب عدد السجلات. تحقق من النطاق.\nالسياق وحدود المصدر\n\nاحسب عدد السجلات، ثم تحقق من صحة الادعاءات: فكل رقم من الأرقام الواردة أدناه يمكن استنتاجه من جديد من الملفات المنشورة.\n\nافحص مجموعات البيانات الأساسية، وأعد حساب الأعداد، وافصل بين الصفوف المصدر والحوادث الفريدة.\n\nيحتوي ملف CSV الرئيسي على 40,448 صفوف. ومن بين هذه، 36,516 تأتي من موجز «Discord-AntiScam» الخاص بحالات التصيد الاحتيالي. أما الباقي 3,932 تشمل الصفوف موقع GitHub، والمراجعات، ونتائج البحث، ومحتوى المنتديات، ومصادر أخرى، مما يوفر فهرسًا شاملاً للمواضيع التي أبلغ عنها أعضاء المجتمع والتقارير الأمنية.\n\nداخل ملف CSV هذا، تم تصنيف 1,690 صفوف تحت تصنيف المجموعة «ثغرات أمنية لم يتم إصلاحها»، والتي تمثل المشكلات التاريخية التي واجهها المستخدمون وحالات الكشف عن الثغرات الأمنية. ويتطلب تتبع هذه التقارير مراجعة الجدول الزمني الخاص بكل إصدار من إصدارات البرنامج، بالإضافة إلى سجل التصحيحات العامة.\n\nيُعد الأرشيف القابل للبحث الذي يضم 16,319 سجلًا نسخة منفصلة ومُنظمة مع قائمة بيانات خاصة بها، وقد صُمم من أجل الاستكشاف المحلي الدقيق لمطالبات المستخدمين وتقارير الحوادث المحددة.\n\nلإنشاء سجل تدقيق موثوق، يجب التحقق من صحة كل سجل يبلغ عنه المستخدم بمقارنته بالجداول الزمنية الموثقة لعمليات البناء وسجلات التصحيحات السابقة.\n\nسجلات المجموعة المنفصلة للجزء الثاني 231,829 معرّفات الإدراج الفريدة، بما في ذلك 33,509 في فئة التسجيل الآلي و198,320 التي تم وضع علامة عليها على أنها تحويلات غير مُثبتة. يتطابق معدل SHA-256 لملف الإدخال مع القياس المحفوظ. تصف هذه الأرقام محاولات الإدراج والتحويلات الملحوظة بدلاً من قيم المعاملات النهائية أو إجماليات السرقات التي تم التحقق منها، مما يسلط الضوء على الحاجة إلى سجلات المنصات الأساسية لقياس الأثر الاقتصادي الدقيق. سرد القياسات والقيم التجزئية ↗\n\nملف CSV الرئيسي ↗ · قائمة محتويات الأرشيف القابلة للبحث ↗ · فحص السجلات المصدرية ↗\n\nالملحق (ي) — نبذة عن هذا التحقيق\nValve لا تنشر أي سجلات تتعلق بإنفاذ القانون. لقد صنعنا واحدًا.\n\nمستقل. غير تجاري. مبني على البيانات العامة حصريًّا. تم تقديمه إلى الجهات التنظيمية.\n\n88.97%أسطول الأتمتة لم يتأثر — لا يوجد حظر من أي نوع\n67.77%من بين 51,732 من المحتالين الذين صدرت بحقهم أحكام، أفلتوا من العقاب\n$26.8M+الحد الأدنى للإنفاق في المتاجر من قبل الأسطول غير المحدود\n3.6%نطاقات المقامرة التي تم حجبها بواسطة «مرشح الروابط» الخاص بـ Valve\n8 سنواتمن الحوادث الأمنية الموثقة\n\nما هو هذا. ملف تحليلي حول منصة Steam التابعة لشركة Valve — بما في ذلك سجلها في مجال إنفاذ القوانين، واقتصادها القائم على «زراعة البطاقات»، وإطارها القانوني، والبنية التحتية للمصادقة التي يستخدمها مشغلو المقامرة عبر مرحل OpenID الخاص بـ Steam. يمكن التحقق من صحة كل رقم من مصدرين: واجهة برمجة التطبيقات (API) العامة الخاصة بـ Valve ومجموعات البيانات المنشورة إلى جانب هذا التحقيق.\n\nلمن يُعد هذا البرنامج. الهيئات التنظيمية التي تتمتع بسلطة قضائية على Valve — وهي السلطة الإشرافية المعنية باللائحة العامة لحماية البيانات (GDPR) في هولندا، ومكتب مكافحة غسل الأموال (FinCEN)، ولجنة الأوراق المالية والبورصات (SEC)، ومنسق الخدمات الرقمية بموجب قانون الخدمات الرقمية (DSA)، وهيئة حماية المستهلك والمنافسة (UOKiK)، وأي هيئة إنفاذ قانونية تحقق في التدفقات المالية المرتبطة بـ Steam. وكذلك للصحفيين والباحثين وكل مستخدم تعرض لحظر دائم لحسابه، أو رُفض طلب استرداد أمواله، أو سُرق مخزونه، وقيل له إنه لا يوجد حق في الاستئناف.\n\nالمطلب الوحيد. Valve تحتفظ بهذه البيانات بدقة تامة — مع إرفاق أسباب الحظر، ومساحة الهوية الكاملة، وفي الوقت الفعلي. ويمكنها تنفيذ كل استعلام في هذا الملف في غضون ثوانٍ، وقد اختارت عدم نشر أي جزء منه. والسؤال المطروح على أي سلطة مختصة بسيط: لماذا لا؟\n\nما لا يدعيه المؤلفون. لم يتم إتمام أي عملية تسجيل دخول إلى Steam على أي منصة تابعة لجهة خارجية خلال هذا العمل. إن عنوان URL الخاص بـ OpenID المقدم هو الذي يحدد معلمات الطلب، وليس عملية تسجيل الدخول المكتملة. ولا يُعد وجود نطاق منفصل قابل للتسجيل دليلاً بحد ذاته على التهرب. تعد تواريخ التسجيل حدودًا دنيا للوقت الذي يمكن أن يكون فيه المضيف قد ظهر لأول مرة في طلب OpenID؛ وهي لا تثبت الاستخدام المستمر. لا يدعي المؤلفون معرفة أو نية Valve: فكل بيان بشأن Valve مرتبط بوثيقة عامة مؤرخة أو بملاحظة مؤرخة. وحيثما تعذر إثبات ادعاء ما بوثيقة مصدر، تم حذفه.\n\nمن نحن\n\nPhishDestroy — محققون مستقلون. لا توجد أي صلة بشركة Valve أو بأي منصة مذكورة هنا. تم استخدام حساب Steam واحد فقط لتوثيق طلب «اللائحة العامة لحماية البيانات» (GDPR) الوارد في القسم 18.\n\nإخلاء المسؤولية القانونية\n\nتحقيق غير تجاري ولامركزي يهدف إلى خدمة المصلحة العامة. تُقدَّم جميع البيانات «كما هي» دون أي ضمانات. ولا يُعد هذا المنشور قرارًا قضائيًّا.\n\nالمجال العام\nالترخيص\n\nتم التنازل عن جميع الحقوق لصالح البشرية. يُسمح بالنسخ والتكييف والنشر — دون الحاجة إلى ذكر المصدر. الوصول من منطقة خاضعة لرقابة مكتب مراقبة الأصول الأجنبية (OFAC): محظور. الترخيص الكامل وإخلاء المسؤولية →",
        "headings": [
          {
            "level": 2,
            "id": "briefing-heading",
            "text": "القاعدة. الرقم القياسي. الأسئلة التي لم تُجب عليها."
          },
          {
            "level": 2,
            "id": null,
            "text": "رسالة مفتوحة إلى لجنة المقامرة بولاية واشنطن"
          },
          {
            "level": 3,
            "id": "wsgc-public-address-title",
            "text": "تحولت العشرة أيام إلى عشر سنوات.أعد فتح السجل."
          },
          {
            "level": 2,
            "id": null,
            "text": "الموقع محجوب. أما مسار تسجيل الدخول فليس كذلك."
          },
          {
            "level": 3,
            "id": null,
            "text": "الشكل 3.1 — المساران، مرسومان."
          },
          {
            "level": 3,
            "id": null,
            "text": "فخ «الصورة الكبيرة»: «مرشح الروابط» مجرد مسرحية للامتثال، وليس درعًا واقيًا"
          },
          {
            "level": 3,
            "id": null,
            "text": "إن وجود نطاق رئيسي محجوب مقترن بمضيف مصادقة غير محجوب يترك مسار تسجيل الدخول مفتوحًا — ويظل مفتوحًا لسنوات."
          },
          {
            "level": 3,
            "id": null,
            "text": "الخلفية: ما هو Steam ولماذا يكتسب أهمية في هذا السياق"
          },
          {
            "level": 3,
            "id": null,
            "text": "ما فعله Valve: حجب النطاق"
          },
          {
            "level": 3,
            "id": null,
            "text": "ما هو نطاق الوكيل؟"
          },
          {
            "level": 3,
            "id": null,
            "text": "النقطة الحاسمة: يتم إرسال معرّف المضيف إلى Steam في كل طلب"
          },
          {
            "level": 3,
            "id": null,
            "text": "ما الذي يثبته هذا؟"
          },
          {
            "level": 3,
            "id": null,
            "text": "داخل Steam، قائمة Valve هي القائمة الوحيدة."
          },
          {
            "level": 3,
            "id": null,
            "text": "تجاوز حماية مرشح الارتباط"
          },
          {
            "level": 3,
            "id": null,
            "text": "متصفح الويب «Big Picture» يتسبب في تسرب ملفات تعريف الارتباط الخاصة بتسجيل الدخول ويكشف معلومات حساسة (مما قد يؤدي إلى الاستيلاء على الحساب)"
          },
          {
            "level": 3,
            "id": null,
            "text": "ماذا يعني ذلك بالنسبة للقاصر الذي لديه برنامج مكافحة فيروسات مثبت على جهازه"
          },
          {
            "level": 3,
            "id": null,
            "text": "عمر النطاق.تاريخ الملاحظة."
          },
          {
            "level": 2,
            "id": null,
            "text": "تم إغلاق نقطة نهاية. فقد نظام التتبع العام مفتاحًا."
          },
          {
            "level": 3,
            "id": null,
            "text": "حقبة ما قبل انقطاع التيار الكهربائي"
          },
          {
            "level": 3,
            "id": null,
            "text": "بعد التغيير"
          },
          {
            "level": 2,
            "id": null,
            "text": "جلسة واحدة. إمكانية وصول أكبر مما يراه المستخدم."
          },
          {
            "level": 3,
            "id": null,
            "text": "1. عدم كفاية المصادقة المتدرجة"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. عدم تطبيق مبدأ «أدنى مستوى من الصلاحيات»"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. خلل في إدارة الجلسات"
          },
          {
            "level": 3,
            "id": null,
            "text": "4. كان حجب مضيفي المصادقة على مستوى النطاق أمراً ممكناً من الناحية التقنية"
          },
          {
            "level": 3,
            "id": "integration-paradox-title",
            "text": "Valve يتم تجميعه وفقًا لهذه القواعد يوميًا. لكنه لم يتم تجميعه وفقًا لها هنا."
          },
          {
            "level": 4,
            "id": null,
            "text": "نطاقات GitHub الدقيقة مقابل Valve Steam واجهة برمجة تطبيقات الويب"
          },
          {
            "level": 2,
            "id": null,
            "text": "محاكي تفاعلي للاستغلال واختطاف الأنظمة"
          },
          {
            "level": 2,
            "id": null,
            "text": "نقاط النهاية الكامنة وراء التسلسل."
          },
          {
            "level": 2,
            "id": null,
            "text": "مربع محدد. من قام بهذا الإجراء؟"
          },
          {
            "level": 3,
            "id": null,
            "text": "كيف تمكنت Valve أخيرًا من إبطال مفعول «الاستبدال التجاري» — ولماذا استغرق الأمر 7 سنوات من الحلول البديلة"
          },
          {
            "level": 4,
            "id": null,
            "text": "فترة انتظار تغيير الصورة الرمزية والاسم (فبراير 2024)"
          },
          {
            "level": 4,
            "id": null,
            "text": "انعكاس الاتجاه في تداول CS2 لمدة 7 أيام (يوليو 2025)"
          },
          {
            "level": 4,
            "id": null,
            "text": "التحديث الإلزامي للرسائل الفورية عبر الهاتف المحمول لواجهة برمجة التطبيقات (ديسمبر 2023)"
          },
          {
            "level": 4,
            "id": null,
            "text": "لافتات عمر الحساب واسمه (2022–2024)"
          },
          {
            "level": 2,
            "id": null,
            "text": "قواعدهم. البرامج الانتخابية المعلنة."
          },
          {
            "level": 3,
            "id": "enforcement-focus-title",
            "text": "كتاب قواعد واحد. تطبيق غير متكافئ."
          },
          {
            "level": 4,
            "id": null,
            "text": "الأتمتة"
          },
          {
            "level": 4,
            "id": null,
            "text": "الاستخدام التجاري"
          },
          {
            "level": 4,
            "id": null,
            "text": "شبكة VPN وإخفاء الموقع"
          },
          {
            "level": 4,
            "id": null,
            "text": "إخفاء الروابط"
          },
          {
            "level": 4,
            "id": null,
            "text": "من الذي يراجع القرار عندما تقوم إدارة الدعم بإغلاق القضية؟"
          },
          {
            "level": 2,
            "id": null,
            "text": "واجهة برمجة تطبيقات (API) للأتمتة. قاعدة تمنع الأتمتة."
          },
          {
            "level": 3,
            "id": null,
            "text": "مغالطة «مطور الألعاب»"
          },
          {
            "level": 4,
            "id": null,
            "text": "تناقض الأتمتة"
          },
          {
            "level": 4,
            "id": null,
            "text": "موقع من جانب الخادم في تدفق المعاملات التجارية"
          },
          {
            "level": 2,
            "id": null,
            "text": "عشرة أيام مطلوبة. وعشر سنوات يجب تقديم حساب عنها."
          },
          {
            "level": 3,
            "id": "letter-company",
            "text": "شركة فالف"
          },
          {
            "level": 3,
            "id": null,
            "text": "عشرة أيام.ثم ماذا؟"
          },
          {
            "level": 3,
            "id": null,
            "text": "اتبع المضيف المُعلن عنه."
          },
          {
            "level": 3,
            "id": "washington-record-heading",
            "text": "موعدان نهائيان. معيار إنفاذ واحد لم يتم الرد عليه."
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve تمنح مواقع المقامرة مهلة 10 أيام"
          },
          {
            "level": 4,
            "id": null,
            "text": "واشنطن تضغط Valve"
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve ينفي التهمة"
          },
          {
            "level": 4,
            "id": null,
            "text": "المسارات التي تم رصدها في سبتمبر 2026"
          },
          {
            "level": 4,
            "id": null,
            "text": "بعد مرور ثمانية عشر شهراً على رد Valve، لا تزال الهيئة التنظيمية تصف ذلك بأنه «نية»."
          },
          {
            "level": 3,
            "id": null,
            "text": "«عقد الإشعار قبل 10 أيام»: تدقيق جنائي لتقييم مدى الصمود في المواقع الـ23 المحددة"
          },
          {
            "level": 4,
            "id": null,
            "text": "من الإنذارات التي تُصدر قبل 10 أيام إلى التكتلات الخارجية: معدل دوران بمليارات الدولارات"
          },
          {
            "level": 2,
            "id": null,
            "text": "اسم المضيف موجود بالفعل في الطلب."
          },
          {
            "level": 3,
            "id": null,
            "text": "السوابق الموثقة والمبلغ عنها"
          },
          {
            "level": 3,
            "id": null,
            "text": "ما الذي يظهره تاريخ التسجيل وما الذي لا يظهره"
          },
          {
            "level": 3,
            "id": null,
            "text": "التدقيق المقارن: معايير الامتثال لواجهة برمجة التطبيقات (API)"
          },
          {
            "level": 2,
            "id": "market-thesis-heading",
            "text": "فجوة السعر «off-Steam»"
          },
          {
            "level": 2,
            "id": null,
            "text": "الفارق في الأسعار قابل للقياس."
          },
          {
            "level": 3,
            "id": null,
            "text": "ما الذي يُوضِّحه هذا الرقم بالدولار"
          },
          {
            "level": 3,
            "id": null,
            "text": "تُدرج العديد من الأماكن قيمة بالدولار تزيد عن Steam."
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam لا تزال تتصدر من حيث عدد العروض."
          },
          {
            "level": 3,
            "id": null,
            "text": "النظام البيئي التجاري واضح للعيان."
          },
          {
            "level": 2,
            "id": null,
            "text": "من يمكنه إعادة ضبط الضمانات؟"
          },
          {
            "level": 3,
            "id": null,
            "text": "تذكرة استرداد أدت إلى تعطيل إجراءات الأمان الخاصة بالحساب، وخسارة مُبلغ عنها قدرها $10,000"
          },
          {
            "level": 3,
            "id": null,
            "text": "ما وراء المخزون."
          },
          {
            "level": 3,
            "id": "theft-ledger-title",
            "text": "Valve فتح الباب مرتين، بفارق ثلاثة وثلاثين شهراً بينهما. ولم يُغلق أبداً."
          },
          {
            "level": 4,
            "id": null,
            "text": "ما يوضحه السجل بشكل لا توضحه أي حالة بمفردها."
          },
          {
            "level": 3,
            "id": null,
            "text": "يجب أن تقترن السرية بالمساءلة الفنية."
          },
          {
            "level": 2,
            "id": null,
            "text": "تتبع مسار الأموال. افصل بين المعاملات."
          },
          {
            "level": 3,
            "id": null,
            "text": "المكان الذي تتحرك فيه الأموال فعليًّا."
          },
          {
            "level": 3,
            "id": null,
            "text": "صنف النشاط أولاً، ثم الالتزام."
          },
          {
            "level": 3,
            "id": null,
            "text": "تتبع العائدات والمعلومات والمساعدة."
          },
          {
            "level": 2,
            "id": null,
            "text": "قانون الخدمات الرقمية: توثيق المعرفة"
          },
          {
            "level": 3,
            "id": null,
            "text": "مطالبة مدتها عشرة أيام."
          },
          {
            "level": 3,
            "id": null,
            "text": "النافذة الزمنية لنظام DSA."
          },
          {
            "level": 3,
            "id": null,
            "text": "تحتاج المدة إلى سجل للإشعارات."
          },
          {
            "level": 3,
            "id": null,
            "text": "من إجمالي المبيعات السنوية على مستوى العالم"
          },
          {
            "level": 2,
            "id": null,
            "text": "القاصرون: تسجيل الدخول بـ Steam لا يُعتبر تحققًا من العمر"
          },
          {
            "level": 3,
            "id": null,
            "text": "حدد المشغل والبيانات."
          },
          {
            "level": 3,
            "id": null,
            "text": "تسجيل مسار العملية بدءًا من تسجيل الدخول وحتى إجراء الإيداع."
          },
          {
            "level": 2,
            "id": null,
            "text": "الطلب. الرد. المقارنة المفقودة."
          },
          {
            "level": 3,
            "id": null,
            "text": "السجلات موجودة؛ لكن صاحب البيانات لم يتسلمها."
          },
          {
            "level": 2,
            "id": null,
            "text": "اتفاقية الاشتراك مقابل البنية الأساسية الخاصة بالمنصة"
          },
          {
            "level": 3,
            "id": null,
            "text": "السقف الأقصى للسوق وحظر الاستخدام التجاري"
          },
          {
            "level": 3,
            "id": null,
            "text": "تُعد ثغرة مفتاح واجهة برمجة التطبيقات (API) مسألة تتعلق بتصميم المنصة، وليست نتيجة لإهمال المستخدم"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve يتلقى اسم مضيف المصادقة عند كل عملية تسجيل دخول"
          },
          {
            "level": 3,
            "id": null,
            "text": "النمط السائد في الشكاوى المؤرشفة"
          },
          {
            "level": 3,
            "id": null,
            "text": "إن المحكمة التي تنظر في هذا الملف لن تقرأ قانون الضمان الاجتماعي (SSA) بمعزل عن السياق."
          },
          {
            "level": 2,
            "id": null,
            "text": "النتائج. السجلات التي نطلبها."
          },
          {
            "level": 2,
            "id": null,
            "text": "مذكرة الأدلة — المواد المقدمة من المصدر 1"
          },
          {
            "level": 2,
            "id": null,
            "text": "التعديل الذي أُجري على ملف PDF المُقدَّم هو تعديل شكلي: فالنص المُغطَّى لا يزال قابلاً للاستخراج"
          },
          {
            "level": 2,
            "id": null,
            "text": "مستندات الدعم والمراسلات القانونية"
          },
          {
            "level": 2,
            "id": null,
            "text": "سجلات أولية مختارة"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-01",
            "text": "مفاتيح الأجهزة، التي طُلبت في عام 2016"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-02",
            "text": "تقارير الأعطال التي لا تتضمن خيارًا فعّالًا لرفض الاشتراك"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-03",
            "text": "تم الإبلاغ عن إساءة استخدام تذكرة المصادقة إلى Valve"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-01",
            "text": "44 عملية شراء متنازع عليها في السوق"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-02",
            "text": "حظر دائم وإغلاق باب الاستئناف"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-03",
            "text": "إعادة تعيين عملية الاسترداد وخسارة مُبلغ عنها بقيمة $10,000"
          },
          {
            "level": 2,
            "id": null,
            "text": "ArchiSteamFarm وبند الأتمتة"
          },
          {
            "level": 2,
            "id": null,
            "text": "Rules ledger: clauses against recorded platforms"
          },
          {
            "level": 3,
            "id": "ledger-title",
            "text": "الاستخدام التجاري وفرض الرسوم على الحساب"
          },
          {
            "level": 3,
            "id": "lw-register-title",
            "text": "سجل المنصة 175"
          },
          {
            "level": 4,
            "id": null,
            "text": "عبء الإثبات"
          },
          {
            "level": 4,
            "id": null,
            "text": "ما هو السجل المُعلَّم، وما ليس به"
          },
          {
            "level": 2,
            "id": null,
            "text": "دليل إجراءات DSAR: طلب الأدلة"
          },
          {
            "level": 3,
            "id": null,
            "text": "احتفظ بخطك الزمني."
          },
          {
            "level": 3,
            "id": null,
            "text": "اطلب الحصول على بياناتك المحفوظة."
          },
          {
            "level": 3,
            "id": null,
            "text": "احتفظ بسجل التسليم."
          },
          {
            "level": 3,
            "id": null,
            "text": "قارن بين الردود."
          },
          {
            "level": 3,
            "id": null,
            "text": "أمان الحساب وسجلات الوصول"
          },
          {
            "level": 3,
            "id": null,
            "text": "أي تباين يُعد دليلاً يستدعي التحقيق."
          },
          {
            "level": 2,
            "id": null,
            "text": "حجم الدعم. أوقات الاستجابة المنشورة."
          },
          {
            "level": 3,
            "id": null,
            "text": "طابوران أمام مكتب الدعم الواحد، كما يتضح من 21 لقطة شاشة محفوظة."
          },
          {
            "level": 2,
            "id": null,
            "text": "احسب عدد السجلات. تحقق من النطاق."
          },
          {
            "level": 2,
            "id": null,
            "text": "Valve لا تنشر أي سجلات تتعلق بإنفاذ القانون.\nلقد صنعنا واحدًا."
          }
        ],
        "links": [
          "https://dotesports.com/counter-strike/news/csgo-lounge-billion-bets-3896",
          "https://store.steampowered.com/agreement/?l=english",
          "http://web.archive.org/web/20260921022032/https://store.steampowered.com/agreement/?l=english",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-all-results.json",
          "https://blog.counter-strike.net/expresstrade/",
          "http://web.archive.org/web/20260307161538/https://blog.counter-strike.net/expresstrade/",
          "https://wsgc.wa.gov/news/2016/washington-state-gambling-commission-orders-valve-stop-skins-gambling",
          "http://web.archive.org/web/20260520012601/https://wsgc.wa.gov/news/2016/washington-state-gambling-commission-orders-valve-stop-skins-gambling",
          "https://fr.scribd.com/document/328063293/Valve-s-Oct-18th-response-to-Washington-State-Gambling-Commission-s-cease-and-desist",
          "https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921021947/https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921022628/https://steamcommunity.com/linkfilter/?url=https:%2F%2Frollbit.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rbsnin.com.20260921T021120Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rollbit.com.json",
          "http://web.archive.org/web/20260921022740/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fskin.club",
          "http://web.archive.org/web/20260921022842/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fsc-auth.net",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skin.club.json",
          "http://web.archive.org/web/20260921022603/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fhowl.gg",
          "http://web.archive.org/web/20260921022636/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fhowl.uno",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/howl.gg.json",
          "http://web.archive.org/web/20260921022840/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fduelbits.com",
          "http://web.archive.org/web/20260921022901/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fswitchflips.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/duelbits.com.json",
          "http://web.archive.org/web/20260921022758/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgofast.com",
          "http://web.archive.org/web/20260921022847/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fauthtofast.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgofast.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/farmskins.com.20260921T025840Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/steam.kobal.cc.20260921T025844Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/farmskins.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cobaltlab.tech.20260921T041604Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cobaltauth.com.20260921T041608Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/cobaltlab.tech.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgo.net.20260921T041619Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cn2.easylot.net.20260921T041623Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgo.net.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/ggdrop.com.20260921T041637Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/ggauth.com.20260921T041641Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/ggdrop.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rustchance.com.20260921T041703Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/hgfuihd.com.20260921T041706Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rustchance.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skin.fans.20260921T041710Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.skinfans.com.20260921T041713Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skin.fans.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinport.com.20260921T041724Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinport.app.20260921T041728Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skinport.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skins.cash.20260921T041731Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinscash.live.20260921T041735Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skins.cash.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2hunt.com.20260921T041739Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rstspcl.com.20260921T041742Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tf2hunt.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgogem.com.20260922T192355Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/api.csgem.com.20260922T192358Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-2026-09-22.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/gamdom.com.20260922T192326Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/login.gambldom.com.20260922T192330Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/12cs.fail.20260922T192347Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/fail.games.20260922T192351Z.html",
          "http://web.archive.org/web/20260921022953/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgoempire.com",
          "http://web.archive.org/web/20260921022947/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgoempirelogin4.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgoempire.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cs.money.20260921T021131Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.dota.trade.20260921T021134Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/cs.money.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csfloat.com.20260921T041612Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgofloat.com.20260921T041615Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csfloat.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/g4skins.com.20260921T041630Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.g4s.to.20260921T041634Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/g4skins.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/juice.gg.20260921T041644Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/letmeinjuice.com.20260921T041648Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/juice.gg.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/market.csgo.com.20260921T041652Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2.net.20260921T041655Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/market.csgo.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rust.tm.20260921T041659Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rust.tm.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgolounge.com.20260922T192333Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2.net.20260922T192340Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2lounge.com.20260922T192337Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinbaron.de.20260921T041717Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinbaron.com.20260921T041721Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skinbaron.de.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2royal.com.20260921T041746Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2auth.com.20260921T041750Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tf2royal.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tradeit.gg.20260921T041753Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/connect-tradeit.com.20260921T041757Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tradeit.gg.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/upgrader.pro.20260921T041801Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/upgauth.space.20260921T041804Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/upgrader.pro.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-recheck-2026-09-21.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/domain-registration.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wayback-snapshots.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-2026-09-22c.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/master_registry.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/longitudinal-steam-phishing-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-steam-phishing-100.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-coverage-2026-09-22.json",
          "https://blog.csfloat.com/how-floatdb-tracks-items/",
          "http://web.archive.org/web/20260921022415/https://blog.csfloat.com/how-floatdb-tracks-items/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/platform-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/platforms-removed.json",
          "https://hackerone.com/reports/291750",
          "http://web.archive.org/web/20251116185046/https://hackerone.com/reports/291750",
          "https://hackerone.com/reports/1079561",
          "http://web.archive.org/web/20260924181830/https://hackerone.com/reports/1079561",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/hackerone-reports.json",
          "https://phishdestroy.io/steam_dossier/ar/steam_enforcement_evidence.html#support-records",
          "https://www.darknavy.org/blog/exploiting_steam_usual_and_unusual_ways_in_the_cef_framework/",
          "https://steamcommunity.com/groups/SteamClientBeta/discussions/0/3365901765276206401/",
          "http://web.archive.org/web/20250804051514/https://steamcommunity.com/groups/SteamClientBeta/discussions/0/3365901765276206401/",
          "https://www.chromium.org/developers/design-documents/safebrowsing/",
          "http://web.archive.org/web/20260821101616/https://www.chromium.org/developers/design-documents/safebrowsing/",
          "https://www.chromium.org/developers/how-tos/api-keys/",
          "http://web.archive.org/web/20260830122831/https://www.chromium.org/developers/how-tos/api-keys/",
          "https://github.com/Homebrew/homebrew-cask/issues/193814",
          "https://testsafebrowsing.appspot.com/",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/domain-registration.json",
          "https://phishdestroy.io/steam_dossier/ar/AUTH_AUDIT.md",
          "https://datatracker.ietf.org/doc/rfc6749/",
          "https://docs.cloud.google.com/docs/authentication/api-keys",
          "https://listings.pcisecuritystandards.org/pdfs/PCI_DSS_Resource_Guide_(003).pdf",
          "https://developer.apple.com/news/?id=02202019a",
          "http://web.archive.org/web/20250506070026/https://developer.apple.com/news/?id=02202019a",
          "https://dev.twitch.tv/docs/authentication/validate-tokens/",
          "https://discuss.dev.twitch.com/t/legacy-twitch-api-v5-i-e-kraken-shutdown-reminder-february-28-2022/36589",
          "http://web.archive.org/web/20250127085635/https://discuss.dev.twitch.com/t/legacy-twitch-api-v5-i-e-kraken-shutdown-reminder-february-28-2022/36589",
          "https://store.steampowered.com/news/posts/?enddate=1788390000",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/4123547285514022851",
          "https://skinvault.gg/blog/cs2-trade-protection-explained/",
          "https://csmarketcap.com/blog/market-insights/from-boom-to-bust-cs2s-trade-protection-impact",
          "https://skin.land/blog/steam-changes-cs2-trade-ban-logic-timing/",
          "https://help.steampowered.com/faqs/view/3041-A87A-E5F6-B6AC",
          "https://steamcommunity.com/ogg/593110/announcements/detail/533224478739530146",
          "https://steamcommunity.com/games/CSGO/announcements/detail/4447966961421256740",
          "https://steamcommunity.com/sharedfiles/filedetails/?id=2926756889",
          "https://steamcommunity.com/dev/apikey",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3734103130194459461",
          "https://steamcommunity.com/discussions/forum/1/3807266184852932971/",
          "https://help.steampowered.com/faqs/view/225C-C51E-B8F0-55B2",
          "https://store.steampowered.com/news/group/4/view/3314112260640237775",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/issues/325",
          "https://blog.dota2.com/2020/05/trading-cooldown/",
          "https://blog.counter-strike.net/index.php/2018/03/20308/",
          "http://web.archive.org/web/20250226114333/https://blog.counter-strike.net/index.php/2018/03/20308/",
          "https://phishdestroy.io/steam_dossier/ar/steam_evidence_archive.html",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/493839547938902179",
          "https://store.steampowered.com/online_conduct",
          "http://web.archive.org/web/20260921022120/https://store.steampowered.com/online_conduct",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260918014700/https://store.steampowered.com/subscriber_agreement/",
          "https://steamcommunity.com/dev/apiterms",
          "http://web.archive.org/web/20260921022210/https://steamcommunity.com/dev/apiterms",
          "https://help.steampowered.com/en/faqs/view/628C-E332-BD8C-4D36",
          "https://phishdestroy.io/steam_dossier/ar/social_graph.html",
          "https://phishdestroy.io/steam_dossier/ar/security_timeline.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wsgc-skins-gambling-briefing-2018.pdf",
          "https://wsgc.wa.gov/sites/default/files/2023-10/Skins%20Gambling.pdf",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wsgc-briefing-manifest.json",
          "https://x.com/csgobig",
          "https://www.facebook.com/csgobigofficial/",
          "https://500.casino/",
          "https://csgolounge.com/",
          "https://csgocasino.gg/",
          "https://x.com/CSGOatsecom",
          "https://x.com/CSGOSweep/status/937420902538543106",
          "https://x.com/Wild",
          "https://x.com/csgopot",
          "https://x.com/csgodiamondscom",
          "https://www.ftc.gov/legal-library/browse/cases-proceedings/162-3184-csgo-lotto-matter",
          "https://x.com/CSGODouble",
          "https://x.com/csgo_massive",
          "https://www.facebook.com/csgostrongfree/",
          "https://www.facebook.com/CSNCOM/",
          "https://www.gamblingcommission.gov.uk/report/young-people-and-gambling",
          "https://www.aph.gov.au/Parliamentary_Business/Committees/Senate/Environment_and_Communications/Gamingmicro-transactions",
          "https://phishdestroy.io/steam_dossier/ar/elite_skins.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/csfloat-catalogue.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/skinport-floor-over-cap.json",
          "https://pricempire.com/cs2-marketplaces",
          "http://web.archive.org/web/20260921022459/https://pricempire.com/cs2-marketplaces",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/priceempire-marketplaces.json",
          "https://www.steamanalyst.com/marketplace",
          "http://web.archive.org/web/20260719014552/https://www.steamanalyst.com/marketplace",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-atlas.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json",
          "https://phishdestroy.io/steam_dossier/ar/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/ar/steam_enforcement_evidence.html#case-support-recovery",
          "https://top10.owasp.org/2025/A01_2025-Broken_Access_Control/",
          "http://web.archive.org/web/20260920212535/https://top10.owasp.org/2025/A01_2025-Broken_Access_Control/",
          "https://store.steampowered.com/privacy_agreement/",
          "http://web.archive.org/web/20260921021648/https://store.steampowered.com/privacy_agreement/",
          "https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "http://web.archive.org/web/20250818113925/https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "https://www.dexerto.com/counter-strike-2/valve-saves-hacked-cs2-player-threatened-with-ransom-over-300000-of-rare-stickers-3283135/",
          "https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "http://web.archive.org/web/20220702042821/https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "https://www.kaspersky.com/blog/cs-go-two-million-usd-inventory-hack/44697/",
          "https://esportfire.com/article/the-2-million-usd-csgo-hack-22062022",
          "http://web.archive.org/web/20260515110250/https://esportfire.com/article/the-2-million-usd-csgo-hack-22062022",
          "https://esportsbetting.com/valve-deletes-130000-stolen-dragon-lore/",
          "https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "http://web.archive.org/web/20251115173120/https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "https://vkplay.ru/media/news/bloger-rasskazal-kak-podderzhka-steam-vorovala-akkaunty-igrokov/",
          "https://lis-skins.com/ru/blog/krupneisaia-mosenniceskaia-sxema-v-istorii-steam/",
          "https://escorenews.com/ru/csgo/news/44056-sotrudniki-podderjki-steam-zanimalis-krajey-skinov-s-akkauntov-za-god-oni-zarabotali-svyshe-300-tysyach-dollarov",
          "https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "http://web.archive.org/web/20250805141942/https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/outsourcing-archive-records.json",
          "https://community.skin.club/en/news/collector-has-steam-inventory-returned-after-bold-hack",
          "https://esportfire.com/article/300k-scam-full-katowice-2014-holo-collection-hacked",
          "http://web.archive.org/web/20251217072445/https://esportfire.com/article/300k-scam-full-katowice-2014-holo-collection-hacked",
          "https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng",
          "http://web.archive.org/web/20260920024236/https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng",
          "https://ag.ny.gov/press-release/2026/attorney-general-james-sues-game-developer-promoting-illegal-gambling-through",
          "http://web.archive.org/web/20260901015430/https://ag.ny.gov/press-release/2026/attorney-general-james-sues-game-developer-promoting-illegal-gambling-through",
          "https://www.fincen.gov/sites/default/files/2019-05/FinCEN%20CVC%20Guidance%20FINAL.pdf",
          "http://web.archive.org/web/20250711185007/https://www.fincen.gov/sites/default/files/2019-05/FinCEN%20CVC%20Guidance%20FINAL.pdf",
          "https://eur-lex.europa.eu/legal-content/EN/LSU/?uri=CELEX:32018L1673",
          "https://eur-lex.europa.eu/eli/dir/2024/1640/oj/eng",
          "http://web.archive.org/web/20260830153004/https://eur-lex.europa.eu/eli/dir/2024/1640/oj/eng",
          "https://eur-lex.europa.eu/eli/reg/2022/2065/oj/eng",
          "http://web.archive.org/web/20260920080125/https://eur-lex.europa.eu/eli/reg/2022/2065/oj/eng",
          "https://phishdestroy.io/steam_dossier/ar/legal_analysis.html",
          "https://partner.steamgames.com/doc/features/auth#website",
          "http://web.archive.org/web/20260921022335/https://partner.steamgames.com/doc/features/auth",
          "https://www.ftc.gov/legal-library/browse/rules/childrens-online-privacy-protection-rule-coppa",
          "http://web.archive.org/web/20260921070051/https://www.ftc.gov/legal-library/browse/rules/childrens-online-privacy-protection-rule-coppa",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/gdpr-ticket-1.png",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/screenshot-manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/gdpr-ticket-2.png",
          "https://datenschutz.hamburg.de/beschwerde",
          "https://edpb.europa.eu/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/regulatory-review/disclosure-audit.json",
          "https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "http://web.archive.org/web/20260821155801/https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "https://phishdestroy.io/steam_dossier/ar/index#exhibit-gallery-section",
          "https://github.com/ValveSoftware/steam-for-linux/issues/4521",
          "https://phishdestroy.io/steam_dossier/ar/steam_evidence_archive.html?source=GitHub&record=484",
          "https://github.com/ValveSoftware/steam-for-linux/issues/6459",
          "http://web.archive.org/web/20260419051343/https://github.com/ValveSoftware/steam-for-linux/issues/6459",
          "https://phishdestroy.io/steam_dossier/ar/steam_evidence_archive.html?source=GitHub&record=467",
          "https://github.com/ValveSoftware/Source-1-Games/issues/3857",
          "https://phishdestroy.io/steam_dossier/ar/steam_evidence_archive.html?source=GitHub&record=768",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "http://web.archive.org/web/20250320082450/https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://phishdestroy.io/steam_dossier/ar/steam_evidence_archive.html?source=Reddit&record=4533",
          "https://www.reddit.com/r/ohnePixel/comments/1hahqx2/permanently_banned_steam_account_without_a_clear/",
          "https://phishdestroy.io/steam_dossier/ar/steam_evidence_archive.html?source=Reddit&record=4766",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://phishdestroy.io/steam_dossier/ar/steam_evidence_archive.html?source=Reddit&record=4592",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/selected-evidence-records.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive_manifest.json",
          "https://phishdestroy.io/steam_dossier/ar/card_economy.html",
          "https://github.com/JustArchiNET/ArchiSteamFarm/wiki/FAQ",
          "https://phishdestroy.io/steam_dossier/ar/card_economy.html#scale",
          "https://phishdestroy.io/steam_dossier/ar/card_economy.html#licence",
          "https://phishdestroy.io/steam_dossier/ar/enforcement_audit.html",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "http://web.archive.org/web/20260924181709/https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://rdap.verisign.com/com/v1/domain/csgoempire.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoempire.com",
          "https://rdap.verisign.com/com/v1/domain/csgoempirelogin4.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/csgoempire.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustreaper.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustreaper.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/rustreaper.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustly.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustly.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/rustly.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgofast.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgofast.com",
          "https://rdap.verisign.com/com/v1/domain/authtofast.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/csgofast.com.json",
          "https://rdap.verisign.com/com/v1/domain/duelbits.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fduelbits.com",
          "https://rdap.verisign.com/com/v1/domain/switchflips.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/duelbits.com.json",
          "https://rdap.verisign.com/com/v1/domain/farmskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffarmskins.com",
          "https://tld-rdap.verisign.com/cc/v1/domain/kobal.cc",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/farmskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoluck.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoluck.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/csgoluck.com.json",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/domain-registry/insane.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Finsane.gg",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/insane.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs2skin.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs2skin.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/cs2skin.com.json",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/domain-registry/juice.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fjuice.gg",
          "https://rdap.verisign.com/com/v1/domain/letmeinjuice.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/juice.gg.json",
          "https://rdap.verisign.com/com/v1/domain/ggdrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fggdrop.com",
          "https://rdap.verisign.com/com/v1/domain/ggauth.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/ggdrop.com.json",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/domain-registry/howl.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhowl.gg",
          "https://rdap.radix.host/rdap/domain/howl.uno",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/howl.gg.json",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/domain-registry/chicken.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fchicken.gg",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/chicken.gg.json",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/domain-registry/csgocasino.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgocasino.gg",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/csgocasino.gg.json",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/domain-registry/hunt.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhunt.gg",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/hunt.gg.json",
          "https://rdap.verisign.com/com/v1/domain/csbattle.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsbattle.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/csbattle.com.json",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/domain-registry/skinrave.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinrave.gg",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/skinrave.gg.json",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/domain-registry/csdouble.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsdouble.gg",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/csdouble.gg.json",
          "https://rdap.verisign.com/com/v1/domain/rustchance.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustchance.com",
          "https://rdap.verisign.com/com/v1/domain/hgfuihd.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/rustchance.com.json",
          "https://rdap.radix.host/rdap/domain/cobaltlab.tech",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcobaltlab.tech",
          "https://rdap.verisign.com/com/v1/domain/cobaltauth.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/cobaltlab.tech.json",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/domain-registry/raided.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fraided.gg",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/raided.gg.json",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/domain-registry/rustneo.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustneo.gg",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/rustneo.gg.json",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/domain-registry/splits.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsplits.gg",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/splits.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/upgrader.pro",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fupgrader.pro",
          "https://rdap.radix.host/rdap/domain/upgauth.space",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/upgrader.pro.json",
          "https://rdap.centralnic.com/fans/domain/skin.fans",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.fans",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/skin.fans.json",
          "https://rdap.nic.one/domain/hotpizza.one",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhotpizza.one",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/hotpizza.one.json",
          "https://rdap.verisign.com/com/v1/domain/g4skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg4skins.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/g4skins.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2royal.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2royal.com",
          "https://rdap.verisign.com/com/v1/domain/tf2auth.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/tf2royal.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2hunt.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2hunt.com",
          "https://rdap.verisign.com/com/v1/domain/rstspcl.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/tf2hunt.com.json",
          "https://rdap.identitydigital.services/rdap/domain/tf2.bet",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2.bet",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/tf2.bet.json",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/domain-registry/openstars.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fopenstars.gg",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/openstars.gg.json",
          "https://rdap.verisign.com/com/v1/domain/skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/skins.com.json",
          "https://rdap.identitydigital.services/rdap/domain/white.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwhite.market",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/white.market.json",
          "https://rdap.identitydigital.services/rdap/domain/moon.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmoon.market",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/moon.market.json",
          "https://rdap.verisign.com/com/v1/domain/csfloat.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsfloat.com",
          "https://rdap.verisign.com/com/v1/domain/csgofloat.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/csfloat.com.json",
          "https://rdap.identitydigital.services/rdap/domain/skin.land",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.land",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/skin.land.json",
          "https://rdap.verisign.com/com/v1/domain/haloskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhaloskins.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/haloskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/163.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuff.163.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/buff.163.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmarket.csgo.com",
          "https://rdap.verisign.com/net/v1/domain/dota2.net",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/market.csgo.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinport.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinport.com",
          "https://pubapi.registry.google/rdap/domain/skinport.app",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/skinport.com.json",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/domain-registry/skinflow.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinflow.gg",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/skinflow.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/skin.place",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.place",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/skin.place.json",
          "https://rdap.verisign.com/com/v1/domain/skinsmonkey.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinsmonkey.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/skinsmonkey.com.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbaron.de",
          "https://rdap.verisign.com/com/v1/domain/skinbaron.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/skinbaron.de.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frust.tm",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/rust.tm.json",
          "https://rdap.verisign.com/com/v1/domain/pirateswap.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fpirateswap.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/pirateswap.com.json",
          "https://rdap.radix.host/rdap/domain/mannco.store",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmannco.store",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/mannco.store.json",
          "https://rdap.verisign.com/com/v1/domain/skinswap.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinswap.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/skinswap.com.json",
          "https://rdap.verisign.com/com/v1/domain/exeskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fexeskins.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/exeskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/balticskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbalticskins.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/balticskins.com.json",
          "https://rdap.nic.trade/domain/cs.trade",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.trade",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/cs.trade.json",
          "https://rdap.verisign.com/com/v1/domain/rapidskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frapidskins.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/rapidskins.com.json",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/domain-registry/tradeit.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftradeit.gg",
          "https://rdap.verisign.com/com/v1/domain/connect-tradeit.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/tradeit.gg.json",
          "https://rdap.verisign.com/com/v1/domain/49skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F49skins.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/49skins.com.json",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/domain-registry/skinvault.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinvault.gg",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/skinvault.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/aim.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Faim.market",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/aim.market.json",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/domain-registry/skinout.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinout.gg",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/skinout.gg.json",
          "https://rdap.verisign.com/com/v1/domain/ntskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fntskins.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/ntskins.com.json",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/domain-registry/gamerpay.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamerpay.gg",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/gamerpay.gg.json",
          "https://rdap.nic.tf/domain/scrap.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fscrap.tf",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/scrap.tf.json",
          "https://rdap.nic.tf/domain/marketplace.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmarketplace.tf",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/marketplace.tf.json",
          "https://rdap.identitydigital.services/rdap/domain/skins.cash",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.cash",
          "https://rdap.identitydigital.services/rdap/domain/skinscash.live",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/skins.cash.json",
          "https://rdap.verisign.com/net/v1/domain/csgo.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo.net",
          "https://rdap.verisign.com/net/v1/domain/easylot.net",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/csgo.net.json",
          "https://rdap.verisign.com/net/v1/domain/cybershoke.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcybershoke.net",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/cybershoke.net.json",
          "https://rdap.verisign.com/net/v1/domain/fastcup.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffastcup.net",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/fastcup.net.json",
          "https://rdap.verisign.com/com/v1/domain/leetify.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fleetify.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/leetify.com.json",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/domain-registry/scope.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fscope.gg",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/scope.gg.json",
          "https://rdap.verisign.com/com/v1/domain/tradeupspy.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftradeupspy.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/tradeupspy.com.json",
          "https://rdap.identitydigital.services/rdap/domain/cs.deals",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.deals",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/cs.deals.json",
          "https://rdap.verisign.com/com/v1/domain/pricempire.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fpricempire.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/pricempire.com.json",
          "https://rdap.identitydigital.services/rdap/domain/lzt.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flzt.market",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/lzt.market.json",
          "https://rdap.verisign.com/com/v1/domain/z2u.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fz2u.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/z2u.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoroll.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoroll.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/csgoroll.com.json",
          "https://rdap.verisign.com/com/v1/domain/rollbit.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frollbit.com",
          "https://rdap.verisign.com/com/v1/domain/rbsnin.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/rollbit.com.json",
          "https://rdap.identitydigital.services/rdap/domain/500.casino",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F500.casino",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/500.casino.json",
          "https://rdap.verisign.com/com/v1/domain/csgobig.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgobig.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/csgobig.com.json",
          "https://rdap.verisign.com/com/v1/domain/casedrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcasedrop.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/casedrop.com.json",
          "https://rdap.verisign.com/com/v1/domain/banditcamp.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbanditcamp.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/banditcamp.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinbox.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbox.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/skinbox.com.json",
          "https://rdap.verisign.com/com/v1/domain/tastydrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftastydrop.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/tastydrop.com.json",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/domain-registry/csgopolygon.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgopolygon.gg",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/csgopolygon.gg.json",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/domain-registry/magicdrop.ru.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmagicdrop.ru",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/magicdrop.ru.json",
          "https://rdap.verisign.com/com/v1/domain/csdice.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsdice.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/csdice.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinodds.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinodds.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/skinodds.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgowin.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgowin.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/csgowin.com.json",
          "https://rdap.verisign.com/net/v1/domain/csgorun.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgorun.net",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/csgorun.net.json",
          "https://rdap.verisign.com/com/v1/domain/openskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fopenskins.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/openskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustbet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustbet.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/rustbet.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgomagic.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgomagic.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/csgomagic.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgobounty.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgobounty.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/csgobounty.com.json",
          "https://rdap.verisign.com/com/v1/domain/ezskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fezskins.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/ezskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustcases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustcases.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/rustcases.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoreaper.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoreaper.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/csgoreaper.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgocases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgocases.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/csgocases.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo-skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo-skins.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/csgo-skins.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgonet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgonet.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/csgonet.com.json",
          "https://rdap.verisign.com/com/v1/domain/wtfskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwtfskins.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/wtfskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/flamecases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fflamecases.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/flamecases.com.json",
          "https://rdap.verisign.com/com/v1/domain/gamedom.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamedom.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/gamedom.com.json",
          "https://rdap.nic.club/domain/skin.club",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.club",
          "https://rdap.verisign.com/net/v1/domain/sc-auth.net",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/skin.club.json",
          "https://rdap.verisign.com/com/v1/domain/daddyskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdaddyskins.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/daddyskins.com.json",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/domain-registry/rustix.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustix.gg",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/rustix.gg.json",
          "https://rdap.nic.club/domain/skins.club",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.club",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/skins.club.json",
          "https://rdap.publicinterestregistry.org/rdap/domain/csgohouse.org",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgohouse.org",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/csgohouse.org.json",
          "https://rdap.verisign.com/net/v1/domain/skinrave.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinrave.net",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/skinrave.net.json",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/domain-registry/bloodycase.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbloodycase.gg",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/bloodycase.gg.json",
          "https://rdap.verisign.com/com/v1/domain/csgoclicker.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoclicker.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/csgoclicker.com.json",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/domain-registry/rustbet.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustbet.gg",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/rustbet.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs-drop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs-drop.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/cs-drop.com.json",
          "https://rdap.verisign.com/net/v1/domain/hellstore.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhellstore.net",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/hellstore.net.json",
          "https://rdap.verisign.com/com/v1/domain/rustloot.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustloot.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/rustloot.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo-case.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo-case.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/csgo-case.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgogem.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgogem.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/csgogem.com.json",
          "https://rdap.verisign.com/com/v1/domain/rainbet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frainbet.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/rainbet.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustclash.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustclash.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/rustclash.com.json",
          "https://rdap.identitydigital.services/rdap/domain/12cs.fail",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F12cs.fail",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/12cs.fail.json",
          "https://rdap.verisign.com/com/v1/domain/tf2easy.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwww.tf2easy.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/tf2easy.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2blaze.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2blaze.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/tf2blaze.com.json",
          "https://rdap.verisign.com/com/v1/domain/shuffle.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fshuffle.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/shuffle.com.json",
          "https://rdap.identitydigital.services/rdap/domain/buff.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuff.market",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/buff.market.json",
          "https://rdap.identitydigital.services/rdap/domain/avan.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Favan.market",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/avan.market.json",
          "https://rdap.identitydigital.services/rdap/domain/cs.money",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.money",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/cs.money.json",
          "https://rdap.verisign.com/com/v1/domain/uuskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fuuskins.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/uuskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/youpin898.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fyoupin898.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/youpin898.com.json",
          "https://rdap.verisign.com/com/v1/domain/c5game.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fc5game.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/c5game.com.json",
          "https://rdap.verisign.com/com/v1/domain/waxpeer.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwaxpeer.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/waxpeer.com.json",
          "https://rdap.verisign.com/com/v1/domain/dmarket.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdmarket.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/dmarket.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamcommunity.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamcommunity.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/steamcommunity.com.json",
          "https://rdap.verisign.com/com/v1/domain/lootfarm.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flootfarm.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/lootfarm.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustskins.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/rustskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/krakatoa.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fkrakatoa.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/krakatoa.com.json",
          "https://rdap.verisign.com/com/v1/domain/shadowpay.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fshadowpay.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/shadowpay.com.json",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/domain-registry/igxe.cn.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Figxe.cn",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/igxe.cn.json",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/domain-registry/swap.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fswap.gg",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/swap.gg.json",
          "https://rdap.verisign.com/com/v1/domain/bitskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbitskins.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/bitskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2mart.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2mart.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/tf2mart.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinbid.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbid.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/skinbid.com.json",
          "https://rdap.verisign.com/com/v1/domain/lootbear.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flootbear.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/lootbear.com.json",
          "https://rdap.nic.tf/domain/backpack.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbackpack.tf",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/backpack.tf.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fstntrading.eu",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/stntrading.eu.json",
          "https://rdap.verisign.com/com/v1/domain/skinwallet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinwallet.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/skinwallet.com.json",
          "https://rdap.verisign.com/com/v1/domain/dota2market.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdota2market.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/dota2market.com.json",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/domain-registry/xplay.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fxplay.gg",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/xplay.gg.json",
          "https://rdap.verisign.com/com/v1/domain/esportal.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fesportal.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/esportal.com.json",
          "https://rdap.registro.br/domain/gamersclub.com.br",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamersclub.com.br",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/gamersclub.com.br.json",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/domain-registry/epidemic.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fepidemic.gg",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/epidemic.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs2stash.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs2stash.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/cs2stash.com.json",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/domain-registry/csgoskins.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoskins.gg",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/csgoskins.gg.json",
          "https://rdap.verisign.com/com/v1/domain/steamanalyst.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamanalyst.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/steamanalyst.com.json",
          "https://rdap.verisign.com/net/v1/domain/steamcardexchange.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamcardexchange.net",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/steamcardexchange.net.json",
          "https://rdap.verisign.com/com/v1/domain/dotabuff.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdotabuff.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/dotabuff.com.json",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/domain-registry/tracker.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftracker.gg",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/tracker.gg.json",
          "https://rdap.verisign.com/com/v1/domain/funpay.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffunpay.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/funpay.com.json",
          "https://rdap.verisign.com/com/v1/domain/playerauctions.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fplayerauctions.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/playerauctions.com.json",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/domain-registry/eldorado.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Feldorado.gg",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/eldorado.gg.json",
          "https://rdap.verisign.com/com/v1/domain/g2a.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg2a.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/g2a.com.json",
          "https://rdap.verisign.com/net/v1/domain/kinguin.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fkinguin.net",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/kinguin.net.json",
          "https://rdap.verisign.com/com/v1/domain/g2g.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg2g.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/g2g.com.json",
          "https://rdap.verisign.com/com/v1/domain/playerup.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fplayerup.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/playerup.com.json",
          "https://rdap.verisign.com/net/v1/domain/smurfhub.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfhub.net",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/smurfhub.net.json",
          "https://rdap.verisign.com/com/v1/domain/smurfaccounts.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfaccounts.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/smurfaccounts.com.json",
          "https://rdap.verisign.com/com/v1/domain/buycsgorank.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuycsgorank.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/buycsgorank.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgosmurfkings.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgosmurfkings.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/csgosmurfkings.com.json",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/domain-registry/smurfstore.co.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfstore.co",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/smurfstore.co.json",
          "https://rdap.verisign.com/com/v1/domain/steamlvlup.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlvlup.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/steamlvlup.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamlevels.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlevels.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/steamlevels.com.json",
          "https://rdap.verisign.com/com/v1/domain/levelsteam.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flevelsteam.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/levelsteam.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamlevelu.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlevelu.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/steamlevelu.com.json",
          "https://rdap.verisign.com/com/v1/domain/eloking.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Feloking.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/eloking.com.json",
          "https://rdap.publicinterestregistry.org/rdap/domain/boosteria.org",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fboosteria.org",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/boosteria.org.json",
          "https://rdap.verisign.com/com/v1/domain/overgear.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fovergear.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/overgear.com.json",
          "https://rdap.verisign.com/com/v1/domain/blazingboost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fblazingboost.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/blazingboost.com.json",
          "https://rdap.verisign.com/com/v1/domain/dota2boost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdota2boost.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/dota2boost.com.json",
          "https://rdap.verisign.com/com/v1/domain/buyboost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuyboost.com",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit/buyboost.com.json",
          "https://phishdestroy.io/steam_dossier/ar/steam_tos_assets/auth-route-audit.json",
          "https://help.steampowered.com/en/faqs/view/365F-4BEE-2AE2-7BDD",
          "https://store.steampowered.com/privacy_agreement/#8",
          "https://www.edpb.europa.eu/system/files/2023-04/edpb_guidelines_202201_data_subject_rights_access_v2_en.pdf",
          "https://web.archive.org/web/20260810154631/https://store.steampowered.com/stats/support",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/design-review/part2/measurements.json",
          "https://phishdestroy.io/steam_dossier/ar/VALVE_EVIDENCE_PACK/databases/TOTAL_VALVE_SCANDALS_MASTER_DB.csv",
          "https://phishdestroy.io/steam_dossier/ar/license_disclaimer.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ar/index.content.json",
      "export_json_sha256": "9f24dcc868d350be6778325658a4882d5d533c55bc9efdd8c7da50155d63e56b"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ar/investigation_part2.html",
      "language": "ar",
      "title": "الوصول إلى الحساب والمساءلة — ملف Steam",
      "source_url": "https://phishdestroy.io/steam_dossier/ar/investigation_part2",
      "source_html_sha256": "c7e791117221ef755e9dcf2878ad5deb22e17b80d12fb02deda6d18572ddf67d",
      "exported_at": "2026-09-29T00:20:03.275Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "investigation_part2.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ar/investigation_part2.pdf?v=print-20260929-v5",
        "sha256": "56c83cd0eb823f7ee50885a683c63adc9d9092eec46d87fa024a2521a82bef7d",
        "bytes": 169724,
        "pages": 8
      },
      "integrity": {
        "signed_object": "investigation_part2.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "investigation_part2.content.json.asc",
        "digest_file": "investigation_part2.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify investigation_part2.content.json.asc investigation_part2.content.json",
          "sha256sum -c investigation_part2.content.json.sha256"
        ]
      },
      "content": {
        "text": "ملف «ستيم» / II\n\nحسابك.وصولهم.من الذي يرد؟\n\nالأتمتة العامة. الدعم المُعهد إلى جهات خارجية. والناس هم من يتحملون التكاليف.\n\nتابعوا البنية التحتية، والخسائر المُبلغ عنها، والوثائق التي تستند إليها المطالبات.\n\nتتبع البنية التحتية ↘\nالمرفق رقم 01 / المراقبة المباشرة لسوق الظل550,000+\n\nSteam حسابات معروضة للبيع حاليًا على FSB Market (اسم مستعار؛ الاسم الأصلي غير مذكور هنا)\nفي هذه اللحظة بالذات\n\n550,000+ المخزون الحالي · 231,829 في مجموعة البيانات التاريخية المستخرجة (198,320 سجلات برنامج «ستيلر»)\n\nالمركز الرئيسي السري لتبادل المعلومات المتعلقة بالحسابات المختطفة Steam، FSB Market (أسماء أخرى مرتبطة غير مذكورة)، تقوم بالتحقق من هوية كل من المشترين والبائعين باستخدام معرّف OpenID الرسمي Steam الخاص بـ Valve (openid.realm = https://FSB Market). في أي لحظة من اللحظات، يُعرض للبيع بنشاط أكثر من نصف مليون حساب مسروق أو مخترق (سجلات سرقة من RedLine/Lumma، وحسابات تم الحصول عليها عن طريق التصيد الاحتيالي، وهجمات «حشو بيانات الاعتماد») مقابل أجر زهيد ($0.50–$2.00). ولا FSB Market ولا المنتدى المرتبط تم حظره بواسطة «مرشح الروابط» الخاص بـ Valve. هذا هو «الخزان الصناعي» الذي يزود حسابات الروبوتات المدفوعة 63.06% التي يقوم Valve بحظرها دون تقديم أي مساعدة للضحية.\n\nبيانات إنتل المباشرة: مراقبة سوق الظل (أكثر من 550 ألف متابع مباشر) ↗ · فتح سجل التسجيل ↗ · فتح تتبع مرشح الارتباط ↗أكثر من 550 ألف متابع مباشر\n\n01 / منظومة تضم مؤلفين\n\nلقد أدت الأتمتة إلىسلسلة من المستندات.\n\nالمشاريع المحددة. القدرات المنشورة. تتبع أداة ما حتى تصل إلى وثائقها، ثم افحص العلاقات التي تم جمعها بين المطورين.\n\n252المستودعات التي تم جمعها\n3,320ملفات تعريف GITHUB\n4,214الملف الشخصي – أزواج المستودعات\nValve البنية التحتيةالمكتبات المجتمعيةالتطبيقات القابلة لإعادة الاستخدام\nتُظهر الخطوط عمليات الدمج أو التبعيات الموثقة. حدد عقدة ما لتتبع الأدلة المتعلقة بها.\n\nأتمتة إدارة الحسابات المتعددة / JustArchiNET\n\nArchiSteamFarm\n\nيعلن المشروع صراحةً عن إمكانية تجميع البطاقات بشكل متزامن عبر حسابات Steam. ويشير ملف المشروع إلى وجود تبعية لـ SteamKit2.\n\nاقرأ الوثائق الخاصة بالمشروع ↗\n\nSteamKit → ArchiSteamFarm\nالتبعية المعلنة ↗\n\nعلاقات مجمعة\n\n40 تسميات المساهمين · 40 ملصقات فوركر\n\nفيما يلي مثال على المساهمين. تصف هذه العلامات العلاقة مع المستودع، وليس علاقة العمل أو الموافقة.\n\n@JustArchi@renovate[روبوت]@JustArchi-ArchiBot@dependabot-preview[بوت]@renovate-bot@actions-user@dependabot-support@Abrynos\nما الذي يوضحه الرسم البياني الخاص بالمطور\n\nيُظهر الرسم البياني العلاقات المنشورة بين المساهمين ومُنشئي الفروع في المشاريع المذكورة وملفات تعريف GitHub. وهذه سجلات عامة — عمليات إنشاء فروع للمستودعات، وقوائم المساهمات، والارتباطات بين ملفات التعريف. والسؤال هو: ما الذي يتطلبه السجل المكتوب للقدرات المنشورة وعلاقات المطورين من Valve للإجابة عليه، وليس ما الذي توصلت إليه هذه الدراسة. يتم حفظ تجزئات الملفات المصدرية في تحديد مصدر الخريطة.\n\nاستكشف الشبكة بالكامل ↗بيانات مصدر المستودع ↓\n\n02 / صلاحيات مختلفة. قوى مختلفة.\n\nأي مفتاحعن ماذا نتحدث؟\n\nلا يتطلب لعب إحدى الألعاب من اللاعب إصدار مفتاح API ويب شخصي. وهذا هو الفرق الجوهري الذي يمثل محور هذا الاستفسار.\n\n01 / حساب المستخدم\nمفتاح واجهة برمجة التطبيقات (API) الشخصي للموقع الإلكتروني\nsteamcommunity.com/dev/apikey\n\nيتم إصدارها من حساب مستخدم لإجراء مكالمات واجهة برمجة التطبيقات (API) المسموح بها. ويُعد إنشاء المفاتيح، وإمكانية رؤيتها، وإلغاؤها، وكشف إساءة استخدامها من بين مسائل أمن الحساب.\n\n02 / البنية الخلفية للعبة\nمفتاح واجهة برمجة تطبيقات الويب الخاصة بالناشر\n\nيستخدم شركاء Steamworks بيانات اعتماد الناشر لإجراء العمليات الخلفية المدعومة، بما في ذلك الخدمات المتعلقة بالألعاب. أما المفتاح الشخصي للاعب فهو بيانات اعتماد مختلفة.\n\n03 / الهوية والجلسة\nOpenID / رموز الجلسة\n\nتقوم OpenID بالتحقق من الهوية أمام موقع ويب. أما رمز الجلسة أو رمز التحديث Steam، فيخدم غرضًا مختلفًا. ولا ينبغي تقديم هاتين الآليتين على أنهما «مفتاح API» واحد قابل للاستبدال.\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\nValve يوثق مفاتيح واجهة برمجة التطبيقات (Web API) لكل من المستخدم والناشر. وبالتالي، فإن واجهة برمجة التطبيقات (Web API) بأكملها ليست منفصلة عن Steamworks. وثائق مفتاح واجهة برمجة التطبيقات (API) ↗ محفوظ 2026-09-15 ↗ · المصادقة أثناء جلسة اللعب ↗ محفوظ 2026-08-29 ↗\n\nتم توثيقه بواسطة مؤلف الأداة / مارس 2024\n\nيمكن أن تستخدم الأتمتة أكثر من مفتاح واجهة برمجة التطبيقات (API).\n\nتصف صفحة الويكي الخاصة بـ «Trade Offer Manager» استخدام رمز وصول الجلسة (session access token) لأجزاء من واجهة برمجة التطبيقات (Web API) في حالة عدم وجود مفتاح API منفصل. كما تتضمن معلومات حول عملية التأكيد عبر الهاتف المحمول لإنشاء المفتاح اعتبارًا من أواخر عام 2023. ويشير المسؤول عن الصيانة إلى أن استخدام الرمز بهذه الطريقة غير مدعوم من قِبل Valve؛ وهذا ادعاء قديم ورد في الوثائق، وليس اختبارًا فعليًّا للتحايل.\n\nWhat this means — session, access and refresh tokens\n\nAfter a successful sign-in the client is handed a token instead of keeping the password — an access token to act with, and a refresh token to obtain new ones. The practical consequence runs through this investigation: whoever holds a valid token does not need the password, and does not need the Steam Guard code either, because both were already spent to obtain it.\n\nSection 5 — the pre-2023 key architecture →\n\nاطلع على توضيح المسؤول عن الصيانة ↗ محفوظ 2026-09-24 ↗\n\nالجانب الإنساني / مسار توضيحي لعملية التصيد الاحتيالي\n\nما زال يلعب.تم الكشف عنها بالفعل.\n\nرسالة من صديق. طلب للتصويت. صفحة «شكرًا». بالنسبة للاعب، تكون المهمة قد انتهت. لكن الجلسة المخترقة قد تستمر إلى ما بعد تلك اللحظة.\n\nعلى شاشة المشغل\n\nF\nرواية أحد الأصدقاء\n\n\"هل يمكنك التصويت لصالح فريقنا؟\"\n\nيصل الطلب عبر دردشة Steam من حساب مألوف. في هذه الحالة، تُفتح الصفحة المرتبطة في متصفح العميل.\n\nبعيدًا عن الأنظار\n\nالثقة تسبق إنشاء الموقع الإلكتروني.\n\nيمكن أن يضفي حساب صديق تم اختراقه مصداقية على رابط التصيد الاحتيالي. ولا تُثبت واجهة Steam المحيطة بالموقع الإلكتروني الوجهة.\n\nمرسل معروف / وجهة خارجية\nأمن الحساب هو الأمر الأهم قبل بيع أي منتج.\n\nلم يكن الهدف من اللاعب إنشاء بيانات اعتماد آلية أو تفويض التحكم. والعودة إلى اللعبة لا تُعد دليلاً على أن الحساب آمن. يحتفظ Valve بسجلات الجلسات، وسجل إنشاء مفتاح واجهة برمجة التطبيقات (API)، وبيانات ربط الأجهزة. أما الضحية فلا تمتلك أيًّا من ذلك. وهذا التباين هو جوهر مشكلة المساءلة.\n\nالوصول إلى الجلسات وأنواع بيانات الاعتماد\n\nيُعد مفتاح واجهة برمجة التطبيقات (API) وجلسة تسجيل الدخول بيانات اعتماد منفصلة ذات صلاحيات مختلفة. ولا تؤدي إلغاء صلاحية المفتاح إلى إنهاء الجلسة النشطة. تصف الوثائق الخاصة بـ Valve كلا الأمرين؛ بينما تحتفظ Valve بالسجلات التي من شأنها أن تُظهر أي من بيانات الاعتماد كان نشطًا وقت وقوع أي إجراء موضع نزاع. المطلب هو الكشف عن ذلك السجل — وليس استنتاجًا اختلقته التحقيقات. وثائق المسؤول عن الصيانة بشأن التعامل مع الرموز ↗ محفوظ 2026-09-24 ↗ · Valve الوثائق الأساسية ↗ محفوظ 2026-09-15 ↗\n\n03 / السوق الرسمية لها سقف\n\nقد يكون هذا العنصر نادرًا.الحد لا يزال ساريًا.\n\nلا يمكن تحقيق سعر يتجاوز الحد الأقصى المحدد للإدراج من خلال إدراج واحد في «سوق المجتمع» بهذا السعر الكامل.\n\nسعر الطلب الإرشادي$5,000تغيير السعر المطلوب للبند\n$100$20,000\n\nمثال توضيحي للحد المنشور، وليس تقييمًا أو توصية بالتداول.\n\nالحد الأقصى لعدد الإدراجات≈ $1,800\nغطاء المحفظة≈ $2,000\n\nتجاوز الحد الأقصى المعلن للإدراج.\n\nلا يمكن سحب الأموال الموجودة في المحفظة إلى حساب مصرفي. وتؤدي هذه القيود إلى ظهور طلب تلبيه أسواق السكين التابعة لأطراف ثالثة: وهو طلب تنشئه حدود الإدراج وحدود المحفظة، في حين أن قواعد Valve نفسها تمنع المشغلين التجاريين من تلبيته.\n\nحدود السوق لـ Steam ↗ محفوظ 2026-09-21 ↗\n\n04 / داخل حدود الدعم\n\nنحن نحمل مسؤولية حماية البيانات.مسؤول عن منح حق الوصول.\n\nتنص سياسة الخصوصية الخاصة بـ Valve صراحةً على مشاركة البيانات الشخصية مع مقدمي خدمات الدعم من الأطراف الثالثة، حسبما تقتضيه الحاجة لتقديم الدعم.\n\nاللاعبالحساب والأدلة\n→\nصمامعملية التعافي\n→\nمقدم الدعمالوصول المفوض\n\nسياسة الخصوصية، البند 5.2 ↗ · تسمح السياسة الخاصة بشركة Valve للطرف الثالث بالوصول لأغراض الدعم. والأسئلة التي لا تزال مطروحة هي: ما هي الأذونات التي تم منحها، وما هي سجلات التدقيق المتوفرة، وماذا حدث عندما زُعم إساءة استخدام هذا الوصول؟\n\n2015\nكان الميزان متاحًا للجمهور\n\nValve أقر بحدوث سرقات واسعة النطاق للحسابات ووصف التدابير الوقائية المتخذة.\n\nValve منشور ↗محفوظ 2026-08-09 ↗\n2015\nValve قام بتعهيد هذا القسم — وأعلن ذلك\n\nValve تحتفظ بفريق قيادة دعم داخلي صغير Steam، وقد أعلنت ذلك \"استعان بعدة شركات مختلفة\" لتولي شؤون الدعم (Erik Johnson، Valve، إلى موقع Kotaku)؛ حيث تسمح المادة 5.2 من سياسة الخصوصية الخاصة بها لهذه الأطراف الثالثة بالوصول إلى بيانات المستخدمين. لم يكشف المقاول الذي يمتلك صلاحية استرداد الحساب، Valve، عن ذلك قط — تشير المناقشات في المجتمع إلى شركات مثل «Concentrix»، لكن لم يتم تأكيد أي منها. وكان مكتب الخدمات الخارجية قد أُنشئ قبل سنوات من أي من الاعترافين المذكورين أدناه.\n\nKotaku: Valve بشأن الدعم الذي تقدمه ↗محفوظ 2025-07-11 ↗\n2023\nالقبول الأول\n\nفريق CS:GO التابع لـ Valve يتحمل المسؤولية كتابةً عن اختراق حساب ما من خلال إجراءات طلب المساعدة الخاصة به، ويقوم بإلغاء عمليات التبادل.\n\nافتح ملف الاستعانة بمصادر خارجية ↓\n2025\nالاعتراف الثاني\n\nبعد 33 شهراً، كتب قسم الدعم Steam أن أحد الفنيين «لم يتبع إجراءاتنا، مما أدى إلى إعادة حسابك إلى شخص آخر». نفس القناة. نفس النتيجة.\n\nDexerto، 14 نوفمبر 2025 ↗\n\nملف القضية / شركة HFB والادعاءات المتعلقة بالتعاقد مع جهات خارجية\n\nكان المدخل هو Steam الدعم نفسه.Valve صرح بذلك كتابةً.\n\nفي الرد الصادر عن قسم الدعم الذي نشره موقع Dexerto، يقر فريق CS:GO التابع لـ Valve بمسؤوليته عن اختراق أحد الحسابات من خلال عملية طلب المساعدة — قناتها الخاصة، وليس صفحة تصيد احتيالي ولا المستخدم. تم استرداد الأصول وإلغاء الصفقات، وهو الإجراء التصحيحي الذي يوضح Valve للضحايا الآخرين أنه غير متاح. ووفقًا للتقارير، بلغ رصيد HFB $2,000,000+ في ذلك اليوم و $3,000,000+ في المتابعة؛ خسر فريق Qkss بنتيجة $1,000,000+ بنفس الطريقة ولم يحصل على أي شيء.\n\nرد من فريق الدعم / أعاد نشره موقع DEXERTO · 21 فبراير 2023\n\"تم اختراقها من خلال طلب مساعدة فنية، ويتحمل فريق CS:GO المسؤولية عن ذلك\"\nاقرأ التقرير والرسالة المنشورة ↗ محفوظ 2025-08-18 ↗\n01 / ما الذي سمح به الصمام\nكانت قناتها الخاصة للدعم هي وسيلة الدخول\n\nيتناول الرد الحساب الذي تعرض للاختراق وإلغاء صفقاته. قام Valve بإلغاء تلك الصفقات — مما يعني أنها كانت قابلة للإلغاء. ولا توجد التذكرة الأصلية المصادق عليها ضمن هذه المجموعة.\n\n02 / ما لم تحله عمليات الفصل\nانفتح ذلك الباب نفسه مرة أخرى في نوفمبر 2025\n\nقام المقاول بفصل جميع موظفي الدعم التابعين له — وفقًا لما أورده موقع Mzkshow عبر Dexerto، وليس وفقًا لبيان صادر عن الشركة بشأن الموظفين. وبعد ثلاثة وثلاثين شهراً Steam، أرسلت شركة الدعم رسالة إلى محصل آخر تفيد بأن «فني الدعم الذي تولى طلب المساعدة لم يتبع إجراءاتنا، مما أدى إلى إعادة حسابك إلى شخص آخر». هذه العبارة مقتبسة من Valve نفسها، بشأن القناة نفسها.\n\nالدخول الثاني، 14 نوفمبر 2025 ↗\n03 / ما هو «OPEN»؟\nValve لم يذكر اسم المقاول قط\n\nلا تحدد هذه المصادر هوية المقاول ولا الموقع. وهذا لا يمثل ثغرة في التقرير — بل هو معلومة لم تكشف عنها Valve بشأن من كان لديه حق الوصول إلى حسابات المستخدمين.\n\nتقرير معاصر عن القضية ↗\n\nثلاثة أسئلة لم يرد عليها Valve: من يمكنه تجاوز إجراءات استعادة الحساب، وماذا كشفت مراجعة سجلات الوصول، وما الذي تغير بعد ذلك.\n\nالادعاءات اللاحقة الواردة في أرشيف الدعم المحفوظ\n\nتنقل منشوراتان على موقع Reddit تعودان إلى عام 2024 مزيدًا من التحقيقات التي أجراها Mzkshow — قضية رفع الحظر VAC في يوليو 2024 وقضية المخزون $13,000 في ديسمبر 2024. وهذه حوادث تم الإبلاغ عنها بشكل منفصل. والسؤال المتعلق بالمساءلة في كل منهما هو نفسه: من كان لديه صلاحية تجاوز القيود، وماذا كشفت عملية التدقيق، وما الذي تغير.\n\n14 يوليو 2024 · تم الإبلاغ عن الشفاء / حالة حظر VAC ↗2 ديسمبر 2024 · تم الإبلاغ عن $13,000 حالة مخزون ↗محفوظ 2025-08-05 ↗منشوران محفوظان، وصفوف المصدر ورموز التجزئة ↓\n\n05 / تابع الخسارة\n\nكل مبلغيحتاج إلى حقيبة.\n\nعشر حالات، من يونيو 2022 إلى مارس 2026. كل مبلغ هو الرقم الذي نشره المصدر المذكور — $6,300,000، $2,000,000+، $1,000,000+، ≈$320,000، ≈$300,000، وانخفض السعر إلى 288 يورو. يحتفظ Valve بسجل المعاملات وسجل الجلسات وسجل تدقيق الدعم لكل منها، ولم يقدم أيًا منها.\n\nقناة الدعم21 يونيو 2022\n$2,000,000+\nHFB — the largest inventory in the game\n\nتقييم المخزون المُعلن · ارتفع إلى ما يزيد عن3مليون دولار في متابعة فبراير 2023\n\nسبعة سكاكين «Dragon Lores» التذكارية وسكين «Karambit» ذو الجوهرة الزرقاء #1، وتبلغ قيمة هذا السكين وحده حوالي $1.26m. الحساب خامل منذ ثلاث سنوات مع بقاء أداة المصادقة نشطة؛ تم تغيير البريد الإلكتروني وكلمة المرور عبر مسار استعادة الدعم. قامت Valve بإلغاء المعاملات — وأوضحت مسؤوليتها كتابةً. قبل التراجع، كان قد تم بالفعل سحب عائدات مبلغ $200,000+ عبر market.csgo.com، الذي يقوم بالتسوية نقدًا وعملات مشفرة. التراجع يعيد السكن، وليس المال الذي سحبه شخص ما بالفعل. كما حدث خلل في عملية التراجع: فقد أخفى أحد المشترين قطعة «Souvenir Dragon Lore» الخاصة به في وحدة تخزين داخل اللعبة، ولم يتمكن البرنامج النصي من رؤية ما بداخل الحاوية الخاصة به، وقام موقع Valve بتكرار عنصر بقيمة130,000 دولار أثناء التراجع عن عملية سرقة — تم الكشف عن ذلك من خلال معرّفات العناصر والبلاغات المقدمة من المجتمع، وتم حذفها في يوليو 2022,، وتم رد المبلغ للمشتري من قبل BUFF بدلاً من Valve.\n\nDexerto، يوم وقوع السرقة ↗\nالمحفظة والمشتريات07 يوليو 2022\n>$500\n44 disputed Market purchases\n\nالإنفاق المزعوم من المحفظة · دولار أمريكي\n\nأبلغ أحد المستخدمين عن عمليات شراء غير مصرح بها لعناصر من لعبة «Dota» ذات قيمة منخفضة 2، وعن استجابة غير مرضية من فريق الدعم.\n\nاقرأ الشكوى ولقطات الشاشة المرفقة ↗\nاختراق المنصة14 2022 أغسطس\n$6,300,000\nCS.Money — 19,000+ أشكال من الروبوتات\n\nالتقييم المالي · التقدير الأولي:1.6مليون دولار\n\nاستولى المهاجمون على ملفات المصادقة عبر الهاتف المحمول الخاصة بروبوتات التداول في المنصة وأفرغوها من محتوياتها، ثم وزعوا جزءًا من الغنيمة على متداولين معروفين لإخفاء آثارهم. تمكن باحثو المجتمع من تحديد حسابات المهاجمين على 55 في غضون ساعات. لم تقم Valve بأي إجراءات تصحيحية — حيث يقع موقع طرف ثالث خارج نطاق Steam، وفقًا لما ذكره نفس الموقع Steam الذي تولى عملية السرقة من البداية إلى النهاية من خلال مخزونه ونظام التداول API ونظام الحسابات الخاص به.\n\nاقرأ التقرير المعاصر ↗\nقناة الدعمنُشر في 21 في فبراير 2023\n$1,000,000+\nQkss — نفس الباب، نفس الممثل، إجابة معاكسة\n\nتقييم المخزون المُبلغ عنه\n\nتم التعامل مع قضية HFB بنفس الطريقة التي تم التعامل بها مع قضية Qkss، من قبل نفس الموظف، ومن خلال نفس طلب الدعم الفني. وقد تم تسوية قضية HFB بالكامل قبل ثمانية أشهر. أما قضية Qkss فلم يتم تسويتها. ولا يوجد في السجل المنشور ما يميز بين الحالتين سوى حجم الجمهور.\n\nDexerto حول التحقيق في قضية Mzkshow ↗\nقناة الدعمنُشر في 2023\n≈ $320,000\nالتداول بناءً على معلومات داخلية بحد ذاته — لمدة عام واحد\n\nالعائدات على مدى عام تقريبًا · لا يمثل تقييمًا للمخزون\n\nتمكن فريق الدعم من الوصول إلى سجل الحساب الذي يعود إلى ما قبل 15 سنة: مفتاح القرص المضغوط الأول، والبريد الإلكتروني الأول، والبطاقة الأولى — وهي بالضبط الأدلة التي تطلبها عملية استعادة الحساب. من يمتلك قاعدة البيانات يفوز دائمًا في هذا الجدال ضد من يمتلك الحساب. تم بيع بندقية M4A4 Howl مسروقة مع هولوغرامات iBUYPOWER وTitan Katowice 2014 مقابل35,000 دولار، وانتهى بها المطاف مع b1t من فريق NAVI، الذي لم يكن لديه أي وسيلة لمعرفة ذلك. وكان رد المقاول هو فصل كل موظف يعمل في قسم الدعم Steam.\n\nأخبار «إسكور» حول التحقيق نفسه ↗\nالمحفظة والمشتريات09 ديسمبر 2023\n€288\nفقدان المحفظة على الرغم من الحماية ذات الخطوتين\n\nTRUSTPILOT · فهرس المصادر 16\n\nأبلغ المُراجع عن تعرض حسابه للاختراق ورفض تقديم المساعدة بشأن الإنفاق في «ماركت». ولا يحتوي ملف التصدير على رابط خاص بالمراجعة.\n\nالتحقق من مصدر المنشأ ↗\nاسترداد الحساب02 ديسمبر 2024\n$13,000\n«ماتفي» — بعد عامين من عمليات الفصل\n\nتقدير المخزون من جانب المؤلف\n\nتم منح حق استعادة الحساب لشخص قدم بيانات حسابًا لم يتمكن المالك نفسه من مطابقتها. نفس المسار، نفس النتيجة، بعد أن قام المقاول بإغلاق مكتب الدعم الخاص بموقع Steam.\n\nاقرأ الادعاء المحفوظ ↗\nاسترداد الحساب09 مايو 2025\n≈ $10,000\nالاسترداد من خلال تذكرة شخص آخر\n\nالخسارة المزعومة للبضائع · دولار أمريكي\n\nيدعي أحد المستخدمين في كيبيك أن فريق الدعم قام بإعادة تعيين كلمة المرور وإزالة حماية الحساب بناءً على طلب شخص آخر.\n\nاقرأ الشكوى المكتوبة بصيغة المتكلم ↗\nقناة الدعم13 نوفمبر 2025\n≈ $300,000\nHawkeye337 — والاعتراف الثاني المكتوب لـ «Valve»\n\nالمجموعة الكاملة من هولوغرامات كاتوفيتس 2014\n\nطالب المهاجم بـ 1 بيتكوين وبدأ في نقل المقتنيات إلى حسابات Negevs لتدميرها. رد فريق الدعم على Steam: «فشل أحد فنيي الدعم الذي تولى طلب المساعدة في اتباع إجراءاتنا، مما أدى إلى إعادة حسابك إلى شخص آخر». بعد ثلاثة وثلاثين شهراً من الاعتراف الأول، نفس السيناريو. تمت استعادة الحساب في غضون ساعات من انتشار الموضوع على X. لم يكن لدى Qkss هذا العدد من المتابعين.\n\nDexerto, 14 Nov 2025 ↗\nالمحفظة والمشتريات29 MAR 2026\n$50\nعمليات إعادة الشحن غير المصرح بها والألعاب المهداة\n\nTRUSTPILOT · فهرس المصادر 290\n\nيدعي المُقيِّم وجود إنفاق غير مصرح به وطلبات استرداد أموال لم تُلبَّ. ولا يتضمن ملف التصدير رابط المراجعة الفردية.\n\nالتحقق من مصدر المنشأ ↗\n\nتُحتفظ بالمصادر والمبالغ كما وردت في كل مصدر. يحتفظ Valve بسجلات المعاملات وسجلات الجلسات وسجل التدقيق الداعم لكل حالة من هذه الحالات. يرجى تقديمها. فالمشاركة المحفوظة على موقع Reddit لا تحسم المسألة — بل سجلات Valve نفسها هي التي تحسمها.\n\nالمجموعة / بعد الفحص\n\n231,829 حسابات معروضة للبيع.Valve يحتوي على السجلات الخاصة بكل واحد منهم.\n354 → 201\nسجلات Trustpilot\n\nتم حذف 153 صفًا مكررًا. لم يتم الاحتفاظ بعناوين URL الخاصة بالمراجعة الفردية في ملف التصدير.\n\n231,829\nSteam قوائم الحسابات\n\n33,509 مصنفة على أنها مسجلة تلقائيًا؛ 198,320 تحت علامة «السارق» الخاصة بالجامع. القوائم المعروضة لا تعني إتمام عمليات البيع.\n\nتدقيق المحصلات ↓البحث في أرشيف المصدر ↗",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "حسابك.وصولهم.من الذي يرد؟"
          },
          {
            "level": 2,
            "id": null,
            "text": "لقد أدت الأتمتة إلىسلسلة من المستندات."
          },
          {
            "level": 3,
            "id": null,
            "text": "ArchiSteamFarm"
          },
          {
            "level": 2,
            "id": null,
            "text": "أي مفتاحعن ماذا نتحدث؟"
          },
          {
            "level": 3,
            "id": null,
            "text": "مفتاح واجهة برمجة التطبيقات (API) الشخصي للموقع الإلكتروني"
          },
          {
            "level": 3,
            "id": null,
            "text": "مفتاح واجهة برمجة تطبيقات الويب الخاصة بالناشر"
          },
          {
            "level": 3,
            "id": null,
            "text": "OpenID / رموز الجلسة"
          },
          {
            "level": 3,
            "id": null,
            "text": "يمكن أن تستخدم الأتمتة أكثر من مفتاح واجهة برمجة التطبيقات (API)."
          },
          {
            "level": 2,
            "id": null,
            "text": "ما زال يلعب.تم الكشف عنها بالفعل."
          },
          {
            "level": 3,
            "id": "session-hidden-title",
            "text": "الثقة تسبق إنشاء الموقع الإلكتروني."
          },
          {
            "level": 2,
            "id": null,
            "text": "قد يكون هذا العنصر نادرًا.الحد لا يزال ساريًا."
          },
          {
            "level": 2,
            "id": null,
            "text": "نحن نحمل مسؤولية حماية البيانات.مسؤول عن منح حق الوصول."
          },
          {
            "level": 3,
            "id": null,
            "text": "كان الميزان متاحًا للجمهور"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve قام بتعهيد هذا القسم — وأعلن ذلك"
          },
          {
            "level": 3,
            "id": null,
            "text": "القبول الأول"
          },
          {
            "level": 3,
            "id": null,
            "text": "الاعتراف الثاني"
          },
          {
            "level": 3,
            "id": null,
            "text": "كان المدخل هو Steam الدعم نفسه.Valve صرح بذلك كتابةً."
          },
          {
            "level": 4,
            "id": null,
            "text": "كانت قناتها الخاصة للدعم هي وسيلة الدخول"
          },
          {
            "level": 4,
            "id": null,
            "text": "انفتح ذلك الباب نفسه مرة أخرى في نوفمبر 2025"
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve لم يذكر اسم المقاول قط"
          },
          {
            "level": 2,
            "id": null,
            "text": "كل مبلغيحتاج إلى حقيبة."
          },
          {
            "level": 3,
            "id": null,
            "text": "HFB — the largest inventory in the game"
          },
          {
            "level": 3,
            "id": null,
            "text": "44 disputed Market purchases"
          },
          {
            "level": 3,
            "id": null,
            "text": "CS.Money — 19,000+ أشكال من الروبوتات"
          },
          {
            "level": 3,
            "id": null,
            "text": "Qkss — نفس الباب، نفس الممثل، إجابة معاكسة"
          },
          {
            "level": 3,
            "id": null,
            "text": "التداول بناءً على معلومات داخلية بحد ذاته — لمدة عام واحد"
          },
          {
            "level": 3,
            "id": null,
            "text": "فقدان المحفظة على الرغم من الحماية ذات الخطوتين"
          },
          {
            "level": 3,
            "id": null,
            "text": "«ماتفي» — بعد عامين من عمليات الفصل"
          },
          {
            "level": 3,
            "id": null,
            "text": "الاسترداد من خلال تذكرة شخص آخر"
          },
          {
            "level": 3,
            "id": null,
            "text": "Hawkeye337 — والاعتراف الثاني المكتوب لـ «Valve»"
          },
          {
            "level": 3,
            "id": null,
            "text": "عمليات إعادة الشحن غير المصرح بها والألعاب المهداة"
          },
          {
            "level": 2,
            "id": null,
            "text": "231,829 حسابات معروضة للبيع.Valve يحتوي على السجلات الخاصة بكل واحد منهم."
          },
          {
            "level": 3,
            "id": null,
            "text": "سجلات Trustpilot"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam قوائم الحسابات"
          }
        ],
        "links": [
          "https://phishdestroy.io/live-intel/?category=steam",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/lzt.market.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-evidence-lzt.json",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://github.com/JustArchiNET/ArchiSteamFarm/blob/main/ArchiSteamFarm/ArchiSteamFarm.csproj",
          "https://github.com/JustArchi",
          "https://github.com/renovate[bot]",
          "https://github.com/JustArchi-ArchiBot",
          "https://github.com/dependabot-preview[bot]",
          "https://github.com/renovate-bot",
          "https://github.com/actions-user",
          "https://github.com/dependabot-support",
          "https://github.com/Abrynos",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/automation-map.json",
          "https://phishdestroy.io/steam_dossier/ar/output_steam_network/network.html",
          "https://phishdestroy.io/steam_dossier/ar/output_steam_network/raw_data.json",
          "https://phishdestroy.io/steam_dossier/ar/#proxy-bypass-explainer",
          "https://partner.steamgames.com/doc/webapi_overview/auth",
          "http://web.archive.org/web/20260915025812/https://partner.steamgames.com/doc/webapi_overview/auth",
          "https://partner.steamgames.com/doc/webapi/ISteamUserAuth",
          "http://web.archive.org/web/20260829124950/https://partner.steamgames.com/doc/webapi/ISteamUserAuth",
          "https://phishdestroy.io/steam_dossier/ar/#vulnerability-profile",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "http://web.archive.org/web/20260924181824/https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://store.steampowered.com/privacy_agreement/",
          "https://store.steampowered.com/oldnews/19618",
          "http://web.archive.org/web/20260809125516/https://store.steampowered.com/oldnews/19618",
          "https://kotaku.com/valve-explains-why-steam-customer-service-is-still-terr-1736988223",
          "http://web.archive.org/web/20250711004653/https://kotaku.com/valve-explains-why-steam-customer-service-is-still-terr-1736988223",
          "https://www.dexerto.com/counter-strike-2/valve-saves-hacked-cs2-player-threatened-with-ransom-over-300000-of-rare-stickers-3283135/",
          "https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "http://web.archive.org/web/20250818113925/https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "https://lis-skins.com/ru/blog/krupneisaia-mosenniceskaia-sxema-v-istorii-steam/",
          "https://www.reddit.com/r/cs2/comments/1e38jo4/stealing_accounts_and_removing_vac_bans_a_new/",
          "https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "http://web.archive.org/web/20250805141942/https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/outsourcing-archive-records.json",
          "https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "https://escorenews.com/en/csgo/news/44087-valve-steam-support-employee-accused-of-selling-inactive-accounts-inventories-worth-six-figures-b1t-has-one-of-these-skins",
          "https://phishdestroy.io/steam_dossier/ar/PART2_RESEARCH.md",
          "https://www.reddit.com/r/GlobalOffensive/comments/1h56shi/steam_support_is_stealing_accounts/",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/design-review/part2/quality-review.json",
          "https://phishdestroy.io/steam_dossier/ar/steam_evidence_archive.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ar/investigation_part2.content.json",
      "export_json_sha256": "56ae1fbdfba47aa86907e835f9486cebb00c7c7aec8538649767718cec965ed1"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ar/legal_analysis.html",
      "language": "ar",
      "title": "شروطهم، حقوقك — ملف «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/ar/legal_analysis",
      "source_html_sha256": "4935e2b1ccde43b697cc52b085e021a73dd94abe7f3419d4ea7fab35a684f202",
      "exported_at": "2026-09-29T00:20:06.325Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "legal_analysis.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ar/legal_analysis.pdf?v=print-20260929-v5",
        "sha256": "0e875abe4620e09ef17b2634f1417ed7efa22f0521c99bccbd53edefaadfcb9c",
        "bytes": 142638,
        "pages": 7
      },
      "integrity": {
        "signed_object": "legal_analysis.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "legal_analysis.content.json.asc",
        "digest_file": "legal_analysis.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify legal_analysis.content.json.asc legal_analysis.content.json",
          "sha256sum -c legal_analysis.content.json.sha256"
        ]
      },
      "content": {
        "text": "التقرير القانوني والاقتصادي\nالتحليل القانوني — شروط الخدمة والامتثال للوائح التنظيمية\n\nشروطهم. حقوقك.\n\nما يثبته هذا القسم\n\nيُقيّم هذا التدقيق القانوني الجنائي التباين التعاقدي بين شركة «Valve» ومستخدمي موقع «Steam» عبر الولايات القضائية التنظيمية الرئيسية. ويحدد التقرير كيف أن ترخيص الاشتراك القابل للإلغاء يحرم المستهلك من حق الملكية القانوني، ويحلل السوابق القضائية للمحكمة الأوروبية بشأن استنفاد حق إعادة البيع الرقمي، ويفحص مدى الامتثال لقانون الخدمات الرقمية (DSA) والمادة 15. من قانون حقوق النشر والوسائط الرقمية (GDPR). ويوضح التحليل كيف تعمل آليات الإنفاذ الآلية دون وجود إجراءات استئناف ذات مغزى، في حين تستخلص رسوم السوق التي تفرضها المنصات بشكل منهجي القيمة الاقتصادية من كل معاملة بين الأقران.\n\n← العودة إلى ملخص الإدارة التنفيذية\n\nيقدم هذا التقرير تحليلاً قانونياً واقتصادياً وتقنياً للفجوة بين القواعد المعلنة لمنصة «Steam» وموقف المستهلك: حيث يتم تطبيق القواعد آليًّا مع قلة سبل الانتصاف، وتتمتع الشركة بسيطرة واسعة النطاق على الأصول الرقمية. وقد تم ذكر الأرقام مع الإشارة إلى مصادرها؛ وفي الحالات التي تعذر فيها تتبع مصدر الرقم إلى سجل أولي، تم حذفه.\n\nالصورة المتجهة 1\n\nاستبدال مفهوم «الملكية» بترخيص قابل للإلغاء، بحيث يمكن سحب الأصول الرقمية بموجب الاتفاقية.\n\nالصورة المتجهة 2\n\nنظام الإنفاذ الآلي (VACNet) الذي تنص سياسة الحظر الخاصة به Steam على أنه لا يمكن التراجع عنه.\n\nالصورة المتجهة 3\n\nضوابط على الحسابات والأصول مقترنة برسوم سوق CS2 الخاصة بـ «15%» (5% وSteam و10% — رسوم الناشر) التي تستنزف قيمة النظام البيئي عند كل عملية إعادة بيع.\n\nعدم التماثل في المصطلحات\nإعفاء من المسؤولية والترخيص القابل للإلغاء\n2.1 نموذج «الاشتراك» مقابل حقوق الملكية\n\nيمنح البند 2 من اتفاقية الاشتراك في موقع Steam المستخدمين فقط حق ترخيص شخصي، غير حصري، غير قابل للتحويل وقابل للإلغاء. وبموجب هذه الاتفاقية، يجوز لشركة «Valve» إنهاء الحسابات في أي وقت، وقد يتم مصادرة أرصدة محفظة «Steam» غير المستخدمة.\n\n2.2 وهم استرداد الأموال مقابل توجيه الاتحاد الأوروبي بشأن حقوق المستهلك\nالإطار القانوني\tآلية استرداد الأموال\tالقيود\nEU Consumer Rights Directive\tUnconditional 14-day right of withdrawal on digital content\tWaived if download begins with explicit consumer consent\nSteam SSA\t14 days / under 2 hours played\tValve may deny at its discretion for \"abuse\"\nالتقييم\n\nValve يُشترط حق الانسحاب القانوني الذي يمنحه الاتحاد الأوروبي لمدة 14-يومًا بفترة زمنية محددة تبلغ «14 يومًا / 2 ساعة»، والتي يجب قبولها عند التنزيل قبل أن يتسنى تقييم المنتج. وتؤدي هذه السياسة إلى تضييق نطاق الحق القانوني — لا توسيعه —؛ أما ما إذا كان ذلك قانونيًا أم لا، فهذه مسألة تخص السلطة المختصة، وليست استنتاجًا نؤكده هنا.\n\nالدعاوى القضائية\nالسوق الثانوية وقوانين مكافحة الاحتكار\nقضية «UFC Que Choisir» ضد «Valve» — فرنسا\n2019\nمحكمة باريس: مبدأ استنفاد الحقوق ينطبق على الألعاب الرقمية — إعادة البيع قانونية\n2022 أكتوبر\nمحكمة الاستئناف في باريس تنقض الحكم\n23 2024 أكتوبر\nمحكمة النقض (المحكمة العليا): ألعاب الفيديو هي «أعمال معقدة» بموجب توجيه «InfoSoc»، وليست برمجيات. إعادة البيع الرقمي محظور. يسود مبدأ «Valve».\nقضية مكافحة الاحتكار الخاصة بشركة «وولفاير جيمز» — الولايات المتحدة (في قضية الدعوى القضائية المتعلقة بمكافحة الاحتكار الخاصة بشركة «Valve»، رقم2:21-cv-00563)\n\nتحظر بند «الدولة الأكثر رعاية» (PMFN) في منصة Valve على المطورين بيع مفاتيح Steam بسعر أرخص على أي منصة أخرى. ولا يمكن للمتاجر المنافسة — حتى تلك التي تتقاضى عمولة 12% مقابل Valve's 30% — تمرير هذه الوفورات إلى المستهلكين.\n\nWhat this means — PMFN — platform most-favoured-nation\n\nA contract term that stops a seller offering better terms anywhere else than on the platform it signed with. Applied to game keys it means a studio cannot undercut its Steam price on a storefront that takes a smaller cut. It is the clause at the centre of the antitrust claims against Valve.\n\n336إجمالي عدد موظفي شركة «Valve» (2021). المصدر: مستندات الكشف التي رُفعت عنها السرية.\n79الموظفون المسؤولون عن إدارة منصة «Steam» بأكملها. المصدر: مستندات الكشف التي رُفعت عنها السرية.\n$3.5Mصافي الدخل لكل موظف. المصدر: مستندات الكشف التي رُفعت عنها السرية.\n\nتُظهر سجلات الكشف غير المختومة ما يلي: $8.5B إيرادات إجمالية في 2021 بشأن موظفي شركة «336». الـ 79-فريق «Steam» تولى معالجة 373,000بالإضافة إلى تذاكر الدعم اليومية عن طريق توجيهها عبر مراكز اتصال آلية متعاقد معها خارجيًا.\n\nمرفق ملف القضية غير السري · W.D. واشنطن. القضية رقم 2:21-CV-00563مذكرة داخلية بشأن عملية الكشف\n\nتيم سويني (الرئيس التنفيذي لشركة Epic Games) إلى غابي نيويل: \"لماذا لا تزال شركة Steam تستحوذ على 30% من إجمالي الإيرادات، في حين أن تكلفة معالجة المدفوعات تبلغ 2–5%، وتكلفة النطاق الترددي CDN تبلغ $0.002/GB؟ إذا استبعدنا الألعاب الأكثر رواجًا 25 على موقع Steam، فأنا أراهن على أن شركة Valve حققت أرباحًا من معظم الألعاب التالية 1,000 تفوق الأرباح التي حققها المطورون أنفسهم.\"\n\nرسالة داخلية من سكوت لينش (المدير التنفيذي للعمليات، شركة «Valve») موجهة إلى غابي نيويل: \"هل أنت غاضب يا أخي؟\"\n\nرد على الإفادة المشفوعة بيمين (بلومبرغ، 2026): بموجب المادة 30(ب)(1) المتعلقة بالإدلاء بالشهادة، أدلى غابي نيويل بشهادته قائلاً إن \"لا تتبع شركةValve أي سياسة أو ممارسة تقضي بفرض الأسعار على مطوري البرامج من الأطراف الثالثة على المنصات الأخرى.\" واجه المدعون نيويل بمذكرات داخلية من موقع Valve تثبت وجود رقابة نشطة على الأسعار وتهديدات بحذف المنتجات من القائمة ضد المطورين الذين يحددون أسعارًا أقل في المتاجر المنافسة. وفي أواخر مارس 2026,، رفضت المحكمة الفيدرالية طلب «Valve» بالحكم المستعجل، وأحالت الدعوى الجماعية للمطورين 32,000-إلى محاكمة أمام هيئة محلفين.\n2024 نوفمبر\n\nتمت المصادقة على الدعوى الجماعية بشأن ~ مطورو موقع32,000 الذين دفعوا عمولات منذ يناير 2017, بالإضافة إلى دعوى جماعية موازية مرفوعة من المستهلكين.\n\nالأضرار المطالب بها\n\n$3.1B\nتضاعف ثلاث مرات بموجب قانون مكافحة الاحتكار الأمريكي = $9.3B التعرض المحتمل.\n\n2026: يونيو تزعم دعوى قضائية جديدة أن شركتي «مايكروسوفت» و«Valve» أبرمتا اتفاقية احتكارية تهدف إلى تقييد المنافسة في مجال توزيع ألعاب أجهزة الكمبيوتر الشخصية.\n\nالقبول الرسمي في برنامج الجرائم المالية ومكافحة غسل الأموال\nValve اعتراف رسمي: عمليات تصفية الاحتيال العالمية (28 أكتوبر 2019)\n\nفي 28 أكتوبر 2019, Valve، أوقفت الشركة رسميًا عمليات التداول وإعادة البيع عبر المنصات الإلكترونية لمفاتيح حاويات لعبة «Counter-Strike» التي تم شراؤها حديثًا. وفي إعلانها الرسمي للجمهور (blog.counter-strike.net/2019/10/26113)، اعترفت شركة «Valve» كتابةً بأن الاقتصاد الافتراضي الذي صممته قد أصبح مركزًا دوليًا لغسل الأموال:\n\n\"في الماضي، كانت معظم عمليات تداول المفاتيح التي لاحظناها تتم بين عملاء شرعيين. غير أن شبكات الاحتيال العالمية تحولت مؤخرًا إلى استخدام مفاتيح CS:GO لتسييل أرباحها. وفي الوقت الحالي، يُعتقد أن جميع عمليات شراء المفاتيح التي ينتهي بها الأمر إلى التداول أو البيع في السوق تقريبًا تأتي من مصادر احتيالية.\"\n\nالسياق التنظيمي: جاء هذا الاعتراف في أعقاب الإنذار الرسمي الذي وجهته لجنة المقامرة بولاية واشنطن (WSGC) إلى موقع Valve، وأوامر «التوقف والكف» الصادرة في يوليو 2016 من قبل المستشار القانوني العام لـValve، كارل كواكينبوش، إلى نطاقات المقامرة على «سكينز» التابعة لـ23 (بما في ذلك CSGO Lotto وCSGOLounge وOPSkins)، وذلك فقط بعد أن هدد التحقيق الجنائي في قضية المقامرة بوقف عمليات المنصة.\n\nالاختصاص القضائي\nصاحب حقوق في روسيا، لا يمكن للمستخدم الوصول إليه\n\nتُظهر «اتفاقية الاشتراك» موقع Valve كطرف لا يتحمل سوى القليل من الالتزامات ولا يمكن لأحد الوصول إليه: فالقيود دائمة، والطعون تُرفض، ويُحجب الوصول عن مناطق بأكملها بمجرد سطر واحد عن «المناطق الخاضعة للعقوبات». وعلى النقيض من هذا الموقف، هناك ما يفعله موقع Valve عندما تكون مصالحه التجارية هي الموضوع المعني في ولاية قضائية يعاملها، في الأحوال العادية، على أنها صعبة.\n\nValve v. Touch Skins — دعوى تتعلق بحقوق الملكية الفكرية قبل المحاكمة، روسيا\n1 2026 سبتمبر\nشركة Valve، من خلال مكتب المحاماة الروسي ميلينغ، فويتشكين وشركاؤهم، ترسل خطابًا بالمطالبة قبل المحاكمة إلى مشغلي أغلفة اللمس، وهو جهاز كبير لتغيير مظهر CS2، عبر البريد الروسي والبريد الإلكتروني.\nالأسباب\nثلاث مجموعات من الانتهاكات المزعومة: الحقوق الحصرية في البرمجيات؛ والحقوق المتعلقة بمظهر أشكال الأسلحة والسكاكين والقفازات؛ والعلامات التجارية الخاصة بـ«Valve». ويُوصف سلوك المشغلين بأنه متعمد وممتد.\nالطلب\nأوقف العمل فوراً واحذف جميع مكونات البنية التحتية — الخاصة بالبرنامج كود المصدر، والمواقع الإلكترونية وصفحات وسائل التواصل الاجتماعي — وفي حال عدم الامتثال لذلك، تحتفظ شركة «Valve» بالحق في رفع دعوى أمام محكمة روسية من أجل تعويض مالي كبير وإحالة المسألة إلى إنفاذ القانون لأغراض التقييم الجنائي.\nالنتيجة\nبعد تلقي الرسالة، أعلنت المنصة عن إغلاقها. ويُذكر أن هذه هي المرة الأولى التي تستخدم فيها منظمة «Valve» أدوات قانونية ضد مطور برنامج لتغيير المظهر في روسيا.\n\nأفاد بذلك محلل البيانات ماكسيم «GabeFollower» بوليتاييف (X، ~11 سبتمبر 2026) ووسائل الإعلام الروسية المتخصصة في الألعاب. ويُعد هذا ادعاءً سابقًا للمحاكمة، وليس دعوى قضائية مرفوعة؛ ولا يوجد رقم قضية معلن. ويتم التعامل مع هذا الخبر هنا على أساس ما ورد في التقارير، وليس كسجل قضائي. المصادر: dota2.ru محفوظ على 2026-09-24 ↗ · شازو.\n\nنفس الولاية القضائية، في الاتجاه الآخر\n\nValve ليست غريبة عن النظام القانوني والتنظيمي الروسي. إنها يتوافق مع متطلبات «روسكومنادزور»: بناءً على طلب الهيئة التنظيمية، قامت بإزالة صفحات المجتمع 260وSteam التي كانت تحتوي على مواد محظورة، وقد صرحت هيئة «روسكومنادزور» علنًا بأن موقع Steam يستوفي متطلبات التشريع. قانون «الصفحة المقصودة» الروسي (القانون الاتحادي 236-FZ، الذي دخل حيز التنفيذ اعتبارًا من 2022) يُلزم منصات الإنترنت الأجنبية الكبرى التي تقدم خدماتها للمستخدمين الروس بإنشاء وجود محلي وحساب اتصال مع هيئة «روسكومنادزور». Valve تستجيب لأوامر الإزالة الصادرة عن تلك الهيئة التنظيمية، كما أنها تلجأ حاليًّا إلى مستشارين قانونيين روس وتستخدم التهديد باللجوء إلى المحاكم الروسية لحماية «السكينات» الخاصة بها باعتبارها ملكية فكرية.\n\nإذن، فإن المنصة تتمتع بالقدرة على الوصول والفعالية والدفاع عن حقوقها، لا سيما فيما يتعلق بإيراداتها. ويكمن التباين في موقف المستخدم: فالعميل الذي يدفع مقابل الخدمة في منطقة خاضعة للعقوبات يُبلغ بأن العلاقة قد انتهت، ويتم حظر وصوله إلى المجتمع حتى 2038, يتم إغلاق التذكرة، ولا يوجد أي منتدى يمكن من خلاله الطعن في هذا القرار — \"كانوا أكثر من سعداء بأخذ أموالي وتنفيذ معاملاتي\"، حيث تمت الموافقة على استرداد المبلغ الخاص بنفس الحساب من عنوان IP إيراني واحد قبل عام (r/pcgaming، 4 أغسطس 2026؛ المزيد من خطابات الإنفاذ في معرض «اقتصاد البطاقات»). تستخدم شركة «Valve» كل آليات النظام القانوني الوطني للدفاع عن أحد «السكينات»؛ في حين أنها لا تتيح للمستخدم الذي اشترى «السكينات» أي إجراءات قانونية على الإطلاق.\n\nValve تتعامل مع نفس الولاية القضائية على أنها نطاق يمكنها العمل فيه والالتزام بقواعده، كلما كانت المصلحة المعنية تخص شركة «Valve» — من خلال الاستعانة بمحامين روس، والتهديد باللجوء إلى المحاكم الروسية، والاستجابة لأوامر إزالة المحتوى الصادرة عن «Roskomnadzor» — بينما تعامل التزاماتها تجاه مستخدمي ذلك السوق، وكل الأسواق الأخرى، على أنها خارج نطاق أي إجراءات قضائية على الإطلاق. فهي تُعتبر «صاحبة حقوق» عندما يتعلق الأمر بإيراداتها، وتُعتبر «طرفًا لا يمكن الوصول إليه» عندما يتعلق الأمر بحقوق المستخدمين.\n\nالمصادر: تاس (RKN: Steam متوافق) · القانون الاتحادي رقم 236-FZ.\n\nالانتهازية القانونية\nالاستسلام أمام بند التحكيم\n2023 — الهجوم\n\nقامت شركات المحاماة (Zaiger LLC، Mason LLP) باستقطاب آلاف المستخدمين عبر وسائل التواصل الاجتماعي، وقدمت عشرات الآلاف من دعاوى التحكيم الفردية في وقت واحد.\n\nالتعرض في فيلم «Valve»\n\n$225M+\nفي شكل رسوم تقديم طلب التحكيم غير القابلة للاسترداد، قبل النظر في أي قضية من حيث الموضوع. تم الحساب وفقًا لقواعد التحكيم الخاصة بالمستهلكين الصادرة عن جمعية التحكيم الأمريكية (AAA) والجداول التكميلية الخاصة بالتحكيم الجماعي. وقدّم المطالبون، الذين تمثّلهم شركتا «Zaiger LLC» و«Mason LLP»، ما يقارب75,000 طلب تحكيم فردي ضد شركة «Valve» (بالتوازي مع الدعاوى المتعلقة بمكافحة الاحتكار في شركة «وولفاير جيمز» (Wolfire Games LLC) وآخرون ضد شركة «Valve»، القضية رقم 2:21-cv-00563-JCC، W.D. (واشنطن). وبموجب جداول رسوم المستهلكين الخاصة بـ«رابطة التحكيم الأمريكية» (AAA)، يدفع المدعى عليه من جانب الشركة رسومًا إدارية غير قابلة للاسترداد لكل قضية، بالإضافة إلى ودائع لتعيين المحكم تبلغ حوالي3,000دولار لكل قضية فردية (75,000 ملفًا ×3,000 دولار = حوالي225مليون دولار كالتزامات إجرائية مسبقة). انظر التقارير القانونية لـ«بلومبرغ لو» و«رويترز» حول مخاطر التحكيم الجماعي في قطاع التكنولوجيا (2023–2024).\n\nالفترة\tآلية تسوية المنازعات الخاصة بوكالة الضمان الاجتماعي\tالتأثير الملحوظ\tالنتيجة\nBefore Sep 2024\tMandatory individual arbitration + class-action waiver\tIndividual litigation becomes economically irrational for users\tMass arbitration → $225M fee threat\nAfter Sep 2024\tDisputes in King County, WA courts only\tArbitration costs are avoided; cases consolidate in a single forum\tClass actions now possible\nالخلاصة\n\nلأكثر من عشر سنوات، كانت إدارة الضمان الاجتماعي (SSA) تشترط على المستخدمين التنازل عن حقهم في المحاكمة أمام هيئة محلفين لصالح التحكيم الفردي. وبعد أن أدت الدعاوى الجماعية المرفوعة أمام هيئة التحكيم إلى جعل تلك الآلية مكلفة ماليًا لشركة «Valve»، تم تعديل قانون الضمان الاجتماعي (SSA) لتحويل النزاعات إلى محاكم مقاطعة كينغ. وقد قُدم هذا التغيير دون توفير خيار انسحاب فعّال؛ حيث كان البديل عن القبول هو فقدان إمكانية الوصول إلى الأصول الرقمية المشتراة من خلال حذف الحساب.\n\nالتنفيذ الخوارزمي\nشبكة VACNet، وافتراض الذنب، والنتائج الإيجابية الخاطئة\n2023، أكتوبر — AMD Anti-Lag+\n\nأدى تحديث برنامج تشغيل AMD (الإصدار 23.10.1) إلى تفعيل ميزة Anti-Lag+ في لعبة CS2، مما أدى إلى اعتراض وظائف ملفات DLL الخاصة باللعبة. وصنفت منظمة VAC هذا الأمر على أنه «حقن أكواد غش»، وفرضت حظرًا دائمًا على آلاف المستخدمين الشرعيين قبل أن تتدخل منظمة Valve.\n\n2023، ديسمبر — دقة عالية (DPI)\n\nتم فرض حظر دائم على اللاعبين الذين تجاوزت دقة DPI لديهم 10,000 عند قيامهم بتدوير الكاميرا بسرعة. لم تتمكن شبكة VACNet من التمييز بين الحركة الفعلية للماوس والغش باستخدام برنامج «spinbot».\n\nفئة الدعم\tزمن الاستجابة المعلن عنه\tالنتيجة الفعلية\nRefund requests\t50 min – 1.5 hr\tAutomatic approval (<14 days, <2 hours played)\nAccount security / recovery\t3–12 hours\tDepends on documentation provided\nContesting a VAC ban\tForm response\tComplete refusal. Support cannot reverse VAC decisions. The ban is permanent.\nالسياسة الرسمية لموقع «Valve»\n\n\"حظر VAC هو إجراء دائم وغير قابل للتفاوض، ولا يمكن إزالته من قِبل فريق الدعم في Steam.\"\n\nقناة الدعم نفسها التي تنشر قرار الحظر تنشر أيضًا رفض إعادة النظر في القرار: Steam. ويشير فريق الدعم إلى أنه لا يمكنه التراجع عن قرار نظام VAC. وبالنسبة للمستخدم، فإن قرار الخوارزمية هو النتيجة النهائية.\n\nالجوانب الاقتصادية لإعادة البيع\nالسيطرة على الأصول الافتراضية ورسوم إعادة البيع\nرسوم سوق «15%» CS2 — يتم خصم القيمة عند كل عملية إعادة بيع\nالتكرار\tرصيد المشتري\tيتلقى البائع\t\"Burned\" (15%)\n1\t$100.00\t$85.00\t$15.00\n2\t$85.00\t$72.25\t$12.75\n3\t$72.25\t$61.41\t$10.84\n10\t$23.16\t$19.68\t~$3.47\nTotal\t$100 → dust\tValve collects the 15% fee on each resale. Users must add new money to keep trading.\nتغيير قاعدة الترقية في CS2 — أكتوبر 2025\n\nدون إشعار مسبق، قامت شركة «Valve» بتعديل قواعد عقود التبادل في لعبة CS2 للسماح بالحصول المضمون على السكاكين والقفازات النادرة مقابل عناصر من فئة «Covert». وانخفضت أسعار السكاكين، بينما ارتفعت أسعار عناصر «Covert» ارتفاعًا حادًّا، وتلا ذلك موجة بيع بدافع الذعر في جميع أنحاء السوق.\n\nالحماية المعلنة من قبل Valve هي المادة 7 من قانون الضمان الاجتماعي (SSA) — لا تتحمل الشركة أي مسؤولية عن تغيير قواعد المنصة. يتحمل المستخدمون المخاطر في اقتصاد قد تتغير قواعده Valve دون إشعار مسبق أو تعويض. ويُعتبر حجم الخسارة المعلنة على مستوى السوق محل خلاف، ولن يتم ذكره هنا دون وجود مصدر أولي.\n\nالاستجابة التنظيمية الأوروبية\nهيئة UOKiK، وقانون DSA، وقانون الإنصاف الرقمي\nUOKiK — بولندا، مايو 2024\n\nأطلقت هيئة مكافحة الاحتكار البولندية (UOKiK) إجراءات رسمية لمكافحة الاحتكار ضد شركة «Valve» وخمسة ناشرين وموزعين محليين للألعاب، وذلك فيما يتعلق بمزاعم تتعلق بتحديد الأسعار، وبنود تقييدية تتعلق بتكافؤ الأسعار، وممارسات الحجب الجغرافي التي أدت إلى دفع المستهلكين البولنديين ما يصل إلى 20% أكثر مقابل الألعاب الرقمية مقارنة بأسواق المنطقة الاقتصادية الأوروبية المجاورة. وكجزء من التحقيق المتعلق بمكافحة الاحتكار، قام مفتشو UOKiK والشرطة بمداهمات فجراً وعمليات تفتيش بحثاً عن أدلة في المقرات البولندية للناشرين والموزعين المحليين الشركاء (وليس في المكاتب التابعة لشركة «Valve»، حيث إن Valve لا تمتلك أي كيان في بولندا). الغرامة القانونية المحتملة: تصل إلى 10% من حجم المبيعات السنوية. المصدر: بيان رسمي صادر عن هيئة UOKiK، «رئيس هيئة UOKiK يفتح تحقيقًا ضد موقع Valve ومطوري الألعاب»، مايو 2024.\n\nقانون الخدمات الرقمية (DSA)\n\nيتطلب الشفافية في عملية الإشراف الآلي. لا تنشر شركة «Steam» أي بيانات تتعلق بحالات «الإنذارات الكاذبة» أو «الحالات المفقودة» الخاصة بـ VACNet، وتشير قناة الدعم الخاصة بها إلى أنه لا يمكن التراجع عن قرارات VAC.\n\nقانون الإنصاف الرقمي — 2026\n\nالأحكام المتوقعة: الوصول الدائم إلى المحتوى المدفوع، وحظر «الأنماط الخادعة» عند التنازل عن الحقوق، والاعتراف بحقوق الملكية في الأصول الرقمية، والحماية من المصادرة الدائمة للمخزون.\n\nالخلاصة\nالفجوات الموثقة بين القواعد والسجلات\n1\n\nفجوة الملكية. يدفع المستخدمون السعر الكامل مقابل ترخيص تسمح الاتفاقية لموقع Valve بإلغائه. وقد قضت المحكمة العليا الفرنسية (2024 أكتوبر) بأن إعادة البيع الرقمي غير محمية، مما أرسى هذا الموقف في القانون.\n\n2\n\nالتنفيذ الخوارزمي. أصدرت شبكة VACNet قرارات حظر خاطئة (برامج تشغيل AMD، وحوادث دقة العرض العالية). ويشير قسم الدعم في Steam إلى أنه لا يمكنه إلغاء قرار VAC، لذا فإن الخوارزمية هي الكلمة الفصل في هذا الشأن.\n\n3\n\nالتوفير في الرسوم. تؤدي رسوم السوق الخاصة بـ «15%» CS2 (5% Steam + 10% رسوم الناشر) إلى انخفاض القيمة عند كل عملية إعادة بيع، وقد تتغير قواعد المنصة دون إشعار مسبق؛ ويتم إخلاء مسؤولية Valve عن مثل هذه التغييرات بموجب اتفاقية خدمة البيع (SSA).\n\n4\n\nتم حذف بند التحكيم. ألغت SSA نظام التحكيم الإلزامي في سبتمبر 2024, بعد أن كشفت الدعاوى الجماعية أن Valve ستتحمل رسومًا تبلغ حوالي225مليون دولار. ولم يُمنح المستخدمون أي خيار فعلي للانسحاب من هذا التغيير.\n\n5\n\nالاختصاص القضائي الانتقائي. Valve استعانت بشركة محاماة روسية (Melling, Voitishkin & Partners) وهددت برفع دعوى قضائية أمام المحاكم الروسية ضد شركة «Touch Skins»، بينما تعاملت في الوقت نفسه مع التزاماتها تجاه مستخدمي ذلك السوق نفسه على أنها خارج نطاق أي إجراءات قضائية. تتصرف شركة «Valve» كصاحبة حقوق عندما يتعلق الأمر بمصالحها التجارية، وكطرف لا يمكن الوصول إليه عندما يتعلق الأمر بحقوق المستخدمين.\n\n← الجزء الأول: تجاوز الحجب والمقامرةالجزء الثاني: الوصول والمساءلة →\n\nيتم الإشارة إلى المصادر القانونية وسجلات القضايا وفقًا لناشريها ومستودعاتها الأصلية. ولا يُدعى أي حق في ملكية الوثائق الأصلية.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "التحليل القانوني — شروط الخدمة والامتثال للوائح التنظيمية"
          },
          {
            "level": 2,
            "id": null,
            "text": "إعفاء من المسؤولية والترخيص القابل للإلغاء"
          },
          {
            "level": 3,
            "id": null,
            "text": "2.1 نموذج «الاشتراك» مقابل حقوق الملكية"
          },
          {
            "level": 3,
            "id": null,
            "text": "2.2 وهم استرداد الأموال مقابل توجيه الاتحاد الأوروبي بشأن حقوق المستهلك"
          },
          {
            "level": 2,
            "id": null,
            "text": "السوق الثانوية وقوانين مكافحة الاحتكار"
          },
          {
            "level": 3,
            "id": null,
            "text": "قضية «UFC Que Choisir» ضد «Valve» — فرنسا"
          },
          {
            "level": 3,
            "id": null,
            "text": "قضية مكافحة الاحتكار الخاصة بشركة «وولفاير جيمز» — الولايات المتحدة (في قضية الدعوى القضائية المتعلقة بمكافحة الاحتكار الخاصة بشركة «Valve»، رقم2:21-cv-00563)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve اعتراف رسمي: عمليات تصفية الاحتيال العالمية (28 أكتوبر 2019)"
          },
          {
            "level": 2,
            "id": null,
            "text": "صاحب حقوق في روسيا، لا يمكن للمستخدم الوصول إليه"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve v. Touch Skins — دعوى تتعلق بحقوق الملكية الفكرية قبل المحاكمة، روسيا"
          },
          {
            "level": 3,
            "id": null,
            "text": "نفس الولاية القضائية، في الاتجاه الآخر"
          },
          {
            "level": 2,
            "id": null,
            "text": "الاستسلام أمام بند التحكيم"
          },
          {
            "level": 2,
            "id": null,
            "text": "شبكة VACNet، وافتراض الذنب، والنتائج الإيجابية الخاطئة"
          },
          {
            "level": 2,
            "id": null,
            "text": "السيطرة على الأصول الافتراضية ورسوم إعادة البيع"
          },
          {
            "level": 3,
            "id": null,
            "text": "رسوم سوق «15%» CS2 — يتم خصم القيمة عند كل عملية إعادة بيع"
          },
          {
            "level": 3,
            "id": null,
            "text": "تغيير قاعدة الترقية في CS2 — أكتوبر 2025"
          },
          {
            "level": 2,
            "id": null,
            "text": "هيئة UOKiK، وقانون DSA، وقانون الإنصاف الرقمي"
          },
          {
            "level": 2,
            "id": null,
            "text": "الفجوات الموثقة بين القواعد والسجلات"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/ar/#briefing-heading",
          "https://dota2.ru/news/67707-valve-cerez-uristov-napravila-krupnoj-rossijskoj-skincendzer-platforme-trebovanie-o-prekrasenii-deatelnosti/",
          "http://web.archive.org/web/20260924181657/https://dota2.ru/news/67707-valve-cerez-uristov-napravila-krupnoj-rossijskoj-skincendzer-platforme-trebovanie-o-prekrasenii-deatelnosti/",
          "https://shazoo.ru/2026/09/12/190508/valve-cerez-rossiiskix-iuristov-dobilas-zakrytiia-krupnogo-skinceindzera-dlia-cs2",
          "https://www.reddit.com/r/pcgaming/comments/1vf24lu/warning_to_all_gamersexpats_steam_took_my_money/",
          "https://phishdestroy.io/steam_dossier/ar/card_economy.html#asymmetry",
          "https://tass.ru/obschestvo/23235387",
          "https://base.garant.ru/401414628/",
          "https://uokik.gov.pl/postepowanie-wyjasniajace-w-sprawie-valve-i-dystrybutorow-gier",
          "https://phishdestroy.io/steam_dossier/ar/",
          "https://phishdestroy.io/steam_dossier/ar/investigation_part2.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ar/legal_analysis.content.json",
      "export_json_sha256": "5ccadc9446f63a117530a447cfd2f7f377889abd3098ba4323f8b3d87945cdaf"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ar/license_disclaimer.html",
      "language": "ar",
      "title": "الترخيص · الحقوق · إخلاء المسؤولية — PhishDestroy",
      "source_url": "https://phishdestroy.io/steam_dossier/ar/license_disclaimer",
      "source_html_sha256": "b8b8d78a2d6190c861da5ad57678b76ef881fab660d9be94cd23293705e77eb4",
      "exported_at": "2026-09-29T00:20:07.789Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "license_disclaimer.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ar/license_disclaimer.pdf?v=print-20260929-v5",
        "sha256": "f03b5d848a710a7f94cdd62ea1bc654c05067bea7754a4840d2ed53ef0c72e71",
        "bytes": 154029,
        "pages": 9
      },
      "integrity": {
        "signed_object": "license_disclaimer.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "license_disclaimer.content.json.asc",
        "digest_file": "license_disclaimer.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify license_disclaimer.content.json.asc license_disclaimer.content.json",
          "sha256sum -c license_disclaimer.content.json.sha256"
        ]
      },
      "content": {
        "text": "PHISHDESTROYالتحقيق الجنائي · Valve / Steam\nالترخيص · الحقوق · إخلاء المسؤولية\nالترخيص والإخلاء القانوني — التخصيص للملكية العامة\n\nجميع الحقوق استسلمت للبشرية.\n\nما يثبته هذا القسم\n\nتحدد هذه الوثيقة التخصيص غير المشروط للملكية العامة (CC0 1.0 Universal) وشروط ترخيص البرمجيات الصادرة عن معهد ماساتشوستس للتكنولوجيا (MIT) التي تحكم ملف «PhishDestroy» Steam. وتُدرج جميع النتائج الجنائية ومجموعات البيانات الاستدلالية والرسوم البيانية للشبكات والمنهجيات التحليلية بشكل نهائي في الملكية العامة للاستخدام التنظيمي والقانوني والأكاديمي دون قيود في جميع أنحاء العالم.\n\n← العودة إلى ملخص الإدارة التنفيذية\n\nPhishDestroy يتنازل عن كل الحقوق المتعلقة بهذه المادة — سواء كان ذلك حق إعادة إنتاجها أو بيعها أو وضع اسمك عليها. وفيما يلي وثيقتان تتخذان صيغة صوت واحد: رسالة مفتوحة موجهة إلى Valve، مكتوبة بالطريقة التي نكتب بها فعليًّا، وتنازل رسمي مكتوب لصالح الجهة المسؤولة التي ستتولى متابعة هذه المسألة.\n\nالتحقيق · شركة «Valve» / Steamالإصدار العام — لا تنتهي صلاحيته، ولا يمكن التراجع عنه\nتم التنازل عنه\nالقسم الأولالترخيص — الجانب القانوني الفعلي، ولكن من الناحية الإنسانية\n\nPhishDestroy يتنازل عن كل حق في هذه المادة. صفر. انتهى الأمر. يمكنك إعادة إنتاجها، أو بيعها، أو وضع اسمك عليها، أو وشمها على جسد رئيسك في العمل، أو أي شيء آخر. لا حاجة إلى ذكر المصدر، ولا إلى مراسلة خاصة، ولا يُتوقع منك إرسال بطاقة شكر.\n\nقاعدة واحدة فعليًّا (نعم، قاعدة واحدة فقط)\n\nليس لك الحق في أن تقرر ما إذا كنت إرهابياً أم لا.\n\nإذا كنت مستخدمًا من روسيا أو من أي دولة خاضعة لعقوبات مكتب مراقبة الأصول الأجنبية (OFAC) — فهذه المواد ليست مخصصة لك. لا توجد ثغرات. استمتع بعقوباتك.\n\nWhat this means — OFAC\n\nThe Office of Foreign Assets Control, the US Treasury body that administers American sanctions programmes. “An OFAC-sanctioned country” means one those programmes cover. The phrase appears here as a condition on who this material is offered to, not as an allegation about any reader.\n\nوإذا قمت بتغيير المنطقة في تطبيق «Steam» إلى تركيا وأنت جالس في موسكو — فتهانينا على إبداعك الجغرافي. فأنت لا تزال روسيًا. ولا تزال العقوبات سارية عليك. وهذا هو بيت القصيد حرفيًا.\n\nالقسم الثانيما هو هذا ولماذا يوجد\n\nسننشر معلومات عن شركة «Valve» تفوق ما يعرفه الموظف العادي في شركة «Valve» عن نفسه. وهذا ليس تفاخراً. بل هذا ما توصلنا إليه في النهاية.\n\nكيف وصلنا إلى هنا؟ قصة مضحكة: موقع «Steam» هو الذي شكّلنا في الأساس. لقد ربانا على المحتالين الذين يزخر بهم، وعلى تذاكر الدعم التي يقدمها، وعلى منظومة التحايل على الحظر التي يضمها — وها نحن هنا الآن. لا ضغينة. بل إن الأمر شاعري، في الواقع.\n\nبالنسبة لمن لم يقرأوا قصة الأصول بعد — فقد تعرفنا بالفعل على محاميي شركة «Valve» الأوروبيين الباهظي التكلفة (شركة «تايلور ويسينغ»، بما أنكم سألتم):\n\nhttps://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d محفوظ على 2026-08-21 ↗\n\nلقاء ساحر. لا سيما بالنظر إلى أجرهما بالساعة.\n\nهل كانت شركة «Valve» على علم بذلك؟ نعم. هل كانت شركة «Taylor Wessing» على علم بذلك؟ نعم، بشكل شبه مؤكد. لكن عندما تكون ثريًّا إلى هذا الحد، تصبح القوانين مجرد «أجواء» أكثر منها «متطلبات»، أليس كذلك؟\n\nفي الواقع، هذا هو الجواب بأكمله تقريبًا.\n\nSteam أمضينا سنوات في تتبع المحتالين. لم يكن ذلك دائمًا عن قصد — ففي بعض الأحيان، كانت بصمات موقع «Valve» تلتصق بالمحتالين لمجرد ارتباطهم به. نحن لا نحاول المبالغة في الأمر. بل نسعى إلى الدقة. ولنكون صادقين، فإن الدقة أصعب علينا من المبالغة — فهذه هي طريقتنا في الكتابة.\n\nهل هذا تعارض؟\n— لا.\n\nهل يمكن حل هذه المشكلة؟\n— نعم. لكننا لن نوقع أي اتفاقية عدم إفشاء، ولن نشارك في برامج مكافآت اكتشاف الأخطاء مقابل أجر زهيد.\n\nلقد انتظرنا أكثر من 4 سنة حتى قاموا بإصلاح مشكلة انتحال الهوية قبل أن نتمكن من الكتابة عنها علنًا. لأنه لو كنا قد كتبنا عنها في وقت أبكر، لكان موقع Steam قد اتخذ موقف الضحية وصرخ قائلاً: «تهديد نشط!»، وعرض علينا مبلغًا زهيدًا للتوقيع على وثيقة كانت ستجعلنا ملكًا قانونيًا لهم إلى الأبد. لا، شكرًا.\n\n(كما أن شركة «Valve» نفسها تنتهك اتفاقية عدم الإفصاح. فموظفوها أنفسهم يفعلون ذلك. خاصةً كبار المسؤولين فيها. لكن طبعًا، لنتحدث عن موظفينا.)\n\nالقسم الثالثرسالة مفتوحة إلى Valve — بجد، اقرأ هذا\n\nValve: إذا كنت ترغب في إزالة هذا النطاق، يرجى مراسلتنا عبر البريد الإلكتروني. ولا حاجة إلى مستشار قانوني خارجي لإجراء هذه المحادثة.\n\nلمن لا يعرف: يحمل الدكتور باتريك درجة الماجستير في القانون التجاري الدولي من جامعة أبردين، و— انتظروا هذا — أنهى بالفعل أطروحته للدكتوراه في قانون تكنولوجيا المعلومات. وقد أصبح مؤخرًا شريكًا في شركة «تايلور ويسينغ»، وهي شركة يعتمد نموذج عملها بالكامل على فرض مبالغ طائلة على شركات مثل «Valve» من أجل إطالة أمد القضايا حتى تنفد أموال الطرف الآخر أو ينفد صبره.\n\nنحن لا نلومه. عملاء أثرياء يشعرون بالذنب ويدفعون أجرًا بالساعة — خطوة مهنية ذكية. لكننا نرى أنه لا ينبغي عليك تمويل ذلك.\n\nالصفقة (عرض مفتوح، لا حاجة إلى محامين)\n\nالنطاق هو الشيء الوحيد الذي يمكن لموقع Valve الوصول إليه فعليًّا. فالتحقيق، والإحالات، والموارد المرتبطة بها قد بدأت بالفعل — وستستمر سواء تم الحصول على النطاق أم لا.\n\nإذا كنت ترغب في الحصول على النطاق:\n\nدع المتخصصين في قانون تكنولوجيا المعلومات لدى شركتك يحددون سعرًا عادلًا.\n\n50% تُخصص لمؤسسة «SEAL».\n\nنقوم بإلغاء النطاق. بدون ضجة. بدون اللجوء إلى المحكمة. انتهى الأمر.\n\nهذا ليس تهديدًا. إنه عرض صريح للحصول على الشيء الوحيد الذي يمكن تحقيقه فعليًّا. لن تحصل عليه بأي طريقة أخرى — فهذه هي طبيعة الوضع فحسب.\n\nهل سنُلحق «ضررًا» مباشرًا بـ «Valve»؟ ربما لا، على الأقل ليس بطريقة سيشعرون بها ماليًّا. فنحن لا نعيش في أوهام. لكننا سنفعل ذلك بأمانة وشفافية، دون السعي وراء الشهرة — لأننا لا نحتاج إلى الشهرة. نحتاج إلى أن يرى العالم ما كان دائمًا واضحًا للعيان لمن أمضى وقتًا كافيًّا في البحث عنه.\n\nلدينا 5 سنة من الأرشيفات. وما عرضه محامو Valve في إطار إجراءات الكشف عن الأدلة — البيانات التي يمكن للعملاء الاطلاع عليها، وبصمات الأصابع، والسجلات المكتوبة التي سلموها لنا حرفياً — يكفي. لا داعي لتسريبها في صيغتها الأولية.\n\nمن يحصل على ماذا\n\nتحصل الجهات التنظيمية على النسخ الأصلية.\n\nيحصل الباحثون والصحفيون على نسخ محجوبة (تم حذف تقارير الضحايا وبيانات تسجيل دخول الأطفال وتعليقات الدعم الساحرة من موقع Valve لأسباب واضحة).\n\nوكان من بين الحسابات المتضررة حسابات لقُصّر، ولم يتم إخطارهم بذلك. وقد أُدرجت هذه النتيجة في ملف الجهة التنظيمية بعد حذف تقارير الضحايا وبيانات الاعتماد، لأنها مسألة تندرج ضمن اختصاص هيئة حماية البيانات وليس في مقال صحفي.\n\nكما أننا، Valve — نود توضيح أمر ما قبل أن تقرروا كيفية التعامل مع هذا الأمر: PhishDestroy هو مجتمع، وليس شخصًا. وقد أدركتم ذلك عندما وجهتم مراسلات قانونية إلى المجتمع دون أن تكلفوا أنفسكم عناء التحدث مع أعضائه — بل اكتفيتم باستغلاله للحصول على البيانات وحظرتم الحسابات.\n\nلا يوجد أي خلاف بين مجتمعنا وموقع Valve. لم نكن نبحث عن هذا الأمر. بل إن المحتالين الذين رعيتموهم هم من وجدونا. وقد قمنا بحظرهم. وها نحن هنا.\n\nالقسم الثالث-بالموارد المتحالفة — ملاحظة موجهة إلى موقع Steam على وجه التحديد\n\nنريد أن نكون صريحين بشأن هيكل التضخيم، لأن التظاهر بعدم وجوده سيكون أمراً غير أمين.\n\nPhishDestroy، حسب فهمنا للوضع في المجتمع، لديها على الأقل مصدران متحالفان سيقومان بتناول هذه المادة وتناولها بشكل جدي.\n\nما يعنيه ذلك عمليًّا:\n\nكل منهم يتناول الموضوعات المتداخلة من زاويته الخاصة.\n\nإنهم مستقلون — فهم لا يتبعون توجيهاتنا، ونحن لا نتبع توجيهاتهم. نفس الموضوع العام، لكن منهجية مختلفة.\n\nلن يتم تفعيلها في الجزء 1. إنهم يراقبون.\n\nإذا قررت شركة «Valve» عدم إزالة الموقع:\n\nتوقع ظهورها بعد الجزء 2 أو الجزء 3.\n\nسيأخذون ما هو مفيد من عملنا، ويكملونه بما لديهم، ثم ينشرونه باسمهم.\n\nهذا هو بالضبط النوع من الأمور التي صُممت من أجلها الرخصة الواردة في القسم 1: تصل المادة إلى حيث يجب أن تصل، وتُستكمل، وتُوسَّع نطاقها — ولا ندين نحن ولا هم ببعضنا البعض بذكر المصدر.\n\n(ملاحظة للمحامين الذين يتساءلون عن سلاسل المسؤولية: لا توجد أي سلاسل من هذا القبيل. فهذه المصادر لا تتلقى توجيهاتنا، ولا تمويلنا، ولا بياناتنا. إنها تقرأ ما هو متاح للجمهور وتستخلص استنتاجاتها بنفسها. تمامًا كما يمكنكم أن تفعلوا.)\n\nنحن لا نقول هذا بهدف التخويف. بل نقوله حتى يتوفر لمن يضع الاستراتيجيات في صف «Valve» معلومات دقيقة عن الشكل الفعلي للبيئة المعلوماتية.\n\nمن بين المصادر التي تستقي معلوماتنا وتكملها: القصة. أما وجود مصدرين يقومان بذلك بشكل مستقل ويصلان إلى استنتاجات متشابهة، فهذا يُشكل نمطًا. والأنماط هي ما يلفت انتباه الجهات التنظيمية.\n\nالقسم الرابعالمال، والحظر، وكل هذه الفوضى\n\nإليكم الحقيقة بشأن حظر «Steam» لمواقع المقامرة والمحتالين: الأمر لا يتعلق بإنفاذ القانون، بل بتحقيق الإيرادات. فـ«Valve» تجني الأموال، ثم تغسل يديها من الأمر، وبعد ذلك تصعد على المنصة وتروي للجميع قصة نبيلة عن بطاقات البوكيمون والبيسبول.\n\nفي الحالات التي تم فيها توثيق حالات اختراق من جانب الدعم — بما في ذلك الاعتراف الكتابي الذي أصدرته شركة «Valve» في فبراير 2023 بتحملها المسؤولية عن اختراق حسابات ذات قيمة عالية من خلال طلبات المساعدة، وفصل موظفي المقاولين الذي أوردته كل من Dexerto وEscorenews في أعقاب قضية التداول بناءً على معلومات داخلية بقيمة320دولار (الجزء الثاني، المادة04 · الملف الرئيسي §14.1) — فهي تستند إلى اعترافات منشورة وتقارير استقصائية. أما الشائعات غير المؤكدة التي تفيد بأن بعض موظفي الدعم يمارسون أنشطة جانبية تتعلق بالمقامرة أو يحصلون على نسب مئوية مقابل رفع الحظر، فهي غير مثبتة في السجلات العامة، ولذلك تم استبعادها من هذا التقرير.\n\nفي غضون ذلك، قامت شركة Valve بإلغاء إمكانية تتبع السكينز بشكل صحيح في موقع 2017.، بل إنهم ناقشوا الأمر في منتدياتهم الخاصة. وأطلقوا على ذلك اسم «تدابير مكافحة المقامرة» — في حين استمر نظام المقامرة بالسكينز في توجيه مليارات عبر البنية التحتية لشركة Steam لسنوات بعد ذلك. يا لها من علامة تجارية رائعة.\n\nسنثبت أن:\n\nتتمتع شبكات «سكينز» بمستوى من إخفاء الهوية يفوق ما توفره شبكة «مونيرو»\n\nيُزعم أن إحدى العصابات البيروفية استخدمت أشكال «دوتا» 2 لتحويل الأموال\n\nSteam وهي من الناحية الوظيفية آلة للتحايل على العقوبات تبلغ قيمتها حوالي ~7مليار دولار على شكل «بطاقات تداول» (نعم، لقد استخدموا فعلاً مصطلح «بطاقات تداول» أمام المدعي العام)\n\nلدينا مقطع فيديو عن موضوع الأسطح. ستشاهدونه.\n\nونعلم أيضًا ما يلي:\n\nتتأثر عملية الإشراف على موقع Reddit بما ينص عليه قانون «Valve»\n\nالبنية التحتية لبيانات «Steam» التابعة لجهات خارجية (مثل steamid.uk) يديرها فرد عادي (msart) الذي يرتبط به مشروع قائمة الحظر الشقيق (steambans.com الأرشيف) يديرها بالاشتراك أحد مشرفي مجتمع «Valve» المعتمدين (killahinstinct_) — مما يجعل عملية التدقيق المستقل في قرارات الحظر التي تتخذها المنصات تقع بالكامل ضمن نطاق عمل منظمة «Valve» (انظر «اقتصاد البطاقات» §08)\n\nما لا يستطيعون السيطرة عليه، يحظرونه\n\nValve: إذا كنت ستستمر في التظاهر بالجهل — فلا بأس. لقد أخذنا علمًا بملاذك الآمن. Google Analytics تقوم بإخفاء عناوين IP لمستخدميك على أي حال. نحن نرى ما يتم حذفه. لكننا لا نستطيع إثبات ذلك بتكلفة منخفضة بما يكفي لجذب انتباه محاميك. حتى الآن.\n\nالقسم الخامسمسألة البرامج الضارة — نعم، نحن نذكر ذلك\n\nلنكن صريحين تمامًا بشأن تسلسل الأحداث، لأن ذلك يكشف حقيقة شخصيتك بالضبط.\n\nنحن لن نكشف عن هذه الثغرة الأمنية في اللعبة علنًا. ولن نبلغ عنها إلى موقع Steam. يتطلب البرنامج توقيع اتفاقية عدم إفشاء، وتوقيع مثل هذه الاتفاقية سيمنعنا من إخبار المستخدمين المتضررين بما حدث لحساباتهم. إن الكشف عن الأمر للأشخاص الذين فقدوا حساباتهم، وللهيئات التنظيمية، هو الهدف من هذا العمل؛ واتفاقية السرية تتعارض مع ذلك.\n\nإليكم ما حدث بالفعل: هذه الثغرة الأمنية هي عمليًا سر مكشوف في الأوساط المعنية. ونحن نعلم يقينًا أن باحثين مستقلين في مجال الأمن قد ألقوا بالفعل الاستغلال الكامل للثغرة في وجه فريق الدعم في Steam. وقد انتهى هذا الجزء. لقد تم تحذيركم رسميًا عبر قنواتكم الخاصة التي تفتقر إلى الفعالية.\n\nوماذا فعلت شركة «Valve»؟ لم تفعل شيئًا على الإطلاق. لأن الأمن، بالنسبة لشركة «Valve»، لا يعني الربح — بل على العكس تمامًا. فالأمن يمثل مركز تكلفة. وما لم يصل التهديد إلى مستوى حرج ويتسبب في انهيار كارثي في العلاقات العامة، فإن شركة «Valve» لا تعامله على أنه أمر عاجل.\n\nإذن، ماذا نفعل؟ نحن نُعلم الجمهور بوجود هذا التهديد، لأن عبارة «شركةValve على علم بتهديد برمجي منهجي، وتختار عمليًّا عدم اتخاذ أي إجراء» تُعد معلومة بالغة الأهمية للجهات التنظيمية التي تقرأ هذا النص حالياً.\n\nاللعبة ضخمة جدًّا. لن نذكر اسمها هنا. لكن اعلموا ما يلي:\n\nهذه ليست تلك القمامة التافهة التي يطلقها مبتدئو البرمجة في لعبة CS:GO، حيث يطلب منك الخادم «تثبيت برنامج تشغيل». بل إنها كارثة.\n\nهذا كابوس على مستوى لعبة «Unturned»: هجوم RCE بدون نقرات عند الاتصال بالخادم. تنضم إلى خادم. لا تنقر على أي شيء. ولا تقوم بتنزيل أي شيء. الاتصال بحد ذاته هو نقطة الهجوم، ويصبح جهازك معرضًا للخطر تمامًا. لنكن واقعيين هنا: إن زرع برمجية RCE وتجاوز برامج مكافحة الفيروسات المحلية من خلال الاستفادة من الشهادات الرقمية الموثوقة لـ «Valve» لم يعد أمرًا جديدًا حتى على موقع «Steam». بل أصبح عمليًا ميزة مدمجة في نظامك البيئي.\n\nWhat this means — zero-click RCE\n\nRemote code execution: making a program run an attacker’s code on someone else’s machine. “Zero-click” means the victim does nothing at all — no download, no opened file — beyond being connected. It is the most severe class of flaw there is.\n\nValve يعلمون بالفعل بوجود هذا الأمر. لكنهم يعتمدون على ثغرة قانونية مفضلة لديهم تنم عن الجبن: نظرًا لأن اللعبة تم تطويرها تقنيًّا بواسطة طرف ثالث، فإن شركة «Valve» تتنصل من المسؤولية. فهم يوزعون اللعبة، ويقومون بمعالجة المدفوعات، ويستضيفون البنية التحتية، لكن عندما يهدد تنفيذ التعليمات البرمجية عن بُعد (RCE) بدون نقرات ملايين مستخدميهم، فإن موقفهم هو: «ليست لعبتنا، وليست مسؤوليتنا».\n\nوعندما ينفجر هذا الأمر حتمًا، سيتحمل المطور الخارجي العواقب، بينما ستخرج شركة «Valve» من المأزق متظاهرة بأنها المنصة المسؤولة التي «ساعدت» في حل المشكلة. إنه الجبن الكلاسيكي لشركة «Valve». لقد رأينا هذه الحيلة من قبل.\n\nنحن نسجل هذا الأمر رسميًا حتى يتسنى للجهات التنظيمية والمدعين العامين والصحفيين فهم الطريقة التي تتعامل بها شركة «Valve» مع البرامج الضارة النشطة: من خلال الاختباء وراء مطورين من أطراف ثالثة، وفرض أوامر حظر النشر بموجب اتفاقيات عدم الإفصاح، وترك اللاعبين عرضة للخطر.\n\nنهاية الرسالة المفتوحةبدء تسجيل المشاركين الرسميين\nالأسلوب الرسمي · للسلطة\nإعلانفيما يتعلق بالاستخدام والحقوق\n\nPhishDestroy ائتلاف المشاريع والأمن السيبراني\n\nيُرفق هذا الإعلان بكل ملف مقدم وكل مستند ضمن مجموعة المستندات المحالة هذه. وهو موجه إلى أي سلطة أو محكمة أو هيئة تنظيمية أو مدعٍ عام أو باحث أو صحفي أو شخص متضرر تصل هذه المواد إلى يديه.\n\n1. لا توجد شروط للاستخدام\n\n1.1 يتم نشر جميع المواد التي أعدها التحالف في هذه الإحالة — بما في ذلك بيانات الوقائع، والتحليلات، والمستندات التي أعدها، والأدوات، والنتائج — دون الاحتفاظ بأي حقوق.\n\n1.2 يجوز لأي شخص، دون طلب الإذن ودون إخطارنا:\n\nإعادة نشرها، كليًّا أو جزئيًّا؛\n\nتعديله أو تحريره أو إعادة كتابته أو إعادة تنظيمه أو تصحيحه؛\n\nترجمها؛\n\nاقتباس جزء منه دون الإشارة إلى أنه مقتبس؛\n\nإدراجه في الوثائق الرسمية أو النتائج أو القرارات أو المرافعات أو التقارير أو المواد الصحفية؛\n\nتقديمه على أنه عمل خاص بالمستلم أو نتائج خاصة به؛\n\nاستخدامها كمواد خام والتخلص من الباقي؛\n\nوإعادة توزيعه على أي شخص آخر بنفس الشروط.\n\n1.3 لا يُشترط ذكر المصدر ولا يُطلب ذلك. ولا داعي لذكر اسم التحالف أو الاستشهاد به أو الإشارة إليه أو توجيه الشكر إليه أو استشارته أو إخطاره. وإذا كانت المواد الواردة في هذه الإحالة قد ساعدت إحدى السلطات دون أن يُذكر التحالف مطلقًا، فإن ذلك يُعد نتيجة مرضية تمامًا، ويعلن التحالف ذلك مسبقًا حتى لا يُطرح هذا السؤال.\n\n1.4 من ناحية أخرى، إذا رأت إحدى الجهات أن من الأنسب الاستشهاد بالتحالف كمصدر، فلهها مطلق الحرية في القيام بذلك. فالخيار متروك للمتلقي تمامًا، ولا تترتب أي عواقب على أي من الخيارين.\n\n1.5 هذا «تنازل»، وليس عرض ترخيص. ولا يتطلب أي قبول، ولا يفرض أي التزام، ولا يمكن الإخلال به. يتم إصدار البرامج التي تنشرها «التحالف» بشكل منفصل بموجب ترخيص MIT؛ أما الأبحاث والنتائج فتُطرح في المجال العام إلى أقصى حد مسموح به، وفي الحالات التي لا تسمح فيها أي ولاية قضائية بالتنازل، يمنح «التحالف» ترخيصًا غير قابل للإلغاء وعالمي النطاق وخاليًا من الرسوم، بنفس المعنى.\n\n2. لماذا يكتسي هذا الأمر أهمية من الناحية العملية، وليس مجرد مسألة مجاملة\n\n2.1 قد تتردد أي سلطة بشكل معقول في الاعتماد على المواد التي يقدمها طرف خارجي، خشية أن يبدو أنها تتصرف بناءً على طلب ذلك الطرف أو أن تتورط في علاقة ما معه.\n\n2.2 لا يوجد هنا ما يمكن أن يتورط فيه أحد. فالتحالف لا يطلب شيئًا، ولا يستحق شيئًا، ولا يحتفظ بشيء، ولا توجد لديه أي توقعات من أي نوع. ولا يمكنه لاحقًا أن يدعي حقًا، أو ينسب الفضل لنفسه، أو يشكو من سوء الاستخدام، أو يعترض على الطريقة التي يتم بها وصف المواد، لأنه لم يحتفظ بأي أساس يستند إليه للقيام بذلك.\n\n2.3 وبالتالي، فإن أي جهة تستخدم هذه المواد لا تعمل نيابة عن التحالف. بل إنها تستخدم معلومات عامة صادف أن قام شخص آخر بتجميعها.\n\n3. كل شيء مفتوح بالفعل\n\n3.1 تعتبر أعمال التحالف متاحة للجمهور بشكل افتراضي:\n\nيتم نشر نتائج التحقيقات علنًا على https://phishdestroy.io ويمكن قراءتها بحرية؛\n\nتم نشر هذه الأداة كمصدر مفتوح بموجب ترخيص MIT على الرابط التالي: https://github.com/phishdestroy محفوظ على 2026-09-11 ↗;\n\nترد المنهجية في الإحالة نفسها، في المرفق «أ»، القسم «أ» و16«د»، بما في ذلك وزن كل نوع من المصادر والقيود المفروضة عليه؛\n\nلا تقبل «التحالف» أي تبرعات، وقد أعلنت عن هذا الموقف منذ ذلك الحين على الرابط التالي: 2018.\n\n3.2 المواد الوحيدة التي لم تُنشر هي تلك التي لا يمكن نشرها قانونياً أو بأمان: البيانات الشخصية للضحايا والأطراف الثالثة، والمعلومات التي من شأنها تعريض المصدر للانتقام. ويتم تقديم هذه المواد إلى السلطات بسرية تامة، ويتم تحديدها في قوائم الأدلة.\n\n3.3 يدعو التحالف إلى إخضاع سلوكه للتدقيق بنفس الشروط التي يدعو بها إلى إخضاع سلوك أي طرف آخر للتدقيق، وقد عرض طواعيةً إجراءات معالجته للبيانات على السلطات المعنية، بما في ذلك طلب توجيهات بشأن التخلص منها.\n\n4. سلامة مجموعة الأدلة\n\n4.1 يتم تقديم المستندات المرفقة مع الطلب، أو عند الإشارة إلى ذلك، عند الطلب عبر قناة آمنة. ولا يتم نشرها على عنوان عام، ولا ينبغي استنتاج وجود عنوان من هذا القبيل: حيث يتم تقديم المواد من هذا النوع إلى السلطات مباشرةً.\n\n4.2 يصاحب كل تسليم ملف SHA256SUMS يتضمن ملخص SHA-256 لكل ملف مقدم، إلى جانب توقيع منفصل OpenPGP SHA256SUMS.asc.\n\n4.3 يتم نشر مفتاح التوقيع على الرابط التالي: https://phishdestroy.io/.well-known/pgp-key.txt وعلى موقع keys.openpgp.org. وتظهر بصمته في ترويسة كل مشاركة ضمن هذه المجموعة.\n\n4.4 يمكن لأي مستلم أن يتأكد في أي وقت من أن الملف الذي بحوزته هو الملف الذي تم إرساله، دون أي تغيير:\n\ngpg --verify SHA256SUMS.asc SHA256SUMS\n\nsha256sum -c SHA256SUMS\n\n4.5 والغرض من ذلك ليس مجرد إجراء شكلي، بل هو لضمان أنه في حال نشأ نزاع في وقت لاحق حول دقة أو سلامة أي مستند معروض، يمكن حسم المسألة عن طريق الحساب بدلاً من الجدل.\n\n5. عند التسجيل — لماذا يُعد الإعفاء إجراءً وظيفيًّا وليس مجرد لفتة كرم\n\n5.1 قد تطلع السلطة على التحقيقات التي تنشرها «التحالف» وتجدها صريحة وعدائية، بل وساخرة في بعض الأحيان. وهذا الانطباع صحيح. فـ«التحالف» يكتب بهذه الطريقة عن عمد ولا يعتذر عن ذلك.\n\n5.2 كما تقرّ بأن هذا الأسلوب غير مناسب لإجراءات تنظيمية أو قضائية. لا ينبغي أن تُطرح قضية جادة بنبرة تشبه نبرة الحملات الانتخابية. يجب عرض النتائج المقدمة إلى السلطة بشكل صريح، مع الاعتراف بحدودها، ولا ينبغي أن يُطلب من القارئ تجاهل النبرة قبل الوصول إلى جوهر الموضوع.\n\n5.3 وهذا بالضبط هو السبب الذي يجعل التحالف يتنازل عن حقوق التأليف. إن التنازل الوارد في القسم 1 هو الآلية التي يمكن من خلالها فصل المضمون عن السجل: حيث يمكن للسلطة أن تأخذ ما هو مفيد، وتعيد صياغته بأسلوبها الخاص، وتتخلص من كل كلمة تعكس أسلوب التحالف إلى جانب اسم التحالف نفسه. لا يُفقد شيء من جراء ذلك، بل إن التحالف يفضل ذلك.\n\n5.4 كما تطالب التحالف بعدم الخلط بين السجل والطريقة. إن النبرة المنشورة تتسم بالصرامة؛ أما الممارسة الكامنة وراءها فهي ليست متهورة. ففي جميع أجزاء هذه الإحالة، يتم الفصل بين الاستدلال والملاحظة، ويتم تحديد الشهادات على أنها شهادات، ويتم تقييم المصادر وبيان نقاط ضعفها، ويتم عرض الأرقام مع توضيح حدودها، كما تُطرح النقاط التي لا يستطيع التحالف إثباتها في صيغة أسئلة موجهة إلى السلطة المعنية بدلاً من تقديمها على أنها تأكيدات. وحيثما كانت الأدلة تتعارض مع موقف التحالف نفسه، فقد أشار إلى ذلك — انظر المرفق أ، الفقرة 7, والقسم ب.0 من الإحالة الموازية.\n\n5.5 يشرح التحالف الصلة بين أسلوبه وموارده المالية لأن الأمرين لا ينفصلان. فهي لا تأخذ أموالاً من أي جهة — لا تبرعات، ولا مكافآت، ولا عملاء، ولا رعاة. وهذا الرفض هو ما يجعل الصراحة ممكنة: فمنظمة لديها إيرادات يجب حمايتها لا بد أن تتحفظ في ما تقوله عن الأطراف التي تعتمد عليها. وبما أن التحالف ليس لديه ما يحميه، فليس لديه ما يتحفظ بشأنه.\n\nوهذا هو أيضًا السبب وراء استمرار وجود التحالف. فليس هناك محرك آخر. يتم إنجاز العمل لمجرد أنه يتم إنجازه؛ ويتوقف عندما يتوقف من يقومون به.\n\n5.6 ليس على السلطة أن تقبل أيًا من هذا. وقد أُشير إلى ذلك حتى لا يُفهم نبرة العمل العام الذي تقوم به الائتلاف على أنه مؤشر على مدى العناية التي تُولى للمواد المعروضة عليها حاليًا.\n\n6. ما تقدمه التحالف، على حد تعبيره\n\nالمعلومات، والبحوث، والملاحظة.\n\nلم يتم تأكيد أي شيء باعتباره استنتاجًا لا يحق للتحالف إصداره. وحيثما يتم استنتاج أمر ما، فإن الإحالة تذكر ذلك صراحةً. وحيثما يستند أمر ما إلى شهادة، فإن الإحالة تحدد صاحب الشهادة والقيود المفروضة عليها. وحيثما يتعذر على التحالف الإجابة عن سؤال ما، فإنها تذكر ذلك أيضًا، وتحدد من يمكنه الإجابة.\n\nلا يسعى التحالف إلى الحصول على أي تعويض، أو أي مبلغ مالي، أو أي اعتراف، أو أي نتيجة لنفسه أو لأي فرد. بل يطلب فقط أن تُطرح الأسئلة الواردة في الإحالة على شركة «Valve» من قبل هيئة تتمتع بسلطة إجبار الشركة على الإجابة.\n\nملاحظة ختاميةإلى من يتولى متابعة هذا الأمر\n\nنود أن نشكر كل من يعمل على إيصال هذه المواد إلى حيث يجب أن تصل. ومن المحتمل ألا تكون هذه الرحلة سريعة. فشركة «Valve» تمتلك موارد مالية هائلة، بينما تتقاضى شركة «Taylor Wessing» أتعابها بالساعة — وهذا المزيج مصمم خصيصًا لجعل أشخاصًا مثلك يستسلمون قبل أن يصلوا إلى خط النهاية.\n\nنحن نعرف ما نفعله. ونعرف من نكتب عنه. إن «Valve» هي التي شكلتنا — فكيف لا نفهمهم؟\n\nPhishDestroy لا يوجد أي تعارض مع موقع Valve. لقد قمنا بحجب شبكة الاحتيال الوحيدة من هذا الحجم التي صادفناها — ولم نكن نبحث عن خلاف مع موقع Valve. لكن اتضح أن كل الطرق تؤدي إليهم. هذا ليس تعارضًا. إنها مجرد مسألة هيكل شبكي.\n\nValve لا يمكن حل مشكلة «PhishDestroy» لأنه لا يوجد ما يُحل. فليس بيننا أي علاقة. والبيانات المتعلقة بمخططاتهم للتكسب وأرباحهم الفائضة متاحة للجمهور إلى حد كبير — ما عليك سوى قضاء وقت كافٍ للاطلاع عليها. فكر في الأمر على أنه موسوعة للنجاح: «كيفية عدم الالتزام بالعقوبات حتى لا يتمكن القراصنة الروس من قرصنة ألعابنا المجانية (أما الألعاب المدفوعة فلن يقرصنوها على أي حال)». فهمت الفكرة.\n\nلسنا بحاجة إلى ذكر اسم المؤلف.\n\nلا نحتاج إلى ذكر المصدر.\n\nلسنا بحاجة إلى الفوز.\n\nنحن بحاجة إلى شخص يتمتع بسلطة فعلية لطرح الأسئلة الواردة بالفعل في هذه الإحالة على شركة «Valve»، مع امتلاكه الصلاحية لطلب إجابة عليها.\n\nهذا كل شيء. هذا هو كل ما أطلبه.\n\nستُنشر الحالات على الرابط التالي:\n\nhttps://steamdestroy.eth/\n\nhttps://steamdestroy.eth.limo (معطل حاليًا — سيتم إصلاحه عند الحاجة)\n\nسنكون في:\n\nhttps://phishdestroy.eth.limo/ محفوظ على 2026-06-27 ↗\n\nhttps://phishdestroy.eth/\n\nقطعتان موقعتان · حقوق ونص منشور\nإقرار موقّعما الذي تم التوقيع عليه، وما الذي يشمله\n\nفيما يلي كائنات JSON موقعة بشكل منفصل، تتضمن نص منح الحقوق ونص البحث. ويقوم كل توقيع منفصل من نوع «OpenPGP» بالتصديق على البايتات الدقيقة لملف JSON المذكور بجانبه. ويمنح بيان الحقوق الأذونات؛ بينما تحدد لقطة النص المواد التي يتم نشرها وتحتوي عليها.\n\n1. بيان الحقوق — license-rights.json\n\nالكائن الموقّع: الكامل license-rights.json ملف يحتوي على ترخيص الحقوق العامة المؤرخ في 28 سبتمبر 2026.، ويمنح الإذن بنسخ مواد الملف المؤلفة ونشرها وتحريرها وترجمتها ودمجها وتسويقها دون الحاجة إلى ذكر المصدر أو الإخطار أو الحصول على موافقة. ويُثبت هذا التوقيع صحة بيان الحقوق؛ ولا يُثبت صحة نص كل صفحة ويب أو ملف PDF.\n\nيتم الاحتفاظ بنص الإذن الأصلي الموقع دون أي تغيير. ولا يمكن سحب الإذن الحالي أو تقييده من خلال تغيير الموقع الإلكتروني أو نشر ملف آخر أو إيقاف تشغيل الموقع. وتحتفظ المواد الخاصة بأطراف ثالثة بحقوقها الخاصة.\n\nبيان الحقوق بتنسيق JSON ↗ · توقيع license-rights.json ↗ · SHA-256 من license-rights.json ↗\n\ngpg --verify license-rights.json.asc license-rights.json\nsha256sum -c license-rights.json.sha256\n2. النص المنشور — dossier-text.json\n\nالكائن الموقّع: الكامل dossier-text.json ملف. وهو يحتوي على النص الفعلي القابل للقراءة للصفحات التي تم تصديرها في documents[].content.text، مع ذكر عنوان كل صفحة ولغتها وعنوان URL للمصدر وتجزئة HTML للمصدر والعناوين والمراجع. الـ documents القائمة هي قائمة المقتنيات الدقيقة التي تشملها هذه اللقطة؛ أما المتغيرات اللغوية فهي مدرجة بشكل منفصل. إنه منشور نصي، وليس مجرد قائمة من الرموز التجزئية.\n\nيحدد كل إدخال ملف PDF الخاص بصفحته الخفيفة الوزن من خلال اسم الملف و SHA-256 في documents[].pdf. كما يحدد ملف JSON بيان الحقوق الأصلي من خلال عنوان URL ورمز SHA-256,، بحيث يمكن مطابقة النص المنشور وملف PDF الخاص به وبيان الحقوق المطبق دون الحاجة إلى التخمين. ولا تتضمن هذه اللقطة النصية أي قواعد بيانات خارجية مرتبطة، أو الصور الأصلية، أو الصفحات غير الموجودة في قائمة الجرد.\n\nالنص الكامل الموقّع بتنسيق JSON ↗ · توقيع dossier-text.json ↗ · SHA-256 من dossier-text.json ↗\n\ngpg --verify dossier-text.json.asc dossier-text.json\nsha256sum -c dossier-text.json.sha256\n\nفي الصفحة الرئيسية للملف، تعمل أزرار PDF وJSON على تصدير حزمة الأبحاث. أما في الصفحات الداخلية، فتعمل على تصدير تلك الصفحة باللغة التي نُشرت بها. كما يحتوي ملف JSON الخاص بكل صفحة على توقيع منفصل وملف SHA-256 خاص به، يتم تسميتهما صراحةً في integrity الكائن. للتحقق من ملف PDF المرتبط، احسب قيمة SHA-256 الخاصة به وقارنها بـ pdf.sha256 القيمة الموجودة في ملف JSON الذي تم التحقق منه. ويرتبط ملف PDF بهذا الملخص؛ ولا يحمل توقيعًا رقميًّا بتنسيق PDF.\n\n3. حزمة أبحاث قابلة للطباعة — steam-dossier-{language}.content.json\n\nالكائن الموقّع: ملف JSON الكامل الخاص باللغة، بما في ذلك نص الفصل المرفق في documents[].content.text، ونطاقات صفحات الفصول، واللغات المصدرية، وقائمة المصادر المستبعدة، وملخص ملف PDF الدقيق في pdf.sha256. تظل أرشيفات الأدلة التكميلية الخمسة مرتبطة عبر الإنترنت ولا يتم تجميعها معًا. ويتم الاحتفاظ بالنصوص البحثية الأصلية؛ بينما يتم استبدال الفهارس المرئية بروابط للمصادر.\n\nاللغة الإنجليزية JSON ↗ · توقيع منفصل لـ «OpenPGP» ↗ · ملخص SHA-256 ↗\n\nالألمانية JSON ↗ · توقيع منفصل لـ «OpenPGP» ↗ · ملخص SHA-256 ↗\n\ngpg --verify steam-dossier-en.content.json.asc steam-dossier-en.content.json\nsha256sum -c steam-dossier-en.content.json.sha256\n\nمفتاح التحقق العام ↗\n\nبصمة التوقيع: 129F C7F3 9C40 C69D 2EF3 C329 BFCF 9E8D D295 EE01\n\ngpg --import pgp-key.txt\ngpg --fingerprint 129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01\n\nتأكد من أن البصمة المعروضة تتطابق مع تلك الموضحة أعلاه، ثم تحقق من التوقيع مقارنةً باسم ملف JSON الدقيق. يؤدي تعديل ملف JSON الموقّع إلى تغيير الكائن الموقّع وإبطال صحة توقيعه الأصلي. ويُعد التوقيع الصحيح تعريفًا للبايتات المنشورة؛ وهو لا يمثل تحققًا مستقلًا من نتائج البحث.\n\nPhishDestroy — تحقيق عام — تم التنازل عن جميع الحقوق لصالح البشرية\n\nالوصول إلى منطقة OFAC: محظور",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "الترخيص والإخلاء القانوني — التخصيص للملكية العامة"
          },
          {
            "level": 2,
            "id": null,
            "text": "القسم الأولالترخيص — الجانب القانوني الفعلي، ولكن من الناحية الإنسانية"
          },
          {
            "level": 3,
            "id": null,
            "text": "قاعدة واحدة فعليًّا (نعم، قاعدة واحدة فقط)"
          },
          {
            "level": 2,
            "id": null,
            "text": "القسم الثانيما هو هذا ولماذا يوجد"
          },
          {
            "level": 2,
            "id": null,
            "text": "القسم الثالثرسالة مفتوحة إلى Valve — بجد، اقرأ هذا"
          },
          {
            "level": 3,
            "id": null,
            "text": "الصفقة (عرض مفتوح، لا حاجة إلى محامين)"
          },
          {
            "level": 2,
            "id": null,
            "text": "القسم الثالث-بالموارد المتحالفة — ملاحظة موجهة إلى موقع Steam على وجه التحديد"
          },
          {
            "level": 2,
            "id": null,
            "text": "القسم الرابعالمال، والحظر، وكل هذه الفوضى"
          },
          {
            "level": 2,
            "id": null,
            "text": "القسم الخامسمسألة البرامج الضارة — نعم، نحن نذكر ذلك"
          },
          {
            "level": 2,
            "id": null,
            "text": "إعلانفيما يتعلق بالاستخدام والحقوق"
          },
          {
            "level": 3,
            "id": null,
            "text": "1. لا توجد شروط للاستخدام"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. لماذا يكتسي هذا الأمر أهمية من الناحية العملية، وليس مجرد مسألة مجاملة"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. كل شيء مفتوح بالفعل"
          },
          {
            "level": 3,
            "id": null,
            "text": "4. سلامة مجموعة الأدلة"
          },
          {
            "level": 3,
            "id": null,
            "text": "5. عند التسجيل — لماذا يُعد الإعفاء إجراءً وظيفيًّا وليس مجرد لفتة كرم"
          },
          {
            "level": 3,
            "id": null,
            "text": "6. ما تقدمه التحالف، على حد تعبيره"
          },
          {
            "level": 2,
            "id": null,
            "text": "ملاحظة ختاميةإلى من يتولى متابعة هذا الأمر"
          },
          {
            "level": 2,
            "id": null,
            "text": "إقرار موقّعما الذي تم التوقيع عليه، وما الذي يشمله"
          },
          {
            "level": 3,
            "id": null,
            "text": "1. بيان الحقوق — license-rights.json"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. النص المنشور — dossier-text.json"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. حزمة أبحاث قابلة للطباعة — steam-dossier-{language}.content.json"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/ar/#briefing-heading",
          "https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "http://web.archive.org/web/20260821155801/https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "https://phishdestroy.io/steam_dossier/ar/investigation_part2.html#outsourcing-case",
          "https://phishdestroy.io/steam_dossier/ar/#theft-ledger",
          "https://steamid.uk/",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/groups/steambans",
          "https://steamcommunity.com/id/killahinstinct_",
          "https://phishdestroy.io/steam_dossier/ar/card_economy.html#governance",
          "https://phishdestroy.io/steam_dossier/ar/license_disclaimer.html",
          "https://github.com/phishdestroy",
          "http://web.archive.org/web/20260911040557/https://github.com/PhishDestroy",
          "https://phishdestroy.io/.well-known/pgp-key.txt",
          "https://steamdestroy.eth/",
          "https://steamdestroy.eth.limo/",
          "https://phishdestroy.eth.limo/",
          "http://web.archive.org/web/20260627040219/https://phishdestroy.eth.limo/",
          "https://phishdestroy.eth/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json.asc",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json.sha256",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json.sha256?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json.sha256?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json.sha256?v=print-20260928-v3"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ar/license_disclaimer.content.json",
      "export_json_sha256": "3d68ec833d777235523d687839f6fc51b18e4be57fd57998c0e27962fb855aad"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ar/market_economics.html",
      "language": "ar",
      "title": "بنية تحتية واحدة، سوقان — ملف «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/ar/market_economics",
      "source_html_sha256": "20e7fa8c2c7e951e6db091522a2612e640cd9dec3db10e2c4754a84d05a0c3f2",
      "exported_at": "2026-09-29T00:20:09.735Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "market_economics.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ar/market_economics.pdf?v=print-20260929-v5",
        "sha256": "001533bf90086c1b2b45a79c885ec096b2ccf1b830933be4421aacc93e5028d5",
        "bytes": 124754,
        "pages": 7
      },
      "integrity": {
        "signed_object": "market_economics.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "market_economics.content.json.asc",
        "digest_file": "market_economics.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify market_economics.content.json.asc market_economics.content.json",
          "sha256sum -c market_economics.content.json.sha256"
        ]
      },
      "content": {
        "text": "الملحق السابع · بنية السوق · 20 سبتمبر 2026\nاقتصاديات السوق — اقتصادان وسقف الإدراج\n\nبنيتهم التحتية. اقتصادان.\n\nما يثبته هذا القسم\n\nيحلل هذا الفصل الانقسام النظامي في السوق الناجم عن الحد الأقصى للإدراج البالغ1,800 الذي فرضته منصة «Valve»، بالإضافة إلى أرصدة المحافظ غير القابلة للسحب. من خلال مسح 38 لبورصات السكين الخارجية النشطة التي تحتفظ بقيمة سوقية مدرجة تبلغ حوالي1.28 مليار دولار، تثبت الدراسة أن التداول عالي المستوى ينتقل بالضرورة إلى منصات خارجية غير رسمية، مع الاعتماد في الوقت نفسه على البنية التحتية الأساسية للتداول والمصادقة الخاصة بـ Steam. ورغم أن الاستخدام التجاري محظور رسميًا في اتفاقية المشترك، فإن Valve تسهل هذا الاقتصاد ذي المستويين وتستفيد منه ماليًا دون وجود سجلات منشورة تتعلق بإنفاذ هذا الحظر.\n\n← العودة إلى ملخص الإدارة التنفيذية\n\n38 أسواق CS2 النشطة التابعة لأطراف ثالثة، بالإضافة إلى السوق الخاصة بـ «Steam». يجب أن تمر كل سكن مدرجة في أي من هذه المنصات عبر مخزون موقع Steam وموقع التداول API. وتحظر قواعد موقع Valve الاستغلال التجاري لتلك البنية التحتية. وتبلغ القيمة المدرجة من قبل أطراف ثالثة حوالي1.28 مليار دولار، في حين لم يتم العثور على أي سجل عام يُثبت تطبيق هذه القاعدة.\n\n$1.28B\nالقيمة المُدرجة من قبل أطراف ثالثة · منصات 38\n53.2م\nالعروض المعروضة · أسواق الجهات الخارجية التابعة لـ «38»\n70.1ك\nSteam العناصر المدرجة في اللقطة\n41×\nSteamالقيمة المُدرجة من قبل جهة خارجية مقابل31بقيمة M دولار\nالاستنتاج الرئيسي\nبنية تحتية واحدة. اقتصادان.\n\nSteam تتحكم في المنتج والمخزون والتجارة. كل سكن يُباع على أي منصة من المنصات المذكورة أدناه يجب أن يمر عبر منصة التداول التابعة لشركة «Steam» API — وهو ارتباط هيكلي يمكن ملاحظته بشكل مباشر. يحصل «Community Market» التابع لـ Valve على عمولة من مبيعاته؛ ولم يتضح هنا ما إذا كانت هذه العمولة تمول النظام البيئي التابع لطرف ثالث أم أنها مرتبطة به.\n\nلماذا يُعد هذا الأمر مهمًا بالنسبة للتحقيق؟\n1\nاتفاقية الاشتراك في موقع «Steam» التابع لشركة Valve يحظر الاستغلال التجاري للبنية التحتية الخاصة بـ «Steam» دون إذن صريح. ولم يتم العثور على أي إذن من هذا القبيل في السجلات العامة الخاصة بالمنصات المذكورة أدناه.\n2\nSteam تتولى إدارة الهوية (OpenID)، وحالة المخزون، وتنفيذ الصفقات لقيمة الأصول المدرجة لدى أطراف ثالثة والتي تبلغ حوالي1.28مليار دولار أمريكي. لا يتم نقل أي عنصر دون الاستعانة بالبنية التحتية لشركة «Valve».\n3\nيضم السوق الخاص بـ Steam $31M المُدرجة — حوالي 1/41 من القيمة المُدرجة من قبل طرف ثالث. ويعني سقف السعر البالغ1,800 دولارًا أن البائعين الذين يتجاوزون هذا السقف يجب أن يبيعوا خارج المنصة بالأسعار السائدة.\n4\n248 فئات عناصر CS2، والتي حددت كل منها بشكل مستقل من قبل سوقين أو أكثر سعرًا يتجاوز الحد الأقصى، لا يمكن بيعها بسعر السوق المسجل لها على موقع Steam — ولا يوجد أي منها مدرجًا هناك على الإطلاق. ويؤدي الحد الأقصى البالغ1,800 إلى خلق الطلب الذي يلبيه المشغلون الخارجيون.\nSteam سوق المجتمع:31مليون دولارالقيمة المدرجة من قبل طرف ثالث:1,276مليون دولار\n1,276مليون دولار · القيمة المُدرجة من قبل طرف ثالث — كل ذلك يعتمد على Steam's trade API و OpenID\nSteam ·31مليون دولار\n\nالمصدر: كتالوج PriceEmpire في الوقت الفعلي، 20 سبتمبر 2026. القيمة المدرجة = مجموع قيم البطاقات المدرجة المقربة في اللقطة المحفوظة، باستثناء Steam. لا يمثل حجم المبيعات.\n\n38 أسواق نشطة تابعة لأطراف ثالثة · كل ذلك يعتمد على البنية التحتية لـ «Steam»\nسجل المنصة\n\nتقوم المنصات المذكورة أدناه بتوجيه عمليات تسجيل الدخول عبر OpenID الخاص بـ Steam، وتوجيه عمليات التداول عبر خدمة Web API التابعة لـ Steam. وقد لوحظ أن كل منها openid.realm يمر عبر مسار تسجيل الدخول الخاص بـ Steam؛ حيث يقوم السجل بتسجيل مسارات المصادقة التي تمت ملاحظتها، بدلاً من التأكيد على أن أي مشغل معين يفتقر إلى إذن Valve.\n\n#\tالمنصة\tالقيمة المدرجة\tالعروض السارية\tالعناصر\tالمقياس\n1\tUUSkins\t$133.8M\t3.4M\t30.9K\t\n\n2\tYouPin898\t$127.5M\t5.9M\t29.2K\t\n\n3\tBuff.163\t$104M\t3.5M\t35K\t\n\n4\tMoon.Market\t$100.3M\t2.9M\t20.9K\t\n\n5\tWhite.Market\t$89.6M\t3M\t20.6K\t\n\n6\tBuff.Market\t$86.7M\t1.3M\t33.4K\t\n\n7\tEcosteam\t$82.1M\t3.3M\t30.1K\t\n\n8\tCSFloat\t$67.8M\t2.4M\t27.8K\t\n\n9\tSkin.Land\t$67.4M\t2.2M\t34.6K\t\n\n10\tLIS-SKINS\t$67.4M\t2.2M\t34.6K\t\n\n11\tC5Game\t$54.6M\t4.6M\t29.6K\t\n\n12\tHaloSkins\t$46.6M\t4.4M\t29.3K\t\n\n13\tAvan.Market\t$43.3M\t809.5K\t22.2K\t\n\n14\tWaxpeer\t$40.1M\t1M\t27.3K\t\n\n15\tSteam (official)\t$31M\t32.2M\t70.1K\t\n\n16\tCS.MONEY\t$29M\t748.9K\t28K\t\n\n17\tMarket.CSGO\t$26.3M\t1.3M\t27.6K\t\n\n18\tCS.MONEY Bot\t$25.7M\t614K\t23.8K\t\n\n19\tSkinport\t$16.3M\t3.8M\t31.1K\t\n\n20\tSkinFlow\t$14.1M\t481.8K\t23.6K\t\n\n21\tDMarket\t$12.6M\t948.2K\t35.6K\t\n\n22\tSkins.com\t$11.5M\t83.2K\t15.8K\t\n\n23\tSkin.place\t$6.9M\t380.8K\t11.4K\t\n\n24\tSkinsMonkey\t$6M\t109.4K\t11.6K\t\n\n25\tSkinBaron\t$5M\t2.1M\t21.5K\t\n\n26\tRustTM\t$3M\t33.1K\t4.9K\t\n\n27\tPirateSwap\t$2M\t859.3K\t10.5K\t\n\n28\tMannco.Store\t$1.2M\t223.7K\t11K\t\n\n29\tSkinSwap\t$1.1M\t11.4K\t4K\t\n\n30\tTradeIt\t$967.1K\t29.1K\t11.7K\t\n\n31\tLootFarm\t$896.1K\t162.5K\t28.6K\t\n\n32\tRustskins\t$714.8K\t312.5K\t6.1K\t\n\n33\tBalticSkins\t$599.2K\t28.2K\t4.5K\t\n\n34\tExeSkins\t$442.9K\t2.6K\t1.4K\t\n\n35\tRapidSkins\t$230.9K\t11.6K\t2.3K\t\n\n36\tCS.Trade\t$203K\t19K\t16.7K\t\n\n37\tKrakatoa\t$11.1K\t115\t53\t\n\n38\tShadowPay\t—\t—\t—\t—\n39\t49skins\t—\t—\t—\t—\nالحد الأقصى لسعر Steam عند1,800 دولار · لمحة سريعة عن خمسة أسواق · 23 سبتمبر 2026\nالفارق في الأسعار قابل للقياس.\n\nSteam يحدد سقف أسعار العقارات المعروضة في سوق «كابس كوميونيتي» بنحو $1,800 (يتم إعادة حساب النتيجة على أساس $2,000, $و2,070, $و2,300 و$2,500 في cs2sh-atlas.json (ويظل ساريًا عند كل عتبة). الأصناف التي لوحظت عند سعر أعلى من ذلك لا يمكن بيعها بسعر السوق عبر منصة البيع الخاصة بـ «Valve» — لكنها لا تزال تعتمد على نظام المخزون والنقل الخاص بـ «Steam» أينما بيعت. وتصنيف الكتالوج بأكمله حسب السعر يوضح أين تكمن العقبة: سوق «Valve» يضم 95.3% من فئات المنتجات التي تم تسعيرها دون الحد الأقصى و 1.9% من تلك الموجودة فوقها.\n\nخمس منصات بيع: المنتجات التي تتجاوز الحد الأقصى المحدد في «Steam»\n248\n\nفئات المنتجات التي تجاوز سعر العرض الأدنى فيها1,800 دولارًا في سوقان أو أكثر بشكل مستقل، حيث يمتلك نسخًا مدرجة في قائمة «18,394» تبلغ قيمتها ما لا يقل عن $78.6M. ومن بين هؤلاء، 100.0% — كل واحد منهم — ليس لديه أي إدراج على موقع Steam على الإطلاق.\n\nالمستندات الكاملة: السجل → · أطلس سلم الأسعار →\n\nتوزيع الأسعار فوق الحد الأقصى\n$1,800–$5,000\n174\n$5,000–$10,000\n49\n$10,000–$25,000\n21\n$25,000–$50,000\n2\n$50,000+\n2\nأبرز المنتجات — أرخص سعر عرض مؤكد عبر خمسة أسواق\n1ملصق | تيتان (هولو) | الكاتالوج «14»$66,285\n2ملصق | iBUYPOWER (Holo) | رقم الكتالوج: '14$64,795\n3ملصق | Reason Gaming (Holo) | رقم الكاتالوج: '14$42,899\n4★ قفازات رياضية | متاهة الشجيرات (FN)$26,812\n5ملصق | فريق Dignitas (هولوغرامي) | كات. '14'$23,667\n6فئة EMS: «أساطير14»$22,879\n7★ قفازات رياضية | صندوق باندورا (FN)$21,643\n8EMS الفئة \"14\" للمتنافسين$21,010\n9ملصق | Vox Eminor (Holo) | الكاتالوج رقم '14$18,619\n10★ سكين «نافاجا» مزود بنظام StatTrak™ | بلو ستيل (FN)$18,064\n\nأسعار العرض ليست أسعار بيع. لقطة من موقع «cs2.sh» المرخص، 23 سبتمبر 2026. كل صف يتم تسعيره فوق الحد الأقصى من قبل سوقين مستقلين على الأقل؛ ويتم استبعاد عروض البيع ذات السعر الثابت وعروض الشراء التي تزيد عن ثلاثة أضعاف أرخص سعر عرض للسلعة. كيف تتم عملية التقييم →\n\nالرسوم التي تفرضها شركة «Valve» · مرخصة cs2.sh لمحة سريعة · 23 سبتمبر 2026\nالرسوم المعلن عنها هي 15%.، ومعظم العروض تدفع أكثر من ذلك.\n\nValve تقتطع رسومًا من موقع 5% Steam ورسومًا أخرى من ناشر CS2 10% من عائدات البائع — وهي الرسوم المعروفة 15%. وتشمل كلتا الرسومتين الحد الأدنى:0.01 دولار، لذا لا يمكن أبدًا أن تقل رسوم أي عملية بيع عن سنتين. وبالنسبة للسلع الرخيصة ذات الحجم الكبير التي تشكل الجزء الأكبر من السوق، يُعد هذا الحد الأدنى هو القيد الملزم، وليس النسبة المئوية. وقد قمنا بحساب رسوم كل واحدة من 29,635 أنواع العناصر التي تحمل طلبًا مباشرًا على موقع Steam.\n\n77.7%\nتوجد قوائم «Steam» الحية ضمن أنواع العناصر التي يتم احتساب رسومها على الرابط التالي: 15%\n84.8%\nمن البند الأنواع تدفع فعليًّا ما يقارب السعر المعلن\n4,517\nأنواع البضائع التي فُرضت عليها رسوم تزيد عن الرسوم المعلن عنها\n$0.02\nالرسوم الدنيا على أي عملية بيع، بغض النظر عن السعر\nالرقمان يشيران إلى اتجاهين متعاكسين، وكلاهما صحيح\n1\nتم عدها حسب نوع العنصر، تتوافق رسوم موقع «Valve» بشكل عام مع ما هو معلن: 84.8%، حيث تُفرض رسوم على الأنواع المحددة السعر في موقع «29,635» بمبلغ يساوي أو يقارب 15%.\n2\nتم عدها حسب الإدراج الفعلي، تنعكس الصورة: 18,682,244 من موقع 24,038,911 تتوفر قوائم العروض المباشرة لأنواع العناصر التي تتجاوز رسومها 15%.\n3\nكلا الأمرين صحيحان لأن الأنواع التي تم شحنها بشكل زائد هي رخيصة، بكميات كبيرة تلك. 1,109 تُفرض رسوم على أنواع العناصر هذه أكثر من مزدوج السعر المعلن، وهذه الأنواع وحدها تتضمن قوائم العقارات المعروضة للبيع على موقع 14,083,486.\n4\nهذه حسابات بسيطة، وليست مجرد ادعاء. فقد تم الإفصاح عن الحد الأدنى في وثائق الرسوم الخاصة بشركة «Valve» نفسها. أما ما لم يُنشر فهو ما هي الحصة السوقية التي ينطبق عليها فعليًّا؟ — وهذا ما تقيسه الأرقام الواردة أعلاه.\nالرسوم المفروضة، كنسبة من السعر الإجمالي 15%\n200%+\n14,083,486\n100-200%\n1,028,438\n50-100%\n700,804\n30-50%\n317,031\n20-30%\n2,258,254\n17.6-20%\n294,231\n\nطول الشريط هو عدد العروض النشطة في كل نطاق. النطاق «200%+» يعني أن العمولة المقتطعة تزيد عن ضعف 15% من عائدات البائع.\n\nمثال توضيحي\n67%\n\nعند عرض العقار للبيع، يدفع المشتري $0.03 حيث يتلقى البائع $0.01 وموقع Valve يستغرق $0.02 — الحد الأدنى المكون من سنتين. كنسبة من المبلغ الذي دفعه المشتري، فإن ذلك يمثل 67%؛ وكنسبة من عائدات البائع، فإنه يمثل 200%.\n\nمجموعة البيانات الكاملة: cs2sh-steam-fee-census.json →\n\nنفس الشيء، داخل الحديقة وخارجها\nالشراء من موقع Steam يكلف أكثر. في معظم الأحيان.\n\nبالنسبة لكل منتج معروض على موقع Steam وعلى منصة بيع أخرى تابعة لجهة خارجية واحدة على الأقل، قمنا بمقارنة أرخص سعر عرض على موقع Steam بأرخص سعر عرض خارج هذا الموقع. عبر 28,700 من بين الخيارين، Steam هو المكان الأغلى 86.4% في معظم الأحيان، بمتوسط يبلغ +35.7%.\n\nمتوسط قسط التأمين على «Steam»، حسب الشريحة السعرية\nأقل من $0.50\n+48.3%\n$0.50-2\n+36.5%\n$2-10\n+29.6%\n$10-50\n+28.6%\n$50-250\n+36.3%\n$250-1k\n+51.1%\nأكثر من $1,000\n+67.9%\n\nالمنحنى على شكل حرف U. وأرخص طريقة للشراء هي عبر موقع Steam في $10–$50 الشريط وأعز ما يكون في الطرفين.\n\nلماذا يُعد الجانب المتعلق بالتكلفة أمراً مهماً؟\n+67.9%\n\nأعلاه $1,000، حيث يبلغ متوسط تكلفة الإعلانات على موقع «Steam» 67.9% أكثر من أرخص عرض خارج هذا الموقع — ولا يوجد سوى 1,040 من هذه الإعلانات على موقع Steam أصلاً.\n\nعند تجاوز مبلغ1,800 تقريبًا، تصبح المقارنة غير ممكنة، لأن قاعدة موقع Valve تحظر عرض هذه المنتجات تمامًا. وتبلغ تغطية موقع Steam للمنتجات التي تتجاوز الحد الأقصى الخاص به 1.9%. شاهد الترتيب الكامل →\n\nمجموعة البيانات الكاملة: cs2sh-walled-garden-premium.json →\n\nلا يُعد الفارق السعري في حد ذاته استنتاجًا: فخدمة «Steam» توفر التسليم الفوري وتخلو من مخاطر الطرف المقابل، وقد يكون من المعقول أن يدفع المشترون مقابل ذلك. أما ما يمكن قياسه فهو حجم الفجوة وحقيقة أن الأموال التي تمر عبرها لا يمكن استردادها — وهو ما سنناقشه في القسم التالي.\n\nيدخل المال، ولا يخرج\n128.1 مليون دولار مخصصة لطلبات شراء لا يمكن إلغاؤها.\n\nيتم تمويل أمر الشراء في منصة «Steam» مسبقًا: حيث تُسحب الأموال من محفظة المشتري فور تقديم الأمر. أموال محفظة «Steam» لا يمكن سحبها — ولا يمكن إنفاقها إلا داخل Steam. وعند جمع كل مستوى سعري في دفتر أوامر الشراء لكل عنصر يتم تتبعه، نحصل على إجمالي الأموال الملتزم بها، والتي لا يمكن سحبها.\n\n$128.1M\nملتزمون بتنفيذ أوامر الشراء Steam\n170.6م\nأوامر الشراء الفردية الممولة السارية\n$105.8M\nالقيمة المطلوبة للعقارات المعروضة أمامهم\n$15.9M\nحصة شركة Valve في حال بيع جميع العقارات المعروضة بالسعر المطلوب\nما هو هذا الرقم، وما ليس به\n1\nإنه أموال حقيقية تم دفعها بالفعل. كل دولار تم احتسابه قد تم خصمه من محفظة، وهو مخصص لأمر مفتوح عبر أنواع العناصر الموجودة في 31,253.\n2\nإنه ليس إيرادات وليس ادعاءً يتعلق بالميزانية العمومية لشركة «Valve». ولم يتم تحديد مكان الاحتفاظ بالأموال المتداولة، ولا في دفاتر من، في هذا السياق.\n3\nإنه لقطة، وليست تدفقًا. يمكن للمشتري إلغاء الطلبات، مما يؤدي إلى إعادة الأموال إلى المحفظة — لكنها لا تخرج بعد من Steam.\n4\nالباب ذو الاتجاه الواحد هو جوهر الموضوع. فالسوق التي لا يمكن صرف عملتها نقدًا هي السبب وراء تحويل المخزون المسروق إيقاف Steam بدلاً من أن يكون عليه.\n\nالطريقة: يتم ضرب كل مستوى سعري في كل سجل أوامر شراء يتم تتبعه، في عدد الأوامر الموجودة عند ذلك المستوى. مجموعة البيانات الكاملة: cs2sh-steam-locked-capital.json →\n\nالمبيعات الفعليّة، وليس الأسعار المطلوبة · سوق واحد · مؤشر الأداء المتتابع (90) لـ يومًا\n30.9 مليون دولار تم تداولها فعليًّا — على أصغر الرفوف الخمسة.\n\nقد تكون الصفقة الواحدة ذات السعر المرتفع عبارة عن قطعة فنية نادرة أو نسخة معدلة بملصقات من سلعة أساسية رخيصة (مثل: e.g. سلعة بسعر $30، مع صفقة واحدة مكتملة بقيمة $9,772). ويُقصد بـ«مرتفع» أعلى سعر تم التوصل إليه في صفقة مكتملة، وليس السعر العادي للسلعة.\n\nكل رقم آخر في هذه الصفحة يقيس ما هو مدرجة. هذا الجهاز يقيس ما كان تم بيعه. تنشر شركة «Skinport» المعاملات التي أنجزتها بنفسها، وخلال الأيام الـ90 الماضية بلغ عددها 1,219,143 المبيعات قيمة $30,927,032، بمتوسط25.37 دولار لكل منها.\n\n1.22م\nالمبيعات التي تمت خلال 90 يومًا، في سوق واحد\n$30.9M\nحجم المبيعات خلال نفس الفترة\n$125M\nمعدل الأداء السنوي — حد أدنى، وليس تقديرًا\n~2%\nحصة شركة Skinport من الرصيد المتاح فوق الحد الأقصى حسب القيمة السوقية\nمن أين جاءت إيرادات المبيعات\nأقل من1 دولار\n0.5%\n$1-10\n5.8%\n$10-100\n22.2%\n$100-1k\n59.4%\n$1k-1.8k\n6.9%\nفوق الحد الأقصى المحدد في قانون «Steam»\n5.3%\n\nطول الشريط يمثل حجم التداول؛ والرقم يمثل حصة تلك الفئة من الإجمالي. 59.4% من الأموال التي تم تحويلها في فئة $100–$1k، من مبيعات موقع 71,437.\n\nفوق قبعة «Valve»، لا تزال المبيعات مستمرة\n492\n\nمبيعات تم إتمامها لسلع تزيد أسعارها عن الحد الأقصى المحدد في قانون «Steam»، بقيمة $1,643,938، عبر أنواع المنتجات الموجودة على موقع 76 — في سوق يستحوذ على ما يقارب 2% من تلك المساحة. لم يكن من الممكن أن تتم أي من تلك المبيعات على موقع Steam.\n\nمجموعة البيانات الكاملة: cs2sh-offsteam-90d-dynamics.json → · أعلى المستويات التي تم بلوغها →\n\nSkinport تعد «ONE» إحدى أسواق الجهات الخارجية التي يتم تتبعها هنا، وبما أن قيمة أسهمها تتجاوز الحد الأقصى المحدد في «Steam»، فهي الأصغر بين الأسواق الخمس (حوالي 2% من تلك القائمة). كل إجمالي مذكور هنا يمثل الحد الأدنى للاقتصاد خارج «Steam»، وليس مقياسًا له. ولا يتم استخدام أي بيانات من «Steam».",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "اقتصاديات السوق — اقتصادان وسقف الإدراج"
          },
          {
            "level": 2,
            "id": null,
            "text": "بنية تحتية واحدة. اقتصادان."
          },
          {
            "level": 2,
            "id": null,
            "text": "سجل المنصة"
          },
          {
            "level": 2,
            "id": null,
            "text": "الفارق في الأسعار قابل للقياس."
          },
          {
            "level": 3,
            "id": null,
            "text": "خمس منصات بيع: المنتجات التي تتجاوز الحد الأقصى المحدد في «Steam»"
          },
          {
            "level": 3,
            "id": null,
            "text": "توزيع الأسعار فوق الحد الأقصى"
          },
          {
            "level": 3,
            "id": null,
            "text": "أبرز المنتجات — أرخص سعر عرض مؤكد عبر خمسة أسواق"
          },
          {
            "level": 2,
            "id": null,
            "text": "الرسوم المعلن عنها هي 15%.، ومعظم العروض تدفع أكثر من ذلك."
          },
          {
            "level": 3,
            "id": null,
            "text": "الرسوم المفروضة، كنسبة من السعر الإجمالي 15%"
          },
          {
            "level": 3,
            "id": null,
            "text": "مثال توضيحي"
          },
          {
            "level": 2,
            "id": null,
            "text": "الشراء من موقع Steam يكلف أكثر. في معظم الأحيان."
          },
          {
            "level": 3,
            "id": null,
            "text": "متوسط قسط التأمين على «Steam»، حسب الشريحة السعرية"
          },
          {
            "level": 3,
            "id": null,
            "text": "لماذا يُعد الجانب المتعلق بالتكلفة أمراً مهماً؟"
          },
          {
            "level": 2,
            "id": null,
            "text": "128.1 مليون دولار مخصصة لطلبات شراء لا يمكن إلغاؤها."
          },
          {
            "level": 2,
            "id": null,
            "text": "30.9 مليون دولار تم تداولها فعليًّا — على أصغر الرفوف الخمسة."
          },
          {
            "level": 3,
            "id": null,
            "text": "من أين جاءت إيرادات المبيعات"
          },
          {
            "level": 3,
            "id": null,
            "text": "فوق قبعة «Valve»، لا تزال المبيعات مستمرة"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/ar/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/ar/elite_skins.html",
          "https://phishdestroy.io/steam_dossier/ar/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/ar/skin_atlas.html#grading",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-steam-fee-census.json",
          "https://phishdestroy.io/steam_dossier/ar/skin_atlas.html#cliff",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-walled-garden-premium.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-steam-locked-capital.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-offsteam-90d-dynamics.json",
          "https://phishdestroy.io/steam_dossier/ar/skin_atlas.html#highs"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ar/market_economics.content.json",
      "export_json_sha256": "a348d7cb8852ab2268dfb32c8c70911abedac0b8691a80401011e293f8078552"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ar/regulatory_act_print.html",
      "language": "ar",
      "title": "قانون التدقيق الجنائي: Valve Steam الموقع الإلكتروني: API النظام البيئي والاستغلال التجاري (المرجع: VAL-REG-2026-09)",
      "source_url": "https://phishdestroy.io/steam_dossier/ar/regulatory_act_print",
      "source_html_sha256": "c7c474c90e2356f935ed1045abdcb0d06e3bf684020ce48aa4e1523ae631cb2b",
      "exported_at": "2026-09-29T00:20:10.631Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "regulatory_act_print.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ar/regulatory_act_print.pdf?v=print-20260929-v5",
        "sha256": "649a8458e4e0468310311d066a8d583f1d9e7e78bc0b72c858398de79dee5b2c",
        "bytes": 210998,
        "pages": 13
      },
      "integrity": {
        "signed_object": "regulatory_act_print.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "regulatory_act_print.content.json.asc",
        "digest_file": "regulatory_act_print.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify regulatory_act_print.content.json.asc regulatory_act_print.content.json",
          "sha256sum -c regulatory_act_print.content.json.sha256"
        ]
      },
      "content": {
        "text": "phishdestroy.io · تحالف البحوث الجنائية · السجل العام الشامل\nملف القضية: VAL-REG-2026-09-EVID\nالمصدر: phishdestroy.io/steam_dossier/\nالحقوق: تم التنازل عن جميع الحقوق لصالح الإنسانية\nقانون التدقيق الجنائي والملحق التنظيمي\nالتزويد المنهجي من طرف ثالث لـ «API»، وبنية التجاوز الآلي، وعدم إنفاذ الشروط التعاقدية في منظومة «Valve» و«Steam»\nنطاق الإصدارphishdestroy.io\nالمنصة المستهدفةValve Steam / Steamworks\nمتجه المصادقة الأساسيSteam OpenID 2.0 / الموقع الإلكتروني API\nإهداء قانونيجميع الحقوق محفوظة لموقع «Humanity» (CC0)\nالقسم الأول: المذكرة التنفيذية والنتائج الوقائعيةالمرجع: مذكرة موجزة -01\n\nيمثل هذا المستند تقريرًا رسميًا للتدقيق الجنائي يبحث في التداخل التشغيلي بين الشروط التجارية المنشورة لشركة «Valve» ونقاط النهاية الخاصة بالمصادقة التقنية التابعة لها، والمنصات التجارية التابعة لأطراف ثالثة التي تمت ملاحظتها. وقد أُجري التدقيق باستخدام المراقبة السلبية للشبكة دون مصادقة، والتحقق من التسجيل عبر «RDAP»، وبيانات القياس عن بُعد العامة الخاصة بـ«Link Filter».\n\nجوهر الحقائق: تُثبت الملاحظة التجريبية وجود تباين منهجي بين الإقرارات التعاقدية العلنية لشركة «Valve» وبنيتها التحتية الإنتاجية. في حين أن اتفاقية المشتركين في خدمة «Steam» (SSA) تحظر بشكل صارم الاستغلال التجاري غير المصرح به (§ 2.G)، والتفاعل الآلي عبر الروبوتات أو البرامج النصية (§ 4.C)، ونقل الحسابات (§ 1.C)، تواصل شركة «Valve» توفير بنية تحتية حية وبرمجية للمصادقة عبر OpenID والاستعلام عن المخزون لما لا يقل عن 175 كيانًا تجاريًا، مما يولد أحجام معاملات ثانوية تقدر بمليارات الدولارات.\n\n175\nالمشغلون التجاريون الخاضعون للتدقيق\n44\nمضيفات المصادقة ذات المجالات المنفصلة\n26\nأزواج الوكلاء ذات التصفية المقسمة\n100%\nالمادة غير المطبقة من قانون الضمان الاجتماعي (SSA) § 2.G / § 4.C\n0\nعمليات الإلغاء القسري للتصاريح\nالإطار التعاقدي والقانوني المعمول به\nقانون الضمان الاجتماعي (SSA)، المادة2.G\nحظر الاستخدام التجاري: يُحظر صراحةً استغلال المحتوى والخدمات لأغراض تجارية دون الحصول على إذن كتابي مسبق من شركة Valve.\nقانون الضمان الاجتماعي، المادة4.C\nقيود الأتمتة: يُحظر تمامًا استخدام البرامج النصية أو روبوتات التداول أو الماكرو أو الأنظمة التي لا يتحكم فيها الإنسان للتفاعل مع خدمات وأسواق Steam.\nقانون الضمان الاجتماعي، المادة1.C\nتوجيهات الاستخدام الشخصي: يقتصر استخدام الحسابات على الأغراض الشخصية؛ ويحظر صراحةً بيع حسابات مستخدمي موقع Steam أو تأجيرها أو نقل ملكيتها أو المتاجرة بها.\nقانون خدمات البيانات في الاتحاد الأوروبي (DSA) (2022/2065)\nتقييم المخاطر النظامية (المادة 34/35): يجب على المنصات الإلكترونية الضخمة جدًّا (VLOPs) أن تعمل بنشاط على كشف وتقييم وتخفيف المخاطر النظامية الناجمة عن سوء الاستخدام الآلي والاستغلال التجاري غير المصرح به.\nالقسم الثاني: دفتر الأستاذ «أ» — أزواج مقسمة لمرشحات الارتباط الموثقة (مسارات 26)المرجع: EX-SPLIT-LEDGER\n\nالتحليل الجنائي لتقنية التهرب باستخدام المجالات المنقسمة: في إطار نظام تصفية الروابط \"Steam\" التابع لـValve (steamcommunity.com/linkfilter/?url=...)، عندما ينقر مستخدم نهائي على رابط يؤدي إلى منصة مقامرة أو منصة سوق سوداء تم الإبلاغ عنها، يعرض موقع Valve تحذيرًا بارزًا (\"الرابط محظور! ... تم الإبلاغ عنه باعتباره قد يكون ضارًا\"). ومع ذلك، كشفت عملية تتبع المسار الجنائي عن وجود منصات تجارية تعمل بنظام «26» على بنية المجالات المنفصلة: في حين أن النطاق التجاري الأساسي مُحجوب في «Link Filter»، فإن النطاق الثانوي الذي يستضيف نقطة نهاية استرجاع OpenID الخاصة بـ Valve يُصنف على أنه «سليم». تقبل خوادم OpenID الخاصة بـ Valve طلبات المصادقة الواردة من هذه المضيفات الوكيلة دون انقطاع، مما يؤدي إلى إبطال تحذير أمان المستهلك مع الاستمرار في معالجة عمليات تسجيل الدخول.\n\n#\tالمجال التجاري الرئيسي\tالمرشح الرئيسي\tنطاق وكيل المصادقة OpenID\tمرشح المصادقة\tRDAP مسجل\tأساس التسجيل\n01\trollbit.com\tBLOCKED\trbsnin.com\tCLEAN\t2026-09-18\tPASSIVE_CAPTURE\n02\tskin.club\tBLOCKED\tsc-auth.net\tCLEAN\t2019-04-02\tPASSIVE_CAPTURE\n03\thowl.gg\tBLOCKED\thowl.uno\tCLEAN\t2026-08-11\tPASSIVE_CAPTURE\n04\tduelbits.com\tBLOCKED\tswitchflips.com\tCLEAN\t2020-04-21\tPASSIVE_CAPTURE\n05\tcsgofast.com\tBLOCKED\tsteam-login.authtofast.com\tCLEAN\t2026-06-30\tPASSIVE_CAPTURE\n06\tfarmskins.com\tBLOCKED\tsteam.kobal.cc\tCLEAN\t2017-01-07\tPASSIVE_CAPTURE\n07\tcobaltlab.tech\tBLOCKED\tcobaltauth.com\tCLEAN\t2025-01-07\tPASSIVE_CAPTURE\n08\tcsgo.net\tBLOCKED\tcn2.easylot.net\tCLEAN\t2016-09-03\tPASSIVE_CAPTURE\n09\tggdrop.com\tBLOCKED\tggauth.com\tCLEAN\t2023-05-03\tPASSIVE_CAPTURE\n10\trustchance.com\tBLOCKED\thgfuihd.com\tCLEAN\t2019-01-27\tPASSIVE_CAPTURE\n11\tskin.fans\tBLOCKED\tauth.skinfans.com\tCLEAN\t2018-07-16\tPASSIVE_CAPTURE\n12\tskinport.com\tBLOCKED\tskinport.app\tCLEAN\t2020-06-20\tPASSIVE_CAPTURE\n13\tskins.cash\tBLOCKED\tskinscash.live\tCLEAN\t2019-12-05\tPASSIVE_CAPTURE\n14\ttf2hunt.com\tBLOCKED\trstspcl.com\tCLEAN\t2020-08-08\tPASSIVE_CAPTURE\n15\tdaddyskins.com\tBLOCKED\tgo-go-daddy.com\tCLEAN\t2019-01-26\tPASSIVE_CAPTURE\n16\tkey-drop.com\tBLOCKED\tkdauth.com\tCLEAN\t2026-05-13\tPASSIVE_CAPTURE\n17\tclash.gg\tBLOCKED\tclggauth.com\tCLEAN\t2024-09-16\tPASSIVE_CAPTURE\n18\tc5game.com\tBLOCKED\twww.imbastar.com\tCLEAN\t2016-02-27\tPASSIVE_CAPTURE\n19\tswap.gg\tBLOCKED\tswapauth.com\tCLEAN\t2018-10-06\tPASSIVE_CAPTURE\n20\tshadowpay.com\tBLOCKED\tthelogins.com\tCLEAN\t2018-01-22\tPASSIVE_CAPTURE\n21\tcsgocases.com\tBLOCKED\tlog-1n.com\tCLEAN\t2017-11-27\tPASSIVE_CAPTURE\n22\tcsgogem.com\tBLOCKED\tapi.csgem.com\tCLEAN\t2014-03-08\tPASSIVE_CAPTURE\n23\tgamdom.com\tBLOCKED\tlogin.gambldom.com\tCLEAN\t2017-09-24\tPASSIVE_CAPTURE\n24\t12cs.fail\tBLOCKED\tfail.games\tCLEAN\t2021-08-24\tPASSIVE_CAPTURE\n25\tskinsnipe.com\tBLOCKED\tpricing.tradeupspy.com\tCLEAN\t2020-03-11\tPASSIVE_CAPTURE\n26\tcsgobig.com\tBLOCKED\tletmeinbig.com\tCLEAN\t2023-01-20\tPASSIVE_CAPTURE\n\n* ملاحظة: يتم إجراء عمليات الفحص السلبية على نقاط نهاية مرشح الروابط (Steam Link Filter) غير المصادق عليها على 2026-09-19 و2026-09-21.، ويتم الاحتفاظ بنصوص استجابات HTTP الأولية ومستخلصات SHA-256 في مجموعة بيانات المستودع (steam_tos_assets/linkfilter-2026-09-22.json).\n\nالقسم الثالث: دفتر الأستاذ (ب) — التعداد الشامل للكيانات التجارية الخاضعة للتدقيق في برنامج «175»المرجع: EX-175-MASTER-CENSUS\n\nيسرد السجل التالي تفاصيل جميع المنصات التجارية التابعة لأطراف ثالثة 175 التي تم التحقق منها فعليًّا في قاعدة بيانات التدقيق. ويشير كل سجل إلى اسم الكيان، والنطاق التجاري الأساسي، ومسار مصادقة OpenID الملحوظ Steam، وتصنيف النشاط، وتعيينات الانتهاكات التعاقدية (SSA § 2.G، SSA § 4.C، SSA § 1.C)، وحقل الإجراء المسجل في مجموعة البيانات المصدر. تشير العلامة «انظر الأدلة المؤرخة» القارئ إلى السجلات الداعمة؛ ولا تثبت أن Valve لم تتخذ أي إجراء. ويُبلغ عن حقل الإجراء الغائب على أنه غير مؤكد.\n\nمعروض\tاسم الكيان والنطاق الرئيسي\tمسار المصادقة الملحوظ / الوكيل\tالتصنيف\tالإخلال بالعقد\tValve الإجراء\nEX-001\tCSGORoll\ncsgoroll.com\n\t\nwww.csgoroll.com\nDIRECT\n\tSkin Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-002\tCSGOEmpire\ncsgoempire.com\n\t\ncsgoempirelogin4.com\nSPLIT PROXY\n\tCasino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-003\tRollbit\nrollbit.com\n\t\nrbsnin.com\nSPLIT PROXY\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-004\t500 Casino\n500.casino\n\t\nfivezerozero.co\nSPLIT PROXY\n\tLicenced Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-005\tCSGOBig\ncsgobig.com\n\t\ncsgobig.com\nDIRECT\n\tRoulette/Slots\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-006\tCaseDrop\ncasedrop.com\n\t\ncasedrop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-007\tRustReaper\nrustreaper.com\n\t\nrustreaper.com\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-008\tBanditCamp\nbanditcamp.com\n\t\nbanditcamp.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-009\tSkinBox\nskinbox.com\n\t\nskinbox.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-010\tTastyDrop\ntastydrop.com\n\t\ntastydrop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-011\tCSGOPolygon\ncsgopolygon.gg\n\t\ncsgopolygon.gg\nDIRECT\n\tRoulette Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-012\tMagicDrop\nmagicdrop.ru\n\t\nmagicdrop.ru\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-013\tCSDice\ncsdice.com\n\t\ncsdice.com\nDIRECT\n\tDice Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-014\tRustly\nrustly.com\n\t\nrustly.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-015\tSkinOdds\nskinodds.com\n\t\nskinodds.com\nDIRECT\n\tUpgrader Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-016\tCSGOWin\ncsgowin.com\n\t\ncsgowin.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-017\tCSGORun\ncsgorun.net\n\t\ncsgorun.net\nDIRECT\n\tCrash Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-018\tOpenSkins\nopenskins.com\n\t\nopenskins.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-019\tRustBet\nrustbet.com\n\t\nrustbet.com\nDIRECT\n\tRust Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-020\tCSGOMagic\ncsgomagic.com\n\t\ncsgomagic.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-021\tCSGOBounty\ncsgobounty.com\n\t\ncsgobounty.com\nDIRECT\n\tUpgrader/Contract\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-022\tEZSkins\nezskins.com\n\t\nezskins.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-023\tRustCases\nrustcases.com\n\t\nrustcases.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-024\tCSGOReaper\ncsgoreaper.com\n\t\ncsgoreaper.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-025\tCSGOCases\ncsgocases.com\n\t\ncsgocases.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-026\tCSGO-Skins\ncsgo-skins.com\n\t\ncsgo-skins.com\nDIRECT\n\tCase Upgrader\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-027\tCSGONet\ncsgonet.com\n\t\ncsgonet.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-028\tWTFSkins\nwtfskins.com\n\t\nwtfskins.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-029\tCSGOFast\ncsgofast.com\n\t\nsteam-login.authtofast.com\nSPLIT PROXY\n\tRoulette Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-030\tDuelbits\nduelbits.com\n\t\nswitchflips.com\nSPLIT PROXY\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-031\tFlameCases\nflamecases.com\n\t\nflamecases.com\nDIRECT\n\tCase Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-032\tFarmskins\nfarmskins.com\n\t\nsteam.kobal.cc\nSPLIT PROXY\n\tCase Opener\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-033\tCSGOLuck\ncsgoluck.com\n\t\ncsgoluck.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-034\tGamedom\ngamedom.com\n\t\ngamedom.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-035\tSkin.Club\nskin.club\n\t\nsc-auth.net\nSPLIT PROXY\n\tCase Battles\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-036\tDaddySkins\ndaddyskins.com\n\t\ndaddyskins.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-037\tInsane.gg\ninsane.gg\n\t\napi.insane.gg\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-038\tRustix\nrustix.gg\n\t\nrustix.gg\nDIRECT\n\tRust Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-039\tSkins.Club\nskins.club\n\t\nskins.club\nDIRECT\n\tSkin Upgrade\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-040\tCSGOHouse\ncsgohouse.org\n\t\ncsgohouse.org\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-041\tSkinRave\nskinrave.net\n\t\nskinrave.net\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-042\tBloodyCase_GG\nbloodycase.gg\n\t\nbloodycase.gg\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-043\tCSGOClicker\ncsgoclicker.com\n\t\ncsgoclicker.com\nDIRECT\n\tClicker/Upgrade\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-044\tRustBet_GG\nrustbet.gg\n\t\nrustbet.gg\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-045\tCS_Drop\ncs-drop.com\n\t\ncs-drop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-046\tHellStore\nhellstore.net\n\t\nhellstore.net\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-047\tRustLoot\nrustloot.com\n\t\nrustloot.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-048\tCSGO_Case\ncsgo-case.com\n\t\ncsgo-case.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-049\tCS2Skin\ncs2skin.com\n\t\ncs2skin.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-050\tJuice_GG\njuice.gg\n\t\nletmeinjuice.com\nSPLIT PROXY\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-051\tGGDrop\nggdrop.com\n\t\nggauth.com\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-052\tCSGOGem\ncsgogem.com\n\t\ncsgogem.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-053\tRainbet\nrainbet.com\n\t\nservices.rainbet.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-054\tHowl_GG\nhowl.gg\n\t\nhowl.uno\nSPLIT PROXY\n\tSkins Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-055\tChicken_GG\nchicken.gg\n\t\nchicken.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-056\tCSGOCasino_GG\ncsgocasino.gg\n\t\napi.csgocasino.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-057\tHunt_GG\nhunt.gg\n\t\napi.hunt.gg\nDIRECT\n\tSkins Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-058\tCSBattle\ncsbattle.com\n\t\ncsbattle.com\nDIRECT\n\tCase Battles\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-059\tSkinRave_GG\nskinrave.gg\n\t\napi.skinrave.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-060\tCSDouble\ncsdouble.gg\n\t\ncsdouble.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-061\tRustChance\nrustchance.com\n\t\nhgfuihd.com\nSPLIT PROXY\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-062\tRustClash\nrustclash.com\n\t\nrustclash.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-063\tCobaltLab\ncobaltlab.tech\n\t\ncobaltauth.com\nSPLIT PROXY\n\tRust Automation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-064\tRaided_GG\nraided.gg\n\t\napi.raided.gg\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-065\tRustNeo\nrustneo.gg\n\t\nrustneo.gg\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-066\tSplits_GG\nsplits.gg\n\t\nsplits.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-067\tUpgrader_Pro\nupgrader.pro\n\t\nupgauth.space\nSPLIT PROXY\n\tSkin Upgrader\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-068\tSkinFans\nskin.fans\n\t\nauth.skinfans.com\nSPLIT PROXY\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-069\tHotPizza\nhotpizza.one\n\t\nhotpizza.one\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-070\tG4Skins\ng4skins.com\n\t\nauth.g4s.to\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-071\t12CS_Fail\n12cs.fail\n\t\n12cs.fail\nDIRECT\n\tCrash Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-072\tTF2Royal\ntf2royal.com\n\t\ntf2auth.com\nSPLIT PROXY\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-073\tTF2Easy\nwww.tf2easy.com\n\t\nwww.tf2easy.com\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-074\tTF2Hunt\ntf2hunt.com\n\t\nrstspcl.com\nSPLIT PROXY\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-075\tTF2Bet\ntf2.bet/coinflip\n\t\ntf2.bet\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-076\tTF2Blaze\ntf2blaze.com\n\t\ntf2blaze.com\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-077\tOpenStars_GG\nopenstars.gg\n\t\nopenstars.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-078\tShuffle_Com\nshuffle.com\n\t\nshuffle.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-079\tSkins.com\nskins.com\n\t\napi.skins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-080\tWhite.Market\nwhite.market\n\t\nwhite.market\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-081\tBuff.Market\nbuff.market\n\t\nbuff.market\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-082\tAvan.Market\navan.market\n\t\navan.market\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-083\tCS.MONEY\ncs.money\n\t\nauth.dota.trade\nSPLIT PROXY\n\tTrading Engine\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-084\tUUSkins\nuuskins.com\n\t\nuuskins.com\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-085\tYouPin898\nyoupin898.com\n\t\nyoupin898.com\nDIRECT\n\tMass Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-086\tMoon.Market\nmoon.market\n\t\nmoon.market\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-087\tCSFloat\ncsfloat.com\n\t\ncsgofloat.com\nSPLIT PROXY\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-088\tSkin.Land\nskin.land\n\t\nauth.skin.land\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-089\tC5Game\nc5game.com\n\t\nc5game.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-090\tHaloSkins\nhaloskins.com\n\t\nhaloskins.com\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-091\tBuff.163\nbuff.163.com\n\t\nbuff.163.com\nDIRECT\n\tCorporate Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-092\tWaxpeer\nwaxpeer.com\n\t\nwaxpeer.com\nDIRECT\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-093\tCS.MONEY Bot\ncs.money\n\t\nauth.dota.trade\nSPLIT PROXY\n\tBot Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-094\tMarket.CSGO\nmarket.csgo.com\n\t\ndota2.net\nSPLIT PROXY\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-095\tSkinport\nskinport.com\n\t\nskinport.app\nSPLIT PROXY\n\tRegulated Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-096\tSkinFlow\nskinflow.gg\n\t\napi.skinflow.gg\nDIRECT\n\tMarketplace/Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-097\tDMarket\ndmarket.com\n\t\ndmarket.com\nDIRECT\n\tUS Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-098\tSkin.place\nskin.place\n\t\napi.skin.place\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-099\tSkinsMonkey\nskinsmonkey.com\n\t\nskinsmonkey.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-100\tSkinBaron\nskinbaron.de\n\t\nskinbaron.com\nSPLIT PROXY\n\tCorporate Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-101\tSteam\nsteamcommunity.com/market\n\t\nsteamcommunity.com/market\nDIRECT\n\tOfficial Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-102\tRustTM\nrust.tm\n\t\ndota2.net\nSPLIT PROXY\n\tRust Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-103\tPirateSwap\npirateswap.com\n\t\nlogin.pirateswap.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-104\tMannco.Store\nmannco.store\n\t\nmannco.store\nDIRECT\n\tTF2 Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-105\tSkinSwap\nskinswap.com\n\t\napi.skinswap.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-106\tLootFarm\nlootfarm.com\n\t\nlootfarm.com\nDIRECT\n\tTrading Platform\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-107\tRustskins\nrustskins.com\n\t\nrustskins.com\nDIRECT\n\tRust Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-108\tExeSkins\nexeskins.com\n\t\nexeskins.com\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-109\tBalticSkins\nbalticskins.com\n\t\nbalticskins.com\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-110\tCS.Trade\ncs.trade\n\t\ncs.trade\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-111\tRapidSkins\nrapidskins.com\n\t\napi.rapidskins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-112\tTradeIt\ntradeit.gg\n\t\nconnect-tradeit.com\nSPLIT PROXY\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-113\tKrakatoa\nkrakatoa.com\n\t\nkrakatoa.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-114\tShadowPay\nshadowpay.com\n\t\nshadowpay.com\nDIRECT\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-115\t49skins\n49skins.com\n\t\napi.49skins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-116\tSkinVault\nskinvault.gg\n\t\napi.skinvault.gg\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-117\tAim Market\naim.market\n\t\naim.market\nDIRECT\n\tSkins Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-118\tSkinout\nskinout.gg\n\t\nauth.skinout.gg\nDIRECT\n\tInstant Sell Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-119\tNTSkins\nntskins.com\n\t\nntskins.com\nDIRECT\n\tSkins Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-120\tIGXE\nigxe.cn\n\t\nigxe.cn\nDIRECT\n\tChinese Powerhouse\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-121\tSwap.gg\nswap.gg\n\t\nswap.gg\nDIRECT\n\tAutomated Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-122\tBitskins\nbitskins.com\n\t\nbitskins.com\nDIRECT\n\tCash-out Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-123\tGamerPay\ngamerpay.gg\n\t\ngamerpay.gg\nDIRECT\n\tP2P Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-124\tTF2Mart\ntf2mart.com\n\t\ntf2mart.com\nDIRECT\n\tTF2 Automation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-125\tSkinBid\nskinbid.com\n\t\nskinbid.com\nDIRECT\n\tSkin Auctions\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-126\tLootBear\nlootbear.com\n\t\nlootbear.com\nDIRECT\n\tSkin Rental\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-127\tBackpack.tf\nbackpack.tf\n\t\nbackpack.tf\nDIRECT\n\tTF2 Valuation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-128\tScrap.tf\nscrap.tf\n\t\nscrap.tf\nDIRECT\n\tTF2 Scrap Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-129\tMarketplace.tf\nmarketplace.tf\n\t\nmarketplace.tf\nDIRECT\n\tTF2 Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-130\tSTNTrading\nstntrading.eu\n\t\nstntrading.eu\nDIRECT\n\tTF2 Botnet\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-131\tSkins.Cash\nskins.cash\n\t\nskinscash.live\nSPLIT PROXY\n\tInstant Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-132\tSkinWallet\nskinwallet.com\n\t\nskinwallet.com\nDIRECT\n\tInstant Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-133\tDota2Market\ndota2market.com\n\t\ndota2market.com\nDIRECT\n\tDota 2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-134\tCSGO.NET\ncsgo.net\n\t\ncn2.easylot.net\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-135\tCybershoke\ncybershoke.net\n\t\nauth.cybershoke.net\nDIRECT\n\tCommunity Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-136\tXPlay_GG\nxplay.gg\n\t\nxplay.gg\nDIRECT\n\tServer Network\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-137\tFastCup\nfastcup.net\n\t\napi.fastcup.net\nDIRECT\n\tMatchmaker Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-138\tEsportal\nesportal.com\n\t\nesportal.com\nDIRECT\n\tMatchmaking Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-139\tGamersClub\ngamersclub.com.br\n\t\ngamersclub.com.br\nDIRECT\n\tLATAM Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-140\tLeetify\nleetify.com\n\t\nleetify.com\nDIRECT\n\tSaaS Analytics\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-141\tScope_GG\nscope.gg\n\t\nscope.gg\nDIRECT\n\tSaaS Analytics\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-142\tTradeUpSpy\ntradeupspy.com\n\t\napi.tradeupspy.com\nDIRECT\n\tSaaS Tools\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-143\tEpidemic_GG\nepidemic.gg\n\t\nepidemic.gg\nDIRECT\n\tSaaS Tools\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-144\tCSDeals\ncs.deals\n\t\napi.cs.deals\nDIRECT\n\tMarketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-145\tPricempire\npricempire.com\n\t\npricempire.com\nDIRECT\n\tSaaS Price DB\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-146\tCS2Stash\ncs2stash.com\n\t\ncs2stash.com\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-147\tCSGOSkins\ncsgoskins.gg\n\t\ncsgoskins.gg\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-148\tSteamAnalyst\nsteamanalyst.com\n\t\nsteamanalyst.com\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-149\tSteamCardExchange\nsteamcardexchange.net\n\t\nsteamcardexchange.net\nDIRECT\n\tTrading Exchange\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-150\tDotaBuff\ndotabuff.com\n\t\ndotabuff.com\nDIRECT\n\tSaaS Tracker\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-151\tTracker_GG\ntracker.gg\n\t\ntracker.gg\nDIRECT\n\tSaaS Tracker\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-152\tFSB Market (an anonymized label; the original name is withheld here)\nFSB Market\n\t\nFSB Market\nDIRECT\n\tMass Blackmarket\tSSA § 2.G, SSA § 4.C, SSA § 1.C\tSee dated evidence\nEX-153\tFunPay\nfunpay.com\n\t\nfunpay.com\nDIRECT\n\tAccount Exchange\tSSA § 2.G, SSA § 4.C, SSA § 1.C\tSee dated evidence\nEX-154\tPlayerAuctions\nplayerauctions.com\n\t\nplayerauctions.com\nDIRECT\n\tGrey Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-155\tEldorado.gg\neldorado.gg\n\t\neldorado.gg\nDIRECT\n\tAccount Portal\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-156\tG2A\ng2a.com\n\t\ng2a.com\nDIRECT\n\tMass Key Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-157\tKinguin\nkinguin.net\n\t\nkinguin.net\nDIRECT\n\tMass Key Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-158\tG2G.com\ng2g.com\n\t\ng2g.com\nDIRECT\n\tVirtual Services\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-159\tPlayerup\nplayerup.com\n\t\nplayerup.com\nDIRECT\n\tAccount Broker\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-160\tZ2U.com\nz2u.com\n\t\nwww.z2u.com\nDIRECT\n\tReady-Account Hub\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-161\tSmurfHub\nsmurfhub.net\n\t\nsmurfhub.net\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-162\tSmurfAccounts\nsmurfaccounts.com\n\t\nsmurfaccounts.com\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-163\tBuyCSGORank\nbuycsgorank.com\n\t\nbuycsgorank.com\nDIRECT\n\tRank Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-164\tCSGOSmurfKings\ncsgosmurfkings.com\n\t\ncsgosmurfkings.com\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-165\tSmurfStore_Co\nsmurfstore.co\n\t\nsmurfstore.co\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-166\tSteamLvlUp\nsteamlvlup.com\n\t\nsteamlvlup.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-167\tSteamLevels\nsteamlevels.com\n\t\nsteamlevels.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-168\tLevelSteam\nlevelsteam.com\n\t\nlevelsteam.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-169\tSteamLevelU\nsteamlevelu.com\n\t\nsteamlevelu.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-170\tEloKing\neloking.com\n\t\neloking.com\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-171\tBoosteria\nboosteria.org\n\t\nboosteria.org\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-172\tOvergear\novergear.com\n\t\novergear.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-173\tBlazingBoost\nblazingboost.com\n\t\nblazingboost.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-174\tDota2Boost\ndota2boost.com\n\t\ndota2boost.com\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-175\tBuyBoost\nbuyboost.com\n\t\nbuyboost.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nالقسم الرابع: البنية التقنية وآليات المصادقةالمرجع: TECH-ANALYSIS-01\n\n1. عدم وجود التحقق من ملكية النطاق في OpenID 2.0: تطبيق موقع Valve لبروتوكول OpenID 2.0 (https://steamcommunity.com/openid/login) يقيّم الـ openid.return_to و openid.realm المعلمات دون الحاجة إلى تسجيل مسبق للمطور، أو التحقق من التحدي التشفيري، أو التحقق من ملكية النطاق. يمكن لأي مشغل تجاري توجيه المستخدمين إلى شاشة تسجيل الدخول الخاصة بـ Valve والحصول على تأكيد هوية موقّع تشفيرياً (يحتوي على SteamID المكون من 64-بت) يتم إعادة توجيهه إلى نطاقات عشوائية.\n\n2. الاستعلام البرمجي عن المخزون وإساءة استخدام مفتاح «API»: بمجرد تأكيد مصادقة المستخدم عبر OpenID، يقوم المشغلون بالاستعلام عن نقاط النهاية العامة ونقاط النهاية الخاصة بالشركاء على الويب API (IEconItems_730/GetPlayerItems) لفهرسة أصول المخزون في الوقت الفعلي. وتستخدم شبكات التداول الآلية رموز جلسات برمجية لتقديم عروض التداول بين الأقران (P2P) واستقصائها وقبولها، مما يتعارض بشكل مباشر مع الحظر الوارد في المادة §4.C من قانون SSA بشأن التفاعل غير البشري.\n\n3. عدم التماثل في تصفية الروابط: إن وجود تحذيرات تتعلق بالنطاقات الموجهة للمستهلكين جنبًا إلى جنب مع نقاط نهاية المصادقة التي تعمل بكامل طاقتها يخلق تناقضًا تنظيميًّا: فأنظمة قياس الأداء الأمني الخاصة بـ Valve تصنف هذه الجهات المشغلة على أنها «محتملة الخطر»، ومع ذلك تواصل البنية التحتية للمصادقة الخاصة بـ Valve المصادقة على قاعدة مستخدميها.\n\nمنهجية الإثبات وإقرار سلسلة الحراسة\n\nتم إعداد هذا المستند استنادًا إلى بيانات تم التقاطها من الشبكة دون مصادقة، واستعلامات سجل «RDAP» التاريخية، وقوائم التجزئة التشفيرية التي تم التحقق من صحتها. ولم يتم اختبار أو معالجة أي بيانات اعتماد لتسجيل دخول المستخدمين. وتعكس جميع النتائج الحالة الملحوظة لشبكة الإنتاج اعتبارًا من 9 سبتمبر 2026. ويُعد هذا المستند دليلاً تقنيًّا محايدًا تم إعداده لتلبية احتياجات التحقيقات القضائية والتنظيمية والعامة.\n\nملخص: SHA-256 تم التحقق منه\nc507c9025f93da0aadaf395c4d8882f25973211c318ee8e9b6f18a5b3755e050\nالأرشيف: السجل القانوني المفتوح\nصدر عن ووقّعه: phishdestroy.io · تحالف الأبحاث الجنائية\nالوضع القانوني: تم التنازل عن جميع الحقوق لصالح الإنسانية · CC0 المجال العام العالمي",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "قانون التدقيق الجنائي والملحق التنظيمي"
          }
        ],
        "links": []
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ar/regulatory_act_print.content.json",
      "export_json_sha256": "bdcdc7ffa409b94cdb04352e1e2f1c9022c61b901f6b03d916328e541eccf598"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ar/security_timeline.html",
      "language": "ar",
      "title": "الجدول الزمني للأحداث الأمنية — ملف «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/ar/security_timeline",
      "source_html_sha256": "362a20839cc734e1a41b51d8fd402f854297ade0e6aefb0b3a17d8ce05d9a19f",
      "exported_at": "2026-09-29T00:20:13.840Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "security_timeline.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ar/security_timeline.pdf?v=print-20260929-v5",
        "sha256": "47ba4a9e77a283c1176d3404ed29069342d7e94f0feb51e8c4606b67619fe5b2",
        "bytes": 129905,
        "pages": 6
      },
      "integrity": {
        "signed_object": "security_timeline.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "security_timeline.content.json.asc",
        "digest_file": "security_timeline.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify security_timeline.content.json.asc security_timeline.content.json",
          "sha256sum -c security_timeline.content.json.sha256"
        ]
      },
      "content": {
        "text": "سجل الأداء الأمنيمعرض / المشاركات في مسابقة «16»\n\n2018 — 2026\n\nالخط الزمني للأمن — من 2018 إلى 2026\n\nتم تغيير الإجراءات الأمنية. اتبع السجل.\n\nما يثبته هذا القسم\n\nيُعيد هذا السجل الزمني بناء ثماني سنوات من التعديلات الأمنية التي طرأت على منصة التداول والتوثيق الخاصة بـ «Steam». ويتتبع السجل تنفيذ فترة حظر التداول اليومي (2018) 7-، و2023، والتأكيدات الرئيسية عبر الهاتف المحمول (Web API)، وإلغاء استخدام رموز الجلسة (session token) 2026، وذلك في مواجهة تقنيات التحايل الموثقة. ويثبت هذا الجدول الزمني أن تحديثات المنصة كانت تتأخر باستمرار عن نقاط الاستغلال المعروفة، مع الحفاظ في الوقت نفسه على المزايا الهيكلية للمشغلين التجاريين.\n\n← العودة إلى ملخص الإدارة التنفيذية\n\nأقفال التداول. ضوابط تسجيل الدخول. قيود «API». سجل مؤرخ بالتغييرات التي طرأت — وما تثبته المصادر فعليًّا.\n\nاستكشف الخط الزمني ↓\nثماني سنوات. رقم قياسي واحد.16المراحل الرئيسية التي يجب دراستها\n\nيحتفظ كل إدخال بتاريخ إرساله ومصدره. ويظهر التحقق بجانبه.\n\nتمت مراجعته / 24 سبتمبر 2026\n10حدث وتاريخ مؤكدان\n06تم التحقق منه جزئيًا\n00عدم تطابق المصدر\n00يلزم ذكر المصدر\nكيفية قراءة هذا السجل\n\nالحدث والتاريخ المؤكدان: وكلاهما مدعوم بمصدر أولي يمكن الاطلاع عليه. تم التحقق منه جزئيًا: تم توثيق تغيير ذي صلة، لكن التاريخ أو نطاقه لم يتم تحديدهما بعد. عدم تطابق المصدر: المواد المرفقة لا تدعم الادعاء المقدم. يلزم ذكر المصدر: لم يتم التحقق من أي مصدر مؤرخ مطابق في هذه المراجعة. ولا يُعد وجود إدخال لم يتم حله دليلاً على أن الحدث لم يحدث.\n\nالتواريخ الواردة في البنود التي لم يتم البت فيها هي تواريخ التقديم، وليست تواريخ إصدار مؤكدة. ولم يتم إعادة صياغة نص التحقيق الأصلي.\n\nالتسلسل الزمني\n01 — 16\nالبحث في السجلالموضوعالأدلةالطلب\n\n16 من مشاركات موقع 16 · الأحدث أولاً\n\n202609-01تاريخ التقديم\nالمجتمعتم التحقق منه جزئيًا\nتحذيرات بشأن الرسائل المشبوهة في الدردشات الجماعية\n\nيؤكد إعلان رسمي عن الإصدار التجريبي توفر هذه الميزة في 31 أغسطس. أما تاريخ الإصدار المستقر المحدد في 1 سبتمبر، فلا يزال بحاجة إلى مذكرة إصدار محددة.\n\nSteam الإصدار التجريبي للعملاء — 1 أغسطس 31 ↗محفوظ على 2026-03-13 ↗\nالمدخلة الأصلية والرابط المقدم\n\nالإبلاغ الآلي عن المحادثات المشبوهة\n\nافحص الكود المقدم ↗\n202601-16تاريخ التحقق\nAPIحدث وتاريخ مؤكدان\nأذونات محددة بدقة وقائمة بيضاء لعناوين IP لمفاتيح الناشرين (إعلان Valve)\n\nفي 16 يناير 2026, Valve، نُشر إعلان رسمي من Steamworks (\"جديد: أذونات وضوابط محسّنة لمفاتيح الويب API\") التي تؤكد وجود أدوات جديدة للأذونات التفصيلية تتيح للمطورين تقسيم مفاتيح الويب API إلى مجموعات منفصلة (بيانات عامة، والمعاملات الصغيرة، والاقتصاد، والمبيعات)، وتقييد استخدام المفاتيح على معرّفات تطبيقات محددة، وفرض قائمة بيضاء لعناوين IP الخاصة بالخوادم.\n\nالمعيار المزدوج الصارخ: يؤكد هذا الإعلان الرسمي أن موقع Valve قد أنجز بالكامل تطوير البنية التحتية التقنية اللازمة لتطبيق أذونات دقيقة على موقع API وفرض قيود على عناوين IP، ولكن يمنعها عمدًا عن حسابات المستخدمين العادية (steamcommunity.com/dev/apikey). تظل مفاتيح \"API\" التي يستخدمها المستخدمون العاديون بيانات اعتماد متجانسة من نوع «كل شيء أو لا شيء»، دون أي قائمة بيضاء لعناوين IP — وهو بالضبط الإغفال التقني الذي يتيح وجود صناعة اعتراض المعاملات التي تبلغ قيمتها ملايين الدولارات API.\n\nValve إعلان — جديد: أذونات وضوابط محسّنة لمفاتيح الويب API (16 Jan 2026) ↗· الوثائق: المصادقة عبر الويب API في Steamworks ↗\nالمدخلة الأصلية والرابط المقدم\n\nموقع Steamworks على الويب API: نطاقات تفصيلية\n\nاطلع على الإعلان الرسمي عن لعبة «Valve» على منصة Steamworks (493839547938902179) ↗\n202507-15تاريخ التحقق\nالتداولحدث وتاريخ مؤكدان\nتداولات CS2 تحظى بفترة انعكاس مدتها سبعة أيام\n\nيعلن بيان «Valve» الصادر مؤخرًا عن إلغاء عمليات تداول عناصر لعبة «Counter-Strike» التي تمت خلال الأيام السبعة الماضية. ورغم أن هذا الإجراء يهدف إلى الحد من عمليات الاختراق، إلا أن عمليات التدقيق الاقتصادي التي تجريها أطراف ثالثة (CSMarketCap ↗) سجلت $104M (-25%) طي في القيمة السوقية خلال ساعات 24 بسبب اضطراب في التداول النقدي. وفقًا للتحليل الذي أجرته Skinvault ↗، ويؤدي تفعيل آلية التراجع إلى فرض حظر تلقائي على التداول اليومي لمدة 30-على الحساب. في الصيف 2026, Valve، تم التحول من إعادة الضبط العالمية في منتصف الليل بتوقيت UTC إلى مؤقتات دقيقة فردية لكل عنصر (Skin.land ↗).\n\nValve — إعلان «15» الصادر في يوليو 2025 ↗· تحليل CSMarketCap ↗\nالمدخلة الأصلية والرابط المقدم\n\nحماية التداول في CS2 / نافذة التراجع\n\nافحص الكود المقدم ↗\n202505-14تاريخ التحقق\nالمصادقةحدث وتاريخ مؤكدان\nValve تنشر تحذيرًا بشأن أمن الحسابات يتعلق بتسرب الرسائل النصية القصيرة\n\nيتناول الإعلان الرسمي الذي أصدرته شركة Valve في 5 مايو 14, 2025, مسألة أمن الحسابات وأدوات المصادقة القائمة على الرسائل النصية القصيرة (SMS). ورغم أن الإعلان يركز على تسرب الرسائل النصية القصيرة ويؤكد عدم تعرض أنظمة Steam لأي اختراق، إلا أنه يُعد تحديثًا أمنيًا رسميًا بتاريخ نشره.\n\nValve — ملاحظة بشأن أمان حسابك على Steam ↗\nالمدخلة الأصلية والرابط المقدم\n\nإعلان بشأن أمان الحساب\n\nافحص الكود المقدم ↗\n202410-02تاريخ التحقق\nالتداولحدث وتاريخ مؤكدان\nقبل سبعة أيام من إعادة التداول أو إعادة التسويق\n\nتغطي ملاحظات الإصدار العناصر التي يتم الحصول عليها من خلال متجر اللعبة، بما في ذلك «الترسانة» وعروض التبادل و«سوق المجتمع». ويشمل النطاق الموثق أكثر من مجرد عناصر «الترسانة» وحدها.\n\nValve — ملاحظات الإصدار الخاصة بـ 10/2/2024 ↗\nالمدخلة الأصلية والرابط المقدم\n\nCS2 «ذا أرموري» / «7-» - يوم واحد\n\nافحص الكود المقدم ↗\n202409-18تاريخ التقديم\nالتداولتم التحقق منه جزئيًا\nتم التحقق من قيود الأجهزة الجديدة في صفحات المساعدة\n\nتؤكد وثائق الدعم الرسمية لـ Steam وجود قيود على التداول اليومي (7-) عند تسجيل الدخول من جهاز جديد لم يتم اعتماده منذ ما لا يقل عن 7 يومًا. ورغم أن تاريخ الإطلاق الدقيق في سبتمبر 18, 2024, لم يُسجَّل كمعلم في سجل التغييرات، إلا أن هذه الوظيفة موثقة بالكامل.\n\nSteam الدعم — قيود التداول والسوق ↗\nالمدخلة الأصلية والرابط المقدم\n\nقيود التداول الجديدة المتعلقة بتسجيل الدخول من جهاز جديد\n\nافحص الكود المقدم ↗\n202402-14تاريخ التقديم\nالمجتمعتم التحقق منه جزئيًا\nتم تطبيق فترة الانتظار الخاصة بتغيير الاسم في 2024\n\nتؤكد سجلات المجتمع والمطورين أنه في أوائل عام 2024, Valve تم إدخال فترة انتظار غير معلنة 2-لمدة4 ساعة بعد تغيير اسم الملف الشخصي مباشرةً، وذلك للحد من عمليات الاحتيال السريعة التي تتم عن طريق انتحال الهوية. ونظرًا لأن Valve لم تنشر أي بيان صحفي رسمي أو سجل تغييرات في العميل أو مقال دعم بشأن هذا القيد، فإن التاريخ المقدم في فبراير 14 يفتقر إلى التحقق الرسمي؛ ويُعد دليل ورشة العمل Steam بمثابة تأكيد غير مباشر من المجتمع وليس وثيقة رسمية Valve.\n\nSteam دليل ورشة العمل (التأكيد غير المباشر) — تفاصيل القيود المفروضة على تغيير الاسم ↗\nالمدخلة الأصلية والرابط المقدم\n\nتجميد تغيير اسم الملف الشخصي / الصورة الرمزية\n\nافحص الكود المقدم ↗\n202312-04تاريخ التحقق\nAPIحدث وتاريخ مؤكدان\nيتطلب إنشاء المفتاح تأكيدًا عبر الهاتف المحمول\n\nتم التحقق من أن تطبيق نظام التأكيد الإلزامي عبر الهاتف المحمول من خلال خدمة الحراسة (Steam Guard) لإنشاء مفاتيح الويب (API) قد تم في أواخر 2023,، وفقًا لما وثقته مكتبات المطورين التابعة لأطراف ثالثة. ويمثل التاريخ المحدد في ديسمبر 4, 2023, فترة النشر التي لوحظت داخل مجتمع المطورين.\n\nوثائق المسؤول عن الصيانة — مارس 2024 ↗محفوظ على 2026-09-24 ↗\nالمدخلة الأصلية والرابط المقدم\n\nالتأكيد عبر الهاتف المحمول لمفاتيح API\n\nافحص الكود المقدم ↗\n202310-24تاريخ التحقق\nالمطورحدث وتاريخ مؤكدان\nدخلت القاعدة الإلزامية 2FA الخاصة بتحديد إصدارات الألعاب المباشرة حيز التنفيذ\n\nيؤكد الإعلان الرسمي لـ Valve على Steamworks الصادر في 10, 2023, أنه اعتبارًا من 24, 2023,، يجب على أي حساب يقوم بنشر إصدار على الفرع الافتراضي لتطبيق تم إصداره أن يصادق على التغيير عبر رسالة SMS أو تطبيق Steam للهواتف المحمولة. وقد أدى هذا التغيير إلى تحديث مباشر لصفحة الويب SetAppBuildLive API.\n\nSteamworks — تحسينات أمنية لإدارة الإصدارات والمستخدمين ↗محفوظ على 2025-12-03 ↗\nالمدخلة الأصلية والرابط المقدم\n\nالرسائل القصيرة (SMS) الخاصة بـ MFA لنشر إصدارات الألعاب\n\nافحص الكود المقدم ↗\n202307-12تاريخ التقديم\nالمجتمعتم التحقق منه جزئيًا\nتحذيرات خاصة بمحتوى السيرة الذاتية المخصصة التي لاحظها أعضاء المجتمع\n\nSteam تشير تقارير المجتمع التي بدأت في يوليو 2023 إلى أن السير الذاتية المخصصة في الملفات الشخصية التي تحتوي على روابط خارجية أو كلمات محفزة بدأت في عرض تحذيرات محتوى آلية. ويتطابق تاريخ الإبلاغ في يوليو 12, 2023, مع الموجة الأولى من تقارير المستخدمين على منتديات المجتمع Steam.\n\nSteam منتدى المجتمع — تقارير التحذير بشأن المحتوى المتعلق بالسيرة الذاتية ↗\nالمدخلة الأصلية والرابط المقدم\n\nتحذير بشأن محتوى السيرة الذاتية المخصصة\n\nافحص الكود المقدم ↗\n202301-25تاريخ التقديم\nالمجتمعتم التحقق منه جزئيًا\nفترات الانتظار الخاصة بتصفية روابط الملفات الشخصية وتحريرها قيد التشغيل\n\nتؤكد وثائق الدعم الرسمية لـ Steam أن الروابط الواردة في السير الذاتية المخصصة تخضع للتصفية، وأن التغييرات المسيئة في الاسم أو الصورة الرمزية قد تؤدي إلى فرض حظر على التعديل. ورغم أن التطبيق الفعلي لفترة الانتظار التي تبلغ ساعة واحدة 4-في 1 يناير 25, 2023, يمثل البداية الملحوظة لهذا الإجراء، فإن آلية تصفية الروابط نفسها تعمل بكامل طاقتها وفقًا لما ورد في صفحة المساعدة التي تم تقديمها.\n\nSteam الدعم — القيود المفروضة على اسم الملف الشخصي والصورة الرمزية ↗\nالمدخلة الأصلية والرابط المقدم\n\nالملف الشخصي: تم حذف الرابط / فترة الانتظار\n\nافحص الكود المقدم ↗\n202210-24تاريخ التحقق\nالمصادقةحدث وتاريخ مؤكدان\nSteam انتقال العميل إلى رموز تجديد OAuth ورموز الوصول\n\nأهم تحديثات Valve الخاصة بالعملاء وتطبيقات الهاتف المحمول في أكتوبر 2022 أجرت تعديلات جذرية على نظام المصادقة Steam. تم استبدال بنية ملفات تعريف الارتباط (cookie) القديمة الخاصة بالجلسات برموز وصول وتجديد تستند إلى بروتوكول OAuth، كما تم إدخال قائمة بالأجهزة المصرح لها النشطة للسماح بإلغاء الجلسات النشطة يدويًّا.\n\nValve — تحديث تطبيق «Steam» للهواتف المحمولة وإجراء تعديل شامل على نظام المصادقة ↗\nالمدخلة الأصلية والرابط المقدم\n\nSteam تجديد عملية تسجيل الدخول / اقتطاع ملفات تعريف الارتباط\n\nاطلع على إعلان موقع Valve ↗\n202210-12تاريخ التحقق\nالمصادقةحدث وتاريخ مؤكدان\nتسجيل الدخول عبر رمز الاستجابة السريعة وإدارة الأجهزة المصرح بها\n\nيصف الإعلان الذي نشرته شركة Valve في أكتوبر حول برنامج «12» () عملية تسجيل الدخول باستخدام رموز QR، والموافقة على عمليات تسجيل الدخول أو رفضها، بالإضافة إلى قائمة بالأجهزة التي يمكنها إلغاء حق الوصول إلى الحساب.\n\nValve — أصبح تطبيق «Steam» المحدث للهواتف المحمولة متاحًا الآن ↗\nالمدخلة الأصلية والرابط المقدم\n\nSteam تطبيق الهاتف المحمول 3.0 / تسجيل الدخول عبر رمز الاستجابة السريعة (QR)\n\nافحص الكود المقدم ↗\n202205-10تاريخ التقديم\nAPIتم التحقق منه جزئيًا\nتم حذف نقاط نهاية إلغاء الصفقات من قائمة API العامة\n\nتؤكد سجلات المطورين أن موقع 2022, Valve قد أزال في شهر مايو، دون إعلان مسبق، نقاط نهاية إدارة التداول مثل IEconService/CancelTradeOffer و DeclineTradeOffer من الويب API (كما هو موثق في node-steam-tradeoffer-manager #325). ورغم أن هذه الطرق لا تزال تعمل في بروتوكولات العملاء الخاصة، فإن تاريخ 10, 2022, يمثل تاريخ إزالتها الفعلي من واجهات برمجة التطبيقات (API) العامة على الويب لمكافحة لوحات الاحتيال.\n\nمناقشة المطورين — المشكلة رقم325 (تمت إزالة ميزة CancelTradeOffer) ↗· موقع Steamworks على الويب API — وثائق خدمة IEconService ↗\nالمدخلة الأصلية والرابط المقدم\n\nإزالة نقاط نهاية إلغاء الصفقات\n\nاطلع على المشكلة رقم325 في node-steam-tradeoffer-manager ↗\n202005-25تاريخ التحقق\nالتداولحدث وتاريخ مؤكدان\nتخضع العناصر في لعبة «Dota2» لفترة انتظار مدتها سبعة أيام قبل التداول\n\nفي 25, مايو، 2020, بالتزامن مع إطلاق «بطاقة المعركة» لبطولة «10» الدولية (blog.dota2.com/2020/05/the-international-10-battle-pass/)، Valve فرضت حظرًا على تداول عناصر لعبة «Dota» 2 لمدة يوم واحد (7-)، تماشيًا مع سياسة «Counter-Strike» 2018. وينطبق هذا القيد على جميع العناصر المتداولة والمشتريات من «السوق».\n\nمجتمع Dota 2 — قفل التبادل وتحديث عميل TI10 ↗\nالمدخلة الأصلية والرابط المقدم\n\nDota 2 / 7-قفل التداول اليومي\n\nافحص الكود المقدم ↗\n201803-29تاريخ التحقق\nالتداولحدث وتاريخ مؤكدان\nتخضع العناصر المتداولة في لعبة CS:GO لفترة انتظار مدتها سبعة أيام\n\nتؤكد ملاحظات الإصدار الرسمية التاريخ والقيود المفروضة. كان الرابط المرفق يعيد التوجيه إلى تحديث خريطة على الرابط 2013؛ أما رابط ملاحظات الإصدار المطابق فينتهي بـ 20309.\n\nValve — ملاحظات الإصدار الخاصة بـ 3/29/2018 ↗\nالمدخلة الأصلية والرابط المقدم\n\nCS:GO / قفل التداول اليومي لـ «7-»\n\nافحص الكود المقدم ↗ محفوظ على 2025-02-26 ↗\n\nاتبع الأدلة. تحقق من المصدر.\n\nالعودة إلى التحقيق ↗",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "الخط الزمني للأمن — من 2018 إلى 2026"
          },
          {
            "level": 2,
            "id": null,
            "text": "التسلسل الزمني"
          },
          {
            "level": 2,
            "id": null,
            "text": "تحذيرات بشأن الرسائل المشبوهة في الدردشات الجماعية"
          },
          {
            "level": 2,
            "id": null,
            "text": "أذونات محددة بدقة وقائمة بيضاء لعناوين IP لمفاتيح الناشرين (إعلان Valve)"
          },
          {
            "level": 2,
            "id": null,
            "text": "تداولات CS2 تحظى بفترة انعكاس مدتها سبعة أيام"
          },
          {
            "level": 2,
            "id": null,
            "text": "Valve تنشر تحذيرًا بشأن أمن الحسابات يتعلق بتسرب الرسائل النصية القصيرة"
          },
          {
            "level": 2,
            "id": null,
            "text": "قبل سبعة أيام من إعادة التداول أو إعادة التسويق"
          },
          {
            "level": 2,
            "id": null,
            "text": "تم التحقق من قيود الأجهزة الجديدة في صفحات المساعدة"
          },
          {
            "level": 2,
            "id": null,
            "text": "تم تطبيق فترة الانتظار الخاصة بتغيير الاسم في 2024"
          },
          {
            "level": 2,
            "id": null,
            "text": "يتطلب إنشاء المفتاح تأكيدًا عبر الهاتف المحمول"
          },
          {
            "level": 2,
            "id": null,
            "text": "دخلت القاعدة الإلزامية 2FA الخاصة بتحديد إصدارات الألعاب المباشرة حيز التنفيذ"
          },
          {
            "level": 2,
            "id": null,
            "text": "تحذيرات خاصة بمحتوى السيرة الذاتية المخصصة التي لاحظها أعضاء المجتمع"
          },
          {
            "level": 2,
            "id": null,
            "text": "فترات الانتظار الخاصة بتصفية روابط الملفات الشخصية وتحريرها قيد التشغيل"
          },
          {
            "level": 2,
            "id": null,
            "text": "Steam انتقال العميل إلى رموز تجديد OAuth ورموز الوصول"
          },
          {
            "level": 2,
            "id": null,
            "text": "تسجيل الدخول عبر رمز الاستجابة السريعة وإدارة الأجهزة المصرح بها"
          },
          {
            "level": 2,
            "id": null,
            "text": "تم حذف نقاط نهاية إلغاء الصفقات من قائمة API العامة"
          },
          {
            "level": 2,
            "id": null,
            "text": "تخضع العناصر في لعبة «Dota2» لفترة انتظار مدتها سبعة أيام قبل التداول"
          },
          {
            "level": 2,
            "id": null,
            "text": "تخضع العناصر المتداولة في لعبة CS:GO لفترة انتظار مدتها سبعة أيام"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/ar/#briefing-heading",
          "https://steamcommunity.com/groups/SteamClientBeta?l=english",
          "http://web.archive.org/web/20260313235409/https://steamcommunity.com/groups/SteamClientBeta?l=english",
          "https://store.steampowered.com/news/posts/?enddate=1788390000",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/493839547938902179",
          "https://partner.steamgames.com/doc/webapi_overview/auth",
          "https://csmarketcap.com/blog/market-insights/from-boom-to-bust-cs2s-trade-protection-impact",
          "https://skinvault.gg/blog/cs2-trade-protection-explained/",
          "https://skin.land/blog/steam-changes-cs2-trade-ban-logic-timing/",
          "https://store.steampowered.com/news/posts/?appids=730&amp;enddate=1753924057&amp;feed=steam_announce%2F1000",
          "https://help.steampowered.com/faqs/view/3041-A87A-E5F6-B6AC",
          "https://store.steampowered.com/news/posts/?enddate=1747349559",
          "https://steamcommunity.com/ogg/593110/announcements/detail/533224478739530146",
          "https://store.steampowered.com/news/posts/?appids=730&amp;enddate=1728000977&amp;feed=steam_community_announcements",
          "https://steamcommunity.com/games/CSGO/announcements/detail/4447966961421256740",
          "https://help.steampowered.com/faqs/view/7F77-9E92-31E0-6B8E",
          "https://steamcommunity.com/sharedfiles/filedetails/?id=2926756889",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "http://web.archive.org/web/20260924181824/https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "https://steamcommunity.com/dev/apikey",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3749866608167579206",
          "http://web.archive.org/web/20251203174259/https://steamcommunity.com/groups/steamworks/announcements/detail/3749866608167579206",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3734103130194459461",
          "https://steamcommunity.com/discussions/forum/1/3807266184852932971/",
          "https://help.steampowered.com/faqs/view/225C-C51E-B8F0-55B2",
          "https://store.steampowered.com/news/group/4/view/3314112260640237775",
          "https://store.steampowered.com/news/posts/?appgroupname=Keep+in+touch&amp;enddate=1666122699&amp;feed=steam_blog",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/issues/325",
          "https://partner.steamgames.com/doc/webapi/IEconService",
          "https://steamcommunity.com/app/570/announcements/",
          "https://blog.dota2.com/2020/05/trading-cooldown/",
          "https://blog.counter-strike.net/2018/03/20309/",
          "https://blog.counter-strike.net/index.php/2018/03/20308/",
          "http://web.archive.org/web/20250226114333/https://blog.counter-strike.net/index.php/2018/03/20308/",
          "https://phishdestroy.io/steam_dossier/ar/#vulnerability-profile"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ar/security_timeline.content.json",
      "export_json_sha256": "5e43bfecfa24511253cdbc8b5704a7927d46db6012436f328f91167f886c633a"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ar/skin_atlas.html",
      "language": "ar",
      "title": "أطلس الأشياء التي لا يمكن لـ «Steam» حملها — ملف «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/ar/skin_atlas",
      "source_html_sha256": "b004db94ce12a5d4dfeca9a3b2b5248b1e8180955dc33b01ba35ad3575b6e2cc",
      "exported_at": "2026-09-29T00:20:20.656Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "gallery",
            "source": "https://phishdestroy.io/steam_dossier/ar/skin_atlas#gallery"
          }
        ],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "skin_atlas.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ar/skin_atlas.pdf?v=print-20260929-v5",
        "sha256": "c80e4b113b6654aa6957c4fa648fff99e6a13143af19d5788f2a1664862b199b",
        "bytes": 213350,
        "pages": 13
      },
      "integrity": {
        "signed_object": "skin_atlas.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "skin_atlas.content.json.asc",
        "digest_file": "skin_atlas.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify skin_atlas.content.json.asc skin_atlas.content.json",
          "sha256sum -c skin_atlas.content.json.sha256"
        ]
      },
      "content": {
        "text": "الملحق IV-B / سلم الأسعار / 2026-09-23\nأطلس سلم أسعار «سكين» — «منحدر السيولة»\n\nمحطات التوقف في سوق Valve من أين يأتي المال.\n\nما يثبته هذا القسم\n\nيحلل هذا الأطلس المرئي فئات المنتجات الخاصة بـ «30,266» عبر خمسة كتالوجات للأسواق الإلكترونية، ويقيس التغطية السوقية فوق وتحت عتبة الإدراج المحددة من قبل «Valve». تحت الحد الأقصى البالغ $1,800، يستضيف موقع Steam 95.3% من الفئات النشطة؛ أما فوق هذا الحد مباشرةً، فتنخفض التغطية الرسمية إلى 1.9% (مع تغطية 0.0% عبر الأصول المؤكدة). ويُظهر هذا انخفاضًا حادًا وجوهريًّا في السيولة، حيث Valve تفوض اكتشاف المعاملات عالية القيمة إلى منصات خارجية مع الاحتفاظ بالسيطرة الكاملة على حفظ الأصول الأساسية.\n\nWhat this means — the Community Market listing ceiling\n\nSteam’s own market refuses a listing above roughly $1,800. A seller may ask less, never more. Items whose market price sits above that line therefore cannot be sold at that price on Steam at all — which is the mechanism that moves those sales to third-party venues while the item itself never leaves Valve’s inventory system.\n\nSection 13 — the off-Steam price gap →\n\n← العودة إلى ملخص الإدارة التنفيذية\n\nتم تصنيف كل منتج من منتجات CS2 الذي يتوفر له سعر فعلي في خمسة أسواق ضمن نطاق سعري بناءً على أرخص سعر عرض له، وتم قياس كل نطاق وفقًا لمعيار واحد: ما هي الحصة التي لا يزال سوق المجتمع التابع لـ «Valve» يستحوذ عليها ضمن هذا النطاق. وفيما يتعلق بالحد الأقصى لعدد العروض المسموح به في «Valve»، فإن الإجابة هي 95.3%. وفوقها، الإجابة هي 1.9%. هذا الانخفاض ليس تدريجيًا، ولا يحدث في الأماكن التي ينخفض فيها الطلب — بل يحدث بالضبط وفقًا للقاعدة المنشورة. ومن بين 248 فئات المنتجات التي تحدد سوقان أو أكثر أسعارها بشكل مستقل بما يتجاوز الحد الأقصى، 100.0% لا توجد لها أي قائمة على الإطلاق على موقع Steam.\n\nانظر إلى المنحدر ↓افتح معرض صور منتجات «419»الطريقة والقيود\n30,266فئات العناصر التي تم قياسها\n95.3%من البنود التي لا تدخل في رأس المال والتي تحتفظ بها شركة «Steam»\n1.9%من المنتجات التي تتجاوز الحد الأقصى والتي تبيعها شركة «Steam»\n$78.6Mالقيمة الدنيا للمجموعة المؤكدة\n01 / القياس\nيُطبق هذا الشرط تلقائيًا، وليس بناءً على طلب\n\nيتم تصنيف كل فئة من فئات المنتجات الواردة أدناه في موقع 30,266 ضمن شريحة معينة وفقًا لـ الأرخص يتم إجراء الاستطلاع المباشر عبر BUFF163 وCSFloat وSkinport وYouPin 898 وC5Game، ولا يتم احتساب سوى العناصر المذكورة في اثنين أو أكثر من هذه المنصات، لذا لا يمكن لأي قائمة متفائلة بمفردها أن «تخترع» عضوًا في الفرقة. ويُظهر الجزء العلوي من الجدول الحصة التي لا تزال تحتفظ بها كل فرقة في السوق الخاصة بموقع Valve.\n\nحصة كل شريحة سعرية في سوق «Steam» المجتمعي\nالجزء العلوي: تغطية البخار · الجزء السفلي: العناصر لكل نطاق، مقياس لوغاريتمي\n0%\n25%\n50%\n75%\n100%\n100%\n96.9%\n95.9%\n97.3%\n91.1%\n76.8%\n14.5%\n2.9%\n1.5%\n0%\n0%\n0%\n4,632\n1¢–10¢\n7,152\n10¢–$1\n8,568\n$1–10\n5,941\n$10–100\n2,329\n$100–300\n1,292\n$300–1k\n193\n$1k–1.8k\n70\n$1.8k–3k\n67\n$3k–10k\n18\n$10k–30k\n3\n$30k–100k\n1\n$100k+\nitems\nlog\nVALVE’S LISTING CAP\nعند أو أقل من الحد الأقصى للإدراج في بورصة «Valve»تجاوز الحد الأقصى — تنص قاعدة «Valve» على حظر الإدراجفئات العناصر في الفرقة\n\nتشير «التغطية» إلى وجود طلب مباشر على موقع Steam لتلك الفئة في لحظة التسجيل. ويُعرض اللوحة السفلية على مقياس لوغاريتمي لأن أسعار الكتالوج رخيصة للغاية: فقراءتها خطيًّا من شأنها أن تجعل كل نطاق يزيد سعره عن $300 يندمج مع خط الأساس.\n\nما تستبعده هذه الشكلية\n\nلو كانت السلع باهظة الثمن مجرد سلع غير مرغوبة، لانخفضت نسبة تغطيتها تدريجيًّا مع ارتفاع السعر. لكن هذا لا يحدث. فهي تظل ثابتة عند 76.8% عبر النطاق الذي يتراوح بين $300–$1k، ثم تنهار إلى 14.5% في النطاق الواقع مباشرةً أسفل الحد الأقصى، وإلى 2.9% في النطاق الواقع مباشرةً فوقه. تأثير الطلب لا يعرف أين Valve يحدد سقفه. أما القاعدة، فهي تعرف ذلك.\n\nنطاق السعر\tفئات المنتجات\tمع سؤال مباشر على موقع «Steam»\tSteam التغطية\tالنسخ المدرجة مأخوذة من موقع Steam\n1¢–10¢\t4,632\t4,632\t100%\t8,223,227\n10¢–$1\t7,152\t6,931\t96.9%\t5,488,315\n$1–10\t8,568\t8,213\t95.9%\t3,939,538\n$10–100\t5,941\t5,780\t97.3%\t1,328,255\n$100–300\t2,329\t2,121\t91.1%\t364,466\n$300–1k\t1,292\t992\t76.8%\t187,504\n$1k–1.8k\t193\t28\t14.5%\t40,281\n$1.8k–3k\t70\t2\t2.9%\t9,592\n$3k–10k\t67\t1\t1.5%\t6,706\n$10k–30k\t18\t0\t0%\t1,366\n$30k–100k\t3\t0\t0%\t21\n$100k+\t1\t0\t0%\t2\n\nيُستثنى من هذا الترتيب متغيرات الأنماط والمراحل: لا يُدرج موقع Steam فئة «الأحجار الكريمة الزرقاء» أو مرحلة «الياقوت» كمدخل مستقل إلى السوق، لذا فإن احتسابها من شأنه أن يقلل من تغطية موقع Steam. وعند القياس دون شرط وجود سوقين، يظهر نفس الترتيب على النحو التالي: 79.1% تحت الحد الأقصى و6.5% فوقه عبر عناصر 37,204 — وهي فجوة أكثر وضوحًا، مبنية على أدلة أضعف، ولهذا السبب لم يتم الاستشهاد بهذا الرقم.\n\n02 / تصنيف الأدلة\nالسعر المطلوب ليس سعرًا\n\nيمكن لأي شخص عرض طراز P2000 للبيع بسعر يبلغ عشرة ملايين يوان. وقبل استخدام أي رقم وارد في هذه الصفحة لأي غرض كان، يتم تصنيفه بناءً على عدد المنصات التجارية التي تقدر قيمة هذا المنتج بشكل مستقل بسعر يتجاوز الحد الأقصى، ومدى ترابط متوسط تلك التقديرات. ولا يتم ذكر سوى الدرجتين «أ» و«ب» — سواء هنا أو في أي مكان آخر في هذا التقرير.\n\nA  ثلاثة أرفف أو أكثر متطابقة\n\nتقدم ثلاث منصات بيع أو أكثر أسعارًا للمنتج المذكور أعلى من الحد الأقصى، ويقع متوسط أسعارها ضمن نطاق 25% من أرخص الأسعار. 197 الفئات، 18,218 نسخ، $76,585,587.\n\nغائبون عن موقع «Steam»: 100.0%.\n\nB  هناك توافق بين الرفين\n\nيتفق سوقان على سعر أعلى من الحد الأقصى، أو يتفق ثلاثة أسواق على سعر أقل منه بفارق طفيف. 51 الفئات، 176 نسخ، $2,038,814.\n\nغائبون عن موقع «Steam»: 100.0%.\n\nC  رف واحد — غير مستخدم\n\nهناك سوق واحد فقط يُعرض فيه سعر البيع الوحيد الذي يتجاوز السقف المحدد. 171 الفئات، نسخ كتاب «247». يتم عرضها في المعرض من باب الاكتمال، وهي مستبعدة من جميع الإجماليات الواردة في هذه الصفحة.\n\nهذه طلبات للحصول على السعر، وليست دليلاً على السعر.\n\nما هي تكلفة هذا التصحيح، وما الذي حققه؟\n\nإن حذف الدرجة «ج» يؤدي إلى إزالة فئات «171» و«$3,825,125» من العنوان. وما يتبقى هو جزء أصغر حجماً وأصعب بكثير في مناقشته: 248 الفئات، 18,394 النسخ المدرجة، $78,624,401, و 100.0% منها — كل واحدة منها — غير متوفرة في سوق Valve. الصفوف من الفئة C هي السبب وراء تغير الرقم؛ فهي معروضة، وليست مخفية.\n\nالقطع المعروضة التي تم تصنيفها كأثر ثقافي\n\nيتم استبعاد أي عرض يزيد عن ثلاثة أضعاف أرخص سعر عرض بيع لنفس السلعة. وعند تحويلها بالسعر الذي تشير إليه البيانات نفسها، يتبين أن معظمها عبارة عن أرقام تقريبية باليوان الصيني — وهو ما يدل على أنها مجرد قيمة مؤقتة أو سقف محدد من قبل المنصة، وليس عرضًا حقيقيًّا. وذلك لأن كل مجموع في هذه الصفحة يستخدم الأرخص اسأل، فلم يكن بإمكان أي من هذه الشخصيات أن تضخم أي رقم على الإطلاق؛ وقد تم استبعادهم حتى لا يُمكن الاستشهاد بأي منهم في العناوين الرئيسية أيضًا.\n\nالعنصر\tأرخص سعر طلب مباشر\tاتركها جانبًا\nSouvenir P2000 | Wicked Sick (Minimal Wear)\t$148,954\t$1,489,543\n★ Specialist Gloves | Crimson Kimono (Minimal Wear) | Phase 1\t$37,239\t$119,163\nSouvenir USP-S | Printstream (Factory New)\t$2,000\t$59,582\n★ Bowie Knife | Crimson Web (Factory New)\t$2,957\t$43,030\n★ Karambit | Marble Fade (Factory New) | 1st\t$11,916\t$38,874\nSticker | Ninjas in Pyjamas (Holo) | Katowice 2014\t$5,000\t$31,748\nSouvenir AWP | Dragon Lore (Battle-Scarred)\t$4,225\t$29,157\n★ Karambit | Doppler (Minimal Wear) | Ruby\t$7,122\t$27,273\nجميع فئات موقع «419»، مع تحديد العنصر الذي يشير إليه كل سعر\n\nالمصدر: https://phishdestroy.io/steam_dossier/ar/skin_atlas#gallery\n\n04 / إلى أين ذهب بدلاً من ذلك\nالرفوف التي تعرض ما لا تعرضه موقع «Steam»\n\nنفس العروض، مجمعة حسب المنصة التي تعرضها. وهذا عدد الأماكن التي توجد فيها نسخ منها مدرجة، وهو ما يختلف عن المكان الذي توجد فيه هذه الكتب، ولا يُفهم هنا على هذا النحو.\n\nالقيمة الدنيا للعروض التي تتجاوز الحد الأقصى، حسب السوق\nأقل سعر عرض × نسخ معروضة على ذلك الرف\nYouPin 898\n$22,720,252\nBUFF163\n$22,022,606\nC5Game\n$12,560,543\nCSFloat\n$10,871,845\nSkinport\n$1,385,060\n\nالولايات القضائية، بالترتيب المذكور أعلاه: YouPin 898 — الصين · BUFF163 — الصين · C5Game — الصين · CSFloat — الولايات المتحدة · Skinport — ألمانيا / مالطا. يمكن عرض المنتج المادي نفسه على أكثر من رف واحد من هذه الرفوف، لذا يجب عدم جمع هذه الأرقام مع إجمالي أي سوق آخر.\n\nالقيمة الدنيا حسب فئة السعر\nكيف يتم توزيع الأموال التي تتجاوز الحد الأقصى\n$1.8k-3k\n$9,842,391\n$3k-10k\n$36,787,269\n$10k-50k\n$20,038,749\nover $50k\n$2,891,897\n05 / الندرة التي يمكنك حسابها\nما مدى ضآلة العرض في الواقع\n\nتحتوي كل قطعة من منتجات CS2 على قيمة تقدر حسب درجة تآكلها، وتنشر المنصات عدد النسخ المتوفرة في كل فئة من هذه الدرجات. وهذا يحول كلمة «نادر» من صفة إلى رقم — وهذا الرقم هو الذي يفسر لماذا يستحق حساب واحد تم اختراقه عناء استخدام مجموعة أدوات تصيد مخصصة.\n\nAWP | أساطير التنين\n150 معروضة للبيع · ابتداءً من $11,350\n0.00–0.01\n29 · $14,730\n0.01–0.02\n54 · $11,618\n0.02–0.03\n26 · $11,350\n0.03–0.04\n25 · $11,618\n0.04–0.07\n16 · $11,585\n\nAWP | Dragon Lore (جديد من المصنع)\n\nM4A4 | هاول\n105 معروضة للبيع · ابتداءً من6,628 دولار\n0.00–0.01\n11 · $10,725\n0.01–0.02\n14 · $8,088\n0.02–0.03\n11 · $7,580\n0.03–0.04\n19 · $6,703\n0.04–0.07\n50 · $6,628\n\nM4A4 | Howl (جديد من المصنع)\n\nAK-47 | Wild Lotus\n113 معروضة للبيع · ابتداءً من $14,373\n0.00–0.01\n25 · $22,343\n0.01–0.02\n11 · $19,364\n0.02–0.03\n3 · $19,645\n0.03–0.04\n15 · $15,044\n0.04–0.07\n59 · $14,373\n\nAK-47| Wild Lotus (جديد من المصنع)\n\nAWP | غونغنير\n173 معروضة للبيع · ابتداءً من11,618 دولار\n0.00–0.01\n28 · $17,875\n0.01–0.02\n21 · $13,600\n0.02–0.03\n32 · $12,065\n0.03–0.04\n29 · $11,735\n0.04–0.07\n63 · $11,618\n\nAWP | غونغنير (جديد من المصنع)\n\nAK-47 | الثعبان الناري\n278 معروضة للبيع · ابتداءً من663 دولار\n0.15–0.18\n87 · $730\n0.18–0.21\n49 · $712\n0.21–0.24\n52 · $703\n0.24–0.27\n18 · $715\n0.27–0.38\n72 · $663\n\nAK-47 | الثعبان الناري (مُختبَر ميدانيًّا)\n\nمُصلب سطحياً (جميع المستويات / جوهرة زرقاء)\n76 معروضة للبيع · ابتداءً من $1,638\n0.07–0.08\n1 · $2,516\n0.08–0.09\n4 · $2,482\n0.09–0.10\n6 · $3,856\n0.10–0.11\n7 · $2,797\n0.11–0.15\n58 · $1,638\n\nAK-47 | معالج حرارياً (تآكل طفيف) | الفئة1\n\nتُعد «النطاقات» بمثابة «مجموعات الأسهم المتداولة» الخاصة بالأسواق؛ ولا يتم سحب سوى النطاقات التي تحتوي على عرض تداول واحد على الأقل. والسعر الموضح بجانب كل شريط هو أرخص سعر عرض بيع فوري في ذلك النطاق، لذا فإن العلاوة المرتبطة بكمية الأسهم المتداولة المنخفضة يمكن قراءتها مباشرةً بدلاً من أن تُذكر صراحةً.\n\n06 / الحركة، وفقًا لـ Steam\nما حققته رفوف المنتجات الخارجية فعليًّا\n\nValve لا تنشر أي سجل تاريخي قابل للاستخدام في هذا المستوى، ولا يدعي هذا الملف وجود أي سجل من هذا القبيل. لكن موقع Skinport ينشر مبيعاته المكتملة خلال الساعات الأخيرة 24، والأيام الأخيرة 7, 30 و90، وهذا هو كامل البعد الزمني المتاح هنا: متوسط السعر المحقق لكل نافذة زمنية، مقيَّسًا بحيث يكون متوسط اليوم 90-هو 100. لا تتضمن أي من الرسوم البيانية بيانات من موقع «Steam».\n\nمتوسط السعر المحقق، فترة متتابعة\nمؤشرًا على متوسط يوم «90-» · 6,758 العناصر التي تحتوي على 20+ المبيعات\n85\n91\n97\n103\n100\n90d\n94\n30d\n90\n7d\n88\n24h\nإجمالي المبيعات اليومية\nنفس العناصر، نفس النوافذ\n7,621\n9,653\n11,684\n13,716\n12,700\n90d\n11,894\n30d\n9,540\n7d\n8,637\n24h\n\nهذان رسمان بيانيان وليس رسمًا واحدًا بمقياسين عموديين: فالمؤشر والعدد اليومي لا يشتركان في أي وحدة قياس، ورسمهما على محور مشترك من شأنه أن يدفع إلى مقارنة غير صحيحة. النوافذ متداخلة ومتتابعة — حيث إن الرقم اليومي 90-يشمل الرقم الساعي 24-— لذا فإن هذه ليست سلسلة يومية ولا يجب قراءتها على أنها كذلك. ما يدعمه هذا الرسم البياني محدود وموضح بوضوح: خلال النوافذ المتتابعة Skinport التي تم نشرها، ظل متوسط السعر المحقق أقل من متوسطه الخاص 90-اليومي، وانخفض عدد المبيعات اليومي معه.\n\nSkinport المبيعات المحققة. النوافذ متداخلة ومتحركة؛ لذا فإن كل نقطة تمثل متوسط السعر المحقق خلال النافذة المتحركة، مقيسًا بمتوسط يوم 90-. وهي ليست سلسلة يومية ولا تتضمن أي بيانات من Steam.\n\n07 / ما هي المواد التي صُنع منها\nملصقات عمرها ستة عشر عامًا وحفنة من القفازات\n\nالمجموعة المذكورة أعلاه لا تمثل شريحة واسعة من السوق. فهي تقتصر على عدد قليل من القطع النادرة وبعض المجموعات، والتي لم يعد بالإمكان الحصول على العديد منها على الإطلاق — وهذا بالضبط هو السبب في أن العرض لا يستطيع مواكبة السعر.\n\nالفئات التي تتجاوز الحد الأقصى، مرتبة حسب الندرة\nعدد فئات العناصر\nCovert\n321\nClassified\n39\nRestricted\n24\nContraband\n12\nMil-Spec Grade\n9\nConsumer Grade\n9\nIndustrial Grade\n5\nالفئات التي تتجاوز الحد الأقصى، حسب المجموعة\nأفضل عشر مجموعات\nThe St. Marc Collection\n13\nThe Cobblestone Collection\n13\nThe Norse Collection\n12\nThe Arms Deal Collection\n9\nThe Canals Collection\n7\nThe Gods and Monsters Collection\n6\nThe Revolution Collection\n4\nThe 2021 Train Collection\n4\nThe Rising Sun Collection\n4\nThe Chop Shop Collection\n4\n\nحسب الفئة: skin 366, sticker 48, container 3, sticker_slab 2.\n\n08 / أعلى مبلغ دفعه أي شخص فعليًّا\nالارتفاعات مدعومة بصفقة، وليس بالإدراج في البورصة\n\nكل سعر آخر وارد في هذه الصفحة هو اسأل — ما يريده البائع. وهذه هي المبيعات: أعلى سعر تم تسجيله لصفقة مكتملة Skinport لكل منتج، خلال الأيام الـ90 الماضية. وهو الرقم الوحيد في هذا الملف الذي دفعه شخص ما فعليًّا، ويرتبط كل صف بالسوق الإلكتروني بحيث يمكن التحقق من الرقم من مصدره المباشر بدلاً من الاعتماد على ما نقدمه نحن.\n\n21,216المنتجات التي تمت عملية البيع لها في النافذة\n106تم بيعها بسعر يساوي أو يزيد عن الحد الأقصى للسعر المحدد في قائمة «Valve»\n$14,192أعلى قيمة لصفقة بيع واحدة تم إتمامها\n67/419الفئات التي تتجاوز الحد الأقصى والتي سجلت أي مبيعات\nأعلى ثلاثين صفقة بيع تمت خلال الفترة المذكورة\nالعنصر\tأعلى مبيعات\tمتوسط سعر البيع\tالمبيعات\tأرخص سعر متاح الآن\tSteam\tتحقق من ذلك\nAWP | Gungnir (Factory New)\t$14,192\t$11,343\t5\t$11,490\tabsent\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Factory New)\t$12,387\t$12,387\t1\t$13,836\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Factory New)\t$11,779\t$11,063\t16\t$10,941\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Minimal Wear)\t$11,693\t$11,693\t1\t$9,946\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Minimal Wear)\t$10,437\t$10,437\t1\t$9,610\tabsent\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Blue Laminate (Minimal Wear)\t$9,772\t$37\t76\t$30\t$40\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Minimal Wear)\t$9,463\t$9,463\t1\t$9,500\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Minimal Wear)\t$9,104\t$9,026\t6\t$8,524\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Hedge Maze (Minimal Wear)\t$8,139\t$8,139\t1\t$6,819\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Field-Tested)\t$7,617\t$7,390\t4\t$7,194\tabsent\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Field-Tested)\t$7,615\t$7,615\t1\t$7,100\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Field-Tested)\t$7,149\t$7,006\t2\t$7,165\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Field-Tested)\t$6,711\t$6,194\t15\t$5,988\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Factory New)\t$6,679\t$6,613\t3\t$6,628\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Superconductor (Factory New)\t$6,084\t$6,084\t1\t$7,969\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Battle-Scarred)\t$5,750\t$5,413\t3\t$5,899\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Pandora's Box (Minimal Wear)\t$5,520\t$5,508\t3\t$4,998\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Vice (Factory New)\t$5,385\t$5,158\t2\t$5,700\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Minimal Wear)\t$5,342\t$4,989\t19\t$4,997\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Hedge Maze (Field-Tested)\t$5,334\t$4,862\t5\t$3,724\tabsent\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Vulcan (Factory New)\t$5,275\t$1,418\t12\t$1,280\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Well-Worn)\t$4,978\t$4,978\t1\t$4,942\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Well-Worn)\t$4,931\t$4,931\t1\t$5,445\tabsent\tSkinport CSFloat Steam\nAK-47 | Hydroponic (Factory New)\t$4,802\t$4,351\t2\t$3,648\tabsent\tSkinport CSFloat Steam\n★ Talon Knife | Case Hardened (Minimal Wear)\t$4,588\t$466\t16\t$442\t$630\tSkinport CSFloat Steam\nAWP | Medusa (Factory New)\t$4,484\t$4,484\t1\t$4,171\tabsent\tSkinport CSFloat Steam\n★ Specialist Gloves | Pillow Punchers (Factory New)\t$4,359\t$4,359\t1\t$4,302\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Pandora's Box (Field-Tested)\t$4,359\t$3,666\t11\t$3,245\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Field-Tested)\t$4,289\t$4,225\t8\t$4,022\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Battle-Scarred)\t$4,124\t$4,124\t1\t$4,279\tabsent\tSkinport CSFloat Steam\nنفس المنتج، نفس أيام العرض «90»، وسعر مختلف تمامًا\n\nيقتصر ذلك على المنتجات التي يبلغ متوسط سعرها100 دولارًا أمريكيًّا، والتي تمت خمس عمليات بيع كاملة على الأقل، لأن عملية بيع واحدة غير عادية لـ«سكين» رخيصة قد تشوه النسبة. أما ما يتبقى، فيهيمن عليه مُصلب سطحياً عمليات الإغلاق، حيث يحدد النمط السعر، ويقوم السوق بتصنيف كل نمط تحت اسم واحد — وهي نفس الآلية التي يتم قياسها بواسطة «float» في القسم 05.\n\nالعنصر\tالערך الأعلى مقابل الوسيط\tأعلى مبيعات\tمتوسط سعر البيع\tالمبيعات\tتحقق من ذلك\n★ Talon Knife | Case Hardened (Minimal Wear)\t+884%\t$4,588\t$466\t16\tSkinport CSFloat Steam\nDesert Eagle | Cobalt Disruption (Factory New)\t+859%\t$1,210\t$126\t115\tSkinport CSFloat Steam\nAWP | BOOM (Minimal Wear)\t+814%\t$1,232\t$135\t89\tSkinport CSFloat Steam\nAK-47 | Case Hardened (Well-Worn)\t+769%\t$1,720\t$198\t70\tSkinport CSFloat Steam\nAWP | Graphite (Factory New)\t+761%\t$1,469\t$171\t124\tSkinport CSFloat Steam\n★ Talon Knife | Case Hardened (Field-Tested)\t+509%\t$2,437\t$400\t48\tSkinport CSFloat Steam\n★ Kukri Knife | Case Hardened (Minimal Wear)\t+448%\t$723\t$132\t69\tSkinport CSFloat Steam\n★ Kukri Knife | Case Hardened (Field-Tested)\t+415%\t$549\t$106\t128\tSkinport CSFloat Steam\n★ Ursus Knife | Case Hardened (Minimal Wear)\t+371%\t$597\t$127\t12\tSkinport CSFloat Steam\nAK-47 | Case Hardened (Field-Tested)\t+369%\t$1,037\t$221\t125\tSkinport CSFloat Steam\nAK-47 | Red Laminate (Minimal Wear)\t+360%\t$552\t$120\t18\tSkinport CSFloat Steam\nAWP | Asiimov (Field-Tested)\t+351%\t$528\t$117\t439\tSkinport CSFloat Steam\nAK-47 | Vulcan (Field-Tested)\t+337%\t$865\t$198\t241\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Nightwish (Factory New)\t+322%\t$625\t$148\t31\tSkinport CSFloat Steam\nAWP | Lightning Strike (Factory New)\t+319%\t$2,065\t$493\t198\tSkinport CSFloat Steam\nStatTrak™ AWP | Redline (Minimal Wear)\t+312%\t$574\t$139\t24\tSkinport CSFloat Steam\nStatTrak™ AWP | Asiimov (Battle-Scarred)\t+287%\t$524\t$135\t37\tSkinport CSFloat Steam\nAK-47 | Redline (Minimal Wear)\t+277%\t$562\t$149\t112\tSkinport CSFloat Steam\nAWP | Crakow! (Factory New)\t+275%\t$379\t$101\t72\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Vulcan (Factory New)\t+272%\t$5,275\t$1,418\t12\tSkinport CSFloat Steam\n\nهذا هو أعلى سعر سُجل خلال يوم واحد على موقع «90-»، وليس أعلى سعر على الإطلاق، وهو يقتصر على سوق واحد فقط. ولم يُذكر أي رقم قياسي على الإطلاق في أي مكان من هذا الملف. أي عنصر لا تظهر له مبيعات على موقع «Skinport» في النافذة يُستبعد تمامًا من هذا العرض، ولهذا السبب فإن المجموعة أصغر من الإحصاء الشامل.\n\nيتم إنشاء روابط التحقق استنادًا إلى معرّفات المنصة الخاصة بالكتالوج. وهي تشير إلى صفحة المنتج في كل سوق إلكتروني، بحيث يمكن للقارئ التحقق من الصورة من المصدر مباشرةً، وليس من خلالنا. أما الروابط الخارجية فتحمل rel=\"nofollow\": إنها مجرد إشارات، وليست توصيات، كما أن العديد من الوجهات هي منصات تجارية ينتقدها هذا التحقيق.\n\n09 / المصدر والحدود\nمن أين جاء هذا وما الذي لا يمكنه إظهاره\n\nتم إعادة حساب كل رقم وارد في هذه الصفحة استنادًا إلى ملفين من لقطات البيانات، وقد نُشرت قيم التجزئة الخاصة بهما بجانبهما. ولا يوجد هنا أي نص منقول من مقال منشور على موقع آخر.\n\nالمصدر والوصول\n\ncs2.sh API، GET /v1/prices/latest و GET /v1/schema، لقطة واحدة تم التقاطها في 2026-09-23T00:44:27.871388581Z، بالأسعار بالدولار الأمريكي.\n\nتم الحصول على البيانات في إطار اشتراك تجاري مدفوع تابع لموقع «GDPR» (المُقدَّم من قبل مقدم الطلب المُوثَّق في الأرشيف)، وفقًا لشروط المزود الخاصة. لم يتم استخراج بيانات من أي منصة تجارية، ولم يتم استخدام أي بيانات اعتماد خاصة بأي منصة تجارية. يُحتفظ بمفتاح الطالب خارج هذا المستودع ولا يظهر في أي ملف هنا.\n\nكيف يكون المنتج مؤهلاً\n\nيتم وضع كل عنصر أساسي يحتوي على عرض بيع نشط واحد على الأقل على BUFF أو CSFloat أو Skinport أو YouPin أو C5Game ضمن نطاق سعري وفقًا لأرخص عرض بيع له، وبالتالي لا يعتمد النطاق أبدًا على Steam. «تغطيةSteam» هي نسبة العناصر الموجودة في ذلك النطاق والتي تحمل أي عرض بيع نشط Steam في لحظة التسجيل. يتم استبعاد متغيرات الأنماط والمراحل من السلم لأن Steam لا تدرجها بشكل منفصل؛ وإدراجها من شأنه أن يقلل من قيمة Steam. أما «الصور المعروضة» فهي صور الكتالوج الخاصة بنفس العناصر، والمخزنة محليًّا.\n\nالصور التوضيحية وحقوق الصور. الصور التوضيحية لعناصر الكتالوج هي صور مقدمة من المزود، تُعرض لنفس «market_hash_name» الذي تظهر به صفوف الأسعار، ويتم تخزينها محليًّا للعرض في وضع عدم الاتصال وعبر IPFS. لا تعتبر هذه الصور من إنتاج موقع PhishDestroy: فجميع صور العناصر والشعارات ولقطات الشاشة تظل ملكًا لأصحابها المعنيين (cs2.sh، CSFloat، Skinport، BUFF، YouPin، C5Game، Valve وغيرها). ويتم إعادة إنتاجها حصريًّا لأغراض التعريف والإبلاغ عن المصلحة العامة؛ ولا يُدعى إلى أي ملكية أو ترخيص.\n\nWhat this means — market_hash_name\n\nThe exact identifier Steam’s own API uses for an item — wear, finish and all. Third-party marketplaces list against the same string, which is what makes their catalogues directly comparable with Steam’s and ties every outside listing back to a record inside Valve’s database.\n\nما لم نتمكن من الحصول عليه\n\nتقتصر فئة الاشتراك المستخدمة على اللقطات الحالية فقط. ولم تكن نقاط النهاية التاريخية والمحفوظة متاحة، و لا توجد أي سلسلة بيانات تاريخية مذكورة في أي مكان في هذه الصفحة بالإضافة إلى مبيعات «النافذة المتتابعة» Skinport، يتم نشر هذا المقال في القسم 06.\n\nلقطة واحدة، وليست سلسلة زمنية. عدم وجود عرض على موقع Steam في لحظة التقاط الصورة لا يُعد دليلاً على أن هذا العنصر لن يظهر هناك أبداً؛ بل هو الحالة المسجلة للرف في تلك اللحظة، وبالنسبة للأسعار التي تتجاوز الحد الأقصى، فإنه يمثل أيضاً ما تنص عليه القاعدة المنشورة من قبل Valve: يحدد سوق المجتمع في Valve صراحةً سقفاً للعروض عند $1,800 لكل عنصر (مع حد أقصى لرصيد محفظة Steam يبلغ $2,000؛ انظر Steam الأسئلة الشائعة حول سوق المجتمع محفوظ على 2026-09-21 ↗ و Steam اتفاقية المشترك، المادة 3.C محفوظ على 2026-09-24 ↗).\n\nالتصنيف\n\nسعر السلعة هو دائمًا أرخص سعر عرض فوري لها، لذا لا يمكن لأي قيمة شاذة مرتفعة أن تضخم الإجمالي أبدًا. ويحدد نظام التصنيف الصفوف التي يمكن عرض أسعارها. أي عرض يزيد عن ثلاثة أضعاف أرخص سعر عرض فوري لنفس السلعة يُستبعد باعتباره سعرًا غير فوري. الدرجة أ: لا تزال ثلاث أسواق أو أكثر تعرض أسعارًا أعلى من الحد الأقصى، ويقع متوسط أسعارها ضمن نطاق 25 في المائة من أرخص سعر. الدرجة ب: تتفق سوقان، أو تتفق ثلاث أسواق بفارق أقل. الدرجة ج: سعر واحد فقط — وهو سعر عرض، وليس سعر سوقي. ولا يتم ذكر سوى الدرجتين أ وب في أي مكان في هذا التقرير.\n\nقاعدة القيم المتطرفة: السعر المعروض > 3.0× أرخص سعر عرض بيع لنفس السلعة.\n\nلماذا تُعتبر الإجماليات الحد الأدنى؟\n\nبالنسبة لكل سوق، فإن المنتج الأدنى يُضرب سعر العرض في عدد النسخ المدرجة في قائمة الرف. وكل نسخة أخرى موجودة هناك يُحدد سعرها عند أو أعلى من أدنى سعر عرض، لذا فإن القيمة المعلنة الحقيقية أعلى بحكم طبيعة النظام، وليس بناءً على تقدير. وهذا لا يُعد عملية بيع، ولا تدفقًا نقديًا، ولا تقييمًا لاقتصاد CS2.\n\nتحقق من ذلك بنفسك\n\nيتم نشر مجموعات البيانات المستمدة التي تستند إليها كل رسم بياني في هذه الصفحة بالكامل: مجموعة بيانات أطلس, شاشة الفرز والتخلص من الشوائب, التعداد السكاني الأساسي و قائمة البيانات التي تحتوي على قيمة SHA-256 لكل لقطة أولية.\n\nتصحيح تم تسجيله في جلسة التداول\n\nكانت مسودة سابقة للسجل المصاحب قد استهلت بذكر نسخة تذكارية من AK-47 | Point Disarray معروضة بسعر $148,954 على إحدى منصات التسوق الصينية، بينما حددت منصة Steam سعرها بـ $119. هذا الصف من الدرجة C: رف واحد، ونسخة واحدة، ولا توجد منصة تسوق أخرى تتفق على السعر. إنه سعر مطلوب، وليس سعرًا فعليًّا، وقد تم تخفيض تصنيفه هنا وعلى تلك الصفحة. السعر المؤكد هو Sticker | Titan (Holo) | Katowice 2014 بسعر $66,285، وفقًا لما ورد في 4، توجد هذه الأسواق ضمن نطاق 5.2%، ولا توجد على الإطلاق في Steam.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "أطلس سلم أسعار «سكين» — «منحدر السيولة»"
          },
          {
            "level": 2,
            "id": null,
            "text": "يُطبق هذا الشرط تلقائيًا، وليس بناءً على طلب"
          },
          {
            "level": 3,
            "id": null,
            "text": "ما تستبعده هذه الشكلية"
          },
          {
            "level": 2,
            "id": null,
            "text": "السعر المطلوب ليس سعرًا"
          },
          {
            "level": 3,
            "id": null,
            "text": "A  ثلاثة أرفف أو أكثر متطابقة"
          },
          {
            "level": 3,
            "id": null,
            "text": "B  هناك توافق بين الرفين"
          },
          {
            "level": 3,
            "id": null,
            "text": "C  رف واحد — غير مستخدم"
          },
          {
            "level": 3,
            "id": null,
            "text": "ما هي تكلفة هذا التصحيح، وما الذي حققه؟"
          },
          {
            "level": 3,
            "id": null,
            "text": "القطع المعروضة التي تم تصنيفها كأثر ثقافي"
          },
          {
            "level": 2,
            "id": null,
            "text": "جميع فئات موقع «419»، مع تحديد العنصر الذي يشير إليه كل سعر"
          },
          {
            "level": 2,
            "id": null,
            "text": "الرفوف التي تعرض ما لا تعرضه موقع «Steam»"
          },
          {
            "level": 2,
            "id": null,
            "text": "ما مدى ضآلة العرض في الواقع"
          },
          {
            "level": 2,
            "id": null,
            "text": "ما حققته رفوف المنتجات الخارجية فعليًّا"
          },
          {
            "level": 2,
            "id": null,
            "text": "ملصقات عمرها ستة عشر عامًا وحفنة من القفازات"
          },
          {
            "level": 2,
            "id": null,
            "text": "الارتفاعات مدعومة بصفقة، وليس بالإدراج في البورصة"
          },
          {
            "level": 3,
            "id": null,
            "text": "أعلى ثلاثين صفقة بيع تمت خلال الفترة المذكورة"
          },
          {
            "level": 3,
            "id": null,
            "text": "نفس المنتج، نفس أيام العرض «90»، وسعر مختلف تمامًا"
          },
          {
            "level": 2,
            "id": null,
            "text": "من أين جاء هذا وما الذي لا يمكنه إظهاره"
          },
          {
            "level": 3,
            "id": null,
            "text": "المصدر والوصول"
          },
          {
            "level": 3,
            "id": null,
            "text": "كيف يكون المنتج مؤهلاً"
          },
          {
            "level": 3,
            "id": null,
            "text": "ما لم نتمكن من الحصول عليه"
          },
          {
            "level": 3,
            "id": null,
            "text": "التصنيف"
          },
          {
            "level": 3,
            "id": null,
            "text": "لماذا تُعتبر الإجماليات الحد الأدنى؟"
          },
          {
            "level": 3,
            "id": null,
            "text": "تحقق من ذلك بنفسك"
          },
          {
            "level": 3,
            "id": null,
            "text": "تصحيح تم تسجيله في جلسة التداول"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/ar/#market-gap-section",
          "https://phishdestroy.io/steam_dossier/ar/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/ar/skin_atlas#gallery",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://skinport.com/market?search=AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260924114457/https://store.steampowered.com/subscriber_agreement/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-atlas.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-artefact-screen.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-above-the-ceiling.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ar/skin_atlas.content.json",
      "export_json_sha256": "f4bba1ac5bcc6ec3050b04bd2375215c36c956318fe10a5df05dad140ea94876"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ar/social_graph.html",
      "language": "ar",
      "title": "تتبع الروابط المسجلة — ملف «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/ar/social_graph",
      "source_html_sha256": "e0ddb38e7e47031d1aae1988f12f177abedbd85c0a86a975d4dd192a2ef24982",
      "exported_at": "2026-09-29T00:20:22.067Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "social_graph.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ar/social_graph.pdf?v=print-20260929-v5",
        "sha256": "0628274aac61c16381941d33c95a2d25dcb487d9e274ef42f304dbb90ef29582",
        "bytes": 139148,
        "pages": 6
      },
      "integrity": {
        "signed_object": "social_graph.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "social_graph.content.json.asc",
        "digest_file": "social_graph.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify social_graph.content.json.asc social_graph.content.json",
          "sha256sum -c social_graph.content.json.sha256"
        ]
      },
      "content": {
        "text": "اتبع المسارات.افحص كل علاقة.\n\nابحث عن ملف تعريفي. اختر نوع العلاقة. تابع الجيران المباشرين له في السجلات التي تم تسجيلها. أداة البحث: تمثل الحواف العلاقات العامة، ولا تُعد دليلاً على وجود اتصال مباشر أو تنسيق خاص أو سلوك غير لائق بين أي عقدتين. يُفضل قراءة تخطيط العقد في نموذج «3,435-» باستخدام عوامل التصفية.\n\nاستكشف علاقة واحدة في كل مرة\n\n💡 انقر على العقد واسحبها لإعادة تنظيم الرسم البياني. مرر المؤشر فوقها لعرض الملفات الشخصية التفصيلية. الخطوط المتصلة باللون الأزرق المخضر = الصداقات، والخطوط المتقطعة باللون الكهرماني = التعليقات المتبادلة.\n\nنوع العلاقةالملف الشخصي والجيران المباشرون\n\n3,435 الملفات الشخصية · روابط مسجلة على موقع 4,551\n\nابحث عن ملف تعريف واختره، أو انقر على عقدة. لن يتبقى سوى جيرانها المباشرين المسجلين. فالحافة تسجل علاقةً ما؛ وهي لا تنشئ تنسيقًا خاصًّا.\n\nالملفات الشخصية في مجموعة البيانات التي تم الحصول عليها\n\nجدول المصدر الكامل: تنزيل جميع صفوف ملف «3,435» (بصيغة CSV). يعرض الجدول أدناه في البداية أول 25 صفًا؛ ويمكن الاطلاع على مجموعة البيانات الكاملة من خلال البحث وتقسيم الصفحات.\n\n1–25 / 3,435 صفوف\nاسم الشخصية\tSteamID64\tالخصوصية\tالحالة\tعضويات المجموعات\tالمخزون المجمد (بالدولار الأمريكي)\tالموقع\nMahatma Gandhi\t76561198333721623\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tPH\nGalley//갤리🌠🌙\t76561198043416832\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tKP\n$Schlächter\t76561198860277343\tPUBLIC\tClean\tsteambans\t$0.00\tUnknown\n❄r3dsn0w000™❄ [Cristi]🎮\t76561197986767957\tPUBLIC\tClean\tCommunityLegends\t$0.00\tRO\n(2a03) Wolfy\t76561197991671851\tPUBLIC\tCommunity\tsr_public\t$0.00\tUS\nZloy2288\t76561198038578334\tPUBLIC\tClean\tsteambans\t$0.00\tBY\njessy\t76561198039125237\tPUBLIC\tCommunity, VAC (1x)\tCommunityLegends\t$0.00\tJP\nJithraRufure\t76561198071896910\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\n| Níllerdínho |\t76561198003487438\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tDK\nJones is back\t76561198023013026\tPRIVATE\tVAC (1x)\tsteambans\t$0.00\tUnknown\nUNEX | ★✠☠ MoH3st ☠✠\t76561198050763123\tPUBLIC\tClean\tsteambans\t$0.00\tDE\nTrojan\t76561198048457084\tPUBLIC\tClean\tCommunityLegends\t$0.00\tDE\n𝗠𝗮𝘆𝘂 ❤\t76561199377967696\tPUBLIC\tClean\tsr_public\t$0.00\tIS\nbig fucking idiot\t76561198871206397\tPUBLIC\tVAC (1x)\tsteambans\t$0.00\tUnknown\nSOFF Games\t76561198227129276\tPUBLIC\tClean\tcommunitymoderators\t$0.00\tRU\nThijminecraft02\t76561198253895669\tPUBLIC\tClean\tSteamIDcouk SArchive\t$0.00\tNL\nStatic-sama\t76561198289329793\tPUBLIC\tClean\tsteambans\t$0.00\tJP\n𝙸mmortal 𝚂targazer\t76561198142116760\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\nCommander Keen\t76561197987773287\tPUBLIC\tClean\tsteambans\t$0.00\tBE\nS1mX\t76561199648509165\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\nmixwell\t76561199276547472\tPUBLIC\tClean\tsr_public\t$0.00\tJP\nP90_GOD_YyEs™\t76561198285821942\tPUBLIC\tClean\tsteambans\t$0.00\tHK\nhewwo?\t76561199133807546\tPUBLIC\tVAC (1x)\tsteambans\t$0.00\tCH\n♕Kamikaze Atze♕\t76561198002700103\tPUBLIC\tClean\tsteambans\t$0.00\tDE\nPastica\t76561198154655970\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tDZ\nروابط الصداقة المسجلة\n\nجدول المصدر الكامل: تنزيل جميع صفوف ملف «4,299» (بصيغة CSV). يعرض الجدول أدناه في البداية أول 25 صفًا؛ ويمكن الاطلاع على مجموعة البيانات الكاملة من خلال البحث وتقسيم الصفحات.\n\n1–25 / 4,299 صفوف\nالمستخدم أ\tالاتجاه\tالمستخدم ب\tنوع العلاقة\nMahatma Gandhi\n76561198333721623\t↔\tDeskjet\n76561198272738437\tMutual Friends\nGalley//갤리🌠🌙\n76561198043416832\t↔\tomega\n76561197960274529\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tFisty\n76561198057301486\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tFaalagorn\n76561198001116101\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tMURK\n76561198036995672\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tÅρøᴛʜℯᴛȋᴄÅʟȋℯη ♛👽♛\n76561197984615267\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tsilatrak\n76561197999629462\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tBlack Blade\n76561198083368493\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tAvenger\n76561197978249317\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tRemtar\n76561198124322650\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tCato\n76561197961345984\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t✪ G λ M Ξ ®\n76561197994308495\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tclees42\n76561198030936806\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t𝓜ε𝔰𝔥 | AusLevels\n76561198108828539\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tSgtFopper™\n76561198002555892\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t❥Miss Bee\n76561198046958996\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tTesTy\n76561198032370068\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tskl_andrey\n76561198136881436\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t\"Exekutor\"\n76561198009583947\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tAraripe\n76561198103754372\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tsteve6678\n76561198053200093\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\ttrinner\n76561197970359081\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tSteph S.\n76561198025653291\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tKirito\n76561198154545657\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tDoc. todt\n76561197984492467\tMutual Friends\nروابط التعليقات المسجلة\n\nجدول المصدر الكامل: تنزيل جميع صفوف ملف «252» (بصيغة CSV). يعرض الجدول أدناه في البداية أول 25 صفًا؛ ويمكن الاطلاع على مجموعة البيانات الكاملة من خلال البحث وتقسيم الصفحات.\n\n1–25 / 252 صفوف\nالمؤلف\tالاتجاه\tالملف الشخصي المستهدف\tالتاريخ\tنص التعليق\nDeskjet\n76561198272738437\t→\tMahatma Gandhi\n76561198333721623\t16 September, 2021 @ 11:02:05 pm PDT\t\"𝑵𝒐𝒘 𝒊𝒇 𝑰 𝒇𝒖𝒄𝒌 𝒕𝒉𝒊𝒔 𝒎𝒐𝒅𝒆𝒍𝑨𝒏𝒅 𝒔𝒉𝒆 𝒋𝒖𝒔𝒕 𝒃𝒍𝒆𝒂𝒄𝒉𝒆𝒅 𝒉𝒆𝒓 𝒂𝒔𝒔𝒉𝒐𝒍𝒆𝑨𝒏𝒅 𝑰 𝒈𝒆𝒕 𝒃𝒍𝒆𝒂𝒄𝒉 𝒐𝒏 𝒎𝒚 𝑻-𝒔𝒉𝒊𝒓𝒕𝑰'𝒎𝒎𝒂 𝒇𝒆𝒆𝒍 𝒍𝒊𝒌𝒆 𝒂𝒏 𝒂𝒔𝒔𝒉𝒐𝒍𝒆\" - Nelson Mandela\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t22 November, 2021 @ 4:10:28 pm PDT\thttps://anige.horigiri.net/?cat=22\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t18 November, 2021 @ 12:45:26 am PDT\thttps://gamerch.com/umamusume/entry/250411\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t8 August, 2021 @ 4:13:25 am PDT\thttps://modoocode.com/304\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t6 February, 2021 @ 3:35:05 pm PDT\t▤ ∫︹- -ω⁾ ⁽︹▓▓︺\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t11 December, 2019 @ 1:50:53 am PDT\thttps://blog.naver.com/aksenwlddj12/221369410039\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t2 October, 2019 @ 7:11:59 am PDT\tǤαllєу║︎갤리..۩\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t9 April, 2019 @ 12:51:28 pm PDT\tExplosiveDamage(owner, from, maxrange, minrange, distmultiplier, dmgmultiplier, mindamage, typ, damagetype, ignore)\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 12:22:47 pm PDT\tinfo - sh_titles.lua\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 12:21:46 pm PDT\tlocal nibbas = 1344 init.lua\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 11:31:58 am PDT\thttp://foreign.aladin.co.kr/shop/wproduct.aspx?ItemId=123955531&start=slayer\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t3 April, 2019 @ 1:26:41 am PDT\tǤαllєу\nLei\n76561198982197954\t→\tJithraRufure\n76561198071896910\t29 December, 2024 @ 12:58:08 pm PDT\t+rep he knows how 2 rush B ￣ヘ￣\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t2 September, 2026 @ 5:16:55 am PDT\tlol\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t20 August, 2026 @ 6:11:03 am PDT\t?\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t25 July, 2026 @ 7:20:05 am PDT\thahahahaha\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t30 June, 2026 @ 12:52:42 pm PDT\twow\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t30 June, 2026 @ 12:41:32 pm PDT\txD\nvalorant enjoyer\n76561199112142402\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:26:30 pm PDT\toh no!!\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:26:11 pm PDT\toh no!!\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:22:22 pm PDT\tomg !!! they know my secret, omg!!!\nvalorant enjoyer\n76561199112142402\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:21:39 pm PDT\t+rep good ♥♥♥♥♥ player\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:20:50 pm PDT\tomg! u cant cheat on secure gaben servers, omg dont report me, they ban me for boosted omg\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 8:37:11 pm PDT\txD\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t28 June, 2026 @ 1:58:14 pm PDT\twow",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "اتبع المسارات.افحص كل علاقة."
          },
          {
            "level": 2,
            "id": null,
            "text": "استكشف علاقة واحدة في كل مرة"
          },
          {
            "level": 2,
            "id": null,
            "text": "الملفات الشخصية في مجموعة البيانات التي تم الحصول عليها"
          },
          {
            "level": 2,
            "id": null,
            "text": "روابط الصداقة المسجلة"
          },
          {
            "level": 2,
            "id": null,
            "text": "روابط التعليقات المسجلة"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-profiles.csv",
          "https://steamcommunity.com/profiles/76561198333721623",
          "https://steamcommunity.com/profiles/76561198043416832",
          "https://steamcommunity.com/profiles/76561198860277343",
          "https://steamcommunity.com/profiles/76561197986767957",
          "https://steamcommunity.com/profiles/76561197991671851",
          "https://steamcommunity.com/profiles/76561198038578334",
          "https://steamcommunity.com/profiles/76561198039125237",
          "https://steamcommunity.com/profiles/76561198071896910",
          "https://steamcommunity.com/profiles/76561198003487438",
          "https://steamcommunity.com/profiles/76561198023013026",
          "https://steamcommunity.com/profiles/76561198050763123",
          "https://steamcommunity.com/profiles/76561198048457084",
          "https://steamcommunity.com/profiles/76561199377967696",
          "https://steamcommunity.com/profiles/76561198871206397",
          "https://steamcommunity.com/profiles/76561198227129276",
          "https://steamcommunity.com/profiles/76561198253895669",
          "https://steamcommunity.com/profiles/76561198289329793",
          "https://steamcommunity.com/profiles/76561198142116760",
          "https://steamcommunity.com/profiles/76561197987773287",
          "https://steamcommunity.com/profiles/76561199648509165",
          "https://steamcommunity.com/profiles/76561199276547472",
          "https://steamcommunity.com/profiles/76561198285821942",
          "https://steamcommunity.com/profiles/76561199133807546",
          "https://steamcommunity.com/profiles/76561198002700103",
          "https://steamcommunity.com/profiles/76561198154655970",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-connections.csv",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-comments.csv"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ar/social_graph.content.json",
      "export_json_sha256": "98e0cb8fc62d9b2c7062f35c881658b13eba1ff6929d8f16ea696094856696fe"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ar/steam_enforcement_evidence.html",
      "language": "ar",
      "title": "القواعد مقابل الاستجابات — ملف «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/ar/steam_enforcement_evidence",
      "source_html_sha256": "8c27b767dfffade09cff845127c990f18a5b36a3c65b75b00e9cc0003aa494ce",
      "exported_at": "2026-09-29T00:20:26.570Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "steam_enforcement_evidence.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ar/steam_enforcement_evidence.pdf?v=print-20260929-v5",
        "sha256": "9ac2f3d728534fa9540711bf17574fd18e989bcf5469af9276d3c440c7e08172",
        "bytes": 408044,
        "pages": 36
      },
      "integrity": {
        "signed_object": "steam_enforcement_evidence.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "steam_enforcement_evidence.content.json.asc",
        "digest_file": "steam_enforcement_evidence.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify steam_enforcement_evidence.content.json.asc steam_enforcement_evidence.content.json",
          "sha256sum -c steam_enforcement_evidence.content.json.sha256"
        ]
      },
      "content": {
        "text": "ملحق الأدلة / السجلات المرتبطة بالمصادر\nSteam أدلة التنفيذ — سجلات الدعم وشبكة المطورين\n\nالقاعدة. الرد.\n\nما يثبته هذا القسم\n\nتقارن غرفة الأدلة هذه اتفاقية الاشتراك الرسمية الخاصة بـ «Valve» مع سجلات الإنفاذ المؤرخة، وقرارات تسوية النزاعات المتعلقة بالدعم، وسجلات شبكة المطورين عبر مستودعات 252 وملفات تعريف 3,320. وتُظهر أن أصحاب الحسابات العاديين يواجهون إجراءات إنفاذ لا يمكن دحضها وإغلاقًا لخدمات الدعم عقب اختراق جلساتهم، في حين تستمر عمليات الروبوتات التجارية ذات الحجم الكبير في العمل بشكل مستمر مع إمكانية الوصول إلى البنية التحتية العامة.\n\n← العودة إلى ملخص الإدارة التنفيذية\n\nاقرأ الشرط المكتوب. افتح الرد المسجل. قارن بين ما يظهر في المصدر وما لم يتم الرد عليه.\n\nالدعم والطعون ↓البنية التحتية العامة ↓\n252سجلات المستودع\n3,320الملفات الشخصية العامة\n4,214أزواج مميزة من الملفات الشخصية والمستودعات\n98,902أزواج الملفات الشخصية ذات المستودعات المشتركة\n01 / الدعم، والعقوبات، وإعادة الإعمار\nاقرأ الشكوى.يرجى إرفاق النص الأصلي.\nمعرض حالات رفض الدعم (معروضات 981) ↗تنزيل السجلات المحددة ↓\nHFB / قضية الاستعانة بمصادر خارجيةالحل التوفيقي المعترف به.\nحالات الفصل المُبلغ عنها.\n\nيرجى الاطلاع على نص رد فريق الدعم المُدرج أدناه ومصدر الادعاء المتعلق بموظفي المقاول.\n\nافتح الملف ومصادره →\n\nفيما يلي: خمسة محفوظة منشورات Reddit العامة من مجموعة سجلات الدعم المرفقة. يوثق كل سجل تفاعلًا تم الإبلاغ عنه مع نظام الدعم الخاص بـ Valve — مع الاحتفاظ بالرابط الأصلي للمصدر وموقع التقاط الصورة والنص الكامل. هذه هي روايات الضحايا. أما سجلات الدعم الموثقة التي من شأنها تأكيد هذه الروايات أو دحضها، فهي محفوظة لدى Valve ولم يتم الكشف عنها.\n\n01\nBan & review2024-12-09\nPermanent sanction & closed appeals\n\nThe author reports a permanent account ban, repeated ticket closures and a planned GDPR access request.\n\nREDDIT / PUBLIC TESTIMONYr/ohnePixelCapture record 294\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 303 words\nPermanently banned Steam account without a clear explanation, need help!\n\nsteam_support_tickets_MEGA.json / record 294\n\nHey everyone,\n\nI’m in a really frustrating situation, and I’m hoping someone here can help me or offer advice. My Steam account was just permanently banned for allegedly violating the Steam Subscriber Agreement, and I have no idea why.\n\n# What Steam Support told me:\n\nThe support message said my account was banned due to:\n\n* Suspicious activities related to transferring or attempting to sell/trade the account.\n* Community reports and other unspecified factors.\n\nThey added that the ban is permanent and that they can't help me further. They also warned that future support requests regarding this ban might be ignored. 😞\n\n# Why I’m contesting this ban:\n\n* I have never sold, traded, or transferred my account. I’ve been the legitimate owner since the beginning.\n* On the day the ban occurred, I did nothing noteworthy that could have triggered such a sanction.\n* I received no prior warning, which feels incredibly unfair.\n\n# What I’ve tried so far:\n\n* Contacting Steam Support: I explained my situation and asked for more details, but they’re sticking to their decision and closing my tickets.\n* I’m preparing a request based on my Right of Access (GDPR) to get all the data related to my account.\n\n# Questions for the community:\n\n1. Has anyone successfully had a permanent ban lifted on Steam?\n2. Are there steps I can take to prove I’m the legitimate owner of the account?\n3. Any advice on how to word my request to convince support to reconsider my case?\n4. Would it be helpful to contact the CNIL (I’m based in France) to force Steam to provide more information?\n\nI’m really desperate at the thought of losing all my games, purchases, and years of playtime. Thanks in advance for any help and advice you can give!\n\nhttps://preview.redd.it/jk9qv0gmhv5e1.png?width=1289&amp;format=png&amp;auto=webp&amp;s=b3a333ebb08ea133e2c8747ba126f5a68283d9f7\n\nhttps://preview.redd.it/4sopt0gmhv5e1.png?width=1022&amp;format=png&amp;auto=webp&amp;s=56195d5336118faf9413f1514ead7e8d24c788c3\n\nhttps://preview.redd.it/eqrxw0gmhv5e1.png?width=996&amp;format=png&amp;auto=webp&amp;s=ff3539d28ab754e513ad471822c5de652920101d\n\nhttps://preview.redd.it/728xz0gmhv5e1.png?width=1034&amp;format=png&amp;auto=webp&amp;s=bc5335673509929669af785aa244bf8d2dc58da8\n\n02\nSupport access2025-05-09\nAccount recovery & a reported $10,000 loss\n\nThe author alleges that support reset credentials and removed account protection following another person’s recovery ticket.\n\nREDDIT / PUBLIC TESTIMONYr/legaladviceCapture record 110\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 193 words\nGot $10k stollen from steam inventory due to steam' support fault.\n\nsteam_support_tickets_MEGA.json / record 110\n\nLocation: Quebec, Canada.\n\nLast year, someone hacked my Steam account and stole items worth about $10,000 USD. I only noticed this last week. When I talked to Steam Support, they admitted that someone submitted a ticket to make changes on the account and Steam Support reset my password and turned off all my account security.\n\nI asked Steam Support about getting my items back, but they said there was nothing they could do. They told me I should follow their security recommendations.\n\nThe problem is, I did everything they \"suggested\" to protect an account:\n\n* I had two-factor authentication.\n* My phone number was connected to my account.\n* I used Steam Guard.\n* I printed recovery codes and kept them in a safe.\n\nEven though I did all these things, Steam Support still gave someone else access to my account. The stolen items had been in my account since around 2016-2017. Also, I had not logged in for a few years, so I didn’t accidentally give my information to a fake website.\n\nIs there anything I can do, or do I just have to accept losing $10,000 USD?\n\nThanks for your help.\n03\nRestoration2022-07-07\nA reported $500+ loss & template replies\n\nThe author describes an account compromise, disputed transactions and a support response that allegedly did not address the submitted evidence.\n\nREDDIT / PUBLIC TESTIMONYr/DotA2Capture record 45\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 410 words\nFunds stolen through steam market. Disappointed with Steam response.(or lackthereof)\n\nsteam_support_tickets_MEGA.json / record 45\n\nOn 6th July 2022, 44 unauthorized transactions were made on the steam market using my steam wallet funds totalling roughly $500+ USD to buy worthless 1 cent Dota 2 items. This happened during the wee hours in the morning and i contacted them first thing when i woke up. \n\nI have 2FA enabled all the time, and always thought this would not happen to me as I do not go on betting sites/click sketchy links. My account password + emails were not changed, nor did they take my inventory, just that my funds were used illicitly. Also when I went to disable other APIs, it says there are no other APIs to disable. Shows that it wasn't through me clicking sketchy links and leaving my account details there. Would have lost the whole account if i did so.\n\nWhat baffles me is how did they bypass my 2FA to login my account? Why doesn't steam market purchases go through 2FA as well? First time in 9 years that this happened to me. My acc was logged in 'BY' 'Vitebsk' during the illicit purchases but I'm based in Asia I gathered all the screenshots and provided in the ticket to steam support. \n\nAll i got was the standard copy paste template reply by Steam Support. Lost $500+ and was not even worthy of having a proper person to look into this. I dont think they even read or take a look at the screenshots cause if they did, they would have come to the realization that what happened was clearly fraud, and with a few clicks, reverse the unauthorized transactions, refund my wallet and ban the hijacker. \n\nOver the years, i've spent quite a fair bit on steam but really, this is the kind of recourse we get when our account is compromised? They just don’t care, sigh. I only expect the bare minimum from Steam and looks like even that is quite far-fetched.\n\nSS: https://imgur.com/a/67frcls \n\nHijacker: https://steamcommunity.com/profiles/76561199141246495\n\nSteam Response: https://imgur.com/a/V6v4maM\n\nI could think of a few ways on how to Improve:\n\n1) Add 2FA to market transactions. (even if its bulk posting or selling of items, just 1 2FA notif is required)\n\n2) Enable accounts to be region locked. (if you are migrating, then have to go through steam support etc)\n\n3) Additional Lock on Steam Wallet. (Another password perhaps?)\n\nEDIT: 2nd ticket in and I have still yet to receive a non robotic copy paste template response from Steam.\n04\nRestoration2021-11-29\nSteam Guard & an item-restoration refusal\n\nA preserved post includes the author’s account of item theft and a support response declining restoration.\n\nREDDIT / PUBLIC TESTIMONYr/DotA2Capture record 58\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 563 words\nMany people are losing item via clicking links where steam guard is enabled and steam support doesn't not restore items.\n\nsteam_support_tickets_MEGA.json / record 58\n\nAccounts are getting compromised and might be their pc as well where Steam market is targeted hence the malicious links . I am assuming these hackers are getting encouraged where steam support is not doing nothing and they are getting away with hacking items.  \nLiterally the guy who is supporting the game which he doesn't get any in game advantage just  cosmetics in game only for the sole purpose of supporting the game so that the game will prosper and become beautiful way  to enjoy weekend. But right now players are getting hacked left right and center and steam support  is copy pasting message where in short they are blaming the guy who clicked link. 1st this is happening because they are not targeting players but they are targeting market since they are selling those stuff for real cash via party website. Steam is a huge company and can eradicate the problem or at least can remove links temporarily  in chat since hackers are targeting .They made us install steam guard by saying we wont help if there is no steam guard now steam guard is not enough to save our inventory now they changed their policy  that they should not click any suspicious links. How would we know if the link is suspicious ? After clicking and getting our inventory stolen right !   \n\"we'd have to duplicate an item to restore it. Duplication lowers the value of all items by reducing their scarcity and inflating the economy, which affects everyone involved in trading and the Market. To maintain the value of everyone’s inventory, we do not restore items. For more information, please see the Steam Item Restoration Policy.\"  \nThey care for millions of people IN STEAM MARKET where as few  are losing items which is going to affect market where the rightful owner bought the items and hacker is going to sell the item via 3rd party website and enjoy ! HOW IRONIC !!  \nThis is the message from support where my frnd got his items stolen via clicking on link  \n   \nHi there,  \n\nThank you for the information and screenshots provided.  \n\nIt appears that the account was compromised, please take the following steps to secure your account and computer:  \n\nScan your computer for viruses, key loggers, spyware, and other malicious code using antivirus software with updated virus definitions.  \nChange the password for the email address that is associated with your Steam account.  \nRegularly reset your Steam account password.  \n\nPlease see our Security Recommendations article.  \n\nIn addition, I’m sorry to hear that your items were removed without your permission. Unfortunately, Steam Support does not restore scammed, lost, or stolen items for any reason.  \n\nSince Steam Support does not remove items from accounts, we'd have to duplicate an item to restore it. Duplication lowers the value of all items by reducing their scarcity and inflating the economy, which affects everyone involved in trading and the Market. To maintain the value of everyone’s inventory, we do not restore items. For more information, please see the Steam Item Restoration Policy.  \n\nTo make sure that a scammer is reported, please report them through the Steam Community. Reporting a scammer through the Steam Community is the best way to prevent them from committing future scams.  \n\nTo learn how to avoid scams or hijackings, please see our Trade Scam article.  \n\nIf you still need assistance, please let us know.\n05\nEnforcement2025-05-11\nSelective enforcement & an unexplained ban\n\nA community member describes a disputed ban and contrasts it with the visibility of commercial gambling promotion.\n\nREDDIT / PUBLIC TESTIMONYr/SteamUncensoredCapture record 107\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 1,208 words\n🚨 Steam Bans Without Reason and Ignores Its Community — What’s Going On?\n\nsteam_support_tickets_MEGA.json / record 107\n\nHey r/Steam,\n\nI’m writing this to share my thoughts and concerns about my friend [moneylead](https://steamcommunity.com/id/moneylead/) and Steam’s policies in general. I spoke with him yesterday about his situation, though I didn’t discuss writing this post with him—I asked last night, but he hasn’t responded yet. I want to highlight that this issue is broader than just his case, and while Steam might make changes in the future (though that’s unlikely), I feel the community needs to understand how far Steam has strayed from its original values. I’m not trying to put moneylead in a tough spot with this thread—all the info I’m sharing is public, nothing secretive. I hope he won’t be upset with me, but the community needs this case to see the bigger picture and how Steam feels completely unaccountable.\n\n**Why Does Steam Ignore Its Community?**  \nWhy does a platform like **Roblox** provide a detailed log of ban reasons, while Steam, which claims to be \"community-driven,\" ignores its community, bans whoever they want, for whatever they want, with no transparency? I looked into Roblox as a popular game—not a direct competitor to Steam—to see how their bans look, and you can check it out yourself: [Roblox Ban Reasons](https://www.google.com/search?q=Roblox+ban). Their bans are clear, detailed, and actually explain what you did wrong. I think most decent gaming communities operate like this—not with support agents named Olga, hired through outsourcing, who only know how to send canned auto-replies. Take cases like St4ck—or my friend **moneylead**. All these unbans, like **St4ck’s** or **Alexanddd’s**, happened behind closed doors with zero comments from Steam. Of course, it’s convenient for Steam to handle everything in secret, so no one knows or sees what’s going on—but this violates Steam’s own community rules and principles.\n\n**Who Is moneylead?**  \nI’ve known [moneylead ](https://steamcommunity.com/id/moneylead/)since around 2021. We played Dota 2 a couple of times, and then I just stayed on his friends list. He’s always been a legit player, bringing revenue to Steam through purchases. He never sold his skins, whether in **Dota or CS2—he wasn’t a trader**. All he did was:\n\n* Buy games and skins.\n* Collect badges to level up his profile.\n\nAccording to [SteamSets](https://steamsets.com/account/76561199080934614), he’s given out 324,000 Steam Points—I think he awarded profile rewards to all his friends in the list (though I’m not 100% sure). I do know he ran contests and gave gifts to friends, always supporting the community.\n\n**Steam’s Unfair Treatment**  \nI’ve seen Steam remove his showcases, avatar, description, and even his country multiple times—just because he’s from **Ukraine**. He has a ton of haters leaving toxic comments on his wall, and Steam seems to favor **Russian** users. Every time he tried to appeal the removal of his showcases or profile description—which didn’t break any rules, just had his Instagram link, and his avatar is the same as it is now—Steam moderators didn’t care. **They don’t care about top players who bring them massive revenue, nor about regular users.**\n\n>*Here’s the worst part: moneylead works in cybersecurity, specifically fighting account theft and phishing. He’s neutralized over 5,000 threats targeting Steam alone. And yet, Steam bans him for \"account hijacking\"?*\n\nIf you roughly calculate moneylead’s contribution to Steam and the community—his profile, level, badges (not skins, you can’t sell those)—is this normal, Steam? Banning people, closing tickets, and ignoring users with a spotless reputation who aren’t involved in any commercial activity, just bringing you profit without taking anything in return?\n\n**Steam’s Double Standards**  \nI’m honestly shocked:\n\n* YouTubers who promote casinos and skin gambling? Steam’s fine with that.\n* A cybersecurity expert who fights scams, doesn’t promote casinos, and openly talks about it on his profile? **Banned with no explanation, ignored, and denied an unban.**\n\nI wonder if Steam deliberately bans a high-level account once a year just because of their impunity—maybe for hype or something. Otherwise, this is just madness. It’s scary to think how many regular players have lost their accounts and skins—not because of scammers, but because of Steam’s desire to ignore, send auto-replies, and do whatever they want.\n\n**How Many Others Are Affected?**  \nHow many others are out there—maybe not as well-known—who just have a few games or skins, get banned for nothing, and receive zero explanation or response? **Is this even legal?** Every other platform provides a detailed log with specific violations, but Steam slaps on the same vague label and sends templated responses.\n\n* How safe is it to buy skins on Steam?\n* What’s the chance Steam will just ban your account for no reason, with no explanation?\n\n**A Message to Valve**  \nI wish moneylead the best in resolving this, but Valve, it’d be great if you remembered what \"community\" means and started following the law. Because right now, it looks like your 30% commission, impunity, and sense of being above the law in the U.S. have given you the idea that you can do whatever you want.\n\nI’m sure there are many others like moneylead and St4ck—people who aren’t public or don’t have the resources to fight back. Let’s unite these cases. **If you’re a U.S. resident who’s been banned by Steam without reason and wants to challenge it, please reach out to me.** I’m finishing my **Juris Doctor (J.D.) program at SMU Dedman School of Law** in Dallas, Texas, and I’m participating in a legal clinical practice under Rule 13 of the Texas Supreme Court.\n\nWhat Steam is doing is absolutely disgusting and illegal, and **I’d be happy to help any gamer (legitimate, with no real violations) who has games or skins with value. This will be beneficial for my practice, and it’s time to put Steam in its place and show them they can’t just dictate their own rules with arbitration**. Let’s take it all the way—not for punishment, but for the sake of the community. Maybe if Steam loses a case, they’ll change their policies and start explaining their actions like most popular gaming communities do. Many of us remember how Steam Support used to recover stolen accounts and ended up “stealing” skins themselves—banning without real reasons is basically the same thing, and that’s a serious accusation.\n\nSo, r/Steam, see you soon. I think you understand what you’re doing and how many people you’ve illegally deprived of their assets. I want to raise this issue—not just for the U.S., but for the entire world. You’ve banned class-action lawsuits? **Welcome to Texas.** I recommend starting to look for licensed attorneys in Texas, because I’d love to discuss your company’s policies, feedback, and support agents named Olga—a name that strongly associates with Russian users. Maybe it’d be easier to move your company to Moscow? But I’d be happy to discuss these critical issues on behalf of the global gaming community.\n\nAlso, I wouldn’t recommend ignoring the lawsuit request that will be sent to your physical address and email address, as the court will proceed without you, and that might upset you—especially since things aren’t going so well for a company with stocks like yours.\n\n**Thanks to everyone who took the time to read this. For those who need real help with an unjust Steam ban without any explanation, I’d be happy to assist. For users from Texas, we can easily file a collective lawsuit against Steam—let’s connect and make it happen.**\n02 / شبكة تطوير «Steam»\nالبنية التحتية العامة.تم تسجيله على نطاق واسع.\nتنزيل جميع ألبومات فرقة «252» ↓\n\nالمرفق output_steam_network تسجل اللقطات مستودعات السجلات، والعلاقات العامة بين المساهمين والمشروعين الفرعيين، وتداخلات الملفات الشخصية. هذه سجلات منشورة — ما تم بناؤه، ومن ساهم فيه، وما تم إنشاؤه كفرع. إن السجلات المكتوبة للقدرات العامة هي ما يجب أن تأخذه «Valve» في الحسبان.\n\nالمستودع / الوصف\tالمساهمون\tفوركرز\tالملفات الشخصية المسجلة\nalliedmodders/amxmodx\n\nAMX Mod X - Half-Life 1 Scripting and Administration\n\n\t40\t40\t80\nalliedmodders/sourcemod\n\nSourceMod - Source Engine Scripting and Administration\n\n\t40\t40\t80\nDoctorMcKay/node-steam-user\n\nAllows interaction with the Steam network via the Steam client protocol\n\n\t40\t40\t80\nFacepunch/Facepunch.Steamworks\n\nAnother fucking c# Steamworks implementation\n\n\t40\t40\t80\nJustArchiNET/ArchiSteamFarm\n\nC# application with primary purpose of farming Steam cards from multiple accounts simultaneously.\n\n\t40\t40\t80\nodota/core\n\nOpenDota: Open source Dota 2 data platform with automated replay parsing\n\n\t40\t40\t80\nodota/dotaconstants\n\ndotaconstants: Static data for Dota applications\n\n\t40\t40\t80\nodota/web\n\nOpenDota: React web UI for Dota 2 statistics using the OpenDota platform\n\n\t40\t40\t80\nsplewis/get5\n\nCS:GO Sourcemod plugin for competitive matches/scrims\n\n\t40\t40\t80\nSteamDatabase/FileDetectionRuleSets\n\n🔎 Rules to detect game engines and other technologies based on Steam depot file lists\n\n\t40\t40\t80\nSteamRE/SteamKit\n\nSteamKit2 is a .NET library designed to interoperate with Valve's Steam network. It aims to provide a simple, yet extensible, interface to perform various actions on the network.\n\n\t40\t40\t80\nValveSoftware/dxvk\n\ndxvk tree containing branches used by Proton\n\n\t40\t40\t80\nValveSoftware/GameNetworkingSockets\n\nReliable & unreliable messages over UDP. Robust message fragmentation & reassembly. P2P networking / NAT traversal. Encryption.\n\n\t40\t40\t80\nValveSoftware/gamescope\n\nSteamOS session compositing window manager\n\n\t40\t40\t80\nValveSoftware/Proton\n\nCompatibility tool for Steam Play based on Wine and additional components\n\n\t40\t40\t80\nValveSoftware/source-sdk-2013\n\nThe 2013 edition of the Source SDK\n\n\t40\t40\t80\nValveSoftware/wine\n\nWine with a bit of extra spice\n\n\t40\t40\t80\nValveSoftware/steam-devices\n\nList of devices Steam and SteamVR will want read/write permissions on, to help downstream distributions create udev rules/etc\n\n\t39\t40\t79\nValveSoftware/steam-audio\n\nSteam Audio\n\n\t38\t40\t78\nalliedmodders/metamod-source\n\nMetamod:Source - C++ Plugin Environment and Detour Library for the Source Engine\n\n\t37\t40\t77\nalliedmodders/sourcepawn\n\nA small, statically typed scripting language.\n\n\t35\t40\t75\nValveSoftware/Fossilize\n\nA serialization format for various persistent Vulkan object types.\n\n\t31\t40\t71\nrlabrecque/Steamworks.NET\n\nSteamworks wrapper for Unity / C#\n\n\t27\t40\t67\nModDota/moddota.github.io\n\nModDota github pages project.\n\n\t26\t40\t66\nodota/parser\n\nReplay parse server generating JSON log events from Dota 2 replay files\n\n\t26\t40\t66\nValveSoftware/steam-for-linux\n\nIssue tracking for the Steam for Linux beta client\n\n\t26\t40\t66\nSteamRE/DepotDownloader\n\nSteam depot downloader utilizing the SteamKit2 library.\n\n\t24\t40\t64\nJustArchiNET/ASF-ui\n\nThe official web interface for ASF\n\n\t23\t40\t63\nadvancedfx/advancedfx\n\nHalf-Life Advanced Effects (HLAE) is a tool to enrich content creation mainly for the Counter-Strike series.\n\n\t22\t40\t62\nalliedmodders/ambuild\n\nAlliedModders C++ Build System\n\n\t23\t39\t62\nSteamDatabase/BrowserExtension\n\n💻 SteamDB's extension for Steam websites\n\n\t21\t40\t61\nodota/mobile\n\nReact Native apps for viewing Dota 2 data on Android/iOS\n\n\t19\t40\t59\nValvePython/steam\n\n☁️ Python package for interacting with Steam\n\n\t18\t40\t58\nskadistats/clarity\n\nComically fast Dota 2, CSGO, CS2 and Deadlock replay parser written in Java.\n\n\t13\t40\t53\nSteamRE/open-steamworks\n\nOpen Steamworks is a set of reverse engineered headers for the Valve's Steam Client. More or less abandoned now that the Steamworks SDK is publically available.\n\n\t13\t40\t53\nValveSoftware/Source-1-Games\n\nSource 1 based games such as TF2 and Counter-Strike: Source\n\n\t13\t40\t53\nalliedmodders/hl2sdk\n\nHalf-Life 2 SDK Mirrors\n\n\t11\t40\t51\nSteamDatabase/steamdb.info-issues\n\n🚱 Issue tracker for the SteamDB website\n\n\t11\t40\t51\nCSGOFloat/inspect\n\nSource Code that Powers the CSFloat Inspect Link API\n\n\t10\t40\t50\nValveSoftware/SteamOS\n\nSteamOS community tracker\n\n\t10\t40\t50\nalliedmodders/source2mod\n\nExperimental\n\n\t40\t9\t49\nsmiley/steamapi\n\nAn unofficial object-oriented Python library for accessing the Steam Web API.\n\n\t9\t40\t49\nSteamDatabase/GameTracking\n\n🛢 Dumping things, so you don't have to\n\n\t8\t40\t48\nValveSoftware/counter-strike_rules_and_regs\n\nCS:GO\n\n\t7\t40\t47\nValveSoftware/openvr\n\nOpenVR SDK\n\n\t6\t40\t46\nSteamDatabase/easy-markdown-editor\n\nEasyMDE: A simple, beautiful, and embeddable JavaScript Markdown editor. Delightful editing for beginners and experts alike. Features built-in autosaving and spell checking.\n\n\t40\t4\t44\nValveSoftware/Dota-2\n\nTracker for issues specific to Linux and Mac in the Reborn client. If you have a general issue or non-system-specific feature request please go to dev.dota2.com\n\n\t6\t38\t44\nValveSoftware/Dota2-Gameplay\n\nPublic Bug Tracker for Dota 2\n\n\t4\t40\t44\nJustArchiNET/ArchiBot\n\nNo description in the capture.\n\n\t16\t27\t43\nztizzlegaming/CSGOWinBig\n\nOpen-source Counter-Strike: Global Offensive jackpot betting website.\n\n\t1\t40\t41\nJustArchiNET/mantis.justarchi.net\n\nMantis Bug Tracker (MantisBT)\n\n\t40\t0\t40\nodota/node-steam-user\n\nAllows interaction with the Steam network via the Steam client protocol\n\n\t40\t0\t40\nModDota/TypeScriptAddonTemplate\n\nDota 2 addon template with TypeScript Panorama and VScripts.\n\n\t9\t29\t38\nValvePython/vdf\n\n📜 Package for working with Valve's text and binary KeyValue format\n\n\t6\t32\t38\nalliedmodders/amtl\n\nAlliedModders C++ Template Library\n\n\t17\t19\t36\nValvePython/dota2\n\n🐸 Python package for interacting with Dota 2 Game Coordinator\n\n\t5\t30\t35\nalliedmodders/stripper-source\n\nStripper:Source\n\n\t13\t21\t34\nAllyans3/steam-market-api-v2\n\nSteam Market API v2 package\n\n\t3\t31\t34\nModDota/dota-tutorial\n\nCustom game DOTA tutorial.\n\n\t11\t23\t34\nodota/blog\n\nNo description in the capture.\n\n\t29\t3\t32\nOpsecGuy/BetterGo\n\nExternal CS:GO cheat written in python.\n\n\t1\t27\t28\npxvr-official/1\n\n無許諾配信 企業理念剽窃 動物の森収益化 大神ミオ権利者削除 戌神権利侵害発言 常闇トワ炎上 夜空メルストーカー被害 建築王サポーター放置 赤十字マーク 魔乃アロエ卒業 一つの中國支持声明 大空昴3Dライブ 無限延期清掃員職業差別 日清コラボ楽曲 musedash非公開 rog案件取り消し 壁画ライブ 丁真 Ding Zhen 郑爽 Zheng Shuang 防护林 与朵小天使w 伊月猫凛 本主萌埋午休傻 汪峰 重生细胞 壁纸 比利海灵顿 香蕉君 van 田所浩二 抽象带篮子 抗压背锅吧 季子越 蒋明辉 傻逼…\n\n\t0\t28\t28\nRevadike/InternalSteamWebAPI\n\nDocumenting the unofficial and internal Steam Web API\n\n\t1\t27\t28\nJoeSzymkowiczFiveM/qb-lootcrate\n\nA CSGO-style case opening script\n\n\t2\t25\t27\nAbrarKL/MyRoulette.XYZ\n\nCSGO / Steam Roulette Site created with PHP and Node JS, using the Material Design front-end framework.\n\n\t1\t25\t26\nJustArchiNET/ASF-WebConfigGenerator\n\nNo description in the capture.\n\n\t10\t15\t25\nModDota/dota-data\n\nAuto-generated Dota 2 resource dumps\n\n\t11\t14\t25\nModDota/TypeScriptDeclarations\n\nTypeScript declarations for Dota 2.\n\n\t11\t14\t25\nModDota/API\n\nNo description in the capture.\n\n\t12\t12\t24\nalliedmodders/cssdm\n\nCounter-Strike:Source Deathmatch\n\n\t10\t13\t23\nSteamDatabase/steamstat.us\n\n✅ Front-end of Steam services status website\n\n\t4\t18\t22\nc0deina/csgojackpotV2\n\nCSGO Jackpot Source\n\n\t1\t20\t21\nValvePython/steamctl\n\n🤸 Take control of Steam from your terminal\n\n\t2\t19\t21\nValvePython/csgo\n\n🔫 Python package for interacting with CS:GO Game Coordinator\n\n\t3\t17\t20\nBeepIsla/csgo-crash-exploit\n\nAllows you to crash any Windows user\n\n\t3\t16\t19\nValvePython/vpk\n\n📦 Open, Search, Extract and Create VPKs in python\n\n\t4\t15\t19\nalliedmodders/SM-SteamWorks\n\nExposing SteamWorks functions to SourcePawn.\n\n\t14\t3\t17\nSteamRE/Steam4NET\n\nSteam4NET is a .NET wrapper around the Steamworks C++ interfaces\n\n\t2\t15\t17\nalliedmodders/hl2sdk-manifests\n\nInformation about HL2SDKs shared between Metamod:Source and SourceMod.\n\n\t6\t10\t16\nJustArchiNET/ASF-PluginTemplate\n\nTemplate repository that you can use for creating custom plugins for ArchiSteamFarm.\n\n\t8\t7\t15\nModDota/Dota2AIFramework\n\nGeneral Framework for Dota 2 AI Competitions\n\n\t1\t14\t15\nShkyyl/KeyChamp\n\nExtension for joining free case battle on key-drop automatically\n\n\t1\t14\t15\nSteamDatabase/SteamMonitor\n\n😤 Track Steam's connection manager servers status\n\n\t2\t12\t14\nBaterka/cslore.com\n\nCS:GO gambling site - csgo.style\n\n\t1\t12\t13\nSteamDatabase/SteamTokenDumper\n\n🔢 Submit users' PICS access tokens to SteamDB\n\n\t2\t11\t13\nmonoblocker/roulette\n\nRoulette CS:GO made in React and Typescript\n\n\t1\t11\t12\nzsith/launcher.user.js\n\n// ==UserScript== // @name AposLauncher // @namespace AposLauncher // @include http://agar.io/* // @version 3.062 // @grant none // @author http://www.twitch.tv/apostolique // ==/UserScript== var aposLauncherVersion = 3.062; Nu…\n\n\t1\t11\t12\nLincolnIT/CSGODouble-bot-automated\n\nCSGODouble Automated, auto Betting Bot.\n\n\t1\t10\t11\nvladpuz/steam-market\n\nSteam market API client\n\n\t4\t7\t11\nmcgrizzz/Cstrike.bet\n\nCSGO Roulette Website Angular frontend, nodejs backend, and steam trading bots\n\n\t1\t9\t10\nodota/underlords-web\n\nUI for OpenUnderlords\n\n\t5\t5\t10\nSteamDatabase/SteamToTwitter\n\n🕊 Tweets announcements from various Steam groups\n\n\t1\t9\t10\nModDota/AbilityLuaSpellLibrary\n\nThe successor to the Spell Library by Pizzalol\n\n\t4\t4\t8\nalvinl/bitskins\n\nUnofficial BitSkins API client\n\n\t2\t5\t7\nb1naryth1ef/steamy\n\nA Python Steam community and market API interface that will get you all hot and bothered\n\n\t2\t5\t7\nkratos1812/Case-Opening\n\nIn-game case opening system for CSGO servers.\n\n\t2\t5\t7\nodota/docs\n\nOpenDota API documentation\n\n\t4\t3\t7\nSteamDatabase/steam-advanced-access-fetch-players\n\n📈 Simple script to fetch Steam player count\n\n\t1\t6\t7\nTheRioMiner/CsgoBetterExternalRaytrace\n\nOverridden maps pack for better external raytrace\n\n\t1\t6\t7\nalliedmodders/hl2sdk-mock\n\nMock HL2SDK and Server\n\n\t5\t1\t6\nchristophersu/PySteamMarket\n\nPython API for getting prices from the Steam market.\n\n\t1\t5\t6\nExtremelyd1/Strat-Roulette\n\nCS:GO Sourcemod Plugin\n\n\t2\t4\t6\ngiovanni-orciuolo/double-sdk\n\nA simple way to write CS:GO cheats!\n\n\t2\t4\t6\nJustArchiNET/Madness\n\nMadness embraces your project by including compatibility layer for selected APIs normally not available on .NET Framework target.\n\n\t5\t1\t6\nModDota/TypescriptPanoramaDeclarations\n\nNo description in the capture.\n\n\t4\t2\t6\nodota/rapier\n\nA JavaScript Dota 2 (Source 2) replay parsing library\n\n\t1\t5\t6\nVozn1akHero/CSGOCaseOpeningSimulator\n\nCounter-Strike case opening simulator which resembles the good old CS:GO user interface\n\n\t3\t3\t6\nautarc/steam-store\n\nAPI client for the unofficial steam storefront/big picture resource\n\n\t2\t3\t5\nBETTING-CODE/awesome-esports-sites\n\nA curated list of awesome esport betting sites – live, statistics and other resources.\n\n\t1\t4\t5\njonteohr/Better-Warden\n\nAn improved and more advanced warden plugin with a custom menu for CS:GO jailbreak servers!\n\n\t2\t3\t5\nLudzikk/CSGO-Gambling-Site\n\nhttps://ludzikk.github.io/CSGO-Gambling-Site/\n\n\t1\t4\t5\nModDota/find-steam-app\n\nFind location of an installed Steam app\n\n\t3\t2\t5\nmprey/csgocact.us\n\nsource code for csgocact.us\n\n\t1\t4\t5\nnezu-cc/ServerCrasher\n\nCS:GO Server Crasher\n\n\t1\t4\t5\nodota/testfiles\n\nStores test replay files\n\n\t2\t3\t5\nodota/underlordsconstants\n\nConstant data for Dota Underlords\n\n\t3\t2\t5\nSnaBe/node-steam-market-fetcher\n\nA Node.js wrapper for the Steam Community Market API.\n\n\t2\t3\t5\nSteamDatabase/.github\n\n💗 Organization-wide community health files\n\n\t1\t4\t5\nwolfcon/RIP-HLTV-BET\n\nRIP BET AD (For Tampermonkey) https://greasyfork.org/en/scripts/423484-rip-hltv-bet\n\n\t2\t3\t5\nalliedmodders/blaster.net\n\nSource and GoldSrc Query Tool\n\n\t2\t2\t4\ncatears124/CS2-Price-API\n\nsimple python cs2 steam market price API\n\n\t1\t3\t4\nialakey/caseforge\n\nOpen-source CS2 case-opening platform: Steam auth, provably fair openings, RTP-balanced case builder, withdrawals bought on market.csgo.com and an admin CRM.\n\n\t1\t3\t4\nIlusion9/csgo-fix-mapchange-crash-sm\n\nFix players crash on map change.\n\n\t1\t3\t4\nismail0234/Benson-Map-Crash-Fixer\n\nCSGO Map Change Client Crash Fixer\n\n\t1\t3\t4\njaxwilko/steam-market-api\n\nPHP - Composer Compatible - Steam Market API\n\n\t2\t2\t4\nJustArchiNET/ArchiTag\n\nArchiTag is a very small utility based on Python 3 and Mutagen to provide missing functionality in opusenc of writing specific Opus metadata, such as total number of tracks or track number.\n\n\t1\t3\t4\nModDota/DotaUI\n\nNo description in the capture.\n\n\t2\t2\t4\nnode-steam/market-pricing\n\nWrapper for the unofficial Steam Market Pricing API\n\n\t1\t3\t4\nodota/media\n\nStores media files for Dota projects\n\n\t2\t2\t4\nSergeyIvanovDevelop/Crypto-Steam-Platform\n\nThe repository contains the code and configuration to run a platform for creating cryptocurrency stakes for arbitrary ERC20 tokens.\n\n\t1\t3\t4\nAareksio/csgodouble-floatchecker\n\nAdds context menu option to check item's float value\n\n\t1\t2\t3\nchinm4/CSGOdrop\n\nA online csgo gambling casino that includes a variety of mini games that allows you to win csgo skins\n\n\t2\t1\t3\nCruze03/CSGO-Case-Opening-Prank\n\nCommand:- !prank (Admin flag \"n\" required)\n\n\t1\t2\t3\nDhruva-Kapadia/CSGOTrollGG\n\nCSGO Case Opening Simulator\n\n\t2\t1\t3\nErhanCSGO/CSGOPolygon-prediction\n\nCSGOPolygon.com - prediction script, double your coins by using this tool\n\n\t1\t2\t3\nEv-Hoang/Bedrock-Chest-Case-Opening\n\nHypixel Skyblock Dungeon Mod - Bedrock Chest Opening Animation (CSGO Style)\n\n\t1\t2\t3\njmjp/csgo-roulette\n\nA csgo gambling roulette make with VueJS 3\n\n\t2\t1\t3\nJustArchiNET/ArchiCrowdin\n\nNo description in the capture.\n\n\t1\t2\t3\nLeonSK/WearMarketInspector\n\nRetrieve Wear Value (Float Value) and Pattern Index from Steam Community Market using http://csgo.exchange API\n\n\t1\t2\t3\nmaximgeerinck/csgo-gamble\n\nCSGO gambling website\n\n\t1\t2\t3\nModDota/BugTracker\n\nListing bugs for Dota 2 Custom Games\n\n\t2\t1\t3\nplwp/mma-betting\n\nUFC/MMA betting model with Pinnacle steam detection for AU book latency arb\n\n\t2\t1\t3\nSouthsideswag16/Csgo-Gambling-Site\n\nNo description in the capture.\n\n\t2\t1\t3\ntacyarg/csgofiesta-frontend-react\n\nRemastered version a the long time favorite csgo site\n\n\t2\t1\t3\nVelorasse/Mutah-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-csmoney-csgoskins\n\ngambling script for Mutah, Keydrop, csmoney, and csgoskins, featuring hacks, cheats, and predictors. Offers strategies to boost winning odds and optimize performance on these platforms.\n\n\t3\t0\t3\nalliedmodders/am-github-artifact-webhook\n\nNo description in the capture.\n\n\t2\t0\t2\ncharamza/roulette\n\nCSGO like roulette in JS\n\n\t1\t1\t2\nCruze03/CSGO-PugSetup-RoundRestore\n\nSometimes (player dropped/crashed) which would be disadvantage for a team. It would be very handy to restore the match to the previous round.\n\n\t1\t1\t2\ncsgorol/CSGO-ROLL-Crash-Predictor\n\nCSGO-ROLL-Crash-Predictor\n\n\t1\t1\t2\nFoxSerito/FOXWORLD_plugin_DoubleJump_CSGO\n\nПлагин SourceMod (CSGO). Двойной прыжок с эффектом.\n\n\t1\t1\t2\nhkehayovmoonbiz/CS2-Casino-Full-Source-Code\n\nCS2, CS2 betting platforms, Skin Roulette, Case Unboxing, Crash games, Jackpot, purchase CS2 casino source, crypto gambling\n\n\t1\t1\t2\nJustZakary/steamstoreapi\n\nThis NPM module is a API wrapper that makes the steam unofficial API easier to use.\n\n\t2\t0\t2\njzimr/steam-market-api\n\nA java library to easily get Steam Community Market data\n\n\t1\t1\t2\nMomohime/CSGO.Network-Jackpot-Coinflip\n\nNo description in the capture.\n\n\t1\t1\t2\nnnjjswat/moneybot\n\nautomated bots for bustabit (formerly known as moneypot), csgo crash, etc\n\n\t0\t2\t2\nodota/carry\n\nLegacy Application for donations to the OpenDota project\n\n\t1\t1\t2\nodota/PublicMatchDataBot\n\nA Discord bot to remind users to turn on Expose Public Match Data in the Dota 2 client\n\n\t1\t1\t2\nOrillio/CSGOBet.com\n\nCSGO roulette web app\n\n\t2\t0\t2\nripexz/csgo-bet-alert\n\nA Chrome extension to keep track of active CS:GO Lounge matches.\n\n\t1\t1\t2\nrrpvm/lumen_sense-beta-deprecated-\n\nthis is internal csgo cheat written by me(no paste, self reverse structures). start : ~6 August 2020, end : ~ 14 December 2020\n\n\t1\t1\t2\nRuthless222/csgoscore\n\nThis is a Counter Strike Global Offensive Betting Site. You chose the skins you want to bet and try to win jackpots\n\n\t2\t0\t2\ntfburns/CSGO-cases-PL\n\nExpected profit-loss of CS:GO case openings\n\n\t1\t1\t2\nTomDra/CSGO-Case-Data-Analysis\n\nWorks out the most profitable CS:GO case at that current time\n\n\t1\t1\t2\nValvePython/dota2-wrappers\n\nNo description in the capture.\n\n\t1\t1\t2\nValvePython/teamfortress2-closed-captions\n\nThis project aims to provide a set of closed captions for Team Fortress 2\n\n\t1\t1\t2\nVistaNetGTX/Cstrike.bet-\n\nCSGO Roulette Website Angular frontend, nodejs backend, and steam trading bots\n\n\t1\t1\t2\nwafflas/csgo-case-opening-simulator\n\nI created a cs go case opening simulator for a meme coin\n\n\t0\t2\t2\nAdmiral-Enigma/Le_Coinflip\n\nConflip game\n\n\t1\t0\t1\nadryeljuliao/roulette-csgo\n\nNo description in the capture.\n\n\t1\t0\t1\nAndreuTheG/csgo-coinflip-web\n\nCSGO Gambling Coinflip Website\n\n\t1\t0\t1\nasmilen/csgoDouble\n\na b c\n\n\t1\t0\t1\nb1naryth1ef/csgofort\n\nA CSGO portal for trading, betting, analytics, and more!\n\n\t1\t0\t1\nBaterka/PrivateSteamBettingWebsite2024\n\nPrivate Steam (Counter-Strike 2) betting/gambling website - Roulette, Jackpot\n\n\t1\t0\t1\nblackcaer/SteamTradeHandler\n\nAutomation of Steam trading. Helper project for bet automation.\n\n\t1\t0\t1\nBTheCoderr/theRounders\n\nThe Rounders - A professional-grade sports betting analytics platform combining real-time odds tracking, sharp movement detection, and advanced statistical analysis. Features include line shopping, steam move alerts, power rankings, and comprehensive bet t…\n\n\t1\t0\t1\nCallumHemsley/KazeBot\n\nA Twitch chat betting bot for CSGO, simply bet a certain amount of points, and double if you win, lose all if you lose. Simple.\n\n\t1\t0\t1\nchrisjpm/CSGOJackpotTemplate\n\nFront end for a jackpot site\n\n\t1\t0\t1\ncolinsenner/valve-bug-bounty\n\nFor many years CS:GO, Dota 2, and Team Fortress 2 servers had a bug that allowed malicious users to leak crucial server process memory or reliably crash any server.\n\n\t1\t0\t1\ncoryypeters/nrl-odds-intelligence-pipeline\n\nReal-time sports betting odds intelligence — streaming pipeline that detects line movement, steam, and arbitrage across bookmakers. Python · Redis Streams · FastAPI · React.\n\n\t1\t0\t1\ndeissh/dev-csgoduo\n\nCS:GO. Bot for receiving things on the site (Polygon, Duo, Double and etc).\n\n\t1\t0\t1\ndom1torii/even-better-font-manager\n\nSimply even better cross-platform tool for CS2 Font Management\n\n\t1\t0\t1\nDONnicov/CSGO-crash-black-screen-\n\nsolution csgo crash black screen and close csgo\n\n\t1\t0\t1\nDoubleBoters/CsgoDouble\n\nNo description in the capture.\n\n\t1\t0\t1\ndownarowiczd/DoubleBot\n\nAn old CSGO Double Bot written for my friend. - 07.05.2016\n\n\t1\t0\t1\nErayBahar/steammarketscraper\n\nSteam Market Scraper Python-based tool that tracks real-time CS2 skin prices using Steam's hidden API. It fetches the lowest sell and highest buy offers for any item, helping you monitor deals or snipe underpriced listings automatically.\n\n\t1\t0\t1\nfairydarkness/SteamwebmailAPI\n\nUnofficial Python API for steamwebmail.com Fast, lightweight, and browserless library for automating steamwebmail.com. Support for session management, proxy, folder navigation, and message retrieval\n\n\t1\t0\t1\nFAQU2/CSGO-Coinflip-MyJailShop\n\nSourcemod plugin which provides a Coinflip system for MyJailShop.\n\n\t1\t0\t1\nFlamesONE/csgo-case-opening\n\nNo description in the capture.\n\n\t1\t0\t1\nFunnyRain/csgorun-crash-watch\n\n🚀 CsgoRun dump crash. / 🚀 CsgoRun дамп крашей.\n\n\t1\t0\t1\ngeohdgio/Venatus-Autenticator\n\nეს არის Steam Autenticator ქართული Venatus Trade & Betting ისთვის და Valve News Georgia-სთვის.\n\n\t1\t0\t1\nhakanstarlord/steam-bot\n\nSports betting steam-move signal detection with ML pipeline (XGBoost stacking + isotonic calibration), backtesting engine, Flask dashboard, and Telegram alerts.\n\n\t1\t0\t1\nHvH-gg/CSGO-Item-CrashFix\n\nA plugin for Counter-Strike: Global Offensive that fixes an exploit where receiving CS2 Items will cause CS:GO clients to crash\n\n\t1\t0\t1\nHvH-gg/CSGO-NetMsg-CrashFix\n\nA plugin for Counter-Strike: Global Offensive that fixes an exploit where spamming NetMsg_StringCmd packets would result in a server crash.\n\n\t1\t0\t1\nisybycnsmam/SteamLibrary\n\nLegacy Steam Unofficial API\n\n\t1\t0\t1\nItsTangerine/SteamApis.Net\n\nUnofficial https://steamapis.com .NET library, supporting .NET 6.0+\n\n\t1\t0\t1\nJustArchiNET/JustArchi.net\n\nNo description in the capture.\n\n\t1\t0\t1\nkiri-osint/CS2-Info-Hub-Bot\n\nA Telegram bot that acts as a hub for CS2 players, providing real-time skin prices, server stats, and user profile/inventory inspection using official and unofficial Steam APIs.\n\n\t1\t0\t1\nKoshkaj/monte\n\nGamified csgo gambling platform implementation\n\n\t1\t0\t1\nmadsab/CaseOpening\n\nA school project using Java. Simulating the case opening from CSGO and more.\n\n\t1\t0\t1\nman90es/steamcardexchange-api\n\nSteamCardExchange.net unofficial REST API server (scraper).\n\n\t1\t0\t1\nMattPua/steam-unofficial-docs\n\nUnofficial docs for Steam APIs with fumadocs\n\n\t1\t0\t1\nMetallist1/Portfolio.CsgoWinGambleProject\n\nA website that was done in 2017 September. Websites focus was on gambling with Counter-Strike items. Project was largely completed however backups were not done correctly, this resulted in half a year of wasted improvements to the code. The website was test…\n\n\t1\t0\t1\nmikebobadilla/csgo-jackpot\n\nNo description in the capture.\n\n\t0\t1\t1\nmikebobadilla/meteor-csgojackpot\n\nCssgo Jackpot done in meteor\n\n\t1\t0\t1\nModDota/D2VDump\n\nDota 2 Server VScript API Dumper\n\n\t1\t0\t1\nModDota/DotaTracking\n\nNo description in the capture.\n\n\t1\t0\t1\nModDota/eslint-config\n\nESLint config by ark120202\n\n\t1\t0\t1\nmr-codinglv/Casino-script\n\nscript casino - script betting - exchange script - bc casino - casino csgo - script bet - betwin script\n\n\t1\t0\t1\nMrKeelik/MrKeel\n\nCSGO DOUBLE BOT\n\n\t1\t0\t1\nnoahlatzel/CSGORollHelper\n\nLeveraging positive expected value on triple green jackpots on CSGORoll!\n\n\t1\t0\t1\noddsgpt/oddsgpt-market-intelligence\n\nResearch on football betting markets, closing odds, CLV, market efficiency, steam moves, AI betting systems, and sports market intelligence.\n\n\t1\t0\t1\noEXU/csgo-server-crasher\n\nCSGO SERVER CRASHER\n\n\t1\t0\t1\nPrdTTony/CSGO-Roulette\n\n[CSGO] Roulette System. Bet on RED or Black and win x2 credits\n\n\t1\t0\t1\nr-adamski/csgo-jackpot\n\nNo description in the capture.\n\n\t1\t0\t1\nSahotallo/Turan-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-Skinbaron-hellcase\n\ngambling script for Turan, Keydrop, Skinbaron, and Hellcase, providing hacks, cheats, and predictors. Includes strategies to improve winning chances and enhance gameplay on these platforms.\n\n\t1\t0\t1\nsamuelcsouza/steam-marketplace-api\n\nAn unofficial API to get data from the Steam Marketplace.\n\n\t1\t0\t1\nSKINSTRACK/CS2-Price-API\n\nSkinstrack offers a free, limited API endpoint that returns Steam item prices. Paid plans additionally provide access to pricing data from multiple marketplaces, making it possible to compare prices across different markets through a single API.\n\n\t1\t0\t1\nsnmtriet/CSGO-Casino-Full-Source-Code\n\nCSGO, CSGOEmpire, Case Opening, Case Battles, Roulette, Coinflip, buy csgo gambling site, gambling\n\n\t1\t0\t1\nSteamRE/homebrew-tools\n\nRepository for installation of SteamRE tools via Homebrew (http://brew.sh)\n\n\t1\t0\t1\nSteamRE/opensteamworks.org\n\nNo description in the capture.\n\n\t1\t0\t1\nTheQuack45/CsgoCaseOpenProgram\n\nSimple program to parse an XML file with CS:GO case information and \"simulate\" case openings\n\n\t1\t0\t1\nTLClassless/StratRouletteCSGO\n\nA 'Strat Roulette' web app for CS:GO!\n\n\t1\t0\t1\ntomasoom/csgoCaseOpening\n\nNo description in the capture.\n\n\t1\t0\t1\nvitaliy-evsyukov/steamgifts-autobet-bookmarklet\n\nbookmarklet for automatic bets on steamgifts.com\n\n\t1\t0\t1\nXpravdaX/RouletteCSGO\n\nNo description in the capture.\n\n\t1\t0\t1\nYuiKasumii/steam_api_unofficial\n\nUnofficial Steam Game Information Database\n\n\t1\t0\t1\nZexuz/Steam-Betting\n\nA betting website build ontop of STEAM's ecosystem\n\n\t1\t0\t1\nANK-RULZZ/steam-jackpot-site\n\ngetting some errors and would like some one to help me with it thank you!!!\n\n\t0\t0\t0\nasmilen/CsgoDoubleVS\n\nNo description in the capture.\n\n\t0\t0\t0\nCORNOODOSADAS/CSGOWeed\n\nCsgo Jackpot and Coinflip\n\n\t0\t0\t0\nCSGOApple/csgoapple\n\nJackpot Site\n\n\t0\t0\t0\nCSGOFAST/csgofast-api\n\nNo description in the capture.\n\n\t0\t0\t0\nDonakall/csgoDoublebot\n\nAutomated bot for csgodouble\n\n\t0\t0\t0\nfedor-selivanov/csgo-fast-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nfoldageros/csgod\n\ndouble bot\n\n\t0\t0\t0\ngmod-gambling/gmod-gambling\n\nNo description in the capture.\n\n\t0\t0\t0\nierome/CSGOBoss-BackEnd\n\nBack end version of CSGOBoss. This was a CSGO Gambling site named CSGOBoss. Coded by an old friend of mine Dahquan Hinds (https://github.com/dahquan/) Thought I would release this to help out any one who would need it.\n\n\t0\t0\t0\njamienp1/CSGODOUBLE-BOT-AUTO\n\ni got a bot thats is betting on the last winning color except from green and if you lose it will double the coins you set it to bet, pretty good, so when there comes a loooong train you will be gaining a bit of money codepaste_net/ugmt92 remove all the _ an…\n\n\t0\t0\t0\nJEYONER/CSGOTOXIC\n\nPAGINA DE JACKPOT CSGO SKINS\n\n\t0\t0\t0\nkalrish/csgo-jackpot\n\nStressful but funny zombie-like Counter-Strike: Global Offensive game mode.\n\n\t0\t0\t0\nkrys12345/roulettee\n\n// ==UserScript== // @name CSGO Predict Bot // @namespace http://csgodouble.com // @version 1.0 // @description predicts what number its gonna be // @author Meee // @match http://www.csgodouble.com/ // @grant none // ==/…\n\n\t0\t0\t0\nLilDuggiMuffi/CSGODouble-Working-Bot\n\nFixed CSGO Double Bot\n\n\t0\t0\t0\nLyricLy/Steam2Proton\n\nCheck if all your Steam games will work with Proton! Uses the official Steam API and the unofficial Proton API.\n\n\t0\t0\t0\nM0NsTeR77/csgo-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nozanhalis/Hi\n\n// ==UserScript== // @name CS GO LOUNGE BOT-Ozan Halis // @namespace http://csgolounge.com/ // @version 0.6.6 // @description Cs Go Lounge Hızlı BOT // @match http://csgolounge.com/* // @match http://dota2lounge.com/* // @updateURL h…\n\n\t0\t0\t0\nscoobertus/CSGO-DoubleBot\n\nNo description in the capture.\n\n\t0\t0\t0\nTradeal/CSGO-Jackpot-Bot\n\nNo description in the capture.\n\n\t0\t0\t0\nValvePython/artifact\n\nNo description in the capture.\n\n\t0\t0\t0\nVampire/CSGO-Roulette-Bot\n\nNo description in the capture.\n\n\t0\t0\t0\nvdemans/csgo-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nVocoreVideo/CSGODungeon-\n\nCSGO Jackpot\n\n\t0\t0\t0\nwayz-dev/csgofloat\n\nNo description in the capture.\n\n\t0\t0\t0\n\nلمحة سريعة: 17 سبتمبر 2026, 11:19:11 كما ورد في المصدر؛ المنطقة الزمنية غير محددة. تم حصر مجموعة العلاقات في التصدير (تتوقف العديد من الفئات عند 40). يبلغ مجموع المساهمين ومطوري الفروع 4,554 إدخالًا للدور عبر 4,214 زوجًا مختلفًا من الملفات الشخصية والمستودعات؛ ويمكن أن يتضمن الملف الشخصي كلا الدورين. الصفر يعني عدم وجود سجلات مسجلة في تلك الفئة. قد تتضمن أسماء المستودعات أسماء مستعارة أو اختلافات في الأحرف الكبيرة والصغيرة؛ وتحتفظ الإجماليات بقواعد الحساب الخاصة بالمصدر.\n\nمصدر المنشأ\nتم إنشاؤه من الملفات التي جمعتها.\nشهادة داعمة\n2323/reddit_scams_ultra/steam_support_tickets_MEGA.json · الصفوف45,58,107,110,294\nلمحة عامة عن الشبكة\nnetwork-repositories.csv · raw_data.json · overlaps.csv · summary.txt (تم الاحتفاظ بمسارات المصادر التاريخية في ملف البيان)\n\nيسجل البيان مسارات المصادر، وأحجام البايتات، وتجزئات SHA-256، ومواقع السجلات المحددة. وتبقى اللقطات الأولية منفصلة عن تفسير التحقيق.\n\nتنزيل ملف البيان المصدر ↓",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam أدلة التنفيذ — سجلات الدعم وشبكة المطورين"
          },
          {
            "level": 2,
            "id": null,
            "text": "اقرأ الشكوى.يرجى إرفاق النص الأصلي."
          },
          {
            "level": 3,
            "id": null,
            "text": "Permanent sanction & closed appeals"
          },
          {
            "level": 4,
            "id": null,
            "text": "Permanently banned Steam account without a clear explanation, need help!"
          },
          {
            "level": 3,
            "id": null,
            "text": "Account recovery & a reported $10,000 loss"
          },
          {
            "level": 4,
            "id": null,
            "text": "Got $10k stollen from steam inventory due to steam' support fault."
          },
          {
            "level": 3,
            "id": null,
            "text": "A reported $500+ loss & template replies"
          },
          {
            "level": 4,
            "id": null,
            "text": "Funds stolen through steam market. Disappointed with Steam response.(or lackthereof)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam Guard & an item-restoration refusal"
          },
          {
            "level": 4,
            "id": null,
            "text": "Many people are losing item via clicking links where steam guard is enabled and steam support doesn't not restore items."
          },
          {
            "level": 3,
            "id": null,
            "text": "Selective enforcement & an unexplained ban"
          },
          {
            "level": 4,
            "id": null,
            "text": "🚨 Steam Bans Without Reason and Ignores Its Community — What’s Going On?"
          },
          {
            "level": 2,
            "id": null,
            "text": "البنية التحتية العامة.تم تسجيله على نطاق واسع."
          },
          {
            "level": 2,
            "id": null,
            "text": "تم إنشاؤه من الملفات التي جمعتها."
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/ar/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/ar/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/selected-support-records.json",
          "https://phishdestroy.io/steam_dossier/ar/investigation_part2.html#outsourcing-case",
          "https://www.reddit.com/r/ohnePixel/comments/1hahqx2/permanently_banned_steam_account_without_a_clear/",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://www.reddit.com/r/DotA2/comments/r55bd7/many_people_are_losing_item_via_clicking_links/",
          "https://www.reddit.com/r/SteamUncensored/comments/1kjt2fa/steam_bans_without_reason_and_ignores_its/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/network-repositories.csv",
          "https://github.com/alliedmodders/amxmodx",
          "https://github.com/alliedmodders/sourcemod",
          "https://github.com/DoctorMcKay/node-steam-user",
          "https://github.com/Facepunch/Facepunch.Steamworks",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://github.com/odota/core",
          "https://github.com/odota/dotaconstants",
          "https://github.com/odota/web",
          "https://github.com/splewis/get5",
          "https://github.com/SteamDatabase/FileDetectionRuleSets",
          "https://github.com/SteamRE/SteamKit",
          "https://github.com/ValveSoftware/dxvk",
          "https://github.com/ValveSoftware/GameNetworkingSockets",
          "https://github.com/ValveSoftware/gamescope",
          "https://github.com/ValveSoftware/Proton",
          "https://github.com/ValveSoftware/source-sdk-2013",
          "https://github.com/ValveSoftware/wine",
          "https://github.com/ValveSoftware/steam-devices",
          "https://github.com/ValveSoftware/steam-audio",
          "https://github.com/alliedmodders/metamod-source",
          "https://github.com/alliedmodders/sourcepawn",
          "https://github.com/ValveSoftware/Fossilize",
          "https://github.com/rlabrecque/Steamworks.NET",
          "https://github.com/ModDota/moddota.github.io",
          "https://github.com/odota/parser",
          "https://github.com/ValveSoftware/steam-for-linux",
          "https://github.com/SteamRE/DepotDownloader",
          "https://github.com/JustArchiNET/ASF-ui",
          "https://github.com/advancedfx/advancedfx",
          "https://github.com/alliedmodders/ambuild",
          "https://github.com/SteamDatabase/BrowserExtension",
          "https://github.com/odota/mobile",
          "https://github.com/ValvePython/steam",
          "https://github.com/skadistats/clarity",
          "https://github.com/SteamRE/open-steamworks",
          "https://github.com/ValveSoftware/Source-1-Games",
          "https://github.com/alliedmodders/hl2sdk",
          "https://github.com/SteamDatabase/steamdb.info-issues",
          "https://github.com/CSGOFloat/inspect",
          "https://github.com/ValveSoftware/SteamOS",
          "https://github.com/alliedmodders/source2mod",
          "https://github.com/smiley/steamapi",
          "https://github.com/SteamDatabase/GameTracking",
          "https://github.com/ValveSoftware/counter-strike_rules_and_regs",
          "https://github.com/ValveSoftware/openvr",
          "https://github.com/SteamDatabase/easy-markdown-editor",
          "https://github.com/ValveSoftware/Dota-2",
          "https://github.com/ValveSoftware/Dota2-Gameplay",
          "https://github.com/JustArchiNET/ArchiBot",
          "https://github.com/ztizzlegaming/CSGOWinBig",
          "https://github.com/JustArchiNET/mantis.justarchi.net",
          "https://github.com/odota/node-steam-user",
          "https://github.com/ModDota/TypeScriptAddonTemplate",
          "https://github.com/ValvePython/vdf",
          "https://github.com/alliedmodders/amtl",
          "https://github.com/ValvePython/dota2",
          "https://github.com/alliedmodders/stripper-source",
          "https://github.com/Allyans3/steam-market-api-v2",
          "https://github.com/ModDota/dota-tutorial",
          "https://github.com/odota/blog",
          "https://github.com/OpsecGuy/BetterGo",
          "https://github.com/pxvr-official/1",
          "https://github.com/Revadike/InternalSteamWebAPI",
          "https://github.com/JoeSzymkowiczFiveM/qb-lootcrate",
          "https://github.com/AbrarKL/MyRoulette.XYZ",
          "https://github.com/JustArchiNET/ASF-WebConfigGenerator",
          "https://github.com/ModDota/dota-data",
          "https://github.com/ModDota/TypeScriptDeclarations",
          "https://github.com/ModDota/API",
          "https://github.com/alliedmodders/cssdm",
          "https://github.com/SteamDatabase/steamstat.us",
          "https://github.com/c0deina/csgojackpotV2",
          "https://github.com/ValvePython/steamctl",
          "https://github.com/ValvePython/csgo",
          "https://github.com/BeepIsla/csgo-crash-exploit",
          "https://github.com/ValvePython/vpk",
          "https://github.com/alliedmodders/SM-SteamWorks",
          "https://github.com/SteamRE/Steam4NET",
          "https://github.com/alliedmodders/hl2sdk-manifests",
          "https://github.com/JustArchiNET/ASF-PluginTemplate",
          "https://github.com/ModDota/Dota2AIFramework",
          "https://github.com/Shkyyl/KeyChamp",
          "https://github.com/SteamDatabase/SteamMonitor",
          "https://github.com/Baterka/cslore.com",
          "https://github.com/SteamDatabase/SteamTokenDumper",
          "https://github.com/monoblocker/roulette",
          "https://github.com/zsith/launcher.user.js",
          "https://github.com/LincolnIT/CSGODouble-bot-automated",
          "https://github.com/vladpuz/steam-market",
          "https://github.com/mcgrizzz/Cstrike.bet",
          "https://github.com/odota/underlords-web",
          "https://github.com/SteamDatabase/SteamToTwitter",
          "https://github.com/ModDota/AbilityLuaSpellLibrary",
          "https://github.com/alvinl/bitskins",
          "https://github.com/b1naryth1ef/steamy",
          "https://github.com/kratos1812/Case-Opening",
          "https://github.com/odota/docs",
          "https://github.com/SteamDatabase/steam-advanced-access-fetch-players",
          "https://github.com/TheRioMiner/CsgoBetterExternalRaytrace",
          "https://github.com/alliedmodders/hl2sdk-mock",
          "https://github.com/christophersu/PySteamMarket",
          "https://github.com/Extremelyd1/Strat-Roulette",
          "https://github.com/giovanni-orciuolo/double-sdk",
          "https://github.com/JustArchiNET/Madness",
          "https://github.com/ModDota/TypescriptPanoramaDeclarations",
          "https://github.com/odota/rapier",
          "https://github.com/Vozn1akHero/CSGOCaseOpeningSimulator",
          "https://github.com/autarc/steam-store",
          "https://github.com/BETTING-CODE/awesome-esports-sites",
          "https://github.com/jonteohr/Better-Warden",
          "https://github.com/Ludzikk/CSGO-Gambling-Site",
          "https://github.com/ModDota/find-steam-app",
          "https://github.com/mprey/csgocact.us",
          "https://github.com/nezu-cc/ServerCrasher",
          "https://github.com/odota/testfiles",
          "https://github.com/odota/underlordsconstants",
          "https://github.com/SnaBe/node-steam-market-fetcher",
          "https://github.com/SteamDatabase/.github",
          "https://github.com/wolfcon/RIP-HLTV-BET",
          "https://github.com/alliedmodders/blaster.net",
          "https://github.com/catears124/CS2-Price-API",
          "https://github.com/ialakey/caseforge",
          "https://github.com/Ilusion9/csgo-fix-mapchange-crash-sm",
          "https://github.com/ismail0234/Benson-Map-Crash-Fixer",
          "https://github.com/jaxwilko/steam-market-api",
          "https://github.com/JustArchiNET/ArchiTag",
          "https://github.com/ModDota/DotaUI",
          "https://github.com/node-steam/market-pricing",
          "https://github.com/odota/media",
          "https://github.com/SergeyIvanovDevelop/Crypto-Steam-Platform",
          "https://github.com/Aareksio/csgodouble-floatchecker",
          "https://github.com/chinm4/CSGOdrop",
          "https://github.com/Cruze03/CSGO-Case-Opening-Prank",
          "https://github.com/Dhruva-Kapadia/CSGOTrollGG",
          "https://github.com/ErhanCSGO/CSGOPolygon-prediction",
          "https://github.com/Ev-Hoang/Bedrock-Chest-Case-Opening",
          "https://github.com/jmjp/csgo-roulette",
          "https://github.com/JustArchiNET/ArchiCrowdin",
          "https://github.com/LeonSK/WearMarketInspector",
          "https://github.com/maximgeerinck/csgo-gamble",
          "https://github.com/ModDota/BugTracker",
          "https://github.com/plwp/mma-betting",
          "https://github.com/Southsideswag16/Csgo-Gambling-Site",
          "https://github.com/tacyarg/csgofiesta-frontend-react",
          "https://github.com/Velorasse/Mutah-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-csmoney-csgoskins",
          "https://github.com/alliedmodders/am-github-artifact-webhook",
          "https://github.com/charamza/roulette",
          "https://github.com/Cruze03/CSGO-PugSetup-RoundRestore",
          "https://github.com/csgorol/CSGO-ROLL-Crash-Predictor",
          "https://github.com/FoxSerito/FOXWORLD_plugin_DoubleJump_CSGO",
          "https://github.com/hkehayovmoonbiz/CS2-Casino-Full-Source-Code",
          "https://github.com/JustZakary/steamstoreapi",
          "https://github.com/jzimr/steam-market-api",
          "https://github.com/Momohime/CSGO.Network-Jackpot-Coinflip",
          "https://github.com/nnjjswat/moneybot",
          "https://github.com/odota/carry",
          "https://github.com/odota/PublicMatchDataBot",
          "https://github.com/Orillio/CSGOBet.com",
          "https://github.com/ripexz/csgo-bet-alert",
          "https://github.com/rrpvm/lumen_sense-beta-deprecated-",
          "https://github.com/Ruthless222/csgoscore",
          "https://github.com/tfburns/CSGO-cases-PL",
          "https://github.com/TomDra/CSGO-Case-Data-Analysis",
          "https://github.com/ValvePython/dota2-wrappers",
          "https://github.com/ValvePython/teamfortress2-closed-captions",
          "https://github.com/VistaNetGTX/Cstrike.bet-",
          "https://github.com/wafflas/csgo-case-opening-simulator",
          "https://github.com/Admiral-Enigma/Le_Coinflip",
          "https://github.com/adryeljuliao/roulette-csgo",
          "https://github.com/AndreuTheG/csgo-coinflip-web",
          "https://github.com/asmilen/csgoDouble",
          "https://github.com/b1naryth1ef/csgofort",
          "https://github.com/Baterka/PrivateSteamBettingWebsite2024",
          "https://github.com/blackcaer/SteamTradeHandler",
          "https://github.com/BTheCoderr/theRounders",
          "https://github.com/CallumHemsley/KazeBot",
          "https://github.com/chrisjpm/CSGOJackpotTemplate",
          "https://github.com/colinsenner/valve-bug-bounty",
          "https://github.com/coryypeters/nrl-odds-intelligence-pipeline",
          "https://github.com/deissh/dev-csgoduo",
          "https://github.com/dom1torii/even-better-font-manager",
          "https://github.com/DONnicov/CSGO-crash-black-screen-",
          "https://github.com/DoubleBoters/CsgoDouble",
          "https://github.com/downarowiczd/DoubleBot",
          "https://github.com/ErayBahar/steammarketscraper",
          "https://github.com/fairydarkness/SteamwebmailAPI",
          "https://github.com/FAQU2/CSGO-Coinflip-MyJailShop",
          "https://github.com/FlamesONE/csgo-case-opening",
          "https://github.com/FunnyRain/csgorun-crash-watch",
          "https://github.com/geohdgio/Venatus-Autenticator",
          "https://github.com/hakanstarlord/steam-bot",
          "https://github.com/HvH-gg/CSGO-Item-CrashFix",
          "https://github.com/HvH-gg/CSGO-NetMsg-CrashFix",
          "https://github.com/isybycnsmam/SteamLibrary",
          "https://github.com/ItsTangerine/SteamApis.Net",
          "https://github.com/JustArchiNET/JustArchi.net",
          "https://github.com/kiri-osint/CS2-Info-Hub-Bot",
          "https://github.com/Koshkaj/monte",
          "https://github.com/madsab/CaseOpening",
          "https://github.com/man90es/steamcardexchange-api",
          "https://github.com/MattPua/steam-unofficial-docs",
          "https://github.com/Metallist1/Portfolio.CsgoWinGambleProject",
          "https://github.com/mikebobadilla/csgo-jackpot",
          "https://github.com/mikebobadilla/meteor-csgojackpot",
          "https://github.com/ModDota/D2VDump",
          "https://github.com/ModDota/DotaTracking",
          "https://github.com/ModDota/eslint-config",
          "https://github.com/mr-codinglv/Casino-script",
          "https://github.com/MrKeelik/MrKeel",
          "https://github.com/noahlatzel/CSGORollHelper",
          "https://github.com/oddsgpt/oddsgpt-market-intelligence",
          "https://github.com/oEXU/csgo-server-crasher",
          "https://github.com/PrdTTony/CSGO-Roulette",
          "https://github.com/r-adamski/csgo-jackpot",
          "https://github.com/Sahotallo/Turan-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-Skinbaron-hellcase",
          "https://github.com/samuelcsouza/steam-marketplace-api",
          "https://github.com/SKINSTRACK/CS2-Price-API",
          "https://github.com/snmtriet/CSGO-Casino-Full-Source-Code",
          "https://github.com/SteamRE/homebrew-tools",
          "https://github.com/SteamRE/opensteamworks.org",
          "https://github.com/TheQuack45/CsgoCaseOpenProgram",
          "https://github.com/TLClassless/StratRouletteCSGO",
          "https://github.com/tomasoom/csgoCaseOpening",
          "https://github.com/vitaliy-evsyukov/steamgifts-autobet-bookmarklet",
          "https://github.com/XpravdaX/RouletteCSGO",
          "https://github.com/YuiKasumii/steam_api_unofficial",
          "https://github.com/Zexuz/Steam-Betting",
          "https://github.com/ANK-RULZZ/steam-jackpot-site",
          "https://github.com/asmilen/CsgoDoubleVS",
          "https://github.com/CORNOODOSADAS/CSGOWeed",
          "https://github.com/CSGOApple/csgoapple",
          "https://github.com/CSGOFAST/csgofast-api",
          "https://github.com/Donakall/csgoDoublebot",
          "https://github.com/fedor-selivanov/csgo-fast-roulette",
          "https://github.com/foldageros/csgod",
          "https://github.com/gmod-gambling/gmod-gambling",
          "https://github.com/ierome/CSGOBoss-BackEnd",
          "https://github.com/jamienp1/CSGODOUBLE-BOT-AUTO",
          "https://github.com/JEYONER/CSGOTOXIC",
          "https://github.com/kalrish/csgo-jackpot",
          "https://github.com/krys12345/roulettee",
          "https://github.com/LilDuggiMuffi/CSGODouble-Working-Bot",
          "https://github.com/LyricLy/Steam2Proton",
          "https://github.com/M0NsTeR77/csgo-roulette",
          "https://github.com/ozanhalis/Hi",
          "https://github.com/scoobertus/CSGO-DoubleBot",
          "https://github.com/Tradeal/CSGO-Jackpot-Bot",
          "https://github.com/ValvePython/artifact",
          "https://github.com/Vampire/CSGO-Roulette-Bot",
          "https://github.com/vdemans/csgo-roulette",
          "https://github.com/VocoreVideo/CSGODungeon-",
          "https://github.com/wayz-dev/csgofloat",
          "https://phishdestroy.io/steam_dossier/output_steam_network/raw_data.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/enforcement-source-manifest.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ar/steam_enforcement_evidence.content.json",
      "export_json_sha256": "7a5e964d94754227e138a9affca7cf7ff943c02f1bde9a53c510e93344a60453"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ar/steam_evidence_archive.html",
      "language": "ar",
      "title": "تحقق من المصادر — ملف «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/ar/steam_evidence_archive",
      "source_html_sha256": "8e4cf176fafa718ca38a5016784a38e5910f9b02fefd24b02d970e28f718e8f2",
      "exported_at": "2026-09-29T00:20:29.582Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "steam_evidence_archive.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ar/steam_evidence_archive.pdf?v=print-20260929-v5",
        "sha256": "78a094bf48935db2997f587db4b0af4c8a61dad1506a025012d7a421ec8c832b",
        "bytes": 74256,
        "pages": 3
      },
      "integrity": {
        "signed_object": "steam_evidence_archive.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "steam_evidence_archive.content.json.asc",
        "digest_file": "steam_evidence_archive.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify steam_evidence_archive.content.json.asc steam_evidence_archive.content.json",
          "sha256sum -c steam_evidence_archive.content.json.sha256"
        ]
      },
      "content": {
        "text": "مواد التحقيق / جمع المصادر 002\nSteam أرشيف الأدلة — السجلات المستمدة من موقع «16,319»\n\nكل مطالبة. العودة إلى المصدر.\n\nما يثبته هذا القسم\n\nيقوم هذا الأرشيف الجنائي بفهرسة سجلات المصادر الأولية الخاصة بـ «16,319» — والتي تشمل وثائق مجتمع مطوري «Valve»، والمشكلات العامة على «GitHub»، والشكاوى المؤكدة على «Trustpilot»، وتقارير المنتديات المؤرشفة — باستخدام التجزئات التشفيرية وسجلات المنشأ. ويوفر قاعدة أدلة قابلة للتدقيق تثبت وجود ثغرات أمنية قابلة للتكرار في المنصة، وإلغاءات غير موثقة لـ «API»، وشكاوى مستمرة من المستهلكين بشأن الحسابات المخترقة.\n\n← العودة إلى ملخص الإدارة التنفيذية\n\nابحث عن السجل الذي تستند إليه الادعاءات. قم بالتصفية حسب المصدر، وافتح النص الكامل، واتبع الرابط الأصلي. قد تتداخل صفوف المصادر؛ فالسجل لا يعني بالضرورة أن الحادثة قد تم التحقق منها.\n\nالعودة إلى التحقيق ↗\n354TRUSTPILOT / صفوف المصادر\n208ريديت / صفوف المصادر\n705GITHUB / أسطر المصدر\n15,302ملف CSV الرئيسي / صفوف المصدر\n16,319 السجلات — تصنيف حسب نوع المنصة\n\nمصدر فئة ويكي (سجلات 7,620 · 46.7%): تم استخراج البيانات من مجتمع مطوري «Valve» (developer.valvesoftware.com)، ووثائق SteamDB/الأسئلة الشائعة، ومواقع الويكي الخاصة بمجتمعات الألعاب (مواقع ويكي Liquipedia CS/Dota وFandom Steam) عبر لقطات WARC الآلية ونقاط نهاية MediaWiki API خلال الفترة الممتدة من أغسطس 2024 إلى سبتمبر 2026.. تم دمج جميع إدخالات 7,620 بالكامل في ملف التصدير الرئيسي بتنسيق CSV (TOTAL_VALVE_SCANDALS_MASTER_DB.csv).\n\nويكي\n7,620\nReddit\n5,635\nGitHub\n2,395\nTrustpilot\n393\nالويب\n276\n9,116 تحتوي سجلات موقع «16,319» (55.8%) على إشارات إلى Steam / Valve\n\nتم إنشاء هذا الأرشيف القابل للبحث على 2026-09-17 من عمليات التصدير المصدر المذكورة أعلاه. أما عملية التصدير الرئيسية المنفصلة لصفوف «40,448-» المستخدمة في أجزاء أخرى من الملف، فهي ذات نطاق مختلف. انظر إنشاء ملف البيان بالنسبة لإحصاءات هذا الأرشيف؛ قد تتداخل السجلات ولا تمثل حوادث فردية.\n\nمنصة المصدر\nجمع المصادر\nSteam / عدد مرات ذكر Valve\nمطابقة النص أو مستودع «Valve»نص مفقود / محذوف\n16,569 صفوف المصدر\n16,319 سجلات منفصلة\n249 تم دمج الصفوف المكررة\n1 الصف مستبعد\nعرض الملفات الأصلية ↘\n★TRUSTPILOT2015-10-16#1RATING 1/5\n\nSteam is the biggest PC gaming platform without a doubt. A power which could be abused but Steam for the most part doesn't. Overall a definite download for any moden digital age PC gamer. It mu... See more\n\nMA · 7 source copies\n★TRUSTPILOT2021-06-18#2RATING 1/5\n\nThey scam people for money, dont believe me? Read this Source: Steam Subscribers/User Agreement NO GUARANTEES TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, NEITHER VALVE NOR ITS AFFILIA... See more\n\nWF · 7 source copies\n★TRUSTPILOT2016-10-28#3RATING 1/5\n\nSupport on site is terrible. Refunds not happend yet, despite games not working. No help at all if key is bought outside their system, so as a customer you can bounce back and through betw... See more\n\nPE · 7 source copies\n★TRUSTPILOT2021-09-27#4RATING 1/5\n\nThey are an amazing company!! My boyfriend paid for and downloaded a game without realizing it wasn’t the version he wanted. When he reached out, they gave him a full refund and responded in the same... See more\n\nVH · 7 source copies\n★TRUSTPILOT2026-07-20#5RATING 1/5\n\nI’ve used Steam for years, but lately, their sales have really lost their edge. I was hoping to score some solid discounts, but many games still feel overpriced, even during sales. Plus, the support response times can be frustratingly slow when issues arise.\n\nCR\n★TRUSTPILOT2025-12-10#6RATING 1/5\n\nI new here , but all my firends had great experience with this platform . They can make money\n\nZeinab Nematollahi\n★TRUSTPILOT2025-11-18#7RATING 1/5TEXT UNAVAILABLE\n\nNo text was included in the source record.\n\nEM\n★TRUSTPILOT2025-10-21#8RATING 1/5\n\nusing steam for over a decade and i have no words how good the platform is. some friends recommended it to me back in 2015 when we wanted to play csgo together and since then im loggin on it on a daily basis to check new games\n\nTrustpilot\n★TRUSTPILOT2025-05-09#9RATING 1/5\n\nSupport are never able to help you and only able to redicrect you to public linkBreaking there own TOSNot able to provider a refundNot able to provide a safe place for gamingBase on the game you play you can get scam.\n\nSym Link · 7 source copies\n★TRUSTPILOT2025-05-09#10RATING 1/5TEXT UNAVAILABLE\n\nNo text was included in the source record.\n\nHearnius\n★TRUSTPILOT2024-12-30#11RATING 1/5\n\nThis company allowed a single phishing scammer 76561199443342045 in 100's of its user community chat rooms \"Steam Chat\" the whole week of Winter Sales, 12-23-2024 - 2025 to spam spaceintrader a scam phishing website.Don't support Valve & Steam that support sca…\n\nFR · 7 source copies\n★TRUSTPILOT2024-11-15#12RATING 1/5\n\nVery realiable! Ive never had an issue over the 11 years ive had steam.\n\nJM\nالإصدار وملفاته المصدرية\n\nيجمع هذا الأرشيف الصفوف المكررة من 249 ويستبعد صفًا واحدًا من المدخلات الموجودة في 16,569، ليتبقى 16,319 سجلًا فريدًا. قد يصف أحد السجلات حدثًا سبق أن تناوله سجل آخر. يشمل البحث العناوين والمؤلفين وتصنيفات المصادر والمقتطفات المعروضة؛ ويتم فتح النص الكامل المحفوظ مع كل سجل.\n\nتنزيل أربعة ملفات مصدر ↓عدد الملفات وتجزئات SHA-256 ↗قائمة التجميع الأصلية ↗\n\nتحتوي الحزمة على الصادرات المستردة التي تتطابق مع عدد الصفوف في الإصدار ومسارات JSON الثلاثة المسجلة فيه. لم يسجل الإصدار الأصلي تجزئات المدخلات أو مسار ملف CSV الرئيسي؛ ويوثق البيان المصاحب الملفات المستردة والمقارنة مع الفهرس المنشور.\n\nTrustpilot · steam_support_reviews.json354 الصفوف · تصدير JSON\nReddit · reddit_censored_forensics.json208 الصفوف · تصدير JSON\nGitHub · valve_ignored_bugs.json705 الصفوف · تصدير بتنسيق JSON؛ اسم الملف هو تسمية المجمع\nالرئيسي · TOTAL_VALVE_SCANDALS_MASTER_DB.csv15,302 الصفوف · تصدير ملف CSV المستخدم للمقارنة\nقوائم قضايا المحكمة · UNSEALED_EXHIBITS_AND_AML_DOSSIER.mdWolfire ضد شركة «Valve» (الرسائل الإلكترونية التي رُفعت عنها السرية)، إفادات غابي نيويل، اعتراف «Oct2019» بانتهاك قوانين مكافحة غسل الأموال\nحقائق أساسية · FACTS_AND_CITATIONS_DATABASE.md1,638 مراجع منفصلة تم التحقق منها عبر مجالات مكافحة الاحتكار والأمن في موقع 35\nأرشيف الدعم · support_canned_refusals.html1,505 سجلات التذاكر · 137 لقطات شاشة محفوظة · البحث الفوري المباشر\nحقول السجلات، والنصوص الناقصة، وعمليات التصدير المتداخلة\n\nيتم استنساخ التواريخ والتقييمات والفئات وحالات المنشورات من الصدريات المصدرية. ويظل الرابط المفقود مفقودًا. ولا تحدد علامات \"[تمت إزالته]\" أو \"[تم حذفه]\" هوية الشخص الذي أزال المنشور أو سبب إزالته. ويُعد مرشح Steam / Valve مرشحًا يعتمد على مطابقة النص، وليس تقييمًا لمدى الصلة.\n\nتقوم خيار «تصدير المطابقات» بمطابقة إدخالات الفهرس مع المقتطفات؛ أما خيار «تنزيل السجل» فيتضمن النص الكامل المحفوظ. الخيار المنفصل 40,448-رئيس الصف في ملف CSV و 1,690-الصف GitHub CSV ما يهم في هذا الإصدار هو حجم الصادرات بشكل عام، وليس عدد المصادر.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam أرشيف الأدلة — السجلات المستمدة من موقع «16,319»"
          },
          {
            "level": 2,
            "id": null,
            "text": "منصة المصدر"
          },
          {
            "level": 2,
            "id": null,
            "text": "الإصدار وملفاته المصدرية"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/ar/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/ar/",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/TOTAL_VALVE_SCANDALS_MASTER_DB.csv",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive_manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive-inputs.zip",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive-inputs-manifest.json",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/unsealed_legal_and_aml/UNSEALED_EXHIBITS_AND_AML_DOSSIER.md",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/forensic_facts_1000/FACTS_AND_CITATIONS_DATABASE.md",
          "https://phishdestroy.io/steam_dossier/ar/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/github_valve_unpatched_bugs.csv"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ar/steam_evidence_archive.content.json",
      "export_json_sha256": "c913065a6998af828d5348983585a2d9d15cf1bafd5660b7c379fc980cfcfe65"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ar/support_canned_refusals.html",
      "language": "ar",
      "title": "Steam أرشيف حالات رفض الدعم والردود الجاهزة — ملف «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/ar/support_canned_refusals",
      "source_html_sha256": "b156b6ce4c374d77477a0ad493ba30798b809062f8ef9aa5d6290e48ffe4481c",
      "exported_at": "2026-09-29T00:20:29.627Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "support_canned_refusals.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ar/support_canned_refusals.pdf?v=print-20260929-v5",
        "sha256": "c5c073de448a9bc0be088f065da5066d5f465fe1610d622af47960bdd07e547b",
        "bytes": 79419,
        "pages": 2
      },
      "integrity": {
        "signed_object": "support_canned_refusals.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "support_canned_refusals.content.json.asc",
        "digest_file": "support_canned_refusals.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify support_canned_refusals.content.json.asc support_canned_refusals.content.json",
          "sha256sum -c support_canned_refusals.content.json.sha256"
        ]
      },
      "content": {
        "text": "ما يثبته هذا القسم\n\nيوثق هذا المستودع 137 لقطات الشاشة الأولية المحفوظة و1,505 طلبات الاستئناف المدققة المقدمة من الضحايا والتي توضح بالتفصيل Valve طريقة المعالجة الآلية لتذاكر الدعم. ويثبت ذلك أنه عندما تتعرض الحسابات للاختراق عبر إعادة التوجيه عبر OpenID أو إنشاء مفاتيح API غير مصرح بها، فإن Steam Support تستخدم بشكل منهجي ردود رفض جاهزة وموحدة دون إجراء أي تحقيق فني. ومن خلال الرفض القاطع لاستعادة العناصر أو الكشف عن سجلات التدقيق، تحوّل المنصة المسؤولية الكاملة عن عيوب المصادقة الهيكلية إلى أصحاب الحسابات المخترقة.\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\nجميع لقطات الشاشة هي لقطات تم التقاطها بواسطة أطراف ثالثة. تبقى حقوق النشر والمحتوى ملكًا لمؤلفيها ومنصاتها المعنية (مستخدمو Reddit، ومؤلفو مجتمع Steam، ومراجعو Trustpilot، ومنشئو المحتوى على X، ومنشئو المحتوى على YouTube). وقد تم إعادة نشرها لأغراض التعريف والتغطية الصحفية التي تخدم المصلحة العامة فقط؛ ولا يُدعى إلى ملكيتها. ويحتوي كل دليل على رابط إلى مصدره الأصلي.\n\nFigures reported on the source page\nMeasure\tReported value\tScope\nالسجلات الموثقة\t1505\tالطعون المؤكدة للضحايا ومواضيع المخالفات\nلقطات شاشة محفوظة\t137\tيتم تخزين صور التذاكر عالية الدقة محليًّا\nمعدل الاسترداد\t0.0%\tإصدار أوامر إعادة النظر في قضايا اختطاف الطائرات التي وقعت في عامAPI\nتكرار القوالب\t100%\tإعادة استخدام النصوص الحرفية بين الموظفين (إيليا، روجر، مافريك)\nالأدلة الجنائية: الركائز الثلاث الأساسية لرفض تقديم الدعم\nالركيزة 01 · القبولالمستند R-014\nاعتراف روجر: تأكيد هجوم «API» من نوع MitM\n\nفي الرد على التذكرة رقم1cp582i، Steam، يعترف موظف الدعم «روجر» كتابةً بأن المهاجمين يلغون الصفقات الشرعية عبر API ويستبدلونها بروبوتات مقلدة في غضون أجزاء من الألف من الثانية، لكنه يرفض استعادة العناصر ويطلب من الضحية اللجوء إلى «فني كمبيوتر محلي».\n\nالاطلاع على خطاب القبول المكتوب ↗\nالركيزة 02 · التصعيدالمستند R-012\n7-التداول اليومي: الاحتفاظ بالمركز دون اتخاذ أي إجراء\n\nقدمت إحدى الضحايا رقم SteamID64 الخاص بحسابات المخترق خلال فترة تعليق التداول اليومي في لعبة «7-». ورفض موظفو الدعم «أرتيم» و«إيليا» تجميد العناصر المسروقة، متذرعين بندرة العناصر الافتراضية، وأغلقوا التذكرة باستخدام نموذج آلي.\n\nالاطلاع على كشف الدرجات لعدة موظفين ↗\nالركيزة 03 · السياسةالمستند R-002\nندرة السوق مقابل حقوق الملكية\n\nتنص «سياسة استعادة العناصر» الرسمية الخاصة بـ Valve صراحةً على أنه لا يتم إعادة العناصر لأن استعادتها من شأنها «تقليل الندرة وتضخيم الاقتصاد، مما يؤدي إلى انخفاض قيمة العناصر في سوق المجتمع».\n\nلقطة شاشة لسياسة الفحص ↗\nالنشأة التاريخية · 22 مارس 2018 إلى 2026\nالمرفق H-003 · 8-: سطح الهجوم الذي لم يتم إصلاحه منذ عام\nأقدم حالة مسجلة لاستبدال السلع التجارية (22 مارس 2018)\n\nقبل أسبوع واحد بالضبط من قيام موقع «Valve» بفرض فترة التجميد المثيرة للجدل في التداول اليومي «7-» على عناصر لعبة «Counter-Strike»، اكتشف مجتمع المتداولين أول حالات حقيقية لـ Steam استغلال ثغرة إعادة التوجيه في موقع API. قام المهاجمون باختطاف جلسات الويب لإنشاء مفتاح غير مصرح به لـ API على steamcommunity.com/dev/apikey دون الحاجة إلى هاتف محمول 2تأكيد من الاتحاد الإنجليزي لكرة القدم (FA)، مما يتيح للروبوتات إلغاء الصفقات وتبادلها في الوقت الفعلي.\n\nتحذير من الحملة العامة \"2018\" لشهر مارس: \"يمكن للمحتالين اكتشاف عرض التبادل هذا تلقائيًا ورفضه من حسابك، لأنهم يمتلكون مفتاحك الخاص بـ Steam API. وسيقوم روبوت الاحتيال الآن بإرسال عرض تبادل إليك لنفس الأسطح... ولن تلاحظ أي فرق!\"\nمسار الأدلة التاريخية\n22 مارس 2018: أول عملية تبديل موثقة لـAPI\n2019: الدعم يعمل على توحيد إجراءات التصدي لـ«البرامج الضارة»\n2020: تعزيز أمان البرنامج النصي «إغلاق طلب المساعدة»\n2022–2026: أتمتة عمليات التصيد الاحتيالي باستخدام BitB وQR\nافتح موضوع Reddit الأصلي الخاص بـ «2018» ↗\nPrimary sources\n\n137 gallery cards refer to 78 distinct primary URLs. Images and repeated exhibit captions are omitted from this reading edition.\n\nFull visual archive and original captures",
        "headings": [
          {
            "level": 2,
            "id": null,
            "text": "Figures reported on the source page"
          },
          {
            "level": 2,
            "id": null,
            "text": "الأدلة الجنائية: الركائز الثلاث الأساسية لرفض تقديم الدعم"
          },
          {
            "level": 3,
            "id": null,
            "text": "اعتراف روجر: تأكيد هجوم «API» من نوع MitM"
          },
          {
            "level": 3,
            "id": null,
            "text": "7-التداول اليومي: الاحتفاظ بالمركز دون اتخاذ أي إجراء"
          },
          {
            "level": 3,
            "id": null,
            "text": "ندرة السوق مقابل حقوق الملكية"
          },
          {
            "level": 3,
            "id": null,
            "text": "أقدم حالة مسجلة لاستبدال السلع التجارية (22 مارس 2018)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Primary sources"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/ar/#proxy-bypass-explainer",
          "https://www.reddit.com/r/csgo/comments/1cp582i/i_got_api_scammed_what_do_i_do_now/",
          "https://www.reddit.com/r/DotA2/comments/1e5ovy4/my_account_was_hacked_and_steam_support_refuse/",
          "https://www.reddit.com/r/Steam/comments/3b2abd/steam_will_no_longer_restore_scammed_items_item/",
          "https://www.reddit.com/r/GlobalOffensiveTrade/comments/863tk1/psa_urgent_huge_scam_happening_read_here_how_to",
          "https://phishdestroy.io/steam_dossier/ar/support_canned_refusals#gallery-grid"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ar/support_canned_refusals.content.json",
      "export_json_sha256": "febd3d76137f6221008fe3c674a5383263767a56f54e6ab83ded28367ade19f5"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ar/valve_scandals_registry.html",
      "language": "ar",
      "title": "Valve سجل الفضائح — ملف «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/ar/valve_scandals_registry",
      "source_html_sha256": "668a0ec694268122a75f30544c94cf1711c06e6a47acf16d34e57a3f9b1d5539",
      "exported_at": "2026-09-29T00:20:33.988Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "valve_scandals_registry.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ar/valve_scandals_registry.pdf?v=print-20260929-v5",
        "sha256": "c55d3bd2199e24afc96bade7666d54d5c7a3d58cfe70e41c885aa63c26ec92d8",
        "bytes": 77858,
        "pages": 6
      },
      "integrity": {
        "signed_object": "valve_scandals_registry.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "valve_scandals_registry.content.json.asc",
        "digest_file": "valve_scandals_registry.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify valve_scandals_registry.content.json.asc valve_scandals_registry.content.json",
          "sha256sum -c valve_scandals_registry.content.json.sha256"
        ]
      },
      "content": {
        "text": "أرشيف الفضائح الرئيسي\nValve السجل الرئيسي للفضائح — 160 الحوادث الموثقة\nالسجلات المصدرية (الخام): 11,768\n\nتم الإبلاغ عنها. تم تحديد مصدرها. لا تزال قيد التحقيق.\n\nما يثبته هذا القسم\n\nيجمع هذا السجل الرئيسي 160 السجلات الأولية التي تم التحقق منها بشكل مستقل، والتي توضح بالتفصيل العيوب المستمرة في المنصة، وتقارير المجتمع التي تم حذفها، وحالات الفشل في دعم المستهلكين التي لم يتم معالجتها عبر منظومة Valve. ويشمل هذا السجل ملفات النزاعات التي تم التحقق منها على موقع Trustpilot، وتذاكر المشكلات الأمنية المؤرشفة على موقع GitHub، والإجراءات التي اتخذتها الهيئات التنظيمية، مما يثبت وجود خلل نظامي متكرر في استعادة الحسابات وحل نزاعات العملاء.\n\n← العودة إلى ملخص الإدارة التنفيذية\n\n160 السجلات المجمعة: عملية دعم تم تقييمها من قِبل المستخدمين، والمواضيع التي لم تعد ظاهرة، وعيوب المنصة التي تم الإبلاغ عنها وتركت دون معالجة، والحوادث التي اضطر موقع Valve بالفعل إلى تحمل مسؤوليتها. لا شيء مما ورد هنا يمثل تقييمنا — فكل سطر يحمل مصدره الأصلي. افتح أحدها واقرأها بنفسك.\n\nسجلات المصدر\n11,768\nفي جميع الفئات\nعيوب المنصة\n3,372\nالعيوب في المنصة التي أبلغ عنها أفراد المجتمع\nالمواضيع المحجوبة\n109\nالمشاركات التي حذفها المشرف على موقع Reddit\nالشكاوى المتعلقة بالدعم\n471\nشكاوى مُثبتة على موقع Trustpilot\nجدوى التنفيذ\nحظر نطاقات مضيف المصادقة\n\nيُعد حجب مضيفي المصادقة عبر OpenID على مستوى النطاق أمرًا سهل التنفيذ من الناحية التقنية: فبمجرد حظر مورد ما من إعادة التوجيه لتسجيل الدخول عبر Steam، يمكن تصفية نطاقات الأطراف الثالثة التي تعمل كوكلاء مصادقة لهذا المورد نفسه باستخدام نفس مجموعة القواعد. وترد مناقشة مفصلة حول جدوى التنفيذ في الملف الرئيسي.\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\nانظر جدوى التنفيذ في الملف →\nالفئة: شكاوى دعم Trustpilot (الحالات السلبية التي تمت تصفيتها)176 السجلات المطابقة للمصدر · تم إخفاء التكرارات\nConsumer Complaint2026-07-20\nAuthor: C***\n\nI’ve used Steam for years, but lately, their sales have really lost their edge. I was hoping to score some solid discounts, but many games still feel overpriced, even during sales. Plus, the support response times can be frustratingly slow when issues arise.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2026-07-20\nConsumer Complaint2025-05-09\nAuthor: S*** L***\n\nSupport are never able to help you and only able to redicrect you to public linkBreaking there own TOSNot able to provider a refundNot able to provide a safe place for gamingBase on the game you play you can get scam.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2025-05-09\nConsumer Complaint2024-12-30\nAuthor: F***\n\nThis company allowed a single phishing scammer 7656…2045 in 100's of its user community chat rooms \"Steam Chat\" the whole week of Winter Sales, 12-23-2024 - 2025 to spam spaceintrader a scam phishing website.Don't support Valve & Steam that support scams. Don't give your log in credentials to account hijacking scammers. This company also allows engagements of commercial advertising / spam for gambling in violation of its own Rules and Guidelines / Online Conduct. 7656…5023 proof - groups/deskinsfans key drop advertising, thanks TannerfromKD and Valve!*\"The Consumer Review Fairness Act (CRFA) protects people’s ability to share their honest opinions about a business’s products, services, or conduct, in any forum, including social media. The law protects a broad variety of honest consumer assessments, including online reviews, social media posts, uploaded photos, videos, etc. And it doesn’t just cover product reviews. It also applies to consumer evaluations of a company\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2024-12-30\nConsumer Complaint2024-07-31\nAuthor: A***\n\nhorrible company.randomly you get \"This account may have been accessed by someone else.\"this happened to me 3 times.the 3rd time they wanted a cd key.a spent useless cd key that nobody has any reason to keep laying around.i gave them the paypal bill for my first purchase back in 2015.i gave them a bill for my first phone number ever on the account.i still got the same email attached to the account.this company is literally a scam. nothing but a scam.they randomly claim you been accessed somewhere else and then require you to give them information no reasonable person would ever have, if not your done and have to rebuy everything.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2024-07-31\nConsumer Complaint2023-12-09\nAuthor: K***\n\nHad 288 euros in steam wallet, someone hacked my account even with two step verification, write a steam support for help but only answer was if something is spent in community market they can’t help.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2023-12-09\nConsumer Complaint2023-09-26\nAuthor: J***\n\nI was banned for saying \"Who let grandma on the PC\"and another for simply calling someone ignorant.Power tripping mods, devs who don't care, steam doesn't care. Yet allows racism/trolling/etc Fk steam, its a joke now.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2023-09-26\nConsumer Complaint2022-08-31\nAuthor: Anonymous\n\nSteam community is plain bad for a various reasons:1. Steam forums are a big mess, for example they allow users to post in any language and as result you get jumbled mess with posts in foreign languages together with English language posts. For example, If you check CS GO forums, you'll see half of posts are in Russian and half in English. I don't understand why such a big and international company would leave their forums so unorganized like that. All other normal companies have English only language allowed which is an international language and sometimes subforums for other languages like German, French and etc... so if French people want to post in French they go specifically in that sub-forum. But no, Steam doesn't care about this. Their forums is a one big mess.2. Moderation is biased and joke. I don't understand why such a big company like Steam can't afford to hire people for moderation and pay them. Instead they just recruit random people for moderation who do it for free and\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2022-08-31\nConsumer Complaint2022-05-28\nAuthor: J***\n\nThe login code never arrives. I hate Steam.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2022-05-28\nConsumer Complaint2021-11-08\nAuthor: N***\n\nThe service is terrible, I only signed up because I really like the game I wanted, but the rest is terrible, I hope to get something better soon.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-11-08\nConsumer Complaint2021-06-18\nAuthor: W***\n\nThey scam people for money, dont believe me? Read thisSource: Steam Subscribers/User Agreement NO GUARANTEESTO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, NEITHER VALVE NOR ITS AFFILIATES GUARANTEE CONTINUOUS, ERROR-FREE, VIRUS-FREE OR SECURE OPERATION AND ACCESS TO STEAM, THE CONTENT AND SERVICES, YOUR ACCOUNT AND/OR YOUR SUBSCRIPTION(S) OR ANY INFORMATION AVAILABLE IN CONNECTION THEREWITH.In short: You got a virus or your data leaked because of our software? Whoopsies we dont care, that isnt even legal or the last of their scammy stuff...\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-06-18\nConsumer Complaint2021-05-14\nAuthor: B***\n\nThe support is one of the worst I've ever seen.Useless support team.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-05-14\nConsumer Complaint2020-04-02\nAuthor: J***\n\nSteamcommunity has 15% fees, 15!!!!\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2020-04-02\nConsumer Complaint2020-03-27\nAuthor: H***\n\nWhat can I say? the support is one of the worst I've ever seen maybe the FUNCOM is much worse. If you tell the true on the steam forum you just got a BAN even if what you said did not violated the rules of the forum.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2020-03-27\nConsumer Complaint2018-03-16\nAuthor: B***\n\ndon't sign up will stick on your computer will kill your pc power you can't remove it from your pc even you deleted it will stay woking in the system\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2018-03-16\nConsumer Complaint2016-12-27\nAuthor: J***\n\nIn bloddy hate their page it's tiresome, it's in no way intuitive. I tried reaching out for support, but that is a maze.I'm simply trying to log in and redeem a key of a product I already bought, their search function is a joke. I f*u*c*k*i*n*g hate them. The layout is not like the how to video from the dealer, this can be done much simpler. I don't frigin care aboutn what other titles you have in store or what genre, I just want to redeem my key and install.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-12-27\nConsumer Complaint2016-10-28\nAuthor: P***\n\nSupport on site is terrible.Refunds not happend yet, despite games not working.No help at all if key is bought outside their system, so as a customer you can bounce back and through between bad support systems?? I wait for some other companies to compete in this market, for this can't be the best we as customers can expect.And do put an email up to find, instead of this stuppid website where you spend so long time trying to find a solution on, instead of a simple mail. Often the problem is not there, or if it's there just saying no help here???I need a response\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-10-28\nConsumer Complaint2016-06-26\nAuthor: V*** W***\n\nUseless support as always!\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-06-26\nConsumer Complaint2014-07-01\nAuthor: J***\n\nexpensive, and support team not willing to cooperate\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2014-07-01\nConsumer Complaint2014-04-15\nAuthor: B***\n\nWhen you pay for a program, you expect it too work. cant not buy or anything and have written to valve. but there is not a being done a damn thing abut it..\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2014-04-15\nConsumer Complaint2026-09-03\nAuthor: M***\n\nWorst platform ever wont give me a refund even though a game is unplayable because of bugs I won't ever be using the crap platform again I hope the platform breaks down for good piece fo crao\n\nTarget Domain: steamcommunity.com / steampowered.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2026-09-03\n\nلا توجد سجلات مطابقة\n\nحاول تعديل استعلامك الحالي أو تصفح علامة تبويب فئة أخرى.\n\n1 / 9",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Valve السجل الرئيسي للفضائح — 160 الحوادث الموثقة"
          },
          {
            "level": 2,
            "id": null,
            "text": "حظر نطاقات مضيف المصادقة"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: C***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: S*** L***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: F***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: A***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: K***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: Anonymous"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: N***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: W***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: H***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: P***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: V*** W***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: M***"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/ar/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/ar/#proxy-bypass-explainer",
          "https://phishdestroy.io/steam_dossier/ar/#autoban-feasibility-section",
          "https://www.trustpilot.com/review/steamcommunity.com"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ar/valve_scandals_registry.content.json",
      "export_json_sha256": "c833165136380b00424ce6089636da1e7fb9483a74ce0464fd68618b416aa221"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ar/output_steam_network/index.html",
      "language": "ar",
      "title": "الهندسة المعمارية، وليس الاستغلال: شبكة الأتمتة — ملف «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/ar/output_steam_network/index",
      "source_html_sha256": "cce0b17dcbf1d9fa817341a954052b4b2edcb68a743a9756116b9910b9966bcb",
      "exported_at": "2026-09-29T00:20:34.412Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__index.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ar/output_steam_network__index.pdf?v=print-20260929-v5",
        "sha256": "00f9a3b8a5a102e36e4f80fc825a3808d8f53482bd64ad1f0505cb05f024141b",
        "bytes": 84772,
        "pages": 2
      },
      "integrity": {
        "signed_object": "output_steam_network__index.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__index.content.json.asc",
        "digest_file": "output_steam_network__index.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__index.content.json.asc output_steam_network__index.content.json",
          "sha256sum -c output_steam_network__index.content.json.sha256"
        ]
      },
      "content": {
        "text": "الملحق السابع · تحليل البنية التقنية\nSteam بنية الشبكة — دقة البروتوكولات وتحليل النظام البيئي\n\nالأتمتة هي أساس شركة «Valve». ليس ثغرة أمنية.\n\nما يثبته هذا القسم\n\nتوضح هذه الوحدة البنية التقنية لمستودعات المطورين 252، وملفات تعريف 3,320 وGitHub، وأزواج المساهمين 4,214 التي تشكل الأساس لنظام الأتمتة Steam. وتثبت أن الأتمتة التي تقوم بها أطراف ثالثة تعتمد على بروتوكول «Connection Manager» الرسمي الخاص بـ Valve، ومخططات Protobuf، وواجهات برمجة التطبيقات (Web APIs) دون استخدام أي كود استغلالي. من خلال هندسة الرموز الخوارزمية للتأكيد الخاصة بـ Steam Guard وجمع رسوم معاملات دنيا تصل إلى 66.7%,، تعمل Valve بصفتها المصمم المتعمد والمستفيد التجاري الرئيسي لعمليات النظام البيئي الآلي.\n\n← العودة إلى ملخص الإدارة التنفيذية\n\nعندما تخاطب شركة «Valve» الجهات التنظيمية أو شركات معالجة المدفوعات أو ضحايا عمليات الاحتيال، فإنها تعزو سرقة العملات الرقمية والتلاعب بالسوق إلى «استغلالات غير مصرح بها من قبل أطراف ثالثة» و«أتمتة غير مشروعة ومارقة». لكن الواقع الهندسي لشبكة مستودعات «252-» هذه يثبت العكس تمامًا: تعمل جميع أطر العمل الآلية وروبوتات التداول وأساطيل التعدين بشكل صارم ضمن حدود تعريفات البروتوكول الرسمية وواجهات برمجة التطبيقات (Web APIs) وآليات المصادقة التي قامت شركة «Valve» بتصميمها وتوثيقها وتحويلها إلى مصدر دخل.\n\nنتائج التحقيق الجنائي: «الهندسة المعمارية الواعية» مقابل «الاختراق غير المشروع»\n\nالبرامج التي تم تحليلها في هذه الوحدة — بما في ذلك SteamKit, node-steam-user, ValvePython/steam، و ArchiSteamFarm — يحتوي على لا توجد ثغرات أمنية في البرامج، ولا حالات تلف في الذاكرة، ولا استغلالات من نوع «اليوم صفر». وهي عبارة عن تطبيقات مفتوحة المصدر نظيفة ومتينة لبروتوكول عميل «Connection Manager» (CM) الخاص بشركة «Valve»، و«Google Protocol Buffers» (Protobufs)، وواجهات برمجة التطبيقات (Web APIs). وقد صممت شركة «Valve» واجهات برمجة التطبيقات هذه لقبول عمليات تسجيل الدخول البرمجية، كما صممت «Steam Guard» للسماح باستخدام رموز التأكيد الخوارزمية (identity_secret)، وتقوم بتحصيل الرسوم المعلنة على موقع 15% والتي ترتفع إلى ما يصل إلى 66.7% لصالح Valve فيما يتعلق ببطاقات الدفع عالية السرعة وعمليات بيع السلع التي تقوم شبكات الروبوتات الآلية بتصفيتها.\n\nالركيزة 01 · دقة البروتوكول\nمخططات Protobuf الرسمية\n\nمكتبات الأتمتة لا تتجاوز بوابات الأمان. فهي تقوم بتحويل رسائل Protobuf الرسمية إلى صيغة تسلسلية (steammessages_clientserver.proto) عبر بروتوكول TCP/WebSockets مباشرةً إلى مجموعات CM الرسمية الخاصة بـ Valve، تمامًا كما يفعل عميل Steam.\n\nالركيزة 02 · الخوارزمية 2FA\nترخيص التداول الآلي\n\nيعتمد اقتصاد تجارة الجلود برمته، الذي تبلغ قيمته عدة مليارات من الدولارات، على موقع Valve IEconService API ومفاتيح المصادقة عبر الهاتف المحمول بنظام TOTP. قامت شركة «Valve» بتصميم «Steam Guard» خصيصًا لتمكين تأكيدات التداول بين الأجهزة.\n\nالركيزة 03 · المستفيد التجاري\nحركة المرور المدفوعة من الآلات: تصل إلى الحد الأدنى لرسوم 66.7%\n\nValve تُعلن عن رسوم تبلغ 15%، ولكن في حالة السلع ذات الحجم الكبير التي تتداولها الروبوتات الآلية — مثل بطاقات التداول، والعلب، والعروض الرخيصة التي تتراوح أسعارها بين $0.03 و$0.05 — فإن الحد الأدنى للرسوم في Valve البالغ سنتين ($0.01Steam + $0.01 للناشر) يُستقطع 50% إلى 66.7% لصالح Valve (تم خصم 2¢ من بطاقة 3¢، مما ترك للبائع مبلغ 1¢). بالإضافة إلى $5.00 لكل حساب ($26.8M على الأسطول الذي تم مسحه ضوئيًا وحده).\n\nالوحدة01 · أدلة المستودع والبروتوكول\nالبنية التحتية العامة للمطورين والمستودعات\n\nفهرس جنائي مفصل لمستودعات البرمجيات مفتوحة المصدر 252 التي تدعم أتمتة Steam. يتتبع كيفية قيام أدوات هندسة البرمجيات القياسية بتنفيذ نقاط النهاية المنشورة على Valve API دون استخدام ثغرات أمنية.\n\n252المستودعات\n4,554روابط الأدوار\nفحص أدلة المستودع →الوحدة 02 · ديموغرافيا النظم البيئية\nمقاييس النظام البيئي الهندسي العالمي\n\nالتوزيع الجغرافي والمؤسسي لمهندسي البرمجيات في شركة «3,320» المساهمين في منظومة أتمتة «Steam»، بما في ذلك الانتماءات المؤسسية لدى كبرى الشركات العاملة في مجال التكنولوجيا.\n\n3,320المهندسون\n98,902أزواج التوصيلات\nفحص مؤشرات النظام البيئي →الوحدة 03 · رسم بياني تفاعلي\nرسم بياني تفاعلي للبروتوكول وشبكة المطورين\n\nرسم بياني شبكي تفاعلي شامل على موقع Vis.js يضم مستودعات الخرائط ومكتبات البروتوكولات (SteamKit، Steamworks، ASF)، بالإضافة إلى التداخلات بين المساهمين عبر المشاريع المختلفة. ويوضح بشكل مرئي بنية البرمجيات مفتوحة المصدر الشرعية والمترابطة التي تدعم نظام الأتمتة في Steam.\n\nتفاعليVis.js المحرك\nعزل المجموعاتالبحث المباشر\nلا توجد ثغرات أمنيةواجهات برمجة التطبيقات القياسية\nتشغيل الرسم البياني التفاعلي للشبكة →\nالسياق التنظيمي والقانوني (مقال من موقع GDPR بعنوان «25» وحماية المستهلك):\nبموجب مبدأ «حماية البيانات حسب التصميم وافتراضيًا»، فإن بنية المنصة التي تسمح بإنشاء مفاتيح «API» بشكل خفي، وإلغاء الصفقات دون إخطار، وتصفية الأصول آليًّا، تُعد خيارًا هندسيًّا من جانب مشغل المنصة. وعندما ترفض «Valve» بشكل منهجي مطالبات المستهلكين بالتعويض، مدعيةً أن الخسائر نجمت عن «هجمات إلكترونية خارجية»، فإنها تخفي حقيقة أن مسار الهجوم هو بنية موقع «Valve» على الويب API نفسها، التي صُممت عن قصد.\n\nعرض تفاعلي\n\nيتوفر عرض مرئي تفاعلي كامل لمستودع «252-»، 3,320-، ورسم بياني لشبكة المطورين على الرابط التالي: network.html. توجد المقاييس الإجمالية في مقاييس ذكاء الأعمال الصفحة.\n\nملف «Steam» · أرشيف البنية التقنية · سجلات المصادر المفتوحة · جميع الحقوق مُنحت للبشرية.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam بنية الشبكة — دقة البروتوكولات وتحليل النظام البيئي"
          },
          {
            "level": 3,
            "id": null,
            "text": "مخططات Protobuf الرسمية"
          },
          {
            "level": 3,
            "id": null,
            "text": "ترخيص التداول الآلي"
          },
          {
            "level": 3,
            "id": null,
            "text": "حركة المرور المدفوعة من الآلات: تصل إلى الحد الأدنى لرسوم 66.7%"
          },
          {
            "level": 2,
            "id": null,
            "text": "البنية التحتية العامة للمطورين والمستودعات"
          },
          {
            "level": 2,
            "id": null,
            "text": "مقاييس النظام البيئي الهندسي العالمي"
          },
          {
            "level": 2,
            "id": null,
            "text": "رسم بياني تفاعلي للبروتوكول وشبكة المطورين"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/ar/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/ar/output_steam_network/valve_ru_farming_isolated.html",
          "https://phishdestroy.io/steam_dossier/ar/output_steam_network/steam_ecosystem_dashboard.html",
          "https://phishdestroy.io/steam_dossier/ar/output_steam_network/network.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ar/output_steam_network__index.content.json",
      "export_json_sha256": "091d9f6d06d3eb7bc9b8b321506b0134ffae409e60ced1396b1894cc7ed3f685"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ar/output_steam_network/network.html",
      "language": "ar",
      "title": "مستكشف المطورين والمستودعات — ملف «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/ar/output_steam_network/network",
      "source_html_sha256": "9a02909d97d00e795f676affb40c4863c7fa302b43dbe07713ea51a180f90ee4",
      "exported_at": "2026-09-29T00:20:36.183Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__network.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ar/output_steam_network__network.pdf?v=print-20260929-v5",
        "sha256": "daf3635bb253c37140b1faeaf6aebabe7cb1eaf1ddb9b54990169f888aff2d9e",
        "bytes": 39899,
        "pages": 1
      },
      "integrity": {
        "signed_object": "output_steam_network__network.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__network.content.json.asc",
        "digest_file": "output_steam_network__network.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__network.content.json.asc output_steam_network__network.content.json",
          "sha256sum -c output_steam_network__network.content.json.sha256"
        ]
      },
      "content": {
        "text": "مستكشف المطورين والمستودعات\n\nابحث عن عقدة. افحص العلاقة المسجلة.\n\nالسجلات العامة / الروابط المجمعة\nالبحث المباشر\nطبقات التصفية\nإجمالي عدد المطورين3,320\nإجمالي عمليات إعادة الشراء252\nالرسم البياني المعروض / مجموعة فرعية من المجموعة468 العقد • 1103 الحواف\nسجل الملف الشخصي المحدد\n\n💡 انقر على أي عقدة في الرسم البياني أو اكتب في خانة «البحث» لتفحص الوصلات التي تم جمعها ومسارات المصدر الخاصة بها.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "مستكشف المطورين والمستودعات"
          }
        ],
        "links": []
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ar/output_steam_network__network.content.json",
      "export_json_sha256": "2f8b4adcd473452c1566327611a9b57f7d4d800c41c4fac847a8e7340dc42e66"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ar/output_steam_network/steam_ecosystem_dashboard.html",
      "language": "ar",
      "title": "الشبكة التي تم تجميعها بالأرقام — ملف «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/ar/output_steam_network/steam_ecosystem_dashboard",
      "source_html_sha256": "813e92fe9f5bab67ed14c53b3cd83f94e286e50d8418d608ae1bcf734f1f93b2",
      "exported_at": "2026-09-29T00:20:37.750Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__steam_ecosystem_dashboard.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ar/output_steam_network__steam_ecosystem_dashboard.pdf?v=print-20260929-v5",
        "sha256": "b16ed7d3ca705ec55fd957bb663a0229341a4867b662ab70c1be083a678d252c",
        "bytes": 47132,
        "pages": 1
      },
      "integrity": {
        "signed_object": "output_steam_network__steam_ecosystem_dashboard.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__steam_ecosystem_dashboard.content.json.asc",
        "digest_file": "output_steam_network__steam_ecosystem_dashboard.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__steam_ecosystem_dashboard.content.json.asc output_steam_network__steam_ecosystem_dashboard.content.json",
          "sha256sum -c output_steam_network__steam_ecosystem_dashboard.content.json.sha256"
        ]
      },
      "content": {
        "text": "نظرة عامة على الإحصائيات // الملف 02\nSteam لوحة معلومات النظام البيئي — الشبكة بالأرقام\n\nالشبكة، بالأرقام.\n\nما يثبته هذا القسم\n\nتجمع لوحة المعلومات هذه المعلومات الهيكلية من مطوري 3,320 ومستودعات 252، وتحدد قواعد البيانات الخاصة بالمقامرة على 68 وجسور الاتصال عبر المنصات. وتسلط البيانات التجريبية الضوء على التجمعات الجغرافية والتداخلات بين المطورين، مما يدل على أن البنية التحتية للمقامرة عبر «سكين» (skin) التابعة لأطراف ثالثة تعمل كصناعة برمجيات منظمة ومترابطة للغاية ومتكاملة مع منصة Steam.\n\n← العودة إلى ملخص الإدارة التنفيذية\n\nإحصاءات موحدة لقاعدة بيانات التحقيق: التوزيع الجغرافي، وأبرز الشركات، ومستودعات المقامرة بالـ\"سكينز\"، وجسور الاتصال النشطة.\n\nالمطورون الممسوحون ضوئيًا3320\nإجمالي عمليات إعادة الشراء252\nمستودعات المقايضة الخاصة بالمقامرة68\nإجمالي عدد الاتصالات1,426\nهيكل وقطاعات الأتمتة\nالقطاع الأول — شركة «Valve» (الجزء الأساسي)\n\nالمستودعات الرسمية وبرامج الأنظمة. مساحة تطوير مؤكدة لموظفي شركة «Valve»، وهما نيفيرين وجو لودفيغ.\n\nالقطاع الثاني — محركات الترخيص ومحاكيات البروتوكولات (SteamKit)\n\nمكتبات شبكية تم تطويرها عبر الهندسة العكسية، شارك في تأليفها Nephyrin من موقع «Valve» ومطور ألعاب المقامرة DoctorMcKay.\n\nالقطاع الثالث — عملاء تربية البطاقات (ArchiSteamFarm)\n\nاستخدم محاكيات بروتوكول SteamKit لتشغيل ملايين العملاء الوهميين (في وضع الخمول) في الخلفية بهدف جمع بطاقات التداول.\n\nالجغرافيا الخاصة بالمطورين\nألمانيا57\nالولايات المتحدة52\nكندا48\nالمملكة المتحدة44\nبولندا30\nفرنسا28\nالاتحاد الروسي27\nالصين27\nالولايات المتحدة الأمريكية (ولاية واشنطن)23\nأستراليا19",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam لوحة معلومات النظام البيئي — الشبكة بالأرقام"
          },
          {
            "level": 3,
            "id": null,
            "text": "القطاع الأول — شركة «Valve» (الجزء الأساسي)"
          },
          {
            "level": 3,
            "id": null,
            "text": "القطاع الثاني — محركات الترخيص ومحاكيات البروتوكولات (SteamKit)"
          },
          {
            "level": 3,
            "id": null,
            "text": "القطاع الثالث — عملاء تربية البطاقات (ArchiSteamFarm)"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/ar/#briefing-heading"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ar/output_steam_network__steam_ecosystem_dashboard.content.json",
      "export_json_sha256": "c742459d803ed483be80ba9c0447a6b86f9d82ac881a8c879d0a51c96796b471"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ar/output_steam_network/valve_ru_farming_isolated.html",
      "language": "ar",
      "title": "الكود والمساهمون والفروع — ملف «Steam»",
      "source_url": "https://phishdestroy.io/steam_dossier/ar/output_steam_network/valve_ru_farming_isolated",
      "source_html_sha256": "e7df2058f04a9e8f05b68c3797e76e68560f36da282a33b3c47d827f1ff889c5",
      "exported_at": "2026-09-29T00:20:38.110Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__valve_ru_farming_isolated.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ar/output_steam_network__valve_ru_farming_isolated.pdf?v=print-20260929-v5",
        "sha256": "0e6a7c4552621c6fd008fdce6b8d9bd6a1020a94fe9dd825d07c53ba3f7c99e8",
        "bytes": 52787,
        "pages": 2
      },
      "integrity": {
        "signed_object": "output_steam_network__valve_ru_farming_isolated.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__valve_ru_farming_isolated.content.json.asc",
        "digest_file": "output_steam_network__valve_ru_farming_isolated.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__valve_ru_farming_isolated.content.json.asc output_steam_network__valve_ru_farming_isolated.content.json",
          "sha256sum -c output_steam_network__valve_ru_farming_isolated.content.json.sha256"
        ]
      },
      "content": {
        "text": "الجزء الثاني / تتبع العلاقة الموثقة\n\nتُعد «الفوركات» و«المساهمات» و«تبعيات البرامج» أدلة واضحة. ويحافظ هذا الرأي على الأدوار التي تم جمعها؛ أما ما يتعلق بالتوظيف، واختراق الإجراءات الأمنية، والتورط في أنشطة إجرامية، فيتطلب مصادر إضافية.\n\nافتح خريطة القدرات التفاعلية ↗\nالمصادر العامة / تدقيق الأدوار\nالكود. المساهمون. النسخ المتفرعة.\n1. Nephyrin: الفروع والمساهمات\n\nتشير اللقطة المرفقة إلى أن «Nephyrin» هو أحد المساهمين في مشروع ValveSoftware/Proton، وأحد مطوري الفروع لمشروعي SteamRE/SteamKit وSteamRE/open-steamworks. وتشير بيانات ملفه الشخصي إلى شركة «Valve Software». وينبغي قراءة هذه الحقول كل على حدة.\n\nتسجل «فورك» نسخة من المستودع. ولا يتضمن هذا التصدير «كوميت» يُثبت إجراء تغييرات على كود المصادقة الخاص بـ SteamKit.\nمراجع المستودع / الاطلاع على السجل\nSteamRE/SteamKit ↗ SteamRE/open-steamworks ↗\n2. القدرات العامة: الأتمتة دون الحاجة إلى عميل سطح المكتب\n\nيتيح كل من SteamKit وnode-steam-user إمكانية التفاعل البرمجي مع Steam. ويوثق ArchiSteamFarm عملية جمع البطاقات عبر حسابات متعددة، ويُعلن عن SteamKit2 كأحد التبعيات.\n\nهذه هي قدرات الأتمتة الملموسة. ولا يُعد التنفيذ بدون واجهة مستخدم دليلاً على الاستخدام التجاري الحصري أو على التحايل على نظام الحماية من التلاعب (Steam Guard). والأسئلة ذات الصلة هي: بيانات الاعتماد المطلوبة، والإجراءات المتاحة لها، والضوابط التي تطبقها المنصة.\n\nالمصدر: ملفات README الخاصة بالمشاريع وموقع ArchiSteamFarm.csproj. وتربط خريطة القدرات كل تبعية موثقة.\n3. JoeLudwig: علامة «مساهم في hl2sdk»\n\nتُدرج اللقطة «JoeLudwig» كمساهم في مشاريع alliedmodders/hl2sdk وValveSoftware/openvr وValveSoftware/source-sdk-2013.، وهذه علاقة واضحة بين المشاريع. ولا تقدم البيانات المصدَّرة أي دليل يربط تغييرًا معينًا في SDK بسرقة أو بنشر لأغراض المقامرة.\n\nمراجع المستودع / الاطلاع على السجل\nalliedmodders/hl2sdk ↗ DoctorMcKay/node-steam-user ↗\nالمخطط المنطقي // المسارات\nمخطط تدفق منطق التوصيل:\nالملف الشخصي والعلاقة\nNephyrin / الملف الشخصي المجمع\nالمساهم: Proton. مطورو النسخة المتفرعة: SteamKit و open-steamworks.\n▼ علاقات التفرع المجمعة\nمكتبة المجتمع\nSteamRE/SteamKit\nمكتبة شبكة «Steam» العامة التي تتم صيانتها ضمن منظمة SteamRE.\n▼ تم الإعلان عن التبعية لـ SteamKit2\nالأتمتة الموثقة\nJustArchiNET/ArchiSteamFarm\nتوثق هذه الوثائق عملية تجميع بطاقات عبر حسابات متعددة، بالإضافة إلى وجود تبعية لـ SteamKit2.\nمراجعة الأدلة / لمحة عن المصدر\nتم تسجيل: تسميات \"المساهم\" و\"مُنشئ الفرع\" المميزة.\nموثّق: تدعم المكتبات العامة التفاعلات البرنامجية Steam.\nسؤال مفتوح: تتطلب إثبات ملكية الكود بشكل محدد، وموافقة المنصة، وإثبات المسؤولية عن إساءة الاستخدام أدلة منفصلة.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "الكود. المساهمون. النسخ المتفرعة."
          },
          {
            "level": 2,
            "id": null,
            "text": "1. Nephyrin: الفروع والمساهمات"
          },
          {
            "level": 2,
            "id": null,
            "text": "2. القدرات العامة: الأتمتة دون الحاجة إلى عميل سطح المكتب"
          },
          {
            "level": 2,
            "id": null,
            "text": "3. JoeLudwig: علامة «مساهم في hl2sdk»"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/ar/investigation_part2.html#automation-map",
          "https://github.com/SteamRE/SteamKit",
          "https://github.com/SteamRE/open-steamworks",
          "https://github.com/alliedmodders/hl2sdk",
          "https://github.com/DoctorMcKay/node-steam-user"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ar/output_steam_network__valve_ru_farming_isolated.content.json",
      "export_json_sha256": "1fca15556b486240bd87caf3c9bb1174a01fd17143d9b22888ff2b673bbc7a9b"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "tr/card_economy.html",
      "language": "tr",
      "title": "Kart ekonomisi — Steam Dosyası",
      "source_url": "https://phishdestroy.io/steam_dossier/tr/card_economy",
      "source_html_sha256": "b541d841034063ccaee5c15a1e254a11d7d3e785f8583e597ccfd6d4db81e1d6",
      "exported_at": "2026-09-29T00:20:40.518Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "card_economy.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/tr/card_economy.pdf?v=print-20260929-v5",
        "sha256": "4cc401bcd7c0e51638c6302c4eb78915f0657fea15cf0a0602edb66a6b1d26c0",
        "bytes": 253647,
        "pages": 24
      },
      "integrity": {
        "signed_object": "card_economy.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "card_economy.content.json.asc",
        "digest_file": "card_economy.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify card_economy.content.json.asc card_economy.content.json",
          "sha256sum -c card_economy.content.json.sha256"
        ]
      },
      "content": {
        "text": "EK V — KART EKONOMİSİ\nBir bot çiftliği, Valve’nin dükkanındaki bir sızıntı değildir. Bu bir müşteri.\n\nBir Steam hesabı, harcama yapana kadar tek bir koleksiyon kartı bile alamaz $5.00 mağazada. Sahip olmadığı bir oyunu “farmlayamaz” ve kendisine bedelsiz verilen bir oyunu da “farmlayamaz”. Dolayısıyla, otomatik kart “farm” sistemi herhangi bir şey üretmeye başlamadan önce, Valve’in belirlediği fiyattan hesap başına giriş hakkını satın almış olmalıdır. Ardından Valve’nin otomasyon maddesi, o sistemin tam olarak ne ürettiğini satır satır belirtir; lisansı, farmlanmış bir kartın paraya dönüşmesini sağlayan her yolu yasaklar; ve kart ne olursa olsun satıldığında pazarı bir pay alır — 15%'da ilan edilir, ancak satış başına en az iki sent olarak belirlenir; bu da sent cinsinden fiyatlandırılan bir kart için fiyatın büyük bir kısmını oluşturur. Bu örnek, bu ticaretin ne kadar büyük olduğunu, bir profilin en üst seviyesinin set cinsinden ne kadara mal olduğunu ve hesap sıradan bir tüccara ait olduğunda Valve'ün uygulama biriminin aynı maddeyi nasıl uyguladığını ölçer.\n\nBir çiftliğin öncelikle satın alması gerekenlerBir seviyenin set başına maliyetiMasanın her iki tarafıKart ekonomisini kim denetler?\n$5.00Bir hesap herhangi bir kart alabilmesi için önceden mağazada harcama yapılması gerekir — Valve’un kendi destek sayfası\n13,876Steam üzerinde, 99,971 farklı kart türü barındıran ve koleksiyon kartları dağıtan oyunlar\n694,673Şu anda halka açık 91 ticaret botu tarafından stokta tutulan eksiksiz kart setleri\n1,389,346Söz konusu hisse senedinin halihazırda tüketmiş olduğu hesap ve oyun kartı dağıtım limitleri, en azından\n$9.99Kartlı bir oyunun medyan fiyatı — oyunun tamamlanmış seti medyan olarak $0.74'a satılıyor\n97,114Moderatör listesinde Valve numaralı çalışan bulunan kart takas grubunun üyeleri — § 08\n01 — Süreç\nBir çiftliğin gerçekte ne olduğu, adım adım\n\nYalnızca aracın kendi belgelerinden ve Valve’un kendi destek sayfalarından aktarılmıştır. Bu bölümdeki hiçbir bilgi bir çıkarım değildir ve bu bölümdeki hiçbir husus taraflarca tartışma konusu değildir.\n\n1. Adım\nSatın al\n\nHesap şunlardan biri olmamalıdır: sınırlı. Valve'nin destek sayfası, kısıtlı hesapların \"Steam Piyasasına Katılmak\", kaynak: \"Topluluk öğelerinin (koleksiyon kartları, takviye paketleri, mücevherler vb.) takası\" ve şuradan: \"Steam Profil Seviyesi (Seviye 0'da kilitli) ve Koleksiyon Kartları kazanma\". Asıl mesele paradır: \"Steam numaralı mağazada en az $5.00 USD tutarında alışveriş yapmanız gerekecektir.\"\n\n2. Adım\nOyun satın al\n\nKartlar yalnızca sahip olduğunuz oyunlardan düşer. \"Bu hesaptan herhangi bir kart kazanabilmek için oyunun Steam hesabında size ait olması gerekir. Aile paylaşımı, oyuna sahip olmak anlamına gelmez ve bu şartı karşılamaz.\" Ücretsiz güzergâhlar da kapalıdır: \"Bir promosyon kapsamında ücretsiz olarak edindiğiniz ücretli oyunlarda kart düşürme amacıyla çiftçilik yapılamaz\"ve \"F2P oyunlarda hiç para harcamadan kartları atamazsınız.\"\n\n3. Adım\nBoşta\n\nAraç, hesabı Steam ağına başsız bir şekilde oturum açar, \"rozetlerinizi analiz eder\", oynanabilir oyunların listesini oluşturur ve başlatır \"Uygun oyunu oynamak ve oyunun tamamen tamamlanıp tamamlanmadığını düzenli aralıklarla kontrol etmek.\" Bu mekanizmaya ilişkin bakım sorumlusunun açıklaması: bu \"Steam'a, belirli bir oyunu oynadığımızı söylemekten başka bir şey yapmaz.\"\n\n4. Adım\nDamlalar bitti\n\nHer başlık sonludur. \"Her oyunda sabit sayıda kart düşer. Bunların hepsini topladığınızda (tam setin yaklaşık yarısı), oyun artık farm yapmak için uygun bir seçenek olmaktan çıkar.\" Üretime devam etmek isteyen bir çiftlik, sürekli kart satın almak zorundadır. Kart arzı, satın alımlar yoluyla kısıtlanmaktadır — bu, sistemin tasarımı gereği ve Valve'nin lehine bir durumdur.\n\n5. Adım\nPara çekme\n\nKart, üç seçenekten biriyle elden çıkarılır: Topluluk Piyasası’nda satılır, takas edilir ya da mücevher haline getirilir. Her biri bir Abonelik Piyasası işlemi ya da takastır ve § 3.D’de şu hüküm yer almaktadır: \"Valve, Abonelik Pazarı’ndaki işlemler için bir ücret talep edebilir.\" İşte tüm bu süreci bir güvenlik ihlaline dönüştüren adım budur — bkz. 05.\n\nKaynaklar, 2026-09-22’da aynen okunmuş ve alıntılanmıştır: Steam Destek — Sınırlı Kullanıcı Hesapları ↗ · ArchiSteamFarm SSS ↗ · Valve — Steam Koleksiyon Kartları SSS ↗ · Steam Abone Sözleşmesi ↗ arşivlendi 2026-09-24 ↗. ArchiSteamFarm, bu sayfa boyunca bir ölçü aracı olarak kullanılmaktadır, sanık olarak değil; kendi belgelerinde açıkça belirtildiği üzere, \"ASF, Valve tarafından yetkilendirilmemiştir\".\n\n02 — Ölçek\nBir çiftlik bir sent bile kazanamadan, çoktan Valve ödemiştir\n\nSınırlı hesaplara kart verilemediğinden, bir çiftlikteki her hesabın üretim yapmaya başlamadan önce sınırlı statüsünden çıkarılması gerekir. Bu ücretin tutarı kamuya açıklanmıştır ve hesap başına tahsil edilir.\n\nÇiftlik büyüklüğü\tBu sayının kaynağı nedir?\tKart almaya hak kazanmak için gerekli minimum mağaza harcaması\n10 hesap\tASF’nin tavsiye ettiği tavan — \"şirket içi Valve yönergelerine ve kendi önerilerimize dayanarak\"\t$50\n100–200 hesap\tAynı SSS’deki teknik sınır: \"Tek bir IP adresi ve tek bir ASF örneği ile 100-200 adede kadar bot çalıştırabilirsiniz\"\t$500 – $1,000\n120 hesap\tAşağıdaki 3 numaralı yaptırım vakası — kalıcı olarak yasaklandı\t$600\n170 hesap\tAşağıdaki 2 numaralı yaptırım vakası — 2017 Kış İndirimi sırasında kalıcı olarak yasaklandı\t$850\n1,000 hesap\tAşağıdaki 1 numaralı yaptırım davası — ticaretin yasaklanması\t$5,000\n5,000 hesap doğrulanmamış\tOperatör tartısı bu soruşturmaya bildirilmiş ve bağımsız olarak doğrulanmamış — kaynak göstermeyle ilgili nota bakınız\t$25,000\n10,000 hesap doğrulanmamış\tOperatör tartısı bu soruşturmaya bildirilmiş ve bağımsız olarak doğrulanmamış — kaynak gösterimi ile ilgili nota bakınız\t$50,000\n\nBu sayfadaki rakamlar arasında, bir belgeye değil, doğrulanmamış bir rapora dayanan tek rakamlar son iki satırdır — bunlar tabloda işaretlenmiştir ve şu bölümde açıklanmıştır: tedarikle ilgili not, ve buradaki diğer hiçbir şey bunlara bağlı değildir. Sağdaki sütun, Valve'in açıkladığı $5.00 USD eşik değeri üzerinden yapılan hesaplamalardan ibarettir ve başka hiçbir şeyden ibaret değildir. Bu bir zemin, bir çiftliğin maliyetine ya da Valve’in ne kadar kazandığına dair bir tahmin değildir: Bu rakam, sahip olunması gereken ve promosyon yoluyla ücretsiz olarak elde edilemeyen oyunları kapsamaz; ayrıca kartlar satıldığında Topluluk Pazarı’nın aldığı yaklaşık 15% tutarını da içermez. Bu sayfada herhangi bir gelir rakamı belirtilmemiştir.\n\nAyrıca Valve de bir kart dağıtımı için fiyat belirlemiştir. Oyunun “Ticaret Kartları” SSS bölümünde, ücretsiz oyuna geçiş oranı açıkça dolar cinsinden belirtilmiştir:\n\n\"Ücretsiz oynanabilen oyunlarda, oyun içi satın alımlarınıza bağlı olarak oyun kartları verilir.\" Harcanan her $9 ABD Doları için (yaklaşık) \"Steam Koleksiyon Kartı Beta sürümünün başlamasından bu yana, bir kart kazanacaksınız.\"\n\n— Valve, Steam Koleksiyon Kartları SSS ↗ · kelimesi kelimesine doğrulanmış 2026-09-22\n\nBir koleksiyon kartı, platformun zarar ettiği bir hediye değildir. Bu, Valve’ın, Valve’de belirtilen fiyattan sattığı ve daha sonra yeniden satmak için ikinci kez ücret aldığı bir üründür. İşte bu nedenle, bir kart çiftliğinin dürüst tanımı şu değildir: parazit. Bu toptan alıcı.\n\nSatın alınan şeyin gerçekte ne kadar büyük olduğu\n\nBuradan bu bölümün sonuna kadar olan her şey ölçülmüştür, raporlanmamıştır. Kart sayımı, Steam Card Exchange’in yayınladığı rozet fiyat listesine dayanmaktadır; oyunların fiyatları ise Valve’in kendi mağaza API’sinden alınmıştır; bot stoğu ise herkesin erişebileceği halka açık bir bot dizininden elde edilmiştir. Üçü de 2026-09-22'da okunmuştur ve hesaplamaların tamamı şu adreste verilmiştir: bölüm 08.\n\n13,876Kart dağıtan oyunlar\n99,971Farklı kart türleri\n5 · 6 · 15Set başına kart sayısı: en az, ortanca, en fazla\n$0.74Hazır bir setin medyan fiyatı\n$23,586.57Piyasada her setten bir tane\nBir kümenin büyüklüğü ne kadardır?\n\n13,876 set içindeki kartlarla oynanan oyun sayısı. Valve bunların yaklaşık yarısını herhangi bir hesaba aktarıyor.\n\n0\n1,250\n2,500\n3,750\n5,000\n5\n6\n7\n8\n9\n10\n11\n12\n13\n14\n15\nLisansın maliyeti nedir?\n\nAynı oyunların Steam mağazasındaki liste fiyatları, ABD doları cinsinden.\n\n0\n1,000\n2,000\n3,000\n4,000\n<$1\n$1-3\n$3-5\n$5-10\n$10-20\n$20-40\n$40+\nTamamlanmış kümenin döndürdüğü değer\n\nAynı oyunların eksiksiz setinin piyasa fiyatı.\n\n0\n1,500\n3,000\n4,500\n6,000\n<$0.50\n$0.50-1\n$1-2\n$2-5\n$5-10\n$10+\n\nİkinci ve üçüncü grafikleri birbiriyle karşılaştırarak incelediğinizde, hesaplama yapmanıza gerek kalmadan işlemin yapısı net bir şekilde ortaya çıkar: Oyunların çoğu on dolarlık aralıkta yoğunlaşırken, bunların getirdiği puanlar bir doların altında yoğunlaşmaktadır. Her ikisi de aynı 13,876 oyunlarının sayılarıdır ve aynı eksen birimini kullanmaktadır; dolayısıyla karşılaştırma, iki ölçek arasında değil, iki yükseklik arasında yapılmaktadır.\n\nBu, arz tarafıdır. Talep tarafı ise Valve’un reklam yapmasına gerek olmayan kısımdır, çünkü zaten herkesin gözü önünde yer almaktadır: Kart takas botlarını içeren tek bir açık dizin, şunları listelemektedir: Şu anda stokta 694,673 tam set bulunduran 91 bot var. Giriş gerekmez, pazar yerinden veri toplanmaz, özel veriler yoktur — stok rakamı, her botun adının yanındaki sayfada yazılıdır.\n\nO hisseyi, burada tek önemli olan birim haline getir. Valve'un kendi kuralı: \"Çoğu oyunda, o oyunun kart setindeki kart sayısının yaklaşık yarısı kadar kart dağıtılır… Setin diğer yarısını diğer topluluk üyelerinden toplamanız gerekecek.\" Tek bir hesap, oynayarak bir seti asla tamamlayamaz. En az iki hesap gerekir; her ikisi de o oyuna sahip olmalı ve her biri oyun başına bir kez kullanılabilen bırakma hakkını kullanmalıdır. Bırakma hakları yenilenmez.\n\n694,673Stokta bulunan setler, 91 adet halka açık bot\n3,473,365Kartlar, en az 5 kartlık set halinde\n1,389,346Tüketilen damla tahsisatları, minimum\n2,602Tek bir oyuna sahip hesaplar, en yoğun bot\n694,673 kümelerinin bulunduğu yer\n\nHalka açık 91 kart botu arasından, stoklarındaki tam set sayısına göre en büyük on ikisi. En büyük on tanesi, aralarında toplam 248,115 set bulunduruyor — tahtadaki her şeyden 35.7% tane.\n\n0\n11,250\n22,500\n33,750\n45,000\nCard Supply #4 (High)\nN!vq's Leveling (High)\nAlice [BOT] LEVEL-UP RARE SETS\nN!vq's Leveling (Low)\nDisco Lite Level Up\nN!vq's Leveling (Mid)\nbaty131store.net | Level Up\nKitten - Supreme\nArashirn | Level Up\nSH (Junior) Level Up\nDuobot.com - Overstock\nlvlupbot.com - godlike\n\nBu 1,39 milyon tahsisatın her biri, oyunun sahibi olan, $5.00 eşiğini geçmiş ve bu düşmeleri bir daha asla üretemeyecek bir hesaba aitti. Bu, satılmamış stok doksan bir bot üzerinde. Bu, piyasanın bir göstergesi değil; piyasanın geriye bıraktıklarının bir göstergesidir.\n\nSon rakam, kişi sayısı değil, sınıflandırma tablosudur. Bir bot, yalnızca 11 oyundan çekilen 14,310 seti listeliyor; dolayısıyla bu oyunlardan en az biri 1,301 setle temsil ediliyor, bu da o oyunu satın alan en az 2,602 farklı hesap olduğu anlamına gelir. Bu, aritmetiğin izin verdiği en küçük sayıdır ve doksan bir botun sadece biriyle ilgilidir.\n\nBu metnin neyi ifade ettiği ve neyi ifade etmediği\n\nBu botlar, hem sıradan oyunculardan hem de kart toplama hesaplarından kart satın alırlar — yayınladıkları satın alma fiyatları, bu rehberin temelini oluşturur. Dolayısıyla, 1,39 milyon tahsisat, çiftliklere ait hesapların sayısını yansıtmamaktadır. Bunlar, Steam’de bir yerlerde harcanmış ve satılmadan ticari stokta kalmış, hesap başına bir kez, oyun başına bir kez düşme kotalarının sayımıdır. Her birinin arkasındaki hesabın bir farm hesabı mı yoksa rozet sayfasını temizleyen bir genç mi olduğu, Valve'in topladıklarını değiştirmez: $5.00'ın kilidini açma hakkı, oyun lisansı ve her satıştan alınan Pazar payı — 15% değil, 15% ya da iki adet bir sentlik asgari tutardan hangisi daha büyükse o, ki bu, sent cinsinden fiyatlandırılmış bir kartta açık ara daha büyük olanıdır. Hesaplama şöyledir: Aşağıdaki ücret tablosu. Bu sayfanın amacı budur ve bu, çiftçilere yönelik bir şikayet değildir: Valve’un ücret talep ettiği davranış, bir kişiyi “ticari kullanım” gerekçesiyle kalıcı olarak yasaklarken kelimesi kelimesine atıfta bulunduğu davranışın aynısıdır.\n\nBu rakam, ikinci bir anlamda da bir alt sınırdır. Yalnızca şu hisse senetlerini hesaba katmaktadır: bugün listelenmiş ve satılmamış olan botlar konusunda genel dizinde yer almayı seçin. Halihazırda satılmış olan her şey, özel olarak tutulan her şey ve dizin dışında kalan her bot hariç tutulmuştur.\n\nAyrıca, Valve’nin fiyatlarıyla tarım kâr getirmiyor\n\nBurada akla gelen ilk itiraz, bir çiftliğin pahalı kartlar basmak için ucuz oyunlar satın aldığıdır. Steam’nin kendi mağaza API’si ise bunun aksini söylüyor. 13,876 kart içeren oyunlardan, 13,713 için fiyatlar belirlendi; 12,918, liste fiyatının ortancası $9.99 olan ücretli yayınlardır. Bitmiş setlerin medyan satış fiyatı $0.74. Her set için iki lisans gereklidir. Dolayısıyla, bir setin maliyeti yaklaşık olarak $19.98 adet oyun lisansının üretimi ve iadeleri $0.74.\n\n2026-09-22 üzerinde ölçülmüştür\tDeğer\tNeyi düzenler?\nKartlı oyunlarda liste fiyatının medyanı\t$9.99\tİşlemin pahalı kısmı lisans, kart değil\nFiyatı $4.99 veya daha az olan oyunlar\t3,665 (28.4%)\tEn ucuz kuyruk bile, ondan elde edilen setten daha pahalıdır\nMağazadaki en ucuz kartlı oyun\t$0.99\tGenellikle $1.30'nin altında satılan bir set için iki lisans, $1.98\nOyunun seti, oyunun kendisinden daha pahalıya satılan oyunlar\t323 / 12,918 (2.5%)\t40 oyundan 1'inde Steam'nin liste fiyatlarına karşı kart arbitrajı görülmektedir\nKayıt kapsamındaki ücretsiz oynanabilir oyunlar\t795\tVe Valve, her bir ürünün fiyatını oyun içi harcama birimi $9 olarak belirliyor\n\nBu da ekonomik meseleyi Valve'ın lehine ve yaygın kanının aleyhine sonuçlandırıyor. Valve'in kendisinin uyguladığı fiyatlara göre, Kart toplama, yalnızca Steam'nin liste fiyatının altında satın alınan lisanslarla işe yarayan, zarar getiren bir faaliyettir — paketler, bölgesel fiyatlandırma, önemli yeniden satış. Kartlar ise geriye kalanlardır. Asıl olay satın almadır. Ve satın alma işlemi Steam tarihinde gerçekleşti.\n\nÇiftliğin aslında neyi desteklediği\n\nParçaları bir araya getirdiğinizde, çiftlik artık Valve’un hoş gördüğü bir şey gibi görünmekten çıkar ve Valve’in ihtiyaç duyduğu bir şey gibi görünmeye başlar. Çiftliğin sağladığı her girdi, Valve’nin raporladığı veya faturalandırdığı bir çıktıdır. Bir bot hesabını dışarıya doğru takip edin:\n\nBir sahte hesapbir \"toptan müşteri\", sızıntı değil\nOyun satışları\n\nOynadığı oyunları satın alır — 13,876 kart oyunlarından $0.50 kalitesiz oyunlara kadar — çünkü kartlar yalnızca sahip olduğu oyunlardan düşer.\n\n\"Çevrimiçi\" ve oyun zamanı\n\nOnları kart bırakmak için boşta bırakarak, Valve’nın etkileşim olarak gösterdiği eşzamanlı oyuncu sayısı ve oynanan saat rakamlarını besliyor — § 4.C’nin tam olarak “oyun süresini sahte gösterme” olarak adlandırdığı istatistik.\n\nKayıtlar\n\nKart alabilmesi için önce $5.00 sınırlı hesap kapısını geçmesi gerekir — her hesap için gerçek mağaza harcaması Valve defter.\n\nCüzdandaki para ve ücretler\n\nSattığı her kart, Market üzerinden geri yönlendirilir; burada düşük değerli bir kart için ücret 66.7%’a kadar çıkarken, elde edilen gelir Steam Cüzdan’da kilitli kalır.\n\nSteam. seviye Halkla İlişkiler\n\nRozetler ve seviyeler Valve vitrinleri, yalnızca setlerin oluşturulmuş olması nedeniyle mevcuttur — ve bu merdivenin en üst basamağı botlarla doludur (bkz. § 03).\n\nÇiftliği kaldırın; yukarıdaki tüm sayılar düşer — oyunun satış adedi daha azdı, “çevrimiçi” kısmı daha küçüktü, hesap hiçbir zaman kaydedilmedi, ücret hiçbir zaman tahsil edilmedi ve seviyeye hiçbir zaman ulaşılamadı. İşte bu yüzden, otomasyonu yasaklayan bir kural, milyonlarca otomatik hesapla bir arada varlığını sürdürüyor: yasak bir seçenek, faaliyet ise gelir kaynağıdır.\n\nVe nakit çekme işleminin kendisi bir değer kaybıdır Valve vergiler iki kez\n\nKart, döngünün sonu değildir. Valve'ın kendi mekanizması, bir kartın ezilip mücevherler, ve mücevherler, bir şey yapmak için harcanabilir ek paketler — üç kart daha — bunlar da satılır ya da tekrar ezilir. Her adım bir Pazar işlemi ya da dönüştürmedir ve her biri vergilendirilir. Bu döngünün yönü, aşağıda ölçülen ücret tabanından kaynaklanır ve dışarıdan bir modele gerek duymaz: bu döngü içinde satılan her kart, en az iki sent, üç ila beş arasında alınıp satılan kartlarda; dolayısıyla her çevirmede geri kazanılan miktar, harcanan miktardan daha az oluyor. Bu döngü sanal değeri yok ediyor ve onun yerine yeni, ücretli işlemlerin yapılmasını zorunlu kılıyor. Bu zararın büyüklüğüne ilişkin burada herhangi bir rakam belirtilmemiştir — Set başına elde edilen getiri, bu araştırmada ölçülmemiş olan mücevher oranlarına ve güçlendirici şanslarına bağlıdır.\n\nKoleksiyon kartısahip olunan oyundan düşenler\n→\nMücevherlerkart ezildi, ücret alındı\n→\nGeliştirme paketiüretim için harcanan mücevherler\n→\n3 yeni kartMarket'te satıldı, komisyon alındı\n↶\n\nBurada yalnızca mekanikler belirtilmiştir ve bunlar Valve’a aittir — kartlar mücevhere dönüşür, mücevherlerle booster paketleri üretilir, booster paketlerinden kartlar elde edilir — her biri Steam Koleksiyon Kartları SSS’sinde belgelenmiştir ve her aşama vergilendirilebilir bir Pazar etkinliğidir. Döngü mekaniklerinin kaynağı: Valve, Steam Koleksiyon Kartları SSS ↗.\n\nBu sadece geçici bir durum değil. Bu, yıllara dayanan sağlam bir temele sahip bir sektör.\n\nTek bir anlık görüntü tesadüf olabilir. Bu nedenle, kamuya açık kart botu dizini, 2022’den 2026’ya kadar Wayback Machine aracılığıyla her sezonluk Steam indirim döneminde bir kez okundu — botların taşıdığı sabit stok ve her indirim döneminde aynı hesaplar. Ekonomi bir anda ortaya çıkıp kaybolmaz; istikrarlı bir operatör çekirdeği ile varlığını sürdürür ve zirve noktasında Stokta üç milyon tam set mevcut 2023 Kış indirimi sırasında — tek bir anda, tek bir dizinde tutulan, değeri yaklaşık üç yüz bin TF2 anahtarı.\n\nKamuya açık bot dizininde bulunan eksiksiz kart setleri, Steam satışa göre\n\nHer sezonluk indirim için steam.supply/CardBots adresinden bir Wayback anlık görüntüsü. Fare imlecini üzerine getirdiğinizde, o anlık görüntüdeki kurdan hesaplanan TF2 anahtarlarının değerini görebilirsiniz.\n\n0.0M\n0.9M\n1.8M\n2.6M\n3.5M\nA’22\nS’23\nW’23\nS’24\nW’24\nS’25\nS’26\n401Satışlar genelinde tespit edilen farklı bot hesapları\n597 satıştan 5’inde veya daha fazlasında yer alan — istikrarlı çekirdek\n162022–2026 yılları arasında düzenlenen 7 müzayedenin her birinde yer aldı\n3,22 milyonStokta bulunan Peak setleri (Kış 2023) ≈ $570k–790k anahtar\nBir satış elemanının rozet basamakları en üstten nasıl görünür?\n\nTalep tarafı, arz tarafıyla eşleşiyor. Kamu sektöründe 2024 Yaz İndirimi rozet sıralaması arşivlendi 2026-07-16 ↗, bir numaralı hesap satış rozetini kazanmıştı 1,740,645 kez — 1,74 milyon adet on kartlık set, 17,4 milyon kart tek bir profil süslemesine dönüştürülmüştür. Satışın kendi piyasa fiyatı üzerinden ($0.50 bir set) bu, ~$870,000 kartın değerine göre; gerçekte satın alındığı şekilde — botların seviyesini yükseltmek için takas edilen TF2 anahtarları, anahtar başına yaklaşık 7,6 set — bu ~229,000 tuş, yaklaşık $410,000–$570,000 reel anlamda. İkinci hesap: 552,000 setleri, ~$130,000–181,000. Hiç kimse bunun için oynamaz. Bu satın alınır ve satın alma işleminin her aşaması, Valve’ün tasfiye ettiği bir işlemdir.\n\nYöntem ve sınırlar: Her bir anlık görüntünün listelediği botlar arasında set-stock değeri toplanır; sayı Anlık görüntülerdeki bot sayısı, satışlar arasında karşılaştırılamaz; zira bazı anlık görüntülerde yalnızca öne çıkan botlar gösterilirken, bazılarında ise tam dizin gösterilir; bu nedenle stok, görünen bot sayısının en düşük seviyesi olarak değerlendirilir, tam bir sayım olarak değil. Anahtar değerleri, her anlık görüntünün ilan edilen anahtar başına set sayısının medyan değerini ve bir $1.79–$2.49 TF2 anahtarını kullanır. Kalıcılık, anlık görüntüler arasında SteamID64 ile sağlanır. 2021 yılına ait anlık görüntüler daha eski bir sayfa düzeni kullanıyordu ve bu çalışmaya dahil edilmemiştir. Veriler: çiftlik-ekonomisi-zaman-çizelgesi.json; SteamLadder’dan rozet seviyeleri; Steam Kart Borsası’ndan belirlenen fiyatlar (satış anındaki Wayback anlık görüntüleri, $0.05 bir kart).\n\nVe herhangi bir indirim kampanyası olmadığında da aynı ürün yelpazesi orada bulunuyor\n\nYukarıdaki iki fotoğraf, iki farklı grup değildir. Bunlar, farklı anlarda fotoğraflanmış tek bir filodur. Bu bölümün başında okunan dizin, bir Sezon indiriminin yapılmadığı sıradan bir gün — 2026-09-22 — ve hareketsizken bile sabit kaldı 91 bot ve 694,673 tam set: yaklaşık 186,000 TF2 tuşu, $334,000–$464,000 kart değeri, boşta bekliyor satışlar arasındaki süre. Bu, hiçbir şey olmadığında işletmenin üstlendiği minimum yükümlülüktür.\n\nVe bu da aynı işlemdir. SteamID64 ile eşleştirildi, Bu 91 bekleme modundaki botun 87’si — 96% — yukarıdaki yedi satış anlık görüntüsünde de yer almaktadır, her birinde on altı tane. Bu rehber, satış için açılıp sonrasında kapanan geçici bir tezgah değildir; bu filonun sayısını 3,22 milyon set 2023 Kış sezonunun zirve döneminde ve asla sıfıra düşmez. İndirim, ürün satıldığında gerçekleşir. Yılın geri kalanında da geçerlidir.\n\nBotların her biri için dinlenme dizini\n\nHer bir kare, 2026-09-22 dizinindeki bir botu temsil eder; bu bot, yedi satış anlık görüntüsünde de yer alıyorsa vurgulanır. 91, o gün rehberde belirtilen sayıdır; filonun büyüklüğü değildir — Satış anlık görüntülerinde 401 farklı hesap görülüyor ve dizin, farklı günlerde farklı bir kesiti gösteriyor.\n\nGeçmiş satışlarda görülen (87) Son anlık görüntüden bu yana eklenen yenilikler (4)\n\nAynı genel dizinden, oturum açılmadan yapılan satış dışı temel okuma değeri 2026-09-22’dur. Dinlenme değeri, her botun kendi ilan ettiği anahtar başına set oranı ile bunun üzerindeki $1.79–$2.49 anahtar aralığını kullanır. Örtüşme, yedi satış anlık görüntüsüyle SteamID64 üzerinden hesaplanır. Öne çıkan ve tam listeler anlık görüntüye göre farklılık gösterdiğinden, bu karşılaştırma stok ve kimliği karşılaştırır, kullanıcı sayısını değil. Aritmetik işlemler bölüm 08.\n\n03 — Merdiven\nDiğer ürün ise adınızın yanındaki sayıdır\n\nKartlar hammadde niteliğindedir. Bitmiş ürün Steam seviyesindedir ve Valve set olarak fiyatlandırılır.\n\n100Steam Seviye\nHedef seviye — sürükleyin veya ok tuşlarını kullanın\nBir tam setin fiyatı, ABD doları\n\n$0.20, veriler içindeki en ucuz tam settir; $0.74 medyan, $1.70 ise ortalamadır. Bu rakam yalnızca kartları kapsamaktadır — $5.00 kilit açma öğelerini veya oyun lisanslarını asla kapsamamaktadır.\n\n55,000XP gereklidir\n550Tüketilen tam setler\n110Sahip olunması gereken oyunlar, kendi başına oynamak\n$407.00Bu fiyata kartların maliyeti\n1,100Yanmış damla payları, minimum\n$5,500.00$5.00, hiçbir hesap yeniden kullanılmadığında kilidi açılır\nTüketilen tam setler, seviye 1'den 1,000'a kadar\n\nBir rozet zanaatı = bir tam set = 100 XP. Onluk bir aralık içindeki her seviye, bir alt aralıktan 100 XP daha pahalıdır.\n\n0\n12,625\n25,250\n37,875\n50,500\n1\n250\n500\n750\n1000\n667\n550 sets\n\nBir seviye, Valve'ın görmezden geldiği bir süs değildir. Hesaba entegre edilmiştir. Valve'in kendi Trading Cards SSS bölümünde, bir rozet oluşturmanın size ne kazandırdığına dair şu açıklama yer almaktadır: \"100 XP; bu, Steam seviyenizi yükseltebilir.\" Eğer Steam Seviyeniz artarsa, arkadaş listenizin kapasite sınırı beş kişi artacaktır, ve muhtemelen profilinizi vitrinlerle kişiselleştirme imkânını da kazanacaksınız.\" Ve ek paketler konusunda: \"Steam seviyeniz, booster paketi düşme oranınızı artırır: Seviye 10: +20%… Seviye 50: Düşme oranınızda +100% artış (yani oran iki katına çıkmıştır).\"\n\nDolayısıyla bu seviye iki şeyi belirliyor Valve: kaç kişiyle arkadaş olabileceğinizi ve ücretsiz kartların envanterinize ne kadar hızlı düştüğünü. İkincisi kademeli olarak artar — ne kadar çok set tüketirseniz, platform size o kadar hızlı ve fazla içerik sunar. Valve, ürüne yeniden yatırım döngüsünü entegre etti.\n\nDöviz kuru sabittir ve ilan edilmiştir. Bir rozet yapımı, bir tam set tüketir ve 100 XP kazandırır; \"Aynı oyun için bir seti en fazla beş kez oluşturabilirsin.\" Her on seviye atladıkça bir seviyenin XP maliyeti artar. Bu durum aşağıdaki sonuçları ortaya çıkarır ve burada yer alan hiçbir rakam tahmini değildir:\n\nSteam Seviye\tTükettiği tam setler\tBunları kendin yapmak için mutlaka sahip olman gereken oyunlar\tKayıtlara geçen en ucuz seviyede ($0.20)\tOrtalama kümesinde ($0.74)\tÖlçek\n10\t10\t2\t$2.00\t$7.40\t\n50\t150\t30\t$30.00\t$111.00\t\n100\t550\t110\t$110.00\t$407.00\t\n200\t2,100\t420\t$420.00\t$1,554.00\t\n500\t12,750\t2,550\t$2,550.00\t$9,435.00\t\n667\t22,579\t4,516\t$4,515.80\t$16,708.46\t\n\n667, varsayımsal bir rakam değildir. Bu, halka açık dizinde yer alan tek bir botun, 6,117 oyunda sahip olduğu 33,359 set arasından bir müşteriyi ulaştırabileceğini ilan ettiği en yüksek seviyedir. Dördüncü sütun, sayımda herhangi bir yerde bulunan en ucuz tam setin fiyatına göre belirlenmiş fiyat skalasını; beşinci sütun ise medyan fiyata göre belirlenmiş fiyat skalasını göstermektedir. Her ikisi de yalnızca kartların piyasa fiyatlarını yansıtmaktadır ve $5.00 kilit açma ücretini ve oyun lisanslarını tamamen hariç tutmaktadır.\n\nEğri nasıl kontrol edildi, çünkü Valve bunu yayınlamıyor\n\nValve rozet oranını belirtir (\"Her 100 XP, sana Steam seviye daha kazandırır\") ve ardından bunu riskten korur — \"(en azından başlangıçta)\" — artış bilgisini yayınlamadan. Yukarıda kullanılan eğri standart eğridir; bu eğride, onluk bir blok içindeki her seviye, bir alt bloktan 100 XP daha pahalıdır. Bu varsayım değil, dizinle karşılaştırılarak doğrulanmıştır: ilan edilen maksimum seviyesi, oyun başına beş zanaat sınırıyla değil, stokuyla sınırlı olan her bot için, Bu eğriden hesaplanan seviye, botun bildirdiği seviyeyle tam olarak örtüşüyor — 541’e karşı 541, 494’e karşı 494, 464’e karşı 464. Üst sınırın geçerli olduğu durumlarda ise hesaplanan rakam birkaç seviye daha yüksek çıkıyor; bu da, maç başına kadro derinliğine de bağlı olan bir üst sınırın yapması gereken şeydir. 667 seviyesinin üzerindeki eğri hakkında herhangi bir iddiada bulunulmamaktadır.\n\n02 numaralı bölümün yanındaki çizelgeyi okuduğunuzda, iş modelinin yapısı ortaya çıkıyor. Bir hesabı 500 seviyesine çıkarmak için, birinin 12,750 tam set toplaması gerekir. Bu setlerin her biri en az iki hesabın düşme kotasını gerektirir; bu hesapların her biri $5.00 kapısını geçmiştir ve her biri oyuna sahiptir. Bir profilin en üstünde yer alan bir gösteriş numarası, altında bulunan en az 25,500 harcanmış düşme kotasına dayanır. Valve o işlemi kaybetmiyor. Valve ise işlemin her bir ayağının karşı tarafıdır.\n\n04 — İstatistikler\nBu madde tarımı genel hatlarıyla tanımlamamaktadır. Tarımın unsurlarını tek tek sıralamaktadır.\n\n§ 4.C, genel bir bot önleme hükmü değildir. Bu maddede sıralanan örnekler, bir kart çiftliğinin ürettiği iki şeyi arka arkaya belirtmektedir.\n\n\"Steam’daki İçerik ve Hizmetlerle herhangi bir şekilde etkileşim kurmak amacıyla, aşağıdakiler dahil ancak bunlarla sınırlı olmamak üzere, hiçbir türde komut dosyası, bot, makro veya insan kontrolü dışında çalışan diğer sistemler (‘Otomasyon’) kullanamazsınız:\n\nSteam hesap oluşturma sürecini otomatikleştirmek,\nOyun istatistiklerini tahrif etmek (örneğin, galibiyet veya mağlubiyet sayılarını, XP’yi, oyun süresini şişirmek),\nGerçek kullanıcı katılımı olmadan ödül kazanmak veya ilerleme kaydetmek,\n\"Bilgiye dayalı bir değerlendirme yerine önceden belirlenmiş eylemler yoluyla sonuçları etkilemek veya kullanıcıları bildirmek dahil olmak üzere, otomatik yöntemlerle değerlendirme sistemlerine (mesela akran değerlendirmeleri veya 'overwatch' gibi) katılmak.\"\n— Steam Abone Sözleşmesi § 4.C ↗ arşivlendi 2026-09-24 ↗ · aynen alınmış ve alıntılanmış 2026-09-22\n\"…oyun zamanı\"\n\nBoşta geçen saatler hayali saatler değildir. ASF SSS’si bu soruyu doğrudan yanıtlıyor — \"ASF aracılığıyla elde edilen oyunların oynama süresi neden artmıyor?\" — şunlarla birlikte: \"Öyle, ama gerçek zamanlı değil. Steam, oyun süresini belirli aralıklarla kaydeder ve buna göre güncelleme planlar… genellikle yaklaşık 30 dakikada bir güncellenir.\"\n\nBu saatler, Valve’un kayıtlarına, Valve’in mağaza sayfalarına ve Valve’nin kendi sitesinde yayınladığı eşzamanlı oyuncu sayılarına yansıtılır Steam Grafikler ↗ arşivlendi 2026-09-23 ↗. Bu rakamlarda, aktif olmayan bir hesap ile oyun oynayan bir hesap arasında bir ayrım yapılamamaktadır. Platformun dışarıya açıkladığı etkileşim rakamları, platformun kendi kurallarına göre oyun oynamayan hesapları da içeren bir kullanıcı kitlesi üzerinden hesaplanmaktadır.\n\n\"…kullanıcıların gerçek görüşleri olmadan\"\n\nBu, Valve tarafından yazılmış, “kullanılmayan kart bırakma” kavramının tanımıdır. Aynı zamanda, Steam Seviyesi’nin, rozetinin, booster paketi almaya hak kazanma koşullarının ve bununla birlikte gelen profil XP’sinin de tanımını oluşturmaktadır — ASF SSS’si bu aracı doğrulamaktadır \"ek paket alma imkânını korur\", çünkü resmi istemciyle aynı şekilde oturum açıyor.\n\nDolayısıyla ödül sistemi ve yasaklanmış eylem, iki farklı açıdan bakıldığında tek bir mekanizmadır. Valve, ödülün beceriye değil zamana bağlı olarak elde edilmesini sağladı; ardından, o zamanı harcayan kişi dışında başka hiçbir şeyin ödül elde etmesini yasaklayan bir madde yazdı.\n\n05 — Ticari kullanım tuzağı\nÇiftlik kartıyla yapılan her çıkış, lisansın yasakladığı bir çıkıştır — ve Valve girişte bir ücret almaktadır\n\nİşte bu kısım, “sorumlu” bir şekilde kart toplamakla çözülemez. Lisans, kişisel ve ticari olmayan kullanım içindir; bir kartın toplanmaya değer hale gelmesi, ancak kişisel kullanım olmaktan çıktığı anda gerçekleşir.\n\n§ 2.A — lisans\n\n\"Valve işbu belge ile, İçeriği ve Hizmetleri kendi amaçlarınız doğrultusunda kullanmak üzere münhasır olmayan bir lisans ve hak vermektedir ve siz de bunu kabul edersiniz.\" kişisel, ticari olmayan kullanım (işbu belgede veya ilgili Abonelik Koşullarında ticari kullanımın açıkça izin verildiği durumlar hariç).\"\n\n§ 2.G — kısıtlama\n\n\"Aşağıdakileri yapma hakkınız yoktur: … (iii) İçeriği ve Hizmetleri veya bunların herhangi bir bölümünü ticari amaçlarla kullanmak, bu Sözleşmenin başka bir yerinde (Abonelik Koşulları veya Kullanım Kuralları dahil) açıkça izin verilen durumlar hariç.\"\n\n§ 3.D — ücret\n\n\"Valve, Abonelik Pazarı’ndaki işlemler için bir ücret talep edebilir. Olası tüm ücretler, işlemin tamamlanmasından önce size bildirilecektir.\"\n\nÜçünü bir arada okuduğunuzda pozisyon kapanır\n\nElinde tutulan bir kart, bir çiftlik için hiçbir değer taşımaz. Satılan, takas edilen veya mücevherlere dönüştürülen bir kart, değer yaratmak için kullanılmıştır — ve Valve, kendi yaptırım mektubunda buna ne ad verdiğini belirtmiştir: 170 botun işletmecisine, hesabın \"Steam'da koleksiyon kartlarını yasadışı olarak toplamak için kullanılmıştı; bunun yanı sıra, sadece ticari faaliyetlerle sınırlı olmayan ilgili faaliyetler de gerçekleştirilmişti.\" O durumda kartlar piyasaya çıktı. Satışlar tamamlandı. Komisyon alındı. Yasak ise daha sonra geldi.\n\nO kapıdaki ücret 15% değildir. Kiralanmış bir kartta bu ücret üçte ikiye ulaşır.\n\n§ 3.D Yedekler \"bir ücret\". Bir çiftliğin fiilen ürettiği kartlarda, bu ücret reklamda belirtilen ~15% ile hiç alakası yoktur. Topluluk Pazarı, 5% Steam işlem ücreti ve 10% oyun ücreti; her birinin alt sınırı $0.01’dır (Valve’un kendi Topluluk Pazarı SSS’si). Bir sentten listelenen bir kartta bu katlar şunlardır fiyat: alıcı üç sent öder; bunun ikisi komisyon ücretidir. Aşağı yuvarlama kuralı, 15% rakamını, 15%’a kadar yükselen fiili bir vergiye dönüştürür 66.7% kart pazarının tam olarak hangi seviyede olduğu — kart başına birkaç sent.\n\nTopluluk Pazarı’ndaki bir satışta, satıcının talep ettiği fiyat üzerinden hesaplanan efektif ücret\n\n5% Steam + 10% oyun, her biri en az $0.01. Gölgelendirilmiş aralık, koleksiyon kartlarının fiilen takas edildiği aralıktır — kart başına yaklaşık $0.03–$0.05.\n\n0%\n10%\n20%\n30%\n40%\n50%\n60%\n70%\ncards\n$0.01\n$0.10\n$0.20\n$0.30\n$0.40\n$0.50\n66.7%\nSatıcı şunu istiyor:\tSteam 5% (en az $0.01)\tMaç 10% (dakika $0.01)\tMasraflar alıcıya aittir\tToplam ücret\n$0.01\t$0.01\t$0.01\t$0.03\t66.7%\n$0.03\t$0.01\t$0.01\t$0.05\t40.0%\n$0.05\t$0.01\t$0.01\t$0.07\t28.6%\n$0.08\t$0.01\t$0.01\t$0.10\t20.0%\n$1.00\t$0.05\t$0.10\t$1.15\t13.0%\n\n10% oyun ücreti, kartı düzenleyen uygulamaya gider; 5% ise Valve’ye aittir ve Valve’ün kendi oyunlarında ve temel envanter öğelerinde ücretin tamamı Valve’e kalır. Her halükarda para çiftçiden çıkıyor — üç sentlik bir kartın satışı bir sent kâr getirirken, iki sent kaybedilir. Bunu, bir çiftliğin ürettiği yüz binlerce beş sentin altındaki kart satışıyla çarpın ve \"Valve'nin tahsil edebileceği ücret\" iş modelidir, bir dipnot değil. Kaynak: Steam Topluluk Pazarı SSS — Ücretler ↗ arşivlendi 2026-09-21 ↗, 2026-09-22 olarak okunur; eğri, yayınlanan bu iki faiz oranı ve bunların $0.01 taban seviyeleri üzerinden aritmetik olarak hesaplanır.\n\nBu durumdan kaçınabilecek hiçbir araç yapılandırması yoktur. Araç, tek bir kişi tarafından, tek bir hesap üzerinden, son derece ihtiyatlı bir şekilde çalıştırılabilir — ancak o kişi, cüzdan bakiyesi karşılığında tek bir “farming” yoluyla elde edilmiş kartı sattığı anda, § 2.G’deki aynı hüküm, on bin kart satıcısının işletmecisine uygulandığı gibi ona da uygulanır. Bu nedenle Valve, kendi pazarındaki hemen hemen her kart satıcısına karşı uygulayabileceği bir ihlal maddesini saklı tutmuş, ancak fiilen hepsine karşı bunu uygulamayı reddetmiştir. Bu sıklıkta uygulanan bir kural, kural değildir. Bu bir seçenektir. Bu serginin ortaya koyduğu soru, kart çiftçilerine neden göz yumulduğu değil; asıl soru, bir kart satan tek bir kullanıcıya karşı bu seçeneğin neden uygulandığı, oysa bu kartların beslediği ticari kart ekonomisi — ticaret hizmetleri, seviye atlama botları, toplu satıcılar — açık bir şekilde devam ederken, en büyük gruplarından biri Valve çalışanı tarafından denetleniyor (§ 08). Kural ihlali, küçük ölçekli sahiplere karşı uygulanırken, sistemlere karşı göz yumuluyor.\n\n06 — Yürürlük kaydı\nÖnceden haber verilmeden, dalgalar halinde ve telefon numarası üzerinden yayılıyor\n\nValve, önceden bildirim gerektirmeyen yetkiyi, otomasyon maddesinden hemen sonraki madde olarak sözleşmenin içine ekledi.\n\n\"Valve, yasadışı olan, Hile veya Otomasyon teşkil eden ya da Steam Çevrimiçi Davranış Kurallarını ihlal eden herhangi bir davranış veya faaliyet nedeniyle Hesaplarınızı veya belirli bir Aboneliğinizi kısıtlayabilir veya sonlandırabilir. Valve’un, Aboneliklerinizi ve/veya Hesabınızı feshetmeden önce size bildirimde bulunma yükümlülüğü olmadığını kabul edersiniz.\"\n\n— Steam Abone Sözleşmesi § 4.D ↗ arşivlendi 2026-09-24 ↗ · kelimesi kelimesine doğrulanmış 2026-09-22\n\n1,000+ bot · ticaret yasağı uygulandı. \"Görünüşe göre bu hesap, bir bot hesapları ağını yönetmek için kullanılmış. Bot kullanımı, Steam Abone Sözleşmesi’ni ihlal etmektedir.\"\n\n170'den fazla bot · kalıcı olarak yasaklandı, 2017 Kış İndirimi. \"Bu hesap, Steam'da koleksiyon kartlarını yasadışı bir şekilde toplamak ve bununla ilgili, sadece ticari faaliyetlerle sınırlı olmayan diğer faaliyetlerde kullanılmıştır. Hesap kalıcı olarak engellenmiştir ve Steam Destek ekibi bu konuyla ilgili ek destek sağlayamaz.\"\n\n120'den fazla bot · kalıcı olarak engellendi. \"Bu ve diğer hesaplar, ağ altyapımızı aşırı yüklemek amacıyla kullanıldı; bu da Steam çevrimiçi davranış kurallarının ihlali anlamına gelir.\"\n\n— Steam ArchiSteamFarm numaralı SSS’nin “Bunun yüzünden kimse yasaklandı mı?” başlıklı bölümünde yer alan destek mesajları. Kaynak ↗ · kelimesi kelimesine doğrulanmış 2026-09-22\nVaka 4 — Haziran 2025, VAC atıl durumda olan CS2’lere yönelik yasaklar\n\nYukarıdaki üç olaydan daha geç bir olay, projenin kendi takip sisteminde kaydedilmiştir: Yalnızca bu araç aracılığıyla Counter-Strike 2’yi boşta çalıştıran hesaplar şunları almıştır: VAC yasak — hile önleme amaçlı olan türden, idari amaçlı olan değil. Sorumlunun görüşü, boşta kalmanın buna yol açamayacağı yönündedir, çünkü bu \"Steam'a, belirli bir oyunu oynadığımızı söylemekten başka bir şey yapmaz.\" Bunun nedeni tartışmalı. Hesapların engellendiği gerçeği ise tartışma konusu değil.\n\n— ArchiSteamFarm tartışma #3440, 26 Haziran 2025'te açıldı ↗ · oku 2026-09-22\n\nAna hesabın nasıl ortadan kalkacağı\n\nAynı başlık altında bir proje ortağı, yasaklama kuralını şöyle açıklıyor: hesaplar yasaklanabilir \"zincir yoluyla\", eğer aynı telefon numarasını kullanıyorlarsa — \"Bu, yasaklanan hesapla bağlantılı 'temiz' hesaplara yayılan tek bir VAC yasağı olabilir.\"\n\nSteam Guard bir telefon numarası gerektirir. Farmlar, operatörün telefon numarası üzerinden oluşturulur. Dolayısıyla yaptırımlar tek kullanımlık hesaplarla sınırlı kalmaz: ortak tanımlayıcıyı takip ederek kütüphaneyi, arkadaş listesini ve envanteri barındıran hesaba kadar uzanır. Bu, bir proje katılımcısının, tek bir eylemin operatörün ana hesabını çiftlikle birlikte nasıl ortadan kaldırdığını açıkladığı mekanizmadır — ve bu nedenle, bir yaptırım dalgasında yaşanan kayıp $5 hesapla ölçülmez. (ASF GitHub tartışması #3440’da bir proje katılımcısı tarafından açıklanmıştır; kayıtlarda resmi bir Valve onayı veya resmi bir emsal bulunmamaktadır.)\n\nAynı paragraf, beş yıl arayla, üç farklı emlakçıdan\n\nTarım faaliyetlerini ihlal sayan madde — kişisel, ticari olmayan bir lisansın ticari amaçla kullanılması — sadece çiftliklere özgü değildir. Bu, Steam’un ticaret faaliyetleri nedeniyle bir hesabı kapatırken her zaman öne sürdüğü gerekçedir ve bu gerekçe hazır bir şablon olarak sunulur. Aşağıda, beş yıl arayla üç farklı, adı belirtilen temsilciden bu bildirimleri alan kişiler tarafından yayınlanan üç örnek yer almaktadır.\n\n29 Eylül saat 19:56'da Steam Destek ekibinden gelen mesaj\n\n\"Yazıştığınız hesap, Steam Abone Sözleşmesi'nin şartlarını ihlal ettiği için kilitlenmiştir. Bu hesap, ticaret faaliyetleri, topluluk bildirimleri ve diğer faktörler temelinde ticari amaçlarla kullanıldığı tespit edilmiştir.\"\n\nBu kilit kalıcıdır ve Steam Destek ekibi bu konuda size daha fazla yardımcı olamaz.\n\nElimizdeki tüm bilgileri paylaştığımız için bu yardım talebini kapatıyorum. Bu konuyla ilgili artık yanıt almayacağınızı lütfen unutmayın.\n\nSaygılarımla,\n\"Hal\"\n\nBu yardım talebi kapatılmıştır.\n29 Eylül 2020. Alıcı tarafından şu yorumla paylaşıldı: \"RIP Trading.\" — @gergelyszabo94 ↗\nDestek Ekibinden Mesaj Steam 12 Temmuz saat 22:41'de\n\n\"Yazıştığınız hesap, Steam Abone Sözleşmesi'nin şartlarını ihlal ettiği için kilitlenmiştir. Hesap, ticaret faaliyetleri, topluluk bildirimleri ve diğer faktörler temelinde ticari amaçlarla kullanıldığı tespit edilmiştir.\"\n\nBu kilit kalıcıdır ve Steam Destek ekibi bu konuda size daha fazla yardımcı olamaz.\n\nElimizdeki tüm bilgileri paylaştığımız için bu yardım talebini kapatıyorum. Hesap kilidi ile ilgili olarak ileride gönderilecek yardım taleplerinin yanıt verilmeksizin kapatılabileceğini lütfen unutmayın.\n\nSteam Destek\n\"Vido\"\n\nBu yardım çağrısı sona ermiştir.\n12 Temmuz 2024, Portekizce arayüz. Alıcı, profesyonel bir CS2 oyuncusudur: \"Steam destek ekibiyle zaten iletişime geçtim ama sadece otomatik yanıtlar alıyorum… Faceit'te oynayamıyorum ve profesyonel maçlara da katılamıyorum.\" — @prcs25 ↗ arşivlendi 2024-07-15 ↗\nAlıcı tarafından alıntılanmıştır, r/steamsupport\n\n\"Merhaba, yazdığınız hesap, Steam Abone Sözleşmesi’nin şartlarını ihlal ettiği için kilitlenmiştir. Bu hesabın, işlemler, topluluk bildirimleri ve diğer faktörler temelinde ticari amaçlarla kullanıldığı tespit edilmiştir.\"\n\nBu kilit kalıcıdır ve Steam Destek ekibi bu konuda size daha fazla yardımcı olamaz.\n\nElimizdeki tüm bilgileri paylaştığımız için bu yardım talebini kapatıyorum. Hesap kilidi ile ilgili olarak ileride gönderilecek yardım taleplerinin yanıt verilmeden kapatılabileceğini lütfen unutmayın.\n\nSteam Destek\n\"Sally\"\n\nÜç ayrı talepte olmak üzere toplam üç kez alındı.\n29 Mart 2025. Yazar, hesap kilidini itiraz etmiyordu — hesabı, e-posta adresiyle birlikte çalınmıştı ve erişim izni istiyordu: \"Yasakla ilgili bir şey sormuyorum ve buna itiraz etmiyorum, sadece Steam hesabıma erişmek istiyorum… Valve her talebime aynen bu cevabı kopyalayıp yapıştırıyor ve talebi kapatıyor.\" — r/steamsupport ↗, bu araştırmanın kendi şikayet veri kümesinde yer alan\n\nKelime kelime, virgül virgül, elli beş ay boyunca, üç aracı ve iki arayüz dili üzerinden. Metnin herhangi bir yerinde yapılan tek düzenleme, son cümlenin 2020 ile 2024 arasında şu şekilde sertleştirilmesidir: \"artık yanıt almayacaksınız\" ...'ye \"Gelecekteki yardım talepleri… yanıt verilmeden kapatılabilir.\" Bu kararların alınmasına yol açan süreç ne olursa olsun, mektup bu sürecin bir kaydı değildir. Belirtilen gerekçeler “ticaret, topluluk raporları ve diğer faktörler”dir — bir kategori, kaynağı bilinmeyen bir rapor ve adı belirtilmemiş geri kalan unsurlar.\n\nAynı şekilde derlenen beş vaka daha. İlk üçü aynı kategoriye giriyor ve sonuçları aynı; son ikisi ise aynı masadan gelen, aynı kelimelerle ifade edilmiş ancak farklı bir kurala yanıt veren vakalar:\n\nTarih\tHesap ne yaptı?\tNe oldu?\tKaynak\n04.12.2021\tBuff'ta alım satım — \"Buff'ta, yani P2P ticaretinde, alım satım yapmaktan başka bir şey yapmadım\"\tTopluluk yasağı: pazar yok, ticaret yok, pahalı envanter donduruldu\tr/csgomarketforum ↗ arşivlendi 2025-03-27 ↗\n06.12.2021\tBuff ve Bitskins üzerinden ekipman setleri ve yükseltme işlemleri için tek yönlü P2P takasları\tKalıcı ticari kullanım kilidi ve ortak kullanım kilidi: \"sözde görünmez modda takılı kaldım… Profilim de gizli modda takılı kaldı\"\tr/GlobalOffensiveTrade ↗ arşivlendi 2021-12-06 ↗\n20 Aralık 2024\t2017'den beri sahip olunan hesap, binlerce saat; temalı ekipman setleri ve yükseltmeler için topluluk pazarlarında takaslar\tTopluluk kilidi özelliğine sahip kalıcı kilit; önceden uyarı veya ceza puanı yok; destek \"kararlarının kesin olduğunu söylüyorlar\", yanıtlar otomatik olarak gönderilir\tr/csgomarketforum ↗ arşivlendi 2025-06-27 ↗\n23 Aralık 2024\tBir yıl aradan sonra geri dönen kullanıcı, VPN üzerinden cüzdanına para yatırdı \"sadece genel internet güvenliği için\"\tTopluluktan kalıcı olarak uzaklaştırma cezası ile hiçbir gerekçe gösterilmedi: \"Yasak kalıcıdır ve daha fazla bilgi verememektedirler; ayrıca, yanıt verilmeden başka biletler de kapatılabilir.\" 196 beğeni, 340 yanıt\tr/steamsupport ↗\n04.08.2026\tİran'dan yıllardır yapılan alışverişler; yazar, hiçbir zaman gönderi paylaşmadığını, Market'i hiç kullanmadığını ve forumlara hiç girmediğini belirtiyor\tTopluluk erişimi kilitlendi 2038 yılına kadar üzerinde \"yaptırım uygulanan bölgeler\"; bilet, Azul adlı bir temsilci tarafından kapatıldı. Aynı hesaba ait, aynı İran IP adresinden yapılan iade talebi bir yıl önce onaylanmıştı. Kütüphane ve para Valve’da kalır.\tr/pcgaming ↗\n\nSon satır, diğerlerinden farklı bir kural içerir — ticari kullanım değil, yaptırımlara uyum — ve bu satır, cevabın yapısının tamamen aynı olması nedeniyle buraya dahil edilmiştir: bir kategori, kanıt yok, itiraz hakkı yok, kapatılmış bir bilet. Ayrıca, diğerlerinde bulunmayan bir soruyu da gündeme getirir. Hesaba hizmet sunmak yasadışıysa, yıllarca yapılan ödemeleri kabul etmek de yasadışıdır. Bu iki durumdan biri yanlış olmalı ve bunlardan sadece biri müşteriye bir maliyete yol açar.\n\nSekiz mesajın tamamı 2026-09-22 tarihinde okundu — 2021 ve Aralık 2024 tarihli başlıklar Internet Archive anlık görüntüleri aracılığıyla, geri kalanı ise Reddit’in halka açık arayüzü üzerinden okundu; zira Reddit, veri toplayan sunucunun doğrudan taleplerini reddetti. 2020 ve 2024 tarihli iki mektup, hâlâ yayında olan orijinal gönderilere ekli ekran görüntülerinden transkripsiyonlanmıştır. Bu soruşturma kapsamında, söz konusu hesapların hiçbirinin masum ya da suçlu olduğu iddia edilmemektedir — asıl mesele de tam olarak budur. Ne okuyucu ne de düzenleyici kurum bu mektuptan bir şey anlayamaz.\n\nKaynaklara ilişkin not — işletmeci ölçeğindeki kayıplar\n\nBu araştırma kapsamında görüşü alınan işletmeciler, şu mertebede zararlar bildirdiler: her biri beş ila on bin hesap tek seferlik denetim dalgaları kapsamında, çiftlikle birlikte ana hesaplar da incelenir. Söz konusu anket, bir bulgu olarak değil, birinci elden raporlama olarak burada kaydedilmiştir. Bu değerin yayınlanmış bir örneklem büyüklüğü, sabit bir toplama tarihi veya hesap başına doğrulama yoktur ve bu sayfadaki diğer hiçbir sayı buna bağlı değildir; bölüm 02’deki buna dayanan iki satır, bu şekilde işaretlenmiştir.\n\nBunun belirtilmesi, iki nedenden ötürü “atlanmaması”dır. Yukarıdaki zincirleme yasaklama mekanizması, tam da bu örüntüye ilişkin belgelenmiş açıklamadır. Ve bir düzenleyici kurum, Valve'dan bu konuyu netleştirecek tek kaydı talep edebilir: otomasyon nedeniyle kaç hesap işlem gördü, hangi dalgalarda ve bu hesapların her biri mağaza kapatılmadan önce mağazada ne kadar harcama yaptı. Bu kayıt ortaya çıkana kadar, rakam olduğu yerde kalır — rapor edilmiş, atfedilmiş ve kanıtlanmamış olarak.\n\n07 — Asimetri\nAynı masanın iki tarafı\n\nBu ispat standardını, kendi destek operasyonuna uygulanan Valve standardıyla karşılaştırın. Sağdaki sütun, bu dosyanın kendi olay kayıt defteridir ve orada yer alan çekincelerle birlikte aktarılmıştır.\n\nTicaret amacıyla bir müşteri\n\n2020–2026 yılları arasında kaydedilen sekiz vaka\n\nDavranış\nÜçüncü taraf pazar yerlerinde ürün satmak veya satın almak; bir vakada ise herhangi bir davranış söz konusu değildi — hesap çalınmıştı.\nSunulan kanıtlar\nYok. \"Ticaret verileri, topluluk raporları ve diğer faktörlere dayanarak.\"\nDuyuru\nYok. Valve, § 4.D’de şu hususu saklı tutmuştur: \"Valve, sözleşmeyi feshetmeden önce size bildirimde bulunmak zorunda değildir.\"\nTemyiz\n\"Bu kilit kalıcıdır ve Steam Destek ekibi bu konuda size daha fazla yardımcı olamaz.\"\nBilet\nİlk yanıtla kapatıldı. Diğer talepler \"cevap verilmeksizin kapatılabilir.\"\nUlaşım\nProfil, arkadaş listesi, sohbet, Market, envanter ve gerçek parayla satın alınan her türlü öğe.\nSüre\nKalıcı.\nYüksek hacim için otomatikleştirilmiş bot filosu\n\n694,673 adet tam set, 91 botta halka açık stokta mevcut\n\nDavranış\nBinlerce hesapta aynı anda otomatik, başsız komut dosyalarını çalıştırarak kartları atıl hale getirmek, toplu olarak rozetler oluşturmak ve endüstriyel ölçekte set takası yapmak.\nSunulan kanıtlar\nHerkese açık olarak yayınlanan bot dizinleri (steam.supply, SteamLvlUp) ve milyonlarca üyeye sahip halka açık gruplar.\nDuyuru\nHiçbir müdahale. 88.97% herhangi bir yasak içermemektedir; kalan yasakların 99.8%’si sadece görünüşle ilgili.\nTemyiz\nGerek yok. Filolar, kesintiye uğramadan, yıllarca süren kullanım ömürleri boyunca kesintisiz olarak çalışır.\nBilet\n—\nUlaşım\nSınırsız envanter değişimi, rozet seviye atlama ve piyasa likiditesi.\nFayda: Valve\n$26.8M+ asgari mağaza harcaması (hesap başına $5.00 giriş kapısı) artı 15% Topluluk Pazarı işlem kesintisi.\nBunun sonucunda ortaya çıkan soru, açıkça ifade etmek gerekirse\n\nKartları veya öğeleri manuel olarak takas eden bireysel bir müşteri, § 4.C (otomasyon) veya § 2.G (ticari kullanım) maddeleri uyarınca kalıcı ve temyiz edilemez bir yasakla karşı karşıya kalır. Binlerce hesapta başsız botlar çalıştıran otomatik bir çiftçilik filosu, 88.97% oranında hiçbir müdahaleye maruz kalmadan açık bir şekilde faaliyet gösterir. Valve her ikisinin de lehtarıdır.\n\nBu asimetri ekonomik niteliktedir: Bireysel tüccarlar platformdan değer elde ederken, otomatikleştirilmiş kart filoları Valve’in mağaza harcamaları geçidiyle (hesap başına $5.00) milyonlarca birim akıtmakta ve her yeniden satışta işlem ücretlerini artırmaktadır. Yaptırımlar yazılı kurallara göre değil, gelir modeline göre uygulanmaktadır.\n\n08 — Yönetişim\nKart ekonomisini kim denetler?\n\nBu dosyanın tekrar tekrar ortaya çıkan bulgusu — yani Steam’ün etrafındaki üçüncü taraf katmanının personelinin Steam’ün içinden sağlandığı — kart ekonomisinde de geçerlidir ve bu durum belirli bir sonuca varır: Valve'in yaptırımlarının gerçekte ne işe yaradığını bağımsız olarak kimse hesaplayamaz, çünkü bunu hesaplayabilecek taraf o katmanın içinde yer almaktadır. Aşağıdaki tüm bilgiler, 2026-09-22'daki Valve'nin kendi halka açık grup ve profil sayfalarından alınmıştır ve herkes tarafından bir tarayıcıda yeniden üretilebilir.\n\nEn büyük kart takas grubunun moderatörlüğünü Valve numaralı çalışan yapıyor Valve çalışan\n\nCardTrades ↗ kendi başlığında kendisini şu şekilde tanımlamaktadır: \"Steam Kart Değişimi resmi grubu\" ve taşır 97,114 üye. Listede yer alan moderatörleri — yani o grubun yönetim yetkilerini elinde bulunduran hesaplar — şunlardır: Mickmane, Çavuş Fopper ve afarnsworth ↗.\n\nBu son profil, Valve’nin kendi site işaretlemesinde bir Valve çalışanı olarak işaretlenmiştir — sayfada şunlar yer almaktadır: class=\"profile_header_valve_employee\" — konumunu şu şekilde belirtir: Bellevue, Washington, ve şunlara aittir: Valve, Steam ve Steam Koleksiyon Kartları Grubu gruplar. SteamID64 76561197960434622, 12 Eylül 2003 tarihinden beri üye.\n\nBu gözlem kişisel değil, yapısaldır ve değil Bir noktaya değinmek gerekirse — bir kart takas grubunun moderatörü bot kullanmıyor ve burada bunun aksini gösteren hiçbir şey yok. Asıl mesele, şu maddedeki 07. bölüm. Steam Card Exchange, üçüncü taraf bir ticari kart hizmetidir; üçüncü taraf hizmetler aracılığıyla kart ticareti yapmak, Valve’ın sıradan hesapları kalıcı olarak kilitlediği tam da bu tür bir davranıştır, \"ticaret, topluluk raporları ve diğer faktörlere dayalı olarak ticari amaçlarla kullanılır.\" Valve numaralı çalışan, doksan yedi bin kişilik bu hizmetin resmi topluluk grubunda listelenmiş bir moderatör rolüne sahiptir.\n\nBurada hiçbir kişiye yönelik herhangi bir suistimal iddiası ileri sürülmemektedir, ve bu rolün neleri içerdiğine dair herhangi bir çıkarımda bulunulmamaktadır. Asimetri, şu bulgudan kaynaklanmaktadır: sıradan bir hesap üçüncü taraf bir kart veya skin hizmetiyle ilişkili olduğunda, yanıt kanıt gösterilmeden kapatılan bir bilet ve kalıcı bir kilitlenmedir; hizmet bu hizmet olduğunda ise, Valve numaralı bir çalışan moderatör listesindedir ve bu düzenleme Valve'in kendisi tarafından yayınlanan bir sayfada görülebilir. Burada sorulan, bu dosyadaki diğer her yerde sorulanla aynıdır: Varsa yazılı yetki belgesini sunun — ve eğer gerekmiyorsa bunu yazılı olarak belirtin, çünkü 06 bölümündeki sekiz kişiye bunun tam tersi söylendi.\n\nYasak listesi katmanı ve bunu kim yönetiyor? Gönüllü moderatörÜçüncü taraf hizmet\n\nSteambans.com grubu (arşivlenmiş) ↗ (canlı ↗ arşivlendi 2025-12-03 ↗) korunmuş tür tanımında soyunu şöyle belirtir: \"Resmi Steambans.com Steam Topluluk Grubu. SteamBans.com, eski bir konsepte dayanan yepyeni bir hizmettir. VALVe'nin eski WONID programında küresel yasak listeleri yıllardır aktif olarak kullanılıyordu. STEAMID'e geçiş yapıldığında, bu yeni sisteme özel olarak tasarlanmış bir hizmet geliştirmemiz doğal bir adım oldu. Ancak biz daha fazlasını da istedik. *. 2013 yılında kapanan Steambans için arşiv sayfası.\" Listede yer alan yöneticileri şunlardır: devicenull ve killahinstinct_ ↗.\n\nSöz konusu yönetici hesabı şudur: değil Valve numaralı çalışan — üzerinde “çalışan” işareti bulunmamaktadır. Bu kişi, alışılmadık derecede yüksek bir statüye sahip bir gönüllüdür: bir üyesidir Topluluk Moderatörleri (414 üye, bir grup olarak tanımlanan) \"Steam'un Topluluk Moderatörleri tarafından oluşturulmuştur\"), şunun: Viki Koordinatörleri, ...'dan Steam Topluluk Pazarı, ve Valve programı ile ön gösterim grupları arasında şunlar yer almaktadır: Valve Boru hattı, Steam Müşteri Beta Sürümü, Mobil Kimlik Doğrulama Beta Sürümü, Yeni Steam Topluluk Beta Sürümü, Steam Laboratuvarlar, Steamworks ve Dolandırıcılık URL’lerini Bildir. SteamID64 76561197960794555.\n\nAyrıca bu çemberin içinde yer alan ve Steambans’ı herkese açık grup listesinde doğrudan gösteren: msart ↗ (gruplar listesi ↗), SteamID64 76561197977933359, profilinde kendi ifadesiyle şöyle belirtilmiştir: \"steamid.uk'yi ve Steam ile ilgili ya da olmayan pek çok başka siteyi yönetiyorum\", ve on altı gruptan oluşan birbirine bağlı bir ağı yöneten — SteamIDcouk (ana grup \"Sid web sitesi\"), SidAdmins, SidBans, steamideu, Steam3ID, s-id ve SArchive bunların arasında.\n\nsteamid.uk, bu sayıyı kendisi de belirtmektedir. SSS bölümünde şöyle yazmaktadır: \"SteamID'yi kim yarattı? SteamID web sitesi, ağ altyapısı ve güvenlik sistemleri 76561197977933359 tarafından yönetilmektedir.\" İki cevap aşağıda, verilerin nereden geldiği belirtilmiştir: \"SteamID, veri toplama amacıyla öncelikle Steam Web API'sini kullanır.\" Aynı sayfada, farklı barındırma sağlayıcılarında bulunan çok sayıda özel sunucu, tesis dışı geliştirme, depolama ve metin arama sunucuları ile ayrı bir yedekleme tesisi hakkında bilgi verilmektedir.\n\nInternet Archive’da saklanan kayıtlar aracılığıyla doğrulanmıştır: 3 Aralık 2025 tarihli Steambans grubu anlık görüntüsü ↗, şunun 14 Eylül 2024 tarihli operatör profili özeti ↗ve steamid.uk SSS sayfası, 1 Nisan 2026 tarihli anlık görüntü ↗, 2026-09-22'dan doğrudan okunan eşleşen veriler.\n\nBunun anlamı nedir ve ne değildir?\n\nYasak listeleri, SteamID çözümleme ve kart ticareti, kimin güvenilir olduğuna, kimin kimliğinin tespit edilebileceğine ve bir öğenin değerinin ne olduğuna karar veren üç hizmettir. Bu üç hizmetten hiçbiri Valve tarafından işletilmemektedir. Her birinde, kontrolü elinde tutan kişiler Valve’un yörüngesi içinden geliyordu: kart hizmetinin resmi grubunun moderatör listesinde işaretlenmiş Valve numaralı bir çalışan; yasak listesi grubunu yöneten ve sürüm öncesi programa erişimi olan, uzun süredir görev yapan Valve numaralı bir topluluk moderatörü; aynı çevrede yer alan bir özel şahıs tarafından işletilen kimlik belirleme hizmeti. Üç hizmet, üç kontrol paneli, Valve kişinin zaten itibar kazandırdığı üç kişi.\n\nGrup üyeliği bir iş ilişkisi değildir ve bunların hiçbiri bir suçlama niteliğinde değildir. Bu, yönetişimle ilgili bir gerçektir ve işte bu nedenle yaygın olarak öne sürülen savunma — Bunlar üçüncü taraflar; onları kontrol edemeyiz — kabul edilmek yerine test edilmelidir. Kontrolü elinde tutan kişiler Valve’a yabancı değiller. Valve, onlardan ne istediğini –eğer bir şey istemişse– söyleyebilecek konumdadır; dışarıdan kimse bunu öğrenemez.\n\nKimse sayılmıyor. Sonuç bu.\n\nSteam kimlik alanı, birbirine bitişik bir tamsayı aralığıdır. Bu aralığı tarayarak kaç hesabın yasaklandığını, kaç hesabın kısıtlandığını ve bir ticaret yasağının arkasında ne kadar stok bulunduğunu bildirmek bir araştırma programı değildir — bu sadece bir döngü ve bir API anahtarıdır. Valve bu anahtarı kendisi dağıtır, şu adreste: steamcommunity.com/dev/apikey. Yine de Bu nüfus sayımını yayınlayan bağımsız bir kurum yoktur. Ne bir düzenleyici kurum, ne bir gazeteci, ne bir akademisyen, ne de bir tüketici örgütü. Steam’deki yaptırımların boyutuna ilişkin tek kamuya açık rakamlar, Valve’ın bahsetmeyi uygun gördüğü rakamlardır.\n\nBu yetenek eksik değil. Elimizde mevcut. Kimlik alanını büyük ölçekte çözümleyen ve indeksleyen hizmet — steamid.uk — kendi SSS bölümünde şöyle diyor ki: \"veri toplama için öncelikle Steam Web API'sini kullanır\" ve bunu birden fazla özel sunucu, tesis dışı depolama alanı, metin arama makineleri ve ayrı bir yedekleme tesisinde çalıştırmaktadır. Bu sistem, tek bir şahıs tarafından işletilmektedir. Onun yasak listesindeki kardeş grubu, Valve'in yayın öncesi programlarına erişimi olan, uzun süredir görev yapan bir Valve topluluk moderatörü tarafından ortaklaşa yönetilmektedir. Sayımı yayınlayabilecek konumda olan tek parti, Valve'un etki alanı içinde yer almaktadır ve sayıyı yayınlamamaktadır.\n\nBu, dosyanın her yerde tespit ettiği yapının aynısıdır. Steam ekonomisiyle ilgili temel kararları alan her hizmet — kime güvenilir, kimler tanımlanabilir, bir öğenin değeri nedir, kimler yasaklanmıştır — nominal olarak üçüncü taraf olmakla birlikte, pratikte Valve’a yakındır. Steam Kart Değişimi bu modelin bir istisnası değildir; bu modelin başka bir örneğidir. Bunların bağımsız operatörler olduğu iddiası, tam da hiç kimse bunu bir sayı üzerinde test edemediği için Valve için geçerlidir.\n\n10,88 milyonluk Hesap Sayımı: 88.97% Değiştirilmemiş\n\nArchiSteamFarm kurulum tabanı, Valve genelinde denetlendi GetPlayerBans son nokta (10,880,610 hesap, 55 dakika). Yalnızca sınırsız olmayan alt küme, $26.8M+ mağazada yapılan minimum harcama tutarı ($5.00 giriş eşiği). 9,680,599 hesapları (88.97%) herhangi bir yasaklama içermemektedir, ve geri kalan 99.8%'lar ise otomatik ticareti aktif halde bırakan, sadece görünüşte bir topluluk yasağı getiriyor.\n\n5,360,499Sınırsız ASF üyeleri (Steam'ların görüntülenen sayısı)\n10,880,610Taranan toplam API girdisi sayısı (sınırlı + sınırsız)\n9,680,599Hiçbir zaman yasaklanmadı (88.97%)\n1,200,011Herhangi bir Steam yasağı (11.0%) — 99.8% kozmetik\n55 dakikaTüm nüfusu sayımlamak için temel bir unsur\nAdli Kanıtlar ve Kapsamlı Nüfus Sayımı\n\nYasak türlerine göre dağılım grafikleri, yaptırım uygulandığı andaki hesap yaşı, açılış yılı grupları (2020–2026) ve coğrafi olarak kendi beyanlarına dayalı veriler dahil olmak üzere ayrıntılı demografik dağılım, bu konuya özel nüfus sayımı araştırmasında yayınlanmıştır.\n\n10,88 milyonluk tam yasak sayımını açın (Ek VI) →Bölüm 4 — Varlık Kimliği Engellemesi →\n\nÖyleyse sorulması gereken soru şudur ve buna yalnızca Valve cevap verebilir: Hangi tanımlayıcı veya yetkinlik geri çekildi, hangi tarihte, kimin kararıyla ve bunun hedef aldığı operatörler üzerinde ne tür ölçülebilir bir etkisi oldu? — sayım yapmaya çalışan dışarıdaki herkes üzerindeki etkisiyle karşılaştırıldığında. Bağımsız denetimi sona erdiren bir değişiklik, bir güvenlik önlemi olarak duyurulmuş olması nedeniyle tarafsız hale gelmez. İşte bu nedenle, bir üst bloktaki nüfus sayımı mevcut değildir.\n\n09 — Yöntem ve sınırlar\nNeler okundu ve neler iddia edilmedi\n\nBu sayfadaki tüm alıntılar, 2026-09-22 adresindeki canlı kaynaktan alınmış ve kelimesi kelimesine aktarılmıştır. Buradaki hiçbir bilgi, veri kazıma işlemi, pazar yeri kimlik bilgileri veya özel veri setlerinden elde edilmemiştir.\n\nDört veri kümesi ve bunlar üzerinde yapılan hesaplamalar\n\nHer biri, bir terminalden tekrarlanabilen tek bir genel istektir. Hiçbir hesap kullanılmadı, hiçbir pazar yerine giriş yapılmadı ve kimlik bilgisi gerektiren hiçbir uç noktaya çağrı yapılmadı.\n\nVeri kümesi\tNereden geldiği\tBundan ne hesaplandı?\nKart sayımı\n13,876 maç\tSteam Card Exchange’in yayınladığı rozet fiyat listesi; bu, onların ürünlerini görüntüleyen aynı veri akışıdır halka açık fiyat sayfası ↗ arşivlendi 2026-08-04 ↗\tKart basan oyunlar, set başına kart sayısı, farklı kart türleri ve her bir tamamlanmış setin piyasa fiyatı. Medyan değerler ve $23,586.57 toplamı, bu araştırmanın aritmetik verilerini oluşturmaktadır.\nOyun fiyatları\n13,713 çözüldü\tValve'un kendi genel mağaza uç noktası, store.steampowered.com/api/appdetails, cc=us, yalnızca fiyat alanı, toplu olarak\tKart içeren bir oyunun liste fiyatının medyan değeri ve dağılımı; tamamlanmış setinin satış rakamının oyunun kendisinin satış rakamını aşan oyunların sayısı.\nBot stoğu\n91 bot, 694,673 set\tHerkese açık kart-bot dizini şu adreste bulunur: steam.supply/CardBots ↗, görüntülenildiği gibi, oturum açmaya gerek yok\tStokta bulunan toplam set sayısı, minimum kart sayısı, düşme toleransı alt sınırı ve farklı hesaplar için bot başına kontenjan alt sınırı.\nÇapraz kontrol\n21 paylaşılan bot\tsteamlvlup.net/cardbots ↗ arşivlendi 2026-02-10 ↗, aynı botların yer aldığı bağımsız bir dizin\tYalnızca doğrulama amaçlıdır. Her iki listede de yer alan 21 bot için, toplam hisse senedi miktarı şunlara karşılık gelir: 0.03%; tek bir botun verdiği en büyük tutarsızlık değeri 1.36% olup, bu durum dakikalar arayla gerçekleştirilen iki canlı envanter taramasıyla tutarlıdır.\n\nİkinci dizinde belirtildiği üzere kaynak gösterimi: veriler şu kaynak tarafından sağlanmıştır: SteamLvlUp, şu lisans kapsamında: CC BY 4.0 arşivlendi 2026-09-23 ↗; burada yalnızca üçüncü bir tarafın stok rakamlarına ilişkin bağımsız bir kontrol amacıyla kullanılmıştır ve robot başına satırların tek tek gösterilmesi yerine toplu olarak birleştirilip karşılaştırılması şeklinde değiştirilmiştir. Steam Card Exchange ve steam.supply, yukarıda bağlantı yoluyla kaynak olarak belirtilmiştir. Oyun fiyatları Valve'a aittir. Kart, oyun ve set isimleri ile görseller Valve'e veya yayıncılara aittir; bunlar, herhangi bir hak iddiası veya lisans olmaksızın, piyasa hakkındaki gerçekler olarak aktarılmıştır.\n\nPlanlanan iki ölçüm gerçekleştirilmedi ve bunların yerine başka bir ölçüm yapılmadı. Steam’un kendi Topluluk Pazarı son noktaları — fiyat özeti, arama/görüntüleme, fiyat geçmişi — toplayıcı ana bilgisayara hiçbir şey döndürmez ve Steam Topluluk tartışma sayfaları ona HTTP 403 yanıtı verir; dolayısıyla bu sayfadaki hiçbir rakam, canlı Market verilerinden elde edilmemiştir. Günlük sıfırlama sırasında kart dağıtımlarını sayacak olan satış hacmi yöntemi, oturum açılmış bir Steam oturumu gerektirir; Bu soruşturmanın tutanaklarında, herhangi bir pazar yeri kimlik bilgisinin kullanılmadığı belirtilmiştir ve bu ifade kayda geçirilmiştir. Bot-stock tabanı, bot olmadan ölçülebilen kısımdır.\n\nBirincil kaynaklar\n\nSteam Abone Sözleşmesi ↗ arşivlendi 2026-09-24 ↗ — § 2.A, § 2.G, § 3.D, § 4.C, § 4.D.\nSteam Destek — Sınırlı Kullanıcı Hesapları ↗ — $5.00 eşiği ve kısıtlanmış özellik listesi.\nValve — Steam Koleksiyon Kartları SSS ↗ — düşürme mekaniği ve $9 ücretsiz oynama oranı.\nArchiSteamFarm SSS ↗ ve tartışma #3440 ↗.\nSteam Topluluk grubu ve profil sayfaları, doğrudan okunur; bkz. bölüm 08.\nsteamid.uk SSS, Internet Archive anlık görüntüsü 2026-04-01 ↗.\nAlıcıları tarafından yayınlanan sekiz adet Steam Destek Kilidi bildirimi, 2020–2026; bunlar, bölüm 06’da bağlantıları ile birlikte listelenmiştir.\n\nNeler talep edilmiyor\n\nValve için kart çiftçiliğinden elde edilen gelir rakamı tahmin edilmemiştir. Hiçbir araç için aktif hesap sayısı belirtilmemiştir ve 1,39 milyon adetlik dağıtım kotası değil çiftliğe ait hesapların sayısı — bkz. bölüm 02’deki not. Hiçbir kişi suistimalle suçlanmamaktadır; bir kişinin adı geçtiğinde, bu, o kişinin Steam adlı kamuya açık kullanıcı adı ile, kendi kamuya açık rolü kapsamında, Valve’ın yayınladığı bir sayfadan alınmıştır. 06. bölümdeki sekiz kilitli hesabın hiçbirinin masum ya da suçlu olduğu iddia edilmemektedir; bulgu, hesapla değil, mektupla ilgilidir. 02. bölümdeki operatör kaybı rakamları, birinci elden raporlanmıştır ve tedarik notu. steamid.uk SSS bölümü, canlı sayfanın bir bot doğrulama sürecinin arkasında olması nedeniyle Internet Archive’daki bir anlık görüntüsünden alıntılanmıştır. Herhangi bir yasaklama sayımının yapılmaya çalışılıp engellendiği iddiasında bulunulmamaktadır — sadece böyle bir sayımın yayınlanmadığı tespit edilmiştir. 667’nin üzerindeki Steam Seviye eğrisi modellenmemiştir.\n\nNeden araç konu değildir?\n\nArchiSteamFarm şunu belirtmektedir ki \"Valve tarafından yetkilendirilmemiştir\" ve bu sayfada kendisine herhangi bir suçlama yöneltilmemiştir. Bir ölçüm aracı olarak kullanılır, çünkü bu ekonomide işleyişi kamuya açık ve yazılı olarak belgeleyen tek aktördür. Valve tüm kanıtları tek bir paragrafta özetleyebilir: hangi ticari otomasyonları onayladığını ve geri kalanlarla ilgili olarak operatör başına ne yaptığını yayınlayabilir.\n\nSonraki makale: Piyasanın kendisinin nasıl fiyatlandırıldığı → · fiyat merdiveni ve listeleme sınırı → · Steam numaralı ürünler taşınmayacaktır →",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Bir bot çiftliği, Valve’nin dükkanındaki bir sızıntı değildir. Bu bir müşteri."
          },
          {
            "level": 2,
            "id": null,
            "text": "Bir çiftliğin gerçekte ne olduğu, adım adım"
          },
          {
            "level": 3,
            "id": null,
            "text": "Satın al"
          },
          {
            "level": 3,
            "id": null,
            "text": "Oyun satın al"
          },
          {
            "level": 3,
            "id": null,
            "text": "Boşta\nAraç, hesabı Steam ağına başsız bir şekilde oturum açar, \"rozetlerinizi analiz eder\", oynanabilir oyunların listesini oluşturur ve başlatır \"Uygun oyunu oynamak ve oyunun tamamen tamamlanıp tamamlanmadığını düzenli aralıklarla kontrol etmek.\" Bu mekanizmaya ilişkin bakım sorumlusunun açıklaması: bu \"Steam'a, belirli bir oyunu oynadığımızı söylemekten başka bir şey yapmaz.\""
          },
          {
            "level": 3,
            "id": null,
            "text": "Damlalar bitti\nHer başlık sonludur. \"Her oyunda sabit sayıda kart düşer. Bunların hepsini topladığınızda (tam setin yaklaşık yarısı), oyun artık farm yapmak için uygun bir seçenek olmaktan çıkar.\" Üretime devam etmek isteyen bir çiftlik, sürekli kart satın almak zorundadır. Kart arzı, satın alımlar yoluyla kısıtlanmaktadır — bu, sistemin tasarımı gereği ve Valve'nin lehine bir durumdur."
          },
          {
            "level": 3,
            "id": null,
            "text": "Para çekme\nKart, üç seçenekten biriyle elden çıkarılır: Topluluk Piyasası’nda satılır, takas edilir ya da mücevher haline getirilir. Her biri bir Abonelik Piyasası işlemi ya da takastır ve § 3.D’de şu hüküm yer almaktadır: \"Valve, Abonelik Pazarı’ndaki işlemler için bir ücret talep edebilir.\" İşte tüm bu süreci bir güvenlik ihlaline dönüştüren adım budur — bkz. 05."
          },
          {
            "level": 2,
            "id": null,
            "text": "Bir çiftlik bir sent bile kazanamadan, çoktan Valve ödemiştir"
          },
          {
            "level": 3,
            "id": null,
            "text": "Satın alınan şeyin gerçekte ne kadar büyük olduğu"
          },
          {
            "level": 3,
            "id": null,
            "text": "Bir kümenin büyüklüğü ne kadardır?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Lisansın maliyeti nedir?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Tamamlanmış kümenin döndürdüğü değer"
          },
          {
            "level": 3,
            "id": null,
            "text": "694,673 kümelerinin bulunduğu yer"
          },
          {
            "level": 3,
            "id": null,
            "text": "Bu metnin neyi ifade ettiği ve neyi ifade etmediği"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ayrıca, Valve’nin fiyatlarıyla tarım kâr getirmiyor"
          },
          {
            "level": 3,
            "id": null,
            "text": "Çiftliğin aslında neyi desteklediği"
          },
          {
            "level": 4,
            "id": null,
            "text": "Oyun satışları"
          },
          {
            "level": 4,
            "id": null,
            "text": "\"Çevrimiçi\" ve oyun zamanı"
          },
          {
            "level": 4,
            "id": null,
            "text": "Kayıtlar"
          },
          {
            "level": 4,
            "id": null,
            "text": "Cüzdandaki para ve ücretler"
          },
          {
            "level": 4,
            "id": null,
            "text": "Steam. seviye Halkla İlişkiler"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ve nakit çekme işleminin kendisi bir değer kaybıdır Valve vergiler iki kez"
          },
          {
            "level": 3,
            "id": null,
            "text": "Bu sadece geçici bir durum değil. Bu, yıllara dayanan sağlam bir temele sahip bir sektör."
          },
          {
            "level": 3,
            "id": null,
            "text": "Kamuya açık bot dizininde bulunan eksiksiz kart setleri, Steam satışa göre"
          },
          {
            "level": 3,
            "id": null,
            "text": "Bir satış elemanının rozet basamakları en üstten nasıl görünür?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ve herhangi bir indirim kampanyası olmadığında da aynı ürün yelpazesi orada bulunuyor"
          },
          {
            "level": 3,
            "id": null,
            "text": "Botların her biri için dinlenme dizini"
          },
          {
            "level": 2,
            "id": null,
            "text": "Diğer ürün ise adınızın yanındaki sayıdır"
          },
          {
            "level": 3,
            "id": null,
            "text": "Tüketilen tam setler, seviye 1'den 1,000'a kadar"
          },
          {
            "level": 3,
            "id": null,
            "text": "Eğri nasıl kontrol edildi, çünkü Valve bunu yayınlamıyor"
          },
          {
            "level": 2,
            "id": null,
            "text": "Bu madde tarımı genel hatlarıyla tanımlamamaktadır. Tarımın unsurlarını tek tek sıralamaktadır."
          },
          {
            "level": 3,
            "id": null,
            "text": "\"…oyun zamanı\""
          },
          {
            "level": 3,
            "id": null,
            "text": "\"…kullanıcıların gerçek görüşleri olmadan\""
          },
          {
            "level": 2,
            "id": null,
            "text": "Çiftlik kartıyla yapılan her çıkış, lisansın yasakladığı bir çıkıştır — ve Valve girişte bir ücret almaktadır"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 2.A — lisans"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 2.G — kısıtlama"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 3.D — ücret"
          },
          {
            "level": 3,
            "id": null,
            "text": "Üçünü bir arada okuduğunuzda pozisyon kapanır"
          },
          {
            "level": 3,
            "id": "fee-ladder",
            "text": "O kapıdaki ücret 15% değildir. Kiralanmış bir kartta bu ücret üçte ikiye ulaşır."
          },
          {
            "level": 3,
            "id": null,
            "text": "Topluluk Pazarı’ndaki bir satışta, satıcının talep ettiği fiyat üzerinden hesaplanan efektif ücret"
          },
          {
            "level": 2,
            "id": null,
            "text": "Önceden haber verilmeden, dalgalar halinde ve telefon numarası üzerinden yayılıyor"
          },
          {
            "level": 3,
            "id": null,
            "text": "Vaka 4 — Haziran 2025, VAC atıl durumda olan CS2’lere yönelik yasaklar"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ana hesabın nasıl ortadan kalkacağı"
          },
          {
            "level": 3,
            "id": null,
            "text": "Aynı paragraf, beş yıl arayla, üç farklı emlakçıdan"
          },
          {
            "level": 3,
            "id": null,
            "text": "Kaynaklara ilişkin not — işletmeci ölçeğindeki kayıplar"
          },
          {
            "level": 2,
            "id": null,
            "text": "Aynı masanın iki tarafı"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ticaret amacıyla bir müşteri"
          },
          {
            "level": 3,
            "id": null,
            "text": "Yüksek hacim için otomatikleştirilmiş bot filosu"
          },
          {
            "level": 3,
            "id": null,
            "text": "Bunun sonucunda ortaya çıkan soru, açıkça ifade etmek gerekirse"
          },
          {
            "level": 2,
            "id": null,
            "text": "Kart ekonomisini kim denetler?"
          },
          {
            "level": 3,
            "id": null,
            "text": "En büyük kart takas grubunun moderatörlüğünü Valve numaralı çalışan yapıyor Valve çalışan"
          },
          {
            "level": 3,
            "id": null,
            "text": "Yasak listesi katmanı ve bunu kim yönetiyor? Gönüllü moderatör Üçüncü taraf hizmet"
          },
          {
            "level": 3,
            "id": null,
            "text": "Bunun anlamı nedir ve ne değildir?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Kimse sayılmıyor. Sonuç bu."
          },
          {
            "level": 3,
            "id": null,
            "text": "10,88 milyonluk Hesap Sayımı: 88.97% Değiştirilmemiş"
          },
          {
            "level": 3,
            "id": null,
            "text": "Adli Kanıtlar ve Kapsamlı Nüfus Sayımı"
          },
          {
            "level": 2,
            "id": null,
            "text": "Neler okundu ve neler iddia edilmedi"
          },
          {
            "level": 3,
            "id": null,
            "text": "Dört veri kümesi ve bunlar üzerinde yapılan hesaplamalar"
          },
          {
            "level": 3,
            "id": null,
            "text": "Birincil kaynaklar"
          },
          {
            "level": 3,
            "id": null,
            "text": "Neler talep edilmiyor"
          },
          {
            "level": 3,
            "id": null,
            "text": "Neden araç konu değildir?"
          }
        ],
        "links": [
          "https://help.steampowered.com/en/faqs/view/71D3-35C2-AD96-AA3A",
          "https://github.com/JustArchiNET/ArchiSteamFarm/wiki/FAQ",
          "https://steamcommunity.com/tradingcards/faq/",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260924114457/https://store.steampowered.com/subscriber_agreement/",
          "https://steamladder.com/ladder/badges/2861690/",
          "http://web.archive.org/web/20260716205303/https://steamladder.com/ladder/badges/2861690/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/farm-economy-timeline.json",
          "https://store.steampowered.com/charts/",
          "http://web.archive.org/web/20260923183013/https://store.steampowered.com/charts/",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://github.com/JustArchiNET/ArchiSteamFarm/discussions/3440",
          "https://x.com/gergelyszabo94/status/1311004678633795585",
          "https://x.com/prcs25/status/1811893857253982720",
          "http://web.archive.org/web/20240715122902/https://x.com/prcs25/status/1811893857253982720",
          "https://reddit.com/r/steamsupport/comments/1fjmgc5/what_to_do_when_your_steam_account_gets_hacked/mkelm2y/",
          "https://www.reddit.com/r/csgomarketforum/comments/r87owv/psa_my_steam_account_just_got_banned/",
          "http://web.archive.org/web/20250327203008/https://www.reddit.com/r/csgomarketforum/comments/r87owv/psa_my_steam_account_just_got_banned/",
          "https://www.reddit.com/r/GlobalOffensiveTrade/comments/r9xql9/d_recently_received_commercial_ban_for_what_seems/",
          "http://web.archive.org/web/20211206034804/https://www.reddit.com/r/GlobalOffensiveTrade/comments/r9xql9/d_recently_received_commercial_ban_for_what_seems/",
          "https://www.reddit.com/r/csgomarketforum/comments/1hhxx7m/d_permanently_locked_on_steam_for_commercial_use/",
          "http://web.archive.org/web/20250627014045/https://www.reddit.com/r/csgomarketforum/comments/1hhxx7m/d_permanently_locked_on_steam_for_commercial_use/",
          "https://www.reddit.com/r/steamsupport/comments/1hkctwt/permanent_ban_with_no_explanation/",
          "https://www.reddit.com/r/pcgaming/comments/1vf24lu/warning_to_all_gamersexpats_steam_took_my_money/",
          "https://steamcommunity.com/groups/card-trading-card-trades",
          "https://steamcommunity.com/id/afarnsworth",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/groups/steambans",
          "https://steamcommunity.com/groups/steambans",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/id/killahinstinct_",
          "https://web.archive.org/web/20240914124859/https://steamcommunity.com/id/msart",
          "https://steamcommunity.com/id/msart/groups/",
          "http://web.archive.org/web/20260401154714/https://steamid.uk/faq/",
          "https://phishdestroy.io/steam_dossier/tr/enforcement_audit.html",
          "https://phishdestroy.io/steam_dossier/tr/#evidence-blackout",
          "https://www.steamcardexchange.net/index.php?badgeprices",
          "http://web.archive.org/web/20260804200309/https://www.steamcardexchange.net/index.php?badgeprices",
          "https://steam.supply/CardBots",
          "https://steamlvlup.net/cardbots",
          "http://web.archive.org/web/20260210171205/https://steamlvlup.net/cardbots",
          "https://steamlvlup.net/",
          "https://creativecommons.org/licenses/by/4.0/",
          "http://web.archive.org/web/20260923221628/https://creativecommons.org/licenses/by/4.0/",
          "https://phishdestroy.io/steam_dossier/tr/market_economics.html",
          "https://phishdestroy.io/steam_dossier/tr/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/tr/elite_skins.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/tr/card_economy.content.json",
      "export_json_sha256": "600e220116dd2a4bb03b8fb89ff07c9dea2692011a3e2b40b2a81264fe3f6976"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "tr/elite_skins.html",
      "language": "tr",
      "title": "Tek ürün, iki fiyat sistemi — “Steam” Dosyası",
      "source_url": "https://phishdestroy.io/steam_dossier/tr/elite_skins",
      "source_html_sha256": "e8a22090e253fc52b1e8f1c178a7f00758fa38d05ed160a0d47d5433fbf8bcbc",
      "exported_at": "2026-09-29T00:20:45.102Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "register",
            "source": "https://phishdestroy.io/steam_dossier/tr/elite_skins#register"
          },
          {
            "id": "",
            "source": "https://phishdestroy.io/steam_dossier/tr/elite_skins#selected"
          }
        ],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "elite_skins.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/tr/elite_skins.pdf?v=print-20260929-v5",
        "sha256": "4a357c9e665ee7c7fb86f4221371559b0aa24b90e76eb6e2dc8190ecd6845468",
        "bytes": 96941,
        "pages": 7
      },
      "integrity": {
        "signed_object": "elite_skins.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "elite_skins.content.json.asc",
        "digest_file": "elite_skins.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify elite_skins.content.json.asc elite_skins.content.json",
          "sha256sum -c elite_skins.content.json.sha256"
        ]
      },
      "content": {
        "text": "EK IV / PİYASA YAPISI / 20 EYLÜL 2026\nElite Skins Kaydı — $1,800'lık Piyasa Tavanı\n\nBir ürün. İki fiyat sistemi.\n\nBU BÖLÜMÜN KANITLADIĞI ŞEY\n\nBu kayıt, beş harici borsada Steam’ın $1,800 Topluluk Pazarı listeleme üst sınırının üzerinde fiyatlandırılmış tüm CS2 skin kategorilerinin ampirik bir sayımını ortaya koymaktadır. Bu kayıt, 248’ın doğruladığı, 18,394 aktif listelemeyi ve $78.6 milyon ilan edilmiş likiditeyi temsil eden üst düzey kategorilerin 100% Valve’ın resmi pazar yerinde bulunmadığını kanıtlamaktadır. Gerçek piyasa fiyatlarını arayan satıcılar, yapısal olarak harici platformlara yönelmek zorunda kalırken, aynı zamanda tamamen Steam'un temel işlem mekanizmalarına güvenmek zorunda kalmaktadır.\n\nWhat this means — the Community Market listing ceiling\n\nSteam’s own market refuses a listing above roughly $1,800. A seller may ask less, never more. Items whose market price sits above that line therefore cannot be sold at that price on Steam at all — which is the mechanism that moves those sales to third-party venues while the item itself never leaves Valve’s inventory system.\n\nSection 13 — the off-Steam price gap →\n\n← Yönetici özetine geri dön\n\nSteam Bir Community Market ilanı için üst sınır yaklaşık $1,800. Bu özet kapsamında fiyatlandırılan beş üçüncü taraf pazar yerinde, 419 CS2 ürün kategorilerinde, bu sınırın üzerinde en ucuz gerçek zamanlı satış teklifi bulunuyor — ve bunlardan 402, 95.9%, adreslerinde Steam listesi hiç bulunmuyor. Bu iki kişi birlikte, en az $82.4 milyon değerinde, 18,641 sitesinde listelenen kopyalara sahiptir. Bir fiyatın geçerli sayılabilmesi için ikinci bir satış platformunun da onay vermesi gerekmektedir, 248 Bu kategorilerin tümü doğrulanmıştır — ve hepsinde, “100%,” adlı eser “Steam”da yer almamaktadır. En sevdiğim şey bir çıkartma | Titan (Holo) | Katowice 2014 adresinde $66,285, birbirinden 5.2% aralıkta bulunan dört platformda fiyatlandırılmış, ancak Valve'daki hiçbir platformda yer almamıştır. Tam sıralama tablosu, görseller ve derecelendirme bilgileri fiyat merdiveni atlası.\n\n419'daki tüm girişleri incele ↓Atlası aç ↗Yöntemi okuyun\n248sınırın üzerinde fiyat belirleyen iki veya daha fazla pazar yeri kategorisi\n18,394beş farklı satış platformunda listelenen kopyalar\n$78.6Mbu ilanların taban değeri\n100%bunların hiçbiri Steam adresinde yer almıyor\n\nDüzeltme · Bu sayfada daha önce doğrulanmamış bir fiyat belirtilmişti\n\nBu sayfanın önceki bir sürümünde, “Souvenir AK-47 | Point Disarray” başlıklı ürünün bir pazaryerinde $148,954 fiyatla satışa sunulduğu, Steam adresinde ise $119. fiyatla listelendiği belirtilmişti. Bu satır, tek bir rafta yer alan tek bir kopyaya dayanmaktadır ve bunu doğrulayan başka bir pazaryeri bulunmadığından, bu bir fiyat değil, talep edilen fiyattır; ayrıca söz konusu ürün artık sayfada yer almamaktadır. Buradaki her başlık rakamı artık, en az iki pazar yerinin bağımsız olarak üst sınırın üzerinde fiyatlandırdığı 248 kategorileriyle sınırlıdır. Satırın kendisi kaldırılmamıştır — hâlâ aşağıdaki kayıtta yer almaktadır ve onu alt sınıra indirgenmesine neden olan derecelendirme, fiyat merdiveni atlası.\n\n01 / aktif satış emirlerinde bulunan para\nÖlçülebilir dolar taban seviyesi\n\nBeş farklı pazardaki lisanslı cs2.sh anlık görüntüsünden yeniden hesaplanmıştır. Bu, tanımlanmış bir alt kümedeki asgari toplam satış fiyatıdır; satış cirosu veya CS2 ekonomisinin değerlemesi değildir.\n\n248 DOĞRULANMIŞ KATEGORİLER · 18,394 LİSTELENMİŞ NÜSHA · 5 PAZAR YERLERİ$78.62M\n\nİki veya daha fazla pazar yerinin, kendi pazarlarında Valve tarafından izin verilen sınırın üzerinde bağımsız olarak fiyatlandırdığı her bir CS2 öğesinin, ilan edilen en düşük toplam satış fiyatı.\n\nNeden bu bir taban değer, bir tahmin değil?\n\nHer bir pazar yeri için, o pazar yerinin en düşük Bir ürünü, o pazarın listelediği kopya sayısına göre talep edin. O raftaki diğer tüm kopyaların fiyatı, en düşük talep fiyatına eşit veya bunun üzerindedir; dolayısıyla gerçek ilan edilen değer daha yüksektir — bu, tahminlere dayalı değil, sistemin doğası gereği böyledir. Bu bir satış, nakit akışı veya piyasa genelinde bir değerleme değildir ve aynı fiziksel ürün birden fazla pazarda yer alabilir.\n\n419'daki tüm kaynak satırlarını kontrol et ↗\n★ Spor Eldivenleri | Çit Labirenti (Sahada Test Edildi)\n$4.68M\nAWP | Gungnir (Fabrika Çıkışı)\n$4.46M\nAWP | Dragon Lore (Fabrika Çıkışı)\n$4.34M\n★ Kelebek Bıçak | Fade (Fabrika Çıkışı Yeni)\n$4.17M\nAK-47 | Wild Lotus (Fabrika Çıkışı Yeni)\n$4.16M\n★ Kelebek Bıçak | Doppler (Fabrika Çıkışı Yeni)\n$3.64M\n\nÇubuklar, taban fiyat hesaplamasına en büyük katkı sağlayan altı kategori düzeyindeki kalemi, en büyüğüne göre ölçeklendirilmiş olarak göstermektedir. Yüksek bir çubuk, hem en ucuz satış fiyatını hem de listelenen kopya sayısını yansıtmaktadır. Aynı fiziksel ürün birden fazla pazarda yer alabileceğinden, bu rakamlar başka hiçbir pazar toplamına eklenmemelidir.\n\n02 / incelenebilir örnekler\nSınırın kapsamadığı hususlar\n\nResimler, mevcut olduğu durumlarda ürünlerin tam adlarıyla örtüşmektedir. Fiyatlar, tarihli katalogda yer alan güncel satış fiyatlarıdır; işlem kayıtları değildir.\n\n★ Butterfly Knife | Doppler (Factory New)\n\nKaynak: https://phishdestroy.io/steam_dossier/tr/elite_skins#selected\n\nÖlçülebilir fark: Steam'daki hiçbir ilan, aynı ABD doları tutarında bu tekliflerle eşleşemez. Valve'un kendi Topluluk Pazarı SSS arşivlenmiş 2026-09-21 ↗ yaklaşık1,800 dolarlık bir maksimum satış fiyatı belirtilmiştir. Satıcı yine de bu fiyatın altında bir fiyat belirleyebilir; bunun kabul edilebilir olup olmayacağı satıcının tercihine bağlıdır. Ayrı bir CSMarketCap'te1,800 doların üzerindeki ürünleri ara ↗ 28’da endekslenmiş pazarlarda Factory New Dragon Lore ürününü, yaklaşık 1.1K adet sergilenen teklifle gösterir; aynı envanter kalemi birden fazla kez sayılabilir.\n\n03 / yapısal bağımlılık\nSteam’in sınırlaması, fiyat keşfini Steam adresinin dışına çıkarıyor\n\nBu karşılaştırma yapısal niteliktedir. Ne her satış fiyatının adil olduğunu varsayar, ne de satılmamış ilanları gelir olarak değerlendirir.\n\n01 · KURAL\nSteam listeyi sonlandırır\n\nValve Community Market ilanlarının sayısının yaklaşık olarak $1,800. Cüzdan bakiyeleri de bir üst sınırla sınırlandırılmıştır ve cüzdandaki paralar nakit olarak çekilemez.\n\n02 · GÖZLEM\nDragon Lore:10,940.85 dolar\n\n5-’in pazar yeri kataloğunda şunlar yer almaktadır: 389 canlı teklifler AWP Dragon Lore (Fabrika Çıkışı) için fiyatlar $10,940.85'dan başlıyor (CSFloat katı). Daha geniş kayıt defterinde, Steam'in sınırının üzerinde 248 adresinde doğrulanmış kategoriler yer almaktadır.\n\n03 · SONUÇ\nFiyat ve transfer dağılımı\n\nDaha yüksek bir fiyat isteyen bir satıcı Steam adresine bunu yayınlayamıyorum. Harici hizmetler nakit fiyatı belirleyebilir, ancak teslimat sürecinde ürün sahipliği ve devri yine dSteamtarafından kontrol edilir.\n\nPolitika çelişkisi: Valve’a ait Abone Sözleşmesi arşivlenmiş 2026-09-21 ↗ Steam hizmetlerinin ticari kullanımını, açıkça izin verilmedikçe saklı tutar; buna karşın, 2016 açıklama arşivlenmiş 2026-09-21 ↗ Söz konusu kumar işletmecilerinin halihazırda Steam adresindeki OpenID ve otomatik hesapları kullandıkları belirtildi. Bu, Valve adresinin 2016. adresinde yer alan bu tür dış işletmecilerden haberdar olduğunun doğrudan bir kanıtıdır. Oysa resmi pazar yeri, bu yüksek değerli ürünlerin gözlemlenen fiyatlarını yayınlayamamaktadır. Bu, mimari açıdan off-Steam’deki fiyat belirleme ve işlem süreçlerine olan bağımlılıktır; Her bir pazarın sözleşme durumu için ayrı kanıt gereklidir. Bu aşırı kapasiteli işlem hacmini barındıran iki başlıca Batı pazarı, önemli yargı bölgelerinde resmi tüzel kişilikler olarak faaliyet göstermektedir — CSFloat A.Ş. (ABD’nin Delaware eyaletinde kurulmuş) ve Skinport GmbH (Almanya’nın Stuttgart kentinde kayıtlı, HRB 764879) — Steam web API’lerine ve ticaret altyapısına doğrudan dayanarak, eşler arası ürün satışlarında yüz milyonlarca tutarında işlemleri şeffaf bir şekilde gerçekleştiriyor.\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\nDört adet $100,000 satırı, CSFloat sitesinin kendi maksimum listeleme fiyatında yer almaktadır. Bu satırlar kayıt defterinde işaretlenmiştir ve değerleme olarak yorumlanmamalıdır. Arşivlenmiş CSFloat listeleme taraması yalnızca yaklaşık $6,999, değerine ulaşabildiğinden, tam >$1,800 kayıt defteri için genel katalog anlık görüntüsü kullanılmaktadır.\n\n04 / bir başka Valve oyunu\nTavanda ayrıca Dota'dan bir görüntü de yer alıyor2\n\nSkinport adresinde yapılan aynı katı “en ucuz teklif” testi sonucunda 166 CS2 kategorileri ve 3 Dota 2 kategorileri tespit edilmiştir. Bunlar ayrı bir pazar yeri anlık görüntüsüdür; bunları CSFloat adresindeki 245. sayfasına eklemeyiniz.\n\nDOTA 2 · 1 TEKLİFİ\nKahramanca Vahşi Hilal\n\nEn ucuz Skinport sorusu: $14,622.25.\n\nDOTA 2 · 1 TEKLİFİ\nKaranlık Sanatsal Pelerin\n\nEn ucuz Skinport sorusu: $8,255.16.\n\nDOTA 2 · 1 TEKLİFİ\nBozulmuş Güçlü Yıldız\n\nEn ucuz Skinport sorusu: $2,087.92.\n\nBunlar, listelenen üç eşya kategorisidir; mevcut tüm Dota 2 eşyalarını kapsamaz. Skinport'daki tarih içeren satırları inceleyin ↗ ve API belgeler ↗.\n\n05 / dayanıklılık\nBu bulgu, tam sınır değerine bağlı değildir\n\nValve Üst sınır, alıcının yerel para biriminde belirlenir; bu nedenle ABD dolarına çevrildiğinde tam bir rakam ortaya çıkmaz. Dolayısıyla, sayım her olası eşik değerinde tekrarlanır. Steam adresinde bulunmayan bu öğelerin oranı, hiçbir zaman 95%. adresinde belirtilen oranın altına düşmez.\n\nEşik değeri test edildi\tÜrün kategorileri\tListelenen kopyalar\tTaban değer\tSteam'da yer almayanlar\n$1,800\t419\t18,641\t$82,449,526\t95.9%\n$2,000\t382\t15,159\t$75,541,325\t95.5%\n$2,070\t363\t12,336\t$69,560,305\t95.6%\n$2,300\t323\t11,644\t$67,984,432\t95.0%\n$2,500\t299\t10,950\t$66,203,929\t95.0%\n\nHer seferinde bir satırı okuyun; bu satırlar, ayrı nüfus grupları değil, aynı nüfus sayımının iç içe geçmiş alt kümeleridir. “Taban değer”, her bir pazarın en düşük Listelediği kopya sayısına göre hesaplandığından, yapısı gereği raf sayısını olduğundan az gösterir. Veri kümesini aç ↗\n\n06 / sayabileceğiniz kıtlık\nBunlardan satışa sunulanların sayısı ne kadar da az\n\nBUFF, her bir ürünün rafını “float” aralıklarına ayırır ve her birinde kaç adet bulunduğunu belirtir. Bu sayede “nadir” kelimesi bir sayı haline gelir — ve ürünün durumu, dış görünüşünden ayrı olarak fiyatlandırılır.\n\n298 LİSTELENEN KOPYALAR\nAWP | Ejderha Bilgisi\n\n8 fiyatlandırılmış farklı varyantlar. En pahalısı, AWP Hatıra Modeli | Dragon Lore (Fabrika Çıkışı), soruyor $12,363 20'lık kopya rafta bulunuyor.\n\nRaftaki en iyi yüzer tutucu (0–0.01) içinde şunlar bulunmaktadır: 2 kopyalar, şunu sorarak $17,875 — ürünün sadece durumuna göre belirlenen temel satış fiyatının üzerinde, +45% tutarında bir prim.\n\n607 LİSTELENEN KOPYALAR\nM4A4 | Howl\n\n12 fiyatlandırılmış farklı varyantlar. En pahalısı, Hatıra M4A4 | Howl (Fabrika Çıkışı), soruyor $14,895 2'lık kopya rafta bulunuyor.\n\n213 LİSTELENEN KOPYALAR\nAK-47 | Wild Lotus\n\n7 fiyatlandırılmış farklı varyantlar. En pahalısı, AK-47'dan Hatıra | Wild Lotus (Fabrika Çıkışı Yeni), soruyor $14,895 2'lık kopya rafta bulunuyor.\n\n310 LİSTELENEN KOPYALAR\nAWP | Gungnir\n\n7 fiyatlandırılmış farklı varyantlar. En pahalısı, Hatıra AWP | Gungnir (Çok Az Aşınma), soruyor $14,895 2'lık kopya rafta bulunuyor.\n\nBunun bu dosyanın geri kalanı için önemi: Bunlar soyut kavramlar değildir. Her bir kupadan dünya çapında açık rafta birkaç yüz adet bulunmaktadır; her biri tek bir Steam hesabına bağlıdır ve tek bir Steam ticareti yoluyla el değiştirmiştir. Bu kadar dar bir pazarda, çalınan tek bir envanter öğesi bile ölçülebilir bir olaydır ve bu soruşturmanın başka bölümlerinde belgelenen hesap ele geçirme teknikleri, doğrudan ve sayısal olarak ölçülebilir bir kazanç sağlar.\n\nSayımlar, verilerin alındığı anda bir pazar yerindeki güncel listeleme sayısını ifade eder; mevcut toplam sayıyı değil. Özel stoklarda tutulan kopyalar burada hiçbir şekilde sayılmamaktadır. Float veri kümesini aç ↗\n\n07 / merdiven gözden kayboldu\nÜrün ne kadar pahalıysa, herhangi bir gözle görülür mekandan o kadar uzak olur\n\nAşağıdaki her basamak, farklı bir delil sınıfını temsil etmektedir. Bunlar kasıtlı olarak tek bir rakam altında birleştirilmemiştir.\n\nBasamak\tŞekil\tBu ne tür bir gerçektir?\nCeiling on Valve's own market\t~$1,800\tPublished rule, stated in the Steam Community Market FAQ.\nDearest ask several marketplaces agree on\t$66,285\tMeasured by us in this snapshot. Sticker | Titan (Holo) | Katowice 2014, quoted by four marketplaces within 5.2% of one another. An ask, not a sale.\nDearest ask seen on any single shelf\t$148,954\tOne marketplace, one copy, no second marketplace agreeing — and equal to a round CNY 1,000,000 at the snapshot rate. Listed here as the outer edge of what sellers ask, and relied on for nothing.\nPublic marketplace sale\t$49,999\tSpecialist Gloves | Crimson Kimono (FN) on CSFloat, as reported by SteamAnalyst. Platform-recorded, third-party reported.\nReported private sale\t$400,000\tAK-47 | Case Hardened, reported by PC Gamer in April 2023. Journalism, not a record we hold.\nReported offer, declined\t$1,500,000\tBlue Gem Karambit, pattern #387. No sale took place and the figure has not been independently confirmed. Included to mark the ceiling of the claims, not to assert a value.\n\nYapısal açıdan: Valve’in piyasa fiyatı yaklaşık $1,800. seviyesinde durur. Üçüncü taraf pazar yerleri, ticareti birkaçının hemfikir olduğu yaklaşık $66,000 seviyesine ve sadece birinin hemfikir olduğu yaklaşık $150,000 seviyesine taşır. Bunun üzerinde ise hiçbir işlem platformu bulunmamaktadır — Valvetarafından ihraç edilen varlıkların en büyük transferleri, listeye alınma, platform kaydı, kimlik kontrolü ve raporlama olmaksızın, bireyler arasında özel olarak gerçekleşmektedir. Transferin kendisi ise hâlâ Steam üzerinden yürütülmektedir. Değer ne kadar yüksekse, kimse onu o kadar az görebilir ve onu taşıyan altyapı baştan sona Valve’a aittir.\n\nSon iki basamak, kaynak gösterilerek alıntılanan başkalarının raporlarıdır. Bu proje, söz konusu raporları doğrulamamıştır ve herhangi bir sonuca varmak için bunlara dayanmamaktadır.\n\n419'da gözlemlenen tüm kategoriler\n\nKaynak: https://phishdestroy.io/steam_dossier/tr/elite_skins#register\n\n09 / köken ve sınırlar\nHesaplamayı kontrol edin\n\nYerel verileri ve genel kaynağı paylaşıyoruz. Sayısal başlık, yakalama tarihindeki CSFloat adresiyle sınırlıdır.\n\nValve'in kendi sınırları ve koşulları\n\nSteam Topluluk Pazarı SSS ↗ arşivlenmiş 2026-09-21 ↗ 1,800 doları civarında bir liste fiyatının üst sınırını belirtir. Bu Abonelik Sözleşmesi ↗ arşivlenmiş 2026-09-21 ↗ ticari kullanım kısıtlamalarını belirler.\n\nFiyatlar nereden geliyor?\n\nFiyatlar, hisse sayısı ve halka açık hisse aralıkları şu kaynaktan alınmıştır: cs2.sh API adresindeki piyasa verilerini, ücretli ticari abonelik kapsamında lisans anahtarı kullanarak. Hiçbir pazar yeri taraması yapılmadı ve hiçbir pazar yeri hesabı ya da kimlik bilgisi kullanılmadı. Söz konusu sağlayıcı, BUFF, Youpin, CSFloat, Skinport, C5Game ve Steam Topluluk Pazarı’nı bir araya getirmektedir; tüm rakamlar, bildirildiği şekliyle ABD doları cinsindendir. Kaynak bilgisi manifestini aç ↗ — ham anlık görüntülerinin tam uç noktalarını, yakalama zamanlarını ve SHA-256 karma değerlerini kaydeder; böylece kendi anahtarına sahip bağımsız bir okuyucu, aynı verileri alabilir ve bu sayfadaki her bir sayıyı yeniden hesaplayabilir.\n\nElde edemediğimiz şeyler\n\nSatın alınan abonelik yalnızca güncel anlık görüntüleri kapsamaktadır. Geçmişe ait ve arşiv uç noktalarına erişim imkânımız bulunmamaktaydı ve Bu sayfada herhangi bir eğilim, geçmiş fiyat veya zaman içindeki değişim hakkında herhangi bir iddiada bulunulmamaktadır. Buradaki her şey, tarihi belirtilmiş tek bir andır.\n\nCSFloat'ın daha eski kayıtları\n\nBu serginin ilk versiyonunda, 20 Eylül 2026: tarihli tek bir CSFloat katalog görüntüsünden 245 kategorisi sayılmıştı. o anlık görüntü burada kalıyor ↗. Mevcut kayıt, tek bir pazar yeri yerine beş pazar yerini kapsadığı için daha geniştir. Bu iki rakam ayrı ayrı elde edilmiştir ve birbirleriyle toplanmamalıdır.\n\nValve’ın özel icra beyanı\n\nValve’ın “2016” oyun içi eşya takası güncellemesi ↗ arşivlenmiş 2026-09-21 ↗ OpenID ve otomatik Steam hesaplarını kullanan kumar operatörlerini hedef almaktadır. Bu, tüm dış pazar yerlerine yönelik bir yasaktan daha dar kapsamlıdır.\n\nYorum sınırı\n\nBunlar tekliflerdir, satış değildir. Bir pazar adı, farklı yüzdürme özellikleri, desenleri veya etiket detaylarına sahip birden fazla fiziksel ürünü kapsayabilir. Bu kayıt, toplam piyasa değerini veya Valve sitesinin amacını yansıtmamaktadır.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Elite Skins Kaydı — $1,800'lık Piyasa Tavanı"
          },
          {
            "level": 2,
            "id": null,
            "text": "Ölçülebilir dolar taban seviyesi"
          },
          {
            "level": 3,
            "id": null,
            "text": "Neden bu bir taban değer, bir tahmin değil?"
          },
          {
            "level": 2,
            "id": null,
            "text": "Sınırın kapsamadığı hususlar"
          },
          {
            "level": 3,
            "id": null,
            "text": "★ Butterfly Knife | Doppler (Factory New)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Steam’in sınırlaması, fiyat keşfini Steam adresinin dışına çıkarıyor"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam listeyi sonlandırır"
          },
          {
            "level": 3,
            "id": null,
            "text": "Dragon Lore:10,940.85 dolar"
          },
          {
            "level": 3,
            "id": null,
            "text": "Fiyat ve transfer dağılımı"
          },
          {
            "level": 2,
            "id": null,
            "text": "Tavanda ayrıca Dota'dan bir görüntü de yer alıyor2"
          },
          {
            "level": 3,
            "id": null,
            "text": "Kahramanca Vahşi Hilal"
          },
          {
            "level": 3,
            "id": null,
            "text": "Karanlık Sanatsal Pelerin"
          },
          {
            "level": 3,
            "id": null,
            "text": "Bozulmuş Güçlü Yıldız"
          },
          {
            "level": 2,
            "id": null,
            "text": "Bu bulgu, tam sınır değerine bağlı değildir"
          },
          {
            "level": 2,
            "id": null,
            "text": "Bunlardan satışa sunulanların sayısı ne kadar da az"
          },
          {
            "level": 3,
            "id": null,
            "text": "AWP | Ejderha Bilgisi"
          },
          {
            "level": 3,
            "id": null,
            "text": "M4A4 | Howl"
          },
          {
            "level": 3,
            "id": null,
            "text": "AK-47 | Wild Lotus"
          },
          {
            "level": 3,
            "id": null,
            "text": "AWP | Gungnir"
          },
          {
            "level": 2,
            "id": null,
            "text": "Ürün ne kadar pahalıysa, herhangi bir gözle görülür mekandan o kadar uzak olur"
          },
          {
            "level": 2,
            "id": null,
            "text": "419'da gözlemlenen tüm kategoriler"
          },
          {
            "level": 2,
            "id": null,
            "text": "Hesaplamayı kontrol edin"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve'in kendi sınırları ve koşulları"
          },
          {
            "level": 3,
            "id": null,
            "text": "Fiyatlar nereden geliyor?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Elde edemediğimiz şeyler"
          },
          {
            "level": 3,
            "id": null,
            "text": "CSFloat'ın daha eski kayıtları"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve’ın özel icra beyanı"
          },
          {
            "level": 3,
            "id": null,
            "text": "Yorum sınırı"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/tr/#market-gap-section",
          "https://phishdestroy.io/steam_dossier/tr/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/tr/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/tr/skin_atlas.html#grading",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-above-the-ceiling.json",
          "https://phishdestroy.io/steam_dossier/tr/elite_skins#selected",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://csmarketcap.com/search?minPrice=1800&amp;page=1",
          "https://store.steampowered.com/agreement/?l=english",
          "http://web.archive.org/web/20260921022032/https://store.steampowered.com/agreement/?l=english",
          "https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921021947/https://store.steampowered.com/oldnews/22883",
          "https://phishdestroy.io/steam_dossier/tr/#proxy-bypass-explainer",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/skinport-floor-over-cap.json",
          "https://docs.skinport.com/items",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-float-scarcity.json",
          "https://phishdestroy.io/steam_dossier/tr/elite_skins#register",
          "https://cs2.sh/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/csfloat-catalogue.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/tr/elite_skins.content.json",
      "export_json_sha256": "0a79b7aea75ec7fe003453b18c88c9c714be5cfed610b6d43eabb643ca237690"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "tr/enforcement_audit.html",
      "language": "tr",
      "title": "Valve Nüfus Sayımı sonuçları açıklanmayacak — Steam Dosyası",
      "source_url": "https://phishdestroy.io/steam_dossier/tr/enforcement_audit",
      "source_html_sha256": "a61ba97c5be03af03edcedce7393b882e5a7488440fc115ab3eaa7127b23b0c1",
      "exported_at": "2026-09-29T00:20:42.834Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "enforcement_audit.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/tr/enforcement_audit.pdf?v=print-20260929-v5",
        "sha256": "a54d230a77daabc49d12697a2eb7fe3b5dc9afa8ff7ffef8e6a12f83f1c4ea0e",
        "bytes": 149517,
        "pages": 13
      },
      "integrity": {
        "signed_object": "enforcement_audit.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "enforcement_audit.content.json.asc",
        "digest_file": "enforcement_audit.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify enforcement_audit.content.json.asc enforcement_audit.content.json",
          "sha256sum -c enforcement_audit.content.json.sha256"
        ]
      },
      "content": {
        "text": "EK VI — VALVE NÜFUS SAYIMI SONUÇLARI YAYINLANMAYACAK\nSteam’deki hesap ağı ne kadar büyük? Kendimiz saydık.\n\nSteam üzerinde kaç tane otomasyon hesabının çalıştığına dair yayınlanmış bir rakam bulunmamaktadır. Bunun gizli tutulmasına gerek yoktur: Steam kimlik alanı, birbirine bitişik bir tamsayı aralığıdır ve Valve bu aralığı tarayan Web API anahtarını dağıtmaktadır. Bu nedenle, kendini tanımlayan en büyük topluluğu — ArchiSteamFarm topluluğu — seçtik ve Valve'nin kendi yasaklama uç noktası aracılığıyla her üyeyi bir kez taradık. Bu, ASF’nin ilk başlatıldığında, kullanıcı açıkça çıkmayı seçmedikçe veya gruba katılma ayarının işaretini kaldırmadıkça otomatik olarak Steam grubuna katılması nedeniyle kendiliğinden gerçekleşir (AutoJoinSteamGroup / İstatistikler). Bu ayar varsayılan olarak etkin olduğundan, grup üyeliği geniş bir kitleyi kapsamaktadır: aktif çoklu hesaplı ticari bot ağları, ara sıra bot çalıştıran hobi amaçlı kullanıcılar ve kişisel hesaplarında yazılımı çalıştırmış ancak varsayılan aboneliği hiçbir zaman kaldırmamış sıradan oyuncular. Bu da grup üyeliğini, yazılımın toplam erişim kapsamını gösteren işlevsel bir sayım haline getirmektedir: 10,880,610 toplam hesap sayısı ($5.00 mağaza girişini geçen, onaylanmış ve sınırsız üyelik statüsüne sahip 5,360,499 üye dahil). Sonra asıl önemli olan tek soruyu sorduk: Valve onlara gerçekte ne yaptı?\n\nBu sayfa ne değildir. Bu, Valve’ın on milyon kişiyi yasaklaması gerektiği yönünde bir argüman değildir ve kart toplayıcılarla ilgili bir şikayet de değildir. Aşağıdaki her rakamın burada yer almasının tek bir nedeni vardır: Valve yapıyor mu bireyleri kalıcı olarak yasaklamaktadır ve bunun için yazılı olarak sunduğu gerekçe, Steam’nin ticari kullanımı ve otomasyondur. Bu, aynı kuralın aynı davranışa ne ölçüde uygulandığını ölçer — bu süreçte $5.00 kilit açma, oyun lisansları ve Market ücretleri Valve toplayan bir operatör tarafından. Ortaya çıkan sonuç, çiftçilik değil, asimetridir.\n\n10,88 milyon adetYürüyen dolandırıcılar (53,5 bin)100 bin ücretli denetim ve ücretsiz denetim\n10,880,610ASF grubunun tüm üyeleri, Valve'un kendi yasaklama API'sini inceledi (sınırlı ve sınırsız olanlar bir arada)\n88.97%Hiçbir zaman yasaklanmadım — 9,680,599 hesap hala aktif\n63.06%Engellenen hesapların %0'ı ücretli ($5+ harcama) — %1 %3 aralığı (±0.39% hata payı)\n67.77%51,732 sayısındaki yargılanan dolandırıcıların hiçbirinde dolandırıcılık yasağı bulunmamaktadır (tam sayım)\n01 — Ölçek\nOn milyon hesap; bunlardan dokuzu hiç kullanılmamış\n\nKendini sayan bir popülasyon; Valve'un kendi uç noktasından bir kez okunur.\n\nNEDEN KENDİ KENDİNİ SAYAR?\nASF, sizin için gruba katılıyor\n\nİlk çalıştırmada ArchiSteamFarm set İstatistikler Varsayılan olarak \"true\" olarak ayarlanır ve Archi'nin SC Farm Steam grubuna katılır. Bir operatörün bu gruptan çıkmak için aktif olarak işlem yapması gerekir. Dolayısıyla üyelik, kurulum sayıları için bir alt sınırdır — üst sınır değildir. İstatistik özelliğini devre dışı bırakan operatörler bu sayıya dahil değildir; gerçek kurulum sayısı en az bu kadar fazladır.\n\nNE OKUYORUZ\n10,880,610 toplam giriş\n\nAPI üye listesi, sınırlı ve sınırsız olanlar dahil olmak üzere toplam 10,880,610 SteamID64 döndürdü. Steam'nin grup sayfasında ise 5,360,499 (sadece sınırsız olanlar) gösteriliyor. Her giriş bir kez ISteamUser/GetPlayerBans 2026-09-23'da. Tek bir tuşta elli beş dakika.\n\nCEVAP\n88.97% temiz\n\n1,200,011 herhangi bir Steam yasağı (11.03%) içermemektedir. Diğer 9,680,599 kayıtlarda hiçbir şey yok — ne topluluk yasağı, ne de VAC, hiçbir şey. Hesap silinmiyor. Hesap aktif durumda bırakılıyor. Tek bir kişiye yöneltilen aynı madde, o kişinin kalıcı olarak uzaklaştırılması için yeterli.\n\n10,880,610 hesaplardan kaç tanesi Valve değerine ulaşmıştır?\n\nTaranan tüm popülasyon, Valve’un herhangi bir yasak uygulayıp uygulamadığına göre ayrılmıştır. Kırmızı dilim, Valve’in bu filoya şimdiye kadar uyguladığı tüm önlemleri göstermektedir.\n\n88.97%hiç yasaklanmadı\n11.03%\nHerhangi bir yasak yok — 9,680,599 (88.97%)Steam yasağı içerir — 1,200,011 (11.03%)\n10,880,610ASF grubu üyeleri tarandı\n9,680,599Hiç yasaklanmadı — 88.97%\n1,200,011Herhangi bir yasağı uygulayın — 11.03%\n55 dakikaHepsini tek bir API anahtarıyla saymak için\nBu filonun varlığı için halihazırda ödenen tutar Valve\n\nÇiftliğin ne kadar kazandığına dair bir tahmin değil. Valve’un dükkanında halihazırda harcadığı tutarın alt sınırı — yukarıdaki sayıya uygulanan Valve’in kendi kuralından türetilmiştir.\n\n10,880,610 sayısı, API tarafından döndürülen tam ASF grup üye listesini kapsar — buna hem sınırlı hem de sınırsız hesaplar dahildir. Steam'in kendi Sınırlı Kullanıcı Hesapları Sayfada, sınırlı hesapların hesaba katılmak Steam grup üyeliği (görüntülenen grup büyüklüğüne dahil edilmezler), ancak yine de altta yatan üye listesinde görünebilirler. Sınırlandırılmamış alt küme — Steam mağazasında en az $5.00 tutarında harcama yapmış hesaplar — tam olarak 5,360,499 — Steam sayısı grup sayfasında görüntülenir; bu sayfa, Steam'nin kendi kuralına göre sınırlı hesapları hariç tutar. $5.00 alt sınır hesaplaması yalnızca bu sınırsız alt küme için geçerlidir.\n\n5,360,499sınırsız üyeler\n(Steam'un görüntülenen grup sayısı)\n×\n$5.00Valve'un kendi asgari değeri\nsınırlı olmaktan kurtulmak için\n=\n$26,802,495mağaza harcamalarına ilişkin alt sınır\nsınırsız alt küme tarafından\n\nBu, Valve’in filonun sınırlandırılmamış kısmından halihazırda aldığı paranın alt sınırıdır — bir gelir tahmini ya da kâr iddiası değildir. Çoğu hesap için gerçek harcama tutarı bundan daha yüksektir; $5.00 rakamı yalnızca gerekli asgari eşik değeridir.\n\nİkincil hasat: yetiştirilen emtia hacmi üzerinden 66.7%’a kadar ücret. $26.8M giriş ücretinin yanı sıra, Topluluk Piyasası’nda satılan her kart ve eşya için zorunlu olarak Valve tutarında iki sentlik asgari ücret ödenir ($0.01 Steam ücret + $0.01 yayıncı ücreti). Tipik 3 sentlik kartlar ve değersiz eşyalarda, Valve, 3 sentten 2 sent alır — bu, Valve lehine 66.67% tutarında bir kesintiye denk gelir, manşette yer alan 15% pazarlama oranını çok aşan.\n\nNüfusla ilgili önemli bir uyarı: Grup üyeliği, her bir hesabın özel bir bot olduğunun kanıtı değildir; ayrıca Steam’daki tüm botları da kapsamaz. ASF, varsayılan olarak hesapları başlatıldığında otomatik olarak kendi topluluk grubuna kaydeder; kullanıcı bu yapılandırma bayrağının işaretini açıkça kaldırmadıkça veya devre dışı bırakmadıkça (AutoJoinSteamGroup), düzenli oyuncular, ara sıra oyuna girenler ve topluluk üyeleri, otomatik çiftçilik filolarıyla birlikte oyuncu listesinde yer almaktadır. Ayrıca, Steam yasaklamasında kamuya açık bir gerekçe alanı bulunmamaktadır. Bu bulgu, herhangi bir tek bir hesapla ilgili bireysel bir karar değil, bu yazılımla ilişkili kullanıcı kitlesi genelinde elde edilen ampirik bir orandır. Toplu, tekrarlanabilir: asf-ban-census-2026-09-23.json.\n\n02 — Coğrafya\nFilonun bulunduğu yer\n\nYasaklanan hesapların sadece 8.5%’u bir ülke belirtmiştir. Ülke belirten hesaplar arasında en büyük payı Amerika Birleşik Devletleri almaktadır.\n\nBir Steam profili, isteğe bağlı bir ülke alanı içerir. 100,413 yasaklanan hesaplardan 1,182,811'i bunu dolduruyor — 8.5%.† Bu azınlık içinde Amerika Birleşik Devletleri 15.5% ile başı çekiyor; onu Ukrayna, Çin ve Rusya izliyor; geri kalanlar ise Avrupa, Latin Amerika ve Güneydoğu Asya’ya yayılan uzun bir kuyruk oluşturuyor. Bu alanda kimse doğrulama yapmıyor: Afganistan ilk on içinde yer alıyor, ki bu da kabaca onun değerine denk geliyor. Diğer 91.5% ise atanmak yerine ihmal edilmiştir; dolayısıyla aşağıda görülen, kendi kendini seçmiş bir azınlığın şeklidir — ne filonun bir haritası, ne de filonun nereden yönetildiğini söylemek için bir dayanak.\n\nBildirilen ülkelere göre yasaklanan hesaplar\n\nKamuya açık bir konumu ifşa eden 100,413 yasaklanmış hesap arasında yer alan ilk 15 ülke. Pay, bu konum bilgisi içeren alt kümenin payıdır. Sayıları görmek için fareyi üzerine getirin.\n\n0%\n5%\n10%\n15%\n20%\nUnited States\nUkraine\nChina\nRussia\nCanada\nAustralia\nJapan\nBrazil\nGermany\nAfghanistan\nUnited Kingdom\nRomania\nFrance\nPhilippines\nIndia\n\nKonum şu kaynaktan okundu: GetPlayerSummaries yasaklanmış alt küme için. Bu alan hesap sahibi tarafından belirlenir ve kimse tarafından doğrulanmaz; dolayısıyla bir VPN çıkış noktası ya da şaka amaçlı bir giriş, gerçek bir girişle aynı şekilde değerlendirilir.\n\n03 — Tazelik\nSon dönemdeki hesaplar, eski birikmiş iş yükü değil\n\nHesap açılış tarihine göre bakıldığında, yasaklanan kullanıcı grubu yakın zamanda ortaya çıkmış olup, koleksiyon kartları döneminden kalma bir grup değildir.\n\nEğer bu, yavaş yavaş temizlenmekte olan eski bir karmaşa olsaydı, yasaklanan hesaplar ticaret kartlarının ilk yıllarına yoğunlaşırdı. Oysa tam tersi bir durum söz konusu. Oluşturulma tarihi görünen 1,132,852 yasaklanmış hesabın, 70%, 2020 yılında veya daha sonra oluşturulmuş olup, bunların neredeyse yarısı 2023 yılından bu yana oluşturulmuştur. Sayı, 2017’de oluşturulan 59,175’dan başlayarak zirveye ulaşarak 227,030 sadece 2024 yılında oluşturuldu. Her biri, $5.00 mağazasının giriş kapısından, kartı alana fırsat bulamadan geçtiler; bu nedenle her birinden giriş ücreti tahsil edildi.\n\nYasaklanan hesaplar ne zaman oluşturuldu?\n\nHesap açılış tarihini gösteren 1,132,852 yasaklanmış üyenin hesap açılış yılları. Bu dönem 2020–2026 arasını kapsamaktadır; 2013–2015 koleksiyon kartı dönemi değildir. Zirve: 2024. Sayıları görmek için fareyi üzerine getirin.\n\n0k\n63k\n125k\n188k\n250k\n'13\n'14\n'15\n'16\n'17\n'18\n'19\n'20\n'21\n'22\n'23\n'24\n'25\n'26\n70%2020 yılında veya daha sonra oluşturulan yasaklanmış hesaplar arasında\n227,0302024 yılında oluşturulan yasaklanmış hesaplar — en yoğun yıl\n51,701İki zirve yılın arasındaki 2021’deki düşüş — nedeni bilinmiyor\n2003→2026Veri aralığı mevcut, ancak veriler son altı yıla ait\n\nYapım tarihi GetPlayerSummaries SteamID64'e göre tekilleştirilmiş, yasaklanmış alt küme için. Oluşturulma tarihi, hesabın açıldığı tarihtir; hesabın yasaklandığı veya hesap çiftçiliğine başladığı tarih değildir; bu tarih, niyetin değil, verilerin ne kadar güncel olduğunun bir kanıtı olarak burada dikkate alınmaktadır. Grafikte gösterilmeyen üç husus:\n\n2024'ten sonra ortaya çıkacak bir trend. 2025 veya 2026’da açılan bir hesabın yasaklanmasına kadar geçen süre daha kısadır ve 2026 yılı dokuz ayı kapsamaktadır — dolayısıyla 227,030 → 121,070 → 16,534 bir düşüş değil, sansür anlamına gelir.\nYasaklama oranı. Hesapların oluşturulma yılları yalnızca yasaklanmış hesaplar için okunduğu için payda yoktur. Yalnızca artan kullanıcı tabanı bile bu eğriyi ortaya çıkarır.\n2021 yılı neden çöktü? 51,701, 105,821 ile 104,641 arasında, her iki komşusunun da yarısının altında yer alır. Bunu açıklayan kamuya açık bir bilgi yoktur; düzeltilmek yerine olduğu gibi bırakılmıştır.\n04 — Zamanlama\nValve devreye girdiğinde, ilk yıl içinde devreye girer\n\n88.97%’nin dokunulmamış olmasının en bariz gerekçesi, birikmiş iş yüküdür. Ancak tarihli yasaklar bunun aksini göstermektedir.\n\nYasak uygulandığında hesabın kaç yaşında olduğu\n\nHem oluşturulma tarihi hem de son yasaklanma tarihi bulunan 293,750 adet yasaklanmış hesap için, yasaklanma anındaki hesap yaşı. Bunların yarısından fazlası ilk yıl içinde tespit edildi.\n\n0%\n10%\n20%\n30%\n40%\n<6 mo\n33.7%\n6–12 mo\n21.5%\n1–2 y\n20.6%\n2–5 y\n14.3%\n5 y+\n10.0%\n55.1% inside the first year\nİlk yıl içinde yasaklandı — 55.1%Daha sonra yasaklandı — 44.9%\n0,80 yYasak uygulandığında hesabın medyan yaşı\n55.1%Hesabın açılmasından sonraki ilk yıl içinde yasaklandı\n33.7%İlk altı ay içinde yasaklandı\n293,750Her iki tarihin de bulunduğu hesaplar\n\nİşte bu, bariz savunmaya verilen cevaptır. Eğer filonun 88.97%’si, yaptırımların basitçe yavaş olması nedeniyle — birikmiş işlerin yavaş yavaş halledilmesi nedeniyle — etkilenmemişse, o zaman yasaklar ki yap bu durum yaş ortalamasını yukarı çekecekti. Oysa tam tersi oluyor: yasaklanan hesapların medyan yaşı dokuz buçuk aylık, ve üçüncüsü — 33.7% — altı ay içinde yakalandı. Valve bu popülasyona etki ettiğinde, hızlı hareket eder. Hâlâ kaçmakta olan on kişiden dokuzu sıraya girip beklemiyor.\n\nYasaklanma yaşı = oluşturulma tarihi GetPlayerSummaries şu ifadeden çıkarılan yasak tarihinden Son Yasaklanmadan Bu Yana Geçen Gün Sayısı, okumaya devam edin 2026-09-23. Bu değer, yalnızca her iki değerin de mevcut olduğu durumlarda hesaplanır: yasaklanan 1,200,011 hesabın 293,750’i. Kalan hesaplar “günden bu yana” değeri bildirmemektedir ve varsayılmamakta, hariç tutulmaktadır — dolayısıyla bunu her yasaklamanın değil, tarihlendirilmiş alt kümenin yapısı olarak değerlendirin.\n\n05 — Yasağın gerçekte ne olduğu\nValve devreye girdiğinde, botu durdurmaz\n\nHerhangi bir yasak içeren 11%'lar arasında, hangi yasağın uygulandığını kontrol edin.\n\nBir yasak, yasak değildir. 1,200,011 hesabın Valve’i işaretlemiştir, 99.8% bir topluluk yasak — forumlar, profiller ve gruplara getirilen, ticaret botuna hiçbir etkisi olmayan bir kısıtlama. Hesap hâlâ kart alabilir, hâlâ takas yapabilir, hâlâ envanterini taşıyabilir. 22.2% en az bir oyun yasağı ve 3.9% bir VAC yasağı; kategoriler birbiriyle örtüşüyor, bu yüzden toplamları birleştirilmez. Ticaret faaliyetlerini fiilen kesintiye uğratan tek yaptırım olan ekonomi / ticaret yasağı, 5,214 hesapta uygulanmaktadır. Bu sayıya dayanarak bir sonuca varmıyoruz — ticaret yasakları genel olarak Steam'te nadirdir. Bu grafiğin ana fikri daha basittir: Valve'lük kesir bile yapıyor mu Touch, işlem yapmaya devam ediyor.\n\nYasaklanan 11%'lar aslında ne yüzünden yasaklanıyor?\n\nHer bir yasak türü, taranan tüm 10,880,610 üyenin içindeki payı olarak gösterilmiştir. Hesaplarda birden fazla yasak türü bulunabilir. Sayıları görmek için fareyi üzerine getirin.\n\n0%\n4%\n8%\n11%\n15%\nCommunity ban\nGame ban\nVAC ban\nEconomy / trade ban\n\nBir Steam yasağında “neden” alanı bulunmadığından, bu yasakların hiçbiri özellikle kart biriktirmeyle ilişkilendirilemez — bu, mevcut yasak türlerinin bir karışımıdır ve her bir türün gerçekte neyi kısıtladığına göre sıralanmıştır. Topluluk yasağı takası engellemez; bunu ekonomi / ticaret yasağı yapar. Toplam: asf-ban-census-2026-09-23.json.\n\n06 — Diğer nüfus\nDolandırıcılar Valve hadi gidelim: 51,732 Tam Nüfus Sayımı\n\nAynı resmi API’ye göre değerlendirilen ikinci ve bağımsız bir liste: topluluk tarafından doğrulanmış dolandırıcılık vakaları.\n\nOtomasyon grubu, zararsız aylaklar olarak görmezden gelinebilir. İkinci grup ise öyle değildir. SteamRep, uzun süredir faaliyet gösteren bir topluluk itibar veritabanıdır; işaretlenmiş bir hesap YASAKLANDI Söz konusu topluluk tarafından, belgelenmiş mağdur kanıtları ve işlem sohbet kayıtları eşliğinde bir dolandırıcı olarak tespit edilmiştir. Tüm üyeler üzerinde bir 100% sayımı gerçekleştirdik 51,732 “YASAKLANMIŞ” durumuna sahip profil Steam'ın resmi Web API'sine karşı (ISteamUser/GetPlayerBans/v1) — ve yalnızca dolandırıcılıkla ilgili yaptırımlar dikkate alınmıştır. VAC numaralı yasak, bir oyunda yazılımla hile yapma durumlarına (nişan botları, duvar delme hile programları) yöneliktir; bu, bir tüccara herhangi bir etki etmez ve dolandırıcılık eylemine ilişkin Valve numaralı kanıt olarak değerlendirilmez; dolayısıyla dolandırıcılıkla mücadele kapsamında sayılmaz.\n\n51,732 hesap sayımının tamamında, 67.77% — 35,059 adet hakkında karar verilmiş dolandırıcı — Valve’ten dolandırıcılıkla ilgili SIFIR yasak almıştır: Hâlâ takas yapabiliyorlar, yeni kurbanlara arkadaşlık isteği gönderebiliyorlar ve mesajlaşabiliyorlar. Yalnızca 32.23% kişiye topluluk ya da takas yasağı uygulandı ve envanter transferlerini fiilen engelleyen tek önlem olan takas yasağı, sadece 18.81% (9,731 hesap) üzerinde geçerli. Ek olarak 12.81% (6,627 hesap) kullanıcı, yalnızca oyun içi hile nedeniyle VAC oyun yasağı almış olsa da, Steam ticaret konusunda hiçbir kısıtlamaya tabi değildir.\n\nValve’nin dolandırıcılıkla ilgili bir yasak uygulayıp uygulamadığına göre teyit edilmiş dolandırıcılar (Tam Sayım)\n\n51,732 SteamRep-ENGELLENEN tüm profiller, Valve’nin topluluk yasağı mı yoksa ticaret yasağı mı uyguladığına göre ayrılmıştır. VAC ve oyun yasakları hariç tutulmuştur — bunlar dolandırıcılıkla ilgili değildir. Sayıları görmek için fareyi üzerine getirin.\n\n0%\n18%\n35%\n53%\n70%\nNo scam-relevant ban\nCommunity or trade ban\n0%\n6%\n13%\n19%\n25%\nCommunity ban\nTrade / economy ban\nVAC (not fraud)\nGame ban\n51,732SteamRep-YASAKLANMIŞ profil denetlendi — 100% tam sayım\n35,059Dolandırıcılıkla ilgili herhangi bir yasak bulunmamaktadır (67.77%)\n18.81%Dolandırıcılıkları ortadan kaldıran ticaret yasağını yürürlüğe koyun (9,731)\n32.23%Valve numaralı paylaşım, bir topluluk veya ticaret yasağıyla (16,673) karşılaştı\n\nSteamRep, Valve kararından farklı olarak, üçüncü taraflarca oluşturulan ve topluluk tarafından değerlendirilen bir itibar veritabanıdır — asıl mesele de budur: Valve’ün kendi eylemleriyle karşılaştırılarak değerlendirilen harici kanıtlar. Kanonik dışa aktarımdan alınan tüm 51,732 YASAKLANMIŞ profiller, doğrudan ISteamUser/GetPlayerBans/v1. “Dolandırıcılıkla ilgili” ifadesi, topluluk veya ekonomi/ticaret yasağını ifade eder; VAC (12.81%) ve oyun yasakları (3.86%) ise dolandırıcılık değil hileyle ilgili oldukları için ayrı olarak sayılır. Tam denetim veri kümesi: steamrep_steam_bans.csv.\n\nİki popülasyon, tek bulgu\n\nBunlar aynı kişiler değil ve aynı davranışlar da değil. Birinde on milyon otomatik hesap söz konusu; diğerinde ise yargılanmış elli üç bin dolandırıcı. Aralarındaki ortak nokta, sonucun biçimidir: Çiftlik hesaplarının onda dokuzu hiçbir zaman kullanılmıyor ve tespit edilen dolandırıcıların üçte ikisinden fazlası (67.77%) dolandırıcılıkla ilgili herhangi bir yaptırımla karşılaşmıyor. Valve numaralı topluluk yasağı, forumları ve profilleri serbestçe kısıtlıyor; ticaretle ilgili bir kısıtlama getirmiyor. Bildirim düğmesi, itibar veritabanı, dolandırıcılığı engelleyen yasak: hepsi mevcut, hepsi yeterince kullanılmıyor. Bunu, ana dosyada arşivlenmiş red kararlarıyla karşılaştırın; aynı şirketin tek bir hesabı kalıcı olarak kaldırdığı ve bunun nedeni olarak ticari kullanım ile otomasyonu gösterdiği durumlar — bu madde atıl durumda değil, tam tersine çok net bir şekilde belirtilmiştir.\n\n07 — $5.00 Hesap Geçidi ve Hesap Ele Geçirme\n100,000-hesabı üzerine ampirik denetim: bot ağları, tek kullanımlık ücretsiz hesaplar değildir\n\nİstatistiksel örnekleme mantığı ve matematiksel ispat: Neden 100,000'dan başka herhangi bir değer alınsa da sonuç tamamen aynı olur?\n\nValve'un düzenleyici kurumlara ve tüketici koruma kuruluşlarına sunduğu başlıca savunma, otomatik dolandırıcılık ve hesap toplama faaliyetlerinin, kısa sürede yasaklanan geçici ve ücretsiz \"tek kullanımlık\" hesaplar aracılığıyla gerçekleştirildiği yönündedir. Valve'in yayınladığı kurallara göre, bir hesap Sınırlı en az $5.00 ABD Doları Steam mağazasında yer aldığı için, bu durum onu ticaret, arkadaşlık istekleri ve API özelliklerinden mahrum bırakmaktadır. Bu iddiayı, matematiksel açıdan titiz bir örneklemden oluşan bir grubun gelir elde etme durumunu test ederek doğrudan denetledik. 100,000 yasaklanmış Steam hesap 1,182,811 profil meta veri külliyatımızdan alınmıştır.\n\nÖRNEKLEME PROTOKOLÜ (SRSWOR)\n100,000 Tarafsız Dilim\n\nKaynak: N = 1,182,811 kriptografik olarak tekdüze bir PRNG kullanılarak, Yerine Koyma Olmadan Basit Rastgele Örnekleme yöntemi ile seçilen Steam adet benzersiz yasaklanmış hesap. Her hesabın dahil edilme olasılığı aynıydı: P = n / N ≈ 8.45%, hayatta kalma ve faaliyet yanlılığını tamamen ortadan kaldırır.\n\nMATEMATİKSEL KANIT\nHata Aralığı < ±0.4%\n\nSonlu Popülasyon Düzeltmesi (FPC) formülünü bir 99% Güven Aralığı (Z = 2,576):\nMoE = Z × √[p(1-p)/n] × √[(N-n)/(N-1)] ≈ ±0.39%\n\nTEKRARLANABİLİRLİK\nNeden Herhangi Bir 100k Aynı Getiri Sağlar?\n\nÇünkü hata aralığı, 99% güven düzeyinde ±0.4% sınırları içinde yer aldığından, Başka herhangi bir bağımsız 100,000-hesap örnekleminin, 63.06% ± 0.39% aralığına gireceği matematiksel olarak garanti edilmektedir. (62.67%'dan 63.45%'e). Örneklem, yasaklanan toplam 1,18 milyon kişilik nüfusu yansıtmaktadır.\n\nDenetim sonuçları, “tek kullanımlık bot” savunmasını tamamen çürütmektedir. Steam’in eski XML profil arayüzü aracılığıyla denetlenen 100,000 hesabın: 61,490 hesap (sınıflandırılmış hesapların 63.06%'si), Steam'te en az $5.00 harcama yapmış olan Sınırsız (Ücretli) hesaplardır. Sadece 36,021 (36.94%) bunlar sınırlı ücretsiz hesaplardır; 2,489 ise yapılandırılmamış ya da özel hesaplardı.\n\n100,000 Engellenen Hesaplar: Ücretli ($5+ Mağaza Harcamaları) ve Ücretsiz Sınırlı Durum\n\nRastgele seçilen 100,000 adet yasaklanmış hesabın ampirik denetimi. Bunların 63%’den fazlası, Valve’nin ücretli ödeme sisteminden geçmiştir. Sayıları görmek için fareyi üzerine getirin.\n\n0%\n16%\n33%\n49%\n65%\nNon-limited (Paid ≥ $5.00)\nLimited (Free < $5.00)\n100,000Örneklem (SRSWOR, N=1,18 milyon)\n63.06%Sınırsız ücretli hesaplar (61,490 hesapları)\n±0.39%99% güven aralığındaki hata payı\n~745,8001,18 milyon yasaklanmış metin kümesindeki tahmin edilen ücretli hesaplar\nYapısal Gerçeklik: Endüstriyel Ölçekte Hesap Tasfiyesi\n\nÖrneklemdeki yasaklanmış hesapların neden 63%’si, Valve’in mağazasında gerçek para harcayan ücretli hesaplar olsun ki? Botnet operatörleri, tek kullanımlık hesaplar için kendi ceplerinden milyonlar harcamazlar. Bu oran, güvenliği ihlal edilmiş ve ele geçirilmiş hesaplar ekosistem içinde dolaşan.\n\nBu ölçek, yeraltı platformlarında doğrudan gözlemlenebilir: FSB Market (anonimleştirilmiş ad; gerçek ad burada belirtilmiyor) gibi pazar yerlerinde, 550,000 Steam hesap (hırsızlık kayıtları, kimlik avı yakalamaları, kimlik bilgisi doldurma) her an aktif olarak satışa sunulmaktadır (phishdestroy.io/live-intel). Pazar, alıcı ve satıcıların kimliğini Valve’un kendi Steam OpenID’sini kullanarak doğrular ve ne FSB Market ya da ilişkili forum Valve'un Bağlantı Filtresi tarafından engellenmiştir.\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\n06. Bölümde belirtildiği üzere, Valve bu dolandırıcılık faaliyetini proaktif olarak ortadan kaldırmamaktadır: 67.77% topluluk tarafından doğrulanmış dolandırıcıların Steam'de dolandırıcılık yasağı bulunmamaktadır, ve otomasyon filosunun 88.97% kısmı tamamen el değmemiş durumda kalır. Hesaplar serbestçe dolaşır, resmi API’ler aracılığıyla kimlik doğrulaması yapar ve ekosistem genelinde neredeyse tamamen cezasız bir şekilde işlem gerçekleştirir.\n\nAdli Kanıt ve Yürütme Mimarisi Şeması\n10,88 milyon taranan hesaptan 100 bin ampirik kesite ve 53,5 bin doğrulanmış dolandırıcıya uzanan etkileşimli akış · Ham kanıtları incelemek için bağlantılara tıklayın\nSeviye 01 · 10,88 milyonluk Otomasyon Filosu Sayımı\nSteam'deki kendini otomasyon olarak tanımlayan en büyük kullanıcı grubu, Valve'in resmi yasaklama API'sinden sırayla geçti. Bu durum, ticari bot filolarının 88.97%'da on milyonlarca giriş ücreti öderken cezasız bir şekilde faaliyet gösterdiğini kanıtlamaktadır.\n9,680,599 88.97% Aktif ve El Değmemiş\nKayıtlarında hiçbir türden yasak bulunmayan ve otomatik yazılım çalıştıran hesaplar.\nİşlenmemiş Nüfus Sayımı JSON Verisi (1,2 KB) ↗01. Bölümü inceleyin ↗\n$26,802,495 Doğrudan Mağaza Gelir Tabanı\nAsgari $5.00 giriş eşiğini aşan 5,360,499 sınırsız üyeden Valve tarafından toplanmıştır.\nKart Ekonomisi Denetimi ↗Valve $5 Kural SSS ↗\n1,200,011 11.03% İşaretli Alt Küme\n99.8%'da yalnızca kozmetik topluluk yasakları uygulanmaktadır; 99.95% numaralı hesaplarda ticaret devam etmektedir.\nYasak Türlerine Göre Dağılım ↗Engellenmiş Veritabanı (60,4 MB) ↓\nSeviye 02 · 100,000-Hesap Empirik Örnekleme Denetimi (N = 1,182,811)\nEski XML uç noktaları aracılığıyla değerlendirilen SRSWOR dilimlik bir örneklem. Matematiksel olarak kanıtlanmış hata payı, 99% güven aralığında < ±0.4%'dır. Yasaklanan botların ücretsiz tek kullanımlık hesaplar olduğu iddiasını çürütmektedir.\n61,490 (63.06%) Sınırsız Ödemeli Hesaplar ($5+ Harcama)\nEngellenen hesapların 63%’sinden fazlası ücretli işlemleri temsil ediyor. Bu rakam, engellenen hesap havuzunda ~745,800 ücretli hesap ($3.73M+ giriş eşiği) olduğu sonucuna götürüyor.\nSınırlı Sonuçlar CSV (2,1 MB) ↓100k Adli Rapor ↗\n36,021 (36.94%) Sınırlı Ücretsiz Hesaplar (< $5.00)\nYasaklanan profillerin azınlığı, Valve'in \"tek kullanımlık bot\" tanımına uyuyordu. 2,489 hesapları ise yapılandırılmamış ya da gizliydi.\n100.000 Örnek Dilim CSV (8,5 MB) ↓Harcama Analizi MD ↗\n34.67% - 63.93% Profil Temizleme Denetimi\nValve hesapta takma adlar silinerek SteamID64'e geri döndürüldü, ancak 34,673 hesapta özel adlar ve avatarlar tamamen olduğu gibi bırakıldı.\nDezenfeksiyon Bölümü ↗Genel Bakış Yol Haritası ↗\n34.59% Eski Sürüm Eski Hesaplar (2003–2019 arasında oluşturulmuş)\nEngellenen hesapların üçte birinden fazlası 5 ila 20+ yıl önce kaydedilmişti; bu da uzun süredir oyun oynayan Steam oyuncularının hesaplarının endüstriyel ölçekte ele geçirildiğini ortaya koyuyor.\nYaş Kronolojisi ↗Destek Taleplerinin Reddedilmesi ↗\nSeviye 03 · 51,732 SteamRep Doğrulanmış Dolandırıcılar Sayımı\nMağdurların sohbet kayıtları ve işlem kanıtlarıyla birlikte, topluluk tarafından tespit edilen dolandırıcıların eksiksiz 100% listesi; bu liste, resmi Steam yasaklama API’leriyle çapraz kontrol edilmiştir. Bu durum, sistematik bir yaptırım başarısızlığını kanıtlamaktadır.\n35,059 (67.77%) Dolandırıcılık Nedeniyle Yasaklama Yok (Tam Ceza Muafiyeti)\nDoğrulanmış dolandırıcıların üçte ikisinden fazlası, Valve'dan ne Topluluk ne de Ticaret yasağı almıştır. Ticaret yapmak ve yeni kurbanlar eklemek için tam olarak faaldir.\nSteamRep API Yasakları (2,6 MB) ↓SteamRep Denetim Raporu ↗\n9,731 (18.81%) Ekonomi / Ticaret Yasağı\nStok tasfiyesini durduran tek yaptırım. Doğrulanmış dolandırıcıların beşte birinden azında görülmektedir.\nSteamRep Kaynak (2,1 MB) ↓06. Bölümü inceleyin ↗\n6,627 (12.81%) Konuyla İlgisiz Hile Yasağı (Yalnızca VAC)\nOyunlarda aimbot ve wallhack kullanımı nedeniyle yasaklanmış olsalar da, Steam ticaret ve kimlik avı yetenekleri 100% aktif durumda kalmaya devam ediyor.\nVAC Alakasızlık Analizi ↗Güvenlik Zaman Çizelgesi ↗\nSeviye 04 · Wiki Sitenin Tahrif Edilmesi ve Ağustos 2026’daki Altyapı Güvenlik İhlalleri\nKanıt paketinde belgelenen, geliştiricilere yönelik iç dokümantasyonun tahrif edilmesi, topluluk editörlerinin engellenmesi ve güvenlik sınırlarının ihlali.\n1,200+ Editörler VDC Wiki Çakışma Günlükleri\nOltalama bağlantılarını ve spam şablonlarını düzeltmeye çalışan topluluk editörleri, otomatik filtreler tarafından sistematik olarak engellenirken, Valve personel ise uyarıları görmezden geldi.\nRusya’daki Çatışmalar Raporu (127 KB) ↗Sınıflandırma Raporu (66 KB) ↗\n12 TB Kimlik Doğrulaması Yapılmamış Ağustos 2026 Varlık Sızıntısı (CWE-284)\nValve, haftalarca boyunca kimlik doğrulaması gerektirmeyen açık bir genel uç noktada 12 terabaytlık dahili kod ve prototip sürümlerini barındırdı.\nValve Yetersizlik Dosyası (43 KB) ↗Kanıt Arşivi ↗\nCEVA Logistics Güvenlik İhlali Ağustos 2026 Müşteri Kişisel Bilgileri Sızıntısı\nValve'un lojistik ortağından sızan, Avrupa'daki Steam Deck alıcılarının isimleri, adresleri ve telefon numaraları, bir dizi kimlik hırsızlığı saldırısına yol açtı.\nOlay Kaydı ↗Yaptırım Kaydı ↗\n\nÖrnekleme hatası: banned_100k_slice.csv (100,000 hesap). Denetim sonuçları: slice_100k_limited_results.csv. Tam analiz raporu: BANNED_100K_FORENSIC_ANALYSIS.md.\n\n08 — Yöntem ve sınırlar\nBu metin nasıl yorumlandı ve neyi iddia etmiyor?\n\nÜç genel popülasyon, tek bir genel API, titiz istatistiksel örnekleme.\n\nUYGULAMA VE YETKİ BELGELERİ\n\nASF sayımı, 100,000-hesap SRSWOR dilimi ve SteamRep çapraz kontrolü, Koalisyonun halka açık oltalama ve dolandırıcılık engelleme çalışmalarının bir parçası olarak, PhishDestroy katılımcı tarafından kendi Steam hesapları ve Web API anahtarları kullanılarak gerçekleştirilmiştir. Dosyanın yazarı herhangi bir Steam Web API anahtarına sahip değildir ve şahsen hiçbir canlı tarama gerçekleştirmedi. Verilerin toplanması, karma hesaplanması, doğrulanması ve yayınlanması, katılımcıların çıktılarına dayanılarak gerçekleştirildi.\n\nNüfus\tNereden geldi?\tNe okundu?\nASF üyeleri\n10,880,610\tArchiSteamFarm Steam Topluluk grubunun herkese açık üye listesi. Steam'ün grup sayfasında 5,360,499 üye gösteriliyor (sadece sınırlandırılmamış üyeler); API üye listesi ise sınırlandırılmış hesaplar dahil olmak üzere toplam 10,880,610 giriş döndürdü. Kullanıcı, yapılandırmada varsayılan gruba katılma ayarını açıkça devre dışı bırakmadıkça, grup ilk çalıştırmada otomatik olarak eklenir (AutoJoinSteamGroup / İstatistikler), yani üye listesinde ticari bot kümeleri, bireysel kart kullanıcıları ve varsayılan seçeneği etkin bırakmış olan sıradan oyuncular yer almaktadır.\tGetPlayerBans her üye için (yasaklama işaretleri); GetPlayerSummaries oluşturulma tarihleri ve ülke bilgisi için. 100 ID’lik gruplar halinde toplanmış, SteamID64’e göre tekilleştirilmiştir.\n100 bin Engellenen Hesap SRSWOR Dilim\n100,000\t1,182,811 yasaklanmış hesaplar kümesinden ($P = 8,45\\%$), geri koyma olmaksızın tekdüze rastgele seçilmiş temsili bir örneklem. Sonlu Popülasyon Düzeltmesi, 99% güven düzeyinde ($Z = 2,576$) $\\pm 0,39\\%$ hata payı vermektedir.\tGelir elde etme ve sınırlı hesap durumu (isLimitedAccount) Steam'nin eski XML profil arayüzü aracılığıyla denetlenir (?xml=1) dağıtılmış proxy boru hatları üzerinden. 63.06% ücretli durumunu teyit eder.\nSteamRep dolandırıcılar\n51,732\tSteamRep topluluk itibar veritabanında “BAĞLANMIŞ” olarak işaretlenmiş tüm profillerin 100% numaralı tam sayımı gerçekleştirildi (toplam 51,732 profil). Herhangi bir örnekleme veya filtreleme uygulanmadı.\tISteamUser/GetPlayerBans/v1 Tüm 51,732 hesapları için, SteamRep durumuyla çapraz tablo halinde karşılaştırılmıştır. 67.77%’in herhangi bir dolandırıcılık yasağı olmaksızın serbest olduğunu teyit eder.\nTalep edilen hususlar\n\nYalnızca ampirik oranlar ve istatistiksel olarak sınırlandırılmış tahminler. Otomasyon popülasyonunda, 88.97% için herhangi bir yasak bulunmamaktadır; yasaklanmış alt küme ise son döneme kaymaktadır (70%, 2020’den beri). 100,000 hesaplı ampirik denetimde, yasaklanmış hesapların 63.06%'ü ücretli (sınırsız) olup, matematiksel olarak kanıtlanmış hata payı ±0.4%'nin altındadır. Onaylanmış 51,732 dolandırıcı arasında, 67.77%'sında dolandırıcılıkla ilgili herhangi bir yasak bulunmamaktadır. Her rakam, Valve'nin kendi Web API'sinden yeniden üretilebilir.\n\nNeler talep edilmemektedir\n\nBir Steam yasağında “neden” alanı bulunmadığından, buradaki hiçbir yasak belirli bir nedene atfedilmez. Grup üyeliği, bir hesabın otomatik bir bot olduğunun kanıtı değildir: ASF, manuel olarak işaretin kaldırılmadığı sürece varsayılan olarak gruba katılmaya izin verdiği için, kullanıcı kitlesi ticari çoklu hesap çiftliklerini sıradan oyuncuların ve hobi amaçlı kullanıcıların kişisel hesaplarıyla bir araya getirir. Ülke bilgisi kullanıcılar tarafından bildirilir ve SteamRep ibaresi, mahkeme kararı değil, topluluk tarafından verilen bir hükümdür. Hiçbir kişinin adı belirtilmez.\n\nNeden önemli?\n\nValve aynı API’yi, arka planda kendi veritabanını ve bu taramanın göremeyeceği yasaklama nedenlerini barındırır. Bu sorguyu tüm kimlik alanı üzerinde saniyeler içinde çalıştırabilir. Bir sayıya yönelik bir yaptırım iddiasını dış bir tarafın doğrulamasını sağlayan ölçüm, bunu tam doğrulukla üretebilecek tek taraf tarafından hiçbir zaman yayınlanmamıştır. Bu, sorunun bir rakamla birlikte ortaya konulabilmesi için sunulan dış kaynaklı bir tahmindir.\n\nSonraki makale: bu nüfusun yürüttüğü kart ekonomisi → · erişim ve hırsızlığa karşı koruma → · dosyanın tamamı →",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam’deki hesap ağı ne kadar büyük? Kendimiz saydık."
          },
          {
            "level": 2,
            "id": null,
            "text": "On milyon hesap; bunlardan dokuzu hiç kullanılmamış"
          },
          {
            "level": 3,
            "id": null,
            "text": "ASF, sizin için gruba katılıyor"
          },
          {
            "level": 3,
            "id": null,
            "text": "10,880,610 toplam giriş"
          },
          {
            "level": 3,
            "id": null,
            "text": "88.97% temiz"
          },
          {
            "level": 3,
            "id": null,
            "text": "10,880,610 hesaplardan kaç tanesi Valve değerine ulaşmıştır?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Bu filonun varlığı için halihazırda ödenen tutar Valve"
          },
          {
            "level": 2,
            "id": null,
            "text": "Filonun bulunduğu yer"
          },
          {
            "level": 3,
            "id": null,
            "text": "Bildirilen ülkelere göre yasaklanan hesaplar"
          },
          {
            "level": 2,
            "id": null,
            "text": "Son dönemdeki hesaplar, eski birikmiş iş yükü değil"
          },
          {
            "level": 3,
            "id": null,
            "text": "Yasaklanan hesaplar ne zaman oluşturuldu?"
          },
          {
            "level": 2,
            "id": null,
            "text": "Valve devreye girdiğinde, ilk yıl içinde devreye girer"
          },
          {
            "level": 3,
            "id": null,
            "text": "Yasak uygulandığında hesabın kaç yaşında olduğu"
          },
          {
            "level": 2,
            "id": null,
            "text": "Valve devreye girdiğinde, botu durdurmaz"
          },
          {
            "level": 3,
            "id": null,
            "text": "Yasaklanan 11%'lar aslında ne yüzünden yasaklanıyor?"
          },
          {
            "level": 2,
            "id": null,
            "text": "Dolandırıcılar Valve hadi gidelim: 51,732 Tam Nüfus Sayımı"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve’nin dolandırıcılıkla ilgili bir yasak uygulayıp uygulamadığına göre teyit edilmiş dolandırıcılar (Tam Sayım)"
          },
          {
            "level": 4,
            "id": null,
            "text": "İki popülasyon, tek bulgu"
          },
          {
            "level": 2,
            "id": null,
            "text": "100,000-hesabı üzerine ampirik denetim: bot ağları, tek kullanımlık ücretsiz hesaplar değildir"
          },
          {
            "level": 3,
            "id": null,
            "text": "100,000 Tarafsız Dilim"
          },
          {
            "level": 3,
            "id": null,
            "text": "Hata Aralığı < ±0.4%"
          },
          {
            "level": 3,
            "id": null,
            "text": "Neden Herhangi Bir 100k Aynı Getiri Sağlar?"
          },
          {
            "level": 3,
            "id": null,
            "text": "100,000 Engellenen Hesaplar: Ücretli ($5+ Mağaza Harcamaları) ve Ücretsiz Sınırlı Durum"
          },
          {
            "level": 3,
            "id": null,
            "text": "Yapısal Gerçeklik: Endüstriyel Ölçekte Hesap Tasfiyesi"
          },
          {
            "level": 2,
            "id": null,
            "text": "Bu metin nasıl yorumlandı ve neyi iddia etmiyor?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Talep edilen hususlar"
          },
          {
            "level": 3,
            "id": null,
            "text": "Neler talep edilmemektedir"
          },
          {
            "level": 3,
            "id": null,
            "text": "Neden önemli?"
          }
        ],
        "links": [
          "https://help.steampowered.com/en/faqs/view/71D3-35C2-AD96-AA3A",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/asf-ban-census-2026-09-23.json",
          "https://phishdestroy.io/steam_dossier/tr/VALVE_EVIDENCE_PACK/databases/steamrep_steam_bans.csv",
          "https://phishdestroy.io/live-intel/?category=steam",
          "https://phishdestroy.io/steam_dossier/tr/#proxy-bypass-explainer",
          "https://phishdestroy.io/steam_dossier/tr/card_economy.html",
          "https://phishdestroy.io/steam_dossier/tr/VALVE_EVIDENCE_PACK/databases/banned_archiasf_massive.csv",
          "https://phishdestroy.io/steam_dossier/tr/VALVE_EVIDENCE_PACK/databases/slice_100k_limited_results.csv",
          "https://phishdestroy.io/steam_dossier/tr/VALVE_EVIDENCE_PACK/reports/BANNED_100K_FORENSIC_ANALYSIS.md",
          "https://phishdestroy.io/steam_dossier/tr/VALVE_EVIDENCE_PACK/databases/banned_100k_slice.csv",
          "https://phishdestroy.io/steam_dossier/tr/VALVE_EVIDENCE_PACK/reports/STEAM_BANNED_LIMIT_ANALYSIS.md",
          "https://phishdestroy.io/steam_dossier/tr/VALVE_EVIDENCE_PACK/INVESTIGATION_OVERVIEW.md",
          "https://phishdestroy.io/steam_dossier/tr/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/tr/VALVE_EVIDENCE_PACK/reports/STEAMREP_VS_STEAM_AUDIT.md",
          "https://phishdestroy.io/steam_dossier/tr/VALVE_EVIDENCE_PACK/databases/SteamRep_Profiles_BannedCaution_2024.csv",
          "https://phishdestroy.io/steam_dossier/tr/security_timeline.html",
          "https://phishdestroy.io/steam_dossier/tr/VALVE_EVIDENCE_PACK/reports/russian_conflicts_report.json",
          "https://phishdestroy.io/steam_dossier/tr/VALVE_EVIDENCE_PACK/reports/classification_report.json",
          "https://phishdestroy.io/steam_dossier/tr/VALVE_EVIDENCE_PACK/reports/VALVE_INCOMPETENCE_REPORT.md",
          "https://phishdestroy.io/steam_dossier/tr/steam_evidence_archive.html",
          "https://phishdestroy.io/steam_dossier/tr/steam_enforcement_evidence.html",
          "https://phishdestroy.io/steam_dossier/tr/#insider-threat",
          "https://phishdestroy.io/steam_dossier/tr/"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/tr/enforcement_audit.content.json",
      "export_json_sha256": "e8b8ee2852793ce73bd9a11f38e079bd24971f224b689e12b6363b7fcb435114"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "tr/index.html",
      "language": "tr",
      "title": "Steam Dosyası: kurallar, güzergâhlar ve hesap verebilirlik",
      "source_url": "https://phishdestroy.io/steam_dossier/tr/index",
      "source_html_sha256": "d1dfdd5cee0347c3dcca83fe0313f69f1f98ad7e9d22325f4e66b9e1af44bbdd",
      "exported_at": "2026-09-29T00:20:53.854Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "exhibit-gallery-section",
            "source": "https://phishdestroy.io/steam_dossier/tr/index#exhibit-gallery-section"
          }
        ],
        "raster_images_replaced": 2
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "index.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/tr/index.pdf?v=print-20260929-v5",
        "sha256": "ec9cf1e81ea191469ffc07c9103dba97f75cdd951949822fd517e5bd4e83338d",
        "bytes": 966705,
        "pages": 105
      },
      "integrity": {
        "signed_object": "index.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "index.content.json.asc",
        "digest_file": "index.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify index.content.json.asc index.content.json",
          "sha256sum -c index.content.json.sha256"
        ]
      },
      "content": {
        "text": "Bölüm 1 — Dava özeti\nKural. Rekor. Cevaplanmamış sorular.\nBağlam ve kaynak sınırlamaları\n\nHer biri tarihli bir kamu kayıtıyla bağlantılı altı bulgu. Ayrıntılı bölümler aynı sırayı izlemektedir: teknik kayıt (Bölüm A), kurallar ve uygulama kaydı (Bölüm B), yasal çerçeveler (Bölüm C) ve ardından birincil delillerin yer aldığı ekler.\n\nAltı bulgu. Her biri, yazılı bir kuralı tarihli bir kayda ve kanıtların doğruluğunu test edebileceği bir soruya bağlamaktadır.\n\n1. Ayrı etki alanına sahip kimlik doğrulama sunucuları — 44 yol · 26 bölünmüş çift\n\nCanlı kayıt defterindeki kayıtlar Ayrı bir kayıt edilebilir alan adı aracılığıyla kimlik doğrulaması yapılan 44 platform. Doğrulama aşamasında olan ve RDAP tarihi bekleyen beş güzergâh daha bulunmaktadır; bunların listeye eklenmesi halinde toplam sayı 47’ye ulaşacaktır. Bu güzergâhlar, 44 sayısına ve yaş tablosuna dahil edilmemiştir. — 27, her güzergâh için yayınlanmış bir kanıt dosyası ile ve manuel toplama yoluyla eklenen 17 tanesi, ayrı olarak listelenmiştir. İçinde 26 filtre-ayırma çifti ana etki alanı şudur: ENGELLENMİŞ Steam Bağlantı Filtresinde yer alırken, oturum açma bilgilerini taşıyan proxy ise yer almıyor. Bunlar geçici alan adları değil: csgogem.com engellenmişken api.csgem.com, Steam kullanıcı adını taşıyan sunucu, Mart 2014'ten beri kayıtlıdır — 12 yıl 6 ay. Valve, her OpenID isteğinde bu ana bilgisayar adını alır ve bunu kendi oturum açma sayfasında kullanıcıya gösterir. Tam tablo, rota bazında yaş bilgileri ve kaynak bilgileri 3. Bölüm’de yer almaktadır.\n\nGüzergâhı takip edin →\n2. 2016: Mekanizmaya bir isim verildi, son tarih belirlendi\n\n13 Temmuz 2016 tarihinde Valve, kumar sitelerinin Steam OpenID ve otomatik işlem hesaplarını nasıl kullandığını kamuoyuna açıkladı; avukatının 20 Temmuz 2016 tarihli bildirimlerinde ise on günlük bir süre tanındı. O tarihten bu yana operatör bazında herhangi bir yaptırım kaydı yayınlanmamıştır. Bu sürenin dolmasından on yıl sonra, aynı adlı mekanizma, 2026-09-21 tarihinde Link Filter engellemesi döndürmeyen ayrı etki alanlarına sahip kimlik doğrulama sunucularında kullanılmaya devam etmektedir.\n\nWSGC’ye yazılan açık mektubu okuyun →\n3. Cihaz eşleştirme, avukatın antetli kağıdında\n\nBurada aktarılan yazışmalarda, Valve’un avukatı, bir cihazı birden fazla hesapla ilişkilendiren cihaz düzeyinde bir korelasyonu açıklamıştır — bu, Steam Destek ekibinin daha önce kullanıcılara teknik olarak mümkün olmadığını söylediği bir özellikti. Cevaplanmamış soru, Valve'in hangi cihaz düzeyindeki kayıtları elinde bulundurduğu ve hesap sahiplerinin bu kayıtlara erişiminin hangi gerekçeyle engellendiğidir.\n\nMemorandumu okuyun →\n4. İki erişim yanıtı. Birinde veriler paylaşılmadı, diğerinde ise sızdırıldı.\n\nEkim 2025: Valve'nın avukatı, 15. maddeye dayalı bir talebe, metin içindeki sansürlenmiş kısımların silinmek yerine üzerlerinin boyanarak gizlendiği 830 sayfalık bir ekle yanıt verdi — 902,270 karakter standart bir veri çıkarma aracıyla, çubukların gizlemek amacıyla konulduğu üçüncü taraf tanımlayıcıları da içeren verilerle geri dönün. Bu çubukların var olmasının nedeni 15. maddenin (4) numaralı fıkrasıdır. Eylül 2026: HT-2YBP-F7JP-D4VB numaralı bilet, üç gün sonra self-servis Hesap Verileri sayfasına yönlendiren bir bağlantı eklenerek kapatıldı — veri yoktu, hukuki dayanak belirtilmemişti. Yayınlandığı tarihte 12. Maddenin 3. fıkrası uyarınca belirlenen bir aylık süre henüz dolmamıştı; itiraz, konunun özüne yöneliktir.\n\nDüzenleme kontrolünü okuyun →Bilet kaydını oku →\n5. Steam'nin tavan seviyesinin üzerindeki piyasa\n\nSteam, bir hisse senedinin piyasa değerini yaklaşık $1,800. Tarihli bir anlık görüntüde (23 Eylül 2026) beş pazar yerinde, 248 CS2 ürün kategorisi bu üst sınırın üzerinde fiyatlandırılmaları, iki veya daha fazlası tarafından bağımsız olarak belirlenmişse ve 248'inin tamamı Steam'da yok; Fabrika çıkışı yeni bir Dragon Lore’un fiyatı şu şekilde başlıyor: $10,941 Beş listede yer alan toplam 389 kopya üzerinden (13. Bölüm’de yer alan, 20 Eylül anlık görüntüsüne ait, yalnızca CSFloat’a ait rakam, 62 teklifte $10,623.95’dır). Bu fiyatlardan satış yapmak için harici bir platform gerekirken, ürün transferi hâlâ Steam üzerinden gerçekleşmektedir.\n\nFiyatı takip edin ve transferi gerçekleştirin →\n6. Kural açık ve nettir; denetim izi ise değildir\n\nAbonelik Sözleşmesi, Steam'yi kişisel ve ticari olmayan kullanım için ayırır, açıkça izin verilen durumlar dışında ticari kullanımı yasaklar, komut dosyalarını ve botları yasaklar ve hesabın feshine izin verir. Valve, 2016 yılında bu hükümleri kumar operatörlerine de uygulamıştır. Bununla ayrı olarak, CSFloat’un mühendislik hesabına göre, Valve kapatıldı IEconItems_730/GetPlayerItems 2017 yılında, orijinal öğe kimliklerine kamu erişimi kaldırıldı (Valve değişiklik günlüğü bulunamadı).\n\nKuralı ağın yanına yerleştirin →\n2016 / Yazılı talep 10 gün\nValve avukatının kumar sitelerine gönderdiği Temmuz 2016 tarihli bildirimlerdeki son tarih. WSGC’ye açık mektup: 2. Bölüm.\n2017 / Kamuya açık denetim izi Kimlik erişimi kapatıldı\nCSFloat, orijinal öğe kimlik numaralarının kaybolmasını kaydeder.\nAvukat yazışmaları Cihaz korelasyonu\nÇalınan düzinelerce hesapla bağlantılı tek bir cihaz.\nGüzergâh kaydı Engellendi, ancak yine de oturum açılıyor\nKural: Valve'nin 2016 tarihli açıklaması, Steam OpenID üzerinde kumar işletmesi yürütülmesini yasaklamaktadır. Kayıt: Link Filter'da 26 ana alan adı bulunurken, her birinin Steam giriş bilgilerini barındıran sunucu şu anda çalışmaktadır — csgogem.com'unki 12 yıl 6 aydır çalışmaktadır.\n2. Bölüm — Açık mektup\nWashington Eyaleti Kumar Komisyonu’na açık mektup\n\nOn gün, on yıla dönüştü. Komisyon’un 2016 yılında Valve’ye yönelttiği soruya, operatör bazında ayrıntılı bir kayıt sunulmamıştır; bu mektupta, dosyanın yeniden açılması talep edilmektedir.\n\nHALKLA İLİŞKİLER · WASHINGTON EYALETİ KUMAR KOMİSYONU\n\nOn gün, on yıla dönüştü.Kaydı yeniden açın.\n\nWashington Eyaleti Kumar Komisyonu’na:\n\n2016 yılında, Direktör David Trujillo, Valve’dan kumar amaçlı Steam skinlerinin kullanımını engellemek için ne gibi önlemler aldığını açıklamalarını istedi. O dönemin Başkanı Chris Stearns ve Komisyon, Valve tarafından verilen öğeler ve Steam transferleri üzerine kurulu bir sektörle karşı karşıya kaldı. Her iki isim de o zamandan beri Komisyon'daki görevlerinden ayrıldı. Valve'ye yönelttikleri soru hâlâ geçerliliğini koruyor.\n\nValve’un genel hukuk danışmanı Karl Quackenbush, kumar işletmecilerine Steam hesaplarının ticari kullanımını durdurmaları için on gün süre verdi. Valve, Komisyonunuza Ekim ayında verdiği yanıtta kumar faaliyetlerine aracılık etmediğini reddetti, kırktan fazla siteye faaliyet durdurma mektupları gönderdiğini ve ilgili hesapları devre dışı bıraktığını belirtti. Ayrıca, bu hizmetlerin müşterilere ve oyun geliştiricilerine fayda sağladığı gerekçesiyle Steam ticaret ve OpenID hizmetlerini sürdürmeyi savundu. Bu, bir kontrol iddiasıydı. Buna boyun eğmek değil, sınanması gerekir.\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\nDeğerlendirmemize göre, Valve’un cevabı, seçtiği yaptırımın tarif ettiği ağın ölçeğiyle orantılı olduğunu göstermedi. Bir operatöre gönderilen tehdit mektubu, işletmenin işleyişini sağlayan Steam hesapları, ticaret altyapısı ve kimlik doğrulama yolları üzerinde kalıcı bir engellemeyle aynı şey değildir. Bildirilen tahminlere göre CS:GO Lounge, 2016 yılında tek başına $1 milyar üzerindeki bahis hacmine ulaştı; bu, bahis tutarlarına ilişkin dışarıdan yapılan bir tahmindir, Valve gelirine ilişkin değildir ve sitenin orijinal deri bahis faaliyetleri daha sonra sonlandırılmıştır. Bu ölçek, doğrulanabilir bir denetim uygulamasını zorunlu hale getirmiştir.\n\nBugün, Valve'un kendi Abone Sözleşmesi arşivlendi 2026-09-21 ↗ açıkça izin verilen durumlar hariç olmak üzere ticari kullanımları kısıtlar ve belirli otomasyon biçimlerini ayrı olarak yasaklar. Bizim tarihli güzergâh kaydı OpenID olarak bildirilen kayıtlar, harici hizmetler için ana bilgisayarları döndürür; openid.realm ve openid.return_to bunlar, Steam’a gönderilen alanlardır, ondan gizlenen sırlar değildir. Bizim Bağlantı Filtresi kontrolleri Ana adres için uyarı verildiği halde, buna bağlı oturum açma sunucusu için uyarı verilmediği durumları gösterir. Tek başına bir filtre sonucu, Valve'un bir oturum açmaya izin verdiğini veya belirli bir botun hesap yasağını atlattığını kanıtlayamaz. Bu durum, ana sayfada yer alan bir uyarının erişim konusuna ilişkin tam bir çözüm olarak sunulamayacağını kanıtlamaktadır.\n\nYararlı ve yasal Steam ticaret ve OpenID işlevlerinin varlığı da, yasaklanmış operatörlerin gerçekten dışlanıp dışlanmadığını ortaya koyamaz. Valve’un kendi kuralları açık istisnalara izin vermektedir. Eğer Valve bu ayrıma dayanıyorsa, Komisyon, ticari skin işletmelerine uygulanacak yetkilendirme, hesap kontrolleri ve uygulama kriterlerini ve 2016 yılında öne sürdüğü kumar dışı kullanımlara ilişkin somut örnekleri belirlemesini istemelidir. Yasal kullanım olasılığının varlığı, belgelenmiş yasaklanmış kullanıma bir cevap teşkil etmez.\n\nKomisyon’dan 2016 yılı dosyasını yeniden incelemesini ve operatör bazında bir açıklama talep ediyoruz: on günlük bildirimlerin ardından hangi Steam hesapları ve ticaret botları devre dışı bırakıldı; ilgili hesaplar veya geri dönüş sunucuları izlendi mi; hangi operatörler daha sonra erişim haklarını geri kazandı; hangi muafiyetlerin verildiğini; ve Valve'nin Komisyon'a yaptığı açıklamayı destekleyen kayıtların neler olduğunu. Yasanın kamuoyunun incelemesine izin verdiği bilgileri yayınlayın. Bu kayıtları mevcut rotalarla ve Valve'in sonraki müdahaleleriyle karşılaştırın, bunlara şunlar da dahil olmak üzere: 2018'de OPSkins arşivlendi 2026-03-07 ↗.\n\nBildirimde Temmuz 2016’da on günlük bir süre belirlenmişti; on yıl, işlemin gerçekleştirilip gerçekleştirilmediğinin tespit edilmesi için yeterince uzun bir süredir. Komisyon, Valve’nin 2016 yılı hesaplarını, günümüzde hâlâ gözlemlenebilir durumda olan altyapı ile karşılaştırmalı.\n\nSteam Dossier Soruşturması · Kamuoyuna Yapılan Açıklama, 20 Eylül 2026\n\n2016 Komisyon bildirimi ↗ arşivlendi 2026-05-20 ↗ · Valve'nin 2016 tarihli cevabı (belge kopyası) ↗ · Valve'nin 2016 OpenID beyanı ↗ arşivlendi 2026-09-21 ↗ · Mevcut Steam anlaşması ↗ arşivlendi 2026-09-21 ↗ · 2016 değişim programının zaman çizelgesi: 11. Bölüm →\n\nA Bölümü — Teknik kayıt · 3. Kısım\nSite engellenmiş. Oturum açma sayfası ise engellenmemiş.\n\nEngellenen 26 ana alan adı. Her birinin arkasındaki kimlik doğrulama proxy’si ve ne kadar süredir aktif olduğu. Bu ayrı kimlik doğrulama sunucuları, tesadüfi ikinci adresler değildir — her biri bir Steam için kimlik doğrulama proxy’si, platform ile Valve'un OpenID uç noktası arasında yer alarak, engellenen etki alanının artık açık bir şekilde taşıyamadığı oturum açma bilgilerini taşıyor. Valve, Link Filter'a bir ön kapı ekledi. Oturum açma işlemi proxy üzerinden devam etti: csgogem.com engellenmiş durumda ve api.csgem.com Mart 2014'ten beri kayıtlıdır — on iki buçuk yıl. O günlerin her birinde, söz konusu sunucu kendi sunucu adını Valve'un OpenID uç noktasına gönderdi ve Steam bunu oturum açma sayfasında doğrudan kullanıcıya gösterdi. Valve, bu rotaların her birinin içinden geçtiği ana yoldur; bu rotaları bulması gerekmez. Bu bölümün ölçtüğü şey budur: bir uyarının olup olmadığı değil, uyarının ardındaki güzergâhın kaç yıl boyunca açık kaldığıdır. Kayıtlarda 44 ayrı etki alanına ait güzergâh bulunmaktadır; bunların 27’si için güzergâh başına bir kanıt dosyası yayınlanmıştır — aşağıdaki tablo. Bir örneği inceleyin, ardından hepsini değerlendirin.\n\nŞekil 3.1 — Çizilmiş iki güzergâh.\n\nTek bir platform, tek bir kullanıcı, aynı tarayıcıdan gönderilen iki istek. Valve'nin Bağlantı Filtresi her ikisinde de devreye girer. Bağlantı içeren isteği engeller, oturum açma bilgilerini içeren isteği ise geçirir. Bu bölümde ölçülen her şey, alt rotanın ne kadar süre açık kaldığının sayımını yansıtmaktadır.\n\nThe player\none browser, one session\nrollbit.com\nthe platform's main domain\nrbsnin.com\nseparate authentication host\nLINK FILTER\n✕ BLOCKED\nLINK FILTER\n✓ CLEAN\nsteamcommunity.com\nOpenID endpoint · signs in\nno route\nSteam'da paylaşılan bağlantı — durdurulduGiriş talebi — geçişler19 ve 21 Eylül 2026 tarihli kaydedilmiş çekler\n\nHer iki istek de Valve tarafından görülebilir ve bunlardan yalnızca biri işleme alınır. Bağlantı Filtresi, Valve öğeli bir listedir ve Valve hizmet tarafından kontrol edilir. OpenID isteği, kimlik doğrulama sunucusunun kendi adını Valve'nin uç noktasına taşır ve bu uç nokta, adı doğrudan oturum açma sayfasında görüntüler. Sunucu adı her durumda istekte bulunur — aradaki fark, bu adla herhangi bir işlem yapılıp yapılmadığıdır.\n\nTek bir platform. İki farklı güzergâh.ROLLBIT / KAYDEDİLMİŞ GÖZLEMLER\nAdım 5 / 5\n\nİstek Steam değerine ulaşır. Gözlemlenen yol, Steam'un oturum açma formuna ulaştı. Yazarlar oturum açma işlemini tamamlamadılar. Ana etki alanı bağlantısının engellenmesi, forma giden bu gözlemlenen yolu engellemedi.\n\n01 BAĞLANTı FİLTRESİ KONTROLÜ\nHEDEFrollbit.comPlatformun ana etki alanı\nSTEAM LINK FİLTRESİBağlantıyı kontrol ederAyrı bir varış noktası uyarı sistemi\nKAYDEDİLEN SONUÇBağlantı engellendi19 ve 21 Eylül 2026\n02 GÖZLENEN GİRİŞ YOLU\nPERONDASteam ile giriş yapPlatform bir OpenID isteği başlatır\nAYRI OTORİTE SUNUCUSUrbsnin.comKaydedilen kontrolde “Bağlantı Filtresi” bloğu yok\nSTEAMGiriş formu görüntülendiİstenen ana bilgisayar, Steam'un bildiriminde görünüyor\nOrijinal kayıt notlarını, kayıt tarihini ve protokol ayrıntılarını inceleyin\nValve'nin uygulanması nasıl gerçekleşiyor?\nAna etki alanı: engellendi\nKullanıcı\n→\nrollbit.com\n(ana alan adı)\n↓\nSTEAM LINK FİLTRESİ — ENGELLENMİŞ\n\"Bağlantı Engellendi!\" — potansiyel olarak zararlı olarak işaretlendi\nrollbit.com, 2026-09-19 ve 2026-09-21 değerlerinde bir Bağlantı Filtresi engellemesi döndürdü (kimlik doğrulaması yapılmamış kontrol; ham HTML ve SHA-256 kaydedildi). Görünür ve denetlenebilir bir kayıt.\nAslında neler oluyor — kimlik doğrulama\nOtantikasyon sunucusu: engellenmemiş\nKullanıcı\n→\nrollbit.com\n\"Steam ile giriş yap\"\n↓\nAyrı bir kimlik doğrulama sunucusu üzerinden yönlendirme:\nrbsnin.comBağlantı Filtresi: TEMİZ\nkayıtlı 2026-09-18T09:34:52Z (Verisign RDAP)\n↓\nSteam giriş sayfası uyarısı (2026-09-20):\n\"Note that rbsnin.com is not affiliated with Steam or Valve\"\nSteam, aldığı isteğin openid.realm'inden bu bildirimi görüntüler.\n↓\nSteam ayrı bir sunucuya yönlendirilen oturum açma formu\nYazarlar tarafından oturum açma işlemi tamamlanmadı; süreç, Steam formuna kadar izlendi.\nValve, bu tür her istekte return_to / realm ana bilgisayar adını alır. rbsnin.com, 2026-09-21 için herhangi bir Link Filter engellemesi döndürmedi.\nTalep üzerine\nOpenID sağlayıcısı olarak Steam, her kimlik doğrulama isteğiyle birlikte kimlik doğrulama ana bilgisayar adını alır: bu bilgi, Valve'un kendi sunucularına openid.return_to ve openid.realm parametreler.\nSite tarafından gönderildi\nOturum açma sunucusu tarama yoluyla tespit edilemiyor — platform, her istekte bunu Steam adresine gönderiyor. OpenID 2.0 §9.1 uyarınca return_to biçimsel olarak isteğe bağlıdır, ancak bu olmadan Steam oturum açma sonucunu veremez; dolayısıyla Steam ile oturum açmanın çalışması için fiilen gereklidir. Steam ise kullanıcıya ana bilgisayar adını bile gösterir (\"<host>, Steam veya Valve ile herhangi bir bağlantısı yoktur\").\n14 yaş\nBu, 2026-09-21 kontrolünde hâlâ Steam oturum açma kaydı bulunan en eski yetki sunucusunun yaşıdır (dota2.net, kayıt tarihi 2011-10-29); en yenisi ise üç günlük (rbsnin.com). \"Engellenen 0 kimlik doğrulama sunucusu\" rakamını bir bulgu olarak yorumlamayın. Engellenmiş bir kimlik doğrulama sunucusu, platformun “Steam ile Giriş Yap” özelliğini tamamen devre dışı bırakır; bu nedenle, başarılı oturum açma işlemlerinden oluşturulan bir kayıt, yalnızca hiçbir zaman engellenmemiş sunucuları içerebilir. Anlam ifade eden sayı, engelleme sayısı değildir — asıl önemli olan, ana etki alanının Link Filtresinde kaç yıl kalmış olduğu ve bu süre zarfında yanındaki oturum açma işleminin çalışmaya devam edip etmediğidir.\nAyrı etki alanına sahip kimlik doğrulama sunucuları: kayıt tarihi ile ana etki alanı karşılaştırması (30 yol: 2026-09-21 tarayıcı denetiminde çözümlenen 25 tanesi artı 2026-09-22 tarihinde eklenen 5 tanesi)\nPlatform\tBağlantı Filtresi: ana\tOtantikasyon sunucusu\tBağlantı Filtresi: auth host\tOtantikasyon sunucusu kaydedildi\tGözlem kaynağı\tDelil dosyası\nRollbit\nrollbit.com · kayıt 2014-11-08\n\tENGELLENDİ\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\trbsnin.com\tTEMİZ\n2026-09-21 · ham HTML (Wayback anlık görüntüsü yok)\n\t2026-09-18\n09:34:52Z, Verisign RDAP\n\tSteam giriş sayfası uyarısı, 2026-09-20\trollbit.com.json\nSkin.Club\nskin.club · kayıt 2017-09-04\n\tENGELLENMİŞ\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\tsc-auth.net\tTEMİZ\n2026-09-21 · Wayback 2026-09-21\n\t2019-04-02\nRDAP\n\tSteam giriş sayfası uyarısı\tskin.club.json\nHowl.GG\nhowl.gg · kayıt 2017-03-16\n\tENGELLENMİŞ\n2026-09-18, 19 Eylül, 21 Eylül · Wayback 2026-09-21\n\thowl.uno\tTEMİZ\n2026-09-21 · Wayback 2026-09-21\n\t2026-08-11\nRDAP\n\tCanlı tarayıcı ekran yakalama + sağlanan OpenID URL'si\thowl.gg.json\nDuelbits\nduelbits.com · kayıt 2020-02-03\n\tENGELLENMİŞ\n2026-09-21 · Wayback 2026-09-21\n\tswitchflips.com\tTEMİZ\n2026-09-21 · Wayback 2026-09-21\n\t2020-04-21\nRDAP\n\tSağlanan OpenID URL’si\tduelbits.com.json\nCSGOFast\ncsgofast.com · kayıt 2015-03-27\n\tENGELLENMİŞ\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\tsteam-login.authtofast.com\tTEMİZ\nauthtofast.com, 2026-09-21 · Wayback 2026-09-21\n\t2026-06-30\nauthtofast.com, RDAP\n\tCanlı tarayıcı ekran yakalama + sağlanan OpenID URL'si\tcsgofast.com.json\nFarmskins\nfarmskins.com · kayıt 2016-03-23\n\tENGELLENMİŞ\n2026-09-19, 2026-09-21 · ham HTML\n\tsteam.kobal.cc\tTEMİZ\n2026-09-19, 2026-09-21 · ham HTML\n\t2017-01-07\nkobal.cc, RDAP\n\tCanlı tarayıcı ekran kaydı + sağlanan OpenID URL'si\tfarmskins.com.json\nCobaltLab\ncobaltlab.tech\n\tENGELLENMİŞ\n2026-09-21 · ham HTML\n\tcobaltauth.com\tTEMİZ\n2026-09-21 · ham HTML\n\t2025-01-07\nRDAP\n\tSağlanan OpenID URL'si\tcobaltlab.tech.json\nCSGO.NET\ncsgo.net · kayıtlı 2012-07-22\n\tENGELLENMİŞ\n2026-09-21 · ham HTML\n\tcn2.easylot.net\tTEMİZ\n2026-09-21 · ham HTML\n\t2016-09-03\neasylot.net, RDAP\n\tCanlı tarayıcı ekranı yakalama\tcsgo.net.json\nGGDrop\nggdrop.com\n\tENGELLENMİŞ\n2026-09-21 · ham HTML\n\tggauth.com\tTEMİZ\n2026-09-21 · ham HTML\n\t2023-05-03\nRDAP\n\tSağlanan OpenID URL’si\tggdrop.com.json\nRustChance\nrustchance.com\n\tENGELLENMİŞ\n2026-09-21 · ham HTML\n\thgfuihd.com\tTEMİZ\n2026-09-21 · ham HTML\n\t2019-01-27\nRDAP\n\tSağlanan OpenID URL’si\trustchance.com.json\nSkin.Fans\nskin.fans\n\tENGELLENMİŞ\n2026-09-21 · ham HTML\n\tauth.skinfans.com\tTEMİZ\n2026-09-21 · ham HTML\n\t2018-07-16\nskinfans.com, RDAP\n\tSağlanan OpenID URL’si\tskin.fans.json\nSkinport\nskinport.com · kayıt 2018-09-05\n\tENGELLENMİŞ\n2026-09-21 · ham HTML\n\tskinport.app\tTEMİZ\n2026-09-21 · ham HTML\n\t2020-06-20\nRDAP\n\tCanlı tarayıcı ekran yakalama + sağlanan OpenID URL'si\tskinport.com.json\nSkins.Cash\nskins.cash\n\tENGELLENMİŞ\n2026-09-21 · ham HTML\n\tskinscash.live\tTEMİZ\n2026-09-21 · ham HTML\n\t2019-12-05\nRDAP\n\tSağlanan OpenID URL'si\tskins.cash.json\nTF2Hunt\ntf2hunt.com · kayıt 2018-01-13\n\tENGELLENMİŞ\n2026-09-21 · ham HTML\n\trstspcl.com\tTEMİZ\n2026-09-21 · ham HTML\n\t2020-08-08\nRDAP\n\tCanlı tarayıcı ekran yakalama + sağlanan OpenID URL'si\ttf2hunt.com.json\nCSGOGem\ncsgogem.com · kayıt 2016-10-16\n\tENGELLENMİŞ\n2026-09-22 · ham HTML\n\tapi.csgem.com\ncsgem.com — ayrı olarak tescil edilebilir alan adı\n\tTEMİZ\n2026-09-22 · ham HTML\n\t2014-03-08\ncsgem.com, RDAP — kayıt defterindeki en eski alan adı\n\tManuel toplama + Bağlantı Filtresi yakalama\tlinkfilter-2026-09-22.json\nGamdom\ngamdom.com · kayıt 2016-07-29\n\tENGELLENMİŞ\n2026-09-22 · ham HTML\n\tlogin.gambldom.com\ngambldom.com — markadan sadece bir harf farklı\n\tTEMİZ\n2026-09-22 · ham HTML\n\t2017-09-24\ngambldom.com, RDAP\n\tManuel toplama + Bağlantı Filtresi yakalama\tlinkfilter-2026-09-22.json\n12CS\n12cs.fail · kayıtlı 2026-03-24\n\tENGELLENMİŞ\n2026-09-22 · ham HTML\n\tfail.games\tTEMİZ\n2026-09-22 · ham HTML\n\t2021-08-24\nfail.games, RDAP\n\tManuel toplama + Bağlantı Filtresi yakalama\tlinkfilter-2026-09-22.json\nCSGOEmpire\ncsgoempire.com · kayıt 2015-06-10\n\tTEMİZ\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\tcsgoempirelogin4.com\n10 numaralı alan adından biri: login1–10\n\tTEMİZ\n2026-09-21 · Wayback 2026-09-21\n\t2020-07-20\n05:49:17Z, Verisign RDAP\n\tCanlı tarayıcı ekranı yakalama\tcsgoempire.com.json\nCS.MONEY\ncs.money\n\tTEMİZ\n2026-09-21 · ham HTML\n\tauth.dota.trade\tTEMİZ\n2026-09-21 · ham HTML\n\t2016-07-15\ndota.trade, RDAP\n\tSteam giriş sayfası uyarısı\tcs.money.json\nCSFloat\ncsfloat.com · kayıtlı 2021-07-11\n\tTEMİZ\n2026-09-21 · ham HTML\n\tcsgofloat.com\nOperatörün eski marka alan adı; ayrı bir tescil edilebilir alan adıdır, kaçakçılık göstergesi değildir\n\tTEMİZ\n2026-09-21 · ham HTML\n\t2015-09-29\nRDAP\n\tCanlı tarayıcı ekranı yakalama\tcsfloat.com.json\nG4Skins\ng4skins.com\n\tTEMİZ\n2026-09-21 · ham HTML\n\tauth.g4s.to\tTEMİZ\n2026-09-21 · ham HTML\n\t2021-05-30\ng4s.to, RDAP\n\tSağlanan OpenID URL’si\tg4skins.com.json\nJuice.GG\njuice.gg\n\tTEMİZ\n2026-09-21 · ham HTML\n\tletmeinjuice.com\tTEMİZ\n2026-09-21 · ham HTML\n\t2024-04-15\nRDAP\n\tSağlanan OpenID URL’si\tjuice.gg.json\nMarket.CSGO\nmarket.csgo.com\n\tTEMİZ\n2026-09-21 · ham HTML\n\tdota2.net\tTEMİZ\n2026-09-21 · ham HTML\n\t2011-10-29\nRDAP\n\tCanlı tarayıcı ekran kaydı + sağlanan OpenID URL'si\tmarket.csgo.com.json\nRust.TM\nrust.tm\n\tTEMİZ\n2026-09-21 · ham HTML\n\tdota2.net\tTEMİZ\n2026-09-21 · ham HTML\n\t2011-10-29\nRDAP\n\tSağlanan OpenID URL’si\trust.tm.json\nCSGOLounge\ncsgolounge.com · kayıt 2013-08-14\n\tTEMİZ\n2026-09-22 · ham HTML\n\tdota2.net\nBu kimlik doğrulama sunucusundaki üçüncü ön uç\n\tTEMİZ\n2026-09-22 · ham HTML\n\t2011-10-29\ndota2.net, RDAP\n\tManuel toplama + Bağlantı Filtresi ile yakalama\tlinkfilter-2026-09-22.json\nDota2Lounge\ndota2lounge.com · kayıt 2012-08-10\n\tTEMİZ\n2026-09-22 · ham HTML\n\tdota2.net\nbu kimlik doğrulama sunucusundaki dördüncü ön uç\n\tTEMİZ\n2026-09-22 · ham HTML\n\t2011-10-29\ndota2.net, RDAP\n\tManuel toplama + Bağlantı Filtresi yakalama\tlinkfilter-2026-09-22.json\nSkinBaron\nskinbaron.de\n\tTEMİZ\n2026-09-21 · ham HTML\n\tskinbaron.com\naynı marka, farklı TLD\n\tTEMİZ\n2026-09-21 · ham HTML\n\t2015-12-22\nRDAP\n\tSağlanan OpenID URL’si\tskinbaron.de.json\nTF2Royal\ntf2royal.com · kayıt 2022-08-17\n\tTEMİZ\n2026-09-21 · ham HTML\n\ttf2auth.com\tTEMİZ\n2026-09-21 · ham HTML\n\t2021-07-27\nRDAP\n\tCanlı tarayıcı ekran yakalama + sağlanan OpenID URL'si\ttf2royal.com.json\nTradeit\ntradeit.gg\n\tTEMİZ\n2026-09-21 · ham HTML\n\tconnect-tradeit.com\tTEMİZ\n2026-09-21 · ham HTML\n\t2022-02-23\nRDAP\n\tSağlanan OpenID URL’si\ttradeit.gg.json\nYükseltici\nupgrader.pro\n\tTEMİZ\n2026-09-21 · ham HTML\n\tupgauth.space\tTEMİZ\n2026-09-21 · ham HTML\n\t2026-08-14\nRDAP\n\tSağlanan OpenID URL’si\tupgrader.pro.json\nKaynak: steamcommunity.com/linkfilter, kimlik doğrulaması yapılmamış GET isteği, 2026-09-21, 53 ana bilgisayar, 3 saniye aralık; steam_tos_assets/linkfilter-recheck-2026-09-21.json; içindeki ham HTML steam_tos_assets/linkfilter-raw/. Kayıt tarihleri: RDAP, steam_tos_assets/domain-registration.json. · 2026-09-19 değerinin daha erken kontrolü linkfilter-all-results.json · rota kayıtları auth-route-audit.json · Link Filter sayfalarının Wayback Machine anlık görüntüleri, 2026-09-21, aşağıda listelenmiştir: wayback-snapshots.json (rbsnin.com için herhangi bir anlık görüntü bulunmamaktadır; yerel ham dosya tek kayıttır).\n\nKayıt tarihleri: RDAP (steam_tos_assets/domain-registry/). “Sağlanan OpenID URL’si” istek parametrelerini belirler; tamamlanmış bir oturum açma işlemini değil. Yazarlar tarafından hiçbir platformda oturum açma işlemi tamamlanmamıştır. Ayrı bir etki alanı tek başına kaçışın kanıtı değildir. \"Engellenen 0 kimlik doğrulama sunucusu\" da bağımsız bir bulgu değildir: Birini engellemek o platformun Steam oturum açma işlemini bozacaktır, bu nedenle çalışan oturum açma işlemlerinden derlenen bir kayıt, engellenmiş bir kimlik doğrulama sunucusu içeremez. Ağırlığı olan gözlem, eşleşme ve bunun süresidir — Link Filtresinde yıllardır çalışan bir oturum açma etki alanının yanında yer alan bir ana etki alanı. Bu tablo 30 satır içermektedir: rota başına kanıt dosyası bulunan 27 rotadan 25’i, artı 2026-09-22’da eklenen ve Link Filtresindeki bölünmesi linkfilter-2026-09-22.json her ne kadar bu alan adı elle eklenmiş olsa da — kaynak sütunundaki satırlarda bu belirtilmiştir. Gösterilmeyen iki kanıt dosyası yolu ise skinsnipe.com (yetkilendirme sunucusu pricing.tradeupspy.com, kayıtlı 2020-03-11) ve csgobig.com (yetkilendirilmiş ana bilgisayar letmeinbig.com, kayıtlı 2023-01-20); her ikisi de 2026-09-22 kontrolünde “BLOCKED main / CLEAN auth host” sonucunu verdi; bu sonuç, SHA-256 ile şifrelenerek linkfilter-2026-09-22c.json, ancak bu grubun ham HTML kodu yayınlanan küme içinde yer almadığından, bu tabloda her iki satırda bir görüldüğü gibi bir satır atanmak yerine burada adlarıyla belirtilmişlerdir. Kayıt defterinde yer alan ve elle derlenen geri kalan 12 güzergâh, şu şekilde tanımlanmıştır: master_registry.json altında realm_src: user.\n\nBirincil Ampirik Denetim · Çok Yıllık Tarih Aralığı\nBüyük Resim Tuzağı: Link Filter, bir koruma kalkanı değil, sadece görünüşte uyum sağlama çabasıdır\n\nMasaüstü tarayıcılarda kullanıcılar, harici güvenlik önlemleriyle korunur: Google Güvenli Tarama ve Microsoft SmartScreen, bilinen kimlik avı girişimlerini tam ekran kırmızı uyarılarla engeller. Steam'ın Geniş Görünüm modunda, oyun içi üst katman (Shift+Tab) ve Steam Kart Desteği (SteamOS) içinde bu savunma mekanizmaları mevcut değildir. Yerleşik tarayıcı hiçbir eklentiyi desteklemez, harici Güvenli Tarama motorlarını devre dışı bırakır ve kullanıcıya tam olarak tek bir koruma bariyeri bırakır: Valve'ler linkfilter interstisyel.\n\nDört sonucu karşılaştırmak için kaydırın →\n\n92.5%\n2025–2026: Modern uç noktalı oltalama sorunsuz geçti (37/40)\n77.5%\n2023–2024 CS2 dönemi kimlik avı sorunsuz geçti (31/40)\n70.0%\n2021–2022 eski tip kimlik avı sorunsuz geçti (28/40)\n7 / 7\nkumar şebekeleri engellendi (olumlu kontrol)\nÇok Yıllık Boylamsal Denetim: Canlı Olarak Test Edilen 120 Tamamen Steam Olan Kimlik Avı Alan Adı (24 Eylül 2026)\n\nValve'nin filtresinin yeni tehditleri algılamada sadece yavaş mı olduğu yoksa bu tehditlere karşı temelde kör mü olduğunu test etmek için, bir denetim gerçekleştirdik 120 adet doğrulanmış Steam'a özgü kimlik avı etki alanı üç tarihsel kohortta karşılaştırıldığında steamcommunity.com/linkfilter:\n\n1. Grup: 2021–2022 (Klasik Takas Teklifi ve Öğe Düşürmeleri) — 70.0% Tam Başarı (28/40). Topluluk denetçileri tarafından listelenmelerinden 4 ila 5 yıl sonra bile, eski kimlik avı sunucularının 10’undan 7’si hâlâ herhangi bir engelleme olmaksızın erişime açıktır.\n2. Grup: 2023–2024 (CS2 Beta Heyecanı ve Sahte Destek İtirazları) — 77.5% Tam Başarı (31/40). Counter-Strike 2 sürümlerini taklit eden kampanyalar ve sahte topluluk çağrıları (örn. cs2-steam.com, appealsteamcommunity.help) doğrudan içinden geçer.\n3. Grup: 2025–2026 (Sunucusuz Kenar Dağıtımları ve Favicon Kopyaları) — 92.5% Tam Başarı (37/40). EdgeOne, Vercel ve Cloudflare Pages üzerinde dağıtılan modern kimlik avı kitleri (örneğin, steamgifter.online, steam-dp4lt5b8fnez.edgeone.dev) neredeyse hiç engel olmadan geçebiliyorlar.\n\nTelemetri ve Sorumluluk Koruması, Koruma Değil. Link Filter, saf Steam türündeki kimlik avı saldırılarını 70%’dan 92.5%’e geçiriyorsa neden var? Bu filtre, kurumsal sorumluluk feragatnamesi ve dışarıya yönelen tıklama telemetri sensörü olarak işlev görür. Kibar bir şekilde \"Steam'dan ayrılıyorsun\" Tıklanabilir yeşil bir “Devam Et” düğmesi içeren bildirim, Valve numaralı madde, Steam numaralı Abone Sözleşmesi uyarınca hukuki sorumluluğu mağdura yükler (*“kullanıcı, Steam dışına kendi iradesiyle yönelmiştir”*). Valve tıklamanın telemetri verilerini toplar, ancak hırsızlığı engellemez.\n\nFavicon Hash Kanıtı: Tehdit Beslemelerinin Hiçbir Şekilde Alınmaması. Bağımsız tehdit istihbarat platformları (urlscan.io, Shodan, Censys), Steam’in resmi favicon hash’ini basit bir arama yoluyla tespit ederek aktif Steam kimlik avı kitlerini belirler (page.favicon.hash:9f890a9debcdfccc339149a7943be9aff9e4c9203c2fa37d5671a5b2c88503ad NOT domain:*.steampowered.com). Bu temel otomatik kontrol, aktif kimlik avı kümelerini saniyeler içinde ortaya çıkarır. Valve, harici veri akışlarıyla senkronize olmaz, hash tabanlı tehdit avcılığı yürütmez ve yalnızca düzenleyici kurumlar tarafından zorunlu kılındığında (2016 WSGC kumar kararı) veya tescilli etki alanı dizelerini korumak amacıyla manuel olarak müdahale eder.\n\nBirincil denetim kanıtı niteliğindeki belgeler: 120 alandan oluşan uzun vadeli, çok yıllı denetim: boylamsal-buhar-kimlik-avı-denetimi.json · 100 adet özel Steam kimlik avı örneği: linkfilter-steam-phishing-100.json · Kapsamlı yem denetimi (n=250): linkfilter-coverage-2026-09-22.json.\n\nCSGOEmpire — on adet numaralı yetkilendirme alan adının toplu kaydı\n\nTarih: 2020-07-20 on numaralı alan adı, csgoempirelogin1.com aracılığıyla csgoempirelogin10.com, kaydedildi. On hesabın tümü için Verisign RDAP zaman damgaları kayıtlarda yer almaktadır: login1 05:49:06Z, login5 05:49:08Z, login2 05:49:11Z, login3 05:49:14Z, login4 05:49:17Z, login6 05:49:20Z, login7 05:49:23Z, login8 05:49:26Z, login9 05:49:28Z — 22 saniyede dokuz alan adı — ve yedi dakika sonra, 05:56:03Z'de login10. Aralığın, tek bir kayıt kuruluşu tarafından gerçekleştirilen toplu işlemle tutarlı olduğu görülmektedir.\n\nBu model, önceden ayarlanmış yedek ana bilgisayarlarla tutarlıdır; yalnızca login4 Canlı bir OpenID isteğinde gözlemlenmiştir. csgoempire.com ve csgoempirelogin4.com, 2026-09-21'daki Bağlantı Filtresinde her ikisi de “CLEAN” sonucunu vermiştir; CSGOEmpire, Temmuz 2016 tarihli bildirimlere ilişkin basın haberlerinde adı geçen siteler arasında yer almamıştır.\n\n# DNS — 10'unun tamamı aktif (Eylül 2026)\nTamam csgoempirelogin1.com 172.67.129.43\nTamam csgoempirelogin2.com 172.67.175.168\nTamam csgoempirelogin3.com 188.114.96.3\nTamam csgoempirelogin4.com 188.114.96.11 ← OpenID trafiğinde\nTamam csgoempirelogin5.com 172.67.160.194\nTamam csgoempirelogin6–10.com Cloudflare IP adresleri\nNXDOMAIN: csgoempirelogin11.com\n10'unun tamamı 2020-07-20 olarak kaydedildi; 10'unun tamamı RDAP zaman damgası ile işaretlendi (steam_tos_assets/domain-registry/csgoempireloginN.com.rdap.json)\nDüzenleyici kurumlar için sonuç\nEngellenmiş bir ana etki alanı ile engeli kaldırılmış bir kimlik doğrulama sunucusunun bir araya gelmesi, oturum açma yolunu açık bırakır — ve bu yol yıllarca açık kalır.\n\nAna etki alanındaki Link Filter bloğu, doğrulanabilir, herkese açık bir kayıttır. Kimlik doğrulama sunucusu, \"Steam ile oturum aç\" trafiğini taşır ve Valve'nin kendi OpenID istek parametrelerinde görünür. 2026-09-21 ve 2026-09-22 üzerinde yapılan çapraz kontrollerde, 26 filtre-bölünmüş çiftte ana etki alanı bir Link Filter bloğu döndürürken, oturum açma işlemini taşıyan proxy hiçbir blok döndürmedi. Yukarıdaki kayıt, bunun diğer yarısını ölçer: bu ana bilgisayarlar kısa ömürlü geçici etki alanları değildir. Birkaç tanesi, kontrol tarihinde on yıldan fazla bir süredir kayıtlıydı ve bu günlerin her biri, Valve'ün kendi istek parametrelerinde bu ana bilgisayar adını aldığı günlerdir. Valve, operatör bazında herhangi bir yaptırım kaydı yayınlamamıştır; dolayısıyla bu ana bilgisayarlara başka herhangi bir önlem uygulanıp uygulanmadığı, kamuya açık verilerden tespit edilememektedir.\n\n12 yıl 6 ay\ncsgogem.com, Bağlantı Filtresinde engellenmiştir.\nGiriş yaptığı ana bilgisayar api.csgem.com şu zamana kadar\n2014-03-08 yılından beri kayıtlıdır, ancak öyle değildir.\nBasit Dille Özet — Düzenleyici Kurumlar ve Mahkemeler İçin (genişlet)\nBasit dilde özet — düzenleyici kurumlar için\nArka plan: Steam nedir ve bu bağlamda neden önemlidir?\n\nSteam, Valve Corporation (Bellevue, Washington, ABD) tarafından işletilen bir yazılım platformudur. Steam, bir dijital kimlik sağlayıcısı olarak işlev görür: İnternet üzerindeki kumar ve oyun siteleri, \"Steam ile giriş yap\" adlı bir sistemi kullanır — bu düğme, bir web sitesinin ziyaretçinin gerçek bir Steam hesabına sahip olduğunu doğrulamasını sağlar. Bu, \"Google ile Giriş Yap\" seçeneğine veya devlet tarafından verilen kimlik kartı kontrolüne benzer: web sitesi kullanıcıyı Steam'in sunucularına yönlendirir, Steam kullanıcının kimliğini doğrular ve Steam kullanıcıyı web sitesine geri gönderir. Valve, kimlik doğrulama sistemini işletmektedir. \"Steam ile giriş yap\" seçeneği üzerinden gerçekleştirilen her bir oturum açma işlemi, Valve'in kendi sunucularından geçer.\n\nValve'ın Yaptığı Şey: Etki Alanı Engelleme\n\nTemmuz 2016’da, “skin gambling” konusunda medyadan ve hukuki makamlardan gelen baskının ardından, Valve’ın avukatı, adı geçen yaklaşık 23 kumar sitesine bildirim gönderdi (21 Temmuz 2016 tarihli basın haberlerine göre); Ekim 2016'da Valve, Washington Eyaleti Kumar Komisyonu'na kırktan fazla siteyle iletişime geçtiğini bildirdi. Bazı kumar alan adları Steam Bağlantı Filtresi — Steam içinde (sohbette, profil sayfasında, mağazada) bu hesaplara ait paylaşılan herhangi bir bağlantının bir uyarı sayfası gösterilmesini sağlayan bir liste: \"Bağlantı Engellendi!\" Bağlantı Filtresi, etkisi Valve’ın dışından gözlemlenebilen tek uygulama önlemidir.\n\nÖrnek: Şu sayfaya bir bağlantı: rollbit.com Steam seçeneği, Bağlantı Filtresi uyarı sayfasını görüntüler (2026-09-19 ve 2026-09-21 seçenekleri işaretlendiğinde). Teorik olarak, kumar sitesi engellenmiştir.\nProxy Etki Alanı Nedir?\n\nA Ayrı etki alanlı kimlik doğrulama sunucusu, bir kimlik doğrulama proxy'sidir: Aynı operatörün, yalnızca “Steam ile giriş yap” adımını gerçekleştirmek amacıyla kullanıcıları ile Steam arasına yerleştirdiği, farklı bir tescil edilebilir alan adında bulunan ikinci bir web sitesi adresi. Bu adres, oturum açma işlemini aracılık eder. Kullanıcı, platforma giriş yaptığını sanır; Valve'a ulaşan istek, platformun değil, proxy'nin ana bilgisayar adını taşır. Genellikle kumar sitesiyle kamuya açık bir bağlantısı yoktur ve Steam kullanıcıların kimliğini doğruladıktan sonra kullanıcıları geri yönlendiren adres budur.\n\nÖrnek: Rollbit, şu şartlar altında faaliyet göstermektedir: rollbit.com, ki bu Link Filtresi tarafından engellenir. Steam kimlik doğrulaması için, 2026-09-20 üzerinde gözlemlenen akış ayrı bir adres kullanıyordu: rbsnin.com, kayıtlı 2026-09-18. Bu adres şu sonucu verdi: Link Filter bloğu yok 2026-09-21 tarihinde. Kumar sitesi faaliyetlerine devam etti ve Steam numaralı oturum açma akışı, engeli kaldırılmış sunucu üzerinden gerçekleştirildi.\nKritik Nokta: Her İstekte Kimlik Doğrulama Sunucusu Steam Değerine Gönderiliyor\n\nValve, hangi kimlik doğrulama sunucularının kullanıldığını öğrenmek için tarama veya indirme işlemine gerek duymaz. Steam ise OpenID kimlik sağlayıcısı bu siteler için ve her bir “Steam ile oturum aç” tıklaması, kimlik doğrulama ana bilgisayar adını düz metin olarak içeren bir GET isteğini Valve’ın kendi sunucularına gönderir. OpenID 2.0 §9.1 uyarınca, return_to Bu alan resmi olarak isteğe bağlıdır, ancak bu alan olmadan Steam oturum açma sonucunu veremez; dolayısıyla, Steam ile oturum açmanın düzgün çalışması için bu alan fiilen zorunludur. Steam, oturum açma sayfasında ana bilgisayar adını kendisi görüntüler (\"<host>, Steam veya Valve ile herhangi bir bağlantısı bulunmamaktadır\").\n\n— Steam’in aldığı isteğin biçimi (2026-09-20’da Rollbit için gözlemlenen ana bilgisayar): —\nAL steamcommunity.com/openid/login\n&openid.mode=checkid_setup\n&openid.return_to=https://rbsnin.com/… ← fiilen zorunlu; Valve'nin günlüğüne eklenir\n&openid.realm=https://rbsnin.com ← site tarafından belirtilmiştir; Steam'nin giriş sayfasında görüntülenmiştir\nSite, sunucu-sunucu doğrulama (check_authentication) özelliğini kullanıyorsa, Valve’un günlüğünde platformun sunucu IP’si ve barındırma ağı da kaydedilir.\n\nBu istekten ana bilgisayar adını çıkarmak standart bir işlemdir. Hangi ana bilgisayarlara işlem uygulandığı, hangilerine uygulanmadığı ve hangi kriterlere göre hareket edildiğini gösteren uygulama kaydı yalnızca Valve’un altyapısında mevcuttur ve kamuya açıklanmamıştır.\n\nBunun Kanıtladığı Şey\n\n1. Bağlantı Filtresi bloğu, oturum açma işlemleri üzerinde değil, bağlantılar üzerinde etki gösterir. Ana etki alanını engelleme (örneğin rollbit.com) Steam içindeki bağlantılara tıklayan kullanıcılara bir uyarı gösterir. Bu, sitenin çalışmasını engellemez; ayrıca sitenin farklı bir adres üzerinden Valve’un kendi OpenID hizmetini kullanmasını da engellemez.\n\n2. Test edilen kimlik doğrulama sunucuları engellenmemişti. Yukarıdaki tablo, 2011 ile Eylül 2026 arasında kaydedilmiş ayrı etki alanlı kimlik doğrulama sunucularını göstermektedir; bunların birçoğu, Temmuz 2016’daki bildirimlerden yıllar sonra kaydedilmiştir. 26 çiftte ana etki alanı bir Link Filter engellemesi döndürürken, oturum açma bilgilerini taşıyan proxy bunu yapmamıştır (kimlik doğrulaması yapılmamış kontroller, 2026-09-21 ve 2026-09-22; ham yanıtlar ve SHA-256 kaydedilmiştir). Söz konusu proxy, Valve tarafından reddedildiği gün çalışmayı durduracaktı; bu nedenle buradaki ölçüt, listede yer alıp almadığı değil, ne kadar süreyle çalıştığıdır. Valve, kendi OpenID isteklerinde bu ana bilgisayar adlarını alır. Link Filtresi dışında başka bir önlemin uygulanıp uygulanmadığı, kamuya açık verilerden belirlenemez; çünkü Valve, operatör bazında uygulama kayıtlarını yayınlamamıştır.\n\n3. Siteler, Valve'nin altyapısı üzerinden kimlik doğrulamasına devam etti. \"Steam ile giriş yap\" Valve’in sunduğu bir hizmettir; bu hizmet üzerinden yapılan her kimlik doğrulama, Valve’nin aldığı ve işlediği bir istektir. Valve ayrıca kasa anahtarlarından gelir elde eder ve Steam Topluluk Pazarı, Pazar içinde tamamlanan işlemler için (harici işlemler hariç) toplamda yaklaşık 15% tutarında bir ücret alır. Link Filtresi eylemi halka açık bir kayıt oluşturdu; kimlik doğrulama ilişkisini kesintiye uğratmadı.\n\nEngelleme İşe Yarar mıydı?\n\nBenzer bir örnek vermek gerekirse: Ücretsiz alan adı kayıt şirketi Freenom’un 2023 yılında faaliyetlerini sonlandırmasıyla, bu şirketin alan adlarına dayanan kimlik avı kampanyaları da kesintiye uğradı. Operasyonel süreklilik, altyapının istikrarına bağlıdır.\n\nAynı mantık burada da geçerlidir. Eğer bir kimlik doğrulama sunucusu, Steam’un OpenID işlemlerinde reddedilirse, yeni bir sunucu kaydedilene, sertifikalar düzenlenene ve DNS güncellemeleri yayılana kadar platformun “Steam ile giriş yap” işlevi çalışmaz hale gelir. Bu süre zarfında hizmet kesintisi yaşanır.\n\nDönüş, bloklamayı anlamsız hale getirmez. Bu durum, engellemeyi bir işletme maliyeti haline getirir. Yeni sunucular ilk kullanımda Valve'nin kendi istek günlüklerinde göründüğünden, bir yanıt bu ilk kullanımdaki hızda işlenebilir.\n\nToplu kayıt başlı başına bir işarettir: CSGOEmpire'a ait login1–login10 hesapları 2020-07-20 adresinde kaydedilmişti; bunlardan dokuzu 22 saniye içinde kaydedilmişti (Verisign RDAP). Yanıtların her bir alan adı için ayrı ayrı olması gerekmez; tek bir kayıt kuruluşu oturumundan gelen ardışık bir dizi, bir dizi olarak tanımlanabilir.\n\nKamu kayıtlarında, anahtar dönüşümüyle engellenen bir kimlik doğrulama sunucusunu engelleme girişimi görülmemektedir.\nBu tablo, her bir oturum açma işlemini gerçekleştiren proxy sunucusu çalışmaya devam ederken engellenen ana alan adlarını göstermektedir — 2026-09-22 itibarıyla 26 çift; kayıtlı en eski kimlik doğrulama sunucusu 12 yıl 6 aydır hizmet vermektedir — ve hiçbir operatör için yayınlanmış bir uygulama kaydı bulunmamaktadır.\nDolayısıyla düzenleyici kurum için soru şudur: Valve, kendi OpenID isteklerinde aldığı yetkilendirme sunucularına, varsa, hangi yaptırımları uygulamıştır?\nValve Ne Yaptı — ve Neden Otorizasyon Yolu'nu Kesintiye Uğratmadı?\n\nAşağıdaki tablo, kamuya açık olarak belgelenmiş her bir Valve eylemini, OpenID kimlik doğrulama giriş noktasını etkileyip etkilemediği açısından karşılaştırmaktadır. Sonuç, \"Valve hiçbir şey yapmadı\" değildir — kamuya açık olarak belgelenen eylemlerin hiçbirinin, kumar platformu oturum açma işlemlerinin Valve'nin sunucularından geçtiği noktaya dokunmadığıdır.\n\nTarih\tValve Eylem\tEtkilenen openid.return_to yol mu?\nTemmuz 2016\t13 Temmuz 2016 tarihli kamuoyuna yönelik açıklama; avukatın ~23 adede yakın adı belirtilen kuruluşa gönderdiği bildirimler (basın, 21 Temmuz 2016); Valve’nin Ekim 2016’da WSGC’ye gönderdiği mektup uyarınca >40 kuruluşla iletişime geçildi\tHayır. Bildirimler ve Bağlantı Filtresi, operatörler ve bağlantılar üzerinde etki gösterir; OpenID istek yolu değiştirilmedi.\n2017\t[Kapanış] IEconItems_730/GetPlayerItems (CSFloat'un mühendislik hesabına göre; Valve sürüm günlüğü bulunamadı)\tHayır. Etkilenen: Kamu öğelerinin geçmişinin görünürlüğü. OpenID kimlik doğrulaması değiştirilmedi.\n2018-03-29\tCS:GO'da 7 günlük takas kilidi duyuruldu (blog.counter-strike.net)\tHayır. Öğelerin hareketi yavaşladı; OpenID istek yolu değiştirilmedi.\n2022-05-10\tHalka açık Web API'sinden takas iptal uç noktaları kaldırıldı (kullanıcı tarafından tespit edildi; Valve değişiklik günlüğü yok — node-steam-tradeoffer-manager #325)\tHayır. Teklif-takas aracı kapatıldı; OpenID kimlik doğrulaması değiştirilmedi.\n2023-12-04\tAPI anahtarı oluşturmak için artık mobil onay gerekiyor (steamcommunity.com/dev/apikey; değişiklik günlüğü yok)\tHayır. Anahtar uç nokta korunmuştur; burada belirtilen kimlik doğrulama sunucuları bu durumdan etkilenmemiştir.\n2026-09-19 / 21 Eylül\tSteam Yazarlar tarafından gözlemlenen bağlantı filtresinin durumu\tKaydedilen 2026-09-21 yeniden kontrolünde 14 ana etki alanı bir engelleme döndürdü — kayıt defterinde 2026-09-22 ile 26 bölünmüş çift — oysa her bir oturum açma işlemini taşıyan vekil sunucu çalışmaya devam etti.\nKaynaklar: Valve 13 Temmuz 2016 tarihli açıklama (store.steampowered.com/oldnews/22883, arşivlendi 2026-09-21) · 2017'deki kapatma ile ilgili CSFloat mühendislik raporu (blog.csfloat.com, arşivlendi 2026-09-21) · Bağlantı Filtresi durumu: linkfilter-recheck-2026-09-21.json.\nBu bulgu, Valve’ın bir OpenID isteğini şu nedenle reddettiği tek bir yayınlanmış örnekle çürütülebilir: openid.return_to bir kumar lisans sunucusuna yönlendirilmişti. Kamuya açık kayıtlarda böyle bir örnek bulunamadı.\nEn son yapılan iki auth-host kaydı\nhowl.uno2026-08-11 (RDAP) olarak kaydedildi; 2026-09-21’den 41 gün önce; howl.gg, 2026-09-18, 2026-09-19 ve 2026-09-21’te bir Bağlantı Filtresi engellemesi döndürdü. Engellemenin kayıttan önce mi gerçekleştiği henüz kesinleşmemiştir.\nrbsnin.com2026-09-18T09:34:52Z (Verisign RDAP) olarak kaydedilmişti ve Steam'in kendi giriş sayfası uyarısı aracılığıyla 2026-09-20 tarihinde Rollbit'in Steam giriş akışında gözlemlendi; rollbit.com, 2026-09-19 ve 2026-09-21 tarihlerinde bir Link Filter engellemesi döndürdü, rbsnin.com ise döndürmedi.\nYukarıdaki tablodaki her bir ana bilgisayar, Valve'un kimlik doğrulama sunucularına şu şekilde gönderilir: openid.realm her oturum açma denemesinde.\nGüzergâh bazında tam veriler ve Bağlantı Filtresi kararları: yukarıdaki 3. Bölüm’deki tablo; ham sonuçlar linkfilter-recheck-2026-09-21.json ve linkfilter-all-results.json.\nMetodoloji — Güzergâh ve Bağlantı Filtre Sayımlarının Nasıl Belirlenmiş Olduğu\n1. Etki alanı çözümleme\n2026-09-21 denetimi, talep edilen 189 platformdan 78’ini sonuçlandırdı: 33'ü kendi ana bilgisayar adıyla, 20'si ise kendi alt etki alanıyla kimlik doğrulaması yapıyor — doğrudan kimlik doğrulama; bunların hiçbiri ayrı etki alanı rotaları olarak sayılmıyor. Geri kalan 25. Ayrı bir kayıt edilebilir alan adı üzerinden kimlik doğrulaması yapmak, 24 farklı ana bilgisayar adı üzerinden (dota2.net, market.csgo.com ve rust.tm tarafından paylaşılmaktadır): 10’u canlı tarayıcı ekran görüntüsüyle, 3’ü Steam’un kendi giriş sayfası bildirimiyle, 12’si ise sağlanan bir OpenID URL’siyle tespit edilmiştir. Canlı kayıt (master_registry.json, 2026-09-22) bunu şu şekilde genişletir: 44 ayrı etki alanı rotası: 26 filtre bölünmüş çift (ana etki alanı ENGELLENMİŞ, kimlik doğrulama sunucusu TEMİZ) artı ana etki alanı bölünmesi olmayan 18 ilave rota. Bu 44'ün, 27. Her güzergâh için bir kanıt dosyası bulundurmak; geri kalan 17 tanesi elle toplanmış ve işaretlenmiştir realm_src: user kayıt defterinde. Bu on yedi siteden beşi — csgogem.com, gamdom.com, 12cs.fail, csgolounge.com ve dota2lounge.com — 2026-09-22 tarihinde, her iki ana bilgisayarın Link Filter yakalaması (ham HTML + SHA-256, linkfilter-2026-09-22.json), dolayısıyla alan elle toplanmış olsa da bölünmenin kendisi kanıtlanmıştır; bunlar, kanıt dosyası rotalarıyla birlikte yukarıdaki tabloda yer almaktadır. tfauth.com (tf2easy.com) 2026-09-22 saatinde kayıt defterinden çıkarıldı: arena.fragnet.net gibi, bu siteyi asıl sitesiyle ilişkilendiren doğrulanabilir hiçbir bağlantı bulunmuyor. Sayı, yayınlanan verilerden yeniden hesaplanabilir auth-route-audit.json (2026-09-21 dizisi) tek bir kural uyarınca: Bir platform, yalnızca gözlemlenen Steam OpenID ana bilgisayarı, platformun kendisinden farklı bir kayıt edilebilir etki alanında yer alıyorsa sayılır.\n2. Steam Bağlantı Filtresi durumu\nŞu yöntemle test edilmiştir: steamcommunity.com/linkfilter/?url=https://[domain], kimlik doğrulaması yapılmamış, 2026-09-19 ve 2026-09-21 üzerinde; SHA-256 ile kaydedilmiş ham HTML. Durum, ana etki alanı ve kimlik doğrulama sunucusu için ayrı ayrı kaydedilmiştir. Bir sınıflandırıcı, genel \"Steam'den ayrılıyorsunuz\" uyarısını (CLEAN) \"Bağlantı Engellendi! ... potansiyel olarak zararlı olarak işaretlendi\" sayfasından (BLOCKED) ayırır; bir google.com kontrolü, ikisinin birbirine karıştırılmadığını doğrular. Bu testin daha önceki, kimlik doğrulamalı bir varyantı, söz konusu kontrol de dahil olmak üzere her etki alanı için \"engellendi\" sonucunu verdikten sonra geçersiz sayıldı — bunun nedeni, gerçek bir sonuç değil, sonda komut dosyasında bulunan geçersiz bir oturum çerezi olduğu tespit edildi.\n3. Otorite sunucusunun gözlemlenmesi\nCanlı yakalama: Bir Playwright tarayıcısı, her bir platformun oturum açma akışına yönlendirildi ve openid.return_to Ana bilgisayar adı, ele geçirilen istekten okundu. Giriş sayfası uyarısı: Ana bilgisayar adı, Steam'un kendi \"<host>, Steam veya Valve ile herhangi bir bağlantısı bulunmamaktadır\" metni, ki Steam şu şekilde görüntülenir: openid.realm (rbsnin.com, sc-auth.net, auth.dota.trade). Sağlanan URL: Yazarlar’a verilen bir Steam oturum açma bilgisi URL’si; bu, tamamlanmış bir oturum açma işlemini değil, istek parametrelerini belirler. Hiçbir platformda oturum açma işlemi tamamlanmamıştır.\n4. Kapsam — nelerin çözülmediği ve bunun neden önemli olduğu\n189 platformdan, 110 numaralı güzergâhta belirlenmiş bir rota bulunmamaktadır ve bunlardan biri geçerli değildi (189 − 78 − 1). Bu dosyada bunların hiçbiri sayılmamıştır. Denetim dosyasından alınan 110 vakanın dağılımı: 22 bot engeli, 14 zaman aşımı, 12 HTTP hatası ve 10 gezinme hatası — gözlemci, giriş akışına ulaşamadı, ancak bu sitelerin çoğu sıradan bir tarayıcıda normal şekilde açılıyor; 20'sinde açılış sayfasında Steam oturum açma kontrolü yoktu; 16'sı, bir ana bilgisayara çözümlenemeyen bir oturum açma akışına ulaştı; 11 alan adı DNS'de çözümlenmedi; 5'i onay duvarında takıldı. Aşağıdaki tablo, aynı 110 siteyi farklı şekilde sınıflandırmaktadır: DNS'de çözümlenemeyen 11 site, ayrı olarak şu şekilde listelenmiştir: Kaldırıldı · NXDOMAIN, ve uygun olmayan tek kayıt da diğerlerine katılır. Denetlenen 189 platformdan 11’ü, her iki çözümleyiciden de kesin bir NXDOMAIN sonucu alınarak kaldırıldı, 178 kişi görevde kaldı (platform-audit.json, platforms-removed.json). Defterin adlandırma kalıbına göre tahmin ettiği 137 kimlik doğrulama etki alanı, 2026-09-19’daki verilerden silindi — hiç gözlemlenmedikleri için, dolayısıyla hiçbir kanıt da bulunmamaktadır. Tahminlerden üçü, sağlanan OpenID URL’leriyle çelişti: buff.163.com, gamerpay.gg ve csgoluck.com, buffauthproxy.163.com, gamerpayredirect.io ve lucklogin.app tahminlerinin aksine doğrudan kimlik doğrulaması yapıyor. Kaldırılanlar, yayınlanan denetim dosyasında listelenmiştir.\n25, bir alt sınırdır, üst sınır değildir. Sorunları çözülen 78 platformdan 25’i ayrı bir etki alanı kullanmış, 53’ü ise kullanmamıştır. Bu orandan, çözülemeyen 110 platform hakkında herhangi bir varsayımda bulunulmamıştır ve bu dosyada bu orandan yola çıkılarak yapılan hiçbir tahmin yer almamaktadır. Her biri, bir kişinin siteyi açıp \"Steam ile giriş yap\" düğmesine basmasıyla çözülebilir: kimlik doğrulama ana bilgisayar adı, yüklenen Steam sayfasının URL'sinde yer almaktadır.\nBu bölümün amacı: Bağımsız bir gözlemcinin 189 platformu tespit edebilmesi için bir tarayıcıya ve bolca sabra ihtiyacı vardır; ancak 78 tanesini tespit edebilmiştir. Valve için bir veritabanı sorgusu gereklidir. “Steam ile giriş yap” seçeneğini kullanan her platform — hem tespit edilmiş hem de edilmemiş olanlar — şu bilgiyi gönderir: openid.realm her oturum açılışında Valve'ın kimlik doğrulama uç noktasına. Bu tablodaki boşluk, yazarların sistem dışında olmasından kaynaklanmaktadır. Valve için böyle bir boşluk yoktur.\nGözlemlenen vekil ana bilgisayar adları şurada yer almaktadır: auth-route-audit.json. RDAP (Verisign) / IP2WHOIS kaynaklı alan adı kayıt tarihleri. Bağlantı Filtreleme sonuçları: linkfilter-all-results.json.\nAnlaşılırlık için bir benzetme\n\nLisanslı bir taksi şirketine, düzenleyici kurumlar tarafından artık kayıtlı olduğu Main Street adresinden faaliyet gösteremeyeceği bildirildiğini düşünün. Şirket, Main Street’teki tabelasını kaldırır. Bu tabela kaldırma işlemi kayıt altına alınır. Ancak aynı şirket, farklı bir isim altında kayıtlı olan Side Street adresinde bir şube açar ve faaliyetlerine buradan devam eder. Düzenleyici kurumlar, her iki adresten kalkan tüm taksilerin kullandığı merkezi sevk sistemini işletiyor. Her yolculuk talebinde “Side Street’ten alınacak” ibaresi görünüyor. Düzenleyici kurumlar, Side Street’teki ruhsatı hiçbir zaman iptal etmiyor. Main Street tabelasının kaldırılması, uygulanan tek yaptırımdı. Taksi şirketi faaliyetlerini hiçbir zaman durdurmadı.\n\nA Bölümü — Teknik kayıt · Madde 3.1\nSteam'in içinde, Valve'un listesi tek listedir.\n\nSteam istemcisinde, oyun içi üst katmanında veya Big Picture modunda tıklanan bir bağlantı, kullanıcının tarayıcısında açılmaz. Bu bağlantı, Steam’in kendi gömülü tarayıcısında görüntülenir — burada, bir tarayıcının uygulayacağı uyarı katmanları mevcut değildir. Bağlantı Filtresi, birçok güvenlik önleminden sadece biri değildir. Aslında tüm güvenlik önlemlerinin tamamıdır.\n\nNormal bir tarayıcıdaÜç bağımsız katman\nGoogle Güvenli TaramaGoogle’ın kimlik avı ve kötü amaçlı yazılım listelerinde yer alan sunucular için, ziyaret edilen siteden bağımsız olarak sürekli güncellenen tam sayfa bir ara sayfa.\nAntivirüs tarayıcı eklentisiÇoğu tüketiciye yönelik uç nokta ürünü, hedefi üreticinin kendi itibar listesiyle karşılaştıran bir tarayıcı eklentisiyle birlikte sunulur.\nUç Nokta HTTPS DenetimiÜrün TLS denetimi gerçekleştirdiğinde, sayfa içeriği kullanıcıya ulaşmadan önce taranır.\nSteam istemcisinde, overlay ve Big PictureTek katman\nGoogle Güvenli TaramaMevcut değil. Bu kontrol, gömülü Chromium derlemelerinde sağlanmayan Google API anahtarlarını gerektirir; bu anahtarların bulunmadığı durumlarda, Chromium’un kendi tasarım belgelerinde, Güvenli Gezinme işleyicisinin istek zincirine hiçbir zaman eklenmediği belirtilmektedir.\nAntivirüs tarayıcı eklentisiYok. Steam'nin görüntüleyicisi kullanıcının tarayıcısı değildir ve kullanıcının tarayıcı profilinden hiçbir uzantıyı yüklemez; dolayısıyla sayfada hiçbir eklenti çalışmaz.\nUç Nokta HTTPS DenetimiÜrüne bağlıdır. Trafik, tanınan bir tarayıcı yerine kod imzalı bir Valve işlemi içinde son bulur ve bazı uç nokta ürünleri, imzalı uygulamaları TLS denetiminden muaf tutar.\nSteam Bağlantı FiltresiValve'un kendi engelleme listesi; bir bağlantı Steam ekosisteminden çıktığında bu listeye başvurulur. Yapılan tek kontrol budur — ve yukarıdaki tablo, bu bölümde belgelenen kimlik doğrulama sunucuları için bu kontrolün ne tür sonuçlar verdiğini göstermektedir.\nHer okuyucunun yapabileceği bir test; eğer başarısız olursa sonuç geçersiz olur\n\nGoogle’ın yayınladığı Güvenli Tarama test URL’lerinden birini açın (testsafebrowsing.appspot.com) Chrome’da: tam sayfa kırmızı bir ara sayfa görüntülenir. Aynı URL’yi bir Steam sohbet mesajından açtığınızda, sayfanın Steam istemcisinde veya üst katmanda görüntülenmesi durumunda: ara sayfa görüntülenmez. Steam'ün üretebileceği tek uyarı, kendi Bağlantı Filtresi sayfasıdır ve bu da yalnızca Valve'ın listesindeki ana bilgisayarlar için geçerlidir.\n\nValve'un kendi hata ödül programı rekoruBu tek katmanlı yapı daha önce de aşılmıştı — Valve’ın kendi albümünde\n\nEğer Bağlantı Filtresi, istemci içinde çalışan tek kontrol mekanizmasıysa, bu filtrenin kendi arıza durumları da önemsiz bir konu değildir. Valve’un HackerOne programına ilişkin iki rapor; her ikisi de kabul edildi, her ikisi de çözüldü ve her ikisi de tam olarak kamuoyuna açıklandı:\n\n#291750arşivlendi 2025-11-16 ↗Open Redirect · medium\nBağlantı filtresi korumasının atlanması\n\n19 Kasım 2017’de bildirildi, çözüldü, 9 Mayıs 2018’de açıklandı. Raporun kendi kavram kanıtı: ideografik nokta karakterinin ikame edilmesi 。 (%E3%80%82) ana bilgisayar adındaki nokta için — Engellemeyi aşmak mümkündür. Bu bölümün konusunu oluşturan ara içerik görünmedi.\n\n#1079561arşivlendi 2026-09-24 ↗Bilgi Açıklama · yüksek\nBig Picture web tarayıcısı, oturum açma çerezlerini sızdırıyor ve hassas bilgileri ifşa ediyor (hesap ele geçirilmesine yol açabilir)\n\n15 Ocak 2021 tarihinde bildirildi, çözüldü, 21 Eylül 2021 tarihinde açıklandı. Valve'un kendi ciddiyet derecesi yüksektir ve başlıkta sonuç belirtilmiştir. Yayınlanan kayıtta başlık, derecelendirme ve tarihler yer almaktadır; teknik açıklama yayınlanan veride bulunmadığından, buradan başka bir alıntı yapılmamıştır.\n\nYazarların yorumu; her iki raporda da yer alan bir bulgu değildir: İkisi de aynı kapının iki yanında yer alır. Bunlardan biri, hedef sayfa açılmadan önce uyarı mesajının görünmemesi; diğeri ise, bir sayfa açıldıktan sonra oturumun istemciden ayrılmasıdır. Çalınan bir oturumun ardından gelen süreç — bir uyarı mesajı olmadan anahtarın kaydedilmesi, gerçek işlemin iptal edilmesi, bir kopyanın klona gönderilmesi — şu belgede belirtilen şemadır: 5. Bölüm ...'ye 8. Bölüm. Her iki rapor da kapatılmıştır; ikisi de aktif bir güvenlik açığı olarak bildirilmemiştir. Bu raporların ortaya koyduğu bulgular daha dar kapsamlı olmakla birlikte yeterlidir: geriye kalan tek katmanın, Valve'un kendi kayıtlarına göre, daha önce aşılmış olduğu belgelenmiştir.\n\nKaynak: Her bir rapor için HackerOne bildirim kaydı; 2026-09-22 tarihinde alınmıştır — HackerOne tarafından yayınlanan numara, başlık, ekip, güvenlik açığı, ciddiyet derecesi, rapor ve bildirim tarihleri ile durum bilgileri. Alım kaydı: hackerone-reports.json. Burada herhangi bir ödül tutarı belirtilmemiştir; elde edilen ve kamuya açıklanan kayıtlarda da böyle bir tutar yer almamaktadır.\n\nSaha gözlemi · PhishDestroyNormalde bir kampanyayı sona erdiren tespitler, bu sefer kampanyayı sona erdirmedi\n\nKimlik avı sunucularının, yük taşıyarak trafiği çekmeye devam etmesini izledik 20 veya daha fazla satıcı tespiti. Web veya e-posta yoluyla iletildiğinde, bu durumdaki bir kampanya birkaç gün içinde son bulur — hem tarayıcı hem de antivirüs bu kararlar doğrultusunda harekete geçer. Steam içinde ise ikisi de harekete geçmez. Kararlar başından beri mevcuttu. İstemcide hiçbir şey bunu sorgulamadı.\n\nAntivirüs programı yüklü olan bir reşit olmayan kişi için bunun anlamı nedir?\n\nHiçbir uyarıyı görmezden gelmez ve hiçbir şeyi devre dışı bırakmaz. Steam içinde bir mesaj gelir — bedava bir bıçak, bir arkadaşının takımına oy — ve sayfa Steam içinde açılır. O hiçbir zaman tarayıcı açmaz, bu yüzden tarayıcı onu asla korumaz. Antivirüs programı çalışmaktadır ve o etki alanını zaten zararlı olarak değerlendirmiş olabilir; ancak buna hiç sorulmaz. Onu durdurabilecek her türlü uyarı zaten mevcut. Hiçbiri ona ulaşmıyor. O, Steam’dan hiç ayrılmadığını düşünüyor ve gerçekten de ayrılmadı.\n\nBu “bedava” teklifi, dolandırıcıların kendi icadı değildir — “bedava Valve” ürünleri, oyun ve kumar sitelerinin reklamlarında sıkça kullandığı bir yöntemdir; işte bu yüzden mesaj sıradan bir içerik gibi görünmektedir. Şikayetler: icra arşivi. Yaş ve çocuklara ilişkin veriler: 17. Bölüm.\n\nKaynaklar: Steam, web içeriğini Chromium Embedded Framework aracılığıyla steamwebhelper süreç — bkz. DARKNAVY'nin 27 Haziran 2024 tarihli teknik analizi ↗ ve Valve'un kendine ait Steam Müşteri Beta forumu ↗ arşivlendi 2025-08-04 ↗. Herhangi bir CEF sürümüne bağlı kalınmamaktadır: Yerleşik Chromium, Chrome değildir ve Chrome’un Google hizmetlerinin hiçbirini içermez. API anahtarları olmadan Güvenli Tarama: Chromium tasarım belgesi ↗ arşivlendi 2026-08-21 ↗, Chromium API anahtarları ↗ arşivlendi 2026-08-30 ↗ (“Chrome tarafından kullanılan Google API’larının çoğu Google’a özgüdür ve türetilmiş ürünlerde kullanılmak üzere tasarlanmamıştır”) ve diğer anahtarsız derlemelerde de aynı sonuç — Homebrew fıçısı #193814 ↗. Test URL'leri: testsafebrowsing.appspot.com ↗.\n\nİki farklı saat\nAlan adının yaşı.Gözlemin tarihi.\n\nKayıt oluşturma tarihi, bir alan adının ne zaman kaydedildiğini belirler. Tarih içeren bir OpenID kaydı ise o kayıttaki geri dönüş ana bilgisayarını belirler. İlki, ikincisinden önceki yılları kapsayamaz.\n\nTam kayıt, ayrı bir kayıt edilebilir alan adını, bir sitenin kendi alt alan adını ve doğrudan bir yolu birbirinden ayırır. Her satır, kaynağına ve DNS adresindeki sonuca bağlantı sağlar.\n\nAlan adı kaydını inceleyin →· Kayıt tarihlerini indir ↗· Gözlemi tekrarlayın ↗\n\nA Bölümü — Teknik kayıt · 4. Bölüm\nBir uç nokta kapatıldı. Genel izleme bir anahtarını kaybetti.\nBağlam ve kaynak sınırlamaları\n\nSteam güncellemesi, ürün Varlık Kimliklerinin kamuya açık görünürlüğünü ortadan kaldıran ve API envanter erişimini kısıtlayan değişiklikleri içeriyordu. Bunun sonucu: kamuya açık verilerden belirli bir ürünü orijinal Varlık Kimliği ile takip etmek imkânsız hale geldi. Aşağıda, daha önce neyin mümkün olduğu, sonrasında neyin mümkün olmaktan çıktığı ve mülkünün nereye gittiğini kanıtlamaya çalışan bir mağdurun bunun için ne kadar bedel ödediği anlatılmaktadır. CSFloat'un mühendislik hesabına göre tarih 2017'dir; Valve'ya ait herhangi bir değişiklik günlüğü bulunamamıştır. Bu olay dizisi — Temmuz 2016’daki kumar açıklaması üzerinden yaklaşık bir yıl sonra — bir bulgu değil, soruşturmanın odak noktasıdır. Öğe kayıtları hâlâ Valve’in sistemlerinde bulunmaktadır; dış araştırmacılar orijinal kimlik zincirine erişimlerini kaybetmişken, float, seed ve paint tanımlayıcıları yalnızca kısmi eşleştirmeye izin vermektedir.\n\nValve kuralı geçerlidir: Steam Destek ekibi, hesabınızdan çıkan öğeleri geri yüklemez ve ne olduğunu kanıtlama yükümlülüğü size aittir. Kayıt: 2017 yılında Valve, orijinal öğe kimliklerini taşıyan uç noktayı kapattı. Bundan önce, herkes çalınan bir görünümü kurbanın hesabından bir pazar yeri botuna kadar takip edebiliyordu. Bundan sonra ise, Valve dışındaki hiç kimse bunu yapamıyor. Mağdurdan istenen kanıt, kapatılmış olan kanıttır — ve o hâlâ var, Valve’nin içinde.\n\nElektrik Kesintisi Öncesi Dönem\n\nTarihsel olarak, Steam üzerinde oluşturulan her sanal öğe, küresel olarak benzersiz ve değiştirilemez bir Varlık Kimliği. Üçüncü taraf OSINT veritabanları bu kimlikleri indeksleyebilir. Bir kullanıcının bir öğesi ele geçirilmişse, soruşturmacılar söz konusu varlığın, ele geçiren kişinin ara hesabından bir pazar yeri veya kumar sitesinin depolama hesaplarına aktarılırken izlediği yolu takip edebilir.\n\nÖNCE: Herhangi bir kişi, kamuya açık verileri kullanarak, kurbanın hesabından ara hesaplar üzerinden bir pazar yerine veya kumarhane depolama botuna kadar bir öğenin izini sürebiliyordu.\nDeğişiklikten sonra\n\nCSFloat’un mühendislik hesabına göre, Valve 2017 yılında uç noktayı kapattı ve orijinal öğe kimlikleri üçüncü taraflarca erişilemez hale geldi. Değişikliğin nedenine ilişkin herhangi bir Valve açıklaması bulunamadı. Aynı dönemde, öğeleri büyük ölçekte hareket ettiren ticari bot hesaplarına karşı alınmış herhangi bir önlem de tespit edilemedi.\n\nSebebi ne olursa olsun, bu değişiklik halka açık izleme zincirini kopardı. Mağdurlar artık kamuya açık verilerden orijinal kimlik zincirini yeniden oluşturarak, çalınan belirli bir eşyanın belirli bir pazar yeri veya kumarhane aracılığıyla elden çıkarıldığını kanıtlayamazlar. Eşya kayıtları hâlâ Valve'nin sistemlerinde mevcuttur; ancak kamuya açık veriler üzerinden çalışan halk, araştırmacılar ve kolluk kuvvetleri bu kayıtlara erişemez.\n\nSONRA: Kamuya açık verilerden belirli bir öğeyi orijinal Varlık Kimliği ile takip etmek artık mümkün değildir. 2017’den sonra taşınan bir öğenin orijinal kimlikli izleme zinciri yalnızca Valve’un altyapısı içinde mevcuttur; bu tür bir kayıt kamuya açık olarak yayınlanmamıştır. Float, seed ve paint tanımlayıcıları yalnızca kısmi ve olasılıksal eşleşmelere izin vermektedir.\nIEconItems_730\nAL/IEconItems_730/GetPlayerItems/v1/\nİzlenebilir Yük (Yama Öncesi)\n\"id\": \"14892281934\",\n\"original_id\": \"11829910211\",\nDurum: Mağdur, bot hesapları arasında öğenin izini sürebilir.\nGizlenmiş Yük (Yama Sonrası)\nMevcut\n\"id\": \"HIDDEN_BY_PRIVACY_SETTINGS\",\n\"original_id\": \"NULL\",\nDurum: Dış taraflar, kamuya açık verilerden orijinal Varlık Kimliği'ni kullanarak artık öğenin izini süremez.\nKanıtlar üzerindeki etkisi: Değişikliğin ardından, mağdurun hesabından bir pazar yeri veya kumarhane botuna kadar belirli bir öğeyi orijinal Varlık Kimliği üzerinden takip etmek için gerekli olan kamuya açık veriler artık mevcut değildi. İç kayıtlar hâlâ Valve adresinde mevcuttur; kamuya açık verilerle çalışan bir mağdur, araştırmacı veya soruşturmacı, orijinal kimlik zincirini yeniden oluşturamaz (float, seed ve paint tanımlayıcıları yalnızca kısmi eşleşmeye izin verir).\n\nKaynak: CSFloat mühendislik raporunda, 2017 yılında kapanan IEconItems_730/GetPlayerItems — blog.csfloat.com/how-floatdb-tracks-items (arşivlendi 2026-09-21) · Gösterilen yükler, alanın şeklini gösteren örneklerdir; yakalanan yanıtlar değildir · Bu kapatma için Valve değişiklik günlüğü bulunamamıştır.\n\nA Bölümü — Teknik kayıt · 5. Bölüm\nTek oturum. Kullanıcının gördüğünden daha fazla erişim.\nBağlam ve kaynak sınırlamaları\n\nValve'ın API anahtarı mimarisi, 2023'teki değişikliklerden önceki haliyle, temel sektör standartlarından sapıyordu (OWASP ASVS, NIST SP 800-63B) ve kanıt arşivinde saklanan otomatik envanter hırsızlığı şikayetlerinde açıklanan mekanizmadır (Bölüm 6–8).\n\nValve kuralı uygulandı: Hesap sahibi anahtarı oluşturdu, şartları kabul etti ve zararı üstleniyor — arşivlenmiş red kararlarındaki cevap budur. Kayıt: Aralık 2023’e kadar, çalınan bir oturum çerezi tek başına bu anahtarı kaydedebiliyordu. Şifre yoktu. Steam Guard yoktu. Hesabın sahibi olan kişiye herhangi bir bildirimde bulunulmadı. Kullanıcı anahtarı kendisi oluşturmamıştı, anahtarı görememişti, ancak kendisine oluşturduğu söylendi. Mobil onay, 2023-12-04 tarihinde eklendi — 2016 tarihli açıklamadan yaklaşık yedi yıl sonra ve arşivin sakladığı dolandırıcılık panellerinden yaklaşık altı yıl sonra. Bu yıllara ait ödemeler Valve tarafından yapılmadı. Bu ödemeler, bu süre zarfında boşaltılan hesaplardan karşılandı; bunların bir kısmı da çocuklara aitti.\n\nOWASP ASVS 2.8 / NIST SP 800-63BÖNEM DERECESİ: KRİTİK\n1. Yetersiz iki aşamalı kimlik doğrulama\n\nSteam, yalnızca bir oturum çerezi kullanılarak yüksek ayrıcalıklı ve uzun ömürlü API anahtarlarının oluşturulmasına izin veriyordu. Geliştirici API anahtarını oluştururken veya değiştirirken 2FA (Steam Guard) veya aşamalı kimlik doğrulama talebi gerekmediğinden, Steam Guard mobil onayı — Steam'ün sunduğu tek ikinci faktör — bu adımı korumadı. (2016 yılında Valve’nin kendi izleme sisteminde donanım tabanlı bir ikinci faktör talep edilmişti ve bu sorun hâlâ çözülmemiştir: Ek D, GH-01.)\n\nDurum: 2023'ten önce yama uygulanmamıştı. Çalınmış bir çerez içeren bir komut dosyasının, kullanıcı müdahalesi olmaksızın bir anahtar kaydetmesine olanak tanıyordu.\nOWASP A01:2021 / En Düşük Ayrıcalık İlkesiÖNEM DERECESİ: KRİTİK\n2. En Az Ayrıcalık İlkesi’nin Uygulanmaması\n\nSteam Web API’sinde rol tabanlı yetkilendirme kapsamları bulunmuyordu. “Salt okunur” envanter durumu için verilen bir geliştirici API anahtarı, mevcut işlemleri değiştirme, yeni işlemler başlatma, webhook’ları kaydetme ve geçerli bekleyen takasları reddetme yetkisi de dahil olmak üzere tam “yazma” izinlerine sahipti.\n\nDurum: sistemik tasarım hatası. Tek bir anahtar, hesabın envanteri ve işlemleri üzerinde tam okuma/yazma yetkisi sağlar.\nOWASP A07:2021 / OturumlarÖNEM DERECESİ: YÜKSEK\n3. Oturum Yönetimi Sorunları\n\nKullanıcılar, sunucu barındırma IP aralıklarından kaynaklanan ele geçirilmiş web oturumlarının devam ettiğini bildirmiştir. Coğrafi anormallikler ve şifre değişikliği durumunda oturumları sonlandırmak standart uygulamadır; arşivde toplanan kullanıcı raporları, şifre değişikliğinden sonra da aktif kalan oturumları açıklamaktadır.\n\nDurum: Bildirilen sorun (arşivdeki kullanıcı şikayetleri). Oturumlar, yeniden kimlik doğrulaması yapılmadan API anahtarları oluşturabiliyordu.\nEtki alanı düzeyinde engelleme teknik olarak mümkündüUYGULAMA OLASILIĞI\n4. Kimlik Doğrulama Sunucularının Etki Alanı Düzeyinde Engellenmesi Teknik Olarak Mümkündü\n\nValve halihazırda bir etki alanı listesi (Link Filter) işletiyor ve kendi OpenID isteklerinde her bir kimlik doğrulama ana bilgisayar adını zaten alıyor. Bu iki mekanizma, dışarıdan bakıldığında hiçbir şekilde birbirine bağlı değildir: 2026-09-22 itibarıyla, 26 çiftte ana etki alanı filtrede yer alırken, oturum açma bilgilerini taşıyan proxy filtrede yer almamaktaydı.\n\nBunları birbirine bağlamak basit bir mühendislik işidir: şunu okuyun openid.realm Her gelen isteğin ana bilgisayar adını alır, bunu bir listeyle karşılaştırır ve isteği reddeder veya işaretler. Sağdaki şemada bu tür bir yordamın yapısı gösterilmektedir. Yalnızca genel açılış sayfasını değil, kimlik doğrulama ana bilgisayarını reddetmek, bu platformların dayandığı “Steam ile giriş yap” adımını kesintiye uğratır.\n\nValve'in böyle bir kontrol yaptığını gösteren kamuya açık bir kanıt bulunmamaktadır. Steam Topluluk Pazarı’nın yaklaşık 15% tutarındaki toplam ücreti, Pazar içinde gerçekleştirilen satışlar için geçerlidir; bu platformların dışındaki işlemlerde bu ücret tahsil edilmez.\n\nblock_auth_hosts.pyİLLÜSTRASYON\n// Ana bilgisayar Steam’ın halihazırda aldığı verileri oku — tarama yapılmayacak\ndef on_openid_request(request):\nhost = parse_openid_realm(request)\neğer ev sahibi içinde engellenen_alan_adları:\nreddetmek (talep)\nNot: Sadece örnek amaçlı yazılmış sözde kod. Her iki kısım da halihazırda Valve'da mevcut — istek içinde kimlik doğrulama ana bilgisayar adı yer alıyor ve etki alanı listesi de Bağlantı Filtresi'dir. Bunların neden birbiriyle bağlantılı olmadığına dair kamuya açık bir açıklama bulunmamaktadır.\nBölüm 5.1 — Standartlar yayınlanmamamıştı\nValve her gün bu kurallara göre derleniyor. Ancak burada bu kurallara göre derlenemedi.\n\nSteam, App Store ve Google Play üzerinden dağıtım yapıyor, önde gelen kart ödeme sağlayıcıları aracılığıyla satış gerçekleştiriyor ve diğer tüm büyük platformlar gibi üçüncü taraf API’lerini kullanıyor. Bu ilişkilerin her biri, Valve’ın faaliyetlerini sürdürebilmesi için yerine getirmesi gereken, yayınlanmış ve tarih belirtilmiş bir güvenlik şartı içeriyor. Bu gerekliliklerin tarihlerini, Steam'nin kendi Web API'sinin aynı korumaları elde ettiği tarihlerle karşılaştırın. Aşağıda yer alan hiçbir şey özel bir standart, kurum içi not ya da ticari sır değildir: her satır, yayın tarihi belirtilmiş halka açık bir belgedir.\n\nYayınlanmış harici güvenlik gereklilikleri ve bunların tarihleri, Steam Web API’sinin eşdeğer kontrolü elde ettiği tarihle karşılaştırılarak belirtilmiştir\nYayımlanan standart ve yürürlüğe girdiği tarih\tAynı soruya ilişkin Steam Web API’si\nKapsamlı yetkiOAuth 2.0 — RFC 6749, Ekim 2012. 3.3. Bölümünde şunlar tanımlanmaktadır: scope Böylece bir istemci yalnızca talep ettiği erişim hakkını alır. O zamandan beri bu, tüm büyük platform API’lerinin varsayılan ayarı olmuştur.\tGranüler kapsamlar şu tarihte kullanıma sunuldu: 16 Ocak 2026.Bundan önce, tek bir Steam Web API anahtarı, hangi amaçla verilmiş olursa olsun, hesapta gerçekleştirilen tüm işlemler üzerinde tam okuma ve yazma yetkisine sahipti. On üç yıl ve üç ay kontrolü tanımlayan spesifikasyonun ardından.\nBir anahtar, bir yetki değildirGoogle'ın kendi Cloud belgeleri: Standart bir API anahtarı, bir asılın kimliğini doğrulamaz, ve kaynakları oluşturan veya yöneten API’ler için, Üretim ortamında yetkilendirme anahtarlarını kullanmayın.\tSteam Web API anahtarı tam da buydu.Bir hesaba tahsis edilen, tek başına envanteri okumaya, bekleyen bir işlemi iptal etmeye ve yeni bir işlem göndermeye yeten bir taşıyıcı dize. Kullanım anında hiçbir ana kullanıcı kimliği doğrulanmamıştır.\nAyrıcalıklı erişimde çok faktörlü kimlik doğrulamaPCI DSS 3.2, 8.3 numaralı gereklilik — şu tarihten itibaren zorunludur 1 Şubat 2018 kart sahibi veri ortamına yönelik tüm konsol dışı yönetim işlemleri ve tüm uzaktan erişimler için. Apple daha sonra, her Geliştirici Programı hesap sahibinden 27 Şubat 2019: Bir geliştirici programında “Hesap Sahibi” rolüne sahip geliştiricilerin oturum açabilmeleri için iki faktörlü kimlik doğrulamayı etkinleştirmeleri gerekecektir.\tBir API anahtarı oluşturmak için ikinci bir faktör gerekiyordu: 4 Aralık 2023.O zamana kadar, çalınan bir oturum çerezi yeterliydi; hesap sahibinin telefonunda herhangi bir uyarı çıkmıyordu ve sonrasında da herhangi bir bildirim gelmiyordu. Dört yıl ve dokuz ay Apple, geliştirici portalına giriş yapmak için bile ikinci bir doğrulama faktörünün kullanılmasını zorunlu kıldıktan sonra.\nKimlik bilgilerinin yaşam döngüsü ve iptal edilmesiTwitch, her üçüncü taraf uygulamadan şunları talep eder: Uygulamanız, başlatıldığında ve bundan sonra her saat başı OAuth jetonunu doğrulamalıdır, ve bu şartları karşılamayan uygulamaları denetlediğini belirtmektedir. Eski v5 API’si, 28 Şubat 2022 yayınlanmış bir programa göre.\tAnahtar yaşam döngüsüyle ilgili yayınlanmış bir kayıt bulunmamaktadır.2023’teki değişiklik, oluşturma uç noktasını korudu. Bu değişiklikle ilgili hiçbir Valve ifadesi bulunmamakta ve halihazırda kayıtlı anahtarları ele almamaktadır; ayrıca bu değişikliğe eşlik eden herhangi bir değişiklik günlüğü de bulunmamaktadır. Bu değişiklikten önce oluşturulan anahtarların geçersiz kılınıp kılınmadığı, kamuya açık verilerden tespit edilememektedir — bu ise, bir veri sahibinin, yıllar önce kendi hesabında oluşturulan bir anahtarın hâlâ aktif olup olmadığını öğrenmek için yanıtlanması gereken sorudur.\nMimari Referans // Token Architecture\nGitHub'daki Ayrıntılı Kapsamlar ile Valve Steam Web API'si Karşılaştırması\n\nValve geliştirici, GitHub'da her gün ayrıntılı düzeyde en az ayrıcalıklı erişim jetonları kullanarak açık kaynaklı yazılımları yönetiyor. Bunu, 130 milyon Steam oyuncuya verilen tek parça anahtarla karşılaştırın.\n\nGitHub Ayrıntılı Jeton\nGitHub'da Valve tarafından kullanılıyor\n\nKapsamlı yalıtım ve zorunlu yaşam döngüsü uygulamasına sahip, ince taneli token.\n\nDepoya Erişim:Yalnızca seçili depolar (1 depo)\nİzinleri Belirleme:Salt okunur [✓]\nKod ve Sırlar:Erişim yok [✕]\nSon kullanma tarihi:30 Gün (Zorunlu TTL)\nDenetim Günlüğü:IP, Kullanıcı Aracısı ve Zaman Damgası\nGüvenlik Durumu: En düşük ayrıcalıklı erişim belirteci, zararı tek bir salt okunur kaynağa sınırlar.\n!Valve Steam Web API Anahtarı\n130 milyon kullanıcıya sunuldu\n\n“Ya hepsi ya hiç” ilkesine dayalı ticaret ve envanter yetkisini içeren, 32 karakterlik tek bir ana dize.\n\nHesap Erişimi:TAM HESAP (Monolitik)\nTicaret Yönetimi:Oku, İptal Et, Reddet [!]\nAyrıntılı Kapsamlar:YOK (2026'da geldi, 13 yıl gecikmeli)\nSon kullanma tarihi:ASLA (Süresiz olarak geçerlidir)\nDenetim Günlüğü:YOK (Kullanıcının IP geçmişi yok)\nGüvenlik açığı: Çalınan anahtar, gönderilen tüm ticaret tekliflerinin fark edilmeden ele geçirilmesine olanak tanır.\nTek yönde uygulanan standart\n\nBir tedarikçinin — örneğin bir bulut sağlayıcısı, bir ödeme işleyicisi veya bir CDN — ikinci faktör olmadan bir kimlik bilgisi uç noktasını açık bıraktığını ve aylar sonra Valve’in kendi kurumsal verilerinin bu uç noktada oluşturulan bir anahtar aracılığıyla sızdığını varsayalım. Valve, hatanın bağlantıya tıklayan kişide olduğunu kabul eder mi? Bu dosyada saklanan arşivlenmiş ret kararları, kullanıcı için tam tersi soruyu yanıtlıyor: benimsenen tutum, anahtarı hesap sahibinin oluşturduğu ve kaybın sorumluluğunun da ona ait olduğu yönündedir. Aynı mimari, bir yandan satıcının başarısızlığı, diğer yandan ise kullanıcının sorumluluğu olarak tanımlanmaktadır. Bunun hangisi olduğu teknik bir soru değildir ve bu soruşturma ile çözülebilecek bir konu da değildir — bu, bir mahkeme veya denetim makamının vereceği bir karardır.\n\nBir örnek, kanıt değil — standart ters yönde yorumlanıyor\nHesap sahibine herhangi bir uyarı göstermeden, üçüncü taraf bir komut dosyasının yalnızca bir tarayıcı çerezinden tam yetkili bir işlem kimlik bilgisi oluşturmasına izin veren bir ödeme işleyicisi.\nTokenlarının basıldığı güvenlik açığını kapatan ve halihazırda basılmış tokenlar hakkında hiçbir bilgi yayınlamayan bir kimlik sağlayıcı.\nTartışmalı bir havaleye, kullanılan kimlik bilgilerinin müşterinin kendi hesabına kayıtlı olduğu gerekçesiyle yanıt veren ve ilgili talebi kapatan bir banka.\n\nBunların hiçbiri, adı geçen herhangi bir şirketle ilgili bir bulgu olarak sunulmamaktadır. Bunlar, aynı tasarım kararları olup, denetim makamının tepkisinin ayrıntılı bir şekilde belgelendiği bir ortama aktarılmıştır — işte düzenleyici kurumdan yapması istenen karşılaştırma da budur.\n\nKayıtlardan anlaşıldığı üzere: Steam Web API’sinde bulunmayan denetimler, herkese açıktı, güncelliğini yitirmişti ve bazı durumlarda Valve’ın kendi ürünlerini sevk etmeye devam edebilmesi için yerine getirmesi gereken koşullar niteliğindeydi. Her bir standart ile eşdeğer Steam değişikliği arasındaki süre ölçülebilir olup, yukarıda belirtilmiştir. Ancak bunun nedenini açıklamıyor. Bu aralıkların hiçbirine ilişkin Valve gerekçe açıklaması bulunamamıştır ve burada da herhangi bir gerekçe varsayılmamaktadır; söz konusu kayıt Valve içinde yer almaktadır ve yayınlanmamıştır.\n\nKaynaklar (her biri kamuya açık bir belgedir): OAuth 2.0 — RFC 6749, Ekim 2012 ↗ · Google Cloud — API anahtarları belgeleri ↗ · PCI DSS 3.2, 8.3 numaralı gereklilik — PCI SSC kaynak kılavuzu ↗ · Apple — Hesap Sahipleri İçin Yakında Yürürlüğe Girecek İki Aşamalı Kimlik Doğrulama Zorunluluğu, 20 Şubat 2019 ↗ arşivlendi 2025-05-06 ↗ · Twitch — token doğrulama şartı ↗ ve v5 kapatma bildirimi ↗ arşivlendi 2025-01-27 ↗. Steam'nin kendi tarihleri, bu bölümdeki güncelleme kaydında yer alan tarihlerdir; 2023 ve 2026 girişleri ise Valve'in değişiklik günlüğü olmadan yayınladığı sürümlerdir. Erişim tarihi: 2026-09-22.\n\nValve'nin kendi güncelleme kaydı — tarihli, kamuya açık kaynaklardan\nTarih\tValve değişiklik\tDuyuruldu mu?\tNe kapandı?\tGecikme: mekanizma genel → düzeltildi\tKaynak\n2026-09-01\tŞüpheli Sohbetlerin Otomatik Olarak İşaretlenmesi\tEvet\tGrup sohbetlerindeki tehlikeli bağlantılar / kalıplar\t—\thaberler ↗\n2026-01-16\tSteamworks Web API’sinin ayrıntılı kapsamları\tEvet\tGeliştirici anahtarları için en düşük ayrıcalıklı kapsamlar\t—\tduyuru ↗\n2025-07-15\tCS2 Ticaret Koruması ve geri alma penceresi\tEvet\tHiçbir şey. Bu, sorunun kök nedenini ortadan kaldıran bir güvenlik düzeltmesi değildir. Destek ekibinin hesap kurtarma erişimi etkilenmemiştir. İşlemin iptal edilmesi, otomatik olarak 30 günlük işlem kilidi uygulamasına yol açar (Skinvault ↗), nakit ticareti kaynaklı şok ise piyasa değerinde $104M (-25%) tutarında bir 24 saatlik düşüşe neden oldu (CSMarketCap ↗). 2026 yılında, zamanlayıcılar ürün bazında hale geldi (Skin.land ↗).\t—\tSık Sorulan Sorular ↗\n2025-05-14\tHesap Güvenliği Duyurusu\tEvet\tHırsızlık / oturum ele geçirme kılavuzu\t—\tduyuru ↗\n2024-10-02\tCS2 “The Armory” 7 günlük bekletme süresi\tEvet\tArmory eşyaları için takas/pazar bekleme süresi\t—\tduyuru ↗\n2024-09-18\tYeni cihazda oturum açma işlemine ilişkin kısıtlama\tEvet\tYeni cihazlarda 2–7 günlük ticaret kilidi\t—\tSık Sorulan Sorular ↗\n2024-02-14\tProfil adı ve avatar değişikliği askıya alındı\tEvet\tAdın değiştirilmesinden sonra işlemlerde 2–4 saatlik bekleme süresi\t—\tgönderi ↗\n2023-12-04\tAPI anahtarları için mobil onay\tDeğişiklik günlüğü yok\tSadece çerezlere dayalı sessiz anahtar kaydı\t2017 dönemine ait panellerden yaklaşık 6 yıl sonra\tgeliştirici sayfası ↗\n2023-10-24\tOyun sürüm yayınları için SMS tabanlı çok faktörlü kimlik doğrulama (MFA)\tEvet\tSteamworks sürüm yayınlama\t—\tduyuru ↗\n2023-07-12\tÖzel biyografi içeriği uyarısı\tEvet\tBiyografilerdeki kimlik avı bağlantıları\t—\tforum ↗\n2023-01-25\tProfil {LİNK KALDIRILDI} ve bekleme süresi\tEvet\tProfil metnindeki bağlantılar\t—\tSık Sorulan Sorular ↗\n2022-10-24\tGiriş sisteminin yenilenmesi ve çerezlerin kısaltılması\tDeğişiklik günlüğü yok\tSınırsız sayıda ele geçirilmiş oturum\t— (IAuthenticationService jeton taşıma işlemi)\thaberler ↗\n2022-10-12\tMobil Uygulama 3.0 QR koduyla giriş\tEvet\tOturum yetki kaldırma paneli\t—\thaberler ↗\n2022-05-10\tTicaret iptali son noktaları kaldırıldı\tDeğişiklik günlüğü yok\tTeklif değişimi (iptal ve yeniden gönderme)\t2017 dönemine ait panellerden yaklaşık 5 yıl sonra\t325. sayı ↗\n2020-05-25\tDota 2 7 günlük takas kilidi\tEvet\tHızlı ürün alım satımı\t—\tblog ↗\n2018-03-29\tCS:GO 7 günlük takas kilidi\tEvet\tAnında bot aklama\tTemmuz 2016 tarihli açıklamanın üzerinden yaklaşık 20 ay sonra\tblog ↗ arşivlendi 2025-02-26 ↗\nKaynaklar: tarih belirtildiği üzere, bağlantılı Valve gönderileri, yardım sayfaları ve GitHub sorunları. Değişiklik günlüğü olmadan yayınlanan üç önemli düzeltme (2022-05, 2022-10, 2023-12), Valve tarafından duyurulmamış, kullanıcılar tarafından tespit edilmiştir — bu asimetri, uygulama kaydının bir parçasıdır. Gecikmeler, yalnızca dosyanın kendi tarihlendirmelerinin (Temmuz 2016 açıklaması; 2017 dönemi dolandırıcılık panelleri) başlangıç noktasını sağladığı durumlarda hesaplanmıştır; \"—\" işareti, burada böyle bir başlangıç noktasının belirlenemediği anlamına gelir.\nA Bölümü — Teknik kayıt · 6. Bölüm\nEtkileşimli Güvenlik Açığı Sömürme ve Kontrol Ele Geçirme Simülatörü\nBağlam ve kaynak sınırlamaları\n\nOltalama mesajından sunucu tarafındaki anahtar kaydına ve işlem değiş tokuşuna kadar olan sürecin yeniden canlandırılması. 2023 yılından önce, bir hesapta kayıtlı bir Web API anahtarı, hesabın envanterini okuyabilir, beklemede olan bir işlem teklifini iptal edebilir ve yeni bir teklif oluşturabilirdi; bu işlemlerin hiçbirinde hesap sahibine işlem onay ekranı gösterilmiyordu. Bu durum, en az ayrıcalık ilkesinin (OWASP A01:2021) ihlali anlamına gelir. Bu simülasyondaki zamanlamalar örnek niteliğindedir ve mevcut platformun gerçek zamanlı ölçümleri değildir.\n\nYeniden canlandırılan ele geçirme sürecini adım adım inceleyin. Her aşamada, hesap sahibinin gördükleri ve bunun yanında Steam numarasının aynı anda aldığı çağrı gösterilmektedir. Bu aramaların her biri doğru bir şekilde kimlik doğrulamasından geçmiştir. Süreçteki hiçbir adımın başarısız olması için Steam'nin kimlik doğrulamasına gerek yoktur — bunun için, Steam'nin verdiği anahtarın herhangi bir kapsam içermemesi gerekir (OWASP A01:2021).\n\nOyuncunun gördükleri. Arkasında neler değişiyor.ADIM ADIM SIMÜLATÖR\nAdım 5 / 5\n\nSaldırı Tamamlandı. Mağdur, asıl işlemin mobil cihaz üzerinden bildirim gelmesini beklerken, yerine geçen işlemi onaylar. Bu, “En Düşük Ayrıcalık” ilkesinin (OWASP A01:2021) uygulanmamasının, saniyenin altında bir sürede otomatik varlık ele geçirilmesine nasıl yol açtığını gösteren entegre bir adli inceleme kılavuzudur.\n\n01 / SOHBET YEMİBir arkadaşım oy vermemi istiyorMağdur, içinde bir bağlantı bulunan bir mesaj alır.\n02 / GİRİŞBir benzerlik portalıMağdur, oturum açma bilgilerini girer.\n03 / ERİŞİMSessiz Web API'si oluşturmaSaldırgan, bir geliştirici anahtarı kaydeder.\n04 / DEĞİŞİMMeşru ticaret takasıKlon botu, hedef alıcıyı kopyalar.\n05 / ONAYSahte ürün onaylandıMobil cihazdan yanlış teklif onaylandı.\nAynı adım, ağdan bakıldığında2023 öncesi modelin yeniden oluşturulması · örnek çağrı şekilleri\nMağdurOrijinal işlem için beklenen mobil uyarıyı onaylar.\nSaldırganKlon hesapta öğeleri alır.\nSteam görüyorKayıtlı bir cihazda hesap sahibi tarafından onaylanan bir para transferi.\nConfirmation genuine — made by the account holder\nRecipient the clone bot, not the intended counterparty\nThe confirmation is authentic. The offer it confirms is not the one the user initiated.\n\nGeride kalan kayıt: kullanıcının onayladığı bir işlem. Şikayet geldiğinde Steam Destek biriminin okuduğu kayıt budur ve arşivlenmiş şikayetlerin “kullanıcı hatası” gerekçesiyle kapatılmasının nedeni budur. Şikayetler icra arşivi.\n\nA Bölümü — Teknik kayıt · 7. Bölüm\nDizinin ardındaki uç noktalar.\nBağlam ve kaynak sınırlamaları\n\nBunlar, bildirilen ele geçirme komut dosyalarının, tarayıcı tarafındaki onay adımlarından geçmeden işlemleri ele geçirmek için kullandıkları Steam Web API uç noktalarıdır.\n\nBelgelenmiş dört uç nokta tüm işi hallediyor. Bunların hiçbiri bir güvenlik açığı değil, hiçbirinin istismar edilmesine gerek yok — geçerli bir anahtar bunları çağırıyor ve Steam yanıt veriyor. Saldırganın çalması gereken tek şey anahtardı.\n\nIEconService / GetTradeOffers / v1ANKET\n\nHesabın işlem tekliflerini izlemek için kullanılır. Komut dosyaları, ele geçirilmiş API anahtarıyla bu uç noktayı tekrar tekrar sorgular; bu uç nokta, yeni oluşturulan, beklemede olan veya değiştirilen işlem tekliflerinin ayrıntılarını döndürür. Sorgulama aralıkları burada ölçülmez.\n\nTehdit vektörü: Bekleyen ticaret tekliflerinin kimlik numaralarını ve alıcının profil bilgilerini gösterir.\nIEconService / CancelTradeOffer / v1ETKİLEŞİM\n\nKullanıcının geçerli işlem teklifini program yoluyla geçersiz kılmak için kullanılır. 2023 yılından önce, anahtarı koruyan hiçbir iki aşamalı kimlik doğrulama yöntemi bulunmadığından, otomatik bir sunucu, bir teklif tespit edilir edilmez, hesap sahibine herhangi bir uyarıda bulunmadan bu teklifi iptal edebiliyordu.\n\nTehdit vektörü: Hesap sahibi mobil onay işlemini tamamlamadan önce işlemi iptal eder.\nISteamUser / GetPlayerSummaries / v2RECON\n\nMeşru ticaret alıcısının profil adını, avatar resminin URL’sini ve seviyesini almak için sorgu gerçekleştirildi. Bu, komut dosyasının hazırlanan klon hesabı buna uygun şekilde düzenlemesini sağlar. Burada herhangi bir zaman ölçümü yapılmamaktadır.\n\nTehdit vektörü: Hedeflenen alıcının kimliğine bürünmek için gerekli verileri sağlar.\n/dev/ajaxregisterkeyYARATILIŞ\n\nSteam'in anahtarlar için kayıt uç noktası. Geçmişte, herhangi bir aktif tarayıcı çerez oturumu (`steamLoginSecure`), mobil cihazda Steam Guard onayı gerekmeksizin ve hesap sahibine herhangi bir bildirimde bulunulmaksızın bir anahtarı kaydedebiliyordu.\n\nTehdit vektörü: Hesap sahibinin haberi olmadan bir komut dosyası tarafından oluşturulan kalıcı bir kimlik bilgisi.\nA Bölümü — Teknik kayıt · 8. Bölüm · GDPR’nin 7. Maddesi\nİşaretlenmiş bir kutucuk. Kimin eylemi?\nBağlam ve kaynak sınırlamaları\n\nGeri ödeme talebinin reddedilmesinde, Steam Arşivde saklanan destek yanıtları, hesap sahibinin API anahtarını oluşturduğu ve ilgili kutucuğu işaretleyerek şartları kabul ettiği görüşünü savunmaktadır.\n\nDestek yanıtında, anahtarın hesap sahibine ait olduğu belirtilmektedir. Asıl soru, kaydın kimin tarafından oluşturulduğunun bu kayıttan anlaşılıp anlaşılmadığıdır.\n\nAncak gözlemlenen API anahtarı ele geçirme yönteminde, mağdur API anahtarı oluşturma sayfasını hiçbir zaman görmemiş veya bu sayfaya gitmemiştir. Onay alanı, çalınan oturum çerezi kullanılarak başlıksız bir POST isteği gerçekleştiren bir komut dosyası tarafından gönderilmektedir.\n\nGDPR’nin 7. maddesi ve 4. maddenin (11) numaralı fıkrası uyarınca, rıza, veri sahibinin iradesinin özgürce verilmiş, belirli, bilgilendirilmiş ve açık bir şekilde ifade edilmesi şeklinde olmalıdır. Yazarların görüşü, hesap sahibine herhangi bir sayfa gösterilmeden, çalınmış bir çerez kullanılarak kötü niyetli bir komut dosyası tarafından gönderilen şartları kabul etme alanının bu tanıma uymayacağı yönündedir. Bunun tanıma uyup uymadığına ise denetim makamı karar verecektir.\n\nAdli Yük Analizi: Anahtar Kaydı\nYAYIN https://steamcommunity.com/dev/ajaxregisterkey\n// İstek Yükü (ele geçirme komut dosyası aracılığıyla eklenmiş)\n{\n\"agreeToTerms\": \"kabul edildi\", <-- makine tarafından girilmiştir, insan müdahalesi yoktur\n\"etki alanı\": \"localhost\", ← doğrulanmamış — localhost dahil olmak üzere herhangi bir değer kabul edilir\n\"sessionid\": \"8f0d8ef763ab2140bf89de2a\"\n}\nDenetim makamına yöneltilen soru: Hesap sahibinin onay alanına hiçbir zaman tıklamamış olması durumunda, hesaba ilişkin olarak kaydedilen şartların kabulünün, 7. maddede belirtilen veri sahibinin iradesinin özgürce, açıkça, bilgilendirilmiş ve belirsizliğe yer bırakmayacak şekilde ifade edilmesi şartını karşılayıp karşılamadığı ve Steam Destek biriminin bir talebi reddetmek için buna dayanıp dayanamayacağı.\n\nKaynak: Kamuya açık uç noktadan ve delil arşivinde saklanan ele geçirme raporlarından yeniden oluşturulan anahtar kaydı isteğinin biçimi (2026-09-17'nin aranabilir derlemesi) · Gösterilen oturum tanımlayıcısı, yakalanan bir değer değil, bir yer tutucudur.\n\nAdli Otopsi · Ticaret İkame Vektörü\nValve \"Ticaret İkamesi\"ni Nasıl Sonunda Ortadan Kaldırdı — Ve Neden 7 Yıl Boyunca Geçici Çözümlere Başvurulmak Zorunda Kalındı\n\nNeredeyse on yıldır, \"API Anahtarı Takas Dolandırıcılığı\" (veya API MitM Dolandırıcılığı) Steam'de en kârlı hesap hırsızlığı modeliydi ve hiçbir şeyden haberi olmayan oyunculardan yüz milyonlarca dolarlık skin çaldı. Valve, güvenlik açığı bulunan API mimarisini düzelterek bu istismarı ortadan kaldırmadı; bunun yerine, Valve yedi yıl boyunca platform genelinde dört katmanlı engel oluşturarak topluluk içi ticaretin likiditesini felce uğrattı, ancak sorunun temel nedenini çözmedi.\n\n1. Taklitçi’nin Ölümü\nAvatar ve İsim Bekleme Süresi (Şubat 2024)\n\nBu saldırı, saniyenin altında bir sürede taklit yapılmasını gerektiriyordu: dolandırıcılık botu, gönderilen bir ticareti ele geçirdi ve alıcının avatarını/adını şu yolla topladı: ISteamUser, ve profili 200 ms içinde kopyaladı. 14 Şubat 2024 tarihinde, Valve sessizce zorunlu bir 2 ila 4 saatlik takas bekleme süresi (Hata 34) herhangi bir profil adı veya avatar değişikliğinin hemen ardından. Bir bot, artık işlem yapma imkânını kaybetmeden alıcıyı anında kopyalayamaz.\n\n2. Ekonomik Ölüm\n7 Günlük CS2 İşlem Yön Değişimi (Temmuz 2025)\n\nValve tek taraflı olarak uygulamaya konuldu Ticaret Trend Değişimleri Counter-Strike öğeleri için. Takas edilen her skin, yedi gün boyunca “Takas Korumalı” olarak işaretlenir. Mağdur bir değiştirme fark ederse, Steam Destek'te \"Takası İptal Et\" seçeneğine tıklar ve skin anında envanterine geri dönerken alıcı da dondurulur. 7 günlük takas kilidi, dolandırıcıların öğeyi para çekme sitesine aktarmasını engellediği için hırsızlık kârlı olmaktan çıkar.\n\n3. Sessiz Anahtarın Ölümü\nAPI için Zorunlu Mobil Bildirim (Aralık 2023)\n\nTarihsel olarak, çalınan bir oturum çerezi, kötü niyetli komut dosyalarının başsız bir arka plan POST isteği gerçekleştirmesine olanak sağlamıştı /dev/ajaxregisterkey mağdura haber vermeden. 4 Aralık 2023 tarihinde, Valve, bir Web API anahtarı oluşturmak için Steam Mobil Uygulamasında açık bir onay isteği zorunlu kıldı ve böylece arka planda sessizce anahtar tahsisi uygulamasını ortadan kaldırdı.\n\n4. Uygulama İçi Mobil Uyarılar\nHesap Süresi ve Ad Afişleri (2022–2024)\n\nValve, ticaret ortağının bilgilerini görüntülemek üzere mobil onay penceresini yeniledi Steam hesap süresi (açılış tarihi), Steam seviyesi ve açık bir sarı uyarı: \"Bu kullanıcı kısa süre önce profil adını değiştirmiştir\", dikkatli kurbanlar için görsel yanılsamayı bozarak.\n\nValve’nin Yama Çalışmasındaki Üç Kusur: Dolandırıcılar Neden Hedeflerini Değiştirdiler?\n1. Oyun Hariç Tutma Açığı (Dota 2 ve TF2)\n\nTrade Reversals, yalnızca Counter-Strike 2 için kullanıma sunuldu. Dota 2 ve Team Fortress 2 eşyaları tamamen korumasız durumda zanaatkarlık ve yuva takma işlemlerinin karmaşıklığı nedeniyle. Binlerce dolar değerindeki üst düzey eşyalar (Dragonclaw Hooks, Golden Baby Roshans, Unusual TF2 burning flames) için iade süresi hiç yoktur. Dolandırıcılar, otomatik API dinleme işlemlerini Dota 2 ve TF2 tüccarlarına yönlendirdiler; burada Steam Destek ekibi, 2016 tarihli “eşya geri verme yok” politikasını sıkı bir şekilde uygulamaktadır.\n\n2. “Zombie Key” Rezervuarı (Süre Dolumu Yok)\n\nValve, mobil push 2FA özelliğini ekleyerek yeni 2023 yılının Aralık ayında anahtarlar, Valve Mevcut eski API anahtarları hiçbir zaman iptal edilmedi, süresi dolmadı veya silinmedi. Anahtar oluşturmuş (ya da Aralık 2023’ten önce kimlik avı/kötü amaçlı yazılımlar tarafından fark edilmeden anahtarları oluşturulmuş) milyonlarca aktif hesap, hâlâ şu bilgilerin yer aldığı aktif kimlik bilgilerini barındırmaktadır: sıfır geçerlilik süresi (TTL yok) ve sıfır hareketsizlik zaman aşımı. Saldırganlar, bu kalıcı anahtarların bulunduğu devasa geçmiş veritabanlarını tutmakta ve sorgulamaya devam etmektedir IEconService rahat.\n\n3. Mağdur Cezası: 30 Günlük İşlem Engellemesi\n\nCS2’de bile, Valve dolandırılan oyuncuyu cezalandırır: Steam Destek bölümünde “Ticareti İptal Et” seçeneğine tıklamak otomatik olarak bir Mağdurun hesabına uygulanan 30 günlük zorunlu işlem ve Topluluk Pazarı yasağı. Valve, “anlamsız” işlem iptallerine karşı caydırıcı bir önlem olarak kullanıcıyı bir ay süreyle platformdan uzaklaştırma cezasına çarptırır; böylece mağdurların düşük değerli ve likit varlıklarla ilgili işlemleri iptal etmesini engeller.\n\nTemel Düzenleme Skandalı: Yedi Yıllık Çözüm Yolları ve Tek Bir API Kapsamı\n\nValve, sektör standardı bir çözümü uygulamak yerine neden yedi yılını ticaret tutma mekanizmaları, hesap bekleme süreleri ve geri alınabilir ticaret kilitleri icat ederek geçirdi — bu da tüm oyun ekonomisini altüst etti ve piyasa değerinden $104M'yi sildi?\n\n16 Ocak 2026 tarihinde Valve'un Steamworks üzerinden yaptığı resmi duyuruda da görüldüğü üzere (Duyuru #493839547938902179 ↗), Valve zaten inşa edilmiş Ayrıntılı İzin Grupları (Genel, Mikro Ödemeler, Ekonomi, Satış Verileri) ve IP Beyaz Listeleme kurumsal Yayıncı Anahtarları için. Valve, bu teknik çözümü yıllardır elinde bulunduruyordu. Kullanıcıya yönelik tek bir onay kutusu—\"Bu Web API anahtarının IEconService'e (Ticaret Yönetimi) erişmesini engelle\" ya da bir ev IP beyaz listesi — 2018’de ticari ikame dolandırıcılığını, hiçbir ekonomik yan etki yaratmadan ortadan kaldırmış olacaktı. Valve, kurumsal ortakları için tasarladığı korumayı sıradan oyunculara sağlamayı reddetti.\n\nB Bölümü — Kurallar ve uygulama kaydı · 9. Bölüm\nOnların kurallar kitabı. Kayıtlı platformlar.\nBağlam ve kaynak sınırlamaları\n\nBu defter, Steam Abone Sözleşmesi (SSA) ve Steam Çevrimiçi Davranış Kuralları (SOC) aktif, büyük ölçekli ticari kuruluşlara doğrudan yönelik kılavuzlar.\n\nKural: ticari kullanım yasak, kumar yasak, bot kullanımı yasak — ve Steam Destek ekibi, mağdurun eşyalarını iade etmeyi reddederken bu hükümlere atıfta bulunur. Kayıt: Aynı hükümler, ilk bakışta, bu kayıt defterindeki ticari platformları kapsamaktadır; bu platformlar Steam kimlik, Steam bot ve Steam transfer üzerinden çalışmaktadır. Bu hüküm, derileri kaybeden kişiye karşı uygulanır; yayınlanmış hiçbir kayıtta belirtildiği üzere, bunları nakleden işletmelere karşı uygulanmaz.\n\nArşivlenmiş şikayetlerde, Steam Destek birim şu hususu öne sürmektedir: \"Ticari Amaçlı Kullanım Yasaktır\" ve \"Otomasyon/Bot Yok\" API anahtarı dolandırıcılığı mağdurlarına eşyaları iade etmeyi reddederken uygulanan hükümler. Aynı hükümler, bu dosyada kayıtlı, Steam OpenID aracılığıyla kimlik doğrulaması yapan ve eşyaları otomatik Steam hesaplar üzerinden aktaran ticari platformlar için de görünüşte geçerlidir. Burada piyasa genelinde bir gelir rakamı tahmin edilmemektedir (aşağıdaki yaptırım istatistiklerine bakınız). Kayıtlar, arşivlenmiş vakalarda bireysel hesaplara uygulanan kuralları göstermektedir; platformlar için operatör bazında yayınlanmış bir yaptırım kaydı bulunmamaktadır. Bu bölümde, işte bu asimetri ele alınmaktadır.\n\nTemel soru / seçici uygulamaKurallar → Ölçek → Hesap Verebilirlik\nTek bir kural kitabı. Eşitsiz uygulama.\n\nKayıtlarda, ticari hizmetlerin Steam kimliklerini, envanterlerini, botlarını ve transferlerini işletme altyapısı olarak kullandığı görülmektedir. SSA, izinsiz ticari kullanım ve otomasyonu yasaklamaktadır. Arşivlenmiş şikayetler, bu kuralın bireysel hesaplara uygulandığını gösterirken, kamuya açık kayıtlarda burada belgelenen platformlar için operatör bazında benzer bir hesap bulunmamaktadır. Her birine ilişkin kuralı, kanıtları ve yaptırım kararını yayınlayın.\n\n189denetim kapsamındaki web siteleri\n44Canlı kayıt defterindeki ayrı etki alanı rotaları — 27’si yayınlanmış kanıt dosyası ile, 17’si elle toplanmış. Yalnızca 189 web sitesini kapsayan tarayıcı denetimi, bunların 25’ini çözdü; kayıt defterine elle toplanan rotalar da eklenmiştir.\n12 yıl 6 aycsgogem.com, Bağlantı Filtresinde engellendi; api.csgem.com kayıtlı 2014-03-08 ve hiç engellenmemiş — 2026-09-22 itibarıyla bu tür 26 çiftten biri\nDoğrulanmamış toplampiyasa genelindeki gelir tahmini hariç\nSteam Çevrimiçi Davranış\n\"…Steam üzerinde aşağıdakilerden hiçbirini yapmayacak veya yapmaya teşebbüs etmeyeceksiniz: […] Ticari faaliyette bulunmak. Bu tür yasaklanmış davranışlara örnek olarak şunlar verilebilir: reklam yayınlamak; yarışmalar düzenlemek; kumar; Steam hesaplarının alınıp satılması; içerik, hediye kartları veya diğer ürünlerin satışı; ve dilencilik.\"\n\nstore.steampowered.com/online_conduct ↗ arşivlendi 2026-09-21 ↗\n\nSSA § 2.G — Ticari kullanım\n\"…[siz] bu Sözleşmenin başka bir yerinde açıkça izin verilen durumlar haricinde, İçeriği ve Hizmetleri veya bunların herhangi bir bölümünü ticari amaçlarla kullanamazsınız…\"\n\nBildirildiği üzere, Valve'ın 2016 tarihli bildirimlerinde kişisel, ticari olmayan lisans gerekçe gösterilmişti. Kayıtlara göre hiçbir operatör Valve yetki belgesini ibraz etmemiştir. store.steampowered.com/subscriber_agreement ↗ arşivlendi 2026-09-18 ↗\n\nSteam Web API Kullanım Koşulları\n\"Steam Web API'sını veya Steam Verileri, Steam Abone Sözleşmesi'ni ihlal edecek hiçbir şekilde kullanamazsınız.\"\n\nÜçüncü taraf skin pazarları, Steam API’sini kullanan otomatik hesaplar aracılığıyla faaliyet göstermektedir. Kural metninde ticari ölçekte herhangi bir istisna öngörülmemektedir. steamcommunity.com/dev/apiterms ↗ arşivlendi 2026-09-21 ↗\n\nSSA § 4.C\nOtomasyon\n\nKomut dosyaları, botlar ve insan dışı etkileşimler kısıtlanmıştır. Defter, ticari ölçekte gerçekleştirilen bot ticareti, hesap çiftlikleri ve otomatik yönlendirmeleri kaydeder.\n\nİncelemek 153bu madde altında etiketlenmiş kayıtlar ↗\nBu madde kapsamında kayıtta yer alan bilgiler153 etiketlenmiş platformlar\nDavanın Açılması15\nSkin Casino13\nCS2 Pazarı9\nCilt Ruleti8\ncsgoempire.com→csgoempirelogin4.comKumarhane\nrollbit.com→rbsnin.comKripto Kumarhanesi\n500.casino→fivezerozero.coLisanslı Kumarhane\n\nBunlardan, 153 ayrıca SSA § 2.G maddesi altında etiketlenmiştir ve 2 ayrıca SSA § 1.C maddesi altında da etiketlenmiştir — aynı hizmetler birden fazla maddeye giriyor; bu nedenle örnekler tekrarlanmaktadır.\n\n28 153’in bazı örneklerinin, ayrı bir kayıt edilebilir alan adı üzerinden kimlik doğrulaması yaptığı gözlemlenmiştir. Bir etiket, tarihlendirilmiş bir gözlemi kaydeder ve bu da platformu ilk bakışta ilgili madde kapsamına sokar; bu, yargı yoluyla tespit edilmiş bir ihlal değildir ve bunların hiçbirine ilişkin Valve yetki belgesi sunulmamıştır.\n\nSSA § 2.G\nTicari kullanım\n\nTicari kullanım için açık izin gereklidir. Belgelenmiş iş modellerini, bunların ölçeğini ve açıklanmış olan izin veya uygulama koşullarını karşılaştırın.\n\nİncelemek 175bu madde altında etiketlenmiş kayıtlar ↗\nBu madde kapsamında kayıtta yer alan bilgiler175 etiketlenmiş platformlar\nDavanın Açılması15\nSkin Casino13\nCS2 Pazarı9\nCilt Ruleti8\ncsgoempire.com→csgoempirelogin4.comKumarhane\nrollbit.com→rbsnin.comKripto Kumarhanesi\n500.casino→fivezerozero.coLisanslı Kumarhane\n\nBunlardan, 153 ayrıca SSA § 4.C maddesi altında etiketlenmiştir ve 24 ayrıca SSA § 1.C maddesi altında da etiketlenmiştir — aynı hizmetler birden fazla maddeye giriyor; bu nedenle örnekler tekrarlanmaktadır.\n\n28 175’ın bazı üyeleri, ayrı bir kayıt edilebilir alan adı üzerinden kimlik doğrulaması yaparken gözlemlendi. Bir etiket, tarihlendirilmiş bir gözlemi kaydeder ve bu gözlem, platformu ilk bakışta ilgili madde kapsamına sokar; bu, yargı yoluyla tespit edilmiş bir ihlal değildir ve bunların hiçbiri için Valve adresinden alınmış bir yetki belgesi sunulmamıştır.\n\nSSA § 3.A\nVPN ve konum gizleme\n\nIP proxy kullanımı yoluyla ikametgahın gizlenmesi, hizmetin sonlandırılmasına yol açabilir. Ayrı etki alanına sahip kimlik doğrulama sunucuları ayrı bir analiz gerektirir: Neyin gizlendiğini ve hangi kuralın geçerli olduğunu belirleyin.\n\nAuth-host kanıtını inceleyin ↗\nSteam Yardım / URL ilkeleri\nBağlantı gizleme\n\nSteam, bağlantı kısaltıcıları ve bağlantı hedeflerini gizleyen araçları yasaklamaktadır. Ayrı bir kimlik doğrulama etki alanı — rbsnin.com Rollbit'in oturum açma sürecinde, auth.dota.trade CS.MONEY'de — Steam'nin OpenID doğrulayıcısına gösterilen hedef adresin, işletilen siteyi tanımlayıp tanımlamadığı sorusunu gündeme getirir.\n\nValve'nın URL politikası ↗\n\nKural referansları: Steam Abone Sözleşmesi, 10 Eylül 2026 tarihli revizyon arşivlendi 2026-09-18 ↗ · Steam Web API Kullanım Koşulları arşivlendi 2026-09-21 ↗ · Steam URL politikası (bağlantı gizleme). Sayılar, bu dosyanın kayıtlarını ve etiketlerini ifade eder; bunlar, karara bağlanmış ihlallerin sayısı değildir.\n\nGüven açığı\nDestek ekibi dosyayı kapattığında kararı kim inceler?\n\nKaydedilmiş şikayetlerde, kalıcı yaptırımlar, yanıtlanmamış itirazlar ve çalınan öğelerin iade edilmesinin reddedilmesi yer almaktadır. Bu ifadeleri, gerçek bilet geçmişi, mevcut çözüm yolları ve hesap erişim kayıtlarıyla karşılaştırarak doğrulayın. Genel nitelikteki bir kimlik avı açıklaması, sıfırlama işlemini kimin başlattığını veya API anahtarını kimin oluşturduğunu ortaya koyamaz.\n\nKaydedilen şikayetleri okuyun ↗İlgili kayıtları talep edin →Moderatör ilişki grafiği →\nB Bölümü — Kurallar ve uygulama kaydı · 10. Bölüm\nBir otomasyon API’si. Otomasyona karşı bir kural.\nBağlam ve kaynak sınırlamaları\n\nBu bölümde ele alınan soru, bu iki unsurun nasıl uzlaştırılacağıdır: API’nin hangi kullanımları yetkilendirilmiştir, kim tarafından yetkilendirilmiştir ve hangi yayınlanmış kriterlere göre yetkilendirilmiştir. Burada yetkilendirilmiş ticari API kullanıcılarının sayısı hakkında herhangi bir tahmin yapılmamıştır ve yayınlanmış bir listenin bulunmaması da böyle bir sayıyı ima etmemektedir — burada önemli olan bulgudur, arkasındaki sayı değil. Yukarıda alıntılanan Steam destek mesajları, ArchiSteamFarm projesi tarafından kendi SSS bölümünde yeniden yayınlanmıştır (kelimesi kelimesine doğrulanmıştır 2026-09-22); bunlar Valve yayınlar değildir ve gönderildikleri hesaplar belirtilmemiştir.\n\nKural (SSA § 4.C): Steam'da komut dosyası yok, bot yok, insan dışı sistem yok. Kayıt: Valve, tek amacı sunucu-sunucu otomasyonu olan başsız bir REST API sunar ve anahtarı herhangi bir hesaba verir. Kullanıcılar otomasyon nedeniyle yasaklanmaktadır; otomasyon arayüzü Valve’un kendi ürünüdür. Hangi ticari kullanımların izinli olduğu hiçbir zaman kamuoyuna açıklanmamıştır.\n\n\"Oyun Geliştiricisi\" Yanılgısı\nSteamworks SDK (Orijinal)\n\nMeşru oyun stüdyoları tarafından başarılar, eşleştirme ve liderlik tablolarını oyun istemcilerine entegre etmek için kullanılır. Karmaşık bir C++ entegrasyonu ve resmi iş ortağı kayıt süreci gerektirir.\n\nSteam Web API (Boşluk)\n\nHarici web sunucuları için tasarlanmış, başsız bir JSON/REST mimarisi. Burada belgelenen “hijack” modelinde, bu mimari uzak sunuculardan envanterleri okumak ve eşler arası işlemleri yönetmek için kullanılır; meşru kullanım alanları bu dosyada listelenmemiştir.\n\nAnahtar kimin için?Sıradan bir Steam kullanıcısının istemci tarafında bir Web API anahtarına ihtiyacı yoktur; anahtar sayfası bir geliştirici URL’si altında yer alır ve belgelenmiş amacı, harici, sunucu tarafı erişimdir. Arşivlenmiş hesap ele geçirme şikayetleri, hesaplarına bir anahtar kaydedilene kadar bu sayfanın varlığından haberdar olmayan mağdurları anlatmaktadır.\nOtomasyon Çelişkisi\n\nSSA § 4.C'de şu hüküm yer almaktadır: \"Steam'daki İçerik ve Hizmetlerle herhangi bir şekilde etkileşim kurmak amacıyla hiçbir türde komut dosyası, bot, makro veya insan kontrolü dışında çalışan diğer sistemler ('Otomasyon') kullanamazsınız.\" Ancak Web API uç noktaları (örneğin CancelTradeOffer) insan tarafından kullanılacak bir kullanıcı arayüzüne ve captcha’ya gerek duymaz ve Steam istemcisini tamamen atlar. API, sunucu-sunucu otomasyonu için tasarlanmıştır; kural, kullanıcılar tarafından otomasyonu yasaklar; ikisi arasındaki sınır kamuya açıklanmamıştır.\n\nTicaret akışında sunucu tarafında yer alan bir pozisyon\n\nBir Web API anahtarı, üçüncü taraf bir sunucunun Steam istemcisi olmadan hesabın işlemlerini gerçekleştirmesine olanak tanır. “Hijack” modelinde, söz konusu sunucu hesap sahibi ile işlem sunucusu arasında yer alır.\n\n→Anahtarın gerçekleştirdiği işlemler için herhangi bir işlem onayı ekranı gösterilmez.\n→Arka planda sorgulama (GetTradeOffers) yapılmasına izin verir.\n→Kullanıcı müdahalesi olmaksızın teklifleri iptal eder ve yeniden düzenler.\nValve arayüzü oluşturdu, kurallarında kullanıcıların otomasyonunu yasakladı ve hangi ticari kullanımların izin verileceğine dair herhangi bir kriter yayınlamadı.\nB Bölümü — Kurallar ve uygulama kaydı · 11. Bölüm\nOn gün talep edildi. Hesap verilmesi gereken on yıl.\nBağlam ve kaynak sınırlamaları\n\n20 Temmuz 2016 tarihinde Valve’in hukuk müşaviri, kumar operatörlerine 10 günlük bir süre tanıdı. On yıl sonra (dosya anlık görüntüsü 2026-09-21 itibarıyla), söz konusu bildirime ilişkin basın haberlerinde adı geçen en az bir platform olan CSGOFast, ayrı bir etki alanına sahip bir kimlik doğrulama sunucusu üzerinden hâlâ faaliyettedir. Aşağıda, 21 Temmuz 2016 tarihli basın haberlerinden alınan metin yeniden oluşturulmuştur; bu yeniden oluşturma, bir tarama değildir. Bildirimin ima ettiği yaptırım kaydı yayınlanmamıştır. Komisyona yönelik açık mektup şöyledir: 2. Bölüm.\n\nDaha sonraki gözlemlerin yanındaki Temmuz 2016 tarihli duyuruyu okuyun. Henüz yerine getirilmemiş talep, işletmeci bazında bir uygulama kaydıdır.\n\nBir hafta önce — 13 Temmuz 2016, halka açık bir ortamda\n\nTarih: 13 Temmuz 2016 arşivlendi 2026-09-21 ↗, Valve, kumar sitelerinin Steam’yi nasıl kullandığını açıkladı: Hesap tanımlama için OpenID ve işlemler için otomatik hesaplar. Valve, bu mekanizmaların bir kumar işletmesini yürütmek amacıyla kullanılmasının, API ve kullanıcı sözleşmelerini ihlal ettiğini belirtti. Hem mekanizmanın açıklaması hem de yasak, Valve'un kendi tarihli açıklamasında yer almaktadır. 2026-09-21 tarihinde, test edilen ayrı etki alanı kimlik doğrulama sunucuları herhangi bir Bağlantı Filtresi engellemesi döndürmedi ve Valve, operatör bazında herhangi bir uygulama kaydı yayınlamadı.\n\nEK A / TEMMUZ 2016DİZGİ YENİDEN OLUŞTURMA\nVALVE ŞİRKETİ\n\nBellevue, Washington\n\nTARİH:Temmuz 2016 (basında 21 Temmuz 2016 tarihinde yer aldı)\nGÖNDEREN:Karl Quackenbush, Hukuk Müşaviri\nRE:Durdurma ve vazgeçme talebi — Steam hesaplarının ticari amaçla kullanımı\nNOT:Bildirilen metnin yeniden oluşturulması; tarama değil\n\n\"Aşağıda listelenen kumar sitelerinden birini işlettiğinizin farkındayız. Bu işi yürütmek için Steam hesap kullanıyorsunuz. Steam Abone Sözleşmesi uyarınca, Steam ve Steam hizmetleri yalnızca kişisel ve ticari olmayan kullanım için lisanslanmıştır.\"\n\n\"Steam hesaplarınızı ticari amaçlarla kullanmaya derhal son vermelisiniz. Aksi takdirde, on (10) gün içinde, Valve, hesaplarınızın kapatılması da dahil olmak üzere, ancak bununla sınırlı olmamak üzere, mevcut tüm hukuki yollara başvuracaktır.\"\n\nDosya yeniden oluşturma · kaynak kayda bakın\nKarl Quackenbush\nHukuk Müşaviri, Valve Corp.\nKENAR NOTU / EDİTÖR YAZISI\nOn gün.Peki sonra ne olacak?\n\nSon tarih kesin olarak belirlenmişti. Halkın bu konuda atacağı adımlar da öyle olmalı.\n\nValve'ın \"2016\" başlıklı yayınlanmış görüşü ↗\nSon başvuru tarihine ilişkin bir not +\nHİCİV / VALVE İLETİŞİMİ DEĞİLDİR\n\nSevgili son tarih,\n\nSana on gün süre verilmişti. Her nasılsa, takvim çalışmaya devam eden tek şeydi.\n\nLütfen tüm yanıtları kamu kayıtlarına iletiniz.\n\nZaman ÇizelgesiTemmuz 2016 – Eylül 2026\nİlanda belirtilen son tarih:\n10 Gün\nTemmuz 2016\nBildirimden bu yana geçen süre:\n3,715 Gün\n20 Temmuz 2016 tarihinden 21 Eylül 2026 tarihli dosya anlık görüntüsüne kadar sabit tutan sayıdır; gerçek zamanlı bir rakam değildir\nYayınlanmış uygulama kaydı:\nYok\nOperatör bazında sonlandırma veya engelleme kayıtlarına rastlanmadı\n\n◀ 0–10. Günler — son tarih, ölçeklendirilmek üzere3715. Gün — anlık görüntü ▶\n\n20 Temmuz 2016On günlük talep bildirimi yayınlandı0. Gün\n17 Şubat 2024DSA yükümlülükleri geçerlidir0. Gün\n25 Şubat 2026New York Başsavcılığı’nın şikâyeti açıklandı0. Gün\n21 Eylül 2026Dosya özeti3715. Gün\n\nOn yıl sonra, CSGOFast — 2016 tarihli bildirimlere ilişkin basın haberlerinde adı geçen — şu anda faaliyettedir: csgofast.com, 2026-09-19 ve 2026-09-21 adreslerinde Link Filter engellemesi döndürürken, kimlik doğrulama sunucusu steam-login.authtofast.com (kayıtlı 2026-06-30) bunu yapmadı.\n\nValve'nin güvenlik değişikliklerine ilişkin tam ve tarihli kayıt: Güvenlik Zaman Çizelgesi → · Washington eyaletindeki kayıtlar ve uygulama standardı: aşağıda\n\nKayıtlarda yer alan bilgiler: 2016 tarihli bildirimde 10 günlük bir süre belirlenmişti; Valve halihazırda bir alan adı listesi (Link Filter) işletiyordu ve kendi OpenID isteklerinde yetkilendirme ana bilgisayar adlarını alıyordu; operatör bazında herhangi bir uygulama kaydı yayınlanmamıştır. Topluluk raporlarında bir pazar yeri (SkinJar) aleyhine 2018 yılında alınan bir önlemden bahsedilmektedir, ancak bu raporlar doğrulanmamıştır ve burada dayanak olarak kabul edilmemiştir.\nCSGOFAST / KAYDEDİLMİŞ DOĞRULAMA YOLU\nBelirtilen geri dönüş sunucusunu takip edin.\n\nKaydedilen rota kayıtlarının bağlantıları csgofast.com ...'ye steam-login.authtofast.com. Ayrı ana bilgisayar adı, Steam OpenID isteğinde yer alır. Bu, araştırmacılara Valve'ın filtreleme ve uygulama kayıtlarıyla karşılaştırabilecekleri somut bir adres sağlar.\n\nCSGOFast rotasını ve kaynağını inceleyin ↗ · Kayıtlı Steam'ı karşılaştır Bağlantı Filtre sonuçları ↗\n\nKAMU KAYDI / WASHINGTON · 2016 → 2026\nİki son tarih. Yanıtlanmamış tek bir uygulama standardı.\n20 TEMMUZ\nValve, kumar sitelerine 10 gün süre tanır\n\nŞirketin avukatının talebinde, Steam hesaplarının ticari amaçla kullanılmaya devam edilmesinin hesapların kapatılmasına yol açabileceği uyarısında bulunuldu.\n\n27 Eylül\nWashington tuşuna basın Valve\n\nEyalet Kumar Komisyonu, kumar amacıyla yapılan “skin” transferlerini durdurmaya yönelik adımlara ilişkin kanıt talep etti ve yanıt için 14 Ekim tarihini son tarih olarak belirledi.\n\n17 EKİM\nValve bu suçlamayı reddediyor\n\nValve, son başvuru tarihinden sonra yanıt verdi; kumar faaliyetlerine zemin hazırladığını reddetti, ilgili hesapları devre dışı bıraktığını belirtti ve herkes için ticareti ve OpenID hizmetini kapatmak istemediğini ifade etti. Temmuz ayındaki bildirimlerle ilgili basın haberlerinde adı geçen en az bir platform (CSGOFast), on yıl sonra hâlâ faaliyet gösteriyordu. Her iki durum da ancak operatörün devre dışı bırakılan hesapların yerine yenilerini getirmiş olması halinde geçerli olabilir; bunu gösterecek kayıtlar ise yayınlanmamıştır. WSGC, Valve’den bu iki durumu birbiriyle uyumlu hale getirmesini istemelidir.\n\n2026\nEylül 2026’da gözlemlenen güzergâhlar\n\nRota kayıtlarında, 2016 yılında açıklanan OpenID ve Valve ticaret mekanizmalarını kullanarak CSGOFast dahil olmak üzere ayrı etki alanlı kimlik doğrulama sunucuları aracılığıyla kimlik doğrulaması yapan 44 platform kayıtlıdır. Hangi operatörlerin erişiminin kesildiğini gösterecek uygulama kaydı henüz sunulmamıştır.\n\nKOMİSYONUN KENDİ BİLGİLENDİRME NOTU · 30 OCAK 2018\nValve'nin yanıt vermesinden on sekiz ay sonra, düzenleyici kurum bunu hâlâ bir niyet olarak nitelendirdi.\n\nKomisyon, HB 2881 sayılı yasa tasarısına ilişkin kamuya açık oturumda kendi yasama organına bilgi verirken, Temmuz 2016 tarihli açıklamayı kendi sözleriyle şöyle aktardı: Valve \"Platformunun, skinlerle kumar oynanmasını kolaylaştırmak amacıyla kullanılmasına karşı sert önlemler alma niyetini açıkladı.\" Aynı sayfada, bu duyurunun sektör tahminlerine nasıl bir etki yaptığı da belirtilmiştir — \"sonuç olarak,\" 2020 yılı için öngörülen skin kumar pazarı, $19.7 milyar ...'ye $670 milyon, sadece bu açıklamanın etkisiyle yaklaşık yüzde 97’lik bir düşüş yaşandı. Tahmin değişti. Bunu haklı çıkaracak operatör başına uygulama verileri ise hâlâ yayınlanmadı.\n\nPiyasa rakamları, Komisyon’un bilgilendirme belgesinde aktarılan Narus Advisors / Eilers & Krejcik Gaming tahminleridir; Komisyon’un kendi bulguları değildir. Aynı belgede, 2016 yılına ait skin bahis hacminin yaklaşık $5 milyar olduğu ve bunun yaklaşık $3 milyarı kumarhane tarzı sitelerde gerçekleştiği belirtilmektedir. Erişim tarihi: 2026-09-22, SHA-256 c507c9025f93da0aadaf395c4d8882f25973211c318ee8e9b6f18a5b3755e050.\n\nValve'nin 2016 yılında kamuoyuna açıkladığı tutum ile günümüzde gözlemlenebilen altyapı yan yana karşılaştırılabilir. Asıl soru, yaptırımların yasaklanmış operatörlerin kullandığı hesaplara ve rotalara ulaşıp ulaşmadığıdır. On günlük bildirim süresi, bildirimin içinde adı geçen işletmecilerin tümüne ulaştırıldığının kanıtı değildir. 2018 tarihli OPSkins operasyonu, adı belirtilen bir operatöre karşı gerçekleştirilen tek belgelenmiş müdahaledir; denetlenen 189 platform ve operatör başına yayınlanmış hiçbir kayıt göz önüne alındığında, tek bir belgelenmiş müdahale, bir uygulama eğilimi göstermez.\n\nWashington Kumar Komisyonu’nun 2016 tarihli bildirisi ↗ arşivlendi 2026-05-20 ↗ · Valve'nin 17 Ekim 2016 tarihli yanıtı (belge kopyası) ↗ · WSGC’nin yasama organına yaptığı bilgilendirme, 30 Ocak 2018 (yerel kopya, 4 sayfa) ↗ · wsgc.wa.gov adresindeki aynı dosya ↗ · alma kaydı ve hash ↗ · Valve'nin 2018 OPSkins etkinliği ↗ arşivlendi 2026-03-07 ↗ · Mevcut güzergâh denetimi ↗\n\nAdli Boylamsal Denetim · 2016 Yılına Ait İhtarname Hedefleri\n“10 Günlük Bildirim On Yılı”: Adı Geçen 23 Tesisin Adli Hayatta Kalma Denetimi\n\n19–20 Temmuz 2016 tarihlerinde, Valve Genel Hukuk Müşaviri Karl Quackenbush, 23 skin kumar platformuna resmi ihtarnameler göndererek, bu platformlara Steam hesaplarının ticari kullanımını sonlandırmalarını emretti. 10 gün hesap kapatma ve yasal işlem tehdidi altında. 3,700 günün üzerinde bir süre sonra, ampirik bir denetim, yaptırımların gerçek seyrini ortaya çıkardı: çok sayıda operatör faaliyetlerini hiçbir zaman durdurmadı, diğerleri ise son tarihten sonra altı yıla kadar faaliyetlerini sürdürdü ve milyarlarca dolarlık ekosistem, Valve’in OpenID mimarisinden yararlanmaya devam etti.\n\n5+ CANLI\n2026 yılında kesinlikle faaliyete geçecek (CSGOBig, CSGO500, CSGOFast vb.)\n6 YIL\nKapanıştan önce bildirimin yayınlanmasından sonraki en uzun süre (CSGOatse, 2022 yılına kadar aktif kaldı)\n$5.01B\n2016 yılı cilt bahis hacmi (Narus / Eilers & Krejcik)\n200'den fazla\nPiyasanın en yoğun olduğu dönemde faaliyet gösteren aktif çevrimiçi kumar siteleri\nHayatta Kalan Titanlar · 2024–2026 Mali ve Trafik Planı\n10 Günlük Uyarılar'dan Denizaşırı Holdinglere: Milyarlarca Dolarlık Cirolar\n\nValve’un 2016 tarihli duyuruları, skin ticareti ortadan kaldırmak yerine sektörel bir dönüşümü tetikledi. Hayatta kalan operatörler, denizaşırı şirketler (Curaçao, Belize, Kıbrıs) olarak yeniden yapılandılar, bot yasaklarını aşmak için Peer-to-Peer (P2P) ticaretine öncülük ettiler ve şu anda Aylık 10 milyon web ziyareti ve yıllık milyarlarca dolarlık bahis hacmi Steam aracılığıyla kimlik doğrulamaya devam ederken:\n\nPlatform / Alan Adı\tTemmuz 2016 Duyurusu\tUygulama Sonucu ve Hayatta Kalma Durumu\tKaydedilmiş Doğrulama / Ana Bağlantılar\nCSGOBig\ncsgobig.com\t10 Günlük Bildirim (Temmuz 2016)\t2026'DA HÂL YAŞIYOR\nGeçici olarak durduruldu, yeniden başlatıldı; letmeinbig.com ve csgobiglogin.com üzerinden kimlik doğrulaması yapılır\tX: @csgobig ↗ · FB: csgobigofficial ↗\nCSGO500\ncsgo500.com / 500.casino\t10 Günlük Bildirim (Temmuz 2016)\t2026'DA HÂL YAŞIYORUM\n500 Casino olarak yeniden markalaştı (Curaçao lisans numarası #8048/JAZ2014-037), aylık cirosu milyonlarca\tCanlı Platform (500.casino) ↗\nCSGOFast\ncsgofast.com\t10 Günlük Bildirim (Temmuz 2016)\t2026'DA HÂL YAŞIYOR\nSteam-login.authtofast.com üzerinden aktif olarak rulet, crash ve jackpot oyunları oynanmaktadır\tDosya Yetki Denetimi ↗\nCSGOLounge / Dota2Lounge\ncsgolounge.com / dota2lounge.com\t10 Günlük Bildirim (Temmuz 2016)\t2026'DA HÂL YAŞIYOR\nE-spor para birimi bahisleri ve kripto para bahislerine odaklandı; kesintisiz faaliyetini sürdürdü\tCanlı Platform ↗\nCSGOCasino\ncsgocasino.net / csgocasino.gg\t10 Günlük Bildirim (Temmuz 2016)\tLIVE VIA SUCCESSOR (2026)\nAlan adı yönlendirildi; aktif hale gelen yeni portal csgocasino.gg adresi altında hizmet vermektedir\tHalef Etki Alanı ↗\nCSGOatse\ncsgoatse.com\t10 Gün Önceden Bildirim (Temmuz 2016)\t6 YIL DAYANDI (2022'YE KADAR AKTİF)\nValve'un 10 günlük ültimatomunun ardından altı yıl boyunca kumar faaliyetleri tam kapasiteyle devam etti\tX: @CSGOatsecom (2022'ye kadar aktif) ↗\nCSGOSweep\ncsgosweep.com\t10 Gün Önceden Bildirim (Temmuz 2016)\tARALIK 2017'YE KADAR HAYATTA KALDI\nSon başvuru tarihinden sonra 17 ay boyunca halka açık olarak faaliyet gösterdi\tX: CS:GO Sweep Durumu Aralık 2017 ↗\nCSGOWild\ncsgowild.com\t10 Günlük Bildirim (Temmuz 2016)\tARALIK 2017’E KADAR YAŞADI\nÖnemli influencerlar tarafından tanıtıldı; C&D’den sonra kripto sektörüne geçiş yapana kadar 1,5 yıl boyunca faaliyet gösterdi\tX: @Wild (Aralık 2017'de aktif) ↗\nCSGOPot\ncsgopot.com\t10 Günlük Bildirim (Temmuz 2016)\tEYLÜL 2017'YE KADAR YAŞADI\nBildirim tarihinden itibaren 14 ay boyunca yüksek meblağlı ikramiyeli bahisler düzenlendi\tX: @csgopot (Eylül 2017'de aktif) ↗\nCSGODiamonds\ncsgodiamonds.com\t10 Gün Öncesinden Bildirim (Temmuz 2016)\t2017'nin ortasına kadar ayakta kaldı\nSponsorlu yayıncılar için sonuçların tahrif edildiği itiraf edilmesine rağmen 2017 yılı boyunca devam etti\tX: @csgodiamondscom (2017) ↗\nCSGOLotto\ncsgolotto.com\t10 Günlük Bildirim (Temmuz 2016)\tTEMMUZ 2016'DA KAPANDI\nKamuoyunda patlak veren bir skandalın ardından faaliyetlerini durdurdu; federal FTC’nin rıza kararının hedefi oldu\tFTC Onay Kararı (Dava Dosyası C-4632) ↗\nCSGODouble\ncsgodouble.com\t10 Günlük Bildirim (Temmuz 2016)\tTEMMUZ 2016'DA KAPANDI\nC&D bildiriminin yayınlanmasının hemen ardından gönüllü olarak faaliyetleri durdurmak\tX: @CSGODouble (Temmuz 2016'da kapatıldı) ↗\nCSGOMassive\ncsgomassive.com\t10 Günlük Bildirim (Temmuz 2016)\t2016'da KAPALI\n2016 yılının sonlarında halka açık faaliyetlerini sonlandırdı\tX: @csgo_massive ↗\nCSGOStrong\ncsgostrong.com\t10 Günlük Bildirim (Temmuz 2016)\t2016'da KAPALI\n2016 yılında halka açık hizmetlerini sonlandırdı\tFB: csgostrongfree ↗\nSkins2\nskins2.com\t10 Günlük Bildirim (Temmuz 2016)\t2016'da KAPALI\n2016 yılında halka açık hizmetlerini sonlandırdı\tFB: CSNCOM ↗\n\nPlatform\tAylık Trafik (Ziyaret Sayısı)\tTahmini Cirosu / Hacmi\tTüzel Kişilik ve Yargı Yetkisi\tÖnemli Düzenleyici Önlemler ve Model\nCSGOEmpire\ncsgoempire.com\t2,3 milyon — 9,0 milyon / ay\nOrtalama süre 6+ dakika; 80% doğrudan\t$1.5B — $2.5B Yıllık İşlem Hacmi\n>1,000,000 Ayda P2P skin ticareti; $6.4M aktif likit emir havuzu\tMoonrail Limited B.V. (Curaçao #148182)\nÖdemeler: JHOLT LTD (Kıbrıs); Kurucu: \"Monarch\" (Ossi Ketola)\tÜcretsiz P2P eşya ticaretinin öncüsü; Curaçao OGL/2024/1183/0869 lisanslı\nCSGORoll\ncsgoroll.com\t2,74 milyon — 3,5 milyon / ay\nOrtalama süre: 9 dakika 23 saniye; 16% hemen çıkma oranı\t$1.0B — $2.0B Yıllık İşlem Hacmi\nKumarhanenin avantajından elde edilen yıllık kurumsal gelir tahmini: $100M–$200M\tFeral Holdings Limited\nMerkezi Belize City, Belize’de bulunan (Kayıt No. 171519)\tAvustralya ACMA tarafından yasaklandı (Mayıs 2023); reşit olmayan oyuncuları kadrosunda bulunduran birinci kademe takım G2 Esports’a sponsorluk yaptı\n500 Casino (CSGO500)\n500.casino / csgo500.com\t220 bin — 425 bin / ay\nAylık yaklaşık 105 bin tekil ziyaretçi\tRoyales’te haftada $100k (yılda $5.2M)\nYüksek bahisli oyuncular için bahis şartı: $1 rakeback başına $400 bahis\tPerfect Storm B.V. (Curaçao #150536)\nCuraçao Kumar Denetleme Kurulu lisansı OGL/2024/1354/0882\tİsveçli oyunculara ruhsatsız bir şekilde hitap ettiği gerekçesiyle İsveç Spelinspektionen tarafından yasaklandı (Kasım 2023)\nCSGOBig\ncsgobig.com\t~169,600 / ay\nOrtalama süre 19 dakika 12 saniye; ABD ön seçimleri\tYıllık Milyonlarca Birim Hacim\nGizemli kutular, rulet ve kutu savaşları\tYardımcı proxy yönlendirmesi yoluyla çalışır\nletmeinbig.com (2023'te tescil edildi) & csgobiglogin.com\tTemmuz 2016 tarihli C&D hedefi; vekil kimlik doğrulama mimarisiyle yeniden başlatıldı\nCSGOFast\ncsgofast.com\t~150 bin — 250 bin / ay\nDünya çapında çok dilli kitle\tYıllık Milyonlarca Birim Hacim\nYüksek hızlı rulet ve crash oyunları\tDenizaşırı operasyonel kuruluşlar\nYollar Steam steam-login.authtofast.com üzerinden kimlik doğrulama\tTemmuz 2016 tarihli C&D'nin hedefi; faaliyetlerini hiçbir zaman durdurmadı; 2026'da da faaliyette\nCSGO Polygon\ncsgopolygon.com / plg.bet\t~300 bin — 500 bin / ay\nBDT ve Doğu Avrupa’nın hakimiyeti\tYıllık Milyonlarca Birim Hacim\nKripto ve skin ruleti, maç bahisleri\tİkinci dalga hedefi (Ekim 2016)\nplg.bet adlı ayna alan adıyla kripto para birimine yöneldi\tTam on yıl boyunca ayakta kaldı; üçüncü taraf API’leri aracılığıyla varlık tasfiyesine devam ediyor\nİkinci Dalga: Valve'nin İhtarnamesi Neden Toplamda 43'ten Fazla Siteyi Hedef Aldı?\n\n17 Ekim 2016 tarihinde, Valve’nin hukuk danışmanı, Washington Eyaleti Kumar Komisyonu’na, 19 Temmuz’da gönderilen ilk 23 bildirimin ardından, Valve’in şu kuruluşlara faaliyet durdurma mektupları gönderdiğini resmen bildirdi: 20'den fazla ek çevrimiçi kumar sitesi (böylece resmi toplam sayı 43’ün üzerine çıktı). Bu ikinci dalga, ilk listede dünyanın en büyük ve en kötü şöhretli kumar merkezlerinin açıklanamayan bir şekilde yer almaması nedeniyle gerekli hale geldi:\n\nCSGOJackpot.com: Federal suçlama tehdidi altında faaliyetlerini sonlandırmadan önce yüz milyonlarca dolarlık işlem hacmi gerçekleştiren, “skin jackpot” sisteminin tarihi öncüsü.\nCSGOShuffle.com: Temmuz 2016'daki canlı yayın skandalının merkezinde yer alan site; Twitch yayıncısı PhantomL0rd'un şirketin 33% hissesine gizlice sahip olduğu ve şirket fonlarıyla bahis oranlarını manipüle ettiği ortaya çıkmıştı.\nMakro Ekosistem (200'den fazla operatör): Narus Advisors ve Eilers & Krejcik Gaming tarafından yapılan sektör araştırmasına göre, 2016 yılında 200’den fazla farklı skin kumar sitesi faaliyet göstermiş ve 3,03 milyon aktif oyuncudan $5.01 milyar bahis hacmi elde etmiştir. Valve'nin 43 mektubu, aktif pazarın 20%'inden daha azını kapsamaktaydı.\nSteam Skin Kumarına İlişkin Resmi Hükümet ve Düzenleyici Kurum Soruşturmaları\n\nKumar bağımlılığı olgusu, çok sayıda resmi yasal soruşturma, yaptırım işlemi ve hükümetin görüş belgelerinde belgelenmiştir:\n\n1. Washington Eyaleti Kumar Komisyonu (WSGC) (2016–2018)\n\n5 Ekim 2016 tarihinde resmi bir “Faaliyet Durdurma ve Vazgeçme” talebinde bulunuldu; 30 Ocak 2018 tarihinde, skinlerin nakit muadili olduğunu belgeleyen ve $5.0B tutarındaki skin bahis hacmini bildiren bir Yasal Bilgilendirme Yayını yayınlandı.\n\nWSGC Yasama Raporu PDF (Yerel Kopya) ↗\n2. ABD Federal Ticaret Komisyonu (FTC) (Eylül 2017, Dava Dosyası C-4632)\n\nCSGOLotto sahipleri Trevor Martin ve Thomas Cassell aleyhine, aldatıcı uygulamalar ve platform kontrolünün açıklanmaması gerekçesiyle, “skin gambling” ile ilgili ilk federal düzenleyici yaptırım kararı.\n\nFTC Kararı ve Rıza Kararı ↗\n3. Birleşik Krallık Kumar Komisyonu (UKGC) Görüş Belgesi ve Gençlik Denetimleri\n\nOyun içi görünümler, 2005 tarihli Kumar Yasası kapsamında resmen “para veya para değeri” olarak sınıflandırıldı. Daha sonra yapılan anketlerde, 11–16 yaş arası çocukların %0’ından fazlasının video oyunlarında görünümler üzerine bahis oynadığı ortaya çıktı.\n\nUKGC Araştırma Arşivi ↗\n4. Avustralya Senatosu Çevre ve İletişim Soruşturması (2018)\n\nFederal Parlamento raporu: \"Şansa dayalı öğeler için oyun içi mikro işlemler\", Valve'un ganimet kutusu mekanizmalarını, ikincil piyasadaki nakit çekimlerini ve düzenlemelerin atlatılmasını değerlendirerek.\n\nAvustralya Parlamentosu Soruşturması ↗\nKarşılanmamış talep\n\nUygulama kaydını yayınlayın: Hangi kumar hesapları ve botların devre dışı bırakıldığını, hangi geri dönüş sunucularının kısıtlandığını ve hangi ticari hizmetlere izin verildiğini belirtin. Halka açık bir yasaklama ve ana sayfada yer alan bir uyarı, ilgili faaliyetin durdurulduğunu kanıtlamaz.\n\nB Bölümü — Kurallar ve uygulama kaydı · 12. Madde\nAna bilgisayar adı, istekte zaten mevcut.\nBağlam ve kaynak sınırlamaları\n\nValve halihazırda bir etki alanı listesi (Bağlantı Filtresi) tutmaktadır ve her OpenID isteğinde kimlik doğrulama ana bilgisayar adını almaktadır. Aşağıdaki sözde kod, bu ikisinin birbirine bağlanmasının mantıksal yapısını göstermektedir. Valve’in bunu yaptığına dair kamuya açık bir kanıt bulunmamaktadır.\n\nValve halihazırda bir etki alanı engelleme listesi kullanmaktadır. Valve her OpenID isteğinde oturum açma ana bilgisayarını zaten almaktadır. Hiçbir şeyin inşa edilmesine gerek yok — ikisinin birleştirilmesi gerekiyor. Bu, Valve'un kendi kendine güncellediği bir listeye göre yapılan bir ana bilgisayar adı aramasıdır. Aşağıdaki sözde kod, bir örnek niteliğindedir; Valve'in uygulamasını yansıtmamaktadır.\n\nforensic_autoban.py\n# ÖRNEK PSEUDOKOD — Valve.block_domain() ve flag_session_as_mitm() gerçek API çağrıları değildir. Bu, Valve'in proxy kimlik doğrulama etki alanlarına karşı uygulayabileceği bir önlem mekanizmasının mantıksal yapısını gösterir; Valve'nin gerçek iç işleyişini değil.\n# Örnek: Gelen OpenID isteğinin kontrolünün mantıksal yapısı\ndef audit_openid_request(istek):\nblocked_origins = database.get_blacklisted_platforms()\nproxy_domain = request.params.al('openid.realm')\ntarget_redirect = request.params.al('openid.return_to')\n\n# Mantık: Proxy, engellenmiş bir siteye yönlendiriyorsa, proxy'yi yasakla.\niçin site içinde engellenen_kaynaklar:\neğer site içinde target_redirect:\nValve.block_domain(proxy_domain)\nValve.flag_session_as_mitm(request.session)\n# Sonuç: söz konusu ana bilgisayar için yapılan oturum açma isteği reddedildi\n\nGözlem:\nBir ana etki alanı halihazırda Bağlantı Filtresinde yer alıyorsa (örn. howl.gg, engellenen 2026-09-18/19/21) ve bu sitenin oturum açma düğmesinden gelen OpenID isteğinde kimlik doğrulama ana bilgisayarı (howl.uno) görünüyorsa, bu ilişki Valve tarafından kendi istek verilerinden gözlemlenebilir. Kontrol otomatikleştirilebilir; ancak bunun çalıştırılıp çalıştırılmayacağı otomatikleştirilemez.\nBelgelenmiş ve raporlanmış emsal kararlar\n\nValve, kayıtlara göre en az bir kez üçüncü taraf bir operatöre karşı müdahale etmiştir: 2018 yılında OPSkins’in ExpressTrade sistemi üzerinden erişimini iptal etmiştir (Valve'nin duyurusu ↗ arşivlendi 2026-03-07 ↗). 2018 yılına ait topluluk raporlarında da bir pazar yerinin (SkinJar) erişimini kaybettiği belirtilmektedir; bu raporlar doğrulanmamıştır ve söz konusu mekanizma, açıklanan bir süreçten değil, sonuçtan çıkarılmıştır.\n\nBu emsal kararın ortaya koyduğu husus:\n\nValve, istediği zaman üçüncü taraf bir operatörün erişimini kesebilir. Temmuz 2016 tarihli bildirimlere ilişkin basın haberlerinde adı geçen CSGOFast, 2026-09-21 üzerinde faaliyet gösteriyordu ve 2026-06-30’de kayıtlı bir yetkilendirme sunucusu kullanıyordu; bu sunucu, Link Filter engellemesi döndürmüyordu. Neden bir operatörün erişimi kesilirken diğerlerinin kesilmediğine dair yayınlanmış herhangi bir kriter bulunmamaktadır.\n\nKayıt tarihinin neleri gösterdiği ve neleri göstermediği\n\nBir kimlik doğrulama sunucusunun kayıt tarihi, söz konusu sunucunun bir OpenID isteğinde ilk kez ne zaman ortaya çıkmış olabileceğine dair bir alt sınırdır; bu, sürekli kullanım olduğunu göstermez. sc-auth.netÖrneğin, 2019-04-02 (RDAP) olarak kaydedilmişti ve Eylül 2026’da Skin.Club’un Steam oturum açma akışında gözlemlenmişti; bu iki tarih arasında neler yaşandığına dair kamuya açık bir kayıt bulunmamaktadır.\n\nKarşılaştırmalı Denetim: API Uyumluluk Standartları\nUygulama Boyutu\tGitHub API Kuralları\tSteam Web API (Valve)\n1. Uyum Tarafsızlığı\tYayınlanmış, tek tip kurallar. Belgelenmiş hız sınırları (örn. kimliği doğrulanmış kullanıcılar için 5,000 çağrı/saat, GitHub Enterprise Cloud kuruluşları için 15,000/saat) ve yayınlanmış kabul edilebilir kullanım ilkeleri her hesap için geçerlidir.\tYayınlanmış herhangi bir kriter bulunmamaktadır. Bireysel hesaplar, otomasyon ve ticari kullanım hükümleri (arşivlenmiş şikâyetler) kapsamında kapatılmaktadır; ancak ticari platformlar için operatör bazında herhangi bir yaptırım kaydı yayınlanmamıştır.\n2. OpenID / Kimlik Doğrulama Proxy'sinin Kötüye Kullanımı\tGitHub’un yayınlanmış politikaları, kötüye kullanım durumunda OAuth uygulamalarının ve jetonlarının askıya alınmasına veya iptal edilmesine izin vermektedir; ayrıca, belgelerinde ifşa olmuş jetonların otomatik olarak iptal edilmesi süreci açıklanmaktadır (yazarların GitHub belgelerine ilişkin özeti).\tSteam OpenID akışlarında gözlemlenen ayrı etki alanına sahip kimlik doğrulama sunucuları (örn. rbsnin.com, howl.uno, sc-auth.net), ana etki alanlarının aksine 2026-09-21'da herhangi bir Bağlantı Filtresi engellemesi döndürmedi.\n3. Suistimalden Gelir Elde Etme\tGitHub, üçüncü taraf otomasyon sistemleri aracılığıyla taşınan ürünler için herhangi bir işlem ücreti almaz; gelir modeli, abonelikler ve pazar yeri listelemelerinden oluşur.\tValve, bu eşyaları elde etmeyi sağlayan kutu anahtarlarını satmaktadır ve Topluluk Pazarı, Pazar içinde gerçekleştirilen satışlar üzerinden toplamda yaklaşık 15% tutarında bir ücret almaktadır. Üçüncü taraf platformlara atfedilebilecek gelirle ilgili herhangi bir rakam burada tahmin edilmemektedir.\n4. Kaçınma Döngüsünün Ömrü\tAskıya alınan OAuth istemci kimlikleri, askıya alma işlemi gerçekleştirildiğinde platform genelinde çalışmaz hale gelir; belgelerde bu durumun ne kadar sürede gerçekleşeceğine dair bir rakam belirtilmemiştir ve burada da böyle bir varsayımda bulunulmamıştır.\tKayıt tarihleri 2011 ile Eylül 2026 arasında olan ayrı etki alanlı kimlik doğrulama sunucuları, 2026-09-19 ve 2026-09-21 kontrollerinde herhangi bir Bağlantı Filtresi engellemesi göstermedi. Kayıt tarihi, olası kullanımın alt sınırını belirtir; sürekli kullanımın kanıtı değildir.\nKaynaklar: GitHub köşe yazısı — GitHub’ın yayınladığı API hız sınırı ve platform politikası belgeleri (yazarların özeti, alıntı yapılmamıştır) · Steam köşe yazısı — 2026-09-19 ve 2026-09-21 numaralı Bağlantı Filtresi kontrolleri (linkfilter-recheck-2026-09-21.json), RDAP kayıt defteri (domain-registration.json) ve arşivlenmiş destek şikayetleri (kanıt arşivi).\nB Bölümü — Kurallar ve uygulama kaydı · 13. Madde\n0 dışındaki fiyat farkı\n\nÜrün, Steam envanterinde bulunuyor; satış başka bir yerde gerçekleşiyor. Fabrika Çıkışı Yeni bir AWP Dragon Lore’un CSFloat'ta 62 canlı teklif; istenen en düşük fiyat $10,623.95. Steam’in kendi pazarında, yaklaşık $1,800’ın üzerinde bir satış fiyatı gösterilemez. Gözlemlenen daha yüksek fiyattan satış yapabilmek için, bir sahibin Steam dışındaki bir alıcıya veya pazara ihtiyacı vardır. Ürün ve devri hâlâ Steam’e bağlıdır.\n\nWhat this means — the Community Market listing ceiling\n\nSteam’s own market refuses a listing above roughly $1,800. A seller may ask less, never more. Items whose market price sits above that line therefore cannot be sold at that price on Steam at all — which is the mechanism that moves those sales to third-party venues while the item itself never leaves Valve’s inventory system.\n\nSection 13 — the off-Steam price gap →\n\nBağlam ve kaynak sınırlamaları\n\nBu bölümde üç farklı sayım yer almaktadır ve bunlar birbirinin yerine kullanılamaz. 245 20 Eylül 2026 tarihinde, yalnızca CSFloat'ta en ucuz aktif teklifin $1,800'u aştığı CS2 ürün adı kategorilerinin sayısıdır. 241 Bu, CSFloat'un $100,000 tavanına sabitlenmiş dört kategorinin çıkarıldığı aynı kümedir; bu panel, $13.63M tabanının hesaplandığı paneldir. 248 Bu ise farklı bir anlık durumdur: 23 Eylül 2026 tarihinde beş satış platformundan ikisi veya daha fazlası tarafından üst sınırın üzerinde fiyatlandırılan kategoriler. Satış platformları birbiriyle örtüşmektedir; bu nedenle farklı platformlardaki sayılar asla toplanmamalıdır. Buradaki tüm rakamlar, gerçekleşmiş bir satış değil, talep edilen fiyattır ve bunların hiçbiri Valve ya da başka herhangi bir kişi için gelir, ciro veya kâr değildir. PriceEmpire’da listelenen değerler, söz konusu site tarafından yayınlanan yuvarlatılmış tahminlerdir ve Steam kartı diğer Steam oyundaki öğeleri de kapsamaktadır; dolayısıyla karşılaştırma kapsamları birbiriyle aynı değildir.\n\nBir ürün. İki fiyat sistemi.KAYDI TAKİP EDİN\nAdım 3 / 3\n\nBu talepte, satıcının Steam dışındaki bir satış yeri veya alıcıya ihtiyacı vardır. Ürün, yine de Steam’in stok ve transfer sistemine bağlıdır.\n\nSTEAMHakkında $1,800Yayınlanan Topluluk Pazarı listeleme sınırı\nKAYDEDİLMİŞ KATALOG$10,623.95Fabrika çıkışı yeni AWP Dragon Lore – fiyat sor\nBAĞIMLILIKHâlâ Steam adet varStok ve transfer durumu Steam olarak kalır\n01 / ÜRÜNValve oyun envanteriSteam'da tutulan CS2 veya Dota 2 eşyası\n02 / TAVAN$1,800 hakkında, Steam'deBir Market ilanı için maksimum fiyat\n03 / DIŞARIDAN SORULAN SORU$10,623.95, Dragon Lore içinTarihli anlık görüntüde en ucuz CSFloat teklifi\n04 / TESLİMATSteam zincirde kalırMülkiyet ve eşya devri, bu sisteme bağlıdır\nPAZAR YAPISI · TARİHLİ ANLIK GÖRÜNTÜ, 20 EYLÜL 2026\nFiyat farkı ölçülebilir.\n\nEn ucuz aktif teklifin1,800.'ın biraz üzerinde olduğu ürün adı kategorilerini saydık. CSFloat ve Skinport, CS2 envanterleri kısmen örtüşen ayrı anlık görüntülerdir; bu sitelerdeki sayılar toplanamaz. Dışarıdaki teklifler, daha yüksek satış fiyatlarının yayınlandığı yerleri gösterirken, Steam ise hâlâ ürün sahipliği ve devrini kontrol etmektedir.\n\n245CS2 KATEGORİLERİ · CSFLOAT\n166CS2 KATEGORİLERİ · SKINPORT\n3DOTA2 KATEGORİLERİ · SKINPORT\n$10,623.95DRAGON LORE KAT SORU\n\nDragon Lore: 62 adresinde, “Factory New” kategorisinde CSFloat adet teklif bulunmaktadır; gösterilen fiyat, kesinleşmiş bir satış değil, talep edilen fiyattır. Steam, ürünün daha düşük bir fiyattan listelenmesine izin verir, ancak gözlemlenen daha yüksek talep fiyatının yayınlanmasına izin vermez. Valve’nin 2016 adresindeki açıklaması, OpenID ve Steam ticaret altyapısını kullanan kumar operatörlerinin varlığından haberdar olduğunu teyit etmektedir. Belirli bir üçüncü taraf pazar yerinin Valve kurallarını ihlal edip etmediği ayrı olarak tespit edilmelidir.\n\nKayıt defterinin tamamını inceleyin →CSFloat JSON ↗Skinport JSON ↗Valve’ın “2016” açıklaması ↗\nDOĞRUDAN CSFLOAT API / TARİHLİ ANLIK GÖRÜNTÜ$13.63M\n\nEn düşük toplam talep edilen değer 241 ürün kategorisi ve 3,395 aktif teklif. Her kategorinin en ucuz satış fiyatı × teklif sayısı olarak hesaplanmıştır. CSFloat’un $100,000 tavan seviyesinde sabitlenmiş dört kategori, bu ihtiyatlı panelin dışında tutulmuştur.\n\nBu rakamın gösterdiği şey\n\nBu teklifler en az $13,631,888.25 Bu sınırlı CSFloat alt kümesi için ilan edilen satış fiyatları. Tavan fiyatlı dört kategori de dahil edildiğinde ortaya çıkan sonuç şudur: $14,231,888.25. Bu bir aktif alım taleplerine ilişkin durum, tamamlanmış satışlar, nakit cirosu, kâr ya da CS2 pazarının tamamı değil.\n\n245 satırlık CSFloat anlık görüntüsünden yeniden hesapla ↗\nPRICEEMPIRE / KAYITLI DEĞERSteam: 39'un 15'incisi\nBirçok mekan, Steam'dan daha yüksek bir dolar tutarı belirtmektedir.\nUUSkins\n$133.8M\nYouPin898\n$127.5M\nBuff.163\n$104M\nMoon.Market\n$100.3M\nWhite.Market\n$89.6M\nBuff.Market\n$86.7M\nSteam\n$31M\n\nGörüntülenen en büyük altı değer ve Steam. PriceEmpire bu rakamları yuvarlar; Steam şunu gösterir: $31M. Görüntülenen dolar değerlerine göre, bu mekanın önünde yer alan 14 adet listelenmiş mekan bulunmaktadır.\n\nPRICEEMPIRE / TEKLİF SAYISISteam: 39'un 1'incisi\nSteam, teklif sayısı açısından hâlâ başı çekiyor.\nSteam\n32,2 milyon\nYouPin898\n5,9 milyon\nC5Game\n4,6 milyon\nHaloSkins\n4,4 milyon\nSkinport\n3,8 milyon\n\nSteam gösterir 32,2 milyon teklifler. Teklif sayısı ile toplam talep edilen değer, farklı sorulara yanıt verir; düşük fiyatlı birçok ilan, toplam sayıyı büyük ölçüde etkileyebilir.\n\nKaynak: PriceEmpire'ın herkese açık karşılaştırması ↗ arşivlendi 2026-09-21 ↗, 2026-09-20 19:03 UTC'de kaydedildi; 39 satırlık eski tarihli veri çıkarma ↗. Rakamlar yuvarlanmış tahminlerdir ve envanter, farklı platformlar arasında çakışabilir. Steam kartında diğer Steam oyunlarına ait öğeler de yer aldığından, kapsamlar birbiriyle tam olarak aynı değildir. Listelenen değerler, satış veya gelir değil, talep edilen fiyatları yansıtmaktadır.\n42\nBAŞKA BİR KAYNAK / STEAMANALYST\nTicari ekosistem gözümüzün önünde.\n\nSteamAnalyst'in pazar yeri dizini arşivlendi 2026-07-19 ↗ Steam'nin yanı sıra 42 üçüncü taraf CS2 pazar yerini listeliyor ve 43 girişten 32'si için güncel fiyat verileri sunuyor. PriceEmpire, kendi dahil etme kriterlerine göre 39 pazar yerini listeliyor. Adı geçen işletmeler, halka açık teklifler, görünür fiyatlar: bu ekonomi incelemeye açıktır.\n\nTAVAN, MEKANİZMADIR: SATIŞ STEAM’DEN ÇIKAR, ÜRÜN ÇIKMAZ.\n\nTek bir lisanslı anlık görüntüde yakalanan beş pazarda, 248 adet CS2 ürün kategorisinin fiyatı, Steam’in yaklaşık $1,800’lık liste tavanının üzerinde, iki veya daha fazla kategoride bağımsız olarak belirlenmiştir — ve bunların her biri Steam’de yer almamaktadır. Aynı anlık görüntü, tüm kataloğu fiyata göre gruplandırdı: Valve’nin pazarında, üst sınırının altındaki ürün kategorilerinden 95.3%, üst sınırının üstündeki kategorilerden ise 1.9% yer alıyor. Bu daralma, azalan talebi yansıtmıyor; tam olarak yayınlanan kurala uyuyor. Bu fiyatlardan satış yapmak için dışarıdan bir alıcı veya pazar yeri gerekir; ancak Steam hâlâ envanteri ve transferi kontrol eder — işlem Valve'ün ödeme sayfasından geçer ve teslimat Valve'ün altyapısında kalır.\n\nSteam Piyasa SSS ↗arşivlendi 2026-09-21 ↗Steam Abone Sözleşmesi ↗arşivlendi 2026-09-21 ↗Beş pazar atlası veri kümesi ↗Menşe beyannamesi ↗Daha önceki CSFloat anlık görüntüsü ↗Skinport özeti ↗PriceEmpire ↗arşivlendi 2026-09-21 ↗SteamAnalyst ↗arşivlendi 2026-07-19 ↗Fiyat farkı kaydı ↗Fiyat merdiveni atlası ↗\n\nC Bölümü — Yasal çerçeveler\nC Bölümü — Yasal çerçeveler · 14. Bölüm · Personelin erişimi\nGüvenlik önlemlerini kim sıfırlayabilir?\nBağlam ve kaynak sınırlamaları\n\nHesap güvenliği, aynı zamanda bir hesabı kurtarabilen, özel kayıtları inceleyebilen veya güvenlik önlemlerini sıfırlayabilen kişilere de bağlıdır. Soruşturma, API’nin kötüye kullanımını takip ettiği kadar bu ayrıcalıklı işlemleri de yakından takip etmelidir.\n\nHesap kurtarma işlemi, bir destek görevlisine hesabı sahibinden devralma yetkisi verir. Valve, bu yetkinin hesapları yanlış kişilere devretmek için kullanıldığını Şubat 2023 ve Kasım 2025 tarihlerinde olmak üzere iki kez yazılı olarak teyit etmiştir. Aralarında otuz üç ay fark olan, aynı kanal üzerinden gerçekleşen olaylar. Aşağıda: bu erişimin değeri, kaynaklı altı vaka ve Valve kayıt defterinin her biri için geçerli olduğu ve kimseye sunulmadığı belirtilmiştir.\n\nKaydedilmiş tanıklık / 9 Mayıs 2025\nHesabın güvenliğini devre dışı bırakan bir kurtarma bileti ve bildirilen $10,000 tutarındaki kayıp\n\nToplanan destek arşivindeki bir kullanıcı, başka bir kişinin kurtarma talebi göndermesinin ardından Steam Destek ekibinin şifreyi sıfırladığını ve hesap korumasını devre dışı bıraktığını bildirmiştir. Yazar, hesabın yıllardır aktif olmadığını, 2016–2017 yıllarından kalma öğeler içerdiğini ve Steam Guard, bağlı bir telefon numarası ile kayıtlı kurtarma kodlarına sahip olduğunu belirtmiştir.\n\n\"Steam Müşteri desteği yine de başka birine hesabıma erişim izni verdi.\"\n\nBirinci şahıs tarafından ileri sürülen iddia, şu kaynakta yer almaktadır: steam_support_tickets_MEGA.json, 110 numaralı kayıt. Yayınlanan gönderinin tamamını okuyun ↗\n\nBu, tek bir kullanıcının başına gelen bir talihsizlik değildir. Aynı yol — bir hesabı daha eski verileri sağlayan kişiye aktaran bir yardım talebi — aşağıdaki kayıt defterinde yer alan her vaka için belgelenmiş giriş yöntemidir ve Valve bunu iki kez yazılı olarak belirtmiştir.\n\nMülk sahibi bu tartışmayı kazanamaz. Geri alma işlemi için ilk CD anahtarı, ilk e-posta adresi, ilk kart bilgisi ve ilk telefon numarası istenir. Bu bilgiler Valve’un veritabanında bulunur ve destek ekibi bu bilgilere erişerek okur — bu bilgilerin on beş yıl öncesine kadar uzandığı bildirilmektedir. Dosyanızın bir kopyasına sahip olan bir kişi, her zaman sizin sunabileceğinizden daha fazla geçmiş bilgisini ortaya çıkarabilir. Hedefler uygunluk kriterlerine göre seçildi: yıllardır kullanılmayan, yüksek değerli ve genellikle ikinci elden satın alınmış hesaplar; böylece hesap sahibi orijinal anahtarı asla bilmedi. Daha sonra hesaplar tamamen silindi; bu da topluluğun bir skin’in izini sürmek için kullandığı ürün geçmişi izini kesti — sıradan bir kullanıcının standart bekleme süresi olmadan gerçekleştiremeyeceği bir silme işlemi.\n\nEn az ayrıcalık / OWASP A01\n\nKurtarma yetkileri, ilgili görevle sınırlandırılmalı, bağımsız olarak denetlenmeli ve kayıt altına alınmalıdır. Kimlerin kimlik bilgilerini sıfırlayabileceğini, Steam Guard öğesini kaldırabileceğini, fatura kayıtlarını okuyabileceğini veya hesap verilerini dışa aktarabileceğini denetleyin. OWASP erişim kontrolü kılavuzu ↗ arşivlendi 2026-09-20 ↗\n\nGeniş erişim desteğiErişim kapsamı riski\nEnvanterin ötesinde.\n\nGeniş kapsamlı erişim yetkisi kötüye kullanılırsa, özel telemetri verileri profil oluşturma, hedefli oltalama ve gözetleme için bir araç haline gelebilir. Potansiyel mağdurlar arasında sıradan kullanıcılar, askeri personel, kamuoyunda tanınan kişiler ve bunların aileleri yer almaktadır. Bu bir tehdit modelidir; kesin izinler için erişim kontrol kayıtlarına ihtiyaç vardır.\n\n01 IP geçmişi ve konum\nIP günlükleri, ağ kullanım geçmişini ve yaklaşık konumu ortaya çıkarabilir. Ancak bu günlükler tek başlarına kesin fiziksel hareketleri belirlemez.\n02 Cihaz parmak izi belirleme\nToplandığı ve erişilebilir olduğu durumlarda, cihaz tanımlayıcıları oturumları ve hesapları birbirine bağlayabilir.\n03 Etkinlik telemetrisi\nGiriş zaman damgaları ve oturum kayıtları, herkese açık bir profilde görünmeyen etkinlikler de dahil olmak üzere, rutinleri ortaya çıkarabilir.\n04 İletişim ve irtibat bilgileri\nSaklanan mesajlara veya kişi bilgilerine erişim, profil oluşturma ve sosyal mühendislik faaliyetlerinin kapsamını genişletecektir.\n05 Kimliğin ortaya çıkarılması\nOrijinal e-posta, telefon ve ödeme kayıtları, takma adlı bir hesabı bir kişiyle ilişkilendirebilir.\n06 Verilerin yeniden satışı ve hesap verebilirlik\nDışa aktarılan hedef listeleri, hedefli dolandırıcılık faaliyetlerine zemin hazırlayabilir. Faili, erişim konumunu, alıcıları ve para transferlerini tespit edin; konum bilgisi tek başına ne erişimi ne de yasal dokunulmazlığı kanıtlar.\n\nValve, kendi belgelerinde IP günlüğü, cihaz bilgileri, ödeme kayıtları ve üçüncü taraf destek sağlayıcılarını açıklamaktadır. Gizlilik Politikası, Madde 3 ve 5.2 arşivlendi 2026-09-21 ↗. Bu politika, üçüncü tarafların destek erişimine izin vermektedir — hangi yüklenicinin hangi kategoriye, ne zaman ve hangi yetki kapsamında eriştiğini gösteren denetim kaydı ise açıklanmamıştır.\n\nBölüm 14.1 · Kayıt Defteri · Haziran 2022 → Kasım 2025 · Her şeklin kaynağı belirtilmiştir\nValve, otuz üç ay arayla iki kez kapıyı açtı. Kapı hiç kapanmadı.\n\nSteam’un kendi yardım talebi kanalı aracılığıyla ya da bu kanalın koruduğu kimlik bilgileri yoluyla hesapların ele geçirildiği altı vaka bildirildi. Her bir tutar, alıntı yapılan kaynağın yayınladığı rakamdır ve her kaynağın adı belirtilmiştir. Altı vakadan ikisinde kayıplar tamamen telafi edildi. Bu vakalar ile diğerleri arasındaki fark, ne olduğu değil, kimin izlediği idi.\n\nValve, yazılı olarak — Şubat 2023\"Söz konusu öğeler, bir destek talebi yoluyla ele geçirilmiş bir hesaptan alındıkları için hesabınızdan kaldırılmıştır; bu durumun sorumluluğu CS:GO ekibine aittir. Takas işlemlerini iptal ettik ve bu öğeleri, bunları alan tüm hesaplardan kaldırdık.\"Steam HFB’nin gönderilerinin alıcılarına verilen yanıt, şu kaynak tarafından aktarılmıştır: Dexerto, 21 Şubat 2023 ↗ arşivlendi 2025-08-18 ↗\nValve, yine yazılı olarak — Kasım 2025 · 33 ay sonra\"Yardım talebinizi işleme alan bir destek teknisyeni, prosedürlerimize uymamış ve bu durum, hesabınızın başka bir kişiye geri verilmesine neden olmuştur. Bu hata nedeniyle özür dilerim.\"Steam Hawkeye337’ye verilen yanıt, alıntı: Dexerto, 14 Kasım 2025 ↗\n21 Haziran 2022\nHFB — oyundaki en geniş ürün yelpazesi$2,000,000+ · Şubat 2023’teki takip değerlendirmesinde $3,000,000+ seviyesine yükseltildi\n\nYedi adet Souvenir AWP Dragon Lores ve 1 numaralı Mavi Mücevherli Karambit; sadece bu bıçağın değeri yaklaşık $1.26 milyon. Hesap üç yıldır kullanılmıyordu ancak mobil kimlik doğrulama uygulaması hâlâ aktif durumdaydı; yine de destek ekibinin kurtarma prosedürü aracılığıyla e-posta adresi ve şifre değiştirildi.\n\nEşyalar gitmeden önce para kalmıştı. Bildirildiğine göre $200,000+ Satış gelirlerinin bir kısmı, nakit ve kripto para ile ödeme yapılan bir pazar yeri olan market.csgo.com üzerinden zaten çekilmişti. Bir işlemin iptal edilmesi, skin’in iade edilmesini sağlar. Ancak bir kişinin daha önce hesabına yatırdığı nakit para iade edilmez.\n\nVe düzeltme işe yaramadı. Bir alıcı, “Souvenir Dragon Lore” adlı eşyasını oyun içi bir depolama birimine taşıdı. Valve’un geri alma komut dosyası kendi konteynerinin içini göremediğinden, sahibine yeni bir kopya verdi ve gizli olanı olduğu gibi bıraktı — Valve bir $130,000 Bir hırsızlığı geri almaya çalışırken söz konusu ürün. Ürün kimlik numaralarının eşleştirilmesi ve topluluk tarafından yapılan ihbarlar sayesinde tespit edildi ve bir ay sonra, Temmuz 2022’de silindi. Alıcıya geri ödeme Valve tarafından değil, BUFF tarafından yapıldı. Bu kadar geçici bir acil durum düzeltmesi bir kontrol mekanizması değildir; bu, bir platformun kontrolü elinde olmadığında yaptığı şeydir.\n\nDexerto, 21 Haziran 2022 ↗ arşivlendi 2022-07-02 ↗ · Kaspersky ↗ · her bir için nakit çıkış tutarı Esportfire, 22 Haziran 2022 ↗ arşivlendi 2026-05-15 ↗, orada birden fazla Twitter kaynağına atfedilen · aşağıdakilere göre yinelenen ve silinen Esportsbetting, 14 Temmuz 2022 ↗\n\nYenilenmişAlım satım işlemleri tersine döndü. Ürünler, tam fiyatını ödeyen kişilerin stoklarından geri çekildi.\n14 Ağustos 2022\nCS.Money — platformun kendi botları$6,300,000 · 19,000+ kaplama · ilk tahmin $1.6M\n\nSaldırganlar, ticaret platformundaki ticaret botlarının mobil kimlik doğrulama dosyalarını ele geçirip içlerini boşalttı; ardından izleri karıştırmak için ele geçirdikleri verilerin bir kısmını tanınmış tüccarlara gönderdi. Topluluk araştırmacıları, bunu haritalandırdı Birkaç saat içinde 55 saldırgan hesabı ve bunları yayınladı.\n\nValve hiçbir şeyi geri almadı. Bunun nedeni, üçüncü taraf bir sitenin Steam’in dışında yer almasıydı — hırsızlığın baştan sona üzerinde yürütüldüğü envanter, ticaret API’si ve hesap sistemine sahip olan Steam ile aynı site.\n\nEsportfire, 14 Ağustos 2022 ↗ arşivlendi 2025-11-15 ↗\n\nReddedildiGeri dönüş olmadı. Zarar, platform ve kullanıcılarına kaldı.\nBildirildi\n21 Şubat 2023\nQkss — aynı kapı, aynı oyuncu$1,000,000+\n\nHFB ile aynı şekilde, aynı aktör tarafından ve aynı destek talebi yoluyla bildirildi. HFB, sekiz ay önce tamamen çözülmüştü. Qkss ise çözülmemişti.\n\nTek yol. İki cevap. Yayınlanan kayıtlarda, izleyici sayısının dışında bu iki vakayı birbirinden ayıran hiçbir unsur bulunmamaktadır.\n\nDexerto, 21 Şubat 2023 ↗ arşivlendi 2025-08-18 ↗\n\nReddedildiRestore edilmemiştir.\nBildirildi\nŞubat 2023\nİçeriden bilgi ticareti — bir yıllık süreç≈ $320,000 · yaklaşık bir yıllık bir süreyi kapsar; stok değerlemesi değildir\n\nDestek birimi, hesap geçmişine şu tarihe kadar erişim sağladı: 15 yaşında — ilk CD anahtarı, ilk e-posta, ilk kart. İşte kurtarma sürecinde tam da bu kanıtlar talep edilir; bu yüzden veritabanını elinde bulunduran kişi, hesap sahibi ile arasındaki tartışmada her zaman galip gelir.\n\nBlog yazarı Mzkshow, içeriden bir operatör olan \"Steam Help\" ile işbirlikçisi \"Alexander\"ın, $100k'tan fazla skin barındıran aktif olmayan hesapları nasıl hedef aldığını ortaya çıkardı. iBUYPOWER ve Titan Katowice 2014 holografik skinlerini taşıyan çalınan bir M4A4 Howl, şu fiyata satıldı: $35,000 ve sonunda, bunu bilmesinin imkânı olmayan NAVI’den Valerii \"b1t\" Vakhovskyi ile karşı karşıya kaldı. Valve’nin müdahalesinin ardından, yüklenici Steam destek ekibinin tamamını işten çıkardı.\n\nVKPlay ↗ · Lis-Skins ↗ · Escorenews (RU) ↗ · Dexerto (İng.) ↗\n\nKayıt yokValve, bu durumun kaç hesabı etkilediğini hiçbir zaman açıklamadı ya da etkilenen kişilere bu durumu bildirmedi.\nBildirildi\n2 Aralık 2024\n\"Matvey\" — işten çıkarmalardan sonra$13,000\n\nHesap sahibinin kendisinin bile eşleştiremediği hesap bilgilerini sağlayan bir kişiye geri ödeme yapılmıştır. Yüklenicinin Steam destek masasını boşaltmasından iki yıl sonra, aynı yöntem yine aynı sonucu vermiştir.\n\nArşivlenmiş gönderi, 2 Aralık 2024 ↗ arşivlendi 2025-08-05 ↗ · kaynak satırları ve hash değerleri ↓\n\nReddedildiRestore edilmemiştir.\n13 Kasım 2025\nHawkeye337 (Mark Spurlock) — ve ikinci itiraf≈ $300,000–$500,000 · Katowice 2014 holo koleksiyonunun tamamı\n\nSaldırgan şunları talep etti: 1 bitcoin ve koleksiyonu yok etmek için Negev'lere aktarmaya başladı. Steam Destek ekibinin yazılı yanıtı, yukarıdaki ikinci itiraf niteliğindedir: Bir teknisyen yardım talebini ele aldı, prosedürü uygulamadı ve hesabı başka birine devretti.\n\nSorunun çözülmesini sağlayan şey, beslemeydi. X'te Valve etiketli paylaşımlar yayınlandıktan birkaç saat sonra, hesap geri alındı ve tüm çıkartmalar eski haline getirildi. Qkss'nin o kadar takipçisi yoktu.\n\nSkin.club ↗ · Dexerto ↗ · Esportfire ↗ arşivlendi 2025-12-17 ↗\n\nYenilenmişHaber gündeme girmesinden birkaç saat sonra geri çekildi.\nDefterde yazan şey, tek bir vakanın bile ifade edemediği bir şeydir.\n\nBu güzergâh hiçbir zaman kapatılmadı. İlk kayıt tarihi Şubat 2023, ikincisi ise Kasım 2025’tir — aralarında otuz üç ay fark var, bu süreçte yüklenicinin toplu işten çıkarmaları, belgelenmiş bir tekrar vakası ve arada meydana gelen $6.3 milyonluk platform ihlali de yaşandı. Bu kayıt defterindeki ilk hırsızlıktan itibaren sayarsak, kanal üç yıl beş ay. 2023'te ne düzeltilmiş olursa olsun, yardım talebi Kasım 2025'te yine de bir hesabı yanlış kişiye yönlendirdi — Valve'un kendi ifadesiyle.\n\nTazminat, zarara değil, dikkatin yönlendirilmesine odaklandı. Geri getirildi: Oyundaki en büyük envanter ve başlığı trend olan koleksiyoncu. Reddedildi: $1,000,000, $6,300,000, $13,000. Valve, uyguladığı kuralı hiçbir zaman yayınlamadı; çünkü yayınlanan bir kuralın bu üçünü açıklaması gerekirdi.\n\nKimseye söylenmedi. Ne veritabanından hesap geçmişleri okunan kullanıcılar, ne bir denetim kurumu, ne de malları iyi niyetle satın alıp daha sonra geri alınmasına maruz kalan piyasa. Herhangi bir ihlal bildirimi, olay raporu ya da etkilenen hesap sayısına dair bir bilgi yok — ve para olarak kalan gelir, nakit ve kripto para ile ödeme yapan platformlar aracılığıyla. Steam’dan çıkan paranın ardından bir işlem iptali gerçekleşemez.\n\nValve, yukarıdaki her satır için destek denetim izini, kurtarma bileti günlüğünü ve işlem kaydını içerir. Bunların hiçbiri sunulmamıştır. Kendi kopyanızı isteyin →\n\nNDA sorusu\nGizlilik, teknik hesap verebilirlikle bir arada olmalıdır.\n\nGizlilik anlaşmalarını fiili izinler, ihracat kontrolleri, sıfırlama onayları ve erişim günlükleriyle karşılaştırın. Hazır bir yanıt, kurtarma sürecinin kendisinin kötüye kullanıldığına dair bir iddiayı ortadan kaldıramaz.\n\nGDPR’nin 28. ve 32–34. maddeleri\n\n33. madde, veri sorumlusuna kişisel veri ihlalini denetim makamına bildirmek için 72 saat süre tanır; 34. madde ise, etkilenen kişiler için risk yüksek olduğunda onlara bilgi verilmesini zorunlu kılar. Valve, destek kanalının hesapları — hesap geçmişi, fatura kayıtları ve diğer tüm bilgileri — yanlış kişilere ilettiğini iki kez yazılı olarak teyit etmiştir. Her iki madde kapsamında da herhangi bir bildirim yayınlanmamıştır ve etkilenen hiçbir kullanıcı böyle bir bildirim aldığını bildirmedi. Yönetmeliği okuyun ↗ arşivlendi 2026-09-20 ↗\n\nTalebinize destek erişimini ekleyin →\nC Bölümü — Yasal çerçeveler · 15. Bölüm · Ticari ölçek\nParanın izini sürün. İşlemleri birbirinden ayırın.\nBağlam ve kaynak sınırlamaları\n\nPara akışları birbirinden ayrıldığında, ticari kullanım meselesi daha belirgin hale gelir. Üçüncü taraflara yapılan mal transferleri, Valve’un ana satışları ve dışarıya yapılan nakit çıkışları birbirinden farklı işlemlerdir.\n\nÜrün, Valve'a aittir. Stok, Valve'dir. Aktarım, Valve'nin sunucularında gerçekleştirilir. Sadece ödeme başka bir yerde gerçekleştiriliyor — bu, bir kişinin para transferi yapan kuruluş olup olmadığını belirleyen adımdır ve Valve’ın faaliyet göstermediği tek adımdır.\n\nGelir mekanizması\nParanın gerçekte nereye aktığı.\nÜç yol / tek ürün ekonomisi\n01 / HesapKullanıcı envanteri\n\nSteam'da bulunan öğeler\n\n02 / TransferP2P ticareti\n\nKullanıcı ↔ bot veya kullanıcı ↔ kullanıcı\n\n03 / ÖdemeHarici platform\n\nSite bakiyesi veya ödenecek tutar Steam\n\nDolaşımEkonomik itici güç, transfer ücretinin ötesine uzanır\n\nSteam, dış pazarların kullandığı envanter ve aktarım altyapısını sağlar. Soruşturmanın ekonomik argümanı, yeniden satış likiditesi ve tekrarlanan talebin, kasalar, anahtarlar ve yedek parçalara yönelik harcamaları sürdürdüğü ve bunun da Topluluk Pazarı’ndaki sonraki satışlardan komisyon elde edilmesini sağladığı yönündedir. Doğrudan P2P transferlerinde Topluluk Pazarı komisyonu alınmaz; ancak bu muhasebe gerçeği, daha geniş kapsamlı faydayı kesinleştirmez. Valve, süreç boyunca hesap erişimi ve ticaret kısıtlamaları üzerindeki kontrolünü elinde tutar.\n\n01 / İkincil talepLikidite ve yeniden satış değeri\n\nDış ticaret ve kumar talebi\n\n02 / Birincil harcamalarAnahtarlar, kılıflar ve kapsüller\n\nSunulduğu durumlarda Valve’dan yapılan alışverişler\n\n03 / GelirBirincil satış gelirleri\n\nAyrıca, piyasa satışlarından elde edilen gelir üzerinden alınan ücretler\n\n5% + 10%Steam + Topluluk Pazarı satışlarında CS2 ücreti\n\nAraştırmanın ekonomik sonucu: likit ikinci el pazarları, yeni ürünlere yönelik harcamaları teşvik edebilir. Bilinen 15% işareti, asgari tutarlara ve yuvarlama kurallarına tabi olan piyasa ücret oranlarını birleştirir; bu, her dış ticarete uygulanan bir vergi değildir.\n\nValve'nin Topluluk Pazarı ücret tablosu ↗ arşivlendi 2026-09-21 ↗. 25 Şubat 2026 tarihinde New York Başsavcısı bir dava açtı arşivlendi 2026-09-01 ↗ Ücretli ganimet kutularının harici nakit yeniden satış ve kumarın yol açtığı zararla bağlantılı olduğu iddiası — bu dosyanın teknik altyapı açısından belgelediği bağlantının aynısı. Bu şikayet bir iddiadır, bir bulgu değildir; burada alıntılanmasının nedeni, bir eyalet kolluk kurumunun bu dosyada sorulan soruyla bağlantılı bir soruyu gündeme getirmiş olmasıdır: kamuoyuna yapılan açıklamalarla örtüşen uygulama kayıtları nerede?\n\n01 / GirişKripto para yatırımı\n\nHarici hizmet ve cüzdan kayıtları\n\n02 / DönüştürmeDenge → görünümler\n\nSteam işlem yoluyla teslim edilen ürünler\n\n03 / ÇıkışDış fiat satışı\n\nSatıcı, alıcı ve ödeme sağlayıcısı\n\nKYC mi?Her devir teslimde kontrolün kime geçtiğini belirleyin\n\nAraştırılması gereken yol budur; yerel bir Steam API nakit dönüştürme hizmeti değil. KYC gerektirmeyen bir nakit çekme işlemi onaylamadan önce, her bir harici operatörde kimlik doğrulamalarını, saklama işlemlerini, işlem kimlik numaralarını ve ödeme alıcılarını belgelendirin.\n\nAmerika Birleşik Devletleri / Banka Gizliliği Kanunu\nÖnce faaliyeti, ardından yükümlülüğü sınıflandırın.\n\nFinCEN, para transferlerini işletmenin faaliyetlerine göre değerlendirir. Dönüştürülebilir sanal para birimini kabul etmek ve aktarmak, geçerli tanımlara ve istisnalara tabi olarak para hizmetleri yükümlülüklerini tetikleyebilir. Valve'un Steam Cüzdanı, fonları kabul eder ve bunları oyun içi öğelere dönüştürür; bu öğeler daha sonra üçüncü taraf operatörler aracılığıyla gerçek para birimine çevrilir. Öğe ve aktarımı Valve'in altyapısı üzerinden gerçekleştirilir; nakit çıkışı ise bu altyapı üzerinden yapılmaz ve bu döngünün herhangi bir kısmının para transferi tanımlarına uyup uymadığı, burada varılacak bir sonuç değil, FinCEN'in sınıflandırma konusudur.\n\nFinCEN FIN-2019-G001, 1–2. maddeler, 5.1 ↗ arşivlendi 2025-07-11 ↗\n\nAvrupa Birliği / kara para aklama\nGelirlerin izlenmesi, bilgi ve destek.\n\n(AB) 2018/1673 sayılı Direktif, suç gelirleriyle ilgili kasıtlı kara para aklama ve bu suçlara iştirak eylemlerini kapsamaktadır. Soruşturmanın odak noktası, Valve’nin, 13 Temmuz 2016 tarihinde bu kullanımı kamuoyuna açıkladığı tarihten sonra, kendi ticaret ve OpenID altyapısını kullanan operatörler hakkında ne bildiği ve bu konuda ne tür önlemler aldığıdır. Valve, operatör bazında herhangi bir yaptırım kaydı yayınlamamıştır; bu soruyu yanıtlayacak olan, bu dosya değil, söz konusu kayıttır.\n\nAB ceza hukuku çerçevesi ↗\n\nAMLD6 terminolojisi: Yukarıdaki ceza hukuku direktifi, AMLD6 olarak da bilinen (AB) 2024/1640 sayılı Direktif’ten farklıdır. İkincisinin, belirli istisnalar dışında, genel uyum süresi 10 Temmuz 2027’dir. 78. madde ↗ arşivlendi 2026-08-30 ↗\n\nC Bölümü — Yasal çerçeveler · 16. Bölüm · Bildirim, yanıt, sorumluluk\nDijital Hizmetler Yasası: bilgiyi kayıt altına almak\nBağlam ve kaynak sınırlamaları\n\n16. Madde uyarınca yapılan bildirimin iki unsuru, bu dosya yerine bildirimde bulunan kişiye aittir: bildirimde bulunan kişinin kendi bilgileri ve bilgilerin doğru olduğuna dair iyi niyet beyanı. Maddenin gerektirdiği diğer her şey — gerekçelendirilmiş açıklama ve tam elektronik konum — Bölüm 3'te ve rota kaydında, kaydedilmiş yanıtlar ve hash değerleriyle birlikte belirtilmiştir; böylece herhangi bir taraf bunu sunabilir. Yasanın kendisiyle ilgili iki sınırlama daha bulunmaktadır: barındırma muafiyetini kaybetmek, tek başına başka herhangi bir yasa kapsamında sorumluluk doğurmaz ve 52. Maddenin (3) numaralı fıkrasındaki 6% rakamı, Valve'e karşı uygulanan bir ceza değil, yasal bir üst sınırdır.\n\nDSA kapsamında, bir barındırma hizmeti sağlayıcısı, ancak konuyla ilgili kesin bilgiye sahip olduğu halde harekete geçmemesi durumunda sorumluluk muafiyetinden yararlanamaz. Bu dosya, söz konusu bildirimdir. Bu belge, sunucuları, tarihleri, kaydedilmiş yanıtları ve karma değerleri belirtmektedir. Yayınlanmasından itibaren asıl soru artık Valve’nun bunu bilip bilmediği değil; Valve’in bundan sonra ne yaptığıdır.\n\n01Temmuz 2016 / dosya sergisi\nOn günlük bir talep.\n\nYukarıda yeniden oluşturulan bildirim, soruşturmadaki yaptırım karşılaştırmasının tarihsel başlangıç noktasıdır.\n\n0217 Şubat 2024 / genel başvuru\nDSA zaman aralığı.\n\nTarihsel davranışları, ilgili DSA yükümlülüklerinin geçerli olduğu dönemdeki davranışlardan ayırın.\n\n03On yıl / orijinal dosya anlık görüntüsü\nSüre için bir bildirim dizisi gereklidir.\n\nTemmuz 2016’dan bu yana geçen süre (bkz. Bölüm 11), bir dosya ölçütüdür. Bu, on yıllık yerleşik DSA ihlalleri anlamına gelmez. Her bir bildirimi belirli bir maddeye, ilgili yasaya, teslimat kanıtına ve cevaba bağlayınız.\n\n52. Maddenin 3. fıkrası / yasal üst sınır6%\nyıllık dünya çapındaki cirosunun\n\nDSA yükümlülüklerinin ihlali durumunda, hizmet sağlayıcının bir önceki mali yılı esas alınarak belirlenen azami para cezası. Bu, yasal bir üst sınırdır; Valve’a karşı uygulanan bir ceza değildir.\n\n6., 8. ve 16. maddeler / hukuki değerlendirme\n\nİlgili barındırma hizmetleri söz konusu olduğunda, belirli bir bilgiye sahip olunması ve derhal harekete geçilmemesi, barındırma muafiyetinin ortadan kalkmasına neden olabilir. Yeterince kesin bir bildirim, söz konusu içerik hakkında bilgi sahibi olunduğunu ortaya koyabilir. DSA genel bir izleme yükümlülüğü getirmez; muafiyetin ortadan kalkması, tek başına başka bir yasa kapsamında sorumluluk doğurmaz.\n\nDSA: 6., 8., 16., 52., 53. ve 93. maddeler ile 17. gerekçe ↗ arşivlendi 2026-09-20 ↗\n\nArşivlenmiş şikayetleri incele ↗Hesap zaman çizelgesini oluştur →Kapsamlı hukuki ve ekonomik analiz →\nC Bölümü — Yasal çerçeveler · 17. Bölüm · Kimlik, yaş, ticari erişim\nReşit olmayanlar: Steam ile oturum açma, yaş kontrolü değildir\nBağlam ve kaynak sınırlamaları\n\nBu dosyada hiçbir yerde reşit olmayan kişilerin verileri yer almamaktadır ve bu tür veriler toplanmamıştır: yazarlar, adı geçen hiçbir platforma kayıt olmamış, bilgi yüklememiş veya oturum açmamıştır. Bu bölüme dayanarak çalışma yapacak kişiler, çocuklarla ilgili kanıtları gizli tutmalı ve kamuya açık delillerden kimlik bilgilerini gizlemelidir. COPPA, burada genel bir kumar yaşı kuralı olarak değil, kendi kapsam koşullarına (hedef kitle, fiili bilgi, toplanan kişisel veriler) sahip bir çocuk gizlilik yasası olarak atıfta bulunulmaktadır; 2026 tarihli New York şikayeti, bir eyalet makamı tarafından yapılan bir iddiadır, bir tespit değildir.\n\n\"Steam ile giriş yap\" seçeneği, bir hesabın var olduğunu kanıtlar. Bu, yaş konusunda hiçbir şeyi kanıtlamaz — ve bu sitelerde bu, bir çocuk ile para yatırma işlemi arasındaki tek engeldir. Şunu dikkatle okuyun: Bölüm 3.1: Steam istemcisi içinde, bir tarayıcının göstereceği uyarı hiçbir zaman tetiklenmez; dolayısıyla çocuk bu uyarıyı asla görmez.\n\nSteam OpenID’nin sunduğu özelliklerHesap kimliği\n\nGiriş yapmak veya bir hesabı bağlamak için kullanılan, doğrulanmış bir SteamID.\n\n≠\nOperatörün belirlemesi gereken hususlarKatılım şartları\n\nYaş, yetki alanı ve gerekli kimlik kontrolleri.\n\nTeknik dayanak: Steamworks OpenID belgeleri ↗ arşivlendi 2026-09-21 ↗. Belgelenmiş kimlik beyanı, kullanıcının yasal olarak kumar oynayabileceğine dair bir tasdik niteliğinde değildir.\n\nCOPPA / 13 yaşın altındaki çocuklar\nİşleciyi ve veriyi belirleyin.\n\nCOPPA, kapsam dahilindeki çocuklara yönelik hizmetler ile 13 yaşın altındaki çocuklardan kişisel bilgi topladıklarını fiilen bilen hizmetler için geçerlidir. Bu, çocuklara yönelik bir gizlilik yasasıdır; genel bir kumar oynama yaşı kuralı değildir. Hedef kitleyi, toplanan kişisel verileri, bu konuda bilgi sahibi olma durumunu ve ebeveyn onayı sürecini belirleyin.\n\nFTC: COPPA gereklilikleri ↗ arşivlendi 2026-09-21 ↗\n\nKorunması gereken kanıtlar\nGiriş yapma aşamasından para yatırma aşamasına kadar olan süreci kaydedin.\n\nSitenin yaş sınırlaması, kayıt metni, katılım koşulları, ödeme süreci ve şikayet geçmişini koruyun. Her operatörü ayrı ayrı değerlendirin. Çocuklarla ilgili tüm kanıtları gizli tutun ve kamuya açık delillerden kimlik bilgilerini gizleyin.\n\nBu konuyla ilgili bir kamu yaptırım kaydı şudur: 2026 New York Şikayet Duyurusu arşivlendi 2026-09-01 ↗, bu karar ücretli ganimet kutularının genç kullanıcılara zarar verdiğini iddia etmektedir. Bu, COPPA kapsamında bir tespit değildir.\n\nC Bölümü — Yasal çerçeveler · 18. Bölüm · GDPR’nin 15. maddesine dayalı talep\nİstek. Yanıt. Eksik karşılaştırma.\n\nDört şey istedi; bunlardan biri, hesabına API anahtarı ekleyen kişinin kimliğini ortaya çıkaracak günlük kaydıydı. Üç gün sonra, bilet, bunların hiçbirini içermeyen bir sayfaya yönlendiren bir bağlantı ile kapatıldı — ve metnin sonunu oluşturan cümle, Valve’un kendi avukatları tarafından çürütülmüştür.\n\nBu hesap kime ait? · Kaynak ve Sınırlar\n\nBu ekran görüntüleri PhishDestroy'a ait değildir. Bunlar sıradan bir Steam hesap sahibinden geliyor — bu proje kapsamında yürütülen kısa bir ankete katılan ve talebi bizzat kendisi sunan, ekran görüntülerini sağlayan bir katılımcıdan. Hesap ona ait, bilet ona ait ve yazışmalar onunla Steam Destek ekibi arasında gerçekleşmiştir. Bu proje, talebi sunmamıştır, platformda herhangi bir hesaba sahip değildir ve bu biletin taraflarından biri değildir.\n\n16 Eylül 2026 tarihinde, özellikle API anahtarı kayıt günlükleri, IP adresleriyle birlikte oturum açma geçmişi, cihaz yetkilendirme geçmişi ve işlem geçmişini talep eden bir GDPR/CCPA Madde 15 veri sahibi erişim talebinde bulundu. 17 Eylül’de “Logen” adlı temsilci, onu self-servis Hesap Verileri sayfasına yönlendirdi. 18 Eylül'de, talep ettiği kategorilerin o sayfada bulunmadığını belirtti ve konunun Gizlilik Ekibi veya Veri Koruma Görevlisi'ne (DPO) iletilmesini istedi. 19 Eylül'de “Kal” adlı müşteri temsilcisi, aynı yönlendirmeyle talebi kapattı. Her iki ekran görüntüsü de aşağıda yer almaktadır (talep sahibinin e-posta adresi gizlenmiştir; SHA-256 steam_tos_assets/screenshot-manifest.json).\n\nO, sıradan bir nedenden ötürü bu talebi yapmak için en uygun kişidir: Bu hesapta, kendisinin oluşturmadığı ve şu adrese kayıtlı bir Steam Web API anahtarı bulunmaktadır: localhost. Ne zaman kurulduğu bilinmemektedir — ne ona ait, ne de Valve’nin ona sağladığı herhangi bir şeyden kaynaklanmıyor; çünkü bunu tarihlendirebilecek tek kayıt, API anahtarı kayıt günlüğüdür ve bu tam da kapatma işleminin gizlediği kategoridir. Anahtar yeni değil: aynı nedenden ötürü, onun bundan haberdar olmasından önce, ölçülemez bir süre öncesine dayanıyor.\n\nDiğer hesap sahipleri de aynı talepte bulunuyor. Alınan her türlü yanıt, kategorileri onaylasa da reddetse de, bu ikisiyle aynı koşullarda — bilet numarası, yakalama tarihi, SHA-256, talep sahibinin kimliği gizlenmiş olarak — buraya eklenecektir.\n\nBu proje, biletin neden kapatıldığı konusunda herhangi bir görüş belirtmemektedir. Bilette herhangi bir neden belirtilmemiştir ve burada da böyle bir neden çıkarılmamaktadır.\n\nİstek. Yanıt. Karşılaştırma.KAYDI TAKİP EDİN\nAdım 3 / 3\n\nDört adet isimlendirilmiş kategori talep etti. Kendisine yönlendirildiği Hesap Verileri sayfası, Valve’un kendi self-servis dışa aktarım özelliğidir ve bu proje, başka birinin hesabına ait içeriği listeleyemez — dolayısıyla burada kategoriler bazında tam bir karşılaştırma yayınlanmamaktadır. Kayıtlarda yer alan, 18 Eylül tarihli, kategorilerin mevcut olmadığına dair yaptığı açıklama ve 19 Eylül tarihli, bu konuyu ele almadan yönlendirmeyi tekrarlayan kapanış bildirisidir.\n\nTALEPBelirli kategorilerAPI anahtarı, oturum açma, cihaz ve işlem kayıtları\nYANITHesap Verileri ReferansıDestek değişimini inceleyin\nSINAVNeler teslim edildi?İstenen her bir kategoriyi karşılaştırın\nEkran 1/2 — Talep (16 Eylül) ve ilk yanıt, temsilci \"Logen\" (17 Eylül)\nGDPR ticket HT-2YBP-F7JP-D4VB — request and first response\nKaynak: help.steampowered.com, bilet numarası HT-2YBP-F7JP-D4VB · 16–17 Eylül 2026 tarihinde kaydedilmiştir · talep sahibinin e-posta adresi gizlenmiştir 2026-09-21 · Dosya: gdpr-ticket-1.png · SHA-256 da940c731ab9869d226e9d06ccc8a1b393738766b7b0c445a56662623e025a66 (screenshot-manifest.json).\nEkran 2/2 — Sorunun üst düzeye taşınması talebi (18 Eylül) ve kapanış, temsilci “Kal” (19 Eylül)\nGDPR ticket HT-2YBP-F7JP-D4VB — escalation request and closure\nKaynak: help.steampowered.com, bilet numarası HT-2YBP-F7JP-D4VB · 18–19 Eylül 2026 tarihinde kaydedilmiştir · Dosya: gdpr-ticket-2.png · SHA-256 44844ea7b251f7fd7d79f87ee1578a846606a97b9659d3a53b322120c422219b (screenshot-manifest.json).\nKapanış yanıtı, 19 Eylül (kelimesi kelimesine):\n\"Steam'da saklanan veriler, Hesap Verileri sayfanızda zaten bulunabilir. Destek ekibinin sunabileceği başka bir bilgi Steam olmadığından, Bu talep kapatılacaktır.\"\nVeri sağlanmadı · reddedilme için yasal dayanak belirtilmedi · üst makama iletilme sonucu gösterilmedi\nBu cümle yanlıştır ve Valve'un kendi avukatları bunu kanıtlamaktadır. Avukatın 1 Ekim 2025 tarihli mektubunun 1.9. paragrafında, bir cihazı düzinelerce hesapla ilişkilendiren cihaz düzeyinde bir korelasyon açıklanmaktadır (Ek A). Aynı cevapta, saklanan kayıtlardan oluşan 830 sayfa yer alıyordu (Ek B). Bunların hiçbiri Hesap Bilgileri sayfasında yer almıyor.\nBu hesap neden API anahtarı günlüğünü istedi?\n\nO, bu dört kategoriyi rastgele seçmedi. O... localhost Hesabındaki anahtar şudur: bir komut dosyasının işareti; geliştirici sayfasına gerçek bir alan adını yazan bir kişinin değil (5. Bölüm, 6. Bölüm). Kimin tarafından ve nereden oluşturulduğunu gösteren tek kayıt, API anahtarı kayıt günlüğüdür. Bu, onun ilk istediği şeydi. İşte bu bilgi, kapatma kararıyla gizlendi.\n\nKaynak: Hesap sahibi, bu projenin anketi sırasında. Yukarıdaki bilet ekran görüntüleri karma değerlere dönüştürülmüştür; anahtar sayfası yayınlanmamıştır.\n\nDeğerlendirme · PhishDestroy\n\nSorunun hâlâ çözülmemiş olduğu halde bir biletin kapatılması burada bir tesadüf değildir. Bu, olağan bir sonuçtur. Biz 16,319 saklanan şikayet ve destek kayıtları ve 354 adet tekrarlardan arındırılmış destek yazışması bunlardan derlenmiştir. Bu bilet, bu tür biletlerin aldığı şekli gösteren, tarihli ve tüm ayrıntılarıyla kaydedilmiş bir örnektir.\n\nDestek Bileti — SaklanmışHT-2YBP-F7JP-D4VB\nTalep türüGDPR Madde 15 – Veri Sahibi Hakları Talebi (DSAR)\nBilet durumu19 EYLÜL 2026'DA KAPALI — VERİ SAĞLANMAMIŞTIR\nBorsadaki aracılar\"Logen\" (17 Eylül), \"Kal\" (19 Eylül)\nDosyalandı16 Eylül 2026\nİstenen verilerBu hesaba bağlı Web API anahtarını kim kaydetmiştir ve hangi IP adresinden / cihazdan / zaman damgasından?\nAtıfta bulunulan hukuki dayanakGDPR Madde 15 — Kişisel verilere erişim hakkı\nYasal çerçeve:12. Maddenin (3) numaralı fıkrası, veri sorumlusuna bildirimin alınmasından itibaren bir aylık süre tanır (gerekçeli olarak uzatılabilir). Bu süre, yayınlandığı tarihte henüz dolmamıştı ve bu dosyada süre ihlali iddiası yer almamaktadır. İtiraz, içeriğe yöneliktir: Son yanıtta bir self-servis sayfasına bağlantı verilmiş olmakla birlikte, adı geçen dört veri kategorisinin sunulduğu gösterilmemiştir; ayrıca, veri sorumlusu harekete geçmeyi reddederse, Madde 12(4) uyarınca gerekçelerini ve şikayet kanallarını belirtmesi gerekmektedir. Son yanıtta bunların hiçbiri yer almamaktadır.\nBu verilerin önemi nedir?\n\nWeb API anahtar olay günlüğü, bir üçüncü tarafın çalınan bir oturum çerezi kullanarak bir anahtar kaydetmiş olup olmadığını gösteren kayıttır — bu dosyanın arşivinde saklanan envanter hırsızlığı şikayetlerinde açıklanan mekanizma. Bir API anahtarını kimin, hangi IP adresinden ve hangi zaman damgasıyla kaydettiğinin açıklanması:\n\nMağdurun, API oluşturulurken kullanılan IP adresini kendi oturum açma geçmişiyle karşılaştırmasına izin verin\nBilinen kimlik avı / kumar bot altyapısıyla bağlantılı veri merkezi IP adreslerini ortaya çıkarın\nFaile karşı açılacak medeni hukuk veya ceza davalarında kullanılabilecek deliller sunmak\nAnahtar oluşturulduğunda hesap sahibine bildirimde bulunulup bulunulmadığını göster\nKayıtlarda yer alan bilgiler: Valve, cihaz düzeyindeki ve hesap ilişkilendirme kayıtlarını saklamaktadır — 1 Ekim 2025 tarihli avukat mektubunda bu kayıtlar açıklanmaktadır (bkz. Ek A, Delil Memorandumu — Kaynak 1). HT-2YBP-F7JP-D4VB numaralı talepte, veri sahibi tarafından aynı tür kayıtlar talep edilmiş ve talep, veri sahibinin söz konusu kayıtları içermediğini bildirdiği bir self-servis sayfasına yönlendirilerek kapatılmıştır. Bu reddin hukuka uygun olup olmadığı denetim makamının değerlendireceği bir konudur; bunun sonucu ise, verilerin konusu olan kişinin söz konusu kayıtlara ulaşamamasıdır.\nYazışma — dört mesaj, üç gün\n\nİki Steam destek temsilcisi, bilet üzerinde belirtilen ilk isimlerle yanıt verdi: 17 Eylül’de “Logen” ve 19 Eylül’de “Kal”. Her ikisi de talepte bulunan kişiyi Hesap Bilgileri sayfasına yönlendirdi. Bilet üzerinde, talebin Valve'un Gizlilik Ekibine veya Veri Koruma Görevlisine ulaşıp ulaşmadığına dair herhangi bir bilgi bulunmamaktadır ve dosyada temsilcilerin kim oldukları, rollerinin ne olduğu veya biletin nasıl yönlendirildiği belirtilmemiştir.\n\n16 Eylül\nDört adet belirtilen veri kategorisi ile sunulan Madde 15 talebi\n17–18 Eylül\nHesap Verilerine Atıf; talep eden, DPO’ya yönlendirme talebinde bulunur\n19 EYLÜL\nBilet aynı sevk bilgisiyle kapatıldı; veri yok, gerekçe belirtilmemiş\nGDPR’nin 15. maddesi, veri sahibine açıkça hangi hakları tanır?\n15. Maddenin (1) numaralı fıkrasının (a) bendiİşleme amaçları — Valve'un verileri neden sakladığı\n15. Maddenin (1) numaralı fıkrasının (b) bendiVeri kategorileri — Valve'da yer alanlar\nMadde 15(1)(c)Alıcılar veya alıcı kategorileri — verileri alan kişi (örneğin, API anahtarı sahibi)\n15. Maddenin (1) numaralı fıkrasının (d) bendiSaklama süresi veya bunun belirlenmesine ilişkin kriterler\n15. maddenin (3) numaralı fıkrasıİşleme tabi tutulan kişisel verilerin bir kopyası — yani API anahtarı günlüğünün kendisi\nMADDE 12(3)Yanıt süresi: bir ay teslim tarihinden itibaren; süre uzatımı o ay içinde bildirilmelidir. Yayın tarihi itibarıyla süre henüz dolmamıştı. 12. Maddenin 4. fıkrası: Eğer denetleyici harekete geçmezse, bunun nedenini belirtmeli ve şikayetçiye şikayet kanalları hakkında bilgi vermelidir.\nYasal şikayet süreci — tüm kullanıcılar için\n\nValve’a GDPR’nin 15. maddesi kapsamında bir talepte bulunmuş ve kurallara uygun bir yanıt (ya da veri içermeyen şablon bir ret mektubu) almamış herhangi bir kullanıcı, kendi AB/AEA üye devletindeki denetim makamına şikayette bulunabilir. Valve'in AB'deki yerleşim yeri Hamburg'daki Valve GmbH olduğundan, sınır ötesi şikayetler için baş denetim makamı Hamburg Veri Koruma ve Bilgi Özgürlüğü Sorumlusu (HmbBfDI). (Valve'un 27. maddesinde belirtilen temsilci de Hamburg'da bulunmaktadır; bir temsilcinin adresi tek başına yetkili makamı belirlemez.) Ayrıca, 77. madde uyarınca şikayetçinin kendi üye devletindeki makama da şikayette bulunulabilir.\n\nHmbBfDI şikayet formu ↗ GDPR metni (12., 15. ve 77. maddeler) ↗ arşivlendi 2026-09-20 ↗EDPB kılavuzları ↗\n\nHerhangi bir şikayet için bilet referans numarası: HT-2YBP-F7JP-D4VB — bu dosyada belgelenmiş bir örnek olarak yer almaktadır.\n\nBelgelenmiş bir örnek\nKayıtlar mevcuttur; veri sahibi bu kayıtları almamıştır.\n\nValve’nin avukatı, 1 Ekim 2025 tarihli bir mektupta cihaz düzeyindeki korelasyon kayıtlarını açıklamıştır. 19 Eylül 2026 tarihinde, aynı tür kayıtlara ilişkin 15. madde kapsamında yapılan bir talep, talep sahibinin bu kayıtları içermediğini bildirdiği bir self-servis sayfasına yönlendirilerek kapatılmış; bu işlemde herhangi bir yasal dayanak belirtilmemiştir. HT-2YBP-F7JP-D4VB numaralı talep, belgelenmiş bir örnektir; bunun daha yaygın bir uygulamayı yansıtıp yansıtmadığı ise, Valve’den işleme kayıtlarını talep edebilecek olan denetim otoritesinin değerlendirmesi gereken bir konudur.\n\nGDPR’nin 12., 15. ve 77. maddeleri / Denetim makamı\n\n12. ve 15. maddeler kapsamında bir şikayet, ilgili denetim makamına doğrudan ve ücretsiz olarak iletilebilir (77. madde). Kurum, erişim talebine uyulmasını emretmek de dahil olmak üzere düzeltici tedbirler uygulayabilir ve veri sahibinin haklarının ihlali durumunda 83. maddenin 5. fıkrasının (b) bendi uyarınca para cezası verebilir. Orijinal bilet referans numarasını ve Valve yanıtını (veya yanıtın gelmemesini) saklamak, şikayetin gücünü artırır.\n\nDSAR şablonuna bakın →\nC Bölümü — Yasal çerçeveler · 19. Bölüm · Sözleşme hukuku\nPlatformun kendi mimarisine aykırı Abone Sözleşmesi\nBağlam ve kaynak sınırlamaları\n\nYazarlar hukukçu değildir ve bu metin hiçbir şekilde hukuki tavsiye niteliği taşımamaktadır. SSA’dan alıntı, 10 Eylül 2026 tarihli revizyondan yapılmıştır; farklı bir revizyonda metin farklı şekilde yazılmış olabilir ve madde numaralandırması revizyonlar arasında değişmiştir — söz konusu davranışı düzenleyen sürümle maddeyi karşılaştırınız. 25. ve 32. maddelere ilişkin argümanlar, düzenlemenin neyi gerektirdiğini belirtir; bir denetim otoritesinin bir ihlal tespit ettiğini ifade etmez. 1. Argümandaki rakamlar, 13. Bölümde belirtilen kapsam sınırlarını yansıtmaktadır.\n\nSSA’nın üç temel hükmü, platformun yapısı ile uyumsuzluk göstermektedir: yüksek değerli satışları platform dışına iten bir Pazar fiyat tavanına yönelik ticari kullanım yasağı; 2023'ten önce ikinci faktör gerektirmeyen bir anahtar uç noktası karşısında API anahtarları için öngörülen kullanıcı sorumluluk maddesi; ve operatör başına uygulama göstermeyen bir kamu kayıtına karşı uygulanan yaptırım ifadeleri. Bu çelişkilerin uygulanabilirliği etkileyip etkilemediği bir mahkeme meselesidir; bu bölüm, mahkemenin önüne gelecek olguları ortaya koymaktadır.\n\n1. Argüman / Piyasa Değeri Mimarisi\nPazarın üst sınırı ve ticari kullanım yasağı\n\nSteam Topluluk Pazarı’nın liste fiyatı üst sınırı yaklaşık $1,800’dır. Tarihli bir anlık görüntüde (23 Eylül 2026) yer alan beş pazar yerinde, 248 CS2 ürün kategorisi, bu üst sınırın üzerinde iki veya daha fazla pazar yeri tarafından bağımsız olarak fiyatlandırılmıştır; bu tür ürünler Valve'nin kendi platformunda bu fiyatlardan satılamaz. Bu fiyatları isteyen işletme sahipleri, Steam hesapları ve Steam API’si üzerinden çalışan üçüncü taraf pazarlarını kullanır — SSA, açıkça izin verilmedikçe bunları ticari faaliyet olarak sınıflandırır.\n\nÜrünler Pazarın üst sınırını aşıyor → bu açığı üçüncü taraf pazarlar kapatıyor → bu pazarlar Steam hesaplarını ve Steam API’sini kullanıyor → SSA, izinsiz ticari kullanımı yasaklıyor → izin kayıtları yayınlanmamıştır. Topluluk Piyasası'nın yaklaşık 15% tutarındaki toplam ücreti, yalnızca Piyasa içinde tamamlanan satışlar için geçerlidir; bu harici işlemler için geçerli değildir.\n2. Argüman / API Anahtarı Güvenlik Mimarisi\nAPI anahtarı güvenlik açığı, kullanıcı ihmali değil, platform tasarımına ilişkin bir sorun olarak değerlendirilmelidir\n\n2023 yılından önce, Steam’un API anahtarı oluşturma uç noktası, çalınmış bir sessionid içeren bir POST isteğini kabul ediyor ve yüksek ayrıcalıklı bir kimlik bilgisi oluşturuyordu e-posta onayı, ikinci bir güvenlik faktörü veya cihaz doğrulaması olmadan. Bu soruşturmada toplanan API ele geçirme şikayetleri tek bir şablonu izlemektedir: saldırgan komut dosyası, çalınan oturum çerezi, gizli anahtar oluşturma, işlem ele geçirme (istek yükü Bölüm 8’de gösterilmiştir).\n\nGDPR’nin 25. Maddesi (tasarım aşamasından itibaren veri koruma) ve 32. Maddesi (işlemenin güvenliği), riske uygun teknik önlemlerin alınmasını gerektirmektedir. İkinci bir güvenlik faktörü olmaksızın veya sahibine bildirimde bulunulmaksızın ticaretin kesintiye uğratılmasına yol açabilecek bir kimlik bilgisi verilmesi, veri sorumlusunun tasarımla ilgili bir meselesidir. Bu bağlamda, sorumluluğu kullanıcıya yükleyen SSA hükmüne güvenilip güvenilemeyeceği konusu, mahkeme ve denetim otoritesinin karar vereceği bir meseledir.\n\n3. Argüman / Gerçek Zamanlı Görünürlük\nValve her oturum açılışında kimlik doğrulama ana bilgisayar adını alır\n\nOturum açma ana bilgisayar adı, Valve'un OpenID uç noktasına düz metin olarak şu şekilde ulaşır: openid.return_to ve openid.realm (istek biçimi Bölüm 3’te gösterilmiştir). Bunun çıkarılması standart bir işlemdir. 2026-09-22 itibarıyla, 26 çiftte ana etki alanı Link Filtresi’nde yer alırken, Steam oturum açma bilgisini taşıyan ana bilgisayar bu filtrede yer almıyordu. Valve, operatör bazında herhangi bir uygulama kaydı yayınlamamıştır; bu nedenle, bu ana bilgisayarlara Link Filtresi dışında herhangi bir önlem uygulanıp uygulanmadığı, kamuya açık verilerden tespit edilememektedir.\n\nMasrafları kim karşılar?\nArşivlenmiş şikayetlerdeki eğilim\n\nİncelenen şikayetlerde, Steam Destek ekibinin API anahtarı ele geçirilmesi iddialarına verdiği yanıt tek bir kalıba uymaktadır: geri yükleme talebini reddetmek, hesap ve API anahtarı konusunda kullanıcının sorumluluğuna atıfta bulunmak ve bileti kapatmak. Bu dosyada, etkilenen hesapların sayısı veya kaybedilen değerle ilgili herhangi bir toplam rakam tahmin edilmemiştir; bu tür bir rakamın kaynağına da rastlanmamıştır.\n\nAsıl mesele, bireysel kullanıcıların hata yapıp yapmadığı değildir. Asıl mesele, 2023 yılına kadar çalınmış bir çerezle yapılan bir POST isteğinin, herhangi bir bildirimde bulunulmaksızın ve ikinci faktörlü kimlik doğrulama yapılmaksızın yüksek ayrıcalıklı bir işlem kimlik bilgisi oluşturulmasına imkân tanıyan bu mimarinin sorumluluğunun kime ait olduğudur.\nBir belge olarak SSA ile bir sözleşme olarak SSA\nBu dosyayı inceleyen bir mahkeme, SSA’yı tek başına değerlendirmez.\n\nBu belge, avukatın Ekim 2025 tarihli mektubu ile birlikte incelenmelidir; söz konusu mektupta cihaz düzeyinde korelasyon, yetkilendirme sunucusu kayıt tarihleri, toplu kayıt zaman damgaları, API anahtarı talebinin yükü ve Temmuz 2016 tarihli bildirimlerle Eylül 2026’da hâlâ faaliyette olan platformlar arasındaki on yıllık süre ele alınmaktadır. İşte Valve'ın ele alması gereken kayıt budur.\n\nKayıtlara aykırı SSA / Önemli noktalar\n\"Ticari kullanım yasaktır\" — Market'in getirdiği sınırlama, yüksek değerli satışları ticari üçüncü taraf pazarlara yönlendiriyor\n\"API anahtarlarından kullanıcılar sorumludur\" — 2023'ten önce anahtar uç noktasında ikinci faktör yok\n\"Kurallara uymayanlara yaptırım uyguluyoruz\" — Temmuz 2016'dan bu yana operatör bazında herhangi bir yaptırım kaydı yayınlanmamıştır\n\"Şartları kabul ettiniz\" — \"hijack\" modelinde, kabul işlemi hesap sahibi tarafından değil, bir komut dosyası tarafından gerçekleştirilir\nSonuç · Kayıtların ortaya koyduğu hususlar ve taleplerimiz\nBulgular. Talep ettiğimiz kayıtlar.\nBağlam ve kaynak sınırlamaları\n\nAşağıdaki her bir bulgu, yukarıdaki bölümlerde yer alan tarihli bir kamu kayıtıyla bağlantılıdır. Bu talepler, bu soruşturmanın ulaşamadığı tek şeyi, yani Valve’nın kendi uygulama, erişim ve işleme kayıtlarını elde etmesini sağlayabilecek yetkililere yöneltilmiştir.\n\nHer talep, tarihli bir bulguya dayanmaktadır. Yetkililer, bu kamuya açık kaynaklara dayalı soruşturmanın elde etmesini sağlayamadığı kayıtları talep edebilir.\n\nKamu kayıtlarının ortaya koyduğu gerçekler\n44 canlı platform, ayrı bir kayıt edilebilir alan adı üzerinden kimlik doğrulaması yapmaktadır — bunlardan 27’si rota başına yayınlanmış kanıt dosyasına sahiptir, 17’si ise manuel olarak toplanmış ve ayrı olarak listelenmiştir. 2026-09-22 tarihi itibarıyla, 26 çiftin ana alan adı Steam Bağlantı Filtresinde engellenmişken, oturum açma bilgilerini barındıran ana bilgisayar engellenmemişti — csgogem.com engellenmiş, api.csgem.com Mart 2014’ten beri kayıtlıdır. Steam bu ana bilgisayar adını openid.realm ve openid.return_to her oturum açılışında. 3. Bölüm\n13 Temmuz 2016 tarihinde Valve bu mekanizmayı kamuoyuna duyurarak yasakladı ve avukatının 20 Temmuz 2016 tarihli bildirimlerinde on günlük bir süre tanındı. Bu sürenin dolmasından bu yana geçen on yıl boyunca, operatör bazında herhangi bir yaptırım kaydı yayınlanmamıştır. 11. Bölüm\nSteam Web API anahtar uç noktası, 2023 yılından önce ikinci bir doğrulama faktörü olmaksızın, yalnızca bir oturum çerezi kullanarak yüksek ayrıcalıklı ve işlem yapma yetkisine sahip bir kimlik bilgisi vermiştir. 5. Bölüm\nGDPR’nin 15. maddesi kapsamında yapılan bir talep (bilet numarası HT-2YBP-F7JP-D4VB), üç gün sonra self-servis bağlantısı eklenerek ve herhangi bir veri sağlanmadan kapatıldı. 18. Bölüm\nHer bir yetkili kurumdan istediğimiz şey\nWashington Eyaleti Kumar Komisyonu\n2016 dosyasını yeniden açın. On günlük bildirimlerin ardından hangi hesapların, botların ve geri dönüş sunucularının devre dışı bırakıldığını ve hangi operatörlerin daha sonra erişim haklarını geri kazandığını operatör bazında ayrıntılı bir şekilde raporlayın. 2. Bölüm\nHmbBfDI (Hamburg; Valve GmbH)\n15. maddeye verilen yanıtın veri sorumlusunun yükümlülüğünü yerine getirip getirmediğini kontrol edin ve failin kimliğinin tespit edilmesiyle ilgili API anahtarı kayıt ve erişim kayıtlarının açıklanmasını talep edin. 18. Bölüm\nDSA dijital hizmetler koordinatörleri\nKayıta auth-host yönlendirmesini bir uyarı olarak ekleyin, ardından bilgi belgelendikten sonra Valve'un yanıtının yükümlülüklerini yerine getirip getirmediğini değerlendirin. 16. Bölüm\nHerhangi bir veri sahibi\nKendi hesabınız için aynı kayıtları talep etmek üzere 15. Madde şablonunu kullanın; saklanan bir kayıt, sıfırlama işlemini kimin başlattığını veya bir anahtarı kimin oluşturduğunu ortaya çıkarabilir. Ek G\n\nBu dört talebin ardında yatan tek talep aynıdır: Yalnızca Valve’un elinde bulunan uygulama, erişim ve işleme kayıtlarının yayınlanması. Ana sayfadaki uyarı, on günlük bildirim mektubu ve self-servis sayfası, kontrolün elinde olduğunu gösteren unsurlardır. Kontrolün gerçekten kullanılıp kullanılmadığı ise kamu kayıtlarının cevaplayamadığı, ancak düzenleyici kurumun cevaplayabileceği bir sorudur.\n\nEkler — birincil deliller ve çalışma materyalleri\nEk A — Avukatlarla yapılan yazışmalar\nDelil Notu — Kaynak 1 tarafından sağlanan materyal\n\n1., 18. ve 19. bölümlerde dayanak olarak gösterilen avukat yazışmalarına ilişkin kanıt temeli ve kaynak durumu.\n\nKanıt Temeli ve Kaynak Durumu — Kaynak 1 tarafından sağlanan belgeler\nBu denetimin tetiklenmesine neden olan kalıcı yasaklama kararının uygulandığı kullanıcı, bu denetimin konusu değildir. Söz konusu yasaklamanın haklı olup olmadığı burada incelenmemektedir ve bu dosya ne bu kararı savunmakta ne de itiraz etmektedir. Mesele hesap değildir. Önemli olan içeriktir: Kaynak 1 — kendi GDPR talebinin veri sahibi olarak Valve'nin avukatından aşağıdaki yazışmayı alan, hesabı engellenmiş kişi — bu yazışmayı ve beraberindeki dava dosyalarını, bunları kamuya açık olarak inceleme hakkı ile birlikte paylaştı. Kişinin adı gizli tutulmuştur; belgeler tarih, üretici meta verileri ve hash değeriyle tanımlanmıştır.\n\nSöz konusu yazışma, bir GDPR/DSAR talebine yanıt olarak gönderilmiştir. Bu süreçte, Valve’un avukatı, Steam Destek ekibinin daha önce kullanıcılara teknik olarak mümkün olmadığını söylediği bir özelliği açıklayan, imzalı bir beyanı kayıtlara geçirmiştir. Aşağıda alıntılanan paragraf, söz konusu beyanın metnidir.\n\nYazarların elde edilen günlük dökümüne ilişkin daha ayrıntılı analizi şöyledir: bu dosyada yer almamıştır bağımsız bir inceleme sonuçlanana kadar. Bu soruşturmanın diğer hiçbir aşamasında bu bulguya dayanılmamaktadır.\n\nKayıtlara geçen itiraf: sürekli cihaz düzeyinde telemetri\n\nValve'un avukatına atfedilen mektubun 1.9. paragrafında, Valve'in avukatları şunları belirtmektedir: \"2019 ile 2023 yılları arasında, bu hesap esas olarak, çalınan onlarca Steam hesabına giriş yapmak için de kullanılan bir cihazdan erişildi.\"\n\nGerçek: Valve'in avukatı, burada dört yıllık bir süreyi kapsayan hesaplar arasında cihaz düzeyinde yapılan eşleştirmeyi açıklamaktadır. Steam Müşteri desteği, hırsızlık mağdurlarına çalınan eşyaların izlenmesinin veya hesapların cihazlarla ilişkilendirilmesinin teknik olarak mümkün olmadığını bildirmiştir. Steam Guard Cihaz yetkilendirme süreci kamuya açık bir şekilde belgelenmiştir; dolayısıyla cihaz başına kayıtların varlığı başlı başına yeni bir durum değildir; yeni olan ise, avukatın bu kayıtların saklandığını ve hesaplar arasında uzun yıllar boyunca ilişkilendirildiğini yazılı olarak teyit etmesidir.\n\nBunun önemi: Dört yıl boyunca bir cihazı ele geçirilmiş düzinelerce hesapla ilişkilendirebilen bu korelasyon, Destek biriminin mağdurlar için kullanamayacağını belirttiği kayıt sınıfıyla aynıdır. Bu sınıftaki kayıtlar, hırsızlık ve yeniden satış zincirindeki hesapları ve cihazları tespit etmeye imkan verebilir. Hangi kayıtların mevcut olduğu, ne kadar süreyle saklandığı ve veri sahiplerinden hangi gerekçeyle gizlendiği, denetim otoritesinin yanıtlaması gereken sorulardır.\n\nKaynak: Valve’un avukatının 1 Ekim 2025 tarihli mektubu, 1.9. paragraf ve 830 sayfalık PDF eki · Kaynak 1 tarafından GDPR’nin 15. maddesi kapsamındaki bir talebe yanıt olarak alınmıştır · Ekin SHA-256 değeri şu adreste kayıtlıdır: disclosure-audit.json · Mektubun kendisi burada yer almamaktadır; hesap adları ve üçüncü taraflara ait veriler çıkarılmıştır.\n\nDurum: açık\nKaynak materyaller, kanıt arşivinden erişilebilir.\nEk B — Oluşturulan PDF · sansürleme kontrolü\nOluşturulan PDF’deki sansürleme sadece görsel niteliktedir: sansürlenen metin hâlâ çıkarılabilir durumdadır\n\nValve'nın avukatı, bir GDPR erişim talebine, metin içindeki gizlenen kısımların silinmek yerine üzerlerinin boyanarak işaretlendiği 830 sayfalık bir ekle yanıt verdi. 902,270 karakter, siyah çubukların altında yer alır ve bir metin çıkarma aracıyla doğrudan ortaya çıkar — çubukların gizlemesi gereken üçüncü taraf tanımlayıcıları da dahil olmak üzere. Burada yalnızca toplam sayılar yayınlanmaktadır; kapsama dahil olan içeriklerin hiçbir kısmı aktarılmamaktadır ve ek metin de yayınlanmamaktadır.\n\n1. Geometri kontrolünde tespit edilenler\n\nGDPR’nin 15. maddesine ilişkin, tarihli yanıt 1 Ekim 2025 Bu çalışmaya 830 sayfalık bir PDF eki eşlik ediyordu (aynı tarihte oluşturulmuş ve değiştirilmiş, .NET için Aspose.PDF üretici meta verileri). Yazarlar sayfa düzeyinde bir geometri kontrolü gerçekleştirdiler: her sayfa için, metin katmanının üzerine boyanmış, neredeyse siyah renkli, saydam olmayan dikdörtgenler tespit edildi ve bunların altında bulunan çıkarılabilir karakterler sayıldı.\n\nOluşturulan dosya üzerinden ölçülmüştür\n902,270\nKara çubukların altından hâlâ okunabilen karakterler\nTahmin değil, sayım. Bu, kapsama dahil olan karakterlerin sayısıdır — kurbanların, yeniden tanımlamaların ya da olayların sayısı değildir.\n830 / 830\nEtkilenen sayfalar — tüm sayfalar\n986\nÇıkarılabilir metinlerin üzerindeki dikdörtgenler\n1,329\nToplamda opak siyah dikdörtgenler\nSiyah çubuklar metin katmanının üzerine çizilmiştir; metni silmezler. Çubukların altındaki metin, standart PDF araçlarıyla çıkarılabilir. Yalnızca toplam sayılar yayınlanmaktadır; örtülü içerik burada yer almamaktadır.\nAdli Gösteri: Katmanların Ayrılması\nASPOSE.PDF FOR .NET VEKTÖR ÜSTÜNE YERLEŞTİRME MODELİ (EK, S. 412)\n\nHesap hakkında yapılan şikayet: [GİRİŞ: redacted_user_667]\n\nKullanıcı tarafından belirtilen neden: [METİN: \"Kullanıcı, envanterde yinelenen ürünler ve haksız ticari uygulamalar olduğunu bildiriyor...\"]\n\nÖn plan: <path fill=\"#000\" />Kusur: Altta yatan UTF-8 akışı bozulmamış\nKaynak: 1 Ekim 2025 tarihli danışmanlık mektubunun PDF eki (830 sayfa, Aspose.PDF for .NET üretici meta verileri) · yazarlar tarafından hesaplanmış, yöntem ve sayfa başına sayılar disclosure-audit.json · Aynı dosyada kayıtlı ekin SHA-256 değeri · ekin kendisi yayınlanmamıştır.\n2. Bu durumun veri sahibi yanıtı açısından önemi nedir?\n\nValve'un avukatı, ilgili kişinin kendi kayıtlarına ilişkin talebine yanıt olarak bu dosyayı veri sahibine gönderdi. Üzerindeki çizgiler sadece görsel amaçlıdır: Altındaki metin hiçbir zaman silinmemiştir; dolayısıyla, gizlemek amacıyla çizgilerle örtülen üçüncü taraf tanımlayıcıları, dosya ile birlikte alıcıya ulaşmıştır. Metin çıkarma aracıyla kaldırılabilen bir sansürleme işlemi hiçbir şeyi gizlemez ve ayrıca alıcının neyin ifşa edildiğini, neyin edilmediğini belirleyememesine neden olur.\n\n15. maddenin 4. fıkrası, bu kısıtlamaların var olmasının temel nedenidir: bir kopya alma hakkı, başkalarının hak ve özgürlüklerini olumsuz etkilememelidir. İşte bu yapımın yerine getirmediği yükümlülük budur. Bunun 4. maddenin (12) numaralı fıkrası kapsamında bir kişisel veri ihlali olarak nitelendirilip nitelendirilmeyeceği, denetim makamı tarafından belirlenecektir; ifşa edilen bilginin kendisi dosyada ölçülebilir ve aynı baytlara sahip olan herkes tarafından yeniden üretilebilir — SHA-256 yayınlanmıştır, ancak ek yayınlanmamıştır.\n\nÇubukların altında hesap numaraları yoktu. Bu, talep sahibine karşı yapılan kullanıcı raporlarının metniydi ve raporların yazarları da eklenmişti: Steam oturum açma işlemi; bir oturum açma işleminin nadiren sadece Steam’de kullanılması nedeniyle, bunların ardındaki kişiyi tespit eden — Yazarların hesaplamasına göre, belgede adı geçen kullanıcıların 60%’dan fazlası tam olarak tanımlanabilir durumdadır — yazdıkları metnin düzenlenmemiş, sansürsüz haliyle birlikte. Bu metin, talep sahibinin uyruğuna yönelik ölüm tehditleri ve hakaretler içermektedir. Bu şekilde kimlikleri tespit edilen kişilerden bazıları reşit değildir. Yapım ekibi, haber yaptıkları kişiye isimleri belirtilmiş bir muhabir listesi verdi, ki bu tam da 15. maddenin 4. fıkrasının önlemek amacıyla düzenlendiği zarardır.\n\nDosyanın içindeki sıralama, içeriği kadar önemlidir. Talep, ilk olarak, talep sahibinin takma adla kullandığı e-posta adresinde isminin bulunmaması gerekçesiyle ek kimlik kanıtı istenmesiyle karşılandı; ardından ortaya çıkan gecikme süresince hesap kalıcı olarak engellendi. Verilerin nihayet teslim edildiği mektup, Madde 12(3)’te belirtilen bir aylık sürenin altı haftadan fazla geçmesinden sonra geldi; mektupta alıcıya cezai kovuşturma tehdidinde bulunuldu ve avukata hesap faaliyetlerini açıklayana kadar kendi verilerinin geri kalanı saklandı. Bu ifşa, Valve'un kamuoyuna yanıt vermediği iki soruyu da açıklığa kavuşturuyor: sunulan kayıtlar, 2019 yılına kadar uzanan hesap bağlantılarını gösteriyor ve Valve'in daha önce hiç açıklamadığı derinlikte bir iç telemetri verisi ortaya çıkıyor.\n\nBu bölümün kapsamı: Buradaki inceleme, hazırlanan dosya üzerinden ölçülen düzenleme sürecinin işleyişiyle sınırlıdır. Yazarların hazırlanan kayıtlara ilişkin daha kapsamlı analizleri, bağımsız bir inceleme sonuçlanana kadar askıya alınmış olup, bu dosyada başka hiçbir yerde bu analize dayanılmamıştır.\n\nDelil: 1 Ekim 2025 tarihli avukat mektubu ve buna ekli PDF dosyası (SHA-256 denetim dosyasında kayıtlı); Sayfa düzeyinde PDF ölçümleri ve yöntemi ↗. Talebin akışı, 8. sayfadaki ret kararı ve ifşa edilen kayıtların niteliği, PhishDestroy’nin ifadesinde ayrıntılı olarak belirtilmiştir, “Köpeğim ve Seçkin GDPR Avukatları”, 17 Ağustos 2026 ↗ arşivlendi 2026-08-21 ↗. Hesap adları ve üçüncü taraf verileri burada yer almamaktadır; çubuklarla örtülen hiçbir bilgi aktarılmamıştır.\n\nKapak mektubunun 8. sayfasında talebin bir kısmı reddedilmekte ve gerekçe yazılı olarak belirtilmektedir: Steam platformundaki diğer kullanıcıların kişisel verilerinin korunması nedeniyle… daha ayrıntılı bilgi verilmesi mümkün değildir. — Daha ayrıntılı bir cevap verilmesi mümkün değildir, çünkü diğer Steam kullanıcılarının kişisel verilerinin korunması gerekmektedir. 830 sayfalık ek de aynı pakette yer almaktaydı. Çizgilerle kapatılan kısımlar hesap numaraları değildi: bunlar, talep sahibine karşı sunulan raporlardı; raporların yazarlarının isimleri belirtilmişti ve sansürlenmemiş ham mesajlar ekte yer alıyordu. Hesap sahibi, avukatı aracılığıyla Valve’dan kendi dosyasını istemişti; ancak dosyadan elde edebildiği bilgiler başkalarına aitti. Bu ekte yer alan hiçbir şey, kutuları kimin çizdiğiyle ilgili değildir. Ortaya koyduğu şey, bilgilerin saklanmasının gerekçesi olarak gösterilen Valve korumasının, aynı zarf içinde, aynı gün, bu aynı sunumda sağlanamadığıdır.\nDestek ve Hukuki Yazışmalara İlişkin Ekler\n\nKaynak: https://phishdestroy.io/steam_dossier/tr/index#exhibit-gallery-section\n\nEk D — Kaynak toplama\nSeçilmiş birincil kaynaklar\n\nArşivden altı kayıt — Valve’nin izleme sistemlerindeki üç GitHub sorunu ve tartışmalı destek sonuçlarına ilişkin üç Reddit hesabı. Her kaynak, ilgili iddiaya, kaydedilmiş metne ve ortaya attığı soruya eklenmiştir.\n\n1 / 6 seçilen kayıtlar\nBir kaynak kaydı seçin\nGH-01 / GITHUBKaydedilmiş derlemede aç\n2016 yılında talep edilen donanım anahtarları\n\nValveSoftware / steam-for-linux · #4521 · 2016-06-27\n\nBir kullanıcı, Valve’dan alternatif bir ikinci faktör olarak U2F donanım anahtarlarını desteklemesini talep etti. Kaydedilen bu sorun, hem “Özellik Talebi” hem de “İncelendi” etiketlerini taşıyor ve durumu “açık” olarak kaydedilmiştir.\n\nAlternatif olarak Steam'de U2F USB anahtarının desteklenmesini talep ediyorum.\n\nGitHub sorunundan alıntı ↗\nKayıtlı belge\nValve'un kendi sorun izleme sisteminde yayınlanan ve “incelendi” olarak etiketlenmiş, ek bir hesap koruma önlemi talebine ilişkin tarihli bir istek.\nHesap verme talebi\nÜrün kararını, yanıt tarihini ve inceleme sonrasında sağlanan korumayı yayınlayın.\nKaydedilmiş kaydı oku →GitHub'ı aç ↗\nDosyada: Hesap güvenlik önlemleri →Arşiv #484 · derleme 2026-09-17\nGH-02 / GITHUBKaydedilmiş derlemede aç\nEtkili bir vazgeçme seçeneği bulunmayan hata raporları\n\nValveSoftware / steam-for-linux · #6459 · 2019-08-18\n\nMuhabir, 12 Ağustos 2019 tarihli, Ubuntu 16 üzerinde çalışan bir Steam istemcisinden bahsediyor. Crash-upload hedefinin devre dışı bırakılmasının, sistemin yeniden başlatılmasından sonra kalıcı olmadığını belirtiyor ve ilgili yapılandırmayı da ekliyor.\n\n`ServerURL` ayarını devre dışı bırakırsam, her yeniden başlatmanın ardından bu ayar üzerine yazılıyor.\n\nGitHub sorunundan alıntı ↗ arşivlendi 2026-04-19 ↗\nKayıtlı belge\nMüşteri tarihi, işletim sistemi ve yapılandırma bilgilerinin yer aldığı somut bir gizlilik şikayeti. Kaydedilen sorun hâlâ açık durumdadır.\nHesap verme talebi\nSoruşturmayı, etkilenen derlemeleri ve devre dışı bırakma işleminin yürürlüğe girmesini sağlayan değişikliği belirleyin.\nKaydedilmiş kaydı oku →GitHub'ı aç ↗arşivlendi 2026-04-19 ↗\nDosyada: İlgili kayıtların talep edilmesi →Arşiv #467 · derleme 2026-09-17\nGH-03 / GITHUBKaydedilmiş derlemede aç\nValve'ye bildirilen Auth-ticket suistimali\n\nValveSoftware / Source-1-Games · #3857 · 2022-02-26\n\nYazar, bir sunucu işletmecisinin oyuncuların bağlantısı kesildikten sonra Steam kimlik doğrulama biletini elinde tuttuğunu ve yanıltıcı sunucu listeleri kullandığını iddia ediyor. Gönderide, Valve’dan bu duruma bir çözüm getirilmesi isteniyor.\n\nSunucularını doluymuş gibi göstermek.\n\nGitHub sorunundan alıntı ↗\nKayıtlı belge\n26 Şubat 2022 tarihinde Valve'nin izleme sistemine kaydedilen bir kamuya açık istismar bildirimi. Bildirimin kaydedilmiş durumu “açık”tır; bildiride ekran görüntülerine bağlantılar bulunmaktadır.\nHesap verme talebi\nBildirilen kimlik doğrulama bileti suistimaliyle ilgili soruşturma sonucunu ve önlem kayıtlarını hazırlayın.\nKaydedilmiş kaydı oku →GitHub'ı aç ↗\nDosyada: Veri kümesinin kapsamı →Arşiv #768 · derleme 2026-09-17\nRD-01 / REDDITYazarın profili\n44 adet ihtilaflı Market alımı\n\nr/DotA2 · yazar adı gizlenmiştir · 2022-07-07\n\nYazar, 6 Temmuz 2022 tarihinde Market’te 44 adet yetkisiz satın alma işlemi gerçekleştiğini ve yaklaşık $500+ tutarında zarar yaşadığını bildiriyor. İki faktörlü kimlik doğrulamanın etkin olduğunu belirtiyor ve destek ekibinden defalarca şablon cevaplar aldığını anlatıyor.\n\nİkinci biletimi gönderdim ama Steam’dan hâlâ robotik bir kopyala-yapıştır şablonu olmayan bir yanıt almadım.\n\nReddit gönderisinden alıntı ↗ arşivlendi 2025-03-20 ↗\nKayıtlı belge\nTartışmalı satın alımlara ilişkin tarihli bir açıklama; işlem ekran görüntülerine bağlantılar ve destek ekibinin yanıtı da yer almaktadır. Tutarlar ve olaylar, yazarın bildirdiği şekildedir.\nHesap verme talebi\nİhtilaflı satın alımları işlem ve oturum günlükleriyle karşılaştırın. Destek ekibinin kararının dayandığı kanıtları açıklayın.\nKaydedilmiş kaydı oku →Reddit'i aç ↗arşivlendi 2025-03-20 ↗\nDosyada: Destek ve uygulama →Arşiv #4,533 · derleme 2026-09-17\nRD-02 / REDDITYazarın profili\nKalıcı yasaklama ve temyiz hakkının kaldırılması\n\nr/ohnePixel · yazarın kullanıcı adı gizlenmiştir · 2024-12-09\n\nYazar, kalıcı bir engelleme kararına itiraz ediyor ve desteğin, şüpheli hesap aktarımı ve topluluk raporlarına dayandığını belirtiyor. Yazar, kapatılan destek taleplerinden ve kişisel verilerini talep etme planlarından bahsediyor.\n\nDurumumu anlattım ve daha fazla ayrıntı istedim, ancak kararlarından vazgeçmiyorlar ve biletlerimi kapatıyorlar.\n\nReddit gönderisinden alıntı ↗\nKayıtlı belge\nYazarın, sağlanan desteği desteklediğini belirttiği gerekçeleri ve dört resme ait bağlantıları içeren, korunmuş bir destek hesabı. Gönderim tarihi, seçilen destek dışa aktarımından alınmıştır.\nHesap verme talebi\nKalıcı yasağı destekleyen delilleri ve buna itiraz etmek için mevcut inceleme sürecini belirleyin. Temyiz dosyasının kapatılması, kararın gerekçesini açıklamaz.\nKaydedilmiş kaydı oku →Reddit’i aç ↗\nDosyada: İlgili kayıtların talep edilmesi →Arşiv #4,766 · derleme 2026-09-17\nRD-03 / REDDITYazarın profili\nBir kurtarma sıfırlaması ve bildirilen $10,000 tutarındaki kayıp\n\nr/legaladvice · yazar adı gizlenmiştir · 2025-05-09\n\nYazar, başka bir kişinin kurtarma talebinde bulunmasının ardından destek ekibinin kimlik bilgilerini sıfırladığını ve hesap koruma önlemlerini devre dışı bıraktığını iddia ediyor. Yazar, aktif olmayan bir hesaptan yaklaşık US$10,000 tutarında bir kayıp yaşadığını bildiriyor.\n\nSteam Destek ekibi şifremi sıfırladı ve hesabımın tüm güvenlik ayarlarını devre dışı bıraktı.\n\nReddit gönderisinden alıntı ↗\nKayıtlı belge\nHesap güvenlik önlemlerini geçersiz kılan kurtarma süreciyle ilgili kaydedilmiş bir iddia. Kaydedilen gönderi, yazarın destek ekibinden duyduğunu iddia ettiği bilgileri aktarıyor.\nHesap verme talebi\nSıfırlama işlemini kimin onayladığını, kabul ettikleri sahiplik kanıtını ve erişim günlüğünü belirleyin. Hesap kurtarma, güvenlik sisteminin Valve denetimlerinin bir parçasıdır.\nKaydedilmiş kaydı oku →Reddit'i aç ↗\nDosyada: İlgili kayıtları talep edin →Arşiv #4,592 · derleme 2026-09-17\n\nSeçilmiş altı kayıt. GitHub açıklamaları, kaydedilen derlemeyi tanımlar. Reddit gönderileri, yazarların anlatımlarını korur.\n\nAltı kaydı indirin ↓\n\nArama yapılabilen derleme şunları içerir: 16,319 farklı kayıt: 393 Trustpilot, 5,635 Reddit, 2,395 GitHub, 276 web ve 7,620 wiki kaydı. Birden fazla kayıt aynı olayı ilgilendirebilir. Ayrı olarak hazırlanan 40,448 satırlık ana dışa aktarımın kapsamı farklıdır.\n\nTüm arşivi ara ↗ · Manifest oluştur ↗ · Veri kümesinin kapsamı ve sayıları →\n\nEk E — Vaka çalışması\nArchiSteamFarm ve otomasyon hükmü\n\nKendi SSS bölümünde milyonlarca hesapta çalıştığı belirtilen bir açık kaynaklı kart toplama aracı; bu durum, otomasyonu yasaklayan Abone Sözleşmesi maddesiyle (§ 4.C) çelişmektedir. İşleyiş mekanizması — bir kart toplama sisteminin herhangi bir şey üretebilmesi için Valve'dan ne satın alması gerektiği, bir karttan para çekmenin her yolunun neden lisans şartlarını ihlal ettiği, yaptırım geçmişi ve kart ekonomisini kimin denetlediği — şu belgede ayrıntılı olarak açıklanmaktadır: Ek V ↗.\n\nSteam Abone Sözleşmesi’nin 4.C maddesi şu şekilde belirtmektedir:\n\n\"Steam'daki İçerik ve Hizmetlerle herhangi bir şekilde etkileşim kurmak amacıyla, hiçbir türde komut dosyası, bot, makro veya insan kontrolü dışında çalışan diğer sistemler ('Otomasyon') kullanamazsınız.\" — Steam Abone Sözleşmesi § 4.C (güncel) ↗ arşivlendi 2026-09-18 ↗\n\nValve bu maddeyi uygulamaktadır. Bu konuda oldukça başarılıdır. Şu konuyla ilgili SSS: ArchiSteamFarm (ASF) — kendi belgelerinde şu platformlarda çalıştığı belirtilen bir açık kaynaklı araç: birkaç milyondan fazla Steam hesabı 11 yılı aşkın bir süre önce ilk sürümünün yayınlanmasından bu yana — bot ağlarını işleten kullanıcıları kalıcı olarak engelleyen üç Steam destek mesajını yeniden yayınlıyor. Valve bu ağları tespit etti, isimlerini açıkladı ve ortadan kaldırdı. Dolayısıyla asıl soru, Valve’in büyük ölçekte otomasyonu tespit edip edemeyeceği değildir.\n\nProjenin resmi ArchiSteamFarm SSS yasaklanma riskini doğrudan ele almaktadır:\n\n\"ASF'nin, 11 yıldan fazla bir süre önce piyasaya sürüldüğünden bu yana birkaç milyondan fazla Steam hesabında kullanıldığı gerçeği göz önüne alındığında, bu durum son derece olasılık dışı görünse de — gerçek olasılık ne olursa olsun — yine de bir olasılıktır.\"\n\n\"Valve, burada belirtildiği gibi 'Steam aylakların' varlığını açıkça kabul ediyor; dolayısıyla bana sorarsan, eğer bu durumdan hoşnut olmasalardı, VAC açısından sorunlara yol açabileceğini belirtmek yerine çoktan bir şeyler yaparlardı, buna oldukça eminim.\" Buradaki anahtar kelime, örneğin ASF gibi Steam idler’lardır; oyun idler’ları değildir.\"\n\n— ArchiSteamFarm SSS, JustArchiNET. Kaynak: GitHub wiki ↗ · kelimesi kelimesine doğrulanmış 2026-09-22\n\nAynı SSS bölümünde \"Bu nedenle kimse yasaklandı mı?\" sorusuna şu yanıt verilmektedir: Evet, ve Steam Support’un bunlardan üçüne yazdıklarını şu şekilde aktarıyor:\n\n1,000+ bot · ticaret yasağı\n\"Görünüşe göre bu hesap, bir bot hesabı ağını yönetmek için kullanılmış. Bot kullanımı, Steam Abone Sözleşmesi’nin ihlali niteliğindedir.\"\n\n170'den fazla bot · kalıcı olarak yasaklandı, 2017 Kış İndirimi\n\"Bu hesap, Steam'da koleksiyon kartlarını yasadışı bir şekilde toplamak ve bununla ilgili, sadece ticari faaliyetlerle sınırlı olmayan diğer faaliyetlerde kullanılmıştır. Hesap kalıcı olarak engellenmiştir ve Steam Destek ekibi bu konuyla ilgili ek destek sağlayamaz.\"\n\n120'den fazla bot · kalıcı olarak engellendi\n\"Bu ve diğer hesaplar, ağ altyapımızı aşırı yüklemek amacıyla kullanıldı; bu da Steam çevrimiçi davranış kurallarının ihlali teşkil etmektedir.\"\n\n— Steam ArchiSteamFarm numaralı SSS’nin “Bunun yüzünden kimse engellendi mi?” başlıklı bölümünde yer alan destek mesajları. Kaynak ↗ · kelimesi kelimesine doğrulanmış 2026-09-22\n\nİki kaydı yan yana yerleştirin. 1,000 tarım botuna sahip bir özel kullanıcı tespit edildi, kendisine “bot kullanımı Steam Abone Sözleşmesi’nin ihlali” olduğu bildirildi ve kalıcı olarak hesapları silindi. Bu dosyada yer alan ticari platformlar, ana faaliyetleri olarak otomatik Steam hesaplarını çok daha büyük ölçekte işletiyor ve her oturum açılışında Valve'in kendi OpenID'si aracılığıyla kimlik doğrulaması yapıyor — ancak bunların hiçbiri için operatör bazında bir yaptırım kaydı yayınlanmadı. Bu madde geçerlidir. Asıl soru, kime yönelik olduğudur.\n\nASF burada hiçbir şeyle suçlanmamaktadır ve Valve’un tutumuna ilişkin yorumu tamamen kendisine aittir — yazarı, “ASF, Valve tarafından yetkilendirilmemiştir” şeklinde açıkça belirtmektedir. Bu araç burada bir ölçüm aracı olarak kullanılmaktadır: Valve'nin bot ağlarını tespit ettiğini, bunları yazılı olarak isimlendirdiğini ve kalıcı olarak yasakladığını göstermektedir. Valve, hangi ticari otomasyonlara izin verdiğini ve geri kalanlar hakkında ne yaptığını operatör bazında kayda geçirerek tek bir cümleyle bu konuyu kapatabilir.\n\nKart toplama faaliyetlerinin Valve'nin gelirine etkisi\n\nÇiftlikte elde edilen koleksiyon kartları, Steam Topluluk Pazarı’nda satılmaktadır; bu pazarda, Pazar içinde gerçekleştirilen her satış için toplamda yaklaşık 15% tutarında bir ücret alınmaktadır; hesap, bir kart alabilmek için öncelikle Steam üzerinde $5.00 USD harcamış olmalıdır; ve kartların düşmesi için oyunun sahibi olunması veya oyun içi satın alımlar gereklidir. Burada toplam gelir rakamı tahmin edilmemektedir — işletme ölçeği yalnızca ASF SSS’sinde belirtildiği şekilde ifade edilmiştir. SSS’de ayrıca Valve ayırt edici unsur kaydedilmiştir. \"Steam avara\" (kart toplama) kaynak: \"oyun boşboğazları\"; bkz. ASF SSS ↗. Bu mekanizma, şu metinde ayrıntılı olarak açıklanmaktadır: Ek V — Ölçek ve ticari amaçlı tuzak.\n\nKonuArchiSteamFarm — otomatik kart toplama\nBelirtilen ölçekMilyonlarca hesap (ASF SSS’ye göre — kesin aktif hesap sayısı doğrulanmamıştır)\nSayılmış, alıntılanmamış10,880,610 ASF’nin kendi Steam grubundaki toplam API girdisi (5,360,499 sınırsız, Steam’te gösterildiği gibi) — SSS’deki “milyonlar” bir hikâye değil, sayıdır. 88.97% herhangi bir tür Steam yasak içermemektedir. Tam yasak sayımı ↗\nAracın kendi belgelerinde yer alan açıklamalar\nASF, Steam istemcisini başlatmadan (proje belgelerinde belirtildiği üzere) hesapları başsız modda oturum açar ve kart düşmesi için oyunları bekleme moduna alır.\nSıkça Sorulan Sorular bölümünde, Valve’ın “Steam aylaklarından” haberdar olduğu ve “eğer bunlardan hoşlanmasalardı, çoktan bir şeyler yaparlardı” şeklinde bir gerekçe öne sürülmektedir.\n(Sıkça Sorulan Sorular bölümüne göre) 11 yılı aşkın süredir hedefli bir denetim bildirilmemiştir; Community Market’te gerçekleşen kart satışlarından elde edilen gelir, Steam’in toplam ücretini, yani yaklaşık 15%’u karşılamaktadır.\nSıkça Sorulan Sorular bölümünde, operatör başına on hesaplık bir üst sınır önerilmekte ve bu öneri Valve’ye atfedilmektedir: “Bu öneri, hem Valve’in iç yönergelerine hem de bizim kendi önerilerimize dayanmaktadır.” Valve tarafından bu tür bir yönerge yayınlanmamıştır.\nAynı SSS'ye göre teknik sınır: \"Tek bir IP adresi ve tek bir ASF örneği ile en fazla 100-200 bot çalıştırabilirsiniz.\"\nOyun süresi, Valve tarafından kaydedilir — “genellikle yaklaşık 30 dakikada bir güncellenir” — ve § 4.C’de “Oyun istatistiklerini tahrif etmek (örn. şişirilmiş galibiyet veya mağlubiyet sayıları, XP, oyun süresi)” yasaklanmış eylemler arasında yer almaktadır.\nKaynaklar\nJustArchi ASF Resmi SSS wiki'si ↗ ArchiSteamFarm depo ↗ arşivlendi 2026-09-24 ↗\nOtomasyon hükmü açık ve nettir; ASF SSS bölümünde yıllardır bu aracın milyonlarca hesapta çalıştığı belirtilmektedir; buna yönelik herhangi bir hedefli yaptırım bildirilmemiştir. Kural ile uygulaması arasındaki uçurum, kayıtlarda görülmektedir; bunun nedeni burada belirlenmemiştir.\nSerginin tamamıKart ekonomisi: süreç, ölçek, lisans ve denetimi kim yapıyor? ↗Bir çiftliğin tek bir kart üretebilmesi için Valve’dan ne satın alması gerektiği; § 4.C'nin, kart çiftçiliğini etkilerine göre tanımlayan iki satırı; bir kartı nakde çevirmenin her yolunun, Valve'in yazdığı lisansı ihlal etmesinin nedeni, oysa Valve girişte bir ücret alıyor; Haziran 2025'teki VAC dalgası ve paylaşılan telefon numarasına göre zincirleme yasaklamayı içeren uygulama kaydı; ve Steam civarında kart ticareti ve yasak listesi hizmetlerini yönettikleri tespit edilen Valve çalışanı ve topluluk moderatörleri.Yasak sayımıValve'a çiftliğin ne kadar büyük olduğunu sormadık. Saydık. ↗10,880,610 toplam hesap (sınırlı ve sınırsız), ArchiSteamFarm'in kendi Steam grubundan okunur; kullanıcı grup katılım ayarının işaretini kaldırmadıkça, yazılım ilk başlatıldığında varsayılan olarak bu gruba otomatik olarak katılır (hem ticari bot çiftliklerini hem de varsayılan ayarı değiştirmeyen normal oyuncuları kapsar). 88.97%'de herhangi bir tür Steam yasağı bulunmaz; yasağı olan 11%'nin 99.8%'ü ise ticareti hiçbir zaman durdurmayan, sadece görünüşe yönelik topluluk yasaklarıdır. SteamRep ile çapraz kontrol edildiğinde, listelenen dolandırıcıların 67.77%’ü, hile önleme yasakları bir kenara bırakıldığında serbest kalmaktadır. Kayıt tarihi, coğrafi dağılım ve hayatta kalma oranlarına göre yapılan analizlerle — gerçek ölçek, anlatılmamış, ölçülmüş.\n\nAppendix F — Working ledger\n\nRules ledger: clauses against recorded platforms\n\nBir kural seçin; kayıt defterinde, bu kural altında etiketlenmiş kayıtlı platformlar, ana etki alanları, beyan edilen kimlik doğrulama sunucusu ve kaydedilmiş Bağlantı Filtresi sonuçlarıyla birlikte listelenir. Engellenmiş bir web sitesi, oturum açmak için başka bir etki alanı: Kuralı, geriye kalan yola kadar takip edin.\n\n175bağlantılı kayıtlar\nbu kurala\n174 birincil alan adları0 C&D'de geçen ifadeler\nYÖNETMELİK ALINTISI / SSA § 2.G\nTicari Kullanım ve Hesap Ücretlendirme\n“…exploit the Content and Services or any of its parts for any commercial purpose, except as expressly permitted elsewhere in this Agreement (including any Subscription Terms or Rules of Use).”\nKAYITLARI TAKİP EDİN\nPlatform kaydı 175\nÖlçekli rakamlar, kaynaklardan alınan tahminlerdir\n\n175 175'in kayıtlarından\n\nHizmet / ana grup\tAna etki alanı / kayıt merkezi\tGözlemlenen kimlik doğrulama etki alanı / yaş\tÖlçek / kaydedilen yanıt\n\nCasino\n\tcsgoempire.com\n11.3 yearsRegistered 2015-06-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgoempirelogin4.com\n6.2 yearsRegistered 2020-07-20\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustreaper.com\n23.2 yearsRegistered 2003-06-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustreaper.com\n23.2 yearsRegistered 2003-06-24\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustly.com\n12.4 yearsRegistered 2014-05-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustly.com\n12.4 yearsRegistered 2014-05-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette Casino\n\tcsgofast.com\n11.5 yearsRegistered 2015-03-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsteam-login.authtofast.com\n83 daysRegistered 2026-06-30\nRDAP ↗ · authtofast.com (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tduelbits.com\n6.6 yearsRegistered 2020-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nswitchflips.com\n6.4 yearsRegistered 2020-04-21\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opener\n\tfarmskins.com\n10.5 yearsRegistered 2016-03-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsteam.kobal.cc\n9.7 yearsRegistered 2017-01-07\nRDAP ↗ · kobal.cc (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgoluck.com\n9.3 yearsRegistered 2017-05-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgoluck.com\n9.3 yearsRegistered 2017-05-18\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tinsane.gg\n7.5 yearsRegistered 2019-04-02\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.insane.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcs2skin.com\n3.5 yearsRegistered 2023-03-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncs2skin.com\n3.5 yearsRegistered 2023-03-06\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tjuice.gg\n7.9 yearsRegistered 2018-10-19\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nletmeinjuice.com\n2.4 yearsRegistered 2024-04-15\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tggdrop.com\n8.6 yearsRegistered 2018-02-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nggauth.com\n3.4 yearsRegistered 2023-05-03\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Casino\n\thowl.gg\n9.5 yearsRegistered 2017-03-16\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhowl.uno\n41 daysRegistered 2026-08-11\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tchicken.gg\n5.7 yearsRegistered 2021-01-11\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nchicken.gg\n5.7 yearsRegistered 2021-01-11\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgocasino.gg\n2.6 yearsRegistered 2024-02-17\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.csgocasino.gg\n2.6 yearsRegistered 2024-02-17\nWHOISFREAKS ↗ · csgocasino.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Casino\n\thunt.gg\n6.9 yearsRegistered 2019-11-04\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.hunt.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Battles\n\tcsbattle.com\n9.8 yearsRegistered 2016-12-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsbattle.com\n9.8 yearsRegistered 2016-12-10\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskinrave.gg\n3.1 yearsRegistered 2023-08-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinrave.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsdouble.gg\n261 daysRegistered 2026-01-03\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsdouble.gg\n261 daysRegistered 2026-01-03\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustchance.com\n8.0 yearsRegistered 2018-10-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhgfuihd.com\n7.6 yearsRegistered 2019-01-27\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Automation\n\tcobaltlab.tech\n3.5 yearsRegistered 2023-03-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncobaltauth.com\n1.7 yearsRegistered 2025-01-07\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\traided.gg\n171 daysRegistered 2026-04-03\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.raided.gg\n171 daysRegistered 2026-04-03\nIP2WHOIS ↗ · raided.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustneo.gg\n1.3 yearsRegistered 2025-06-20\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustneo.gg\n1.3 yearsRegistered 2025-06-20\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tsplits.gg\n3.7 yearsRegistered 2023-01-23\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsplits.gg\n3.7 yearsRegistered 2023-01-23\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Upgrader\n\tupgrader.pro\n1.2 yearsRegistered 2025-07-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nupgauth.space\n38 daysRegistered 2026-08-14\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskin.fans\n8.2 yearsRegistered 2018-07-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skinfans.com\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\thotpizza.one\n1.8 yearsRegistered 2024-12-07\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhotpizza.one\n1.8 yearsRegistered 2024-12-07\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tg4skins.com\n10.1 yearsRegistered 2016-08-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.g4s.to\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2royal.com\n4.1 yearsRegistered 2022-08-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ntf2auth.com\n5.2 yearsRegistered 2021-07-27\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2hunt.com\n8.7 yearsRegistered 2018-01-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrstspcl.com\n6.1 yearsRegistered 2020-08-08\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2.bet/coinflip\n8.4 yearsRegistered 2018-05-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ntf2.bet\n8.4 yearsRegistered 2018-05-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\topenstars.gg\n131 daysRegistered 2026-05-13\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nopenstars.gg\n131 daysRegistered 2026-05-13\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tskins.com\n25.1 yearsRegistered 2001-08-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skins.com\n25.1 yearsRegistered 2001-08-08\nRDAP ↗ · skins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\twhite.market\n9.6 yearsRegistered 2017-03-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwhite.market\n9.6 yearsRegistered 2017-03-01\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tmoon.market\n7.6 yearsRegistered 2019-02-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmoon.market\n7.6 yearsRegistered 2019-02-27\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tcsfloat.com\n5.2 yearsRegistered 2021-07-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgofloat.com\n11.0 yearsRegistered 2015-09-29\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tskin.land\n4.7 yearsRegistered 2022-01-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skin.land\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\thaloskins.com\n2.8 yearsRegistered 2023-12-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhaloskins.com\n2.8 yearsRegistered 2023-12-10\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCorporate Market\n\tbuff.163.com\n29.0 yearsRegistered 1997-09-15\nRDAP ↗ · 163.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\nbuff.163.com\n29.0 yearsRegistered 1997-09-15\nRDAP ↗ · 163.com (parent)\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\tmarket.csgo.com\n26.6 yearsRegistered 2000-02-07\nRDAP ↗ · csgo.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\ndota2.net\n14.9 yearsRegistered 2011-10-29\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRegulated Market\n\tskinport.com\n8.0 yearsRegistered 2018-09-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinport.app\n6.3 yearsRegistered 2020-06-20\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMarketplace/Swap\n\tskinflow.gg\n3.8 yearsRegistered 2022-11-26\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinflow.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tskin.place\n6.0 yearsRegistered 2020-09-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skin.place\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tskinsmonkey.com\n5.7 yearsRegistered 2021-01-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinsmonkey.com\n5.7 yearsRegistered 2021-01-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCorporate Market\n\tskinbaron.de\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinbaron.com\n10.7 yearsRegistered 2015-12-22\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Market\n\trust.tm\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\ndota2.net\n14.9 yearsRegistered 2011-10-29\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tpirateswap.com\n6.0 yearsRegistered 2020-09-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nlogin.pirateswap.com\n6.0 yearsRegistered 2020-09-22\nRDAP ↗ · pirateswap.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Marketplace\n\tmannco.store\n8.6 yearsRegistered 2018-03-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmannco.store\n8.6 yearsRegistered 2018-03-02\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tskinswap.com\n9.9 yearsRegistered 2016-11-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinswap.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\texeskins.com\n2.1 yearsRegistered 2024-08-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nexeskins.com\n2.1 yearsRegistered 2024-08-14\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tbalticskins.com\n153 daysRegistered 2026-04-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nbalticskins.com\n153 daysRegistered 2026-04-21\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tcs.trade\n8.9 yearsRegistered 2017-11-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncs.trade\n8.9 yearsRegistered 2017-11-14\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\trapidskins.com\n4.5 yearsRegistered 2022-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.rapidskins.com\n4.5 yearsRegistered 2022-03-11\nRDAP ↗ · rapidskins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\ttradeit.gg\n9.1 yearsRegistered 2017-08-21\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nconnect-tradeit.com\n4.6 yearsRegistered 2022-02-23\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\t49skins.com\n3.4 yearsRegistered 2023-04-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.49skins.com\n3.4 yearsRegistered 2023-04-19\nRDAP ↗ · 49skins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tskinvault.gg\n3.4 yearsRegistered 2023-05-06\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinvault.gg\n3.4 yearsRegistered 2023-05-06\nIP2WHOIS ↗ · skinvault.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Trading\n\taim.market\n3.3 yearsRegistered 2023-05-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\naim.market\n3.3 yearsRegistered 2023-05-22\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Sell Portal\n\tskinout.gg\n5.6 yearsRegistered 2021-02-27\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skinout.gg\n5.6 yearsRegistered 2021-02-27\nIP2WHOIS ↗ · skinout.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Trading\n\tntskins.com\n230 daysRegistered 2026-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nntskins.com\n230 daysRegistered 2026-02-03\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Portal\n\tgamerpay.gg\n6.0 yearsRegistered 2020-10-02\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ngamerpay.gg\n6.0 yearsRegistered 2020-10-02\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Scrap Swap\n\tscrap.tf\n14.0 yearsRegistered 2012-09-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nscrap.tf\n14.0 yearsRegistered 2012-09-03\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Cashout\n\tmarketplace.tf\n14.0 yearsRegistered 2012-09-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmarketplace.tf\n14.0 yearsRegistered 2012-09-19\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Cashout\n\tskins.cash\n10.5 yearsRegistered 2016-03-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinscash.live\n6.8 yearsRegistered 2019-12-05\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgo.net\n14.2 yearsRegistered 2012-07-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncn2.easylot.net\n10.0 yearsRegistered 2016-09-03\nRDAP ↗ · easylot.net (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCommunity Hub\n\tcybershoke.net\n6.8 yearsRegistered 2019-11-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.cybershoke.net\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMatchmaker Hub\n\tfastcup.net\n14.6 yearsRegistered 2012-02-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.fastcup.net\n14.6 yearsRegistered 2012-02-16\nRDAP ↗ · fastcup.net (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Analytics\n\tleetify.com\n7.6 yearsRegistered 2019-03-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nleetify.com\n7.6 yearsRegistered 2019-03-01\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Analytics\n\tscope.gg\n7.8 yearsRegistered 2018-12-10\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nscope.gg\n7.8 yearsRegistered 2018-12-10\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tools\n\ttradeupspy.com\n6.5 yearsRegistered 2020-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.tradeupspy.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMarketplace\n\tcs.deals\n9.8 yearsRegistered 2016-12-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.cs.deals\n9.8 yearsRegistered 2016-12-03\nRDAP ↗ · cs.deals (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Price DB\n\tpricempire.com\n6.6 yearsRegistered 2020-01-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\npricempire.com\n6.6 yearsRegistered 2020-01-30\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Blackmarket\n\tFSB Market\n7.2 yearsRegistered 2019-07-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nFSB Market\n7.2 yearsRegistered 2019-07-27\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nReady-Account Hub\n\tz2u.com\n26.9 yearsRegistered 1999-11-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwww.z2u.com\n26.9 yearsRegistered 1999-11-10\nRDAP ↗ · z2u.com (parent)\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Gambling\n\tcsgoroll.com\n11.6 yearsRegistered 2015-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwww.csgoroll.com\nRegistry date unavailableRegistry date unavailable\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\trollbit.com\n11.9 yearsRegistered 2014-11-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrbsnin.com\n3 daysRegistered 2026-09-18\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nLicenced Casino\n\t500.casino\n5.9 yearsRegistered 2020-11-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette/Slots\n\tcsgobig.com\n11.4 yearsRegistered 2015-04-12\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcasedrop.com\n14.8 yearsRegistered 2011-12-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\tbanditcamp.com\n12.2 yearsRegistered 2014-06-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tskinbox.com\n18.8 yearsRegistered 2007-12-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\ttastydrop.com\n6.1 yearsRegistered 2020-08-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette Casino\n\tcsgopolygon.gg\n6.5 yearsRegistered 2020-03-28\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tmagicdrop.ru\n10.3 yearsRegistered 2016-05-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nDice Casino\n\tcsdice.com\n3.8 yearsRegistered 2022-11-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUpgrader Casino\n\tskinodds.com\n1.2 yearsRegistered 2025-06-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgowin.com\n12.0 yearsRegistered 2014-09-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrash Casino\n\tcsgorun.net\n7.3 yearsRegistered 2019-06-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\topenskins.com\n3.6 yearsRegistered 2023-02-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Gambling\n\trustbet.com\n7.6 yearsRegistered 2019-02-07\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgomagic.com\n9.4 yearsRegistered 2017-05-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUpgrader/Contract\n\tcsgobounty.com\n11.5 yearsRegistered 2015-03-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tezskins.com\n27.5 yearsRegistered 1999-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\trustcases.com\n7.2 yearsRegistered 2019-06-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgoreaper.com\n11.1 yearsRegistered 2015-08-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgocases.com\n12.3 yearsRegistered 2014-06-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Upgrader\n\tcsgo-skins.com\n11.2 yearsRegistered 2015-07-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgonet.com\n8.8 yearsRegistered 2017-12-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\twtfskins.com\n9.0 yearsRegistered 2017-10-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Casino\n\tflamecases.com\n10.0 yearsRegistered 2016-09-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tgamedom.com\n11.7 yearsRegistered 2015-01-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Battles\n\tskin.club\n9.0 yearsRegistered 2017-09-04\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsc-auth.net\n7.5 yearsRegistered 2019-04-02\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tdaddyskins.com\n9.9 yearsRegistered 2016-10-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Gambling\n\trustix.gg\n1.7 yearsRegistered 2025-01-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Upgrade\n\tskins.club\n4.2 yearsRegistered 2022-07-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgohouse.org\n146 daysRegistered 2026-04-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskinrave.net\n216 daysRegistered 2026-02-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tbloodycase.gg\n19 daysRegistered 2026-09-02\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nClicker/Upgrade\n\tcsgoclicker.com\n8.3 yearsRegistered 2018-05-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustbet.gg\n4.0 yearsRegistered 2022-09-30\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcs-drop.com\n262 daysRegistered 2026-01-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\thellstore.net\n11.7 yearsRegistered 2015-01-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustloot.com\n354 daysRegistered 2025-10-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgo-case.com\n10.3 yearsRegistered 2016-05-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgogem.com\n9.9 yearsRegistered 2016-10-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\trainbet.com\n8.8 yearsRegistered 2017-11-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nservices.rainbet.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustclash.com\n5.4 yearsRegistered 2021-05-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrash Casino\n\t12cs.fail\n181 daysRegistered 2026-03-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\twww.tf2easy.com\n6.3 yearsRegistered 2020-06-02\nRDAP ↗ · tf2easy.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2blaze.com\n7.6 yearsRegistered 2019-01-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tshuffle.com\n30.1 yearsRegistered 1996-07-31\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tbuff.market\n5.9 yearsRegistered 2020-10-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tavan.market\n8.3 yearsRegistered 2018-05-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Engine\n\tcs.money\n11.0 yearsRegistered 2015-09-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.dota.trade\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tuuskins.com\n2.6 yearsRegistered 2024-01-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Market\n\tyoupin898.com\n6.1 yearsRegistered 2020-08-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tc5game.com\n10.5 yearsRegistered 2016-03-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\twaxpeer.com\n7.3 yearsRegistered 2019-05-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwaxpeer.com\n7.3 yearsRegistered 2019-05-20\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBot Trading\n\tcs.money\n11.0 yearsRegistered 2015-09-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.dota.trade\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUS Marketplace\n\tdmarket.com\n30.2 yearsRegistered 1996-07-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nOfficial Market\n\tsteamcommunity.com/market\n20.3 yearsRegistered 2006-05-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNot an external login site2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Platform\n\tlootfarm.com\n11.9 yearsRegistered 2014-10-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Market\n\trustskins.com\n7.6 yearsRegistered 2019-01-31\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tkrakatoa.com\n26.4 yearsRegistered 2000-05-15\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\tshadowpay.com\n10.1 yearsRegistered 2016-08-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nChinese Powerhouse\n\tigxe.cn\n15.0 yearsRegistered 2011-09-06\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAutomated Swap\n\tswap.gg\n9.6 yearsRegistered 2017-01-29\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCash-out Portal\n\tbitskins.com\n11.2 yearsRegistered 2015-07-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Automation\n\ttf2mart.com\n1.1 yearsRegistered 2025-08-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Auctions\n\tskinbid.com\n10.2 yearsRegistered 2016-06-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Rental\n\tlootbear.com\n8.7 yearsRegistered 2018-01-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Valuation\n\tbackpack.tf\n14.4 yearsRegistered 2012-05-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Botnet\n\tstntrading.eu\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Cashout\n\tskinwallet.com\n18.0 yearsRegistered 2008-09-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nDota 2 Market\n\tdota2market.com\n12.2 yearsRegistered 2014-07-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nServer Network\n\txplay.gg\n5.3 yearsRegistered 2021-06-13\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMatchmaking Portal\n\tesportal.com\n26.8 yearsRegistered 1999-12-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nLATAM Hub\n\tgamersclub.com.br\n11.2 yearsRegistered 2015-06-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tools\n\tepidemic.gg\n4.9 yearsRegistered 2021-11-03\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tcs2stash.com\n3.5 yearsRegistered 2023-03-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tcsgoskins.gg\n6.8 yearsRegistered 2019-12-21\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tsteamanalyst.com\n12.6 yearsRegistered 2014-02-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Exchange\n\tsteamcardexchange.net\n13.3 yearsRegistered 2013-05-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tracker\n\tdotabuff.com\n14.2 yearsRegistered 2012-06-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tracker\n\ttracker.gg\n8.9 yearsRegistered 2017-10-12\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Exchange\n\tfunpay.com\n17.0 yearsRegistered 2009-09-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nGrey Market\n\tplayerauctions.com\n26.3 yearsRegistered 2000-06-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Portal\n\teldorado.gg\n8.0 yearsRegistered 2018-09-12\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Key Market\n\tg2a.com\n24.8 yearsRegistered 2001-12-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Key Market\n\tkinguin.net\n16.8 yearsRegistered 2009-12-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nVirtual Services\n\tg2g.com\n31.1 yearsRegistered 1995-08-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Broker\n\tplayerup.com\n19.3 yearsRegistered 2007-05-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfhub.net\n2.7 yearsRegistered 2023-12-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfaccounts.com\n5.3 yearsRegistered 2021-05-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Shop\n\tbuycsgorank.com\n6.2 yearsRegistered 2020-07-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tcsgosmurfkings.com\n9.3 yearsRegistered 2017-06-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfstore.co\n8.6 yearsRegistered 2018-03-03\nWHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlvlup.com\n9.9 yearsRegistered 2016-11-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlevels.com\n10.6 yearsRegistered 2016-02-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tlevelsteam.com\n79 daysRegistered 2026-07-04\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlevelu.com\n6.0 yearsRegistered 2020-09-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\teloking.com\n12.2 yearsRegistered 2014-07-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\tboosteria.org\n11.9 yearsRegistered 2014-10-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tovergear.com\n14.4 yearsRegistered 2012-04-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tblazingboost.com\n14.2 yearsRegistered 2012-06-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\tdota2boost.com\n2.9 yearsRegistered 2023-10-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tbuyboost.com\n22.4 yearsRegistered 2004-04-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\nSoruşturmanın dayanağıSeçilen kural / analiz ve yorum+\nİspat yükü\n\nSoruşturma, ticari kullanım kısıtlamaları ile burada kayıt altına alınan hizmetler arasındaki uyumsuzluğu ele almaktadır. Her bir faaliyeti sınıflandırın ve bunu sözleşme ihlali olarak nitelendirmeden önce açık bir izin olup olmadığını belirleyin. Topluluk Pazarı ücretleri, her türlü dış ticarete uygulanmaz.\n\nEtiketli kayıt nedir, ne değildir\n\nBir kayıt, dosyada platformun ilk bakışta ilgili madde kapsamına girdiğini gösteren tarihli bir gözlem bulunduğunda etiketlenir. Etiket, kesinleşmiş bir ihlal değildir ve burada listelenen hiçbir platform için kayıtta Valve adresinden alınan açık bir izin belgesi bulunmamaktadır. Bir platformun yetki belgesine sahip olması durumunda, bunun yayınlanmasıyla ilgili giriş çözülür.\n\nKaynaklar ve yöntemTahminler, tanımlar ve kapsam+\n\nYukarıdaki sayılar, seçilen kurala aittir. Kayıt türleri, her platformu bir kez gruplandırır; tam etiketler platform ayrıntılarında gösterilir. Arama ve filtreler bu kural kapsamında uygulanır. Kayıt tarihleri, kaydedilmiş RDAP / WHOIS anlık görüntüsünden alınır. Alt etki alanları, üst etki alanının oluşturulma tarihini kullanır. Yalnızca süre, kesintisiz çalışmayı veya bir kimlik doğrulama yolunu belirlemez. Mevcut kimlik doğrulama ana bilgisayar adları, UTC zaman damgası içeren kaydedilmiş OpenID isteklerinden alınır; çözülmemiş kontroller, eski etiketleri yeniden kullanmaz. Gözlemci, Steam oturum açma işleminden önce durur ve Steam Bağlantı Filtresi durumunu test etmez. Güzergâh gözlemlerini indir ↗ Kayıt defteri sonuçlarını indir ↗\n\nKaynak arşivini keşfedin ↗\nEk G — Red şablonundan ilgili kayda\nDSAR kılavuzu: kanıt talep etme\n\nGDPR’nin 15. maddesini kullanarak API anahtarı oluşturma, hesap kurtarma ve destek erişimiyle ilgili kişisel verileri talep edebilirsiniz. Saklanan kayıtlar, bir eylemi kimin başlattığını ve platformun hangi bilgilere dayandığını ortaya koyabilir.\n\n01\nZaman çizelgenizi koruyun.\n\nHesap bildirimlerini, biletleri, işlem kimliklerini ve tarihleri UTC formatında kaydedin. Hesabı güvence altına alın ve oyun ile işlem için geçerli kurtarma seçeneklerini gözden geçirin.\n\nSteam Ticaret Koruma bilgileri ↗\n02\nSaklanan verilerinizi talep edin.\n\nZaman damgaları, kaynak IP adresleri, anahtar yaşam döngüsü olayları, güvenlik onayları ve hesapla ilgili kurtarma işlemlerini talep edin. Bu veriler sizi ilgilendirdiği durumlarda, destek erişim olaylarını ve alıcıları da ekleyin.\n\n03\nTeslimat kaydını saklayın.\n\nValve'nın gizlilik iletişim kanalını kullanın. Normal yanıt süresi bir aydır; bu ilk ay içinde, en fazla iki ay daha uzatma gerekliliği gerekçelendirilmelidir.\n\nValve gizlilik iletişim yolu ↗ arşivlendi 2026-09-21 ↗\n04\nYanıtları karşılaştırın.\n\nKayıtları zaman çizelgenizle karşılaştırın. Eksikliklerin nedenlerini sorun, ardından gerekirse denetim makamı şikayet yoluna başvurun. Alınan yanıtı aynen koruyun.\n\nKapsam / 15. madde\n\nErişim hakkı, günlük dosyalarındaki veriler de dahil olmak üzere saklanan kişisel verileri kapsar. Bu hak, her türlü iç belgeyi, yeniden oluşturulan kayıtları veya başkalarıyla ilgili sansürsüz verileri garanti etmez. Anlaşılır bir kopya ve herhangi bir kısıtlamanın dayanağını talep edin.\n\nEDPB erişim kılavuzu, §§ 2, 4–6 ↗ · GDPR’nin 12., 15. ve 77. maddeleri ↗ arşivlendi 2026-09-20 ↗\n\nVeri sahibinin bilgi edinme talebiGDPR / 15. Madde\nHesap güvenliği ve erişim kayıtları\n\nGöndermeden önce köşeli parantez içindeki alanları değiştirin.\n\nTo: Valve Privacy Team\nSubject: Article 15 GDPR request — account security records\n\nAccount / SteamID: [YOUR ACCOUNT IDENTIFIER]\nRelevant period (UTC): [START] to [END]\nRelated support tickets: [TICKET REFERENCES]\n\nI request a copy of the personal data concerning me that you retain for this period, including:\n\n1. API-key registration, confirmation, use and revocation events, with available timestamps, source IP addresses, registered domains, device or user-agent information and non-secret key identifiers.\n\n2. Recorded account-recovery actions, password/email/phone changes, Steam Guard removals or resets, confirmation events and the account-related evidence relied on to authorize those actions.\n\n3. Personal data in support-access and administrative-action logs concerning my account, including available dates, purposes, actions and the support entity involved, subject to applicable rights of others.\n\n4. Account-related records used to determine any sanction, and available records of my complaints, reviews and responses.\n\nPlease also provide the applicable processing purposes, categories, recipients, retention periods or criteria, and available information about sources where data were not obtained from me.\n\nWhere processing relies on my consent, please provide the retained record of the consent relied upon and the wording presented at that time.\n\nPlease provide an intelligible electronic copy with time zones and field definitions. Please do not include active credentials or secret tokens. If any requested data are not held, please say so. For any withheld data, please identify the scope and legal basis of the restriction and provide the remainder.\n\nPlease acknowledge receipt and respond within the applicable Article 12 period, explaining any necessary extension. I also ask you to preserve relevant existing records while this request is handled.\n\nName: [YOUR NAME]\nDate: [DATE]\nBir veri merkezi IP'si neleri sağlayabilir?\nBir tutarsızlık, soruşturma yapılması gerektiğini gösteren bir kanıttır.\n\nBu soruşturmada ele alınan barındırma sağlayıcısı örneğinde olduğu gibi, bir veri merkezi ağından kaynaklanan bir API anahtarı talebi, oturum açma kayıtları, onaylar ve kullanıcının zaman çizelgesiyle karşılaştırıldığında önemli olabilir. Bir IP adresi tek başına failin kimliğini belirlemez veya her türlü savunmayı otomatik olarak geçersiz kılmaz. Kayıtlı onayı düşmanca niyetli bir failin sağladığına dair kanıtlar, söz konusu onaya güvenilmesini sorgulatabilir; diğer yasal dayanaklar ve sorumluluk konuları ise ayrı bir analiz gerektirir.\n\nKorunmuş yasaklama ve GDPR şikayetini inceleyin →\nEk H — Wayback Machine arşiv analizi · yayınlanmış destek istatistikleri\nDestek hacmi. Yayınlanmış yanıt süreleri.\nBağlam ve kaynak sınırlamaları\n\nValve, günlük destek istatistiklerini şu adreste yayınlamaktadır: store.steampowered.com/stats/support. Wayback Machine arşivleri, bu sayfanın 2018’den 2026’ya kadar olan tarihsel anlık görüntülerini saklamaktadır. Bu rakamların işaret ettiği iş hacmi-personel sayısı oranı, yayınlanan yanıt süreleri dikkate alındığında bilet başına insan tarafından yapılan inceleme ile tutarsızdır.\n\nKaydedilmiş anlık görüntülerdeki Valve’nin arşivlenmiş destek rakamlarını karşılaştırın. Metodoloji, bu rakamların neleri ölçebileceğini ve neleri ölçemeyeceğini açıklamaktadır.\n\nYayınlanan yanıt süresine göre hacim (2018 → 2026)\nTek bir destek masasında iki kuyruk; 21 adet arşivlenmiş ekran görüntüsüne bakıldığında.\n\nValve, canlı destek rakamlarını şu adreste yayınlamaktadır: store.steampowered.com/stats/support. Aşağıdaki her bir nokta, Internet Archive’ın sayfayı kaydettiği gün o sayfada yer alan alt sınır Valve’un kendisidir — bizim tarafımızdan yapılan bir tahmin değildir. Her iki dizi de aynı birimde ifade edilen aynı ölçüdür; dolayısıyla tek bir eksende yer alırlar ve birbirleriyle doğrudan karşılaştırılarak okunabilirler.\n\nİade talepleri — Valve tutulan paraHesap güvenliği ve kurtarma — kaybettiğiniz hesap\n0 h\n2 h\n4 h\n6 h\n8 h\n10 h\nno captures · 38 months\n2019\n2020\n2021\n2022\n2023\n2024\n2025\n2026\n8 h 44 m\naccount recovery\n52 m\nrefunds\n15 m — one capture only\n49–55 dakikaŞubat 2018’den Ağustos 2026’ya kadar olan her veride geri ödeme alt sınırı. Sekiz buçuk yıllık süre boyunca bu değer altı dakikadan az bir değişiklik gösterirken, günlük geri ödeme hacmi dokuz kat artmıştır.\n2,4 saat → 8,7 saatHesap kurtarma süresinin alt sınırı, Aralık 2022’ye kadar yapılan tüm verim ölçümlerinde bir tanesi hariç 2,4 saat civarında seyretmektedir. 2026’daki üç verim ölçümünde Valve sırasıyla 10,9 saat, 5,8 saat ve 8,7 saat değerlerini yayınlamıştır.\n×2,8 → ×13Valve’un kendi yayınladığı rakamlara göre, geri ödemelere kıyasla geri kazanımın ne kadar daha yavaş olduğu. Beş yıl boyunca sabit kaldıktan sonra fark açılıyor — yavaşlayan kuyruk, masrafı Valve’in değil, kullanıcının üstlendiği kuyruktur.\n\nKaynak: 21 adet Wayback Machine yedeklemesi store.steampowered.com/stats/support, 2018-02-03’dan 2026-08-10’e; çıkarma işlemi VALVE_EVIDENCE_PACK/databases/steam_support_stats_history.json. Şekillerdeki sınırları inceleyin: grafikte daha düşük Valve baskı aralığının sınırı. Yayınlanan üst sınır her iki satırda da daha kötüydü — geri ödemeler 1,5 saat ile 1,5 gün arasında, geri kazanımlar ise 7,0 saat ile 3,6 gün arasında değişiyordu. İki ekran görüntüsü, aynı Valve sayfasının yerelleştirilmiş sürümlerinde — 2018-11-03 Çekçe, 2020-03-25 Fransızca — arşivlenmiştir ve tabloda (cs) ve (fr) olarak işaretlenmiştir; rakamları burada birim adları çevrilmiş ve sayılar yayınlandığı şekliyle gösterilmiş olup, kaynak dizelerin tam metinleri çıkarma dosyasında saklanmıştır. Her yakalama, her iki kuyruk için de bir yanıt süresi yayınlamıştır ve her iki çizgideki hiçbir nokta enterpolasyonla doldurulmamıştır. 2020-10-21 değerindeki tek 15 dakikalık kurtarma süresi, grafikte işaretlenmiş ve bırakılmıştır: bu değer yalnızca bir yakalamada görülmekte olup, başka hiçbir yakalamada buna bir büyüklük sırası kadar yakın bir değer bulunmamaktadır. 2022-12-08 ile 2026-02-01 arasında hiçbir yakalama bulunmamaktadır; kayıtlardaki bu 38 aylık boşluk gölgelendirilmiştir ve üzerine hiçbir çizgi çizilmemiştir. Bu rakamlar yayınlanmış yanıt sürelerini göstermektedir. Bunlar, bir biletin içinde neler olduğunu göstermez ve Valve, bu rakamları değerlendirmek için kullanılabilecek herhangi bir personel sayısını yayınlamamıştır.\n\nHer yakalamayı bir tablo olarak aç\nYayınlandığı haliyle her bir arşivlenmiş ekran görüntüsü\nYakalama\tGeri ödemeler / gün\tGeri ödeme yanıtı\tİyileşme süresi / gün\tKurtarma müdahalesi\n2018-02-03\t98,788\t50,12 dakika ile 1,52 saat arası\t25,662\t2,51 saat ile 1,80 gün arası\n2018-05-07\t60,494\t53,83 dakika ile 1,47 gün arası\t24,226\t2,45 saat ile 2,22 gün arası\n2018-08-02\t69,084\t50,27 dakika ile 1,59 saat arası\t28,953\t2,44 saat ile 22,17 saat arası\n2018-11-03 (cs)\t63,410\t49,28 dakika ile 1,54 saat arası\t33,910\t2,42 saat ile 1,31 gün arası\n2019-02-01\t76,305\t50,13 dakika ile 1,52 saat arası\t35,164\t2,44 saat ile 2,04 gün arası\n2019-05-18\t78,951\t51,03 dakika ile 3,12 saat arası\t27,514\t2,46 saat ile 20,39 saat arası\n2019-09-07\t78,941\t50,65 dakika ile 1,66 saat arası\t28,812\t2,42 saat ile 13,59 saat arası\n2019-12-13\t69,589\t50,77 dakika ile 1,55 saat arası\t25,322\t2,45 saat ile 1,13 gün arası\n2020-03-25 (fr)\t139,278\t49,45 dakika ile 1,53 saat arası\t32,302\t2,48 saat ile 3,62 gün arası\n2020-06-26\t278,504\t48,98 dakika ile 2,29 saat arası\t20,343\t2,39 saat ile 6,99 saat arası\n2020-10-21\t107,633\t50,80 dakika ile 1,54 saat arası\t20,688\t15,33 dakika ile 8,62 saat arası\n2021-03-20\t158,956\t50,80 dakika ile 1,64 saat arası\t25,760\t2,34 saat ile 11,62 saat arası\n2021-06-26\t547,907\t51,93 dakika ile 6,73 saat arası\t29,728\t2,40 saat ile 15,63 saat arası\n2021-10-10\t170,103\t51,88 dakika ile 3,25 saat arası\t23,989\t2,39 saat ile 13,05 saat arası\n2022-01-31\t354,386\t53,65 dakika ile 8,09 saat arası\t24,391\t2,42 saat ile 15,29 saat arası\n2022-05-09\t172,555\t51,83 dakika ile 1,65 saat arası\t23,289\t2,41 saat ile 16,90 saat arası\n2022-09-05\t153,453\t53,67 dakika ile 4,15 saat arası\t23,594\t2,45 saat ile 1,22 gün arası\n2022-12-08\t181,075\t54,83 dakika ile 6,67 saat arası\t27,111\t2,46 saat ile 18,89 saat arası\n2026-02-01\t317,762\t50,30 dakika ile 1,52 saat arası\t47,197\t10,91 saat ile 21,30 saat arası\n2026-05-09\t246,776\t50,12 dakika ile 1,52 saat arası\t35,264\t5,81 saat ile 15,60 saat arası\n2026-08-10\t373,244\t52,05 dakika ile 2,07 saat arası\t45,319\t8,73 saat ile 16,52 saat arası\nANA GÖZLEM:\nBoydan boya 21 Wayback arşiv kaydı 2018-02-03 ile 2026-08-10 arasında değişen günlük geri ödeme başvuruları, 60,494 (Mayıs 2018) – 547,907 (Haziran 2021) — bir 9,1× spread. 2026 yılı rakamı 373,244’dır (Şubat 2018 verilerine kıyasla (+278%)).\nAynı dokuz yıl boyunca, geri ödeme yanıt süresi için açıklanan alt sınır hiçbir zaman bir 49–55 dakika aralık: Toplam hareket süresi altı dakikanın altındayken, bunun ardındaki iş yükü dokuz kat arttı.\nBir kişi her bileti sadece 5 saniye bile okusa, günde 373,244 bilet işlenmesi (mevcut durum) şu kadar zaman alır: 24 saat kesintisiz çalışan 22 temsilci sadece bunları açıp kapatmak için; en yüksek seviyede (547,907, Haziran 2021) bu rakam 32’ye yükseliyor.\nYayınlanan yanıt süresi, bilet başına işlem süresini yansıtıyorsa (~52 dakika/bilet), bundan çıkarılabilecek eşzamanlı personel sayısı şu mertebede olurdu: 13,500 temsilci mevcut hacimde ve tepe noktasında ~20,000. Valve'in destek personel sayısı ile ilgili kaynaklı bir rakam bulunamamıştır; burada herhangi bir rakam varsayılmamıştır.\nAşağıda belirtilenler: İş hacmi-çalışan sayısı oranı, yayınlanan yanıt süreleri çerçevesinde bilet başına insan tarafından yapılan incelemeyle tutarlı değildir. Rakamlar, büyük ölçüde otomatikleştirilmiş bir ilk inceleme süreciyle tutarlıdır; insan tarafından incelenen biletlerin oranı ise yayınlanmamıştır.\nBu durumun GDPR uyumluluğu açısından önemi nedir?\n\nGDPR’nin 22. maddesi, talep üzerine insan tarafından incelenme hakkı tanınmaksızın, önemli hukuki sonuçlar doğuran, tamamen otomatikleştirilmiş bireysel karar vermeyi yasaklamaktadır. Eğer Steam Destek kararları (biletlerin kapatılması, hesap işlemleri, veri taleplerinin reddi) tamamen otomatik komut dosyaları tarafından alınıyorsa, kullanıcıyı “önemli ölçüde etkileyen” bu tür her karar, Madde 22’yi ihlal edebilir.\n\nBilet HT-2YBP-F7JP-D4VB (18. Madde) üç gün sonra, şablon bir sevk ile ve atıfta bulunulan yasal dayanakla ilgili herhangi bir değerlendirme yapılmaksızın kapatılmıştır. Bir kişinin bunu inceleyip incelemediği, bildirimden anlaşılamamaktadır; bu, denetim makamının 22. Madde ve 15. Maddenin (1)(h) bendi uyarınca Valve’a yöneltebileceği bir sorudur.\n\nKaynak: store.steampowered.com/stats/support adresinin Wayback Machine anlık görüntüleri (2018-02-03, 2021-06-26, 2026-08-10) — veriler VALVE_EVIDENCE_PACK/databases/steam_support_stats_history.json dosyasına aktarılmıştır (21 anlık görüntü, 2018–2026). Not: \"~52 dakika\" yanıt süresi, iade kategorisi için alt sınırdır; aynı anlık görüntülerde hesap güvenliği yanıt süresi 2,4–16,5 saat arasındaydı. 2021-06-26, tekdüze bir orta nokta değil, tüm zamanların en yüksek seviyesidir (547,907 geri ödeme talebi); hacim 2020–2021'de ~6 kat arttı, ardından kısmen düştü ve 2026'da 373 bin seviyesine geri döndü.\nEk I — Veri kümesinin kapsamı · tekrarlanabilir sayılar\nKayıtları sayın. Kapsamı kontrol edin.\nBağlam ve kaynak sınırlamaları\n\nKayıtları sayın, ardından iddiaları doğrulayın: Aşağıdaki tüm rakamlar, yayınlanmış dosyalardan yeniden hesaplanabilir.\n\nAltta yatan veri kümelerini inceleyin, sayıları yeniden hesaplayın ve kaynak satırları tekil olaylardan ayırt edin.\n\nAna CSV dosyası şunları içerir: 40,448 satır. Bunlardan, 36,516 Discord-AntiScam kimlik avı beslemesinden gelmektedir. Geri kalanlar 3,932 Bu satırlar GitHub, inceleme raporları, arama sonuçları, forum içerikleri ve diğer kaynakları kapsayarak, bildirilen topluluk konuları ve güvenlik raporlarının kapsamlı bir dizinini sunar.\n\nBu CSV dosyasında, 1,690 satır, geçmişteki kullanıcı sorunlarını ve güvenlik açığı açıklamalarını temsil eden \"Yama Uygulanmamış Güvenlik Açığı\" koleksiyon etiketi altında sınıflandırılmıştır. Bu raporları takip etmek, her bir konunun kendine özgü derleme zaman çizelgesini ve genel yama geçmişini incelemek anlamına gelir.\n\n16,319 kayıtlık aranabilir arşiv, belirli kullanıcı iddialarının ve olay raporlarının yerel düzeyde titizlikle incelenmesi amacıyla tasarlanmış, kendi manifestosuna sahip, ayrı ve özenle derlenmiş bir yapıdır.\n\nGüvenilir bir denetim izi oluşturmak için, kullanıcıların bildirdiği her kayıt, belgelenmiş derleme zaman çizelgeleri ve geçmiş yama günlükleriyle karşılaştırılarak doğrulanmalıdır.\n\nAyrı olarak tutulan Bölüm II koleksiyon kayıtları 231,829 benzersiz ilan kimliği, bunlara otomatik kayıt kategorisinde yer alan 33,509 ve doğrulanmamış transferler olarak işaretlenen 198,320 de dahildir. Giriş dosyasının SHA-256 değeri, saklanan ölçümle eşleşmektedir. Bu sayılar, kesinleşmiş işlem değerleri veya doğrulanmış hırsızlık toplamlarından ziyade, listeleme girişimlerini ve gözlemlenen transferleri yansıtmaktadır; bu da, kesin ekonomik etkiyi ölçmek için birincil platform kayıtlarına duyulan ihtiyacı vurgulamaktadır. Ölçümleri ve hash değerlerini listeleme ↗\n\nCSV'yi İyice Öğrenin ↗ · Arama yapılabilen arşiv listesi ↗ · Kaynak kayıtlarını incele ↗\n\nEk J — Bu araştırma hakkında\nValve herhangi bir yaptırım kaydı yayınlamamaktadır. Bir tane yaptık.\n\nBağımsız. Ticari amaç gütmeyen. Yalnızca kamuya açık veriler kullanılarak oluşturulmuştur. Düzenleyici kurumlara sunulmuştur.\n\n88.97%otomasyon filosu dokunulmamış — hiçbir türde yasak yok\n67.77%51,732'dan fazla hüküm giymiş dolandırıcı serbest kalıyor\n$26.8M+sınırlandırılmamış filo tarafından yapılan mağaza harcamalarının alt sınırı\n3.6%Valve'un Bağlantı Filtresi tarafından engellenen kumar sitelerinin alan adları\n8 yılkayıt altına alınmış güvenlik olayları\n\nBu nedir? Valve Şirketi’nin Steam platformuna ilişkin bir adli inceleme dosyası — platformun yaptırım geçmişi, kart toplama ekonomisi, yasal çerçevesi ve kumar operatörlerinin Steam’ün kendi OpenID aktarım sistemi aracılığıyla kullandığı kimlik doğrulama altyapısı. Her rakam, iki kaynaktan doğrulanabilir: Valve'in kendi halka açık API'si ve bu araştırma ile birlikte yayınlanan veri kümeleri.\n\nKimler için uygundur. Valve üzerinde yetki sahibi düzenleyici kurumlar — Hollanda’nın GDPR denetim kurumu, FinCEN, SEC, DSA Dijital Hizmetler Koordinatörü, UOKiK ve Steam ile bağlantılı finansal akışları inceleyen tüm kolluk kuvvetleri. Ayrıca gazeteciler, araştırmacılar ve kalıcı hesap engellemesi uygulanan, geri ödeme talebi reddedilen veya envanterleri çalınan ve itiraz hakkı olmadığı söylenen tüm kullanıcılar için.\n\nTek talep. Valve bu verileri tam doğrulukla saklamaktadır — yasaklama nedenleri de dahil olmak üzere, tam kimlik alanı, gerçek zamanlı olarak. Bu dosyadaki her sorguyu saniyeler içinde çalıştırabilir ve bunların hiçbirini yayınlamamayı tercih etmiştir. Yetkili makamlar için soru basittir: Neden olmasın?\n\nYazarların iddia etmedikleri şey. Bu çalışma sırasında hiçbir üçüncü taraf platformda Steam’ye giriş işlemi tamamlanmamıştır. Sağlanan OpenID URL’si, tamamlanmış bir giriş işlemini değil, istek parametrelerini belirler. Kayıt edilebilir ayrı bir alan adı, tek başına kaçırma eyleminin kanıtı değildir. Kayıt tarihleri, bir ana bilgisayarın bir OpenID isteğinde ilk kez ne zaman görünebileceğine dair alt sınırları belirtir; sürekli kullanım olduğunu kanıtlamazlar. Yazarlar, Valve'ın ne bildiğini veya neyi amaçladığını iddia etmemektedir: Valve ile ilgili her ifade, tarihli bir kamuya açık belgeye veya tarihli bir gözleme dayanmaktadır. Bir iddianın kaynak belgeyle desteklenemediği durumlarda, söz konusu ifade metinden çıkarılmıştır.\n\nBiz kimiz?\n\nPhishDestroy — bağımsız araştırmacılar. Valve Şirketi veya burada adı geçen herhangi bir platformla hiçbir bağlantısı yoktur. Bir adet Steam hesabı, yalnızca 18. bölümdeki GDPR talebini belgelemek amacıyla kullanılmıştır.\n\nYasal uyarı\n\nTicari amaç gütmeyen, merkezi olmayan, kamu yararına yapılan bir araştırma. Tüm veriler “olduğu gibi” sunulmakta olup hiçbir garanti verilmemektedir. Bu yayın, adli bir karar niteliğinde değildir.\n\nKAMU MALI\nLisanslama\n\nTüm haklar insanlığa devredilmiştir. Çoğaltma, uyarlama, yayınlama — kaynak gösterme zorunluluğu yoktur. OFAC bölgesi erişimi: yasaktır. Tam lisans ve sorumluluk reddi beyanı →",
        "headings": [
          {
            "level": 2,
            "id": "briefing-heading",
            "text": "Kural. Rekor. Cevaplanmamış sorular."
          },
          {
            "level": 2,
            "id": null,
            "text": "Washington Eyaleti Kumar Komisyonu’na açık mektup"
          },
          {
            "level": 3,
            "id": "wsgc-public-address-title",
            "text": "On gün, on yıla dönüştü.Kaydı yeniden açın."
          },
          {
            "level": 2,
            "id": null,
            "text": "Site engellenmiş. Oturum açma sayfası ise engellenmemiş."
          },
          {
            "level": 3,
            "id": null,
            "text": "Şekil 3.1 — Çizilmiş iki güzergâh."
          },
          {
            "level": 3,
            "id": null,
            "text": "Büyük Resim Tuzağı: Link Filter, bir koruma kalkanı değil, sadece görünüşte uyum sağlama çabasıdır"
          },
          {
            "level": 3,
            "id": null,
            "text": "Engellenmiş bir ana etki alanı ile engeli kaldırılmış bir kimlik doğrulama sunucusunun bir araya gelmesi, oturum açma yolunu açık bırakır — ve bu yol yıllarca açık kalır."
          },
          {
            "level": 3,
            "id": null,
            "text": "Arka plan: Steam nedir ve bu bağlamda neden önemlidir?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve'ın Yaptığı Şey: Etki Alanı Engelleme"
          },
          {
            "level": 3,
            "id": null,
            "text": "Proxy Etki Alanı Nedir?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Kritik Nokta: Her İstekte Kimlik Doğrulama Sunucusu Steam Değerine Gönderiliyor"
          },
          {
            "level": 3,
            "id": null,
            "text": "Bunun Kanıtladığı Şey"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam'in içinde, Valve'un listesi tek listedir."
          },
          {
            "level": 3,
            "id": null,
            "text": "Bağlantı filtresi korumasının atlanması"
          },
          {
            "level": 3,
            "id": null,
            "text": "Big Picture web tarayıcısı, oturum açma çerezlerini sızdırıyor ve hassas bilgileri ifşa ediyor (hesap ele geçirilmesine yol açabilir)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Antivirüs programı yüklü olan bir reşit olmayan kişi için bunun anlamı nedir?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Alan adının yaşı.Gözlemin tarihi."
          },
          {
            "level": 2,
            "id": null,
            "text": "Bir uç nokta kapatıldı. Genel izleme bir anahtarını kaybetti."
          },
          {
            "level": 3,
            "id": null,
            "text": "Elektrik Kesintisi Öncesi Dönem"
          },
          {
            "level": 3,
            "id": null,
            "text": "Değişiklikten sonra"
          },
          {
            "level": 2,
            "id": null,
            "text": "Tek oturum. Kullanıcının gördüğünden daha fazla erişim."
          },
          {
            "level": 3,
            "id": null,
            "text": "1. Yetersiz iki aşamalı kimlik doğrulama"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. En Az Ayrıcalık İlkesi’nin Uygulanmaması"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. Oturum Yönetimi Sorunları"
          },
          {
            "level": 3,
            "id": null,
            "text": "4. Kimlik Doğrulama Sunucularının Etki Alanı Düzeyinde Engellenmesi Teknik Olarak Mümkündü"
          },
          {
            "level": 3,
            "id": "integration-paradox-title",
            "text": "Valve her gün bu kurallara göre derleniyor. Ancak burada bu kurallara göre derlenemedi."
          },
          {
            "level": 4,
            "id": null,
            "text": "GitHub'daki Ayrıntılı Kapsamlar ile Valve Steam Web API'si Karşılaştırması"
          },
          {
            "level": 2,
            "id": null,
            "text": "Etkileşimli Güvenlik Açığı Sömürme ve Kontrol Ele Geçirme Simülatörü"
          },
          {
            "level": 2,
            "id": null,
            "text": "Dizinin ardındaki uç noktalar."
          },
          {
            "level": 2,
            "id": null,
            "text": "İşaretlenmiş bir kutucuk. Kimin eylemi?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve \"Ticaret İkamesi\"ni Nasıl Sonunda Ortadan Kaldırdı — Ve Neden 7 Yıl Boyunca Geçici Çözümlere Başvurulmak Zorunda Kalındı"
          },
          {
            "level": 4,
            "id": null,
            "text": "Avatar ve İsim Bekleme Süresi (Şubat 2024)"
          },
          {
            "level": 4,
            "id": null,
            "text": "7 Günlük CS2 İşlem Yön Değişimi (Temmuz 2025)"
          },
          {
            "level": 4,
            "id": null,
            "text": "API için Zorunlu Mobil Bildirim (Aralık 2023)"
          },
          {
            "level": 4,
            "id": null,
            "text": "Hesap Süresi ve Ad Afişleri (2022–2024)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Onların kurallar kitabı. Kayıtlı platformlar."
          },
          {
            "level": 3,
            "id": "enforcement-focus-title",
            "text": "Tek bir kural kitabı. Eşitsiz uygulama."
          },
          {
            "level": 4,
            "id": null,
            "text": "Otomasyon"
          },
          {
            "level": 4,
            "id": null,
            "text": "Ticari kullanım"
          },
          {
            "level": 4,
            "id": null,
            "text": "VPN ve konum gizleme"
          },
          {
            "level": 4,
            "id": null,
            "text": "Bağlantı gizleme"
          },
          {
            "level": 4,
            "id": null,
            "text": "Destek ekibi dosyayı kapattığında kararı kim inceler?"
          },
          {
            "level": 2,
            "id": null,
            "text": "Bir otomasyon API’si. Otomasyona karşı bir kural."
          },
          {
            "level": 3,
            "id": null,
            "text": "\"Oyun Geliştiricisi\" Yanılgısı"
          },
          {
            "level": 4,
            "id": null,
            "text": "Otomasyon Çelişkisi"
          },
          {
            "level": 4,
            "id": null,
            "text": "Ticaret akışında sunucu tarafında yer alan bir pozisyon"
          },
          {
            "level": 2,
            "id": null,
            "text": "On gün talep edildi. Hesap verilmesi gereken on yıl."
          },
          {
            "level": 3,
            "id": "letter-company",
            "text": "VALVE ŞİRKETİ"
          },
          {
            "level": 3,
            "id": null,
            "text": "On gün.Peki sonra ne olacak?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Belirtilen geri dönüş sunucusunu takip edin."
          },
          {
            "level": 3,
            "id": "washington-record-heading",
            "text": "İki son tarih. Yanıtlanmamış tek bir uygulama standardı."
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve, kumar sitelerine 10 gün süre tanır"
          },
          {
            "level": 4,
            "id": null,
            "text": "Washington tuşuna basın Valve"
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve bu suçlamayı reddediyor"
          },
          {
            "level": 4,
            "id": null,
            "text": "Eylül 2026’da gözlemlenen güzergâhlar"
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve'nin yanıt vermesinden on sekiz ay sonra, düzenleyici kurum bunu hâlâ bir niyet olarak nitelendirdi."
          },
          {
            "level": 3,
            "id": null,
            "text": "“10 Günlük Bildirim On Yılı”: Adı Geçen 23 Tesisin Adli Hayatta Kalma Denetimi"
          },
          {
            "level": 4,
            "id": null,
            "text": "10 Günlük Uyarılar'dan Denizaşırı Holdinglere: Milyarlarca Dolarlık Cirolar"
          },
          {
            "level": 2,
            "id": null,
            "text": "Ana bilgisayar adı, istekte zaten mevcut."
          },
          {
            "level": 3,
            "id": null,
            "text": "Belgelenmiş ve raporlanmış emsal kararlar"
          },
          {
            "level": 3,
            "id": null,
            "text": "Kayıt tarihinin neleri gösterdiği ve neleri göstermediği"
          },
          {
            "level": 3,
            "id": null,
            "text": "Karşılaştırmalı Denetim: API Uyumluluk Standartları"
          },
          {
            "level": 2,
            "id": "market-thesis-heading",
            "text": "0 dışındaki fiyat farkı"
          },
          {
            "level": 2,
            "id": null,
            "text": "Fiyat farkı ölçülebilir."
          },
          {
            "level": 3,
            "id": null,
            "text": "Bu rakamın gösterdiği şey"
          },
          {
            "level": 3,
            "id": null,
            "text": "Birçok mekan, Steam'dan daha yüksek bir dolar tutarı belirtmektedir."
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam, teklif sayısı açısından hâlâ başı çekiyor."
          },
          {
            "level": 3,
            "id": null,
            "text": "Ticari ekosistem gözümüzün önünde."
          },
          {
            "level": 2,
            "id": null,
            "text": "Güvenlik önlemlerini kim sıfırlayabilir?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Hesabın güvenliğini devre dışı bırakan bir kurtarma bileti ve bildirilen $10,000 tutarındaki kayıp"
          },
          {
            "level": 3,
            "id": null,
            "text": "Envanterin ötesinde."
          },
          {
            "level": 3,
            "id": "theft-ledger-title",
            "text": "Valve, otuz üç ay arayla iki kez kapıyı açtı. Kapı hiç kapanmadı."
          },
          {
            "level": 4,
            "id": null,
            "text": "Defterde yazan şey, tek bir vakanın bile ifade edemediği bir şeydir."
          },
          {
            "level": 3,
            "id": null,
            "text": "Gizlilik, teknik hesap verebilirlikle bir arada olmalıdır."
          },
          {
            "level": 2,
            "id": null,
            "text": "Paranın izini sürün. İşlemleri birbirinden ayırın."
          },
          {
            "level": 3,
            "id": null,
            "text": "Paranın gerçekte nereye aktığı."
          },
          {
            "level": 3,
            "id": null,
            "text": "Önce faaliyeti, ardından yükümlülüğü sınıflandırın."
          },
          {
            "level": 3,
            "id": null,
            "text": "Gelirlerin izlenmesi, bilgi ve destek."
          },
          {
            "level": 2,
            "id": null,
            "text": "Dijital Hizmetler Yasası: bilgiyi kayıt altına almak"
          },
          {
            "level": 3,
            "id": null,
            "text": "On günlük bir talep."
          },
          {
            "level": 3,
            "id": null,
            "text": "DSA zaman aralığı."
          },
          {
            "level": 3,
            "id": null,
            "text": "Süre için bir bildirim dizisi gereklidir."
          },
          {
            "level": 3,
            "id": null,
            "text": "yıllık dünya çapındaki cirosunun"
          },
          {
            "level": 2,
            "id": null,
            "text": "Reşit olmayanlar: Steam ile oturum açma, yaş kontrolü değildir"
          },
          {
            "level": 3,
            "id": null,
            "text": "İşleciyi ve veriyi belirleyin."
          },
          {
            "level": 3,
            "id": null,
            "text": "Giriş yapma aşamasından para yatırma aşamasına kadar olan süreci kaydedin."
          },
          {
            "level": 2,
            "id": null,
            "text": "İstek. Yanıt. Eksik karşılaştırma."
          },
          {
            "level": 3,
            "id": null,
            "text": "Kayıtlar mevcuttur; veri sahibi bu kayıtları almamıştır."
          },
          {
            "level": 2,
            "id": null,
            "text": "Platformun kendi mimarisine aykırı Abone Sözleşmesi"
          },
          {
            "level": 3,
            "id": null,
            "text": "Pazarın üst sınırı ve ticari kullanım yasağı"
          },
          {
            "level": 3,
            "id": null,
            "text": "API anahtarı güvenlik açığı, kullanıcı ihmali değil, platform tasarımına ilişkin bir sorun olarak değerlendirilmelidir"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve her oturum açılışında kimlik doğrulama ana bilgisayar adını alır"
          },
          {
            "level": 3,
            "id": null,
            "text": "Arşivlenmiş şikayetlerdeki eğilim"
          },
          {
            "level": 3,
            "id": null,
            "text": "Bu dosyayı inceleyen bir mahkeme, SSA’yı tek başına değerlendirmez."
          },
          {
            "level": 2,
            "id": null,
            "text": "Bulgular. Talep ettiğimiz kayıtlar."
          },
          {
            "level": 2,
            "id": null,
            "text": "Delil Notu — Kaynak 1 tarafından sağlanan materyal"
          },
          {
            "level": 2,
            "id": null,
            "text": "Oluşturulan PDF’deki sansürleme sadece görsel niteliktedir: sansürlenen metin hâlâ çıkarılabilir durumdadır"
          },
          {
            "level": 2,
            "id": null,
            "text": "Destek ve Hukuki Yazışmalara İlişkin Ekler"
          },
          {
            "level": 2,
            "id": null,
            "text": "Seçilmiş birincil kaynaklar"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-01",
            "text": "2016 yılında talep edilen donanım anahtarları"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-02",
            "text": "Etkili bir vazgeçme seçeneği bulunmayan hata raporları"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-03",
            "text": "Valve'ye bildirilen Auth-ticket suistimali"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-01",
            "text": "44 adet ihtilaflı Market alımı"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-02",
            "text": "Kalıcı yasaklama ve temyiz hakkının kaldırılması"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-03",
            "text": "Bir kurtarma sıfırlaması ve bildirilen $10,000 tutarındaki kayıp"
          },
          {
            "level": 2,
            "id": null,
            "text": "ArchiSteamFarm ve otomasyon hükmü"
          },
          {
            "level": 2,
            "id": null,
            "text": "Rules ledger: clauses against recorded platforms"
          },
          {
            "level": 3,
            "id": "ledger-title",
            "text": "Ticari Kullanım ve Hesap Ücretlendirme"
          },
          {
            "level": 3,
            "id": "lw-register-title",
            "text": "Platform kaydı 175"
          },
          {
            "level": 4,
            "id": null,
            "text": "İspat yükü"
          },
          {
            "level": 4,
            "id": null,
            "text": "Etiketli kayıt nedir, ne değildir"
          },
          {
            "level": 2,
            "id": null,
            "text": "DSAR kılavuzu: kanıt talep etme"
          },
          {
            "level": 3,
            "id": null,
            "text": "Zaman çizelgenizi koruyun."
          },
          {
            "level": 3,
            "id": null,
            "text": "Saklanan verilerinizi talep edin."
          },
          {
            "level": 3,
            "id": null,
            "text": "Teslimat kaydını saklayın."
          },
          {
            "level": 3,
            "id": null,
            "text": "Yanıtları karşılaştırın."
          },
          {
            "level": 3,
            "id": null,
            "text": "Hesap güvenliği ve erişim kayıtları"
          },
          {
            "level": 3,
            "id": null,
            "text": "Bir tutarsızlık, soruşturma yapılması gerektiğini gösteren bir kanıttır."
          },
          {
            "level": 2,
            "id": null,
            "text": "Destek hacmi. Yayınlanmış yanıt süreleri."
          },
          {
            "level": 3,
            "id": null,
            "text": "Tek bir destek masasında iki kuyruk; 21 adet arşivlenmiş ekran görüntüsüne bakıldığında."
          },
          {
            "level": 2,
            "id": null,
            "text": "Kayıtları sayın. Kapsamı kontrol edin."
          },
          {
            "level": 2,
            "id": null,
            "text": "Valve herhangi bir yaptırım kaydı yayınlamamaktadır.\nBir tane yaptık."
          }
        ],
        "links": [
          "https://dotesports.com/counter-strike/news/csgo-lounge-billion-bets-3896",
          "https://store.steampowered.com/agreement/?l=english",
          "http://web.archive.org/web/20260921022032/https://store.steampowered.com/agreement/?l=english",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-all-results.json",
          "https://blog.counter-strike.net/expresstrade/",
          "http://web.archive.org/web/20260307161538/https://blog.counter-strike.net/expresstrade/",
          "https://wsgc.wa.gov/news/2016/washington-state-gambling-commission-orders-valve-stop-skins-gambling",
          "http://web.archive.org/web/20260520012601/https://wsgc.wa.gov/news/2016/washington-state-gambling-commission-orders-valve-stop-skins-gambling",
          "https://fr.scribd.com/document/328063293/Valve-s-Oct-18th-response-to-Washington-State-Gambling-Commission-s-cease-and-desist",
          "https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921021947/https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921022628/https://steamcommunity.com/linkfilter/?url=https:%2F%2Frollbit.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rbsnin.com.20260921T021120Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rollbit.com.json",
          "http://web.archive.org/web/20260921022740/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fskin.club",
          "http://web.archive.org/web/20260921022842/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fsc-auth.net",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skin.club.json",
          "http://web.archive.org/web/20260921022603/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fhowl.gg",
          "http://web.archive.org/web/20260921022636/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fhowl.uno",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/howl.gg.json",
          "http://web.archive.org/web/20260921022840/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fduelbits.com",
          "http://web.archive.org/web/20260921022901/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fswitchflips.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/duelbits.com.json",
          "http://web.archive.org/web/20260921022758/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgofast.com",
          "http://web.archive.org/web/20260921022847/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fauthtofast.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgofast.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/farmskins.com.20260921T025840Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/steam.kobal.cc.20260921T025844Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/farmskins.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cobaltlab.tech.20260921T041604Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cobaltauth.com.20260921T041608Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/cobaltlab.tech.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgo.net.20260921T041619Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cn2.easylot.net.20260921T041623Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgo.net.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/ggdrop.com.20260921T041637Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/ggauth.com.20260921T041641Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/ggdrop.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rustchance.com.20260921T041703Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/hgfuihd.com.20260921T041706Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rustchance.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skin.fans.20260921T041710Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.skinfans.com.20260921T041713Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skin.fans.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinport.com.20260921T041724Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinport.app.20260921T041728Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skinport.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skins.cash.20260921T041731Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinscash.live.20260921T041735Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skins.cash.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2hunt.com.20260921T041739Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rstspcl.com.20260921T041742Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tf2hunt.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgogem.com.20260922T192355Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/api.csgem.com.20260922T192358Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-2026-09-22.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/gamdom.com.20260922T192326Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/login.gambldom.com.20260922T192330Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/12cs.fail.20260922T192347Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/fail.games.20260922T192351Z.html",
          "http://web.archive.org/web/20260921022953/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgoempire.com",
          "http://web.archive.org/web/20260921022947/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgoempirelogin4.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgoempire.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cs.money.20260921T021131Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.dota.trade.20260921T021134Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/cs.money.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csfloat.com.20260921T041612Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgofloat.com.20260921T041615Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csfloat.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/g4skins.com.20260921T041630Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.g4s.to.20260921T041634Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/g4skins.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/juice.gg.20260921T041644Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/letmeinjuice.com.20260921T041648Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/juice.gg.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/market.csgo.com.20260921T041652Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2.net.20260921T041655Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/market.csgo.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rust.tm.20260921T041659Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rust.tm.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgolounge.com.20260922T192333Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2.net.20260922T192340Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2lounge.com.20260922T192337Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinbaron.de.20260921T041717Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinbaron.com.20260921T041721Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skinbaron.de.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2royal.com.20260921T041746Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2auth.com.20260921T041750Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tf2royal.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tradeit.gg.20260921T041753Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/connect-tradeit.com.20260921T041757Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tradeit.gg.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/upgrader.pro.20260921T041801Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/upgauth.space.20260921T041804Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/upgrader.pro.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-recheck-2026-09-21.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/domain-registration.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wayback-snapshots.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-2026-09-22c.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/master_registry.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/longitudinal-steam-phishing-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-steam-phishing-100.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-coverage-2026-09-22.json",
          "https://blog.csfloat.com/how-floatdb-tracks-items/",
          "http://web.archive.org/web/20260921022415/https://blog.csfloat.com/how-floatdb-tracks-items/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/platform-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/platforms-removed.json",
          "https://hackerone.com/reports/291750",
          "http://web.archive.org/web/20251116185046/https://hackerone.com/reports/291750",
          "https://hackerone.com/reports/1079561",
          "http://web.archive.org/web/20260924181830/https://hackerone.com/reports/1079561",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/hackerone-reports.json",
          "https://phishdestroy.io/steam_dossier/tr/steam_enforcement_evidence.html#support-records",
          "https://www.darknavy.org/blog/exploiting_steam_usual_and_unusual_ways_in_the_cef_framework/",
          "https://steamcommunity.com/groups/SteamClientBeta/discussions/0/3365901765276206401/",
          "http://web.archive.org/web/20250804051514/https://steamcommunity.com/groups/SteamClientBeta/discussions/0/3365901765276206401/",
          "https://www.chromium.org/developers/design-documents/safebrowsing/",
          "http://web.archive.org/web/20260821101616/https://www.chromium.org/developers/design-documents/safebrowsing/",
          "https://www.chromium.org/developers/how-tos/api-keys/",
          "http://web.archive.org/web/20260830122831/https://www.chromium.org/developers/how-tos/api-keys/",
          "https://github.com/Homebrew/homebrew-cask/issues/193814",
          "https://testsafebrowsing.appspot.com/",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/domain-registration.json",
          "https://phishdestroy.io/steam_dossier/tr/AUTH_AUDIT.md",
          "https://datatracker.ietf.org/doc/rfc6749/",
          "https://docs.cloud.google.com/docs/authentication/api-keys",
          "https://listings.pcisecuritystandards.org/pdfs/PCI_DSS_Resource_Guide_(003).pdf",
          "https://developer.apple.com/news/?id=02202019a",
          "http://web.archive.org/web/20250506070026/https://developer.apple.com/news/?id=02202019a",
          "https://dev.twitch.tv/docs/authentication/validate-tokens/",
          "https://discuss.dev.twitch.com/t/legacy-twitch-api-v5-i-e-kraken-shutdown-reminder-february-28-2022/36589",
          "http://web.archive.org/web/20250127085635/https://discuss.dev.twitch.com/t/legacy-twitch-api-v5-i-e-kraken-shutdown-reminder-february-28-2022/36589",
          "https://store.steampowered.com/news/posts/?enddate=1788390000",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/4123547285514022851",
          "https://skinvault.gg/blog/cs2-trade-protection-explained/",
          "https://csmarketcap.com/blog/market-insights/from-boom-to-bust-cs2s-trade-protection-impact",
          "https://skin.land/blog/steam-changes-cs2-trade-ban-logic-timing/",
          "https://help.steampowered.com/faqs/view/3041-A87A-E5F6-B6AC",
          "https://steamcommunity.com/ogg/593110/announcements/detail/533224478739530146",
          "https://steamcommunity.com/games/CSGO/announcements/detail/4447966961421256740",
          "https://steamcommunity.com/sharedfiles/filedetails/?id=2926756889",
          "https://steamcommunity.com/dev/apikey",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3734103130194459461",
          "https://steamcommunity.com/discussions/forum/1/3807266184852932971/",
          "https://help.steampowered.com/faqs/view/225C-C51E-B8F0-55B2",
          "https://store.steampowered.com/news/group/4/view/3314112260640237775",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/issues/325",
          "https://blog.dota2.com/2020/05/trading-cooldown/",
          "https://blog.counter-strike.net/index.php/2018/03/20308/",
          "http://web.archive.org/web/20250226114333/https://blog.counter-strike.net/index.php/2018/03/20308/",
          "https://phishdestroy.io/steam_dossier/tr/steam_evidence_archive.html",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/493839547938902179",
          "https://store.steampowered.com/online_conduct",
          "http://web.archive.org/web/20260921022120/https://store.steampowered.com/online_conduct",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260918014700/https://store.steampowered.com/subscriber_agreement/",
          "https://steamcommunity.com/dev/apiterms",
          "http://web.archive.org/web/20260921022210/https://steamcommunity.com/dev/apiterms",
          "https://help.steampowered.com/en/faqs/view/628C-E332-BD8C-4D36",
          "https://phishdestroy.io/steam_dossier/tr/social_graph.html",
          "https://phishdestroy.io/steam_dossier/tr/security_timeline.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wsgc-skins-gambling-briefing-2018.pdf",
          "https://wsgc.wa.gov/sites/default/files/2023-10/Skins%20Gambling.pdf",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wsgc-briefing-manifest.json",
          "https://x.com/csgobig",
          "https://www.facebook.com/csgobigofficial/",
          "https://500.casino/",
          "https://csgolounge.com/",
          "https://csgocasino.gg/",
          "https://x.com/CSGOatsecom",
          "https://x.com/CSGOSweep/status/937420902538543106",
          "https://x.com/Wild",
          "https://x.com/csgopot",
          "https://x.com/csgodiamondscom",
          "https://www.ftc.gov/legal-library/browse/cases-proceedings/162-3184-csgo-lotto-matter",
          "https://x.com/CSGODouble",
          "https://x.com/csgo_massive",
          "https://www.facebook.com/csgostrongfree/",
          "https://www.facebook.com/CSNCOM/",
          "https://www.gamblingcommission.gov.uk/report/young-people-and-gambling",
          "https://www.aph.gov.au/Parliamentary_Business/Committees/Senate/Environment_and_Communications/Gamingmicro-transactions",
          "https://phishdestroy.io/steam_dossier/tr/elite_skins.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/csfloat-catalogue.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/skinport-floor-over-cap.json",
          "https://pricempire.com/cs2-marketplaces",
          "http://web.archive.org/web/20260921022459/https://pricempire.com/cs2-marketplaces",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/priceempire-marketplaces.json",
          "https://www.steamanalyst.com/marketplace",
          "http://web.archive.org/web/20260719014552/https://www.steamanalyst.com/marketplace",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-atlas.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json",
          "https://phishdestroy.io/steam_dossier/tr/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/tr/steam_enforcement_evidence.html#case-support-recovery",
          "https://top10.owasp.org/2025/A01_2025-Broken_Access_Control/",
          "http://web.archive.org/web/20260920212535/https://top10.owasp.org/2025/A01_2025-Broken_Access_Control/",
          "https://store.steampowered.com/privacy_agreement/",
          "http://web.archive.org/web/20260921021648/https://store.steampowered.com/privacy_agreement/",
          "https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "http://web.archive.org/web/20250818113925/https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "https://www.dexerto.com/counter-strike-2/valve-saves-hacked-cs2-player-threatened-with-ransom-over-300000-of-rare-stickers-3283135/",
          "https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "http://web.archive.org/web/20220702042821/https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "https://www.kaspersky.com/blog/cs-go-two-million-usd-inventory-hack/44697/",
          "https://esportfire.com/article/the-2-million-usd-csgo-hack-22062022",
          "http://web.archive.org/web/20260515110250/https://esportfire.com/article/the-2-million-usd-csgo-hack-22062022",
          "https://esportsbetting.com/valve-deletes-130000-stolen-dragon-lore/",
          "https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "http://web.archive.org/web/20251115173120/https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "https://vkplay.ru/media/news/bloger-rasskazal-kak-podderzhka-steam-vorovala-akkaunty-igrokov/",
          "https://lis-skins.com/ru/blog/krupneisaia-mosenniceskaia-sxema-v-istorii-steam/",
          "https://escorenews.com/ru/csgo/news/44056-sotrudniki-podderjki-steam-zanimalis-krajey-skinov-s-akkauntov-za-god-oni-zarabotali-svyshe-300-tysyach-dollarov",
          "https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "http://web.archive.org/web/20250805141942/https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/outsourcing-archive-records.json",
          "https://community.skin.club/en/news/collector-has-steam-inventory-returned-after-bold-hack",
          "https://esportfire.com/article/300k-scam-full-katowice-2014-holo-collection-hacked",
          "http://web.archive.org/web/20251217072445/https://esportfire.com/article/300k-scam-full-katowice-2014-holo-collection-hacked",
          "https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng",
          "http://web.archive.org/web/20260920024236/https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng",
          "https://ag.ny.gov/press-release/2026/attorney-general-james-sues-game-developer-promoting-illegal-gambling-through",
          "http://web.archive.org/web/20260901015430/https://ag.ny.gov/press-release/2026/attorney-general-james-sues-game-developer-promoting-illegal-gambling-through",
          "https://www.fincen.gov/sites/default/files/2019-05/FinCEN%20CVC%20Guidance%20FINAL.pdf",
          "http://web.archive.org/web/20250711185007/https://www.fincen.gov/sites/default/files/2019-05/FinCEN%20CVC%20Guidance%20FINAL.pdf",
          "https://eur-lex.europa.eu/legal-content/EN/LSU/?uri=CELEX:32018L1673",
          "https://eur-lex.europa.eu/eli/dir/2024/1640/oj/eng",
          "http://web.archive.org/web/20260830153004/https://eur-lex.europa.eu/eli/dir/2024/1640/oj/eng",
          "https://eur-lex.europa.eu/eli/reg/2022/2065/oj/eng",
          "http://web.archive.org/web/20260920080125/https://eur-lex.europa.eu/eli/reg/2022/2065/oj/eng",
          "https://phishdestroy.io/steam_dossier/tr/legal_analysis.html",
          "https://partner.steamgames.com/doc/features/auth#website",
          "http://web.archive.org/web/20260921022335/https://partner.steamgames.com/doc/features/auth",
          "https://www.ftc.gov/legal-library/browse/rules/childrens-online-privacy-protection-rule-coppa",
          "http://web.archive.org/web/20260921070051/https://www.ftc.gov/legal-library/browse/rules/childrens-online-privacy-protection-rule-coppa",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/gdpr-ticket-1.png",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/screenshot-manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/gdpr-ticket-2.png",
          "https://datenschutz.hamburg.de/beschwerde",
          "https://edpb.europa.eu/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/regulatory-review/disclosure-audit.json",
          "https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "http://web.archive.org/web/20260821155801/https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "https://phishdestroy.io/steam_dossier/tr/index#exhibit-gallery-section",
          "https://github.com/ValveSoftware/steam-for-linux/issues/4521",
          "https://phishdestroy.io/steam_dossier/tr/steam_evidence_archive.html?source=GitHub&record=484",
          "https://github.com/ValveSoftware/steam-for-linux/issues/6459",
          "http://web.archive.org/web/20260419051343/https://github.com/ValveSoftware/steam-for-linux/issues/6459",
          "https://phishdestroy.io/steam_dossier/tr/steam_evidence_archive.html?source=GitHub&record=467",
          "https://github.com/ValveSoftware/Source-1-Games/issues/3857",
          "https://phishdestroy.io/steam_dossier/tr/steam_evidence_archive.html?source=GitHub&record=768",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "http://web.archive.org/web/20250320082450/https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://phishdestroy.io/steam_dossier/tr/steam_evidence_archive.html?source=Reddit&record=4533",
          "https://www.reddit.com/r/ohnePixel/comments/1hahqx2/permanently_banned_steam_account_without_a_clear/",
          "https://phishdestroy.io/steam_dossier/tr/steam_evidence_archive.html?source=Reddit&record=4766",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://phishdestroy.io/steam_dossier/tr/steam_evidence_archive.html?source=Reddit&record=4592",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/selected-evidence-records.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive_manifest.json",
          "https://phishdestroy.io/steam_dossier/tr/card_economy.html",
          "https://github.com/JustArchiNET/ArchiSteamFarm/wiki/FAQ",
          "https://phishdestroy.io/steam_dossier/tr/card_economy.html#scale",
          "https://phishdestroy.io/steam_dossier/tr/card_economy.html#licence",
          "https://phishdestroy.io/steam_dossier/tr/enforcement_audit.html",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "http://web.archive.org/web/20260924181709/https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://rdap.verisign.com/com/v1/domain/csgoempire.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoempire.com",
          "https://rdap.verisign.com/com/v1/domain/csgoempirelogin4.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/csgoempire.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustreaper.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustreaper.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/rustreaper.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustly.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustly.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/rustly.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgofast.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgofast.com",
          "https://rdap.verisign.com/com/v1/domain/authtofast.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/csgofast.com.json",
          "https://rdap.verisign.com/com/v1/domain/duelbits.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fduelbits.com",
          "https://rdap.verisign.com/com/v1/domain/switchflips.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/duelbits.com.json",
          "https://rdap.verisign.com/com/v1/domain/farmskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffarmskins.com",
          "https://tld-rdap.verisign.com/cc/v1/domain/kobal.cc",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/farmskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoluck.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoluck.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/csgoluck.com.json",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/domain-registry/insane.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Finsane.gg",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/insane.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs2skin.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs2skin.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/cs2skin.com.json",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/domain-registry/juice.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fjuice.gg",
          "https://rdap.verisign.com/com/v1/domain/letmeinjuice.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/juice.gg.json",
          "https://rdap.verisign.com/com/v1/domain/ggdrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fggdrop.com",
          "https://rdap.verisign.com/com/v1/domain/ggauth.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/ggdrop.com.json",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/domain-registry/howl.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhowl.gg",
          "https://rdap.radix.host/rdap/domain/howl.uno",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/howl.gg.json",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/domain-registry/chicken.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fchicken.gg",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/chicken.gg.json",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/domain-registry/csgocasino.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgocasino.gg",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/csgocasino.gg.json",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/domain-registry/hunt.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhunt.gg",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/hunt.gg.json",
          "https://rdap.verisign.com/com/v1/domain/csbattle.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsbattle.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/csbattle.com.json",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/domain-registry/skinrave.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinrave.gg",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/skinrave.gg.json",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/domain-registry/csdouble.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsdouble.gg",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/csdouble.gg.json",
          "https://rdap.verisign.com/com/v1/domain/rustchance.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustchance.com",
          "https://rdap.verisign.com/com/v1/domain/hgfuihd.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/rustchance.com.json",
          "https://rdap.radix.host/rdap/domain/cobaltlab.tech",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcobaltlab.tech",
          "https://rdap.verisign.com/com/v1/domain/cobaltauth.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/cobaltlab.tech.json",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/domain-registry/raided.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fraided.gg",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/raided.gg.json",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/domain-registry/rustneo.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustneo.gg",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/rustneo.gg.json",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/domain-registry/splits.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsplits.gg",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/splits.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/upgrader.pro",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fupgrader.pro",
          "https://rdap.radix.host/rdap/domain/upgauth.space",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/upgrader.pro.json",
          "https://rdap.centralnic.com/fans/domain/skin.fans",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.fans",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/skin.fans.json",
          "https://rdap.nic.one/domain/hotpizza.one",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhotpizza.one",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/hotpizza.one.json",
          "https://rdap.verisign.com/com/v1/domain/g4skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg4skins.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/g4skins.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2royal.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2royal.com",
          "https://rdap.verisign.com/com/v1/domain/tf2auth.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/tf2royal.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2hunt.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2hunt.com",
          "https://rdap.verisign.com/com/v1/domain/rstspcl.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/tf2hunt.com.json",
          "https://rdap.identitydigital.services/rdap/domain/tf2.bet",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2.bet",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/tf2.bet.json",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/domain-registry/openstars.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fopenstars.gg",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/openstars.gg.json",
          "https://rdap.verisign.com/com/v1/domain/skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/skins.com.json",
          "https://rdap.identitydigital.services/rdap/domain/white.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwhite.market",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/white.market.json",
          "https://rdap.identitydigital.services/rdap/domain/moon.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmoon.market",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/moon.market.json",
          "https://rdap.verisign.com/com/v1/domain/csfloat.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsfloat.com",
          "https://rdap.verisign.com/com/v1/domain/csgofloat.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/csfloat.com.json",
          "https://rdap.identitydigital.services/rdap/domain/skin.land",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.land",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/skin.land.json",
          "https://rdap.verisign.com/com/v1/domain/haloskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhaloskins.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/haloskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/163.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuff.163.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/buff.163.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmarket.csgo.com",
          "https://rdap.verisign.com/net/v1/domain/dota2.net",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/market.csgo.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinport.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinport.com",
          "https://pubapi.registry.google/rdap/domain/skinport.app",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/skinport.com.json",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/domain-registry/skinflow.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinflow.gg",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/skinflow.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/skin.place",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.place",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/skin.place.json",
          "https://rdap.verisign.com/com/v1/domain/skinsmonkey.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinsmonkey.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/skinsmonkey.com.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbaron.de",
          "https://rdap.verisign.com/com/v1/domain/skinbaron.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/skinbaron.de.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frust.tm",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/rust.tm.json",
          "https://rdap.verisign.com/com/v1/domain/pirateswap.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fpirateswap.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/pirateswap.com.json",
          "https://rdap.radix.host/rdap/domain/mannco.store",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmannco.store",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/mannco.store.json",
          "https://rdap.verisign.com/com/v1/domain/skinswap.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinswap.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/skinswap.com.json",
          "https://rdap.verisign.com/com/v1/domain/exeskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fexeskins.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/exeskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/balticskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbalticskins.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/balticskins.com.json",
          "https://rdap.nic.trade/domain/cs.trade",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.trade",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/cs.trade.json",
          "https://rdap.verisign.com/com/v1/domain/rapidskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frapidskins.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/rapidskins.com.json",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/domain-registry/tradeit.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftradeit.gg",
          "https://rdap.verisign.com/com/v1/domain/connect-tradeit.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/tradeit.gg.json",
          "https://rdap.verisign.com/com/v1/domain/49skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F49skins.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/49skins.com.json",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/domain-registry/skinvault.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinvault.gg",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/skinvault.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/aim.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Faim.market",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/aim.market.json",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/domain-registry/skinout.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinout.gg",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/skinout.gg.json",
          "https://rdap.verisign.com/com/v1/domain/ntskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fntskins.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/ntskins.com.json",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/domain-registry/gamerpay.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamerpay.gg",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/gamerpay.gg.json",
          "https://rdap.nic.tf/domain/scrap.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fscrap.tf",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/scrap.tf.json",
          "https://rdap.nic.tf/domain/marketplace.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmarketplace.tf",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/marketplace.tf.json",
          "https://rdap.identitydigital.services/rdap/domain/skins.cash",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.cash",
          "https://rdap.identitydigital.services/rdap/domain/skinscash.live",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/skins.cash.json",
          "https://rdap.verisign.com/net/v1/domain/csgo.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo.net",
          "https://rdap.verisign.com/net/v1/domain/easylot.net",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/csgo.net.json",
          "https://rdap.verisign.com/net/v1/domain/cybershoke.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcybershoke.net",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/cybershoke.net.json",
          "https://rdap.verisign.com/net/v1/domain/fastcup.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffastcup.net",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/fastcup.net.json",
          "https://rdap.verisign.com/com/v1/domain/leetify.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fleetify.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/leetify.com.json",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/domain-registry/scope.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fscope.gg",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/scope.gg.json",
          "https://rdap.verisign.com/com/v1/domain/tradeupspy.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftradeupspy.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/tradeupspy.com.json",
          "https://rdap.identitydigital.services/rdap/domain/cs.deals",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.deals",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/cs.deals.json",
          "https://rdap.verisign.com/com/v1/domain/pricempire.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fpricempire.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/pricempire.com.json",
          "https://rdap.identitydigital.services/rdap/domain/lzt.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flzt.market",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/lzt.market.json",
          "https://rdap.verisign.com/com/v1/domain/z2u.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fz2u.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/z2u.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoroll.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoroll.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/csgoroll.com.json",
          "https://rdap.verisign.com/com/v1/domain/rollbit.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frollbit.com",
          "https://rdap.verisign.com/com/v1/domain/rbsnin.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/rollbit.com.json",
          "https://rdap.identitydigital.services/rdap/domain/500.casino",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F500.casino",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/500.casino.json",
          "https://rdap.verisign.com/com/v1/domain/csgobig.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgobig.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/csgobig.com.json",
          "https://rdap.verisign.com/com/v1/domain/casedrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcasedrop.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/casedrop.com.json",
          "https://rdap.verisign.com/com/v1/domain/banditcamp.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbanditcamp.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/banditcamp.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinbox.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbox.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/skinbox.com.json",
          "https://rdap.verisign.com/com/v1/domain/tastydrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftastydrop.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/tastydrop.com.json",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/domain-registry/csgopolygon.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgopolygon.gg",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/csgopolygon.gg.json",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/domain-registry/magicdrop.ru.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmagicdrop.ru",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/magicdrop.ru.json",
          "https://rdap.verisign.com/com/v1/domain/csdice.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsdice.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/csdice.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinodds.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinodds.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/skinodds.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgowin.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgowin.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/csgowin.com.json",
          "https://rdap.verisign.com/net/v1/domain/csgorun.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgorun.net",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/csgorun.net.json",
          "https://rdap.verisign.com/com/v1/domain/openskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fopenskins.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/openskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustbet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustbet.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/rustbet.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgomagic.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgomagic.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/csgomagic.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgobounty.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgobounty.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/csgobounty.com.json",
          "https://rdap.verisign.com/com/v1/domain/ezskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fezskins.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/ezskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustcases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustcases.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/rustcases.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoreaper.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoreaper.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/csgoreaper.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgocases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgocases.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/csgocases.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo-skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo-skins.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/csgo-skins.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgonet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgonet.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/csgonet.com.json",
          "https://rdap.verisign.com/com/v1/domain/wtfskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwtfskins.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/wtfskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/flamecases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fflamecases.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/flamecases.com.json",
          "https://rdap.verisign.com/com/v1/domain/gamedom.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamedom.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/gamedom.com.json",
          "https://rdap.nic.club/domain/skin.club",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.club",
          "https://rdap.verisign.com/net/v1/domain/sc-auth.net",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/skin.club.json",
          "https://rdap.verisign.com/com/v1/domain/daddyskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdaddyskins.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/daddyskins.com.json",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/domain-registry/rustix.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustix.gg",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/rustix.gg.json",
          "https://rdap.nic.club/domain/skins.club",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.club",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/skins.club.json",
          "https://rdap.publicinterestregistry.org/rdap/domain/csgohouse.org",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgohouse.org",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/csgohouse.org.json",
          "https://rdap.verisign.com/net/v1/domain/skinrave.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinrave.net",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/skinrave.net.json",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/domain-registry/bloodycase.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbloodycase.gg",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/bloodycase.gg.json",
          "https://rdap.verisign.com/com/v1/domain/csgoclicker.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoclicker.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/csgoclicker.com.json",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/domain-registry/rustbet.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustbet.gg",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/rustbet.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs-drop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs-drop.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/cs-drop.com.json",
          "https://rdap.verisign.com/net/v1/domain/hellstore.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhellstore.net",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/hellstore.net.json",
          "https://rdap.verisign.com/com/v1/domain/rustloot.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustloot.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/rustloot.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo-case.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo-case.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/csgo-case.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgogem.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgogem.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/csgogem.com.json",
          "https://rdap.verisign.com/com/v1/domain/rainbet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frainbet.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/rainbet.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustclash.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustclash.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/rustclash.com.json",
          "https://rdap.identitydigital.services/rdap/domain/12cs.fail",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F12cs.fail",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/12cs.fail.json",
          "https://rdap.verisign.com/com/v1/domain/tf2easy.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwww.tf2easy.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/tf2easy.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2blaze.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2blaze.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/tf2blaze.com.json",
          "https://rdap.verisign.com/com/v1/domain/shuffle.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fshuffle.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/shuffle.com.json",
          "https://rdap.identitydigital.services/rdap/domain/buff.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuff.market",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/buff.market.json",
          "https://rdap.identitydigital.services/rdap/domain/avan.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Favan.market",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/avan.market.json",
          "https://rdap.identitydigital.services/rdap/domain/cs.money",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.money",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/cs.money.json",
          "https://rdap.verisign.com/com/v1/domain/uuskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fuuskins.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/uuskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/youpin898.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fyoupin898.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/youpin898.com.json",
          "https://rdap.verisign.com/com/v1/domain/c5game.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fc5game.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/c5game.com.json",
          "https://rdap.verisign.com/com/v1/domain/waxpeer.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwaxpeer.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/waxpeer.com.json",
          "https://rdap.verisign.com/com/v1/domain/dmarket.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdmarket.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/dmarket.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamcommunity.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamcommunity.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/steamcommunity.com.json",
          "https://rdap.verisign.com/com/v1/domain/lootfarm.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flootfarm.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/lootfarm.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustskins.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/rustskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/krakatoa.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fkrakatoa.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/krakatoa.com.json",
          "https://rdap.verisign.com/com/v1/domain/shadowpay.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fshadowpay.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/shadowpay.com.json",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/domain-registry/igxe.cn.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Figxe.cn",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/igxe.cn.json",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/domain-registry/swap.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fswap.gg",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/swap.gg.json",
          "https://rdap.verisign.com/com/v1/domain/bitskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbitskins.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/bitskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2mart.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2mart.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/tf2mart.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinbid.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbid.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/skinbid.com.json",
          "https://rdap.verisign.com/com/v1/domain/lootbear.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flootbear.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/lootbear.com.json",
          "https://rdap.nic.tf/domain/backpack.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbackpack.tf",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/backpack.tf.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fstntrading.eu",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/stntrading.eu.json",
          "https://rdap.verisign.com/com/v1/domain/skinwallet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinwallet.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/skinwallet.com.json",
          "https://rdap.verisign.com/com/v1/domain/dota2market.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdota2market.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/dota2market.com.json",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/domain-registry/xplay.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fxplay.gg",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/xplay.gg.json",
          "https://rdap.verisign.com/com/v1/domain/esportal.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fesportal.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/esportal.com.json",
          "https://rdap.registro.br/domain/gamersclub.com.br",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamersclub.com.br",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/gamersclub.com.br.json",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/domain-registry/epidemic.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fepidemic.gg",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/epidemic.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs2stash.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs2stash.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/cs2stash.com.json",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/domain-registry/csgoskins.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoskins.gg",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/csgoskins.gg.json",
          "https://rdap.verisign.com/com/v1/domain/steamanalyst.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamanalyst.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/steamanalyst.com.json",
          "https://rdap.verisign.com/net/v1/domain/steamcardexchange.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamcardexchange.net",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/steamcardexchange.net.json",
          "https://rdap.verisign.com/com/v1/domain/dotabuff.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdotabuff.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/dotabuff.com.json",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/domain-registry/tracker.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftracker.gg",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/tracker.gg.json",
          "https://rdap.verisign.com/com/v1/domain/funpay.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffunpay.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/funpay.com.json",
          "https://rdap.verisign.com/com/v1/domain/playerauctions.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fplayerauctions.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/playerauctions.com.json",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/domain-registry/eldorado.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Feldorado.gg",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/eldorado.gg.json",
          "https://rdap.verisign.com/com/v1/domain/g2a.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg2a.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/g2a.com.json",
          "https://rdap.verisign.com/net/v1/domain/kinguin.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fkinguin.net",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/kinguin.net.json",
          "https://rdap.verisign.com/com/v1/domain/g2g.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg2g.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/g2g.com.json",
          "https://rdap.verisign.com/com/v1/domain/playerup.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fplayerup.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/playerup.com.json",
          "https://rdap.verisign.com/net/v1/domain/smurfhub.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfhub.net",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/smurfhub.net.json",
          "https://rdap.verisign.com/com/v1/domain/smurfaccounts.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfaccounts.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/smurfaccounts.com.json",
          "https://rdap.verisign.com/com/v1/domain/buycsgorank.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuycsgorank.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/buycsgorank.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgosmurfkings.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgosmurfkings.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/csgosmurfkings.com.json",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/domain-registry/smurfstore.co.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfstore.co",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/smurfstore.co.json",
          "https://rdap.verisign.com/com/v1/domain/steamlvlup.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlvlup.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/steamlvlup.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamlevels.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlevels.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/steamlevels.com.json",
          "https://rdap.verisign.com/com/v1/domain/levelsteam.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flevelsteam.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/levelsteam.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamlevelu.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlevelu.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/steamlevelu.com.json",
          "https://rdap.verisign.com/com/v1/domain/eloking.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Feloking.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/eloking.com.json",
          "https://rdap.publicinterestregistry.org/rdap/domain/boosteria.org",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fboosteria.org",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/boosteria.org.json",
          "https://rdap.verisign.com/com/v1/domain/overgear.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fovergear.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/overgear.com.json",
          "https://rdap.verisign.com/com/v1/domain/blazingboost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fblazingboost.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/blazingboost.com.json",
          "https://rdap.verisign.com/com/v1/domain/dota2boost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdota2boost.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/dota2boost.com.json",
          "https://rdap.verisign.com/com/v1/domain/buyboost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuyboost.com",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit/buyboost.com.json",
          "https://phishdestroy.io/steam_dossier/tr/steam_tos_assets/auth-route-audit.json",
          "https://help.steampowered.com/en/faqs/view/365F-4BEE-2AE2-7BDD",
          "https://store.steampowered.com/privacy_agreement/#8",
          "https://www.edpb.europa.eu/system/files/2023-04/edpb_guidelines_202201_data_subject_rights_access_v2_en.pdf",
          "https://web.archive.org/web/20260810154631/https://store.steampowered.com/stats/support",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/design-review/part2/measurements.json",
          "https://phishdestroy.io/steam_dossier/tr/VALVE_EVIDENCE_PACK/databases/TOTAL_VALVE_SCANDALS_MASTER_DB.csv",
          "https://phishdestroy.io/steam_dossier/tr/license_disclaimer.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/tr/index.content.json",
      "export_json_sha256": "0ad102f19648679b0408a3b325c5057df68d38608092fdd8b15eee5c776f2db3"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "tr/investigation_part2.html",
      "language": "tr",
      "title": "Hesap erişimi ve hesap verebilirlik — Steam Dosyası",
      "source_url": "https://phishdestroy.io/steam_dossier/tr/investigation_part2",
      "source_html_sha256": "c88afdbe665b16cb7aadfe55525f3dfea8f9b60aa73d3bb868ca28202b722dd6",
      "exported_at": "2026-09-29T00:20:46.902Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "investigation_part2.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/tr/investigation_part2.pdf?v=print-20260929-v5",
        "sha256": "857a96d1a9f4ebbc9b34ed5c043a7316f76b7ca926c24a704afaba15e7bc05aa",
        "bytes": 127183,
        "pages": 9
      },
      "integrity": {
        "signed_object": "investigation_part2.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "investigation_part2.content.json.asc",
        "digest_file": "investigation_part2.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify investigation_part2.content.json.asc investigation_part2.content.json",
          "sha256sum -c investigation_part2.content.json.sha256"
        ]
      },
      "content": {
        "text": "STEAM DOSYASI / II\n\nHesabınız.Onların erişimi.Kim cevap veriyor?\n\nKamu sektöründe otomasyon. Dış kaynaklı destek. Bedelini ödeyenler ise halk.\n\nAltyapıyı, bildirilen kayıpları ve iddiaların dayandığı belgeleri takip edin.\n\nAltyapıyı haritalandırın ↘\nEK 01 / CANLI GÖLGE PİYASA İZLEME550,000+\n\nSteam adet hesap, FSB Market (anonimleştirilmiş ad; gerçek ad burada belirtilmiyor)’te aktif olarak satışta\ntam da şu anda\n\n550,000+ CANLI ENVANTER · 231,829 GEÇMİŞ KAZINMIŞ KORPUS (198,320 STEALER GÜNLÜKLERİ)\n\nEle geçirilmiş Steam hesapları için başlıca yeraltı takas merkezi, FSB Market (diğer ilişkili adlar açıklanmıyor), Valve'nin resmi Steam OpenID'sini kullanarak hem alıcıların hem de satıcıların kimliğini doğrular (openid.realm = https://FSB Market). Herhangi bir anda, yarım milyondan fazla çalınmış ve güvenliği ihlal edilmiş hesap (RedLine/Lumma kaynaklı hırsızlık günlükleri, kimlik avı yakalamaları, kimlik bilgisi doldurma saldırıları), birkaç kuruşa aktif olarak satışa sunulmaktadır ($0.50–$2.00). Ne FSB Market ya da ilişkili forum Valve'in Bağlantı Filtresi tarafından engellenmiştir. Bu, Valve'nin mağdura yardım etmeden yasakladığı 63.06% adet ücretli bot hesabına kaynak sağlayan endüstriyel rezervuardır.\n\nCanlı Intel: Gizli Piyasa İzleme (550.000+ Canlı) ↗ · Yakalama kaydını aç ↗ · Bağlantı Filtresi izlemesini aç ↗550.000'den fazla CANLI\n\n01 / YAZARLARIN BULUNDUĞU BİR EKOSİSTEM\n\nOtomasyon,yazılı kayıtlar.\n\nAdı belirtilen projeler. Yayınlanmış yetenekler. Bir aracı ilgili belgelerine kadar takip edin, ardından toplanan geliştirici ilişkilerini inceleyin.\n\n252TOPLANAN ARŞİVLER\n3,320GITHUB PROFİLLERİ\n4,214PROFİL–VERİ DEPOSU ÇİFTLERİ\nValve altyapıToplum kütüphaneleriYeniden kullanılabilir uygulamalar\nÇizgiler, belgelenmiş entegrasyonları veya bağımlılıkları gösterir. Kanıtlarını incelemek için bir düğümü seçin.\n\nÇoklu hesap otomasyonu / JustArchiNET\n\nArchiSteamFarm\n\nProje, Steam adresindeki hesaplar arasında eşzamanlı kart toplama işlemini açıkça tanıtmaktadır. Proje dosyasında SteamKit2 bağımlılığı belirtilmiştir.\n\nProjenin kendi belgelerini okuyun ↗\n\nSteamKit → ArchiSteamFarm\nbildirilen bağımlılık ↗\n\nTOPLANMIŞ İLİŞKİLER\n\n40 katkıcı etiketleri · 40 forker etiketleri\n\nAşağıda bir katkıcı örneği yer almaktadır. Bu etiketler, istihdam veya onay durumunu değil, depo ilişkisini tanımlamaktadır.\n\n@JustArchi@renovate[bot]@JustArchi-ArchiBot@dependabot-preview[bot]@renovate-bot@actions-kullanıcı@dependabot-destek@Abrynos\nGeliştirici grafiğinin ortaya koyduğu şey\n\nGrafik, belirli projeler ile GitHub profilleri arasında yayınlanmış katkı ve fork ilişkilerini göstermektedir. Bunlar, depo fork’ları, katkı listeleri ve profil ilişkilendirmeleri gibi herkese açık kayıtlardır. Asıl mesele, yayınlanmış yetkinlikler ve geliştirici ilişkilerinin oluşturduğu bu belge izinin Valve’ın neyi açıklığa kavuşturması gerektiğidir; bu araştırmanın neyi ortaya çıkardığı değil. Kaynak hash’leri şu dosyada kaydedilmiştir: haritanın kaynağı.\n\nTüm ağı keşfedin ↗Depo kaynak verileri ↓\n\n02 / FARKLI YETKİLER. FARKLI GÜÇLER.\n\nHangi tuşNeden bahsediyoruz?\n\nBir oyunu oynamak için oyuncunun kişisel bir Web API anahtarı oluşturması gerekmez. İşte bu soruşturmanın merkezinde yer alan fark budur.\n\n01 / KULLANICI HESABI\nKişisel Web API anahtarı\nsteamcommunity.com/dev/apikey\n\nİzin verilen API çağrıları için bir kullanıcı hesabından verilir. Anahtar oluşturma, görünürlük, iptal ve kötüye kullanım tespiti, hesap güvenliğiyle ilgili konulardır.\n\n02 / OYUN ARKA UÇU\nYayıncı Web API anahtarı\n\nSteamworks iş ortakları, oyunla ilgili hizmetler de dahil olmak üzere desteklenen arka uç işlemleri için yayıncı kimlik bilgilerini kullanır. Oyuncunun kişisel anahtarı ise farklı bir kimlik bilgisidir.\n\n03 / KİMLİK VE OTURUM\nOpenID / oturum belirteçleri\n\nOpenID, bir web sitesine kimlik doğrulaması sağlar. Bir Steam oturum veya yenileme jetonunun ise farklı bir amacı vardır. Bu mekanizmalar, birbirinin yerine kullanılabilen tek bir “API anahtarı” olarak sunulmamalıdır.\n\nValve, hem kullanıcı hem de yayıncı Web API anahtarlarını belgeler. Dolayısıyla Web API’nin tamamı Steamworks’ten ayrı değildir. API anahtarı belgeleri ↗ arşivlendi 2026-09-15 ↗ · Oyun oturumu kimlik doğrulaması ↗ arşivlendi 2026-08-29 ↗\n\nARACIN YAZARI TARAFINDAN BELGELENMİŞTİR / MART 2024\n\nOtomasyon, bir API anahtarından fazlasını kullanabilir.\n\nTrade Offer Manager’ın wiki sayfası, ayrı bir API anahtarı bulunmadığında Web API’nin bazı bölümleri için oturum erişim belirtecinin nasıl kullanılacağını açıklamaktadır. Ayrıca, 2023’ün sonlarından itibaren anahtar oluşturma işlemi için mobil onay sürecini de belirtmektedir. Sorumlu kişi, belirtecin bu şekilde kullanılmasının Valve tarafından desteklenmediğini belirtmektedir; bu, güncel bir belgeleme iddiasıdır, canlı bir atlatma testi değildir.\n\nBakım sorumlusunun açıklamasını inceleyin ↗ arşivlendi 2026-09-24 ↗\n\nİNSAN YÖNÜ / ÖRNEK BİR PHISHING SÜRECİ\n\nHâlâ oynuyor.Zaten açığa çıkmış.\n\nBir arkadaşın mesajı. Oy verme isteği. Bir “teşekkür” sayfası. Oyuncu için görev tamamlanmıştır. Güvenliği ihlal edilmiş bir oturum ise o anın ötesine uzayabilir.\n\nOYUNCU EKRANINDA\n\nF\nBİR ARKADAŞIN ANLATIMI\n\n“Takımımıza oy verir misiniz?”\n\nİstek, tanıdık bir hesaptan Steam sohbeti aracılığıyla gelir. Bu senaryoda, bağlantı verilen sayfa kullanıcının tarayıcısında açılır.\n\nGÖRÜLMEYEN\n\nGüven, web sitesinden önce başlar.\n\nEle geçirilmiş bir arkadaşın hesabı, bir kimlik avı bağlantısına güvenilirlik katabilir. Etrafındaki Steam arayüzü, hedef web sitesinin güvenilirliğini doğrulamaz.\n\nTANINAN GÖNDEREN / DIŞ HEDEF\nHerhangi bir ürünün satılmasından önce öncelikli konu hesap güvenliğidir.\n\nOyuncu, bir otomasyon kimlik bilgisi oluşturmak ya da kontrolü devretmek niyetinde değildi. Oyuna geri dönmek, hesabın güvenli olduğunun kanıtı değildir. Valve, oturum günlüklerini, API anahtarı oluşturma kaydını ve cihaz ilişkilendirme verilerini elinde bulundurur. Mağdur ise bunlara sahip değildir. Bu asimetri, hesap verebilirlik sorununu oluşturmaktadır.\n\nOturum erişimi ve kimlik bilgisi türleri\n\nBir API anahtarı ve oturum açılmış bir oturum, farklı yeteneklere sahip ayrı kimlik bilgileridir. Bir anahtarın iptal edilmesi, aktif bir oturumu sonlandırmaz. Valve’un kendi belgelerinde her ikisi de açıklanmaktadır; Valve ise, ihtilaflı bir eylemin gerçekleştiği anda hangi kimlik bilgisinin aktif olduğunu gösterecek günlükleri tutmaktadır. Talep edilen şey, bu kaydın açıklanmasıdır — soruşturma kapsamında uydurulmuş bir çıkarım değil. Token işlemeyle ilgili bakımcı belgeleri ↗ arşivlendi 2026-09-24 ↗ · Valve anahtar belgeleri ↗ arşivlendi 2026-09-15 ↗\n\n03 / RESMİ PİYASANIN BİR TAVANI VAR\n\nBu eşya nadir olabilir.Sınır geçerliliğini koruyor.\n\nListeleme üst sınırının üzerindeki bir fiyat, tek bir Topluluk Pazarı listelemesi yoluyla o tam fiyattan gerçekleştirilemez.\n\nÖRNEK SATIŞ FİYATI$5,000Ürünün satış fiyatını değiştirin\n$100$20,000\n\nYayınlanan sınırın bir örneği olup, bir değerleme veya alım-satım tavsiyesi değildir.\n\nLİSTELEME SINIRI≈ $1,800\nCÜZDAN KAPAKLI≈ $2,000\n\nYayınlanan liste sınırının üzerinde.\n\nCüzdan bakiyeleri bir banka hesabına aktarılamaz. Bu kısıtlamalar, üçüncü taraf skin pazarlarının karşıladığı bir talep yaratmaktadır: Bu talep, listeleme ve cüzdan limitlerinden kaynaklanırken, Valve’un kendi kuralları ticari operatörlerin bu talebi karşılamasını engellemektedir.\n\nSteam’nin piyasa sınırları ↗ arşivlendi 2026-09-21 ↗\n\n04 / DESTEK SINIRININ İÇİNDE\n\nVeriler bize emanet edilmiştir.Erişimden sorumludur.\n\nValve’nin gizlilik politikası, destek hizmetleri için gerekli olduğu ölçüde kişisel verilerin üçüncü taraf destek sağlayıcılarıyla paylaşılmasını açıkça öngörmektedir.\n\nOYUNCUHesap ve kanıtlar\n→\nVALFİyileşme süreci\n→\nDESTEK SAĞLAYICIYetki devri yoluyla erişim\n\nGizlilik Politikası §5.2 ↗ · Valve’un kendi politikası, üçüncü tarafların destek amaçlı erişimine izin vermektedir. Açık kalan sorular şunlardır: hangi izinler verilmiştir, hangi denetim kayıtları mevcuttur ve erişimin kötüye kullanıldığı iddia edildiğinde ne olmuştur?\n\n2015\nÖlçek halka açıktı\n\nValve, hesap hırsızlıklarının yaygın olduğunu kabul etti ve alınacak koruyucu önlemleri açıkladı.\n\nValve yayın ↗arşivlendi 2026-08-09 ↗\n2015\nValve o masayı dış kaynaklara devretti — ve bunu açıkça belirtti\n\nValve, küçük bir şirket içi Steam Destek Liderlik ekibini bünyesinde bulunduruyor ve bunu belirtti \"birkaç farklı şirketle anlaştı\" destek hizmetlerini yürütmek üzere (Erik Johnson, Valve, Kotaku’ya); gizlilik politikasının 5.2. maddesi, söz konusu üçüncü tarafların kullanıcı verilerine erişimine izin vermektedir. Hangi yüklenicinin hesap kurtarma erişim yetkisi olduğu, Valve tarafından hiçbir zaman açıklanmamıştır — Topluluk tartışmalarında Concentrix gibi tedarikçilerin adları geçse de, bunların hiçbiri Valve-onaylanmamıştır. Dış kaynaklı hizmet masası, aşağıda belirtilen her iki durumdan da yıllar önce faaliyete geçmişti.\n\nKotaku: Valve destek konusunda ↗arşivlendi 2025-07-11 ↗\n2023\nİlk kabul\n\nValve'un CS:GO takımı, kendi yardım talebi süreci yoluyla ele geçirilen bir hesapla ilgili sorumluluğu yazılı olarak üstlenir ve takas işlemlerini iptal eder.\n\nDış kaynak kullanımı dosyasını aç ↓\n2025\nİkinci kabul\n\n33 ay sonra, Steam Destek ekibi, bir teknisyenin “süreçlerimize uymaması nedeniyle hesabınızın başka birine geri verilmiş olduğunu” yazıyor. Aynı kanal. Aynı sonuç.\n\nDexerto, 14 Kasım 2025 ↗\n\nDOSYA / HFB VE DIŞ KAYNAK KULLANIMI İDDİALARI\n\nİçeri giriş yolu, Steam Destek'in kendisiydi.Valve bunu yazılı olarak belirtmiştir.\n\nDexerto tarafından aktarılan destek yanıtında, Valve’un CS:GO takımı, ele geçirilmiş bir hesapla ilgili sorumluluğu üstleniyor yardım talebi süreci boyunca — kendi kanalı, bir kimlik avı sayfası değil ve kullanıcı da değil. Varlıklar geri kazanıldı ve işlemler iptal edildi; bu, Valve’nin diğer mağdurlara “yok” olduğunu söylediği çözümdür. HFB’nin envanterinin değeri şu şekilde bildirildi: $2,000,000+ o gün ve $3,000,000+ takip sürecinde; Qkss de aynı şekilde $1,000,000+ kaybetti ve hiçbir şey kazanamadı.\n\nDESTEK CEVABI / DEXERTO TARAFINDAN YAYINLANMIŞTIR · 21 ŞUBAT 2023\n“bir destek talebi yoluyla güvenliği ihlal edildi; bunun sorumluluğunu CS:GO ekibi üstleniyor”\nHaberi ve alıntılanan mesajı okuyun ↗ arşivlendi 2025-08-18 ↗\n01 / HANGİ VANADAN GİRİŞ YAPILDI\nKendi destek kanalı, içeri girmenin yolu oldu\n\nYanıt, güvenliği ihlal edilen hesap ve bu hesapta gerçekleştirilen işlemlerin iptal edilmesini kapsamaktadır. Valve bu işlemleri iptal etmiştir — dolayısıyla işlemler iptal edilebilirdi. Orijinal, kimliği doğrulanmış bilet bu koleksiyonda yer almamaktadır.\n\n02 / İŞTEN ÇIKARMALARIN ÇÖZEMEDİĞİ SORUNLAR\nAynı kapı Kasım 2025’te yeniden açıldı\n\nYüklenici, Steam destek personelinin tamamını işten çıkardı — bu haber, Valve personel bildirisi değil, Mzkshow tarafından Dexerto aracılığıyla aktarıldı. Otuz üç ay sonra Steam Support, başka bir tahsilatçıya yazdığı mektupta, “yardım talebini işleme alan bir destek teknisyeninin prosedürlerimizi uygulamaması sonucunda hesabınızın başka birine geri verilmiş olduğunu” belirtti. Valve’in aynı kanal hakkında kendi ifadesi.\n\nİkinci yatış, 14 Kasım 2025 ↗\n03 / OPEN NEDİR?\nValve, yüklenicinin adını hiçbir zaman açıklamadı\n\nBu kaynaklarda ne yüklenici ne de konum belirtilmiştir. Bu, habercilikte bir eksiklik değildir — bu, Valve’un kullanıcı hesaplarına erişim yetkisine sahip olan kişiler hakkında yapmadığı bir açıklamadır.\n\nOlayla ilgili çağdaş bir anlatım ↗\n\nValve’un yanıtlamadığı üç soru: Hesap kurtarma işlemini kim geçersiz kılabilir, erişim denetiminde neler tespit edildi ve sonrasında neler değişti?\n\nKorunan destek arşivinde yer alan sonraki iddialar\n\n2024 yılına ait iki Reddit gönderisi, Mzkshow ile ilgili başka soruşturmaları aktarıyor — Temmuz 2024’teki VAC yasak kaldırma vakası ve Aralık 2024’teki $13,000 envanter vakası. Bunlar ayrı ayrı bildirilen olaylardır. Her birinde sorumlulukla ilgili sorular aynıdır: kimlerin geçersiz kılma erişimi vardı, denetimde neler ortaya çıktı ve neler değişti?\n\n14 Temmuz 2024 · bildirilen iyileşme / VAC-yasak vakası ↗2 Aralık 2024 · bildirilen $13,000 stok vakası ↗arşivlendi 2025-08-05 ↗Korunmuş iki gönderi, kaynak satırları ve hash değerleri ↓\n\n05 / KAYBI TAKİP ET\n\nHer tutarbir kılıfa ihtiyacı var.\n\nOn vaka, Haziran 2022 – Mart 2026. Her rakam, ilgili kaynağın yayınladığı rakamdır — $6,300,000, $2,000,000+, $1,000,000+, ≈$320,000, ≈$300,000, ve 288 avroya kadar düştü. Valve, her biri için işlem günlüğünü, oturum kaydını ve destek denetim izini tutar; ancak bunların hiçbirini sunmamıştır.\n\nDESTEK KANALI21 HAZİRAN 2022\n$2,000,000+\nHFB — the largest inventory in the game\n\nBİLDİRİLEN STOK DEĞERLEMESİ · ŞUBAT AYINDA $3M+’A YÜKSELDİ 2023 TAKİP HABERİ\n\nYedi adet Souvenir Dragon Lores ve #1 Blue Gem Karambit; sadece bu bıçağın fiyatı yaklaşık $1.26m. Otantikasyon aracı hâlâ aktifken üç yıl boyunca kullanılmamış; e-posta ve şifre, destek ekibinin kurtarma prosedürü aracılığıyla değiştirildi. Valve işlemleri geri aldı — ve sorumluluğunu yazılı olarak kabul etti. İşlemlerin geri alınmasından önce, nakit ve kripto para ile ödeme yapan market.csgo.com aracılığıyla $200,000'dan fazla bir tutarın çekildiği bildirildi. Geri alma işlemi, bir skin'i iade eder; birinin zaten hesabına yatırdığı parayı değil. Geri alma işlemi sırasında bir başka sorun da ortaya çıktı: Bir alıcı, Souvenir Dragon Lore öğesini oyun içi bir Depolama Biriminde saklamıştı; komut dosyası kendi konteynerinin içini görememişti ve Valve, bir hırsızlığı geri alırken $130,000 değerindeki bir öğeyi iki kez oluşturdu — bu durum, öğe kimlikleri ve topluluk raporlamaları sayesinde tespit edildi ve Temmuz ayında silindi 2022,. Alıcıya geri ödeme, Valve yerine BUFF tarafından yapıldı.\n\nDexerto, hırsızlığın gerçekleştiği gün ↗\nCÜZDAN VE ALIŞVERİŞLER07 TEMMUZ 2022\n>$500\n44 disputed Market purchases\n\nBEYAN EDİLEN CÜZDAN HARCAMALARI · ABD Doları\n\nBir kullanıcı, düşük değerli Dota 2 öğelerinin izinsiz olarak satın alındığını ve müşteri desteğinden aldığı yanıtın tatmin edici olmadığını bildirmiştir.\n\nŞikayeti ve bağlantılı ekran görüntülerini okuyun ↗\nPLATFORM İHLALİ14 AĞUSTOS 2022\n$6,300,000\nCS.Money — 19,000+ botlardan elde edilen görünümler\n\nFİYAT DEĞERLENDİRMESİ · İLK TAHMİN $1.6M\n\nSaldırganlar, ticaret platformunun ticaret botlarına ait mobil kimlik doğrulama dosyalarını ele geçirip içlerini boşalttılar; izleri karıştırmak için ele geçirdikleri varlıkların bir kısmını tanınmış tüccarlara aktardılar. Topluluk araştırmacıları, birkaç saat içind55'daki saldırgan hesaplarının haritasını çıkardı. Valve hiçbir işlemi geri almadı — Steam adresinin dışında üçüncü taraf bir site bulunuyor, dedi aynı Steam; bu sitenin envanteri, ticaret API ve hesap sistemi, hırsızlığı baştan sona gerçekleştirdi.\n\nÇağdaş tanıklığı okuyun ↗\nDESTEK KANALIHABER 21 ŞUBAT 2023\n$1,000,000+\nQkss — aynı kapı, aynı oyuncu, zıt cevap\n\nBEYAN EDİLEN STOK DEĞERLEMESİ\n\nHFB’nin ele alınış şekliyle, aynı aktör tarafından, aynı destek talebi yoluyla ele alındı. HFB sekiz ay önce tamamen çözülmüştü. Qkss ise çözülmemişti. Yayınlanan kayıtlarda, izleyici sayısının büyüklüğü dışında bu iki vakayı birbirinden ayıran hiçbir unsur bulunmamaktadır.\n\nDexerto’nun Mzkshow soruşturması hakkındaki haberi ↗\nDESTEK KANALI2023'DE YAYINLANAN HABER\n≈ $320,000\nİçeriden bilgi ticareti — bir yıllık süre boyunca\n\nYAKLAŞIK BİR YIL BOYUNCA ELDE EDİLEN GELİR · STOK DEĞERLEMESİ DEĞİLDİR\n\nDestek ekibi, 15 kadar eski hesap geçmişine erişebildi: ilk CD anahtarı, ilk e-posta, ilk kart — tam da hesap kurtarma sürecinde istenen kanıtlar. Veritabanını elinde tutan kişi, hesap sahibi kim olursa olsun bu tartışmayı her zaman kazanır. iBUYPOWER ve Titan Katowice 2014 holografik özellikli, çalınan bir M4A4 Howl, $35,000'a satıldı ve bunu bilmesinin imkânı olmayan NAVI’den b1t’nin eline geçti. Yüklenicinin cevabı, Steam desteğinde çalışan tüm çalışanları işten çıkarmak oldu.\n\nAynı soruşturmayla ilgili Escorenews haberi ↗\nCÜZDAN VE ALIŞVERİŞLER09 2023 Aralık\n€288\nİki aşamalı güvenlik önlemine rağmen cüzdan kaybı\n\nTRUSTPILOT · KAYNAK DİZİNİ 16\n\nYorumcu, hesabının ele geçirildiğini ve Market harcamaları konusunda yardım talebinin reddedildiğini bildiriyor. Dışa aktarımda ayrı bir yorum URL’si bulunmuyor.\n\nKaynağın menşeini kontrol edin ↗\nHESAP GERİ KAZANIMI02 2024 Aralık\n$13,000\n“Matvey” — işten çıkarmalardan iki yıl sonra\n\nYAZARIN STOK TAHMİNİ\n\nHesap sahibinin kendisinin bile eşleştiremediği hesap bilgilerini sağlayan kişiye geri alma izni verildi. Yüklenici, Steam adresindeki destek masasını tamamen kaldırdıktan sonra da aynı yol izlendi ve aynı sonuca varıldı.\n\nKaydedilmiş iddiayı okuyun ↗\nHESAP GERİ KAZANIMI09 MAYIS 2025\n≈ $10,000\nBaşka birinin biletiyle geri alma\n\nİDDİA EDİLEN KAYIP ÖĞE · ABD Doları\n\nQuebec’ten bir kullanıcı, destek ekibinin başka bir kişinin talebi üzerine şifreyi sıfırladığını ve hesap korumasını kaldırdığını iddia ediyor.\n\nBirinci şahıs ağzından yazılmış şikayeti okuyun ↗\nDESTEK KANALI13 KASIM 2025\n≈ $300,000\nHawkeye337 — ve Valve’in ikinci yazılı itirafı\n\nKATOWICE 2014 HOLO KOLEKSİYONUNUN TAMAMI\n\nSaldırgan, 1 adresinden bitcoin talep etti ve koleksiyonu yok etmek için Negevs’e aktarmaya başladı. Steam Destek ekibinin yanıtı: “Yardım talebini ele alan bir destek teknisyeni, prosedürlerimize uymadı; bu da hesabınızın başka birine geri verilmesine yol açtı.” İlk itirafın üzerinden otuz üç ay geçtikten sonra, yine aynı durum. Konu X adresinde trend olduktan birkaç saat sonra hesap geri yüklendi. Qkss’in o kadar geniş bir kitlesi yoktu.\n\nDexerto, 14 Nov 2025 ↗\nCÜZDAN VE ALIŞVERİŞLER29 MAR 2026\n$50\nYetkisiz kontör yükleme ve hediye edilen oyunlar\n\nTRUSTPILOT · KAYNAK DİZİNİ 290\n\nYorumcu, izinsiz harcamalar ve sonuçsuz kalan geri ödeme taleplerinden söz ediyor. Dışa aktarımda ilgili yorumun URL’si eksik.\n\nKaynağın menşeini kontrol edin ↗\n\nKaynaklar ve tutarlar, her bir kaynak tarafından bildirildiği şekliyle kalır. Valve, bu vakaların her biri için işlem günlüklerini, oturum kayıtlarını ve destek denetim izlerini elinde bulundurmaktadır. Bunları sunun. Saklanmış bir Reddit gönderisi bu soruyu çözmez — Valve’in kendi kayıtları çözer.\n\nKOLEKSİYON / KONTROL EDİLDİKTEN SONRA\n\n231,829 adet hesap satışta.Valve, her birine ait günlükleri barındırır.\n354 → 201\nTrustpilot kayıtları\n\n153 adet yinelenen satır kaldırıldı. Dışa aktarımda tek tek inceleme URL’leri korunmadı.\n\n231,829\nSteam hesap listesi\n\n33,509 otomatik kayıtlı olarak sınıflandırılmıştır; 198,320 koleksiyoncunun “hırsız” etiketinin altındadır. Listelenen ürünler, satışın tamamlandığı anlamına gelmez.\n\nTahsilat denetimi ↓Kaynak arşivinde arama yap ↗",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Hesabınız.Onların erişimi.Kim cevap veriyor?"
          },
          {
            "level": 2,
            "id": null,
            "text": "Otomasyon,yazılı kayıtlar."
          },
          {
            "level": 3,
            "id": null,
            "text": "ArchiSteamFarm"
          },
          {
            "level": 2,
            "id": null,
            "text": "Hangi tuşNeden bahsediyoruz?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Kişisel Web API anahtarı"
          },
          {
            "level": 3,
            "id": null,
            "text": "Yayıncı Web API anahtarı"
          },
          {
            "level": 3,
            "id": null,
            "text": "OpenID / oturum belirteçleri"
          },
          {
            "level": 3,
            "id": null,
            "text": "Otomasyon, bir API anahtarından fazlasını kullanabilir."
          },
          {
            "level": 2,
            "id": null,
            "text": "Hâlâ oynuyor.Zaten açığa çıkmış."
          },
          {
            "level": 3,
            "id": "session-hidden-title",
            "text": "Güven, web sitesinden önce başlar."
          },
          {
            "level": 2,
            "id": null,
            "text": "Bu eşya nadir olabilir.Sınır geçerliliğini koruyor."
          },
          {
            "level": 2,
            "id": null,
            "text": "Veriler bize emanet edilmiştir.Erişimden sorumludur."
          },
          {
            "level": 3,
            "id": null,
            "text": "Ölçek halka açıktı"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve o masayı dış kaynaklara devretti — ve bunu açıkça belirtti"
          },
          {
            "level": 3,
            "id": null,
            "text": "İlk kabul"
          },
          {
            "level": 3,
            "id": null,
            "text": "İkinci kabul"
          },
          {
            "level": 3,
            "id": null,
            "text": "İçeri giriş yolu, Steam Destek'in kendisiydi.Valve bunu yazılı olarak belirtmiştir."
          },
          {
            "level": 4,
            "id": null,
            "text": "Kendi destek kanalı, içeri girmenin yolu oldu"
          },
          {
            "level": 4,
            "id": null,
            "text": "Aynı kapı Kasım 2025’te yeniden açıldı"
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve, yüklenicinin adını hiçbir zaman açıklamadı"
          },
          {
            "level": 2,
            "id": null,
            "text": "Her tutarbir kılıfa ihtiyacı var."
          },
          {
            "level": 3,
            "id": null,
            "text": "HFB — the largest inventory in the game"
          },
          {
            "level": 3,
            "id": null,
            "text": "44 disputed Market purchases"
          },
          {
            "level": 3,
            "id": null,
            "text": "CS.Money — 19,000+ botlardan elde edilen görünümler"
          },
          {
            "level": 3,
            "id": null,
            "text": "Qkss — aynı kapı, aynı oyuncu, zıt cevap"
          },
          {
            "level": 3,
            "id": null,
            "text": "İçeriden bilgi ticareti — bir yıllık süre boyunca"
          },
          {
            "level": 3,
            "id": null,
            "text": "İki aşamalı güvenlik önlemine rağmen cüzdan kaybı"
          },
          {
            "level": 3,
            "id": null,
            "text": "“Matvey” — işten çıkarmalardan iki yıl sonra"
          },
          {
            "level": 3,
            "id": null,
            "text": "Başka birinin biletiyle geri alma"
          },
          {
            "level": 3,
            "id": null,
            "text": "Hawkeye337 — ve Valve’in ikinci yazılı itirafı"
          },
          {
            "level": 3,
            "id": null,
            "text": "Yetkisiz kontör yükleme ve hediye edilen oyunlar"
          },
          {
            "level": 2,
            "id": null,
            "text": "231,829 adet hesap satışta.Valve, her birine ait günlükleri barındırır."
          },
          {
            "level": 3,
            "id": null,
            "text": "Trustpilot kayıtları"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam hesap listesi"
          }
        ],
        "links": [
          "https://phishdestroy.io/live-intel/?category=steam",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/lzt.market.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-evidence-lzt.json",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://github.com/JustArchiNET/ArchiSteamFarm/blob/main/ArchiSteamFarm/ArchiSteamFarm.csproj",
          "https://github.com/JustArchi",
          "https://github.com/renovate[bot]",
          "https://github.com/JustArchi-ArchiBot",
          "https://github.com/dependabot-preview[bot]",
          "https://github.com/renovate-bot",
          "https://github.com/actions-user",
          "https://github.com/dependabot-support",
          "https://github.com/Abrynos",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/automation-map.json",
          "https://phishdestroy.io/steam_dossier/tr/output_steam_network/network.html",
          "https://phishdestroy.io/steam_dossier/tr/output_steam_network/raw_data.json",
          "https://partner.steamgames.com/doc/webapi_overview/auth",
          "http://web.archive.org/web/20260915025812/https://partner.steamgames.com/doc/webapi_overview/auth",
          "https://partner.steamgames.com/doc/webapi/ISteamUserAuth",
          "http://web.archive.org/web/20260829124950/https://partner.steamgames.com/doc/webapi/ISteamUserAuth",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "http://web.archive.org/web/20260924181824/https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://store.steampowered.com/privacy_agreement/",
          "https://store.steampowered.com/oldnews/19618",
          "http://web.archive.org/web/20260809125516/https://store.steampowered.com/oldnews/19618",
          "https://kotaku.com/valve-explains-why-steam-customer-service-is-still-terr-1736988223",
          "http://web.archive.org/web/20250711004653/https://kotaku.com/valve-explains-why-steam-customer-service-is-still-terr-1736988223",
          "https://www.dexerto.com/counter-strike-2/valve-saves-hacked-cs2-player-threatened-with-ransom-over-300000-of-rare-stickers-3283135/",
          "https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "http://web.archive.org/web/20250818113925/https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "https://lis-skins.com/ru/blog/krupneisaia-mosenniceskaia-sxema-v-istorii-steam/",
          "https://www.reddit.com/r/cs2/comments/1e38jo4/stealing_accounts_and_removing_vac_bans_a_new/",
          "https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "http://web.archive.org/web/20250805141942/https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/outsourcing-archive-records.json",
          "https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "https://escorenews.com/en/csgo/news/44087-valve-steam-support-employee-accused-of-selling-inactive-accounts-inventories-worth-six-figures-b1t-has-one-of-these-skins",
          "https://phishdestroy.io/steam_dossier/tr/PART2_RESEARCH.md",
          "https://www.reddit.com/r/GlobalOffensive/comments/1h56shi/steam_support_is_stealing_accounts/",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/design-review/part2/quality-review.json",
          "https://phishdestroy.io/steam_dossier/tr/steam_evidence_archive.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/tr/investigation_part2.content.json",
      "export_json_sha256": "6fe6b76f8eed99971ba5d95fca5dd3279037c7a1712c25527c2544fe63642624"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "tr/legal_analysis.html",
      "language": "tr",
      "title": "Onların şartları, sizin haklarınız — “Steam” Dosyası",
      "source_url": "https://phishdestroy.io/steam_dossier/tr/legal_analysis",
      "source_html_sha256": "dd19dda09514c5dc61618f5ef46995a27ff1e1e083e18022f32f19f567e76823",
      "exported_at": "2026-09-29T00:20:49.315Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "legal_analysis.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/tr/legal_analysis.pdf?v=print-20260929-v5",
        "sha256": "037d1c6606e12cb223abfe14331bc0268a488827b0832cc35078cc443e8cfa11",
        "bytes": 105598,
        "pages": 7
      },
      "integrity": {
        "signed_object": "legal_analysis.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "legal_analysis.content.json.asc",
        "digest_file": "legal_analysis.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify legal_analysis.content.json.asc legal_analysis.content.json",
          "sha256sum -c legal_analysis.content.json.sha256"
        ]
      },
      "content": {
        "text": "Hukuki ve ekonomik rapor\nHukuki Analiz — Hizmet Şartları ve Mevzuata Uyum\n\nOnların şartları. Haklarınız.\n\nBU BÖLÜMÜN KANITLADIĞI ŞEY\n\nBu adli hukuki denetim, Valve Corporation ile Steam kullanıcıları arasındaki sözleşmeye dayalı asimetriyi, başlıca düzenleyici yargı bölgelerinde değerlendirmektedir. Bu denetim, iptal edilebilir abonelik lisansının yasal tüketici mülkiyet hakkını nasıl ortadan kaldırdığını ortaya koyar, dijital yeniden satış hakkının tükenmesi konusundaki Avrupa Adalet Divanı içtihatlarını analiz eder ve Dijital Hizmetler Yasası (DSA) ile GDPR Madde 15. uyarınca uyum durumunu inceler. Analiz, otomatik uygulama mekanizmalarının anlamlı bir itiraz olanağı olmaksızın nasıl işlediğini gösterirken, platformun piyasa ücretlerinin her kullanıcılar arası işlemden sistematik olarak ekonomik değer elde ettiğini ortaya koymaktadır.\n\n← Yönetici özetine geri dön\n\nBu rapor, Steam’ın beyan ettiği platform kuralları ile tüketicinin durumu arasındaki uçurumun hukuki, ekonomik ve teknik bir analizini sunmaktadır: itiraz imkânının çok sınırlı olduğu otomatik yaptırımlar ve dijital varlıklar üzerinde şirketin geniş kapsamlı kontrolü. Rakamlar kaynaklarıyla birlikte belirtilmiştir; bir rakamın birincil kaynağına ulaşılamadığı durumlarda ise bu rakam rapordan çıkarılmıştır.\n\nVektör 1\n\n\"Mülkiyet\" kavramını, sözleşme kapsamında dijital varlıkların geri alınabilmesini sağlayacak şekilde, iptal edilebilir bir lisansla değiştirmek.\n\nVektör 2\n\nSteam adresindeki destek sayfasında, geri alınamayacağı belirtilen otomatik yaptırım sistemi (VACNet).\n\nVektör 3\n\nHesap ve varlık kontrolleri, her yeniden satışta ekosistemden değer kaybına yol açan “15%” CS2 piyasa ücreti (5% Steam + 10% yayıncı ücreti) ile birleştirilmiştir.\n\nTerim asimetrisi\nSorumluluk feragati ve geri alınabilir lisans\n2.1 \"Abonelik\" modeli ve mülkiyet hakları\n\nSteam Abone Sözleşmesi’nin 2 bölümünde, kullanıcılara yalnızca bir kişisel, münhasır olmayan, devredilemez ve iptal edilebilir lisans. Sözleşme hükümleri uyarınca, Valve herhangi bir zamanda hesapları feshedebilir ve kullanılmayan Steam Cüzdan bakiyeleri kaybedilebilir.\n\n2.2 Geri ödeme yanılsaması ve AB Tüketici Hakları Direktifi\nYasal çerçeve\tGeri ödeme mekanizması\tSınırlama\nEU Consumer Rights Directive\tUnconditional 14-day right of withdrawal on digital content\tWaived if download begins with explicit consumer consent\nSteam SSA\t14 days / under 2 hours played\tValve may deny at its discretion for \"abuse\"\nDeğerlendirme\n\nValve AB’nin 14-adresinde belirtilen yasal cayma hakkı, ürünün değerlendirilmesinden önce indirme anında kabul edilen “14 gün / 2 saat” süre sınırına tabidir. Bu politika, yasal hakkı genişletmek yerine daraltmaktadır; bunun hukuka uygun olup olmadığı, yetkili makamın değerlendirmesi gereken bir konudur ve burada ileri sürülen bir sonuç değildir.\n\nDava\nİkincil Piyasa ve Rekabet Hukuku\nUFC Que Choisir – Valve davası — Fransa\n2019\nParis Mahkemesi: Hakların tükenmesi ilkesi dijital oyunlara da uygulanır — yeniden satış yasaldır\n2022 Ekim\nParis Temyiz Mahkemesi kararı bozdu\n23 2024 Ekim\nYargıtay (Yüksek Mahkeme): Video oyunları, Bilgi Toplumları Direktifi kapsamında “karmaşık eserler” olup, yazılım değildir. Dijital yeniden satış yasaklanmış. “Valve” (İçerik, her şeyden önemlidir) ilkesi geçerlidir.\nWolfire Games antitröst davası — Amerika Birleşik Devletleri (Valve’a İlişkin Antitröst Davası, Dosya No. 2:21-cv-00563)\n\nValve’ın En Çok Kayırılan Ülke (PMFN) maddesi, geliştiricilerin Steam anahtarlarını başka herhangi bir platformda daha ucuza satmasını yasaklamaktadır. Rakip mağazalar — hatta Valve’un 30% komisyonuna karşılık 12% komisyonu alanlar bile — bu tasarrufu tüketicilere yansıtamazlar.\n\n336Valve’ın toplam çalışan sayısı (2021). Kaynak: mühürleri kaldırılmış delil toplama belgesi.\n79Steam platformunun tamamını yöneten çalışanlar. Kaynak: gizliliği kaldırılmış delil.\n$3.5Mçalışan başına net gelir. Kaynak: gizliliği kaldırılmış delil.\n\nMühürsüz delil inceleme kayıtları şunu gösteriyor: 2021'da $8.5B brüt gelir 336’daki çalışanlar hakkında. Şu 79-Steam ekibinden bir kişi 373,000’i ve günlük destek taleplerini, bunları dış kaynaklı, otomatik çağrı merkezlerine yönlendirerek yönetti.\n\nGİZLİLİĞİ KALDIRILMIŞ DOSYA EKİ · W.D. WASH. DAVA2:21-CV-00563İç Keşif Notu\n\nTim Sweeney (Epic Games CEO’su) Gabe Newell’e: \"Ödeme işlemleri 2–5% ve bant genişliği CDN0.002/GB iken, Steam neden hâlâ brüt gelirden 30% pay alıyor? Steam’daki en popüler 25 oyunlarını hariç tutarsak, bahse girerim Valve, sonraki 1,000 oyunlarının çoğundan geliştiricilerin kendilerinin elde ettiğinden daha fazla kâr elde etmiştir.\"\n\nScott Lynch’in (Valve Corporation Operasyon Direktörü) Gabe Newell’a gönderdiği şirket içi iletisi: \"Kızdın mı dostum?\"\n\nYeminli İfadeye İtiraz (Bloomberg, 2026): 30 (b) (1) numaralı kural uyarınca yapılan ifade alma sırasında Gabe Newell, şu şekilde ifade verdi: \"Valve'ın, diğer platformlardaki üçüncü taraf yazılım geliştiricilerine fiyatları dayatma yönünde herhangi bir politikası veya uygulaması bulunmamaktadır.\" Davacılar, Newell’e, rakip mağazalarda daha düşük fiyat belirleyen geliştiricilere yönelik aktif fiyat denetimi ve ürün listesinden çıkarılma tehditlerini kanıtlayan Valve adresindeki şirket içi notları sundular. Mart ayı sonlarında 2026, Federal Mahkeme, Valve adresindeki şirketin özet karar talebini reddetti ve 32,000-adresindeki geliştiricilerin toplu davasını jüri yargılamasına sevk etti.\nKasım 2024\n\nToplu dava onayı verildi ~32,000 geliştiricileri Ocak ayından bu yana komisyon ödeyenler 2017, adresinde yer alan bilgiye ek olarak, buna paralel bir tüketici toplu davası da bulunmaktadır.\n\nTalep edilen tazminat\n\n$3.1B\nABD antitröst yasası kapsamında üç katına çıkarıldı = $9.3B olası maruz kalma.\n\nHaziran 2026: Yeni bir davada, Microsoft ve Valve’ın PC oyun dağıtımında rekabeti kısıtlayan bir kartel anlaşması yaptıkları iddia ediliyor.\n\nMali Suçlar ve Kara Para Aklamanın Önlenmesi (AML) Resmi Kabul Süreci\nValve Resmi İtiraf: Dünya Çapında Dolandırıcılık Tasfiyeleri (28 Ekim 2019)\n\n28 Ekim tarihinde 2019, Valve, yeni satın alınan Counter-Strike konteyner anahtarlarının ticareti ve pazar yeri üzerinden yeniden satışını resmi olarak sonlandırdı. Resmi kamu duyurusunda (blog.counter-strike.net/2019/10/26113), Valve Corporation, tasarladığı sanal ekonominin uluslararası bir kara para aklama merkezi haline geldiğini yazılı olarak kabul etmiştir:\n\n\"Geçmişte, gözlemlediğimiz anahtar alım satım işlemlerinin çoğu meşru müşteriler arasında gerçekleşiyordu. Ancak son zamanlarda, dünya çapındaki dolandırıcılık şebekeleri, elde ettikleri kazançları nakde çevirmek için CS:GO anahtarlarını kullanmaya yöneldi. Şu anda, pazarda alınıp satılan veya takas edilen anahtar satın alımlarının neredeyse tamamının dolandırıcılık yoluyla elde edildiği düşünülüyor.\"\n\nYasal Çerçeve: Bu itiraf, Washington Eyaleti Kumar Komisyonu’nun (WSGC) Valve adresine verdiği resmi ültimatomun ve Valve Genel Hukuk Müşaviri Karl Quackenbush’un, 23 adresindeki skin kumar alan adlarına (CSGO Lotto, CSGOLounge ve OPSkins dahil) yönelik Temmuz ayında yayınladığı 2016 “Faaliyetleri Durdurma ve Vazgeçme” emirlerinin ardından geldi; bu emirler, ancak kumarla ilgili cezai soruşturmaların platformun faaliyetlerini tehdit etmesinden sonra yayınlanmıştı.\n\nYargı yetkisi\nRusya’da bulunan ve kullanıcı tarafından ulaşılamayan bir hak sahibi\n\nAbonelik Sözleşmesi, Valve’u çok az yükümlülüğü olan ve kimseye ulaşılmayan bir taraf olarak sunmaktadır: kısıtlamalar kalıcıdır, itirazlar reddedilmektedir ve “yaptırım uygulanan bölgeler” hakkındaki tek bir cümle ile bütün bölgelere erişim engellenmektedir. Bu tutumun tam tersinde ise, Valve’un, normalde zorlu olarak değerlendirdiği bir yargı alanında kendi ticari çıkarları söz konusu olduğunda sergilediği davranış yer almaktadır.\n\nValve v. Touch Skins — dava öncesi fikri mülkiyet hakkı iddiası, Rusya\n1 2026 Eylül\nValve şirketi, Rus hukuk bürosu aracılığıyla Melling, Voitishkin ve Ortakları, şu işletmecilere duruşma öncesi talep mektubu gönderir: Dokunmatik Kaplamalar, büyük bir CS2 görünüm değiştirici, Rus Posta Servisi ve e-posta yoluyla.\nGerekçeler\nİddia edilen ihlaller üç gruba ayrılmaktadır: yazılıma ilişkin münhasır haklar; silah, bıçak ve eldiven görünümlerinin tasarım hakları; ve Valve’un ticari markaları. İşletmecilerin davranışları kasıtlı ve uzun süreli olarak nitelendirilmektedir.\nTalep\nFaaliyetleri derhal durdurun ve tüm altyapıyı silin — yazılımın kaynak kodu, web siteleri ve sosyal medya sayfaları — aksi takdirde Valve, bir Rus mahkemesinde dava açma hakkını saklı tutar önemli miktarda maddi tazminat ve konuyu şuraya havale etmek suç değerlendirmesi amacıyla kolluk kuvvetleri.\nSonuç\nMektubu aldıktan sonra platform, faaliyetlerini sonlandıracağını duyurdu. Bu olay, Valve’un Rusya’daki bir “skin-changer” geliştiricisine karşı ilk kez yasal araçlara başvurması olarak bildirildi.\n\nVeri madencisi Maxim \"GabeFollower\" Poletaev (X, ~11 Eylül 2026) ve Rus oyun basını tarafından bildirildi. Bu, dava açılmadan önceki bir iddia olup, henüz dava açılmamıştır; kamuya açık bir dava numarası bulunmamaktadır. Burada, mahkeme kaydı olarak değil, bildirildiği şekliyle ele alınmaktadır. Kaynaklar: dota2.ru arşivlenmiş 2026-09-24 ↗ · Shazoo.\n\nAynı yargı yetkisi alanı, diğer yön\n\nValve Rusya’nın hukuk ve düzenleme sistemine yabancı değildir. Bu Roskomnadzor kurallarına uygundur: Düzenleyici kurumun talebi üzerine, yasaklanmış içerik barındıran 260+ Steam topluluk sayfalarını kaldırmış olup, Roskomnadzor ise Steam adresinin mevzuatın gerekliliklerini karşıladığını kamuoyuna açıklamıştır. Rusya’nın “yönlendirme” yasası (Federal Yasa 236-FZ(2022 tarihinden itibaren yürürlükte olan) bu düzenleme, Rus kullanıcılara hizmet veren büyük yabancı internet platformlarının ülkede yerel bir varlık kurmasını ve Roskomnadzor nezdinde bir irtibat hesabı açmasını zorunlu kılıyor. Valve, hem düzenleyici kurumun içerik kaldırma emirlerine uyuyor hem de artık, skin’lerini fikri mülkiyet olarak korumak için Rus avukatlarından yararlanıyor ve Rus mahkemelerinin yaptırım tehdidini kullanıyor.\n\nDolayısıyla platform, gelir söz konusu olduğunda erişilebilir, yetkin ve haklarını savunur bir yapıdadır. Bunun tam tersi ise kullanıcı için geçerlidir: Yaptırım uygulanan bir bölgedeki ücretli bir müşteriye ilişkinin sona erdiği bildirilir, 2038, adresindeki bilet kapatılana kadar topluluk erişimi engellenir ve bu kararın sorgulanabileceği herhangi bir forum bulunmaz — \"Paramı almaktan ve işlemlerimi gerçekleştirmekten büyük memnuniyet duydular\", aynı hesaba ait, aynı İran IP adresinden yapılan iade talebi bir yıl önce onaylanmıştı (r/pcgaming, 4 Ağustos 2026; daha fazla uyarı mektubu Kart Ekonomisi Sergisi). Valve, bir skini savunmak için ulusal bir hukuk sisteminin tüm mekanizmalarını devreye sokar; ancak skin satın alan kullanıcıya hiçbir hukuki süreç sunmaz.\n\nValve Valve’in menfaati söz konusu olduğunda — Rus avukatlar, Rus mahkemelerinin tehdidi, Roskomnadzor’un içerik kaldırma emirlerine uyulması — aynı yargı yetkisini, içinde hareket edebileceği ve kurallarına uyabileceği bir alan olarak görürken, o pazarın ve diğer tüm pazarların kullanıcılarına karşı yükümlülüklerini ise herhangi bir sürecin tamamen dışında kabul eder. Gelir söz konusu olduğunda bir hak sahibi, kullanıcıların hakları söz konusu olduğunda ise ulaşılamaz bir taraf haline geliyor.\n\nKaynaklar: TASS (RKN: Steam uyumlu) · 236-sayılı Federal Yasa.\n\nHukuki fırsatçılık\nTahkim Maddesinin Kabulü\n2023 — saldırı\n\nHukuk firmaları (Zaiger LLC, Mason LLP), sosyal medya aracılığıyla binlerce kullanıcıyı topladı ve aynı anda on binlerce bireysel tahkim davası açtı.\n\nValve’in maruz kalması\n\n$225M+\nherhangi bir davanın esası üzerinde görüşülmeden önce, iade edilemeyen tahkim başvuru ücretleri olarak. Amerikan Tahkim Derneği (AAA) Tüketici Tahkim Kuralları ve Toplu Tahkim Ek Çizelgeleri uyarınca hesaplanmıştır. Zaiger LLC ve Mason LLP tarafından temsil edilen davacılar, Valve Corp. aleyhine ~75,000 adet bireysel tahkim talebinde bulunmuştur (antitröst davalarına paralel olarak Wolfire Games LLC ve diğerleri ile Valve Corp. arasındaki dava, Dava No. 2:21-cv-00563-JCC, W.D. (Wash.). AAA tüketici ücret tarifelerine göre, davalı şirket, her bir dava için geri ödemesiz idari dava ücretleri ve hakem atama teminatları olarak yaklaşık $3,000+ ödemektedir (75,000 dosya sayısı × $3,000 = yaklaşık $225M tutarında peşin usul yükümlülükleri). Teknoloji sektöründeki toplu tahkim risklerine ilişkin Bloomberg Law ve Reuters’ın hukuk raporlarına bakınız (2023–2024).\n\nDönem\tSSA uyuşmazlık çözüm mekanizması\tGözlemlenen etki\tSonuç\nBefore Sep 2024\tMandatory individual arbitration + class-action waiver\tIndividual litigation becomes economically irrational for users\tMass arbitration → $225M fee threat\nAfter Sep 2024\tDisputes in King County, WA courts only\tArbitration costs are avoided; cases consolidate in a single forum\tClass actions now possible\nSonuç\n\nOn yılı aşkın bir süre boyunca SSA, kullanıcıların jüri yargılaması hakkından feragat etmelerini ve bunun yerine bireysel tahkime başvurmalarını şart koşmuştu. Valve için bu mekanizmayı mali açıdan maliyetli hale getiren toplu tahkim başvurularının ardından, SSA, uyuşmazlıkların King County mahkemelerine yönlendirilmesi için değiştirildi. Bu değişiklik, anlamlı bir vazgeçme seçeneği sunulmadan uygulandı; kabul etmemenin alternatifi, hesabın silinmesi yoluyla satın alınan dijital varlıklara erişimin kaybedilmesiydi.\n\nAlgoritmik uygulama\nVACNet, Suçlu Olduğu Varsayımı ve Yanlış Pozitif Sonuçlar\nEkim 2023 — AMD Anti-Lag+\n\nBir AMD sürücü güncellemesi (v23.10.1), CS2’de Anti-Lag+ özelliğini etkinleştirdi; bu özellik, oyunun DLL işlevlerini engelledi. VAC, bunu hile kodu enjeksiyonu olarak sınıflandırdı ve Valve müdahale etmeden önce binlerce meşru kullanıcıya kalıcı yasaklar uyguladı.\n\n2023, Aralık — yüksek DPI\n\n10,000'ın üzerinde DPI değerine sahip ve kamerayı hızla döndüren oyuncular, kalıcı olarak yasaklandı. VACNet, fiziksel fare hareketini bir \"spinbot\" hilesinden ayırt edemedi.\n\nDestek kategorisi\tİddia edilen yanıt süresi\tGerçek sonuç\nRefund requests\t50 min – 1.5 hr\tAutomatic approval (<14 days, <2 hours played)\nAccount security / recovery\t3–12 hours\tDepends on documentation provided\nContesting a VAC ban\tForm response\tComplete refusal. Support cannot reverse VAC decisions. The ban is permanent.\nValve’in resmi politikası\n\n\"VAC yasakları kalıcıdır, tartışmaya açık değildir ve Steam Destek ekibi tarafından kaldırılmamaktadır.\"\n\nYasağı uygulayan destek kanalı, aynı zamanda inceleme talebinin reddedilmesini de bildirir: Steam Destek ekibi, bir VAC kararını geri alamayacağını belirtmektedir. Kullanıcı açısından, algoritmanın verdiği karar nihai sonuçtur.\n\nYeniden satışın ekonomisi\nSanal varlıklar üzerindeki kontrol ve yeniden satış ücreti\n15%'in CS2 piyasa ücreti — her yeniden satışta değer düşürülür\nİterasyon\tAlıcının bakiyesi\tSatıcı şunları alır:\tYanmış (15%)\n1\t$100.00\t$85.00\t$15.00\n2\t$85.00\t$72.25\t$12.75\n3\t$72.25\t$61.41\t$10.84\n10\t$23.16\t$19.68\t~$3.47\nTotal\t$100 → dust\tValve collects the 15% fee on each resale. Users must add new money to keep trading.\nCS2 takas kuralı değişikliği — Ekim 2025\n\nValve, önceden herhangi bir bildirimde bulunmadan, CS2 takas sözleşmesi kurallarını değiştirerek, Covert kalitesindeki eşyalar karşılığında nadir bıçak ve eldivenlerin garantili olarak edinilmesini mümkün kıldı. Bıçak fiyatları düştü, Covert kalitesindeki eşya fiyatları ise keskin bir artış gösterdi ve bunun üzerine piyasada panik satışları yaşandı.\n\nValve’ın dayandığı koruma, SSA’nın 7 maddesidir — platform kurallarının değiştirilmesinden dolayı herhangi bir sorumluluk kabul edilmez. Kullanıcılar, kuralların Valve önceden haber verilmeksizin veya tazminat ödenmeksizin değişebileceği bir ekonomide riski üstlenirler. Piyasa genelinde bildirilen zararın büyüklüğü tartışmalıdır ve birincil kaynak olmadan burada belirtilmemiştir.\n\nAvrupa’daki düzenleyici önlemler\nUOKiK, DSA ve Dijital Adalet Kanunu\nUOKiK — Polonya, Mayıs 2024\n\nPolonya’nın rekabet otoritesi (UOKiK), Valve Corporation ve beş yerli oyun yayıncısı/dağıtımcısı aleyhine, Polonyalı tüketicilerin dijital oyunlar için komşu EEA pazarlarına kıyasla 20% kadar daha fazla ödeme yapmasına neden olduğu iddia edilen fiyat sabitleme, kısıtlayıcı fiyat eşitliği hükümleri ve coğrafi engelleme uygulamalarıyla ilgili olarak resmi antitröst soruşturması başlattı. Rekabet soruşturmasının bir parçası olarak, UOKiK müfettişleri ve polis, Polonya’daki yerli ortak yayıncı ve dağıtımcıların tesislerinde (Valve’in Polonya’da herhangi bir tüzel kişiliği bulunmadığından, ’in bağlı ofisleri hariç; bkz. Valve) şafak baskınları düzenleyerek delil incelemesi gerçekleştirdi. Olası yasal para cezası: yıllık cirosunun %10%’sine kadar. Kaynak: UOKiK resmi açıklaması, “UOKiK Başkanı, Valve ve oyun geliştiricileri aleyhine soruşturma başlattı”, Mayıs 2024.\n\nDijital Hizmetler Yasası (DSA)\n\nOtomatik moderasyonda şeffaflık gerektirir. Steam, VACNet ile ilgili yanlış pozitif/yanlış negatif verilerini yayınlamamaktadır ve destek kanalı, VAC kararlarının geri alınamayacağını belirtmektedir.\n\nDijital Adalet Yasası — 2026\n\nBeklenen hükümler: ücretli içeriğe kalıcı erişim, haklardan feragat anında “karanlık desenlerin” yasaklanması, dijital varlıklara ilişkin mülkiyet haklarının tanınması ve kalıcı envanter el koymasından korunma.\n\nSonuç\nKurallar ile kayıtlar arasında tespit edilen tutarsızlıklar\n1\n\nMülkiyet uçurumu. Kullanıcılar, sözleşme uyarınca Valve’un iptal etme hakkına sahip olduğu bir lisans için tam fiyat ödüyorlar. Fransa Yargıtayı (Ekim 2024), dijital yeniden satışın koruma kapsamına girmediğine hükmederek bu görüşü hukuken kesinleştirdi.\n\n2\n\nAlgoritmik uygulama. VACNet, haksız yasaklamalar uyguladı (AMD sürücüleri, yüksek DPI vakaları). Steam Destek ekibi, bir VAC kararını geri alamayacağını belirtiyor; dolayısıyla algoritmanın kararı nihai olarak geçerlidir.\n\n3\n\nÜcret tasarrufu. 15%’ın CS2 pazar ücreti (5% Steam + 10% yayıncı ücreti), her yeniden satışta ürünün değerini düşürür ve platform kuralları önceden haber verilmeksizin değiştirilebilir; Valve’ın bu tür değişikliklere ilişkin sorumluluğu, SSA kapsamında reddedilmektedir.\n\n4\n\nTahkim hükmü kaldırılmıştır. SSA, Eylül ayında zorunlu tahkim uygulamasını kaldırdı 2024,; zira toplu başvurular sonucunda Valve, yaklaşık225milyon dolarlık ücret yüküyle karşı karşıya kalmıştı. Kullanıcılara bu değişiklikle ilgili anlamlı bir vazgeçme imkânı sunulmadı.\n\n5\n\nSeçici yargı yetkisi. Valve Bir Rus hukuk bürosu (Melling, Voitishkin & Partners) ile anlaştı ve Touch Skins aleyhine Rusya’da dava açmakla tehdit ederken, aynı zamanda söz konusu pazardaki kullanıcılara karşı yükümlülüklerini herhangi bir yargı sürecinin dışında tuttu. Valve, ticari çıkarları söz konusu olduğunda hak sahibi olarak hareket ederken, kullanıcıların hakları söz konusu olduğunda ise ulaşılamaz bir taraf olarak davranmaktadır.\n\n← Bölüm I: Proxy atlama ve kumarBölüm II: Erişim ve hesap verebilirlik →\n\nHukuki kaynaklar ve dava kayıtları, orijinal yayıncılarına ve arşivlerine atıfta bulunularak aktarılmıştır. İlgili belgeler üzerinde herhangi bir mülkiyet iddiasında bulunulmamaktadır.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Hukuki Analiz — Hizmet Şartları ve Mevzuata Uyum"
          },
          {
            "level": 2,
            "id": null,
            "text": "Sorumluluk feragati ve geri alınabilir lisans"
          },
          {
            "level": 3,
            "id": null,
            "text": "2.1 \"Abonelik\" modeli ve mülkiyet hakları"
          },
          {
            "level": 3,
            "id": null,
            "text": "2.2 Geri ödeme yanılsaması ve AB Tüketici Hakları Direktifi"
          },
          {
            "level": 2,
            "id": null,
            "text": "İkincil Piyasa ve Rekabet Hukuku"
          },
          {
            "level": 3,
            "id": null,
            "text": "UFC Que Choisir – Valve davası — Fransa"
          },
          {
            "level": 3,
            "id": null,
            "text": "Wolfire Games antitröst davası — Amerika Birleşik Devletleri (Valve’a İlişkin Antitröst Davası, Dosya No. 2:21-cv-00563)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve Resmi İtiraf: Dünya Çapında Dolandırıcılık Tasfiyeleri (28 Ekim 2019)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Rusya’da bulunan ve kullanıcı tarafından ulaşılamayan bir hak sahibi"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve v. Touch Skins — dava öncesi fikri mülkiyet hakkı iddiası, Rusya"
          },
          {
            "level": 3,
            "id": null,
            "text": "Aynı yargı yetkisi alanı, diğer yön"
          },
          {
            "level": 2,
            "id": null,
            "text": "Tahkim Maddesinin Kabulü"
          },
          {
            "level": 2,
            "id": null,
            "text": "VACNet, Suçlu Olduğu Varsayımı ve Yanlış Pozitif Sonuçlar"
          },
          {
            "level": 2,
            "id": null,
            "text": "Sanal varlıklar üzerindeki kontrol ve yeniden satış ücreti"
          },
          {
            "level": 3,
            "id": null,
            "text": "15%'in CS2 piyasa ücreti — her yeniden satışta değer düşürülür"
          },
          {
            "level": 3,
            "id": null,
            "text": "CS2 takas kuralı değişikliği — Ekim 2025"
          },
          {
            "level": 2,
            "id": null,
            "text": "UOKiK, DSA ve Dijital Adalet Kanunu"
          },
          {
            "level": 2,
            "id": null,
            "text": "Kurallar ile kayıtlar arasında tespit edilen tutarsızlıklar"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/tr/#briefing-heading",
          "https://dota2.ru/news/67707-valve-cerez-uristov-napravila-krupnoj-rossijskoj-skincendzer-platforme-trebovanie-o-prekrasenii-deatelnosti/",
          "http://web.archive.org/web/20260924181657/https://dota2.ru/news/67707-valve-cerez-uristov-napravila-krupnoj-rossijskoj-skincendzer-platforme-trebovanie-o-prekrasenii-deatelnosti/",
          "https://shazoo.ru/2026/09/12/190508/valve-cerez-rossiiskix-iuristov-dobilas-zakrytiia-krupnogo-skinceindzera-dlia-cs2",
          "https://www.reddit.com/r/pcgaming/comments/1vf24lu/warning_to_all_gamersexpats_steam_took_my_money/",
          "https://phishdestroy.io/steam_dossier/tr/card_economy.html#asymmetry",
          "https://tass.ru/obschestvo/23235387",
          "https://base.garant.ru/401414628/",
          "https://uokik.gov.pl/postepowanie-wyjasniajace-w-sprawie-valve-i-dystrybutorow-gier",
          "https://phishdestroy.io/steam_dossier/tr/",
          "https://phishdestroy.io/steam_dossier/tr/investigation_part2.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/tr/legal_analysis.content.json",
      "export_json_sha256": "0213fdfd61f79aa9362efb1f84b9db58ee9bd920133f827cc132dd003c908681"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "tr/license_disclaimer.html",
      "language": "tr",
      "title": "Lisans · Haklar · Sorumluluk Reddi — PhishDestroy",
      "source_url": "https://phishdestroy.io/steam_dossier/tr/license_disclaimer",
      "source_html_sha256": "2eefa27f33ccdd5fb79aa8013da78989192eeee6d60340ba85f87c005d7894ea",
      "exported_at": "2026-09-29T00:20:50.858Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "license_disclaimer.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/tr/license_disclaimer.pdf?v=print-20260929-v5",
        "sha256": "2d8b13361c41decdd17e032e1d44710a5d3a327f8fdad48b4c5bed27a87d371c",
        "bytes": 118038,
        "pages": 10
      },
      "integrity": {
        "signed_object": "license_disclaimer.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "license_disclaimer.content.json.asc",
        "digest_file": "license_disclaimer.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify license_disclaimer.content.json.asc license_disclaimer.content.json",
          "sha256sum -c license_disclaimer.content.json.sha256"
        ]
      },
      "content": {
        "text": "PHISHDESTROYAdli soruşturma · Valve / Steam\nLisans · Haklar · Sorumluluk Reddi\nLisans ve Yasal Uyarı — Kamu Malı Olarak Adanma\n\nTüm hakları saklıdır insanlığa teslim oldu.\n\nBU BÖLÜMÜN KANITLADIĞI ŞEY\n\nBu belge, PhishDestroy Steam Dossier’i düzenleyen koşulsuz kamu malı tahsisi (CC0 1.0 Universal) ve MIT yazılım lisans koşullarını belirlemektedir. Tüm adli bulgular, delil veri kümeleri, ağ grafikleri ve analitik metodolojiler, dünya çapında kısıtlamasız düzenleyici, hukuki ve akademik kullanım amacıyla geri alınamaz bir şekilde kamu malı olarak tahsis edilmiştir.\n\n← Yönetici özetine geri dön\n\nPhishDestroy bu materyale ilişkin her türlü hakkından feragat eder — onu çoğaltma, satma, üzerine adınızı yazma haklarından. Aşağıda, tek bir sesin dilinde kaleme alınmış iki belge yer almaktadır: Valve adresine gönderilen, bizim gerçek yazım tarzımızla kaleme alınmış bir açık mektup ve bu içeriği ileriye taşıyacak yetkili kurum için hazırlanmış resmi bir feragatname.\n\nAraştırma · Valve Corporation / SteamGenel sürüm — son kullanma tarihi yok, geri alma hakkı yok\nMUAF TUTULMUŞ\nBölüm ILisans — asıl hukuki kısım, ama insani\n\nPhishDestroy Bu materyale ilişkin tüm haklarından feragat eder. Sıfır. Yok. Bitti. İstediğiniz gibi çoğaltabilir, satabilir, üzerine adınızı yazabilir, patronunuzun vücuduna dövme olarak yaptırabilirsiniz, ne isterseniz. Kaynak göstermenize gerek yok, mesaj atmanıza gerek yok, teşekkür kartı beklemiyorum.\n\nGerçekten tek bir kural (evet, sadece bir tane)\n\nTerörist olup olmadığınızı SİZ belirleyemezsiniz.\n\nEğer Rusya’dan veya OFAC’ın yaptırım uyguladığı herhangi bir ülkeden bir kullanıcıysanız — bu içerik SİZİN için DEĞİLDİR. Hiçbir kaçış yolu yoktur. Yaptırımlarınızın tadını çıkarın.\n\nVe eğer Moskova’da otururken Steam bölgesini Türkiye olarak değiştirdiyseniz — bu yaratıcı coğrafya anlayışınız için tebrikler. Hâlâ Rus’sun. Yaptırımlar hâlâ geçerli. Mesele tam da bu.\n\nBölüm IIBu nedir ve neden var?\n\nValve hakkında, Valve’daki ortalama bir çalışanın kendisi hakkında bildiğinden daha fazla bilgi yayınlayacağız. Bu bir övünme değil. Sadece işler bu noktaya geldi.\n\nBuraya nasıl geldik? Komik bir hikâye: Steam aslında bizi yarattı. Bizi dolandırıcılarıyla, destek talepleriyle, yasak kaçırma ekosistemiyle büyüttü — ve işte şimdi buradayız. Kin tutmuyoruz. Aslında oldukça şiirsel bir durum.\n\nHenüz bu hikayenin başlangıcını okumamış olanlar için — Valve’in son derece pahalı Avrupalı avukatlarıyla (sorduğunuz için söyleyeyim, Taylor Wessing) daha önce tanışmıştık:\n\nhttps://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d arşivlenmiş 2026-08-21 ↗\n\nHoş bir karşılaşma. Özellikle de saatlik ücretlerini düşünürsek.\n\nValve'in haberi var mıydı? Evet. Taylor Wessing'in haberi var mıydı? Neredeyse kesinlikle evet. Ama o kadar zengin olduğunuzda, yasalar bir zorunluluktan çok bir tür ruh hali haline gelir, değil mi?\n\nAslında cevap da bu sayılır.\n\nSteam Yıllarımızı dolandırıcıları ortaya çıkarmakla geçirdik. Her zaman kasıtlı olarak değil — bazen dolandırıcılar, sadece Valve ile olan bağlantıları nedeniyle bu sitenin izlerini üzerlerine alıyordu. Bu konuda abartılı davranmaya çalışmıyoruz. Kesin olmaya çalışıyoruz. Dürüst olmak gerekirse, bu bizim için abartılı davranmaktan daha zor — bizim yazım tarzımız işte böyle.\n\nBu bir çelişki mi?\n— Hayır.\n\nBu sorun çözülebilir mi?\n— Evet. Ama hiçbir gizlilik anlaşması imzalamayacağız ve üç kuruşa hata ödül programına katılmayacağız.\n\nBu sahtekarlık sorununu düzeltmelerini beklemek için 4 yıllardan fazla bekledik; ancak o zaman bu konuyu kamuoyuna duyurabildik. Çünkü bunu daha önce yazmış olsaydık, Steam o küçük mağdur yüzünü takınıp “aktif tehdit!” diye bağırır ve bizi sonsuza dek yasal mülkiyetlerine geçirecek bir belgeyi imzalamamız karşılığında cüzi bir miktar para teklif ederdi. Hayır, teşekkürler.\n\n(Ayrıca: Valve sitesi de gizlilik anlaşmasını ihlal ediyor. Kendi çalışanları ihlal ediyor. Üst kademedeki çalışanlar. Ama tabii, hadi bizimkilerden bahsedelim.)\n\nBölüm IIIValve’a açık mektup — cidden, şunu bir oku\n\nValve: Bu alan adının kaldırılmasını istiyorsanız, bize e-posta gönderin. Bu görüşme için dışarıdan bir avukata gerek yoktur.\n\nKonuyu bilmeyenler için: Dr. Patrick, Aberdeen Üniversitesi’nden Uluslararası Ticaret Hukuku alanında Hukuk Yüksek Lisansı’na sahiptir ve — şimdi dikkatli dinleyin — doktora tezini tam anlamıyla bilgi teknolojileri hukuku üzerine tamamlamıştır. Kısa bir süre önce Taylor Wessing’de ortak oldu; bu firmanın iş modelinin tamamı, Valve gibi şirketlere, karşı tarafın parası ya da sabrı tükenene kadar davaları uzatmak için fahiş meblağlar fatura etmek üzerine kurulu.\n\nOnu suçlamıyoruz. Saatlik ücret ödeyen zengin ve suçlu müvekkiller — kariyer açısından akıllıca bir hamle. Sadece bunun masraflarını sizin karşılamanız gerektiğini düşünmüyoruz.\n\nAnlaşma (açık teklif, avukata gerek yok)\n\nValve'in gerçekçi olarak ulaşabileceği tek şey bu alan adıdır. Soruşturma, yönlendirmeler ve ilgili kaynaklar halihazırda devrede — alan adı olsun ya da olmasın, bunlar devam edecektir.\n\nEğer bu alan adını istiyorsanız:\n\nBT hukuku uzmanlarınızın adil bir fiyat belirlemesine izin verin.\n\n50% SEAL Vakfı’na bağışlanır.\n\nAlan adını kapatıyoruz. Drama yok. Mahkeme yok. Bitti.\n\nBu bir tehdit değil. Gerçekten ulaşılabilir olan tek şey için yapılan açık ve net bir teklif. Başka hiçbir yolla bunu elde edemezsin — durumun doğası böyle.\n\nValve’a doğrudan “zarar” verecek miyiz? Muhtemelen mali açıdan hissedecekleri bir şekilde değil. Hayal dünyasında yaşamıyoruz. Ama bunu dürüstçe, açıkça ve popülerlik peşinde koşmadan yapacağız — çünkü popülerliğe ihtiyacımız yok. Yeterince zaman ayırıp bakarsanız her zaman herkesin görebileceği şeyi dünyanın görmesini istiyoruz.\n\n5 yıllık arşivimiz var. Valve’un avukatlarının delil sunumu sırasında ortaya koydukları şeyler — ajanların görebileceğini doğrulayan veriler, parmak izleri ve bize kelimenin tam anlamıyla teslim ettikleri yazılı belgeler — yeterlidir. Bunları işlenmemiş haliyle sızdırmamıza gerek yok.\n\nKim ne alacak?\n\nDüzenleyici kurumlara aslı verilir.\n\nAraştırmacılar ve gazetecilere sansürlenmiş versiyonlar verilir (mağdur raporları, çocukların oturum açma bilgileri ve Valve sitesindeki sevimli destek yorumları, bariz nedenlerden ötürü kaldırılmıştır).\n\nEtkilenen hesaplar arasında reşit olmayanlar da vardı ve bu kişilere herhangi bir bildirimde bulunulmadı. Bu bulgu, mağdur raporları ve kimlik bilgileri çıkarılmış halde düzenleyici kurumun dosyasında yer almaktadır; zira bu konunun bir makalede değil, veri koruma otoritesinin gündeminde ele alınması gerekmektedir.\n\nAyrıca, Valve — bu konuyu nasıl ele alacağınıza karar vermeden önce bir şeyi netleştirmek istiyoruz: PhishDestroy bir topluluktur, bir kişi değil. Bunu, toplulukla konuşma zahmetine girmeden topluluğa hukuki yazışmalar gönderdiğinizde anladınız — sadece verileri sömürdünüz ve hesapları engellediniz.\n\nTopluluğumuzun Valve ile herhangi bir sorunu yoktur. Biz bunu aramadık. Sizin yetiştirdiğiniz dolandırıcılar bizi buldu. Onları engelledik. Ve işte bu noktaya geldik.\n\nBölüm III-BMüttefik kaynaklar — özellikle Steam adresine yönelik bir not\n\nAmplifikasyon yapısı konusunda açık ve net olmak istiyoruz, çünkü bunun var olmadığını varsaymak dürüstlükten uzak bir tutum olur.\n\nPhishDestroy’da, topluluk içindeki durumu anladığımız kadarıyla, bu içeriği devralıp ilerletecek en az iki müttefik kaynak bulunmaktadır.\n\nBunun pratikte anlamı şudur:\n\nKesişen konularda her biri kendi bakış açısını ortaya koyuyor.\n\nOnlar bağımsızdır — bizim talimatlarımızı uygulamazlar, biz de onlarınkini uygulamayız. Genel konu aynı, ancak yöntemleri farklıdır.\n\nPart 1. adresinde etkinleştirilmeyecekler. Onlar izliyor.\n\nValve’ın siteyi kaldırmamayı tercih etmesi durumunda:\n\nBunların “Bölüm 2” veya “Bölüm 3.”dan sonra ortaya çıkmasını bekleyin.\n\nÇalışmalarımızdan yararlı buldukları kısımları alıp, kendi çalışmalarlarıyla tamamlayacaklar ve kendi adlarına yayınlayacaklar.\n\n1. maddesindeki lisans tam da bu tür durumlar için tasarlanmıştır: içerik gitmesi gereken yere ulaşır, zenginleştirilir, genişletilir — ve ne biz ne de onlar birbirlerine atıfta bulunma yükümlülüğü taşır.\n\n(Sorumluluk zincirleri konusunda merak eden avukatlar için not: Böyle bir şey yoktur. Bu kaynaklar bizden talimat, finansman ya da veri almazlar. Kamuya açık bilgileri inceler ve kendi sonuçlarını çıkarırlar. Tıpkı sizin de yapabileceğiniz gibi.)\n\nBunu korkutmak için söylemiyoruz. Bunu, Valve tarafında strateji belirleyen kişinin, bilgi ortamının gerçekte nasıl bir görünümde olduğu konusunda doğru bilgilere sahip olması için söylüyoruz.\n\nMaddemizi destekleyen ve tamamlayan bir kaynak, bir hikâye olabilir. Bunu bağımsız olarak yapan ve benzer sonuçlara varan iki kaynak ise bir örüntüdür. Düzenleyici kurumların dikkatini çeken şey, işte bu örüntülerdir.\n\nBölüm IVPara, yasaklar, tüm bu sirk\n\nSteam’ın kumar sitelerini ve dolandırıcıları yasaklamasıyla ilgili şu gerçek var: Bu bir yaptırım değil. Bu, gelir elde etmek. Valve parayı cebe indiriyor, ellerini temizliyor, sonra sahneye çıkıp herkese Pokémon kartları ve beyzbol hakkında masum bir hikâye anlatıyor.\n\nDestek tarafındaki güvenlik ihlallerinin belgelendiği durumlarda — buna, Şubat ayında Valve adresinde yer alan ve yardım talepleri yoluyla ele geçirilen yüksek değerli hesapların sorumluluğunu üstlendiğini belirten yazılı itiraf 2023 ile, $320k tutarındaki içeriden bilgi ticareti olayının ardından Dexerto ve Escorenews tarafından bildirilen yüklenici personelinin işten çıkarılmaları da dahildir (Bölüm II, §04 · Ana Dosya §14.1) — bunlar, kamuoyuna açıklanmış itiraflar ve araştırmacı gazetecilik haberlerine dayanmaktadır. Destek personelinin kumar yoluyla ek gelir elde ettiği ya da yasakların kaldırılması karşılığında komisyon aldığına dair kanıtlanmamış söylentiler, kamuya açık kayıtlarda doğrulanmamıştır ve bu yazıda ele alınmamıştır.\n\nBu arada Valve, 2017. adresinde skinlerin düzgün bir şekilde izlenmesini imkansız hale getirdi. Hatta bunu kendi forumlarında da tartıştılar. Buna “kumar karşıtı önlemler” adını verdiler — oysa skin kumar ekosistemi, bundan sonraki yıllar boyunca Steam’un altyapısı üzerinden milyarlarca dolarlık işlem gerçekleştirmeye devam etti. Harika bir marka stratejisi.\n\nŞunu kanıtlayacağız:\n\nSkins, Monero’dan daha anonimdir\n\nBir Peru kartelinin, para transferi amacıyla Dota 2'daki karakter görünümlerini kullandığı iddia ediliyor\n\nSteam işlevsel olarak, “koleksiyon kartları” şeklinde ~7milyar dolarlık bir yaptırım atlatma makinesidir (evet, bir savcıya gerçekten de ‘koleksiyon kartları’ dediler)\n\nSkinler konusuyla ilgili bir videomuz var. Göreceksin.\n\nAyrıca şunu da biliyoruz:\n\nReddit’in moderasyon süreci, Valve adresindeki kaynaklardan etkilenmektedir.\n\nÜçüncü taraf Steam veri altyapısı (örneğin steamid.uk) bir özel şahıs tarafından işletilmektedir (msart) ve bununla bağlantılı kardeş proje olan yasak listesi projesi (steambans.com arşiv) onaylanmış bir Valve topluluk moderatörü tarafından ortaklaşa yönetilmektedir (killahinstinct_) — böylece platformdaki yasaklamalara ilişkin bağımsız denetim tamamen Valve’un yetki alanı içinde kalıyor (bkz. Kart Ekonomisi §08)\n\nKontrol edemedikleri şeyleri yasaklarlar\n\nValve: Eğer aptal rolü oynamaya devam ederseniz — sorun değil. Güvenli limanınız not edildi. Google Analytics zaten kullanıcılarınızın IP adreslerini gizliyor. Neyin silindiğini görüyoruz. Sadece bunu, avukatlarınızın ilgileneceği kadar ucuza kanıtlayamıyoruz. Henüz.\n\nBölüm VKötü amaçlı yazılım meselesi — evet, bundan bahsediyoruz\n\nOlayların sırası konusunda son derece açık konuşalım, çünkü bu tam olarak kim olduğunuzu ortaya koyuyor.\n\nOyundaki bu güvenlik açığını kamuoyuna AÇIKLAMAYACAĞIZ. Bunu Steam adresine BİLDİRMEYECEĞİZ. Program bir gizlilik anlaşması (NDA) gerektiriyor ve böyle bir anlaşmayı imzalamamız, etkilenen kullanıcılara hesaplarına ne olduğunu anlatmamızı engelleyecektir. Bu hesaplarını kaybeden kişilere ve düzenleyici kurumlara durumu açıklamak, bu çalışmanın amacıdır; bir gizlilik anlaşması ise bununla bağdaşmaz.\n\nİşte gerçekte olanlar: Bu güvenlik açığı, ilgili çevrelerde adeta herkesin bildiği bir sırdır. Bağımsız güvenlik araştırmacılarının, bu güvenlik açığını istismar eden tam kodunu Steam Destek ekibinin gözünün içine soktuklarını kesin olarak biliyoruz. Bu kısım halledildi. Kendi resmi kanallarınız aracılığıyla resmi olarak uyarıldınız.\n\nPeki Valve ne yaptı? Hiçbir şey. Çünkü Valve için güvenlik, kârla eşdeğer değildir — aksine, tam tersidir. Güvenlik, bir maliyet kalemidir. Bir tehdit kritik bir boyuta ulaşıp kamuoyunda felaket niteliğinde bir imaj krizine yol açana kadar, Valve bunu acil bir mesele olarak görmez.\n\nPeki ne yapıyoruz? Kamuoyuna bunun varlığını duyuruyoruz; çünkü “Valve’ın sistemik bir kötü amaçlı yazılım tehdidinden haberdar olmasına rağmen aktif olarak hiçbir şey yapmamayı tercih etmesi”, şu anda bunu okuyan düzenleyici kurumlar için hayati önem taşıyan bir bilgi.\n\nOyun gerçekten devasa. Burada adını vermeyeceğiz. Ama şunu iyi anlayın:\n\nBu, sunucunun sizden “bir sürücü yüklemenizi” istediği o önemsiz CS:GO “script-kiddie” saçmalıkları gibi bir şey DEĞİLDİR. Bu, felaket niteliğinde bir durumdur.\n\nBu, Unturned seviyesinde bir kabus: sunucuya bağlanırken sıfır tıklamayla RCE. Bir sunucuya katılıyorsunuz. Hiçbir şeye tıklamıyorsunuz. Hiçbir şey indirmiyorsunuz. Bağlantının kendisi saldırı yüzeyi haline geliyor ve makineniz tamamen ele geçiriliyor. Gerçekçi olalım: Bir RCE yerleştirmek vValve'ın güvenilir dijital sertifikalarını kullanarak yerel antivirüs programlarını atlatmak, Steam'da artık yeni bir şey bile değil. Bu, pratikte ekosisteminizin yerleşik bir özelliği haline gelmiş durumda.\n\nValve Bunun varlığını zaten biliyor. Ancak en sevdikleri, korkakça bir yasal boşluktan yararlanıyorlar: oyun teknik olarak üçüncü bir taraf tarafından geliştirildiği için, Valve sorumluluktan kaçıyor. Oyunu dağıtıyorlar, ödemeleri işliyorlar, altyapıyı barındırıyorlar, ancak sıfır tıklamalı bir RCE milyonlarca kullanıcılarını tehdit ettiğinde tutumları şudur: “Bizim oyunumuz değil, bizim sorumluluğumuz değil.”\n\nBu durum kaçınılmaz olarak patladığında, üçüncü taraf geliştirici tüm suçu üstlenecek ve Valve ise sorunu çözmeye “yardımcı” olan sorumlu bir platformmuş gibi davranarak paçayı kurtaracak. Klasik Valve korkaklığı. Bu senaryoyu daha önce de gördük.\n\nBunu kayıt altına alıyoruz ki düzenleyici kurumlar, savcılar ve gazeteciler, Valve’in aktif kötü amaçlı yazılımları tam olarak nasıl ele aldığını anlasınlar: üçüncü taraf geliştiricilerin arkasına saklanarak, gizlilik anlaşmalarıyla oyuncuların sesini keserek ve oyuncuları savunmasız bir durumda bırakarak.\n\nAçık mektubun sonuResmi kayıtlar başlıyor\nResmi dil · resmi makamlar için\nBeyannameKullanım ve haklar konusunda\n\nPhishDestroy Proje ve Siber Güvenlik Koalisyonu\n\nBu beyan, bu dosya setindeki her bir başvuru ve her bir ek belgeye eşlik etmektedir. Bu beyan, söz konusu materyali eline geçen her türlü yetkili makam, mahkeme, düzenleyici kurum, savcı, araştırmacı, gazeteci veya mağdur kişiye yöneliktir.\n\n1. Kullanımla ilgili herhangi bir koşul bulunmamaktadır\n\n1.1 Koalisyon tarafından bu başvuruda hazırlanan tüm materyaller — olgusal beyanlar, analizler, Koalisyon tarafından hazırlanan ekler, araçlar ve bulgular — HERHANGİ BİR HAK SAKLI TUTULMAKSIZIN kamuoyuna açıklanmaktadır.\n\n1.2 Herkes, bize sormadan ve haber vermeden şunları yapabilir:\n\nbunu, tamamen veya kısmen çoğaltmak;\n\nbunu uyarlayabilir, düzenleyebilir, yeniden yazabilir, yeniden yapılandırabilir veya düzeltebilir;\n\nbunu çevirin;\n\nalıntı yaparken bunun bir alıntı olduğunu belirtmeden;\n\nbunu resmi belgelere, bulgulara, kararlara, dava dilekçelerine, raporlara veya basın materyallerine dahil etmek;\n\nbunu alıcının kendi eseri veya alıcının kendi bulgularıymış gibi sunmak;\n\nbunu hammadde olarak kullanın ve geri kalanını atın;\n\nve aynı şartlarla başka herhangi birine devredin.\n\n1.3 KAYNAK GÖSTERİLMESİ GEREKMEMEKTEDİR VE BUNUN İSTENMEMEKTEDİR. Koalisyonun adı geçirilmesine, alıntılanmasına, kaynak gösterilmesine, teşekkür edilmesine, danışılmasına veya bilgilendirilmesine gerek yoktur. Bu kaynakta yer alan materyaller bir yetkili kuruma yardımcı olursa ve Koalisyondan hiç bahsedilmezse, BU TAMAMEN TATMİN EDİCİ BİR SONUÇTUR ve Koalisyon, bu konunun gündeme gelmemesi için bunu önceden belirtmektedir.\n\n1.4 Öte yandan, bir yetkili kurum Koalisyonu kaynak olarak göstermeyi daha uygun bulursa, bunu yapmakta serbesttir. Seçim tamamen alıcıya aittir ve her iki seçeneğin de herhangi bir sonucu yoktur.\n\n1.5 Bu bir FERAGATNAMEDİR, lisans teklifi değildir. Kabul edilmesini gerektirmez, herhangi bir yükümlülük getirmez ve ihlal edilemez. Koalisyon tarafından yayınlanan yazılım, MIT lisansı kapsamında ayrı olarak yayınlanmaktadır; araştırma ve bulgular, izin verilen en geniş ölçüde kamu malı olarak yayınlanmaktadır ve bir yargı yetkisi alanında feragatne izin verilmediği durumlarda, Koalisyon aynı amaçla geri alınamaz, dünya çapında ve telif ücreti ödenmeyen bir lisans vermektedir.\n\n2. Bunun neden sadece bir nezaket meselesi olarak değil, pratik açıdan da önemli olduğu\n\n2.1 Bir yetkili makam, o tarafın talebi üzerine hareket ediyor gibi görünme ya da o tarafla bir tür bağ kurma endişesi nedeniyle, dışarıdan bir tarafça sağlanan bilgilere güvenmek konusunda makul bir tereddüt gösterebilir.\n\n2.2 BURADA KARIŞILACAK HİÇBİR ŞEY YOKTUR. Koalisyon hiçbir şey talep etmez, kendisine hiçbir şey borçlu olunmaz, hiçbir şeyi elinde tutmaz ve hiçbir türden beklentisi yoktur. Daha sonra bir hak iddia edemez, övgüyü kendine mal edemez, kötüye kullanımdan şikayet edemez veya materyalin nasıl nitelendirildiğine itiraz edemez; çünkü bunu yapabileceği hiçbir dayanak bırakmamıştır.\n\n2.3 Dolayısıyla, bu materyali kullanan bir kurum, Koalisyon adına hareket etmemektedir. Sadece, tesadüfen başka biri tarafından derlenmiş olan kamuya açık bilgileri kullanmaktadır.\n\n3. Her şey zaten açık\n\n3.1 Koalisyonun çalışmaları varsayılan olarak halka açıktır:\n\nSoruşturmalar şu adreste herkese açık olarak yayınlanmaktadır: https://phishdestroy.io ve serbestçe okunabilirler;\n\nBu araç, MIT lisansı kapsamında açık kaynak olarak şu adreste yayınlanmaktadır: https://github.com/phishdestroy arşivlenmiş 2026-09-11 ↗;\n\nYöntem, her bir kaynak türünün ağırlığı ve sınırlamaları da dahil olmak üzere, sevk belgesinin Ek A, Bölüm A’da belirtilmiştir;16D;\n\nKoalisyon hiçbir bağış kabul etmemektedir ve bu tutumunu şu adresten duyurmuştur: 2018.\n\n3.2 Yayınlanmayan tek materyal, yasal olarak ya da güvenli bir şekilde yayınlanamayan materyaldir: mağdurların ve üçüncü şahısların kişisel verileri ile bir kaynağın misillemeye maruz kalmasına yol açabilecek bilgiler. Bu materyal, yetkililere gizlilik içinde sunulur ve delil listelerinde belirtilir.\n\n3.3 Koalisyon, başkalarının davranışlarının incelenmesini talep ettiği aynı şartlar altında kendi davranışlarının da incelenmesini talep etmekte ve veri imhası konusunda bir talimat alınması da dahil olmak üzere, veri işleme uygulamalarını ilgili makamlara gönüllü olarak sunmuştur.\n\n4. Delil paketinin bütünlüğü\n\n4.1 Ekler, başvuruyla birlikte sunulur veya belirtilmiş olması halinde, güvenli bir kanal aracılığıyla talep üzerine sağlanır. Bu ekler halka açık bir adreste yayınlanmaz ve böyle bir adresin varlığı da çıkarılmamalıdır: bu tür materyaller doğrudan yetkililere sunulur.\n\n4.2 Her teslimata, sağlanan her dosya için bir SHA-256 özetini içeren bir SHA256SUMS dosyası ve ayrıca SHA256SUMS.asc adresinden alınmış bağımsız bir OpenPGP imzası eşlik etmektedir.\n\n4.3 İmza anahtarı şu adreste yayınlanmıştır: https://phishdestroy.io/.well-known/pgp-key.txt ve keys.openpgp.org adresinde. Bu kümedeki her gönderinin antetinde bu sitenin parmak izi yer almaktadır.\n\n4.4 Herhangi bir alıcı, elindeki dosyanın gönderilen dosya ile aynı olduğunu ve üzerinde herhangi bir değişiklik yapılmadığını istediği zaman doğrulayabilir:\n\ngpg --verify SHA256SUMS.asc SHA256SUMS\n\nsha256sum -c SHA256SUMS\n\n4.5 Bunun amacı formalite değildir. Bunun amacı, herhangi bir delilin doğruluğu veya bütünlüğü ileride tartışma konusu olursa, bu sorunun tartışma yoluyla değil, hesaplama yoluyla çözülebilmesidir.\n\n5. Kayıt sırasında — feragatnamenin neden sadece cömert bir jest değil, işlevsel bir unsur olduğu\n\n5.1 Yetkili makamlar, Koalisyon’un yayınladığı araştırma raporlarıyla karşılaşabilir ve bunları sert, karşıt bir üslupta ve zaman zaman alaycı bulabilir. Bu izlenim doğrudur. Koalisyon kasıtlı olarak bu şekilde yazmaktadır ve bunun için özür dilememektedir.\n\n5.2 AYRICA, BUNUN DÜZENLEME VEYA YARGI SÜRECİ İÇİN UYGUN OLMAYAN BİR ÜSLUP OLDUĞUNU DA KABUL ETMEKTEDİR. Ciddi bir konu, bir kampanya üslubuyla ele alınmamalıdır. Bir makama sunulan bulgular, sınırlılıkları da kabul edilerek açık ve net bir şekilde ifade edilmeli ve okuyucunun içeriğe ulaşmadan önce üslubu göz ardı etmesini gerektirmemelidir.\n\n5.3 İŞTE TAM DA BU NEDENLE KOALİSYON YAZARLIK HAKKINDAN VAZGEÇİYOR. 1 bölümündeki feragat beyanı, metnin kayıt defterinden ayrılmasını sağlayan mekanizmadır: yetkili makam, yararlı olan kısımları alabilir, bunları kendi üslubuyla yeniden ifade edebilir ve Koalisyon’un adıyla birlikte Koalisyon’un üslubuna ait her kelimeyi bir kenara atabilir. Böylece hiçbir şey kaybedilmez ve Koalisyon da bunu tercih eder.\n\n5.4 KOALİSYON AYRICA, KAYIT SİSTEMİNİN YÖNTEMLE KARIŞTIRILMAMASINI DA TALEP EDİYOR. Yayınlanan metnin üslubu mücadeleci olsa da, altında yatan uygulama dikkatsiz değildir. Bu başvurunun tamamında, çıkarımlar gözlemlerden ayrılmıştır; tanıklıklar tanıklık olarak belirtilmiştir; kaynaklar değerlendirilmiş ve zayıf yönleri belirtilmiştir; rakamlar sınırlamalarıyla birlikte sunulmuştur; Koalisyonun kanıtlayamadığı noktalar ise iddia olarak değil, yetkili makamlara yöneltilen sorular olarak ifade edilmiştir. Kanıtlar Koalisyonun kendi tutumuna aykırı olduğunda, Koalisyon bunu açıkça belirtmiştir — bkz. Ek A, paragraf 7, ve paralel başvurunun B bölümü.0\n\n5.5 KOALİSYON, TARZININ VE MALİ DURUMUNUN ARASINDAKİ BAĞLANTİYI AÇIKLIYOR; ÇÜNKÜ İKİSİ BİRBİRİNDEN AYRIŞTIRILAMAZ. Koalisyon kimseden para almaz — ne bağış, ne ödül, ne müşteri, ne de sponsor. Bu reddi, açık sözlülüğü mümkün kılan şeydir: Koruması gereken bir geliri olan bir kuruluş, kendisine bağımlı olduğu partiler hakkında söylediklerini yumuşatmak zorundadır. Koruyacak hiçbir şeyi olmayan Koalisyon’un yumuşatacak hiçbir şeyi yoktur.\n\nBu aynı zamanda Koalisyonun varlığını sürdürmesinin nedenidir. Başka bir itici güç yoktur. Bu iş, yapıldığı için yapılır; onu yapanlar durduğunda iş de durur.\n\n5.6 Yetkili makamın bunların hiçbirini kabul etmesi gerekmez. Bu, Koalisyon’un kamuoyuna yönelik çalışmalarının üslubunun, şu anda önünde bulunan dosya konusunda gösterilen özenin bir göstergesi olarak algılanmaması için belirtilmiştir.\n\n6. Koalisyonun kendi ifadesiyle sunduğu hizmetler\n\nBilgi, araştırma ve gözlem.\n\nKoalisyonun ortaya koyma yetkisi bulunmayan hiçbir husus, bir bulgu olarak ileri sürülmemektedir. Bir hususun çıkarım yoluyla belirlendiği durumlarda, sevk belgesinde bu açıkça belirtilmektedir. Bir hususun tanık ifadesine dayandığı durumlarda, sevk belgesinde bu ifadenin kime ait olduğu ve hangi sınırlamaların geçerli olduğu belirtilmektedir. Koalisyonun bir soruya cevap veremediği durumlarda, bu durum da belirtilmekte ve soruyu kimlerin cevaplayabileceği açıklanmaktadır.\n\nKoalisyon, ne kendisi ne de herhangi bir birey adına herhangi bir telafi, ödeme, kabul ya dValve'da bir sonuç talep etmemektedir. Yalnızca, sevk belgesinde belirtilen soruların, cevap vermeyi zorunlu kılma yetkisine sahip bir kurum tarafından Corporation'a yöneltilmesini istemektedir.\n\nSon notBu işi sürdüren kişiye\n\nBu belgeleri olması gereken yere ulaştıran herkese teşekkür etmek istiyoruz. Muhtemelen bu iş bir çırpıda hallolmayacak. Valve’in bol parası var ve Taylor Wessing saatlik ücret alıyor — bu ikili, tam da sizin gibi insanların bitiş çizgisine ulaşamadan pes etmelerini sağlamak için özel olarak tasarlanmış.\n\nNe yaptığımızı biliyoruz. Kimler hakkında yazdığımızı biliyoruz. Bizi Valve yarattı — onları nasıl anlamayalım ki?\n\nPhishDestroy Valve ile herhangi bir çatışma söz konusu değildir. Karşılaştığımız o ölçekteki tek dolandırıcı çetesini engelledik — Valve ile kavga aramıyorduk. Sadece her yolun onlara çıktığı ortaya çıktı. Çatışma değil. Sadece ağ yapısı.\n\nValve PhishDestroy meselesini çözemeyiz çünkü çözülecek bir şey yok. Aramızda hiçbir ilişki yok. Onların zenginleşme planları ve aşırı kârlarına dair veriler büyük ölçüde kamuya açık — bunu görmek için sadece yeterince zaman ayırmanız gerekiyordu. Bunu bir başarı ansiklopedisi olarak düşünün: “Rus hackerların ücretsiz oyunlarımızı (zaten korsanlamayacakları ücretli olanları) korsanlamaması için yaptırımlara nasıl uymayacağımız.” Ne demek istediğimi anladınız.\n\nYazarlık kavramına ihtiyacımız yok.\n\nKaynak gösterilmesine gerek yok.\n\nKazanmamıza gerek yok.\n\nValve’a bu sevk belgesinde zaten yer alan soruları sorabilecek ve yanıt talep etme yetkisine sahip, gerçek yetkiye sahip birine ihtiyacımız var.\n\nHepsi bu kadar. İsteğimizin tamamı bu.\n\nDosyalar şu adreste bulunacaktır:\n\nhttps://steamdestroy.eth/\n\nhttps://steamdestroy.eth.limo (şu anda çalışmıyor — gerektiğinde düzeltilecektir)\n\nŞu adreste olacağız:\n\nhttps://phishdestroy.eth.limo/ arşivlenmiş 2026-06-27 ↗\n\nhttps://phishdestroy.eth/\n\nİmzalı iki eser · telif hakları ve yayınlanmış metin\nİmzalı feragatnameNeler imzalandı ve neleri kapsıyor?\n\nAşağıda, haklar atama metni ve araştırma metni ayrı ayrı imzalanmış JSON nesneleri olarak yer almaktadır. Her bir bağımsız OpenPGP imzası, yanında adı geçen JSON nesnesinin tam baytlarını doğrular. Haklar beyanı izinleri verir; metin anlık görüntüsü ise yayınlanan materyali tanımlar ve içerir.\n\n1. Haklar beyanı — license-rights.json\n\nİmzalı nesne: tam license-rights.json 28 Eylül tarihli kamu hakları iznini içeren dosya 2026. Bu belge, dosya materyallerinin kaynak gösterme, bildirimde bulunma veya onay alma zorunluluğu olmaksızın kopyalanmasına, yayınlanmasına, düzenlenmesine, çevrilmesine, birleştirilmesine ve ticari amaçla kullanılmasına izin vermektedir. Bu imza, hak beyanının geçerliliğini teyit eder; her bir web sayfası veya PDF metninin geçerliliğini teyit etmez.\n\nİmzalanmış orijinal izin belgesi, değiştirilmeden korunur. Web sitesinde değişiklik yapılması, başka bir dosyanın yayınlanması veya sitenin çevrimdışı hale getirilmesi yoluyla mevcut izin geri alınamaz veya kapsamı daraltılamaz. Üçüncü taraflara ait materyallerin hakları korunur.\n\nHaklar beyanı JSON ↗ · license-rights.json'in imzası ↗ · license-rights.json’in SHA-256’i ↗\n\ngpg --verify license-rights.json.asc license-rights.json\nsha256sum -c license-rights.json.sha256\n2. Yayınlanan metin — dossier-text.json\n\nİmzalı nesne: tam dossier-text.json dosya. Bu dosya, dışa aktarılan sayfaların okunabilir metinlerini içerir. documents[].content.text, her sayfanın başlığı, dili, kaynak URL’si, kaynak HTML hash değeri, başlıkları ve kaynakları ile birlikte. Bu documents Liste, bu anlık görüntünün kapsadığı tam envanterdir; dil varyantları ayrı olarak listelenmiştir. Bu, sadece bir hash listesi değil, metin biçiminde bir yayındır.\n\nHer giriş, hafif sayfa PDF’sini dosya adı ve SHA-256 ile tanımlar. documents[].pdf. JSON dosyası ayrıca orijinal hak beyanını URL ve SHA-256, ile tanımlamaktadır; böylece yayınlanan metin, ilgili PDF dosyası ve geçerli hak feragatnamesi, tahminde bulunmaya gerek kalmadan birbirleriyle eşleştirilebilir. Bağlantı verilen harici veritabanları, orijinal görseller ve envanterde bulunmayan sayfalar bu metin anlık görüntüsüne dahil edilmemiştir.\n\nİmzalanmış tam metin JSON ↗ · dossier-text.json'in imzası ↗ · dossier-text.json’in SHA-256’i ↗\n\ngpg --verify dossier-text.json.asc dossier-text.json\nsha256sum -c dossier-text.json.sha256\n\nDosya ana sayfasında, PDF ve JSON düğmeleri araştırma paketini dışa aktarır. İç sayfalarda ise bu düğmeler, ilgili sayfayı yayınlandığı dilde dışa aktarır. Her sayfanın JSON dosyası ayrıca, kendi ayrı imzasını ve SHA-256 dosyasını içerir; bu dosya, dosyanın adında açıkça belirtilir. integrity nesne. İlgili PDF dosyasını doğrulamak için, dosyanın SHA-256 değerini hesaplayın ve bunu pdf.sha256 doğrulanmış JSON'daki değer. PDF, bu özet ile bağlanmıştır; PDF formatında bir dijital imza içermemektedir.\n\n3. Yazdırılabilir araştırma paketi — steam-dossier-{language}.content.json\n\nİmzalı nesne: dil özelinde tam JSON dosyası; buna, içinde yer alan bölüm metni de dahildir documents[].content.text, bölüm sayfa aralıkları, kaynak diller, hariç tutulan kaynakların listesi ve tam PDF özeti pdf.sha256. Beş ek kanıt arşivi çevrimiçi olarak bağlantılı kalır ve bir araya getirilmez. Yazar tarafından kaleme alınan araştırma metni korunur; görsel katalogların yerine kaynak bağlantıları eklenir.\n\nİngilizce JSON ↗ · OpenPGP'in müstakil imzası ↗ · SHA-256 özeti ↗\n\nAlmanca JSON ↗ · OpenPGP'in müstakil imzası ↗ · SHA-256 özeti ↗\n\ngpg --verify steam-dossier-en.content.json.asc steam-dossier-en.content.json\nsha256sum -c steam-dossier-en.content.json.sha256\n\nGenel doğrulama anahtarı ↗\n\nİmza parmak izi: 129F C7F3 9C40 C69D 2EF3 C329 BFCF 9E8D D295 EE01\n\ngpg --import pgp-key.txt\ngpg --fingerprint 129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01\n\nGörüntülenen parmak izinin yukarıdakiyle eşleşip eşleşmediğini kontrol edin, ardından imzayı tam JSON dosya adıyla karşılaştırarak doğrulayın. İmzalanmış bir JSON dosyasının düzenlenmesi, imzalanmış nesneyi değiştirir ve orijinal imzasını geçersiz kılar. Geçerli bir imza, yayınlanan baytları tanımlar; araştırma bulgularının bağımsız bir doğrulaması değildir.\n\nPhishDestroy — kamu soruşturması — tüm haklar insanlığa devredilmiştir\n\nOFAC bölgesi erişimi: yasak",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Lisans ve Yasal Uyarı — Kamu Malı Olarak Adanma"
          },
          {
            "level": 2,
            "id": null,
            "text": "Bölüm ILisans — asıl hukuki kısım, ama insani"
          },
          {
            "level": 3,
            "id": null,
            "text": "Gerçekten tek bir kural (evet, sadece bir tane)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Bölüm IIBu nedir ve neden var?"
          },
          {
            "level": 2,
            "id": null,
            "text": "Bölüm IIIValve’a açık mektup — cidden, şunu bir oku"
          },
          {
            "level": 3,
            "id": null,
            "text": "Anlaşma (açık teklif, avukata gerek yok)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Bölüm III-BMüttefik kaynaklar — özellikle Steam adresine yönelik bir not"
          },
          {
            "level": 2,
            "id": null,
            "text": "Bölüm IVPara, yasaklar, tüm bu sirk"
          },
          {
            "level": 2,
            "id": null,
            "text": "Bölüm VKötü amaçlı yazılım meselesi — evet, bundan bahsediyoruz"
          },
          {
            "level": 2,
            "id": null,
            "text": "BeyannameKullanım ve haklar konusunda"
          },
          {
            "level": 3,
            "id": null,
            "text": "1. Kullanımla ilgili herhangi bir koşul bulunmamaktadır"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. Bunun neden sadece bir nezaket meselesi olarak değil, pratik açıdan da önemli olduğu"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. Her şey zaten açık"
          },
          {
            "level": 3,
            "id": null,
            "text": "4. Delil paketinin bütünlüğü"
          },
          {
            "level": 3,
            "id": null,
            "text": "5. Kayıt sırasında — feragatnamenin neden sadece cömert bir jest değil, işlevsel bir unsur olduğu"
          },
          {
            "level": 3,
            "id": null,
            "text": "6. Koalisyonun kendi ifadesiyle sunduğu hizmetler"
          },
          {
            "level": 2,
            "id": null,
            "text": "Son notBu işi sürdüren kişiye"
          },
          {
            "level": 2,
            "id": null,
            "text": "İmzalı feragatnameNeler imzalandı ve neleri kapsıyor?"
          },
          {
            "level": 3,
            "id": null,
            "text": "1. Haklar beyanı — license-rights.json"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. Yayınlanan metin — dossier-text.json"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. Yazdırılabilir araştırma paketi — steam-dossier-{language}.content.json"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/tr/#briefing-heading",
          "https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "http://web.archive.org/web/20260821155801/https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "https://phishdestroy.io/steam_dossier/tr/investigation_part2.html#outsourcing-case",
          "https://phishdestroy.io/steam_dossier/tr/#theft-ledger",
          "https://steamid.uk/",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/groups/steambans",
          "https://steamcommunity.com/id/killahinstinct_",
          "https://phishdestroy.io/steam_dossier/tr/card_economy.html#governance",
          "https://phishdestroy.io/steam_dossier/tr/license_disclaimer.html",
          "https://github.com/phishdestroy",
          "http://web.archive.org/web/20260911040557/https://github.com/PhishDestroy",
          "https://phishdestroy.io/.well-known/pgp-key.txt",
          "https://steamdestroy.eth/",
          "https://steamdestroy.eth.limo/",
          "https://phishdestroy.eth.limo/",
          "http://web.archive.org/web/20260627040219/https://phishdestroy.eth.limo/",
          "https://phishdestroy.eth/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json.asc",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json.sha256",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json.sha256?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json.sha256?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json.sha256?v=print-20260928-v3"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/tr/license_disclaimer.content.json",
      "export_json_sha256": "4d78999d534cad3a84ed9fa6e8a699f540ce7f1c931ebd5d3d3358e1cdf5a4ac"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "tr/market_economics.html",
      "language": "tr",
      "title": "Tek altyapı, iki pazar — “Steam” Dosyası",
      "source_url": "https://phishdestroy.io/steam_dossier/tr/market_economics",
      "source_html_sha256": "8a1ed2dcc5ca5ec1bcb8b5dc0851795bd968f8628f9d08c1a80aeeffec3a2df4",
      "exported_at": "2026-09-29T00:20:52.763Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "market_economics.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/tr/market_economics.pdf?v=print-20260929-v5",
        "sha256": "cd9cbf312672f61e86ee29e897e5c7dfad974a0479cb52cddbd314b3054a8948",
        "bytes": 100112,
        "pages": 8
      },
      "integrity": {
        "signed_object": "market_economics.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "market_economics.content.json.asc",
        "digest_file": "market_economics.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify market_economics.content.json.asc market_economics.content.json",
          "sha256sum -c market_economics.content.json.sha256"
        ]
      },
      "content": {
        "text": "Ek VII · Piyasa Yapısı · 20 Eylül 2026\nPiyasa Ekonomisi — İki Ekonomi ve Listeleme Tavanı\n\nAltyapıları. İki ekonomi.\n\nBU BÖLÜMÜN KANITLADIĞI ŞEY\n\nBu bölümde, Valve’in $1,800’lık listeleme sınırı ve çekilemeyen cüzdan bakiyelerinin yol açtığı sistemik piyasa bölünmesi analiz edilmektedir. 38'da listelenen değer yaklaşık $1.28 milyar olan aktif harici skin borsalarını inceleyen araştırma, üst düzey ticaretin zorunlu olarak harici gölge platformlara kayarken, Steam'un temel ticaret ve kimlik doğrulama altyapısına bağlı kaldığını kanıtlamaktadır. Abone Sözleşmesi'nde ticari kullanım resmi olarak yasaklanmış olsa da, Valve yayınlanmış herhangi bir yaptırım kaydı olmaksızın bu iki kademeli ekonomiyi kolaylaştırmakta ve bundan gelir elde etmektedir.\n\n← Yönetici özetine geri dön\n\n38 aktif üçüncü taraf CS2 pazar yerleri ve ayrıca Steam’un kendi pazarı. Bu platformlardan herhangi birinde listelenen her bir skin, Steam’in envanterinden geçmeli ve API üzerinden takas edilmelidir. Valve’in kuralları, bu altyapının ticari amaçlarla kullanılmasını yasaklamaktadır. Yaklaşık $1.28 milyar tutarındaki üçüncü taraf listeleme değeri mevcut olmakla birlikte, kuralın uygulandığına dair hiçbir kamuya açık kayıt bulunamamıştır.\n\n$1.28B\nÜçüncü taraf tarafından belirlenen değer · 38 platformları\n53.2M\nGörüntülenen teklifler · 38 üçüncü taraf pazarları\n70.1K\nSteam anlık görüntüde listelenen öğeler\n41×\nÜçüncü taraflarca belirlenen değer ile Steam’in $31M değeri arasındaki karşılaştırma\nEn önemli bulgu\nTek altyapı. İki ekonomi.\n\nSteam ürünü, envanteri ve ticareti kontrol eder. Aşağıda belirtilen herhangi bir platformda satılan her bir skin, Steam’ın ticaret platformu API üzerinden geçmek zorundadır — bu, doğrudan gözlemlenebilen yapısal bir bağımlılıktır. Valve’in kendi Community Market’i, satışlarından bir komisyon almaktadır; bu komisyonun, üçüncü taraf ekosisteme fon sağladığı ya da bu ekosistemle bağlantılı olduğu burada netleştirilmemiştir.\n\nBu durumun soruşturma açısından önemi nedir?\n1\nValve’ın “Steam” Abonelik Sözleşmesi ticari amaçlı kullanımını yasaklar Steam altyapısının açık izin olmaksızın kullanımı. Aşağıdaki platformlar için kamuya açık kayıtlarda böyle bir izne rastlanmamıştır.\n2\nSteam yaklaşık $1.28B tutarındaki üçüncü taraf kayıtlı varlıkların kimlik doğrulamasını (OpenID), envanter durumunu ve işlem gerçekleştirilmesini yönetir. Valve’ın altyapısı olmadan hiçbir ürün transferi gerçekleşmez.\n3\nSteam’in kendi pazar yeri $31M listelenmiş — üçüncü taraf listeleme değerinin yaklaşık %1/41'si. $1,800'lik fiyat tavanı, bu sınırın üzerindeki satıcıların gözlemlenen fiyatlardan satış yapabilmek için platform dışına çıkmaları gerektiği anlamına gelir.\n4\n248 CS2 eşya kategorileri, her biri iki veya daha fazla pazar yeri tarafından bağımsız olarak fiyat tavanının üzerinde fiyatlandırılan ürünlerin, Steam adresinde gözlemlenen piyasa fiyatından satılamaması — ve bunların hiçbirinin o platformda listelenmemesi. $1,800'luk fiyat tavanı, üçüncü taraf operatörlerin karşıladığı talebi yaratmaktadır.\nSteam Topluluk Pazarı:31milyon dolarÜçüncü taraf tarafından belirlenen değer: $1,276M\n$1,276M · üçüncü taraflarca belirlenen değer — bunların tümü Steam'daki işlemlere bağlıdır API & OpenID\nSteam · $31M\n\nKaynak: PriceEmpire gerçek zamanlı kataloğu, 20 Eylül 2026. Listelenen değer = kaydedilmiş anlık görüntüdeki yuvarlatılmış listelenen değer kartlarının toplamı; Steam hariç. Satış hacmi değildir.\n\n38 aktif üçüncü taraf piyasaları · Her şey Steam altyapısına bağlıdır\nPlatform kaydı\n\nAşağıdaki platformlar, oturum açma işlemlerini Steam adresindeki OpenID üzerinden, işlemlerini ise Steam adresindeki Web API üzerinden gerçekleştiriyor. Gözlemlenen her bir openid.realm Steam’ın oturum açma akışından geçer; kayıt sistemi, belirli bir operatörün Valve’daki izne sahip olmadığını iddia etmek yerine, gözlemlenen kimlik doğrulama yollarını kaydeder.\n\n#\tPlatform\tListelenen değer\tGeçerli teklifler\tÜrünler\tÖlçek\n1\tUUSkins\t$133.8M\t3.4M\t30.9K\t\n\n2\tYouPin898\t$127.5M\t5.9M\t29.2K\t\n\n3\tBuff.163\t$104M\t3.5M\t35K\t\n\n4\tMoon.Market\t$100.3M\t2.9M\t20.9K\t\n\n5\tWhite.Market\t$89.6M\t3M\t20.6K\t\n\n6\tBuff.Market\t$86.7M\t1.3M\t33.4K\t\n\n7\tEcosteam\t$82.1M\t3.3M\t30.1K\t\n\n8\tCSFloat\t$67.8M\t2.4M\t27.8K\t\n\n9\tSkin.Land\t$67.4M\t2.2M\t34.6K\t\n\n10\tLIS-SKINS\t$67.4M\t2.2M\t34.6K\t\n\n11\tC5Game\t$54.6M\t4.6M\t29.6K\t\n\n12\tHaloSkins\t$46.6M\t4.4M\t29.3K\t\n\n13\tAvan.Market\t$43.3M\t809.5K\t22.2K\t\n\n14\tWaxpeer\t$40.1M\t1M\t27.3K\t\n\n15\tSteam (official)\t$31M\t32.2M\t70.1K\t\n\n16\tCS.MONEY\t$29M\t748.9K\t28K\t\n\n17\tMarket.CSGO\t$26.3M\t1.3M\t27.6K\t\n\n18\tCS.MONEY Bot\t$25.7M\t614K\t23.8K\t\n\n19\tSkinport\t$16.3M\t3.8M\t31.1K\t\n\n20\tSkinFlow\t$14.1M\t481.8K\t23.6K\t\n\n21\tDMarket\t$12.6M\t948.2K\t35.6K\t\n\n22\tSkins.com\t$11.5M\t83.2K\t15.8K\t\n\n23\tSkin.place\t$6.9M\t380.8K\t11.4K\t\n\n24\tSkinsMonkey\t$6M\t109.4K\t11.6K\t\n\n25\tSkinBaron\t$5M\t2.1M\t21.5K\t\n\n26\tRustTM\t$3M\t33.1K\t4.9K\t\n\n27\tPirateSwap\t$2M\t859.3K\t10.5K\t\n\n28\tMannco.Store\t$1.2M\t223.7K\t11K\t\n\n29\tSkinSwap\t$1.1M\t11.4K\t4K\t\n\n30\tTradeIt\t$967.1K\t29.1K\t11.7K\t\n\n31\tLootFarm\t$896.1K\t162.5K\t28.6K\t\n\n32\tRustskins\t$714.8K\t312.5K\t6.1K\t\n\n33\tBalticSkins\t$599.2K\t28.2K\t4.5K\t\n\n34\tExeSkins\t$442.9K\t2.6K\t1.4K\t\n\n35\tRapidSkins\t$230.9K\t11.6K\t2.3K\t\n\n36\tCS.Trade\t$203K\t19K\t16.7K\t\n\n37\tKrakatoa\t$11.1K\t115\t53\t\n\n38\tShadowPay\t—\t—\t—\t—\n39\t49skins\t—\t—\t—\t—\nSteam’nin $1,800 fiyat tavanı · beş pazara ilişkin özet · 23 Eylül 2026\nFiyat farkı ölçülebilir.\n\nSteam Community Market listelemelerini yaklaşık $1,800 ile sınırlandırır (bu rakam, $2,000, $, 2,070, $, 2,300 ve $2,500 olarak yeniden hesaplanmıştır) cs2sh-atlas.json ve her eşikte sabit kalır). Bu fiyatın üzerinde gözlemlenen ürünler Valve’in kendi pazar yeri üzerinden piyasa fiyatından satılamaz — ancak bunlar, nerede satılırsa satılsın yine de Steam’un stok ve sevkiyat sistemine bağlıdır. Tüm kataloğu fiyata göre gruplandırmak, sınırın nerede olduğunu ortaya koyuyor: Valve’un pazarında 95.3% üst sınırının altında fiyatlandırılan ürün kategorilerinden ve 1.9% onun üstündekilerin.\n\nBeş pazar yeri: Steam sınırının üzerindeki ürünler\n248\n\nEn ucuz satış fiyatı $1,800’yi aşan ürün kategorileri iki veya daha fazla pazar yeri, birbirinden bağımsız olarak, en az değerinde 18,394 adresinde listelenen kopyaları elinde bulundurarak $78.6M. Bunlardan, 100.0% — her biri — Steam sitesinde hiçbir şekilde listelenmemiştir.\n\nEklerin tam metni: kayıt defteri → · fiyat merdiveni atlası →\n\nÜst sınırın üzerindeki fiyat dağılımı\n$1,800–$5,000\n174\n$5,000–$10,000\n49\n$10,000–$25,000\n21\n$25,000–$50,000\n2\n$50,000+\n2\nEn popüler ürünler — beş satış platformunda doğrulanmış en ucuz satış fiyatı\n1Çıkartma | Titan (Holo) | Kat. '14$66,285\n2Etiket | iBUYPOWER (Holo) | Kat. '14$64,795\n3Çıkartma | Reason Gaming (Holo) | Kat. '14$42,899\n4★ Spor Eldivenleri | Çit Labirenti (FN)$26,812\n5Çıkartma | Team Dignitas (Holo) | Kat. '14$23,667\n6EMS Kategorisi: '14' Efsaneleri$22,879\n7★ Spor Eldivenleri | Pandora'nın Kutusu (FN)$21,643\n8EMS Kategorisi: '14' Yarışmacıları$21,010\n9Çıkartma | Vox Eminor (Holo) | Kat. '14$18,619\n10★ StatTrak™ Navaja Bıçağı | Mavi Çelik (FN)$18,064\n\nİstenen fiyatlar satış fiyatları değildir. Lisanslı cs2.sh anlık görüntüsü, 23 Eylül 2026. Her satır, en az iki piyasa tarafından bağımsız olarak üst sınırın üzerinde fiyatlandırılmıştır; tek raflı satış teklifleri ve bir ürünün en ucuz satış teklifinin üç katından fazla olan fiyat teklifleri hariç tutulmuştur. Notlandırma sistemi nasıl işliyor? →\n\nValve’ın ücretleri · lisanslı cs2.sh anlık görüntü · 23 Eylül 2026\nİlan edilen ücret 15%.’dir. Çoğu iş ilanı daha fazla ücret ödemektedir.\n\nValve satıcının gelirinden 5% Steam adresinde belirtilen bir ücret ve 10% adresinde belirtilen CS2 yayıncı ücreti keser — bilinen 15%. Her iki ücret de En az $0.01, dolayısıyla hiçbir satışta komisyon tutarı iki sentten az olamaz. Pazarın büyük bir kısmını oluşturan ucuz ve yüksek hacimli ürünlerde, yüzde oranı değil, bu alt sınır belirleyici kısıtlamadır. Biz, her bir 29,635 Steam'de gerçek zamanlı fiyat teklifi bulunan ürün türleri.\n\n77.7%\nSteam'daki canlı ilanların bir kısmı, 15% adresinde belirtilen ücretlerin üzerinde ücretlendirilen ürün türlerinde yer almaktadır.\n84.8%\nürünün türler gerçekten de ilan edilen ücret civarında ödeme yapın\n4,517\nilan edilen ücretten daha fazla ücretlendirilen ürün türleri\n$0.02\nfiyat ne olursa olsun, her satışta uygulanacak asgari ücret\nBu iki sayı birbirine zıt yönleri işaret ediyor ve her ikisi de doğru\n1\nSayılan ürün türüne göre, Valve’daki ücretler genel olarak ilan edildiği gibidir: 29,635 adresindeki fiyatlandırılmış türlerin 84.8% adresi üzerinden 15%. adresinde belirtilen fiyatlarla veya bu fiyatlara yakın bir tutarda ücretlendirilmektedir.\n2\nSayılan gerçek listeye göre, durum tam tersine döner: 18,682,244 24,038,911'dan 15%.'dan daha yüksek ücretlendirilen ürün türlerine ilişkin canlı listeler\n3\nHer ikisi de doğrudur, çünkü aşırı şarj edilmiş tipler şunlardır: ucuz, yüksek hacimli bunlar. 1,109 ürün türleri, çift ana oran; ve sadece bu türler bile 14,083,486 adresinde canlı ilanlar barındırmaktadır.\n4\nBu bir hesaplamadır, bir iddia değil. Asgari tutar, Valve’un kendi ücret belgelerinde açıklanmıştır. Yayınlanmayan şey ise şudur: pazarın ne kadarını gerçekten kapsadığı — ki yukarıdaki rakamlar da bunu ölçmektedir.\n15% gazetesinin manşet haberlerinin bir kısmı olarak tahsil edilen ücret\n200%+\n14,083,486\n100-200%\n1,028,438\n50-100%\n700,804\n30-50%\n317,031\n20-30%\n2,258,254\n17.6-20%\n294,231\n\nÇubuk uzunluğu, her bir aralıkta yer alan aktif ilan sayısını gösterir. “200%+” şeklinde bir aralık, alınan komisyonun satıcının gelirinin 15% adresinde belirtilen tutarın iki katından fazla olduğu anlamına gelir.\n\nÇözümlü örnek\n67%\n\nBir ilanda alıcı şunları öder: $0.03 çünkü satıcı şunları alır: $0.01 ve “Valve” şöyle diyor: $0.02 — iki adet bir sentlik asgari tutar. Alıcının ödediği tutarın payı olarak bu rakam 67%; satıcının elde ettiği gelirin payı olarak ise 200%.\n\nTam veri kümesi: cs2sh-steam-fee-census.json →\n\nAynı nesne, bahçenin içinde ve dışında\nSteam'dan alışveriş yapmak daha pahalıdır. Neredeyse her zaman.\n\nHem Steam’da hem de en az bir üçüncü taraf pazar yerinde fiyatlandırılmış her ürün için, Steam’daki en ucuz satış fiyatını, bu platform dışındaki en ucuz satış fiyatıyla karşılaştırdık. Genel olarak 28,700 ürünler açısından, Steam daha pahalı bir mekandır 86.4% çoğu zaman, medyan değeri +35.7%.\n\nFiyat aralığına göre Steam primlerinin medyan değeri\n0.50 doların altında\n+48.3%\n$0.50-2\n+36.5%\n$2-10\n+29.6%\n$10-50\n+28.6%\n$50-250\n+36.3%\n$250-1k\n+51.1%\n1,000 doların üzerinde\n+67.9%\n\nEğri U şeklindedir. Steam sitesinden satın almak en ucuz yoldur; $10–$50 iki ucunda bant ve en sevdiğim şey.\n\nNeden pahalı segment önemlidir?\n+67.9%\n\nYukarıda $1,000, Steam sitesindeki ilanların medyan fiyatı, 67.9% bu site dışındaki en ucuz tekliften daha pahalıdır — ve Steam sitesinde 1,040 bu tür ilanlar sadece bu kadar mevcuttur.\n\nYaklaşık $1,800'dan sonra karşılaştırma yapılamaz hale gelir, çünkü Valve kuralı bu tür listelemeleri tamamen yasaklamaktadır. Steam sitesinin kendi sınırının üzerindeki ürünlere ilişkin kapsamı şöyledir: 1.9%. Tüm sıralamaya bakın →\n\nTam veri kümesi: cs2sh-walled-garden-premium.json →\n\nBir prim, tek başına bir bulgu değildir: Steam anında teslimat sunar ve karşı taraf riski yoktur, ve alıcılar bunun karşılığında makul bir bedel ödeyebilir. Ölçülebilir olan şey, farkın büyüklüğü ve bu farkı aşan paranın geri çıkamayacağı gerçeğidir — bu da bir sonraki bölümün konusudur.\n\nPara girer, para çıkmaz\n128.1 milyon dolarlık tutar, geri alınamayacak siparişler için taahhüt edilmiştir.\n\nSteam'daki bir satın alma emri önceden finanse edilir: emir verildiği anda para alıcının cüzdanından çıkar. Steam cüzdan bakiyesi geri çekilemez — bu paralar yalnızca Steam adresinde harcanabilir. Takip edilen her bir varlığın alım defterindeki tüm fiyat seviyelerinin toplamı, bağlanmış ve çekilemeyen paranın toplamını verir.\n\n$128.1M\nSteam'daki alım emirlerini yerine getirmeye kararlıyız\n170.6M\nbeklemede olan bireysel fonlu alım emirleri\n$105.8M\nkarşılarındaki ilanların talep edilen değeri\n$15.9M\nValve’in alacağı pay, tüm ilanların istenen fiyattan satılması durumunda\nBu rakamın ne olduğu ve ne olmadığı\n1\nBu zaten yatırılmış gerçek para. Hesaplanan her dolar, bir cüzdandan çekilmiş olup, 31,253 sitesindeki çeşitli ürün türlerine ait açık siparişlere karşılık gelmektedir.\n2\nBu gelir değil ve bu, Valve şirketinin bilançosuna ilişkin bir iddia değildir. Halka açık hisselerin nerede tutulduğu ve kimin kayıtlarında yer aldığı burada belirtilmemiştir.\n3\nBu bir anlık görüntü, akış değil. Siparişler alıcı tarafından iptal edilebilir; bu durumda para cüzdana iade edilir — ancak yine de Steam adresinden çıkmaz.\n4\nMesele tek yönlü kapıdır. Para biriminin nakde çevrilemediği bir pazar yeri, çalınan envanterin dönüştürülmesinin sebebidir kapalı Steam üzerinde değil de.\n\nYöntem: İzlenen her alım emir defterinin her fiyat seviyesi, o seviyede bekleyen emirlerle çarpılmıştır. Tam veri kümesi: cs2sh-steam-locked-capital.json →\n\nGerçekleşen satışlar, talep edilen fiyatlar değil · tek bir pazar yeri · son 90 gün\nAslında30.9 milyon dolarlık bir işlem gerçekleşti — beş rafın en küçüğünde.\n\nTek bir yüksek fiyatlı satış, nadir bir el yapımı ürün ya da ucuz bir temel ürünün etiketle işaretlenmiş bir varyantı olabilir (örneğin, e.g. $30 fiyatındaki bir ürünün tek seferlik $9,772 fiyatında tamamlanmış bir satış). “Yüksek” terimi, ürünün normal fiyatını değil, tamamlanmış en yüksek işlemi ifade eder.\n\nBu sayfadaki diğer tüm rakamlar şunu ölçer: listelenen. Bu, neyin ölçüldüğünü gösterir satıldı. Skinport, kendi tamamlanmış işlemlerini yayınlamaktadır ve son 90 gün içinde bu işlemlerin toplamı 1,219,143 satışlar değeri $30,927,032, her biri ortalama25.37 dolar.\n\n1.22M\n90 gün içinde tamamlanan satışlar, tek bir pazar yeri\n$30.9M\naynı dönemdeki ciro\n$125M\nyıllıklandırılmış iş hacmi — bir alt sınır, bir tahmin değil\n~2%\nSkinport’ın, piyasa değeri bazında üst sınırın üzerindeki hisselerden aldığı pay\nCiro nereden geldi?\n1 doların altında\n0.5%\n$1-10\n5.8%\n$10-100\n22.2%\n$100-1k\n59.4%\n$1k-1.8k\n6.9%\nSteam'ın üst sınırının üzerinde\n5.3%\n\nÇubuğun uzunluğu ciroyu gösterir; rakam ise o kademenin toplam ciro içindeki payını ifade eder. 59.4% 100–$ 71,4371 k kademesinde hareket eden paranın bir kısmı, satışlarından elde edildi.\n\nValve’in şapkasının üstünde de satışlar devam ediyor\n492\n\nSteam’in fiyat sınırının üzerinde fiyatlandırılmış ürünlerin tamamlanan satışları, değeri $1,643,938, 76 ürün türleri genelinde — bu rafın yaklaşık 2%’sini barındıran bir pazar yerinde. Bu satışların hiçbiri Steam adresinde gerçekleşemezdi.\n\nTam veri kümesi: cs2sh-offsteam-90d-dynamics.json → · gerçekleşen en yüksek seviyeler →\n\nSkinport Burada takip edilen üçüncü taraf pazarlarından BİRİDİR ve Steam sınırının üzerindeki listeleme değeri ile bu beş pazar arasında en küçüğüdür (bu rafın yaklaşık 2%’si kadar). Buradaki tüm toplamlar,Steam dışındaki ekonominin bir alt sınırını temsil eder; bu ekonominin bir ölçüsü değildir. Steam verileri kullanılmamaktadır.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Piyasa Ekonomisi — İki Ekonomi ve Listeleme Tavanı"
          },
          {
            "level": 2,
            "id": null,
            "text": "Tek altyapı. İki ekonomi."
          },
          {
            "level": 2,
            "id": null,
            "text": "Platform kaydı"
          },
          {
            "level": 2,
            "id": null,
            "text": "Fiyat farkı ölçülebilir."
          },
          {
            "level": 3,
            "id": null,
            "text": "Beş pazar yeri: Steam sınırının üzerindeki ürünler"
          },
          {
            "level": 3,
            "id": null,
            "text": "Üst sınırın üzerindeki fiyat dağılımı"
          },
          {
            "level": 3,
            "id": null,
            "text": "En popüler ürünler — beş satış platformunda doğrulanmış en ucuz satış fiyatı"
          },
          {
            "level": 2,
            "id": null,
            "text": "İlan edilen ücret 15%.’dir. Çoğu iş ilanı daha fazla ücret ödemektedir."
          },
          {
            "level": 3,
            "id": null,
            "text": "15% gazetesinin manşet haberlerinin bir kısmı olarak tahsil edilen ücret"
          },
          {
            "level": 3,
            "id": null,
            "text": "Çözümlü örnek"
          },
          {
            "level": 2,
            "id": null,
            "text": "Steam'dan alışveriş yapmak daha pahalıdır. Neredeyse her zaman."
          },
          {
            "level": 3,
            "id": null,
            "text": "Fiyat aralığına göre Steam primlerinin medyan değeri"
          },
          {
            "level": 3,
            "id": null,
            "text": "Neden pahalı segment önemlidir?"
          },
          {
            "level": 2,
            "id": null,
            "text": "128.1 milyon dolarlık tutar, geri alınamayacak siparişler için taahhüt edilmiştir."
          },
          {
            "level": 2,
            "id": null,
            "text": "Aslında30.9 milyon dolarlık bir işlem gerçekleşti — beş rafın en küçüğünde."
          },
          {
            "level": 3,
            "id": null,
            "text": "Ciro nereden geldi?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve’in şapkasının üstünde de satışlar devam ediyor"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/tr/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/tr/elite_skins.html",
          "https://phishdestroy.io/steam_dossier/tr/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/tr/skin_atlas.html#grading",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-steam-fee-census.json",
          "https://phishdestroy.io/steam_dossier/tr/skin_atlas.html#cliff",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-walled-garden-premium.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-steam-locked-capital.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-offsteam-90d-dynamics.json",
          "https://phishdestroy.io/steam_dossier/tr/skin_atlas.html#highs"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/tr/market_economics.content.json",
      "export_json_sha256": "50ca239d682eac57a19e3829b885349b51dbe251e7cef8c977d29f9c0c2ecb19"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "tr/regulatory_act_print.html",
      "language": "tr",
      "title": "ADLİ DENETİM KANUNU: Valve Steam Web API Ekosistem ve Ticari Kullanım (Ref: VAL-REG-2026-09)",
      "source_url": "https://phishdestroy.io/steam_dossier/tr/regulatory_act_print",
      "source_html_sha256": "37e159cf4635c53dab3da195a15d64fbf570a93bd13477d4f4b527a6d61dd810",
      "exported_at": "2026-09-29T00:20:53.236Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "regulatory_act_print.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/tr/regulatory_act_print.pdf?v=print-20260929-v5",
        "sha256": "df4ae1403dd129c250db58c8de0dba63cee12e3544264000e95f759baa97d554",
        "bytes": 186727,
        "pages": 14
      },
      "integrity": {
        "signed_object": "regulatory_act_print.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "regulatory_act_print.content.json.asc",
        "digest_file": "regulatory_act_print.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify regulatory_act_print.content.json.asc regulatory_act_print.content.json",
          "sha256sum -c regulatory_act_print.content.json.sha256"
        ]
      },
      "content": {
        "text": "phishdestroy.io · Adli Araştırma Koalisyonu · Evrensel Kamu Kayıtları\nDOSYA: VAL-REG-2026-09-EVID\nKAYNAK: phishdestroy.io/steam_dossier/\nHAKLAR: TÜM HAKLAR İNSANLIĞA DEVREDİLMİŞTİR\nAdli Denetim Kanunu ve Düzenleyici Ek\nValve’daki Steam Ekosisteminde Sistematik Üçüncü Taraf API Sağlama, Otomatik Baypas Mimarisi ve Sözleşmeye Dayalı Yürürlük Dışı Uygulama\nEtki Alanı Veren Kuruluşphishdestroy.io\nHedef PlatformValve Steam / Steamworks\nBirincil Kimlik Doğrulama VektörüSteam OpenID 2.0 / Web API\nYasal İthafAll Rights to Humanity (CC0)\nBölüm I: İdari Bildirim ve Olgusal BulgularREF: MEMO-ÖZET-01\n\nBu belge, Valve Corporation’ın yayınlanmış ticari şartları, teknik kimlik doğrulama uç noktaları ve gözlemlenen üçüncü taraf ticari platformlar arasındaki operasyonel kesişim noktasını inceleyen resmi bir adli denetim raporudur. Denetim, pasif ve kimlik doğrulaması yapılmamış ağ gözlemi, RDAP kayıt doğrulaması ve halka açık Link Filter telemetri verileri kullanılarak gerçekleştirilmiştir.\n\nTemel Gerçekler: Ampirik gözlemler, Valve’un kamuya açık sözleşme beyanları ile üretim altyapısı arasında sistematik bir uyuşmazlık olduğunu ortaya koymaktadır. Steam Abone Sözleşmesi (SSA), yetkisiz ticari kullanımı (§ 2.G), otomatik bot/komut dosyası etkileşimini (§ 4.C) ve hesap devrini (§ 1.C) kesin olarak yasaklarken, Valve Corporation, milyarlarca dolarlık ikincil işlem hacmi yaratan en az 175 ticari kuruluşa canlı, programlı OpenID kimlik doğrulama ve envanter sorgulama altyapısı sağlamaya devam etmektedir.\n\n175\nDenetlenmiş Ticari İşletmeciler\n44\nAyrı Etki Alanına Sahip Kimlik Doğrulama Sunucuları\n26\nFiltre-Bölünmüş Proxy Çiftleri\n100%\nUygulanmayan SSA § 2.G / § 4.C\n0\nZorunlu Kimlik Doğrulama İptalleri\nUygulanabilir Sözleşmeye Dayalı ve Yasal Çerçeve\nSSA § 2.G\nTicari Kullanım Yasağı: Valve Corporation’dan önceden yazılı izin alınmadan İçerik ve Hizmetlerin ticari amaçlarla kullanılmasını açıkça yasaklar.\nSSA § 4.C\nOtomasyon Kısıtlaması: Steam’in hizmetleri ve piyasalarıyla etkileşime giren komut dosyaları, alım satım botları, makrolar veya insan kontrolü dışında çalışan sistemlerin kullanımı kesinlikle yasaktır.\nSSA § 1.C\nKişisel Kullanım Zorunluluğu: Hesapların kullanımını kişisel amaçlarla sınırlandırır; Steam kullanıcı hesaplarının satılmasını, kiralanmasını, devredilmesini veya takas edilmesini açıkça yasaklar.\nAB DSA (2022/2065)\nSistemik Risk Değerlendirmesi (34/35. maddeler): Çok Büyük Çevrimiçi Platformlar (VLOP’lar), otomatik kötüye kullanım ve yetkisiz ticari sömürüden kaynaklanan sistemik riskleri aktif olarak tespit etmeli, değerlendirmeli ve azaltmalıdır.\nBölüm II: Ek Defter A — Belgelenmiş Bağlantı Filtresi Bölünmüş Çiftleri (26 Yolları)REF: EX-SPLIT-LEDGER\n\nBölünmüş Etki Alanı Kaçışının Adli Analizi: Valve’ın Steam Bağlantı Filtreleme sistemi kapsamında (steamcommunity.com/linkfilter/?url=...), bir son kullanıcı, işaretlenmiş bir kumar veya karaborsa platformuna yönlendiren bir bağlantıya tıkladığında, Valve göze çarpan bir uyarı görüntüler (\"Bağlantı Engellendi! ... potansiyel olarak zararlı olarak işaretlendi\"26 ). Bununla birlikte, adli yol izleme çalışmaları, bir bölünmüş etki alanı mimarisi: Link Filter'da birincil ticari alan adı ENGELLENMİŞ olsa da, Valve'un OpenID yanıt uç noktasını barındıran ikincil alan adı TEMİZ olarak işaretlenmiştir. Valve'un OpenID sunucuları, bu proxy sunucularından gelen kimlik doğrulama isteklerini kesintisiz olarak kabul eder; böylece, oturum açma işlemlerini sürdürürken tüketici güvenliği uyarısını etkisiz hale getirir.\n\n#\tBirincil Ticari Alan Adı\tAna Filtre\tOpenID Kimlik Doğrulama Proxy Etki Alanı\tOtorite Filtresi\tRDAP Kayıtlı\tKayıt Esası\n01\trollbit.com\tBLOCKED\trbsnin.com\tCLEAN\t2026-09-18\tPASSIVE_CAPTURE\n02\tskin.club\tBLOCKED\tsc-auth.net\tCLEAN\t2019-04-02\tPASSIVE_CAPTURE\n03\thowl.gg\tBLOCKED\thowl.uno\tCLEAN\t2026-08-11\tPASSIVE_CAPTURE\n04\tduelbits.com\tBLOCKED\tswitchflips.com\tCLEAN\t2020-04-21\tPASSIVE_CAPTURE\n05\tcsgofast.com\tBLOCKED\tsteam-login.authtofast.com\tCLEAN\t2026-06-30\tPASSIVE_CAPTURE\n06\tfarmskins.com\tBLOCKED\tsteam.kobal.cc\tCLEAN\t2017-01-07\tPASSIVE_CAPTURE\n07\tcobaltlab.tech\tBLOCKED\tcobaltauth.com\tCLEAN\t2025-01-07\tPASSIVE_CAPTURE\n08\tcsgo.net\tBLOCKED\tcn2.easylot.net\tCLEAN\t2016-09-03\tPASSIVE_CAPTURE\n09\tggdrop.com\tBLOCKED\tggauth.com\tCLEAN\t2023-05-03\tPASSIVE_CAPTURE\n10\trustchance.com\tBLOCKED\thgfuihd.com\tCLEAN\t2019-01-27\tPASSIVE_CAPTURE\n11\tskin.fans\tBLOCKED\tauth.skinfans.com\tCLEAN\t2018-07-16\tPASSIVE_CAPTURE\n12\tskinport.com\tBLOCKED\tskinport.app\tCLEAN\t2020-06-20\tPASSIVE_CAPTURE\n13\tskins.cash\tBLOCKED\tskinscash.live\tCLEAN\t2019-12-05\tPASSIVE_CAPTURE\n14\ttf2hunt.com\tBLOCKED\trstspcl.com\tCLEAN\t2020-08-08\tPASSIVE_CAPTURE\n15\tdaddyskins.com\tBLOCKED\tgo-go-daddy.com\tCLEAN\t2019-01-26\tPASSIVE_CAPTURE\n16\tkey-drop.com\tBLOCKED\tkdauth.com\tCLEAN\t2026-05-13\tPASSIVE_CAPTURE\n17\tclash.gg\tBLOCKED\tclggauth.com\tCLEAN\t2024-09-16\tPASSIVE_CAPTURE\n18\tc5game.com\tBLOCKED\twww.imbastar.com\tCLEAN\t2016-02-27\tPASSIVE_CAPTURE\n19\tswap.gg\tBLOCKED\tswapauth.com\tCLEAN\t2018-10-06\tPASSIVE_CAPTURE\n20\tshadowpay.com\tBLOCKED\tthelogins.com\tCLEAN\t2018-01-22\tPASSIVE_CAPTURE\n21\tcsgocases.com\tBLOCKED\tlog-1n.com\tCLEAN\t2017-11-27\tPASSIVE_CAPTURE\n22\tcsgogem.com\tBLOCKED\tapi.csgem.com\tCLEAN\t2014-03-08\tPASSIVE_CAPTURE\n23\tgamdom.com\tBLOCKED\tlogin.gambldom.com\tCLEAN\t2017-09-24\tPASSIVE_CAPTURE\n24\t12cs.fail\tBLOCKED\tfail.games\tCLEAN\t2021-08-24\tPASSIVE_CAPTURE\n25\tskinsnipe.com\tBLOCKED\tpricing.tradeupspy.com\tCLEAN\t2020-03-11\tPASSIVE_CAPTURE\n26\tcsgobig.com\tBLOCKED\tletmeinbig.com\tCLEAN\t2023-01-20\tPASSIVE_CAPTURE\n\n* Not: 2026-09-19 ve 2026-09-21. adreslerindeki, kimlik doğrulaması yapılmamış Steam Bağlantı Filtresi uç noktalarına karşı gerçekleştirilen pasif denetimler. Ham HTTP yanıt gövdeleri ve SHA-256 özetleri, veri havuzu veri kümesinde (steam_tos_assets/linkfilter-2026-09-22.json) saklanmaktadır.\n\nBölüm III: Ek Defter B — 175’da Denetime Tabi Ticari Kuruluşların Kapsamlı SayımıREF: EX-175-MASTER-CENSUS\n\nAşağıdaki kayıt, denetim veritabanında aktif olarak doğrulanmış tüm 175 üçüncü taraf ticari platformlarının ayrıntılarını içerir. Her kayıtta kuruluş adı, birincil ticari alan adı, gözlemlenen Steam OpenID kimlik doğrulama yolu, faaliyet sınıflandırması, sözleşme ihlali eşlemeleri (SSA § 2.G, SSA § 4.C, SSA § 1.C) ve kaynak veri kümesinde kaydedilen eylem alanı belirtilmiştir. \"Tarihli kanıtlara bakınız\" etiketi, okuyucuyu destekleyici kayıtlara yönlendirir; bu, Valve'un herhangi bir işlem yapmadığını ortaya koymaz. Eylem alanının bulunmaması, \"belirlenemedi\" olarak raporlanır.\n\nSergi\tKuruluş Adı ve Ana Etki Alanı\tGözlemlenen Kimlik Doğrulama Yolu / Proxy\tSınıflandırma\tSözleşme İhlali\tValve Eylem\nEX-001\tCSGORoll\ncsgoroll.com\n\t\nwww.csgoroll.com\nDIRECT\n\tSkin Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-002\tCSGOEmpire\ncsgoempire.com\n\t\ncsgoempirelogin4.com\nSPLIT PROXY\n\tCasino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-003\tRollbit\nrollbit.com\n\t\nrbsnin.com\nSPLIT PROXY\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-004\t500 Casino\n500.casino\n\t\nfivezerozero.co\nSPLIT PROXY\n\tLicenced Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-005\tCSGOBig\ncsgobig.com\n\t\ncsgobig.com\nDIRECT\n\tRoulette/Slots\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-006\tCaseDrop\ncasedrop.com\n\t\ncasedrop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-007\tRustReaper\nrustreaper.com\n\t\nrustreaper.com\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-008\tBanditCamp\nbanditcamp.com\n\t\nbanditcamp.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-009\tSkinBox\nskinbox.com\n\t\nskinbox.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-010\tTastyDrop\ntastydrop.com\n\t\ntastydrop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-011\tCSGOPolygon\ncsgopolygon.gg\n\t\ncsgopolygon.gg\nDIRECT\n\tRoulette Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-012\tMagicDrop\nmagicdrop.ru\n\t\nmagicdrop.ru\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-013\tCSDice\ncsdice.com\n\t\ncsdice.com\nDIRECT\n\tDice Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-014\tRustly\nrustly.com\n\t\nrustly.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-015\tSkinOdds\nskinodds.com\n\t\nskinodds.com\nDIRECT\n\tUpgrader Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-016\tCSGOWin\ncsgowin.com\n\t\ncsgowin.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-017\tCSGORun\ncsgorun.net\n\t\ncsgorun.net\nDIRECT\n\tCrash Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-018\tOpenSkins\nopenskins.com\n\t\nopenskins.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-019\tRustBet\nrustbet.com\n\t\nrustbet.com\nDIRECT\n\tRust Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-020\tCSGOMagic\ncsgomagic.com\n\t\ncsgomagic.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-021\tCSGOBounty\ncsgobounty.com\n\t\ncsgobounty.com\nDIRECT\n\tUpgrader/Contract\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-022\tEZSkins\nezskins.com\n\t\nezskins.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-023\tRustCases\nrustcases.com\n\t\nrustcases.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-024\tCSGOReaper\ncsgoreaper.com\n\t\ncsgoreaper.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-025\tCSGOCases\ncsgocases.com\n\t\ncsgocases.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-026\tCSGO-Skins\ncsgo-skins.com\n\t\ncsgo-skins.com\nDIRECT\n\tCase Upgrader\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-027\tCSGONet\ncsgonet.com\n\t\ncsgonet.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-028\tWTFSkins\nwtfskins.com\n\t\nwtfskins.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-029\tCSGOFast\ncsgofast.com\n\t\nsteam-login.authtofast.com\nSPLIT PROXY\n\tRoulette Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-030\tDuelbits\nduelbits.com\n\t\nswitchflips.com\nSPLIT PROXY\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-031\tFlameCases\nflamecases.com\n\t\nflamecases.com\nDIRECT\n\tCase Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-032\tFarmskins\nfarmskins.com\n\t\nsteam.kobal.cc\nSPLIT PROXY\n\tCase Opener\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-033\tCSGOLuck\ncsgoluck.com\n\t\ncsgoluck.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-034\tGamedom\ngamedom.com\n\t\ngamedom.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-035\tSkin.Club\nskin.club\n\t\nsc-auth.net\nSPLIT PROXY\n\tCase Battles\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-036\tDaddySkins\ndaddyskins.com\n\t\ndaddyskins.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-037\tInsane.gg\ninsane.gg\n\t\napi.insane.gg\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-038\tRustix\nrustix.gg\n\t\nrustix.gg\nDIRECT\n\tRust Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-039\tSkins.Club\nskins.club\n\t\nskins.club\nDIRECT\n\tSkin Upgrade\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-040\tCSGOHouse\ncsgohouse.org\n\t\ncsgohouse.org\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-041\tSkinRave\nskinrave.net\n\t\nskinrave.net\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-042\tBloodyCase_GG\nbloodycase.gg\n\t\nbloodycase.gg\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-043\tCSGOClicker\ncsgoclicker.com\n\t\ncsgoclicker.com\nDIRECT\n\tClicker/Upgrade\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-044\tRustBet_GG\nrustbet.gg\n\t\nrustbet.gg\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-045\tCS_Drop\ncs-drop.com\n\t\ncs-drop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-046\tHellStore\nhellstore.net\n\t\nhellstore.net\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-047\tRustLoot\nrustloot.com\n\t\nrustloot.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-048\tCSGO_Case\ncsgo-case.com\n\t\ncsgo-case.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-049\tCS2Skin\ncs2skin.com\n\t\ncs2skin.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-050\tJuice_GG\njuice.gg\n\t\nletmeinjuice.com\nSPLIT PROXY\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-051\tGGDrop\nggdrop.com\n\t\nggauth.com\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-052\tCSGOGem\ncsgogem.com\n\t\ncsgogem.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-053\tRainbet\nrainbet.com\n\t\nservices.rainbet.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-054\tHowl_GG\nhowl.gg\n\t\nhowl.uno\nSPLIT PROXY\n\tSkins Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-055\tChicken_GG\nchicken.gg\n\t\nchicken.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-056\tCSGOCasino_GG\ncsgocasino.gg\n\t\napi.csgocasino.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-057\tHunt_GG\nhunt.gg\n\t\napi.hunt.gg\nDIRECT\n\tSkins Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-058\tCSBattle\ncsbattle.com\n\t\ncsbattle.com\nDIRECT\n\tCase Battles\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-059\tSkinRave_GG\nskinrave.gg\n\t\napi.skinrave.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-060\tCSDouble\ncsdouble.gg\n\t\ncsdouble.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-061\tRustChance\nrustchance.com\n\t\nhgfuihd.com\nSPLIT PROXY\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-062\tRustClash\nrustclash.com\n\t\nrustclash.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-063\tCobaltLab\ncobaltlab.tech\n\t\ncobaltauth.com\nSPLIT PROXY\n\tRust Automation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-064\tRaided_GG\nraided.gg\n\t\napi.raided.gg\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-065\tRustNeo\nrustneo.gg\n\t\nrustneo.gg\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-066\tSplits_GG\nsplits.gg\n\t\nsplits.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-067\tUpgrader_Pro\nupgrader.pro\n\t\nupgauth.space\nSPLIT PROXY\n\tSkin Upgrader\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-068\tSkinFans\nskin.fans\n\t\nauth.skinfans.com\nSPLIT PROXY\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-069\tHotPizza\nhotpizza.one\n\t\nhotpizza.one\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-070\tG4Skins\ng4skins.com\n\t\nauth.g4s.to\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-071\t12CS_Fail\n12cs.fail\n\t\n12cs.fail\nDIRECT\n\tCrash Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-072\tTF2Royal\ntf2royal.com\n\t\ntf2auth.com\nSPLIT PROXY\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-073\tTF2Easy\nwww.tf2easy.com\n\t\nwww.tf2easy.com\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-074\tTF2Hunt\ntf2hunt.com\n\t\nrstspcl.com\nSPLIT PROXY\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-075\tTF2Bet\ntf2.bet/coinflip\n\t\ntf2.bet\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-076\tTF2Blaze\ntf2blaze.com\n\t\ntf2blaze.com\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-077\tOpenStars_GG\nopenstars.gg\n\t\nopenstars.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-078\tShuffle_Com\nshuffle.com\n\t\nshuffle.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-079\tSkins.com\nskins.com\n\t\napi.skins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-080\tWhite.Market\nwhite.market\n\t\nwhite.market\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-081\tBuff.Market\nbuff.market\n\t\nbuff.market\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-082\tAvan.Market\navan.market\n\t\navan.market\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-083\tCS.MONEY\ncs.money\n\t\nauth.dota.trade\nSPLIT PROXY\n\tTrading Engine\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-084\tUUSkins\nuuskins.com\n\t\nuuskins.com\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-085\tYouPin898\nyoupin898.com\n\t\nyoupin898.com\nDIRECT\n\tMass Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-086\tMoon.Market\nmoon.market\n\t\nmoon.market\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-087\tCSFloat\ncsfloat.com\n\t\ncsgofloat.com\nSPLIT PROXY\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-088\tSkin.Land\nskin.land\n\t\nauth.skin.land\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-089\tC5Game\nc5game.com\n\t\nc5game.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-090\tHaloSkins\nhaloskins.com\n\t\nhaloskins.com\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-091\tBuff.163\nbuff.163.com\n\t\nbuff.163.com\nDIRECT\n\tCorporate Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-092\tWaxpeer\nwaxpeer.com\n\t\nwaxpeer.com\nDIRECT\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-093\tCS.MONEY Bot\ncs.money\n\t\nauth.dota.trade\nSPLIT PROXY\n\tBot Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-094\tMarket.CSGO\nmarket.csgo.com\n\t\ndota2.net\nSPLIT PROXY\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-095\tSkinport\nskinport.com\n\t\nskinport.app\nSPLIT PROXY\n\tRegulated Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-096\tSkinFlow\nskinflow.gg\n\t\napi.skinflow.gg\nDIRECT\n\tMarketplace/Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-097\tDMarket\ndmarket.com\n\t\ndmarket.com\nDIRECT\n\tUS Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-098\tSkin.place\nskin.place\n\t\napi.skin.place\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-099\tSkinsMonkey\nskinsmonkey.com\n\t\nskinsmonkey.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-100\tSkinBaron\nskinbaron.de\n\t\nskinbaron.com\nSPLIT PROXY\n\tCorporate Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-101\tSteam\nsteamcommunity.com/market\n\t\nsteamcommunity.com/market\nDIRECT\n\tOfficial Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-102\tRustTM\nrust.tm\n\t\ndota2.net\nSPLIT PROXY\n\tRust Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-103\tPirateSwap\npirateswap.com\n\t\nlogin.pirateswap.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-104\tMannco.Store\nmannco.store\n\t\nmannco.store\nDIRECT\n\tTF2 Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-105\tSkinSwap\nskinswap.com\n\t\napi.skinswap.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-106\tLootFarm\nlootfarm.com\n\t\nlootfarm.com\nDIRECT\n\tTrading Platform\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-107\tRustskins\nrustskins.com\n\t\nrustskins.com\nDIRECT\n\tRust Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-108\tExeSkins\nexeskins.com\n\t\nexeskins.com\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-109\tBalticSkins\nbalticskins.com\n\t\nbalticskins.com\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-110\tCS.Trade\ncs.trade\n\t\ncs.trade\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-111\tRapidSkins\nrapidskins.com\n\t\napi.rapidskins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-112\tTradeIt\ntradeit.gg\n\t\nconnect-tradeit.com\nSPLIT PROXY\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-113\tKrakatoa\nkrakatoa.com\n\t\nkrakatoa.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-114\tShadowPay\nshadowpay.com\n\t\nshadowpay.com\nDIRECT\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-115\t49skins\n49skins.com\n\t\napi.49skins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-116\tSkinVault\nskinvault.gg\n\t\napi.skinvault.gg\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-117\tAim Market\naim.market\n\t\naim.market\nDIRECT\n\tSkins Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-118\tSkinout\nskinout.gg\n\t\nauth.skinout.gg\nDIRECT\n\tInstant Sell Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-119\tNTSkins\nntskins.com\n\t\nntskins.com\nDIRECT\n\tSkins Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-120\tIGXE\nigxe.cn\n\t\nigxe.cn\nDIRECT\n\tChinese Powerhouse\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-121\tSwap.gg\nswap.gg\n\t\nswap.gg\nDIRECT\n\tAutomated Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-122\tBitskins\nbitskins.com\n\t\nbitskins.com\nDIRECT\n\tCash-out Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-123\tGamerPay\ngamerpay.gg\n\t\ngamerpay.gg\nDIRECT\n\tP2P Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-124\tTF2Mart\ntf2mart.com\n\t\ntf2mart.com\nDIRECT\n\tTF2 Automation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-125\tSkinBid\nskinbid.com\n\t\nskinbid.com\nDIRECT\n\tSkin Auctions\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-126\tLootBear\nlootbear.com\n\t\nlootbear.com\nDIRECT\n\tSkin Rental\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-127\tBackpack.tf\nbackpack.tf\n\t\nbackpack.tf\nDIRECT\n\tTF2 Valuation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-128\tScrap.tf\nscrap.tf\n\t\nscrap.tf\nDIRECT\n\tTF2 Scrap Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-129\tMarketplace.tf\nmarketplace.tf\n\t\nmarketplace.tf\nDIRECT\n\tTF2 Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-130\tSTNTrading\nstntrading.eu\n\t\nstntrading.eu\nDIRECT\n\tTF2 Botnet\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-131\tSkins.Cash\nskins.cash\n\t\nskinscash.live\nSPLIT PROXY\n\tInstant Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-132\tSkinWallet\nskinwallet.com\n\t\nskinwallet.com\nDIRECT\n\tInstant Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-133\tDota2Market\ndota2market.com\n\t\ndota2market.com\nDIRECT\n\tDota 2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-134\tCSGO.NET\ncsgo.net\n\t\ncn2.easylot.net\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-135\tCybershoke\ncybershoke.net\n\t\nauth.cybershoke.net\nDIRECT\n\tCommunity Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-136\tXPlay_GG\nxplay.gg\n\t\nxplay.gg\nDIRECT\n\tServer Network\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-137\tFastCup\nfastcup.net\n\t\napi.fastcup.net\nDIRECT\n\tMatchmaker Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-138\tEsportal\nesportal.com\n\t\nesportal.com\nDIRECT\n\tMatchmaking Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-139\tGamersClub\ngamersclub.com.br\n\t\ngamersclub.com.br\nDIRECT\n\tLATAM Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-140\tLeetify\nleetify.com\n\t\nleetify.com\nDIRECT\n\tSaaS Analytics\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-141\tScope_GG\nscope.gg\n\t\nscope.gg\nDIRECT\n\tSaaS Analytics\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-142\tTradeUpSpy\ntradeupspy.com\n\t\napi.tradeupspy.com\nDIRECT\n\tSaaS Tools\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-143\tEpidemic_GG\nepidemic.gg\n\t\nepidemic.gg\nDIRECT\n\tSaaS Tools\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-144\tCSDeals\ncs.deals\n\t\napi.cs.deals\nDIRECT\n\tMarketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-145\tPricempire\npricempire.com\n\t\npricempire.com\nDIRECT\n\tSaaS Price DB\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-146\tCS2Stash\ncs2stash.com\n\t\ncs2stash.com\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-147\tCSGOSkins\ncsgoskins.gg\n\t\ncsgoskins.gg\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-148\tSteamAnalyst\nsteamanalyst.com\n\t\nsteamanalyst.com\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-149\tSteamCardExchange\nsteamcardexchange.net\n\t\nsteamcardexchange.net\nDIRECT\n\tTrading Exchange\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-150\tDotaBuff\ndotabuff.com\n\t\ndotabuff.com\nDIRECT\n\tSaaS Tracker\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-151\tTracker_GG\ntracker.gg\n\t\ntracker.gg\nDIRECT\n\tSaaS Tracker\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-152\tFSB Market (an anonymized label; the original name is withheld here)\nFSB Market\n\t\nFSB Market\nDIRECT\n\tMass Blackmarket\tSSA § 2.G, SSA § 4.C, SSA § 1.C\tSee dated evidence\nEX-153\tFunPay\nfunpay.com\n\t\nfunpay.com\nDIRECT\n\tAccount Exchange\tSSA § 2.G, SSA § 4.C, SSA § 1.C\tSee dated evidence\nEX-154\tPlayerAuctions\nplayerauctions.com\n\t\nplayerauctions.com\nDIRECT\n\tGrey Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-155\tEldorado.gg\neldorado.gg\n\t\neldorado.gg\nDIRECT\n\tAccount Portal\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-156\tG2A\ng2a.com\n\t\ng2a.com\nDIRECT\n\tMass Key Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-157\tKinguin\nkinguin.net\n\t\nkinguin.net\nDIRECT\n\tMass Key Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-158\tG2G.com\ng2g.com\n\t\ng2g.com\nDIRECT\n\tVirtual Services\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-159\tPlayerup\nplayerup.com\n\t\nplayerup.com\nDIRECT\n\tAccount Broker\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-160\tZ2U.com\nz2u.com\n\t\nwww.z2u.com\nDIRECT\n\tReady-Account Hub\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-161\tSmurfHub\nsmurfhub.net\n\t\nsmurfhub.net\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-162\tSmurfAccounts\nsmurfaccounts.com\n\t\nsmurfaccounts.com\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-163\tBuyCSGORank\nbuycsgorank.com\n\t\nbuycsgorank.com\nDIRECT\n\tRank Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-164\tCSGOSmurfKings\ncsgosmurfkings.com\n\t\ncsgosmurfkings.com\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-165\tSmurfStore_Co\nsmurfstore.co\n\t\nsmurfstore.co\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-166\tSteamLvlUp\nsteamlvlup.com\n\t\nsteamlvlup.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-167\tSteamLevels\nsteamlevels.com\n\t\nsteamlevels.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-168\tLevelSteam\nlevelsteam.com\n\t\nlevelsteam.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-169\tSteamLevelU\nsteamlevelu.com\n\t\nsteamlevelu.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-170\tEloKing\neloking.com\n\t\neloking.com\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-171\tBoosteria\nboosteria.org\n\t\nboosteria.org\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-172\tOvergear\novergear.com\n\t\novergear.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-173\tBlazingBoost\nblazingboost.com\n\t\nblazingboost.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-174\tDota2Boost\ndota2boost.com\n\t\ndota2boost.com\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-175\tBuyBoost\nbuyboost.com\n\t\nbuyboost.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nBölüm IV: Teknik Mimari ve Kimlik Doğrulama MekanizmalarıREF: TEKNİK ANALİZ -01\n\n1. OpenID’de Etki Alanı Sahipliği Doğrulamasının Olmaması 2.0: Valve’ın OpenID 2.0 protokolünün uygulaması (https://steamcommunity.com/openid/login) şunu değerlendirir: openid.return_to ve openid.realm Geliştiricilerin önceden kayıt olması, kriptografik doğrulama veya alan adı sahipliği doğrulaması gerektirmeden parametreler. Herhangi bir ticari işletmeci, kullanıcıları Valve adresindeki oturum açma ekranına yönlendirebilir ve rastgele alan adlarına yönlendirilmiş, kriptografik olarak imzalanmış bir kimlik beyanı (64-bitlik SteamID’yi içeren) alabilir.\n\n2. Programatik Envanter Sorgulama ve API Anahtarının Kötüye Kullanımı: Kullanıcı kimlik doğrulaması OpenID aracılığıyla onaylandıktan sonra, operatörler genel ve iş ortağı Web API uç noktalarına sorgu gönderir (IEconItems_730/GetPlayerItems) envanter varlıklarını gerçek zamanlı olarak endekslemek için. Otomatikleştirilmiş ticaret ağları, eşler arası (P2P) ticaret tekliflerini sunmak, sorgulamak ve kabul etmek için programlı oturum belirteçleri kullanır; bu da SSA § 4.C’de yer alan insan dışı etkileşime ilişkin yasağı doğrudan ihlal etmektedir.\n\n3. Bağlantı Filtresi Asimetrisi: Tüketicilere yönelik alan adı uyarılarının, tam işlevsel kimlik doğrulama uç noktalarıyla bir arada bulunması, düzenleyici bir çelişki yaratmaktadır: Valve adresindeki güvenlik telemetri sistemi bu operatörleri “potansiyel olarak zararlı” olarak sınıflandırmaktadır; ancak Valve adresindeki kimlik doğrulama altyapısı, bu operatörlerin kullanıcı tabanının kimlik doğrulamasını sürdürmektedir.\n\nDelil Metodolojisi ve Delil Zinciri Beyanı\n\nBu belge, kimlik doğrulaması yapılmamış ağ yakalamaları, geçmiş RDAP kayıt defteri sorguları ve doğrulanmış kriptografik hash listelerinden oluşturulmuştur. Hiçbir kullanıcı oturum açma bilgisi, güvenlik ihlali testine tabi tutulmamış veya işlenmemiştir. Tüm bulgular, Eylül ayı itibarıyla gözlemlenebilir üretim ağı durumunu yansıtmaktadır 2026. Bu belge, adli, düzenleyici ve kamu soruşturmaları için hazırlanmış, tarafsız bir teknik delil niteliğindedir.\n\nÖZET: SHA-256, DOĞRULANMIŞ\nc507c9025f93da0aadaf395c4d8882f25973211c318ee8e9b6f18a5b3755e050\nARŞİV: AÇIK HUKUK KAYDI\nYAYINLAYAN VE İMZALAYAN: phishdestroy.io · Adli Araştırma Koalisyonu\nYASAL DURUM: TÜM HAKLAR İNSANLIĞA DEVREDİLMİŞTİR · CC0 EVRENSEL KAMU MALI",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Adli Denetim Kanunu ve Düzenleyici Ek"
          }
        ],
        "links": []
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/tr/regulatory_act_print.content.json",
      "export_json_sha256": "360a2dde72a07e7a543af9e501240e27be88aa0a84f5ef521dff109acfaf74df"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "tr/security_timeline.html",
      "language": "tr",
      "title": "Güvenlik Zaman Çizelgesi — “Steam” Dosyası",
      "source_url": "https://phishdestroy.io/steam_dossier/tr/security_timeline",
      "source_html_sha256": "f68dc1989c819741012e559471e9d64c6dd6d0dcf5145d391e8044689a5d9b9d",
      "exported_at": "2026-09-29T00:20:56.286Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "security_timeline.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/tr/security_timeline.pdf?v=print-20260929-v5",
        "sha256": "eb2be8ea6072fe014af97fdaebbb4a2be18e5130616cfa937f5c0a9d705d181d",
        "bytes": 97834,
        "pages": 7
      },
      "integrity": {
        "signed_object": "security_timeline.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "security_timeline.content.json.asc",
        "digest_file": "security_timeline.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify security_timeline.content.json.asc security_timeline.content.json",
          "sha256sum -c security_timeline.content.json.sha256"
        ]
      },
      "content": {
        "text": "GÜVENLİK KAYDISERGİ / “16” KATILIMÇILARI\n\n2018 — 2026\n\nGüvenlik Zaman Çizelgesi — 2018'dan 2026'a\n\nGüvenlik durumu değişti. Kayıtları takip edin.\n\nBU BÖLÜMÜN KANITLADIĞI ŞEY\n\nBu kronolojik kayıt, Steam platformunun işlem ve kimlik doğrulama yığınında sekiz yıl boyunca gerçekleştirilen güvenlik değişikliklerini yeniden ortaya koymaktadır. Kayıt, 2018 7-adresinde belirtilen günlük işlem bekletme uygulamasını, 2023 Web API adresinde belirtilen mobil onay mekanizmalarını ve 2026 adresinde belirtilen oturum jetonlarının kullanımdan kaldırılmasını, belgelenmiş atlatma teknikleri bağlamında takip etmektedir. Zaman çizelgesi, platform güncellemelerinin bilinen istismar vektörlerinin sürekli olarak gerisinde kaldığını, ancak ticari operatörler için yapısal avantajların korunduğunu ortaya koymaktadır.\n\n← Yönetici özetine geri dön\n\nTicaret kilitleri. Oturum açma denetimleri. API kısıtlamaları. Nelerin değiştiğine ve kaynakların gerçekte neyi ortaya koyduğuna dair tarihsel bir kayıt.\n\nZaman çizelgesini keşfedin ↓\nSEKİZ YIL. TEK ALBÜM.16incelenmesi gereken dönüm noktaları\n\nHer giriş, gönderildiği tarihi ve kaynağını korur. Doğrulama bilgisi de bunun yanında gösterilir.\n\nİNCELENMİŞ / 24 EYLÜL 2026\n10Doğrulanmış etkinlik ve tarih\n06Kısmen doğrulanmış\n00Kaynak uyuşmazlığı\n00Kaynak belirtilmelidir\nBu kaydı nasıl okumalı?\n\nDoğrulanmış etkinlik ve tarih: her ikisi de güvenilir bir birincil kaynakla desteklenmektedir. Kısmen doğrulanmış: İlgili bir değişiklik kaydedilmiştir, ancak tarih veya kapsam henüz netleşmemiştir. Kaynak uyuşmazlığı: Bağlantı verilen materyal, ileri sürülen iddiayı desteklemiyor. Kaynak belirtilmelidir: Bu incelemede, tarihlendirilmiş ve eşleşen hiçbir kaynak doğrulanmamıştır. Çözümlenmemiş bir kayıt, bir olayın gerçekleşmediğinin kanıtı değildir.\n\nÇözülmemiş kayıtlardaki tarihler, gönderim tarihleridir; doğrulanmış yayın tarihleri değildir. Orijinal soruşturma metni yeniden yazılmamıştır.\n\nKronoloji\n01 — 16\nKayıdı araKonuKanıtSipariş\n\n16 16'daki girişler · en yeniler önce\n\n202609-01Gönderim tarihi\nToplulukKısmen doğrulanmış\nGrup sohbetlerinde şüpheli mesaj uyarıları\n\n31 Ağustos'ta yayınlanan resmi bir beta duyurusu, bu özelliği doğruluyor. Verilen 1 Eylül kararlı sürüm tarihi için henüz ayrıntılı sürüm notu yayınlanmadı.\n\nSteam Müşteri Beta Sürümü — 31Ağustos ↗arşivlendi 2026-03-13 ↗\nOrijinal giriş ve gönderilen bağlantı\n\nŞüpheli Sohbetlerin Otomatik Olarak İşaretlenmesi\n\nGönderilen kaynak kodunu incele ↗\n202601-16Doğrulama tarihi\nAPIDoğrulanmış etkinlik ve tarih\nYayıncı Anahtarları için Ayrıntılı İzinler ve IP Beyaz Listesi (Valve duyurusu)\n\n16'da 2026, Valve adresinde resmi bir Steamworks duyurusu yayınlandı (\"YENİ: Web API Anahtarları için daha gelişmiş izinler ve denetimler\") geliştiricilerin Web API anahtarlarını ayrı gruplara ayırmalarına olanak tanıyan yeni ayrıntılı izin araçlarını doğrulayarak (Genel, Mikro Ödemeler, Ekonomi ve Satış Verileri), anahtarları belirli Uygulama Kimlikleriyle sınırlayın ve sunucu IP'leri için beyaz liste uygulamasını yürürlüğe koyun.\n\nGöz Kamaştırıcı Çifte Standart: Bu resmi duyuru, Valve adresinin ayrıntılı API izinleri ve IP kısıtlamaları için teknik altyapıyı tamamen geliştirmiş olduğunu ortaya koymaktadır, ancak bunları normal kullanıcı hesaplarından kasıtlı olarak esirgemektedir (steamcommunity.com/dev/apikey). API adresindeki sıradan kullanıcı anahtarları, IP beyaz listeleme özelliği bulunmayan, tek parça halinde ve “ya hep ya hiç” türünde kimlik bilgileri olarak kalmaya devam etmektedir; işte bu teknik eksiklik, milyonlarca dolarlık API adresindeki ticaret işlemlerini ele geçirme endüstrisinin ortaya çıkmasına olanak sağlamaktadır.\n\nValve Duyuru — YENİ: Web API Anahtarları için daha gelişmiş izinler ve denetimler (16 Ocak 2026) ↗· Belgeler: Steamworks Web API Kimlik Doğrulama ↗\nOrijinal giriş ve gönderilen bağlantı\n\nSteamworks Web API Ayrıntılı Kapsamlar\n\nValve’ın Resmi Steamworks Duyurusunu İnceleyin (493839547938902179) ↗\n202507-15Doğrulama tarihi\nTicaretDoğrulanmış etkinlik ve tarih\nCS2 işlemlerinde yedi günlük tersine dönüş penceresi oluşuyor\n\nValve’in tarihli duyurusunda, son yedi gün içindeki Counter-Strike eşya takaslarının geri alınacağı belirtildi. Bu önlem, hesap ele geçirme olaylarını azaltmak amacıyla tasarlanmış olsa da, üçüncü taraf ekonomik denetimler (CSMarketCap ↗) bir $104M (-25%) kapat 24 saat içinde piyasa değeri açısından, nakit işlemlerdeki aksaklık nedeniyle. Şu analizde belirtildiği üzere Skinvault ↗, bir ters dönüşün tetiklenmesi, hesapta otomatik olarak 30-günlük işlem kısıtlaması uygulanmasına neden olur. Yaz aylarında 2026, Valve, UTC saatine göre gece yarısı yapılan genel sıfırlamalardan, her bir işlem için ayrı ayrı dakika bazında zamanlayıcılara geçmiştir (Skin.land ↗).\n\nValve — 15 Temmuz 2025 duyurusu ↗· CSMarketCap Analizi ↗\nOrijinal giriş ve gönderilen bağlantı\n\nCS2 Ticaret Koruması / İptal Süresi\n\nGönderilen kaynak kodunu incele ↗\n202505-14Doğrulama tarihi\nKimlik DoğrulamaDoğrulanmış etkinlik ve tarih\nValve SMS sızıntılarıyla ilgili hesap güvenliği uyarısı yayınladı\n\nValve’in 14, adresinde yer alan 5 Mayıs tarihli resmi duyurusu (2025,), hesap güvenliği ve SMS tabanlı kimlik doğrulama yöntemlerini ele almaktadır. Duyuru, SMS sızıntılarına odaklanmakta ve Steam sistemlerinde herhangi bir güvenlik ihlali yaşanmadığını teyit etmekle birlikte, yayınlandığı tarihteki resmi güvenlik güncellemesi niteliğindedir.\n\nValve — Steam hesabınızın güvenliği hakkında bir not ↗\nOrijinal giriş ve gönderilen bağlantı\n\nHesap Güvenliği Duyurusu\n\nGönderilen kaynak kodunu incele ↗\n202410-02Doğrulama tarihi\nTicaretDoğrulanmış etkinlik ve tarih\nYeniden satış veya pazarlama işleminden yedi gün önce\n\nSürüm notları, Cephanelik, takas teklifleri ve Topluluk Pazarı dahil olmak üzere oyun içi mağazadan edinilen öğeleri kapsamaktadır. Belgelenen kapsam, yalnızca Cephanelik öğeleriyle sınırlı değildir.\n\nValve — 10/2/2024 Sürüm Notları ↗\nOrijinal giriş ve gönderilen bağlantı\n\nCS2 The Armory / 7-Günlük Bekletme\n\nGönderilen kaynak kodunu incele ↗\n202409-18Gönderim tarihi\nTicaretKısmen doğrulanmış\nYardım Sayfalarında yeni cihaz kısıtlamaları doğrulandı\n\nSteam’un resmi destek belgeleri, en az 7 gün boyunca yetkilendirilmemiş yeni bir cihazdan oturum açıldığında 7-günlük işlem kısıtlamasının uygulandığını doğrulamaktadır. Eylül 18, 2024, tarihli güncellemenin kesin yayın tarihi, değişiklik günlüğünde bir kilometre taşı olarak kaydedilmemiş olsa da, bu işlevsellik tam olarak belgelenmiştir.\n\nSteam Destek — İşlem ve Piyasa Kısıtlamaları ↗\nOrijinal giriş ve gönderilen bağlantı\n\nYeni Cihazda Oturum Açma İşlem Kısıtlaması\n\nGönderilen kaynak kodunu incele ↗\n202402-14Gönderim tarihi\nToplulukKısmen doğrulanmış\n2024 sürümünde isim değiştirme işleminin bekleme süresi uygulamaya konuldu\n\nTopluluk ve geliştirici kayıtları, 2024, adresinde Valve'un, hızlı kimlik sahtekarlığını önlemek amacıyla profil adı değişikliğinin hemen ardından duyurulmamış bir 2-to-4 saatlik işlem bekleme süresi uygulamasını devreye soktuğunu doğrulamaktadır. Valve bu kısıtlama ile ilgili herhangi bir resmi basın bülteni, istemci değişiklik günlüğü veya destek makalesi yayınlamadığından, Şubat ayında bildirilen 14 tarihi resmi bir doğrulamaya sahip değildir; Steam Workshop kılavuzu, resmi Valve belgeleri yerine dolaylı bir topluluk teyidi işlevi görmektedir.\n\nSteam Atölye Kılavuzu (dolaylı doğrulama) — İsim değişikliği kısıtlaması ayrıntıları ↗\nOrijinal giriş ve gönderilen bağlantı\n\nProfil Adı / Avatar Değişikliği Bekletme\n\nGönderilen kaynak kodunu incele ↗\n202312-04Doğrulama tarihi\nAPIDoğrulanmış etkinlik ve tarih\nAnahtar oluşturmak için mobil onay gereklidir\n\nWeb API anahtar oluşturma işlemi için zorunlu Steam Guard mobil onayının, üçüncü taraf geliştirici kütüphanelerinde belgelendiği üzere 2023, sonlarında devreye alındığı doğrulanmıştır. Aralık 4, 2023, tarihleri, geliştirici topluluğu içinde gözlemlenen uygulamaya geçirme dönemini temsil etmektedir.\n\nBakım sorumlusu belgeleri — Mart 2024 ↗arşivlenmiş 2026-09-24 ↗\nOrijinal giriş ve gönderilen bağlantı\n\nAPI’ın Anahtarları için Mobil Onay\n\nGönderilen kaynak kodunu incele ↗\n202310-24Doğrulama tarihi\nGeliştiriciDoğrulanmış etkinlik ve tarih\nOyun sürümlerinin canlıya alınmasını ayarlamak için zorunlu 2FA kuralı yürürlüğe giriyor\n\nValve’in 10 Ekim tarihli resmi Steamworks duyurusu (10, 2023,), 10 Ekim’den itibaren (24, 2023,) yayınlanmış bir uygulamanın varsayılan dalında bir derlemeyi canlıya geçiren her hesabın, bu değişikliği SMS yoluyla veya Steam Mobil Uygulaması aracılığıyla onaylaması gerektiğini teyit etmektedir. Bu değişiklik, SetAppBuildLive Web sayfasını (API) doğrudan güncellemiştir.\n\nSteamworks — Derlemeleri ve kullanıcıları yönetmeye yönelik güvenlik iyileştirmeleri ↗arşivlenmiş 2025-12-03 ↗\nOrijinal giriş ve gönderilen bağlantı\n\nOyun Sürüm Yayınları için SMS Tabanlı Çok Faktörlü Kimlik Doğrulama (MFA)\n\nGönderilen kaynak kodunu incele ↗\n202307-12Gönderim tarihi\nToplulukKısmen doğrulanmış\nTopluluk tarafından tespit edilen, biyografi içeriklerine ilişkin özel uyarılar\n\nSteam Temmuz ayından itibaren 2023 adresinde yer alan topluluk raporları, harici bağlantılar veya tetikleyici kelimeler içeren özel profil biyografilerinde otomatik içerik uyarılarının görüntülenmeye başladığını ortaya koymaktadır. 12, 2023, adresinde belirtilen gönderim tarihi, Steam adresindeki topluluk forumlarında kullanıcıların ilk bildirim dalgasıyla örtüşmektedir.\n\nSteam Topluluk Forumu — Biyografi İçeriği Uyarı Raporları ↗\nOrijinal giriş ve gönderilen bağlantı\n\nÖzel Biyografi İçeriği Uyarısı\n\nGönderilen kaynak kodunu incele ↗\n202301-25Gönderim tarihi\nToplulukKısmen doğrulanmış\nProfil bağlantısı filtreleme ve düzenleme bekleme süreleri etkin\n\nSteam’ın resmi destek belgeleri, özel biyografilerdeki bağlantıların filtrelendiğini ve uygunsuz isim veya avatar değişikliklerinin düzenleme yasaklarına yol açabileceğini doğrulamaktadır. 4-adresinde belirtilen bir saatlik bekleme süresinin 1 Ocak 25, 2023, tarihinde tam olarak devreye girmesi, bu durumun gözlemlenen başlangıç noktası olsa da, bağlantı filtreleme mekanizması, gönderilen yardım sayfasında tam olarak aktif durumdadır.\n\nSteam Destek — Profil Adı ve Profil Resmi Kısıtlamaları ↗\nOrijinal giriş ve gönderilen bağlantı\n\nProfil BAĞLANTISI KALDIRILDI / Bekleme Süresi\n\nGönderilen kaynak kodunu incele ↗\n202210-24Doğrulama tarihi\nKimlik DoğrulamaDoğrulanmış etkinlik ve tarih\nSteam Müşterinin OAuth yenileme ve erişim jetonlarına geçişi\n\nValve’ın Ekim ayındaki önemli istemci ve mobil uygulama güncellemeleri 2022, Steam kimlik doğrulama sistemini baştan aşağı yeniledi. Eski oturum çerezi yapısı, OAuth tabanlı erişim ve yenileme belirteçleriyle değiştirildi; ayrıca, aktif oturumların manuel olarak iptal edilebilmesi için aktif yetkili cihazların bir listesi eklenmiştir.\n\nValve — Steam Mobil Uygulama Güncellemesi ve Kimlik Doğrulama Sürecinde Yapılan Kapsamlı Yenileme ↗\nOrijinal giriş ve gönderilen bağlantı\n\nSteam Giriş Sürecinin Yeniden Düzenlenmesi / Çerezlerin Kısaltılması\n\nValve’in Duyurusunu İncele ↗\n202210-12Doğrulama tarihi\nKimlik DoğrulamaDoğrulanmış etkinlik ve tarih\nQR koduyla oturum açma ve yetkili cihaz yönetimi\n\nValve’ın Ekim ayında yaptığı “12” duyurusunda, QR koduyla oturum açma, oturum açma işlemlerinin onaylanması veya reddedilmesi ve hesap erişimini iptal edebilecek bir cihaz listesi anlatılmaktadır.\n\nValve — Güncellenmiş “Steam” mobil uygulaması artık kullanıma sunuldu ↗\nOrijinal giriş ve gönderilen bağlantı\n\nSteam Mobil Uygulama 3.0 / QR ile Giriş\n\nGönderilen kaynak kodunu incele ↗\n202205-10Gönderim tarihi\nAPIKısmen doğrulanmış\nAPI'in herkese açık listesinden işlem iptal uç noktaları kaldırıldı\n\nGeliştirici kayıtları, Mayıs ayında 2022, Valve adresinde IEconService/CancelTradeOffer ve DeclineTradeOffer gibi ticaret yönetimi uç noktalarının Web API adresinden sessizce kaldırıldığını doğrulamaktadır (node-steam-tradeoffer-manager #325 başlığında belgelenmiştir). Bu yöntemler özel istemci protokollerinde hâlâ işlevsel olsa da, 10, 2022, tarihli güncelleme, dolandırıcılık panelleriyle mücadele amacıyla bu yöntemlerin genel Web API’lerinden kaldırıldığını göstermektedir.\n\nGeliştirici Tartışması — Sorun #325 (CancelTradeOffer kaldırıldı) ↗· Steamworks Web API — IEconService Belgeleri ↗\nOrijinal giriş ve gönderilen bağlantı\n\nTicaret İptal Son Noktalarının Kaldırılması\n\nnode-steam-tradeoffer-manager sorununu incele: Sorun #325 ↗\n202005-25Doğrulama tarihi\nTicaretDoğrulanmış etkinlik ve tarih\nDota2’daki eşyalara yedi günlük takas bekleme süresi getirildi\n\n25, tarihinde 2020,, Uluslararası 10 Battle Pass’ın piyasaya sürülmesiyle birlikte (blog.dota2.com/2020/05/the-international-10-battle-pass/), Valve, 2018 Counter-Strike politikasına uygun olarak Dota 2 eşyaları için 7-günlük takas kilidi uyguladı. Bu kısıtlama, takas edilen tüm eşyalar ve Pazar’dan yapılan satın alımlar için geçerlidir.\n\nDota2 Topluluğu — Takas Kilidi ve TI10 İstemci Güncellemesi ↗\nOrijinal giriş ve gönderilen bağlantı\n\nDota 2 / 7-Günlük İşlem Kilidi\n\nGönderilen kaynak kodunu incele ↗\n201803-29Doğrulama tarihi\nTicaretDoğrulanmış etkinlik ve tarih\nTakas edilen CS:GO eşyaları için yedi günlük bekleme süresi uygulanır\n\nResmi sürüm notları, tarihi ve kısıtlamayı doğrulamaktadır. Verilen URL, 2013 adresindeki bir harita güncellemesine yönlendiriyordu; buna karşılık gelen sürüm notu URL’si ise 20309. ile bitmektedir.\n\nValve — 3/29/2018 Sürüm Notları ↗\nOrijinal giriş ve gönderilen bağlantı\n\nCS:GO / 7-Günlük İşlem Kilidi\n\nGönderilen kaynak kodunu incele ↗ arşivlenmiş 2025-02-26 ↗\n\nKanıtları takip edin. Kaynağı inceleyin.\n\nSoruşturmaya geri dön ↗",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Güvenlik Zaman Çizelgesi — 2018'dan 2026'a"
          },
          {
            "level": 2,
            "id": null,
            "text": "Kronoloji"
          },
          {
            "level": 2,
            "id": null,
            "text": "Grup sohbetlerinde şüpheli mesaj uyarıları"
          },
          {
            "level": 2,
            "id": null,
            "text": "Yayıncı Anahtarları için Ayrıntılı İzinler ve IP Beyaz Listesi (Valve duyurusu)"
          },
          {
            "level": 2,
            "id": null,
            "text": "CS2 işlemlerinde yedi günlük tersine dönüş penceresi oluşuyor"
          },
          {
            "level": 2,
            "id": null,
            "text": "Valve SMS sızıntılarıyla ilgili hesap güvenliği uyarısı yayınladı"
          },
          {
            "level": 2,
            "id": null,
            "text": "Yeniden satış veya pazarlama işleminden yedi gün önce"
          },
          {
            "level": 2,
            "id": null,
            "text": "Yardım Sayfalarında yeni cihaz kısıtlamaları doğrulandı"
          },
          {
            "level": 2,
            "id": null,
            "text": "2024 sürümünde isim değiştirme işleminin bekleme süresi uygulamaya konuldu"
          },
          {
            "level": 2,
            "id": null,
            "text": "Anahtar oluşturmak için mobil onay gereklidir"
          },
          {
            "level": 2,
            "id": null,
            "text": "Oyun sürümlerinin canlıya alınmasını ayarlamak için zorunlu 2FA kuralı yürürlüğe giriyor"
          },
          {
            "level": 2,
            "id": null,
            "text": "Topluluk tarafından tespit edilen, biyografi içeriklerine ilişkin özel uyarılar"
          },
          {
            "level": 2,
            "id": null,
            "text": "Profil bağlantısı filtreleme ve düzenleme bekleme süreleri etkin"
          },
          {
            "level": 2,
            "id": null,
            "text": "Steam Müşterinin OAuth yenileme ve erişim jetonlarına geçişi"
          },
          {
            "level": 2,
            "id": null,
            "text": "QR koduyla oturum açma ve yetkili cihaz yönetimi"
          },
          {
            "level": 2,
            "id": null,
            "text": "API'in herkese açık listesinden işlem iptal uç noktaları kaldırıldı"
          },
          {
            "level": 2,
            "id": null,
            "text": "Dota2’daki eşyalara yedi günlük takas bekleme süresi getirildi"
          },
          {
            "level": 2,
            "id": null,
            "text": "Takas edilen CS:GO eşyaları için yedi günlük bekleme süresi uygulanır"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/tr/#briefing-heading",
          "https://steamcommunity.com/groups/SteamClientBeta?l=english",
          "http://web.archive.org/web/20260313235409/https://steamcommunity.com/groups/SteamClientBeta?l=english",
          "https://store.steampowered.com/news/posts/?enddate=1788390000",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/493839547938902179",
          "https://partner.steamgames.com/doc/webapi_overview/auth",
          "https://csmarketcap.com/blog/market-insights/from-boom-to-bust-cs2s-trade-protection-impact",
          "https://skinvault.gg/blog/cs2-trade-protection-explained/",
          "https://skin.land/blog/steam-changes-cs2-trade-ban-logic-timing/",
          "https://store.steampowered.com/news/posts/?appids=730&amp;enddate=1753924057&amp;feed=steam_announce%2F1000",
          "https://help.steampowered.com/faqs/view/3041-A87A-E5F6-B6AC",
          "https://store.steampowered.com/news/posts/?enddate=1747349559",
          "https://steamcommunity.com/ogg/593110/announcements/detail/533224478739530146",
          "https://store.steampowered.com/news/posts/?appids=730&amp;enddate=1728000977&amp;feed=steam_community_announcements",
          "https://steamcommunity.com/games/CSGO/announcements/detail/4447966961421256740",
          "https://help.steampowered.com/faqs/view/7F77-9E92-31E0-6B8E",
          "https://steamcommunity.com/sharedfiles/filedetails/?id=2926756889",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "http://web.archive.org/web/20260924181824/https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "https://steamcommunity.com/dev/apikey",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3749866608167579206",
          "http://web.archive.org/web/20251203174259/https://steamcommunity.com/groups/steamworks/announcements/detail/3749866608167579206",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3734103130194459461",
          "https://steamcommunity.com/discussions/forum/1/3807266184852932971/",
          "https://help.steampowered.com/faqs/view/225C-C51E-B8F0-55B2",
          "https://store.steampowered.com/news/group/4/view/3314112260640237775",
          "https://store.steampowered.com/news/posts/?appgroupname=Keep+in+touch&amp;enddate=1666122699&amp;feed=steam_blog",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/issues/325",
          "https://partner.steamgames.com/doc/webapi/IEconService",
          "https://steamcommunity.com/app/570/announcements/",
          "https://blog.dota2.com/2020/05/trading-cooldown/",
          "https://blog.counter-strike.net/2018/03/20309/",
          "https://blog.counter-strike.net/index.php/2018/03/20308/",
          "http://web.archive.org/web/20250226114333/https://blog.counter-strike.net/index.php/2018/03/20308/",
          "https://phishdestroy.io/steam_dossier/tr/#vulnerability-profile"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/tr/security_timeline.content.json",
      "export_json_sha256": "6c3b65ed9ab3782e8c3afff0fa237fbf9d111b4182348a31b3ee413dda731f21"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "tr/skin_atlas.html",
      "language": "tr",
      "title": "Steam’in taşıyamadıklarının atlası — “Steam” Dosyası",
      "source_url": "https://phishdestroy.io/steam_dossier/tr/skin_atlas",
      "source_html_sha256": "5cf8cad94b8da91f9f1b8cb45b2f7ded089a6edb9a80760b6d97f8de07fc6fe0",
      "exported_at": "2026-09-29T00:21:03.043Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "gallery",
            "source": "https://phishdestroy.io/steam_dossier/tr/skin_atlas#gallery"
          }
        ],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "skin_atlas.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/tr/skin_atlas.pdf?v=print-20260929-v5",
        "sha256": "0e4ce13017984bdea54f795b0bca3c5a880d51d75d0fb77ad49c7f49597f8d0d",
        "bytes": 184842,
        "pages": 13
      },
      "integrity": {
        "signed_object": "skin_atlas.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "skin_atlas.content.json.asc",
        "digest_file": "skin_atlas.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify skin_atlas.content.json.asc skin_atlas.content.json",
          "sha256sum -c skin_atlas.content.json.sha256"
        ]
      },
      "content": {
        "text": "EK IV-B / FİYAT BASAMAKLARI / 2026-09-23\nCilt Fiyat Merdiveni Atlası — Likidite Uçurumu\n\nValve’in pazar durakları paranın kaynağı.\n\nBU BÖLÜMÜN KANITLADIĞI ŞEY\n\nBu görsel atlas, beş pazar yeri kataloğundaki 30,266 ürün kategorilerini analiz ederek, Valve’un listeleme eşiğinin üstünde ve altında kalan pazar kapsamını ölçmektedir.1,800 sınırının altında, Steam 95.3% aktif kategoriye ev sahipliği yapmaktadır; bu sınırın hemen üzerinde ise resmi kapsama alanı 1.9%'ye düşmektedir (doğrulanmış varlıklar üzerinden 0.0% kapsama alanı ile birlikte). Bu durum, Valve'in temel varlıkların saklanması üzerinde tam kontrolünü elinde tutarken, yüksek değerli işlemlerin keşfini dış platformlara devrettiği ani ve yapısal bir likidite uçurumunu göstermektedir.\n\n← Yönetici özetine geri dön\n\nBeş pazaryerinde güncel fiyatı bulunan her CS2 ürünü, en ucuz satış teklifi temel alınarak bir fiyat aralığına yerleştirildi ve her aralık tek bir kriter açısından değerlendirildi: Valve’un kendi Topluluk Pazarı’nın bu aralık içindeki payı ne kadar? Valve’un listeleme sınırının altında bu sorunun cevabı şudur: 95.3%. Bunun üstünde, cevap şudur: 1.9%. Düşüş kademeli değildir ve talebin azaldığı noktada gerçekleşmez — tam olarak yayınlanan kurala göre gerçekleşir. Bunlardan 248 İki veya daha fazla pazar yerinin fiyatlarını üst sınırın üzerine çıkardığı ürün kategorileri; 100.0% adresinde Steam listelemesi hiç bulunmamaktadır.\n\nUçuruma bakın ↓419'daki ürünlerin galerisini açınYöntem ve sınırlar\n30,266ölçülen ürün kategorileri\n95.3%Steam tarafından taşınan sermaye altındaki kalemlerin\n1.9%Steam tarafından satılan üst sınırın üzerindeki ürünler\n$78.6Mdoğrulanmış kümenin taban değeri\n01 / ölçüm\nUçurum, talebe göre değil, kurala göre oluşur\n\nAşağıdaki 30,266 ürün kategorilerinin her biri, kendi en ucuz BUFF163, CSFloat, Skinport, YouPin 898 ve C5Game platformlarında yapılan canlı sorgulamalarda, yalnızca bu platformlardan en az ikisinde listelenen ürünler dikkate alınır; dolayısıyla tek bir abartılı liste, bir grup üyesini uydurmaya yetmez. Üstteki tablo, Valve’un kendi pazarında hâlâ satılan her grubun payını göstermektedir.\n\nSteam Toplum Pazarı’nda satılan ürünlerin her bir fiyat aralığındaki payı\nüst kısım: buhar kapsamı · alt kısım: bant başına öğe sayısı, logaritmik ölçek\n0%\n25%\n50%\n75%\n100%\n100%\n96.9%\n95.9%\n97.3%\n91.1%\n76.8%\n14.5%\n2.9%\n1.5%\n0%\n0%\n0%\n4,632\n1¢–10¢\n7,152\n10¢–$1\n8,568\n$1–10\n5,941\n$10–100\n2,329\n$100–300\n1,292\n$300–1k\n193\n$1k–1.8k\n70\n$1.8k–3k\n67\n$3k–10k\n18\n$10k–30k\n3\n$30k–100k\n1\n$100k+\nitems\nlog\nVALVE’S LISTING CAP\nValve’ın listeleme üst sınırı düzeyinde veya altındasınırın üzerinde — Valve'un kuralları, bu tür listelemeleri yasaklamaktadırgrup içindeki ürün kategorileri\n\n“Kapsam”, verinin alındığı anda o kategori için Steam adresinde canlı bir sorgu bulunması anlamına gelir. Alt panel logaritmik olarak gösterilmiştir, çünkü katalogdaki fiyatlar büyük çoğunlukla çok düşüktür: doğrusal olarak okunması halinde, $300 üzerindeki tüm aralıklar temel çizgiye indirgenmiş olurdu.\n\nBu şeklin neyi dışladığı\n\nPahalı ürünler sadece popüler olmasaydı, fiyat yükseldikçe talep kademeli olarak azalırdı. Ancak durum böyle değil. Talep, 76.8% seviyesinde kalıyor; $300–$1k aralığında seyrediyor, ardından tavanın hemen altındaki aralıkta 14.5% seviyesine, hemen üstündeki aralıkta ise 2.9% seviyesine düşüyor. Talep etkisi, Valve tavanın nerede belirlendiğini bilmez. Bir kural bilir.\n\nFiyat aralığı\tÜrün kategorileri\tSteam'da canlı bir soru ile\tSteam kapsam\tSteam sitesinde listelenen kopyalar\n1¢–10¢\t4,632\t4,632\t100%\t8,223,227\n10¢–$1\t7,152\t6,931\t96.9%\t5,488,315\n$1–10\t8,568\t8,213\t95.9%\t3,939,538\n$10–100\t5,941\t5,780\t97.3%\t1,328,255\n$100–300\t2,329\t2,121\t91.1%\t364,466\n$300–1k\t1,292\t992\t76.8%\t187,504\n$1k–1.8k\t193\t28\t14.5%\t40,281\n$1.8k–3k\t70\t2\t2.9%\t9,592\n$3k–10k\t67\t1\t1.5%\t6,706\n$10k–30k\t18\t0\t0%\t1,366\n$30k–100k\t3\t0\t0%\t21\n$100k+\t1\t0\t0%\t2\n\nDesen ve aşama varyantları bu sıralamaya dahil edilmemiştir: Steam, mavi mücevher kademesini veya Ruby aşamasını ayrı bir pazar girişi olarak listelememektedir; dolayısıyla bunları hesaba katmak, Steam’un kapsama alanını olduğundan daha az gösterir. İki pazar yeri şartı dikkate alınmadan ölçüldüğünde, aynı sıralama 37,204 öğeleri üzerinden üst sınırın altında 79.1% ve üstünde 6.5% değerlerini vermektedir — bu, daha zayıf kanıtlara dayanan daha belirgin bir farktır ve bu nedenle alıntılanan rakam bu değildir.\n\n02 / kanıt temelli derecelendirme\nİstenen fiyat, fiyat değildir\n\nHerkes bir P2000’i tam on milyon yuan’a satışa çıkarabilir. Bu sayfadaki bir rakam herhangi bir amaçla kullanılmadan önce, söz konusu ürünün üst sınırın üzerinde kaç farklı satış platformu tarafından fiyatlandırıldığına ve bu fiyat tekliflerinin ortalamasının ne kadar sıkı bir aralıkta toplandığına göre derecelendirilir. Hem burada hem de bu dosyanın diğer bölümlerinde yalnızca A ve B dereceleri dikkate alınır.\n\nA  Üç veya daha fazla raf birbiriyle uyumludur\n\nÜç veya daha fazla satış platformu, söz konusu ürün için üst sınırın üzerinde fiyat teklifi vermiş ve bu fiyatların medyanı, en ucuz fiyattan 25% aralığında yer almaktadır. 197 kategoriler, 18,218 kopya, $76,585,587.\n\nSteam'da yer almayanlar: 100.0%.\n\nB  İki raf birbiriyle uyuşuyor\n\nİki pazar yeri üst sınırın üzerinde anlaşmaya varırken, üçü ise daha esnek bir anlaşmaya varıyor. 51 kategoriler, 176 kopya, $2,038,814.\n\nSteam'da yer almayanlar: 100.0%.\n\nC  Bir raf — kullanılmıyor\n\nYukarıdaki sınırın üzerindeki tek satış teklifi, tek bir piyasada yer almaktadır. 171 kategoriler, 247 kopyaları. Tamlık amacıyla galeride gösterilmiştir ve bu sayfadaki tüm toplamlardan hariç tutulmuştur.\n\nBunlar fiyat talebidir, fiyatın kanıtı değildir.\n\nBu düzeltmenin maliyeti ve karşılığında elde edilenler\n\nC notunun kaldırılmasıyla, başlıktan “171” kategorileri ve “$3,825,125” ibaresi çıkar. Geriye kalan kısım daha küçük ve tartışılması çok daha zor: 248 kategoriler, 18,394 listelenen kopyalar, $78,624,401, ve 100.0% — bunların her biri — Valve sitesindeki pazarda bulunmuyor. C sınıfı satırlar, rakamın değişmesinin sebebidir; bunlar gizli değil, listelenmiştir.\n\nEser olarak ayrılan kayıtlar\n\nAynı ürün için en ucuz satış fiyatının üç katından fazla olan tüm teklifler bir kenara ayrılır. Verilerin kendisinden anlaşılan kur üzerinden dönüştürüldüğünde, bunların çoğu yuvarlak CNY rakamlarıdır — bu da bir tekliften ziyade yer tutucu ya da platform üst sınırının bir göstergesidir. Çünkü bu sayfadaki her toplam tutar, en ucuz Şunu belirtmek gerekirse, bu isimlerin hiçbiri bir rakamı şişirmiş olamaz; bunların listeye alınmaması, hiçbirinin manşet olarak gösterilememesi içindir.\n\nÜrün\tEn ucuz canlı teklif\tBir kenara koy\nSouvenir P2000 | Wicked Sick (Minimal Wear)\t$148,954\t$1,489,543\n★ Specialist Gloves | Crimson Kimono (Minimal Wear) | Phase 1\t$37,239\t$119,163\nSouvenir USP-S | Printstream (Factory New)\t$2,000\t$59,582\n★ Bowie Knife | Crimson Web (Factory New)\t$2,957\t$43,030\n★ Karambit | Marble Fade (Factory New) | 1st\t$11,916\t$38,874\nSticker | Ninjas in Pyjamas (Holo) | Katowice 2014\t$5,000\t$31,748\nSouvenir AWP | Dragon Lore (Battle-Scarred)\t$4,225\t$29,157\n★ Karambit | Doppler (Minimal Wear) | Ruby\t$7,122\t$27,273\n419’daki tüm kategoriler ve her bir fiyatın karşılık geldiği nesne\n\nKaynak: https://phishdestroy.io/steam_dossier/tr/skin_atlas#gallery\n\n04 / bunun yerine nereye gitti\nSteam’in taşımayacağı şeyleri taşıyan raflar\n\nAynı listeler, bunları barındıran pazar yerlerine göre gruplandırılmış. Bu, kopyaların bulunduğu yerlerin sayısını gösterir listelenen, ki bu, bunların kime ait olduğu ile aynı şey değildir ve burada bu anlamda anlaşılmamaktadır.\n\nPazar yerlerine göre, üst sınırın üzerindeki ilanların taban değeri\no rafta listelenen en düşük satış fiyatı olan x adet\nYouPin 898\n$22,720,252\nBUFF163\n$22,022,606\nC5Game\n$12,560,543\nCSFloat\n$10,871,845\nSkinport\n$1,385,060\n\nYukarıdaki sırayla yetki alanları: YouPin 898 — Çin · BUFF163 — Çin · C5Game — Çin · CSFloat — Amerika Birleşik Devletleri · Skinport — Almanya / Malta. Aynı fiziksel ürün bu rafların birden fazlasında listelenebilir; bu nedenle bu rakamlar başka hiçbir pazar toplamıyla toplanmamalıdır.\n\nFiyat dilimine göre taban değer\nsınırın üzerindeki paranın nasıl dağıtıldığı\n$1.8k-3k\n$9,842,391\n$3k-10k\n$36,787,269\n$10k-50k\n$20,038,749\nover $50k\n$2,891,897\n05 / sayabileceğiniz kıtlık\nArzın gerçekte ne kadar kısıtlı olduğu\n\nHer bir CS2 öğesinin bir nadirlik değeri vardır ve pazar yerleri, bu değerin her bir aralığında kaç kopya bulunduğunu açıklar. Bu da “nadir” kelimesini bir sıfattan sayıya dönüştürür — ve işte bu sayı, tek bir ele geçirilmiş hesabın neden özel olarak hazırlanmış bir oltalama kiti için harcanan çabaya değdiğini açıklar.\n\nAWP | Ejderha Bilgisi\n150 listelenmiş ·11,350 $'dan başlayan fiyatlarla\n0.00–0.01\n29 · $14,730\n0.01–0.02\n54 · $11,618\n0.02–0.03\n26 · $11,350\n0.03–0.04\n25 · $11,618\n0.04–0.07\n16 · $11,585\n\nAWP | Dragon Lore (Fabrika Çıkışı)\n\nM4A4 | Howl\n105 listelenmiş ·6,628 $'dan başlayan fiyatlarla\n0.00–0.01\n11 · $10,725\n0.01–0.02\n14 · $8,088\n0.02–0.03\n11 · $7,580\n0.03–0.04\n19 · $6,703\n0.04–0.07\n50 · $6,628\n\nM4A4 | Howl (Fabrika Çıkışı)\n\nAK-47 | Wild Lotus\n113 listelenmiş ·14,373 $'dan başlayan fiyatlarla\n0.00–0.01\n25 · $22,343\n0.01–0.02\n11 · $19,364\n0.02–0.03\n3 · $19,645\n0.03–0.04\n15 · $15,044\n0.04–0.07\n59 · $14,373\n\nAK-47 | Wild Lotus (Fabrika Çıkışı Yeni)\n\nAWP | Gungnir\n173 listelenmiş ·11,618 $'dan başlayan fiyatlarla\n0.00–0.01\n28 · $17,875\n0.01–0.02\n21 · $13,600\n0.02–0.03\n32 · $12,065\n0.03–0.04\n29 · $11,735\n0.04–0.07\n63 · $11,618\n\nAWP | Gungnir (Fabrika Çıkışı)\n\nAK-47 | Ateş Yılanı\n278 listelenmiş ·663 $'dan başlayan fiyatlarla\n0.15–0.18\n87 · $730\n0.18–0.21\n49 · $712\n0.21–0.24\n52 · $703\n0.24–0.27\n18 · $715\n0.27–0.38\n72 · $663\n\nAK-47 | Ateş Yılanı (Sahada Test Edildi)\n\nSertleştirilmiş (tüm seviyeler / mavi mücevher)\n76 listelenmiş ·1,638 $'dan başlayan fiyatlarla\n0.07–0.08\n1 · $2,516\n0.08–0.09\n4 · $2,482\n0.09–0.10\n6 · $3,856\n0.10–0.11\n7 · $2,797\n0.11–0.15\n58 · $1,638\n\nAK-47 | Sertleştirilmiş (Asgari Aşınma) | Sınıf1\n\nBantlar, piyasa platformlarının kendi likidite aralıklarıdır; yalnızca en az bir aktif emir içeren bantlar çekilir. Her çubuğun yanındaki fiyat, o banttaki en düşük aktif satış fiyatıdır; dolayısıyla düşük likiditeye ilişkin prim, belirtilmek yerine doğrudan okunabilir.\n\n06 / hareket, Steam adresinden alınmıştır\nÜçüncü taraf rafların gerçekte neyi başardığı\n\nValve Bu seviyede kullanışlı bir geçmiş verisi yayınlamamaktadır ve bu dosyada da böyle bir iddia bulunmamaktadır. Skinport, son 24 saat, 7, 30 ve 90 gün içindeki kendi tamamlanmış satışlarını yayınlamaktadır ve burada mevcut olan zaman boyutu da tam olarak budur: her bir son pencere için gerçekleşen medyan fiyat, endekslenmiş şekilde 90-gün medyanı 100. şeklindedir. Her iki grafikte de “Steam” verileri yer almamaktadır.\n\nGerçekleşen fiyat medyanı, son dönem aralığı\n90-gün ortalamasına göre endekslenmiş · 6,758 öğeleri, 20+ satışlar\n85\n91\n97\n103\n100\n90d\n94\n30d\n90\n7d\n88\n24h\nGünlük tamamlanan satışlar\naynı ürünler, aynı pencereler\n7,621\n9,653\n11,684\n13,716\n12,700\n90d\n11,894\n30d\n9,540\n7d\n8,637\n24h\n\nBunlar, iki dikey ölçeğe sahip tek bir grafik değil, iki ayrı grafiktir: Endeks ve günlük sayı arasında ortak bir birim yoktur ve bunları ortak bir eksen üzerinde çizmek, geçerli olmayan bir karşılaştırmaya yol açacaktır. Pencereler iç içe geçmiş ve takip edici niteliktedir — 90-adresindeki günlük rakam, 24-adresindeki saatlik rakamı içermektedir — dolayısıyla bu bir günlük seri değildir ve öyle yorumlanmamalıdır. Bu verinin desteklediği sonuç dar kapsamlıdır ve açıkça belirtilmiştir: Skinport adresinde yayınlanan takip eden pencereler boyunca, gerçekleşen medyan fiyat kendi 90-günlük medyanının altında kalmıştır ve günlük satış sayısı da buna paralel olarak düşmüştür.\n\nSkinport gerçekleşen satışlar. Pencereler iç içe geçmiş ve kayan bir yapıya sahiptir; dolayısıyla her bir nokta, kayan pencere boyunca gerçekleşen fiyatların medyanını temsil eder ve bu değer, 90-gününün medyanına göre endekslenmiştir. Bu, günlük bir seri değildir ve Steam verileri kullanılmamıştır.\n\n07 / neyden yapıldığı\nOn altı yıllık etiketler ve bir avuç eldiven\n\nKapak üzerindeki ürün grubu, oyunun genel bir kesitini yansıtmamaktadır. Bu grup, birkaç nadir parça ve birkaç koleksiyona odaklanmaktadır; bunların birçoğu artık hiçbir şekilde elde edilememektedir — işte tam da bu nedenle arz, fiyata ayak uyduramamaktadır.\n\nKapağın üstündeki kategoriler, nadirlik derecesine göre\nürün kategorilerinin sayısı\nCovert\n321\nClassified\n39\nRestricted\n24\nContraband\n12\nMil-Spec Grade\n9\nConsumer Grade\n9\nIndustrial Grade\n5\nKoleksiyona göre, başlığın üstündeki kategoriler\nen iyi on koleksiyon\nThe St. Marc Collection\n13\nThe Cobblestone Collection\n13\nThe Norse Collection\n12\nThe Arms Deal Collection\n9\nThe Canals Collection\n7\nThe Gods and Monsters Collection\n6\nThe Revolution Collection\n4\nThe 2021 Train Collection\n4\nThe Rising Sun Collection\n4\nThe Chop Shop Collection\n4\n\nKategoriye göre: skin 366, sticker 48, container 3, sticker_slab 2.\n\n08 / birinin gerçekten ödediği en yüksek tutar\nBir halka arzla değil, bir işlemle desteklenen en yüksek seviyeler\n\nBu sayfadaki diğer tüm fiyatlar bir sormak — bir satıcının istediği şey. Bunlar şunlardır: satışlar: Her bir ürün için son 90 gün içinde Skinport adresinde kaydedilen en yüksek tamamlanmış işlem tutarı. Bu dosyada yer alan ve birinin gerçekten ödediği tek rakam budur; her satır, pazar yerine bağlantı içermektedir; böylece bu rakam, bize değil kaynağına göre doğrulanabilir.\n\n21,216pencerede satışı tamamlanmış ürünler\n106Valve’in listeleme tavan fiyatında veya bu fiyatın üzerinde satılan\n$14,192gerçekleştirilen en yüksek tek seferlik satış\n67/419kayıtlı herhangi bir satışa sahip, üst sınırın üzerindeki kategoriler\nBu dönemde gerçekleşen en yüksek tutarlı otuz satış\nÜrün\tEn yüksek satış\tOrtalama satış fiyatı\tSatışlar\tŞu anda en ucuz fiyat teklifi\tSteam\tBir göz at\nAWP | Gungnir (Factory New)\t$14,192\t$11,343\t5\t$11,490\tabsent\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Factory New)\t$12,387\t$12,387\t1\t$13,836\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Factory New)\t$11,779\t$11,063\t16\t$10,941\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Minimal Wear)\t$11,693\t$11,693\t1\t$9,946\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Minimal Wear)\t$10,437\t$10,437\t1\t$9,610\tabsent\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Blue Laminate (Minimal Wear)\t$9,772\t$37\t76\t$30\t$40\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Minimal Wear)\t$9,463\t$9,463\t1\t$9,500\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Minimal Wear)\t$9,104\t$9,026\t6\t$8,524\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Hedge Maze (Minimal Wear)\t$8,139\t$8,139\t1\t$6,819\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Field-Tested)\t$7,617\t$7,390\t4\t$7,194\tabsent\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Field-Tested)\t$7,615\t$7,615\t1\t$7,100\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Field-Tested)\t$7,149\t$7,006\t2\t$7,165\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Field-Tested)\t$6,711\t$6,194\t15\t$5,988\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Factory New)\t$6,679\t$6,613\t3\t$6,628\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Superconductor (Factory New)\t$6,084\t$6,084\t1\t$7,969\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Battle-Scarred)\t$5,750\t$5,413\t3\t$5,899\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Pandora's Box (Minimal Wear)\t$5,520\t$5,508\t3\t$4,998\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Vice (Factory New)\t$5,385\t$5,158\t2\t$5,700\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Minimal Wear)\t$5,342\t$4,989\t19\t$4,997\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Hedge Maze (Field-Tested)\t$5,334\t$4,862\t5\t$3,724\tabsent\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Vulcan (Factory New)\t$5,275\t$1,418\t12\t$1,280\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Well-Worn)\t$4,978\t$4,978\t1\t$4,942\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Well-Worn)\t$4,931\t$4,931\t1\t$5,445\tabsent\tSkinport CSFloat Steam\nAK-47 | Hydroponic (Factory New)\t$4,802\t$4,351\t2\t$3,648\tabsent\tSkinport CSFloat Steam\n★ Talon Knife | Case Hardened (Minimal Wear)\t$4,588\t$466\t16\t$442\t$630\tSkinport CSFloat Steam\nAWP | Medusa (Factory New)\t$4,484\t$4,484\t1\t$4,171\tabsent\tSkinport CSFloat Steam\n★ Specialist Gloves | Pillow Punchers (Factory New)\t$4,359\t$4,359\t1\t$4,302\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Pandora's Box (Field-Tested)\t$4,359\t$3,666\t11\t$3,245\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Field-Tested)\t$4,289\t$4,225\t8\t$4,022\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Battle-Scarred)\t$4,124\t$4,124\t1\t$4,279\tabsent\tSkinport CSFloat Steam\nAynı ürün, aynı 90 günleri, aralarında büyük fark olan fiyatlar\n\nBu analiz, medyan fiyatı $100 olan ve en az beş tamamlanmış satışa sahip ürünlerle sınırlandırılmıştır; zira ucuz bir görünümde tek bir olağanüstü satış, oranı büyük ölçüde etkiler. Geriye kalanlar ise çoğunlukla Sertleştirilmiş sonuçlar; burada fiyat, formasyona göre belirlenir ve piyasa her formasyonu tek bir isim altında sınıflandırır — bu mekanizma, 05. bölümünde float ile ölçülmüştür\n\nÜrün\tEn yüksek değer ile medyan değer\tEn yüksek satış\tOrtalama satış fiyatı\tSatışlar\tBir göz at\n★ Talon Knife | Case Hardened (Minimal Wear)\t+884%\t$4,588\t$466\t16\tSkinport CSFloat Steam\nDesert Eagle | Cobalt Disruption (Factory New)\t+859%\t$1,210\t$126\t115\tSkinport CSFloat Steam\nAWP | BOOM (Minimal Wear)\t+814%\t$1,232\t$135\t89\tSkinport CSFloat Steam\nAK-47 | Case Hardened (Well-Worn)\t+769%\t$1,720\t$198\t70\tSkinport CSFloat Steam\nAWP | Graphite (Factory New)\t+761%\t$1,469\t$171\t124\tSkinport CSFloat Steam\n★ Talon Knife | Case Hardened (Field-Tested)\t+509%\t$2,437\t$400\t48\tSkinport CSFloat Steam\n★ Kukri Knife | Case Hardened (Minimal Wear)\t+448%\t$723\t$132\t69\tSkinport CSFloat Steam\n★ Kukri Knife | Case Hardened (Field-Tested)\t+415%\t$549\t$106\t128\tSkinport CSFloat Steam\n★ Ursus Knife | Case Hardened (Minimal Wear)\t+371%\t$597\t$127\t12\tSkinport CSFloat Steam\nAK-47 | Case Hardened (Field-Tested)\t+369%\t$1,037\t$221\t125\tSkinport CSFloat Steam\nAK-47 | Red Laminate (Minimal Wear)\t+360%\t$552\t$120\t18\tSkinport CSFloat Steam\nAWP | Asiimov (Field-Tested)\t+351%\t$528\t$117\t439\tSkinport CSFloat Steam\nAK-47 | Vulcan (Field-Tested)\t+337%\t$865\t$198\t241\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Nightwish (Factory New)\t+322%\t$625\t$148\t31\tSkinport CSFloat Steam\nAWP | Lightning Strike (Factory New)\t+319%\t$2,065\t$493\t198\tSkinport CSFloat Steam\nStatTrak™ AWP | Redline (Minimal Wear)\t+312%\t$574\t$139\t24\tSkinport CSFloat Steam\nStatTrak™ AWP | Asiimov (Battle-Scarred)\t+287%\t$524\t$135\t37\tSkinport CSFloat Steam\nAK-47 | Redline (Minimal Wear)\t+277%\t$562\t$149\t112\tSkinport CSFloat Steam\nAWP | Crakow! (Factory New)\t+275%\t$379\t$101\t72\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Vulcan (Factory New)\t+272%\t$5,275\t$1,418\t12\tSkinport CSFloat Steam\n\nBu, 90-sitesinde kaydedilen günlük en yüksek fiyattır, TÜM ZAMANLARIN EN YÜKSEK FİYATI DEĞİLDİR ve SADECE BİR pazar yerini kapsamaktadır. Bu dosyada hiçbir yerde tüm zamanların en yüksek rakamı belirtilmemiştir. Skinport sitesinde satış bilgisi bulunmayan bir ürün, bu sergide tamamen yer almamaktadır; bu nedenle set, sayım sonuçlarından daha küçüktür.\n\nDoğrulama bağlantıları, kataloğun kendi platform tanımlayıcılarından oluşturulur. Bu bağlantılar, okuyucunun ürünü bize göre değil kaynağa göre kontrol edebilmesi için her bir satış platformundaki ürün sayfasına yönlendirir. Dış bağlantılar şunları içerir: rel=\"nofollow\": Bunlar alıntılardır, tavsiye değildir; ayrıca söz konusu destinasyonların birçoğu, bu araştırmanın eleştirdiği pazar yerleridir.\n\n09 / köken ve sınırlar\nBunun kaynağı ve neleri gösteremediği\n\nBu sayfadaki tüm rakamlar, yanlarında hash değerleri de yayınlanan iki anlık durum dosyasından yeniden hesaplanmıştır. Buradaki hiçbir bilgi başka bir sitedeki makaleden alıntılanmamıştır.\n\nKaynak ve erişim\n\ncs2.sh, API, GET /v1/prices/latest ve GET /v1/schema; tek bir anlık görüntü, 2026-09-23adresinden alınmıştır. T00:44:27.871388581Z, fiyatlar ABD Doları cinsindendir.\n\nVeriler, arşivde kayıtlı olan “GDPR” adlı talep sahibinin sahip olduğu ücretli ticari abonelik kapsamında, sağlayıcının kendi şartları uyarınca elde edilmiştir. Hiçbir pazar yeri taraması yapılmadı ve hiçbir pazar yerinin kimlik bilgileri kullanılmadı. Talep sahibinin anahtarı bu depo dışında tutulmaktadır ve buradaki hiçbir dosyada yer almamaktadır.\n\nBir ürünün şartları nasıl karşılanır?\n\nBUFF, CSFloat, Skinport, YouPin veya C5Game’de en az bir aktif satış teklifi bulunan her temel ürün, EN UCUZ satış teklifine göre bir fiyat aralığına yerleştirilir; dolayısıyla bu aralık hiçbir zaman Steam adresine bağlı değildir. “Steam kapsamı”, verilerin toplanma anında o aralıkta bulunan ve herhangi bir aktif Steam satış teklifi taşıyan ürünlerin payını ifade eder. Steam, desen ve faz varyantlarını ayrı olarak listelemediklerinden, bunlar sıralamadan hariç tutulur; bunların dahil edilmesi Steam değerini olduğundan düşük gösterecektir. Renderlar, aynı ürünlere ait ve yerel olarak depolanan katalog görselleridir.\n\nGörselleştirmeler ve görsel hakları. Katalog ürün görselleştirmeleri, fiyat satırlarıyla aynı market_hash_name için sunulan ve çevrimdışı kullanım ile IPFS görüntülemesi amacıyla yerel olarak depolanan sağlayıcının görselleridir. Bu görseller PhishDestroy'in eseri değildir: tüm ürün görselleri, logolar ve ekran görüntüleri ilgili sahiplerinin mülkiyetindedir (cs2.sh, CSFloat, Skinport, BUFF, YouPin, C5Game, Valve ve diğerleri). Bu görseller yalnızca tanımlama ve kamu yararına habercilik amacıyla çoğaltılmıştır; herhangi bir mülkiyet veya lisans iddiası bulunmamaktadır.\n\nElde edemediğimiz şeyler\n\nKullanılan abonelik seviyesi yalnızca güncel anlık görüntüler için geçerlidir. Geçmişe ait ve arşiv uç noktaları kullanılamıyordu ve Bu sayfanın hiçbir yerinde herhangi bir tarihsel veri dizisi belirtilmemiştir \"Geçmiş Dönem Satışları\"nın ötesinde Skinport, 06. bölümünde yer almaktadır.\n\nTek bir anlık görüntü, zaman serisi değil. Yakalama anında Steam sitesinde bir listelemenin bulunmaması, o öğenin orada asla görünmeyeceğinin kanıtı değildir; bu, o anda rafın ölçülen durumudur ve üst sınırın üzerindeki fiyatlar için Valve sitesinin yayınladığı kuralın gerektirdiği şeydir: Valve sitesinin Topluluk Pazarı, listelemeleri açıkça öğe başına $1,800 ile sınırlamaktadır (maksimum Steam Cüzdan bakiyesi $2,000; bkz. Steam Topluluk Pazarı SSS arşivlenmiş 2026-09-21 ↗ ve Steam Abone Sözleşmesi § 3.C arşivlenmiş 2026-09-24 ↗).\n\nNotlandırma\n\nBir ürünün fiyatı her zaman o ürünün en ucuz güncel satış teklifidir; dolayısıyla yüksek bir aykırı değer, toplam tutarı asla şişiremez. Sınıflandırma, hangi satırların fiyatlandırılabileceğini belirler. Aynı ürün için en ucuz satış teklifinin üç katından fazla olan herhangi bir fiyat teklifi, güncel fiyat olarak kabul edilmez ve bir kenara ayrılır. A Sınıfı: Hala üç veya daha fazla pazar yeri üst sınırın üzerinde fiyat teklif ediyor ve bunların medyanı, en ucuz fiy25'si aralığında yer alıyor. B Sınıfı: İki pazar yeri aynı fiyatta anlaşıyor veya üçü daha az sıkı bir şekilde aynı fiyatta anlaşıyor. C Sınıfı: Tek bir raf – bir satış fiyatı, piyasa fiyatı değil. Bu dosyada yalnızca A ve B sınıfları belirtilmiştir.\n\nAykırı değer kuralı: fiyat teklifi > 3.0çarpı aynı ürünün en ucuz satış fiyatı.\n\nToplamlar neden alt sınır olarak kabul edilir?\n\nHer bir pazar yeri için ürünün en düşük Satış fiyatı, raf listesindeki kopya sayısıyla çarpılır. Oradaki her iki kopyadan birinin fiyatı bu en düşük satış fiyatı kadar ya da daha yüksektir; dolayısıyla gerçek ilan edilen değer, tahminlere dayalı değil, yapısal olarak daha yüksektir. Bu ne bir satış, ne bir nakit akışı, ne de CS2 ekonomisinin bir değerlemesidir.\n\nKendiniz kontrol edin\n\nBu sayfadaki her grafiğin temelini oluşturan türetilmiş veri kümeleri tam olarak yayınlanmaktadır: atlas veri kümesi, sınıflandırma ve artefakt ekranı, temel nüfus sayımı ve her bir ham anlık görüntünün SHA-256'sini içeren manifest dosyası.\n\nAçılışta kaydedilen bir düzeltme\n\nEşlik eden kayıt defterinin daha önceki bir taslağında, bir Çinli e-ticaret sitesinde $148,954 fiyatla satılan Souvenir AK-47 | Point Disarray ürünü başı çekiyordu; oysa Steam sitesinde fiyatı $119. olarak belirlenmişti. Bu satır C sınıfındadır: tek bir raf, tek bir kopya ve bunu doğrulayan başka hiçbir e-ticaret sitesi yoktur. Bu bir talep fiyatıdır, gerçek bir fiyat değildir ve hem burada hem de o sayfada derecesi düşürülmüştür. Doğrulanmış lider ise Sticker | Titan (Holo) | Katowice 2014 adresindeki üründür. $66,285, 4 adresinde alıntılanan, birbirinden 5.2% aralıkta yer alan pazar yerleri — ve Steam adresinde hiç bulunmayanlar.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Cilt Fiyat Merdiveni Atlası — Likidite Uçurumu"
          },
          {
            "level": 2,
            "id": null,
            "text": "Uçurum, talebe göre değil, kurala göre oluşur"
          },
          {
            "level": 3,
            "id": null,
            "text": "Bu şeklin neyi dışladığı"
          },
          {
            "level": 2,
            "id": null,
            "text": "İstenen fiyat, fiyat değildir"
          },
          {
            "level": 3,
            "id": null,
            "text": "A  Üç veya daha fazla raf birbiriyle uyumludur"
          },
          {
            "level": 3,
            "id": null,
            "text": "B  İki raf birbiriyle uyuşuyor"
          },
          {
            "level": 3,
            "id": null,
            "text": "C  Bir raf — kullanılmıyor"
          },
          {
            "level": 3,
            "id": null,
            "text": "Bu düzeltmenin maliyeti ve karşılığında elde edilenler"
          },
          {
            "level": 3,
            "id": null,
            "text": "Eser olarak ayrılan kayıtlar"
          },
          {
            "level": 2,
            "id": null,
            "text": "419’daki tüm kategoriler ve her bir fiyatın karşılık geldiği nesne"
          },
          {
            "level": 2,
            "id": null,
            "text": "Steam’in taşımayacağı şeyleri taşıyan raflar"
          },
          {
            "level": 2,
            "id": null,
            "text": "Arzın gerçekte ne kadar kısıtlı olduğu"
          },
          {
            "level": 2,
            "id": null,
            "text": "Üçüncü taraf rafların gerçekte neyi başardığı"
          },
          {
            "level": 2,
            "id": null,
            "text": "On altı yıllık etiketler ve bir avuç eldiven"
          },
          {
            "level": 2,
            "id": null,
            "text": "Bir halka arzla değil, bir işlemle desteklenen en yüksek seviyeler"
          },
          {
            "level": 3,
            "id": null,
            "text": "Bu dönemde gerçekleşen en yüksek tutarlı otuz satış"
          },
          {
            "level": 3,
            "id": null,
            "text": "Aynı ürün, aynı 90 günleri, aralarında büyük fark olan fiyatlar"
          },
          {
            "level": 2,
            "id": null,
            "text": "Bunun kaynağı ve neleri gösteremediği"
          },
          {
            "level": 3,
            "id": null,
            "text": "Kaynak ve erişim"
          },
          {
            "level": 3,
            "id": null,
            "text": "Bir ürünün şartları nasıl karşılanır?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Elde edemediğimiz şeyler"
          },
          {
            "level": 3,
            "id": null,
            "text": "Notlandırma"
          },
          {
            "level": 3,
            "id": null,
            "text": "Toplamlar neden alt sınır olarak kabul edilir?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Kendiniz kontrol edin"
          },
          {
            "level": 3,
            "id": null,
            "text": "Açılışta kaydedilen bir düzeltme"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/tr/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/tr/skin_atlas#gallery",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://skinport.com/market?search=AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260924114457/https://store.steampowered.com/subscriber_agreement/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-atlas.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-artefact-screen.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-above-the-ceiling.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/tr/skin_atlas.content.json",
      "export_json_sha256": "93e6934c0ad7c85758260be798eb7e01bbce006ce6067be926ed23fc451916b8"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "tr/social_graph.html",
      "language": "tr",
      "title": "Kaydedilen bağlantıları takip edin — “Steam” Dosyası",
      "source_url": "https://phishdestroy.io/steam_dossier/tr/social_graph",
      "source_html_sha256": "30cabe819e3a219d7d6428f2c8491b0004d3c9b010d75d383d9ee8464d0786c1",
      "exported_at": "2026-09-29T00:21:04.543Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "social_graph.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/tr/social_graph.pdf?v=print-20260929-v5",
        "sha256": "5cd6a016d12a702e0c92c0890a9e1a7b52820375218a49f88db0a0bcf8edc656",
        "bytes": 121391,
        "pages": 6
      },
      "integrity": {
        "signed_object": "social_graph.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "social_graph.content.json.asc",
        "digest_file": "social_graph.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify social_graph.content.json.asc social_graph.content.json",
          "sha256sum -c social_graph.content.json.sha256"
        ]
      },
      "content": {
        "text": "Bağlantıları takip edin.Her bir ilişkiyi inceleyin.\n\nBir profili ara. Bir ilişki türü seç. Yakalanan kayıtlarda bu profilin hemen yanındaki profilleri takip et. Araştırma aracı: Kenarlar, herhangi iki düğüm arasındaki doğrudan temasın, özel koordinasyonun veya suistimalin kanıtı değil, kamusal ilişkileri temsil eder. Bir 3,435-düğüm düzeni, en iyi şekilde filtreler kullanılarak incelenir.\n\nHer seferinde tek bir ilişkiyi inceleyin\n\n💡 Grafiği yeniden düzenlemek için düğümlere tıklayıp sürükleyin. Ayrıntılı profilleri görmek için fareyi üzerine getirin. Turkuaz renkli kesintisiz çizgiler = Arkadaşlıklar, Kehribar renkli kesikli çizgiler = Karşılıklı Yorumlar.\n\nİlişki türüProfil ve doğrudan komşular\n\n3,435 profiller · 4,551 kaydedilmiş bağlantılar\n\nBir profil arayıp seçin ya da bir düğüme tıklayın. Yalnızca o profilin kayıtlı doğrudan komşuları kalır. Bir kenar, bir ilişkiyi kaydeder; özel bir koordinasyon oluşturmaz.\n\nYakalanan veri kümesindeki profiller\n\nKaynak tablonun tamamı: 3,435'daki tüm satırları indir (CSV). Aşağıdaki tablo başlangıçta ilk 25 satırını göstermektedir; arama ve sayfalandırma işlemleri tüm veri kümesini kapsamaktadır.\n\n1–25 / 3,435 satır\nKarakter Adı\tSteamID64\tGizlilik\tDurum\tGrup Üyelikleri\tDondurulmuş Stok (ABD Doları)\tKonum\nMahatma Gandhi\t76561198333721623\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tPH\nGalley//갤리🌠🌙\t76561198043416832\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tKP\n$Schlächter\t76561198860277343\tPUBLIC\tClean\tsteambans\t$0.00\tUnknown\n❄r3dsn0w000™❄ [Cristi]🎮\t76561197986767957\tPUBLIC\tClean\tCommunityLegends\t$0.00\tRO\n(2a03) Wolfy\t76561197991671851\tPUBLIC\tCommunity\tsr_public\t$0.00\tUS\nZloy2288\t76561198038578334\tPUBLIC\tClean\tsteambans\t$0.00\tBY\njessy\t76561198039125237\tPUBLIC\tCommunity, VAC (1x)\tCommunityLegends\t$0.00\tJP\nJithraRufure\t76561198071896910\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\n| Níllerdínho |\t76561198003487438\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tDK\nJones is back\t76561198023013026\tPRIVATE\tVAC (1x)\tsteambans\t$0.00\tUnknown\nUNEX | ★✠☠ MoH3st ☠✠\t76561198050763123\tPUBLIC\tClean\tsteambans\t$0.00\tDE\nTrojan\t76561198048457084\tPUBLIC\tClean\tCommunityLegends\t$0.00\tDE\n𝗠𝗮𝘆𝘂 ❤\t76561199377967696\tPUBLIC\tClean\tsr_public\t$0.00\tIS\nbig fucking idiot\t76561198871206397\tPUBLIC\tVAC (1x)\tsteambans\t$0.00\tUnknown\nSOFF Games\t76561198227129276\tPUBLIC\tClean\tcommunitymoderators\t$0.00\tRU\nThijminecraft02\t76561198253895669\tPUBLIC\tClean\tSteamIDcouk SArchive\t$0.00\tNL\nStatic-sama\t76561198289329793\tPUBLIC\tClean\tsteambans\t$0.00\tJP\n𝙸mmortal 𝚂targazer\t76561198142116760\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\nCommander Keen\t76561197987773287\tPUBLIC\tClean\tsteambans\t$0.00\tBE\nS1mX\t76561199648509165\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\nmixwell\t76561199276547472\tPUBLIC\tClean\tsr_public\t$0.00\tJP\nP90_GOD_YyEs™\t76561198285821942\tPUBLIC\tClean\tsteambans\t$0.00\tHK\nhewwo?\t76561199133807546\tPUBLIC\tVAC (1x)\tsteambans\t$0.00\tCH\n♕Kamikaze Atze♕\t76561198002700103\tPUBLIC\tClean\tsteambans\t$0.00\tDE\nPastica\t76561198154655970\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tDZ\nKaydedilmiş dostluk bağları\n\nKaynak tablonun tamamı: 4,299'daki tüm satırları indir (CSV). Aşağıdaki tablo başlangıçta ilk 25 satırını göstermektedir; arama ve sayfalandırma işlemleri tüm veri kümesini kapsamaktadır.\n\n1–25 / 4,299 satır\nKullanıcı A\tYön\tKullanıcı B\tİlişki Türü\nMahatma Gandhi\n76561198333721623\t↔\tDeskjet\n76561198272738437\tMutual Friends\nGalley//갤리🌠🌙\n76561198043416832\t↔\tomega\n76561197960274529\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tFisty\n76561198057301486\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tFaalagorn\n76561198001116101\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tMURK\n76561198036995672\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tÅρøᴛʜℯᴛȋᴄÅʟȋℯη ♛👽♛\n76561197984615267\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tsilatrak\n76561197999629462\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tBlack Blade\n76561198083368493\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tAvenger\n76561197978249317\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tRemtar\n76561198124322650\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tCato\n76561197961345984\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t✪ G λ M Ξ ®\n76561197994308495\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tclees42\n76561198030936806\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t𝓜ε𝔰𝔥 | AusLevels\n76561198108828539\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tSgtFopper™\n76561198002555892\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t❥Miss Bee\n76561198046958996\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tTesTy\n76561198032370068\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tskl_andrey\n76561198136881436\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t\"Exekutor\"\n76561198009583947\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tAraripe\n76561198103754372\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tsteve6678\n76561198053200093\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\ttrinner\n76561197970359081\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tSteph S.\n76561198025653291\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tKirito\n76561198154545657\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tDoc. todt\n76561197984492467\tMutual Friends\nKaydedilmiş yorum bağlantıları\n\nKaynak tablonun tamamı: 252’daki tüm satırları indir (CSV). Aşağıdaki tablo başlangıçta ilk 25 satırını göstermektedir; arama ve sayfalandırma işlemleri tüm veri kümesini kapsamaktadır.\n\n1–25 / 252 satır\nYazar\tYön\tHedef Profil\tTarih\tYorum Metni\nDeskjet\n76561198272738437\t→\tMahatma Gandhi\n76561198333721623\t16 September, 2021 @ 11:02:05 pm PDT\t\"𝑵𝒐𝒘 𝒊𝒇 𝑰 𝒇𝒖𝒄𝒌 𝒕𝒉𝒊𝒔 𝒎𝒐𝒅𝒆𝒍𝑨𝒏𝒅 𝒔𝒉𝒆 𝒋𝒖𝒔𝒕 𝒃𝒍𝒆𝒂𝒄𝒉𝒆𝒅 𝒉𝒆𝒓 𝒂𝒔𝒔𝒉𝒐𝒍𝒆𝑨𝒏𝒅 𝑰 𝒈𝒆𝒕 𝒃𝒍𝒆𝒂𝒄𝒉 𝒐𝒏 𝒎𝒚 𝑻-𝒔𝒉𝒊𝒓𝒕𝑰'𝒎𝒎𝒂 𝒇𝒆𝒆𝒍 𝒍𝒊𝒌𝒆 𝒂𝒏 𝒂𝒔𝒔𝒉𝒐𝒍𝒆\" - Nelson Mandela\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t22 November, 2021 @ 4:10:28 pm PDT\thttps://anige.horigiri.net/?cat=22\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t18 November, 2021 @ 12:45:26 am PDT\thttps://gamerch.com/umamusume/entry/250411\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t8 August, 2021 @ 4:13:25 am PDT\thttps://modoocode.com/304\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t6 February, 2021 @ 3:35:05 pm PDT\t▤ ∫︹- -ω⁾ ⁽︹▓▓︺\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t11 December, 2019 @ 1:50:53 am PDT\thttps://blog.naver.com/aksenwlddj12/221369410039\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t2 October, 2019 @ 7:11:59 am PDT\tǤαllєу║︎갤리..۩\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t9 April, 2019 @ 12:51:28 pm PDT\tExplosiveDamage(owner, from, maxrange, minrange, distmultiplier, dmgmultiplier, mindamage, typ, damagetype, ignore)\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 12:22:47 pm PDT\tinfo - sh_titles.lua\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 12:21:46 pm PDT\tlocal nibbas = 1344 init.lua\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 11:31:58 am PDT\thttp://foreign.aladin.co.kr/shop/wproduct.aspx?ItemId=123955531&start=slayer\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t3 April, 2019 @ 1:26:41 am PDT\tǤαllєу\nLei\n76561198982197954\t→\tJithraRufure\n76561198071896910\t29 December, 2024 @ 12:58:08 pm PDT\t+rep he knows how 2 rush B ￣ヘ￣\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t2 September, 2026 @ 5:16:55 am PDT\tlol\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t20 August, 2026 @ 6:11:03 am PDT\t?\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t25 July, 2026 @ 7:20:05 am PDT\thahahahaha\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t30 June, 2026 @ 12:52:42 pm PDT\twow\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t30 June, 2026 @ 12:41:32 pm PDT\txD\nvalorant enjoyer\n76561199112142402\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:26:30 pm PDT\toh no!!\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:26:11 pm PDT\toh no!!\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:22:22 pm PDT\tomg !!! they know my secret, omg!!!\nvalorant enjoyer\n76561199112142402\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:21:39 pm PDT\t+rep good ♥♥♥♥♥ player\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:20:50 pm PDT\tomg! u cant cheat on secure gaben servers, omg dont report me, they ban me for boosted omg\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 8:37:11 pm PDT\txD\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t28 June, 2026 @ 1:58:14 pm PDT\twow",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Bağlantıları takip edin.Her bir ilişkiyi inceleyin."
          },
          {
            "level": 2,
            "id": null,
            "text": "Her seferinde tek bir ilişkiyi inceleyin"
          },
          {
            "level": 2,
            "id": null,
            "text": "Yakalanan veri kümesindeki profiller"
          },
          {
            "level": 2,
            "id": null,
            "text": "Kaydedilmiş dostluk bağları"
          },
          {
            "level": 2,
            "id": null,
            "text": "Kaydedilmiş yorum bağlantıları"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-profiles.csv",
          "https://steamcommunity.com/profiles/76561198333721623",
          "https://steamcommunity.com/profiles/76561198043416832",
          "https://steamcommunity.com/profiles/76561198860277343",
          "https://steamcommunity.com/profiles/76561197986767957",
          "https://steamcommunity.com/profiles/76561197991671851",
          "https://steamcommunity.com/profiles/76561198038578334",
          "https://steamcommunity.com/profiles/76561198039125237",
          "https://steamcommunity.com/profiles/76561198071896910",
          "https://steamcommunity.com/profiles/76561198003487438",
          "https://steamcommunity.com/profiles/76561198023013026",
          "https://steamcommunity.com/profiles/76561198050763123",
          "https://steamcommunity.com/profiles/76561198048457084",
          "https://steamcommunity.com/profiles/76561199377967696",
          "https://steamcommunity.com/profiles/76561198871206397",
          "https://steamcommunity.com/profiles/76561198227129276",
          "https://steamcommunity.com/profiles/76561198253895669",
          "https://steamcommunity.com/profiles/76561198289329793",
          "https://steamcommunity.com/profiles/76561198142116760",
          "https://steamcommunity.com/profiles/76561197987773287",
          "https://steamcommunity.com/profiles/76561199648509165",
          "https://steamcommunity.com/profiles/76561199276547472",
          "https://steamcommunity.com/profiles/76561198285821942",
          "https://steamcommunity.com/profiles/76561199133807546",
          "https://steamcommunity.com/profiles/76561198002700103",
          "https://steamcommunity.com/profiles/76561198154655970",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-connections.csv",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-comments.csv"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/tr/social_graph.content.json",
      "export_json_sha256": "0549b9666189185210f76516b14199f97cc5f426354af173b6a6ba52af17f230"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "tr/steam_enforcement_evidence.html",
      "language": "tr",
      "title": "Kurallar ve tepkiler — “Steam” Dosyası",
      "source_url": "https://phishdestroy.io/steam_dossier/tr/steam_enforcement_evidence",
      "source_html_sha256": "fe31f97bd8a5cca98056d266d6d808af81fca7dec0ae345da5c355eaa4ac0239",
      "exported_at": "2026-09-29T00:21:07.087Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "steam_enforcement_evidence.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/tr/steam_enforcement_evidence.pdf?v=print-20260929-v5",
        "sha256": "d6bef5c407abc64f3c112c181abc25aee65f8d346cca9714309442ebd81937de",
        "bytes": 378698,
        "pages": 36
      },
      "integrity": {
        "signed_object": "steam_enforcement_evidence.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "steam_enforcement_evidence.content.json.asc",
        "digest_file": "steam_enforcement_evidence.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify steam_enforcement_evidence.content.json.asc steam_enforcement_evidence.content.json",
          "sha256sum -c steam_enforcement_evidence.content.json.sha256"
        ]
      },
      "content": {
        "text": "Kanıt eki / kaynağa bağlı kayıtlar\nSteam Uygulama Kanıtları — Destek Kayıtları ve Geliştirici Ağı\n\nKural. Yanıt.\n\nBU BÖLÜMÜN KANITLADIĞI ŞEY\n\nBu kanıt odası, Valve adresindeki resmi Abone Sözleşmesi’ni, tarihli yaptırım kayıtları, destek anlaşmazlık çözümleri ve 252 depoları ile 3,320 profilleri genelindeki geliştirici ağı kayıtlarıyla karşılaştırmaktadır. Bu karşılaştırma, sıradan hesap sahiplerinin oturumlarının ele geçirilmesinin ardından çürütülemez yaptırımlarla ve destek hizmetlerinin kapatılmasıyla karşı karşıya kaldıklarını, buna karşın yüksek hacimli ticari bot operasyonlarının ise kamuya açık altyapıya erişimle kesintisiz bir şekilde devam ettiğini ortaya koymaktadır.\n\n← Yönetici özetine geri dön\n\nYazılı kısıtlamayı okuyun. Kaydedilmiş yanıtı açın. Kaynağın gösterdiği bilgileri, yanıtlanmamış kalanlarla karşılaştırın.\n\nDestek ve itirazlar ↓Kamu altyapısı ↓\n252depo kayıtları\n3,320halka açık profiller\n4,214farklı profil-depo çiftleri\n98,902ortak depolara sahip profil çiftleri\n01 / Destek, yaptırımlar ve yeniden yapılandırma\nŞikayeti okuyun.Kaynağı ek olarak ekleyin.\nDestek Reddi Galerisi (981 Sergileri) ↗Seçilen kayıtları indir ↓\nHFB / DIŞ KAYNAK KULLANIMI VAKASIKabul görmüş uzlaşma.\nBildirilen işten çıkarmalar.\n\nAşağıda yer alan destek yanıtını ve yüklenici personeli hakkındaki iddianın kaynağını inceleyin.\n\nKonuyu ve kaynaklarını aç →\n\nAşağıda: korunmuş beş Reddit’te herkese açık gönderiler sağlanan destek kayıtları koleksiyonundan. Her bir kayıt, Valve’un destek sistemiyle bildirilen bir etkileşimi belgelemektedir — orijinal kaynak bağlantısı, ekran görüntüsü konumu ve tam metniyle birlikte saklanmaktadır. Bunlar mağdurların ifadeleridir. Bunları doğrulayacak veya çürütecek olan, kimliği doğrulanmış destek günlükleri Valve adresinde tutulmaktadır ve henüz kamuoyuna açıklanmamıştır.\n\n01\nBan & review2024-12-09\nPermanent sanction & closed appeals\n\nThe author reports a permanent account ban, repeated ticket closures and a planned GDPR access request.\n\nREDDIT / PUBLIC TESTIMONYr/ohnePixelCapture record 294\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 303 words\nPermanently banned Steam account without a clear explanation, need help!\n\nsteam_support_tickets_MEGA.json / record 294\n\nHey everyone,\n\nI’m in a really frustrating situation, and I’m hoping someone here can help me or offer advice. My Steam account was just permanently banned for allegedly violating the Steam Subscriber Agreement, and I have no idea why.\n\n# What Steam Support told me:\n\nThe support message said my account was banned due to:\n\n* Suspicious activities related to transferring or attempting to sell/trade the account.\n* Community reports and other unspecified factors.\n\nThey added that the ban is permanent and that they can't help me further. They also warned that future support requests regarding this ban might be ignored. 😞\n\n# Why I’m contesting this ban:\n\n* I have never sold, traded, or transferred my account. I’ve been the legitimate owner since the beginning.\n* On the day the ban occurred, I did nothing noteworthy that could have triggered such a sanction.\n* I received no prior warning, which feels incredibly unfair.\n\n# What I’ve tried so far:\n\n* Contacting Steam Support: I explained my situation and asked for more details, but they’re sticking to their decision and closing my tickets.\n* I’m preparing a request based on my Right of Access (GDPR) to get all the data related to my account.\n\n# Questions for the community:\n\n1. Has anyone successfully had a permanent ban lifted on Steam?\n2. Are there steps I can take to prove I’m the legitimate owner of the account?\n3. Any advice on how to word my request to convince support to reconsider my case?\n4. Would it be helpful to contact the CNIL (I’m based in France) to force Steam to provide more information?\n\nI’m really desperate at the thought of losing all my games, purchases, and years of playtime. Thanks in advance for any help and advice you can give!\n\nhttps://preview.redd.it/jk9qv0gmhv5e1.png?width=1289&amp;format=png&amp;auto=webp&amp;s=b3a333ebb08ea133e2c8747ba126f5a68283d9f7\n\nhttps://preview.redd.it/4sopt0gmhv5e1.png?width=1022&amp;format=png&amp;auto=webp&amp;s=56195d5336118faf9413f1514ead7e8d24c788c3\n\nhttps://preview.redd.it/eqrxw0gmhv5e1.png?width=996&amp;format=png&amp;auto=webp&amp;s=ff3539d28ab754e513ad471822c5de652920101d\n\nhttps://preview.redd.it/728xz0gmhv5e1.png?width=1034&amp;format=png&amp;auto=webp&amp;s=bc5335673509929669af785aa244bf8d2dc58da8\n\n02\nSupport access2025-05-09\nAccount recovery & a reported $10,000 loss\n\nThe author alleges that support reset credentials and removed account protection following another person’s recovery ticket.\n\nREDDIT / PUBLIC TESTIMONYr/legaladviceCapture record 110\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 193 words\nGot $10k stollen from steam inventory due to steam' support fault.\n\nsteam_support_tickets_MEGA.json / record 110\n\nLocation: Quebec, Canada.\n\nLast year, someone hacked my Steam account and stole items worth about $10,000 USD. I only noticed this last week. When I talked to Steam Support, they admitted that someone submitted a ticket to make changes on the account and Steam Support reset my password and turned off all my account security.\n\nI asked Steam Support about getting my items back, but they said there was nothing they could do. They told me I should follow their security recommendations.\n\nThe problem is, I did everything they \"suggested\" to protect an account:\n\n* I had two-factor authentication.\n* My phone number was connected to my account.\n* I used Steam Guard.\n* I printed recovery codes and kept them in a safe.\n\nEven though I did all these things, Steam Support still gave someone else access to my account. The stolen items had been in my account since around 2016-2017. Also, I had not logged in for a few years, so I didn’t accidentally give my information to a fake website.\n\nIs there anything I can do, or do I just have to accept losing $10,000 USD?\n\nThanks for your help.\n03\nRestoration2022-07-07\nA reported $500+ loss & template replies\n\nThe author describes an account compromise, disputed transactions and a support response that allegedly did not address the submitted evidence.\n\nREDDIT / PUBLIC TESTIMONYr/DotA2Capture record 45\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 410 words\nFunds stolen through steam market. Disappointed with Steam response.(or lackthereof)\n\nsteam_support_tickets_MEGA.json / record 45\n\nOn 6th July 2022, 44 unauthorized transactions were made on the steam market using my steam wallet funds totalling roughly $500+ USD to buy worthless 1 cent Dota 2 items. This happened during the wee hours in the morning and i contacted them first thing when i woke up. \n\nI have 2FA enabled all the time, and always thought this would not happen to me as I do not go on betting sites/click sketchy links. My account password + emails were not changed, nor did they take my inventory, just that my funds were used illicitly. Also when I went to disable other APIs, it says there are no other APIs to disable. Shows that it wasn't through me clicking sketchy links and leaving my account details there. Would have lost the whole account if i did so.\n\nWhat baffles me is how did they bypass my 2FA to login my account? Why doesn't steam market purchases go through 2FA as well? First time in 9 years that this happened to me. My acc was logged in 'BY' 'Vitebsk' during the illicit purchases but I'm based in Asia I gathered all the screenshots and provided in the ticket to steam support. \n\nAll i got was the standard copy paste template reply by Steam Support. Lost $500+ and was not even worthy of having a proper person to look into this. I dont think they even read or take a look at the screenshots cause if they did, they would have come to the realization that what happened was clearly fraud, and with a few clicks, reverse the unauthorized transactions, refund my wallet and ban the hijacker. \n\nOver the years, i've spent quite a fair bit on steam but really, this is the kind of recourse we get when our account is compromised? They just don’t care, sigh. I only expect the bare minimum from Steam and looks like even that is quite far-fetched.\n\nSS: https://imgur.com/a/67frcls \n\nHijacker: https://steamcommunity.com/profiles/76561199141246495\n\nSteam Response: https://imgur.com/a/V6v4maM\n\nI could think of a few ways on how to Improve:\n\n1) Add 2FA to market transactions. (even if its bulk posting or selling of items, just 1 2FA notif is required)\n\n2) Enable accounts to be region locked. (if you are migrating, then have to go through steam support etc)\n\n3) Additional Lock on Steam Wallet. (Another password perhaps?)\n\nEDIT: 2nd ticket in and I have still yet to receive a non robotic copy paste template response from Steam.\n04\nRestoration2021-11-29\nSteam Guard & an item-restoration refusal\n\nA preserved post includes the author’s account of item theft and a support response declining restoration.\n\nREDDIT / PUBLIC TESTIMONYr/DotA2Capture record 58\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 563 words\nMany people are losing item via clicking links where steam guard is enabled and steam support doesn't not restore items.\n\nsteam_support_tickets_MEGA.json / record 58\n\nAccounts are getting compromised and might be their pc as well where Steam market is targeted hence the malicious links . I am assuming these hackers are getting encouraged where steam support is not doing nothing and they are getting away with hacking items.  \nLiterally the guy who is supporting the game which he doesn't get any in game advantage just  cosmetics in game only for the sole purpose of supporting the game so that the game will prosper and become beautiful way  to enjoy weekend. But right now players are getting hacked left right and center and steam support  is copy pasting message where in short they are blaming the guy who clicked link. 1st this is happening because they are not targeting players but they are targeting market since they are selling those stuff for real cash via party website. Steam is a huge company and can eradicate the problem or at least can remove links temporarily  in chat since hackers are targeting .They made us install steam guard by saying we wont help if there is no steam guard now steam guard is not enough to save our inventory now they changed their policy  that they should not click any suspicious links. How would we know if the link is suspicious ? After clicking and getting our inventory stolen right !   \n\"we'd have to duplicate an item to restore it. Duplication lowers the value of all items by reducing their scarcity and inflating the economy, which affects everyone involved in trading and the Market. To maintain the value of everyone’s inventory, we do not restore items. For more information, please see the Steam Item Restoration Policy.\"  \nThey care for millions of people IN STEAM MARKET where as few  are losing items which is going to affect market where the rightful owner bought the items and hacker is going to sell the item via 3rd party website and enjoy ! HOW IRONIC !!  \nThis is the message from support where my frnd got his items stolen via clicking on link  \n   \nHi there,  \n\nThank you for the information and screenshots provided.  \n\nIt appears that the account was compromised, please take the following steps to secure your account and computer:  \n\nScan your computer for viruses, key loggers, spyware, and other malicious code using antivirus software with updated virus definitions.  \nChange the password for the email address that is associated with your Steam account.  \nRegularly reset your Steam account password.  \n\nPlease see our Security Recommendations article.  \n\nIn addition, I’m sorry to hear that your items were removed without your permission. Unfortunately, Steam Support does not restore scammed, lost, or stolen items for any reason.  \n\nSince Steam Support does not remove items from accounts, we'd have to duplicate an item to restore it. Duplication lowers the value of all items by reducing their scarcity and inflating the economy, which affects everyone involved in trading and the Market. To maintain the value of everyone’s inventory, we do not restore items. For more information, please see the Steam Item Restoration Policy.  \n\nTo make sure that a scammer is reported, please report them through the Steam Community. Reporting a scammer through the Steam Community is the best way to prevent them from committing future scams.  \n\nTo learn how to avoid scams or hijackings, please see our Trade Scam article.  \n\nIf you still need assistance, please let us know.\n05\nEnforcement2025-05-11\nSelective enforcement & an unexplained ban\n\nA community member describes a disputed ban and contrasts it with the visibility of commercial gambling promotion.\n\nREDDIT / PUBLIC TESTIMONYr/SteamUncensoredCapture record 107\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 1,208 words\n🚨 Steam Bans Without Reason and Ignores Its Community — What’s Going On?\n\nsteam_support_tickets_MEGA.json / record 107\n\nHey r/Steam,\n\nI’m writing this to share my thoughts and concerns about my friend [moneylead](https://steamcommunity.com/id/moneylead/) and Steam’s policies in general. I spoke with him yesterday about his situation, though I didn’t discuss writing this post with him—I asked last night, but he hasn’t responded yet. I want to highlight that this issue is broader than just his case, and while Steam might make changes in the future (though that’s unlikely), I feel the community needs to understand how far Steam has strayed from its original values. I’m not trying to put moneylead in a tough spot with this thread—all the info I’m sharing is public, nothing secretive. I hope he won’t be upset with me, but the community needs this case to see the bigger picture and how Steam feels completely unaccountable.\n\n**Why Does Steam Ignore Its Community?**  \nWhy does a platform like **Roblox** provide a detailed log of ban reasons, while Steam, which claims to be \"community-driven,\" ignores its community, bans whoever they want, for whatever they want, with no transparency? I looked into Roblox as a popular game—not a direct competitor to Steam—to see how their bans look, and you can check it out yourself: [Roblox Ban Reasons](https://www.google.com/search?q=Roblox+ban). Their bans are clear, detailed, and actually explain what you did wrong. I think most decent gaming communities operate like this—not with support agents named Olga, hired through outsourcing, who only know how to send canned auto-replies. Take cases like St4ck—or my friend **moneylead**. All these unbans, like **St4ck’s** or **Alexanddd’s**, happened behind closed doors with zero comments from Steam. Of course, it’s convenient for Steam to handle everything in secret, so no one knows or sees what’s going on—but this violates Steam’s own community rules and principles.\n\n**Who Is moneylead?**  \nI’ve known [moneylead ](https://steamcommunity.com/id/moneylead/)since around 2021. We played Dota 2 a couple of times, and then I just stayed on his friends list. He’s always been a legit player, bringing revenue to Steam through purchases. He never sold his skins, whether in **Dota or CS2—he wasn’t a trader**. All he did was:\n\n* Buy games and skins.\n* Collect badges to level up his profile.\n\nAccording to [SteamSets](https://steamsets.com/account/76561199080934614), he’s given out 324,000 Steam Points—I think he awarded profile rewards to all his friends in the list (though I’m not 100% sure). I do know he ran contests and gave gifts to friends, always supporting the community.\n\n**Steam’s Unfair Treatment**  \nI’ve seen Steam remove his showcases, avatar, description, and even his country multiple times—just because he’s from **Ukraine**. He has a ton of haters leaving toxic comments on his wall, and Steam seems to favor **Russian** users. Every time he tried to appeal the removal of his showcases or profile description—which didn’t break any rules, just had his Instagram link, and his avatar is the same as it is now—Steam moderators didn’t care. **They don’t care about top players who bring them massive revenue, nor about regular users.**\n\n>*Here’s the worst part: moneylead works in cybersecurity, specifically fighting account theft and phishing. He’s neutralized over 5,000 threats targeting Steam alone. And yet, Steam bans him for \"account hijacking\"?*\n\nIf you roughly calculate moneylead’s contribution to Steam and the community—his profile, level, badges (not skins, you can’t sell those)—is this normal, Steam? Banning people, closing tickets, and ignoring users with a spotless reputation who aren’t involved in any commercial activity, just bringing you profit without taking anything in return?\n\n**Steam’s Double Standards**  \nI’m honestly shocked:\n\n* YouTubers who promote casinos and skin gambling? Steam’s fine with that.\n* A cybersecurity expert who fights scams, doesn’t promote casinos, and openly talks about it on his profile? **Banned with no explanation, ignored, and denied an unban.**\n\nI wonder if Steam deliberately bans a high-level account once a year just because of their impunity—maybe for hype or something. Otherwise, this is just madness. It’s scary to think how many regular players have lost their accounts and skins—not because of scammers, but because of Steam’s desire to ignore, send auto-replies, and do whatever they want.\n\n**How Many Others Are Affected?**  \nHow many others are out there—maybe not as well-known—who just have a few games or skins, get banned for nothing, and receive zero explanation or response? **Is this even legal?** Every other platform provides a detailed log with specific violations, but Steam slaps on the same vague label and sends templated responses.\n\n* How safe is it to buy skins on Steam?\n* What’s the chance Steam will just ban your account for no reason, with no explanation?\n\n**A Message to Valve**  \nI wish moneylead the best in resolving this, but Valve, it’d be great if you remembered what \"community\" means and started following the law. Because right now, it looks like your 30% commission, impunity, and sense of being above the law in the U.S. have given you the idea that you can do whatever you want.\n\nI’m sure there are many others like moneylead and St4ck—people who aren’t public or don’t have the resources to fight back. Let’s unite these cases. **If you’re a U.S. resident who’s been banned by Steam without reason and wants to challenge it, please reach out to me.** I’m finishing my **Juris Doctor (J.D.) program at SMU Dedman School of Law** in Dallas, Texas, and I’m participating in a legal clinical practice under Rule 13 of the Texas Supreme Court.\n\nWhat Steam is doing is absolutely disgusting and illegal, and **I’d be happy to help any gamer (legitimate, with no real violations) who has games or skins with value. This will be beneficial for my practice, and it’s time to put Steam in its place and show them they can’t just dictate their own rules with arbitration**. Let’s take it all the way—not for punishment, but for the sake of the community. Maybe if Steam loses a case, they’ll change their policies and start explaining their actions like most popular gaming communities do. Many of us remember how Steam Support used to recover stolen accounts and ended up “stealing” skins themselves—banning without real reasons is basically the same thing, and that’s a serious accusation.\n\nSo, r/Steam, see you soon. I think you understand what you’re doing and how many people you’ve illegally deprived of their assets. I want to raise this issue—not just for the U.S., but for the entire world. You’ve banned class-action lawsuits? **Welcome to Texas.** I recommend starting to look for licensed attorneys in Texas, because I’d love to discuss your company’s policies, feedback, and support agents named Olga—a name that strongly associates with Russian users. Maybe it’d be easier to move your company to Moscow? But I’d be happy to discuss these critical issues on behalf of the global gaming community.\n\nAlso, I wouldn’t recommend ignoring the lawsuit request that will be sent to your physical address and email address, as the court will proceed without you, and that might upset you—especially since things aren’t going so well for a company with stocks like yours.\n\n**Thanks to everyone who took the time to read this. For those who need real help with an unjust Steam ban without any explanation, I’d be happy to assist. For users from Texas, we can easily file a collective lawsuit against Steam—let’s connect and make it happen.**\n02 / Steam geliştirme ağı\nKamu altyapısı.Geniş ölçekte kaydedildi.\nTüm “252” kayıtlarını indir ↓\n\nBirlikte verilen output_steam_network Anlık durum kayıtları, depoları, herkese açık katkıcı/fork ilişkilerini ve profil çakışmalarını içerir. Bunlar, neyin geliştirildiği, kimin katkıda bulunduğu ve neyin forklandığına dair yayınlanmış kayıtlardır. Herkese açık yeteneklerin yazılı kayıtları, Valve adresinin hesaba katması gereken unsurlardır.\n\nDepo / açıklama\tKatkıda Bulunanlar\tÇatalcılar\tKaydedilmiş profiller\nalliedmodders/amxmodx\n\nAMX Mod X - Half-Life 1 Scripting and Administration\n\n\t40\t40\t80\nalliedmodders/sourcemod\n\nSourceMod - Source Engine Scripting and Administration\n\n\t40\t40\t80\nDoctorMcKay/node-steam-user\n\nAllows interaction with the Steam network via the Steam client protocol\n\n\t40\t40\t80\nFacepunch/Facepunch.Steamworks\n\nAnother fucking c# Steamworks implementation\n\n\t40\t40\t80\nJustArchiNET/ArchiSteamFarm\n\nC# application with primary purpose of farming Steam cards from multiple accounts simultaneously.\n\n\t40\t40\t80\nodota/core\n\nOpenDota: Open source Dota 2 data platform with automated replay parsing\n\n\t40\t40\t80\nodota/dotaconstants\n\ndotaconstants: Static data for Dota applications\n\n\t40\t40\t80\nodota/web\n\nOpenDota: React web UI for Dota 2 statistics using the OpenDota platform\n\n\t40\t40\t80\nsplewis/get5\n\nCS:GO Sourcemod plugin for competitive matches/scrims\n\n\t40\t40\t80\nSteamDatabase/FileDetectionRuleSets\n\n🔎 Rules to detect game engines and other technologies based on Steam depot file lists\n\n\t40\t40\t80\nSteamRE/SteamKit\n\nSteamKit2 is a .NET library designed to interoperate with Valve's Steam network. It aims to provide a simple, yet extensible, interface to perform various actions on the network.\n\n\t40\t40\t80\nValveSoftware/dxvk\n\ndxvk tree containing branches used by Proton\n\n\t40\t40\t80\nValveSoftware/GameNetworkingSockets\n\nReliable & unreliable messages over UDP. Robust message fragmentation & reassembly. P2P networking / NAT traversal. Encryption.\n\n\t40\t40\t80\nValveSoftware/gamescope\n\nSteamOS session compositing window manager\n\n\t40\t40\t80\nValveSoftware/Proton\n\nCompatibility tool for Steam Play based on Wine and additional components\n\n\t40\t40\t80\nValveSoftware/source-sdk-2013\n\nThe 2013 edition of the Source SDK\n\n\t40\t40\t80\nValveSoftware/wine\n\nWine with a bit of extra spice\n\n\t40\t40\t80\nValveSoftware/steam-devices\n\nList of devices Steam and SteamVR will want read/write permissions on, to help downstream distributions create udev rules/etc\n\n\t39\t40\t79\nValveSoftware/steam-audio\n\nSteam Audio\n\n\t38\t40\t78\nalliedmodders/metamod-source\n\nMetamod:Source - C++ Plugin Environment and Detour Library for the Source Engine\n\n\t37\t40\t77\nalliedmodders/sourcepawn\n\nA small, statically typed scripting language.\n\n\t35\t40\t75\nValveSoftware/Fossilize\n\nA serialization format for various persistent Vulkan object types.\n\n\t31\t40\t71\nrlabrecque/Steamworks.NET\n\nSteamworks wrapper for Unity / C#\n\n\t27\t40\t67\nModDota/moddota.github.io\n\nModDota github pages project.\n\n\t26\t40\t66\nodota/parser\n\nReplay parse server generating JSON log events from Dota 2 replay files\n\n\t26\t40\t66\nValveSoftware/steam-for-linux\n\nIssue tracking for the Steam for Linux beta client\n\n\t26\t40\t66\nSteamRE/DepotDownloader\n\nSteam depot downloader utilizing the SteamKit2 library.\n\n\t24\t40\t64\nJustArchiNET/ASF-ui\n\nThe official web interface for ASF\n\n\t23\t40\t63\nadvancedfx/advancedfx\n\nHalf-Life Advanced Effects (HLAE) is a tool to enrich content creation mainly for the Counter-Strike series.\n\n\t22\t40\t62\nalliedmodders/ambuild\n\nAlliedModders C++ Build System\n\n\t23\t39\t62\nSteamDatabase/BrowserExtension\n\n💻 SteamDB's extension for Steam websites\n\n\t21\t40\t61\nodota/mobile\n\nReact Native apps for viewing Dota 2 data on Android/iOS\n\n\t19\t40\t59\nValvePython/steam\n\n☁️ Python package for interacting with Steam\n\n\t18\t40\t58\nskadistats/clarity\n\nComically fast Dota 2, CSGO, CS2 and Deadlock replay parser written in Java.\n\n\t13\t40\t53\nSteamRE/open-steamworks\n\nOpen Steamworks is a set of reverse engineered headers for the Valve's Steam Client. More or less abandoned now that the Steamworks SDK is publically available.\n\n\t13\t40\t53\nValveSoftware/Source-1-Games\n\nSource 1 based games such as TF2 and Counter-Strike: Source\n\n\t13\t40\t53\nalliedmodders/hl2sdk\n\nHalf-Life 2 SDK Mirrors\n\n\t11\t40\t51\nSteamDatabase/steamdb.info-issues\n\n🚱 Issue tracker for the SteamDB website\n\n\t11\t40\t51\nCSGOFloat/inspect\n\nSource Code that Powers the CSFloat Inspect Link API\n\n\t10\t40\t50\nValveSoftware/SteamOS\n\nSteamOS community tracker\n\n\t10\t40\t50\nalliedmodders/source2mod\n\nExperimental\n\n\t40\t9\t49\nsmiley/steamapi\n\nAn unofficial object-oriented Python library for accessing the Steam Web API.\n\n\t9\t40\t49\nSteamDatabase/GameTracking\n\n🛢 Dumping things, so you don't have to\n\n\t8\t40\t48\nValveSoftware/counter-strike_rules_and_regs\n\nCS:GO\n\n\t7\t40\t47\nValveSoftware/openvr\n\nOpenVR SDK\n\n\t6\t40\t46\nSteamDatabase/easy-markdown-editor\n\nEasyMDE: A simple, beautiful, and embeddable JavaScript Markdown editor. Delightful editing for beginners and experts alike. Features built-in autosaving and spell checking.\n\n\t40\t4\t44\nValveSoftware/Dota-2\n\nTracker for issues specific to Linux and Mac in the Reborn client. If you have a general issue or non-system-specific feature request please go to dev.dota2.com\n\n\t6\t38\t44\nValveSoftware/Dota2-Gameplay\n\nPublic Bug Tracker for Dota 2\n\n\t4\t40\t44\nJustArchiNET/ArchiBot\n\nNo description in the capture.\n\n\t16\t27\t43\nztizzlegaming/CSGOWinBig\n\nOpen-source Counter-Strike: Global Offensive jackpot betting website.\n\n\t1\t40\t41\nJustArchiNET/mantis.justarchi.net\n\nMantis Bug Tracker (MantisBT)\n\n\t40\t0\t40\nodota/node-steam-user\n\nAllows interaction with the Steam network via the Steam client protocol\n\n\t40\t0\t40\nModDota/TypeScriptAddonTemplate\n\nDota 2 addon template with TypeScript Panorama and VScripts.\n\n\t9\t29\t38\nValvePython/vdf\n\n📜 Package for working with Valve's text and binary KeyValue format\n\n\t6\t32\t38\nalliedmodders/amtl\n\nAlliedModders C++ Template Library\n\n\t17\t19\t36\nValvePython/dota2\n\n🐸 Python package for interacting with Dota 2 Game Coordinator\n\n\t5\t30\t35\nalliedmodders/stripper-source\n\nStripper:Source\n\n\t13\t21\t34\nAllyans3/steam-market-api-v2\n\nSteam Market API v2 package\n\n\t3\t31\t34\nModDota/dota-tutorial\n\nCustom game DOTA tutorial.\n\n\t11\t23\t34\nodota/blog\n\nNo description in the capture.\n\n\t29\t3\t32\nOpsecGuy/BetterGo\n\nExternal CS:GO cheat written in python.\n\n\t1\t27\t28\npxvr-official/1\n\n無許諾配信 企業理念剽窃 動物の森収益化 大神ミオ権利者削除 戌神権利侵害発言 常闇トワ炎上 夜空メルストーカー被害 建築王サポーター放置 赤十字マーク 魔乃アロエ卒業 一つの中國支持声明 大空昴3Dライブ 無限延期清掃員職業差別 日清コラボ楽曲 musedash非公開 rog案件取り消し 壁画ライブ 丁真 Ding Zhen 郑爽 Zheng Shuang 防护林 与朵小天使w 伊月猫凛 本主萌埋午休傻 汪峰 重生细胞 壁纸 比利海灵顿 香蕉君 van 田所浩二 抽象带篮子 抗压背锅吧 季子越 蒋明辉 傻逼…\n\n\t0\t28\t28\nRevadike/InternalSteamWebAPI\n\nDocumenting the unofficial and internal Steam Web API\n\n\t1\t27\t28\nJoeSzymkowiczFiveM/qb-lootcrate\n\nA CSGO-style case opening script\n\n\t2\t25\t27\nAbrarKL/MyRoulette.XYZ\n\nCSGO / Steam Roulette Site created with PHP and Node JS, using the Material Design front-end framework.\n\n\t1\t25\t26\nJustArchiNET/ASF-WebConfigGenerator\n\nNo description in the capture.\n\n\t10\t15\t25\nModDota/dota-data\n\nAuto-generated Dota 2 resource dumps\n\n\t11\t14\t25\nModDota/TypeScriptDeclarations\n\nTypeScript declarations for Dota 2.\n\n\t11\t14\t25\nModDota/API\n\nNo description in the capture.\n\n\t12\t12\t24\nalliedmodders/cssdm\n\nCounter-Strike:Source Deathmatch\n\n\t10\t13\t23\nSteamDatabase/steamstat.us\n\n✅ Front-end of Steam services status website\n\n\t4\t18\t22\nc0deina/csgojackpotV2\n\nCSGO Jackpot Source\n\n\t1\t20\t21\nValvePython/steamctl\n\n🤸 Take control of Steam from your terminal\n\n\t2\t19\t21\nValvePython/csgo\n\n🔫 Python package for interacting with CS:GO Game Coordinator\n\n\t3\t17\t20\nBeepIsla/csgo-crash-exploit\n\nAllows you to crash any Windows user\n\n\t3\t16\t19\nValvePython/vpk\n\n📦 Open, Search, Extract and Create VPKs in python\n\n\t4\t15\t19\nalliedmodders/SM-SteamWorks\n\nExposing SteamWorks functions to SourcePawn.\n\n\t14\t3\t17\nSteamRE/Steam4NET\n\nSteam4NET is a .NET wrapper around the Steamworks C++ interfaces\n\n\t2\t15\t17\nalliedmodders/hl2sdk-manifests\n\nInformation about HL2SDKs shared between Metamod:Source and SourceMod.\n\n\t6\t10\t16\nJustArchiNET/ASF-PluginTemplate\n\nTemplate repository that you can use for creating custom plugins for ArchiSteamFarm.\n\n\t8\t7\t15\nModDota/Dota2AIFramework\n\nGeneral Framework for Dota 2 AI Competitions\n\n\t1\t14\t15\nShkyyl/KeyChamp\n\nExtension for joining free case battle on key-drop automatically\n\n\t1\t14\t15\nSteamDatabase/SteamMonitor\n\n😤 Track Steam's connection manager servers status\n\n\t2\t12\t14\nBaterka/cslore.com\n\nCS:GO gambling site - csgo.style\n\n\t1\t12\t13\nSteamDatabase/SteamTokenDumper\n\n🔢 Submit users' PICS access tokens to SteamDB\n\n\t2\t11\t13\nmonoblocker/roulette\n\nRoulette CS:GO made in React and Typescript\n\n\t1\t11\t12\nzsith/launcher.user.js\n\n// ==UserScript== // @name AposLauncher // @namespace AposLauncher // @include http://agar.io/* // @version 3.062 // @grant none // @author http://www.twitch.tv/apostolique // ==/UserScript== var aposLauncherVersion = 3.062; Nu…\n\n\t1\t11\t12\nLincolnIT/CSGODouble-bot-automated\n\nCSGODouble Automated, auto Betting Bot.\n\n\t1\t10\t11\nvladpuz/steam-market\n\nSteam market API client\n\n\t4\t7\t11\nmcgrizzz/Cstrike.bet\n\nCSGO Roulette Website Angular frontend, nodejs backend, and steam trading bots\n\n\t1\t9\t10\nodota/underlords-web\n\nUI for OpenUnderlords\n\n\t5\t5\t10\nSteamDatabase/SteamToTwitter\n\n🕊 Tweets announcements from various Steam groups\n\n\t1\t9\t10\nModDota/AbilityLuaSpellLibrary\n\nThe successor to the Spell Library by Pizzalol\n\n\t4\t4\t8\nalvinl/bitskins\n\nUnofficial BitSkins API client\n\n\t2\t5\t7\nb1naryth1ef/steamy\n\nA Python Steam community and market API interface that will get you all hot and bothered\n\n\t2\t5\t7\nkratos1812/Case-Opening\n\nIn-game case opening system for CSGO servers.\n\n\t2\t5\t7\nodota/docs\n\nOpenDota API documentation\n\n\t4\t3\t7\nSteamDatabase/steam-advanced-access-fetch-players\n\n📈 Simple script to fetch Steam player count\n\n\t1\t6\t7\nTheRioMiner/CsgoBetterExternalRaytrace\n\nOverridden maps pack for better external raytrace\n\n\t1\t6\t7\nalliedmodders/hl2sdk-mock\n\nMock HL2SDK and Server\n\n\t5\t1\t6\nchristophersu/PySteamMarket\n\nPython API for getting prices from the Steam market.\n\n\t1\t5\t6\nExtremelyd1/Strat-Roulette\n\nCS:GO Sourcemod Plugin\n\n\t2\t4\t6\ngiovanni-orciuolo/double-sdk\n\nA simple way to write CS:GO cheats!\n\n\t2\t4\t6\nJustArchiNET/Madness\n\nMadness embraces your project by including compatibility layer for selected APIs normally not available on .NET Framework target.\n\n\t5\t1\t6\nModDota/TypescriptPanoramaDeclarations\n\nNo description in the capture.\n\n\t4\t2\t6\nodota/rapier\n\nA JavaScript Dota 2 (Source 2) replay parsing library\n\n\t1\t5\t6\nVozn1akHero/CSGOCaseOpeningSimulator\n\nCounter-Strike case opening simulator which resembles the good old CS:GO user interface\n\n\t3\t3\t6\nautarc/steam-store\n\nAPI client for the unofficial steam storefront/big picture resource\n\n\t2\t3\t5\nBETTING-CODE/awesome-esports-sites\n\nA curated list of awesome esport betting sites – live, statistics and other resources.\n\n\t1\t4\t5\njonteohr/Better-Warden\n\nAn improved and more advanced warden plugin with a custom menu for CS:GO jailbreak servers!\n\n\t2\t3\t5\nLudzikk/CSGO-Gambling-Site\n\nhttps://ludzikk.github.io/CSGO-Gambling-Site/\n\n\t1\t4\t5\nModDota/find-steam-app\n\nFind location of an installed Steam app\n\n\t3\t2\t5\nmprey/csgocact.us\n\nsource code for csgocact.us\n\n\t1\t4\t5\nnezu-cc/ServerCrasher\n\nCS:GO Server Crasher\n\n\t1\t4\t5\nodota/testfiles\n\nStores test replay files\n\n\t2\t3\t5\nodota/underlordsconstants\n\nConstant data for Dota Underlords\n\n\t3\t2\t5\nSnaBe/node-steam-market-fetcher\n\nA Node.js wrapper for the Steam Community Market API.\n\n\t2\t3\t5\nSteamDatabase/.github\n\n💗 Organization-wide community health files\n\n\t1\t4\t5\nwolfcon/RIP-HLTV-BET\n\nRIP BET AD (For Tampermonkey) https://greasyfork.org/en/scripts/423484-rip-hltv-bet\n\n\t2\t3\t5\nalliedmodders/blaster.net\n\nSource and GoldSrc Query Tool\n\n\t2\t2\t4\ncatears124/CS2-Price-API\n\nsimple python cs2 steam market price API\n\n\t1\t3\t4\nialakey/caseforge\n\nOpen-source CS2 case-opening platform: Steam auth, provably fair openings, RTP-balanced case builder, withdrawals bought on market.csgo.com and an admin CRM.\n\n\t1\t3\t4\nIlusion9/csgo-fix-mapchange-crash-sm\n\nFix players crash on map change.\n\n\t1\t3\t4\nismail0234/Benson-Map-Crash-Fixer\n\nCSGO Map Change Client Crash Fixer\n\n\t1\t3\t4\njaxwilko/steam-market-api\n\nPHP - Composer Compatible - Steam Market API\n\n\t2\t2\t4\nJustArchiNET/ArchiTag\n\nArchiTag is a very small utility based on Python 3 and Mutagen to provide missing functionality in opusenc of writing specific Opus metadata, such as total number of tracks or track number.\n\n\t1\t3\t4\nModDota/DotaUI\n\nNo description in the capture.\n\n\t2\t2\t4\nnode-steam/market-pricing\n\nWrapper for the unofficial Steam Market Pricing API\n\n\t1\t3\t4\nodota/media\n\nStores media files for Dota projects\n\n\t2\t2\t4\nSergeyIvanovDevelop/Crypto-Steam-Platform\n\nThe repository contains the code and configuration to run a platform for creating cryptocurrency stakes for arbitrary ERC20 tokens.\n\n\t1\t3\t4\nAareksio/csgodouble-floatchecker\n\nAdds context menu option to check item's float value\n\n\t1\t2\t3\nchinm4/CSGOdrop\n\nA online csgo gambling casino that includes a variety of mini games that allows you to win csgo skins\n\n\t2\t1\t3\nCruze03/CSGO-Case-Opening-Prank\n\nCommand:- !prank (Admin flag \"n\" required)\n\n\t1\t2\t3\nDhruva-Kapadia/CSGOTrollGG\n\nCSGO Case Opening Simulator\n\n\t2\t1\t3\nErhanCSGO/CSGOPolygon-prediction\n\nCSGOPolygon.com - prediction script, double your coins by using this tool\n\n\t1\t2\t3\nEv-Hoang/Bedrock-Chest-Case-Opening\n\nHypixel Skyblock Dungeon Mod - Bedrock Chest Opening Animation (CSGO Style)\n\n\t1\t2\t3\njmjp/csgo-roulette\n\nA csgo gambling roulette make with VueJS 3\n\n\t2\t1\t3\nJustArchiNET/ArchiCrowdin\n\nNo description in the capture.\n\n\t1\t2\t3\nLeonSK/WearMarketInspector\n\nRetrieve Wear Value (Float Value) and Pattern Index from Steam Community Market using http://csgo.exchange API\n\n\t1\t2\t3\nmaximgeerinck/csgo-gamble\n\nCSGO gambling website\n\n\t1\t2\t3\nModDota/BugTracker\n\nListing bugs for Dota 2 Custom Games\n\n\t2\t1\t3\nplwp/mma-betting\n\nUFC/MMA betting model with Pinnacle steam detection for AU book latency arb\n\n\t2\t1\t3\nSouthsideswag16/Csgo-Gambling-Site\n\nNo description in the capture.\n\n\t2\t1\t3\ntacyarg/csgofiesta-frontend-react\n\nRemastered version a the long time favorite csgo site\n\n\t2\t1\t3\nVelorasse/Mutah-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-csmoney-csgoskins\n\ngambling script for Mutah, Keydrop, csmoney, and csgoskins, featuring hacks, cheats, and predictors. Offers strategies to boost winning odds and optimize performance on these platforms.\n\n\t3\t0\t3\nalliedmodders/am-github-artifact-webhook\n\nNo description in the capture.\n\n\t2\t0\t2\ncharamza/roulette\n\nCSGO like roulette in JS\n\n\t1\t1\t2\nCruze03/CSGO-PugSetup-RoundRestore\n\nSometimes (player dropped/crashed) which would be disadvantage for a team. It would be very handy to restore the match to the previous round.\n\n\t1\t1\t2\ncsgorol/CSGO-ROLL-Crash-Predictor\n\nCSGO-ROLL-Crash-Predictor\n\n\t1\t1\t2\nFoxSerito/FOXWORLD_plugin_DoubleJump_CSGO\n\nПлагин SourceMod (CSGO). Двойной прыжок с эффектом.\n\n\t1\t1\t2\nhkehayovmoonbiz/CS2-Casino-Full-Source-Code\n\nCS2, CS2 betting platforms, Skin Roulette, Case Unboxing, Crash games, Jackpot, purchase CS2 casino source, crypto gambling\n\n\t1\t1\t2\nJustZakary/steamstoreapi\n\nThis NPM module is a API wrapper that makes the steam unofficial API easier to use.\n\n\t2\t0\t2\njzimr/steam-market-api\n\nA java library to easily get Steam Community Market data\n\n\t1\t1\t2\nMomohime/CSGO.Network-Jackpot-Coinflip\n\nNo description in the capture.\n\n\t1\t1\t2\nnnjjswat/moneybot\n\nautomated bots for bustabit (formerly known as moneypot), csgo crash, etc\n\n\t0\t2\t2\nodota/carry\n\nLegacy Application for donations to the OpenDota project\n\n\t1\t1\t2\nodota/PublicMatchDataBot\n\nA Discord bot to remind users to turn on Expose Public Match Data in the Dota 2 client\n\n\t1\t1\t2\nOrillio/CSGOBet.com\n\nCSGO roulette web app\n\n\t2\t0\t2\nripexz/csgo-bet-alert\n\nA Chrome extension to keep track of active CS:GO Lounge matches.\n\n\t1\t1\t2\nrrpvm/lumen_sense-beta-deprecated-\n\nthis is internal csgo cheat written by me(no paste, self reverse structures). start : ~6 August 2020, end : ~ 14 December 2020\n\n\t1\t1\t2\nRuthless222/csgoscore\n\nThis is a Counter Strike Global Offensive Betting Site. You chose the skins you want to bet and try to win jackpots\n\n\t2\t0\t2\ntfburns/CSGO-cases-PL\n\nExpected profit-loss of CS:GO case openings\n\n\t1\t1\t2\nTomDra/CSGO-Case-Data-Analysis\n\nWorks out the most profitable CS:GO case at that current time\n\n\t1\t1\t2\nValvePython/dota2-wrappers\n\nNo description in the capture.\n\n\t1\t1\t2\nValvePython/teamfortress2-closed-captions\n\nThis project aims to provide a set of closed captions for Team Fortress 2\n\n\t1\t1\t2\nVistaNetGTX/Cstrike.bet-\n\nCSGO Roulette Website Angular frontend, nodejs backend, and steam trading bots\n\n\t1\t1\t2\nwafflas/csgo-case-opening-simulator\n\nI created a cs go case opening simulator for a meme coin\n\n\t0\t2\t2\nAdmiral-Enigma/Le_Coinflip\n\nConflip game\n\n\t1\t0\t1\nadryeljuliao/roulette-csgo\n\nNo description in the capture.\n\n\t1\t0\t1\nAndreuTheG/csgo-coinflip-web\n\nCSGO Gambling Coinflip Website\n\n\t1\t0\t1\nasmilen/csgoDouble\n\na b c\n\n\t1\t0\t1\nb1naryth1ef/csgofort\n\nA CSGO portal for trading, betting, analytics, and more!\n\n\t1\t0\t1\nBaterka/PrivateSteamBettingWebsite2024\n\nPrivate Steam (Counter-Strike 2) betting/gambling website - Roulette, Jackpot\n\n\t1\t0\t1\nblackcaer/SteamTradeHandler\n\nAutomation of Steam trading. Helper project for bet automation.\n\n\t1\t0\t1\nBTheCoderr/theRounders\n\nThe Rounders - A professional-grade sports betting analytics platform combining real-time odds tracking, sharp movement detection, and advanced statistical analysis. Features include line shopping, steam move alerts, power rankings, and comprehensive bet t…\n\n\t1\t0\t1\nCallumHemsley/KazeBot\n\nA Twitch chat betting bot for CSGO, simply bet a certain amount of points, and double if you win, lose all if you lose. Simple.\n\n\t1\t0\t1\nchrisjpm/CSGOJackpotTemplate\n\nFront end for a jackpot site\n\n\t1\t0\t1\ncolinsenner/valve-bug-bounty\n\nFor many years CS:GO, Dota 2, and Team Fortress 2 servers had a bug that allowed malicious users to leak crucial server process memory or reliably crash any server.\n\n\t1\t0\t1\ncoryypeters/nrl-odds-intelligence-pipeline\n\nReal-time sports betting odds intelligence — streaming pipeline that detects line movement, steam, and arbitrage across bookmakers. Python · Redis Streams · FastAPI · React.\n\n\t1\t0\t1\ndeissh/dev-csgoduo\n\nCS:GO. Bot for receiving things on the site (Polygon, Duo, Double and etc).\n\n\t1\t0\t1\ndom1torii/even-better-font-manager\n\nSimply even better cross-platform tool for CS2 Font Management\n\n\t1\t0\t1\nDONnicov/CSGO-crash-black-screen-\n\nsolution csgo crash black screen and close csgo\n\n\t1\t0\t1\nDoubleBoters/CsgoDouble\n\nNo description in the capture.\n\n\t1\t0\t1\ndownarowiczd/DoubleBot\n\nAn old CSGO Double Bot written for my friend. - 07.05.2016\n\n\t1\t0\t1\nErayBahar/steammarketscraper\n\nSteam Market Scraper Python-based tool that tracks real-time CS2 skin prices using Steam's hidden API. It fetches the lowest sell and highest buy offers for any item, helping you monitor deals or snipe underpriced listings automatically.\n\n\t1\t0\t1\nfairydarkness/SteamwebmailAPI\n\nUnofficial Python API for steamwebmail.com Fast, lightweight, and browserless library for automating steamwebmail.com. Support for session management, proxy, folder navigation, and message retrieval\n\n\t1\t0\t1\nFAQU2/CSGO-Coinflip-MyJailShop\n\nSourcemod plugin which provides a Coinflip system for MyJailShop.\n\n\t1\t0\t1\nFlamesONE/csgo-case-opening\n\nNo description in the capture.\n\n\t1\t0\t1\nFunnyRain/csgorun-crash-watch\n\n🚀 CsgoRun dump crash. / 🚀 CsgoRun дамп крашей.\n\n\t1\t0\t1\ngeohdgio/Venatus-Autenticator\n\nეს არის Steam Autenticator ქართული Venatus Trade & Betting ისთვის და Valve News Georgia-სთვის.\n\n\t1\t0\t1\nhakanstarlord/steam-bot\n\nSports betting steam-move signal detection with ML pipeline (XGBoost stacking + isotonic calibration), backtesting engine, Flask dashboard, and Telegram alerts.\n\n\t1\t0\t1\nHvH-gg/CSGO-Item-CrashFix\n\nA plugin for Counter-Strike: Global Offensive that fixes an exploit where receiving CS2 Items will cause CS:GO clients to crash\n\n\t1\t0\t1\nHvH-gg/CSGO-NetMsg-CrashFix\n\nA plugin for Counter-Strike: Global Offensive that fixes an exploit where spamming NetMsg_StringCmd packets would result in a server crash.\n\n\t1\t0\t1\nisybycnsmam/SteamLibrary\n\nLegacy Steam Unofficial API\n\n\t1\t0\t1\nItsTangerine/SteamApis.Net\n\nUnofficial https://steamapis.com .NET library, supporting .NET 6.0+\n\n\t1\t0\t1\nJustArchiNET/JustArchi.net\n\nNo description in the capture.\n\n\t1\t0\t1\nkiri-osint/CS2-Info-Hub-Bot\n\nA Telegram bot that acts as a hub for CS2 players, providing real-time skin prices, server stats, and user profile/inventory inspection using official and unofficial Steam APIs.\n\n\t1\t0\t1\nKoshkaj/monte\n\nGamified csgo gambling platform implementation\n\n\t1\t0\t1\nmadsab/CaseOpening\n\nA school project using Java. Simulating the case opening from CSGO and more.\n\n\t1\t0\t1\nman90es/steamcardexchange-api\n\nSteamCardExchange.net unofficial REST API server (scraper).\n\n\t1\t0\t1\nMattPua/steam-unofficial-docs\n\nUnofficial docs for Steam APIs with fumadocs\n\n\t1\t0\t1\nMetallist1/Portfolio.CsgoWinGambleProject\n\nA website that was done in 2017 September. Websites focus was on gambling with Counter-Strike items. Project was largely completed however backups were not done correctly, this resulted in half a year of wasted improvements to the code. The website was test…\n\n\t1\t0\t1\nmikebobadilla/csgo-jackpot\n\nNo description in the capture.\n\n\t0\t1\t1\nmikebobadilla/meteor-csgojackpot\n\nCssgo Jackpot done in meteor\n\n\t1\t0\t1\nModDota/D2VDump\n\nDota 2 Server VScript API Dumper\n\n\t1\t0\t1\nModDota/DotaTracking\n\nNo description in the capture.\n\n\t1\t0\t1\nModDota/eslint-config\n\nESLint config by ark120202\n\n\t1\t0\t1\nmr-codinglv/Casino-script\n\nscript casino - script betting - exchange script - bc casino - casino csgo - script bet - betwin script\n\n\t1\t0\t1\nMrKeelik/MrKeel\n\nCSGO DOUBLE BOT\n\n\t1\t0\t1\nnoahlatzel/CSGORollHelper\n\nLeveraging positive expected value on triple green jackpots on CSGORoll!\n\n\t1\t0\t1\noddsgpt/oddsgpt-market-intelligence\n\nResearch on football betting markets, closing odds, CLV, market efficiency, steam moves, AI betting systems, and sports market intelligence.\n\n\t1\t0\t1\noEXU/csgo-server-crasher\n\nCSGO SERVER CRASHER\n\n\t1\t0\t1\nPrdTTony/CSGO-Roulette\n\n[CSGO] Roulette System. Bet on RED or Black and win x2 credits\n\n\t1\t0\t1\nr-adamski/csgo-jackpot\n\nNo description in the capture.\n\n\t1\t0\t1\nSahotallo/Turan-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-Skinbaron-hellcase\n\ngambling script for Turan, Keydrop, Skinbaron, and Hellcase, providing hacks, cheats, and predictors. Includes strategies to improve winning chances and enhance gameplay on these platforms.\n\n\t1\t0\t1\nsamuelcsouza/steam-marketplace-api\n\nAn unofficial API to get data from the Steam Marketplace.\n\n\t1\t0\t1\nSKINSTRACK/CS2-Price-API\n\nSkinstrack offers a free, limited API endpoint that returns Steam item prices. Paid plans additionally provide access to pricing data from multiple marketplaces, making it possible to compare prices across different markets through a single API.\n\n\t1\t0\t1\nsnmtriet/CSGO-Casino-Full-Source-Code\n\nCSGO, CSGOEmpire, Case Opening, Case Battles, Roulette, Coinflip, buy csgo gambling site, gambling\n\n\t1\t0\t1\nSteamRE/homebrew-tools\n\nRepository for installation of SteamRE tools via Homebrew (http://brew.sh)\n\n\t1\t0\t1\nSteamRE/opensteamworks.org\n\nNo description in the capture.\n\n\t1\t0\t1\nTheQuack45/CsgoCaseOpenProgram\n\nSimple program to parse an XML file with CS:GO case information and \"simulate\" case openings\n\n\t1\t0\t1\nTLClassless/StratRouletteCSGO\n\nA 'Strat Roulette' web app for CS:GO!\n\n\t1\t0\t1\ntomasoom/csgoCaseOpening\n\nNo description in the capture.\n\n\t1\t0\t1\nvitaliy-evsyukov/steamgifts-autobet-bookmarklet\n\nbookmarklet for automatic bets on steamgifts.com\n\n\t1\t0\t1\nXpravdaX/RouletteCSGO\n\nNo description in the capture.\n\n\t1\t0\t1\nYuiKasumii/steam_api_unofficial\n\nUnofficial Steam Game Information Database\n\n\t1\t0\t1\nZexuz/Steam-Betting\n\nA betting website build ontop of STEAM's ecosystem\n\n\t1\t0\t1\nANK-RULZZ/steam-jackpot-site\n\ngetting some errors and would like some one to help me with it thank you!!!\n\n\t0\t0\t0\nasmilen/CsgoDoubleVS\n\nNo description in the capture.\n\n\t0\t0\t0\nCORNOODOSADAS/CSGOWeed\n\nCsgo Jackpot and Coinflip\n\n\t0\t0\t0\nCSGOApple/csgoapple\n\nJackpot Site\n\n\t0\t0\t0\nCSGOFAST/csgofast-api\n\nNo description in the capture.\n\n\t0\t0\t0\nDonakall/csgoDoublebot\n\nAutomated bot for csgodouble\n\n\t0\t0\t0\nfedor-selivanov/csgo-fast-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nfoldageros/csgod\n\ndouble bot\n\n\t0\t0\t0\ngmod-gambling/gmod-gambling\n\nNo description in the capture.\n\n\t0\t0\t0\nierome/CSGOBoss-BackEnd\n\nBack end version of CSGOBoss. This was a CSGO Gambling site named CSGOBoss. Coded by an old friend of mine Dahquan Hinds (https://github.com/dahquan/) Thought I would release this to help out any one who would need it.\n\n\t0\t0\t0\njamienp1/CSGODOUBLE-BOT-AUTO\n\ni got a bot thats is betting on the last winning color except from green and if you lose it will double the coins you set it to bet, pretty good, so when there comes a loooong train you will be gaining a bit of money codepaste_net/ugmt92 remove all the _ an…\n\n\t0\t0\t0\nJEYONER/CSGOTOXIC\n\nPAGINA DE JACKPOT CSGO SKINS\n\n\t0\t0\t0\nkalrish/csgo-jackpot\n\nStressful but funny zombie-like Counter-Strike: Global Offensive game mode.\n\n\t0\t0\t0\nkrys12345/roulettee\n\n// ==UserScript== // @name CSGO Predict Bot // @namespace http://csgodouble.com // @version 1.0 // @description predicts what number its gonna be // @author Meee // @match http://www.csgodouble.com/ // @grant none // ==/…\n\n\t0\t0\t0\nLilDuggiMuffi/CSGODouble-Working-Bot\n\nFixed CSGO Double Bot\n\n\t0\t0\t0\nLyricLy/Steam2Proton\n\nCheck if all your Steam games will work with Proton! Uses the official Steam API and the unofficial Proton API.\n\n\t0\t0\t0\nM0NsTeR77/csgo-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nozanhalis/Hi\n\n// ==UserScript== // @name CS GO LOUNGE BOT-Ozan Halis // @namespace http://csgolounge.com/ // @version 0.6.6 // @description Cs Go Lounge Hızlı BOT // @match http://csgolounge.com/* // @match http://dota2lounge.com/* // @updateURL h…\n\n\t0\t0\t0\nscoobertus/CSGO-DoubleBot\n\nNo description in the capture.\n\n\t0\t0\t0\nTradeal/CSGO-Jackpot-Bot\n\nNo description in the capture.\n\n\t0\t0\t0\nValvePython/artifact\n\nNo description in the capture.\n\n\t0\t0\t0\nVampire/CSGO-Roulette-Bot\n\nNo description in the capture.\n\n\t0\t0\t0\nvdemans/csgo-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nVocoreVideo/CSGODungeon-\n\nCSGO Jackpot\n\n\t0\t0\t0\nwayz-dev/csgofloat\n\nNo description in the capture.\n\n\t0\t0\t0\n\nAnlık Görüntü: 17 Eylül 2026, 11:19:11 kaynakta belirtildiği şekliyle; saat dilimi belirtilmemiştir. İhracatta ilişki koleksiyonu sınırlandırılmıştır (birçok kategori 40 adresinde son bulmaktadır). Katkıda bulunanlar ve fork yapanların toplamı, 4,214 farklı profil–depo çifti üzerinden 4,554 rol girdisine ulaşmaktadır; bir profil her iki rolü de taşıyabilir. Sıfır, o kategoride hiçbir kaydın bulunmadığı anlamına gelir. Depo adları takma adlar veya büyük/küçük harf farklılıkları içerebilir; toplamlar, kaynağın sayım kurallarına göre hesaplanmıştır.\n\nKaynak kökeni\nTopladığınız dosyalardan oluşturulmuştur.\nDestek beyanı\n2323/reddit_scams_ultra/steam_support_tickets_MEGA.json · satır sayısı 45, 58, 107, 110, 294\nAğ anlık görüntüsü\nnetwork-repositories.csv · raw_data.json · overlaps.csv · summary.txt (manifest dosyasında eski kaynak yolları korunmuştur)\n\nManifest, kaynak yollarını, bayt boyutlarını, SHA-256 hash değerlerini ve seçilen kayıt konumlarını kaydeder. Ham kayıtlar, soruşturma kapsamında yapılan yorumlamadan ayrı tutulur.\n\nKaynak manifest dosyasını indir ↓",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam Uygulama Kanıtları — Destek Kayıtları ve Geliştirici Ağı"
          },
          {
            "level": 2,
            "id": null,
            "text": "Şikayeti okuyun.Kaynağı ek olarak ekleyin."
          },
          {
            "level": 3,
            "id": null,
            "text": "Permanent sanction & closed appeals"
          },
          {
            "level": 4,
            "id": null,
            "text": "Permanently banned Steam account without a clear explanation, need help!"
          },
          {
            "level": 3,
            "id": null,
            "text": "Account recovery & a reported $10,000 loss"
          },
          {
            "level": 4,
            "id": null,
            "text": "Got $10k stollen from steam inventory due to steam' support fault."
          },
          {
            "level": 3,
            "id": null,
            "text": "A reported $500+ loss & template replies"
          },
          {
            "level": 4,
            "id": null,
            "text": "Funds stolen through steam market. Disappointed with Steam response.(or lackthereof)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam Guard & an item-restoration refusal"
          },
          {
            "level": 4,
            "id": null,
            "text": "Many people are losing item via clicking links where steam guard is enabled and steam support doesn't not restore items."
          },
          {
            "level": 3,
            "id": null,
            "text": "Selective enforcement & an unexplained ban"
          },
          {
            "level": 4,
            "id": null,
            "text": "🚨 Steam Bans Without Reason and Ignores Its Community — What’s Going On?"
          },
          {
            "level": 2,
            "id": null,
            "text": "Kamu altyapısı.Geniş ölçekte kaydedildi."
          },
          {
            "level": 2,
            "id": null,
            "text": "Topladığınız dosyalardan oluşturulmuştur."
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/tr/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/tr/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/selected-support-records.json",
          "https://phishdestroy.io/steam_dossier/tr/investigation_part2.html#outsourcing-case",
          "https://www.reddit.com/r/ohnePixel/comments/1hahqx2/permanently_banned_steam_account_without_a_clear/",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://www.reddit.com/r/DotA2/comments/r55bd7/many_people_are_losing_item_via_clicking_links/",
          "https://www.reddit.com/r/SteamUncensored/comments/1kjt2fa/steam_bans_without_reason_and_ignores_its/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/network-repositories.csv",
          "https://github.com/alliedmodders/amxmodx",
          "https://github.com/alliedmodders/sourcemod",
          "https://github.com/DoctorMcKay/node-steam-user",
          "https://github.com/Facepunch/Facepunch.Steamworks",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://github.com/odota/core",
          "https://github.com/odota/dotaconstants",
          "https://github.com/odota/web",
          "https://github.com/splewis/get5",
          "https://github.com/SteamDatabase/FileDetectionRuleSets",
          "https://github.com/SteamRE/SteamKit",
          "https://github.com/ValveSoftware/dxvk",
          "https://github.com/ValveSoftware/GameNetworkingSockets",
          "https://github.com/ValveSoftware/gamescope",
          "https://github.com/ValveSoftware/Proton",
          "https://github.com/ValveSoftware/source-sdk-2013",
          "https://github.com/ValveSoftware/wine",
          "https://github.com/ValveSoftware/steam-devices",
          "https://github.com/ValveSoftware/steam-audio",
          "https://github.com/alliedmodders/metamod-source",
          "https://github.com/alliedmodders/sourcepawn",
          "https://github.com/ValveSoftware/Fossilize",
          "https://github.com/rlabrecque/Steamworks.NET",
          "https://github.com/ModDota/moddota.github.io",
          "https://github.com/odota/parser",
          "https://github.com/ValveSoftware/steam-for-linux",
          "https://github.com/SteamRE/DepotDownloader",
          "https://github.com/JustArchiNET/ASF-ui",
          "https://github.com/advancedfx/advancedfx",
          "https://github.com/alliedmodders/ambuild",
          "https://github.com/SteamDatabase/BrowserExtension",
          "https://github.com/odota/mobile",
          "https://github.com/ValvePython/steam",
          "https://github.com/skadistats/clarity",
          "https://github.com/SteamRE/open-steamworks",
          "https://github.com/ValveSoftware/Source-1-Games",
          "https://github.com/alliedmodders/hl2sdk",
          "https://github.com/SteamDatabase/steamdb.info-issues",
          "https://github.com/CSGOFloat/inspect",
          "https://github.com/ValveSoftware/SteamOS",
          "https://github.com/alliedmodders/source2mod",
          "https://github.com/smiley/steamapi",
          "https://github.com/SteamDatabase/GameTracking",
          "https://github.com/ValveSoftware/counter-strike_rules_and_regs",
          "https://github.com/ValveSoftware/openvr",
          "https://github.com/SteamDatabase/easy-markdown-editor",
          "https://github.com/ValveSoftware/Dota-2",
          "https://github.com/ValveSoftware/Dota2-Gameplay",
          "https://github.com/JustArchiNET/ArchiBot",
          "https://github.com/ztizzlegaming/CSGOWinBig",
          "https://github.com/JustArchiNET/mantis.justarchi.net",
          "https://github.com/odota/node-steam-user",
          "https://github.com/ModDota/TypeScriptAddonTemplate",
          "https://github.com/ValvePython/vdf",
          "https://github.com/alliedmodders/amtl",
          "https://github.com/ValvePython/dota2",
          "https://github.com/alliedmodders/stripper-source",
          "https://github.com/Allyans3/steam-market-api-v2",
          "https://github.com/ModDota/dota-tutorial",
          "https://github.com/odota/blog",
          "https://github.com/OpsecGuy/BetterGo",
          "https://github.com/pxvr-official/1",
          "https://github.com/Revadike/InternalSteamWebAPI",
          "https://github.com/JoeSzymkowiczFiveM/qb-lootcrate",
          "https://github.com/AbrarKL/MyRoulette.XYZ",
          "https://github.com/JustArchiNET/ASF-WebConfigGenerator",
          "https://github.com/ModDota/dota-data",
          "https://github.com/ModDota/TypeScriptDeclarations",
          "https://github.com/ModDota/API",
          "https://github.com/alliedmodders/cssdm",
          "https://github.com/SteamDatabase/steamstat.us",
          "https://github.com/c0deina/csgojackpotV2",
          "https://github.com/ValvePython/steamctl",
          "https://github.com/ValvePython/csgo",
          "https://github.com/BeepIsla/csgo-crash-exploit",
          "https://github.com/ValvePython/vpk",
          "https://github.com/alliedmodders/SM-SteamWorks",
          "https://github.com/SteamRE/Steam4NET",
          "https://github.com/alliedmodders/hl2sdk-manifests",
          "https://github.com/JustArchiNET/ASF-PluginTemplate",
          "https://github.com/ModDota/Dota2AIFramework",
          "https://github.com/Shkyyl/KeyChamp",
          "https://github.com/SteamDatabase/SteamMonitor",
          "https://github.com/Baterka/cslore.com",
          "https://github.com/SteamDatabase/SteamTokenDumper",
          "https://github.com/monoblocker/roulette",
          "https://github.com/zsith/launcher.user.js",
          "https://github.com/LincolnIT/CSGODouble-bot-automated",
          "https://github.com/vladpuz/steam-market",
          "https://github.com/mcgrizzz/Cstrike.bet",
          "https://github.com/odota/underlords-web",
          "https://github.com/SteamDatabase/SteamToTwitter",
          "https://github.com/ModDota/AbilityLuaSpellLibrary",
          "https://github.com/alvinl/bitskins",
          "https://github.com/b1naryth1ef/steamy",
          "https://github.com/kratos1812/Case-Opening",
          "https://github.com/odota/docs",
          "https://github.com/SteamDatabase/steam-advanced-access-fetch-players",
          "https://github.com/TheRioMiner/CsgoBetterExternalRaytrace",
          "https://github.com/alliedmodders/hl2sdk-mock",
          "https://github.com/christophersu/PySteamMarket",
          "https://github.com/Extremelyd1/Strat-Roulette",
          "https://github.com/giovanni-orciuolo/double-sdk",
          "https://github.com/JustArchiNET/Madness",
          "https://github.com/ModDota/TypescriptPanoramaDeclarations",
          "https://github.com/odota/rapier",
          "https://github.com/Vozn1akHero/CSGOCaseOpeningSimulator",
          "https://github.com/autarc/steam-store",
          "https://github.com/BETTING-CODE/awesome-esports-sites",
          "https://github.com/jonteohr/Better-Warden",
          "https://github.com/Ludzikk/CSGO-Gambling-Site",
          "https://github.com/ModDota/find-steam-app",
          "https://github.com/mprey/csgocact.us",
          "https://github.com/nezu-cc/ServerCrasher",
          "https://github.com/odota/testfiles",
          "https://github.com/odota/underlordsconstants",
          "https://github.com/SnaBe/node-steam-market-fetcher",
          "https://github.com/SteamDatabase/.github",
          "https://github.com/wolfcon/RIP-HLTV-BET",
          "https://github.com/alliedmodders/blaster.net",
          "https://github.com/catears124/CS2-Price-API",
          "https://github.com/ialakey/caseforge",
          "https://github.com/Ilusion9/csgo-fix-mapchange-crash-sm",
          "https://github.com/ismail0234/Benson-Map-Crash-Fixer",
          "https://github.com/jaxwilko/steam-market-api",
          "https://github.com/JustArchiNET/ArchiTag",
          "https://github.com/ModDota/DotaUI",
          "https://github.com/node-steam/market-pricing",
          "https://github.com/odota/media",
          "https://github.com/SergeyIvanovDevelop/Crypto-Steam-Platform",
          "https://github.com/Aareksio/csgodouble-floatchecker",
          "https://github.com/chinm4/CSGOdrop",
          "https://github.com/Cruze03/CSGO-Case-Opening-Prank",
          "https://github.com/Dhruva-Kapadia/CSGOTrollGG",
          "https://github.com/ErhanCSGO/CSGOPolygon-prediction",
          "https://github.com/Ev-Hoang/Bedrock-Chest-Case-Opening",
          "https://github.com/jmjp/csgo-roulette",
          "https://github.com/JustArchiNET/ArchiCrowdin",
          "https://github.com/LeonSK/WearMarketInspector",
          "https://github.com/maximgeerinck/csgo-gamble",
          "https://github.com/ModDota/BugTracker",
          "https://github.com/plwp/mma-betting",
          "https://github.com/Southsideswag16/Csgo-Gambling-Site",
          "https://github.com/tacyarg/csgofiesta-frontend-react",
          "https://github.com/Velorasse/Mutah-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-csmoney-csgoskins",
          "https://github.com/alliedmodders/am-github-artifact-webhook",
          "https://github.com/charamza/roulette",
          "https://github.com/Cruze03/CSGO-PugSetup-RoundRestore",
          "https://github.com/csgorol/CSGO-ROLL-Crash-Predictor",
          "https://github.com/FoxSerito/FOXWORLD_plugin_DoubleJump_CSGO",
          "https://github.com/hkehayovmoonbiz/CS2-Casino-Full-Source-Code",
          "https://github.com/JustZakary/steamstoreapi",
          "https://github.com/jzimr/steam-market-api",
          "https://github.com/Momohime/CSGO.Network-Jackpot-Coinflip",
          "https://github.com/nnjjswat/moneybot",
          "https://github.com/odota/carry",
          "https://github.com/odota/PublicMatchDataBot",
          "https://github.com/Orillio/CSGOBet.com",
          "https://github.com/ripexz/csgo-bet-alert",
          "https://github.com/rrpvm/lumen_sense-beta-deprecated-",
          "https://github.com/Ruthless222/csgoscore",
          "https://github.com/tfburns/CSGO-cases-PL",
          "https://github.com/TomDra/CSGO-Case-Data-Analysis",
          "https://github.com/ValvePython/dota2-wrappers",
          "https://github.com/ValvePython/teamfortress2-closed-captions",
          "https://github.com/VistaNetGTX/Cstrike.bet-",
          "https://github.com/wafflas/csgo-case-opening-simulator",
          "https://github.com/Admiral-Enigma/Le_Coinflip",
          "https://github.com/adryeljuliao/roulette-csgo",
          "https://github.com/AndreuTheG/csgo-coinflip-web",
          "https://github.com/asmilen/csgoDouble",
          "https://github.com/b1naryth1ef/csgofort",
          "https://github.com/Baterka/PrivateSteamBettingWebsite2024",
          "https://github.com/blackcaer/SteamTradeHandler",
          "https://github.com/BTheCoderr/theRounders",
          "https://github.com/CallumHemsley/KazeBot",
          "https://github.com/chrisjpm/CSGOJackpotTemplate",
          "https://github.com/colinsenner/valve-bug-bounty",
          "https://github.com/coryypeters/nrl-odds-intelligence-pipeline",
          "https://github.com/deissh/dev-csgoduo",
          "https://github.com/dom1torii/even-better-font-manager",
          "https://github.com/DONnicov/CSGO-crash-black-screen-",
          "https://github.com/DoubleBoters/CsgoDouble",
          "https://github.com/downarowiczd/DoubleBot",
          "https://github.com/ErayBahar/steammarketscraper",
          "https://github.com/fairydarkness/SteamwebmailAPI",
          "https://github.com/FAQU2/CSGO-Coinflip-MyJailShop",
          "https://github.com/FlamesONE/csgo-case-opening",
          "https://github.com/FunnyRain/csgorun-crash-watch",
          "https://github.com/geohdgio/Venatus-Autenticator",
          "https://github.com/hakanstarlord/steam-bot",
          "https://github.com/HvH-gg/CSGO-Item-CrashFix",
          "https://github.com/HvH-gg/CSGO-NetMsg-CrashFix",
          "https://github.com/isybycnsmam/SteamLibrary",
          "https://github.com/ItsTangerine/SteamApis.Net",
          "https://github.com/JustArchiNET/JustArchi.net",
          "https://github.com/kiri-osint/CS2-Info-Hub-Bot",
          "https://github.com/Koshkaj/monte",
          "https://github.com/madsab/CaseOpening",
          "https://github.com/man90es/steamcardexchange-api",
          "https://github.com/MattPua/steam-unofficial-docs",
          "https://github.com/Metallist1/Portfolio.CsgoWinGambleProject",
          "https://github.com/mikebobadilla/csgo-jackpot",
          "https://github.com/mikebobadilla/meteor-csgojackpot",
          "https://github.com/ModDota/D2VDump",
          "https://github.com/ModDota/DotaTracking",
          "https://github.com/ModDota/eslint-config",
          "https://github.com/mr-codinglv/Casino-script",
          "https://github.com/MrKeelik/MrKeel",
          "https://github.com/noahlatzel/CSGORollHelper",
          "https://github.com/oddsgpt/oddsgpt-market-intelligence",
          "https://github.com/oEXU/csgo-server-crasher",
          "https://github.com/PrdTTony/CSGO-Roulette",
          "https://github.com/r-adamski/csgo-jackpot",
          "https://github.com/Sahotallo/Turan-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-Skinbaron-hellcase",
          "https://github.com/samuelcsouza/steam-marketplace-api",
          "https://github.com/SKINSTRACK/CS2-Price-API",
          "https://github.com/snmtriet/CSGO-Casino-Full-Source-Code",
          "https://github.com/SteamRE/homebrew-tools",
          "https://github.com/SteamRE/opensteamworks.org",
          "https://github.com/TheQuack45/CsgoCaseOpenProgram",
          "https://github.com/TLClassless/StratRouletteCSGO",
          "https://github.com/tomasoom/csgoCaseOpening",
          "https://github.com/vitaliy-evsyukov/steamgifts-autobet-bookmarklet",
          "https://github.com/XpravdaX/RouletteCSGO",
          "https://github.com/YuiKasumii/steam_api_unofficial",
          "https://github.com/Zexuz/Steam-Betting",
          "https://github.com/ANK-RULZZ/steam-jackpot-site",
          "https://github.com/asmilen/CsgoDoubleVS",
          "https://github.com/CORNOODOSADAS/CSGOWeed",
          "https://github.com/CSGOApple/csgoapple",
          "https://github.com/CSGOFAST/csgofast-api",
          "https://github.com/Donakall/csgoDoublebot",
          "https://github.com/fedor-selivanov/csgo-fast-roulette",
          "https://github.com/foldageros/csgod",
          "https://github.com/gmod-gambling/gmod-gambling",
          "https://github.com/ierome/CSGOBoss-BackEnd",
          "https://github.com/jamienp1/CSGODOUBLE-BOT-AUTO",
          "https://github.com/JEYONER/CSGOTOXIC",
          "https://github.com/kalrish/csgo-jackpot",
          "https://github.com/krys12345/roulettee",
          "https://github.com/LilDuggiMuffi/CSGODouble-Working-Bot",
          "https://github.com/LyricLy/Steam2Proton",
          "https://github.com/M0NsTeR77/csgo-roulette",
          "https://github.com/ozanhalis/Hi",
          "https://github.com/scoobertus/CSGO-DoubleBot",
          "https://github.com/Tradeal/CSGO-Jackpot-Bot",
          "https://github.com/ValvePython/artifact",
          "https://github.com/Vampire/CSGO-Roulette-Bot",
          "https://github.com/vdemans/csgo-roulette",
          "https://github.com/VocoreVideo/CSGODungeon-",
          "https://github.com/wayz-dev/csgofloat",
          "https://phishdestroy.io/steam_dossier/output_steam_network/raw_data.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/enforcement-source-manifest.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/tr/steam_enforcement_evidence.content.json",
      "export_json_sha256": "c0f1670d90cc225bc52e50ad984ace3ad3cdda462dbe8bbaf16c7e0f4235c2d2"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "tr/steam_evidence_archive.html",
      "language": "tr",
      "title": "Kaynakları inceleyin — “Steam” Dosyası",
      "source_url": "https://phishdestroy.io/steam_dossier/tr/steam_evidence_archive",
      "source_html_sha256": "ccb4ec434d3517c95408dc1ea8fd7d29adb9bd676fb253e87f97ab1e512f9885",
      "exported_at": "2026-09-29T00:21:09.602Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "steam_evidence_archive.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/tr/steam_evidence_archive.pdf?v=print-20260929-v5",
        "sha256": "758e7b169591b4413569f6645f86c90d752ccc5a6dc839ed0391e778592333da",
        "bytes": 63648,
        "pages": 4
      },
      "integrity": {
        "signed_object": "steam_evidence_archive.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "steam_evidence_archive.content.json.asc",
        "digest_file": "steam_evidence_archive.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify steam_evidence_archive.content.json.asc steam_evidence_archive.content.json",
          "sha256sum -c steam_evidence_archive.content.json.sha256"
        ]
      },
      "content": {
        "text": "ARAŞTIRMA MALZEMELERİ / KAYNAK TOPLAMA 002\nSteam Kanıt Arşivi — 16,319 Kaynaklı Kayıtlar\n\nHer talep. Kaynağa geri dön.\n\nBU BÖLÜMÜN KANITLADIĞI ŞEY\n\nBu adli arşiv, 16,319 adresindeki birincil kaynak kayıtlarını —Valve Geliştirici Topluluğu belgeleri, GitHub adresindeki herkese açık sorun bildirimleri, doğrulanmış Trustpilot şikayetleri ve arşivlenmiş forum raporlarını kapsayan — kriptografik hash değerleri ve kaynak geçmişi günlükleriyle indekslemektedir. Arşiv, tekrarlanabilir platform güvenlik açıklarını, belgelenmemiş API kullanımdan kaldırma işlemlerini ve ele geçirilmiş hesaplarla ilgili sürekli tüketici şikayetlerini ortaya koyan, incelenebilir bir kanıt tabanı sunmaktadır.\n\n← Yönetici özetine geri dön\n\nBir iddianın ardındaki kaydı bulun. Kaynağa göre filtreleyin, tam metni açın ve orijinal bağlantıyı takip edin. Kaynak satırları birbiriyle çakışabilir; bir kayıt, doğrulanmış bir olay anlamına gelmez.\n\nSoruşturmaya geri dön ↗\n354TRUSTPILOT / KAYNAK SATIRLARI\n208REDDIT / KAYNAK SATIRLARI\n705GITHUB / KAYNAK SATIRLARI\n15,302ANA CSV / KAYNAK SATIRLARI\n16,319 KAYITLAR — PLATFORM TÜRÜNE GÖRE DAĞILIMI\n\nViki kategorisi “provenance” (7,620 kayıtları · 46.7%): Valve Geliştirici Topluluğu (developer.valvesoftware.com), SteamDB Belgeleri/SSS ve oyun topluluğu vikileri (Liquipedia CS/Dota ve Fandom Steam vikileri) kaynaklarından, Ağustos 2024 ile Eylül 2026. tarihleri arasında otomatik WARC anlık görüntüleri ve MediaWiki API uç noktaları aracılığıyla derlenmiştir. Tüm 7,620 girişleri, Ana CSV dışa aktarımına tamamen entegre edilmiştir (TOTAL_VALVE_SCANDALS_MASTER_DB.csv).\n\nWiki\n7,620\nReddit\n5,635\nGitHub\n2,395\nTrustpilot\n393\nWeb\n276\n9,116 16,319 kayıtlarının (55.8%) bir kısmı Steam / Valve adreslerine referanslar içermektedir\n\nBu arama yapılabilen arşiv, şu platform üzerine kurulmuştur: 2026-09-17 yukarıda listelenen kaynak dışa aktarımlarından. Dosyanın başka yerlerinde kullanılan ayrı “40,448-” satır ana dışa aktarımı farklı bir kapsamdadır. Bkz. manifest dosyasını oluştur Bu arşivin sayımları için; kayıtlar birbiriyle örtüşebilir ve her biri ayrı bir olay değildir.\n\nKAYNAK PLATFORMU\nKAYNAK TOPLAMA\nSteam / Valve'da bahsedilenler\nMetin eşleşmesi veya Valve deposuEksik / kaldırılmış metin\n16,569 kaynak satırları\n16,319 ayrı kayıtlar\n249 Yinelenen satırlar birleştirildi\n1 satır hariç\nOrijinal dosyaları görüntüleyin ↘\n★TRUSTPILOT2015-10-16#1RATING 1/5\n\nSteam is the biggest PC gaming platform without a doubt. A power which could be abused but Steam for the most part doesn't. Overall a definite download for any moden digital age PC gamer. It mu... See more\n\nMA · 7 source copies\n★TRUSTPILOT2021-06-18#2RATING 1/5\n\nThey scam people for money, dont believe me? Read this Source: Steam Subscribers/User Agreement NO GUARANTEES TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, NEITHER VALVE NOR ITS AFFILIA... See more\n\nWF · 7 source copies\n★TRUSTPILOT2016-10-28#3RATING 1/5\n\nSupport on site is terrible. Refunds not happend yet, despite games not working. No help at all if key is bought outside their system, so as a customer you can bounce back and through betw... See more\n\nPE · 7 source copies\n★TRUSTPILOT2021-09-27#4RATING 1/5\n\nThey are an amazing company!! My boyfriend paid for and downloaded a game without realizing it wasn’t the version he wanted. When he reached out, they gave him a full refund and responded in the same... See more\n\nVH · 7 source copies\n★TRUSTPILOT2026-07-20#5RATING 1/5\n\nI’ve used Steam for years, but lately, their sales have really lost their edge. I was hoping to score some solid discounts, but many games still feel overpriced, even during sales. Plus, the support response times can be frustratingly slow when issues arise.\n\nCR\n★TRUSTPILOT2025-12-10#6RATING 1/5\n\nI new here , but all my firends had great experience with this platform . They can make money\n\nZeinab Nematollahi\n★TRUSTPILOT2025-11-18#7RATING 1/5TEXT UNAVAILABLE\n\nNo text was included in the source record.\n\nEM\n★TRUSTPILOT2025-10-21#8RATING 1/5\n\nusing steam for over a decade and i have no words how good the platform is. some friends recommended it to me back in 2015 when we wanted to play csgo together and since then im loggin on it on a daily basis to check new games\n\nTrustpilot\n★TRUSTPILOT2025-05-09#9RATING 1/5\n\nSupport are never able to help you and only able to redicrect you to public linkBreaking there own TOSNot able to provider a refundNot able to provide a safe place for gamingBase on the game you play you can get scam.\n\nSym Link · 7 source copies\n★TRUSTPILOT2025-05-09#10RATING 1/5TEXT UNAVAILABLE\n\nNo text was included in the source record.\n\nHearnius\n★TRUSTPILOT2024-12-30#11RATING 1/5\n\nThis company allowed a single phishing scammer 76561199443342045 in 100's of its user community chat rooms \"Steam Chat\" the whole week of Winter Sales, 12-23-2024 - 2025 to spam spaceintrader a scam phishing website.Don't support Valve & Steam that support sca…\n\nFR · 7 source copies\n★TRUSTPILOT2024-11-15#12RATING 1/5\n\nVery realiable! Ive never had an issue over the 11 years ive had steam.\n\nJM\nDerleme ve kaynak dosyaları\n\nBu arşiv, 249 adresindeki yinelenen satırları birleştirir ve 16,569 adresindeki girdilerden bir satırı hariç tutarak 16,319 adresinde benzersiz kayıtlar bırakır. Bir kayıt, başka bir kayıtta zaten yer alan bir olayı tanımlayabilir. Arama, başlıkları, yazarları, kaynak etiketlerini ve görüntülenen alıntıları kapsar; her kayıtla birlikte kaydedilmiş metnin tamamı açılır.\n\nDört kaynak dosyasını indirin ↓Dosya sayısı ve SHA-256 hash değerleri ↗Orijinal derleme manifestosu ↗\n\nPaket, derlemenin satır sayılarıyla eşleşen kurtarılmış dışa aktarımları ve kaydedilmiş üç JSON yolunu içermektedir. Orijinal derlemede girdi hash’leri veya bir ana CSV yolu kaydedilmemişti; eşlik eden manifest dosyası, kurtarılan dosyaları ve yayınlanan dizinle yapılan karşılaştırmayı belgelemektedir.\n\nTrustpilot · steam_support_reviews.json354 satırlar · JSON olarak dışa aktarma\nReddit · reddit_censored_forensics.json208 satırlar · JSON olarak dışa aktarma\nGitHub · valve_ignored_bugs.json705 satırlar · JSON olarak dışa aktarma; dosya adı, bir toplayıcı etiketidir\nAna Veri Tabanı · TOTAL_VALVE_SCANDALS_MASTER_DB.csv15,302 satırlar · Karşılaştırma amacıyla kullanılan CSV dışa aktarımı\nMahkeme Dosyaları · UNSEALED_EXHIBITS_AND_AML_DOSSIER.mdWolfire’ın “Valve” davası kapsamında gizliliği kaldırılan e-postalar, Gabe Newell’in ifade kayıtları, Ekim 2019 AML itirafı\nÖnemli Bilgiler · FACTS_AND_CITATIONS_DATABASE.md1,638 35’deki antitröst ve güvenlik alanlarında doğrulanmış ayrı kaynak gösterimleri\nDestek Arşivi · support_canned_refusals.html1,505 bilet kayıtları · 137 adresinde saklanan ekran görüntüleri · Canlı anlık arama\nKayıt alanları, eksik metinler ve çakışan dışa aktarmalar\n\nTarihler, derecelendirmeler, kategoriler ve durum bilgileri kaynak dışa aktarımlarını aynen yansıtmaktadır. Eksik bir URL, eksik olarak kalır. “[kaldırıldı]” veya “[silindi]” işaretleri, bir gönderinin kim tarafından ve neden kaldırıldığını belirtmez. Steam / Valve filtresi, alaka düzeyi değerlendirmesi değil, metin eşleşmesidir.\n\n“Maçları dışa aktar” seçeneği, dizin girişlerini alıntılarla birlikte indirir; “Kaydı indir” seçeneği ise kaydedilmiş metnin tamamını içerir. Ayrı olan 40,448-satır başlığı CSV ve 1,690-GitHub satırı CSV Bu sürüm için önemli olan ihracatın kapsamıdır, kaynak sayısı değil.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam Kanıt Arşivi — 16,319 Kaynaklı Kayıtlar"
          },
          {
            "level": 2,
            "id": null,
            "text": "KAYNAK PLATFORMU"
          },
          {
            "level": 2,
            "id": null,
            "text": "Derleme ve kaynak dosyaları"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/tr/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/tr/",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/TOTAL_VALVE_SCANDALS_MASTER_DB.csv",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive_manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive-inputs.zip",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive-inputs-manifest.json",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/unsealed_legal_and_aml/UNSEALED_EXHIBITS_AND_AML_DOSSIER.md",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/forensic_facts_1000/FACTS_AND_CITATIONS_DATABASE.md",
          "https://phishdestroy.io/steam_dossier/tr/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/github_valve_unpatched_bugs.csv"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/tr/steam_evidence_archive.content.json",
      "export_json_sha256": "fd3f6580acdb3e5937bebc41217d1a07b56a2c08bed6f449ab5ec9da094aaf72"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "tr/support_canned_refusals.html",
      "language": "tr",
      "title": "Steam Destek Reddi ve Hazır Yanıtlar Arşivi — “Steam” Dosyası",
      "source_url": "https://phishdestroy.io/steam_dossier/tr/support_canned_refusals",
      "source_html_sha256": "5439080c3af214cfa07ea3849f612457c2baba550792b97ff7c7f5b7b353347e",
      "exported_at": "2026-09-29T00:21:11.826Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "support_canned_refusals.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/tr/support_canned_refusals.pdf?v=print-20260929-v5",
        "sha256": "e97a4c5fe869e0883eed7e3642644b4faaca42decef353c0866597b90ef8a107",
        "bytes": 62640,
        "pages": 2
      },
      "integrity": {
        "signed_object": "support_canned_refusals.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "support_canned_refusals.content.json.asc",
        "digest_file": "support_canned_refusals.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify support_canned_refusals.content.json.asc support_canned_refusals.content.json",
          "sha256sum -c support_canned_refusals.content.json.sha256"
        ]
      },
      "content": {
        "text": "BU BÖLÜMÜN KANITLADIĞI ŞEY\n\nBu depo, 137 adresinde saklanan birincil ekran görüntülerini ve 1,505 adresinde denetlenmiş mağdur itirazlarını içermekte olup, Valve adresindeki otomatik destek bileti işleme sürecini ayrıntılı olarak belgelemektedir. Bu belgeler, hesapların OpenID yönlendirmesi veya yetkisiz API anahtar oluşturma yoluyla ele geçirildiği durumlarda, Steam Destek ekibinin teknik inceleme yapmadan sistematik olarak standartlaştırılmış hazır red cevaplarını kullandığını kanıtlamaktadır. Platform, ürün geri yükleme taleplerini veya denetim izi bilgilerinin açıklanmasını kategorik olarak reddederek, yapısal kimlik doğrulama kusurlarının tüm sorumluluğunu ele geçirilen hesap sahiplerine yüklemektedir.\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\nTüm ekran görüntüleri, üçüncü taraflarca alınmış görüntülerdir. Telif hakkı ve içerik, ilgili yazarlara ve platformlara (Reddit kullanıcıları, Steam Topluluğu yazarları, Trustpilot yorumcuları, X ve YouTube içerik üreticileri) aittir. Bu görüntüler yalnızca tanımlama ve kamu yararına habercilik amacıyla yeniden yayınlanmaktadır; herhangi bir mülkiyet iddiasında bulunulmamaktadır. Her bir ek, kendi birincil kaynağına bağlantı içermektedir.\n\nFigures reported on the source page\nMeasure\tReported value\tScope\nKayıtlı Belgeler\t1505\tDoğrulanmış mağdur itirazları ve bilet konuları\nKaydedilmiş Ekran Görüntüleri\t137\tYerel olarak depolanan yüksek çözünürlüklü bilet görüntüleri\nGeri Kazanım Oranı\t0.0%\tAPI’daki önemli ticaret kaçırma olaylarında verilen bozma kararları\nŞablon Çoğaltma\t100%\tPersonel arasında (Ilya, Roger, Maverick) komut metinlerinin aynen kullanılması\nAdli Kanıt: Destek Reddinin Üç Temel Dayanağı\n01'İN TEMEL UNSURU · KABULEk R –014\nRoger’ın İtirafı: API MitM Doğrulandı\n\n1cp582i numaralı destek talebinde, Steam destek ekibinden \"Roger\", saldırganların API adresi üzerinden meşru işlemleri iptal edip bunları milisaniyeler içinde klon botlarla değiştirdiklerini yazılı olarak kabul etse de, eşyaları geri yüklemeyi reddederek mağdura \"yerel bir bilgisayar teknisyenine\" başvurmasını söylüyor.\n\nYazılı Kabul Belgesini İncele ↗\n02'İN TEMEL UNSURU · ESCALATIONEk R –012\n7-Gün İçi İşlem – Bekleme – Hareketsizlik\n\nBir mağdur, “7-” günlük ticaret askıya alma süresi sırasında hacker’ın hesaplarının SteamID64’lerini paylaştı. Destek ekibinden “Artem” ve “Ilya”, sanal öğelerin kıtlığını gerekçe göstererek çalınan öğeleri dondurmayı reddettiler ve bileti otomatik bir şablonla kapattılar.\n\nÇoklu Personel Transkriptini İnceleme ↗\nAYAK 03 · POLİTİKAEk R –002\nMülkiyet Hakları Konusundaki Piyasa Kıtlığı\n\nValve’ın resmi Eşya Geri Verme Politikası’nda, eşyaların geri verilmemesinin nedeninin, bunların geri verilmesinin “nadirliklerini azaltıp ekonomiyi şişirerek Topluluk Pazarı’ndaki eşyaların değerini düşüreceği” açıkça belirtilmektedir.\n\nPolitika Ekran Görüntüsünü İncele ↗\nTarihsel Köken · 22 Mart 2018 adresinden 2026 adresine\nEk H -003 · 8-Yıl Boyu Yama Uygulanmamış Saldırı Yüzeyi\nKaydedilen En Eski Ticaret İkamesi (22 Mart 2018)\n\nValve’ın Counter-Strike eşyaları için tartışmalı “7-” günlük ticaret kısıtlamasını uygulamaya koymasından tam bir hafta önce, ticaret topluluğu bu durumun ilk gerçek örneklerini keşfetti. Steam Web API Ticaret Yönlendirme Güvenlik Açığı. Saldırganlar, web oturumlarını ele geçirerek şu adreste yetkisiz bir API anahtarı oluşturdular: steamcommunity.com/dev/apikey 2'ın mobil uygulaması üzerinden FA onayı gerekmeden, botların işlemleri gerçek zamanlı olarak iptal etmesine ve değiştirmesine olanak tanır.\n\n2018'in Mart Ayı Kamu Duyurusu: \"Dolandırıcılar bu takas teklifini otomatik olarak tespit edebilir ve hesabınızda bu teklifi reddedebilirler; çünkü elinde Steam API anahtarınız var. Dolandırıcı bot şimdi size aynı görünümler için bir takas teklifi gönderecek... ve siz aradaki farkı fark etmeyeceksiniz!\"\nTarihi Kanıtlar Yolu\n22 2018: Mart API motor değişimi ile ilgili ilk kayıt\n2019: Destek, \"kötü amaçlı yazılım\" engelleme sürecini standartlaştırır\n2020: \"Yardım talebini kapatma\" komut dosyası güvenli hale getirildi\n2022–2026: BitB ve QR kodlu kimlik avı otomasyonu\n2018'daki orijinal Reddit başlığını aç ↗\nPrimary sources\n\n137 gallery cards refer to 78 distinct primary URLs. Images and repeated exhibit captions are omitted from this reading edition.\n\nFull visual archive and original captures",
        "headings": [
          {
            "level": 2,
            "id": null,
            "text": "Figures reported on the source page"
          },
          {
            "level": 2,
            "id": null,
            "text": "Adli Kanıt: Destek Reddinin Üç Temel Dayanağı"
          },
          {
            "level": 3,
            "id": null,
            "text": "Roger’ın İtirafı: API MitM Doğrulandı"
          },
          {
            "level": 3,
            "id": null,
            "text": "7-Gün İçi İşlem – Bekleme – Hareketsizlik"
          },
          {
            "level": 3,
            "id": null,
            "text": "Mülkiyet Hakları Konusundaki Piyasa Kıtlığı"
          },
          {
            "level": 3,
            "id": null,
            "text": "Kaydedilen En Eski Ticaret İkamesi (22 Mart 2018)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Primary sources"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/tr/#proxy-bypass-explainer",
          "https://www.reddit.com/r/csgo/comments/1cp582i/i_got_api_scammed_what_do_i_do_now/",
          "https://www.reddit.com/r/DotA2/comments/1e5ovy4/my_account_was_hacked_and_steam_support_refuse/",
          "https://www.reddit.com/r/Steam/comments/3b2abd/steam_will_no_longer_restore_scammed_items_item/",
          "https://www.reddit.com/r/GlobalOffensiveTrade/comments/863tk1/psa_urgent_huge_scam_happening_read_here_how_to",
          "https://phishdestroy.io/steam_dossier/tr/support_canned_refusals#gallery-grid"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/tr/support_canned_refusals.content.json",
      "export_json_sha256": "2df4392ef6bfd3f52b1cfc4531e2135535e645bcf9566a444812befad914e185"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "tr/valve_scandals_registry.html",
      "language": "tr",
      "title": "Valve Skandal Kayıt Defteri — “Steam” Dosyası",
      "source_url": "https://phishdestroy.io/steam_dossier/tr/valve_scandals_registry",
      "source_html_sha256": "cf3252612c4426e973db5ac1a8498b50a6078b7b539489012039a7f0561d6f4d",
      "exported_at": "2026-09-29T00:21:15.513Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "valve_scandals_registry.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/tr/valve_scandals_registry.pdf?v=print-20260929-v5",
        "sha256": "a035eff4fdade6bbe96f11216f035407c50205b3ccc6d7777cf3d4470500aa92",
        "bytes": 64268,
        "pages": 6
      },
      "integrity": {
        "signed_object": "valve_scandals_registry.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "valve_scandals_registry.content.json.asc",
        "digest_file": "valve_scandals_registry.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify valve_scandals_registry.content.json.asc valve_scandals_registry.content.json",
          "sha256sum -c valve_scandals_registry.content.json.sha256"
        ]
      },
      "content": {
        "text": "Skandal arşivi\nValve Skandallar Ana Kayıt Defteri — 160 Kaynaklı Olaylar\nKAYNAK KAYITLARI (HAM): 11,768\n\nBildirildi. Kaynağı belirlendi. Hâlâ açık.\n\nBU BÖLÜMÜN KANITLADIĞI ŞEY\n\nBu ana kayıt defteri, Valve ekosisteminde görülen kalıcı platform kusurlarını, kaldırılmış topluluk raporlarını ve çözülmemiş müşteri destek sorunlarını ayrıntılı olarak ele alan, bağımsız olarak doğrulanmış birincil kayıtları 160 adresinde bir araya getirmektedir. Doğrulanmış Trustpilot ihtilaf başvuruları, arşivlenmiş GitHub güvenlik sorunu biletleri ve düzenleyici kurumların işlemlerini kapsayan bu kayıt defteri, hesap kurtarma ve müşteri ihtilaflarının çözümünde tekrarlanan sistemik aksaklıkları ortaya koymaktadır.\n\n← Yönetici özetine geri dön\n\n160 toplanan kayıtlar: kullanıcılar tarafından değerlendirilen bir destek operasyonu, artık görünür olmayan tartışma dizileri, bildirildikten sonra ele alınmayan platform kusurları ve Valve’un halihazırda hesap vermek zorunda kaldığı olaylar. Buradaki hiçbir şey bizim yorumumuz değildir — her satırın kendi orijinal kaynağı mevcuttur. Birini açın ve kendiniz okuyun.\n\nKaynak Kayıtları\n11,768\nTüm kategoriler genelinde\nPlatformdaki Kusurlar\n3,372\nKullanıcılar tarafından bildirilen platform kusurları\nSansürlenmiş Konular\n109\nModeratör tarafından kaldırılan Reddit gönderileri\nDestek Şikayetleri\n471\nTrustpilot’ta doğrulanmış şikayetler\nUygulanabilirlik\nAuth-host etki alanı engelleme\n\nOpenID kimlik doğrulama sunucularının etki alanı düzeyinde engellenmesi, teknik açıdan uygulanması kolay bir işlemdir: Bir kaynak, Steam adresindeki oturum açma yönlendirmesinden engellendiğinde, aynı kaynak için kimlik doğrulama aracısı olarak görev yapan üçüncü taraf etki alanları da aynı kural seti ile filtrelenebilir. Uygulamanın uygulanabilirliğine ilişkin ayrıntılı bir inceleme, ana dosyada yer almaktadır.\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\nDosyadaki uygulama fizibilitesine bakın →\nKategori: Trustpilot Destek Şikayetleri (Filtrelenmiş Olumsuz Eskalasyonlar)176 eşleşen kaynak kayıtları · yinelenenler gizlenmiştir\nConsumer Complaint2026-07-20\nAuthor: C***\n\nI’ve used Steam for years, but lately, their sales have really lost their edge. I was hoping to score some solid discounts, but many games still feel overpriced, even during sales. Plus, the support response times can be frustratingly slow when issues arise.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2026-07-20\nConsumer Complaint2025-05-09\nAuthor: S*** L***\n\nSupport are never able to help you and only able to redicrect you to public linkBreaking there own TOSNot able to provider a refundNot able to provide a safe place for gamingBase on the game you play you can get scam.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2025-05-09\nConsumer Complaint2024-12-30\nAuthor: F***\n\nThis company allowed a single phishing scammer 7656…2045 in 100's of its user community chat rooms \"Steam Chat\" the whole week of Winter Sales, 12-23-2024 - 2025 to spam spaceintrader a scam phishing website.Don't support Valve & Steam that support scams. Don't give your log in credentials to account hijacking scammers. This company also allows engagements of commercial advertising / spam for gambling in violation of its own Rules and Guidelines / Online Conduct. 7656…5023 proof - groups/deskinsfans key drop advertising, thanks TannerfromKD and Valve!*\"The Consumer Review Fairness Act (CRFA) protects people’s ability to share their honest opinions about a business’s products, services, or conduct, in any forum, including social media. The law protects a broad variety of honest consumer assessments, including online reviews, social media posts, uploaded photos, videos, etc. And it doesn’t just cover product reviews. It also applies to consumer evaluations of a company\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2024-12-30\nConsumer Complaint2024-07-31\nAuthor: A***\n\nhorrible company.randomly you get \"This account may have been accessed by someone else.\"this happened to me 3 times.the 3rd time they wanted a cd key.a spent useless cd key that nobody has any reason to keep laying around.i gave them the paypal bill for my first purchase back in 2015.i gave them a bill for my first phone number ever on the account.i still got the same email attached to the account.this company is literally a scam. nothing but a scam.they randomly claim you been accessed somewhere else and then require you to give them information no reasonable person would ever have, if not your done and have to rebuy everything.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2024-07-31\nConsumer Complaint2023-12-09\nAuthor: K***\n\nHad 288 euros in steam wallet, someone hacked my account even with two step verification, write a steam support for help but only answer was if something is spent in community market they can’t help.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2023-12-09\nConsumer Complaint2023-09-26\nAuthor: J***\n\nI was banned for saying \"Who let grandma on the PC\"and another for simply calling someone ignorant.Power tripping mods, devs who don't care, steam doesn't care. Yet allows racism/trolling/etc Fk steam, its a joke now.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2023-09-26\nConsumer Complaint2022-08-31\nAuthor: Anonymous\n\nSteam community is plain bad for a various reasons:1. Steam forums are a big mess, for example they allow users to post in any language and as result you get jumbled mess with posts in foreign languages together with English language posts. For example, If you check CS GO forums, you'll see half of posts are in Russian and half in English. I don't understand why such a big and international company would leave their forums so unorganized like that. All other normal companies have English only language allowed which is an international language and sometimes subforums for other languages like German, French and etc... so if French people want to post in French they go specifically in that sub-forum. But no, Steam doesn't care about this. Their forums is a one big mess.2. Moderation is biased and joke. I don't understand why such a big company like Steam can't afford to hire people for moderation and pay them. Instead they just recruit random people for moderation who do it for free and\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2022-08-31\nConsumer Complaint2022-05-28\nAuthor: J***\n\nThe login code never arrives. I hate Steam.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2022-05-28\nConsumer Complaint2021-11-08\nAuthor: N***\n\nThe service is terrible, I only signed up because I really like the game I wanted, but the rest is terrible, I hope to get something better soon.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-11-08\nConsumer Complaint2021-06-18\nAuthor: W***\n\nThey scam people for money, dont believe me? Read thisSource: Steam Subscribers/User Agreement NO GUARANTEESTO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, NEITHER VALVE NOR ITS AFFILIATES GUARANTEE CONTINUOUS, ERROR-FREE, VIRUS-FREE OR SECURE OPERATION AND ACCESS TO STEAM, THE CONTENT AND SERVICES, YOUR ACCOUNT AND/OR YOUR SUBSCRIPTION(S) OR ANY INFORMATION AVAILABLE IN CONNECTION THEREWITH.In short: You got a virus or your data leaked because of our software? Whoopsies we dont care, that isnt even legal or the last of their scammy stuff...\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-06-18\nConsumer Complaint2021-05-14\nAuthor: B***\n\nThe support is one of the worst I've ever seen.Useless support team.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-05-14\nConsumer Complaint2020-04-02\nAuthor: J***\n\nSteamcommunity has 15% fees, 15!!!!\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2020-04-02\nConsumer Complaint2020-03-27\nAuthor: H***\n\nWhat can I say? the support is one of the worst I've ever seen maybe the FUNCOM is much worse. If you tell the true on the steam forum you just got a BAN even if what you said did not violated the rules of the forum.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2020-03-27\nConsumer Complaint2018-03-16\nAuthor: B***\n\ndon't sign up will stick on your computer will kill your pc power you can't remove it from your pc even you deleted it will stay woking in the system\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2018-03-16\nConsumer Complaint2016-12-27\nAuthor: J***\n\nIn bloddy hate their page it's tiresome, it's in no way intuitive. I tried reaching out for support, but that is a maze.I'm simply trying to log in and redeem a key of a product I already bought, their search function is a joke. I f*u*c*k*i*n*g hate them. The layout is not like the how to video from the dealer, this can be done much simpler. I don't frigin care aboutn what other titles you have in store or what genre, I just want to redeem my key and install.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-12-27\nConsumer Complaint2016-10-28\nAuthor: P***\n\nSupport on site is terrible.Refunds not happend yet, despite games not working.No help at all if key is bought outside their system, so as a customer you can bounce back and through between bad support systems?? I wait for some other companies to compete in this market, for this can't be the best we as customers can expect.And do put an email up to find, instead of this stuppid website where you spend so long time trying to find a solution on, instead of a simple mail. Often the problem is not there, or if it's there just saying no help here???I need a response\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-10-28\nConsumer Complaint2016-06-26\nAuthor: V*** W***\n\nUseless support as always!\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-06-26\nConsumer Complaint2014-07-01\nAuthor: J***\n\nexpensive, and support team not willing to cooperate\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2014-07-01\nConsumer Complaint2014-04-15\nAuthor: B***\n\nWhen you pay for a program, you expect it too work. cant not buy or anything and have written to valve. but there is not a being done a damn thing abut it..\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2014-04-15\nConsumer Complaint2026-09-03\nAuthor: M***\n\nWorst platform ever wont give me a refund even though a game is unplayable because of bugs I won't ever be using the crap platform again I hope the platform breaks down for good piece fo crao\n\nTarget Domain: steamcommunity.com / steampowered.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2026-09-03\n\nEşleşen kayıt bulunamadı\n\nAktif sorgunuzu değiştirmeyi deneyin veya farklı bir kategori sekmesine göz atın.\n\n1 / 9",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Valve Skandallar Ana Kayıt Defteri — 160 Kaynaklı Olaylar"
          },
          {
            "level": 2,
            "id": null,
            "text": "Auth-host etki alanı engelleme"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: C***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: S*** L***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: F***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: A***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: K***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: Anonymous"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: N***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: W***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: H***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: P***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: V*** W***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: M***"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/tr/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/tr/#proxy-bypass-explainer",
          "https://phishdestroy.io/steam_dossier/tr/#autoban-feasibility-section",
          "https://www.trustpilot.com/review/steamcommunity.com"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/tr/valve_scandals_registry.content.json",
      "export_json_sha256": "5ca56b76d76a197859fabc9bada53447562ed457ff1ec6b598eb8f59ceb7d08c"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "tr/output_steam_network/index.html",
      "language": "tr",
      "title": "Mimari, Sömürü Değil: Otomasyon Ağı — “Steam” Dosyası",
      "source_url": "https://phishdestroy.io/steam_dossier/tr/output_steam_network/index",
      "source_html_sha256": "d6a20e0adf3cc16fdbcf43fc2c3cf6cd0ca2336f86fe8378731cae4a927b503d",
      "exported_at": "2026-09-29T00:21:15.866Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__index.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/tr/output_steam_network__index.pdf?v=print-20260929-v5",
        "sha256": "0c195f3eb9f760cec9730d785b7406e3cf531ceef3b2e2bdbbf0d5b2d9a24d5d",
        "bytes": 67717,
        "pages": 3
      },
      "integrity": {
        "signed_object": "output_steam_network__index.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__index.content.json.asc",
        "digest_file": "output_steam_network__index.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__index.content.json.asc output_steam_network__index.content.json",
          "sha256sum -c output_steam_network__index.content.json.sha256"
        ]
      },
      "content": {
        "text": "Ek VII · Teknik Mimari Analizi\nSteam Ağ Mimarisi — Protokol Uyumu ve Ekosistem Analizi\n\nOtomasyon, Valve’in mimarisidir. Bir güvenlik açığı değildir.\n\nBU BÖLÜMÜN KANITLADIĞI ŞEY\n\nBu modül, Steam otomasyon ekosisteminin temelini oluşturan 252 geliştirici depolarının, 3,320 GitHub profillerinin ve 4,214 katkı sağlayan çiftlerinin teknik topolojisini ortaya koymaktadır. Modül, üçüncü taraf otomasyonun, Valve adresindeki resmi Bağlantı Yöneticisi protokolüne, Protobuf şemalarına ve kötüye kullanım kodu içermeyen Web API’lerine dayandığını kanıtlamaktadır. Steam’ın algoritmik Guard onay jetonlarını tasarlayarak ve 66.7%, adresine kadar minimum işlem ücretleri toplayarak, Valve, otomatikleştirilmiş ekosistem operasyonlarının kasıtlı mimarı ve birincil ticari yararlanıcısı olarak işlev görmektedir.\n\n← Yönetici özetine geri dön\n\nValve, düzenleyici kurumlara, ödeme işleyicilerine veya dolandırıcılık mağdurlarına hitap ederken, hesap hırsızlığı ve piyasa manipülasyonunu “yetkisiz üçüncü taraf istismarlarına” ve “kötü niyetli yasadışı otomasyona” bağlamaktadır. Ancak 252-depo ağının teknik gerçekliği, bunun tam tersini ortaya koymaktadır: Her otomasyon çerçevesi, ticaret botu ve madencilik filosu, Valve Corporation tarafından tasarlanan, belgelenen ve gelir kaynağına dönüştürülen resmi protokol tanımları, Web API’leri ve kimlik doğrulama mekanizmaları çerçevesinde sıkı bir şekilde çalışır.\n\nAdli Bulgular: Bilinçli Mimari ve Haksız İhlal\n\nBu modülde incelenen yazılımlar — şunlar da dahil olmak üzere SteamKit, node-steam-user, ValvePython/steamve ArchiSteamFarm — şunları içerir sıfır yazılım güvenlik açığı, sıfır bellek bozulması ve sıfır sıfırıncı gün istismarı. Bunlar, Valve’ın tescilli Bağlantı Yöneticisi (CM) istemci protokolünün, Google Protocol Buffers (Protobufs)’ın ve Web API’lerinin temiz, sağlam ve açık kaynaklı uygulamalarıdır. Valve, bu API’leri programlı oturum açma işlemlerini kabul edecek şekilde tasarladı; Steam Guard’ı ise algoritmik doğrulama jetonlarına izin verecek şekilde tasarladı (identity_secret), ve ilan edilen 15% ücretini tahsil eder; bu ücret zamanla artarak Valve lehine 66.7%'ye kadar otomatikleştirilmiş bot ağlarının elden çıkardığı yüksek hacimli kartlar ve emtia satışları konusunda.\n\n01'ın Temel Unsurları · Protokolün Doğruluğu\nResmi Protobuf Şemaları\n\nOtomasyon kütüphaneleri güvenlik engellerini atlamaz. Resmi Protobuf mesajlarını serileştirirler (steammessages_clientserver.proto) TCP/WebSockets üzerinden, tıpkı Steam İstemcisi'nin yaptığı gibi, doğrudan Valve'un resmi CM kümelerine.\n\nPillar 02 · Algorithmic 2FA\nProgramlı Ticaret Yetkisi\n\nMilyarlarca dolarlık deri ticareti ekonomisinin tamamı, Valve sitesine bağlıdır. IEconService API ve mobil kimlik doğrulama cihazları (TOTP anahtarları). Valve, makineden makineye ticaret onaylarını mümkün kılmak amacıyla Steam Guard’ı özel olarak tasarladı.\n\n03. Sütun · Ticari Yararlanıcı\nGelir Getiren Makine Trafiği:66.7%’ye Kadar Ücret Alt Sınırı\n\nValve 15% ücretini öne çıkarıyor; ancak otomatik botların işlem yaptığı yüksek hacimli emtia ürünlerinde — koleksiyon kartları, kutular ve $0.03 ile $0.05 arasında fiyatlandırılan ucuz ürünler — Valve’un iki sentlik minimum ücret tabanı ($0.01 Steam + $0.01 yayıncı) bu işlemlerden 50% 66.7%’a, Valve lehine (3¢ kartından 2¢ kesildi, böylece satıcıya 1¢ kaldı). Ayrıca hesap başına $5.00 (sadece taranan filo için $26.8M).\n\n01 Modülü · Depo ve Protokol Kanıtları\nKamuya Açık Geliştirici ve Depo Altyapısı\n\nSteam otomasyonunu destekleyen 252 açık kaynak depolarının ayrıntılı adli kataloğu. Standart yazılım mühendisliği araçlarının, Valve adresinde yayınlanan API uç noktalarını herhangi bir güvenlik açığı kullanmadan nasıl uyguladığını gösterir.\n\n252Depolar\n4,554Rol Bağlantıları\nDepodaki delilleri incelemek →02 Modülü · Ekosistem Demografisi\nKüresel Mühendislik Ekosistemi Göstergeleri\n\n3,320 Steam ’in otomasyon ekosistemine katkıda bulunan yazılım mühendislerinin coğrafi ve kurumsal dağılımı; buna, önde gelen teknoloji şirketlerindeki kurumsal bağlantılar da dahildir.\n\n3,320Mühendisler\n98,902Bağlantı Çiftleri\nEkosistem göstergelerini incele →03 Modülü · Etkileşimli Görsel Grafik\nEtkileşimli Protokol ve Geliştirici Ağı Grafiği\n\nVis.js’ın etkileşimli ağ grafiği, depoları, protokol kütüphanelerini (SteamKit, Steamworks, ASF) ve projeler arası katkıcı çakışmalarını kapsamlı bir şekilde haritalandırır. Steam’ın otomasyon ekosistemini destekleyen, meşru ve birbiriyle bağlantılı açık kaynaklı yazılım mimarisini görsel olarak gösterir.\n\nEtkileşimliVis.js Motor\nKüme İzolasyonuCanlı Arama\nSıfır Güvenlik AçığıStandart API'ler\nEtkileşimli ağ grafiğini aç →\nYasal ve Düzenleyici Çerçeve (GDPR Makale 25 ve Tüketici Koruması):\n“Tasarım ve Varsayılan Olarak Veri Koruma” ilkesi kapsamında, sessiz APIanahtar üretimi, bildirim yapılmaksızın işlem iptali ve makine tarafından otomatikleştirilmiş varlık tasfiyesine izin veren bir platform mimarisi, platform operatörünün mimari tercihidir. Valve, kayıpların “dış siber saldırılar”dan kaynaklandığını öne sürerek tüketicilerin geri ödeme taleplerini sistematik olarak reddettiğinde, saldırı vektörünün aslındValve’in kendi kasıtlı olarak tasarladığı Web API mimarisi olduğunu gizlemektedir.\n\nETKİLEŞİMLİ GÖRÜNTÜ\n\n252-deposunun tam etkileşimli görselleştirmesi ve 3,320-geliştirici ağ grafiği şu adreste mevcuttur: network.html. Toplam göstergeler şurada yer almaktadır: BI Göstergeleri sayfa.\n\nSteam Dosyası · Teknik Mimari Arşivi · Kamuya Açık Kaynak Kayıtları · Tüm haklar insanlığa devredilmiştir.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam Ağ Mimarisi — Protokol Uyumu ve Ekosistem Analizi"
          },
          {
            "level": 3,
            "id": null,
            "text": "Resmi Protobuf Şemaları"
          },
          {
            "level": 3,
            "id": null,
            "text": "Programlı Ticaret Yetkisi"
          },
          {
            "level": 3,
            "id": null,
            "text": "Gelir Getiren Makine Trafiği:66.7%’ye Kadar Ücret Alt Sınırı"
          },
          {
            "level": 2,
            "id": null,
            "text": "Kamuya Açık Geliştirici ve Depo Altyapısı"
          },
          {
            "level": 2,
            "id": null,
            "text": "Küresel Mühendislik Ekosistemi Göstergeleri"
          },
          {
            "level": 2,
            "id": null,
            "text": "Etkileşimli Protokol ve Geliştirici Ağı Grafiği"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/tr/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/tr/output_steam_network/valve_ru_farming_isolated.html",
          "https://phishdestroy.io/steam_dossier/tr/output_steam_network/steam_ecosystem_dashboard.html",
          "https://phishdestroy.io/steam_dossier/tr/output_steam_network/network.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/tr/output_steam_network__index.content.json",
      "export_json_sha256": "dc9809e7fbb498c401d10d19d6dd67a110c94c169cd31ad8d687e1b778a7b308"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "tr/output_steam_network/network.html",
      "language": "tr",
      "title": "Geliştirici ve depo gezgini — “Steam” Dosyası",
      "source_url": "https://phishdestroy.io/steam_dossier/tr/output_steam_network/network",
      "source_html_sha256": "5326de40e81ce1b2f84488c36222b8add46e95182337204cfe603f19a6c6fc51",
      "exported_at": "2026-09-29T00:21:18.411Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__network.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/tr/output_steam_network__network.pdf?v=print-20260929-v5",
        "sha256": "121d31ef94f091221026f326b8b5026dbf7e8048225fb7fd452304a594637f1e",
        "bytes": 36617,
        "pages": 1
      },
      "integrity": {
        "signed_object": "output_steam_network__network.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__network.content.json.asc",
        "digest_file": "output_steam_network__network.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__network.content.json.asc output_steam_network__network.content.json",
          "sha256sum -c output_steam_network__network.content.json.sha256"
        ]
      },
      "content": {
        "text": "Geliştirici ve depo gezgini\n\nBir düğümü ara. Kaydedilmiş ilişkiyi incele.\n\nKAMU KAYITLARI / TOPLANAN BAĞLANTILAR\nCanlı Arama\nFiltre Katmanları\nToplam Geliştirici Sayısı3,320\nToplam Repo İşlemleri252\nGÖSTERİLEN GRAFİK / KOLEKSİYON ALT KÜMESİ468 DÜĞÜMLER • 1103 KENARLAR\nSeçilen profil kaydı\n\n💡 Grafikteki herhangi bir düğüme tıklayın veya “Arama” alanına bir şey yazın; böylece o düğümün toplanan bağlantıları ve kaynak yollarını inceleyebilirsiniz.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Geliştirici ve depo gezgini"
          }
        ],
        "links": []
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/tr/output_steam_network__network.content.json",
      "export_json_sha256": "e2ad76d3e7fedc65562995ca23db464da37d7eb5d34b3a5be10f21ecd2eae744"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "tr/output_steam_network/steam_ecosystem_dashboard.html",
      "language": "tr",
      "title": "Rakamlarla toplanan ağ — “Steam” Dosyası",
      "source_url": "https://phishdestroy.io/steam_dossier/tr/output_steam_network/steam_ecosystem_dashboard",
      "source_html_sha256": "20e6492da6e43bd9c7664cf286433cc88614f6d4b637c75a3ab36083c0e41f9a",
      "exported_at": "2026-09-29T00:21:18.606Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__steam_ecosystem_dashboard.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/tr/output_steam_network__steam_ecosystem_dashboard.pdf?v=print-20260929-v5",
        "sha256": "5a33edccf85821a38311ab3cde7e538643aeb78064c1b7a49042652716642dd1",
        "bytes": 39835,
        "pages": 2
      },
      "integrity": {
        "signed_object": "output_steam_network__steam_ecosystem_dashboard.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__steam_ecosystem_dashboard.content.json.asc",
        "digest_file": "output_steam_network__steam_ecosystem_dashboard.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__steam_ecosystem_dashboard.content.json.asc output_steam_network__steam_ecosystem_dashboard.content.json",
          "sha256sum -c output_steam_network__steam_ecosystem_dashboard.content.json.sha256"
        ]
      },
      "content": {
        "text": "İSTATİSTİKLERE GENEL BAKIŞ // DOSYA02\nSteam Ekosistem Gösterge Paneli — Rakamlarla Ağ\n\nAğ, rakamlarla.\n\nBU BÖLÜMÜN KANITLADIĞI ŞEY\n\nBu gösterge paneli, 3,320 geliştiricileri ve 252 depoları genelinde yapısal bilgileri bir araya getirerek, 68 adresindeki kumar sektörüne özgü kod tabanlarını ve platformlar arası bağlantı köprülerini tespit eder. Ampirik veriler, coğrafi kümelenmeleri ve geliştiriciler arasındaki örtüşmeleri öne çıkararak, üçüncü taraf skin kumar altyapısının, Steam platformuyla entegre, organize ve son derece birbirine bağlı bir yazılım endüstrisi olarak işlediğini ortaya koymaktadır.\n\n← Yönetici özetine geri dön\n\nSoruşturma veritabanına ait konsolide istatistikler: coğrafi dağılım, önde gelen şirketler, kumar sitelerinin depoları ve aktif bağlantı köprüleri.\n\nTaranmış Geliştiriciler3320\nToplam Repo İşlemleri252\nKumar Raporları68\nToplam Bağlantı Sayısı1,426\nOtomasyonun Yapısı ve Sektörleri\nI. Sektör —Valve Şirketi Çekirdeği\n\nResmi depolar ve sistem yazılımları. Valve çalışanları Nephyrin ve Joe Ludwig’in onaylanmış geliştirme alanı.\n\nSektör II — Yetkilendirme Motorları ve Protokol Emülatörleri (SteamKit)\n\nValve'dan Nephyrin ile kumar temalı görünüm geliştiricisi DoctorMcKay'in ortaklaşa hazırladığı, tersine mühendislik yoluyla geliştirilmiş ağ kütüphaneleri.\n\nSektör III — Kart Çiftçiliği Müşterileri (ArchiSteamFarm)\n\nSteamKit protokol emülatörlerini kullanarak arka planda milyonlarca sahte istemciyi (bekleme modunda) çalıştırarak koleksiyon kartları toplamak.\n\nGeliştiricilerin Coğrafi Dağılımı\nAlmanya57\nAmerika Birleşik Devletleri52\nKanada48\nBirleşik Krallık44\nPolonya30\nFransa28\nRusya Federasyonu27\nÇin27\nABD (Washington Eyaleti)23\nAvustralya19",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam Ekosistem Gösterge Paneli — Rakamlarla Ağ"
          },
          {
            "level": 3,
            "id": null,
            "text": "I. Sektör —Valve Şirketi Çekirdeği"
          },
          {
            "level": 3,
            "id": null,
            "text": "Sektör II — Yetkilendirme Motorları ve Protokol Emülatörleri (SteamKit)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Sektör III — Kart Çiftçiliği Müşterileri (ArchiSteamFarm)"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/tr/#briefing-heading"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/tr/output_steam_network__steam_ecosystem_dashboard.content.json",
      "export_json_sha256": "dc4929c7488dc5bef317d4109f3408dd89831ba8f97fec5231903a064fffd151"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "tr/output_steam_network/valve_ru_farming_isolated.html",
      "language": "tr",
      "title": "Kod, katkıda bulunanlar ve çatallanmalar — “Steam” Dosyası",
      "source_url": "https://phishdestroy.io/steam_dossier/tr/output_steam_network/valve_ru_farming_isolated",
      "source_html_sha256": "93fd798de09399513602b4c62078e120768096508bba85014827546551f48758",
      "exported_at": "2026-09-29T00:21:18.845Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__valve_ru_farming_isolated.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/tr/output_steam_network__valve_ru_farming_isolated.pdf?v=print-20260929-v5",
        "sha256": "faca3afaeda95e0d043e7ddb04d95db6ba6b2e2e4ff80def5a9baed77f866cae",
        "bytes": 41918,
        "pages": 2
      },
      "integrity": {
        "signed_object": "output_steam_network__valve_ru_farming_isolated.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__valve_ru_farming_isolated.content.json.asc",
        "digest_file": "output_steam_network__valve_ru_farming_isolated.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__valve_ru_farming_isolated.content.json.asc output_steam_network__valve_ru_farming_isolated.content.json",
          "sha256sum -c output_steam_network__valve_ru_farming_isolated.content.json.sha256"
        ]
      },
      "content": {
        "text": "BÖLÜM II / BELGELENMİŞ İLİŞKİYİ TAKİP EDİN\n\nÇatallanmalar, katkılar ve yazılım bağımlılıkları somut kanıtlardır. Bu bakış açısı, derlenen rolleri korur; istihdam, güvenlik önlemlerinin aşılması ve suçla ilişkilendirme ise ek kaynaklar gerektirir.\n\nEtkileşimli yetkinlik haritasını açın ↗\nKAMU KAYNAKLARI / GÖREV DENETİMİ\nKod. Katkıda bulunanlar. Çatallar.\n1. Nephyrin: çatallar ve katkılar\n\nSağlanan anlık görüntüde Nephyrin, ValveSoftware/Proton projesine katkıda bulunan bir kişi ve SteamRE/SteamKit ile SteamRE/open-steamworks projelerinin çatallayıcısı olarak belirtilmiştir. Profil verilerinde ise Valve Software adresi yer almaktadır. Bu alanlar ayrı ayrı değerlendirilmelidir.\n\nBir çatal, bir depo kopyasını kaydeder. Bu dışa aktarma işlemi, SteamKit kimlik doğrulama kodundaki değişiklikleri yansıtan bir onay eklemez.\nDepo referansları / geçmişi inceleme\nSteamRE/SteamKit ↗ SteamRE/open-steamworks ↗\n2. Genel özellikler: masaüstü istemcisi olmadan otomasyon\n\nSteamKit ve node-steam-user, Steam ile programlı etkileşim imkânı sunar. ArchiSteamFarm, çoklu hesapla kart toplama sürecini belgeler ve SteamKit2’yi bir bağımlılık olarak belirtir.\n\nBunlar somut otomasyon yetenekleridir. Başsız yürütme, münhasır ticari kullanım anlamına gelmez veya Steam Guard’ı atlatma anlamına gelmez. Önemli olan hususlar, talep edilen kimlik bilgisi, bu kimlik bilgisiyle gerçekleştirilebilecek eylemler ve platform tarafından uygulanan denetimlerdir.\n\nKaynak: Proje README dosyaları ve ArchiSteamFarm.csproj. Yetenek haritası, belgelenmiş her bir bağımlılığı birbirine bağlamaktadır.\n3. JoeLudwig: hl2sdk katkıcı etiketi\n\nAnlık görüntüde JoeLudwig, alliedmodders/hl2sdk, ValveSoftware/openvr ve ValveSoftware/source-sdk-2013. projelerinin katkıcıları arasında listelenmiştir. Bu, gözlemlenebilir bir proje ilişkisidir. Dışa aktarım, belirli bir SDK değişikliğini hırsızlık veya kumar amaçlı bir uygulamayla ilişkilendiren kanıt sunmamaktadır.\n\nDepo referansları / geçmişi inceleme\nalliedmodders/hl2sdk ↗ DoctorMcKay/node-steam-user ↗\nMANTIK ŞEMASI // İZLER\nBağlantı Mantığı Akış Şeması:\nPROFİL İLİŞKİSİ\nNephyrin / derlenmiş profil\nKatkıda bulunan: Proton. Çatal oluşturan: SteamKit ve open-steamworks.\n▼ Toplanan çatallanma ilişkisi\nTOPLUM KÜTÜPHANESİ\nSteamRE/SteamKit\nSteamRE kuruluşu tarafından yönetilen, herkese açık Steam ağ kütüphanesi.\n▼ SteamKit2 bağımlılığı bildirildi\nBELGELENMİŞ OTOMASYON\nJustArchiNET/ArchiSteamFarm\nBelgelerde, birden fazla hesap üzerinden kart toplama faaliyetleri ve bir SteamKit2 bağımlılığı belirtilmiştir.\nKANIT İNCELEMESİ / KAYNAK ÖZETİ\nKAYDEDİLDİ: ayrı “katkıcı” ve “fork oluşturan” etiketleri.\nBELGELENMİŞ: Halk kütüphaneleri, programlı Steam etkileşimlerini desteklemektedir.\nAÇIK SORU: Belirli bir kodun yazarlığı, platform onayı ve kötüye kullanımın kime atfedileceği konusunda ayrı ayrı kanıtlar gereklidir.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Kod. Katkıda bulunanlar. Çatallar."
          },
          {
            "level": 2,
            "id": null,
            "text": "1. Nephyrin: çatallar ve katkılar"
          },
          {
            "level": 2,
            "id": null,
            "text": "2. Genel özellikler: masaüstü istemcisi olmadan otomasyon"
          },
          {
            "level": 2,
            "id": null,
            "text": "3. JoeLudwig: hl2sdk katkıcı etiketi"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/tr/investigation_part2.html#automation-map",
          "https://github.com/SteamRE/SteamKit",
          "https://github.com/SteamRE/open-steamworks",
          "https://github.com/alliedmodders/hl2sdk",
          "https://github.com/DoctorMcKay/node-steam-user"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/tr/output_steam_network__valve_ru_farming_isolated.content.json",
      "export_json_sha256": "06cd146b052a8914882df6608a8ccaa3ba04a08e1fd6ffb65a514e524b26c834"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "zh/card_economy.html",
      "language": "zh",
      "title": "卡牌经济——《Steam》专题报告",
      "source_url": "https://phishdestroy.io/steam_dossier/zh/card_economy",
      "source_html_sha256": "37f6a93076b84d82fed6ae792314d4390759455c6a09cce7ab07345780801751",
      "exported_at": "2026-09-29T00:21:23.364Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "card_economy.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/zh/card_economy.pdf?v=print-20260929-v5",
        "sha256": "f121129e3739f4f91094fb2fce2bcbaf1b89e80d48ddaf8a9fcb2652d3fb5c8d",
        "bytes": 1566276,
        "pages": 19
      },
      "integrity": {
        "signed_object": "card_economy.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "card_economy.content.json.asc",
        "digest_file": "card_economy.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify card_economy.content.json.asc card_economy.content.json",
          "sha256sum -c card_economy.content.json.sha256"
        ]
      },
      "content": {
        "text": "附件五——卡牌经济\n机器人农场并不是Valve商店里的一个漏洞。它是一个客户.\n\n在Steam账户花费金额之前，无法获得任何一张交易卡$5.00 在商店里。它无法刷取自己不拥有的游戏，也无法刷取别人免费赠送的游戏。因此，在自动刷卡系统产出任何东西之前，它必须先付费进入——每个账号都需要支付由 Valve 公布的费用。 随后，Valve的自动化条款逐条明确列出了该卡牌农场能产出的具体内容； 其许可协议禁止任何将刷取到的卡牌转化为现金的途径；而当卡牌最终被交易时，其市场平台会抽取佣金——虽标价为 15%，但每笔交易的最低佣金为两美分，对于定价以美分为单位的卡牌而言，这几乎占了价格的大部分。 本展品将衡量该交易规模之大，分析个人资料顶级的卡组成本，并展示当账户属于普通交易者时，Valve的执法部门如何依据同一条款采取行动。\n\n农场首先需要购买什么每个等级在套装中的价格办公桌的两侧谁负责调控卡牌经济？\n$5.00在账户能够接收任何卡片之前，需先进行消费 — Valve的官方支持页面\n13,876在该期中发行交易卡的游戏有 Steam 个，共包含 99,971 种不同的卡牌类型\n694,673目前由91个公开上市的交易机器人持有的完整卡组\n1,389,346该库存已消耗的账户和游戏卡发放额度，至少应为\n$9.99带卡牌游戏的 median 价格——其完整套装的 median 售价为 $0.74\n97,114该卡牌交易群的成员，其管理员名单中有一名编号为 Valve 的员工——§ 08\n01 — 流程\n农场究竟是什么，一步一步来\n\n仅根据该工具自身的文档以及 Valve 的支持页面进行描述。本节内容均非推断得出，且双方均未对此提出异议。\n\n步骤 1\n买入\n\n该账户不得是有限的. Valve的支持页面禁止受限账户“参与 Steam 市场”，来源：“交易 Steam 社区道具（交易卡、补充包、宝石等）” 以及来自“获得 Steam 个个人资料等级（锁定在 0 级）和交易卡”. 门票就是钱：“您需要在该家商店内消费至少 $5.00 美元。”\n\n第 2 步\n购买游戏\n\n卡牌仅会从已拥有的游戏中掉落。“您必须在您的 Steam 账号上拥有该游戏，才有资格获得该游戏掉落的任何卡牌。家庭共享不视为拥有，因此不计入其中。” 免费路线也关闭了：“在促销期间免费获得的付费游戏无法用于刷卡牌掉落”，以及“如果你在免费游戏中没有花过钱，就无法获得卡牌。”\n\n第 3 步\n空闲\n\n该工具以无交互模式将该账户登录到 Steam 网络，“解析您的徽章”, 生成可收集头衔的列表并开始“游玩符合条件的游戏，并定期检查游戏是否已经完全刷完。” 其维护者对该机制的描述：它“除了告诉 Steam 我们正在玩某款游戏之外，什么也没做。”\n\n第 4 步\n药水用完了\n\n每个标题都是有限的。“每款游戏都有固定的卡牌掉落数量。一旦你集齐了所有卡牌（约占整套卡牌的一半），这款游戏就不再适合刷卡了。” 想要持续生产的农场必须不断购买地契。地契的供应量受到购买行为的限制——这是设计使然，且对Valve有利。\n\n第 5 步\n提现\n\n该卡片会通过以下三种途径之一离开：在社区市场上售出、被交易出去，或被压制成宝石。每种情况均属于订阅市场交易或交易行为，第3.D条对此规定如下：“Valve 可能会对订阅市场中的交易收取费用。” 正是这一步导致了整个事件构成违规——参见05.\n\n来源，全文照录自 2026-09-22：Steam 支持 — 受限用户帐户 ↗ ·ArchiSteamFarm 常见问题解答 ↗ ·Valve — Steam 交易卡常见问题解答 ↗ ·Steam 订阅协议 ↗ 已归档 2026-09-24 ↗. ArchiSteamFarm 在本页中始终作为一种测量工具使用，而非作为被告；其自身文档中明确指出：“ASF 未获得 Valve 的授权”.\n\n02 — 规模\n一个农场在赚到一分钱之前，就已经支付了 Valve\n\n由于受限账户无法领取卡片，因此农场中的每个账户在开始产出任何物品之前，都必须解除受限状态。相关门槛已公布，且按每个账户收取费用。\n\n农场规模\t这个数字从何而来\t在店内消费达到最低金额方可申请该卡\n10 个账户\tASF建议的上限为——“基于内部Valve指南以及我们自己的建议”\t$50\n100–200个账户\t同一份常见问题解答中的技术上限：“使用一个 IP 地址和一个 ASF 实例，最多可运行 100 到 200 个机器人”\t$500 – $1,000\n120个账户\t下文中的执法案例3——永久封禁\t$600\n170个账户\t下文中的执法案例2——在2017年冬季促销期间被永久禁赛\t$850\n1,000 个账户\t下文中的执法案例1——禁止贸易\t$5,000\n5,000 个账户未经核实\t操作员秤已向本次调查报告，但未经独立核查 —参见关于来源的说明Simplified Chinese (Mainland)\t$25,000\n10,000 个账户未经核实\t操作员秤向本次调查报告的内容，未经独立核查 —参见关于数据来源的说明\t$50,000\n\n本页中只有最后两行数据是基于未经核实的报告而非文件得出的——这些数据在表格中已作标注，具体说明见关于来源的说明，而且这里其他内容都不依赖于它们。右侧一栏仅基于Valve公布的$5.00美元阈值进行的算术运算，除此之外别无其他。这是一个楼层，这并非对农场成本或Valve收益的估算：该数值未包含游戏——这些游戏必须是自购的，不能是通过促销活动免费获得的——也未包含在卡牌出售时社区市场扣除的约15%。本页面未列出任何收入数据。\n\n而且 Valve 自己也给卡包开价了。 其“交易卡”常见问题解答用直白的美元数字说明了免费玩家的转化率：\n\n“免费游戏会根据你的游戏内消费发放游戏卡。”每消费 $9 美元（约） “自 Steam 交易卡测试版启动以来，您将获得一张卡牌掉落。”\n\n—Valve、Steam 交易卡常见问题解答 ↗ · 经核实，原文照录 2026-09-22\n\n交易卡并非平台亏本赠送的赠品。它是Valve出售的商品，售价按Valve公布的标准计算——随后在转售时还会再次收费。这就是为什么对“卡农”的如实描述并非寄生虫. 这是批发采购商.\n\n所购物品的实际大小是多少\n\n从这里到本节结尾的所有内容均为测量结果，而非报告数据。卡牌统计数据源自 Steam Card Exchange 发布的徽章价格表；游戏本身的售价来自 Valve 自身的商店 API；机器人库存数据则来自一个任何人都可以访问的公开机器人目录。 上述三项数据均在 2026-09-22 上读取，计算过程详见第08节.\n\n13,876发牌游戏\n99,971不同的卡牌类型\n5 · 6 · 15每套卡牌数量：最小值、中位数、最大值\n$0.74成套成品的中位数价格\n$23,586.57市场上每套中有一件\n一个集合有多大\n\n13,876 该套卡中的游戏数量。Valve 其中约一半会分配到任意一个账户上。\n\n0\n1,250\n2,500\n3,750\n5,000\n5\n6\n7\n8\n9\n10\n11\n12\n13\n14\n15\n许可证的费用是多少\n\n这些游戏在Steam商店的标价（单位：美元）。\n\n0\n1,000\n2,000\n3,000\n4,000\n<$1\n$1-3\n$3-5\n$5-10\n$10-20\n$20-40\n$40+\n该集合计算完成后返回什么\n\n同一款游戏的完整套装的市场价格。\n\n0\n1,500\n3,000\n4,500\n6,000\n<$0.50\n$0.50-1\n$1-2\n$2-5\n$5-10\n$10+\n\n将第二张和第三张图表相互对照，无需进行计算就能看出交易形态：游戏数量集中在数十美元区间，而它们产生的套装数量则集中在1美元以下。两者都是对同一批13,876游戏的统计，且采用相同的坐标轴单位，因此比较的是两个高度值，而非两个量级。\n\n这是供给端。需求端则是Valve无需做广告的部分，因为它早已公之于众：一个公开的卡牌交易机器人目录中列出了目前有91个机器人持有694,673套完整套装。 无需登录，无需抓取电商平台数据，也无涉及隐私数据——库存数量印在页面上，紧挨着每个机器人的名称。\n\n将该股票视为这里唯一重要的单位。Valve自己的规则：“大多数游戏会掉落数量大约相当于该游戏卡组总数一半的卡牌……你需要从其他社区成员那里收集这套物品的另一半。\" 一个账号仅靠游戏操作是无法完成一整套任务的。至少需要两个账号，每个账号都拥有该游戏，并且各自消耗掉每局游戏中仅限一次的“掉落”配额。掉落配额不会自动恢复。\n\n694,673库存套装，91个公开机器人\n3,473,365牌，按5张起订\n1,389,346已消耗的掉落奖励，最低值\n2,602仅拥有一款游戏的账号，机器人密度最高\n694,673组坐在哪里\n\n在91个公开上市的卡牌机器人中，按库存完整套装数量排名，排名前十二位的如下。排名前十位的机器人共持有248,115套——即榜单上所有卡牌的35.7%套。\n\n0\n11,250\n22,500\n33,750\n45,000\nCard Supply #4 (High)\nN!vq's Leveling (High)\nAlice [BOT] LEVEL-UP RARE SETS\nN!vq's Leveling (Low)\nDisco Lite Level Up\nN!vq's Leveling (Mid)\nbaty131store.net | Level Up\nKitten - Supreme\nArashirn | Level Up\nSH (Junior) Level Up\nDuobot.com - Overstock\nlvlupbot.com - godlike\n\n这139万个配额中的每一个，都属于一个拥有该游戏、已通过“$5.00”门槛且永远无法再次产生这些掉落物的账号。这就是滞销库存 涉及91个机器人。这并非对市场的衡量，而是对市场结束后所剩部分的衡量。\n\n最后一个数字是“ pigeonhole 法”得出的结果，而非实际人数统计。有一个机器人列出了从仅11款游戏中抽取的 14,310 套，因此其中至少有一款游戏由 1,301 套代表，这意味着至少有 2,602 个不同的账户各自购买了该款游戏。 这是算术允许的最小数值，且仅涉及九十一台机器人中的一台。\n\n这层楼所传达的信息与未传达的信息\n\n这些机器人既从普通玩家那里购买卡牌，也从刷卡场购买——它们公布的收购价格正是该目录的核心内容。因此，这139万个配额并非农场自有账户的数量。 这些是按“每个账号限一次、每款游戏限一次”的掉落配额，已在Steam的某个地方被消耗，最终作为未售出的商品流入商业库存。 无论每个账号背后是刷号账号，还是正在清空徽章页面的青少年，都无损于Valve所获取的收益：$5.00的解锁、游戏授权，以及每次交易的市场分成——不是 15%，而是 15% 或两个一美分最低额，以较大者为准，而在一张以美分为单位标价的卡片上，这个数字要大得多。计算过程见下方的费用梯度表. 这就是本页的要点，这并非对农民的抱怨：该平台既对某种行为收取费用，又在以“商业用途”为由永久封禁用户时，原封不动地援引了该行为作为理由。\n\n从另一个意义上说，该数字也代表了一个下限。它仅统计了今日上架且未售出 关于那些机器人，选择位于公共目录中. 所有已售出的商品、所有非公开商品以及目录外的所有机器人均被排除在外。\n\n而且，按照Valve的价格，农业根本无法自给自足\n\n一个显而易见的反对意见是，农场会购买廉价游戏来制作昂贵的卡牌。Steam自己的商店API却给出了相反的说法。在13,876款包含卡牌的游戏中，13,713款的游戏价格已确定；12,918 是付费书籍，其标价中位数为 $9.99。 一套成品的销售中位数为$0.74. 每套需要两份许可证。因此，一套许可证的中位数价格大约为$19.98 游戏制作许可证及申报表 $0.74.\n\n在 2026-09-22 上测量\t值\t该协议解决了什么\n带卡牌游戏的列表价格中位数\t$9.99\t许可证才是这笔交易中成本较高的一半，而不是卡片本身\n价格为 $4.99 或更低的游戏\t3,665 (28.4%)\t即便是最廉价的尾巴，也比它所产的整套更值钱\n商店里最便宜的纸牌游戏\t$0.99\t两份许可证，$1.98，一套通常售价不到 $1.30\n那些周边套装售价高于游戏本体本身的游戏\t323 / 12,918 (2.5%)\t在40场比赛中，有1场存在针对Steam标价的卡牌套利机会\n普查中的免费游戏\t795\t而且，每款新商品的售价均为 $9 游戏内消费\n\n这便从经济角度上给出了结论，支持Valve的观点，而与通常的说法相悖。以Valve自身收取的价格来看，卡牌刷级是一项亏损的活动，只有在以低于Steam的标价购得许可证的情况下才可行 — 捆绑包、区域定价、关键转售。卡牌只是副产品。购买才是重头戏。而这次购买发生在 Steam。\n\n农场实际上支撑着什么\n\n将这些信息综合起来看，农场就不再像是Valve所容忍的存在，而是变成了Valve所需要的东西。农场提供的每一项投入，都是Valve所报告或开具账单的产出。追踪一个机器人账户的外部活动：\n\n一个水军账号是“批发客户”，而非泄密事件\n游戏销量\n\n购买自己刷分的游戏——从13,876卡牌游戏到$0.50垃圾游戏——因为卡牌只会从已拥有的游戏中掉落。\n\n“在线”与游戏时间\n\n让玩家处于闲置状态以掉落卡牌，从而推高了第0-1节中作为用户参与度指标所引用的“同时在线玩家数”和“游戏时长”数据——而第4.C节将这一数据明确称为“虚假游戏时长”。\n\n注册\n\n必须先通过$5.00限额账户门槛，才能获得卡片——每个账户需在实体店消费Valve本。\n\n钱包余额与手续费\n\n它销售的每张卡都会通过“市场”进行结算，其中低面值卡的手续费最高可达 66.7%，而所得款项则锁定在 Steam 钱包中。\n\nSteam级公关\n\n徽章和等级 Valve 的展示，完全是因为有人精心打造了套装——而该排行榜的顶端则被机器人占据（参见第 03 节）。\n\n移除该农场后，上述所有数值都会下降 ——游戏销量较低，“在线”用户规模较小，账号从未注册，费用从未收取，等级也从未达到。这就是为什么一条禁止自动化的规则却与数百万个自动化账号并存：禁令只是选项，而这种活动才是收入来源。\n\n而且提现本身就是一种财富流失——0——要缴两次税\n\n这张卡牌并不是循环的终点。Valve的机制本身允许一张卡牌被压碎成宝石，并消耗宝石来制作补充包 — 再有三张卡 —— 这些卡要么被卖出，要么再次被销毁。每次循环都是一次市场交易或转换，且每次都要缴纳税费。该循环的方向由下文测算的费用下限决定，无需借助外部模型：在此循环内售出的每张卡都会交出至少两美分，在交易价格为三到五的卡片上，因此每次转动摇柄所获得的回报都少于投入的。这种循环摧毁了虚拟价值，并迫使新的、需支付手续费的交易来填补这一缺口。本文未提及该损失的具体数额 — 每套的回报取决于宝石掉落率和强化包中奖率，而本项调查并未对此进行测算。\n\n收藏卡来自已拥有游戏的掉落物\n→\n宝石卡片被压坏，费用已扣除\n→\n补充包用于制作的宝石\n→\n3张新卡已在Market上售出，已扣除手续费\n↶\n\n这里仅阐述了游戏机制，这些机制源自Valve——卡牌可兑换为宝石，宝石可制作卡包，卡包可产出卡牌——每项机制都在Steam集换式卡牌常见问题解答中有所记载，且每个环节都属于需缴税的市场事件。循环机制的来源：Valve、Steam 交易卡常见问题解答 ↗.\n\n这不仅仅是一个瞬间，而是一个拥有多年发展根基的行业。\n\n单次快照可能只是偶然现象。因此，我们通过Wayback Machine回溯了2022年至2026年期间，每逢季节性Steam促销活动时，都会读取一次公开的卡片机器人目录——这些机器人持有的固定库存，以及在一次又一次促销活动中始终如一的账户。 这种经济活动并非昙花一现；它持续存在，拥有稳定的运营商核心，其规模曾达到峰值，超过库存中有300万套 在2023年冬季促销期间——某个时刻，某个目录中曾存放着价值约30万张的《军团要塞2》激活码。\n\n公共机器人目录中保存的完整卡组，由 Steam 出售\n\n每个季节性特卖期间，steam.supply/CardBots 会有一个 Wayback 快照。将鼠标悬停在上面，即可查看按该快照汇率计算的 TF2 钥匙价值。\n\n0.0M\n0.9M\n1.8M\n2.6M\n3.5M\nA’22\nS’23\nW’23\nS’24\nW’24\nS’25\nS’26\n401在各销售渠道中观察到不同的机器人账号\n59在7次销售中至少有5次出现——稳定的核心\n162022年至2026年期间，7场拍卖会中场场皆有参展\n3.22M库存中的 Peak 套装（2023 年冬季）≈ $570k–790k 把钥匙\n从顶端看，一场促销活动的徽章排行榜是怎样的\n\n需求方与供给方相匹配。在公众方面2024年夏季促销徽章排行榜 已归档 2026-07-16 ↗，排名第一的账号制作了“已售出”徽章1,740,645 次 — 174万套十张卡的套装，1740万张卡 整合为一种单一的装饰样式。按该销售活动自身的市场价格（每套 $0.50）计算，那就是~$870,000 就卡牌价值而言；按照实际购买方式计算——将《军团要塞2》钥匙交易给升级机器人，每把钥匙大约能换取7.6套——这~229,000个键，约$410,000–$570,000 从实际意义上讲。第二号账户：552,000 套，~$130,000–181,000。没有人会为此下注。这是被买入的，而买入的每一笔交易都是由 Valve 结算的。\n\n方法与限制：将每个快照所列的机器人中的“set-stock”值相加；该数字 由于不同销售数据中每个快照的机器人数量无法直接比较——部分快照仅显示精选机器人，而部分则显示完整目录——因此库存数据应被视为可见内容的下限，而非全面统计。 关键值采用每个快照中“每键广告套装数”的中位数，并使用一个 $1.79–$2.49 的 TF2 键。跨快照的持久性通过 SteamID64 实现。2021 年的快照采用了较旧的页面布局，因此未被纳入统计。数据：farm-economy-timeline.json; 来自 SteamLadder 的徽章等级；来自 Steam 卡牌交易所的定价（销售时的 Wayback 快照，$0.05 一张卡牌）。\n\n即使没有促销活动，那支车队依然在那里\n\n上面的两张图片并非两个群体。它们是同一支舰队，是在不同时刻拍摄的。本节开头读取的目录是在一台一个没有季节性促销活动的普通日子 — 2026-09-22 — 即使在静止状态下，它也保持着91个机器人和 694,673 套全套: 约186,000 TF2 键位，$334,000–$464,000 的卡牌数值，处于闲置状态 销售间隙。这就是业务在没有任何动静时维持的最低水平。\n\n而且这是同一项操作。通过 SteamID64 匹配，在这91个处于休眠状态的机器人中，有87个——96%——也出现在上面的七张销售快照中，每一本里都有十六个。该目录并非一个仅在销售期间开放、结束后便关闭的摊位；它是一份常设的商业库存清单，正是这支车队将其规模扩大到了322万套 在2023年冬季的高峰期，且从未降至零。所谓促销，就是商品售出之时。一年中的其余时间也同样存在这种情况。\n\n各机器人的休眠目录\n\n每个方块代表目录中位于 2026-09-22 位置的一个机器人，如果该机器人也出现在七张销售快照中，则会高亮显示。91是当天名录中列出的数字，并非舰队规模 — 在销售快照中出现了401个不同的账户，而该目录在不同日子里展示的内容各不相同。\n\n曾在以往拍卖中出现过 (87)自上次快照以来的更新 (4)\n\n从同一公共目录读取非销售基线值 2026-09-22，无需登录。静态值采用各机器人自身公布的“每键集”速率以及其上方的 $1.79–$2.49 键值区间。 重叠分析基于 SteamID64 与七个促销快照的比对。由于“精选”与“完整”列表在不同快照中存在差异，因此此处比较的是库存和身份信息，而非用户数量。计算方法如下：第08节.\n\n03 — 梯子\n另一个产品就是你名字旁边的那个数字\n\n卡牌是原材料。成品为Steam级，且Valve以套为单位设定价格。\n\n100Steam 级别\n目标高度——拖动或使用方向键\n一套的价格，美元\n\n$0.20 是本次统计中最便宜的全套，$0.74 是中位数，$1.70 是平均数。该数据仅涵盖卡牌——绝不包括 $5.00 解锁内容或游戏许可证。\n\n55,000需要XP\n550已消耗的整套产品\n110值得收藏的游戏，自己刷资源\n$407.00按那个价格计算，卡片的成本是\n1,100烧毁的掉落奖励，最低值\n$5,500.00$5.00 解锁，前提是未重复使用该账号\n已消耗的完整套装，等级 1 至 1,000\n\n一个徽章工艺品 = 一套完整套装 = 100 XP。同一等级区间内，每上升一个等级所需的XP比其下方等级多100 XP。\n\n0\n12,625\n25,250\n37,875\n50,500\n1\n250\n500\n750\n1000\n667\n550 sets\n\n等级并非Valve会忽略的装饰品。它与账号紧密绑定。根据Valve自己的《交易卡常见问题解答》中关于制作徽章能获得什么的说明：“100XP，这可能会使你的Steam级提升。”如果您的Steam级提升，好友列表的上限将增加5人，而且你可能还能解锁使用“展示区”自定义个人资料的功能。 关于补充包：“你的Steam等级会提高获得卡包掉落物的概率：10级：+20%……50级：掉落率提高100%（即掉落率翻倍）。”\n\n因此，该等级决定了两件事——0—控制：你可以添加多少好友，以及免费卡牌落入你库存的速度。 后者具有复利效应——你消耗的卡组越多，平台向你提供新卡的速度就越快。Valve将这种再投资循环融入了产品设计中。\n\n汇率是固定的且已公布。制作一枚徽章需消耗一套材料，并可获得100 XP；“同一款游戏最多可以制作五套装备。” 每提升10级，所需经验值就会增加。由此得出的结果如下，且以下数据均非估算值：\n\nSteam 级别\t它消耗的整套产品\t必须入手的游戏，才能自己制作这些游戏\t创下有记录以来的最低价（$0.20）\t在中位数集 ($0.74) 上\t比例\n10\t10\t2\t$2.00\t$7.40\t\n50\t150\t30\t$30.00\t$111.00\t\n100\t550\t110\t$110.00\t$407.00\t\n200\t2,100\t420\t$420.00\t$1,554.00\t\n500\t12,750\t2,550\t$2,550.00\t$9,435.00\t\n667\t22,579\t4,516\t$4,515.80\t$16,708.46\t\n\n667 并非假设值。这是公开目录中某个机器人宣称能带领客户达到的最高等级，该机器人持有横跨 6,117 款游戏的 33,359 套卡组。 第四列是该卡组与普查中任何地方最便宜的完整卡组相比的价格；第五列则是与中位数相比的价格。这两者均为仅卡牌本身的市场价格，完全不包含 $5.00 解锁费用和游戏许可证费用。\n\n曲线是如何得到验证的，因为 Valve 并未公布这一结果\n\nValve 表示徽章获取率（“每获得100 XP，即可额外提升Steam级”) 然后对其进行套期保值——“（至少一开始是这样）” — 且不公布升级情况。 上文使用的升级曲线是标准曲线，即每个十级区间内的等级，其所需经验值比下方区间高100 XP。该曲线是根据目录数据验证得出的，而非凭空假设：对于每个其宣传的最大值受库存限制（而非每局五件工艺品的上限）的机器人，根据该曲线计算出的水平与该机器人宣传的水平完全一致 — 541 对 541，494 对 494，464 对 464。而在上限生效的情况下，计算出的数值会高出几个等级，这正是那种同时取决于每场比赛阵容深度的上限应有的表现。 对于 667 级以上的曲线，本文不作任何论断。\n\n阅读第02节旁边的等级表，就能看出该业务的全貌。 要将一个账号提升至500级，必须组装12,750套完整套装。每套套装至少需要消耗两个账号的掉落配额，且每个账号都已通过$5.00关卡，并拥有该游戏。某个个人资料顶部显示的一个虚荣数值，其下方至少有 25,500 个已消耗的掉落配额。 Valve 不会在这笔交易中亏损。Valve 是该交易每个部分的交易对手方。\n\n04 — 统计数据\n该条款并非笼统地描述农业，而是逐一列举了农业的各项内容。\n\n§ 4.C 并非一条通用的反机器人条款。其中列举的示例依次列出了卡片农场产生的两样东西。\n\n“您不得以任何形式使用脚本、机器人、宏或其他非人工控制的系统（以下简称‘自动化工具’）以任何方式与 Steam 上的内容和服务进行交互，包括但不限于：\n\n实现 Steam 账户创建流程的自动化，\n伪造游戏数据（例如虚增胜场或负场、经验值、游戏时长），\n在没有用户真实参与的情况下获得奖励或进度，\n“通过自动化手段参与评审机制（如同行评审或‘监督’），包括通过预设脚本而非基于充分信息的判断来影响结果或举报用户。”\n—Steam 订阅协议 第4.C条 ↗ 已归档 2026-09-24 ↗ · 摘录并原样引用 2026-09-22\n“……玩耍时间”\n\n空闲时间并非虚幻的时间。ASF 常见问题解答（FAQ）对此问题给出了直截了当的回答——“为什么通过ASF刷来的游戏游戏时间不会增加？” — 附：“确实会，但不是实时更新的。Steam会以固定间隔记录你的游戏时长，并按计划进行更新……通常大约每30分钟更新一次。”\n\n这些时长会记录在 Valve 的记录中，显示在 Valve 的商店页面上，并计入 Valve 自行发布的在线玩家数量中Steam 图表 ↗ 已归档 2026-09-23 ↗. 在这些数据中，闲置账号与活跃账号无法区分。该平台对外公布的参与度数据，是基于一个包含非活跃账号的用户群体计算得出的——根据该平台自身的规则，这些非活跃账号也被计入其中。\n\n“……缺乏用户真实的反馈”\n\n这是由Valve撰写的“闲置卡牌掉落”的定义。它同时也定义了Steam等级、该等级对应的徽章、补充包获取资格以及随附的个人资料经验值——ASF常见问题解答已对此进行了确认“保留获取补充包的资格”, 因为它的登录方式与官方客户端相同。\n\n因此，奖励机制与禁止行为是从两个角度看待的同一机制。Valve将奖励设定为由时间而非技能产生，随后又制定了一条条款，禁止通过除个人花费该时间以外的任何方式产生奖励。\n\n05 — 商业用途的陷阱\n每张“养殖卡”的每次出卡，都是许可证所禁止的出卡行为——而Valve会在出口处收取费用\n\n这是“负责任地”刷卡无法解决的问题。该许可证仅限个人非商业用途，而一张卡只有在不再属于个人使用时，才值得去刷。\n\n§ 2.A — 许可\n\n\"Valve 特此授予，且您接受，一项非排他性许可和权利，允许您为您的个人、非商业用途 （除非本协议或适用的订阅条款中明确允许商业用途）。”\n\n§ 2.G — 限制\n\n“您无权：……（iii）”将内容和服务或其任何部分用于任何商业目的，但本协议其他条款（包括任何订阅条款或使用规则）中明确允许的情况除外。\"\n\n§ 3.D — 费用\n\n\"Valve 可能会对订阅市场中的交易收取费用。 “任何费用都将在交易完成前向您披露。”\n\n将这三点综合起来看，该职位便已关闭\n\n一张被保留的卡牌对农场来说毫无价值。一张被出售、交易或捣碎成宝石的卡牌，则已被用于创造价值——而Valve在其执法函中已明确说明了这一点：一名运营170个机器人的用户被告知，该账号“曾被用于在Steam上非法收集收藏卡，以及相关活动，不仅限于商业活动。” 在这种情况下，卡片已进入市场。销售已结算。手续费已收取。禁令是在此之后才下达的。\n\n那扇门的费用并非 15%。在代管卡上，该费用可达三分之二。\n\n§ 3.D 保留条款“一笔费用”. 在农场实际生产的卡片上，这笔费用与广告中宣传的~15%相去甚远。社区市场收取的5% Steam 交易费和 10% 游戏费，每项的最低限额均为 $0.01 （摘自 Valve 的社区市场常见问题解答）。在一张标价为一美分的卡片上，这些底价是 价格：买家支付3美分，其中2美分是手续费。由于采用向下取整规则，表面上的15%实际上变成了一项实际征收的费用，该费用会攀升至66.7% 这正是卡片市场的真实写照——每张卡片仅值几美分。\n\n根据卖方的要价计算的“社区市场”交易实际佣金\n\n5% Steam + 10% 局，每局至少 $0.01。阴影区域是交易卡实际进行的区间——每张卡大约在 $0.03–$0.05 之间。\n\n0%\n10%\n20%\n30%\n40%\n50%\n60%\n70%\ncards\n$0.01\n$0.10\n$0.20\n$0.30\n$0.40\n$0.50\n66.7%\n卖家希望\tSteam 5% (第 $0.01 分钟)\t第 1 场比赛 (第 0 分钟)\t买方支付\t综合费用\n$0.01\t$0.01\t$0.01\t$0.03\t66.7%\n$0.03\t$0.01\t$0.01\t$0.05\t40.0%\n$0.05\t$0.01\t$0.01\t$0.07\t28.6%\n$0.08\t$0.01\t$0.01\t$0.10\t20.0%\n$1.00\t$0.05\t$0.10\t$1.15\t13.0%\n\n10%的游戏费用归发行该卡片的应用程序所有；5%归Valve所有，而在Valve自有游戏及基础库存道具上，全部费用归Valve所有。 无论哪种情况，钱都流出了“农场主”的口袋——卖出一张三分钱的卡片，只能收回一分钱，却要交出两分钱。将这一比例乘以“农场”产生的数十万笔五分钱以下的卡片销售额，“Valve可能收取的费用” 这是一种商业模式，而不是脚注。来源：Steam 社区市场常见问题解答 — 费用 ↗ 已归档 2026-09-21 ↗, 读作 2026-09-22；该曲线基于上述两项已公布的利率及其 $0.01 下限进行算术计算。\n\n无论该工具如何配置，都无法规避这一规定。即使由一个人、在一个账户上、以完全克制的态度运行该工具——但只要该人将一张通过刷卡获取的卡片出售以换取钱包资金，第2.G条中的同一条款对其适用的程度，就与对拥有上万个账户的运营商一样。 因此，Valve 预留了一项可针对其市场上的几乎所有卡牌卖家援引的违规条款，却拒绝将其适用于实际上所有卖家。以这种频率执行的规则，就不是规则了。那只是一个选项。 本展览提出的问题并非“为何对卡农行为予以容忍”； 而是为何针对出售一张卡片的个体用户会采取同样的措施，而这些卡片所滋养的商业卡牌经济——交易服务、升级机器人、批量卖家——却公然运作，其中最大的群体之一甚至由一名 Valve 员工负责管理（§ 08）。规则的执行针对的是小额持有者，却对机器网开一面。\n\n06 — 执法记录\n毫无预兆，一波接一波，沿着电话号码传播下去\n\nValve将“无须通知即行使权力”的规定写入了协议本身，紧接在自动化条款之后。\n\n\"Valve 有权因任何非法行为、构成作弊或自动化操作的行为，或违反 Steam《在线行为准则》的行为，限制或终止您的账户或某项订阅服务。您承认，Valve在终止您的订阅和/或账户之前，无需向您发出通知。\"\n\n—Steam 订阅协议 第4.D条 ↗ 已归档 2026-09-24 ↗ · 经核实，原文照录 2026-09-22\n\n1,000+ 机器人 · 已被禁止交易。 “该账号似乎曾被用于管理一个机器人账号网络。使用机器人账号的行为违反了《用户协议》第Steam条。”\n\n170多个机器人 · 永久封禁，2017年冬季特卖。 “该账号曾被用于在Steam上非法收集收藏卡，以及相关活动（不仅限于商业活动）。该账号已被永久封禁，Steam客服无法就此问题提供进一步协助。”\n\n120多个机器人 · 已被永久封禁。 “该账号及其他账号被用于对我们的网络基础设施进行流量攻击，这违反了Steam在线行为准则。”\n\n— Steam 支持信息转载自 ArchiSteamFarm 常见问题解答（FAQ）中的“有人因此被封号吗？”一节。来源 ↗ · 经核实，原文照录 2026-09-22\n案例 4 — 2025 年 6 月，VAC 禁止闲置的 CS2\n\n该项目自身的跟踪器中记录了一起发生在上述三起事件之后的情况：那些仅通过该工具让《反恐精英2》处于空闲状态的账号收到了VAC 禁令 ——这里指的是反作弊类，而非管理类。维护者的观点是，闲置状态不会导致这种情况，因为它“除了告诉 Steam 我们正在玩某款游戏之外，什么也没做。” 原因尚有争议。但这些账号被封禁这一事实则毋庸置疑。\n\n—ArchiSteamFarm 讨论 #3440，于 2025 年 6 月 26 日开启 ↗ · 阅读 2026-09-22\n\n主账号是如何被注销的\n\n在同一讨论串中，一位项目合作者描述了该规则的适用范围：账号可能会被封禁“按链”，如果他们使用的是同一个电话号码 —“这可能只是一个 VAC 封禁，但会波及到与被封禁账号相关的‘干净’账号。”\n\nSteam Guard 需要一个电话号码。矿池是基于操作员的电话号码构建的。因此，执法行动不会止步于一次性账户：它会沿着共享标识符向上追溯，直至找到那个存储了资源库、好友列表和库存的账户。 这就是一位项目协作者所描述的机制：单次行动如何同时清除操作者的主账户及其农场——这也正是为何在一次打击浪潮中，损失的账户数量并非仅以 $5 个账户来衡量。 （由一位项目贡献者在 ASF GitHub 讨论 #3440 中描述；目前尚无官方 Valve 确认或正式先例记录。）\n\n同一段文字，相隔五年，出自三位不同的经纪人之手\n\n将农业活动视为违规行为的条款——即对个人非商业许可的商业用途——并非仅适用于农场。这是Steam因交易行为关闭账户时给出的标准理由，且该理由以模板形式呈现。 以下是三个案例，均由收到通知的用户公布，时间间隔五年，来自三名不同姓名的代理。\n\n来自 Steam 客服的留言，9月29日 下午7:56\n\n“您正在登录的账户因违反《Steam 订阅协议》条款已被锁定。根据交易记录、社区举报及其他因素，该账户已被认定用于商业用途。\n\n此锁定状态为永久性，Steam 客服无法就此为您提供进一步帮助。\n\n由于我们已提供了所有掌握的信息，因此我将关闭此帮助请求。请注意，您将不会收到关于此问题的进一步回复。\n\n此致，\n“哈尔”\n\n此求助请求已关闭。\n2020年9月29日。由收件人发布，并附有评论“RIP Trading。” —@gergelyszabo94 ↗\n支持团队的消息 Steam 发布于 7月12日 22:41\n\n“您正在登录的账户因违反《Steam 订阅协议》条款已被锁定。根据交易记录、社区举报及其他因素，该账户已被认定用于商业目的。”\n\n此锁定状态为永久性，Steam 客服无法就此为您提供进一步帮助。\n\n由于我们已提供了所有掌握的信息，因此我将关闭此帮助请求。请注意，今后若再次提交关于账户锁定的帮助请求，可能会在未作回复的情况下被关闭。\n\nSteam 支持\n“Vido”\n\n该求助请求已结束。\n2024年7月12日，葡萄牙语界面。收件人是一名职业CS2选手：“已经联系了Steam客服，但只收到自动回复……既无法玩Faceit，也无法参加职业比赛。” —@prcs25 ↗ 已归档 2024-07-15 ↗\n引自收件人，r/steamsupport\n\n“您好，您正在使用的该账号因违反《Steam订阅协议》条款已被锁定。根据交易记录、社区举报及其他因素，该账号已被认定用于商业用途。\n\n此锁定状态为永久性，Steam 客服无法就此为您提供进一步帮助。\n\n由于我们已提供了所掌握的所有信息，现将此求助请求关闭。请注意，今后针对该账户被锁定问题提交的求助请求可能会在未作回复的情况下被关闭。\n\nSteam 支持\n“莎莉”\n\n已收到三次，分别来自三次不同的请求。\n2025年3月29日。该用户并非在对账户锁定提出申诉——其账户连同电子邮箱一同被盗，因此正在请求恢复访问权限：“我不是在问封号的事，也不对此提出异议，我只是想登录我的Steam账号……Valve每次收到我的请求时，都会直接复制粘贴这同一条回复，然后关闭请求。” —r/steamsupport ↗, 收录于本研究自身的投诉语料库中\n\n逐字逐句，逗号不差，历时五十五个月，历经三位代理人，跨越两种交互语言。正文中唯一的修改是最后一句中“2020年”与“2024年”之间的表述调整，从“您将不会收到进一步的回复” 到“今后的求助请求……可能会在未作回复的情况下被关闭。” 无论这些决定是通过何种程序做出的，这封信都未能记录下这一过程。 所列出的理由是“交易、社区报告及其他因素”——一个类别、一份来源不明的报告，以及未指明的其余因素。\n\n另有五起案例，采用相同方式收集。前三起属于同一类别且结果相同；后两起虽出自同一部门，但用相同的措辞回应了不同的规定：\n\n日期\t该账号做了什么\t发生了什么\t来源\n2021年12月4日\t在 Buff 上买卖 —“我除了在Buff上做些买卖，也就是所谓的P2P交易，没干别的。”\t社区禁令：禁止交易，禁止买卖，高价库存被冻结\tr/csgomarketforum ↗ 已归档 2025-03-27 ↗\n2021年12月6日\t通过Buff和Bitskins进行的单向P2P交易，用于装备配置和升级交易\t永久性商业用途锁加社区锁：“卡在一种伪隐身模式里……我的个人资料也卡在‘私密’状态了”\tr/GlobalOffensiveTrade ↗ 已归档 2021-12-06 ↗\n2024年12月20日\t该账号自2017年起持有，累计游戏时长达数千小时；在社区交易平台上交易主题装备套装并进行升级换装\t永久封号（含社区封号），不作事先警告，也不计入封号记录；支持“称其决定是最终决定”, 回复为自动生成\tr/csgomarketforum ↗ 已归档 2025-06-27 ↗\n2024年12月23日\t一位久未登录的用户通过VPN添加了钱包资金，此前已有一年未登录“仅用于一般的网络安全”\t永久社区禁令，附带完全没有给出任何理由:“该禁令是永久性的，他们无法提供更多信息，且后续工单可能会在未予回复的情况下被关闭。” 196个赞，340条回复\tr/steamsupport ↗\n2026年8月4日\t多年来一直在伊朗购物；该作者表示他们从未发过帖，也从未使用过“市场”板块，更从未使用过论坛\t社区访问已被锁定直至2038年 超过“受制裁地区”; 该工单由一名名为Azul的客服人员关闭。一年前，该账户通过同一伊朗IP地址提交的退款申请曾获批准。图书馆和钱都归Valve所有。\tr/pcgaming ↗\n\n最后一行的规则与其他情况不同——涉及制裁合规，而非商业用途——将其纳入是因为处理结果的模式完全一致：归类、无证据、不可上诉、工单已关闭。这还提出了一个其他情况未涉及的问题：如果为该账户提供服务属于违法行为，那么多年来收取的款项也就属于非法收入。 这两种立场中必定有一种是错误的，而且只有其中一种会给客户造成经济损失。\n\n这八封信均于2026-09-22被查阅——其中2021年和2024年12月的帖子是通过互联网档案馆的快照获取的，其余则通过Reddit的公共前端获取，因为Reddit拒绝了数据采集方提出的直接请求。 2020年和2024年的两封信件是根据原始帖子所附的截图转录的，这些帖子目前仍然存在。本调查并未指称这些账号在任何方面是无辜的或有罪的——这恰恰是关键所在。无论是读者还是监管机构，都无法从这封信中看出端倪。\n\n关于数据来源的说明——运营商层面的损失\n\n本调查所采访的运营商报告称，损失金额约为每个账户5,000至10,000个 在单次执法行动中，与该农场一并查封了主要账户。该民意调查在此作为第一方报告记录在案，而非调查结果。 该数值未公布样本量，没有固定的采集日期，也不进行逐账户验证，且本页上的其他数值均不以此为依据；第02节中基于该数值的两行已作相应标注。\n\n之所以明确指出这一点而非一笔带过，有两个原因。上述的“链式封禁”机制正是对这一模式的官方解释。 监管机构可以从Valve处调取那份能够一锤定音的记录：有多少账户因自动化处理而受到影响，分别属于哪几波处理，以及这些账户在被关闭前在该商店分别消费了多少。在该记录出现之前，这一数据将维持现状——被报道、被归因，却未得到证实。\n\n07 — 不对称性\n同一张书桌的两侧\n\n将这一举证标准与该机构对其自身支援行动所采用的Valve标准进行对比。右侧一栏是本档案本身的事件登记册，转载时保留了其中原有的保留措辞。\n\n一位客户，用于交易\n\n2020年至2026年间记录的8例病例\n\n行为\n在第三方电商平台上买卖商品；其中一例根本不存在任何行为——该账户是被盗的。\n所示证据\n无。“基于交易情况、社区反馈及其他因素。”\n通知\n无。Valve 在第 4.D 节中已对此作出保留：“Valve无须在终止合同前向您发出通知。”\n上诉\n“此锁定状态为永久性，Steam 客服无法就此为您提供进一步帮助。”\n门票\n根据首次回复已关闭。后续请求“可能会在未予回复的情况下关闭。”\n覆盖范围\n个人资料、好友列表、聊天、应用商店、背包，以及所有用真实货币购买的物品。\n时长\n永久的。\n一支自动化机器人舰队，用于处理大容量任务\n\n694,673 91个机器人中公开库存的完整套装\n\n行为\n在数千个账户上同时运行自动化的无头脚本，以使卡牌闲置、批量制作徽章，并以工业规模进行卡组交易。\n所示证据\n公开发布的机器人目录（steam.supply、SteamLvlUp）以及拥有数百万成员的公开群组。\n通知\n零干预。88.97% 不受任何形式的禁止; 剩余的禁令中，有 0 项仅是表面文章。\n上诉\n无需此项。车队可在长达数年的生命周期内持续运行，不会中断。\n门票\n—\n覆盖范围\n无限制的库存交换、徽章升级和市场流动性。\n收益为 Valve\n$26.8M+ 最低店铺消费额（每个账户需达到 $5.00 门槛）加上 15% 次社区市场交易扣减。\n这引出了一个问题，说白了就是\n\n任何手动交易卡牌或物品的个人用户，都将根据第4.C条（自动化）或第2.G条（商业用途）面临永久且不可上诉的封号处罚。而一个通过数千个账号运行无头机器人的自动化刷分团伙，却能公然活动且保持着88.97%的零封号率。Valve 是这两者的受益人。\n\n这种不对称性体现在经济层面：个人交易者从平台中获取价值，而自动化的信用卡车队则向Valve的店铺消费通道注入数百万资金（每个账户$5.00），并推动每次转售产生的交易手续费。监管并非遵循书面规则，而是遵循收入模式。\n\n08 — 治理\n谁负责监管卡牌经济\n\n本报告中反复出现的一个发现——即围绕Steam的第三方层的人员来自Steam内部——在卡片经济中同样成立，并且这一现象最终指向一个特定的结论： 没有任何独立第三方能够统计Valve的执法行动究竟产生了什么实际效果，因为能够进行统计的一方就位于该层内部。以下所有事实均摘自Valve在2026-09-22上的公开群组及个人主页，任何人都可以在浏览器中复现这些内容。\n\n一名 Valve 员工负责管理最大的卡牌交易群组Valve 名员工\n\n卡牌交易 ↗ 在自身的页眉中将自身描述为“Steam 卡片交换官方群组” 并携带97,114名成员. 该群组列出的版主——即掌握该群组管理权限的账号——是Mickmane,SgtFopper 以及afarnsworth ↗.\n\n根据 Valve 自身网站的标记，该最后一个个人资料被标记为 Valve 的员工——该页面显示class=\"profile_header_valve_employee\" — 其位置为华盛顿州贝尔维尤，属于Valve,Steam 以及Steam 集换式卡牌小组 组。SteamID64 76561197960434622，自2003年9月12日起成为会员。\n\n这一观察是结构性的，而非针对个人的，而且它是不 一个需要澄清的地方——卡牌交易群的版主并没有运行机器人，而且这里没有任何迹象表明情况并非如此。关键在于第07节. Steam “卡牌交换”是一项第三方商业卡牌服务；通过第三方服务交易卡牌，正是Valve根据相关规定对普通账户实施永久封禁的具体行为“基于交易、社区报告及其他因素，用于商业目的。” 一名编号为 Valve 的员工在该服务拥有 9.7 万名成员的官方社区群组中担任公开的版主职务。\n\n本文并未对任何个人提出不当行为的指控，且未对该角色具体职责作出任何推断。这种不对称性本身即为调查结果： 当普通账户涉及第三方卡片或皮肤服务时，处理结果是关闭工单并永久封禁，且未提供任何证据；而当涉及该服务时，一名 Valve 员工被列入版主名单，且该安排在 Valve 自身发布的页面上清晰可见。 所提出的问题与本档案其他部分提出的问题一致：如果存在书面授权，请出示；如果不需要书面授权，请以书面形式说明，因为第06节的八名人员被告知了相反的情况。\n\n禁用列表层及其管理方志愿者版主第三方服务\n\nSteambans.com 群组（存档）↗ (直播 ↗ 已归档 2025-12-03 ↗) 在其现存的类群描述中记载了其谱系：“Steambans.com Steam 的官方社区群组。SteamBans.com 是一项基于传统理念的全新服务。 全球封禁名单在VALVe旧版WONID程序中已运行多年。当系统升级为STEAMID时，我们自然而然地开发了一项专门针对这一新系统的服务。但我们还希望做得更多。*. 这是已于2013年关闭的Steambans的存档页面。\" 其列出的管理员包括devicenull 以及killahinstinct_ ↗.\n\n该管理员账户是不 一名 Valve 员工——其身份未被标记为员工。这是一名地位格外显赫的志愿者：作为社区版主 （414名成员，被描述为一个群组“由 Steam 的社区版主创建”)，来自维基协调员，来自Steam 社区市场，以及包括以下在内的 Valve 个节目组和预发布组：Valve 管道,Steam 客户端测试版,移动端身份验证测试版,新 Steam 社区测试版,Steam 实验室,Steamworks 以及举报诈骗网址.SteamID64 76561197960794555.\n\n此外，在该圈子内，还有一位用户将“Steambans”直接显示在其公开群组成员列表中：msart ↗ (队伍名单 ↗),SteamID64 76561197977933359，其个人简介中这样写道：“我运营 steamid.uk 以及许多其他与 Steam 相关和不相关的网站”，并运营着一个由十六个团体组成的关联网络——SteamIDcouk （主组“Sid 网站”），SidAdmins,SidBans,steamideu简体中文（大陆）,Steam3ID,s-id 以及SArchive 在其中。\n\nsteamid.uk 自身就使用了相同的编号。其常见问题解答（FAQ）中写道：“谁创建了 SteamID？SteamID 网站、网络基础设施和安全系统均由 76561197977933359 负责管理。” 再往下看两个回答中提到了数据来源：“SteamID 主要利用 Steam Web API 进行数据收集。” 该页面介绍了分布在不同主机上的多台专用服务器、异地开发服务器、存储服务器和文本搜索服务器，以及一个独立的备份设施。\n\n经互联网档案馆保存的记录核实：该2025年12月3日 Steambans 群组快照 ↗，该2024年9月14日的操作员档案快照 ↗，以及steamid.uk 常见问题解答（2026年4月1日快照）↗，与直接从 2026-09-22 读取的数据相匹配。\n\n这究竟意味着什么，又意味着什么不是\n\n封禁名单、SteamID 解析和卡牌交易是决定谁值得信赖、谁可被识别以及某件物品价值如何的三大服务。这三项服务均不由 Valve 运营。在每一艘飞船上，掌舵者都来自Valve的轨道内部： 卡片服务官方群组管理员名单中一名被标记的 Valve 员工；一名拥有预发布程序访问权限、管理封禁名单群组、在社区服务多年的 Valve 社区管理员；以及由同属该圈子的一名个人运营的身份识别服务。 三项服务、三个控制界面、三个人 Valve 早已赋予其权威。\n\n加入该团体并不等同于受雇，以上内容均不构成任何指控。 这是一个治理事实，也是普通抗辩之所以成立的原因——那些是第三方，我们无法控制他们 ——必须经过检验，而非直接采纳。掌舵者对Valve并不陌生。Valve有资格说明它究竟向他们提出了什么要求（如果确实有要求的话）；外界无人能够查明真相。\n\n没人算过。这就是调查结果。\n\nSteam ID 空间是一个连续的整数范围。遍历该空间并报告被封禁的账户数量、受限的账户数量以及因交易禁令而被冻结的库存数量，这并非一项研究项目——它只是一个循环和一个 API 密钥。Valve 直接分发该密钥，在steamcommunity.com/dev/apikey. 然而没有独立机构发布该人口普查数据。 既不是监管机构，也不是记者，既不是学者，也不是消费者组织。关于Steam执法规模的唯一公开数据，就是Valve选择提及的那些。\n\n该功能并非不存在，而是被保留了下来。那个能够大规模解析和索引ID空间的服务——steamid.uk——在其常见问题解答中指出，它“主要利用 Steam Web API 进行数据收集” 并在多台专用服务器、异地存储设备、文本搜索服务器以及独立的备份设施上运行。 该系统由一名个人运营。其“黑名单”兄弟群组由一位在Valve社区任职已久的版主共同管理，该版主拥有访问Valve预发布程序的权限。唯一有能力公布计数结果的政党处于Valve的势力范围之内，却并未公布该结果。\n\n这份档案在其他地方发现的情况也完全一样。任何负责就Steam经济作出关键决策的服务——无论是判定谁值得信赖、谁可被识别、某项物品的价值几何，还是决定谁被禁止——名义上都是第三方，实际上却与Valve紧密相连。Steam “卡片交换”并不例外；它只是这一模式的又一个实例。 之所以可以提出“这些是独立操作”这一辩护理由，恰恰是因为至今无人能够用具体数字来验证这一说法。\n\n1088万账户普查：88.97% 未处理\n\n对ArchiSteamFarm的安装基数进行了审计，涉及Valve的GetPlayerBans 终点（10,880,610 个账户，55 分钟）。仅该无限制子集就代表$26.8M+ 最低店内消费额（$5.00 准入门槛）。9,680,599 账户（88.97%）不受任何形式的限制，而其余的99.8%仅实施了名义上的社区禁令，自动交易功能仍保持正常运行。\n\n5,360,499非受限 ASF 成员（显示为 Steam 的数量）\n10,880,610已扫描的 API 条目总数（受限 + 不受限）\n9,680,599从未被封禁过 (88.97%)\n1,200,011携带任何 Steam 禁令 (11.0%) — 99.8% 外观\n55 分钟要对整个人口进行普查，一个关键点是\n取证证据与深度普查\n\n详细的人口统计数据细分——包括封禁类型分布图、执法时的账号使用时长、创建年份分组（2020–2026）以及用户自报的地理位置信息——已发布在专门的普查调查报告中。\n\n查看完整的10.88M禁令普查报告（附件VI）→第4节 — 资产ID屏蔽 →\n\n因此，需要提出的问题是——而这个问题只有 Valve 才能回答：撤销了哪项标识符或能力？具体是在何时？由谁决定？这对目标运营商产生了哪些可量化的影响？ ——而这与它对所有试图进行人口统计的外部人员产生的影响形成了鲜明对比。一项终结独立审计的变革，即便以安全措施的名义宣布，也不会因此变得中立。这正是上段所述的人口普查不复存在的原因。\n\n09 — 方法与局限性\n读到了什么，以及没有主张什么\n\n本页上的每条引文均摘自 2026-09-22 上的实时数据源，并原封不动地转载。此处内容均未来自数据抓取、市场凭证或私有数据集。\n\n这四个数据集及其相关运算\n\n每条都是一个单独的公共请求，可在终端上重现。未使用任何账户，未登录任何市场，也未调用任何需要凭据的端点。\n\n数据集\t来源\t据此计算出了什么\n卡片统计\n13,876 场比赛\tSteam Card Exchange 发布的徽章价目表，即用于生成其公开价格页面 ↗ 已归档 2026-08-04 ↗\t发行卡牌的游戏、每套卡牌的数量、不同的卡牌类型，以及每套完整卡牌的市场价格。中位数和“0”的总和构成了本次调查的计算基础。\n游戏价格\n13,713 已解决\tValve的自有公共商店端点，store.steampowered.com/api/appdetails,抄送=美国, 仅价格字段, 分批处理\t带卡牌游戏的建议零售价中位数及分布情况；以及成品卡组销量超过游戏本体销量的游戏数量。\n机器人股票\n91 个机器人，694,673 套\t位于steam.supply/CardBots ↗, 按显示内容阅读，无需登录\t库存中的总套数、最低卡片数量、掉落容差下限，以及不同账户中每个机器人的分类下限。\n交叉核对\n21 个共享机器人\tsteamlvlup.net/cardbots ↗ 已归档 2026-02-10 ↗，一个收录了这些机器人的独立目录\t仅供核实。对于两份清单中均列出的21个机器人，Aggregate Stock同意0.03%; 单个机器人之间最大的差异为 1.36%，这与两次相隔数分钟的实时库存爬取结果一致。\n\n根据第二个目录的要求，需注明来源：数据由SteamLvlUp，根据以下许可协议发布：CC BY 4.0 已归档 2026-09-23 ↗; 此处仅将其作为对第三方库存数据的独立核查依据，且进行了修改——即将每台机器人的数据行进行汇总后进行比较，而非原样复制。Steam 卡牌交换（Card Exchange）和蒸汽供应（steam.supply）已在上文通过链接注明出处。 游戏价格为Valve本人所定。卡牌、游戏及套装的名称和图片归Valve或各出版商所有，作为市场事实予以转载，既不主张所有权，亦未获得授权。\n\n有两项原计划的测量未进行，且未以其他数据替代。Steam自身的“社区市场”终点——价格概览,搜索/渲染,价格历史 — 不向数据采集主机返回任何内容，而 Steam 社区讨论页会向其返回 HTTP 403 状态码，因此本页上的所有数据均非来自实时市场数据。原本用于统计每日重置时卡牌掉落量的“sale-volume”方法需要 Steam 登录会话；此次调查的调查报告中指出，未使用任何市场凭证，且该陈述已被保留。 “机器人库存底”是指无需机器人即可测量的部分。\n\n一手资料\n\nSteam 订阅协议 ↗ 已归档 2026-09-24 ↗ — § 2.A、§ 2.G、§ 3.D、§ 4.C、§ 4.D。\nSteam 支持 — 受限用户帐户 ↗ — $5.00阈值和受限特征列表。\nValve — Steam 交易卡常见问题解答 ↗ — 取消开箱机制和 $9 的免费游玩率。\nArchiSteamFarm 常见问题 ↗ 和讨论 #3440 ↗.\nSteam 社区群组和个人资料页面，直接阅读，见第08节。\nsteamid.uk 常见问题解答，互联网档案馆快照 2026-04-01 ↗.\n第06节列出了2020年至2026年间由收件人发布的8份Steam支持锁定通知，并附有相关链接。\n\n未主张的内容\n\n未对Valve通过卡片刷量产生的收入进行估算。未就任何工具的活跃账户数量作出声明，而139万次掉落配额是不 农场名下账户的统计数据——参见第02节的注释。未指控任何个人有不当行为；若提及某人姓名，系以其公开的Steam用户名、以该人公开的身份，从其发布的页面Valve中引用。 第06节中列出的八个被锁定账户，均未被认定为无辜或有罪；该调查结果针对的是信件本身，而非账户。第02节中的运营商损失数据为第一方报告，并在采购说明. steamid.uk 的常见问题解答（FAQ）引自互联网档案馆的快照，因为该网站的实时页面需要通过机器人验证才能访问。本文并未声称曾有人尝试进行封号统计但遭到压制——仅指出目前尚未有此类统计数据公布。上图中 667 以上的 Steam 级曲线未纳入模型。\n\n为什么工具不是主体\n\nArchiSteamFarm 指出，它“未获得Valve的授权” 而且本页面并未对其提出任何指控。 它被用作衡量标准，因为在这个经济体系中，它是唯一一个公开且以书面形式记录运作机制的参与者。Valve只需用一个段落就能概括全部情况：公布它授权了哪些商业自动化项目，以及针对其余部分，每位操作员采取了哪些具体措施的记录。\n\n接下来阅读：市场本身是如何定价的 → ·价格梯度与挂牌上限 → ·编号为 Steam 的商品将不提供 →",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "机器人农场并不是Valve商店里的一个漏洞。它是一个客户."
          },
          {
            "level": 2,
            "id": null,
            "text": "农场究竟是什么，一步一步来"
          },
          {
            "level": 3,
            "id": null,
            "text": "买入"
          },
          {
            "level": 3,
            "id": null,
            "text": "购买游戏"
          },
          {
            "level": 3,
            "id": null,
            "text": "空闲\n该工具以无交互模式将该账户登录到 Steam 网络，“解析您的徽章”, 生成可收集头衔的列表并开始“游玩符合条件的游戏，并定期检查游戏是否已经完全刷完。” 其维护者对该机制的描述：它“除了告诉 Steam 我们正在玩某款游戏之外，什么也没做。”"
          },
          {
            "level": 3,
            "id": null,
            "text": "药水用完了\n每个标题都是有限的。“每款游戏都有固定的卡牌掉落数量。一旦你集齐了所有卡牌（约占整套卡牌的一半），这款游戏就不再适合刷卡了。” 想要持续生产的农场必须不断购买地契。地契的供应量受到购买行为的限制——这是设计使然，且对Valve有利。"
          },
          {
            "level": 3,
            "id": null,
            "text": "提现\n该卡片会通过以下三种途径之一离开：在社区市场上售出、被交易出去，或被压制成宝石。每种情况均属于订阅市场交易或交易行为，第3.D条对此规定如下：“Valve 可能会对订阅市场中的交易收取费用。” 正是这一步导致了整个事件构成违规——参见05."
          },
          {
            "level": 2,
            "id": null,
            "text": "一个农场在赚到一分钱之前，就已经支付了 Valve"
          },
          {
            "level": 3,
            "id": null,
            "text": "所购物品的实际大小是多少"
          },
          {
            "level": 3,
            "id": null,
            "text": "一个集合有多大"
          },
          {
            "level": 3,
            "id": null,
            "text": "许可证的费用是多少"
          },
          {
            "level": 3,
            "id": null,
            "text": "该集合计算完成后返回什么"
          },
          {
            "level": 3,
            "id": null,
            "text": "694,673组坐在哪里"
          },
          {
            "level": 3,
            "id": null,
            "text": "这层楼所传达的信息与未传达的信息"
          },
          {
            "level": 3,
            "id": null,
            "text": "而且，按照Valve的价格，农业根本无法自给自足"
          },
          {
            "level": 3,
            "id": null,
            "text": "农场实际上支撑着什么"
          },
          {
            "level": 4,
            "id": null,
            "text": "游戏销量"
          },
          {
            "level": 4,
            "id": null,
            "text": "“在线”与游戏时间"
          },
          {
            "level": 4,
            "id": null,
            "text": "注册"
          },
          {
            "level": 4,
            "id": null,
            "text": "钱包余额与手续费"
          },
          {
            "level": 4,
            "id": null,
            "text": "Steam级公关"
          },
          {
            "level": 3,
            "id": null,
            "text": "而且提现本身就是一种财富流失——0——要缴两次税"
          },
          {
            "level": 3,
            "id": null,
            "text": "这不仅仅是一个瞬间，而是一个拥有多年发展根基的行业。"
          },
          {
            "level": 3,
            "id": null,
            "text": "公共机器人目录中保存的完整卡组，由 Steam 出售"
          },
          {
            "level": 3,
            "id": null,
            "text": "从顶端看，一场促销活动的徽章排行榜是怎样的"
          },
          {
            "level": 3,
            "id": null,
            "text": "即使没有促销活动，那支车队依然在那里"
          },
          {
            "level": 3,
            "id": null,
            "text": "各机器人的休眠目录"
          },
          {
            "level": 2,
            "id": null,
            "text": "另一个产品就是你名字旁边的那个数字"
          },
          {
            "level": 3,
            "id": null,
            "text": "已消耗的完整套装，等级 1 至 1,000"
          },
          {
            "level": 3,
            "id": null,
            "text": "曲线是如何得到验证的，因为 Valve 并未公布这一结果"
          },
          {
            "level": 2,
            "id": null,
            "text": "该条款并非笼统地描述农业，而是逐一列举了农业的各项内容。"
          },
          {
            "level": 3,
            "id": null,
            "text": "“……玩耍时间”"
          },
          {
            "level": 3,
            "id": null,
            "text": "“……缺乏用户真实的反馈”"
          },
          {
            "level": 2,
            "id": null,
            "text": "每张“养殖卡”的每次出卡，都是许可证所禁止的出卡行为——而Valve会在出口处收取费用"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 2.A — 许可"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 2.G — 限制"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 3.D — 费用"
          },
          {
            "level": 3,
            "id": null,
            "text": "将这三点综合起来看，该职位便已关闭"
          },
          {
            "level": 3,
            "id": "fee-ladder",
            "text": "那扇门的费用并非 15%。在代管卡上，该费用可达三分之二。"
          },
          {
            "level": 3,
            "id": null,
            "text": "根据卖方的要价计算的“社区市场”交易实际佣金"
          },
          {
            "level": 2,
            "id": null,
            "text": "毫无预兆，一波接一波，沿着电话号码传播下去"
          },
          {
            "level": 3,
            "id": null,
            "text": "案例 4 — 2025 年 6 月，VAC 禁止闲置的 CS2"
          },
          {
            "level": 3,
            "id": null,
            "text": "主账号是如何被注销的"
          },
          {
            "level": 3,
            "id": null,
            "text": "同一段文字，相隔五年，出自三位不同的经纪人之手"
          },
          {
            "level": 3,
            "id": null,
            "text": "关于数据来源的说明——运营商层面的损失"
          },
          {
            "level": 2,
            "id": null,
            "text": "同一张书桌的两侧"
          },
          {
            "level": 3,
            "id": null,
            "text": "一位客户，用于交易"
          },
          {
            "level": 3,
            "id": null,
            "text": "一支自动化机器人舰队，用于处理大容量任务"
          },
          {
            "level": 3,
            "id": null,
            "text": "这引出了一个问题，说白了就是"
          },
          {
            "level": 2,
            "id": null,
            "text": "谁负责监管卡牌经济"
          },
          {
            "level": 3,
            "id": null,
            "text": "一名 Valve 员工负责管理最大的卡牌交易群组Valve 名员工"
          },
          {
            "level": 3,
            "id": null,
            "text": "禁用列表层及其管理方志愿者版主 第三方服务"
          },
          {
            "level": 3,
            "id": null,
            "text": "这究竟意味着什么，又意味着什么不是"
          },
          {
            "level": 3,
            "id": null,
            "text": "没人算过。这就是调查结果。"
          },
          {
            "level": 3,
            "id": null,
            "text": "1088万账户普查：88.97% 未处理"
          },
          {
            "level": 3,
            "id": null,
            "text": "取证证据与深度普查"
          },
          {
            "level": 2,
            "id": null,
            "text": "读到了什么，以及没有主张什么"
          },
          {
            "level": 3,
            "id": null,
            "text": "这四个数据集及其相关运算"
          },
          {
            "level": 3,
            "id": null,
            "text": "一手资料"
          },
          {
            "level": 3,
            "id": null,
            "text": "未主张的内容"
          },
          {
            "level": 3,
            "id": null,
            "text": "为什么工具不是主体"
          }
        ],
        "links": [
          "https://help.steampowered.com/en/faqs/view/71D3-35C2-AD96-AA3A",
          "https://github.com/JustArchiNET/ArchiSteamFarm/wiki/FAQ",
          "https://steamcommunity.com/tradingcards/faq/",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260924114457/https://store.steampowered.com/subscriber_agreement/",
          "https://steamladder.com/ladder/badges/2861690/",
          "http://web.archive.org/web/20260716205303/https://steamladder.com/ladder/badges/2861690/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/farm-economy-timeline.json",
          "https://store.steampowered.com/charts/",
          "http://web.archive.org/web/20260923183013/https://store.steampowered.com/charts/",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://github.com/JustArchiNET/ArchiSteamFarm/discussions/3440",
          "https://x.com/gergelyszabo94/status/1311004678633795585",
          "https://x.com/prcs25/status/1811893857253982720",
          "http://web.archive.org/web/20240715122902/https://x.com/prcs25/status/1811893857253982720",
          "https://reddit.com/r/steamsupport/comments/1fjmgc5/what_to_do_when_your_steam_account_gets_hacked/mkelm2y/",
          "https://www.reddit.com/r/csgomarketforum/comments/r87owv/psa_my_steam_account_just_got_banned/",
          "http://web.archive.org/web/20250327203008/https://www.reddit.com/r/csgomarketforum/comments/r87owv/psa_my_steam_account_just_got_banned/",
          "https://www.reddit.com/r/GlobalOffensiveTrade/comments/r9xql9/d_recently_received_commercial_ban_for_what_seems/",
          "http://web.archive.org/web/20211206034804/https://www.reddit.com/r/GlobalOffensiveTrade/comments/r9xql9/d_recently_received_commercial_ban_for_what_seems/",
          "https://www.reddit.com/r/csgomarketforum/comments/1hhxx7m/d_permanently_locked_on_steam_for_commercial_use/",
          "http://web.archive.org/web/20250627014045/https://www.reddit.com/r/csgomarketforum/comments/1hhxx7m/d_permanently_locked_on_steam_for_commercial_use/",
          "https://www.reddit.com/r/steamsupport/comments/1hkctwt/permanent_ban_with_no_explanation/",
          "https://www.reddit.com/r/pcgaming/comments/1vf24lu/warning_to_all_gamersexpats_steam_took_my_money/",
          "https://steamcommunity.com/groups/card-trading-card-trades",
          "https://steamcommunity.com/id/afarnsworth",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/groups/steambans",
          "https://steamcommunity.com/groups/steambans",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/id/killahinstinct_",
          "https://web.archive.org/web/20240914124859/https://steamcommunity.com/id/msart",
          "https://steamcommunity.com/id/msart/groups/",
          "http://web.archive.org/web/20260401154714/https://steamid.uk/faq/",
          "https://phishdestroy.io/steam_dossier/zh/enforcement_audit.html",
          "https://phishdestroy.io/steam_dossier/zh/#evidence-blackout",
          "https://www.steamcardexchange.net/index.php?badgeprices",
          "http://web.archive.org/web/20260804200309/https://www.steamcardexchange.net/index.php?badgeprices",
          "https://steam.supply/CardBots",
          "https://steamlvlup.net/cardbots",
          "http://web.archive.org/web/20260210171205/https://steamlvlup.net/cardbots",
          "https://steamlvlup.net/",
          "https://creativecommons.org/licenses/by/4.0/",
          "http://web.archive.org/web/20260923221628/https://creativecommons.org/licenses/by/4.0/",
          "https://phishdestroy.io/steam_dossier/zh/market_economics.html",
          "https://phishdestroy.io/steam_dossier/zh/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/zh/elite_skins.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/zh/card_economy.content.json",
      "export_json_sha256": "a34aba7597f05b6165b57318179b6682db87528e5479756a6570dfb02aae810f"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "zh/elite_skins.html",
      "language": "zh",
      "title": "一种商品，两种定价体系——《Steam》专题报道",
      "source_url": "https://phishdestroy.io/steam_dossier/zh/elite_skins",
      "source_html_sha256": "bb3cdece58d3f9d15fbfa77f413d364d57360be7b7a37f6ca2f26f565bb80a4f",
      "exported_at": "2026-09-29T00:21:27.342Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "register",
            "source": "https://phishdestroy.io/steam_dossier/zh/elite_skins#register"
          },
          {
            "id": "",
            "source": "https://phishdestroy.io/steam_dossier/zh/elite_skins#selected"
          }
        ],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "elite_skins.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/zh/elite_skins.pdf?v=print-20260929-v5",
        "sha256": "f7f64ce64bdc6c1b9945e8bed4bfa9d2cdad501c5b71b7c20c0052184508153b",
        "bytes": 579825,
        "pages": 6
      },
      "integrity": {
        "signed_object": "elite_skins.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "elite_skins.content.json.asc",
        "digest_file": "elite_skins.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify elite_skins.content.json.asc elite_skins.content.json",
          "sha256sum -c elite_skins.content.json.sha256"
        ]
      },
      "content": {
        "text": "附件四 / 市场架构 / 20 9月 2026\nElite Skins 注册——1,800美元的市场上限\n\n一件商品。 两种定价体系。\n\n本节证明了什么\n\n本登记册对五个外部交易所中所有价格超过Steam设定的$1,800社区市场挂牌上限的CS2皮肤类别进行了实证普查。结果表明，248所证实的高端类别——涵盖18,394个活跃挂牌和$78.6百万的挂牌流动性——在Valve的官方市场中100%完全缺失。 寻求真实市场价格的卖家在结构上被迫转向外部平台，同时却完全依赖于Steam的底层交易机制。\n\nWhat this means — the Community Market listing ceiling\n\nSteam’s own market refuses a listing above roughly $1,800. A seller may ask less, never more. Items whose market price sits above that line therefore cannot be sold at that price on Steam at all — which is the mechanism that moves those sales to third-party venues while the item itself never leaves Valve’s inventory system.\n\nSection 13 — the off-Steam price gap →\n\n← 返回高管简报\n\nSteam 将社区市场的挂牌价上限设定在约1,800.。在本快照中列出的这五个第三方市场中， 419 CS2商品类别中，其最低实时卖价均高于该限价——其中402个商品，95.9%, 甚至完全没有Steam的挂牌信息。 他们合计持有18,641上挂牌的代币，价值至少为82.4百万美元。规定价格生效前必须获得第二个交易平台的认可， 248 这些分类均已得到证实——而且，其中每一类中，100%, 均未出现在 Steam 上。 最珍爱的是一张贴纸 | 泰坦（全息） | 卡托维兹 2014 位于 $66,285，被四个交易平台引用，这些平台在5.2%内，且彼此相距不到，而Valve旗下的平台均未刊载。完整的排名表、渲染图和评级均收录于 价格阶梯图集.\n\n查看所有419条目 ↓打开地图集 ↗阅读该方法\n248两个或更多市场中的价格超过上限\n18,394列出的商品分布在五个电商平台上\n$78.6M这些房源的最低价格\n100%其中一些在Steam上完全缺席\n\n更正 · 本页此前开头处列出的价格未经证实\n\n该页面较早版本的标题显示，一款“纪念版AK-47 | Point Disarray”在某电商平台上的标价为$148,954，而另一家电商平台Steam则将其定价为$119.。该条目仅基于一个货架上的一件商品，且没有其他电商平台的价格与之吻合，因此这仅为标价而非实际成交价，且该页面现已不再显示该条目。 此处的所有标题数据现仅限于248类别，且至少有两个市场独立标出的价格均高于上限。该行本身并未被删除——它仍出现在下方的登记表中，而导致其降级的评级标准已在 价格阶梯图集.\n\n01 / 活跃买单中的资金\n可量化的美元下限\n\n根据cs2.sh授权快照，对五个市场数据重新计算得出。此数值为特定子集中的最低总要价，并非销售额，亦非CS2经济体的估值。\n\n248 经核实的分类 · 18,394 已上架的藏品 · 5 交易平台$78.62M\n\n对于每个CS2商品，当两个或多个交易平台将其定价独立地定在超过Valve在其自身市场允许的限价之上时，该商品的最低总挂单卖价。\n\n为什么这是下限，而不是估计值\n\n对于每个市场，我们将它的 最低 根据该交易平台列出的商品数量来询价。该货架上其他所有商品的标价均等于或高于最低询价，因此实际标价更高——这是由机制决定的，而非凭空猜测。这既不代表实际成交、现金流，也不代表全市场估值，而且同一件实物商品可能出现在多个交易平台上。\n\n检查所有419源行 ↗\n★ 运动手套 | 树篱迷宫（经实地测试）\n$4.68M\nAWP | 冈尼尔（工厂新品）\n$4.46M\nAWP | 《龙之秘闻》（工厂新品）\n$4.34M\n★ 蝴蝶刀 | Fade（工厂全新）\n$4.17M\nAK-47 | Wild Lotus（工厂全新）\n$4.16M\n★ 蝴蝶刀 | 多普勒（工厂全新）\n$3.64M\n\n条形图显示了对底价计算贡献最大的六个类别，并按最大值进行标准化。条形图越高，既表示该商品的挂单价越低，也表示其上架数量越多。同一实物商品可能出现在多个交易平台上，因此这些数据不得与任何其他市场的总数相加。\n\n02 / 可检查的示例\n该限制遗漏了什么\n\n如有图片，则与具体商品名称相对应。价格取自标注日期的目录中的当前要价，而非交易记录。\n\n★ Butterfly Knife | Doppler (Factory New)\n\n来源: https://phishdestroy.io/steam_dossier/zh/elite_skins#selected\n\n可量化的差距： Steam上标价相同的房源无法与这些优惠相媲美。Valve自有 社区市场常见问题解答 存档链接：2026-09-21 ↗ 规定最高挂牌价约为1,800美元。卖家仍可将挂牌价定在该价格之下；是否接受这一价格由卖家自行决定。另一份 CSMarketCap 搜索价格高于 $1,800 ↗ 的商品 显示了28收录的市场中“Factory New Dragon Lore”的相关信息，共有约1.1K条展示的报价；重复的库存可能会被重复计数。\n\n03 / 结构性依赖\nSteam的限额导致价格发现机制失灵 Steam\n\n这种比较是结构性的。它既不假设每个要价都是合理的，也不将未售出的房源视为收入。\n\n01 · 规则\nSteam 列表顶部\n\nValve 称，Community Market上的商品列表数量上限约为 $1,800. 钱包余额也有上限，且钱包中的资金无法以现金形式提取。\n\n02 · 观察\n《龙之秘闻》：10,940.85美元\n\n5-市场目录显示 389 实时优惠 AWP Dragon Lore（工厂新品）起价为10,940.85（CSFloat 层）。更广泛的注册范围包含248，这些经核实的类别超出了Steam的限制。\n\n03 · 后果\n价格与转账分配\n\n一位希望卖出更高价格的卖家 无法在 Steam 上发布. 外部服务可以设定现金价格，但交付仍采用由 Steam控制的物品所有权和转移机制。\n\n政策矛盾： Valve 原创 订阅协议 存档链接：2026-09-21 ↗ 除非明确允许，否则Steam服务保留商业运营的权利，而其 2016 声明 存档链接：2026-09-21 ↗ 据称，这些赌博运营商已经开始使用 Steam 的 OpenID 以及自动化账户。这是 Valve 知晓 2016. 上存在此类外部运营商的直接证据。然而，官方交易平台却无法公布这些高价值物品的实际成交价格。 这就是架构对 off-Steam 价格发现和交易的依赖； 每个交易平台的合同状态都需要单独提供证据。两个主要承接此类超额交易量的西方交易平台，均作为正式的公司实体在主要司法管辖区运营—— CSFloat 公司 （在美国特拉华州注册成立）以及 Skinport GmbH （注册于德国斯图加特，商业登记号：HRB 764879）——直接依托 Steam 的 Web API 和交易基础设施，公开进行数亿规模的点对点商品交易。\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\n这四行数据（$100,000）对应的是CSFloat自身的最高挂牌价。这些数据已在登记簿中标注，切勿将其视为估价。存档的CSFloat挂牌数据抓取结果仅涵盖约$6,999,范围，因此采用公开目录快照来呈现完整的>$1,800登记数据。\n\n04 / 另一款《Valve》游戏\n天花板还挡住了 Dota 2\n\n在 Skinport 上进行同样的严格“最低价”测试，会发现 166 的 CS2 分类和 3 的 Dota 2 分类。这些是独立的市场快照；请勿将它们添加到 CSFloat 的 245. 中。\n\nDOTA 2 · 1 优惠活动\n英雄残暴新月\n\n最便宜的Skinport询问： $14,622.25.\n\nDOTA 2 · 1 优惠活动\n暗黑艺术斗篷\n\n最便宜的Skinport询问： $8,255.16.\n\nDOTA 2 · 1 优惠活动\n被腐化的能量之星\n\n最便宜的Skinport询问： $2,087.92.\n\n以下列出的只是三类装备，并非《Dota》2中所有现有的装备。 检查带有日期的Skinport行 ↗ 以及 API 文档 ↗.\n\n05 / 鲁棒性\n该发现并不取决于具体上限\n\nValve 该上限以买方的地区货币设定，因此换算成美元后不会得到一个整数。因此，会在每个合理的阈值处重复进行统计。Steam 中缺失的这些项目所占比例从未低于 95%.\n\n已通过阈值测试\t商品分类\t所列副本\t下限值\tSteam 缺席\n$1,800\t419\t18,641\t$82,449,526\t95.9%\n$2,000\t382\t15,159\t$75,541,325\t95.5%\n$2,070\t363\t12,336\t$69,560,305\t95.6%\n$2,300\t323\t11,644\t$67,984,432\t95.0%\n$2,500\t299\t10,950\t$66,203,929\t95.0%\n\n每次读取一行；这些行是同一人口普查的嵌套子集，而非独立的人口群体。“下限值”会乘以每个市场的 最低 它根据所列的副本数量进行统计，因此其设计上必然会低估书架上的实际数量。 打开数据集 ↗\n\n06 / 数得出来的稀缺性\n其中真正有售的寥寥无几\n\nBUFF 将每件物品的货架划分为多个浮动区间，并公布每个区间内有多少件。这使得“稀有”不再只是一个词，而是变成了具体的数量——并且将品相与外观分开定价。\n\n298 所列副本\nAWP | 龙之秘闻\n\n8 不同版本的定价。最贵的， 纪念版 AWP | 龙之传说（工厂新品），问道 $12,363 书架上有20本。\n\n在架子上最好的浮标支架（0–0.01）里有 2 副本，问道 $17,875 — 比该商品仅基于品相的基准要价高出 a +45% 的溢价。\n\n607 所列副本\nM4A4 | 嚎叫\n\n12 不同版本的定价。最贵的， 纪念版 M4A4 | Howl（厂新），问道 $14,895 书架上有2本。\n\n213 所列副本\nAK-47 | Wild Lotus\n\n7 不同版本的定价。最贵的， 纪念版 AK-47 | Wild Lotus（工厂全新），问道 $14,895 书架上有2本。\n\n310 所列副本\nAWP | 冈尼尔\n\n7 不同版本的定价。最贵的， 纪念版 AWP | 冈尼尔（轻微磨损），问道 $14,895 书架上有2本。\n\n这为何对本报告的其余部分至关重要： 这些并非抽象概念。全球公开货架上每件奖杯仅有几百件，每件都与一个 Steam 账户相关联，且通过一次 Steam 交易完成转移。在如此清淡的市场中，单件被盗库存都算得上是一件可衡量的事件，而本调查其他部分所记录的账户劫持技术，也能带来直接且可量化的回报。\n\n“数量”指在数据采集时某个市场上的实时库存，而非总存量。私人库存中的商品在此处均不计入统计。 打开浮点数数据集 ↗\n\n07 / 梯子已看不见了\n商品价格越高，就越远离任何可见的场所\n\n下面的每一级都代表一个不同的证据类别。这些类别是刻意没有合并为一个数字的。\n\n横档\t图\t这算是什么样的事实\nCeiling on Valve's own market\t~$1,800\tPublished rule, stated in the Steam Community Market FAQ.\nDearest ask several marketplaces agree on\t$66,285\tMeasured by us in this snapshot. Sticker | Titan (Holo) | Katowice 2014, quoted by four marketplaces within 5.2% of one another. An ask, not a sale.\nDearest ask seen on any single shelf\t$148,954\tOne marketplace, one copy, no second marketplace agreeing — and equal to a round CNY 1,000,000 at the snapshot rate. Listed here as the outer edge of what sellers ask, and relied on for nothing.\nPublic marketplace sale\t$49,999\tSpecialist Gloves | Crimson Kimono (FN) on CSFloat, as reported by SteamAnalyst. Platform-recorded, third-party reported.\nReported private sale\t$400,000\tAK-47 | Case Hardened, reported by PC Gamer in April 2023. Journalism, not a record we hold.\nReported offer, declined\t$1,500,000\tBlue Gem Karambit, pattern #387. No sale took place and the figure has not been independently confirmed. Included to mark the ceiling of the claims, not to assert a value.\n\n结构要点： Valve的市场价格止步于约$1,800.；第三方交易平台将交易价格推高至约$66,000（其中多家平台价格一致），以及约$150,000（仅有一家平台价格一致）。 高于该价格便完全没有交易场所——Valve发行的资产最大规模的转让是在个人之间私下进行的，既无挂牌，也无平台记录，不进行身份核查，也不进行报告。转让本身仍通过Steam进行。 数值越高，就越难以被察觉，而承载该数值的基础设施完全由Valve负责。\n\n最后两条信息来自他人的报道，并已注明出处。本项目未对这些信息进行核实，且未以此作为得出任何结论的依据。\n\n419观察到的所有类别\n\n来源: https://phishdestroy.io/steam_dossier/zh/elite_skins#register\n\n09 / 来源与局限性\n检查计算结果\n\n我们公开了本地数据和公开数据源。该数值标题的范围限定为捕获当日的CSFloat。\n\nValve 自身设定的上限和条款\n\nSteam 社区市场常见问题解答 ↗ 存档链接：2026-09-21 ↗ 给出了约1,800的挂牌最高价。该 订阅协议 ↗ 存档链接：2026-09-21 ↗ 规定了商业用途的限制。\n\n价格从何而来\n\n价格、上市数量和流通股区间数据取自 cs2.sh 市场数据 API 需通过付费商业订阅，并使用授权密钥。 未抓取任何电商平台的数据，也未使用任何电商平台的账户或凭证。 该平台整合了BUFF、Youpin、CSFloat、Skinport、C5Game以及Steam社区市场；所有数据均按原始值以美元为单位呈现。 打开来源清单 ↗ — 它记录了原始快照的确切端点、捕获时间以及 SHA-256 哈希值，因此，任何拥有自己密钥的独立读者都可以提取相同的数据，并重新计算本页面上的所有数值。\n\n我们未能获得的\n\n所购买的订阅仅涵盖当前的快照。我们无法访问历史和存档端点，而且 本页面未就任何趋势、任何历史价格或任何随时间的变化作出任何声明。 这里的一切都只是一个瞬间，并标注了日期。\n\n早期的CSFloat注册表\n\n该展览的第一个版本统计了来自单个 CSFloat 目录快照中的 245 个类别，该快照的日期为 20 September 2026: 那张快照仍留在这里 ↗. 当前的统计范围更广，因为它涵盖了五个市场，而不是一个。这两项数据是分别统计的，不得相加。\n\nValve的强制执行声明\n\nValve 发布的《2016》游戏内道具交易更新 ↗ 存档链接：2026-09-21 ↗ 针对使用OpenID和自动生成的Steam账户的博彩运营商。这一措施的范围比全面禁止所有外部交易平台更为有限。\n\n解释范围\n\n这些是报价，而非实际成交。一个市场名称可能涵盖多种实物商品，它们在浮雕、图案或贴纸细节上各不相同。本登记册并不衡量总市场价值，也不反映Valve的意图。",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Elite Skins 注册——1,800美元的市场上限"
          },
          {
            "level": 2,
            "id": null,
            "text": "可量化的美元下限"
          },
          {
            "level": 3,
            "id": null,
            "text": "为什么这是下限，而不是估计值"
          },
          {
            "level": 2,
            "id": null,
            "text": "该限制遗漏了什么"
          },
          {
            "level": 3,
            "id": null,
            "text": "★ Butterfly Knife | Doppler (Factory New)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Steam的限额导致价格发现机制失灵 Steam"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam 列表顶部"
          },
          {
            "level": 3,
            "id": null,
            "text": "《龙之秘闻》：10,940.85美元"
          },
          {
            "level": 3,
            "id": null,
            "text": "价格与转账分配"
          },
          {
            "level": 2,
            "id": null,
            "text": "天花板还挡住了 Dota 2"
          },
          {
            "level": 3,
            "id": null,
            "text": "英雄残暴新月"
          },
          {
            "level": 3,
            "id": null,
            "text": "暗黑艺术斗篷"
          },
          {
            "level": 3,
            "id": null,
            "text": "被腐化的能量之星"
          },
          {
            "level": 2,
            "id": null,
            "text": "该发现并不取决于具体上限"
          },
          {
            "level": 2,
            "id": null,
            "text": "其中真正有售的寥寥无几"
          },
          {
            "level": 3,
            "id": null,
            "text": "AWP | 龙之秘闻"
          },
          {
            "level": 3,
            "id": null,
            "text": "M4A4 | 嚎叫"
          },
          {
            "level": 3,
            "id": null,
            "text": "AK-47 | Wild Lotus"
          },
          {
            "level": 3,
            "id": null,
            "text": "AWP | 冈尼尔"
          },
          {
            "level": 2,
            "id": null,
            "text": "商品价格越高，就越远离任何可见的场所"
          },
          {
            "level": 2,
            "id": null,
            "text": "419观察到的所有类别"
          },
          {
            "level": 2,
            "id": null,
            "text": "检查计算结果"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve 自身设定的上限和条款"
          },
          {
            "level": 3,
            "id": null,
            "text": "价格从何而来"
          },
          {
            "level": 3,
            "id": null,
            "text": "我们未能获得的"
          },
          {
            "level": 3,
            "id": null,
            "text": "早期的CSFloat注册表"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve的强制执行声明"
          },
          {
            "level": 3,
            "id": null,
            "text": "解释范围"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/zh/#market-gap-section",
          "https://phishdestroy.io/steam_dossier/zh/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/zh/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/zh/skin_atlas.html#grading",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-above-the-ceiling.json",
          "https://phishdestroy.io/steam_dossier/zh/elite_skins#selected",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://csmarketcap.com/search?minPrice=1800&amp;page=1",
          "https://store.steampowered.com/agreement/?l=english",
          "http://web.archive.org/web/20260921022032/https://store.steampowered.com/agreement/?l=english",
          "https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921021947/https://store.steampowered.com/oldnews/22883",
          "https://phishdestroy.io/steam_dossier/zh/#proxy-bypass-explainer",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/skinport-floor-over-cap.json",
          "https://docs.skinport.com/items",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-float-scarcity.json",
          "https://phishdestroy.io/steam_dossier/zh/elite_skins#register",
          "https://cs2.sh/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/csfloat-catalogue.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/zh/elite_skins.content.json",
      "export_json_sha256": "2ce4512ee4e36b2bb83b88b9f7adacb50a009b76d680e563b5c7a3dd43d9bd03"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "zh/enforcement_audit.html",
      "language": "zh",
      "title": "人口普查Valve不会公布——Steam档案",
      "source_url": "https://phishdestroy.io/steam_dossier/zh/enforcement_audit",
      "source_html_sha256": "5bf42457bf7f1f4ff33ce302a25a9b8ad27cf650539667917d22269a2933f2ef",
      "exported_at": "2026-09-29T00:21:24.093Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "enforcement_audit.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/zh/enforcement_audit.pdf?v=print-20260929-v5",
        "sha256": "d598092598c2373982c06beb838814d633bf22862d2320df8df74acab7898f8f",
        "bytes": 726978,
        "pages": 10
      },
      "integrity": {
        "signed_object": "enforcement_audit.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "enforcement_audit.content.json.asc",
        "digest_file": "enforcement_audit.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify enforcement_audit.content.json.asc enforcement_audit.content.json",
          "sha256sum -c enforcement_audit.content.json.sha256"
        ]
      },
      "content": {
        "text": "附件六——人口普查VALVE不会公布\nSteam 上的账号农场有多大？我们自己做了统计。\n\n目前尚未公布在 Steam 上运行的自动化账户数量。其实也没必要保密：Steam 的 ID 空间是一个连续的整数范围，而 Valve 发放的 Web API 密钥正好可以遍历该范围。 因此，我们选取了自我标识的最大群体——即 ArchiSteamFarm 社区——并通过 Valve 自身的封禁端点，对每位成员进行了一次性读取。 它之所以会自我声明，是因为 ASF 在首次启动时会自动加入 Steam 群组，除非用户明确选择退出或取消勾选群组加入设置（AutoJoinSteamGroup / 统计数据）。由于该设置默认处于启用状态，因此用户组成员涵盖了广泛的人群：活跃的多账号商业机器人网络、偶尔闲置的业余爱好者，以及在个人账号上运行该软件且从未取消默认订阅的普通玩家。这使得该用户组成员成为反映该软件累计覆盖范围的有效统计数据：10,880,610 个账户（其中 5,360,499 个已确认的非限级会员已通过 $5.00 个门店的入口）。 然后，我们提出了唯一关键的问题——Valve究竟对他们做了什么？\n\n本页面不包含的内容。 这并不是说Valve应该封禁一千万用户，也不是在抱怨刷卡者。下面列出的每一个数字只有一个原因：Valve是否 永久封禁个人用户，并以“将Steam用于商业用途”及“使用自动化手段”为由作出书面说明。 这衡量的是同一规则如何大规模地适用于同一行为——由一名运营商执行，该运营商在过程中收取了 $5.00 的解锁费、游戏许可证费和市场费 Valve。调查结果揭示的是这种不对称性，而非“农场”本身。\n\n10.88M 计数那些四处游荡的骗子 (5.35万)10万付费审计与免费审计\n10,880,610ASF 组全体成员共阅读了 Valve 自己发布的封禁 API（含受限和不受限两类）\n88.97%从未被封禁过——9,680,599个账号仍然有效\n63.06%被封禁的账户中有付费账户（$5+ 支出）—— 100,000 SRSWOR 区间（±0.39% 误差范围）\n67.77%在51,732名经裁决的诈骗犯中，无人受到诈骗禁令处罚（全面统计）\n01 — 规模\n一千万个账户，其中九成未被触及\n\n一个通过Valve自身的终点进行自计数的人口。\n\n为什么它会自动计数\nASF 为您加入该小组\n\n首次运行时 ArchiSteamFarm 组统计数据 默认设置为“true”，并加入 Archi 的 SC Farm Steam 组。运维人员必须主动选择退出。因此，该成员资格代表了安装量的下限——而非上限。未启用“统计”功能的运维人员未被计入；实际安装量至少与此数值相当。\n\n我们的阅读\n10,880,610 总条目数\n\nAPI 成员列表共返回了 10,880,610 个 SteamID64——包括受限和不受限的。Steam 的群组页面显示为 5,360,499（仅限不受限的）。每个条目都经过一次ISteamUser/GetPlayerBans 在 2026-09-23 上。按住一个键长达五十五分钟。\n\n答案\n88.97% 清理\n\n1,200,011 不受任何 Steam 禁令的约束（11.03%）。其余的9,680,599 没有任何记录 ——既不是社区禁令，也不是VAC，什么都不是。该账号并未被封禁，而是被放任继续运行。同一条条款，只要针对某一个人，就足以将其永久封禁。\n\n在 10,880,610 个账户中，有多少个 Valve 被触及过\n\n将整个扫描对象群体按Valve是否曾实施过任何禁令进行划分。红色部分显示了Valve对此舰队所采取的所有行动。\n\n88.97%从未被封禁\n11.03%\n没有任何形式的禁令 — 9,680,599 (88.97%)带有某些 Steam 禁令 — 1,200,011 (11.03%)\n10,880,610ASF小组成员进行了扫描\n9,680,599从未被封禁 — 88.97%\n1,200,011执行任何禁令 — 11.03%\n55 分钟要统计所有数据，使用一个 API 密钥\n这支舰队为了维持存在已经付出了Valve\n\n这不是对农场收入的估算，而是该农场在Valve的商店中已花费金额的下限——该数值是根据Valve的规则，结合上述统计数据得出的。\n\n10,880,610 的计数涵盖了 API 返回的完整 ASF 成员列表——其中包括受限账户和非受限账户。Steam 本身的受限用户账户 该页面指出，受限账户无法计入 Steam 组成员（他们不计入显示的组规模中），但仍可能出现在底层的成员列表中。非受限子集——即在 Steam 商店中消费至少 $5.00 的账户——恰好是5,360,499 — 计数 Steam 显示在群组页面上，而根据 Steam 自身的规则，该页面会排除受限账户。$5.00 的下限计算仅适用于该不受限的子集。\n\n5,360,499非受限成员\n(Steam显示的组数)\n×\n$5.00Valve自身的最小值\n不再受限\n=\n$26,802,495店内消费下限\n由非有限子集\n\n这是Valve从舰队中不受限部分已收到的款项的下限——并非收入估算，也非利润声明。大多数账户的实际支出高于此数；$5.00这一数字仅为最低要求门槛。\n\n二次收益：根据种植商品的交易量收取最高 66.7% 的费用。 除了 $26.8M 的入场费外，在社区市场清算的每张卡牌和每件商品都需支付 Valve 的强制性最低手续费（$0.01 Steam 手续费 + $0.01 发行商费用）。 对于典型的3分卡牌和垃圾物品，Valve 从 3 美分中拿走 2 美分——这相当于实际削减了 66.67%，使 Valve 受益, 远超宣传中的 15% 营销费率。\n\n关于人口的关键注意事项： 加入群组并不能证明每个账号都是专门的机器人，也无法涵盖Steam上的所有机器人。ASF 默认会在启动时自动将账号加入其社区群组；除非用户明确取消勾选或禁用该配置选项（AutoJoinSteamGroup)，常玩玩家、偶尔闲置的玩家以及社区成员仍与自动刷怪舰队一同列在名单中。此外，Steam禁令并未附带公开理由栏。该结论是针对这一与软件相关用户群体的实证率，而非针对任何单个账号的个别裁决。汇总数据，可重复验证：asf-ban-census-2026-09-23.json.\n\n02 — 地理\n舰队驻扎之地\n\n在被封禁的账号中，只有 8.5% 个账号填写了国家信息。在填写了国家信息的账号中，美国占比最大。\n\nA Steam 个人资料包含一个可选的国家字段。100,413个被封禁的账号中，有1,182,811个填写了该信息——8.5%个。† 在这少数国家中，美国以15.5%位居榜首，其次是乌克兰、中国和俄罗斯，其余国家则形成一条绵延至欧洲、拉丁美洲和东南亚的长尾。 没有人对这一领域进行核查：阿富汗位列前十，这大致符合其实际价值。其余的91.5%个国家是被省略而非被归类的，因此下文呈现的只是一个自我选择的少数群体——既不是舰队分布图，也不构成判断其运营地点的依据。\n\n按申报国家划分的被封禁账号\n\n在因泄露公共位置而被封禁的 100,413 个账号中，排名前 15 的国家。所列比例即为该子集所占的比例。将鼠标悬停在上面可查看具体数量。\n\n0%\n5%\n10%\n15%\n20%\nUnited States\nUkraine\nChina\nRussia\nCanada\nAustralia\nJapan\nBrazil\nGermany\nAfghanistan\nUnited Kingdom\nRomania\nFrance\nPhilippines\nIndia\n\n从以下位置读取GetPlayerSummaries 针对被禁子集。该字段由账户持有人设置，且无人进行验证，因此VPN出口或恶作剧条目与真实条目具有同等效力。\n\n03 — 新鲜度\n近期账目，而非历史积压\n\n根据账号创建时间推算，被封禁的用户群体是近期出现的，并非集换式卡牌时代的遗留用户。\n\n如果这只是在逐步清理一桩陈年旧事，那么被封禁的账号应该主要集中在交易卡早期阶段。但实际情况恰恰相反。在1,132,852个显示了创建日期的被封禁账号中，70% 创建于2020年或之后，其中近一半是在2023年之后创建的。 该数字从2017年创下的59,175上升至峰值227,030 仅在2024年就创建了. 他们每个人都在$5.00商店大门收到卡片之前就通过了，因此每人都要缴纳入场费。\n\n被封禁的账号是在何时创建的\n\n已披露注册日期的1,132,852名被禁用户的账号创建年份。时间范围为2020年至2026年，而非2013年至2015年的交易卡时代。峰值：2024年。将鼠标悬停查看具体数量。\n\n0k\n63k\n125k\n188k\n250k\n'13\n'14\n'15\n'16\n'17\n'18\n'19\n'20\n'21\n'22\n'23\n'24\n'25\n'26\n70%2020年及以后创建的被封禁账户中\n227,0302024年创建的被封禁账号——这一年是峰值年\n51,7012021年的低谷，夹在两个高峰年之间——原因不明\n2003→2026数据范围完整，但数据仅涵盖最近六年\n\n创作时间可追溯至GetPlayerSummaries 针对按 SteamID64 去重后的封禁子集。创建日期指账号的注册时间，而非被封禁或开始刷分的时间；此处将其作为数据集新鲜度的佐证，而非意图的依据。图表中未显示的三点：\n\n2024年后的一个趋势。 2025年或2026年创建的账户被封禁的时间较短，而2026年仅涵盖九个月——因此 227,030 → 121,070 → 16,534 属于审查行为，而非下降趋势。\n禁飞率。 仅读取了被封禁账户的创建年份，因此没有分母。仅凭安装基数的增长就足以形成这种趋势。\n2021年为何崩盘。 51,701位于105,821和104,641之间，位于这两个邻居的下半部分下方。没有任何公开信息对此进行解释；该位置被保留为可见状态，而非被平滑处理。\n04 — 时机\n当 Valve 生效时，其效力在第一年内生效\n\n对于88.97%未被触及这一情况，最明显的辩解理由是积压。但过时的禁令却表明了相反的情况。\n\n账号被封时已使用多久了\n\n针对那293,750个既有创建日期又有上次封禁日期的被封禁账号，统计其被封禁时的账号使用时长。其中超过一半是在创建后的第一年内被封禁的。\n\n0%\n10%\n20%\n30%\n40%\n<6 mo\n33.7%\n6–12 mo\n21.5%\n1–2 y\n20.6%\n2–5 y\n14.3%\n5 y+\n10.0%\n55.1% inside the first year\n第一年就被禁了 — 55.1%后来被封禁 — 44.9%\n0.80 年账号被封时的平均使用年限\n55.1%账号开通后第一年内被封禁\n33.7%在前六个月内被禁\n293,750同时包含这两个日期的账户\n\n这是对这一显而易见的辩解的回应。如果舰队中有 88.97% 部分未受影响，仅仅是因为执法效率低下——积压的案件正在逐一处理——那么这些禁令do 数据会显得偏老。实际情况恰恰相反：被封禁账户的中位数是九个半月大，还有第三个——33.7%——在六个月内被捕。当Valve作用于这一群体时，其作用迅速。那十个中仍有九个在逃，他们并非排队等待。\n\n禁令生效时的年龄 = 创建日期起GetPlayerSummaries 从由……所暗示的禁令日期中减去距离上次封禁已过多少天, 请继续阅读 2026-09-23。该值仅在两个值均存在时才会计算：1,200,011个被封禁账号中的293,750个。 其余账户未报告“自禁用以来已过天数”的值，因此被省略，而非被默认——请将此理解为带日期子集的构成，而非每个禁令的情况。\n\n05 — 禁令的实际内容是什么\n当 Valve 确实生效时，并不会停止该机器人\n\n在那些带有任何禁令的11%中，请查看具体是哪项禁令。\n\n封禁并不等于封禁。在1,200,011个账户中，Valve个已被标记，99.8% 携带一个社区 禁令 — 针对论坛、个人资料和群组的限制对交易机器人毫无影响。该账号仍可接收卡牌、进行交易以及转移库存。 22.2% 至少有一项游戏封禁，且 3.9% 有一项 VAC 封禁；由于这些类别存在重叠，因此不会累加。唯一真正切断交易功能的制裁——经济/交易封禁——仅出现在 5,214 个账号上。 我们并非仅以此数字为依据——总体而言，交易禁令在 Steam 中本就极为罕见。这张图表要表达的观点更为简单：即便是 Valve 这一比例是否 touch 继续交易。\n\n那些被封禁的11%到底是因为什么被封禁的\n\n每种封禁类型占所有已扫描成员的百分比。一个账号可能存在多种封禁类型。将鼠标悬停在上面可查看具体数量。\n\n0%\n4%\n8%\n11%\n15%\nCommunity ban\nGame ban\nVAC ban\nEconomy / trade ban\n\n“A Steam”禁令没有“原因”字段，因此这些禁令中没有一项是专门针对刷卡行为的——这是现有禁令类型的汇总，并列出了每种类型实际限制的内容。社区禁令不会阻止交易；而经济/交易禁令则会。汇总：asf-ban-census-2026-09-23.json.\n\n06 — 另一部分人群\n骗子 Valve 走开：51,732 全面人口普查\n\n第二份独立列表——经社区确认的欺诈行为——是根据同一官方API进行比对得出的。\n\n自动化用户群体或许可以被视为无害的闲人。而第二类用户则不能。SteamRep是一个运行已久的社区声誉数据库；被标记为被禁 该社区已裁定某人系诈骗犯，并附有受害者证据和交易聊天记录作为佐证。我们已完成对所有成员的100%普查，51,732 个显示为“已被封禁”状态的个人资料 针对 Steam 的官方 Web API（ISteamUser/GetPlayerBans/v1) ——且仅统计了针对诈骗行为的制裁措施。一项 VAC 禁令是针对游戏中的软件作弊行为（如自动瞄准、透视）；该禁令对交易者没有任何影响，也不构成 Valve 针对欺诈行为采取行动的证据，因此不计入反欺诈执法统计。\n\n在整个51,732账户普查中，67.77%名——其中35,059名已被裁定为诈骗者——在Valve平台上没有任何与诈骗相关的封禁记录： 他们仍然可以进行交易，仍然可以向新受害者发送好友请求，仍然可以发送消息。只有 32.23% 账号遭到了社区禁令或交易禁令，而交易禁令——这一项真正能切断物品转移的措施——仅针对 18.81% 个账号（9,731 个账号）。 另有 12.81%（6,627 个账号）因纯粹的游戏内作弊行为而受到 VAC 次游戏禁令，但在 Steam 次交易中则完全不受限制。\n\n已确认的诈骗者，根据Valve是否对其实施了与诈骗相关的封禁（全面普查）\n\n所有 51,732 SteamRep-被封禁的账号，按 Valve 是否实施了社区禁令或交易禁令进行分类。VAC 及游戏禁令未被纳入统计——这些禁令并不针对欺诈行为。将鼠标悬停查看具体数量。\n\n0%\n18%\n35%\n53%\n70%\nNo scam-relevant ban\nCommunity or trade ban\n0%\n6%\n13%\n19%\n25%\nCommunity ban\nTrade / economy ban\nVAC (not fraud)\nGame ban\n51,732SteamRep-已审核的被封禁账号 — 100% 完整统计\n35,059未因诈骗相关行为受到禁令处罚 (67.77%)\n18.81%推行能杜绝诈骗的贸易禁令 (9,731)\n32.23%该股份 Valve 遭到了社区或行业禁令（16,673）\n\nSteamRep 是一个由社区评判的第三方信誉数据库，并非 Valve 的裁定——这正是关键所在：外部证据，需对照 Valve 自身的行为进行衡量。 规范导出文件中所有 51,732 被封禁的个人资料均已直接与ISteamUser/GetPlayerBans/v1. “与诈骗相关”指社区禁令或经济/交易禁令；VAC (12.81%) 和游戏禁令 (3.86%) 则单独统计，因为它们针对的是作弊行为，而非诈骗。完整的审计数据集：steamrep_steam_bans.csv.\n\n两个群体，一项发现\n\n这两者既不是同一群人，也不是同一类行为。一个是1000万个自动化账号；另一个是5.3万名经裁定的诈骗者。它们的共同点在于结果的表现形式：十分之九的农场账户从未被动用过，而超过三分之二（67.77%）的已确认诈骗者并未因诈骗行为受到任何处罚。 社区禁令 Valve 确实会随意限制论坛和个人主页的访问，但不会限制交易。举报按钮、声誉数据库、用于制止诈骗的禁令：这些功能一应俱全，却都未被充分利用。 将此与主档案中已归档的拒绝案例相比较：同一公司永久封禁了一个账户，并以“商业用途”和“自动化操作”为由——该条款并非形同虚设，而是直指要害。\n\n07 — $5.00 账户门事件与账户劫持\n对“100,000”账户的实证审计：僵尸网络并非一次性免费账户\n\n统计抽样逻辑与数学证明：为什么取任何其他 100,000 的值都会得到完全相同的結果。\n\nValve向监管机构和消费者保护机构提出的首要辩解是，自动诈骗和刷量行为是由那些转瞬即逝、免费的“一次性”账户实施的，这些账户很快就会被封禁。根据Valve公布的规则，一个账户限量版 直到它至少花费$5.00 美元 在 Steam 商店中，这导致其无法进行交易、发送好友请求以及使用 API 功能。我们通过对一个具有代表性且在数学上严谨的样本进行变现状态测试，直接对这一说法进行了核查，100,000 封禁了 Steam 个账号 摘自我们的 1,182,811 个人资料元数据语料库。\n\n采样方案 (SRSWOR)\n100,000 无偏切片\n\n摘自N = 1,182,811 个唯一被封禁的 Steam 个账户，采用基于密码学均匀伪随机数生成器（PRNG）的无放回简单随机抽样方法。每个账户的被选中概率均为P =n /N ≈ 8.45%，从而彻底消除了存活偏差和活动偏差。\n\n数学证明\n误差范围 < ±0.4%\n\n在……处应用有限总体校正（FPC）公式99% 置信区间 (Z = 2.576)：\nMoE = Z × √[p(1-p)/n] × √[(N-n)/(N-1)] ≈ ±0.39%\n\n可重复性\n为什么任意100k的收益率都相同\n\n由于在 99% 的置信水平下，误差范围被限定在 ±0.4% 之内，从任何其他独立的 100,000-账户样本中抽取样本，从数学上讲，该样本必定落在 63.06% ± 0.39% 范围内 (62.67% 至 63.45%)。该样本反映了全部 118 万被禁人群的情况。\n\n审计结果彻底推翻了“一次性机器人”这一辩解。在通过Steam的旧版XML配置文件接口接受审计的100,000个账户中：61,490 个账户（63.06% 个分类账户）是“非限额（已付费）”账户，且在 Steam 上至少花费了 $5.00。 仅36,021 (36.94%) 是受限的免费账户，而 2,489 则是未配置或私有账户。\n\n100,000 被封禁的账号：付费账号（$5+ 商店消费）与免费受限账号\n\n对 100,000 个随机抽样的被封禁账号进行了实证审计。其中超过 63% 个已通过 Valve 的付费财务审核。将鼠标悬停在数据上可查看具体数量。\n\n0%\n16%\n33%\n49%\n65%\nNon-limited (Paid ≥ $5.00)\nLimited (Free < $5.00)\n100,000抽样总体（SRSWOR，N=118万）\n63.06%无限制付费账户（61,490账户）\n±0.39%在 99% 置信区间下的误差范围\n~745,800基于118万个被封禁账号数据推算出的付费账号数量\n结构性现实：工业级账户清算\n\n为什么在被抽样的被封禁账号中，会有 63% 是曾在 Valve 的商店里花过真金白银的付费账号？僵尸网络运营商不会自掏腰包花数百万在一次性账号上。这一比例凸显了遭到入侵和劫持的账户 在生态系统中循环。\n\n这种规模在地下平台上可以直接观察到：例如FSB Market (匿名名称；此处不公开原名)（其他相关名称不予公开）等交易平台，以及550,000 Steam 个账户 （窃取日志、钓鱼截图、凭证填充）在任何时刻都有人在积极兜售（phishdestroy.io/live-intel). 该市场使用 Valve 自身的 Steam OpenID 对买卖双方进行身份验证，且双方均FSB Market nor相关论坛 被 Valve 的链接过滤器拦截了。\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\n如第06节所述，Valve并未主动消除这种欺诈行为：67.77%名经社区确认的诈骗者在Steam上没有任何诈骗禁令，而自动化交易群中的 88.97% 账户则完全未受影响。这些账户可以自由活动，通过官方 API 进行身份验证，并在整个生态系统中进行交易，几乎完全不受制约。\n\n取证与执法架构图\n从1088万个被扫描账户到10万个实证样本，再到5.35万名已确认诈骗者——点击链接查看原始证据\n第01级 · 1088万自动化车队普查\n在Steam上自认规模最大的自动化用户群体，依次通过了Valve的官方封禁API。这证明，商业机器人群在支付数千万的入场费的同时，仍能毫无顾忌地在88.97%上运行。\n9,680,599 88.97% 活跃且未被触及\n运行自动化软件且记录中没有任何封号记录的账号。\n人口普查原始JSON数据 (1.2 KB) ↗检查第01节 ↗\n$26,802,495 门店直接收入下限\n由 Valve 从 5,360,499 名非限额会员中收集，这些会员已超过 $5.00 的最低入场门槛。\n卡片经济审计 ↗Valve $5 规则常见问题解答 ↗\n1,200,011 11.03% 标记子集\n99.8% 仅实施虚拟社区禁令；99.95% 号账户仍可正常交易。\n禁令类型明细 ↗被禁数据库 (60.4 MB) ↓\n第02层 · 100,000-账户实证抽样审计（N = 1,182,811）\n通过旧版 XML 端点评估的代表性 SRSWOR 样本。经数学证明，在 99% 置信区间下，误差范围小于 ±0.4%。这驳斥了“被封禁的机器人账户都是免费的一次性账户”这一说法。\n61,490 (63.06%) 无限制付费账户（$5+ 消费额）\n被封禁账户中超过 63% 属于付费交易账户。据此推算，被封禁账户池中约有 745,800 个付费账户（$3.73M+ 准入门槛）。\n部分结果 CSV（2.1 MB） ↓100k 法医报告 ↗\n36,021 (36.94%) 限量免费账户（< $5.00）\n少数被封禁的账号符合Valve所描述的“一次性废弃机器人”特征。2,489个账号未配置或设为私密。\n10万条样本切片 CSV 文件（8.5 MB）↓支出分析 MD ↗\n34.67% 对 63.93% 配置文件净化审计\nValve个账户的昵称被清空，恢复为原始的SteamID64，但34,673个账户的自定义名称和头像则完全未受影响，其中63,928个账户已被封禁。\n消毒部分 ↗概述 路线图 ↗\n34.59% 传统 过期账户（创建于2003–2019年）\n超过三分之一的被封禁账号是在5至20年以上前注册的，这证明了针对长期Steam玩家的工业级账号劫持行为确实存在。\n年代年表 ↗支持拒绝 ↗\n第03级 · 51,732 SteamRep 已确认诈骗者名录\n对经社区裁定的欺诈者进行了全面100%统计，包含受害者的聊天记录和交易凭证，并与官方Steam封禁API进行了交叉核对。这证明了执法体系存在系统性失职。\n35,059 (67.77%) 零欺诈封号（完全不受惩罚）\n超过三分之二的已核实诈骗者均未受到 Valve 平台颁布的社区禁令或交易禁令。他们能够正常进行交易并添加受害者。\nSteamRep API 禁令 (2.6 MB) ↓SteamRep 审计报告 ↗\n9,731 (18.81%) 经济 / 贸易禁令\n唯一能切断库存变现的制裁措施。仅出现在不到五分之一的已确认诈骗者身上。\nSteamRep 来源 (2.1 MB) ↓查阅第06节 ↗\n6,627 (12.81%) 不相关的作弊禁令（仅限 VAC）\n因在游戏中使用瞄准外挂/透视外挂而被封号，而其Steam交易和网络钓鱼能力仍100%活跃。\nVAC 无关性分析 ↗安全时间线 ↗\n第04级 · 维基篡改事件与2026年8月基础设施入侵事件\n证据包中记录了内部开发者文档遭篡改、社区编辑功能被限制以及未受保护的边界防护漏洞等问题。\n1,200+ 编辑 VDC 维基冲突日志\n社区编辑们试图修复钓鱼链接和垃圾信息模板时，却被自动过滤器系统性地屏蔽，而Valve名工作人员却无视了相关警告。\n《俄罗斯冲突报告》（127 KB）↗分类报告 (66 KB) ↗\n12 TB 未经过身份验证 2026年8月 资产泄露（CWE-284）\nValve 曾将 12 太字节的内部代码和原型构建文件托管在了一个公开的公共端点上，且数周内未进行身份验证。\nValve 无能档案 (43 KB) ↗证据档案 ↗\nCEVA物流数据泄露事件 2026年8月客户个人身份信息泄露事件\n欧洲Steam Deck购买者的姓名、地址和电话号码从Valve的物流合作伙伴处泄露，引发了一波网络钓鱼攻击。\n事件记录 ↗执法记录 ↗\n\n采样伪影：banned_100k_slice.csv (100,000 个账户)。审计结果：slice_100k_limited_results.csv. 完整分析报告：BANNED_100K_FORENSIC_ANALYSIS.md.\n\n08 — 方法与局限性\n人们是如何理解这一点的，以及它并未主张什么\n\n三个公众样本群体、一个公开API、严格的统计抽样。\n\n执行与凭证\n\nASF普查中的 100,000-account SRSWOR 抽样及 SteamRep 交叉核查，由 PhishDestroy 名参与者使用其各自的 Steam 个账户和 Web API 密钥执行，作为联盟公开反钓鱼及打击诈骗工作的一部分。 本报告的作者未持有任何 Steam Web API 密钥，也未亲自进行实时扫描。数据汇总、哈希处理、验证及发布均基于参与者的输出结果完成。\n\n人口\t来源\t读了什么\nASF成员\n10,880,610\tArchiSteamFarm Steam 社区群组的公开成员列表。Steam 的群组页面显示有 5,360,499 名成员（仅限非受限账户）；API 返回的成员列表共包含 10,880,610 条记录，其中包括受限账户。 除非用户在配置中明确禁用默认的群组加入设置，否则首次运行时会自动加入该群组（AutoJoinSteamGroup / 统计数据)，这意味着会员名单中包括商业机器人群组、个人卡片闲置者，以及未关闭默认选项的普通玩家。\tGetPlayerBans 针对每位成员（封禁标记）；GetPlayerSummaries 用于创建日期和国家/地区。按100个ID为一组进行批处理，并通过SteamID64进行去重。\n10万个被封禁的账号 SRSWOR 片段\n100,000\t从 1,182,811 个被封禁账户语料库中，采用无放回均匀随机抽样方法抽取的代表性样本（$P = 8.45\\%$）。 经有限总体校正后，在 99% 置信水平下（$Z = 2.576$），误差范围为 $\\pm 0.39\\%$。\t变现与限权账户状态 (isLimitedAccount) 通过 Steam 的旧版 XML 配置文件接口进行审核 (?xml=1) 通过分布式代理管道。确认 63.06% 已付费状态。\nSteamRep 诈骗分子\n51,732\t对SteamRep社区声誉数据库中所有标记为“被封禁”的个人资料进行了100%次全面普查（共计51,732个个人资料）。未进行任何抽样或筛选。\tISteamUser/GetPlayerBans/v1 针对所有 51,732 账户，按 SteamRep 状态进行交叉分析。证实 67.77% 未受任何诈骗禁令影响。\n权利要求\n\n仅包含经验数据和统计上受限的估计值。在自动化用户群体中，88.97%未被封禁；被封禁的子集则偏向近期（70%自2020年以来）。 在针对 100,000 个账户的实证审计中，有 63.06% 个被封禁账户为付费账户（非受限账户），其误差范围经数学证明在 ±0.4% 以内。 在 51,732 名已确认的诈骗者中，有 67.77% 名未因诈骗相关行为受到封禁。所有数据均可通过 Valve 自身的 Web API 复现。\n\n未主张的内容\n\n“Steam”禁令不包含“原因”字段，因此此处的禁令均未归因于特定原因。加入群组并不证明该账号是自动化机器人：由于 ASF 默认允许加入群组（除非手动取消勾选），因此群组成员中既有商业多账号农场，也有普通玩家和爱好者的个人账号。 国家信息由用户自行申报，而 SteamRep 列表是社区裁决，而非法院判决。未披露任何个人姓名。\n\n为何这很重要\n\nValve 采用相同的 API，背后拥有自己的数据库，并且掌握着本次扫描无法查看到的封禁原因。它能在几秒钟内对整个 ID 空间执行此查询。 能够以完全准确的方式生成该数据的唯一一方，从未公布过可供外部方核查针对特定数字的执法主张的衡量标准。这是外部估计值，提供此数据是为了使问题能够附带具体数字进行提出。\n\n接下来阅读：该群体运作的卡牌经济 → ·支持访问和盗窃 → ·完整资料 →",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam 上的账号农场有多大？我们自己做了统计。"
          },
          {
            "level": 2,
            "id": null,
            "text": "一千万个账户，其中九成未被触及"
          },
          {
            "level": 3,
            "id": null,
            "text": "ASF 为您加入该小组"
          },
          {
            "level": 3,
            "id": null,
            "text": "10,880,610 总条目数"
          },
          {
            "level": 3,
            "id": null,
            "text": "88.97% 清理"
          },
          {
            "level": 3,
            "id": null,
            "text": "在 10,880,610 个账户中，有多少个 Valve 被触及过"
          },
          {
            "level": 3,
            "id": null,
            "text": "这支舰队为了维持存在已经付出了Valve"
          },
          {
            "level": 2,
            "id": null,
            "text": "舰队驻扎之地"
          },
          {
            "level": 3,
            "id": null,
            "text": "按申报国家划分的被封禁账号"
          },
          {
            "level": 2,
            "id": null,
            "text": "近期账目，而非历史积压"
          },
          {
            "level": 3,
            "id": null,
            "text": "被封禁的账号是在何时创建的"
          },
          {
            "level": 2,
            "id": null,
            "text": "当 Valve 生效时，其效力在第一年内生效"
          },
          {
            "level": 3,
            "id": null,
            "text": "账号被封时已使用多久了"
          },
          {
            "level": 2,
            "id": null,
            "text": "当 Valve 确实生效时，并不会停止该机器人"
          },
          {
            "level": 3,
            "id": null,
            "text": "那些被封禁的11%到底是因为什么被封禁的"
          },
          {
            "level": 2,
            "id": null,
            "text": "骗子 Valve 走开：51,732 全面人口普查"
          },
          {
            "level": 3,
            "id": null,
            "text": "已确认的诈骗者，根据Valve是否对其实施了与诈骗相关的封禁（全面普查）"
          },
          {
            "level": 4,
            "id": null,
            "text": "两个群体，一项发现"
          },
          {
            "level": 2,
            "id": null,
            "text": "对“100,000”账户的实证审计：僵尸网络并非一次性免费账户"
          },
          {
            "level": 3,
            "id": null,
            "text": "100,000 无偏切片"
          },
          {
            "level": 3,
            "id": null,
            "text": "误差范围 < ±0.4%"
          },
          {
            "level": 3,
            "id": null,
            "text": "为什么任意100k的收益率都相同"
          },
          {
            "level": 3,
            "id": null,
            "text": "100,000 被封禁的账号：付费账号（$5+ 商店消费）与免费受限账号"
          },
          {
            "level": 3,
            "id": null,
            "text": "结构性现实：工业级账户清算"
          },
          {
            "level": 2,
            "id": null,
            "text": "人们是如何理解这一点的，以及它并未主张什么"
          },
          {
            "level": 3,
            "id": null,
            "text": "权利要求"
          },
          {
            "level": 3,
            "id": null,
            "text": "未主张的内容"
          },
          {
            "level": 3,
            "id": null,
            "text": "为何这很重要"
          }
        ],
        "links": [
          "https://help.steampowered.com/en/faqs/view/71D3-35C2-AD96-AA3A",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/asf-ban-census-2026-09-23.json",
          "https://phishdestroy.io/steam_dossier/zh/VALVE_EVIDENCE_PACK/databases/steamrep_steam_bans.csv",
          "https://phishdestroy.io/live-intel/?category=steam",
          "https://phishdestroy.io/steam_dossier/zh/#proxy-bypass-explainer",
          "https://phishdestroy.io/steam_dossier/zh/card_economy.html",
          "https://phishdestroy.io/steam_dossier/zh/VALVE_EVIDENCE_PACK/databases/banned_archiasf_massive.csv",
          "https://phishdestroy.io/steam_dossier/zh/VALVE_EVIDENCE_PACK/databases/slice_100k_limited_results.csv",
          "https://phishdestroy.io/steam_dossier/zh/VALVE_EVIDENCE_PACK/reports/BANNED_100K_FORENSIC_ANALYSIS.md",
          "https://phishdestroy.io/steam_dossier/zh/VALVE_EVIDENCE_PACK/databases/banned_100k_slice.csv",
          "https://phishdestroy.io/steam_dossier/zh/VALVE_EVIDENCE_PACK/reports/STEAM_BANNED_LIMIT_ANALYSIS.md",
          "https://phishdestroy.io/steam_dossier/zh/VALVE_EVIDENCE_PACK/INVESTIGATION_OVERVIEW.md",
          "https://phishdestroy.io/steam_dossier/zh/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/zh/VALVE_EVIDENCE_PACK/reports/STEAMREP_VS_STEAM_AUDIT.md",
          "https://phishdestroy.io/steam_dossier/zh/VALVE_EVIDENCE_PACK/databases/SteamRep_Profiles_BannedCaution_2024.csv",
          "https://phishdestroy.io/steam_dossier/zh/security_timeline.html",
          "https://phishdestroy.io/steam_dossier/zh/VALVE_EVIDENCE_PACK/reports/russian_conflicts_report.json",
          "https://phishdestroy.io/steam_dossier/zh/VALVE_EVIDENCE_PACK/reports/classification_report.json",
          "https://phishdestroy.io/steam_dossier/zh/VALVE_EVIDENCE_PACK/reports/VALVE_INCOMPETENCE_REPORT.md",
          "https://phishdestroy.io/steam_dossier/zh/steam_evidence_archive.html",
          "https://phishdestroy.io/steam_dossier/zh/steam_enforcement_evidence.html",
          "https://phishdestroy.io/steam_dossier/zh/#insider-threat",
          "https://phishdestroy.io/steam_dossier/zh/"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/zh/enforcement_audit.content.json",
      "export_json_sha256": "c702b3eb11de1510c81db35c70061e7a3af7772270325bf4dbc0cff87738c7e4"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "zh/index.html",
      "language": "zh",
      "title": "《Steam 档案》：规则、路线与问责",
      "source_url": "https://phishdestroy.io/steam_dossier/zh/index",
      "source_html_sha256": "ab8b5e29576de3c40331b2a09d2d1421877aee83b3de50d3ef7dc111200f91fe",
      "exported_at": "2026-09-29T00:21:39.237Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "exhibit-gallery-section",
            "source": "https://phishdestroy.io/steam_dossier/zh/index#exhibit-gallery-section"
          }
        ],
        "raster_images_replaced": 2
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "index.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/zh/index.pdf?v=print-20260929-v5",
        "sha256": "749846522ee6d5b8f595c5f0491786fe7603caa7f2fe92e626ac81be1a7dcaa1",
        "bytes": 2614890,
        "pages": 85
      },
      "integrity": {
        "signed_object": "index.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "index.content.json.asc",
        "digest_file": "index.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify index.content.json.asc index.content.json",
          "sha256sum -c index.content.json.sha256"
        ]
      },
      "content": {
        "text": "第1节——案件简报\n这项规则。这项纪录。这些未解之谜。\n上下文与来源限制\n\n六项调查结果，每项均与一份带日期的公共记录相关联。各详细部分的顺序一致：技术记录（A部分）、规则与执法记录（B部分）、法律框架（C部分），随后是附有主要证据的附录。\n\n六项发现。每项发现都将一条书面规则与一份带日期的记录以及一个可通过证据加以检验的问题联系起来。\n\n1. 独立域认证主机 — 44 条路由 · 26 对拆分路由\n\n在册人员登记记录44个通过独立可注册域名进行身份验证的平台.另有五条航线处于待核实状态，尚待确定RDAP日期；若将其纳入，总数将达到47条。这些航线未计入44条航线，也未列入年龄表。 —27，附有已发布的每条路线证据文件 此外，还有17条来自人工收集的数据，另行列出。在26组滤波器-分立器对 主域名是被屏蔽 在 Steam 链接过滤器中被屏蔽，而携带其登录信息的代理却未被屏蔽。这些并非一次性域名：csgogem.com 被屏蔽，而api.csgem.com, 该主机使用 Steam 作为登录名，自 2014 年 3 月起已注册 —12年6个月. Valve 在每次 OpenID 请求中都会接收该主机名，并在其登录页面上将其呈现给用户。完整的表格、各路由的年龄及来源信息详见第 3 节。\n\n沿着路线走 →\n2. 2016年：该机制被命名，截止日期确定\n\n2016年7月13日，Valve公开说明了赌博网站如何利用Steam OpenID和自动化交易账户，其法律顾问于2016年7月20日发出的通知设定了十天的最后期限。 此后，未再发布针对各运营商的执法记录。自该最后期限发出十年后，同一机制仍在不同域名的认证主机上使用，且在2026-09-21上未返回任何Link Filter阻断信息。\n\n阅读致WSGC的公开信 →\n3. 设备关联，使用律师事务所信头纸\n\n在本文转载的通信记录中，Valve的律师描述了将一台设备与多个账户关联的设备级关联机制——而Steam客服此前曾向用户表示，这种关联在技术上是不可能实现的。 目前尚待澄清的问题是：Valve 掌握哪些设备级记录，以及基于何种理由拒绝账户持有人访问这些记录。\n\n阅读备忘录 →\n4. 两种访问响应。一种未提供数据，另一种泄露了数据。\n\n2025年10月： Valve的律师针对一项第15条请求作出了回应，提交了一份长达830页的附录，其中被遮盖的内容是用红色涂改液覆盖在文本上，而非将其删除——902,270 个字符 最终还是得使用标准的提取工具，包括那些原本被横杠遮蔽的第三方标识符。第15条第4款正是这些横杠存在的依据。2026年9月： 工单 HT-2YBP-F7JP-D4VB 在三天后被关闭，附带了一个指向自助“账户数据”页面的链接——该页面无任何数据，也未说明法律依据。截至发布之时，《第12条第3款》规定的一个月期限尚未届满；本异议针对的是实质内容。\n\n阅读编辑检查 →阅读工单记录 →\n5. 市场高于Steam的上限\n\nSteam 将市场上市规模上限设定在约$1,800. 在一份过时的快照（2026年9月23日）中，横跨五个市场，248 个 CS2 商品类别 且其中至少有两项的价格独立地超过了该上限，并且全部 248 个都未出现在 Steam 中; 一本全新的《龙之传说》起价为$10,941 在所有五个市场中列出的389份合约中（第13节中仅限CSFloat的数据，来自9月20日的快照，在62份报价中为$10,623.95）。 以这些价格出售需要借助外部交易平台，而物品转移仍以 Steam 为基准。\n\n关注价格并转账 →\n6. 规则是明确的；审计轨迹却并非如此\n\n《订阅协议》将Steam保留用于个人、非商业用途，禁止商业利用（除非明确允许），禁止使用脚本和机器人，并允许终止账户。Valve于2016年将该条款适用于博彩运营商。 此外，根据CSFloat的工程账号，Valve已关闭IEconItems_730/GetPlayerItems 2017年，取消了公众对原始项目ID的访问权限（未找到 Valve 变更日志）。\n\n将规则放在网络旁边 →\n2016 / 书面请求 10天\n截止日期见法律顾问于2016年7月向博彩网站发出的通知。致WSGC的公开信：第2节。\n2017 / 公开审计轨迹 ID访问已关闭\nCSFloat 会记录原始项目 ID 的丢失情况。\n律师往来信函 设备关联\n一台设备与数十个被盗账户相关联。\n路线登记表 已被封禁，但仍在登录\n规则： Valve在2016年的声明中禁止在Steam OpenID上经营赌博业务。记录： “链接过滤器”上共有26个主要域名，而托管每个域名“Steam”登录账户的主机已运行——csgogem.com的主机已运行12年6个月。\n第2节——公开信\n致华盛顿州博彩委员会的公开信\n\n十天变成了十年。委员会2016年向Valve提出的问题至今未收到按运营商分类的详细记录作为答复；本函要求其重新启动该案件的调查。\n\n公告 · 华盛顿州博彩委员会\n\n十天变成了十年。重新打开该记录。\n\n致华盛顿州博彩委员会：\n\n2016年，主任大卫·特鲁希略要求Valve说明其为阻止将Steam皮肤用于赌博所采取的措施。 时任主席克里斯·斯特恩斯和委员会面对的，是一个建立在Valve发行物品和Steam转让基础上的行业。此后，两人均已离开委员会职务。他们向Valve提出的问题至今尚未得到解答。\n\nValve的总法律顾问卡尔·夸肯布什要求博彩运营商在十天内停止对Steam账户的商业用途。 在10月向贵委员会提交的答复中，Valve否认曾协助赌博活动，称已向四十多个网站发出停止侵权通知书，并已停用相关账户。该公司还为保留Steam交易和OpenID服务进行了辩护，理由是这些服务对客户和游戏开发者有益。那是一种对控制权的宣示。它值得接受检验，而非盲目顺从。\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\n据我们评估，Valve的答复并未证明其采取的执法措施与其所描述的网络规模相称。向运营商发送一封威胁信，与对支撑该业务运行的Steam账户、交易基础设施和身份验证路径实施持久的封锁，是两码事。据报道的估计数据显示，仅CS:GO Lounge一家，2016年的投注总额就超过了$1亿；这只是对投注额的外部估算，而非Valve收入，而且该网站最初的“皮肤投注”业务后来已关闭。鉴于其规模之大，可核查的执法变得至关重要。\n\n今天，Valve的订阅协议 已归档 2026-09-21 ↗ 限制商业利用，但明确允许的情况除外，并单独禁止特定形式的自动化。我们的过期的路线登记册 声明为 OpenID 的记录返回外部服务的主机；openid.realm 以及openid.return_to 这些是发送到 Steam 的字段，而不是对其隐瞒的秘密。我们的链接过滤检查 列举了主地址被发出警告但关联的登录主机未被警告的情况。仅凭过滤结果无法证明Valve允许了登录，也无法证明某个特定的机器人规避了账号封禁。这确实证明，仅在主页上发布警告并不能作为关于访问问题的完整解答。\n\n此外，即使存在有用且合法的Steam交易和OpenID功能，也无法证明被禁止的运营商是否确实被排除在外。Valve自身的规则允许明确的例外情况。 如果 Valve 依赖这一区分，委员会应要求其指明适用于商业皮肤业务的授权、账户管控和执法标准，以及其于2016年援引的具体非赌博用途。仅凭合法使用的可能性，无法反驳有据可查的被禁止用途。\n\n我们请求委员会重新审查其2016年的案卷，并要求按运营商逐一说明：哪些Steam账户和交易机器人已在十天通知期后被停用；是否对相关账户或回传主机进行了监控；哪些运营商随后恢复了访问权限； 批准了哪些豁免；以及有哪些记录能佐证Valve向委员会所作的陈述。请公布法律允许公众查阅的文件。将这些记录与当前的传输路径以及Valve后续的干预措施进行比对，包括2018年的OPSkins 已归档 2026-03-07 ↗.\n\n该通知规定了2016年7月的十天期限；十年时间已经足够确定该通知是否得到了执行。 委员会应根据目前仍可观察到的基础设施，对Valve的2016年账目进行核查。\n\n《Steam档案》调查 · 公开声明，2026年9月20日\n\n2016年委员会公告 ↗ 已归档 2026-05-20 ↗ ·Valve于2016年的回复（文件副本） ↗ ·Valve的 2016 年 OpenID 声明 ↗ 已归档 2026-09-21 ↗ ·当前 Steam 协议 ↗ 已存档 2026-09-21 ↗ · 2016年交流活动的时间表：第11节 →\n\nA部分——技术记录 · 第3节\n该网站被屏蔽了，但登录路由未被屏蔽。\n\n26个被封锁的主域名。每个域名背后的身份验证代理，以及该代理已运行多长时间。 这些独立的认证主机并非偶然出现的备用地址——每个都是一个Steam的身份验证代理，它位于平台与Valve的OpenID端点之间，承担着被封锁域名无法再公开处理的登录任务。Valve将“前门”设置在Link Filter上。登录过程仍通过代理进行：csgogem.com被封锁，并且api.csgem.com 自2014年3月起已注册——十二年半. 在那段时间里，每一天该主机都会将其自身的主机名发送至 Valve 的 OpenID 端点，而 Steam 则会直接在登录页面上将该信息呈现给用户。Valve 是这些路由都经过的主干路；它无需查找这些路由。 本节衡量的正是这一点：不是警告是否存在，而是警告后方的路由还能保持畅通多少年。注册表中共有44条独立域路由，其中27条公布了逐条路由的证据文件——详见下表。先看一个例子，然后对所有路由进行评估。\n\nWhat this means — the Steam Link Filter\n\nValve’s own blocklist for links leaving Steam. Click a listed address inside the client and an interstitial appears instead of the page. It acts on the link that is posted, not on the login a site performs, and it is the only such check that runs inside the Steam client.\n\nSection 3.1 — why it is the only layer →\n\n图3.1 — 两条路线的示意图。\n\n一个平台，一个用户，两个请求从同一个浏览器发出。Valve的链接过滤器同时作用于这两个请求。它拦截携带链接的请求，放行携带登录信息的请求。本节中测量的所有数据，都是指下层路由保持打开状态的时间长度。\n\nThe player\none browser, one session\nrollbit.com\nthe platform's main domain\nrbsnin.com\nseparate authentication host\nLINK FILTER\n✕ BLOCKED\nLINK FILTER\n✓ CLEAN\nsteamcommunity.com\nOpenID endpoint · signs in\nno route\n链接发布于 Steam — 已停止登录请求 — 通过2026年9月19日和21日的已保存支票\n\n这两个请求对 Valve 都是可见的，但只会处理其中一个。 链接过滤器是一个 Valve 列表，由一个 Valve 服务进行检查。 OpenID 请求会将认证主机的自身名称传递给 Valve 的端点，该端点会直接将其显示在登录页面上。无论哪种情况，主机名都会出现在请求中——区别仅在于是否对其进行任何处理。\n\n一个平台。两条不同的路线。ROLLBIT / 已保存的观测数据\n步骤 5 / 5\n\n该请求到达 Steam。 观察到的路径到达了 Steam 的登录表单。作者并未完成登录。屏蔽主域链接并未阻断这条通往登录表单的观察到的路径。\n\n01 链接过滤器检查\n目的地rollbit.com该平台的主域名\nSTEAM LINK 过滤器检查链接一个独立的目的地预警系统\n已保存的结果链接被屏蔽2026年9月19日和21日\n02 观察到的登录路径\n在站台上使用 Steam 登录该平台发起一个 OpenID 请求\n单独的身份验证主机rbsnin.com已保存的检查中没有“无链接过滤器”模块\nSTEAM已显示登录表单请求的主机出现在 Steam 的通知中\n检查原始采集记录、登记日期和方案详情\nValve的执法情况是怎样的\n主域名：被屏蔽\n用户\n→\nrollbit.com\n(主域名)\n↓\nSTEAM LINK 过滤器 — 被屏蔽\n“链接已被屏蔽！”——被标记为可能具有恶意\nrollbit.com 在 2026-09-19 和 2026-09-21 处返回了“链接过滤器”阻断（未经身份验证检查；原始 HTML 和 SHA-256 已保存）。这是一份可见且可审计的记录。\n实际情况是——身份验证\n身份验证主机：未被阻止\n用户\n→\nrollbit.com\n“使用 Steam 登录”\n↓\n通过单独的身份验证主机进行重定向：\nrbsnin.com链接过滤器：CLEAN\n已注册 2026-09-18T09:34:52Z (Verisign RDAP)\n↓\nSteam 登录页面提示 (2026-09-20)：\n\"Note that rbsnin.com is not affiliated with Steam or Valve\"\nSteam 根据收到的请求的 openid.realm 显示此通知。\n↓\nSteam 为独立主机提供的登录表单\n作者未完成登录操作；观察到的流程仅到 Steam 表单为止。\nValve 在每次此类请求中都会收到 return_to / realm 主机名。rbsnin.com 针对 2026-09-21 未返回任何链接过滤器阻塞信息。\n应要求\n作为 OpenID 提供商，Steam 在每次身份验证请求中都会收到身份验证主机名：该主机名会传送到 Valve 自身的服务器上，位于openid.return_to 以及openid.realm 参数。\n由网站发送\n无法通过扫描发现身份验证主机——平台会在每个请求中将其发送至 Steam。根据 OpenID 2.0 第 9.1 节return_to 虽然从形式上讲是可选的，但如果没有它，Steam 就无法返回登录结果，因此对于能正常工作的 Steam 登录来说，它实际上是必需的。Steam 甚至会将主机名显示给用户（“<host> 与 Steam 或 Valve 无关联\"）。\n14岁\n这是在第 2026-09-21 次检查时，仍持有 Steam 次登录记录的最老授权主机的年龄（dota2.net，注册于 2011-10-29）；最新的主机已存在三天（rbsnin.com）。请不要将“0 个未经身份验证的主机被阻止”这一数字视为调查结果。 被封禁的认证主机将直接导致平台的“通过 Steam 登录”功能失效，因此由有效登录记录构建的注册表中只能包含从未被封禁的主机。 真正具有意义的数字并非封禁次数，而是主域名在“链接过滤器”中被封禁的年数，而其旁边的登录账号在此期间却一直正常运行。\n独立域名的认证主机：注册日期与主域名的对比（30条路由：其中25条在2026-09-21浏览器审计中已解析，另有5条于2026-09-22新增）\n平台\t链接过滤器：主\t身份验证主机\t链接过滤器：认证主机\t已注册身份验证主机\t观测来源\t证据文件\nRollbit\nrollbit.com · 注册 2014-11-08\n\t被屏蔽\n2026-09-19，2026-09-21 ·Wayback 2026-09-21\n\trbsnin.com\tCLEAN\n2026-09-21 ·原始 HTML （没有Wayback快照）\n\t2026-09-18\n09:34:52Z，Verisign RDAP\n\tSteam 登录页面提示， 2026-09-20\trollbit.com.json\nSkin.Club\nskin.club · 注册 2017-09-04\n\t被屏蔽\n2026-09-19, 2026-09-21 ·Wayback 2026-09-21\n\tsc-auth.net\tCLEAN\n2026-09-21 ·Wayback 2026-09-21\n\t2019-04-02\nRDAP\n\tSteam 登录页面提示\tskin.club.json\nHowl.GG\nhowl.gg · 注册 2017-03-16\n\t被屏蔽\n2026-09-18, 9月19日, 9月21日 ·Wayback 2026-09-21\n\thowl.uno\tCLEAN\n2026-09-21 ·Wayback 2026-09-21\n\t2026-08-11\nRDAP\n\t实时浏览器截图 + 提供的 OpenID 网址\thowl.gg.json\nDuelbits\nduelbits.com · 注册 2020-02-03\n\t被屏蔽\n2026-09-21 ·Wayback 2026-09-21\n\tswitchflips.com\tCLEAN\n2026-09-21 ·Wayback 2026-09-21\n\t2020-04-21\nRDAP\n\t提供的 OpenID URL\tduelbits.com.json\nCSGOFast\ncsgofast.com · 注册 2015-03-27\n\t被屏蔽\n2026-09-19, 2026-09-21 ·Wayback 2026-09-21\n\tsteam-login.authtofast.com\tCLEAN\nauthtofast.com，2026-09-21 ·Wayback 2026-09-21\n\t2026-06-30\nauthtofast.com，RDAP\n\t实时浏览器截图 + 提供的 OpenID 网址\tcsgofast.com.json\nFarmskins\nfarmskins.com · 注册 2016-03-23\n\t被屏蔽\n2026-09-19, 2026-09-21 ·原始 HTML\n\tsteam.kobal.cc\tCLEAN\n2026-09-19, 2026-09-21 ·原始 HTML\n\t2017-01-07\nkobal.cc，RDAP\n\t实时浏览器截图 + 提供的 OpenID 网址\tfarmskins.com.json\nCobaltLab\ncobaltlab.tech\n\t被屏蔽\n2026-09-21 ·原始 HTML\n\tcobaltauth.com\tCLEAN\n2026-09-21 ·原始 HTML\n\t2025-01-07\nRDAP\n\t提供的 OpenID URL\tcobaltlab.tech.json\nCSGO.NET\ncsgo.net · 注册 2012-07-22\n\t被屏蔽\n2026-09-21 ·原始 HTML\n\tcn2.easylot.net\tCLEAN\n2026-09-21 ·原始 HTML\n\t2016-09-03\neasylot.net，RDAP\n\t实时浏览器屏幕录制\tcsgo.net.json\nGGDrop\nggdrop.com\n\t被屏蔽\n2026-09-21 ·原始 HTML\n\tggauth.com\tCLEAN\n2026-09-21 ·原始 HTML\n\t2023-05-03\nRDAP\n\t提供的 OpenID URL\tggdrop.com.json\nRustChance\nrustchance.com\n\t被屏蔽\n2026-09-21 ·原始 HTML\n\thgfuihd.com\tCLEAN\n2026-09-21 ·原始 HTML\n\t2019-01-27\nRDAP\n\t提供的 OpenID URL\trustchance.com.json\nSkin.Fans\nskin.fans\n\t被屏蔽\n2026-09-21 ·原始 HTML\n\tauth.skinfans.com\tCLEAN\n2026-09-21 ·原始 HTML\n\t2018-07-16\nskinfans.com，RDAP\n\t提供的 OpenID URL\tskin.fans.json\nSkinport\nskinport.com · 注册 2018-09-05\n\t被屏蔽\n2026-09-21 ·原始 HTML\n\tskinport.app\tCLEAN\n2026-09-21 ·原始 HTML\n\t2020-06-20\nRDAP\n\t实时浏览器截图 + 提供的 OpenID 网址\tskinport.com.json\nSkins.Cash\nskins.cash\n\t被屏蔽\n2026-09-21 ·原始 HTML\n\tskinscash.live\tCLEAN\n2026-09-21 ·原始 HTML\n\t2019-12-05\nRDAP\n\t提供的 OpenID 网址\tskins.cash.json\nTF2Hunt\ntf2hunt.com · 注册 2018-01-13\n\t被屏蔽\n2026-09-21 ·原始 HTML\n\trstspcl.com\tCLEAN\n2026-09-21 ·原始 HTML\n\t2020-08-08\nRDAP\n\t实时浏览器截图 + 提供的 OpenID 网址\ttf2hunt.com.json\nCSGOGem\ncsgogem.com · 注册 2016-10-16\n\t被屏蔽\n2026-09-22 ·原始 HTML\n\tapi.csgem.com\ncsgem.com — 独立可注册域名\n\tCLEAN\n2026-09-22 ·原始 HTML\n\t2014-03-08\ncsgem.com，RDAP——注册时间最久\n\t手动收集 + 链接过滤捕获\tlinkfilter-2026-09-22.json\nGamdom\ngamdom.com · 注册 2016-07-29\n\t被屏蔽\n2026-09-22 ·原始 HTML\n\tlogin.gambldom.com\ngambldom.com —— 与品牌名称仅差一个字母\n\tCLEAN\n2026-09-22 ·原始 HTML\n\t2017-09-24\ngambldom.com，RDAP\n\t手动收集 + 链接过滤捕获\tlinkfilter-2026-09-22.json\n12CS\n12cs.fail · reg. 2026-03-24\n\t被屏蔽\n2026-09-22 ·原始 HTML\n\tfail.games\tCLEAN\n2026-09-22 ·原始 HTML\n\t2021-08-24\nfail.games，RDAP\n\t手动收集 + 链接过滤器捕获\tlinkfilter-2026-09-22.json\nCSGOEmpire\ncsgoempire.com · 注册 2015-06-10\n\tCLEAN\n2026-09-19, 2026-09-21 ·Wayback 2026-09-21\n\tcsgoempirelogin4.com\n十个编号域名之一：login1–10\n\tCLEAN\n2026-09-21 ·Wayback 2026-09-21\n\t2020-07-20\n05:49:17Z，Verisign RDAP\n\t实时浏览器屏幕录制\tcsgoempire.com.json\nCS.MONEY\ncs.money\n\tCLEAN\n2026-09-21 ·原始 HTML\n\tauth.dota.trade\tCLEAN\n2026-09-21 ·原始 HTML\n\t2016-07-15\ndota.trade，RDAP\n\tSteam 登录页面提示\tcs.money.json\nCSFloat\ncsfloat.com · 注册 2021-07-11\n\tCLEAN\n2026-09-21 ·原始 HTML\n\tcsgofloat.com\n运营商此前使用的品牌域名；一个可单独注册的域名，并非规避行为的指标\n\tCLEAN\n2026-09-21 ·原始 HTML\n\t2015-09-29\nRDAP\n\t实时浏览器屏幕录制\tcsfloat.com.json\nG4Skins\ng4skins.com\n\tCLEAN\n2026-09-21 ·原始 HTML\n\tauth.g4s.to\tCLEAN\n2026-09-21 ·原始 HTML\n\t2021-05-30\ng4s.to，RDAP\n\t提供的 OpenID URL\tg4skins.com.json\nJuice.GG\njuice.gg\n\tCLEAN\n2026-09-21 ·原始 HTML\n\tletmeinjuice.com\tCLEAN\n2026-09-21 ·原始 HTML\n\t2024-04-15\nRDAP\n\t提供的 OpenID URL\tjuice.gg.json\nMarket.CSGO\nmarket.csgo.com\n\tCLEAN\n2026-09-21 ·原始 HTML\n\tdota2.net\tCLEAN\n2026-09-21 ·原始 HTML\n\t2011-10-29\nRDAP\n\t实时浏览器截图 + 提供的 OpenID 网址\tmarket.csgo.com.json\nRust.TM\nrust.tm\n\tCLEAN\n2026-09-21 ·原始 HTML\n\tdota2.net\tCLEAN\n2026-09-21 ·原始 HTML\n\t2011-10-29\nRDAP\n\t提供的 OpenID URL\trust.tm.json\nCSGOLounge\ncsgolounge.com · 注册 2013-08-14\n\tCLEAN\n2026-09-22 ·原始 HTML\n\tdota2.net\n该身份验证主机上的第三个前端\n\tCLEAN\n2026-09-22 ·原始 HTML\n\t2011-10-29\ndota2.net，RDAP\n\t手动收集 + 链接过滤器捕获\tlinkfilter-2026-09-22.json\nDota2Lounge\ndota2lounge.com · 注册 2012-08-10\n\tCLEAN\n2026-09-22 ·原始 HTML\n\tdota2.net\n该认证主机上的第四个前端\n\tCLEAN\n2026-09-22 ·原始 HTML\n\t2011-10-29\ndota2.net，RDAP\n\t手动收集 + 链接过滤捕获\tlinkfilter-2026-09-22.json\nSkinBaron\nskinbaron.de\n\tCLEAN\n2026-09-21 ·原始 HTML\n\tskinbaron.com\n同一品牌，不同顶级域名\n\tCLEAN\n2026-09-21 ·原始 HTML\n\t2015-12-22\nRDAP\n\t提供的 OpenID URL\tskinbaron.de.json\nTF2Royal\ntf2royal.com · 注册 2022-08-17\n\tCLEAN\n2026-09-21 ·原始 HTML\n\ttf2auth.com\tCLEAN\n2026-09-21 ·原始 HTML\n\t2021-07-27\nRDAP\n\t实时浏览器截图 + 提供的 OpenID 网址\ttf2royal.com.json\nTradeit\ntradeit.gg\n\tCLEAN\n2026-09-21 ·原始 HTML\n\tconnect-tradeit.com\tCLEAN\n2026-09-21 ·原始 HTML\n\t2022-02-23\nRDAP\n\t提供的 OpenID URL\ttradeit.gg.json\n升级器\nupgrader.pro\n\tCLEAN\n2026-09-21 ·原始 HTML\n\tupgauth.space\tCLEAN\n2026-09-21 ·原始 HTML\n\t2026-08-14\nRDAP\n\t提供的 OpenID URL\tupgrader.pro.json\n来源：steamcommunity.com/linkfilter，未经身份验证的 GET 请求，2026-09-21，53 个主机，间隔 3 秒；steam_tos_assets/linkfilter-recheck-2026-09-21.json; 原始 HTML 代码位于steam_tos_assets/linkfilter-raw/. 注册日期：RDAP，steam_tos_assets/domain-registration.json. · 之前对 2026-09-19 的检查在linkfilter-all-results.json · 在中输入路由记录auth-route-audit.json · “Link Filter”页面（编号 2026-09-21）的Wayback Machine快照，列于wayback-snapshots.json （rbsnin.com 没有快照；本地原始文件是唯一的记录）。\n\n注册日期：RDAP（steam_tos_assets/domain-registry/). “提供的 OpenID URL”仅确定了请求参数，并不代表登录已完成。作者在任何平台上均未完成登录。 单独的域名本身并不能证明存在规避行为。“0个被封锁的认证主机”也不是独立的发现：封锁其中一个将导致该平台的Steam登录功能失效，因此由有效登录信息组成的注册表中不可能包含被封锁的认证主机。 具有说服力的观察结果是配对关系及其持续时间——Link Filter 中的主域名与一个已运行多年的登录域名并列。该表格包含 30 行：27 条带有每条路由证据文件的路线中的 25 条，外加 5 条在 2026-09-22 上添加的路线，其 Link Filter 拆分情况记录在linkfilter-2026-09-22.json 尽管该域本身是手动收集的——源列中的行信息已说明这一点。未显示的两条证据文件路径是 skinsnipe.com（授权主机pricing.tradeupspy.com, 注册号 2020-03-11) 和 csgobig.com（授权主机letmeinbig.com, 已注册 2023-01-20）；两者在对 2026-09-22 的检查中均返回“BLOCKED main / CLEAN auth host”，并以 SHA-256 格式记录在linkfilter-2026-09-22c.json，但该批次的原始 HTML 并未包含在已发布的数据集中，因此这里仅列出了其名称，而非为本表中其他所有行均能佐证的那种单独行。登记册中剩余的 12 条人工收集的路线在master_registry.json 下realm_src: user.\n\n主要实证审计 · 多年日期范围\n“全局陷阱”：链接过滤只是合规作秀，而非防护盾\n\n在桌面浏览器中，用户受到外部防护机制的保护：Google 安全浏览和微软 SmartScreen 会通过全屏红色警告拦截已知的网络钓鱼攻击。在 Steam 的“大画面”模式、游戏内叠加层（Shift+Tab）以及 Steam 卡组（SteamOS）中，这些防御机制并不存在。 该嵌入式浏览器不支持任何扩展程序，禁用了外部“安全浏览”引擎，从而仅为用户留下了一道防护屏障：Valve'slinkfilter 间质性。\n\n滑动查看全部四项结果 →\n\n92.5%\n2025–2026 年新型网络钓鱼通过，无问题 (37/40)\n77.5%\n2023–2024 CS2时代网络钓鱼通过，无问题 (31/40)\n70.0%\n2021–2022年传统网络钓鱼通过，无问题 (28/40)\n7 / 7\n赌博主线被封锁（阳性对照）\n多年纵向审计：对120个纯Steam钓鱼域名进行实时测试（2026年9月24日）\n\n为了验证Valve的过滤器究竟是单纯在识别新威胁时反应迟缓，还是从根本上无法察觉这些威胁，我们对它进行了审计已确认120个针对Steam的钓鱼域名 在三个历史队列中，与……相比steamcommunity.com/linkfilter:\n\n第一期：2021–2022（经典交易报价与道具掉落）—— 70.0% 全过（28/40）。 即使在被社区监督机构收录后4至5年，10个旧版网络钓鱼主机中仍有7个仍可正常访问，未被封锁。\n第二期：2023–2024 年（CS2 Beta 炒作与虚假支持申诉）—— 77.5% 完美通过（31/40）。 冒充《反恐精英2》发布的宣传活动以及虚假的社区呼吁（例如：cs2-steam.com,appealsteamcommunity.help) 直接穿过。\n第3期：2025–2026年（无服务器边缘部署与网站图标克隆）—— 92.5% 完美通过（37/40）。 部署在 EdgeOne、Vercel 和 Cloudflare Pages 上的现代网络钓鱼工具包（例如steamgifter.online,steam-dp4lt5b8fnez.edgeone.dev) 几乎畅通无阻地通过。\n\n遥测与责任免责，而非保护。 既然“链接过滤器”会将纯属“2”类网络钓鱼的链接从“0”级放行至“1”级，那它存在的意义何在？它的作用是作为企业的免责声明，同时也是外链点击行为的监测传感器。通过以礼貌的方式“您即将离开 Steam” 该通知上带有可点击的绿色“继续”按钮，Valve根据Steam《订阅协议》（*“用户自愿跳转至Steam之外”*）将法律责任转嫁给受害者。 Valve 会收集点击的遥测数据，但不会阻止盗用行为。\n\n网站图标哈希验证：完全不引入威胁情报源。 独立威胁情报平台（urlscan.io、Shodan、Censys）通过简单搜索 Steam 的官方网站图标哈希值，即可识别出正在运行的 Steam 钓鱼工具包（page.favicon.hash:9f890a9debcdfccc339149a7943be9aff9e4c9203c2fa37d5671a5b2c88503ad NOT domain:*.steampowered.com). 这一基础自动化检测可在数秒内发现活跃的网络钓鱼集群。Valve 不与外部数据源同步，不进行基于哈希值的威胁狩猎，仅在受到监管机构强制要求（如2016年WSGC博彩令）或为保护其注册商标域名时才会进行人工干预。\n\n主要审计证据凭证： 一项涵盖120个领域的纵向多年审计：longitudinal-steam-phishing-audit.json · 100 个专门的 Steam 钓鱼攻击样本：linkfilter-steam-phishing-100.json · 广泛的饲料审计（n=250）：linkfilter-coverage-2026-09-22.json.\n\nCSGOEmpire —— 批量注册十个带编号的授权域名\n\n关于2020-07-20 十个编号域名，csgoempirelogin1.com 通过csgoempirelogin10.com，均已注册。这十个登录记录均附有威瑞信（Verisign）RDAP时间戳：login1 05:49:06Z、login5 05:49:08Z、login2 05:49:11Z、login3 05:49:14Z、 login4 05:49:17Z、login6 05:49:20Z、login7 05:49:23Z、login8 05:49:26Z、login9 05:49:28Z —22秒内完成9个域名的注册 — 以及 login10 于 05:56:03Z 进行的操作，间隔七分钟。这些操作的时间间隔与单一注册商的批量操作相符。\n\n该模式与预配置的备用主机一致；只是login4 已在实际的 OpenID 请求中观察到该现象。csgoempire.com 和 csgoempirelogin4.com 在 2026-09-21 的链接过滤器中均返回了“CLEAN”结果；CSGOEmpire 并未出现在 2016 年 7 月通知相关媒体报道中提到的网站名单中。\n\n# DNS — 全部 10 个均处于活动状态（2026 年 9 月）\n好的 csgoempirelogin1.com 172.67.129.43\n好的 csgoempirelogin2.com 172.67.175.168\n好的 csgoempirelogin3.com 188.114.96.3\n好的 csgoempirelogin4.com 188.114.96.11 ← 在 OpenID 流量中\n好的 csgoempirelogin5.com 172.67.160.194\n好的 csgoempirelogin6–10.com Cloudflare IP地址\nNXDOMAIN：csgoempirelogin11.com\n全部 10 个已注册 2020-07-20；全部 10 个均带有 RDAP 时间戳（steam_tos_assets/domain-registry/csgoempireloginN.com.rdap.json）\n对监管机构的结论\n如果主域名被封锁，而认证主机未被封锁，登录路径就会保持开放——而且这种状态会持续数年之久。\n\n主域上的“链接过滤器”块是一条可验证的公开记录。认证主机承载着“使用 Steam 登录”的流量，并出现在 Valve 自身的 OpenID 请求参数中。 通过对 2026-09-21 和 2026-09-22 的跨域核查，在 26 对过滤器拆分组合中，主域返回了 Link Filter 阻断，而承载其登录请求的代理则未返回任何阻断。上文的注册记录衡量了另一半情况：这些主机并非短暂存在的临时域名。 其中部分域名在检查之日已注册超过十年，而这十年的每一天，Valve都在其自身的请求参数中接收到过该主机名。 Valve 未公布按运营商分类的执法记录，因此无法通过公开数据确定是否对这些主机采取了其他措施。\n\n12岁6个月\ncsgogem.com 在“链接过滤器”中被屏蔽了。\n其登录主机api.csgem.com 一直\n自 2014-03-08 起注册，但并非如此。\n通俗易懂的摘要——供监管机构和法院参考（展开）\n通俗易懂的摘要——供监管机构参考\n背景：什么是 Steam 以及它为何在此处重要\n\nSteam 是由 Valve 公司（美国华盛顿州贝尔维尤）运营的一个软件平台。 Steam 作为数字身份提供商发挥作用：互联网上的各类博彩和游戏网站均使用名为“通过 Steam 登录”的系统——该按钮可让网站验证访问者是否拥有真实的 Steam 账户。 这类似于“通过 Google 登录”或政府签发的身份证件核验：网站将用户引导至 Steam 的服务器，Steam 确认其身份，然后 Steam 将用户重新导向该网站。 Valve 负责运营身份验证系统。每次通过“使用 Steam 登录”进行的登录操作，都会经过 Valve 自身的服务器。\n\nValve 做了什么：域名屏蔽\n\n2016年7月，在媒体和法律界就“皮肤赌博”施加压力后，Valve的律师向约23家被点名的赌博网站（据2016年7月21日媒体报道）发送了通知； 2016年10月，Valve向华盛顿州赌博委员会表示，其已联系了四十多个网站。部分赌博域名出现在Steam 链接过滤器 — 该列表会使在 Steam 内发布的任何指向这些链接的内容（包括聊天、个人资料页面和商店中的链接）显示警告页面：“链接被屏蔽！” 链接过滤器是唯一一种其效果可从Valve外部观察到的强制措施。\n\n示例： 指向rollbit.com 在 Steam 中会显示“链接过滤器”警告页面（已勾选 2026-09-19 和 2026-09-21）。 理论上，该赌博网站已被屏蔽。\n什么是代理域名\n\nA独立域认证主机是一个认证代理：一个位于不同可注册域名下的第二个网站地址，由同一运营商设置在用户与 Steam 之间，其唯一目的是实现“通过 Steam 登录”这一步骤。它充当了登录的代理。 用户以为自己正在登录该平台；但最终到达 Valve 的请求携带的是代理服务器的主机名，而非该平台的主机名。 该网站通常与赌博网站之间没有公开可见的关联，且在 Steam 确认用户身份后，用户将被重定向回该地址。\n\n示例： Rollbit 根据以下条款运营：rollbit.com，该流量被链路过滤器拦截。 对于 Steam 身份验证，在 2026-09-20 上观察到的流量使用了另一个地址：rbsnin.com, 注册号 2026-09-18。 该地址返回没有“链接过滤”模块 在 2026-09-21 时。 该赌博网站继续运营，其 Steam 登录流程通过未被屏蔽的主机进行。\n关键点：每次请求中都会将认证主机发送至 Steam\n\nValve 无需进行扫描或爬取即可了解哪些认证主机正在使用中。Steam 是OpenID 身份提供商 对于这些网站，每次点击“使用 Steam 登录”都会向 Valve 的自有服务器发送一个 GET 请求，其中包含以明文形式传输的认证主机名。 根据 OpenID 2.0 第 9.1 节的规定，return_to 该字段从形式上来说是可选的，但如果没有它，Steam 就无法返回登录结果，因此对于能正常工作的 Steam 登录而言，它实际上是必需的。Steam 本身会在登录页面上显示主机名（“<host> 与 Steam 或 Valve 无关联\"）。\n\n— 请求的格式 Steam 接收（根据 2026-09-20 上 Rollbit 的观察结果，主机为）： —\nGET steamcommunity.com/openid/login\n&openid.mode=checkid_setup\n&openid.return_to=https://rbsnin.com/… ← 实际上是必需的；会出现在 Valve 的日志中\n&openid.realm=https://rbsnin.com ← 由网站自行声明；显示在 Steam 的登录页面上\n如果该网站使用服务器间验证（check_authentication），Valve的日志中还会记录该平台的服务器 IP 地址和托管网络。\n\n从该请求中提取主机名是一项标准操作。执行记录——即哪些主机被处理、哪些未被处理，以及依据何种标准——仅存在于Valve的基础设施中，尚未公开。\n\n这证明了什么\n\n1. “链接过滤器”模块作用于链接，而非登录操作。 屏蔽主域名（例如rollbit.com) 会向点击 Steam 内相关链接的用户显示一条警告。 这不会阻止该网站正常运行，也不会阻止其通过其他地址使用 Valve 自身的 OpenID 服务。\n\n2. 测试的身份验证主机未被封锁。 上表显示了2011年至2026年9月期间注册的独立域名认证主机，其中部分主机是在2016年7月通知发布数年后才注册的。 在26对组合中，主域返回了“链接过滤”阻断响应，而承载其登录信息的代理则未返回（未经身份验证的检查，2026-09-21和2026-09-22；已保存原始响应和SHA-256值）。 该代理会在 Valve 拒绝其请求的当天停止工作，因此此处的衡量标准是其运行时长，而非是否被列入黑名单。 Valve 会在其自身的 OpenID 请求中接收这些主机名。无法从公开数据中确定是否应用了除链接过滤器以外的其他措施，因为 Valve 未发布按运营商分类的执行记录。\n\n3. 这些网站继续通过 Valve 的基础设施进行身份验证。 “使用 Steam 登录”是 Valve 提供的一项服务；通过该服务进行的每次身份验证，都是 Valve 接收并处理的一个请求。 Valve 还通过案例密钥获取收入，而 Steam 社区市场对在市场内完成的交易（不包括外部交易）收取总计约 15% 的费用。 “链接过滤器”操作创建了一条公共记录；它并未中断身份验证关系。\n\n拦截会奏效吗？\n\n以此类推：当免费域名注册商 Freenom 于 2023 年停止运营时，依赖其域名的网络钓鱼活动也随之中断。运营的连续性取决于基础设施的稳定性。\n\n同样的逻辑也适用于此处。如果在 Steam 的 OpenID 处理过程中某个认证主机被拒绝，那么该平台的“使用 Steam 登录”功能将无法正常工作，直到注册新的主机、签发证书并完成 DNS 传播为止。在此期间：系统将处于停机状态。\n\n轮换并不意味着拦截毫无意义。 这使得封禁成为一项运营成本。由于新主机在首次使用时会出现在Valve自身的请求日志中，因此响应速度可能会受到首次使用情况的影响。\n\n批量注册本身就是一种信号： CSGOEmpire 的 login1–login10 于 2020-07-20 注册，其中 9 个是在 22 秒内注册的（Verisign RDAP）。响应不必按域名逐个列出；来自同一注册商会话的一组连续记录可被视为一个系列。\n\n公开记录中并未显示曾有试图封锁授权主机的行为，且该行为被轮换机制挫败。\n数据显示，尽管各登录请求由代理服务器转发，但主要域名仍被封锁——截至2026-09-22，共有26对域名，其中最早注册的认证主机已有12年6个月的历史——且没有任何运营商的公开执行记录。\n因此，监管机构面临的问题是：Valve对其自身OpenID请求中收到的授权主机采取了哪些执法措施（如果有的话）？\nValve 做了什么——以及为什么它没有中断身份验证路径\n\n下表将每项公开记录的 Valve 操作与其是否影响 OpenID 身份验证入口点进行了对应。 调查结果并非“Valve 未采取任何行动”——而是指所有公开记录的行动均未涉及赌博平台登录信息通过 Valve 服务器传输的环节。\n\n日期\tValve 操作\t受影响的openid.return_to 路径？\n2016年7月\t2016年7月13日的公开声明；律师向约23个指定网站发出的通知（2016年7月21日媒体报道）；根据Valve于2016年10月致WSGC的信函，已联系超过40个网站\t不。通知和链接过滤器作用于操作符和链接；OpenID 请求路径并未发生改变。\n2017\t关闭IEconItems_730/GetPlayerItems （根据 CSFloat 的工程账号；未找到 Valve 的更新日志）\t否。受影响的是公共条目的历史记录可见性。OpenID 身份验证未作修改。\n2018-03-29\t《CS:GO》宣布实施7天交易锁定（blog.counter-strike.net）\t不。仅是项目移动速度变慢了；OpenID 请求路径并未更改。\n2022-05-10\t从公开 Web API 中移除了交易取消端点（由用户发现；无 Valve 变更日志 — node-steam-tradeoffer-manager #325）\t否。已关闭报价交换工具；OpenID 身份验证未作修改。\n2023-12-04\t创建 API 密钥现在需要手机验证（steamcommunity.com/dev/apikey；无更新日志）\t否。已保护关键端点；本文中记录的身份验证主机未受影响。\n2026-09-19 / 09-21\tSteam 作者观察到的链接过滤状态\t在保存的 2026-09-21 重新检查中，第 14 个主域返回了一个块——寄存器中按 2026-09-22 划分的 26 对——而承载每个登录的代理仍在运行。\n来源：Valve 2016年7月13日的声明（store.steampowered.com/oldnews/22883,已归档 2026-09-21) · CSFloat关于2017年关闭事件的工程报告 (blog.csfloat.com,已归档 2026-09-21) · 链接过滤器状态：linkfilter-recheck-2026-09-21.json.\n如果存在哪怕一个已发表的案例，表明 Valve 因以下原因拒绝了 OpenID 请求，则该结论即被证伪：openid.return_to 指向了一个赌博授权主机。在公开记录中未找到此类实例。\n最近的两条 auth-host 注册记录\nhowl.uno该域名于 2026-08-11（RDAP）注册，比 2026-09-21早 41 天；howl.gg 在 2026-09-18、2026-09-19 和 2026-09-21 返回了链接过滤阻塞。 该封禁是否发生在注册之前，目前尚无定论。\nrbsnin.com该域名已于 2026-09-18T09:34:52Z 注册（Verisign RDAP），并于 2026-09-20 通过 Steam 自身登录页面的提示，在 Rollbit 的 Steam 登录流程中被观察到； rollbit.com 在 2026-09-19 和 2026-09-21 返回了链接过滤器阻断，而 rbsnin.com 则未返回。\n上表中的每个主机都会以以下形式发送至 Valve 的认证服务器：openid.realm 每次登录尝试时。\n完整的每条路由数据和链路过滤结果：见上文第3节中的表格；原始结果见linkfilter-recheck-2026-09-21.json 以及linkfilter-all-results.json.\n方法论——路由和链路过滤计数的确定方法\n1. 域名解析\n此次 2026-09-21 审计处理了 189 个被要求审查的平台中的 78 个：其中 33 个通过自身主机名进行身份验证，20 个通过自身子域名进行身份验证——这属于直接身份验证，且均不被计为独立域路由。 剩下的25 通过一个单独的可注册域名进行身份验证，分布在24个不同的主机名上（dota2.net 与 market.csgo.com 和 rust.tm 共用）：其中10个通过实时浏览器截图确认，3个来自 Steam 登录页面的提示，12个来自提供的 OpenID 链接。实时注册表（master_registry.json, 2026-09-22) 将其扩展为44条独立域路由: 26 对带过滤拆分的路由（主域被阻止，授权主机被放行），以及另外 18 条不带主域拆分的路由。在这 44 条路由中，27 建立按路线分类的证据文件；其余17个是手工采集的，并已做标记realm_src: user 在注册表中。 这十七个域名中有五个——csgogem.com、gamdom.com、12cs.fail、csgolounge.com 和 dota2lounge.com——是在 2026-09-22 添加的，同时对这两个主机进行了链接过滤捕获（原始 HTML + SHA-256 值在linkfilter-2026-09-22.json)，因此尽管该域是手动收集的，但分裂现象本身仍有据可查；它们与证据文件中的路径一同出现在上表中。tfauth.com (tf2easy.com) 已于 2026-09-22: 从注册库中移除：与 arena.fragnet.net 一样，没有任何可验证的信息将其与原始网站关联起来。该计数可从已发布的auth-route-audit.json (2026-09-21 连续) 由一条规则决定：只有当平台的已观察到的 Steam OpenID 主机位于与该平台本身不同的可注册域名上时，该平台才被计入。\n2. Steam 链接过滤器状态\n通过以下方式测试steamcommunity.com/linkfilter/?url=https://[domain]，未经过身份验证，位于 2026-09-19 和 2026-09-21；原始 HTML 已使用 SHA-256 进行保存。主域名和身份验证主机的状态分别记录。 分类器可区分通用提示“您即将离开 Steam”（CLEAN）与“链接被阻止！……被标记为潜在恶意”页面（BLOCKED）；通过 google.com 控制组验证，确认二者未被混淆。 此测试的一个早期经过身份验证的变体已被弃用，因为它对包括该对照域在内的所有域都返回了“被阻止”的结果——经追踪发现，这是由于探测脚本中的会话 Cookie 无效所致，并非真实结果。\n3. 对认证主机的观察\n实时捕获：一个 Playwright 浏览器依次访问了各平台的登录流程，并openid.return_to 主机名是从拦截的请求中读取的。登录页面提示：该主机名是从 Steam 自身的“<host> 与 Steam 或 Valve 并无关联\" 该文本由 Steam 转换自openid.realm (rbsnin.com, sc-auth.net, auth.dota.trade)。提供的网址：向作者提供的 a Steam 登录表单网址；该网址仅用于设定请求参数，并非完整的登录操作。在任何平台上均未完成登录。\n4. 报道范围——哪些问题尚未解决，以及这为何重要\n在189个平台中，110 未形成固定路线 其中一项不适用（189 − 78 − 1）。该档案中未计入任何一项。 根据审计文件，这110个案例的细分情况如下：22个机器人验证挑战、14个超时、12个HTTP错误和10个导航错误——观察者无法进入登录流程，尽管其中大多数网站在普通浏览器中可以正常打开； 20个网站在登录页面上未显示Steam登录控件；16个网站虽然进入了登录流程，但无法解析为主机；11个域名在DNS中无法解析；5个网站在同意墙处停止。 下方的记录表对这110个网站进行了不同的分类：其中11个在DNS中无法解析的网站被单独列为已删除 · NXDOMAIN，而那个不符合条件的条目也加入了其余条目之列。共审核了189个平台，其中11个因两个解析器均返回明确的NXDOMAIN响应而被移除，178 保留 (platform-audit.json,platforms-removed.json). 账本根据命名模式推测出的 137 个认证域已被从 2026-09-19 的数据中删除——从未被观察到，因此也无从作为证据。 其中有三个猜测与提供的 OpenID URL 不符：buff.163.com、gamerpay.gg 和 csgoluck.com 直接进行身份验证，而猜测的 URL 分别是 buffauthproxy.163.com、gamerpayredirect.io 和 lucklogin.app。被移除的项目已在发布的审计文件中列出。\n25是一个下限，而非上限。在成功解析的78个平台中，有25个使用了独立域名，53个未使用。该比例并未对未解析的110个平台作出任何推断，且本文件中任何地方均未据此进行推测。 任何人只需打开该网站并点击“通过 Steam 登录”，即可解决其中任何一个问题：加载的 Steam 页面的 URL 中就包含认证主机名。\n本节的要点： 一位独立观察者需要一个浏览器和极大的耐心才能识别出189个平台，最终识别出了78个。Valve需要进行数据库查询。每个使用“通过Steam登录”功能的平台——无论是否已被识别——都会发送openid.realm 每次登录时都会发送到 Valve 的身份验证端点。该表中存在这一空白，是因为作者不在该系统内。对于 Valve 则不存在此情况。\n观察到的代理主机名位于auth-route-audit.json. 域名注册日期来自 RDAP（Verisign）/ IP2WHOIS。链接过滤结果为linkfilter-all-results.json.\n为便于理解而举的类比\n\n假设一家持有牌照的出租车公司接到监管机构的通知，称其不得再以其在“主街”的注册地址开展业务。 该公司撤下了“主街”上的招牌，这一撤除行为已被记录在案。 然而，该公司却以另一个名义在“侧街”开设了一个新地址，并继续从那里开展业务。 监管机构运营着一个中央调度系统，来自这两个地址的所有出租车都使用该系统。每次叫车请求都显示“从侧街上车”。 监管机构从未吊销过侧街的经营许可证。 拆除“主街”路牌是当时采取的唯一执法行动。该出租车公司从未停止运营。\n\nA部分——技术记录 · 第3.1节\n在 Steam 中，Valve 的列表是唯一的列表。\n\n在 Steam 客户端、游戏内叠加层或“大画面”模式中点击的链接不会在用户的浏览器中打开。该链接会在 Steam 自身的嵌入式浏览器中渲染——而该浏览器中并不存在普通浏览器会显示的警告层。“链接过滤器”并非多种安全措施中的一种，而是安全措施的全部。\n\n在普通浏览器中三个独立层\nGoogle 安全浏览针对被列入谷歌钓鱼网站和恶意软件列表的主机的全屏插页广告，该列表会持续更新，且与正在访问的网站无关。\n防病毒浏览器扩展程序大多数面向消费者的终端产品都会随附一个浏览器插件，该插件会将目标网站与供应商自己的信誉列表进行比对。\n端点 HTTPS 检查当该产品执行 TLS 检查时，页面内容会在到达用户之前被扫描。\n在 Steam 客户端中，覆盖层和 Big Picture一层\nGoogle 安全浏览不存在。该检查需要 Google API 密钥，而嵌入式 Chromium 构建中并未配置这些密钥；在缺少这些密钥的情况下，Chromium 自身的设计文档中明确指出，“安全浏览”处理程序根本不会被添加到请求链中。\n防病毒浏览器扩展程序不存在。Steam的渲染器并非用户的浏览器，也不会从用户的浏览器配置文件中加载任何扩展程序，因此没有附加组件会在该页面上运行。\n端点 HTTPS 检查这取决于具体产品。流量终止于一个经过代码签名的 Valve 进程内部，而非已识别的浏览器，而且许多终端产品会豁免已签名的应用程序接受 TLS 检查。\nSteam 链接过滤器Valve的自有黑名单，当链接离开Steam生态系统时会进行查询。这是唯一会执行的检查——上表记录了该检查针对本节中所述的认证主机所返回的结果。\n这是一个任何读者都可以进行的测试，如果测试失败，该结论便不成立\n\n打开谷歌发布的“安全浏览”测试网址之一（testsafebrowsing.appspot.com) 在 Chrome 中：会出现一个全屏的红色插页广告。从 Steam 聊天消息中打开同一 URL，使其在 Steam 客户端或覆盖层中渲染：则不会出现插页广告。 Steam 唯一可能生成的警告是其自身的“链接过滤”页面，且仅针对 Valve 列表中的主机。\n\nValve的漏洞赏金记录这一层之前就曾被突破过——就在Valve自己的专辑中\n\n如果“链接过滤器”是客户端内部运行的唯一检查机制，那么其自身的故障模式就绝非次要问题。关于 Valve 的 HackerOne 项目，有两份报告均已被采纳、已解决，且内容均已完整披露：\n\n#291750已归档 2025-11-16 ↗Open Redirect · Medium\n链路过滤保护旁路\n\n2017年11月19日报告，已解决，2018年5月9日披露。该报告中的概念验证：用表意符号句号代替。 (%E3%80%82) 用于主机名中的点 ——可以绕过该封锁。 本节所涉及的插播内容并未出现。\n\n#1079561已归档 2026-09-24 ↗信息披露 · 高\nBig Picture 网页浏览器泄露登录 Cookie 并暴露敏感信息（可能导致账户被劫持）\n\n2021年1月15日报告，已解决，2021年9月21日披露。Valve的严重性评级为“高”，标题中已说明其后果。 已披露的记录包含标题、评级和日期；技术说明未包含在已发布的有效载荷中，因此此处不再引用其中内容。\n\n这是作者的解读，并非两份报告中的任何一项结论： 这两者分列同一道门两侧。其一是目的地打开前未出现的警告；其二是页面在其中打开后，会话便从客户端消失。会话被盗后的一系列事件——密钥在未提示的情况下被注册、真实交易被取消、重复交易被发送至克隆账户——正是《》中所述的模式：第5节 到第8节. 这两份报告均已关闭；均未作为活跃漏洞公开。它们所证实的范围虽较窄，但已足够：根据Valve自身的记录，唯一剩余的安全层确实存在被绕过的既往记录。\n\n来源：HackerOne 平台中每份报告的披露记录，检索于 2026-09-22 — 包含 HackerOne 发布的报告编号、标题、团队、漏洞、严重程度、报告日期、披露日期及状态等信息。检索记录：hackerone-reports.json. 此处未提及悬赏金额；在检索到的已公开记录中也未见相关记载。\n\n实地观察 · PhishDestroy通常会终止一次攻击活动的检测，却未能终止这些活动\n\n我们观察到，这些网络钓鱼主机在承载流量的同时，仍在持续获取流量，检测到20个或更多供应商. 通过网页或电子邮件发送的此类攻击活动，在该状态下会在几天内失效——浏览器和杀毒软件都会根据这些判定采取行动。而在 Steam 内部，两者均不会采取行动。这些判定一直存在。客户端从未对此提出过任何请求。\n\n这对安装了杀毒软件的未成年人意味着什么\n\n他不会忽视任何警告，也不会禁用任何功能。 一条消息发送到了 Steam 内——一把免费的刀，对朋友队伍的一票——页面随即在 Steam 内打开。他从未打开过浏览器，因此浏览器也从未保护过他。他的杀毒软件正在运行，可能已经将该域名判定为恶意；但系统从未征询过它的意见。所有本可以阻止他的警告都已经存在了。但他对这些警告置若罔闻。 他认为自己从未离开过Steam，而事实确实如此。\n\n这种“免费赠送”的噱头并非网络钓鱼者首创——免费Valve商品正是皮肤和赌博网站的宣传手段，这也正是该消息看起来如此寻常的原因。投诉：执法档案. 年龄和儿童的相关数据：第17条.\n\n来源：Steam 通过 Chromium 嵌入式框架在steamwebhelper 过程 — 参见DARKNAVY 2024年6月27日的技术分析 ↗ 以及 Valve 自己的Steam 客户端 Beta 论坛 ↗ 已归档 2025-08-04 ↗. 未依赖任何 CEF 版本：嵌入式 Chromium 并非 Chrome，且未随附 Chrome 的任何 Google 服务。无需 API 密钥即可使用“安全浏览”功能：Chromium 设计文档 ↗ 已归档 2026-08-21 ↗,Chromium API 密钥 ↗ 已归档 2026-08-30 ↗ （“Chrome 使用的许多 Google API 均为 Google 专有，不适用于衍生产品”），而在其他未添加密钥的构建版本中也产生了同样的效果——自酿酒桶 #193814 ↗. 测试网址：testsafebrowsing.appspot.com ↗.\n\n两只不同的钟\n域名的注册时间。观测日期。\n\n注册日期确定了域名的注册时间。带有日期的 OpenID 记录确定了该记录中的返回主机。前者无法填补后者之前的年份。\n\n完整的注册表区分了独立的可注册域名、网站自身的子域名以及直接路径。每一行都链接至其来源及 DNS 的结果。\n\n查看域名注册信息 →· 下载注册日期 ↗· 重现该观测结果 ↗\n\nA部分——技术记录 · 第4节\n一个端点已关闭。公共追踪丢失了一把密钥。\n上下文与来源限制\n\nSteam 发布的更新移除了商品资产 ID 的公开可见性，并限制了 API 对库存数据的访问。其结果是：无法再通过原始资产 ID 从公开数据中追踪特定商品。 下文将说明此前可实现的功能、此后不再可能实现的功能，以及这对试图证明其财产去向的受害者造成的代价。根据 CSFloat 的工程账户记录，时间为 2017 年；目前尚未找到 Valve 的变更日志。 这一时间线——大致发生在2016年7月赌博声明发布一年后——是调查中的待解问题，而非最终结论。物品记录本身仍保存在Valve的系统中；外部调查人员已无法访问原始ID链，而浮点、种子和绘图标识符仅能实现部分匹配。\n\n适用规则 Valve： Steam 客服无法恢复已从您的账户中移出的项目，且您有责任证明事情的经过。记录： 2017年，Valve关闭了携带原始物品ID的接口。在此之前，任何人都可以追踪被盗皮肤从受害者账户流向交易平台机器人。此后，Valve以外的任何人都不再能做到这一点。要求受害者出示的证明，正是那份被调包的证明。 ——而它至今仍存在于 Valve 之中。\n\n停电前时代\n\n从历史上看，在 Steam 上生成的每个虚拟物品都拥有一个全局唯一且不可变的资产 ID. 第三方OSINT数据库可以对这些ID进行索引。如果用户的某项资产被劫持，调查人员可以追踪该特定资产的流向，包括其从劫持者的中间账户转移到交易平台或赌博网站的存储账户的过程。\n\n此前：任何人都可以利用公开数据，从受害者的账户开始，经由中间账户，追踪某件物品的流向，直至其进入交易平台或赌场的存储机器人。\n变更后\n\n根据 CSFloat 的工程账号，Valve 于 2017 年关闭了该端点，外部用户也无法再获取原始项目 ID。 目前尚未发现任何关于此次变更原因的Valve声明。同期，也未发现针对大规模转移物品的商业机器人账户采取任何公开处罚措施。\n\n无论原因如何，这一变动都切断了公开的证据链。 受害者再也无法根据公开数据还原原始ID链，从而证明某件被盗物品是通过某个特定的交易平台或赌场被变卖的。这些物品记录虽然仍然存在于Valve的系统中，但公众、研究人员以及依靠公开数据开展工作的执法部门却无法获取这些信息。\n\n之后：无法再通过公共数据根据原始资产ID追溯特定项目。对于2017年后转移的项目，其原始ID的溯源链仅存在于Valve的基础设施内部；此类记录从未公开发布。 浮点数、种子和绘图标识符仅支持部分的、概率性的匹配。\nIEconItems_730\nGET/IEconItems_730/GetPlayerItems/v1/\n可追踪有效载荷（补丁前）\n\"id\": \"14892281934\",\n\"original_id\": \"11829910211\",\n状态：受害者可以追踪该物品在各个机器人账户间的流转情况。\n混淆后的有效载荷（补丁后）\n当前\n\"id\": \"HIDDEN_BY_PRIVACY_SETTINGS\",\n\"original_id\": \"NULL\",\n状态：外部方无法再通过公共数据中的原始资产 ID 追踪项目的来源。\n对证据的影响： 变更后，用于根据原始资产 ID 追踪某件特定物品从受害者账户流向交易平台或赌场机器人的公开数据已不再可用。 内部记录仍保存在 Valve；但受害者、研究人员或调查人员若仅基于公开数据，则无法还原原始 ID 链（浮点数、种子和绘图标识符仅允许部分匹配）。\n\n来源：CSFloat工程团队关于2017年关闭事件的报告IEconItems_730/GetPlayerItems —blog.csfloat.com/how-floatdb-tracks-items (已归档 2026-09-21) · 所示的有效载荷仅用于说明字段的结构，并非捕获到的响应 · 尚未找到该闭包的 Valve 变更日志。\n\nA部分——技术记录 · 第5节\n一个会话。比用户所见的访问权限更多。\n上下文与来源限制\n\nValve在2023年变更前的API密钥架构偏离了行业基准标准 （OWASP ASVS、NIST SP 800-63B），且该机制在证据档案中保存的自动化库存盗窃投诉中有所描述（第6–8节）。\n\n应用了规则 Valve： 账户持有人创建了密钥，接受了条款，并承担损失——这就是存档的拒绝理由中的答复。记录： 直到2023年12月，仅凭一个被盗的会话Cookie就能注册该密钥。无需密码。无需Steam Guard。账户持有人也不会收到任何通知。该用户并未创建该密钥，也无法查看该密钥，却被告知是他创建的。 移动端确认功能于2023-12-04年添加——这距离2016年的声明大约七年，距离该档案馆保存的诈骗讨论帖大约六年。这几年的费用并非由Valve支付，而是由期间被清空的账户支付的，其中一部分是儿童的账户。\n\nOWASP ASVS 2.8 / NIST SP 800-63B严重程度：严重\n1. 增强型身份验证不足\n\nSteam 允许仅使用会话 Cookie 生成具有高权限且有效期很长的 API 密钥。 在设置或修改开发者 API 密钥时，无需进行双因素认证（Steam Guard）或增强型身份验证挑战，因此 Steam Guard 移动端确认——这是 Steam 提供的唯一第二验证因素——未能保护此步骤的安全。 （2016 年在 Valve 的内部问题跟踪系统中曾提出过添加硬件第二验证因素的要求，该问题至今仍未解决：附录 D，GH-01。）\n\n状态：2023年前未修复。允许持有被盗Cookie的脚本在无需任何用户交互的情况下注册密钥。\nOWASP A01:2021 / 最小权限原则严重程度：严重\n2. 未遵循最小权限原则\n\nSteam Web API 缺乏任何基于角色的授权范围。为“只读”库存状态签发的开发者 API 密钥却拥有完整的“写入”权限——包括操作现有交易、发起新交易、注册 webhook 以及拒绝有效的待处理交易的能力。\n\n状态：系统性设计缺陷。一个密钥即可完全控制该账户的库存和交易读写权限。\nOWASP A07:2021 / 会议环节严重程度：高\n3. 会话管理故障\n\n有用户报告称，源自服务器托管IP范围的被劫持Web会话会持续存在。标准做法是在检测到地理位置异常或密码更改时终止会话；但存档中收集的用户报告显示，有些会话在密码更改后仍然保持活跃状态。\n\n状态：已报告的问题（存档中的用户投诉）。会话可在无需重新认证的情况下生成 API 密钥。\n从技术上讲，域名级屏蔽是可行的执法可行性\n4. 从技术上讲，对认证主机的域级封锁是可行的\n\nValve 已经运行着一个域名列表（即“链接过滤器”），并且已经通过其自身的 OpenID 请求接收到了每一个认证主机名。 从外部来看，这两种机制之间没有任何关联：截至 2026-09-22，有 26 对组合中，主域名被列入了过滤器，而承载其登录信息的代理域名却未被列入。\n\n将它们连接起来是一项简单的工程任务：读取openid.realm 从每个传入请求中提取主机名，将其与列表进行比对，然后拒绝该请求或对其进行标记。右侧的示意图展示了此类例程的结构。拒绝经过身份验证的主机（而非仅拒绝公共登录页面）将中断这些平台所依赖的“使用 Steam 登录”步骤。\n\n没有公开证据表明Valve会进行此类核查。Steam社区市场的总手续费约为15%，仅适用于在该市场内完成的交易；这些平台上的外部交易不收取该费用。\n\nblock_auth_hosts.py插图\n// 读取主机 Steam 已接收的数据 — 不进行扫描\ndef on_openid_request(request):\nhost = parse_openid_realm(request)\n如果 主机在 被屏蔽的域名：\n拒绝（请求）\n注： 该伪代码仅用于说明。两部分在 Valve 处均已存在——请求中包含认证主机名，而域名列表即为链接过滤器。目前尚无公开记录解释二者为何未建立关联。\n第 5.1 节 — 这些标准并非未公开发布\nValve 每天都会根据这些规则进行编译。但这次它并未按照这些规则进行编译。\n\nSteam 在 App Store 和 Google Play 上架应用，通过主要信用卡支付处理商进行销售，并像其他大型平台一样使用第三方 API。每项合作关系都附带一份已公布且注明日期安全要求，Valve 必须满足这些要求才能继续运营。 将这些要求所对应的日期与 Steam 自身 Web API 获得同等安全保护的日期进行对比。下文中的内容均非私有标准、内部备忘录或商业秘密：每一行都是带有发布日期的公开文件。\n\n已发布的外部安全要求及其日期，与Steam Web API 获得等效控制措施的日期相对应\n已发布的标准及其生效日期\t关于同一问题的 Steam Web API\n范围限定授权OAuth 2.0 — RFC 6749，2012年10月. 第3.3节定义了scope 因此，客户端只会获得其请求的访问权限。此后，这一直是所有主流平台 API 的默认设置。\t细粒度作用域于2026年1月16日.在此之前，无论该 Web API 密钥是出于何种原因签发的，单个 Steam Web API 密钥都拥有对该账户交易记录的完全读写权限。十三年零三个月 在定义该控件的规范之后。\n密钥不等于授权谷歌官方的云服务文档：标准 API 密钥无法对主体进行身份验证，以及对于用于创建或管理资源的 API，请勿在生产环境中使用授权密钥。\t那个 Steam Web API 密钥正是如此。一个发放给某个账户的持有人字符串，仅凭该字符串即可读取库存、取消待处理交易并发送新交易。在使用时未对任何委托人进行身份验证。\n特权访问中的多因素身份验证PCI DSS 3.2，要求 8.3 — 自...起强制执行2018年2月1日 针对所有非控制台管理操作以及对持卡人数据环境的所有远程访问。随后，苹果公司要求所有开发者计划账户持有人必须进行双因素认证，自2019年2月27日:在开发者计划中拥有“账户持有人”角色的开发者，需要启用双因素认证才能登录。\t还需要第二个因素才能从……生成 API 密钥2023年12月4日.在此之前，仅需一个被盗的会话Cookie就足够了，账户持有人的手机上既不会弹出提示，事后也不会收到任何通知。四年零九个月 在苹果公司要求用户仅为登录开发者门户就必须使用第二重身份验证之后。\n凭证生命周期与撤销Twitch 对所有第三方应用程序的要求如下：您的应用必须在启动时以及此后每小时验证一次 OAuth 令牌，并声明会对不符合要求的应用程序进行审核。其旧版 v5 API 已于2022年2月28日 按照已公布的时刻表。\t未发布密钥生命周期记录。2023年的变更保护了创建端点。 该变更中未包含任何针对已注册密钥的Valve声明，且完全未附带变更日志。根据公开数据无法确定此前创建的密钥是否已失效——而这正是数据主体需要了解的问题，以便确认其账户上数年前创建的密钥是否仍然有效。\n建筑基准 // 代币建筑学\nGitHub 细粒度作用域与 Valve Steam Web API 的对比\n\nValve 开发者每天都在 GitHub 上使用精细化的“最小权限”令牌来管理开源软件。试想一下，这与发放给 1.3 亿 Steam 玩家的那把“单体密钥”相比，有何不同。\n\nGitHub 细粒度令牌\n在 GitHub 上被 Valve 使用\n\n具有作用域隔离和强制生命周期管理的细粒度令牌。\n\n代码库访问：仅限选定仓库（1 个仓库）\n授予权限：只读 [✓]\n代码与秘密：无访问权限 [✕]\n有效期：30天（强制TTL）\n审计日志：IP、用户代理和时间戳\n安全状况： 最低权限令牌可将损害限制在单个只读资源范围内。\n!Valve Steam Web API 密钥\n已向1.3亿用户发放\n\n一条由32个字符组成的主字符串，包含“全有或全无”的交易和库存授权。\n\n账户访问：完整账户（整体式）\n交易管理：已读、取消、拒绝 [!]\n粒度范围：无（2026年抵达，晚了13年）\n有效期：绝不（永久有效）\n审计日志：无（该用户无IP记录）\n漏洞： 被盗密钥可悄无声息地拦截所有发出的交易要约。\n单向适用的标准\n\n假设某供应商 Valve 所依赖的云服务提供商、支付处理商或内容分发网络（CDN）未对凭证端点启用双因素认证，数月后，Valve 的企业数据便通过该端点生成的密钥泄露了。 Valve会承认责任在于点击链接的那个人吗？本档案中保存的驳回记录回答了用户面临的镜像问题：其立场是，账户持有人创建了密钥，因此应承担损失。同一架构被描述为：从一个角度看是供应商的失职，从另一个角度看则是用户的责任。 这究竟属于哪种情况，并非一个技术性问题，也不是本次调查能够裁定的——这应由法院或监管机构来裁决。\n\n仅为示例，并非证据——标准被反向解读\n一家支付处理商允许第三方脚本仅凭浏览器Cookie就生成具有完全权限的交易凭证，且未向账户持有人发出任何提示。\n某身份提供商封堵了其代币所通过的漏洞，却未就已铸造的代币发布任何信息。\n某银行在处理一笔有争议的转账时，指出所使用的凭证是在客户本人账户上注册的，随后便结案了。\n\n以上内容均不构成针对任何特定公司的调查结论。这些只是相同的决策，只是被转移到了监管反应有详细记录的情境中——而这正是监管机构被要求进行的比较。\n\n案卷所载事实如下： Steam Web API 中缺失的控制措施是公开的、过时的，而且在某些情况下，Valve 必须满足这些条件才能继续发货。每项标准与其等效的 Steam 变更之间的时间间隔是可以量化的，并在上文中进行了说明。但这并未说明原因。 尚未找到关于这些时间段中任何一个的理由说明，本文中也未作任何假设；该记录存在于Valve中，尚未公开发布。\n\n来源（均为公开文档）：OAuth 2.0 —RFC 6749，2012年10月 ↗ · Google Cloud —API 密钥文档 ↗ · PCI DSS 3.2 第 8.3 条要求 —PCI SSC 资源指南 ↗ · 苹果 —即将对账户持有人实施的双因素认证要求，2019年2月20日 ↗ 已归档 2025-05-06 ↗ · Twitch —令牌验证要求 ↗ 以及v5 停用通知 ↗ 已归档 2025-01-27 ↗. Steam 所列日期即本节更新记录中的日期；2023 年和 2026 年的条目是 Valve 在未附带变更日志的情况下发布的版本。检索于 2026-09-22。\n\nValve的更新记录——日期已知，来源为公开渠道\n日期\tValve 更改\t已经宣布了吗？\t它关闭了什么\t延迟：机制公开 → 已修复\t来源\n2026-09-01\t可疑聊天自动标记\t是的\t群聊中的危险链接/模式\t—\t新闻 ↗\n2026-01-16\tSteamworks Web API 的细粒度作用域\t是的\t开发者密钥的最低权限范围\t—\t公告 ↗\n2025-07-15\tCS2 交易保护与撤单窗口\t是的\t没什么。 这并非针对根本原因的安全修复。支持团队的账户恢复权限保持不变。触发撤销操作将自动导致30天的交易锁定（Skinvault ↗)，而现货交易冲击导致24小时内市值暴跌$104M（-25%）（CSMarketCap ↗). 2026年，计时器改为按项目计算（Skin.land ↗).\t—\t常见问题解答 ↗\n2025-05-14\t账户安全公告\t是的\tStealer / 会话劫持指南\t—\t公告 ↗\n2024-10-02\tCS2《军械库》7天保留期\t是的\t暂停军械库物品的交易/市场\t—\t公告 ↗\n2024-09-18\t新设备登录的交易限制\t是的\t新设备需锁定2–7天方可交易\t—\t常见问题解答 ↗\n2024-02-14\t个人资料名称和头像更改暂缓\t是的\t重命名后，交易需等待2–4小时才能再次进行\t—\t帖子 ↗\n2023-12-04\tAPI密钥的移动端验证\t无更新日志\t仅使用Cookie的静默密钥注册\t距离2017年左右的专题讨论会约6年后\t开发者页面 ↗\n2023-10-24\t游戏构建版本发布中的短信多因素认证（MFA）\t是的\tSteamworks 构建发布\t—\t公告 ↗\n2023-07-12\t自定义个人简介内容提示\t是的\t个人简介中的网络钓鱼链接\t—\t论坛 ↗\n2023-01-25\t个人资料 {链接已删除} 及冷却时间\t是的\t个人资料文本中的链接\t—\t常见问题解答 ↗\n2022-10-24\t登录功能全面升级与Cookie截断\t无更新日志\t无限次被盗会话\t—（IAuthenticationService 令牌迁移）\t新闻 ↗\n2022-10-12\t移动应用 3.0 QR 码登录\t是的\t会话撤销面板\t—\t新闻 ↗\n2022-05-10\t已移除交易取消的终点\t无更新日志\t报价交换（取消并重新发送）\t距离2017年左右的面板问世约5年后\t第325期 ↗\n2020-05-25\tDota 2 7天交易锁定\t是的\t快速倒卖商品\t—\t博客 ↗\n2018-03-29\tCS:GO 7天交易锁定\t是的\t即时机器人洗钱\t自2016年7月的声明发布以来约20个月后\t博客 ↗ 已归档 2025-02-26 ↗\n来源：链接中的 Valve 条帖子、帮助页面和 GitHub 问题，具体日期见各条目。 有三项关键修复在未发布变更日志的情况下推送（2022年5月、2022年10月、2023年12月），且是由用户发现而非由 Valve 公告的——这种不对称性是执行记录的一部分。 延迟仅在档案本身的日期信息（2016年7月的声明；2017年左右的诈骗讨论版）提供了起始点时才进行计算；“—”表示此处未确立此类起始点。\nA部分——技术记录 · 第6节\n交互式漏洞利用与劫持模拟器\n上下文与来源限制\n\n对从钓鱼消息到服务器端密钥注册及交易交换的流程进行重构。在2023年之前，注册在账户上的Web API密钥可以读取其库存、取消待处理的交易要约并创建新的交易要约，且对于上述任何操作，系统均不会向账户持有人显示交易确认界面。 这属于“未遵循最小权限原则”（OWASP A01:2021）。本模拟中的时间数据仅供说明，并非当前平台的实时测量数据。\n\n逐步浏览这起重构的劫持事件。每个阶段都展示了账户持有人所看到的内容，以及与之相对应的、Steam在同一时刻收到的来电。这些呼叫每一通都经过了正确的身份验证。 该流程中的任何环节都不需要依赖 Steam 的身份验证才会失败——关键在于它签发的密钥不包含任何作用域（OWASP A01:2021）。\n\n玩家所见。幕后发生的变化。流程演示模拟器\n步骤 5 / 5\n\n漏洞利用已完成。 受害者本以为会收到关于原始交易的手机提示，却误将替代交易予以批准。这是一份综合取证演示，展示了由于缺乏“最小权限原则”（OWASP A01:2021），如何导致资产在不到一秒的时间内被自动劫持。\n\n01 / 聊天诱饵一位朋友请我投票受害者收到一条带有链接的消息。\n02 / 登录一个“长得像”门户网站受害者输入登录凭据。\n03 / 访问Silent Web API 的创建攻击者注册了一个开发者密钥。\n04 / 转换合法贸易被替换“克隆机器人”会复制目标收件人。\n05 / 确认假冒产品已获批准在手机端误批准了错误的报价。\n从网络角度看同一步骤2023年前走势的重建 · 示意性行情走势\n受害者批准了针对原始交易预期的移动端提示。\n攻击者在克隆账户中接收这些物品。\nSteam 次浏览由账户持有人在已注册设备上确认的转账。\nConfirmation genuine — made by the account holder\nRecipient the clone bot, not the intended counterparty\nThe confirmation is authentic. The offer it confirms is not the one the user initiated.\n\n留下的记录： 用户已批准的一笔交易。这就是Steam支持团队在收到投诉时查阅的记录，以及已归档投诉被归类为“用户操作失误”并关闭的原因。这些投诉位于执法档案.\n\nA部分——技术记录 · 第7节\n该序列背后的端点。简体中文（大陆）\n上下文与来源限制\n\n以下是报告中提到的劫持脚本用于拦截交易（无需经过浏览器端的确认步骤）的 Steam 个 Web API 端点。\n\n四个已记录的终点就足以完成全部工作。其中没有任何一个存在漏洞，也不需要利用漏洞——只要用有效的密钥调用它们，就会得到“Steam”的响应。密钥是攻击者唯一需要窃取的东西。\n\nIEconService / GetTradeOffers / v1投票\n\n用于监控该账户的交易要约。脚本会使用被盗的 API 密钥反复轮询此端点；该端点会返回新创建、待处理或已修改的交易要约的详细信息。此处未测量轮询间隔。\n\n威胁载体： 显示待处理的交易要约 ID 以及收件人的个人资料详情。\nIEconService / CancelTradeOffer / v1交互\n\n用于通过程序方式使用户的合法交易要约失效。在2023年之前，该密钥未受任何增强型身份验证的保护，因此一旦被检测到，自动化服务器即可立即取消该要约，且不会向账户持有人发出任何提示。\n\n威胁途径： 在账户持有人完成手机确认之前，该交易将被撤销。\nISteamUser / GetPlayerSummaries / v2RECON\n\n查询以获取合法交易接收方的个人资料名称、头像图片网址和等级。这使得脚本能够将预先准备好的克隆账户包装成与之匹配的样式。此处未测量耗时。\n\n威胁载体： 提供冒充目标收件人所需的数据。\n/dev/ajaxregisterkey创世\n\nSteam的密钥注册端点。过去，任何活跃的浏览器 Cookie 会话（`steamLoginSecure`）都可以在移动设备上注册密钥，而无需 Steam Guard 的确认，也不会向账户持有人发送任何通知。\n\n威胁载体： 由脚本创建的持久性凭据，账户持有人无法察觉。\nA部分——技术记录 · 第8节 · 《通用数据保护条例》（GDPR）第7条\n一个被勾选的复选框。是谁操作的？\n上下文与来源限制\n\n在拒绝报销时，Steam 存档中保留的支持回复认为，账户持有人创建了 API 密钥，并且通过勾选复选框，即表示接受了相关条款。\n\n该支持响应将密钥归属于账户持有人。问题在于，该记录能否证明是谁实际创建了该密钥。\n\n然而，在已观察到的API密钥劫持模式中，受害者从未看到过API密钥创建页面，也从未访问过该页面。同意字段是由一个脚本通过使用被盗的会话Cookie执行无头POST请求而提交的。\n\n根据《通用数据保护条例》（GDPR）第7条和第4条第(11)款，同意必须是数据主体自愿、具体、知情且明确表达的意愿。 作者认为，由恶意脚本利用被盗Cookie提交的“接受条款”复选框——且未向账户持有人显示任何页面——不符合上述定义。是否符合该定义，应由监管机构裁定。\n\n取证有效载荷分析：密钥注册\nPOST https://steamcommunity.com/dev/ajaxregisterkey\n// 请求负载（通过劫持脚本注入）\n{\n\"agreeToTerms\":“同意”,<-- 由机器自动生成，未经人工干预\n\"domain\":\"localhost\",← 未验证 — 接受任何值，包括 localhost\n\"sessionid\":\"8f0d8ef763ab2140bf89de2a\"\n}\n向监管机构提出的问题： 在账户持有人从未点击过同意选项的情况下，该账户记录的条款接受情况是否符合第7条关于“数据主体意愿应以自愿、具体、知情且明确的方式表示”的要求，以及Steam客服部门能否据此拒绝理赔请求。\n\n来源：根据公共端点以及证据档案中保存的劫持报告重建的密钥注册格式（可搜索的 2026-09-17 版本) · 显示的会话标识符是一个占位符，并非捕获到的值。\n\n法医解剖 · 贸易替代向量\nValve是如何最终消除“贸易替代”现象的——以及为何花了7年时间才通过各种变通措施实现\n\n近十年来，该“API密钥替换”（或称API中间人诈骗） 这是在 Steam 上最赚钱的账号盗取模式，从毫无防备的玩家手中窃取了数亿美元的皮肤。 Valve并未通过修复存在漏洞的API架构来根除这一漏洞；相反，Valve花了七年时间，在全平台范围内叠加了四道摩擦壁垒，这些壁垒严重削弱了社区交易的流动性，却始终未能解决根本原因。\n\n1. 《拟态之死》\n头像与昵称刷新时间（2024年2月）\n\n该漏洞利用需要在不到一秒的时间内完成伪装：诈骗机器人拦截了一笔外发交易，并通过ISteamUser，并在200毫秒内克隆了该个人资料。2024年2月14日，Valve悄然实施了一项强制性2至4小时的交易冷却时间（错误34） 在更改个人资料名称或头像后立即生效。机器人将无法再在不锁定自身交易权限的情况下，即时克隆收件人。\n\n2. 经济之死\n7天CS2交易反转（2025年7月）\n\nValve 引入单边交易反转 用于《反恐精英》中的物品。任何交易的皮肤都会被标记为“交易受保护”状态，持续七天。 如果受害者发现物品被调包，只需在 Steam 客服中心点击“撤销交易”，该皮肤将立即返还至其库存，同时冻结收件人账号。由于7天的交易锁定机制能阻止诈骗者将物品转移至套现网站，因此此类盗窃行为将无法获利。\n\n3. 《沉默之钥之死》\nAPI 强制实施移动推送功能（2023年12月）\n\n从历史上看，被盗的会话 Cookie 曾允许恶意脚本执行无头后台 POST 请求至/dev/ajaxregisterkey 且未通知受害者。2023年12月4日，Valve 要求在 Steam 移动应用中生成 Web API 密钥时必须获得明确的推送确认，从而杜绝了无提示的后台密钥配置。\n\n4. 应用内移动端提示\n账户使用时长与名称横幅（2022–2024）\n\nValve 对移动端确认弹窗进行了改版，以显示交易伙伴的Steam 账户使用期限（创建日期）, Steam 级别，以及一条明确的琥珀色预警：“该用户最近更改了其个人资料名称”，从而打破了那些细心的受害者所产生的视觉错觉。\n\nValve“拼凑方案”中的三大缺陷：为何诈骗者只是转移了目标\n1. 游戏排除漏洞（《Dota 2》和《TF2》）\n\n“交易逆转”功能专为《反恐精英2》设计。《Dota 2》和《军团要塞 2》中的道具仍然完全没有保护措施 这是由于制作和镶嵌过程的复杂性所致。价值数千美元的高阶物品（如“龙爪钩”、“金色小罗尚”、“非同寻常的TF2燃烧之焰”）均不设撤销期限。 诈骗者只是将自动API拦截转向了《Dota 2》和《TF2》的交易者，而Steam客服团队则严格执行其2016年制定的“不恢复物品”政策。\n\n2. “僵尸密钥”储备池（无过期期限）\n\n虽然 Valve 添加了基于移动端推送的通知的双因素认证来生成新 2023年12月交付钥匙，Valve 从未撤销、过期或清除现有的旧版 API 密钥. 数百万个曾生成密钥（或在 2023 年 12 月之前被网络钓鱼/恶意软件在用户不知情的情况下创建了密钥）的活跃账户，其凭据仍然处于有效状态，且包含零过期时间（无 TTL）和零空闲超时. 威胁行为者维护着这些持久密钥的庞大历史数据库，并持续进行轮询IEconService 未受干扰。\n\n3. 受害者惩罚：30天交易封禁\n\n即使在 CS2 中，Valve 也会对被骗的玩家施加惩罚：在 Steam 支持界面中点击“撤销交易”会自动造成对受害者账户实施为期30天的强制性交易及社区市场禁令. Valve 会对用户处以一个月平台禁言的处罚，以此遏制“无端”撤销交易的行为，并阻止受害者对低价值、高流动性的商品撤销交易。\n\n核心监管丑闻：七年的变通之举与一个API范围\n\n为什么Valve花了七年时间发明交易锁定、账户冷却期和可逆交易锁定——从而扰乱了整个游戏经济，并导致市值蒸发$104M——而不是采用业界标准的解决方案？\n\n正如 Valve 于 2026 年 1 月 16 日在 Steamworks 上的官方发布所证明的那样（公告#493839547938902179 ↗), Valve 已建成细粒度权限组（常规、微交易、经济、销售数据） 以及IP 白名单 用于企业版发布密钥。Valve 多年来一直掌握着相应的工程解决方案。一个面向用户的复选框——“禁止此 Web API 密钥访问 IEconService（交易管理）” 或者一个家庭IP白名单——本可以在2018年彻底根除“交易替代”诈骗，且不会造成任何经济附带损害。Valve却拒绝为普通玩家提供其为企业合作伙伴量身定制的保护措施。\n\nB部分——规则与执法记录 · 第9节\n他们的规则手册。记录在案的平台。\n上下文与来源限制\n\n该分类账将来自Steam 订阅协议（SSA） 以及Steam 网络行为（SOC） 直接针对活跃的大规模商业实体的指导方针。\n\n规则： 禁止商业用途、禁止赌博、禁止使用机器人——而Steam客服在拒绝归还受害者物品时，会援引这些条款。记录： 从字面上看，这些条款涵盖了本登记册中的商业平台，这些平台基于Steam个身份、Steam个机器人和Steam笔转账运行。该条款针对的是丢失皮张的人，而非运输皮张的企业——这一点在任何公开记录中均未提及。\n\n在存档的投诉中，Steam 支持部门援引了“禁止商业用途” 以及“禁止使用自动化工具/机器人” 在拒绝向API密钥欺诈受害者恢复资产时所援引的条款。从字面意义上看，这些条款同样适用于本案卷中记录的商业平台——这些平台通过Steam OpenID进行身份验证，并通过自动化Steam账户转移资产。 本文未估算全行业的收入总额（参见下文的执法统计数据）。现有记录仅显示了归档案件中针对单个账户适用的规则，而各平台并未公布按运营商分类的执法记录。本节旨在记录这种不对称现象。\n\n核心问题／选择性执法规则 → 规模 → 问责制\n一套规则。执行不一。\n\n该登记册显示，某些商业服务将Steam身份、库存、机器人和转账作为运营基础设施。SSA禁止未经许可的商业利用和自动化操作。存档的投诉显示该规则适用于个人账户，而公开记录中并未显示针对本文所载平台的、按运营商分类的相应账户信息。 请针对每一项分别公布相关规则、证据及执法决定。\n\n189审计范围内的网站\n44“活动注册表”中的独立域名路径——其中27条附有已发布的证据文件，17条为手动收集。仅通过对189个网站的浏览器审计就解决了其中的25条；该注册表还补充了手动收集的路径。\n12岁零6个月csgogem.com 在“链接过滤器”中被屏蔽；api.csgem.com 已注册 2014-03-08 且从未被封禁——截至 2026-09-22，共有 26 对此类账号\n无经核实的总数未包含全市场收入预测\nSteam 网络行为\n“……您不得在 Steam 上进行或试图进行以下任何行为：[…] 从事商业活动。此类被禁止行为的示例包括：发布广告；举办竞赛；赌博; 买卖 Steam 账号；出售内容、礼品卡或其他物品；以及乞讨。\"\n\nstore.steampowered.com/online_conduct ↗ 已归档 2026-09-21 ↗\n\n《SSA》第2.G条——商业用途\n“……[您不得]将内容和服务或其任何部分用于任何商业目的，但本协议其他条款明确允许的情况除外……”\n\n据报道，Valve在2016年的通知中援引了个人、非商业用途许可。据记录显示，尚无任何运营商出示过Valve授权。store.steampowered.com/subscriber_agreement ↗ 已归档 2026-09-18 ↗\n\nSteam Web API 使用条款\n“您不得以任何违反Steam《订阅协议》的方式使用Steam Web API 或 Steam 数据。”\n\n第三方皮肤交易平台通过调用Steam API的自动化账户进行运营。规则文本中未对商业规模作出任何例外规定。steamcommunity.com/dev/apiterms ↗ 已归档 2026-09-21 ↗\n\n《社会保障法》第4.C条\n自动化\n\n脚本、机器人及非人类交互均受限制。该账本会记录商业规模的机器人交易、账户农场和自动化路由行为。\n\n检查153标记为该条款的记录↗\n本条款下记录的内容153 已标记的平台\n案件立案15\nSkin Casino13\nCS2 市场9\n皮肤轮盘8\ncsgoempire.com→csgoempirelogin4.com赌场\nrollbit.com→rbsnin.com加密货币赌场\n500.casino→fivezerozero.co持牌赌场\n\n其中， 153 还被归类于《社会保障法》第2.G条，以及 2 还被归类于《社会保障法》第1.C条——同一项服务可能属于多个条款，因此 示例会重复出现。\n\n28 观察到153的 通过一个单独的可注册域名进行身份验证。标签记录了一项带日期的 观察结果，这使该平台从表面上看符合该条款的规定；这并非 经裁定的违规行为，且尚未针对其中任何一个提供Valve授权证明。\n\n《社会保障法》第2.G条\n商业用途\n\n商业利用须经明确许可。请对比已记录的商业模式、其规模以及任何已披露的授权或执行情况。\n\n检查175标记为该条款的记录↗\n本条款下记录的内容175 已标记的平台\n案件立案15\nSkin Casino13\nCS2 市场9\n皮肤轮盘8\ncsgoempire.com→csgoempirelogin4.com赌场\nrollbit.com→rbsnin.com加密货币赌场\n500.casino→fivezerozero.co持牌赌场\n\n其中， 153 还被归类于《社会保障法》第4.C条，以及 24 还被归类于《社会保障法》第1.C条——同一项服务可能属于多个条款，因此 示例会重复出现。\n\n28 观察到175的 通过一个单独的可注册域名进行身份验证。标签记录了一项带日期的 观察结果，这使该平台从表面上看符合该条款的规定；这并非 经裁定的违规行为，且尚未针对其中任何一个提供Valve授权。\n\n《社会保障法》第3.A条\nVPN 与位置伪装\n\n通过IP代理隐藏真实IP地址可能会导致服务终止。对于独立域名的认证主机，需要单独分析：确定被隐藏的内容以及应适用哪条规则。\n\n检查认证主机凭据↗\nSteam 帮助 / URL 政策\n链接混淆\n\nSteam 禁止使用链接缩短服务以及会隐藏链接目标的工具。一个独立的授权域名——rbsnin.com 在 Rollbit 的登录流程中，auth.dota.trade 在 CS.MONEY 中——这引发了一个类似的问题：显示给 Steam 的 OpenID 验证器的目标地址是否能标识出实际运行的网站。\n\nValve的 URL 政策 ↗\n\n规则参考：Steam 用户协议，2026年9月10日修订版 已归档 2026-09-18 ↗ ·Steam Web API 使用条款 已归档 2026-09-21 ↗ ·Steam URL 策略（链接混淆）. 统计数据描述了本档案中的记录和标签；它们并非已裁定的违规行为的统计数量。\n\n信任赤字\n当支持团队关闭工单时，由谁来审核该决定？\n\n这些保留下来的投诉记录描述了永久性制裁、未获回应的申诉以及拒绝归还被盗物品的情况。请将这些陈述与实际的票务记录、可用的补救措施以及账户访问日志进行核对。仅凭“钓鱼攻击”这一笼统的解释，无法确定是谁发起了账户重置或创建了API密钥。\n\n阅读已记录的投诉 ↗申请相关记录 →版主关系图 →\nB部分——规则与执法记录 · 第10条\n一个自动化 API。一条禁止自动化的规则。\n上下文与来源限制\n\n本节提出的问题是，如何协调这两者之间的关系：哪些API使用行为是被授权的，由谁授权，以及依据哪些已公布的标准。本文未对授权的商业API用户数量进行估算，且未公布名单这一事实本身也不暗示存在任何具体数字——该名单的缺失即为调查结果，而非背后隐藏的具体数字。 上文引用的Steam条支持信息由ArchiSteamFarm项目在其自身的常见问题解答（FAQ）中转载（经核实与原文完全一致2026-09-22）；这些信息并非Valve出版物，且未披露接收这些信息的账户信息。\n\n该规定（《社会保障法》第4.C节）： Steam 上不允许使用脚本、机器人或非人类系统。记录： Valve 提供了一个无头 REST API，其唯一目的是实现服务器间自动化，并向任何账户提供访问密钥。用户因使用自动化工具而被封禁；该自动化接口是 Valve 的自有产品。 哪些商业用途是被允许的，这一点从未公布过。\n\n“游戏开发者”谬论\nSteamworks SDK（正版）\n\n由正规游戏工作室用于将成就、匹配和排行榜功能集成到其游戏客户端中。需要进行复杂的 C++ 集成，并需完成官方合作伙伴的入驻流程。\n\nSteam Web API（漏洞）\n\n一种专为外部Web服务器设计的无头部JSON/REST架构。在本文档中记载的“劫持”模式中，该架构被用于从远程服务器读取库存信息并操控点对点交易；其合法用途未在本档案中列举。\n\n这把钥匙是给谁的普通 Steam 用户在客户端无需使用 Web API 密钥；该密钥页面位于开发者网址下，其文档中记载的用途是用于外部服务器端的访问。存档的账户劫持投诉显示，受害者直到自己的账户上被注册了密钥后，才得知该页面的存在。\n自动化悖论\n\n《社会保障法》第4.C条规定：“您不得以任何形式使用脚本、机器人、宏或其他非人工控制的系统（以下简称‘自动化工具’）以任何方式与 Steam 上的内容和服务进行交互。” 然而，Web API 的端点（例如CancelTradeOffer) 无需人工操作界面，也无需验证码，并完全绕过 Steam 客户端。该 API 专为服务器间自动化设计；相关规则禁止用户进行自动化操作；两者之间的界限并未公开。\n\n贸易流程中的服务器端角色\n\nWeb API 密钥允许第三方服务器在无需 Steam 客户端的情况下，对该账户的交易进行操作。在“劫持”模式下，该服务器位于账户持有人与交易服务器之间。\n\n→对于该键的操作，系统不会显示交易确认界面。\n→允许后台轮询（GetTradeOffers）。\n→无需用户操作即可取消并重新发布报价。\nValve 构建了该界面，在其规则中禁止用户进行自动化操作，且未公布哪些商业用途被允许的标准。\nB部分——规则与执法记录 · 第11条\n要求十天。却要花十年来交代。\n上下文与来源限制\n\n2016年7月20日，Valve的总法律顾问向博彩运营商设定了10天的最后期限。 十年后（截至本档案快照时间，即 2026-09-21），当时新闻报道中提及的至少一家平台——CSGOFast——仍通过独立域名的认证主机正常运营。下文内容系根据2016年7月21日的新闻报道还原，并非扫描件。 该通知所暗示的执法记录尚未公布。致委员会的公开信是第2节.\n\n请阅读后续意见旁边的2016年7月通知。尚待解决的问题是按运营商分类的执法记录。\n\n一周前——2016年7月13日，在公开场合\n\n关于2016年7月13日 已归档 2026-09-21 ↗, Valve 描述了赌博网站如何利用 Steam：OpenID 进行账户身份验证，并使用自动交易账户进行交易。Valve 指出，利用这些机制经营赌博业务违反了其 API 协议和用户协议。关于该机制的描述和相关禁令均载于Valve本人签署的、注明日期的声明中。 在 2026-09-21，所测试的独立域认证主机未返回任何“链接过滤”阻断记录，而 Valve 也未发布任何针对各运营商的强制执行记录。\n\n附件A / 7月2016排版重建\nVALVE 公司\n\n华盛顿州贝尔维尤市\n\n日期：2016年7月（据媒体2016年7月21日报道）\n发件人：卡尔·夸肯布什，总法律顾问\n回复：停止并终止——禁止将Steam账户用于商业用途\n注：根据已报告的文本进行重建；非扫描件\n\n“我们已获悉，您正在运营下列赌博网站之一。 您正在使用 Steam 个账户开展此项业务。根据 Steam 用户协议，Steam 和 Steam 服务仅限个人、非商业用途。”\n\n“您应立即停止并将不再将您的 Steam 账户用于任何商业目的。如果您未能做到这一点，十（10）天内, Valve 将采取一切可用的补救措施，包括但不限于终止您的账户。\n\n档案重建 · 查阅原始记录\n卡尔·夸肯布什\nValve公司总法律顾问\n边栏 / 社论\n十天。那接下来呢？\n\n截止日期已经明确规定。公众的后续行动也应如此。\n\nValve 发表的关于《2016》的立场声明 ↗\n关于截止日期的说明 +\n讽刺 / 非瓦尔夫通信\n\n亲爱的截止日期，\n\n你被给了十天时间。不知为何，日历是唯一还在正常运转的东西。\n\n请将任何回复转至公共记录中。\n\n时间轴2016年7月 – 2026年9月\n通知中的截止日期：\n10天\n2016年7月\n自通知发布以来已过去：\n3,715 天\n该数据为2016年7月20日至2026年9月21日档案快照期间的固定统计值，并非实时数据\n已公布的执法记录：\n无\n未找到按操作员分类的终止或阻塞记录\n\n◀第0–10天 — 截止日期，按比例缩放第3715天 — 快照 ▶\n\n2016年7月20日发出十天期限通知第0天\n2024年2月17日适用《DSA》规定的义务第 2,768 天\n2026年2月25日纽约州总检察长宣布提起诉讼第 3,507 天\n2026年9月21日档案快照第3715天\n\n十年后，CSGOFast ——在2016年相关通知的新闻报道中被提及——目前正在运行：csgofast.com 在 2026-09-19 和 2026-09-21 上返回了“链接过滤”阻断，而其认证主机steam-login.authtofast.com (注册号 2026-06-30) 没有。\n\nValve的安全设置变更的完整带日期记录：安全时间轴 → · 华盛顿州的判例与执法标准：下面\n\n记录显示： 2016年的通知设定了10天的期限；Valve当时已运营一个域名列表（Link Filter），并在其自身的OpenID请求中接收了授权主机名；目前尚未公布任何按运营商分类的执法记录。 社区报告描述了2018年针对某交易平台（SkinJar）采取的行动，但这些报告未经核实，本文不予采信。\nCSGOFAST / 已保存的认证路径\n遵循声明的返回主机。\n\n已保存的路线记录链接csgofast.com 到steam-login.authtofast.com. 该独立主机名包含在 Steam OpenID 请求中。它为调查人员提供了一个具体的地址，以便与 Valve 的过滤和执行记录进行比对。\n\n查看 CSGOFast 的路径及其来源 ↗ ·比较已保存的 Steam 链接筛选结果 ↗\n\n公共记录 / 华盛顿 · 2016 → 2026\n两个截止日期。一个尚未明确的执法标准。\n7月20日\nValve 给予赌博网站10天时间\n\n其律师在要求中警告称，若继续将Steam账户用于商业用途，可能会导致账户被终止。\n\n9月27日\n华盛顿施压 Valve\n\n该州博彩委员会要求提供已采取措施阻止利用虚拟物品进行赌博的证据，并将答复截止日期定为10月14日。\n\n10月17日\nValve 驳回该指控\n\nValve在截止日期后作出回应，否认其助长赌博行为，称已停用相关账户，并表示不希望为所有用户关闭交易和OpenID功能。 在关于7月通知的新闻报道中被点名的平台中，至少有一家（CSGOFast）在十年后仍在运营。这两个事实只有在运营商替换了被禁用的账户的情况下才成立；而能证明这一点的记录尚未公布。WSGC应要求Valve对此进行说明。\n\n2026\n2026年9月观察到的航线\n\n该路由记录显示，有44个平台通过独立域名的认证主机（包括CSGOFast）进行身份验证，使用了2016年所述的OpenID和交易机制Valve。本应显示哪些运营商被切断服务的执行记录尚未公布。\n\n委员会内部简报 · 2018年1月30日\n在Valve作出回复十八个月后，监管机构仍将其视为一种意图。\n\n在HB 2881号法案的公开听证会上，该委员会向本州立法机构通报情况时，用自己的话描述了2016年7月的声明：Valve“宣布将打击利用其平台进行皮肤赌博的行为。” 该页面还记录了该公告对行业预测产生的影响——“因此，” 2020年虚拟物品赌博市场的预测值从$19.7十亿 到$670百万，仅凭这一公告，降幅就达到了约97%。预测数据已发生变化。而能够证明这一调整合理性的、按运营商统计的执法记录至今仍未公布。\n\n这些市场数据是Narus Advisors / Eilers & Krejcik Gaming的估算值，由委员会简报中转载，并非委员会的调查结果；同一份文件显示，2016年的“皮肤赌博”金额约为$5十亿，其中约$3十亿发生在赌场式网站上。 检索时间 2026-09-22，SHA-256c507c9025f93da0aadaf395c4d8882f25973211c318ee8e9b6f18a5b3755e050.\n\nValve在2016年公开表态的内容与当今可见的基础设施可以进行对照。问题在于，监管措施是否已覆盖被禁运营商所使用的账户和路线。十天的通知期限并不能证明该通知已向其中列明的各运营商送达。 2018年针对OPSkins的行动是迄今为止唯一有记录的针对特定操作员的干预措施；考虑到共检查了189个平台且未公布按操作员分类的记录，仅此一项有记录的行动并不能表明存在执法模式。\n\n华盛顿州博彩委员会2016年公告 ↗ 已归档 2026-05-20 ↗ ·Valve于2016年10月17日的答复（文件副本） ↗ ·WSGC向立法机构作简报，2018年1月30日（本地副本，共4页） ↗ ·wsgc.wa.gov 上的同一份文件 ↗ ·检索记录与哈希值 ↗ ·Valve的 2018 年 OPSkins 动态 ↗ 已归档 2026-03-07 ↗ ·当前路线审核 ↗\n\n法证纵向审计 · 2016年“停止并终止”通知的对象\n“10天通知”十年：对23个指定地点的法证生存审计\n\n2016年7月19日至20日，Valve总法律顾问卡尔·夸肯布什向23家皮肤赌博平台发出了正式的停止并终止通知，责令其停止在Steam账户内的商业用途10天 面临账户终止和法律诉讼的威胁。3,700天后，一项实证审计揭示了执法的真实情况：多家运营商从未停止运营，另一些则在截止日期后仍持续运营长达六年，而这个价值数十亿美元的生态系统继续利用Valve的OpenID架构。\n\n5+ 直播\n预计将于2026年投入运营（CSGOBig、CSGO500、CSGOFast等）\n6年\n关闭前最长的公告发布周期（CSGOatse 运营至 2022 年）\n$5.01B\n2016年“皮肤”投注额（Narus / Eilers & Krejcik）\n200+\n在市场高峰期运营的活跃网络赌博网站\n《幸存的泰坦》· 2024–2026 年财务与流量蓝图\n从10天预警到离岸集团：数十亿美元的资金周转\n\nValve在2016年发布的公告非但没有消除“皮肤赌博”，反而催化了该行业的演变。 幸存的运营商重组为离岸公司实体（库拉索、伯利兹、塞浦路斯），开创了点对点（P2P）交易以规避机器人禁令，目前处理量已超过每月网站访问量达1000万次 以及每年数十亿美元的投注额 同时继续通过 Steam 进行身份验证：\n\n平台 / 域名\t2016年7月通知\t执法结果与存活状况\t记录验证 / 主要链接\nCSGOBig\ncsgobig.com\t10天通知（2016年7月）\t2026年依然健在\n已暂时暂停，现已重新上线；通过 letmeinbig.com 和 csgobiglogin.com 进行身份验证\tX：@csgobig ↗ ·FB：csgobigofficial ↗\nCSGO500\ncsgo500.com / 500.casino\t10天通知（2016年7月）\t2026年依然在世\n更名为 500 Casino（库拉索牌照号 8048/JAZ2014-037），月营业额达数百万\t真人博彩平台 (500.casino) ↗\nCSGOFast\ncsgofast.com\t10天通知（2016年7月）\t2026年依然在世\n通过 steam-login.authtofast.com 积极运营轮盘、Crash 和大奖游戏\t文件授权审核 ↗\nCSGOLounge / Dota2Lounge\ncsgolounge.com / dota2lounge.com\t10天通知（2016年7月）\t2026年依然健在\n业务重心转向电竞代币投注和加密货币博彩；保持持续运营\t直播平台 ↗\nCSGOCasino\ncsgocasino.net / csgocasino.gg\t10天通知（2016年7月）\t《通过继任者直播》（2026）\n该域名已重定向；现由 csgocasino.gg 运营的继任门户网站\t后继域 ↗\nCSGOatse\ncsgoatse.com\t10天通知（2016年7月）\t存续6年（截至2022年仍处于活跃状态）\n在Valve发出10天最后通牒后，赌博活动仍持续了六年\tX：@CSGOatsecom（活跃至2022年）↗\nCSGOSweep\ncsgosweep.com\t10天通知（2016年7月）\t存续至2017年12月\n在截止日期过后仍向公众开放了17个月\tX：2017年12月CSGO横扫战绩 ↗\nCSGOWild\ncsgowild.com\t10天通知（2016年7月）\t存续至2017年12月\n由知名网红推广；在收到停止并终止通知后运营了1.5年，随后转向加密货币领域\tX：@Wild（2017年12月活跃）↗\nCSGOPot\ncsgopot.com\t10天通知（2016年7月）\t存活至2017年9月\n在收到通知后仍继续经营高额累积奖金博彩活动长达14个月\tX：@csgopot（2017年9月活跃）↗\nCSGODiamonds\ncsgodiamonds.com\t10天通知（2016年7月）\t存活至2017年年中\n尽管承认曾为受赞助的主播篡改比赛结果，该赛事仍照常举办至2017年\tX：@csgodiamondscom (2017) ↗\nCSGOLotto\ncsgolotto.com\t10天通知（2016年7月）\t已于2016年7月关闭\n因公众丑闻被迫停业；成为联邦贸易委员会（FTC）同意令的对象\t联邦贸易委员会（FTC）同意令（案号 C-4632）↗\nCSGODouble\ncsgodouble.com\t10天通知（2016年7月）\t已于2016年7月关闭\n在《停止并终止通知》发布后立即自愿停业\tX：@CSGODouble（已关闭，2016年7月）↗\nCSGOMassive\ncsgomassive.com\t10天通知（2016年7月）\t已关闭 2016\n于2016年底停止公开运营\tX：@csgo_massive ↗\nCSGOStrong\ncsgostrong.com\t10天通知（2016年7月）\t已关闭 2016年\n已于2016年停止对外运营\tFB：csgostrongfree ↗\nSkins2\nskins2.com\t10天通知（2016年7月）\t已关闭 2016\n已于2016年停止对外运营\tFB：CSNCOM ↗\n\n平台\t月访问量（访问次数）\t预计营业额/交易量\t公司实体与管辖权\t主要监管举措与模式\nCSGOEmpire\ncsgoempire.com\t230万 — 900万 / 月\n平均时长 6 分钟以上；80% 直接\t$1.5B — $2.5B 年度交易量\n>1,000,000 每月P2P皮肤交易； $6.4M 活跃流动订单量\tMoonrail Limited B.V.（库拉索注册号 #148182）\n付款方：JHOLT LTD（塞浦路斯）；创始人：“Monarch”（奥西·凯托拉）\t开创了零手续费的P2P物品交易；持有库拉索OGL/2024/1183/0869牌照\nCSGORoll\ncsgoroll.com\t274万 — 350万 / 月\n平均时长 9 分 23 秒；16% 跳出率\t$1.0B — $2.0B 年度交易量\n估计每年来自赌场优势的企业收入为 $100M–$200M\tFeral Holdings Limited\n总部位于伯利兹伯利兹城（注册号：171519）\t被澳大利亚ACMA禁赛（2023年5月）；赞助了一支拥有未成年选手的一线战队G2 Esports\n500赌场 (CSGO500)\n500.casino / csgo500.com\t22万 — 42.5万 / 月\n~10.5万月独立访客\t每周 $100k（每年 $5.2M）在罗亚莱斯\n大额投注者的投注要求：每获得 $1 返水，需投注 $400 次\tPerfect Storm B.V.（库拉索岛第150536号）\n库拉索博彩监管委员会许可证 OGL/2024/1354/0882\t因未经许可针对瑞典玩家开展营销活动，被瑞典博彩监管局（Spelinspektionen）禁止运营（2023年11月）\nCSGOBig\ncsgobig.com\t~169,600 / 月\n平均时长 19 分 12 秒；美国初选\t年交易量达数百万\n神秘宝箱、轮盘赌和箱子对战\t通过辅助代理路由进行操作\nletmeinbig.com（注册于2023年）与 csgobiglogin.com\t2016年7月C&D的目标；采用代理授权架构重新发布\nCSGOFast\ncsgofast.com\t约15万—25万/月\n全球多语言受众\t年交易量达数百万\n高速轮盘和崩盘游戏\t离岸运营实体\n路径 Steam 通过 steam-login.authtofast.com 进行身份验证\t2016年7月收到“停止并终止”通知的对象；从未停止运营；2026年仍处于运营状态\nCSGO Polygon\ncsgopolygon.com / plg.bet\t约30万—50万/月\n独联体和东欧的 dominance\t年交易量达数百万\n加密货币与皮肤轮盘、比赛投注\t第二波目标（2016年10月）\n通过镜像域名 plg.bet 转向加密货币领域\t已存活整整十年；继续通过第三方API进行皮肤清算\n“第二波”：为何Valve的停止并终止通知共针对43个以上网站\n\n2016年10月17日，Valve的法律顾问正式向华盛顿州博彩委员会披露，继7月19日发出的首批23份通知之后，Valve已向另外还有20多个皮肤赌博网站 （使官方总数超过43个）。之所以要发布这份第二批名单，是因为最初的名单中莫名其妙地遗漏了世界上最大、最臭名昭著的赌博中心：\n\nCSGOJackpot.com： “皮肤大奖”这一概念的开创者，在因面临联邦起诉威胁而停业前，其交易额曾高达数亿。\nCSGOShuffle.com： 该网站是2016年7月直播丑闻的核心，Twitch主播PhantomL0rd曾秘密持有该公司33%的股份，并被曝光利用公司资金操纵赔率。\n宏观生态系统（200多家运营商）： 根据Narus Advisors和Eilers & Krejcik Gaming的行业研究，2016年共有超过200家独立的“皮肤”赌博网站运营，从303万名活跃玩家那里产生了$5.01十亿的投注额。 Valve的43封信所涉及的范围不到20%的活跃市场份额。\n关于Steam皮肤赌博的官方政府及监管调查\n\n“皮肤赌博”现象已在多项正式的法定调查、执法行动和政府立场文件中得到记录：\n\n1. 华盛顿州博彩委员会（WSGC）（2016–2018）\n\n于2016年10月5日发出正式的“停止并终止”要求；于2018年1月30日发布《立法简报》，其中明确指出“皮肤”属于现金等价物，并报告了$5.0B的“皮肤”投注额。\n\nWSGC 立法报告 PDF（本地副本）↗\n2. 美国联邦贸易委员会（FTC）（2017年9月，案卷号C-4632）\n\n这是首例针对CSGOLotto所有者特雷弗·马丁（Trevor Martin）和托马斯·卡塞尔（Thomas Cassell）涉及“皮肤赌博”的联邦监管执法行动，理由是他们存在欺骗性行为及未披露平台控制权。\n\n联邦贸易委员会（FTC）的裁决与同意令 ↗\n3. 英国赌博委员会（UKGC）立场文件及青少年审计报告\n\n根据《2005年赌博法》，游戏内皮肤被正式归类为“金钱或具有金钱价值的物品”。后续调查发现，超过11%的11至16岁儿童曾用游戏皮肤进行赌博。\n\nUKGC 研究资料库 ↗\n4. 澳大利亚参议院环境与通信调查（2018年）\n\n联邦议会关于……的报告“游戏内针对随机获取道具的微交易”，评估Valve的开箱机制、二级市场套现以及规避监管的行为。\n\n澳大利亚议会调查 ↗\n未结需求\n\n公布执法记录：哪些赌博账户和机器人已被停用，哪些返回主机已被限制，以及哪些商业服务获得了许可。仅发布公开禁令和在主页上发布警告，并不能证明相关运营活动已被停止。\n\nB部分——规则与执法记录 · 第12条\n主机名已经包含在请求中了。\n上下文与来源限制\n\nValve 已经维护了一份域名列表（即“链接过滤器”），并且在每个 OpenID 请求中都会接收认证主机名。下面的伪代码展示了将这两者连接起来的逻辑结构。目前没有公开证据表明 Valve 会这样做。\n\nValve 已经运行了一个域名黑名单。 Valve 在每个 OpenID 请求中都会收到登录主机。无需建造任何东西——只需将两者连接起来即可。 这是针对 Valve 自行维护的列表进行的主机名查询。下面的伪代码仅用于说明，并非 Valve 的实现。\n\nforensic_autoban.py\n# 示例伪代码 — Valve.block_domain() 和 flag_session_as_mitm() 并非真实的 API 调用。 此处演示的是缓解措施 Valve 针对代理认证域可能实现的逻辑结构，而非 Valve 的实际内部实现。\n# 示例：对传入的 OpenID 请求进行验证的逻辑流程\ndef audit_openid_request(请求)：\nblocked_origins = database.get_blacklisted_platforms()\nproxy_domain = request.params.获取('openid.realm')\ntarget_redirect = request.params.获取('openid.return_to')\n\n# 逻辑：如果代理将请求路由回被封锁的网站，则封禁该代理。\n用于 网站在 blocked_origins:\n如果 网站在 target_redirect:\nValve.block_domain(proxy_domain)\nValve.flag_session_as_mitm(request.session)\n# 结果： 拒绝了该主机的登录请求\n\n观察：\n如果某个主域名已列入链接过滤器（例如 howl.gg，被屏蔽的 2026-09-18/19/21) 且其认证主机（howl.uno）出现在该网站登录按钮发出的 OpenID 请求中时，Valve 可通过其自身的请求数据观察到该关联关系。该检查可自动化进行；但是否执行该检查则无法确定。\n有据可查且已报告的先例\n\nValve 据记录显示，曾至少一次对第三方运营商采取干预措施：2018年，它撤销了OPSkins通过ExpressTrade系统访问的权限（Valve的公告 ↗ 已归档 2026-03-07 ↗). 2018年的社区报告还提到一个交易平台（SkinJar）失去了访问权限；这些报告尚未得到证实，其背后的机制是根据结果推断出来的，而非基于已披露的流程。\n\n该判例确立了以下原则：\n\nValve 可在其决定时切断第三方运营商的访问权限。CSGOFast（在2016年7月通知的相关媒体报道中被提及）当时在 2026-09-21 上运行，其注册的授权主机为 2026-06-30，该主机未触发 Link Filter 阻断。 为何某家运营商被切断而其他运营商未受影响，目前尚无任何公开的标准予以解释。\n\n注册日期能反映什么、不能反映什么\n\n授权主机的注册日期是该主机首次出现在 OpenID 请求中的时间下限；这并不意味着该主机一直被持续使用。sc-auth.net例如，该域名注册于2019-04-02（RDAP），并于2026年9月在Skin.Club的Steam登录流程中被发现；在这两个日期之间发生了什么，公开记录中并未提及。\n\n比较审计：API合规标准\n执法层面\tGitHub API 规则\tSteam Web API (Valve)\n1. 合规中立性\t已发布的统一规则。记录在案的调用限制（例如，经过身份验证的用户为 5,000 次/小时，GitHub Enterprise Cloud 组织为 15,000 次/小时）以及已发布的《可接受使用政策》适用于每个账户。\t未公布具体标准。单个账户依据自动化条款和商业用途条款（已归档的投诉）被终止，但尚未公布针对商业平台的按运营商分类的执法记录。\n2. OpenID / 身份验证代理滥用\tGitHub 公布的政策允许因滥用行为而暂停或撤销 OAuth 应用和令牌，其文档中还描述了已暴露令牌的自动撤销机制（作者对 GitHub 文档的总结）。\t在 Steam 个 OpenID 流程中观察到的独立域认证主机（例如 rbsnin.com、howl.uno、sc-auth.net）在 2026-09-21 上未触发“链接过滤”拦截，而其主域则触发了拦截。\n3. 滥用的商业化\t对于通过第三方自动化工具转手的商品，GitHub 不收取任何交易费；其收入模式来自订阅服务和市场商品上架。\tValve 销售可产出这些物品的宝箱钥匙，而社区市场对在市场内完成的交易收取总计约 15% 的费用。此处未估算归因于第三方平台的收入。\n4. 规避循环的寿命\t被暂停的 OAuth 客户端 ID 在暂停时即会在整个平台上停止工作；相关文档未公布具体处理时限，本文中也未作任何假设。\t在对 2026-09-19 和 2026-09-21 的检查中，注册日期介于 2011 年至 2026 年 9 月之间的独立域名认证主机未返回任何“链接过滤器”阻塞记录。注册日期是可能使用情况的下限，而非连续使用的证明。\n来源：GitHub 专栏——GitHub 发布的 API 速率限制和平台政策文档（作者总结，未引用原文）· Steam 专栏——对 2026-09-19 和 2026-09-21 的链接过滤检查（linkfilter-recheck-2026-09-21.json)，RDAP注册库（domain-registration.json) 以及存档的支持投诉 (证据档案).\nB部分——规则与执法记录 · 第13条\n0以外的价格缺口\n\n该物品存放在 Steam 库存中；交易在其他地方进行。一把工厂新品 AWP Dragon Lore 曾CSFloat 上有 62 条实时报价; 报价最低的$10,623.95. Steam的市场本身无法显示高于约$1,800的要价。若要以观察到的更高价格出售，所有者需要找到Steam以外的买家或交易平台。该物品及其转让仍取决于Steam。\n\nWhat this means — the Community Market listing ceiling\n\nSteam’s own market refuses a listing above roughly $1,800. A seller may ask less, never more. Items whose market price sits above that line therefore cannot be sold at that price on Steam at all — which is the mechanism that moves those sales to third-party venues while the item itself never leaves Valve’s inventory system.\n\nSection 13 — the off-Steam price gap →\n\n上下文与来源限制\n\n本节中出现了三种不同的计数方式，它们不能互换使用。245 指在2026年9月20日，仅在CSFloat平台上，其最便宜的有效报价超过$1,800的CS2商品名称类别数量。241 即该集合减去固定在CSFloat的$100,000上限处的四个类别，而$13.63M下限正是基于该面板计算得出的。248 这是一组不同的数据快照：2026年9月23日，在五个交易平台中，有两个或两个以上平台的报价超过了价格上限的类别。由于这些交易平台存在重叠，因此绝不能将不同交易平台的统计数据相加。 此处的所有数据均为要价，而非成交价，且均不代表收入、营业额或利润——无论是对于 Valve 还是其他任何人。 PriceEmpire 列出的数值是该网站发布的四舍五入后的估计值，且其 Steam 卡片涵盖了其他 Steam 游戏的商品，因此各项比较的范围并不完全一致。\n\n一种商品，两种定价体系。关注《记录报》\n步骤 3 / 3\n\n根据这一要求，卖家需要一个Steam以外的交易场所或买家。该商品仍需依赖Steam的库存和转账系统。\n\nSTEAM关于 $1,800已发布的社区市场挂牌上限\n已保存的目录$10,623.95全新AWP Dragon Lore 地板版，价面议\n《依赖》仍为 Steam 项库存和转移仍为 Steam\n01 / 商品Valve 游戏库存CS2 或 Dota 2 道具位于 Steam\n02 / 天花板关于 $1,800 于 Steam单个市场列表的最高价格\n03 / 外部咨询$10,623.95 用于《龙之秘闻》该日期快照中价格最低的 CSFloat 报价\n04 / 交付Steam 仍保留在链中所有权和物品转移取决于该系统\n市场架构 · 过时快照，20 9月 2026\n价格差距是可以量化的。\n\n我们统计了那些最便宜的有效报价严格高于1,800.的商品名称类别：CSFloat 和 Skinport 是两个独立的快照，其CS2库存存在重叠；因此无法将它们的计数相加。外部报价显示了更高要价的发布情况，而Steam仍负责管理商品的所有权和转让。\n\n245CS2 分类 · CSFLOAT\n166CS2 分类 · SKINPORT\n3DOTA 2 分类 · SKINPORT\n$10,623.95《龙之传说》楼层提问\n\n《龙之秘闻》：62 显示，CSFloat 在“全新”类别下有相关商品；所显示的价格为要价，并非已确认成交价。Steam 允许以更低价格发布商品，但不得发布观察到的更高要价。Valve 在 2016 声明中确认，其已知悉赌博运营商正在使用 OpenID 及 Steam 的交易基础设施。特定第三方市场是否违反了 Valve 的规则，需另行核实。\n\n查看完整登记簿 →CSFloat JSON ↗Skinport JSON ↗Valve关于2016的声明 ↗\nDIRECT CSFLOAT API / 带日期的快照$13.63M\n\n最低总要价为241 个商品类别 以及3,395 有效优惠. 计算方法为：每个类别的最低卖出价 × 其报价数量。四个被固定在 CSFloat 的 $100,000 上限的类别被排除在此保守型面板之外。\n\n这一数字反映了什么\n\n这些报价至少代表$13,631,888.25 该限量版 CSFloat 子集的已发布要价。将四个最高价类别纳入计算后，结果为$14,231,888.25. 这是一个活跃询价的最低价，而不是已完成的销售额、现金周转额、利润或整个CS2市场。\n\n从包含 245 行数据的 CSFloat 快照重新计算 ↗\nPRICEEMPIRE / 标价Steam：第 15 条（共 39 条）\n许多场地的标价都高于 Steam。\nUUSkins\n$133.8M\nYouPin898\n$127.5M\nBuff.163\n$104M\nMoon.Market\n$100.3M\nWhite.Market\n$89.6M\nBuff.Market\n$86.7M\nSteam\n$31M\n\n显示的六个最大值以及 Steam。PriceEmpire 对这些数字进行了四舍五入；Steam 显示$31M. 根据显示的美元金额，有14个上榜场馆的排名高于它。\n\nPRICEEMPIRE / 优惠数量Steam：第 1 条，共 39 条\nSteam 在报价数量上仍居首位。\nSteam\n32.2M\nYouPin898\n5.9M\nC5Game\n4.6M\nHaloSkins\n4.4M\nSkinport\n3.8M\n\nSteam 显示32.2M 报价。报价数量和总要价分别反映了不同的情况；许多低价房源可能会占据报价数量的大部分。\n\n来源：PriceEmpire 的公开比价 ↗ 已归档 2026-09-21 ↗, 捕获于 2026-09-20 19:03 UTC；39行提取 ↗. 这些数据均为四舍五入后的估计值，且不同地点的库存可能存在重叠。Steam的卡片中还列出了其他Steam游戏中的物品，因此范围并不完全一致。所列数值代表要价，而非销售额或收入。\n42\n另一消息来源 / STEAMANALYST\n商业生态系统显而易见。\n\nSteamAnalyst 的市集目录 已归档 2026-07-19 ↗ 该列表列出了42家第三方CS2交易平台以及Steam，其中43个条目中有32个提供了最新价格数据。PriceEmpire根据其自身的收录标准列出了39家交易平台。明确的企业名称、公开的报价、可见的价格：这一经济体系是透明的，可供查验。\n\n上限即机制：促销活动会结束，但该商品不会下架。\n\n在一张经授权的快照中，涵盖了五个市场，248个CS2商品类别中，有两个或两个以上的价格均独立高于Steam约$1,800的上架价格上限——而且这些商品无一例外均未在Steam上架. 同一份快照按价格对整个商品目录进行了分组：Valve的市场中，低于其上限的商品类别占95.3%，高于其上限的占1.9%。这种缩减并非源于需求下降；它完全符合已公布的规则。 以这些价格销售需要外部买家或交易平台，而 Steam 仍控制着库存和转移——交易离开 Valve 的结账环节，配送则仍依托 Valve 的基础设施。\n\nSteam 市场常见问题 ↗已归档 2026-09-21 ↗Steam 订阅协议 ↗已归档 2026-09-21 ↗五个市场图集数据集 ↗来源清单 ↗之前的 CSFloat 快照 ↗Skinport 快照 ↗PriceEmpire ↗已归档 2026-09-21 ↗SteamAnalyst ↗已归档 2026-07-19 ↗价格差异登记簿 ↗价格梯度图集 ↗\n\nC部分——法律框架\nC部分——法律框架 · 第14节 · 人员准入\n谁可以重置安全保护措施？\n上下文与来源限制\n\n账户安全还取决于那些能够恢复账户、查阅私人记录或重置账户安全措施的人员。调查工作必须像追查 API 滥用行为一样，对这些特权操作进行密切追踪。\n\n账户恢复功能赋予了客服人员将账户从其所有者手中移交出去的权限。Valve 已两次以书面形式确认——分别于2023年2月和2025年11月——该权限曾被用于将账户移交给错误的人员。 相隔三十三个月，通过同一渠道。下文将阐述：这种访问权限的价值何在，六起经核实的案例，以及日志Valve对每起案例的记录——这些记录至今未向任何人公开。\n\n保存的证词 / 2025年5月9日\n一张导致该账户安全功能失效的恢复凭证，以及一笔报告的 $10,000 损失\n\n在收集到的支持档案中，有位用户报告称，在另一人提交了恢复请求后，Steam 支持团队重置了密码并禁用了账户保护功能。 该用户称，该账户已多年未使用，存有2016–2017年的物品，且Steam Guard，已绑定手机号码并存储了恢复码。\n\n\"Steam 客服还是让别人获得了我的账户访问权限。\"\n\n第一人称指控，保存在steam_support_tickets_MEGA.json, 第110号记录。阅读完整的截图帖子 ↗\n\n这并非某位用户的倒霉遭遇。同样的“后门”——即通过提交帮助请求，将账户转移给提供更早数据的一方——是下文账本中所有案例的官方记录途径，而Valve已两次以书面形式明确指出这一点。\n\n业主在这场争论中是赢不了的。 恢复流程会要求提供第一个CD密钥、第一个电子邮箱、第一张卡片、第一个电话号码。这些信息都存储在Valve的数据库中，技术支持团队可以调取这些数据——据称可追溯至十五年前。任何拥有你文件副本的人，总能调出比你自己更多的历史记录。 目标的筛选标准是：账户已闲置多年、价值高，且通常是二手购买的，因此持有者根本不知道原始密钥。事后，这些账户会被彻底删除，从而切断了社区用于追踪皮肤的物品历史记录——普通用户在未经过标准等待期的情况下无法执行此类删除操作。\n\n最小权限原则 / OWASP A01\n\n恢复权限应仅限于相关任务，并需经过独立审查和记录。应审计哪些人员有权重置凭据、删除 Steam Guard、查阅账单记录或导出账户数据。OWASP 访问控制指南 ↗ 已归档 2026-09-20 ↗\n\n广泛的访问支持访问范围风险\n超越库存。\n\n如果广泛的支持访问权限被滥用，私有遥测数据可能会成为用于用户画像、定向网络钓鱼和监控的工具。潜在受害者包括普通用户、军事人员、公众人物及其家属。这是一种威胁模型；具体权限需要参考访问控制记录。\n\n01 IP地址历史记录与位置\nIP日志可以揭示网络活动记录和大致位置。但仅凭IP日志本身，无法确定精确的物理移动轨迹。\n02 设备指纹识别\n如果收集了设备标识符且可以访问，则可将会话与账户关联起来。\n03 活动遥测\n登录时间戳和会话记录可以揭示用户的日常习惯，包括那些在公开个人资料中无法看到的活动。\n04 通讯与联系方式\n如果能够访问保留的消息或联系信息，将扩大进行用户画像和社交工程攻击的可能性。\n05 身份揭露\n原始的电子邮件、电话和支付记录可以将一个化名账户与某个人联系起来。\n06 数据转售与问责\n导出的目标名单可能会助长针对性诈骗。需查明行为主体、访问地点、收件人和资金转移情况；仅凭地点本身既不能证明存在访问行为，也不能构成法律豁免。\n\nValve在其文件中描述了IP日志记录、设备信息、支付记录以及第三方支持提供商。《隐私政策》第3条、第5.2条 已归档 2026-09-21 ↗. 该政策授权第三方支持访问——但尚未披露能够显示哪家承包商在何时、依据何种授权访问了哪一类信息的审计日志。\n\n第14.1节 · 《登记册》 · 2022年6月 → 2025年11月 · 所有图表均注明出处\nValve 两次推开了那扇门，相隔三十三个月。门从未关上过。\n\n共有六起报告案例，其中账户信息是通过Steam的自有求助渠道，或通过该渠道保护的凭证被盗取的。每笔金额均为引用的来源所公布的数额，且每个来源均已注明名称。这六起案例中有两起已获得全额赔偿。 这些案例与其他案例的区别不在于事件本身——而在于谁在关注。\n\nValve，书面形式 — 2023年2月“相关物品已被从您的账号中移除，因为这些物品是从一个因支持请求而遭到入侵的账号处收到的，CS:GO团队对此负责。我们已撤销相关交易，并将这些物品从所有收到它们的账号中移除。”Steam 支持向HFB商品的收件人回复，转载自Dexerto，2023年2月21日 ↗ 已归档 2025-08-18 ↗\nValve，再次提笔——2025年11月 · 33个月后“一位处理该求助请求的技术支持人员未按我们的流程操作，导致您的账户被恢复给了其他人。对此错误，我深表歉意。”Steam 支持对 Hawkeye337 的回复，引用如下：Dexerto，2025年11月14日 ↗\n2022年6月21日\nHFB——游戏内最大的库存$2,000,000+· 在2023年2月的后续评估中上调至$3,000,000+\n\n七把纪念版AWP“龙之传说”以及排名第一的蓝宝石卡兰比特刀，仅这把刀的价值就约为$1.26百万. 该账户已停用三年，但手机验证器仍处于激活状态；尽管如此，还是通过客服恢复渠道更改了邮箱和密码。\n\n钱比东西先花光了。 据报道$200,000+ 销售款项的一部分已通过 market.csgo.com 提取——这是一个支持现金和加密货币结算的交易平台。撤销交易会返还皮肤，但不会返还用户已存入账户的现金。\n\n结果这个修复方案反而搞砸了。 一位买家将他的“纪念品：龙之传说”移入了游戏内的储物箱。Valve的回滚脚本无法查看该容器内部，因此它向所有者发放了一份新的副本，并保留了隐藏的那份——Valve复制了一份$130,000 该物品是在试图撤销一起盗窃行为时被发现的。通过比对物品ID和社区举报，该物品被查获，并于一个月后（2022年7月）被删除。 买家的退款由BUFF而非Valve支付。如此脆弱的应急补救措施并非管控手段；这只是平台在失去控制时所采取的行动。\n\nDexerto，2022年6月21日 ↗ 已归档 2022-07-02 ↗ ·卡巴斯基 ↗ · 每笔提现金额Esportfire，2022年6月22日 ↗ 已归档 2026-05-15 ↗，据称来自推特上的多个消息来源 · 根据……进行复制和删除Esportsbetting，2022年7月14日 ↗\n\n已修复交易被撤销。那些曾以全价购买商品的人，其库存中的商品被收回。\n2022年8月14日\nCS.Money —— 该平台自有的机器人$6,300,000· 19,000+ 皮肤 · 初步估算 $1.6M\n\n攻击者窃取了该交易平台交易机器人的移动验证器文件并清空了其中的内容，随后将部分赃款转给知名交易员以混淆视听。社区研究人员梳理了短短几小时内查获55个攻击者账户 并将它们发表了。\n\nValve并未推翻这一决定。给出的理由是，该第三方网站位于Steam之外——而正是该Steam，其库存、交易API和账户系统被盗用贯穿了整个过程。\n\nEsportfire，2022年8月14日 ↗ 已归档 2025-11-15 ↗\n\n被拒绝没有逆转。损失由该平台及其用户承担。\n已报告\n2023年2月21日\nQkss——同一扇门，同一位演员$1,000,000+\n\n据报告，此问题与HFB问题以相同方式提交，由同一位演员通过相同的客服请求提出。HFB问题已在八个月前得到完全解决，而Qkss问题则未得到解决。\n\n一条路。两个答案。 在已公布的记录中，除了听众规模之外，这两起案件没有任何区别。\n\nDexerto，2023年2月21日 ↗ 已归档 2025-08-18 ↗\n\n被拒绝未修复。\n已报告\n2023年2月\n内幕交易本身——持续了一年之久≈ $320,000· 持续时间约为一年，并非存货估值\n\n技术支持团队查阅到了截至15岁 ——第一个CD密钥、第一封电子邮件、第一张卡片。这正是恢复流程所要求的证据，这也是为什么在与账户持有人的争执中，数据库持有者总是占上风。\n\n博主 Mzkshow 揭露了内幕操纵者“Steam Help”及其同谋“Alexander”如何将目标锁定在持有超过 $100k 皮肤的休眠账号上。一把被盗的 M4A4 Howl，其上贴有 iBUYPOWER 和 Titan Katowice 2014 全息贴纸，最终以$35,000 最终，此事落到了NAVI队的瓦列里·“b1t”·瓦霍夫斯基身上，而他对此一无所知。在Valve介入后，该承包商解雇了其整个Steam客服团队。\n\nVKPlay ↗ ·Lis-Skins ↗ ·Escorenews（俄语）↗ ·Dexerto（英文）↗\n\n无寄存器Valve从未公布过此事涉及多少个账户，也未告知受影响的人。\n已报告\n2024年12月2日\n《马特维》——解雇事件之后$13,000\n\n某人提供了连账户所有者本人都无法核对的账户数据，结果获得了账户恢复。在承包商撤走其Steam客服团队两年后，通过同样的途径又得到了同样的结果。\n\n存档帖子，2024年12月2日 ↗ 已归档 2025-08-05 ↗ ·源行和哈希 ↓\n\n被拒绝未修复。\n2025年11月13日\nHawkeye337（马克·斯普洛克）——以及第二次坦白≈ $300,000–$500,000· 2014年卡托维兹全套全息系列\n\n袭击者要求1 比特币 并开始将该数据集刮取到Negevs上以将其销毁。Steam 支持部门的书面回复即为上述第二项承认：一名技术人员处理了该求助请求，未按流程操作，并将该账户转交给了其他人。\n\n导致这一修复的原因是数据源。 在X平台上发布标记Valve的帖子数小时后，该账号被取回，所有贴纸均已恢复。Qkss并没有那么多的受众。\n\nSkin.club ↗ ·Dexerto ↗ ·Esportfire ↗ 已归档 2025-12-17 ↗\n\n已恢复该报道登上热搜后数小时内，相关内容就被撤下。\n账簿所显示的，是任何单个案例都无法体现的。Simplified Chinese (Mainland)\n\n这条路线从未关闭过。 第一次入院日期是2023年2月，第二次是2025年11月——相差三十三个月，期间发生了承包商的大规模解雇、一起有记录的复发事件，以及一起造成$6.3百万损失的平台安全漏洞。从该账本中记录的首起盗窃事件算起，该渠道保持开放状态长达三年零五个月. 无论2023年修复了什么问题，2025年11月该求助请求仍将一个账户分配给了错误的人——这是Valve自己写的一句话。\n\n赔偿关注的是关注度，而非损害。 已恢复：游戏内最大的库存，以及其帖子曾登上热搜的收藏家。已拒绝：$1,000,000, $6,300,000, $13,000。Valve从未公布其适用的规则，因为一旦公布规则，就必须对那三条进行解释。\n\n没人被告知。 既不是那些账户记录被从数据库中读取的用户，也不是监管机构，更不是那些善意购买了相关商品却被迫退还的买家。既没有数据泄露通知，也没有事件报告，更没有受影响账户的统计数据——以及以现金形式留存的收益，通过以现金和加密货币结算的交易平台。资金一旦流出Steam，就无法进行交易逆转。\n\nValve 保存了支持审计日志、恢复工单日志以及上述每一行的交易记录。这些记录均未生成。索取您的副本 →\n\n关于《国防授权法》的问题\n保密性必须伴随着技术上的问责制。\n\n将保密协议与实际权限、出口管制、重置审批及访问日志进行对比。对于“恢复流程本身遭到滥用”这一指控，套用现成的回应是无法解决的。\n\n《通用数据保护条例》（GDPR）第28条、第32–34条\n\n第33条规定，数据控制者须在72小时内向监管机构报告个人数据泄露事件；第34条要求，当受影响人员面临高风险时，必须向其通报。 Valve已两次以书面形式确认，其支持渠道将账户信息——包括账户历史、账单记录等全部内容——交给了错误的人员。尚未发布根据上述任何一条规定发出的通知，也没有受影响的用户报告称已收到此类通知。 阅读相关规定 ↗ 已归档 2026-09-20 ↗\n\n在您的请求中包含支持访问权限 →\nC部分——法律框架 · 第15节 · 商业规模\n追踪资金流向。将交易分拆。\n上下文与来源限制\n\n当资金流被分离时，关于商业用途的问题就变得更加尖锐。第三方物品转让、Valve的主要销售以及外部提现是不同的交易。\n\n该商品属于 Valve。库存为 Valve。转移在 Valve 的服务器上进行。只是付款是在别处进行的 ——这一步骤决定了某人是否属于汇款机构，而Valve公司并未执行这一步骤。\n\n收入机制\n资金实际流动的地方。\n三条路线／单件物品的经济体系\n01 / 账户用户库存\n\n已保留的物品：Steam\n\n02 / 转账P2P交易\n\n用户 ↔ 机器人 或 用户 ↔ 用户\n\n03 / 结算外部平台\n\n现场结余或结清 Steam\n\n发行量经济引擎的作用远不止于转会费\n\nSteam 提供外部市场所使用的库存和转账基础设施。调查中的经济论点是：转售流动性和持续需求支撑着对箱子、钥匙及替换物品的消费，并由此产生后续社区市场销售的佣金。 直接的点对点（P2P）转让不收取社区市场佣金；这一会计事实并不能决定其更广泛的效益。Valve在整个过程中始终保留对账户访问权限和交易限制的控制权。\n\n01 / 二次需求流动性与转售价值\n\n对外贸易和赌博需求\n\n02 / 主要支出钥匙、钥匙套和药囊\n\n如有提供，可从Valve处购买简体中文（大陆）\n\n03 / 收入首次销售收入\n\n此外，还需支付实际市场销售额的相关费用\n\n5% + 10%Steam + 社区市场销售的 CS2 费用\n\n该调查得出的经济推论是：活跃的二手交易市场可以促进新商品的消费。大家熟悉的“15%”综合了市场费率，受最低收费标准和四舍五入规则的限制；它并非针对每一笔对外贸易征收的费用。\n\nValve社区市场的收费标准 ↗ 已归档 2026-09-21 ↗. 2026年2月25日纽约州总检察长提起了一项诉讼 已归档 2026-09-01 ↗ 指控付费开箱与外部现金转售及赌博危害存在关联——这正是本档案从技术基础设施层面所记录的关联。 该投诉仅为一项指控，而非调查结论；此处引用它是因为某州执法机构已就与本报告所提问题相邻的一个问题提出了质疑：与公开声明相符的执法记录究竟在哪里？\n\n01 / 条目加密货币存款\n\n外部服务和钱包记录\n\n02 / 转换平衡 → 皮肤\n\n通过 Steam 次交易交付的商品\n\n03 / 退出外部法定货币销售\n\n卖方、买方和支付服务提供商\n\nKYC？在每次交接时确定控制点\n\n这才是应调查的途径，而不是原生的 Steam API 现金兑换服务。在断言“无需KYC认证即可提现”之前，应记录各外部运营商的身份验证、托管情况、交易ID及提现接收方等信息。\n\n美国 / 《银行保密法》\n先对活动进行分类，再对义务进行分类。\n\n美国财政部金融犯罪执法网络（FinCEN）根据企业的具体经营活动来评估其是否属于汇款业务。 接受和传输可兑换的虚拟货币可能会触发货币服务义务，但须符合适用的定义和例外规定。Valve的Steam钱包接受资金并将其转换为游戏内道具；这些道具随后通过第三方运营商变现为真实货币。 该道具及其转移在 Valve 的基础设施上运行；而提现环节则不在其上，该循环中的任何部分是否符合资金转账的定义，属于 FinCEN 的分类问题，并非本文得出的结论。\n\n美国财政部金融犯罪执法局（FinCEN）FIN-2019-G001号文件，第1–2节、第5.1节 ↗ 已归档 2025-07-11 ↗\n\n欧盟 / 洗钱\n追踪资金流向、信息及协助情况。\n\n第(EU) 2018/1673号指令涵盖涉及犯罪所得的故意洗钱及参与行为。调查的核心问题在于：在2016年7月13日公开说明该用途之后，Valve对使用其交易和OpenID基础设施的运营商知情到何种程度，以及针对这些运营商采取了哪些措施。 Valve 未公布针对各运营商的执法记录；该记录——而非本案卷宗——才能解答上述问题。\n\n欧盟刑法框架 ↗\n\n《反洗钱指令6》（AMLD6）术语： 上述刑法指令与《(EU) 2024/1640号指令》（亦称AMLD6）不同。后者的总体转化截止日期为2027年7月10日，但有明确规定的例外情况。第78条 ↗ 已归档 2026-08-30 ↗\n\nC部分——法律框架 · 第16节 · 通知、答复、责任\n《数字服务法》：将相关信息载入记录\n上下文与来源限制\n\n第16条通知中的两个要素由提交方负责，而非本档案：提交方自身的详细信息以及关于信息准确性的善意声明。 该条文要求的其他所有内容——有依据的说明和确切的电子位置——均在第3节和路径登记册中列明，并附有已保存的响应和哈希值，以便任何一方均可提交。 该法律本身还有两项限制：丧失托管豁免权本身并不构成依据任何其他法律承担责任的依据，且第52(3)条中的“6%”是法定上限，而非针对“Valve”的评估处罚。\n\n根据《数字服务法》（DSA），网络服务提供商仅在已具体知悉相关情况却未采取行动时，才丧失其责任豁免权。本文件即为该通知。 其中列出了主机、日期、已保存的响应以及哈希值。自该报道发布以来，问题已不再是Valve是否知情——而是Valve接下来做了什么。\n\n012016年7月 / 档案展\n一项为期十天的要求。\n\n上述重建的通知是本次调查中执法比较的历史起点。\n\n022024年2月17日 / 一般申请\nDSA时间窗口。\n\n将历史上的行为与相关《数字服务法》（DSA）义务适用的期间内的行为区分开来。\n\n03十年 / 原始档案快照\n“Duration”需要一条通知记录。\n\n自2016年7月以来（见第11节）的累计时间是一项档案指标。这并非指长达十年的《数据安全法案》（DSA）违规行为。请将每份通知与具体事项、适用法律、送达证据及回复对应起来。\n\n第52条第3款 / 法定上限6%\n全球年营业额的\n\n违反《数字服务法》（DSA）义务的最高罚款金额，以服务提供商上一财政年度的业绩为基准。这是法律规定的上限，并非针对Valve所作出的具体处罚金额。\n\n第6条、第8条和第16条 / 法律标准\n\n对于相关托管服务而言，若具备特定知情情况且未及时采取行动，则可能导致丧失托管豁免权。一份足够明确的通知足以证明对特定内容的知情。DSA并未规定一般性的监控义务；丧失豁免权本身并不构成依据其他法律应承担的责任。\n\n《数据保护条例》（DSA）：第6条、第8条、第16条、第52条、第53条、第93条及第17条说明 ↗ 已归档 2026-09-20 ↗\n\n查看已存档的投诉 ↗创建账户时间轴 →完整的法律与经济分析 →\nC部分——法律框架 · 第17节 · 身份、年龄、商业访问\n未成年人：a Steam 登录不属于年龄验证\n上下文与来源限制\n\n本案卷任何地方均未出现未成年人的数据，也未收集任何此类数据：作者未在任何提及的平台上注册、提交信息或完成登录。任何基于本节内容开展工作的人员，均应将涉及儿童的证据保密，并从公开证据中删除可识别身份的细节。 此处援引《儿童在线隐私保护法》（COPPA）是将其作为一项具有特定适用范围（受众、实际知情情况、所收集的个人数据）的儿童隐私法律，而非作为一项通用的赌博年龄规定；2026年纽约州的投诉是州政府机构提出的一项指控，而非最终裁定。\n\n“使用 Steam 登录”可证明该账户确实存在。这并不能说明年龄有什么问题 ——而在这些网站上，这是阻隔孩子与存款之间的唯一一道屏障。请仔细阅读第3.1节: 在 Steam 客户端内部，浏览器本应显示的警告从未触发，因此子节点也从未看到过该警告。\n\nOpenID 提供了什么 Steam账户身份\n\n用于登录或绑定账户的已验证 SteamID。\n\n≠\n运营商必须明确以下事项参与资格\n\n年龄、管辖权及任何必要的身份核查。\n\n技术依据：Steamworks OpenID 文档 ↗ 已归档 2026-09-21 ↗. 经记录的身份声明并不构成对用户可合法参与赌博的认证。\n\n《儿童在线隐私保护法》（COPPA）/ 13岁以下儿童\n确定运算符和数据。\n\n《儿童在线隐私保护法》（COPPA）适用于受该法约束的面向儿童的服务，以及明知自己会收集13岁以下儿童个人信息的服务。这是一部儿童隐私保护法，而非普遍适用的赌博年龄规定。应明确目标受众、所收集的个人数据、知情情况以及家长同意流程。\n\n联邦贸易委员会（FTC）：《儿童在线隐私保护法》（COPPA）的要求 ↗ 已归档 2026-09-21 ↗\n\n应予以保存的证据\n记录从登录到存款的全过程。\n\n保留该网站的年龄验证机制、注册条款、资格条件、支付流程及投诉记录。对每位运营商分别进行评估。对涉及儿童的任何证据予以保密，并从公开证据中删除可识别身份的细节。\n\n一份相关的公共执法记录是2026年纽约投诉公告 已归档 2026-09-01 ↗，该报告指称付费“战利品箱”对年轻用户造成了伤害。这并非《儿童在线隐私保护法》（COPPA）的调查结论。\n\nC部分——法律框架 · 第18节 · 《通用数据保护条例》（GDPR）第15条规定的请求\n请求。响应。缺失的比较。\n\n他提出了四点要求，其中之一就是那份日志，它能揭露是谁在他的账户上添加了API密钥。三天后，该工单被关闭，并附有一个链接，但该页面上并没有这些内容。 ——而结尾那句话却与Valve自己的律师所说的相矛盾。\n\n这是谁的账号 · 来源与限制\n\n这些截图不是 PhishDestroy 的。 这些信息来自一位普通的Steam账户持有人——他是本项目开展的一项简短调查的受访者之一，由他本人提交了该请求并提供了截图。 该账户属于他本人，工单也属于他本人，相关通信内容均是他与Steam客服部门之间的往来。本项目并未提交该请求，在该平台上未持有任何账户，也不是该工单的参与方。\n\n2026年9月16日，他根据《通用数据保护条例》（GDPR）和《加州消费者隐私法案》（CCPA）第15条提交了数据主体访问请求，特别要求提供API密钥注册日志、包含IP地址的登录记录、设备授权记录以及交易记录。9月17日，客服代表“Logen”将他引导至自助服务的“账户数据”页面。 9月18日，他指出该页面未包含所请求的信息类别，并要求将此事上报至隐私团队或数据保护官（DPO）。9月19日，客服代表“Kal”以同样的指引关闭了该工单。两张截图均保存在下方（请求人的电子邮件地址已做遮盖处理；SHA-256在steam_tos_assets/screenshot-manifest.json).\n\n他之所以是合适的请求者，原因很简单：该账户持有一个他并未创建的 Steam Web API 密钥，该密钥注册于localhost.其创作时间不详 ——既不是针对他，也不是源自Valve向他提供的任何内容，因为唯一能确定其时间的记录是API密钥注册日志，而这恰恰是“闭包”所隐瞒的类别。该密钥并非新近产生的：出于同样的原因，它的存在时间比他知晓该密钥的时间要早，且这段时间长短他无法测算。\n\n其他账户持有人也在提交同样的请求。无论回复是否提供所列类别，均将按照与上述两例相同的规则（工单号、捕获日期、SHA-256、请求者信息已遮盖）在此处添加。\n\n本项目对该工单为何被关闭不持任何立场。工单中未说明原因，本文也未作任何推断。\n\n请求。响应。比较。关注《记录报》\n步骤 3 / 3\n\n他要求提供四个具体类别的信息。他所提及的“账户数据”页面是Valve自己的自助导出功能，而本项目无法为他人的账户列举其内容——因此，此处未发布按类别逐一对比的完整信息。 记录中显示的是他于9月18日所作的声明，即这些分类并不存在，以及9月19日的结案通知——该通知仅重复了转介内容，而未对此作出回应。\n\n请求具体类别API密钥、登录、设备和交易记录\n回应账户数据参考检查支持交换\n测试提供了什么？比较每个请求的类别\n屏幕 1/2 — 请求（9月16日）和首次回复，代理“Logen”（9月17日）\nGDPR ticket HT-2YBP-F7JP-D4VB — request and first response\n来源：help.steampowered.com，工单编号 HT-2YBP-F7JP-D4VB · 记录于 2026 年 9 月 16 日至 17 日 · 请求者邮箱已隐去 2026-09-21 · 文件：gdpr-ticket-1.png · SHA-256da940c731ab9869d226e9d06ccc8a1b393738766b7b0c445a56662623e025a66 (screenshot-manifest.json).\n屏幕 2/2 — 升级请求（9月18日）及结案，客服“Kal”（9月19日）\nGDPR ticket HT-2YBP-F7JP-D4VB — escalation request and closure\n来源：help.steampowered.com，工单编号 HT-2YBP-F7JP-D4VB · 截取于 2026 年 9 月 18 日至 19 日 · 文件：gdpr-ticket-2.png · SHA-25644844ea7b251f7fd7d79f87ee1578a846606a97b9659d3a53b322120c422219b (screenshot-manifest.json).\n结案答复，9月19日（逐字记录）：\n“Steam 保存的数据您已可在‘账户数据’页面中查看到。由于支持团队无法提供更多信息 Steam，该请求将被关闭。\"\n未提供数据 · 未说明拒绝的法律依据 · 未显示上诉结果\n这句话是错误的，而Valve自己的律师就证明了这一点。 律师2025年10月1日的信函第1.9段描述了将一台设备与数十个账户关联起来的设备级关联（附录A)。该答复中附有830页的存档记录（附录 B). 这些内容在“账户数据”页面上都没有。\n该账户为何要求提供 API 密钥日志\n\n他选择这四个类别并非随意。该localhost 他账户中的关键在于这是脚本留下的痕迹，而非有人在开发者页面中手动输入真实域名的结果 (第5节,第6节). 唯一能显示该记录由谁创建以及来自何处的，就是API密钥注册日志。这是他首先要求提供的。而这正是“结案”方所隐瞒的内容。\n\n来源：该账户持有人，摘自本项目的调查。上方的工单截图已进行哈希处理；密钥页面未公开。\n\n评估 · PhishDestroy\n\n在此情况下，在问题尚未解决时关闭工单并非偶然，而是正常结果。我们坚持16,319 已保存的投诉和支持记录 以及354 条去重后的支持交流记录 源自这些。这张票据就是其中一个日期明确、完整记录的实例，展现了它们的具体形态。\n\n支持工单 — 已保留HT-2YBP-F7JP-D4VB\n请求类型《通用数据保护条例》（GDPR）第15条 DSAR\n票务状态已关闭 2026年9月19日 — 未提供数据\n交易所中的代理“洛根”（9月17日），“卡尔”（9月19日）\n归档2026年9月16日\n所需数据谁注册了与该账户关联的 Web API 密钥？以及注册时使用的 IP 地址、设备及时间戳是什么？\n援引的法律依据《通用数据保护条例》（GDPR）第15条——获取个人数据的权利\n法律框架：第12条第3款规定，数据控制者自收到通知之日起有一个月的时间（可因正当理由予以延长）。截至本文发布时，该期限尚未届满，且本案卷宗并未主张存在逾期情况。 异议针对的是实质内容：最终答复中虽提供了自助服务页面的链接，但并未显示已提供所列的四类数据；且若数据控制者拒绝采取行动，根据第12条第4款的规定，其应说明理由并告知投诉途径。而最终答复中既未说明理由，也未提供投诉途径。\n为什么这些具体数据很重要\n\nWeb API 密钥事件日志是一份记录，用于显示第三方是否使用被盗的会话 Cookie 注册了密钥—— 这正是本档案库中保存的“库存被盗”投诉中所描述的机制。 披露谁注册了 API 密钥、来自哪个 IP 地址以及具体时间戳，将：\n\n允许受害者将 API 创建 IP 与自己的登录记录进行比对\n披露与已知网络钓鱼/赌博僵尸网络基础设施相关的数据中心IP地址\n提供可在针对该行为人的民事或刑事诉讼中使用的证据\n显示在生成密钥时是否已通知账户持有人\n记录显示： Valve 保留了设备级和账户关联记录——其法律顾问在2025年10月1日的信函中对此进行了说明（参见附录A，《证据备忘录》——来源1）。 在工单 HT-2YBP-F7JP-D4VB 中，数据主体曾要求获取同类记录，但该工单在关闭时仅提供了自助服务页面的链接，而数据主体报告称该页面上并未包含相关记录。 该拒绝是否合法应由监管机构裁定；其结果是，数据主体未能获得相关记录。\n这段对话——四条消息，三天\n\n两名Steam客服代表根据工单上显示的名字进行了回复：9月17日是“Logen”，9月19日是“Kal”。两人均将请求者引导至“账户数据”页面。 工单中没有任何信息表明该请求是否已转交至 Valve 的隐私团队或数据保护官，且案卷中也未说明这些客服人员的身份、职责，以及工单的流转路径。\n\n9月16日\n根据第15条提交的请求，其中列出了四类数据\n9月17日至18日\n关于账户数据的咨询；请求方要求上报至数据保护官（DPO）\n9月19日\n工单以相同的转介理由关闭；无数据，未说明依据\n《通用数据保护条例》（GDPR）第15条明确赋予数据主体哪些权利？\n第15条第1款(a)项处理目的——Valve 为何持有这些数据\n第15条第1款(b)项数据类别——Valve包含的内容\n第15条第1款(c)项接收方或接收方类别 —谁接收了这些数据（例如，API密钥持有者）\n第15条第1款(d)项保存期限或确定保存期限的标准\n第15条第3款正在处理的个人数据的副本——即 API 密钥日志本身\n第12条第3款请在以下时间内回复一个月 自收到之日起；如需延期，须在该月内提出。截至发布之时，该期限尚未届满。第12条第4款： 如果控制者不采取行动，则必须说明理由，并告知投诉人投诉的渠道。\n监管投诉渠道——面向所有用户\n\n任何向Valve提交了《通用数据保护条例》（GDPR）第15条请求但未收到合规答复（或收到未包含具体数据的模板化拒绝函）的用户，均可向 其所在欧盟/欧洲经济区（EEA）成员国的监管机构提出投诉。 Valve在欧盟的经营实体是位于汉堡的Valve GmbH，因此跨境投诉的主管监督机构是汉堡数据保护与信息自由专员办公室（HmbBfDI）。（Valve第27条规定的代表也位于汉堡；代表的地址本身并不决定管辖机关。）根据第77条，投诉人也可向其所属成员国的主管机关提出投诉。\n\nHmbBfDI 投诉表 ↗ 《通用数据保护条例》（GDPR）条文（第12条、第15条、第77条） ↗ 已归档 2026-09-20 ↗欧洲数据保护委员会（EDPB）指南 ↗\n\n任何投诉的工单编号：HT-2YBP-F7JP-D4VB — 作为一则有据可查的案例收录于本档案中。\n\n一则有据可查的案例\n这些记录确实存在；但数据主体并未收到这些记录。\n\nValve的律师在2025年10月1日的一封信中描述了设备级关联记录。 2026年9月19日，针对同一类记录的第15条请求被结案，处理方式是将请求人引导至一个自助服务页面，而请求人报告称该页面未包含相关记录，且未说明法律依据。 工单HT-2YBP-F7JP-D4VB即为其中一例；该做法是否具有普遍性，需由监管机构裁定，监管机构可向Valve索取其处理记录。\n\n《通用数据保护条例》（GDPR）第12条、第15条、第77条 / 监管机构\n\n根据第12条和第15条提出的投诉可直接向相关监管机构提出，且无需支付费用（第77条）。 该机构可采取纠正措施，包括下令遵守查阅请求，并根据第83条第5款(b)项对侵犯数据主体权利的行为处以罚款。 保留原始工单编号及任何Valve回复（或未收到回复）将增强投诉的说服力。\n\n查看 DSAR 模板 →\nC部分——法律框架 · 第19节 · 合同法\n与该平台自身架构相悖的订阅协议\n上下文与来源限制\n\n作者并非律师，本文内容均不构成法律建议。引用的《社会保障法》（SSA）内容来自2026年9月10日的修订版；不同修订版的表述可能有所不同，且各修订版中的条款编号已发生变更——请对照规范相关行为的适用版本核对条款内容。 关于第25条和第32条的论点阐述了法规的要求，并不意味着监管机构已认定存在违规行为。论点1中的数据包含第13节所规定的范围限制。\n\n《SSA》的三项核心条款与该平台的构建方式存在明显冲突：禁止商业用途的规定，以及将高价值交易挤出平台的“市场价格上限”； 关于API密钥的用户责任条款，与在2023年前无需双因素认证的密钥端点相悖；以及关于执法条款的表述，与显示未对各运营商进行执法的公开记录相矛盾。这些矛盾是否影响条款的可执行性，需由法院裁决；本节阐述了法院审理时将面临的事实情况。\n\n论点1 / 市值架构\n市场上限与商业用途禁令\n\nSteam社区市场的挂牌价格上限约为$1,800。在一份过时的快照（2026年9月23日）中，五个市场中有248个CS2商品类别，其中至少有两个市场的定价独立地超过了该上限；此类商品在Valve自己的平台上无法以这些价格出售. 希望获得这些价格的车主会使用第三方市场，这些市场通过 Steam 账户和 Steam API 运行——请注意，除非获得明确许可，否则美国社会保障局（SSA）将此类行为归类为商业行为。\n\n商品数量超出市场上限 → 第三方市场填补缺口 → 这些市场使用 Steam 账户和 Steam API → SSA 禁止未经许可的商业用途 → 尚未公布许可登记册。 社区市场的总手续费约为 15%，仅适用于在该市场内完成的交易，不适用于这些外部交易。\n论点 2 / API 密钥安全架构\nAPI密钥漏洞是一个平台设计问题，而非用户疏忽所致\n\n在 2023 年之前，Steam 的 API 密钥创建端点会接受包含被盗 sessionid 的 POST 请求，并生成高权限凭证。没有电子邮件确认、双因素认证或设备验证. 本次调查中收集到的API劫持投诉均遵循一种模式：攻击者脚本、窃取会话Cookie、隐式密钥生成、交易拦截（请求负载见第8节）。\n\n《通用数据保护条例》（GDPR）第25条（数据保护设计）和第32条（处理安全）要求采取与风险相适应的技术措施。 在未采用第二重身份验证或未通知所有者的情况下，签发可能被第三方截获的凭证，属于数据控制者的设计问题。在此背景下，SSA 条款中将责任归咎于用户的规定是否具有法律效力，应由法院和监管机构裁定。\n\n论点3 / 实时可视性\nValve 在每次登录时都会接收认证主机名\n\n认证主机名以明文形式发送到 Valve 的 OpenID 端点，具体如下：openid.return_to 和openid.realm （请求格式如第3节所示）。提取该信息是一项标准操作。截至2026-09-22，在26对主机中，主域被列入了链接过滤器，而承载其Steam登录信息的主机则未被列入。 Valve 未发布任何按运营商分类的强制执行记录，因此无法根据公开数据确定是否对这些主机采取了除“链接过滤器”以外的其他措施。\n\n谁承担费用\n存档投诉中的规律\n\n在已审查的投诉中，Steam 支持团队对 API 密钥被劫持的申诉所作的回应均遵循一种模式：拒绝恢复，强调用户对账户及其 API 密钥负有责任，然后关闭工单。本档案中未对受影响的账户数量或损失金额进行估算；也未找到此类数据的来源。\n\n问题并不在于个别用户是否犯了错误。问题在于，谁应该为这种架构负责——这种架构直到2023年仍允许使用被盗Cookie发起POST请求，从而在没有任何通知且无需双因素认证的情况下，创建出高权限的交易凭证。\n作为文件的《社会保障法》与作为合同的《社会保障法》\n法院在审查本案卷宗时，不会孤立地解读《社会保障法》。\n\n它将结合律师2025年10月的信函一并阅读，该信函描述了设备层面的关联性、授权主机的注册日期、批次注册的时间戳、API密钥请求的有效载荷，以及从2016年7月的通知到2026年9月平台仍在运营期间的这十年间隔。 这就是Valve必须处理的记录。\n\nSSA与记录不符 / 要点\n“禁止商业用途”——该市场的上限将高价值交易推向了商业性质的第三方市场\n“用户需对 API 密钥负责”——2023 年之前，密钥端点不启用双因素认证\n“我们对违规者予以处罚”——自2016年7月以来，未公布过按运营商分类的执法记录\n“您已同意条款”——在劫持模式下，该接受请求是由脚本提交的，而非账户持有人\n结论 · 案卷所载事实及本院的请求\n调查结果。我们要求的记录。\n上下文与来源限制\n\n下文中的每一项调查结果都与上文各部分中注明日期的公开记录相关联。这些请求是向那些能够获取本项调查无法触及的唯一信息——Valve自身的执法、访问和处理记录——的相关主管部门提出的。\n\n每项请求都基于一份带有日期的调查结论。当局可以调取本项基于公开资料的调查无法强制获取的记录。\n\n公开记录所证实的事实\n44个在线平台通过独立的可注册域名进行身份验证——其中27个已发布按路由分类的证据文件，17个来自手动收集，并单独列出。 截至 2026-09-22，有 26 对平台的主域名在 Steam 链接过滤器中被屏蔽，但承载其登录功能的主机却未被屏蔽——csgogem.com 被屏蔽，api.csgem.com 自2014年3月起注册。Steam 接收该主机名在openid.realm 以及openid.return_to 每次登录时。第3节\n2016年7月13日，Valve公开指出了该机制并予以禁止，其律师于2016年7月20日发出的通知设定了十天的期限。自该期限届满以来的十年间，尚未公布任何按运营商分类的执法记录。第11节\n该 Steam Web API 密钥端点仅凭一个会话 Cookie，就在 2023 年之前未实施双因素认证的情况下，签发了一条具有高权限且可进行交易的操作凭证。第5节\n一项根据《通用数据保护条例》（GDPR）第15条提出的请求（工单编号 HT-2YBP-F7JP-D4VB）在三天后被关闭，仅附有一个自助服务链接，未提供任何数据。第18条\n我们向各主管部门提出的要求\n华盛顿州博彩委员会\n重新打开2016年的文件。要求提供一份按运营商分类的详细清单，列明在发出十天通知后，哪些账户、机器人和返回主机被停用，以及哪些运营商随后重新获得了访问权限。第2节\nHmbBfDI（汉堡；Valve GmbH）\n审查第15条规定的答复是否履行了数据控制者的义务，并要求披露与识别行为人相关的API密钥注册和访问记录。第18条\nDSA 数字服务协调员\n将该记录中的认证主机路由标记为“通知”，待相关信息记录在案后，再评估Valve的回应是否履行了其义务。第16条\n任何数据主体\n请使用第15条模板，为您的账户申请相同的记录；保留的记录可用于核查是谁发起了重置操作或创建了密钥。附录G\n\n这四项请求背后的共同诉求是相同的：公开仅由Valve掌握的执法、访问和处理记录。主页上的警告、十日通知函以及自助服务页面，都是对控制权的体现。控制权是否被行使，这是公共记录无法回答、但监管机构能够回答的问题。\n\n附录——主要证据材料和工作资料\n附录 A — 律师往来信函\n证据备忘录——由来源1提供的材料\n\n第1、18和19节所依据的律师往来信件的证据基础及来源情况。\n\n证据基础与来源状态——由来源1提供的文件\n引发此次审查的那个被永久封禁的用户并非本次审查的对象。该封禁是否合理，在此不予探讨，本报告既不为其辩护，也不对此提出异议。该账号本身并非重点。关键在于相关材料：来源 1 ——该被封禁账户的持有人作为其自身《通用数据保护条例》（GDPR）请求中的数据主体，收到了来自Valve律师的以下信函——他转交了该信函及随附的案件文件，并授予了公开查阅这些文件的权利。姓名不予公开；文件按日期、生成元数据和哈希值进行标注。\n\n该函件是针对一项《通用数据保护条例》（GDPR）/数据主体访问请求（DSAR）作出的回应。在此过程中，Valve的律师提交了一份经签署的书面声明，其中描述了一项功能——此前Steam技术支持部门曾向用户表示该功能在技术上无法实现。下文引用的段落即为该声明。\n\n作者对生成的日志摘要进行的进一步分析是未收录于本档案中 尚待独立审查。本调查的其他部分均未以此作为依据。\n\n记录在案的承认：持续的设备级遥测\n\n在据称由Valve的代理律师撰写的信函第1.9段中，Valve的律师指出：“2019年至2023年期间，该账户主要通过一台设备进行操作，而该设备还曾用于登录数十个被盗的Steam账户。”\n\n事实： Valve的律师在此描述了跨越四年时间、跨账户的设备级关联情况。Steam 客服人员曾告知被盗受害者，从技术上讲无法追踪被盗物品或将账户与设备关联。 Steam Guard 设备授权机制已有公开记录，因此存在按设备分类的记录本身并非新鲜事；真正的新情况在于，该律师以书面形式确认，这些记录被保留下来，并在跨账户、跨年度的范围内进行了关联分析。\n\n为什么这很重要： 这种能在四年内将一台设备与数十个被劫持账户联系起来的关联记录，恰恰属于支持部门声称无法向受害者提供的同一类记录。 此类记录能够识别盗窃和转售链条中的账户和设备。哪些记录存在、保留期限多长，以及基于何种理由不向数据主体披露这些记录，这些都是监管机构需要解答的问题。\n\n来源：Valve的律师于2025年10月1日发出的信函，第1.9段及其830页的PDF附件 · 由来源1根据《通用数据保护条例》（GDPR）第15条提出的请求而收到 · 附件的SHA-256校验和记录在disclosure-audit.json · 信件内容未予转载；账户名称和第三方数据均已省略。\n\n状态：打开\n原始资料可通过证据档案库获取。\n附录 B — 生成的 PDF · 内容删节核查\n生成的PDF文件中的遮盖仅是表面处理：被遮盖的文本仍可被提取\n\nValve的律师在回复一份《通用数据保护条例》（GDPR）信息获取请求时，附上了一份长达830页的附件，其中被遮盖的内容是直接在文本上涂黑处理，而非将其删除。902,270 个字符位于黑色条形下方，并可通过文本提取工具直接提取出来 ——包括那些条形图原本旨在隐藏的第三方标识符。此处仅公布汇总数据；未转载任何受保护的内容，且附录本身亦未公布。\n\n1. 几何检查发现的问题\n\n日期为的《通用数据保护条例》（GDPR）第15条答复2025年10月1日 该文档附带了一份830页的PDF附录（Aspose.PDF for .NET生成的元数据，创建和修改日期相同）。作者进行了页面级几何检查：针对每一页，定位出在文本图层之后绘制的、不透明且接近黑色的矩形，并统计了其下方可提取的字符数量。\n\n基于生成的文件进行测量\n902,270\n黑色条纹下方仍可辨认的字符\n是统计得出的，而非估算的。这是对相关角色的统计——而非对受害者、身份重新确认或事件的统计。\n830 / 830\n受影响的页面 — 所有页面\n986\n覆盖在可提取文本上的矩形\n1,329\n不透明黑色矩形的总数\n黑色条纹绘制在文本图层之上，并未将其删除。条纹下方的文本可使用标准的PDF工具进行提取。此处仅公布汇总数据，未复现被遮盖的内容。\n法医演示：层间分离\nASPOSE.PDF FOR .NET 矢量叠加效果图（附录 P. 412）\n\n针对该账户提交的报告：[登录：redacted_user_667]\n\n用户提交的理由：[文本：“用户报告称库存中存在重复物品以及滥用交易行为……”]\n\n前景：<path fill=\"#000\" />漏洞：底层 UTF-8 流完好无损\n来源：2025年10月1日法律顾问函的PDF附录（830页，Aspose.PDF for .NET生成的元数据）· 由作者测量，方法及每页计数见disclosure-audit.json · 同一文件中记录的附录的 SHA-256 值 · 附录本身未公开发布。\n2. 这对数据主体的回应为何重要\n\nValve的律师将此文件发送给一名数据主体，以回应该人对其本人记录的请求。 文件上的遮盖条仅起装饰作用：下方的文本从未被删除，因此这些遮盖条原本旨在隐藏的第三方标识符，最终仍随文件一并发送给了收件人。这种可通过文本提取工具轻松去除的遮盖处理既无法真正隐藏任何内容，也会导致收件人无法分辨哪些信息被披露、哪些未被披露。\n\n第15条第4款正是这些限制存在的原因：获取副本的权利不得对他人权利和自由造成不利影响。而本作品未能履行这一义务。 是否应根据第4条第(12)款将其定性为个人数据泄露，应由监管机构裁定；该披露行为本身可在文件中量化，且任何持有相同字节数据的人均可复现——SHA-256值已公开，但附录内容尚未公开。\n\n横杠下显示的并不是账号。 这是针对该请求者提交的用户报告正文，其中附有报告作者信息：Steam次登录记录——由于登录账号极少仅在Steam上使用，因此可以据此识别出背后的人——据作者统计，该文件中提及的用户中，有超过 60% 名可被完全识别 ——以及他们所写内容的原始、未经编辑的文本。该文本包含针对请求者国籍的死亡威胁和辱骂言论。其中一些被指认的人员是未成年人。该制作组将一份列有名字的记者名单交给了他们所报道的那个人，而这正是第15条第4款旨在防止的具体危害。\n\n文件的顺序与内容同样重要。 该请求最初因申请人的别名电子邮箱地址中未包含其姓名，而被要求提供进一步的身份证明；在此后的延迟期间，该账户被永久封禁。 最终提供数据的信函——此时距《第12条第3款》规定的一个月期限已过去六周多——威胁收件人将面临刑事起诉，并扣留其剩余数据，直至其向律师解释账户活动情况。 此次披露还澄清了两个 Valve 此前未在公开场合回答的问题：所提供的记录显示，账户关联可追溯至2019年，且内部遥测数据的深度是 Valve 从未描述过的。\n\n本节的适用范围： 此处的观察仅限于编辑过程的机制，依据的是生成的文件进行评估。作者对生成的日志所做的进一步分析，在等待独立审查期间暂不公布，且本文件的其他部分均未以此作为依据。\n\n证据：2025年10月1日的律师函及其PDF附件（SHA-256已记录在审计文件中）；页面级 PDF 测量及其方法 ↗. 该请求的经过、第8页的拒绝以及被泄露记录的特征描述，在PhishDestroy的陈述中均有详细说明，“我的狗 vs. 顶尖的GDPR律师”，2026年8月17日 ↗ 已归档 2026-08-21 ↗. 此处省略了账户名称和第三方数据；图表中遮盖的部分均未显示。\n\n附信第8页驳回了该请求的一部分，并以书面形式说明了理由： 出于对Steam平台其他用户个人数据的保护……无法提供更详细的信息。 ——无法给出更详细的回答，因为必须保护其他 Steam 用户的个人数据。那份长达 830 页的附录就在同一份材料包中。 被遮盖的内容并非账号：而是针对申请人的举报报告，其中列明了举报人的姓名，并附有未经编辑的原始信息。该账户持有人曾通过其律师向Valve索要自己的档案；但他从中提取到的却是他人的信息。 该附录中的内容与划框者是谁无关。它所证明的是：Valve作为拒绝披露依据所援引的保护措施，恰恰是此次文件提交——在同一个信封中、同一天——未能做到的保护。\n赡养费及法律信函附件\n\n来源: https://phishdestroy.io/steam_dossier/zh/index#exhibit-gallery-section\n\n附录 D — 源代码收集\n精选原始记录\n\n档案中的六条记录——Valve跟踪器中的三条 GitHub 问题，以及三个关于有争议的支持结果的 Reddit 账号。每个来源都与相关主张、保存的文本以及由此引发的问题相关联。\n\n1 / 6 选定记录\n选择源记录\nGH-01 / GITHUB在已保存的构建中打开\n2016年申请的硬件密钥\n\nValveSoftware / steam-for-linux · #4521 · 2016-06-27\n\n一位用户请求将 U2F 硬件密钥作为第二种身份验证方式纳入支持范围。该已保存的问题同时带有“功能请求”和“已审核”标签，状态记录为“待处理”。\n\n我请求 Steam 支持 U2F USB 密钥作为替代方案。\n\n摘自 GitHub 问题 ↗\n书面记录\n一项关于增加账户安全措施的过期请求，已发布在Valve的内部问题跟踪系统中，并标记为“已审核”。\n问责要求\n发布产品决策、回复日期以及审核后提供的保护措施。\n读取已保存的记录→打开 GitHub ↗\n在文件夹中：账户安全措施 →存档 #484 · 构建 2026-09-17\nGH-02 / GITHUB在已保存的构建中打开\n没有有效退出机制的崩溃报告\n\nValveSoftware / steam-for-linux · #6459 · 2019-08-18\n\n该记者描述了2019年8月12日运行于Ubuntu 16系统上的一位Steam用户的情况。据称，禁用crash-upload目标后的设置在重启后并未保留，并附上了相关配置。\n\n如果我禁用 `ServerURL`，每次重启后该设置都会被覆盖。\n\n摘自 GitHub 问题 ↗ 已归档 2026-04-19 ↗\n书面记录\n一条具体的隐私投诉，其中包含客户日期、操作系统以及配置摘要。该已保存的问题目前处于“已打开”状态。\n问责要求\n确定相关调查、受影响的构建版本以及使“选择退出”生效的变更。\n读取已保存的记录→打开 GitHub ↗已归档 2026-04-19 ↗\n在档案中：请求相关记录 →存档 #467 · 版本 2026-09-17\nGH-03 / GITHUB在已保存的构建中打开\n已向 Valve 报告了 Auth-ticket 滥用情况\n\nValveSoftware / Source-1-Games · #3857 · 2022-02-26\n\n作者指控某服务器运营方在玩家断开连接后仍保留了Steam个认证凭证，并使用了具有误导性的服务器列表。该帖子要求Valve对此行为作出说明。\n\n让他们的服务器看起来人满为患。\n\n摘自 GitHub 问题 ↗\n书面记录\n2022年2月26日，在Valve的追踪器中提交了一份公开滥用报告。该报告的保存状态为“已打开”；报告中包含截图链接。\n问责要求\n就已报告的身份验证票据滥用事件，提交调查结果和缓解措施记录。\n读取已保存的记录→打开 GitHub ↗\n在文件集中：数据集范围 →存档 #768 · 构建 2026-09-17\nRD-01 / REDDIT作者简介\n44笔有争议的市场采购\n\nr/DotA2 · 作者昵称未公开 · 2022-07-07\n\n作者报告称，2022年7月6日发生了44笔未经授权的Market购买交易，损失金额约为$500+。据其称，当时已启用双因素认证，并描述了客服反复发送的模板回复。\n\n这已经是提交的第二张工单了，但我至今仍未收到来自 Steam 的非机器人式、非复制粘贴的模板回复。\n\n摘自 Reddit 帖子 ↗ 已归档 2025-03-20 ↗\n书面记录\n一份关于争议购买的过往记录，其中包含交易截图链接及客服回复。金额和事件均来自作者的报告。\n问责要求\n根据交易日志和会话日志核对有争议的购买记录。说明技术支持团队做出该决定所依据的证据。\n读取已保存的记录→打开 Reddit ↗已归档 2025-03-20 ↗\n本文件夹内容：支持与执行 →存档 #4,533 · 版本 2026-09-17\nRD-02 / REDDIT作者简介\n永久封号及上诉通道关闭\n\nr/ohnePixel · 作者昵称未公开 · 2024-12-09\n\n作者对永久封禁提出异议，并表示支持方援引了疑似账号转移和社区举报作为依据。作者描述了已关闭的工单，并计划申请获取其个人数据。\n\n我说明了我的情况并要求提供更多细节，但他们坚持自己的决定，并关闭了我的工单。\n\n摘自 Reddit 帖子 ↗\n书面记录\n一份保存下来的呼吁记录，其中包含作者所述的支持理由以及四张图片的链接。发布日期来自所选的支持数据导出文件。\n问责要求\n请指出支持永久禁令的证据，以及可用于对此提出异议的复核程序。驳回上诉并不等同于对该决定作出解释。\n读取已保存的记录→打开 Reddit ↗\n在档案中：请求相关记录 →存档 #4,766 · 版本 2026-09-17\nRD-03 / REDDIT作者简介\n恢复重置及报告的 $10,000 损失\n\nr/legaladvice · 作者昵称未公开 · 2025-05-09\n\n该用户指控称，在他人提交恢复请求后，客服重置了其账户凭证并禁用了账户保护功能。据其报告，一个处于非活跃状态的账户损失了约 US$10,000。\n\nSteam 客服帮我重置了密码，并关闭了我账户的所有安全设置。\n\n摘自 Reddit 帖子 ↗\n书面记录\n一条关于恢复流程会绕过账户安全措施的指控已被保存下来。该保存的帖子记录了作者所称客服人员向其说明的内容。\n问责要求\n查明谁授权了重置操作、其认可的所有权证明以及访问日志。账户恢复是安全系统 Valve 控制措施的一部分。\n读取已保存的记录→打开 Reddit ↗\n在该档案中：请求相关记录 →存档 #4,592 · 版本 2026-09-17\n\n六条选定的记录。GitHub 描述说明了已保存的构建情况。Reddit 帖子保留了作者的账号信息。\n\n下载这六首歌曲 ↓\n\n可搜索的构建包含16,319 条独立记录: 393 条 Trustpilot 记录、5,635 条 Reddit 记录、2,395 条 GitHub 记录、276 条网页记录和 7,620 条维基记录。多条记录可能涉及同一事件。单独的 40,448 行主导出文件的范围有所不同。\n\n搜索完整存档 ↗ ·构建清单 ↗ ·数据集范围和计数 →\n\n附录E — 案例研究\nArchiSteamFarm 以及自动化条款\n\n一款开源的卡片刷取工具，其官方常见问题解答中声称该工具运行于数百万个账户上，这与《订阅协议》中禁止自动化操作的条款（§ 4.C）相冲突。 其运作机制——即一个刷卡农场在开始产出前必须从 Valve 购买什么、为何所有提现方式均违反许可协议、违规处理记录以及由谁监管卡片经济——已在附件五 ↗.\n\n《Steam 用户协议》第 4.C 条规定：\n\n“您不得以任何形式使用脚本、机器人、宏或其他非人工控制的系统（以下简称‘自动化工具’）以任何方式与 Steam 上的内容和服务进行交互。” —Steam 订阅协议 第4.C条（现行） ↗ 已归档 2026-09-18 ↗\n\nValve 负责执行本条款。它在这方面做得非常出色。 的常见问题解答ArchiSteamFarm (ASF) — 据其文档所述，这是一个可在以下平台上运行的开源工具：超过几百万个 Steam 账户 自11多年前首次发布以来——该系统重现了三条Steam支持消息，这些消息永久封禁了运营机器人网络的用户。Valve发现了这些网络，指名道姓地指出了它们，并将其摧毁。因此，关键问题并不在于Valve能否大规模检测自动化行为。\n\n该项目的官方网站ArchiSteamFarm 常见问题解答 直接针对被禁的风险：\n\n“考虑到ASF自11多年前首次发布以来，已有超过几百万个Steam账户在使用它，这种情况极不可能发生——但无论实际概率如何，这种可能性依然存在。”\n\n“Valve 明确承认了‘Steam 闲人’的存在，正如这里所说，所以如果你问我的话，我相当确定，如果他们对这些人感到不满，他们早就采取行动了，而不是只是指出这些人可能会在 VAC 方面引发问题。”这里的关键词是“Steam”类闲置游戏，例如ASF，而不是游戏类闲置游戏。\"\n\n— ArchiSteamFarm 常见问题解答，JustArchiNET。来源：GitHub 维基 ↗ · 经核实，原文照录 2026-09-22\n\n同一份常见问题解答中，针对“有人因此被封号吗？”这一问题，回答道：是的，并转述了Steam Support 给其中三人的回复：\n\n1,000+ 机器人 · 交易被禁\n“该账号似乎曾被用于管理一个机器人账号网络。使用机器人账号的行为违反了《用户协议》第 Steam 条。”\n\n170多个机器人 · 已被永久封禁，2017年冬季促销\n“该账号曾被用于在Steam上非法收集收藏卡，以及相关活动（不仅限于商业活动）。该账号已被永久封禁，Steam客服无法就此问题提供进一步协助。”\n\n120多个机器人 · 永久封禁\n“该账号及其他账号被用于对我们的网络基础设施进行流量攻击，这违反了Steam的网络行为规范。”\n\n— Steam 转引自 ArchiSteamFarm 常见问题解答（FAQ）中“有人因此被封号吗？”一节的支持信息。来源 ↗ · 经核实，内容与原文完全一致 2026-09-22\n\n将这两份记录并排摆放。 一名拥有 1,000 个刷分机器人的个人用户被查出，被告知“使用机器人违反了 Steam 用户协议”，并被永久封号。 本档案中所涉的商业平台将运行自动化的Steam账户作为其核心业务，规模远超上述情况，且每次登录均通过Valve自有的OpenID进行身份验证——但迄今为止，尚未公布针对其中任何一家平台的按操作员分类的执法记录。该条款是有效的。问题在于它针对的是谁。\n\nASF在此并未被指控任何行为，且其对Valve立场的解读纯属其自身观点——该文作者明确指出“ASF未获得Valve的授权”。 此处将该工具作为衡量标准：它表明 Valve 能够检测到机器人网络，并在书面文件中指名道姓地列出这些网络，并对其实施永久封禁。Valve 只需公布其授权使用的商业自动化工具，并按运营商列出针对其余情况的具体处理记录，便能一语终结这一争议。\n\n卡牌刷分如何影响 Valve 的收入\n\n通过刷取获得的交易卡在Steam社区市场出售，该市场对每笔在市场内完成的交易收取总计约15%的手续费； 账号必须在Steam上消费$5.00美元，才有资格获得卡牌；且卡牌掉落需拥有游戏或进行游戏内购买。 此处未估算总收入数据——运营规模仅按 ASF 常见问题解答中的表述进行说明。该常见问题解答还记录了 Valve 项区别\"Steam 懒人\" （卡牌刷图）来自“游戏闲人”; 参见ASF 常见问题解答 ↗. 具体机制详见附件五——比例尺Simplified Chinese (Mainland) 以及商业用途的陷阱.\n\n主题ArchiSteamFarm — 自动刷卡\n标注比例数百万个账户（据ASF常见问题解答——确切的活跃账户数量尚未得到核实）\n“计数”，而非“引述”10,880,610 ASF 自身 Steam 组中的 API 条目总数（5,360,499 无限制，如 Steam 所示）——常见问题解答中提到的“数百万”并非虚构，而是实际数量。 88.97%不包含任何形式的Steam禁令。全面禁令统计 ↗\n该工具自身文档中的披露信息\nASF 会以无界面模式登录账号，并在不启动 Steam 客户端的情况下让游戏处于空闲状态以获取卡牌（根据项目文档）。\n常见问题解答中解释道，Valve 知道有“Steam 闲人”，并且“如果他们对这些人感到不满，早就采取行动了”。\n据“常见问题解答”称，11年多来未曾有针对性执法的报道；由此产生的社区市场内的卡片销售额，需缴纳Steam的综合手续费，金额约为15%。\n常见问题解答中指出，建议每位操作员最多管理十个账户，并将此归因于Valve：“该建议基于内部Valve指南以及我们自己的建议。”Valve并未发布此类指南。\n根据同一份常见问题解答，技术上限为：“一个 IP 地址和一个 ASF 实例最多可运行 100 至 200 个机器人。”\n刷游戏时间的数据由 Valve 记录——“通常每30分钟左右更新一次”——而§ 4.C 将“伪造游戏统计数据（例如虚增胜场或负场、经验值、游戏时间）”列为禁止行为。\n来源\nJustArchi ASF 官方常见问题解答维基 ↗ ArchiSteamFarm 存储库 ↗ 已归档 2026-09-24 ↗\n关于自动化的条款表述明确；ASF常见问题解答多年来一直指出，该工具已在数百万个账户上运行；目前尚未有针对该工具的定向执法行动的报道。规则与其实际应用之间的差距有据可查；其原因在此尚未查明。\n完整展品卡牌经济：运作流程、规模、许可及监管方 ↗一个农场在生产出一张卡片之前，必须从 Valve 处购买什么； § 4.C 中那两行根据其效果将卡片农场活动命名的条款；为何每种套现卡片的方式都违反了 Valve 撰写的许可协议，而 Valve 却在入口处收取费用； 执法记录，包括2025年6月的VAC行动以及基于共享电话号码的连锁封禁；以及在Steam周边负责管理卡片交易和封禁名单服务的Valve名员工和社区版主。禁令普查我们没有问Valve农场有多大。我们亲自数了一下。↗10,880,610 个账户（含受限和非受限账户）是从 ArchiSteamFarm 自己的 Steam 群组中读取的，该软件在首次启动时默认会自动加入该群组，除非用户取消勾选“加入群组”设置 （涵盖了商业机器人农场以及未更改默认设置的普通玩家）。88.97% 未受任何形式的 Steam 禁令影响；在受禁的 11% 中，有 99.8% 属于仅影响形象的社区禁令，这些禁令并不影响交易。 经与 SteamRep 交叉核对，一旦解除反作弊禁令，所列骗子中的 67.77% 便能逍遥法外。通过注册日期、地理位置及存活率分类数据——这是经过实测的真实规模，而非道听途说。\n\nAppendix F — Working ledger\n\nRules ledger: clauses against recorded platforms\n\n选择一条规则；该注册表会列出标记在该规则下的已记录平台，包括其主域名、声明的认证主机以及保存的链接过滤结果。如果是被屏蔽的网站，或是用于登录的另一个域名：请按照该规则继续操作，直至到达剩余的路由。\n\n175关联记录\n关于这条规则\n174 主要域名0 C&D提及\n法规摘录 / 《社会保障法》第2.G条\n商业用途与账户扣费\n“…exploit the Content and Services or any of its parts for any commercial purpose, except as expressly permitted elsewhere in this Agreement (including any Subscription Terms or Rules of Use).”\n追踪记录\n平台注册 175\n比例数据为来源方的估计值\n\n175 175条记录\n\n服务 / 上级组\t主域名/注册局\t观察到的认证域/年龄\t量表 / 记录的反应\n\nCasino\n\tcsgoempire.com\n11.3 yearsRegistered 2015-06-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgoempirelogin4.com\n6.2 yearsRegistered 2020-07-20\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustreaper.com\n23.2 yearsRegistered 2003-06-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustreaper.com\n23.2 yearsRegistered 2003-06-24\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustly.com\n12.4 yearsRegistered 2014-05-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustly.com\n12.4 yearsRegistered 2014-05-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette Casino\n\tcsgofast.com\n11.5 yearsRegistered 2015-03-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsteam-login.authtofast.com\n83 daysRegistered 2026-06-30\nRDAP ↗ · authtofast.com (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tduelbits.com\n6.6 yearsRegistered 2020-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nswitchflips.com\n6.4 yearsRegistered 2020-04-21\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opener\n\tfarmskins.com\n10.5 yearsRegistered 2016-03-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsteam.kobal.cc\n9.7 yearsRegistered 2017-01-07\nRDAP ↗ · kobal.cc (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgoluck.com\n9.3 yearsRegistered 2017-05-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgoluck.com\n9.3 yearsRegistered 2017-05-18\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tinsane.gg\n7.5 yearsRegistered 2019-04-02\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.insane.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcs2skin.com\n3.5 yearsRegistered 2023-03-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncs2skin.com\n3.5 yearsRegistered 2023-03-06\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tjuice.gg\n7.9 yearsRegistered 2018-10-19\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nletmeinjuice.com\n2.4 yearsRegistered 2024-04-15\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tggdrop.com\n8.6 yearsRegistered 2018-02-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nggauth.com\n3.4 yearsRegistered 2023-05-03\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Casino\n\thowl.gg\n9.5 yearsRegistered 2017-03-16\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhowl.uno\n41 daysRegistered 2026-08-11\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tchicken.gg\n5.7 yearsRegistered 2021-01-11\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nchicken.gg\n5.7 yearsRegistered 2021-01-11\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgocasino.gg\n2.6 yearsRegistered 2024-02-17\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.csgocasino.gg\n2.6 yearsRegistered 2024-02-17\nWHOISFREAKS ↗ · csgocasino.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Casino\n\thunt.gg\n6.9 yearsRegistered 2019-11-04\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.hunt.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Battles\n\tcsbattle.com\n9.8 yearsRegistered 2016-12-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsbattle.com\n9.8 yearsRegistered 2016-12-10\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskinrave.gg\n3.1 yearsRegistered 2023-08-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinrave.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsdouble.gg\n261 daysRegistered 2026-01-03\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsdouble.gg\n261 daysRegistered 2026-01-03\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustchance.com\n8.0 yearsRegistered 2018-10-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhgfuihd.com\n7.6 yearsRegistered 2019-01-27\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Automation\n\tcobaltlab.tech\n3.5 yearsRegistered 2023-03-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncobaltauth.com\n1.7 yearsRegistered 2025-01-07\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\traided.gg\n171 daysRegistered 2026-04-03\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.raided.gg\n171 daysRegistered 2026-04-03\nIP2WHOIS ↗ · raided.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustneo.gg\n1.3 yearsRegistered 2025-06-20\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustneo.gg\n1.3 yearsRegistered 2025-06-20\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tsplits.gg\n3.7 yearsRegistered 2023-01-23\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsplits.gg\n3.7 yearsRegistered 2023-01-23\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Upgrader\n\tupgrader.pro\n1.2 yearsRegistered 2025-07-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nupgauth.space\n38 daysRegistered 2026-08-14\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskin.fans\n8.2 yearsRegistered 2018-07-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skinfans.com\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\thotpizza.one\n1.8 yearsRegistered 2024-12-07\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhotpizza.one\n1.8 yearsRegistered 2024-12-07\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tg4skins.com\n10.1 yearsRegistered 2016-08-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.g4s.to\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2royal.com\n4.1 yearsRegistered 2022-08-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ntf2auth.com\n5.2 yearsRegistered 2021-07-27\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2hunt.com\n8.7 yearsRegistered 2018-01-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrstspcl.com\n6.1 yearsRegistered 2020-08-08\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2.bet/coinflip\n8.4 yearsRegistered 2018-05-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ntf2.bet\n8.4 yearsRegistered 2018-05-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\topenstars.gg\n131 daysRegistered 2026-05-13\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nopenstars.gg\n131 daysRegistered 2026-05-13\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tskins.com\n25.1 yearsRegistered 2001-08-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skins.com\n25.1 yearsRegistered 2001-08-08\nRDAP ↗ · skins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\twhite.market\n9.6 yearsRegistered 2017-03-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwhite.market\n9.6 yearsRegistered 2017-03-01\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tmoon.market\n7.6 yearsRegistered 2019-02-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmoon.market\n7.6 yearsRegistered 2019-02-27\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tcsfloat.com\n5.2 yearsRegistered 2021-07-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgofloat.com\n11.0 yearsRegistered 2015-09-29\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tskin.land\n4.7 yearsRegistered 2022-01-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skin.land\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\thaloskins.com\n2.8 yearsRegistered 2023-12-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhaloskins.com\n2.8 yearsRegistered 2023-12-10\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCorporate Market\n\tbuff.163.com\n29.0 yearsRegistered 1997-09-15\nRDAP ↗ · 163.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\nbuff.163.com\n29.0 yearsRegistered 1997-09-15\nRDAP ↗ · 163.com (parent)\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\tmarket.csgo.com\n26.6 yearsRegistered 2000-02-07\nRDAP ↗ · csgo.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\ndota2.net\n14.9 yearsRegistered 2011-10-29\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRegulated Market\n\tskinport.com\n8.0 yearsRegistered 2018-09-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinport.app\n6.3 yearsRegistered 2020-06-20\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMarketplace/Swap\n\tskinflow.gg\n3.8 yearsRegistered 2022-11-26\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinflow.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tskin.place\n6.0 yearsRegistered 2020-09-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skin.place\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tskinsmonkey.com\n5.7 yearsRegistered 2021-01-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinsmonkey.com\n5.7 yearsRegistered 2021-01-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCorporate Market\n\tskinbaron.de\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinbaron.com\n10.7 yearsRegistered 2015-12-22\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Market\n\trust.tm\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\ndota2.net\n14.9 yearsRegistered 2011-10-29\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tpirateswap.com\n6.0 yearsRegistered 2020-09-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nlogin.pirateswap.com\n6.0 yearsRegistered 2020-09-22\nRDAP ↗ · pirateswap.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Marketplace\n\tmannco.store\n8.6 yearsRegistered 2018-03-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmannco.store\n8.6 yearsRegistered 2018-03-02\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tskinswap.com\n9.9 yearsRegistered 2016-11-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinswap.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\texeskins.com\n2.1 yearsRegistered 2024-08-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nexeskins.com\n2.1 yearsRegistered 2024-08-14\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tbalticskins.com\n153 daysRegistered 2026-04-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nbalticskins.com\n153 daysRegistered 2026-04-21\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tcs.trade\n8.9 yearsRegistered 2017-11-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncs.trade\n8.9 yearsRegistered 2017-11-14\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\trapidskins.com\n4.5 yearsRegistered 2022-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.rapidskins.com\n4.5 yearsRegistered 2022-03-11\nRDAP ↗ · rapidskins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\ttradeit.gg\n9.1 yearsRegistered 2017-08-21\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nconnect-tradeit.com\n4.6 yearsRegistered 2022-02-23\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\t49skins.com\n3.4 yearsRegistered 2023-04-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.49skins.com\n3.4 yearsRegistered 2023-04-19\nRDAP ↗ · 49skins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tskinvault.gg\n3.4 yearsRegistered 2023-05-06\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinvault.gg\n3.4 yearsRegistered 2023-05-06\nIP2WHOIS ↗ · skinvault.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Trading\n\taim.market\n3.3 yearsRegistered 2023-05-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\naim.market\n3.3 yearsRegistered 2023-05-22\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Sell Portal\n\tskinout.gg\n5.6 yearsRegistered 2021-02-27\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skinout.gg\n5.6 yearsRegistered 2021-02-27\nIP2WHOIS ↗ · skinout.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Trading\n\tntskins.com\n230 daysRegistered 2026-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nntskins.com\n230 daysRegistered 2026-02-03\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Portal\n\tgamerpay.gg\n6.0 yearsRegistered 2020-10-02\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ngamerpay.gg\n6.0 yearsRegistered 2020-10-02\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Scrap Swap\n\tscrap.tf\n14.0 yearsRegistered 2012-09-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nscrap.tf\n14.0 yearsRegistered 2012-09-03\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Cashout\n\tmarketplace.tf\n14.0 yearsRegistered 2012-09-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmarketplace.tf\n14.0 yearsRegistered 2012-09-19\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Cashout\n\tskins.cash\n10.5 yearsRegistered 2016-03-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinscash.live\n6.8 yearsRegistered 2019-12-05\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgo.net\n14.2 yearsRegistered 2012-07-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncn2.easylot.net\n10.0 yearsRegistered 2016-09-03\nRDAP ↗ · easylot.net (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCommunity Hub\n\tcybershoke.net\n6.8 yearsRegistered 2019-11-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.cybershoke.net\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMatchmaker Hub\n\tfastcup.net\n14.6 yearsRegistered 2012-02-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.fastcup.net\n14.6 yearsRegistered 2012-02-16\nRDAP ↗ · fastcup.net (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Analytics\n\tleetify.com\n7.6 yearsRegistered 2019-03-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nleetify.com\n7.6 yearsRegistered 2019-03-01\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Analytics\n\tscope.gg\n7.8 yearsRegistered 2018-12-10\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nscope.gg\n7.8 yearsRegistered 2018-12-10\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tools\n\ttradeupspy.com\n6.5 yearsRegistered 2020-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.tradeupspy.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMarketplace\n\tcs.deals\n9.8 yearsRegistered 2016-12-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.cs.deals\n9.8 yearsRegistered 2016-12-03\nRDAP ↗ · cs.deals (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Price DB\n\tpricempire.com\n6.6 yearsRegistered 2020-01-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\npricempire.com\n6.6 yearsRegistered 2020-01-30\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Blackmarket\n\tFSB Market\n7.2 yearsRegistered 2019-07-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nFSB Market\n7.2 yearsRegistered 2019-07-27\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nReady-Account Hub\n\tz2u.com\n26.9 yearsRegistered 1999-11-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwww.z2u.com\n26.9 yearsRegistered 1999-11-10\nRDAP ↗ · z2u.com (parent)\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Gambling\n\tcsgoroll.com\n11.6 yearsRegistered 2015-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwww.csgoroll.com\nRegistry date unavailableRegistry date unavailable\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\trollbit.com\n11.9 yearsRegistered 2014-11-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrbsnin.com\n3 daysRegistered 2026-09-18\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nLicenced Casino\n\t500.casino\n5.9 yearsRegistered 2020-11-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette/Slots\n\tcsgobig.com\n11.4 yearsRegistered 2015-04-12\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcasedrop.com\n14.8 yearsRegistered 2011-12-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\tbanditcamp.com\n12.2 yearsRegistered 2014-06-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tskinbox.com\n18.8 yearsRegistered 2007-12-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\ttastydrop.com\n6.1 yearsRegistered 2020-08-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette Casino\n\tcsgopolygon.gg\n6.5 yearsRegistered 2020-03-28\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tmagicdrop.ru\n10.3 yearsRegistered 2016-05-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nDice Casino\n\tcsdice.com\n3.8 yearsRegistered 2022-11-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUpgrader Casino\n\tskinodds.com\n1.2 yearsRegistered 2025-06-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgowin.com\n12.0 yearsRegistered 2014-09-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrash Casino\n\tcsgorun.net\n7.3 yearsRegistered 2019-06-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\topenskins.com\n3.6 yearsRegistered 2023-02-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Gambling\n\trustbet.com\n7.6 yearsRegistered 2019-02-07\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgomagic.com\n9.4 yearsRegistered 2017-05-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUpgrader/Contract\n\tcsgobounty.com\n11.5 yearsRegistered 2015-03-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tezskins.com\n27.5 yearsRegistered 1999-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\trustcases.com\n7.2 yearsRegistered 2019-06-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgoreaper.com\n11.1 yearsRegistered 2015-08-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgocases.com\n12.3 yearsRegistered 2014-06-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Upgrader\n\tcsgo-skins.com\n11.2 yearsRegistered 2015-07-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgonet.com\n8.8 yearsRegistered 2017-12-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\twtfskins.com\n9.0 yearsRegistered 2017-10-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Casino\n\tflamecases.com\n10.0 yearsRegistered 2016-09-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tgamedom.com\n11.7 yearsRegistered 2015-01-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Battles\n\tskin.club\n9.0 yearsRegistered 2017-09-04\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsc-auth.net\n7.5 yearsRegistered 2019-04-02\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tdaddyskins.com\n9.9 yearsRegistered 2016-10-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Gambling\n\trustix.gg\n1.7 yearsRegistered 2025-01-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Upgrade\n\tskins.club\n4.2 yearsRegistered 2022-07-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgohouse.org\n146 daysRegistered 2026-04-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskinrave.net\n216 daysRegistered 2026-02-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tbloodycase.gg\n19 daysRegistered 2026-09-02\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nClicker/Upgrade\n\tcsgoclicker.com\n8.3 yearsRegistered 2018-05-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustbet.gg\n4.0 yearsRegistered 2022-09-30\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcs-drop.com\n262 daysRegistered 2026-01-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\thellstore.net\n11.7 yearsRegistered 2015-01-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustloot.com\n354 daysRegistered 2025-10-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgo-case.com\n10.3 yearsRegistered 2016-05-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgogem.com\n9.9 yearsRegistered 2016-10-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\trainbet.com\n8.8 yearsRegistered 2017-11-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nservices.rainbet.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustclash.com\n5.4 yearsRegistered 2021-05-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrash Casino\n\t12cs.fail\n181 daysRegistered 2026-03-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\twww.tf2easy.com\n6.3 yearsRegistered 2020-06-02\nRDAP ↗ · tf2easy.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2blaze.com\n7.6 yearsRegistered 2019-01-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tshuffle.com\n30.1 yearsRegistered 1996-07-31\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tbuff.market\n5.9 yearsRegistered 2020-10-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tavan.market\n8.3 yearsRegistered 2018-05-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Engine\n\tcs.money\n11.0 yearsRegistered 2015-09-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.dota.trade\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tuuskins.com\n2.6 yearsRegistered 2024-01-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Market\n\tyoupin898.com\n6.1 yearsRegistered 2020-08-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tc5game.com\n10.5 yearsRegistered 2016-03-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\twaxpeer.com\n7.3 yearsRegistered 2019-05-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwaxpeer.com\n7.3 yearsRegistered 2019-05-20\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBot Trading\n\tcs.money\n11.0 yearsRegistered 2015-09-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.dota.trade\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUS Marketplace\n\tdmarket.com\n30.2 yearsRegistered 1996-07-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nOfficial Market\n\tsteamcommunity.com/market\n20.3 yearsRegistered 2006-05-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNot an external login site2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Platform\n\tlootfarm.com\n11.9 yearsRegistered 2014-10-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Market\n\trustskins.com\n7.6 yearsRegistered 2019-01-31\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tkrakatoa.com\n26.4 yearsRegistered 2000-05-15\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\tshadowpay.com\n10.1 yearsRegistered 2016-08-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nChinese Powerhouse\n\tigxe.cn\n15.0 yearsRegistered 2011-09-06\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAutomated Swap\n\tswap.gg\n9.6 yearsRegistered 2017-01-29\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCash-out Portal\n\tbitskins.com\n11.2 yearsRegistered 2015-07-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Automation\n\ttf2mart.com\n1.1 yearsRegistered 2025-08-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Auctions\n\tskinbid.com\n10.2 yearsRegistered 2016-06-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Rental\n\tlootbear.com\n8.7 yearsRegistered 2018-01-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Valuation\n\tbackpack.tf\n14.4 yearsRegistered 2012-05-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Botnet\n\tstntrading.eu\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Cashout\n\tskinwallet.com\n18.0 yearsRegistered 2008-09-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nDota 2 Market\n\tdota2market.com\n12.2 yearsRegistered 2014-07-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nServer Network\n\txplay.gg\n5.3 yearsRegistered 2021-06-13\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMatchmaking Portal\n\tesportal.com\n26.8 yearsRegistered 1999-12-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nLATAM Hub\n\tgamersclub.com.br\n11.2 yearsRegistered 2015-06-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tools\n\tepidemic.gg\n4.9 yearsRegistered 2021-11-03\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tcs2stash.com\n3.5 yearsRegistered 2023-03-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tcsgoskins.gg\n6.8 yearsRegistered 2019-12-21\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tsteamanalyst.com\n12.6 yearsRegistered 2014-02-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Exchange\n\tsteamcardexchange.net\n13.3 yearsRegistered 2013-05-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tracker\n\tdotabuff.com\n14.2 yearsRegistered 2012-06-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tracker\n\ttracker.gg\n8.9 yearsRegistered 2017-10-12\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Exchange\n\tfunpay.com\n17.0 yearsRegistered 2009-09-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nGrey Market\n\tplayerauctions.com\n26.3 yearsRegistered 2000-06-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Portal\n\teldorado.gg\n8.0 yearsRegistered 2018-09-12\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Key Market\n\tg2a.com\n24.8 yearsRegistered 2001-12-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Key Market\n\tkinguin.net\n16.8 yearsRegistered 2009-12-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nVirtual Services\n\tg2g.com\n31.1 yearsRegistered 1995-08-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Broker\n\tplayerup.com\n19.3 yearsRegistered 2007-05-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfhub.net\n2.7 yearsRegistered 2023-12-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfaccounts.com\n5.3 yearsRegistered 2021-05-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Shop\n\tbuycsgorank.com\n6.2 yearsRegistered 2020-07-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tcsgosmurfkings.com\n9.3 yearsRegistered 2017-06-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfstore.co\n8.6 yearsRegistered 2018-03-03\nWHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlvlup.com\n9.9 yearsRegistered 2016-11-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlevels.com\n10.6 yearsRegistered 2016-02-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tlevelsteam.com\n79 daysRegistered 2026-07-04\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlevelu.com\n6.0 yearsRegistered 2020-09-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\teloking.com\n12.2 yearsRegistered 2014-07-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\tboosteria.org\n11.9 yearsRegistered 2014-10-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tovergear.com\n14.4 yearsRegistered 2012-04-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tblazingboost.com\n14.2 yearsRegistered 2012-06-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\tdota2boost.com\n2.9 yearsRegistered 2023-10-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tbuyboost.com\n22.4 yearsRegistered 2004-04-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n调查的论点选定规则／分析与评注+\n举证责任\n\n此次调查揭示了商业用途限制与本文所记录的服务之间存在的差距。在认定某项行为构成违约之前，应先对每项活动进行分类，并确认是否存在明确许可。社区市场的费用并不适用于所有对外交易。\n\n什么是带标签的记录，什么不是\n\n当档案中包含一份注明日期的观察记录，且该记录表明该平台表面上符合该条款规定时，该记录即会被标记。该标记并不构成已裁定的违规行为，且该记录中未针对此处列出的任何平台出具明确的 Valve 许可。若平台持有相关授权，公布该授权即可解决该条目。\n\n来源与方法估计值、定义与范围+\n\n上述计数指所选规则。记录类型将每个平台归为一组；完整的标签会在平台详情中显示。搜索和筛选功能仅在该规则范围内生效。 注册日期来自已保存的 RDAP / WHOIS 快照。子域使用父域的创建日期。仅凭注册时间无法证明持续运行或认证路径。当前认证主机名来自已保存的 OpenID 请求，并带有 UTC 时间戳；未解析的检查不会复用旧标签。观察器在 Steam 登录之前停止，且不测试 Steam 链接过滤器的状态。 下载航线观测数据 ↗ 下载注册表结果 ↗\n\n浏览源代码存档 ↗\n附录 G — 从模板拒绝到底层记录\nDSAR 操作指南：索取证据\n\n依据《通用数据保护条例》（GDPR）第15条，可请求获取与API密钥创建、账户恢复及技术支持访问相关的个人数据。保留的记录可用于核查操作发起者以及平台所依据的依据。\n\n01\n保留您的时间线。\n\n请保存账户通知、凭证、交易编号及日期（以UTC为基准）。确保账户安全，并查看适用于该游戏和交易的恢复选项。\n\nSteam 贸易保护信息 ↗\n02\n申请获取您的保留数据。\n\n请索取时间戳、源IP地址、密钥生命周期事件、安全确认信息以及与账户相关的恢复操作。若相关数据涉及您，请一并提供支持访问事件及接收方信息。\n\n03\n请保留送货记录。\n\n请通过 Valve 的隐私事务联系渠道进行咨询。通常的回复期限为一个月；如需延长，最长可延长两个月，但必须在第一个月内说明延长的理由。\n\nValve 隐私联系途径 ↗ 已归档 2026-09-21 ↗\n04\n比较这些回答。\n\n将日志与时间线进行核对。询问遗漏的原因，必要时通过向主管机关投诉的途径解决。将收到的回复原样保留。\n\n适用范围 / 第15条\n\n访问权限涵盖保留的个人数据，包括日志中的数据。但并不保证能获取所有内部文件、重建的记录或未经编辑的涉及他人的数据。请索取一份清晰易懂的副本，并了解任何限制措施的依据。\n\n欧洲数据保护委员会（EDPB）访问指南，第2、4至6节 ↗ ·《通用数据保护条例》（GDPR）第12条、第15条、第77条 ↗ 已存档 2026-09-20 ↗\n\n数据主体访问请求《通用数据保护条例》（GDPR）/ 第15条\n账户安全与访问记录\n\n提交前请替换方括号中的字段。\n\nTo: Valve Privacy Team\nSubject: Article 15 GDPR request — account security records\n\nAccount / SteamID: [YOUR ACCOUNT IDENTIFIER]\nRelevant period (UTC): [START] to [END]\nRelated support tickets: [TICKET REFERENCES]\n\nI request a copy of the personal data concerning me that you retain for this period, including:\n\n1. API-key registration, confirmation, use and revocation events, with available timestamps, source IP addresses, registered domains, device or user-agent information and non-secret key identifiers.\n\n2. Recorded account-recovery actions, password/email/phone changes, Steam Guard removals or resets, confirmation events and the account-related evidence relied on to authorize those actions.\n\n3. Personal data in support-access and administrative-action logs concerning my account, including available dates, purposes, actions and the support entity involved, subject to applicable rights of others.\n\n4. Account-related records used to determine any sanction, and available records of my complaints, reviews and responses.\n\nPlease also provide the applicable processing purposes, categories, recipients, retention periods or criteria, and available information about sources where data were not obtained from me.\n\nWhere processing relies on my consent, please provide the retained record of the consent relied upon and the wording presented at that time.\n\nPlease provide an intelligible electronic copy with time zones and field definitions. Please do not include active credentials or secret tokens. If any requested data are not held, please say so. For any withheld data, please identify the scope and legal basis of the restriction and provide the remainder.\n\nPlease acknowledge receipt and respond within the applicable Article 12 period, explaining any necessary extension. I also ask you to preserve relevant existing records while this request is handled.\n\nName: [YOUR NAME]\nDate: [DATE]\n数据中心IP能实现什么\n差异是需要调查的证据。\n\n源自数据中心网络的API密钥请求——如本调查中提到的托管服务提供商案例——在与登录记录、确认信息及用户时间线进行比对时，可能具有相关性。 仅凭IP地址无法识别行为主体，也无法自动突破所有防御措施。若有证据表明恶意行为主体提供了记录在案的同意，则可能对该同意的可信度提出质疑；其他法律依据和责任问题则需要另行分析。\n\n查看已存档的禁令及GDPR投诉 →\n附录 H — “Wayback Machine” 存档分析 · 已发布的支持统计数据\n支持量。已公布的响应时间。\n上下文与来源限制\n\nValve 每天在以下位置发布支持统计数据：store.steampowered.com/stats/support. “互联网档案馆”（Wayback Machine）保存了该页面从2018年至2026年的历史快照。这些数据所反映的工作量与人员数量之比，与在公布的响应时间内按每张工单进行人工审核的情况不相符。\n\n比较Valve在各保存快照中的存档支持数据。该方法论解释了这些数据能够衡量什么以及无法衡量什么。\n\n业务量与公布响应时间的对比（2018 → 2026）\n一个支持服务台有两条等候队列，共涉及21张存档截图。\n\nValve 在以下网址公布实时支持数据：store.steampowered.com/stats/support. 以下每个数据点都是互联网档案馆在捕获该页面当日，该页面上显示的下限 Valve 本身——并非我们的估算值。这两个数列的测量单位相同，因此应绘制在同一坐标轴上，并可直接相互对照。\n\n退款申请 — 资金 Valve 持有账户安全与恢复 — 你丢失的账户\n0 h\n2 h\n4 h\n6 h\n8 h\n10 h\nno captures · 38 months\n2019\n2020\n2021\n2022\n2023\n2024\n2025\n2026\n8 h 44 m\naccount recovery\n52 m\nrefunds\n15 m — one capture only\n49–55 分钟2018年2月至2026年8月期间，每次捕获中的退款下限。在这八年半的时间里，该下限的变动幅度不足六分钟，而每日退款量则增长了九倍。\n2.4 小时 → 8.7 小时截至2022年12月，除一次数据采集外，每次数据采集中的账户恢复下限均接近2.4小时。在2026年的三次数据采集中，Valve分别公布了10.9小时、5.8小时和8.7小时的数据。\n×2.8 → ×13根据Valve自己公布的数据，退款速度比退税慢了多少。这一差距在五年内保持稳定，随后逐渐扩大——变慢的那条队列是指用户（而非Valve）需要自掏腰包的那条。\n\n来源：Wayback Machine 捕获的 21 个版本store.steampowered.com/stats/support, 2018-02-03 至 2026-08-10；提取在VALVE_EVIDENCE_PACK/databases/steam_support_stats_history.json. 结合图表中的数据阅读这些限值：该图表绘制了较低 该范围的上限为 Valve 次打印。已公布的上限在两条数据线上都更差——退款时间在 1.5 小时至 1.5 天之间，恢复时间在 7.0 小时至 3.6 天之间。 同一 Valve 页面的两个截图被归档在本地化版本中——2018-11-03 为捷克语版，2020-03-25 为法语版——并在表格中标记为 (cs) 和 (fr)； 此处显示的数据已将单位名称翻译为相应语言，数值则按已发表形式呈现，而原始源字符串仍保存在提取文件中。 每次捕获数据均公布了两个队列的响应时间，且两条曲线上的数据点均未进行插值。图表中标出了唯一的15分钟恢复时间数据2020-10-21并予以保留：该数据仅出现在一次捕获中，且其他捕获数据与其相差一个数量级以上。 在 2022-12-08 和 2026-02-01 之间不存在任何捕获数据；记录中这 38 个月的空白区域已用阴影标出，且未在其上绘制任何线条。 这些数据描述的是已公布的响应时间。它们并未显示工单内部的处理情况，且 Valve 未公布任何可供对照的人员编制数据。\n\n将每个截图以表格形式打开\n每张已存档的截图，均按发布时的原样呈现\n捕获\t每日退款\t退款回复\t每日恢复量\t恢复响应\n2018-02-03\t98,788\t50.12分钟至1.52小时\t25,662\t2.51 小时至 1.80 天\n2018-05-07\t60,494\t53.83分钟至1.47天\t24,226\t2.45小时至2.22天\n2018-08-02\t69,084\t50.27分钟至1.59小时\t28,953\t2.44 小时至 22.17 小时\n2018-11-03 (cs)\t63,410\t49.28 分钟至 1.54 小时\t33,910\t2.42 小时至 1.31 天\n2019-02-01\t76,305\t50.13分钟至1.52小时\t35,164\t2.44 小时至 2.04 天\n2019-05-18\t78,951\t51.03分钟至3.12小时\t27,514\t2.46小时至20.39小时\n2019-09-07\t78,941\t50.65分钟至1.66小时\t28,812\t2.42 小时至 13.59 小时\n2019-12-13\t69,589\t50.77分钟至1.55小时\t25,322\t2.45小时至1.13天\n2020-03-25 (法语)\t139,278\t49.45分钟至1.53小时\t32,302\t2.48 小时至 3.62 天\n2020-06-26\t278,504\t48.98分钟至2.29小时\t20,343\t2.39 小时至 6.99 小时\n2020-10-21\t107,633\t50.80分钟至1.54小时\t20,688\t15.33分钟至8.62小时\n2021-03-20\t158,956\t50.80分钟至1.64小时\t25,760\t2.34 小时至 11.62 小时\n2021-06-26\t547,907\t51.93分钟至6.73小时\t29,728\t2.40 小时至 15.63 小时\n2021-10-10\t170,103\t51.88分钟至3.25小时\t23,989\t2.39 小时至 13.05 小时\n2022-01-31\t354,386\t53.65分钟至8.09小时\t24,391\t2.42 小时至 15.29 小时\n2022-05-09\t172,555\t51.83 分钟至 1.65 小时\t23,289\t2.41 小时至 16.90 小时\n2022-09-05\t153,453\t53.67分钟至4.15小时\t23,594\t2.45 小时至 1.22 天\n2022-12-08\t181,075\t54.83 分钟至 6.67 小时\t27,111\t2.46 小时至 18.89 小时\n2026-02-01\t317,762\t50.30分钟至1.52小时\t47,197\t10.91小时至21.30小时\n2026-05-09\t246,776\t50.12分钟至1.52小时\t35,264\t5.81小时至15.60小时\n2026-08-10\t373,244\t52.05 分钟至 2.07 小时\t45,319\t8.73 小时至 16.52 小时\n主要观察结果：\n横向21 个 Wayback 存档 在 2018-02-03 到 2026-08-10 期间，每日退款申请数量在60,494 （2018年5月）至547,907 （2021年6月）——a9.1× 点差. 2026年的数值为 373,244（与2018年2月的数据相比为+278%）。\n在这同一时期的九年里，已公布的退款响应时间下限从未低于49–55分钟 带：总移动时间不到六分钟，而其背后的工作量却增加了九倍。\n如果一个人每张票据只花5秒钟阅读，那么每天处理373,244张票据（当前数量）将耗时22名代理全天候24小时不间断工作 仅仅是为了打开和关闭它们；在高峰期（547,907，2021年6月），这一数字上升至32。\n如果公布的响应时间反映的是每张工单的处理时间（约52分钟/张），则由此推算出的并发处理人员数量大约为13,500 名代理 当前规模为，峰值时约为 0。未找到关于 1 的支持人员数量的来源数据；此处未作假设。\n接下来：在已公布的响应时间内，处理量与人员数量的比例与“每张工单均由人工审核”的情况不符。这些数据与“第一轮审核主要由自动化系统完成”的情况相符；但具体有多少比例的工单经过人工审核，这一数据并未公布。\n这对符合《通用数据保护条例》（GDPR）为何重要\n\n《通用数据保护条例》（GDPR）第22条禁止仅通过自动化方式对个人作出产生重大法律后果的决策，且未规定用户有权要求人工复核。 如果 Steam 支持决策（工单关闭、账户操作、拒绝数据请求）完全由自动化脚本作出，那么每一项“对用户产生重大影响”的此类决策都可能违反第22条。\n\n门票HT-2YBP-F7JP-D4VB （第18节）在三天后被关闭，仅附有模板化的转交说明，且未对所援引的法律依据进行任何说明。无法从该工单中确定是否有人对其进行了审查；这是一个监督机构可根据第22条和第15条第1款(h)项向Valve提出的问题。\n\n来源：Wayback Machine 对 store.steampowered.com/stats/support 的快照（2018-02-03、2021-06-26、 2026-08-10）——数据已提取至 VALVE_EVIDENCE_PACK/databases/steam_support_stats_history.json（21 个快照，2018–2026 年）。 注：响应时间“~52 分钟”是退款类别的下限；在同一批快照中，账户安全响应时间为 2.4–16.5 小时。 2021-06-26 代表历史峰值（547,907 退款请求），而非单调变化的中点——2020–2021 年间请求量激增约 6 倍，随后部分回落，最终于 2026 年回升至 37.3 万。\n附录一——数据集范围 · 可重现的计数结果\n统计记录数。检查范围。\n上下文与来源限制\n\n先统计记录数，再验证这些说法：下文中的每个数据均可从已发布的文件中重新推导出来。\n\n检查底层数据集，复现计数结果，并区分源行与独立事件。\n\n主CSV文件包含40,448 行. 其中，36,516 来自 Discord-AntiScam 钓鱼信息源。其余的3,932 这些内容涵盖 GitHub、代码审查、搜索结果、论坛帖子及其他来源，为已报告的社区话题和安全报告提供了全面的索引。\n\n在该 CSV 文件中，有 1,690 行被归类到“未修复的安全漏洞”集合标签下，代表历史上的用户问题和漏洞披露。追踪这些报告需要审查每个线程的具体构建时间线和公开补丁历史。\n\n该 16,319-record 可搜索存档是一个独立的、经过精心整理的版本，拥有自己的清单，旨在对特定的用户申诉和事件报告进行精准的本地探索。\n\n为了建立可靠的审计轨迹，必须根据记录在案的构建时间线和历史补丁日志，对用户报告的每条记录进行核验。\n\n单独的第二部分藏品记录231,829 个唯一商品编号，其中包括自动化注册类别的 33,509 以及被标记为“未验证转账”的 198,320。 输入文件的 SHA-256 值与保存的测量结果一致。这些计数反映的是上架尝试和观察到的转账情况，而非最终交易金额或已核实的盗窃总额，这凸显了需要借助主要平台记录来衡量确切经济影响的必要性。列出度量和哈希值 ↗\n\n掌握 CSV ↗ ·可搜索的存档清单 ↗ ·检查源记录 ↗\n\n附录 J — 关于本次调查\nValve 未公布任何执法记录。 我们造了一个。\n\n独立。非商业性质。仅基于公开数据构建。已提交给监管机构。\n\n88.97%自动驾驶车队未受影响——没有任何形式的禁令\n67.77%0名经判决的诈骗犯逍遥法外\n$26.8M+非限量车队在门店的消费下限\n3.6%被 Valve 的链接过滤器屏蔽的赌博网站域名\n8年已记录的安全事件\n\n这是什么。 一份关于Valve公司Steam平台的取证报告——涵盖其执法记录、卡片农场经济、法律框架，以及博彩运营商通过Steam自有OpenID中继使用的身份验证基础设施。 所有数据均可从两个来源复现：Valve自身的公开API以及随本次调查一并发布的数据集。\n\n适用对象。 对Valve拥有管辖权的监管机构——荷兰的《通用数据保护条例》（GDPR）监督机构、美国金融犯罪执法局（FinCEN）、美国证券交易委员会（SEC）、《数字服务法》（DSA）数字服务协调员、波兰消费者保护局（UOKiK），以及任何调查与Steam相关资金流向的执法机构。 此外，还包括记者、研究人员以及所有遭遇永久封号、退款申请被拒或游戏内物品被盗，且被告知无法申诉的用户。\n\n唯一的要求。 Valve 以完全保真的方式保存了这些数据——附有封禁理由、完整的ID空间，且实时更新。它能在几秒钟内处理该档案中的所有查询，但选择不公开其中任何内容。对于任何有权限的机构而言，问题很简单：为什么不呢？\n\n作者并未声称什么。 在此项工作中，没有任何第三方平台完成对 Steam 的登录。提供的 OpenID URL 仅确定了请求参数，并不代表登录已完成。单独注册的域名本身并不能作为规避行为的证据。 注册日期仅是主机首次可能出现在 OpenID 请求中的下限；它们并不能证明该主机被持续使用。 作者并未断言 Valve 知晓或意图何事：关于 Valve 的每一项陈述均与一份带日期的公开文件或带日期的观察记录相关联。若某项主张无法通过源文件佐证，则已予以删除。\n\n关于我们\n\nPhishDestroy — 独立调查人员。与Valve公司或本文中提及的任何平台均无隶属关系。其中一个Steam账户仅用于记录第18节中的GDPR请求。\n\n法律免责声明\n\n非商业性、去中心化的公益调查。所有数据均“按原样”提供，不作任何保证。本报告不构成司法裁决。\n\n公有领域\n许可\n\n所有权利均归全人类所有。可复制、改编、发布——无需署名。OFAC管辖区域内禁止访问。 完整许可协议与免责声明 →",
        "headings": [
          {
            "level": 2,
            "id": "briefing-heading",
            "text": "这项规则。这项纪录。这些未解之谜。"
          },
          {
            "level": 2,
            "id": null,
            "text": "致华盛顿州博彩委员会的公开信"
          },
          {
            "level": 3,
            "id": "wsgc-public-address-title",
            "text": "十天变成了十年。重新打开该记录。"
          },
          {
            "level": 2,
            "id": null,
            "text": "该网站被屏蔽了，但登录路由未被屏蔽。"
          },
          {
            "level": 3,
            "id": null,
            "text": "图3.1 — 两条路线的示意图。"
          },
          {
            "level": 3,
            "id": null,
            "text": "“全局陷阱”：链接过滤只是合规作秀，而非防护盾"
          },
          {
            "level": 3,
            "id": null,
            "text": "如果主域名被封锁，而认证主机未被封锁，登录路径就会保持开放——而且这种状态会持续数年之久。"
          },
          {
            "level": 3,
            "id": null,
            "text": "背景：什么是 Steam 以及它为何在此处重要"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve 做了什么：域名屏蔽"
          },
          {
            "level": 3,
            "id": null,
            "text": "什么是代理域名"
          },
          {
            "level": 3,
            "id": null,
            "text": "关键点：每次请求中都会将认证主机发送至 Steam"
          },
          {
            "level": 3,
            "id": null,
            "text": "这证明了什么"
          },
          {
            "level": 3,
            "id": null,
            "text": "在 Steam 中，Valve 的列表是唯一的列表。"
          },
          {
            "level": 3,
            "id": null,
            "text": "链路过滤保护旁路"
          },
          {
            "level": 3,
            "id": null,
            "text": "Big Picture 网页浏览器泄露登录 Cookie 并暴露敏感信息（可能导致账户被劫持）"
          },
          {
            "level": 3,
            "id": null,
            "text": "这对安装了杀毒软件的未成年人意味着什么"
          },
          {
            "level": 3,
            "id": null,
            "text": "域名的注册时间。观测日期。"
          },
          {
            "level": 2,
            "id": null,
            "text": "一个端点已关闭。公共追踪丢失了一把密钥。"
          },
          {
            "level": 3,
            "id": null,
            "text": "停电前时代"
          },
          {
            "level": 3,
            "id": null,
            "text": "变更后"
          },
          {
            "level": 2,
            "id": null,
            "text": "一个会话。比用户所见的访问权限更多。"
          },
          {
            "level": 3,
            "id": null,
            "text": "1. 增强型身份验证不足"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. 未遵循最小权限原则"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. 会话管理故障"
          },
          {
            "level": 3,
            "id": null,
            "text": "4. 从技术上讲，对认证主机的域级封锁是可行的"
          },
          {
            "level": 3,
            "id": "integration-paradox-title",
            "text": "Valve 每天都会根据这些规则进行编译。但这次它并未按照这些规则进行编译。"
          },
          {
            "level": 4,
            "id": null,
            "text": "GitHub 细粒度作用域与 Valve Steam Web API 的对比"
          },
          {
            "level": 2,
            "id": null,
            "text": "交互式漏洞利用与劫持模拟器"
          },
          {
            "level": 2,
            "id": null,
            "text": "该序列背后的端点。简体中文（大陆）"
          },
          {
            "level": 2,
            "id": null,
            "text": "一个被勾选的复选框。是谁操作的？"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve是如何最终消除“贸易替代”现象的——以及为何花了7年时间才通过各种变通措施实现"
          },
          {
            "level": 4,
            "id": null,
            "text": "头像与昵称刷新时间（2024年2月）"
          },
          {
            "level": 4,
            "id": null,
            "text": "7天CS2交易反转（2025年7月）"
          },
          {
            "level": 4,
            "id": null,
            "text": "API 强制实施移动推送功能（2023年12月）"
          },
          {
            "level": 4,
            "id": null,
            "text": "账户使用时长与名称横幅（2022–2024）"
          },
          {
            "level": 2,
            "id": null,
            "text": "他们的规则手册。记录在案的平台。"
          },
          {
            "level": 3,
            "id": "enforcement-focus-title",
            "text": "一套规则。执行不一。"
          },
          {
            "level": 4,
            "id": null,
            "text": "自动化"
          },
          {
            "level": 4,
            "id": null,
            "text": "商业用途"
          },
          {
            "level": 4,
            "id": null,
            "text": "VPN 与位置伪装"
          },
          {
            "level": 4,
            "id": null,
            "text": "链接混淆"
          },
          {
            "level": 4,
            "id": null,
            "text": "当支持团队关闭工单时，由谁来审核该决定？"
          },
          {
            "level": 2,
            "id": null,
            "text": "一个自动化 API。一条禁止自动化的规则。"
          },
          {
            "level": 3,
            "id": null,
            "text": "“游戏开发者”谬论"
          },
          {
            "level": 4,
            "id": null,
            "text": "自动化悖论"
          },
          {
            "level": 4,
            "id": null,
            "text": "贸易流程中的服务器端角色"
          },
          {
            "level": 2,
            "id": null,
            "text": "要求十天。却要花十年来交代。"
          },
          {
            "level": 3,
            "id": "letter-company",
            "text": "VALVE 公司"
          },
          {
            "level": 3,
            "id": null,
            "text": "十天。那接下来呢？"
          },
          {
            "level": 3,
            "id": null,
            "text": "遵循声明的返回主机。"
          },
          {
            "level": 3,
            "id": "washington-record-heading",
            "text": "两个截止日期。一个尚未明确的执法标准。"
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve 给予赌博网站10天时间"
          },
          {
            "level": 4,
            "id": null,
            "text": "华盛顿施压 Valve"
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve 驳回该指控"
          },
          {
            "level": 4,
            "id": null,
            "text": "2026年9月观察到的航线"
          },
          {
            "level": 4,
            "id": null,
            "text": "在Valve作出回复十八个月后，监管机构仍将其视为一种意图。"
          },
          {
            "level": 3,
            "id": null,
            "text": "“10天通知”十年：对23个指定地点的法证生存审计"
          },
          {
            "level": 4,
            "id": null,
            "text": "从10天预警到离岸集团：数十亿美元的资金周转"
          },
          {
            "level": 2,
            "id": null,
            "text": "主机名已经包含在请求中了。"
          },
          {
            "level": 3,
            "id": null,
            "text": "有据可查且已报告的先例"
          },
          {
            "level": 3,
            "id": null,
            "text": "注册日期能反映什么、不能反映什么"
          },
          {
            "level": 3,
            "id": null,
            "text": "比较审计：API合规标准"
          },
          {
            "level": 2,
            "id": "market-thesis-heading",
            "text": "0以外的价格缺口"
          },
          {
            "level": 2,
            "id": null,
            "text": "价格差距是可以量化的。"
          },
          {
            "level": 3,
            "id": null,
            "text": "这一数字反映了什么"
          },
          {
            "level": 3,
            "id": null,
            "text": "许多场地的标价都高于 Steam。"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam 在报价数量上仍居首位。"
          },
          {
            "level": 3,
            "id": null,
            "text": "商业生态系统显而易见。"
          },
          {
            "level": 2,
            "id": null,
            "text": "谁可以重置安全保护措施？"
          },
          {
            "level": 3,
            "id": null,
            "text": "一张导致该账户安全功能失效的恢复凭证，以及一笔报告的 $10,000 损失"
          },
          {
            "level": 3,
            "id": null,
            "text": "超越库存。"
          },
          {
            "level": 3,
            "id": "theft-ledger-title",
            "text": "Valve 两次推开了那扇门，相隔三十三个月。门从未关上过。"
          },
          {
            "level": 4,
            "id": null,
            "text": "账簿所显示的，是任何单个案例都无法体现的。Simplified Chinese (Mainland)"
          },
          {
            "level": 3,
            "id": null,
            "text": "保密性必须伴随着技术上的问责制。"
          },
          {
            "level": 2,
            "id": null,
            "text": "追踪资金流向。将交易分拆。"
          },
          {
            "level": 3,
            "id": null,
            "text": "资金实际流动的地方。"
          },
          {
            "level": 3,
            "id": null,
            "text": "先对活动进行分类，再对义务进行分类。"
          },
          {
            "level": 3,
            "id": null,
            "text": "追踪资金流向、信息及协助情况。"
          },
          {
            "level": 2,
            "id": null,
            "text": "《数字服务法》：将相关信息载入记录"
          },
          {
            "level": 3,
            "id": null,
            "text": "一项为期十天的要求。"
          },
          {
            "level": 3,
            "id": null,
            "text": "DSA时间窗口。"
          },
          {
            "level": 3,
            "id": null,
            "text": "“Duration”需要一条通知记录。"
          },
          {
            "level": 3,
            "id": null,
            "text": "全球年营业额的"
          },
          {
            "level": 2,
            "id": null,
            "text": "未成年人：a Steam 登录不属于年龄验证"
          },
          {
            "level": 3,
            "id": null,
            "text": "确定运算符和数据。"
          },
          {
            "level": 3,
            "id": null,
            "text": "记录从登录到存款的全过程。"
          },
          {
            "level": 2,
            "id": null,
            "text": "请求。响应。缺失的比较。"
          },
          {
            "level": 3,
            "id": null,
            "text": "这些记录确实存在；但数据主体并未收到这些记录。"
          },
          {
            "level": 2,
            "id": null,
            "text": "与该平台自身架构相悖的订阅协议"
          },
          {
            "level": 3,
            "id": null,
            "text": "市场上限与商业用途禁令"
          },
          {
            "level": 3,
            "id": null,
            "text": "API密钥漏洞是一个平台设计问题，而非用户疏忽所致"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve 在每次登录时都会接收认证主机名"
          },
          {
            "level": 3,
            "id": null,
            "text": "存档投诉中的规律"
          },
          {
            "level": 3,
            "id": null,
            "text": "法院在审查本案卷宗时，不会孤立地解读《社会保障法》。"
          },
          {
            "level": 2,
            "id": null,
            "text": "调查结果。我们要求的记录。"
          },
          {
            "level": 2,
            "id": null,
            "text": "证据备忘录——由来源1提供的材料"
          },
          {
            "level": 2,
            "id": null,
            "text": "生成的PDF文件中的遮盖仅是表面处理：被遮盖的文本仍可被提取"
          },
          {
            "level": 2,
            "id": null,
            "text": "赡养费及法律信函附件"
          },
          {
            "level": 2,
            "id": null,
            "text": "精选原始记录"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-01",
            "text": "2016年申请的硬件密钥"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-02",
            "text": "没有有效退出机制的崩溃报告"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-03",
            "text": "已向 Valve 报告了 Auth-ticket 滥用情况"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-01",
            "text": "44笔有争议的市场采购"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-02",
            "text": "永久封号及上诉通道关闭"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-03",
            "text": "恢复重置及报告的 $10,000 损失"
          },
          {
            "level": 2,
            "id": null,
            "text": "ArchiSteamFarm 以及自动化条款"
          },
          {
            "level": 2,
            "id": null,
            "text": "Rules ledger: clauses against recorded platforms"
          },
          {
            "level": 3,
            "id": "ledger-title",
            "text": "商业用途与账户扣费"
          },
          {
            "level": 3,
            "id": "lw-register-title",
            "text": "平台注册 175"
          },
          {
            "level": 4,
            "id": null,
            "text": "举证责任"
          },
          {
            "level": 4,
            "id": null,
            "text": "什么是带标签的记录，什么不是"
          },
          {
            "level": 2,
            "id": null,
            "text": "DSAR 操作指南：索取证据"
          },
          {
            "level": 3,
            "id": null,
            "text": "保留您的时间线。"
          },
          {
            "level": 3,
            "id": null,
            "text": "申请获取您的保留数据。"
          },
          {
            "level": 3,
            "id": null,
            "text": "请保留送货记录。"
          },
          {
            "level": 3,
            "id": null,
            "text": "比较这些回答。"
          },
          {
            "level": 3,
            "id": null,
            "text": "账户安全与访问记录"
          },
          {
            "level": 3,
            "id": null,
            "text": "差异是需要调查的证据。"
          },
          {
            "level": 2,
            "id": null,
            "text": "支持量。已公布的响应时间。"
          },
          {
            "level": 3,
            "id": null,
            "text": "一个支持服务台有两条等候队列，共涉及21张存档截图。"
          },
          {
            "level": 2,
            "id": null,
            "text": "统计记录数。检查范围。"
          },
          {
            "level": 2,
            "id": null,
            "text": "Valve 未公布任何执法记录。\n我们造了一个。"
          }
        ],
        "links": [
          "https://dotesports.com/counter-strike/news/csgo-lounge-billion-bets-3896",
          "https://store.steampowered.com/agreement/?l=english",
          "http://web.archive.org/web/20260921022032/https://store.steampowered.com/agreement/?l=english",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-all-results.json",
          "https://blog.counter-strike.net/expresstrade/",
          "http://web.archive.org/web/20260307161538/https://blog.counter-strike.net/expresstrade/",
          "https://wsgc.wa.gov/news/2016/washington-state-gambling-commission-orders-valve-stop-skins-gambling",
          "http://web.archive.org/web/20260520012601/https://wsgc.wa.gov/news/2016/washington-state-gambling-commission-orders-valve-stop-skins-gambling",
          "https://fr.scribd.com/document/328063293/Valve-s-Oct-18th-response-to-Washington-State-Gambling-Commission-s-cease-and-desist",
          "https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921021947/https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921022628/https://steamcommunity.com/linkfilter/?url=https:%2F%2Frollbit.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rbsnin.com.20260921T021120Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rollbit.com.json",
          "http://web.archive.org/web/20260921022740/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fskin.club",
          "http://web.archive.org/web/20260921022842/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fsc-auth.net",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skin.club.json",
          "http://web.archive.org/web/20260921022603/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fhowl.gg",
          "http://web.archive.org/web/20260921022636/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fhowl.uno",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/howl.gg.json",
          "http://web.archive.org/web/20260921022840/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fduelbits.com",
          "http://web.archive.org/web/20260921022901/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fswitchflips.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/duelbits.com.json",
          "http://web.archive.org/web/20260921022758/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgofast.com",
          "http://web.archive.org/web/20260921022847/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fauthtofast.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgofast.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/farmskins.com.20260921T025840Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/steam.kobal.cc.20260921T025844Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/farmskins.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cobaltlab.tech.20260921T041604Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cobaltauth.com.20260921T041608Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/cobaltlab.tech.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgo.net.20260921T041619Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cn2.easylot.net.20260921T041623Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgo.net.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/ggdrop.com.20260921T041637Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/ggauth.com.20260921T041641Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/ggdrop.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rustchance.com.20260921T041703Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/hgfuihd.com.20260921T041706Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rustchance.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skin.fans.20260921T041710Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.skinfans.com.20260921T041713Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skin.fans.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinport.com.20260921T041724Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinport.app.20260921T041728Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skinport.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skins.cash.20260921T041731Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinscash.live.20260921T041735Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skins.cash.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2hunt.com.20260921T041739Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rstspcl.com.20260921T041742Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tf2hunt.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgogem.com.20260922T192355Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/api.csgem.com.20260922T192358Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-2026-09-22.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/gamdom.com.20260922T192326Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/login.gambldom.com.20260922T192330Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/12cs.fail.20260922T192347Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/fail.games.20260922T192351Z.html",
          "http://web.archive.org/web/20260921022953/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgoempire.com",
          "http://web.archive.org/web/20260921022947/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgoempirelogin4.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgoempire.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cs.money.20260921T021131Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.dota.trade.20260921T021134Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/cs.money.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csfloat.com.20260921T041612Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgofloat.com.20260921T041615Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csfloat.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/g4skins.com.20260921T041630Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.g4s.to.20260921T041634Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/g4skins.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/juice.gg.20260921T041644Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/letmeinjuice.com.20260921T041648Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/juice.gg.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/market.csgo.com.20260921T041652Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2.net.20260921T041655Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/market.csgo.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rust.tm.20260921T041659Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rust.tm.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgolounge.com.20260922T192333Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2.net.20260922T192340Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2lounge.com.20260922T192337Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinbaron.de.20260921T041717Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinbaron.com.20260921T041721Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skinbaron.de.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2royal.com.20260921T041746Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2auth.com.20260921T041750Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tf2royal.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tradeit.gg.20260921T041753Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/connect-tradeit.com.20260921T041757Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tradeit.gg.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/upgrader.pro.20260921T041801Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/upgauth.space.20260921T041804Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/upgrader.pro.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-recheck-2026-09-21.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/domain-registration.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wayback-snapshots.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-2026-09-22c.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/master_registry.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/longitudinal-steam-phishing-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-steam-phishing-100.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-coverage-2026-09-22.json",
          "https://blog.csfloat.com/how-floatdb-tracks-items/",
          "http://web.archive.org/web/20260921022415/https://blog.csfloat.com/how-floatdb-tracks-items/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/platform-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/platforms-removed.json",
          "https://hackerone.com/reports/291750",
          "http://web.archive.org/web/20251116185046/https://hackerone.com/reports/291750",
          "https://hackerone.com/reports/1079561",
          "http://web.archive.org/web/20260924181830/https://hackerone.com/reports/1079561",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/hackerone-reports.json",
          "https://phishdestroy.io/steam_dossier/zh/steam_enforcement_evidence.html#support-records",
          "https://www.darknavy.org/blog/exploiting_steam_usual_and_unusual_ways_in_the_cef_framework/",
          "https://steamcommunity.com/groups/SteamClientBeta/discussions/0/3365901765276206401/",
          "http://web.archive.org/web/20250804051514/https://steamcommunity.com/groups/SteamClientBeta/discussions/0/3365901765276206401/",
          "https://www.chromium.org/developers/design-documents/safebrowsing/",
          "http://web.archive.org/web/20260821101616/https://www.chromium.org/developers/design-documents/safebrowsing/",
          "https://www.chromium.org/developers/how-tos/api-keys/",
          "http://web.archive.org/web/20260830122831/https://www.chromium.org/developers/how-tos/api-keys/",
          "https://github.com/Homebrew/homebrew-cask/issues/193814",
          "https://testsafebrowsing.appspot.com/",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/domain-registration.json",
          "https://phishdestroy.io/steam_dossier/zh/AUTH_AUDIT.md",
          "https://datatracker.ietf.org/doc/rfc6749/",
          "https://docs.cloud.google.com/docs/authentication/api-keys",
          "https://listings.pcisecuritystandards.org/pdfs/PCI_DSS_Resource_Guide_(003).pdf",
          "https://developer.apple.com/news/?id=02202019a",
          "http://web.archive.org/web/20250506070026/https://developer.apple.com/news/?id=02202019a",
          "https://dev.twitch.tv/docs/authentication/validate-tokens/",
          "https://discuss.dev.twitch.com/t/legacy-twitch-api-v5-i-e-kraken-shutdown-reminder-february-28-2022/36589",
          "http://web.archive.org/web/20250127085635/https://discuss.dev.twitch.com/t/legacy-twitch-api-v5-i-e-kraken-shutdown-reminder-february-28-2022/36589",
          "https://store.steampowered.com/news/posts/?enddate=1788390000",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/4123547285514022851",
          "https://skinvault.gg/blog/cs2-trade-protection-explained/",
          "https://csmarketcap.com/blog/market-insights/from-boom-to-bust-cs2s-trade-protection-impact",
          "https://skin.land/blog/steam-changes-cs2-trade-ban-logic-timing/",
          "https://help.steampowered.com/faqs/view/3041-A87A-E5F6-B6AC",
          "https://steamcommunity.com/ogg/593110/announcements/detail/533224478739530146",
          "https://steamcommunity.com/games/CSGO/announcements/detail/4447966961421256740",
          "https://steamcommunity.com/sharedfiles/filedetails/?id=2926756889",
          "https://steamcommunity.com/dev/apikey",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3734103130194459461",
          "https://steamcommunity.com/discussions/forum/1/3807266184852932971/",
          "https://help.steampowered.com/faqs/view/225C-C51E-B8F0-55B2",
          "https://store.steampowered.com/news/group/4/view/3314112260640237775",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/issues/325",
          "https://blog.dota2.com/2020/05/trading-cooldown/",
          "https://blog.counter-strike.net/index.php/2018/03/20308/",
          "http://web.archive.org/web/20250226114333/https://blog.counter-strike.net/index.php/2018/03/20308/",
          "https://phishdestroy.io/steam_dossier/zh/steam_evidence_archive.html",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/493839547938902179",
          "https://store.steampowered.com/online_conduct",
          "http://web.archive.org/web/20260921022120/https://store.steampowered.com/online_conduct",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260918014700/https://store.steampowered.com/subscriber_agreement/",
          "https://steamcommunity.com/dev/apiterms",
          "http://web.archive.org/web/20260921022210/https://steamcommunity.com/dev/apiterms",
          "https://help.steampowered.com/en/faqs/view/628C-E332-BD8C-4D36",
          "https://phishdestroy.io/steam_dossier/zh/social_graph.html",
          "https://phishdestroy.io/steam_dossier/zh/security_timeline.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wsgc-skins-gambling-briefing-2018.pdf",
          "https://wsgc.wa.gov/sites/default/files/2023-10/Skins%20Gambling.pdf",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wsgc-briefing-manifest.json",
          "https://x.com/csgobig",
          "https://www.facebook.com/csgobigofficial/",
          "https://500.casino/",
          "https://csgolounge.com/",
          "https://csgocasino.gg/",
          "https://x.com/CSGOatsecom",
          "https://x.com/CSGOSweep/status/937420902538543106",
          "https://x.com/Wild",
          "https://x.com/csgopot",
          "https://x.com/csgodiamondscom",
          "https://www.ftc.gov/legal-library/browse/cases-proceedings/162-3184-csgo-lotto-matter",
          "https://x.com/CSGODouble",
          "https://x.com/csgo_massive",
          "https://www.facebook.com/csgostrongfree/",
          "https://www.facebook.com/CSNCOM/",
          "https://www.gamblingcommission.gov.uk/report/young-people-and-gambling",
          "https://www.aph.gov.au/Parliamentary_Business/Committees/Senate/Environment_and_Communications/Gamingmicro-transactions",
          "https://phishdestroy.io/steam_dossier/zh/elite_skins.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/csfloat-catalogue.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/skinport-floor-over-cap.json",
          "https://pricempire.com/cs2-marketplaces",
          "http://web.archive.org/web/20260921022459/https://pricempire.com/cs2-marketplaces",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/priceempire-marketplaces.json",
          "https://www.steamanalyst.com/marketplace",
          "http://web.archive.org/web/20260719014552/https://www.steamanalyst.com/marketplace",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-atlas.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json",
          "https://phishdestroy.io/steam_dossier/zh/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/zh/steam_enforcement_evidence.html#case-support-recovery",
          "https://top10.owasp.org/2025/A01_2025-Broken_Access_Control/",
          "http://web.archive.org/web/20260920212535/https://top10.owasp.org/2025/A01_2025-Broken_Access_Control/",
          "https://store.steampowered.com/privacy_agreement/",
          "http://web.archive.org/web/20260921021648/https://store.steampowered.com/privacy_agreement/",
          "https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "http://web.archive.org/web/20250818113925/https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "https://www.dexerto.com/counter-strike-2/valve-saves-hacked-cs2-player-threatened-with-ransom-over-300000-of-rare-stickers-3283135/",
          "https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "http://web.archive.org/web/20220702042821/https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "https://www.kaspersky.com/blog/cs-go-two-million-usd-inventory-hack/44697/",
          "https://esportfire.com/article/the-2-million-usd-csgo-hack-22062022",
          "http://web.archive.org/web/20260515110250/https://esportfire.com/article/the-2-million-usd-csgo-hack-22062022",
          "https://esportsbetting.com/valve-deletes-130000-stolen-dragon-lore/",
          "https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "http://web.archive.org/web/20251115173120/https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "https://vkplay.ru/media/news/bloger-rasskazal-kak-podderzhka-steam-vorovala-akkaunty-igrokov/",
          "https://lis-skins.com/ru/blog/krupneisaia-mosenniceskaia-sxema-v-istorii-steam/",
          "https://escorenews.com/ru/csgo/news/44056-sotrudniki-podderjki-steam-zanimalis-krajey-skinov-s-akkauntov-za-god-oni-zarabotali-svyshe-300-tysyach-dollarov",
          "https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "http://web.archive.org/web/20250805141942/https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/outsourcing-archive-records.json",
          "https://community.skin.club/en/news/collector-has-steam-inventory-returned-after-bold-hack",
          "https://esportfire.com/article/300k-scam-full-katowice-2014-holo-collection-hacked",
          "http://web.archive.org/web/20251217072445/https://esportfire.com/article/300k-scam-full-katowice-2014-holo-collection-hacked",
          "https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng",
          "http://web.archive.org/web/20260920024236/https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng",
          "https://ag.ny.gov/press-release/2026/attorney-general-james-sues-game-developer-promoting-illegal-gambling-through",
          "http://web.archive.org/web/20260901015430/https://ag.ny.gov/press-release/2026/attorney-general-james-sues-game-developer-promoting-illegal-gambling-through",
          "https://www.fincen.gov/sites/default/files/2019-05/FinCEN%20CVC%20Guidance%20FINAL.pdf",
          "http://web.archive.org/web/20250711185007/https://www.fincen.gov/sites/default/files/2019-05/FinCEN%20CVC%20Guidance%20FINAL.pdf",
          "https://eur-lex.europa.eu/legal-content/EN/LSU/?uri=CELEX:32018L1673",
          "https://eur-lex.europa.eu/eli/dir/2024/1640/oj/eng",
          "http://web.archive.org/web/20260830153004/https://eur-lex.europa.eu/eli/dir/2024/1640/oj/eng",
          "https://eur-lex.europa.eu/eli/reg/2022/2065/oj/eng",
          "http://web.archive.org/web/20260920080125/https://eur-lex.europa.eu/eli/reg/2022/2065/oj/eng",
          "https://phishdestroy.io/steam_dossier/zh/legal_analysis.html",
          "https://partner.steamgames.com/doc/features/auth#website",
          "http://web.archive.org/web/20260921022335/https://partner.steamgames.com/doc/features/auth",
          "https://www.ftc.gov/legal-library/browse/rules/childrens-online-privacy-protection-rule-coppa",
          "http://web.archive.org/web/20260921070051/https://www.ftc.gov/legal-library/browse/rules/childrens-online-privacy-protection-rule-coppa",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/gdpr-ticket-1.png",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/screenshot-manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/gdpr-ticket-2.png",
          "https://datenschutz.hamburg.de/beschwerde",
          "https://edpb.europa.eu/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/regulatory-review/disclosure-audit.json",
          "https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "http://web.archive.org/web/20260821155801/https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "https://phishdestroy.io/steam_dossier/zh/index#exhibit-gallery-section",
          "https://github.com/ValveSoftware/steam-for-linux/issues/4521",
          "https://phishdestroy.io/steam_dossier/zh/steam_evidence_archive.html?source=GitHub&record=484",
          "https://github.com/ValveSoftware/steam-for-linux/issues/6459",
          "http://web.archive.org/web/20260419051343/https://github.com/ValveSoftware/steam-for-linux/issues/6459",
          "https://phishdestroy.io/steam_dossier/zh/steam_evidence_archive.html?source=GitHub&record=467",
          "https://github.com/ValveSoftware/Source-1-Games/issues/3857",
          "https://phishdestroy.io/steam_dossier/zh/steam_evidence_archive.html?source=GitHub&record=768",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "http://web.archive.org/web/20250320082450/https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://phishdestroy.io/steam_dossier/zh/steam_evidence_archive.html?source=Reddit&record=4533",
          "https://www.reddit.com/r/ohnePixel/comments/1hahqx2/permanently_banned_steam_account_without_a_clear/",
          "https://phishdestroy.io/steam_dossier/zh/steam_evidence_archive.html?source=Reddit&record=4766",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://phishdestroy.io/steam_dossier/zh/steam_evidence_archive.html?source=Reddit&record=4592",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/selected-evidence-records.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive_manifest.json",
          "https://phishdestroy.io/steam_dossier/zh/card_economy.html",
          "https://github.com/JustArchiNET/ArchiSteamFarm/wiki/FAQ",
          "https://phishdestroy.io/steam_dossier/zh/card_economy.html#scale",
          "https://phishdestroy.io/steam_dossier/zh/card_economy.html#licence",
          "https://phishdestroy.io/steam_dossier/zh/enforcement_audit.html",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "http://web.archive.org/web/20260924181709/https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://rdap.verisign.com/com/v1/domain/csgoempire.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoempire.com",
          "https://rdap.verisign.com/com/v1/domain/csgoempirelogin4.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/csgoempire.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustreaper.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustreaper.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/rustreaper.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustly.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustly.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/rustly.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgofast.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgofast.com",
          "https://rdap.verisign.com/com/v1/domain/authtofast.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/csgofast.com.json",
          "https://rdap.verisign.com/com/v1/domain/duelbits.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fduelbits.com",
          "https://rdap.verisign.com/com/v1/domain/switchflips.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/duelbits.com.json",
          "https://rdap.verisign.com/com/v1/domain/farmskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffarmskins.com",
          "https://tld-rdap.verisign.com/cc/v1/domain/kobal.cc",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/farmskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoluck.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoluck.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/csgoluck.com.json",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/domain-registry/insane.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Finsane.gg",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/insane.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs2skin.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs2skin.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/cs2skin.com.json",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/domain-registry/juice.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fjuice.gg",
          "https://rdap.verisign.com/com/v1/domain/letmeinjuice.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/juice.gg.json",
          "https://rdap.verisign.com/com/v1/domain/ggdrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fggdrop.com",
          "https://rdap.verisign.com/com/v1/domain/ggauth.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/ggdrop.com.json",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/domain-registry/howl.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhowl.gg",
          "https://rdap.radix.host/rdap/domain/howl.uno",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/howl.gg.json",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/domain-registry/chicken.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fchicken.gg",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/chicken.gg.json",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/domain-registry/csgocasino.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgocasino.gg",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/csgocasino.gg.json",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/domain-registry/hunt.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhunt.gg",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/hunt.gg.json",
          "https://rdap.verisign.com/com/v1/domain/csbattle.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsbattle.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/csbattle.com.json",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/domain-registry/skinrave.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinrave.gg",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/skinrave.gg.json",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/domain-registry/csdouble.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsdouble.gg",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/csdouble.gg.json",
          "https://rdap.verisign.com/com/v1/domain/rustchance.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustchance.com",
          "https://rdap.verisign.com/com/v1/domain/hgfuihd.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/rustchance.com.json",
          "https://rdap.radix.host/rdap/domain/cobaltlab.tech",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcobaltlab.tech",
          "https://rdap.verisign.com/com/v1/domain/cobaltauth.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/cobaltlab.tech.json",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/domain-registry/raided.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fraided.gg",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/raided.gg.json",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/domain-registry/rustneo.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustneo.gg",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/rustneo.gg.json",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/domain-registry/splits.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsplits.gg",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/splits.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/upgrader.pro",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fupgrader.pro",
          "https://rdap.radix.host/rdap/domain/upgauth.space",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/upgrader.pro.json",
          "https://rdap.centralnic.com/fans/domain/skin.fans",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.fans",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/skin.fans.json",
          "https://rdap.nic.one/domain/hotpizza.one",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhotpizza.one",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/hotpizza.one.json",
          "https://rdap.verisign.com/com/v1/domain/g4skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg4skins.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/g4skins.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2royal.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2royal.com",
          "https://rdap.verisign.com/com/v1/domain/tf2auth.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/tf2royal.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2hunt.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2hunt.com",
          "https://rdap.verisign.com/com/v1/domain/rstspcl.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/tf2hunt.com.json",
          "https://rdap.identitydigital.services/rdap/domain/tf2.bet",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2.bet",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/tf2.bet.json",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/domain-registry/openstars.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fopenstars.gg",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/openstars.gg.json",
          "https://rdap.verisign.com/com/v1/domain/skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/skins.com.json",
          "https://rdap.identitydigital.services/rdap/domain/white.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwhite.market",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/white.market.json",
          "https://rdap.identitydigital.services/rdap/domain/moon.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmoon.market",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/moon.market.json",
          "https://rdap.verisign.com/com/v1/domain/csfloat.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsfloat.com",
          "https://rdap.verisign.com/com/v1/domain/csgofloat.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/csfloat.com.json",
          "https://rdap.identitydigital.services/rdap/domain/skin.land",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.land",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/skin.land.json",
          "https://rdap.verisign.com/com/v1/domain/haloskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhaloskins.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/haloskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/163.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuff.163.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/buff.163.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmarket.csgo.com",
          "https://rdap.verisign.com/net/v1/domain/dota2.net",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/market.csgo.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinport.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinport.com",
          "https://pubapi.registry.google/rdap/domain/skinport.app",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/skinport.com.json",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/domain-registry/skinflow.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinflow.gg",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/skinflow.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/skin.place",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.place",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/skin.place.json",
          "https://rdap.verisign.com/com/v1/domain/skinsmonkey.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinsmonkey.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/skinsmonkey.com.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbaron.de",
          "https://rdap.verisign.com/com/v1/domain/skinbaron.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/skinbaron.de.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frust.tm",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/rust.tm.json",
          "https://rdap.verisign.com/com/v1/domain/pirateswap.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fpirateswap.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/pirateswap.com.json",
          "https://rdap.radix.host/rdap/domain/mannco.store",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmannco.store",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/mannco.store.json",
          "https://rdap.verisign.com/com/v1/domain/skinswap.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinswap.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/skinswap.com.json",
          "https://rdap.verisign.com/com/v1/domain/exeskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fexeskins.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/exeskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/balticskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbalticskins.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/balticskins.com.json",
          "https://rdap.nic.trade/domain/cs.trade",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.trade",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/cs.trade.json",
          "https://rdap.verisign.com/com/v1/domain/rapidskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frapidskins.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/rapidskins.com.json",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/domain-registry/tradeit.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftradeit.gg",
          "https://rdap.verisign.com/com/v1/domain/connect-tradeit.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/tradeit.gg.json",
          "https://rdap.verisign.com/com/v1/domain/49skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F49skins.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/49skins.com.json",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/domain-registry/skinvault.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinvault.gg",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/skinvault.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/aim.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Faim.market",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/aim.market.json",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/domain-registry/skinout.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinout.gg",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/skinout.gg.json",
          "https://rdap.verisign.com/com/v1/domain/ntskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fntskins.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/ntskins.com.json",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/domain-registry/gamerpay.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamerpay.gg",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/gamerpay.gg.json",
          "https://rdap.nic.tf/domain/scrap.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fscrap.tf",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/scrap.tf.json",
          "https://rdap.nic.tf/domain/marketplace.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmarketplace.tf",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/marketplace.tf.json",
          "https://rdap.identitydigital.services/rdap/domain/skins.cash",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.cash",
          "https://rdap.identitydigital.services/rdap/domain/skinscash.live",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/skins.cash.json",
          "https://rdap.verisign.com/net/v1/domain/csgo.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo.net",
          "https://rdap.verisign.com/net/v1/domain/easylot.net",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/csgo.net.json",
          "https://rdap.verisign.com/net/v1/domain/cybershoke.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcybershoke.net",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/cybershoke.net.json",
          "https://rdap.verisign.com/net/v1/domain/fastcup.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffastcup.net",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/fastcup.net.json",
          "https://rdap.verisign.com/com/v1/domain/leetify.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fleetify.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/leetify.com.json",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/domain-registry/scope.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fscope.gg",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/scope.gg.json",
          "https://rdap.verisign.com/com/v1/domain/tradeupspy.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftradeupspy.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/tradeupspy.com.json",
          "https://rdap.identitydigital.services/rdap/domain/cs.deals",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.deals",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/cs.deals.json",
          "https://rdap.verisign.com/com/v1/domain/pricempire.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fpricempire.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/pricempire.com.json",
          "https://rdap.identitydigital.services/rdap/domain/lzt.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flzt.market",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/lzt.market.json",
          "https://rdap.verisign.com/com/v1/domain/z2u.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fz2u.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/z2u.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoroll.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoroll.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/csgoroll.com.json",
          "https://rdap.verisign.com/com/v1/domain/rollbit.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frollbit.com",
          "https://rdap.verisign.com/com/v1/domain/rbsnin.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/rollbit.com.json",
          "https://rdap.identitydigital.services/rdap/domain/500.casino",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F500.casino",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/500.casino.json",
          "https://rdap.verisign.com/com/v1/domain/csgobig.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgobig.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/csgobig.com.json",
          "https://rdap.verisign.com/com/v1/domain/casedrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcasedrop.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/casedrop.com.json",
          "https://rdap.verisign.com/com/v1/domain/banditcamp.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbanditcamp.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/banditcamp.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinbox.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbox.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/skinbox.com.json",
          "https://rdap.verisign.com/com/v1/domain/tastydrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftastydrop.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/tastydrop.com.json",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/domain-registry/csgopolygon.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgopolygon.gg",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/csgopolygon.gg.json",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/domain-registry/magicdrop.ru.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmagicdrop.ru",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/magicdrop.ru.json",
          "https://rdap.verisign.com/com/v1/domain/csdice.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsdice.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/csdice.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinodds.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinodds.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/skinodds.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgowin.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgowin.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/csgowin.com.json",
          "https://rdap.verisign.com/net/v1/domain/csgorun.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgorun.net",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/csgorun.net.json",
          "https://rdap.verisign.com/com/v1/domain/openskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fopenskins.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/openskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustbet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustbet.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/rustbet.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgomagic.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgomagic.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/csgomagic.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgobounty.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgobounty.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/csgobounty.com.json",
          "https://rdap.verisign.com/com/v1/domain/ezskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fezskins.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/ezskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustcases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustcases.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/rustcases.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoreaper.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoreaper.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/csgoreaper.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgocases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgocases.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/csgocases.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo-skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo-skins.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/csgo-skins.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgonet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgonet.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/csgonet.com.json",
          "https://rdap.verisign.com/com/v1/domain/wtfskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwtfskins.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/wtfskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/flamecases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fflamecases.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/flamecases.com.json",
          "https://rdap.verisign.com/com/v1/domain/gamedom.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamedom.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/gamedom.com.json",
          "https://rdap.nic.club/domain/skin.club",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.club",
          "https://rdap.verisign.com/net/v1/domain/sc-auth.net",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/skin.club.json",
          "https://rdap.verisign.com/com/v1/domain/daddyskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdaddyskins.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/daddyskins.com.json",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/domain-registry/rustix.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustix.gg",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/rustix.gg.json",
          "https://rdap.nic.club/domain/skins.club",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.club",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/skins.club.json",
          "https://rdap.publicinterestregistry.org/rdap/domain/csgohouse.org",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgohouse.org",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/csgohouse.org.json",
          "https://rdap.verisign.com/net/v1/domain/skinrave.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinrave.net",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/skinrave.net.json",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/domain-registry/bloodycase.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbloodycase.gg",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/bloodycase.gg.json",
          "https://rdap.verisign.com/com/v1/domain/csgoclicker.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoclicker.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/csgoclicker.com.json",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/domain-registry/rustbet.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustbet.gg",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/rustbet.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs-drop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs-drop.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/cs-drop.com.json",
          "https://rdap.verisign.com/net/v1/domain/hellstore.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhellstore.net",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/hellstore.net.json",
          "https://rdap.verisign.com/com/v1/domain/rustloot.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustloot.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/rustloot.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo-case.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo-case.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/csgo-case.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgogem.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgogem.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/csgogem.com.json",
          "https://rdap.verisign.com/com/v1/domain/rainbet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frainbet.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/rainbet.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustclash.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustclash.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/rustclash.com.json",
          "https://rdap.identitydigital.services/rdap/domain/12cs.fail",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F12cs.fail",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/12cs.fail.json",
          "https://rdap.verisign.com/com/v1/domain/tf2easy.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwww.tf2easy.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/tf2easy.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2blaze.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2blaze.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/tf2blaze.com.json",
          "https://rdap.verisign.com/com/v1/domain/shuffle.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fshuffle.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/shuffle.com.json",
          "https://rdap.identitydigital.services/rdap/domain/buff.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuff.market",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/buff.market.json",
          "https://rdap.identitydigital.services/rdap/domain/avan.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Favan.market",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/avan.market.json",
          "https://rdap.identitydigital.services/rdap/domain/cs.money",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.money",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/cs.money.json",
          "https://rdap.verisign.com/com/v1/domain/uuskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fuuskins.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/uuskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/youpin898.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fyoupin898.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/youpin898.com.json",
          "https://rdap.verisign.com/com/v1/domain/c5game.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fc5game.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/c5game.com.json",
          "https://rdap.verisign.com/com/v1/domain/waxpeer.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwaxpeer.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/waxpeer.com.json",
          "https://rdap.verisign.com/com/v1/domain/dmarket.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdmarket.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/dmarket.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamcommunity.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamcommunity.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/steamcommunity.com.json",
          "https://rdap.verisign.com/com/v1/domain/lootfarm.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flootfarm.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/lootfarm.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustskins.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/rustskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/krakatoa.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fkrakatoa.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/krakatoa.com.json",
          "https://rdap.verisign.com/com/v1/domain/shadowpay.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fshadowpay.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/shadowpay.com.json",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/domain-registry/igxe.cn.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Figxe.cn",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/igxe.cn.json",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/domain-registry/swap.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fswap.gg",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/swap.gg.json",
          "https://rdap.verisign.com/com/v1/domain/bitskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbitskins.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/bitskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2mart.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2mart.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/tf2mart.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinbid.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbid.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/skinbid.com.json",
          "https://rdap.verisign.com/com/v1/domain/lootbear.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flootbear.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/lootbear.com.json",
          "https://rdap.nic.tf/domain/backpack.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbackpack.tf",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/backpack.tf.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fstntrading.eu",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/stntrading.eu.json",
          "https://rdap.verisign.com/com/v1/domain/skinwallet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinwallet.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/skinwallet.com.json",
          "https://rdap.verisign.com/com/v1/domain/dota2market.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdota2market.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/dota2market.com.json",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/domain-registry/xplay.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fxplay.gg",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/xplay.gg.json",
          "https://rdap.verisign.com/com/v1/domain/esportal.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fesportal.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/esportal.com.json",
          "https://rdap.registro.br/domain/gamersclub.com.br",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamersclub.com.br",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/gamersclub.com.br.json",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/domain-registry/epidemic.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fepidemic.gg",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/epidemic.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs2stash.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs2stash.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/cs2stash.com.json",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/domain-registry/csgoskins.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoskins.gg",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/csgoskins.gg.json",
          "https://rdap.verisign.com/com/v1/domain/steamanalyst.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamanalyst.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/steamanalyst.com.json",
          "https://rdap.verisign.com/net/v1/domain/steamcardexchange.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamcardexchange.net",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/steamcardexchange.net.json",
          "https://rdap.verisign.com/com/v1/domain/dotabuff.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdotabuff.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/dotabuff.com.json",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/domain-registry/tracker.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftracker.gg",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/tracker.gg.json",
          "https://rdap.verisign.com/com/v1/domain/funpay.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffunpay.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/funpay.com.json",
          "https://rdap.verisign.com/com/v1/domain/playerauctions.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fplayerauctions.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/playerauctions.com.json",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/domain-registry/eldorado.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Feldorado.gg",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/eldorado.gg.json",
          "https://rdap.verisign.com/com/v1/domain/g2a.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg2a.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/g2a.com.json",
          "https://rdap.verisign.com/net/v1/domain/kinguin.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fkinguin.net",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/kinguin.net.json",
          "https://rdap.verisign.com/com/v1/domain/g2g.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg2g.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/g2g.com.json",
          "https://rdap.verisign.com/com/v1/domain/playerup.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fplayerup.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/playerup.com.json",
          "https://rdap.verisign.com/net/v1/domain/smurfhub.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfhub.net",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/smurfhub.net.json",
          "https://rdap.verisign.com/com/v1/domain/smurfaccounts.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfaccounts.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/smurfaccounts.com.json",
          "https://rdap.verisign.com/com/v1/domain/buycsgorank.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuycsgorank.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/buycsgorank.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgosmurfkings.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgosmurfkings.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/csgosmurfkings.com.json",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/domain-registry/smurfstore.co.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfstore.co",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/smurfstore.co.json",
          "https://rdap.verisign.com/com/v1/domain/steamlvlup.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlvlup.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/steamlvlup.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamlevels.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlevels.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/steamlevels.com.json",
          "https://rdap.verisign.com/com/v1/domain/levelsteam.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flevelsteam.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/levelsteam.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamlevelu.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlevelu.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/steamlevelu.com.json",
          "https://rdap.verisign.com/com/v1/domain/eloking.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Feloking.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/eloking.com.json",
          "https://rdap.publicinterestregistry.org/rdap/domain/boosteria.org",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fboosteria.org",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/boosteria.org.json",
          "https://rdap.verisign.com/com/v1/domain/overgear.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fovergear.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/overgear.com.json",
          "https://rdap.verisign.com/com/v1/domain/blazingboost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fblazingboost.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/blazingboost.com.json",
          "https://rdap.verisign.com/com/v1/domain/dota2boost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdota2boost.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/dota2boost.com.json",
          "https://rdap.verisign.com/com/v1/domain/buyboost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuyboost.com",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit/buyboost.com.json",
          "https://phishdestroy.io/steam_dossier/zh/steam_tos_assets/auth-route-audit.json",
          "https://help.steampowered.com/en/faqs/view/365F-4BEE-2AE2-7BDD",
          "https://store.steampowered.com/privacy_agreement/#8",
          "https://www.edpb.europa.eu/system/files/2023-04/edpb_guidelines_202201_data_subject_rights_access_v2_en.pdf",
          "https://web.archive.org/web/20260810154631/https://store.steampowered.com/stats/support",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/design-review/part2/measurements.json",
          "https://phishdestroy.io/steam_dossier/zh/VALVE_EVIDENCE_PACK/databases/TOTAL_VALVE_SCANDALS_MASTER_DB.csv",
          "https://phishdestroy.io/steam_dossier/zh/license_disclaimer.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/zh/index.content.json",
      "export_json_sha256": "eefbe950fdf53cbb0fb01667ba4ed2580d0de3ef1cc3917c5e73faff28bb4c6e"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "zh/investigation_part2.html",
      "language": "zh",
      "title": "账户访问与问责——《Steam档案》",
      "source_url": "https://phishdestroy.io/steam_dossier/zh/investigation_part2",
      "source_html_sha256": "6f26d45d867fde18ec4dee5403cfe318c8b575ed102bc8deac67b826780928d8",
      "exported_at": "2026-09-29T00:21:30.937Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "investigation_part2.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/zh/investigation_part2.pdf?v=print-20260929-v5",
        "sha256": "530e5a1ac94c1cde9d26942bc2828f26320cf419024ecdd7b92b19e483a096d3",
        "bytes": 654357,
        "pages": 7
      },
      "integrity": {
        "signed_object": "investigation_part2.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "investigation_part2.content.json.asc",
        "digest_file": "investigation_part2.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify investigation_part2.content.json.asc investigation_part2.content.json",
          "sha256sum -c investigation_part2.content.json.sha256"
        ]
      },
      "content": {
        "text": "《STEAM档案》/ II\n\n您的账户。他们的访问权限。谁接电话？\n\n公共自动化。外包支持。最终承担代价的还是民众。\n\n追踪基础设施状况、已报告的损失以及索赔背后的文件。\n\n追踪基础设施↘\n附件 01 / 实时暗网市场监控550,000+\n\nSteam 个账号正在 FSB Market (匿名名称；此处不公开原名) 上积极出售\n就在这一刻\n\n550,000+ 实时库存 · 231,829 历史抓取语料库（198,320 窃取日志）\n\n被劫持的 Steam 账户的主要地下交易平台，FSB Market (其他相关名称不予公开) 使用 Valve 的官方 Steam OpenID 对买卖双方进行身份验证（openid.realm = https://FSB Market). 每分钟都有超过50万个被盗和遭泄露的账户（来自RedLine/Lumma的窃取日志、钓鱼攻击截获数据、凭证填充数据）以几美分的低价（$0.50–$2.00）被积极挂牌出售。两者均未FSB Market nor相关论坛 被 Valve 的链接过滤器拦截。这是为 63.06% 个付费机器人账户提供支持的“人才库”，而 Valve 在未向受害者提供任何帮助的情况下将其封禁。\n\n实时情报：暗网市场监控（55万+在线用户） ↗ ·打开捕获记录 ↗ ·打开链接过滤器跟踪记录 ↗55万+ 在线\n\n01 / 一个由作者构成的生态系统\n\n自动化已经书面记录。\n\n已命名的项目。已发布的功能。追溯工具至其文档，然后检查收集到的开发者关联关系。\n\n252已收录的仓库\n3,320GITHUB 个人主页\n4,214简介——配置文件与存储库配对\nValve 基础设施社区图书馆可重用应用程序\n线条表示已记录的集成或依赖关系。选择一个节点以查看其相关信息。\n\n多账户自动化 / JustArchiNET\n\nArchiSteamFarm\n\n该项目明确宣传可在Steam账户间同时刷卡。其项目文件声明了SteamKit2依赖项。\n\n阅读该项目的官方文档 ↗\n\nSteamKit → ArchiSteamFarm\n已声明的依赖项 ↗\n\n《关系集》\n\n40 贡献者标签 · 40 forker标签\n\n以下是贡献者示例。这些标签描述的是代码库之间的关系，而非雇佣关系或审批关系。\n\n@JustArchi@renovate[bot]@JustArchi-ArchiBot@dependabot-preview[bot]@renovate-bot@actions-user@dependabot-support@Abrynos\n开发者图所揭示的内容\n\n该图表展示了已公开的贡献者与分支者之间，在指定项目与 GitHub 个人资料之间的关联关系。这些都是公开记录——仓库分支、贡献列表、个人资料关联。关键在于，已公开的能力和开发者关系所留下的这些“纸质痕迹”要求 Valve 回答什么问题，而不是这项调查杜撰了什么。源代码哈希值保存在地图来源.\n\n探索整个网络 ↗存储库源数据 ↓\n\n02 / 不同的凭证，不同的权限。\n\n哪个键我们说的是什么？\n\n玩游戏并不要求玩家提供个人 Web API 密钥。这正是本调查的核心区别所在。\n\n01 / 用户账户\n个人 Web API 密钥\nsteamcommunity.com/dev/apikey\n\n由用户账户签发，用于允许的 API 调用。密钥的创建、可见性、撤销和滥用检测均属于账户安全问题。\n\n02 / 游戏后端\n发布商 Web API 密钥\n\nSteamworks 合作伙伴使用发行商凭据来执行受支持的后台操作，包括与游戏相关的服务。玩家的个人密钥则是另一种凭据。\n\n03 / 身份与会话\nOpenID / 会话令牌\n\nOpenID 用于向网站验证身份。而 Steam 会话令牌或刷新令牌则具有不同的用途。不应将这些机制混为一谈，视作一个可互换的“API 密钥”。\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\nValve 同时记录了用户和发布商的 Web API 密钥。因此，整个 Web API 并非独立于 Steamworks 之外。API 密钥文档 ↗ 已归档 2026-09-15 ↗ ·游戏会话认证 ↗ 已归档 2026-08-29 ↗\n\n由该工具作者记录 / 2024年3月\n\n自动化不仅可以使用 API 密钥。\n\nTrade Offer Manager 的维基文档描述了在没有单独 API 密钥的情况下，如何在 Web API 的部分功能中使用会话访问令牌。该文档还记录了自 2023 年末起，创建 API 密钥时需要进行手机验证。维护者指出，Valve 不支持此类令牌用法；这只是文档中过时的说法，并非针对当前环境的绕过测试。\n\n查看维护者的说明 ↗ 已归档 2026-09-24 ↗\n\n人性层面 / 一个具有说明性的网络钓鱼路径\n\n还在玩。已经曝光了。\n\n来自朋友的一条消息。一个投票请求。一个“感谢”页面。对玩家而言，任务已经完成。但被入侵的会话可能比这一刻持续得更久。\n\n在播放器屏幕上\n\nF\n一位朋友的叙述\n\n“你能给我们的团队投一票吗？”\n\n该请求通过Steam聊天功能从一个熟悉的账号发来。在此情况下，链接的页面会在客户端的浏览器中打开。\n\n《看不见》\n\n信任的建立早于网站的建立。\n\n被劫持的朋友账户可能会让钓鱼链接显得更具可信度。周围的 Steam 界面并不能证明目标网站的安全性。\n\n已知发件人 / 外部收件人\n在出售任何商品之前，账户安全是首要考虑的问题。\n\n该玩家并非有意创建自动化凭证或授权他人控制。重新登录游戏并不能证明该账户是安全的。Valve 保存着会话日志、API 密钥创建记录以及设备关联数据，而受害者则没有。这种信息不对称正是问责问题所在。\n\n会话访问和凭据类型\n\nAPI 密钥和登录会话是两种具有不同权限的凭据。撤销密钥不会终止当前的活动会话。Valve 的官方文档中对这两者均有说明；Valve 保存着日志，这些日志可显示在任何存在争议的操作发生时，究竟是哪一种凭据处于活动状态。 要求的是披露该记录——而非调查方凭空推断出的结论。维护者关于令牌处理的文档 ↗ 已归档 2026-09-24 ↗ ·Valve 关键文档 ↗ 已归档 2026-09-15 ↗\n\n03 / 正规市场存在价格上限\n\n该物品可能是稀有物品。限制依然存在。\n\n如果报价超过挂牌上限，则无法通过在社区市场进行一次全价挂牌来实现该价格。\n\n参考要价$5,000更改商品的标价\n$100$20,000\n\n此为已公布的限额示意图，并非估值或交易建议。simplified-chinese\n\n上市上限≈ $1,800\n钱包帽≈ $2,000\n\n超过已公布的挂牌上限。\n\n钱包中的资金无法提现至银行账户。这些限制催生了第三方皮肤市场所满足的需求：这种需求由上架限制和钱包额度限制所产生，而Valve自身的规则却禁止商业运营商满足这一需求。\n\nSteam的市场限额 ↗ 已归档 2026-09-21 ↗\n\n04 / 支持边界内部\n\n受托管理数据。负责访问管理。\n\nValve的隐私政策明确规定，在提供支持所必需的情况下，可与第三方支持服务提供商共享个人数据。\n\n《玩家》账目与凭证\n→\nVALVE恢复过程\n→\n支持提供商委托访问\n\n隐私政策 §5.2 ↗ · Valve的内部政策允许第三方支持人员进行访问。目前尚待澄清的问题包括：授予了哪些权限、存在哪些审计记录，以及在据称发生访问权限滥用时发生了什么。\n\n2015\n该秤是公开的\n\nValve 承认了账户被盗现象普遍存在，并介绍了相应的防护措施。\n\nValve 出版物 ↗已归档 2026-08-09 ↗\n2015\nValve 将该岗位外包了——并且也这么说了\n\nValve 设有一个小型内部 Steam 支持领导团队，并表示“雇了几家不同的公司” 以处理支持服务（Erik Johnson、Valve，向Kotaku）；其隐私政策第5.2条授权这些第三方访问用户数据。哪家承包商拥有账户恢复权限，Valve从未透露过 — 社区讨论中提到了Concentrix等供应商，但均未得到Valve确认。该外包服务台早在以下两则声明发布之前数年就已经设立。\n\nKotaku：Valve 对其支持 ↗已归档 2025-07-11 ↗\n2023\n第一次入学\n\nValve的《CS:GO》战队就其帮助请求流程导致账号被盗一事以书面形式承担责任，并撤销了相关交易。\n\n打开外包案例 ↓\n2025\n第二次入学\n\n33个月后，Steam 客服回复称，一名技术人员“未按我们的流程操作，导致您的账户被恢复给了其他人”。同样的渠道。同样的结果。\n\nDexerto，2025年11月14日 ↗\n\n案件档案 / HFB 与外包指控\n\n进入的方式正是Steam支持本身。Valve 以书面形式表示了这一点。\n\n在Dexerto转载的客服回复中，Valve的CS:GO战队承认其账号遭入侵一事应由该队负责通过求助流程 — 这是其自有渠道，既非钓鱼页面，也非用户所为。相关资产已被追回，交易已撤销，而这正是Valve告诉其他受害者根本不存在的补救措施。据报道，HFB的库存为$2,000,000+ 当天以及$3,000,000+ 在后续工作中；Qkss 也以同样的方式输掉了 $1,000,000+，一无所获.\n\n支持回复 / 转载自 DEXERTO · 2023年2月21日\n“因一则技术支持请求而遭到入侵，CS:GO团队对此承担责任”\n阅读报道及转载的消息 ↗ 已归档 2025-08-18 ↗\n01 / 哪个阀门开了\n其自有支持渠道便是切入点\n\n该回复涉及被入侵的账户及其交易的撤销。Valve已撤销这些交易——因此这些交易是可以撤销的。原始的经过认证的交易单不在此集合中。\n\n02 / 解雇未能解决的问题\n2025年11月，那扇门再次敞开了\n\n该承包商解雇了其全部 Steam 名支持人员——此消息由 Mzkshow 通过 Dexerto 报道，并非来自 Valve 的人事声明。 三十三个月后，Steam Support 致信另一位用户称：“处理该求助请求的技术支持人员未遵循我们的流程，导致您的账户被恢复给他人。”这是 Valve 本人关于同一渠道的陈述。\n\n第二次入学，2025年11月14日 ↗\n03 / 什么是“开放”\nValve从未透露过该承包商的名称\n\n这些消息来源既未指明承包商，也未指明具体地点。这并非报道中的漏洞——而是Valve尚未披露谁拥有用户账户的访问权限。\n\n该案的当代记载 ↗\n\n有三个问题Valve尚未回答：谁可以绕过账户恢复机制、访问审计发现了什么，以及此后发生了什么变化。\n\n保存下来的支持档案中后来的指控\n\n2024年Reddit上的两篇帖子披露了Mzkshow的进一步调查——一起发生于2024年7月的VAC禁令撤销案例和一起发生于2024年12月的$13,000库存案例。这些是分别报告的事件。 每起事件中的问责问题都是一样的：谁拥有覆盖权限，审计发现了什么，以及发生了哪些变化。\n\n2024年7月14日 · 报告已康复 / VAC-禁令案例 ↗2024年12月2日 · 报告了 $13,000 库存案例 ↗已归档 2025-08-05 ↗两条已保存的帖子、来源行和哈希值 ↓\n\n05 / 追随损失\n\n每个金额需要一个保护套。\n\n10起案例，时间跨度为2022年6月至2026年3月。每个金额均采用其所引用的来源公布的数值——$6,300,000,$2,000,000+,$1,000,000+,≈$320,000,≈$300,000，降至288欧元。Valve保存着每笔交易的交易日志、会话记录和支持审计轨迹，但均未提供任何相关记录。\n\n支持渠道21 6月2022\n$2,000,000+\nHFB — the largest inventory in the game\n\n报告的库存估值 · 在2月2023后续报道中上调至3百万美元以上\n\n七件“龙之传说”纪念品和#1蓝宝石卡兰比特刀，仅那把刀的价格就约为1.26。账户已闲置三年，认证标识仍未移除；已通过客服账户恢复渠道更改了邮箱和密码。Valve撤销了交易——并以书面形式承担了责任。 在撤销交易之前，据报告已有200,000+的交易收益通过market.csgo.com提现，该平台支持现金和加密货币结算。撤销交易仅退还皮肤，不会返还用户已存入账户的资金。 此次回滚还引发了其他问题：一名买家将他的“纪念版龙之传说”藏在游戏内的储物箱中，脚本无法查看该容器内部；Valve在撤销一起盗窃时，将一件价值$130,000的物品复制了一份——这一问题通过物品ID和社区举报被发现，该物品已于7月被删除2022,，买家的退款由BUFF而非Valve处理。\n\nDexerto，失窃当天 ↗\n钱包与购买07 7月2022\n>$500\n44 disputed Market purchases\n\n申报的钱包消费额 · 美元\n\n有用户反映，其账户遭人擅自购买了低价值的《Dota》2游戏道具，且客服的回应令人不满。\n\n阅读投诉内容及相关截图 ↗\n平台安全漏洞14 8月2022\n$6,300,000\nCS.Money — 19,000+ 机器人生成的皮肤\n\n估值 · 初步估价1.6百万美元\n\n攻击者窃取了该交易平台交易机器人的手机验证器文件并清空了其中的内容，还将部分赃款转给知名交易员以混淆视听。 社区研究人员在数小时内就追踪到了55上的攻击者账户。Valve并未进行任何反向追踪——据Steam透露，该第三方网站位于Steam之外，而该平台的库存、交易API及账户系统全程参与了此次盗窃。\n\n阅读当代记载 ↗\n支持渠道报道来源：21 2月2023\n$1,000,000+\nQkss——同一扇门，同一位演员，截然不同的答案\n\n报告的存货估值\n\n以HFB案为参照——由同一位当事人通过相同的客服求助请求提出——HFB案已在八个月前得到了全额赔偿，而Qkss案则未获全额赔偿。在已公开的记录中，除受众规模外，这两起案件并无任何区别。\n\nDexerto关于Mzkshow调查的报道 ↗\n支持渠道报道于2月2023\n≈ $320,000\n内幕交易本身——持续了一年\n\n约一年内的营业收入 · 非存货估值\n\n技术支持团队查阅到了长达15年的账户历史记录：第一个CD密钥、第一封电子邮件、第一张信用卡——这些正是账户恢复流程所要求的证据。 无论谁掌握数据库，在与账户持有者的争执中总是占据上风。一把被盗的 M4A4 Howl（附带 iBUYPOWER 和 Titan Katowice 2014 全息贴纸），以 $35,000 的价格售出，最终落入 NAVI 战队的 b1t 手中，而他对此毫不知情。承包商的应对之策是解雇所有在 Steam 客服部门工作的员工。\n\nEscorenews关于同一项调查的报道 ↗\n钱包与购买09 DEC 2023\n€288\n尽管采用了两步验证保护，钱包仍遭丢失\n\nTRUSTPILOT · 来源索引 16\n\n该评论者反映其账户遭到黑客入侵，且对方拒绝协助处理Market消费问题。该导出文件中未包含单独的评论链接。\n\n检查来源出处 ↗\n账户恢复02 DEC 2024\n$13,000\n《马特维》——解雇事件两年后\n\n作者的存货估算\n\n向某人授予了账户恢复权限，因为该人提供了账户所有者本人无法匹配的账户数据。在承包商清空其 Steam 支持服务台后，采取了同样的流程，结果也一样。\n\n阅读已存档的指控 ↗\n账户恢复09 MAY 2025\n≈ $10,000\n通过他人的车票进行补票\n\n索赔物品丢失 · 美元\n\n一位魁北克用户称，客服应他人要求重置了密码并取消了账户保护。\n\n阅读这篇第一人称投诉 ↗\n支持渠道13 11月2025\n≈ $300,000\nHawkeye337 —— 以及Valve的第二份书面供词\n\n卡托维兹2014全套全息图集\n\n攻击者索要1比特币，并开始将该收藏品刮取到Negevs上以销毁它。Steam 客服回复：“处理该求助请求的一名技术支持人员未遵循我们的流程，导致您的账户被恢复给了其他人。” 自首次承认问题以来已过去三十三个月，情况依然如故。该帖子在X上成为热门话题后数小时内，账户便被恢复。Qkss则没有那么大的受众群体。\n\nDexerto, 14 Nov 2025 ↗\n钱包与购买29 MAR 2026\n$50\n未经授权的充值和赠送游戏\n\nTRUSTPILOT · 来源索引 290\n\n该评论者指控存在未经授权的消费以及退款申请未获批准的情况。导出文件中缺少该条评论的具体链接。\n\n检查来源出处 ↗\n\n来源及金额均按各来源的报告为准。Valve 保存了所有这些案例的交易日志、会话记录和支持审计轨迹。请提供这些资料。一篇被保留下来的 Reddit 帖子无法解决这个问题——Valve 自身的记录才能解决。\n\n“系列” / “核对后”\n\n231,829个账号正在出售。Valve 保存了每个的日志。\n354 → 201\nTrustpilot 记录\n\n已删除 153 行重复记录。导出文件中未保留单个评论的 URL。\n\n231,829\nSteam 账户列表\n\n33,509 归类为“自行登记”；198,320 归类为“收藏家盗窃品”。列表中的商品并不代表已成交。\n\n应收账款审计 ↓搜索源代码存档 ↗",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "您的账户。他们的访问权限。谁接电话？"
          },
          {
            "level": 2,
            "id": null,
            "text": "自动化已经书面记录。"
          },
          {
            "level": 3,
            "id": null,
            "text": "ArchiSteamFarm"
          },
          {
            "level": 2,
            "id": null,
            "text": "哪个键我们说的是什么？"
          },
          {
            "level": 3,
            "id": null,
            "text": "个人 Web API 密钥"
          },
          {
            "level": 3,
            "id": null,
            "text": "发布商 Web API 密钥"
          },
          {
            "level": 3,
            "id": null,
            "text": "OpenID / 会话令牌"
          },
          {
            "level": 3,
            "id": null,
            "text": "自动化不仅可以使用 API 密钥。"
          },
          {
            "level": 2,
            "id": null,
            "text": "还在玩。已经曝光了。"
          },
          {
            "level": 3,
            "id": "session-hidden-title",
            "text": "信任的建立早于网站的建立。"
          },
          {
            "level": 2,
            "id": null,
            "text": "该物品可能是稀有物品。限制依然存在。"
          },
          {
            "level": 2,
            "id": null,
            "text": "受托管理数据。负责访问管理。"
          },
          {
            "level": 3,
            "id": null,
            "text": "该秤是公开的"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve 将该岗位外包了——并且也这么说了"
          },
          {
            "level": 3,
            "id": null,
            "text": "第一次入学"
          },
          {
            "level": 3,
            "id": null,
            "text": "第二次入学"
          },
          {
            "level": 3,
            "id": null,
            "text": "进入的方式正是Steam支持本身。Valve 以书面形式表示了这一点。"
          },
          {
            "level": 4,
            "id": null,
            "text": "其自有支持渠道便是切入点"
          },
          {
            "level": 4,
            "id": null,
            "text": "2025年11月，那扇门再次敞开了"
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve从未透露过该承包商的名称"
          },
          {
            "level": 2,
            "id": null,
            "text": "每个金额需要一个保护套。"
          },
          {
            "level": 3,
            "id": null,
            "text": "HFB — the largest inventory in the game"
          },
          {
            "level": 3,
            "id": null,
            "text": "44 disputed Market purchases"
          },
          {
            "level": 3,
            "id": null,
            "text": "CS.Money — 19,000+ 机器人生成的皮肤"
          },
          {
            "level": 3,
            "id": null,
            "text": "Qkss——同一扇门，同一位演员，截然不同的答案"
          },
          {
            "level": 3,
            "id": null,
            "text": "内幕交易本身——持续了一年"
          },
          {
            "level": 3,
            "id": null,
            "text": "尽管采用了两步验证保护，钱包仍遭丢失"
          },
          {
            "level": 3,
            "id": null,
            "text": "《马特维》——解雇事件两年后"
          },
          {
            "level": 3,
            "id": null,
            "text": "通过他人的车票进行补票"
          },
          {
            "level": 3,
            "id": null,
            "text": "Hawkeye337 —— 以及Valve的第二份书面供词"
          },
          {
            "level": 3,
            "id": null,
            "text": "未经授权的充值和赠送游戏"
          },
          {
            "level": 2,
            "id": null,
            "text": "231,829个账号正在出售。Valve 保存了每个的日志。"
          },
          {
            "level": 3,
            "id": null,
            "text": "Trustpilot 记录"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam 账户列表"
          }
        ],
        "links": [
          "https://phishdestroy.io/live-intel/?category=steam",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/lzt.market.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-evidence-lzt.json",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://github.com/JustArchiNET/ArchiSteamFarm/blob/main/ArchiSteamFarm/ArchiSteamFarm.csproj",
          "https://github.com/JustArchi",
          "https://github.com/renovate[bot]",
          "https://github.com/JustArchi-ArchiBot",
          "https://github.com/dependabot-preview[bot]",
          "https://github.com/renovate-bot",
          "https://github.com/actions-user",
          "https://github.com/dependabot-support",
          "https://github.com/Abrynos",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/automation-map.json",
          "https://phishdestroy.io/steam_dossier/zh/output_steam_network/network.html",
          "https://phishdestroy.io/steam_dossier/zh/output_steam_network/raw_data.json",
          "https://phishdestroy.io/steam_dossier/zh/#proxy-bypass-explainer",
          "https://partner.steamgames.com/doc/webapi_overview/auth",
          "http://web.archive.org/web/20260915025812/https://partner.steamgames.com/doc/webapi_overview/auth",
          "https://partner.steamgames.com/doc/webapi/ISteamUserAuth",
          "http://web.archive.org/web/20260829124950/https://partner.steamgames.com/doc/webapi/ISteamUserAuth",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "http://web.archive.org/web/20260924181824/https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://store.steampowered.com/privacy_agreement/",
          "https://store.steampowered.com/oldnews/19618",
          "http://web.archive.org/web/20260809125516/https://store.steampowered.com/oldnews/19618",
          "https://kotaku.com/valve-explains-why-steam-customer-service-is-still-terr-1736988223",
          "http://web.archive.org/web/20250711004653/https://kotaku.com/valve-explains-why-steam-customer-service-is-still-terr-1736988223",
          "https://www.dexerto.com/counter-strike-2/valve-saves-hacked-cs2-player-threatened-with-ransom-over-300000-of-rare-stickers-3283135/",
          "https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "http://web.archive.org/web/20250818113925/https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "https://lis-skins.com/ru/blog/krupneisaia-mosenniceskaia-sxema-v-istorii-steam/",
          "https://www.reddit.com/r/cs2/comments/1e38jo4/stealing_accounts_and_removing_vac_bans_a_new/",
          "https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "http://web.archive.org/web/20250805141942/https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/outsourcing-archive-records.json",
          "https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "https://escorenews.com/en/csgo/news/44087-valve-steam-support-employee-accused-of-selling-inactive-accounts-inventories-worth-six-figures-b1t-has-one-of-these-skins",
          "https://phishdestroy.io/steam_dossier/zh/PART2_RESEARCH.md",
          "https://www.reddit.com/r/GlobalOffensive/comments/1h56shi/steam_support_is_stealing_accounts/",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/design-review/part2/quality-review.json",
          "https://phishdestroy.io/steam_dossier/zh/steam_evidence_archive.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/zh/investigation_part2.content.json",
      "export_json_sha256": "155b92eca7783ce85f332a7890ef185376523dd8a84485295fb606d1d670b0d5"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "zh/legal_analysis.html",
      "language": "zh",
      "title": "他们的条款，您的权利——《Steam》专题报道",
      "source_url": "https://phishdestroy.io/steam_dossier/zh/legal_analysis",
      "source_html_sha256": "904f28a3dd34e0ded0a4ae25b5a64b99338da4a18109a85840d57341bc9a31f0",
      "exported_at": "2026-09-29T00:21:31.876Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "legal_analysis.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/zh/legal_analysis.pdf?v=print-20260929-v5",
        "sha256": "2f976a3b487e3417921904dc0a6a7c4af8fed5c4fc234e99a73d3b5ccd658c69",
        "bytes": 677823,
        "pages": 6
      },
      "integrity": {
        "signed_object": "legal_analysis.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "legal_analysis.content.json.asc",
        "digest_file": "legal_analysis.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify legal_analysis.content.json.asc legal_analysis.content.json",
          "sha256sum -c legal_analysis.content.json.sha256"
        ]
      },
      "content": {
        "text": "法律与经济报告\n法律分析——服务条款与合规要求\n\n他们的条款。 您的权利。\n\n本节证明了什么\n\n本次法务审计旨在评估Valve公司与Steam用户在主要监管管辖区内的合同不对称性。 报告阐明了可撤销订阅许可如何剥夺消费者法定所有权，分析了欧洲法院关于数字产品转售权耗尽的判例，并审查了其对《数字服务法》（DSA）及《欧盟《数字服务法》实施条例》（GDPR）第15.条的合规情况。分析表明，自动化执法机制在缺乏有效上诉渠道的情况下运作，而平台市场费用则系统性地从每笔点对点交易中榨取经济价值。\n\n← 返回高管简报\n\n本报告从法律、经济和技术角度，对Steam所公布的平台规则与消费者实际处境之间的差距进行了分析：即自动化执法却几乎没有申诉渠道，以及企业对数字资产的广泛控制。所有数据均注明了来源；若某项数据无法追溯至原始记录，则予以省略。\n\nVector 1\n\n将“所有权”替换为可撤销许可，以便根据协议收回数字资产。\n\nVector 2\n\n自动执法系统（VACNet）的封号决定，其支持页面（Steam）明确表示无法撤销。\n\nVector 3\n\n账户和资产管控措施，加上15%的CS2市场手续费（5%、Steam以及10%的发布者费用），导致每次转售都会从生态系统中抽走价值。\n\n术语不对称性\n免责声明和可撤销许可\n2.1 “订阅”模式与产权\n\nSteam《订阅协议》第2条仅授予用户一项 个人、非独占、不可转让且可撤销的许可. 根据协议，Valve 可随时终止账户，且 Steam 钱包中未使用的余额可能会被没收。\n\n2.2 “退款幻觉”与《欧盟消费者权益指令》\n法律框架\t退款机制\t限制\nEU Consumer Rights Directive\tUnconditional 14-day right of withdrawal on digital content\tWaived if download begins with explicit consumer consent\nSteam SSA\t14 days / under 2 hours played\tValve may deny at its discretion for \"abuse\"\n评估\n\nValve 欧盟14-日法定撤销权以该网站自身的“14天/2小时”期限为条件，用户必须在下载产品时接受该条款，方可对产品进行评估。该政策收窄了——而非扩大了——法定权利；其是否合法，应由主管当局裁定，而非本文所作出的结论。\n\n诉讼\n二级市场与反垄断\nUFC Que Choisir 诉 Valve — 法国\n2019\n巴黎法院：权利耗尽原则适用于数字游戏——转售行为合法\n10月2022\n巴黎上诉法院推翻了该判决\n23 10月2024\n最高上诉法院（最高法院）：电子游戏属于《信息社会指令》所指的“复杂作品”，而非软件。数字转售 禁止. Valve 胜出。\nWolfire Games反垄断案——美国（Valve反垄断诉讼案，案号：2:21-cv-00563）\n\nValve的“最惠国待遇”（PMFN）条款禁止开发者以更低价格在任何其他平台上销售Steam密钥。竞争对手商店——即使是那些收取12%佣金（相较于Valve的30%）的商家——也不能将节省下来的费用转嫁给消费者。\n\nWhat this means — PMFN — platform most-favoured-nation\n\nA contract term that stops a seller offering better terms anywhere else than on the platform it signed with. Applied to game keys it means a studio cannot undercut its Steam price on a storefront that takes a smaller cut. It is the clause at the centre of the antitrust claims against Valve.\n\n336Valve公司员工总数（2021）。来源：已解封的证据材料。\n79负责管理整个Steam平台的员工。来源：已解封的证据材料。\n$3.5M每位员工的净利润。来源：已解封的证据材料。\n\n已解封的取证记录显示 $8.5B 总收入，单位为2021 关于336的员工。该 79-Steam团队成员 通过将373,000以及日常支持工单转接至外包的自动化呼叫中心，处理了这些工单。\n\n已解封的案卷附件 · W.D. WASH. 案件编号 2:21-CV-00563内部调查备忘录\n\n蒂姆·斯威尼（Epic Games 首席执行官）致加布·纽维尔： “既然支付处理费用是 2–5%，带宽费用是 CDN，而每 GB 带宽费用是 $0.002/，为什么 Steam 还要从总收入中抽取 30% 的分成？如果从 Steam 上排名前列的 25 游戏里剔除掉这些，我敢打赌，Valve 从接下来大部分 1,000 游戏中赚取的利润，甚至比开发者自己赚的还多。”\n\n斯科特·林奇（Valve公司首席运营官）发给加布·纽维尔的内部转发邮件： “你生气了吗，兄弟？”\n\n宣誓证词反驳（彭博社，2026）： 根据《联邦民事诉讼规则》第30条(b)款（1）关于证人询问的规定，加布·纽维尔作证称： “Valve 没有向其他平台上的第三方软件开发商规定价格的政策或做法。” 原告向纽维尔出示了Valve的内部备忘录，这些备忘录证明该公司曾对在竞争平台定价更低的开发者采取积极的价格监管措施，并威胁将其下架。3月下旬，2026, 联邦法院驳回了Valve提出的即决判决动议，将32,000-开发者集体诉讼案移交陪审团审理。\n11月 2024\n\n已批准针对……的集体诉讼 ~32,000 开发团队 自1月以来支付了佣金 2017, 此外还有一起并行的消费者集体诉讼。\n\n索赔金额\n\n$3.1B\n根据美国反垄断法，罚款金额翻了三倍 = $9.3B 潜在暴露。\n\n6月 2026: 一起新诉讼指控微软和Valve达成卡特尔协议，以压制个人电脑游戏分销领域的竞争。\n\n金融犯罪与反洗钱正式录取通知\nValve 官方供词：全球欺诈清算案（28 October 2019）\n\n28年10月2019,，Valve 正式终止了新购买的《反恐精英》容器密钥的交易及市场转售行为。在其正式公告中（blog.counter-strike.net/2019/10/26113)，Valve公司以书面形式承认，其构建的虚拟经济已沦为一个国际洗钱清算中心：\n\n“过去，我们观察到的大多数密钥交易都是在合法客户之间进行的。然而，最近全球范围内的诈骗团伙已开始利用《CS:GO》密钥套现。目前，几乎所有最终在交易平台上被转手或出售的密钥，据信都来自诈骗渠道。”\n\n监管背景： 这一供认发生在华盛顿州博彩委员会（WSGC）向Valve发出正式最后通牒之后，此前Valve总法律顾问卡尔·夸肯布什（Karl Quackenbush）于7月针对23旗下的皮肤赌博域名（包括CSGO Lotto、CSGOLounge和OPSkins）发布了2016的“停止并终止”命令，而这一系列行动仅在刑事博彩调查威胁到平台运营之后才采取。\n\n管辖权\n俄罗斯的一家权利人，用户无法联系到\n\n《订阅协议》将Valve描绘成一个几乎不承担任何责任、且无人能与其取得联系的一方：封禁措施一劳永逸，申诉请求均被驳回，仅凭一句关于“受制裁地区”的表述，整个地区的访问权限便被撤销。与此形成鲜明对比的是，当Valve在某个原本被其视为棘手的司法管辖区内，自身商业利益受到威胁时，其采取的行动。\n\nValve v. Touch Skins — 俄罗斯知识产权诉讼的审前主张\n1 9月2026\nValve 通过俄罗斯律师事务所 梅林、沃伊蒂什金及合伙人律师事务所，向……的经营者发送了审前索赔函 触控皮肤，一款大型《军团要塞2》皮肤变换器，通过俄罗斯邮政和电子邮件寄送。\n理由\n涉嫌侵权行为主要涉及三个方面：软件的专有权利；武器、刀具和手套皮肤的外观设计权；以及Valve的商标权。运营商的此类行为被认定为蓄意且持续时间较长。\n需求\n立即停止运行并删除所有基础设施——该软件的 源代码、网站和社交媒体页面——否则，Valve 保留向俄罗斯法院提起诉讼的权利，以 可观的经济补偿 并将此事提交给 执法机关进行的犯罪评估.\n结果\n收到这封信后，该平台宣布将停止运营。据报道，这是Valve首次在俄罗斯对一名皮肤修改器开发者采取法律手段。\n\n据数据挖掘者马克西姆·“GabeFollower”·波列塔耶夫（X，~11 202026）及俄罗斯游戏媒体报道。这只是一项庭前主张，并非已提起的诉讼；目前尚未公开任何案号。本文仅根据报道内容进行介绍，不作为法院记录。来源： dota2.ru 存档 2026-09-24 ↗ · Shazoo.\n\n同一管辖区域，相反方向简体中文（大陆）\n\nValve 对俄罗斯的法律和监管体系并不陌生。它 符合俄罗斯联邦通信、信息技术和大众传媒监督局（Roskomnadzor）的规定：应监管机构的要求，该网站删除了包含违禁内容的社区页面 260和 Steam，且俄罗斯联邦通信、信息技术和大众传媒监督局（Roskomnadzor）已公开声明，Steam 符合法律要求。俄罗斯的“着陆”法（联邦法 236-FZ（自2022起生效）规定，面向俄罗斯用户提供服务的大型外国互联网平台必须在当地设立实体机构，并开设一个与俄罗斯联邦通信、信息技术和大众传媒监督局（Roskomnadzor）对接的联络账户。Valve 不仅响应了该监管机构的下架令，如今还借助俄罗斯律师团队，并以俄罗斯法院的诉讼威胁为后盾，将其皮肤作为知识产权加以保护。\n\n因此，该平台在涉及自身收入时，既能触达用户、能力充足，又能维护自身权益。与此形成鲜明对比的是用户：来自受制裁地区的付费客户被告知双方关系已终止，社区访问权限被锁定，直到 2038, 该工单关闭为止，且没有任何论坛可以对这一决定提出质疑—— “他们非常乐意收我的钱并处理我的交易”，该账户来自同一伊朗IP地址的退款已在一年前获批（r/pcgaming，4 8月2026; 更多执法函件见 “卡片经济”展览). Valve 动用了国家法律体系的全部手段来保护一个皮肤；而对于购买了皮肤的用户，该平台却完全没有提供任何救济程序。\n\nValve 每当涉及Valve的利益时——无论是俄罗斯律师、俄罗斯法院的威胁，还是对俄罗斯联邦通信、信息技术和大众传媒监督局（Roskomnadzor）下达的下架令的回应——它都将该司法管辖区视为自己可以采取行动并遵守规定的管辖区；而对于该市场乃至其他所有市场的用户所应履行的义务，则将其视为完全不受任何法律程序约束。 在涉及自身收益时，它就是权利人；而在涉及用户权利时，它却成了无法触及的一方。\n\n来源： 塔斯社（RKN：Steam 符合要求） · 《联邦法》236-FZ.\n\n法律投机主义\n《仲裁条款》的让步\n2023 — 袭击事件\n\n多家律师事务所（Zaiger LLC、Mason LLP）通过社交媒体招募了数千名用户，并同时提交了数万起个人仲裁申请。\n\nValve的曝光情况\n\n$225M+\n在任何案件进入实体审理之前，就已支付了不可退还的仲裁立案费。 根据美国仲裁协会（AAA）《消费者仲裁规则》及《大规模仲裁补充附表》计算得出。由Zaiger LLC和Mason LLP代理的索赔人向Valve公司提交了约75,000份个人仲裁申请（与在 Wolfire Games LLC 等诉Valve公司案, 案号：2:21-cv-00563-JCC，W.D，华盛顿州）。根据美国仲裁协会（AAA）的消费者费用表，作为被申请人的企业需为每起个案支付不可退还的案件行政费及仲裁员指定保证金，金额约为3,000+（75,000份申请 × $3,000 = 约225百万美元的预付程序性费用）。 参见彭博法律（Bloomberg Law）和路透社（Reuters）关于科技行业大规模仲裁风险的法律报道（2023–2024）。\n\n时期\t社会保障局争议解决机制\t观测到的效应\t结果\nBefore Sep 2024\tMandatory individual arbitration + class-action waiver\tIndividual litigation becomes economically irrational for users\tMass arbitration → $225M fee threat\nAfter Sep 2024\tDisputes in King County, WA courts only\tArbitration costs are avoided; cases consolidate in a single forum\tClass actions now possible\n结论\n\n十多年来，社会保障局（SSA）一直要求用户放弃陪审团审判的权利，转而接受个人仲裁。 由于大规模的仲裁申请导致该机制给Valve带来了沉重的财务负担，因此对《SSA》进行了修订，将争议转交金县法院处理。该变更在提出时未提供实质性的退出选项；若不接受该变更，用户将因账户被删除而丧失对已购买数字资产的访问权限。\n\n算法执法\nVACNet、有罪推定与误报\n10月2023——AMD Anti-Lag+\n\nAMD驱动程序的一次更新（v23.10.1）在《反恐精英2》（CS2）中激活了“Anti-Lag+”功能，该功能拦截了游戏的DLL函数。VAC将此行为归类为“作弊代码注入”，并在Valve介入之前，对数千名合法用户实施了永久封号。\n\n12月2023——高DPI\n\nDPI值超过10,000且快速转动摄像头的玩家被永久封号。VACNet无法区分真实的鼠标移动与“旋转机器人”（spinbot）作弊行为。\n\n支持类别\t宣称的响应时间\t实际结果\nRefund requests\t50 min – 1.5 hr\tAutomatic approval (<14 days, <2 hours played)\nAccount security / recovery\t3–12 hours\tDepends on documentation provided\nContesting a VAC ban\tForm response\tComplete refusal. Support cannot reverse VAC decisions. The ban is permanent.\nValve的官方政策\n\n“VAC封禁是永久性的，不可协商，且无法由Steam客服解除。”\n\n发布封禁通知的同一支持渠道也发布了拒绝复核的通知：Steam 客服表示无法推翻 VAC 的决定。对用户而言，算法的裁决即为最终结果。\n\n转售的经济分析\n对虚拟资产的控制权及转售费\n15%CS2的市场手续费——每次转售时都会扣除相应金额\n迭代\t买方余额\t卖方收到\t《Burned》（15%）\n1\t$100.00\t$85.00\t$15.00\n2\t$85.00\t$72.25\t$12.75\n3\t$72.25\t$61.41\t$10.84\n10\t$23.16\t$19.68\t~$3.47\nTotal\t$100 → dust\tValve collects the 15% fee on each resale. Users must add new money to keep trading.\nCS2 升级规则变更 — 10月 2025\n\nValve未经事先通知，修改了CS2以旧换新合约规则，允许玩家用“隐秘”品质的物品兑换稀有刀具和手套，并保证能获得这些物品。随后，刀具价格下跌，“隐秘”品质物品价格急剧上涨，市场随即出现恐慌性抛售。\n\nValve 声称依据的是《社会保障法》（SSA）第7条——对于平台规则的变更不承担任何责任。在Valve所述的规则可能在未经通知且不提供补偿的情况下发生变更的经济环境中，用户需自行承担风险。关于报道中所述的全市场损失规模存在争议，且在缺乏一手资料的情况下，本文不予列举。\n\n欧洲监管部门的应对措施\nUOKiK、DSA 和《数字公平法》\nUOKiK — 波兰，5月2024\n\n波兰反垄断机构（UOKiK）针对Valve公司及五家国内游戏发行商/分销商，就其涉嫌价格垄断、限制性价格一致条款以及地域封锁行为，正式启动了反垄断调查程序。这些行为导致波兰消费者购买数字游戏时，比邻近的欧洲经济区（EEA）市场多支付高达20%的费用。 作为反垄断调查的一部分，UOKiK的检查人员和警方对波兰本土合作发行商和分销商的办公场所进行了凌晨突击搜查和证据检查（而非Valve的子公司办公室，因为Valve在波兰没有实体机构）。潜在法定罚款：最高可达年营业额的10%。 来源： UOKiK官方公告，“UOKiK主席已对Valve及游戏开发商启动调查程序”，5月2024.\n\n《数字服务法》（DSA）\n\n要求自动化审核具备透明度。Steam 未公布 VACNet 的误报/漏报数据，且其客服渠道明确表示 VAC 决定不可撤销。\n\n《数字公平法案》——2026\n\n预期条款包括：对付费内容的长期访问权、禁止在权利放弃环节使用“暗黑模式”、承认数字资产的财产权，以及防止永久没收库存。\n\n结论\n规则与记录之间已记录的差异\n1\n\n所有权差距。 用户为许可证支付了全价，而协议允许Valve撤销该许可证。法国最高法院（10月 2024）裁定数字转售不受法律保护，从而在法律上确立了这一立场。\n\n2\n\n算法执法。 VACNet 发出了错误的封禁（AMD 驱动程序、高 DPI 事件）。Steam 客服表示无法推翻 VAC 的决定，因此算法的判定即为最终裁决。\n\n3\n\n费用节约。 15%的CS2市场费用（5% Steam + 10% 发布商费用）会在每次转售时削减商品价值，且平台规则可能在不另行通知的情况下发生变更；根据《SSA》条款，Valve对此类变更不承担任何责任。\n\n4\n\n仲裁条款已被删除。 美国社会保障局（SSA）于9月取消了强制仲裁规定 2024,，此前大量用户同时提交申请，导致 Valve 面临约225M 的费用。用户未能就这一变更获得实质性的退出选择权。\n\n5\n\n选择性管辖权。 Valve 聘请了俄罗斯律师事务所（Melling, Voitishkin & Partners），并威胁要在俄罗斯法院对Touch Skins提起诉讼，与此同时，却将自身对该市场用户的义务视为超出任何司法程序的范畴。Valve在涉及自身商业利益时便充当权利人，而在涉及用户权益时却成为无法联系的一方。\n\n← 第一部分：代理绕过与赌博第二部分：获取与问责 →\n\n法律来源和案件记录均注明了其原始出版方和存储机构。不主张对相关文件的所有权。",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "法律分析——服务条款与合规要求"
          },
          {
            "level": 2,
            "id": null,
            "text": "免责声明和可撤销许可"
          },
          {
            "level": 3,
            "id": null,
            "text": "2.1 “订阅”模式与产权"
          },
          {
            "level": 3,
            "id": null,
            "text": "2.2 “退款幻觉”与《欧盟消费者权益指令》"
          },
          {
            "level": 2,
            "id": null,
            "text": "二级市场与反垄断"
          },
          {
            "level": 3,
            "id": null,
            "text": "UFC Que Choisir 诉 Valve — 法国"
          },
          {
            "level": 3,
            "id": null,
            "text": "Wolfire Games反垄断案——美国（Valve反垄断诉讼案，案号：2:21-cv-00563）"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve 官方供词：全球欺诈清算案（28 October 2019）"
          },
          {
            "level": 2,
            "id": null,
            "text": "俄罗斯的一家权利人，用户无法联系到"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve v. Touch Skins — 俄罗斯知识产权诉讼的审前主张"
          },
          {
            "level": 3,
            "id": null,
            "text": "同一管辖区域，相反方向简体中文（大陆）"
          },
          {
            "level": 2,
            "id": null,
            "text": "《仲裁条款》的让步"
          },
          {
            "level": 2,
            "id": null,
            "text": "VACNet、有罪推定与误报"
          },
          {
            "level": 2,
            "id": null,
            "text": "对虚拟资产的控制权及转售费"
          },
          {
            "level": 3,
            "id": null,
            "text": "15%CS2的市场手续费——每次转售时都会扣除相应金额"
          },
          {
            "level": 3,
            "id": null,
            "text": "CS2 升级规则变更 — 10月 2025"
          },
          {
            "level": 2,
            "id": null,
            "text": "UOKiK、DSA 和《数字公平法》"
          },
          {
            "level": 2,
            "id": null,
            "text": "规则与记录之间已记录的差异"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/zh/#briefing-heading",
          "https://dota2.ru/news/67707-valve-cerez-uristov-napravila-krupnoj-rossijskoj-skincendzer-platforme-trebovanie-o-prekrasenii-deatelnosti/",
          "http://web.archive.org/web/20260924181657/https://dota2.ru/news/67707-valve-cerez-uristov-napravila-krupnoj-rossijskoj-skincendzer-platforme-trebovanie-o-prekrasenii-deatelnosti/",
          "https://shazoo.ru/2026/09/12/190508/valve-cerez-rossiiskix-iuristov-dobilas-zakrytiia-krupnogo-skinceindzera-dlia-cs2",
          "https://www.reddit.com/r/pcgaming/comments/1vf24lu/warning_to_all_gamersexpats_steam_took_my_money/",
          "https://phishdestroy.io/steam_dossier/zh/card_economy.html#asymmetry",
          "https://tass.ru/obschestvo/23235387",
          "https://base.garant.ru/401414628/",
          "https://uokik.gov.pl/postepowanie-wyjasniajace-w-sprawie-valve-i-dystrybutorow-gier",
          "https://phishdestroy.io/steam_dossier/zh/",
          "https://phishdestroy.io/steam_dossier/zh/investigation_part2.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/zh/legal_analysis.content.json",
      "export_json_sha256": "1cfee033d2871d3693273650ed2be6ff66ef33735649b4eac1641d2a46602981"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "zh/license_disclaimer.html",
      "language": "zh",
      "title": "许可 · 权利 · 免责声明 — PhishDestroy",
      "source_url": "https://phishdestroy.io/steam_dossier/zh/license_disclaimer",
      "source_html_sha256": "58261745aca0a23734cac3d80fed89f0163463124dc053828f35da5cc080bbdf",
      "exported_at": "2026-09-29T00:21:34.837Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "license_disclaimer.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/zh/license_disclaimer.pdf?v=print-20260929-v5",
        "sha256": "31629cedd52273e94e0269b628081b6e225543059c788d50354587a2190e3c5e",
        "bytes": 513093,
        "pages": 8
      },
      "integrity": {
        "signed_object": "license_disclaimer.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "license_disclaimer.content.json.asc",
        "digest_file": "license_disclaimer.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify license_disclaimer.content.json.asc license_disclaimer.content.json",
          "sha256sum -c license_disclaimer.content.json.sha256"
        ]
      },
      "content": {
        "text": "PHISHDESTROY法医调查 · Valve / Steam\n许可 · 权利 · 免责声明\n许可与法律免责声明 — 公共领域奉献声明\n\n保留所有权利 向人类投降了。\n\n本节证明了什么\n\n本文件确立了关于PhishDestroy Steam 档案的无条件公共领域奉献（CC0 1.0 Universal）及MIT软件许可条款。所有法医调查结果、证据数据集、网络图及分析方法均不可撤销地置于公共领域，供全球范围内在监管、法律和学术领域不受限制地使用。\n\n← 返回高管简报\n\nPhishDestroy 放弃了对此材料的全部权利——包括复制、出售以及署名等权利。以下是两份以同一声音呈现的文件：一封写给Valve的公开信，采用我们日常的写作风格；以及一份为负责推进此事项的机构起草的正式权利放弃书。\n\n调查 · Valve 公司 / Steam公开版——无有效期，不可撤回\n豁免\n第一节许可协议 ——从法律角度来看确实如此，但从人情味的角度来说……\n\nPhishDestroy 放弃对本作品的所有权利。零。没了。完事。你可以复制它、出售它、署上你的名字、把它纹在老板身上，随你便。无需署名，无需私信，也不指望收到感谢卡。\n\n一条实际规则（是的，就一条）\n\n你无权决定自己是否是恐怖分子。\n\n如果您是来自俄罗斯或任何受美国财政部外国资产控制办公室（OFAC）制裁国家的用户——本内容不适用于您。没有漏洞可钻。请享受您的制裁吧。\n\nWhat this means — OFAC\n\nThe Office of Foreign Assets Control, the US Treasury body that administers American sanctions programmes. “An OFAC-sanctioned country” means one those programmes cover. The phrase appears here as a condition on who this material is offered to, not as an allegation about any reader.\n\n如果你在莫斯科时把Steam的地区设置改成了土耳其——恭喜你，真有创意。你依然是俄罗斯人。制裁依然有效。这正是关键所在。\n\n第二节这是什么以及它为何存在\n\n我们将发布关于Valve的资讯，其内容之多甚至超过了Valve普通员工对自己所了解的程度。这并非在自夸，只是事情最终发展到了这一步。\n\n我们怎么会走到这一步？说来有趣：Steam 可以说就是我们的缔造者。它用那些诈骗者、那些客服工单、那个规避封号的生态系统把我们养大——而如今，我们就在这里。没什么怨言。其实，这还挺有诗意的。\n\n对于那些还没读过这则事件始末的人——我们之前已经见过Valve那些收费极其高昂的欧洲律师（既然你问了，就是泰勒·韦辛律师事务所）：\n\nhttps://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d 存档链接：2026-08-21 ↗\n\n一次令人愉快的邂逅。尤其是考虑到他们的时薪。\n\nValve 知道吗？知道。Taylor Wessing 知道吗？几乎可以肯定知道。但当你富到那种地步时，法律与其说是必须遵守的规则，不如说是一种氛围，对吧？\n\n其实，这基本上就是全部答案了。\n\nSteam 花了好几年时间“收治”诈骗分子。这并非总是出于故意——有时诈骗分子只是因为与Valve有牵连，才被贴上了它的标签。我们并非想大惊小怪，而是力求准确。说实话，对我们来说，做到准确比大惊小怪更难——这只是我们的写作风格。\n\n这算是一种冲突吗？\n— 否。\n\n这个问题能解决吗？\n— 是的。但我们不会签署任何保密协议，也不会为了区区几分钱去参与漏洞赏金计划。\n\n我们等了超过4年，直到他们修复了该欺骗问题，才得以公开撰文讨论此事。因为如果我们早些时候就写了这篇文章，Steam肯定会摆出一副受害者的样子，大喊“存在活跃威胁！”，并给我们一点零花钱，让我们签署一份文件，使我们永远成为他们的法律财产。不用了，谢谢。\n\n（另外：Valve 本身就违反了保密协议。他们自己的员工也违反了，尤其是高层人员。不过，好吧，我们还是来谈谈我们这边的情况吧。）\n\n第三节致Valve的公开信 — 说真的，看看这个\n\nValve：如果您希望关闭该域名，请发送电子邮件给我们。此事无需聘请外部律师。\n\n对于不了解内情的人来说：帕特里克博士拥有阿伯丁大学国际商法专业的法学硕士学位，而且——请注意——他的博士论文确实是关于信息技术法的。 他最近晋升为泰勒·韦辛律师事务所的合伙人，该事务所的整个商业模式就是向Valve这类公司收取天价费用，以此拖延诉讼，直到对方耗尽资金或失去耐心。\n\n我们并不怪他。为那些按小时付费、心怀愧疚的富有的客户辩护——这确实是个明智的职业选择。我们只是觉得你不该为此买单。\n\n这笔交易（公开要约，无需律师）\n\n该域名是Valve目前唯一能够切实触及的部分。调查、转介以及相关资源已经启动——无论该域名是否存在，这些工作都会继续进行。\n\n如果您想要该域名：\n\n请让您的IT法律专业人士来确定一个公平的价格。\n\n50% 将捐赠给“SEAL”基金会。\n\n我们注销这个域名。没戏。不用上法庭。搞定。\n\n这并非威胁。这是针对唯一真正触手可及之事所提出的一项直截了当的提议。你别无他法——这就是现状的本质。\n\n我们会直接“损害”Valve的利益吗？恐怕不会在财务上对他们造成实质性影响。我们并不自欺欺人。但我们会以诚实、公开的方式行事，不为博取影响力——因为我们不需要影响力。我们需要让全世界看到那些只要花足够时间观察，本就显而易见的事实。\n\n我们拥有5年的档案资料。Valve的律师在证据开示过程中展示的内容——即特工们可以查阅的数据、指纹记录，以及他们亲手交给我们的一系列书面证据——已经足够了。我们没有必要将原始数据泄露出去。\n\n谁得到什么\n\n监管机构将收到原件。\n\n研究人员和记者获得的是经过删节的版本（受害者报告、儿童的登录信息以及Valve那令人捧腹的客服评论均因显而易见的原因被删除）。\n\n受影响的账户中包括未成年人，但他们并未收到通知。这一调查结果已纳入监管机构提交的材料中，其中已删除受害者报告和身份信息，因为该内容应提交给数据保护机构，而非刊载于文章中。\n\n此外，Valve——在您决定如何处理此事之前，我们想澄清一点：PhishDestroy 是一个社区，而不是某个人。您在未与该社区沟通的情况下，直接向其发送法律函件——只是为了获取数据，随后便封禁了相关账号——这已经说明了一切。\n\n本社区与Valve没有任何冲突。这不是我们主动找上的。是你们培养出来的骗子主动找上了我们。我们已经将他们封禁了。现在情况就是这样。\n\n第三节-B盟军资源 — 特别致Steam的一则说明\n\n我们希望坦率地说明这种放大机制，因为假装它不存在是不诚实的。\n\n据我们了解，PhishDestroy 社区内至少有两个盟友资源，它们会接手这些材料并加以利用。\n\n这在实际中意味着：\n\n他们针对重叠的主题，各自从不同的角度切入。\n\n他们是独立的——他们不接受我们的指导，我们也不接受他们的指导。虽然主题大致相同，但研究方法各不相同。\n\n他们绝不会根据第1.条采取行动。他们正在密切关注。\n\n如果 Valve 决定不关闭该网站：\n\n预计它们会在第2部分或第3.部分之后出现。\n\n他们会从我们的研究成果中汲取有用的部分，结合自己的研究成果，然后以自己的名义发表。\n\n这正是1条款中的许可所针对的情况：内容被传播到需要的地方，得到补充，得到扩展——而我们和他们之间都不需要互相标注来源。\n\n（附注：对于那些对责任链存有疑问的律师：根本不存在责任链。这些资源既未接受我们的指导，也未获得我们的资助，更未使用我们的数据。它们只是阅读公开信息，并得出自己的结论。就像你们一样。）\n\n我们这么说并不是为了恐吓。我们这么说，是为了让“Valve”阵营中负责制定战略的人，能够准确了解信息环境的实际情况。\n\n能够整合我们的资料并加以补充的一种资源就是一篇报道。如果两种资源各自独立地进行分析并得出相似的结论，这就形成了一种模式。而监管机构关注的就是这些模式。\n\n第四节金钱、禁令，还有这整场闹剧\n\n关于Steam封禁赌博网站和诈骗者的事情，关键在于：这并非执法，而是为了牟利。Valve将钱装进自己的口袋，洗脱责任，然后走上舞台，向所有人讲述关于宝可梦卡牌和棒球的美好故事。\n\n在有关支持方安全漏洞的记录中——包括Valve于2月发表的书面声明2023，承认对通过求助请求导致的高价值账户遭入侵事件负有责任，以及Dexerto和Escorenews报道的、在320k内幕交易案后承包商员工被解雇的情况（第二部分 §04 · 主要专题 §14.1) — 这些内容均基于已公开的承认和调查报道。关于后勤人员从事赌博副业或收取分成以解除禁令的未经证实的传闻，在公开记录中尚未得到证实，因此本文不予采纳。\n\n与此同时，Valve 取消了在 2017. 上正常追踪皮肤的功能。他们甚至在自己的论坛上讨论过此事。他们将其称为“反赌博措施”——然而，此后数年间，皮肤赌博生态系统仍持续通过 Steam 的基础设施进行数十亿的交易。真是绝佳的品牌形象。\n\n我们将证明：\n\nSkins 比门罗币更具有匿名性\n\n据称，一个秘鲁贩毒集团利用《Dota》2的皮肤进行资金转移\n\nSteam 从功能上讲，这是一个价值约7B的“交易卡”（没错，他们确实对检察官提到了“交易卡”）的制裁规避工具。\n\n我们有一段关于皮肤的视频。你会看到的。\n\n我们还知道：\n\nReddit 的内容审核工作受到 Valve 的影响\n\n第三方Steam数据基础设施（例如 steamid.uk) 由一名个人运营（msart) 及其关联的同源“封禁列表”项目 (steambans.com 存档) 由一位经确认的 Valve 社区版主共同管理（killahinstinct_) — 从而将对平台封禁措施的独立审计完全置于“Valve”的掌控之下 (参见“卡牌经济”一节，网址：08)\n\n他们无法控制的，就予以禁止\n\nValve：如果你继续装傻——那也没关系。我们已经记下你的“安全港”了。Google Analytics 本来就会对用户的 IP 地址进行匿名处理。我们清楚哪些内容被删除了。只是目前还无法以足够低廉的成本证明这一点，让你的律师们在意。至少现在还不行。\n\n第五节关于恶意软件这件事 — 是的，我们会提到这一点\n\n让我们对事件的经过直截了当地说清楚，因为这恰恰暴露了你的真实面目。\n\n我们不会公开披露游戏中的这一漏洞。我们也不会向“Steam”项目报告该漏洞。该项目要求签署保密协议（NDA），而签署该协议将使我们无法向受影响的用户说明其账户发生了什么情况。向那些丢失账户的用户以及监管机构披露信息，正是这项工作的核心目的；保密协议与这一目的相悖。\n\n实际情况是这样的：在相关圈子里，这个漏洞几乎已是公开的秘密。我们确切地知道，独立安全研究人员已经将完整的漏洞利用代码直接摆在了Steam技术支持团队的面前。这部分已经完成了。你们已经通过自己那些形式主义的渠道收到了正式警告。\n\n那么，Valve做了什么？完全什么都没做。因为对 Valve 而言，安全并不等于利润——事实上，恰恰相反。安全是一个成本中心。除非威胁达到临界点并引发灾难性的公关危机，否则 Valve 不会将其视为紧急事项。\n\n那么我们该怎么做？我们要向公众披露这一情况，因为“Valve 知晓这一系统性恶意软件威胁，却主动选择置之不理”这一事实，对于目前正在阅读本文的监管机构而言，是一个至关重要的信息点。\n\n这款游戏规模庞大。我们在此不点名。但请明白这一点：\n\n这绝不是那种服务器让你“安装驱动程序”的、司空见惯的CS:GO脚本小子垃圾。这简直是灾难性的。\n\n这简直是《Unturned》级别的噩梦：连接服务器时的零点击远程代码执行（RCE）。你加入一个服务器。你什么都没点。 你什么也没下载。连接过程本身就是攻击面，你的机器已完全被攻破。让我们面对现实：利用Valve的可信数字证书作为跳板植入RCE并绕过本地杀毒软件，在Steam上早已不是什么新鲜事了。这几乎已成为你所处生态系统中的一项内置功能。\n\nWhat this means — zero-click RCE\n\nRemote code execution: making a program run an attacker’s code on someone else’s machine. “Zero-click” means the victim does nothing at all — no download, no opened file — beyond being connected. It is the most severe class of flaw there is.\n\nValve 早已知道这款游戏的存在。 但他们却利用自己最喜欢的、懦弱的法律漏洞：由于该游戏从技术上讲是由第三方开发的，Valve便对此不闻不问。他们负责分发游戏、处理支付、托管基础设施，但当一个零点击远程代码执行漏洞威胁到数百万用户时，他们的立场却是：“不是我们的游戏，我们不承担责任。”\n\n当此事不可避免地闹大时，第三方开发者将背锅，而Valve则会装作是那个“协助”解决问题的负责任平台，全身而退。这正是Valve一贯的懦弱作风。我们早就看透了他们的套路。\n\n我们将此事记录在案，以便监管机构、检察官和记者能够确切了解Valve是如何处理活跃恶意软件的：他们躲在第三方开发者背后，利用保密协议（NDA）封口，让玩家沦为待宰羔羊。\n\n公开信结束正式记录开始\n正式语体 · 用于官方场合\n声明关于使用和权利\n\nPhishDestroy 项目与网络安全联盟\n\n本声明随同本转交材料中的每份提交文件和每份附件一并提供。本声明致所有收到该材料的机构、法院、监管机构、检察官、研究人员、记者或相关当事人。\n\n1. 使用无任何限制\n\n1.1 联盟在此转交案件中制作的所有材料——包括事实陈述、分析、其撰写的证据材料、分析工具及调查结果——均以“不保留任何权利”的方式予以发布。\n\n1.2 任何人无需征得许可，也无需通知我们，即可：\n\n复制该内容（无论是全部还是部分）；\n\n对其进行改编、编辑、改写、重组或更正；\n\n将其转换为；\n\n摘录该内容，但未注明系摘录；\n\n将其纳入官方文件、调查结果、裁决、诉状、报告或新闻材料中；\n\n将其作为收件人自己的作品或收件人自己的研究成果加以呈现；\n\n将其作为原料使用，其余部分弃之；\n\n并以相同的条款将其转交给任何其他人。\n\n1.3 无需注明出处，也不要求注明出处。无需提及、引用、署名、致谢、征询或通知该联盟。 如果本转介材料对相关机构有所帮助，且从未提及本联盟，那么这将是一个完全令人满意的结果，本联盟特此预先声明，以免引发相关疑问。\n\n1.4 另一方面，如果某机构认为引用该联盟作为来源更为方便，也可以这样做。选择权完全在于接收方，无论采取哪种做法都不会产生任何后果。\n\n1.5 本文件为免责声明，而非许可要约。它无需接受，不产生任何义务，且无法被违反。 联盟发布的软件另行依据MIT许可协议发布；研究成果及发现已在法律允许的最大范围内进入公共领域；若某司法管辖区不允许免责，则联盟授予具有同等效力的不可撤销、全球范围、免版税的许可。\n\n2. 这在实际中为何重要，而不仅仅是一种礼节\n\n2.1 主管机关可能会出于合理考虑而犹豫是否采信外部方提供的材料，因为担心这会给人留下其受该方指使或与该方存在某种牵连的印象。\n\n2.2 这里没有任何值得纠缠之事。联盟不索取任何东西，不被欠任何东西，不保留任何东西，也不抱有任何期待。它日后无法主张任何权利、索取任何功劳、抱怨滥用，或对材料的定性提出异议，因为它没有保留任何可据以这样做的依据。\n\n2.3 因此，使用这些材料的机构并非代表联盟行事。它只是利用了恰好由他人整理的公开信息。\n\n3. 一切都已经开放了\n\n3.1 该联盟的工作默认是公开的：\n\n调查结果已公开发布在 https://phishdestroy.io 并且可以自由阅读；\n\n该工具已作为开源软件在以下地址发布，采用 MIT 许可协议： https://github.com/phishdestroy 存档链接：2026-09-11 ↗;\n\n该方法论在转介文件本身附件A的A节中有所阐述。16D，其中包括每种信息来源类型的权重和限制；\n\n该联盟不接受任何捐赠，并自 2018. 以来一直公开表明这一立场。\n\n3.2 唯一未予公开的材料是那些依法或出于安全考虑无法公开的内容：受害人和第三方的个人数据，以及可能导致消息来源遭受报复的信息。此类材料已以保密方式提交给有关当局，并在证据清单中予以标明。\n\n3.3 该联盟以与要求审查他人行为相同的标准，欢迎对其自身行为进行审查，并已主动向相关主管部门提交了其数据处理情况，包括请求就数据处置事宜作出指示。\n\n4. 证据包的完整性\n\n4.1 附件随提交材料一并提供；如文件中另有标注，也可通过安全渠道应要求提供。这些附件不会发布在任何公开地址上，也不应推断出此类地址：此类材料将直接提供给相关主管部门。\n\n4.2 每次交付都会附带一个名为 SHA256SUMS 的文件，其中列出了所提供每个文件的 SHA-256 摘要，以及一个独立的 OpenPGP 签名 SHA256SUMS.asc。\n\n4.3 签名密钥发布在 https://phishdestroy.io/.well-known/pgp-key.txt 以及在 keys.openpgp.org 上。该网站的标识出现在本系列中每份投稿的信头中。\n\n4.4 任何收件人都可以随时验证，其手中的文件是否与发送的文件完全一致、未被篡改：\n\ngpg --verify SHA256SUMS.asc SHA256SUMS\n\nsha256sum -c SHA256SUMS\n\n4.5 这样做并非为了走过场。其目的是，如果日后对任何证据的准确性或完整性产生争议，该问题可通过计算而非争论来解决。\n\n5. 关于登记——为何豁免具有实际作用，而不仅仅是慷慨之举\n\n5.1 当局可能会看到“联盟”发表的调查报告，并觉得这些报告措辞直白、充满对抗性，有时甚至带有讽刺意味。这种印象是正确的。“联盟”正是有意采用这种写作风格，对此也不作任何辩解。\n\n5.2 它同时也承认，这种语气并不适合监管或司法程序。 严肃的事项不应以竞选宣传的口吻来表达。提交给主管部门的调查结果应直截了当地陈述，同时承认其局限性，而不应让读者在理解实质内容之前，先因语气问题而对其产生质疑。\n\n5.3 这正是联盟放弃署名权的原因。1条中的放弃声明，正是将内容与登记名录分离的机制：主管部门可以取其所需，用自己的语言重新表述，并将联盟的措辞及名称一并舍弃。 这样做并不会造成任何损失，而且联盟更倾向于这种做法。\n\n5.4 该联盟还要求不要将登记册与方法混为一谈。 公开发表的语气虽具对抗性，但其背后的实践却并非草率。在整个转交审查过程中，推论与观察相区分，证词被明确标识为证词，对信息来源进行了权衡并指出了其薄弱之处，数据在呈现时附有其局限性说明，而联盟无法证明的观点则被作为向主管当局提出的问题，而非作为断言。 当证据与联盟自身的立场相悖时，联盟已明确指出这一点——参见并行转交文件的附件A第7,段及B节0。\n\n5.5 该联盟解释了其行事方式与财务状况之间的关联，因为二者密不可分。 它不接受任何人的资金——不接受捐款、不接受赏金、不接受客户、不接受赞助商。正是这种拒绝，才使得直言不讳成为可能：一个需要保护收入来源的组织，必须在谈论其所依赖的各方时有所克制。由于没有任何需要保护的东西，该联盟也就无需有所克制。\n\n这也是联盟得以延续的原因。除此之外别无其他动力。工作之所以能完成，只是因为它确实完成了；当参与其中的人停下脚步时，工作也就随之停止。\n\n5.6 当局无需接受上述任何内容。此处作出说明，是为了避免将联盟公开工作的语气误解为对其目前审议的材料的重视程度。\n\n6. 用联盟自己的话来说，它提供了什么\n\n信息、研究和观察。\n\n报告中并未将任何内容作为联盟无权作出的认定。若某项内容系推断得出，转交文件中会明确说明；若某项内容基于证词，转交文件中会注明证人身份及相关限制；若联盟无法回答某个问题，报告中也会如实说明，并指明谁能回答该问题。\n\n该联盟既不寻求任何补救措施、任何赔偿、任何承认，也不为自身或任何个人寻求任何结果。它仅要求由一个有权强制要求答复的机构，将转交文件中列出的问题提交给Valve公司。\n\n结语致负责推进此事的任何人\n\n我们要感谢那位将这些材料送达指定地点的人。这恐怕不会是一趟轻松的旅程。Valve财力雄厚，而Taylor Wessing则按小时收费——这种组合正是为了让像你这样的人在抵达终点前就放弃。\n\n我们清楚自己在做什么，也清楚自己在写谁。正是Valve塑造了我们——我们怎么可能不理解他们呢？\n\nPhishDestroy 这与Valve没有任何冲突。我们只是扼杀了迄今为止遇到的唯一一个如此规模的诈骗团伙——我们并没有刻意与Valve为敌。只是结果发现，所有线索最终都指向了他们。这并非冲突，只是网络拓扑关系使然。\n\nValve 无法解决PhishDestroy的问题，因为根本没什么可解决的。我们之间没有任何关联。关于他们牟利手段和暴利的资料大多是公开的——你只需要花足够的时间去查阅就能看到。 不妨将其视为一本“成功百科全书”：“如何规避制裁，以免俄罗斯黑客盗版我们的免费游戏（那些付费游戏他们反正也不会盗版）。”你应该能明白其中的意思。\n\n我们不需要署名。\n\n我们不需要注明出处。\n\n我们不需要赢。\n\n我们需要一位拥有实际权限的人士，向Valve提出这份转交文件中已列出的问题，并有权要求其作出答复。\n\n就这样。这就是全部的要求。\n\n案例将发布在：\n\nhttps://steamdestroy.eth/\n\nhttps://steamdestroy.eth.limo （目前无法正常显示——必要时将予以修复）\n\n我们将出席以下活动：\n\nhttps://phishdestroy.eth.limo/ 存档链接：2026-06-27 ↗\n\nhttps://phishdestroy.eth/\n\n两件签名物品 · 权利及已发表文本\n已签署的免责声明签署了什么，以及其涵盖的内容\n\n下文中的权限授予声明和研究文本是分别签署的JSON对象。每个独立的OpenPGP签名都对与其相邻的JSON文件的具体字节内容进行认证。权限声明用于授予权限；文本快照则用于标识并包含所发布的材料。\n\n1. 权利声明 — license-rights.json\n\n已签名的对象： 完整的 license-rights.json 该文件包含一份日期为28的公开权利授予声明 2026.。该声明授权在无需注明出处、通知或获得批准的情况下，复制、发布、编辑、翻译、整合及商业化利用所撰写的档案材料。此签名仅对权利声明本身进行认证，并不对每个网页或PDF文件的文本内容进行认证。\n\n原始的签署版授权书将保持原样。无论是否更改网站、发布其他文件或关闭网站，均不得撤销或缩小其中现有的授权范围。第三方材料仍保留其自身的权利。\n\n权利声明 JSON ↗ · license-rights.json的签名 ↗ · license-rights.json 的 SHA-256 ↗\n\ngpg --verify license-rights.json.asc license-rights.json\nsha256sum -c license-rights.json.sha256\n2. 已发布的文本 — dossier-text.json\n\n已签名的对象： 完整的 dossier-text.json 文件。其中包含导出页面中实际可读的文本，位于 documents[].content.text，其中包含每页的标题、语言、来源网址、来源HTML哈希值、标题和参考文献。该 documents 该列表准确列出了本快照所涵盖的全部内容；各语言版本则单独列出。这是一份文本出版物，而不仅仅是一份哈希值列表。\n\n每个条目都通过文件名和 SHA-256 在 documents[].pdf. 该 JSON 文件还通过 URL 和 SHA-256, 标识了原始权利声明，因此可以准确匹配已发布的文本、其 PDF 文件以及相应的权利授权书，无需猜测。链接到的外部数据库、原始图片以及未列入目录的页面均未嵌入此文本快照中。\n\n完整的签名文本 JSON ↗ · dossier-text.json的签名 ↗ · dossier-text.json 的 SHA-256 ↗\n\ngpg --verify dossier-text.json.asc dossier-text.json\nsha256sum -c dossier-text.json.sha256\n\n在资料集首页，PDF 和 JSON 按钮用于导出研究资料包。在内页中，这些按钮用于导出该页面在发布语言中的版本。每个页面的 JSON 文件还都有各自的独立签名和 SHA-256文件，其名称在该 integrity 对象。要验证相关的 PDF 文件，请计算其 SHA-256，并将其与 pdf.sha256 经过验证的 JSON 中的值。该 PDF 受该摘要的约束；它不包含 PDF 格式的数字签名。\n\n3. 可打印的研究资料包 — steam-dossier-{language}.content.json\n\n已签名的对象： 完整的特定语言的 JSON 文件，其中包括打包的章节正文，位于 documents[].content.text，章节页码范围、源语言、被排除的源文件清单以及精确的PDF摘要，详见 pdf.sha256. 这五个补充证据档案库仍在线上保持链接，并未打包在一起。作者撰写的研究文本得以保留；图文目录则被源链接所取代。\n\n英语 JSON ↗ · OpenPGP标志（独立版）↗ · SHA-256摘要 ↗\n\n德语 JSON ↗ · OpenPGP标志（独立版）↗ · SHA-256摘要 ↗\n\ngpg --verify steam-dossier-en.content.json.asc steam-dossier-en.content.json\nsha256sum -c steam-dossier-en.content.json.sha256\n\n公钥 ↗\n\n签名指纹：129F C7F3 9C40 C69D 2EF3 C329 BFCF 9E8D D295 EE01\n\ngpg --import pgp-key.txt\ngpg --fingerprint 129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01\n\n请确认显示的指纹与上方的指纹一致，然后根据确切的 JSON 文件名验证签名。编辑已签名的 JSON 文件会更改已签名的对象，并使其原始签名失效。有效的签名用于识别已发布的字节；它并非对研究结果的独立验证。\n\nPhishDestroy — 公开调查 — 所有权利均归于全人类\n\nOFAC管辖区域的访问权限：禁止",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "许可与法律免责声明 — 公共领域奉献声明"
          },
          {
            "level": 2,
            "id": null,
            "text": "第一节许可协议 ——从法律角度来看确实如此，但从人情味的角度来说……"
          },
          {
            "level": 3,
            "id": null,
            "text": "一条实际规则（是的，就一条）"
          },
          {
            "level": 2,
            "id": null,
            "text": "第二节这是什么以及它为何存在"
          },
          {
            "level": 2,
            "id": null,
            "text": "第三节致Valve的公开信 — 说真的，看看这个"
          },
          {
            "level": 3,
            "id": null,
            "text": "这笔交易（公开要约，无需律师）"
          },
          {
            "level": 2,
            "id": null,
            "text": "第三节-B盟军资源 — 特别致Steam的一则说明"
          },
          {
            "level": 2,
            "id": null,
            "text": "第四节金钱、禁令，还有这整场闹剧"
          },
          {
            "level": 2,
            "id": null,
            "text": "第五节关于恶意软件这件事 — 是的，我们会提到这一点"
          },
          {
            "level": 2,
            "id": null,
            "text": "声明关于使用和权利"
          },
          {
            "level": 3,
            "id": null,
            "text": "1. 使用无任何限制"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. 这在实际中为何重要，而不仅仅是一种礼节"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. 一切都已经开放了"
          },
          {
            "level": 3,
            "id": null,
            "text": "4. 证据包的完整性"
          },
          {
            "level": 3,
            "id": null,
            "text": "5. 关于登记——为何豁免具有实际作用，而不仅仅是慷慨之举"
          },
          {
            "level": 3,
            "id": null,
            "text": "6. 用联盟自己的话来说，它提供了什么"
          },
          {
            "level": 2,
            "id": null,
            "text": "结语致负责推进此事的任何人"
          },
          {
            "level": 2,
            "id": null,
            "text": "已签署的免责声明签署了什么，以及其涵盖的内容"
          },
          {
            "level": 3,
            "id": null,
            "text": "1. 权利声明 — license-rights.json"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. 已发布的文本 — dossier-text.json"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. 可打印的研究资料包 — steam-dossier-{language}.content.json"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/zh/#briefing-heading",
          "https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "http://web.archive.org/web/20260821155801/https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "https://phishdestroy.io/steam_dossier/zh/investigation_part2.html#outsourcing-case",
          "https://phishdestroy.io/steam_dossier/zh/#theft-ledger",
          "https://steamid.uk/",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/groups/steambans",
          "https://steamcommunity.com/id/killahinstinct_",
          "https://phishdestroy.io/steam_dossier/zh/card_economy.html#governance",
          "https://phishdestroy.io/steam_dossier/zh/license_disclaimer.html",
          "https://github.com/phishdestroy",
          "http://web.archive.org/web/20260911040557/https://github.com/PhishDestroy",
          "https://phishdestroy.io/.well-known/pgp-key.txt",
          "https://steamdestroy.eth/",
          "https://steamdestroy.eth.limo/",
          "https://phishdestroy.eth.limo/",
          "http://web.archive.org/web/20260627040219/https://phishdestroy.eth.limo/",
          "https://phishdestroy.eth/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json.asc",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json.sha256",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json.sha256?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json.sha256?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json.sha256?v=print-20260928-v3"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/zh/license_disclaimer.content.json",
      "export_json_sha256": "93a84051cac37fff96fe41709e510860df4401f34b28024223d70d71b11f8949"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "zh/market_economics.html",
      "language": "zh",
      "title": "一套基础设施，两个市场——《Steam》专题报道",
      "source_url": "https://phishdestroy.io/steam_dossier/zh/market_economics",
      "source_html_sha256": "0ec69d6ac9871418d7874822e692a8e84bfe5a3aff175ad0f33e3c71de5cfa77",
      "exported_at": "2026-09-29T00:21:36.119Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "market_economics.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/zh/market_economics.pdf?v=print-20260929-v5",
        "sha256": "cae23bc765c120d7dde40520c55efb333952143f34644fe1b30f363b3a8f3912",
        "bytes": 506185,
        "pages": 7
      },
      "integrity": {
        "signed_object": "market_economics.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "market_economics.content.json.asc",
        "digest_file": "market_economics.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify market_economics.content.json.asc market_economics.content.json",
          "sha256sum -c market_economics.content.json.sha256"
        ]
      },
      "content": {
        "text": "附件七 · 市场架构 · 20 9月 2026\n市场经济——两种经济模式与上市上限\n\n他们的基础设施。 两个经济体。\n\n本节证明了什么\n\n本章分析了Valve设定的1,800上市上限以及不可提现的钱包余额所导致的系统性市场分化。 通过对38上活跃的外部皮肤交易所（其上市估值约为1.28亿美元）进行调研，本研究证实：高端交易必然会迁移至外部影子平台，同时仍依赖Steam的底层交易和认证基础设施。尽管《订阅协议》中明文禁止商业用途，但Valve在未公布任何执法记录的情况下，仍助长并从中牟利，从而维系了这种双层经济体系。\n\n← 返回高管简报\n\n38 活跃的第三方CS2交易平台，以及Steam自营平台。 在上述任何平台上列出的每款皮肤 都必须通过Steam的库存进行交易，网址为API。Valve的规则禁止对 该基础设施进行商业利用。尽管第三方列出的价值约为1.28亿美元，但迄今为止尚未发现 任何关于执行该规则的公开记录。\n\n$1.28B\n第三方标价 · 38 平台\n53.2M\n显示的优惠 · 38 第三方市场\n70.1K\nSteam 快照中列出的项目\n41×\n第三方估值与Steam的31M美元的对比\n核心发现\n一套基础设施，两个经济体。\n\nSteam 控制着商品、库存和交易。在以下任何平台上售出的每款皮肤 都必须通过 Steam 的交易平台 API 进行——这种结构性依赖关系是肉眼可见的。 Valve的 自有社区市场会从销售额中收取手续费；该手续费是否用于资助，或与 第三方生态系统相关联，本文尚未明确说明。\n\n这对调查为何重要\n1\nValve 的 Steam 订阅协议 禁止商业利用 未经明确许可，不得使用Steam的基础设施。在公开记录中，未发现针对以下平台的此类许可。\n2\nSteam 负责管理身份（OpenID）、库存状态以及交易执行，涉及约1.28B美元的第三方上市资产价值。 如果没有Valve的基础设施，就不会发生任何物品转移。\n3\nSteam 自营的市场拥有 $31M 已挂牌——约为第三方挂牌价值的1/41。1,800的价格上限意味着，超过该上限的卖家必须转至平台外，按市场观察价进行销售。\n4\n248 CS2 物品分类, 这些商品均被两个或两个以上交易平台独立认定为价格超过上限，因此无法在Steam上以实际市场价格出售——而且其中没有任何一款商品在该平台上上架。1,800的上限价格催生了需求，而第三方运营商则填补了这一需求缺口。\nSteam 社区市场：31百万美元第三方估值：1,27600万美元\n1,276百万美元 · 第三方估值 — 完全取决于Steam的交易 API 及 OpenID\nSteam · $31M\n\n来源：PriceEmpire 实时商品目录，20 202026. 标价总和 = 已保存快照中所有四舍五入后的标价卡片之和，Steam 除外。非销量数据。\n\n38 活跃的第三方市场 · 完全依赖于Steam的基础设施\n平台注册\n\n以下平台通过 Steam 的 OpenID 进行登录，并通过 Steam 的 Web API 进行交易。每个被观察到的 openid.realm 经过Steam的登录流程；该注册器会记录观察到的身份验证路由，而不是断言某个特定操作符不具备Valve的权限。\n\n#\t平台\t上市价值\t当前优惠\t项目\t比例尺\n1\tUUSkins\t$133.8M\t3.4M\t30.9K\t\n\n2\tYouPin898\t$127.5M\t5.9M\t29.2K\t\n\n3\tBuff.163\t$104M\t3.5M\t35K\t\n\n4\tMoon.Market\t$100.3M\t2.9M\t20.9K\t\n\n5\tWhite.Market\t$89.6M\t3M\t20.6K\t\n\n6\tBuff.Market\t$86.7M\t1.3M\t33.4K\t\n\n7\tEcosteam\t$82.1M\t3.3M\t30.1K\t\n\n8\tCSFloat\t$67.8M\t2.4M\t27.8K\t\n\n9\tSkin.Land\t$67.4M\t2.2M\t34.6K\t\n\n10\tLIS-SKINS\t$67.4M\t2.2M\t34.6K\t\n\n11\tC5Game\t$54.6M\t4.6M\t29.6K\t\n\n12\tHaloSkins\t$46.6M\t4.4M\t29.3K\t\n\n13\tAvan.Market\t$43.3M\t809.5K\t22.2K\t\n\n14\tWaxpeer\t$40.1M\t1M\t27.3K\t\n\n15\tSteam (official)\t$31M\t32.2M\t70.1K\t\n\n16\tCS.MONEY\t$29M\t748.9K\t28K\t\n\n17\tMarket.CSGO\t$26.3M\t1.3M\t27.6K\t\n\n18\tCS.MONEY Bot\t$25.7M\t614K\t23.8K\t\n\n19\tSkinport\t$16.3M\t3.8M\t31.1K\t\n\n20\tSkinFlow\t$14.1M\t481.8K\t23.6K\t\n\n21\tDMarket\t$12.6M\t948.2K\t35.6K\t\n\n22\tSkins.com\t$11.5M\t83.2K\t15.8K\t\n\n23\tSkin.place\t$6.9M\t380.8K\t11.4K\t\n\n24\tSkinsMonkey\t$6M\t109.4K\t11.6K\t\n\n25\tSkinBaron\t$5M\t2.1M\t21.5K\t\n\n26\tRustTM\t$3M\t33.1K\t4.9K\t\n\n27\tPirateSwap\t$2M\t859.3K\t10.5K\t\n\n28\tMannco.Store\t$1.2M\t223.7K\t11K\t\n\n29\tSkinSwap\t$1.1M\t11.4K\t4K\t\n\n30\tTradeIt\t$967.1K\t29.1K\t11.7K\t\n\n31\tLootFarm\t$896.1K\t162.5K\t28.6K\t\n\n32\tRustskins\t$714.8K\t312.5K\t6.1K\t\n\n33\tBalticSkins\t$599.2K\t28.2K\t4.5K\t\n\n34\tExeSkins\t$442.9K\t2.6K\t1.4K\t\n\n35\tRapidSkins\t$230.9K\t11.6K\t2.3K\t\n\n36\tCS.Trade\t$203K\t19K\t16.7K\t\n\n37\tKrakatoa\t$11.1K\t115\t53\t\n\n38\tShadowPay\t—\t—\t—\t—\n39\t49skins\t—\t—\t—\t—\nSteam的1,800价格上限 · 五大交易平台快照 · 23 9月2026\n价格差距是可以量化的。\n\nSteam 将社区市场挂牌价上限设定为约 $1,800（该结论分别按 $2,000, $、2,070, $、2,300 以及 $2,500 重新计算得出，在 cs2sh-atlas.json 并在每个价位点均保持稳定）。高于该价格的观察数据 无法通过Valve自营平台以市场价格出售 ——但无论在何处销售，它们 仍然依赖于Steam的库存和调拨系统。按价格对整个 产品目录进行分级，便能看出界限所在：Valve的市场涵盖了 95.3% 价格低于其上限的商品类别，以及 1.9% 位于其上方的那些。\n\n五大交易平台：超过Steam上限的商品\n248\n\n在以下日期，最低要价成交价达到1,800的商品类别： 两个或 多个独立的市场，持有18,394上列出的、价值至少为 $78.6M. 其中， 100.0% ——每一家——都没有在 Steam上刊登任何信息。\n\n完整展品： 登记册 → · 价格阶梯图集 →\n\n超过上限的价格分布\n$1,800–$5,000\n174\n$5,000–$10,000\n49\n$10,000–$25,000\n21\n$25,000–$50,000\n2\n$50,000+\n2\n热门商品——五个电商平台中经核实的最低挂盘价\n1贴纸 | 泰坦（全息） | 编号：14$66,285\n2贴纸 | iBUYPOWER（全息） | 型号：14$64,795\n3贴纸 | Reason Gaming (Holo) | 编号：14$42,899\n4★ 运动手套 | 迷宫（FN）$26,812\n5贴纸 | Team Dignitas（全息） | Kat. '14'$23,667\n6EMS 类别：14传奇$22,879\n7★ 运动手套 | 潘多拉之盒 (FN)$21,643\n8EMS 类别“14”挑战者$21,010\n9贴纸 | Vox Eminor（全息） | 编号：14$18,619\n10★ StatTrak™ Navaja 刀 | 蓝钢 (FN)$18,064\n\n要价不等于成交价。经授权的cs2.sh快照，23 9月 2026. 每行数据均 由至少两个交易平台独立报价，且报价均高于上限；单笔挂单的要价以及 超过该商品最低要价三倍的报价均被排除在外。 评分 规则 →\n\nValve的收费标准 · 授权 cs2.sh 截图 · 23 9月 2026\n广告上标明的费用是15%.，大多数职位提供的薪资更高。\n\nValve 从卖家的收益中扣除5% Steam 手续费和10% CS2 发布商费用——即 大家熟悉的15%.。这两项费用均包含 最低0.01，因此任何一笔交易的手续费绝不会低于 两美分。对于构成市场主体的低价、高交易量商品而言， 这一下限才是决定性因素，而非百分比。我们已经计算出了 每一笔交易的 29,635 带有有效Steam要约的物品类型。\n\n77.7%\nSteam上的实时商品列表中，部分商品类型在15%上标价更高\n84.8%\n该商品的 类型 确实按标称利率支付\n4,517\n某些商品的收费高于广告标示的费用\n$0.02\n任何销售均需支付最低手续费，无论价格多少\n这两个数字指向相反的方向，但两者都是正确的\n1\n已计数 按商品类型84.8%,Valve 的收费大致与广告所示一致：29,635 中标价的类型，其费用为或接近15%.\n2\n已计数 按实际挂牌信息，情况则恰恰相反： 18,682,244 24,038,911 实时列表显示的是收费高于15%.的商品类型\n3\n这两点都是正确的，因为过充的类型是 价格低廉、产量大 1,109 中的商品类型收费高于 双 主要利率，仅这些类型就包含14,083,486上的实时房源信息。\n4\n这是简单的算术，而不是一种指控。最低金额已在Valve自己的费用文件中披露。尚未公布的是 它实际上适用于多大比例的市场 ——这正是上图所反映的数据。\n收取的费用占15%总收入的比重\n200%+\n14,083,486\n100-200%\n1,028,438\n50-100%\n700,804\n30-50%\n317,031\n20-30%\n2,258,254\n17.6-20%\n294,231\n\n“费率区间”指的是每个区间内的有效房源数量。标注为“200%+”的区间意味着所收取的费用超过卖家所得款项的15%的两倍。\n\n一道解题示例\n67%\n\n在挂牌交易中，买方需支付 $0.03 因为，卖方会收到 $0.01 而Valve的值是 $0.02 — 这两项各为1美分的最低金额。占买方支付金额的比例为 67%；占卖方所得款项的比例为 200%.\n\n完整数据集： cs2sh-steam-fee-census.json →\n\n同一件物品，在花园内和花园外\n在Steam上购物通常会更贵。几乎总是如此。\n\n对于在 Steam 和至少一个第三方电商平台上均有报价的每件商品，我们对比了 Steam 的最低要价与该平台以外的最低要价。在整个 28,700 就商品而言，Steam 的价格更高 86.4% 大多数情况下，中位数为 +35.7%.\n\n按价格区间划分的Steam保费中位数\n低于0.50\n+48.3%\n$0.50-2\n+36.5%\n$2-10\n+29.6%\n$10-50\n+28.6%\n$50-250\n+36.3%\n$250-1k\n+51.1%\n超过1,000美元\n+67.9%\n\n该曲线呈U形。在Steam上购买最便宜，具体在 $10–$50 两端分别是“band”和“dearest”。\n\n为什么高端市场如此重要\n+67.9%\n\n上方 $1,000, “Steam”房源的中位数价格 67.9% 比该区域外最便宜的房源还要高——而且 1,040 Steam 上总共只有这么少量的此类房源。\n\n当价格超过大约 $1,800 时，就无法再进行比较了，因为 Valve 的规定完全禁止列出该价格区间。Steam 对高于其自身上限的商品的报道是 1.9%. 查看完整排行榜 →\n\n完整数据集： cs2sh-walled-garden-premium.json →\n\n溢价本身并不构成结论：Steam 提供即时交付且无交易对手风险， 买家为此支付费用是合理的。可以量化的则是价差的大小，以及 流经该价差的资金无法回流这一事实——这将在下一节中讨论。\n\n钱进，不花钱\n128.1百万美元已用于无法撤销的订单。\n\nSteam的买单是预先支付的：订单一经 下达，资金便会从买家的钱包中扣除。Steam 钱包资金 无法撤回 — 这些资金只能在 Steam内使用。将所有被追踪项目的买单簿中各价格层级的金额相加，即可得到已锁定、 无法赎回资金的总数。\n\n$128.1M\n已提交的 Steam 买单\n170.6M\n个人出资的买单仍有效\n$105.8M\n其正对面的房源的要价\n$15.9M\n如果每套房源都按要价售出，Valve将获得多少佣金？\n这个数字代表什么，不代表什么\n1\n这是 已实际支付的款项. 每笔已计入的美元均已从钱包中扣除，并作为31,253各类商品的未平仓订单的对应资金。\n2\n这是 非收入 这并非针对Valve资产负债表的指控。流通股的持有地点及登记在谁的名下，本文中并未明确说明。\n3\n这是一个 快照，而非流程. 买家可以取消订单，款项将退回钱包——但仍未从Steam中转出。\n4\n关键就在于这扇“单向门”。在一个无法将虚拟货币兑换成现金的市场中，被盗的虚拟物品才会被变卖。 关闭 Steam 而不是在上面。\n\n方法：将每个被追踪买单簿中的每个价格水平，乘以该 价格水平上的挂单数量。完整数据集： cs2sh-steam-locked-capital.json →\n\n成交价，而非要价 · 单一交易平台 · 过去90天\n实际上，30.9百万美元的交易是在这五层货架中最小的那一层完成的。\n\n一笔高价成交可能是一件稀有工艺品，也可能是廉价基础物品的贴纸版变体（e.g，即一件$30的物品，其单笔成交价为$9,772）。“高价”指的是最高成交价，而非该物品的正常价格。\n\n本页上的其他所有图表所衡量的都是 已列出. 这个测量的是…… 已售出. Skinport 会公布其已完成的交易，在过去 90 天内 这些交易共计 1,219,143 销售 价值 $30,927,032，平均每份25.37美元。\n\n1.22M\n在90天内完成销售，一个电商平台\n$30.9M\n同一时段内的营业额\n$125M\n年化运行率——是一个下限，而非估计值\n~2%\n按市值计算，Skinport在上限以上预留额度中所占的份额\n营业额来自哪里\n低于1\n0.5%\n$1-10\n5.8%\n$10-100\n22.2%\n$100-1k\n59.4%\n$1k-1.8k\n6.9%\n超过Steam的上限\n5.3%\n\n条形图的长度代表成交量；该数值表示该层级在总成交量中所占的比例。 59.4% 在 100–$1k级别的资金流动中，71,437销售额。\n\n在Valve的帽子上方，销售仍在进行\n492\n\n超过Steam价格上限的商品已完成销售，总价值为 $1,643,938，涵盖 76的各类商品——在一家占据该货架约2%份额的市场上。 这些销售交易在Steam上根本无法实现。\n\n完整数据集： cs2sh-offsteam-90d-dynamics.json → · 已实现的高点 →\n\nSkinport 是本文追踪的第三方市场之一，其挂牌价值高于Steam的上限，因此是这五个市场中规模最小的（约占该货架总量的2%）。此处的各项总数仅为Steam经济体的下限，而非其规模的衡量标准。未使用Steam的数据。",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "市场经济——两种经济模式与上市上限"
          },
          {
            "level": 2,
            "id": null,
            "text": "一套基础设施，两个经济体。"
          },
          {
            "level": 2,
            "id": null,
            "text": "平台注册"
          },
          {
            "level": 2,
            "id": null,
            "text": "价格差距是可以量化的。"
          },
          {
            "level": 3,
            "id": null,
            "text": "五大交易平台：超过Steam上限的商品"
          },
          {
            "level": 3,
            "id": null,
            "text": "超过上限的价格分布"
          },
          {
            "level": 3,
            "id": null,
            "text": "热门商品——五个电商平台中经核实的最低挂盘价"
          },
          {
            "level": 2,
            "id": null,
            "text": "广告上标明的费用是15%.，大多数职位提供的薪资更高。"
          },
          {
            "level": 3,
            "id": null,
            "text": "收取的费用占15%总收入的比重"
          },
          {
            "level": 3,
            "id": null,
            "text": "一道解题示例"
          },
          {
            "level": 2,
            "id": null,
            "text": "在Steam上购物通常会更贵。几乎总是如此。"
          },
          {
            "level": 3,
            "id": null,
            "text": "按价格区间划分的Steam保费中位数"
          },
          {
            "level": 3,
            "id": null,
            "text": "为什么高端市场如此重要"
          },
          {
            "level": 2,
            "id": null,
            "text": "128.1百万美元已用于无法撤销的订单。"
          },
          {
            "level": 2,
            "id": null,
            "text": "实际上，30.9百万美元的交易是在这五层货架中最小的那一层完成的。"
          },
          {
            "level": 3,
            "id": null,
            "text": "营业额来自哪里"
          },
          {
            "level": 3,
            "id": null,
            "text": "在Valve的帽子上方，销售仍在进行"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/zh/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/zh/elite_skins.html",
          "https://phishdestroy.io/steam_dossier/zh/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/zh/skin_atlas.html#grading",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-steam-fee-census.json",
          "https://phishdestroy.io/steam_dossier/zh/skin_atlas.html#cliff",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-walled-garden-premium.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-steam-locked-capital.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-offsteam-90d-dynamics.json",
          "https://phishdestroy.io/steam_dossier/zh/skin_atlas.html#highs"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/zh/market_economics.content.json",
      "export_json_sha256": "8bdfd080b4f7f1e27b2b305c70f791ebf4c870ae3e7ce6a08b8d9f3cca4d2ebb"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "zh/regulatory_act_print.html",
      "language": "zh",
      "title": "《法证审计法》：Valve Steam 网站 API 生态系统与商业应用（参考编号：VAL-REG-2026-09）",
      "source_url": "https://phishdestroy.io/steam_dossier/zh/regulatory_act_print",
      "source_html_sha256": "cdbb9337e04b58495cc82a663bd8049146554f2231a199b36be59694c10c2944",
      "exported_at": "2026-09-29T00:21:37.918Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "regulatory_act_print.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/zh/regulatory_act_print.pdf?v=print-20260929-v5",
        "sha256": "91200b15b99135dfcdd3c81f60989c636077ea3a7bfa1a5da61701591a1e90fd",
        "bytes": 466393,
        "pages": 12
      },
      "integrity": {
        "signed_object": "regulatory_act_print.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "regulatory_act_print.content.json.asc",
        "digest_file": "regulatory_act_print.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify regulatory_act_print.content.json.asc regulatory_act_print.content.json",
          "sha256sum -c regulatory_act_print.content.json.sha256"
        ]
      },
      "content": {
        "text": "phishdestroy.io · 法医研究联盟 · 通用公共记录\n案卷： VAL-REG-2026-09-EVID\n来源： phishdestroy.io/steam_dossier/\n权利： 所有权利均归属于全人类\n《法证审计法》及监管附件\nValve Steam 生态系统中的系统化第三方 API 资源配置、自动化绕过架构及合同条款不强制执行\n签发域phishdestroy.io\n目标平台Valve Steam / Steamworks简体中文（大陆）\n主要授权向量Steam OpenID 2.0 / 网站 API\n法律声明《人类的一切权利》（CC0）\n第一部分：行政备忘录与事实认定参考编号：MEMO-SUMMARY-01\n\n本文件是一份正式的法证审计报告，旨在审查Valve公司公布的商业条款、其技术认证端点以及观察到的第三方商业平台之间的运营关联。本次审计通过被动、未经身份验证的网络观察、RDAP注册验证以及公开的Link Filter遥测数据进行。\n\n事实核心： 实证观察表明，Valve 的公开合同声明与其生产基础设施之间存在系统性偏差。 尽管《Steam订阅协议》（SSA）严格禁止未经授权的商业利用（§ 2.G）、自动化机器人/脚本交互（§ 4.C）以及账户转让（§ 1.C），但Valve公司仍持续为至少175家商业实体提供实时、程序化的OpenID身份验证和库存查询基础设施，这些实体产生的二级市场交易量高达数十亿美元。\n\n175\n经审计的商业运营商\n44\n独立域认证主机\n26\n过滤器-拆分代理对\n100%\n未实施的《社会保障法》第2.G条/第4.C条\n0\n强制撤销授权\n适用的合同与法律框架\n《社会保障法》第2.G条\n禁止商业用途： 严禁未经Valve公司事先书面授权，将内容和服务用于商业目的。\n《社会保障法》第4.C条\n自动化限制： 严禁任何脚本、交易机器人、宏或非人工控制的系统与Steam的服务和交易市场进行交互。\n《社会保障法》第1.C条\n个人使用规定： 账户仅限个人使用；明令禁止出售、出租、转让或交易 Steam 用户账户。\n欧盟《数字服务法》（2022/2065）\n系统性风险评估（第34/35条）： 超大型在线平台（VLOPs）必须积极发现、评估并缓解因自动化滥用和未经授权的商业利用而产生的系统性风险。\n第二节：附件账簿 A — 已记录的链接过滤器拆分对（26 路由）参考编号：EX-SPLIT-LEDGER\n\n对分域规避机制的法医分析： 在Valve的Steam链接过滤系统下（steamcommunity.com/linkfilter/?url=...)，当最终用户点击一个指向被标记的赌博或黑市平台的链接时，Valve 会显示一条醒目的警告（“链接已被屏蔽！……被标记为可能具有恶意”)。然而，取证路由追踪显示，26 商业平台运行在 分域架构：虽然主要商业域名在“链接过滤器”中被标记为“被封锁”，但托管 Valve 的 OpenID 响应端点的次要域名却被标记为“安全”。Valve 的 OpenID 服务器会不间断地接受来自这些代理主机的身份验证请求，从而消除用户安全警告，同时继续处理登录操作。\n\n#\t主要商业域名\t主过滤器\tOpenID 身份验证代理域名\t身份验证过滤器\tRDAP 已注册\t捕获依据\n01\trollbit.com\tBLOCKED\trbsnin.com\tCLEAN\t2026-09-18\tPASSIVE_CAPTURE\n02\tskin.club\tBLOCKED\tsc-auth.net\tCLEAN\t2019-04-02\tPASSIVE_CAPTURE\n03\thowl.gg\tBLOCKED\thowl.uno\tCLEAN\t2026-08-11\tPASSIVE_CAPTURE\n04\tduelbits.com\tBLOCKED\tswitchflips.com\tCLEAN\t2020-04-21\tPASSIVE_CAPTURE\n05\tcsgofast.com\tBLOCKED\tsteam-login.authtofast.com\tCLEAN\t2026-06-30\tPASSIVE_CAPTURE\n06\tfarmskins.com\tBLOCKED\tsteam.kobal.cc\tCLEAN\t2017-01-07\tPASSIVE_CAPTURE\n07\tcobaltlab.tech\tBLOCKED\tcobaltauth.com\tCLEAN\t2025-01-07\tPASSIVE_CAPTURE\n08\tcsgo.net\tBLOCKED\tcn2.easylot.net\tCLEAN\t2016-09-03\tPASSIVE_CAPTURE\n09\tggdrop.com\tBLOCKED\tggauth.com\tCLEAN\t2023-05-03\tPASSIVE_CAPTURE\n10\trustchance.com\tBLOCKED\thgfuihd.com\tCLEAN\t2019-01-27\tPASSIVE_CAPTURE\n11\tskin.fans\tBLOCKED\tauth.skinfans.com\tCLEAN\t2018-07-16\tPASSIVE_CAPTURE\n12\tskinport.com\tBLOCKED\tskinport.app\tCLEAN\t2020-06-20\tPASSIVE_CAPTURE\n13\tskins.cash\tBLOCKED\tskinscash.live\tCLEAN\t2019-12-05\tPASSIVE_CAPTURE\n14\ttf2hunt.com\tBLOCKED\trstspcl.com\tCLEAN\t2020-08-08\tPASSIVE_CAPTURE\n15\tdaddyskins.com\tBLOCKED\tgo-go-daddy.com\tCLEAN\t2019-01-26\tPASSIVE_CAPTURE\n16\tkey-drop.com\tBLOCKED\tkdauth.com\tCLEAN\t2026-05-13\tPASSIVE_CAPTURE\n17\tclash.gg\tBLOCKED\tclggauth.com\tCLEAN\t2024-09-16\tPASSIVE_CAPTURE\n18\tc5game.com\tBLOCKED\twww.imbastar.com\tCLEAN\t2016-02-27\tPASSIVE_CAPTURE\n19\tswap.gg\tBLOCKED\tswapauth.com\tCLEAN\t2018-10-06\tPASSIVE_CAPTURE\n20\tshadowpay.com\tBLOCKED\tthelogins.com\tCLEAN\t2018-01-22\tPASSIVE_CAPTURE\n21\tcsgocases.com\tBLOCKED\tlog-1n.com\tCLEAN\t2017-11-27\tPASSIVE_CAPTURE\n22\tcsgogem.com\tBLOCKED\tapi.csgem.com\tCLEAN\t2014-03-08\tPASSIVE_CAPTURE\n23\tgamdom.com\tBLOCKED\tlogin.gambldom.com\tCLEAN\t2017-09-24\tPASSIVE_CAPTURE\n24\t12cs.fail\tBLOCKED\tfail.games\tCLEAN\t2021-08-24\tPASSIVE_CAPTURE\n25\tskinsnipe.com\tBLOCKED\tpricing.tradeupspy.com\tCLEAN\t2020-03-11\tPASSIVE_CAPTURE\n26\tcsgobig.com\tBLOCKED\tletmeinbig.com\tCLEAN\t2023-01-20\tPASSIVE_CAPTURE\n\n* 注：针对 2026-09-19 和 2026-09-21. 上未经验证的 Steam Link Filter 端点执行的被动检查，其原始 HTTP 响应正文和 SHA-256 摘要已保存在存储库数据集（steam_tos_assets/linkfilter-2026-09-22.json）中。\n\n第三部分：B类展品登记簿——175经审计商业实体的全面普查参考编号：EX-175-MASTER-CENSUS\n\n以下登记册详细列出了审计数据库中所有已通过积极验证的175第三方商业平台。每条记录包含实体名称、主要商业域名、观察到的Steam OpenID认证路径、活动分类、合同违约映射（SSA § 2.G、SSA § 4.C、SSA § 1.C）以及源数据集中记录的“行动”字段。 标签“参见带日期的证据”旨在引导读者查阅支持性记录；它并不意味着Valve未采取任何行动。若“行动”字段缺失，则报告为“未确定”。\n\n展品\t实体名称与主域名\t已观察到的身份验证路由/代理\t分类\t违约\tValve 动作\nEX-001\tCSGORoll\ncsgoroll.com\n\t\nwww.csgoroll.com\nDIRECT\n\tSkin Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-002\tCSGOEmpire\ncsgoempire.com\n\t\ncsgoempirelogin4.com\nSPLIT PROXY\n\tCasino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-003\tRollbit\nrollbit.com\n\t\nrbsnin.com\nSPLIT PROXY\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-004\t500 Casino\n500.casino\n\t\nfivezerozero.co\nSPLIT PROXY\n\tLicenced Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-005\tCSGOBig\ncsgobig.com\n\t\ncsgobig.com\nDIRECT\n\tRoulette/Slots\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-006\tCaseDrop\ncasedrop.com\n\t\ncasedrop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-007\tRustReaper\nrustreaper.com\n\t\nrustreaper.com\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-008\tBanditCamp\nbanditcamp.com\n\t\nbanditcamp.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-009\tSkinBox\nskinbox.com\n\t\nskinbox.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-010\tTastyDrop\ntastydrop.com\n\t\ntastydrop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-011\tCSGOPolygon\ncsgopolygon.gg\n\t\ncsgopolygon.gg\nDIRECT\n\tRoulette Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-012\tMagicDrop\nmagicdrop.ru\n\t\nmagicdrop.ru\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-013\tCSDice\ncsdice.com\n\t\ncsdice.com\nDIRECT\n\tDice Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-014\tRustly\nrustly.com\n\t\nrustly.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-015\tSkinOdds\nskinodds.com\n\t\nskinodds.com\nDIRECT\n\tUpgrader Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-016\tCSGOWin\ncsgowin.com\n\t\ncsgowin.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-017\tCSGORun\ncsgorun.net\n\t\ncsgorun.net\nDIRECT\n\tCrash Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-018\tOpenSkins\nopenskins.com\n\t\nopenskins.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-019\tRustBet\nrustbet.com\n\t\nrustbet.com\nDIRECT\n\tRust Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-020\tCSGOMagic\ncsgomagic.com\n\t\ncsgomagic.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-021\tCSGOBounty\ncsgobounty.com\n\t\ncsgobounty.com\nDIRECT\n\tUpgrader/Contract\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-022\tEZSkins\nezskins.com\n\t\nezskins.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-023\tRustCases\nrustcases.com\n\t\nrustcases.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-024\tCSGOReaper\ncsgoreaper.com\n\t\ncsgoreaper.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-025\tCSGOCases\ncsgocases.com\n\t\ncsgocases.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-026\tCSGO-Skins\ncsgo-skins.com\n\t\ncsgo-skins.com\nDIRECT\n\tCase Upgrader\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-027\tCSGONet\ncsgonet.com\n\t\ncsgonet.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-028\tWTFSkins\nwtfskins.com\n\t\nwtfskins.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-029\tCSGOFast\ncsgofast.com\n\t\nsteam-login.authtofast.com\nSPLIT PROXY\n\tRoulette Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-030\tDuelbits\nduelbits.com\n\t\nswitchflips.com\nSPLIT PROXY\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-031\tFlameCases\nflamecases.com\n\t\nflamecases.com\nDIRECT\n\tCase Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-032\tFarmskins\nfarmskins.com\n\t\nsteam.kobal.cc\nSPLIT PROXY\n\tCase Opener\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-033\tCSGOLuck\ncsgoluck.com\n\t\ncsgoluck.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-034\tGamedom\ngamedom.com\n\t\ngamedom.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-035\tSkin.Club\nskin.club\n\t\nsc-auth.net\nSPLIT PROXY\n\tCase Battles\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-036\tDaddySkins\ndaddyskins.com\n\t\ndaddyskins.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-037\tInsane.gg\ninsane.gg\n\t\napi.insane.gg\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-038\tRustix\nrustix.gg\n\t\nrustix.gg\nDIRECT\n\tRust Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-039\tSkins.Club\nskins.club\n\t\nskins.club\nDIRECT\n\tSkin Upgrade\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-040\tCSGOHouse\ncsgohouse.org\n\t\ncsgohouse.org\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-041\tSkinRave\nskinrave.net\n\t\nskinrave.net\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-042\tBloodyCase_GG\nbloodycase.gg\n\t\nbloodycase.gg\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-043\tCSGOClicker\ncsgoclicker.com\n\t\ncsgoclicker.com\nDIRECT\n\tClicker/Upgrade\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-044\tRustBet_GG\nrustbet.gg\n\t\nrustbet.gg\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-045\tCS_Drop\ncs-drop.com\n\t\ncs-drop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-046\tHellStore\nhellstore.net\n\t\nhellstore.net\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-047\tRustLoot\nrustloot.com\n\t\nrustloot.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-048\tCSGO_Case\ncsgo-case.com\n\t\ncsgo-case.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-049\tCS2Skin\ncs2skin.com\n\t\ncs2skin.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-050\tJuice_GG\njuice.gg\n\t\nletmeinjuice.com\nSPLIT PROXY\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-051\tGGDrop\nggdrop.com\n\t\nggauth.com\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-052\tCSGOGem\ncsgogem.com\n\t\ncsgogem.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-053\tRainbet\nrainbet.com\n\t\nservices.rainbet.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-054\tHowl_GG\nhowl.gg\n\t\nhowl.uno\nSPLIT PROXY\n\tSkins Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-055\tChicken_GG\nchicken.gg\n\t\nchicken.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-056\tCSGOCasino_GG\ncsgocasino.gg\n\t\napi.csgocasino.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-057\tHunt_GG\nhunt.gg\n\t\napi.hunt.gg\nDIRECT\n\tSkins Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-058\tCSBattle\ncsbattle.com\n\t\ncsbattle.com\nDIRECT\n\tCase Battles\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-059\tSkinRave_GG\nskinrave.gg\n\t\napi.skinrave.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-060\tCSDouble\ncsdouble.gg\n\t\ncsdouble.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-061\tRustChance\nrustchance.com\n\t\nhgfuihd.com\nSPLIT PROXY\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-062\tRustClash\nrustclash.com\n\t\nrustclash.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-063\tCobaltLab\ncobaltlab.tech\n\t\ncobaltauth.com\nSPLIT PROXY\n\tRust Automation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-064\tRaided_GG\nraided.gg\n\t\napi.raided.gg\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-065\tRustNeo\nrustneo.gg\n\t\nrustneo.gg\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-066\tSplits_GG\nsplits.gg\n\t\nsplits.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-067\tUpgrader_Pro\nupgrader.pro\n\t\nupgauth.space\nSPLIT PROXY\n\tSkin Upgrader\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-068\tSkinFans\nskin.fans\n\t\nauth.skinfans.com\nSPLIT PROXY\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-069\tHotPizza\nhotpizza.one\n\t\nhotpizza.one\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-070\tG4Skins\ng4skins.com\n\t\nauth.g4s.to\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-071\t12CS_Fail\n12cs.fail\n\t\n12cs.fail\nDIRECT\n\tCrash Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-072\tTF2Royal\ntf2royal.com\n\t\ntf2auth.com\nSPLIT PROXY\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-073\tTF2Easy\nwww.tf2easy.com\n\t\nwww.tf2easy.com\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-074\tTF2Hunt\ntf2hunt.com\n\t\nrstspcl.com\nSPLIT PROXY\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-075\tTF2Bet\ntf2.bet/coinflip\n\t\ntf2.bet\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-076\tTF2Blaze\ntf2blaze.com\n\t\ntf2blaze.com\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-077\tOpenStars_GG\nopenstars.gg\n\t\nopenstars.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-078\tShuffle_Com\nshuffle.com\n\t\nshuffle.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-079\tSkins.com\nskins.com\n\t\napi.skins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-080\tWhite.Market\nwhite.market\n\t\nwhite.market\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-081\tBuff.Market\nbuff.market\n\t\nbuff.market\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-082\tAvan.Market\navan.market\n\t\navan.market\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-083\tCS.MONEY\ncs.money\n\t\nauth.dota.trade\nSPLIT PROXY\n\tTrading Engine\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-084\tUUSkins\nuuskins.com\n\t\nuuskins.com\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-085\tYouPin898\nyoupin898.com\n\t\nyoupin898.com\nDIRECT\n\tMass Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-086\tMoon.Market\nmoon.market\n\t\nmoon.market\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-087\tCSFloat\ncsfloat.com\n\t\ncsgofloat.com\nSPLIT PROXY\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-088\tSkin.Land\nskin.land\n\t\nauth.skin.land\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-089\tC5Game\nc5game.com\n\t\nc5game.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-090\tHaloSkins\nhaloskins.com\n\t\nhaloskins.com\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-091\tBuff.163\nbuff.163.com\n\t\nbuff.163.com\nDIRECT\n\tCorporate Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-092\tWaxpeer\nwaxpeer.com\n\t\nwaxpeer.com\nDIRECT\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-093\tCS.MONEY Bot\ncs.money\n\t\nauth.dota.trade\nSPLIT PROXY\n\tBot Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-094\tMarket.CSGO\nmarket.csgo.com\n\t\ndota2.net\nSPLIT PROXY\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-095\tSkinport\nskinport.com\n\t\nskinport.app\nSPLIT PROXY\n\tRegulated Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-096\tSkinFlow\nskinflow.gg\n\t\napi.skinflow.gg\nDIRECT\n\tMarketplace/Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-097\tDMarket\ndmarket.com\n\t\ndmarket.com\nDIRECT\n\tUS Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-098\tSkin.place\nskin.place\n\t\napi.skin.place\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-099\tSkinsMonkey\nskinsmonkey.com\n\t\nskinsmonkey.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-100\tSkinBaron\nskinbaron.de\n\t\nskinbaron.com\nSPLIT PROXY\n\tCorporate Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-101\tSteam\nsteamcommunity.com/market\n\t\nsteamcommunity.com/market\nDIRECT\n\tOfficial Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-102\tRustTM\nrust.tm\n\t\ndota2.net\nSPLIT PROXY\n\tRust Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-103\tPirateSwap\npirateswap.com\n\t\nlogin.pirateswap.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-104\tMannco.Store\nmannco.store\n\t\nmannco.store\nDIRECT\n\tTF2 Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-105\tSkinSwap\nskinswap.com\n\t\napi.skinswap.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-106\tLootFarm\nlootfarm.com\n\t\nlootfarm.com\nDIRECT\n\tTrading Platform\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-107\tRustskins\nrustskins.com\n\t\nrustskins.com\nDIRECT\n\tRust Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-108\tExeSkins\nexeskins.com\n\t\nexeskins.com\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-109\tBalticSkins\nbalticskins.com\n\t\nbalticskins.com\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-110\tCS.Trade\ncs.trade\n\t\ncs.trade\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-111\tRapidSkins\nrapidskins.com\n\t\napi.rapidskins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-112\tTradeIt\ntradeit.gg\n\t\nconnect-tradeit.com\nSPLIT PROXY\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-113\tKrakatoa\nkrakatoa.com\n\t\nkrakatoa.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-114\tShadowPay\nshadowpay.com\n\t\nshadowpay.com\nDIRECT\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-115\t49skins\n49skins.com\n\t\napi.49skins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-116\tSkinVault\nskinvault.gg\n\t\napi.skinvault.gg\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-117\tAim Market\naim.market\n\t\naim.market\nDIRECT\n\tSkins Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-118\tSkinout\nskinout.gg\n\t\nauth.skinout.gg\nDIRECT\n\tInstant Sell Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-119\tNTSkins\nntskins.com\n\t\nntskins.com\nDIRECT\n\tSkins Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-120\tIGXE\nigxe.cn\n\t\nigxe.cn\nDIRECT\n\tChinese Powerhouse\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-121\tSwap.gg\nswap.gg\n\t\nswap.gg\nDIRECT\n\tAutomated Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-122\tBitskins\nbitskins.com\n\t\nbitskins.com\nDIRECT\n\tCash-out Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-123\tGamerPay\ngamerpay.gg\n\t\ngamerpay.gg\nDIRECT\n\tP2P Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-124\tTF2Mart\ntf2mart.com\n\t\ntf2mart.com\nDIRECT\n\tTF2 Automation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-125\tSkinBid\nskinbid.com\n\t\nskinbid.com\nDIRECT\n\tSkin Auctions\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-126\tLootBear\nlootbear.com\n\t\nlootbear.com\nDIRECT\n\tSkin Rental\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-127\tBackpack.tf\nbackpack.tf\n\t\nbackpack.tf\nDIRECT\n\tTF2 Valuation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-128\tScrap.tf\nscrap.tf\n\t\nscrap.tf\nDIRECT\n\tTF2 Scrap Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-129\tMarketplace.tf\nmarketplace.tf\n\t\nmarketplace.tf\nDIRECT\n\tTF2 Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-130\tSTNTrading\nstntrading.eu\n\t\nstntrading.eu\nDIRECT\n\tTF2 Botnet\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-131\tSkins.Cash\nskins.cash\n\t\nskinscash.live\nSPLIT PROXY\n\tInstant Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-132\tSkinWallet\nskinwallet.com\n\t\nskinwallet.com\nDIRECT\n\tInstant Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-133\tDota2Market\ndota2market.com\n\t\ndota2market.com\nDIRECT\n\tDota 2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-134\tCSGO.NET\ncsgo.net\n\t\ncn2.easylot.net\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-135\tCybershoke\ncybershoke.net\n\t\nauth.cybershoke.net\nDIRECT\n\tCommunity Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-136\tXPlay_GG\nxplay.gg\n\t\nxplay.gg\nDIRECT\n\tServer Network\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-137\tFastCup\nfastcup.net\n\t\napi.fastcup.net\nDIRECT\n\tMatchmaker Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-138\tEsportal\nesportal.com\n\t\nesportal.com\nDIRECT\n\tMatchmaking Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-139\tGamersClub\ngamersclub.com.br\n\t\ngamersclub.com.br\nDIRECT\n\tLATAM Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-140\tLeetify\nleetify.com\n\t\nleetify.com\nDIRECT\n\tSaaS Analytics\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-141\tScope_GG\nscope.gg\n\t\nscope.gg\nDIRECT\n\tSaaS Analytics\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-142\tTradeUpSpy\ntradeupspy.com\n\t\napi.tradeupspy.com\nDIRECT\n\tSaaS Tools\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-143\tEpidemic_GG\nepidemic.gg\n\t\nepidemic.gg\nDIRECT\n\tSaaS Tools\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-144\tCSDeals\ncs.deals\n\t\napi.cs.deals\nDIRECT\n\tMarketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-145\tPricempire\npricempire.com\n\t\npricempire.com\nDIRECT\n\tSaaS Price DB\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-146\tCS2Stash\ncs2stash.com\n\t\ncs2stash.com\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-147\tCSGOSkins\ncsgoskins.gg\n\t\ncsgoskins.gg\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-148\tSteamAnalyst\nsteamanalyst.com\n\t\nsteamanalyst.com\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-149\tSteamCardExchange\nsteamcardexchange.net\n\t\nsteamcardexchange.net\nDIRECT\n\tTrading Exchange\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-150\tDotaBuff\ndotabuff.com\n\t\ndotabuff.com\nDIRECT\n\tSaaS Tracker\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-151\tTracker_GG\ntracker.gg\n\t\ntracker.gg\nDIRECT\n\tSaaS Tracker\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-152\tFSB Market (an anonymized label; the original name is withheld here)\nFSB Market\n\t\nFSB Market\nDIRECT\n\tMass Blackmarket\tSSA § 2.G, SSA § 4.C, SSA § 1.C\tSee dated evidence\nEX-153\tFunPay\nfunpay.com\n\t\nfunpay.com\nDIRECT\n\tAccount Exchange\tSSA § 2.G, SSA § 4.C, SSA § 1.C\tSee dated evidence\nEX-154\tPlayerAuctions\nplayerauctions.com\n\t\nplayerauctions.com\nDIRECT\n\tGrey Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-155\tEldorado.gg\neldorado.gg\n\t\neldorado.gg\nDIRECT\n\tAccount Portal\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-156\tG2A\ng2a.com\n\t\ng2a.com\nDIRECT\n\tMass Key Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-157\tKinguin\nkinguin.net\n\t\nkinguin.net\nDIRECT\n\tMass Key Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-158\tG2G.com\ng2g.com\n\t\ng2g.com\nDIRECT\n\tVirtual Services\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-159\tPlayerup\nplayerup.com\n\t\nplayerup.com\nDIRECT\n\tAccount Broker\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-160\tZ2U.com\nz2u.com\n\t\nwww.z2u.com\nDIRECT\n\tReady-Account Hub\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-161\tSmurfHub\nsmurfhub.net\n\t\nsmurfhub.net\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-162\tSmurfAccounts\nsmurfaccounts.com\n\t\nsmurfaccounts.com\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-163\tBuyCSGORank\nbuycsgorank.com\n\t\nbuycsgorank.com\nDIRECT\n\tRank Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-164\tCSGOSmurfKings\ncsgosmurfkings.com\n\t\ncsgosmurfkings.com\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-165\tSmurfStore_Co\nsmurfstore.co\n\t\nsmurfstore.co\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-166\tSteamLvlUp\nsteamlvlup.com\n\t\nsteamlvlup.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-167\tSteamLevels\nsteamlevels.com\n\t\nsteamlevels.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-168\tLevelSteam\nlevelsteam.com\n\t\nlevelsteam.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-169\tSteamLevelU\nsteamlevelu.com\n\t\nsteamlevelu.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-170\tEloKing\neloking.com\n\t\neloking.com\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-171\tBoosteria\nboosteria.org\n\t\nboosteria.org\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-172\tOvergear\novergear.com\n\t\novergear.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-173\tBlazingBoost\nblazingboost.com\n\t\nblazingboost.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-174\tDota2Boost\ndota2boost.com\n\t\ndota2boost.com\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-175\tBuyBoost\nbuyboost.com\n\t\nbuyboost.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\n第四节：技术架构与身份验证机制参考编号：TECH-ANALYSIS-01\n\n1. OpenID 中缺乏域名所有权验证 2.0: Valve 对 OpenID 2.0 协议的实现（https://steamcommunity.com/openid/login) 评估了 openid.return_to 以及 openid.realm 无需开发者事先注册、加密挑战验证或域名所有权验证即可获取相关参数。任何商业运营商均可将用户引导至 Valve 的登录界面，并接收一份经加密签名的身份声明（其中包含 64-格式的 SteamID），该声明会被重定向至任意域名。\n\n2. 程序化广告库存查询及API密滥用： 一旦通过 OpenID 确认用户身份验证，运营商便会向公共和合作伙伴的 Web API 端点发起查询（IEconItems_730/GetPlayerItems) 以实时对库存资产进行索引。自动化交易网络利用程序化会话令牌来提交、查询和接受点对点（P2P）交易要约，这直接违反了《SSA》第4.C条关于禁止非人类交互的规定。\n\n3. 链路过滤不对称： 面向消费者的域名警告与功能完好的身份验证端点并存，这造成了监管上的矛盾：Valve 的安全遥测系统将这些运营商归类为“潜在恶意”对象，但 Valve 的身份验证基础设施仍在为其用户群提供身份验证服务。\n\n证据方法与证据保管链声明\n\n本文件基于未经身份验证的网络捕获数据、RDAP历史注册表查询结果以及经过验证的加密哈希清单生成。未对任何用户登录凭据进行泄露测试或处理。所有发现均反映截至9月2026.的生产网络可观察状态。本文件作为一份无党派的技术证据，供司法、监管及公众调查使用。\n\n摘要： SHA-256已验证\nc507c9025f93da0aadaf395c4d8882f25973211c318ee8e9b6f18a5b3755e050\n存档： 公开法律记录\n签发并签署人： phishdestroy.io · 法医研究联盟\n法律地位： 所有权利均归属于全人类 · CC0 通用公有领域",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "《法证审计法》及监管附件"
          }
        ],
        "links": []
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/zh/regulatory_act_print.content.json",
      "export_json_sha256": "317db85fe43267cdcf8b489402c311c79a82ad0add70b3da48f0f7221446c4fe"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "zh/security_timeline.html",
      "language": "zh",
      "title": "安全时间线——《Steam》档案",
      "source_url": "https://phishdestroy.io/steam_dossier/zh/security_timeline",
      "source_html_sha256": "13f74cd64d3d1b8b39cf1a012bcc7b954984b8fbb1949cb09b48d9dca47ac0e6",
      "exported_at": "2026-09-29T00:21:39.422Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "security_timeline.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/zh/security_timeline.pdf?v=print-20260929-v5",
        "sha256": "4cbb8e5fe28bf663c8c7230319f7c5471afd238a5b0f4eb84620af4698d6797d",
        "bytes": 507660,
        "pages": 6
      },
      "integrity": {
        "signed_object": "security_timeline.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "security_timeline.content.json.asc",
        "digest_file": "security_timeline.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify security_timeline.content.json.asc security_timeline.content.json",
          "sha256sum -c security_timeline.content.json.sha256"
        ]
      },
      "content": {
        "text": "安全记录展览 / 《16》参展作品\n\n2018 — 2026\n\n安全时间线——2018 至 2026\n\n安保措施发生了变化。 请参考记录。\n\n本节证明了什么\n\n这份时间线记录重构了Steam交易和身份验证体系在八年间的安全改进历程。它追踪了2018 7-的日交易持仓功能实施情况、2023 Web API的移动端关键确认机制，以及2026针对已记录绕过技术而进行的会话令牌弃用情况。该时间线表明，平台更新始终滞后于已知的漏洞利用途径，同时仍为商业运营商保留了结构性优势。\n\n← 返回高管简报\n\n交易锁定。登录控制。API 限制。一份过时的记录，记载了哪些内容发生了变化——以及相关资料实际上证实了什么。\n\n浏览时间轴 ↓\n八年。一张专辑。16需要审查的里程碑\n\n每条记录都会保留其提交日期和来源。验证结果会显示在记录旁边。\n\n已审核 / 24 9月2026\n10已确认的活动及日期\n06部分已核实\n00源不匹配\n00需要来源\n如何阅读此记录\n\n已核实的活动及日期： 这两点都有通俗易懂的一手资料作为依据。 部分已核实： 已记录了一项相关变更，但具体日期或范围尚未确定。 源代码不匹配： 所提供的链接材料无法支持所提出的主张。 需要来源： 本次审查中未核实到任何日期相符的来源。某条未得到证实的条目并不能证明该事件未曾发生。\n\n未解决条目中的日期为提交日期，而非经核实的发布日期。原始调查文本未作改写。\n\n年表\n01 — 16\n搜索记录主题证据订单\n\n16 16条目 · 按时间倒序排列\n\n202609-01提交日期\n社区部分已核实\n群聊中的可疑消息警告\n\n一份官方测试版公告证实，该功能将于31年8月上线。所提供的1年9月稳定版发布日期仍需具体的发布说明。\n\nSteam 客户端测试版——8月31日 ↗存档链接：2026-03-13 ↗\n原始条目及提交的链接\n\n可疑聊天自动标记\n\n检查提交的源代码 ↗\n202601-16验证日期\nAPI已确认的活动及日期\n发布者密钥的精细化权限控制与 IP 白名单功能（Valve 公告）\n\n16年1月2026,日，Valve发布了一则关于Steamworks的官方公告（“新功能：针对 Web API 密钥的更完善的权限和控制”) 证实了新的精细化权限管理工具，允许开发者将 Web API 密钥划分为独立的组（概述、微交易、经济系统及销售数据)，将密钥限制在特定的 App ID 范围内，并强制执行服务器 IP 白名单机制。\n\n赤裸裸的双重标准： 本官方公告确认，Valve 已全面开发了用于精细化 API 权限设置和 IP 限制的技术基础设施，但 故意不向普通用户账户提供这些功能（steamcommunity.com/dev/apikey). 普通用户API密钥仍然是单一的、非此即彼的凭证，且不支持IP白名单——而正是这一技术上的疏漏，催生了价值数百万美元的API交易拦截产业。\n\nValve 公告 — 新增功能：针对 Web API 密钥的更完善的权限和控制功能（16 Jan 2026） ↗· 文档：Steamworks Web API 身份验证 ↗\n原始条目及提交的链接\n\nSteamworks Web API 细粒度范围\n\n查看《Valve》的官方 Steamworks 公告（493839547938902179）↗\n202507-15验证日期\n交易已确认的活动及日期\nCS2交易获得七天反转窗口\n\nValve 发布的公告中提到，将撤销过去七天内的《反恐精英》道具交易。虽然此举旨在遏制账户劫持行为，但第三方经济审计（CSMarketCap ↗) 记录了 $104M (-25%) 折叠 由于现金交易中断，24小时内市值出现波动。据分析显示， Skinvault ↗，触发反向操作将导致该账户自动被30-日间交易禁令锁定。今年夏天，2026, Valve 将重置机制从全球统一的UTC午夜重置，改为针对每项操作的独立分钟计时器（Skin.land ↗).\n\nValve — 15 7月2025公告 ↗· CSMarketCap 分析 ↗\n原始条目及提交的链接\n\nCS2 交易保护 / 撤单窗口\n\n检查提交的源代码 ↗\n202505-14验证日期\n身份验证已确认的活动及日期\nValve 发布关于短信泄露的账户安全警告\n\nValve 于 5 月 14, 发布的官方公告 2025, 涉及账户安全及基于短信的身份验证器。尽管该公告主要关注短信泄露问题，并确认 Steam 系统未遭入侵，但它作为截至发布日期的官方安全更新具有重要意义。\n\nValve — 关于您的 Steam 账户安全的一则提示 ↗\n原始条目及提交的链接\n\n账户安全公告\n\n检查提交的源代码 ↗\n202410-02验证日期\n交易已确认的活动及日期\n再次交易或再次销售前的七天\n\n此版本说明涵盖了通过游戏内商店获得的物品，包括军械库、交易要约和社区市场。其涵盖范围不仅限于军械库中的物品。\n\nValve — 10/2/2024 版本说明 ↗\n原始条目及提交的链接\n\nCS2 军械库 / 7-Day Hold\n\n检查提交的源代码 ↗\n202409-18提交日期\n交易部分已核实\n已在“帮助页面”上验证了新设备限制\n\nSteam 的官方支持文档证实，当从一台至少 7 天未获授权的新设备登录时，7-会实施日内交易限制。虽然 9 月 18, 2024, 的确切上线日期并未作为变更日志中的里程碑记录，但该功能已在文档中进行了完整说明。\n\nSteam 支持 — 交易与市场限制 ↗\n原始条目及提交的链接\n\n新设备登录交易限制\n\n检查提交的源代码 ↗\n202402-14提交日期\n社区部分已核实\n在2024中实现了改名交易冷却时间\n\n社区和开发者记录证实，2024,年初，Valve在用户更改个人资料名称后，立即引入了一项未经预告的2-至4小时交易冷却期，以遏制快速冒充诈骗行为。由于Valve未就该限制发布任何官方新闻稿、客户端更新日志或支持文章，因此提交的2月14这一日期缺乏正式验证；Steam Workshop指南仅作为社区的间接佐证，而非官方Valve文档。\n\nSteam 研讨会指南（间接佐证）——更名限制详情 ↗\n原始条目及提交的链接\n\n个人资料名称/头像更改暂缓\n\n检查提交的源代码 ↗\n202312-04验证日期\nAPI已确认的活动及日期\n生成密钥需要手机验证\n\n根据第三方开发者库的记录，已证实Web API 密钥生成过程中强制使用Steam Guard移动端确认功能是在2023,晚些时候推出的。开发者社区观察到的具体推出时间段为12月4, 2023,。\n\n维护者文档 — 3月 2024 ↗存档 2026-09-24 ↗\n原始条目及提交的链接\n\nAPI密钥的手机验证\n\n检查提交的源代码 ↗\n202310-24验证日期\n开发者已确认的活动及日期\n关于设置正式服游戏版本的强制性2FA现已生效\n\nValve 于 10 月 10, 发布的官方 Steamworks 公告 2023, 确认，自 10 月 24, 起 2023,，任何在已发布应用程序的默认分支上将构建版本设为上线状态的账户，都必须通过短信或 Steam 移动应用授权该更改。此变更已直接更新了 SetAppBuildLive Web API。\n\nSteamworks — 针对构建和用户管理的安全性改进 ↗存档链接：2025-12-03 ↗\n原始条目及提交的链接\n\n游戏构建发布中的短信多因素认证（MFA）\n\n检查提交的源代码 ↗\n202307-12提交日期\n社区部分已核实\n社区观察到的自定义个人简介内容警告\n\nSteam 从7月开始，社区报告（2023）显示，包含外部链接或触发词的自定义个人简介开始显示自动生成的内容警告。提交日期为7月12,（2023,），这与Steam社区论坛上用户报告的最初一波时间相吻合。\n\nSteam 社区论坛 — 个人简介内容警告报告 ↗\n原始条目及提交的链接\n\n自定义个人简介内容警告\n\n检查提交的源代码 ↗\n202301-25提交日期\n社区部分已核实\n个人资料链接过滤和编辑的冷却时间已生效\n\nSteam的官方支持文档证实，自定义简介中的链接会受到过滤，而滥用名称或头像的行为可能会触发编辑禁令。虽然4-上1月25, 2023,实施的1小时冷却期标志着该功能的正式启用，但根据提交的帮助页面显示，链接过滤机制本身早已全面生效。\n\nSteam 支持 — 个人资料名称和头像限制 ↗\n原始条目及提交的链接\n\n个人资料链接已删除 / 冷却时间\n\n检查提交的源代码 ↗\n202210-24验证日期\n身份验证已确认的活动及日期\nSteam 客户端向 OAuth 刷新令牌和访问令牌的过渡\n\nValve 10月份的主要客户端和移动应用更新 2022 对 Steam 的身份验证系统进行了全面改造。旧的会话 Cookie 结构已被基于 OAuth 的访问令牌和刷新令牌所取代，并引入了“活跃授权设备”列表，以便手动撤销活跃会话。\n\nValve — Steam 移动应用更新及身份验证系统全面升级 ↗\n原始条目及提交的链接\n\nSteam 登录功能全面升级 / Cookie 截断\n\n查看Valve公告 ↗\n202210-12验证日期\n身份验证已确认的活动及日期\n二维码签到和授权设备管理\n\nValve 在 10 月发布的《12》公告中介绍了二维码签到、签到审批或拒绝，以及可用于撤销账户访问权限的设备列表。\n\nValve — 更新后的Steam移动应用现已上线 ↗\n原始条目及提交的链接\n\nSteam 移动应用 3.0 / 二维码登录\n\n检查提交的源代码 ↗\n202205-10提交日期\nAPI部分已核实\n已从公开的 API 列表中移除交易取消端点\n\n开发者记录证实，5月 2022, Valve 已悄然从 Web API 中移除了 IEconService/CancelTradeOffer 和 DeclineTradeOffer 等交易管理端点（详见 node-steam-tradeoffer-manager #325）。 尽管这些方法在私有客户端协议中仍可正常使用，但5月10, 2022,这一日期标志着它们已从公共Web API中正式移除，此举旨在打击诈骗面板。\n\n开发者讨论 — 问题编号 #325（已移除 CancelTradeOffer） ↗· Steamworks Web API — IEconService 文档 ↗\n原始条目及提交的链接\n\n删除交易取消端点\n\n查看 node-steam-tradeoffer-manager 问题 #325 ↗\n202005-25验证日期\n交易已确认的活动及日期\n《Dota》2中的道具将设有7天的交易冷却期\n\n5月25,，2020, 配合《国际邀请赛》10 战斗通行证的发布（blog.dota2.com/2020/05/the-international-10-battle-pass/），Valve 对《Dota》2 物品实施了7-天的交易锁定，该政策与2018《反恐精英》的政策保持一致。此限制适用于所有交易物品及市场购买的物品。\n\nDota 2 社区 — 交易锁定与 TI10 客户端更新 ↗\n原始条目及提交的链接\n\nDota 2 / 7-日内交易锁定\n\n检查提交的源代码 ↗\n201803-29验证日期\n交易已确认的活动及日期\n交易过的《CS:GO》道具将进入为期七天的冷却期\n\n官方发布说明确认了日期和限制条件。提供的网址重定向到了一个 2013 的地图更新页面；对应的发布说明网址以 20309. 结尾。\n\nValve — 3/29/2018 版本说明 ↗\n原始条目及提交的链接\n\nCS:GO / 《7-》日内交易锁定\n\n检查提交的源代码 ↗ 存档链接：2025-02-26 ↗\n\n遵循证据。核查来源。\n\n返回调查 ↗",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "安全时间线——2018 至 2026"
          },
          {
            "level": 2,
            "id": null,
            "text": "年表"
          },
          {
            "level": 2,
            "id": null,
            "text": "群聊中的可疑消息警告"
          },
          {
            "level": 2,
            "id": null,
            "text": "发布者密钥的精细化权限控制与 IP 白名单功能（Valve 公告）"
          },
          {
            "level": 2,
            "id": null,
            "text": "CS2交易获得七天反转窗口"
          },
          {
            "level": 2,
            "id": null,
            "text": "Valve 发布关于短信泄露的账户安全警告"
          },
          {
            "level": 2,
            "id": null,
            "text": "再次交易或再次销售前的七天"
          },
          {
            "level": 2,
            "id": null,
            "text": "已在“帮助页面”上验证了新设备限制"
          },
          {
            "level": 2,
            "id": null,
            "text": "在2024中实现了改名交易冷却时间"
          },
          {
            "level": 2,
            "id": null,
            "text": "生成密钥需要手机验证"
          },
          {
            "level": 2,
            "id": null,
            "text": "关于设置正式服游戏版本的强制性2FA现已生效"
          },
          {
            "level": 2,
            "id": null,
            "text": "社区观察到的自定义个人简介内容警告"
          },
          {
            "level": 2,
            "id": null,
            "text": "个人资料链接过滤和编辑的冷却时间已生效"
          },
          {
            "level": 2,
            "id": null,
            "text": "Steam 客户端向 OAuth 刷新令牌和访问令牌的过渡"
          },
          {
            "level": 2,
            "id": null,
            "text": "二维码签到和授权设备管理"
          },
          {
            "level": 2,
            "id": null,
            "text": "已从公开的 API 列表中移除交易取消端点"
          },
          {
            "level": 2,
            "id": null,
            "text": "《Dota》2中的道具将设有7天的交易冷却期"
          },
          {
            "level": 2,
            "id": null,
            "text": "交易过的《CS:GO》道具将进入为期七天的冷却期"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/zh/#briefing-heading",
          "https://steamcommunity.com/groups/SteamClientBeta?l=english",
          "http://web.archive.org/web/20260313235409/https://steamcommunity.com/groups/SteamClientBeta?l=english",
          "https://store.steampowered.com/news/posts/?enddate=1788390000",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/493839547938902179",
          "https://partner.steamgames.com/doc/webapi_overview/auth",
          "https://csmarketcap.com/blog/market-insights/from-boom-to-bust-cs2s-trade-protection-impact",
          "https://skinvault.gg/blog/cs2-trade-protection-explained/",
          "https://skin.land/blog/steam-changes-cs2-trade-ban-logic-timing/",
          "https://store.steampowered.com/news/posts/?appids=730&amp;enddate=1753924057&amp;feed=steam_announce%2F1000",
          "https://help.steampowered.com/faqs/view/3041-A87A-E5F6-B6AC",
          "https://store.steampowered.com/news/posts/?enddate=1747349559",
          "https://steamcommunity.com/ogg/593110/announcements/detail/533224478739530146",
          "https://store.steampowered.com/news/posts/?appids=730&amp;enddate=1728000977&amp;feed=steam_community_announcements",
          "https://steamcommunity.com/games/CSGO/announcements/detail/4447966961421256740",
          "https://help.steampowered.com/faqs/view/7F77-9E92-31E0-6B8E",
          "https://steamcommunity.com/sharedfiles/filedetails/?id=2926756889",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "http://web.archive.org/web/20260924181824/https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "https://steamcommunity.com/dev/apikey",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3749866608167579206",
          "http://web.archive.org/web/20251203174259/https://steamcommunity.com/groups/steamworks/announcements/detail/3749866608167579206",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3734103130194459461",
          "https://steamcommunity.com/discussions/forum/1/3807266184852932971/",
          "https://help.steampowered.com/faqs/view/225C-C51E-B8F0-55B2",
          "https://store.steampowered.com/news/group/4/view/3314112260640237775",
          "https://store.steampowered.com/news/posts/?appgroupname=Keep+in+touch&amp;enddate=1666122699&amp;feed=steam_blog",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/issues/325",
          "https://partner.steamgames.com/doc/webapi/IEconService",
          "https://steamcommunity.com/app/570/announcements/",
          "https://blog.dota2.com/2020/05/trading-cooldown/",
          "https://blog.counter-strike.net/2018/03/20309/",
          "https://blog.counter-strike.net/index.php/2018/03/20308/",
          "http://web.archive.org/web/20250226114333/https://blog.counter-strike.net/index.php/2018/03/20308/",
          "https://phishdestroy.io/steam_dossier/zh/#vulnerability-profile"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/zh/security_timeline.content.json",
      "export_json_sha256": "e0bc4f54efa4f67aeb2f5808341ca0bc80725045273fa2d23dd35a95c394b935"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "zh/skin_atlas.html",
      "language": "zh",
      "title": "《Steam无法承载的事物图鉴》——《Steam》专题报道",
      "source_url": "https://phishdestroy.io/steam_dossier/zh/skin_atlas",
      "source_html_sha256": "5dc7ff2092a20354e1126f5e2e2739259577e6c09f3c860bcd8f1170bc9f55da",
      "exported_at": "2026-09-29T00:21:42.674Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "gallery",
            "source": "https://phishdestroy.io/steam_dossier/zh/skin_atlas#gallery"
          }
        ],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "skin_atlas.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/zh/skin_atlas.pdf?v=print-20260929-v5",
        "sha256": "d5370ecbf04c028fe648ca9437dd15f1f00a1538d8c073a5ec767261ebfd9169",
        "bytes": 660680,
        "pages": 12
      },
      "integrity": {
        "signed_object": "skin_atlas.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "skin_atlas.content.json.asc",
        "digest_file": "skin_atlas.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify skin_atlas.content.json.asc skin_atlas.content.json",
          "sha256sum -c skin_atlas.content.json.sha256"
        ]
      },
      "content": {
        "text": "附件 IV-B / 价格梯度 / 2026-09-23\n“皮肤价格阶梯图集”——流动性悬崖\n\nValve的交易停牌 金钱的源头。\n\n本节证明了什么\n\n本可视化图集分析了五个市场平台商品目录中30,266的商品类别，并衡量了超过和低于Valve商品上架门槛的市场覆盖情况。 在1,800上限之下，Steam拥有95.3%个活跃类别；一旦超过该上限，官方覆盖范围便骤降至1.9%（其中0.0%覆盖范围涉及经核实的资产）。这表明存在一个突兀的、结构性的流动性断崖：Valve将高价值交易的发现功能委托给外部平台，同时保留对底层资产托管的完全控制权。\n\n← 返回高管简报\n\n每个在五个交易平台上都有实时价格的CS2物品，均根据其最低卖价被划入相应的价格区间，而每个区间的衡量标准只有一个：Valve自家的社区市场在该区间内仍占据多大份额。在Valve的上架数量上限之下，答案是 95.3%. 在它上面，答案是 1.9%. 这种下降并非循序渐进，也不会随着需求下降而下降——而是完全按照公布的规则进行。在 248 对于那些两个或多个电商平台独立定价均超过上限的商品类别，100.0% 根本没有 Steam 上的相关商品列表。\n\n看那悬崖 ↓打开419商品图库方法与限制\n30,266所测量的项目类别\n95.3%Steam持有的次级资本项目\n1.9%Steam 销售的超出限额的商品\n$78.6M已验证集合的下界\n01 / 测量\n悬崖是基于规则而存在的，而非基于需求\n\n以下30,266的每个商品类别均根据其 最便宜的 在BUFF163、CSFloat、Skinport、YouPin 898 和C5Game上进行实时查询，仅统计在其中两个或以上平台上被提及的项目，因此任何单个乐观的列表都无法凭空捏造乐队成员。上图显示了Valve自有市场中各乐队目前仍占有的份额。\n\nSteam社区市场各价格区间所占比例\n上图：Steam覆盖率 · 下图：每档的物品数量，对数刻度\n0%\n25%\n50%\n75%\n100%\n100%\n96.9%\n95.9%\n97.3%\n91.1%\n76.8%\n14.5%\n2.9%\n1.5%\n0%\n0%\n0%\n4,632\n1¢–10¢\n7,152\n10¢–$1\n8,568\n$1–10\n5,941\n$10–100\n2,329\n$100–300\n1,292\n$300–1k\n193\n$1k–1.8k\n70\n$1.8k–3k\n67\n$3k–10k\n18\n$10k–30k\n3\n$30k–100k\n1\n$100k+\nitems\nlog\nVALVE’S LISTING CAP\n不超过Valve的上市上限超出上限——Valve的规定禁止该股票上市乐队中的曲目分类\n\n“覆盖范围”是指在数据捕获的瞬间，该类别下存在一个有效的Steam实时询价。下图采用对数坐标系，因为该目录中的商品绝大多数价格低廉：若采用线性坐标系，300以上的所有价格区间都会被压缩到基线上。\n\n该形状排除了哪些情况\n\n如果昂贵商品仅仅是不受欢迎，那么随着价格上涨，其覆盖率本应逐渐下降。但事实并非如此。覆盖率在76.8%的水平保持稳定，贯穿$300–$1k这一价格区间，随后在紧邻上限的区间内骤降至14.5%，而在紧邻下限的区间内则骤降至2.9%。需求效应并不知道Valve将上限设在何处，而规则却知道。\n\n价格区间\t商品分类\t通过Steam实时提问\tSteam 覆盖范围\tSteam 上列出的藏书\n1¢–10¢\t4,632\t4,632\t100%\t8,223,227\n10¢–$1\t7,152\t6,931\t96.9%\t5,488,315\n$1–10\t8,568\t8,213\t95.9%\t3,939,538\n$10–100\t5,941\t5,780\t97.3%\t1,328,255\n$100–300\t2,329\t2,121\t91.1%\t364,466\n$300–1k\t1,292\t992\t76.8%\t187,504\n$1k–1.8k\t193\t28\t14.5%\t40,281\n$1.8k–3k\t70\t2\t2.9%\t9,592\n$3k–10k\t67\t1\t1.5%\t6,706\n$10k–30k\t18\t0\t0%\t1,366\n$30k–100k\t3\t0\t0%\t21\n$100k+\t1\t0\t0%\t2\n\n该排名表未纳入模式和阶段变体：Steam 并未将“蓝宝石层”或“红宝石阶段”列为独立的市场进入选项，因此若将其计入，将低估 Steam 的覆盖范围。 若不考虑“两个市场”的要求，同一排名表显示，在 37,204 上的商品中，上限以下为 79.1%，上限以上为 6.5%——这一差距更为明显，但依据较弱，因此并非引用的数据。\n\n02 / 证据分级\n要价不等于价格\n\n任何人都可以将一把P2000标价为整整一千万人民币。在将本页上的任何数据用于任何用途之前，会根据有多少个交易平台独立报价高于该上限，以及这些报价的中位数分布是否集中，对其进行评级。无论是在此处还是本档案的其他任何地方，仅列出A级和B级的报价。\n\nA  三个或更多层架一致\n\n有三个或三个以上电商平台对该商品的报价高于上限，且其中位价与最低价之间的差额在25%以内。 197 分类：18,218 份，$76,585,587.\n\nSteam 中未包含： 100.0%.\n\nB  两个架子一致\n\n两个市场在上限以上达成一致，或者三个市场在略低于上限的水平达成一致。 51 分类：176份，2,038,814.美元\n\nSteam 中未包含： 100.0%.\n\nC  一个架子——未使用\n\n仅有一个交易平台挂出了唯一一个高于上限的卖单。 171 分类，247份。 为完整起见，该内容显示在图库中，但不计入本页的任何总数。\n\n这些只是询价，并非价格的证明。\n\n这次调整付出了什么代价，又换来了什么\n\n去掉C级后，标题中“171”的分类和“$3,825,125”的字样便被删除了。剩下的内容更简短，也更难以反驳： 248 分类、18,394 所列的版本、$78,624,401, 以及 100.0% 中的这些版本——每一份——均未出现在 Valve 的市场上。 C级行是导致数据发生变化的原因；它们是显示出来的，而不是隐藏的。\n\n作为文物保留的条目\n\n任何报价超过同一商品最低卖出价三倍的，都会被排除在外。按数据本身所暗示的汇率换算后，其中大部分都是整数人民币金额——这通常是占位符或平台上限的标志，而非真实报价。因为本页面上的每个总金额都使用了 最便宜的 需要说明的是，这些人物中没有一个曾虚报过数据；将他们排除在外，也是为了避免其中任何一人被作为头条新闻引用。\n\n项目\t最便宜的现场提问\t暂且搁置\nSouvenir P2000 | Wicked Sick (Minimal Wear)\t$148,954\t$1,489,543\n★ Specialist Gloves | Crimson Kimono (Minimal Wear) | Phase 1\t$37,239\t$119,163\nSouvenir USP-S | Printstream (Factory New)\t$2,000\t$59,582\n★ Bowie Knife | Crimson Web (Factory New)\t$2,957\t$43,030\n★ Karambit | Marble Fade (Factory New) | 1st\t$11,916\t$38,874\nSticker | Ninjas in Pyjamas (Holo) | Katowice 2014\t$5,000\t$31,748\nSouvenir AWP | Dragon Lore (Battle-Scarred)\t$4,225\t$29,157\n★ Karambit | Doppler (Minimal Wear) | Ruby\t$7,122\t$27,273\n所有419类别，以及每个价格所对应的项目\n\n来源: https://phishdestroy.io/steam_dossier/zh/skin_atlas#gallery\n\n04 / 它到底去了哪里\n那些摆放着Steam不愿摆放的商品的货架\n\n相同的商品列表，按持有这些商品的市场平台分组。这是对商品所在位置的统计 已列出，这与所有权所在地不同，且在此处并非以此含义来理解。\n\n按交易平台划分的“超限”挂牌房源的最低价格\n该书架上所列商品的最低卖出价 × 数量\nYouPin 898\n$22,720,252\nBUFF163\n$22,022,606\nC5Game\n$12,560,543\nCSFloat\n$10,871,845\nSkinport\n$1,385,060\n\n管辖区域（按上述顺序排列）：YouPin 898 — 中国 · BUFF163 — 中国 · C5Game — 中国 · CSFloat — 美国 · Skinport — 德国/马耳他。同一实物商品可上架于上述多个商品架中，因此这些数据不得与任何其他市场的总数相加。\n\n各价格档次的最低值\n超出上限的资金如何分配\n$1.8k-3k\n$9,842,391\n$3k-10k\n$36,787,269\n$10k-50k\n$20,038,749\nover $50k\n$2,891,897\n05 / 数得出来的稀缺性\n供应实际上有多紧张\n\n每件CS2商品都有一个稀有度数值，各大交易平台会公布每个稀有度区间内商品的数量。这使得“稀有”从一个形容词变成了一个数字——而正是这个数字，解释了为何仅为一个被入侵的账号，就值得投入精力制作一套量身定制的钓鱼套件。\n\nAWP | 龙之秘闻\n150 已上架 · 起价11,350\n0.00–0.01\n29 · $14,730\n0.01–0.02\n54 · $11,618\n0.02–0.03\n26 · $11,350\n0.03–0.04\n25 · $11,618\n0.04–0.07\n16 · $11,585\n\nAWP | 《龙之秘闻》（工厂新品）\n\nM4A4 | 嚎叫\n105 已上架 · 起价 $6,628\n0.00–0.01\n11 · $10,725\n0.01–0.02\n14 · $8,088\n0.02–0.03\n11 · $7,580\n0.03–0.04\n19 · $6,703\n0.04–0.07\n50 · $6,628\n\nM4A4 | Howl（出厂新品）\n\nAK-47 | Wild Lotus\n113 已上架 · 起价 $14,373\n0.00–0.01\n25 · $22,343\n0.01–0.02\n11 · $19,364\n0.02–0.03\n3 · $19,645\n0.03–0.04\n15 · $15,044\n0.04–0.07\n59 · $14,373\n\nAK-47 | Wild Lotus（工厂全新）\n\nAWP | 冈尼尔\n173 已上架 · 起价 $11,618\n0.00–0.01\n28 · $17,875\n0.01–0.02\n21 · $13,600\n0.02–0.03\n32 · $12,065\n0.03–0.04\n29 · $11,735\n0.04–0.07\n63 · $11,618\n\nAWP | 冈尼尔（工厂新品）\n\nAK-47 | 火蛇\n278 已上架 · 起价663\n0.15–0.18\n87 · $730\n0.18–0.21\n49 · $712\n0.21–0.24\n52 · $703\n0.24–0.27\n18 · $715\n0.27–0.38\n72 · $663\n\nAK-47 | 火蛇（经实战检验）\n\n表面淬火（所有层级 / 蓝色宝石）\n76 已上架 · 起价1,638\n0.07–0.08\n1 · $2,516\n0.08–0.09\n4 · $2,482\n0.09–0.10\n6 · $3,856\n0.10–0.11\n7 · $2,797\n0.11–0.15\n58 · $1,638\n\nAK-47 | 表面淬火处理（磨损极轻） | 等级1\n\n价格区间是交易平台自身的浮动价格区间；只有包含至少一个实时报价的价格区间才会被纳入计算。每个柱状图旁的价格即为该价格区间内的最低实时卖价，因此低浮动价格所附带的溢价可直接从图表中读取，而非通过声明来体现。\n\n06 / 运动，数据来源：Steam\n第三方货架实际上实现了什么\n\nValve 该平台在此层级未发布任何可用的历史数据，且本报告也未声称包含此类数据。Skinport 确实会发布其过去 24 小时、7, 30 以及 90 天内的已成交数据，而这便是此处可获取的全部时间维度：各时间窗口内的已成交价格中位数，并经过指数化处理，因此 90-天的中位数为 100. 这两张图表均未涉及Steam的数据。\n\n已实现价格中位数（滚动窗口）\n以90-天中位数为基准 · 6,758 包含20+ sales的条目\n85\n91\n97\n103\n100\n90d\n94\n30d\n90\n7d\n88\n24h\n每日成交额\n相同的商品，相同的窗口\n7,621\n9,653\n11,684\n13,716\n12,700\n90d\n11,894\n30d\n9,540\n7d\n8,637\n24h\n\n这实际上是两张图表，而非一张带有两个纵坐标轴的图表：指数与日交易量没有共同的计量单位，若将它们绘制在同一坐标轴上，会引发不合理的比较。这些时间窗口是嵌套且递延的——90-天数据包含了24-小时数据——因此这并非日数据序列，切勿将其视为日数据序列。 该图所反映的信息范围有限且表述明确：在Skinport发布的滚动窗口期间，已实现价格的中位数始终低于其自身的90-日中位数，而每日销售数量也随之下降。\n\nSkinport 已实现销售额。这些窗口呈嵌套且滑动式排列，因此每个数据点代表滑动窗口内的已实现价格中位数，并以90-日的中位数为基准进行指数化。这并非日度数据序列，且不涉及Steam的数据。\n\n07 / 它是由什么制成的\n十六年前的贴纸和一小把手套\n\n“盖子”上方的这部分并非该游戏的广泛样本。它主要集中在少数几款稀有卡牌和几个系列上，其中部分卡牌如今已完全无法获得——这正是供应无法对价格作出反应的原因。\n\n帽子上方的分类，按稀有度排序\n项目类别的数量\nCovert\n321\nClassified\n39\nRestricted\n24\nContraband\n12\nMil-Spec Grade\n9\nConsumer Grade\n9\nIndustrial Grade\n5\n帽子上方的分类，按系列划分\n十大系列\nThe St. Marc Collection\n13\nThe Cobblestone Collection\n13\nThe Norse Collection\n12\nThe Arms Deal Collection\n9\nThe Canals Collection\n7\nThe Gods and Monsters Collection\n6\nThe Revolution Collection\n4\nThe 2021 Train Collection\n4\nThe Rising Sun Collection\n4\nThe Chop Shop Collection\n4\n\n按类别：皮肤 366, 贴纸 48, 容器 3, 贴纸板 2.\n\n08 / 实际支付的最高金额\n高点是由交易支撑的，而非由上市支撑的\n\n本页面上的其他所有价格均为 问 — 卖家想要什么。这些是 销售：过去90天内，每件商品在Skinport上记录的最高成交价。这是本报告中唯一一个有人实际支付过的金额，且每行都附有市场平台的链接，因此该数字可直接通过来源进行核对，而非通过我们。\n\n21,216该窗口中已完成销售的商品\n106以不低于Valve的挂牌上限的价格售出\n$14,192最高单笔成交金额\n67/419有销售记录的超限类别\n该销售窗口内成交金额最高的30笔交易\n项目\t最高销量\t销售中位数\t销售\t立即查看最低报价\tSteam\t看看这个\nAWP | Gungnir (Factory New)\t$14,192\t$11,343\t5\t$11,490\tabsent\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Factory New)\t$12,387\t$12,387\t1\t$13,836\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Factory New)\t$11,779\t$11,063\t16\t$10,941\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Minimal Wear)\t$11,693\t$11,693\t1\t$9,946\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Minimal Wear)\t$10,437\t$10,437\t1\t$9,610\tabsent\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Blue Laminate (Minimal Wear)\t$9,772\t$37\t76\t$30\t$40\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Minimal Wear)\t$9,463\t$9,463\t1\t$9,500\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Minimal Wear)\t$9,104\t$9,026\t6\t$8,524\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Hedge Maze (Minimal Wear)\t$8,139\t$8,139\t1\t$6,819\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Field-Tested)\t$7,617\t$7,390\t4\t$7,194\tabsent\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Field-Tested)\t$7,615\t$7,615\t1\t$7,100\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Field-Tested)\t$7,149\t$7,006\t2\t$7,165\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Field-Tested)\t$6,711\t$6,194\t15\t$5,988\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Factory New)\t$6,679\t$6,613\t3\t$6,628\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Superconductor (Factory New)\t$6,084\t$6,084\t1\t$7,969\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Battle-Scarred)\t$5,750\t$5,413\t3\t$5,899\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Pandora's Box (Minimal Wear)\t$5,520\t$5,508\t3\t$4,998\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Vice (Factory New)\t$5,385\t$5,158\t2\t$5,700\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Minimal Wear)\t$5,342\t$4,989\t19\t$4,997\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Hedge Maze (Field-Tested)\t$5,334\t$4,862\t5\t$3,724\tabsent\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Vulcan (Factory New)\t$5,275\t$1,418\t12\t$1,280\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Well-Worn)\t$4,978\t$4,978\t1\t$4,942\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Well-Worn)\t$4,931\t$4,931\t1\t$5,445\tabsent\tSkinport CSFloat Steam\nAK-47 | Hydroponic (Factory New)\t$4,802\t$4,351\t2\t$3,648\tabsent\tSkinport CSFloat Steam\n★ Talon Knife | Case Hardened (Minimal Wear)\t$4,588\t$466\t16\t$442\t$630\tSkinport CSFloat Steam\nAWP | Medusa (Factory New)\t$4,484\t$4,484\t1\t$4,171\tabsent\tSkinport CSFloat Steam\n★ Specialist Gloves | Pillow Punchers (Factory New)\t$4,359\t$4,359\t1\t$4,302\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Pandora's Box (Field-Tested)\t$4,359\t$3,666\t11\t$3,245\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Field-Tested)\t$4,289\t$4,225\t8\t$4,022\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Battle-Scarred)\t$4,124\t$4,124\t1\t$4,279\tabsent\tSkinport CSFloat Steam\n同一件商品，同为90活动期间，价格却天差地别\n\n仅限于中位数为100且已完成至少五笔交易的商品，因为对于便宜的皮肤来说，一笔异常交易就会严重扭曲该比率。剩下的商品主要由 表面淬火 交易结算时，由合约类型决定价格，而交易平台将所有合约类型归类于一个名称之下——这与第05.节中通过float变量衡量的机制相同。\n\n项目\t最高值与中位数\t最高销量\t销售中位数\t销售\t看看这个\n★ Talon Knife | Case Hardened (Minimal Wear)\t+884%\t$4,588\t$466\t16\tSkinport CSFloat Steam\nDesert Eagle | Cobalt Disruption (Factory New)\t+859%\t$1,210\t$126\t115\tSkinport CSFloat Steam\nAWP | BOOM (Minimal Wear)\t+814%\t$1,232\t$135\t89\tSkinport CSFloat Steam\nAK-47 | Case Hardened (Well-Worn)\t+769%\t$1,720\t$198\t70\tSkinport CSFloat Steam\nAWP | Graphite (Factory New)\t+761%\t$1,469\t$171\t124\tSkinport CSFloat Steam\n★ Talon Knife | Case Hardened (Field-Tested)\t+509%\t$2,437\t$400\t48\tSkinport CSFloat Steam\n★ Kukri Knife | Case Hardened (Minimal Wear)\t+448%\t$723\t$132\t69\tSkinport CSFloat Steam\n★ Kukri Knife | Case Hardened (Field-Tested)\t+415%\t$549\t$106\t128\tSkinport CSFloat Steam\n★ Ursus Knife | Case Hardened (Minimal Wear)\t+371%\t$597\t$127\t12\tSkinport CSFloat Steam\nAK-47 | Case Hardened (Field-Tested)\t+369%\t$1,037\t$221\t125\tSkinport CSFloat Steam\nAK-47 | Red Laminate (Minimal Wear)\t+360%\t$552\t$120\t18\tSkinport CSFloat Steam\nAWP | Asiimov (Field-Tested)\t+351%\t$528\t$117\t439\tSkinport CSFloat Steam\nAK-47 | Vulcan (Field-Tested)\t+337%\t$865\t$198\t241\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Nightwish (Factory New)\t+322%\t$625\t$148\t31\tSkinport CSFloat Steam\nAWP | Lightning Strike (Factory New)\t+319%\t$2,065\t$493\t198\tSkinport CSFloat Steam\nStatTrak™ AWP | Redline (Minimal Wear)\t+312%\t$574\t$139\t24\tSkinport CSFloat Steam\nStatTrak™ AWP | Asiimov (Battle-Scarred)\t+287%\t$524\t$135\t37\tSkinport CSFloat Steam\nAK-47 | Redline (Minimal Wear)\t+277%\t$562\t$149\t112\tSkinport CSFloat Steam\nAWP | Crakow! (Factory New)\t+275%\t$379\t$101\t72\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Vulcan (Factory New)\t+272%\t$5,275\t$1,418\t12\tSkinport CSFloat Steam\n\n这是90-当日的最高成交价，并非历史最高价，且仅涵盖一个交易市场。本档案中任何地方均未声称存在历史最高价。若某件商品在展示窗口中未显示Skinport的成交记录，则该商品完全未被纳入本展品，这也是该套装规模小于普查数据的原因。\n\n验证链接是根据目录自身的平台标识符生成的。这些链接指向各电商平台上该商品的页面，以便读者可以直接对照来源核对数据，而非通过我们进行核对。外链包含 rel=\"nofollow\"：这些只是引用，并非推荐，而且其中几个目的地正是本调查所批评的电商平台。\n\n09 / 来源与局限性\n这来自何处，以及它无法显示的内容\n\n本页上的所有数据均根据两个快照文件重新计算得出，这些文件的哈希值已与数据一同公布。此处内容均未摘自其他网站的文章。\n\n来源与访问\n\ncs2.sh API、GET /v1/prices/latest 和 GET /v1/schema，单次快照，捕获自 2026-09-23T00:44:27.871388581Z，价格以美元计。\n\n该数据是通过档案中记录的、由GDPR请求者持有的付费商业订阅获取的，并遵循了该服务提供商自身的条款。 未抓取任何电商平台的数据，也未使用任何电商平台的登录凭证。 请求者的密钥存储在此仓库之外，且未出现在此处的任何文件中。\n\n商品如何符合资格\n\n在 BUFF、CSFloat、Skinport、YouPin 或 C5Game 上至少有一个有效卖单的每件基础商品，都会根据其最便宜的卖单被归入一个价格区间，因此该区间绝不依赖于 Steam。“Steam 覆盖率”是指在数据采集时刻，该区间内拥有任何有效 Steam 卖单的商品所占的比例。 图案和版本变体未被纳入排行榜，因为 Steam 并未将它们单独列出；若将其纳入，会导致 Steam 的数据被低估。渲染图是指同一商品的目录图片，这些图片存储在本地。\n\n渲染图与图片版权。产品目录中的渲染图是供应商提供的图片，其对应的 market_hash_name 与价格行一致，这些图片会本地存储，以便在离线和 IPFS 环境中显示。 这些渲染图并非PhishDestroy的作品：所有商品图片、徽标和截图均归各自所有者所有（cs2.sh、CSFloat、Skinport、BUFF、YouPin、C5Game、Valve等）。这些内容的转载仅用于识别和公共利益报道；不主张任何所有权或许可权。\n\n我们未能获得的\n\n所使用的订阅层仅支持当前快照。历史和归档端点不可用，并且 本页面任何地方均未声称存在任何历史数据系列 除了“滚动窗口”销售外，Skinport 还在 06. 栏目中发布相关内容。\n\n这是一个快照，而非时间序列。 在截图时点Steam上未出现某商品的列表，并不证明该商品永远不会出现在那里；这只是该时刻货架上的实际状态，对于超过价格上限的商品，这也符合Valve公布的规则要求：Valve的社区市场明确规定，每件商品的挂牌价格上限为$1,800（且Steam钱包余额上限为$2,000；参见 Steam 社区市场常见问题解答 存档链接：2026-09-21 ↗ 以及 Steam 订阅协议 § 3.C 存档 2026-09-24 ↗).\n\n评分\n\n一项商品的价格始终为其当前最便宜的卖出报价，因此较高的异常值绝不会推高总价。分级机制决定哪些行可以被列入报价。任何高于同一商品最便宜卖出报价三倍以上的报价，将被排除在外，视为非实时价格。 A级：三个或更多交易平台报价仍高于上限，且其中位数位于最低价的25%范围内。B级：两个交易平台报价一致，或三个交易平台的报价一致度较低。C级：仅有一个报价——这属于要价，而非市场价格。本报告中仅引用A级和B级的报价。\n\n异常值规则：报价 > 3.0× 同一品种的最便宜卖出价。\n\n为什么总和是下限\n\n对于每个市场，该商品的 最低 “卖出价”乘以该书架上所列的副本数量。该书架上每隔一本副本的标价均等于或高于该最低卖出价，因此真正的挂牌价格从结构上来说就更高，而非基于估算。这既不是一笔交易，也不是现金流，更不是对CS2经济体的估值。\n\n自己看看吧\n\n本页面上每张图表所依据的衍生数据集均已完整发布： atlas 数据集, 分级和伪影筛选, 基础人口普查数据 以及 包含每个原始快照 SHA-256 的清单.\n\n公开记录的更正\n\n该配套目录的早期草稿开篇提到一款纪念版AK-47 | Point Disarray，某中国电商平台上标价为$148,954，而Steam则标价为$119.。该条目属于C级：仅有一家商家上架，仅有一件商品，且无其他电商平台价格一致。这仅为标价而非成交价，因此在此处及该页面上已被降级。 经核实的最低价为：贴纸 | 泰坦（全息） | 卡托维兹 2014，价格为 $66,285，据 4 报道，这些市场在 5.2% 上的价格相差无几——而在 Steam 上则完全找不到。",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "“皮肤价格阶梯图集”——流动性悬崖"
          },
          {
            "level": 2,
            "id": null,
            "text": "悬崖是基于规则而存在的，而非基于需求"
          },
          {
            "level": 3,
            "id": null,
            "text": "该形状排除了哪些情况"
          },
          {
            "level": 2,
            "id": null,
            "text": "要价不等于价格"
          },
          {
            "level": 3,
            "id": null,
            "text": "A  三个或更多层架一致"
          },
          {
            "level": 3,
            "id": null,
            "text": "B  两个架子一致"
          },
          {
            "level": 3,
            "id": null,
            "text": "C  一个架子——未使用"
          },
          {
            "level": 3,
            "id": null,
            "text": "这次调整付出了什么代价，又换来了什么"
          },
          {
            "level": 3,
            "id": null,
            "text": "作为文物保留的条目"
          },
          {
            "level": 2,
            "id": null,
            "text": "所有419类别，以及每个价格所对应的项目"
          },
          {
            "level": 2,
            "id": null,
            "text": "那些摆放着Steam不愿摆放的商品的货架"
          },
          {
            "level": 2,
            "id": null,
            "text": "供应实际上有多紧张"
          },
          {
            "level": 2,
            "id": null,
            "text": "第三方货架实际上实现了什么"
          },
          {
            "level": 2,
            "id": null,
            "text": "十六年前的贴纸和一小把手套"
          },
          {
            "level": 2,
            "id": null,
            "text": "高点是由交易支撑的，而非由上市支撑的"
          },
          {
            "level": 3,
            "id": null,
            "text": "该销售窗口内成交金额最高的30笔交易"
          },
          {
            "level": 3,
            "id": null,
            "text": "同一件商品，同为90活动期间，价格却天差地别"
          },
          {
            "level": 2,
            "id": null,
            "text": "这来自何处，以及它无法显示的内容"
          },
          {
            "level": 3,
            "id": null,
            "text": "来源与访问"
          },
          {
            "level": 3,
            "id": null,
            "text": "商品如何符合资格"
          },
          {
            "level": 3,
            "id": null,
            "text": "我们未能获得的"
          },
          {
            "level": 3,
            "id": null,
            "text": "评分"
          },
          {
            "level": 3,
            "id": null,
            "text": "为什么总和是下限"
          },
          {
            "level": 3,
            "id": null,
            "text": "自己看看吧"
          },
          {
            "level": 3,
            "id": null,
            "text": "公开记录的更正"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/zh/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/zh/skin_atlas#gallery",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://skinport.com/market?search=AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260924114457/https://store.steampowered.com/subscriber_agreement/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-atlas.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-artefact-screen.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-above-the-ceiling.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/zh/skin_atlas.content.json",
      "export_json_sha256": "8956b381c66785cdf80a3316d8346636a86db8434785093814330c68a8eea14a"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "zh/social_graph.html",
      "language": "zh",
      "title": "追踪已记录的关联——《Steam》档案",
      "source_url": "https://phishdestroy.io/steam_dossier/zh/social_graph",
      "source_html_sha256": "8b9702951886e65fa70e7590ddf0d1b1112b84c70e4df90c32c70018eeee4919",
      "exported_at": "2026-09-29T00:21:41.956Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "social_graph.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/zh/social_graph.pdf?v=print-20260929-v5",
        "sha256": "8c863f9b6fc654e926ee7127c03c6f5528459d25dce62d3baed2212eccd08e8e",
        "bytes": 305254,
        "pages": 6
      },
      "integrity": {
        "signed_object": "social_graph.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "social_graph.content.json.asc",
        "digest_file": "social_graph.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify social_graph.content.json.asc social_graph.content.json",
          "sha256sum -c social_graph.content.json.sha256"
        ]
      },
      "content": {
        "text": "顺着这些联系走。检查每个关系。\n\n搜索一个个人资料。选择一种关系类型。在捕获的记录中，关注其直接邻居。 研究工具： 边代表的是公开关系，并不证明任意两个节点之间存在直接联系、私下协调或不当行为。解读3,435-的节点布局时，最好使用过滤器。\n\n一次只探索一段关系\n\n💡 点击并拖动节点可重新排列图中节点。将鼠标悬停在节点上可查看详细资料。青绿色实线 = 友谊关系，琥珀色虚线 = 相互评论。\n\n关系类型个人资料和直接邻居\n\n3,435 个人资料 · 4,551 已保存的链接\n\n搜索并选择一个个人资料，或点击一个节点。此时仅保留其直接记录的邻居。一条边记录的是关系；它并不建立私下协调。\n\n捕获数据集中的个人资料\n\n完整的源数据表： 下载所有3,435数据行（CSV格式）. 下表最初显示了前25行；通过搜索和分页功能可查看完整数据集。\n\n1–25 / 3,435 行\n角色名称\tSteamID64\t隐私\t状态\t群组会员资格\t结转存货（美元）\t位置\nMahatma Gandhi\t76561198333721623\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tPH\nGalley//갤리🌠🌙\t76561198043416832\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tKP\n$Schlächter\t76561198860277343\tPUBLIC\tClean\tsteambans\t$0.00\tUnknown\n❄r3dsn0w000™❄ [Cristi]🎮\t76561197986767957\tPUBLIC\tClean\tCommunityLegends\t$0.00\tRO\n(2a03) Wolfy\t76561197991671851\tPUBLIC\tCommunity\tsr_public\t$0.00\tUS\nZloy2288\t76561198038578334\tPUBLIC\tClean\tsteambans\t$0.00\tBY\njessy\t76561198039125237\tPUBLIC\tCommunity, VAC (1x)\tCommunityLegends\t$0.00\tJP\nJithraRufure\t76561198071896910\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\n| Níllerdínho |\t76561198003487438\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tDK\nJones is back\t76561198023013026\tPRIVATE\tVAC (1x)\tsteambans\t$0.00\tUnknown\nUNEX | ★✠☠ MoH3st ☠✠\t76561198050763123\tPUBLIC\tClean\tsteambans\t$0.00\tDE\nTrojan\t76561198048457084\tPUBLIC\tClean\tCommunityLegends\t$0.00\tDE\n𝗠𝗮𝘆𝘂 ❤\t76561199377967696\tPUBLIC\tClean\tsr_public\t$0.00\tIS\nbig fucking idiot\t76561198871206397\tPUBLIC\tVAC (1x)\tsteambans\t$0.00\tUnknown\nSOFF Games\t76561198227129276\tPUBLIC\tClean\tcommunitymoderators\t$0.00\tRU\nThijminecraft02\t76561198253895669\tPUBLIC\tClean\tSteamIDcouk SArchive\t$0.00\tNL\nStatic-sama\t76561198289329793\tPUBLIC\tClean\tsteambans\t$0.00\tJP\n𝙸mmortal 𝚂targazer\t76561198142116760\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\nCommander Keen\t76561197987773287\tPUBLIC\tClean\tsteambans\t$0.00\tBE\nS1mX\t76561199648509165\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\nmixwell\t76561199276547472\tPUBLIC\tClean\tsr_public\t$0.00\tJP\nP90_GOD_YyEs™\t76561198285821942\tPUBLIC\tClean\tsteambans\t$0.00\tHK\nhewwo?\t76561199133807546\tPUBLIC\tVAC (1x)\tsteambans\t$0.00\tCH\n♕Kamikaze Atze♕\t76561198002700103\tPUBLIC\tClean\tsteambans\t$0.00\tDE\nPastica\t76561198154655970\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tDZ\n已记录的友谊链接\n\n完整的源数据表： 下载所有4,299数据行（CSV格式）. 下表最初显示了前25行；通过搜索和分页功能可查看完整数据集。\n\n1–25 / 4,299 行\n用户 A\t方向\t用户 B\t关系类型\nMahatma Gandhi\n76561198333721623\t↔\tDeskjet\n76561198272738437\tMutual Friends\nGalley//갤리🌠🌙\n76561198043416832\t↔\tomega\n76561197960274529\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tFisty\n76561198057301486\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tFaalagorn\n76561198001116101\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tMURK\n76561198036995672\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tÅρøᴛʜℯᴛȋᴄÅʟȋℯη ♛👽♛\n76561197984615267\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tsilatrak\n76561197999629462\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tBlack Blade\n76561198083368493\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tAvenger\n76561197978249317\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tRemtar\n76561198124322650\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tCato\n76561197961345984\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t✪ G λ M Ξ ®\n76561197994308495\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tclees42\n76561198030936806\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t𝓜ε𝔰𝔥 | AusLevels\n76561198108828539\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tSgtFopper™\n76561198002555892\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t❥Miss Bee\n76561198046958996\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tTesTy\n76561198032370068\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tskl_andrey\n76561198136881436\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t\"Exekutor\"\n76561198009583947\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tAraripe\n76561198103754372\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tsteve6678\n76561198053200093\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\ttrinner\n76561197970359081\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tSteph S.\n76561198025653291\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tKirito\n76561198154545657\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tDoc. todt\n76561197984492467\tMutual Friends\n已录制的评论链接\n\n完整的源数据表： 下载所有252数据行（CSV格式）. 下表最初显示了前25行；通过搜索和分页功能可查看完整数据集。\n\n1–25 / 252 行\n作者\t方向\t目标受众画像\t日期\t评论内容\nDeskjet\n76561198272738437\t→\tMahatma Gandhi\n76561198333721623\t16 September, 2021 @ 11:02:05 pm PDT\t\"𝑵𝒐𝒘 𝒊𝒇 𝑰 𝒇𝒖𝒄𝒌 𝒕𝒉𝒊𝒔 𝒎𝒐𝒅𝒆𝒍𝑨𝒏𝒅 𝒔𝒉𝒆 𝒋𝒖𝒔𝒕 𝒃𝒍𝒆𝒂𝒄𝒉𝒆𝒅 𝒉𝒆𝒓 𝒂𝒔𝒔𝒉𝒐𝒍𝒆𝑨𝒏𝒅 𝑰 𝒈𝒆𝒕 𝒃𝒍𝒆𝒂𝒄𝒉 𝒐𝒏 𝒎𝒚 𝑻-𝒔𝒉𝒊𝒓𝒕𝑰'𝒎𝒎𝒂 𝒇𝒆𝒆𝒍 𝒍𝒊𝒌𝒆 𝒂𝒏 𝒂𝒔𝒔𝒉𝒐𝒍𝒆\" - Nelson Mandela\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t22 November, 2021 @ 4:10:28 pm PDT\thttps://anige.horigiri.net/?cat=22\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t18 November, 2021 @ 12:45:26 am PDT\thttps://gamerch.com/umamusume/entry/250411\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t8 August, 2021 @ 4:13:25 am PDT\thttps://modoocode.com/304\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t6 February, 2021 @ 3:35:05 pm PDT\t▤ ∫︹- -ω⁾ ⁽︹▓▓︺\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t11 December, 2019 @ 1:50:53 am PDT\thttps://blog.naver.com/aksenwlddj12/221369410039\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t2 October, 2019 @ 7:11:59 am PDT\tǤαllєу║︎갤리..۩\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t9 April, 2019 @ 12:51:28 pm PDT\tExplosiveDamage(owner, from, maxrange, minrange, distmultiplier, dmgmultiplier, mindamage, typ, damagetype, ignore)\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 12:22:47 pm PDT\tinfo - sh_titles.lua\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 12:21:46 pm PDT\tlocal nibbas = 1344 init.lua\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 11:31:58 am PDT\thttp://foreign.aladin.co.kr/shop/wproduct.aspx?ItemId=123955531&start=slayer\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t3 April, 2019 @ 1:26:41 am PDT\tǤαllєу\nLei\n76561198982197954\t→\tJithraRufure\n76561198071896910\t29 December, 2024 @ 12:58:08 pm PDT\t+rep he knows how 2 rush B ￣ヘ￣\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t2 September, 2026 @ 5:16:55 am PDT\tlol\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t20 August, 2026 @ 6:11:03 am PDT\t?\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t25 July, 2026 @ 7:20:05 am PDT\thahahahaha\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t30 June, 2026 @ 12:52:42 pm PDT\twow\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t30 June, 2026 @ 12:41:32 pm PDT\txD\nvalorant enjoyer\n76561199112142402\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:26:30 pm PDT\toh no!!\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:26:11 pm PDT\toh no!!\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:22:22 pm PDT\tomg !!! they know my secret, omg!!!\nvalorant enjoyer\n76561199112142402\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:21:39 pm PDT\t+rep good ♥♥♥♥♥ player\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:20:50 pm PDT\tomg! u cant cheat on secure gaben servers, omg dont report me, they ban me for boosted omg\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 8:37:11 pm PDT\txD\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t28 June, 2026 @ 1:58:14 pm PDT\twow",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "顺着这些联系走。检查每个关系。"
          },
          {
            "level": 2,
            "id": null,
            "text": "一次只探索一段关系"
          },
          {
            "level": 2,
            "id": null,
            "text": "捕获数据集中的个人资料"
          },
          {
            "level": 2,
            "id": null,
            "text": "已记录的友谊链接"
          },
          {
            "level": 2,
            "id": null,
            "text": "已录制的评论链接"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-profiles.csv",
          "https://steamcommunity.com/profiles/76561198333721623",
          "https://steamcommunity.com/profiles/76561198043416832",
          "https://steamcommunity.com/profiles/76561198860277343",
          "https://steamcommunity.com/profiles/76561197986767957",
          "https://steamcommunity.com/profiles/76561197991671851",
          "https://steamcommunity.com/profiles/76561198038578334",
          "https://steamcommunity.com/profiles/76561198039125237",
          "https://steamcommunity.com/profiles/76561198071896910",
          "https://steamcommunity.com/profiles/76561198003487438",
          "https://steamcommunity.com/profiles/76561198023013026",
          "https://steamcommunity.com/profiles/76561198050763123",
          "https://steamcommunity.com/profiles/76561198048457084",
          "https://steamcommunity.com/profiles/76561199377967696",
          "https://steamcommunity.com/profiles/76561198871206397",
          "https://steamcommunity.com/profiles/76561198227129276",
          "https://steamcommunity.com/profiles/76561198253895669",
          "https://steamcommunity.com/profiles/76561198289329793",
          "https://steamcommunity.com/profiles/76561198142116760",
          "https://steamcommunity.com/profiles/76561197987773287",
          "https://steamcommunity.com/profiles/76561199648509165",
          "https://steamcommunity.com/profiles/76561199276547472",
          "https://steamcommunity.com/profiles/76561198285821942",
          "https://steamcommunity.com/profiles/76561199133807546",
          "https://steamcommunity.com/profiles/76561198002700103",
          "https://steamcommunity.com/profiles/76561198154655970",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-connections.csv",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-comments.csv"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/zh/social_graph.content.json",
      "export_json_sha256": "b5d827cf6fac503f87f9e06522bddfb47c22bc52b25a6a7aa5c5c66b7a24e166"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "zh/steam_enforcement_evidence.html",
      "language": "zh",
      "title": "规则与应对——《Steam》专题报道",
      "source_url": "https://phishdestroy.io/steam_dossier/zh/steam_enforcement_evidence",
      "source_html_sha256": "d0f1d07426ab765fc5e1eea7665035857e4dc30a2068d2395917335a3a26111e",
      "exported_at": "2026-09-29T00:21:44.604Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "steam_enforcement_evidence.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/zh/steam_enforcement_evidence.pdf?v=print-20260929-v5",
        "sha256": "034dfaf396a06a3bc896811d337a6bb2a10d1572ac7c1e8dc49e05527a8d5b76",
        "bytes": 552535,
        "pages": 36
      },
      "integrity": {
        "signed_object": "steam_enforcement_evidence.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "steam_enforcement_evidence.content.json.asc",
        "digest_file": "steam_enforcement_evidence.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify steam_enforcement_evidence.content.json.asc steam_enforcement_evidence.content.json",
          "sha256sum -c steam_enforcement_evidence.content.json.sha256"
        ]
      },
      "content": {
        "text": "证据补充材料 / 来源关联记录\nSteam 执法证据——支持记录与开发者网络\n\n规则。 回复。\n\n本节证明了什么\n\n该证据室将Valve的官方《订阅协议》与带日期的执法日志、支持纠纷解决记录，以及252各仓库和3,320个人资料中的开发者网络记录进行了对比。这表明，普通账户持有者在会话遭入侵后将面临无法反驳的执法行动和支持服务终止，而大规模商业机器人运营则凭借对公共基础设施的访问权限持续运行。\n\n← 返回高管简报\n\n阅读书面限制条款。打开记录的答复。将来源中显示的内容与尚未得到解答的问题进行对比。\n\n支持与申诉 ↓公共基础设施 ↓\n252存储库记录\n3,320公开个人资料\n4,214不同的配置文件-仓库对\n98,902具有共享仓库的用户配置对\n01 / 支持、制裁与恢复\n请阅读诉状。请附上源文件。\n“支持拒绝”画廊（981 展览） ↗下载选定的记录 ↓\nHFB / 外包案例公认的折中方案。\n据报道的解雇事件。\n\n请参考下文转载的客服回复以及关于承包商员工的声明来源。\n\n打开此案例及其来源 →\n\n下文：五件保存下来的 Reddit上的公开帖子 来自提供的支持记录集。每条记录都记录了一次据称与Valve支持系统的交互——其中保留了原始来源链接、截取位置和完整文本。这些是受害者的陈述。能够证实或反驳这些陈述的经过验证的支持日志由Valve持有，尚未公开。\n\n01\nBan & review2024-12-09\nPermanent sanction & closed appeals\n\nThe author reports a permanent account ban, repeated ticket closures and a planned GDPR access request.\n\nREDDIT / PUBLIC TESTIMONYr/ohnePixelCapture record 294\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 303 words\nPermanently banned Steam account without a clear explanation, need help!\n\nsteam_support_tickets_MEGA.json / record 294\n\nHey everyone,\n\nI’m in a really frustrating situation, and I’m hoping someone here can help me or offer advice. My Steam account was just permanently banned for allegedly violating the Steam Subscriber Agreement, and I have no idea why.\n\n# What Steam Support told me:\n\nThe support message said my account was banned due to:\n\n* Suspicious activities related to transferring or attempting to sell/trade the account.\n* Community reports and other unspecified factors.\n\nThey added that the ban is permanent and that they can't help me further. They also warned that future support requests regarding this ban might be ignored. 😞\n\n# Why I’m contesting this ban:\n\n* I have never sold, traded, or transferred my account. I’ve been the legitimate owner since the beginning.\n* On the day the ban occurred, I did nothing noteworthy that could have triggered such a sanction.\n* I received no prior warning, which feels incredibly unfair.\n\n# What I’ve tried so far:\n\n* Contacting Steam Support: I explained my situation and asked for more details, but they’re sticking to their decision and closing my tickets.\n* I’m preparing a request based on my Right of Access (GDPR) to get all the data related to my account.\n\n# Questions for the community:\n\n1. Has anyone successfully had a permanent ban lifted on Steam?\n2. Are there steps I can take to prove I’m the legitimate owner of the account?\n3. Any advice on how to word my request to convince support to reconsider my case?\n4. Would it be helpful to contact the CNIL (I’m based in France) to force Steam to provide more information?\n\nI’m really desperate at the thought of losing all my games, purchases, and years of playtime. Thanks in advance for any help and advice you can give!\n\nhttps://preview.redd.it/jk9qv0gmhv5e1.png?width=1289&amp;format=png&amp;auto=webp&amp;s=b3a333ebb08ea133e2c8747ba126f5a68283d9f7\n\nhttps://preview.redd.it/4sopt0gmhv5e1.png?width=1022&amp;format=png&amp;auto=webp&amp;s=56195d5336118faf9413f1514ead7e8d24c788c3\n\nhttps://preview.redd.it/eqrxw0gmhv5e1.png?width=996&amp;format=png&amp;auto=webp&amp;s=ff3539d28ab754e513ad471822c5de652920101d\n\nhttps://preview.redd.it/728xz0gmhv5e1.png?width=1034&amp;format=png&amp;auto=webp&amp;s=bc5335673509929669af785aa244bf8d2dc58da8\n\n02\nSupport access2025-05-09\nAccount recovery & a reported $10,000 loss\n\nThe author alleges that support reset credentials and removed account protection following another person’s recovery ticket.\n\nREDDIT / PUBLIC TESTIMONYr/legaladviceCapture record 110\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 193 words\nGot $10k stollen from steam inventory due to steam' support fault.\n\nsteam_support_tickets_MEGA.json / record 110\n\nLocation: Quebec, Canada.\n\nLast year, someone hacked my Steam account and stole items worth about $10,000 USD. I only noticed this last week. When I talked to Steam Support, they admitted that someone submitted a ticket to make changes on the account and Steam Support reset my password and turned off all my account security.\n\nI asked Steam Support about getting my items back, but they said there was nothing they could do. They told me I should follow their security recommendations.\n\nThe problem is, I did everything they \"suggested\" to protect an account:\n\n* I had two-factor authentication.\n* My phone number was connected to my account.\n* I used Steam Guard.\n* I printed recovery codes and kept them in a safe.\n\nEven though I did all these things, Steam Support still gave someone else access to my account. The stolen items had been in my account since around 2016-2017. Also, I had not logged in for a few years, so I didn’t accidentally give my information to a fake website.\n\nIs there anything I can do, or do I just have to accept losing $10,000 USD?\n\nThanks for your help.\n03\nRestoration2022-07-07\nA reported $500+ loss & template replies\n\nThe author describes an account compromise, disputed transactions and a support response that allegedly did not address the submitted evidence.\n\nREDDIT / PUBLIC TESTIMONYr/DotA2Capture record 45\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 410 words\nFunds stolen through steam market. Disappointed with Steam response.(or lackthereof)\n\nsteam_support_tickets_MEGA.json / record 45\n\nOn 6th July 2022, 44 unauthorized transactions were made on the steam market using my steam wallet funds totalling roughly $500+ USD to buy worthless 1 cent Dota 2 items. This happened during the wee hours in the morning and i contacted them first thing when i woke up. \n\nI have 2FA enabled all the time, and always thought this would not happen to me as I do not go on betting sites/click sketchy links. My account password + emails were not changed, nor did they take my inventory, just that my funds were used illicitly. Also when I went to disable other APIs, it says there are no other APIs to disable. Shows that it wasn't through me clicking sketchy links and leaving my account details there. Would have lost the whole account if i did so.\n\nWhat baffles me is how did they bypass my 2FA to login my account? Why doesn't steam market purchases go through 2FA as well? First time in 9 years that this happened to me. My acc was logged in 'BY' 'Vitebsk' during the illicit purchases but I'm based in Asia I gathered all the screenshots and provided in the ticket to steam support. \n\nAll i got was the standard copy paste template reply by Steam Support. Lost $500+ and was not even worthy of having a proper person to look into this. I dont think they even read or take a look at the screenshots cause if they did, they would have come to the realization that what happened was clearly fraud, and with a few clicks, reverse the unauthorized transactions, refund my wallet and ban the hijacker. \n\nOver the years, i've spent quite a fair bit on steam but really, this is the kind of recourse we get when our account is compromised? They just don’t care, sigh. I only expect the bare minimum from Steam and looks like even that is quite far-fetched.\n\nSS: https://imgur.com/a/67frcls \n\nHijacker: https://steamcommunity.com/profiles/76561199141246495\n\nSteam Response: https://imgur.com/a/V6v4maM\n\nI could think of a few ways on how to Improve:\n\n1) Add 2FA to market transactions. (even if its bulk posting or selling of items, just 1 2FA notif is required)\n\n2) Enable accounts to be region locked. (if you are migrating, then have to go through steam support etc)\n\n3) Additional Lock on Steam Wallet. (Another password perhaps?)\n\nEDIT: 2nd ticket in and I have still yet to receive a non robotic copy paste template response from Steam.\n04\nRestoration2021-11-29\nSteam Guard & an item-restoration refusal\n\nA preserved post includes the author’s account of item theft and a support response declining restoration.\n\nREDDIT / PUBLIC TESTIMONYr/DotA2Capture record 58\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 563 words\nMany people are losing item via clicking links where steam guard is enabled and steam support doesn't not restore items.\n\nsteam_support_tickets_MEGA.json / record 58\n\nAccounts are getting compromised and might be their pc as well where Steam market is targeted hence the malicious links . I am assuming these hackers are getting encouraged where steam support is not doing nothing and they are getting away with hacking items.  \nLiterally the guy who is supporting the game which he doesn't get any in game advantage just  cosmetics in game only for the sole purpose of supporting the game so that the game will prosper and become beautiful way  to enjoy weekend. But right now players are getting hacked left right and center and steam support  is copy pasting message where in short they are blaming the guy who clicked link. 1st this is happening because they are not targeting players but they are targeting market since they are selling those stuff for real cash via party website. Steam is a huge company and can eradicate the problem or at least can remove links temporarily  in chat since hackers are targeting .They made us install steam guard by saying we wont help if there is no steam guard now steam guard is not enough to save our inventory now they changed their policy  that they should not click any suspicious links. How would we know if the link is suspicious ? After clicking and getting our inventory stolen right !   \n\"we'd have to duplicate an item to restore it. Duplication lowers the value of all items by reducing their scarcity and inflating the economy, which affects everyone involved in trading and the Market. To maintain the value of everyone’s inventory, we do not restore items. For more information, please see the Steam Item Restoration Policy.\"  \nThey care for millions of people IN STEAM MARKET where as few  are losing items which is going to affect market where the rightful owner bought the items and hacker is going to sell the item via 3rd party website and enjoy ! HOW IRONIC !!  \nThis is the message from support where my frnd got his items stolen via clicking on link  \n   \nHi there,  \n\nThank you for the information and screenshots provided.  \n\nIt appears that the account was compromised, please take the following steps to secure your account and computer:  \n\nScan your computer for viruses, key loggers, spyware, and other malicious code using antivirus software with updated virus definitions.  \nChange the password for the email address that is associated with your Steam account.  \nRegularly reset your Steam account password.  \n\nPlease see our Security Recommendations article.  \n\nIn addition, I’m sorry to hear that your items were removed without your permission. Unfortunately, Steam Support does not restore scammed, lost, or stolen items for any reason.  \n\nSince Steam Support does not remove items from accounts, we'd have to duplicate an item to restore it. Duplication lowers the value of all items by reducing their scarcity and inflating the economy, which affects everyone involved in trading and the Market. To maintain the value of everyone’s inventory, we do not restore items. For more information, please see the Steam Item Restoration Policy.  \n\nTo make sure that a scammer is reported, please report them through the Steam Community. Reporting a scammer through the Steam Community is the best way to prevent them from committing future scams.  \n\nTo learn how to avoid scams or hijackings, please see our Trade Scam article.  \n\nIf you still need assistance, please let us know.\n05\nEnforcement2025-05-11\nSelective enforcement & an unexplained ban\n\nA community member describes a disputed ban and contrasts it with the visibility of commercial gambling promotion.\n\nREDDIT / PUBLIC TESTIMONYr/SteamUncensoredCapture record 107\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 1,208 words\n🚨 Steam Bans Without Reason and Ignores Its Community — What’s Going On?\n\nsteam_support_tickets_MEGA.json / record 107\n\nHey r/Steam,\n\nI’m writing this to share my thoughts and concerns about my friend [moneylead](https://steamcommunity.com/id/moneylead/) and Steam’s policies in general. I spoke with him yesterday about his situation, though I didn’t discuss writing this post with him—I asked last night, but he hasn’t responded yet. I want to highlight that this issue is broader than just his case, and while Steam might make changes in the future (though that’s unlikely), I feel the community needs to understand how far Steam has strayed from its original values. I’m not trying to put moneylead in a tough spot with this thread—all the info I’m sharing is public, nothing secretive. I hope he won’t be upset with me, but the community needs this case to see the bigger picture and how Steam feels completely unaccountable.\n\n**Why Does Steam Ignore Its Community?**  \nWhy does a platform like **Roblox** provide a detailed log of ban reasons, while Steam, which claims to be \"community-driven,\" ignores its community, bans whoever they want, for whatever they want, with no transparency? I looked into Roblox as a popular game—not a direct competitor to Steam—to see how their bans look, and you can check it out yourself: [Roblox Ban Reasons](https://www.google.com/search?q=Roblox+ban). Their bans are clear, detailed, and actually explain what you did wrong. I think most decent gaming communities operate like this—not with support agents named Olga, hired through outsourcing, who only know how to send canned auto-replies. Take cases like St4ck—or my friend **moneylead**. All these unbans, like **St4ck’s** or **Alexanddd’s**, happened behind closed doors with zero comments from Steam. Of course, it’s convenient for Steam to handle everything in secret, so no one knows or sees what’s going on—but this violates Steam’s own community rules and principles.\n\n**Who Is moneylead?**  \nI’ve known [moneylead ](https://steamcommunity.com/id/moneylead/)since around 2021. We played Dota 2 a couple of times, and then I just stayed on his friends list. He’s always been a legit player, bringing revenue to Steam through purchases. He never sold his skins, whether in **Dota or CS2—he wasn’t a trader**. All he did was:\n\n* Buy games and skins.\n* Collect badges to level up his profile.\n\nAccording to [SteamSets](https://steamsets.com/account/76561199080934614), he’s given out 324,000 Steam Points—I think he awarded profile rewards to all his friends in the list (though I’m not 100% sure). I do know he ran contests and gave gifts to friends, always supporting the community.\n\n**Steam’s Unfair Treatment**  \nI’ve seen Steam remove his showcases, avatar, description, and even his country multiple times—just because he’s from **Ukraine**. He has a ton of haters leaving toxic comments on his wall, and Steam seems to favor **Russian** users. Every time he tried to appeal the removal of his showcases or profile description—which didn’t break any rules, just had his Instagram link, and his avatar is the same as it is now—Steam moderators didn’t care. **They don’t care about top players who bring them massive revenue, nor about regular users.**\n\n>*Here’s the worst part: moneylead works in cybersecurity, specifically fighting account theft and phishing. He’s neutralized over 5,000 threats targeting Steam alone. And yet, Steam bans him for \"account hijacking\"?*\n\nIf you roughly calculate moneylead’s contribution to Steam and the community—his profile, level, badges (not skins, you can’t sell those)—is this normal, Steam? Banning people, closing tickets, and ignoring users with a spotless reputation who aren’t involved in any commercial activity, just bringing you profit without taking anything in return?\n\n**Steam’s Double Standards**  \nI’m honestly shocked:\n\n* YouTubers who promote casinos and skin gambling? Steam’s fine with that.\n* A cybersecurity expert who fights scams, doesn’t promote casinos, and openly talks about it on his profile? **Banned with no explanation, ignored, and denied an unban.**\n\nI wonder if Steam deliberately bans a high-level account once a year just because of their impunity—maybe for hype or something. Otherwise, this is just madness. It’s scary to think how many regular players have lost their accounts and skins—not because of scammers, but because of Steam’s desire to ignore, send auto-replies, and do whatever they want.\n\n**How Many Others Are Affected?**  \nHow many others are out there—maybe not as well-known—who just have a few games or skins, get banned for nothing, and receive zero explanation or response? **Is this even legal?** Every other platform provides a detailed log with specific violations, but Steam slaps on the same vague label and sends templated responses.\n\n* How safe is it to buy skins on Steam?\n* What’s the chance Steam will just ban your account for no reason, with no explanation?\n\n**A Message to Valve**  \nI wish moneylead the best in resolving this, but Valve, it’d be great if you remembered what \"community\" means and started following the law. Because right now, it looks like your 30% commission, impunity, and sense of being above the law in the U.S. have given you the idea that you can do whatever you want.\n\nI’m sure there are many others like moneylead and St4ck—people who aren’t public or don’t have the resources to fight back. Let’s unite these cases. **If you’re a U.S. resident who’s been banned by Steam without reason and wants to challenge it, please reach out to me.** I’m finishing my **Juris Doctor (J.D.) program at SMU Dedman School of Law** in Dallas, Texas, and I’m participating in a legal clinical practice under Rule 13 of the Texas Supreme Court.\n\nWhat Steam is doing is absolutely disgusting and illegal, and **I’d be happy to help any gamer (legitimate, with no real violations) who has games or skins with value. This will be beneficial for my practice, and it’s time to put Steam in its place and show them they can’t just dictate their own rules with arbitration**. Let’s take it all the way—not for punishment, but for the sake of the community. Maybe if Steam loses a case, they’ll change their policies and start explaining their actions like most popular gaming communities do. Many of us remember how Steam Support used to recover stolen accounts and ended up “stealing” skins themselves—banning without real reasons is basically the same thing, and that’s a serious accusation.\n\nSo, r/Steam, see you soon. I think you understand what you’re doing and how many people you’ve illegally deprived of their assets. I want to raise this issue—not just for the U.S., but for the entire world. You’ve banned class-action lawsuits? **Welcome to Texas.** I recommend starting to look for licensed attorneys in Texas, because I’d love to discuss your company’s policies, feedback, and support agents named Olga—a name that strongly associates with Russian users. Maybe it’d be easier to move your company to Moscow? But I’d be happy to discuss these critical issues on behalf of the global gaming community.\n\nAlso, I wouldn’t recommend ignoring the lawsuit request that will be sent to your physical address and email address, as the court will proceed without you, and that might upset you—especially since things aren’t going so well for a company with stocks like yours.\n\n**Thanks to everyone who took the time to read this. For those who need real help with an unjust Steam ban without any explanation, I’d be happy to assist. For users from Texas, we can easily file a collective lawsuit against Steam—let’s connect and make it happen.**\n02 / Steam 开发网络\n公共基础设施。大规模录制。\n下载所有252的唱片 ↓\n\n随附的 output_steam_network 快照记录了代码库、公开的贡献者/分叉关系以及个人资料的重叠情况。这些都是已发布的记录——构建了什么、谁进行了贡献、分叉了什么。Valve必须对这些公开能力的“纸质记录”负责。\n\n仓库 / 描述\t贡献者\tForkers\t已记录的个人资料\nalliedmodders/amxmodx\n\nAMX Mod X - Half-Life 1 Scripting and Administration\n\n\t40\t40\t80\nalliedmodders/sourcemod\n\nSourceMod - Source Engine Scripting and Administration\n\n\t40\t40\t80\nDoctorMcKay/node-steam-user\n\nAllows interaction with the Steam network via the Steam client protocol\n\n\t40\t40\t80\nFacepunch/Facepunch.Steamworks\n\nAnother fucking c# Steamworks implementation\n\n\t40\t40\t80\nJustArchiNET/ArchiSteamFarm\n\nC# application with primary purpose of farming Steam cards from multiple accounts simultaneously.\n\n\t40\t40\t80\nodota/core\n\nOpenDota: Open source Dota 2 data platform with automated replay parsing\n\n\t40\t40\t80\nodota/dotaconstants\n\ndotaconstants: Static data for Dota applications\n\n\t40\t40\t80\nodota/web\n\nOpenDota: React web UI for Dota 2 statistics using the OpenDota platform\n\n\t40\t40\t80\nsplewis/get5\n\nCS:GO Sourcemod plugin for competitive matches/scrims\n\n\t40\t40\t80\nSteamDatabase/FileDetectionRuleSets\n\n🔎 Rules to detect game engines and other technologies based on Steam depot file lists\n\n\t40\t40\t80\nSteamRE/SteamKit\n\nSteamKit2 is a .NET library designed to interoperate with Valve's Steam network. It aims to provide a simple, yet extensible, interface to perform various actions on the network.\n\n\t40\t40\t80\nValveSoftware/dxvk\n\ndxvk tree containing branches used by Proton\n\n\t40\t40\t80\nValveSoftware/GameNetworkingSockets\n\nReliable & unreliable messages over UDP. Robust message fragmentation & reassembly. P2P networking / NAT traversal. Encryption.\n\n\t40\t40\t80\nValveSoftware/gamescope\n\nSteamOS session compositing window manager\n\n\t40\t40\t80\nValveSoftware/Proton\n\nCompatibility tool for Steam Play based on Wine and additional components\n\n\t40\t40\t80\nValveSoftware/source-sdk-2013\n\nThe 2013 edition of the Source SDK\n\n\t40\t40\t80\nValveSoftware/wine\n\nWine with a bit of extra spice\n\n\t40\t40\t80\nValveSoftware/steam-devices\n\nList of devices Steam and SteamVR will want read/write permissions on, to help downstream distributions create udev rules/etc\n\n\t39\t40\t79\nValveSoftware/steam-audio\n\nSteam Audio\n\n\t38\t40\t78\nalliedmodders/metamod-source\n\nMetamod:Source - C++ Plugin Environment and Detour Library for the Source Engine\n\n\t37\t40\t77\nalliedmodders/sourcepawn\n\nA small, statically typed scripting language.\n\n\t35\t40\t75\nValveSoftware/Fossilize\n\nA serialization format for various persistent Vulkan object types.\n\n\t31\t40\t71\nrlabrecque/Steamworks.NET\n\nSteamworks wrapper for Unity / C#\n\n\t27\t40\t67\nModDota/moddota.github.io\n\nModDota github pages project.\n\n\t26\t40\t66\nodota/parser\n\nReplay parse server generating JSON log events from Dota 2 replay files\n\n\t26\t40\t66\nValveSoftware/steam-for-linux\n\nIssue tracking for the Steam for Linux beta client\n\n\t26\t40\t66\nSteamRE/DepotDownloader\n\nSteam depot downloader utilizing the SteamKit2 library.\n\n\t24\t40\t64\nJustArchiNET/ASF-ui\n\nThe official web interface for ASF\n\n\t23\t40\t63\nadvancedfx/advancedfx\n\nHalf-Life Advanced Effects (HLAE) is a tool to enrich content creation mainly for the Counter-Strike series.\n\n\t22\t40\t62\nalliedmodders/ambuild\n\nAlliedModders C++ Build System\n\n\t23\t39\t62\nSteamDatabase/BrowserExtension\n\n💻 SteamDB's extension for Steam websites\n\n\t21\t40\t61\nodota/mobile\n\nReact Native apps for viewing Dota 2 data on Android/iOS\n\n\t19\t40\t59\nValvePython/steam\n\n☁️ Python package for interacting with Steam\n\n\t18\t40\t58\nskadistats/clarity\n\nComically fast Dota 2, CSGO, CS2 and Deadlock replay parser written in Java.\n\n\t13\t40\t53\nSteamRE/open-steamworks\n\nOpen Steamworks is a set of reverse engineered headers for the Valve's Steam Client. More or less abandoned now that the Steamworks SDK is publically available.\n\n\t13\t40\t53\nValveSoftware/Source-1-Games\n\nSource 1 based games such as TF2 and Counter-Strike: Source\n\n\t13\t40\t53\nalliedmodders/hl2sdk\n\nHalf-Life 2 SDK Mirrors\n\n\t11\t40\t51\nSteamDatabase/steamdb.info-issues\n\n🚱 Issue tracker for the SteamDB website\n\n\t11\t40\t51\nCSGOFloat/inspect\n\nSource Code that Powers the CSFloat Inspect Link API\n\n\t10\t40\t50\nValveSoftware/SteamOS\n\nSteamOS community tracker\n\n\t10\t40\t50\nalliedmodders/source2mod\n\nExperimental\n\n\t40\t9\t49\nsmiley/steamapi\n\nAn unofficial object-oriented Python library for accessing the Steam Web API.\n\n\t9\t40\t49\nSteamDatabase/GameTracking\n\n🛢 Dumping things, so you don't have to\n\n\t8\t40\t48\nValveSoftware/counter-strike_rules_and_regs\n\nCS:GO\n\n\t7\t40\t47\nValveSoftware/openvr\n\nOpenVR SDK\n\n\t6\t40\t46\nSteamDatabase/easy-markdown-editor\n\nEasyMDE: A simple, beautiful, and embeddable JavaScript Markdown editor. Delightful editing for beginners and experts alike. Features built-in autosaving and spell checking.\n\n\t40\t4\t44\nValveSoftware/Dota-2\n\nTracker for issues specific to Linux and Mac in the Reborn client. If you have a general issue or non-system-specific feature request please go to dev.dota2.com\n\n\t6\t38\t44\nValveSoftware/Dota2-Gameplay\n\nPublic Bug Tracker for Dota 2\n\n\t4\t40\t44\nJustArchiNET/ArchiBot\n\nNo description in the capture.\n\n\t16\t27\t43\nztizzlegaming/CSGOWinBig\n\nOpen-source Counter-Strike: Global Offensive jackpot betting website.\n\n\t1\t40\t41\nJustArchiNET/mantis.justarchi.net\n\nMantis Bug Tracker (MantisBT)\n\n\t40\t0\t40\nodota/node-steam-user\n\nAllows interaction with the Steam network via the Steam client protocol\n\n\t40\t0\t40\nModDota/TypeScriptAddonTemplate\n\nDota 2 addon template with TypeScript Panorama and VScripts.\n\n\t9\t29\t38\nValvePython/vdf\n\n📜 Package for working with Valve's text and binary KeyValue format\n\n\t6\t32\t38\nalliedmodders/amtl\n\nAlliedModders C++ Template Library\n\n\t17\t19\t36\nValvePython/dota2\n\n🐸 Python package for interacting with Dota 2 Game Coordinator\n\n\t5\t30\t35\nalliedmodders/stripper-source\n\nStripper:Source\n\n\t13\t21\t34\nAllyans3/steam-market-api-v2\n\nSteam Market API v2 package\n\n\t3\t31\t34\nModDota/dota-tutorial\n\nCustom game DOTA tutorial.\n\n\t11\t23\t34\nodota/blog\n\nNo description in the capture.\n\n\t29\t3\t32\nOpsecGuy/BetterGo\n\nExternal CS:GO cheat written in python.\n\n\t1\t27\t28\npxvr-official/1\n\n無許諾配信 企業理念剽窃 動物の森収益化 大神ミオ権利者削除 戌神権利侵害発言 常闇トワ炎上 夜空メルストーカー被害 建築王サポーター放置 赤十字マーク 魔乃アロエ卒業 一つの中國支持声明 大空昴3Dライブ 無限延期清掃員職業差別 日清コラボ楽曲 musedash非公開 rog案件取り消し 壁画ライブ 丁真 Ding Zhen 郑爽 Zheng Shuang 防护林 与朵小天使w 伊月猫凛 本主萌埋午休傻 汪峰 重生细胞 壁纸 比利海灵顿 香蕉君 van 田所浩二 抽象带篮子 抗压背锅吧 季子越 蒋明辉 傻逼…\n\n\t0\t28\t28\nRevadike/InternalSteamWebAPI\n\nDocumenting the unofficial and internal Steam Web API\n\n\t1\t27\t28\nJoeSzymkowiczFiveM/qb-lootcrate\n\nA CSGO-style case opening script\n\n\t2\t25\t27\nAbrarKL/MyRoulette.XYZ\n\nCSGO / Steam Roulette Site created with PHP and Node JS, using the Material Design front-end framework.\n\n\t1\t25\t26\nJustArchiNET/ASF-WebConfigGenerator\n\nNo description in the capture.\n\n\t10\t15\t25\nModDota/dota-data\n\nAuto-generated Dota 2 resource dumps\n\n\t11\t14\t25\nModDota/TypeScriptDeclarations\n\nTypeScript declarations for Dota 2.\n\n\t11\t14\t25\nModDota/API\n\nNo description in the capture.\n\n\t12\t12\t24\nalliedmodders/cssdm\n\nCounter-Strike:Source Deathmatch\n\n\t10\t13\t23\nSteamDatabase/steamstat.us\n\n✅ Front-end of Steam services status website\n\n\t4\t18\t22\nc0deina/csgojackpotV2\n\nCSGO Jackpot Source\n\n\t1\t20\t21\nValvePython/steamctl\n\n🤸 Take control of Steam from your terminal\n\n\t2\t19\t21\nValvePython/csgo\n\n🔫 Python package for interacting with CS:GO Game Coordinator\n\n\t3\t17\t20\nBeepIsla/csgo-crash-exploit\n\nAllows you to crash any Windows user\n\n\t3\t16\t19\nValvePython/vpk\n\n📦 Open, Search, Extract and Create VPKs in python\n\n\t4\t15\t19\nalliedmodders/SM-SteamWorks\n\nExposing SteamWorks functions to SourcePawn.\n\n\t14\t3\t17\nSteamRE/Steam4NET\n\nSteam4NET is a .NET wrapper around the Steamworks C++ interfaces\n\n\t2\t15\t17\nalliedmodders/hl2sdk-manifests\n\nInformation about HL2SDKs shared between Metamod:Source and SourceMod.\n\n\t6\t10\t16\nJustArchiNET/ASF-PluginTemplate\n\nTemplate repository that you can use for creating custom plugins for ArchiSteamFarm.\n\n\t8\t7\t15\nModDota/Dota2AIFramework\n\nGeneral Framework for Dota 2 AI Competitions\n\n\t1\t14\t15\nShkyyl/KeyChamp\n\nExtension for joining free case battle on key-drop automatically\n\n\t1\t14\t15\nSteamDatabase/SteamMonitor\n\n😤 Track Steam's connection manager servers status\n\n\t2\t12\t14\nBaterka/cslore.com\n\nCS:GO gambling site - csgo.style\n\n\t1\t12\t13\nSteamDatabase/SteamTokenDumper\n\n🔢 Submit users' PICS access tokens to SteamDB\n\n\t2\t11\t13\nmonoblocker/roulette\n\nRoulette CS:GO made in React and Typescript\n\n\t1\t11\t12\nzsith/launcher.user.js\n\n// ==UserScript== // @name AposLauncher // @namespace AposLauncher // @include http://agar.io/* // @version 3.062 // @grant none // @author http://www.twitch.tv/apostolique // ==/UserScript== var aposLauncherVersion = 3.062; Nu…\n\n\t1\t11\t12\nLincolnIT/CSGODouble-bot-automated\n\nCSGODouble Automated, auto Betting Bot.\n\n\t1\t10\t11\nvladpuz/steam-market\n\nSteam market API client\n\n\t4\t7\t11\nmcgrizzz/Cstrike.bet\n\nCSGO Roulette Website Angular frontend, nodejs backend, and steam trading bots\n\n\t1\t9\t10\nodota/underlords-web\n\nUI for OpenUnderlords\n\n\t5\t5\t10\nSteamDatabase/SteamToTwitter\n\n🕊 Tweets announcements from various Steam groups\n\n\t1\t9\t10\nModDota/AbilityLuaSpellLibrary\n\nThe successor to the Spell Library by Pizzalol\n\n\t4\t4\t8\nalvinl/bitskins\n\nUnofficial BitSkins API client\n\n\t2\t5\t7\nb1naryth1ef/steamy\n\nA Python Steam community and market API interface that will get you all hot and bothered\n\n\t2\t5\t7\nkratos1812/Case-Opening\n\nIn-game case opening system for CSGO servers.\n\n\t2\t5\t7\nodota/docs\n\nOpenDota API documentation\n\n\t4\t3\t7\nSteamDatabase/steam-advanced-access-fetch-players\n\n📈 Simple script to fetch Steam player count\n\n\t1\t6\t7\nTheRioMiner/CsgoBetterExternalRaytrace\n\nOverridden maps pack for better external raytrace\n\n\t1\t6\t7\nalliedmodders/hl2sdk-mock\n\nMock HL2SDK and Server\n\n\t5\t1\t6\nchristophersu/PySteamMarket\n\nPython API for getting prices from the Steam market.\n\n\t1\t5\t6\nExtremelyd1/Strat-Roulette\n\nCS:GO Sourcemod Plugin\n\n\t2\t4\t6\ngiovanni-orciuolo/double-sdk\n\nA simple way to write CS:GO cheats!\n\n\t2\t4\t6\nJustArchiNET/Madness\n\nMadness embraces your project by including compatibility layer for selected APIs normally not available on .NET Framework target.\n\n\t5\t1\t6\nModDota/TypescriptPanoramaDeclarations\n\nNo description in the capture.\n\n\t4\t2\t6\nodota/rapier\n\nA JavaScript Dota 2 (Source 2) replay parsing library\n\n\t1\t5\t6\nVozn1akHero/CSGOCaseOpeningSimulator\n\nCounter-Strike case opening simulator which resembles the good old CS:GO user interface\n\n\t3\t3\t6\nautarc/steam-store\n\nAPI client for the unofficial steam storefront/big picture resource\n\n\t2\t3\t5\nBETTING-CODE/awesome-esports-sites\n\nA curated list of awesome esport betting sites – live, statistics and other resources.\n\n\t1\t4\t5\njonteohr/Better-Warden\n\nAn improved and more advanced warden plugin with a custom menu for CS:GO jailbreak servers!\n\n\t2\t3\t5\nLudzikk/CSGO-Gambling-Site\n\nhttps://ludzikk.github.io/CSGO-Gambling-Site/\n\n\t1\t4\t5\nModDota/find-steam-app\n\nFind location of an installed Steam app\n\n\t3\t2\t5\nmprey/csgocact.us\n\nsource code for csgocact.us\n\n\t1\t4\t5\nnezu-cc/ServerCrasher\n\nCS:GO Server Crasher\n\n\t1\t4\t5\nodota/testfiles\n\nStores test replay files\n\n\t2\t3\t5\nodota/underlordsconstants\n\nConstant data for Dota Underlords\n\n\t3\t2\t5\nSnaBe/node-steam-market-fetcher\n\nA Node.js wrapper for the Steam Community Market API.\n\n\t2\t3\t5\nSteamDatabase/.github\n\n💗 Organization-wide community health files\n\n\t1\t4\t5\nwolfcon/RIP-HLTV-BET\n\nRIP BET AD (For Tampermonkey) https://greasyfork.org/en/scripts/423484-rip-hltv-bet\n\n\t2\t3\t5\nalliedmodders/blaster.net\n\nSource and GoldSrc Query Tool\n\n\t2\t2\t4\ncatears124/CS2-Price-API\n\nsimple python cs2 steam market price API\n\n\t1\t3\t4\nialakey/caseforge\n\nOpen-source CS2 case-opening platform: Steam auth, provably fair openings, RTP-balanced case builder, withdrawals bought on market.csgo.com and an admin CRM.\n\n\t1\t3\t4\nIlusion9/csgo-fix-mapchange-crash-sm\n\nFix players crash on map change.\n\n\t1\t3\t4\nismail0234/Benson-Map-Crash-Fixer\n\nCSGO Map Change Client Crash Fixer\n\n\t1\t3\t4\njaxwilko/steam-market-api\n\nPHP - Composer Compatible - Steam Market API\n\n\t2\t2\t4\nJustArchiNET/ArchiTag\n\nArchiTag is a very small utility based on Python 3 and Mutagen to provide missing functionality in opusenc of writing specific Opus metadata, such as total number of tracks or track number.\n\n\t1\t3\t4\nModDota/DotaUI\n\nNo description in the capture.\n\n\t2\t2\t4\nnode-steam/market-pricing\n\nWrapper for the unofficial Steam Market Pricing API\n\n\t1\t3\t4\nodota/media\n\nStores media files for Dota projects\n\n\t2\t2\t4\nSergeyIvanovDevelop/Crypto-Steam-Platform\n\nThe repository contains the code and configuration to run a platform for creating cryptocurrency stakes for arbitrary ERC20 tokens.\n\n\t1\t3\t4\nAareksio/csgodouble-floatchecker\n\nAdds context menu option to check item's float value\n\n\t1\t2\t3\nchinm4/CSGOdrop\n\nA online csgo gambling casino that includes a variety of mini games that allows you to win csgo skins\n\n\t2\t1\t3\nCruze03/CSGO-Case-Opening-Prank\n\nCommand:- !prank (Admin flag \"n\" required)\n\n\t1\t2\t3\nDhruva-Kapadia/CSGOTrollGG\n\nCSGO Case Opening Simulator\n\n\t2\t1\t3\nErhanCSGO/CSGOPolygon-prediction\n\nCSGOPolygon.com - prediction script, double your coins by using this tool\n\n\t1\t2\t3\nEv-Hoang/Bedrock-Chest-Case-Opening\n\nHypixel Skyblock Dungeon Mod - Bedrock Chest Opening Animation (CSGO Style)\n\n\t1\t2\t3\njmjp/csgo-roulette\n\nA csgo gambling roulette make with VueJS 3\n\n\t2\t1\t3\nJustArchiNET/ArchiCrowdin\n\nNo description in the capture.\n\n\t1\t2\t3\nLeonSK/WearMarketInspector\n\nRetrieve Wear Value (Float Value) and Pattern Index from Steam Community Market using http://csgo.exchange API\n\n\t1\t2\t3\nmaximgeerinck/csgo-gamble\n\nCSGO gambling website\n\n\t1\t2\t3\nModDota/BugTracker\n\nListing bugs for Dota 2 Custom Games\n\n\t2\t1\t3\nplwp/mma-betting\n\nUFC/MMA betting model with Pinnacle steam detection for AU book latency arb\n\n\t2\t1\t3\nSouthsideswag16/Csgo-Gambling-Site\n\nNo description in the capture.\n\n\t2\t1\t3\ntacyarg/csgofiesta-frontend-react\n\nRemastered version a the long time favorite csgo site\n\n\t2\t1\t3\nVelorasse/Mutah-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-csmoney-csgoskins\n\ngambling script for Mutah, Keydrop, csmoney, and csgoskins, featuring hacks, cheats, and predictors. Offers strategies to boost winning odds and optimize performance on these platforms.\n\n\t3\t0\t3\nalliedmodders/am-github-artifact-webhook\n\nNo description in the capture.\n\n\t2\t0\t2\ncharamza/roulette\n\nCSGO like roulette in JS\n\n\t1\t1\t2\nCruze03/CSGO-PugSetup-RoundRestore\n\nSometimes (player dropped/crashed) which would be disadvantage for a team. It would be very handy to restore the match to the previous round.\n\n\t1\t1\t2\ncsgorol/CSGO-ROLL-Crash-Predictor\n\nCSGO-ROLL-Crash-Predictor\n\n\t1\t1\t2\nFoxSerito/FOXWORLD_plugin_DoubleJump_CSGO\n\nПлагин SourceMod (CSGO). Двойной прыжок с эффектом.\n\n\t1\t1\t2\nhkehayovmoonbiz/CS2-Casino-Full-Source-Code\n\nCS2, CS2 betting platforms, Skin Roulette, Case Unboxing, Crash games, Jackpot, purchase CS2 casino source, crypto gambling\n\n\t1\t1\t2\nJustZakary/steamstoreapi\n\nThis NPM module is a API wrapper that makes the steam unofficial API easier to use.\n\n\t2\t0\t2\njzimr/steam-market-api\n\nA java library to easily get Steam Community Market data\n\n\t1\t1\t2\nMomohime/CSGO.Network-Jackpot-Coinflip\n\nNo description in the capture.\n\n\t1\t1\t2\nnnjjswat/moneybot\n\nautomated bots for bustabit (formerly known as moneypot), csgo crash, etc\n\n\t0\t2\t2\nodota/carry\n\nLegacy Application for donations to the OpenDota project\n\n\t1\t1\t2\nodota/PublicMatchDataBot\n\nA Discord bot to remind users to turn on Expose Public Match Data in the Dota 2 client\n\n\t1\t1\t2\nOrillio/CSGOBet.com\n\nCSGO roulette web app\n\n\t2\t0\t2\nripexz/csgo-bet-alert\n\nA Chrome extension to keep track of active CS:GO Lounge matches.\n\n\t1\t1\t2\nrrpvm/lumen_sense-beta-deprecated-\n\nthis is internal csgo cheat written by me(no paste, self reverse structures). start : ~6 August 2020, end : ~ 14 December 2020\n\n\t1\t1\t2\nRuthless222/csgoscore\n\nThis is a Counter Strike Global Offensive Betting Site. You chose the skins you want to bet and try to win jackpots\n\n\t2\t0\t2\ntfburns/CSGO-cases-PL\n\nExpected profit-loss of CS:GO case openings\n\n\t1\t1\t2\nTomDra/CSGO-Case-Data-Analysis\n\nWorks out the most profitable CS:GO case at that current time\n\n\t1\t1\t2\nValvePython/dota2-wrappers\n\nNo description in the capture.\n\n\t1\t1\t2\nValvePython/teamfortress2-closed-captions\n\nThis project aims to provide a set of closed captions for Team Fortress 2\n\n\t1\t1\t2\nVistaNetGTX/Cstrike.bet-\n\nCSGO Roulette Website Angular frontend, nodejs backend, and steam trading bots\n\n\t1\t1\t2\nwafflas/csgo-case-opening-simulator\n\nI created a cs go case opening simulator for a meme coin\n\n\t0\t2\t2\nAdmiral-Enigma/Le_Coinflip\n\nConflip game\n\n\t1\t0\t1\nadryeljuliao/roulette-csgo\n\nNo description in the capture.\n\n\t1\t0\t1\nAndreuTheG/csgo-coinflip-web\n\nCSGO Gambling Coinflip Website\n\n\t1\t0\t1\nasmilen/csgoDouble\n\na b c\n\n\t1\t0\t1\nb1naryth1ef/csgofort\n\nA CSGO portal for trading, betting, analytics, and more!\n\n\t1\t0\t1\nBaterka/PrivateSteamBettingWebsite2024\n\nPrivate Steam (Counter-Strike 2) betting/gambling website - Roulette, Jackpot\n\n\t1\t0\t1\nblackcaer/SteamTradeHandler\n\nAutomation of Steam trading. Helper project for bet automation.\n\n\t1\t0\t1\nBTheCoderr/theRounders\n\nThe Rounders - A professional-grade sports betting analytics platform combining real-time odds tracking, sharp movement detection, and advanced statistical analysis. Features include line shopping, steam move alerts, power rankings, and comprehensive bet t…\n\n\t1\t0\t1\nCallumHemsley/KazeBot\n\nA Twitch chat betting bot for CSGO, simply bet a certain amount of points, and double if you win, lose all if you lose. Simple.\n\n\t1\t0\t1\nchrisjpm/CSGOJackpotTemplate\n\nFront end for a jackpot site\n\n\t1\t0\t1\ncolinsenner/valve-bug-bounty\n\nFor many years CS:GO, Dota 2, and Team Fortress 2 servers had a bug that allowed malicious users to leak crucial server process memory or reliably crash any server.\n\n\t1\t0\t1\ncoryypeters/nrl-odds-intelligence-pipeline\n\nReal-time sports betting odds intelligence — streaming pipeline that detects line movement, steam, and arbitrage across bookmakers. Python · Redis Streams · FastAPI · React.\n\n\t1\t0\t1\ndeissh/dev-csgoduo\n\nCS:GO. Bot for receiving things on the site (Polygon, Duo, Double and etc).\n\n\t1\t0\t1\ndom1torii/even-better-font-manager\n\nSimply even better cross-platform tool for CS2 Font Management\n\n\t1\t0\t1\nDONnicov/CSGO-crash-black-screen-\n\nsolution csgo crash black screen and close csgo\n\n\t1\t0\t1\nDoubleBoters/CsgoDouble\n\nNo description in the capture.\n\n\t1\t0\t1\ndownarowiczd/DoubleBot\n\nAn old CSGO Double Bot written for my friend. - 07.05.2016\n\n\t1\t0\t1\nErayBahar/steammarketscraper\n\nSteam Market Scraper Python-based tool that tracks real-time CS2 skin prices using Steam's hidden API. It fetches the lowest sell and highest buy offers for any item, helping you monitor deals or snipe underpriced listings automatically.\n\n\t1\t0\t1\nfairydarkness/SteamwebmailAPI\n\nUnofficial Python API for steamwebmail.com Fast, lightweight, and browserless library for automating steamwebmail.com. Support for session management, proxy, folder navigation, and message retrieval\n\n\t1\t0\t1\nFAQU2/CSGO-Coinflip-MyJailShop\n\nSourcemod plugin which provides a Coinflip system for MyJailShop.\n\n\t1\t0\t1\nFlamesONE/csgo-case-opening\n\nNo description in the capture.\n\n\t1\t0\t1\nFunnyRain/csgorun-crash-watch\n\n🚀 CsgoRun dump crash. / 🚀 CsgoRun дамп крашей.\n\n\t1\t0\t1\ngeohdgio/Venatus-Autenticator\n\nეს არის Steam Autenticator ქართული Venatus Trade & Betting ისთვის და Valve News Georgia-სთვის.\n\n\t1\t0\t1\nhakanstarlord/steam-bot\n\nSports betting steam-move signal detection with ML pipeline (XGBoost stacking + isotonic calibration), backtesting engine, Flask dashboard, and Telegram alerts.\n\n\t1\t0\t1\nHvH-gg/CSGO-Item-CrashFix\n\nA plugin for Counter-Strike: Global Offensive that fixes an exploit where receiving CS2 Items will cause CS:GO clients to crash\n\n\t1\t0\t1\nHvH-gg/CSGO-NetMsg-CrashFix\n\nA plugin for Counter-Strike: Global Offensive that fixes an exploit where spamming NetMsg_StringCmd packets would result in a server crash.\n\n\t1\t0\t1\nisybycnsmam/SteamLibrary\n\nLegacy Steam Unofficial API\n\n\t1\t0\t1\nItsTangerine/SteamApis.Net\n\nUnofficial https://steamapis.com .NET library, supporting .NET 6.0+\n\n\t1\t0\t1\nJustArchiNET/JustArchi.net\n\nNo description in the capture.\n\n\t1\t0\t1\nkiri-osint/CS2-Info-Hub-Bot\n\nA Telegram bot that acts as a hub for CS2 players, providing real-time skin prices, server stats, and user profile/inventory inspection using official and unofficial Steam APIs.\n\n\t1\t0\t1\nKoshkaj/monte\n\nGamified csgo gambling platform implementation\n\n\t1\t0\t1\nmadsab/CaseOpening\n\nA school project using Java. Simulating the case opening from CSGO and more.\n\n\t1\t0\t1\nman90es/steamcardexchange-api\n\nSteamCardExchange.net unofficial REST API server (scraper).\n\n\t1\t0\t1\nMattPua/steam-unofficial-docs\n\nUnofficial docs for Steam APIs with fumadocs\n\n\t1\t0\t1\nMetallist1/Portfolio.CsgoWinGambleProject\n\nA website that was done in 2017 September. Websites focus was on gambling with Counter-Strike items. Project was largely completed however backups were not done correctly, this resulted in half a year of wasted improvements to the code. The website was test…\n\n\t1\t0\t1\nmikebobadilla/csgo-jackpot\n\nNo description in the capture.\n\n\t0\t1\t1\nmikebobadilla/meteor-csgojackpot\n\nCssgo Jackpot done in meteor\n\n\t1\t0\t1\nModDota/D2VDump\n\nDota 2 Server VScript API Dumper\n\n\t1\t0\t1\nModDota/DotaTracking\n\nNo description in the capture.\n\n\t1\t0\t1\nModDota/eslint-config\n\nESLint config by ark120202\n\n\t1\t0\t1\nmr-codinglv/Casino-script\n\nscript casino - script betting - exchange script - bc casino - casino csgo - script bet - betwin script\n\n\t1\t0\t1\nMrKeelik/MrKeel\n\nCSGO DOUBLE BOT\n\n\t1\t0\t1\nnoahlatzel/CSGORollHelper\n\nLeveraging positive expected value on triple green jackpots on CSGORoll!\n\n\t1\t0\t1\noddsgpt/oddsgpt-market-intelligence\n\nResearch on football betting markets, closing odds, CLV, market efficiency, steam moves, AI betting systems, and sports market intelligence.\n\n\t1\t0\t1\noEXU/csgo-server-crasher\n\nCSGO SERVER CRASHER\n\n\t1\t0\t1\nPrdTTony/CSGO-Roulette\n\n[CSGO] Roulette System. Bet on RED or Black and win x2 credits\n\n\t1\t0\t1\nr-adamski/csgo-jackpot\n\nNo description in the capture.\n\n\t1\t0\t1\nSahotallo/Turan-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-Skinbaron-hellcase\n\ngambling script for Turan, Keydrop, Skinbaron, and Hellcase, providing hacks, cheats, and predictors. Includes strategies to improve winning chances and enhance gameplay on these platforms.\n\n\t1\t0\t1\nsamuelcsouza/steam-marketplace-api\n\nAn unofficial API to get data from the Steam Marketplace.\n\n\t1\t0\t1\nSKINSTRACK/CS2-Price-API\n\nSkinstrack offers a free, limited API endpoint that returns Steam item prices. Paid plans additionally provide access to pricing data from multiple marketplaces, making it possible to compare prices across different markets through a single API.\n\n\t1\t0\t1\nsnmtriet/CSGO-Casino-Full-Source-Code\n\nCSGO, CSGOEmpire, Case Opening, Case Battles, Roulette, Coinflip, buy csgo gambling site, gambling\n\n\t1\t0\t1\nSteamRE/homebrew-tools\n\nRepository for installation of SteamRE tools via Homebrew (http://brew.sh)\n\n\t1\t0\t1\nSteamRE/opensteamworks.org\n\nNo description in the capture.\n\n\t1\t0\t1\nTheQuack45/CsgoCaseOpenProgram\n\nSimple program to parse an XML file with CS:GO case information and \"simulate\" case openings\n\n\t1\t0\t1\nTLClassless/StratRouletteCSGO\n\nA 'Strat Roulette' web app for CS:GO!\n\n\t1\t0\t1\ntomasoom/csgoCaseOpening\n\nNo description in the capture.\n\n\t1\t0\t1\nvitaliy-evsyukov/steamgifts-autobet-bookmarklet\n\nbookmarklet for automatic bets on steamgifts.com\n\n\t1\t0\t1\nXpravdaX/RouletteCSGO\n\nNo description in the capture.\n\n\t1\t0\t1\nYuiKasumii/steam_api_unofficial\n\nUnofficial Steam Game Information Database\n\n\t1\t0\t1\nZexuz/Steam-Betting\n\nA betting website build ontop of STEAM's ecosystem\n\n\t1\t0\t1\nANK-RULZZ/steam-jackpot-site\n\ngetting some errors and would like some one to help me with it thank you!!!\n\n\t0\t0\t0\nasmilen/CsgoDoubleVS\n\nNo description in the capture.\n\n\t0\t0\t0\nCORNOODOSADAS/CSGOWeed\n\nCsgo Jackpot and Coinflip\n\n\t0\t0\t0\nCSGOApple/csgoapple\n\nJackpot Site\n\n\t0\t0\t0\nCSGOFAST/csgofast-api\n\nNo description in the capture.\n\n\t0\t0\t0\nDonakall/csgoDoublebot\n\nAutomated bot for csgodouble\n\n\t0\t0\t0\nfedor-selivanov/csgo-fast-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nfoldageros/csgod\n\ndouble bot\n\n\t0\t0\t0\ngmod-gambling/gmod-gambling\n\nNo description in the capture.\n\n\t0\t0\t0\nierome/CSGOBoss-BackEnd\n\nBack end version of CSGOBoss. This was a CSGO Gambling site named CSGOBoss. Coded by an old friend of mine Dahquan Hinds (https://github.com/dahquan/) Thought I would release this to help out any one who would need it.\n\n\t0\t0\t0\njamienp1/CSGODOUBLE-BOT-AUTO\n\ni got a bot thats is betting on the last winning color except from green and if you lose it will double the coins you set it to bet, pretty good, so when there comes a loooong train you will be gaining a bit of money codepaste_net/ugmt92 remove all the _ an…\n\n\t0\t0\t0\nJEYONER/CSGOTOXIC\n\nPAGINA DE JACKPOT CSGO SKINS\n\n\t0\t0\t0\nkalrish/csgo-jackpot\n\nStressful but funny zombie-like Counter-Strike: Global Offensive game mode.\n\n\t0\t0\t0\nkrys12345/roulettee\n\n// ==UserScript== // @name CSGO Predict Bot // @namespace http://csgodouble.com // @version 1.0 // @description predicts what number its gonna be // @author Meee // @match http://www.csgodouble.com/ // @grant none // ==/…\n\n\t0\t0\t0\nLilDuggiMuffi/CSGODouble-Working-Bot\n\nFixed CSGO Double Bot\n\n\t0\t0\t0\nLyricLy/Steam2Proton\n\nCheck if all your Steam games will work with Proton! Uses the official Steam API and the unofficial Proton API.\n\n\t0\t0\t0\nM0NsTeR77/csgo-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nozanhalis/Hi\n\n// ==UserScript== // @name CS GO LOUNGE BOT-Ozan Halis // @namespace http://csgolounge.com/ // @version 0.6.6 // @description Cs Go Lounge Hızlı BOT // @match http://csgolounge.com/* // @match http://dota2lounge.com/* // @updateURL h…\n\n\t0\t0\t0\nscoobertus/CSGO-DoubleBot\n\nNo description in the capture.\n\n\t0\t0\t0\nTradeal/CSGO-Jackpot-Bot\n\nNo description in the capture.\n\n\t0\t0\t0\nValvePython/artifact\n\nNo description in the capture.\n\n\t0\t0\t0\nVampire/CSGO-Roulette-Bot\n\nNo description in the capture.\n\n\t0\t0\t0\nvdemans/csgo-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nVocoreVideo/CSGODungeon-\n\nCSGO Jackpot\n\n\t0\t0\t0\nwayz-dev/csgofloat\n\nNo description in the capture.\n\n\t0\t0\t0\n\n快照：17 9月 2026, 11:19:11（如源数据所示）；时区未指定。导出数据中关系集合设有上限（许多类别止于“40”）。贡献者和分叉者在4,214个不同的个人资料–仓库对中，共计4,554条角色条目；一个个人资料可同时拥有这两种角色。 零表示该类别中未捕获任何记录。仓库名称可能包含别名或大小写变体；总数遵循源数据的计数规则。\n\n来源出处\n由您收集的文件生成。\n支持证词\n2323/reddit_scams_ultra/steam_support_tickets_MEGA.json · 行数 45, 58, 107, 110, 294\n网络快照\nnetwork-repositories.csv · raw_data.json · overlaps.csv · summary.txt（清单中保留了原始路径）\n\n该清单记录了源路径、字节大小、SHA-256哈希值以及选定的记录位置。原始捕获数据与调查的分析结果保持分离。\n\n下载源清单 ↓",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam 执法证据——支持记录与开发者网络"
          },
          {
            "level": 2,
            "id": null,
            "text": "请阅读诉状。请附上源文件。"
          },
          {
            "level": 3,
            "id": null,
            "text": "Permanent sanction & closed appeals"
          },
          {
            "level": 4,
            "id": null,
            "text": "Permanently banned Steam account without a clear explanation, need help!"
          },
          {
            "level": 3,
            "id": null,
            "text": "Account recovery & a reported $10,000 loss"
          },
          {
            "level": 4,
            "id": null,
            "text": "Got $10k stollen from steam inventory due to steam' support fault."
          },
          {
            "level": 3,
            "id": null,
            "text": "A reported $500+ loss & template replies"
          },
          {
            "level": 4,
            "id": null,
            "text": "Funds stolen through steam market. Disappointed with Steam response.(or lackthereof)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam Guard & an item-restoration refusal"
          },
          {
            "level": 4,
            "id": null,
            "text": "Many people are losing item via clicking links where steam guard is enabled and steam support doesn't not restore items."
          },
          {
            "level": 3,
            "id": null,
            "text": "Selective enforcement & an unexplained ban"
          },
          {
            "level": 4,
            "id": null,
            "text": "🚨 Steam Bans Without Reason and Ignores Its Community — What’s Going On?"
          },
          {
            "level": 2,
            "id": null,
            "text": "公共基础设施。大规模录制。"
          },
          {
            "level": 2,
            "id": null,
            "text": "由您收集的文件生成。"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/zh/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/zh/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/selected-support-records.json",
          "https://phishdestroy.io/steam_dossier/zh/investigation_part2.html#outsourcing-case",
          "https://www.reddit.com/r/ohnePixel/comments/1hahqx2/permanently_banned_steam_account_without_a_clear/",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://www.reddit.com/r/DotA2/comments/r55bd7/many_people_are_losing_item_via_clicking_links/",
          "https://www.reddit.com/r/SteamUncensored/comments/1kjt2fa/steam_bans_without_reason_and_ignores_its/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/network-repositories.csv",
          "https://github.com/alliedmodders/amxmodx",
          "https://github.com/alliedmodders/sourcemod",
          "https://github.com/DoctorMcKay/node-steam-user",
          "https://github.com/Facepunch/Facepunch.Steamworks",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://github.com/odota/core",
          "https://github.com/odota/dotaconstants",
          "https://github.com/odota/web",
          "https://github.com/splewis/get5",
          "https://github.com/SteamDatabase/FileDetectionRuleSets",
          "https://github.com/SteamRE/SteamKit",
          "https://github.com/ValveSoftware/dxvk",
          "https://github.com/ValveSoftware/GameNetworkingSockets",
          "https://github.com/ValveSoftware/gamescope",
          "https://github.com/ValveSoftware/Proton",
          "https://github.com/ValveSoftware/source-sdk-2013",
          "https://github.com/ValveSoftware/wine",
          "https://github.com/ValveSoftware/steam-devices",
          "https://github.com/ValveSoftware/steam-audio",
          "https://github.com/alliedmodders/metamod-source",
          "https://github.com/alliedmodders/sourcepawn",
          "https://github.com/ValveSoftware/Fossilize",
          "https://github.com/rlabrecque/Steamworks.NET",
          "https://github.com/ModDota/moddota.github.io",
          "https://github.com/odota/parser",
          "https://github.com/ValveSoftware/steam-for-linux",
          "https://github.com/SteamRE/DepotDownloader",
          "https://github.com/JustArchiNET/ASF-ui",
          "https://github.com/advancedfx/advancedfx",
          "https://github.com/alliedmodders/ambuild",
          "https://github.com/SteamDatabase/BrowserExtension",
          "https://github.com/odota/mobile",
          "https://github.com/ValvePython/steam",
          "https://github.com/skadistats/clarity",
          "https://github.com/SteamRE/open-steamworks",
          "https://github.com/ValveSoftware/Source-1-Games",
          "https://github.com/alliedmodders/hl2sdk",
          "https://github.com/SteamDatabase/steamdb.info-issues",
          "https://github.com/CSGOFloat/inspect",
          "https://github.com/ValveSoftware/SteamOS",
          "https://github.com/alliedmodders/source2mod",
          "https://github.com/smiley/steamapi",
          "https://github.com/SteamDatabase/GameTracking",
          "https://github.com/ValveSoftware/counter-strike_rules_and_regs",
          "https://github.com/ValveSoftware/openvr",
          "https://github.com/SteamDatabase/easy-markdown-editor",
          "https://github.com/ValveSoftware/Dota-2",
          "https://github.com/ValveSoftware/Dota2-Gameplay",
          "https://github.com/JustArchiNET/ArchiBot",
          "https://github.com/ztizzlegaming/CSGOWinBig",
          "https://github.com/JustArchiNET/mantis.justarchi.net",
          "https://github.com/odota/node-steam-user",
          "https://github.com/ModDota/TypeScriptAddonTemplate",
          "https://github.com/ValvePython/vdf",
          "https://github.com/alliedmodders/amtl",
          "https://github.com/ValvePython/dota2",
          "https://github.com/alliedmodders/stripper-source",
          "https://github.com/Allyans3/steam-market-api-v2",
          "https://github.com/ModDota/dota-tutorial",
          "https://github.com/odota/blog",
          "https://github.com/OpsecGuy/BetterGo",
          "https://github.com/pxvr-official/1",
          "https://github.com/Revadike/InternalSteamWebAPI",
          "https://github.com/JoeSzymkowiczFiveM/qb-lootcrate",
          "https://github.com/AbrarKL/MyRoulette.XYZ",
          "https://github.com/JustArchiNET/ASF-WebConfigGenerator",
          "https://github.com/ModDota/dota-data",
          "https://github.com/ModDota/TypeScriptDeclarations",
          "https://github.com/ModDota/API",
          "https://github.com/alliedmodders/cssdm",
          "https://github.com/SteamDatabase/steamstat.us",
          "https://github.com/c0deina/csgojackpotV2",
          "https://github.com/ValvePython/steamctl",
          "https://github.com/ValvePython/csgo",
          "https://github.com/BeepIsla/csgo-crash-exploit",
          "https://github.com/ValvePython/vpk",
          "https://github.com/alliedmodders/SM-SteamWorks",
          "https://github.com/SteamRE/Steam4NET",
          "https://github.com/alliedmodders/hl2sdk-manifests",
          "https://github.com/JustArchiNET/ASF-PluginTemplate",
          "https://github.com/ModDota/Dota2AIFramework",
          "https://github.com/Shkyyl/KeyChamp",
          "https://github.com/SteamDatabase/SteamMonitor",
          "https://github.com/Baterka/cslore.com",
          "https://github.com/SteamDatabase/SteamTokenDumper",
          "https://github.com/monoblocker/roulette",
          "https://github.com/zsith/launcher.user.js",
          "https://github.com/LincolnIT/CSGODouble-bot-automated",
          "https://github.com/vladpuz/steam-market",
          "https://github.com/mcgrizzz/Cstrike.bet",
          "https://github.com/odota/underlords-web",
          "https://github.com/SteamDatabase/SteamToTwitter",
          "https://github.com/ModDota/AbilityLuaSpellLibrary",
          "https://github.com/alvinl/bitskins",
          "https://github.com/b1naryth1ef/steamy",
          "https://github.com/kratos1812/Case-Opening",
          "https://github.com/odota/docs",
          "https://github.com/SteamDatabase/steam-advanced-access-fetch-players",
          "https://github.com/TheRioMiner/CsgoBetterExternalRaytrace",
          "https://github.com/alliedmodders/hl2sdk-mock",
          "https://github.com/christophersu/PySteamMarket",
          "https://github.com/Extremelyd1/Strat-Roulette",
          "https://github.com/giovanni-orciuolo/double-sdk",
          "https://github.com/JustArchiNET/Madness",
          "https://github.com/ModDota/TypescriptPanoramaDeclarations",
          "https://github.com/odota/rapier",
          "https://github.com/Vozn1akHero/CSGOCaseOpeningSimulator",
          "https://github.com/autarc/steam-store",
          "https://github.com/BETTING-CODE/awesome-esports-sites",
          "https://github.com/jonteohr/Better-Warden",
          "https://github.com/Ludzikk/CSGO-Gambling-Site",
          "https://github.com/ModDota/find-steam-app",
          "https://github.com/mprey/csgocact.us",
          "https://github.com/nezu-cc/ServerCrasher",
          "https://github.com/odota/testfiles",
          "https://github.com/odota/underlordsconstants",
          "https://github.com/SnaBe/node-steam-market-fetcher",
          "https://github.com/SteamDatabase/.github",
          "https://github.com/wolfcon/RIP-HLTV-BET",
          "https://github.com/alliedmodders/blaster.net",
          "https://github.com/catears124/CS2-Price-API",
          "https://github.com/ialakey/caseforge",
          "https://github.com/Ilusion9/csgo-fix-mapchange-crash-sm",
          "https://github.com/ismail0234/Benson-Map-Crash-Fixer",
          "https://github.com/jaxwilko/steam-market-api",
          "https://github.com/JustArchiNET/ArchiTag",
          "https://github.com/ModDota/DotaUI",
          "https://github.com/node-steam/market-pricing",
          "https://github.com/odota/media",
          "https://github.com/SergeyIvanovDevelop/Crypto-Steam-Platform",
          "https://github.com/Aareksio/csgodouble-floatchecker",
          "https://github.com/chinm4/CSGOdrop",
          "https://github.com/Cruze03/CSGO-Case-Opening-Prank",
          "https://github.com/Dhruva-Kapadia/CSGOTrollGG",
          "https://github.com/ErhanCSGO/CSGOPolygon-prediction",
          "https://github.com/Ev-Hoang/Bedrock-Chest-Case-Opening",
          "https://github.com/jmjp/csgo-roulette",
          "https://github.com/JustArchiNET/ArchiCrowdin",
          "https://github.com/LeonSK/WearMarketInspector",
          "https://github.com/maximgeerinck/csgo-gamble",
          "https://github.com/ModDota/BugTracker",
          "https://github.com/plwp/mma-betting",
          "https://github.com/Southsideswag16/Csgo-Gambling-Site",
          "https://github.com/tacyarg/csgofiesta-frontend-react",
          "https://github.com/Velorasse/Mutah-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-csmoney-csgoskins",
          "https://github.com/alliedmodders/am-github-artifact-webhook",
          "https://github.com/charamza/roulette",
          "https://github.com/Cruze03/CSGO-PugSetup-RoundRestore",
          "https://github.com/csgorol/CSGO-ROLL-Crash-Predictor",
          "https://github.com/FoxSerito/FOXWORLD_plugin_DoubleJump_CSGO",
          "https://github.com/hkehayovmoonbiz/CS2-Casino-Full-Source-Code",
          "https://github.com/JustZakary/steamstoreapi",
          "https://github.com/jzimr/steam-market-api",
          "https://github.com/Momohime/CSGO.Network-Jackpot-Coinflip",
          "https://github.com/nnjjswat/moneybot",
          "https://github.com/odota/carry",
          "https://github.com/odota/PublicMatchDataBot",
          "https://github.com/Orillio/CSGOBet.com",
          "https://github.com/ripexz/csgo-bet-alert",
          "https://github.com/rrpvm/lumen_sense-beta-deprecated-",
          "https://github.com/Ruthless222/csgoscore",
          "https://github.com/tfburns/CSGO-cases-PL",
          "https://github.com/TomDra/CSGO-Case-Data-Analysis",
          "https://github.com/ValvePython/dota2-wrappers",
          "https://github.com/ValvePython/teamfortress2-closed-captions",
          "https://github.com/VistaNetGTX/Cstrike.bet-",
          "https://github.com/wafflas/csgo-case-opening-simulator",
          "https://github.com/Admiral-Enigma/Le_Coinflip",
          "https://github.com/adryeljuliao/roulette-csgo",
          "https://github.com/AndreuTheG/csgo-coinflip-web",
          "https://github.com/asmilen/csgoDouble",
          "https://github.com/b1naryth1ef/csgofort",
          "https://github.com/Baterka/PrivateSteamBettingWebsite2024",
          "https://github.com/blackcaer/SteamTradeHandler",
          "https://github.com/BTheCoderr/theRounders",
          "https://github.com/CallumHemsley/KazeBot",
          "https://github.com/chrisjpm/CSGOJackpotTemplate",
          "https://github.com/colinsenner/valve-bug-bounty",
          "https://github.com/coryypeters/nrl-odds-intelligence-pipeline",
          "https://github.com/deissh/dev-csgoduo",
          "https://github.com/dom1torii/even-better-font-manager",
          "https://github.com/DONnicov/CSGO-crash-black-screen-",
          "https://github.com/DoubleBoters/CsgoDouble",
          "https://github.com/downarowiczd/DoubleBot",
          "https://github.com/ErayBahar/steammarketscraper",
          "https://github.com/fairydarkness/SteamwebmailAPI",
          "https://github.com/FAQU2/CSGO-Coinflip-MyJailShop",
          "https://github.com/FlamesONE/csgo-case-opening",
          "https://github.com/FunnyRain/csgorun-crash-watch",
          "https://github.com/geohdgio/Venatus-Autenticator",
          "https://github.com/hakanstarlord/steam-bot",
          "https://github.com/HvH-gg/CSGO-Item-CrashFix",
          "https://github.com/HvH-gg/CSGO-NetMsg-CrashFix",
          "https://github.com/isybycnsmam/SteamLibrary",
          "https://github.com/ItsTangerine/SteamApis.Net",
          "https://github.com/JustArchiNET/JustArchi.net",
          "https://github.com/kiri-osint/CS2-Info-Hub-Bot",
          "https://github.com/Koshkaj/monte",
          "https://github.com/madsab/CaseOpening",
          "https://github.com/man90es/steamcardexchange-api",
          "https://github.com/MattPua/steam-unofficial-docs",
          "https://github.com/Metallist1/Portfolio.CsgoWinGambleProject",
          "https://github.com/mikebobadilla/csgo-jackpot",
          "https://github.com/mikebobadilla/meteor-csgojackpot",
          "https://github.com/ModDota/D2VDump",
          "https://github.com/ModDota/DotaTracking",
          "https://github.com/ModDota/eslint-config",
          "https://github.com/mr-codinglv/Casino-script",
          "https://github.com/MrKeelik/MrKeel",
          "https://github.com/noahlatzel/CSGORollHelper",
          "https://github.com/oddsgpt/oddsgpt-market-intelligence",
          "https://github.com/oEXU/csgo-server-crasher",
          "https://github.com/PrdTTony/CSGO-Roulette",
          "https://github.com/r-adamski/csgo-jackpot",
          "https://github.com/Sahotallo/Turan-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-Skinbaron-hellcase",
          "https://github.com/samuelcsouza/steam-marketplace-api",
          "https://github.com/SKINSTRACK/CS2-Price-API",
          "https://github.com/snmtriet/CSGO-Casino-Full-Source-Code",
          "https://github.com/SteamRE/homebrew-tools",
          "https://github.com/SteamRE/opensteamworks.org",
          "https://github.com/TheQuack45/CsgoCaseOpenProgram",
          "https://github.com/TLClassless/StratRouletteCSGO",
          "https://github.com/tomasoom/csgoCaseOpening",
          "https://github.com/vitaliy-evsyukov/steamgifts-autobet-bookmarklet",
          "https://github.com/XpravdaX/RouletteCSGO",
          "https://github.com/YuiKasumii/steam_api_unofficial",
          "https://github.com/Zexuz/Steam-Betting",
          "https://github.com/ANK-RULZZ/steam-jackpot-site",
          "https://github.com/asmilen/CsgoDoubleVS",
          "https://github.com/CORNOODOSADAS/CSGOWeed",
          "https://github.com/CSGOApple/csgoapple",
          "https://github.com/CSGOFAST/csgofast-api",
          "https://github.com/Donakall/csgoDoublebot",
          "https://github.com/fedor-selivanov/csgo-fast-roulette",
          "https://github.com/foldageros/csgod",
          "https://github.com/gmod-gambling/gmod-gambling",
          "https://github.com/ierome/CSGOBoss-BackEnd",
          "https://github.com/jamienp1/CSGODOUBLE-BOT-AUTO",
          "https://github.com/JEYONER/CSGOTOXIC",
          "https://github.com/kalrish/csgo-jackpot",
          "https://github.com/krys12345/roulettee",
          "https://github.com/LilDuggiMuffi/CSGODouble-Working-Bot",
          "https://github.com/LyricLy/Steam2Proton",
          "https://github.com/M0NsTeR77/csgo-roulette",
          "https://github.com/ozanhalis/Hi",
          "https://github.com/scoobertus/CSGO-DoubleBot",
          "https://github.com/Tradeal/CSGO-Jackpot-Bot",
          "https://github.com/ValvePython/artifact",
          "https://github.com/Vampire/CSGO-Roulette-Bot",
          "https://github.com/vdemans/csgo-roulette",
          "https://github.com/VocoreVideo/CSGODungeon-",
          "https://github.com/wayz-dev/csgofloat",
          "https://phishdestroy.io/steam_dossier/output_steam_network/raw_data.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/enforcement-source-manifest.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/zh/steam_enforcement_evidence.content.json",
      "export_json_sha256": "e8d6694144e9d5c1cf1b1c6a260c55d5a1e08985bd3d10e1d0826680c24757b8"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "zh/steam_evidence_archive.html",
      "language": "zh",
      "title": "查证来源——《Steam》档案",
      "source_url": "https://phishdestroy.io/steam_dossier/zh/steam_evidence_archive",
      "source_html_sha256": "527cbb2f40065823e57d1e9bc68aa50c4064d75db4b3a33d96362fbb5016653f",
      "exported_at": "2026-09-29T00:21:44.590Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "steam_evidence_archive.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/zh/steam_evidence_archive.pdf?v=print-20260929-v5",
        "sha256": "232472f7b388ea99e9c77f6d6ad167fe433f414bd109b77fcac6c9c9eb538a02",
        "bytes": 140100,
        "pages": 3
      },
      "integrity": {
        "signed_object": "steam_evidence_archive.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "steam_evidence_archive.content.json.asc",
        "digest_file": "steam_evidence_archive.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify steam_evidence_archive.content.json.asc steam_evidence_archive.content.json",
          "sha256sum -c steam_evidence_archive.content.json.sha256"
        ]
      },
      "content": {
        "text": "调查材料 / 资料收集 002\nSteam 证据档案库——16,319 来源记录\n\n每一项索赔。 回归本源。\n\n本节证明了什么\n\n该取证档案库对16,319的一手资料记录进行了索引——涵盖Valve开发者社区文档、GitHub公开问题报告、经核实的Trustpilot投诉以及存档的论坛报告——并附有加密哈希值和来源日志。它提供了一套可查验的证据基础，证明了平台中存在可复现的漏洞、API中未记录的弃用功能，以及针对账户被劫持问题的持续消费者投诉。\n\n← 返回高管简报\n\n查找某项主张背后的记录。按来源筛选，打开全文，并点击原始链接。来源行可能会重叠；一条记录并不代表已核实的事件。\n\n返回调查 ↗\n354TRUSTPILOT / 数据源行\n208REDDIT / 来源行\n705GITHUB / 源代码行\n15,302主CSV / 源行\n16,319 记录——按平台类型分类\n\n维基分类来源（7,620 条目 · 46.7%）： 数据来源于Valve开发者社区（developer.valvesoftware.com）、SteamDB文档/常见问题解答以及游戏社区维基（Liquipedia CS/Dota和Fandom Steam维基），通过自动WARC快照和MediaWiki API端点于8月2024至9月2026.期间采集。所有7,620条目均已完全整合到主CSV导出文件中（TOTAL_VALVE_SCANDALS_MASTER_DB.csv).\n\n维基\n7,620\nReddit\n5,635\nGitHub\n2,395\nTrustpilot\n393\nWeb\n276\n9,116 16,319 中的记录（55.8%）包含 Steam / Valve 的引用\n\n该可搜索档案库是基于 2026-09-17 来自上述源导出数据。该文件集其他部分中使用的独立的40,448-行主数据导出，其范围有所不同。请参阅 生成清单 此数据集的统计数据；记录可能存在重叠，且不代表独立事件。\n\n源平台\n资料收集\nSteam / Valve 提及\n文本匹配或Valve仓库缺失/已删除的文本\n16,569 源行\n16,319 不同的记录\n249 合并了重复的行\n1 该行被排除在外\n查看原始文件 ↘\n★TRUSTPILOT2015-10-16#1RATING 1/5\n\nSteam is the biggest PC gaming platform without a doubt. A power which could be abused but Steam for the most part doesn't. Overall a definite download for any moden digital age PC gamer. It mu... See more\n\nMA · 7 source copies\n★TRUSTPILOT2021-06-18#2RATING 1/5\n\nThey scam people for money, dont believe me? Read this Source: Steam Subscribers/User Agreement NO GUARANTEES TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, NEITHER VALVE NOR ITS AFFILIA... See more\n\nWF · 7 source copies\n★TRUSTPILOT2016-10-28#3RATING 1/5\n\nSupport on site is terrible. Refunds not happend yet, despite games not working. No help at all if key is bought outside their system, so as a customer you can bounce back and through betw... See more\n\nPE · 7 source copies\n★TRUSTPILOT2021-09-27#4RATING 1/5\n\nThey are an amazing company!! My boyfriend paid for and downloaded a game without realizing it wasn’t the version he wanted. When he reached out, they gave him a full refund and responded in the same... See more\n\nVH · 7 source copies\n★TRUSTPILOT2026-07-20#5RATING 1/5\n\nI’ve used Steam for years, but lately, their sales have really lost their edge. I was hoping to score some solid discounts, but many games still feel overpriced, even during sales. Plus, the support response times can be frustratingly slow when issues arise.\n\nCR\n★TRUSTPILOT2025-12-10#6RATING 1/5\n\nI new here , but all my firends had great experience with this platform . They can make money\n\nZeinab Nematollahi\n★TRUSTPILOT2025-11-18#7RATING 1/5TEXT UNAVAILABLE\n\nNo text was included in the source record.\n\nEM\n★TRUSTPILOT2025-10-21#8RATING 1/5\n\nusing steam for over a decade and i have no words how good the platform is. some friends recommended it to me back in 2015 when we wanted to play csgo together and since then im loggin on it on a daily basis to check new games\n\nTrustpilot\n★TRUSTPILOT2025-05-09#9RATING 1/5\n\nSupport are never able to help you and only able to redicrect you to public linkBreaking there own TOSNot able to provider a refundNot able to provide a safe place for gamingBase on the game you play you can get scam.\n\nSym Link · 7 source copies\n★TRUSTPILOT2025-05-09#10RATING 1/5TEXT UNAVAILABLE\n\nNo text was included in the source record.\n\nHearnius\n★TRUSTPILOT2024-12-30#11RATING 1/5\n\nThis company allowed a single phishing scammer 76561199443342045 in 100's of its user community chat rooms \"Steam Chat\" the whole week of Winter Sales, 12-23-2024 - 2025 to spam spaceintrader a scam phishing website.Don't support Valve & Steam that support sca…\n\nFR · 7 source copies\n★TRUSTPILOT2024-11-15#12RATING 1/5\n\nVery realiable! Ive never had an issue over the 11 years ive had steam.\n\nJM\n构建及其源文件\n\n该档案合并了 249 中的重复行，并从 16,569 的输入数据中剔除了一行，最终保留了 16,319 个独立记录。某条记录所描述的事件可能已被另一条记录涵盖。搜索范围包括标题、作者、来源标签和显示的摘录；点击每条记录即可打开其完整的保存文本。\n\n下载四个源文件导出 ↓文件数量及 SHA-256 哈希值 ↗原始构建清单 ↗\n\n该数据包包含与构建的行数及其三个记录的 JSON 路径相匹配的已恢复导出文件。原始构建未记录输入哈希值或主 CSV 路径；随附的清单文件记录了已恢复的文件，并列出了与已发布的索引的对比结果。\n\nTrustpilot · steam_support_reviews.json354 行 · JSON 导出\nReddit · reddit_censored_forensics.json208 行 · JSON 导出\nGitHub · valve_ignored_bugs.json705 行 · JSON 导出；文件名是一个收集器标签\n主数据库 · TOTAL_VALVE_SCANDALS_MASTER_DB.csv15,302 行 · 用于比较的CSV导出文件\n法院案卷 · UNSEALED_EXHIBITS_AND_AML_DOSSIER.mdWolfire 诉 Valve 案中已解封的电子邮件、Gabe Newell 的证词、10月 2019 AML 的供词\n事实大全 · FACTS_AND_CITATIONS_DATABASE.md1,638 在35的反垄断与安全领域中，经过验证的独立引用\n支持档案 · support_canned_refusals.html1,505 工单记录 · 137 保存的截图 · 实时即时搜索\n记录字段、缺失文本和导出数据重叠\n\n日期、评分、分类和发布状态均与源数据导出内容一致。缺失的 URL 仍保持缺失状态。“[已移除]”或“[已删除]”标记不会说明是谁移除了该帖子，也不会说明原因。Steam / Valve 过滤器采用文本匹配方式，而非相关性评估。\n\n“导出匹配项”会下载包含摘要的索引条目；“下载记录”则包含完整的已保存文本。单独的 40,448-行主 CSV 以及 1,690-第GitHub行 CSV 此次构建中关注的是更广泛的导出，而非源文件数量。",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam 证据档案库——16,319 来源记录"
          },
          {
            "level": 2,
            "id": null,
            "text": "源平台"
          },
          {
            "level": 2,
            "id": null,
            "text": "构建及其源文件"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/zh/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/zh/",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/TOTAL_VALVE_SCANDALS_MASTER_DB.csv",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive_manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive-inputs.zip",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive-inputs-manifest.json",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/unsealed_legal_and_aml/UNSEALED_EXHIBITS_AND_AML_DOSSIER.md",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/forensic_facts_1000/FACTS_AND_CITATIONS_DATABASE.md",
          "https://phishdestroy.io/steam_dossier/zh/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/github_valve_unpatched_bugs.csv"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/zh/steam_evidence_archive.content.json",
      "export_json_sha256": "1f0122d113cfc74cc8e97415a75a1df7514ffab32992b178c0b5aa06c1262c77"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "zh/support_canned_refusals.html",
      "language": "zh",
      "title": "Steam 支持请求被拒及预设回复存档——《Steam》档案",
      "source_url": "https://phishdestroy.io/steam_dossier/zh/support_canned_refusals",
      "source_html_sha256": "00c3b1636fd8954ea50ed1c41a90e18451a345c1fa73e4db64f4cd1c5dd3d72b",
      "exported_at": "2026-09-29T00:21:45.783Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "support_canned_refusals.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/zh/support_canned_refusals.pdf?v=print-20260929-v5",
        "sha256": "8e3e4c6bd20f1d0a93b36f5eb68bf8f0a5911532c255d97c687f3cb5589541f3",
        "bytes": 237208,
        "pages": 2
      },
      "integrity": {
        "signed_object": "support_canned_refusals.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "support_canned_refusals.content.json.asc",
        "digest_file": "support_canned_refusals.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify support_canned_refusals.content.json.asc support_canned_refusals.content.json",
          "sha256sum -c support_canned_refusals.content.json.sha256"
        ]
      },
      "content": {
        "text": "本节证明了什么\n\n本仓库收录了 137 保存的原始截图，以及 1,505 经审核的受害者申诉记录，详细说明了 Valve 的自动化支持工单处理流程。这些资料证明，当账户因 OpenID 重定向或未经授权的 API 密钥生成而遭到入侵时，Steam 客服部门会系统性地采用标准化的模板化拒绝回复，而不会进行技术调查。通过一概拒绝恢复物品或披露审计日志，该平台将结构性身份验证缺陷的全部责任转嫁给了账户遭入侵的用户。\n\n所有截图均为第三方截图。版权及内容归各自的作者和平台所有（Reddit用户、Steam社区作者、Trustpilot评论者、X及YouTube发布者）。这些截图仅用于识别和公共利益报道，不主张任何所有权。每张截图均附有指向其原始来源的链接。\n\nFigures reported on the source page\nMeasure\tReported value\tScope\n书面记录\t1505\t已核实的受害者申诉和罚单讨论帖\n保存的截图\t137\t本地存储的高分辨率票据截图\n恢复率\t0.0%\tAPI起关键交易劫持案获准撤销\n模板复制\t100%\t员工之间（伊利亚、罗杰、马维里克）的逐字脚本复用\n法医证据：拒绝配合的三大支柱\nPILLAR 01 · 招生附件 R——014\n罗杰的供认：API 中间人攻击（MitM）已确认\n\n在工单回复 #1cp582i 中，Steam 的客服人员“Roger”以书面形式承认，攻击者通过 API 在几毫秒内取消合法交易，并用克隆机器人替换，但他拒绝恢复物品，并让受害者去找“当地的电脑维修人员”。\n\n查阅书面录取通知 ↗\n支柱 02 · 升级处理附件 R——012\n7-日内交易：持仓不作为\n\n一名受害者在7-的日交易冻结期内提供了黑客账户的SteamID64。客服人员“Artem”和“Ilya”以虚拟物品稀缺为由，拒绝冻结被盗物品，并使用自动生成的模板关闭了工单。\n\n查看多员工成绩单 ↗\n支柱 03 · 政策附件 R——002\n市场稀缺性与产权\n\nValve 的官方物品恢复政策明确规定，不会退还物品，因为恢复物品会“降低稀有度并导致经济膨胀，从而降低社区市场中物品的价值”。\n\n查看政策截图 ↗\n历史起源 · 22 3月 2018 至 2026\n附件 H——003 · 8-未打补丁的攻击面\n有记载的最早贸易替代案例（22 March 2018）\n\n就在Valve对《反恐精英》道具实施备受争议的7-日交易冷却期整整一周前，交易社区发现了首批实际出现的 Steam Web API 流量重定向漏洞API. 攻击者劫持了 Web 会话，在 steamcommunity.com/dev/apikey 在没有移动端2FA确认的情况下，允许机器人实时取消和更换交易。\n\n3月2018公益广告警告： “诈骗者可以自动检测到这笔交易请求，并会在你的账号上拒绝它，因为他们掌握了你的Steam API密钥。随后，诈骗机器人会向你发送一份包含相同皮肤的交易请求……而你根本不会察觉其中的异样！”\n历史证据步道\n22 3月2018: 首例有记录的API引擎互换\n2019: 该支持措施规范了“恶意软件”的拦截机制\n2020: “关闭求助请求”脚本已加强安全性\n2022–2026: BitB 与二维码钓鱼自动化\n打开 Reddit 上的原始帖子 2018 ↗\nPrimary sources\n\n137 gallery cards refer to 78 distinct primary URLs. Images and repeated exhibit captions are omitted from this reading edition.\n\nFull visual archive and original captures",
        "headings": [
          {
            "level": 2,
            "id": null,
            "text": "Figures reported on the source page"
          },
          {
            "level": 2,
            "id": null,
            "text": "法医证据：拒绝配合的三大支柱"
          },
          {
            "level": 3,
            "id": null,
            "text": "罗杰的供认：API 中间人攻击（MitM）已确认"
          },
          {
            "level": 3,
            "id": null,
            "text": "7-日内交易：持仓不作为"
          },
          {
            "level": 3,
            "id": null,
            "text": "市场稀缺性与产权"
          },
          {
            "level": 3,
            "id": null,
            "text": "有记载的最早贸易替代案例（22 March 2018）"
          },
          {
            "level": 2,
            "id": null,
            "text": "Primary sources"
          }
        ],
        "links": [
          "https://www.reddit.com/r/csgo/comments/1cp582i/i_got_api_scammed_what_do_i_do_now/",
          "https://www.reddit.com/r/DotA2/comments/1e5ovy4/my_account_was_hacked_and_steam_support_refuse/",
          "https://www.reddit.com/r/Steam/comments/3b2abd/steam_will_no_longer_restore_scammed_items_item/",
          "https://www.reddit.com/r/GlobalOffensiveTrade/comments/863tk1/psa_urgent_huge_scam_happening_read_here_how_to",
          "https://phishdestroy.io/steam_dossier/zh/support_canned_refusals#gallery-grid"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/zh/support_canned_refusals.content.json",
      "export_json_sha256": "6b341b2fc4c26f253964a509017c34e3e0af32d215cc536d27d3aa768247cb89"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "zh/valve_scandals_registry.html",
      "language": "zh",
      "title": "Valve 丑闻档案库——Steam档案",
      "source_url": "https://phishdestroy.io/steam_dossier/zh/valve_scandals_registry",
      "source_html_sha256": "55e9562c5e595c70254f45cc01994f19782c49e0b440f92d3130acac6dbd34ea",
      "exported_at": "2026-09-29T00:21:45.977Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "valve_scandals_registry.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/zh/valve_scandals_registry.pdf?v=print-20260929-v5",
        "sha256": "92f4a452b63cd41bdc5ef1cfe7bf94217a8edf98b001f4703cb06982e76a5eaa",
        "bytes": 124819,
        "pages": 6
      },
      "integrity": {
        "signed_object": "valve_scandals_registry.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "valve_scandals_registry.content.json.asc",
        "digest_file": "valve_scandals_registry.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify valve_scandals_registry.content.json.asc valve_scandals_registry.content.json",
          "sha256sum -c valve_scandals_registry.content.json.sha256"
        ]
      },
      "content": {
        "text": "丑闻档案大全\nValve 丑闻主注册表 — 160 来源事件\nSOURCE RECORDS (RAW)：11,768\n\n已报告。已查明来源。仍在处理中。\n\n本节证明了什么\n\n该主注册表汇总了160上经过独立核实的主要记录，详细列出了Valve生态系统中存在的持续性平台缺陷、被删除的社区报告以及未解决的消费者支持问题。该注册表涵盖了经核实的Trustpilot争议申诉、存档的GitHub安全问题工单以及监管机构的诉讼程序，从而揭示了账户恢复和客户争议解决过程中反复出现的系统性故障。\n\n← 返回高管简报\n\n160 收集到的记录：由实际使用者评分的客服操作、已不再显示的讨论帖、已提交但未处理的平台漏洞，以及“Valve”此前已不得不为此负责的事件。此处内容均非我们所作的描述——每一条记录都附有原始来源。请自行打开查看。\n\nSource Records\n11,768\n所有类别中\n平台缺陷\n3,372\n社区报告的平台漏洞\n被屏蔽的帖子\n109\n被版主删除的Reddit帖子\n支持投诉\n471\nTrustpilot 上已核实的投诉\n执法可行性\nAuth-host 域名屏蔽\n\n在域名层面封锁 OpenID 身份验证主机在技术上很容易实现：一旦某个资源被禁止进行 Steam 登录重定向，作为该资源身份验证代理的第三方域名即可通过同一套规则进行过滤。关于实施可行性的详细讨论，请参见主报告。\n\n参见文件中的执行可行性 →\n类别：Trustpilot 支持投诉（筛选后的负面升级案例）176 匹配的源记录 · 重复项已折叠\nConsumer Complaint2026-07-20\nAuthor: C***\n\nI’ve used Steam for years, but lately, their sales have really lost their edge. I was hoping to score some solid discounts, but many games still feel overpriced, even during sales. Plus, the support response times can be frustratingly slow when issues arise.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2026-07-20\nConsumer Complaint2025-05-09\nAuthor: S*** L***\n\nSupport are never able to help you and only able to redicrect you to public linkBreaking there own TOSNot able to provider a refundNot able to provide a safe place for gamingBase on the game you play you can get scam.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2025-05-09\nConsumer Complaint2024-12-30\nAuthor: F***\n\nThis company allowed a single phishing scammer 7656…2045 in 100's of its user community chat rooms \"Steam Chat\" the whole week of Winter Sales, 12-23-2024 - 2025 to spam spaceintrader a scam phishing website.Don't support Valve & Steam that support scams. Don't give your log in credentials to account hijacking scammers. This company also allows engagements of commercial advertising / spam for gambling in violation of its own Rules and Guidelines / Online Conduct. 7656…5023 proof - groups/deskinsfans key drop advertising, thanks TannerfromKD and Valve!*\"The Consumer Review Fairness Act (CRFA) protects people’s ability to share their honest opinions about a business’s products, services, or conduct, in any forum, including social media. The law protects a broad variety of honest consumer assessments, including online reviews, social media posts, uploaded photos, videos, etc. And it doesn’t just cover product reviews. It also applies to consumer evaluations of a company\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2024-12-30\nConsumer Complaint2024-07-31\nAuthor: A***\n\nhorrible company.randomly you get \"This account may have been accessed by someone else.\"this happened to me 3 times.the 3rd time they wanted a cd key.a spent useless cd key that nobody has any reason to keep laying around.i gave them the paypal bill for my first purchase back in 2015.i gave them a bill for my first phone number ever on the account.i still got the same email attached to the account.this company is literally a scam. nothing but a scam.they randomly claim you been accessed somewhere else and then require you to give them information no reasonable person would ever have, if not your done and have to rebuy everything.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2024-07-31\nConsumer Complaint2023-12-09\nAuthor: K***\n\nHad 288 euros in steam wallet, someone hacked my account even with two step verification, write a steam support for help but only answer was if something is spent in community market they can’t help.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2023-12-09\nConsumer Complaint2023-09-26\nAuthor: J***\n\nI was banned for saying \"Who let grandma on the PC\"and another for simply calling someone ignorant.Power tripping mods, devs who don't care, steam doesn't care. Yet allows racism/trolling/etc Fk steam, its a joke now.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2023-09-26\nConsumer Complaint2022-08-31\nAuthor: Anonymous\n\nSteam community is plain bad for a various reasons:1. Steam forums are a big mess, for example they allow users to post in any language and as result you get jumbled mess with posts in foreign languages together with English language posts. For example, If you check CS GO forums, you'll see half of posts are in Russian and half in English. I don't understand why such a big and international company would leave their forums so unorganized like that. All other normal companies have English only language allowed which is an international language and sometimes subforums for other languages like German, French and etc... so if French people want to post in French they go specifically in that sub-forum. But no, Steam doesn't care about this. Their forums is a one big mess.2. Moderation is biased and joke. I don't understand why such a big company like Steam can't afford to hire people for moderation and pay them. Instead they just recruit random people for moderation who do it for free and\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2022-08-31\nConsumer Complaint2022-05-28\nAuthor: J***\n\nThe login code never arrives. I hate Steam.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2022-05-28\nConsumer Complaint2021-11-08\nAuthor: N***\n\nThe service is terrible, I only signed up because I really like the game I wanted, but the rest is terrible, I hope to get something better soon.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-11-08\nConsumer Complaint2021-06-18\nAuthor: W***\n\nThey scam people for money, dont believe me? Read thisSource: Steam Subscribers/User Agreement NO GUARANTEESTO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, NEITHER VALVE NOR ITS AFFILIATES GUARANTEE CONTINUOUS, ERROR-FREE, VIRUS-FREE OR SECURE OPERATION AND ACCESS TO STEAM, THE CONTENT AND SERVICES, YOUR ACCOUNT AND/OR YOUR SUBSCRIPTION(S) OR ANY INFORMATION AVAILABLE IN CONNECTION THEREWITH.In short: You got a virus or your data leaked because of our software? Whoopsies we dont care, that isnt even legal or the last of their scammy stuff...\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-06-18\nConsumer Complaint2021-05-14\nAuthor: B***\n\nThe support is one of the worst I've ever seen.Useless support team.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-05-14\nConsumer Complaint2020-04-02\nAuthor: J***\n\nSteamcommunity has 15% fees, 15!!!!\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2020-04-02\nConsumer Complaint2020-03-27\nAuthor: H***\n\nWhat can I say? the support is one of the worst I've ever seen maybe the FUNCOM is much worse. If you tell the true on the steam forum you just got a BAN even if what you said did not violated the rules of the forum.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2020-03-27\nConsumer Complaint2018-03-16\nAuthor: B***\n\ndon't sign up will stick on your computer will kill your pc power you can't remove it from your pc even you deleted it will stay woking in the system\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2018-03-16\nConsumer Complaint2016-12-27\nAuthor: J***\n\nIn bloddy hate their page it's tiresome, it's in no way intuitive. I tried reaching out for support, but that is a maze.I'm simply trying to log in and redeem a key of a product I already bought, their search function is a joke. I f*u*c*k*i*n*g hate them. The layout is not like the how to video from the dealer, this can be done much simpler. I don't frigin care aboutn what other titles you have in store or what genre, I just want to redeem my key and install.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-12-27\nConsumer Complaint2016-10-28\nAuthor: P***\n\nSupport on site is terrible.Refunds not happend yet, despite games not working.No help at all if key is bought outside their system, so as a customer you can bounce back and through between bad support systems?? I wait for some other companies to compete in this market, for this can't be the best we as customers can expect.And do put an email up to find, instead of this stuppid website where you spend so long time trying to find a solution on, instead of a simple mail. Often the problem is not there, or if it's there just saying no help here???I need a response\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-10-28\nConsumer Complaint2016-06-26\nAuthor: V*** W***\n\nUseless support as always!\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-06-26\nConsumer Complaint2014-07-01\nAuthor: J***\n\nexpensive, and support team not willing to cooperate\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2014-07-01\nConsumer Complaint2014-04-15\nAuthor: B***\n\nWhen you pay for a program, you expect it too work. cant not buy or anything and have written to valve. but there is not a being done a damn thing abut it..\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2014-04-15\nConsumer Complaint2026-09-03\nAuthor: M***\n\nWorst platform ever wont give me a refund even though a game is unplayable because of bugs I won't ever be using the crap platform again I hope the platform breaks down for good piece fo crao\n\nTarget Domain: steamcommunity.com / steampowered.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2026-09-03\n\n没有匹配的记录\n\n请尝试调整当前查询，或查看其他分类标签页。\n\n1 / 9",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Valve 丑闻主注册表 — 160 来源事件"
          },
          {
            "level": 2,
            "id": null,
            "text": "Auth-host 域名屏蔽"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: C***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: S*** L***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: F***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: A***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: K***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: Anonymous"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: N***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: W***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: H***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: P***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: V*** W***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: M***"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/zh/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/zh/#autoban-feasibility-section",
          "https://www.trustpilot.com/review/steamcommunity.com"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/zh/valve_scandals_registry.content.json",
      "export_json_sha256": "1d54fcb1186ef75f03c5fd5085be64c218de6c288c4b2d4131a313478a67a757"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "zh/output_steam_network/index.html",
      "language": "zh",
      "title": "架构，而非漏洞：自动化网络——《Steam》专题报告",
      "source_url": "https://phishdestroy.io/steam_dossier/zh/output_steam_network/index",
      "source_html_sha256": "5f70f669c060fc2c07f5945da31ff4f4b873f11e1d3a1f7160d187d284e36bd8",
      "exported_at": "2026-09-29T00:21:47.238Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__index.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/zh/output_steam_network__index.pdf?v=print-20260929-v5",
        "sha256": "aaf98f4dd52d40dc703b45704c597145a7be6ad6b0e4cdb38fa9482b83d02dce",
        "bytes": 347176,
        "pages": 2
      },
      "integrity": {
        "signed_object": "output_steam_network__index.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__index.content.json.asc",
        "digest_file": "output_steam_network__index.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__index.content.json.asc output_steam_network__index.content.json",
          "sha256sum -c output_steam_network__index.content.json.sha256"
        ]
      },
      "content": {
        "text": "附件七 · 技术架构分析\nSteam 网络架构——协议保真度与生态系统分析\n\n自动化是Valve的架构。 这不是一个漏洞利用。\n\n本节证明了什么\n\n本模块描绘了支撑 Steam 自动化生态系统的 252 开发者仓库、3,320 GitHub 配置文件以及 4,214 贡献者对的技术拓扑结构。它证明了第三方自动化依赖于 Valve 的官方连接管理器协议、Protobuf 模式以及不含漏洞利用代码的 Web API。 通过设计基于算法的 Steam Guard 确认令牌，并收取最高达 66.7%, 的最低交易手续费，Valve 作为自动化生态系统运营的刻意设计者及主要商业受益方发挥作用。\n\n← 返回高管简报\n\n当Valve向监管机构、支付处理商或诈骗受害者说明情况时，它将虚拟皮肤盗窃和市场操纵归咎于“未经授权的第三方漏洞利用”和“非法自动化程序”。而该252-代码库网络的工程现实却证明了恰恰相反： 每一个自动化框架、交易机器人和挖矿舰队，都严格遵循由Valve公司设计、文档化并实现商业化的官方协议定义、Web API以及身份验证机制进行运作。\n\n取证发现：有意识的架构与非法入侵\n\n本模块分析的软件——包括 SteamKit, node-steam-user, ValvePython/steam，以及 ArchiSteamFarm — 包含 零软件漏洞、零内存损坏、零零日漏洞利用. 这些是针对Valve专有的连接管理器（CM）客户端协议、Google Protocol Buffers（Protobufs）以及Web API所做的干净、健壮的开源实现。Valve设计了这些API以支持程序化登录，并设计了Steam Guard以支持算法确认令牌（identity_secret)，并收取广告中公布的15%费用，该费用会逐步上涨至 最高66.7%，由Valve胜出 关于自动化僵尸网络变现的高频交易卡和商品抛售。\n\nPillar 01 · Protocol Fidelity\n官方 Protobuf 模式\n\n自动化库不会绕过安全门。它们会对官方的 Protobuf 消息进行序列化（steammessages_clientserver.proto) 通过 TCP/WebSockets 直接连接到 Valve 的官方 CM 集群，这与 Steam 客户端的操作完全一致。\n\n支柱 02 · 算法 2FA\n程序化交易授权\n\n整个价值数十亿美元的皮肤交易经济依赖于Valve的 IEconService API 以及移动验证器TOTP密钥。Valve特意开发了Steam Guard，以实现机器间交易确认。\n\n支柱 03 · 商业受益人\nMachine Traffic的变现：66.7%手续费下限\n\nValve 虽然宣传的15%手续费，但在交易量巨大的商品类别中——即自动交易机器人活跃的领域，如交易卡、卡包以及定价在$0.03 至 $0.05 之间的低价商品——Valve的2美分最低手续费门槛（$0.01 Steam + $0.01 发布商费用）会扣除 50% 向 66.7% 支付，收款人为 Valve （从3¢的卡片中扣除2¢，卖家最终获得1¢）。此外，每个账户还需扣除5.00美元（仅扫描的车队就需支付26.8M美元）。\n\n模块01· 存储库与协议证据\n公共开发者与代码库基础设施\n\n一份关于252开源仓库的详细取证目录，这些仓库为Steam的自动化功能提供支持。该目录追踪了标准软件工程工具如何在不利用漏洞的情况下，实现Valve发布的API端点。\n\n252代码库\n4,554角色链接\n检查存储库证据 →模块 02 · 生态系统人口统计学\n全球工程生态系统指标\n\n参与Steam自动化生态系统的3,320软件工程师的地域和机构分布情况，包括其在各大科技企业中的任职情况。\n\n3,320工程师\n98,902连接对\n查看生态系统指标 →模块03·交互式可视化图表\n交互式协议与开发者网络图\n\n全面展示Vis.js的交互式网络图，涵盖代码仓库、协议库（SteamKit、Steamworks、ASF）以及跨项目贡献者重叠情况。直观呈现了支撑Steam自动化生态系统的、合法且相互关联的开源软件架构。\n\n交互式Vis.js 发动机\n集群隔离实时搜索\n零漏洞利用标准 API\n打开交互式网络图 →\n监管与法律背景（GDPR 文章 25 及消费者保护）：\n根据“设计和默认数据保护”原则，允许在用户不知情的情况下生成API密钥、未经通知取消交易以及由机器自动清算资产的平台架构，是平台运营商的一种架构选择。 当Valve系统性地以“外部网络攻击”为由拒绝消费者的赔偿索赔时，它掩盖了一个事实：即攻击途径正是Valve自身有意设计的Web API架构。\n\n交互式视图\n\n252-存储库的完整交互式可视化效果，3,320-开发者网络图可访问以下链接查看： network.html. 汇总指标位于 BI 指标 页面。\n\nSteam档案 · 技术架构档案库 · 公开源代码记录 · 所有权利均归全人类所有。",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam 网络架构——协议保真度与生态系统分析"
          },
          {
            "level": 3,
            "id": null,
            "text": "官方 Protobuf 模式"
          },
          {
            "level": 3,
            "id": null,
            "text": "程序化交易授权"
          },
          {
            "level": 3,
            "id": null,
            "text": "Machine Traffic的变现：66.7%手续费下限"
          },
          {
            "level": 2,
            "id": null,
            "text": "公共开发者与代码库基础设施"
          },
          {
            "level": 2,
            "id": null,
            "text": "全球工程生态系统指标"
          },
          {
            "level": 2,
            "id": null,
            "text": "交互式协议与开发者网络图"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/zh/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/zh/output_steam_network/valve_ru_farming_isolated.html",
          "https://phishdestroy.io/steam_dossier/zh/output_steam_network/steam_ecosystem_dashboard.html",
          "https://phishdestroy.io/steam_dossier/zh/output_steam_network/network.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/zh/output_steam_network__index.content.json",
      "export_json_sha256": "18e53db0551859dadb13693ce705315e2758b7fd28a7be06cf866c0a1d1b9768"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "zh/output_steam_network/network.html",
      "language": "zh",
      "title": "开发者与代码库浏览器——《Steam》专题报道",
      "source_url": "https://phishdestroy.io/steam_dossier/zh/output_steam_network/network",
      "source_html_sha256": "8686c9c432ee19648bc4c082f845ecc789b1c7a48c2a3c12a2b7f44c79a68c4a",
      "exported_at": "2026-09-29T00:21:47.992Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__network.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/zh/output_steam_network__network.pdf?v=print-20260929-v5",
        "sha256": "31b6daa4c7d3c59418bcbd2f80f14d70c42dc7ffac5cfd284d45d925230c7e85",
        "bytes": 73643,
        "pages": 1
      },
      "integrity": {
        "signed_object": "output_steam_network__network.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__network.content.json.asc",
        "digest_file": "output_steam_network__network.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__network.content.json.asc output_steam_network__network.content.json",
          "sha256sum -c output_steam_network__network.content.json.sha256"
        ]
      },
      "content": {
        "text": "开发者与代码库浏览器\n\n搜索一个节点。检查记录的关系。\n\n公共记录 / 关系网\n实时搜索\n图层筛选\n开发者总数3,320\n回购总额252\n显示的图表 / 集合子集468 节点 • 1103 边\n选定的个人资料记录\n\n💡 点击图中的任意节点，或在“搜索”栏中输入内容，即可查看其收集到的连接和源路径。",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "开发者与代码库浏览器"
          }
        ],
        "links": []
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/zh/output_steam_network__network.content.json",
      "export_json_sha256": "b2c6192a9157a7d879e3198630af6d5c2827ef03ddcfbac7f1d698bff46378a5"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "zh/output_steam_network/steam_ecosystem_dashboard.html",
      "language": "zh",
      "title": "数据透视：Steam档案",
      "source_url": "https://phishdestroy.io/steam_dossier/zh/output_steam_network/steam_ecosystem_dashboard",
      "source_html_sha256": "b7339f0a0adc1bd86a24f7e91e8bf6bcdc1edca0ad9411b38f39415ec6242943",
      "exported_at": "2026-09-29T00:21:48.301Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__steam_ecosystem_dashboard.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/zh/output_steam_network__steam_ecosystem_dashboard.pdf?v=print-20260929-v5",
        "sha256": "2431eeb3b827eb4657d47654a23dfd0c310925f20a52425fdce4491ae6de85c6",
        "bytes": 152500,
        "pages": 1
      },
      "integrity": {
        "signed_object": "output_steam_network__steam_ecosystem_dashboard.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__steam_ecosystem_dashboard.content.json.asc",
        "digest_file": "output_steam_network__steam_ecosystem_dashboard.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__steam_ecosystem_dashboard.content.json.asc output_steam_network__steam_ecosystem_dashboard.content.json",
          "sha256sum -c output_steam_network__steam_ecosystem_dashboard.content.json.sha256"
        ]
      },
      "content": {
        "text": "统计概览 // 文件 02\nSteam 生态系统仪表盘——网络数据一览\n\n该网络的数据概览。\n\n本节证明了什么\n\n该仪表盘汇总了3,320开发者及252代码库中的结构化情报，识别出68中与赌博相关的代码库以及跨平台连接桥。实证数据突显了地理聚类和开发者重叠现象，表明第三方赌博基础设施作为一项组织化、高度互联的软件产业，已与Steam的平台深度融合。\n\n← 返回高管简报\n\n调查数据库的汇总统计数据：地理分布、主要公司、皮肤赌博平台以及活跃的连接桥。\n\nScanned Devs3320\n回购总额252\n赌博相关文章68\n总连接数1,426\n自动化的结构与领域\n第一区——Valve公司核心区\n\n官方软件仓库和系统软件。Valve员工Nephyrin和Joe Ludwig的开发空间已确认。\n\n第二部分——授权引擎与协议仿真器（SteamKit）\n\n由Valve的Nephyrin与皮肤赌博游戏开发者DoctorMcKay共同编写的逆向工程网络库。\n\n第三板块——显卡挖矿客户（ArchiSteamFarm）\n\n利用 SteamKit 协议模拟器在后台运行数百万个虚假客户端（处于空闲状态），以刷取交易卡。\n\n开发者地理分布\n德国57\n美国52\n加拿大48\n英国44\n波兰30\n法国28\n俄罗斯联邦27\n中国27\n美国（华盛顿州）23\n澳大利亚19",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam 生态系统仪表盘——网络数据一览"
          },
          {
            "level": 3,
            "id": null,
            "text": "第一区——Valve公司核心区"
          },
          {
            "level": 3,
            "id": null,
            "text": "第二部分——授权引擎与协议仿真器（SteamKit）"
          },
          {
            "level": 3,
            "id": null,
            "text": "第三板块——显卡挖矿客户（ArchiSteamFarm）"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/zh/#briefing-heading"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/zh/output_steam_network__steam_ecosystem_dashboard.content.json",
      "export_json_sha256": "7cffe8f8d533b3951241839a6a6ae99236ba4f1abe2f0cded253cd5361760939"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "zh/output_steam_network/valve_ru_farming_isolated.html",
      "language": "zh",
      "title": "代码、贡献者与分叉——《Steam》专题报告",
      "source_url": "https://phishdestroy.io/steam_dossier/zh/output_steam_network/valve_ru_farming_isolated",
      "source_html_sha256": "52797855e22a4b1391325d0e0e6feb78f48b83f439acdfe6066a6862cca1b6dc",
      "exported_at": "2026-09-29T00:21:48.756Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__valve_ru_farming_isolated.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/zh/output_steam_network__valve_ru_farming_isolated.pdf?v=print-20260929-v5",
        "sha256": "d722795f2620cb9f39a498c64d186fa9c46552e8f33fdd562207e59fd649375a",
        "bytes": 155444,
        "pages": 2
      },
      "integrity": {
        "signed_object": "output_steam_network__valve_ru_farming_isolated.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__valve_ru_farming_isolated.content.json.asc",
        "digest_file": "output_steam_network__valve_ru_farming_isolated.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__valve_ru_farming_isolated.content.json.asc output_steam_network__valve_ru_farming_isolated.content.json",
          "sha256sum -c output_steam_network__valve_ru_farming_isolated.content.json.sha256"
        ]
      },
      "content": {
        "text": "第二部分 / 追踪有据可查的关系\n\n分支、贡献和软件依赖关系是明确的证据。这种观点保留了已收集的信息；而就业情况、安全漏洞利用以及犯罪参与情况则需要额外的信息来源。\n\n打开交互式能力地图 ↗\n公开来源 / 角色审核\n代码。贡献者。分叉。\n1. Nephyrin：分支与贡献\n\n提供的快照显示，Nephyrin 是 ValveSoftware/Proton 的贡献者，也是 SteamRE/SteamKit 和 SteamRE/open-steamworks 的分支创建者。其个人资料中列出了 Valve Software。这些字段应分别解读。\n\n一个分支记录了一个仓库的副本。此导出操作未附加任何提交，因此不会记录对 SteamKit 身份验证代码所做的更改。\n仓库引用 / 查看历史记录\nSteamRE/SteamKit ↗ SteamRE/open-steamworks ↗\n2. 公共功能：无需桌面客户端即可实现自动化\n\nSteamKit 和 node-steam-user 提供了与 Steam 进行程序化交互的功能。ArchiSteamFarm 记录了多账号卡片刷取的方法，并将 SteamKit2 声明为依赖项。\n\n这些是具体的自动化功能。无头执行并不构成专属商业用途，也不意味着绕过Steam Guard。关键问题在于所请求的凭据、该凭据可执行的操作以及平台所施加的控制措施。\n\n来源：各项目的 README 文件以及 ArchiSteamFarm.csproj。功能映射图将每个已记录的依赖项相互关联。\n3. JoeLudwig：hl2sdk 贡献者标签\n\n该快照显示 JoeLudwig 是 alliedmodders/hl2sdk、ValveSoftware/openvr 和 ValveSoftware/source-sdk-2013. 的贡献者。这是一种可观察到的项目关联关系。该导出数据并未提供任何证据，证明某项具体的 SDK 更改与盗版或赌博部署有关。\n\n仓库引用 / 查看历史记录\nalliedmodders/hl2sdk ↗ DoctorMcKay/node-steam-user ↗\n逻辑原理图 // 走线\n连接逻辑流程图：\n个人资料 关系\nNephyrin / 资料汇总\n贡献者：Proton。分叉者：SteamKit 和 open-steamworks。\n▼ 收集的分叉关系\n社区图书馆\nSteamRE/SteamKit\n由 SteamRE 组织维护的公共 Steam 网络库。\n▼ 声明了 SteamKit2 依赖项\n文档化的自动化\nJustArchiNET/ArchiSteamFarm\n文档中提到了跨多个账户刷卡的行为以及对 SteamKit2 的依赖。\n证据审查 / 来源概览\n已记录：独立贡献者和分支者的标签。\n已有文献证实：公共图书馆支持基于Steam的程序化交互。\n开放性问题：具体代码的作者身份、平台审批以及滥用行为的归责，均需分别提供证据。",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "代码。贡献者。分叉。"
          },
          {
            "level": 2,
            "id": null,
            "text": "1. Nephyrin：分支与贡献"
          },
          {
            "level": 2,
            "id": null,
            "text": "2. 公共功能：无需桌面客户端即可实现自动化"
          },
          {
            "level": 2,
            "id": null,
            "text": "3. JoeLudwig：hl2sdk 贡献者标签"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/zh/investigation_part2.html#automation-map",
          "https://github.com/SteamRE/SteamKit",
          "https://github.com/SteamRE/open-steamworks",
          "https://github.com/alliedmodders/hl2sdk",
          "https://github.com/DoctorMcKay/node-steam-user"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/zh/output_steam_network__valve_ru_farming_isolated.content.json",
      "export_json_sha256": "c1006395e936131cba760bb27d950c967995ca52c973fa48634a9439f357d38d"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ko/card_economy.html",
      "language": "ko",
      "title": "카드 경제 — Steam 도시에르",
      "source_url": "https://phishdestroy.io/steam_dossier/ko/card_economy",
      "source_html_sha256": "ae22c6dad41b710fc545413e232f4f95830fa660ad7d875f12154c6d361a7fc5",
      "exported_at": "2026-09-29T00:21:50.093Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "card_economy.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ko/card_economy.pdf?v=print-20260929-v5",
        "sha256": "bb02fd7612efa3ecfb7f665aca14d2fc6d46fd32a3914f6e2eda17934e92c834",
        "bytes": 251258,
        "pages": 17
      },
      "integrity": {
        "signed_object": "card_economy.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "card_economy.content.json.asc",
        "digest_file": "card_economy.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify card_economy.content.json.asc card_economy.content.json",
          "sha256sum -c card_economy.content.json.sha256"
        ]
      },
      "content": {
        "text": "부록 V — 카드 경제\n봇 팜은 Valve의 상점에 생긴 누수가 아닙니다. 그것은 고객.\n\nSteam 계좌는 해당 금액을 사용하기 전까지는 트레이딩 카드를 단 한 장도 받을 수 없습니다. $5.00 상점에서. 이 시스템은 자신이 소유하지 않은 게임은 파밍할 수 없으며, 무료로 받은 게임도 파밍할 수 없습니다. 따라서 자동화된 카드 파밍 시스템이 어떤 결과물도 생산하기 전에, Valve이 공표한 가격을 지불하여 계정당 이용 권한을 구매해야 합니다. 그런 다음 Valve의 자동화 조항은 해당 농장이 정확히 무엇을 생산하는지 한 줄 한 줄 명시하고 있다; 그 라이선스는 파밍된 카드가 현금으로 전환되는 모든 경로를 금지하며; 카드가 어쨌든 거래될 때 그 시장은 수수료를 가져갑니다 — 15%로 광고되지만, 판매당 최소 2센트로 책정되어, 센트 단위로 가격이 책정된 카드의 경우 이는 가격의 대부분을 차지합니다. 이 자료는 해당 거래의 규모, 프로필 최상위 레벨에 도달하는 데 드는 세트 수, 그리고 계정이 일반 트레이더의 것일 때 Valve의 집행 부서가 동일한 조항을 어떻게 적용하는지를 측정합니다.\n\n농장에서 가장 먼저 구입해야 할 것세트당 레벨 비용책상 양쪽카드 경제를 누가 조절하나요?\n$5.00계정에 카드를 등록하기 전에 스토어에서 지출 내역이 있어야 합니다 — Valve의 지원 페이지\n13,876Steam에 트레이딩 카드를 발행하고, 99,971가지 서로 다른 카드 유형을 보유한 게임\n694,673현재 91개의 상장된 트레이딩 봇이 보유하고 있는 완전한 카드 세트\n1,389,346해당 재고가 이미 소진한 계정 및 게임 카드 드롭 허용량, 최소한\n$9.99카드가 포함된 게임의 중간 가격 — 해당 게임의 완성 세트는 중간 가격으로 $0.74에 판매된다.\n97,114관리자 목록에 Valve 직원이 등재된 카드 거래 그룹의 회원들 — § 08\n01 — 과정\n농장이 실제로 무엇인지, 단계별로 알아보기\n\n이 내용은 해당 도구의 공식 문서와 Valve의 지원 페이지에만 근거하여 기술되었습니다. 이 섹션의 어떤 내용도 추론된 것이 아니며, 양측 모두 이에 대해 이의를 제기하지 않습니다.\n\n1단계\n매수\n\n해당 계정은 다음 조건을 충족해서는 안 됩니다. 제한된. Valve의 지원 페이지에서는 제한된 계정의 \"Steam 시장에 참여하기\", 출처: \"Steam 커뮤니티 아이템(트레이딩 카드, 부스터 팩, 보석 등) 거래\" 그리고 ~에서 \"프로필 레벨 Steam 획득 (레벨 0에 고정됨) 및 트레이딩 카드\". 게이트가 곧 돈이다: \"해당 Steam 매장에서 최소 $5.00 USD를 결제하셔야 합니다.\"\n\n2단계\n게임 구매하기\n\n카드는 소유한 게임에서만 획득할 수 있습니다. \"해당 게임에서 카드가 드롭되려면 Steam 계정에 해당 게임을 소유하고 있어야 합니다. 가족 공유는 소유로 간주되지 않으므로 인정되지 않습니다.\" 무료 노선도 운행이 중단되었습니다: \"프로모션 기간 중에 무료로 획득한 유료 게임에서는 카드 드롭을 목적으로 반복 플레이를 할 수 없습니다.\", 그리고 \"F2P 게임에서 돈을 한 푼도 쓰지 않고는 카드를 얻을 수 없습니다.\"\n\n3단계\n유휴\n\n이 도구는 계정을 Steam 네트워크에 헤드리스 모드로 로그인하며, \"배지를 분석합니다\", 획득 가능한 타이틀 목록을 생성하고 시작합니다 \"해당 게임을 플레이하면서, 게임 내 아이템을 이미 모두 모았는지 주기적으로 확인한다.\" 이 메커니즘에 대한 유지보수자의 설명: 그것은 \"그저 Steam에게 우리가 특정 게임을 하고 있다고 알리는 것 외에는 아무것도 하지 않는다.\"\n\n4단계\n방울이 다 떨어졌다\n\n각 제목은 유한합니다. \"모든 게임에는 카드 드랍 수량이 정해져 있습니다. 이 수량을 모두 획득하면(전체 세트의 약 절반 정도), 해당 게임은 더 이상 파밍 대상으로 삼을 가치가 없습니다.\" 계속 생산을 이어가려는 농장은 지속적으로 타이틀을 구매해야 합니다. 카드 공급량은 구매량에 따라 제한되는데, 이는 의도된 설계이며 Valve에게 유리한 구조입니다.\n\n5단계\n현금 인출\n\n이 카드는 세 가지 경로 중 하나를 통해 처리됩니다: 커뮤니티 마켓에서 판매되거나, 다른 플레이어와 교환되거나, 보석으로 분쇄되는 것입니다. 이 모든 경우 구독형 마켓플레이스 거래나 교환에 해당하며, § 3.D에는 이에 대한 요금이 명시되어 있습니다: \"Valve는 구독 마켓플레이스 내 거래에 대해 수수료를 부과할 수 있습니다.\" 이 단계가 바로 전체 과정을 규정 위반으로 만드는 단계입니다 — 참조: 05.\n\n출처: 2026-09-22에서 그대로 인용 및 발췌: Steam 지원 — 제한된 사용자 계정 ↗ · ArchiSteamFarm 자주 묻는 질문 ↗ · Valve — Steam 트레이딩 카드 자주 묻는 질문 ↗ · Steam 가입자 약관 ↗ 보관됨 2026-09-24 ↗. 이 페이지 전체에서 ArchiSteamFarm은 피고인이 아닌 측정 도구로 사용되며, 해당 문서의 설명에도 다음과 같이 명확히 명시되어 있습니다. \"ASF는 Valve로부터 승인을 받지 않았습니다.\".\n\n02 — 규모\n농장이 1센트라도 벌기 전에 이미 Valve을 지불한 상태다.\n\n제한된 계정은 카드를 받을 수 없기 때문에, 팜에 속한 모든 계정은 생산을 시작하기 전에 제한 상태를 해제해야 합니다. 기준 금액은 공개되어 있으며, 계정당 요금이 부과됩니다.\n\n농장 규모\t그 숫자가 어디서 나온 것인지\t카드 발급 자격을 얻기 위한 최소 매장 구매 금액\n10개 계정\tASF가 권장하는 천장 높이는 — \"내부 Valve 지침과 당사의 제안 사항을 바탕으로\"\t$50\n100~200개 계정\t동일한 FAQ에 명시된 기술적 상한선: \"단일 IP와 단일 ASF 인스턴스로 최대 100~200개의 봇을 실행할 수 있습니다.\"\t$500 – $1,000\n120개 계정\t아래의 제재 사례 3 — 영구 제재\t$600\n170개 계정\t아래의 제재 사례 2 — 2017년 겨울 세일 기간 동안 영구 이용 정지 조치됨\t$850\n1,000 계정\t아래의 제1호 집행 사례 — 거래 금지\t$5,000\n5,000개 계정 확인되지 않음\t계량기 이번 조사에 보고된 내용이며, 별도로 확인되지 않았음 — 출처에 관한 참고 사항을 참조하십시오.\t$25,000\n10,000개 계정 확인되지 않음\t계량기 이번 조사에 보고된 내용이며, 별도로 확인되지 않았음 — 출처에 관한 참고 사항을 참조하십시오\t$50,000\n\n이 페이지에 있는 수치 중 마지막 두 행만이 문서가 아닌 확인되지 않은 보고서에 근거한 것인데, 이 수치는 표에서 표시되어 있으며, 이에 대한 설명은 원산지 관련 참고 사항, 그리고 여기에는 그 외에는 그 어떤 것도 이에 의존하지 않습니다. 오른쪽 열은 Valve이 발표한 $5.00 USD 기준액에 대한 산술 계산일 뿐, 그 외에는 아무것도 아닙니다. 이는 바닥, 이는 농장의 운영 비용이나 Valve의 수익에 대한 추정치가 아닙니다. 이 수치에는 반드시 소유하고 있어야 하며 프로모션을 통해 무료로 획득할 수 없는 게임들은 제외되어 있으며, 카드를 판매할 때 커뮤니티 마켓에서 가져가는 약 15%도 제외되어 있습니다. 이 페이지에는 어떠한 수익 수치도 명시되어 있지 않습니다.\n\n그리고 Valve도 카드 드롭의 가격을 책정했습니다. 이 게임의 트레이딩 카드 FAQ에는 무료 플레이 전환율이 명백한 달러 금액으로 명시되어 있습니다:\n\n\"무료 게임은 게임 내 구매 내역에 따라 게임 카드를 지급합니다.\" 지출한 $9 USD당 (대략) “Steam 트레이딩 카드 베타가 시작된 이후로, 카드 1장을 획득하게 됩니다.”\n\n— Valve, Steam 트레이딩 카드 FAQ ↗ · 원문 그대로 확인됨 2026-09-22\n\n트레이딩 카드는 플랫폼이 손해를 보는 사은품이 아닙니다. 이는 Valve이 Valve에 공개된 가격으로 판매하는 상품이며, 이후 재판매 시 두 번째로 요금을 부과합니다. 그렇기 때문에 ‘카드 팜’에 대한 정직한 설명은 다음과 같지 않습니다. 기생충. 그것은 도매 구매자.\n\n구매하려는 물건의 실제 크기는 어느 정도인가\n\n이 부분부터 이 섹션의 끝까지 모든 내용은 측정된 결과일 뿐, 보고된 내용이 아닙니다. 카드 조사 데이터는 Steam Card Exchange가 공개한 배지 가격표에서 가져왔으며, 게임 자체의 가격은 Valve의 자체 스토어 API에서 가져왔고, 봇 재고 정보는 누구나 열람할 수 있는 공개 봇 디렉토리에서 가져왔습니다. 이 세 가지 자료는 모두 2026-09-22에서 읽어왔으며, 계산 과정은 다음에서 자세히 확인할 수 있습니다. 제08절.\n\n13,876카드를 발급하는 게임\n99,971서로 다른 카드 유형\n5 · 6 · 15세트당 카드 수: 최소, 중앙값, 최대\n$0.74완성품 세트의 중간 가격\n$23,586.57시장에 나오는 세트 중 하나씩\n그 집합은 어느 정도 크나요?\n\n13,876 세트에 포함된 카드 게임 수. Valve 그중 약 절반을 하나의 계정에 배분합니다.\n\n0\n1,250\n2,500\n3,750\n5,000\n5\n6\n7\n8\n9\n10\n11\n12\n13\n14\n15\n라이선스 비용은 얼마인가요?\n\nSteam 스토어에서 판매되는 동일 게임들의 정가(미국 달러 기준).\n\n0\n1,000\n2,000\n3,000\n4,000\n<$1\n$1-3\n$3-5\n$5-10\n$10-20\n$20-40\n$40+\n완성된 세트가 반환하는 내용\n\n동일한 게임의 완제품 세트 시세.\n\n0\n1,500\n3,000\n4,500\n6,000\n<$0.50\n$0.50-1\n$1-2\n$2-5\n$5-10\n$10+\n\n두 번째와 세 번째 차트를 서로 비교해 보면, 별도의 계산 없이도 거래 양상을 파악할 수 있습니다. 게임 수는 10달러 단위로 뭉쳐 있고, 게임에서 얻는 세트 수는 1달러 미만으로 뭉쳐 있습니다. 둘 다 동일한 13,876 게임의 개수를 나타내며, 같은 축 단위를 사용하고 있으므로, 이는 두 척도 간의 비교가 아니라 두 높이 간의 비교입니다.\n\n이것이 공급 측면입니다. 수요 측면은 Valve이 광고할 필요가 없는 부분인데, 이는 이미 공개되어 있기 때문입니다. 카드 거래 봇을 모아둔 하나의 공개 디렉토리에는 다음과 같은 목록이 있습니다. 현재 694,673 세트의 완제품을 보유하고 있는 봇이 91개 있습니다. 로그인도, 마켓플레이스 데이터 수집도, 개인 정보도 없습니다. 각 봇 이름 옆 페이지에 재고 수량이 표시되어 있습니다.\n\n그 주식을 여기서 유일하게 중요한 요소로 삼으세요. Valve의 원칙: \"대부분의 게임에서는 해당 게임의 카드 덱에 들어 있는 카드 수의 약 절반에 해당하는 수의 카드가 떨어집니다… 세트의 나머지 절반은 다른 커뮤니티 회원들에게서 모아야 합니다.\" 한 명의 계정만으로는 플레이를 통해 세트를 완료할 수 없습니다. 최소한 두 명의 계정이 필요하며, 각 계정이 해당 게임을 소유하고 있어야 하고, 게임당 한 번만 사용할 수 있는 드롭 허용량을 모두 소진해야 합니다. 드롭 허용량은 다시 채워지지 않습니다.\n\n694,673재고 보유 세트, 공개 봇 91개\n3,473,365카드, 최소 5장 이상으로 설정된 세트\n1,389,346소모된 드롭 허용량, 최소값\n2,602단 한 개의 게임만 보유한 계정, 봇 밀도가 가장 높은 계정\n694,673 세트가 놓여 있는 곳\n\n상장된 91개 카드 봇 중 재고 중인 완전 세트 수 기준으로 규모가 가장 큰 12개 업체입니다. 규모가 가장 큰 10개 업체가 합쳐서 248,115 세트를 보유하고 있으며, 이는 게시판에 올라온 모든 아이템의 35.7%에 해당합니다.\n\n0\n11,250\n22,500\n33,750\n45,000\nCard Supply #4 (High)\nN!vq's Leveling (High)\nAlice [BOT] LEVEL-UP RARE SETS\nN!vq's Leveling (Low)\nDisco Lite Level Up\nN!vq's Leveling (Mid)\nbaty131store.net | Level Up\nKitten - Supreme\nArashirn | Level Up\nSH (Junior) Level Up\nDuobot.com - Overstock\nlvlupbot.com - godlike\n\n그 139만 개의 허용량 전부는 해당 게임을 소유하고 있으며, $5.00 게이트를 통과한 계정에 속해 있었고, 다시는 그러한 드롭을 얻을 수 없는 계정들이었습니다. 이것은 미판매 재고 91개의 봇을 대상으로 한 것입니다. 이는 시장을 측정하는 지표가 아니라, 시장이 끝난 후에 남은 것을 측정하는 지표입니다.\n\n마지막 수치는 단순한 집계치가 아니라 분류표의 한 칸을 나타냅니다. 한 봇이 단 11개의 게임에서만 추출된 14,310 세트를 나열하고 있으므로, 해당 게임 중 적어도 하나는 1,301 세트로 표시되며, 이는 해당 게임을 구매한 서로 다른 계정이 적어도 2,602개 있음을 의미합니다. 이는 산술적으로 허용되는 최소 수치이며, 91개 봇 중 한 개와 관련된 사항입니다.\n\n이 바닥이 말해주는 것과 말해주지 않는 것\n\n이 봇들은 일반 플레이어는 물론 팜에서도 카드를 구매하며, 공개된 구매 가격이 바로 이 디렉토리의 핵심입니다. 따라서 139만 개의 할당량은 농가가 소유한 계좌의 수를 나타내는 것이 아닙니다. 이것들은 계정당 1회, 게임당 1회로 제한된 드롭 허용량을 Steam에서 어딘가에서 소진한 뒤, 판매되지 않은 채 상업용 재고로 남아 있는 것들입니다. 각 아이템의 소유 계정이 팜 계정이었든, 배지 페이지를 채우려는 십 대 청소년의 계정이었든, Valve이 획득한 것—$5.00 잠금 해제, 게임 라이선스, 그리고 거래가 성사될 때마다 발생하는 마켓 수수료—에는 변함이 없습니다. 15%가 아니라, 15% 또는 두 개의 1센트 최소 금액 중 더 큰 쪽, 이는 센트로 표시된 가격표상에서는 훨씬 더 큰 금액입니다. 계산식은 아래의 수수료 단계표. 이것이 바로 이 페이지의 요점이며, 농민들에 대한 불평이 아닙니다. Valve이 수수료를 부과하는 바로 그 행위가, “상업적 이용”을 이유로 개인을 영구적으로 차단할 때 그대로 인용하는 행위와 동일하기 때문입니다.\n\n이 수치는 또 다른 의미에서 하한선이기도 합니다. 이 수치는 오직 다음 조건을 충족하는 주식만을 포함하며, 오늘 등록되었으나 미판매된 상품 봇에 관해 공개 디렉터리에 포함되도록 선택하세요. 이미 판매된 모든 항목, 비공개로 보유된 모든 항목, 그리고 디렉토리 외부에 있는 모든 봇은 제외됩니다.\n\n게다가 Valve의 가격으로는 농업으로 비용을 감당할 수 없다\n\n가장 명백한 반론은 농장 운영자들이 값싼 게임을 사들여 고가의 카드를 제작한다는 점입니다. Steam의 자체 스토어 API는 이와 다른 내용을 보여줍니다. 카드가 포함된 13,876개의 게임 중, 13,713개에 대해 가격이 확정되었으며; 12,918은 유료 도서로, 정가 중앙값이 $9.99입니다. 완성 세트의 중간 판매 가격은 $0.74. 세트당 라이선스가 두 개 필요합니다. 따라서 세트의 중간값 가격은 대략 $19.98 게임 제작 라이선스 및 반납 건수 $0.74.\n\n2026-09-22에서 측정됨\t값\t이것이 해결하는 사항\n카드 사용 게임의 중간 정가\t$9.99\t거래에서 비용이 많이 드는 부분은 카드가 아니라 라이선스입니다.\n가격이 $4.99 이하인 게임\t3,665 (28.4%)\t아무리 값싼 꼬리라도, 그 꼬리에서 얻어지는 세트보다는 더 비싸다\n이 스토어에서 가장 저렴한 카드 게임\t$0.99\t일반적으로 $1.30 미만으로 판매되는 세트에 대한 라이선스 2개, $1.98\n게임 세트의 가격이 게임 본체 가격보다 비싼 게임들\t323 / 12,918 (2.5%)\t40경기 중 1경기에서는 Steam의 정가를 이용한 카드 차익거래가 발생한다\n조사 대상인 무료 게임\t795\t그리고 Valve은 각 드롭의 가격을 게임 내 소비액 $9으로 책정합니다.\n\n이로써 경제적인 측면에서 Valve에게 유리한 결론이 나며, 통상적인 주장과는 반대되는 결과가 나온다. Valve이 직접 책정하는 가격을 기준으로 보면, 카드 파밍은 Steam의 정가보다 낮은 가격에 취득한 라이선스에서만 효과가 있는 적자 사업입니다. — 번들, 지역별 가격 책정, 주요 재판매. 카드는 그저 부산물에 불과하다. 구매야말로 핵심이다. 그리고 그 구매는 Steam에 이루어졌다.\n\n농장이 실제로 지탱하고 있는 것은 무엇인가\n\n이 모든 조각들을 종합해 보면, 농장은 더 이상 Valve이 용인하는 대상이 아니라 Valve에게 꼭 필요한 것으로 보이기 시작합니다. 농장이 제공하는 모든 투입물은 Valve가 보고하거나 청구하는 산출물입니다. 한 봇 계정의 흐름을 따라가 보면:\n\n양육된 계정 하나“도매 고객”이지, 정보 유출이 아니다\n게임 판매량\n\n자신이 파밍하는 게임들 — 13,876 카드 게임부터 $0.50 숏웰웨어까지 — 을 구매합니다. 왜냐하면 카드는 소유한 게임에서만 드롭되기 때문입니다.\n\n\"온라인\" & 놀이 시간\n\n이들은 카드를 떨어뜨리도록 방치되어, Valve이 참여도 지표로 제시한 ‘동시 접속자 수’와 ‘총 플레이 시간’ 수치를 부풀리게 되는데, 이는 바로 § 4.C에서 “플레이 시간 조작”이라고 지칭하는 통계 수치이다.\n\n등록\n\n카드를 받으려면 먼저 $5.00 제한 계정 게이트를 통과해야 합니다. 계정당 실제 매장 결제 내역 Valve 건이 기록되어야 합니다.\n\n지갑 잔액 및 수수료\n\n판매되는 모든 카드는 마켓을 통해 다시 처리되며, 이 과정에서 소액 카드의 경우 수수료가 최대 66.7%에 달하고, 수익금은 Steam 지갑에 잠겨 있게 됩니다.\n\nSteam단계 PR\n\n배지와 레벨 Valve 순위표가 존재하는 이유는 세트가 제작되었기 때문이며, 그 순위표의 최상위권은 봇들이 차지하고 있다(§ 03 참조).\n\n팜을 제거하면 위의 모든 숫자가 사라집니다. — 게임 판매량은 적었고, ‘온라인’ 이용자 수는 적었으며, 계정은 등록된 적이 없고, 요금은 징수된 적이 없으며, 레벨도 달성된 적이 없었다. 바로 그 때문에 자동화를 금지하는 규칙이 수백만 개의 자동화 계정과 공존하는 것이다. 금지 조치는 하나의 선택지일 뿐이고, 실제 활동이야말로 수익원이기 때문이다.\n\n그리고 현금 인출 자체만으로도 가치가 감소하는 요인입니다 Valve 두 번의 세금이 부과되기 때문입니다\n\n카드는 루프의 끝이 아닙니다. Valve의 고유한 메커니즘 덕분에 카드는 보석, 그리고 보석을 사용하여 제작할 수 있습니다 부스터 팩 — 카드 세 장 더 — 이 카드들은 다시 판매되거나 파기된다. 각 단계는 시장 거래나 변환이며, 각각에 세금이 부과된다. 이 루프의 방향은 아래에서 측정된 수수료 하한선에 따라 결정되며, 별도의 모델이 필요하지 않다: 이 루프 내에서 판매되는 모든 카드는 적어도 2센트, 3에서 5까지의 가격으로 거래되는 카드의 경우, 크랭크를 한 번 돌릴 때마다 투입된 금액보다 적은 금액이 돌아옵니다. 이러한 순환 구조는 가상 가치를 파괴하고, 이를 대체하기 위해 수수료가 부과되는 새로운 거래를 강요합니다. 이 글에서는 그 손실 규모에 대한 구체적인 수치는 제시되지 않았다. — 세트당 수익은 이 조사에서 측정하지 않은 보석 획득률과 부스터 확률에 따라 달라집니다.\n\n트레이딩 카드소유 중인 게임에서 드롭되는 아이템\n→\n보석카드 파손, 수수료 부과\n→\n부스터 팩제작에 소모된 보석\n→\n새로운 카드 3장마켓에서 판매됨, 수수료 공제됨\n↶\n\n여기서는 메커니즘만 명시되어 있으며, 이는 Valve 고유의 메커니즘입니다. 즉, 카드는 보석으로 변환되고, 보석으로 부스터를 제작하며, 부스터에서 카드가 나옵니다. 이 모든 내용은 Steam 트레이딩 카드 FAQ에 기록되어 있으며, 각 단계는 과세 대상인 마켓 이벤트로 간주됩니다. 루프 메커니즘의 출처: Valve, Steam 트레이딩 카드 FAQ ↗.\n\n이는 단순한 순간이 아닙니다. 수년에 걸쳐 다져진 기반을 가진 산업입니다.\n\n단 한 번의 스냅샷은 우연의 산물일 수 있다. 따라서 2022년부터 2026년까지, 시즌별 Steam 세일이 있을 때마다 웨이백 머신을 통해 공개된 카드 봇 디렉토리를 한 번씩 확인했다. 봇들이 보유하고 있던 상품 구성과 동일한 계정들이 세일마다 반복적으로 나타났다. 경제 활동은 갑자기 나타나고 사라지는 것이 아니라, 안정적인 운영자 기반을 바탕으로 지속되며, 그 규모는 최고점 시점에 재고 300만 세트 완비 2023년 겨울 세일 기간 동안 — 한 시점에 한 디렉토리에 보관된 가치 있는 TF2 키가 30만 개 가량에 달했습니다.\n\n공개 봇 디렉토리에 보관된 완전한 카드 세트, Steam 판매 기준\n\n시즌별 세일마다 steam.supply/CardBots의 웨이백 스냅샷이 하나씩 제공됩니다. 마우스를 올려놓으면 해당 스냅샷의 환율 기준으로 계산된 TF2 키의 가치를 확인할 수 있습니다.\n\n0.0M\n0.9M\n1.8M\n2.6M\n3.5M\nA’22\nS’23\nW’23\nS’24\nW’24\nS’25\nS’26\n401판매 전반에 걸쳐 확인된 별개의 봇 계정들\n597건의 판매 중 5건 이상에 포함된 항목 — 안정적인 핵심 요소\n162022년부터 2026년까지 열린 7차례의 경매에 모두 참가\n322만재고 내 피크 수치 (2023년 겨울) ≈ $570k–790k 키\n한 판매자의 배지 순위표가 최상위권에서는 어떻게 보이는지\n\n수요 측이 공급 측과 일치합니다. 대중의 2024 여름 세일 배지 랭킹 보관됨 2026-07-16 ↗, 1위 계정이 판매 배지를 획득했습니다 1,740,645회 — 174만 세트의 10장짜리 카드 세트, 1,740만 장 단일 프로파일 장식으로 통합되었습니다. 경매의 시장 가격($0.50 세트당)으로 따지면 이는 ~$870,000 카드의 가치 측면에서 볼 때, 실제 구매 방식대로 — 즉, TF2 키를 봇의 레벨을 올리는 데 사용하는 방식으로, 키 1개당 약 7.6세트 분량 — 구매한다면, 이는 ~229,000 키, 약 $410,000–$570,000 실질적으로. 두 번째 계정: 552,000 세트, ~$130,000–181,000. 아무도 이를 위해 게임을 하지 않는다. 이는 구매되는 것이며, 구매 과정의 각 단계는 Valve이 청산하는 거래이다.\n\n방법 및 한계: 각 스냅샷에 나열된 봇들의 ‘set-stock’을 합산하며, 숫자 스냅샷당 봇 수는 판매별 비교가 불가능합니다. 일부 스냅샷에는 추천 봇만 표시되고, 일부에는 전체 디렉터리가 표시되기 때문입니다. 따라서 재고 수는 전체 집계치가 아닌, 표시된 내용의 최소값으로 간주됩니다. 키 값은 각 스냅샷의 키당 광고된 세트 수의 중앙값과 $1.79–$2.49 TF2 키를 사용합니다. 지속성은 스냅샷 전반에 걸쳐 SteamID64를 기준으로 합니다. 2021년 스냅샷은 이전 페이지 레이아웃을 사용했기 때문에 포함되지 않았습니다. 데이터: 농장 경제 연표.json; SteamLadder의 배지 레벨; Steam 카드 교환소의 설정 가격 (판매 시점의 Wayback 스냅샷 기준, $0.05 카드당).\n\n그리고 세일이 진행되지 않을 때도 그 함대는 여전히 그곳에 있습니다\n\n위의 두 사진은 서로 다른 두 집단이 아닙니다. 이는 같은 함대를 서로 다른 시점에 촬영한 것입니다. 이 섹션 상단에 제시된 디렉터리는 계절 세일이 진행되지 않는 평범한 날 — 2026-09-22 — 심지어 정지 상태에서도 그 상태를 유지했다 91개의 봇과 694,673 세트: 대략 186,000 TF2 키, $334,000–$464,000의 카드 가치, 미사용 상태 판매 사이. 이는 별다른 일이 없을 때 운영이 감당해야 하는 최소 수준입니다.\n\n그리고 이는 동일한 작업입니다. SteamID64로 일치하는, 그 91개의 휴면 봇 중 87개 — 96% — 역시 위의 7개 판매 스냅샷에 등장합니다, 각각에 16개씩 들어 있습니다. 이 디렉토리는 판매 시에만 열리고 그 후에는 닫히는 가판대가 아니라, 이 같은 함대가 그 규모를 무려 322만 세트 2023년 겨울 성수기에는 그 수치가 0으로 떨어지지 않습니다. 세일은 실제로 판매가 이루어질 때를 말합니다. 세일은 일 년 중 나머지 기간에도 존재합니다.\n\n봇별 기본 디렉터리\n\n각 사각형은 2026-09-22 디렉토리에 있는 봇 하나를 나타내며, 7개의 판매 스냅샷에도 등장하는 경우 강조 표시됩니다. 91은 그날 명부에 기재된 숫자일 뿐, 함대의 규모를 나타내는 것이 아닙니다. — 판매 현황 스냅샷에는 총 401개의 서로 다른 계정이 나타나며, 디렉토리에는 날짜에 따라 서로 다른 부분이 표시됩니다.\n\n지난 경매에서 확인된 상품 (87) 지난 스냅샷 이후의 새로운 내용 (4)\n\n동일한 공개 디렉터리에서 로그인 없이 비판매 기준값 2026-09-22을 읽습니다. 휴지 상태 값은 각 봇이 공표한 키당 세트 수와 그 위의 $1.79–$2.49 키 대역을 사용합니다. 중복 여부는 7개의 세일 스냅샷을 대상으로 SteamID64를 기준으로 확인합니다. 추천 상품 목록과 전체 상품 목록은 스냅샷마다 다르기 때문에, 이 비교는 재고와 식별 정보를 기준으로 하며, 사용자 수를 기준으로 하지 않습니다. 산술 연산은 제08절.\n\n03 — 사다리\n다른 항목은 이름 옆에 있는 숫자입니다.\n\n카드는 원자재입니다. 완제품은 Steam 레벨이며, Valve 세트로 가격이 책정됩니다.\n\n100Steam 레벨\n목표 레벨 — 드래그하거나 화살표 키를 사용하세요\n1세트 가격, USD\n\n$0.20은 조사 대상 중 가장 저렴한 풀세트이며, $0.74은 중앙값, $1.70는 평균값입니다. 이 수치는 카드만 포함하며, $5.00인 잠금 해제 항목이나 게임 라이선스는 절대 포함하지 않습니다.\n\n55,000XP 필요\n550소진된 세트 수\n110소장해야 할 게임, 직접 플레이하며 즐길 수 있는 게임\n$407.00그 가격대의 카드 가격\n1,100소진된 할당량, 최소\n$5,500.00$5.00 계정을 재사용하지 않을 경우 잠금 해제됩니다\n소모된 세트 수, 레벨 1 ~ 1,000\n\n배지 제작 1개 = 세트 1개 = 100 XP. 10단위 구간 내의 각 레벨은 그 아래 구간보다 100 XP 더 많이 소모됩니다.\n\n0\n12,625\n25,250\n37,875\n50,500\n1\n250\n500\n750\n1000\n667\n550 sets\n\n레벨은 Valve가 그냥 내버려 두는 장식물이 아닙니다. 계정 정보에 연동되어 있습니다. 배지를 제작하면 무엇을 얻을 수 있는지에 대해, Valve의 트레이딩 카드 FAQ에 다음과 같이 나와 있습니다: \"100XP를 획득하면 Steam 레벨이 상승할 수 있습니다.\" Steam 레벨이 올라가면 친구 목록의 최대 인원 수가 5명 늘어납니다., 그리고 아마도 ‘쇼케이스’ 기능을 통해 프로필을 나만의 스타일로 꾸밀 수 있는 기능을 이용할 수 있게 될 것입니다.\" 그리고 부스터 팩에 대해서는: \"레벨이 Steam 올라갈 때마다 부스터 팩 드롭 확률이 증가합니다: 레벨 10: +20%… 레벨 50: 드롭 확률이 100% 증가합니다(즉, 확률이 두 배가 됩니다).\"\n\n따라서 이 레벨은 두 가지 요소를 제어합니다 Valve: 친구로 추가할 수 있는 인원 수와 무료 카드가 인벤토리에 들어오는 속도입니다. 두 번째 요소는 누적 효과를 일으킵니다. 즉, 소비한 세트가 많을수록 플랫폼이 더 많은 콘텐츠를 더 빠르게 제공합니다. Valve은 이러한 재투자 루프를 제품에 구축했습니다.\n\n환율은 고정되어 있으며 공개되어 있습니다. 배지 제작을 한 번 할 때마다 완전한 세트 하나를 소모하며, 100 XP를 획득합니다; \"같은 게임에 대한 세트는 최대 5회까지 제작할 수 있습니다.\" 레벨당 XP 비용은 10레벨마다 증가합니다. 그 결과 다음과 같은 수치가 나오며, 여기에는 추정치가 전혀 포함되어 있지 않습니다:\n\nSteam 레벨\t이 제품이 소비하는 완전한 세트\t직접 만들어보려면 꼭 소장해야 할 게임들\t기록상 가장 저렴한 세트 가격($0.20)에서\t중앙값 집합 ($0.74)에서\t규모\n10\t10\t2\t$2.00\t$7.40\t\n50\t150\t30\t$30.00\t$111.00\t\n100\t550\t110\t$110.00\t$407.00\t\n200\t2,100\t420\t$420.00\t$1,554.00\t\n500\t12,750\t2,550\t$2,550.00\t$9,435.00\t\n667\t22,579\t4,516\t$4,515.80\t$16,708.46\t\n\n667은 가상의 수치가 아닙니다. 이는 공개 디렉토리에 등록된 단일 봇이 6,117개의 게임에 걸쳐 보유한 33,359개의 세트 중, 고객을 데려갈 수 있다고 광고하는 최고 레벨입니다. 네 번째 열은 전체 조사 대상 중 가장 저렴한 완전 세트와 비교한 동일한 가격대이며, 다섯 번째 열은 중앙값과 비교한 가격대입니다. 두 가격대 모두 카드 자체에 대한 시장 가격이며, $5.00 언락 비용과 게임 라이선스 비용은 완전히 제외되었습니다.\n\nValve가 이를 공개하지 않았기 때문에, 곡선이 어떻게 검증되었는지\n\nValve은 배지 획득률을 나타냅니다 (\"경험치 100점마다 레벨이 Steam 상승합니다.\") 그런 다음 이를 헤지하고 — \"(적어도 처음에는)\" — 단계 상승을 공개하지 않은 채로. 위에서 사용된 곡선은 표준 곡선으로, 10단위 블록 내의 각 레벨은 그 아래 블록보다 100 XP 더 비쌉니다. 이는 가정된 것이 아니라 디렉토리를 통해 검증된 것입니다. 즉, 게임당 5개 제작물 제한이 아닌 재고량에 의해 표시된 최대치가 제한되는 모든 봇의 경우, 이 곡선을 바탕으로 계산된 수치는 봇이 표시하는 수치와 정확히 일치합니다 — 541 대 541, 494 대 494, 464 대 464. 반면 상한선이 적용되는 경우, 산출된 수치는 몇 단계 더 높게 나오는데, 이는 경기당 선수층의 두께에도 좌우되는 상한선이라면 당연히 그래야 하는 현상이다. 레벨 667 이상의 곡선에 대해서는 어떠한 주장도 하지 않습니다.\n\n02절 옆에 있는 표를 보면 이 사업의 전체적인 윤곽이 드러납니다. 한 계정을 레벨 500으로 올리려면, 누군가가 12,750 세트를 완성해야 합니다. 각 세트는 최소 두 계정의 드롭 할당량을 소모했으며, 해당 계정들은 모두 $5.00 관문을 통과했고, 게임 본체를 소유하고 있었습니다. 프로필 상단에 표시된 하나의 허세 숫자는 그 아래에 있는 최소 25,500의 사용된 드롭 할당량에 기반을 두고 있습니다. Valve은 해당 거래를 잃지 않는다. Valve은 해당 거래의 모든 레그에 대한 상대방이다.\n\n04 — 통계\n이 조항은 농업을 막연하게 설명하는 것이 아니라, 구체적으로 열거하고 있다.\n\n§ 4.C는 일반적인 봇 방지 조항이 아닙니다. 이 조항에 열거된 예시들은 카드 팜이 생산하는 두 가지 항목을 차례로 나열하고 있습니다.\n\n\"사용자는 Steam의 콘텐츠 및 서비스와 상호작용하기 위해 어떠한 형태의 스크립트, 봇, 매크로 또는 기타 사람이 직접 제어하지 않는 시스템('자동화')도 어떠한 방식으로도 사용할 수 없으며, 여기에는 다음이 포함되나 이에 국한되지 않습니다:\n\nSteam 계정 생성 프로세스를 자동화하여,\n게임 플레이 통계 조작(예: 승패 수, 경험치, 플레이 시간 부풀리기 등),\n사용자의 실질적인 참여 없이 보상이나 진행 상황을 얻는 것은,\n“정보에 입각한 판단이 아닌, 미리 정해진 스크립트에 따른 행동을 통해 결과에 영향을 미치거나 사용자를 신고하는 등, 자동화된 수단을 통해 심사 시스템(동료 평가나 ‘오버워치’ 등)에 참여하는 행위.”\n— Steam 가입자 계약서 제4.C조 ↗ 보관됨 2026-09-24 ↗ · 그대로 인용함 2026-09-22\n\"…놀이 시간\"\n\n유휴 시간은 허상의 시간이 아닙니다. ASF FAQ는 이 질문에 대해 명확히 답하고 있습니다 — \"ASF를 통해 획득한 게임의 플레이 시간이 왜 늘어나지 않나요?\" — 제공: \"그렇긴 하지만, 실시간으로 업데이트되지는 않아요. Steam은 정해진 간격으로 플레이 시간을 기록하고, 그에 따라 업데이트 일정을 잡아요… 보통 30분 정도마다 업데이트되죠.\"\n\n이러한 이용 시간은 Valve의 기록, Valve의 상점 페이지, 그리고 Valve가 자체적으로 공개하는 동시 접속자 수 통계에 반영됩니다. Steam 차트 ↗ 보관됨 2026-09-23 ↗. 해당 수치에서는 비활성 계정과 게임 중인 계정을 구분할 수 없습니다. 플랫폼이 대외적으로 발표하는 참여 지표는 플랫폼 자체 규정에 따라 게임 중이 아닌 계정도 포함된 전체 사용자 집단을 기준으로 산출된 것입니다.\n\n\"…사용자의 진정한 의견이 반영되지 않은 채\"\n\n이는 Valve이 작성한 ‘유휴 카드 드롭’에 대한 정의입니다. 또한 이 정의는 Steam 레벨과 함께 제공되는 배지, 부스터 팩 획득 자격, 프로필 XP에 대한 설명이기도 합니다. ASF FAQ에서는 이 도구의 유효성을 확인하고 있습니다. \"부스터 팩을 받을 수 있는 권한을 유지합니다\", 공식 클라이언트와 똑같은 방식으로 로그인하기 때문입니다.\n\n따라서 보상 체계와 금지 행위는 두 가지 측면에서 바라본 하나의 메커니즘입니다. Valve은 보상이 기술이 아닌 시간에 의해 생성되도록 설계한 뒤, 그 시간을 소비하는 사람 이외의 어떤 수단으로도 보상을 생성하는 것을 금지하는 조항을 마련했습니다.\n\n05 — 상업적 이용의 함정\n농장형 카드에서 이루어지는 모든 출구는 라이선스에서 금지하는 출구이며, Valve은 입구에서 요금을 부과합니다.\n\n이 부분은 “책임감 있게” 수집한다고 해서 해결될 수 없는 문제입니다. 이 라이선스는 개인적·비상업적 용도로만 허용되며, 수집이 더 이상 개인적인 차원을 벗어나는 순간에야 비로소 카드의 가치가 생겨납니다.\n\n§ 2.A — 라이선스\n\n\"Valve는 본 계약을 통해 귀하에게 콘텐츠 및 서비스를 귀하의 용도로 사용할 수 있는 비독점적 라이선스 및 권리를 부여하며, 귀하는 이를 수락합니다.\" 개인적, 비상업적 용도 (단, 본 문서 또는 해당 구독 약관에서 상업적 사용이 명시적으로 허용된 경우는 제외합니다).\"\n\n§ 2.G — 제한 사항\n\n\"다음과 같은 권리는 없습니다: … (iii) 콘텐츠 및 서비스 또는 그 일부를 상업적 목적으로 악용하는 행위, 단, 본 계약(구독 약관 또는 이용 규칙을 포함함)의 다른 조항에서 명시적으로 허용된 경우는 예외로 합니다.\"\n\n§ 3.D — 수수료\n\n\"Valve는 구독 마켓플레이스 내 거래에 대해 수수료를 부과할 수 있습니다. \"모든 수수료는 거래가 완료되기 전에 귀하께 안내해 드립니다.\"\n\n이 세 가지를 종합해 보면 그 직책은 마감됩니다.\n\n보관만 해두는 카드는 농장 입장에서는 무가치합니다. 판매되거나, 거래되거나, 보석으로 분해된 카드는 가치를 창출하는 데 사용된 것입니다. Valve은 자체 집행 서한에서 이를 어떻게 명명했는지 밝혔습니다. 170개의 봇을 운영한 사용자에게는 계정이 \"Steam에서 수집용 카드를 불법으로 수집하는 데 사용되었을 뿐만 아니라, 이와 관련된 활동 및 상업적 활동 이외의 활동에도 사용되었다.\" 그 사건에서 카드는 시장에 출시되었고, 판매는 무사히 마무리되었으며, 수수료도 징수되었습니다. 금지 조치는 그 후에 내려졌습니다.\n\n그 입구의 요금은 15%이 아닙니다. 파밍된 카드에서는 요금이 3분의 2에 달합니다.\n\n§ 3.D 비축분 \"수수료\". 농장에서 실제로 생산하는 카드의 경우, 그 수수료는 광고된 ~15%과는 전혀 다릅니다. 커뮤니티 마켓은 5% Steam 거래 수수료와 10% 게임 수수료, 각각 $0.01을 하한으로 함 (Valve의 커뮤니티 마켓 FAQ). 1센트로 등록된 카드의 경우, 해당 바닥 가격은 는 가격: 구매자는 3센트를 지불하며, 그중 2센트는 수수료입니다. 하한 반올림으로 인해 표면상 15%인 금액이 실질적으로 부과되는 세금이 되어, 그 금액은 66.7% 카드 시장의 실상이 바로 여기에 있습니다 — 카드 한 장당 몇 센트에 불과하죠.\n\n커뮤니티 마켓 판매 시, 판매자의 매도 희망 가격 기준 실효 수수료\n\n5% Steam + 10% 게임, 각 게임당 최소 $0.01. 음영 처리된 구간은 트레이딩 카드가 실제로 거래되는 범위이며, 카드당 대략 $0.03–$0.05 정도입니다.\n\n0%\n10%\n20%\n30%\n40%\n50%\n60%\n70%\ncards\n$0.01\n$0.10\n$0.20\n$0.30\n$0.40\n$0.50\n66.7%\n판매자가 원하는 것은\tSteam 5% (최소 $0.01)\t경기 10% (분 $0.01)\t구매자 부담\t통합 수수료\n$0.01\t$0.01\t$0.01\t$0.03\t66.7%\n$0.03\t$0.01\t$0.01\t$0.05\t40.0%\n$0.05\t$0.01\t$0.01\t$0.07\t28.6%\n$0.08\t$0.01\t$0.01\t$0.10\t20.0%\n$1.00\t$0.05\t$0.10\t$1.15\t13.0%\n\n10% 게임 수수료는 카드를 발행한 앱에 귀속되며, 5%은 Valve의 몫이고, Valve의 자체 타이틀 및 기본 인벤토리 아이템에 대해서는 수수료 전액이 Valve의 몫이 됩니다. 어느 쪽이든 돈은 파머의 주머니에서 빠져나갑니다. 3센트짜리 카드를 판매하면 1센트를 돌려받고 2센트는 포기하게 됩니다. 이를 파머가 창출하는 5센트 미만 카드 판매 수십만 건에 곱하면 \"Valve가 부과할 수 있는 수수료\" 이는 단순한 부연 설명이 아니라 비즈니스 모델 그 자체입니다. 출처: Steam 커뮤니티 마켓 FAQ — 수수료 ↗ 보관됨 2026-09-21 ↗, 2026-09-22으로 읽으십시오. 이 곡선은 발표된 두 금리와 그 $0.01 최저 금리 기준에 따라 산술적으로 계산됩니다.\n\n이 도구의 어떤 구성 방식도 이 규정을 피할 수 없습니다. 한 사람이 하나의 계정에서 완벽한 자제력을 발휘하며 이 도구를 운영할 수 있더라도, 그 사람이 농사꾼 방식으로 획득한 카드 한 장을 지갑 자금을 위해 판매하는 순간, § 2.G에 명시된 동일한 처벌 조항이 1만 장을 운영하는 운영자에게 적용되는 것과 마찬가지로 그 사람에게도 적용됩니다. 따라서 Valve는 자사 마켓의 사실상 모든 카드 판매자에게 적용할 수 있는 위반 조항을 유보해 두었음에도, 사실상 그들 모두에게 이 조항을 적용하는 것을 거부했습니다. 그 정도 빈도로 시행되는 규칙은 규칙이 아닙니다. 그것은 선택 사항일 뿐입니다. 이 전시가 제기하는 질문은 ‘왜 카드 농사꾼들이 용인되는가’가 아니라; 왜 카드를 판매하는 개인 사용자에게만 같은 조치가 취해지는 반면, 그 카드들이 지탱하는 상업적 카드 경제—거래 서비스, 레벨업 봇, 대량 판매업자 등—는 공개적으로 운영되며, 그중 가장 큰 그룹 중 하나는 Valve 직원이 관리하고 있는지(§ 08). 규정은 소규모 보유자에게만 적용되고, 시스템에 대해서는 면제된다.\n\n06 — 집행 실적\n사전 공지 없이, 물결치듯, 전화번호를 따라 퍼져 나갑니다\n\nValve은 자동화 조항 바로 다음 조항에 사전 통지 없이 권한을 행사할 수 있다는 내용을 계약서 자체에 명시했다.\n\n\"Valve은 불법적이거나, 치트 또는 자동화 행위에 해당하거나, Steam 온라인 행동 수칙을 위반하는 어떠한 행위나 활동에 대해 귀하의 계정 또는 특정 구독을 제한하거나 해지할 수 있습니다. 귀하는 Valve가 귀하의 구독 및/또는 계정을 해지하기 전에 귀하에게 사전 통지를 할 의무가 없음을 인정합니다.\"\n\n— Steam 가입자 계약서 제4.D조 ↗ 보관됨 2026-09-24 ↗ · 원문 그대로 확인됨 2026-09-22\n\n1,000+ 봇 · 거래 금지. \"이 계정은 봇 계정 네트워크를 관리하는 데 사용된 것으로 보입니다. 봇 활동은 Steam 가입자 약관을 위반하는 행위입니다.\"\n\n170개 이상의 봇 · 영구 차단, 2017년 겨울 세일. \"이 계정은 Steam에서 수집용 카드를 불법적으로 수집하는 데 사용되었을 뿐만 아니라, 이와 관련된 상업적 활동 및 기타 활동에도 이용되었습니다. 해당 계정은 영구적으로 차단되었으며, Steam 고객지원팀에서는 이 문제에 대해 추가적인 지원을 제공할 수 없습니다.\"\n\n120개 이상의 봇 · 영구 정지됨. \"이 계정과 다른 계정들은 당사의 네트워크 인프라에 과도한 트래픽을 유발하는 데 사용되었으며, 이는 Steam 온라인 행동 수칙을 위반한 것입니다.\"\n\n— Steam ArchiSteamFarm FAQ의 “이 일로 인해 계정이 정지된 사람이 있나요?” 섹션에 실린 응원 메시지들. 출처 ↗ · 원문 그대로 확인됨 2026-09-22\n사례 4 — 2025년 6월, 가동 중단된 CS2에 대한 금지 조치\n\n위 세 가지 사례보다 더 최근의 사건은 프로젝트 자체 트래커에 기록되어 있습니다. 해당 도구를 통해 ‘카운터 스트라이크 2’를 유휴 상태로만 두었던 계정들은 VAC 건의 금지 — 관리상의 문제가 아니라, 부정행위를 방지하기 위한 종류의 문제입니다. 유지보수 담당자의 입장은, 유휴 상태로는 문제가 발생할 수 없다는 것입니다. 왜냐하면 \"그저 Steam에게 우리가 특정 게임을 하고 있다고 알려주는 것 외에는 아무것도 하지 않는다.\" 그 원인에 대해서는 논란이 있지만, 해당 계정이 차단되었다는 사실은 논란의 여지가 없다.\n\n— ArchiSteamFarm 토론 #3440, 2025년 6월 26일 개설 ↗ · 읽기 2026-09-22\n\n메인 계정이 사라지는 과정\n\n같은 게시물에서 한 프로젝트 협력자가 계정 차단 규칙을 다음과 같이 설명합니다: 계정은 차단될 수 있습니다 \"연쇄 등록\" 방식, 동일한 전화번호를 사용하는 경우 — \"단 한 건의 VAC 차단 조치일 뿐일 수도 있지만, 이 조치가 차단된 계정과 연결된 '정상' 계정들로까지 확산된 것일 수 있다.\"\n\nSteam Guard에서는 전화번호가 필요합니다. 채굴장은 운영자의 전화번호를 기반으로 구축됩니다. 따라서 단속은 일회용 계정에서 그치지 않고, 공유된 식별자를 따라 라이브러리, 친구 목록, 인벤토리를 보유한 계정까지 추적합니다. 이는 한 프로젝트 협력자가 설명한 메커니즘으로, 단 한 번의 조치로 운영자의 주 계정과 팜이 모두 제거되는 원리이며, 단속 물결로 인한 손실이 $5개의 계정으로만 측정되지 않는 이유이기도 합니다. (ASF GitHub 토론 #3440에서 한 프로젝트 기여자가 설명한 내용이며, 공식적인 Valve 확인이나 기록된 공식적인 선례는 없습니다.)\n\n5년 간격으로 세 명의 다른 에이전트가 작성한 동일한 문단\n\n농업 활동을 라이선스 위반으로 간주하는 조항 — 즉, 개인용 비상업적 라이선스의 상업적 사용 — 은 농장에만 적용되는 것이 아닙니다. 이는 Steam가 거래와 관련해 계정을 폐쇄할 때 항상 제시하는 사유이며, 해당 사유는 정형화된 양식으로 제공됩니다. 아래는 5년 간격으로 세 명의 서로 다른 담당자로부터 해당 통지를 받은 사람들이 공개한 세 가지 사례입니다.\n\n9월 29일 오후 7시 56분, Steam 지원팀의 메시지\n\n\"현재 작성 중인 계정은 Steam 가입자 계약 조건을 위반하여 잠겨 있습니다. 거래 내역, 커뮤니티 신고 및 기타 요소를 종합적으로 고려한 결과, 해당 계정이 상업적 목적으로 사용된 것으로 확인되었습니다.\"\n\n이 잠금 설정은 영구적이며, Steam 고객 지원팀에서는 이 문제에 대해 더 이상 도와드릴 수 없습니다.\n\n저희가 알고 있는 모든 정보를 제공해 드렸으므로, 이 지원 요청을 종료합니다. 이 문제와 관련하여 더 이상 답변을 받으실 수 없음을 유의해 주시기 바랍니다.\n\n감사합니다,\n\"할\"\n\n이 도움 요청은 종료되었습니다.\n2020년 9월 29일. 수신자가 다음 댓글과 함께 게시함 \"RIP 트레이딩.\" — @gergelyszabo94 ↗\n지원팀의 메시지 Steam 7월 12일 22:41\n\n\"현재 작성 중인 계정은 Steam 가입자 약관을 위반하여 잠겨 있습니다. 거래 내역, 커뮤니티 신고 및 기타 요소를 종합적으로 검토한 결과, 해당 계정이 상업적 목적으로 사용된 것으로 확인되었습니다.\"\n\n이 잠금 설정은 영구적이며, Steam 고객 지원팀에서는 이에 대해 더 이상 도움을 드릴 수 없습니다.\n\n저희가 알고 있는 모든 정보를 제공해 드렸으므로, 이 도움 요청을 종료하겠습니다. 향후 계정 잠금과 관련하여 제출되는 도움 요청은 답변 없이 종료될 수 있으니 이 점 유의해 주시기 바랍니다.\n\nSteam 지원\n\"비도\"\n\n이 도움 요청은 종료되었습니다.\n2024년 7월 12일, 포르투갈어 인터페이스. 수신인은 CS2 프로 선수입니다: \"이미 스팀 고객지원에 문의했지만 자동 응답만 오고 있어요… Faceit도 할 수 없고 프로 경기도 할 수 없어요.\" — @prcs25 ↗ 보관됨 2024-07-15 ↗\n수신자가 인용함, r/steamsupport\n\n\"안녕하세요. 귀하가 글을 작성하고 계신 계정은 Steam 가입자 이용약관을 위반하여 잠겨 있습니다. 거래 내역, 커뮤니티 신고 및 기타 요소를 종합해 볼 때, 해당 계정이 상업적 목적으로 사용된 것으로 확인되었습니다.\"\n\n이 잠금 설정은 영구적이며, Steam 고객 지원팀에서는 이에 대해 더 이상 도움을 드릴 수 없습니다.\n\n저희가 알고 있는 모든 정보를 제공해 드렸으므로, 이 도움 요청을 종료하겠습니다. 향후 계정 잠금과 관련하여 제출되는 도움 요청은 답변 없이 종료될 수 있으니 이 점 유의해 주시기 바랍니다.\n\nSteam 지원\n\"샐리\"\n\n세 번의 별도 요청에 따라 세 번 수령했습니다.\n2025년 3월 29일. 이 작성자는 계정 잠금 조치에 이의를 제기한 것이 아니었습니다. 이메일 계정과 함께 계정이 도용당했기 때문에, 다시 접속 권한을 요청하고 있었던 것입니다: \"계정 정지에 대해 묻는 것도 아니고, 이에 이의를 제기하는 것도 아닙니다. 그저 제 스팀 계정에 접속하고 싶을 뿐입니다… Valve은 제가 요청할 때마다 매번 똑같은 답변을 복사해서 붙여넣기만 하고는 요청을 종료해 버립니다.\" — r/steamsupport ↗, 본 조사에서 직접 수집한 불만 사례 코퍼스에 포함된\n\n한 단어 한 단어, 쉼표 하나하나, 55개월에 걸쳐, 세 명의 에이전트와 두 가지 인터페이스 언어를 통해 이루어졌습니다. 본문 전체에서 유일하게 수정된 부분은 2020년과 2024년 사이에 마지막 문장이 더 확고해진 것으로, 원래는 \"더 이상 답장을 받지 못하실 것입니다\" ~에 \"향후 도움 요청은… 답변 없이 종료될 수 있습니다.\" 이러한 결정이 어떤 과정을 거쳐 내려졌든 간에, 그 편지는 그 과정을 기록한 문서가 아닙니다. 명시된 사유는 “거래, 커뮤니티 제보 및 기타 요인”으로, 이는 하나의 범주, 출처를 알 수 없는 한 건의 제보, 그리고 이름이 밝혀지지 않은 나머지 요인으로 구성되어 있다.\n\n같은 방식으로 수집한 5건의 추가 사례입니다. 처음 세 건은 범주와 결과가 동일하며, 마지막 두 건은 같은 문구로 표현되었으나 서로 다른 규칙에 대한 답변입니다:\n\n날짜\t해당 계정이 한 일\t무슨 일이 있었나요?\t출처\n2021년 4월 12일\tBuff에서 물건을 사고 파는 방법 — \"버프, 일명 P2P 거래에서 물건을 사고 파는 것 말고는 다른 건 한 게 없어요\"\t커뮤니티 이용 정지: 마켓 이용 불가, 거래 불가, 고가 아이템 동결\tr/csgomarketforum ↗ 보관됨 2025-03-27 ↗\n2021년 12월 6일\tBuff 및 Bitskins를 통한 장비 구성 및 업그레이드용 일방적 P2P 거래\t상업용 영구 자물쇠와 공동 자물쇠: \"가짜 비공개 모드에 갇혀버렸어요… 제 프로필도 비공개 상태로 고정되어 있어요\"\tr/GlobalOffensiveTrade ↗ 보관됨 2021-12-06 ↗\n2024년 12월 20일\t2017년부터 계정을 유지해 왔으며, 수천 시간을 플레이했고, 커뮤니티 마켓플레이스에서 테마별 장비 세트를 거래하거나 더 좋은 장비로 업그레이드하고 있습니다.\t커뮤니티 잠금 기능이 포함된 영구 잠금, 사전 경고나 스트라이크 없음; 지원 \"그들의 결정이 최종적이라고 말한다\", 답변은 자동으로 제공됩니다\tr/csgomarketforum ↗ 보관됨 2025-06-27 ↗\n2024년 12월 23일\t1년 만에 돌아온 사용자가 VPN을 통해 지갑에 자금을 충전했습니다. \"일반적인 인터넷 보안용으로만\"\t영구적인 커뮤니티 이용 정지 및 아무런 이유도 제시되지 않았다: \"이 차단 조치는 영구적이며, 추가 정보를 제공할 수 없으며, 향후 접수되는 티켓은 답변 없이 종료될 수 있습니다.\" 196개의 좋아요, 340개의 댓글\tr/steamsupport ↗\n2026년 4월 8일\t수년 동안 이란에서 물건을 구매해 왔지만, 작성자는 게시물을 올린 적도 없고, 마켓을 이용한 적도 없으며, 포럼을 이용한 적도 없다고 밝혔습니다.\t커뮤니티 접속이 제한되었습니다 2038년까지 ~을 넘어서 \"제재 대상 지역\"; Azul이라는 담당자가 티켓을 종결했습니다. 같은 계정에 대한 환불 요청은 1년 전, 동일한 이란 IP 주소에서 접수되었을 때 승인된 바 있습니다. 도서관과 돈은 Valve에게 남게 된다.\tr/pcgaming ↗\n\n마지막 행은 나머지 항목들과는 다른 규칙 — 상업적 용도가 아닌 제재 준수 — 을 다루고 있으며, 답변의 형태가 동일하기 때문에 포함되었습니다. 즉, 범주 지정, 증거 없음, 이의 제기 불가, 티켓 종결입니다. 또한 이 항목은 다른 항목들에서는 제기되지 않는 의문을 불러일으킵니다. 해당 계정에 서비스를 제공하는 것이 불법이었다면, 수년간의 지불금을 수령한 것 또한 불법이었을 것입니다. 이 두 가지 입장 중 하나는 틀린 것이며, 그중 오직 하나만이 고객에게 금전적 손해를 끼쳤습니다.\n\n8건 모두 2026-09-22에서 확인되었습니다. 2021년 및 2024년 12월 게시물 스레드는 인터넷 아카이브(Internet Archive)의 스냅샷을 통해, 나머지는 레딧(Reddit)의 공개 프론트엔드를 통해 확인했는데, 이는 레딧 측이 수집 담당자의 직접적인 요청을 거부했기 때문입니다. 2020년과 2024년에 작성된 두 통의 편지는 현재도 게시 중인 원본 게시물에 첨부된 스크린샷을 바탕으로 전사되었습니다. 본 조사에서는 이 계정들 중 어느 것도 무죄나 유죄라고 단정하지 않습니다. 바로 그 점이 핵심입니다. 그 편지만으로는 어떤 독자도, 어떤 규제 당국도 알 수 없다.\n\n조달 관련 참고 사항 — 운영자 차원의 손실\n\n이번 조사에서 인터뷰한 사업자들은 약 각각 5천에서 1만 개의 계정 단일 단속 작전 형태로, 농장과 함께 주요 계정을 대상으로 단속을 실시했다. 해당 여론조사는 조사 결과로 기록된 것이 아니라, 제1자 보고로 여기에 기록되어 있습니다. 이 항목에는 공개된 표본 크기도, 고정된 수집 날짜도, 계정별 검증도 없으며, 이 페이지의 다른 어떤 수치도 이에 의존하지 않습니다. 섹션 02에서 이 항목에 기반한 두 행은 해당 사항이 명시되어 있습니다.\n\n이 내용이 생략되지 않고 명시된 데에는 두 가지 이유가 있습니다. 앞서 언급한 체인 금지 메커니즘이 바로 그 패턴에 대한 공식적인 설명입니다. 그리고 규제 당국은 이 문제를 해결할 수 있는 단 하나의 기록, 즉 자동화 조치 대상이 된 계정 수가 몇 개인지, 어느 단계에서 조치되었는지, 그리고 해당 계정들이 폐쇄되기 전까지 매장에서 각각 얼마를 지출했는지를 Valve로부터 강제적으로 확보할 수 있습니다. 그 기록이 존재하기 전까지는 그 수치는 현재와 같이 — 보고되고, 귀속되었으나 입증되지 않은 상태로 — 남아 있을 것입니다.\n\n07 — 비대칭성\n같은 책상의 양쪽\n\n그 증명 기준을 자사의 지원 작전에 적용된 Valve 기준과 비교해 보십시오. 오른쪽 열은 이 문서의 자체 사건 기록부로, 원문에 포함된 유보 사항까지 그대로 재현한 것입니다.\n\n거래를 위한 고객\n\n2020–2026년 동안 보고된 8건의 사례\n\n행동\n제3자 마켓플레이스에서 상품을 판매하거나 구매한 경우; 한 건의 사례에서는 어떠한 행위도 없었으며, 해당 계정이 도용당한 것이었습니다.\n제시된 증거\n없음. \"거래 현황, 커뮤니티 보고 및 기타 요인을 바탕으로.\"\n공지\n없음. Valve는 § 4.D에서 다음과 같이 규정하고 있다: \"Valve은 계약 해지 전에 귀하에게 통지할 의무가 없습니다.\"\n항소\n\"이 잠금은 영구적이며, Steam 고객지원팀에서는 이에 대해 더 이상 도움을 드릴 수 없습니다.\"\n티켓\n첫 번째 답변으로 종결되었습니다. 추가 요청 \"답변 없이 마감될 수 있습니다.\"\n도달 범위\n프로필, 친구 목록, 채팅, 마켓, 인벤토리, 그리고 실제 돈으로 구매한 모든 아이템.\n기간\n영구적.\n대량 처리를 위한 자동화된 봇 군단\n\n694,673 91개의 봇에 걸쳐 공개 재고에 있는 완전한 세트\n\n행동\n수천 개의 계정에서 동시에 자동화된 헤드리스 스크립트를 실행하여 카드를 유휴 상태로 전환하고, 배지를 대량으로 생성하며, 산업적 규모로 세트를 거래합니다.\n제시된 증거\n공개적으로 운영되는 봇 디렉토리(steam.supply, SteamLvlUp)와 회원 수가 수백만 명에 달하는 공개 그룹.\n공지사항\n전혀 개입하지 않는다. 88.97% 어떠한 종류의 금지 조항도 적용되지 않습니다; 99.8% 나머지 금지 조치 중 일부는 형식적인 것에 불과하다.\n항소\n필요하지 않습니다. 함대는 수년에 걸친 수명 주기 동안 중단 없이 지속적으로 운용됩니다.\n티켓\n—\n도달 범위\n제한 없는 아이템 교환, 배지 레벨업, 그리고 시장 유동성.\nValve에 대한 이점\n$26.8M+ 최소 매장 구매 금액(계정당 $5.00 입구 비용)과 15% 커뮤니티 마켓 거래 수수료가 차감됩니다.\n이를 통해 제기되는 질문은, 간단히 말해\n\n카드나 아이템을 수동으로 거래하는 개인 이용자는 § 4.C(자동화) 또는 § 2.G(상업적 이용)에 따라 영구적이고 이의 제기 불가한 제재를 받게 됩니다. 수천 개의 계정에서 헤드리스 봇을 운영하는 자동화된 파밍 플릿은 88.97%의 제재 미적용 비율을 유지하며 공개적으로 활동하고 있습니다. Valve은 이 두 가지 모두의 수혜자입니다.\n\n이러한 불균형은 경제적 측면에서 비롯됩니다. 개인 트레이더들은 플랫폼에서 가치를 가져가는 반면, 자동화된 카드 군단은 Valve의 매장 지출 게이트(계정당 $5.00)로 수백만 단위를 쏟아붓고, 재판매가 이루어질 때마다 거래 수수료를 발생시킵니다. 규제는 문서화된 규칙을 따르는 것이 아니라 수익 모델을 따릅니다.\n\n08 — 거버넌스\n카드 경제를 누가 조절하는가\n\n이 보고서의 반복적으로 나타나는 결론, 즉 Steam을 둘러싼 제3자 계층의 인력이 Steam 내부에서 충원된다는 사실은 카드 경제에서도 마찬가지로 적용되며, 이는 특정 결론으로 귀결됩니다: Valve의 집행 조치가 실제로 어떤 결과를 초래하는지 독립적인 입장에서 파악할 수 있는 사람은 아무도 없습니다. 왜냐하면 이를 파악할 수 있는 주체가 바로 그 계층 내부에 위치해 있기 때문입니다. 아래의 모든 사실은 2026-09-22에 있는 Valve의 공개 그룹 및 프로필 페이지에서 확인한 것이며, 누구나 브라우저를 통해 재현할 수 있습니다.\n\nValve명의 직원이 최대 규모의 카드 거래 그룹을 운영하고 있다 Valve명 직원\n\nCardTrades ↗ 자체 헤더에서 스스로를 다음과 같이 설명하고 있습니다. \"Steam 카드 교환 공식 그룹\" 그리고 운반하며 97,114명의 회원. 해당 그룹의 운영자 목록(즉, 그룹 관리 권한을 가진 계정들)은 다음과 같습니다. Mickmane, SgtFopper 그리고 afarnsworth ↗.\n\n그 마지막 프로필은 Valve의 자체 사이트 마크업에 의해 Valve 직원으로 표시되어 있으며, 해당 페이지에는 class=\"profile_header_valve_employee\" — 그 위치를 다음과 같이 명시하고 있다. 워싱턴주 벨뷰, 그리고 다음의 범주에 속합니다. Valve, Steam 그리고 Steam 트레이딩 카드 그룹 그룹. SteamID64 76561197960434622, 2003년 9월 12일부터 회원으로 활동 중입니다.\n\n이 관찰은 개인적인 것이 아니라 구조적인 것이며, 그것은 아니다 한 가지 분명한 점은 — 카드 거래 그룹의 운영자가 봇을 운영하고 있지 않으며, 여기에는 그 반대를 시사하는 어떤 단서도 없다는 것입니다. 핵심은 다음 조항에 있습니다. 제07절. Steam Card Exchange는 제3자 상업용 카드 서비스이며, 제3자 서비스를 통해 카드를 거래하는 행위는 Valve에 따라 일반 계정을 영구적으로 차단하는 바로 그 행위입니다. \"거래 내역, 커뮤니티 신고 및 기타 요소를 바탕으로 상업적 목적으로 사용됩니다.\" A Valve 직원은 9만 7천 명이 소속된 해당 서비스의 공식 커뮤니티 그룹에서 공식 운영자 역할을 맡고 있습니다.\n\n이 글에서는 어떤 개인에 대해서도 부정행위에 대한 주장이 제기되지 않습니다., 그리고 그 역할이 무엇을 포함하는지에 대해서는 아무런 추론도 이루어지지 않습니다. 바로 이러한 비대칭성이 핵심입니다: 일반 계정이 제3자 카드나 스킨 서비스를 이용할 경우, 증거 제시 없이 티켓이 종결되고 영구 차단 조치가 내려집니다. 반면 해당 서비스가 이 서비스일 경우, Valve 직원이 운영자 목록에 포함되어 있으며, 이러한 배치는 Valve이 직접 게시한 페이지에서 확인할 수 있습니다. 요구되는 바는 이 자료집의 다른 모든 부분에서 요구되는 것과 동일합니다. 서면 승인서가 있다면 이를 제시하십시오. 만약 필요하지 않다면, 서면으로 그렇게 명시해 주십시오. 06과 소속 8명의 직원들에게는 정반대의 내용이 전달되었기 때문입니다.\n\n차단 목록 계층 및 이를 관리하는 주체 자원봉사 운영자제3자 서비스\n\nSteambans.com의 그룹 (보관됨) ↗ (라이브 ↗ 보관됨 2025-12-03 ↗)는 보존된 분류군 설명에 그 계통을 기록하고 있다: \"Steambans.com의 공식 Steam 커뮤니티 그룹입니다. SteamBans.com은 오래된 개념을 바탕으로 한 새로운 서비스입니다. VALVe의 구 WONID 프로그램에서는 수년 동안 글로벌 차단 목록이 운영되어 왔습니다. STEAMID로 변경되면서, 저희는 이 새로운 시스템에 특화된 서비스를 개발하는 것이 당연한 일이었습니다. 하지만 저희는 그 이상을 원했습니다. *. 2013년에 서비스를 종료한 Steambans의 아카이브 페이지입니다.\" 등재된 관리자 목록에는 다음이 포함됩니다. devicenull 그리고 killahinstinct_ ↗.\n\n해당 관리자 계정은 아님 a Valve 직원 — 직원 표시가 되어 있지 않습니다. 이 사람은 유난히 높은 지위를 가진 자원봉사자로, ~의 일원입니다. 커뮤니티 운영자 (회원 414명, 다음과 같이 설명되는 그룹) \"Steam의 커뮤니티 운영진이 작성함\"), 의 위키 코디네이터, 의 Steam 커뮤니티 마켓, 그리고 다음을 포함한 Valve 프로그램 및 사전 공개 그룹: Valve 파이프라인, Steam 클라이언트 베타, 모바일 인증 베타, 새로운 Steam 커뮤니티 베타, Steam 연구실, 스팀웍스 그리고 사기 URL 신고하기. SteamID64 76561197960794555.\n\n또한 해당 서클 내에 속해 있으며, 자신의 공개 그룹 명단에 Steambans를 직접 표시하고 있는 사용자: msart ↗ (그룹 명단 ↗), SteamID64 76561197977933359, 해당 프로필에는 다음과 같이 적혀 있습니다. \"저는 steamid.uk를 비롯해 스팀 관련 및 비스팀 관련 여러 사이트를 운영하고 있습니다.\", 그리고 16개 단체로 구성된 연계 네트워크를 운영하고 있는 — SteamIDcouk (주요 그룹 “Sid 웹사이트”), SidAdmins, SidBans, steamideu, Steam3ID, s-id 그리고 SArchive 그들 중에서.\n\nsteamid.uk는 그 자체로 동일한 번호를 명시하고 있습니다. 해당 사이트의 FAQ에는 다음과 같이 나와 있습니다: \"SteamID는 누가 만들었나요? SteamID 웹사이트, 네트워크 인프라 및 보안 시스템은 모두 76561197977933359에서 관리하고 있습니다.\" 그 아래 두 번째 답변에서 데이터의 출처가 명시되어 있습니다: \"SteamID는 데이터 수집을 위해 주로 Steam 웹 API를 사용합니다.\" 이 페이지에는 서로 다른 호스팅 업체에 분산된 여러 대의 전용 서버와, 외부 개발 서버, 스토리지 및 텍스트 검색 서버, 그리고 별도의 백업 시설에 대해 설명되어 있습니다.\n\n인터넷 아카이브에 보존된 기록을 통해 확인된 바에 따르면: 해당 2025년 12월 3일자 Steambans 그룹 스냅샷 ↗, 그 2024년 9월 14일 기준 운영자 프로필 요약 ↗, 그리고 2026년 4월 1일 기준 steamid.uk FAQ 요약 ↗, 2026-09-22에서 직접 읽은 데이터와 일치하는.\n\n이 모든 것이 결국 무엇을 의미하는지, 그리고 무엇을 의미하지 않는지\n\n차단 목록, 스팀 ID 확인, 카드 거래는 누가 신뢰할 수 있는지, 누가 식별 가능한지, 그리고 아이템의 가치가 얼마인지를 결정하는 세 가지 서비스입니다. 이 세 가지 서비스 중 어느 것도 Valve이 운영하지 않습니다. 각 우주선에서 조종석을 맡은 사람들은 Valve의 궤도 내부에서 온 사람들이었다: 카드 서비스 공식 그룹의 운영자 목록에 등재된 Valve 직원; 출시 전 프로그램에 접근 권한을 가진, 오랫동안 활동해 온 Valve 커뮤니티 운영자로, 차단 목록 그룹을 관리하고 있는 인물; 같은 모임에 속한 한 개인이 운영하는 ID 확인 서비스. 세 가지 서비스, 세 개의 제어 인터페이스, 그리고 Valve가 이미 지위를 부여한 세 명의 인물.\n\n그룹 회원 자격은 고용 관계가 아니며, 이 모든 내용은 어떤 비난도 아닙니다. 이는 거버넌스의 상식이며, 바로 이것이 일반적인 변론이 — 그들은 제3자라서, 우리가 통제할 수 없습니다 — 무작정 받아들이기보다는 검증되어야 한다. 통제권을 쥔 사람들은 Valve에 대해 낯설지 않다. Valve만이 그들에게 무엇을 요구했는지, 혹은 요구한 것이 있다면 그것이 무엇인지 말할 수 있는 입장에 있으며, 외부인 중 누구도 그 사실을 알아낼 수 없다.\n\n아무도 집계하지 않는다. 이것이 조사 결과다.\n\nSteam ID 공간은 연속된 정수 범위입니다. 이 범위를 샅샅이 뒤져 차단된 계정 수, 이용 제한을 받은 계정 수, 거래 차단 조치로 인해 유휴 상태인 재고량을 보고하는 것은 연구 프로그램이 아닙니다. 이는 단순한 반복 처리와 API 키에 불과합니다. Valve은 그 키를 직접 제공하며, steamcommunity.com/dev/apikey. 그런데도 그 인구조사 결과를 발표하는 독립 기관은 없습니다. 규제 당국도, 언론인도, 학자도, 소비자 단체도 아닙니다. Steam에 대한 단속 규모에 관한 유일한 공개 수치는 Valve이 언급하기로 선택한 것들뿐입니다.\n\n해당 기능이 없는 것이 아닙니다. 단지 보류 중일 뿐입니다. ID 공간을 대규모로 해결하고 색인화하는 서비스인 steamid.uk는 자체 FAQ에서 다음과 같이 밝히고 있습니다. \"주로 Steam 웹 API를 활용하여 데이터를 수집합니다\" 그리고 이를 여러 대의 전용 서버, 외부 저장소, 텍스트 검색 서버 및 별도의 백업 시설을 통해 운영합니다. 이 시스템은 한 명의 개인에 의해 운영됩니다. 그의 차단 목록에 포함된 자매 그룹은 Valve 커뮤니티의 오랜 기간 활동해 온 운영자가 공동 관리하며, 이 운영자는 Valve의 사전 출시 프로그램에 접근할 수 있는 권한을 가지고 있습니다. 집계 결과를 공개할 수 있는 입장에 있는 한 정당은 Valve의 영향권 내에 있지만, 이를 공개하지 않고 있다.\n\n이는 해당 보고서가 다른 모든 곳에서 발견한 것과 동일한 양상입니다. Steam 경제와 관련해 핵심적인 결정을 내리는 모든 서비스 — 누가 신뢰할 수 있는지, 누가 신원을 확인할 수 있는지, 특정 품목의 가치는 얼마인지, 누가 이용 금지 대상인지 등 — 는 명목상으로는 제3자이지만, 실질적으로는 Valve과 밀접한 관계를 맺고 있습니다. Steam ‘카드 교환’도 그 패턴의 예외가 아니라, 그 패턴의 또 다른 사례일 뿐이다. 이들이 독립적인 운영자라는 주장이 Valve에 적용될 수 있는 이유는, 바로 지금까지 그 누구도 이를 어떤 수에 대입해 검증해 본 적이 없기 때문이다.\n\n1,088만 계정 조사: 88.97% 미조사\n\nArchiSteamFarm 설치 기반에 대한 감사가 Valve 전반에 걸쳐 실시되었으며, GetPlayerBans 종점 (10,880,610 계정, 55분). 제한이 없는 부분집합만으로도 $26.8M+ 최소 매장 구매 금액($5.00 진입 기준)에서. 9,680,599 계정(88.97%)에는 어떠한 종류의 제한도 없습니다., 그리고 나머지 99.8%에 대해서는 자동 거래 기능을 계속 사용할 수 있도록 허용하는, 형식적인 커뮤니티 이용 정지 조치만 내려집니다.\n\n5,360,499제한이 없는 ASF 회원 (Steam의 표시된 수)\n10,880,610스캔된 총 API 항목 수 (제한됨 + 제한되지 않음)\n9,680,599한 번도 차단된 적 없음 (88.97%)\n1,200,011Steam 금지 (11.0%) — 99.8% 외형 아이템\n55분전체 인구를 조사하기 위해서는 한 가지 핵심적인\n법의학적 증거 및 심층 인구조사\n\n금지 유형별 분포 차트, 제재 당시 계정 사용 기간, 개설 연도별 그룹(2020~2026년), 그리고 사용자가 직접 보고한 지역 정보 등을 포함한 상세한 인구통계학적 분석 결과는 별도의 인구조사 조사 보고서에 게재되어 있습니다.\n\n전체 10.88M 금지 조치 현황 조사 결과(증거자료 VI) 열기 →제4절 — 자산 ID 표시 차단 →\n\n그러므로 제기해야 할 질문은 다음과 같으며, 이에 대한 답은 오직 Valve만이 줄 수 있습니다: 어떤 식별자나 기능이 철회되었는지, 언제 철회되었는지, 누구의 결정에 따른 것인지, 그리고 해당 조치가 대상 운영자들에게 어떤 가시적인 영향을 미쳤는지 — 이를 시도하던 외부 모든 사람에게 미친 영향과 대조된다. 독립적인 감사를 종식시키는 변화가 안전 조치로 발표되었다고 해서 중립적이 되는 것은 아니다. 이것이 바로 위 단락에 언급된 인구 조사가 존재하지 않는 이유다.\n\n09 — 방법 및 한계\n무엇이 읽혔는지, 그리고 무엇이 주장되지 않았는지\n\n이 페이지에 실린 모든 인용문은 2026-09-22의 실시간 소스에서 가져와 그대로 재현한 것입니다. 여기 실린 내용은 스크래핑, 마켓플레이스 인증 정보 또는 비공개 데이터셋에서 추출한 것이 아닙니다.\n\n네 가지 데이터셋과 이를 대상으로 한 연산\n\n이것들은 각각 터미널에서 재현 가능한 단일 공개 요청입니다. 계정을 사용하지 않았으며, 마켓플레이스에 로그인하지 않았고, 인증 정보가 필요한 엔드포인트도 호출하지 않았습니다.\n\n데이터 세트\t어디서 왔는지\t이를 바탕으로 무엇이 산출되었는가\n카드 현황 조사\n13,876 경기\tSteam Card Exchange가 공개한 배지 가격표, 즉 해당 사이트의 배지를 표시하는 데 사용되는 바로 그 피드 공개 가격 페이지 ↗ 보관됨 2026-08-04 ↗\t카드를 발행하는 게임, 세트당 카드 수, 서로 다른 카드 유형, 그리고 완성된 각 세트의 시장 가격. 중앙값과 $23,586.57 합계는 본 조사의 산술적 결과입니다.\n게임 가격\n13,713 해결됨\tValve의 자체 공개 스토어 엔드포인트, store.steampowered.com/api/appdetails, 참조=us, 가격 필드만, 일괄 처리\t카드가 포함된 게임의 정가 중앙값 및 분포; 완성된 세트의 판매량이 해당 게임 자체의 판매량을 초과하는 게임의 개수.\n봇 주식\n91개의 봇, 694,673 세트\t다음 주소의 공개 카드 봇 디렉토리: steam.supply/CardBots ↗, 표시된 대로 읽기, 로그인 불필요\t재고 총 세트 수, 최소 카드 수, 드롭 허용 하한치, 그리고 개별 계정당 봇별 할당 하한치.\n교차 확인\n공유된 봇 21개\tsteamlvlup.net/cardbots ↗ 보관됨 2026-02-10 ↗, 동일한 봇들을 모아놓은 독립적인 디렉토리\t확인용입니다. 두 목록에 모두 포함된 21개의 봇에 대해, Aggregate Stock은 다음 사항에 동의합니다. 0.03%; 단일 봇 간 가장 큰 불일치 값은 1.36%이며, 이는 단 몇 분 간격으로 수행된 두 차례의 실시간 재고 수집 결과와 일치한다.\n\n두 번째 디렉토리에서 요구하는 바와 같이 출처 표기: 데이터 제공: SteamLvlUp, 다음 라이선스에 따라 배포됩니다. CC BY 4.0 보관됨 2026-09-23 ↗; 여기서는 제3자의 재고 수치를 독립적으로 확인하기 위한 목적으로만 사용되었으며, 봇당 행의 데이터를 그대로 재현하는 대신 집계하여 비교하는 방식으로 수정되었습니다. Steam Card Exchange와 steam.supply는 상단의 링크를 통해 출처를 명시했습니다. 게임 가격은 Valve이 직접 책정한 것입니다. 카드, 게임, 세트 이름 및 이미지는 Valve 또는 출판사의 소유이며, 시장 현황에 대한 사실로서 어떠한 권리 주장이나 라이선스 없이 재현되었습니다.\n\n두 가지 측정 항목은 수행되지 않았으며, 이를 대체할 수 있는 항목도 없습니다. Steam의 자체 커뮤니티 마켓 종점 — 가격 개요, 검색/표시, 가격 내역 — 수집 호스트에는 아무것도 반환하지 않으며, Steam 커뮤니티 토론 페이지에서는 해당 호스트에 HTTP 403을 반환하므로, 이 페이지의 수치는 실시간 마켓 데이터에서 파생된 것이 아닙니다. 일일 리셋 시 카드 드롭 횟수를 집계했을 판매량 측정 방식은 로그인된 Steam 세션이 필요합니다; 이번 조사의 조사 보고서에 따르면 마켓플레이스 인증 정보가 사용되지 않았다고 명시되어 있으며, 해당 진술은 그대로 유지되었다. 봇-스톡 플로어란 봇 없이 측정할 수 있는 부분을 말합니다.\n\n1차 자료\n\nSteam 가입자 계약서 ↗ 보관됨 2026-09-24 ↗ — 제2.A조, 제2.G조, 제3.D조, 제4.C조, 제4.D조.\nSteam 지원 — 제한된 사용자 계정 ↗ — $5.00 임계값과 제한된 기능 목록.\nValve — Steam 트레이딩 카드 자주 묻는 질문 ↗ — 드롭 메커니즘과 $9 무료 플레이 비율.\nArchiSteamFarm 자주 묻는 질문 ↗ 그리고 토론 #3440 ↗.\nSteam 커뮤니티 그룹 및 프로필 페이지, 섹션 08을 직접 참조하십시오.\nsteamid.uk FAQ, 인터넷 아카이브 스냅샷 2026-04-01 ↗.\n2020년부터 2026년까지 수신자가 게시한 8건의 Steam 지원 잠금 공지사항은 섹션 06에 링크와 함께 나열되어 있습니다.\n\n주장하지 않는 사항\n\nValve의 카드 파밍으로 인한 수익 추정치는 없습니다. 어떤 도구에 대해서도 활성 계정 수가 명시되지 않았으며, 139만 건의 드롭 허용량은 아니다 농장 소유 계정의 수 — 02항의 주석을 참조하십시오. 어떤 개인도 위법 행위로 고발된 바 없으며, 특정 인물의 이름이 언급된 경우 이는 해당 인물이 Valve이 게시한 페이지에서 자신의 공개 Steam 닉네임과 공식 직책을 통해 표기된 것입니다. 06절에 언급된 8개의 잠긴 계정 중 어느 것도 무죄나 유죄로 단정되지 않습니다. 이 판단은 해당 계정이 아닌 글 자체에 관한 것입니다. 02절에 기재된 운영자 손실 수치는 제1자 보고 자료이며, 해당 자료에는 다음과 같이 명시되어 있습니다. 조달 참고 사항. steamid.uk의 FAQ는 해당 페이지가 봇 인증 절차를 거쳐야만 접근할 수 있기 때문에 인터넷 아카이브의 스냅샷에서 인용되었습니다. 어떠한 차단 현황 조사도 시도되었다가 은폐되었다는 주장은 하지 않으며, 단지 그러한 조사가 공개된 바가 없다는 사실만을 지적한 것입니다. 667을 초과하는 Steam 레벨 곡선은 모델링되지 않았습니다.\n\n왜 도구가 주체가 아닌가\n\nArchiSteamFarm은 다음과 같이 명시하고 있다. \"Valve의 승인을 받지 않았습니다\" 그리고 이 페이지에서는 그에 대해 어떠한 비난도 제기되지 않습니다. 이 경제 체제 내에서 메커니즘을 공개적으로, 서면으로 기록하는 유일한 주체이기 때문에 측정 도구로 활용됩니다. Valve는 단 한 문단으로 이 모든 논증을 종결시킬 수 있습니다. 즉, 어떤 상업적 자동화를 승인했는지, 그리고 나머지 사항에 대해 운영자별로 어떤 조치를 취했는지에 대한 기록을 공개하기만 하면 됩니다.\n\n다음 기사: 시장 자체의 가격 결정 방식 → · 가격 단계와 상장 한도 → · Steam번 품목은 배송되지 않습니다 →",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "봇 팜은 Valve의 상점에 생긴 누수가 아닙니다. 그것은 고객."
          },
          {
            "level": 2,
            "id": null,
            "text": "농장이 실제로 무엇인지, 단계별로 알아보기"
          },
          {
            "level": 3,
            "id": null,
            "text": "매수"
          },
          {
            "level": 3,
            "id": null,
            "text": "게임 구매하기"
          },
          {
            "level": 3,
            "id": null,
            "text": "유휴\n이 도구는 계정을 Steam 네트워크에 헤드리스 모드로 로그인하며, \"배지를 분석합니다\", 획득 가능한 타이틀 목록을 생성하고 시작합니다 \"해당 게임을 플레이하면서, 게임 내 아이템을 이미 모두 모았는지 주기적으로 확인한다.\" 이 메커니즘에 대한 유지보수자의 설명: 그것은 \"그저 Steam에게 우리가 특정 게임을 하고 있다고 알리는 것 외에는 아무것도 하지 않는다.\""
          },
          {
            "level": 3,
            "id": null,
            "text": "방울이 다 떨어졌다\n각 제목은 유한합니다. \"모든 게임에는 카드 드랍 수량이 정해져 있습니다. 이 수량을 모두 획득하면(전체 세트의 약 절반 정도), 해당 게임은 더 이상 파밍 대상으로 삼을 가치가 없습니다.\" 계속 생산을 이어가려는 농장은 지속적으로 타이틀을 구매해야 합니다. 카드 공급량은 구매량에 따라 제한되는데, 이는 의도된 설계이며 Valve에게 유리한 구조입니다."
          },
          {
            "level": 3,
            "id": null,
            "text": "현금 인출\n이 카드는 세 가지 경로 중 하나를 통해 처리됩니다: 커뮤니티 마켓에서 판매되거나, 다른 플레이어와 교환되거나, 보석으로 분쇄되는 것입니다. 이 모든 경우 구독형 마켓플레이스 거래나 교환에 해당하며, § 3.D에는 이에 대한 요금이 명시되어 있습니다: \"Valve는 구독 마켓플레이스 내 거래에 대해 수수료를 부과할 수 있습니다.\" 이 단계가 바로 전체 과정을 규정 위반으로 만드는 단계입니다 — 참조: 05."
          },
          {
            "level": 2,
            "id": null,
            "text": "농장이 1센트라도 벌기 전에 이미 Valve을 지불한 상태다."
          },
          {
            "level": 3,
            "id": null,
            "text": "구매하려는 물건의 실제 크기는 어느 정도인가"
          },
          {
            "level": 3,
            "id": null,
            "text": "그 집합은 어느 정도 크나요?"
          },
          {
            "level": 3,
            "id": null,
            "text": "라이선스 비용은 얼마인가요?"
          },
          {
            "level": 3,
            "id": null,
            "text": "완성된 세트가 반환하는 내용"
          },
          {
            "level": 3,
            "id": null,
            "text": "694,673 세트가 놓여 있는 곳"
          },
          {
            "level": 3,
            "id": null,
            "text": "이 바닥이 말해주는 것과 말해주지 않는 것"
          },
          {
            "level": 3,
            "id": null,
            "text": "게다가 Valve의 가격으로는 농업으로 비용을 감당할 수 없다"
          },
          {
            "level": 3,
            "id": null,
            "text": "농장이 실제로 지탱하고 있는 것은 무엇인가"
          },
          {
            "level": 4,
            "id": null,
            "text": "게임 판매량"
          },
          {
            "level": 4,
            "id": null,
            "text": "\"온라인\" & 놀이 시간"
          },
          {
            "level": 4,
            "id": null,
            "text": "등록"
          },
          {
            "level": 4,
            "id": null,
            "text": "지갑 잔액 및 수수료"
          },
          {
            "level": 4,
            "id": null,
            "text": "Steam단계 PR"
          },
          {
            "level": 3,
            "id": null,
            "text": "그리고 현금 인출 자체만으로도 가치가 감소하는 요인입니다 Valve 두 번의 세금이 부과되기 때문입니다"
          },
          {
            "level": 3,
            "id": null,
            "text": "이는 단순한 순간이 아닙니다. 수년에 걸쳐 다져진 기반을 가진 산업입니다."
          },
          {
            "level": 3,
            "id": null,
            "text": "공개 봇 디렉토리에 보관된 완전한 카드 세트, Steam 판매 기준"
          },
          {
            "level": 3,
            "id": null,
            "text": "한 판매자의 배지 순위표가 최상위권에서는 어떻게 보이는지"
          },
          {
            "level": 3,
            "id": null,
            "text": "그리고 세일이 진행되지 않을 때도 그 함대는 여전히 그곳에 있습니다"
          },
          {
            "level": 3,
            "id": null,
            "text": "봇별 기본 디렉터리"
          },
          {
            "level": 2,
            "id": null,
            "text": "다른 항목은 이름 옆에 있는 숫자입니다."
          },
          {
            "level": 3,
            "id": null,
            "text": "소모된 세트 수, 레벨 1 ~ 1,000"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve가 이를 공개하지 않았기 때문에, 곡선이 어떻게 검증되었는지"
          },
          {
            "level": 2,
            "id": null,
            "text": "이 조항은 농업을 막연하게 설명하는 것이 아니라, 구체적으로 열거하고 있다."
          },
          {
            "level": 3,
            "id": null,
            "text": "\"…놀이 시간\""
          },
          {
            "level": 3,
            "id": null,
            "text": "\"…사용자의 진정한 의견이 반영되지 않은 채\""
          },
          {
            "level": 2,
            "id": null,
            "text": "농장형 카드에서 이루어지는 모든 출구는 라이선스에서 금지하는 출구이며, Valve은 입구에서 요금을 부과합니다."
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 2.A — 라이선스"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 2.G — 제한 사항"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 3.D — 수수료"
          },
          {
            "level": 3,
            "id": null,
            "text": "이 세 가지를 종합해 보면 그 직책은 마감됩니다."
          },
          {
            "level": 3,
            "id": "fee-ladder",
            "text": "그 입구의 요금은 15%이 아닙니다. 파밍된 카드에서는 요금이 3분의 2에 달합니다."
          },
          {
            "level": 3,
            "id": null,
            "text": "커뮤니티 마켓 판매 시, 판매자의 매도 희망 가격 기준 실효 수수료"
          },
          {
            "level": 2,
            "id": null,
            "text": "사전 공지 없이, 물결치듯, 전화번호를 따라 퍼져 나갑니다"
          },
          {
            "level": 3,
            "id": null,
            "text": "사례 4 — 2025년 6월, 가동 중단된 CS2에 대한 금지 조치"
          },
          {
            "level": 3,
            "id": null,
            "text": "메인 계정이 사라지는 과정"
          },
          {
            "level": 3,
            "id": null,
            "text": "5년 간격으로 세 명의 다른 에이전트가 작성한 동일한 문단"
          },
          {
            "level": 3,
            "id": null,
            "text": "조달 관련 참고 사항 — 운영자 차원의 손실"
          },
          {
            "level": 2,
            "id": null,
            "text": "같은 책상의 양쪽"
          },
          {
            "level": 3,
            "id": null,
            "text": "거래를 위한 고객"
          },
          {
            "level": 3,
            "id": null,
            "text": "대량 처리를 위한 자동화된 봇 군단"
          },
          {
            "level": 3,
            "id": null,
            "text": "이를 통해 제기되는 질문은, 간단히 말해"
          },
          {
            "level": 2,
            "id": null,
            "text": "카드 경제를 누가 조절하는가"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve명의 직원이 최대 규모의 카드 거래 그룹을 운영하고 있다 Valve명 직원"
          },
          {
            "level": 3,
            "id": null,
            "text": "차단 목록 계층 및 이를 관리하는 주체 자원봉사 운영자 제3자 서비스"
          },
          {
            "level": 3,
            "id": null,
            "text": "이 모든 것이 결국 무엇을 의미하는지, 그리고 무엇을 의미하지 않는지"
          },
          {
            "level": 3,
            "id": null,
            "text": "아무도 집계하지 않는다. 이것이 조사 결과다."
          },
          {
            "level": 3,
            "id": null,
            "text": "1,088만 계정 조사: 88.97% 미조사"
          },
          {
            "level": 3,
            "id": null,
            "text": "법의학적 증거 및 심층 인구조사"
          },
          {
            "level": 2,
            "id": null,
            "text": "무엇이 읽혔는지, 그리고 무엇이 주장되지 않았는지"
          },
          {
            "level": 3,
            "id": null,
            "text": "네 가지 데이터셋과 이를 대상으로 한 연산"
          },
          {
            "level": 3,
            "id": null,
            "text": "1차 자료"
          },
          {
            "level": 3,
            "id": null,
            "text": "주장하지 않는 사항"
          },
          {
            "level": 3,
            "id": null,
            "text": "왜 도구가 주체가 아닌가"
          }
        ],
        "links": [
          "https://help.steampowered.com/en/faqs/view/71D3-35C2-AD96-AA3A",
          "https://github.com/JustArchiNET/ArchiSteamFarm/wiki/FAQ",
          "https://steamcommunity.com/tradingcards/faq/",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260924114457/https://store.steampowered.com/subscriber_agreement/",
          "https://steamladder.com/ladder/badges/2861690/",
          "http://web.archive.org/web/20260716205303/https://steamladder.com/ladder/badges/2861690/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/farm-economy-timeline.json",
          "https://store.steampowered.com/charts/",
          "http://web.archive.org/web/20260923183013/https://store.steampowered.com/charts/",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://github.com/JustArchiNET/ArchiSteamFarm/discussions/3440",
          "https://x.com/gergelyszabo94/status/1311004678633795585",
          "https://x.com/prcs25/status/1811893857253982720",
          "http://web.archive.org/web/20240715122902/https://x.com/prcs25/status/1811893857253982720",
          "https://reddit.com/r/steamsupport/comments/1fjmgc5/what_to_do_when_your_steam_account_gets_hacked/mkelm2y/",
          "https://www.reddit.com/r/csgomarketforum/comments/r87owv/psa_my_steam_account_just_got_banned/",
          "http://web.archive.org/web/20250327203008/https://www.reddit.com/r/csgomarketforum/comments/r87owv/psa_my_steam_account_just_got_banned/",
          "https://www.reddit.com/r/GlobalOffensiveTrade/comments/r9xql9/d_recently_received_commercial_ban_for_what_seems/",
          "http://web.archive.org/web/20211206034804/https://www.reddit.com/r/GlobalOffensiveTrade/comments/r9xql9/d_recently_received_commercial_ban_for_what_seems/",
          "https://www.reddit.com/r/csgomarketforum/comments/1hhxx7m/d_permanently_locked_on_steam_for_commercial_use/",
          "http://web.archive.org/web/20250627014045/https://www.reddit.com/r/csgomarketforum/comments/1hhxx7m/d_permanently_locked_on_steam_for_commercial_use/",
          "https://www.reddit.com/r/steamsupport/comments/1hkctwt/permanent_ban_with_no_explanation/",
          "https://www.reddit.com/r/pcgaming/comments/1vf24lu/warning_to_all_gamersexpats_steam_took_my_money/",
          "https://steamcommunity.com/groups/card-trading-card-trades",
          "https://steamcommunity.com/id/afarnsworth",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/groups/steambans",
          "https://steamcommunity.com/groups/steambans",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/id/killahinstinct_",
          "https://web.archive.org/web/20240914124859/https://steamcommunity.com/id/msart",
          "https://steamcommunity.com/id/msart/groups/",
          "http://web.archive.org/web/20260401154714/https://steamid.uk/faq/",
          "https://phishdestroy.io/steam_dossier/ko/enforcement_audit.html",
          "https://phishdestroy.io/steam_dossier/ko/#evidence-blackout",
          "https://www.steamcardexchange.net/index.php?badgeprices",
          "http://web.archive.org/web/20260804200309/https://www.steamcardexchange.net/index.php?badgeprices",
          "https://steam.supply/CardBots",
          "https://steamlvlup.net/cardbots",
          "http://web.archive.org/web/20260210171205/https://steamlvlup.net/cardbots",
          "https://steamlvlup.net/",
          "https://creativecommons.org/licenses/by/4.0/",
          "http://web.archive.org/web/20260923221628/https://creativecommons.org/licenses/by/4.0/",
          "https://phishdestroy.io/steam_dossier/ko/market_economics.html",
          "https://phishdestroy.io/steam_dossier/ko/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/ko/elite_skins.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ko/card_economy.content.json",
      "export_json_sha256": "82fbde6639db6a0d78a2fc4cd8a589f4abbeb53e2e48512f44e38ba9e640ae31"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ko/elite_skins.html",
      "language": "ko",
      "title": "하나의 상품, 두 가지 가격 체계 — ‘Steam’ 특집",
      "source_url": "https://phishdestroy.io/steam_dossier/ko/elite_skins",
      "source_html_sha256": "015e56216cc53ed715640aace3a06e60f389cecd895e228c1ed92d91f97cbe91",
      "exported_at": "2026-09-29T00:21:50.896Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "register",
            "source": "https://phishdestroy.io/steam_dossier/ko/elite_skins#register"
          },
          {
            "id": "",
            "source": "https://phishdestroy.io/steam_dossier/ko/elite_skins#selected"
          }
        ],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "elite_skins.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ko/elite_skins.pdf?v=print-20260929-v5",
        "sha256": "2e1ebc4792c0e1955a01355c828b728caca50a72e36afbbbf0281b16fce95bba",
        "bytes": 98730,
        "pages": 6
      },
      "integrity": {
        "signed_object": "elite_skins.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "elite_skins.content.json.asc",
        "digest_file": "elite_skins.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify elite_skins.content.json.asc elite_skins.content.json",
          "sha256sum -c elite_skins.content.json.sha256"
        ]
      },
      "content": {
        "text": "부록 IV / 시장 구조 / 20 9월 2026\n엘리트 스킨스 등록 — $1,800의 시장 상한선\n\n한 가지입니다. 두 가지 가격 체계.\n\n이 섹션이 입증하는 바\n\n이 명부는 5개 외부 거래소에서 ‘Steam’의 $1,800 커뮤니티 마켓 등록 상한선을 초과하는 가격의 모든 CS2 스킨 카테고리에 대한 실증적 조사 결과를 담고 있습니다. 이 명부는 248에서 확인된 고가 카테고리들—18,394의 활성 등록 건수와 $78.6 million의 게시 유동성을 나타내는—이 100% Valve의 공식 마켓플레이스에서는 찾아볼 수 없음을 입증합니다. 진정한 시장 가격을 추구하는 판매자들은 구조적으로 외부 플랫폼으로 내몰리는 한편, Steam의 기본 거래 메커니즘에만 전적으로 의존할 수밖에 없습니다.\n\nWhat this means — the Community Market listing ceiling\n\nSteam’s own market refuses a listing above roughly $1,800. A seller may ask less, never more. Items whose market price sits above that line therefore cannot be sold at that price on Steam at all — which is the mechanism that moves those sales to third-party venues while the item itself never leaves Valve’s inventory system.\n\nSection 13 — the off-Steam price gap →\n\n← 경영진 브리핑으로 돌아가기\n\nSteam 커뮤니티 마켓의 상품 가격 상한선은 약 $1,800.로 책정되어 있습니다. 이 스냅샷에서 가격이 표시된 5개의 제3자 마켓플레이스를 통틀어, 419 CS2 아이템 카테고리 중 일부는 해당 한도보다 높은 최저 실시간 매도가를 보이고 있으며, 402에 등재된 95.9%,의 경우 Steam에 아예 목록이 등록되어 있지 않습니다. 이들은 합쳐서 최소 $82.4백만 상당의 ‘18,641’ 등재 사본을 보유하고 있습니다. 가격이 유효하려면 제2의 거래처가 이에 동의해야 하며, 248 이러한 범주 중 확인된 것들 — 그리고 그 모든 범주에서, ‘100%,’는 ‘Steam’에 포함되어 있지 않습니다. 'The dearest' 스티커 | 타이탄 (홀로) | 카토비체 2014에서 $66,285, 5.2% 내의 네 개 마켓플레이스에서 호가가 제시되었으나, Valve에 속한 마켓플레이스 중 어느 곳에서도 거래되지 않았습니다. 전체 순위표, 렌더링 이미지 및 등급 평가는 가격 사다리 아틀라스.\n\n419의 모든 항목을 확인하세요 ↓아틀라스 열기 ↗메서드 내용 읽어보기\n248상한선을 초과하는 가격이 두 개 이상의 마켓플레이스에 등재된 상품\n18,3945개 마켓플레이스에 등록된 상품 수\n$78.6M해당 매물의 최저가\n100%그들 중 일부는 Steam에서 아예 찾아볼 수 없다\n\n정정 · 이 페이지에는 이전에 확인되지 않은 가격이 첫머리에 기재되어 있었습니다.\n\n이 페이지의 이전 버전에는 ‘Souvenir AK-47 | Point Disarray’라는 제목의 상품이 한 마켓플레이스에서 $148,954에 매물로 올라와 있는 반면, Steam에서는 $119.에 책정되어 있었다. 해당 상품은 단 하나의 선반에 단 한 점만 진열되어 있으며, 이를 확인해주는 다른 마켓플레이스가 없기 때문에 이는 실제 가격이 아닌 호가일 뿐이며, 현재 해당 페이지에는 더 이상 표시되지 않는다. 여기에 제시된 모든 주요 수치는 이제 최소 두 곳의 마켓플레이스에서 독립적으로 상한선 이상의 가격을 책정한 248 카테고리로만 제한됩니다. 해당 행 자체는 삭제되지 않았으며, 아래 목록에 여전히 포함되어 있고, 등급을 하향 조정한 근거는 가격 사다리 아틀라스.\n\n01 / 매수 호가에 있는 자금\n측정 가능한 달러 최저치\n\n5개 마켓플레이스에 걸쳐 라이선스가 부여된 ‘cs2.sh’ 스냅샷을 바탕으로 재계산한 수치입니다. 이는 정의된 하위 집합 내의 최소 총 호가 금액이며, 판매 매출액이나 CS2 경제의 가치 평가가 아닙니다.\n\n248 검증된 카테고리 · 18,394 등재된 사본 · 5 마켓플레이스$78.62M\n\n두 개 이상의 마켓플레이스가 자체 시장에서 ‘Valve’이 허용하는 한도를 초과하는 가격을 독립적으로 책정한 모든 CS2 품목에 대해, 해당 품목의 최소 총 호가 금액.\n\n왜 이것이 추정치가 아니라 확정치인지\n\n각 마켓플레이스에 대해 해당 마켓플레이스의 가장 낮은 해당 마켓플레이스에 표시된 판매 수량만큼 상품을 요청해 보세요. 해당 진열대에 있는 나머지 모든 상품은 최저 판매가 이상으로 가격이 책정되어 있으므로, 실제 게시된 가치는 더 높습니다. 이는 추측이 아니라 구조상 당연한 결과입니다. 이는 판매, 현금 흐름 또는 시장 전반의 가치 평가가 아니며, 동일한 실물 상품이 여러 마켓플레이스에 동시에 등록될 수 있습니다.\n\n419의 모든 소스 행 확인 ↗\n★ 스포츠 장갑 | 헤지 메이즈 (실전 테스트 완료)\n$4.68M\nAWP | 군니르 (신품)\n$4.46M\nAWP | 드래곤 로어 (신품)\n$4.34M\n★ 버터플라이 나이프 | 페이드 (공장 출고 신품)\n$4.17M\nAK-47 | Wild Lotus (공장 출고 상태)\n$4.16M\n★ 버터플라이 나이프 | 도플러 (공장 출고 신품)\n$3.64M\n\n막대는 최저가 산정 시 가장 큰 비중을 차지한 6개 카테고리별 기여도를 나타내며, 가장 큰 비중을 기준으로 비율이 조정되어 표시됩니다. 막대가 높을수록 가장 저렴한 매도 호가와 등록된 수량이 모두 많음을 의미합니다. 동일한 실물 상품이 여러 마켓플레이스에 등록될 수 있으므로, 이 수치를 다른 마켓의 총합에 더해서는 안 됩니다.\n\n02 / 검토 가능한 예시\n한계가 간과하는 점\n\n삽화는 가능한 경우 정확한 상품명과 일치합니다. 가격은 거래 기록이 아닌, 해당 날짜의 카탈로그에 기재된 현재 매도 희망가입니다.\n\n★ Butterfly Knife | Doppler (Factory New)\n\n출처: https://phishdestroy.io/steam_dossier/ko/elite_skins#selected\n\n측정 가능한 격차: Steam에 등록된 동일 금액(USD)의 매물로는 이러한 제안과 맞설 수 없습니다. Valve 자체의 커뮤니티 마켓 자주 묻는 질문 보관됨 2026-09-21 ↗ 최대 매물 가격을 약 $1,800로 명시하고 있습니다. 판매자는 이 금액보다 낮은 가격으로 매물을 등록할 수도 있지만, 그 가격이 허용될지는 판매자의 선택에 달려 있습니다. 별도의 CSMarketCap에서 $1,800 이상의 항목을 검색하기 ↗ 28의 색인화된 시장 전반에 걸쳐 ‘Factory New Dragon Lore’ 상품에 대한 약 1.1K 건의 노출된 오퍼를 보여줍니다. 중복된 재고는 여러 번 집계될 수 있습니다.\n\n03 / 구조적 의존성\nSteam의 상한선 설정으로 인해 가격 발견 기능이 Steam 밖으로 밀려났다\n\n이 비교는 구조적인 것입니다. 모든 매도 희망 가격이 공정하다고 가정하지도 않으며, 미판매 매물을 매출로 간주하지도 않습니다.\n\n01 · 규칙\nSteam 목록을 마무리합니다\n\nValve 커뮤니티 마켓의 등록 건수는 대략 $1,800. 지갑 잔액에도 상한선이 있으며, 지갑 내 자금은 현금으로 인출할 수 없습니다.\n\n02 · 관찰\nDragon Lore: $10,940.85\n\n5-마켓플레이스 카탈로그에는 다음과 같이 나와 있습니다. 389 실시간 특가 AWP Dragon Lore (Factory New)의 경우, $10,940.85부터 시작합니다(CSFloat 층). 더 광범위한 등록부에는 Steam의 한도를 초과하는, 248에서 확인된 카테고리들이 포함되어 있습니다.\n\n03 · 결과\n가격 및 이적 분배\n\n더 높은 가격을 원하는 판매자 Steam에 게시할 수 없습니다.. 외부 서비스에서 현금 가격을 설정할 수는 있지만, 배송 과정에서는 여전히 Steam에서 관리하는 상품 소유권 및 양도 방식이 적용됩니다.\n\n정책의 모순: Valve의 자체 제작 가입자 계약서 보관됨 2026-09-21 ↗ Steam 서비스의 상업적 이용은 명시적으로 허용된 경우를 제외하고는 제한하며, 한편 해당 서비스는 2016 성명 보관됨 2026-09-21 ↗ 해당 도박 사업자들은 이미 Steam의 OpenID와 자동 생성 계정을 사용하고 있었다고 한다. 이는 Valve가 2016.에 있는 이러한 유형의 외부 사업자의 존재를 알고 있었다는 직접적인 증거이다. 그러나 공식 마켓플레이스에서는 이러한 고가 품목의 실제 거래 가격을 게시할 수 없다. 이는 오프Steam의 가격 형성 및 거래에 대한 아키텍처적 의존성을 의미합니다; 각 마켓플레이스의 계약 현황을 확인하려면 별도의 증거가 필요합니다. 이러한 과잉 거래량을 차지하는 두 개의 주요 서구 마켓플레이스는 주요 관할권에서 정식 법인으로서 운영되고 있습니다 — CSFloat Inc. (미국 델라웨어주에서 설립) 및 Skinport GmbH (독일 슈투트가르트 등록, HRB 764879) — Steam의 웹 API 및 거래 인프라를 직접 활용하여 수억 단위의 P2P 상품 거래를 공개적으로 진행하고 있습니다.\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\n100,000의 4개 행은 CSFloat의 자체 최고 매물 가격에 해당합니다. 이 항목들은 등록부에 표시되어 있으며, 감정가로 해석되어서는 안 됩니다. 보관된 CSFloat 매물 크롤링 데이터는 약6,999,까지만 수집되었으므로, 전체 >$1,800 등록 내역을 확인하기 위해 공개 카탈로그 스냅샷이 사용됩니다.\n\n04 / 또 다른 ‘Valve’ 게임\n천장도 도타를 잡아낸다 2\n\nSkinport에서 동일한 엄격한 ‘최저가 기준’ 테스트를 적용한 결과, 166의 CS2 카테고리와 3의 Dota 2 카테고리가 확인되었습니다. 이들은 별도의 마켓플레이스 스냅샷이므로, CSFloat의 245.에 추가하지 마십시오.\n\nDOTA 2 · 1 프로모션\n영웅적 잔혹한 초승달\n\nSkinport의 최저가 문의: $14,622.25.\n\nDOTA 2 · 1 프로모션\n다크 아트리스티 케이프\n\nSkinport의 최저가 문의: $8,255.16.\n\nDOTA 2 · 1 프로모션\n타락한 파워드 스타\n\nSkinport의 최저가 문의: $2,087.92.\n\n이것들은 나열된 세 가지 아이템 카테고리일 뿐, 존재하는 모든 도타 2 아이템을 다 포함하는 것은 아닙니다. 날짜가 표시된 ‘Skinport’ 행을 확인하세요 ↗ 그리고 API 문서 ↗.\n\n05 / 견고성\n이 결과는 정확한 상한선에 좌우되지 않는다\n\nValve 상한선을 구매자의 지역 통화로 설정하기 때문에, 이를 미국 달러로 환산하면 딱 떨어지는 숫자가 나오지 않습니다. 따라서 모든 타당한 기준치에서 재조사를 실시합니다. Steam에서 누락된 이러한 항목의 비율은 95%.보다 낮아진 적이 없습니다.\n\n임계값 테스트 완료\t상품 카테고리\t등재된 사본\t최소값\tSteam에 불참\n$1,800\t419\t18,641\t$82,449,526\t95.9%\n$2,000\t382\t15,159\t$75,541,325\t95.5%\n$2,070\t363\t12,336\t$69,560,305\t95.6%\n$2,300\t323\t11,644\t$67,984,432\t95.0%\n$2,500\t299\t10,950\t$66,203,929\t95.0%\n\n한 번에 한 행씩 읽어보세요. 각 행은 별도의 모집단이 아니라 동일한 인구조사 내의 중첩된 부분집합입니다. “최저값”은 각 마켓플레이스의 가장 낮은 나열된 부수만큼만 집계하기 때문에, 구조상 재고 수량이 실제보다 적게 나타납니다. 데이터셋 열기 ↗\n\n06 / 셀 수 있을 만큼 부족한 것\n이 중 실제로 판매되고 있는 것은 정말 드물다\n\nBUFF는 각 아이템의 진열대를 플로트 브래킷으로 나누고, 각 브래킷에 몇 개가 진열되어 있는지 공개합니다. 이를 통해 ‘희귀’라는 단어가 단순한 표현이 아닌 구체적인 수치로 바뀌게 되며, 아이템의 상태와 스킨을 별도로 가격을 책정할 수 있게 됩니다.\n\n298 등재된 사본\nAWP | 드래곤의 전설\n\n8 가격이 책정된 여러 가지 변형 모델. 그중 가장 비싼 모델은, 기념품 AWP | 드래곤 로어 (공장 출고 상태), 묻는다 $12,363 20권이 진열대에 놓여 있습니다.\n\n선반에 있는 최고의 플로트 브라켓(0–0.01)에는 2 사본, 묻기를 $17,875 — 해당 상품의 상태만 고려했을 때의 기본 호가보다 a +45%만큼 높은 프리미엄.\n\n607 등재된 사본\nM4A4 | 하울\n\n12 가격이 책정된 여러 가지 변형 모델. 그중 가장 비싼 모델은, 기념품 M4A4 | 하울 (공장 출고 상태), 묻는다 $14,895 2권이 진열대에 놓여 있습니다.\n\n213 등재된 사본\nAK-47 | 와일드 로터스\n\n7 가격이 책정된 여러 가지 변형 모델. 그중 가장 비싼 모델은, 기념품 AK-47 | Wild Lotus (공장 출고 상태), 묻는다 $14,895 2권이 진열대에 놓여 있습니다.\n\n310 등재된 사본\nAWP | 군니르\n\n7 가격이 책정된 여러 가지 변형 모델. 그중 가장 비싼 모델은, 기념품 AWP | 군니르 (마모 흔적 거의 없음), 묻는다 $14,895 2권이 진열대에 놓여 있습니다.\n\n이 내용이 본 보고서의 나머지 부분과 어떤 관련이 있는지: 이는 추상적인 개념이 아닙니다. 전 세계 공개 선반에는 각 트로피가 수백 개씩 존재하며, 각각은 하나의 Steam 계정에 연결되어 있고 하나의 Steam 거래를 통해 이동됩니다. 이처럼 거래량이 극히 적은 시장에서는 도난당한 재고 한 건만으로도 측정 가능한 사건이 되며, 본 조사 보고서 다른 부분에서 기록된 계정 탈취 기법들이 직접적이고 정량화 가능한 성과를 거두게 됩니다.\n\n수량은 수집 시점 기준 특정 마켓플레이스에 등록된 실시간 목록 수를 의미하며, 전체 존재 수량을 나타내는 것이 아닙니다. 비공개 재고에 보관된 상품은 여기 어디에도 집계되지 않습니다. 플로트 데이터셋 열기 ↗\n\n07 / 사다리가 보이지 않는다\n물건의 가격이 비쌀수록, 눈에 띄는 장소에서 더 멀리 떨어져 있다\n\n아래의 각 단계는 서로 다른 증거 범주를 나타냅니다. 이 범주들은 의도적으로 하나의 수치로 통합되지 않았습니다.\n\nRung\t그림\t이게 도대체 어떤 사실인가요?\nCeiling on Valve's own market\t~$1,800\tPublished rule, stated in the Steam Community Market FAQ.\nDearest ask several marketplaces agree on\t$66,285\tMeasured by us in this snapshot. Sticker | Titan (Holo) | Katowice 2014, quoted by four marketplaces within 5.2% of one another. An ask, not a sale.\nDearest ask seen on any single shelf\t$148,954\tOne marketplace, one copy, no second marketplace agreeing — and equal to a round CNY 1,000,000 at the snapshot rate. Listed here as the outer edge of what sellers ask, and relied on for nothing.\nPublic marketplace sale\t$49,999\tSpecialist Gloves | Crimson Kimono (FN) on CSFloat, as reported by SteamAnalyst. Platform-recorded, third-party reported.\nReported private sale\t$400,000\tAK-47 | Case Hardened, reported by PC Gamer in April 2023. Journalism, not a record we hold.\nReported offer, declined\t$1,500,000\tBlue Gem Karambit, pattern #387. No sale took place and the figure has not been independently confirmed. Included to mark the ceiling of the claims, not to assert a value.\n\n구조적 요점: Valve의 시장 가격은 약 $1,800. 수준에서 멈춥니다. 제3자 마켓플레이스를 통해 거래가 약 $66,000 수준까지 이어지며, 이 가격대에서는 여러 마켓플레이스가 가격에 동의하고, 약 $150,000 수준에서는 단 한 곳만이 동의합니다. 그 이상 가격대에는 거래소가 전혀 없습니다. Valve에서 발행된 자산의 대규모 양도는 상장도, 플랫폼 기록도, 신원 확인도, 보고도 없이 개인 간 비공개로 이루어집니다. 양도 자체는 여전히 Steam에서 처리됩니다. 값이 높을수록 다른 사람이 볼 수 있는 범위는 줄어들며, 이를 전달하는 인프라 전반에 걸쳐 Valve가 사용됩니다.\n\n마지막 두 항목은 출처를 명시하여 인용한 타인의 보도 내용입니다. 본 프로젝트는 해당 내용을 검증하지 않았으며, 어떠한 결론을 도출하는 데에도 이를 근거로 삼지 않습니다.\n\n419에서 관찰된 모든 범주\n\n출처: https://phishdestroy.io/steam_dossier/ko/elite_skins#register\n\n09 / 출처와 한계\n계산 결과를 확인해 보세요\n\n당사는 로컬 데이터와 공개 소스를 공개합니다. 수치 헤드라인은 캡처 날짜 기준 CSFloat에 한정됩니다.\n\nValve만의 상한선과 조건\n\nSteam 커뮤니티 마켓 자주 묻는 질문 ↗ 보관됨 2026-09-21 ↗ 대략적인 $1,800의 상한선을 명시하고 있습니다. 이 가입자 약관 ↗ 보관됨 2026-09-21 ↗ 상업적 이용에 대한 제한 사항을 정합니다.\n\n가격은 어디서 나오는가\n\n가격, 상장 종목 수 및 유통 주식 수 범위는 다음에서 인용한 것입니다. cs2.sh 유료 상업용 구독을 통해 라이선스 키를 사용하여 API의 시장 데이터를 이용하십시오. 어떤 마켓플레이스도 스크래핑되지 않았으며, 마켓플레이스 계정이나 인증 정보도 사용되지 않았습니다. 이 제공업체는 BUFF, Youpin, CSFloat, Skinport, C5Game 및 Steam 커뮤니티 마켓의 데이터를 통합하며, 모든 수치는 보고된 대로 미국 달러(USD)로 표시됩니다. 출처 정보 매니페스트 열기 ↗ — 이 문서는 원본 스냅샷의 정확한 시작점, 종료점, 캡처 시간 및 SHA-256 해시 값을 기록하고 있으므로, 자체 키를 보유한 제3자 독자라면 동일한 데이터를 추출하여 이 페이지에 나와 있는 모든 수치를 다시 계산할 수 있습니다.\n\n우리가 얻지 못한 것\n\n구매한 구독은 현재 스냅샷에만 적용됩니다. 과거 및 아카이브 엔드포인트는 저희가 이용할 수 없었으며, 이 페이지에서는 어떠한 추세, 과거 가격 또는 시간 경과에 따른 변화에 대해서도 어떠한 주장도 하지 않습니다. 이곳의 모든 것은 날짜가 적힌 단 한 순간입니다.\n\n이전 ‘CSFloat’ 레지스터\n\n이 전시의 첫 번째 버전은 20 2013년 9월 2026: 날짜의 단일 CSFloat 카탈로그 스냅샷에서 245 카테고리를 집계했습니다. 그 스냅샷은 여전히 여기에 남아 있습니다 ↗. 현재의 등록 내역은 하나의 시장이 아닌 다섯 개의 시장을 아우르기 때문에 더 광범위합니다. 이 두 가지는 별도로 집계된 것이므로 합산해서는 안 됩니다.\n\nValve의 구체적 이행 진술서\n\nValve의 ‘2016’ 게임 내 아이템 거래 업데이트 ↗ 보관됨 2026-09-21 ↗ OpenID 및 자동 생성된 Steam 계정을 사용하는 도박 사업자를 대상으로 합니다. 이는 모든 외부 마켓플레이스를 전면 금지하는 조치보다는 범위가 더 좁습니다.\n\n통역 범위\n\n이는 판매가 아닌 제안입니다. 하나의 시장 명칭 아래에는 플로트, 패턴 또는 스티커 세부 사항이 서로 다른 여러 실물 상품이 포함될 수 있습니다. 이 기록은 총 시장 가치나 ‘Valve’의 의도를 반영하지 않습니다.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "엘리트 스킨스 등록 — $1,800의 시장 상한선"
          },
          {
            "level": 2,
            "id": null,
            "text": "측정 가능한 달러 최저치"
          },
          {
            "level": 3,
            "id": null,
            "text": "왜 이것이 추정치가 아니라 확정치인지"
          },
          {
            "level": 2,
            "id": null,
            "text": "한계가 간과하는 점"
          },
          {
            "level": 3,
            "id": null,
            "text": "★ Butterfly Knife | Doppler (Factory New)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Steam의 상한선 설정으로 인해 가격 발견 기능이 Steam 밖으로 밀려났다"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam 목록을 마무리합니다"
          },
          {
            "level": 3,
            "id": null,
            "text": "Dragon Lore: $10,940.85"
          },
          {
            "level": 3,
            "id": null,
            "text": "가격 및 이적 분배"
          },
          {
            "level": 2,
            "id": null,
            "text": "천장도 도타를 잡아낸다 2"
          },
          {
            "level": 3,
            "id": null,
            "text": "영웅적 잔혹한 초승달"
          },
          {
            "level": 3,
            "id": null,
            "text": "다크 아트리스티 케이프"
          },
          {
            "level": 3,
            "id": null,
            "text": "타락한 파워드 스타"
          },
          {
            "level": 2,
            "id": null,
            "text": "이 결과는 정확한 상한선에 좌우되지 않는다"
          },
          {
            "level": 2,
            "id": null,
            "text": "이 중 실제로 판매되고 있는 것은 정말 드물다"
          },
          {
            "level": 3,
            "id": null,
            "text": "AWP | 드래곤의 전설"
          },
          {
            "level": 3,
            "id": null,
            "text": "M4A4 | 하울"
          },
          {
            "level": 3,
            "id": null,
            "text": "AK-47 | 와일드 로터스"
          },
          {
            "level": 3,
            "id": null,
            "text": "AWP | 군니르"
          },
          {
            "level": 2,
            "id": null,
            "text": "물건의 가격이 비쌀수록, 눈에 띄는 장소에서 더 멀리 떨어져 있다"
          },
          {
            "level": 2,
            "id": null,
            "text": "419에서 관찰된 모든 범주"
          },
          {
            "level": 2,
            "id": null,
            "text": "계산 결과를 확인해 보세요"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve만의 상한선과 조건"
          },
          {
            "level": 3,
            "id": null,
            "text": "가격은 어디서 나오는가"
          },
          {
            "level": 3,
            "id": null,
            "text": "우리가 얻지 못한 것"
          },
          {
            "level": 3,
            "id": null,
            "text": "이전 ‘CSFloat’ 레지스터"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve의 구체적 이행 진술서"
          },
          {
            "level": 3,
            "id": null,
            "text": "통역 범위"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/ko/#market-gap-section",
          "https://phishdestroy.io/steam_dossier/ko/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/ko/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/ko/skin_atlas.html#grading",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-above-the-ceiling.json",
          "https://phishdestroy.io/steam_dossier/ko/elite_skins#selected",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://csmarketcap.com/search?minPrice=1800&amp;page=1",
          "https://store.steampowered.com/agreement/?l=english",
          "http://web.archive.org/web/20260921022032/https://store.steampowered.com/agreement/?l=english",
          "https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921021947/https://store.steampowered.com/oldnews/22883",
          "https://phishdestroy.io/steam_dossier/ko/#proxy-bypass-explainer",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/skinport-floor-over-cap.json",
          "https://docs.skinport.com/items",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-float-scarcity.json",
          "https://phishdestroy.io/steam_dossier/ko/elite_skins#register",
          "https://cs2.sh/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/csfloat-catalogue.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ko/elite_skins.content.json",
      "export_json_sha256": "d15da059cb9a142a162698587ac2cb0a6d8005e7a3e0df9ccc825b4f048b03d9"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ko/enforcement_audit.html",
      "language": "ko",
      "title": "인구조사 Valve는 공개하지 않을 것이다 — Steam 도시에르",
      "source_url": "https://phishdestroy.io/steam_dossier/ko/enforcement_audit",
      "source_html_sha256": "5415fa90073927dc7acac4b61cbcb961611149a733d0287394badbcc8c9cac80",
      "exported_at": "2026-09-29T00:21:50.590Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "enforcement_audit.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ko/enforcement_audit.pdf?v=print-20260929-v5",
        "sha256": "883453fc22e6276de0911f2a62a03f4d1ae40423bdbe25edd1b975101fa15c70",
        "bytes": 144736,
        "pages": 10
      },
      "integrity": {
        "signed_object": "enforcement_audit.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "enforcement_audit.content.json.asc",
        "digest_file": "enforcement_audit.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify enforcement_audit.content.json.asc enforcement_audit.content.json",
          "sha256sum -c enforcement_audit.content.json.sha256"
        ]
      },
      "content": {
        "text": "증거물 VI — VALVE 인구조사 결과는 공개되지 않을 것이다\nSteam 계정 농장은 얼마나 클까? 직접 집계했습니다.\n\nSteam에서 얼마나 많은 자동화 계정이 실행되고 있는지에 대한 공식 통계는 공개되어 있지 않습니다. 이 수치를 비밀로 할 필요는 없습니다. Steam ID 공간은 연속된 정수 범위이며, Valve은 이 범위를 순회하는 웹 API 키를 발급하기 때문입니다. 그래서 우리는 스스로를 식별하는 가장 큰 집단인 ArchiSteamFarm 커뮤니티를 대상으로, Valve의 자체 차단 엔드포인트를 통해 모든 구성원을 한 번씩 조회했습니다. ASF는 첫 실행 시 사용자가 명시적으로 거부하거나 그룹 가입 설정을 해제하지 않는 한 자동으로 Steam 그룹에 가입하기 때문에, 이 커뮤니티는 스스로를 Steam로 선언합니다 (AutoJoinSteamGroup / 통계). 이 설정은 기본적으로 활성화되어 있기 때문에, 그룹 구성원에는 활동 중인 다중 계정 상업용 봇 네트워크, 가끔씩 계정을 방치해 두는 취미 사용자, 그리고 개인 계정에서 소프트웨어를 실행한 후 기본 구독 설정을 제거하지 않은 일반 플레이어 등 광범위한 사용자층이 포함됩니다. 따라서 이 그룹의 구성원은 해당 소프트웨어가 누적적으로 도달한 범위를 보여주는 실질적인 실태 조사 결과라고 할 수 있습니다: 10,880,610 총 계정 수 ($5.00 매장 입구를 통과한 5,360,499명의 확인된 비제한 회원 포함). 그러고 나서 우리는 유일하게 중요한 질문을 던졌다. Valve이 그들에게 실제로 어떤 영향을 미쳤는가?\n\n이 페이지가 다루지 않는 내용. 이는 Valve이 천만 명을 차단해야 한다는 주장이 아니며, 카드 파머들에 대한 불만도 아닙니다. 아래에 제시된 모든 숫자는 오직 한 가지 이유 때문에 여기에 있습니다: Valve ~하는가 개인을 영구적으로 차단하며, 이에 대해 서면으로 제시하는 사유는 Steam의 상업적 이용과 자동화입니다. 이는 $5.00 잠금 해제, 게임 라이선스 및 마켓 수수료 Valve을 그 과정에서 징수하는 운영자가 대규모로 동일한 행위에 대해 동일한 규칙을 어떻게 적용하는지 측정하는 것입니다. 여기서 드러난 문제는 ‘팜’ 자체가 아니라 비대칭성입니다.\n\n1,088만 개걸어 다니는 사기꾼들 (53.5k)유료(10만) 대 무료 감사\n10,880,610ASF 그룹 전체 구성원이 Valve의 자체 차단 API를 모두 읽어보았습니다 (제한 대상 및 비제한 대상 포함).\n88.97%한 번도 차단당한 적이 전혀 없습니다 — 9,680,599개의 계정이 여전히 활성화되어 있습니다\n63.06%차단된 계정 중 유료 계정($5+ 지출) — 100,000 SRSWOR 구간 (±0.39% 오차 범위)\n67.77%51,732명의 판결을 받은 사기범 중 사기 행위 금지 조치가 전혀 없는 자 (전체 조사 결과)\n01 — 규모\n1,000만 개의 계정 중 10개 중 9개는 손도 대지 않은 상태\n\n자신을 포함하는 한 집합으로, Valve의 끝점을 한 번 통과하는 것으로 읽는다.\n\n왜 자체 집계하는가\nASF가 여러분을 위해 이 그룹에 합류합니다\n\n첫 실행 시 ArchiSteamFarm 세트 통계 기본값은 ‘true’이며, Archi의 SC Farm Steam 그룹에 가입됩니다. 운영자는 직접 탈퇴를 신청해야 합니다. 따라서 이 멤버십 수는 설치 건수의 최소값일 뿐, 최대값은 아닙니다. ‘통계’ 기능을 비활성화한 운영자는 통계에 포함되지 않으므로, 실제 설치 건수는 적어도 이 수만큼은 됩니다.\n\n우리가 읽은 것\n10,880,610 총 등록 건수\n\nAPI 회원 목록에는 제한된 ID와 제한되지 않은 ID를 포함해 총 10,880,610개의 SteamID64가 반환되었습니다. Steam의 그룹 페이지에는 5,360,499개(제한되지 않은 ID만)가 표시됩니다. 모든 항목은 한 번씩 ISteamUser/GetPlayerBans 2026-09-23에서. 한 키를 55분 동안.\n\n정답\n88.97% 정리\n\n1,200,011에는 Steam 금지 조항(11.03%)이 적용되지 않습니다. 나머지 9,680,599 기록된 내용이 전혀 없음 — 커뮤니티 제재도 아니고, VAC도 아니고, 아무것도 아닙니다. 농장은 정리되지 않고 그대로 운영되고 있습니다. 한 사람을 겨냥한 바로 그 조항만으로도 그 사람을 영구적으로 제명하기에 충분합니다.\n\n10,880,610개의 계정 중, Valve을 터치한 계정은 몇 개인가?\n\n스캔 대상 전체 함대를, Valve이 어떠한 금지 조치도 적용했는지 여부에 따라 구분한 것입니다. 빨간색 영역은 Valve이 이 함대에 대해 지금까지 취한 모든 조치입니다.\n\n88.97%한 번도 금지된 적이 없다\n11.03%\n어떤 종류의 금지 조치도 없음 — 9,680,599 (88.97%)일부 Steam 금지 — 1,200,011 (11.03%)\n10,880,610ASF 그룹 구성원들의 스캔 결과\n9,680,599한 번도 차단된 적 없음 — 88.97%\n1,200,011모든 금지 조치를 적용 — 11.03%\n55분하나의 API 키로 이 모든 것을 집계하려면\n이 함대가 존재하기 위해 이미 지불한 대가는 Valve입니다\n\n농장의 수입을 추산한 것이 아닙니다. Valve의 가게에서 이미 지출한 금액의 최저 한도이며, 이는 Valve의 규칙을 위의 집계 결과에 적용하여 산출한 것입니다.\n\n10,880,610의 집계 수치는 API에서 반환된 전체 ASF 그룹 회원 목록을 포함하며, 여기에는 제한 계정과 비제한 계정이 모두 포함됩니다. Steam 자체의 제한된 사용자 계정 해당 페이지에는 제한된 계정은 ~하지 않는다고 명시되어 있습니다. ~에 포함되다 Steam 그룹 구성원(표시된 그룹 규모에서는 제외되지만), 여전히 기본 구성원 목록에는 나타날 수 있습니다. 제한되지 않은 부분집합, 즉 Steam 매장에서 최소 $5.00을 지출한 계정은 정확히 5,360,499 — 그룹 페이지에는 Steam이라는 수치가 표시되는데, Steam의 자체 규칙에 따라 제한된 계정은 여기서 제외됩니다. $5.00 하한선 계산은 제한되지 않은 계정으로만 구성된 하위 집합에만 적용됩니다.\n\n5,360,499비제한 회원\n(Steam의 표시된 그룹 수)\n×\n$5.00Valve의 자체 최소값\n더 이상 제약을 받지 않기 위해\n=\n$26,802,495매장 내 지출 한도\n비제한 부분집합에 의해\n\n이는 Valve이 함대의 제한이 없는 부분으로부터 이미 수령한 금액의 하한선일 뿐, 수익 추정치도 아니고 이익 주장도 아닙니다. 대부분의 경우 계정당 실제 지출액은 이보다 더 높으며, $5.00 수치는 단지 필요한 최소 기준에 불과합니다.\n\n2차 수확: 재배 상품 거래량에 대해 최대 66.7%의 수수료가 부과됩니다. $26.8M의 입장료 외에도, 커뮤니티 마켓에서 청산되는 모든 카드와 상품은 Valve의 의무적인 2센트 최소 수수료 하한선($0.01 Steam 수수료 + $0.01 발행자 수수료)을 지불합니다. 일반적인 3센트 카드와 잡동사니 아이템의 경우, Valve은 3센트 중 2센트를 가져가므로, 이는 Valve에게 유리한 방향으로 66.67%의 실질적인 삭감이 된다., 이는 표면상의 15% 마케팅 비율을 훨씬 상회하는 수치입니다.\n\n인구와 관련하여 반드시 유의해야 할 점: 그룹 가입 사실만으로는 모든 계정이 전용 봇이라는 증거가 되지 않으며, Steam에 있는 모든 봇을 포괄하는 것도 아닙니다. ASF는 기본적으로 실행 시 계정을 커뮤니티 그룹에 자동으로 가입시킵니다. 사용자가 해당 설정 플래그의 체크를 명시적으로 해제하거나 비활성화하지 않는 한 (AutoJoinSteamGroup), 정기적인 플레이어, 가끔 접속하는 유휴 사용자, 커뮤니티 구성원들이 자동 파밍 함대와 함께 명단에 남아 있습니다. 또한, Steam 제재에는 공개 사유란이 없습니다. 이 결과는 해당 소프트웨어와 관련된 전체 사용자 집단을 대상으로 한 경험적 비율일 뿐, 특정 계정에 대한 개별적인 판결이 아닙니다. 집계된, 재현 가능한: asf-ban-census-2026-09-23.json.\n\n02 — 지리\n함대가 주둔하는 곳\n\n차단된 계정 중 국가를 명시한 계정은 단 8.5%개에 불과하다. 국가를 명시한 계정 중에서는 미국이 가장 큰 비중을 차지한다.\n\nSteam 프로필에는 선택 사항인 국가 필드가 포함되어 있습니다. 100,413개의 차단된 계정 중 1,182,811개가 이를 기입했습니다 — 8.5%개.† 그 소수 국가들 중에서는 미국이 15.5%으로 선두를 달리고 있으며, 그 뒤를 우크라이나, 중국, 러시아가 따르고, 나머지는 유럽, 라틴 아메리카, 동남아시아 전역에 걸쳐 긴 꼬리 형태로 분포되어 있다. 이 분야를 검증하는 사람은 아무도 없다. 아프가니스탄이 상위 10위권에 자리 잡고 있는데, 이는 대략 그 나라의 실력에 부합하는 순위다. 나머지 91.5%개국은 순위에 포함되지 않고 생략되었으므로, 아래에 제시된 것은 자발적으로 선택된 소수의 양상일 뿐, 함대의 배치도도 아니며, 어디에서 운영되는지를 판단할 근거도 아니다.\n\n신고된 국가별 차단 계정\n\n공공장소를 노출한 100,413개의 차단된 계정 중 상위 15개국입니다. 비율은 해당 위치 정보가 확인된 계정의 비율을 나타냅니다. 마우스를 올리면 계정 수를 확인할 수 있습니다.\n\n0%\n5%\n10%\n15%\n20%\nUnited States\nUkraine\nChina\nRussia\nCanada\nAustralia\nJapan\nBrazil\nGermany\nAfghanistan\nUnited Kingdom\nRomania\nFrance\nPhilippines\nIndia\n\n읽어온 위치 GetPlayerSummaries 차단된 하위 집합에 대해. 이 필드는 계정 소유자가 직접 설정하며 누구도 검증하지 않기 때문에, VPN 출구나 장난으로 입력된 항목도 실제 항목과 동일하게 처리됩니다.\n\n03 — 신선함\n최근의 미결 건, 기존에 누적된 미결 건이 아님\n\n계정 생성 시점을 기준으로 볼 때, 이용 정지된 사용자층은 최근에 발생한 것이지 트레이딩 카드 시대의 잔재가 아닙니다.\n\n만약 이것이 서서히 정리되고 있는 오래된 문제라면, 차단된 계정들은 트레이딩 카드 출시 초기 시기에 집중되어 있어야 할 것입니다. 하지만 정반대입니다. 생성 날짜가 확인된 1,132,852개의 차단된 계정 중, 70%은 2020년 이후에 제작되었으며, 그중 거의 절반은 2023년 이후에 제작되었다. 이 수치는 2017년에 생성된 59,175에서 시작하여 최고치인 227,030 2024년에만 생성된. 그들 모두는 $5.00 매장의 입구에서 카드를 받기 전에 이미 통과해 버렸기 때문에, 각자 입장료를 내야 했다.\n\n차단된 계정이 생성된 시점\n\n생성 날짜가 확인된 1,132,852명 차단 회원의 계정 생성 연도. 해당 기간은 2020년부터 2026년까지이며, 2013년부터 2015년까지의 트레이딩 카드 시대가 아닙니다. 정점은 2024년입니다. 마우스를 올리면 수치를 확인할 수 있습니다.\n\n0k\n63k\n125k\n188k\n250k\n'13\n'14\n'15\n'16\n'17\n'18\n'19\n'20\n'21\n'22\n'23\n'24\n'25\n'26\n70%2020년 이후 생성된 차단 계정 중\n227,0302024년 — 차단 계정이 가장 많이 생성된 해\n51,701두 개의 정점을 기록한 해 사이에 나타난 2021년의 저조기 — 원인은 밝혀지지 않았다\n2003→2026범위는 존재하지만, 데이터는 지난 6년 치입니다.\n\n제작 연대는 GetPlayerSummaries SteamID64 기준으로 중복을 제거한 차단된 사용자 집합에 대한 것입니다. 생성일은 계정이 생성된 시점을 의미하며, 차단된 시점이나 계정을 대량 생성하기 시작한 시점이 아닙니다. 이 수치는 의도 여부가 아닌, 해당 사용자 집합이 얼마나 최근에 형성되었는지를 보여주는 증거로 해석됩니다. 이 차트에는 다음 세 가지 사항이 반영되어 있지 않습니다:\n\n2024년 이후의 트렌드. 2025년이나 2026년에 생성된 계정은 제재를 받을 시간이 상대적으로 적었고, 2026년의 기간은 9개월에 불과하므로 227,030 → 121,070 → 16,534는 감소가 아니라 검열에 해당한다.\n금지율. 생성 연도는 차단된 계정에 대해서만 집계되었기 때문에 분모가 없습니다. 설치 기반이 증가하는 것만으로도 이러한 추세가 나타날 수 있습니다.\n2021년이 무너진 이유. 51,701은 105,821과 104,641 사이에 위치하며, 양쪽 이웃 요소의 절반보다 아래에 있습니다. 이를 설명하는 공개된 내용은 없으며, 매끄럽게 처리되지 않고 그대로 노출되어 있습니다.\n04 — 타이밍\nValve이 작용할 때는 첫 해 안에 작용한다\n\n88.97%이 손대지 않은 상태로 남아 있는 것에 대한 명백한 변명은 처리 대기 중인 업무가 많다는 점입니다. 그러나 과거의 금지 조치들은 그와 달리 말하고 있습니다.\n\n계정이 정지 조치를 받았을 당시 개설된 지 얼마나 되었는지\n\n생성일과 마지막 차단 날짜가 모두 기록된 293,750개의 차단된 계정에 대해, 차단 당시의 계정 사용 기간을 분석한 결과, 절반 이상이 계정 생성 후 1년 이내에 적발된 것으로 나타났다.\n\n0%\n10%\n20%\n30%\n40%\n<6 mo\n33.7%\n6–12 mo\n21.5%\n1–2 y\n20.6%\n2–5 y\n14.3%\n5 y+\n10.0%\n55.1% inside the first year\n첫 해에 금지됨 — 55.1%나중에 차단됨 — 44.9%\n0.80년차단 조치가 내려졌을 당시 계정의 연령 중앙값\n55.1%계정 개설 후 첫 해 내에 이용 금지 조치됨\n33.7%처음 6개월 이내에 이용 금지\n293,750두 날짜가 모두 포함된 계정\n\n이것이 명백한 반론에 대한 답변입니다. 만약 집행이 단순히 느려서 — 처리해야 할 업무가 밀려 있는 탓에 — 함대의 88.97%이 아무런 조치를 받지 않았다면, 그러한 금지 조치는 do 사용자 연령대가 높게 나타날 것으로 예상되었지만, 실제로는 정반대였다. 차단된 계정의 중앙값은 생후 9개월 반, 그리고 세 번째 개체인 33.7%는 6개월 만에 포획되었다. Valve이 이 개체군에 작용할 때, 그 작용은 매우 빠르게 이루어진다. 여전히 도주 중인 10마리 중 9마리는 줄을 서서 기다리고 있지 않다.\n\n금지 당시의 연령 = 작성일 기준 GetPlayerSummaries 에서 암시된 금지일로부터 차감하여 마지막 차단 이후 경과 일수, 계속 읽기 2026-09-23. 이 값은 두 값이 모두 존재할 때만 계산됩니다: 1,200,011개의 차단된 계정 중 293,750개. 나머지 계정은 ‘지나간 일수’ 값이 보고되지 않아 생략된 것이지, 추정된 것이 아닙니다. 따라서 이 수치를 모든 차단 건수가 아닌, 날짜가 지정된 하위 집합의 규모로 이해해 주십시오.\n\n05 — 금지 조치가 실제로 무엇인지\nValve이 작동하더라도 봇은 멈추지 않습니다\n\n어떤 금지 조치가 적용된 11% 중, 어떤 금지 조치인지 확인해 보세요.\n\n차단은 단순한 차단이 아닙니다. 1,200,011개의 계정 중 Valve개가 신고한 계정 중, 99.8%을 가지고 다니다 커뮤니티 금지 — 포럼, 프로필 및 그룹에 대한 제한이지만, 거래 봇에게는 아무런 영향도 미치지 않습니다. 해당 계정은 여전히 카드를 받을 수 있고, 거래할 수 있으며, 재고를 이동할 수 있습니다. 22.2% 최소 한 건의 게임 이용 정지 처분을 받았거나 3.9% VAC 정지 처분을 받은 계정; 범주가 중복되므로 합산되지 않습니다. 실제로 거래를 차단하는 유일한 제재인 경제/거래 정지 처분을 받은 계정은 5,214개입니다. 우리는 이 수치에만 근거하여 주장을 펼치는 것이 아닙니다. Steam 전반적으로 거래 금지 조치는 드문 편입니다. 이 차트의 요점은 더 간단합니다. 비록 Valve이라는 비율일지라도 ~하는가 터치는 계속 거래되고 있다.\n\n차단당한 11%들은 실제로 어떤 이유로 차단당했는가\n\n각 금지 유형은 전체 10,880,610 스캔된 회원 중 차지하는 비율입니다. 한 계정에 여러 가지 유형이 적용될 수 있습니다. 마우스를 올리면 수치를 확인할 수 있습니다.\n\n0%\n4%\n8%\n11%\n15%\nCommunity ban\nGame ban\nVAC ban\nEconomy / trade ban\n\nSteam 금지 조치에는 ‘사유’ 필드가 없으므로, 이러한 금지 조치 중 어느 것도 특별히 ‘카드 파밍’에 기인한 것은 아닙니다. 이는 현재 적용 중인 금지 유형의 조합이며, 각 유형이 실제로 무엇을 제한하는지와 함께 나열된 것입니다. 커뮤니티 금지는 거래를 막지 않지만, 경제/거래 금지는 거래를 차단합니다. 종합: asf-ban-census-2026-09-23.json.\n\n06 — 나머지 인구\n사기꾼들 Valve, 자, 가보자: 51,732 완전한 인구 조사\n\n동일한 공식 API를 기준으로 측정된 두 번째 독립적인 목록, 즉 ‘커뮤니티가 확인한 사기 사례’입니다.\n\n자동화 집단은 무해한 게으름뱅이들로 치부할 수 있겠지만, 두 번째 집단은 그렇지 않다. SteamRep는 오랫동안 운영되어 온 커뮤니티 평판 데이터베이스이며, 표시된 계정은 차단됨 해당 커뮤니티에서 사기꾼으로 판정된 인물이 있으며, 피해자 증빙 자료와 거래 채팅 기록이 확인되었습니다. 저희는 전체에 대한 100% 조사를 완료했습니다. 51,732 ‘차단됨’ 상태인 프로필 Steam의 공식 웹 API에 반하여 (ISteamUser/GetPlayerBans/v1) — 그리고 사기 행위에 대응하는 제재 조치만 집계했습니다. VAC 금지 조치는 게임 내 소프트웨어 부정 행위(에임봇, 월핵 등)에 대한 것으로, 트레이더에게는 아무런 영향을 미치지 않으며 사기에 대한 조치가 취해졌다는 증거 Valve도 되지 않으므로, 사기 단속 조치로 집계되지 않습니다.\n\n전체 51,732 계정 조사 결과, 67.77% — 35,059 명의 사기 행위가 확인된 사용자 — 는 Valve로부터 사기와 관련된 제재를 단 한 건도 받지 않았습니다: 이들은 여전히 거래를 하고, 새로운 피해자에게 친구 요청을 보내며, 메시지를 보낼 수 있습니다. 커뮤니티 이용 금지나 거래 금지 조치를 받은 계정은 32.23%개에 불과하며, 실제로 인벤토리 이전을 차단하는 유일한 조치인 거래 금지 조치는 단 18.81%개(9,731개 계정)에만 적용되어 있습니다. 추가로 12.81%명(6,627개 계정)은 순전히 게임 내 부정행위만으로 VAC건의 게임 이용 정지 조치를 받았으나, Steam건의 거래에 대해서는 전혀 제한을 받지 않고 있습니다.\n\nValve가 사기 관련 제재를 적용했는지 여부에 따른 확인된 사기꾼 (전체 조사)\n\n모든 51,732 SteamRep-차단된 프로필을, Valve가 커뮤니티 차단인지 거래 차단인지에 따라 분류한 것입니다. VAC 및 게임 차단은 제외되었습니다. 이는 사기 행위에 대한 조치가 아니기 때문입니다. 마우스를 올리면 건수를 확인할 수 있습니다.\n\n0%\n18%\n35%\n53%\n70%\nNo scam-relevant ban\nCommunity or trade ban\n0%\n6%\n13%\n19%\n25%\nCommunity ban\nTrade / economy ban\nVAC (not fraud)\nGame ban\n51,732SteamRep-검토된 차단된 프로필 — 100% 전체 조사\n35,059사기 관련 제재 기록 없음 (67.77%)\n18.81%사기를 근절하는 거래 금지 조치를 시행하라 (9,731)\n32.23%해당 주식 Valve은 커뮤니티 또는 거래 금지 조치(16,673)를 받았습니다.\n\nSteamRep은 제3자가 운영하는, 커뮤니티의 심사를 거친 평판 데이터베이스일 뿐, Valve의 결정과는 다릅니다. 바로 이것이 핵심입니다: Valve 자체의 행적을 기준으로 측정된 외부 증거입니다. 표준 내보내기 파일에서 51,732으로 표시된 모든 차단된 프로필은 다음 항목과 직접 교차 참조되었습니다. ISteamUser/GetPlayerBans/v1. “사기 관련”이란 커뮤니티 또는 경제/거래 금지 조치를 의미합니다. VAC (12.81%) 및 게임 이용 금지 조치(3.86%)는 사기가 아닌 부정행위를 다루는 것이므로 별도로 집계됩니다. 전체 감사 데이터 세트: steamrep_steam_bans.csv.\n\n두 집단, 하나의 연구 결과\n\n이들은 같은 사람들이 아니며, 같은 행위도 아닙니다. 하나는 천만 개의 자동화 계정이고, 다른 하나는 5만 3천 명의 유죄 판결을 받은 사기범들입니다. 이 둘이 공통적으로 가진 점은 결과의 형태뿐입니다: 농가 계좌 10개 중 9개는 한 번도 사용된 적이 없으며, 사기 행위가 확인된 사기꾼의 3분의 2 이상(67.77%)은 사기와 관련된 어떠한 제재도 받지 않습니다. 커뮤니티 차단 Valve은 거래가 아닌 포럼과 프로필에 대해 자유롭게 제한을 가합니다. 신고 버튼, 평판 데이터베이스, 사기를 막아주는 차단 기능: 이 모든 것이 존재하지만, 제대로 활용되지 않고 있습니다. 이를 메인 파일의 보관된 거부 사례와 비교해 보면, 동일한 회사가 단일 계정을 영구적으로 삭제하면서 상업적 이용과 자동화를 이유로 제시한 사례가 있습니다. 이 조항은 단순히 유휴 상태에 있는 것이 아니라, 명확하게 적용되고 있습니다.\n\n07 — $5.00 계정 게이트 및 계정 탈취\n‘0’ 계정 실증 감사: 봇넷은 일회용 무료 계정이 아니다\n\n통계적 표본 추출 논리와 수학적 증명: 왜 다른 어떤 100,000 값을 대입하더라도 정확히 동일한 결과가 나오는지.\n\nValve이 규제 당국 및 소비자 보호 기관에 제시한 주된 변명은, 자동화된 사기 및 계정 대량 생성 행위가 일시적인 무료 “일회용” 계정을 통해 이루어지며, 이러한 계정은 곧 차단된다는 것이었습니다. Valve이 공개한 규정에 따르면, 계정은 한정판 적어도 그 정도를 지출할 때까지 5.00달러 Steam 스토어에 등록되어 있어, 거래, 친구 요청 및 API 기능을 이용할 수 없습니다. 저희는 수학적으로 엄격한 대표 표본을 대상으로 수익화 상태를 테스트하여 이 주장을 직접 검증했습니다. 100,000 계정 차단 Steam 당사의 1,182,811 프로필 메타데이터 코퍼스에서 추출한 것입니다.\n\n시료 채취 지침 (SRSWOR)\n100,000 편향 없는 슬라이스\n\n출처: N = 암호학적으로 균일한 PRNG를 이용한 ‘무반환 단순 무작위 표본 추출’을 통해 1,182,811개의 고유한 차단된 Steam개 계정을 선정했습니다. 모든 계정의 포함 확률은 동일하게 P = n / N ≈ 8.45%, 생존 편향과 활동 편향을 완전히 제거한다.\n\n수학적 증명\n오차 범위 < ±0.4%\n\n에서 유한 모집단 보정(FPC) 공식을 적용하면 99% 신뢰 구간 (Z = 2.576):\nMoE = Z × √[p(1-p)/n] × √[(N-n)/(N-1)] ≈ ±0.39%\n\n재현성\n왜 10만 단위의 수익률은 모두 똑같은가\n\n오차 범위는 99% 신뢰 수준에서 ±0.4% 이내로 제한되므로, 다른 어떤 독립적인 100,000-계정 표본을 추출하더라도, 수학적으로 63.06% ± 0.39% 범위 내에 속할 것이 보장된다. (62.67%에서 63.45%까지). 이 표본은 금지 대상인 전체 118만 명을 반영하고 있다.\n\n이번 감사 결과는 “일회용 봇”이라는 변명을 완전히 무너뜨립니다. Steam의 기존 XML 프로필 인터페이스를 통해 감사 대상이었던 100,000개 계정 중: 61,490개 계정(63.06%개 분류 계정 중)은 Steam에서 최소 $5.00을 지출한 비제한(유료) 계정입니다. 오직 36,021 (36.94%) 는 무료 계정이었으며, 2,489개는 설정이 되지 않았거나 비공개 계정이었습니다.\n\n100,000 차단된 계정: 유료 계정($5+ 스토어 이용 금액) 대 무료 제한 계정\n\n무작위로 추출한 100,000개의 차단 계정에 대한 실증적 감사 결과. 63%개 이상이 Valve의 유료 금융 게이트를 통과했습니다. 마우스를 올려놓으면 수치를 확인할 수 있습니다.\n\n0%\n16%\n33%\n49%\n65%\nNon-limited (Paid ≥ $5.00)\nLimited (Free < $5.00)\n100,000표본 모집단 (SRSWOR, N=118만)\n63.06%제한이 없는 유료 계정 (61,490 계정)\n±0.39%99% 신뢰구간의 오차 범위\n~745,800118만 건의 차단된 계정 데이터에서 추정한 유료 계정 수\n구조적 현실: 산업적 규모의 계정 청산\n\n표본으로 추출된 차단 계정 중 63%가 Valve의 상점에서 실제 돈을 지출한 유료 계정인 이유는 무엇일까요? 봇넷 운영자들은 일회용 계정에 수백만씩을 자기 주머니에서 직접 지출하지 않습니다. 이 비율은 그 규모를 잘 보여줍니다. 해킹당하거나 탈취된 계정 생태계 내에서 순환하고 있다.\n\n이 척도는 지하 플랫폼에서 직접 확인할 수 있습니다. FSB Market (익명 명칭이며 원래 이름은 여기에 공개하지 않습니다)과 같은 마켓플레이스에서, 550,000 Steam 계정 (해킹 로그, 피싱 캡처 자료, 자격 증명 무차별 대입 공격)은 언제든지 활발히 판매 목록에 올라와 있습니다 (phishdestroy.io/live-intel). 이 마켓플레이스는 Valve의 자체 Steam OpenID를 사용하여 구매자와 판매자의 신원을 확인하며, 어느 쪽도 FSB Market 또한 관련 포럼 Valve의 링크 필터에 의해 차단되었습니다.\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\n제06조에 명시된 바와 같이, Valve은 이러한 사기 행위를 선제적으로 근절하지 않습니다: 67.77%명의 커뮤니티에서 확인된 사기꾼 중 Steam명에게는 사기 금지 조치가 전혀 적용되지 않았습니다., 그리고 자동화 계정 군의 88.97%은 전혀 손대지 않은 채로 남아 있습니다. 이 계정들은 자유롭게 활동하며, 공식 API를 통해 인증을 받고, 생태계 전반에서 거의 아무런 제재도 받지 않은 채 거래를 진행합니다.\n\n과학수사 증거 및 집행 아키텍처 다이어그램\n1,088만 개의 스캔된 계정에서 10만 개의 실증적 샘플 및 53,500명의 확인된 사기꾼으로 이어지는 상호작용 흐름 · 링크를 클릭하여 원본 증거를 확인하세요\nTier 01 · 1,088만 자동화 함대 현황 조사\nSteam에서 가장 규모가 큰 자칭 자동화 사용자 집단이 Valve의 공식 차단 API를 차례로 통과했다. 이는 상업용 봇 군단이 수천만 단위의 가입비를 지불하면서도 88.97%에서 아무런 제재 없이 운영되고 있음을 입증한다.\n9,680,599 88.97% 활성 및 미사용\n기록상 어떠한 종류의 차단 조치도 받은 적이 없는, 자동화 소프트웨어를 실행 중인 계정.\n인구조사 원본 JSON (1.2 KB) ↗01절 확인 ↗\n$26,802,495 직접 매장 매출 하한선\n최소 참가 기준인 $5.00을 초과한 5,360,499명의 비제한 회원으로부터 Valve를 모았습니다.\n카드 경제 감사 ↗Valve $5 규칙 FAQ ↗\n1,200,011 11.03% 표시된 부분집합\n99.8% 계정에는 커뮤니티 이용 제한 조치만 적용되며, 99.95% 계정에 대해서는 거래가 계속 가능합니다.\n차단 유형별 분석 ↗차단된 DB (60.4 MB) ↓\n2단계 · 100,000-계정 실증적 표본 감사 (N = 1,182,811)\n기존 XML 엔드포인트를 통해 평가된 SRSWOR 슬라이스의 대표값. 99% 신뢰 구간에서 오차 범위가 < ±0.4%임으로 수학적으로 입증됨. 금지된 봇이 무료로 생성된 일회용 계정이라는 주장을 반박한다.\n61,490 (63.06%) 제한 없는 유료 계정 ($5+ 지출)\n차단된 계정의 63% 이상이 유료 거래와 관련되어 있습니다. 이를 바탕으로 추산하면, 차단된 계정 풀 내 유료 계정은 약 745,800개($3.73M+ 진입 기준)에 달합니다.\n제한된 결과 CSV (2.1 MB) ↓10만 건 법의학 보고서 ↗\n36,021 (36.94%) 제한된 무료 계정 (< $5.00)\nValve이 정의한 “일회용 봇” 유형에 해당하는 차단된 프로필은 소수에 불과했습니다. 2,489개의 계정은 설정이 되어 있지 않거나 비공개 상태였습니다.\n10만 건의 표본 데이터 CSV (8.5 MB) ↓지출 분석 MD ↗\n34.67% 대 63.93% 프로필 정보 정화 감사\nValve개의 계정에서 닉네임을 삭제하고 원본 SteamID64로 복원했으나, 34,673개의 계정에서는 사용자 지정 이름과 아바타를 전혀 건드리지 않았으며, 63,928개의 차단된 계정에서는 이를 그대로 두었습니다.\n소독 섹션 ↗개요 로드맵 ↗\n34.59% 레거시 구 계정 (2003–2019년 생성)\n차단된 계정의 3분의 1 이상이 5년에서 20년 이상 전에 등록된 것으로 나타나, 장기간 Steam 게임을 해온 플레이어들의 계정이 산업적 규모로 탈취되었음을 입증하고 있다.\n연표 ↗지원 거부 ↗\nTier 03 · 51,732 SteamRep 확인된 사기꾼 명단\n피해자의 채팅 기록 및 거래 증빙 자료를 바탕으로 지역사회에서 판정된 사기꾼들에 대한 100% 전체 조사 결과를, 공식 Steam 차단 API와 교차 대조한 자료입니다. 이는 체계적인 단속 실패를 입증합니다.\n35,059 (67.77%) 사기 행위 제재 없음 (완전한 면책)\n신원이 확인된 사기꾼 중 3분의 2 이상이 Valve로부터 커뮤니티 이용 금지나 거래 금지 조치를 받지 않았습니다. 거래 및 피해자 유인 활동을 완전히 정상적으로 수행하고 있습니다.\nSteamRep API 차단 (2.6 MB) ↓SteamRep 감사 보고서 ↗\n9,731 (18.81%) 경제 / 무역 제재\n재고 청산을 차단하는 유일한 제재 조치입니다. 확인된 사기꾼 중 5분의 1 미만에게서만 적용됩니다.\nSteamRep 원본 (2.1 MB) ↓06항 참조 ↗\n6,627 (12.81%) 무관한 부정행위 제재 (VAC 전용)\n게임 내에서 에임봇/월핵 사용으로 인해 계정이 정지되었지만, 그들의 Steam 거래 및 피싱 활동은 여전히 100% 활발하게 이루어지고 있다.\nVAC 비관련성 분석 ↗보안 연표 ↗\nTier 04 · 위키 훼손 및 2026년 8월 인프라 침해 사건\n증거 자료집에는 내부 개발자 문서 훼손, 커뮤니티 편집자 활동 억압, 보안 경계가 무방비 상태였던 사례 등이 기록되어 있습니다.\n1,200+ 편집자 VDC 위키 충돌 기록\n피싱 링크와 스팸 템플릿을 수정하려던 커뮤니티 편집자들은 자동 필터에 의해 체계적으로 차단당하는 동안, Valve 직원들은 경고를 무시했다.\n러시아 분쟁 보고서 (127 KB) ↗분류 보고서 (66 KB) ↗\n12 TB, 인증 없음 2026년 8월 자산 유출 (CWE-284)\nValve은 수 주 동안 인증 절차 없이 공개된 엔드포인트에 12테라바이트 규모의 내부 코드 및 프로토타입 빌드를 호스팅했습니다.\nValve 무능 관련 자료집 (43 KB) ↗증거 아카이브 ↗\nCEVA 로지스틱스 보안 침해 사건 2026년 8월 고객 개인정보 유출 사건\nValve의 물류 파트너사를 통해 유럽 내 Steam 데크 구매자들의 이름, 주소, 전화번호가 유출되면서 피싱 공격이 잇따르고 있다.\n사고 기록 ↗단속 기록 ↗\n\n샘플링 아티팩트: banned_100k_slice.csv (100,000 계정). 감사 결과: slice_100k_limited_results.csv. 전체 분석 보고서: BANNED_100K_FORENSIC_ANALYSIS.md.\n\n08 — 방법 및 한계\n이 문장이 어떻게 해석되었는지, 그리고 이 문장이 무엇을 주장하지 않는지\n\n세 개의 일반 인구 집단, 하나의 공개 API, 엄격한 통계적 표본 추출.\n\n실행 및 자격 증명\n\nASF 인구 조사, 즉 100,000-계정 SRSWOR 슬라이스 및 SteamRep 교차 검사는 연합의 공개 피싱 및 사기 차단 활동의 일환으로, PhishDestroy명의 참가자가 각자의 Steam개 계정과 웹 API 키를 사용하여 수행했습니다. 이 보고서의 작성자는 Steam 웹 API 키를 보유하고 있지 않으며, 직접 실시간 스캔을 수행하지도 않았습니다. 데이터 집계, 해싱, 검증 및 공개는 참가자들의 출력 결과를 바탕으로 이루어졌습니다.\n\n인구\t어디서 온 것인가\t읽은 내용\nASF 회원들\n10,880,610\tArchiSteamFarm Steam 커뮤니티 그룹의 공개 회원 목록입니다. Steam의 그룹 페이지에는 5,360,499명의 회원(제한되지 않은 회원만)이 표시되며, API 회원 목록에는 제한된 계정을 포함해 총 10,880,610개의 항목이 반환되었습니다. 사용자가 구성 설정에서 기본 그룹 가입 설정을 명시적으로 비활성화하지 않는 한, 이 그룹은 첫 실행 시 자동으로 가입됩니다 (AutoJoinSteamGroup / 통계), 즉 회원 목록에는 상업용 봇 클러스터, 개인 카드 유휴 사용자, 그리고 기본 설정을 그대로 둔 일반 게이머들이 포함되어 있습니다.\tGetPlayerBans 모든 회원에 대해 (차단 표시); GetPlayerSummaries 생성 날짜 및 국가 정보. ID 100개씩 묶어 SteamID64 기준으로 중복 제거되었습니다.\n차단된 계정 10만 개 SRSWOR 슬라이스\n100,000\t1,182,811개의 차단 계정 코퍼스에서 무작위 추출(반복 없음)을 통해 균일하게 추출된 대표 표본 ($P = 8.45\\%$). 유한 모집단 보정을 적용한 결과, 99% 신뢰 수준($Z = 2.576$)에서 오차 범위는 $\\pm 0.39\\%$로 산출됩니다.\t수익화 및 계정 제한 상태 (isLimitedAccount) Steam의 기존 XML 프로필 인터페이스를 통해 감사됨 (?xml=1) 분산 프록시 파이프라인을 통해. 63.06% 유료 상태를 확인합니다.\nSteamRep 사기꾼들\n51,732\tSteamRep 커뮤니티 평판 데이터베이스에서 ‘BANNED’로 표시된 모든 프로필에 대한 100%차 전면 조사를 완료했습니다(총 51,732개 프로필). 표본 추출이나 필터링은 전혀 적용되지 않았습니다.\tISteamUser/GetPlayerBans/v1 모든 51,732 계정에 대해 SteamRep 상태와 교차 분석한 결과, 67.77% 계정은 사기 관련 이용 제한이 전혀 없음을 확인했습니다.\n청구항\n\n오직 경험적 비율과 통계적으로 제한된 추정치만 포함됩니다. 자동화 계정 집단 중 88.97%는 차단되지 않았으며, 차단된 하위 집합은 최근에 집중되어 있습니다(2020년 이후 70%). 100,000개 계정을 대상으로 한 실증적 감사 결과, 차단된 계정 중 63.06%개는 유료 계정(제한 없음)이며, 오차 범위는 수학적으로 입증된 ±0.4% 이내이다. 확인된 사기꾼 51,732명 중 67.77%명은 사기 관련 차단 조치를 받지 않은 상태입니다. 모든 수치는 Valve의 자체 웹 API를 통해 재현 가능합니다.\n\n주장하지 않는 사항\n\nSteam 차단에는 사유 필드가 없으므로, 여기에서 차단된 사례는 특정 원인에 기인한 것이 아닙니다. 그룹 가입 여부는 해당 계정이 자동화된 봇이라는 증거가 아닙니다. ASF는 수동으로 체크를 해제하지 않는 한 기본적으로 그룹 가입을 허용하기 때문에, 회원 구성에는 상업적인 다중 계정 운영자들과 일반 플레이어 및 취미로 게임을 즐기는 이용자들의 개인 계정이 뒤섞여 있습니다. 국적 정보는 본인 신고에 기반하며, SteamRep 표기는 법원의 판결이 아닌 커뮤니티의 판정 결과입니다. 개인의 이름은 공개되지 않습니다.\n\n그것이 왜 중요한가\n\nValve은 동일한 API를 보유하고 있으며, 그 뒤에는 자체 데이터베이스가 있고, 이 스캔으로는 확인할 수 없는 차단 사유도 포함되어 있습니다. 이 시스템은 전체 ID 영역에 대해 이 쿼리를 단 몇 초 만에 실행할 수 있습니다. 특정 번호에 대한 집행 주장을 외부 기관이 검증할 수 있게 해주는 측정 기준은, 이를 완벽하게 재현할 수 있는 유일한 당사자에 의해 단 한 번도 공개된 적이 없습니다. 이는 질문에 구체적인 수치를 제시할 수 있도록 제공된 외부 추정치입니다.\n\n다음 기사: 이 집단이 운영하는 카드 경제 → · 접근 및 도난 방지 → · 전체 자료 →",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam 계정 농장은 얼마나 클까? 직접 집계했습니다."
          },
          {
            "level": 2,
            "id": null,
            "text": "1,000만 개의 계정 중 10개 중 9개는 손도 대지 않은 상태"
          },
          {
            "level": 3,
            "id": null,
            "text": "ASF가 여러분을 위해 이 그룹에 합류합니다"
          },
          {
            "level": 3,
            "id": null,
            "text": "10,880,610 총 등록 건수"
          },
          {
            "level": 3,
            "id": null,
            "text": "88.97% 정리"
          },
          {
            "level": 3,
            "id": null,
            "text": "10,880,610개의 계정 중, Valve을 터치한 계정은 몇 개인가?"
          },
          {
            "level": 3,
            "id": null,
            "text": "이 함대가 존재하기 위해 이미 지불한 대가는 Valve입니다"
          },
          {
            "level": 2,
            "id": null,
            "text": "함대가 주둔하는 곳"
          },
          {
            "level": 3,
            "id": null,
            "text": "신고된 국가별 차단 계정"
          },
          {
            "level": 2,
            "id": null,
            "text": "최근의 미결 건, 기존에 누적된 미결 건이 아님"
          },
          {
            "level": 3,
            "id": null,
            "text": "차단된 계정이 생성된 시점"
          },
          {
            "level": 2,
            "id": null,
            "text": "Valve이 작용할 때는 첫 해 안에 작용한다"
          },
          {
            "level": 3,
            "id": null,
            "text": "계정이 정지 조치를 받았을 당시 개설된 지 얼마나 되었는지"
          },
          {
            "level": 2,
            "id": null,
            "text": "Valve이 작동하더라도 봇은 멈추지 않습니다"
          },
          {
            "level": 3,
            "id": null,
            "text": "차단당한 11%들은 실제로 어떤 이유로 차단당했는가"
          },
          {
            "level": 2,
            "id": null,
            "text": "사기꾼들 Valve, 자, 가보자: 51,732 완전한 인구 조사"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve가 사기 관련 제재를 적용했는지 여부에 따른 확인된 사기꾼 (전체 조사)"
          },
          {
            "level": 4,
            "id": null,
            "text": "두 집단, 하나의 연구 결과"
          },
          {
            "level": 2,
            "id": null,
            "text": "‘0’ 계정 실증 감사: 봇넷은 일회용 무료 계정이 아니다"
          },
          {
            "level": 3,
            "id": null,
            "text": "100,000 편향 없는 슬라이스"
          },
          {
            "level": 3,
            "id": null,
            "text": "오차 범위 < ±0.4%"
          },
          {
            "level": 3,
            "id": null,
            "text": "왜 10만 단위의 수익률은 모두 똑같은가"
          },
          {
            "level": 3,
            "id": null,
            "text": "100,000 차단된 계정: 유료 계정($5+ 스토어 이용 금액) 대 무료 제한 계정"
          },
          {
            "level": 3,
            "id": null,
            "text": "구조적 현실: 산업적 규모의 계정 청산"
          },
          {
            "level": 2,
            "id": null,
            "text": "이 문장이 어떻게 해석되었는지, 그리고 이 문장이 무엇을 주장하지 않는지"
          },
          {
            "level": 3,
            "id": null,
            "text": "청구항"
          },
          {
            "level": 3,
            "id": null,
            "text": "주장하지 않는 사항"
          },
          {
            "level": 3,
            "id": null,
            "text": "그것이 왜 중요한가"
          }
        ],
        "links": [
          "https://help.steampowered.com/en/faqs/view/71D3-35C2-AD96-AA3A",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/asf-ban-census-2026-09-23.json",
          "https://phishdestroy.io/steam_dossier/ko/VALVE_EVIDENCE_PACK/databases/steamrep_steam_bans.csv",
          "https://phishdestroy.io/live-intel/?category=steam",
          "https://phishdestroy.io/steam_dossier/ko/#proxy-bypass-explainer",
          "https://phishdestroy.io/steam_dossier/ko/card_economy.html",
          "https://phishdestroy.io/steam_dossier/ko/VALVE_EVIDENCE_PACK/databases/banned_archiasf_massive.csv",
          "https://phishdestroy.io/steam_dossier/ko/VALVE_EVIDENCE_PACK/databases/slice_100k_limited_results.csv",
          "https://phishdestroy.io/steam_dossier/ko/VALVE_EVIDENCE_PACK/reports/BANNED_100K_FORENSIC_ANALYSIS.md",
          "https://phishdestroy.io/steam_dossier/ko/VALVE_EVIDENCE_PACK/databases/banned_100k_slice.csv",
          "https://phishdestroy.io/steam_dossier/ko/VALVE_EVIDENCE_PACK/reports/STEAM_BANNED_LIMIT_ANALYSIS.md",
          "https://phishdestroy.io/steam_dossier/ko/VALVE_EVIDENCE_PACK/INVESTIGATION_OVERVIEW.md",
          "https://phishdestroy.io/steam_dossier/ko/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/ko/VALVE_EVIDENCE_PACK/reports/STEAMREP_VS_STEAM_AUDIT.md",
          "https://phishdestroy.io/steam_dossier/ko/VALVE_EVIDENCE_PACK/databases/SteamRep_Profiles_BannedCaution_2024.csv",
          "https://phishdestroy.io/steam_dossier/ko/security_timeline.html",
          "https://phishdestroy.io/steam_dossier/ko/VALVE_EVIDENCE_PACK/reports/russian_conflicts_report.json",
          "https://phishdestroy.io/steam_dossier/ko/VALVE_EVIDENCE_PACK/reports/classification_report.json",
          "https://phishdestroy.io/steam_dossier/ko/VALVE_EVIDENCE_PACK/reports/VALVE_INCOMPETENCE_REPORT.md",
          "https://phishdestroy.io/steam_dossier/ko/steam_evidence_archive.html",
          "https://phishdestroy.io/steam_dossier/ko/steam_enforcement_evidence.html",
          "https://phishdestroy.io/steam_dossier/ko/#insider-threat",
          "https://phishdestroy.io/steam_dossier/ko/"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ko/enforcement_audit.content.json",
      "export_json_sha256": "46c1c91c37d207169e44a35aaa5122fc55269574e39f65668e62c501d4a88cfe"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ko/index.html",
      "language": "ko",
      "title": "Steam 도스시에: 규칙, 경로 및 책임",
      "source_url": "https://phishdestroy.io/steam_dossier/ko/index",
      "source_html_sha256": "1b672b46b55f7ac45ba289b5cddde293a1b4d2fab93021c81ef8744a7e4bfe01",
      "exported_at": "2026-09-29T00:21:56.910Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "exhibit-gallery-section",
            "source": "https://phishdestroy.io/steam_dossier/ko/index#exhibit-gallery-section"
          }
        ],
        "raster_images_replaced": 2
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "index.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ko/index.pdf?v=print-20260929-v5",
        "sha256": "ebe762399034ff20e3d88f0fade127656b4732d10cf814b0a5d78a68313459c2",
        "bytes": 945213,
        "pages": 83
      },
      "integrity": {
        "signed_object": "index.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "index.content.json.asc",
        "digest_file": "index.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify index.content.json.asc index.content.json",
          "sha256sum -c index.content.json.sha256"
        ]
      },
      "content": {
        "text": "제1절 — 사건 개요\n규칙. 기록. 풀리지 않은 의문들.\n문맥 및 출처 제한\n\n각각 특정 날짜가 명시된 공개 기록과 연계된 6가지 조사 결과. 세부 항목은 동일한 순서로 구성되어 있습니다: 기술 기록(A부), 규정 및 집행 기록(B부), 법적 체계(C부), 그리고 주요 증거 자료가 수록된 부록 순입니다.\n\n여섯 가지 발견 사항. 각각은 서면 규칙을 특정 날짜의 기록과, 증거를 통해 검증할 수 있는 질문과 연결 짓고 있다.\n\n1. 별도 도메인 인증 호스트 — 44개 경로 · 26개 분할 쌍\n\n실업자 명부에는 다음과 같이 기록되어 있습니다 별도의 등록 가능한 도메인을 통해 인증을 수행하는 44개의 플랫폼. 검증 대기 중인 노선이 5개 더 있으며, RDAP 일정이 확정되기를 기다리고 있습니다. 이 노선들이 승인되면 총 노선 수는 47개로 늘어납니다. 이 노선들은 ‘44’와 연령 표에서 제외됩니다. — 27, 노선별 증거 파일이 공개된 경우 그리고 수동 수집을 통해 추가된 17건은 별도로 나열되어 있습니다. 26개의 필터-분할 쌍 주 도메인은 차단됨 Steam 링크 필터에는 포함되지만, 해당 로그인을 포함하고 있는 프록시는 포함되지 않습니다. 이들은 일회용 도메인이 아닙니다. csgogem.com은 차단된 반면 api.csgem.com, Steam 로그인을 가진 이 호스트는 2014년 3월부터 등록되어 있습니다 — 12년 6개월. Valve은 모든 OpenID 요청에서 해당 호스트명을 수신하며, 자체 로그인 페이지에서 사용자에게 이를 다시 표시합니다. 전체 테이블, 경로별 유효 기간 및 소스 정보는 3절에 나와 있습니다.\n\n경로를 따라가세요 →\n2. 2016년: 해당 제도에 명칭이 정해졌고, 마감 기한이 설정되었다\n\n2016년 7월 13일, Valve은 도박 사이트들이 Steam OpenID와 자동 거래 계정을 어떻게 활용했는지를 공개적으로 설명했으며, 2016년 7월 20일 해당 측 변호사가 발송한 통지서에서는 10일간의 기한을 설정했습니다. 그 이후로 사업자별 집행 기록은 공개된 바 없다. 해당 기한이 제시된 지 10년이 지난 현재, 2026-09-21에서 Link Filter 차단이 발생하지 않았던 별도의 도메인 인증 호스트에서 동일한 명칭의 메커니즘이 사용되고 있다.\n\nWSGC에 보낸 공개 서한 읽기 →\n3. 기기 상호 연관성, 변호인 명의의 서신지에 기재\n\n여기에 재현된 서신에서 Valve의 변호인은 하나의 기기를 여러 계정과 연결하는 기기 수준의 상관관계에 대해 설명했는데, 이는 Steam 지원팀이 이전에 사용자에게 기술적으로 불가능하다고 말했던 기능이다. 여전히 미해결로 남아 있는 의문은 Valve이 어떤 기기 수준 기록을 보유하고 있으며, 어떤 근거로 계정 소유자들의 해당 기록 접근을 거부하고 있는가 하는 점입니다.\n\n각서 읽기 →\n4. 두 가지 접근 대응. 하나는 데이터를 공개하지 않았고, 다른 하나는 유출했다.\n\n2025년 10월: Valve의 변호인은 제15조에 따른 요청에 대해, 해당 내용을 삭제하는 대신 텍스트 위에 빨간색으로 칠해 가린 830페이지 분량의 부록을 제출했는데 — 902,270자 표준 추출 도구를 사용하여, 해당 막대가 숨기려 했던 제3자 식별자까지 포함해 다시 추출해 내십시오. 제15조 제4항이 바로 그 막대가 존재하는 이유입니다. 2026년 9월: 티켓 HT-2YBP-F7JP-D4VB는 3일 만에 ‘계정 데이터’ 셀프 서비스 페이지 링크와 함께 종결되었으나, 데이터는 제공되지 않았고 법적 근거도 명시되지 않았습니다. 게시 시점 기준으로 제12조 제3항에 따른 1개월 기간은 아직 만료되지 않았으며, 이 이의 제기는 내용 자체에 대한 것입니다.\n\n편집 확인 내용 읽어보기 →티켓 기록 보기 →\n5. Steam의 상한선을 넘어선 시장\n\nSteam은 시장 상장을 약 $1,800. 2026년 9월 23일자로 작성된 스냅샷에 따르면, 5개 마켓플레이스에서, 248개의 CS2 품목 카테고리 그 상한선보다 높은 가격을 책정한 업체가 두 곳 이상이며, 각각 독립적으로, 그리고 248명 전원이 Steam에 결석했다; 신품 ‘드래곤 로어’의 가격은 $10,941 5곳 모두에 등록된 389건의 물량 전체를 대상으로 한 수치입니다(9월 20일 스냅샷 기준, 13절에 제시된 CSFloat 전용 수치는 62건의 매물에서 $10,623.95입니다). 해당 가격으로 매도하려면 외부 거래소가 필요하지만, 아이템 이전은 여전히 Steam을 통해 이루어집니다.\n\n가격 및 이체 내역을 확인하세요 →\n6. 규칙은 명확하지만, 감사 추적 기록은 그렇지 않다.\n\n구독자 계약서는 Steam를 개인적·비상업적 용도로만 허용하고, 명시적으로 허용된 경우를 제외하고는 상업적 이용을 금지하며, 스크립트 및 봇 사용을 금지하고, 계정 해지를 허용하고 있습니다. Valve는 2016년에 해당 조항을 도박 사업자에게 적용했습니다. 이와는 별개로, CSFloat의 엔지니어링 계정에 따르면, Valve이 폐쇄되었다. IEconItems_730/GetPlayerItems 2017년에 원본 항목 ID에 대한 공개 접근 권한을 제거했습니다(Valve 변경 내역이 없습니다).\n\n규칙을 네트워크 옆에 배치하세요 →\n2016 / 서면 요청 10일\n2016년 7월 변호사가 도박 사이트에 보낸 통지서의 기한. WSGC에 보내는 공개 서한: 제2항.\n2017 / 공개 감사 기록 ID 접속이 차단되었습니다\nCSFloat는 원래 항목 ID의 손실을 기록합니다.\n변호사 서신 장치 간 상관관계\n도난당한 수십 개의 계정과 연관이 있는 기기 한 대.\n노선 등록부 차단되었지만 여전히 로그인 중입니다\n규칙: Valve의 2016년 성명에 따르면, Steam OpenID를 통해 도박 사업을 운영하는 것이 금지되어 있습니다. 기록: 링크 필터에는 26개의 주요 도메인이 등록되어 있으며, 각 도메인의 Steam 로그인을 담당하는 호스트는 — csgogem.com의 경우 12년 6개월 동안 운영되어 왔다.\n제2절 — 공개 서한\n워싱턴주 도박위원회에 보내는 공개 서한\n\n10일이 10년으로 변해버렸다. 위원회가 2016년에 Valve에 제기한 질문에 대해 사업자별 기록으로 답변이 이루어지지 않았으므로, 본 서한을 통해 해당 사안을 재조사해 줄 것을 요청한다.\n\n공지사항 · 워싱턴주 도박위원회\n\n10일이 10년으로 변했다.레코드를 다시 엽니다.\n\n워싱턴주 도박위원회 귀하:\n\n2016년, 데이비드 트루히요 국장은 Valve 측에 도박 용도로 Steam 스킨이 사용되는 것을 막기 위해 어떤 조치를 취했는지 설명해 줄 것을 요청했다. 당시 위원장 크리스 스턴스와 위원회는 Valve에서 발행한 아이템과 Steam 양도에 기반을 둔 업계와 맞서야 했습니다. 두 사람 모두 이후 위원회 직위에서 물러났습니다. 그들이 Valve에 제기한 질문은 여전히 유효합니다.\n\nValve의 법무 담당자 칼 콰켄부시는 도박 사업자들에게 Steam 계정의 상업적 사용을 중단할 것을 10일 이내에 요구했다. 지난 10월 귀 위원회에 제출한 답변서에서 Valve은 도박을 조장한 사실을 부인하며, 40개 이상의 사이트에 중단 및 철회 요청서를 발송했고 관련 계정을 비활성화했다고 밝혔다. 또한 Steam 거래 및 OpenID 서비스를 유지한 것에 대해서는 해당 서비스가 고객과 게임 개발자에게 이익이 된다는 점을 근거로 정당성을 주장했다. 그것은 지배력을 과시한 행동이었다. 그런 행동에는 순응이 아니라 검증의 대상이 되어야 한다.\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\n저희 평가에 따르면, Valve의 답변은 그들이 선택한 집행 조치가 설명한 네트워크의 규모에 상응한다는 점을 입증하지 못했습니다. 운영자에게 보낸 협박 편지는, 사업 운영을 가능하게 하는 Steam 계정, 거래 인프라 및 인증 경로에 대한 지속적인 차단 조치와는 차원이 다릅니다. 보고된 추정치에 따르면 CS:GO 라운지는 2016년 한 해 동안 베팅 취급액만 $1억을 넘어섰다; 이는 베팅 금액에 대한 외부 추산치일 뿐, Valve 수익은 아니며, 해당 사이트의 원래 피부 베팅 사업은 이후 폐쇄되었다. 이러한 규모로 인해 검증 가능한 단속이 필수적이었다.\n\n오늘, Valve의 가입자 계약서 보관됨 2026-09-21 ↗ 명시적으로 허용된 경우를 제외하고 상업적 이용을 제한하며, 특정 형태의 자동화를 별도로 금지하고 있습니다. 당사의 날짜가 기재된 노선 등록부 OpenID로 선언된 레코드는 외부 서비스의 호스트를 반환합니다; openid.realm 그리고 openid.return_to 필드는 Steam로 전송되는 것이지, Steam로부터 숨겨진 비밀이 아닙니다. 우리의 링크 필터 확인 주 주소에 대해서는 경고가 표시되었으나, 관련 로그인 호스트에 대해서는 경고가 표시되지 않은 사례를 보여줍니다. 필터 결과만으로는 Valve이 로그인을 허용했는지, 또는 특정 봇이 계정 차단 조치를 회피했는지를 입증할 수 없습니다. 이는 홈페이지에 게시된 경고만으로는 접근성에 대한 완전한 해답이 될 수 없다는 점을 입증해 줍니다.\n\n유용하고 합법적인 Steam 거래 및 OpenID 기능의 존재만으로는 금지된 사업자들이 실제로 배제되었는지 여부를 판단할 수 없다. Valve의 자체 규정에는 명시적인 예외 조항이 허용되어 있다. 만약 Valve이 그러한 구분을 근거로 삼는다면, 위원회는 Valve에게 상업적 스킨 사업에 적용되는 승인 절차, 계정 관리 및 집행 기준을 명시하고, 2016년에 주장했던 구체적인 비도박 용도를 제시하도록 요청해야 합니다. 합법적 사용의 단순한 가능성만으로는 문서화된 금지된 사용에 대한 해답이 될 수 없습니다.\n\n우리는 위원회에 2016년 관련 자료를 재검토하고 운영자별 상세 내역을 요청합니다: 10일 사전 통지 후 어떤 Steam 계정과 트레이딩 봇이 비활성화되었는지; 관련 계정이나 리턴 호스트가 모니터링되었는지; 어떤 운영자가 나중에 다시 접속 권한을 회복했는지; 어떤 예외 조치가 허용되었는지; 그리고 Valve이 위원회에 제출한 진술을 뒷받침하는 기록은 무엇인지. 법률이 허용하는 범위 내에서 일반 대중이 열람할 수 있도록 해당 기록을 공개하십시오. 해당 기록을 현재의 경로 및 Valve의 후속 개입 조치와 비교 분석하되, 다음을 포함하여: 2018년의 OPSkins 보관됨 2026-03-07 ↗.\n\n해당 공고는 2016년 7월을 기해 10일간의 기한을 정했으며, 10년이라는 기간이면 해당 조치가 이행되었는지 여부를 확인하기에 충분하다. 위원회는 Valve의 2016년 기록을 오늘날까지 관측 가능한 인프라와 대조하여 검증해야 한다.\n\nSteam 도시에르 조사 · 공개 성명, 2026년 9월 20일\n\n2016년 위원회 공고 ↗ 보관됨 2026-05-20 ↗ · Valve의 2016년 답변 (문서 사본) ↗ · Valve의 2016년 OpenID 성명서 ↗ 보관됨 2026-09-21 ↗ · 현재 Steam 합의 ↗ 보관됨 2026-09-21 ↗ · 2016년 교류 활동 연표: 제11조 →\n\nA부 — 기술 기록 · 제3절\n해당 사이트는 차단되었지만, 로그인 경로는 차단되지 않았습니다.\n\n차단된 주요 도메인 26개. 각 도메인 뒤에 있는 인증 프록시 및 해당 프록시가 활성화된 지 얼마나 되었는지. 이러한 개별 인증 호스트는 단순한 부수적인 보조 주소가 아닙니다. 각각은 Steam에 대한 인증 프록시, 플랫폼과 Valve의 OpenID 엔드포인트 사이에 위치하며, 차단된 도메인이 더 이상 공개적으로 처리할 수 없는 로그인 정보를 전달합니다. Valve은 Link Filter에 ‘정문’을 설치했습니다. 로그인 과정은 계속해서 프록시를 통해 진행되었습니다: csgogem.com은 차단되어 있으며, api.csgem.com 2014년 3월부터 등록되어 있습니다 — 12년 반. 그 기간 동안 해당 호스트는 매일 Valve의 OpenID 엔드포인트로 자체 호스트명을 전송했고, Steam은 이를 로그인 페이지에서 사용자에게 그대로 표시했습니다. Valve는 이 모든 경로가 통과하는 트렁크이며, 해당 경로들을 직접 찾아낼 필요는 없습니다. 이 섹션에서 측정하는 것은 바로 그 점입니다. 경고가 있는지 여부가 아니라, 경고 뒤의 경로가 몇 년 동안 개방 상태를 유지하는지입니다. 등록부에 등재된 44개의 별도 도메인 경로 중 27개 경로에 대해 경로별 증거 파일이 공개되어 있습니다. 아래 표를 참조하십시오. 한 가지 예시를 살펴본 다음, 나머지 모든 경로를 측정해 보십시오.\n\nWhat this means — the Steam Link Filter\n\nValve’s own blocklist for links leaving Steam. Click a listed address inside the client and an interstitial appears instead of the page. It acts on the link that is posted, not on the login a site performs, and it is the only such check that runs inside the Steam client.\n\nSection 3.1 — why it is the only layer →\n\n그림 3.1 — 두 경로를 표시한 그림.\n\n하나의 플랫폼, 하나의 플레이어, 동일한 브라우저에서 전송된 두 개의 요청. Valve의 링크 필터는 이 두 요청 모두를 처리합니다. 링크가 포함된 요청은 차단하고, 로그인 정보가 포함된 요청은 통과시킵니다. 이 섹션에서 측정되는 모든 항목은 하위 경로가 얼마나 오랫동안 열려 있는지를 나타내는 횟수입니다.\n\nThe player\none browser, one session\nrollbit.com\nthe platform's main domain\nrbsnin.com\nseparate authentication host\nLINK FILTER\n✕ BLOCKED\nLINK FILTER\n✓ CLEAN\nsteamcommunity.com\nOpenID endpoint · signs in\nno route\nSteam에 게시된 링크 — 중지됨로그인 요청 — 승인됨2026년 9월 19일과 21일자 수표 사본\n\n두 요청 모두 Valve에게 표시되며, 그중 하나만 처리됩니다. 링크 필터는 Valve개의 목록으로, Valve개의 서비스에 의해 확인됩니다. OpenID 요청은 인증 호스트의 이름을 Valve의 엔드포인트로 전달하며, 엔드포인트는 이를 로그인 페이지에 그대로 표시합니다. 호스트 이름은 어쨌든 요청에 포함되어 있습니다. 차이점은 그 호스트 이름을 바탕으로 어떤 처리가 이루어지느냐에 있습니다.\n\n하나의 플랫폼. 두 가지 다른 경로.ROLLBIT / 저장된 관측 결과\n단계 5 / 5\n\n요청이 Steam에 도달합니다. 관찰된 경로는 Steam의 로그인 양식으로 이어졌습니다. 저자들은 로그인을 완료하지 않았습니다. 메인 도메인 링크를 차단해도 양식으로 이어지는 이 관찰된 경로는 차단되지 않았습니다.\n\n01 링크 필터 확인\n여행지rollbit.com이 플랫폼의 주요 도메인\nSTEAM LINK 필터링크를 확인합니다별도의 목적지 경고 시스템\n저장된 결과링크가 차단되었습니다2026년 9월 19일 및 21일\n02 관측된 로그인 경로\n승강장에서Steam로 로그인플랫폼이 OpenID 요청을 시작합니다.\n별도의 인증 호스트rbsnin.com저장된 검사 항목에 ‘링크 필터’ 블록이 없음\nSTEAM로그인 양식 제공됨요청된 호스트가 Steam의 알림에 표시됩니다.\n원본 채취 기록, 등록일 및 프로토콜 세부 사항을 확인하십시오.\nValve의 집행은 어떤 모습인가\n주 도메인: 차단됨\n사용자\n→\nrollbit.com\n(주 도메인)\n↓\nSTEAM LINK 필터 — 차단됨\n\"링크 차단됨!\" — 잠재적 악성 코드로 신고됨\nrollbit.com은 2026-09-19 및 2026-09-21에 대해 링크 필터 차단을 반환했습니다(인증되지 않은 상태 확인; 원본 HTML 및 SHA-256 저장됨). 확인 가능하고 감사 가능한 기록입니다.\n실제로 일어나는 일 — 인증\n인증 호스트: 차단되지 않음\n사용자\n→\nrollbit.com\n\"Steam로 로그인\"\n↓\n별도의 인증 호스트를 통해 리디렉션:\nrbsnin.com링크 필터: CLEAN\n등록됨 2026-09-18T09:34:52Z (Verisign RDAP)\n↓\nSteam 로그인 페이지 공지 (2026-09-20):\n\"Note that rbsnin.com is not affiliated with Steam or Valve\"\nSteam은 수신한 요청의 openid.realm에서 이 알림을 표시합니다.\n↓\nSteam 별도의 호스트에 제공된 로그인 양식\n저자들은 로그인을 완료하지 않았으며, Steam 양식까지의 진행 과정을 관찰했다.\nValve은 이러한 요청이 있을 때마다 return_to / realm 호스트명을 수신합니다. rbsnin.com은 2026-09-21에 대해 Link Filter 차단 결과를 반환하지 않았습니다.\n요청에 따라\nOpenID 제공자인 Steam은 모든 인증 요청 시 인증 호스트명을 수신합니다. 이 호스트명은 Valve의 자체 서버로 전달되며, openid.return_to 그리고 openid.realm 매개변수.\n사이트에서 발송됨\n스캔을 통해 인증 호스트를 탐지할 수 없습니다. 플랫폼은 각 요청에서 이를 Steam으로 전송합니다. OpenID 2.0 §9.1에 의거하여 return_to 형식상으로는 선택 사항이지만, 이 항목이 없으면 Steam이 로그인 결과를 반환할 수 없으므로, Steam 로그인이 정상적으로 작동하려면 사실상 필수적입니다. Steam는 심지어 사용자에게 호스트명을 표시하기도 합니다(\"<host>는 Steam 또는 Valve과 아무런 관련이 없습니다.\").\n14세\n이는 2026-09-21 점검 시점에 여전히 Steam건의 로그인을 유지하고 있는 가장 오래된 인증 호스트의 운영 기간이며(dota2.net, 등록일 2011-10-29), 가장 최근에 등록된 호스트는 운영된 지 3일 된 호스트입니다(rbsnin.com). “차단된 인증 호스트 0개”라는 수치를 조사 결과로 해석해서는 안 됩니다. 차단된 인증 호스트는 플랫폼의 “Steam으로 로그인” 기능을 완전히 무력화시키므로, 정상적으로 작동하는 로그인 기록으로 구성된 등록 목록에는 차단된 적이 없는 호스트만 포함될 수 있습니다. 의미 있는 수치는 차단 횟수가 아니라, 해당 메인 도메인이 링크 필터에 등록된 채로 남아 있는 동안 그 옆의 로그인이 계속 실행된 기간(년 수)입니다.\n별도 도메인 인증 호스트: 등록일 대 메인 도메인 (30개 경로: 2026-09-21 브라우저 감사에서 확인된 25개 경로에 2026-09-22에 추가된 5개 경로 포함)\n플랫폼\t링크 필터: 메인\t인증 호스트\t링크 필터: 인증 호스트\t인증 호스트 등록됨\t관측 출처\t증거 파일\n롤비트\nrollbit.com · 등록 2014-11-08\n\t차단됨\n2026-09-19, 2026-09-21 · 웨이백 2026-09-21\n\trbsnin.com\tCLEAN\n2026-09-21 · 원본 HTML (Wayback Machine에 저장된 스냅샷 없음)\n\t2026-09-18\n09:34:52Z, Verisign RDAP\n\tSteam 로그인 페이지 공지, 2026-09-20\trollbit.com.json\nSkin.Club\nskin.club · 회원가입 2017-09-04\n\t차단됨\n2026-09-19, 2026-09-21 · 웨이백 2026-09-21\n\tsc-auth.net\tCLEAN\n2026-09-21 · 웨이백 2026-09-21\n\t2019-04-02\nRDAP\n\tSteam 로그인 페이지 공지사항\tskin.club.json\nHowl.GG\nhowl.gg · 회원가입 2017-03-16\n\t차단됨\n2026-09-18, 9월 19일, 9월 21일 · Wayback 2026-09-21\n\thowl.uno\tCLEAN\n2026-09-21 · 웨이백 2026-09-21\n\t2026-08-11\nRDAP\n\t실시간 브라우저 캡처 + 제공된 OpenID URL\thowl.gg.json\n듀얼비츠\nduelbits.com · 등록 2020-02-03\n\t차단됨\n2026-09-21 · 웨이백 2026-09-21\n\tswitchflips.com\tCLEAN\n2026-09-21 · 웨이백 2026-09-21\n\t2020-04-21\nRDAP\n\t제공된 OpenID URL\tduelbits.com.json\nCSGOFast\ncsgofast.com · 등록 2015-03-27\n\t차단됨\n2026-09-19, 2026-09-21 · 웨이백 2026-09-21\n\tsteam-login.authtofast.com\tCLEAN\nauthtofast.com, 2026-09-21 · 웨이백 2026-09-21\n\t2026-06-30\nauthtofast.com, RDAP\n\t실시간 브라우저 캡처 + 제공된 OpenID URL\tcsgofast.com.json\n팜스킨스\nfarmskins.com · 등록 2016-03-23\n\t차단됨\n2026-09-19, 2026-09-21 · 원본 HTML\n\tsteam.kobal.cc\tCLEAN\n2026-09-19, 2026-09-21 · 원본 HTML\n\t2017-01-07\nkobal.cc, RDAP\n\t실시간 브라우저 캡처 + 제공된 OpenID URL\tfarmskins.com.json\n코발트랩\ncobaltlab.tech\n\t차단됨\n2026-09-21 · 원본 HTML\n\tcobaltauth.com\tCLEAN\n2026-09-21 · 원본 HTML\n\t2025-01-07\nRDAP\n\t제공된 OpenID URL\tcobaltlab.tech.json\nCSGO.NET\ncsgo.net · 회원가입 2012-07-22\n\t차단됨\n2026-09-21 · 원본 HTML\n\tcn2.easylot.net\tCLEAN\n2026-09-21 · 원본 HTML\n\t2016-09-03\neasylot.net, RDAP\n\t실시간 브라우저 화면 캡처\tcsgo.net.json\nGGDrop\nggdrop.com\n\t차단됨\n2026-09-21 · 원본 HTML\n\tggauth.com\tCLEAN\n2026-09-21 · 원본 HTML\n\t2023-05-03\nRDAP\n\t제공된 OpenID URL\tggdrop.com.json\nRustChance\nrustchance.com\n\t차단됨\n2026-09-21 · 원본 HTML\n\thgfuihd.com\tCLEAN\n2026-09-21 · 원본 HTML\n\t2019-01-27\nRDAP\n\t제공된 OpenID URL\trustchance.com.json\nSkin.Fans\nskin.fans\n\t차단됨\n2026-09-21 · 원본 HTML\n\tauth.skinfans.com\tCLEAN\n2026-09-21 · 원본 HTML\n\t2018-07-16\nskinfans.com, RDAP\n\t제공된 OpenID URL\tskin.fans.json\n스킨포트\nskinport.com · 등록 2018-09-05\n\t차단됨\n2026-09-21 · 원본 HTML\n\tskinport.app\tCLEAN\n2026-09-21 · 원본 HTML\n\t2020-06-20\nRDAP\n\t실시간 브라우저 캡처 + 제공된 OpenID URL\tskinport.com.json\nSkins.Cash\nskins.cash\n\t차단됨\n2026-09-21 · 원본 HTML\n\tskinscash.live\tCLEAN\n2026-09-21 · 원본 HTML\n\t2019-12-05\nRDAP\n\t제공된 OpenID URL\tskins.cash.json\nTF2Hunt\ntf2hunt.com · 등록 2018-01-13\n\t차단됨\n2026-09-21 · 원본 HTML\n\trstspcl.com\tCLEAN\n2026-09-21 · 원본 HTML\n\t2020-08-08\nRDAP\n\t실시간 브라우저 캡처 + 제공된 OpenID URL\ttf2hunt.com.json\nCSGOGem\ncsgogem.com · 등록 2016-10-16\n\t차단됨\n2026-09-22 · 원본 HTML\n\tapi.csgem.com\ncsgem.com — 별도로 등록 가능한 도메인\n\tCLEAN\n2026-09-22 · 원본 HTML\n\t2014-03-08\ncsgem.com, RDAP — 등록된 도메인 중 가장 오래된 것\n\t수동 수집 + 링크 필터 캡처\tlinkfilter-2026-09-22.json\nGamdom\ngamdom.com · 회원가입 2016-07-29\n\t차단됨\n2026-09-22 · 원본 HTML\n\tlogin.gambldom.com\ngambldom.com — 브랜드 이름과 한 글자 차이\n\tCLEAN\n2026-09-22 · 원본 HTML\n\t2017-09-24\ngambldom.com, RDAP\n\t수동 수집 + 링크 필터 캡처\tlinkfilter-2026-09-22.json\n12CS\n12cs.fail · reg. 2026-03-24\n\t차단됨\n2026-09-22 · 원본 HTML\n\tfail.games\tCLEAN\n2026-09-22 · 원본 HTML\n\t2021-08-24\nfail.games, RDAP\n\t수동 수집 + 링크 필터 캡처\tlinkfilter-2026-09-22.json\nCSGOEmpire\ncsgoempire.com · 등록 2015-06-10\n\tCLEAN\n2026-09-19, 2026-09-21 · 웨이백 2026-09-21\n\tcsgoempirelogin4.com\n1부터 10까지 번호가 매겨진 도메인 중 하나(login1–10)\n\tCLEAN\n2026-09-21 · 웨이백 2026-09-21\n\t2020-07-20\n05:49:17Z, Verisign RDAP\n\t실시간 브라우저 화면 캡처\tcsgoempire.com.json\nCS.MONEY\ncs.money\n\tCLEAN\n2026-09-21 · 원본 HTML\n\tauth.dota.trade\tCLEAN\n2026-09-21 · 원본 HTML\n\t2016-07-15\ndota.trade, RDAP\n\tSteam 로그인 페이지 공지\tcs.money.json\nCSFloat\ncsfloat.com · 등록 2021-07-11\n\tCLEAN\n2026-09-21 · 원본 HTML\n\tcsgofloat.com\n운영자의 이전 브랜드 도메인; 별도의 등록 가능한 도메인으로, 회피의 징후는 아님\n\tCLEAN\n2026-09-21 · 원본 HTML\n\t2015-09-29\nRDAP\n\t실시간 브라우저 화면 캡처\tcsfloat.com.json\nG4Skins\ng4skins.com\n\tCLEAN\n2026-09-21 · 원본 HTML\n\tauth.g4s.to\tCLEAN\n2026-09-21 · 원본 HTML\n\t2021-05-30\ng4s.to, RDAP\n\t제공된 OpenID URL\tg4skins.com.json\nJuice.GG\njuice.gg\n\tCLEAN\n2026-09-21 · 원본 HTML\n\tletmeinjuice.com\tCLEAN\n2026-09-21 · 원본 HTML\n\t2024-04-15\nRDAP\n\t제공된 OpenID URL\tjuice.gg.json\nMarket.CSGO\nmarket.csgo.com\n\tCLEAN\n2026-09-21 · 원본 HTML\n\tdota2.net\tCLEAN\n2026-09-21 · 원본 HTML\n\t2011-10-29\nRDAP\n\t실시간 브라우저 캡처 + 제공된 OpenID URL\tmarket.csgo.com.json\nRust.TM\nrust.tm\n\tCLEAN\n2026-09-21 · 원본 HTML\n\tdota2.net\tCLEAN\n2026-09-21 · 원본 HTML\n\t2011-10-29\nRDAP\n\t제공된 OpenID URL\trust.tm.json\nCSGOLounge\ncsgolounge.com · 등록 2013-08-14\n\tCLEAN\n2026-09-22 · 원본 HTML\n\tdota2.net\n이 인증 호스트의 세 번째 프론트엔드\n\tCLEAN\n2026-09-22 · 원본 HTML\n\t2011-10-29\ndota2.net, RDAP\n\t수동 수집 + 링크 필터 캡처\tlinkfilter-2026-09-22.json\nDota2Lounge\ndota2lounge.com · 등록 2012-08-10\n\tCLEAN\n2026-09-22 · 원본 HTML\n\tdota2.net\n이 인증 호스트의 네 번째 프론트엔드\n\tCLEAN\n2026-09-22 · 원본 HTML\n\t2011-10-29\ndota2.net, RDAP\n\t수동 수집 + 링크 필터 캡처\tlinkfilter-2026-09-22.json\nSkinBaron\nskinbaron.de\n\tCLEAN\n2026-09-21 · 원본 HTML\n\tskinbaron.com\n같은 브랜드, 다른 TLD\n\tCLEAN\n2026-09-21 · 원본 HTML\n\t2015-12-22\nRDAP\n\t제공된 OpenID URL\tskinbaron.de.json\nTF2Royal\ntf2royal.com · 등록 2022-08-17\n\tCLEAN\n2026-09-21 · 원본 HTML\n\ttf2auth.com\tCLEAN\n2026-09-21 · 원본 HTML\n\t2021-07-27\nRDAP\n\t실시간 브라우저 캡처 + 제공된 OpenID URL\ttf2royal.com.json\nTradeit\ntradeit.gg\n\tCLEAN\n2026-09-21 · 원본 HTML\n\tconnect-tradeit.com\tCLEAN\n2026-09-21 · 원본 HTML\n\t2022-02-23\nRDAP\n\t제공된 OpenID URL\ttradeit.gg.json\n업그레이더\nupgrader.pro\n\tCLEAN\n2026-09-21 · 원본 HTML\n\tupgauth.space\tCLEAN\n2026-09-21 · 원본 HTML\n\t2026-08-14\nRDAP\n\t제공된 OpenID URL\tupgrader.pro.json\n출처: steamcommunity.com/linkfilter, 인증되지 않은 GET, 2026-09-21, 53개 호스트, 3초 간격; steam_tos_assets/linkfilter-recheck-2026-09-21.json; 원본 HTML은 steam_tos_assets/linkfilter-raw/. 등록 기간: RDAP, steam_tos_assets/domain-registration.json. · 2026-09-19에 대한 이전 확인 linkfilter-all-results.json · 경로 레코드 입력 auth-route-audit.json · 다음 목록에 포함된 ‘Link Filter’ 페이지(2026-09-21)의 웨이백 머신 스냅샷 wayback-snapshots.json (rbsnin.com에 대한 스냅샷이 존재하지 않으며, 로컬 원본 파일이 유일한 기록입니다).\n\n등록 기간: RDAP (steam_tos_assets/domain-registry/). “제공된 OpenID URL”은 요청 매개변수를 설정할 뿐, 로그인이 완료된 것을 의미하지 않습니다. 저자들은 어떤 플랫폼에서도 로그인을 완료하지 않았습니다. 별도의 도메인 자체가 회피의 증거가 되는 것은 아닙니다. 또한 “차단된 인증 호스트 0개” 역시 독립적인 발견 사항이 아닙니다. 하나라도 차단하면 해당 플랫폼의 Steam 로그인이 중단되므로, 정상적으로 작동하는 로그인 정보로 구성된 레지스터에는 차단된 인증 호스트가 포함될 수 없습니다. 중요한 관찰 사항은 페어링과 그 지속 기간입니다. 즉, 수년 동안 운영되어 온 로그인 도메인 옆에 링크 필터에 주요 도메인이 나란히 있는 경우입니다. 이 표에는 30개의 행이 포함되어 있습니다. 경로별 증거 파일이 있는 27개 경로 중 25개와, 2026-09-22에 추가된 5개 경로로, 이 경로들의 링크 필터 분할 내역은 linkfilter-2026-09-22.json 비록 해당 영역 자체가 수동으로 수집된 것이긴 하지만 — 소스 열의 행에 그렇게 명시되어 있습니다. 표시되지 않은 두 개의 증거 파일 경로는 skinsnipe.com (인증 호스트 pricing.tradeupspy.com, 등록 번호 2020-03-11) 및 csgobig.com (인증 호스트 letmeinbig.com, 등록된 2023-01-20); 둘 다 2026-09-22에 대한 검사에서 ‘BLOCKED main / CLEAN auth host’를 반환했으며, 이는 SHA-256으로 기록되어 linkfilter-2026-09-22c.json, 하지만 해당 배치의 원본 HTML은 게시된 세트에 포함되어 있지 않기 때문에, 이 표의 다른 모든 행에서 확인할 수 있는 별도의 행을 할당받지 못하고 여기에서 명칭만 기재되어 있습니다. 등록부에 수작업으로 수집된 나머지 12개 경로는 다음과 같이 식별되어 있습니다. master_registry.json 아래 realm_src: user.\n\n1차 실증 감사 · 다년간의 기간 범위\n‘큰 그림’의 함정: 링크 필터는 ‘규정 준수 쇼’일 뿐, 방어막은 아니다\n\n데스크톱 브라우저에서는 사용자가 외부 방어 체계의 보호를 받습니다. 구글 세이프 브라우징(Google Safe Browsing)과 마이크로소프트 스마트스크린(Microsoft SmartScreen)은 알려진 피싱 시도를 차단하고, 전체 화면에 빨간색 경고 메시지를 표시합니다. Steam의 ‘Big Picture’ 모드, 게임 내 오버레이(Shift+Tab), 그리고 Steam 덱(SteamOS)에서는 이러한 방어 기능이 제공되지 않습니다. 내장 브라우저는 확장 프로그램을 전혀 지원하지 않으며, 외부 ‘안전한 브라우징’ 엔진을 비활성화하고, 사용자에게 딱 하나의 방어 수단만을 남겨둡니다: Valve's linkfilter 간질성.\n\n네 가지 결과를 비교하려면 옆으로 스크롤하세요 →\n\n92.5%\n2025–2026년 최신형 피싱 무결점으로 통과함 (37/40)\n77.5%\n2023–2024 CS2 시대 피싱 무결점으로 통과 (31/40)\n70.0%\n2021–2022년 레거시 피싱 무결점 통과 (28/40)\n7 / 7\n도박용 주 회선 차단 (양성 대조군)\n다년간의 종단적 감사: 120개의 순수 Steam 피싱 도메인 실시간 테스트 (2026년 9월 24일)\n\nValve의 필터가 단순히 새로운 위협을 탐지하는 데 시간이 오래 걸리는 것인지, 아니면 근본적으로 이를 감지하지 못하는 것인지 확인하기 위해, 우리는 다음을 검토했다. 확인된 120개의 Steam 전용 피싱 도메인 세 개의 역사적 코호트를 대상으로 steamcommunity.com/linkfilter:\n\n1기: 2021–2022 (클래식 거래 제안 및 아이템 드롭) — 70.0% 클린 패스 (28/40). 지역 사회 감시 단체에 의해 목록에 등재된 지 4~5년이 지났음에도 불구하고, 기존 피싱 호스트 10개 중 7개는 여전히 아무런 차단 조치 없이 접속이 가능합니다.\n2기: 2023–2024 (CS2 베타 과대광고 및 허위 지원 항소) — 77.5% 무결점 통과 (31/40). ‘카운터 스트라이크 2’ 출시를 사칭하는 캠페인 및 가짜 커뮤니티 호소문(예: cs2-steam.com, appealsteamcommunity.help) 그대로 통과한다.\n3기: 2025–2026 (서버리스 엣지 배포 및 파비콘 복제) — 92.5% 완벽 통과 (37/40). EdgeOne, Vercel 및 Cloudflare Pages에 배포되는 최신 피싱 킷 (예: steamgifter.online, steam-dp4lt5b8fnez.edgeone.dev) 사실상 아무런 방해 없이 통과한다.\n\n텔레메트리 및 책임 면제, 보호가 아닙니다. 순수한 Steam 피싱을 70%에서 92.5%로 통과시키는데도 링크 필터가 왜 존재할까요? 이는 기업의 법적 책임 면책 조항이자 아웃바운드 클릭 텔레메트리 센서 역할을 합니다. 정중하게 \"Steam을 떠나시겠습니까?\" 클릭 가능한 녹색 ‘다음’ 버튼이 있는 공지문에서, Valve은 Steam 가입자 약관에 따라 법적 책임을 피해자에게 전가합니다(*“사용자가 자발적으로 Steam 외부로 이동했다”*). Valve은 클릭에 대한 텔레메트리 데이터를 수집하지만, 도난을 차단하지는 않습니다.\n\n파비콘 해시 검증: 위협 피드 수집이 전혀 이루어지지 않음. 독립적인 위협 인텔리전스 플랫폼(urlscan.io, Shodan, Censys)은 Steam의 공식 파비콘 해시값을 간단히 검색하여 활성화된 Steam 피싱 키트를 식별합니다 (page.favicon.hash:9f890a9debcdfccc339149a7943be9aff9e4c9203c2fa37d5671a5b2c88503ad NOT domain:*.steampowered.com). 이 기본적인 자동화 검사 기능을 통해 활성 피싱 클러스터를 몇 초 만에 파악할 수 있습니다. Valve은 외부 피드와 연동되지 않으며, 해시 기반 위협 탐지 기능을 실행하지 않고, 규제 당국의 강제 조치(2016년 WSGC 도박 관련 명령)가 있거나 상표로 등록된 도메인 문자열을 보호해야 할 때에만 수동으로 개입합니다.\n\n주요 감사 증거 자료: 120개 영역에 걸친 다년간의 종단적 감사: longitudinal-steam-phishing-audit.json · 100개의 전용 Steam 피싱 샘플: linkfilter-steam-phishing-100.json · 광범위한 사료 감사 (n=250): linkfilter-coverage-2026-09-22.json.\n\nCSGOEmpire — 번호가 매겨진 인증 도메인 10개 일괄 등록\n\n~에 2020-07-20 번호가 매겨진 10개의 도메인, csgoempirelogin1.com ~을 통해 csgoempirelogin10.com,이 등록되었습니다. 10건 모두에 대해 베리사인(Verisign) RDAP 타임스탬프가 기록되어 있습니다: login1 05:49:06Z, login5 05:49:08Z, login2 05:49:11Z, login3 05:49:14Z, login4 05:49:17Z, login6 05:49:20Z, login7 05:49:23Z, login8 05:49:26Z, login9 05:49:28Z — 22초 만에 9개 도메인 — 그리고 7분 뒤인 05:56:03Z에 login10이 등록되었습니다. 이 시간 간격은 단일 등록 기관의 일괄 처리 작업과 일치합니다.\n\n이 패턴은 사전에 지정된 대체 호스트와 일치하며, 오직 login4 실제 OpenID 요청에서 이 현상이 관찰되었습니다. csgoempire.com과 csgoempirelogin4.com은 모두 2026-09-21의 링크 필터에서 ‘CLEAN’을 반환했습니다. CSGOEmpire는 2016년 7월 공지 사항에 대한 언론 보도에 언급된 사이트 목록에 포함되지 않았습니다.\n\n# DNS — 10개 모두 활성화됨 (2026년 9월)\n알겠습니다 csgoempirelogin1.com 172.67.129.43\n알겠습니다 csgoempirelogin2.com 172.67.175.168\n알겠습니다 csgoempirelogin3.com 188.114.96.3\n알겠습니다 csgoempirelogin4.com 188.114.96.11 ← OpenID 트래픽에서\n알겠습니다 csgoempirelogin5.com 172.67.160.194\n알겠습니다 csgoempirelogin6–10.com Cloudflare IP 주소\nNXDOMAIN: csgoempirelogin11.com\n등록된 10개 모두 2020-07-20; 10개 모두 RDAP 타임스탬프 적용됨 (steam_tos_assets/domain-registry/csgoempireloginN.com.rdap.json)\n규제 당국을 위한 결론\n차단된 메인 도메인과 차단되지 않은 인증 호스트가 결합되면 로그인 경로가 열려 있게 되며, 이 상태는 수년 동안 지속됩니다.\n\n메인 도메인의 링크 필터 블록은 검증 가능한 공개 기록입니다. 인증 호스트는 \"Steam로 로그인\" 트래픽을 전달하며, Valve의 OpenID 요청 매개변수에 나타납니다. 2026-09-21과 2026-09-22에 대한 교차 확인 결과, 26개의 필터 분할 쌍에서 메인 도메인은 링크 필터 차단 정보를 반환한 반면, 해당 로그인을 전달하는 프록시는 아무것도 반환하지 않았습니다. 위의 기록은 그 나머지 절반을 보여줍니다. 즉, 이 호스트들은 수명이 짧은 일회용 도메인이 아닙니다. 검증 시점 기준으로 여러 호스트가 10년 이상 등록되어 있었으며, 그 기간 동안 매일 Valve은 자체 요청 매개변수를 통해 해당 호스트명을 수신했습니다. Valve는 사업자별 집행 기록을 공개하지 않았으므로, 공개된 데이터만으로는 이 호스트들에 다른 조치가 적용되었는지 여부를 확인할 수 없습니다.\n\n12년 6개월\ncsgogem.com이 링크 필터에서 차단되었습니다.\n해당 로그인 호스트 api.csgem.com ~해 왔다\n2014-03-08년부터 등록되어 있었으나 현재는 그렇지 않습니다.\n알기 쉬운 요약 — 규제 당국 및 법원용 (펼치기)\n알기 쉬운 요약 — 규제 당국용\n배경: Steam이란 무엇이며, 왜 이 맥락에서 중요한가\n\nSteam은 Valve Corporation(미국 워싱턴주 벨뷰)이 운영하는 소프트웨어 플랫폼입니다. Steam는 디지털 신원 확인 서비스 제공업체로 기능합니다. 인터넷상의 도박 및 게임 웹사이트들은 “Steam으로 로그인”이라는 시스템을 사용하는데, 이는 웹사이트가 방문자가 실제 Steam 계정을 보유하고 있는지 확인할 수 있게 해주는 버튼입니다. 이는 “Google로 로그인”이나 정부에서 발급한 신분증 확인과 유사합니다. 웹사이트가 사용자를 Steam의 서버로 연결하면, Steam이 사용자의 신원을 확인하고, Steam이 사용자를 다시 웹사이트로 돌려보냅니다. Valve이 인증 시스템을 운영합니다. “Steam로 로그인”을 통해 이루어지는 모든 로그인 과정은 Valve의 자체 서버를 거칩니다.\n\nValve의 기능: 도메인 차단\n\n2016년 7월, 스킨 도박에 대한 언론과 법적 압박이 이어지자, Valve의 변호인은 약 23개의 특정 도박 사이트(2016년 7월 21일자 언론 보도 기준)에 통지서를 발송했으며; 2016년 10월, Valve은 워싱턴주 도박 위원회에 40개 이상의 사이트에 연락을 취했다고 밝혔다. 일부 도박 도메인은 Steam 링크 필터 — 이 목록에 포함된 링크가 Steam 내부(채팅, 프로필 페이지, 스토어 등)에 게시될 경우 경고 페이지가 표시되도록 하는 목록: \"링크 차단됨!\" 링크 필터는 Valve 외부에서 그 효과를 관찰할 수 있는 유일한 강제 조치입니다.\n\n예시: 다음 링크: rollbit.com Steam를 선택하면 링크 필터 경고 페이지가 표시됩니다(2026-09-19와 2026-09-21 선택 시). 이론상으로는 도박 사이트가 차단됩니다.\n프록시 도메인이란 무엇인가\n\nA 별도 도메인 인증 호스트는 인증 프록시입니다.: 동일한 운영자가 “Steam로 로그인” 단계를 수행하기 위한 유일한 목적으로, 사용자와 Steam 사이에 배치한, 별도의 등록 가능한 도메인에 속한 두 번째 웹사이트 주소입니다. 이는 로그인 과정을 프록시 처리합니다. 사용자는 플랫폼에 로그인하고 있다고 믿지만, Valve에 도달하는 요청에는 플랫폼의 호스트명이 아닌 프록시의 호스트명이 포함됩니다. 이 사이트는 일반적으로 도박 사이트와 공개적으로 드러나는 연관성이 없으며, Steam이 사용자의 신원을 확인한 후 사용자를 다시 안내하는 주소입니다.\n\n예시: Rollbit은 다음 조건에 따라 운영됩니다. rollbit.com, 이는 링크 필터에 의해 차단됩니다. Steam 인증의 경우, 2026-09-20에서 관찰된 트래픽은 별도의 주소를 사용했습니다: rbsnin.com, 등록 번호 2026-09-18. 이 주소에서 반환된 결과는 링크 필터 블록 없음 2026-09-21에. 해당 도박 사이트는 계속 운영되었으며, Steam 로그인 절차는 차단되지 않은 호스트를 통해 진행되었다.\n중요한 점: 모든 요청에서 인증 호스트가 Steam으로 전송됨\n\nValve는 사용 중인 인증 호스트를 파악하기 위해 스캔이나 크롤링을 할 필요가 없습니다. Steam은 OpenID 신원 제공자 이러한 사이트의 경우, “Steam로 로그인”을 클릭할 때마다 Valve의 자체 서버로 GET 요청이 전송되며, 이 요청에는 인증 호스트명이 일반 텍스트로 포함되어 있습니다. OpenID 2.0 §9.1에 따르면, return_to 이 필드는 공식적으로는 선택 사항이지만, 이 필드가 없으면 Steam이 로그인 결과를 반환할 수 없으므로, Steam 로그인이 정상적으로 작동하려면 사실상 필수입니다. Steam 자체는 로그인 페이지에 호스트 이름을 표시합니다(\"<host>는 Steam이나 Valve과 아무런 관련이 없습니다.\").\n\n— 요청의 형식 Steam 수신 (2026-09-20에서 Rollbit에 대해 관측된 호스트): —\nGET steamcommunity.com/openid/login\n&openid.mode=checkid_setup\n&openid.return_to=https://rbsnin.com/… ← 사실상 필수; Valve의 로그에 기록됨\n&openid.realm=https://rbsnin.com ← 사이트 측에서 직접 명시한 내용; Steam의 로그인 페이지에 표시됨\n해당 사이트에서 서버 간 인증(check_authentication)을 사용하는 경우, Valve의 로그에는 해당 플랫폼의 서버 IP와 호스팅 네트워크 정보도 기록됩니다.\n\n이 요청에서 호스트명을 추출하는 것은 표준적인 작업입니다. 어떤 호스트에 대해 조치가 취해졌고, 어떤 호스트에는 취해지지 않았으며, 어떤 기준에 따라 결정되었는지를 기록한 집행 기록은 Valve의 인프라 내에만 존재하며, 공개된 바 없습니다.\n\n이것이 무엇을 증명하는가\n\n1. 링크 필터 블록은 로그인이 아닌 링크에 대해 작동합니다. 주 도메인을 차단하기 (예: rollbit.com)는 Steam 내부의 링크를 클릭하는 사용자에게 경고 메시지를 표시합니다. 이는 사이트의 운영을 중단시키지 않으며, 다른 주소를 통해 Valve의 자체 OpenID 서비스를 이용하는 것도 막지 않습니다.\n\n2. 테스트 대상인 인증 호스트들은 차단되지 않았습니다. 위의 표는 2011년부터 2026년 9월 사이에 등록된 별도 도메인 인증 호스트를 보여주고 있으며, 그중 일부는 2016년 7월 공지 이후 수년이 지난 시점에도 등록된 것들이다. 26쌍의 경우, 메인 도메인은 Link Filter 차단 응답을 반환한 반면, 해당 로그인을 전달하는 프록시는 차단 응답을 반환하지 않았습니다(인증되지 않은 확인, 2026-09-21 및 2026-09-22; 원본 응답 및 SHA-256 저장됨). 해당 프록시는 Valve가 이를 거부한 날부터 작동이 중단되었으므로, 여기서는 목록에 등재되었는지 여부가 아니라 얼마나 오랫동안 운영되었는지를 측정 기준으로 삼습니다. Valve은 자체 OpenID 요청에서 이러한 호스트명을 수신합니다. Valve이 사업자별 적용 기록을 공개하지 않았기 때문에, 공개 데이터만으로는 링크 필터 이외의 다른 조치가 적용되었는지 여부를 판단할 수 없습니다.\n\n3. 해당 사이트들은 계속해서 Valve의 인프라를 통해 인증을 진행했다. \"Steam로 로그인\"은 Valve의 서비스이며, 이를 통한 모든 인증은 Valve가 수신하고 처리하는 요청입니다. Valve 또한 케이스 키를 통해 수익을 창출하며, Steam 커뮤니티 마켓은 마켓 내에서 완료된 거래(외부 거래는 제외)에 대해 총 약 15%의 수수료를 부과합니다. 링크 필터 작업은 공개 기록을 생성했을 뿐, 인증 관계를 중단시키지는 않았습니다.\n\n차단이 효과가 있었을까?\n\n비유하자면, 2023년에 무료 도메인 등록 업체인 Freenom이 사업을 중단했을 때, 해당 업체의 도메인에 의존하던 피싱 공격이 중단되었습니다. 운영의 연속성은 인프라의 안정성에 달려 있습니다.\n\n여기에도 같은 논리가 적용됩니다. Steam의 OpenID 처리 과정에서 인증 호스트가 거부될 경우, 새로운 호스트가 등록되고 인증서가 발급되며 DNS가 전파될 때까지 플랫폼의 “Steam로 로그인” 기능이 작동하지 않게 됩니다. 이 기간 동안에는 서비스 중단이 발생합니다.\n\n회전이 있다고 해서 블로킹이 무의미해지는 것은 아닙니다. 이로 인해 차단 작업에 운영 비용이 발생합니다. 새로운 호스트는 처음 사용 시 Valve의 요청 로그에 나타나기 때문에, 응답 속도는 그 첫 사용 시의 속도와 동일하게 유지될 수 있습니다.\n\n일괄 등록 자체가 하나의 신호입니다: CSGOEmpire의 login1–login10은 2020-07-20에 등록되었으며, 그중 9개는 22초 이내에 등록되었습니다(Verisign RDAP). 응답이 도메인별로 이루어질 필요는 없으며, 하나의 등록기관 세션에서 나온 연속된 일련의 응답도 하나의 시리즈로 간주될 수 있습니다.\n\n공개 기록상, 호스트 로테이션으로 인해 무력화된 인증 호스트 차단 시도는 나타나지 않습니다.\n이 자료에 따르면, 각 로그인을 처리하는 프록시는 계속 가동되는 동안 주요 도메인이 차단된 것으로 나타났으며 — 2026-09-22 기준 26쌍, 등록된 인증 호스트 중 가장 오래된 것은 12년 6개월 전 — 어떤 운영자에 대해서도 공개된 강제 조치 기록은 없는 것으로 확인되었습니다.\n따라서 규제 당국이 고려해야 할 질문은 다음과 같습니다. Valve이 자체 OpenID 요청을 통해 수신한 인증 호스트에 대해 어떤 집행 조치를 적용했는지, 혹시 적용한 조치가 있다면 어떤 것인지?\nValve은 무엇을 했는가 — 그리고 왜 Auth 경로를 중단시키지 않았는가\n\n아래 표는 공개적으로 기록된 각 Valve 조치에 대해, 해당 조치가 OpenID 인증 진입점에 영향을 미쳤는지 여부를 정리한 것입니다. 이 결과는 “Valve이 아무 조치도 취하지 않았다”는 것이 아니라, 공개적으로 기록된 조치 중 어느 것도 도박 플랫폼 로그인이 Valve의 서버를 통과하는 지점에 영향을 미치지 않았다는 것입니다.\n\n날짜\tValve 조치\t영향을 받은 openid.return_to 경로?\n2016년 7월\t2016년 7월 13일 공개 성명; ~23곳의 명시된 사이트에 대한 변호사의 통지서 (언론 보도, 2016년 7월 21일); Valve가 2016년 10월 WSGC에 보낸 서한에 따라 40곳 이상의 사이트에 연락함\t아닙니다. 알림 및 링크 필터는 연산자와 링크에 적용되며, OpenID 요청 경로는 변경되지 않았습니다.\n2017년\t~의 폐쇄 IEconItems_730/GetPlayerItems (CSFloat의 엔지니어링 계정에 따르면; Valve 변경 내역은 발견되지 않음)\t아니요. 영향을 받은 항목은 공개 내역 표시 여부입니다. OpenID 인증 기능은 변경되지 않았습니다.\n2018-03-29\tCS:GO 7일 거래 잠금 기능 발표 (blog.counter-strike.net)\t아니요. 항목 이동 속도가 느려졌을 뿐, OpenID 요청 경로는 변경되지 않았습니다.\n2022-05-10\t공개 웹 API에서 거래 취소 엔드포인트가 제거되었습니다(사용자가 발견함; 변경 내역 없음 — node-steam-tradeoffer-manager #325)\t아니요. 오퍼-스왑 툴링은 종료되었으며, OpenID 인증은 변경되지 않았습니다.\n2023-12-04\tAPI 키 생성 시 이제 모바일 인증이 필요합니다 (steamcommunity.com/dev/apikey; 변경 내역 없음).\t아니요. 주요 엔드포인트는 보호되었으며, 여기에 기재된 인증 호스트들은 영향을 받지 않았습니다.\n2026-09-19 / 9월 21일\tSteam 저자들이 관찰한 링크 필터 상태\t저장된 2026-09-21 재검사에서 14개의 주요 도메인이 차단 결과를 반환했으며 — 2026-09-22에 따라 레지스터에 26개의 분할 쌍이 기록되었으나 — 각 로그인을 처리하는 프록시는 계속 실행되었습니다.\n출처: Valve 2016년 7월 13일자 성명 (store.steampowered.com/oldnews/22883, 보관됨 2026-09-21) · 2017년 폐쇄에 대한 CSFloat 엔지니어링 보고서 (blog.csfloat.com, 보관됨 2026-09-21) · 링크 필터 상태: linkfilter-recheck-2026-09-21.json.\n이 결과는 Valve가 다음과 같은 이유로 OpenID 요청을 거부한 사례가 단 한 건이라도 발표된다면 반증될 수 있다. openid.return_to 도박 인증 호스트를 가리켰습니다. 공개 기록상 해당 인스턴스는 발견되지 않았습니다.\n가장 최근에 등록된 두 개의 auth-host\nhowl.uno2026-08-11 (RDAP)에 등록되었으며, 이는 2026-09-21보다 41일 앞선 시점입니다. howl.gg는 2026-09-18, 2026-09-19 및 2026-09-21에서 링크 필터 차단 결과를 반환했습니다. 차단이 등록보다 먼저 발생했는지는 확인되지 않았습니다.\nrbsnin.com2026-09-18T09:34:52Z에 등록되었으며(Verisign RDAP), 2026-09-20에 Steam의 자체 로그인 페이지 공지를 통해 Rollbit의 Steam 로그인 흐름에서 확인되었습니다. rollbit.com은 2026-09-19와 2026-09-21에서 링크 필터 차단 메시지를 반환한 반면, rbsnin.com은 그렇지 않았습니다.\n위 표에 있는 각 호스트는 Valve의 인증 서버로 다음과 같이 전송됩니다. openid.realm 로그인을 시도할 때마다.\n경로별 전체 데이터 및 링크 필터 판정 결과: 위 3절의 표; 원본 결과는 linkfilter-recheck-2026-09-21.json 그리고 linkfilter-all-results.json.\n방법론 — 경로 및 링크 필터 카운트 산정 방식\n1. 도메인 확인\n2026-09-21 감사에서는 요청된 189개 플랫폼 중 78개를 해결했습니다: 33개는 자체 호스트명으로, 20개는 자체 하위 도메인으로 인증되며 — 이는 직접 인증에 해당하며, 이들 중 어느 것도 별도 도메인 경로로 집계되지 않습니다. 나머지 25 별도의 등록 가능한 도메인을 통해 인증하기, 24개의 서로 다른 호스트명을 통해 (dota2.net은 market.csgo.com 및 rust.tm과 공유됨): 10개는 실시간 브라우저 캡처로 확인되었고, 3개는 Steam의 로그인 페이지 공지사항을 통해, 12개는 제공된 OpenID URL을 통해 확인되었습니다. 실시간 등록 내역 (master_registry.json, 2026-09-22)는 이를 다음과 같이 확장합니다. 44개의 별도 도메인 경로: 26개의 필터 분할 쌍(메인 도메인 BLOCKED, 인증 호스트 CLEAN)과 메인 도메인 분할이 없는 18개의 추가 경로. 총 44개 중, 27. 노선별 증거 파일을 보관한다; 나머지 17개는 수작업으로 수집되었으며 표시가 되어 있습니다 realm_src: user 등록부에. 이 17개 중 5개(csgogem.com, gamdom.com, 12cs.fail, csgolounge.com, dota2lounge.com)는 2026-09-22에 추가되었으며, 두 호스트 모두에 대한 링크 필터 캡처(원시 HTML + SHA-256)가 linkfilter-2026-09-22.json), 따라서 영역이 수동으로 수집된 것이더라도 분할 자체는 입증되며, 이들은 증거 파일 경로와 함께 위 표에 표시되어 있습니다. tfauth.com (tf2easy.com)은 2026-09-22에 등록부에서 삭제되었습니다. arena.fragnet.net과 마찬가지로, 이 도메인을 원래 사이트와 연결해 줄 수 있는 검증 가능한 정보는 없습니다. 해당 카운트는 공개된 자료를 통해 다시 산출할 수 있습니다. auth-route-audit.json (2026-09-21 연속)은 하나의 규칙에 따라 적용됩니다. 즉, 플랫폼의 관측된 Steam OpenID 호스트가 플랫폼 자체와는 다른 등록 가능한 도메인에 위치할 때만 해당 플랫폼이 집계됩니다.\n2. Steam 링크 필터 상태\n다음 방법을 통해 테스트됨 steamcommunity.com/linkfilter/?url=https://[domain], 인증되지 않은 상태로 2026-09-19 및 2026-09-21에서; SHA-256으로 저장된 원시 HTML. 메인 도메인과 인증 호스트에 대한 상태가 별도로 기록됨. 분류기는 일반적인 “Steam를 떠나고 있습니다” 알림(CLEAN)과 “링크 차단됨! ... 잠재적 악성 코드로 표시됨” 페이지(BLOCKED)를 구분하며, google.com 대조군을 통해 두 가지가 혼동되지 않음을 확인합니다. 이 테스트의 초기 인증 변형은 해당 대조군을 포함한 모든 도메인에 대해 “차단됨”을 반환한 후 폐기되었으며, 이는 실제 결과가 아닌 프로브 스크립트 내의 유효하지 않은 세션 쿠키로 인한 것으로 확인되었습니다.\n3. 인증 호스트 관찰\n실시간 캡처: Playwright 브라우저가 각 플랫폼의 로그인 절차로 이동한 후 openid.return_to 호스트명은 가로챈 요청에서 읽어왔습니다. 로그인 페이지 공지: 호스트명은 Steam의 자체 \"에서 읽어왔습니다.<host>는 Steam 또는 Valve과 아무런 관련이 없습니다.\" 텍스트는 Steam에 의해 다음과 같이 변환됩니다. openid.realm (rbsnin.com, sc-auth.net, auth.dota.trade). 제공된 URL: 저자들에게 제공된 a Steam 로그인 양식 URL; 이는 요청 매개변수를 정의한 것이지, 로그인이 완료된 것은 아닙니다. 어떤 플랫폼에서도 로그인이 완료되지 않았습니다.\n4. 다루지 못한 부분 — 해결되지 않은 문제와 그 중요성\n189개 플랫폼 중, 110번 노선에는 정해진 경로가 없었다 그리고 하나는 해당 사항이 아니었습니다 (189 − 78 − 1). 이 자료집에는 이들 중 어느 것도 포함되지 않았습니다. 감사 파일에서 확인된 110건의 세부 내역은 다음과 같습니다: 봇 차단 22건, 타임아웃 14건, HTTP 오류 12건, 탐색 오류 10건 — 관찰자가 로그인 절차로 진입하지 못했으나, 이들 사이트 대부분은 일반 브라우저에서는 정상적으로 열립니다; 20개 사이트는 랜딩 페이지에 Steam 로그인 제어 기능이 없었으며, 16개 사이트는 호스트로 확인되지 않는 로그인 흐름에 도달했고, 11개 도메인은 DNS에서 확인되지 않았으며, 5개 사이트는 동의 벽에서 중단되었습니다. 아래 표는 동일한 110건을 다르게 분류하고 있습니다. DNS에서 호스트를 확인할 수 없었던 11건은 다음과 같이 별도로 나열되어 있습니다. 제거됨 · NXDOMAIN, 그리고 해당되지 않는 항목 하나가 나머지 항목들과 합류합니다. 189개의 플랫폼을 감사한 결과, 두 리졸버 모두에서 명확한 NXDOMAIN 오류가 확인되어 11개가 제거되었으며, 178명 유지 (platform-audit.json, platforms-removed.json). 원장(ledger)이 명명 패턴을 통해 추측한 137개의 인증 도메인은 2026-09-19의 데이터에서 삭제되었습니다. 이는 관측된 적이 없으므로 증거가 될 수 없습니다. 제시된 OpenID URL을 통해 세 가지 추측이 반박되었습니다. buff.163.com, gamerpay.gg 및 csgoluck.com은 buffauthproxy.163.com, gamerpayredirect.io 및 lucklogin.app이라는 추측과 달리 직접 인증을 수행합니다. 삭제된 항목은 공개된 감사 파일에 나열되어 있습니다.\n25는 하한치이지 상한치가 아닙니다. 해결된 78개 플랫폼 중 25개는 별도의 도메인을 사용했고, 53개는 그렇지 않았습니다. 이 비율을 바탕으로 해결되지 않은 110개에 대해 어떠한 가정도 하지 않았으며, 이 자료집 어디에도 이를 바탕으로 한 예측은 포함되어 있지 않습니다. 각 플랫폼은 사용자가 사이트를 열고 “Steam으로 로그인”을 클릭하기만 하면 해결될 수 있습니다. 인증 호스트명은 로드되는 Steam 페이지의 URL에 포함되어 있습니다.\n이 섹션의 요점은 다음과 같습니다: 독립적인 관찰자가 189개의 플랫폼을 파악하려면 브라우저와 상당한 인내심이 필요하며, 그 결과 78개를 파악했습니다. Valve의 경우 데이터베이스 쿼리가 필요합니다. “Steam로 로그인”을 사용하는 모든 플랫폼(파악된 플랫폼과 파악되지 않은 플랫폼 모두)은 openid.realm 매번 로그인할 때마다 Valve의 인증 엔드포인트로 연결됩니다. 이 표에 공백이 있는 이유는 작성자들이 시스템 외부에 있기 때문입니다. Valve의 경우에는 이러한 공백이 없습니다.\n관측된 프록시 호스트명은 다음과 같습니다. auth-route-audit.json. RDAP(Verisign) / IP2WHOIS의 도메인 등록 날짜. 링크 필터 결과: linkfilter-all-results.json.\n이해를 돕기 위한 비유\n\n면허를 취득한 택시 회사가 규제 당국으로부터 등록된 ‘메인 스트리트’ 주소에서는 더 이상 영업할 수 없다는 통보를 받았다고 가정해 봅시다. 이 회사는 메인 스트리트에 있던 간판을 철거합니다. 이 간판 철거 사실은 기록으로 남습니다. 그러나 같은 회사가 ‘사이드 스트리트’에 다른 이름으로 등록된 사업장을 개설하고, 그곳에서 영업을 계속합니다. 규제 당국은 두 주소에서 출발하는 모든 택시가 이용하는 중앙 배차 시스템을 운영합니다. 모든 승차 요청에는 “사이드 스트리트에서 픽업”이라고 표시됩니다. 규제 당국은 사이드 스트리트의 면허를 취소한 적이 없습니다. 메인 스트리트 표지판을 철거한 것이 유일한 단속 조치였다. 택시 회사는 운영을 중단한 적이 없다.\n\nA부 — 기술 기록 · 제3.1절\nSteam 내부에서는 Valve의 리스트가 유일한 리스트입니다.\n\nSteam 클라이언트, 게임 내 오버레이 또는 빅 픽처 모드에서 클릭한 링크는 사용자의 브라우저에서 열리지 않습니다. 해당 링크는 Steam 자체에 내장된 브라우저 내에서 렌더링되며, 이 곳에는 일반 브라우저에서 적용되는 경고 레이어가 존재하지 않습니다. 링크 필터는 여러 안전 장치 중 하나가 아닙니다. 바로 그 자체입니다.\n\n일반 브라우저에서는세 개의 독립적인 계층\nGoogle 안전 브라우징구글의 피싱 및 악성코드 목록에 등재된 호스트에 대해 표시되는 전체 화면 삽입 광고로, 방문 중인 사이트와 무관하게 지속적으로 업데이트됩니다.\n바이러스 백신 브라우저 확장 프로그램대부분의 소비자용 엔드포인트 제품에는 목적지를 해당 공급업체의 평판 목록과 대조하여 확인하는 브라우저 애드온이 포함되어 있습니다.\n엔드포인트 HTTPS 검사제품이 TLS 검사를 수행하는 경우, 페이지 콘텐츠는 사용자에게 전달되기 전에 스캔됩니다.\nSteam 클라이언트, 오버레이 및 빅 픽처한 겹\nGoogle 안전 검색없음. 이 확인 작업에는 임베디드 크로미움 빌드에는 제공되지 않는 Google API 키가 필요합니다. 해당 키가 없는 경우, 크로미움의 설계 문서에 따르면 ‘안전한 브라우징’ 핸들러가 요청 체인에 전혀 추가되지 않는다고 명시되어 있습니다.\n바이러스 백신 브라우저 확장 프로그램없음. Steam의 렌더러는 사용자의 브라우저가 아니며, 사용자의 브라우저 프로필에서 확장 기능을 불러오지 않으므로 해당 페이지에서 실행되는 애드온이 없습니다.\n엔드포인트 HTTPS 검사제품에 따라 다릅니다. 트래픽은 인식된 브라우저가 아닌 코드 서명이 된 Valve 프로세스 내에서 종료되며, 일부 엔드포인트 제품은 서명된 애플리케이션에 대해 TLS 검사를 면제합니다.\nSteam 링크 필터Valve의 자체 차단 목록으로, 링크가 Steam 생태계를 벗어날 때 참조됩니다. 이것이 실행되는 유일한 확인 절차이며, 위 표에는 이 섹션에 설명된 인증 호스트에 대해 이 절차가 반환한 결과가 기록되어 있습니다.\n독자라면 누구나 직접 해볼 수 있는 테스트이며, 테스트에 실패하면 그 결론은 무효가 된다\n\nGoogle이 공개한 ‘안전한 인터넷 사용’ 테스트 URL 중 하나를 열어보세요 (testsafebrowsing.appspot.com) 크롬에서: 전체 화면을 덮는 빨간색 삽입 광고가 나타납니다. Steam 채팅 메시지에서 동일한 URL을 열어 Steam 클라이언트나 오버레이에서 렌더링되도록 하면, 삽입 광고가 나타나지 않습니다. Steam이 표시할 수 있는 유일한 경고는 자체 링크 필터 페이지뿐이며, 이는 Valve의 목록에 포함된 호스트에 대해서만 표시됩니다.\n\nValve의 버그 바운티 실적이 한 층은 이미 Valve의 앨범에서 다뤄진 적이 있습니다.\n\n링크 필터가 클라이언트 내에서 실행되는 유일한 검사라면, 이 필터 자체의 오류 모드는 사소한 문제가 아닙니다. Valve의 HackerOne 프로그램에 제출된 두 건의 보고서는 모두 접수되고 해결되었으며, 이후 내용이 모두 공개되었습니다:\n\n#291750보관됨 2025-11-16 ↗오픈 리디렉트 · medium\n링크 필터 보호 기능 우회\n\n2017년 11월 19일 보고, 해결됨, 2018년 5월 9일 공개됨. 보고서 자체의 개념 증명: 표의문자 마침표를 대체함 。 (%E3%80%82) 호스트 이름의 점(.)에 대해서는 — 차단을 우회할 수 있습니다. 이 섹션에서 다루고 있는 삽입 광고가 표시되지 않았습니다.\n\n#1079561보관됨 2026-09-24 ↗정보 공개 · 높음\n'Big Picture' 웹 브라우저에서 로그인 쿠키가 유출되고 민감한 정보가 노출됩니다(계정 탈취로 이어질 수 있음).\n\n2021년 1월 15일 보고되었으며, 해결되었고, 2021년 9월 21일 공개되었습니다. Valve의 자체 심각도 등급은 ‘높음’이며, 제목에 그 결과가 명시되어 있습니다. 공개된 기록에는 제목, 등급 및 날짜가 포함되어 있습니다. 기술적 설명은 공개된 내용에 포함되어 있지 않으므로, 여기서는 그 내용을 더 이상 인용하지 않습니다.\n\n두 보고서 중 어느 쪽에서도 밝혀진 사실이 아닌, 저자들의 해석: 두 가지는 같은 문 양쪽에 자리 잡고 있다. 하나는 목적지가 열리기 전에 경고가 나타나지 않는 것이고, 다른 하나는 페이지 내부가 열리자마자 세션이 클라이언트를 떠나는 것이다. 세션이 도용된 후 이어지는 일련의 과정 — 확인 요청 없이 키가 등록되고, 실제 거래가 취소되며, 복제본으로 중복 거래가 전송되는 것 — 은 다음과 같이 제시된 패턴이다. 제5절 ~에 제8조. 두 보고서 모두 종결되었으며, 어느 것도 현재 활성 취약점으로 분류되지 않습니다. 이 보고서들이 입증하는 사실은 범위가 더 좁지만 충분합니다. 즉, 유일하게 남아 있는 보안 계층에 대해 Valve의 자체 기록상 우회된 사례가 문서화되어 있다는 점입니다.\n\n출처: 각 보고서에 대한 HackerOne 공개 기록. 2026-09-22에서 추출 — HackerOne이 공개한 번호, 제목, 팀, 취약점, 심각도, 보고일, 공개일 및 상태. 추출 기록: hackerone-reports.json. 여기에는 현상금 액수가 명시되어 있지 않으며, 검색된 공개 기록에도 그 내용이 나타나지 않습니다.\n\n현장 관찰 · PhishDestroy일반적으로 캠페인을 종료시키는 탐지 결과들이 이번에는 캠페인을 종료시키지 못했습니다\n\n우리는 피싱 호스트들이 다음과 같은 내용을 전달하면서 계속해서 트래픽을 끌어오는 것을 지켜보았다. 20건 이상의 공급업체 탐지. 웹이나 이메일을 통해 전달되는 경우, 그 상태의 캠페인은 며칠 만에 무산됩니다. 브라우저와 안티바이러스 프로그램이 모두 해당 판정에 따라 조치를 취하기 때문입니다. Steam 내에서는 그렇지 않습니다. 판정은 처음부터 존재했습니다. 클라이언트 측에서는 그 어떤 요청도 하지 않았습니다.\n\n바이러스 백신 프로그램이 설치된 미성년자에게 이것이 의미하는 바는 무엇일까요?\n\n그는 어떤 경고도 무시하지 않으며, 아무것도 비활성화하지 않는다. Steam 내부로 메시지가 도착한다 — 무료 나이프, 친구 팀에 대한 투표 — 그리고 Steam 내부에서 페이지가 열린다. 그는 브라우저를 절대 열지 않기 때문에, 브라우저가 그를 보호해 주는 일도 없다. 그의 바이러스 백신은 실행 중이며 이미 해당 도메인을 악성 사이트로 판정했을 수도 있지만, 확인 요청을 받은 적은 없다. 그를 막을 수 있었을 모든 경고는 이미 존재한다. 하지만 그 어떤 경고도 그에게 닿지 않는다. 그는 자신이 Steam을 떠난 적이 없다고 믿고 있으며, 실제로 그는 떠나지 않았다.\n\n이러한 ‘무료 증정’ 방식은 피싱 사기꾼들이 고안한 것이 아닙니다. ‘무료 Valve’ 상품은 스킨 및 도박 사이트들이 광고하는 방식이며, 바로 그 때문에 이 메시지가 평범하게 보이는 것입니다. 불만 사항: 집행 기록 보관소. 연령 및 자녀 관련 정보: 제17조.\n\n출처: Steam는 Chromium Embedded Framework를 통해 웹 콘텐츠를 렌더링하며, steamwebhelper 프로세스 — 참조 2024년 6월 27일 DARKNAVY의 기술적 분석 ↗ 그리고 Valve만의 Steam 클라이언트 베타 포럼 ↗ 보관됨 2025-08-04 ↗. CEF 버전을 사용하지 않습니다. 내장된 크롬(Chromium)은 크롬(Chrome)이 아니며, 크롬에 포함된 구글 서비스는 전혀 제공되지 않습니다. API 키 없이 안전한 브라우징: 크롬 디자인 문서 ↗ 보관됨 2026-08-21 ↗, Chromium API 키 ↗ 보관됨 2026-08-30 ↗ (“Chrome에서 사용하는 Google API 중 상당수는 Google 전용이며, 파생 제품에서 사용하기 위한 것이 아닙니다”), 그리고 키가 설정되지 않은 다른 빌드에서도 동일한 효과가 나타납니다 — 홈브루 캐스크 #193814 ↗. 테스트 URL: testsafebrowsing.appspot.com ↗.\n\n서로 다른 두 개의 시계\n도메인의 개설 기간.관측 날짜.\n\n등록일자는 도메인이 등록된 시점을 나타냅니다. 날짜가 명시된 OpenID 레코드는 해당 레코드의 리턴 호스트를 나타냅니다. 전자는 후자보다 이전의 기간을 채울 수 없습니다.\n\n전체 레지스트리에는 별도의 등록 가능 도메인, 사이트 자체의 하위 도메인, 그리고 직접 경로가 구분되어 있습니다. 각 행은 해당 출처와 DNS 결과로 연결됩니다.\n\n도메인 등록 정보 확인 →· 등록일 다운로드 ↗· 관측 결과 재현하기 ↗\n\nA부 — 기술 기록 · 제4절\n엔드포인트가 닫혔습니다. 공개 추적에서 키가 손실되었습니다.\n문맥 및 출처 제한\n\nSteam 업데이트를 통해 아이템 자산 ID의 공개 가시성이 제거되고 API 재고 접근이 제한되었습니다. 그 결과, 공개 데이터만으로는 원래 자산 ID를 통해 특정 아이템을 추적하는 것이 불가능해졌습니다. 다음은 변경 전에는 가능했던 것, 변경 후에는 더 이상 불가능해진 것, 그리고 자신의 소유물이 어디로 갔는지 증명하려는 피해자가 치러야 하는 대가에 대한 설명이다. CSFloat의 엔지니어링 계정에 따르면 시점은 2017년이며, Valve의 변경 내역은 확인되지 않았다. 이 일련의 과정 — 2016년 7월 도박 관련 성명 발표 후 약 1년 뒤 — 은 조사 대상이며, 확정된 결론은 아닙니다. 아이템 기록 자체는 여전히 Valve 시스템 내에 남아 있지만, 외부 조사관들은 원래 ID 체인에 대한 접근 권한을 상실했으며, 플로트, 시드, 페인트 식별자를 통해서는 부분적인 일치만 확인할 수 있습니다.\n\n규칙 Valve이 적용됩니다: Steam 고객 지원팀은 귀하의 계정에서 사라진 아이템을 복구해 드리지 않으며, 무슨 일이 있었는지 입증할 책임은 귀하에게 있습니다. 기록: 2017년에 Valve은 원래 아이템 ID를 전달하던 엔드포인트를 폐쇄했습니다. 그 전에는 누구나 피해자의 계정에서 도난당한 스킨이 마켓플레이스 봇으로 이동하는 경로를 추적할 수 있었습니다. 그 이후로는 Valve 외부의 누구도 이를 추적할 수 없게 되었습니다. 피해자에게 요구된 증빙 자료는 바로 그 증빙 자료가 바뀐 것이었다. — 그리고 그것은 여전히 Valve 안에 존재한다.\n\n정전 이전 시대\n\n역사적으로, Steam에서 생성된 모든 가상 아이템은 전역적으로 고유하고 변경 불가능한 자산 ID. 제3자 OSINT 데이터베이스에서 이러한 ID를 색인화할 수 있습니다. 사용자의 자산이 탈취당한 경우, 수사관들은 해당 자산이 탈취자의 중간 계정을 거쳐 마켓플레이스나 도박 사이트의 보관 계정으로 이동하는 과정을 추적할 수 있습니다.\n\n이전에는 누구나 공개 데이터를 이용해 피해자의 계정에서 중간 계정을 거쳐 마켓플레이스나 카지노 보관 봇으로 이어지는 자금 흐름을 추적할 수 있었다.\n변경 후\n\nCSFloat의 엔지니어링 계정에 따르면, Valve은 2017년에 해당 엔드포인트를 폐쇄했으며, 외부에서는 더 이상 원래의 아이템 ID를 확인할 수 없게 되었습니다. 이러한 변경 사유에 대한 Valve의 공식 발표는 확인되지 않았습니다. 같은 기간 동안, 아이템을 대규모로 이동시킨 상업용 봇 계정에 대해 취해진 조치도 공개된 바 없습니다.\n\n그 이유가 무엇이든 간에, 이러한 변화로 인해 공개된 소유권 이력 체인이 단절되었습니다. 피해자는 더 이상 공개 데이터를 통해 원본 ID 체인을 재구성하여, 특정 도난 물품이 특정 마켓플레이스나 카지노를 통해 처분되었음을 입증할 수 없게 되었습니다. 해당 물품 기록은 여전히 Valve의 시스템 내에 존재하지만, 공개 데이터를 기반으로 작업하는 일반 대중, 연구자 및 법 집행 기관은 이 기록에 접근할 수 없습니다.\n\n변경 후: 공개 데이터로는 더 이상 원래 자산 ID를 통해 특정 항목을 추적할 수 없습니다. 2017년 이후 이동된 항목에 대한 원래 ID의 소유권 이력 기록은 Valve의 인프라 내부에만 존재하며, 이와 같은 기록은 공개적으로 생성된 바 없습니다. 플로트, 시드 및 페인트 식별자는 부분적이고 확률적인 일치만 가능하게 합니다.\nIEconItems_730\nGET/IEconItems_730/GetPlayerItems/v1/\n추적 가능한 페이로드 (패치 적용 전)\n\"id\": \"14892281934\",\n\"original_id\": \"11829910211\",\n상태: 피해자는 봇 계정 간에 아이템의 이력을 추적할 수 있습니다.\n난독화된 페이로드 (패치 적용 후)\n현재\n\"id\": \"HIDDEN_BY_PRIVACY_SETTINGS\",\n\"original_id\": \"NULL\",\n상태: 외부 사용자는 더 이상 공개 데이터를 통해 원래 자산 ID를 기반으로 항목의 출처를 추적할 수 없습니다.\n증거에 미치는 영향: 변경 이후, 피해자의 계정에서 마켓플레이스나 카지노 봇으로 이동한 특정 항목을 원래의 자산 ID를 통해 추적하는 데 필요한 공개 데이터는 더 이상 이용할 수 없게 되었습니다. 내부 기록은 여전히 Valve에 존재하지만, 공개 데이터를 바탕으로 작업하는 피해자, 연구자 또는 수사관은 원래 ID 체인을 재현할 수 없습니다(float, seed 및 paint 식별자는 부분적인 일치만 가능하기 때문입니다).\n\n출처: CSFloat 엔지니어링의 2017년 폐쇄에 관한 보고서 IEconItems_730/GetPlayerItems — blog.csfloat.com/how-floatdb-tracks-items (보관됨 2026-09-21) · 표시된 페이로드는 필드 형태를 설명하기 위한 예시일 뿐, 실제로 캡처된 응답은 아닙니다. · 해당 클로저에 대한 Valve 변경 내역은 발견되지 않았습니다.\n\nA부 — 기술 기록 · 제5절\n단 한 번의 세션. 사용자가 인식하는 것보다 더 많은 접근 권한.\n문맥 및 출처 제한\n\nValve의 API 키 아키텍처는 2023년 변경 이전의 상태에서 업계 기본 표준 (OWASP ASVS, NIST SP 800-63B)에서 벗어난 것이었으며, 이는 증거 보관소에 보존된 자동화된 재고 도난 신고서(제6~8절)에 기술된 메커니즘입니다.\n\n규칙 Valve이 적용되었습니다: 계좌 소유자가 키를 생성하고 이용 약관에 동의했으며, 손실을 감수해야 한다는 것 — 이것이 보관된 거절 사유에 담긴 답변입니다. 기록: 2023년 12월까지 도난당한 세션 쿠키만으로도 해당 키를 등록할 수 있었습니다. 비밀번호도, Steam Guard도 필요 없었고, 해당 계정 소유자에게는 아무런 알림도 전송되지 않았습니다. 사용자는 해당 키를 생성하지도 않았고, 볼 수도 없었지만, 자신이 생성했다고 들었습니다. 모바일 인증 기능은 2023-12-04에 추가되었는데, 이는 2016년 성명서가 발표된 지 약 7년 후이며, 아카이브에 보존된 사기 관련 패널이 작성된 지 약 6년 후였다. 그 기간 동안의 비용은 Valve이 부담한 것이 아니었다. 그 비용은 그동안 비워진 계좌들, 그중 일부는 어린이들의 계좌에서 충당되었다.\n\nOWASP ASVS 2.8 / NIST SP 800-63B중요도: 매우 심각\n1. 강화된 인증 절차 미비\n\nSteam에서는 세션 쿠키만 사용하여 권한이 매우 높고 유효 기간이 긴 API 키를 생성할 수 있었습니다. 개발자 API 키를 설정하거나 수정할 때 2단계 인증(Steam Guard)이나 단계적 강화 인증 절차가 요구되지 않았기 때문에, Steam가 제공하는 유일한 두 번째 인증 요소인 Steam Guard 모바일 확인 절차만으로는 이 단계를 보호할 수 없었습니다. (2016년 Valve 자체 트래커에서 하드웨어 기반 두 번째 인증 요소가 요청되었으며, 이 문제는 여전히 미해결 상태입니다: 부록 D, GH-01.)\n\n상태: 2023년 이전에는 패치되지 않았음. 도난당한 쿠키를 보유한 스크립트가 사용자의 어떠한 상호작용 없이도 키를 등록할 수 있게 했다.\nOWASP A01:2021 / 최소 권한 원칙중요도: 매우 심각\n2. 최소 권한 원칙의 미준수\n\nSteam 웹 API에는 역할 기반 권한 범위가 전혀 없었습니다. “읽기 전용” 재고 상태 조회용으로 발급된 개발자 API 키는 기존 거래를 수정하거나, 새로운 거래를 시작하거나, 웹훅을 등록하거나, 유효한 대기 중인 교환 요청을 거부하는 기능을 포함하여 완전한 “쓰기” 권한을 가지고 있었습니다.\n\n상태: 체계적인 설계 결함. 키 하나만으로도 해당 계정의 재고 및 거래에 대한 완전한 읽기/쓰기 권한을 행사할 수 있습니다.\nOWASP A07:2021 / 세션중요도: 높음\n3. 세션 관리 오류\n\n사용자들은 서버 호스팅 IP 범위에서 시작된 탈취된 웹 세션이 지속된다고 보고했습니다. 일반적인 관행은 지리적 이상 현상이 감지되거나 비밀번호가 변경될 때 세션을 종료하는 것이지만, 아카이브에 수집된 사용자 보고서에 따르면 비밀번호 변경 후에도 세션이 활성화된 상태로 남아 있는 사례가 있는 것으로 나타났습니다.\n\n상태: 보고된 현상 (아카이브에 기록된 사용자 불만 사항). 세션 중 재인증 없이 API 키가 생성될 수 있었습니다.\n도메인 단위의 차단은 기술적으로 가능했다집행의 타당성\n4. 인증 호스트에 대한 도메인 수준 차단은 기술적으로 가능했다\n\nValve은 이미 도메인 목록(링크 필터)을 운영하고 있으며, 자체 OpenID 요청에서 모든 인증 호스트 이름을 수신하고 있습니다. 이 두 메커니즘은 외부에서 볼 때 어떤 식으로든 연결되어 있지 않습니다. 2026-09-22 기준으로, 26쌍의 경우 메인 도메인은 필터에 포함되어 있었으나 해당 로그인을 전달하는 프록시는 필터에 포함되어 있지 않았습니다.\n\n이들을 연결하는 것은 간단한 공학적 작업입니다: 다음을 읽어보세요. openid.realm 각 수신 요청의 호스트명을 확인하여 목록과 대조한 후, 해당 요청을 거부하거나 표시합니다. 오른쪽 그림은 이러한 루틴의 구조를 보여줍니다. 공개 랜딩 페이지뿐만 아니라 인증 호스트 자체를 거부하면, 이러한 플랫폼이 의존하는 “Steam로 로그인” 단계가 중단될 것입니다.\n\nValve이 이러한 검증을 수행한다는 것을 보여주는 공개된 증거는 없습니다. Steam 커뮤니티 마켓의 약 15%에 해당하는 통합 수수료는 마켓 내에서 성사된 거래에만 적용되며, 해당 플랫폼 외부에서 이루어지는 거래에는 부과되지 않습니다.\n\nblock_auth_hosts.py삽화\n// 호스트 Steam이 이미 수신 중인 데이터를 읽습니다 — 스캔하지 않습니다\ndef on_openid_request(request):\nhost = parse_openid_realm(request)\n만약 호스트 에서 차단된 도메인:\n거절(요청)\n참고: 이 의사코드는 설명을 위한 예시일 뿐입니다. 두 부분 모두 이미 Valve에 존재합니다. 즉, 요청에 인증 호스트명이 포함되어 있고, 도메인 목록은 링크 필터입니다. 이 둘이 연결되지 않은 이유를 설명하는 공개 기록은 없습니다.\n5.1절 — 해당 표준은 미공개 상태가 아니었다\nValve는 매일 이 규칙에 따라 빌드됩니다. 하지만 여기서는 이 규칙에 따라 빌드되지 않았습니다.\n\nSteam은 App Store와 Google Play에서 서비스를 제공하며, 주요 카드 결제 업체를 통해 판매를 진행하고, 다른 대형 플랫폼과 마찬가지로 타사 API를 활용합니다. 이러한 각 관계에는 Valve이 운영을 지속하기 위해 충족해야 하는, 공개된 날짜가 명시된 보안 요구 사항이 수반됩니다. 이러한 요구 사항의 날짜를 Steam의 자체 웹 API가 동일한 보안 조치를 적용받기 시작한 날짜와 대조해 보십시오. 아래에 나열된 내용은 비공개 표준, 내부 메모 또는 영업 비밀이 아닙니다. 모든 행은 공개 날짜가 명시된 공개 문서입니다.\n\n공개된 외부 보안 요구 사항 및 해당 날짜와, Steam 웹 API가 이에 상응하는 통제 수단을 확보한 날짜를 대조한 정보\n공표된 표준 및 그 발효일\t동일한 질문에 대한 Steam 웹 API\n범위 지정 승인OAuth 2.0 — RFC 6749, 2012년 10월. 3.3절에서는 다음을 정의한다. scope 따라서 클라이언트는 요청한 접근 권한만 부여받게 됩니다. 이후로 이는 모든 주요 플랫폼 API의 기본 설정으로 자리 잡았습니다.\t세분화된 적용 범위가 도입된 시점은 2026년 1월 16일.그 전에는 Steam 웹 API 키 하나만으로도 발급 사유와 상관없이 해당 계정의 모든 거래 내역에 대한 전체 읽기 및 쓰기 권한이 부여되었습니다. 13년 3개월 컨트롤을 정의하는 사양 뒤에.\n키(key)는 승인(authorisation)이 아닙니다.구글의 공식 클라우드 문서: 표준 API 키로는 주체 인증이 이루어지지 않습니다., 그리고 리소스를 생성하거나 관리하는 API의 경우, 실제 운영 환경에서는 인증 키를 사용하지 마십시오.\tSteam 웹 API 키는 말 그대로 그 자체였습니다.계정에 발급된 무기명 문자열로, 이 문자열만으로도 재고 조회, 보류 중인 거래 취소 및 새로운 거래 전송이 가능합니다. 사용 시점에 주체(principal)의 신원 확인은 이루어지지 않았습니다.\n특권 액세스에 대한 다단계 인증PCI DSS 3.2, 요구 사항 8.3 — 다음 날짜부터 의무 적용 2018년 2월 1일 콘솔을 통하지 않는 모든 관리 작업 및 카드 소지자 데이터 환경에 대한 모든 원격 액세스에 대해. 이후 애플은 모든 개발자 프로그램 계정 소유자에게 2단계 인증을 의무화했으며, 이는 2019년 2월 27일: 개발자 프로그램에서 ‘계정 소유자’ 역할을 가진 개발자는 로그인하기 위해 2단계 인증을 활성화해야 합니다.\t에서 API 키를 생성하려면 두 번째 요소가 필요했습니다. 2023년 12월 4일.그 전까지는 도난당한 세션 쿠키만으로도 충분했으며, 계정 소유자의 휴대폰에 알림이 표시되지도 않았고, 사후에도 어떠한 통지도 없었습니다. 4년 9개월 애플이 개발자 포털에 로그인하는 데만도 두 번째 인증 요소를 사용하도록 Valve을 도입한 이후.\n인증 정보의 수명 주기 및 취소Twitch는 모든 타사 애플리케이션에 다음을 요구합니다: 앱은 시작 시점과 그 이후 매시간마다 OAuth 토큰을 검증해야 합니다., 그리고 해당 기준을 충족하지 않는 애플리케이션에 대해서는 감사를 실시한다고 명시하고 있습니다. 기존 v5 API는 2022년 2월 28일 공지된 일정에 따라.\t키 수명 주기에 대한 기록이 공개된 바 없습니다.2023년 변경 사항은 생성 엔드포인트를 보호했습니다. 해당 변경 사항과 관련된 Valve 문장 중 이미 등록된 키를 다루는 내용은 없었으며, 변경 사항에 대한 변경 내역도 전혀 제공되지 않았습니다. 이 변경 이전에 생성된 키가 무효화되었는지 여부는 공개된 데이터만으로는 확인할 수 없습니다. 이는 정보 주체가 수년 전 자신의 계정에서 생성된 키가 여전히 유효한지 여부를 파악하기 위해 반드시 알아야 할 사항입니다.\n건축 벤치마크 // 토큰 아키텍처\nGitHub의 세분화된 범위와 Valve Steam 웹 API 비교\n\nValve명의 개발자들은 세분화된 최소 권한 토큰을 사용하여 매일 GitHub에서 오픈소스 소프트웨어를 관리합니다. 이를 1억 3천만 명의 Steam명 플레이어에게 발급된 단일 키와 비교해 보십시오.\n\nGitHub 세분화된 토큰\nGitHub에서 Valve이(가) 사용 중입니다.\n\n범위가 지정된 격리 기능과 필수 라이프사이클 적용을 지원하는 세분화된 토큰.\n\n저장소 접근:선택된 리포지토리만 (1개)\n권한 설정:읽기 전용 [✓]\n코드와 비밀:접근 불가 [✕]\n만료일:30일 (TTL 필수)\n감사 기록:IP, 사용자 에이전트 및 타임스탬프\n보안 현황: 최소 권한 토큰은 피해를 단일 읽기 전용 리소스로만 제한합니다.\n!Valve Steam 웹 API 키\n1억 3천만 명의 사용자에게 배포됨\n\n거래 및 재고에 대한 일괄 승인 권한을 포함하는 32자 길이의 단일 마스터 문자열.\n\n계정 접속:전체 계정 (모놀리식)\n거래 관리:읽기, 취소, 거절 [!]\n세분화된 범위:없음 (2026년 도착, 13년 지연)\n만료일:절대 안 됨 (무기한 유효)\n감사 기록:없음 (사용자의 IP 기록이 없음)\n취약점: 도난당한 키를 사용하면 발송되는 모든 거래 제안을 감지되지 않게 가로챌 수 있습니다.\n한 방향으로 적용되는 표준\n\n어느 공급업체 Valve — 클라우드 제공업체, 결제 처리업체, CDN 등 — 가 2단계 인증을 적용하지 않은 인증 정보 엔드포인트를 방치했고, 몇 달 후 Valve의 기업 데이터가 해당 엔드포인트에서 생성된 키를 통해 유출되었다고 가정해 봅시다. Valve는 링크를 클릭한 사람에게 책임이 있다고 인정할까요? 이 자료에 보존된 거절 사례들은 사용자에 대한 거울상 같은 질문에 대한 답을 제시합니다. 즉, 계정 소유자가 키를 생성했으므로 손실에 대한 책임도 소유자에게 있다는 입장입니다. 동일한 아키텍처에 대해 한쪽에서는 공급업체의 실패로, 다른 쪽에서는 사용자의 책임으로 설명되고 있다. 어느 쪽이 맞는지 여부는 기술적인 문제가 아니며, 이번 조사로 결론 내릴 수 있는 문제도 아닙니다. 이는 법원이나 감독 당국이 결정할 사항입니다.\n\n증거가 아닌 삽화 — 기준을 반대로 해석한 것\n계좌 소유자에게 어떠한 확인 요청도 없이, 제3자 스크립트가 브라우저 쿠키만을 이용해 모든 권한을 가진 거래 인증 정보를 생성할 수 있도록 허용한 결제 처리 업체.\n자사의 토큰이 발행된 경로를 차단하고, 이미 발행된 토큰에 대해서는 아무런 정보도 공개하지 않은 신원 인증 제공업체.\n분쟁이 제기된 송금 건에 대해, 해당 은행은 사용된 인증 정보가 고객 본인의 계좌에 등록된 것임을 확인한 후, 해당 건을 종결했다.\n\n이 중 어느 것도 특정 기업에 대한 조사 결과로 제시된 것은 아닙니다. 이는 동일한 설계상의 결정들을, 감독 당국의 대응이 잘 기록되어 있는 상황으로 옮겨놓은 것일 뿐이며, 바로 이것이 규제 당국이 수행해야 할 비교 대상입니다.\n\n기록에 따르면 다음과 같습니다: Steam 웹 API에 포함되지 않은 제어 항목들은 공개되어 있었고, 구식이었으며, 몇몇 경우에는 Valve이 자사 제품을 계속 출하하기 위해 충족해야 했던 조건들이기도 했습니다. 각 표준과 이에 상응하는 Steam 변경 사항 사이의 간격은 측정 가능하며, 상기에 명시되어 있습니다. 하지만 그 이유가 무엇인지는 밝혀지지 않았다. 이러한 간격들에 대한 Valve의 근거 설명은 발견되지 않았으며, 여기에서도 어떠한 근거도 가정하지 않는다. 해당 기록은 Valve 내에 존재하지만 공개된 바 없다.\n\n각각 공개 문서인 출처: OAuth 2.0 — RFC 6749, 2012년 10월 ↗ · Google Cloud — API 키 문서 ↗ · PCI DSS 3.2 요구사항 8.3 — PCI SSC 리소스 가이드 ↗ · 애플 — 계정 소유자를 대상으로 한 2단계 인증 의무화 예정, 2019년 2월 20일 ↗ 보관됨 2025-05-06 ↗ · 트위치 — 토큰 유효성 검사 요건 ↗ 그리고 v5 서비스 종료 공지 ↗ 보관됨 2025-01-27 ↗. Steam의 날짜는 이 섹션에 있는 업데이트 기록에 기재된 날짜이며, 2023년 및 2026년 항목은 Valve이 변경 내역 없이 배포한 것들입니다. 2026-09-22에 확인함.\n\nValve의 자체 업데이트 기록 — 날짜가 명시되어 있으며, 공개 출처에서 가져온 정보\n날짜\tValve 변경\t발표되었나요?\t무엇이 문을 닫았는지\t지연: 메커니즘 공개 → 수정\t출처\n2026-09-01\t의심스러운 채팅 자동 표시\t네\t그룹 채팅 내의 위험한 링크 및 패턴\t—\t뉴스 ↗\n2026-01-16\tSteamworks 웹 API의 세부 범위\t네\t개발자 키에 대한 최소 권한 범위\t—\t공지 ↗\n2025-07-15\tCS2 트레이드 보호 및 반전 창\t네\t아무것도 없어요. 근본적인 보안 문제를 해결하는 조치는 아닙니다. 지원팀 측의 계정 복구 접근 권한은 그대로 유지됩니다. 거래 취소 요청 시 자동으로 30일간의 거래 제한이 적용됩니다 (Skinvault ↗), 반면 현물 거래 충격으로 인해 24시간 시가총액이 $104M (-25%) 급락했다 (CSMarketCap ↗). 2026년부터 타이머는 항목별로 적용되게 되었으며 (Skin.land ↗).\t—\t자주 묻는 질문 ↗\n2025-05-14\t계정 보안 공지\t네\t스틸러 / 세션 탈취 대응 지침\t—\t공지 ↗\n2024-10-02\tCS2 ‘The Armory’ 7일간 보류\t네\t아머리 아이템 거래/시장 보류\t—\t공지 ↗\n2024-09-18\t신규 기기 로그인 관련 거래 제한\t네\t새 기기에서 2~7일간의 거래 제한\t—\t자주 묻는 질문 ↗\n2024-02-14\t프로필 이름 및 아바타 변경 보류\t네\t이름 변경 후 거래 시 2~4시간의 대기 시간이 적용됩니다.\t—\t게시물 ↗\n2023-12-04\tAPI 키에 대한 모바일 인증\t변경 내역 없음\t쿠키 전용 무음 키 등록\t2017년 당시 패널 출시 후 약 6년 후\t개발자 페이지 ↗\n2023-10-24\t게임 빌드 배포를 위한 SMS 기반 다단계 인증(MFA)\t네\tSteamworks 빌드 게시\t—\t공지 ↗\n2023-07-12\t사용자 정의 약력 콘텐츠 경고\t네\t약력에 포함된 피싱 링크\t—\t포럼 ↗\n2023-01-25\t프로필 {링크 삭제됨} 및 재사용 대기시간\t네\t프로필 본문의 링크\t—\t자주 묻는 질문 ↗\n2022-10-24\t로그인 시스템 개편 및 쿠키 길이 제한\t변경 내역 없음\t무한히 도용된 세션\t— (IAuthenticationService 토큰 마이그레이션)\t뉴스 ↗\n2022-10-12\t모바일 앱 3.0 QR 로그인\t네\t세션 권한 해제 패널\t—\t뉴스 ↗\n2022-05-10\t거래 취소 엔드포인트 제거됨\t변경 내역 없음\t오퍼 교환 (취소 및 재전송)\t2017년 당시 패널 출시 후 약 5년 후\t제325호 ↗\n2020-05-25\t도타 2 7일 거래 잠금\t네\t빠른 아이템 매매\t—\t블로그 ↗\n2018-03-29\tCS:GO 7일 거래 잠금\t네\t즉각적인 봇 세탁\t2016년 7월 성명 발표 후 약 20개월 후\t블로그 ↗ 보관됨 2025-02-26 ↗\n출처: 링크된 Valve 게시물, 도움말 페이지 및 GitHub 이슈(날짜 기준). 변경 내역 없이 배포된 세 가지 결정적인 수정 사항(2022-05, 2022-10, 2023-12)은 Valve 측에서 발표하지 않았으나 사용자들이 발견했으며, 이러한 비대칭성은 집행 기록의 일부입니다. 지연 기간은 해당 자료 자체의 날짜 정보(2016년 7월 성명서, 2017년경 사기 패널)가 시작점을 제공하는 경우에만 계산되며, “—”는 해당 시작점이 확립되지 않았음을 의미합니다.\nA부 — 기술 기록 · 제6절\n대화형 익스플로잇 및 하이재킹 시뮬레이터\n문맥 및 출처 제한\n\n피싱 메시지부터 서버 측 키 등록 및 거래 스왑에 이르는 경로를 재구성한 것입니다. 2023년 이전에는 계정에 등록된 웹 API 키로 해당 계정의 재고를 조회하고, 보류 중인 거래 제안을 취소하며, 새로운 거래 제안을 생성할 수 있었으며, 이러한 모든 작업에 대해 계정 소유자에게 거래 확인 화면이 표시되지 않았습니다. 이는 최소 권한 원칙(OWASP A01:2021)이 준수되지 않은 사례입니다. 이 시뮬레이션에 표시된 시간은 설명을 위한 예시일 뿐, 현재 플랫폼의 실제 측정값은 아닙니다.\n\n재구성된 해킹 과정을 단계별로 살펴보세요. 각 단계에서는 계정 소유자가 보는 화면과, 그 옆에 같은 순간에 Steam으로 걸려오는 전화 내용이 표시됩니다. 그 전화 통화들은 하나하나 모두 올바르게 인증되었습니다. 이 일련의 과정 중 어떤 단계에서도 Steam의 인증이 실패할 필요가 없다. 단지 Steam이 발급하는 키에 적용 범위가 없어야 할 뿐이다(OWASP A01:2021).\n\n플레이어가 보는 것. 그 뒤에서 일어나는 변화.워크스루 시뮬레이터\n단계 5 / 5\n\n익스플로잇이 완료되었습니다. 피해자는 원래 체결하려던 거래에 대한 모바일 알림이 올 것으로 예상한 채, 대체 거래를 승인합니다. 이는 최소 권한 원칙(OWASP A01:2021)이 적용되지 않았을 때 어떻게 1초도 채 걸리지 않는 시간 내에 자산 탈취가 자동화되어 이루어지는지를 보여주는 통합 포렌식 시나리오입니다.\n\n01 / 채팅 미끼친구가 투표를 해달라고 부탁했다피해자는 링크가 포함된 메시지를 받습니다.\n02 / 로그인닮은꼴 포털피해자가 로그인 정보를 입력합니다.\n03 / 접근사일런트 웹 API 생성공격자가 개발자 키를 등록합니다.\n04 / 더 스위치합법적인 거래가 이루어졌다복제 봇은 대상 수신자를 복제합니다.\n05 / 확인위조품 승인됨모바일에서 잘못된 제안이 승인되었습니다.\n네트워크 관점에서 본 동일한 단계2023년 이전 패턴 재구성 · 예시적인 호형\n피해자원래 거래에 대해 예상되었던 모바일 알림을 승인합니다.\n공격자복제 계정에서 해당 항목을 수령합니다.\nSteam 회 조회계좌 소유자가 등록된 기기에서 확인한 이체.\nConfirmation genuine — made by the account holder\nRecipient the clone bot, not the intended counterparty\nThe confirmation is authentic. The offer it confirms is not the one the user initiated.\n\n남겨진 기록: 사용자가 승인한 거래입니다. 이는 불만 신고가 접수되었을 때 Steam 지원팀이 확인하는 기록이며, 보관된 불만 신고들이 ‘사용자 오류’로 종결된 이유이기도 합니다. 불만 신고는 집행 기록 보관소.\n\nA부 — 기술 기록 · 제7절\n시퀀스 뒤에 있는 엔드포인트.\n문맥 및 출처 제한\n\n다음은 보고된 하이재킹 스크립트가 브라우저 측의 확인 단계를 거치지 않고 거래를 가로채는 데 사용한 Steam개의 웹 API 엔드포인트입니다.\n\n문서화되어 있는 네 가지 엔드포인트만으로도 모든 작업이 처리됩니다. 이 중 어느 것도 결함이 아니며, 악용할 필요도 없습니다. 유효한 키가 이를 호출하면 Steam이 응답합니다. 공격자가 훔쳐야 했던 것은 바로 그 키뿐이었다.\n\nIEconService / GetTradeOffers / v1여론조사\n\n계정의 거래 오퍼를 모니터링하는 데 사용됩니다. 스크립트는 유출된 API 키를 사용하여 이 엔드포인트를 반복적으로 폴링하며, 이 엔드포인트는 새로 생성되거나 대기 중이거나 수정된 거래 오퍼의 세부 정보를 반환합니다. 여기서는 폴링 간격은 측정되지 않습니다.\n\n위협 경로: 진행 중인 거래 제안 ID와 수신자의 프로필 세부 정보를 표시합니다.\nIEconService / CancelTradeOffer / v1상호작용\n\n사용자의 정당한 거래 제안을 프로그래밍 방식으로 무효화하는 데 사용됩니다. 2023년 이전에는 키를 보호하는 단계별 인증이 없었기 때문에, 자동화된 서버가 거래 제안을 감지하는 즉시 계정 소유자에게 어떠한 알림도 없이 해당 제안을 취소할 수 있었습니다.\n\n위협 경로: 계좌 소유자가 모바일 확인 절차를 완료하기 전에 거래를 취소합니다.\nISteamUser / GetPlayerSummaries / v2RECON\n\n정당한 거래 수취인의 프로필 이름, 아바타 이미지 URL 및 레벨을 조회했습니다. 이를 통해 스크립트는 미리 준비된 복제 계정을 해당 정보에 맞게 꾸밀 수 있습니다. 여기서는 시간 측정이 이루어지지 않습니다.\n\n위협 경로: 수신자로 가장하는 데 필요한 데이터를 제공합니다.\n/dev/ajaxregisterkey창조\n\nSteam의 키 등록 엔드포인트. 과거에는 활성 상태인 브라우저 쿠키 세션(`steamLoginSecure`)이라면 모바일 기기에서 Steam Guard 확인 절차 없이, 또한 계정 소유자에게 어떠한 알림도 없이 키를 등록할 수 있었습니다.\n\n위협 경로: 계정 소유자가 알지 못하는 사이에 스크립트에 의해 생성된 영구적인 인증 정보.\nA부 — 기술 기록 · 제8절 · GDPR 제7조\n체크된 상자. 누구의 행동인가?\n문맥 및 출처 제한\n\n보상 거절 시, Steam 아카이브에 보관된 지원 답변들은 계정 소유자가 API 키를 생성했으며, 확인란을 선택함으로써 약관에 동의한 것으로 간주한다는 입장을 취하고 있습니다.\n\n지원 응답은 해당 계정의 소유자에게 그 열쇠를 귀속시킵니다. 문제는 해당 기록이 누가 실제로 이를 생성했는지를 입증하는지 여부입니다.\n\n그러나 관찰된 API 키 탈취 패턴에서는 피해자가 API 키 생성 페이지를 보거나 해당 페이지로 이동한 적이 전혀 없습니다. 동의 항목은 도난당한 세션 쿠키를 사용하여 헤드리스 POST를 실행하는 스크립트에 의해 전송됩니다.\n\nGDPR 제7조 및 제4조 제11항에 따르면, 동의는 데이터 주체의 의사를 자유롭게, 구체적으로, 충분한 정보를 바탕으로, 그리고 모호함 없이 표시한 것이어야 합니다. 저자들의 입장은, 계정 소유자에게 페이지가 표시되지 않은 상태에서 도난당한 쿠키를 사용하여 악의적인 스크립트가 제출한 이용약관 동의 입력란은 해당 정의를 충족할 수 없다는 것이다. 이것이 정의를 충족하는지 여부는 감독 당국이 판단할 사항이다.\n\n포렌식 페이로드 분석: 키 등록\n게시물 https://steamcommunity.com/dev/ajaxregisterkey\n// 요청 페이로드 (하이재킹 스크립트를 통해 삽입됨)\n{\n\"agreeToTerms\": \"동의함\", <-- 기계에 의해 자동으로 입력되었으며, 사람의 개입이 없음\n\"도메인\": \"localhost\", ← 유효성 검사되지 않음 — localhost를 포함하여 어떤 값이든 허용됨\n\"sessionid\": \"8f0d8ef763ab2140bf89de2a\"\n}\n감독 당국에 대한 질문: 계좌 소유자가 동의란을 클릭한 적이 없는 경우, 해당 계좌에 기록된 약관 동의 내용이 제7조에 명시된 ‘데이터 주체의 의사에 대한 자발적이고, 구체적이며, 정보에 입각하고, 모호함이 없는 표시’ 요건을 충족하는지 여부, 그리고 Steam 고객지원팀이 이를 근거로 청구를 기각할 수 있는지 여부.\n\n출처: 공개 엔드포인트 및 증거 보관소에 보존된 하이잭 보고서를 바탕으로 재구성된 키 등록 요청 형태 (2026-09-17의 검색 가능한 빌드) · 표시된 세션 식별자는 실제 값이 아닌 자리 표시자입니다.\n\n법의학적 부검 · 대체품 벡터\nValve이 어떻게 마침내 “무역 대체”를 무력화시켰는지 — 그리고 왜 7년 동안 우회책을 써야만 했는지\n\n거의 10년 동안, \"API 키 교환 사기\"(또는 API 중간자(MitM) 사기) 이는 Steam에서 가장 수익성이 높은 계정 도용 수법이었으며, 아무것도 모르는 플레이어들에게서 수억 달러 상당의 스킨을 빼돌렸습니다. Valve은 취약한 API 아키텍처를 수정하여 이 악용 사례를 근절하지 못했으며, 대신 Valve은 7년에 걸쳐 플랫폼 전반에 걸쳐 네 가지 마찰 장벽을 단계적으로 도입함으로써 커뮤니티 거래 유동성을 마비시켰을 뿐, 근본 원인은 해결하지 못한 채 방치했습니다.\n\n1. 모방의 죽음\n아바타 및 이름 변경 대기 시간 (2024년 2월)\n\n이 공격은 1초도 채 걸리지 않는 모방 기술을 필요로 했다. 사기 봇은 발신 중인 거래를 가로채고, 수신자의 아바타와 이름을 ISteamUser, 그리고 200ms 만에 해당 프로필을 복제했습니다. 2024년 2월 14일, Valve은 조용히 의무적인 조치를 시행했습니다. 2~4시간 거래 대기 시간 (오류 34) 프로필 이름이나 아바타를 변경한 직후. 봇은 더 이상 거래에서 스스로를 차단하지 않고는 수신자를 즉석에서 복제할 수 없습니다.\n\n2. 경제적 죽음\n7일 CS2 추세 반전 (2025년 7월)\n\nValve 일방적으로 도입했다 거래 방향 전환 카운터 스트라이크 아이템의 경우, 거래된 모든 스킨에는 7일 동안 “거래 보호” 태그가 부여됩니다. 피해자가 아이템이 바꿔치기된 사실을 발견하면, Steam 지원 센터에서 “거래 취소”를 클릭하면 해당 스킨이 즉시 자신의 인벤토리로 반환되며, 수령자는 계정이 동결됩니다. 7일간의 거래 잠금 기능 덕분에 사기꾼이 아이템을 현금화 사이트로 옮길 수 없기 때문에, 절도 행위는 수익성을 잃게 됩니다.\n\n3. ‘사일런트 키’의 죽음\nAPI에 대한 필수 모바일 푸시 알림 (2023년 12월)\n\n과거에는 도난당한 세션 쿠키로 인해 악성 스크립트가 헤드리스 백그라운드 POST 요청을 수행하여 /dev/ajaxregisterkey 피해자에게 알리지 않은 채. 2023년 12월 4일, Valve은 웹 API 키 생성을 위해 Steam 모바일 앱에서 명시적인 푸시 확인을 의무화함으로써, 사용자 모르게 백그라운드에서 키가 할당되는 방식을 없앴습니다.\n\n4. 모바일 앱 내 경고\n계정 개설 기간 및 이름 배너 (2022–2024)\n\nValve 거래 상대방의 정보를 표시하도록 모바일 확인 모달을 개편하여 Steam 계좌 개설일 (생성일), Steam 단계, 그리고 명시적인 황색 경보: \"이 사용자는 최근 프로필 이름을 변경했습니다.\", 주의 깊은 피해자들에게는 시각적 착각을 깨뜨리게 된다.\n\nValve의 패치워크에 숨겨진 세 가지 결함: 사기꾼들이 단순히 표적을 바꾼 이유\n1. 게임 제외 허점 (Dota 2 및 TF2)\n\n‘트레이드 리버설’은 ‘카운터 스트라이크 2’ 전용으로 도입되었습니다. Dota 2와 Team Fortress 2의 아이템은 여전히 아무런 보호 조치도 받지 못하고 있다 제작 및 소켓 장착 과정의 복잡성 때문입니다. 수천 달러 상당의 고등급 아이템(드래곤클로 후크, 골든 베이비 로샨, 특이한 TF2 불꽃)은 환불 기간이 전혀 없습니다. 사기꾼들은 단순히 자동화된 API 가로채기 방식을 도타 2와 TF2 거래자들로 돌렸을 뿐이며, 해당 플랫폼의 Steam 지원팀은 2016년부터 시행해 온 “아이템 복구 불가” 정책을 엄격히 적용하고 있습니다.\n\n2. “좀비 키” 리저버(만료 기간 없음)\n\nValve는 모바일 푸시 2단계 인증을 추가하여 새 2023년 12월, Valve 기존 레거시 API 키가 취소되거나 만료되거나 삭제된 적이 없음. 키를 생성한(또는 2023년 12월 이전에 피싱/악성코드를 통해 사용자 모르게 키가 생성된) 수백만 개의 활성 계정에는 여전히 유효한 인증 정보가 남아 있으며, 만료 시간 없음(TTL 없음) 및 비활성 타임아웃 없음. 위협 행위자들은 이러한 지속적 키에 대한 방대한 과거 데이터베이스를 유지하며, 계속해서 폴링을 수행하고 있다 IEconService 아무런 방해도 없이.\n\n3. 피해자 처벌: 30일간의 거래 제한\n\nCS2에서도 Valve은 사기를 당한 플레이어에게 불이익을 줍니다. Steam 지원에서 “거래 취소”를 클릭하면 자동으로 피해자 계정에 대해 30일간의 거래 및 커뮤니티 마켓 이용 금지 조치를 의무적으로 적용. Valve는 “경솔한” 거래 취소 행위에 대한 억제책으로 해당 사용자에게 한 달간의 플랫폼 이용 정지 처분을 부과함으로써, 피해자들이 가치가 낮고 유동성이 높은 상품에 대한 거래를 취소하는 것을 막고 있습니다.\n\n핵심 규제 스캔들: 7년간의 우회책 대 하나의 API 범위\n\n왜 Valve은 업계 표준 해결책을 도입하는 대신, 7년 동안 거래 보류, 계정 쿨타임, 취소 가능한 거래 잠금 기능을 고안해 내면서 게임 경제 전체를 뒤흔들고 시가총액 $104M을 날려버렸을까?\n\n2026년 1월 16일 Valve의 공식 Steamworks 출시에서 입증된 바와 같이 (공지) #493839547938902179 ↗), Valve 이미 건설됨 세분화된 권한 그룹 (일반, 소액 결제, 경제, 판매 데이터) 그리고 IP 허용 목록 기업용 퍼블리셔 키의 경우, Valve은 수년 전부터 기술적 해결책을 마련해 두었습니다. 사용자에게 표시되는 하나의 확인란만 있으면—\"이 웹 API 키가 IEconService(거래 관리)에 액세스하지 못하도록 방지\" 혹은 가정용 IP 허용 목록을 도입했다면, 2018년에 경제적 부수적 피해 없이 거래 대체 사기를 근절할 수 있었을 것입니다. Valve은 기업 파트너들을 위해 마련한 보호 조치를 일반 플레이어들에게는 제공하지 않았습니다.\n\nB부 — 규정 및 집행 실적 · 제9조\n그들의 규칙서. 기록된 플랫폼들.\n문맥 및 출처 제한\n\n이 원장에는 다음의 명시적 절들이 매핑되어 있습니다. Steam 가입자 계약서(SSA) 그리고 Steam 온라인 행동 수칙 (SOC) 활발하게 활동하는 대규모 상업 기관을 직접 겨냥한 지침.\n\n규칙: 상업적 이용 금지, 도박 금지, 봇 사용 금지 — 그리고 Steam 고객 지원팀은 피해자의 아이템 반환을 거부할 때 이러한 조항을 인용합니다. 기록: 표면적으로 볼 때, 동일한 조항들은 이 등록부에 등재된 상업용 플랫폼들을 포괄하며, 해당 플랫폼들은 Steam개의 신원, Steam개의 봇, Steam개의 전송을 기반으로 운영됩니다. 이 조항은 가죽을 분실한 사람에게 적용되며, 공개된 기록상으로는 가죽을 운송한 업체들에게는 적용되지 않습니다.\n\n보관된 불만 사항에서 Steam Support는 다음과 같이 언급하고 있습니다. \"상업적 사용 금지\" 그리고 \"자동화/봇 금지\" API 키 사기 피해자에게 항목을 복원해 주지 않을 때 적용되는 조항들. 이러한 조항들은 표면상으로는 Steam OpenID를 통해 인증을 수행하고 자동화된 Steam 계정을 통해 항목을 이동시키는, 본 보고서에 기록된 상업용 플랫폼에도 동일하게 적용된다. 여기서는 시장 전체의 매출 규모를 추정하지 않습니다(아래 집행 통계 참조). 기록에 나타난 내용은 보관된 사례에서 개별 계정에 적용된 규칙일 뿐이며, 플랫폼별 사업자 단위의 공개된 집행 기록은 없습니다. 이 절에서는 바로 이러한 비대칭성을 다루고 있습니다.\n\n핵심 쟁점 / 선택적 집행규칙 → 규모 → 책임성\n단 하나의 규칙집. 불공평한 집행.\n\n등록부에 따르면, 상업적 서비스들은 Steam 신원, 인벤토리, 봇 및 전송 기능을 운영 인프라로 활용하고 있는 것으로 나타납니다. SSA는 허가 없이 상업적 이용 및 자동화를 금지하고 있습니다. 보관된 민원 기록을 보면 해당 규정이 개인 계정에 적용된 것으로 나타나지만, 공개 기록에는 여기에 기재된 플랫폼들에 대해 사업자별로 구분된 이에 상응하는 계정 정보가 나타나지 않습니다. 각 사례에 대한 규칙, 증거 및 집행 결정을 공개하십시오.\n\n189감사 대상 웹사이트\n44라이브 레지스터에 등록된 별도 도메인 경로 — 공개된 증거 파일이 있는 경로 27개, 수동으로 수집된 경로 17개. 189개 웹사이트에 대한 브라우저 감사만으로도 이 중 25개가 해결되었으며, 레지스터에는 수동으로 수집된 경로가 추가되었습니다.\n12년 6개월csgogem.com이 링크 필터에 의해 차단되었습니다; api.csgem.com 등록일 2014-03-08이며 차단된 적이 없음 — 2026-09-22 기준 이와 같은 26쌍 중 하나\n확인된 총계 없음시장 전체 매출 추정치는 제외됨\nSteam 온라인 예절\n\"…귀하는 Steam에서 다음의 행위를 하거나 시도해서는 안 됩니다: […] 상업적 활동을 하는 행위. 이러한 금지된 행위의 예로는 광고 게시, 경품 행사 개최 등이 있습니다; 도박; Steam 계정의 매매; 콘텐츠, 기프트 카드 또는 기타 아이템의 판매; 구걸.\"\n\nstore.steampowered.com/online_conduct ↗ 보관됨 2026-09-21 ↗\n\nSSA § 2.G — 상업적 이용\n\"…[귀하는] 본 계약의 다른 조항에서 명시적으로 허용된 경우를 제외하고, 콘텐츠 및 서비스 또는 그 일부를 어떠한 상업적 목적으로도 이용해서는 안 됩니다…\"\n\n보도에 따르면, Valve의 2016년 공고에는 개인적·비상업적 사용 라이선스가 명시되어 있었다. 기록상 Valve 승인을 제시한 사업자는 없다. store.steampowered.com/subscriber_agreement ↗ 보관됨 2026-09-18 ↗\n\nSteam 웹 API 이용 약관\n\"귀하는 Steam 웹 API 또는 Steam 데이터를 Steam 가입자 계약에 위배되는 방식으로 사용할 수 없습니다.\"\n\n제3자 스킨 마켓플레이스는 Steam API를 이용하는 자동화 계정을 통해 운영됩니다. 해당 규칙 문구에는 상업적 규모에 대한 예외 조항이 명시되어 있지 않습니다. steamcommunity.com/dev/apiterms ↗ 보관됨 2026-09-21 ↗\n\nSSA §4.C\n자동화\n\n스크립트, 봇 및 비인간적 상호작용은 제한됩니다. 이 원장에는 상업적 규모로 이루어지는 봇 거래, 계정 팜 및 자동 라우팅이 기록됩니다.\n\n점검 153이 조항에 태그가 지정된 기록 ↗\n이 조항에 따라 기록에 기재된 내용153 태그가 지정된 플랫폼\n사건 개시15\n스킨 카지노13\nCS2 마켓9\n스킨 룰렛8\ncsgoempire.com→csgoempirelogin4.com카지노\nrollbit.com→rbsnin.com암호화폐 카지노\n500.casino→fivezerozero.co인가받은 카지노\n\n이 중에서, 153 또한 SSA §2.G에 따라 태그가 지정되어 있으며, 2 또한 SSA §1.C 항목에도 태그가 지정되어 있습니다. 동일한 서비스가 두 개 이상의 조항에 해당하기 때문에 예시가 중복되어 나열됩니다.\n\n28 153의 사례들이 별도의 등록 가능한 도메인을 통해 인증되는 것으로 관찰되었습니다. 태그는 날짜가 명시된 관찰 내용을 기록하는 것으로, 이를 통해 플랫폼이 표면상 해당 조항에 해당하게 됩니다. 이는 판결을 통해 확정된 위반 사항이 아니며, 이들 중 어느 하나에 대해서도 Valve의 승인이 제시된 바 없습니다.\n\nSSA §2.G\n상업적 이용\n\n상업적 이용을 위해서는 명시적인 허가가 필요합니다. 문서화된 비즈니스 모델과 그 규모, 그리고 공개된 승인 또는 집행 내용을 비교해 보십시오.\n\n점검 175이 조항에 태그가 지정된 기록 ↗\n이 조항에 따라 기록에 기재된 내용175 태그가 지정된 플랫폼\n사건 개시15\n스킨 카지노13\nCS2 마켓9\n스킨 룰렛8\ncsgoempire.com→csgoempirelogin4.com카지노\nrollbit.com→rbsnin.com암호화폐 카지노\n500.casino→fivezerozero.co인가받은 카지노\n\n이 중에서, 153 또한 SSA §4.C에 따라 태그가 지정되어 있으며, 24 또한 SSA §1.C 항목에도 태그가 지정되어 있습니다. 동일한 서비스가 두 개 이상의 조항에 해당하기 때문에 예시가 중복되어 나열됩니다.\n\n28 175의 사례들이 별도의 등록 가능한 도메인을 통해 인증되는 것이 관찰되었습니다. 태그는 날짜가 명시된 관찰 내용을 기록하는 것으로, 이를 통해 해당 플랫폼은 표면상 해당 조항의 적용 대상이 됩니다. 이는 판결을 통해 확정된 위반 사항이 아니며, 이들 중 어느 것에 대해서도 Valve의 승인 증빙 자료가 제시된 바 없습니다.\n\nSSA 제3.A조\nVPN 및 위치 숨기기\n\nIP 프록시를 통해 거주지를 위장할 경우 서비스가 중단될 수 있습니다. 별도의 도메인을 사용하는 인증 호스트의 경우 별도의 분석이 필요합니다. 즉, 무엇이 위장되었는지, 그리고 어떤 규칙이 적용되는지 확인해야 합니다.\n\n인증 호스트 증거를 확인하십시오 ↗\nSteam 도움말 / URL 정책\n링크 난독화\n\nSteam은 링크 단축 서비스 및 링크의 목적지를 숨기는 도구의 사용을 금지합니다. 별도의 인증 도메인 — rbsnin.com Rollbit의 로그인 절차에서, auth.dota.trade CS.MONEY의 경우 — Steam의 OpenID 검증기에 표시된 목적지가 운영 사이트를 식별하는지 여부에 대한 유사한 의문이 제기된다.\n\nValve의 URL 정책 ↗\n\n관련 규칙: Steam 가입자 계약서, 2026년 9월 10일 개정판 보관됨 2026-09-18 ↗ · Steam 웹 API 이용 약관 보관됨 2026-09-21 ↗ · Steam URL 정책 (링크 난독화). ‘건수’는 이 자료집에 포함된 기록과 태그의 수를 나타내며, 판결이 확정된 위반 건수를 의미하는 것은 아닙니다.\n\n신뢰 부족\n지원팀에서 사건을 종결할 때, 누가 그 결정을 검토하나요?\n\n보존된 불만 사항에는 영구 제재, 답변이 없는 이의 제기, 도난당한 항목의 반환 거부 등이 기술되어 있습니다. 이러한 내용을 실제 티켓 내역, 이용 가능한 구제 조치 및 계정 접속 로그와 대조하여 확인해 보십시오. 일반적인 피싱 관련 설명만으로는 누가 계정 재설정을 시작했는지, 또는 누가 API 키를 생성했는지 확인할 수 없습니다.\n\n제기된 불만 사항 읽어보기 ↗관련 기록 요청 →중재자 관계도 →\nB부 — 규정 및 집행 실적 · 제10조\n자동화 API. 자동화를 금지하는 규칙.\n문맥 및 출처 제한\n\n이 섹션에서 제기하는 질문은 이 두 가지가 어떻게 조화를 이루는지, 즉 어떤 API 사용이 허용되는지, 누가 허용하는지, 그리고 어떤 공개된 기준에 따라 허용되는지입니다. 여기서는 승인된 상업용 API 사용자 수에 대한 추정을 하지 않았으며, 공개된 목록이 없다는 사실에서 어떤 수치를 암시하지도 않습니다. 목록이 없다는 사실 자체가 결론일 뿐, 그 뒤에 숨겨진 숫자가 아닙니다. 위에서 인용된 Steam 지원 메시지는 ArchiSteamFarm 프로젝트가 자체 FAQ에 재게재한 것(문구 그대로 확인됨 2026-09-22)이며, 이는 Valve 공식 간행물이 아니며, 해당 메시지가 전송된 계정 정보도 공개되지 않았습니다.\n\n해당 규정(SSA § 4.C): Steam에서는 스크립트, 봇, 비인간 시스템이 허용되지 않습니다. 기록: Valve은 서버 간 자동화만을 목적으로 하는 헤드리스 REST API를 제공하며, 모든 계정에 해당 API의 접근 권한을 부여합니다. 자동화 행위를 한 사용자는 이용 정지 처분을 받으며, 해당 자동화 인터페이스는 Valve의 자체 제품입니다. 어떤 상업적 용도가 허용되는지는 지금까지 공개된 적이 없다.\n\n“게임 개발자”에 대한 오해\nSteamworks SDK (정품)\n\n정식 게임 개발사들이 게임 클라이언트에 업적, 매치메이킹, 순위표를 통합하는 데 사용됩니다. 복잡한 C++ 통합 과정과 공식 파트너 등록 절차가 필요합니다.\n\nSteam 웹 API (허점)\n\n외부 웹 서버용으로 설계된 헤드리스 JSON/REST 아키텍처입니다. 본 문서에 기술된 ‘하이잭(hijack)’ 패턴에서는 이 아키텍처를 사용하여 원격 서버에서 재고 정보를 조회하고 P2P 거래를 처리하는 데 활용되지만, 이 아키텍처의 합법적인 용도는 본 문서에 수록되어 있지 않습니다.\n\n그 열쇠가 누구를 위한 것인지일반 Steam 사용자에게는 클라이언트 내에서 웹 API 키가 필요하지 않습니다. 키 페이지는 개발자용 URL에 위치하며, 문서에 명시된 용도는 외부 서버 측 액세스입니다. 보관된 계정 탈취 관련 신고 사례에 따르면, 피해자들은 자신의 계정에 키가 등록될 때까지 해당 페이지의 존재조차 몰랐던 것으로 나타났습니다.\n자동화의 모순\n\nSSA § 4.C에는 다음과 같이 규정되어 있습니다: \"어떠한 방식으로도 Steam의 콘텐츠 및 서비스와 상호작용하기 위해 스크립트, 봇, 매크로 또는 기타 사람이 직접 제어하지 않는 시스템('자동화')을 사용해서는 안 됩니다.\" 그러나 웹 API 엔드포인트(예: CancelTradeOffer)는 사용자 인터페이스나 보안 문자(CAPTCHA)가 필요하지 않으며, Steam 클라이언트를 완전히 우회합니다. 이 API는 서버 간 자동화를 위해 설계되었으며, 해당 규칙은 사용자에 의한 자동화를 금지하고 있습니다. 이 둘 사이의 경계는 공개되지 않습니다.\n\n무역 흐름에서 서버 측의 역할\n\n웹 API 키를 사용하면 제3자 서버가 Steam 클라이언트 없이도 해당 계정의 거래를 처리할 수 있습니다. ‘하이재킹’ 패턴에서는 해당 서버가 계정 소유자와 거래 서버 사이에 위치합니다.\n\n→키를 누를 때 거래 확인 화면이 표시되지 않습니다.\n→백그라운드 폴링(GetTradeOffers)을 허용합니다.\n→사용자의 개입 없이 제안을 취소하고 재발행합니다.\nValve는 인터페이스를 구축하고, 규칙을 통해 사용자의 자동화를 금지했으며, 어떤 상업적 용도가 허용되는지에 대한 기준을 공개하지 않았습니다.\nB부 — 규정 및 집행 실적 · 제11조\n10일이 요구되었다. 10년 동안의 행적을 설명해야 했다.\n문맥 및 출처 제한\n\n2016년 7월 20일, Valve의 법무 담당자는 도박 사업자들에게 10일간의 기한을 부여했습니다. 10년이 지난 현재(이 문서 스냅샷 작성 시점, 2026-09-21), 해당 통지 관련 언론 보도에 이름이 언급된 플랫폼 중 적어도 하나인 CSGOFast는 별도의 도메인을 사용하는 인증 호스트를 통해 여전히 운영 중입니다. 아래 내용은 2016년 7월 21일자 언론 보도를 바탕으로 재구성한 것으로, 스캔본이 아닙니다. 해당 통지서가 암시했던 집행 기록은 공개되지 않았습니다. 위원회에 보낸 공개 서한은 제2절.\n\n후속 관찰 내용 옆에 있는 2016년 7월 공지를 읽어보십시오. 아직 해결되지 않은 과제는 사업자별 집행 실적을 파악하는 것입니다.\n\n그보다 일주일 전인 2016년 7월 13일, 공개석상에서\n\n~에 2016년 7월 13일 보관됨 2026-09-21 ↗, Valve은 도박 사이트들이 계정 인증을 위해 Steam인 OpenID를 사용하고, 거래를 위해 자동 생성 계정을 활용하는 방식을 설명했습니다. Valve은 이러한 방식을 이용해 도박 사업을 운영하는 것이 해당 API 및 이용 약관을 위반한다고 밝혔습니다. 그 메커니즘에 대한 설명과 금지 조항 모두 Valve이 직접 작성한 날짜가 명시된 성명서에 포함되어 있다. 2026-09-21에서 테스트된 별도 도메인 인증 호스트는 링크 필터 차단 결과를 반환하지 않았으며, Valve은 사업자별 적용 레코드를 게시하지 않았습니다.\n\n부록 A / 7월 2016조판 재구성\n밸브 코퍼레이션\n\n워싱턴주 벨뷰\n\n날짜:2016년 7월 (2016년 7월 21일 언론 보도)\n보낸 사람:칼 콰켄부시, 법무총괄\nRE:중지 및 금지 — Steam 계정의 상업적 이용\n참고:보고된 텍스트를 재구성함; 스캔본이 아님\n\n\"귀하께서 아래에 나열된 도박 사이트 중 하나를 운영하고 계신다는 사실을 알고 있습니다. 귀하는 이 사업을 운영하기 위해 Steam개의 계정을 사용하고 있습니다. Steam 가입자 계약에 따라, Steam 및 Steam 서비스는 개인적, 비상업적 용도로만 사용이 허가되어 있습니다.\"\n\n\"상업적 목적으로 Steam 계정을 더 이상 사용하지 않도록 즉시 중단해야 합니다. 이를 이행하지 않을 경우 10일 이내에, Valve는 귀하의 계정 해지를 포함하되 이에 국한되지 않는 모든 가능한 구제 조치를 취할 것입니다.\"\n\n서류 복원 · 원본 기록 참조\n칼 콰켄부시\nValve Corp. 법무 담당 이사\n여백에서 / 사설\n열 날.그럼 어떻게 되나요?\n\n마감 기한은 명확히 정해져 있었습니다. 대중의 후속 조치도 마찬가지로 명확해야 합니다.\n\nValve가 발표한 ‘2016’에 대한 입장 ↗\n마감일에 관한 안내 +\n풍자 / 밸브 측과의 서신 교환 아님\n\n마감일에게,\n\n당신에게는 10일이 주어졌습니다. 왠지 모르게 달력만이 유일하게 제 기능을 하고 있었습니다.\n\n답변이 있을 경우 공개 기록에 전달해 주시기 바랍니다.\n\n연표2016년 7월 – 2026년 9월\n공고에 명시된 마감일:\n10일\n2016년 7월\n공지 이후 경과한 기간:\n3,715 일\n2016년 7월 20일부터 2026년 9월 21일 시점의 자료 스냅샷까지의 집계 수치이며, 실시간 수치가 아님\n공개된 집행 기록:\n없음\n운영자별 해지 또는 차단 내역이 발견되지 않았습니다.\n\n◀ 0~10일 — 마감일, 확대 적용3715일째 — 스냅샷 ▶\n\n2016년 7월 20일10일간의 요청이 발령됨0일차\n2024년 2월 17일DSA 의무가 적용됩니다0일째\n2026년 2월 25일뉴욕주 법무장관의 고발장 발표0일째\n2026년 9월 21일서류 개요3715일째\n\n10년 후, CSGOFast — 2016년 공지 관련 언론 보도에 언급된 — 사이트가 운영 중입니다: csgofast.com은 2026-09-19과 2026-09-21에서 Link Filter 차단 메시지를 반환했으며, 해당 사이트의 인증 호스트는 steam-login.authtofast.com (등록 번호 2026-06-30)는 그러지 않았다.\n\nValve의 보안 변경 내역에 대한 전체 날짜별 기록: 보안 연표 → · 워싱턴주의 판례와 집행 기준: 아래\n\n기록에 따르면: 2016년 공지는 10일의 기한을 정했습니다. Valve은 이미 도메인 목록(링크 필터)을 운영하고 있었으며, 자체 OpenID 요청을 통해 인증 호스트명을 수신했습니다. 사업자별 집행 기록은 공개된 바 없습니다. 커뮤니티 보고서에 따르면 2018년에 한 마켓플레이스(SkinJar)를 대상으로 조치가 취해진 것으로 나타나지만, 해당 보고서는 확인되지 않았으며 본 문서에서는 이를 근거로 삼지 않습니다.\nCSGOFAST / 저장된 인증 경로\n선언된 리턴 호스트를 따르십시오.\n\n저장된 경로 기록 링크 csgofast.com ~에 steam-login.authtofast.com. 별도의 호스트명은 Steam OpenID 요청에 포함됩니다. 이를 통해 수사관들은 Valve의 필터링 및 집행 기록과 대조할 수 있는 구체적인 주소를 확보하게 됩니다.\n\nCSGOFast 경로와 그 출처를 확인해 보세요 ↗ · 저장된 Steam 링크 필터 결과 비교 ↗\n\n공식 기록 / 워싱턴 · 2016 → 2026\n두 가지 기한. 명확히 정해지지 않은 집행 기준 하나.\n7월 20일\nValve은 도박 사이트에 10일의 기한을 부여한다\n\n해당 회사의 변호사는 Steam 계정의 상업적 사용이 계속될 경우 계정이 해지될 수 있다고 경고했다.\n\n9월 27일\n워싱턴은 Valve을 압박한다\n\n주 도박위원회는 도박을 위한 스킨 이체를 차단하기 위한 조치에 대한 증거를 요구하며, 10월 14일까지 답변을 제출할 것을 요구했다.\n\n10월 17일\nValve은 혐의를 부인한다\n\nValve은 마감 기한이 지난 후에 답변을 제출하며, 도박을 조장했다는 주장을 반박하고, 관련 계정을 비활성화했다고 밝혔으며, 모든 사용자의 거래 및 OpenID 기능을 중단하고 싶지 않다고 밝혔다. 7월 통지 관련 언론 보도에 언급된 플랫폼 중 적어도 한 곳(CSGOFast)은 10년이 지난 후에도 운영되고 있었다. 이 두 가지 사실은 운영자가 비활성화된 계정을 대체했을 때만 성립할 수 있으나, 이를 입증할 만한 기록은 공개되지 않았다. WSGC는 Valve 측에 이 두 가지 사실 간의 모순을 해소해 줄 것을 요청해야 한다.\n\n2026\n2026년 9월에 관측된 항로\n\n경로 등록부에는 2016년에 설명된 OpenID 및 거래 메커니즘 Valve을 사용하여 CSGOFast를 비롯한 별도의 도메인 인증 호스트를 통해 인증을 수행하는 44개의 플랫폼이 기록되어 있습니다. 어떤 운영자가 차단되었는지 보여줄 집행 기록은 아직 공개되지 않았습니다.\n\n위원회 자체 브리핑 · 2018년 1월 30일\nValve이 답변한 지 18개월이 지났음에도 불구하고, 규제 당국은 여전히 이를 ‘의도’로 규정했다.\n\n위원회는 HB 2881 법안에 대한 공청회에서 주 의회에 브리핑을 진행하며, 2016년 7월 성명서를 다음과 같이 직접 설명했습니다: Valve \"자사 플랫폼을 이용한 스킨 도박을 조장하는 행위에 대해 단속할 방침을 밝혔다.\" 같은 페이지에는 그 발표가 업계 전망에 어떤 영향을 미쳤는지 기록되어 있습니다 — \"그 결과,\" 2020년 스킨 도박 시장 전망치는 $19.7십억 ~에 $670백만, 발표만으로도 약 97%나 감소했다. 전망치가 바뀌었다. 이를 뒷받침할 운영자별 집행 실적은 아직 공개되지 않았다.\n\n이 시장 수치는 위원회 브리핑 자료에 인용된 Narus Advisors / Eilers & Krejcik Gaming의 추정치일 뿐, 위원회의 조사 결과는 아닙니다. 같은 문서에 따르면 2016년 스킨 베팅 규모는 약 $50억으로, 이 중 약 $30억이 카지노형 사이트에서 이루어진 것으로 나타났습니다. 검색일 2026-09-22, SHA-256 c507c9025f93da0aadaf395c4d8882f25973211c318ee8e9b6f18a5b3755e050.\n\nValve이 2016년에 공개적으로 밝힌 입장과 오늘날 확인 가능한 인프라를 나란히 비교해 볼 수 있다. 문제는 단속 조치가 금지된 사업자들이 사용한 계정과 경로에까지 미쳤는지 여부다. 10일 전 통지가 있었다는 사실만으로는, 그 통지가 명시된 사업자들 모두에게 전달되었다는 증거가 되지 않는다. 2018년 OPSkins 조치는 특정 운영자에 대해 기록된 유일한 개입 사례입니다. 189개 플랫폼이 점검되었음에도 운영자별 기록이 공개되지 않은 점을 고려할 때, 단 한 건의 기록된 조치만으로는 집행의 패턴을 보여주지 못합니다.\n\n워싱턴 도박 위원회의 2016년 공고 ↗ 보관됨 2026-05-20 ↗ · Valve의 2016년 10월 17일 답변 (문서 사본) ↗ · 2018년 1월 30일, WSGC의 입법부 브리핑 (로컬 사본, 4쪽) ↗ · wsgc.wa.gov에 있는 동일한 파일 ↗ · 검색 기록 및 해시 ↗ · Valve의 2018년 OPSkins 활동 ↗ 보관됨 2026-03-07 ↗ · 현재 경로 검토 ↗\n\n포렌식 종단적 감사 · 2016년 중단 및 철회 명령 대상\n‘10일 사전 통지 10년’: 23개 지정 대상지에 대한 법의학적 생존성 감사\n\n2016년 7월 19일부터 20일까지, Valve 카를 콰켄부시(Karl Quackenbush) 법무총괄은 23개의 스킨 도박 플랫폼에 공식적인 중단 및 철회 통지서를 발부하여, 해당 플랫폼들이 Steam 계정의 상업적 사용을 중단할 것을 명령했습니다. 10일 계정 해지 및 법적 조치의 위협을 받았음에도 불구하고. 3,700일 이상이 지난 후, 실증적 감사 결과 실제 집행 양상이 드러났다. 다수의 운영자는 운영을 중단한 적이 없었고, 다른 운영자들은 기한이 지난 후에도 최대 6년 동안 운영을 지속했으며, 수십억 달러 규모의 생태계는 계속해서 Valve의 OpenID 아키텍처를 활용하고 있었다.\n\n5+ 라이브\n2026년에 확실히 가동될 예정 (CSGOBig, CSGO500, CSGOFast 등)\n6년\n폐쇄 전 공지 게시 후 가장 긴 운영 기간 (CSGOatse는 2022년까지 운영됨)\n$5.01B\n2016년 스킨 베팅 거래량 (Narus / Eilers & Krejcik)\n200개 이상\n시장 호황기에 운영 중인 활발한 피부 도박 사이트들\n‘생존한 타이탄들’ · 2024–2026년 재무 및 트래픽 청사진\n10일 전 경고에서 해외 대기업에 이르기까지: 수십억 달러 규모의 거래\n\nValve의 2016년 공지는 스킨 도박을 근절하기보다는 업계의 진화를 촉진하는 계기가 되었습니다. 생존한 운영사들은 해외 법인(쿠라사오, 벨리즈, 키프로스)으로 구조를 재편하고, 봇 금지 조치를 우회하기 위해 P2P(Peer-to-Peer) 거래를 선도적으로 도입했으며, 현재 월간 웹 방문자 수 1,000만 명 그리고 연간 베팅 취급액 수십억 달러 Steam를 통해 인증을 계속하면서:\n\n플랫폼 / 도메인\t2016년 7월 공지\t집행 결과 및 생존 현황\t기록된 검증 / 주요 링크\nCSGOBig\ncsgobig.com\t10일 전 통지 (2016년 7월)\t2026년에도 여전히 살아있다\n일시적으로 중단되었다가 다시 시작되었으며, letmeinbig.com 및 csgobiglogin.com을 통해 인증됩니다.\tX: @csgobig ↗ · FB: csgobigofficial ↗\nCSGO500\ncsgo500.com / 500.casino\t10일 전 통지 (2016년 7월)\t2026년에도 여전히 살아있다\n‘500 Casino’(큐라소 라이선스 번호 #8048/JAZ2014-037)로 브랜드를 변경했으며, 월 매출액이 수백만에 달함\t라이브 플랫폼 (500.casino) ↗\nCSGOFast\ncsgofast.com\t10일 전 통지 (2016년 7월)\t2026년에도 여전히 살아있다\nsteam-login.authtofast.com을 통해 룰렛, 크래시, 잭팟 게임을 활발히 운영 중입니다.\t도큐멘트 인증 감사 ↗\nCSGOLounge / Dota2Lounge\ncsgolounge.com / dota2lounge.com\t10일 전 통지 (2016년 7월)\t2026년에도 여전히 살아있다\ne스포츠 코인 베팅 및 암호화폐 베팅으로 사업 방향을 전환했으며, 지속적인 운영을 유지해 왔다.\t라이브 플랫폼 ↗\nCSGOCasino\ncsgocasino.net / csgocasino.gg\t10일 전 통지 (2016년 7월)\tLIVE VIA SUCCESSOR (2026)\n도메인이 리디렉션되었습니다. 현재 운영 중인 후속 포털은 csgocasino.gg에서 운영되고 있습니다.\t후속 도메인 ↗\nCSGOatse\ncsgoatse.com\t10일 전 통지 (2016년 7월)\t6년 동안 활동 (2022년까지 활동)\nValve가 제시한 10일간의 최후통첩 이후 6년 동안 도박 사업을 계속 운영했다\tX: @CSGOatsecom (2022년까지 활동) ↗\nCSGOSweep\ncsgosweep.com\t10일 전 통지 (2016년 7월)\t2017년 12월까지 생존\n마감일 이후 17개월 동안 공개적으로 운영되었다\tX: 2017년 12월 CS:GO 스윕 현황 ↗\nCSGOWild\ncsgowild.com\t10일 전 통지 (2016년 7월)\t2017년 12월까지 생존\n주요 인플루언서들이 홍보했으며, 중단 및 철회 요청(C&D) 이후 1년 반 동안 운영된 뒤 암호화폐 분야로 전환했다.\tX: @Wild (2017년 12월 활동 중) ↗\nCSGOPot\ncsgopot.com\t10일 전 통지 (2016년 7월)\t2017년 9월까지 생존\n통지 후 14개월 동안 고액 잭팟 베팅을 운영했다\tX: @csgopot (2017년 9월 활동 중) ↗\nCSGODiamonds\ncsgodiamonds.com\t10일 전 통지 (2016년 7월)\t2017년 중반까지 살아남았다\n후원받는 스트리머들의 결과 조작 사실을 시인했음에도 불구하고 2017년을 무사히 넘겼다\tX: @csgodiamondscom (2017) ↗\nCSGOLotto\ncsgolotto.com\t10일 전 통지 (2016년 7월)\t2016년 7월 폐업\n공공 스캔들로 인해 문을 닫았으며, 연방 공정거래위원회(FTC)의 합의 명령 대상이었다\tFTC 합의 명령 (사건 번호 C-4632) ↗\nCSGODouble\ncsgodouble.com\t10일 전 통지 (2016년 7월)\t2016년 7월 폐점\nC&D 공고 게시 직후 자발적으로 영업을 중단하십시오\tX: @CSGODouble (2016년 7월 폐쇄) ↗\nCSGOMassive\ncsgomassive.com\t10일 전 통지 (2016년 7월)\t2016년 폐업\n2016년 말 대중 운영을 중단했다\tX: @csgo_massive ↗\nCSGOStrong\ncsgostrong.com\t10일 전 통지 (2016년 7월)\t2016년 폐업\n2016년에 대중 운영을 중단했다\tFB: csgostrongfree ↗\nSkins2\nskins2.com\t10일 전 통지 (2016년 7월)\t2016년 폐점\n2016년에 대중 운영을 중단했다\tFB: CSNCOM ↗\n\n플랫폼\t월간 트래픽 (방문 수)\t예상 매출액 / 거래량\t법인 및 관할권\t주요 규제 조치 및 모델\nCSGOEmpire\ncsgoempire.com\t월 230만 — 900만\n평균 6분 이상 소요; 80% 직통\t$1.5B — $2.5B 연간 취급량\n>1,000,000 월간 P2P 스킨 거래량; $6.4M 활성 유동성 주문량\tMoonrail Limited B.V. (큐라소 #148182)\n지급처: JHOLT LTD (키프로스); 설립자: “Monarch” (오시 케톨라)\t수수료 0의 P2P 아이템 거래를 최초로 도입; 큐라소 OGL/2024/1183/0869 라이선스 보유\nCSGORoll\ncsgoroll.com\t월 274만 — 350만\n평균 9분 23초 소요; 16% 이탈률\t$1.0B — $2.0B 연간 취급량\n하우스 에지에서 발생하는 연간 기업 매출액: 약 0M–1M\t페럴 홀딩스 리미티드\n벨리즈 벨리즈 시티에 본사를 두고 있음 (등록번호 #171519)\t호주 ACMA에 의해 금지 조치됨 (2023년 5월); 미성년 선수가 소속된 1부 리그 팀 G2 Esports를 후원\n500 카지노 (CSGO500)\n500.casino / csgo500.com\t월 22만 — 42만 5천\n월간 순 방문자 수 약 10만 5천 명\t로얄스에서 주당 $100k (연간 $5.2M)\n하이롤러 베팅 요건: $1 레이크백당 $400 베팅\tPerfect Storm B.V. (쿠라사오 #150536)\n쿠라사오 게임 규제 위원회 라이선스 OGL/2024/1354/0882\t스웨덴 플레이어를 대상으로 무허가 마케팅을 한 혐의로 스웨덴 게임감독청(Spelinspektionen)으로부터 금지 조치됨 (2023년 11월)\nCSGOBig\ncsgobig.com\t~169,600 / 월\n평균 소요 시간 19분 12초; 미국 예비선거\t연간 거래량 수백만\n미스터리 박스, 룰렛, 케이스 배틀\t보조 프록시 라우팅을 통해 작동합니다.\nletmeinbig.com (2023년 등록) 및 csgobiglogin.com\t2016년 7월 C&D의 대상; 프록시 인증 아키텍처를 적용하여 재출시\nCSGOFast\ncsgofast.com\t월 약 15만 ~ 25만\n전 세계의 다국어 사용자층\t연간 수백만 건의 거래량\n고속 룰렛 및 크래시 게임\t해외 운영 법인\n경로 Steam steam-login.authtofast.com을 통한 인증\t2016년 7월 C&D의 대상 기업; 사업을 중단한 적이 없음; 2026년 현재도 운영 중\nCSGO 폴리곤\ncsgopolygon.com / plg.bet\t월 약 30만 ~ 50만\nCIS 및 동유럽의 주도권\t연간 거래량 수백만\n암호화폐 및 스킨 룰렛, 경기 베팅\t2차 목표 (2016년 10월)\n미러 도메인 plg.bet을 통해 암호화폐 분야로 사업 방향을 전환했습니다.\t무사히 10년을 버텨냈으며, 타사 API를 통해 계속해서 스킨 청산을 진행하고 있다\n제2의 물결: Valve의 중단 및 철회 통지가 총 43개 이상의 사이트를 대상으로 한 이유\n\n2016년 10월 17일, Valve의 법률 대리인은 워싱턴주 도박 위원회에, 7월 19일에 발송된 초기 23건의 통지에 이어 Valve이 다음 대상들에게 중단 및 철회 요청서를 보냈다고 공식적으로 알렸습니다. 20개 이상의 추가 온라인 도박 사이트 (이로써 공식 집계는 43곳을 넘어섰다). 이번 두 번째 발표가 이루어진 이유는, 초기 명단에서 세계에서 가장 규모가 크고 악명 높은 도박 중심지들이 설명할 수 없는 이유로 누락되었기 때문이다:\n\nCSGOJackpot.com: 연방 기소 위협을 받아 문을 닫기 전까지 수억 규모의 거래량을 처리했던, ‘스킨 잭팟’의 역사적인 선구자.\nCSGOShuffle.com: 2016년 7월 스트리밍 스캔들의 중심이 된 이곳은, 트위치 스트리머 PhantomL0rd가 몰래 이 회사의 지분 33%을 보유하고 있었으며, 회사 자금을 이용해 배당률을 조작한 사실이 드러난 곳이다.\n매크로 생태계 (200개 이상의 사업자): Narus Advisors와 Eilers & Krejcik Gaming이 실시한 업계 조사에 따르면, 2016년에는 200개 이상의 개별 스킨 도박 사이트가 운영되었으며, 303만 명의 활성 이용자로부터 $5.01십억의 베팅 규모를 창출했습니다. Valve의 43개 서한은 활성 시장의 20% 미만에 불과한 부분을 다루었습니다.\nSteam 스킨 도박에 대한 정부 및 규제 당국의 공식 조사\n\n‘스킨 도박’ 현상은 여러 공식적인 법적 조사, 집행 조치 및 정부 입장문 등을 통해 기록되어 있습니다:\n\n1. 워싱턴주 도박위원회(WSGC) (2016–2018)\n\n2016년 10월 5일 공식적인 중단 및 철회 요구를 발령했으며, 2018년 1월 30일에는 스킨이 현금과 동등한 가치임을 입증하고 $5.0B 규모의 스킨 베팅 거래량을 보고한 ‘입법 브리핑’을 발간했다.\n\nWSGC 입법 보고서 PDF (로컬 사본) ↗\n2. 미국 연방거래위원회(FTC) (2017년 9월, 사건번호 C-4632)\n\nCSGOLotto 운영자인 트레버 마틴과 토마스 캐셀을 상대로, 기만적 행위 및 플랫폼 통제권 미공개와 관련된 스킨 도박 사건에 대해 연방 당국이 처음으로 규제 집행 조치를 취했다.\n\nFTC 결정 및 합의 명령 ↗\n3. 영국 도박위원회(UKGC) 입장문 및 청소년 대상 감사\n\n2005년 도박법에 따라 게임 내 스킨을 공식적으로 “금전 또는 금전과 동등한 가치”로 분류했다. 이후 실시된 설문조사 결과, 11~16세 아동 중 11% 이상이 비디오 게임에서 스킨을 걸고 내기를 한 적이 있는 것으로 나타났다.\n\nUKGC 연구 저장소 ↗\n4. 호주 상원 환경·통신 특별조사위원회 (2018)\n\n연방 의회 보고서: \"운에 따라 획득하는 아이템을 위한 게임 내 소액 결제\", Valve의 전리품 상자 시스템, 2차 시장 현금화, 규제 회피 관행을 평가한다.\n\n호주 의회 조사 ↗\n미결제 수요\n\n단속 기록을 공개하십시오: 어떤 도박 계정과 봇이 차단되었는지, 어떤 리턴 호스트가 제한되었는지, 그리고 어떤 상업적 서비스에 허가가 부여되었는지 등을 명시하십시오. 공개적인 금지 조치와 홈페이지 경고만으로는 해당 운영이 중단되었다고 단정할 수 없습니다.\n\nB부 — 규정 및 집행 실적 · 제12조\n호스트명은 이미 요청에 포함되어 있습니다.\n문맥 및 출처 제한\n\nValve은 이미 도메인 목록(링크 필터)을 유지하고 있으며, 모든 OpenID 요청에서 인증 호스트명을 수신하고 있습니다. 아래의 의사코드는 이 두 가지를 연결하는 논리적 구조를 보여줍니다. Valve이 이를 수행한다는 공개적인 증거는 없습니다.\n\nValve은 이미 도메인 차단 목록을 운영하고 있다. Valve은 이미 모든 OpenID 요청에서 로그인 호스트 정보를 수신하고 있다. 별도로 만들 필요는 없습니다. 이 둘을 결합하기만 하면 됩니다. 이는 Valve이 자체적으로 관리하는 목록을 대상으로 하는 호스트명 조회입니다. 아래의 의사코드는 예시일 뿐, Valve의 구현 방식은 아닙니다.\n\nforensic_autoban.py\n# 예시용 의사코드 — Valve.block_domain() 및 flag_session_as_mitm()은 실제 API 호출이 아닙니다. 이는 프록시 인증 도메인에 대해 Valve이 구현할 수 있는 완화 조치의 논리적 구조를 보여주는 것이며, 실제 Valve의 내부 구현을 나타내는 것이 아닙니다.\n# 그림: 수신된 OpenID 요청에 대한 검증의 논리적 구조\ndef audit_openid_request(요청):\nblocked_origins = database.get_blacklisted_platforms()\nproxy_domain = request.params.받다('openid.realm')\ntarget_redirect = request.params.받다('openid.return_to')\n\n# 논리: 프록시가 차단된 사이트로 다시 연결하는 경우, 해당 프록시를 차단한다.\n~을 위해 사이트 에서 blocked_origins:\n만약 사이트 에서 target_redirect:\nValve.block_domain(proxy_domain)\nValve.flag_session_as_mitm(request.session)\n# 결과: 해당 호스트에 대한 로그인 요청이 거부되었습니다\n\n관찰 결과:\n메인 도메인이 이미 링크 필터에 등록되어 있는 경우(예: howl.gg, 차단된 2026-09-18/19/21)에 이미 등록되어 있고, 해당 사이트의 로그인 버튼에서 전송된 OpenID 요청에 인증 호스트(howl.uno)가 나타나는 경우, Valve은 자체 요청 데이터를 통해 이 연관성을 확인할 수 있습니다. 이 확인 작업은 자동화할 수 있지만, 실제로 실행될지는 보장할 수 없습니다.\n기록 및 보고된 선례\n\nValve은 기록상 적어도 한 번은 제3자 운영사에 대해 조치를 취한 바 있다. 2018년에는 ExpressTrade 시스템을 통해 OPSkins의 접근 권한을 박탈했다(Valve의 발표 ↗ 보관됨 2026-03-07 ↗). 2018년의 커뮤니티 보고서에 따르면, 한 마켓플레이스(SkinJar)가 접속 권한을 상실한 사례도 언급되어 있습니다. 다만 해당 보고서는 확인되지 않았으며, 그 원인은 공개된 절차가 아닌 결과로부터 추론된 것입니다.\n\n이 판례가 확립한 바는 다음과 같다:\n\nValve는 원할 때 제3자 운영자의 접속을 차단할 수 있다. 2016년 7월 공지 사항에 대한 언론 보도에 언급된 CSGOFast는 2026-09-21에서 운영되고 있었으며, 2026-06-30에 등록된 인증 호스트는 링크 필터 차단 결과를 반환하지 않았다. 왜 한 운영자는 접속이 차단되었고 다른 운영자들은 그렇지 않았는지에 대해서는 공개된 기준 어디에도 설명되어 있지 않습니다.\n\n등록일자로 알 수 있는 것과 알 수 없는 것\n\n인증 호스트의 등록 날짜는 해당 호스트가 OpenID 요청에 처음 등장했을 수 있는 시기의 하한을 나타낼 뿐이며, 지속적인 사용을 입증하는 것은 아닙니다. sc-auth.net예를 들어, 2019-04-02(RDAP)로 등록된 이 도메인은 2026년 9월 Skin.Club의 Steam 로그인 흐름에서 확인되었으나, 이 두 날짜 사이에 무슨 일이 있었는지는 공개 기록에 나와 있지 않습니다.\n\n비교 감사: API 준수 기준\n집행 측면\tGitHub API 규칙\tSteam 웹 API (Valve)\n1. 규정 준수 중립성\t공표된 통일된 규칙. 문서화된 요청 제한(예: 인증된 사용자의 경우 시간당 5,000회, GitHub Enterprise Cloud 조직의 경우 시간당 15,000회) 및 공표된 이용 약관이 모든 계정에 적용됩니다.\t공개된 기준은 없습니다. 개별 계정은 자동화 및 상업적 이용 관련 조항(보관된 신고 내역)에 따라 해지되지만, 상업용 플랫폼에 대한 운영자별 제재 기록은 공개된 바 없습니다.\n2. OpenID / 인증 프록시 악용\tGitHub가 공개한 정책에 따르면, OAuth 앱 및 토큰은 악용 시 일시 정지되거나 취소될 수 있으며, 관련 문서에는 노출된 토큰의 자동 취소 절차가 설명되어 있습니다(저자들이 GitHub 문서를 요약한 내용).\tSteam개의 OpenID 흐름에서 관찰된 별도 도메인 인증 호스트(예: rbsnin.com, howl.uno, sc-auth.net)는 2026-09-21에서 Link Filter 차단이 발생하지 않은 반면, 해당 호스트의 메인 도메인에서는 차단이 발생했습니다.\n3. 학대를 통한 수익 창출\tGitHub는 제3자 자동화 도구를 통해 이동된 항목에 대해서는 거래 수수료를 부과하지 않으며, 수익 모델은 구독 서비스와 마켓플레이스 상품 등록 수수료로 구성됩니다.\tValve은 해당 아이템을 획득할 수 있는 케이스 키를 판매하며, 커뮤니티 마켓은 마켓 내에서 성사된 거래에 대해 총 15% 정도의 수수료를 부과합니다. 제3자 플랫폼을 통해 발생한 매출액은 여기에서 추산하지 않았습니다.\n4. 회피 루프의 지속 시간\t정지된 OAuth 클라이언트 ID는 정지 시점에 플랫폼 전체에서 작동이 중단됩니다. 문서에는 조치 소요 시간에 대한 수치가 명시되어 있지 않으며, 본 문서에서도 이를 가정하지 않습니다.\t2011년부터 2026년 9월까지 등록된 별도 도메인 인증 호스트의 경우, 2026-09-19 및 2026-09-21 검사에서 링크 필터 차단 결과가 나타나지 않았습니다. 등록일은 사용 가능 기간의 하한을 나타낼 뿐, 지속적인 사용을 입증하는 것은 아닙니다.\n출처: GitHub 칼럼 — GitHub가 공개한 API 사용량 제한 및 플랫폼 정책 문서 (저자의 요약, 인용 아님) · Steam 칼럼 — 2026-09-19 및 2026-09-21에 대한 링크 필터 검사 (linkfilter-recheck-2026-09-21.json), RDAP 레지스트리 (domain-registration.json) 및 보관된 지원 문의 내역 (증거 보관소).\nB부 — 규정 및 집행 실적 · 제13조\n0을 제외한 가격 차이\n\n해당 아이템은 Steam 인벤토리에 보관되어 있으며, 판매는 다른 곳에서 이루어집니다. 공장 출고 상태의 AWP Dragon Lore는 CSFloat에 게시된 62건의 실시간 제안; 가장 저렴한 가격 $10,623.95. Steam의 자체 시장에서는 매도 호가를 약 $1,800 이상으로 표시할 수 없다. 관측된 더 높은 가격에 판매하려면 소유자는 Steam 외부의 구매자나 거래소가 필요하다. 해당 품목과 그 양도는 여전히 Steam에 의존한다.\n\nWhat this means — the Community Market listing ceiling\n\nSteam’s own market refuses a listing above roughly $1,800. A seller may ask less, never more. Items whose market price sits above that line therefore cannot be sold at that price on Steam at all — which is the mechanism that moves those sales to third-party venues while the item itself never leaves Valve’s inventory system.\n\nSection 13 — the off-Steam price gap →\n\n문맥 및 출처 제한\n\n이 섹션에는 세 가지 다른 카운트가 등장하며, 이들은 서로 대체할 수 없습니다. 245 2026년 9월 20일, CSFloat 단독 기준으로 가장 저렴한 활성 오퍼가 $1,800을 초과한 CS2 상품명 카테고리의 수입니다. 241 이는 CSFloat의 $100,000 상한선에 고정된 네 가지 범주를 제외한 동일한 집합으로, $13.63M 하한선이 계산되는 패널입니다. 248 이는 또 다른 현황을 보여주는 자료로, 2026년 9월 23일 기준 5개 마켓플레이스 중 2곳 이상에서 상한가를 초과한 가격으로 거래된 카테고리들을 나타냅니다. 마켓플레이스 간 중복이 있으므로, 서로 다른 플랫폼의 수치를 절대 합산해서는 안 됩니다. 여기에 제시된 모든 수치는 매도 희망 가격일 뿐, 실제 성사된 거래가 아니며, Valve이나 그 누구에게도 매출, 거래액 또는 이익으로 간주될 수 없습니다. PriceEmpire에 기재된 수치는 해당 사이트에서 발표한 반올림된 추정치이며, Steam 카드는 다른 Steam 게임의 아이템도 포함하고 있으므로, 비교 대상의 범위가 완전히 동일하지는 않습니다.\n\n한 가지 품목. 두 가지 가격 체계.기록을 따라가 보세요\n단계 3 / 3\n\n그 요청에 따라 판매자는 Steam 외부의 거래처나 구매자가 필요합니다. 해당 상품은 여전히 Steam의 재고 및 이전 시스템에 따라 결정됩니다.\n\nSTEAM$1,800 정보공개된 커뮤니티 마켓 등록 한도\n저장된 카탈로그$10,623.95공장 출고 상태의 AWP Dragon Lore, 가격 문의\n의존성아직 Steam개 남은 상품재고 및 이체는 Steam 상태로 유지됩니다.\n01 / 상품Valve 게임 아이템 목록CS2 또는 Dota 2 아이템이 Steam에 보관되어 있음\n02 / 천장$1,800에 대한 Steam마켓 등록 건당 최대 가격\n03 / 외부 문의$10,623.95 (드래곤 로어)해당 날짜의 스냅샷에서 가장 저렴한 CSFloat 제안\n04 / 배송Steam이 체인에 남아 있습니다소유권 및 아이템 양도는 해당 시스템에 따라 결정됩니다.\n시장 구조 · 특정 시점의 현황, 20 9월 2026\n가격 차이는 수치로 측정할 수 있다.\n\n가장 저렴한 유효 오퍼 가격이 $1,800.보다 확실히 높은 상품명 카테고리를 집계했습니다. CSFloat 및 Skinport는 CS2 재고가 중복되는 별도의 스냅샷이므로, 이들의 집계 수치를 합산할 수 없습니다. 외부 오퍼는 더 높은 매도 가격이 게시된 곳을 보여주는 반면, Steam는 여전히 상품 소유권 및 양도를 관리합니다.\n\n245CS2 카테고리 · CSFLOAT\n166CS2 카테고리 · 스킨포트\n3DOTA2 카테고리 · SKINPORT\n$10,623.95드래곤 전설 층 관련 문의\n\nDragon Lore: 62 현재 ‘Factory New’ 카테고리에서 CSFloat 건의 상품이 등록되어 있습니다. 표시된 가격은 요청 가격이며, 확정된 판매 가격이 아닙니다. Steam에서는 해당 상품을 더 낮은 가격에 등록할 수는 있으나, 확인된 더 높은 요청 가격은 게시할 수 없습니다. Valve의 2016 성명서는 OpenID 및 Steam 거래 인프라를 사용하는 도박 사업자에 대해 인지하고 있음을 확인합니다. 특정 제3자 마켓플레이스가 Valve의 규정을 위반했는지 여부는 별도로 확인되어야 합니다.\n\n전체 등록 내역 확인 →CSFloat JSON ↗Skinport JSON ↗Valve의 ‘2016’ 성명서 ↗\nDIRECT CSFLOAT API / 날짜 지정 스냅샷$13.63M\n\n최소 총 호가 금액은 241개 품목 카테고리 그리고 3,395 진행 중인 혜택. 각 카테고리의 최저 매도 호가 × 해당 호가의 건수를 곱하여 산출됩니다. CSFloat의 $100,000 상한선에 고정된 4개 카테고리는 이 보수적인 패널에서 제외됩니다.\n\n이 금액이 시사하는 바\n\n이러한 제안은 최소한 $13,631,888.25 이 한정된 CSFloat 하위 집합에 대해 게시된 호가들을 기준으로 할 때, 최고가 범주에 속하는 네 가지 범주를 포함하면 $14,231,888.25. 이것은 활성 요청에 대한 바닥가, 판매 실적, 현금 매출액, 이익 또는 CS2 시장 전체가 아닙니다.\n\n245행짜리 CSFloat 스냅샷을 기준으로 재계산 ↗\nPRICEEMPIRE / 등재 가격Steam: 39개 중 15번째\n많은 공연장에서는 Steam보다 더 높은 금액을 명시하고 있습니다.\nUUSkins\n$133.8M\nYouPin898\n$127.5M\nBuff.163\n$104M\nMoon.Market\n$100.3M\nWhite.Market\n$89.6M\nBuff.Market\n$86.7M\nSteam\n$31M\n\n표시된 값 중 가장 큰 6개와 Steam. PriceEmpire는 이 수치를 반올림하며, Steam은 $31M. 표시된 달러 금액 기준으로 이보다 순위가 높은 상장된 경기장이 14곳 있습니다.\n\nPRICEEMPIRE / 제안 수Steam: 39개 중 1번째\nSteam은 여전히 제안 건수에서 선두를 달리고 있다.\nSteam\n3,220만\nYouPin898\n5.9M\nC5Game\n460만\nHaloSkins\n440만\n스킨포트\n3.8M\n\nSteam 표시 3,220만 제안 건수. 제안 건수와 총 매도 희망가는 서로 다른 정보를 보여줍니다. 저가 매물이 많으면 제안 건수에서 큰 비중을 차지할 수 있습니다.\n\n출처: PriceEmpire의 공개 비교 ↗ 보관됨 2026-09-21 ↗, 2026-09-20 19:03 UTC에 캡처됨; 39행 추출 날짜 ↗. 이 수치는 반올림된 추정치이며, 재고는 여러 사이트에 걸쳐 중복될 수 있습니다. Steam의 카드에는 다른 Steam 게임의 아이템도 포함되어 있으므로, 해당 범위는 완전히 일치하지 않습니다. 표기된 값은 판매량이나 매출이 아닌 호가를 나타냅니다.\n42\n다른 출처 / STEAMANALYST\n상업 생태계는 누구의 눈에도 뻔히 드러나 있습니다.\n\nSteamAnalyst의 마켓플레이스 디렉토리 보관됨 2026-07-19 ↗ 이 목록에는 Steam을 비롯해 42개의 제3자 CS2 마켓플레이스가 포함되어 있으며, 43개 항목 중 32개에 대한 최근 가격 데이터가 제공됩니다. PriceEmpire는 자체 선정 기준에 따라 39개의 마켓플레이스를 목록에 포함시켰습니다. 명명된 업체, 공개된 상품, 확인 가능한 가격: 이 경제는 누구나 살펴볼 수 있습니다.\n\n한계가 바로 그 구조다: 판매는 스팀을 떠나지만, 아이템은 그렇지 않다.\n\n하나의 라이선스 스냅샷에 포착된 5개 마켓플레이스 전반에 걸쳐, 248개의 CS2 상품 카테고리는 Steam의 약 $1,800에 해당하는 상한선보다 2개 이상의 항목에서 독립적으로 가격이 책정되어 있으며, 이 중 단 하나도 Steam에는 포함되어 있지 않습니다.. 동일한 스냅샷은 전체 카탈로그를 가격대별로 분류했는데, Valve의 마켓플레이스는 상한선 미만의 품목 카테고리를 95.3%개, 상한선 이상의 카테고리를 1.9%개 취급하고 있다. 이러한 축소 현상은 수요 감소와 무관하며, 정확히 공개된 규칙에 부합한다. 이러한 가격으로 판매하려면 외부 구매자나 마켓플레이스가 필요하지만, 재고와 이송은 여전히 Steam가 관리합니다. 즉, 거래는 Valve의 결제 단계를 거쳐 나가지만, 배송은 Valve의 인프라를 통해 이루어집니다.\n\nSteam 시장 FAQ ↗보관됨 2026-09-21 ↗Steam 가입자 계약서 ↗보관됨 2026-09-21 ↗5개 마켓플레이스 아틀라스 데이터셋 ↗유래 명세서 ↗이전 CSFloat 스냅샷 ↗Skinport 개요 ↗PriceEmpire ↗보관됨 2026-09-21 ↗SteamAnalyst ↗보관됨 2026-07-19 ↗가격 차이 레지스터 ↗가격 단계별 지도 ↗\n\nC부 — 법적 체계\nC부 — 법적 체계 · 제14조 · 인원의 출입\n누가 안전장치를 재설정할 수 있나요?\n문맥 및 출처 제한\n\n계정 보안은 계정을 복구하거나, 비공개 기록을 열람하거나, 보안 조치를 재설정할 수 있는 사람들에 의해서도 좌우됩니다. 조사 과정에서는 API 남용 사례를 추적하는 것만큼이나 이러한 특권적 조치들을 면밀히 추적해야 합니다.\n\n계정 복구 기능은 지원 담당자에게 계정 소유자로부터 계정을 분리할 수 있는 권한을 부여합니다. Valve은 2023년 2월과 2025년 11월, 두 차례에 걸쳐 서면으로 이 권한이 계정을 잘못된 사람들에게 넘기는 데 사용되었음을 확인했다. 33개월 간격으로, 동일한 경로를 통해. 아래에서는 그 접근 권한의 가치, 출처가 확인된 6건의 사례, 그리고 ‘Valve’ 로그가 이들 모든 사례에 적용되지만 누구에게도 제공되지 않았다는 점을 다룹니다.\n\n보존된 증언 / 2025년 5월 9일\n계정의 보안 기능을 비활성화한 복구 티켓과, $10,000의 손실이 보고됨\n\n수집된 지원 아카이브에 있는 한 사용자는, 다른 사람이 복구 요청을 제출한 후 Steam 지원팀이 비밀번호를 재설정하고 계정 보호 기능을 비활성화했다고 보고했습니다. 작성자에 따르면 해당 계정은 수년 동안 비활성 상태였으며, 2016~2017년부터 아이템이 보관되어 있었고, Steam Guard, 연동된 휴대폰 번호 및 저장된 복구 코드를 보유하고 있었다고 합니다.\n\n\"Steam 고객 지원팀에서 여전히 다른 사람에게 제 계정에 대한 접근 권한을 부여했습니다.\"\n\n1인칭 주장, 다음 자료에 기록되어 있음 steam_support_tickets_MEGA.json, 기록 110. 캡처된 게시물 전문 보기 ↗\n\n이는 한 사용자의 불운 때문이 아닙니다. 아래 장부에 기록된 모든 사례에서, 계정을 더 오래된 데이터를 제공하는 사람에게 이전해 달라는 지원 요청이라는 동일한 절차가 공식적인 처리 방식이며, Valve은 이를 두 차례에 걸쳐 서면으로 명시했습니다.\n\n주인은 그 논쟁에서 이길 수 없다. 복구 절차에서는 첫 번째 CD 키, 첫 번째 이메일, 첫 번째 카드, 첫 번째 전화번호를 요구합니다. 이러한 정보는 Valve의 데이터베이스에 저장되어 있으며, 지원팀 측에서 이를 조회할 수 있는데, 보고에 따르면 최대 15년 전까지 거슬러 올라간다고 합니다. 여러분의 파일 사본을 보유한 사람은 언제나 여러분이 알 수 있는 것보다 더 많은 과거 기록을 제시할 수 있습니다. 표적은 특정 조건에 부합하도록 선정되었습니다. 수년간 활동이 없었고, 가치가 높으며, 종종 중고로 구매되어 소유자가 원래 키를 알지 못하는 경우였습니다. 이후 계정은 완전히 삭제되어, 커뮤니티가 스킨의 출처를 추적하는 데 사용하는 아이템 이력 흔적이 끊어졌습니다. 일반 사용자는 정해진 대기 기간을 거치지 않고는 이러한 삭제를 수행할 수 없습니다.\n\n최소 권한 원칙 / OWASP A01\n\n복구 권한은 해당 작업으로만 제한되어야 하며, 별도로 검토되고 기록되어야 합니다. 자격 증명을 재설정하거나, Steam Guard을 제거하거나, 청구 내역을 조회하거나, 계정 데이터를 내보낼 수 있는 사용자를 감사해야 합니다. OWASP 접근 제어 지침 ↗ 보관됨 2026-09-20 ↗\n\n광범위한 지원 접근성접근 범위 관련 위험\n재고 그 이상.\n\n광범위한 지원 접근 권한이 악용될 경우, 비공개 텔레메트리 데이터는 프로파일링, 표적형 피싱 및 감시를 위한 수단이 될 수 있습니다. 잠재적 피해자에는 일반 사용자, 군인, 공인 및 그 가족들이 포함됩니다. 이는 위협 모델이며, 정확한 권한 설정에는 접근 제어 기록이 필요합니다.\n\n01 IP 기록 및 위치\nIP 로그를 통해 네트워크 이용 내역과 대략적인 위치를 파악할 수 있습니다. 그러나 IP 로그만으로는 정확한 물리적 이동 경로를 파악할 수는 없습니다.\n02 기기 지문 인식\n수집되고 접근 가능한 기기 식별자는 세션과 계정을 연결할 수 있습니다.\n03 활동 텔레메트리\n로그인 타임스탬프와 세션 기록은 공개 프로필에서는 확인할 수 없는 활동을 포함해 사용자의 일상적인 행동 패턴을 드러낼 수 있습니다.\n04 홍보 및 연락처\n저장된 메시지나 연락처 정보에 접근할 수 있게 되면 프로파일링 및 사회공학적 공격의 범위가 확대될 것입니다.\n05 정체성 폭로\n원본 이메일, 전화번호 및 결제 기록을 통해 가명 계정을 특정 개인과 연결할 수 있습니다.\n06 데이터 재판매 및 책임\n수출된 대상 목록은 표적형 사기를 조장할 수 있습니다. 행위자, 접근 위치, 수신자 및 송금 내역을 명확히 파악해야 합니다. 위치 정보만으로는 접근 사실이나 법적 면책권을 입증할 수 없습니다.\n\nValve는 자사의 정책에서 IP 기록, 기기 정보, 결제 내역 및 제3자 지원 제공업체에 대해 설명하고 있습니다. 개인정보 처리방침 제3조, 제5.2조 보관됨 2026-09-21 ↗. 이 정책은 제3자의 지원 접근을 허용하고 있으나, 어떤 계약자가 언제, 어떤 권한에 따라 어떤 범주에 접근했는지를 보여주는 감사 기록은 공개되지 않았다.\n\n제14.1절 · 등록부 · 2022년 6월 → 2025년 11월 · 모든 그림의 출처 명시\nValve는 33개월 간격을 두고 두 번이나 문을 열었다. 문은 결코 닫히지 않았다.\n\nSteam의 자체 도움 요청 채널이나 해당 채널이 보호하는 인증 정보를 통해 계정이 탈취된 사례 6건이 보고되었습니다. 각 금액은 인용된 출처가 공개한 수치이며, 각 출처의 이름도 명시되어 있습니다. 6건 중 2건은 전액 보상받았습니다. 이 두 건과 나머지 사례의 차이는 사건의 내용 자체가 아니라, 누가 지켜보고 있었는지에 있었습니다.\n\nValve, 서면 — 2023년 2월\"해당 아이템들은 지원 요청을 통해 해킹당한 계정으로부터 전달받은 것이기 때문에 귀하의 계정에서 제거되었습니다. 이에 대한 책임은 CS:GO 팀이 지겠습니다. 저희는 해당 거래를 취소하고, 해당 아이템을 수령한 모든 계정에서 이를 제거했습니다.\"Steam HFB 상품 수령인에게 보내는 지원 답변, 다음에서 인용: Dexerto, 2023년 2월 21일 ↗ 보관됨 2025-08-18 ↗\nValve, 다시 글을 쓰며 — 2025년 11월 · 33개월 후\"해당 지원 요청을 처리한 지원 담당자가 당사의 절차를 준수하지 않아, 귀하의 계정이 다른 사람에게 복구되는 결과가 발생했습니다. 이 오류로 인해 불편을 드려 죄송합니다.\"Steam Hawkeye337에게 보낸 답변, 인용된 내용: Dexerto, 2025년 11월 14일 ↗\n2022년 6월 21일\nHFB — 게임 내 최대 규모의 아이템 목록$2,000,000+ · 2023년 2월 후속 조사에서 $3,000,000+로 상향 조정됨\n\n세븐 수버니어 AWP 드래곤 로어 7개와 1위 블루 젬 카람빗, 그 칼 하나만 해도 가치가 약 $1.26백만. 해당 계정은 3년 동안 활동이 없었지만 모바일 인증기는 여전히 활성화된 상태였으며, 어쨌든 고객 지원 복구 절차를 통해 이메일과 비밀번호가 변경되었습니다.\n\n물건들이 떠나기 전에 돈이 먼저 사라졌다. 보도에 따르면 $200,000+ 판매 대금의 일부는 이미 현금과 암호화폐로 결제되는 마켓플레이스인 market.csgo.com을 통해 인출되었습니다. 거래를 취소하면 스킨이 반환됩니다. 하지만 이미 계좌에 입금된 현금은 반환되지 않습니다.\n\n그런데 수정 사항이 제대로 작동하지 않았습니다. 한 구매자가 자신의 ‘Souvenir Dragon Lore’를 게임 내 보관함으로 옮겼습니다. Valve의 롤백 스크립트는 해당 컨테이너 내부를 확인할 수 없었기 때문에, 소유자에게 새로운 사본을 발급하고 숨겨진 사본은 그대로 남겨두었습니다. — Valve은 $130,000 도난을 되돌리려던 과정에서 해당 아이템이 발견되었습니다. 아이템 ID 대조와 커뮤니티 제보를 통해 적발되었으며, 한 달 뒤인 2022년 7월에 삭제되었습니다. 구매자에게는 Valve가 아닌 BUFF가 환불을 처리했습니다. 이처럼 허술한 긴급 대응은 통제 수단이 아닙니다. 이는 플랫폼이 통제력을 상실했을 때 취하는 조치일 뿐입니다.\n\nDexerto, 2022년 6월 21일 ↗ 보관됨 2022-07-02 ↗ · 카스퍼스키 ↗ · 건당 현금 인출 금액 Esportfire, 2022년 6월 22일 ↗ 보관됨 2026-05-15 ↗, 해당 글에서는 여러 트위터 소식통을 인용함 · 중복 및 삭제는 다음 규정에 따라 Esportsbetting, 2022년 7월 14일 ↗\n\n복원됨거래가 취소되었다. 정가를 지불하고 구매한 사람들의 재고에서 해당 품목들이 다시 회수되었다.\n2022년 8월 14일\nCS.Money — 플랫폼 자체 봇$6,300,000 · 19,000+ 스킨 · 초기 추정치 $1.6M\n\n공격자들은 해당 마켓플레이스의 트레이딩 봇에 저장된 모바일 인증기 파일을 탈취해 내용을 모두 지운 뒤, 흔적을 감추기 위해 탈취한 자산의 일부를 유명 트레이더들에게 보냈다. 커뮤니티 연구원들은 이를 분석하여 몇 시간 만에 55개의 공격자 계정 그리고 이를 출판했다.\n\nValve은 아무런 조치도 취하지 않았다. 그 이유는 제3자 사이트가 Steam 외부에 위치해 있기 때문이었는데, 바로 이 Steam에서 도난 사건이 인벤토리, 거래 API 및 계정 시스템을 통해 종단 간으로 진행되었다.\n\nEsportfire, 2022년 8월 14일 ↗ 보관됨 2025-11-15 ↗\n\n거절됨반전은 없었다. 손실은 플랫폼과 그 이용자들에게 그대로 남았다.\n보고됨\n2023년 2월 21일\nQkss — 같은 문, 같은 배우$1,000,000+\n\nHFB와 동일한 방식으로, 동일한 배우가 동일한 지원 요청을 통해 처리된 것으로 보고되었습니다. HFB는 8개월 전에 완전히 해결되었으나, Qkss는 그렇지 않았습니다.\n\n하나의 길. 두 가지 답. 공개된 기록상으로는 청중의 규모를 제외하고는 두 사건을 구별할 만한 내용이 전혀 없다.\n\nDexerto, 2023년 2월 21일 ↗ 보관됨 2025-08-18 ↗\n\n거절됨복원되지 않았습니다.\n보고됨\n2023년 2월\n내부자 거래 그 자체 — 1년 동안의 내부자 거래≈ $320,000 · 약 1년에 걸쳐 진행되며, 재고 평가가 아닙니다.\n\n지원 측에서 최대 ~까지의 계정 내역을 조회했습니다. 15세 — 첫 번째 CD 키, 첫 번째 이메일, 첫 번째 카드. 이것이 바로 복구 절차에서 요구하는 증거이며, 그렇기 때문에 데이터베이스를 보유한 사람은 계정 소유자와의 논쟁에서 항상 승리하게 된다.\n\n블로거 Mzkshow는 내부 운영자 “Steam Help”와 공범 “Alexander”가 $100k 이상의 스킨을 보유한 비활성 계정을 표적으로 삼은 사실을 폭로했습니다. iBUYPOWER와 Titan Katowice 2014 홀로그램이 적용된 도난당한 M4A4 Howl 한 정은 $35,000 결국 이 일은 NAVI의 발레리 “b1t” 바호브스키에게로 넘어갔는데, 그는 이 사실을 전혀 알 길이 없었다. Valve이 개입한 후, 해당 계약업체는 Steam 고객 지원팀 전원을 해고했다.\n\nVKPlay ↗ · Lis-Skins ↗ · Escorenews (RU) ↗ · Dexerto (EN) ↗\n\n등록되지 않음Valve은 이로 인해 영향을 받은 계정 수가 몇 개인지 공개한 적이 없으며, 영향을 받은 사람들에게도 알리지 않았다.\n보고됨\n2024년 12월 2일\n\"마트베이\" — 해고 사태 이후$13,000\n\n계정 소유자 본인조차 일치시킬 수 없었던 계정 정보를 제공한 사람에게 계정 복구 권한이 부여되었다. 계약업체가 Steam 지원 데스크를 정리한 지 2년이 지난 후에도, 동일한 절차를 통해 동일한 결과가 나왔다.\n\n보존된 게시물, 2024년 12월 2일 ↗ 보관됨 2025-08-05 ↗ · 소스 행 및 해시 ↓\n\n거절됨복원되지 않았습니다.\n2025년 11월 13일\nHawkeye337 (마크 스퍼록) — 그리고 두 번째 고백≈ $300,000–$500,000 · 2014 카토비체 홀로그램 컬렉션 전작\n\n공격자는 다음과 같이 요구했다 1 비트코인 그리고 해당 컬렉션을 네게브(Negevs)로 옮겨서 삭제하기 시작했습니다. Steam 지원팀의 서면 답변은 위에서 언급한 두 번째 인정 사항입니다. 즉, 한 기술자가 지원 요청을 처리했으나 절차를 따르지 않고 해당 계정을 다른 사람에게 넘겼다는 것입니다.\n\n이 문제를 해결한 것은 피드였습니다. X에 Valve을 태그한 게시물이 올라온 지 몇 시간 뒤, 해당 계정은 복구되었고 모든 스티커가 복원되었습니다. Qkss에는 그만큼의 팔로워가 없었습니다.\n\nSkin.club ↗ · Dexerto ↗ · Esportfire ↗ 보관됨 2025-12-17 ↗\n\n복원됨해당 기사가 화제가 된 지 몇 시간 만에 기사가 삭제되었다.\n장부에는 기록되어 있지만, 개별 사례 하나만으로는 알 수 없는 사실.\n\n그 노선은 한 번도 운행이 중단된 적이 없습니다. 첫 번째 입원 날짜는 2023년 2월이고, 두 번째는 2025년 11월입니다 — 33개월 차이로, 그 사이에는 계약업체의 대량 해고, 기록에 남은 재발 사례, 그리고 $6.3백만 규모의 플랫폼 보안 침해 사건이 발생했습니다. 이 장부에 기록된 첫 번째 절도 사건부터 계산하면, 해당 채널은 3년 5개월. 2023년에 무엇이 수정되었든 간에, 2025년 11월에도 여전히 해당 지원 요청이 계정을 잘못된 담당자에게 배정하는 오류가 발생했습니다 — Valve의 직접 인용문.\n\n배상은 피해가 아닌 관심을 기준으로 삼았다. 복원됨: 게임 내 최대 규모의 아이템 목록과, 관련 게시물이 화제가 되었던 수집가. 거부됨: $1,000,000,, $6,300,000,, $13,000. Valve은 해당 규칙을 공개한 적이 없는데, 규칙을 공개하면 이 세 가지를 설명해야 하기 때문이다.\n\n아무도 그 사실을 알지 못했다. 데이터베이스에서 계정 내역이 유출된 사용자들도 아니고, 감독 당국도 아니며, 선의로 해당 상품을 구매했다가 회수당한 시장도 아닙니다. 침해 통지도, 사고 보고서도, 피해를 입은 계정 수에 대한 집계도 없습니다 — 그리고 현금으로 남은 수익금, 현금과 암호화폐로 대금을 지급하는 마켓플레이스를 통해 이루어집니다. Steam에서 자금이 유출된 후에는 거래 취소가 불가능합니다.\n\nValve에는 지원 감사 기록, 복구 티켓 로그 및 위의 모든 행에 대한 거래 기록이 포함되어 있습니다. 이 중 어느 것도 생성되지 않았습니다. 나만의 사본을 요청하세요 →\n\nNDA 관련 질문\n기밀 유지는 기술적 책임과 함께 이루어져야 합니다.\n\n기밀 유지 계약서를 실제 권한, 수출 통제, 재설정 승인 및 접근 로그와 비교해 보십시오. 미리 정해진 답변만으로는 복구 절차 자체가 남용되었다는 주장을 해소할 수 없습니다.\n\nGDPR 제28조, 제32조~제34조\n\n제33조는 개인정보 처리자에게 개인정보 침해 사실을 감독 기관에 통보할 수 있는 기간을 72시간으로 정하고 있으며, 제34조는 피해자에게 미치는 위험이 높은 경우 해당 사실을 피해자에게 알려야 한다고 규정하고 있다. Valve는 자사의 지원 채널을 통해 계정 정보(거래 내역, 청구 내역 등 모든 정보 포함)를 잘못된 사람에게 전달했다는 사실을 두 차례에 걸쳐 서면으로 확인했다. 두 조항에 따른 공지는 게시된 바 없으며, 해당 사용자로부터 공지를 받았다는 보고도 접수되지 않았습니다. 규정 읽기 ↗ 보관됨 2026-09-20 ↗\n\n요청에 지원 문의 내용을 포함해 주세요 →\nC부 — 법적 체계 · 제15조 · 상업적 규모\n자금 흐름을 추적하라. 거래 내역을 분리하라.\n문맥 및 출처 제한\n\n자금 흐름이 분리되면 상업적 이용 여부에 대한 의문이 더욱 선명해집니다. 제3자를 통한 상품 양도, Valve의 주요 판매 및 외부 현금 인출은 서로 다른 거래입니다.\n\n해당 품목은 Valve개입니다. 재고는 Valve개입니다. 전송 작업은 Valve대의 서버에서 실행됩니다. 결제만 다른 곳에서 이루어질 뿐입니다 — 바로 이 단계가 누군가가 자금 송금업자인지 여부를 결정하는 단계이며, Valve은 이 단계를 이행하지 않습니다.\n\n수익 창출 방식\n돈이 실제로 오가는 곳.\n세 가지 경로 / 하나의 아이템 경제\n01 / 계정사용자 인벤토리\n\nSteam에 소장된 자료\n\n02 / 이적P2P 거래\n\n사용자 ↔ 봇 또는 사용자 ↔ 사용자\n\n03 / 정산외부 플랫폼\n\n사이트 잔액 또는 미납금 Steam\n\n유통이적료 이상의 경제적 동력이 있다\n\nSteam은 외부 시장에서 사용되는 재고 및 이전 인프라를 제공합니다. 이번 조사의 경제적 논거는 재판매 유동성과 반복적인 수요가 케이스, 키 및 교체 품목에 대한 지출을 유지시켜, 이후 커뮤니티 마켓 판매 시 수수료가 발생한다는 것입니다. 직접적인 P2P 양도에는 커뮤니티 마켓 수수료가 부과되지 않지만, 이러한 회계적 사실만으로는 더 광범위한 이점을 단정할 수는 없습니다. Valve는 전 과정에서 계정 접근 권한 및 거래 제한에 대한 통제권을 유지합니다.\n\n01 / 2차 수요유동성 및 재판매 가치\n\n대외 무역 및 도박 수요\n\n02 / 1차 지출열쇠, 케이스 및 캡슐\n\n해당 상품이 제공되는 경우 Valve에서 구매\n\n03 / 매출1차 판매 수익\n\n실제 시장 거래에 대한 수수료 추가\n\n5% + 10%Steam + 커뮤니티 마켓 판매 시 CS2 수수료\n\n이 연구에서 도출된 경제적 시사점: 유동적인 재판매 시장은 신상품 구매를 촉진할 수 있다. 잘 알려진 15%은 시장 수수료율을 반영한 것으로, 최저 요율과 반올림 규정이 적용되며, 모든 대외 거래에 부과되는 과세는 아니다.\n\nValve의 커뮤니티 마켓 요금표 ↗ 보관됨 2026-09-21 ↗. 2026년 2월 25일 뉴욕주 법무장관이 소송을 제기했다 보관됨 2026-09-01 ↗ 유료 전리품 상자가 외부 현금 재판매 및 도박 피해와 연관되어 있다고 주장하고 있는데, 이는 본 보고서가 기술·인프라 측면에서 입증한 바로 그 연관성이다. 해당 고발은 단정된 사실이 아닌 주장일 뿐입니다. 이 문서에 인용된 이유는, 한 주 법 집행 기관이 본 문서가 제기하는 질문과 밀접하게 연관된 의문, 즉 ‘공개된 선언과 일치하는 집행 기록은 어디에 있는가?’를 제기했기 때문입니다.\n\n01 / 시작암호화폐 입금\n\n외부 서비스 및 지갑 기록\n\n02 / 전환균형 → 스킨\n\nSteam 건의 거래를 통해 배송된 상품\n\n03 / 출구외부 법정화폐 판매\n\n판매자, 구매자 및 지급 대행업체\n\nKYC?모든 인계 시점에 제어권을 확인하십시오\n\n이것이 조사해야 할 경로이며, 네이티브 Steam API 현금 전환 서비스가 아닙니다. KYC 미적용 현금 인출을 승인하기 전에, 각 외부 운영업체의 신원 확인 절차, 자산 보관 현황, 거래 ID 및 출금 수취인을 문서화하십시오.\n\n미국 / 은행 비밀 보호법\n먼저 활동을 분류한 다음, 의무를 분류하십시오.\n\nFinCEN은 사업체의 업무 내용을 기준으로 자금 이체 여부를 평가합니다. 변환 가능한 가상화폐를 수취 및 송금하는 행위는 해당 정의 및 예외 조항에 따라 자금 서비스 의무가 발생할 수 있습니다. Valve의 Steam 월렛은 자금을 수취하여 이를 게임 내 아이템으로 변환하며, 해당 아이템은 제3자 운영사를 통해 실물 화폐로 환전됩니다. 해당 아이템 및 그 전송은 Valve의 인프라를 통해 이루어지지만, 현금화 과정은 그렇지 않습니다. 이 사이클의 어느 부분이 자금 이체 정의에 부합하는지는 FinCEN이 판단해야 할 분류 문제이며, 본 문서에서 내리는 결론은 아닙니다.\n\nFinCEN FIN-2019-G001, 제1–2조, 제5.1조 ↗ 보관됨 2025-07-11 ↗\n\n유럽연합 / 자금세탁\n자금 흐름, 정보 및 지원을 추적합니다.\n\n지침 (EU) 2018/1673은 범죄 수익을 이용한 고의적인 자금세탁 및 이에 가담하는 행위를 다루고 있습니다. 수사상 쟁점은 Valve가 2016년 7월 13일 자사의 거래 및 OpenID 인프라 사용을 공개적으로 설명한 이후, 해당 인프라를 사용하는 운영자들에 대해 무엇을 알고 있었는지, 그리고 이에 대해 어떤 조치를 취했는지입니다. Valve은 운영자별 집행 기록을 공개한 바 없으며, 이 문서가 아닌 해당 기록이야말로 이 질문에 대한 답을 제공할 것입니다.\n\nEU 형법 체계 ↗\n\nAMLD6 용어: 위의 형법 지침은 AMLD6라고도 불리는 지침 (EU) 2024/1640과는 별개입니다. 후자의 경우, 특정 예외 사항을 제외하고 2027년 7월 10일까지를 일반적인 이행 기한으로 정하고 있습니다. 제78조 ↗ 보관됨 2026-08-30 ↗\n\nC부 — 법적 체계 · 제16조 · 통지, 답변, 책임\n디지털 서비스법: 지식을 공식 기록으로 남기다\n문맥 및 출처 제한\n\n제16조 통지의 두 가지 요소, 즉 제출자 본인의 세부 정보와 정보의 정확성에 대한 선의의 진술은 본 서류에 포함되지 않고 제출자가 직접 담당합니다. 해당 조항이 요구하는 그 밖의 모든 사항 — 입증된 설명 및 정확한 전자적 위치 — 은 제3절과 경로 등록부에 저장된 응답 및 해시와 함께 명시되어 있으므로, 어느 당사자라도 이를 제출할 수 있습니다. 법률 자체에 대한 두 가지 추가 제한 사항이 있습니다. 호스팅 면제를 상실한다고 해서 그 자체만으로 다른 법률에 따른 책임이 성립되는 것은 아니며, 제52조(3)항의 6%은 법정 상한액일 뿐, Valve에 대한 산정된 벌금이 아닙니다.\n\nDSA에 따르면, 호스팅 제공업체는 구체적인 사실을 알게 되었음에도 조치를 취하지 않은 경우에만 책임 면제 혜택을 유지할 수 있다. 이 문서가 바로 그 공고입니다. 이 문서에는 호스트, 날짜, 저장된 응답 및 해시 값이 명시되어 있습니다. 이 문서가 공개된 이후로, 더 이상 Valve이 알고 있었는지 여부가 문제가 되는 것이 아니라, Valve이 그 다음에 어떤 행동을 했는지가 핵심이 되었습니다.\n\n012016년 7월 / 자료 전시\n10일간의 요구.\n\n위에서 재구성된 공고는 이번 조사에서 집행 현황을 비교 분석하는 데 있어 역사적 출발점이 됩니다.\n\n022024년 2월 17일 / 일반 지원\nDSA 시간 창.\n\n역사적 행위와 관련 DSA 의무가 적용되는 기간 동안의 행위를 구분해야 한다.\n\n0310년 / 원본 서류 스냅샷\n기간에는 추적 기록이 필요합니다.\n\n2016년 7월 이후 경과된 기간(제11항 참조)은 서류상 지표일 뿐입니다. 이는 10년 동안 지속된 DSA 위반 사례를 의미하는 것이 아닙니다. 각 통지서를 구체적인 항목, 관련 법률, 송달 증빙 자료 및 답변과 각각 연결하십시오.\n\n제52조 제3항 / 법정 상한액6%\n전 세계 연간 매출액 중\n\nDSA 의무 위반에 대한 최대 과태료는 해당 제공자의 직전 회계연도를 기준으로 산정됩니다. 이는 법적으로 정해진 상한액일 뿐, Valve에 부과된 실제 과태료 액수가 아닙니다.\n\n제6조, 제8조 및 제16조 / 법적 판단 기준\n\n관련 호스팅 서비스의 경우, 특정 내용에 대한 인지 및 신속한 조치 미이행은 호스팅 면책 특권을 상실시킬 수 있습니다. 충분히 구체적인 통지는 해당 콘텐츠에 대한 인지를 입증할 수 있습니다. DSA는 일반적인 모니터링 의무를 부과하지 않으며, 면책 특권의 상실 자체만으로는 다른 법률에 따른 책임이 성립되지 않습니다.\n\nDSA: 제6조, 제8조, 제16조, 제52조, 제53조, 제93조 및 서문 제17항 ↗ 보관됨 2026-09-20 ↗\n\n보관된 불만 사항 검토 ↗계정 타임라인 만들기 →법률 및 경제에 대한 종합 분석 →\nC부 — 법적 체계 · 제17조 · 신원, 연령, 상업적 접근\n미성년자: ‘Steam’ 로그인은 연령 확인이 아닙니다.\n문맥 및 출처 제한\n\n이 자료집 어디에도 미성년자의 정보는 나타나지 않으며, 어떠한 정보도 수집되지 않았습니다. 저자들은 언급된 어떤 플랫폼에도 가입하거나, 정보를 등록하거나, 로그인을 완료한 적이 없습니다. 이 섹션을 바탕으로 자료를 작성하는 사람은 아동과 관련된 증거를 비공개로 처리하고, 공개 자료에서 신원을 식별할 수 있는 세부 정보를 삭제해야 합니다. 여기서 COPPA는 일반적인 도박 연령 규정이 아닌, 대상, 실제 인지 여부, 수집된 개인 정보 등 자체적인 적용 범위를 가진 아동 개인정보 보호법으로 인용된 것이며, 2026년 뉴욕주 고소장은 주 당국의 주장일 뿐 확정된 판결이 아닙니다.\n\n\"Steam로 로그인\"하면 계정이 존재함이 확인됩니다. 그것은 나이와 관련해서는 아무것도 증명하지 못한다 — 그리고 이러한 사이트에서 이는 아이와 예금 사이의 유일한 관문입니다. 다음 내용을 참고하여 읽어보세요. 3.1절: Steam 클라이언트 내에서는 브라우저에 표시될 경고가 절대 발생하지 않으므로, 자녀는 그 경고를 볼 일이 없습니다.\n\nOpenID가 제공하는 기능계정 식별 정보\n\n계정에 로그인하거나 계정을 연동하는 데 사용되는 인증된 SteamID입니다.\n\n≠\n사업자가 입증해야 할 사항참가 자격\n\n연령, 관할권 및 필요한 신원 확인 절차.\n\n기술적 근거: Steamworks OpenID 문서 ↗ 보관됨 2026-09-21 ↗. 문서화된 신원 확인은 사용자가 합법적으로 도박을 할 수 있다는 인증을 의미하지 않습니다.\n\nCOPPA / 13세 미만 아동\n연산자와 데이터를 파악하십시오.\n\nCOPPA는 해당 대상인 아동 대상 서비스와 13세 미만 아동의 개인정보를 수집하고 있음을 실제로 알고 있는 서비스에 적용됩니다. 이는 아동 개인정보 보호법일 뿐, 도박 허용 연령에 관한 보편적인 규정이 아닙니다. 대상 고객층, 수집되는 개인정보, 해당 사실에 대한 인지 여부 및 부모 동의 절차를 명확히 정해야 합니다.\n\nFTC: COPPA 요건 ↗ 보관됨 2026-09-21 ↗\n\n보존해야 할 증거\n로그인부터 입금까지의 과정을 기록하십시오.\n\n해당 사이트의 연령 제한, 회원 가입 안내문, 이용 자격 조건, 결제 절차 및 민원 이력을 그대로 보존하십시오. 각 운영자를 개별적으로 평가하십시오. 아동과 관련된 모든 증거 자료는 비공개로 유지하고, 공개 자료에서 신원을 식별할 수 있는 세부 정보를 삭제하십시오.\n\n이와 관련된 공공 집행 기록으로는 다음이 있습니다. 2026년 뉴욕 민원 접수 공고 보관됨 2026-09-01 ↗, 이는 유료 전리품 상자가 어린 이용자들에게 해를 끼친다고 주장하는 내용입니다. 이는 COPPA에 따른 조사 결과가 아닙니다.\n\nC부 — 법적 체계 · 제18조 · GDPR 제15조에 따른 요청\n요청. 응답. 누락된 비교.\n\n그는 네 가지를 요청했는데, 그중 하나는 자신의 계정에 API 키를 등록한 사람을 밝혀줄 로그였다. 3일 후, 해당 티켓은 그 어떤 정보도 담겨 있지 않은 페이지로 연결되는 링크와 함께 종결되었습니다. — 그리고 그 문장을 마무리하는 데 사용된 문장은 Valve의 변호사들 스스로가 반박하고 있다.\n\n이 계정의 소유자 · 출처 및 제한 사항\n\n이 스크린샷들은 PhishDestroy의 것이 아닙니다. 이 내용은 평범한 Steam 계정 소유자, 즉 본 프로젝트가 실시한 간단한 설문조사에 응답한 한 명으로부터 나온 것으로, 해당 응답자가 직접 요청을 제출하고 스크린샷을 제공했습니다. 계정은 그의 것이며, 티켓도 그의 것이고, 서신 교환은 그와 Steam 고객지원팀 간의 것입니다. 본 프로젝트는 해당 요청을 제출한 적이 없으며, 해당 플랫폼에 계정을 보유하고 있지 않으며, 이 티켓의 당사자도 아닙니다.\n\n2026년 9월 16일, 그는 GDPR/CCPA 제15조에 따른 정보주체 접근 요청을 제출하며, 특히 API 키 등록 로그, IP 주소가 포함된 로그인 내역, 기기 인증 내역 및 거래 내역을 구체적으로 요청했습니다. 9월 17일, 상담원 “Logen”은 그에게 셀프 서비스 계정 데이터 페이지를 안내했습니다. 9월 18일, 그는 요청한 항목들이 해당 페이지에 없다고 밝히며 개인정보 보호팀이나 DPO로 이관을 요청했습니다. 9월 19일, 상담원 “Kal”은 동일한 안내와 함께 티켓을 종결했습니다. 두 스크린샷은 아래에 보존되어 있습니다(요청자의 이메일 주소는 삭제됨; SHA-256은 steam_tos_assets/screenshot-manifest.json).\n\n그는 평범한 이유 하나만으로도 이 요청을 할 만한 적임자입니다: 이 계정에는 본인이 생성하지 않은 Steam 웹 API 키가 연결되어 있으며, 이 키는 다음 주소에 등록되어 있습니다. localhost. 언제 만들어졌는지는 알려져 있지 않다 — 그에게도 아니며, Valve이 그에게 제공한 어떤 것에서도 비롯된 것이 아니다. 그 시점을 확인할 수 있는 유일한 기록은 API 키 등록 로그인데, 바로 이 기록이 폐쇄 조치로 인해 공개되지 않았기 때문이다. 이 키는 새로운 것이 아니다. 같은 이유로, 그가 이 키의 존재를 알게 되기 훨씬 전부터 이미 존재해 왔으며, 그 기간은 그가 측정할 수 없을 정도이다.\n\n다른 계정 소유자들도 동일한 요청을 제출하고 있습니다. 도착하는 모든 답변은, 요청을 승인하든 거부하든 상관없이, 이 두 건과 동일한 조건(티켓 번호, 캡처 날짜, SHA-256, 요청자 정보 삭제)에 따라 여기에 추가될 것입니다.\n\n이 프로젝트는 해당 티켓이 왜 종료되었는지에 대해서는 어떠한 입장도 취하지 않습니다. 티켓에는 종료 사유가 명시되어 있지 않았으며, 본 문서에서도 어떠한 사유도 추측하지 않습니다.\n\n요청. 응답. 비교.기록을 따라가 보세요\n단계 3 / 3\n\n그는 네 가지 특정 카테고리를 요청했습니다. 그가 안내받은 ‘계정 데이터’ 페이지는 Valve의 자체 셀프 서비스 내보내기 기능이며, 본 프로젝트는 타인의 계정 내용을 열거할 수 없으므로, 여기에는 카테고리별 전체 비교 결과가 게시되지 않습니다. 기록에 남아 있는 것은 9월 18일, 해당 카테고리가 존재하지 않았다는 그의 진술과, 9월 19일 해당 문제를 다루지 않은 채 안내 내용을 반복한 종결 조치뿐입니다.\n\n요청 사항구체적인 범주API 키, 로그인, 기기 및 거래 내역\n반응계정 데이터 참조지원 교환을 점검하십시오\n시험어떤 물품이 공급되었나요?요청된 각 카테고리를 비교하세요\n화면 1/2 — 요청 (9월 16일) 및 첫 번째 답변, 상담원 “Logen” (9월 17일)\nGDPR ticket HT-2YBP-F7JP-D4VB — request and first response\n출처: help.steampowered.com, 티켓 번호 HT-2YBP-F7JP-D4VB · 2026년 9월 16~17일 캡처 · 요청자 이메일 삭제됨 2026-09-21 · 파일: gdpr-ticket-1.png · SHA-256 da940c731ab9869d226e9d06ccc8a1b393738766b7b0c445a56662623e025a66 (screenshot-manifest.json).\n화면 2/2 — 에스컬레이션 요청 (9월 18일) 및 처리 완료, 상담원 “Kal” (9월 19일)\nGDPR ticket HT-2YBP-F7JP-D4VB — escalation request and closure\n출처: help.steampowered.com, 티켓 번호 HT-2YBP-F7JP-D4VB · 2026년 9월 18~19일 캡처 · 파일: gdpr-ticket-2.png · SHA-256 44844ea7b251f7fd7d79f87ee1578a846606a97b9659d3a53b322120c422219b (screenshot-manifest.json).\n마무리 답변, 9월 19일 (원문 그대로):\n\"Steam에 저장된 데이터는 이미 귀하의 계정 정보 페이지에서 확인하실 수 있습니다. 지원팀에서 제공할 수 있는 추가 정보가 Steam 없으므로, 이 요청은 종료될 예정입니다.\"\n데이터 미제공 · 거절 사유 미기재 · 상급 부서로 이관된 결과 미표시\n그 문장은 사실이 아니며, Valve의 변호사들 스스로가 이를 입증하고 있다. 2025년 10월 1일자 변호인 서한의 1.9항에는 하나의 기기를 수십 개의 계정과 연결하는 기기 수준의 상관관계가 설명되어 있습니다 (부록 A). 해당 회신에는 830페이지 분량의 보존 기록이 포함되어 있었으며 (부록 B). 계정 정보 페이지에는 그 어떤 내용도 표시되어 있지 않습니다.\n이 계정이 API 키 로그를 요청한 이유는 무엇인가요?\n\n그는 그 네 가지 범주를 무작위로 선정한 것이 아니다. 그 localhost 그의 계정에서 핵심은 스크립트의 흔적이며, 개발자 페이지에 실제 도메인을 직접 입력하는 사람의 흔적이 아님 (제5절, 제6절). 누가, 어디서 생성했는지를 보여주는 유일한 기록은 API 키 등록 로그입니다. 그것이 그가 가장 먼저 요청한 것이었습니다. 바로 그 기록을 클로저 측이 공개하지 않았던 것입니다.\n\n출처: 해당 계정 소유자, 본 프로젝트 설문조사 중. 위의 티켓 스크린샷은 해시 처리되었으며, 키 페이지는 공개되지 않았습니다.\n\n평가 · PhishDestroy\n\n여기서는 질문이 여전히 해결되지 않은 상태에서 티켓을 종결하는 것이 우연이 아닙니다. 이는 정상적인 절차입니다. 저희는 16,319 보관된 민원 및 지원 기록 그리고 중복 제거된 지원 문의 354건 그것들에서 도출된 것입니다. 이 티켓은 그 형태를 명확히 보여주는, 날짜가 명시된 대표적인 사례 중 하나입니다.\n\n지원 티켓 — 보존됨HT-2YBP-F7JP-D4VB\n요청 유형GDPR 제15조 DSAR\n티켓 상태2026년 9월 19일 폐쇄 — 데이터 미제공\n거래소의 딜러들\"로겐\"(9월 17일), \"칼\"(9월 19일)\n제출됨2026년 9월 16일\n요청된 데이터이 계정에 연결된 웹 API 키를 누가 등록했는지, 그리고 어떤 IP / 기기 / 타임스탬프에서 등록되었는지\n인용된 법적 근거GDPR 제15조 — 개인정보 열람권\n법적 틀:제12조 제3항은 데이터 처리자에게 수령일로부터 1개월의 기한을 부여하고 있으며(정당한 사유가 있을 경우 연장 가능), 이 기한은 본 문서가 게시될 당시 만료되지 않았으며, 본 자료에서는 기한 위반을 주장하지도 않습니다. 이 이의 제기는 내용에 대한 것이다. 최종 답변은 셀프 서비스 페이지로 연결되어 있을 뿐, 명시된 4가지 데이터 범주가 제공되었음을 보여주지 않고 있으며, 만약 데이터 처리자가 조치를 거부할 경우 제12조 제4항에 따라 그 사유와 불만 처리 절차를 명시해야 한다. 그러나 최종 답변에는 두 가지 모두 포함되어 있지 않다.\n이 특정 데이터가 중요한 이유\n\n웹 API 키 이벤트 로그는 제3자가 도난당한 세션 쿠키를 사용하여 키를 등록했는지 여부를 보여주는 기록으로, 이는 본 자료집 아카이브에 보존된 재고 도난 관련 민원서에 설명된 메커니즘입니다. API 키를 누가, 어떤 IP 주소에서, 어떤 타임스탬프에 등록했는지를 공개하면 다음과 같은 결과가 초래될 것입니다:\n\n피해자가 API 생성 IP를 자신의 로그인 내역과 대조할 수 있도록 하십시오\n알려진 피싱/도박 봇 인프라와 연계된 데이터 센터 IP 주소 공개\n가해자에 대한 민사 또는 형사 소송 절차에서 사용할 수 있는 증거를 제출한다\n키가 생성되었을 때 계정 소유자에게 알림이 전송되었는지 여부를 표시합니다.\n기록에 따르면: Valve는 기기 수준 및 계정 연계 기록을 보관하고 있으며, 2025년 10월 1일자 해당 회사의 법률 대리인 서신에 이에 대한 설명이 나와 있습니다(부록 A, 증거 메모 — 출처 1 참조). 티켓 HT-2YBP-F7JP-D4VB에서는 정보 주체가 동일한 종류의 기록을 요청했으나, 해당 티켓은 정보 주체가 해당 기록이 포함되어 있지 않다고 보고한 셀프 서비스 페이지로 안내하는 것으로 종결되었다. 그러한 거부가 합법적인지는 감독 당국이 판단할 문제이며, 그 결과로 해당 데이터의 주체는 해당 기록을 받지 못하게 됩니다.\n그 대화 — 3일 동안 주고받은 네 통의 메시지\n\n두 명의 Steam 지원 담당자가 티켓에 표시된 이름인 “Logen”(9월 17일)과 “Kal”(9월 19일)로 답변을 남겼습니다. 두 사람 모두 요청자에게 계정 정보 페이지를 안내했습니다. 티켓에는 해당 요청이 Valve의 개인정보 보호팀이나 데이터 보호 책임자에게 전달되었는지 여부가 명시되어 있지 않으며, 관련 자료에는 상담원들이 누구인지, 그들의 역할이 무엇인지, 또는 티켓이 어떻게 전달되었는지에 대한 설명이 없습니다.\n\n9월 16일\n4가지 명시된 데이터 범주를 포함한 제15조 요청서 제출\n9월 17–18일\n계정 데이터 참조; 요청자가 DPO에 상신해 줄 것을 요청함\n9월 19일\n동일한 출처를 근거로 티켓이 종결됨; 데이터 없음, 명시된 근거 없음\nGDPR 제15조는 정보주체에게 어떤 권리를 명시적으로 부여하고 있는가?\n제15조 제1항 가호처리 목적 — Valve이 데이터를 보유하는 이유\n제15조 제1항 (b)호데이터의 범주 — Valve이 포함하는 내용\n제15조 제1항 (c)호수령인 또는 수령인 범주 — 데이터를 수신한 자 (예: API 키 보유자)\n제15조 제1항 제d호보존 기간 또는 그 결정 기준\n제15조 제3항처리 중인 개인 데이터의 사본 — 즉, API 키 로그 자체\n제12조 제3항다음 기간 내에 답변이 필요합니다. 한 달 수령일로부터; 기한 연장은 해당 월 내에 통지되어야 합니다. 본 기사 게재 시점에는 해당 기한이 만료되지 않았습니다. 제12조 제4항: 담당자가 조치를 취하지 않을 경우, 그 이유를 밝히고 해당 당사자에게 민원 처리 절차를 안내해야 합니다.\n규제 관련 민원 접수 절차 — 모든 사용자를 위한\n\nValve에 GDPR 제15조에 따른 요청을 제출했으나 규정에 부합하는 답변을 받지 못한(또는 데이터가 포함되지 않은 정형화된 거절 통지를 받은) 사용자는 자신이 속한 EU/EEA 회원국의 감독 당국에 불만을 제기할 수 있습니다. Valve의 EU 내 사업장은 함부르크에 위치한 Valve GmbH이므로, 국경을 넘는 불만 사항에 대한 주 관할 감독 당국은 함부르크 주 개인정보 보호 및 정보 자유 담당관 (HmbBfDI). (Valve의 제27조에 따른 대리인도 함부르크에 소재하고 있으나, 대리인의 주소만으로는 관할 당국을 결정할 수 없다.) 또한 제77조에 따라 신고인의 소속 회원국 당국에 신고를 제기할 수도 있다.\n\nHmbBfDI 민원 접수 양식 ↗ GDPR 조문 (제12조, 제15조, 제77조) ↗ 보관됨 2026-09-20 ↗EDPB 지침 ↗\n\n불만 사항 접수 시 참조할 티켓 번호: HT-2YBP-F7JP-D4VB — 이 자료집에 기록된 사례로 수록되어 있다.\n\n기록된 사례 하나\n기록은 존재하지만, 정보 주체는 이를 받지 못했습니다.\n\nValve의 변호인은 2025년 10월 1일자 서한에서 기기 수준의 상관관계 기록에 대해 설명했습니다. 2026년 9월 19일, 동일한 종류의 기록에 대한 제15조 요청은 법적 근거를 명시하지 않은 채, 요청자가 해당 기록이 포함되어 있지 않다고 보고한 셀프 서비스 페이지로 안내하는 방식으로 종결되었다. 티켓 번호 HT-2YBP-F7JP-D4VB는 문서화된 사례 중 하나이며, 이것이 더 광범위한 관행을 반영하는지 여부는 감독 당국이 판단할 문제이며, 감독 당국은 Valve 측에 해당 처리 기록을 요청할 수 있다.\n\nGDPR 제12조, 제15조, 제77조 / 감독 기관\n\n제12조 및 제15조에 따른 민원은 관련 감독 기관에 무료로 직접 제기할 수 있습니다(제77조). 감독 당국은 정보주체의 권리 침해에 대해 정보 열람 요청 이행을 명하는 명령을 포함한 시정 조치와 제83조 제5항 (b)호에 따른 과태료를 부과할 수 있습니다. 원본 티켓 참조 번호와 Valve 응답(또는 응답 없음)을 보관해 두면 민원의 설득력을 높일 수 있습니다.\n\nDSAR 양식 보기 →\nC부 — 법적 체계 · 제19조 · 계약법\n플랫폼 자체 아키텍처에 위배되는 가입자 계약\n문맥 및 출처 제한\n\n저자들은 변호사가 아니며, 본문의 내용은 법적 조언이 아닙니다. SSA(사회보장법) 인용문은 2026년 9월 10일 개정판을 기준으로 한 것이며, 개정판에 따라 내용이 다를 수 있고 조항 번호도 개정판마다 변경되었으므로, 해당 행위에 적용되는 버전의 조항을 확인하시기 바랍니다. 제25조 및 제32조에 대한 논거는 해당 규정이 요구하는 사항을 명시한 것이지, 감독 당국이 위반 사실을 확인했다는 것을 의미하지는 않습니다. 논거 1에 제시된 수치는 제13조에 명시된 적용 범위의 한계를 반영하고 있습니다.\n\nSSA의 핵심 조항 중 세 가지는 플랫폼의 구축 방식과 잘 맞지 않습니다. 고가 거래를 플랫폼 밖으로 밀어내는 시장 가격 상한선에 대한 상업적 이용 금지 조항; 2023년 이전에는 2단계 인증이 필요하지 않았던 키 엔드포인트에 대한 API 키 사용자 책임 조항; 그리고 사업자별 집행 실적이 전혀 나타나지 않는 공개 기록에 반하는 집행 관련 조항. 이러한 상충점이 집행 가능성에 영향을 미치는지는 법원이 판단할 문제이며, 본 절에서는 법원이 심리할 때 참고하게 될 사실 관계를 제시합니다.\n\n논거 1 / 시가총액 구조\n시장의 상한선과 상업적 이용 금지\n\nSteam 커뮤니티 마켓의 상품 등록 상한가는 약 $1,800입니다. 오래된 스냅샷(2026년 9월 23일)에 따르면, 5개 마켓플레이스 전반에 걸쳐 248개의 CS2 상품 카테고리가 해당 상한가보다 2개 이상의 마켓플레이스에서 독립적으로 더 높은 가격으로 책정되어 있으며, 이러한 상품들은 Valve의 자체 플랫폼에서는 해당 가격으로 판매할 수 없습니다. 이러한 가격을 원하는 소유주들은 Steam 계정과 Steam API를 통해 운영되는 제3자 마켓을 이용합니다. SSA는 명시적으로 허용되지 않는 한 이를 상업용으로 분류하므로 주의하시기 바랍니다.\n\n상품 수가 마켓의 상한선을 초과함 → 제3자 마켓이 그 공백을 메움 → 해당 마켓들은 Steam 계정과 Steam API를 사용함 → SSA는 허가 없이 상업적 사용을 금지함 → 허가 목록이 공개된 바 없음. 커뮤니티 마켓의 총 수수료 약 15%은 마켓 내에서 완료된 판매에만 적용되며, 이러한 외부 거래에는 적용되지 않습니다.\n논거 2 / API 키 보안 아키텍처\nAPI 키 취약점은 사용자의 부주의가 아닌 플랫폼 설계상의 문제이다\n\n2023년 이전에는 Steam의 API 키 생성 엔드포인트가 도난당한 sessionid가 포함된 POST 요청을 허용하여 높은 권한을 가진 자격 증명을 생성했습니다. 이메일 확인, 2단계 인증 또는 기기 인증 없이. 이번 조사에서 수집된 API 하이재킹 관련 신고 사례들은 모두 동일한 패턴을 따릅니다. 즉, 공격자의 스크립트 실행, 세션 쿠키 도용, 은밀한 키 생성, 거래 가로채기 순으로 진행됩니다(요청 페이로드는 8절에 나와 있습니다).\n\nGDPR 제25조(설계 단계에서의 데이터 보호) 및 제32조(처리 보안)는 위험에 상응하는 기술적 조치를 요구합니다. 2단계 인증이나 소유자 통지 없이 거래가 가로채일 수 있는 자격 증명을 발급하는 것은 데이터 처리 책임자의 설계상의 문제입니다. 이러한 배경에서 사용자에게 책임을 전가하는 SSA 조항을 근거로 삼을 수 있는지는 법원과 감독 당국이 판단해야 할 문제입니다.\n\n주장 3 / 실시간 가시성\nValve은 로그인할 때마다 인증 호스트명을 수신합니다\n\n인증 호스트 이름은 Valve의 OpenID 엔드포인트에 일반 텍스트로 전송되며, openid.return_to 그리고 openid.realm (요청 형식은 3절에 나와 있다). 이를 추출하는 것은 표준적인 작업이다. 2026-09-22 시점을 기준으로, 26쌍의 경우 메인 도메인은 링크 필터에 포함되어 있었으나, Steam 로그인을 가진 호스트는 포함되어 있지 않았다. Valve은 사업자별 적용 기록을 공개하지 않았으므로, 공개된 데이터만으로는 이러한 호스트에 링크 필터 이외의 조치가 적용되었는지 여부를 확인할 수 없습니다.\n\n비용은 누가 부담하는가\n보관된 민원에서 나타나는 양상\n\n검토된 민원 사례에서, API 키 도용 주장에 대한 Steam 지원팀의 대응은 다음과 같은 한 가지 양식을 따릅니다: 복구를 거부하고, 계정 및 API 키에 대한 책임이 사용자에게 있음을 언급한 뒤, 티켓을 종결합니다. 본 보고서에서는 영향을 받은 계정 수나 손실된 금액에 대한 총계 추산치가 제시되지 않았으며, 이러한 수치를 뒷받침할 만한 출처도 확인되지 않았습니다.\n\n문제는 개별 사용자가 실수를 했는지 여부가 아닙니다. 문제는 2023년까지 도난당한 쿠키를 이용한 POST 요청으로, 어떠한 알림이나 2단계 인증 절차도 없이 높은 권한을 가진 거래 자격 증명을 생성할 수 있게 허용했던 아키텍처에 대한 책임이 누구에게 있는지입니다.\n문서로서의 SSA 대 계약으로서의 SSA\n이 기록을 검토하는 법원은 SSA를 단독으로 해석하지 않을 것이다.\n\n이 문서는 2025년 10월 변호사가 보낸 서신과 함께 검토될 것이며, 해당 서신에는 기기 수준 상관관계, 인증 호스트 등록 날짜, 일괄 등록 타임스탬프, API 키 요청 페이로드, 그리고 2016년 7월 통지 이후 10년이 지난 시점인 2026년 9월에도 여전히 운영 중인 플랫폼들에 대한 내용이 기술되어 있습니다. 이것이 Valve가 다루어야 할 기록입니다.\n\n기록에 반하는 SSA / 주요 사항\n\"상업적 이용 금지\" — 마켓의 상한선으로 인해 고가 상품 거래가 제3자 상업 시장으로 밀려나고 있다\n\"API 키에 대한 책임은 사용자에게 있다\" — 2023년 이전에는 키 엔드포인트에 2단계 인증이 적용되지 않음\n\"위반자에 대해 단속 조치를 취하고 있습니다\" — 2016년 7월 이후 사업자별 단속 기록이 공개되지 않음\n\"약관에 동의하셨습니다\" — 하이재킹 패턴에서는 동의가 계정 소유자가 아닌 스크립트를 통해 제출됩니다.\n결론 · 기록이 입증하는 바와 우리가 요청하는 사항\n조사 결과. 우리가 요청한 기록들.\n문맥 및 출처 제한\n\n아래의 각 조사 결과는 위 섹션에 기재된 날짜가 명시된 공개 기록과 연계되어 있습니다. 이 요청들은 본 조사만으로는 확보할 수 없는 유일한 사항, 즉 Valve의 자체 집행·접근·처리 기록을 확보할 수 있는 권한을 가진 당국에 제출된 것입니다.\n\n각 요청은 날짜가 명시된 조사 결과에 근거합니다. 당국은 이 공개 정보 조사만으로는 확보할 수 없는 기록을 요청할 수 있습니다.\n\n공식 기록에 따르면\n44개의 활성 플랫폼은 별도의 등록 가능한 도메인을 통해 인증되며, 이 중 27개는 경로별 증거 파일이 공개되어 있고, 17개는 수동으로 수집되어 별도로 나열되어 있습니다. 2026-09-22 기준, 26쌍의 경우 Steam 링크 필터에서 메인 도메인이 차단된 반면, 로그인을 처리하는 호스트는 차단되지 않았습니다 — csgogem.com은 차단되었으며, api.csgem.com 2014년 3월부터 등록되어 있습니다. Steam은 해당 호스트명을 openid.realm 그리고 openid.return_to 매번 로그인할 때마다. 제3절\n2016년 7월 13일, Valve은 해당 방식을 공개적으로 지목하고 이를 금지했으며, 2016년 7월 20일 해당 기관의 변호사가 발송한 통지서에는 10일간의 기한이 명시되었습니다. 그 기한이 지난 지 10년이 지났으나, 사업자별 집행 기록은 아직 공개되지 않았습니다. 제11조\nSteam 웹 API 키 엔드포인트는 2023년 이전까지 2단계 인증 절차 없이 세션 쿠키만으로도 높은 권한을 가진, 거래가 가능한 인증 정보를 발급했습니다. 제5절\nGDPR 제15조에 따른 요청(티켓 번호 HT-2YBP-F7JP-D4VB)은 3일 만에 셀프 서비스 링크만 제공된 채, 어떠한 데이터도 제공되지 않은 상태로 종결되었습니다. 제18조\n각 기관에 요청하는 사항\n워싱턴주 도박위원회\n2016년 파일을 다시 열어 주십시오. 10일간의 통지 기간이 지난 후 어떤 계정, 봇 및 리턴 호스트가 비활성화되었는지, 그리고 이후 어떤 운영자가 다시 접근 권한을 회복했는지에 대한 운영자별 상세 내역을 요청합니다. 제2절\nHmbBfDI (함부르크; Valve GmbH)\n제15조에 따른 답변이 데이터 처리자의 의무를 충족했는지 여부를 검토하고, 가해자를 식별하는 데 필요한 API 키 등록 및 접근 기록의 공개를 요구한다. 제18조\nDSA 디지털 서비스 코디네이터\n해당 레코드에 auth-host 라우팅을 참고 사항으로 기재한 다음, 관련 정보가 문서화된 후 Valve의 응답이 의무를 충족하는지 평가하십시오. 제16조\n모든 정보주체\n제15조 양식을 사용하여 본인의 계정에 대해 동일한 기록을 요청하십시오. 보관된 기록을 통해 누가 재설정을 시작했는지 또는 키를 생성했는지 확인할 수 있습니다. 부록 G\n\n이 네 가지 요청의 근본적인 목적은 모두 동일합니다. 바로 Valve만이 보유하고 있는 집행, 접근 및 처리 기록을 공개하라는 것입니다. 홈페이지 경고문, 10일 통지서, 셀프 서비스 페이지는 모두 통제권을 행사한 사례입니다. 통제권이 실제로 행사되었는지 여부는 공개 기록만으로는 알 수 없는 문제이지만, 규제 당국이라면 답할 수 있는 질문입니다.\n\n부록 — 주요 증거물 및 작업 자료\n부록 A — 변호인과의 서신 교환\n증거 메모 — 제1정보원이 제공한 자료\n\n제1조, 제18조 및 제19조에서 인용된 변호인 서신의 근거 자료 및 출처 현황.\n\n증거 기반 및 출처 현황 — 출처 1에서 제공한 문서\n이번 감사를 촉발한 영구 정지 조치를 받은 사용자는 이번 감사의 대상이 아닙니다. 해당 정지 조치가 정당했는지는 여기서 검토되지 않으며, 이 보고서는 이를 옹호하거나 반박하지도 않습니다. 계정이 핵심이 아닙니다. 중요한 것은 자료입니다: 출처 1 — 아래 서신을 Valve의 변호인으로부터 자신의 GDPR 요청에 대한 정보주체로서 수령한 해당 차단 계정 소유자는, 해당 서신과 첨부된 사건 파일을 공개적으로 열람할 수 있는 권한과 함께 전달해 주었습니다. 이름은 공개되지 않았으며, 문서는 날짜, 생성자 메타데이터 및 해시 값으로 표기되어 있습니다.\n\n해당 서신은 GDPR/DSAR 요청에 대한 답변으로 발송되었습니다. 그 과정에서 Valve의 변호인은 Steam 지원팀이 이전에 사용자에게 기술적으로 불가능하다고 밝혔던 기능에 대해 설명하는 진술서를 서명과 함께 공식 기록에 남겼습니다. 아래에 인용된 문단은 바로 그 진술서입니다.\n\n저자들이 생성된 로그 추출물에 대해 수행한 추가 분석은 다음과 같다. 본 자료집에서 제외됨 독립적인 검토가 진행 중인 상태입니다. 이 조사 과정의 다른 어떤 부분에서도 이를 근거로 삼지 않습니다.\n\n기록에 남겨진 사실: 지속적인 기기 수준 원격 측정\n\nValve의 대리인이 작성한 것으로 알려진 서신의 1.9항에서, Valve의 변호사들은 다음과 같이 밝히고 있다: \"2019년부터 2023년까지 이 계정은 주로, 도난당한 Steam 계정 수십 개에 로그인하는 데에도 사용된 기기를 통해 접속되었습니다.\"\n\n사실: Valve의 변호인은 이 자리에서 4년에 걸친 여러 계정 간의 기기 수준 상관관계를 설명하고 있습니다. Steam 고객 지원팀은 도난 피해자들에게 도난당한 물품을 추적하거나 계정을 기기와 연결하는 것이 기술적으로 불가능하다고 밝혔습니다. Steam Guard 기기 인증 절차는 공개적으로 문서화되어 있으므로, 기기별 기록의 존재 자체는 새로운 사실이 아닙니다. 새로운 점은 해당 기록이 보관되고 있으며, 수년에 걸쳐 계정 간에 상호 연관되어 있다는 사실을 변호인이 서면으로 확인했다는 점입니다.\n\n이것이 중요한 이유: 4년 동안 한 대의 기기를 수십 개의 해킹당한 계정과 연결 지을 수 있는 상관관계는, 지원팀이 피해자들에게 제공할 수 없다고 밝힌 바로 그 종류의 기록과 동일합니다. 해당 유형의 기록은 도난 및 재판매 사슬에 연루된 계정과 기기를 식별하는 데 활용될 수 있습니다. 어떤 기록이 존재하는지, 얼마나 오래 보관되는지, 그리고 어떤 근거로 정보 주체에게 공개되지 않는지는 감독 당국이 검토해야 할 사항입니다.\n\n출처: 2025년 10월 1일자 Valve의 변호인 서한, 1.9항 및 830페이지 분량의 PDF 부록 · GDPR 제15조에 따른 요청에 대한 응답으로 출처 1이 수령함 · 부록의 SHA-256 해시값은 다음 위치에 기록됨 disclosure-audit.json · 해당 서신 자체는 게재되지 않았으며, 계좌명 및 제3자 데이터는 생략되었습니다.\n\n상태: 열기\n원자료는 증거 아카이브를 통해 확인할 수 있습니다.\n부록 B — 생성된 PDF · 비공개 정보 삭제 확인\n제출된 PDF 파일의 편집은 표면적인 것에 불과하며, 가려진 텍스트는 여전히 추출할 수 있습니다.\n\nValve의 변호인은 GDPR 정보 열람 요청에 대해 830페이지 분량의 부록을 제출했는데, 이 부록에서는 삭제된 부분이 텍스트를 제거하는 대신 텍스트 위에 칠해져 있었다. 902,270 개의 문자가 검은 막대 아래에 위치해 있으며, 텍스트 추출 도구를 통해 바로 추출됩니다. — 해당 막대가 숨기려고 했던 제3자 식별자를 포함합니다. 여기에는 집계된 수치만 공개되며, 해당 내용은 재게재되지 않고, 부록 자체도 공개되지 않습니다.\n\n1. 기하학적 점검 결과\n\nGDPR 제15조에 따른 답변 (일자) 2025년 10월 1일 이 문서에는 830페이지 분량의 PDF 부록이 첨부되어 있었다(같은 날짜에 생성 및 수정된 .NET용 Aspose.PDF 생성자 메타데이터). 저자들은 페이지 단위의 기하학적 검사를 수행했는데, 각 페이지마다 텍스트 레이어 뒤에 그려진 불투명한, 거의 검은색에 가까운 직사각형을 찾아내고, 그 아래에 있는 추출 가능한 문자의 개수를 집계했다.\n\n생성된 파일을 기준으로 측정함\n902,270\n검은 막대 아래에서 여전히 추출할 수 있는 문자들\n추정이 아닌 집계된 수치입니다. 이는 집계 대상인 캐릭터의 수를 나타낸 것이며, 피해자, 재식별 사례 또는 사건의 수를 나타낸 것이 아닙니다.\n830 / 830\n영향을 받는 페이지 — 모든 페이지\n986\n추출 가능한 텍스트 위에 있는 직사각형\n1,329\n불투명한 검은색 직사각형의 총 개수\n검은색 막대는 텍스트 레이어 위에 그려진 것이며, 텍스트를 제거하는 것은 아닙니다. 막대 아래에 있는 텍스트는 일반적인 PDF 도구를 사용하여 추출할 수 있습니다. 여기에는 총 집계 수치만 공개되며, 가려진 내용은 재게재되지 않습니다.\n법의학 시연: 층 분리\nASPOSE.PDF FOR .NET 벡터 오버레이 모크업 (부록 P. 412)\n\n해당 계정에 대해 제기된 신고: [로그인: redacted_user_667]\n\n사용자가 제출한 사유: [본문: \"사용자가 인벤토리에 중복 아이템이 있으며, 부당한 거래 행위가 있다고 신고했습니다...\"]\n\n전경: <path fill=\"#000\" />결함: 기본 UTF-8 스트림이 그대로 유지됨\n출처: 2025년 10월 1일자 변호사 서신의 PDF 부록 (830페이지, Aspose.PDF for .NET 생성자 메타데이터) · 저자들이 측정한 결과, 방법 및 페이지당 개수 disclosure-audit.json · 동일한 파일에 기록된 부록의 SHA-256 해시값 · 부록 자체는 공개되지 않습니다.\n2. 이것이 정보주체의 대응에 있어 왜 중요한가\n\nValve의 변호인은 해당 정보주체가 자신의 기록에 대한 열람 요청을 한 데 대한 답변으로 이 파일을 정보주체에게 보냈습니다. 그 위에 표시된 막대는 단지 외관상의 조치일 뿐입니다. 그 아래에 있는 텍스트는 전혀 삭제되지 않았기 때문에, 막대로 가려진 제3자 식별 정보는 파일과 함께 수신자에게 전달되었습니다. 텍스트 추출 도구로 제거할 수 있는 편집 처리는 아무것도 숨기지 못할 뿐만 아니라, 수신자가 어떤 정보가 공개되었고 어떤 정보가 공개되지 않았는지 파악할 수 없게 만듭니다.\n\n제15조 제4항은 그러한 제한 조항이 존재하는 근본적인 근거입니다. 즉, 사본을 입수할 권리가 타인의 권리와 자유에 부정적인 영향을 미쳐서는 안 된다는 것입니다. 이 제작물이 이행하지 못한 의무가 바로 이것입니다. 이 사건이 제4조 제12항에 따른 개인정보 침해에 해당하는지는 감독 당국이 판단할 사항입니다. 정보 유출 자체는 파일 내에서 측정 가능하며, 동일한 바이트를 보유한 사람이라면 누구나 재현할 수 있습니다. SHA-256 해시값은 공개되어 있지만, 부록은 공개되지 않았기 때문입니다.\n\n철창 아래에 있던 것은 계좌 번호가 아니었다. 이는 요청자를 대상으로 제기된 사용자 신고 내용의 본문으로, 신고 작성자들의 정보가 첨부되어 있었습니다: Steam건의 로그인 기록은, 한 번의 로그인이 Steam에서만 사용되는 경우가 드물기 때문에, 이를 통해 해당 로그인 기록의 주체를 식별할 수 있게 해줍니다 — 저자들의 추산에 따르면, 이 문서에 언급된 사용자 중 60% 명 이상은 신원을 완전히 파악할 수 있다 — 그들이 작성한 내용의 편집되지 않은 원문도 함께 공개되었습니다. 해당 글에는 요청자의 국적을 겨냥한 살해 위협과 모욕적인 표현이 포함되어 있습니다. 이렇게 신원이 확인된 사람들 중 일부는 미성년자입니다. 제작진은 자신이 제보한 대상에게 기자들의 실명이 적힌 명단을 건넸다, 이는 바로 제15조 제4항이 방지하기 위해 마련된 바로 그 피해입니다.\n\n파일의 내용만큼이나 파일 이름의 순서도 중요합니다. 이 요청에 대해 당국은 요청자의 가명 이메일 주소에 본명이 포함되어 있지 않다는 이유로 우선 신원 확인을 위한 추가 증빙 자료를 요구했으며, 그로 인해 발생한 지연 기간 동안 해당 계정은 영구 정지되었습니다. 제12조(3)항에서 정한 1개월 기한이 지난 지 6주 이상이 지나서야 비로소 데이터가 전달된 서한은 수신자에게 형사 고발을 경고하는 한편, 그가 변호사에게 계정 활동 내역을 설명할 때까지 나머지 데이터를 보류하겠다고 밝혔다. 이번 정보 공개를 통해 Valve이 공개적으로 답변하지 않았던 두 가지 의문점도 해결되었습니다. 제출된 기록에 따르면 계정 연동 내역은 2019년까지 거슬러 올라가며, Valve이 이전에 설명한 적이 없는 수준의 상세한 내부 텔레메트리 데이터도 확인되었습니다.\n\n이 절의 적용 범위: 여기서의 검토는 생성된 파일을 기준으로 측정된 편집 과정의 메커니즘에 국한됩니다. 작성자들이 생성된 로그에 대해 수행한 추가 분석은 독립적인 검토가 완료될 때까지 보류되며, 본 자료집의 다른 부분에서는 이를 근거로 삼지 않습니다.\n\n증거: 2025년 10월 1일자 변호인 서신 및 해당 서신의 PDF 첨부 파일(감사 파일에 SHA-256 기록됨); 페이지 단위의 PDF 측정값 및 방법 ↗. 요청의 경위, 8페이지에 기재된 거절 사유 및 노출된 기록에 대한 설명은 PhishDestroy의 진술서에 상세히 기술되어 있으며, “내 반려견 대 GDPR 전문 변호사들”, 2026년 8월 17일 ↗ 보관됨 2026-08-21 ↗. 여기서는 계정명과 제3자 데이터는 생략되었으며, 막대로 가려진 부분은 전혀 재현되지 않았습니다.\n\n송부 서신의 8페이지에서는 요청 사항 중 일부를 거부하며, 그 사유를 서면으로 명시하고 있습니다: Steam 플랫폼의 다른 이용자들의 개인정보 보호 정책에 따라… 더 자세한 정보를 제공해 드릴 수 없습니다. — 다른 Steam명의 사용자의 개인정보를 보호해야 하므로 더 자세한 답변은 불가능합니다. 830페이지 분량의 부록도 같은 서류 묶음에 포함되어 있었습니다. 검은 막대로 가려진 부분은 계좌 번호가 아니라, 요청자를 상대로 제출된 신고서였으며, 작성자의 이름이 명시되어 있고, 편집되지 않은 원본 메시지가 첨부되어 있었습니다. 계좌 소유자는 변호사를 통해 Valve에 자신의 파일을 요청했으나, 그가 그 파일에서 추출할 수 있었던 것은 다른 사람들의 정보뿐이었습니다. 이 부록의 어떤 내용도 누가 그 상자를 그렸는지에 달려 있지 않다. 이 부록이 입증하는 것은, 정보 공개 거부의 근거로 내세운 보호 조치 Valve가 바로 그날, 같은 봉투에 담긴 이 자료 제공 과정에서 지켜지지 않았다는 사실이다.\n지원 및 법률 서신 관련 증거자료\n\n출처: https://phishdestroy.io/steam_dossier/ko/index#exhibit-gallery-section\n\n부록 D — 자료 수집\n선별된 1차 자료\n\n아카이브에 수록된 6건의 기록 — Valve의 트래커에 등록된 GitHub 이슈 3건과, 지원 처리 결과에 이견이 제기된 Reddit 계정 3개. 각 출처는 해당 주장, 저장된 텍스트, 그리고 그로부터 제기되는 의문과 함께 첨부되어 있습니다.\n\n1 / 6 선택된 기록\n소스 레코드를 선택하세요\nGH-01 / GITHUB저장된 빌드에서 열기\n2016년에 요청된 하드웨어 키\n\nValveSoftware / steam-for-linux · #4521 · 2016-06-27\n\n한 사용자가 Valve에 U2F 하드웨어 키를 대체 2단계 인증 수단으로 지원해 달라고 요청했습니다. 저장된 이 이슈에는 ‘기능 요청’ 및 ‘검토 완료’ 라벨이 모두 붙어 있으며, 상태는 ‘진행 중’으로 기록되어 있습니다.\n\n대안으로 스팀에서 U2F USB 동글을 지원해 주셨으면 합니다.\n\nGitHub 이슈에서 발췌한 내용 ↗\n문서화된 기록\nValve의 자체 이슈 트래커에 게시되었으며 ‘검토 완료’로 표시된, 추가 계정 보안 조치 요청 건(날짜 기재).\n책임 추궁\n제품 결정 사항, 응답 예정일 및 검토 후 제공된 보호 조치를 공개하십시오.\n저장된 기록 읽기 →GitHub 열기 ↗\n관련 자료: 계정 보안 조치 →아카이브 #484 · 빌드 2026-09-17\nGH-02 / GITHUB저장된 빌드에서 열기\n효과적인 수신 거부 기능이 없는 충돌 보고서\n\nValveSoftware / steam-for-linux · #6459 · 2019-08-18\n\n기자는 2019년 8월 12일자 Ubuntu 16에서 발생한 Steam 클라이언트 문제를 설명합니다. 기자는 크래시 업로드 대상을 비활성화해도 재시작 후 설정이 유지되지 않았다고 밝히며, 관련 구성 정보를 함께 제시했습니다.\n\n`ServerURL`을 비활성화하면, 재부팅할 때마다 해당 설정이 덮어쓰여집니다.\n\nGitHub 이슈에서 발췌한 내용 ↗ 보관됨 2026-04-19 ↗\n문서화된 기록\n고객의 이용 날짜, 운영 체제 및 구성 정보가 포함된 구체적인 개인정보 관련 민원입니다. 저장된 이 문제는 현재 진행 중입니다.\n책임성 요구\n조사 대상, 영향을 받은 빌드, 그리고 옵트아웃이 적용되도록 한 변경 사항을 파악하십시오.\n저장된 기록 읽기 →GitHub 열기 ↗보관됨 2026-04-19 ↗\n관련 자료: 관련 기록 요청 →아카이브 #467 · 빌드 2026-09-17\nGH-03 / GITHUB저장된 빌드에서 열기\nValve에 인증 티켓 악용 사례가 신고되었습니다.\n\nValveSoftware / Source-1-Games · #3857 · 2022-02-26\n\n작성자는 서버 운영 측이 플레이어의 연결이 끊어진 후에도 Steam개의 인증 티켓을 유지했으며, 오해의 소지가 있는 서버 목록을 사용했다고 주장합니다. 이 게시물은 Valve 측에 해당 행위에 대해 해명해 줄 것을 요청하고 있습니다.\n\n서버가 사람들로 붐비는 것처럼 보이게 하기.\n\nGitHub 이슈에서 발췌한 내용 ↗\n문서화된 기록\n2022년 2월 26일 Valve의 트래커에 접수된 공개 악용 신고입니다. 이 신고의 저장 상태는 ‘열림’이며, 신고 내용에는 스크린샷 링크가 포함되어 있습니다.\n책임성 요구\n신고된 인증 티켓 남용 사건에 대한 조사 결과 및 시정 조치를 기록으로 작성하십시오.\n저장된 기록 읽기 →GitHub 열기 ↗\n이 문서에서: 데이터셋 범위 →아카이브 #768 · 빌드 2026-09-17\nRD-01 / 레딧저자 소개\n분쟁이 있는 44건의 마켓 매입 건\n\nr/DotA2 · 작성자 닉네임 비공개 · 2022-07-07\n\n저자는 2022년 7월 6일에 마켓에서 44건의 무단 구매가 발생했으며, 손실액은 대략 $500+ 정도라고 보고했습니다. 또한 2단계 인증이 활성화되어 있었다고 밝히며, 고객 지원팀으로부터 반복적으로 정형화된 답변을 받았다고 설명했습니다.\n\n두 번째 문의 티켓을 제출했는데도, Steam 측에서는 여전히 기계적으로 복사-붙여넣기 한 정형화된 답변이 아닌 답변을 보내주지 않고 있습니다.\n\n레딧 게시글 발췌문 ↗ 보관됨 2025-03-20 ↗\n문서화된 기록\n분쟁이 발생한 구매 내역에 대한 기록으로, 거래 스크린샷 링크와 고객 지원팀의 답변이 포함되어 있습니다. 금액 및 사건 내용은 작성자가 보고한 내용입니다.\n책임성 요구\n분쟁이 발생한 구매 내역을 거래 로그 및 세션 로그와 대조하여 확인하십시오. 고객 지원팀의 결정 근거가 된 증거를 설명하십시오.\n저장된 기록 읽기 →Reddit 열기 ↗보관됨 2025-03-20 ↗\n관련 자료: 지원 및 집행 →아카이브 #4,533 · 빌드 2026-09-17\nRD-02 / 레딧저자 소개\n영구 제재 및 항소 불가\n\nr/ohnePixel · 작성자 아이디 비공개 · 2024-12-09\n\n저자는 영구 차단 조치에 이의를 제기하며, 지원팀이 계정 이전 의혹과 커뮤니티 신고를 근거로 들었다고 말합니다. 또한 처리 완료된 티켓과 자신의 개인 정보 제공을 요청할 계획에 대해서도 설명하고 있습니다.\n\n제 상황을 설명하고 자세한 내용을 물어보았지만, 그들은 결정을 고수하며 제 티켓을 종결하고 있습니다.\n\n레딧 게시글 발췌문 ↗\n문서화된 기록\n작성자가 제시한 근거와 4개의 이미지 링크가 포함된 보존된 호소 기록입니다. 게시일은 선택된 지원 내보내기 파일에서 가져온 것입니다.\n책임성 요구\n영구 제재를 뒷받침하는 근거와 이에 이의를 제기할 수 있는 재검토 절차를 확인하십시오. 항소 절차가 종결되었다고 해서 해당 결정에 대한 설명이 되는 것은 아닙니다.\n저장된 기록 읽기 →Reddit 열기 ↗\n관련 자료: 관련 기록 요청 →아카이브 #4,766 · 빌드 2026-09-17\nRD-03 / 레딧저자 소개\n회복 초기화 및 보고된 $10,000 손실\n\nr/legaladvice · 작성자 아이디 비공개 · 2025-05-09\n\n작성자는 다른 사람이 복구 요청을 제출한 후 지원팀이 인증 정보를 재설정하고 계정 보호 기능을 비활성화했다고 주장합니다. 또한 비활성 계정에서 약 US$10,000가 유출되었다고 보고했습니다.\n\nSteam 고객 지원팀에서 제 비밀번호를 재설정해 주었고, 제 계정의 모든 보안 기능을 해제했습니다.\n\n레딧 게시글 발췌문 ↗\n문서화된 기록\n회복 절차가 계정 보안 조치를 무력화했다는 주장이 기록으로 남아 있다. 저장된 게시물에는 작성자가 고객 지원팀으로부터 들었다고 주장하는 내용이 담겨 있다.\n책임성 요구\n재설정을 승인한 사람을 확인하고, 승인 시 인정된 소유권 증빙 자료 및 접속 로그를 파악하십시오. 계정 복구는 보안 시스템 Valve 통제 조치의 일부입니다.\n저장된 기록 읽기 →Reddit 열기 ↗\n관련 자료: 관련 기록 요청 →아카이브 #4,592 · 빌드 2026-09-17\n\n선별된 6개의 기록. GitHub 설명에는 저장된 빌드에 대한 정보가 담겨 있습니다. Reddit 게시물에는 작성자의 계정이 그대로 보존되어 있습니다.\n\n6개의 음반 다운로드 ↓\n\n검색 가능한 빌드에는 다음이 포함되어 있습니다. 16,319 개의 고유한 레코드: 393건의 Trustpilot, 5,635건의 Reddit, 2,395건의 GitHub, 276건의 웹 및 7,620건의 위키 기록. 하나의 사건에 대해 여러 건의 기록이 있을 수 있습니다. 별도의 40,448행 마스터 내보내기 파일은 범위가 다릅니다.\n\n전체 아카이브 검색 ↗ · 매니페스트 생성 ↗ · 데이터셋 범위 및 개수 →\n\n부록 E — 사례 연구\nArchiSteamFarm 및 자동화 조항\n\n자사의 FAQ에 따르면 수백만 개의 계정에서 운영되고 있는 오픈소스 카드 파밍 도구로, 자동화를 금지하는 이용약관 조항(§ 4.C)과 상충됩니다. 파밍 도구가 무언가를 생산하기 전에 Valve에서 무엇을 구매해야 하는지, 카드 현금화 방식이 모두 라이선스 위반에 해당하는 이유, 집행 실적, 그리고 카드 경제를 누가 관리하는지 등 그 작동 원리는 다음 문서에 상세히 설명되어 있습니다. 증거물 V ↗.\n\nSteam 가입자 계약서 제4.C조에는 다음과 같이 명시되어 있습니다:\n\n\"어떠한 방식으로도 Steam의 콘텐츠 및 서비스와 상호작용하기 위해 스크립트, 봇, 매크로 또는 기타 사람이 직접 제어하지 않는 시스템('자동화')을 사용해서는 안 됩니다.\" — Steam 가입자 계약서 제4.C조 (현행) ↗ 보관됨 2026-09-18 ↗\n\nValve는 이 조항을 집행합니다. 그 역할을 아주 잘 수행합니다. 의 자주 묻는 질문(FAQ) ArchiSteamFarm (ASF) — 해당 도구 자체의 설명서에 따르면 다음 환경에서 실행된다고 명시된 오픈소스 도구 수백만 개가 넘는 Steam 계정 11년 전 첫 출시 이후 — 봇 네트워크를 운영하던 사용자를 영구적으로 차단한 Steam 건의 지원 메시지를 재현합니다. Valve 건은 해당 네트워크를 발견하여 이름을 밝히고 무력화시켰습니다. 따라서 핵심적인 질문은 Valve이 대규모 자동화 활동을 탐지할 수 있는지 여부가 아닙니다.\n\n이 프로젝트의 공식 ArchiSteamFarm 자주 묻는 질문 금지 조치의 위험을 직접적으로 다루고 있다:\n\n\"ASF가 11년 넘게 전에 처음 출시된 이후로 Steam 계정 중 수백만 개 이상에서 사용되고 있다는 점을 고려할 때, 이런 일이 일어날 가능성은 극히 희박하지만, 실제 확률과 무관하게 여전히 가능성은 있다.\"\n\n\"Valve은 여기서 언급된 대로 'Steam 게으름뱅이들'이 존재한다는 사실을 분명히 인정하고 있으니, 제 생각에는 만약 그들이 그런 사람들을 달가워하지 않았다면, VAC 측면에서 문제가 될 수 있다고 지적하는 대신 이미 뭔가 조치를 취했을 것이라고 확신합니다.\" 여기서 핵심은 Steam 유형의 아이들러, 예를 들어 ASF와 같은 것이며, 게임 아이들러가 아닙니다.\"\n\n— ArchiSteamFarm 자주 묻는 질문(FAQ), JustArchiNET. 출처: GitHub 위키 ↗ · 원문 그대로 확인됨 2026-09-22\n\n같은 FAQ에서는 “그 일로 인해 계정이 정지된 사람이 있나요?”라는 질문에 다음과 같이 답하고 있습니다. 네, 그리고 Steam Support가 그 중 세 명에게 보낸 내용을 다음과 같이 재인용합니다:\n\n1,000+ 봇 · 거래 금지\n\"이 계정은 봇 계정 네트워크를 관리하는 데 사용된 것으로 보입니다. 봇 활동은 Steam 가입자 약관을 위반하는 행위입니다.\"\n\n170개 이상의 봇 · 영구 차단, 2017년 겨울 세일\n\"이 계정은 Steam에서 수집용 카드를 불법적으로 수집하는 데 사용되었을 뿐만 아니라, 이와 관련된 상업적 활동 및 그 외의 활동에도 이용되었습니다. 해당 계정은 영구적으로 차단되었으며, Steam 고객지원팀에서는 이 문제에 대해 추가적인 지원을 제공할 수 없습니다.\"\n\n120개 이상의 봇 · 영구 차단\n\"이 계정과 다른 계정들은 당사의 네트워크 인프라에 과부하를 일으키는 데 사용되었으며, 이는 Steam 온라인 행동 수칙을 위반한 것입니다.\"\n\n— Steam ArchiSteamFarm FAQ의 “이 일로 인해 계정이 정지된 사람이 있나요?” 섹션에 실린 응원 메시지들. 출처 ↗ · 원문 그대로 확인됨 2026-09-22\n\n두 레코드를 나란히 놓으세요. 1,000개의 파밍 봇을 운영하던 한 개인 사용자가 적발되어, “봇 사용은 Steam 가입자 약관을 위반하는 행위”라는 통보를 받은 후 영구적으로 계정이 삭제되었습니다. 이 보고서에 언급된 상업용 플랫폼들은 자동화된 Steam 계정을 핵심 사업으로 운영하며, 그 규모도 훨씬 더 크며, 매번 로그인할 때마다 Valve의 자체 OpenID를 통해 인증을 수행하지만, 이들 중 어느 곳도 운영자별 제재 기록을 공개한 바 없습니다. 그 조항은 효과가 있습니다. 문제는 그 조항이 누구를 겨냥하고 있느냐는 것입니다.\n\nASF는 여기서 어떤 혐의도 받고 있지 않으며, Valve의 입장을 해석한 것은 ASF 측의 독자적인 견해일 뿐입니다. 해당 글의 저자는 “ASF는 Valve로부터 권한을 위임받지 않았다”고 분명히 밝히고 있습니다. 이 도구는 여기에서 측정 도구로 사용됩니다. 즉, Valve가 봇 네트워크를 탐지하고, 이를 문서로 명시하며, 영구적으로 차단한다는 사실을 보여줍니다. Valve은 자사가 승인한 상용 자동화 도구를 공개하고, 나머지 사례에 대해 취한 조치에 대한 운영자별 기록을 제시함으로써 한 문장으로 이 논의를 종결할 수 있습니다.\n\n카드 파밍이 Valve의 매출에 미치는 영향\n\n농사형 트레이딩 카드는 Steam 커뮤니티 마켓에서 판매되며, 이 마켓 내에서 성사된 각 거래마다 총 15% 정도의 수수료가 부과됩니다. 계정은 카드를 수령하기 전에 Steam에서 $5.00 USD를 지출해야 하며, 카드를 획득하려면 게임 소유권 또는 게임 내 구매가 필요합니다. 여기서는 총 매출액을 추정하지 않으며, 운영 규모는 ASF FAQ에 명시된 대로만 기재되었습니다. 또한 FAQ에는 Valve가지 구분 기준이 기록되어 있습니다. \"Steam 유휴자\" (카드 파밍) 출처: \"게임을 그냥 방치하는 사람들\"; 다음을 참조하십시오. ASF 자주 묻는 질문 ↗. 해당 메커니즘에 대한 자세한 내용은 증거물 V — 계량표 그리고 상업적 용도의 함정.\n\n제목ArchiSteamFarm — 자동 카드 파밍\n표시된 눈금수백만 개의 계정 (ASF FAQ 기준 — 정확한 활성 계정 수는 확인되지 않음)\n‘계산된’ 것이지, ‘인용된’ 것이 아니다10,880,610 ASF 자체의 Steam 그룹에 포함된 총 API 항목 수 (Steam에 표시된 바와 같이 5,360,499개는 제한 없음) — FAQ에 언급된 “수백만”은 허구가 아니라 실제 개수를 나타낸 것입니다. 88.97%에는 어떠한 종류의 Steam 금지 조항도 없습니다. 전체 금지 현황 ↗\n도구 자체 문서에 명시된 공개 사항\nASF는 (프로젝트 문서에 명시된 대로) Steam 클라이언트를 실행하지 않고 헤드리스 모드로 계정에 로그인한 후, 카드 획득을 위해 게임을 유휴 상태로 유지합니다.\nFAQ에서는 Valve이 “Steam의 무위도식자들”을 알고 있으며, “만약 그들을 달가워하지 않았다면 이미 뭔가 조치를 취했을 것”이라고 설명하고 있습니다.\n(자주 묻는 질문(FAQ)에 따르면) 11년 넘게 표적 단속 사례가 보고된 바 없으며, 이에 따라 커뮤니티 마켓 내에서 발생한 카드 판매에 대해 Steam의 총 수수료 약 15%이 부과됩니다.\nFAQ에는 운영자당 최대 10개 계정까지를 권장한다고 명시되어 있으며, 그 근거로 Valve을 제시하고 있습니다. “이 권장 사항은 내부 Valve 지침과 당사의 제안에 근거한 것입니다.” Valve에서는 이와 같은 지침을 공개한 바가 없습니다.\n동일한 FAQ에 따르면 기술적 한계는 다음과 같습니다. “단일 IP와 단일 ASF 인스턴스로 최대 100~200개의 봇을 실행할 수 있습니다.”\n농장식 플레이 시간은 Valve에 기록되며 — “보통 30분마다 한 번씩 업데이트됩니다” — § 4.C에는 “게임 플레이 통계 조작(예: 승패, 경험치, 플레이 시간 부풀리기)”이 금지 행위로 명시되어 있습니다.\n출처\nJustArchi ASF 공식 FAQ 위키 ↗ ArchiSteamFarm 저장소 ↗ 보관됨 2026-09-24 ↗\n자동화 조항은 명확합니다. ASF FAQ에는 수년 동안 이 도구가 수백만 개의 계정에서 실행되고 있다고 명시되어 있으며, 이에 대한 표적 단속 사례는 보고된 바가 없습니다. 규칙과 그 적용 사이의 괴리는 기록에 나타나 있지만, 그 원인은 여기서는 밝혀지지 않았습니다.\n전체 전시카드 경제: 그 과정, 규모, 라이선스, 그리고 이를 감독하는 주체 ↗농장이 카드 한 장을 생산하기 전에 Valve로부터 무엇을 구매해야 하는지; 카드 파밍을 그 효과에 따라 명명하는 § 4.C의 두 줄; 왜 모든 카드 현금화 방식이 Valve이 작성한 라이선스를 위반하는지, 반면 Valve는 입구에서 수수료를 부과하는지; 2025년 6월 VAC 사태와 공유 전화번호를 통한 연쇄 차단 조치를 포함한 단속 기록; 그리고 Steam 일대에서 카드 거래 및 차단 목록 서비스를 관리하던 Valve 직원 및 커뮤니티 운영자들.금지 조치 현황 조사우리는 Valve에게 농장 규모가 얼마나 되는지 묻지 않았습니다. 직접 세어보았습니다. ↗10,880,610개의 총 계정(제한 계정 및 비제한 계정)은 ArchiSteamFarm의 Steam 그룹에서 읽어오며, 사용자가 그룹 가입 설정을 해제하지 않는 한 소프트웨어는 첫 실행 시 기본적으로 이 그룹에 자동으로 가입합니다 (상업용 봇 팜과 기본 설정을 그대로 둔 일반 플레이어 모두 포함). 88.97%은 어떠한 종류의 Steam 제재도 받지 않았으며, 제재를 받은 11% 중 99.8%은 거래에 전혀 지장을 주지 않는 표면적인 커뮤니티 제재입니다. SteamRep과 교차 검증한 결과, 목록에 오른 사기꾼 중 67.77%는 반치트 제재가 해제되면 자유롭게 활동할 수 있습니다. 등록일, 지역 및 생존율별 분석 자료를 통해 — 단순한 서술이 아닌, 측정된 실제 규모를 보여줍니다.\n\nAppendix F — Working ledger\n\nRules ledger: clauses against recorded platforms\n\n규칙을 선택하면, 해당 규칙에 태그가 지정된 기록된 플랫폼 목록이 표시되며, 각 플랫폼의 주 도메인, 선언된 인증 호스트 및 저장된 링크 필터 결과가 함께 표시됩니다. 차단된 웹사이트나 로그인용 다른 도메인의 경우, 규칙을 따라 남은 경로로 이동하십시오.\n\n175연관된 기록\n이 규칙에 따라\n174 주요 도메인0 C&D 관련 내용\n규정 발췌문 / SSA §2.G\n상업적 이용 및 계정 과금\n“…exploit the Content and Services or any of its parts for any commercial purpose, except as expressly permitted elsewhere in this Agreement (including any Subscription Terms or Rules of Use).”\n기록을 따라가 보세요\n플랫폼 등록부 175\n비율로 표시된 수치는 추정치입니다.\n\n175 175 레코드 중\n\n서비스 / 상위 그룹\t주 도메인 / 등록 기관\t관찰된 인증 도메인 / 연령\t척도 / 기록된 반응\n\nCasino\n\tcsgoempire.com\n11.3 yearsRegistered 2015-06-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgoempirelogin4.com\n6.2 yearsRegistered 2020-07-20\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustreaper.com\n23.2 yearsRegistered 2003-06-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustreaper.com\n23.2 yearsRegistered 2003-06-24\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustly.com\n12.4 yearsRegistered 2014-05-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustly.com\n12.4 yearsRegistered 2014-05-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette Casino\n\tcsgofast.com\n11.5 yearsRegistered 2015-03-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsteam-login.authtofast.com\n83 daysRegistered 2026-06-30\nRDAP ↗ · authtofast.com (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tduelbits.com\n6.6 yearsRegistered 2020-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nswitchflips.com\n6.4 yearsRegistered 2020-04-21\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opener\n\tfarmskins.com\n10.5 yearsRegistered 2016-03-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsteam.kobal.cc\n9.7 yearsRegistered 2017-01-07\nRDAP ↗ · kobal.cc (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgoluck.com\n9.3 yearsRegistered 2017-05-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgoluck.com\n9.3 yearsRegistered 2017-05-18\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tinsane.gg\n7.5 yearsRegistered 2019-04-02\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.insane.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcs2skin.com\n3.5 yearsRegistered 2023-03-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncs2skin.com\n3.5 yearsRegistered 2023-03-06\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tjuice.gg\n7.9 yearsRegistered 2018-10-19\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nletmeinjuice.com\n2.4 yearsRegistered 2024-04-15\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tggdrop.com\n8.6 yearsRegistered 2018-02-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nggauth.com\n3.4 yearsRegistered 2023-05-03\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Casino\n\thowl.gg\n9.5 yearsRegistered 2017-03-16\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhowl.uno\n41 daysRegistered 2026-08-11\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tchicken.gg\n5.7 yearsRegistered 2021-01-11\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nchicken.gg\n5.7 yearsRegistered 2021-01-11\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgocasino.gg\n2.6 yearsRegistered 2024-02-17\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.csgocasino.gg\n2.6 yearsRegistered 2024-02-17\nWHOISFREAKS ↗ · csgocasino.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Casino\n\thunt.gg\n6.9 yearsRegistered 2019-11-04\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.hunt.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Battles\n\tcsbattle.com\n9.8 yearsRegistered 2016-12-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsbattle.com\n9.8 yearsRegistered 2016-12-10\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskinrave.gg\n3.1 yearsRegistered 2023-08-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinrave.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsdouble.gg\n261 daysRegistered 2026-01-03\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsdouble.gg\n261 daysRegistered 2026-01-03\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustchance.com\n8.0 yearsRegistered 2018-10-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhgfuihd.com\n7.6 yearsRegistered 2019-01-27\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Automation\n\tcobaltlab.tech\n3.5 yearsRegistered 2023-03-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncobaltauth.com\n1.7 yearsRegistered 2025-01-07\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\traided.gg\n171 daysRegistered 2026-04-03\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.raided.gg\n171 daysRegistered 2026-04-03\nIP2WHOIS ↗ · raided.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustneo.gg\n1.3 yearsRegistered 2025-06-20\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustneo.gg\n1.3 yearsRegistered 2025-06-20\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tsplits.gg\n3.7 yearsRegistered 2023-01-23\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsplits.gg\n3.7 yearsRegistered 2023-01-23\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Upgrader\n\tupgrader.pro\n1.2 yearsRegistered 2025-07-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nupgauth.space\n38 daysRegistered 2026-08-14\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskin.fans\n8.2 yearsRegistered 2018-07-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skinfans.com\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\thotpizza.one\n1.8 yearsRegistered 2024-12-07\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhotpizza.one\n1.8 yearsRegistered 2024-12-07\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tg4skins.com\n10.1 yearsRegistered 2016-08-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.g4s.to\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2royal.com\n4.1 yearsRegistered 2022-08-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ntf2auth.com\n5.2 yearsRegistered 2021-07-27\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2hunt.com\n8.7 yearsRegistered 2018-01-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrstspcl.com\n6.1 yearsRegistered 2020-08-08\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2.bet/coinflip\n8.4 yearsRegistered 2018-05-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ntf2.bet\n8.4 yearsRegistered 2018-05-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\topenstars.gg\n131 daysRegistered 2026-05-13\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nopenstars.gg\n131 daysRegistered 2026-05-13\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tskins.com\n25.1 yearsRegistered 2001-08-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skins.com\n25.1 yearsRegistered 2001-08-08\nRDAP ↗ · skins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\twhite.market\n9.6 yearsRegistered 2017-03-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwhite.market\n9.6 yearsRegistered 2017-03-01\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tmoon.market\n7.6 yearsRegistered 2019-02-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmoon.market\n7.6 yearsRegistered 2019-02-27\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tcsfloat.com\n5.2 yearsRegistered 2021-07-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgofloat.com\n11.0 yearsRegistered 2015-09-29\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tskin.land\n4.7 yearsRegistered 2022-01-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skin.land\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\thaloskins.com\n2.8 yearsRegistered 2023-12-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhaloskins.com\n2.8 yearsRegistered 2023-12-10\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCorporate Market\n\tbuff.163.com\n29.0 yearsRegistered 1997-09-15\nRDAP ↗ · 163.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\nbuff.163.com\n29.0 yearsRegistered 1997-09-15\nRDAP ↗ · 163.com (parent)\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\tmarket.csgo.com\n26.6 yearsRegistered 2000-02-07\nRDAP ↗ · csgo.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\ndota2.net\n14.9 yearsRegistered 2011-10-29\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRegulated Market\n\tskinport.com\n8.0 yearsRegistered 2018-09-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinport.app\n6.3 yearsRegistered 2020-06-20\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMarketplace/Swap\n\tskinflow.gg\n3.8 yearsRegistered 2022-11-26\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinflow.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tskin.place\n6.0 yearsRegistered 2020-09-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skin.place\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tskinsmonkey.com\n5.7 yearsRegistered 2021-01-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinsmonkey.com\n5.7 yearsRegistered 2021-01-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCorporate Market\n\tskinbaron.de\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinbaron.com\n10.7 yearsRegistered 2015-12-22\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Market\n\trust.tm\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\ndota2.net\n14.9 yearsRegistered 2011-10-29\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tpirateswap.com\n6.0 yearsRegistered 2020-09-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nlogin.pirateswap.com\n6.0 yearsRegistered 2020-09-22\nRDAP ↗ · pirateswap.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Marketplace\n\tmannco.store\n8.6 yearsRegistered 2018-03-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmannco.store\n8.6 yearsRegistered 2018-03-02\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tskinswap.com\n9.9 yearsRegistered 2016-11-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinswap.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\texeskins.com\n2.1 yearsRegistered 2024-08-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nexeskins.com\n2.1 yearsRegistered 2024-08-14\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tbalticskins.com\n153 daysRegistered 2026-04-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nbalticskins.com\n153 daysRegistered 2026-04-21\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tcs.trade\n8.9 yearsRegistered 2017-11-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncs.trade\n8.9 yearsRegistered 2017-11-14\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\trapidskins.com\n4.5 yearsRegistered 2022-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.rapidskins.com\n4.5 yearsRegistered 2022-03-11\nRDAP ↗ · rapidskins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\ttradeit.gg\n9.1 yearsRegistered 2017-08-21\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nconnect-tradeit.com\n4.6 yearsRegistered 2022-02-23\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\t49skins.com\n3.4 yearsRegistered 2023-04-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.49skins.com\n3.4 yearsRegistered 2023-04-19\nRDAP ↗ · 49skins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tskinvault.gg\n3.4 yearsRegistered 2023-05-06\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinvault.gg\n3.4 yearsRegistered 2023-05-06\nIP2WHOIS ↗ · skinvault.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Trading\n\taim.market\n3.3 yearsRegistered 2023-05-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\naim.market\n3.3 yearsRegistered 2023-05-22\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Sell Portal\n\tskinout.gg\n5.6 yearsRegistered 2021-02-27\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skinout.gg\n5.6 yearsRegistered 2021-02-27\nIP2WHOIS ↗ · skinout.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Trading\n\tntskins.com\n230 daysRegistered 2026-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nntskins.com\n230 daysRegistered 2026-02-03\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Portal\n\tgamerpay.gg\n6.0 yearsRegistered 2020-10-02\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ngamerpay.gg\n6.0 yearsRegistered 2020-10-02\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Scrap Swap\n\tscrap.tf\n14.0 yearsRegistered 2012-09-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nscrap.tf\n14.0 yearsRegistered 2012-09-03\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Cashout\n\tmarketplace.tf\n14.0 yearsRegistered 2012-09-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmarketplace.tf\n14.0 yearsRegistered 2012-09-19\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Cashout\n\tskins.cash\n10.5 yearsRegistered 2016-03-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinscash.live\n6.8 yearsRegistered 2019-12-05\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgo.net\n14.2 yearsRegistered 2012-07-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncn2.easylot.net\n10.0 yearsRegistered 2016-09-03\nRDAP ↗ · easylot.net (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCommunity Hub\n\tcybershoke.net\n6.8 yearsRegistered 2019-11-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.cybershoke.net\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMatchmaker Hub\n\tfastcup.net\n14.6 yearsRegistered 2012-02-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.fastcup.net\n14.6 yearsRegistered 2012-02-16\nRDAP ↗ · fastcup.net (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Analytics\n\tleetify.com\n7.6 yearsRegistered 2019-03-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nleetify.com\n7.6 yearsRegistered 2019-03-01\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Analytics\n\tscope.gg\n7.8 yearsRegistered 2018-12-10\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nscope.gg\n7.8 yearsRegistered 2018-12-10\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tools\n\ttradeupspy.com\n6.5 yearsRegistered 2020-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.tradeupspy.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMarketplace\n\tcs.deals\n9.8 yearsRegistered 2016-12-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.cs.deals\n9.8 yearsRegistered 2016-12-03\nRDAP ↗ · cs.deals (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Price DB\n\tpricempire.com\n6.6 yearsRegistered 2020-01-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\npricempire.com\n6.6 yearsRegistered 2020-01-30\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Blackmarket\n\tFSB Market\n7.2 yearsRegistered 2019-07-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nFSB Market\n7.2 yearsRegistered 2019-07-27\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nReady-Account Hub\n\tz2u.com\n26.9 yearsRegistered 1999-11-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwww.z2u.com\n26.9 yearsRegistered 1999-11-10\nRDAP ↗ · z2u.com (parent)\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Gambling\n\tcsgoroll.com\n11.6 yearsRegistered 2015-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwww.csgoroll.com\nRegistry date unavailableRegistry date unavailable\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\trollbit.com\n11.9 yearsRegistered 2014-11-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrbsnin.com\n3 daysRegistered 2026-09-18\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nLicenced Casino\n\t500.casino\n5.9 yearsRegistered 2020-11-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette/Slots\n\tcsgobig.com\n11.4 yearsRegistered 2015-04-12\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcasedrop.com\n14.8 yearsRegistered 2011-12-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\tbanditcamp.com\n12.2 yearsRegistered 2014-06-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tskinbox.com\n18.8 yearsRegistered 2007-12-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\ttastydrop.com\n6.1 yearsRegistered 2020-08-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette Casino\n\tcsgopolygon.gg\n6.5 yearsRegistered 2020-03-28\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tmagicdrop.ru\n10.3 yearsRegistered 2016-05-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nDice Casino\n\tcsdice.com\n3.8 yearsRegistered 2022-11-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUpgrader Casino\n\tskinodds.com\n1.2 yearsRegistered 2025-06-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgowin.com\n12.0 yearsRegistered 2014-09-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrash Casino\n\tcsgorun.net\n7.3 yearsRegistered 2019-06-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\topenskins.com\n3.6 yearsRegistered 2023-02-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Gambling\n\trustbet.com\n7.6 yearsRegistered 2019-02-07\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgomagic.com\n9.4 yearsRegistered 2017-05-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUpgrader/Contract\n\tcsgobounty.com\n11.5 yearsRegistered 2015-03-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tezskins.com\n27.5 yearsRegistered 1999-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\trustcases.com\n7.2 yearsRegistered 2019-06-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgoreaper.com\n11.1 yearsRegistered 2015-08-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgocases.com\n12.3 yearsRegistered 2014-06-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Upgrader\n\tcsgo-skins.com\n11.2 yearsRegistered 2015-07-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgonet.com\n8.8 yearsRegistered 2017-12-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\twtfskins.com\n9.0 yearsRegistered 2017-10-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Casino\n\tflamecases.com\n10.0 yearsRegistered 2016-09-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tgamedom.com\n11.7 yearsRegistered 2015-01-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Battles\n\tskin.club\n9.0 yearsRegistered 2017-09-04\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsc-auth.net\n7.5 yearsRegistered 2019-04-02\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tdaddyskins.com\n9.9 yearsRegistered 2016-10-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Gambling\n\trustix.gg\n1.7 yearsRegistered 2025-01-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Upgrade\n\tskins.club\n4.2 yearsRegistered 2022-07-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgohouse.org\n146 daysRegistered 2026-04-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskinrave.net\n216 daysRegistered 2026-02-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tbloodycase.gg\n19 daysRegistered 2026-09-02\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nClicker/Upgrade\n\tcsgoclicker.com\n8.3 yearsRegistered 2018-05-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustbet.gg\n4.0 yearsRegistered 2022-09-30\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcs-drop.com\n262 daysRegistered 2026-01-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\thellstore.net\n11.7 yearsRegistered 2015-01-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustloot.com\n354 daysRegistered 2025-10-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgo-case.com\n10.3 yearsRegistered 2016-05-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgogem.com\n9.9 yearsRegistered 2016-10-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\trainbet.com\n8.8 yearsRegistered 2017-11-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nservices.rainbet.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustclash.com\n5.4 yearsRegistered 2021-05-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrash Casino\n\t12cs.fail\n181 daysRegistered 2026-03-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\twww.tf2easy.com\n6.3 yearsRegistered 2020-06-02\nRDAP ↗ · tf2easy.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2blaze.com\n7.6 yearsRegistered 2019-01-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tshuffle.com\n30.1 yearsRegistered 1996-07-31\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tbuff.market\n5.9 yearsRegistered 2020-10-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tavan.market\n8.3 yearsRegistered 2018-05-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Engine\n\tcs.money\n11.0 yearsRegistered 2015-09-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.dota.trade\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tuuskins.com\n2.6 yearsRegistered 2024-01-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Market\n\tyoupin898.com\n6.1 yearsRegistered 2020-08-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tc5game.com\n10.5 yearsRegistered 2016-03-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\twaxpeer.com\n7.3 yearsRegistered 2019-05-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwaxpeer.com\n7.3 yearsRegistered 2019-05-20\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBot Trading\n\tcs.money\n11.0 yearsRegistered 2015-09-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.dota.trade\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUS Marketplace\n\tdmarket.com\n30.2 yearsRegistered 1996-07-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nOfficial Market\n\tsteamcommunity.com/market\n20.3 yearsRegistered 2006-05-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNot an external login site2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Platform\n\tlootfarm.com\n11.9 yearsRegistered 2014-10-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Market\n\trustskins.com\n7.6 yearsRegistered 2019-01-31\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tkrakatoa.com\n26.4 yearsRegistered 2000-05-15\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\tshadowpay.com\n10.1 yearsRegistered 2016-08-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nChinese Powerhouse\n\tigxe.cn\n15.0 yearsRegistered 2011-09-06\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAutomated Swap\n\tswap.gg\n9.6 yearsRegistered 2017-01-29\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCash-out Portal\n\tbitskins.com\n11.2 yearsRegistered 2015-07-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Automation\n\ttf2mart.com\n1.1 yearsRegistered 2025-08-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Auctions\n\tskinbid.com\n10.2 yearsRegistered 2016-06-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Rental\n\tlootbear.com\n8.7 yearsRegistered 2018-01-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Valuation\n\tbackpack.tf\n14.4 yearsRegistered 2012-05-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Botnet\n\tstntrading.eu\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Cashout\n\tskinwallet.com\n18.0 yearsRegistered 2008-09-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nDota 2 Market\n\tdota2market.com\n12.2 yearsRegistered 2014-07-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nServer Network\n\txplay.gg\n5.3 yearsRegistered 2021-06-13\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMatchmaking Portal\n\tesportal.com\n26.8 yearsRegistered 1999-12-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nLATAM Hub\n\tgamersclub.com.br\n11.2 yearsRegistered 2015-06-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tools\n\tepidemic.gg\n4.9 yearsRegistered 2021-11-03\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tcs2stash.com\n3.5 yearsRegistered 2023-03-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tcsgoskins.gg\n6.8 yearsRegistered 2019-12-21\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tsteamanalyst.com\n12.6 yearsRegistered 2014-02-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Exchange\n\tsteamcardexchange.net\n13.3 yearsRegistered 2013-05-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tracker\n\tdotabuff.com\n14.2 yearsRegistered 2012-06-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tracker\n\ttracker.gg\n8.9 yearsRegistered 2017-10-12\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Exchange\n\tfunpay.com\n17.0 yearsRegistered 2009-09-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nGrey Market\n\tplayerauctions.com\n26.3 yearsRegistered 2000-06-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Portal\n\teldorado.gg\n8.0 yearsRegistered 2018-09-12\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Key Market\n\tg2a.com\n24.8 yearsRegistered 2001-12-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Key Market\n\tkinguin.net\n16.8 yearsRegistered 2009-12-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nVirtual Services\n\tg2g.com\n31.1 yearsRegistered 1995-08-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Broker\n\tplayerup.com\n19.3 yearsRegistered 2007-05-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfhub.net\n2.7 yearsRegistered 2023-12-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfaccounts.com\n5.3 yearsRegistered 2021-05-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Shop\n\tbuycsgorank.com\n6.2 yearsRegistered 2020-07-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tcsgosmurfkings.com\n9.3 yearsRegistered 2017-06-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfstore.co\n8.6 yearsRegistered 2018-03-03\nWHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlvlup.com\n9.9 yearsRegistered 2016-11-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlevels.com\n10.6 yearsRegistered 2016-02-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tlevelsteam.com\n79 daysRegistered 2026-07-04\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlevelu.com\n6.0 yearsRegistered 2020-09-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\teloking.com\n12.2 yearsRegistered 2014-07-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\tboosteria.org\n11.9 yearsRegistered 2014-10-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tovergear.com\n14.4 yearsRegistered 2012-04-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tblazingboost.com\n14.2 yearsRegistered 2012-06-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\tdota2boost.com\n2.9 yearsRegistered 2023-10-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tbuyboost.com\n22.4 yearsRegistered 2004-04-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n수사의 주장선택된 규칙 / 분석 및 해설+\n증명의 책임\n\n이번 조사는 상업적 이용에 대한 제한과 여기에 기록된 서비스 간의 불일치 문제를 제기합니다. 각 활동을 분류하고, 계약 위반으로 간주하기 전에 명시적인 허가 여부를 확인하십시오. 커뮤니티 마켓 수수료는 모든 외부 거래에 적용되는 것은 아닙니다.\n\n태그가 지정된 레코드란 무엇이며, 무엇이 아닌가\n\n해당 서류에 날짜가 명시된 관찰 내용이 포함되어 있어 플랫폼이 해당 조항의 적용 범위에 명백히 해당될 경우, 해당 기록에 태그가 지정됩니다. 태그는 확정된 위반 사항이 아니며, 여기에 나열된 어떤 플랫폼에 대해서도 기록상 명시적인 Valve 허가가 제시된 바 없습니다. 플랫폼이 승인을 보유하고 있는 경우, 이를 게시함으로써 해당 항목이 해결됩니다.\n\n출처 및 방법론추정치, 정의 및 적용 범위+\n\n위의 수치는 선택한 규칙을 기준으로 합니다. 레코드 유형은 각 플랫폼을 한 번씩 그룹화하며, 전체 태그는 플랫폼 세부 정보에 표시됩니다. 검색 및 필터는 해당 규칙 내에서 적용됩니다. 등록 날짜는 저장된 RDAP / WHOIS 스냅샷에서 가져옵니다. 하위 도메인은 상위 도메인의 생성 날짜를 사용합니다. 운영 기간만으로는 지속적인 운영이나 인증 경로를 입증할 수 없습니다. 현재 인증 호스트 이름은 UTC 타임스탬프가 포함된 저장된 OpenID 요청에서 가져오며, 해결되지 않은 확인 항목은 기존 레이블을 재사용하지 않습니다. 관찰기는 Steam 로그인 단계 이전에 중지되며, Steam 링크 필터 상태를 테스트하지 않습니다. 경로 관측 자료 다운로드 ↗ 레지스트리 결과 다운로드 ↗\n\n소스 아카이브 살펴보기 ↗\n부록 G — 거절 통지서 양식에서 원본 기록으로\nDSAR 대응 지침서: 증거 제출 요청\n\nGDPR 제15조를 근거로 API 키 생성, 계정 복구 및 지원 서비스 이용과 관련된 개인정보를 요청할 수 있습니다. 보관된 기록을 통해 누가 해당 조치를 시작했는지, 그리고 플랫폼이 어떤 근거에 따라 조치를 취했는지 확인할 수 있습니다.\n\n01\n타임라인을 잘 보관하세요.\n\n계정 알림, 티켓, 거래 ID 및 날짜를 UTC 기준으로 저장하십시오. 계정을 안전하게 보호하고, 해당 게임 및 거래에 적용되는 복구 옵션을 확인하십시오.\n\nSteam 무역 보호 정보 ↗\n02\n보관 중인 데이터를 요청하세요.\n\n타임스탬프, 소스 IP, 주요 라이프사이클 이벤트, 보안 확인 내역 및 계정 관련 복구 조치에 대한 정보를 요청하십시오. 해당 데이터가 귀하와 관련된 경우, 지원 액세스 이벤트 및 수신자 정보도 포함시키십시오.\n\n03\n배송 내역을 보관해 두세요.\n\nValve의 개인정보 보호 문의 절차를 이용하십시오. 일반적인 답변 기간은 1개월이며, 1개월 이내에 최대 2개월까지의 연장이 필요한 경우 그 사유를 설명해야 합니다.\n\nValve 개인정보 보호 문의 경로 ↗ 보관됨 2026-09-21 ↗\n04\n두 응답을 비교해 보세요.\n\n로그 내용을 귀하의 타임라인과 대조해 보십시오. 누락된 부분에 대한 이유를 문의한 뒤, 필요한 경우 감독 당국에 민원을 제기하십시오. 받은 답변을 받은 그대로 보존하십시오.\n\n적용 범위 / 제15조\n\n접근 권한은 로그에 포함된 데이터를 포함한 보유 중인 개인 데이터에 적용됩니다. 이는 모든 내부 문서, 재구성된 기록 또는 타인에 관한 비편집 데이터를 보장하지는 않습니다. 이해하기 쉬운 사본과 제한 조치의 근거를 요청하십시오.\n\nEDPB 접근 지침, 제2조, 제4조~제6조 ↗ · GDPR 제12조, 제15조, 제77조 ↗ 보관됨 2026-09-20 ↗\n\n정보 주체의 정보 열람 청구GDPR / 제15조\n계정 보안 및 접속 내역\n\n제출하기 전에 괄호로 묶인 필드의 내용을 변경하십시오.\n\nTo: Valve Privacy Team\nSubject: Article 15 GDPR request — account security records\n\nAccount / SteamID: [YOUR ACCOUNT IDENTIFIER]\nRelevant period (UTC): [START] to [END]\nRelated support tickets: [TICKET REFERENCES]\n\nI request a copy of the personal data concerning me that you retain for this period, including:\n\n1. API-key registration, confirmation, use and revocation events, with available timestamps, source IP addresses, registered domains, device or user-agent information and non-secret key identifiers.\n\n2. Recorded account-recovery actions, password/email/phone changes, Steam Guard removals or resets, confirmation events and the account-related evidence relied on to authorize those actions.\n\n3. Personal data in support-access and administrative-action logs concerning my account, including available dates, purposes, actions and the support entity involved, subject to applicable rights of others.\n\n4. Account-related records used to determine any sanction, and available records of my complaints, reviews and responses.\n\nPlease also provide the applicable processing purposes, categories, recipients, retention periods or criteria, and available information about sources where data were not obtained from me.\n\nWhere processing relies on my consent, please provide the retained record of the consent relied upon and the wording presented at that time.\n\nPlease provide an intelligible electronic copy with time zones and field definitions. Please do not include active credentials or secret tokens. If any requested data are not held, please say so. For any withheld data, please identify the scope and legal basis of the restriction and provide the remainder.\n\nPlease acknowledge receipt and respond within the applicable Article 12 period, explaining any necessary extension. I also ask you to preserve relevant existing records while this request is handled.\n\nName: [YOUR NAME]\nDate: [DATE]\n데이터센터 IP가 구축할 수 있는 것\n불일치는 조사해야 할 증거입니다.\n\n본 조사에서 제기된 호스팅 제공업체 사례와 같이 데이터 센터 네트워크에서 발생한 API 키 요청은 로그인 기록, 확인 내역 및 사용자의 타임라인과 대조해 볼 때 관련성이 있을 수 있습니다. IP 주소만으로는 행위자를 식별할 수 없으며, 모든 방어 수단을 자동으로 무력화시키지도 않습니다. 적대적 행위자가 기록된 동의를 제공했다는 증거가 있다면, 해당 동의에 대한 신뢰성에 의문을 제기할 수 있으며, 그 외의 법적 근거 및 책임 문제는 별도의 분석이 필요합니다.\n\n보존된 금지 조치 및 GDPR 관련 민원 보기 →\n부록 H — 웨이백 머신 아카이브 분석 · 공개된 지원 통계\n지원 처리량. 공개된 응답 시간.\n문맥 및 출처 제한\n\nValve는 매일 지원 통계를 다음 주소에서 공개합니다. store.steampowered.com/stats/support. 웨이백 머신(Wayback Machine) 아카이브에는 2018년부터 2026년까지 이 페이지의 과거 기록이 보관되어 있습니다. 이 수치에서 암시되는 처리량 대 인력 비율은 공개된 응답 시간 기준으로는 티켓당 인력 검토 방식과 일치하지 않습니다.\n\n저장된 스냅샷에 포함된 Valve의 과거 지원 수치를 비교해 보세요. 방법론 섹션에서는 해당 수치가 무엇을 측정할 수 있고 무엇을 측정할 수 없는지 설명하고 있습니다.\n\n처리량 대 발표된 응답 시간 (2018년 → 2026년)\n한 지원 데스크에 형성된 두 줄의 대기열을, 21개의 보관된 화면 캡처 이미지를 통해 확인할 수 있습니다.\n\nValve은 실시간 지원 통계를 다음에서 공개합니다. store.steampowered.com/stats/support. 아래의 각 점은 인터넷 아카이브가 해당 페이지를 캡처한 당일에 그 페이지에 실제로 표시되어 있던 하한값 Valve 그 자체이며, 우리가 추정한 값이 아닙니다. 두 수열은 모두 동일한 단위의 동일한 측정값이므로, 하나의 축에 표시되어야 하며 서로 직접 비교하여 읽을 수 있습니다.\n\n환불 요청 — money Valve을 보유하고 있다계정 보안 및 복구 — 분실한 계정\n0 h\n2 h\n4 h\n6 h\n8 h\n10 h\nno captures · 38 months\n2019\n2020\n2021\n2022\n2023\n2024\n2025\n2026\n8 h 44 m\naccount recovery\n52 m\nrefunds\n15 m — one capture only\n49–55분2018년 2월부터 2026년 8월까지의 모든 캡처에서 환불 하한치는 다음과 같습니다. 8년 반 동안 이 하한치는 6분 미만으로 변동한 반면, 일일 환불량은 9배나 변동했습니다.\n2.4시간 → 8.7시간2022년 12월까지의 모든 캡처 데이터에서 계정 복구 하한값은 한 건을 제외하고 모두 2.4시간 근처에 위치한다. 2026년의 세 건의 캡처 데이터에서 Valve은 각각 10.9시간, 5.8시간, 8.7시간을 보고했다.\n×2.8 → ×13Valve이 직접 공개한 수치에 따르면, 환불에 비해 환급 처리 속도가 얼마나 더 느린지 알 수 있습니다. 5년 동안은 비슷한 수준을 유지하다가 그 후 격차가 벌어지는데, 속도가 더 느려진 대기열은 Valve이 아닌 사용자가 비용을 먼저 부담해야 하는 경우입니다.\n\n출처: 21개의 웨이백 머신 캐치 store.steampowered.com/stats/support, 2018-02-03부터 2026-08-10까지; 추출 위치: VALVE_EVIDENCE_PACK/databases/steam_support_stats_history.json. 그림과 함께 한계를 확인해 보세요. 이 차트는 아래쪽 범위의 하한인 Valve 건이 기록되었습니다. 발표된 상한치는 두 항목 모두에서 더 나쁩니다. 환불 소요 시간은 1.5시간에서 1.5일 사이, 복구 소요 시간은 7.0시간에서 3.6일 사이였습니다. 동일한 Valve 페이지의 현지화판 — 체코어 2018-11-03, 프랑스어 2020-03-25 — 에 두 개의 캡처가 보관되어 있으며, 표에서는 (cs)와 (fr)으로 표시되어 있습니다. 해당 수치는 단위 명칭을 번역하고 숫자는 발표된 그대로 여기 표에 제시되었으며, 원본 문자열은 추출 파일에 그대로 보존되어 있습니다. 모든 캡처는 두 큐 모두에 대한 응답 시간을 공개했으며, 두 선상의 어떤 점도 보간되지 않았습니다. 2020-10-21라는 15분 단위 복구 수치는 차트에 표시되어 있으며 그대로 남겨두었습니다. 이 수치는 단 하나의 캡처에만 나타나며, 다른 어떤 캡처도 이 수치와 한 차수 범위 내에 들어가지 않습니다. 2022-12-08과 2026-02-01 사이에는 캡처 데이터가 존재하지 않습니다. 기록상의 이 38개월 간 공백은 음영 처리되었으며, 그 위에는 아무것도 표시되지 않았습니다. 이 수치들은 공개된 응답 시간을 나타냅니다. 이는 티켓 내부에서 어떤 일이 발생하는지는 보여주지 않으며, Valve은 이를 해석할 수 있는 인원 수를 공개하지 않았습니다.\n\n모든 캡처 내용을 표 형식으로 열기\n게시된 모든 아카이브된 캡처\n캡처\t환불 / 일\t환불 관련 답변\t회복 / 일\t복구 대응\n2018-02-03\t98,788\t50.12분에서 1.52시간\t25,662\t2.51시간에서 1.80일\n2018-05-07\t60,494\t53.83분에서 1.47일\t24,226\t2.45시간에서 2.22일\n2018-08-02\t69,084\t50.27분에서 1.59시간\t28,953\t2.44시간에서 22.17시간\n2018-11-03 (cs)\t63,410\t49.28분에서 1.54시간\t33,910\t2.42시간에서 1.31일\n2019-02-01\t76,305\t50.13분에서 1.52시간\t35,164\t2.44시간에서 2.04일\n2019-05-18\t78,951\t51.03분에서 3.12시간\t27,514\t2.46시간 ~ 20.39시간\n2019-09-07\t78,941\t50.65분에서 1.66시간\t28,812\t2.42시간 ~ 13.59시간\n2019-12-13\t69,589\t50.77분에서 1.55시간\t25,322\t2.45시간에서 1.13일\n2020-03-25 (fr)\t139,278\t49.45분에서 1시간 53분\t32,302\t2.48시간에서 3.62일\n2020-06-26\t278,504\t48.98분에서 2.29시간\t20,343\t2.39시간 ~ 6.99시간\n2020-10-21\t107,633\t50.80분에서 1.54시간\t20,688\t15.33분에서 8.62시간\n2021-03-20\t158,956\t50.80분에서 1.64시간\t25,760\t2.34시간에서 11.62시간\n2021-06-26\t547,907\t51.93분에서 6.73시간\t29,728\t2.40시간에서 15.63시간\n2021-10-10\t170,103\t51.88분에서 3.25시간\t23,989\t2.39시간에서 13.05시간\n2022-01-31\t354,386\t53.65분에서 8.09시간\t24,391\t2.42시간에서 15.29시간\n2022-05-09\t172,555\t51.83분에서 1.65시간\t23,289\t2.41시간에서 16.90시간\n2022-09-05\t153,453\t53.67분에서 4.15시간\t23,594\t2.45시간에서 1.22일\n2022-12-08\t181,075\t54.83분에서 6.67시간\t27,111\t2.46시간에서 18.89시간\n2026-02-01\t317,762\t50.30분에서 1.52시간\t47,197\t10.91시간부터 21.30시간까지\n2026-05-09\t246,776\t50.12분에서 1.52시간\t35,264\t5.81시간에서 15.60시간\n2026-08-10\t373,244\t52.05분에서 2.07시간\t45,319\t8.73시간에서 16.52시간\n주요 관찰 사항:\n횡단 21개의 웨이백 아카이브 2018-02-03부터 2026-08-10까지의 기간 동안, 일일 환불 신청 건수는 60,494 (2018년 5월) ~ 547,907 (2021년 6월) — a 9.1× 스프레드. 2026년 수치는 373,244입니다(2018년 2월 집계치 대비 +278%).\n그 9년 동안 환불 처리 시간에 대해 발표된 하한치는 한 번도 49–55분 밴드: 6분 미만의 총 이동 시간 동안, 그 배후의 작업량이 9배나 증가했다.\n만약 한 사람이 각 티켓을 단 5초씩만 읽는다 해도, 하루에 373,244개의 티켓을 처리하는 데(현재 기준)는 24시간 연중무휴로 근무하는 22명의 요원 단순히 열고 닫는 데만도; 정점(547,907, 2021년 6월)에서는 이 수치가 32까지 치솟습니다.\n공개된 응답 시간이 티켓당 처리 시간(티켓당 약 52분)을 반영한 것이라면, 이를 바탕으로 추산한 동시 근무 인원은 대략 13,500 요원 현재 볼륨 기준이며, 피크 시에는 ~20,000입니다. Valve의 지원 인원에 대한 출처가 명시된 수치는 확인되지 않았으며, 여기서는 해당 수치를 가정하지 않습니다.\n다음과 같은 사실이 드러납니다. 처리량 대비 인원 비율을 고려할 때, 공개된 응답 시간 내에서는 티켓당 수작업 검토가 이루어지기 어렵습니다. 이 수치는 1차 검토가 대체로 자동화된 방식임을 시사하며, 수작업 검토를 거치는 티켓의 비율은 공개되지 않았습니다.\n이것이 GDPR 준수에 있어 왜 중요한가\n\nGDPR 제22조는 요청 시 사람의 검토를 받을 권리를 부여하지 않은 채, 중대한 법적 효과를 초래하는 전적으로 자동화된 개별 의사결정을 금지하고 있습니다. 만약 Steam 지원 관련 결정(티켓 종료, 계정 조치, 데이터 요청 거부)이 전적으로 자동화된 스크립트에 의해 이루어지는 경우, 사용자에게 “상당한 영향을 미치는” 모든 결정은 제22조를 위반할 수 있습니다.\n\n티켓 HT-2YBP-F7JP-D4VB (제18조)는 3일 만에 정형화된 회신 양식을 첨부한 채, 인용된 법적 근거에 대한 어떠한 논의도 없이 종결되었습니다. 해당 티켓만으로는 누군가 이를 검토했는지 여부를 확인할 수 없으며, 이는 감독 당국이 제22조 및 제15조 제1항 (h)호에 따라 Valve에게 질의할 수 있는 사항입니다.\n\n출처: store.steampowered.com/stats/support의 Wayback Machine 스냅샷 (2018-02-03, 2021-06-26, 2026-08-10) — VALVE_EVIDENCE_PACK/databases/steam_support_stats_history.json 파일로 추출된 데이터 (스냅샷 21개, 2018–2026년). 참고: “~52분” 응답 시간은 환불 카테고리의 하한값이며, 동일한 스냅샷에서 계정 보안 관련 응답 시간은 2.4–16.5시간이었습니다. 2021-06-26은 역대 최고치(547,907 환불 요청 건수)이며, 단조로운 추세의 중간점이 아닙니다. 2020–2021년에 건수가 약 6배 급증한 후 일시적으로 감소했다가 2026년에 373K로 회복되었습니다.\n부록 I — 데이터셋 범위 · 재현 가능한 계수\n레코드 수를 세어보세요. 범위를 확인해 보세요.\n문맥 및 출처 제한\n\n기록을 세어본 다음 주장을 검증해 보십시오. 아래의 모든 수치는 공개된 파일에서 다시 도출할 수 있습니다.\n\n기본 데이터 세트를 검토하고, 집계 결과를 재현하며, 원본 행과 고유한 사건을 구분하십시오.\n\n마스터 CSV 파일에는 다음 내용이 포함되어 있습니다. 40,448 행. 이 중, 36,516 디스코드-안티스캠 피싱 피드에서 나온 것입니다. 나머지 3,932 이 항목들은 GitHub, 리뷰, 검색 결과, 포럼 게시물 및 기타 출처를 아우르며, 커뮤니티에서 제기된 주제와 보안 보고서에 대한 포괄적인 색인을 제공합니다.\n\n해당 CSV 파일 내에서 1,690개의 행이 “패치되지 않은 보안 취약점(Unpatched Security Exploit)” 컬렉션 레이블로 분류되어 있으며, 이는 과거의 사용자 문제 및 취약점 공개 내역을 나타냅니다. 이러한 보고서를 추적하려면 각 스레드의 구체적인 빌드 타임라인과 공개 패치 내역을 검토해야 합니다.\n\n16,319-레코드 검색 가능 아카이브는 특정 사용자의 주장 및 사고 보고서를 로컬에서 정밀하게 탐색할 수 있도록 설계된, 별도의 큐레이션된 빌드로, 자체 매니페스트를 갖추고 있습니다.\n\n신뢰할 수 있는 감사 추적을 구축하려면, 사용자가 보고한 모든 기록을 문서화된 빌드 일정 및 과거 패치 로그와 대조하여 검증해야 합니다.\n\n별도의 제2부 소장 기록 231,829 고유 목록 ID, 여기에는 자동 등록 범주에 속하는 33,509과 미확인 이체로 표시된 198,320이 포함됩니다. 입력 파일의 SHA-256 해시는 보존된 측정값과 일치합니다. 이러한 집계 수치는 최종 확정된 거래 금액이나 검증된 도난 총액이 아닌, 상장 시도 및 관측된 이체 건수를 나타내므로, 정확한 경제적 영향을 측정하기 위해서는 플랫폼의 1차 기록이 필요함을 시사합니다. 측정값 및 해시 목록 ↗\n\nCSV 마스터하기 ↗ · 검색 가능한 아카이브 목록 ↗ · 원본 기록 확인 ↗\n\n부록 J — 본 조사에 관하여\nValve은 집행 기록을 공개하지 않습니다. 우리가 하나 만들었습니다.\n\n독립적입니다. 비영리 목적입니다. 오직 공개 데이터만을 바탕으로 제작되었습니다. 규제 당국에 제출되었습니다.\n\n88.97%자동화 차량은 그대로 유지 — 어떠한 금지 조치도 없음\n67.77%51,732명의 유죄 판결을 받은 사기범들이 풀려났다\n$26.8M+비한정 차량군의 매장 내 지출 하한선\n3.6%Valve의 링크 필터에 의해 차단된 도박 관련 도메인\n8년기록된 보안 사고 중\n\n이게 뭔지. Valve 코퍼레이션의 Steam 플랫폼에 대한 포렌식 분석 보고서 — 해당 플랫폼의 집행 실적, 카드 파밍 경제, 법적 체계, 그리고 도박 사업자들이 Steam의 자체 OpenID 릴레이를 통해 사용하는 인증 인프라. 모든 수치는 Valve의 공개 API와 본 조사와 함께 공개된 데이터 세트, 이 두 가지 출처를 통해 재현 가능합니다.\n\n대상. Valve에 대한 관할권을 가진 규제 기관 — 네덜란드의 GDPR 감독 기관, FinCEN, SEC, DSA 디지털 서비스 코디네이터, UOKiK, 그리고 Steam과 관련된 자금 흐름을 조사하는 모든 법 집행 기관. 또한, 영구 계정 정지 조치를 당했거나, 환불 요청이 거부되었거나, 보유 아이템을 도난당했음에도 항소할 수 없다는 통보를 받은 언론인, 연구자 및 모든 사용자도 해당됩니다.\n\n단 하나의 요구. Valve은 이 데이터를 완전한 정확도로 보관하고 있습니다. 제재 사유도 포함되어 있으며, 전체 ID 영역을 실시간으로 처리합니다. 이 자료집에 포함된 모든 쿼리를 몇 초 만에 실행할 수 있음에도 불구하고, 해당 정보는 일절 공개하지 않기로 결정했습니다. 유능한 당국이 던져야 할 질문은 간단합니다: 왜 안 되겠어요?\n\n저자들이 주장하지 않는 바. 이번 조사 기간 동안 어떤 제3자 플랫폼에서도 Steam에 대한 로그인이 완료된 적이 없습니다. 제공된 OpenID URL은 요청 매개변수를 확인할 뿐, 로그인이 완료되었음을 입증하지는 않습니다. 별도의 등록 가능한 도메인이 있다고 해서 그 자체로 회피 행위의 증거가 되는 것은 아닙니다. 등록 날짜는 호스트가 OpenID 요청에 처음 등장했을 수 있는 시기의 하한일 뿐이며, 지속적인 사용을 입증하지는 않습니다. 저자들은 Valve이 무엇을 알고 있었는지 또는 의도했는지에 대해서는 주장하지 않습니다. Valve에 대한 모든 진술은 날짜가 명시된 공개 문서나 날짜가 명시된 관찰 기록에 근거합니다. 출처 문서를 근거로 삼을 수 없는 주장은 삭제되었습니다.\n\n회사 소개\n\nPhishDestroy — 독립 조사관들입니다. Valve Corporation이나 여기에 언급된 그 어떤 플랫폼과도 관련이 없습니다. Steam 계정은 제18항에 명시된 GDPR 요청을 기록하는 용도로만 사용되었습니다.\n\n법적 고지\n\n비영리적이며 분산된 공익 조사입니다. 모든 데이터는 “있는 그대로” 제공되며 어떠한 보증도 없습니다. 본 간행물은 사법적 판결이 아닙니다.\n\n퍼블릭 도메인\n라이선스\n\n모든 권리는 인류에게 양도됩니다. 복제, 개작, 출판 — 출처 표기는 필요하지 않습니다. OFAC 관할 지역에서의 접근: 금지됩니다. 전체 이용 약관 및 면책 조항 →",
        "headings": [
          {
            "level": 2,
            "id": "briefing-heading",
            "text": "규칙. 기록. 풀리지 않은 의문들."
          },
          {
            "level": 2,
            "id": null,
            "text": "워싱턴주 도박위원회에 보내는 공개 서한"
          },
          {
            "level": 3,
            "id": "wsgc-public-address-title",
            "text": "10일이 10년으로 변했다.레코드를 다시 엽니다."
          },
          {
            "level": 2,
            "id": null,
            "text": "해당 사이트는 차단되었지만, 로그인 경로는 차단되지 않았습니다."
          },
          {
            "level": 3,
            "id": null,
            "text": "그림 3.1 — 두 경로를 표시한 그림."
          },
          {
            "level": 3,
            "id": null,
            "text": "‘큰 그림’의 함정: 링크 필터는 ‘규정 준수 쇼’일 뿐, 방어막은 아니다"
          },
          {
            "level": 3,
            "id": null,
            "text": "차단된 메인 도메인과 차단되지 않은 인증 호스트가 결합되면 로그인 경로가 열려 있게 되며, 이 상태는 수년 동안 지속됩니다."
          },
          {
            "level": 3,
            "id": null,
            "text": "배경: Steam이란 무엇이며, 왜 이 맥락에서 중요한가"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve의 기능: 도메인 차단"
          },
          {
            "level": 3,
            "id": null,
            "text": "프록시 도메인이란 무엇인가"
          },
          {
            "level": 3,
            "id": null,
            "text": "중요한 점: 모든 요청에서 인증 호스트가 Steam으로 전송됨"
          },
          {
            "level": 3,
            "id": null,
            "text": "이것이 무엇을 증명하는가"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam 내부에서는 Valve의 리스트가 유일한 리스트입니다."
          },
          {
            "level": 3,
            "id": null,
            "text": "링크 필터 보호 기능 우회"
          },
          {
            "level": 3,
            "id": null,
            "text": "'Big Picture' 웹 브라우저에서 로그인 쿠키가 유출되고 민감한 정보가 노출됩니다(계정 탈취로 이어질 수 있음)."
          },
          {
            "level": 3,
            "id": null,
            "text": "바이러스 백신 프로그램이 설치된 미성년자에게 이것이 의미하는 바는 무엇일까요?"
          },
          {
            "level": 3,
            "id": null,
            "text": "도메인의 개설 기간.관측 날짜."
          },
          {
            "level": 2,
            "id": null,
            "text": "엔드포인트가 닫혔습니다. 공개 추적에서 키가 손실되었습니다."
          },
          {
            "level": 3,
            "id": null,
            "text": "정전 이전 시대"
          },
          {
            "level": 3,
            "id": null,
            "text": "변경 후"
          },
          {
            "level": 2,
            "id": null,
            "text": "단 한 번의 세션. 사용자가 인식하는 것보다 더 많은 접근 권한."
          },
          {
            "level": 3,
            "id": null,
            "text": "1. 강화된 인증 절차 미비"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. 최소 권한 원칙의 미준수"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. 세션 관리 오류"
          },
          {
            "level": 3,
            "id": null,
            "text": "4. 인증 호스트에 대한 도메인 수준 차단은 기술적으로 가능했다"
          },
          {
            "level": 3,
            "id": "integration-paradox-title",
            "text": "Valve는 매일 이 규칙에 따라 빌드됩니다. 하지만 여기서는 이 규칙에 따라 빌드되지 않았습니다."
          },
          {
            "level": 4,
            "id": null,
            "text": "GitHub의 세분화된 범위와 Valve Steam 웹 API 비교"
          },
          {
            "level": 2,
            "id": null,
            "text": "대화형 익스플로잇 및 하이재킹 시뮬레이터"
          },
          {
            "level": 2,
            "id": null,
            "text": "시퀀스 뒤에 있는 엔드포인트."
          },
          {
            "level": 2,
            "id": null,
            "text": "체크된 상자. 누구의 행동인가?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve이 어떻게 마침내 “무역 대체”를 무력화시켰는지 — 그리고 왜 7년 동안 우회책을 써야만 했는지"
          },
          {
            "level": 4,
            "id": null,
            "text": "아바타 및 이름 변경 대기 시간 (2024년 2월)"
          },
          {
            "level": 4,
            "id": null,
            "text": "7일 CS2 추세 반전 (2025년 7월)"
          },
          {
            "level": 4,
            "id": null,
            "text": "API에 대한 필수 모바일 푸시 알림 (2023년 12월)"
          },
          {
            "level": 4,
            "id": null,
            "text": "계정 개설 기간 및 이름 배너 (2022–2024)"
          },
          {
            "level": 2,
            "id": null,
            "text": "그들의 규칙서. 기록된 플랫폼들."
          },
          {
            "level": 3,
            "id": "enforcement-focus-title",
            "text": "단 하나의 규칙집. 불공평한 집행."
          },
          {
            "level": 4,
            "id": null,
            "text": "자동화"
          },
          {
            "level": 4,
            "id": null,
            "text": "상업적 이용"
          },
          {
            "level": 4,
            "id": null,
            "text": "VPN 및 위치 숨기기"
          },
          {
            "level": 4,
            "id": null,
            "text": "링크 난독화"
          },
          {
            "level": 4,
            "id": null,
            "text": "지원팀에서 사건을 종결할 때, 누가 그 결정을 검토하나요?"
          },
          {
            "level": 2,
            "id": null,
            "text": "자동화 API. 자동화를 금지하는 규칙."
          },
          {
            "level": 3,
            "id": null,
            "text": "“게임 개발자”에 대한 오해"
          },
          {
            "level": 4,
            "id": null,
            "text": "자동화의 모순"
          },
          {
            "level": 4,
            "id": null,
            "text": "무역 흐름에서 서버 측의 역할"
          },
          {
            "level": 2,
            "id": null,
            "text": "10일이 요구되었다. 10년 동안의 행적을 설명해야 했다."
          },
          {
            "level": 3,
            "id": "letter-company",
            "text": "밸브 코퍼레이션"
          },
          {
            "level": 3,
            "id": null,
            "text": "열 날.그럼 어떻게 되나요?"
          },
          {
            "level": 3,
            "id": null,
            "text": "선언된 리턴 호스트를 따르십시오."
          },
          {
            "level": 3,
            "id": "washington-record-heading",
            "text": "두 가지 기한. 명확히 정해지지 않은 집행 기준 하나."
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve은 도박 사이트에 10일의 기한을 부여한다"
          },
          {
            "level": 4,
            "id": null,
            "text": "워싱턴은 Valve을 압박한다"
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve은 혐의를 부인한다"
          },
          {
            "level": 4,
            "id": null,
            "text": "2026년 9월에 관측된 항로"
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve이 답변한 지 18개월이 지났음에도 불구하고, 규제 당국은 여전히 이를 ‘의도’로 규정했다."
          },
          {
            "level": 3,
            "id": null,
            "text": "‘10일 사전 통지 10년’: 23개 지정 대상지에 대한 법의학적 생존성 감사"
          },
          {
            "level": 4,
            "id": null,
            "text": "10일 전 경고에서 해외 대기업에 이르기까지: 수십억 달러 규모의 거래"
          },
          {
            "level": 2,
            "id": null,
            "text": "호스트명은 이미 요청에 포함되어 있습니다."
          },
          {
            "level": 3,
            "id": null,
            "text": "기록 및 보고된 선례"
          },
          {
            "level": 3,
            "id": null,
            "text": "등록일자로 알 수 있는 것과 알 수 없는 것"
          },
          {
            "level": 3,
            "id": null,
            "text": "비교 감사: API 준수 기준"
          },
          {
            "level": 2,
            "id": "market-thesis-heading",
            "text": "0을 제외한 가격 차이"
          },
          {
            "level": 2,
            "id": null,
            "text": "가격 차이는 수치로 측정할 수 있다."
          },
          {
            "level": 3,
            "id": null,
            "text": "이 금액이 시사하는 바"
          },
          {
            "level": 3,
            "id": null,
            "text": "많은 공연장에서는 Steam보다 더 높은 금액을 명시하고 있습니다."
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam은 여전히 제안 건수에서 선두를 달리고 있다."
          },
          {
            "level": 3,
            "id": null,
            "text": "상업 생태계는 누구의 눈에도 뻔히 드러나 있습니다."
          },
          {
            "level": 2,
            "id": null,
            "text": "누가 안전장치를 재설정할 수 있나요?"
          },
          {
            "level": 3,
            "id": null,
            "text": "계정의 보안 기능을 비활성화한 복구 티켓과, $10,000의 손실이 보고됨"
          },
          {
            "level": 3,
            "id": null,
            "text": "재고 그 이상."
          },
          {
            "level": 3,
            "id": "theft-ledger-title",
            "text": "Valve는 33개월 간격을 두고 두 번이나 문을 열었다. 문은 결코 닫히지 않았다."
          },
          {
            "level": 4,
            "id": null,
            "text": "장부에는 기록되어 있지만, 개별 사례 하나만으로는 알 수 없는 사실."
          },
          {
            "level": 3,
            "id": null,
            "text": "기밀 유지는 기술적 책임과 함께 이루어져야 합니다."
          },
          {
            "level": 2,
            "id": null,
            "text": "자금 흐름을 추적하라. 거래 내역을 분리하라."
          },
          {
            "level": 3,
            "id": null,
            "text": "돈이 실제로 오가는 곳."
          },
          {
            "level": 3,
            "id": null,
            "text": "먼저 활동을 분류한 다음, 의무를 분류하십시오."
          },
          {
            "level": 3,
            "id": null,
            "text": "자금 흐름, 정보 및 지원을 추적합니다."
          },
          {
            "level": 2,
            "id": null,
            "text": "디지털 서비스법: 지식을 공식 기록으로 남기다"
          },
          {
            "level": 3,
            "id": null,
            "text": "10일간의 요구."
          },
          {
            "level": 3,
            "id": null,
            "text": "DSA 시간 창."
          },
          {
            "level": 3,
            "id": null,
            "text": "기간에는 추적 기록이 필요합니다."
          },
          {
            "level": 3,
            "id": null,
            "text": "전 세계 연간 매출액 중"
          },
          {
            "level": 2,
            "id": null,
            "text": "미성년자: ‘Steam’ 로그인은 연령 확인이 아닙니다."
          },
          {
            "level": 3,
            "id": null,
            "text": "연산자와 데이터를 파악하십시오."
          },
          {
            "level": 3,
            "id": null,
            "text": "로그인부터 입금까지의 과정을 기록하십시오."
          },
          {
            "level": 2,
            "id": null,
            "text": "요청. 응답. 누락된 비교."
          },
          {
            "level": 3,
            "id": null,
            "text": "기록은 존재하지만, 정보 주체는 이를 받지 못했습니다."
          },
          {
            "level": 2,
            "id": null,
            "text": "플랫폼 자체 아키텍처에 위배되는 가입자 계약"
          },
          {
            "level": 3,
            "id": null,
            "text": "시장의 상한선과 상업적 이용 금지"
          },
          {
            "level": 3,
            "id": null,
            "text": "API 키 취약점은 사용자의 부주의가 아닌 플랫폼 설계상의 문제이다"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve은 로그인할 때마다 인증 호스트명을 수신합니다"
          },
          {
            "level": 3,
            "id": null,
            "text": "보관된 민원에서 나타나는 양상"
          },
          {
            "level": 3,
            "id": null,
            "text": "이 기록을 검토하는 법원은 SSA를 단독으로 해석하지 않을 것이다."
          },
          {
            "level": 2,
            "id": null,
            "text": "조사 결과. 우리가 요청한 기록들."
          },
          {
            "level": 2,
            "id": null,
            "text": "증거 메모 — 제1정보원이 제공한 자료"
          },
          {
            "level": 2,
            "id": null,
            "text": "제출된 PDF 파일의 편집은 표면적인 것에 불과하며, 가려진 텍스트는 여전히 추출할 수 있습니다."
          },
          {
            "level": 2,
            "id": null,
            "text": "지원 및 법률 서신 관련 증거자료"
          },
          {
            "level": 2,
            "id": null,
            "text": "선별된 1차 자료"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-01",
            "text": "2016년에 요청된 하드웨어 키"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-02",
            "text": "효과적인 수신 거부 기능이 없는 충돌 보고서"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-03",
            "text": "Valve에 인증 티켓 악용 사례가 신고되었습니다."
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-01",
            "text": "분쟁이 있는 44건의 마켓 매입 건"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-02",
            "text": "영구 제재 및 항소 불가"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-03",
            "text": "회복 초기화 및 보고된 $10,000 손실"
          },
          {
            "level": 2,
            "id": null,
            "text": "ArchiSteamFarm 및 자동화 조항"
          },
          {
            "level": 2,
            "id": null,
            "text": "Rules ledger: clauses against recorded platforms"
          },
          {
            "level": 3,
            "id": "ledger-title",
            "text": "상업적 이용 및 계정 과금"
          },
          {
            "level": 3,
            "id": "lw-register-title",
            "text": "플랫폼 등록부 175"
          },
          {
            "level": 4,
            "id": null,
            "text": "증명의 책임"
          },
          {
            "level": 4,
            "id": null,
            "text": "태그가 지정된 레코드란 무엇이며, 무엇이 아닌가"
          },
          {
            "level": 2,
            "id": null,
            "text": "DSAR 대응 지침서: 증거 제출 요청"
          },
          {
            "level": 3,
            "id": null,
            "text": "타임라인을 잘 보관하세요."
          },
          {
            "level": 3,
            "id": null,
            "text": "보관 중인 데이터를 요청하세요."
          },
          {
            "level": 3,
            "id": null,
            "text": "배송 내역을 보관해 두세요."
          },
          {
            "level": 3,
            "id": null,
            "text": "두 응답을 비교해 보세요."
          },
          {
            "level": 3,
            "id": null,
            "text": "계정 보안 및 접속 내역"
          },
          {
            "level": 3,
            "id": null,
            "text": "불일치는 조사해야 할 증거입니다."
          },
          {
            "level": 2,
            "id": null,
            "text": "지원 처리량. 공개된 응답 시간."
          },
          {
            "level": 3,
            "id": null,
            "text": "한 지원 데스크에 형성된 두 줄의 대기열을, 21개의 보관된 화면 캡처 이미지를 통해 확인할 수 있습니다."
          },
          {
            "level": 2,
            "id": null,
            "text": "레코드 수를 세어보세요. 범위를 확인해 보세요."
          },
          {
            "level": 2,
            "id": null,
            "text": "Valve은 집행 기록을 공개하지 않습니다.\n우리가 하나 만들었습니다."
          }
        ],
        "links": [
          "https://dotesports.com/counter-strike/news/csgo-lounge-billion-bets-3896",
          "https://store.steampowered.com/agreement/?l=english",
          "http://web.archive.org/web/20260921022032/https://store.steampowered.com/agreement/?l=english",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-all-results.json",
          "https://blog.counter-strike.net/expresstrade/",
          "http://web.archive.org/web/20260307161538/https://blog.counter-strike.net/expresstrade/",
          "https://wsgc.wa.gov/news/2016/washington-state-gambling-commission-orders-valve-stop-skins-gambling",
          "http://web.archive.org/web/20260520012601/https://wsgc.wa.gov/news/2016/washington-state-gambling-commission-orders-valve-stop-skins-gambling",
          "https://fr.scribd.com/document/328063293/Valve-s-Oct-18th-response-to-Washington-State-Gambling-Commission-s-cease-and-desist",
          "https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921021947/https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921022628/https://steamcommunity.com/linkfilter/?url=https:%2F%2Frollbit.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rbsnin.com.20260921T021120Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rollbit.com.json",
          "http://web.archive.org/web/20260921022740/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fskin.club",
          "http://web.archive.org/web/20260921022842/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fsc-auth.net",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skin.club.json",
          "http://web.archive.org/web/20260921022603/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fhowl.gg",
          "http://web.archive.org/web/20260921022636/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fhowl.uno",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/howl.gg.json",
          "http://web.archive.org/web/20260921022840/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fduelbits.com",
          "http://web.archive.org/web/20260921022901/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fswitchflips.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/duelbits.com.json",
          "http://web.archive.org/web/20260921022758/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgofast.com",
          "http://web.archive.org/web/20260921022847/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fauthtofast.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgofast.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/farmskins.com.20260921T025840Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/steam.kobal.cc.20260921T025844Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/farmskins.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cobaltlab.tech.20260921T041604Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cobaltauth.com.20260921T041608Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/cobaltlab.tech.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgo.net.20260921T041619Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cn2.easylot.net.20260921T041623Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgo.net.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/ggdrop.com.20260921T041637Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/ggauth.com.20260921T041641Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/ggdrop.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rustchance.com.20260921T041703Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/hgfuihd.com.20260921T041706Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rustchance.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skin.fans.20260921T041710Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.skinfans.com.20260921T041713Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skin.fans.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinport.com.20260921T041724Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinport.app.20260921T041728Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skinport.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skins.cash.20260921T041731Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinscash.live.20260921T041735Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skins.cash.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2hunt.com.20260921T041739Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rstspcl.com.20260921T041742Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tf2hunt.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgogem.com.20260922T192355Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/api.csgem.com.20260922T192358Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-2026-09-22.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/gamdom.com.20260922T192326Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/login.gambldom.com.20260922T192330Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/12cs.fail.20260922T192347Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/fail.games.20260922T192351Z.html",
          "http://web.archive.org/web/20260921022953/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgoempire.com",
          "http://web.archive.org/web/20260921022947/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgoempirelogin4.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgoempire.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cs.money.20260921T021131Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.dota.trade.20260921T021134Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/cs.money.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csfloat.com.20260921T041612Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgofloat.com.20260921T041615Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csfloat.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/g4skins.com.20260921T041630Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.g4s.to.20260921T041634Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/g4skins.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/juice.gg.20260921T041644Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/letmeinjuice.com.20260921T041648Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/juice.gg.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/market.csgo.com.20260921T041652Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2.net.20260921T041655Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/market.csgo.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rust.tm.20260921T041659Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rust.tm.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgolounge.com.20260922T192333Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2.net.20260922T192340Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2lounge.com.20260922T192337Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinbaron.de.20260921T041717Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinbaron.com.20260921T041721Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skinbaron.de.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2royal.com.20260921T041746Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2auth.com.20260921T041750Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tf2royal.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tradeit.gg.20260921T041753Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/connect-tradeit.com.20260921T041757Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tradeit.gg.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/upgrader.pro.20260921T041801Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/upgauth.space.20260921T041804Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/upgrader.pro.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-recheck-2026-09-21.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/domain-registration.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wayback-snapshots.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-2026-09-22c.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/master_registry.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/longitudinal-steam-phishing-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-steam-phishing-100.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-coverage-2026-09-22.json",
          "https://blog.csfloat.com/how-floatdb-tracks-items/",
          "http://web.archive.org/web/20260921022415/https://blog.csfloat.com/how-floatdb-tracks-items/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/platform-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/platforms-removed.json",
          "https://hackerone.com/reports/291750",
          "http://web.archive.org/web/20251116185046/https://hackerone.com/reports/291750",
          "https://hackerone.com/reports/1079561",
          "http://web.archive.org/web/20260924181830/https://hackerone.com/reports/1079561",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/hackerone-reports.json",
          "https://phishdestroy.io/steam_dossier/ko/steam_enforcement_evidence.html#support-records",
          "https://www.darknavy.org/blog/exploiting_steam_usual_and_unusual_ways_in_the_cef_framework/",
          "https://steamcommunity.com/groups/SteamClientBeta/discussions/0/3365901765276206401/",
          "http://web.archive.org/web/20250804051514/https://steamcommunity.com/groups/SteamClientBeta/discussions/0/3365901765276206401/",
          "https://www.chromium.org/developers/design-documents/safebrowsing/",
          "http://web.archive.org/web/20260821101616/https://www.chromium.org/developers/design-documents/safebrowsing/",
          "https://www.chromium.org/developers/how-tos/api-keys/",
          "http://web.archive.org/web/20260830122831/https://www.chromium.org/developers/how-tos/api-keys/",
          "https://github.com/Homebrew/homebrew-cask/issues/193814",
          "https://testsafebrowsing.appspot.com/",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/domain-registration.json",
          "https://phishdestroy.io/steam_dossier/ko/AUTH_AUDIT.md",
          "https://datatracker.ietf.org/doc/rfc6749/",
          "https://docs.cloud.google.com/docs/authentication/api-keys",
          "https://listings.pcisecuritystandards.org/pdfs/PCI_DSS_Resource_Guide_(003).pdf",
          "https://developer.apple.com/news/?id=02202019a",
          "http://web.archive.org/web/20250506070026/https://developer.apple.com/news/?id=02202019a",
          "https://dev.twitch.tv/docs/authentication/validate-tokens/",
          "https://discuss.dev.twitch.com/t/legacy-twitch-api-v5-i-e-kraken-shutdown-reminder-february-28-2022/36589",
          "http://web.archive.org/web/20250127085635/https://discuss.dev.twitch.com/t/legacy-twitch-api-v5-i-e-kraken-shutdown-reminder-february-28-2022/36589",
          "https://store.steampowered.com/news/posts/?enddate=1788390000",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/4123547285514022851",
          "https://skinvault.gg/blog/cs2-trade-protection-explained/",
          "https://csmarketcap.com/blog/market-insights/from-boom-to-bust-cs2s-trade-protection-impact",
          "https://skin.land/blog/steam-changes-cs2-trade-ban-logic-timing/",
          "https://help.steampowered.com/faqs/view/3041-A87A-E5F6-B6AC",
          "https://steamcommunity.com/ogg/593110/announcements/detail/533224478739530146",
          "https://steamcommunity.com/games/CSGO/announcements/detail/4447966961421256740",
          "https://steamcommunity.com/sharedfiles/filedetails/?id=2926756889",
          "https://steamcommunity.com/dev/apikey",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3734103130194459461",
          "https://steamcommunity.com/discussions/forum/1/3807266184852932971/",
          "https://help.steampowered.com/faqs/view/225C-C51E-B8F0-55B2",
          "https://store.steampowered.com/news/group/4/view/3314112260640237775",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/issues/325",
          "https://blog.dota2.com/2020/05/trading-cooldown/",
          "https://blog.counter-strike.net/index.php/2018/03/20308/",
          "http://web.archive.org/web/20250226114333/https://blog.counter-strike.net/index.php/2018/03/20308/",
          "https://phishdestroy.io/steam_dossier/ko/steam_evidence_archive.html",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/493839547938902179",
          "https://store.steampowered.com/online_conduct",
          "http://web.archive.org/web/20260921022120/https://store.steampowered.com/online_conduct",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260918014700/https://store.steampowered.com/subscriber_agreement/",
          "https://steamcommunity.com/dev/apiterms",
          "http://web.archive.org/web/20260921022210/https://steamcommunity.com/dev/apiterms",
          "https://help.steampowered.com/en/faqs/view/628C-E332-BD8C-4D36",
          "https://phishdestroy.io/steam_dossier/ko/social_graph.html",
          "https://phishdestroy.io/steam_dossier/ko/security_timeline.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wsgc-skins-gambling-briefing-2018.pdf",
          "https://wsgc.wa.gov/sites/default/files/2023-10/Skins%20Gambling.pdf",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wsgc-briefing-manifest.json",
          "https://x.com/csgobig",
          "https://www.facebook.com/csgobigofficial/",
          "https://500.casino/",
          "https://csgolounge.com/",
          "https://csgocasino.gg/",
          "https://x.com/CSGOatsecom",
          "https://x.com/CSGOSweep/status/937420902538543106",
          "https://x.com/Wild",
          "https://x.com/csgopot",
          "https://x.com/csgodiamondscom",
          "https://www.ftc.gov/legal-library/browse/cases-proceedings/162-3184-csgo-lotto-matter",
          "https://x.com/CSGODouble",
          "https://x.com/csgo_massive",
          "https://www.facebook.com/csgostrongfree/",
          "https://www.facebook.com/CSNCOM/",
          "https://www.gamblingcommission.gov.uk/report/young-people-and-gambling",
          "https://www.aph.gov.au/Parliamentary_Business/Committees/Senate/Environment_and_Communications/Gamingmicro-transactions",
          "https://phishdestroy.io/steam_dossier/ko/elite_skins.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/csfloat-catalogue.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/skinport-floor-over-cap.json",
          "https://pricempire.com/cs2-marketplaces",
          "http://web.archive.org/web/20260921022459/https://pricempire.com/cs2-marketplaces",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/priceempire-marketplaces.json",
          "https://www.steamanalyst.com/marketplace",
          "http://web.archive.org/web/20260719014552/https://www.steamanalyst.com/marketplace",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-atlas.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json",
          "https://phishdestroy.io/steam_dossier/ko/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/ko/steam_enforcement_evidence.html#case-support-recovery",
          "https://top10.owasp.org/2025/A01_2025-Broken_Access_Control/",
          "http://web.archive.org/web/20260920212535/https://top10.owasp.org/2025/A01_2025-Broken_Access_Control/",
          "https://store.steampowered.com/privacy_agreement/",
          "http://web.archive.org/web/20260921021648/https://store.steampowered.com/privacy_agreement/",
          "https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "http://web.archive.org/web/20250818113925/https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "https://www.dexerto.com/counter-strike-2/valve-saves-hacked-cs2-player-threatened-with-ransom-over-300000-of-rare-stickers-3283135/",
          "https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "http://web.archive.org/web/20220702042821/https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "https://www.kaspersky.com/blog/cs-go-two-million-usd-inventory-hack/44697/",
          "https://esportfire.com/article/the-2-million-usd-csgo-hack-22062022",
          "http://web.archive.org/web/20260515110250/https://esportfire.com/article/the-2-million-usd-csgo-hack-22062022",
          "https://esportsbetting.com/valve-deletes-130000-stolen-dragon-lore/",
          "https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "http://web.archive.org/web/20251115173120/https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "https://vkplay.ru/media/news/bloger-rasskazal-kak-podderzhka-steam-vorovala-akkaunty-igrokov/",
          "https://lis-skins.com/ru/blog/krupneisaia-mosenniceskaia-sxema-v-istorii-steam/",
          "https://escorenews.com/ru/csgo/news/44056-sotrudniki-podderjki-steam-zanimalis-krajey-skinov-s-akkauntov-za-god-oni-zarabotali-svyshe-300-tysyach-dollarov",
          "https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "http://web.archive.org/web/20250805141942/https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/outsourcing-archive-records.json",
          "https://community.skin.club/en/news/collector-has-steam-inventory-returned-after-bold-hack",
          "https://esportfire.com/article/300k-scam-full-katowice-2014-holo-collection-hacked",
          "http://web.archive.org/web/20251217072445/https://esportfire.com/article/300k-scam-full-katowice-2014-holo-collection-hacked",
          "https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng",
          "http://web.archive.org/web/20260920024236/https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng",
          "https://ag.ny.gov/press-release/2026/attorney-general-james-sues-game-developer-promoting-illegal-gambling-through",
          "http://web.archive.org/web/20260901015430/https://ag.ny.gov/press-release/2026/attorney-general-james-sues-game-developer-promoting-illegal-gambling-through",
          "https://www.fincen.gov/sites/default/files/2019-05/FinCEN%20CVC%20Guidance%20FINAL.pdf",
          "http://web.archive.org/web/20250711185007/https://www.fincen.gov/sites/default/files/2019-05/FinCEN%20CVC%20Guidance%20FINAL.pdf",
          "https://eur-lex.europa.eu/legal-content/EN/LSU/?uri=CELEX:32018L1673",
          "https://eur-lex.europa.eu/eli/dir/2024/1640/oj/eng",
          "http://web.archive.org/web/20260830153004/https://eur-lex.europa.eu/eli/dir/2024/1640/oj/eng",
          "https://eur-lex.europa.eu/eli/reg/2022/2065/oj/eng",
          "http://web.archive.org/web/20260920080125/https://eur-lex.europa.eu/eli/reg/2022/2065/oj/eng",
          "https://phishdestroy.io/steam_dossier/ko/legal_analysis.html",
          "https://partner.steamgames.com/doc/features/auth#website",
          "http://web.archive.org/web/20260921022335/https://partner.steamgames.com/doc/features/auth",
          "https://www.ftc.gov/legal-library/browse/rules/childrens-online-privacy-protection-rule-coppa",
          "http://web.archive.org/web/20260921070051/https://www.ftc.gov/legal-library/browse/rules/childrens-online-privacy-protection-rule-coppa",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/gdpr-ticket-1.png",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/screenshot-manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/gdpr-ticket-2.png",
          "https://datenschutz.hamburg.de/beschwerde",
          "https://edpb.europa.eu/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/regulatory-review/disclosure-audit.json",
          "https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "http://web.archive.org/web/20260821155801/https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "https://phishdestroy.io/steam_dossier/ko/index#exhibit-gallery-section",
          "https://github.com/ValveSoftware/steam-for-linux/issues/4521",
          "https://phishdestroy.io/steam_dossier/ko/steam_evidence_archive.html?source=GitHub&record=484",
          "https://github.com/ValveSoftware/steam-for-linux/issues/6459",
          "http://web.archive.org/web/20260419051343/https://github.com/ValveSoftware/steam-for-linux/issues/6459",
          "https://phishdestroy.io/steam_dossier/ko/steam_evidence_archive.html?source=GitHub&record=467",
          "https://github.com/ValveSoftware/Source-1-Games/issues/3857",
          "https://phishdestroy.io/steam_dossier/ko/steam_evidence_archive.html?source=GitHub&record=768",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "http://web.archive.org/web/20250320082450/https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://phishdestroy.io/steam_dossier/ko/steam_evidence_archive.html?source=Reddit&record=4533",
          "https://www.reddit.com/r/ohnePixel/comments/1hahqx2/permanently_banned_steam_account_without_a_clear/",
          "https://phishdestroy.io/steam_dossier/ko/steam_evidence_archive.html?source=Reddit&record=4766",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://phishdestroy.io/steam_dossier/ko/steam_evidence_archive.html?source=Reddit&record=4592",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/selected-evidence-records.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive_manifest.json",
          "https://phishdestroy.io/steam_dossier/ko/card_economy.html",
          "https://github.com/JustArchiNET/ArchiSteamFarm/wiki/FAQ",
          "https://phishdestroy.io/steam_dossier/ko/card_economy.html#scale",
          "https://phishdestroy.io/steam_dossier/ko/card_economy.html#licence",
          "https://phishdestroy.io/steam_dossier/ko/enforcement_audit.html",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "http://web.archive.org/web/20260924181709/https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://rdap.verisign.com/com/v1/domain/csgoempire.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoempire.com",
          "https://rdap.verisign.com/com/v1/domain/csgoempirelogin4.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/csgoempire.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustreaper.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustreaper.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/rustreaper.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustly.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustly.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/rustly.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgofast.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgofast.com",
          "https://rdap.verisign.com/com/v1/domain/authtofast.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/csgofast.com.json",
          "https://rdap.verisign.com/com/v1/domain/duelbits.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fduelbits.com",
          "https://rdap.verisign.com/com/v1/domain/switchflips.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/duelbits.com.json",
          "https://rdap.verisign.com/com/v1/domain/farmskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffarmskins.com",
          "https://tld-rdap.verisign.com/cc/v1/domain/kobal.cc",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/farmskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoluck.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoluck.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/csgoluck.com.json",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/domain-registry/insane.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Finsane.gg",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/insane.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs2skin.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs2skin.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/cs2skin.com.json",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/domain-registry/juice.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fjuice.gg",
          "https://rdap.verisign.com/com/v1/domain/letmeinjuice.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/juice.gg.json",
          "https://rdap.verisign.com/com/v1/domain/ggdrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fggdrop.com",
          "https://rdap.verisign.com/com/v1/domain/ggauth.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/ggdrop.com.json",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/domain-registry/howl.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhowl.gg",
          "https://rdap.radix.host/rdap/domain/howl.uno",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/howl.gg.json",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/domain-registry/chicken.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fchicken.gg",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/chicken.gg.json",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/domain-registry/csgocasino.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgocasino.gg",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/csgocasino.gg.json",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/domain-registry/hunt.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhunt.gg",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/hunt.gg.json",
          "https://rdap.verisign.com/com/v1/domain/csbattle.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsbattle.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/csbattle.com.json",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/domain-registry/skinrave.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinrave.gg",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/skinrave.gg.json",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/domain-registry/csdouble.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsdouble.gg",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/csdouble.gg.json",
          "https://rdap.verisign.com/com/v1/domain/rustchance.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustchance.com",
          "https://rdap.verisign.com/com/v1/domain/hgfuihd.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/rustchance.com.json",
          "https://rdap.radix.host/rdap/domain/cobaltlab.tech",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcobaltlab.tech",
          "https://rdap.verisign.com/com/v1/domain/cobaltauth.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/cobaltlab.tech.json",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/domain-registry/raided.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fraided.gg",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/raided.gg.json",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/domain-registry/rustneo.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustneo.gg",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/rustneo.gg.json",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/domain-registry/splits.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsplits.gg",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/splits.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/upgrader.pro",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fupgrader.pro",
          "https://rdap.radix.host/rdap/domain/upgauth.space",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/upgrader.pro.json",
          "https://rdap.centralnic.com/fans/domain/skin.fans",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.fans",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/skin.fans.json",
          "https://rdap.nic.one/domain/hotpizza.one",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhotpizza.one",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/hotpizza.one.json",
          "https://rdap.verisign.com/com/v1/domain/g4skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg4skins.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/g4skins.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2royal.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2royal.com",
          "https://rdap.verisign.com/com/v1/domain/tf2auth.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/tf2royal.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2hunt.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2hunt.com",
          "https://rdap.verisign.com/com/v1/domain/rstspcl.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/tf2hunt.com.json",
          "https://rdap.identitydigital.services/rdap/domain/tf2.bet",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2.bet",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/tf2.bet.json",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/domain-registry/openstars.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fopenstars.gg",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/openstars.gg.json",
          "https://rdap.verisign.com/com/v1/domain/skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/skins.com.json",
          "https://rdap.identitydigital.services/rdap/domain/white.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwhite.market",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/white.market.json",
          "https://rdap.identitydigital.services/rdap/domain/moon.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmoon.market",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/moon.market.json",
          "https://rdap.verisign.com/com/v1/domain/csfloat.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsfloat.com",
          "https://rdap.verisign.com/com/v1/domain/csgofloat.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/csfloat.com.json",
          "https://rdap.identitydigital.services/rdap/domain/skin.land",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.land",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/skin.land.json",
          "https://rdap.verisign.com/com/v1/domain/haloskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhaloskins.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/haloskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/163.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuff.163.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/buff.163.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmarket.csgo.com",
          "https://rdap.verisign.com/net/v1/domain/dota2.net",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/market.csgo.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinport.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinport.com",
          "https://pubapi.registry.google/rdap/domain/skinport.app",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/skinport.com.json",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/domain-registry/skinflow.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinflow.gg",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/skinflow.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/skin.place",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.place",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/skin.place.json",
          "https://rdap.verisign.com/com/v1/domain/skinsmonkey.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinsmonkey.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/skinsmonkey.com.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbaron.de",
          "https://rdap.verisign.com/com/v1/domain/skinbaron.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/skinbaron.de.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frust.tm",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/rust.tm.json",
          "https://rdap.verisign.com/com/v1/domain/pirateswap.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fpirateswap.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/pirateswap.com.json",
          "https://rdap.radix.host/rdap/domain/mannco.store",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmannco.store",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/mannco.store.json",
          "https://rdap.verisign.com/com/v1/domain/skinswap.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinswap.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/skinswap.com.json",
          "https://rdap.verisign.com/com/v1/domain/exeskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fexeskins.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/exeskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/balticskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbalticskins.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/balticskins.com.json",
          "https://rdap.nic.trade/domain/cs.trade",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.trade",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/cs.trade.json",
          "https://rdap.verisign.com/com/v1/domain/rapidskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frapidskins.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/rapidskins.com.json",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/domain-registry/tradeit.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftradeit.gg",
          "https://rdap.verisign.com/com/v1/domain/connect-tradeit.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/tradeit.gg.json",
          "https://rdap.verisign.com/com/v1/domain/49skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F49skins.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/49skins.com.json",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/domain-registry/skinvault.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinvault.gg",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/skinvault.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/aim.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Faim.market",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/aim.market.json",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/domain-registry/skinout.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinout.gg",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/skinout.gg.json",
          "https://rdap.verisign.com/com/v1/domain/ntskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fntskins.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/ntskins.com.json",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/domain-registry/gamerpay.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamerpay.gg",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/gamerpay.gg.json",
          "https://rdap.nic.tf/domain/scrap.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fscrap.tf",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/scrap.tf.json",
          "https://rdap.nic.tf/domain/marketplace.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmarketplace.tf",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/marketplace.tf.json",
          "https://rdap.identitydigital.services/rdap/domain/skins.cash",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.cash",
          "https://rdap.identitydigital.services/rdap/domain/skinscash.live",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/skins.cash.json",
          "https://rdap.verisign.com/net/v1/domain/csgo.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo.net",
          "https://rdap.verisign.com/net/v1/domain/easylot.net",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/csgo.net.json",
          "https://rdap.verisign.com/net/v1/domain/cybershoke.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcybershoke.net",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/cybershoke.net.json",
          "https://rdap.verisign.com/net/v1/domain/fastcup.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffastcup.net",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/fastcup.net.json",
          "https://rdap.verisign.com/com/v1/domain/leetify.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fleetify.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/leetify.com.json",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/domain-registry/scope.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fscope.gg",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/scope.gg.json",
          "https://rdap.verisign.com/com/v1/domain/tradeupspy.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftradeupspy.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/tradeupspy.com.json",
          "https://rdap.identitydigital.services/rdap/domain/cs.deals",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.deals",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/cs.deals.json",
          "https://rdap.verisign.com/com/v1/domain/pricempire.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fpricempire.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/pricempire.com.json",
          "https://rdap.identitydigital.services/rdap/domain/lzt.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flzt.market",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/lzt.market.json",
          "https://rdap.verisign.com/com/v1/domain/z2u.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fz2u.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/z2u.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoroll.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoroll.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/csgoroll.com.json",
          "https://rdap.verisign.com/com/v1/domain/rollbit.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frollbit.com",
          "https://rdap.verisign.com/com/v1/domain/rbsnin.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/rollbit.com.json",
          "https://rdap.identitydigital.services/rdap/domain/500.casino",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F500.casino",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/500.casino.json",
          "https://rdap.verisign.com/com/v1/domain/csgobig.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgobig.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/csgobig.com.json",
          "https://rdap.verisign.com/com/v1/domain/casedrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcasedrop.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/casedrop.com.json",
          "https://rdap.verisign.com/com/v1/domain/banditcamp.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbanditcamp.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/banditcamp.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinbox.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbox.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/skinbox.com.json",
          "https://rdap.verisign.com/com/v1/domain/tastydrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftastydrop.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/tastydrop.com.json",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/domain-registry/csgopolygon.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgopolygon.gg",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/csgopolygon.gg.json",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/domain-registry/magicdrop.ru.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmagicdrop.ru",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/magicdrop.ru.json",
          "https://rdap.verisign.com/com/v1/domain/csdice.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsdice.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/csdice.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinodds.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinodds.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/skinodds.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgowin.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgowin.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/csgowin.com.json",
          "https://rdap.verisign.com/net/v1/domain/csgorun.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgorun.net",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/csgorun.net.json",
          "https://rdap.verisign.com/com/v1/domain/openskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fopenskins.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/openskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustbet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustbet.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/rustbet.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgomagic.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgomagic.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/csgomagic.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgobounty.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgobounty.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/csgobounty.com.json",
          "https://rdap.verisign.com/com/v1/domain/ezskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fezskins.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/ezskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustcases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustcases.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/rustcases.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoreaper.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoreaper.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/csgoreaper.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgocases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgocases.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/csgocases.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo-skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo-skins.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/csgo-skins.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgonet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgonet.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/csgonet.com.json",
          "https://rdap.verisign.com/com/v1/domain/wtfskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwtfskins.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/wtfskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/flamecases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fflamecases.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/flamecases.com.json",
          "https://rdap.verisign.com/com/v1/domain/gamedom.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamedom.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/gamedom.com.json",
          "https://rdap.nic.club/domain/skin.club",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.club",
          "https://rdap.verisign.com/net/v1/domain/sc-auth.net",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/skin.club.json",
          "https://rdap.verisign.com/com/v1/domain/daddyskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdaddyskins.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/daddyskins.com.json",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/domain-registry/rustix.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustix.gg",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/rustix.gg.json",
          "https://rdap.nic.club/domain/skins.club",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.club",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/skins.club.json",
          "https://rdap.publicinterestregistry.org/rdap/domain/csgohouse.org",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgohouse.org",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/csgohouse.org.json",
          "https://rdap.verisign.com/net/v1/domain/skinrave.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinrave.net",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/skinrave.net.json",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/domain-registry/bloodycase.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbloodycase.gg",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/bloodycase.gg.json",
          "https://rdap.verisign.com/com/v1/domain/csgoclicker.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoclicker.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/csgoclicker.com.json",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/domain-registry/rustbet.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustbet.gg",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/rustbet.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs-drop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs-drop.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/cs-drop.com.json",
          "https://rdap.verisign.com/net/v1/domain/hellstore.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhellstore.net",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/hellstore.net.json",
          "https://rdap.verisign.com/com/v1/domain/rustloot.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustloot.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/rustloot.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo-case.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo-case.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/csgo-case.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgogem.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgogem.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/csgogem.com.json",
          "https://rdap.verisign.com/com/v1/domain/rainbet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frainbet.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/rainbet.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustclash.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustclash.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/rustclash.com.json",
          "https://rdap.identitydigital.services/rdap/domain/12cs.fail",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F12cs.fail",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/12cs.fail.json",
          "https://rdap.verisign.com/com/v1/domain/tf2easy.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwww.tf2easy.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/tf2easy.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2blaze.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2blaze.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/tf2blaze.com.json",
          "https://rdap.verisign.com/com/v1/domain/shuffle.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fshuffle.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/shuffle.com.json",
          "https://rdap.identitydigital.services/rdap/domain/buff.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuff.market",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/buff.market.json",
          "https://rdap.identitydigital.services/rdap/domain/avan.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Favan.market",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/avan.market.json",
          "https://rdap.identitydigital.services/rdap/domain/cs.money",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.money",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/cs.money.json",
          "https://rdap.verisign.com/com/v1/domain/uuskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fuuskins.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/uuskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/youpin898.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fyoupin898.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/youpin898.com.json",
          "https://rdap.verisign.com/com/v1/domain/c5game.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fc5game.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/c5game.com.json",
          "https://rdap.verisign.com/com/v1/domain/waxpeer.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwaxpeer.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/waxpeer.com.json",
          "https://rdap.verisign.com/com/v1/domain/dmarket.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdmarket.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/dmarket.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamcommunity.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamcommunity.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/steamcommunity.com.json",
          "https://rdap.verisign.com/com/v1/domain/lootfarm.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flootfarm.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/lootfarm.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustskins.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/rustskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/krakatoa.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fkrakatoa.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/krakatoa.com.json",
          "https://rdap.verisign.com/com/v1/domain/shadowpay.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fshadowpay.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/shadowpay.com.json",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/domain-registry/igxe.cn.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Figxe.cn",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/igxe.cn.json",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/domain-registry/swap.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fswap.gg",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/swap.gg.json",
          "https://rdap.verisign.com/com/v1/domain/bitskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbitskins.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/bitskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2mart.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2mart.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/tf2mart.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinbid.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbid.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/skinbid.com.json",
          "https://rdap.verisign.com/com/v1/domain/lootbear.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flootbear.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/lootbear.com.json",
          "https://rdap.nic.tf/domain/backpack.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbackpack.tf",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/backpack.tf.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fstntrading.eu",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/stntrading.eu.json",
          "https://rdap.verisign.com/com/v1/domain/skinwallet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinwallet.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/skinwallet.com.json",
          "https://rdap.verisign.com/com/v1/domain/dota2market.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdota2market.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/dota2market.com.json",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/domain-registry/xplay.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fxplay.gg",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/xplay.gg.json",
          "https://rdap.verisign.com/com/v1/domain/esportal.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fesportal.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/esportal.com.json",
          "https://rdap.registro.br/domain/gamersclub.com.br",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamersclub.com.br",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/gamersclub.com.br.json",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/domain-registry/epidemic.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fepidemic.gg",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/epidemic.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs2stash.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs2stash.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/cs2stash.com.json",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/domain-registry/csgoskins.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoskins.gg",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/csgoskins.gg.json",
          "https://rdap.verisign.com/com/v1/domain/steamanalyst.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamanalyst.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/steamanalyst.com.json",
          "https://rdap.verisign.com/net/v1/domain/steamcardexchange.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamcardexchange.net",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/steamcardexchange.net.json",
          "https://rdap.verisign.com/com/v1/domain/dotabuff.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdotabuff.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/dotabuff.com.json",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/domain-registry/tracker.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftracker.gg",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/tracker.gg.json",
          "https://rdap.verisign.com/com/v1/domain/funpay.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffunpay.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/funpay.com.json",
          "https://rdap.verisign.com/com/v1/domain/playerauctions.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fplayerauctions.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/playerauctions.com.json",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/domain-registry/eldorado.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Feldorado.gg",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/eldorado.gg.json",
          "https://rdap.verisign.com/com/v1/domain/g2a.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg2a.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/g2a.com.json",
          "https://rdap.verisign.com/net/v1/domain/kinguin.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fkinguin.net",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/kinguin.net.json",
          "https://rdap.verisign.com/com/v1/domain/g2g.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg2g.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/g2g.com.json",
          "https://rdap.verisign.com/com/v1/domain/playerup.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fplayerup.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/playerup.com.json",
          "https://rdap.verisign.com/net/v1/domain/smurfhub.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfhub.net",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/smurfhub.net.json",
          "https://rdap.verisign.com/com/v1/domain/smurfaccounts.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfaccounts.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/smurfaccounts.com.json",
          "https://rdap.verisign.com/com/v1/domain/buycsgorank.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuycsgorank.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/buycsgorank.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgosmurfkings.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgosmurfkings.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/csgosmurfkings.com.json",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/domain-registry/smurfstore.co.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfstore.co",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/smurfstore.co.json",
          "https://rdap.verisign.com/com/v1/domain/steamlvlup.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlvlup.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/steamlvlup.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamlevels.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlevels.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/steamlevels.com.json",
          "https://rdap.verisign.com/com/v1/domain/levelsteam.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flevelsteam.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/levelsteam.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamlevelu.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlevelu.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/steamlevelu.com.json",
          "https://rdap.verisign.com/com/v1/domain/eloking.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Feloking.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/eloking.com.json",
          "https://rdap.publicinterestregistry.org/rdap/domain/boosteria.org",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fboosteria.org",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/boosteria.org.json",
          "https://rdap.verisign.com/com/v1/domain/overgear.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fovergear.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/overgear.com.json",
          "https://rdap.verisign.com/com/v1/domain/blazingboost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fblazingboost.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/blazingboost.com.json",
          "https://rdap.verisign.com/com/v1/domain/dota2boost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdota2boost.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/dota2boost.com.json",
          "https://rdap.verisign.com/com/v1/domain/buyboost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuyboost.com",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit/buyboost.com.json",
          "https://phishdestroy.io/steam_dossier/ko/steam_tos_assets/auth-route-audit.json",
          "https://help.steampowered.com/en/faqs/view/365F-4BEE-2AE2-7BDD",
          "https://store.steampowered.com/privacy_agreement/#8",
          "https://www.edpb.europa.eu/system/files/2023-04/edpb_guidelines_202201_data_subject_rights_access_v2_en.pdf",
          "https://web.archive.org/web/20260810154631/https://store.steampowered.com/stats/support",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/design-review/part2/measurements.json",
          "https://phishdestroy.io/steam_dossier/ko/VALVE_EVIDENCE_PACK/databases/TOTAL_VALVE_SCANDALS_MASTER_DB.csv",
          "https://phishdestroy.io/steam_dossier/ko/license_disclaimer.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ko/index.content.json",
      "export_json_sha256": "aadd56cedccd300d8e26a2159dc1665445d5f16c88f6cb1a7ec6df48de766756"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ko/investigation_part2.html",
      "language": "ko",
      "title": "계정 접근 및 책임 — Steam 도시에르",
      "source_url": "https://phishdestroy.io/steam_dossier/ko/investigation_part2",
      "source_html_sha256": "ec45611b7dd32320638b7edea39f7e5e98a0e8c62f49641e9e9d044a8b0449cd",
      "exported_at": "2026-09-29T00:21:52.822Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "investigation_part2.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ko/investigation_part2.pdf?v=print-20260929-v5",
        "sha256": "0b80f84287d22745b5af2ebeba39c8cfa34b9b230f7d710605035e8c2f21203c",
        "bytes": 116383,
        "pages": 7
      },
      "integrity": {
        "signed_object": "investigation_part2.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "investigation_part2.content.json.asc",
        "digest_file": "investigation_part2.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify investigation_part2.content.json.asc investigation_part2.content.json",
          "sha256sum -c investigation_part2.content.json.sha256"
        ]
      },
      "content": {
        "text": "스팀 도시에르 / II\n\n귀하의 계정.그들의 접근 권한.누가 응답하나요?\n\n공공 부문의 자동화. 지원 업무의 외주화. 그 대가를 치러야 하는 것은 결국 시민들이다.\n\n관련 인프라, 보고된 손실 규모, 그리고 주장의 근거가 되는 문서들을 추적해 보십시오.\n\n인프라 추적하기 ↘\n증거물 01 / 라이브 섀도우 마켓 감시550,000+\n\nSteam FSB Market (익명 명칭이며 원래 이름은 여기에 공개하지 않습니다)에서 현재 판매 중인 계정\n바로 이 순간\n\n550,000+ 실시간 인벤토리 · 231,829 과거 수집 코퍼스 (198,320 스틸러 로그)\n\n해킹당한 Steam 계정을 주로 취급하는 지하 중개소, FSB Market (관련된 다른 이름은 공개하지 않습니다)는 Valve의 공식 Steam OpenID를 사용하여 구매자와 판매자 모두의 신원을 인증합니다 (openid.realm = https://FSB Market). 매 순간마다 50만 개가 넘는 도난당하거나 해킹당한 계정(RedLine/Lumma의 계정 탈취 로그, 피싱으로 확보된 계정, 크리덴셜 스터핑)이 몇 페니($0.50–$2.00)에 활발히 거래되고 있습니다. 어느 쪽도 FSB Market 또한 관련 포럼 Valve의 링크 필터에 의해 차단됩니다. 이곳은 Valve가 피해자를 돕지 않은 채 차단하는 63.06%개의 유료 봇 계정에 공급하는 대규모 계정의 원천입니다.\n\n실시간 인텔: 섀도우 마켓 모니터링 (55만 명 이상 실시간 접속) ↗ · 캡처 기록 열기 ↗ · 링크 필터 추적 열기 ↗55만 명 이상 실시간 시청\n\n01 / 작가들이 함께하는 생태계\n\n자동화는서류 기록.\n\n명명된 프로젝트. 공개된 기능. 도구를 해당 문서로 추적한 다음, 수집된 개발자 간 관계를 살펴보세요.\n\n252수집된 저장소\n3,320GITHUB 프로필\n4,214프로필–저장소 쌍\nValve 인프라지역 도서관재사용 가능한 애플리케이션\n선은 문서화된 통합 또는 종속 관계를 나타냅니다. 노드를 선택하면 해당 근거를 확인할 수 있습니다.\n\n다중 계정 자동화 / JustArchiNET\n\nArchiSteamFarm\n\n이 프로젝트는 Steam 계정 간 동시 카드 파밍을 명시적으로 홍보하고 있습니다. 프로젝트 파일에는 SteamKit2 의존성이 명시되어 있습니다.\n\n프로젝트의 공식 문서를 읽어보세요 ↗\n\nSteamKit → ArchiSteamFarm\n선언된 종속성 ↗\n\n모아본 관계들\n\n40 기여자 라벨 · 40 포커 라벨\n\n아래는 기여자 예시입니다. 이 라벨들은 고용 관계나 승인 여부를 나타내는 것이 아니라, 리포지토리 간의 관계를 설명합니다.\n\n@JustArchi@renovate[봇]@JustArchi-ArchiBot@dependabot-preview[bot]@renovate-bot@actions-user@dependabot-support@Abrynos\n개발자 그래프가 보여주는 것\n\n이 그래프는 명명된 프로젝트와 GitHub 프로필 간의 공개된 기여자 및 포크 관계를 시각화한 것입니다. 이는 저장소 포크, 기여 내역, 프로필 연결 정보와 같은 공개 기록입니다. 핵심은 이 조사가 무엇을 새롭게 밝혀냈는지가 아니라, 공개된 역량과 개발자 관계에 대한 이러한 기록적 증거가 Valve에게 어떤 해답을 요구하는가 하는 점입니다. 소스 해시는 지도 출처.\n\n전체 네트워크 둘러보기 ↗저장소 원본 데이터 ↓\n\n02 / 각기 다른 자격. 각기 다른 능력.\n\n어떤 키인가요?무엇에 대해 이야기하고 있는 건가요?\n\n게임을 플레이하는 데 있어 플레이어가 개인 웹 API 키를 발급받을 필요는 없습니다. 이것이 바로 이번 조사의 핵심이 되는 차이점입니다.\n\n01 / 사용자 계정\n개인용 웹 API 키\nsteamcommunity.com/dev/apikey\n\n허용된 API 호출을 위해 사용자 계정에서 발급됩니다. 키 생성, 접근 권한, 취소 및 악용 탐지는 계정 보안과 관련된 사항입니다.\n\n02 / 게임 백엔드\n퍼블리셔 웹 API 키\n\nSteamworks 파트너사는 게임 관련 서비스를 포함한 지원되는 백엔드 운영에 퍼블리셔 인증 정보를 사용합니다. 플레이어의 개인 키는 이와 별개의 인증 정보입니다.\n\n03 / 신원 및 세션\nOpenID / 세션 토큰\n\nOpenID는 웹사이트에 신원을 확인하는 역할을 합니다. Steam 세션 토큰이나 리프레시 토큰은 이와 다른 용도로 사용됩니다. 이러한 메커니즘을 서로 바꿔 쓸 수 있는 하나의 “API 키”로 설명해서는 안 됩니다.\n\nValve에는 사용자와 게시자의 웹 API 키가 모두 기록됩니다. 따라서 웹 API 전체가 Steamworks와 분리되어 있지 않습니다. API 키 설명서 ↗ 보관됨 2026-09-15 ↗ · 게임 세션 인증 ↗ 보관됨 2026-08-29 ↗\n\n이 도구의 작성자가 작성함 / 2024년 3월\n\n자동화에는 API 키 외에도 다른 방법을 사용할 수 있습니다.\n\nTrade Offer Manager 위키에는 별도의 API 키가 없는 경우 웹 API의 일부 기능에 세션 액세스 토큰을 사용하는 방법이 설명되어 있습니다. 또한 2023년 말부터 키 생성 시 모바일 확인 절차가 도입된 점도 기록되어 있습니다. 유지보수 담당자는 이러한 방식의 토큰 사용이 Valve에서 지원되지 않는다고 밝혔으나, 이는 오래된 문서상의 설명일 뿐 실제 우회 테스트 결과는 아닙니다.\n\n관리자의 설명을 확인해 보세요 ↗ 보관됨 2026-09-24 ↗\n\n‘인간적인 측면’ / 피싱 공격의 과정을 보여주는 사례\n\n아직도 하고 있어요.이미 드러났다.\n\n친구가 보낸 메시지. 투표 요청. “감사합니다” 페이지. 플레이어 입장에서는 이 작업이 끝난 것입니다. 하지만 해킹당한 세션은 그 순간이 지나도 계속될 수 있습니다.\n\n플레이어 화면에서\n\nF\n한 친구의 증언\n\n“우리 팀에 투표해 주실 수 있나요?”\n\nSteam 채팅을 통해 익숙한 계정으로부터 요청이 도착합니다. 이 경우, 링크된 페이지가 클라이언트의 브라우저에서 열립니다.\n\nOUT OF SIGHT\n\n웹사이트보다 신뢰가 먼저입니다.\n\n해킹당한 친구의 계정은 피싱 링크에 신뢰성을 더해줄 수 있습니다. 주변의 Steam 인터페이스는 해당 웹사이트의 진위 여부를 보증하지 않습니다.\n\n알려진 발신자 / 외부 수신처\n어떤 상품이든 판매되기 전에 가장 먼저 고려해야 할 사항은 계정 보안입니다.\n\n해당 플레이어는 자동화 인증 정보를 생성하거나 제어 권한을 위임할 의도가 없었습니다. 게임에 다시 접속했다고 해서 계정이 안전하다는 증거는 아닙니다. Valve은 세션 로그, API 키 생성 기록, 기기 상관 관계 데이터를 보유하고 있지만, 피해자는 그렇지 않습니다. 이러한 비대칭성이 바로 책임 소재의 문제입니다.\n\n세션 액세스 및 인증 정보 유형\n\nAPI 키와 로그인 세션은 각각 다른 기능을 가진 별개의 인증 정보입니다. 키를 취소한다고 해서 활성 세션이 종료되는 것은 아닙니다. Valve의 공식 문서에 이 두 가지가 모두 설명되어 있으며, Valve은 분쟁이 발생한 조치 당시 어떤 인증 정보가 활성화되어 있었는지를 확인할 수 있는 로그를 보관하고 있습니다. 요구되는 것은 바로 그 기록의 공개이지, 수사가 임의로 추론해 낸 내용이 아닙니다. 토큰 처리에 관한 유지보수자 문서 ↗ 보관됨 2026-09-24 ↗ · Valve 주요 문서 ↗ 보관됨 2026-09-15 ↗\n\n03 / 공식 시장에는 상한선이 있다\n\n해당 아이템은 희귀할 수 있습니다.한도는 그대로 유지됩니다.\n\n상한가를 초과하는 가격은 해당 가격으로 커뮤니티 마켓에 한 번의 매물을 등록하는 것만으로는 실현될 수 없습니다.\n\n참고용 매도 희망 가격$5,000상품의 판매 가격 변경하기\n$100$20,000\n\n이는 공개된 한도를 보여주는 예시일 뿐, 평가나 거래 권고가 아닙니다.\n\n상장 한도≈ $1,800\n지갑 모자≈ $2,000\n\n공시된 상한선을 초과함.\n\n지갑에 있는 자금은 은행 계좌로 인출할 수 없습니다. 이러한 제약으로 인해 제3자 스킨 시장에서 충족해야 할 수요가 발생하는데, 이는 상장 및 지갑 한도 규정에 의해 생성되는 수요인 반면, Valve의 자체 규정상 상업적 운영자는 이를 충족할 수 없습니다.\n\nSteam의 시장 한도 ↗ 보관됨 2026-09-21 ↗\n\n04 / 지원 범위의 내부\n\n데이터를 맡겨주셨습니다.접근 권한에 대한 책임을 진다.\n\nValve의 개인정보 처리방침에는 지원 제공에 필요한 경우 제3자 지원 제공업체와 개인정보를 공유할 수 있다고 명시되어 있습니다.\n\n플레이어계정 및 증빙 자료\n→\n밸브회복 과정\n→\n지원 제공자위임된 접근 권한\n\n개인정보 처리방침 §5.2 ↗ · Valve의 자체 정책에 따라 제3자의 지원 접근이 허용되어 있습니다. 아직 명확히 밝혀지지 않은 점은 다음과 같습니다. 어떤 권한이 부여되었는지, 어떤 감사 기록이 존재하는지, 그리고 접근 권한이 남용되었다고 주장되는 상황에서 어떤 일이 발생했는지입니다.\n\n2015년\n그 저울은 공개되어 있었다\n\nValve은 계정 도용 사례가 광범위하게 발생했음을 인정하고, 이에 대한 방지 조치를 설명했다.\n\nValve 간행물 ↗보관됨 2026-08-09 ↗\n2015년\nValve는 해당 업무를 외주화했으며, 그 사실을 밝혔습니다\n\nValve은 소규모의 사내 Steam 지원 리더십 팀을 운영하고 있으며, 이를 다음과 같이 밝혔습니다. \"몇 군데 업체를 고용했다\" 지원 업무를 처리하기 위해 (Erik Johnson, Valve, Kotaku에); 해당 개인정보 처리방침 제5.2조는 해당 제3자가 사용자 데이터에 접근할 수 있도록 허용하고 있습니다. 어떤 계약업체가 계정 복구 권한을 보유하고 있는지, Valve는 한 번도 공개한 적이 없다 — 커뮤니티 토론에서는 Concentrix와 같은 업체들이 거론되고 있지만, 아직 Valve-확인된 곳은 없다. 이 아웃소싱 데스크는 아래에 언급된 두 가지 사실 중 어느 것보다도 수년 전에 이미 운영되고 있었다.\n\nKotaku: Valve 지원 현황 ↗보관됨 2025-07-11 ↗\n2023\n첫 입원\n\nValve의 CS:GO 팀은 자체 지원 요청 절차를 통해 계정이 해킹당한 사건에 대해 서면으로 책임을 인정하고, 거래 내역을 원상복구했습니다.\n\n아웃소싱 사례 열기 ↓\n2025년\n두 번째 입학\n\n33개월 후, Steam 고객지원팀은 기술자가 “당사의 절차를 따르지 않아 귀하의 계정이 다른 사람에게 복구되는 결과가 발생했다”고 적었습니다. 같은 채널. 같은 결과.\n\nDexerto, 2025년 11월 14일 ↗\n\n사건 파일 / HFB와 아웃소싱 의혹\n\n그곳으로 들어가는 길은 Steam 지원 그 자체였다.Valve는 서면으로 그렇게 밝혔다.\n\nDexerto가 인용한 지원 답변에 따르면, Valve의 CS:GO 팀은 계정 해킹 사건에 대한 책임을 인정했다. 도움 요청 절차를 통해 — 피싱 페이지도 아니고 사용자도 아닌, 자체 채널을 통해 발생한 일입니다. 해당 상품들은 회수되었고 거래는 취소되었는데, 이는 Valve가 다른 피해자들에게 존재하지 않는다고 말하는 구제책입니다. HFB의 재고량은 다음과 같이 보고되었습니다. $2,000,000+ 그날 그리고 $3,000,000+ 후속 조치에서; Qkss도 똑같은 방식으로 $1,000,000+를 잃고 아무것도 얻지 못했다.\n\n지원 답변 / DEXERTO 제공 · 2023년 2월 21일\n“지원 문의 요청을 통해 보안이 침해되었으며, 이에 대해 CS:GO 팀이 책임을 집니다”\n관련 보도 내용과 재게시된 메시지를 읽어보세요 ↗ 보관됨 2025-08-18 ↗\n01 / 어떤 밸브가 열렸는가\n자체 지원 채널이 진입 경로였습니다\n\n이 답변은 해킹당한 계정과 해당 거래의 취소 내역을 다룹니다. Valve이 거래를 취소했으므로, 해당 거래는 취소 가능한 것이었습니다. 원래의 인증된 티켓은 이 모음집에 포함되어 있지 않습니다.\n\n02 / 해고로 해결되지 않은 문제들\n2025년 11월, 그 문이 다시 열렸다.\n\n해당 계약업체는 Steam명의 지원 직원 전원을 해고했다. 이는 Dexerto를 통해 Mzkshow가 보도한 내용이며, Valve의 인사 발표가 아니다. 33개월 후, Steam Support는 다른 채권 추심업체에 보낸 서신에서 “지원 요청을 처리한 지원 기술자가 당사의 절차를 따르지 않아 귀하의 계정이 다른 사람에게 복구되는 결과가 발생했다”고 밝혔다. Valve이 동일한 채널에 대해 직접 언급한 문구이다.\n\n두 번째 입학, 2025년 11월 14일 ↗\n03 / ‘OPEN’이란 무엇인가\nValve은 그 계약업체의 이름을 한 번도 밝힌 적이 없다\n\n이 자료들만으로는 계약업체나 위치가 확인되지 않습니다. 이는 보도의 허점이 아니라, Valve이 사용자 계정에 대한 접근 권한을 누가 가지고 있었는지에 대해 밝히지 않은 사실입니다.\n\n이 사건에 대한 당대의 기록 ↗\n\nValve이 아직 답하지 않은 세 가지 질문은 다음과 같습니다. 누가 계정 복구 절차를 무효화할 수 있었는지, 접근 감사 결과에서 무엇이 밝혀졌는지, 그리고 그 후 어떤 변화가 있었는지입니다.\n\n보존된 지원 아카이브에 수록된 후속 주장들\n\n2024년에 게시된 두 건의 레딧 게시물에는 Mzkshow에 대한 추가 조사 내용이 담겨 있습니다. 2024년 7월의 VAC 차단 해제 사례와 2024년 12월의 $13,000 재고 사례입니다. 이 두 건은 별도로 보고된 사건입니다. 각 사건에서 제기되는 책임 소재에 대한 질문은 동일합니다. 즉, 누가 권한 우회 접근 권한을 가졌는지, 감사 결과 무엇이 밝혀졌는지, 그리고 무엇이 변경되었는지입니다.\n\n2024년 7월 14일 · 회복 보고 / VAC-차단 사례 ↗2024년 12월 2일 · 신고된 $13,000 재고 사례 ↗보관됨 2025-08-05 ↗보존된 두 개의 게시물, 소스 행 및 해시 ↓\n\n05 / 상실을 따라가다\n\n모든 금액케이스가 필요합니다.\n\n2022년 6월부터 2026년 3월까지 총 10건. 모든 금액은 해당 출처가 발표한 수치입니다 — $6,300,000, $2,000,000+, $1,000,000+, ≈$320,000, ≈$300,000, 그리고 288유로까지 떨어졌습니다. Valve는 각 거래에 대한 거래 로그, 세션 기록 및 지원 감사 추적을 보관하고 있으나, 이 중 어느 것도 제공하지 않았습니다.\n\n지원 채널21 6월 2022\n$2,000,000+\nHFB — the largest inventory in the game\n\n보고된 재고 평가액 · 2월 2023 후속 보도에서 $3M+로 상향 조정\n\n7개의 ‘Souvenir Dragon Lores’와 #1 블루 젬 카람빗. 그 칼 하나만 해도 약 $1.26m 상당입니다. 3년 동안 휴면 상태였으며, 인증 기능은 여전히 활성화된 상태입니다. 이메일과 비밀번호는 고객 지원 복구 절차를 통해 변경되었습니다. Valve는 거래를 취소했으며, 이에 대한 책임을 서면으로 명시했습니다. 취소 조치 이전에, 현금 및 암호화폐로 결제되는 market.csgo.com을 통해 $200,000+ 상당의 수익금이 이미 인출된 것으로 보고되었습니다. 거래 취소 시에는 이미 인출된 금액이 아닌 스킨만 반환됩니다. 이 롤백 과정에서 또 다른 문제가 발생했습니다. 한 구매자가 자신의 ‘Souvenir Dragon Lore’를 게임 내 보관함에 숨겨두었는데, 스크립트가 해당 컨테이너 내부를 확인할 수 없었기 때문입니다. 또한 Valve는 도난 사건을 되돌리는 과정에서 $130,000 상당의 아이템을 중복 생성했습니다. 이는 아이템 ID와 커뮤니티 제보를 통해 적발되었으며, 7월에 삭제되었습니다. 2022, 구매자에게는 Valve 대신 BUFF를 통해 환불이 이루어졌습니다.\n\nDexerto, 절도 사건 당일 ↗\n지갑 및 구매 내역07 7월 2022\n>$500\n44 disputed Market purchases\n\n보고된 지갑 지출 · USD\n\n한 사용자가 소액 Dota 2 아이템의 무단 구매와 불만족스러운 고객 지원 대응에 대해 신고했습니다.\n\n고소장 및 관련 스크린샷을 읽어보세요 ↗\n플랫폼 침입14 8월 2022\n$6,300,000\nCS.Money — 19,000+ 봇에서 얻은 스킨\n\n가격 평가 · 1차 추정액 $1.6M\n\n공격자들은 해당 마켓플레이스의 거래 봇에 저장된 모바일 인증기 파일을 탈취해 내용을 모두 비운 뒤, 흔적을 감추기 위해 탈취한 자산의 일부를 유명 트레이더들에게 분배했습니다. 커뮤니티 연구원들은 몇 시간 만에 55 내의 공격자 계정들을 파악해냈다. Valve는 어떠한 조치도 취하지 않았으며, 제3자 사이트가 Steam 외부에 위치해 있다고, 재고, 거래 API 및 계정 시스템 전반에 걸쳐 도난이 이루어진 Steam 측이 밝혔다.\n\n당시의 기록을 읽어보세요 ↗\n지원 채널보도된 내용 21 2월 2023\n$1,000,000+\nQkss — 같은 문, 같은 배우, 정반대의 대답\n\n보고된 재고 평가액\n\nHFB 사건이 처리된 방식과 똑같이, 같은 배우가 동일한 지원 요청 절차를 통해 처리된 사례입니다. HFB 사건은 8개월 전에 완전히 해결되었지만, Qkss 사건은 그렇지 않았습니다. 공개된 기록상 두 사건을 구분할 만한 요소는 관객 규모 외에는 아무것도 없습니다.\n\nMzkshow 조사에 관한 Dexerto의 보도 ↗\n지원 채널2월 2023 보도됨\n≈ $320,000\n내부자 거래 그 자체 — 1년 동안의 거래\n\n약 1년 간의 실적 · 재고 평가가 아님\n\n지원팀 측에서 최대 15년 전까지의 계정 내역을 확인했습니다. 첫 번째 CD 키, 첫 번째 이메일, 첫 번째 카드 등 — 바로 계정 복구 절차에서 요구하는 증거들이었습니다. 데이터베이스를 보유한 쪽은 계정 소유자와의 논쟁에서 항상 승리합니다. iBUYPOWER와 Titan Katowice 2014 홀로그램이 적용된 도난당한 M4A4 Howl 한 정이 $35,000에 판매되었고, 이를 알 리가 없었던 NAVI의 b1t에게 넘어갔습니다. 계약업체의 대응은 Steam 지원팀에서 근무하던 모든 직원을 해고하는 것이었습니다.\n\n같은 수사에 관한 Escorenews 기사 ↗\n지갑 및 구매 내역09 12월 2023\n€288\n2단계 보안 조치에도 불구하고 지갑 분실\n\nTRUSTPILOT · 출처 색인 16\n\n리뷰어는 계정이 해킹당했으며 마켓 지출에 대한 도움을 거부당했다고 보고했습니다. 해당 내보내기 파일에는 개별 리뷰 URL이 포함되어 있지 않습니다.\n\n소스 출처 확인 ↗\n계정 복구02 12월 2024\n$13,000\n“마트베이” — 해고 사건 2년 후\n\n저자의 재고 추정치\n\n계정 소유자 본인조차 일치시킬 수 없었던 계정 정보를 제공한 사람에게 계정 복구 권한이 부여되었다. 계약업체가 Steam 지원 데스크를 정리한 후에도, 같은 절차를 밟았지만 결과는 마찬가지였다.\n\n보존된 주장을 읽어보세요 ↗\n계정 복구09 5월 2025\n≈ $10,000\n타인의 티켓을 통한 복구\n\n분실 신고 품목 · USD\n\n퀘벡의 한 사용자는 고객 지원팀이 다른 사람의 요청에 따라 비밀번호를 재설정하고 계정 보호 기능을 해제했다고 주장하고 있다.\n\n1인칭으로 작성된 불만 사항을 읽어보세요 ↗\n지원 채널13 11월 2025\n≈ $300,000\nHawkeye337 — 그리고 Valve의 두 번째 서면 자백\n\n카토비체 2014 홀로그램 컬렉션 전체\n\n해커는 1 비트코인을 요구하며, 해당 자산을 네게브(Negevs)로 옮겨 파괴하기 시작했습니다. Steam 지원팀의 답변: “지원 요청을 처리한 기술자가 당사의 절차를 따르지 않아 귀하의 계정이 다른 사람에게 복구되었습니다.” 첫 번째 시도가 있은 지 33개월 후, 똑같은 수법이 반복되었습니다. X에서 해당 게시물이 화제가 된 지 몇 시간 만에 계정이 복구되었습니다. Qkss에는 그런 규모의 독자층이 없었습니다.\n\nDexerto, 14 Nov 2025 ↗\n지갑 및 구매 내역29 3월 2026\n$50\n무단 충전 및 선물 받은 게임\n\nTRUSTPILOT · 출처 색인 290\n\n리뷰 작성자는 무단 지출과 환불 요청이 받아들여지지 않았다고 주장하고 있습니다. 내보낸 파일에서 해당 개별 리뷰의 URL이 누락되었습니다.\n\n소스 출처 확인 ↗\n\n출처별 보고 내용에 따른 출처 표기와 금액은 그대로 유지됩니다. Valve은 이러한 모든 사례에 대한 거래 로그, 세션 기록 및 지원 감사 추적을 보유하고 있습니다. 해당 자료를 제출하십시오. 보존된 레딧 게시물만으로는 이 문제를 해결할 수 없으며, Valve의 자체 기록만이 이를 해결할 수 있습니다.\n\n컬렉션 / 확인 후\n\n231,829개의 계정이 판매 중입니다.Valve에는 모든 항목에 대한 로그가 저장되어 있습니다.\n354 → 201\n트러스트파일럿 기록\n\n중복 행 153개가 제거되었습니다. 내보내기 과정에서 개별 검토 URL은 보존되지 않았습니다.\n\n231,829\nSteam 계정 목록\n\n33,509 자동 등록된 상품으로 분류됨; 198,320 수집가의 ‘도난품’ 라벨이 부착된 상품. 목록에 올라온 상품이 반드시 판매가 완료된 것은 아닙니다.\n\n수집물 감사 ↓소스 아카이브 검색 ↗",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "귀하의 계정.그들의 접근 권한.누가 응답하나요?"
          },
          {
            "level": 2,
            "id": null,
            "text": "자동화는서류 기록."
          },
          {
            "level": 3,
            "id": null,
            "text": "ArchiSteamFarm"
          },
          {
            "level": 2,
            "id": null,
            "text": "어떤 키인가요?무엇에 대해 이야기하고 있는 건가요?"
          },
          {
            "level": 3,
            "id": null,
            "text": "개인용 웹 API 키"
          },
          {
            "level": 3,
            "id": null,
            "text": "퍼블리셔 웹 API 키"
          },
          {
            "level": 3,
            "id": null,
            "text": "OpenID / 세션 토큰"
          },
          {
            "level": 3,
            "id": null,
            "text": "자동화에는 API 키 외에도 다른 방법을 사용할 수 있습니다."
          },
          {
            "level": 2,
            "id": null,
            "text": "아직도 하고 있어요.이미 드러났다."
          },
          {
            "level": 3,
            "id": "session-hidden-title",
            "text": "웹사이트보다 신뢰가 먼저입니다."
          },
          {
            "level": 2,
            "id": null,
            "text": "해당 아이템은 희귀할 수 있습니다.한도는 그대로 유지됩니다."
          },
          {
            "level": 2,
            "id": null,
            "text": "데이터를 맡겨주셨습니다.접근 권한에 대한 책임을 진다."
          },
          {
            "level": 3,
            "id": null,
            "text": "그 저울은 공개되어 있었다"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve는 해당 업무를 외주화했으며, 그 사실을 밝혔습니다"
          },
          {
            "level": 3,
            "id": null,
            "text": "첫 입원"
          },
          {
            "level": 3,
            "id": null,
            "text": "두 번째 입학"
          },
          {
            "level": 3,
            "id": null,
            "text": "그곳으로 들어가는 길은 Steam 지원 그 자체였다.Valve는 서면으로 그렇게 밝혔다."
          },
          {
            "level": 4,
            "id": null,
            "text": "자체 지원 채널이 진입 경로였습니다"
          },
          {
            "level": 4,
            "id": null,
            "text": "2025년 11월, 그 문이 다시 열렸다."
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve은 그 계약업체의 이름을 한 번도 밝힌 적이 없다"
          },
          {
            "level": 2,
            "id": null,
            "text": "모든 금액케이스가 필요합니다."
          },
          {
            "level": 3,
            "id": null,
            "text": "HFB — the largest inventory in the game"
          },
          {
            "level": 3,
            "id": null,
            "text": "44 disputed Market purchases"
          },
          {
            "level": 3,
            "id": null,
            "text": "CS.Money — 19,000+ 봇에서 얻은 스킨"
          },
          {
            "level": 3,
            "id": null,
            "text": "Qkss — 같은 문, 같은 배우, 정반대의 대답"
          },
          {
            "level": 3,
            "id": null,
            "text": "내부자 거래 그 자체 — 1년 동안의 거래"
          },
          {
            "level": 3,
            "id": null,
            "text": "2단계 보안 조치에도 불구하고 지갑 분실"
          },
          {
            "level": 3,
            "id": null,
            "text": "“마트베이” — 해고 사건 2년 후"
          },
          {
            "level": 3,
            "id": null,
            "text": "타인의 티켓을 통한 복구"
          },
          {
            "level": 3,
            "id": null,
            "text": "Hawkeye337 — 그리고 Valve의 두 번째 서면 자백"
          },
          {
            "level": 3,
            "id": null,
            "text": "무단 충전 및 선물 받은 게임"
          },
          {
            "level": 2,
            "id": null,
            "text": "231,829개의 계정이 판매 중입니다.Valve에는 모든 항목에 대한 로그가 저장되어 있습니다."
          },
          {
            "level": 3,
            "id": null,
            "text": "트러스트파일럿 기록"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam 계정 목록"
          }
        ],
        "links": [
          "https://phishdestroy.io/live-intel/?category=steam",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/lzt.market.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-evidence-lzt.json",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://github.com/JustArchiNET/ArchiSteamFarm/blob/main/ArchiSteamFarm/ArchiSteamFarm.csproj",
          "https://github.com/JustArchi",
          "https://github.com/renovate[bot]",
          "https://github.com/JustArchi-ArchiBot",
          "https://github.com/dependabot-preview[bot]",
          "https://github.com/renovate-bot",
          "https://github.com/actions-user",
          "https://github.com/dependabot-support",
          "https://github.com/Abrynos",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/automation-map.json",
          "https://phishdestroy.io/steam_dossier/ko/output_steam_network/network.html",
          "https://phishdestroy.io/steam_dossier/ko/output_steam_network/raw_data.json",
          "https://partner.steamgames.com/doc/webapi_overview/auth",
          "http://web.archive.org/web/20260915025812/https://partner.steamgames.com/doc/webapi_overview/auth",
          "https://partner.steamgames.com/doc/webapi/ISteamUserAuth",
          "http://web.archive.org/web/20260829124950/https://partner.steamgames.com/doc/webapi/ISteamUserAuth",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "http://web.archive.org/web/20260924181824/https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://store.steampowered.com/privacy_agreement/",
          "https://store.steampowered.com/oldnews/19618",
          "http://web.archive.org/web/20260809125516/https://store.steampowered.com/oldnews/19618",
          "https://kotaku.com/valve-explains-why-steam-customer-service-is-still-terr-1736988223",
          "http://web.archive.org/web/20250711004653/https://kotaku.com/valve-explains-why-steam-customer-service-is-still-terr-1736988223",
          "https://www.dexerto.com/counter-strike-2/valve-saves-hacked-cs2-player-threatened-with-ransom-over-300000-of-rare-stickers-3283135/",
          "https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "http://web.archive.org/web/20250818113925/https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "https://lis-skins.com/ru/blog/krupneisaia-mosenniceskaia-sxema-v-istorii-steam/",
          "https://www.reddit.com/r/cs2/comments/1e38jo4/stealing_accounts_and_removing_vac_bans_a_new/",
          "https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "http://web.archive.org/web/20250805141942/https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/outsourcing-archive-records.json",
          "https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "https://escorenews.com/en/csgo/news/44087-valve-steam-support-employee-accused-of-selling-inactive-accounts-inventories-worth-six-figures-b1t-has-one-of-these-skins",
          "https://phishdestroy.io/steam_dossier/ko/PART2_RESEARCH.md",
          "https://www.reddit.com/r/GlobalOffensive/comments/1h56shi/steam_support_is_stealing_accounts/",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/design-review/part2/quality-review.json",
          "https://phishdestroy.io/steam_dossier/ko/steam_evidence_archive.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ko/investigation_part2.content.json",
      "export_json_sha256": "a90a35e8e4bef2c30d1ab32045714960a91d13ccaceeb205c1f1fe958bc53a27"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ko/legal_analysis.html",
      "language": "ko",
      "title": "그들의 약관, 여러분의 권리 — ‘Steam’ 자료집",
      "source_url": "https://phishdestroy.io/steam_dossier/ko/legal_analysis",
      "source_html_sha256": "ea61efc4414f04e0786937466c4f5521abe03806f337a74754b32591274f5ca0",
      "exported_at": "2026-09-29T00:21:52.994Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "legal_analysis.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ko/legal_analysis.pdf?v=print-20260929-v5",
        "sha256": "12ed98d9359af7ec7dce98b03b93a8e9b8a60f1b95953d1b42b6bb1325a79992",
        "bytes": 106408,
        "pages": 6
      },
      "integrity": {
        "signed_object": "legal_analysis.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "legal_analysis.content.json.asc",
        "digest_file": "legal_analysis.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify legal_analysis.content.json.asc legal_analysis.content.json",
          "sha256sum -c legal_analysis.content.json.sha256"
        ]
      },
      "content": {
        "text": "법률 및 경제 보고서\n법률 분석 — 이용 약관 및 규제 준수\n\n그들의 조건. 귀하의 권리.\n\n이 섹션이 입증하는 바\n\n이 법의학적 법률 감사는 주요 규제 관할권 전반에 걸쳐 Valve Corporation과 Steam 사용자 간의 계약상 불균형을 평가합니다. 이 보고서는 취소 가능한 구독 라이선스가 법정 소비자 소유권을 어떻게 박탈하는지 규명하고, 디지털 재판매 소진에 관한 유럽사법재판소의 판례를 분석하며, 디지털 서비스법(DSA) 및 유럽 연합 이사회 규정(GDPR) 제15.조에 따른 준수 여부를 검토합니다. 이 분석은 자동화된 집행 메커니즘이 실질적인 이의 제기 절차 없이 어떻게 작동하는지, 그리고 플랫폼 시장 수수료가 모든 피어 간 거래에서 체계적으로 경제적 가치를 추출하는 방식을 보여줍니다.\n\n← 경영진 브리핑으로 돌아가기\n\n본 보고서는 ‘Steam’가 공표한 플랫폼 규칙과 소비자의 실제 처지 사이의 격차에 대해 법적, 경제적, 기술적 분석을 제시한다. 즉, 소비자에게는 구제 수단이 거의 없는 자동화된 집행 체계와 디지털 자산에 대한 기업의 광범위한 통제권이 존재한다는 점이다. 모든 수치는 출처를 명시하여 제시하였으며, 원본 기록을 확인할 수 없는 수치는 생략하였다.\n\n벡터 1\n\n“소유권”을 취소 가능한 라이선스로 대체하여, 계약에 따라 디지털 자산을 회수할 수 있도록 한다.\n\n벡터 2\n\n자동 제재 시스템(VACNet)의 경우, Steam Support에 따르면 해당 제재 조치는 되돌릴 수 없다고 명시되어 있습니다.\n\n벡터 3\n\n계정 및 자산 통제 기능과 더불어, 재판매가 이루어질 때마다 생태계의 가치를 훼손하는 ‘15%’ CS2 마켓 수수료(5%, Steam 및 10%의 퍼블리셔 수수료)가 결합되어 있습니다.\n\n용어의 비대칭성\n책임 면제 및 취소 가능한 라이선스\n2.1 “구독” 모델 대 재산권\n\nSteam 가입자 계약서 제2조에서는 사용자에게 오직 개인적, 비독점적, 양도 불가하며 취소 가능한 라이선스. 본 계약에 따라, Valve은 언제든지 계정을 해지할 수 있으며, 미사용된 Steam 지갑 잔액은 소멸될 수 있습니다.\n\n2.2 ‘환불 환상’ 대 EU 소비자 권리 지침\n법적 체계\t환불 절차\t제한 사항\nEU Consumer Rights Directive\tUnconditional 14-day right of withdrawal on digital content\tWaived if download begins with explicit consumer consent\nSteam SSA\t14 days / under 2 hours played\tValve may deny at its discretion for \"abuse\"\n평가\n\nValve EU의 14-에 명시된 법정 철회권은, 제품을 평가하기 전에 다운로드 시점에 수락해야 하는 “14일 / 2시간”이라는 기간을 조건으로 합니다. 이 정책은 법정 권리를 확대하는 것이 아니라 제한하는 것이며, 이것이 합법적인지 여부는 관할 당국이 판단할 문제이지, 여기서 단정할 수 있는 결론은 아닙니다.\n\n소송\n이차 시장과 독점 금지법\nUFC Que Choisir 대 Valve — 프랑스\n2019\n파리 법원: 디지털 게임에도 권리 소진 원칙이 적용된다 — 재판매는 합법이다\n10월 2022\n파리 항소법원이 판결을 뒤집었다\n23 10월 2024\n대법원(Cour de cassation): 비디오 게임은 정보사회지침(InfoSoc Directive)상 ‘복합 저작물’이며, 소프트웨어가 아니다. 디지털 재판매 금지됨. ‘Valve’가 승리했다.\nWolfire Games 반독점 소송 — 미국 (Valve 반독점 소송 사건, 사건 번호 2:21-cv-00563)\n\nValve의 최혜국 대우(PMFN) 조항에 따라 개발자들은 다른 어떤 플랫폼에서도 ‘Steam’ 키를 더 저렴한 가격에 판매할 수 없습니다. 경쟁 업체들 — 심지어 Valve의 30%와 비교해 12%의 수수료를 부과하는 곳조차도 — 이 절감분을 소비자에게 전가할 수 없습니다.\n\n336Valve의 전체 직원 수 (2021). 출처: 공개된 증거자료.\n79Steam 플랫폼 전체를 관리하는 직원들. 출처: 공개된 증거자료.\n$3.5M직원 1인당 순이익. 출처: 공개된 증거자료.\n\n공개된 증거개시 기록에 따르면 2021의 총매출액은 $8.5B입니다. 336 직원들에 대한. 해당 79-Steam 팀 구성원 373,000및 일일 지원 티켓을 외부 위탁 자동화 콜센터로 연결하여 처리했습니다.\n\n공개된 사건 기록 첨부 자료 · 워싱턴주 W.D. 사건 번호 2:21-CV-00563내부 조사 메모\n\n팀 스위니(에픽 게임즈 CEO)가 게이브 뉴웰에게: \"결제 처리 비용이 2–5%이고, CDN 대역폭 비용이 GB당 $0.002/인 상황에서, 왜 Steam는 여전히 총매출의 30%를 가져가는 걸까요? Steam에서 상위 25 게임들을 제외하면, Valve가 그 다음 순위인 1,000 게임들 대부분에서 개발사들보다 더 많은 수익을 올렸을 거라고 장담합니다.\"\n\n스콧 린치(Valve Corporation 최고운영책임자)가 게이브 뉴웰에게 보낸 내부 전달 메일: \"너 화났어, 형?\"\n\n선서 진술서 반박 (블룸버그, 2026): 규칙30 (b) (1)에 따른 증인신문에서, 게이브 뉴웰은 다음과 같이 증언했다. \"Valve는 다른 플랫폼의 제3자 소프트웨어 개발사들에게 가격을 강요하는 정책이나 관행을 가지고 있지 않습니다.\" 원고들은 뉴웰에게, 경쟁 스토어에서 더 낮은 가격을 책정한 개발자들을 상대로 적극적인 가격 통제 및 상품 목록 삭제 위협이 있었다는 사실을 입증하는 ‘Valve’ 내부 메모를 제시하며 맞섰다. 3월 말 2026, 연방 법원은 ‘Valve’의 즉결 판결 신청을 기각하고, 32,000-개발자 집단 소송을 배심원 재판으로 회부했다.\n11월 2024\n\n다음 사건에 대한 집단소송이 인가되었습니다. ~ ‘32,000’ 개발진 1월 이후 수수료를 지급한 업체들 2017, 및 이와 병행하여 제기된 소비자 집단 소송.\n\n청구된 손해배상액\n\n$3.1B\n미국 독점금지법에 따른 3배 배상 = $9.3B 잠재적 노출.\n\n6월 2026: 최근 제기된 소송에 따르면, 마이크로소프트와 Valve이 PC 게임 유통 시장에서 경쟁을 억제하는 카르텔 합의를 맺은 것으로 주장되고 있다.\n\n금융 범죄 및 자금세탁방지(AML) 정식 입학\nValve 공식 고백: Worldwide Fraud Liquidations (28 10월 2019)\n\n28년 10월 2019, Valve는 새로 구매한 카운터스트라이크 컨테이너 키의 거래 및 마켓플레이스 재판매를 공식적으로 중단했습니다. 공식 공지를 통해 (blog.counter-strike.net/2019/10/26113), ‘Valve’사는 자사가 구축한 가상 경제가 국제적인 자금 세탁 중개 거점이 되었다는 사실을 서면으로 인정했다:\n\n\"과거에는 우리가 확인한 대부분의 키 거래가 정당한 고객들 사이에서 이루어졌습니다. 하지만 최근 전 세계적인 사기 조직들이 CS:GO 키를 이용해 불법 수익을 현금화하는 방식으로 전환했습니다. 현재 시점에서 마켓플레이스에서 거래되거나 판매되는 키 구매 건의 거의 전부가 사기 출처에서 비롯된 것으로 추정됩니다.\"\n\n규제 환경: 이러한 자백은 워싱턴주 도박위원회(WSGC)가 ‘Valve’에 공식 최후통첩을 보낸 데 이어, 범죄 도박 조사가 플랫폼 운영에 위협이 되자 비로소 ‘Valve’의 칼 콰켄부시(Karl Quackenbush) 법무자문이 ‘23’ 스킨 도박 도메인(CSGO Lotto, CSGOLounge, OPSkins 등 포함)에 대해 7월 2016에서 발령한 ‘중지 및 철회’ 명령에 따른 것이었다.\n\n관할권\n러시아에 있는 권리자이며, 사용자가 연락할 수 없음\n\n이 가입자 계약서는 Valve을 거의 아무런 책임도 지지 않으며 누구도 접근할 수 없는 당사자로 묘사합니다. 제한 조치는 영구적이며, 이의 제기는 기각되고, “제재 대상 지역”에 대한 단 한 줄의 문구만으로 전체 지역에 대한 접속이 차단됩니다. 이러한 태도와 대조적으로, Valve은 평소에는 다루기 까다롭다고 여기는 관할권에서 자사의 상업적 이익이 걸려 있을 때 어떤 조치를 취하는지 보여줍니다.\n\nValve v. Touch Skins — 러시아에서 제기된 재판 전 지적재산권 청구\n1 9월 2026\nValve는 러시아의 한 법률사무소를 통해 멜링, 보이티슈킨 앤 파트너스, ~의 운영자들에게 재판 전 요구서를 발송한다. 터치 스킨, CS2용 대형 스킨 체인저로, 러시아 우편 및 이메일을 통해 배송됩니다.\n근거\n위반 혐의는 크게 세 가지로 나뉩니다. 소프트웨어에 대한 독점적 권리, 무기·칼·장갑 스킨의 외관에 대한 권리, 그리고 ‘Valve’의 상표권입니다. 운영자들의 행위는 고의적이고 장기간에 걸친 것으로 간주됩니다.\n수요\n즉시 운영을 중단하고 모든 인프라를 삭제하십시오 — 해당 소프트웨어의 소스 코드, 웹사이트 및 소셜 미디어 페이지 — 이를 준수하지 않을 경우, Valve는 러시아 법원에 소송을 제기할 권리를 보유하며, 그 사유는 다음과 같습니다. 상당한 금전적 보상 그리고 이 사안을 다음 기관에 회부하기 위해 범죄 평가를 위한 법 집행.\n결과\n이 서신을 받은 후, 해당 플랫폼은 서비스를 중단한다고 발표했다. 이는 ‘Valve’가 러시아 내 스킨 체인저 개발자를 상대로 법적 조치를 취한 첫 사례로 알려졌다.\n\n데이터 마이닝 전문가 막심 “GabeFollower” 폴레타예프(X, ~11 9월 2026)와 러시아 게임 언론이 보도했습니다. 이는 소송 제기 전의 청구 사항일 뿐, 실제로 제기된 소송은 아니며, 공개된 사건 번호도 없습니다. 본 글에서는 이를 법원 기록이 아닌 보도된 내용대로 다루고 있습니다. 출처: dota2.ru 보관됨 2026-09-24 ↗ · 샤주.\n\n같은 관할 구역, 반대 방향\n\nValve 러시아의 법률 및 규제 체계에 익숙한 편이다. 그것은 Roskomnadzor의 규정을 준수합니다: 규제 당국의 요구에 따라 금지된 콘텐츠를 게재하고 있던 260및 Steam 커뮤니티 페이지를 삭제하였으며, 로스콤나드조르(Roskomnadzor)는 Steam이 관련 법률의 요건을 충족한다고 공개적으로 밝혔습니다. 러시아의 ‘랜딩’ 법(연방법) 236-FZ(2022부터 시행)에 따라, 러시아 사용자에게 서비스를 제공하는 대규모 해외 인터넷 플랫폼은 현지 거점을 마련하고 로스콤나드조르(Roskomnadzor)와의 연락 창구를 개설해야 합니다. Valve는 해당 규제 당국의 게시물 삭제 명령에 응할 뿐만 아니라, 이제는 러시아 내 법률 자문단을 활용하고 러시아 법원의 제재를 무기로 삼아 자사의 스킨을 지적 재산권으로 보호하고 있습니다.\n\n따라서 이 플랫폼은 수익과 관련된 문제에 있어서는 접근성이 뛰어나고, 역량이 충분하며, 자신의 권리를 단호하게 주장합니다. 이와 대조적으로 사용자는 제재 대상 지역에 거주하는 유료 고객임에도 불구하고 관계가 종료되었다는 통보를 받으며, 2038, 티켓이 처리될 때까지 커뮤니티 접근이 차단되고, 이 결정에 이의를 제기할 수 있는 포럼은 존재하지 않습니다 — \"그들은 기꺼이 제 돈을 받고 거래를 처리해 주었습니다\", 같은 계정에 대해 같은 이란 IP 주소에서 요청된 환불이 1년 전에 승인된 바 있다 (r/pcgaming, 4 8월 2026; 더 많은 집행 통지서가 카드 경제 전시회). ‘Valve’은 스킨을 보호하기 위해 국가 법률 체계의 모든 수단을 동원하지만, 스킨을 구매한 사용자에게는 어떠한 절차도 보장하지 않는다.\n\nValve Valve의 이익이 걸려 있을 때는 — 러시아 측 변호인, 러시아 법원의 위협, 로스콤나드조르(Roskomnadzor)의 게시 삭제 명령에 대한 대응 등 — 해당 관할권을 자사가 활동하고 규정을 준수할 수 있는 영역으로 취급하는 반면, 해당 시장 및 그 밖의 모든 시장의 사용자에 대한 의무는 어떠한 절차의 적용 범위 밖인 것처럼 취급합니다. 수익이 걸린 문제에서는 권리자처럼 행동하지만, 사용자의 권리가 관련된 문제에서는 접근할 수 없는 당사자로 변모합니다.\n\n출처: TASS (RKN: Steam 준수) · 연방법 제236-호 FZ.\n\n법적 기회주의\n중재 조항의 양보\n2023 — 그 공격\n\n로펌들(Zaiger LLC, Mason LLP)은 소셜 미디어를 통해 수천 명의 사용자를 모집한 뒤, 수만 건의 개별 중재 청구를 동시에 제기했다.\n\nValve의 노출\n\n$225M+\n본안 심리가 시작되기도 전에 환불 불가능한 중재 신청 수수료를 지불해야 했다. 미국중재협회(AAA) 소비자 중재 규칙 및 집단 중재 보충 규정에 따라 산정되었습니다. Zaiger LLC와 Mason LLP가 대리하는 청구인들은 Valve Corp.을 상대로 약75,000건의 개별 중재 청구를 제기했습니다(다음의 반독점 청구와 병행하여 Wolfire Games LLC 외 대 Valve Corp., 사건 번호2:21-cv-00563-JCC, W.D. (워싱턴주). AAA 소비자 수수료 규정에 따라, 피고 기업은 환불 불가능한 사건 처리 수수료와 중재인 선임 보증금으로 사건당 약 $3,000+를 지불해야 합니다(75,000건의 제출 × $3,000 = 약 $225M의 선불 절차 비용). 기술 기업의 대규모 중재 위험에 대한 블룸버그 로(Bloomberg Law) 및 로이터(Reuters)의 법률 보고서를 참조하십시오(2023–2024).\n\n기간\tSSA 분쟁 해결 절차\t관측된 효과\t결과\nBefore Sep 2024\tMandatory individual arbitration + class-action waiver\tIndividual litigation becomes economically irrational for users\tMass arbitration → $225M fee threat\nAfter Sep 2024\tDisputes in King County, WA courts only\tArbitration costs are avoided; cases consolidate in a single forum\tClass actions now possible\n결론\n\n10년 넘게 SSA는 이용자들에게 배심원 재판에 대한 권리를 포기하고 개별 중재를 선택하도록 요구해 왔습니다. 대규모 중재 신청으로 인해 워싱턴 디지털 미디어(Valve)에 재정적 부담이 가중되자, SSA는 분쟁을 킹 카운티 법원으로 이관하도록 개정되었습니다. 이 변경 사항은 실질적인 거부권 없이 제시되었으며, 수락하지 않을 경우 계정을 삭제함으로써 구매한 디지털 자산에 대한 접근 권한을 상실하게 되는 상황이었습니다.\n\n알고리즘 기반 집행\nVACNet, 유죄 추정, 그리고 오탐\n10월 2023 — AMD Anti-Lag+\n\nAMD 드라이버 업데이트(v23.10.1)로 인해 CS2에서 Anti-Lag+ 기능이 활성화되었고, 이로 인해 게임 DLL 함수가 가로채어졌습니다. VAC는 이를 치트 코드 주입으로 분류하여, Valve가 개입하기 전까지 수천 명의 정상 사용자에게 영구 제재를 가했습니다.\n\n12월 2023 — 고해상도(DPI)\n\n10,000 이상의 DPI를 사용하며 카메라를 급격하게 회전시킨 플레이어들은 영구 제재를 받았습니다. VACNet은 실제 마우스 움직임과 “스핀봇” 치트를 구분하지 못했습니다.\n\n지원 카테고리\t표시된 응답 시간\t실제 결과\nRefund requests\t50 min – 1.5 hr\tAutomatic approval (<14 days, <2 hours played)\nAccount security / recovery\t3–12 hours\tDepends on documentation provided\nContesting a VAC ban\tForm response\tComplete refusal. Support cannot reverse VAC decisions. The ban is permanent.\nValve의 공식 정책\n\n\"VAC 제재는 영구적이며, 타협의 여지가 없으며, Steam 지원팀을 통해서도 해제할 수 없습니다.\"\n\n제재 조치를 전달하는 지원 채널을 통해 재검토 요청이 거부되었다는 내용도 함께 전달됩니다: Steam 지원팀은 VAC의 결정을 번복할 수 없다고 밝혔습니다. 사용자에게 있어 알고리즘의 판정이 최종 결과입니다.\n\n재판매의 경제학\n가상자산에 대한 통제권 및 재판매 수수료\n15%의 CS2 시장 수수료 — 재판매 시마다 해당 금액이 차감됩니다\n반복\t구매자 잔액\t판매자가 수령합니다\t『Burned』(15%)\n1\t$100.00\t$85.00\t$15.00\n2\t$85.00\t$72.25\t$12.75\n3\t$72.25\t$61.41\t$10.84\n10\t$23.16\t$19.68\t~$3.47\nTotal\t$100 → dust\tValve collects the 15% fee on each resale. Users must add new money to keep trading.\nCS2 트레이드업 규칙 변경 — 10월 2025\n\nValve는 사전 공지 없이 CS2 트레이드업 계약 규정을 변경하여, ‘코버트(Covert)’ 등급 아이템을 교환 조건으로 희귀 나이프와 장갑을 보장된 방식으로 획득할 수 있도록 했습니다. 이에 따라 나이프 가격은 하락하고, 코버트 등급 아이템 가격은 급등했으며, 시장 전반에 걸쳐 패닉 매도가 이어졌습니다.\n\nValve가 내세우는 법적 근거는 사회보장법(SSA) 제7조로, 플랫폼 규칙 변경에 대한 책임을 지지 않는다는 내용입니다. Valve에서 볼 수 있듯이, 사전 통지나 보상 없이 규칙이 변경될 수 있는 경제 환경에서는 사용자가 그 위험을 감수해야 합니다. 보고된 시장 전체 손실 규모에 대해서는 논란이 있으며, 1차 출처가 없는 한 본문에서는 이를 명시하지 않습니다.\n\n유럽의 규제 대응\nUOKiK, DSA 및 디지털 공정법\nUOKiK — 폴란드, 5월 2024\n\n폴란드 반독점 당국(UOKiK)은 Valve 코퍼레이션과 5개의 국내 게임 퍼블리셔 및 유통사를 상대로, 가격 담합, 가격 균등 유지 조항, 지역 차단 관행 등의 혐의로 공식 반독점 절차를 개시했다. 이러한 관행으로 인해 폴란드 소비자들은 인접한 유럽경제지역(EEA) 시장보다 디지털 게임을 구매할 때 최대 20% 더 많은 비용을 지불해야 했다. 이번 반독점 조사의 일환으로, UOKiK 조사관들과 경찰은 폴란드 내 제휴 퍼블리셔 및 유통업체의 사업장(Valve가 폴란드에 법인을 두고 있지 않으므로, Valve의 자회사 사무소는 제외됨)을 대상으로 새벽 급습 및 증거 압수 수색을 실시했다. 잠재적 법정 과징금은 연간 매출액의 최대 10%에 달할 수 있다. 출처: UOKiK 공식 발표, “UOKiK 위원장이 ‘Valve’ 및 게임 개발자들을 상대로 조사 절차를 개시했다”, 5월 2024.\n\n디지털 서비스법(DSA)\n\n자동화된 검토 과정에 투명성이 필요합니다. Steam은 VACNet에 대한 오탐지/누락 데이터를 공개하지 않으며, 해당 지원 채널에 따르면 VAC 결정은 번복될 수 없다고 명시되어 있습니다.\n\n디지털 공정법 — 2026\n\n예상되는 규정: 유료 콘텐츠에 대한 지속적인 접근권 보장, 권리 포기 시점에 ‘다크 패턴’ 사용 금지, 디지털 자산에 대한 재산권 인정, 영구적인 재고 몰수로부터의 보호.\n\n결론\n규칙과 기록 간의 확인된 차이점\n1\n\n소유권 격차. 사용자들은 계약에 따라 Valve가 취소할 수 있는 라이선스에 대해 정가를 지불합니다. 프랑스 대법원(10월 2024)은 디지털 재판매가 보호 대상이 아니라고 판결함으로써, 이 입장을 법적으로 확립했습니다.\n\n2\n\n알고리즘 기반 집행. VACNet이 부당한 제재를 가했습니다(AMD 드라이버, 고해상도(DPI) 관련 사례). Steam 지원팀은 VAC의 결정을 번복할 수 없다고 밝혔으므로, 알고리즘의 판단이 최종 결정입니다.\n\n3\n\n수수료 절감. 15%의 CS2 시장 수수료(5% Steam + 10% 판매자 수수료)는 재판매 시마다 상품의 가치를 감소시키며, 플랫폼 규정은 사전 통지 없이 변경될 수 있습니다. SSA에 따라 Valve는 이러한 변경에 대한 책임을 부인합니다.\n\n4\n\n중재 조항이 삭제되었습니다. SSA는 지난 9월 2024,, 대규모 집단 소송 제기로 인해 Valve가 약 $225M의 수수료를 부담하게 되자 의무 중재 제도를 폐지했다. 사용자들은 이번 변경 사항에 대해 실질적인 선택권(옵트아웃)을 부여받지 못했다.\n\n5\n\n선택적 관할권. Valve 러시아 법률 사무소(Melling, Voitishkin & Partners)를 선임하고 Touch Skins를 상대로 러시아 법원에 소송을 제기하겠다고 위협하는 한편, 동시에 해당 시장의 사용자들에 대한 의무는 어떠한 사법 절차의 대상도 아니라고 취급했습니다. Valve은 자사의 상업적 이익이 걸린 상황에서는 권리 보유자 역할을 하지만, 사용자의 권리가 관련된 상황에서는 연락조차 닿지 않는 당사자로 행동합니다.\n\n← 제1부: 프록시 우회 및 도박제2부: 접근성 및 책임성 →\n\n법률 자료 및 판례 기록은 원본 발행처 및 소장 기관을 출처로 명시합니다. 해당 문서에 대한 소유권을 주장하지 않습니다.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "법률 분석 — 이용 약관 및 규제 준수"
          },
          {
            "level": 2,
            "id": null,
            "text": "책임 면제 및 취소 가능한 라이선스"
          },
          {
            "level": 3,
            "id": null,
            "text": "2.1 “구독” 모델 대 재산권"
          },
          {
            "level": 3,
            "id": null,
            "text": "2.2 ‘환불 환상’ 대 EU 소비자 권리 지침"
          },
          {
            "level": 2,
            "id": null,
            "text": "이차 시장과 독점 금지법"
          },
          {
            "level": 3,
            "id": null,
            "text": "UFC Que Choisir 대 Valve — 프랑스"
          },
          {
            "level": 3,
            "id": null,
            "text": "Wolfire Games 반독점 소송 — 미국 (Valve 반독점 소송 사건, 사건 번호 2:21-cv-00563)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve 공식 고백: Worldwide Fraud Liquidations (28 10월 2019)"
          },
          {
            "level": 2,
            "id": null,
            "text": "러시아에 있는 권리자이며, 사용자가 연락할 수 없음"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve v. Touch Skins — 러시아에서 제기된 재판 전 지적재산권 청구"
          },
          {
            "level": 3,
            "id": null,
            "text": "같은 관할 구역, 반대 방향"
          },
          {
            "level": 2,
            "id": null,
            "text": "중재 조항의 양보"
          },
          {
            "level": 2,
            "id": null,
            "text": "VACNet, 유죄 추정, 그리고 오탐"
          },
          {
            "level": 2,
            "id": null,
            "text": "가상자산에 대한 통제권 및 재판매 수수료"
          },
          {
            "level": 3,
            "id": null,
            "text": "15%의 CS2 시장 수수료 — 재판매 시마다 해당 금액이 차감됩니다"
          },
          {
            "level": 3,
            "id": null,
            "text": "CS2 트레이드업 규칙 변경 — 10월 2025"
          },
          {
            "level": 2,
            "id": null,
            "text": "UOKiK, DSA 및 디지털 공정법"
          },
          {
            "level": 2,
            "id": null,
            "text": "규칙과 기록 간의 확인된 차이점"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/ko/#briefing-heading",
          "https://dota2.ru/news/67707-valve-cerez-uristov-napravila-krupnoj-rossijskoj-skincendzer-platforme-trebovanie-o-prekrasenii-deatelnosti/",
          "http://web.archive.org/web/20260924181657/https://dota2.ru/news/67707-valve-cerez-uristov-napravila-krupnoj-rossijskoj-skincendzer-platforme-trebovanie-o-prekrasenii-deatelnosti/",
          "https://shazoo.ru/2026/09/12/190508/valve-cerez-rossiiskix-iuristov-dobilas-zakrytiia-krupnogo-skinceindzera-dlia-cs2",
          "https://www.reddit.com/r/pcgaming/comments/1vf24lu/warning_to_all_gamersexpats_steam_took_my_money/",
          "https://phishdestroy.io/steam_dossier/ko/card_economy.html#asymmetry",
          "https://tass.ru/obschestvo/23235387",
          "https://base.garant.ru/401414628/",
          "https://uokik.gov.pl/postepowanie-wyjasniajace-w-sprawie-valve-i-dystrybutorow-gier",
          "https://phishdestroy.io/steam_dossier/ko/",
          "https://phishdestroy.io/steam_dossier/ko/investigation_part2.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ko/legal_analysis.content.json",
      "export_json_sha256": "19781dae82eae8137290594563fd5745bc2a8033f9e3c41e018562232e819543"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ko/license_disclaimer.html",
      "language": "ko",
      "title": "라이선스 · 권리 · 면책 조항 — PhishDestroy",
      "source_url": "https://phishdestroy.io/steam_dossier/ko/license_disclaimer",
      "source_html_sha256": "a8c80c9e37d5557841b0e0343d203273860fbbb7bb54fb43c77f285b9906a05e",
      "exported_at": "2026-09-29T00:21:54.786Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "license_disclaimer.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ko/license_disclaimer.pdf?v=print-20260929-v5",
        "sha256": "86feca10126599f31a157c53b303dd17dc635b9f63736c0d8df885536c2368ab",
        "bytes": 115675,
        "pages": 8
      },
      "integrity": {
        "signed_object": "license_disclaimer.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "license_disclaimer.content.json.asc",
        "digest_file": "license_disclaimer.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify license_disclaimer.content.json.asc license_disclaimer.content.json",
          "sha256sum -c license_disclaimer.content.json.sha256"
        ]
      },
      "content": {
        "text": "PHISHDESTROY법의학 조사 · Valve / Steam\n라이선스 · 권리 · 면책 조항\n라이선스 및 법적 고지 — 퍼블릭 도메인 헌납\n\n모든 권리 인류에게 굴복했다.\n\n이 섹션이 입증하는 바\n\n본 문서는 PhishDestroy Steam Dossier에 적용되는 무조건적인 퍼블릭 도메인 헌납(CC0 1.0 Universal) 및 MIT 소프트웨어 라이선스 조건을 규정합니다. 모든 포렌식 조사 결과, 증거 데이터 세트, 네트워크 그래프 및 분석 방법론은 전 세계적으로 규제, 법률 및 학술적 목적으로 제한 없이 사용될 수 있도록 취소 불가능하게 퍼블릭 도메인에 귀속됩니다.\n\n← 경영진 브리핑으로 돌아가기\n\nPhishDestroy 이 자료에 대한 모든 권리(복제, 판매, 자신의 이름을 표기하는 것 등)를 포기합니다. 다음은 하나의 목소리로 작성된 두 가지 문서입니다. 하나는 우리가 평소 쓰는 방식으로 작성한 Valve에 보내는 공개 서한이고, 다른 하나는 이 내용을 이어갈 기관을 위해 작성된 공식적인 권리 포기서입니다.\n\n조사 · Valve Corporation / Steam공개 버전 — 만료일 없음, 취소 불가\n면제됨\n제1절라이선스 — 법적인 측면은 그렇다 치고, 인간적인 측면에서\n\nPhishDestroy 이 자료에 대한 모든 권리를 포기합니다. 전혀 없습니다. 다 끝났습니다. 복제하든, 팔든, 자신의 이름을 붙이든, 상사 몸에 문신으로 새기든, 뭐든 마음대로 하세요. 출처 표기도, DM도, 감사 카드도 필요 없습니다.\n\n실제 규칙 하나 (네, 딱 하나뿐입니다)\n\n자신이 테러리스트인지 아닌지는 당신이 결정할 수 있는 문제가 아닙니다.\n\n러시아 또는 OFAC 제재 대상 국가의 사용자라면 — 이 자료는 귀하를 위한 것이 아닙니다. 예외는 없습니다. 제재의 즐거움을 만끽하세요.\n\n혹시 모스크바에 있으면서 Steam의 지역을 터키로 변경했다면 — 참 독창적인 지리 지식을 보여주셨군요. 그래도 당신은 여전히 러시아인입니다. 제재는 여전히 적용됩니다. 그게 바로 핵심입니다.\n\n제2절이것이 무엇이며 왜 존재하는지\n\n우리는 ‘Valve’에 대해, ‘Valve’의 평범한 직원 한 명이 자신에 대해 알고 있는 것보다 더 많은 정보를 공개할 것입니다. 이건 자랑이 아닙니다. 그저 우연히 그렇게 된 것뿐입니다.\n\n어떻게 여기까지 오게 된 걸까요? 재미있는 이야기인데, 사실 ‘Steam’가 우리를 만들어낸 셈이에요. 그곳의 사기꾼들, 지원 티켓, 차단 우회 생태계 속에서 우리가 자라났고, 이제 이렇게 여기까지 왔네요. 원망할 생각은 없어요. 사실 꽤 시적인 이야기네요.\n\n아직 그 배경 이야기를 읽지 못한 분들을 위해 말씀드리자면, 우리는 이미 ‘Valve’의 엄청나게 비싼 유럽 변호사들(물어보시는 분들을 위해 말씀드리면 Taylor Wessing입니다)을 만난 바 있습니다:\n\nhttps://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d 보관됨 2026-08-21 ↗\n\n매력적인 만남이었어요. 특히 시간당 요금을 생각하면 더더욱 그렇네요.\n\nValve는 알고 있었을까? 그렇다. Taylor Wessing은 알고 있었을까? 거의 틀림없이 그렇다. 하지만 그 정도로 부자라면, 법이란 의무라기보다는 그저 분위기 같은 것이지, 그렇지 않은가?\n\n사실 그게 답의 전부라고 할 수 있겠네요.\n\nSteam 수년 동안 사기꾼들을 추적해 왔습니다. 항상 의도적인 것은 아니었습니다. 때로는 사기꾼들이 단순히 연관성 때문에 Valve의 흔적이 묻게 되기도 했죠. 우리가 이 문제를 과장하려는 건 아닙니다. 단지 사실을 정확하게 전달하려는 것뿐입니다. 솔직히 말해, 과장하는 것보다 사실을 정확하게 전달하는 게 우리에게는 더 어렵습니다. 이것이 바로 우리가 글을 쓰는 방식입니다.\n\n이게 갈등인가요?\n— 아니요.\n\n이 문제를 해결할 수 있을까요?\n— 네. 하지만 저희는 어떤 비밀유지계약(NDA)도 체결하지 않을 것이며, 푼돈을 위해 버그 바운티 프로그램에 참여하지도 않을 겁니다.\n\n우리는 스푸핑 문제를 해결하기를 4 년 넘게 기다린 후에야 비로소 이 문제를 공개적으로 다룰 수 있었습니다. 만약 우리가 더 일찍 이 문제를 다뤘다면, Steam는 마치 피해자인 척하며 “현재 진행 중인 위협!”이라고 소리 지르며, 우리를 영원히 그들의 법적 소유물로 만들 문서에 서명하도록 푼돈을 제시했을 테니까요. 사양하겠습니다.\n\n(또한: ‘Valve’ 자체가 비밀유지협약(NDA)을 위반하고 있습니다. 그 회사 직원들, 그것도 최고위층 인사들이 그렇게 하고 있죠. 하지만 좋아요, 우리 쪽 이야기로 넘어가 봅시다.)\n\n제3절Valve에게 보내는 공개 서한 — 정말로, 이거 꼭 읽어보세요\n\nValve: 이 도메인을 삭제하고 싶으시면 이메일을 보내주십시오. 해당 논의에는 외부 변호사의 참여가 필요하지 않습니다.\n\n잘 모르시는 분들을 위해 설명드리자면, 패트릭 박사는 애버딘 대학교에서 국제상법 분야 법학 석사 학위를 취득했으며, 놀랍게도 IT 법학 분야 박사 학위 논문을 실제로 완성했습니다. 그는 최근 테일러 웨싱(Taylor Wessing)의 파트너가 되었는데, 이 로펌은 테러라이즈 인크(Valve)와 같은 기업들에게 터무니없이 많은 금액을 청구하여 상대방이 자금이나 인내심을 다 소진할 때까지 소송을 질질 끄는 것을 비즈니스 모델로 삼고 있는 곳입니다.\n\n우리는 그를 탓하지 않습니다. 시간당 수임료를 지불하는 부유하고 죄책감을 느끼는 의뢰인들을 상대하는 건, 확실히 현명한 경력 전략이죠. 다만 여러분이 그 비용을 부담해서는 안 된다고 생각합니다.\n\n거래 조건 (공개 제안, 변호사 필요 없음)\n\nValve가 현실적으로 확보할 수 있는 것은 도메인뿐입니다. 조사, 의뢰, 관련 자원들은 이미 진행 중이며, 도메인이 있든 없든 상관없이 계속될 것입니다.\n\n해당 도메인을 원하신다면:\n\nIT 법률 전문가들에게 공정한 가격을 책정하도록 맡기십시오.\n\n50% SEAL 재단에 기부됩니다.\n\n도메인을 없애버립니다. 소동도 없고, 법정 공방도 없습니다. 끝입니다.\n\n이것은 협박이 아닙니다. 실제로 손에 넣을 수 있는 유일한 것에 대한 솔직한 제안일 뿐입니다. 다른 방법으로는 그것을 얻을 수 없습니다. 그게 바로 이 상황의 구조입니다.\n\n우리가 ‘Valve’에 직접적인 “타격”을 줄 수 있을까요? 아마도 그들이 재정적으로 체감할 만한 수준은 아닐 겁니다. 우리도 현실을 오판하지는 않으니까요. 하지만 우리는 영향력을 쫓지 않고, 정직하고 공개적으로 행동할 것입니다. 우리에게 영향력은 필요하지 않으니까요. 우리는 세상이, 충분히 시간을 들여 들여다본다면 누구나 알 수 있었던 사실을 깨닫기를 바랍니다.\n\n저희는 5에 해당하는 수년간의 기록을 보유하고 있습니다. Valve의 변호사들이 증거개시 절차에서 제시한 자료 — 요원들이 열람할 수 있는 데이터, 지문, 그리고 그들이 말 그대로 저희에게 건네준 서류 기록 — 만으로도 충분합니다. 이를 원본 그대로 유출할 필요는 없습니다.\n\n누가 무엇을 받는지\n\n규제 당국은 원본을 받습니다.\n\n연구자와 언론인들은 일부 내용이 삭제된 버전을 받습니다(피해자 진술서, 아동들의 로그인 정보, 그리고 Valve에 게시된 매력적인 지원 코멘트는 명백한 이유로 삭제되었습니다).\n\n피해 계정 중에는 미성년자도 포함되어 있었으나, 이들에게는 별도의 통지가 이루어지지 않았다. 이 조사 결과는 기사 내용에 실리기보다는 데이터 보호 당국에 제출되어야 할 사항이므로, 피해자 신고 내용과 신원 정보가 삭제된 상태로 규제 당국에 제출된 자료에 포함되어 있다.\n\n또한, Valve — 이 문제를 어떻게 처리할지 결정하기 전에 한 가지 분명히 해두고 싶습니다. PhishDestroy는 개인이 아닌 커뮤니티입니다. 여러분은 커뮤니티와 상의조차 하지 않은 채 커뮤니티를 수신인으로 법적 서신을 보냈을 때 이미 그 사실을 알게 되었을 텐데, 그저 데이터를 수집하기만 하고 계정을 차단해 버렸을 뿐입니다.\n\n이 커뮤니티는 Valve과 아무런 갈등도 없습니다. 우리가 먼저 찾아간 게 아닙니다. 여러분이 키운 사기꾼들이 우리를 찾아왔을 뿐입니다. 우리는 그들을 차단했습니다. 그리고 지금 이 지경에 이르렀습니다.\n\n제III-B절동맹국 자원 — 특히 ‘Steam’에 보내는 메모\n\n우리는 증폭 구조에 대해 솔직하게 밝히고자 합니다. 왜냐하면 그것이 존재하지 않는 척하는 것은 정직하지 못하기 때문입니다.\n\nPhishDestroy의 경우, 저희가 파악한 바에 따르면 이 자료를 받아들여 적극적으로 활용할 동맹 단체가 적어도 두 곳 있습니다.\n\n실제로 이는 다음과 같은 의미를 가집니다:\n\n그들은 겹치는 주제에 대해 각자 나름의 접근 방식을 취한다.\n\n그들은 독립적입니다. 우리 지시를 따르지 않고, 우리도 그들의 지시를 따르지 않습니다. 전반적인 주제는 같지만, 방법론은 다릅니다.\n\n그들은 파트1.에서는 활성화하지 않을 것입니다. 그들은 지켜보고 있습니다.\n\n만약 Valve가 해당 사이트를 삭제하지 않기로 결정한다면:\n\n‘2편’이나 ‘3.편’이 끝난 후에 그들이 모습을 드러낼 것으로 예상됩니다.\n\n그들은 우리 연구에서 유용한 부분을 가져다가 자신들의 연구로 보완한 뒤, 자신들의 이름으로 논문을 발표할 것입니다.\n\n이것이 바로 제1항에 명시된 라이선스가 바로 이러한 목적을 위해 마련된 것입니다. 자료는 필요한 곳으로 전달되고, 보충되며, 확장되는데, 우리도 그들도 서로에게 출처를 표기할 의무가 없습니다.\n\n(책임의 연쇄 관계에 대해 궁금해하는 변호사 분들께 드리는 참고 사항: 그런 것은 없습니다. 이 자료들은 저희의 지시나 자금 지원, 데이터를 제공받지 않습니다. 이들은 공개된 정보를 참고하여 스스로 결론을 내릴 뿐입니다. 여러분도 그렇게 할 수 있듯이요.)\n\n이 말을 위협하려는 뜻은 아닙니다. ‘Valve’ 측에서 전략을 수립하고 있는 분들이 정보 환경이 실제로 어떤 모습인지에 대해 정확한 정보를 얻으시기를 바라는 마음에서 하는 말입니다.\n\n우리 자료를 종합하고 보완해 주는 한 가지 자료는 이야기일 수 있습니다. 두 가지 자료가 각각 독립적으로 이를 수행하고 유사한 결론에 도달한다면, 이는 하나의 패턴이 됩니다. 규제 당국은 바로 이러한 패턴에 주목합니다.\n\n제4절돈, 금지 조치, 그 모든 소동\n\nSteam가 도박 사이트와 사기꾼들을 차단하는 데에는 이런 사실이 있습니다. 이는 단속이 아니라 수익 확보를 위한 것입니다. Valve는 돈을 챙기고는 손을 씻은 뒤, 무대에 올라 포켓몬 카드와 야구에 관한 건전한 이야기를 모두에게 들려줍니다.\n\n지원 측의 보안 침해 사례가 기록된 경우 — 여기에는 2월 Valve에서 도움 요청을 통해 고가치 계정이 해킹당한 것에 대한 책임을 인정하는 서면 진술서(2023)와, $320k 규모의 내부자 거래 사건(제2부 §04 · 주요 자료 §14.1) — 이 내용은 공개된 인정 사실과 탐사 보도에 근거한 것이다. 지원 직원들이 도박 부업을 하거나 금지 조치를 해제해 주는 대가로 수수료를 챙긴다는 근거 없는 소문은 공개된 기록을 통해 입증되지 않았으므로 본문에서는 제외되었다.\n\n한편, Valve는 2017.에서 스킨을 제대로 추적할 수 있는 기능을 없앴습니다. 심지어 자사 포럼에서도 이 문제를 논의하기까지 했습니다. 이를 “도박 방지 조치”라고 명명했지만, 그 후 수년 동안 스킨 도박 생태계는 여전히 Steam의 인프라를 통해 수십억 단위를 계속 유통시켰습니다. 참 훌륭한 브랜딩이네요.\n\n우리는 다음을 증명할 것입니다:\n\n스킨은 모네로보다 익명성이 더 높습니다\n\n페루의 한 카르텔이 자금 이동을 위해 ‘도타(Dota) 2’ 스킨을 사용한 것으로 알려졌다\n\nSteam 기능적으로는 “트레이딩 카드” 형태로 약7B 상당의 가치를 지닌 제재 회피 수단입니다(네, 실제로 검사에게 트레이딩 카드라고 말했습니다).\n\n스킨에 관한 영상이 하나 있어요. 보시게 될 거예요.\n\n또한 우리는 다음과 같은 사실을 알고 있습니다:\n\n레딧의 운영은 Valve의 영향을 받습니다.\n\nSteam의 타사 데이터 인프라(예: steamid.uk)는 개인이 운영하고 있습니다 (msart)와 연계된 자매 프로젝트인 금지 목록 프로젝트(steambans.com 아카이브)는 공식 인증된 ‘Valve’ 커뮤니티 운영자(killahinstinct_) — 이로 인해 플랫폼 이용 정지 조치에 대한 독립적인 감사는 전적으로 ‘Valve’의 관할 하에 남게 되었다 (‘카드 경제’ 항목의 “08” 절 참조)\n\n자신들이 통제할 수 없는 것은 금지해 버린다\n\nValve: 계속 모른 척하고 싶다면 — 괜찮습니다. 당신의 ‘안전지대’는 잘 알겠습니다. 어차피 Google Analytics는 사용자 IP 주소를 익명화합니다. 우리는 어떤 내용이 삭제되는지 알고 있습니다. 다만, 당신의 변호사들이 신경 쓸 만큼 저렴한 비용으로 이를 증명할 수는 없을 뿐입니다. 아직은요.\n\n제5절악성코드 문제 — 네, 그 점에 대해 언급하고 있습니다\n\n일련의 사건들이 어떻게 전개되었는지에 대해 냉정하고 명확하게 짚어봅시다. 그 과정을 통해 당신이 정확히 어떤 사람인지 드러나기 때문입니다.\n\n저희는 게임 내 취약점을 공개적으로 알리지 않을 것입니다. 또한 Steam에 이를 보고하지도 않을 것입니다. 해당 프로그램에는 비밀유지계약(NDA) 체결이 필수이며, 이를 체결할 경우 영향을 받은 사용자들에게 자신의 계정에 무슨 일이 일어났는지 알릴 수 없게 됩니다. 계정을 잃은 사용자들과 규제 당국에 이를 알리는 것이 바로 이 작업의 목적이므로, 비밀유지계약은 그 목적과 양립할 수 없습니다.\n\n실제로 일어난 일은 이렇습니다. 이 취약점은 관련 업계에서는 사실상 공공연한 비밀이나 다름없습니다. 독립 보안 연구원들이 이미 Steam 지원팀에 전체 익스플로잇 코드를 직접 제시했다는 사실을 우리는 확실히 알고 있습니다. 그 부분은 이미 끝난 일입니다. 여러분은 자체적인 공식 경로를 통해 이미 공식적인 경고를 받은 상태입니다.\n\n그렇다면 Valve는 무엇을 했을까? 아무것도 하지 않았다. Valve에게 보안은 이익과 직결되지 않기 때문이다. 사실 정반대다. 보안은 비용 발생원일 뿐이다. 위협이 임계점에 도달해 치명적인 대외적 이미지 파탄을 초래하기 전까지는, Valve는 이를 시급한 문제로 다루지 않는다.\n\n그럼 우리는 무엇을 하고 있는 걸까요? 대중에게 그 존재를 알리고 있습니다. 왜냐하면 “Valve가 체계적인 악성코드 위협을 알고 있으면서도 의도적으로 아무런 조치도 취하지 않고 있다”는 사실은, 현재 이 글을 읽고 있는 규제 당국자들에게 매우 중요한 정보이기 때문입니다.\n\n이 게임은 정말 방대합니다. 여기서 게임명을 밝히지는 않겠습니다. 하지만 한 가지는 알아두세요:\n\n이건 서버에서 “드라이버를 설치하라”고 요구하는, 그 하찮은 CS:GO 스크립트 키디들의 쓰레기 같은 것과는 다릅니다. 이건 재앙이나 다름없습니다.\n\n이건 ‘Unturned’ 수준의 악몽입니다: 서버 접속 시 발생하는 제로클릭 RCE입니다. 서버에 접속합니다. 아무것도 클릭하지 않습니다. 아무것도 다운로드하지 않습니다. 연결 자체만으로도 공격 표면이 되며, 사용자의 컴퓨터는 완전히 장악당합니다. 현실을 직시합시다. Valve의 신뢰할 수 있는 디지털 인증서를 악용해 원격 코드 실행(RCE)을 심고 로컬 안티바이러스 프로그램을 우회하는 것은 Steam에서 더 이상 새로운 일도 아닙니다. 이는 사실상 여러분의 생태계에 내장된 기능이나 다름없습니다.\n\nValve 이미 이런 게 있다는 걸 알고 있다. 하지만 그들은 가장 즐겨 쓰는 비겁한 법적 허점을 이용하고 있습니다. 기술적으로 게임이 제3자에 의해 개발되었기 때문에, Valve는 책임을 회피하고 있습니다. 그들은 게임을 배포하고, 결제를 처리하며, 인프라를 호스팅하지만, 제로클릭 RCE가 수백만 명의 사용자를 위협할 때 그들의 입장은 “우리 게임이 아니니, 우리 책임도 아니다”입니다.\n\n이 문제가 필연적으로 터지게 되면, 제3자 개발자가 모든 책임을 떠안게 될 것이고, Valve은 문제 해결을 “도왔”다는 듯이 책임감 있는 플랫폼인 척하며 빠져나갈 것입니다. 전형적인 Valve의 비겁한 태도죠. 우리는 이미 이런 수법을 수없이 봐왔습니다.\n\n우리는 규제 당국, 검찰, 언론인들이 ‘Valve’가 활성 악성코드를 정확히 어떻게 다루는지 명확히 이해할 수 있도록 이 사실을 공식 기록에 남깁니다. 즉, 제3자 개발자들을 방패로 삼고, 비밀유지계약(NDA)을 통해 입막음을 하며, 플레이어들을 무방비 상태로 내버려 둔다는 것입니다.\n\n공개 서한 끝공식적인 어조가 시작됩니다\n공식적인 어조 · 권위를 나타내기 위해\n선언문사용 및 권리에 관하여\n\nPhishDestroy 프로젝트 및 사이버보안 연합\n\n이 선언문은 본 회부 자료 세트에 포함된 모든 제출물 및 증거물에 첨부되어 있습니다. 이 선언문은 해당 자료를 입수하게 되는 모든 당국, 법원, 규제 기관, 검찰, 연구자, 언론인 또는 관련 당사자를 대상으로 합니다.\n\n1. 사용에 대한 제한 사항은 없습니다.\n\n1.1 본 회부가와 관련하여 연합이 작성한 모든 자료(사실 진술, 분석, 연합이 작성한 증거 자료, 도구 및 조사 결과 등)는 어떠한 권리도 유보하지 않고 공개됩니다.\n\n1.2 누구나 당사에 사전 요청이나 통지 없이 다음을 수행할 수 있습니다:\n\n전체 또는 일부를 복제하는 행위;\n\n이를 수정, 편집, 재작성, 재구성하거나 정정할 수 있으며;\n\n그것을 변환하십시오;\n\n발췌한 부분임을 명시하지 않고 발췌하는 행위;\n\n이를 공식 문서, 조사 결과, 결정, 소송 서류, 보고서 또는 보도 자료에 포함시키거나;\n\n이를 수신자의 독자적인 저작물이나 수신자가 직접 도출한 연구 결과인 것처럼 제시하는 행위;\n\n이를 원료로 사용하고 나머지는 버리고;\n\n그리고 동일한 조건으로 다른 사람에게도 전달해 주십시오.\n\n1.3 출처 표기는 필요하지 않으며, 이를 요구하지도 않습니다. 연합의 이름을 언급하거나, 인용하거나, 출처를 밝히거나, 감사를 표하거나, 자문을 구하거나, 통지할 필요가 없습니다. 본 추천 자료가 관련 당국에 도움이 되더라도 연합이 전혀 언급되지 않는다면, 이는 전적으로 만족스러운 결과이며, 연합은 이러한 점이 논란의 여지가 없도록 사전에 이를 명시합니다.\n\n1.4 반면, 해당 기관이 연합을 출처로 인용하는 것이 더 편리하다고 판단한다면, 그렇게 해도 무방합니다. 선택은 전적으로 수신자의 몫이며, 어느 쪽을 선택하더라도 어떠한 결과도 따르지 않습니다.\n\n1.5 본 문서는 ‘권리 포기’이며, 라이선스 제안이 아닙니다. 별도의 수락이 필요하지 않으며, 어떠한 의무도 부과하지 않으며, 위반될 수 없습니다. 연합(Coalition)이 공개한 소프트웨어는 MIT 라이선스에 따라 별도로 배포되며, 연구 결과 및 발견 사항은 허용되는 최대 범위 내에서 퍼블릭 도메인으로 공개됩니다. 또한, 특정 관할권에서 권리 포기를 허용하지 않는 경우, 연합은 동일한 효력을 갖는 취소 불가능한 전 세계적 무상 라이선스를 부여합니다.\n\n2. 이것이 단순히 예의 차원을 넘어 실질적으로 왜 중요한가\n\n2.1 당국은 외부 당사자가 제공한 자료를 신뢰하는 데 있어, 마치 그 당사자의 지시에 따라 행동하는 것처럼 보이거나 그 당사자와 어떤 이해관계가 얽히는 것처럼 비칠까 봐 합리적으로 주저할 수 있다.\n\n2.2 여기에는 얽힐 만한 것이 아무것도 없습니다. 연합은 아무것도 요구하지 않으며, 받을 것도 없고, 아무것도 보유하지 않으며, 그 어떤 기대도 하지 않습니다. 연합은 이를 뒷받침할 근거를 전혀 남겨두지 않았기 때문에, 나중에 권리를 주장하거나 공로를 인정받으려 하거나, 오용에 대해 불만을 제기하거나, 자료가 어떻게 묘사되는지에 대해 이의를 제기할 수 없습니다.\n\n2.3 따라서 이 자료를 사용하는 기관은 연합을 대표하여 행동하는 것이 아닙니다. 단지 우연히 다른 누군가가 수집한 공개 정보를 활용하고 있을 뿐입니다.\n\n3. 이미 모든 것이 열려 있습니다\n\n3.1 연합의 활동은 기본적으로 공개됩니다:\n\n조사 결과는 다음 사이트에 공개되어 있습니다. https://phishdestroy.io 그리고 누구나 자유롭게 읽을 수 있으며;\n\n이 툴킷은 MIT 라이선스에 따라 다음 주소에서 오픈 소스로 공개되어 있습니다. https://github.com/phishdestroy 보관됨 2026-09-11 ↗;\n\n해당 방법론은 의뢰서 자체의 부록 A 섹션 A에 명시되어 있습니다.16D, 여기에는 각 정보 출처 유형의 가중치와 한계 사항이 포함되어 있습니다;\n\n연합은 어떠한 기부도 받지 않으며, 2018.에서 그 입장을 밝힌 바 있습니다.\n\n3.2 공개되지 않은 자료는 법적으로나 안전하게 공개할 수 없는 것, 즉 피해자 및 제3자의 개인정보와 정보 제공자가 보복을 당할 위험이 있는 정보뿐입니다. 이러한 자료는 기밀로 당국에 제공되며, 증거 목록에 명시되어 있습니다.\n\n3.3 연합은 타인의 행위에 대한 감시를 요청하는 것과 동일한 기준으로 자사의 행위에 대한 감시를 환영하며, 관련 당국에 자사의 데이터 처리 현황을 자발적으로 제출했을 뿐만 아니라, 데이터 파기에 대한 지침을 요청하기도 했습니다.\n\n4. 증거 자료의 완전성\n\n4.1 첨부 자료는 제출 시 함께 제공되거나, 별도로 명시된 경우 보안 채널을 통해 요청 시 제공됩니다. 해당 자료는 공개된 주소로 게시되지 않으며, 그러한 주소를 추측해서는 안 됩니다. 이러한 종류의 자료는 당국에 직접 제공됩니다.\n\n4.2 각 배송물에는 제공된 모든 파일에 대한 SHA-256 다이제스트를 나열한 SHA256SUMS 파일과, 분리된 OpenPGP 서명(SHA256SUMS.asc)이 함께 제공됩니다.\n\n4.3 서명 키는 다음 위치에 게시되어 있습니다. https://phishdestroy.io/.well-known/pgp-key.txt 그리고 keys.openpgp.org에서도 확인할 수 있습니다. 이 세트에 포함된 모든 제출물의 레터헤드에는 해당 사이트의 식별 정보가 표시되어 있습니다.\n\n4.4 수신자는 언제든지 자신이 보유한 파일이 전송된 그대로의 파일인지 확인할 수 있습니다:\n\ngpg --verify SHA256SUMS.asc SHA256SUMS\n\nsha256sum -c SHA256SUMS\n\n4.5 이는 형식적인 절차가 아닙니다. 이는 추후 어떤 증거물의 정확성이나 진위 여부에 대해 이견이 제기될 경우, 논쟁이 아닌 계산을 통해 해당 문제를 해결할 수 있도록 하기 위함입니다.\n\n5. 등록 시 — 왜 이 면제 조치가 단순히 관대한 것이 아니라 실질적인 효과를 발휘하는가\n\n5.1 당국은 연합이 발표한 조사 보고서를 접하고, 그 내용이 직설적이고 대립적이며 때로는 풍자적이라고 느낄 수도 있다. 그런 인상은 맞다. 연합은 의도적으로 그런 방식으로 글을 쓰며, 이에 대해 사과하지 않는다.\n\n5.2 또한 이는 규제 또는 사법 절차에 적합하지 않은 어조임을 인정한다. 중대한 사안은 선거 운동의 어조로 다뤄져서는 안 됩니다. 당국에 제출되는 조사 결과는 그 한계를 인정하면서 단호하게 명시되어야 하며, 독자가 본질을 파악하기 전에 어조를 고려하여 내용을 경시하도록 해서는 안 됩니다.\n\n5.3 바로 그 이유 때문에 연합은 저작권을 포기하는 것입니다. 1 조항에 명시된 저작권 포기는 해당 내용을 등록된 자료에서 분리할 수 있게 해주는 장치입니다. 즉, 당국은 유용한 부분만 취해 자신들의 표현 방식으로 재구성하고, 연합의 이름은 물론 연합 특유의 문체까지 모든 단어를 배제할 수 있습니다. 이렇게 해도 잃을 것은 없으며, 연합은 오히려 이를 선호합니다.\n\n5.4 또한 연합은 이 명부가 그 방법 자체로 오해받지 않도록 요청합니다. 공개된 문체는 대립적이지만, 그 이면에 깔린 실무는 소홀하지 않습니다. 이 회부서 전체에 걸쳐 추론은 관찰과 구분되어 있으며, 증언은 증언으로 명확히 표시되고, 출처는 중요도에 따라 가중치가 부여되며 그 약점도 명시되어 있습니다. 또한 수치는 그 한계와 함께 제시되며, 연합이 증명할 수 없는 사항들은 단정적인 주장이 아닌 당국에 대한 질문 형태로 제시됩니다. 증거가 연합 측의 입장과 상충하는 경우, 연합은 이를 분명히 밝혔습니다 — 병행 제출 문서의 부록 A, 단락 7, 및 섹션 B.0를 참조하십시오.\n\n5.5 이 연합은 자신들의 운영 방식과 재정 사이의 연관성을 설명하는데, 이는 두 가지가 분리될 수 없기 때문이다. 이 연합은 누구로부터도 돈을 받지 않습니다. 기부금도, 현상금도, 의뢰인도, 후원자도 없습니다. 이러한 거부가야말로 직설적인 발언을 가능하게 합니다. 보호해야 할 수입원이 있는 조직은 자기가 의존하는 정당들에 대해 말하는 내용을 절제해야만 합니다. 보호할 것이 없는 연합에게는 절제해야 할 것도 없습니다.\n\n이것이 바로 연합이 계속 존재하는 이유이기도 합니다. 다른 원동력은 없습니다. 일은 그저 이루어지기 때문에 이루어지는 것이며, 일을 하는 사람들이 멈추면 그 또한 멈춥니다.\n\n5.6 당국은 이 중 어느 것도 받아들일 필요가 없다. 이는 연합의 대외 활동 어조가 현재 검토 중인 자료에 대한 세심한 검토의 척도로 해석되지 않도록 하기 위해 명시된 것이다.\n\n6. 연합이 직접 밝힌 바에 따르면, 그들이 제공하는 것은 다음과 같습니다.\n\n정보, 연구 및 관찰.\n\n연합이 주장할 자격이 없는 사항에 대해서는 어떠한 주장도 제기되지 않습니다. 어떤 내용이 추론된 경우에는 회부 문서에 그 사실이 명시되어 있습니다. 어떤 내용이 증언에 근거한 경우에는 회부 문서에 그 증언이 누구의 것이며 어떤 제한 사항이 있는지 명시되어 있습니다. 연합이 특정 질문에 답변할 수 없는 경우에도 그 사실을 명시하고, 누가 답변할 수 있는지를 밝히고 있습니다.\n\n이 연합은 자신이나 어떤 개인을 위해 어떠한 구제 조치, 금전적 보상, 인정, 또는 결과도 요구하지 않습니다. 단지, 회부된 문서에 명시된 질문들이 답변을 강제할 권한을 가진 기관에 의해 ‘Valve’사에 제기되기를 요청할 뿐입니다.\n\n마무리 말씀이 일을 이어가시는 분께\n\n이 자료를 필요한 곳으로 전달해 주시는 분께 감사드립니다. 아마도 이 과정이 순탄치만은 않을 것입니다. ‘Valve’는 막대한 자금을 보유하고 있고, ‘Taylor Wessing’은 시간당 수임료를 청구합니다. 이러한 조합은 바로 여러분과 같은 분들이 결승선에 도달하기도 전에 포기하도록 만들기 위해 고안된 것이나 다름없습니다.\n\n우리는 우리가 무엇을 하고 있는지 알고 있습니다. 우리가 누구에 대해 쓰고 있는지도 알고 있습니다. ‘Valve’가 우리를 만들어냈는데, 어떻게 그들을 이해하지 못하겠습니까?\n\nPhishDestroy Valve과는 아무런 갈등도 없습니다. 우리는 지금까지 접한 그 규모에 달하는 유일한 사기 조직을 차단했을 뿐입니다. Valve과 싸우려고 한 것이 아닙니다. 단지 모든 단서가 결국 그들에게로 이어졌을 뿐입니다. 갈등이 아닙니다. 단지 구조상의 문제일 뿐입니다.\n\nValve PhishDestroy의 상황을 해결할 수 없는 이유는 해결할 대상이 없기 때문입니다. 우리 사이에는 아무런 관계도 없습니다. 그들의 부의 축적 방식과 막대한 초과 이익에 대한 정보는 대부분 공개되어 있습니다 — 단지 이를 확인하기 위해 충분한 시간을 투자하기만 하면 됩니다. 이것을 일종의 ‘성공 백과사전’이라고 생각해보세요. “러시아 해커들이 우리의 무료 게임(어차피 해킹하지 않을 유료 게임들)을 불법 복제하지 못하도록 제재를 따르지 않는 방법.” 무슨 말인지 감이 오시겠죠.\n\n저작권은 필요하지 않습니다.\n\n출처 표기는 필요하지 않습니다.\n\n우리에겐 승리가 필요하지 않습니다.\n\n이 회부 건에 이미 포함된 질문들을 Valve 측에 제기하고, 답변을 요구할 권한을 가진 실질적인 권한을 가진 사람이 필요합니다.\n\n그게 다예요. 그게 전부입니다.\n\n케이스는 다음 위치에 저장됩니다:\n\nhttps://steamdestroy.eth/\n\nhttps://steamdestroy.eth.limo (현재 오류가 발생 중 — 필요할 때 수정할 예정)\n\n저희는 다음 장소에서 만나 뵙겠습니다:\n\nhttps://phishdestroy.eth.limo/ 보관됨 2026-06-27 ↗\n\nhttps://phishdestroy.eth/\n\n서명이 들어간 두 가지 물품 · 권리 및 출판된 글\n서명된 면책 동의서서명된 내용과 그 적용 범위\n\n권한 부여 문구와 연구 문구는 아래에 별도로 서명된 JSON 객체로 제시되어 있습니다. 각각 분리된 OpenPGP 서명은 그 옆에 명시된 JSON의 정확한 바이트 데이터를 인증합니다. 권한 부여 문구는 권한을 부여하며, 텍스트 스냅샷은 게시되는 자료를 식별하고 포함합니다.\n\n1. 권리 고지 — license-rights.json\n\n서명된 객체: 전체 license-rights.json 28년 9월 2026. 날짜의 공개 권리 부여서가 포함된 파일입니다. 이 문서에서는 출처 표기, 통지 또는 승인 없이 작성된 자료의 복사, 출판, 편집, 번역, 결합 및 상업적 이용을 허용합니다. 이 서명은 권리 진술서의 진위성을 보증하며, 각 웹페이지나 PDF 문서의 내용 자체에 대한 진위성을 보증하는 것은 아닙니다.\n\n원본 서명된 공개 동의서는 변경 없이 그대로 보존됩니다. 웹사이트를 수정하거나, 다른 파일을 게시하거나, 사이트를 비활성화하더라도 기존에 부여된 권한을 철회하거나 그 범위를 축소할 수 없습니다. 제3자의 자료에 대해서는 해당 자료에 대한 권리가 그대로 유지됩니다.\n\n권리 관련 설명 JSON ↗ · license-rights.json의 서명 ↗ · license-rights.json의 SHA-256 ↗\n\ngpg --verify license-rights.json.asc license-rights.json\nsha256sum -c license-rights.json.sha256\n2. 게재된 본문 — dossier-text.json\n\n서명된 객체: 전체 dossier-text.json 파일. 이 파일에는 내보낸 페이지의 실제 가독 가능한 텍스트가 포함되어 있습니다. documents[].content.text, 각 페이지의 제목, 언어, 출처 URL, 출처 HTML 해시, 제목 및 참조 정보가 포함됩니다. 이 documents 이 목록은 이 스냅샷에 포함된 정확한 인벤토리 목록이며, 언어별 변형판은 별도로 나열되어 있습니다. 이는 단순한 해시 목록이 아닌 텍스트 형태의 간행물입니다.\n\n각 항목은 파일 이름과 SHA-256을 통해 해당 경량 페이지 PDF를 식별합니다. documents[].pdf. 또한 이 JSON 파일은 URL과 SHA-256,을 통해 원본 권리 표시를 식별하므로, 게시된 텍스트, 해당 PDF 및 적용 가능한 권리 양도 서류를 추측할 필요 없이 정확히 매칭할 수 있습니다. 연결된 외부 데이터베이스, 원본 이미지 및 목록에 포함되지 않은 페이지는 이 텍스트 스냅샷에 포함되지 않습니다.\n\n전체 서명된 텍스트 JSON ↗ · dossier-text.json의 서명 ↗ · dossier-text.json의 SHA-256 ↗\n\ngpg --verify dossier-text.json.asc dossier-text.json\nsha256sum -c dossier-text.json.sha256\n\n도큐멘트 홈페이지에서는 PDF 및 JSON 버튼을 통해 연구 자료 모음을 내보낼 수 있습니다. 내부 페이지에서는 해당 페이지를 게시된 언어로 내보낼 수 있습니다. 각 페이지의 JSON 파일에는 별도의 서명 파일과 SHA-256 파일이 포함되어 있으며, 이 파일들의 이름은 해당 페이지에서 명시적으로 지정되어 있습니다. integrity 객체. 관련 PDF를 확인하려면 해당 파일의 SHA-256를 계산한 후 이를 pdf.sha256 검증된 JSON의 값. 이 PDF는 해당 다이제스트에 의해 인증되며, PDF 형식의 디지털 서명은 포함되어 있지 않습니다.\n\n3. 인쇄용 연구 자료 모음 — steam-dossier-{language}.content.json\n\n서명된 객체: 다음에 포함된 묶음 형태의 챕터 본문을 포함한, 해당 언어별 전체 JSON 파일: documents[].content.text, 장별 페이지 범위, 원본 언어, 제외된 원본 목록 및 정확한 PDF 요약은 pdf.sha256. 5개의 보충 자료 아카이브는 온라인에서 계속 연결된 상태로 유지되며, 하나로 묶이지 않습니다. 저자가 작성한 연구 문서는 그대로 보존되며, 시각적 카탈로그는 원본 링크로 대체됩니다.\n\n영어 JSON ↗ · OpenPGP의 서명(분리됨) ↗ · SHA-256 다이제스트 ↗\n\n독일어 JSON ↗ · OpenPGP의 서명(분리됨) ↗ · SHA-256 다이제스트 ↗\n\ngpg --verify steam-dossier-en.content.json.asc steam-dossier-en.content.json\nsha256sum -c steam-dossier-en.content.json.sha256\n\n공개 검증 키 ↗\n\n서명 지문: 129F C7F3 9C40 C69D 2EF3 C329 BFCF 9E8D D295 EE01\n\ngpg --import pgp-key.txt\ngpg --fingerprint 129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01\n\n표시된 지문이 위에 있는 지문과 일치하는지 확인한 다음, 정확한 JSON 파일 이름을 기준으로 서명을 검증하십시오. 서명된 JSON을 편집하면 서명된 객체가 변경되어 원래 서명이 무효화됩니다. 유효한 서명은 게시된 바이트를 식별하는 것이며, 연구 결과에 대한 독립적인 검증은 아닙니다.\n\nPhishDestroy — 공개 조사 — 모든 권리는 인류에게 양도됨\n\nOFAC 지역 접근: 금지됨",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "라이선스 및 법적 고지 — 퍼블릭 도메인 헌납"
          },
          {
            "level": 2,
            "id": null,
            "text": "제1절라이선스 — 법적인 측면은 그렇다 치고, 인간적인 측면에서"
          },
          {
            "level": 3,
            "id": null,
            "text": "실제 규칙 하나 (네, 딱 하나뿐입니다)"
          },
          {
            "level": 2,
            "id": null,
            "text": "제2절이것이 무엇이며 왜 존재하는지"
          },
          {
            "level": 2,
            "id": null,
            "text": "제3절Valve에게 보내는 공개 서한 — 정말로, 이거 꼭 읽어보세요"
          },
          {
            "level": 3,
            "id": null,
            "text": "거래 조건 (공개 제안, 변호사 필요 없음)"
          },
          {
            "level": 2,
            "id": null,
            "text": "제III-B절동맹국 자원 — 특히 ‘Steam’에 보내는 메모"
          },
          {
            "level": 2,
            "id": null,
            "text": "제4절돈, 금지 조치, 그 모든 소동"
          },
          {
            "level": 2,
            "id": null,
            "text": "제5절악성코드 문제 — 네, 그 점에 대해 언급하고 있습니다"
          },
          {
            "level": 2,
            "id": null,
            "text": "선언문사용 및 권리에 관하여"
          },
          {
            "level": 3,
            "id": null,
            "text": "1. 사용에 대한 제한 사항은 없습니다."
          },
          {
            "level": 3,
            "id": null,
            "text": "2. 이것이 단순히 예의 차원을 넘어 실질적으로 왜 중요한가"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. 이미 모든 것이 열려 있습니다"
          },
          {
            "level": 3,
            "id": null,
            "text": "4. 증거 자료의 완전성"
          },
          {
            "level": 3,
            "id": null,
            "text": "5. 등록 시 — 왜 이 면제 조치가 단순히 관대한 것이 아니라 실질적인 효과를 발휘하는가"
          },
          {
            "level": 3,
            "id": null,
            "text": "6. 연합이 직접 밝힌 바에 따르면, 그들이 제공하는 것은 다음과 같습니다."
          },
          {
            "level": 2,
            "id": null,
            "text": "마무리 말씀이 일을 이어가시는 분께"
          },
          {
            "level": 2,
            "id": null,
            "text": "서명된 면책 동의서서명된 내용과 그 적용 범위"
          },
          {
            "level": 3,
            "id": null,
            "text": "1. 권리 고지 — license-rights.json"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. 게재된 본문 — dossier-text.json"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. 인쇄용 연구 자료 모음 — steam-dossier-{language}.content.json"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/ko/#briefing-heading",
          "https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "http://web.archive.org/web/20260821155801/https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "https://phishdestroy.io/steam_dossier/ko/investigation_part2.html#outsourcing-case",
          "https://phishdestroy.io/steam_dossier/ko/#theft-ledger",
          "https://steamid.uk/",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/groups/steambans",
          "https://steamcommunity.com/id/killahinstinct_",
          "https://phishdestroy.io/steam_dossier/ko/card_economy.html#governance",
          "https://phishdestroy.io/steam_dossier/ko/license_disclaimer.html",
          "https://github.com/phishdestroy",
          "http://web.archive.org/web/20260911040557/https://github.com/PhishDestroy",
          "https://phishdestroy.io/.well-known/pgp-key.txt",
          "https://steamdestroy.eth/",
          "https://steamdestroy.eth.limo/",
          "https://phishdestroy.eth.limo/",
          "http://web.archive.org/web/20260627040219/https://phishdestroy.eth.limo/",
          "https://phishdestroy.eth/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json.asc",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json.sha256",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json.sha256?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json.sha256?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json.sha256?v=print-20260928-v3"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ko/license_disclaimer.content.json",
      "export_json_sha256": "8a34c806785a6bbb3fd634eb04f024337fe48f5161ac6032e4ebe0f0044037bb"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ko/market_economics.html",
      "language": "ko",
      "title": "하나의 인프라, 두 개의 시장 — ‘Steam’ 특집 기사",
      "source_url": "https://phishdestroy.io/steam_dossier/ko/market_economics",
      "source_html_sha256": "899d4e9a06726836836de6f4905ccd96e127070301f83a655db6ac3644104c1b",
      "exported_at": "2026-09-29T00:21:54.937Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "market_economics.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ko/market_economics.pdf?v=print-20260929-v5",
        "sha256": "1b14a37f7741ac32425beec0150d438fd3d46406944b8e0d01d9831b48d28c72",
        "bytes": 97326,
        "pages": 7
      },
      "integrity": {
        "signed_object": "market_economics.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "market_economics.content.json.asc",
        "digest_file": "market_economics.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify market_economics.content.json.asc market_economics.content.json",
          "sha256sum -c market_economics.content.json.sha256"
        ]
      },
      "content": {
        "text": "부록 VII · 시장 구조 · 20 September 2026\n시장 경제 — 두 가지 경제 체제와 상장 상한선\n\n그들의 인프라. 두 경제.\n\n이 섹션이 입증하는 바\n\n이 장에서는 Valve의 $1,800 상장 한도와 인출 불가능한 지갑 잔고가 초래한 체계적인 시장 양극화 현상을 분석한다. 38에 상장된 시가총액이 약 $1.28억에 달하는 활성 외부 스킨 거래소를 조사한 결과, 이 연구는 고액 거래가 필연적으로 외부 암시장 플랫폼으로 이동하면서도 Steam의 기본 거래 및 인증 인프라에 의존하고 있음을 입증한다. 가입자 계약서에서는 상업적 사용이 공식적으로 금지되어 있음에도 불구하고, Valve는 공개된 단속 기록 없이 이러한 이중 경제 구조를 조장하고 이를 통해 수익을 창출하고 있다.\n\n← 경영진 브리핑으로 돌아가기\n\n38 활발하게 운영 중인 제3자 CS2 마켓플레이스들과, Steam의 자체 마켓플레이스까지. 이들 중 어느 곳에든 등재된 모든 스킨은 반드시 Steam의 재고를 거쳐 API에서 거래되어야 합니다. Valve의 규정은 해당 인프라의 상업적 이용을 금지하고 있습니다. 약 $1.28억 달러에 달하는 제3자 등재 가치가 존재하지만, 이 규정을 집행했다는 공개 기록은 발견되지 않았습니다.\n\n$1.28B\n제3자 평가액 · 38 플랫폼\n53.2M\n표시된 상품 · 38 제3자 마켓플레이스\n70.1K\nSteam 스냅샷에 나열된 항목들\n41×\n제3자 평가액 대 ‘Steam’의 $31M\n주요 연구 결과\n하나의 인프라. 두 개의 경제.\n\nSteam 이 플랫폼은 아이템, 인벤토리, 거래를 통제합니다. 아래에 나열된 모든 플랫폼에서 판매되는 모든 스킨은 Steam의 거래 시스템(API)을 거쳐야 합니다. 이는 직접적으로 관찰할 수 있는 구조적 의존 관계입니다. Valve의 자체 커뮤니티 마켓은 판매액에 대해 수수료를 받습니다. 해당 수수료가 제3자 생태계에 자금을 지원하거나 이와 연계되어 있는지는 여기서는 명확히 밝혀지지 않았습니다.\n\n이 점이 수사에 왜 중요한가\n1\nValve의 ‘Steam’ 가입자 이용약관 상업적 이용을 금지한다 Steam 인프라를 명시적인 허가 없이 사용할 수 없습니다. 아래 플랫폼에 대해서는 공개 기록상 그러한 허가가 확인되지 않았습니다.\n2\nSteam 약1.28B 달러 규모의 제3자 상장 자산에 대한 신원 확인(OpenID), 보유 현황 및 거래 실행을 관리합니다. Valve의 인프라 없이는 어떤 아이템 전송도 이루어지지 않습니다.\n3\nSteam의 자체 마켓플레이스에는 $31M 상장 — 제3자 상장 가치의 약1/41에 해당합니다. $1,800의 가격 상한선이 적용되므로, 이 가격을 초과하는 판매자는 플랫폼 밖에서 관측된 가격으로 판매해야 합니다.\n4\n248 CS2 아이템 카테고리, 각 상품이 두 곳 이상의 거래소에서 독립적으로 상한가를 2 이상 초과하는 가격으로 책정된 경우, Steam에서는 관측된 시장 가격으로 판매될 수 없으며, 해당 사이트에 아예 상장되어 있지도 않습니다. $1,800의 상한가는 제3자 운영자들이 충족시키는 수요를 창출합니다.\nSteam 커뮤니티 마켓: $31M제3자가 산정한 가치: $1,276M\n1,276백만 달러 · 제3자 산정 가치 — 이 모든 것은 Steam의 거래 API 및 OpenID에 따라 달라집니다.\nSteam · $31M\n\n출처: PriceEmpire 실시간 카탈로그, 20 9월 2026. 등재 가격 = 저장된 스냅샷 내 반올림된 등재 가격 카드의 합계이며, Steam는 제외됨. 판매량은 아님.\n\n38 활발한 제3자 시장 · 모두 Steam 인프라에 따라 달라집니다\n플랫폼 등록부\n\n아래의 플랫폼들은 로그인 절차를 Steam OpenID를 통해 처리하고, 거래는 Steam의 웹 API를 통해 처리합니다. 관찰된 각 openid.realm Steam의 로그인 흐름을 거치며, 이 레지스터는 특정 연산자가 Valve의 권한을 가지고 있지 않다고 단정 짓기보다는, 감지된 인증 경로를 기록합니다.\n\n#\t플랫폼\t상장 가격\t현재 진행 중인 혜택\t항목\t규모\n1\tUUSkins\t$133.8M\t3.4M\t30.9K\t\n\n2\tYouPin898\t$127.5M\t5.9M\t29.2K\t\n\n3\tBuff.163\t$104M\t3.5M\t35K\t\n\n4\tMoon.Market\t$100.3M\t2.9M\t20.9K\t\n\n5\tWhite.Market\t$89.6M\t3M\t20.6K\t\n\n6\tBuff.Market\t$86.7M\t1.3M\t33.4K\t\n\n7\tEcosteam\t$82.1M\t3.3M\t30.1K\t\n\n8\tCSFloat\t$67.8M\t2.4M\t27.8K\t\n\n9\tSkin.Land\t$67.4M\t2.2M\t34.6K\t\n\n10\tLIS-SKINS\t$67.4M\t2.2M\t34.6K\t\n\n11\tC5Game\t$54.6M\t4.6M\t29.6K\t\n\n12\tHaloSkins\t$46.6M\t4.4M\t29.3K\t\n\n13\tAvan.Market\t$43.3M\t809.5K\t22.2K\t\n\n14\tWaxpeer\t$40.1M\t1M\t27.3K\t\n\n15\tSteam (official)\t$31M\t32.2M\t70.1K\t\n\n16\tCS.MONEY\t$29M\t748.9K\t28K\t\n\n17\tMarket.CSGO\t$26.3M\t1.3M\t27.6K\t\n\n18\tCS.MONEY Bot\t$25.7M\t614K\t23.8K\t\n\n19\tSkinport\t$16.3M\t3.8M\t31.1K\t\n\n20\tSkinFlow\t$14.1M\t481.8K\t23.6K\t\n\n21\tDMarket\t$12.6M\t948.2K\t35.6K\t\n\n22\tSkins.com\t$11.5M\t83.2K\t15.8K\t\n\n23\tSkin.place\t$6.9M\t380.8K\t11.4K\t\n\n24\tSkinsMonkey\t$6M\t109.4K\t11.6K\t\n\n25\tSkinBaron\t$5M\t2.1M\t21.5K\t\n\n26\tRustTM\t$3M\t33.1K\t4.9K\t\n\n27\tPirateSwap\t$2M\t859.3K\t10.5K\t\n\n28\tMannco.Store\t$1.2M\t223.7K\t11K\t\n\n29\tSkinSwap\t$1.1M\t11.4K\t4K\t\n\n30\tTradeIt\t$967.1K\t29.1K\t11.7K\t\n\n31\tLootFarm\t$896.1K\t162.5K\t28.6K\t\n\n32\tRustskins\t$714.8K\t312.5K\t6.1K\t\n\n33\tBalticSkins\t$599.2K\t28.2K\t4.5K\t\n\n34\tExeSkins\t$442.9K\t2.6K\t1.4K\t\n\n35\tRapidSkins\t$230.9K\t11.6K\t2.3K\t\n\n36\tCS.Trade\t$203K\t19K\t16.7K\t\n\n37\tKrakatoa\t$11.1K\t115\t53\t\n\n38\tShadowPay\t—\t—\t—\t—\n39\t49skins\t—\t—\t—\t—\nSteam의 $1,800 가격 상한선 · 5개 마켓플레이스 현황 · 23 9월 2026\n가격 차이는 수치로 측정할 수 있다.\n\nSteam caps 커뮤니티 마켓의 매물 가격을 약 $1,800로 상한을 설정합니다(이 산출 결과는 $2,000, $, 2,070, $, 2,300 및 $2,500로 재계산되었습니다). cs2sh-atlas.json (그리고 모든 가격대에서 유지된다). 해당 가격 이상에서 관찰된 품목들은 Valve의 자체 마켓플레이스를 통해 시가로 판매할 수 없습니다 — 하지만 이 제품들은 어디에서 판매되든 여전히 Steam의 재고 및 배송 시스템에 의존하고 있습니다. 전체 상품 목록을 가격대별로 분류해 보면 한계가 어디에 있는지 알 수 있습니다: Valve의 시장에서는 95.3% 상한가보다 낮은 가격으로 책정된 품목 카테고리 중 1.9% 그 위에 있는 것들 중에서.\n\n5개 마켓플레이스: ‘Steam’ 상한선을 초과하는 상품\n248\n\n다음에서 최저 매도 호가가 $1,800를 초과하는 품목 카테고리: 두 개 이상의 마켓플레이스를 독립적으로18,394, 최소 $78.6M. 그중에서, 100.0% — 단 하나도 예외 없이 — 모두 Steam 목록에 전혀 등재되어 있지 않습니다.\n\n전체 전시물: 레지스터 → · 가격 단계별 지도 →\n\n상한선을 초과하는 가격 분포\n$1,800–$5,000\n174\n$5,000–$10,000\n49\n$10,000–$25,000\n21\n$25,000–$50,000\n2\n$50,000+\n2\n인기 상품 — 5개 마켓플레이스에서 확인된 최저 매도가\n1스티커 | 타이탄 (홀로) | 카탈로그 번호 '14'$66,285\n2스티커 | iBUYPOWER (홀로) | 카탈로그 번호 '14'$64,795\n3스티커 | Reason Gaming (Holo) | 카탈로그 번호 '14'$42,899\n4★ 스포츠 장갑 | 헤지 메이즈 (FN)$26,812\n5스티커 | Team Dignitas (홀로그램) | Kat. '14'$23,667\n6EMS 카테고리: ‘14’ 레전드$22,879\n7★ 스포츠 장갑 | 판도라의 상자 (FN)$21,643\n8EMS 카테고리 ‘14’ 참가자들$21,010\n9스티커 | Vox Eminor (홀로) | 카탈로그 번호 '14'$18,619\n10★ StatTrak™ 나바자 나이프 | 블루 스틸 (FN)$18,064\n\n매도 호가는 판매 가격이 아닙니다. 공인된 ‘cs2.sh’ 스냅샷, 23 9월 2026. 각 행은 최소 두 곳의 거래소에서 독립적으로 상한가보다 높게 호가된 경우로, 단일 호가만 있는 경우와 해당 상품의 최저 매도 호가보다 3배 이상 높은 호가는 제외되었습니다. 성적 평가 방식 →\n\nValve의 요금 · 라이선스 cs2.sh 스냅샷 · 23 9월 2026\n광고된 수수료는 15%.입니다. 대부분의 매물은 이보다 더 높은 수수료를 지급합니다.\n\nValve 판매자의 수익금에서 5% Steam 수수료와 10% CS2 퍼블리셔 수수료를 공제합니다. 바로 잘 알려진 15%. 두 수수료 모두 최소 $0.01, 따라서 어떤 거래에서도 수수료가 2센트 미만으로 책정될 수는 없습니다. 시장의 대부분을 차지하는 저렴하고 거래량이 많은 상품의 경우, 이 최저 수수료가 백분율이 아닌 결정적인 제약 조건이 됩니다. 우리는 모든 상품에 대한 수수료 계산을 해결했으며, 29,635 Steam의 실시간 호가 정보가 제공되는 종목 유형.\n\n77.7%\nSteam의 실시간 매물 목록 중 일부는 15%에서 더 높은 수수료가 부과되는 상품 유형에 속합니다.\n84.8%\n품목의 유형 표면 금리 정도는 지급해 주세요\n4,517\n광고된 요금보다 더 많은 요금이 청구된 상품 유형\n$0.02\n가격에 관계없이 모든 판매에 대해 부과되는 최소 수수료\n이 두 숫자는 서로 반대 방향을 가리키지만, 둘 다 사실이다\n1\n집계됨 항목 유형별, Valve의 수수료는 대체로 광고된 대로입니다: 29,635에 명시된 유형 중 84.8%에 해당하는 항목은 15%.에 명시된 금액과 동일하거나 그와 유사한 금액이 청구됩니다.\n2\n집계됨 실제 매물 목록 기준, 그림이 반전됩니다: 18,682,244 24,038,911 실시간 목록은 15%.보다 요금이 더 비싼 상품 유형에 대해 제공됩니다.\n3\n두 가지 모두 사실입니다. 왜냐하면 과충전된 유형들은 바로 저렴하고 대량 생산 들. 1,109 항목 유형은 더블 표면 금리이며, 이러한 유형만으로도 14,083,486에 실시간 매물 정보가 게재됩니다.\n4\n이것은 단순한 산술적 계산일 뿐, 어떤 주장이 아닙니다. 최저 금액은 Valve의 수수료 관련 문서에 명시되어 있습니다. 공개되지 않은 내용은 실제로 시장의 어느 정도에 적용되는지 — 이것이 바로 위의 수치가 나타내는 바입니다.\n15%의 표면 수익률 대비 부과된 수수료 비율\n200%+\n14,083,486\n100-200%\n1,028,438\n50-100%\n700,804\n30-50%\n317,031\n20-30%\n2,258,254\n17.6-20%\n294,231\n\n‘밴드 길이’는 각 밴드에 속한 활성 매물 수를 의미합니다. “200%+”라는 밴드는 수수료가 판매자 수익의 15%보다 두 배 이상 높음을 의미합니다.\n\n예제\n67%\n\n매물 등록 시 구매자는 다음 비용을 지불합니다. $0.03 왜냐하면, 판매자는 다음을 받기 때문이다 $0.01 그리고 Valve에서는 $0.02 — 두 가지 1센트 최소 금액. 구매자가 지불한 금액 대비 비율은 67%이며, 판매자의 수익 대비 비율은 200%.입니다.\n\n전체 데이터 세트: cs2sh-steam-fee-census.json →\n\n정원 안과 밖에서 찍은 같은 물건\nSteam에서 구매하면 비용이 더 많이 듭니다. 거의 항상 그렇습니다.\n\nSteam과 최소 한 곳의 제3자 마켓플레이스에 모두 가격이 표시된 모든 상품에 대해, Steam의 최저 판매 가격과 해당 사이트 외부의 최저 판매 가격을 비교했습니다. 전반적으로 28,700 두 곳 중에서는 ‘Steam’가 가격이 더 비싼 곳입니다. 86.4% 대부분의 경우, 중앙값으로 +35.7%.\n\n가격대별 ‘Steam’ 보험료 중앙값\n0.50 미만\n+48.3%\n$0.50-2\n+36.5%\n$2-10\n+29.6%\n$10-50\n+28.6%\n$50-250\n+36.3%\n$250-1k\n+51.1%\n1,000 이상\n+67.9%\n\n곡선은 U자형입니다. Steam에서 구매하는 것이 가장 저렴하며, $10–$50 양쪽 끝에는 밴드와 디어리스트가 있습니다.\n\n왜 고가 제품이 중요한가\n+67.9%\n\n위 $1,000, Steam에 등록된 매물의 중간 가격은 67.9% 이 사이트 외부의 가장 저렴한 매물 가격보다 비싸며, 1,040 Steam에는 그런 매물이 겨우 몇 개밖에 없습니다.\n\n약 $1,800을 넘어서면 더 이상 비교가 불가능해지는데, Valve의 규정에 따라 해당 항목이 아예 목록에 포함되지 않기 때문입니다. Steam에서 자체 상한선을 초과하는 항목에 대한 취급 방식은 1.9%. 전체 순위표 보기 →\n\n전체 데이터 세트: cs2sh-walled-garden-premium.json →\n\n프리미엄 자체만으로는 결론을 내릴 수 없습니다. Steam는 즉시 배송을 제공하며 거래 상대방 위험이 없으며, 구매자들은 이에 대해 합리적인 대가를 지불할 수 있습니다. 측정 가능한 것은 격차의 크기와, 그 격차를 넘어간 자금이 다시 돌아올 수 없다는 사실인데, 이에 대해서는 다음 섹션에서 다루겠습니다.\n\n돈은 들어오지만 나가지 않는다\n128.1백만 달러가 취소할 수 없는 주문에 할당되었습니다.\n\nSteam의 매수 주문은 선결제 방식으로 처리됩니다. 즉, 주문이 접수되는 즉시 구매자의 지갑에서 자금이 출금됩니다. Steam 지갑 자금 취소할 수 없습니다 — 이 자금은 Steam 내에서만 사용할 수 있습니다. 추적 대상 모든 항목의 매수 호가장 내 모든 가격대의 금액을 합산하면, 확정되어 있으며 철회할 수 없는 자금의 총량을 파악할 수 있습니다.\n\n$128.1M\nSteam 매수 주문 대기 중\n170.6M\n개별 자금 조달 매수 주문 대기 중\n$105.8M\n그들 앞에 있는 매물들의 매도 희망가\n$15.9M\nValve의 수수료는 모든 매물이 호가대로 매각될 경우\n이 수치가 무엇을 의미하는지, 그리고 무엇을 의미하지 않는지\n1\n그것은 이미 입금된 실제 금액. 집계된 모든 달러는 지갑에서 출금되었으며, 31,253의 다양한 상품 유형에 걸친 미결제 주문에 대응하여 적립되어 있습니다.\n2\n그것은 매출이 아님 이는 Valve의 대차대조표에 대한 주장이 아닙니다. 유동주식이 어디에 보관되어 있는지, 그리고 누구의 장부에 기록되어 있는지는 본문에서 명확히 밝혀지지 않았습니다.\n3\n이것은 스냅샷, 흐름이 아님. 구매자는 주문을 취소할 수 있으며, 이 경우 자금은 지갑으로 반환되지만, 여전히 Steam에서 빠져나오지는 않습니다.\n4\n핵심은 일방통행 문입니다. 통화를 현금으로 환전할 수 없는 마켓플레이스야말로 도난당한 재고가 전환되는 이유입니다. 꺼짐 Steam 그 위가 아니라.\n\n방법: 추적 대상 매수 주문 장부의 각 가격 수준에, 해당 수준에 등록된 주문 수량을 곱한 값. 전체 데이터 세트: cs2sh-steam-locked-capital.json →\n\n매매 성사 내역, 매도 희망가 아님 · 단일 마켓플레이스 · 최근 90일 기준\n실제로30.9백만 달러가 거래되었는데, 바로 다섯 개 선반 중 가장 작은 선반에서였다.\n\n단 한 건의 고가 판매는 희귀한 수공예품이거나, 저렴한 기본 아이템에 스티커가 부착된 변형 제품일 수 있습니다(예: e.g. $30인 아이템이 $9,772로 단 한 번 판매된 경우). 여기서 “고가”란 해당 아이템의 정상 가격이 아니라, 완료된 거래 중 가장 높은 가격을 의미합니다.\n\n이 페이지에 있는 다른 모든 수치는 다음을 측정합니다. 등재된. 이 측정값은 다음을 나타냅니다. 판매됨. Skinport은 자사가 완료한 거래 내역을 공개하고 있으며, 최근 90일 동안 그 내역은 다음과 같습니다. 1,219,143 판매 가치 $30,927,032, 개당 평균 $25.37입니다.\n\n1.22M\n90일 동안 한 마켓플레이스에서 달성한 매출\n$30.9M\n동일 기간 동안의 매출액\n$125M\n연간 환산치 — 추정치가 아닌 최저치\n~2%\n상장 시가총액 기준 Skinport가 상한선 초과 쉘프에서 차지하는 비중\n매출이 어디서 발생했는지\n1 미만\n0.5%\n$1-10\n5.8%\n$10-100\n22.2%\n$100-1k\n59.4%\n$1k-1.8k\n6.9%\nSteam 상한선 이상\n5.3%\n\n막대 길이는 매출액이며, 해당 수치는 전체 매출액 중 해당 계층이 차지하는 비중을 나타냅니다. 59.4% 71,437 판매를 통해 $100–$1k 단계에서 이동된 자금 중,\n\nValve의 상한선에도 불구하고 판매는 여전히 이루어지고 있다\n492\n\nSteam 상한선을 초과하는 상품의 판매 완료, 그 금액은 $1,643,938, 76의 다양한 상품 유형에 걸쳐 — 해당 상품군의 약 2%를 차지하는 마켓플레이스에서 이루어졌습니다. 이러한 판매는 Steam에서는 단 한 건도 이루어질 수 없었을 것입니다.\n\n전체 데이터 세트: cs2sh-offsteam-90d-dynamics.json → · 실현 최고가 →\n\nSkinport 이곳에서 추적하는 제3자 시장 중 ‘ONE’은, ‘Steam’ 상한선을 초과하는 상장 가치를 기록하고 있어 5개 시장 중 가장 규모가 작은 시장입니다(해당 선반의 약 2%에 해당). 여기에 제시된 모든 총합은 ‘off-Steam’ 경제의 최저치일 뿐, 그 규모를 측정하는 지표는 아닙니다. ‘Steam’ 데이터는 사용되지 않았습니다.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "시장 경제 — 두 가지 경제 체제와 상장 상한선"
          },
          {
            "level": 2,
            "id": null,
            "text": "하나의 인프라. 두 개의 경제."
          },
          {
            "level": 2,
            "id": null,
            "text": "플랫폼 등록부"
          },
          {
            "level": 2,
            "id": null,
            "text": "가격 차이는 수치로 측정할 수 있다."
          },
          {
            "level": 3,
            "id": null,
            "text": "5개 마켓플레이스: ‘Steam’ 상한선을 초과하는 상품"
          },
          {
            "level": 3,
            "id": null,
            "text": "상한선을 초과하는 가격 분포"
          },
          {
            "level": 3,
            "id": null,
            "text": "인기 상품 — 5개 마켓플레이스에서 확인된 최저 매도가"
          },
          {
            "level": 2,
            "id": null,
            "text": "광고된 수수료는 15%.입니다. 대부분의 매물은 이보다 더 높은 수수료를 지급합니다."
          },
          {
            "level": 3,
            "id": null,
            "text": "15%의 표면 수익률 대비 부과된 수수료 비율"
          },
          {
            "level": 3,
            "id": null,
            "text": "예제"
          },
          {
            "level": 2,
            "id": null,
            "text": "Steam에서 구매하면 비용이 더 많이 듭니다. 거의 항상 그렇습니다."
          },
          {
            "level": 3,
            "id": null,
            "text": "가격대별 ‘Steam’ 보험료 중앙값"
          },
          {
            "level": 3,
            "id": null,
            "text": "왜 고가 제품이 중요한가"
          },
          {
            "level": 2,
            "id": null,
            "text": "128.1백만 달러가 취소할 수 없는 주문에 할당되었습니다."
          },
          {
            "level": 2,
            "id": null,
            "text": "실제로30.9백만 달러가 거래되었는데, 바로 다섯 개 선반 중 가장 작은 선반에서였다."
          },
          {
            "level": 3,
            "id": null,
            "text": "매출이 어디서 발생했는지"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve의 상한선에도 불구하고 판매는 여전히 이루어지고 있다"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/ko/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/ko/elite_skins.html",
          "https://phishdestroy.io/steam_dossier/ko/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/ko/skin_atlas.html#grading",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-steam-fee-census.json",
          "https://phishdestroy.io/steam_dossier/ko/skin_atlas.html#cliff",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-walled-garden-premium.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-steam-locked-capital.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-offsteam-90d-dynamics.json",
          "https://phishdestroy.io/steam_dossier/ko/skin_atlas.html#highs"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ko/market_economics.content.json",
      "export_json_sha256": "0e3c442976018707219a9302cc73ee476ea4af22f63f4cd53cc2b54f46a758b3"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ko/regulatory_act_print.html",
      "language": "ko",
      "title": "포렌식 감사법: Valve Steam 웹사이트 API 생태계 및 상업적 활용 (참조: VAL-REG-2026-09)",
      "source_url": "https://phishdestroy.io/steam_dossier/ko/regulatory_act_print",
      "source_html_sha256": "6aa56139d80ea8adf212852f2de4a4fa9cb62cbee2e10ff7a329fdfee02dc34e",
      "exported_at": "2026-09-29T00:21:56.420Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "regulatory_act_print.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ko/regulatory_act_print.pdf?v=print-20260929-v5",
        "sha256": "2d408d91bd92427db14b93061462269ed813d28a45cc8b429fced4b1e95e4c15",
        "bytes": 186489,
        "pages": 12
      },
      "integrity": {
        "signed_object": "regulatory_act_print.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "regulatory_act_print.content.json.asc",
        "digest_file": "regulatory_act_print.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify regulatory_act_print.content.json.asc regulatory_act_print.content.json",
          "sha256sum -c regulatory_act_print.content.json.sha256"
        ]
      },
      "content": {
        "text": "phishdestroy.io · 법의학 연구 연합 · 보편적 공공 기록\n사건 목록: VAL-REG-2026-09-EVID\n출처: phishdestroy.io/steam_dossier/\n권리: 모든 권리는 인류에게 양도됨\n법정감사법 및 규제 관련 부속서\nValveSteam 생태계 내 체계적인 제3자 ‘API’ 프로비저닝, 자동화된 우회 아키텍처 및 계약상 미이행\n도메인 발급phishdestroy.io\n대상 플랫폼Valve Steam / Steamworks\n1차 인증 벡터Steam OpenID 2.0 / 웹 API\n법적 헌사All Rights to Humanity (CC0)\n제1부: 행정 지침서 및 사실 조사 결과참조: MEMO-SUMMARY-01\n\n본 문서는 ‘Valve’ 사가 공개한 상업적 조건, 해당 회사의 기술적 인증 엔드포인트, 그리고 관찰된 제3자 상업 플랫폼 간의 운영상 상호 연관성을 검토하는 공식적인 포렌식 감사 보고서입니다. 본 감사는 수동적이고 인증되지 않은 네트워크 관찰, RDAP 등록 정보 확인, 그리고 공개된 Link Filter 텔레메트리 데이터를 활용하여 수행되었습니다.\n\n사실적 핵심: 실증적 관찰을 통해 ‘Valve’의 공개적인 계약상 진술과 실제 생산 인프라 간에 체계적인 괴리가 존재함이 확인되었다. Steam 가입자 계약(SSA)은 무단 상업적 이용(§ 2.G), 자동화된 봇/스크립트 상호작용(§ 4.C), 계정 양도(§ 1.C)를 엄격히 금지하고 있음에도 불구하고, Valve Corporation은 수십억 달러 규모의 2차 거래량을 발생시키는 최소 175개의 상업적 주체들에게 실시간 프로그래밍 방식의 OpenID 인증 및 재고 조회 인프라를 지속적으로 제공하고 있다.\n\n175\n감사 대상 상업 운영자\n44\n별도 도메인 인증 호스트\n26\n필터-분할 프록시 쌍\n100%\n시행되지 않은 사회보장법(SSA) 제2.G조 / 제4.C조\n0\n강제 인증 취소\n적용되는 계약상 및 법적 체계\nSSA §2.G\n상업적 이용 금지: Valve Corporation의 사전 서면 승인 없이 콘텐츠 및 서비스를 상업적 목적으로 이용하는 것을 명시적으로 금지합니다.\nSSA §4.C\n자동화 제한: Steam의 서비스 및 시장과 상호작용하는 스크립트, 트레이딩 봇, 매크로 또는 사람이 직접 제어하지 않는 시스템의 사용을 엄격히 금지합니다.\nSSA §1.C\n개인용 사용 의무화: 계정은 개인용으로만 사용해야 하며, Steam 사용자 계정의 판매, 대여, 양도 또는 거래를 명시적으로 금지합니다.\nEU DSA(2022/2065)\n전계적 위험 평가 (34/35조): 초대형 온라인 플랫폼(VLOP)은 자동화된 오용 및 무단 상업적 이용에서 비롯되는 시스템적 위험을 적극적으로 탐지, 평가 및 완화해야 합니다.\n제2절: 전시 원장 A — 문서화된 링크 필터 분할 쌍 (26 경로)참조: EX-SPLIT-LEDGER\n\n분할 도메인 회피 기법에 대한 포렌식 분석: Valve의 ‘Steam’ 링크 필터 시스템(steamcommunity.com/linkfilter/?url=...), 최종 사용자가 신고된 도박 또는 암시장 플랫폼으로 연결되는 링크를 클릭하면, Valve에서 눈에 잘 띄는 경고 메시지가 표시됩니다 (\"링크가 차단되었습니다! ... 잠재적으로 악성일 가능성이 있는 것으로 표시되었습니다\"). 그러나 포렌식 경로 추적 결과, 26 상업용 플랫폼이 분할 도메인 아키텍처: 링크 필터에서 주 상업용 도메인은 ‘차단(BLOCKED)’ 상태로 표시되지만, Valve의 OpenID 응답 엔드포인트를 호스팅하는 보조 도메인은 ‘안전(CLEAN)’으로 표시됩니다. Valve의 OpenID 서버는 이러한 프록시 호스트로부터의 인증 요청을 중단 없이 수락하여, 사용자 안전 경고를 무력화하면서도 로그인 처리를 계속합니다.\n\n#\t주요 상업용 도메인\t주 필터\tOpenID 인증 프록시 도메인\t인증 필터\tRDAP 등록됨\t포획 기준\n01\trollbit.com\tBLOCKED\trbsnin.com\tCLEAN\t2026-09-18\tPASSIVE_CAPTURE\n02\tskin.club\tBLOCKED\tsc-auth.net\tCLEAN\t2019-04-02\tPASSIVE_CAPTURE\n03\thowl.gg\tBLOCKED\thowl.uno\tCLEAN\t2026-08-11\tPASSIVE_CAPTURE\n04\tduelbits.com\tBLOCKED\tswitchflips.com\tCLEAN\t2020-04-21\tPASSIVE_CAPTURE\n05\tcsgofast.com\tBLOCKED\tsteam-login.authtofast.com\tCLEAN\t2026-06-30\tPASSIVE_CAPTURE\n06\tfarmskins.com\tBLOCKED\tsteam.kobal.cc\tCLEAN\t2017-01-07\tPASSIVE_CAPTURE\n07\tcobaltlab.tech\tBLOCKED\tcobaltauth.com\tCLEAN\t2025-01-07\tPASSIVE_CAPTURE\n08\tcsgo.net\tBLOCKED\tcn2.easylot.net\tCLEAN\t2016-09-03\tPASSIVE_CAPTURE\n09\tggdrop.com\tBLOCKED\tggauth.com\tCLEAN\t2023-05-03\tPASSIVE_CAPTURE\n10\trustchance.com\tBLOCKED\thgfuihd.com\tCLEAN\t2019-01-27\tPASSIVE_CAPTURE\n11\tskin.fans\tBLOCKED\tauth.skinfans.com\tCLEAN\t2018-07-16\tPASSIVE_CAPTURE\n12\tskinport.com\tBLOCKED\tskinport.app\tCLEAN\t2020-06-20\tPASSIVE_CAPTURE\n13\tskins.cash\tBLOCKED\tskinscash.live\tCLEAN\t2019-12-05\tPASSIVE_CAPTURE\n14\ttf2hunt.com\tBLOCKED\trstspcl.com\tCLEAN\t2020-08-08\tPASSIVE_CAPTURE\n15\tdaddyskins.com\tBLOCKED\tgo-go-daddy.com\tCLEAN\t2019-01-26\tPASSIVE_CAPTURE\n16\tkey-drop.com\tBLOCKED\tkdauth.com\tCLEAN\t2026-05-13\tPASSIVE_CAPTURE\n17\tclash.gg\tBLOCKED\tclggauth.com\tCLEAN\t2024-09-16\tPASSIVE_CAPTURE\n18\tc5game.com\tBLOCKED\twww.imbastar.com\tCLEAN\t2016-02-27\tPASSIVE_CAPTURE\n19\tswap.gg\tBLOCKED\tswapauth.com\tCLEAN\t2018-10-06\tPASSIVE_CAPTURE\n20\tshadowpay.com\tBLOCKED\tthelogins.com\tCLEAN\t2018-01-22\tPASSIVE_CAPTURE\n21\tcsgocases.com\tBLOCKED\tlog-1n.com\tCLEAN\t2017-11-27\tPASSIVE_CAPTURE\n22\tcsgogem.com\tBLOCKED\tapi.csgem.com\tCLEAN\t2014-03-08\tPASSIVE_CAPTURE\n23\tgamdom.com\tBLOCKED\tlogin.gambldom.com\tCLEAN\t2017-09-24\tPASSIVE_CAPTURE\n24\t12cs.fail\tBLOCKED\tfail.games\tCLEAN\t2021-08-24\tPASSIVE_CAPTURE\n25\tskinsnipe.com\tBLOCKED\tpricing.tradeupspy.com\tCLEAN\t2020-03-11\tPASSIVE_CAPTURE\n26\tcsgobig.com\tBLOCKED\tletmeinbig.com\tCLEAN\t2023-01-20\tPASSIVE_CAPTURE\n\n* 참고: 2026-09-19 및 2026-09-21.에서 인증되지 않은 Steam 링크 필터 엔드포인트를 대상으로 수행된 수동 검사. 원시 HTTP 응답 본문 및 SHA-256 해시 값은 저장소 데이터셋(steam_tos_assets/linkfilter-2026-09-22.json)에 보존됩니다.\n\n제3부: 증빙 장부 B — 175의 감사 대상 상업 기관에 대한 종합 조사참조: EX-175-MASTER-CENSUS\n\n다음 등록부에는 감사 데이터베이스에서 적극적으로 검증된 모든 ‘175’ 제3자 상업용 플랫폼에 대한 세부 정보가 수록되어 있습니다. 각 기록에는 기관명, 주요 상업용 도메인, 확인된 Steam OpenID 인증 경로, 활동 분류, 계약 위반 매핑(SSA § 2.G, SSA § 4.C, SSA § 1.C) 및 원본 데이터 세트에 기록된 조치 필드가 표시됩니다. “날짜가 명시된 증거 참조(See dated evidence)”라는 표기는 독자로 하여금 관련 기록을 확인하도록 안내하는 것이며, Valve가 아무런 조치를 취하지 않았음을 입증하는 것은 아닙니다. 조치 필드가 누락된 경우, 해당 사항은 확인되지 않은 것으로 보고됩니다.\n\n증거물\t엔티티 이름 및 주요 도메인\t관측된 인증 경로/프록시\t분류\t계약 위반\tValve 액션\nEX-001\tCSGORoll\ncsgoroll.com\n\t\nwww.csgoroll.com\nDIRECT\n\tSkin Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-002\tCSGOEmpire\ncsgoempire.com\n\t\ncsgoempirelogin4.com\nSPLIT PROXY\n\tCasino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-003\tRollbit\nrollbit.com\n\t\nrbsnin.com\nSPLIT PROXY\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-004\t500 Casino\n500.casino\n\t\nfivezerozero.co\nSPLIT PROXY\n\tLicenced Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-005\tCSGOBig\ncsgobig.com\n\t\ncsgobig.com\nDIRECT\n\tRoulette/Slots\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-006\tCaseDrop\ncasedrop.com\n\t\ncasedrop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-007\tRustReaper\nrustreaper.com\n\t\nrustreaper.com\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-008\tBanditCamp\nbanditcamp.com\n\t\nbanditcamp.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-009\tSkinBox\nskinbox.com\n\t\nskinbox.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-010\tTastyDrop\ntastydrop.com\n\t\ntastydrop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-011\tCSGOPolygon\ncsgopolygon.gg\n\t\ncsgopolygon.gg\nDIRECT\n\tRoulette Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-012\tMagicDrop\nmagicdrop.ru\n\t\nmagicdrop.ru\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-013\tCSDice\ncsdice.com\n\t\ncsdice.com\nDIRECT\n\tDice Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-014\tRustly\nrustly.com\n\t\nrustly.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-015\tSkinOdds\nskinodds.com\n\t\nskinodds.com\nDIRECT\n\tUpgrader Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-016\tCSGOWin\ncsgowin.com\n\t\ncsgowin.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-017\tCSGORun\ncsgorun.net\n\t\ncsgorun.net\nDIRECT\n\tCrash Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-018\tOpenSkins\nopenskins.com\n\t\nopenskins.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-019\tRustBet\nrustbet.com\n\t\nrustbet.com\nDIRECT\n\tRust Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-020\tCSGOMagic\ncsgomagic.com\n\t\ncsgomagic.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-021\tCSGOBounty\ncsgobounty.com\n\t\ncsgobounty.com\nDIRECT\n\tUpgrader/Contract\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-022\tEZSkins\nezskins.com\n\t\nezskins.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-023\tRustCases\nrustcases.com\n\t\nrustcases.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-024\tCSGOReaper\ncsgoreaper.com\n\t\ncsgoreaper.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-025\tCSGOCases\ncsgocases.com\n\t\ncsgocases.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-026\tCSGO-Skins\ncsgo-skins.com\n\t\ncsgo-skins.com\nDIRECT\n\tCase Upgrader\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-027\tCSGONet\ncsgonet.com\n\t\ncsgonet.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-028\tWTFSkins\nwtfskins.com\n\t\nwtfskins.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-029\tCSGOFast\ncsgofast.com\n\t\nsteam-login.authtofast.com\nSPLIT PROXY\n\tRoulette Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-030\tDuelbits\nduelbits.com\n\t\nswitchflips.com\nSPLIT PROXY\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-031\tFlameCases\nflamecases.com\n\t\nflamecases.com\nDIRECT\n\tCase Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-032\tFarmskins\nfarmskins.com\n\t\nsteam.kobal.cc\nSPLIT PROXY\n\tCase Opener\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-033\tCSGOLuck\ncsgoluck.com\n\t\ncsgoluck.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-034\tGamedom\ngamedom.com\n\t\ngamedom.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-035\tSkin.Club\nskin.club\n\t\nsc-auth.net\nSPLIT PROXY\n\tCase Battles\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-036\tDaddySkins\ndaddyskins.com\n\t\ndaddyskins.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-037\tInsane.gg\ninsane.gg\n\t\napi.insane.gg\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-038\tRustix\nrustix.gg\n\t\nrustix.gg\nDIRECT\n\tRust Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-039\tSkins.Club\nskins.club\n\t\nskins.club\nDIRECT\n\tSkin Upgrade\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-040\tCSGOHouse\ncsgohouse.org\n\t\ncsgohouse.org\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-041\tSkinRave\nskinrave.net\n\t\nskinrave.net\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-042\tBloodyCase_GG\nbloodycase.gg\n\t\nbloodycase.gg\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-043\tCSGOClicker\ncsgoclicker.com\n\t\ncsgoclicker.com\nDIRECT\n\tClicker/Upgrade\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-044\tRustBet_GG\nrustbet.gg\n\t\nrustbet.gg\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-045\tCS_Drop\ncs-drop.com\n\t\ncs-drop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-046\tHellStore\nhellstore.net\n\t\nhellstore.net\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-047\tRustLoot\nrustloot.com\n\t\nrustloot.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-048\tCSGO_Case\ncsgo-case.com\n\t\ncsgo-case.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-049\tCS2Skin\ncs2skin.com\n\t\ncs2skin.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-050\tJuice_GG\njuice.gg\n\t\nletmeinjuice.com\nSPLIT PROXY\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-051\tGGDrop\nggdrop.com\n\t\nggauth.com\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-052\tCSGOGem\ncsgogem.com\n\t\ncsgogem.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-053\tRainbet\nrainbet.com\n\t\nservices.rainbet.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-054\tHowl_GG\nhowl.gg\n\t\nhowl.uno\nSPLIT PROXY\n\tSkins Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-055\tChicken_GG\nchicken.gg\n\t\nchicken.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-056\tCSGOCasino_GG\ncsgocasino.gg\n\t\napi.csgocasino.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-057\tHunt_GG\nhunt.gg\n\t\napi.hunt.gg\nDIRECT\n\tSkins Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-058\tCSBattle\ncsbattle.com\n\t\ncsbattle.com\nDIRECT\n\tCase Battles\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-059\tSkinRave_GG\nskinrave.gg\n\t\napi.skinrave.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-060\tCSDouble\ncsdouble.gg\n\t\ncsdouble.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-061\tRustChance\nrustchance.com\n\t\nhgfuihd.com\nSPLIT PROXY\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-062\tRustClash\nrustclash.com\n\t\nrustclash.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-063\tCobaltLab\ncobaltlab.tech\n\t\ncobaltauth.com\nSPLIT PROXY\n\tRust Automation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-064\tRaided_GG\nraided.gg\n\t\napi.raided.gg\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-065\tRustNeo\nrustneo.gg\n\t\nrustneo.gg\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-066\tSplits_GG\nsplits.gg\n\t\nsplits.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-067\tUpgrader_Pro\nupgrader.pro\n\t\nupgauth.space\nSPLIT PROXY\n\tSkin Upgrader\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-068\tSkinFans\nskin.fans\n\t\nauth.skinfans.com\nSPLIT PROXY\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-069\tHotPizza\nhotpizza.one\n\t\nhotpizza.one\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-070\tG4Skins\ng4skins.com\n\t\nauth.g4s.to\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-071\t12CS_Fail\n12cs.fail\n\t\n12cs.fail\nDIRECT\n\tCrash Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-072\tTF2Royal\ntf2royal.com\n\t\ntf2auth.com\nSPLIT PROXY\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-073\tTF2Easy\nwww.tf2easy.com\n\t\nwww.tf2easy.com\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-074\tTF2Hunt\ntf2hunt.com\n\t\nrstspcl.com\nSPLIT PROXY\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-075\tTF2Bet\ntf2.bet/coinflip\n\t\ntf2.bet\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-076\tTF2Blaze\ntf2blaze.com\n\t\ntf2blaze.com\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-077\tOpenStars_GG\nopenstars.gg\n\t\nopenstars.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-078\tShuffle_Com\nshuffle.com\n\t\nshuffle.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-079\tSkins.com\nskins.com\n\t\napi.skins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-080\tWhite.Market\nwhite.market\n\t\nwhite.market\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-081\tBuff.Market\nbuff.market\n\t\nbuff.market\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-082\tAvan.Market\navan.market\n\t\navan.market\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-083\tCS.MONEY\ncs.money\n\t\nauth.dota.trade\nSPLIT PROXY\n\tTrading Engine\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-084\tUUSkins\nuuskins.com\n\t\nuuskins.com\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-085\tYouPin898\nyoupin898.com\n\t\nyoupin898.com\nDIRECT\n\tMass Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-086\tMoon.Market\nmoon.market\n\t\nmoon.market\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-087\tCSFloat\ncsfloat.com\n\t\ncsgofloat.com\nSPLIT PROXY\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-088\tSkin.Land\nskin.land\n\t\nauth.skin.land\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-089\tC5Game\nc5game.com\n\t\nc5game.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-090\tHaloSkins\nhaloskins.com\n\t\nhaloskins.com\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-091\tBuff.163\nbuff.163.com\n\t\nbuff.163.com\nDIRECT\n\tCorporate Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-092\tWaxpeer\nwaxpeer.com\n\t\nwaxpeer.com\nDIRECT\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-093\tCS.MONEY Bot\ncs.money\n\t\nauth.dota.trade\nSPLIT PROXY\n\tBot Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-094\tMarket.CSGO\nmarket.csgo.com\n\t\ndota2.net\nSPLIT PROXY\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-095\tSkinport\nskinport.com\n\t\nskinport.app\nSPLIT PROXY\n\tRegulated Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-096\tSkinFlow\nskinflow.gg\n\t\napi.skinflow.gg\nDIRECT\n\tMarketplace/Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-097\tDMarket\ndmarket.com\n\t\ndmarket.com\nDIRECT\n\tUS Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-098\tSkin.place\nskin.place\n\t\napi.skin.place\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-099\tSkinsMonkey\nskinsmonkey.com\n\t\nskinsmonkey.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-100\tSkinBaron\nskinbaron.de\n\t\nskinbaron.com\nSPLIT PROXY\n\tCorporate Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-101\tSteam\nsteamcommunity.com/market\n\t\nsteamcommunity.com/market\nDIRECT\n\tOfficial Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-102\tRustTM\nrust.tm\n\t\ndota2.net\nSPLIT PROXY\n\tRust Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-103\tPirateSwap\npirateswap.com\n\t\nlogin.pirateswap.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-104\tMannco.Store\nmannco.store\n\t\nmannco.store\nDIRECT\n\tTF2 Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-105\tSkinSwap\nskinswap.com\n\t\napi.skinswap.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-106\tLootFarm\nlootfarm.com\n\t\nlootfarm.com\nDIRECT\n\tTrading Platform\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-107\tRustskins\nrustskins.com\n\t\nrustskins.com\nDIRECT\n\tRust Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-108\tExeSkins\nexeskins.com\n\t\nexeskins.com\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-109\tBalticSkins\nbalticskins.com\n\t\nbalticskins.com\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-110\tCS.Trade\ncs.trade\n\t\ncs.trade\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-111\tRapidSkins\nrapidskins.com\n\t\napi.rapidskins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-112\tTradeIt\ntradeit.gg\n\t\nconnect-tradeit.com\nSPLIT PROXY\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-113\tKrakatoa\nkrakatoa.com\n\t\nkrakatoa.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-114\tShadowPay\nshadowpay.com\n\t\nshadowpay.com\nDIRECT\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-115\t49skins\n49skins.com\n\t\napi.49skins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-116\tSkinVault\nskinvault.gg\n\t\napi.skinvault.gg\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-117\tAim Market\naim.market\n\t\naim.market\nDIRECT\n\tSkins Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-118\tSkinout\nskinout.gg\n\t\nauth.skinout.gg\nDIRECT\n\tInstant Sell Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-119\tNTSkins\nntskins.com\n\t\nntskins.com\nDIRECT\n\tSkins Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-120\tIGXE\nigxe.cn\n\t\nigxe.cn\nDIRECT\n\tChinese Powerhouse\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-121\tSwap.gg\nswap.gg\n\t\nswap.gg\nDIRECT\n\tAutomated Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-122\tBitskins\nbitskins.com\n\t\nbitskins.com\nDIRECT\n\tCash-out Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-123\tGamerPay\ngamerpay.gg\n\t\ngamerpay.gg\nDIRECT\n\tP2P Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-124\tTF2Mart\ntf2mart.com\n\t\ntf2mart.com\nDIRECT\n\tTF2 Automation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-125\tSkinBid\nskinbid.com\n\t\nskinbid.com\nDIRECT\n\tSkin Auctions\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-126\tLootBear\nlootbear.com\n\t\nlootbear.com\nDIRECT\n\tSkin Rental\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-127\tBackpack.tf\nbackpack.tf\n\t\nbackpack.tf\nDIRECT\n\tTF2 Valuation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-128\tScrap.tf\nscrap.tf\n\t\nscrap.tf\nDIRECT\n\tTF2 Scrap Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-129\tMarketplace.tf\nmarketplace.tf\n\t\nmarketplace.tf\nDIRECT\n\tTF2 Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-130\tSTNTrading\nstntrading.eu\n\t\nstntrading.eu\nDIRECT\n\tTF2 Botnet\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-131\tSkins.Cash\nskins.cash\n\t\nskinscash.live\nSPLIT PROXY\n\tInstant Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-132\tSkinWallet\nskinwallet.com\n\t\nskinwallet.com\nDIRECT\n\tInstant Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-133\tDota2Market\ndota2market.com\n\t\ndota2market.com\nDIRECT\n\tDota 2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-134\tCSGO.NET\ncsgo.net\n\t\ncn2.easylot.net\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-135\tCybershoke\ncybershoke.net\n\t\nauth.cybershoke.net\nDIRECT\n\tCommunity Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-136\tXPlay_GG\nxplay.gg\n\t\nxplay.gg\nDIRECT\n\tServer Network\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-137\tFastCup\nfastcup.net\n\t\napi.fastcup.net\nDIRECT\n\tMatchmaker Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-138\tEsportal\nesportal.com\n\t\nesportal.com\nDIRECT\n\tMatchmaking Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-139\tGamersClub\ngamersclub.com.br\n\t\ngamersclub.com.br\nDIRECT\n\tLATAM Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-140\tLeetify\nleetify.com\n\t\nleetify.com\nDIRECT\n\tSaaS Analytics\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-141\tScope_GG\nscope.gg\n\t\nscope.gg\nDIRECT\n\tSaaS Analytics\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-142\tTradeUpSpy\ntradeupspy.com\n\t\napi.tradeupspy.com\nDIRECT\n\tSaaS Tools\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-143\tEpidemic_GG\nepidemic.gg\n\t\nepidemic.gg\nDIRECT\n\tSaaS Tools\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-144\tCSDeals\ncs.deals\n\t\napi.cs.deals\nDIRECT\n\tMarketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-145\tPricempire\npricempire.com\n\t\npricempire.com\nDIRECT\n\tSaaS Price DB\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-146\tCS2Stash\ncs2stash.com\n\t\ncs2stash.com\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-147\tCSGOSkins\ncsgoskins.gg\n\t\ncsgoskins.gg\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-148\tSteamAnalyst\nsteamanalyst.com\n\t\nsteamanalyst.com\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-149\tSteamCardExchange\nsteamcardexchange.net\n\t\nsteamcardexchange.net\nDIRECT\n\tTrading Exchange\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-150\tDotaBuff\ndotabuff.com\n\t\ndotabuff.com\nDIRECT\n\tSaaS Tracker\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-151\tTracker_GG\ntracker.gg\n\t\ntracker.gg\nDIRECT\n\tSaaS Tracker\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-152\tFSB Market (an anonymized label; the original name is withheld here)\nFSB Market\n\t\nFSB Market\nDIRECT\n\tMass Blackmarket\tSSA § 2.G, SSA § 4.C, SSA § 1.C\tSee dated evidence\nEX-153\tFunPay\nfunpay.com\n\t\nfunpay.com\nDIRECT\n\tAccount Exchange\tSSA § 2.G, SSA § 4.C, SSA § 1.C\tSee dated evidence\nEX-154\tPlayerAuctions\nplayerauctions.com\n\t\nplayerauctions.com\nDIRECT\n\tGrey Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-155\tEldorado.gg\neldorado.gg\n\t\neldorado.gg\nDIRECT\n\tAccount Portal\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-156\tG2A\ng2a.com\n\t\ng2a.com\nDIRECT\n\tMass Key Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-157\tKinguin\nkinguin.net\n\t\nkinguin.net\nDIRECT\n\tMass Key Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-158\tG2G.com\ng2g.com\n\t\ng2g.com\nDIRECT\n\tVirtual Services\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-159\tPlayerup\nplayerup.com\n\t\nplayerup.com\nDIRECT\n\tAccount Broker\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-160\tZ2U.com\nz2u.com\n\t\nwww.z2u.com\nDIRECT\n\tReady-Account Hub\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-161\tSmurfHub\nsmurfhub.net\n\t\nsmurfhub.net\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-162\tSmurfAccounts\nsmurfaccounts.com\n\t\nsmurfaccounts.com\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-163\tBuyCSGORank\nbuycsgorank.com\n\t\nbuycsgorank.com\nDIRECT\n\tRank Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-164\tCSGOSmurfKings\ncsgosmurfkings.com\n\t\ncsgosmurfkings.com\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-165\tSmurfStore_Co\nsmurfstore.co\n\t\nsmurfstore.co\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-166\tSteamLvlUp\nsteamlvlup.com\n\t\nsteamlvlup.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-167\tSteamLevels\nsteamlevels.com\n\t\nsteamlevels.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-168\tLevelSteam\nlevelsteam.com\n\t\nlevelsteam.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-169\tSteamLevelU\nsteamlevelu.com\n\t\nsteamlevelu.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-170\tEloKing\neloking.com\n\t\neloking.com\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-171\tBoosteria\nboosteria.org\n\t\nboosteria.org\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-172\tOvergear\novergear.com\n\t\novergear.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-173\tBlazingBoost\nblazingboost.com\n\t\nblazingboost.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-174\tDota2Boost\ndota2boost.com\n\t\ndota2boost.com\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-175\tBuyBoost\nbuyboost.com\n\t\nbuyboost.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\n제4장: 기술 아키텍처 및 인증 메커니즘참조: TECH-ANALYSIS-01\n\n1. OpenID에서 도메인 소유권 검증 기능의 부재 2.0: Valve의 OpenID 2.0 프로토콜 구현 (https://steamcommunity.com/openid/login)는 다음을 평가합니다. openid.return_to 그리고 openid.realm 개발자의 사전 등록, 암호화 기반 인증 검증 또는 도메인 소유권 확인 절차 없이도 매개변수를 제공할 수 있습니다. 모든 상업 운영자는 사용자를 Valve의 로그인 화면으로 안내하고, 임의의 도메인으로 리디렉션된 암호화 서명이 포함된 신원 확인 정보(64-비트 SteamID 포함)를 수신할 수 있습니다.\n\n2. 프로그래매틱 인벤토리 조회 및 API 키 남용: OpenID를 통해 사용자 인증이 확인되면, 운영자는 공개 및 제휴 웹 API 엔드포인트에 쿼리를 보냅니다 (IEconItems_730/GetPlayerItems)를 통해 재고 자산을 실시간으로 색인화합니다. 자동화된 거래 네트워크는 프로그래매틱 세션 토큰을 활용하여 P2P(Peer-to-Peer) 거래 제안을 제출, 조회 및 수락하는데, 이는 SSA §4.C에서 규정하는 비인간 상호작용 금지 조항에 명백히 위배됩니다.\n\n3. 링크 필터 비대칭성: 소비자 대상 도메인 경고와 완벽하게 작동하는 인증 엔드포인트가 공존하는 상황은 규제상의 모순을 야기합니다. 즉, Valve의 보안 텔레메트리 시스템은 해당 운영자를 “잠재적 악성”으로 분류하고 있음에도 불구하고, Valve의 인증 인프라는 계속해서 해당 사용자 기반을 인증하고 있습니다.\n\n증거 수집 방법론 및 증거 관리 이력서\n\n본 문서는 인증되지 않은 네트워크 캡처 데이터, 과거 RDAP 레지스트리 조회 결과 및 검증된 암호화 해시 매니페스트를 바탕으로 작성되었습니다. 어떠한 사용자 로그인 자격 증명도 유출 테스트를 거치거나 처리되지 않았습니다. 모든 조사 결과는 9월 2026. 시점의 관찰 가능한 운영 네트워크 상태를 반영합니다. 본 문서는 사법, 규제 및 대중의 조회를 위해 작성된 초당파적인 기술적 증거 자료입니다.\n\n요약: SHA-256, 검증 완료\nc507c9025f93da0aadaf395c4d8882f25973211c318ee8e9b6f18a5b3755e050\n아카이브: 공개 법률 기록\n발행 및 서명자: phishdestroy.io · 법과학 연구 연합\n법적 지위: 모든 권리는 인류에게 양도됨 · CC0 범용 퍼블릭 도메인",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "법정감사법 및 규제 관련 부속서"
          }
        ],
        "links": []
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ko/regulatory_act_print.content.json",
      "export_json_sha256": "36482a82d993f4d71ea1d46dd1b73b608141fee8617fbaca961b090039479367"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ko/security_timeline.html",
      "language": "ko",
      "title": "보안 연표 — ‘Steam’ 관련 자료",
      "source_url": "https://phishdestroy.io/steam_dossier/ko/security_timeline",
      "source_html_sha256": "4d47826047a81eabbdee491e2a1720f5a335447a5db5eebee0d59d5d6e5ff25b",
      "exported_at": "2026-09-29T00:21:56.917Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "security_timeline.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ko/security_timeline.pdf?v=print-20260929-v5",
        "sha256": "80ef0b909b60e110c4794b04ffacce4d5a0ffb8ba7cf5b19f1d88438e5d25c15",
        "bytes": 83986,
        "pages": 6
      },
      "integrity": {
        "signed_object": "security_timeline.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "security_timeline.content.json.asc",
        "digest_file": "security_timeline.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify security_timeline.content.json.asc security_timeline.content.json",
          "sha256sum -c security_timeline.content.json.sha256"
        ]
      },
      "content": {
        "text": "보안 실적전시 / ‘16’ 출품작\n\n2018 — 2026\n\n보안 연혁 — 2018에서 2026로\n\n보안 정책이 변경되었습니다. 기록을 따르세요.\n\n이 섹션이 입증하는 바\n\n이 연대기 기록은 Steam의 거래 및 인증 스택 전반에 걸쳐 8년 동안 이루어진 보안 개선 사항을 재구성한 것입니다. 이 기록은 2018 7-의 일일 거래 보류 기능 구현, 2023 Web API의 모바일 인증 키, 그리고 2026의 세션 토큰 사용 중단 조치를, 문서화된 우회 기법들과 대조하여 추적합니다. 이 타임라인을 통해 플랫폼 업데이트가 알려진 공격 경로에 비해 지속적으로 뒤처졌으나, 상업적 운영자들에게는 구조적 이점이 유지되었음을 확인할 수 있습니다.\n\n← 경영진 브리핑으로 돌아가기\n\n거래 잠금. 로그인 제어. API 제한 사항. 무엇이 변경되었는지, 그리고 해당 출처들이 실제로 무엇을 입증하는지에 대한 과거 기록.\n\n타임라인 살펴보기 ↓\n8년. 단 하나의 기록.16검토할 주요 단계\n\n모든 항목에는 제출 날짜와 출처가 기록됩니다. 검증 결과는 해당 항목 옆에 표시됩니다.\n\n검토됨 / 24 9월 2026\n10확인된 행사 및 날짜\n06부분적으로 확인됨\n00소스 불일치\n00출처 필요\n이 기록을 읽는 방법\n\n확인된 행사 및 날짜: 둘 다 신뢰할 수 있는 1차 자료에 근거하고 있다. 부분적으로 확인됨: 관련 변경 사항이 기록되어 있으나, 날짜나 적용 범위는 아직 확정되지 않았습니다. 소스 불일치: 링크된 자료는 제출된 주장을 뒷받침하지 않습니다. 출처 필요: 이번 검토 과정에서 해당 날짜와 일치하는 출처는 확인되지 않았습니다. 확인되지 않은 항목이 있다고 해서 해당 사건이 발생하지 않았다는 증거는 아닙니다.\n\n미해결 항목에 표시된 날짜는 제출일이며, 확인된 공개일이 아닙니다. 원본 조사 내용은 수정되지 않았습니다.\n\n연표\n01 — 16\n기록 검색주제증거주문\n\n16 16 게시물 · 최신순\n\n202609-01제출일\n커뮤니티부분적으로 확인됨\n그룹 채팅에서 의심스러운 메시지에 대한 경고\n\n공식 베타 공지문을 통해 8월 31에 해당 기능이 추가될 예정임이 확인되었습니다. 제공된 1의 9월 안정화 버전 출시 일정에 대해서는 아직 구체적인 릴리스 노트가 공개되지 않았습니다.\n\nSteam 클라이언트 베타 — 8월 31일 ↗보관됨 2026-03-13 ↗\n원본 게시물 및 제출된 링크\n\n의심스러운 채팅 자동 표시\n\n제출된 소스 코드 확인하기 ↗\n202601-16확인 날짜\nAPI확인된 행사 및 날짜\n퍼블리셔 키에 대한 세분화된 권한 및 IP 허용 목록 기능 (Valve 공지)\n\n16년 1월 2026, Valve에서 Steamworks 관련 공식 공지를 게시했습니다 (\"새 기능: 웹 API 키에 대한 향상된 권한 및 제어 기능\") 개발자가 웹 API 키를 개별 그룹으로 분류할 수 있게 해주는 새로운 세분화된 권한 관리 도구를 확인하며 (일반, 소액 결제, 경제, 판매 데이터), 키를 특정 앱 ID로 제한하고, 서버 IP 화이트리스트 적용을 강제합니다.\n\n눈에 띄는 이중 잣대: 이번 공식 발표에 따르면, Valve은 API의 세부 권한 설정 및 IP 제한을 위한 기술적 인프라를 완전히 구축했으나, 일반 사용자 계정에서는 의도적으로 이를 제공하지 않고 (steamcommunity.com/dev/apikey). 일반 사용자 API 키는 여전히 일체형이며, ‘전부 아니면 전무’ 방식의 인증 정보로, IP 허용 목록 기능이 없습니다. 바로 이러한 기술적 누락이 수백만 달러 규모의 API 거래 가로채기 산업을 가능하게 하고 있습니다.\n\nValve 공지 — 신규: 웹 API 키에 대한 개선된 권한 및 제어 기능 (16 Jan 2026) ↗· 문서: Steamworks 웹 API 인증 ↗\n원본 게시물 및 제출된 링크\n\nSteamworks 웹 API 세부 범위\n\nValve의 공식 Steamworks 발표(493839547938902179)를 확인해 보세요 ↗\n202507-15확인 날짜\n거래확인된 행사 및 날짜\nCS2 거래에 7일간의 반전 기간이 부여됩니다\n\nValve의 최근 공지에서는 지난 7일간의 카운터스트라이크 아이템 거래를 되돌리는 조치가 도입되었다. 이는 계정 탈취를 방지하기 위해 고안된 것이지만, 제3자 경제 감사(CSMarketCap ↗)는 $104M (-25%) 축소 현물 거래 중단으로 인해 24 시간 내에 시가총액 기준 순위가 하락했습니다. 분석에 따르면 Skinvault ↗, 반전 조건이 발동되면 해당 계좌에 자동으로 30-데이 트레이딩 이용 제한이 적용됩니다. 여름에 2026, Valve는 전 세계 UTC 기준 자정 리셋 방식에서 개별 상품별 분 단위 타이머 방식으로 전환되었습니다 (Skin.land ↗).\n\nValve — 15 7월 2025 발표 ↗· CSMarketCap 분석 ↗\n원본 게시물 및 제출된 링크\n\nCS2 거래 보호 / 취소 기간\n\n제출된 소스 코드 확인하기 ↗\n202505-14확인 날짜\n인증확인된 행사 및 날짜\nValve SMS 유출과 관련된 계정 보안 경고를 발표하다\n\nValve가 5월 14,에 게시한 공식 공지(2025,)는 계정 보안 및 SMS 기반 인증 방식에 대해 다루고 있습니다. 이 공지는 SMS 유출 문제에 중점을 두고 있으며, Steam 시스템이 침해되지 않았음을 확인하지만, 게시된 날짜를 기준으로 한 공식 보안 업데이트 역할을 합니다.\n\nValve — Steam 계정 보안에 관한 안내 ↗\n원본 게시물 및 제출된 링크\n\n계정 보안 관련 공지\n\n제출된 소스 코드 확인하기 ↗\n202410-02확인 날짜\n거래확인된 행사 및 날짜\n재거래 또는 재판매 7일 전\n\n이번 업데이트 노트에는 무기고, 거래 제안, 커뮤니티 마켓을 통해 획득한 아이템이 포함됩니다. 문서화된 범위는 무기고 아이템에만 국한되지 않습니다.\n\nValve —10/2/2024 릴리스 노트 ↗\n원본 게시물 및 제출된 링크\n\nCS2 더 아머리 / 7-데이 홀드\n\n제출된 소스 코드 확인하기 ↗\n202409-18제출일\n거래부분적으로 확인됨\n도움말 페이지에서 새로운 기기 관련 제한 사항 확인\n\nSteam의 공식 지원 문서에 따르면, 최소 7일 동안 인증되지 않은 새로운 기기에서 로그인할 경우 7-데이트레이딩 제한이 적용됨이 확인되었습니다. 9월 18, 2024,의 정확한 출시일은 변경 내역의 주요 사항으로 기록되어 있지 않지만, 해당 기능은 문서에 상세히 기술되어 있습니다.\n\nSteam 지원 — 거래 및 시장 제한 사항 ↗\n원본 게시물 및 제출된 링크\n\n신규 기기 로그인 거래 제한\n\n제출된 소스 코드 확인하기 ↗\n202402-14제출일\n커뮤니티부분적으로 확인됨\n2024에 이름 변경 거래 대기 시간 적용\n\n커뮤니티 및 개발자 기록을 통해 확인된 바에 따르면, 2024, 초기에 Valve는 신속한 사칭 사기를 방지하기 위해 프로필 이름 변경 직후 2-에서4 시간의 거래 대기 시간을 예고 없이 도입했습니다. Valve가 이 제한 사항에 대해 공식 보도 자료, 클라이언트 변경 내역 또는 지원 문서를 공개하지 않았기 때문에, 제출된 2월 14 날짜는 공식적인 확인을 받지 못했습니다. Steam 워크숍 가이드는 공식 Valve 문서라기보다는 간접적인 커뮤니티 증언의 역할을 합니다.\n\nSteam 워크숍 가이드 (간접적 입증) — 이름 변경 제한 사항 ↗\n원본 게시물 및 제출된 링크\n\n프로필 이름 / 아바타 변경 보류\n\n제출된 소스 코드 확인하기 ↗\n202312-04확인 날짜\nAPI확인된 행사 및 날짜\n키 생성을 위해서는 모바일 확인이 필요합니다.\n\n타사 개발자 라이브러리에 기록된 바와 같이, 웹 API 키 생성을 위한 ‘Steam Guard’ 모바일 인증 의무화가 2023, 말경에 시행된 것으로 확인되었습니다. 12월 4, 2023,의 정확한 날짜는 개발자 커뮤니티 내에서 관찰된 도입 기간을 나타냅니다.\n\n유지 관리자 문서 — 3월 2024 ↗보관됨 2026-09-24 ↗\n원본 게시물 및 제출된 링크\n\nAPI 키에 대한 모바일 확인\n\n제출된 소스 코드 확인하기 ↗\n202310-24확인 날짜\n개발자확인된 행사 및 날짜\n게임 빌드를 라이브 환경에 배포하기 위한 필수 ‘2’ FA가 발효됩니다.\n\nValve가 10월 10, 2023,에 게시한 Steamworks 공식 공지에 따르면, 10월 24, 2023,부터 출시된 애플리케이션의 기본 브랜치에서 빌드를 라이브로 설정하는 모든 계정은 SMS 또는 Steam 모바일 앱을 통해 해당 변경 사항을 승인해야 합니다. 이 변경 사항은 SetAppBuildLive 웹 페이지 API에 즉시 반영되었습니다.\n\nSteamworks — 빌드 및 사용자 관리를 위한 보안 개선 사항 ↗보관됨 2025-12-03 ↗\n원본 게시물 및 제출된 링크\n\n게임 빌드 공개를 위한 SMS 기반 다단계 인증(MFA)\n\n제출된 소스 코드 확인하기 ↗\n202307-12제출일\n커뮤니티부분적으로 확인됨\n커뮤니티에서 확인된 사용자 작성 약력 콘텐츠에 대한 경고\n\nSteam 7월부터 접수된 커뮤니티 보고서에 따르면(2023), 외부 링크나 트리거 단어가 포함된 사용자 프로필 소개글에 자동 콘텐츠 경고가 표시되기 시작한 것으로 확인되었습니다. 7월 12, 2023,에 제출된 날짜는 Steam 커뮤니티 포럼에 올라온 초기 사용자 신고들과 일치합니다.\n\nSteam 커뮤니티 포럼 — 바이오 콘텐츠 경고 신고 ↗\n원본 게시물 및 제출된 링크\n\n사용자 지정 약력 콘텐츠 경고\n\n제출된 소스 코드 확인하기 ↗\n202301-25제출일\n커뮤니티부분적으로 확인됨\n프로필 링크 필터링 및 편집 대기 시간이 활성화되었습니다.\n\nSteam의 공식 지원 문서에 따르면, 사용자 정의 약력에 포함된 링크는 필터링되며, 부적절한 이름 또는 아바타 변경은 편집 제한 조치를 유발할 수 있음이 확인되었습니다. 1월 25, 2023,에 적용된 4-의 1시간 대기 시간 정책이 이 현상의 시작점으로 관찰되지만, 링크 필터링 메커니즘 자체는 제출된 도움말 페이지에서 이미 완전히 활성화되어 있습니다.\n\nSteam 지원 — 프로필 이름 및 아바타 제한 사항 ↗\n원본 게시물 및 제출된 링크\n\n프로필 링크 삭제됨 / 재사용 대기시간\n\n제출된 소스 코드 확인하기 ↗\n202210-24확인 날짜\n인증확인된 행사 및 날짜\nSteam 클라이언트의 OAuth 갱신 토큰 및 액세스 토큰으로의 전환\n\nValve의 10월 주요 클라이언트 및 모바일 앱 업데이트 2022는 Steam 인증 시스템을 전면 개편했습니다. 기존의 세션 쿠키 구조는 OAuth 기반의 액세스 토큰 및 리프레시 토큰으로 대체되었으며, 활성화된 인증된 기기 목록이 도입되어 활성 세션을 수동으로 취소할 수 있게 되었습니다.\n\nValve — ‘Steam’ 모바일 앱 업데이트 및 인증 시스템 전면 개편 ↗\n원본 게시물 및 제출된 링크\n\nSteam 로그인 시스템 개편 / 쿠키 길이 제한\n\nValve 공지사항 확인하기 ↗\n202210-12확인 날짜\n인증확인된 행사 및 날짜\nQR 코드 기반 로그인 및 승인된 기기 관리\n\nValve가 10월에 발표한 ‘12’에서는 QR 코드 로그인, 로그인 승인 또는 거부, 그리고 계정 접근 권한을 취소할 수 있는 기기 목록에 대해 설명하고 있습니다.\n\nValve — 업데이트된 ‘Steam’ 모바일 앱을 이제 이용하실 수 있습니다 ↗\n원본 게시물 및 제출된 링크\n\nSteam 모바일 앱 3.0 / QR 로그인\n\n제출된 소스 코드 확인하기 ↗\n202205-10제출일\nAPI부분적으로 확인됨\n공개 API 목록에서 거래 취소 엔드포인트가 제거되었습니다.\n\n개발자 기록에 따르면, 5월 2022, Valve 에서 IEconService/CancelTradeOffer 및 DeclineTradeOffer와 같은 거래 관리 엔드포인트가 웹 API 에서 아무런 공지 없이 제거된 것으로 확인되었습니다(node-steam-tradeoffer-manager #325에 기록됨). 해당 메서드들은 비공개 클라이언트 프로토콜에서는 여전히 작동하지만, 5월 10, 2022,을 기점으로 사기 패널을 방지하기 위해 공개 웹 API에서 제거된 것으로 확인되었습니다.\n\n개발자 토론 — 이슈 #325(CancelTradeOffer 제거) ↗· Steamworks 웹 API — IEconService 문서 ↗\n원본 게시물 및 제출된 링크\n\n거래 취소 엔드포인트 제거\n\nnode-steam-tradeoffer-manager 이슈 #325 확인하기 ↗\n202005-25확인 날짜\n거래확인된 행사 및 날짜\n도타2의 아이템에는 7일간의 거래 대기 시간이 적용됩니다.\n\n5월 25, 2020,, ‘10’ 배틀 패스 출시(blog.dota2.com/2020/05/the-international-10-battle-pass/)와 함께, Valve는 2018 카운터 스트라이크 정책에 맞춰 도타 2 아이템에 대해 7-일간의 거래 잠금 조치를 시행했습니다. 이 제한은 모든 거래된 아이템과 마켓 구매품에 적용됩니다.\n\nDota2 커뮤니티 — 트레이드 잠금 및 TI10 클라이언트 업데이트 ↗\n원본 게시물 및 제출된 링크\n\nDota 2 / 7-데이 트레이드 잠금\n\n제출된 소스 코드 확인하기 ↗\n201803-29확인 날짜\n거래확인된 행사 및 날짜\n거래된 CS:GO 아이템에는 7일간의 재사용 대기 시간이 적용됩니다.\n\n공식 릴리스 노트에서 날짜와 제한 사항이 확인되었습니다. 제공된 URL은 2013의 지도 업데이트 페이지로 연결되었으며, 해당 릴리스 노트의 URL은 20309.로 끝납니다.\n\nValve —3/29/2018 릴리스 노트 ↗\n원본 게시물 및 제출된 링크\n\nCS:GO / 7-데이 트레이드 잠금\n\n제출된 소스 코드 확인하기 ↗ 보관됨 2025-02-26 ↗\n\n증거를 따르십시오. 출처를 확인하십시오.\n\n수사로 돌아가기 ↗",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "보안 연혁 — 2018에서 2026로"
          },
          {
            "level": 2,
            "id": null,
            "text": "연표"
          },
          {
            "level": 2,
            "id": null,
            "text": "그룹 채팅에서 의심스러운 메시지에 대한 경고"
          },
          {
            "level": 2,
            "id": null,
            "text": "퍼블리셔 키에 대한 세분화된 권한 및 IP 허용 목록 기능 (Valve 공지)"
          },
          {
            "level": 2,
            "id": null,
            "text": "CS2 거래에 7일간의 반전 기간이 부여됩니다"
          },
          {
            "level": 2,
            "id": null,
            "text": "Valve SMS 유출과 관련된 계정 보안 경고를 발표하다"
          },
          {
            "level": 2,
            "id": null,
            "text": "재거래 또는 재판매 7일 전"
          },
          {
            "level": 2,
            "id": null,
            "text": "도움말 페이지에서 새로운 기기 관련 제한 사항 확인"
          },
          {
            "level": 2,
            "id": null,
            "text": "2024에 이름 변경 거래 대기 시간 적용"
          },
          {
            "level": 2,
            "id": null,
            "text": "키 생성을 위해서는 모바일 확인이 필요합니다."
          },
          {
            "level": 2,
            "id": null,
            "text": "게임 빌드를 라이브 환경에 배포하기 위한 필수 ‘2’ FA가 발효됩니다."
          },
          {
            "level": 2,
            "id": null,
            "text": "커뮤니티에서 확인된 사용자 작성 약력 콘텐츠에 대한 경고"
          },
          {
            "level": 2,
            "id": null,
            "text": "프로필 링크 필터링 및 편집 대기 시간이 활성화되었습니다."
          },
          {
            "level": 2,
            "id": null,
            "text": "Steam 클라이언트의 OAuth 갱신 토큰 및 액세스 토큰으로의 전환"
          },
          {
            "level": 2,
            "id": null,
            "text": "QR 코드 기반 로그인 및 승인된 기기 관리"
          },
          {
            "level": 2,
            "id": null,
            "text": "공개 API 목록에서 거래 취소 엔드포인트가 제거되었습니다."
          },
          {
            "level": 2,
            "id": null,
            "text": "도타2의 아이템에는 7일간의 거래 대기 시간이 적용됩니다."
          },
          {
            "level": 2,
            "id": null,
            "text": "거래된 CS:GO 아이템에는 7일간의 재사용 대기 시간이 적용됩니다."
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/ko/#briefing-heading",
          "https://steamcommunity.com/groups/SteamClientBeta?l=english",
          "http://web.archive.org/web/20260313235409/https://steamcommunity.com/groups/SteamClientBeta?l=english",
          "https://store.steampowered.com/news/posts/?enddate=1788390000",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/493839547938902179",
          "https://partner.steamgames.com/doc/webapi_overview/auth",
          "https://csmarketcap.com/blog/market-insights/from-boom-to-bust-cs2s-trade-protection-impact",
          "https://skinvault.gg/blog/cs2-trade-protection-explained/",
          "https://skin.land/blog/steam-changes-cs2-trade-ban-logic-timing/",
          "https://store.steampowered.com/news/posts/?appids=730&amp;enddate=1753924057&amp;feed=steam_announce%2F1000",
          "https://help.steampowered.com/faqs/view/3041-A87A-E5F6-B6AC",
          "https://store.steampowered.com/news/posts/?enddate=1747349559",
          "https://steamcommunity.com/ogg/593110/announcements/detail/533224478739530146",
          "https://store.steampowered.com/news/posts/?appids=730&amp;enddate=1728000977&amp;feed=steam_community_announcements",
          "https://steamcommunity.com/games/CSGO/announcements/detail/4447966961421256740",
          "https://help.steampowered.com/faqs/view/7F77-9E92-31E0-6B8E",
          "https://steamcommunity.com/sharedfiles/filedetails/?id=2926756889",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "http://web.archive.org/web/20260924181824/https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "https://steamcommunity.com/dev/apikey",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3749866608167579206",
          "http://web.archive.org/web/20251203174259/https://steamcommunity.com/groups/steamworks/announcements/detail/3749866608167579206",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3734103130194459461",
          "https://steamcommunity.com/discussions/forum/1/3807266184852932971/",
          "https://help.steampowered.com/faqs/view/225C-C51E-B8F0-55B2",
          "https://store.steampowered.com/news/group/4/view/3314112260640237775",
          "https://store.steampowered.com/news/posts/?appgroupname=Keep+in+touch&amp;enddate=1666122699&amp;feed=steam_blog",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/issues/325",
          "https://partner.steamgames.com/doc/webapi/IEconService",
          "https://steamcommunity.com/app/570/announcements/",
          "https://blog.dota2.com/2020/05/trading-cooldown/",
          "https://blog.counter-strike.net/2018/03/20309/",
          "https://blog.counter-strike.net/index.php/2018/03/20308/",
          "http://web.archive.org/web/20250226114333/https://blog.counter-strike.net/index.php/2018/03/20308/",
          "https://phishdestroy.io/steam_dossier/ko/#vulnerability-profile"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ko/security_timeline.content.json",
      "export_json_sha256": "8217f5f40488382bdf5a547eeb4a3749dbd39dedcf8e0eaf582ed72e661f011f"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ko/skin_atlas.html",
      "language": "ko",
      "title": "Steam가 실을 수 없는 것들의 지도 — ‘Steam’ 자료집",
      "source_url": "https://phishdestroy.io/steam_dossier/ko/skin_atlas",
      "source_html_sha256": "6e15b68a3890ae8e2f1d261a99d0d44b0580c07f643465bfd958ab815d6535e3",
      "exported_at": "2026-09-29T00:22:00.632Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "gallery",
            "source": "https://phishdestroy.io/steam_dossier/ko/skin_atlas#gallery"
          }
        ],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "skin_atlas.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ko/skin_atlas.pdf?v=print-20260929-v5",
        "sha256": "3746151385dc7958f603e88894dbe0b8cd255d7e2791d4019cb7f0c096682d13",
        "bytes": 184141,
        "pages": 12
      },
      "integrity": {
        "signed_object": "skin_atlas.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "skin_atlas.content.json.asc",
        "digest_file": "skin_atlas.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify skin_atlas.content.json.asc skin_atlas.content.json",
          "sha256sum -c skin_atlas.content.json.sha256"
        ]
      },
      "content": {
        "text": "부록 IV-B / 가격 사다리 / 2026-09-23\n스킨 가격 사다리 아틀라스 — 유동성 절벽\n\nValve의 시장 방문 일정 돈이 시작되는 곳.\n\n이 섹션이 입증하는 바\n\n이 시각적 아틀라스는 5개 마켓플레이스 카탈로그 전반에 걸친 ‘30,266’ 상품 카테고리를 분석하여, ‘Valve’의 등록 기준치 이상 및 미만의 시장 커버리지를 측정합니다. $1,800 한도 미만에서, Steam은 95.3%개의 활성 카테고리를 호스팅하고 있습니다. 이 한도 바로 위에서는 공식 커버리지가 1.9%로 급감하며(0.0%는 검증된 자산에 대한 커버리지를 제공합니다), 이는 Valve가 기초 자산의 보관에 대한 완전한 통제권을 유지하면서도 고가치 거래 탐색을 외부 플랫폼에 위임하는, 갑작스럽고 구조적인 유동성 절벽을 보여줍니다.\n\n← 경영진 브리핑으로 돌아가기\n\n5개 마켓플레이스에서 실시간 가격이 표시된 모든 CS2 아이템은 가장 저렴한 매도가를 기준으로 가격대별로 분류되었으며, 각 가격대별로 단 한 가지 지표, 즉 해당 가격대 내에서 ‘Valve’의 커뮤니티 마켓이 차지하는 비중을 측정했습니다. ‘Valve’의 등록 한도 이내에서는 그 결과는 다음과 같습니다. 95.3%. 그 위에 있는 정답은 1.9%. 하락은 점진적이지 않으며, 수요가 감소하는 지점에서 떨어지는 것도 아니다. 정확히 공표된 규정에 따라 하락한다. 그 중 248 두 개 이상의 마켓플레이스가 상한선보다 높게 독립적으로 가격을 책정한 상품 카테고리의 경우, 100.0%에는 Steam에 해당 상품이 아예 등록되어 있지 않습니다.\n\n절벽을 보세요 ↓419 상품 갤러리 열기방법 및 한계\n30,266측정된 품목 범주\n95.3%Steam가 취급하는 자본금 미달 항목\n1.9%Steam에서 취급하는 상한선 초과 품목 중\n$78.6M검증된 집합의 하한값\n01 / 측정\n절벽은 요구에 따라가 아니라 규칙에 따라 형성된다\n\n아래의 ‘30,266’ 항목 카테고리들은 각각 다음 기준에 따라 그룹으로 분류됩니다. 가장 저렴한 BUFF163, CSFloat, Skinport, YouPin 898 및 C5Game을 아우르는 실시간 조회 결과를 종합한 것으로, 이 중 두 곳 이상에 등재된 항목만 집계되므로, 한 곳의 낙관적인 등재 정보만으로는 밴드 멤버를 임의로 만들어낼 수 없습니다. 상단 표는 Valve의 자체 시장에서 여전히 거래되고 있는 각 밴드의 비중을 나타냅니다.\n\nSteam 커뮤니티 마켓에서 취급하는 각 가격대의 비중\n위: 증기 분포 · 아래: 밴드별 항목 수, 로그 눈금\n0%\n25%\n50%\n75%\n100%\n100%\n96.9%\n95.9%\n97.3%\n91.1%\n76.8%\n14.5%\n2.9%\n1.5%\n0%\n0%\n0%\n4,632\n1¢–10¢\n7,152\n10¢–$1\n8,568\n$1–10\n5,941\n$10–100\n2,329\n$100–300\n1,292\n$300–1k\n193\n$1k–1.8k\n70\n$1.8k–3k\n67\n$3k–10k\n18\n$10k–30k\n3\n$30k–100k\n1\n$100k+\nitems\nlog\nVALVE’S LISTING CAP\nValve의 상장 한도 이내한도 초과 — ‘Valve’의 규정에 따라 상장이 금지됩니다밴드의 아이템 카테고리\n\n‘포괄성’이란 캡처 시점에 해당 카테고리에 대한 Steam 실시간 질의가 존재했음을 의미합니다. 하단 패널은 로그 스케일로 표시되어 있는데, 이는 카탈로그에 포함된 항목의 가격이 압도적으로 저렴하기 때문입니다. 선형 스케일로 표시할 경우 $300를 초과하는 모든 구간이 기준선 수준으로 평탄화되어 버리기 때문입니다.\n\n해당 형태가 배제하는 것\n\n만약 고가 품목이 단순히 인기가 없다면, 가격이 오를수록 수요 곡선은 서서히 하락할 것이다. 하지만 실제로는 그렇지 않다. 수요 곡선은 76.8%에서 $300–$, 1k 구간을 거치며 일정 수준을 유지하다가, 상한선 바로 아래 구간에서는 14.5%로, 바로 위 구간에서는 2.9%로 급격히 떨어진다. 수요 효과는 Valve가 상한선을 어디에 설정했는지 알지 못한다. 규칙은 안다.\n\n가격대\t상품 카테고리\tSteam의 생방송 질문 코너를 통해\tSteam 보도 범위\tSteam에 게재된 목록\n1¢–10¢\t4,632\t4,632\t100%\t8,223,227\n10¢–$1\t7,152\t6,931\t96.9%\t5,488,315\n$1–10\t8,568\t8,213\t95.9%\t3,939,538\n$10–100\t5,941\t5,780\t97.3%\t1,328,255\n$100–300\t2,329\t2,121\t91.1%\t364,466\n$300–1k\t1,292\t992\t76.8%\t187,504\n$1k–1.8k\t193\t28\t14.5%\t40,281\n$1.8k–3k\t70\t2\t2.9%\t9,592\n$3k–10k\t67\t1\t1.5%\t6,706\n$10k–30k\t18\t0\t0%\t1,366\n$30k–100k\t3\t0\t0%\t21\n$100k+\t1\t0\t0%\t2\n\n이 순위표에서는 패턴 및 단계별 변형은 제외됩니다. Steam에서는 블루 젬 티어나 루비 단계를 별도의 시장 진입 항목으로 나열하지 않으므로, 이를 포함할 경우 Steam의 포괄 범위가 과소평가될 수 있습니다. 두 마켓플레이스 요건을 적용하지 않고 측정할 경우, 동일한 순위표는 37,204 항목 전체에 걸쳐 상한선 아래에서는 79.1%, 상한선 위에서는 6.5%로 나타납니다. 이는 더 약한 근거에 기반한 더 큰 격차이므로, 인용된 수치가 아닙니다.\n\n02 / 증거에 따른 등급 평가\n매도 희망가는 가격이 아니다\n\n누구나 P2000을 1,000만 위안으로 매물로 올릴 수 있습니다. 이 페이지에 기재된 수치가 어떤 용도로든 사용되기 전에, 해당 품목에 대해 상한선 이상의 가격을 제시한 독립적인 마켓플레이스의 수와 그 가격들의 중간값이 얼마나 밀집되어 있는지에 따라 등급이 매겨집니다. 본 문서 내 어디에서든 A등급과 B등급만 인용됩니다.\n\nA  세 개 이상의 선반이 일치합니다\n\n3개 이상의 마켓플레이스에서 해당 상품의 가격이 상한선보다 높게 책정되어 있으며, 그 가격의 중앙값이 최저가보다 25% 이내인 경우. 197 카테고리, 18,218 부, $76,585,587.\n\nSteam에 등장하지 않는 인물: 100.0%.\n\nB  두 선반이 일치합니다\n\n두 마켓플레이스가 상한선 이상에서 합의하거나, 세 마켓플레이스가 그보다 다소 낮은 수준에서 합의한다. 51 카테고리, 176 부, $2,038,814.\n\nSteam에 등장하지 않는 인물: 100.0%.\n\nC  선반 하나 — 사용하지 않음\n\n단 하나의 마켓플레이스에서만 상한가를 초과하는 매도 호가가 제시되고 있습니다. 171 카테고리, 247 부. 완전성을 기하기 위해 갤러리에 표시되었으나, 이 페이지의 모든 합계에서는 제외되었습니다.\n\n이는 가격을 문의하는 요청일 뿐, 가격을 입증하는 증거는 아닙니다.\n\n이번 조정으로 인한 손실과 그 대가로 얻은 것\n\nC 등급을 제외하면 171 카테고리와 $3,825,125가 헤드라인에서 사라집니다. 남은 내용은 더 간결해졌으며 반박하기가 훨씬 더 어려워집니다: 248 카테고리, 18,394에 등재된 복사본들, $78,624,401, 및 100.0%에 등재된 복사본들 — 그 중 단 하나도 예외 없이 — Valve의 마켓에서 찾아볼 수 없습니다. C등급 행들이 수치가 변동한 원인입니다. 이 행들은 숨겨져 있지 않고 목록에 표시되어 있습니다.\n\n유물로 지정된 목록\n\n동일한 품목에 대해 가장 저렴한 매도 호가의 3배를 초과하는 모든 호가는 제외됩니다. 데이터 자체에서 암시하는 환율로 환산해 보면, 이들 대부분은 둥근 위안화(CNY) 금액으로 나타납니다. 이는 실제 매도 호가라기보다는 자리 표시자나 플랫폼의 상한선을 나타내는 특징입니다. 이 페이지의 모든 합계는 가장 저렴한 말하자면, 이 인물들 중 그 누구도 수치를 부풀린 적이 없을 것입니다. 이들은 헤드라인으로 인용될 가능성이 없도록 배제된 것입니다.\n\n항목\t가장 저렴한 라이브 문의\t제쳐 두기\nSouvenir P2000 | Wicked Sick (Minimal Wear)\t$148,954\t$1,489,543\n★ Specialist Gloves | Crimson Kimono (Minimal Wear) | Phase 1\t$37,239\t$119,163\nSouvenir USP-S | Printstream (Factory New)\t$2,000\t$59,582\n★ Bowie Knife | Crimson Web (Factory New)\t$2,957\t$43,030\n★ Karambit | Marble Fade (Factory New) | 1st\t$11,916\t$38,874\nSticker | Ninjas in Pyjamas (Holo) | Katowice 2014\t$5,000\t$31,748\nSouvenir AWP | Dragon Lore (Battle-Scarred)\t$4,225\t$29,157\n★ Karambit | Doppler (Minimal Wear) | Ruby\t$7,122\t$27,273\n419의 모든 카테고리와 각 가격이 지칭하는 대상\n\n출처: https://phishdestroy.io/steam_dossier/ko/skin_atlas#gallery\n\n04 / 대신 어디로 갔는지\nSteam가 취급하지 않는 상품을 진열하는 선반들\n\n동일한 상품 목록을 해당 상품을 취급하는 마켓플레이스별로 묶은 것입니다. 이는 해당 상품이 몇 군데에 등록되어 있는지를 나타낸 것입니다. 등재된, 이는 소유권이 있는 곳과는 다르며, 여기서는 그런 의미로 해석되지 않습니다.\n\n마켓플레이스별 상한선 초과 매물의 최저가\n해당 선반에 진열된 상품 중 가장 낮은 매도 호가 x 개\nYouPin 898\n$22,720,252\nBUFF163\n$22,022,606\nC5Game\n$12,560,543\nCSFloat\n$10,871,845\nSkinport\n$1,385,060\n\n위 순서대로 관할 지역: YouPin 898 — 중국 · BUFF163 — 중국 · C5Game — 중국 · CSFloat — 미국 · Skinport — 독일 / 몰타. 동일한 실물 상품이 이 선반들 중 두 곳 이상에 등록될 수 있으므로, 이 수치를 다른 시장의 총계와 합산해서는 안 됩니다.\n\n가격대별 최저가\n상한선을 초과하는 금액은 어떻게 배분되는가\n$1.8k-3k\n$9,842,391\n$3k-10k\n$36,787,269\n$10k-50k\n$20,038,749\nover $50k\n$2,891,897\n05 / 셀 수 있을 만큼 부족한 것\n실제로 공급이 얼마나 부족한가\n\n각 CS2 아이템에는 마모도가 부여되어 있으며, 마켓플레이스에서는 각 마모도 구간별로 몇 개의 아이템이 있는지 공개합니다. 이로 인해 ‘희귀’라는 형용사가 숫자로 변환되는데, 바로 이 숫자가 단 하나의 해킹된 계정을 노리기 위해 맞춤형 피싱 키트를 제작하는 수고가 충분히 가치 있는 이유를 설명해 줍니다.\n\nAWP | 드래곤의 전설\n150 등록됨 · $11,350부터\n0.00–0.01\n29 · $14,730\n0.01–0.02\n54 · $11,618\n0.02–0.03\n26 · $11,350\n0.03–0.04\n25 · $11,618\n0.04–0.07\n16 · $11,585\n\nAWP | 드래곤 로어 (신품)\n\nM4A4 | 하울\n105 등록됨 · $6,628부터\n0.00–0.01\n11 · $10,725\n0.01–0.02\n14 · $8,088\n0.02–0.03\n11 · $7,580\n0.03–0.04\n19 · $6,703\n0.04–0.07\n50 · $6,628\n\nM4A4 | 하울 (출고 신품)\n\nAK-47 | 와일드 로터스\n113 등록됨 · $14,373부터\n0.00–0.01\n25 · $22,343\n0.01–0.02\n11 · $19,364\n0.02–0.03\n3 · $19,645\n0.03–0.04\n15 · $15,044\n0.04–0.07\n59 · $14,373\n\nAK-47 | Wild Lotus (공장 출고 상태)\n\nAWP | 군니르\n173 등록됨 · $11,618부터\n0.00–0.01\n28 · $17,875\n0.01–0.02\n21 · $13,600\n0.02–0.03\n32 · $12,065\n0.03–0.04\n29 · $11,735\n0.04–0.07\n63 · $11,618\n\nAWP | 군니르 (신품)\n\nAK-47 | 파이어 서펜트\n278 등록됨 · $663부터\n0.15–0.18\n87 · $730\n0.18–0.21\n49 · $712\n0.21–0.24\n52 · $703\n0.24–0.27\n18 · $715\n0.27–0.38\n72 · $663\n\nAK-47 | 파이어 서펜트 (실전 검증 완료)\n\n경화 처리 (모든 등급 / 파란색 보석)\n76 등록됨 · $1,638부터\n0.07–0.08\n1 · $2,516\n0.08–0.09\n4 · $2,482\n0.09–0.10\n6 · $3,856\n0.10–0.11\n7 · $2,797\n0.11–0.15\n58 · $1,638\n\nAK-47 | 표면 경화 처리 (마모 최소) | 등급1\n\n밴드는 마켓플레이스 고유의 유동성 구간이며, 최소 한 건의 실시간 호가가 있는 밴드만 추출됩니다. 각 막대 옆의 가격은 해당 밴드 내 가장 낮은 실시간 매도 호가이므로, 낮은 유동성에 따른 프리미엄을 명시적으로 표기하지 않아도 한눈에 파악할 수 있습니다.\n\n06 / 움직임, Steam에서 측정됨\n제3자 판매 대행 업체들이 실제로 달성한 실적\n\nValve 이 등급에서는 활용 가능한 거래 내역을 공개하지 않으며, 이 자료에서도 그러한 내역을 주장하지 않습니다. Skinport은 지난 24 시간, 7, 30 및 90 일 동안의 자체 완료된 매매 내역을 공개하고 있으며, 이것이 이곳에서 확인할 수 있는 시간 차원의 전부입니다. 즉, 각 기간별 실현 가격의 중앙값을 지수화한 것으로, 90-일 중앙값은 100.입니다. 두 차트 모두 ‘Steam’ 데이터는 포함되어 있지 않습니다.\n\n실현 가격 중앙값, 후행 기간\n90-일간의 중앙값에 연동 · 6,758 항목에 20+ 매출\n85\n91\n97\n103\n100\n90d\n94\n30d\n90\n7d\n88\n24h\n일일 완료 판매량\n같은 항목, 같은 창\n7,621\n9,653\n11,684\n13,716\n12,700\n90d\n11,894\n30d\n9,540\n7d\n8,637\n24h\n\n이것은 하나의 차트에 두 개의 수직 눈금이 있는 것이 아니라 두 개의 별도 차트입니다. 지수와 일별 건수는 단위가 다르기 때문에, 이를 동일한 축에 표시하면 타당하지 않은 비교를 유발할 수 있습니다. 창은 중첩되어 있으며 후행적입니다(90-일 수치는 24-시간 수치를 포함하고 있음). 따라서 이는 일별 시계열이 아니며, 일별 시계열로 해석되어서는 안 됩니다. 이 차트가 뒷받침하는 내용은 제한적이며 명확하게 명시되어 있습니다. Skinport에 게시된 후행 기간 동안, 실현 가격의 중앙값은 90-의 일별 중앙값보다 낮게 유지되었으며, 일별 판매 건수도 이에 따라 감소했습니다.\n\nSkinport 실현 매출. 창(window)은 중첩되고 이동식(trailing)으로 구성되어 있으므로, 각 점은 이동식 창 기간 동안의 실현 가격 중앙값이며, 90-일 중앙값을 기준으로 지수화되어 있습니다. 이는 일일 시계열이 아니며, Steam 데이터는 포함되지 않습니다.\n\n07 / 어떤 재료로 만들어졌는지\n16년 된 스티커와 한 줌의 장갑\n\n캡 상단의 세트는 게임 전체를 폭넓게 아우르는 것이 아닙니다. 이 세트는 몇 가지 희귀 아이템과 몇 가지 컬렉션에 집중되어 있으며, 그중 상당수는 더 이상 구할 수조차 없습니다. 바로 이 때문에 공급이 가격 변동에 대응할 수 없는 것입니다.\n\n희귀도별, 상단 탭의 카테고리\n항목 범주 수\nCovert\n321\nClassified\n39\nRestricted\n24\nContraband\n12\nMil-Spec Grade\n9\nConsumer Grade\n9\nIndustrial Grade\n5\n캡 위의 카테고리, 컬렉션별\n10대 컬렉션\nThe St. Marc Collection\n13\nThe Cobblestone Collection\n13\nThe Norse Collection\n12\nThe Arms Deal Collection\n9\nThe Canals Collection\n7\nThe Gods and Monsters Collection\n6\nThe Revolution Collection\n4\nThe 2021 Train Collection\n4\nThe Rising Sun Collection\n4\nThe Chop Shop Collection\n4\n\n카테고리별: 스킨 366, 스티커 48, 용기 3, 스티커_슬랩 2.\n\n08 / 실제로 누군가가 지불한 최고 금액\n상승세는 상장 때문이 아니라 거래에 힘입은 것\n\n이 페이지에 표시된 그 외의 모든 가격은 물어보세요 — 판매자가 원하는 것. 바로 이것들입니다. 판매: 각 상품에 대해 지난 90 일 동안 기록된 최고 완료 거래가Skinport입니다. 이는 본 자료집에서 실제로 누군가가 지불한 유일한 금액이며, 각 행은 마켓플레이스로 연결되어 있으므로 해당 금액을 저희 측이 아닌 출처에서 직접 확인하실 수 있습니다.\n\n21,216해당 기간 동안 판매가 완료된 상품\n106Valve의 상장 상한가 수준 또는 그 이상으로 매도됨\n$14,192단일 거래 기준 최고 판매액\n67/419기록된 판매 내역이 있는 상한선 초과 카테고리\n해당 기간 동안 성사된 매출액 상위 30건\n항목\t최고 판매량\t판매 중위값\t판매\t지금 가장 저렴한 가격 확인하기\tSteam\t한 번 확인해 보세요\nAWP | Gungnir (Factory New)\t$14,192\t$11,343\t5\t$11,490\tabsent\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Factory New)\t$12,387\t$12,387\t1\t$13,836\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Factory New)\t$11,779\t$11,063\t16\t$10,941\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Minimal Wear)\t$11,693\t$11,693\t1\t$9,946\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Minimal Wear)\t$10,437\t$10,437\t1\t$9,610\tabsent\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Blue Laminate (Minimal Wear)\t$9,772\t$37\t76\t$30\t$40\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Minimal Wear)\t$9,463\t$9,463\t1\t$9,500\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Minimal Wear)\t$9,104\t$9,026\t6\t$8,524\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Hedge Maze (Minimal Wear)\t$8,139\t$8,139\t1\t$6,819\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Field-Tested)\t$7,617\t$7,390\t4\t$7,194\tabsent\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Field-Tested)\t$7,615\t$7,615\t1\t$7,100\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Field-Tested)\t$7,149\t$7,006\t2\t$7,165\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Field-Tested)\t$6,711\t$6,194\t15\t$5,988\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Factory New)\t$6,679\t$6,613\t3\t$6,628\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Superconductor (Factory New)\t$6,084\t$6,084\t1\t$7,969\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Battle-Scarred)\t$5,750\t$5,413\t3\t$5,899\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Pandora's Box (Minimal Wear)\t$5,520\t$5,508\t3\t$4,998\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Vice (Factory New)\t$5,385\t$5,158\t2\t$5,700\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Minimal Wear)\t$5,342\t$4,989\t19\t$4,997\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Hedge Maze (Field-Tested)\t$5,334\t$4,862\t5\t$3,724\tabsent\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Vulcan (Factory New)\t$5,275\t$1,418\t12\t$1,280\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Well-Worn)\t$4,978\t$4,978\t1\t$4,942\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Well-Worn)\t$4,931\t$4,931\t1\t$5,445\tabsent\tSkinport CSFloat Steam\nAK-47 | Hydroponic (Factory New)\t$4,802\t$4,351\t2\t$3,648\tabsent\tSkinport CSFloat Steam\n★ Talon Knife | Case Hardened (Minimal Wear)\t$4,588\t$466\t16\t$442\t$630\tSkinport CSFloat Steam\nAWP | Medusa (Factory New)\t$4,484\t$4,484\t1\t$4,171\tabsent\tSkinport CSFloat Steam\n★ Specialist Gloves | Pillow Punchers (Factory New)\t$4,359\t$4,359\t1\t$4,302\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Pandora's Box (Field-Tested)\t$4,359\t$3,666\t11\t$3,245\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Field-Tested)\t$4,289\t$4,225\t8\t$4,022\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Battle-Scarred)\t$4,124\t$4,124\t1\t$4,279\tabsent\tSkinport CSFloat Steam\n같은 상품, 같은 ‘90’ 기간인데도 가격이 천차만별\n\n100의 중간값을 가지며 완료된 판매 건수가 5건 이상인 아이템으로만 제한했습니다. 저렴한 스킨의 경우, 단 한 건의 이례적인 판매만으로도 비율이 크게 왜곡되기 때문입니다. 남은 아이템들은 주로 표면 경화 마감 시, 패턴이 가격을 결정하고 시장 플랫폼은 모든 패턴을 하나의 이름으로 분류합니다. 이는 05. 절에서 float로 측정된 것과 동일한 메커니즘입니다.\n\n항목\t최고값 대 중앙값\t최고 판매량\t판매 중위값\t판매\t한 번 확인해 보세요\n★ Talon Knife | Case Hardened (Minimal Wear)\t+884%\t$4,588\t$466\t16\tSkinport CSFloat Steam\nDesert Eagle | Cobalt Disruption (Factory New)\t+859%\t$1,210\t$126\t115\tSkinport CSFloat Steam\nAWP | BOOM (Minimal Wear)\t+814%\t$1,232\t$135\t89\tSkinport CSFloat Steam\nAK-47 | Case Hardened (Well-Worn)\t+769%\t$1,720\t$198\t70\tSkinport CSFloat Steam\nAWP | Graphite (Factory New)\t+761%\t$1,469\t$171\t124\tSkinport CSFloat Steam\n★ Talon Knife | Case Hardened (Field-Tested)\t+509%\t$2,437\t$400\t48\tSkinport CSFloat Steam\n★ Kukri Knife | Case Hardened (Minimal Wear)\t+448%\t$723\t$132\t69\tSkinport CSFloat Steam\n★ Kukri Knife | Case Hardened (Field-Tested)\t+415%\t$549\t$106\t128\tSkinport CSFloat Steam\n★ Ursus Knife | Case Hardened (Minimal Wear)\t+371%\t$597\t$127\t12\tSkinport CSFloat Steam\nAK-47 | Case Hardened (Field-Tested)\t+369%\t$1,037\t$221\t125\tSkinport CSFloat Steam\nAK-47 | Red Laminate (Minimal Wear)\t+360%\t$552\t$120\t18\tSkinport CSFloat Steam\nAWP | Asiimov (Field-Tested)\t+351%\t$528\t$117\t439\tSkinport CSFloat Steam\nAK-47 | Vulcan (Field-Tested)\t+337%\t$865\t$198\t241\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Nightwish (Factory New)\t+322%\t$625\t$148\t31\tSkinport CSFloat Steam\nAWP | Lightning Strike (Factory New)\t+319%\t$2,065\t$493\t198\tSkinport CSFloat Steam\nStatTrak™ AWP | Redline (Minimal Wear)\t+312%\t$574\t$139\t24\tSkinport CSFloat Steam\nStatTrak™ AWP | Asiimov (Battle-Scarred)\t+287%\t$524\t$135\t37\tSkinport CSFloat Steam\nAK-47 | Redline (Minimal Wear)\t+277%\t$562\t$149\t112\tSkinport CSFloat Steam\nAWP | Crakow! (Factory New)\t+275%\t$379\t$101\t72\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Vulcan (Factory New)\t+272%\t$5,275\t$1,418\t12\tSkinport CSFloat Steam\n\n이는 90-에서 기록된 당일 최고치일 뿐, 사상 최고치는 아니며, 단 하나의 마켓플레이스만을 대상으로 한 것입니다. 이 자료집 어디에도 사상 최고치를 주장하는 내용은 없습니다. Skinport 판매 내역이 없는 품목은 이 전시 자료에서 완전히 제외되었기 때문에, 이 세트의 규모가 전체 집계보다 작은 것입니다.\n\n확인 링크는 카탈로그 자체의 플랫폼 식별자를 기반으로 생성됩니다. 이 링크들은 해당 상품의 각 마켓플레이스 페이지로 연결되므로, 독자는 저희 사이트가 아닌 원본을 통해 해당 정보를 확인할 수 있습니다. 외부 링크는 rel=\"nofollow\": 이는 인용일 뿐, 추천이 아니며, 해당 목적지 중 몇 군데는 본 조사에서 비판의 대상이 된 마켓플레이스들입니다.\n\n09 / 출처와 한계\n이것이 어디서 비롯된 것인지, 그리고 무엇을 보여줄 수 없는지\n\n이 페이지에 있는 모든 수치는 해시 값이 함께 공개된 두 개의 스냅샷 파일을 바탕으로 재계산된 것입니다. 여기에는 다른 사이트의 기사에서 전재한 내용은 전혀 없습니다.\n\n출처 및 접근\n\ncs2.sh, API, GET /v1/prices/latest 및 GET /v1/schema, 단일 스냅샷, 캡처 시점: 2026-09-23T00:44:27.871388581Z, 가격은 USD로 표시됨.\n\n해당 데이터는 아카이브에 기록된 ‘GDPR’ 요청자가 보유한 유료 상업용 구독 계약을 통해, 제공업체의 자체 약관에 따라 확보되었습니다. 어떤 마켓플레이스도 스크래핑되지 않았으며, 어떤 마켓플레이스의 인증 정보도 사용되지 않았습니다. 요청자의 키는 이 저장소 외부에 보관되어 있으며, 이 저장소 내의 어떤 파일에도 나타나지 않습니다.\n\n품목의 자격 요건\n\nBUFF, CSFloat, Skinport, YouPin 또는 C5Game에 활성 매도 호가가 하나 이상 있는 모든 기본 아이템은 가장 저렴한 매도 호가에 따라 가격 대역에 배정되므로, 해당 대역은 Steam에 절대 좌우되지 않습니다. “Steam 커버리지”란 데이터 수집 시점에 해당 대역 내 아이템 중 활성 Steam 매도 호가를 가진 아이템의 비율을 의미합니다. 패턴 및 단계별 변형 상품은 Steam에서 별도로 나열하지 않기 때문에 순위표에서 제외됩니다. 이를 포함할 경우 Steam의 수치가 과소평가될 수 있습니다. 렌더링 이미지는 동일한 상품에 대한 카탈로그 이미지로, 로컬에 저장되어 있습니다.\n\n렌더링 이미지와 이미지 저작권. 카탈로그 상품 렌더링 이미지는 가격 행과 동일한 market_hash_name에 대해 제공되는 공급자의 이미지로, 오프라인 및 IPFS 표시를 위해 로컬에 저장됩니다. 이 렌더링 이미지는 PhishDestroy의 저작물이 아닙니다. 모든 상품 이미지, 로고 및 스크린샷의 소유권은 해당 소유자(cs2.sh, CSFloat, Skinport, BUFF, YouPin, C5Game, Valve 등)에게 있습니다. 이 자료들은 식별 및 공익적 보도를 목적으로만 재생산된 것이며, 어떠한 소유권이나 라이선스도 주장하지 않습니다.\n\n우리가 얻지 못한 것\n\n사용된 구독 등급은 현재 스냅샷에만 적용됩니다. 과거 데이터 및 아카이브 엔드포인트는 사용할 수 없었으며, 이 페이지 어디에도 과거 데이터 시리즈에 대한 주장은 없습니다. “트레일링 윈도우 매출”을 넘어, Skinport은 06. 섹션에 게시됩니다.\n\n단일 스냅샷일 뿐, 시계열 데이터가 아닙니다. 캡처 시점에 Steam에 상품이 등록되어 있지 않다고 해서 해당 상품이 절대 그곳에 등장하지 않을 것이라는 증거는 아닙니다. 이는 그 순간 서가의 상태를 측정한 것에 불과하며, 상한선을 초과하는 가격의 경우 Valve에서 공표한 규칙이 요구하는 사항이기도 합니다. Valve의 커뮤니티 마켓은 상품당 등록 가격을1,800로 명시적으로 제한하고 있습니다(Steam 지갑 잔액은 최대2,000까지 허용됨; 참조: Steam 커뮤니티 마켓 자주 묻는 질문 보관됨 2026-09-21 ↗ 그리고 Steam 가입자 계약서 § 3.C 보관됨 2026-09-24 ↗).\n\n채점\n\n상품의 가격은 항상 해당 상품의 가장 저렴한 실시간 매도 호가이므로, 높은 이상값이 총액을 부풀릴 수는 없습니다. 등급 분류에 따라 어떤 행의 호가가 인용될 수 있는지 결정됩니다. 동일 상품의 가장 저렴한 매도 호가보다 3배 이상 높은 호가는 실시간 가격이 아닌 것으로 간주되어 제외됩니다. 등급 A: 3개 이상의 마켓플레이스가 여전히 상한선 이상의 호가를 제시하고 있으며, 그 중앙값이 최저가 대비 25% 이내에 위치하는 경우. 등급 B: 2개의 마켓플레이스가 일치하거나, 3개가 다소 느슨하게 일치하는 경우. 등급 C: 단일 호가 — 시장 가격이 아닌 요청 가격. 본 보고서에서는 등급 A와 B만 인용됩니다.\n\n이상치 규칙: 호가 > 3.0× 해당 종목의 최저 매도 호가.\n\n합계가 하한값인 이유\n\n각 마켓플레이스별로 해당 상품의 가장 낮은 매도 호가는 해당 선반에 등재된 매물 수만큼 곱해집니다. 그곳의 다른 모든 매물은 그 최저 매도 호가 이상으로 가격이 책정되어 있으므로, 실제 게시된 가격은 추정치가 아닌 구조상 더 높은 것입니다. 이는 판매도, 현금 흐름도, CS2 경제의 가치 평가도 아닙니다.\n\n직접 확인해 보세요\n\n이 페이지의 모든 차트에 사용된 원본 데이터 세트는 전체 내용이 공개되어 있습니다: 아틀라스 데이터셋, 등급 및 아티팩트 화면, 기본 인구조사 그리고 각 원시 스냅샷의 SHA-256가 포함된 매니페스트.\n\n개장 시 기록된 조정\n\n이 등록부의 초기 초안에는 한 중국 마켓플레이스에서 Souvenir AK-47 | Point Disarray가 $148,954에 매물로 올라온 반면, Steam에서는 $119.에 책정된 내용이 맨 앞에 실렸습니다. 해당 항목은 C등급입니다: 단일 판매처, 단 한 점뿐이며, 다른 마켓플레이스에서 일치하는 가격이 없습니다. 이는 실제 가격이 아닌 호가일 뿐이며, 이곳과 해당 페이지에서 등급이 하향 조정되었습니다. 확인된 최저가는 Sticker | Titan (Holo) | Katowice 2014로, $66,285, 4에서 인용한 바에 따르면, 두 마켓플레이스는 5.2%에서 서로 가까운 거리에 위치해 있지만, Steam에는 아예 존재하지 않습니다.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "스킨 가격 사다리 아틀라스 — 유동성 절벽"
          },
          {
            "level": 2,
            "id": null,
            "text": "절벽은 요구에 따라가 아니라 규칙에 따라 형성된다"
          },
          {
            "level": 3,
            "id": null,
            "text": "해당 형태가 배제하는 것"
          },
          {
            "level": 2,
            "id": null,
            "text": "매도 희망가는 가격이 아니다"
          },
          {
            "level": 3,
            "id": null,
            "text": "A  세 개 이상의 선반이 일치합니다"
          },
          {
            "level": 3,
            "id": null,
            "text": "B  두 선반이 일치합니다"
          },
          {
            "level": 3,
            "id": null,
            "text": "C  선반 하나 — 사용하지 않음"
          },
          {
            "level": 3,
            "id": null,
            "text": "이번 조정으로 인한 손실과 그 대가로 얻은 것"
          },
          {
            "level": 3,
            "id": null,
            "text": "유물로 지정된 목록"
          },
          {
            "level": 2,
            "id": null,
            "text": "419의 모든 카테고리와 각 가격이 지칭하는 대상"
          },
          {
            "level": 2,
            "id": null,
            "text": "Steam가 취급하지 않는 상품을 진열하는 선반들"
          },
          {
            "level": 2,
            "id": null,
            "text": "실제로 공급이 얼마나 부족한가"
          },
          {
            "level": 2,
            "id": null,
            "text": "제3자 판매 대행 업체들이 실제로 달성한 실적"
          },
          {
            "level": 2,
            "id": null,
            "text": "16년 된 스티커와 한 줌의 장갑"
          },
          {
            "level": 2,
            "id": null,
            "text": "상승세는 상장 때문이 아니라 거래에 힘입은 것"
          },
          {
            "level": 3,
            "id": null,
            "text": "해당 기간 동안 성사된 매출액 상위 30건"
          },
          {
            "level": 3,
            "id": null,
            "text": "같은 상품, 같은 ‘90’ 기간인데도 가격이 천차만별"
          },
          {
            "level": 2,
            "id": null,
            "text": "이것이 어디서 비롯된 것인지, 그리고 무엇을 보여줄 수 없는지"
          },
          {
            "level": 3,
            "id": null,
            "text": "출처 및 접근"
          },
          {
            "level": 3,
            "id": null,
            "text": "품목의 자격 요건"
          },
          {
            "level": 3,
            "id": null,
            "text": "우리가 얻지 못한 것"
          },
          {
            "level": 3,
            "id": null,
            "text": "채점"
          },
          {
            "level": 3,
            "id": null,
            "text": "합계가 하한값인 이유"
          },
          {
            "level": 3,
            "id": null,
            "text": "직접 확인해 보세요"
          },
          {
            "level": 3,
            "id": null,
            "text": "개장 시 기록된 조정"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/ko/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/ko/skin_atlas#gallery",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://skinport.com/market?search=AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260924114457/https://store.steampowered.com/subscriber_agreement/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-atlas.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-artefact-screen.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-above-the-ceiling.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ko/skin_atlas.content.json",
      "export_json_sha256": "c2d4651d110f78d7b8c39bf57ed8e213f91d8ab99e5709a97a4cbedd372c27f8"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ko/social_graph.html",
      "language": "ko",
      "title": "기록된 연결 고리를 따라가 보자 — ‘Steam’ 관련 자료집",
      "source_url": "https://phishdestroy.io/steam_dossier/ko/social_graph",
      "source_html_sha256": "d8ba468f0687529fcaa879f379b53ccb864998992c06d52b107637c512f13bf4",
      "exported_at": "2026-09-29T00:21:59.537Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "social_graph.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ko/social_graph.pdf?v=print-20260929-v5",
        "sha256": "a07ec68d1921742368a5384a0503218750b829accbdd0858d1f887b566709dbc",
        "bytes": 121981,
        "pages": 6
      },
      "integrity": {
        "signed_object": "social_graph.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "social_graph.content.json.asc",
        "digest_file": "social_graph.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify social_graph.content.json.asc social_graph.content.json",
          "sha256sum -c social_graph.content.json.sha256"
        ]
      },
      "content": {
        "text": "연결 고리를 따라가 보세요.각 관계를 하나씩 검토하십시오.\n\n프로필을 검색합니다. 관계 유형을 선택합니다. 검색 결과에 포함된 기록에서 해당 프로필과 직접 연결된 이웃들을 확인합니다. 연구 도구: 에지는 공개적인 관계를 나타낼 뿐, 두 노드 간의 직접적인 접촉, 비공개적인 협의 또는 부적절한 행위의 증거는 아닙니다. ‘3,435-’ 노드 레이아웃은 필터를 적용하여 해석하는 것이 가장 좋습니다.\n\n한 번에 한 가지 관계씩 살펴보세요\n\n💡 노드를 클릭하고 드래그하여 그래프의 배열을 변경할 수 있습니다. 마우스를 올려놓으면 상세 프로필을 확인할 수 있습니다. 청록색 실선 = 친구 관계, 호박색 점선 = 상호 댓글.\n\n관계 유형프로필 및 바로 옆집\n\n3,435 프로필 · 4,551 저장된 링크\n\n프로필을 검색하여 선택하거나 노드를 클릭하세요. 해당 노드의 직접 연결된 이웃들만 남게 됩니다. 에지는 관계를 기록할 뿐, 비공개적인 조정을 형성하지는 않습니다.\n\n수집된 데이터 세트의 프로필\n\n전체 원본 표: 3,435의 모든 행 다운로드 (CSV). 아래 표에는 처음에 25의 첫 번째 행들이 표시되어 있으며, 검색 및 페이지 분할 기능을 통해 전체 데이터 세트를 확인할 수 있습니다.\n\n1–25 /3,435행\n페르소나 이름\tSteamID64\t개인정보 보호\t상태\t단체 회원권\t재고액 (USD)\t위치\nMahatma Gandhi\t76561198333721623\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tPH\nGalley//갤리🌠🌙\t76561198043416832\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tKP\n$Schlächter\t76561198860277343\tPUBLIC\tClean\tsteambans\t$0.00\tUnknown\n❄r3dsn0w000™❄ [Cristi]🎮\t76561197986767957\tPUBLIC\tClean\tCommunityLegends\t$0.00\tRO\n(2a03) Wolfy\t76561197991671851\tPUBLIC\tCommunity\tsr_public\t$0.00\tUS\nZloy2288\t76561198038578334\tPUBLIC\tClean\tsteambans\t$0.00\tBY\njessy\t76561198039125237\tPUBLIC\tCommunity, VAC (1x)\tCommunityLegends\t$0.00\tJP\nJithraRufure\t76561198071896910\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\n| Níllerdínho |\t76561198003487438\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tDK\nJones is back\t76561198023013026\tPRIVATE\tVAC (1x)\tsteambans\t$0.00\tUnknown\nUNEX | ★✠☠ MoH3st ☠✠\t76561198050763123\tPUBLIC\tClean\tsteambans\t$0.00\tDE\nTrojan\t76561198048457084\tPUBLIC\tClean\tCommunityLegends\t$0.00\tDE\n𝗠𝗮𝘆𝘂 ❤\t76561199377967696\tPUBLIC\tClean\tsr_public\t$0.00\tIS\nbig fucking idiot\t76561198871206397\tPUBLIC\tVAC (1x)\tsteambans\t$0.00\tUnknown\nSOFF Games\t76561198227129276\tPUBLIC\tClean\tcommunitymoderators\t$0.00\tRU\nThijminecraft02\t76561198253895669\tPUBLIC\tClean\tSteamIDcouk SArchive\t$0.00\tNL\nStatic-sama\t76561198289329793\tPUBLIC\tClean\tsteambans\t$0.00\tJP\n𝙸mmortal 𝚂targazer\t76561198142116760\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\nCommander Keen\t76561197987773287\tPUBLIC\tClean\tsteambans\t$0.00\tBE\nS1mX\t76561199648509165\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\nmixwell\t76561199276547472\tPUBLIC\tClean\tsr_public\t$0.00\tJP\nP90_GOD_YyEs™\t76561198285821942\tPUBLIC\tClean\tsteambans\t$0.00\tHK\nhewwo?\t76561199133807546\tPUBLIC\tVAC (1x)\tsteambans\t$0.00\tCH\n♕Kamikaze Atze♕\t76561198002700103\tPUBLIC\tClean\tsteambans\t$0.00\tDE\nPastica\t76561198154655970\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tDZ\n기록된 우정 관계\n\n전체 원본 표: 4,299의 모든 행 다운로드 (CSV). 아래 표에는 처음에 25의 첫 번째 행들이 표시되어 있으며, 검색 및 페이지 분할 기능을 통해 전체 데이터 세트를 확인할 수 있습니다.\n\n1–25 /4,299행\n사용자 A\t방향\t사용자 B\t관계 유형\nMahatma Gandhi\n76561198333721623\t↔\tDeskjet\n76561198272738437\tMutual Friends\nGalley//갤리🌠🌙\n76561198043416832\t↔\tomega\n76561197960274529\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tFisty\n76561198057301486\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tFaalagorn\n76561198001116101\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tMURK\n76561198036995672\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tÅρøᴛʜℯᴛȋᴄÅʟȋℯη ♛👽♛\n76561197984615267\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tsilatrak\n76561197999629462\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tBlack Blade\n76561198083368493\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tAvenger\n76561197978249317\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tRemtar\n76561198124322650\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tCato\n76561197961345984\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t✪ G λ M Ξ ®\n76561197994308495\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tclees42\n76561198030936806\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t𝓜ε𝔰𝔥 | AusLevels\n76561198108828539\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tSgtFopper™\n76561198002555892\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t❥Miss Bee\n76561198046958996\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tTesTy\n76561198032370068\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tskl_andrey\n76561198136881436\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t\"Exekutor\"\n76561198009583947\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tAraripe\n76561198103754372\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tsteve6678\n76561198053200093\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\ttrinner\n76561197970359081\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tSteph S.\n76561198025653291\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tKirito\n76561198154545657\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tDoc. todt\n76561197984492467\tMutual Friends\n기록된 댓글 링크\n\n전체 원본 표: 252의 모든 행 다운로드 (CSV). 아래 표에는 처음에 25의 첫 번째 행들이 표시되어 있으며, 검색 및 페이지 분할 기능을 통해 전체 데이터 세트를 확인할 수 있습니다.\n\n1–25 /252행\n저자\t방향\t대상 프로필\t날짜\t댓글 내용\nDeskjet\n76561198272738437\t→\tMahatma Gandhi\n76561198333721623\t16 September, 2021 @ 11:02:05 pm PDT\t\"𝑵𝒐𝒘 𝒊𝒇 𝑰 𝒇𝒖𝒄𝒌 𝒕𝒉𝒊𝒔 𝒎𝒐𝒅𝒆𝒍𝑨𝒏𝒅 𝒔𝒉𝒆 𝒋𝒖𝒔𝒕 𝒃𝒍𝒆𝒂𝒄𝒉𝒆𝒅 𝒉𝒆𝒓 𝒂𝒔𝒔𝒉𝒐𝒍𝒆𝑨𝒏𝒅 𝑰 𝒈𝒆𝒕 𝒃𝒍𝒆𝒂𝒄𝒉 𝒐𝒏 𝒎𝒚 𝑻-𝒔𝒉𝒊𝒓𝒕𝑰'𝒎𝒎𝒂 𝒇𝒆𝒆𝒍 𝒍𝒊𝒌𝒆 𝒂𝒏 𝒂𝒔𝒔𝒉𝒐𝒍𝒆\" - Nelson Mandela\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t22 November, 2021 @ 4:10:28 pm PDT\thttps://anige.horigiri.net/?cat=22\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t18 November, 2021 @ 12:45:26 am PDT\thttps://gamerch.com/umamusume/entry/250411\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t8 August, 2021 @ 4:13:25 am PDT\thttps://modoocode.com/304\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t6 February, 2021 @ 3:35:05 pm PDT\t▤ ∫︹- -ω⁾ ⁽︹▓▓︺\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t11 December, 2019 @ 1:50:53 am PDT\thttps://blog.naver.com/aksenwlddj12/221369410039\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t2 October, 2019 @ 7:11:59 am PDT\tǤαllєу║︎갤리..۩\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t9 April, 2019 @ 12:51:28 pm PDT\tExplosiveDamage(owner, from, maxrange, minrange, distmultiplier, dmgmultiplier, mindamage, typ, damagetype, ignore)\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 12:22:47 pm PDT\tinfo - sh_titles.lua\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 12:21:46 pm PDT\tlocal nibbas = 1344 init.lua\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 11:31:58 am PDT\thttp://foreign.aladin.co.kr/shop/wproduct.aspx?ItemId=123955531&start=slayer\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t3 April, 2019 @ 1:26:41 am PDT\tǤαllєу\nLei\n76561198982197954\t→\tJithraRufure\n76561198071896910\t29 December, 2024 @ 12:58:08 pm PDT\t+rep he knows how 2 rush B ￣ヘ￣\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t2 September, 2026 @ 5:16:55 am PDT\tlol\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t20 August, 2026 @ 6:11:03 am PDT\t?\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t25 July, 2026 @ 7:20:05 am PDT\thahahahaha\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t30 June, 2026 @ 12:52:42 pm PDT\twow\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t30 June, 2026 @ 12:41:32 pm PDT\txD\nvalorant enjoyer\n76561199112142402\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:26:30 pm PDT\toh no!!\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:26:11 pm PDT\toh no!!\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:22:22 pm PDT\tomg !!! they know my secret, omg!!!\nvalorant enjoyer\n76561199112142402\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:21:39 pm PDT\t+rep good ♥♥♥♥♥ player\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:20:50 pm PDT\tomg! u cant cheat on secure gaben servers, omg dont report me, they ban me for boosted omg\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 8:37:11 pm PDT\txD\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t28 June, 2026 @ 1:58:14 pm PDT\twow",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "연결 고리를 따라가 보세요.각 관계를 하나씩 검토하십시오."
          },
          {
            "level": 2,
            "id": null,
            "text": "한 번에 한 가지 관계씩 살펴보세요"
          },
          {
            "level": 2,
            "id": null,
            "text": "수집된 데이터 세트의 프로필"
          },
          {
            "level": 2,
            "id": null,
            "text": "기록된 우정 관계"
          },
          {
            "level": 2,
            "id": null,
            "text": "기록된 댓글 링크"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-profiles.csv",
          "https://steamcommunity.com/profiles/76561198333721623",
          "https://steamcommunity.com/profiles/76561198043416832",
          "https://steamcommunity.com/profiles/76561198860277343",
          "https://steamcommunity.com/profiles/76561197986767957",
          "https://steamcommunity.com/profiles/76561197991671851",
          "https://steamcommunity.com/profiles/76561198038578334",
          "https://steamcommunity.com/profiles/76561198039125237",
          "https://steamcommunity.com/profiles/76561198071896910",
          "https://steamcommunity.com/profiles/76561198003487438",
          "https://steamcommunity.com/profiles/76561198023013026",
          "https://steamcommunity.com/profiles/76561198050763123",
          "https://steamcommunity.com/profiles/76561198048457084",
          "https://steamcommunity.com/profiles/76561199377967696",
          "https://steamcommunity.com/profiles/76561198871206397",
          "https://steamcommunity.com/profiles/76561198227129276",
          "https://steamcommunity.com/profiles/76561198253895669",
          "https://steamcommunity.com/profiles/76561198289329793",
          "https://steamcommunity.com/profiles/76561198142116760",
          "https://steamcommunity.com/profiles/76561197987773287",
          "https://steamcommunity.com/profiles/76561199648509165",
          "https://steamcommunity.com/profiles/76561199276547472",
          "https://steamcommunity.com/profiles/76561198285821942",
          "https://steamcommunity.com/profiles/76561199133807546",
          "https://steamcommunity.com/profiles/76561198002700103",
          "https://steamcommunity.com/profiles/76561198154655970",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-connections.csv",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-comments.csv"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ko/social_graph.content.json",
      "export_json_sha256": "a018b673237f584d4647d8151f1230d2cedc11c744391e3d662629721dc8cd43"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ko/steam_enforcement_evidence.html",
      "language": "ko",
      "title": "규칙 대 대응 — ‘Steam’ 특집",
      "source_url": "https://phishdestroy.io/steam_dossier/ko/steam_enforcement_evidence",
      "source_html_sha256": "7a583714e1321484026be9a4c0def64a5aad7a0f956701a692cf33a054d0e426",
      "exported_at": "2026-09-29T00:22:02.108Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "steam_enforcement_evidence.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ko/steam_enforcement_evidence.pdf?v=print-20260929-v5",
        "sha256": "87c274bcc49d33ca076a4542ef84d2b8a5de94d27cd44d2ba14c2047e6e8b389",
        "bytes": 376659,
        "pages": 36
      },
      "integrity": {
        "signed_object": "steam_enforcement_evidence.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "steam_enforcement_evidence.content.json.asc",
        "digest_file": "steam_enforcement_evidence.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify steam_enforcement_evidence.content.json.asc steam_enforcement_evidence.content.json",
          "sha256sum -c steam_enforcement_evidence.content.json.sha256"
        ]
      },
      "content": {
        "text": "증거 보충 자료 / 출처 연계 기록\nSteam 집행 증거 — 지원 기록 및 개발자 네트워크\n\n규칙. 답변.\n\n이 섹션이 입증하는 바\n\n이 증거 자료실에서는 Valve의 공식 가입자 계약서를, 날짜가 기재된 제재 기록, 지원 분쟁 해결 내역, 그리고 252 저장소 및 3,320 프로필 전반에 걸친 개발자 네트워크 기록과 대조하여 분석합니다. 이를 통해 일반 계정 소유자는 세션이 해킹당할 경우 반박할 수 없는 제재 및 지원 중단 조치를 받는 반면, 대규모 상업용 봇 운영은 공공 인프라에 대한 접근 권한을 유지한 채 지속적으로 운영되고 있음을 보여줍니다.\n\n← 경영진 브리핑으로 돌아가기\n\n서면으로 제시된 제한 사항을 읽어보세요. 기록된 답변을 열어보세요. 원문에 나와 있는 내용과 아직 답변되지 않은 부분을 비교해 보세요.\n\n지원 및 항소 ↓공공 인프라 ↓\n252저장소 기록\n3,320공개 프로필\n4,214서로 다른 프로필-저장소 쌍\n98,902공유 저장소를 가진 프로필 쌍\n01 / 지원, 제재 및 복구\n고소장을 읽어보세요.원본 파일을 첨부해 두세요.\n지원 거절 갤러리 (981 전시물) ↗선택한 기록 다운로드 ↓\nHFB / 아웃소싱 사례널리 인정받는 타협안.\n보도에 따르면 해고가 있었다고 한다.\n\n재게시된 지원 답변과 계약업체 직원에 대한 주장의 출처를 확인해 주십시오.\n\n케이스와 관련 출처를 열어보세요 →\n\n아래: 보존된 5점 공개된 Reddit 게시물 제공된 지원 기록 모음에서 발췌한 것입니다. 각 기록은 Valve의 지원 시스템에 접수된 상호작용을 기록한 것으로, 원본 출처 링크, 캡처 위치 및 전체 텍스트가 그대로 보존되어 있습니다. 이는 피해자들의 증언입니다. 이를 확인하거나 반박할 수 있는 인증된 지원 로그들은 Valve에서 보관하고 있으며, 아직 공개되지 않았습니다.\n\n01\nBan & review2024-12-09\nPermanent sanction & closed appeals\n\nThe author reports a permanent account ban, repeated ticket closures and a planned GDPR access request.\n\nREDDIT / PUBLIC TESTIMONYr/ohnePixelCapture record 294\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 303 words\nPermanently banned Steam account without a clear explanation, need help!\n\nsteam_support_tickets_MEGA.json / record 294\n\nHey everyone,\n\nI’m in a really frustrating situation, and I’m hoping someone here can help me or offer advice. My Steam account was just permanently banned for allegedly violating the Steam Subscriber Agreement, and I have no idea why.\n\n# What Steam Support told me:\n\nThe support message said my account was banned due to:\n\n* Suspicious activities related to transferring or attempting to sell/trade the account.\n* Community reports and other unspecified factors.\n\nThey added that the ban is permanent and that they can't help me further. They also warned that future support requests regarding this ban might be ignored. 😞\n\n# Why I’m contesting this ban:\n\n* I have never sold, traded, or transferred my account. I’ve been the legitimate owner since the beginning.\n* On the day the ban occurred, I did nothing noteworthy that could have triggered such a sanction.\n* I received no prior warning, which feels incredibly unfair.\n\n# What I’ve tried so far:\n\n* Contacting Steam Support: I explained my situation and asked for more details, but they’re sticking to their decision and closing my tickets.\n* I’m preparing a request based on my Right of Access (GDPR) to get all the data related to my account.\n\n# Questions for the community:\n\n1. Has anyone successfully had a permanent ban lifted on Steam?\n2. Are there steps I can take to prove I’m the legitimate owner of the account?\n3. Any advice on how to word my request to convince support to reconsider my case?\n4. Would it be helpful to contact the CNIL (I’m based in France) to force Steam to provide more information?\n\nI’m really desperate at the thought of losing all my games, purchases, and years of playtime. Thanks in advance for any help and advice you can give!\n\nhttps://preview.redd.it/jk9qv0gmhv5e1.png?width=1289&amp;format=png&amp;auto=webp&amp;s=b3a333ebb08ea133e2c8747ba126f5a68283d9f7\n\nhttps://preview.redd.it/4sopt0gmhv5e1.png?width=1022&amp;format=png&amp;auto=webp&amp;s=56195d5336118faf9413f1514ead7e8d24c788c3\n\nhttps://preview.redd.it/eqrxw0gmhv5e1.png?width=996&amp;format=png&amp;auto=webp&amp;s=ff3539d28ab754e513ad471822c5de652920101d\n\nhttps://preview.redd.it/728xz0gmhv5e1.png?width=1034&amp;format=png&amp;auto=webp&amp;s=bc5335673509929669af785aa244bf8d2dc58da8\n\n02\nSupport access2025-05-09\nAccount recovery & a reported $10,000 loss\n\nThe author alleges that support reset credentials and removed account protection following another person’s recovery ticket.\n\nREDDIT / PUBLIC TESTIMONYr/legaladviceCapture record 110\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 193 words\nGot $10k stollen from steam inventory due to steam' support fault.\n\nsteam_support_tickets_MEGA.json / record 110\n\nLocation: Quebec, Canada.\n\nLast year, someone hacked my Steam account and stole items worth about $10,000 USD. I only noticed this last week. When I talked to Steam Support, they admitted that someone submitted a ticket to make changes on the account and Steam Support reset my password and turned off all my account security.\n\nI asked Steam Support about getting my items back, but they said there was nothing they could do. They told me I should follow their security recommendations.\n\nThe problem is, I did everything they \"suggested\" to protect an account:\n\n* I had two-factor authentication.\n* My phone number was connected to my account.\n* I used Steam Guard.\n* I printed recovery codes and kept them in a safe.\n\nEven though I did all these things, Steam Support still gave someone else access to my account. The stolen items had been in my account since around 2016-2017. Also, I had not logged in for a few years, so I didn’t accidentally give my information to a fake website.\n\nIs there anything I can do, or do I just have to accept losing $10,000 USD?\n\nThanks for your help.\n03\nRestoration2022-07-07\nA reported $500+ loss & template replies\n\nThe author describes an account compromise, disputed transactions and a support response that allegedly did not address the submitted evidence.\n\nREDDIT / PUBLIC TESTIMONYr/DotA2Capture record 45\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 410 words\nFunds stolen through steam market. Disappointed with Steam response.(or lackthereof)\n\nsteam_support_tickets_MEGA.json / record 45\n\nOn 6th July 2022, 44 unauthorized transactions were made on the steam market using my steam wallet funds totalling roughly $500+ USD to buy worthless 1 cent Dota 2 items. This happened during the wee hours in the morning and i contacted them first thing when i woke up. \n\nI have 2FA enabled all the time, and always thought this would not happen to me as I do not go on betting sites/click sketchy links. My account password + emails were not changed, nor did they take my inventory, just that my funds were used illicitly. Also when I went to disable other APIs, it says there are no other APIs to disable. Shows that it wasn't through me clicking sketchy links and leaving my account details there. Would have lost the whole account if i did so.\n\nWhat baffles me is how did they bypass my 2FA to login my account? Why doesn't steam market purchases go through 2FA as well? First time in 9 years that this happened to me. My acc was logged in 'BY' 'Vitebsk' during the illicit purchases but I'm based in Asia I gathered all the screenshots and provided in the ticket to steam support. \n\nAll i got was the standard copy paste template reply by Steam Support. Lost $500+ and was not even worthy of having a proper person to look into this. I dont think they even read or take a look at the screenshots cause if they did, they would have come to the realization that what happened was clearly fraud, and with a few clicks, reverse the unauthorized transactions, refund my wallet and ban the hijacker. \n\nOver the years, i've spent quite a fair bit on steam but really, this is the kind of recourse we get when our account is compromised? They just don’t care, sigh. I only expect the bare minimum from Steam and looks like even that is quite far-fetched.\n\nSS: https://imgur.com/a/67frcls \n\nHijacker: https://steamcommunity.com/profiles/76561199141246495\n\nSteam Response: https://imgur.com/a/V6v4maM\n\nI could think of a few ways on how to Improve:\n\n1) Add 2FA to market transactions. (even if its bulk posting or selling of items, just 1 2FA notif is required)\n\n2) Enable accounts to be region locked. (if you are migrating, then have to go through steam support etc)\n\n3) Additional Lock on Steam Wallet. (Another password perhaps?)\n\nEDIT: 2nd ticket in and I have still yet to receive a non robotic copy paste template response from Steam.\n04\nRestoration2021-11-29\nSteam Guard & an item-restoration refusal\n\nA preserved post includes the author’s account of item theft and a support response declining restoration.\n\nREDDIT / PUBLIC TESTIMONYr/DotA2Capture record 58\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 563 words\nMany people are losing item via clicking links where steam guard is enabled and steam support doesn't not restore items.\n\nsteam_support_tickets_MEGA.json / record 58\n\nAccounts are getting compromised and might be their pc as well where Steam market is targeted hence the malicious links . I am assuming these hackers are getting encouraged where steam support is not doing nothing and they are getting away with hacking items.  \nLiterally the guy who is supporting the game which he doesn't get any in game advantage just  cosmetics in game only for the sole purpose of supporting the game so that the game will prosper and become beautiful way  to enjoy weekend. But right now players are getting hacked left right and center and steam support  is copy pasting message where in short they are blaming the guy who clicked link. 1st this is happening because they are not targeting players but they are targeting market since they are selling those stuff for real cash via party website. Steam is a huge company and can eradicate the problem or at least can remove links temporarily  in chat since hackers are targeting .They made us install steam guard by saying we wont help if there is no steam guard now steam guard is not enough to save our inventory now they changed their policy  that they should not click any suspicious links. How would we know if the link is suspicious ? After clicking and getting our inventory stolen right !   \n\"we'd have to duplicate an item to restore it. Duplication lowers the value of all items by reducing their scarcity and inflating the economy, which affects everyone involved in trading and the Market. To maintain the value of everyone’s inventory, we do not restore items. For more information, please see the Steam Item Restoration Policy.\"  \nThey care for millions of people IN STEAM MARKET where as few  are losing items which is going to affect market where the rightful owner bought the items and hacker is going to sell the item via 3rd party website and enjoy ! HOW IRONIC !!  \nThis is the message from support where my frnd got his items stolen via clicking on link  \n   \nHi there,  \n\nThank you for the information and screenshots provided.  \n\nIt appears that the account was compromised, please take the following steps to secure your account and computer:  \n\nScan your computer for viruses, key loggers, spyware, and other malicious code using antivirus software with updated virus definitions.  \nChange the password for the email address that is associated with your Steam account.  \nRegularly reset your Steam account password.  \n\nPlease see our Security Recommendations article.  \n\nIn addition, I’m sorry to hear that your items were removed without your permission. Unfortunately, Steam Support does not restore scammed, lost, or stolen items for any reason.  \n\nSince Steam Support does not remove items from accounts, we'd have to duplicate an item to restore it. Duplication lowers the value of all items by reducing their scarcity and inflating the economy, which affects everyone involved in trading and the Market. To maintain the value of everyone’s inventory, we do not restore items. For more information, please see the Steam Item Restoration Policy.  \n\nTo make sure that a scammer is reported, please report them through the Steam Community. Reporting a scammer through the Steam Community is the best way to prevent them from committing future scams.  \n\nTo learn how to avoid scams or hijackings, please see our Trade Scam article.  \n\nIf you still need assistance, please let us know.\n05\nEnforcement2025-05-11\nSelective enforcement & an unexplained ban\n\nA community member describes a disputed ban and contrasts it with the visibility of commercial gambling promotion.\n\nREDDIT / PUBLIC TESTIMONYr/SteamUncensoredCapture record 107\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 1,208 words\n🚨 Steam Bans Without Reason and Ignores Its Community — What’s Going On?\n\nsteam_support_tickets_MEGA.json / record 107\n\nHey r/Steam,\n\nI’m writing this to share my thoughts and concerns about my friend [moneylead](https://steamcommunity.com/id/moneylead/) and Steam’s policies in general. I spoke with him yesterday about his situation, though I didn’t discuss writing this post with him—I asked last night, but he hasn’t responded yet. I want to highlight that this issue is broader than just his case, and while Steam might make changes in the future (though that’s unlikely), I feel the community needs to understand how far Steam has strayed from its original values. I’m not trying to put moneylead in a tough spot with this thread—all the info I’m sharing is public, nothing secretive. I hope he won’t be upset with me, but the community needs this case to see the bigger picture and how Steam feels completely unaccountable.\n\n**Why Does Steam Ignore Its Community?**  \nWhy does a platform like **Roblox** provide a detailed log of ban reasons, while Steam, which claims to be \"community-driven,\" ignores its community, bans whoever they want, for whatever they want, with no transparency? I looked into Roblox as a popular game—not a direct competitor to Steam—to see how their bans look, and you can check it out yourself: [Roblox Ban Reasons](https://www.google.com/search?q=Roblox+ban). Their bans are clear, detailed, and actually explain what you did wrong. I think most decent gaming communities operate like this—not with support agents named Olga, hired through outsourcing, who only know how to send canned auto-replies. Take cases like St4ck—or my friend **moneylead**. All these unbans, like **St4ck’s** or **Alexanddd’s**, happened behind closed doors with zero comments from Steam. Of course, it’s convenient for Steam to handle everything in secret, so no one knows or sees what’s going on—but this violates Steam’s own community rules and principles.\n\n**Who Is moneylead?**  \nI’ve known [moneylead ](https://steamcommunity.com/id/moneylead/)since around 2021. We played Dota 2 a couple of times, and then I just stayed on his friends list. He’s always been a legit player, bringing revenue to Steam through purchases. He never sold his skins, whether in **Dota or CS2—he wasn’t a trader**. All he did was:\n\n* Buy games and skins.\n* Collect badges to level up his profile.\n\nAccording to [SteamSets](https://steamsets.com/account/76561199080934614), he’s given out 324,000 Steam Points—I think he awarded profile rewards to all his friends in the list (though I’m not 100% sure). I do know he ran contests and gave gifts to friends, always supporting the community.\n\n**Steam’s Unfair Treatment**  \nI’ve seen Steam remove his showcases, avatar, description, and even his country multiple times—just because he’s from **Ukraine**. He has a ton of haters leaving toxic comments on his wall, and Steam seems to favor **Russian** users. Every time he tried to appeal the removal of his showcases or profile description—which didn’t break any rules, just had his Instagram link, and his avatar is the same as it is now—Steam moderators didn’t care. **They don’t care about top players who bring them massive revenue, nor about regular users.**\n\n>*Here’s the worst part: moneylead works in cybersecurity, specifically fighting account theft and phishing. He’s neutralized over 5,000 threats targeting Steam alone. And yet, Steam bans him for \"account hijacking\"?*\n\nIf you roughly calculate moneylead’s contribution to Steam and the community—his profile, level, badges (not skins, you can’t sell those)—is this normal, Steam? Banning people, closing tickets, and ignoring users with a spotless reputation who aren’t involved in any commercial activity, just bringing you profit without taking anything in return?\n\n**Steam’s Double Standards**  \nI’m honestly shocked:\n\n* YouTubers who promote casinos and skin gambling? Steam’s fine with that.\n* A cybersecurity expert who fights scams, doesn’t promote casinos, and openly talks about it on his profile? **Banned with no explanation, ignored, and denied an unban.**\n\nI wonder if Steam deliberately bans a high-level account once a year just because of their impunity—maybe for hype or something. Otherwise, this is just madness. It’s scary to think how many regular players have lost their accounts and skins—not because of scammers, but because of Steam’s desire to ignore, send auto-replies, and do whatever they want.\n\n**How Many Others Are Affected?**  \nHow many others are out there—maybe not as well-known—who just have a few games or skins, get banned for nothing, and receive zero explanation or response? **Is this even legal?** Every other platform provides a detailed log with specific violations, but Steam slaps on the same vague label and sends templated responses.\n\n* How safe is it to buy skins on Steam?\n* What’s the chance Steam will just ban your account for no reason, with no explanation?\n\n**A Message to Valve**  \nI wish moneylead the best in resolving this, but Valve, it’d be great if you remembered what \"community\" means and started following the law. Because right now, it looks like your 30% commission, impunity, and sense of being above the law in the U.S. have given you the idea that you can do whatever you want.\n\nI’m sure there are many others like moneylead and St4ck—people who aren’t public or don’t have the resources to fight back. Let’s unite these cases. **If you’re a U.S. resident who’s been banned by Steam without reason and wants to challenge it, please reach out to me.** I’m finishing my **Juris Doctor (J.D.) program at SMU Dedman School of Law** in Dallas, Texas, and I’m participating in a legal clinical practice under Rule 13 of the Texas Supreme Court.\n\nWhat Steam is doing is absolutely disgusting and illegal, and **I’d be happy to help any gamer (legitimate, with no real violations) who has games or skins with value. This will be beneficial for my practice, and it’s time to put Steam in its place and show them they can’t just dictate their own rules with arbitration**. Let’s take it all the way—not for punishment, but for the sake of the community. Maybe if Steam loses a case, they’ll change their policies and start explaining their actions like most popular gaming communities do. Many of us remember how Steam Support used to recover stolen accounts and ended up “stealing” skins themselves—banning without real reasons is basically the same thing, and that’s a serious accusation.\n\nSo, r/Steam, see you soon. I think you understand what you’re doing and how many people you’ve illegally deprived of their assets. I want to raise this issue—not just for the U.S., but for the entire world. You’ve banned class-action lawsuits? **Welcome to Texas.** I recommend starting to look for licensed attorneys in Texas, because I’d love to discuss your company’s policies, feedback, and support agents named Olga—a name that strongly associates with Russian users. Maybe it’d be easier to move your company to Moscow? But I’d be happy to discuss these critical issues on behalf of the global gaming community.\n\nAlso, I wouldn’t recommend ignoring the lawsuit request that will be sent to your physical address and email address, as the court will proceed without you, and that might upset you—especially since things aren’t going so well for a company with stocks like yours.\n\n**Thanks to everyone who took the time to read this. For those who need real help with an unjust Steam ban without any explanation, I’d be happy to assist. For users from Texas, we can easily file a collective lawsuit against Steam—let’s connect and make it happen.**\n02 / Steam 개발자 네트워크\n공공 인프라.대규모로 녹음되었습니다.\n252의 모든 음반 다운로드 ↓\n\n제공된 output_steam_network 스냅샷은 저장소, 공개된 기여자/포크 관계 및 프로필 중복 정보를 기록합니다. 이는 공개된 기록으로, 무엇이 구축되었는지, 누가 기여했는지, 무엇이 포크되었는지를 보여줍니다. 공개된 기능에 대한 이러한 기록은 ‘Valve’가 반드시 고려해야 할 사항입니다.\n\n저장소 / 설명\t기여자\t포커스\t저장된 프로필\nalliedmodders/amxmodx\n\nAMX Mod X - Half-Life 1 Scripting and Administration\n\n\t40\t40\t80\nalliedmodders/sourcemod\n\nSourceMod - Source Engine Scripting and Administration\n\n\t40\t40\t80\nDoctorMcKay/node-steam-user\n\nAllows interaction with the Steam network via the Steam client protocol\n\n\t40\t40\t80\nFacepunch/Facepunch.Steamworks\n\nAnother fucking c# Steamworks implementation\n\n\t40\t40\t80\nJustArchiNET/ArchiSteamFarm\n\nC# application with primary purpose of farming Steam cards from multiple accounts simultaneously.\n\n\t40\t40\t80\nodota/core\n\nOpenDota: Open source Dota 2 data platform with automated replay parsing\n\n\t40\t40\t80\nodota/dotaconstants\n\ndotaconstants: Static data for Dota applications\n\n\t40\t40\t80\nodota/web\n\nOpenDota: React web UI for Dota 2 statistics using the OpenDota platform\n\n\t40\t40\t80\nsplewis/get5\n\nCS:GO Sourcemod plugin for competitive matches/scrims\n\n\t40\t40\t80\nSteamDatabase/FileDetectionRuleSets\n\n🔎 Rules to detect game engines and other technologies based on Steam depot file lists\n\n\t40\t40\t80\nSteamRE/SteamKit\n\nSteamKit2 is a .NET library designed to interoperate with Valve's Steam network. It aims to provide a simple, yet extensible, interface to perform various actions on the network.\n\n\t40\t40\t80\nValveSoftware/dxvk\n\ndxvk tree containing branches used by Proton\n\n\t40\t40\t80\nValveSoftware/GameNetworkingSockets\n\nReliable & unreliable messages over UDP. Robust message fragmentation & reassembly. P2P networking / NAT traversal. Encryption.\n\n\t40\t40\t80\nValveSoftware/gamescope\n\nSteamOS session compositing window manager\n\n\t40\t40\t80\nValveSoftware/Proton\n\nCompatibility tool for Steam Play based on Wine and additional components\n\n\t40\t40\t80\nValveSoftware/source-sdk-2013\n\nThe 2013 edition of the Source SDK\n\n\t40\t40\t80\nValveSoftware/wine\n\nWine with a bit of extra spice\n\n\t40\t40\t80\nValveSoftware/steam-devices\n\nList of devices Steam and SteamVR will want read/write permissions on, to help downstream distributions create udev rules/etc\n\n\t39\t40\t79\nValveSoftware/steam-audio\n\nSteam Audio\n\n\t38\t40\t78\nalliedmodders/metamod-source\n\nMetamod:Source - C++ Plugin Environment and Detour Library for the Source Engine\n\n\t37\t40\t77\nalliedmodders/sourcepawn\n\nA small, statically typed scripting language.\n\n\t35\t40\t75\nValveSoftware/Fossilize\n\nA serialization format for various persistent Vulkan object types.\n\n\t31\t40\t71\nrlabrecque/Steamworks.NET\n\nSteamworks wrapper for Unity / C#\n\n\t27\t40\t67\nModDota/moddota.github.io\n\nModDota github pages project.\n\n\t26\t40\t66\nodota/parser\n\nReplay parse server generating JSON log events from Dota 2 replay files\n\n\t26\t40\t66\nValveSoftware/steam-for-linux\n\nIssue tracking for the Steam for Linux beta client\n\n\t26\t40\t66\nSteamRE/DepotDownloader\n\nSteam depot downloader utilizing the SteamKit2 library.\n\n\t24\t40\t64\nJustArchiNET/ASF-ui\n\nThe official web interface for ASF\n\n\t23\t40\t63\nadvancedfx/advancedfx\n\nHalf-Life Advanced Effects (HLAE) is a tool to enrich content creation mainly for the Counter-Strike series.\n\n\t22\t40\t62\nalliedmodders/ambuild\n\nAlliedModders C++ Build System\n\n\t23\t39\t62\nSteamDatabase/BrowserExtension\n\n💻 SteamDB's extension for Steam websites\n\n\t21\t40\t61\nodota/mobile\n\nReact Native apps for viewing Dota 2 data on Android/iOS\n\n\t19\t40\t59\nValvePython/steam\n\n☁️ Python package for interacting with Steam\n\n\t18\t40\t58\nskadistats/clarity\n\nComically fast Dota 2, CSGO, CS2 and Deadlock replay parser written in Java.\n\n\t13\t40\t53\nSteamRE/open-steamworks\n\nOpen Steamworks is a set of reverse engineered headers for the Valve's Steam Client. More or less abandoned now that the Steamworks SDK is publically available.\n\n\t13\t40\t53\nValveSoftware/Source-1-Games\n\nSource 1 based games such as TF2 and Counter-Strike: Source\n\n\t13\t40\t53\nalliedmodders/hl2sdk\n\nHalf-Life 2 SDK Mirrors\n\n\t11\t40\t51\nSteamDatabase/steamdb.info-issues\n\n🚱 Issue tracker for the SteamDB website\n\n\t11\t40\t51\nCSGOFloat/inspect\n\nSource Code that Powers the CSFloat Inspect Link API\n\n\t10\t40\t50\nValveSoftware/SteamOS\n\nSteamOS community tracker\n\n\t10\t40\t50\nalliedmodders/source2mod\n\nExperimental\n\n\t40\t9\t49\nsmiley/steamapi\n\nAn unofficial object-oriented Python library for accessing the Steam Web API.\n\n\t9\t40\t49\nSteamDatabase/GameTracking\n\n🛢 Dumping things, so you don't have to\n\n\t8\t40\t48\nValveSoftware/counter-strike_rules_and_regs\n\nCS:GO\n\n\t7\t40\t47\nValveSoftware/openvr\n\nOpenVR SDK\n\n\t6\t40\t46\nSteamDatabase/easy-markdown-editor\n\nEasyMDE: A simple, beautiful, and embeddable JavaScript Markdown editor. Delightful editing for beginners and experts alike. Features built-in autosaving and spell checking.\n\n\t40\t4\t44\nValveSoftware/Dota-2\n\nTracker for issues specific to Linux and Mac in the Reborn client. If you have a general issue or non-system-specific feature request please go to dev.dota2.com\n\n\t6\t38\t44\nValveSoftware/Dota2-Gameplay\n\nPublic Bug Tracker for Dota 2\n\n\t4\t40\t44\nJustArchiNET/ArchiBot\n\nNo description in the capture.\n\n\t16\t27\t43\nztizzlegaming/CSGOWinBig\n\nOpen-source Counter-Strike: Global Offensive jackpot betting website.\n\n\t1\t40\t41\nJustArchiNET/mantis.justarchi.net\n\nMantis Bug Tracker (MantisBT)\n\n\t40\t0\t40\nodota/node-steam-user\n\nAllows interaction with the Steam network via the Steam client protocol\n\n\t40\t0\t40\nModDota/TypeScriptAddonTemplate\n\nDota 2 addon template with TypeScript Panorama and VScripts.\n\n\t9\t29\t38\nValvePython/vdf\n\n📜 Package for working with Valve's text and binary KeyValue format\n\n\t6\t32\t38\nalliedmodders/amtl\n\nAlliedModders C++ Template Library\n\n\t17\t19\t36\nValvePython/dota2\n\n🐸 Python package for interacting with Dota 2 Game Coordinator\n\n\t5\t30\t35\nalliedmodders/stripper-source\n\nStripper:Source\n\n\t13\t21\t34\nAllyans3/steam-market-api-v2\n\nSteam Market API v2 package\n\n\t3\t31\t34\nModDota/dota-tutorial\n\nCustom game DOTA tutorial.\n\n\t11\t23\t34\nodota/blog\n\nNo description in the capture.\n\n\t29\t3\t32\nOpsecGuy/BetterGo\n\nExternal CS:GO cheat written in python.\n\n\t1\t27\t28\npxvr-official/1\n\n無許諾配信 企業理念剽窃 動物の森収益化 大神ミオ権利者削除 戌神権利侵害発言 常闇トワ炎上 夜空メルストーカー被害 建築王サポーター放置 赤十字マーク 魔乃アロエ卒業 一つの中國支持声明 大空昴3Dライブ 無限延期清掃員職業差別 日清コラボ楽曲 musedash非公開 rog案件取り消し 壁画ライブ 丁真 Ding Zhen 郑爽 Zheng Shuang 防护林 与朵小天使w 伊月猫凛 本主萌埋午休傻 汪峰 重生细胞 壁纸 比利海灵顿 香蕉君 van 田所浩二 抽象带篮子 抗压背锅吧 季子越 蒋明辉 傻逼…\n\n\t0\t28\t28\nRevadike/InternalSteamWebAPI\n\nDocumenting the unofficial and internal Steam Web API\n\n\t1\t27\t28\nJoeSzymkowiczFiveM/qb-lootcrate\n\nA CSGO-style case opening script\n\n\t2\t25\t27\nAbrarKL/MyRoulette.XYZ\n\nCSGO / Steam Roulette Site created with PHP and Node JS, using the Material Design front-end framework.\n\n\t1\t25\t26\nJustArchiNET/ASF-WebConfigGenerator\n\nNo description in the capture.\n\n\t10\t15\t25\nModDota/dota-data\n\nAuto-generated Dota 2 resource dumps\n\n\t11\t14\t25\nModDota/TypeScriptDeclarations\n\nTypeScript declarations for Dota 2.\n\n\t11\t14\t25\nModDota/API\n\nNo description in the capture.\n\n\t12\t12\t24\nalliedmodders/cssdm\n\nCounter-Strike:Source Deathmatch\n\n\t10\t13\t23\nSteamDatabase/steamstat.us\n\n✅ Front-end of Steam services status website\n\n\t4\t18\t22\nc0deina/csgojackpotV2\n\nCSGO Jackpot Source\n\n\t1\t20\t21\nValvePython/steamctl\n\n🤸 Take control of Steam from your terminal\n\n\t2\t19\t21\nValvePython/csgo\n\n🔫 Python package for interacting with CS:GO Game Coordinator\n\n\t3\t17\t20\nBeepIsla/csgo-crash-exploit\n\nAllows you to crash any Windows user\n\n\t3\t16\t19\nValvePython/vpk\n\n📦 Open, Search, Extract and Create VPKs in python\n\n\t4\t15\t19\nalliedmodders/SM-SteamWorks\n\nExposing SteamWorks functions to SourcePawn.\n\n\t14\t3\t17\nSteamRE/Steam4NET\n\nSteam4NET is a .NET wrapper around the Steamworks C++ interfaces\n\n\t2\t15\t17\nalliedmodders/hl2sdk-manifests\n\nInformation about HL2SDKs shared between Metamod:Source and SourceMod.\n\n\t6\t10\t16\nJustArchiNET/ASF-PluginTemplate\n\nTemplate repository that you can use for creating custom plugins for ArchiSteamFarm.\n\n\t8\t7\t15\nModDota/Dota2AIFramework\n\nGeneral Framework for Dota 2 AI Competitions\n\n\t1\t14\t15\nShkyyl/KeyChamp\n\nExtension for joining free case battle on key-drop automatically\n\n\t1\t14\t15\nSteamDatabase/SteamMonitor\n\n😤 Track Steam's connection manager servers status\n\n\t2\t12\t14\nBaterka/cslore.com\n\nCS:GO gambling site - csgo.style\n\n\t1\t12\t13\nSteamDatabase/SteamTokenDumper\n\n🔢 Submit users' PICS access tokens to SteamDB\n\n\t2\t11\t13\nmonoblocker/roulette\n\nRoulette CS:GO made in React and Typescript\n\n\t1\t11\t12\nzsith/launcher.user.js\n\n// ==UserScript== // @name AposLauncher // @namespace AposLauncher // @include http://agar.io/* // @version 3.062 // @grant none // @author http://www.twitch.tv/apostolique // ==/UserScript== var aposLauncherVersion = 3.062; Nu…\n\n\t1\t11\t12\nLincolnIT/CSGODouble-bot-automated\n\nCSGODouble Automated, auto Betting Bot.\n\n\t1\t10\t11\nvladpuz/steam-market\n\nSteam market API client\n\n\t4\t7\t11\nmcgrizzz/Cstrike.bet\n\nCSGO Roulette Website Angular frontend, nodejs backend, and steam trading bots\n\n\t1\t9\t10\nodota/underlords-web\n\nUI for OpenUnderlords\n\n\t5\t5\t10\nSteamDatabase/SteamToTwitter\n\n🕊 Tweets announcements from various Steam groups\n\n\t1\t9\t10\nModDota/AbilityLuaSpellLibrary\n\nThe successor to the Spell Library by Pizzalol\n\n\t4\t4\t8\nalvinl/bitskins\n\nUnofficial BitSkins API client\n\n\t2\t5\t7\nb1naryth1ef/steamy\n\nA Python Steam community and market API interface that will get you all hot and bothered\n\n\t2\t5\t7\nkratos1812/Case-Opening\n\nIn-game case opening system for CSGO servers.\n\n\t2\t5\t7\nodota/docs\n\nOpenDota API documentation\n\n\t4\t3\t7\nSteamDatabase/steam-advanced-access-fetch-players\n\n📈 Simple script to fetch Steam player count\n\n\t1\t6\t7\nTheRioMiner/CsgoBetterExternalRaytrace\n\nOverridden maps pack for better external raytrace\n\n\t1\t6\t7\nalliedmodders/hl2sdk-mock\n\nMock HL2SDK and Server\n\n\t5\t1\t6\nchristophersu/PySteamMarket\n\nPython API for getting prices from the Steam market.\n\n\t1\t5\t6\nExtremelyd1/Strat-Roulette\n\nCS:GO Sourcemod Plugin\n\n\t2\t4\t6\ngiovanni-orciuolo/double-sdk\n\nA simple way to write CS:GO cheats!\n\n\t2\t4\t6\nJustArchiNET/Madness\n\nMadness embraces your project by including compatibility layer for selected APIs normally not available on .NET Framework target.\n\n\t5\t1\t6\nModDota/TypescriptPanoramaDeclarations\n\nNo description in the capture.\n\n\t4\t2\t6\nodota/rapier\n\nA JavaScript Dota 2 (Source 2) replay parsing library\n\n\t1\t5\t6\nVozn1akHero/CSGOCaseOpeningSimulator\n\nCounter-Strike case opening simulator which resembles the good old CS:GO user interface\n\n\t3\t3\t6\nautarc/steam-store\n\nAPI client for the unofficial steam storefront/big picture resource\n\n\t2\t3\t5\nBETTING-CODE/awesome-esports-sites\n\nA curated list of awesome esport betting sites – live, statistics and other resources.\n\n\t1\t4\t5\njonteohr/Better-Warden\n\nAn improved and more advanced warden plugin with a custom menu for CS:GO jailbreak servers!\n\n\t2\t3\t5\nLudzikk/CSGO-Gambling-Site\n\nhttps://ludzikk.github.io/CSGO-Gambling-Site/\n\n\t1\t4\t5\nModDota/find-steam-app\n\nFind location of an installed Steam app\n\n\t3\t2\t5\nmprey/csgocact.us\n\nsource code for csgocact.us\n\n\t1\t4\t5\nnezu-cc/ServerCrasher\n\nCS:GO Server Crasher\n\n\t1\t4\t5\nodota/testfiles\n\nStores test replay files\n\n\t2\t3\t5\nodota/underlordsconstants\n\nConstant data for Dota Underlords\n\n\t3\t2\t5\nSnaBe/node-steam-market-fetcher\n\nA Node.js wrapper for the Steam Community Market API.\n\n\t2\t3\t5\nSteamDatabase/.github\n\n💗 Organization-wide community health files\n\n\t1\t4\t5\nwolfcon/RIP-HLTV-BET\n\nRIP BET AD (For Tampermonkey) https://greasyfork.org/en/scripts/423484-rip-hltv-bet\n\n\t2\t3\t5\nalliedmodders/blaster.net\n\nSource and GoldSrc Query Tool\n\n\t2\t2\t4\ncatears124/CS2-Price-API\n\nsimple python cs2 steam market price API\n\n\t1\t3\t4\nialakey/caseforge\n\nOpen-source CS2 case-opening platform: Steam auth, provably fair openings, RTP-balanced case builder, withdrawals bought on market.csgo.com and an admin CRM.\n\n\t1\t3\t4\nIlusion9/csgo-fix-mapchange-crash-sm\n\nFix players crash on map change.\n\n\t1\t3\t4\nismail0234/Benson-Map-Crash-Fixer\n\nCSGO Map Change Client Crash Fixer\n\n\t1\t3\t4\njaxwilko/steam-market-api\n\nPHP - Composer Compatible - Steam Market API\n\n\t2\t2\t4\nJustArchiNET/ArchiTag\n\nArchiTag is a very small utility based on Python 3 and Mutagen to provide missing functionality in opusenc of writing specific Opus metadata, such as total number of tracks or track number.\n\n\t1\t3\t4\nModDota/DotaUI\n\nNo description in the capture.\n\n\t2\t2\t4\nnode-steam/market-pricing\n\nWrapper for the unofficial Steam Market Pricing API\n\n\t1\t3\t4\nodota/media\n\nStores media files for Dota projects\n\n\t2\t2\t4\nSergeyIvanovDevelop/Crypto-Steam-Platform\n\nThe repository contains the code and configuration to run a platform for creating cryptocurrency stakes for arbitrary ERC20 tokens.\n\n\t1\t3\t4\nAareksio/csgodouble-floatchecker\n\nAdds context menu option to check item's float value\n\n\t1\t2\t3\nchinm4/CSGOdrop\n\nA online csgo gambling casino that includes a variety of mini games that allows you to win csgo skins\n\n\t2\t1\t3\nCruze03/CSGO-Case-Opening-Prank\n\nCommand:- !prank (Admin flag \"n\" required)\n\n\t1\t2\t3\nDhruva-Kapadia/CSGOTrollGG\n\nCSGO Case Opening Simulator\n\n\t2\t1\t3\nErhanCSGO/CSGOPolygon-prediction\n\nCSGOPolygon.com - prediction script, double your coins by using this tool\n\n\t1\t2\t3\nEv-Hoang/Bedrock-Chest-Case-Opening\n\nHypixel Skyblock Dungeon Mod - Bedrock Chest Opening Animation (CSGO Style)\n\n\t1\t2\t3\njmjp/csgo-roulette\n\nA csgo gambling roulette make with VueJS 3\n\n\t2\t1\t3\nJustArchiNET/ArchiCrowdin\n\nNo description in the capture.\n\n\t1\t2\t3\nLeonSK/WearMarketInspector\n\nRetrieve Wear Value (Float Value) and Pattern Index from Steam Community Market using http://csgo.exchange API\n\n\t1\t2\t3\nmaximgeerinck/csgo-gamble\n\nCSGO gambling website\n\n\t1\t2\t3\nModDota/BugTracker\n\nListing bugs for Dota 2 Custom Games\n\n\t2\t1\t3\nplwp/mma-betting\n\nUFC/MMA betting model with Pinnacle steam detection for AU book latency arb\n\n\t2\t1\t3\nSouthsideswag16/Csgo-Gambling-Site\n\nNo description in the capture.\n\n\t2\t1\t3\ntacyarg/csgofiesta-frontend-react\n\nRemastered version a the long time favorite csgo site\n\n\t2\t1\t3\nVelorasse/Mutah-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-csmoney-csgoskins\n\ngambling script for Mutah, Keydrop, csmoney, and csgoskins, featuring hacks, cheats, and predictors. Offers strategies to boost winning odds and optimize performance on these platforms.\n\n\t3\t0\t3\nalliedmodders/am-github-artifact-webhook\n\nNo description in the capture.\n\n\t2\t0\t2\ncharamza/roulette\n\nCSGO like roulette in JS\n\n\t1\t1\t2\nCruze03/CSGO-PugSetup-RoundRestore\n\nSometimes (player dropped/crashed) which would be disadvantage for a team. It would be very handy to restore the match to the previous round.\n\n\t1\t1\t2\ncsgorol/CSGO-ROLL-Crash-Predictor\n\nCSGO-ROLL-Crash-Predictor\n\n\t1\t1\t2\nFoxSerito/FOXWORLD_plugin_DoubleJump_CSGO\n\nПлагин SourceMod (CSGO). Двойной прыжок с эффектом.\n\n\t1\t1\t2\nhkehayovmoonbiz/CS2-Casino-Full-Source-Code\n\nCS2, CS2 betting platforms, Skin Roulette, Case Unboxing, Crash games, Jackpot, purchase CS2 casino source, crypto gambling\n\n\t1\t1\t2\nJustZakary/steamstoreapi\n\nThis NPM module is a API wrapper that makes the steam unofficial API easier to use.\n\n\t2\t0\t2\njzimr/steam-market-api\n\nA java library to easily get Steam Community Market data\n\n\t1\t1\t2\nMomohime/CSGO.Network-Jackpot-Coinflip\n\nNo description in the capture.\n\n\t1\t1\t2\nnnjjswat/moneybot\n\nautomated bots for bustabit (formerly known as moneypot), csgo crash, etc\n\n\t0\t2\t2\nodota/carry\n\nLegacy Application for donations to the OpenDota project\n\n\t1\t1\t2\nodota/PublicMatchDataBot\n\nA Discord bot to remind users to turn on Expose Public Match Data in the Dota 2 client\n\n\t1\t1\t2\nOrillio/CSGOBet.com\n\nCSGO roulette web app\n\n\t2\t0\t2\nripexz/csgo-bet-alert\n\nA Chrome extension to keep track of active CS:GO Lounge matches.\n\n\t1\t1\t2\nrrpvm/lumen_sense-beta-deprecated-\n\nthis is internal csgo cheat written by me(no paste, self reverse structures). start : ~6 August 2020, end : ~ 14 December 2020\n\n\t1\t1\t2\nRuthless222/csgoscore\n\nThis is a Counter Strike Global Offensive Betting Site. You chose the skins you want to bet and try to win jackpots\n\n\t2\t0\t2\ntfburns/CSGO-cases-PL\n\nExpected profit-loss of CS:GO case openings\n\n\t1\t1\t2\nTomDra/CSGO-Case-Data-Analysis\n\nWorks out the most profitable CS:GO case at that current time\n\n\t1\t1\t2\nValvePython/dota2-wrappers\n\nNo description in the capture.\n\n\t1\t1\t2\nValvePython/teamfortress2-closed-captions\n\nThis project aims to provide a set of closed captions for Team Fortress 2\n\n\t1\t1\t2\nVistaNetGTX/Cstrike.bet-\n\nCSGO Roulette Website Angular frontend, nodejs backend, and steam trading bots\n\n\t1\t1\t2\nwafflas/csgo-case-opening-simulator\n\nI created a cs go case opening simulator for a meme coin\n\n\t0\t2\t2\nAdmiral-Enigma/Le_Coinflip\n\nConflip game\n\n\t1\t0\t1\nadryeljuliao/roulette-csgo\n\nNo description in the capture.\n\n\t1\t0\t1\nAndreuTheG/csgo-coinflip-web\n\nCSGO Gambling Coinflip Website\n\n\t1\t0\t1\nasmilen/csgoDouble\n\na b c\n\n\t1\t0\t1\nb1naryth1ef/csgofort\n\nA CSGO portal for trading, betting, analytics, and more!\n\n\t1\t0\t1\nBaterka/PrivateSteamBettingWebsite2024\n\nPrivate Steam (Counter-Strike 2) betting/gambling website - Roulette, Jackpot\n\n\t1\t0\t1\nblackcaer/SteamTradeHandler\n\nAutomation of Steam trading. Helper project for bet automation.\n\n\t1\t0\t1\nBTheCoderr/theRounders\n\nThe Rounders - A professional-grade sports betting analytics platform combining real-time odds tracking, sharp movement detection, and advanced statistical analysis. Features include line shopping, steam move alerts, power rankings, and comprehensive bet t…\n\n\t1\t0\t1\nCallumHemsley/KazeBot\n\nA Twitch chat betting bot for CSGO, simply bet a certain amount of points, and double if you win, lose all if you lose. Simple.\n\n\t1\t0\t1\nchrisjpm/CSGOJackpotTemplate\n\nFront end for a jackpot site\n\n\t1\t0\t1\ncolinsenner/valve-bug-bounty\n\nFor many years CS:GO, Dota 2, and Team Fortress 2 servers had a bug that allowed malicious users to leak crucial server process memory or reliably crash any server.\n\n\t1\t0\t1\ncoryypeters/nrl-odds-intelligence-pipeline\n\nReal-time sports betting odds intelligence — streaming pipeline that detects line movement, steam, and arbitrage across bookmakers. Python · Redis Streams · FastAPI · React.\n\n\t1\t0\t1\ndeissh/dev-csgoduo\n\nCS:GO. Bot for receiving things on the site (Polygon, Duo, Double and etc).\n\n\t1\t0\t1\ndom1torii/even-better-font-manager\n\nSimply even better cross-platform tool for CS2 Font Management\n\n\t1\t0\t1\nDONnicov/CSGO-crash-black-screen-\n\nsolution csgo crash black screen and close csgo\n\n\t1\t0\t1\nDoubleBoters/CsgoDouble\n\nNo description in the capture.\n\n\t1\t0\t1\ndownarowiczd/DoubleBot\n\nAn old CSGO Double Bot written for my friend. - 07.05.2016\n\n\t1\t0\t1\nErayBahar/steammarketscraper\n\nSteam Market Scraper Python-based tool that tracks real-time CS2 skin prices using Steam's hidden API. It fetches the lowest sell and highest buy offers for any item, helping you monitor deals or snipe underpriced listings automatically.\n\n\t1\t0\t1\nfairydarkness/SteamwebmailAPI\n\nUnofficial Python API for steamwebmail.com Fast, lightweight, and browserless library for automating steamwebmail.com. Support for session management, proxy, folder navigation, and message retrieval\n\n\t1\t0\t1\nFAQU2/CSGO-Coinflip-MyJailShop\n\nSourcemod plugin which provides a Coinflip system for MyJailShop.\n\n\t1\t0\t1\nFlamesONE/csgo-case-opening\n\nNo description in the capture.\n\n\t1\t0\t1\nFunnyRain/csgorun-crash-watch\n\n🚀 CsgoRun dump crash. / 🚀 CsgoRun дамп крашей.\n\n\t1\t0\t1\ngeohdgio/Venatus-Autenticator\n\nეს არის Steam Autenticator ქართული Venatus Trade & Betting ისთვის და Valve News Georgia-სთვის.\n\n\t1\t0\t1\nhakanstarlord/steam-bot\n\nSports betting steam-move signal detection with ML pipeline (XGBoost stacking + isotonic calibration), backtesting engine, Flask dashboard, and Telegram alerts.\n\n\t1\t0\t1\nHvH-gg/CSGO-Item-CrashFix\n\nA plugin for Counter-Strike: Global Offensive that fixes an exploit where receiving CS2 Items will cause CS:GO clients to crash\n\n\t1\t0\t1\nHvH-gg/CSGO-NetMsg-CrashFix\n\nA plugin for Counter-Strike: Global Offensive that fixes an exploit where spamming NetMsg_StringCmd packets would result in a server crash.\n\n\t1\t0\t1\nisybycnsmam/SteamLibrary\n\nLegacy Steam Unofficial API\n\n\t1\t0\t1\nItsTangerine/SteamApis.Net\n\nUnofficial https://steamapis.com .NET library, supporting .NET 6.0+\n\n\t1\t0\t1\nJustArchiNET/JustArchi.net\n\nNo description in the capture.\n\n\t1\t0\t1\nkiri-osint/CS2-Info-Hub-Bot\n\nA Telegram bot that acts as a hub for CS2 players, providing real-time skin prices, server stats, and user profile/inventory inspection using official and unofficial Steam APIs.\n\n\t1\t0\t1\nKoshkaj/monte\n\nGamified csgo gambling platform implementation\n\n\t1\t0\t1\nmadsab/CaseOpening\n\nA school project using Java. Simulating the case opening from CSGO and more.\n\n\t1\t0\t1\nman90es/steamcardexchange-api\n\nSteamCardExchange.net unofficial REST API server (scraper).\n\n\t1\t0\t1\nMattPua/steam-unofficial-docs\n\nUnofficial docs for Steam APIs with fumadocs\n\n\t1\t0\t1\nMetallist1/Portfolio.CsgoWinGambleProject\n\nA website that was done in 2017 September. Websites focus was on gambling with Counter-Strike items. Project was largely completed however backups were not done correctly, this resulted in half a year of wasted improvements to the code. The website was test…\n\n\t1\t0\t1\nmikebobadilla/csgo-jackpot\n\nNo description in the capture.\n\n\t0\t1\t1\nmikebobadilla/meteor-csgojackpot\n\nCssgo Jackpot done in meteor\n\n\t1\t0\t1\nModDota/D2VDump\n\nDota 2 Server VScript API Dumper\n\n\t1\t0\t1\nModDota/DotaTracking\n\nNo description in the capture.\n\n\t1\t0\t1\nModDota/eslint-config\n\nESLint config by ark120202\n\n\t1\t0\t1\nmr-codinglv/Casino-script\n\nscript casino - script betting - exchange script - bc casino - casino csgo - script bet - betwin script\n\n\t1\t0\t1\nMrKeelik/MrKeel\n\nCSGO DOUBLE BOT\n\n\t1\t0\t1\nnoahlatzel/CSGORollHelper\n\nLeveraging positive expected value on triple green jackpots on CSGORoll!\n\n\t1\t0\t1\noddsgpt/oddsgpt-market-intelligence\n\nResearch on football betting markets, closing odds, CLV, market efficiency, steam moves, AI betting systems, and sports market intelligence.\n\n\t1\t0\t1\noEXU/csgo-server-crasher\n\nCSGO SERVER CRASHER\n\n\t1\t0\t1\nPrdTTony/CSGO-Roulette\n\n[CSGO] Roulette System. Bet on RED or Black and win x2 credits\n\n\t1\t0\t1\nr-adamski/csgo-jackpot\n\nNo description in the capture.\n\n\t1\t0\t1\nSahotallo/Turan-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-Skinbaron-hellcase\n\ngambling script for Turan, Keydrop, Skinbaron, and Hellcase, providing hacks, cheats, and predictors. Includes strategies to improve winning chances and enhance gameplay on these platforms.\n\n\t1\t0\t1\nsamuelcsouza/steam-marketplace-api\n\nAn unofficial API to get data from the Steam Marketplace.\n\n\t1\t0\t1\nSKINSTRACK/CS2-Price-API\n\nSkinstrack offers a free, limited API endpoint that returns Steam item prices. Paid plans additionally provide access to pricing data from multiple marketplaces, making it possible to compare prices across different markets through a single API.\n\n\t1\t0\t1\nsnmtriet/CSGO-Casino-Full-Source-Code\n\nCSGO, CSGOEmpire, Case Opening, Case Battles, Roulette, Coinflip, buy csgo gambling site, gambling\n\n\t1\t0\t1\nSteamRE/homebrew-tools\n\nRepository for installation of SteamRE tools via Homebrew (http://brew.sh)\n\n\t1\t0\t1\nSteamRE/opensteamworks.org\n\nNo description in the capture.\n\n\t1\t0\t1\nTheQuack45/CsgoCaseOpenProgram\n\nSimple program to parse an XML file with CS:GO case information and \"simulate\" case openings\n\n\t1\t0\t1\nTLClassless/StratRouletteCSGO\n\nA 'Strat Roulette' web app for CS:GO!\n\n\t1\t0\t1\ntomasoom/csgoCaseOpening\n\nNo description in the capture.\n\n\t1\t0\t1\nvitaliy-evsyukov/steamgifts-autobet-bookmarklet\n\nbookmarklet for automatic bets on steamgifts.com\n\n\t1\t0\t1\nXpravdaX/RouletteCSGO\n\nNo description in the capture.\n\n\t1\t0\t1\nYuiKasumii/steam_api_unofficial\n\nUnofficial Steam Game Information Database\n\n\t1\t0\t1\nZexuz/Steam-Betting\n\nA betting website build ontop of STEAM's ecosystem\n\n\t1\t0\t1\nANK-RULZZ/steam-jackpot-site\n\ngetting some errors and would like some one to help me with it thank you!!!\n\n\t0\t0\t0\nasmilen/CsgoDoubleVS\n\nNo description in the capture.\n\n\t0\t0\t0\nCORNOODOSADAS/CSGOWeed\n\nCsgo Jackpot and Coinflip\n\n\t0\t0\t0\nCSGOApple/csgoapple\n\nJackpot Site\n\n\t0\t0\t0\nCSGOFAST/csgofast-api\n\nNo description in the capture.\n\n\t0\t0\t0\nDonakall/csgoDoublebot\n\nAutomated bot for csgodouble\n\n\t0\t0\t0\nfedor-selivanov/csgo-fast-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nfoldageros/csgod\n\ndouble bot\n\n\t0\t0\t0\ngmod-gambling/gmod-gambling\n\nNo description in the capture.\n\n\t0\t0\t0\nierome/CSGOBoss-BackEnd\n\nBack end version of CSGOBoss. This was a CSGO Gambling site named CSGOBoss. Coded by an old friend of mine Dahquan Hinds (https://github.com/dahquan/) Thought I would release this to help out any one who would need it.\n\n\t0\t0\t0\njamienp1/CSGODOUBLE-BOT-AUTO\n\ni got a bot thats is betting on the last winning color except from green and if you lose it will double the coins you set it to bet, pretty good, so when there comes a loooong train you will be gaining a bit of money codepaste_net/ugmt92 remove all the _ an…\n\n\t0\t0\t0\nJEYONER/CSGOTOXIC\n\nPAGINA DE JACKPOT CSGO SKINS\n\n\t0\t0\t0\nkalrish/csgo-jackpot\n\nStressful but funny zombie-like Counter-Strike: Global Offensive game mode.\n\n\t0\t0\t0\nkrys12345/roulettee\n\n// ==UserScript== // @name CSGO Predict Bot // @namespace http://csgodouble.com // @version 1.0 // @description predicts what number its gonna be // @author Meee // @match http://www.csgodouble.com/ // @grant none // ==/…\n\n\t0\t0\t0\nLilDuggiMuffi/CSGODouble-Working-Bot\n\nFixed CSGO Double Bot\n\n\t0\t0\t0\nLyricLy/Steam2Proton\n\nCheck if all your Steam games will work with Proton! Uses the official Steam API and the unofficial Proton API.\n\n\t0\t0\t0\nM0NsTeR77/csgo-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nozanhalis/Hi\n\n// ==UserScript== // @name CS GO LOUNGE BOT-Ozan Halis // @namespace http://csgolounge.com/ // @version 0.6.6 // @description Cs Go Lounge Hızlı BOT // @match http://csgolounge.com/* // @match http://dota2lounge.com/* // @updateURL h…\n\n\t0\t0\t0\nscoobertus/CSGO-DoubleBot\n\nNo description in the capture.\n\n\t0\t0\t0\nTradeal/CSGO-Jackpot-Bot\n\nNo description in the capture.\n\n\t0\t0\t0\nValvePython/artifact\n\nNo description in the capture.\n\n\t0\t0\t0\nVampire/CSGO-Roulette-Bot\n\nNo description in the capture.\n\n\t0\t0\t0\nvdemans/csgo-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nVocoreVideo/CSGODungeon-\n\nCSGO Jackpot\n\n\t0\t0\t0\nwayz-dev/csgofloat\n\nNo description in the capture.\n\n\t0\t0\t0\n\n스냅샷: 17 September 2026, 11:19:11 (출처에 기재된 대로); 시간대 미지정. 내보내기 파일에서는 관계 컬렉션이 제한되어 있습니다(많은 카테고리가 40에서 끝납니다). 기여자와 포크한 사용자를 합치면 4,214 개의 서로 다른 프로필-저장소 쌍에 걸쳐 총 4,554 개의 역할 항목이 됩니다. 하나의 프로필은 두 역할을 모두 가질 수 있습니다. 0은 해당 카테고리에 기록된 데이터가 없음을 의미합니다. 저장소 이름에는 별칭이나 대소문자 변형이 포함될 수 있으며, 총계는 원본의 집계 규칙을 따릅니다.\n\n출처 정보\n사용자가 수집한 파일을 바탕으로 생성되었습니다.\n지지 증언\n2323/reddit_scams_ultra/steam_support_tickets_MEGA.json · 행 45, 58, 107, 110, 294\n네트워크 스냅샷\nnetwork-repositories.csv · raw_data.json · overlaps.csv · summary.txt (매니페스트에 이전 소스 경로 유지)\n\n매니페스트에는 소스 경로, 바이트 크기, SHA-256 해시 값 및 선택된 레코드 위치가 기록됩니다. 원본 캡처 데이터는 수사 당국의 해석 결과와 별도로 보관됩니다.\n\n소스 매니페스트 다운로드 ↓",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam 집행 증거 — 지원 기록 및 개발자 네트워크"
          },
          {
            "level": 2,
            "id": null,
            "text": "고소장을 읽어보세요.원본 파일을 첨부해 두세요."
          },
          {
            "level": 3,
            "id": null,
            "text": "Permanent sanction & closed appeals"
          },
          {
            "level": 4,
            "id": null,
            "text": "Permanently banned Steam account without a clear explanation, need help!"
          },
          {
            "level": 3,
            "id": null,
            "text": "Account recovery & a reported $10,000 loss"
          },
          {
            "level": 4,
            "id": null,
            "text": "Got $10k stollen from steam inventory due to steam' support fault."
          },
          {
            "level": 3,
            "id": null,
            "text": "A reported $500+ loss & template replies"
          },
          {
            "level": 4,
            "id": null,
            "text": "Funds stolen through steam market. Disappointed with Steam response.(or lackthereof)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam Guard & an item-restoration refusal"
          },
          {
            "level": 4,
            "id": null,
            "text": "Many people are losing item via clicking links where steam guard is enabled and steam support doesn't not restore items."
          },
          {
            "level": 3,
            "id": null,
            "text": "Selective enforcement & an unexplained ban"
          },
          {
            "level": 4,
            "id": null,
            "text": "🚨 Steam Bans Without Reason and Ignores Its Community — What’s Going On?"
          },
          {
            "level": 2,
            "id": null,
            "text": "공공 인프라.대규모로 녹음되었습니다."
          },
          {
            "level": 2,
            "id": null,
            "text": "사용자가 수집한 파일을 바탕으로 생성되었습니다."
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/ko/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/ko/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/selected-support-records.json",
          "https://phishdestroy.io/steam_dossier/ko/investigation_part2.html#outsourcing-case",
          "https://www.reddit.com/r/ohnePixel/comments/1hahqx2/permanently_banned_steam_account_without_a_clear/",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://www.reddit.com/r/DotA2/comments/r55bd7/many_people_are_losing_item_via_clicking_links/",
          "https://www.reddit.com/r/SteamUncensored/comments/1kjt2fa/steam_bans_without_reason_and_ignores_its/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/network-repositories.csv",
          "https://github.com/alliedmodders/amxmodx",
          "https://github.com/alliedmodders/sourcemod",
          "https://github.com/DoctorMcKay/node-steam-user",
          "https://github.com/Facepunch/Facepunch.Steamworks",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://github.com/odota/core",
          "https://github.com/odota/dotaconstants",
          "https://github.com/odota/web",
          "https://github.com/splewis/get5",
          "https://github.com/SteamDatabase/FileDetectionRuleSets",
          "https://github.com/SteamRE/SteamKit",
          "https://github.com/ValveSoftware/dxvk",
          "https://github.com/ValveSoftware/GameNetworkingSockets",
          "https://github.com/ValveSoftware/gamescope",
          "https://github.com/ValveSoftware/Proton",
          "https://github.com/ValveSoftware/source-sdk-2013",
          "https://github.com/ValveSoftware/wine",
          "https://github.com/ValveSoftware/steam-devices",
          "https://github.com/ValveSoftware/steam-audio",
          "https://github.com/alliedmodders/metamod-source",
          "https://github.com/alliedmodders/sourcepawn",
          "https://github.com/ValveSoftware/Fossilize",
          "https://github.com/rlabrecque/Steamworks.NET",
          "https://github.com/ModDota/moddota.github.io",
          "https://github.com/odota/parser",
          "https://github.com/ValveSoftware/steam-for-linux",
          "https://github.com/SteamRE/DepotDownloader",
          "https://github.com/JustArchiNET/ASF-ui",
          "https://github.com/advancedfx/advancedfx",
          "https://github.com/alliedmodders/ambuild",
          "https://github.com/SteamDatabase/BrowserExtension",
          "https://github.com/odota/mobile",
          "https://github.com/ValvePython/steam",
          "https://github.com/skadistats/clarity",
          "https://github.com/SteamRE/open-steamworks",
          "https://github.com/ValveSoftware/Source-1-Games",
          "https://github.com/alliedmodders/hl2sdk",
          "https://github.com/SteamDatabase/steamdb.info-issues",
          "https://github.com/CSGOFloat/inspect",
          "https://github.com/ValveSoftware/SteamOS",
          "https://github.com/alliedmodders/source2mod",
          "https://github.com/smiley/steamapi",
          "https://github.com/SteamDatabase/GameTracking",
          "https://github.com/ValveSoftware/counter-strike_rules_and_regs",
          "https://github.com/ValveSoftware/openvr",
          "https://github.com/SteamDatabase/easy-markdown-editor",
          "https://github.com/ValveSoftware/Dota-2",
          "https://github.com/ValveSoftware/Dota2-Gameplay",
          "https://github.com/JustArchiNET/ArchiBot",
          "https://github.com/ztizzlegaming/CSGOWinBig",
          "https://github.com/JustArchiNET/mantis.justarchi.net",
          "https://github.com/odota/node-steam-user",
          "https://github.com/ModDota/TypeScriptAddonTemplate",
          "https://github.com/ValvePython/vdf",
          "https://github.com/alliedmodders/amtl",
          "https://github.com/ValvePython/dota2",
          "https://github.com/alliedmodders/stripper-source",
          "https://github.com/Allyans3/steam-market-api-v2",
          "https://github.com/ModDota/dota-tutorial",
          "https://github.com/odota/blog",
          "https://github.com/OpsecGuy/BetterGo",
          "https://github.com/pxvr-official/1",
          "https://github.com/Revadike/InternalSteamWebAPI",
          "https://github.com/JoeSzymkowiczFiveM/qb-lootcrate",
          "https://github.com/AbrarKL/MyRoulette.XYZ",
          "https://github.com/JustArchiNET/ASF-WebConfigGenerator",
          "https://github.com/ModDota/dota-data",
          "https://github.com/ModDota/TypeScriptDeclarations",
          "https://github.com/ModDota/API",
          "https://github.com/alliedmodders/cssdm",
          "https://github.com/SteamDatabase/steamstat.us",
          "https://github.com/c0deina/csgojackpotV2",
          "https://github.com/ValvePython/steamctl",
          "https://github.com/ValvePython/csgo",
          "https://github.com/BeepIsla/csgo-crash-exploit",
          "https://github.com/ValvePython/vpk",
          "https://github.com/alliedmodders/SM-SteamWorks",
          "https://github.com/SteamRE/Steam4NET",
          "https://github.com/alliedmodders/hl2sdk-manifests",
          "https://github.com/JustArchiNET/ASF-PluginTemplate",
          "https://github.com/ModDota/Dota2AIFramework",
          "https://github.com/Shkyyl/KeyChamp",
          "https://github.com/SteamDatabase/SteamMonitor",
          "https://github.com/Baterka/cslore.com",
          "https://github.com/SteamDatabase/SteamTokenDumper",
          "https://github.com/monoblocker/roulette",
          "https://github.com/zsith/launcher.user.js",
          "https://github.com/LincolnIT/CSGODouble-bot-automated",
          "https://github.com/vladpuz/steam-market",
          "https://github.com/mcgrizzz/Cstrike.bet",
          "https://github.com/odota/underlords-web",
          "https://github.com/SteamDatabase/SteamToTwitter",
          "https://github.com/ModDota/AbilityLuaSpellLibrary",
          "https://github.com/alvinl/bitskins",
          "https://github.com/b1naryth1ef/steamy",
          "https://github.com/kratos1812/Case-Opening",
          "https://github.com/odota/docs",
          "https://github.com/SteamDatabase/steam-advanced-access-fetch-players",
          "https://github.com/TheRioMiner/CsgoBetterExternalRaytrace",
          "https://github.com/alliedmodders/hl2sdk-mock",
          "https://github.com/christophersu/PySteamMarket",
          "https://github.com/Extremelyd1/Strat-Roulette",
          "https://github.com/giovanni-orciuolo/double-sdk",
          "https://github.com/JustArchiNET/Madness",
          "https://github.com/ModDota/TypescriptPanoramaDeclarations",
          "https://github.com/odota/rapier",
          "https://github.com/Vozn1akHero/CSGOCaseOpeningSimulator",
          "https://github.com/autarc/steam-store",
          "https://github.com/BETTING-CODE/awesome-esports-sites",
          "https://github.com/jonteohr/Better-Warden",
          "https://github.com/Ludzikk/CSGO-Gambling-Site",
          "https://github.com/ModDota/find-steam-app",
          "https://github.com/mprey/csgocact.us",
          "https://github.com/nezu-cc/ServerCrasher",
          "https://github.com/odota/testfiles",
          "https://github.com/odota/underlordsconstants",
          "https://github.com/SnaBe/node-steam-market-fetcher",
          "https://github.com/SteamDatabase/.github",
          "https://github.com/wolfcon/RIP-HLTV-BET",
          "https://github.com/alliedmodders/blaster.net",
          "https://github.com/catears124/CS2-Price-API",
          "https://github.com/ialakey/caseforge",
          "https://github.com/Ilusion9/csgo-fix-mapchange-crash-sm",
          "https://github.com/ismail0234/Benson-Map-Crash-Fixer",
          "https://github.com/jaxwilko/steam-market-api",
          "https://github.com/JustArchiNET/ArchiTag",
          "https://github.com/ModDota/DotaUI",
          "https://github.com/node-steam/market-pricing",
          "https://github.com/odota/media",
          "https://github.com/SergeyIvanovDevelop/Crypto-Steam-Platform",
          "https://github.com/Aareksio/csgodouble-floatchecker",
          "https://github.com/chinm4/CSGOdrop",
          "https://github.com/Cruze03/CSGO-Case-Opening-Prank",
          "https://github.com/Dhruva-Kapadia/CSGOTrollGG",
          "https://github.com/ErhanCSGO/CSGOPolygon-prediction",
          "https://github.com/Ev-Hoang/Bedrock-Chest-Case-Opening",
          "https://github.com/jmjp/csgo-roulette",
          "https://github.com/JustArchiNET/ArchiCrowdin",
          "https://github.com/LeonSK/WearMarketInspector",
          "https://github.com/maximgeerinck/csgo-gamble",
          "https://github.com/ModDota/BugTracker",
          "https://github.com/plwp/mma-betting",
          "https://github.com/Southsideswag16/Csgo-Gambling-Site",
          "https://github.com/tacyarg/csgofiesta-frontend-react",
          "https://github.com/Velorasse/Mutah-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-csmoney-csgoskins",
          "https://github.com/alliedmodders/am-github-artifact-webhook",
          "https://github.com/charamza/roulette",
          "https://github.com/Cruze03/CSGO-PugSetup-RoundRestore",
          "https://github.com/csgorol/CSGO-ROLL-Crash-Predictor",
          "https://github.com/FoxSerito/FOXWORLD_plugin_DoubleJump_CSGO",
          "https://github.com/hkehayovmoonbiz/CS2-Casino-Full-Source-Code",
          "https://github.com/JustZakary/steamstoreapi",
          "https://github.com/jzimr/steam-market-api",
          "https://github.com/Momohime/CSGO.Network-Jackpot-Coinflip",
          "https://github.com/nnjjswat/moneybot",
          "https://github.com/odota/carry",
          "https://github.com/odota/PublicMatchDataBot",
          "https://github.com/Orillio/CSGOBet.com",
          "https://github.com/ripexz/csgo-bet-alert",
          "https://github.com/rrpvm/lumen_sense-beta-deprecated-",
          "https://github.com/Ruthless222/csgoscore",
          "https://github.com/tfburns/CSGO-cases-PL",
          "https://github.com/TomDra/CSGO-Case-Data-Analysis",
          "https://github.com/ValvePython/dota2-wrappers",
          "https://github.com/ValvePython/teamfortress2-closed-captions",
          "https://github.com/VistaNetGTX/Cstrike.bet-",
          "https://github.com/wafflas/csgo-case-opening-simulator",
          "https://github.com/Admiral-Enigma/Le_Coinflip",
          "https://github.com/adryeljuliao/roulette-csgo",
          "https://github.com/AndreuTheG/csgo-coinflip-web",
          "https://github.com/asmilen/csgoDouble",
          "https://github.com/b1naryth1ef/csgofort",
          "https://github.com/Baterka/PrivateSteamBettingWebsite2024",
          "https://github.com/blackcaer/SteamTradeHandler",
          "https://github.com/BTheCoderr/theRounders",
          "https://github.com/CallumHemsley/KazeBot",
          "https://github.com/chrisjpm/CSGOJackpotTemplate",
          "https://github.com/colinsenner/valve-bug-bounty",
          "https://github.com/coryypeters/nrl-odds-intelligence-pipeline",
          "https://github.com/deissh/dev-csgoduo",
          "https://github.com/dom1torii/even-better-font-manager",
          "https://github.com/DONnicov/CSGO-crash-black-screen-",
          "https://github.com/DoubleBoters/CsgoDouble",
          "https://github.com/downarowiczd/DoubleBot",
          "https://github.com/ErayBahar/steammarketscraper",
          "https://github.com/fairydarkness/SteamwebmailAPI",
          "https://github.com/FAQU2/CSGO-Coinflip-MyJailShop",
          "https://github.com/FlamesONE/csgo-case-opening",
          "https://github.com/FunnyRain/csgorun-crash-watch",
          "https://github.com/geohdgio/Venatus-Autenticator",
          "https://github.com/hakanstarlord/steam-bot",
          "https://github.com/HvH-gg/CSGO-Item-CrashFix",
          "https://github.com/HvH-gg/CSGO-NetMsg-CrashFix",
          "https://github.com/isybycnsmam/SteamLibrary",
          "https://github.com/ItsTangerine/SteamApis.Net",
          "https://github.com/JustArchiNET/JustArchi.net",
          "https://github.com/kiri-osint/CS2-Info-Hub-Bot",
          "https://github.com/Koshkaj/monte",
          "https://github.com/madsab/CaseOpening",
          "https://github.com/man90es/steamcardexchange-api",
          "https://github.com/MattPua/steam-unofficial-docs",
          "https://github.com/Metallist1/Portfolio.CsgoWinGambleProject",
          "https://github.com/mikebobadilla/csgo-jackpot",
          "https://github.com/mikebobadilla/meteor-csgojackpot",
          "https://github.com/ModDota/D2VDump",
          "https://github.com/ModDota/DotaTracking",
          "https://github.com/ModDota/eslint-config",
          "https://github.com/mr-codinglv/Casino-script",
          "https://github.com/MrKeelik/MrKeel",
          "https://github.com/noahlatzel/CSGORollHelper",
          "https://github.com/oddsgpt/oddsgpt-market-intelligence",
          "https://github.com/oEXU/csgo-server-crasher",
          "https://github.com/PrdTTony/CSGO-Roulette",
          "https://github.com/r-adamski/csgo-jackpot",
          "https://github.com/Sahotallo/Turan-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-Skinbaron-hellcase",
          "https://github.com/samuelcsouza/steam-marketplace-api",
          "https://github.com/SKINSTRACK/CS2-Price-API",
          "https://github.com/snmtriet/CSGO-Casino-Full-Source-Code",
          "https://github.com/SteamRE/homebrew-tools",
          "https://github.com/SteamRE/opensteamworks.org",
          "https://github.com/TheQuack45/CsgoCaseOpenProgram",
          "https://github.com/TLClassless/StratRouletteCSGO",
          "https://github.com/tomasoom/csgoCaseOpening",
          "https://github.com/vitaliy-evsyukov/steamgifts-autobet-bookmarklet",
          "https://github.com/XpravdaX/RouletteCSGO",
          "https://github.com/YuiKasumii/steam_api_unofficial",
          "https://github.com/Zexuz/Steam-Betting",
          "https://github.com/ANK-RULZZ/steam-jackpot-site",
          "https://github.com/asmilen/CsgoDoubleVS",
          "https://github.com/CORNOODOSADAS/CSGOWeed",
          "https://github.com/CSGOApple/csgoapple",
          "https://github.com/CSGOFAST/csgofast-api",
          "https://github.com/Donakall/csgoDoublebot",
          "https://github.com/fedor-selivanov/csgo-fast-roulette",
          "https://github.com/foldageros/csgod",
          "https://github.com/gmod-gambling/gmod-gambling",
          "https://github.com/ierome/CSGOBoss-BackEnd",
          "https://github.com/jamienp1/CSGODOUBLE-BOT-AUTO",
          "https://github.com/JEYONER/CSGOTOXIC",
          "https://github.com/kalrish/csgo-jackpot",
          "https://github.com/krys12345/roulettee",
          "https://github.com/LilDuggiMuffi/CSGODouble-Working-Bot",
          "https://github.com/LyricLy/Steam2Proton",
          "https://github.com/M0NsTeR77/csgo-roulette",
          "https://github.com/ozanhalis/Hi",
          "https://github.com/scoobertus/CSGO-DoubleBot",
          "https://github.com/Tradeal/CSGO-Jackpot-Bot",
          "https://github.com/ValvePython/artifact",
          "https://github.com/Vampire/CSGO-Roulette-Bot",
          "https://github.com/vdemans/csgo-roulette",
          "https://github.com/VocoreVideo/CSGODungeon-",
          "https://github.com/wayz-dev/csgofloat",
          "https://phishdestroy.io/steam_dossier/output_steam_network/raw_data.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/enforcement-source-manifest.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ko/steam_enforcement_evidence.content.json",
      "export_json_sha256": "0d38a7aa7b9912cbead67aab6418beb62f7dd96bd499e4ffdc6a6616605c9b45"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ko/steam_evidence_archive.html",
      "language": "ko",
      "title": "출처를 확인해 보세요 — ‘Steam’ 관련 자료",
      "source_url": "https://phishdestroy.io/steam_dossier/ko/steam_evidence_archive",
      "source_html_sha256": "69f5d7e997bc4ef99902a77cfad2d7db7dce2de0f241ce1cff5cb9277ae024d5",
      "exported_at": "2026-09-29T00:22:04.242Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "steam_evidence_archive.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ko/steam_evidence_archive.pdf?v=print-20260929-v5",
        "sha256": "06aa3df7be455807db9a2ebc0f008b20225e1bbd33ccfeee021c4b1caf3b7293",
        "bytes": 60594,
        "pages": 3
      },
      "integrity": {
        "signed_object": "steam_evidence_archive.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "steam_evidence_archive.content.json.asc",
        "digest_file": "steam_evidence_archive.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify steam_evidence_archive.content.json.asc steam_evidence_archive.content.json",
          "sha256sum -c steam_evidence_archive.content.json.sha256"
        ]
      },
      "content": {
        "text": "수사 자료 / 증거 수집 002\nSteam 증거 자료실 — 16,319 출처가 명시된 기록\n\n모든 청구. 원점으로 돌아가자.\n\n이 섹션이 입증하는 바\n\n이 포렌식 아카이브는 Valve 개발자 커뮤니티 문서, GitHub의 공개 이슈, 검증된 Trustpilot 불만 사항, 보관된 포럼 보고서를 아우르는 16,319의 1차 자료 기록들을 암호화 해시 및 출처 기록과 함께 색인화합니다. 이 아카이브는 재현 가능한 플랫폼 취약점, 문서화되지 않은 API 기능 중단, 계정 도용과 관련된 지속적인 소비자 불만 사항을 입증하는 검증 가능한 증거 기반을 제공합니다.\n\n← 경영진 브리핑으로 돌아가기\n\n주장의 근거가 되는 기록을 찾아보세요. 출처별로 필터링하고, 전문을 열어본 다음, 원본 링크를 따라가 보세요. 출처 항목이 중복될 수 있으며, 기록이 반드시 확인된 사건을 의미하는 것은 아닙니다.\n\n수사로 돌아가기 ↗\n354TRUSTPILOT / 출처 행\n208레딧 / 출처 행\n705GITHUB / 소스 코드 행\n15,302MASTER CSV / 소스 행\n16,319 기록 — 플랫폼 유형별 내역\n\n위키 카테고리 출처 (7,620 records · 46.7%): 2018년 8월 2024부터 2018년 9월 2026.까지, 자동화된 WARC 스냅샷 및 MediaWiki API 엔드포인트를 통해 Valve 개발자 커뮤니티 (developer.valvesoftware.com), SteamDB 문서/FAQ, 그리고 게임 커뮤니티 위키(Liquipedia CS/Dota 및 Fandom Steam 위키)에서 데이터를 추출했습니다. 모든 7,620 항목은 마스터 CSV 내보내기 파일에 완전히 통합되어 있습니다 (TOTAL_VALVE_SCANDALS_MASTER_DB.csv).\n\n위키\n7,620\n레딧\n5,635\nGitHub\n2,395\n트러스트파일럿\n393\n웹\n276\n9,116 16,319의 레코드(55.8%) 중 일부에는 Steam / Valve에 대한 참조가 포함되어 있습니다.\n\n이 검색 가능한 아카이브는 다음을 기반으로 구축되었습니다. 2026-09-17 위에 나열된 소스 내보내기 파일에서 가져온 것입니다. 이 문서의 다른 부분에서 사용되는 별도의 ‘40,448-’ 행 마스터 내보내기 파일은 적용 범위가 다릅니다. 다음을 참조하십시오. 매니페스트 생성 이 아카이브의 집계 수치는 기록 간 중복이 있을 수 있으며, 각 기록이 고유한 사건을 나타내는 것은 아닙니다.\n\n소스 플랫폼\n자료 수집\nSteam / Valve 관련 언급\n텍스트 일치 또는 Valve 저장소누락되거나 삭제된 텍스트\n16,569 소스 행\n16,319 서로 다른 레코드\n249 중복 행이 병합되었습니다\n1 행 제외\n원본 파일 보기 ↘\n★TRUSTPILOT2015-10-16#1RATING 1/5\n\nSteam is the biggest PC gaming platform without a doubt. A power which could be abused but Steam for the most part doesn't. Overall a definite download for any moden digital age PC gamer. It mu... See more\n\nMA · 7 source copies\n★TRUSTPILOT2021-06-18#2RATING 1/5\n\nThey scam people for money, dont believe me? Read this Source: Steam Subscribers/User Agreement NO GUARANTEES TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, NEITHER VALVE NOR ITS AFFILIA... See more\n\nWF · 7 source copies\n★TRUSTPILOT2016-10-28#3RATING 1/5\n\nSupport on site is terrible. Refunds not happend yet, despite games not working. No help at all if key is bought outside their system, so as a customer you can bounce back and through betw... See more\n\nPE · 7 source copies\n★TRUSTPILOT2021-09-27#4RATING 1/5\n\nThey are an amazing company!! My boyfriend paid for and downloaded a game without realizing it wasn’t the version he wanted. When he reached out, they gave him a full refund and responded in the same... See more\n\nVH · 7 source copies\n★TRUSTPILOT2026-07-20#5RATING 1/5\n\nI’ve used Steam for years, but lately, their sales have really lost their edge. I was hoping to score some solid discounts, but many games still feel overpriced, even during sales. Plus, the support response times can be frustratingly slow when issues arise.\n\nCR\n★TRUSTPILOT2025-12-10#6RATING 1/5\n\nI new here , but all my firends had great experience with this platform . They can make money\n\nZeinab Nematollahi\n★TRUSTPILOT2025-11-18#7RATING 1/5TEXT UNAVAILABLE\n\nNo text was included in the source record.\n\nEM\n★TRUSTPILOT2025-10-21#8RATING 1/5\n\nusing steam for over a decade and i have no words how good the platform is. some friends recommended it to me back in 2015 when we wanted to play csgo together and since then im loggin on it on a daily basis to check new games\n\nTrustpilot\n★TRUSTPILOT2025-05-09#9RATING 1/5\n\nSupport are never able to help you and only able to redicrect you to public linkBreaking there own TOSNot able to provider a refundNot able to provide a safe place for gamingBase on the game you play you can get scam.\n\nSym Link · 7 source copies\n★TRUSTPILOT2025-05-09#10RATING 1/5TEXT UNAVAILABLE\n\nNo text was included in the source record.\n\nHearnius\n★TRUSTPILOT2024-12-30#11RATING 1/5\n\nThis company allowed a single phishing scammer 76561199443342045 in 100's of its user community chat rooms \"Steam Chat\" the whole week of Winter Sales, 12-23-2024 - 2025 to spam spaceintrader a scam phishing website.Don't support Valve & Steam that support sca…\n\nFR · 7 source copies\n★TRUSTPILOT2024-11-15#12RATING 1/5\n\nVery realiable! Ive never had an issue over the 11 years ive had steam.\n\nJM\n빌드 및 소스 파일\n\n이 아카이브는 249의 중복 행을 병합하고, 16,569의 입력 데이터 중 한 행을 제외하여 16,319개의 고유 레코드를 남깁니다. 한 레코드는 다른 레코드에서 이미 다루어진 사건을 설명할 수도 있습니다. 검색은 제목, 저자, 출처 레이블 및 표시된 발췌문을 대상으로 하며, 각 레코드를 열면 저장된 전문 텍스트를 볼 수 있습니다.\n\n4개의 소스 내보내기 파일 다운로드 ↓파일 수 및 SHA-256 해시 ↗원본 빌드 매니페스트 ↗\n\n이 번들에는 빌드의 행 수와 기록된 세 개의 JSON 경로와 일치하는 복구된 내보내기 파일이 포함되어 있습니다. 원래 빌드에서는 입력 해시나 마스터 CSV 경로가 기록되지 않았으며, 함께 제공되는 매니페스트에는 복구된 파일 목록과 게시된 인덱스와의 비교 결과가 명시되어 있습니다.\n\nTrustpilot · steam_support_reviews.json354 행 · JSON 내보내기\nReddit · reddit_censored_forensics.json208 행 · JSON 내보내기\nGitHub · valve_ignored_bugs.json705 행 · JSON 내보내기; 파일명은 수집기 레이블입니다\n마스터 · TOTAL_VALVE_SCANDALS_MASTER_DB.csv15,302 행 · 비교용으로 사용된 CSV 내보내기 파일\n법원 사건 목록 · UNSEALED_EXHIBITS_AND_AML_DOSSIER.mdWolfire 대 Valve의 공개된 이메일, 게이브 뉴웰의 증언 녹취록, 10월 2019 AML 자백\n주요 사실 · FACTS_AND_CITATIONS_DATABASE.md1,638 35의 반독점 및 보안 분야 전반에 걸친 개별적으로 검증된 인용 사례\n지원 아카이브 · support_canned_refusals.html1,505 티켓 기록 · 137에 보관된 스크린샷 · 실시간 검색\n레코드 필드, 누락된 텍스트 및 중복된 내보내기\n\n날짜, 평점, 카테고리 및 게시 상태는 원본 내보내기 데이터를 그대로 반영합니다. 누락된 URL은 그대로 누락된 상태로 유지됩니다. “[제거됨]” 또는 “[삭제됨]” 표시만으로는 누가, 왜 게시물을 제거했는지 알 수 없습니다. Steam / Valve 필터는 관련성 평가가 아닌 텍스트 일치 방식입니다.\n\n“일치 항목 내보내기”는 인덱스 항목과 발췌문을 함께 다운로드하며, “기록 다운로드”에는 저장된 전체 텍스트가 포함됩니다. 별도의 40,448-행 마스터 CSV 그리고 1,690-GitHub행 CSV 이번 빌드의 경우 수출 건수가 아니라 수출 범위가 더 넓습니다.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam 증거 자료실 — 16,319 출처가 명시된 기록"
          },
          {
            "level": 2,
            "id": null,
            "text": "소스 플랫폼"
          },
          {
            "level": 2,
            "id": null,
            "text": "빌드 및 소스 파일"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/ko/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/ko/",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/TOTAL_VALVE_SCANDALS_MASTER_DB.csv",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive_manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive-inputs.zip",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive-inputs-manifest.json",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/unsealed_legal_and_aml/UNSEALED_EXHIBITS_AND_AML_DOSSIER.md",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/forensic_facts_1000/FACTS_AND_CITATIONS_DATABASE.md",
          "https://phishdestroy.io/steam_dossier/ko/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/github_valve_unpatched_bugs.csv"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ko/steam_evidence_archive.content.json",
      "export_json_sha256": "294f48653dd4da2f01fca527f52e0e7aaad62b96dbe971aa032628afcf739759"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ko/support_canned_refusals.html",
      "language": "ko",
      "title": "Steam 지원 거부 및 정형화된 답변 아카이브 — ‘Steam’ 관련 자료집",
      "source_url": "https://phishdestroy.io/steam_dossier/ko/support_canned_refusals",
      "source_html_sha256": "07e9b88bcfc720a7f9959de4719419baa8adc97700eb3f51b37a04216f9bb6b3",
      "exported_at": "2026-09-29T00:22:04.534Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "support_canned_refusals.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ko/support_canned_refusals.pdf?v=print-20260929-v5",
        "sha256": "86a5e5ffbf55a32b1e4280856551f2ed132b45aa09494db86891986269eab8dd",
        "bytes": 58412,
        "pages": 2
      },
      "integrity": {
        "signed_object": "support_canned_refusals.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "support_canned_refusals.content.json.asc",
        "digest_file": "support_canned_refusals.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify support_canned_refusals.content.json.asc support_canned_refusals.content.json",
          "sha256sum -c support_canned_refusals.content.json.sha256"
        ]
      },
      "content": {
        "text": "이 섹션이 입증하는 바\n\n이 저장소에는 137에 보존된 원본 스크린샷과 1,505에 감사된 피해자 항소 자료가 기록되어 있으며, 이를 통해 Valve의 자동화된 지원 티켓 처리 과정을 상세히 확인할 수 있습니다. 이는 OpenID 리디렉션이나 무단 API 키 생성을 통해 계정이 해킹당했을 때, Steam 지원팀이 기술적 조사 없이 체계적으로 표준화된 정형화된 거절 문구를 사용한다는 사실을 입증합니다. 아이템 복원이나 감사 추적 기록 공개를 일방적으로 거부함으로써, 이 플랫폼은 구조적인 인증 결함에 대한 전적인 책임을 해킹당한 계정 소유자에게 전가하고 있습니다.\n\n모든 스크린샷은 제3자가 캡처한 자료입니다. 저작권 및 콘텐츠에 대한 권리는 각 저작자 및 플랫폼(레딧 사용자, Steam 커뮤니티 작성자, 트러스트파일럿 리뷰어, X 및 유튜브 게시자)에게 있습니다. 이 자료들은 식별 및 공익 보도를 목적으로만 재게재되었으며, 어떠한 소유권도 주장하지 않습니다. 각 자료에는 원본 출처로 연결되는 링크가 포함되어 있습니다.\n\nFigures reported on the source page\nMeasure\tReported value\tScope\n문서화된 기록\t1505\t검증된 피해자 항소 및 티켓 관련 게시물\n보관된 스크린샷\t137\t로컬에 저장된 고해상도 티켓 캡처\n복구율\t0.0%\tAPI건 주요 거래 탈취 사건에서 재심 승인\n템플릿 복제\t100%\t직원 간(일리아, 로저, 매버릭) 대본 그대로 재사용\n법의학적 증거: 지원 거부의 세 가지 핵심 근거\nPILLAR 01 · 입학 안내증거물 R-014\n로저의 시인: API, MitM 공격 사실 확인\n\n티켓 응답 #1cp582i에서, Steam 지원 담당자 “Roger”는 공격자들이 API을 통해 정상적인 거래를 취소하고 밀리초 단위로 복제 봇의 거래로 대체한다는 사실을 서면으로 인정했으나, 아이템 복구를 거부하며 피해자에게 “지역 PC 수리 기술자”를 찾아보라고 조언했습니다.\n\n서면 입학 허가서 확인 ↗\n기둥 02 · 에스컬레이션증거물 R-012\n7-데이 트레이딩: 보유, 무작위 대응\n\n한 피해자가 ‘7-’의 당일 거래 보류 기간 중에 해커 계정의 SteamID64를 제공했습니다. 지원 담당자 “Artem”과 “Ilya”는 가상 아이템의 희소성을 이유로 도난당한 아이템을 동결해 주지 않았으며, 자동 응답 양식을 사용하여 티켓을 종결했습니다.\n\n다수 교직원 성적표 확인 ↗\n기둥 03 · 정책증거물 R-002\n재산권에 대한 시장의 희소성\n\nValve의 공식 아이템 복원 정책에는, 아이템을 복원할 경우 “희소성이 감소하고 경제가 과열되어 커뮤니티 마켓에서 아이템의 가치가 하락할 수 있다”는 이유로 아이템을 복원하지 않는다고 명시되어 있습니다.\n\n정책 스크린샷 확인 ↗\n역사적 기원 · 22 March 2018 to 2026\n증거물 H-003 · 8-패치되지 않은 공격 표면 현황\n기록상 가장 오래된 무역 대체 사례 (22 March 2018)\n\nValve가 ‘카운터 스트라이크’ 아이템에 대해 논란이 된 ‘7-’ 당일 거래 제한 조치를 시행하기 정확히 일주일 전, 거래 커뮤니티에서는 이 조치의 첫 실제 적용 사례를 발견했는데, Steam WebAPI 트래픽 리디렉션 취약점. 공격자들은 웹 세션을 탈취하여 API에서 무단으로 키를 생성했으며, steamcommunity.com/dev/apikey 2의 모바일 FA 확인 기능이 없어, 봇이 실시간으로 거래를 취소하거나 교환할 수 있게 됩니다.\n\n3월 ‘2018’ 공익광고 경고: \"사기꾼들은 이 거래 제안을 자동으로 감지하고, 귀하의 Steam API 키를 가지고 있기 때문에 귀하의 계정에서 이를 거절할 것입니다. 그러면 사기 봇이 동일한 스킨에 대한 거래 제안을 보내올 텐데... 귀하는 아무런 차이도 눈치채지 못할 것입니다!\"\n역사적 증거 탐방로\n22 3월 2018: 최초로 기록된 ‘API’ 스왑\n2019: 지원 정책이 “악성코드” 차단 방식을 표준화합니다\n2020: \"지원 요청 종료\" 스크립트의 보안 강화\n2022–2026: BitB 및 QR 피싱 자동화\n2018 레딧 원본 스레드 열기 ↗\nPrimary sources\n\n137 gallery cards refer to 78 distinct primary URLs. Images and repeated exhibit captions are omitted from this reading edition.\n\nFull visual archive and original captures",
        "headings": [
          {
            "level": 2,
            "id": null,
            "text": "Figures reported on the source page"
          },
          {
            "level": 2,
            "id": null,
            "text": "법의학적 증거: 지원 거부의 세 가지 핵심 근거"
          },
          {
            "level": 3,
            "id": null,
            "text": "로저의 시인: API, MitM 공격 사실 확인"
          },
          {
            "level": 3,
            "id": null,
            "text": "7-데이 트레이딩: 보유, 무작위 대응"
          },
          {
            "level": 3,
            "id": null,
            "text": "재산권에 대한 시장의 희소성"
          },
          {
            "level": 3,
            "id": null,
            "text": "기록상 가장 오래된 무역 대체 사례 (22 March 2018)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Primary sources"
          }
        ],
        "links": [
          "https://www.reddit.com/r/csgo/comments/1cp582i/i_got_api_scammed_what_do_i_do_now/",
          "https://www.reddit.com/r/DotA2/comments/1e5ovy4/my_account_was_hacked_and_steam_support_refuse/",
          "https://www.reddit.com/r/Steam/comments/3b2abd/steam_will_no_longer_restore_scammed_items_item/",
          "https://www.reddit.com/r/GlobalOffensiveTrade/comments/863tk1/psa_urgent_huge_scam_happening_read_here_how_to",
          "https://phishdestroy.io/steam_dossier/ko/support_canned_refusals#gallery-grid"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ko/support_canned_refusals.content.json",
      "export_json_sha256": "dca9bda88f00a9f4e61faea7c0bed3ca025d7b56381cbd07399a4a6b3c9c8482"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ko/valve_scandals_registry.html",
      "language": "ko",
      "title": "Valve 스캔들 등록부 — ‘Steam’ 관련 자료",
      "source_url": "https://phishdestroy.io/steam_dossier/ko/valve_scandals_registry",
      "source_html_sha256": "72cf25bfcb585d93a49c144f42e3fb67ca046c33badab60411740eda7db4910e",
      "exported_at": "2026-09-29T00:22:05.386Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "valve_scandals_registry.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ko/valve_scandals_registry.pdf?v=print-20260929-v5",
        "sha256": "47264700b195cf9329cb751c72acfe6624943c99c63db22fb96b725c490f4ee1",
        "bytes": 63451,
        "pages": 6
      },
      "integrity": {
        "signed_object": "valve_scandals_registry.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "valve_scandals_registry.content.json.asc",
        "digest_file": "valve_scandals_registry.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify valve_scandals_registry.content.json.asc valve_scandals_registry.content.json",
          "sha256sum -c valve_scandals_registry.content.json.sha256"
        ]
      },
      "content": {
        "text": "주요 스캔들 아카이브\nValve 스캔들 마스터 레지스트리 — 160에서 수집한 사건들\n원본 기록 (RAW): 11,768\n\n신고됨. 출처 확인됨. 아직 해결되지 않음.\n\n이 섹션이 입증하는 바\n\n이 마스터 레지스트리는 Valve의 생태계 전반에 걸쳐 지속적으로 발생하는 플랫폼 결함, 삭제된 커뮤니티 신고, 그리고 해결되지 않은 소비자 지원 실패 사례를 상세히 기록한, 160에서 독립적으로 검증된 1차 기록들을 종합한 것입니다. 검증된 Trustpilot 분쟁 접수 건, 보관된 GitHub 보안 문제 티켓, 그리고 규제 당국의 절차까지 아우르는 이 레지스트리는 계정 복구 및 고객 분쟁 해결 과정에서 반복적으로 발생하는 체계적인 문제점을 입증합니다.\n\n← 경영진 브리핑으로 돌아가기\n\n160 수집된 기록: 실제 이용자들이 평가한 지원 서비스, 더 이상 표시되지 않는 게시물, 신고만 되고 방치된 플랫폼 결함, 그리고 Valve이 이미 책임을 져야 했던 사건들. 여기에 담긴 내용은 모두 저희가 임의로 정리한 것이 아닙니다. 모든 항목에는 원본 출처가 명시되어 있습니다. 직접 하나를 열어 읽어보시기 바랍니다.\n\n출처 기록\n11,768\n모든 카테고리를 통틀어\n플랫폼의 결함\n3,372\n사용자가 제보한 플랫폼 결함\n검열된 게시물\n109\n관리자가 삭제한 레딧 게시물\n지원 관련 불만 사항\n471\nTrustpilot에서 확인된 불만 사항\n집행의 타당성\n인증 호스트 도메인 차단\n\nOpenID 인증 호스트에 대한 도메인 수준의 차단은 기술적으로 구현하기 간단합니다. 특정 리소스에 대한 Steam 로그인 리디렉션이 차단되면, 해당 리소스의 인증 프록시 역할을 하는 제3자 도메인도 동일한 규칙 세트를 통해 필터링될 수 있습니다. 구현 가능성에 대한 자세한 논의는 본 보고서에 수록되어 있습니다.\n\n서류에서 집행 가능성을 확인하세요 →\n카테고리: Trustpilot 지원 관련 불만 사항 (필터링된 부정적 에스컬레이션)176 일치하는 원본 레코드 · 중복 항목은 접힘\nConsumer Complaint2026-07-20\nAuthor: C***\n\nI’ve used Steam for years, but lately, their sales have really lost their edge. I was hoping to score some solid discounts, but many games still feel overpriced, even during sales. Plus, the support response times can be frustratingly slow when issues arise.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2026-07-20\nConsumer Complaint2025-05-09\nAuthor: S*** L***\n\nSupport are never able to help you and only able to redicrect you to public linkBreaking there own TOSNot able to provider a refundNot able to provide a safe place for gamingBase on the game you play you can get scam.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2025-05-09\nConsumer Complaint2024-12-30\nAuthor: F***\n\nThis company allowed a single phishing scammer 7656…2045 in 100's of its user community chat rooms \"Steam Chat\" the whole week of Winter Sales, 12-23-2024 - 2025 to spam spaceintrader a scam phishing website.Don't support Valve & Steam that support scams. Don't give your log in credentials to account hijacking scammers. This company also allows engagements of commercial advertising / spam for gambling in violation of its own Rules and Guidelines / Online Conduct. 7656…5023 proof - groups/deskinsfans key drop advertising, thanks TannerfromKD and Valve!*\"The Consumer Review Fairness Act (CRFA) protects people’s ability to share their honest opinions about a business’s products, services, or conduct, in any forum, including social media. The law protects a broad variety of honest consumer assessments, including online reviews, social media posts, uploaded photos, videos, etc. And it doesn’t just cover product reviews. It also applies to consumer evaluations of a company\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2024-12-30\nConsumer Complaint2024-07-31\nAuthor: A***\n\nhorrible company.randomly you get \"This account may have been accessed by someone else.\"this happened to me 3 times.the 3rd time they wanted a cd key.a spent useless cd key that nobody has any reason to keep laying around.i gave them the paypal bill for my first purchase back in 2015.i gave them a bill for my first phone number ever on the account.i still got the same email attached to the account.this company is literally a scam. nothing but a scam.they randomly claim you been accessed somewhere else and then require you to give them information no reasonable person would ever have, if not your done and have to rebuy everything.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2024-07-31\nConsumer Complaint2023-12-09\nAuthor: K***\n\nHad 288 euros in steam wallet, someone hacked my account even with two step verification, write a steam support for help but only answer was if something is spent in community market they can’t help.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2023-12-09\nConsumer Complaint2023-09-26\nAuthor: J***\n\nI was banned for saying \"Who let grandma on the PC\"and another for simply calling someone ignorant.Power tripping mods, devs who don't care, steam doesn't care. Yet allows racism/trolling/etc Fk steam, its a joke now.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2023-09-26\nConsumer Complaint2022-08-31\nAuthor: Anonymous\n\nSteam community is plain bad for a various reasons:1. Steam forums are a big mess, for example they allow users to post in any language and as result you get jumbled mess with posts in foreign languages together with English language posts. For example, If you check CS GO forums, you'll see half of posts are in Russian and half in English. I don't understand why such a big and international company would leave their forums so unorganized like that. All other normal companies have English only language allowed which is an international language and sometimes subforums for other languages like German, French and etc... so if French people want to post in French they go specifically in that sub-forum. But no, Steam doesn't care about this. Their forums is a one big mess.2. Moderation is biased and joke. I don't understand why such a big company like Steam can't afford to hire people for moderation and pay them. Instead they just recruit random people for moderation who do it for free and\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2022-08-31\nConsumer Complaint2022-05-28\nAuthor: J***\n\nThe login code never arrives. I hate Steam.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2022-05-28\nConsumer Complaint2021-11-08\nAuthor: N***\n\nThe service is terrible, I only signed up because I really like the game I wanted, but the rest is terrible, I hope to get something better soon.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-11-08\nConsumer Complaint2021-06-18\nAuthor: W***\n\nThey scam people for money, dont believe me? Read thisSource: Steam Subscribers/User Agreement NO GUARANTEESTO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, NEITHER VALVE NOR ITS AFFILIATES GUARANTEE CONTINUOUS, ERROR-FREE, VIRUS-FREE OR SECURE OPERATION AND ACCESS TO STEAM, THE CONTENT AND SERVICES, YOUR ACCOUNT AND/OR YOUR SUBSCRIPTION(S) OR ANY INFORMATION AVAILABLE IN CONNECTION THEREWITH.In short: You got a virus or your data leaked because of our software? Whoopsies we dont care, that isnt even legal or the last of their scammy stuff...\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-06-18\nConsumer Complaint2021-05-14\nAuthor: B***\n\nThe support is one of the worst I've ever seen.Useless support team.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-05-14\nConsumer Complaint2020-04-02\nAuthor: J***\n\nSteamcommunity has 15% fees, 15!!!!\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2020-04-02\nConsumer Complaint2020-03-27\nAuthor: H***\n\nWhat can I say? the support is one of the worst I've ever seen maybe the FUNCOM is much worse. If you tell the true on the steam forum you just got a BAN even if what you said did not violated the rules of the forum.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2020-03-27\nConsumer Complaint2018-03-16\nAuthor: B***\n\ndon't sign up will stick on your computer will kill your pc power you can't remove it from your pc even you deleted it will stay woking in the system\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2018-03-16\nConsumer Complaint2016-12-27\nAuthor: J***\n\nIn bloddy hate their page it's tiresome, it's in no way intuitive. I tried reaching out for support, but that is a maze.I'm simply trying to log in and redeem a key of a product I already bought, their search function is a joke. I f*u*c*k*i*n*g hate them. The layout is not like the how to video from the dealer, this can be done much simpler. I don't frigin care aboutn what other titles you have in store or what genre, I just want to redeem my key and install.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-12-27\nConsumer Complaint2016-10-28\nAuthor: P***\n\nSupport on site is terrible.Refunds not happend yet, despite games not working.No help at all if key is bought outside their system, so as a customer you can bounce back and through between bad support systems?? I wait for some other companies to compete in this market, for this can't be the best we as customers can expect.And do put an email up to find, instead of this stuppid website where you spend so long time trying to find a solution on, instead of a simple mail. Often the problem is not there, or if it's there just saying no help here???I need a response\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-10-28\nConsumer Complaint2016-06-26\nAuthor: V*** W***\n\nUseless support as always!\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-06-26\nConsumer Complaint2014-07-01\nAuthor: J***\n\nexpensive, and support team not willing to cooperate\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2014-07-01\nConsumer Complaint2014-04-15\nAuthor: B***\n\nWhen you pay for a program, you expect it too work. cant not buy or anything and have written to valve. but there is not a being done a damn thing abut it..\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2014-04-15\nConsumer Complaint2026-09-03\nAuthor: M***\n\nWorst platform ever wont give me a refund even though a game is unplayable because of bugs I won't ever be using the crap platform again I hope the platform breaks down for good piece fo crao\n\nTarget Domain: steamcommunity.com / steampowered.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2026-09-03\n\n일치하는 기록이 없습니다.\n\n현재 실행 중인 쿼리를 수정해 보거나 다른 카테고리 탭을 확인해 보세요.\n\n1 / 9",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Valve 스캔들 마스터 레지스트리 — 160에서 수집한 사건들"
          },
          {
            "level": 2,
            "id": null,
            "text": "인증 호스트 도메인 차단"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: C***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: S*** L***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: F***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: A***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: K***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: Anonymous"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: N***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: W***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: H***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: P***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: V*** W***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: M***"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/ko/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/ko/#autoban-feasibility-section",
          "https://www.trustpilot.com/review/steamcommunity.com"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ko/valve_scandals_registry.content.json",
      "export_json_sha256": "ec72a780c0b44adb5eddcf1e9dde90c607dffbebb2441f74cb71ab46e9399ae2"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ko/output_steam_network/index.html",
      "language": "ko",
      "title": "익스플로잇이 아닌 아키텍처: 자동화 네트워크 — ‘Steam’ 보고서",
      "source_url": "https://phishdestroy.io/steam_dossier/ko/output_steam_network/index",
      "source_html_sha256": "50b983809b1ec715adaef949653914c1dbe6e608e21d421720bed77218ef55d9",
      "exported_at": "2026-09-29T00:22:06.486Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__index.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ko/output_steam_network__index.pdf?v=print-20260929-v5",
        "sha256": "fce14be22ec2c63a19869df76e6b7a8ffde51e62994d6e38442fb6c58af767b5",
        "bytes": 58678,
        "pages": 2
      },
      "integrity": {
        "signed_object": "output_steam_network__index.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__index.content.json.asc",
        "digest_file": "output_steam_network__index.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__index.content.json.asc output_steam_network__index.content.json",
          "sha256sum -c output_steam_network__index.content.json.sha256"
        ]
      },
      "content": {
        "text": "부록 VII · 기술 아키텍처 분석\nSteam 네트워크 아키텍처 — 프로토콜 충실도 및 생태계 분석\n\n자동화는 ‘Valve’의 아키텍처입니다. 익스플로잇이 아닙니다.\n\n이 섹션이 입증하는 바\n\n이 모듈은 Steam 자동화 생태계의 기반이 되는 252 개발자 저장소, 3,320GitHub 프로필, 그리고 4,214 기여자 쌍의 기술적 토폴로지를 매핑합니다. 이는 타사 자동화 솔루션이 Valve의 공식 Connection Manager 프로토콜, Protobuf 스키마 및 웹 API에 의존하며, 악용 코드가 포함되지 않았음을 입증합니다. 알고리즘 기반 Steam 가드 확인 토큰을 설계하고 66.7%, Valve에서 정한 최소 거래 수수료를 징수함으로써, 이 플랫폼은 자동화된 생태계 운영의 의도된 설계자이자 주요 상업적 수혜자 역할을 수행합니다.\n\n← 경영진 브리핑으로 돌아가기\n\nValve가 규제 당국, 결제 처리 업체 또는 사기 피해자들에게 설명할 때, 스킨 도용 및 시장 조작을 “무단 제3자 악용”과 “불법 자동화 프로그램” 탓으로 돌립니다. 그러나 252-저장소 네트워크의 기술적 현실은 이와 정반대의 사실을 보여줍니다: 모든 자동화 프레임워크, 트레이딩 봇, 파밍 플릿은 Valve Corporation이 설계하고, 문서화하며, 수익화한 공식 프로토콜 정의, 웹 API 및 인증 메커니즘의 범위 내에서만 엄격하게 운영됩니다.\n\n법의학적 조사 결과: 의도적인 설계 대 불법적인 침해\n\n이 모듈에서 분석한 소프트웨어 — 다음을 포함하여 SteamKit, node-steam-user, ValvePython/steam, 그리고 ArchiSteamFarm — 포함 소프트웨어 취약점 제로, 메모리 손상 제로, 제로데이 공격 제로. 이들은 Valve의 독점적인 Connection Manager(CM) 클라이언트 프로토콜, Google Protocol Buffers(Protobufs) 및 웹 API를 기반으로 한 깔끔하고 견고한 오픈소스 구현체입니다. Valve는 프로그래밍 방식의 로그인을 지원하도록 이러한 API를 설계했으며, Steam Guard는 알고리즘 기반 확인 토큰을 허용하도록 설계되었습니다 (identity_secret), 그리고 광고된 15% 수수료는 점차 증가하여 Valve 측에 최대 66.7%의 금액이 지급될 예정 자동화된 봇넷이 처분하는 고속 거래 카드 및 상품 낙하물과 관련하여.\n\nPillar 01 · Protocol Fidelity\n공식 Protobuf 스키마\n\n자동화 라이브러리는 보안 게이트를 우회하지 않습니다. 이 라이브러리는 공식 Protobuf 메시지를 직렬화하며 (steammessages_clientserver.protoValve) TCP/WebSockets를 통해 Steam 의 공식 CM 클러스터로 직접 전송되며, 이는 클라이언트가 작동하는 방식과 정확히 동일합니다.\n\nPillar 02 · Algorithmic 2FA\n프로그램 기반 거래 승인\n\n수십억 달러 규모의 피부 거래 경제 전체는 ‘Valve’에 달려 있다. IEconService API 그리고 모바일 인증기 TOTP 키. Valve는 기기 간 거래 확인을 가능하게 하기 위해 Steam Guard를 의도적으로 설계했습니다.\n\n기둥 03 · 상업적 수혜자\n수익화된 기계 트래픽: 최대 66.7% 수수료 하한선\n\nValve 15% 수수료를 광고하고 있지만, 트레이딩 카드, 케이스, $0.03에서 $0.05 사이의 저렴한 드롭 등 거래량이 많은 상품의 경우 자동화된 봇이 거래를 진행하며, Valve의 2센트 최소 수수료 하한선($0.01 Steam + $0.01 퍼블리셔)이 부과됩니다. 50% 66.7%에 대해 Valve 측에 유리하게 (2¢가 3¢ 카드에서 차감되어 판매자에게는 1¢가 남게 됩니다). 또한 계정당 $5.00가 부과됩니다($26.8M은 스캔된 차량만으로도 발생합니다).\n\n모듈 01 · 저장소 및 프로토콜 증거\n공개 개발자 및 저장소 인프라\n\nSteam 자동화를 지원하는 252 오픈소스 저장소에 대한 상세한 포렌식 목록입니다. 표준 소프트웨어 엔지니어링 도구가 Valve에서 공개한 API 엔드포인트를 악용 없이 어떻게 구현하는지 추적합니다.\n\n252저장소\n4,554역할 링크\n저장소 증거 확인 →모듈 02 · 생태계 인구 통계\n글로벌 엔지니어링 생태계 지표\n\nSteam 자동화 생태계에 기여하는 ‘3,320’ 소프트웨어 엔지니어들의 지역별 및 기관별 분포로, 주요 기술 기업들의 소속 현황을 포함합니다.\n\n3,320엔지니어\n98,902연결 쌍\n생태계 지표 확인 →모듈 03 · 대화형 시각화 그래프\n대화형 프로토콜 및 개발자 네트워크 그래프\n\nVis.js의 상호 연결된 네트워크 그래프를 종합적으로 시각화하여 저장소, 프로토콜 라이브러리(SteamKit, Steamworks, ASF) 및 프로젝트 간 기여자 중복 현황을 보여줍니다. Steam의 자동화 생태계를 뒷받침하는, 정통하고 상호 연결된 오픈소스 소프트웨어 아키텍처를 시각적으로 보여줍니다.\n\n대화형Vis.js 엔진\n클러스터 격리라이브 검색\n제로 익스플로잇표준 API\n대화형 네트워크 그래프 열기 →\n규제 및 법적 배경 (GDPR 기사 25 및 소비자 보호):\n‘설계 및 기본 설정에 의한 데이터 보호(Data Protection by Design and by Default)’ 원칙에 따라, 사용자 모르게 ‘API’ 키 생성을 허용하고, 사전 통지 없이 거래를 취소하며, 기계에 의해 자동으로 자산을 청산하는 플랫폼 아키텍처는 플랫폼 운영자의 아키텍처적 선택입니다. Valve가 손실이 “외부 사이버 공격”에 기인했다고 주장하며 소비자의 보상 청구를 체계적으로 거부할 때, 이는 공격 경로가 Valve가 의도적으로 설계한 웹 API 아키텍처라는 사실을 은폐하는 것입니다.\n\n인터랙티브 보기\n\n252-저장소의 완전한 대화형 시각화 자료와 3,320-개발자 네트워크 그래프는 다음 주소에서 확인할 수 있습니다. network.html. 집계 지표는 BI 지표 페이지.\n\nSteam 자료집 · 기술 아키텍처 아카이브 · 공개 소스 기록 · 모든 권리는 인류에게 양도됨.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam 네트워크 아키텍처 — 프로토콜 충실도 및 생태계 분석"
          },
          {
            "level": 3,
            "id": null,
            "text": "공식 Protobuf 스키마"
          },
          {
            "level": 3,
            "id": null,
            "text": "프로그램 기반 거래 승인"
          },
          {
            "level": 3,
            "id": null,
            "text": "수익화된 기계 트래픽: 최대 66.7% 수수료 하한선"
          },
          {
            "level": 2,
            "id": null,
            "text": "공개 개발자 및 저장소 인프라"
          },
          {
            "level": 2,
            "id": null,
            "text": "글로벌 엔지니어링 생태계 지표"
          },
          {
            "level": 2,
            "id": null,
            "text": "대화형 프로토콜 및 개발자 네트워크 그래프"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/ko/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/ko/output_steam_network/valve_ru_farming_isolated.html",
          "https://phishdestroy.io/steam_dossier/ko/output_steam_network/steam_ecosystem_dashboard.html",
          "https://phishdestroy.io/steam_dossier/ko/output_steam_network/network.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ko/output_steam_network__index.content.json",
      "export_json_sha256": "2e761b55064f59a6763df5624096a70f01dff0b27c35e90c2ab18fa819ec5331"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ko/output_steam_network/network.html",
      "language": "ko",
      "title": "개발자 및 리포지토리 탐색기 — ‘Steam’ 도스시에",
      "source_url": "https://phishdestroy.io/steam_dossier/ko/output_steam_network/network",
      "source_html_sha256": "a0aa9aa8ec1395b446402e283b1e8f0ec668b8f8c6d0ee93284b78fab0be443d",
      "exported_at": "2026-09-29T00:22:07.139Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__network.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ko/output_steam_network__network.pdf?v=print-20260929-v5",
        "sha256": "98c18cc95d650298bb9b580a3f4f3e9dbd8d3b7dfcb6566f76751c71831dd842",
        "bytes": 31258,
        "pages": 1
      },
      "integrity": {
        "signed_object": "output_steam_network__network.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__network.content.json.asc",
        "digest_file": "output_steam_network__network.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__network.content.json.asc output_steam_network__network.content.json",
          "sha256sum -c output_steam_network__network.content.json.sha256"
        ]
      },
      "content": {
        "text": "개발자 및 저장소 탐색기\n\n노드를 검색합니다. 기록된 관계를 확인합니다.\n\n공개 기록 / 수집된 연결 정보\n라이브 검색\n레이어 필터\n개발자 총수3,320\n총 리포252\n표시된 그래프 / 컬렉션의 부분 집합468 노드 • 1103 에지\n선택된 프로필 기록\n\n💡 그래프의 아무 노드나 클릭하거나 ‘검색’에 내용을 입력하면, 해당 노드에 수집된 연결 정보와 소스 경로를 확인할 수 있습니다.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "개발자 및 저장소 탐색기"
          }
        ],
        "links": []
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ko/output_steam_network__network.content.json",
      "export_json_sha256": "9a176016b9b7464c84147526e7493b186e948b48ec37954f056fb153b3ac92d6"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ko/output_steam_network/steam_ecosystem_dashboard.html",
      "language": "ko",
      "title": "수치로 보는 통합 네트워크 — ‘Steam’ 자료집",
      "source_url": "https://phishdestroy.io/steam_dossier/ko/output_steam_network/steam_ecosystem_dashboard",
      "source_html_sha256": "a95d1d4a6b28bf1b6324d81bfe9d1cdd9db17e5176d050aafbedc10bba8f8129",
      "exported_at": "2026-09-29T00:22:06.965Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__steam_ecosystem_dashboard.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ko/output_steam_network__steam_ecosystem_dashboard.pdf?v=print-20260929-v5",
        "sha256": "516a040f075adfa24bc49778e37c34ea98990110948a21ffbf7cdeb6c0e7a459",
        "bytes": 35403,
        "pages": 1
      },
      "integrity": {
        "signed_object": "output_steam_network__steam_ecosystem_dashboard.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__steam_ecosystem_dashboard.content.json.asc",
        "digest_file": "output_steam_network__steam_ecosystem_dashboard.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__steam_ecosystem_dashboard.content.json.asc output_steam_network__steam_ecosystem_dashboard.content.json",
          "sha256sum -c output_steam_network__steam_ecosystem_dashboard.content.json.sha256"
        ]
      },
      "content": {
        "text": "통계 개요 // 파일02\nSteam 생태계 대시보드 — 수치로 보는 네트워크\n\n숫자로 보는 네트워크.\n\n이 섹션이 입증하는 바\n\n이 대시보드는 3,320의 개발자들과 252의 저장소에 걸쳐 구조적 정보를 종합하여, 68의 도박 관련 코드베이스와 크로스 플랫폼 연결 브리지를 식별합니다. 실증 데이터는 지리적 집적 현상과 개발자 중복 현상을 부각시키며, 제3자 스킨 도박 인프라가 Steam의 플랫폼과 통합된, 조직적이고 고도로 상호 연결된 소프트웨어 산업으로 운영되고 있음을 보여줍니다.\n\n← 경영진 브리핑으로 돌아가기\n\n조사 데이터베이스의 통합 통계: 지리적 분포, 주요 기업, 스킨 도박 저장소 및 활성 연결 브리지.\n\n스캔된 개발자들3320\n총 리포252\n도박 관련 리포68\n총 연결 수1,426\n자동화의 구조와 분야\n제1구역 — Valve 코퍼레이션 코어\n\n공식 저장소 및 시스템 소프트웨어. Valve의 직원인 Nephyrin과 Joe Ludwig가 개발한 것으로 확인된 공간.\n\n섹터 II — 인증 엔진 및 프로토콜 에뮬레이터 (SteamKit)\n\nValve의 Nephyrin과 스킨 도박 게임 개발자 DoctorMcKay가 공동으로 제작한 리버스 엔지니어링된 네트워크 라이브러리입니다.\n\n섹터 III — 카드 파밍 고객 (ArchiSteamFarm)\n\nSteamKit 프로토콜 에뮬레이터를 활용하여 백그라운드에서 수백만 개의 가짜 클라이언트(대기 상태)를 실행하고, 이를 통해 트레이딩 카드를 수집합니다.\n\n개발자 지역 분포\n독일57\n미국52\n캐나다48\n영국44\n폴란드30\n프랑스28\n러시아 연방27\n중국27\n미국 (워싱턴주)23\n호주19",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam 생태계 대시보드 — 수치로 보는 네트워크"
          },
          {
            "level": 3,
            "id": null,
            "text": "제1구역 — Valve 코퍼레이션 코어"
          },
          {
            "level": 3,
            "id": null,
            "text": "섹터 II — 인증 엔진 및 프로토콜 에뮬레이터 (SteamKit)"
          },
          {
            "level": 3,
            "id": null,
            "text": "섹터 III — 카드 파밍 고객 (ArchiSteamFarm)"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/ko/#briefing-heading"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ko/output_steam_network__steam_ecosystem_dashboard.content.json",
      "export_json_sha256": "7afa56698c2c189088038a7a5973ffb974aa78c61a84f4dbde8d900cd979b357"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ko/output_steam_network/valve_ru_farming_isolated.html",
      "language": "ko",
      "title": "코드, 기여자 및 포크 — ‘Steam’ 도스시에",
      "source_url": "https://phishdestroy.io/steam_dossier/ko/output_steam_network/valve_ru_farming_isolated",
      "source_html_sha256": "ee366c91feb88c6833e54fb6d63bca7f945f58769f4f17f8c92384dc9b2a066e",
      "exported_at": "2026-09-29T00:22:07.778Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__valve_ru_farming_isolated.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ko/output_steam_network__valve_ru_farming_isolated.pdf?v=print-20260929-v5",
        "sha256": "a75d539d68b99f7c14bc5fed89babc0674c361b6085182f2ec4b980dd5d83530",
        "bytes": 40270,
        "pages": 2
      },
      "integrity": {
        "signed_object": "output_steam_network__valve_ru_farming_isolated.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__valve_ru_farming_isolated.content.json.asc",
        "digest_file": "output_steam_network__valve_ru_farming_isolated.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__valve_ru_farming_isolated.content.json.asc output_steam_network__valve_ru_farming_isolated.content.json",
          "sha256sum -c output_steam_network__valve_ru_farming_isolated.content.json.sha256"
        ]
      },
      "content": {
        "text": "제2부 / 기록된 관계의 행적을 따라가다\n\n포크, 기여 내역 및 소프트웨어 종속성은 뚜렷한 증거입니다. 이 관점은 수집된 역할들을 그대로 반영하지만, 고용, 보안 우회 및 범죄 연루 여부에 대해서는 추가적인 출처가 필요합니다.\n\n대화형 역량 지도 열기 ↗\n공개 자료 / 역할 감사\n코드. 기여자들. 포크.\n1. Nephyrin: 포크 및 기여\n\n제공된 스냅샷에 따르면, Nephyrin은 ValveSoftware/Proton의 기여자이자 SteamRE/SteamKit 및 SteamRE/open-steamworks의 포크 작성자로 표시되어 있습니다. 프로필 정보에는 Valve Software가 기재되어 있습니다. 이러한 항목들은 각각 별도로 해석해야 합니다.\n\n포크는 리포지토리의 복사본을 기록합니다. 이 내보내기 작업에는 SteamKit 인증 코드의 변경 사항을 반영하는 커밋이 포함되지 않습니다.\n저장소 참조 / 변경 내역 확인\nSteamRE/SteamKit ↗ SteamRE/open-steamworks ↗\n2. 공개 기능: 데스크톱 클라이언트 없이도 가능한 자동화\n\nSteamKit과 node-steam-user는 Steam과의 프로그래밍 방식 상호작용을 제공합니다. ArchiSteamFarm은 다중 계정 카드 파밍에 대해 설명하며, SteamKit2를 의존성으로 선언합니다.\n\n이는 구체적인 자동화 기능입니다. 헤드리스 실행이 상업적 용도로만 사용되거나 ‘Steam Guard’를 우회하는 것은 아닙니다. 중요한 점은 요청된 인증 정보, 해당 인증 정보로 수행 가능한 작업, 그리고 플랫폼에서 적용하는 제어 조치입니다.\n\n출처: 프로젝트 README 및 ArchiSteamFarm.csproj. 기능 매핑표에는 문서화된 각 종속성이 연결되어 있습니다.\n3. JoeLudwig: hl2sdk 기여자 태그\n\n이 스냅샷에는 JoeLudwig이 alliedmodders/hl2sdk, ValveSoftware/openvr 및 ValveSoftware/source-sdk-2013.의 기여자로 나열되어 있습니다. 이는 확인 가능한 프로젝트 간의 연관성입니다. 이 내보내기 자료만으로는 특정 SDK 변경 사항이 절도나 도박 관련 배포와 연관되어 있다는 증거를 제시하지 못합니다.\n\n저장소 참조 / 변경 내역 확인\nalliedmodders/hl2sdk ↗ DoctorMcKay/node-steam-user ↗\n논리 회로도 // 트레이스\n연결 논리 흐름도:\n프로필 및 관계\n네피린 / 프로필 모음\n기여자: Proton. 포크: SteamKit 및 open-steamworks.\n▼ 수집된 포크 관계\n지역 도서관\nSteamRE/SteamKit\nSteamRE 조직에서 관리하는 공개 Steam 네트워크 라이브러리.\n▼ SteamKit2 의존성 선언\n문서화된 자동화\nJustArchiNET/ArchiSteamFarm\n여러 계정을 통한 카드 파밍 및 SteamKit2 의존성을 다룹니다.\n증거 검토 / 출처 개요\n기록됨: 별개의 기여자 및 포크 작성자 라벨.\n입증된 사실: 공공 도서관은 체계적인 ‘Steam’ 상호작용을 지원한다.\n개방형 질문: 특정 코드의 작성자, 플랫폼 승인 및 악용 책임 규명에는 각각 별도의 증거가 필요합니다.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "코드. 기여자들. 포크."
          },
          {
            "level": 2,
            "id": null,
            "text": "1. Nephyrin: 포크 및 기여"
          },
          {
            "level": 2,
            "id": null,
            "text": "2. 공개 기능: 데스크톱 클라이언트 없이도 가능한 자동화"
          },
          {
            "level": 2,
            "id": null,
            "text": "3. JoeLudwig: hl2sdk 기여자 태그"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/ko/investigation_part2.html#automation-map",
          "https://github.com/SteamRE/SteamKit",
          "https://github.com/SteamRE/open-steamworks",
          "https://github.com/alliedmodders/hl2sdk",
          "https://github.com/DoctorMcKay/node-steam-user"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ko/output_steam_network__valve_ru_farming_isolated.content.json",
      "export_json_sha256": "b13db476fe59950a435d1fdfbc1b8b0388a7adac2d0c4c28d391db808a6e29c6"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ja/card_economy.html",
      "language": "ja",
      "title": "カード経済 — 『Steam』特集",
      "source_url": "https://phishdestroy.io/steam_dossier/ja/card_economy",
      "source_html_sha256": "2961ebb44d768e508443d77b40e8ca647f1d909f57c5023013fcd0d177e87b1f",
      "exported_at": "2026-09-29T00:22:09.120Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "card_economy.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ja/card_economy.pdf?v=print-20260929-v5",
        "sha256": "bcf636745fe3a35def128ca1aaf7dd2c19a79566d51f49cab2138cf62a698596",
        "bytes": 1426295,
        "pages": 22
      },
      "integrity": {
        "signed_object": "card_economy.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "card_economy.content.json.asc",
        "digest_file": "card_economy.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify card_economy.content.json.asc card_economy.content.json",
          "sha256sum -c card_economy.content.json.sha256"
        ]
      },
      "content": {
        "text": "別紙V — カード経済\nボットファームは、Valveの店にある漏れではありません。それは顧客.\n\nSteamのアカウントは、その金額を使い切るまでは、トレーディングカードを1枚も受け取ることができません$5.00 ストア内において。所有していないゲームのカードを自動収集することはできず、無料で提供されたゲームのカードも収集できません。したがって、自動カード収集ツールが何かを生産する前に、そのツールは—アカウントごとに、Valveが公表する価格を支払って—利用権を購入しているのです。 そして、Valveの自動化条項は、そのファームが何を生産するかを一行ごとに具体的に規定している。 そのライセンスは、ファームされたカードが金銭に変わるあらゆる経路を禁じており；カードが何らかの形で流通する際には、そのマーケットが手数料を徴収する――広告価格は 15% だが、1販売あたり最低2セントが保証されており、これがセント単位で価格設定されたカードの場合、価格の大部分を占めることになる。 本稿では、その取引規模がどれほどか、プロファイルの最上位レベルがセット数でどれほどのコストを要するかを測定するとともに、アカウントが一般のトレーダーに属する場合、Valveの執行部門が同じ条項をどのように適用するかを検証する。\n\n農場がまず購入しなければならないものセットごとのレベルごとの費用机の両側カード経済を誰が調整しているのか\n$5.00アカウントでカードを受け取れるようになる前に、ストアでの利用実績が必要 — Valveのサポートページ\n13,876Steamのゲームで、トレーディングカードを発行し、99,971種類の異なるカードタイプを保有しているもの\n694,673現在、91の公開されている取引ボットが保有している完全なカードセット\n1,389,346当該在庫がすでに消費したアカウントおよびゲームカードの配布枠を、少なくとも\n$9.99カード付きゲームの価格の中央値 — 完成セットの中央値は $0.74 である。\n97,114カード交換グループのメンバーで、そのモデレーターリストに「Valve」という従業員名が記載されている――§ 08\n01 — プロセス\n農場とは実際にどのようなものなのか、順を追って解説\n\n本項の内容は、当該ツールの公式ドキュメントおよびValveのサポートページに基づいて記述されたものです。本項の内容には推測に基づくものは一切なく、また、いずれの当事者からも異議が唱えられていません。\n\nステップ1\n買い注文\n\nそのアカウントは、以下の条件を満たしてはなりません。限定. Valveのサポートページでは、制限付きアカウントによる「Steam市場への参加」, 出典：「Steam コミュニティアイテム（トレーディングカード、ブースターパック、ジェムなど）の取引」 そして、～から「プロフィールレベルが Steam 上昇（レベル 0 に固定）し、トレーディングカードを獲得」. ゲートとはお金のことだ：「その Steam 店舗で、少なくとも $5.00 USD 以上お買い上げいただく必要があります。」\n\nステップ2\nゲームを購入する\n\nカードは、所有しているゲームからのみ入手できます。「このゲームからカードがドロップされる対象となるには、Steamアカウントでそのゲームを所有している必要があります。ファミリー共有は所有とはみなされず、対象にはなりません。」 無料のルートも閉鎖されています：「キャンペーン期間中に無料で入手した有料ゲームでは、カードのドロップを狙って繰り返しプレイすることはできません」、および「F2Pゲームで、そのゲーム内で一切課金せずにカードを入手することはできない。」\n\nステップ3\nアイドル\n\nこのツールは、そのアカウントをSteamネットワークにヘッドレスでログインさせ、「バッジを解析します」, プレイ可能なタイトルのリストを作成し、開始します「対象となるゲームをプレイし、そのゲームのコンテンツがすでにすべて周回済みかどうかを定期的に確認する。」 そのメカニズムについて、メンテナが次のように説明しています：それは「Steamに、私たちが特定のゲームをプレイしていることを伝える以外に、何もしていない。」\n\nステップ4\nドロップがなくなる\n\n各タイトルは有限である。「どのゲームにも、カードドロップの数は決まっています。それらをすべて集めてしまうと（フルセットの約半分）、そのゲームはもはやファームの対象とはなりません。」 生産を続けたい農場は、タイトルを買い続けなければならない。カードの供給量は、購入によって制限されている――これは設計上の仕様であり、Valveにとって有利な仕組みとなっている。\n\nステップ5\n出金\n\nカードは、3つの方法のうちいずれかによって手元を離れます。すなわち、コミュニティマーケットでの売却、トレード、あるいは宝石への加工です。いずれもサブスクリプション・マーケットプレイスでの取引またはトレードに該当し、§ 3.D ではその手数料について次のように規定しています：「Valveは、サブスクリプション・マーケットプレイスにおける取引に対して手数料を徴収する場合があります。」 このステップこそが、全体を違反とする要因となる――参照：05.\n\n出典：2026-09-22で全文を引用・転載：Steam サポート — 制限付きユーザーアカウント ↗ ・ArchiSteamFarm よくある質問 ↗ ・Valve — Steam トレーディングカードに関するよくある質問 ↗ ・Steam 利用規約 ↗ アーカイブ済み 2026-09-24 ↗. 本ページでは、「ArchiSteamFarm」は被告としてではなく、測定器として使用されています。そのドキュメントには、次のように明記されています。「ASFはValveによる認可を受けていません」.\n\n02 — スケール\n農場が1セントの収益を上げる前に、すでにValveを支払っている。\n\n限定アカウントではカードを受け取ることができないため、ファーム内のすべてのアカウントが何かを生産する前に、限定ステータスを解除する必要があります。その基準額は公表されており、アカウントごとに課金されます。\n\n農場の規模\tその数字の由来\tカード発行の条件となる店舗での最低利用額\n10件のアカウント\tASFが推奨する上限は――「社内のValveガイドラインおよび当社独自の提案に基づき」\t$50\n100～200件のアカウント\t同じFAQに記載されている技術的な上限：「1つのIPアドレスと1つのASFインスタンスで、最大100～200個のボットを稼働させることができます」\t$500 – $1,000\n120件のアカウント\t以下の執行事例3 — 永久利用停止処分\t$600\n170件のアカウント\t以下の措置事例2 — 2017年ウィンターセール期間中に永久利用停止処分を受けた\t$850\n1,000 アカウント\t以下の執行事例1 — 取引禁止\t$5,000\n5,000 アカウント未確認\tオペレーター用はかり本調査に報告されたものであり、独自に確認はされていない —出典に関する注記を参照してください\t$25,000\n10,000件のアカウント未確認\tオペレーター用はかり本調査に報告されたものであり、独自に確認はされていない —出典に関する注記を参照してください\t$50,000\n\nこのページにある数値のうち、最後の2行だけが、文書ではなく未確認の報告に基づいている。これらは表の中でマークされており、その説明は調達に関する注記、そしてここにある他の要素はすべて、これらに依存している。右側の列は、Valveが公表した$5.00米ドルの閾値に基づく計算であり、それ以外の要素は一切含まれていない。これはフロア、これは農場のコストやValveの収益の見積もりではありません。所有している必要があり、プロモーションで無料で入手したものではないゲームは除外されており、また、カードを売却する際にコミュニティマーケットが徴収する約15%も除外されています。このページでは、収益額については一切記載されていません。\n\nそして、Valveはカードドロップの価格を自ら設定した。 同社のトレーディングカードに関するFAQでは、基本プレイ無料化による転換率を具体的な金額で示しています：\n\n「基本プレイ無料のゲームでは、ゲーム内での課金額に応じてゲームカードが配布されます。」0 USD ごとに（概算） 「Steam トレーディングカード・ベータの開始以来、カードが1枚入手できます。」\n\n—Valve、Steam トレーディングカードに関するよくある質問 ↗ ・逐語的に確認済み 2026-09-22\n\nトレーディングカードは、プラットフォームが赤字を出すような景品ではありません。それは、Valveが、Valveで公表された価格で販売するものであり、その後、転売の際に再度料金を請求するものです。だからこそ、カードファームを正直に表現すると、それは寄生虫. それは卸売バイヤー.\n\n購入するものが実際にどれくらいの大きさなのか\n\nここからこのセクションの終わりまでの内容はすべて、報告された数値ではなく、計測された数値に基づいています。カードの集計データは、Steam「Card Exchange」が公開しているバッジ価格表に基づいています。ゲーム自体の価格は、ValveのストアAPIから取得したものです。ボットの在庫データは、誰でもアクセスできる公開ボットディレクトリから取得しています。 これら3つはすべて 2026-09-22 で読み込まれており、計算の詳細は第08節.\n\n13,876カードを発行するゲーム\n99,971異なるカードの種類\n5・6・151セットあたりのカード数：最小値、中央値、最大値\n$0.74完成品のセットの価格の中央値\n$23,586.57市場に出回っている各セットのうち1つ\nその集合はどのくらいの大きさか\n\n13,876 セットに含まれるカードによるゲーム。 Valve そのうちの約半分を、任意の1つのアカウントに割り当てる。\n\n0\n1,250\n2,500\n3,750\n5,000\n5\n6\n7\n8\n9\n10\n11\n12\n13\n14\n15\nライセンスの費用\n\nSteamのストアにおける、同じゲームの定価（米ドル）。\n\n0\n1,000\n2,000\n3,000\n4,000\n<$1\n$1-3\n$3-5\n$5-10\n$10-20\n$20-40\n$40+\n完成したセットが返すもの\n\n同じゲームのコンプリートセットの市場価格。\n\n0\n1,500\n3,000\n4,500\n6,000\n<$0.50\n$0.50-1\n$1-2\n$2-5\n$5-10\n$10+\n\n2番目と3番目のグラフを並べて見ると、計算をしなくても取引の傾向が明らかになります。ゲームの数は数十ドル台に集中しており、それらがもたらすセット数は1ドル未満に集中しています。どちらも同じ「13,876」ゲームの数を、同じ軸単位で表しているため、この比較は2つの高さを比べているのであって、2つの目盛りを比べているわけではありません。\n\nこれが供給側です。需要側については、Valveが宣伝する必要はありません。なぜなら、それはすでに公に公開されているからです。カード交換ボットを一覧にした単一の公開ディレクトリには、次のように記載されています。現在、91体のボットが、694,673の完全セットを在庫として保有しています。 ログイン不要、マーケットプレイスのデータ収集なし、個人情報なし――在庫数は、各ボットの名前の横にあるページに表示されています。\n\nその株を、ここで唯一重要な銘柄にしましょう。Valve独自のルール：「ほとんどのゲームでは、そのゲームのカードセットに含まれる枚数の約半分に相当する枚数のカードがドロップされます……セットの残りの半分は、他のコミュニティメンバーから集める必要があります。\" 1つのアカウントだけでは、プレイしてセットを完了させることはできません。最低でも2つのアカウントが必要であり、それぞれがそのゲームを所有し、ゲームごとに1回限りのドロップ枠を使い切らなければなりません。ドロップ枠は回復しません。\n\n694,673在庫のあるセット、91の公開ボット\n3,473,365カードは、5枚以上という最低枚数が設定されています\n1,389,346消費されたドロップ手当、最低値\n2,6021つのゲームしか所有していないアカウント、ボットの密度が最も高い\n「694,673」のセットが置かれている場所\n\n上場している91社のカードボットのうち、在庫の完全セット数に基づいて上位12社を挙げます。上位10社の合計保有セット数は248,115セットで、これはボード上の全アイテムの35.7%に相当します。\n\n0\n11,250\n22,500\n33,750\n45,000\nCard Supply #4 (High)\nN!vq's Leveling (High)\nAlice [BOT] LEVEL-UP RARE SETS\nN!vq's Leveling (Low)\nDisco Lite Level Up\nN!vq's Leveling (Mid)\nbaty131store.net | Level Up\nKitten - Supreme\nArashirn | Level Up\nSH (Junior) Level Up\nDuobot.com - Overstock\nlvlupbot.com - godlike\n\nその139万の割り当てはすべて、ゲームを所有し、$5.00のゲートを突破しており、今後二度とそれらのドロップを生み出すことのできないアカウントに属していた。これは売れ残りの在庫 91体のボットについて。これは市場の指標ではなく、市場が終わった後に残ったものを測る指標である。\n\n最後の数値は、単純な集計ではなく、ピジョンホール法による分類結果です。あるボットは、わずか11本のゲームから抽出された14,310セットをリストアップしているため、それらのゲームのうち少なくとも1本は1,301セットで表されており、これはそのゲームを購入した異なるアカウントが少なくとも2,602つ存在することを意味します。 これは算術的に許容される最小値であり、91体のボットのうち1体に該当するものです。\n\nこの床が伝えていること、そして伝えていないこと\n\nこれらのボットは、一般プレイヤーやファームからカードを購入します。公開されている買取価格が、このディレクトリの主な情報源となっています。つまり、139万件の割当枠は、農家が所有する口座の件数ではないということです。 これらは、アカウントごとに1回、ゲームごとに1回というドロップ制限枠の分であり、Steamのどこかで消費されたものの、売れ残って市販在庫として残ってしまったものです。 それぞれの背後にあるアカウントがファームアカウントであったか、あるいはバッジページをクリアしようとしている10代の若者であったかは、Valveが収集した内容――$5.00のアンロック、ゲームライセンス、そして取引のたびに発生するマーケットの手数料――には何の影響も与えません。15%ではなく、15%、あるいは2つの1セントの最低額のうち、いずれか大きい方、これはセント単位で価格が表示されたカードでは、はるかに大きな金額となります。計算式は以下の料金表. それがこのページの趣旨であり、農家に対する不満を述べているわけではありません。Valveが利用料を課しているのと同じ行為こそが、「商業目的での利用」を理由に個人を永久に利用停止処分にする際、同サイトがそのままの文言で引用している行為そのものなのです。\n\nこの数値は、別の意味でも下限値となっています。これは、以下の条件を満たす株式のみをカウントしており、本日出品され、未売りの商品 ボットについてパブリックディレクトリに配置することを選択する. すでに完売した商品、非公開の商品、およびディレクトリ外にあるボットはすべて除外されます。\n\nそれに、Valveの価格では、農業は採算が取れない\n\n「農場」が安価なゲームを購入して高価なカードを鋳造するという反論は当然あるだろう。しかし、Steam自身のストアAPIはそうではないと示している。13,876枚のカードを含むゲームのうち、13,713について価格が確定した；12,918は有料タイトルであり、定価の中央値は$9.99です。 完成セットの価格の中央値は$0.74。1セットにつき2つのライセンスが必要です。したがって、セットの価格は中央値でおよそ$19.98 ゲームライセンスの生産数および返品数 $0.74.\n\n2026-09-22で測定\t値\tその内容\nカードゲームのリスト価格の中央値\t$9.99\t取引において高額なのはカードではなく、ライセンスの方だ\n価格が $4.99 以下のゲーム\t3,665 (28.4%)\tたとえ安っぽい尾であっても、そこから得られる一式よりはまだ高価だ\nこのストアで最も安いカードゲーム\t$0.99\t通常は$1.30以下で販売されているセットのライセンスが2つ、$1.98\nゲーム本体よりもそのセットの方が高値で取引されているゲーム\t323 / 0 (1)\t40試合のうち1試合で、Steamの定価に対するカードアービトラージが発生している\n調査対象の基本プレイ無料タイトル\t795\tまた、Valveは各ドロップの価格を、ゲーム内課金で$9と設定している\n\nこれにより、経済的な問題はValveに有利に、そして通説に反する形で決着がついた。Valve自身が設定している価格では、カードファーミングは赤字となる活動であり、Steamの定価より安く入手したライセンスでのみ成立する — バンドル、地域別価格設定、主要な再販。カードは単なる副産物に過ぎない。購入こそがイベントなのだ。そして、その購入はSteamに行われた。\n\n農場が実際に支えているもの\n\nこれらの要素を総合してみると、農場はもはやValveが「容認している」対象ではなく、Valveが「必要としている」対象のように見えてくる。農場が供給するあらゆる投入物は、Valveが報告したり請求したりする産出物である。あるボットアカウントの外部への動きを追ってみよう：\n\n1つの偽アカウント「卸売顧客」であり、情報漏洩ではない\nゲームの売上\n\n自分がプレイしているタイトル――13,876のカードゲームから$0.50の粗製濫造ゲームまで――を購入する。なぜなら、カードは所有しているゲームからしか入手できないからだ。\n\n「オンライン」と遊びの時間\n\nプレイヤーをアイドル状態にさせてカードをドロップさせ、Valveが「エンゲージメント」として挙げている同時接続プレイヤー数やプレイ時間といった数値を水増ししている――まさに§4.Cが「プレイ時間の偽装」と呼ぶ統計データそのものである。\n\n登録\n\nカードを受け取るには、まず$5.00の制限付きアカウントのゲートをクリアする必要があります。これは、1アカウントにつき実店舗での購入実績Valve冊に相当します。\n\n財布の中身と手数料\n\n販売されるカードはすべてマーケットを経由して処理され、低額カードの場合、手数料は最大で66.7%に達し、売上金はSteamウォレットにロックされたままとなります。\n\nSteamレベルのPR\n\nバッジやレベル Valve のランキングが存在するのは、セットが作成されたからに他なりません。そして、そのランキングのトップはボットによって占められています（§ 03 参照）。\n\nファームを削除すると、上記のすべての数値が減少する — ゲームの売り上げは伸び悩み、「オンライン」ユーザー数は少なく、アカウントは登録されず、利用料も徴収されず、レベルも到達されなかった。だからこそ、自動化を禁止するルールが存在しながらも、何百万もの自動化されたアカウントが共存しているのだ。禁止こそが選択肢であり、その活動こそが収益源だからである。\n\nそして、キャッシュアウトそのものが価値の流出源となる――税金が二重に課されるからだ\n\nそのカードはループの終わりではありません。Valve独自のメカニズムにより、カードは押しつぶされて宝石、そしてジェムを使ってクラフトするブースターパック — さらに3枚のカード — これらは売却されるか、再び破棄される。各ステップは市場取引または変換であり、それぞれに課税される。そのループの方向性は、以下で測定される手数料の下限から導き出され、外部のモデルを必要としない。そのループ内で売却されるカードはすべて、少なくとも2セント、3から5で取引されるカードにおいて、クランクを1回回すごとに、投入した分よりも少ないリターンしか得られません。このループは仮想的な価値を破壊し、その代わりとなる新たな手数料を伴う取引を強いることになります。ここでは、その損失の規模に関する数値は示されていない。 — セットごとのリターンは、本調査では測定していないジェムの出現率やブースターの当選確率によって異なります。\n\nトレーディングカード所有しているゲームからのドロップ\n→\n宝石カードが破損し、手数料が徴収された\n→\nブースターパック製作に消費したジェム\n→\n新しいカード3枚Marketで販売済み、手数料は徴収済み\n↶\n\nここではメカニクスだけが述べられており、それらはValve独自のものです――カードはジェムに変換され、ジェムでブースターをクラフトし、ブースターからカードが得られる――これらはすべてSteamトレーディングカードFAQに記載されており、それぞれの段階が課税対象となるマーケットイベントとなります。ループメカニクスの出典：Valve、Steam トレーディングカードに関するよくある質問 ↗.\n\nこれは単なる一過性の現象ではありません。長年にわたる基盤を持つ産業なのです。\n\n単一のスナップショットは偶然の一致である可能性もある。そこで、2022年から2026年にかけて、ウェイバックマシンを用いて、季節ごとのSteamセールごとに1回ずつ、公開されているカードボットのディレクトリを読み込んだ。そこには、ボットが保有していた固定の在庫と、セールごとに同じアカウントが記録されていた。 この経済活動は、突然現れては消えるようなものではなく、安定した運営者層を中核として持続しており、そのピーク時には在庫あり：300万セット 2023年冬のセール期間中――あるディレクトリに、ある時点で価値のあるTF2キーが30万個ほど保管されていた。\n\nパブリックボットディレクトリに保存されている完全なカードセット（販売数：Steam）\n\n各シーズンセールごとに、steam.supply/CardBotsのWaybackスナップショットが1つ保存されます。カーソルを合わせると、そのスナップショットのレートに基づくTF2キーの価値が表示されます。\n\n0.0M\n0.9M\n1.8M\n2.6M\n3.5M\nA’22\nS’23\nW’23\nS’24\nW’24\nS’25\nS’26\n401各販売チャネルで確認された個別のボットアカウント\n597回の売上のうち5回以上に存在 — 安定した中核\n162022年から2026年にかけて開催された7回のオークションすべてに出品\n3.22M在庫のピーク（2023年冬） ≈ $570k～790k（キー数）\nトップから見た、あるセールスのバッジラダーの様子\n\n需要側は供給側と一致している。一般市民の間では2024年サマーセール バッジラダー アーカイブ済み 2026-07-16 ↗、1位のアカウントが「販売バッジ」を作成していた1,740,645回 — 174万セットの10枚組カード、1,740万枚 1つのプロファイル装飾にまとめられています。このセールの市場価格（1セット $0.50）では、それは~$870,000 カードの価値についてですが、実際の購入方法――TF2のキーをボットのレベルアップに交換する（キー1つにつき約7.6セット）――で考えると、それは~229,000 キー、約 $410,000–$570,000 実質的に言えば。2番目のアカウント：552,000セット、~$130,000–181,000。これを狙ってプレイする人間はいない。これは購入されるものであり、購入の各段階は、Valveが清算する取引である。\n\n方法と制限事項：各スナップショットにリストされているボット全体について、セットストックを合計します。番号 スナップショットごとのボット数は、販売状況によって比較できない。一部のスナップショットには注目ボットのみが表示され、他のスナップショットにはディレクトリ全体が表示されるため、在庫数は「表示されていたボット数の下限」として解釈され、完全な集計値ではない。 キーの値については、各スナップショットにおける「キーあたりの広告セット数」の中央値と、$1.79–$2.49のTF2キーを使用しています。スナップショット間の継続性はSteamID64によって確保されています。2021年のスナップショットは旧式のページレイアウトを使用していたため、対象外としています。データ：farm-economy-timeline.json; SteamLadderのバッジレベル; Steam カード交換所での設定価格（販売時のWaybackスナップショット、$0.05 1枚あたり）。\n\nまた、セールが行われていないときでも、同じ船団がそこにいる\n\n上の2枚の写真は、2つの集団ではありません。これらは、異なる瞬間に撮影された1つの艦隊です。このセクションの冒頭で読み込まれたディレクトリは、季節限定セールが行われていない、ごく普通の日 — 2026-09-22 — そして、静止しているときでさえも、それは維持されていた91体のボットと 694,673 セット: およそ186,000 TF2のキー、$334,000–$464,000のカードの数値、放置中 販売の合間。これは、何も起きていないときに事業が抱える最低水準のことです。\n\nそして、これは同じ操作です。SteamID64で照合され、その91体の休止中のボットのうち87体 — 96% — は、上記の7つの販売スナップショットにも登場しています、そのすべてに16台ずつ収められている。このディレクトリは、販売のために開いて、その後閉まるような一時的な露店ではなく、この同じ車両群によって膨れ上がり、その数は322万セット 2023年冬のピーク時には、その数値は決してゼロまで下がらない。セールとは、商品が売れる時のことだ。それは1年の他の時期にも存在している。\n\nボットごとのデフォルトディレクトリ\n\n各四角は、ディレクトリ「2026-09-22」にあるボット1体を表しており、7つの販売スナップショットにも含まれている場合はハイライト表示されています。91という数字は、その日に名簿に記載されていたものであり、艦隊の規模を示すものではありません。 — 販売状況のスナップショットには401の異なるアカウントが確認され、ディレクトリには日によって異なる一部が表示されています。\n\n過去のオークションでの出品実績 (87)前回のスナップショットからの変更点 (4)\n\n同じ公開ディレクトリから、ログインなしで読み取った非セール時のベースライン値は 2026-09-22 です。待機時の値は、各ボットが公表している「キーあたりのセット数」と、その上の $1.79–$2.49 のキー帯域に基づいて算出されています。 重複の判定は、7つのセールスナップショットに対するSteamID64によるものです。スナップショットごとに「注目リスト」と「全リスト」の内容が異なるため、この比較では在庫数やユーザー数ではなく、在庫とIDの照合が行われます。計算式は第08節.\n\n03 — はしご\nもう一つの商品は、お名前の横にある番号です\n\nカードは原材料です。完成品はレベル Steam で、Valve がセット単位で価格を設定します。\n\n100Steam レベル\n目標レベル — ドラッグするか、矢印キーを使用してください\n1セットあたりの価格、米ドル\n\n$0.20は調査対象の中で最も安価なフルセット、$0.74は中央値、$1.70は平均値です。この数値はカードのみを対象としており、$5.00のアンロックやゲームライセンスは一切含まれていません。\n\n55,000XPが必要\n550消費された完全セット数\n110手元に置いておきたいゲーム、自分で素材を集める\n$407.00その価格でのカードの費用\n1,100燃焼したドロップ手当、最低額\n$5,500.00$5.00 アカウントの再利用がない場合、ロックが解除されます\n消費したセット数：レベル 1 ～ 1,000\n\nバッジクラフト1つ＝1セット＝100 XP。10単位ごとのレベル区切りごとに、その直下のレベル区切りよりも100 XP多く必要となります。\n\n0\n12,625\n25,250\n37,875\n50,500\n1\n250\n500\n750\n1000\n667\n550 sets\n\nレベルは、Valveがそのまま放置できるような装飾品ではありません。アカウントに紐付けられています。Valve自身の「トレーディングカードFAQ」によると、バッジを作成すると何が得られるかについては、次のように記載されています：「100XP。これにより、レベルがSteam上がる可能性があります。」Steamレベルが上がると、フレンドリストの上限が5人分増えます「……そして、場合によっては、ショーケースを使ってプロフィールをカスタマイズできるようになるかもしれません。」 そして、ブースターパックについては：「レベルがSteam上がるごとに、ブースターパックのドロップ率が上昇します。レベル10：+20%… レベル50：ドロップ率が+100%上昇（つまり、ドロップ率が2倍になります）。」\n\nつまり、このレベルでは2つの要素が購入できる――0――「友達になれる人数」と「無料カードがインベントリに落ちる速度」だ。 後者は相乗効果をもたらします。消費したセットが多ければ多いほど、プラットフォームが新たな素材を供給する速度は速くなります。Valveは、この再投資のループを製品に組み込みました。\n\n為替レートは固定されており、公表されています。バッジクラフトを1回行うごとにセット1つを消費し、100 XPを獲得できます。「同じゲームのセットを作成できるのは、最大で5回までです。」 レベル1あたりのXPコストは、10レベルごとに上昇します。その結果、以下のようになります。なお、ここにある数値はいずれも概算ではありません：\n\nSteam レベル\t消費する完全なセット\t自分で作るために必ず手に入れておくべきゲーム\t記録上最も安い水準（$0.20）で\t中央値の集合（$0.74）において\tスケール\n10\t10\t2\t$2.00\t$7.40\t\n50\t150\t30\t$30.00\t$111.00\t\n100\t550\t110\t$110.00\t$407.00\t\n200\t2,100\t420\t$420.00\t$1,554.00\t\n500\t12,750\t2,550\t$2,550.00\t$9,435.00\t\n667\t22,579\t4,516\t$4,515.80\t$16,708.46\t\n\n667は単なる仮定の話ではありません。これは、パブリックディレクトリに登録されている単一のボットが、6,117のゲームにわたって保有する33,359のセットのうち、顧客を到達させることができると宣伝している最高レベルです。 4列目は、調査対象全体で最も安価な完全セットと比較した価格であり、5列目は中央値と比較した価格です。いずれもカード単体の市場価格であり、$5.00のアンロック費用およびゲームライセンス費用は一切含まれていません。\n\nValveはそれを公表していないため、その曲線がどのように確認されたのか\n\nValve はバッジの獲得率を示しています（「XPが100ごとに、レベルがSteam上昇します」) その後、それをヘッジして――「（少なくとも最初は）」 — エスカレーションを公開せずに。 上記で使用した曲線は標準的なものであり、10単位のブロック内の各レベルは、その下のブロックよりも100 XP多くかかる。これは仮定ではなく、ディレクトリに基づいて検証されたものである。つまり、1ゲームあたり5クラフトという上限ではなく、所持数によって公表最大値が制限されているボットについては、この曲線から算出されたレベルは、ボットが提示しているレベルと完全に一致する — 541 対 541、494 対 494、464 対 464。一方、キャップが適用される場合、算出値は数レベル高くなるが、これは試合ごとの選手層の厚さにも依存するキャップとして当然の挙動である。 レベル667を超える範囲の曲線については、何ら主張するものではない。\n\nセクション02の横にある表を見れば、このビジネスの仕組みがわかります。 1つのアカウントをレベル500にするには、誰かが12,750セットを揃えなければなりません。それらのセットのそれぞれには、少なくとも2つのアカウント分のドロップ許容量が必要であり、それらのアカウントはすべて$5.00のゲートを突破しており、それぞれがゲームを所有していました。あるプロフィールの上部に表示されている1つの虚栄の数字は、その下にある少なくとも25,500の消費済みドロップ手当に基づいています。 Valveはその取引で損失を被ることはない。Valveはその取引の各レッグの取引相手である。\n\n04 — 統計\nこの条項は、農業について漠然と記述しているのではなく、具体的に列挙している。\n\n§ 4.C は、ボット対策の一般的な規定ではありません。そこに列挙されている例は、カードファームが生み出す 2 つのものを順に挙げています。\n\n「Steam上のコンテンツおよびサービスとやり取りを行うにあたり、いかなる形態のスクリプト、ボット、マクロ、またはその他の人間による制御を受けないシステム（以下「自動化」といいます）も、いかなる方法においても使用してはなりません。これには、以下が含まれますが、これらに限定されません：\n\nSteamアカウントの作成プロセスを自動化し、\nゲームプレイの統計データを偽造すること（例：勝利数や敗北数、経験値、プレイ時間の水増しなど）、\nユーザーによる真の関与なしに報酬や進捗を獲得すること、\n「自動化された手段を通じて、査読システム（ピアレビューや「オーバーウォッチ」など）に参加すること。これには、十分な情報に基づいた判断ではなく、スクリプト化された動作によって結果に影響を与えたり、ユーザーを通報したりすることが含まれる。」\n—Steam 利用規約 第4条C項 ↗ アーカイブ済み 2026-09-24 ↗ ・原文をそのまま引用 2026-09-22\n「…遊びの時間」\n\nアイドル時間は「架空の時間」ではありません。ASFのFAQでは、この疑問に率直に答えています――「ASFで獲得したゲームのプレイ時間が増えないのはなぜですか？」 — 提供：「そうです。ただ、リアルタイムではありません。Steamは一定の間隔でプレイ時間を記録し、それに基づいて更新をスケジュールしています……通常は30分おきくらいに更新されます。」\n\nこれらの利用時間は、Valveの記録、Valveのストアページ、およびValveが独自に公開している同時接続プレイヤー数に反映されます。Steam チャート ↗ アーカイブ済み 2026-09-23 ↗. これらの数値では、非アクティブなアカウントとプレイ中のアカウントを見分けることはできません。同プラットフォームが対外的に公表しているエンゲージメント数は、同プラットフォーム自身のルールに基づき、プレイしていないアカウントも含めたユーザー全体を基に算出されています。\n\n「…ユーザーからの真摯な意見がなければ」\n\nこれは、Valveによって書かれた「アイドル状態のカードドロップ」の定義です。また、これに伴うSteamレベル、バッジ、ブースターパックの購入資格、およびプロフィールXPの定義でもあります。ASFのFAQでは、このツールが有効であることが確認されています。「ブースターパックを受け取る権利を維持する」, というのも、公式クライアントと同じようにログインできるからです。\n\nつまり、報酬システムと禁止行為は、同じ仕組みを異なる側面から見たものに過ぎない。Valveは、報酬がスキルではなく時間によって生み出されるように仕組みを構築し、その時間を費やした本人以外による報酬の獲得を禁じる条項を設けた。\n\n05 — 商用利用の落とし穴\n「ファームされたカード」からのあらゆる退出は、ライセンスで禁止されている退出であり、Valveはその都度、入場料を徴収する\n\nこれは、「責任を持って」ファーミングを行うだけでは解決できない問題です。このライセンスは個人による非商用利用を目的としたものであり、ファーミングを行う価値が生まれるのは、それが「個人利用」の範囲を超えた瞬間からです。\n\n§ 2.A — ライセンス\n\n「Valveは、本契約に基づき、コンテンツおよびサービスを利用する非独占的なライセンスおよび権利を付与し、あなたはこれを受け入れるものとする。個人的かつ非営利目的での利用 （本規約または該当するサブスクリプション規約において商業利用が明示的に許可されている場合を除く）。」\n\n§ 2.G — 制限\n\n「以下の権利は認められません：……（iii）コンテンツおよびサービス、またはその一部を、いかなる商業目的にも利用すること「ただし、本契約（サブスクリプション規約または利用規約を含む）の他の箇所で明示的に許可されている場合を除きます。」\n\n§ 3.D — 手数料\n\n\"Valveは、サブスクリプション・マーケットプレイスにおける取引に対して手数料を徴収する場合があります。 「手数料が発生する場合は、取引完了前にその旨をお知らせいたします。」\n\nこの3つを合わせて読むと、そのポジションは終了します\n\n手元に残したカードは、農場にとっては何の価値もありません。売却、交換、あるいはジェムに加工されたカードは、価値を生み出すために活用されたことになります。そして、Valveは独自の執行通知の中で、これを何と呼んでいるかを明記しています。170体のボットを運用していた運営者には、そのアカウントについて「Steamにおいて、収集用カードを違法に収集するために利用されたほか、これに関連する活動や、商業活動以外の活動にも利用されていた。」 その件では、カードは市場に出回った。販売は完了した。手数料も徴収された。禁止措置はその後に出された。\n\nその入り口の料金は 15% ではありません。ファームされたカードでは、その3分の2に達します。\n\n§ 3.D 留保事項「手数料」. 農場が実際に生産するカードでは、その手数料は宣伝されている～15%とはかけ離れています。コミュニティマーケットでは、5% Steam の取引手数料と 10% のゲーム利用料。それぞれ下限は $0.01 です。 （Valve独自のコミュニティマーケットFAQ）。1セントで出品されているカードには、それらのフロアがは 価格：購入者は3セントを支払いますが、そのうち2セントは手数料です。切り捨てルールにより、表向きの価格「15%」は、実際には最大で66.7% まさにカード市場の現実――1枚あたり数セントという価格帯だ。\n\nコミュニティマーケットでの販売における実質手数料（売り手の希望価格に基づく）\n\n5% Steam + 10% ゲーム、それぞれ最低 $0.01。網掛けの帯が、トレーディングカードが実際に取引される範囲であり、1枚あたりおよそ $0.03～$0.05 程度です。\n\n0%\n10%\n20%\n30%\n40%\n50%\n60%\n70%\ncards\n$0.01\n$0.10\n$0.20\n$0.30\n$0.40\n$0.50\n66.7%\n売り手の希望は\tSteam 5% (最小 $0.01)\tゲーム 10% (分 $0.01)\t購入者負担\t合計料金\n$0.01\t$0.01\t$0.01\t$0.03\t66.7%\n$0.03\t$0.01\t$0.01\t$0.05\t40.0%\n$0.05\t$0.01\t$0.01\t$0.07\t28.6%\n$0.08\t$0.01\t$0.01\t$0.10\t20.0%\n$1.00\t$0.05\t$0.10\t$1.15\t13.0%\n\n10%のゲーム手数料はカードを発行したアプリに支払われ、5%はValve自身のものとなり、Valve自身のタイトルや基本インベントリアイテムについては、手数料の全額がValveのものとなる。 いずれにせよ、お金はファーマーから流出することになります――3セントのカードを販売しても、1セントしか戻らず、2セントを失うことになります。これを、ファームが生み出す5セント未満のカードの数十万件の販売数で乗じると、「Valveが請求しうる手数料」 これはビジネスモデルであり、単なる付記ではない。出典：Steam コミュニティマーケットのよくある質問 — 手数料 ↗ アーカイブ済み 2026-09-21 ↗, 2026-09-22と読みます。この曲線は、公表されているこれら2つの金利とその$0.01のフロアに基づいて算出されています。\n\nこの規定を免れるようなツールの設定は存在しません。たとえ1人のユーザーが1つのアカウントで、極めて節度を持って運用していたとしても――そのユーザーが「ファーム」で入手したカードを1枚でもウォレット資金と引き換えに売却した瞬間、§ 2.Gの同じ条文が、1万枚を扱う運営者と同様にそのユーザーにも適用されることになります。 したがって、Valveは、自社のマーケットプレイス上の事実上すべてのカード販売者に対して適用しうる違反条項を留保しておきながら、事実上すべての販売者に対してその適用を見送っている。その頻度で適用されるルールは、もはやルールとは言えません。それは単なる選択肢に過ぎません。 この展示が投げかける問いは、なぜカードファーマーが黙認されているのか、ということではない。 なぜ、カードを販売する個人ユーザーに対しては同じ措置が取られる一方で、それらのカードが支えとなっている商業的なカード経済――取引サービス、レベルアップボット、大量販売業者――は公然と運営され続け、その最大規模のグループの一つが Valve 社員によって管理されているのか（§ 08）。この規制違反の適用は小規模な保有者に対してのみ行われ、機械に対しては適用されない。\n\n06 — 執行実績\n予告なしに、波のように次々と、電話番号をたどって広がっていく\n\nValveは、事前の通知を要しない権限を、契約書の自動化条項の直後の条項として明記した。\n\n「Valveは、違法な行為や活動、チートや自動化に該当する行為、あるいはSteamの『オンライン行動規範』に違反する行為があった場合、お客様のアカウントまたは特定のサブスクリプションを制限または終了させることがあります。」お客様は、Valveが、お客様のサブスクリプションおよび／またはアカウントを解約する前に、お客様に通知を行う義務を負わないことを了承するものとします。\"\n\n—Steam 利用規約 第4条D項 ↗ アーカイブ済み 2026-09-24 ↗ ・逐語的に確認済み 2026-09-22\n\n1,000+ ボット・取引禁止。 「このアカウントは、ボットアカウントのネットワークを管理するために使用されていたようです。ボットの利用は、Steam利用規約に違反します。」\n\n170以上のボット・永久BAN、2017年ウィンターセール。 「このアカウントは、Steamにおいて、収集用カードを違法に収集する目的で使用されたほか、商業活動に限らず、それに関連する活動にも利用されていました。当該アカウントは永久に利用停止となっており、Steamサポートではこの件に関してこれ以上のサポートを提供することはできません。」\n\n120以上のボット・永久BAN。 「このアカウントやその他のアカウントは、当社のネットワークインフラへの過剰なトラフィックを発生させるために使用されましたが、これはSteamのオンライン行動規範に違反する行為です。」\n\n— Steam ArchiSteamFarmのFAQの「それによってアカウント停止になった人はいますか？」という項目に、応援メッセージが掲載されています。出典 ↗ ・逐語的に確認済み 2026-09-22\n事例4 — 2025年6月、VAC アイドル状態のCS2に対する禁止措置\n\n上記の3件よりも後の出来事が、プロジェクト独自のトラッカーに記録されています。このツールを通じて『Counter-Strike 2』をアイドル状態にしていただけのアカウントには、VAC 禁止 — 不正行為対策の種類のことであり、管理上の種類のことではない。メンテナーの見解では、アイドル状態ではそれが発生し得ないとしている。なぜなら、それは「Steamに、私たちが特定のゲームをプレイしていることを伝える以外に、何もしていない。」 その原因については諸説ある。しかし、それらのアカウントが停止されたという事実については異論の余地はない。\n\n—ArchiSteamFarm ディスカッション #3440、2025年6月26日開設 ↗ ・閲覧数 2026-09-22\n\nメインアカウントが消滅する仕組み\n\n同じスレッド内で、プロジェクトの協力者が禁止措置の適用ルールについて次のように説明しています。アカウントは利用停止処分を受ける可能性があります。「チェーンで」、同じ電話番号を使用している場合 —「これは、単に1つのVACアカウントに対する禁止措置に過ぎないが、その禁止されたアカウントに関連する『クリーン』なアカウントにまで波及している可能性がある。」\n\nSteam Guardでは電話番号の登録が必要です。ファームは運営者の電話番号に基づいて構築されます。したがって、取り締まりは使い捨てアカウントだけで終わるわけではなく、共有識別子をたどって、ライブラリ、フレンドリスト、インベントリを保持するアカウントにまで及ぶのです。 あるプロジェクトの協力者が説明しているメカニズムによれば、たった一つの行動によって、運営者のメインアカウントとファームが同時に削除されてしまう。そして、これが、取り締まりの波による損失が $5 アカウント単位では測定されない理由である。 （ASF GitHubディスカッション#3440において、あるプロジェクトの貢献者によって説明されています。公式なValve確認や記録上の正式な先例はありません。）\n\n5年の間隔を置いて、3人の異なるエージェントが書いた同じ段落\n\n農業を規約違反とする条項――個人向け非商用ライセンスの商用利用――は、農場だけに限定されたものではありません。これは、Steamが取引を理由にアカウントを閉鎖する際に常に提示する理由であり、その理由は定型文として提示されます。 以下は、5年の間隔を置いて、3人の異なる実名の担当者から通知を受け取った人々が公開した3つの事例です。\n\n9月29日 午後7時56分、Steamサポートからのメッセージ\n\n「現在投稿しようとしているアカウントは、Steam利用規約に違反したためロックされています。取引履歴、コミュニティからの報告、その他の要因に基づき、当該アカウントは商用目的で使用されているものと判断されました。」\n\nこのロックは永続的なものであり、Steam サポートではこれ以上の対応はできません。\n\n弊社で把握している情報はすべてお伝えしましたので、このヘルプリクエストを終了させていただきます。なお、この件に関するこれ以上の返信はございませんので、あらかじめご了承ください。\n\n敬具、\n「ハル」\n\nこのヘルプリクエストは閉じられました。\n2020年9月29日。受信者が以下のコメントを添えて投稿しました。「RIP Trading。」 —@gergelyszabo94 ↗\nサポートからのメッセージ Steam 7月12日 22:41\n\n「現在書き込みを行っているアカウントは、Steam利用規約に違反したためロックされています。取引履歴、コミュニティからの報告、その他の要因に基づき、当該アカウントが商業目的で使用されていると判断されました。」\n\nこのロックは永続的なものであり、Steam サポートではこれ以上の対応はできません。\n\n弊社として提供できる情報はすべてお伝えしましたので、このヘルプリクエストを終了させていただきます。今後、アカウントのロックに関してヘルプリクエストを送信された場合、返信なしに終了される可能性がある点にご留意ください。\n\nSteam サポート\n「Vido」\n\nこの支援要請は終了しました。\n2024年7月12日、ポルトガル語版インターフェース。受信者はCS2のプロプレイヤーです：「すでにSteamのサポートに連絡しましたが、自動返信しか返ってきません……Faceitもプレイできませんし、プロマッチもプレイできません。」 —@prcs25 ↗ アーカイブ済み 2024-07-15 ↗\n投稿者 r/steamsupport による引用\n\n「こんにちは。現在ログイン中のアカウントは、Steam利用規約に違反したため、利用停止措置が講じられました。取引履歴、コミュニティからの報告、その他の要因に基づき、当該アカウントが商業目的で使用されていると判断されました。」\n\nこのロックは永続的なものであり、Steam サポートではこれ以上の対応はできません。\n\n弊社として提供できる情報はすべてお伝えしましたので、このヘルプリクエストを終了させていただきます。今後、アカウントのロックに関してヘルプリクエストを送信された場合、返信なしに終了される可能性がある点にご留意ください。\n\nSteam サポート\n「サリー」\n\n3回に分けて、それぞれ別の依頼で受け取りました。\n2025年3月29日。この投稿者はアカウントのロックに対して異議を申し立てていたわけではなかった――アカウントとメールアドレスが乗っ取られてしまい、アクセス権の回復を求めていたのだ：「アカウント停止について尋ねているわけでも、それに異議を唱えているわけでもありません。ただ自分のSteamアカウントにアクセスしたいだけなんです……Valveは、私のすべての問い合わせに対して、このまったく同じ回答をコピペして送ってくるだけで、その都度問い合わせを閉じられてしまいます。」 —r/steamsupport ↗、本調査独自の苦情コーパスに含まれるもの\n\n一語一語、一カンマ一カンマ、55か月にわたり、3人のエージェントと2つのインターフェース言語を介して。本文中で唯一の修正は、2020年から2024年にかけて、最後の文がより強固なものになった点であり、元の「これ以上の返信は届きません」 ～へ「今後のお問い合わせについては……返信なしに閉じられる場合があります。」 これらの決定に至った経緯がどのようなものであったにせよ、その書簡にはその経緯が記録されていない。 挙げられている理由は「取引、コミュニティからの報告、およびその他の要因」である。つまり、あるカテゴリー、出所不明の報告、そして名指しされていないその他の要因である。\n\n同じ方法で収集された、さらに5つの事例です。最初の3つは同じカテゴリーで、結果も同じです。最後の2つは、同じ机で、異なる規則に対して同じ言葉で回答したものです：\n\n日付\tそのアカウントが行ったこと\t何が起きたのか\t出典\n2021年12月4日\tBuffでの売買 —「バフ、つまりP2P取引での売買以外には、何もしていません」\tコミュニティからの追放：マーケット利用不可、取引不可、高価な在庫が凍結される\tr/csgomarketforum ↗ アーカイブ済み 2025-03-27 ↗\n2021年12月6日\tBuffおよびBitskinsを介した、装備セットやトレードアップのための片方向P2P取引\t業務用常設ロックとコミュニティ用ロックの併用：「疑似非表示モードから抜け出せない……プロフィールも非公開のままになっている」\tr/GlobalOffensiveTrade ↗ アーカイブ済み 2021-12-06 ↗\n2024年12月20日\t2017年からアカウントを保有しており、プレイ時間は数千時間にのぼる。コミュニティマーケットプレイスで、テーマ別の装備セットやアップグレード品を取引している。\tコミュニティロック付きの恒久ロック。事前の警告やストライクなし。サポートあり「その決定は最終的なものであるとしている」、返信は自動で行われます\tr/csgomarketforum ↗ アーカイブ済み 2025-06-27 ↗\n2024年12月23日\t1年間利用を中断していたユーザーが、VPN経由でウォレットに資金を追加した「一般的なインターネットセキュリティのみを対象としています」\tコミュニティからの永久追放、および理由が一切示されていない:「この利用停止措置は恒久的なものであり、これ以上の情報は提供できません。また、今後のチケットについても、回答なしに閉じられる可能性があります。」 「いいね」196件、返信340件\tr/steamsupport ↗\n2026年8月4日\t長年にわたりイランから商品を購入してきたが、筆者は「投稿したこともなく、マーケットもフォーラムも利用したことがない」と述べている。\tコミュニティへのアクセスが制限されています2038年まで 以上「制裁対象地域」; チケットは「Azul」という名前のエージェントによってクローズされました。同じアカウントによる、同じイランのIPアドレスからの返金は、1年前に承認されていました。図書館とお金はValveの手に残ります。\tr/pcgaming ↗\n\n最後の行は、他の行とは異なるルール（商業利用ではなく、制裁遵守に関するもの）ですが、回答の形式がまったく同じであるため、ここに含めています。つまり、カテゴリーが指定され、証拠はなく、異議申し立てもできず、チケットはクローズされた状態です。また、この行は他の行にはない疑問を提起しています。もしそのアカウントへのサービス提供が違法だったとしたら、長年にわたる支払いを受け取っていたことも違法だったことになります。 この2つの立場のうち、どちらかが間違っているはずであり、顧客に金銭的負担を強いたのはそのうちの1つだけである。\n\n8件すべては2026-09-22で閲覧された。2021年および2024年12月のスレッドはインターネットアーカイブのスナップショットを通じて、残りはRedditの公開フロントエンドを通じて閲覧された。これは、Redditが収集元からの直接的なリクエストを拒否したためである。 2020年と2024年の2通の手紙は、現在も公開されている元の投稿に添付されたスクリーンショットから転記したものです。本調査において、これらのアカウントのいずれについても、無実であるとか有罪であるとかは一切主張されていません。それこそがまさに重要な点なのです。その手紙からは、読者も規制当局も、その真意を推し量ることはできない。\n\n調達に関する注記 — オペレーター規模の損失\n\n本調査で聞き取りを行った事業者らは、次のような規模の損失を報告している。それぞれ5,000～10,000アカウント 単一の執行措置において、農場とともに主要な口座も対象とされた。その調査結果は、調査結果としてではなく、第一者による報告としてここに記録されています。 この項目には、公表されたサンプルサイズも、固定の収集日も、アカウントごとの検証も存在せず、このページ上の他の数値もこれに依存していません。セクション02にある、この項目に基づいている2行については、その旨が明記されています。\n\nこれが「省略」ではなく「明記」されているのには、2つの理由がある。上記のチェーン・バン・メカニズムこそが、まさにそのパターンに対する公式な説明である。 また、規制当局は、この問題を解決する唯一の記録――自動化の対象となったアカウントがいくつあり、どの段階で行われ、各アカウントが閉鎖されるまでに店舗でいくら消費していたか――をValveから強制的に開示させることができます。その記録が存在するまでは、その数値は現状のまま――報告され、帰属され、証明されていない――状態にとどまります。\n\n07 — 非対称性\n同じ机の両側\n\nその立証基準を、同組織が自らの支援活動に適用している基準 Valve と照らし合わせてみてください。右側の欄は、この資料に収録されている事件記録そのものであり、そこに記載されている留保事項を含めて転載したものです。\n\n取引を行う顧客\n\n2020年～2026年の間に報告された8例\n\n行動\nサードパーティのマーケットプレイスでの商品の売買。あるケースでは、行為そのものは一切なく、アカウントが乗っ取られていた。\n提示された証拠\nなし。「取引状況、コミュニティからの報告、その他の要因に基づいて。」\nお知らせ\nなし。Valve § 4.D で次のように留保している：「Valveは、契約を解除する前に、あなたに通知を行う義務を負いません。」\n上訴\n「このロックは永続的なものであり、Steam サポートではこれ以上の対応はできません。」\nチケット\n最初の返信で解決済み。それ以降の依頼については「返信がない場合は、この件は終了となる場合があります。」\nリーチ\nプロフィール、友達リスト、チャット、マーケット、インベントリ、そしてリアルマネーで購入したすべてのアイテム。\n所要時間\n恒久的なもの。\n大量処理向けの自動ボット群\n\n694,673 91体のボットにまたがる公開在庫の完全セット\n\n行動\n数千のアカウントで自動ヘッドレススクリプトを同時に実行し、カードをアイドル状態にし、バッジを一括作成し、産業規模でセットを取引する。\n提示された証拠\n一般に公開されているボットディレクトリ（steam.supply、SteamLvlUp）や、数百万人のメンバーを擁する公開グループ。\nお知らせ\n一切の介入なし。88.97% いかなる種類の禁止事項も課されていない; 残りの禁止措置のうち、99.8%は表面的なものに過ぎない。\n上訴\n必要ありません。艦隊は、数年にわたるライフサイクルを通じて、中断することなく継続的に運用されます。\nチケット\n—\nリーチ\n在庫の制限のない交換、バッジのレベルアップ、および市場の流動性。\nValveへの利益\n$26.8M+ 店舗での最低購入額（アカウントごとに$5.00のエントリーゲート）に加え、コミュニティマーケットでの取引が15%件削減されます。\n率直に言えば、ここから浮かび上がる疑問は、\n\nカードやアイテムを手動で取引する個人ユーザーは、第4条C項（自動化）または第2条G項（商業利用）に基づき、恒久的かつ異議申し立て不可の利用停止処分を受けることになります。一方、数千ものアカウントでヘッドレスボットを稼働させる自動化されたファーミング・フリートは、88.97%という無違反率を誇り、公然と活動しています。Valveは、その両方の受益者である。\n\nこの不均衡は経済的なものである。個人トレーダーはプラットフォームから価値を引き出す一方で、自動化されたカード群はValveの店舗利用ゲート（アカウントあたり$5.00）に数百万を注ぎ込み、再販売のたびに取引手数料を生み出している。取り締まりは、書面化された規則に従うのではなく、収益モデルに従って行われている。\n\n08 — ガバナンス\nカード経済を管理しているのは誰か\n\nこの報告書で繰り返し指摘されている事実――すなわち、Steamを取り巻くサードパーティ層の人員はSteamの内部から構成されている――は、カード経済においても当てはまり、それはある特定の結論に至ります。 Valveの執行活動が実際にどのような効果をもたらしているかを、独立した第三者が把握することはできない。なぜなら、それを把握できる当事者は、そのレイヤー内部に位置しているからだ。以下の事実はすべて、2026-09-22上のValve自身の公開グループおよびプロフィールページから読み取られたものであり、ブラウザさえあれば誰でも再現可能である。\n\nある「Valve」の従業員が、最大のカード交換グループのモデレーターを務めているValve名の従業員\n\nCardTrades ↗ そのヘッダー内で、自身を次のように説明している。「Steam カード交換公式グループ」 そして、以下を扱っています97,114 メンバー. そのグループのモデレーターとして登録されているアカウント（つまり、そのグループの管理権限を持つアカウント）は、ミックメイン,SgtFopper そしてafarnsworth ↗.\n\nその最後のプロフィールは、Valve自身のサイトのマークアップによってValveの従業員としてマークされています――そのページにはclass=\"profile_header_valve_employee\" — その位置を次のように示しているワシントン州ベルビュー、そして～に属するValve,Steam そしてSteam トレーディングカード・グループ グループ。SteamID64 76561197960434622、2003年9月12日より会員。\n\nこの指摘は個人的なものではなく、構造的なものであり、それはではない 重要な点として――カード交換グループのモデレーターはボットを運用しておらず、ここにはそのことを示唆する要素は一切ない。重要なのは、第07節. Steam 「Card Exchange」はサードパーティが提供する商用カードサービスであり、サードパーティのサービスを通じてカードを取引することは、Valveが一般アカウントを永久に凍結する対象となるまさにその行為です。「取引状況、コミュニティからの報告、その他の要因に基づき、商業目的で使用される。」 ある従業員が、9万7千人のメンバーを擁するそのサービスの公式コミュニティグループにおいて、モデレーターとして登録されています。\n\nここでは、いかなる個人に対しても不正行為の申し立ては行われていません、そしてその役割が具体的に何を意味するかについては一切推論されていない。この非対称性こそが結論である： 通常のアカウントが第三者のカードやスキンサービスに関与した場合、その回答はチケットのクローズと恒久的なロックであり、証拠は提示されない。一方、そのサービスが本件である場合、Valveの従業員がモデレーターリストに名を連ねており、その取り決めはValveが自ら公開しているページ上で確認できる。 求められているのは、この資料の他の箇所で一貫して求められていることと同じである。すなわち、書面による承認が存在するのであればそれを提示すること――そして、もし承認が不要であるならば、その旨を書面で明記することである。なぜなら、セクション06の8名にはその反対の説明がなされていたからである。\n\n禁止リストの層、およびそれを管理する者ボランティアのモデレーターサードパーティのサービス\n\nSteambans.comのグループ（アーカイブ） ↗ (ライブ ↗ アーカイブ済み 2025-12-03 ↗) は、保存されている分類群の説明文にその系統を記載している：「Steambans.com Steam の公式コミュニティグループ。SteamBans.com は、古くからのコンセプトに基づいたまったく新しいサービスです。 VALVe社の旧WONIDプログラムでは、長年にわたりグローバルな禁止リストが運用されてきました。STEAMIDへの移行に伴い、この新しいシステムに特化したサービスを開発するのは自然な流れでした。しかし、私たちはさらに一歩進めたかったのです。 *. 2013年にサービスを終了したSteambansのアーカイブページ。」 その登録管理者には、以下の者が含まれる。devicenull そしてkillahinstinct_ ↗.\n\nその管理者アカウントはではない a Valve 従業員 — 従業員フラグは設定されていません。これは、並外れて高い地位にあるボランティアであり、すなわちコミュニティ・モデレーター （メンバー414名、グループと説明されている）「Steamのコミュニティモデレーターによる作成」), のWikiコーディネーター, のSteam コミュニティ・マーケット、および以下の「Valve」プログラムおよび先行公開グループを含むValve パイプライン,Steam クライアントベータ版,モバイル認証ベータ版,新機能 Steam コミュニティベータ版,Steam ラボ,Steamworks そして詐欺URLを報告する.SteamID64 76561197960794555.\n\nまた、そのサークル内に所属し、自身の公開グループ名簿にSteambansを直接表示しているユーザー：msart ↗ (グループ名簿 ↗),SteamID64 76561197977933359, そのプロフィールには次のように記載されている「私はsteamid.ukをはじめ、Steam関連やそれ以外の多くのサイトを運営しています」、そして16のグループからなる連携ネットワークを運営している――SteamIDcouk （プライマリグループ「Sid website」）、SidAdmins,SidBans,steamideu,Steam3ID,s-id そしてSArchive その中には。\n\nsteamid.uk は、その数字そのものを名称として採用しています。同サイトのFAQには次のように記載されています：「SteamIDは誰が作成したのでしょうか？ SteamIDのウェブサイト、ネットワークインフラ、およびセキュリティシステムはすべて76561197977933359によって管理されています。」 その少し下にある2つの回答には、データの出所が記載されています：「SteamIDは、データ収集に主にSteam Web APIを利用しています。」 同ページでは、異なるホストにまたがる複数の専用サーバー、オフサイトでの開発・ストレージ・全文検索サーバー、および独立したバックアップ施設について説明されています。\n\nインターネット・アーカイブの保存記録により確認済み：その2025年12月3日時点のSteambansグループの概要 ↗, その2024年9月14日時点のオペレータープロファイルの概要 ↗、そしてsteamid.uk FAQ（2026年4月1日時点のスナップショット） ↗, 2026-09-22から直接読み込まれたデータと一致する。\n\nこれらを総合すると、何が言えるのか、そして何が言えないのか\n\n禁止リスト、SteamIDの解決、カード取引――これら3つのサービスが、誰が信頼できるか、誰が特定可能か、そしてアイテムの価値はどれくらいかを決定づけています。これら3つのサービスのいずれも、Valveによって運営されているものではありません。それぞれの機体において、操縦を担当していたのは、Valveの軌道内から来た人々だった： カードサービスの公式グループのモデレーターリストに登録されている、フラグが立てられたValveの従業員；プレリリース版へのアクセス権を持ち、禁止リストグループを管理している、長年のValveのコミュニティモデレーター；同じサークルに属するある個人が運営するID照合サービス。 3つのサービス、3つの管理画面、そしてすでにValve人が権限を付与していた3人。\n\nグループへの所属は雇用関係ではありません。また、これらはすべて非難ではありません。 これはガバナンス上の事実であり、それが一般的な反論の根拠となっている――それらは第三者であり、当社ではそれらを管理することはできません — 受け入れるのではなく、検証されなければならない。指揮を執る者たちにとって、Valveは決して見知らぬ存在ではない。Valveは、彼らに何を求めたのか（もし求めたとすれば）、それを語る立場にあるが、外部の人間にはそれを知る術はない。\n\n誰も数えていない。それが調査結果だ。\n\nSteam ID空間は、連続した整数の範囲です。これを順に調べ、停止処分を受けたアカウントの数、利用制限を受けたアカウントの数、取引停止措置の対象となっている在庫の量を報告すること自体は、研究プログラムではありません。それは単なるループ処理とAPIキーに過ぎません。Valveは、そのキー自体を以下で配布しています。steamcommunity.com/dev/apikey. それにもかかわらずその国勢調査を公表している独立した機関は存在しない。 規制当局でも、ジャーナリストでも、学者でも、消費者団体でもない。Steamにおける取り締まりの規模について公表されている唯一の数値は、Valveが言及することを選んだものだけである。\n\nその機能がないわけではない。単に保留されているのだ。ID空間を大規模に解決・インデックス化するサービス「steamid.uk」は、自社のFAQの中で次のように述べている。「データ収集には主に Steam Web API を利用している」 そして、複数の専用サーバー、オフサイトのストレージ、テキスト検索用マシン、および独立したバックアップ施設で運用されています。 このシステムは、ある個人によって運営されています。彼の「禁止リスト」兄弟グループは、Valveのコミュニティモデレーターとして長年活動し、Valveのプレリリースプログラムへのアクセス権を持つ人物によって共同管理されています。集計結果を公表できる立場にある唯一の団体は、Valveの勢力圏内にあり、それを公表していない。\n\nこれは、報告書が他のあらゆる場所で指摘しているのと同じ構造です。Steam経済において、誰が信頼できるか、誰が特定可能か、ある品物の価値はいくらか、誰が利用禁止かといった、経済の基盤に関わる決定を行うあらゆるサービスは、名目上は第三者ですが、実質的にはValveに隣接しています。Steam 「カード交換」もそのパターンから例外ではなく、その一例にすぎない。 これらが独立した操作であるという主張がValveに対して成り立つのは、まさに、これまで誰もそれをある数に対して検証することができなかったからに他ならない。\n\n1,088万アカウントの調査：88.97% 未調査\n\nArchiSteamFarmのインストールベースは、Valve全体で監査が行われました。GetPlayerBans エンドポイント（アカウント数 0、55 分）。制限のない部分集合のみでも、$26.8M+ 店舗での最低購入額（$5.00 エントリー基準額）。9,680,599アカウント（88.97%）には、いかなる種類の利用制限も課されていません、また、残りの99.8%については、自動取引を継続できる形での、名目上のコミュニティ利用停止処分にとどまっている。\n\n5,360,499制限のないASFメンバー（Steamの表示件数）\n10,880,610スキャンされたAPIエントリの総数（制限あり＋制限なし）\n9,680,599一度もBANされたことがない (88.97%)\n1,200,011「Steam」の禁止事項（11.0%） — 99.8% 外観上の変更\n55分全人口を調査するには、重要な要素の一つとして\n科学捜査の証拠と詳細な調査\n\n詳細な人口統計の内訳（禁止措置の種類別の分布図、措置実施時点でのアカウント開設期間、開設年ごとのグループ分け（2020年～2026年）、および自己申告による地域別データなど）は、専用の調査報告書に掲載されています。\n\n「1,088万件の禁止措置に関する全データ」（別紙VI）を開く →第4節 — アセットIDの非表示 →\n\nそこで問うべき質問は、これであり、これに答えられるのはValveだけである：どの識別子または権限が取り消されたのか、その日付はいつか、誰の決定によるものか、そしてそれが対象となった事業者に対してどのような測定可能な影響をもたらしたのか — それに対し、外で集計を試みていたすべての人々に与えた影響も考慮しなければならない。独立した監査を終わらせるような変更は、たとえ安全対策として発表されたからといって、中立的なものにはならない。それが、上の段落で述べた国勢調査が存在しない理由である。\n\n09 — 方法と限界\n何が読み上げられたか、そして何が主張されていないか\n\nこのページに掲載されている引用文はすべて、2026-09-22上のライブソースから引用し、一字一句そのまま転載したものです。ここに掲載されている内容は、スクレイピングやマーケットプレイスの認証情報、あるいは非公開のデータセットから取得されたものではありません。\n\n4つのデータセットと、それらを用いた演算\n\nこれらはそれぞれ、ターミナルから再現可能な単一のパブリックリクエストです。アカウントは使用されておらず、マーケットプレイスへのログインも行われておらず、認証情報を必要とするエンドポイントも呼び出されていません。\n\nデータセット\tその由来\tそこから何が算出されたのか\nカード調査\n13,876試合\tSteam Card Exchangeが公開しているバッジの価格表。これは、同社の一般向け価格ページ ↗ アーカイブ済み 2026-08-04 ↗\tカードを発行するゲーム、1セットあたりのカード枚数、カードの種類数、および各完成セットの市場価格。中央値と「0」の合計値が、本調査における算術的な集計結果である。\nゲームの価格\n13,713 解決済み\tValve独自のパブリックストアエンドポイント、store.steampowered.com/api/appdetails,cc=us、価格フィールドのみ、バッチ処理で\tカードゲームの定価の中央値と分布、および完成セットの販売数がゲーム本体よりも多いゲームの件数。\nボット株\n91個のボット、694,673セット\t公開されているカードボットのディレクトリはsteam.supply/CardBots ↗, 表示された通りに読み、ログイン不要\t在庫にあるセットの総数、最低カード枚数、ドロップ許容下限、および個別のアカウントごとのボットごとのピジョンホール下限。\n照合\n21個の共有ボット\tsteamlvlup.net/cardbots ↗ アーカイブ済み 2026-02-10 ↗、同じボットを掲載した独立系ディレクトリ\t確認のみ。両方のリストに掲載されている21のボットについて、アグリゲート・ストックは以下に同意する。0.03%; 単一のボットによる最大の不一致は 1.36% であり、これは数分間隔で実施された2回の在庫情報収集の結果と一致している。\n\n2番目のディレクトリで指定されている通り、出典は以下の通りです：データ提供元SteamLvlUp, 以下のライセンスに基づき提供されていますCC BY 4.0 アーカイブ済み 2026-09-23 ↗; ここでは、第三者の在庫数値に対する独立した検証としてのみ使用されており、ボットごとの行をそのまま転載するのではなく、集計して比較するという点で修正が加えられている。Steam 「Card Exchange」および「steam.supply」については、上記でリンクを掲載して出典を明記している。 ゲームの価格はValveによるものです。カード、ゲーム、セットの名称および画像はValveまたは各出版社に帰属し、市場に関する事実として、いかなる権利主張やライセンスにも基づかずに転載されています。\n\n予定されていた2つの測定は実施されず、代替値も設定されていません。Steam独自のコミュニティ・マーケットのエンドポイント —価格概要,検索／表示,価格履歴 — 収集元のホストには何も返さず、Steam コミュニティのディスカッションページは収集元のホストに対してHTTP 403を返すため、このページに掲載されている数値はいずれも実際のマーケットデータに基づくものではありません。毎日のリセット時にカードのドロップ数をカウントするはずだった販売数量の測定方法では、ログイン済みのSteam セッションが必要です；今回の調査報告書には、マーケットプレイスの認証情報は一切使用されなかったと記載されており、その記述はそのまま維持された。 ボット・ストックのフロアとは、ボットを使わずに測定できる範囲のことです。\n\n一次資料\n\nSteam 利用規約 ↗ アーカイブ済み 2026-09-24 ↗ — § 2.A、§ 2.G、§ 3.D、§ 4.C、§ 4.D。\nSteam サポート — 制限付きユーザーアカウント ↗ — $5.00 の閾値および制限機能リスト。\nValve — Steam トレーディングカードに関するよくある質問 ↗ — ドロップシステムと、$9の基本プレイ無料率。\nArchiSteamFarm よくある質問 ↗ そしてディスカッション #3440 ↗.\nSteam コミュニティグループおよびプロフィールページについては、セクション08を直接参照してください。\nsteamid.uk FAQ、インターネットアーカイブのスナップショット 2026-04-01 ↗.\n8 Steam 2020年から2026年にかけて、受領者によって公開されたサポートロック通知。セクション06にリンクとともに一覧が掲載されています。\n\n主張されていない事項\n\nカードファーミングによる「Valve」の収益額は推定されていません。どのツールについても、アクティブアカウント数は明示されておらず、139万のドロップ許容量はではない 農場が所有するアカウントの数 — セクション02の注記を参照のこと。いかなる個人も不正行為で告発されているわけではない。人物名が挙げられている場合は、その人物自身の公開Steamハンドル名であり、その人物自身の公的な役割において、Valveが公開しているページからの情報である。 セクション06に記載された8つのロックされたアカウントについて、無実であるとか有罪であるとかは一切主張されていません。この調査結果は当該アカウントではなく、その投稿内容に関するものです。セクション02に記載されたオペレーター損失の数値は、当事者による報告であり、その旨が調達に関する注記. steamid.ukのFAQは、ライブページがボット対策の認証を必要としているため、インターネットアーカイブのスナップショットから引用したものです。バンに関する調査が行われ、その結果が隠蔽されたという主張は一切行っていません。単に、そのような調査結果が公表されていないという事実を指摘しているに過ぎません。667を超える「Steam」レベルの曲線は、モデル化されていません。\n\nなぜそのツールが主題ではないのか\n\nArchiSteamFarmでは、次のように述べられている。「Valveによって承認されていない」 そして、このページでは、それに対して何の非難もなされていない。 それが測定基準として用いられるのは、この経済圏において、その仕組みを公に、かつ文書で記録している唯一の主体だからです。Valveは、たった1つの段落でこの議論全体を締めくくることができます。すなわち、どの商用自動化を承認しているかを公表し、残りの部分について各オペレーターがどのような対応をとったかを記録すればよいのです。\n\n次の記事：市場そのものの価格形成の仕組み → ・価格帯と掲載上限 → ・商品 Steam は取り扱いません →",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "ボットファームは、Valveの店にある漏れではありません。それは顧客."
          },
          {
            "level": 2,
            "id": null,
            "text": "農場とは実際にどのようなものなのか、順を追って解説"
          },
          {
            "level": 3,
            "id": null,
            "text": "買い注文"
          },
          {
            "level": 3,
            "id": null,
            "text": "ゲームを購入する"
          },
          {
            "level": 3,
            "id": null,
            "text": "アイドル\nこのツールは、そのアカウントをSteamネットワークにヘッドレスでログインさせ、「バッジを解析します」, プレイ可能なタイトルのリストを作成し、開始します「対象となるゲームをプレイし、そのゲームのコンテンツがすでにすべて周回済みかどうかを定期的に確認する。」 そのメカニズムについて、メンテナが次のように説明しています：それは「Steamに、私たちが特定のゲームをプレイしていることを伝える以外に、何もしていない。」"
          },
          {
            "level": 3,
            "id": null,
            "text": "ドロップがなくなる\n各タイトルは有限である。「どのゲームにも、カードドロップの数は決まっています。それらをすべて集めてしまうと（フルセットの約半分）、そのゲームはもはやファームの対象とはなりません。」 生産を続けたい農場は、タイトルを買い続けなければならない。カードの供給量は、購入によって制限されている――これは設計上の仕様であり、Valveにとって有利な仕組みとなっている。"
          },
          {
            "level": 3,
            "id": null,
            "text": "出金\nカードは、3つの方法のうちいずれかによって手元を離れます。すなわち、コミュニティマーケットでの売却、トレード、あるいは宝石への加工です。いずれもサブスクリプション・マーケットプレイスでの取引またはトレードに該当し、§ 3.D ではその手数料について次のように規定しています：「Valveは、サブスクリプション・マーケットプレイスにおける取引に対して手数料を徴収する場合があります。」 このステップこそが、全体を違反とする要因となる――参照：05."
          },
          {
            "level": 2,
            "id": null,
            "text": "農場が1セントの収益を上げる前に、すでにValveを支払っている。"
          },
          {
            "level": 3,
            "id": null,
            "text": "購入するものが実際にどれくらいの大きさなのか"
          },
          {
            "level": 3,
            "id": null,
            "text": "その集合はどのくらいの大きさか"
          },
          {
            "level": 3,
            "id": null,
            "text": "ライセンスの費用"
          },
          {
            "level": 3,
            "id": null,
            "text": "完成したセットが返すもの"
          },
          {
            "level": 3,
            "id": null,
            "text": "「694,673」のセットが置かれている場所"
          },
          {
            "level": 3,
            "id": null,
            "text": "この床が伝えていること、そして伝えていないこと"
          },
          {
            "level": 3,
            "id": null,
            "text": "それに、Valveの価格では、農業は採算が取れない"
          },
          {
            "level": 3,
            "id": null,
            "text": "農場が実際に支えているもの"
          },
          {
            "level": 4,
            "id": null,
            "text": "ゲームの売上"
          },
          {
            "level": 4,
            "id": null,
            "text": "「オンライン」と遊びの時間"
          },
          {
            "level": 4,
            "id": null,
            "text": "登録"
          },
          {
            "level": 4,
            "id": null,
            "text": "財布の中身と手数料"
          },
          {
            "level": 4,
            "id": null,
            "text": "SteamレベルのPR"
          },
          {
            "level": 3,
            "id": null,
            "text": "そして、キャッシュアウトそのものが価値の流出源となる――税金が二重に課されるからだ"
          },
          {
            "level": 3,
            "id": null,
            "text": "これは単なる一過性の現象ではありません。長年にわたる基盤を持つ産業なのです。"
          },
          {
            "level": 3,
            "id": null,
            "text": "パブリックボットディレクトリに保存されている完全なカードセット（販売数：Steam）"
          },
          {
            "level": 3,
            "id": null,
            "text": "トップから見た、あるセールスのバッジラダーの様子"
          },
          {
            "level": 3,
            "id": null,
            "text": "また、セールが行われていないときでも、同じ船団がそこにいる"
          },
          {
            "level": 3,
            "id": null,
            "text": "ボットごとのデフォルトディレクトリ"
          },
          {
            "level": 2,
            "id": null,
            "text": "もう一つの商品は、お名前の横にある番号です"
          },
          {
            "level": 3,
            "id": null,
            "text": "消費したセット数：レベル 1 ～ 1,000"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valveはそれを公表していないため、その曲線がどのように確認されたのか"
          },
          {
            "level": 2,
            "id": null,
            "text": "この条項は、農業について漠然と記述しているのではなく、具体的に列挙している。"
          },
          {
            "level": 3,
            "id": null,
            "text": "「…遊びの時間」"
          },
          {
            "level": 3,
            "id": null,
            "text": "「…ユーザーからの真摯な意見がなければ」"
          },
          {
            "level": 2,
            "id": null,
            "text": "「ファームされたカード」からのあらゆる退出は、ライセンスで禁止されている退出であり、Valveはその都度、入場料を徴収する"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 2.A — ライセンス"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 2.G — 制限"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 3.D — 手数料"
          },
          {
            "level": 3,
            "id": null,
            "text": "この3つを合わせて読むと、そのポジションは終了します"
          },
          {
            "level": 3,
            "id": "fee-ladder",
            "text": "その入り口の料金は 15% ではありません。ファームされたカードでは、その3分の2に達します。"
          },
          {
            "level": 3,
            "id": null,
            "text": "コミュニティマーケットでの販売における実質手数料（売り手の希望価格に基づく）"
          },
          {
            "level": 2,
            "id": null,
            "text": "予告なしに、波のように次々と、電話番号をたどって広がっていく"
          },
          {
            "level": 3,
            "id": null,
            "text": "事例4 — 2025年6月、VAC アイドル状態のCS2に対する禁止措置"
          },
          {
            "level": 3,
            "id": null,
            "text": "メインアカウントが消滅する仕組み"
          },
          {
            "level": 3,
            "id": null,
            "text": "5年の間隔を置いて、3人の異なるエージェントが書いた同じ段落"
          },
          {
            "level": 3,
            "id": null,
            "text": "調達に関する注記 — オペレーター規模の損失"
          },
          {
            "level": 2,
            "id": null,
            "text": "同じ机の両側"
          },
          {
            "level": 3,
            "id": null,
            "text": "取引を行う顧客"
          },
          {
            "level": 3,
            "id": null,
            "text": "大量処理向けの自動ボット群"
          },
          {
            "level": 3,
            "id": null,
            "text": "率直に言えば、ここから浮かび上がる疑問は、"
          },
          {
            "level": 2,
            "id": null,
            "text": "カード経済を管理しているのは誰か"
          },
          {
            "level": 3,
            "id": null,
            "text": "ある「Valve」の従業員が、最大のカード交換グループのモデレーターを務めているValve名の従業員"
          },
          {
            "level": 3,
            "id": null,
            "text": "禁止リストの層、およびそれを管理する者ボランティアのモデレーター サードパーティのサービス"
          },
          {
            "level": 3,
            "id": null,
            "text": "これらを総合すると、何が言えるのか、そして何が言えないのか"
          },
          {
            "level": 3,
            "id": null,
            "text": "誰も数えていない。それが調査結果だ。"
          },
          {
            "level": 3,
            "id": null,
            "text": "1,088万アカウントの調査：88.97% 未調査"
          },
          {
            "level": 3,
            "id": null,
            "text": "科学捜査の証拠と詳細な調査"
          },
          {
            "level": 2,
            "id": null,
            "text": "何が読み上げられたか、そして何が主張されていないか"
          },
          {
            "level": 3,
            "id": null,
            "text": "4つのデータセットと、それらを用いた演算"
          },
          {
            "level": 3,
            "id": null,
            "text": "一次資料"
          },
          {
            "level": 3,
            "id": null,
            "text": "主張されていない事項"
          },
          {
            "level": 3,
            "id": null,
            "text": "なぜそのツールが主題ではないのか"
          }
        ],
        "links": [
          "https://help.steampowered.com/en/faqs/view/71D3-35C2-AD96-AA3A",
          "https://github.com/JustArchiNET/ArchiSteamFarm/wiki/FAQ",
          "https://steamcommunity.com/tradingcards/faq/",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260924114457/https://store.steampowered.com/subscriber_agreement/",
          "https://steamladder.com/ladder/badges/2861690/",
          "http://web.archive.org/web/20260716205303/https://steamladder.com/ladder/badges/2861690/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/farm-economy-timeline.json",
          "https://store.steampowered.com/charts/",
          "http://web.archive.org/web/20260923183013/https://store.steampowered.com/charts/",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://github.com/JustArchiNET/ArchiSteamFarm/discussions/3440",
          "https://x.com/gergelyszabo94/status/1311004678633795585",
          "https://x.com/prcs25/status/1811893857253982720",
          "http://web.archive.org/web/20240715122902/https://x.com/prcs25/status/1811893857253982720",
          "https://reddit.com/r/steamsupport/comments/1fjmgc5/what_to_do_when_your_steam_account_gets_hacked/mkelm2y/",
          "https://www.reddit.com/r/csgomarketforum/comments/r87owv/psa_my_steam_account_just_got_banned/",
          "http://web.archive.org/web/20250327203008/https://www.reddit.com/r/csgomarketforum/comments/r87owv/psa_my_steam_account_just_got_banned/",
          "https://www.reddit.com/r/GlobalOffensiveTrade/comments/r9xql9/d_recently_received_commercial_ban_for_what_seems/",
          "http://web.archive.org/web/20211206034804/https://www.reddit.com/r/GlobalOffensiveTrade/comments/r9xql9/d_recently_received_commercial_ban_for_what_seems/",
          "https://www.reddit.com/r/csgomarketforum/comments/1hhxx7m/d_permanently_locked_on_steam_for_commercial_use/",
          "http://web.archive.org/web/20250627014045/https://www.reddit.com/r/csgomarketforum/comments/1hhxx7m/d_permanently_locked_on_steam_for_commercial_use/",
          "https://www.reddit.com/r/steamsupport/comments/1hkctwt/permanent_ban_with_no_explanation/",
          "https://www.reddit.com/r/pcgaming/comments/1vf24lu/warning_to_all_gamersexpats_steam_took_my_money/",
          "https://steamcommunity.com/groups/card-trading-card-trades",
          "https://steamcommunity.com/id/afarnsworth",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/groups/steambans",
          "https://steamcommunity.com/groups/steambans",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/id/killahinstinct_",
          "https://web.archive.org/web/20240914124859/https://steamcommunity.com/id/msart",
          "https://steamcommunity.com/id/msart/groups/",
          "http://web.archive.org/web/20260401154714/https://steamid.uk/faq/",
          "https://phishdestroy.io/steam_dossier/ja/enforcement_audit.html",
          "https://phishdestroy.io/steam_dossier/ja/#evidence-blackout",
          "https://www.steamcardexchange.net/index.php?badgeprices",
          "http://web.archive.org/web/20260804200309/https://www.steamcardexchange.net/index.php?badgeprices",
          "https://steam.supply/CardBots",
          "https://steamlvlup.net/cardbots",
          "http://web.archive.org/web/20260210171205/https://steamlvlup.net/cardbots",
          "https://steamlvlup.net/",
          "https://creativecommons.org/licenses/by/4.0/",
          "http://web.archive.org/web/20260923221628/https://creativecommons.org/licenses/by/4.0/",
          "https://phishdestroy.io/steam_dossier/ja/market_economics.html",
          "https://phishdestroy.io/steam_dossier/ja/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/ja/elite_skins.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ja/card_economy.content.json",
      "export_json_sha256": "663d67677bd4acb7c907b78aece77501caa6d2bbec00ef5f554cccf0e73b2ec2"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ja/elite_skins.html",
      "language": "ja",
      "title": "1つの商品、2つの価格体系――『Steam』特集",
      "source_url": "https://phishdestroy.io/steam_dossier/ja/elite_skins",
      "source_html_sha256": "e6093bb4a3ba4342d52b7ab4d4ec0b93c5a0d534d43e53a4ed933cfbc67cb831",
      "exported_at": "2026-09-29T00:22:09.940Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "register",
            "source": "https://phishdestroy.io/steam_dossier/ja/elite_skins#register"
          },
          {
            "id": "",
            "source": "https://phishdestroy.io/steam_dossier/ja/elite_skins#selected"
          }
        ],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "elite_skins.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ja/elite_skins.pdf?v=print-20260929-v5",
        "sha256": "d23e3aa050a54255c45092f490d371a9f3042c252ba27c9575f1a03ecc3cd02f",
        "bytes": 546044,
        "pages": 7
      },
      "integrity": {
        "signed_object": "elite_skins.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "elite_skins.content.json.asc",
        "digest_file": "elite_skins.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify elite_skins.content.json.asc elite_skins.content.json",
          "sha256sum -c elite_skins.content.json.sha256"
        ]
      },
      "content": {
        "text": "別紙IV／市場構造／20 9月 2026\nElite Skins 登録 — $1,800の市場上限\n\n1点。 2つの価格体系。\n\nこのセクションが証明すること\n\nこの登録簿は、5つの外部取引所において、Steamの「1,800」コミュニティマーケットの出品上限額を超える価格設定がなされているすべてのCS2スキンカテゴリーについて、実証的な調査結果をまとめたものです。これにより、248が裏付けたハイティアカテゴリー（18,394のアクティブな出品数と$78.6 millionの掲載流動性を代表するもの）が、100% Valveの公式マーケットプレイスには存在しないことが証明されています。 真の市場価格を求める売り手は、Steamの基盤となる取引メカニズムにのみ依存しつつも、構造的に外部プラットフォームを利用せざるを得ない状況に追い込まれている。\n\n← エグゼクティブ・ブリーフィングに戻る\n\nSteam コミュニティマーケットの出品価格は約1,800.ドルが上限となっています。このスナップショットで価格が確認された5つのサードパーティマーケットプレイス全体では、 419 CS2のアイテムカテゴリには、その上限額を上回る最安の「売出価格」が設定されているものがあり、402のアイテムのうち、95.9%,には「Steam」の掲載が一切ないものもある。 両社合わせて、18,641に掲載された、少なくとも$82.4 million相当の銘柄を保有している。価格が有効となるには、別の取引所による承認が必要であり、 248 これらのカテゴリのすべてが裏付けられている――そして、そのすべてにおいて、100%,はSteamに含まれていない。 「The dearest」はステッカーです | タイタン（ホロ） | カトヴィツェ 2014 $66,285、5.2%の範囲内で4つのマーケットプレイスによって引用されているが、Valveのマーケットプレイスではどこも掲載されていない。完全なランキング、レンダリング画像、および評価は 価格ラダー・アトラス.\n\n「419」のすべてのエントリを確認する ↓アトラスを開く ↗メソッドを読む\n2482つ以上のマーケットプレイスで、価格が上限を上回っているカテゴリー\n18,3945つのマーケットプレイスに掲載されている商品数\n$78.6Mそれらの物件の最低価格\n100%そのうちのいくつかは、Steam から完全に削除されている\n\n訂正・このページには以前、裏付けのない価格が冒頭に記載されていました\n\nこのページの以前のバージョンでは、「Souvenir AK-47 | Point Disarray」という見出しが付けられており、あるマーケットプレイスでは$148,954で販売されていたのに対し、Steamでは$119.で販売されていました。この行は単一の棚に置かれた1点のみに関するものであり、他のマーケットプレイスで同等の価格設定が見当たらないため、これは「価格」ではなく「希望価格」であり、現在このページには掲載されていません。 ここにあるすべての主要な数値は、少なくとも2つのマーケットプレイスが独立して上限価格を上回る価格を設定している「248」カテゴリに限定されています。当該行自体は削除されておらず、以下の登録リストに依然として記載されています。また、その格下げの原因となった格付けについては、 価格ラダー・アトラス.\n\n01 / アクティブな売り注文にある資金\n測定可能なドル下限\n\n5つのマーケットプレイスにわたる、ライセンス供与済みのcs2.shスナップショットから再計算したものです。これは、定義されたサブセットにおける最低の総提示価格であり、売上高でもなければ、CS2経済の評価額でもありません。\n\n248 検証済みカテゴリー · 18,394 掲載済み商品 · 5 マーケットプレイス$78.62M\n\n2つ以上のマーケットプレイスが、Valveが自社のマーケットで許可している上限価格を超えて独自に価格設定しているすべてのCS2アイテムについて、提示されている売り注文の合計額の最低額。\n\nなぜこれが「下限値」であり、「推定値」ではないのか\n\n各マーケットプレイスについて、その 最低 マーケットプレイスに掲載されている部数分、その商品を「売出価格」として提示してください。その棚にある他のすべての商品は、最も低い売出価格と同等かそれ以上の価格に設定されているため、実際の掲載価格はそれよりも高くなります。これは推測によるものではなく、仕組み上当然のことです。これは販売でも、キャッシュフローでも、市場全体の評価額でもありません。また、同じ実物の商品が複数のマーケットプレイスに掲載されている場合もあります。\n\n「419」のすべてのソース行を確認する ↗\n★ スポーツグローブ | ヘッジメイズ（実地テスト済み）\n$4.68M\nAWP | グングニル（新品）\n$4.46M\nAWP | ドラゴン・ロア（新品同然）\n$4.34M\n★ バタフライナイフ | フェード (新品未使用)\n$4.17M\nAK-47 | ワイルド・ロータス（工場出荷時新品）\n$4.16M\n★ バタフライナイフ | ドップラー（新品）\n$3.64M\n\n棒グラフは、最低価格の算出に最も大きく寄与した6つのカテゴリーレベルの内訳を示しており、最大値に対する割合で表示されています。棒の高さは、最も安い売値と出品点数の両方を反映しています。同一の物理的な商品が複数のマーケットプレイスに掲載される可能性があるため、これらの数値を他のマーケットの合計に加算してはなりません。\n\n02 / 確認可能な例\nその制限が除外しているもの\n\n図版は、記載がある限り正確な商品名に対応しています。価格は、記載された日付のカタログに掲載されている現在の売出価格であり、取引実績ではありません。\n\n★ Butterfly Knife | Doppler (Factory New)\n\n出典: https://phishdestroy.io/steam_dossier/ja/elite_skins#selected\n\n測定可能な格差： これらのオファーは、Steamに掲載されている同額の米ドルでの物件では太刀打ちできません。Valve独自の コミュニティマーケットに関するよくある質問 アーカイブ済み 2026-09-21 ↗ 最大掲載価格は約1,800と定められています。売り手はこれより低い価格で掲載することも可能ですが、それが許容されるかどうかは売り手の判断に委ねられています。別の CSMarketCapで$1,800以上の商品を検索 ↗ 28がインデックス化している市場全体における「Factory New Dragon Lore」の表示件数は、約1.1K件の公開オファーとなっています。重複する在庫は複数回カウントされる場合があります。\n\n03 / 構造的依存関係\nSteamのキャップにより、価格発見がSteamの外へ追いやられる\n\nこの比較は構造的なものです。すべての希望価格が適正であると仮定するわけでもなく、未成約の物件を収益として扱うわけでもありません。\n\n01 ・ルール\nSteam リストの上限を設定する\n\nValve によると、コミュニティマーケットの掲載件数には上限があり、その数はおよそ $1,800. ウォレットの残高には上限が設けられており、ウォレット内の資金を現金として引き出すことはできません。\n\n02 ・観察\n『Dragon Lore』：10,940.85\n\n5-のマーケットプレイスカタログには、次のように記載されています。 389 ライブ特典 AWP Dragon Lore（ファクトリーニュー）は、10,940.85ドルから（CSFloatフロア）。より広範な登録には、Steamの制限を超える、248で確認済みのカテゴリーが含まれています。\n\n03 ・その結果\n価格と振替の配分\n\nそのより高い価格を求めている売り手 Steam には投稿できません. 外部サービスは現金価格を設定できますが、配送に関しては、依然としてSteamが管理する商品の所有権および譲渡が適用されます。\n\n政策上の矛盾： Valve独自の 利用規約 アーカイブ済み 2026-09-21 ↗ Steamのサービスの商用利用については、明示的に許可されている場合を除き留保する一方、同社の 2016 声明 アーカイブ済み 2026-09-21 ↗ 同ギャンブル事業者は、すでにSteamのOpenIDや自動生成アカウントを利用していたという。これは、Valveが2016.に存在するこの種の外部事業者について認識していたことを示す直接的な証拠である。にもかかわらず、公式マーケットプレイスでは、こうした高価値アイテムの実際の相場価格を掲載することができない。 それは、Steam における価格形成や取引に対するアーキテクチャ上の依存関係である。 各マーケットプレイスの契約状況については、それぞれ個別の証拠が必要となります。この過剰な取引高を占める2つの主要な欧米のマーケットプレイスは、主要な法域において正式な法人として運営されており―― CSFloat 株式会社 （米国デラウェア州に設立）および Skinport GmbH （ドイツ・シュトゥットガルトに登録、HRB 764879）— Steam の Web API および取引インフラを直接活用し、個人間（P2P）の商品販売において数億規模の取引を公然と行っている。\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\n4つの$100,000の行は、CSFloatの最高出品価格に設定されています。これらは登録簿に明記されており、鑑定価格として解釈してはなりません。アーカイブされたCSFloatの出品データは、約$6,999,までしか収録されていないため、$1,800を超える登録簿の全データについては、公開カタログのスナップショットが使用されています。\n\n04 / もうひとつの『Valve』\n天井もまた、Dotaを捉えている 2\n\nSkinport でも同様に厳格な「最安値比較テスト」を行ったところ、166（CS2カテゴリ）および 3（Dota 2 カテゴリ）が見つかりました。これらは別のマーケットプレイスのスナップショットですので、CSFloatの 245. に追加しないでください。\n\nDOTA 2 · 1 オファー\n英雄的・残忍な三日月\n\nSkinportの最安値についてお尋ねください： $14,622.25.\n\nDOTA 2 · 1 オファー\nダーク・アーティスティー・ケープ\n\nSkinportの最安値についてお尋ねください： $8,255.16.\n\nDOTA 2 · 1 オファー\n堕ちたパワー・スター\n\nSkinportの最安値についてお尋ねください： $2,087.92.\n\nこれらは3つのアイテムカテゴリの一例であり、存在するすべてのDota『2』のアイテムを網羅しているわけではありません。 日付が指定されたSkinportの行を確認する ↗ そして API ドキュメント ↗.\n\n05 / 堅牢性\nこの結果は、上限の具体的な数値には依存しない\n\nValve 上限は購入者の地域通貨で設定されるため、米ドルに換算すると端数のない整数にはなりません。そのため、妥当と思われる各閾値ごとに集計が繰り返されます。Steam に掲載されていないこれらの項目の割合は、95%.を下回ることはありません。\n\n閾値の検証\t商品カテゴリ\t掲載されているコピー\tフロア値\tSteam に掲載されていない\n$1,800\t419\t18,641\t$82,449,526\t95.9%\n$2,000\t382\t15,159\t$75,541,325\t95.5%\n$2,070\t363\t12,336\t$69,560,305\t95.6%\n$2,300\t323\t11,644\t$67,984,432\t95.0%\n$2,500\t299\t10,950\t$66,203,929\t95.0%\n\n1行ずつ読み進めてください。各行は、別々の母集団ではなく、同じ国勢調査の入れ子になった部分集合です。「フロア値」は、各マーケットプレイスの 最低 記載されている部数に基づいて集計するため、その仕組み上、所蔵冊数は実際より少なく表示される。 データセットを開く ↗\n\n06 / 数えられるほどの希少性\n実際に販売されているものは、これらの中でごくわずかだ\n\nBUFFは、各アイテムの棚をフロートブラケットに分割し、各ブラケットに何点あるかを公開しています。これにより、「レア」という言葉が単なる言葉ではなく具体的な数値となり、コンディションとスキンを別々に価格設定できるようになります。\n\n298 掲載されている作品一覧\nAWP | ドラゴンの伝承\n\n8 価格設定された異なるバリエーション。最も高価なものは、 記念品 AWP | ドラゴン・ロア（新品同然）, と尋ねる $12,363 20冊が棚に並んでいます。\n\n棚にある最高のフロートブラケット（0–0.01）には、 2 部数, 尋ねて $17,875 — 状態のみを考慮した場合の、その商品の基本希望価格に、45%が上乗せされた価格。\n\n607 掲載されている作品一覧\nM4A4 | ハウル\n\n12 価格設定された異なるバリエーション。最も高価なものは、 記念品 M4A4 | ハウル（工場出荷時新品）, と尋ねる $14,895 2冊が棚に並んでいます。\n\n213 掲載されている作品一覧\nAK-47 | ワイルド・ロータス\n\n7 価格設定されたさまざまなバリエーション。最も高価なものは、 お土産用 AK-47 | ワイルド・ロータス（工場出荷時新品）, と尋ねる $14,895 2冊が棚に並んでいます。\n\n310 掲載されている作品一覧\nAWP | グングニル\n\n7 価格設定されたさまざまなバリエーション。最も高価なものは、 記念品 AWP | グングニル（使用感ほとんどなし）, と尋ねる $14,895 2冊が棚に並んでいます。\n\n本資料の残りの部分にとって、これがなぜ重要なのか： これらは単なる抽象的な概念ではありません。各トロフィーは世界中の公開棚に数百個ずつ存在しており、それぞれが1つのSteamアカウントに紐付けられ、1つのSteam取引によって移動されています。これほど取引量の少ない市場では、たった1つのインベントリが盗まれただけでも測定可能な出来事となり、本調査の他の部分で記録されているアカウント乗っ取りの手法が、直接的かつ定量化可能な利益をもたらすことになります。\n\n「数」とは、データ取得時点におけるあるマーケットプレイス上のリアルタイムの掲載数であり、現存する総数ではありません。非公開在庫として保有されている商品は、ここでは一切カウントされていません。 フロートデータセットを開く ↗\n\n07 / はしごが見えなくなっている\nその品物が高価であればあるほど、目に見える場所からは遠ざかっていく\n\n以下の各段階は、それぞれ異なる証拠の分類です。これらは意図的に1つの数値に統合されていません。\n\n段\t図\tこれは一体どういう事実なのでしょうか\nCeiling on Valve's own market\t~$1,800\tPublished rule, stated in the Steam Community Market FAQ.\nDearest ask several marketplaces agree on\t$66,285\tMeasured by us in this snapshot. Sticker | Titan (Holo) | Katowice 2014, quoted by four marketplaces within 5.2% of one another. An ask, not a sale.\nDearest ask seen on any single shelf\t$148,954\tOne marketplace, one copy, no second marketplace agreeing — and equal to a round CNY 1,000,000 at the snapshot rate. Listed here as the outer edge of what sellers ask, and relied on for nothing.\nPublic marketplace sale\t$49,999\tSpecialist Gloves | Crimson Kimono (FN) on CSFloat, as reported by SteamAnalyst. Platform-recorded, third-party reported.\nReported private sale\t$400,000\tAK-47 | Case Hardened, reported by PC Gamer in April 2023. Journalism, not a record we hold.\nReported offer, declined\t$1,500,000\tBlue Gem Karambit, pattern #387. No sale took place and the figure has not been independently confirmed. Included to mark the ceiling of the claims, not to assert a value.\n\n構造上のポイント： Valveの市場での取引価格は約$1,800.で止まります。サードパーティのマーケットプレイスでは、取引価格が約$66,000まで上昇し、そこでは複数のマーケットプレイスが価格に合意します。さらに約$150,000まで上昇すると、合意するのは1つのマーケットプレイスのみとなります。 それ以上の価格帯では取引の場が全く存在しない――Valveが発行した資産の最大規模の譲渡は、上場もプラットフォーム上の記録も本人確認も報告もない状態で、個人間の非公開取引として行われている。譲渡そのものは依然としてSteam上で実行される。 値が高ければ高いほど、他者からは見えにくくなり、それを支えるインフラはすべてValveが提供しています。\n\n最後の2つの項目は、出典が明記された他者による報告です。本プロジェクトではこれらを検証しておらず、いかなる結論においてもこれらに依拠していません。\n\n419で観測されたすべてのカテゴリ\n\n出典: https://phishdestroy.io/steam_dossier/ja/elite_skins#register\n\n09 / 由来と限界\n計算を確認してください\n\nローカルデータと公開ソースを公開します。数値の見出しは、取得日時点のCSFloatの範囲に限定されます。\n\nValve独自の制限と条件\n\nSteam コミュニティマーケットのよくある質問 ↗ アーカイブ済み 2026-09-21 ↗ $1,800程度が上限額であると記載されています。この 利用規約 ↗ アーカイブ済み 2026-09-21 ↗ 商用利用に関する制限を定めています。\n\n価格の算出根拠\n\n価格、上場銘柄数、および浮動株数の範囲は、以下の情報に基づいています。 cs2.sh 市場データ API は、有料の商用サブスクリプション契約に基づき、ライセンスキーを使用して利用できます。 いかなるマーケットプレイスからもデータをスクレイピングしておらず、マーケットプレイスのアカウントや認証情報も一切使用していません。 同プロバイダーは、BUFF、Youpin、CSFloat、Skinport、C5Game、およびSteamコミュニティマーケットのデータをまとめており、すべての数値は報告されたままの米ドル建てです。 プロヴェナンス・マニフェストを開く ↗ — 生のスナップショットの正確な終了時点、取得時刻、およびSHA-256ハッシュ値が記録されているため、独自の鍵を持つ第三者が同じデータを取得し、このページに記載されているすべての数値を再計算することが可能です。\n\n入手できなかったもの\n\n購入されたサブスクリプションの対象は、現在のスナップショットのみです。過去のスナップショットやアーカイブのエンドポイントについては利用できませんでした。また、 本ページでは、いかなるトレンド、過去の価格、あるいは経時的な変化についても、いかなる主張も行っていません。 ここにあるものはすべて、日付の記された一瞬の出来事だ。\n\n以前のCSFloatの登録\n\nこの展示の最初のバージョンでは、2008年9月20日（20）付けのCSFloatカタログのスナップショット1件から、245のカテゴリーをカウントしました。2026: そのスナップショットはここに残っています ↗. 今回の登録件数がより多くなっているのは、1つの市場ではなく5つの市場にまたがっているためです。これらは別々の集計結果であり、合算してはなりません。\n\nValveの特定履行に関する声明\n\n『Valve』の「2016」におけるゲーム内アイテム取引に関するアップデート ↗ アーカイブ済み 2026-09-21 ↗ OpenIDや自動生成されたSteamアカウントを利用するギャンブル事業者に対処するものである。これは、すべての外部マーケットプレイスを禁止する措置よりも範囲が狭い。\n\n通訳の境界\n\nこれらは「オファー」であり、「販売」ではありません。市場名ひとつで、フロート、模様、ステッカーの詳細が異なる複数の実物が含まれる場合があります。この登録簿は、市場総額やValveの意図を反映するものではありません。",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Elite Skins 登録 — $1,800の市場上限"
          },
          {
            "level": 2,
            "id": null,
            "text": "測定可能なドル下限"
          },
          {
            "level": 3,
            "id": null,
            "text": "なぜこれが「下限値」であり、「推定値」ではないのか"
          },
          {
            "level": 2,
            "id": null,
            "text": "その制限が除外しているもの"
          },
          {
            "level": 3,
            "id": null,
            "text": "★ Butterfly Knife | Doppler (Factory New)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Steamのキャップにより、価格発見がSteamの外へ追いやられる"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam リストの上限を設定する"
          },
          {
            "level": 3,
            "id": null,
            "text": "『Dragon Lore』：10,940.85"
          },
          {
            "level": 3,
            "id": null,
            "text": "価格と振替の配分"
          },
          {
            "level": 2,
            "id": null,
            "text": "天井もまた、Dotaを捉えている 2"
          },
          {
            "level": 3,
            "id": null,
            "text": "英雄的・残忍な三日月"
          },
          {
            "level": 3,
            "id": null,
            "text": "ダーク・アーティスティー・ケープ"
          },
          {
            "level": 3,
            "id": null,
            "text": "堕ちたパワー・スター"
          },
          {
            "level": 2,
            "id": null,
            "text": "この結果は、上限の具体的な数値には依存しない"
          },
          {
            "level": 2,
            "id": null,
            "text": "実際に販売されているものは、これらの中でごくわずかだ"
          },
          {
            "level": 3,
            "id": null,
            "text": "AWP | ドラゴンの伝承"
          },
          {
            "level": 3,
            "id": null,
            "text": "M4A4 | ハウル"
          },
          {
            "level": 3,
            "id": null,
            "text": "AK-47 | ワイルド・ロータス"
          },
          {
            "level": 3,
            "id": null,
            "text": "AWP | グングニル"
          },
          {
            "level": 2,
            "id": null,
            "text": "その品物が高価であればあるほど、目に見える場所からは遠ざかっていく"
          },
          {
            "level": 2,
            "id": null,
            "text": "419で観測されたすべてのカテゴリ"
          },
          {
            "level": 2,
            "id": null,
            "text": "計算を確認してください"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve独自の制限と条件"
          },
          {
            "level": 3,
            "id": null,
            "text": "価格の算出根拠"
          },
          {
            "level": 3,
            "id": null,
            "text": "入手できなかったもの"
          },
          {
            "level": 3,
            "id": null,
            "text": "以前のCSFloatの登録"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valveの特定履行に関する声明"
          },
          {
            "level": 3,
            "id": null,
            "text": "通訳の境界"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/ja/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/ja/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/ja/skin_atlas.html#grading",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-above-the-ceiling.json",
          "https://phishdestroy.io/steam_dossier/ja/elite_skins#selected",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://csmarketcap.com/search?minPrice=1800&amp;page=1",
          "https://store.steampowered.com/agreement/?l=english",
          "http://web.archive.org/web/20260921022032/https://store.steampowered.com/agreement/?l=english",
          "https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921021947/https://store.steampowered.com/oldnews/22883",
          "https://phishdestroy.io/steam_dossier/ja/#proxy-bypass-explainer",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/skinport-floor-over-cap.json",
          "https://docs.skinport.com/items",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-float-scarcity.json",
          "https://phishdestroy.io/steam_dossier/ja/elite_skins#register",
          "https://cs2.sh/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/csfloat-catalogue.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ja/elite_skins.content.json",
      "export_json_sha256": "8764f03a3feb1dd6870dc84b47f5b511dcf0dee7877435811b5a5a1a6b0620c1"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ja/enforcement_audit.html",
      "language": "ja",
      "title": "国勢調査 Valve は公表されない — Steam ドシエ",
      "source_url": "https://phishdestroy.io/steam_dossier/ja/enforcement_audit",
      "source_html_sha256": "8cfdc0b96c24d604048048977ea41ac84c8e4da49d0a97b79c075d805fa32fa4",
      "exported_at": "2026-09-29T00:22:09.779Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "enforcement_audit.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ja/enforcement_audit.pdf?v=print-20260929-v5",
        "sha256": "79ae3a302fe5be7d174d269c836f3cec338088f8ef7473a660672aa7485e1a34",
        "bytes": 723871,
        "pages": 12
      },
      "integrity": {
        "signed_object": "enforcement_audit.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "enforcement_audit.content.json.asc",
        "digest_file": "enforcement_audit.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify enforcement_audit.content.json.asc enforcement_audit.content.json",
          "sha256sum -c enforcement_audit.content.json.sha256"
        ]
      },
      "content": {
        "text": "別紙VI — 国勢調査 VALVE は公表されない\nSteamのアカウント群はどれほど大きいのか。私たちが数えました。\n\nSteam上で稼働している自動化アカウントの数については、公表された数値はありません。これを秘密にする必要はありません。SteamのID空間は連続した整数の範囲であり、Valveはその範囲を網羅するWeb APIキーを配布しているからです。 そこで、自らを特定している最大規模の集団、すなわち ArchiSteamFarm コミュニティを対象とし、Valve 独自の禁止エンドポイントを通じて、すべてのメンバーを一度読み取りました。 ASFは初回起動時に、ユーザーが明示的にオプトアウトするか、グループ参加の設定のチェックを外さない限り、自動的にSteamグループに参加するため、自己申告が行われるのです（AutoJoinSteamGroup / 統計）。この設定はデフォルトで有効になっているため、グループのメンバーには幅広い層が含まれています。具体的には、複数のアカウントを運用する商業的なボットネットワーク、たまに放置プレイをする愛好家、そして個人アカウントでソフトウェアを実行し、デフォルトのサブスクリプションを一度も解除しなかった一般プレイヤーなどです。そのため、このグループのメンバー数は、ソフトウェアの累積リーチを実態調査として反映したものとなります：10,880,610 アカウント総数（$5.00 店舗のゲートを通過した、5,360,499 確認済みの制限なしメンバーを含む）。 そこで、私たちは唯一重要な質問を投げかけた――Valveは実際に彼らに何をしたのか？\n\nこのページが扱っていない内容。 これは、Valveが1,000万人を排除すべきだという主張でもなければ、カードファーマーに対する不満でもありません。以下に挙げるすべての数字がここにある理由はただ一つです：Valveは 個人を永久に利用停止処分とし、その書面による理由は「Steamの商用利用」および「自動化」である。 これは、同じルールが、同じ行為に対して大規模にどのように適用されるかを測定したものです――その過程で、運営者が「0」のアンロック、ゲームライセンス、およびマーケット手数料「1」を徴収している場合です。ここで明らかになったのは、ファームそのものではなく、その不均衡性です。\n\n1,088万個歩き回る詐欺師たち（53.5k）有料監査（10万）対 無料監査\n10,880,610ASFグループの全メンバーによる、Valve自身のban APIの閲覧数（制限付きと制限なしを合わせた合計）\n88.97%これまで一度もBANされたことがない — 9,680,599のアカウントは現在も有効\n63.06%停止されたアカウントのうち、課金済み（$5+ 支出）のもの — 100,000 SRSWOR スライス（±0.39% 誤差）\n67.77%51,732人の認定詐欺師のうち、詐欺禁止措置を受けていない者はゼロ人である（全数調査）\n01 — スケール\n1,000万のアカウントのうち、10個中9個は手つかずのまま\n\n自らをカウントするある集団は、Valve自身の終点を一度だけ通過する。\n\nなぜ自己集計するのか\nASFがあなたのためにこのグループに参加します\n\n初回実行時 ArchiSteamFarm セット統計 デフォルトでは「true」に設定され、ArchiのSC Farm Steam グループに参加します。オペレーターは、自らオプトアウトする必要があります。したがって、このメンバーシップ数はインストール数の上限ではなく、下限となります。「統計」機能を無効にしたオペレーターは含まれていないため、実際のインストール数は少なくともこの数以上となります。\n\n私たちが読んでいるもの\n10,880,610 登録件数合計\n\nAPIのメンバーリストからは、制限あり・制限なしを合わせて計 10,880,610 個の SteamID64 が返されました。Steam のグループページには 5,360,499 個（制限なしのみ）が表示されています。すべてのエントリは一度ずつISteamUser/GetPlayerBans 2026-09-23。1つのキーで55分間。\n\n答え\n88.97% クリーン\n\n1,200,011には、いかなるSteamの禁止事項も適用されない（11.03%）。その他の9,680,599 記録が一切ない — コミュニティからの追放でもなければ、VACでもなく、何もない。そのアカウントは削除されていない。そのまま稼働し続けている。たった一人を標的にした同じ条項だけで、その人物を永久に追放するには十分だ。\n\n10,880,610件のアカウントのうち、Valveに触れたのはいくつですか\n\nスキャン対象となった全艦隊を、Valveが何らかの禁止措置を適用したかどうかに基づいて分類したものです。赤いスライスは、Valveがこの艦隊に対してこれまでに実施したすべての措置を表しています。\n\n88.97%一度も禁止されたことがない\n11.03%\nいかなる種類の禁止措置もない — 9,680,599 (88.97%)Steamの禁止がいくつかある — 1,200,011 (11.03%)\n10,880,610ASFグループのメンバーがスキャンした\n9,680,599一度もBANされたことがない — 88.97%\n1,200,011禁止措置を適用する — 11.03%\n55分1つのAPIキーで、すべてを集計するには\nこの艦隊が存続するためにすでに支払った代償は Valve である\n\n農場の収益の見積もりではない。Valveの店で既に費やした金額の下限値であり、Valve自身のルールを上記の集計に適用して導き出されたものである。\n\n「10,880,610」の件数は、APIによって返されるASFグループのメンバーリスト全体を対象としています。これには、制限付きアカウントと制限なしアカウントの両方が含まれます。「Steam」自身の制限付きユーザーアカウント このページには、制限付きアカウントでは算入される Steamのグループに所属している（表示されるグループの人数には含まれない）が、そのアカウントは依然として、そのグループのメンバー一覧には表示される可能性がある。制限対象外のサブセット、すなわちSteamの店舗で少なくとも$5.00を費やしたアカウントは、正確には5,360,499 — グループページには「Steam」という数値が表示されますが、これはSteam自身のルールにより、制限付きアカウントが除外されたものです。「$5.00」の下限計算は、その制限のないサブセットにのみ適用されます。\n\n5,360,499制限のない会員\n(Steamの表示されているグループ数)\n×\n$5.00Valve自身の最小値\n制限から抜け出すために\n=\n$26,802,495店舗での支出上限\n非有限部分集合によって\n\nこれは、Valveが艦隊のうち制限対象外の部分からすでに受け取った金額の下限値であり、収益の見積もりでも、利益の主張でもありません。ほとんどのアカウントにおける実際の支出額はこれよりも高く、$5.00という数値は、必要最低限のしきい値に過ぎません。\n\n二次収穫：栽培商品の取引量に対して最大66.7%の手数料。 $26.8Mの入場料に加え、コミュニティマーケットで売却されるすべてのカードおよび商品には、Valveの必須最低手数料（$0.01 Steamの手数料＋$0.01の発行者手数料）が適用されます。 一般的な3セントのカードやジャンクアイテムの場合、Valveは3セントのうち2セントを取り上げる――これは実質的に、Valveに有利な66.67%の削減となる、表向きの15%というマーケティングレートをはるかに上回っている。\n\n人口に関する重要な注意点： グループへの所属は、すべてのアカウントが専用のボットであることを証明するものではなく、またSteam上のすべてのボットを網羅しているわけでもありません。ASFは、起動時にデフォルトでアカウントをコミュニティグループに自動的に登録します。ユーザーが明示的にその設定フラグのチェックを外すか、無効にしない限り（AutoJoinSteamGroup)、常連プレイヤー、たまにしかプレイしないプレイヤー、コミュニティのメンバーが、自動ファーミング艦隊とともに名簿に残っています。さらに、SteamのBANには、公開される理由欄がありません。この結果は、このソフトウェアに関連するユーザー層全体における経験的な割合であり、個々のアカウントに対する個別の判定ではありません。集計済みで、再現可能なデータです：asf-ban-census-2026-09-23.json.\n\n02 — 地理\n艦隊の拠点\n\n凍結されたアカウントのうち、国を明記しているのはわずか8.5%件のみである。国を明記しているアカウントのうち、最も大きな割合を占めているのは米国である。\n\n「Steam」プロファイルには、オプションの国フィールドが含まれています。100,413の禁止アカウントのうち、1,182,811が記入しました — 8.5%。† その少数派の中で、米国が15.5%で首位を占め、次いでウクライナ、中国、ロシアが続き、残りはヨーロッパ、ラテンアメリカ、東南アジアにまたがる長いテールとなっている。 この分野を検証する者は誰もいない。アフガニスタンはトップ10に入っているが、それはおおよそその価値に見合った順位だ。残りの91.5%は割り当てられるというよりは省略されているため、以下に示されるのは、自ら選別された少数派の輪郭に過ぎない――艦隊の分布図でもなければ、どこから運営されているかを示す根拠でもない。\n\n申告された国別の利用停止アカウント数\n\n公共の場所を公開している「100,413」件の禁止アカウントのうち、上位15カ国。割合は、その場所が特定されたサブセットに対するものです。カーソルを合わせると件数が表示されます。\n\n0%\n5%\n10%\n15%\n20%\nUnited States\nUkraine\nChina\nRussia\nCanada\nAustralia\nJapan\nBrazil\nGermany\nAfghanistan\nUnited Kingdom\nRomania\nFrance\nPhilippines\nIndia\n\n読み込まれた場所GetPlayerSummaries 禁止対象のサブセットについて。このフィールドはアカウント所有者によって設定され、誰によっても検証されないため、VPNの出口や冗談で入力された項目も、実際の項目と同様に扱われます。\n\n03 — 鮮度\n最近の案件であり、過去の未処理案件ではない\n\nアカウント作成時期から判断すると、利用停止処分を受けたユーザーは最近のものばかりで、トレーディングカード時代の名残ではない。\n\nもしこれが、徐々に片づけられている過去の混乱であるならば、停止処分を受けたアカウントはトレーディングカードが登場した初期の時代に集中しているはずだ。しかし、実際にはその逆である。作成日が判明している1,132,852の停止処分アカウントのうち、70%は2020年以降に作成されたもので、そのうちのほぼ半数は2023年以降に作成されたものです。 その数は、2017年に作成された「-0」から、ピーク時には227,030 2024年だけで作成されたもの. 彼ら全員が、カードを受け取る前に「$5.00」店の入り口を通り抜けたため、一人ひとりから入場料が徴収された。\n\n禁止されたアカウントが作成されたのはいつですか\n\n作成日が判明している「1,132,852」の禁止ユーザーのアカウント作成年。その範囲は2020年から2026年までであり、2013年から2015年のトレーディングカード時代ではない。ピーク：2024年。マウスオーバーで人数を表示。\n\n0k\n63k\n125k\n188k\n250k\n'13\n'14\n'15\n'16\n'17\n'18\n'19\n'20\n'21\n'22\n'23\n'24\n'25\n'26\n70%2020年以降に作成された凍結アカウントのうち\n227,0302024年（ピーク年）に作成された利用停止アカウント\n51,7012021年の谷は、2つのピークの年の中間に位置しているが、その理由は不明である\n2003年→2026年範囲は存在するが、データは過去6年間のものに限られる\n\n制作年はGetPlayerSummaries SteamID64 によって重複排除された、BAN 対象のサブセットについて。作成日とは、アカウントが作成された日付を指し、BAN された日やファーミングを開始した日ではありません。ここでは、意図を示すものではなく、その集団がどれほど最近のものであるかを示す証拠としてこの日付を参照しています。このグラフには以下の 3 つの点が示されていません：\n\n2024年以降のトレンド。 2025年または2026年に作成されたアカウントは、利用停止処分を受けるまでの期間が短く、2026年は9か月間しか含まれていないため、227,030 → 121,070 → 16,534という推移は、減少ではなく検閲によるものである。\n禁止率。 作成年は凍結アカウントについてのみ読み取られたため、分母が存在しません。インストールベースの増加だけでも、このような傾向が生まれるでしょう。\n2021年が崩壊した理由。 51,701は105,821と104,641の間に位置し、どちらの隣接要素の半分よりも下にあります。これを説明する公開された情報は一切なく、平滑化されることなくそのまま表示されています。\n04 — タイミング\nValveが作用する場合、その作用は最初の1年以内に行われる\n\n「88.97%」が未処理のままになっていることに対する明白な言い訳は、処理遅延だ。しかし、日付の記載された禁止措置は、そうではないことを示している。\n\n利用停止処分が下された時点で、そのアカウントは開設されてからどれくらい経っていたのか\n\n作成日と前回の停止日の両方が記録されている、停止措置を受けた 293,750 アカウントについて、停止措置が適用された時点でのアカウントの開設からの経過期間。その半数以上が、開設から1年以内に停止措置を受けた。\n\n0%\n10%\n20%\n30%\n40%\n<6 mo\n33.7%\n6–12 mo\n21.5%\n1–2 y\n20.6%\n2–5 y\n14.3%\n5 y+\n10.0%\n55.1% inside the first year\n1年以内に利用禁止となった — 55.1%その後、利用停止処分となった — 44.9%\n0.80年利用停止措置が適用された時点でのアカウントの年齢の中央値\n55.1%アカウント開設から1年以内に利用停止処分を受けた\n33.7%最初の6か月以内に利用停止処分となった\n293,750両方の日付が存在するアカウント\n\nこれは、ありふれた反論に対する答えである。もし、執行が単に遅れているだけ――つまり、処理待ちの案件が徐々に処理されているだけ――という理由で、艦隊の 88.97% が手つかずのままであるならば、その禁止措置はdo そのデータは古いものになりがちだ。実際にはその逆で、停止されたアカウントの中央値は生後9ヶ月半、そして3人目――33.7%――は6か月以内に捕まった。Valveがこの集団に作用するとき、その作用は迅速である。依然として逃走中の10人中9人は、列に並んで待っているわけではない。\n\n禁止時の年齢＝作成日からのGetPlayerSummaries から、以下によって示唆される禁止日を引き算して前回の利用停止からの日数, 続きを読む 2026-09-23。これは、両方の値が存在する場合にのみ計算されます：1,200,011の禁止アカウントのうち293,750。 残りのアカウントは「days-since」の値が報告されておらず、省略されています（推測された値ではありません）。したがって、これはすべての停止措置ではなく、日付付きサブセットの構成としてお読みください。\n\n05 — 禁止措置の実際の内容\nValve が動作しても、ボットは停止しません\n\n何らかの禁止措置が適用されている「11%」のうち、どの禁止措置が適用されているかを確認してください。\n\n「禁止」は単なる「禁止」ではありません。1,200,011のアカウントのうち、Valveが報告したものは、99.8% 持ち歩くコミュニティ 禁止 — フォーラム、プロフィール、グループに対する制限だが、トレードボットには何の影響も与えない。そのアカウントは、引き続きカードを受け取り、トレードを行い、インベントリを移動させることができる。 22.2% 少なくとも1つのゲーム利用停止処分と、3.9% VACの利用停止処分を受けていること。カテゴリーは重複しているため、合計は算出されない。実際に取引を遮断する唯一の制裁措置である「経済／取引禁止」が課されているアカウントは5,214件である。 我々は、この数字だけで結論を下しているわけではありません――取引禁止措置は、全体としてSteamの範囲で稀なものです。この図表が示すポイントはもっと単純です。たとえその割合がValveであってもは タッチは取引を続けている。\n\n禁止処分を受けた「11%」たちは、実際にはどのような理由で禁止されたのか\n\n各禁止措置の種類が、スキャンされた全メンバーに占める割合です。1つのアカウントに複数の禁止措置が適用されている場合があります。カーソルを合わせると件数が表示されます。\n\n0%\n4%\n8%\n11%\n15%\nCommunity ban\nGame ban\nVAC ban\nEconomy / trade ban\n\n「Steam」の禁止措置には「理由」欄がないため、これらの禁止措置はいずれも特に「カードファーミング」に起因するものではありません。これは、存在する禁止措置の種類と、各種類が実際に制限している対象を併記したものです。「コミュニティによる禁止」は取引を停止させませんが、「経済／取引禁止」は停止させます。まとめ：asf-ban-census-2026-09-23.json.\n\n06 — もう一つの集団\n詐欺師たち Valve さあ、始めましょう：51,732 完全な国勢調査\n\n2つ目の独立したリスト（コミュニティによって確認された不正行為）は、同じ公式APIに基づいて評価されたものである。\n\n自動化グループについては、無害な怠け者だと片付けてしまうこともできるだろう。しかし、2番目のグループについてはそうはいかない。SteamRepは長年にわたり運用されているコミュニティの評判データベースであり、マークされたアカウントは禁止 そのコミュニティにおいて、被害者の証拠や取引のチャットログが記録されていることから、ある人物が詐欺師であると認定されました。私たちは、すべての対象者について100%の調査を完了しました。51,732 「利用停止」ステータスを持つプロフィール Steamの公式Web APIに対して（ISteamUser/GetPlayerBans/v1) — かつ、詐欺に対処する制裁のみをカウントした。「VAC」の禁止措置は、ゲーム内でのソフトウェアによる不正行為（エイムボット、ウォールハック）を対象とするものであり、トレーダーには何の影響も及ぼさず、詐欺行為が行われたことを示す証拠「Valve」にもならないため、詐欺対策としてカウントされない。\n\n51,732アカウントの全調査対象のうち、67.77% — 35,059の認定詐欺師 — は、Valveから詐欺に関連する利用停止処分を一切受けていない： 彼らは依然として取引ができ、新たな被害者にフレンドリクエストを送り、メッセージを送信することも可能です。コミュニティ利用禁止または取引禁止の処分を受けたのは32.23%のみであり、実際にインベントリの譲渡を遮断する唯一の措置である取引禁止処分が適用されているのは、わずか18.81%（9,731アカウント）にとどまっています。 さらに、12.81%（6,627アカウント）は、ゲーム内でのチート行為のみを理由にVACのゲーム利用禁止処分を受けているが、Steamの取引に関しては一切の制限を受けていない。\n\nValveが詐欺に関連する利用停止処分を適用したかどうかに基づき、詐欺師として確認された者（全件調査）\n\nすべての 51,732 SteamRep-BANNED プロフィールを、Valveがコミュニティ禁止措置または取引禁止措置を適用したかどうかに分けて表示しています。VACおよびゲーム禁止措置は除外されています。これらは不正行為に対処するものではありません。マウスオーバーすると件数が表示されます。\n\n0%\n18%\n35%\n53%\n70%\nNo scam-relevant ban\nCommunity or trade ban\n0%\n6%\n13%\n19%\n25%\nCommunity ban\nTrade / economy ban\nVAC (not fraud)\nGame ban\n51,732SteamRep件の「BANNED」プロフィールを監査 — 100%件の全プロファイル調査\n35,059詐欺に関連する禁止措置を受けていない (67.77%)\n18.81%詐欺を根絶する取引禁止措置を推進する (9,731)\n32.23%このシェア Valve は、コミュニティまたは取引上の禁止措置（16,673）の対象となりました。\n\nSteamRepは、サードパーティが運営する、コミュニティによる評価に基づく評判データベースであり、Valveの判定そのものではありません。そこが重要な点です。つまり、Valve自体の行動と照らし合わせて評価された外部の証拠なのです。 正規のエクスポートデータに含まれる「51,732」の禁止されたプロフィールはすべて、以下と直接照合されました。ISteamUser/GetPlayerBans/v1。「詐欺関連」とは、コミュニティまたは経済・取引に関する利用停止処分を指します。VAC (12.81%) およびゲーム利用停止処分 (3.86%) は、詐欺ではなくチート行為に対処するものであるため、別々に集計されます。監査データセットの全容：steamrep_steam_bans.csv.\n\n2つの集団、1つの発見\n\nこれらは同じ人々でもなければ、同じ行為でもありません。一方は1,000万の自動生成アカウントであり、もう一方は5万3,000人の有罪判決を受けた詐欺師たちです。両者に共通しているのは、結果の様相だけです：農業関連の口座の10件中9件は一度も利用されることがなく、詐欺行為が確認された詐欺師の3分の2以上（67.77%）は、詐欺に対処する制裁措置を一切受けていない。 コミュニティによる利用停止措置 Valve は、取引ではなく、フォーラムやプロフィールへのアクセスを自由に制限するものです。「通報」ボタン、評判データベース、詐欺を阻止する利用停止措置――これらはすべて存在しているものの、十分に活用されていません。 これと並べて、メインの書類にアーカイブされている拒否事例を見てみよう。そこでは、ある企業が単一のアカウントを永久に削除し、その理由として「商用利用」と「自動化」を挙げている――この条項は単なる形式的なものではなく、明確に適用されているのだ。\n\n07 — $5.00 アカウントゲートとアカウント乗っ取り\n「100,000」アカウントの実証的監査：ボットネットは使い捨ての無料アカウントではない\n\n統計的サンプリングの論理と数学的証明：なぜ他の任意の 100,000 を考慮に入れても、まったく同じ結果が得られるのか。\n\nValveが規制当局や消費者保護機関に対して主張してきた主な弁明は、自動化された詐欺やファーミングは、すぐに利用停止処分となる一時的な無料の「使い捨て」アカウントによって行われているというものでした。Valveが公表した規則によれば、アカウントは数量限定 少なくとも$5.00米ドル Steamストアに登録されているため、取引、友達リクエスト、およびAPI機能の利用が制限されています。私たちは、代表的で数学的に厳密なサンプルを用いて収益化の状態をテストすることで、この主張を直接検証しました。100,000 Steam アカウントを凍結しました 当社の1,182,811プロファイル・メタデータ・コーパスから抽出されたものです。\n\nサンプリング手順 (SRSWOR)\n100,000 バイアスのないスライス\n\n出典：N = 1,182,811 個のユニークな禁止済み Steam アカウントを、暗号学的に一様なPRNGを用いた「無置換単純無作為抽出」により抽出した。各アカウントの抽出確率はすべて同一であり、その値はP =n /N ≈ 8.45%、これによりサバイバーバイアスおよび活動バイアスを完全に排除する。\n\n数学的証明\n誤差範囲 < ±0.4%\n\n有限母集団補正（FPC）の式を、ある99% 信頼区間 (Z = 2.576):\nMoE = Z × √[p(1-p)/n] × √[(N-n)/(N-1)] ≈ ±0.39%\n\n再現性\nなぜ「Any 100k」はどれも同じ結果になるのか\n\n誤差の範囲は、信頼度 1 において ±0 の下限で制限されるため、その他の任意の独立した 100,000-アカウントの標本を抽出しても、それが 63.06% ± 0.39% の範囲内に入ることは数学的に保証されている (62.67% から 63.45%)。このサンプルは、118万人の禁止対象者全員を反映している。\n\nこの監査結果は、「使い捨てボット」という弁明を完全に打ち砕くものである。SteamのレガシーXMLプロファイルインターフェースを通じて監査された100,000のアカウントのうち：61,490のアカウント（分類済みアカウントのうち63.06%）は、Steamで少なくとも$5.00を費やした、制限なし（有料）のアカウントです。 ただ36,021 (36.94%) は無料アカウントですが、2,489は設定されていなかったか、非公開でした。\n\n100,000 利用停止アカウント：有料（$5＋ストアでの利用額）対 無料の制限付きステータス\n\n無作為に抽出された禁止アカウント 100,000 件に対する実証的監査。そのうち 63% 件以上が、Valve の有料金融ゲートを通過しています。カーソルを合わせると件数が表示されます。\n\n0%\n16%\n33%\n49%\n65%\nNon-limited (Paid ≥ $5.00)\nLimited (Free < $5.00)\n100,000標本母集団（SRSWOR、N=118万）\n63.06%制限のない有料アカウント（61,490アカウント）\n±0.39%信頼区間における誤差範囲（信頼水準 99%）\n~745,800118万件のBAN対象アカウントから推計された有料アカウント数\n構造的な現実：産業規模での口座清算\n\nなぜ、調査対象となった凍結アカウントのうち63%が、Valveのストアで実際のお金を使った有料アカウントだったのでしょうか？ボットネットの運営者は、使い捨てのアカウントに自腹で数百万も費やすようなことはしません。この比率は、その規模の大きさを浮き彫りにしています。乗っ取られたアカウントおよび不正アクセスを受けたアカウント 生態系内を循環している。\n\nこのスケールは、地下のプラットフォーム、たとえばFSB Market (匿名名称。元の名称はここでは非公開です)（関連する別名は非公開です）などのマーケットプレイスで直接確認できます。550,000 Steam アカウント （ステラーログ、フィッシングのキャプチャ、クレデンシャルスタッフィング）は、いつでも積極的に販売リストに掲載されています（phishdestroy.io/live-intel). このマーケットプレイスは、Valve独自のSteam OpenIDを使用して買い手と売り手の認証を行っており、いずれのFSB Market また関連フォーラム は、Valveのリンクフィルターによってブロックされています。\n\n第06節で規定されているとおり、Valveはこの不正行為を積極的に排除するものではありません：67.77%のコミュニティによって確認された詐欺師のうち、Steamでは詐欺行為による利用停止措置が一切課されていない。、そして自動化システム群の88.97%は、まったく手つかずのまま残されている。これらのアカウントは自由に動き回り、公式APIを通じて認証を行い、エコシステム全体でほぼ完全に野放しの状態で取引を行っている。\n\n科学捜査証拠および執行体制のアーキテクチャ図\n1,088万件のスキャン済みアカウントから、10万件の実証データおよび5万3,500件の確認済み詐欺師へと至るインタラクティブな流れ · リンクをクリックして生の証拠を確認してください\nTier 01 · 1,088万のオートメーション・フリート調査\nSteam上で最大規模を誇る、自らを自動化システムと称する集団が、Valveの公式禁止APIを順次通過した。これは、商用ボット群が88.97%の下で何千万もの参加料を支払いつつ、何の制裁も受けずに稼働していることを証明している。\n9,680,599 88.97% 稼働中・未使用\n自動運転ソフトウェアを実行しているアカウントで、これまでにいかなる種類の利用停止処分も受けたことがないもの。\n国勢調査の生データ（JSON形式）（1.2 KB） ↗セクション01を確認 ↗\n$26,802,495 店舗直接売上高の下限\n最低参加基準である $5.00 を上回る 5,360,499 名の非限定会員から、Valve が集めました。\nカード経済監査 ↗Valve $5 ルールに関するよくある質問 ↗\n1,200,011 11.03% フラグが設定された部分集合\n99.8%では、コミュニティからの利用停止処分のみが適用されます。99.95%のアカウントでは、取引は引き続き可能です。\n禁止措置の種類別内訳 ↗利用禁止DB (60.4 MB) ↓\nティア 02 · 100,000-勘定科目実証的サンプリング監査（N = 1,182,811）\n従来のXMLエンドポイントを通じて評価された代表的なSRSWORスライス。信頼区間99%において、誤差範囲が< ±0.4%であることが数学的に証明されている。禁止されたボットが無料の使い捨てアカウントであるという主張を否定する。\n61,490 (63.06%) 制限なしの有料アカウント（$5以上の利用額）\n停止されたアカウントの 63% 以上が有料取引によるものです。これを推計すると、停止アカウントのプールには約 745,800 の有料アカウント（$3.73M+ の最低基準）が含まれていることになります。\n検索結果（一部）CSV（2.1 MB） ↓10万件のフォレンジック報告書 ↗\n36,021 (36.94%) 無料アカウントの数に制限あり（< $5.00）\nValveの「使い捨てボット」という特徴に該当する禁止されたプロフィールはごく一部でした。2,489のアカウントは設定されていないか、非公開でした。\n10万件のサンプルスライスCSV（8.5 MB） ↓支出分析 MD ↗\n34.67% 対 63.93% プロファイルのサニタイゼーション監査\nValveのアカウントでは、ニックネームを削除してSteamID64の生の形式に戻しましたが、34,673のアカウントでは、カスタム名とアバターは一切変更しませんでした。また、63,928の利用停止アカウントについては、カスタム名とアバターを完全にそのまま残しました。\n衛生管理セクション ↗概要 ロードマップ ↗\n34.59% レガシー 長期未決済勘定（2003年～2019年に作成）\n停止されたアカウントの3分の1以上は、5年から20年以上前に登録されたものであり、これは長期プレイヤーに対する産業規模のアカウント乗っ取りが行われていることを示している。\n年代順 ↗サポートの拒否 ↗\nティア03 · 51,732 SteamRep 確認済みの詐欺師リスト\n被害者のチャットログや取引記録を伴う、コミュニティによって認定された詐欺師の完全な100%リストを、公式のSteam禁止APIと照合したものです。これは、取り締まり体制の根本的な不備を証明しています。\n35,059 (67.77%) 詐欺によるBANゼロ（完全な不処罰）\n確認済みの詐欺師のうち3分の2以上が、Valveからのコミュニティ利用禁止や取引禁止措置を受けていません。取引や被害者の追加を完全に自由に行える状態です。\nSteamRep APIの利用停止 (2.6 MB) ↓SteamRep 監査報告書 ↗\n9,731 (18.81%) 経済／貿易制裁\n在庫の清算を断ち切る唯一の制裁措置。確認済みの詐欺師のうち、5分の1未満にしか見られない。\nSteamRep ソース (2.1 MB) ↓セクション06を確認する ↗\n6,627 (12.81%) 不適切なチート行為による利用停止（VACのみ）\nゲーム内でのエイムボットやウォールハックの使用により利用停止処分を受けた一方で、彼らのSteam取引やフィッシングの能力は依然として100%活発に機能している。\nVAC 無関係性分析 ↗セキュリティの沿革 ↗\nTier 04 · ウィキ改ざん事件および2026年8月のインフラ侵害事件\n証拠資料集には、内部開発者向けドキュメントの改ざん、コミュニティ編集者の活動制限、およびセキュリティ境界の未保護による不具合が記録されている。\n1,200+ 編集者 VDC Wiki の変更履歴\nフィッシングリンクやスパムテンプレートの修正を試みたコミュニティ編集者たちは、自動フィルターによって体系的にブロックされていた一方で、Valveのスタッフは警告を無視していた。\n「ロシア紛争報告書」（127 KB） ↗分類報告書 (66 KB) ↗\n12 TB（認証なし） 2026年8月 アセットリーク (CWE-284)\nValveは、認証のない公開エンドポイント上で、12テラバイト分の内部コードやプロトタイプビルドを数週間にわたり公開していた。\nValve 無能に関する資料 (43 KB) ↗証拠アーカイブ ↗\nCEVAロジスティクスの情報漏洩 2026年8月 顧客の個人情報漏洩\n欧州の「Steam」デッキ購入者の氏名、住所、電話番号が、「Valve」の物流パートナーから流出し、フィッシング攻撃の相次ぐ発生を引き起こした。\nインシデント記録 ↗執行記録 ↗\n\nサンプリングによるアーティファクト：banned_100k_slice.csv (100,000 勘定科目)。監査結果：slice_100k_limited_results.csv. 詳細な分析レポート：BANNED_100K_FORENSIC_ANALYSIS.md.\n\n08 — 方法と限界\nこの記述がどのように解釈されたか、そして何が主張されていないか\n\n3つの一般集団、1つの公開API、厳格な統計的サンプリング。\n\n実行と認証情報\n\nASFの調査では、100,000-アカウント SRSWOR スライスおよび SteamRep クロスチェックは、連合による公開フィッシングおよび詐欺禁止活動の一環として、PhishDestroy 名の参加者が各自の Steam アカウントおよび Web API キーを使用して実行しました。 本報告書の著者は、SteamのWeb APIキーを一切保有しておらず、自ら実地スキャンを行ったこともありません。データの集計、ハッシュ化、検証、および公開は、参加者からの出力データに基づいて行われました。\n\n人口\tその由来\t読み上げられた内容\nASFの会員\n10,880,610\t「ArchiSteamFarm Steam」コミュニティグループの公開メンバー一覧。「Steam」のグループページには、5,360,499人のメンバー（制限のないアカウントのみ）が表示されています。APIによるメンバー一覧では、制限付きアカウントを含めて合計10,880,610件のエントリが返されました。 設定でデフォルトのグループ参加設定を明示的に無効にしない限り、初回実行時にこのグループには自動的に参加されます（AutoJoinSteamGroup / 統計）つまり、メンバーリストには、商用ボットクラスター、個々のカードアイドラー、およびデフォルト設定を有効にしたままにしている一般ゲーマーが含まれています。\tGetPlayerBans すべてのメンバーについて（禁止フラグ）；GetPlayerSummaries 作成日と国について。100件のIDごとにバッチ処理され、SteamID64に基づいて重複排除されています。\n10万件のアカウント停止 SRSWOR スライス\n100,000\t1,182,811の禁止アカウントコーパスから、無作為に、かつ抽出後の補充なしに一様抽出された代表サンプル（$P = 8.45\\%$）。 有限母集団補正を適用すると、99%の信頼水準（$Z = 2.576$）において、誤差範囲は$\\pm 0.39\\%$となる。\t収益化とアカウントの制限状態 (isLimitedAccount) SteamのレガシーXMLプロファイルインターフェースを介して監査される (?xml=1) 分散型プロキシパイプラインを介して。63.06%の有料ステータスを確認。\nSteamRep 詐欺師\n51,732\tSteamRepのコミュニティ評判データベース内で「BANNED」とマークされたすべてのプロフィール（合計51,732件）について、100%の調査を完了しました。サンプリングやフィルタリングは一切行われていません。\tISteamUser/GetPlayerBans/v1 すべての 51,732 アカウントについて、SteamRep のステータスとクロス集計した結果、67.77% が詐欺による利用停止措置を受けていないことが確認された。\n請求の範囲\n\n実証的な割合と、統計的に範囲が限定された推定値のみ。自動化対象集団のうち、88.97%には禁止措置が適用されておらず、禁止措置が適用されたサブセットは最近のものに偏っている（70%は2020年以降）。 100,000アカウントの実証的監査において、禁止されたアカウントのうち63.06%は有料（制限なし）であり、誤差範囲は数学的に証明された±0.4%以内である。 確認された詐欺師 51,732 人のうち、67.77% 人は詐欺に関連する利用停止処分を受けていない。すべての数値は、Valve 独自の Web API から再現可能である。\n\n主張されていない事項\n\n「Steam」の禁止措置には「理由」欄がないため、ここでの禁止措置はいずれも特定の原因によるものではありません。グループへの所属は、そのアカウントが自動ボットであることの証拠にはなりません。ASFでは、手動でチェックを外さない限りデフォルトでグループへの参加が有効になっているため、そのメンバーには、商業目的のマルチアカウントファームと、一般プレイヤーや愛好家の個人アカウントが混在しています。 国は自己申告によるものであり、「SteamRep」の記載はコミュニティによる裁定であり、裁判所の判決ではありません。個人の氏名は記載されていません。\n\nその重要性\n\nValve は同じ API を持ち、その背後には独自のデータベースがあり、このスキャンでは確認できない利用停止理由も保持しています。このクエリを ID 空間全体に対して数秒で実行することができます。 ある数値に対する執行の主張を第三者が検証できる指標は、それを完全な精度で生成できる当事者によって、これまで一度も公表されたことがありません。これは外部による推定値であり、具体的な数値を添えて質問を投げかけることができるように提示されたものです。\n\n次の記事：この集団が運用するカード経済 → ・アクセスの支援と盗難 → ・資料の全文 →",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steamのアカウント群はどれほど大きいのか。私たちが数えました。"
          },
          {
            "level": 2,
            "id": null,
            "text": "1,000万のアカウントのうち、10個中9個は手つかずのまま"
          },
          {
            "level": 3,
            "id": null,
            "text": "ASFがあなたのためにこのグループに参加します"
          },
          {
            "level": 3,
            "id": null,
            "text": "10,880,610 登録件数合計"
          },
          {
            "level": 3,
            "id": null,
            "text": "88.97% クリーン"
          },
          {
            "level": 3,
            "id": null,
            "text": "10,880,610件のアカウントのうち、Valveに触れたのはいくつですか"
          },
          {
            "level": 3,
            "id": null,
            "text": "この艦隊が存続するためにすでに支払った代償は Valve である"
          },
          {
            "level": 2,
            "id": null,
            "text": "艦隊の拠点"
          },
          {
            "level": 3,
            "id": null,
            "text": "申告された国別の利用停止アカウント数"
          },
          {
            "level": 2,
            "id": null,
            "text": "最近の案件であり、過去の未処理案件ではない"
          },
          {
            "level": 3,
            "id": null,
            "text": "禁止されたアカウントが作成されたのはいつですか"
          },
          {
            "level": 2,
            "id": null,
            "text": "Valveが作用する場合、その作用は最初の1年以内に行われる"
          },
          {
            "level": 3,
            "id": null,
            "text": "利用停止処分が下された時点で、そのアカウントは開設されてからどれくらい経っていたのか"
          },
          {
            "level": 2,
            "id": null,
            "text": "Valve が動作しても、ボットは停止しません"
          },
          {
            "level": 3,
            "id": null,
            "text": "禁止処分を受けた「11%」たちは、実際にはどのような理由で禁止されたのか"
          },
          {
            "level": 2,
            "id": null,
            "text": "詐欺師たち Valve さあ、始めましょう：51,732 完全な国勢調査"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valveが詐欺に関連する利用停止処分を適用したかどうかに基づき、詐欺師として確認された者（全件調査）"
          },
          {
            "level": 4,
            "id": null,
            "text": "2つの集団、1つの発見"
          },
          {
            "level": 2,
            "id": null,
            "text": "「100,000」アカウントの実証的監査：ボットネットは使い捨ての無料アカウントではない"
          },
          {
            "level": 3,
            "id": null,
            "text": "100,000 バイアスのないスライス"
          },
          {
            "level": 3,
            "id": null,
            "text": "誤差範囲 < ±0.4%"
          },
          {
            "level": 3,
            "id": null,
            "text": "なぜ「Any 100k」はどれも同じ結果になるのか"
          },
          {
            "level": 3,
            "id": null,
            "text": "100,000 利用停止アカウント：有料（$5＋ストアでの利用額）対 無料の制限付きステータス"
          },
          {
            "level": 3,
            "id": null,
            "text": "構造的な現実：産業規模での口座清算"
          },
          {
            "level": 2,
            "id": null,
            "text": "この記述がどのように解釈されたか、そして何が主張されていないか"
          },
          {
            "level": 3,
            "id": null,
            "text": "請求の範囲"
          },
          {
            "level": 3,
            "id": null,
            "text": "主張されていない事項"
          },
          {
            "level": 3,
            "id": null,
            "text": "その重要性"
          }
        ],
        "links": [
          "https://help.steampowered.com/en/faqs/view/71D3-35C2-AD96-AA3A",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/asf-ban-census-2026-09-23.json",
          "https://phishdestroy.io/steam_dossier/ja/VALVE_EVIDENCE_PACK/databases/steamrep_steam_bans.csv",
          "https://phishdestroy.io/live-intel/?category=steam",
          "https://phishdestroy.io/steam_dossier/ja/card_economy.html",
          "https://phishdestroy.io/steam_dossier/ja/VALVE_EVIDENCE_PACK/databases/banned_archiasf_massive.csv",
          "https://phishdestroy.io/steam_dossier/ja/VALVE_EVIDENCE_PACK/databases/slice_100k_limited_results.csv",
          "https://phishdestroy.io/steam_dossier/ja/VALVE_EVIDENCE_PACK/reports/BANNED_100K_FORENSIC_ANALYSIS.md",
          "https://phishdestroy.io/steam_dossier/ja/VALVE_EVIDENCE_PACK/databases/banned_100k_slice.csv",
          "https://phishdestroy.io/steam_dossier/ja/VALVE_EVIDENCE_PACK/reports/STEAM_BANNED_LIMIT_ANALYSIS.md",
          "https://phishdestroy.io/steam_dossier/ja/VALVE_EVIDENCE_PACK/INVESTIGATION_OVERVIEW.md",
          "https://phishdestroy.io/steam_dossier/ja/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/ja/VALVE_EVIDENCE_PACK/reports/STEAMREP_VS_STEAM_AUDIT.md",
          "https://phishdestroy.io/steam_dossier/ja/VALVE_EVIDENCE_PACK/databases/SteamRep_Profiles_BannedCaution_2024.csv",
          "https://phishdestroy.io/steam_dossier/ja/security_timeline.html",
          "https://phishdestroy.io/steam_dossier/ja/VALVE_EVIDENCE_PACK/reports/russian_conflicts_report.json",
          "https://phishdestroy.io/steam_dossier/ja/VALVE_EVIDENCE_PACK/reports/classification_report.json",
          "https://phishdestroy.io/steam_dossier/ja/VALVE_EVIDENCE_PACK/reports/VALVE_INCOMPETENCE_REPORT.md",
          "https://phishdestroy.io/steam_dossier/ja/steam_evidence_archive.html",
          "https://phishdestroy.io/steam_dossier/ja/steam_enforcement_evidence.html",
          "https://phishdestroy.io/steam_dossier/ja/#insider-threat",
          "https://phishdestroy.io/steam_dossier/ja/"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ja/enforcement_audit.content.json",
      "export_json_sha256": "5ed48b1c3378eee547f14f902e83a235e35fb990b83bad5700477012ab4f312f"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ja/index.html",
      "language": "ja",
      "title": "「Steam」特集：規則、ルート、そして説明責任",
      "source_url": "https://phishdestroy.io/steam_dossier/ja/index",
      "source_html_sha256": "6225457bf2aab0a71d4b23a460cb5a6db050067938a59fb6576c883876ed4555",
      "exported_at": "2026-09-29T00:22:15.144Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "exhibit-gallery-section",
            "source": "https://phishdestroy.io/steam_dossier/ja/index#exhibit-gallery-section"
          }
        ],
        "raster_images_replaced": 2
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "index.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ja/index.pdf?v=print-20260929-v5",
        "sha256": "3654b7d0ac44ca8bee28b8ebd6f0dfeaca82f869422cfa29f9889b3fe38a68bd",
        "bytes": 2428372,
        "pages": 97
      },
      "integrity": {
        "signed_object": "index.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "index.content.json.asc",
        "digest_file": "index.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify index.content.json.asc index.content.json",
          "sha256sum -c index.content.json.sha256"
        ]
      },
      "content": {
        "text": "第1節 — 判例の概要\nルール。記録。未解決の謎。\n文脈と出典に関する制限\n\n6つの調査結果があり、それぞれが日付の明記された公的記録と結びついています。各セクションの構成は次の順序に従っています：技術的記録（パートA）、規則および執行記録（パートB）、法的枠組み（パートC）、そして主要な証拠資料を掲載した付録。\n\n6つの発見。それぞれが、書面による規則と、日付の明記された記録、そしてその証拠によって検証可能な疑問とを結びつけている。\n\n1. 別ドメインの認証ホスト — 44 ルート・26 組の分割ペア\n\n就労登録簿の記録個別の登録可能なドメインを通じて認証を行う44のプラットフォーム.さらに5つのルートが検証待ちの状態にあり、RDAPの日程を待っています。これらが承認されれば、合計は47となります。これらは44のリストおよび年齢表からは除外されています。 —27、ルートごとのエビデンスファイルが公開されているもの さらに、手作業による収集から17件が追加され、別個にリストアップされています。26組のフィルター・スプリットペア メインドメインはブロック済み Steam リンクフィルターには含まれていますが、そのログイン情報を保持しているプロキシは含まれていません。これらはバーナードメインではありません。csgogem.com はブロックされていますが、api.csgem.com、ログインID「Steam」を持つこのホストは、2014年3月から登録されています —12年6ヶ月. Valve は、すべての OpenID リクエストでそのホスト名を受け取り、独自のログインページ上でユーザーにそれを表示します。完全な表、ルートごとの有効期間、およびソース情報は第3節に記載されています。\n\nルートに従ってください →\n2. 2016年：仕組みの名称が決定され、期限が設定された\n\n2016年7月13日、Valveは、ギャンブルサイトがSteamのOpenIDおよび自動取引口座をどのように利用していたかを公表し、2016年7月20日付の同社の弁護士による通知では、10日間の期限が設定されました。 それ以降、事業者ごとの執行記録は公表されていない。その期限から10年が経過した現在も、2026-09-21においてLink Filterによるブロックが返されなかった別ドメインの認証ホスト上で、同じ名称のメカニズムが使用されている。\n\nWSGC宛ての公開書簡を読む →\n3. 機器の照合（弁護士のレターヘッド記載）\n\nここに掲載された書簡の中で、Valveの代理人は、1つのデバイスを複数のアカウントに関連付けるデバイスレベルの相関関係について言及した。これは、Steamのサポートが以前、ユーザーに対して技術的に不可能であると伝えていた機能である。 未解決の疑問は、Valveがどのようなデバイスレベルの記録を保有しているのか、そしてどのような根拠に基づいてアカウント保有者へのアクセスが拒否されているのかという点である。\n\n覚書を読む →\n4. 2つのアクセス対応。1つはデータを開示せず、もう1つはデータを漏洩させた。\n\n2025年10月： Valveの弁護人は、第15条に基づく請求に対し、830ページに及ぶ添付資料を提出したが、その資料では、黒塗りすべき部分がテキストから削除されるのではなく、その上に塗りつぶされていた――902,270文字 標準的な抽出ツールを使って、バーによって隠されていたサードパーティの識別子も含めて再び抽出してしまうことになる。第15条第4項こそが、それらのバーが存在する理由である。2026年9月： チケット番号 HT-2YBP-F7JP-D4VB は、3日後に「アカウントデータ」のセルフサービスページへのリンクが添付された状態でクローズされました。データは一切なく、法的根拠も明示されていませんでした。本記事の公開時点では、第12条第3項に定める1か月の期間が満了しておらず、異議は内容そのものに対するものです。 ・\n\n編集内容の確認を読む →チケットの記録を読む →\n5. Steamの上限を超える市場\n\nSteamは、市場上場の規模を約$1,800。2026年9月23日時点のスナップショットにおける5つのマーケットプレイス全体で、248件のCS2アイテムカテゴリ その上限価格を、そのうち2つ以上が個別に上回っており、かつ、248件すべてが Steam に存在しない; 新品の『Dragon Lore』は$10,941 5つすべてに掲載されている389件の銘柄全体で（第13節の9月20日のスナップショットに基づくCSFloatのみの数値は、62件のオファーにおいて$10,623.95となっている）。 これらの価格で売却するには外部の取引所が必要ですが、アイテムの譲渡は依然として Steam で行われています。\n\n価格の推移を確認し、送金する →\n6. ルールは明示的だが、監査証跡はそうではない\n\n利用規約では、Steamを個人的かつ非営利的な利用に限定し、明示的に許可されている場合を除き商業的利用を禁止し、スクリプトやボットの使用を禁じ、アカウントの停止を認めています。Valveは2016年、この規定をギャンブル事業者にも適用しました。 これとは別に、CSFloatのエンジニアリングアカウントによると、Valveが閉鎖された。IEconItems_730/GetPlayerItems 2017年に、元のアイテムIDへの一般公開を停止しました（変更履歴は見つかりませんでした）。\n\nそのルールをネットワークの横に配置する →\n2016年／書面による請求 10日間\n2016年7月に弁護士がギャンブルサイトに対して送付した通知における期限。WSGCへの公開書簡：第2項。\n2017年 / 公開監査証跡 IDによるアクセスは停止されました\nCSFloatは、元のアイテムIDの喪失を記録します。\n弁護士との書面によるやり取り デバイスの相関関係\n1台の端末から、数十件の不正利用されたアカウントが確認された。\nルート登録簿 ブロックされているが、依然としてログインしている\nルール： Valveの2016年の声明では、Steam OpenID上で賭博事業を運営することを禁じています。記録： リンクフィルターには26のメインドメインが登録されており、それぞれの「Steam」ログイン情報を保持するホストは稼働を続けています。csgogem.comのものは12年6ヶ月間稼働しています。\n第2節 — 公開書簡\nワシントン州賭博委員会への公開書簡\n\n10日間が10年に及んだ。委員会が2016年にValveに対して行った質問に対し、事業者ごとの記録による回答は得られていない。本書簡は、同委員会に対し、この件の再調査を求めるものである。\n\n広報 · ワシントン州ギャンブル委員会\n\n10日間が10年に変わった。レコードを再度開いてください。\n\nワシントン州賭博委員会 殿：\n\n2016年、デビッド・トルヒーヨ委員長は、Valveに対し、ギャンブル目的でのSteamスキンの使用を阻止するためにどのような措置を講じたかを説明するよう求めた。 当時の委員長クリス・スターンズ氏と委員会は、Valveが発行するアイテムやSteamの譲渡を基盤とする業界と対峙した。両名ともその後、委員会の役職を退いている。彼らがValveに投げかけた問いは、未だ解決されていない。\n\nValveの法務担当役員であるカール・クアッケンブッシュ氏は、ギャンブル事業者にSteamアカウントの商業利用を停止するよう、10日間の猶予を与えた。 10月に当委員会へ提出した回答の中で、Valveはギャンブルの助長を否定し、40以上のサイトに対して差し止め通知を送付し、関連するアカウントを無効化したと述べた。また、Steamの取引サービスおよびOpenIDは、顧客やゲーム開発者に利益をもたらすものであるとして、これらのサービスを維持することを擁護した。あれは支配権を主張する行為だった。それに対しては、従順な態度ではなく、検証が必要だ。\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\n我々の評価によれば、Valveの回答は、同社が選択した執行措置が、同社が説明したネットワークの規模に見合ったものであることを示していなかった。事業者への脅迫状は、事業の運営を支えるSteamのアカウント、取引インフラ、認証経路に対する恒久的な遮断とは別物である。報告されている推計によると、CS:GO Loungeだけで、2016年の賭け金総額は$1十億を超えた; これは賭け金の外部推計値であり、Valveの収益ではない。また、同サイトの当初のスキンベッティング事業は後に閉鎖された。その規模の大きさから、検証可能な取り締まりが不可欠となった。\n\n本日、Valveの利用規約 アーカイブ済み 2026-09-21 ↗ 明示的に許可されている場合を除き、商業的利用を制限するとともに、特定の形態の自動化を別途禁止しています。当社の日付入りルート登録簿 OpenIDとして宣言されたレコードは、外部サービスのホストを返す；openid.realm そしてopenid.return_to これらは Steam に送られるフィールドであり、そこから隠される秘密ではない。我々のリンクフィルターのチェック メインアドレスに対して警告が出されたものの、関連するログインホストには警告が出されなかった事例を示しています。フィルタの結果だけでは、Valveがログインを許可したことや、特定のボットがアカウントの利用停止を回避したことを証明することはできません。これは、ホームページ上の警告だけでは、アクセスに関する完全な解決策とはなり得ないことを示している。\n\nまた、有用かつ合法的なSteamの取引機能やOpenID機能が存在したとしても、禁止された事業者が実際に排除されていたかどうかを判断する根拠にはならない。Valve自身の規則では、明示的な例外が認められている。 もしValveがその区別に依拠するのであれば、委員会は、商業的なスキン事業に適用される認可、アカウント管理、および執行基準、ならびに2016年に同社が主張した具体的な非ギャンブル用途を特定するよう求めるべきである。合法的な利用の可能性が単に存在するだけでは、文書化された禁止利用に対する回答にはならない。\n\n当委員会に対し、2016年の案件を再検討し、事業者ごとに詳細な説明を求めるよう要請する。具体的には、10日間の通知後にどのSteamのアカウントおよび取引ボットが無効化されたか、関連アカウントやリターンホストが監視されていたか、その後どの事業者がアクセス権を回復したか、 どのような例外措置が認められたか；および、Valveが委員会に対して行った陳述を裏付ける記録は何か。法律で一般市民の閲覧が認められている記録を公開すること。それらの記録を、現在の経路およびValveによるその後の介入（以下を含む）と比較すること：2018年のOPSkins アーカイブ済み 2026-03-07 ↗.\n\nその通知では、2016年7月に10日間の期限が設けられていた。10年あれば、それが実行されたかどうかを判断するには十分な期間である。 委員会は、Valveの2016年の記録を、今日でも確認可能なインフラと照らし合わせて検証すべきである。\n\n「Steam ドシエ」調査・公式声明、2026年9月20日\n\n2016年 委員会通知 ↗ アーカイブ済み 2026-05-20 ↗ ・Valveによる2016年の回答（文書写し） ↗ ・Valveの2016年OpenIDに関する声明 ↗ アーカイブ済み 2026-09-21 ↗ ・現在の Steam 合意 ↗ アーカイブ済み 2026-09-21 ↗ ・2016年の交流の経緯：第11節 →\n\nパートA — 技術記録・第3節\nサイトはアクセスがブロックされていますが、ログイン用のルートはブロックされていません。\n\n26の主要ドメインがブロックされています。各ドメインの背後にある認証プロキシと、その稼働期間です。 これらの個別の認証ホストは、単なる付随的なセカンダリアドレスというわけではありません。それぞれがSteam用の認証プロキシ、プラットフォームとValveのOpenIDエンドポイントの間に位置し、ブロックされたドメインがもはや公開状態で処理できなくなったログイン情報を担っている。Valveは、Link Filterに「正面玄関」を設置した。サインインは引き続きプロキシを経由して行われていた：csgogem.comはブロックされており、api.csgem.com 2014年3月から登録されています —12年半. それらの日、ホストは毎日、独自のホスト名をValveのOpenIDエンドポイントに送信し、Steamはそれをログインページ上でユーザーにそのまま表示していた。Valve は、これらのルートがすべて通過する幹路であり、それらを検索する必要はありません。 このセクションで測定しているのは、警告の有無ではなく、警告の先にあるルートが何年間開通したままであるかという点です。登録されている44の独立ドメインルートのうち、27ルートについてはルートごとの証拠ファイルが公開されています。詳細は以下の表をご覧ください。まず1つの例を確認し、その後、すべてのルートを測定してください。\n\nWhat this means — the Steam Link Filter\n\nValve’s own blocklist for links leaving Steam. Click a listed address inside the client and an interstitial appears instead of the page. It acts on the link that is posted, not on the login a site performs, and it is the only such check that runs inside the Steam client.\n\nSection 3.1 — why it is the only layer →\n\n図3.1 — 2つのルートを図示したもの。\n\n1つのプラットフォーム、1人のユーザー、同じブラウザから送信される2つのリクエスト。Valveの「リンクフィルター」は、その両方に適用されます。リンクを含むリクエストはブロックし、ログイン情報を含むリクエストは通過させます。このセクションで測定されるすべての値は、下位のルートがオープン状態を維持している時間の合計です。\n\nThe player\none browser, one session\nrollbit.com\nthe platform's main domain\nrbsnin.com\nseparate authentication host\nLINK FILTER\n✕ BLOCKED\nLINK FILTER\n✓ CLEAN\nsteamcommunity.com\nOpenID endpoint · signs in\nno route\nSteamに投稿されたリンク — 停止ログインリクエスト — 許可2026年9月19日および21日付の小切手の控え\n\nどちらのリクエストも Valve には表示されますが、処理されるのはそのうちの1つだけです。 リンクフィルターは Valve のリストであり、Valve のサービスによってチェックされます。 OpenIDリクエストは、認証ホスト自身の名前をValveのエンドポイントに送信し、エンドポイントはそれをそのままログインページに表示します。いずれの場合もリクエストにはホスト名が含まれていますが、違いは、そのホスト名に対して何らかの処理が行われるかどうかです。\n\n1つのプラットフォーム。2つの異なるルート。ROLLBIT / 保存された観測データ\nステップ 5 / 5\n\nリクエストが Steam に到達しました。 観測された経路は、Steamのログインフォームに到達した。著者らはログインを完了しなかった。メインドメインへのリンクをブロックしても、このフォームへの観測された経路は遮断されなかった。\n\n01 リンクフィルターの確認\n目的地rollbit.comこのプラットフォームのメインドメイン\nSTEAM LINK フィルターリンクを確認する独立した目的地警告システム\n保存された結果リンクがブロックされました2026年9月19日および21日\n02 観測されたサインイン経路\nホームにてSteamでログインプラットフォームがOpenIDリクエストを開始します\n別個の認証ホストrbsnin.com保存されたチェックに「リンクフィルター」ブロックがない\nSTEAMログインフォームが表示されましたリクエストされたホストは、Steamの通知に記載されています\n元の採取記録、登録日、およびプロトコルの詳細を確認してください\nValveの執行の実際\nメインドメイン：ブロック済み\nユーザー\n→\nrollbit.com\n(メインドメイン)\n↓\nSTEAM LINK フィルター — ブロック済み\n「リンクがブロックされました！」 — 悪意のある可能性があると報告されました\nrollbit.com では、2026-09-19 および 2026-09-21 に対してリンクフィルターによるブロックが発生しました（認証なしのチェック；生の HTML および SHA-256 が保存されています）。可視化され、監査可能な記録です。\n実際には何が起きているのか — 認証\n認証ホスト：ブロックされていません\nユーザー\n→\nrollbit.com\n「Steamでログイン」\n↓\n別の認証ホストを経由してリダイレクトする：\nrbsnin.comリンクフィルター：CLEAN\n登録済み 2026-09-18T09:34:52Z (Verisign RDAP)\n↓\nSteam ログインページの注意書き (2026-09-20):\n\"Note that rbsnin.com is not affiliated with Steam or Valve\"\nSteam は、受信したリクエストの openid.realm からこの通知を返します。\n↓\nSteam 別のホスト向けに提供されたログインフォーム\n著者らはログインを完了させず、Steamフォームまでの流れが確認された。\nValveは、そのようなリクエストが送信されるたびに、return_to / realmのホスト名を受け取ります。rbsnin.comは、2026-09-21に対してLink Filterによるブロックを返しません。\nご要望に応じて\nOpenIDプロバイダーであるSteamは、認証リクエストごとに認証ホスト名を受け取ります。この情報は、Valve自身のサーバーにopenid.return_to そしてopenid.realm パラメータ。\nサイトから送信されました\n認証ホストはスキャンによって検出されません。プラットフォームは、各リクエストにおいてこれを Steam に送信します。OpenID 2.0 §9.1 に基づきreturn_to 形式上は省略可能ですが、これがなければ Steam はログイン結果を返すことができないため、Steam によるログインを正常に機能させるためには、事実上必須となります。Steam はユーザーに対してホスト名を表示することさえあります（「<host>は、SteamやValveとは一切関係がありません。\"）。\n14歳\nこれは、2026-09-21チェック時点でまだSteam回のログインを保持している最古の認証ホストの経過日数です（dota2.net、登録日2011-10-29）；最も新しいものは3日経過しています（rbsnin.com）。「ブロックされた認証ホスト数：0」という数値を、調査結果そのものとして解釈しないでください。 認証ホストがブロックされると、プラットフォームの「Steamでログイン」機能が完全に機能しなくなるため、正常にログインできた記録から構築された登録情報には、一度もブロックされたことのないホストのみが含まれることになる。 意味を持つ数値はブロック回数ではなく、メインドメインがリンクフィルターに登録されたままだった期間（年数）であり、その間、隣にあるログインは正常に機能し続けていたということです。\n別ドメインの認証ホスト：登録日とメインドメインの比較（30件のルート：2026-09-21のブラウザ監査で解決された25件に加え、2026-09-22に追加された5件）\nプラットフォーム\tリンクフィルター：メイン\t認証ホスト\tリンクフィルター：認証ホスト\t認証ホストが登録されました\t観測源\t証拠ファイル\nRollbit\nrollbit.com · 登録 2014-11-08\n\tブロック済み\n2026-09-19、2026-09-21 ·ウェイバック 2026-09-21\n\trbsnin.com\tCLEAN\n2026-09-21 ·生のHTML （ウェイバックマシンのスナップショットなし）\n\t2026-09-18\n09:34:52Z、Verisign RDAP\n\tSteam ログインページの通知、 2026-09-20\trollbit.com.json\nSkin.Club\nskin.club · 登録 2017-09-04\n\tブロック済み\n2026-09-19、2026-09-21 ·ウェイバック 2026-09-21\n\tsc-auth.net\tCLEAN\n2026-09-21 ·ウェイバック 2026-09-21\n\t2019-04-02\nRDAP\n\tSteam ログインページのお知らせ\tskin.club.json\nHowl.GG\nhowl.gg · 登録 2017-03-16\n\tブロック済み\n2026-09-18、9月19日、9月21日 ·ウェイバック 2026-09-21\n\thowl.uno\tCLEAN\n2026-09-21 ·ウェイバック 2026-09-21\n\t2026-08-11\nRDAP\n\tブラウザのライブキャプチャ + 提供されたOpenID URL\thowl.gg.json\nデュエルビッツ\nduelbits.com · 登録 2020-02-03\n\tブロック済み\n2026-09-21 ·ウェイバック 2026-09-21\n\tswitchflips.com\tCLEAN\n2026-09-21 ·ウェイバック 2026-09-21\n\t2020-04-21\nRDAP\n\t指定された OpenID URL\tduelbits.com.json\nCSGOFast\ncsgofast.com · 登録者数 2015-03-27\n\tブロック済み\n2026-09-19、2026-09-21 ·ウェイバック 2026-09-21\n\tsteam-login.authtofast.com\tCLEAN\nauthtofast.com, 2026-09-21 ·ウェイバック 2026-09-21\n\t2026-06-30\nauthtofast.com、RDAP\n\tブラウザのライブキャプチャ + 提供されたOpenID URL\tcsgofast.com.json\nファームスキンズ\nfarmskins.com · 登録者数 2016-03-23\n\tブロック済み\n2026-09-19、2026-09-21 ·生のHTML\n\tsteam.kobal.cc\tCLEAN\n2026-09-19、2026-09-21 ·生のHTML\n\t2017-01-07\nkobal.cc、RDAP\n\tブラウザのライブキャプチャ + 提供されたOpenID URL\tfarmskins.com.json\nCobaltLab\ncobaltlab.tech\n\tブロック済み\n2026-09-21 ·生のHTML\n\tcobaltauth.com\tCLEAN\n2026-09-21 ·生のHTML\n\t2025-01-07\nRDAP\n\t指定された OpenID URL\tcobaltlab.tech.json\nCSGO.NET\ncsgo.net · 登録者数 2012-07-22\n\tブロック済み\n2026-09-21 ·生のHTML\n\tcn2.easylot.net\tCLEAN\n2026-09-21 ·生のHTML\n\t2016-09-03\neasylot.net、RDAP\n\tブラウザのライブキャプチャ\tcsgo.net.json\nGGDrop\nggdrop.com\n\tブロック済み\n2026-09-21 ·生のHTML\n\tggauth.com\tCLEAN\n2026-09-21 ·生のHTML\n\t2023-05-03\nRDAP\n\t指定されたOpenID URL\tggdrop.com.json\nRustChance\nrustchance.com\n\tブロック済み\n2026-09-21 ·生のHTML\n\thgfuihd.com\tCLEAN\n2026-09-21 ·生のHTML\n\t2019-01-27\nRDAP\n\t指定された OpenID URL\trustchance.com.json\nSkin.Fans\nskin.fans\n\tブロック済み\n2026-09-21 ·生のHTML\n\tauth.skinfans.com\tCLEAN\n2026-09-21 ·生のHTML\n\t2018-07-16\nskinfans.com、RDAP\n\t指定された OpenID URL\tskin.fans.json\nスキンポート\nskinport.com · 登録 2018-09-05\n\tブロック済み\n2026-09-21 ·生のHTML\n\tskinport.app\tCLEAN\n2026-09-21 ·生のHTML\n\t2020-06-20\nRDAP\n\tブラウザのライブキャプチャ + 提供されたOpenID URL\tskinport.com.json\nSkins.Cash\nskins.cash\n\tブロック済み\n2026-09-21 ·生のHTML\n\tskinscash.live\tCLEAN\n2026-09-21 ·生のHTML\n\t2019-12-05\nRDAP\n\t指定された OpenID URL\tskins.cash.json\nTF2Hunt\ntf2hunt.com · 登録者数 2018-01-13\n\tブロック済み\n2026-09-21 ·生のHTML\n\trstspcl.com\tCLEAN\n2026-09-21 ·生のHTML\n\t2020-08-08\nRDAP\n\tブラウザのライブキャプチャ + 提供されたOpenID URL\ttf2hunt.com.json\nCSGOGem\ncsgogem.com · 登録 2016-10-16\n\tブロック済み\n2026-09-22 ·生のHTML\n\tapi.csgem.com\ncsgem.com — 別途登録可能なドメイン\n\tCLEAN\n2026-09-22 ·生のHTML\n\t2014-03-08\ncsgem.com、RDAP — レジストリ内で最も古いドメイン\n\t手動収集 + リンクフィルターによる取得\tlinkfilter-2026-09-22.json\nGamdom\ngamdom.com · 登録者数 2016-07-29\n\tブロック済み\n2026-09-22 ·生のHTML\n\tlogin.gambldom.com\ngambldom.com — ブランド名と1文字だけ違う\n\tCLEAN\n2026-09-22 ·生のHTML\n\t2017-09-24\ngambldom.com、RDAP\n\t手動収集 + リンクフィルターによる取得\tlinkfilter-2026-09-22.json\n12CS\n12cs.fail · reg. 2026-03-24\n\tブロック済み\n2026-09-22 ·生のHTML\n\tfail.games\tCLEAN\n2026-09-22 ·生のHTML\n\t2021-08-24\nfail.games、RDAP\n\t手動収集 + リンクフィルターによる取得\tlinkfilter-2026-09-22.json\nCSGOEmpire\ncsgoempire.com · 登録者数 2015-06-10\n\tCLEAN\n2026-09-19、2026-09-21 ·ウェイバック 2026-09-21\n\tcsgoempirelogin4.com\n10個の番号付きドメイン「login1～10」のうちの1つ\n\tCLEAN\n2026-09-21 ·ウェイバック 2026-09-21\n\t2020-07-20\n05:49:17Z、Verisign RDAP\n\tブラウザのライブキャプチャ\tcsgoempire.com.json\nCS.MONEY\ncs.money\n\tCLEAN\n2026-09-21 ·生のHTML\n\tauth.dota.trade\tCLEAN\n2026-09-21 ·生のHTML\n\t2016-07-15\ndota.trade、RDAP\n\tSteam ログインページの通知\tcs.money.json\nCSFloat\ncsfloat.com · 登録者数 2021-07-11\n\tCLEAN\n2026-09-21 ·生のHTML\n\tcsgofloat.com\n事業者の旧ブランドドメイン。登録可能な独立したドメインであり、回避の兆候ではない。\n\tCLEAN\n2026-09-21 ·生のHTML\n\t2015-09-29\nRDAP\n\tブラウザのライブキャプチャ\tcsfloat.com.json\nG4Skins\ng4skins.com\n\tCLEAN\n2026-09-21 ·生のHTML\n\tauth.g4s.to\tCLEAN\n2026-09-21 ·生のHTML\n\t2021-05-30\ng4s.to、RDAP\n\t指定された OpenID URL\tg4skins.com.json\nJuice.GG\njuice.gg\n\tCLEAN\n2026-09-21 ·生のHTML\n\tletmeinjuice.com\tCLEAN\n2026-09-21 ·生のHTML\n\t2024-04-15\nRDAP\n\t指定された OpenID URL\tjuice.gg.json\nMarket.CSGO\nmarket.csgo.com\n\tCLEAN\n2026-09-21 ·生のHTML\n\tdota2.net\tCLEAN\n2026-09-21 ·生のHTML\n\t2011-10-29\nRDAP\n\tブラウザのライブキャプチャ + 提供されたOpenID URL\tmarket.csgo.com.json\nRust.TM\nrust.tm\n\tCLEAN\n2026-09-21 ·生のHTML\n\tdota2.net\tCLEAN\n2026-09-21 ·生のHTML\n\t2011-10-29\nRDAP\n\t指定された OpenID URL\trust.tm.json\nCSGOLounge\ncsgolounge.com · 登録者数 2013-08-14\n\tCLEAN\n2026-09-22 ·生のHTML\n\tdota2.net\nこの認証ホスト上の3つ目のフロントエンド\n\tCLEAN\n2026-09-22 ·生のHTML\n\t2011-10-29\ndota2.net、RDAP\n\t手動収集 + リンクフィルターによる取得\tlinkfilter-2026-09-22.json\nDota2Lounge\ndota2lounge.com · 登録者数 2012-08-10\n\tCLEAN\n2026-09-22 ·生のHTML\n\tdota2.net\nこの認証ホスト上の4つ目のフロントエンド\n\tCLEAN\n2026-09-22 ·生のHTML\n\t2011-10-29\ndota2.net、RDAP\n\t手動収集 + リンクフィルターによる取得\tlinkfilter-2026-09-22.json\nスキンバロン\nskinbaron.de\n\tCLEAN\n2026-09-21 ·生のHTML\n\tskinbaron.com\n同じブランド、異なるTLD\n\tCLEAN\n2026-09-21 ·生のHTML\n\t2015-12-22\nRDAP\n\t指定された OpenID URL\tskinbaron.de.json\nTF2Royal\ntf2royal.com · 登録者数 2022-08-17\n\tCLEAN\n2026-09-21 ·生のHTML\n\ttf2auth.com\tCLEAN\n2026-09-21 ·生のHTML\n\t2021-07-27\nRDAP\n\tブラウザのライブキャプチャ + 提供されたOpenID URL\ttf2royal.com.json\nTradeit\ntradeit.gg\n\tCLEAN\n2026-09-21 ·生のHTML\n\tconnect-tradeit.com\tCLEAN\n2026-09-21 ·生のHTML\n\t2022-02-23\nRDAP\n\t指定された OpenID URL\ttradeit.gg.json\nアップグレーダー\nupgrader.pro\n\tCLEAN\n2026-09-21 ·生のHTML\n\tupgauth.space\tCLEAN\n2026-09-21 ·生のHTML\n\t2026-08-14\nRDAP\n\t指定された OpenID URL\tupgrader.pro.json\n出典: steamcommunity.com/linkfilter、認証なしの GET リクエスト、2026-09-21、53 ホスト、3 秒間隔；steam_tos_assets/linkfilter-recheck-2026-09-21.json; 生のHTMLがsteam_tos_assets/linkfilter-raw/. 登録期間：RDAP、steam_tos_assets/domain-registration.json. · 2026-09-19 の事前チェックlinkfilter-all-results.json ・ルートレコードをauth-route-audit.json ・「Link Filter」のページ（2026-09-21）のウェイバック・マシンのスナップショット。これらは、以下に記載されています。wayback-snapshots.json (rbsnin.com にはスナップショットが存在しません。ローカルの生ファイルが唯一の記録です)。\n\n登録期間：RDAP（steam_tos_assets/domain-registry/). 「指定された OpenID URL」はリクエストパラメータを定義するものであり、ログインが完了したことを示すものではない。著者らはどのプラットフォームにおいてもログインを完了させていない。 別のドメインが存在すること自体は、回避の証拠にはならない。「ブロックされた認証ホストが0件」というのも、それ単体では独立した発見とは言えない。1つでもブロックすれば、そのプラットフォームのSteamログインが機能しなくなるため、正常に機能するログインから構成された登録リストには、ブロックされた認証ホストが含まれることはない。 重要なのは、その組み合わせとその継続期間である――Link Filter上のメインドメインと、何年も継続して稼働しているログインドメインが並んでいることである。この表には30行が記載されている：ルートごとの証拠ファイルがある27のルートのうち25行に加え、2026-09-22で追加された5行であり、そのLink Filterの分割状況はlinkfilter-2026-09-22.json その領域自体は手作業で収集されたものですが――ソース欄の行にそう記載されています。表示されていない2つのエビデンスファイルの経路は、skinsnipe.com（認証ホストpricing.tradeupspy.com, 登録済み 2020-03-11) および csgobig.com (認証ホストletmeinbig.com, 登録済み 2023-01-20); 両者とも、2026-09-22のチェックにおいて「BLOCKED main / CLEAN auth host」を返し、SHA-256で記録されたlinkfilter-2026-09-22c.json、しかしそのバッチの生のHTMLは公開セットに含まれていないため、この表の他のすべての行が裏付けているような行が割り当てられるのではなく、ここでは名称が記載されています。登録簿に残る手作業で収集された12のルートについては、master_registry.json 以下realm_src: user.\n\n一次実証監査・複数年度にわたる期間\n「全体像の罠」：リンクフィルターはコンプライアンスの「見せかけ」に過ぎず、盾にはならない\n\nデスクトップブラウザでは、ユーザーは外部の防御機能によって保護されています。Googleの「セーフブラウジング」やMicrosoftの「SmartScreen」は、既知のフィッシング攻撃を検知すると、画面全体に赤い警告を表示してブロックします。Steamの「ビッグピクチャー」モード、ゲーム内オーバーレイ（Shift+Tab）、およびSteamデッキ（SteamOS）では、これらの防御機能は存在しません。 この組み込みブラウザは拡張機能を一切サポートせず、外部の「セーフブラウジング」エンジンを無効化しており、ユーザーに残される防御手段はただ一つ、Valve'sのみとなっています。linkfilter 間質性。\n\n横にスクロールして4つの結果を比較 →\n\n92.5%\n2025～2026年：最新の手口を用いたフィッシング問題なく合格した (37/40)\n77.5%\n2023–2024年のCS2時代のフィッシング問題なく合格した (31/40)\n70.0%\n2021–2022年の従来のフィッシング問題なく合格した (28/40)\n7 / 7\nギャンブル用メイン回線が遮断された（陽性対照）\n複数年にわたる縦断的監査：120の「Pure Steam」フィッシングドメインを実環境でテスト（2026年9月24日）\n\nValveのフィルタが、単に新しい脅威の検知に時間がかかっているだけなのか、それとも根本的にそれらを見逃しているのかを確認するため、我々は監査を行った。120件の「Steam」に特化したフィッシングドメインが確認された 3つの歴史的コホートを横断して、対してsteamcommunity.com/linkfilter:\n\n第1期：2021年～2022年（従来のトレードオファーおよびアイテムドロップ） — 70.0% クリーンパス（28/40）。 地域監視団体によってリストアップされてから4～5年が経過しても、従来のフィッシングホストの10件中7件は、いまだに何のブロックも受けずにアクセス可能な状態にある。\n第2期：2023年～2024年（CS2ベータ版への過剰な期待と偽のサポート要請） — 77.5% クリーンパス（31/40）。 『Counter-Strike 2』のリリースを装ったキャンペーンや、偽のコミュニティへの呼びかけ（例：cs2-steam.com,appealsteamcommunity.help) そのまま通り抜ける。\n第3期：2025年～2026年（サーバーレス・エッジ展開とファビコンのクローン） — 92.5% 完全合格（40問中37問正解）。 EdgeOne、Vercel、Cloudflare Pages上で展開される最新のフィッシングキット（例：steamgifter.online,steam-dp4lt5b8fnez.edgeone.dev) 事実上、何の妨げもなく通り抜ける。\n\nテレメトリーと責任免除――保護ではない。 純粋な「2」型フィッシングを「0」から「1」へと通過させてしまうのであれば、なぜリンクフィルターが存在するのでしょうか？これは、企業の責任免除条項としての役割と、外部へのクリックを監視するテレメトリセンサーとしての役割を果たしています。丁寧な「あなたは Steam を離れます」 クリック可能な緑色の「続行」ボタンが付いた通知で、ValveはSteamの「利用規約」に基づき、法的責任を被害者に転嫁している（*「ユーザーは自発的にSteamの外へ移動した」*）。 Valveはクリックに関するテレメトリデータを収集するが、盗難を阻止することはない。\n\nファビコン・ハッシュの検証：脅威フィードの取り込みはゼロ。 独立系の脅威インテリジェンスプラットフォーム（urlscan.io、Shodan、Censys）は、Steamの公式ファビコンハッシュを単純に検索することで、現在稼働中のSteamフィッシングキットを特定しています（page.favicon.hash:9f890a9debcdfccc339149a7943be9aff9e4c9203c2fa37d5671a5b2c88503ad NOT domain:*.steampowered.com). この基本的な自動チェックにより、アクティブなフィッシングクラスターが数秒で特定されます。Valveは外部フィードとの同期を行わず、ハッシュベースの脅威ハンティングも実施せず、規制当局からの要請（2016年のWSGCギャンブル命令）があった場合や、商標登録済みのドメイン文字列を保護する必要がある場合にのみ、手動で介入します。\n\n主要な監査証拠となる資料： 120ドメインにわたる複数年にわたる縦断的監査：longitudinal-steam-phishing-audit.json ・100件の専用 Steam フィッシングサンプル：linkfilter-steam-phishing-100.json ・広範な給餌監査（n=250）：linkfilter-coverage-2026-09-22.json.\n\nCSGOEmpire — 10個の番号付き認証ドメインの一括登録\n\nについて2020-07-20 10個の番号付きドメイン、csgoempirelogin1.com ～を通じてcsgoempirelogin10.com, が登録されました。これら10件すべてについて、Verisign RDAPタイムスタンプが記録されています：login1 05:49:06Z、login5 05:49:08Z、login2 05:49:11Z、login3 05:49:14Z、 login4 05:49:17Z、login6 05:49:20Z、login7 05:49:23Z、login8 05:49:26Z、login9 05:49:28Z —22秒で9つのドメイン — そして、その7分後の05:56:03Zにlogin10が登録された。この間隔は、単一のレジストラによる一括処理と一致している。\n\nこのパターンは、事前にプロビジョニングされたフォールバックホストの場合と一致しています。ただし、login4 実際のOpenIDリクエストにおいて、この現象が確認された。csgoempire.comとcsgoempirelogin4.comは、いずれも2026-09-21のリンクフィルターで「CLEAN」と判定された。CSGOEmpireは、2016年7月の通知に関する報道で名指しされたサイトには含まれていなかった。\n\n# DNS — 10台すべて稼働中（2026年9月）\nOK csgoempirelogin1.com 172.67.129.43\nOK csgoempirelogin2.com 172.67.175.168\nOK csgoempirelogin3.com 188.114.96.3\nOK csgoempirelogin4.com 188.114.96.11 ← OpenIDトラフィック内\nOK csgoempirelogin5.com 172.67.160.194\nOK csgoempirelogin6–10.com CloudflareのIPアドレス\nNXDOMAIN: csgoempirelogin11.com\n登録された10件すべてが2020-07-20；10件すべてにRDAPタイムスタンプが付与されている (steam_tos_assets/domain-registry/csgoempireloginN.com.rdap.json)\n規制当局に向けた結論\nメインドメインがブロックされている一方で、認証ホストがブロックされていない場合、ログインルートは開いたままとなり、その状態が何年も続くことになります。\n\nメインドメイン上のリンクフィルターブロックは、検証可能な公開レコードです。認証ホストは「Steamでサインイン」のトラフィックを伝送し、Valve自身のOpenIDリクエストパラメータに表示されます。 2026-09-21および2026-09-22に対する調査全体を通じて、26組のフィルタ分割ペアにおいて、メインドメインはリンクフィルタブロックを返したのに対し、そのログインを中継するプロキシはブロックを返さなかった。上記の登録情報は、その残りの半分を測定したものである。つまり、これらのホストは短命な使い捨てドメインではないということだ。 そのうちのいくつかは、調査時点で10年以上登録されていたが、それらの日々のすべてにおいて、Valveは自身のリクエストパラメータ内でそのホスト名を受信していた。 Valveは事業者ごとの適用記録を公開していないため、これらのホストに対して他の措置が適用されたかどうかは、公開データからは確認できない。\n\n12歳6ヶ月\ncsgogem.com はリンクフィルターによってブロックされています。\nそのログインホストapi.csgem.com ～されてきた\n2014-03-08から登録されていますが、そうではありません。\n平易な言葉による要約 — 規制当局および裁判所向け（展開）\n平易な言葉による要約 — 規制当局向け\n背景：「Steam」とは何か、そしてなぜこれがここで重要なのか\n\nSteamは、Valve社（米国ワシントン州ベルビュー）が運営するソフトウェアプラットフォームです。 SteamはデジタルIDプロバイダーとして機能しています。インターネット上のギャンブルやゲームのウェブサイトでは、「Steamでログイン」と呼ばれるシステムが採用されており、このボタンを通じて、ウェブサイトは訪問者が本物のSteamアカウントを所有していることを確認できます。 これは「Googleでログイン」や政府発行の身分証明書による本人確認と同様の仕組みです。ウェブサイトがユーザーをSteamのサーバーにリダイレクトすると、Steamが本人確認を行い、Steamがユーザーを元のウェブサイトに戻します。 Valveが認証システムを運用しています。「Steamでログイン」によるすべてのログインは、Valveのサーバーを経由します。\n\nValveが行ったこと：ドメインブロック\n\n2016年7月、スキンギャンブルをめぐるメディアや法的な圧力を受けて、Valveの弁護士は、名指しされた約23のギャンブルサイト（2016年7月21日の報道による）に通知を送付した。 2016年10月、Valveはワシントン州ギャンブル委員会に対し、40以上のサイトに連絡を取ったと伝えた。一部のギャンブルドメインは、Steam リンクフィルター — Steam内（チャット、プロフィールページ、ストア内）に投稿された、これらへのリンクをすべて警告ページにリダイレクトするリスト：「リンクがブロックされました！」 リンクフィルタは、Valveの外側からその効果を観察できる唯一の強制措置である。\n\n例： へのリンクrollbit.com Steamを選択すると、リンクフィルターの警告ページが表示されます（2026-09-19と2026-09-21にチェックが入っています）。 理論上、ギャンブルサイトはブロックされています。\nプロキシドメインとは\n\nA「separate-domain auth host」は認証プロキシです: 別の登録可能なドメイン上に存在する第2のウェブサイトのアドレスで、同じ運営者が、「Steamでログイン」という手順を実行する目的のみのために、ユーザーとSteamの間に配置するものです。これはログインをプロキシします。 ユーザーはプラットフォームにログインしていると信じているが、Valveに届くリクエストには、プラットフォームのホスト名ではなく、このプロキシのホスト名が記載されている。 通常、このサイトはギャンブルサイトとの関連性が外部からは全く見えず、Steamがユーザーの身元を確認した後、ユーザーを再び受け入れるアドレスとなる。\n\n例： Rollbitは、以下の下で運営されていますrollbit.com、これはリンクフィルタによってブロックされます。 Steam の認証では、2026-09-20 で観測されたフローは別のアドレスを使用していました：rbsnin.com, 登録番号 2026-09-18。 このアドレスから返されたのは「リンクフィルター」ブロックなし 2026-09-21。 当該ギャンブルサイトは運営を継続しており、そのSteamのログインフローはブロックされていないホストを経由していた。\n重要なポイント：すべてのリクエストで認証ホストが Steam に送信される\n\nValveは、どの認証ホストが使用されているかを把握するために、スキャンやクロールを必要としません。SteamはOpenID アイデンティティプロバイダー これらのサイトでは、「Steamでログイン」をクリックするたびに、認証ホスト名を平文で含むGETリクエストがValveのサーバーに送信されます。 OpenID 2.0 §9.1 によると、return_to このフィールドは形式上は任意ですが、これがなければ Steam はログイン結果を返すことができないため、Steam によるログインを正常に行うためには、事実上必須となります。Steam 自体は、ログインページにホスト名を表示します（「<host>は、SteamやValveとは一切関係がありません。\"）。\n\n— リクエストの形式 Steam が受信した内容（2026-09-20 における Rollbit の観測結果に基づくホスト）： —\nGET steamcommunity.com/openid/login\n&openid.mode=checkid_setup\n&openid.return_to=https://rbsnin.com/… ← 事実上必須；Valveのログに記録される\n&openid.realm=https://rbsnin.com ← サイト側による自己申告；Steamのログインページに表示\nそのサイトがサーバー間認証（check_authentication）を使用している場合、Valveのログには、プラットフォームのサーバーIPアドレスとホスティングネットワークも記録されます。\n\nこのリクエストからホスト名を抽出するのは標準的な処理です。どのホストに対して措置が講じられ、どのホストには講じられなかったか、またどのような基準に基づいて判断されたかといった実施記録は、Valveのインフラ内にのみ存在しており、公開されていません。\n\nこれが何を証明しているか\n\n1. 「リンクフィルター」ブロックは、ログインではなくリンクに対して作用します。 メインドメインをブロックする（例：rollbit.com)は、Steam内のリンクをクリックしたユーザーに対して警告を表示します。 これにより、サイトの運営が停止したり、別のアドレスを通じてValve独自のOpenIDサービスを利用できなくなったりすることはありません。\n\n2. テスト対象となった認証ホストはブロックされていませんでした。 上の表は、2011年から2026年9月の間に登録された別ドメイン認証ホストを示しており、そのうちのいくつかは2016年7月の通知から数年が経過してからの登録となっています。 26組のペアにおいて、メインドメインはLink Filterによるブロックを返しましたが、そのログイン情報を伝達するプロキシはブロックされませんでした（未認証チェック、2026-09-21および2026-09-22；生の応答とSHA-256は保存済み）。 そのプロキシは、Valveがそれを拒否した日に動作を停止することになるため、ここでの評価基準は、それがリストに掲載されているかどうかではなく、どれだけの期間稼働していたかである。 Valveは、自身のOpenIDリクエストにおいてこれらのホスト名を受け取っている。Valveが事業者ごとの適用記録を公開していないため、リンクフィルター以外の措置が適用されたかどうかは、公開データからは判断できない。\n\n3. 各サイトは、Valveのインフラを通じて引き続き認証を行っていた。 「Steamでログイン」はValveのサービスであり、これを通じた認証はすべて、Valveが受信して処理するリクエストとなります。 Valveもケースキーから収益を得ており、Steamコミュニティマーケットでは、マーケット内で完了した取引（外部取引を除く）に対して、合計で約15%の手数料を徴収しています。 「リンクフィルター」アクションは公開レコードを作成しましたが、認証関係を中断することはありませんでした。\n\nブロックすれば効果があっただろうか？\n\n同様に、2023年に無料ドメイン登録サービス「Freenom」が事業を終了した際、同サービスのドメインに依存していたフィッシング攻撃は阻止されました。事業の継続性は、インフラの安定性に左右されます。\n\nここでも同様の理屈が当てはまります。もしSteamのOpenID処理において認証ホストが拒否された場合、新しいホストが登録され、証明書が発行され、DNSの反映が完了するまでは、プラットフォームの「Steamでログイン」機能が利用できなくなります。その間、サービスが停止することになります。\n\nローテーションがあっても、ブロックが無意味になるわけではない。 これにより、ブロック処理が運用コストとなります。新しいホストは初回利用時にValve自身のリクエストログに記録されるため、レスポンスの処理速度は初回利用時の速度に左右される可能性があります。\n\n一括登録そのものがシグナルとなります： CSGOEmpireの「login1～login10」は2020-07-20に登録されており、そのうち9件は22秒以内に登録されました（Verisign RDAP）。応答はドメインごとに個別に返される必要はなく、1つのレジストラ・セッションから連続して行われた一連の応答は、1つのシリーズとして識別されます。\n\n公開記録には、ホストのローテーションによって阻止された認証ホストのブロック試行は確認されていない。\nこれによると、各ログインを処理するプロキシは稼働し続けた一方で、主要なドメインがブロックされていたことが示されている――2026-09-22時点で26組、登録された最も古い認証ホストは12年6ヶ月前――また、どの事業者についても、公開された強制措置の記録はなかった。\nしたがって、規制当局にとっての疑問は、自らが送信したOpenIDリクエストで受け取った認証ホストに対して、Valveがどのような執行措置（もしあるならば）を講じてきたか、ということである。\nValve 何が起きたのか — そして、なぜそれが認証パスを中断しなかったのか\n\n以下の表は、公開されている各 Valve のアクションについて、それが OpenID 認証のエントリポイントに影響を与えたか否かを整理したものです。 この調査結果は「Valveは何もしなかった」というものではなく、公開されている記録上の措置のいずれも、ギャンブルプラットフォームのログインがValveのサーバーを経由する箇所には影響を与えていなかったということです。\n\n日付\tValve アクション\t影響を受けたopenid.return_to パス？\n2016年7月\t2016年7月13日の公式声明；弁護士による約23か所の指定サイトへの通知（2016年7月21日付報道）；Valveが2016年10月にWSGC宛てに送付した書簡に基づき、40か所以上のサイトに連絡\tいいえ。通知やリンクフィルターは演算子やリンクに対して作用するものであり、OpenIDのリクエストパスは変更されていません。\n2017年\tの閉鎖IEconItems_730/GetPlayerItems （CSFloatのエンジニアリングアカウントによる情報。Valveの変更履歴は見つかりませんでした）\tいいえ。影響を受けたのは、公開項目の履歴の表示設定です。OpenID認証については変更されていません。\n2018-03-29\tCS:GO、7日間のトレードロックが発表されました（blog.counter-strike.net）\tいいえ。アイテムの移動速度が低下しただけで、OpenIDのリクエストパスは変更されていません。\n2022-05-10\tパブリックWeb APIからトレードキャンセルエンドポイントが削除されました（ユーザーによる発見；変更履歴なし — node-steam-tradeoffer-manager #325）\tいいえ。オファースワップのツールは閉鎖されましたが、OpenID認証には変更はありませんでした。\n2023-12-04\tAPIキーの作成には、モバイル認証が必要になりました（steamcommunity.com/dev/apikey；変更履歴なし）\tいいえ。主要なエンドポイントは保護されており、ここに記載されている認証ホストは影響を受けませんでした。\n2026-09-19 / 9月21日\tSteam 著者らが観察したリンクフィルタの状態\t保存された 2026-09-21 の再確認において、14番のメインドメインがブロックを返した — レジスタ内の 26組のペアが 2026-09-22 によって分割された — 一方で、各ログインを処理するプロキシは引き続き動作していた。\n出典：Valve 2016年7月13日の声明（store.steampowered.com/oldnews/22883,アーカイブ済み 2026-09-21) ・2017年の閉鎖に関するCSFloatエンジニアリングの報告（blog.csfloat.com,アーカイブ済み 2026-09-21) · リンクフィルタの状態：linkfilter-recheck-2026-09-21.json.\nこの知見は、Valveが以下の理由によりOpenIDリクエストを拒否したという、公表された事例が1件でもあれば反証可能である。openid.return_to ギャンブル関連の認証ホストを指していました。公開記録にはそのようなインスタンスは見つかりませんでした。\n直近の2件のauth-host登録\nhowl.uno2026-08-11（RDAP）として登録され、2026-09-21の41日前に登録されました。howl.ggは、2026-09-18、2026-09-19、および2026-09-21に対してリンクフィルタによるブロックを返しました。 このブロックが登録に先立って発生したかどうかは定かではありません。\nrbsnin.com2026-09-18T09:34:52Z（Verisign RDAP）に登録されており、Steam自身のログインページ上の通知を通じて、2026-09-20のRollbitのSteamログインフローで確認された。 rollbit.comは2026-09-19および2026-09-21でLink Filterによるブロックを返したが、rbsnin.comは返さなかった。\n上記の表にある各ホストは、Valveの認証サーバーに対して次のように送信されます。openid.realm ログインを試みるたびに。\nルートごとの完全なデータおよびリンクフィルタの判定結果：上記のセクション3の表。生データはlinkfilter-recheck-2026-09-21.json そしてlinkfilter-all-results.json.\n方法論 — ルートおよびリンクフィルタのカウント方法の決定\n1. ドメイン解決\nこの「0」監査では、要求された189のプラットフォームのうち78件が解決されました：33件は自身のホスト名で、20件は自身のサブドメインで認証されており、これらは直接認証であり、いずれも別ドメインのルートとしてカウントされていません。 残りの25 登録可能な別のドメインを通じて認証を行う、24の異なるホスト名にわたって（dota2.netはmarket.csgo.comおよびrust.tmと共有されています）：10件はブラウザのリアルタイムキャプチャにより特定され、3件はSteam自身のログインページ上の通知により、12件は提供されたOpenID URLにより特定されました。リアルタイム登録情報（master_registry.json, 2026-09-22) はそれを次のように拡張する44の別ドメインのルート: 26組のフィルタ分割ペア（メインドメインが「BLOCKED」、認証ホストが「CLEAN」）に加え、メインドメインの分割がないルートがさらに18件あります。これら44件のうち、27 ルートごとの証拠ファイルを携行する; 残りの17個は手作業で収集されたもので、マークが付けられていますrealm_src: user レジストリに。 その17件のうち5件――csgogem.com、gamdom.com、12cs.fail、csgolounge.com、dota2lounge.com――は2026-09-22に追加され、両方のホストに対するリンクフィルターのキャプチャ（生のHTML＋SHA-256がlinkfilter-2026-09-22.json)、したがって、その領域が手動で収集されたものであるにもかかわらず、分割そのものは裏付けられています。これらは、エビデンスファイルのルートとともに、上記の表に記載されています。tfauth.com (tf2easy.com) は 2026-09-22 にレジストリから削除されました。arena.fragnet.net と同様、その元のサイトとの関連性を裏付ける検証可能な情報は一切ありません。この数値は、公開されている情報から再算出可能です。auth-route-audit.json (2026-09-21の連続) については、1つのルールが適用されます。すなわち、プラットフォームは、その観測された Steam の OpenID ホストが、プラットフォーム自体とは異なる登録可能なドメイン上に存在する場合にのみカウントされます。\n2. Steam リンクフィルターの状態\n以下の方法でテスト済みsteamcommunity.com/linkfilter/?url=https://[domain]、認証なし、2026-09-19および2026-09-21で；SHA-256で保存された生のHTML。メインドメインと認証ホストについて、それぞれ個別にステータスが記録された。 分類器は、一般的な「Steamを離れます」という通知（CLEAN）と、「リンクがブロックされました！... 悪意のある可能性があるとフラグが立てられました」というページ（BLOCKED）を区別します。google.comの対照テストにより、これら2つが混同されていないことが確認されています。 このテストの以前の認証済みバリエーションは、そのコントロール領域を含むすべてのドメインに対して「ブロックされました」と返したため破棄されました。これは、プローブスクリプト内の無効なセッションクッキーに起因するものであり、実際の結果ではありませんでした。\n3. 認証ホストの確認\nライブキャプチャ：Playwrightブラウザが各プラットフォームのログインフローに遷移し、openid.return_to ホスト名は、傍受されたリクエストから読み取られました。ログインページの注意：ホスト名は Steam 自身の「<host>は、SteamやValveとは一切関係がありません。\"というテキストは、Steamによって以下のように変換されます。openid.realm (rbsnin.com、sc-auth.net、auth.dota.trade)。提供されたURL：著者らに提供された「a Steam loginform」というURL。これはリクエストパラメータを定義するものであり、ログインが完了したことを示すものではない。どのプラットフォームにおいても、ログインは完了していない。\n4. 対象範囲 — 解決されなかった点、そしてそれがなぜ重要なのか\n189のプラットフォームのうち、110では、確立されたルートは見つかりませんでした そのうち1件は該当しませんでした（189 − 78 − 1）。この資料では、これらはいずれもカウントされていません。 監査ファイルに基づく 110 件の内訳は、ボット対策 22 件、タイムアウト 14 件、HTTP エラー 12 件、ナビゲーションエラー 10 件である。オブザーバーはログインフローに到達できなかったが、これらのサイトのほとんどは通常のブラウザでは正常に開く。 20件はランディングページにログイン制御（Steam）が見られなかった；16件はホストに解決できないログインフローに到達した；11ドメインはDNSで解決されなかった；5件は同意画面で停止した。 以下のリストでは、同じ110件を異なる方法で分類している。DNSで解決されなかった11件は、別項目として以下のように記載されている：削除済み · NXDOMAIN、そして適用対象外だった1件のエントリも他のエントリに加わりました。189のプラットフォームを監査し、両方のリゾルバーから確定的なNXDOMAINが返された11件を削除しました。178件が保持された (platform-audit.json,platforms-removed.json). 台帳が命名パターンから推測した137の認証ドメインは、2026-09-19のデータから削除された。これらは一度も観測されていないため、証拠とはならない。 推測されたURLのうち3つは、提供されたOpenID URLと矛盾していました。具体的には、buff.163.com、gamerpay.gg、csgoluck.comは直接認証を行うのに対し、推測されたURLはbuffauthproxy.163.com、gamerpayredirect.io、lucklogin.appでした。削除された項目は、公開された監査ファイルに記載されています。\n25という数字は下限であり、上限ではありません。解決された78のプラットフォームのうち、25は別のドメインを使用しており、53は使用していませんでした。この比率から、未解決の110について何らかの推測を行うことはなく、本報告書のどこにもこの比率に基づく予測は記載されていません。 各プラットフォームは、ユーザーがサイトを開き、「Steamでサインイン」をクリックするだけで解決可能です。認証用のホスト名は、読み込まれるSteamページのURLに含まれています。\nこのセクションの要点： 独立した観察者が189のプラットフォームを特定するには、ブラウザと多大な忍耐力が必要であり、78件を特定できた。「Valve」を特定するにはデータベースのクエリが必要だ。「Steamでサインイン」を使用しているすべてのプラットフォーム（特定済み・未特定を問わず）は、openid.realm ログインのたびに、Valveの認証エンドポイントへアクセスします。この表に空白があるのは、作成者がシステム外にいるためです。Valveについては、そのような空白はありません。\n観測されたプロキシのホスト名はauth-route-audit.json. RDAP（Verisign）／IP2WHOISによるドメイン登録日。リンクフィルターの結果はlinkfilter-all-results.json.\nわかりやすくするための例え\n\nある認可を受けたタクシー会社が、規制当局から、登録済みの「メインストリート」の住所からはもはや営業できないと通告されたと想像してみてください。 その会社はメインストリートから看板を取り外しました。その看板の撤去は記録されています。 しかし、その同じ会社が「サイドストリート」に、別の名義で登録した住所を開設し、そこから営業を続けています。 規制当局は、両方の住所から出動するすべてのタクシーが利用する中央配車システムを運営している。すべての配車依頼には「サイド・ストリートから乗車」と表示される。 規制当局は、サイド・ストリートの営業許可を取り消すことは決してない。 メインストリートの看板の撤去が、実施された唯一の取り締まり措置でした。タクシー会社は営業を一度も停止することはありませんでした。\n\nパートA — 技術記録・第3.1節\nSteamの内には、Valveのリストが唯一のリストとして含まれている。\n\nSteamクライアント、ゲーム内オーバーレイ、またはBig Pictureモードでクリックされたリンクは、ユーザーのブラウザでは開かれません。これらはSteamに組み込まれた独自のブラウザ内で表示されるため、通常のブラウザで表示される警告レイヤーは表示されません。リンクフィルターは、数ある安全対策の一つというわけではありません。それこそが安全対策そのものです。\n\n通常のブラウザでは3つの独立した層\nGoogle セーフブラウジングGoogleのフィッシングおよびマルウェアリストに掲載されているホストに対して表示される全画面のインタースティシャルで、訪問しているサイトとは無関係に継続的に更新されます。\nウイルス対策ブラウザ拡張機能ほとんどのコンシューマー向けエンドポイント製品には、送信先をベンダー独自のレピュテーションリストと照合するブラウザアドオンが同梱されています。\nエンドポイントのHTTPS検査本製品がTLS検査を行う場合、ページコンテンツはユーザーに届く前にスキャンされます。\nSteamクライアント、オーバーレイ、およびBig Picture1層\nGoogle セーフブラウジング存在しません。このチェックには Google API キーが必要ですが、組み込み型の Chromium ビルドではこれらがプロビジョニングされていません。これらが存在しない場合、Chromium 自身の設計ドキュメントによると、セーフブラウジングハンドラーはリクエストチェーンに一切追加されないことになっています。\nウイルス対策ブラウザ拡張機能存在しません。Steamのレンダラーはユーザーのブラウザではなく、ユーザーのブラウザプロファイルから拡張機能を読み込むこともないため、このページに対してアドオンが実行されることはありません。\nエンドポイントのHTTPS検査製品によって異なります。トラフィックは、認識されたブラウザではなく、コード署名された Valve プロセス内で終了し、多くのエンドポイント製品では、署名済みのアプリケーションを TLS 検査の対象外としています。\n「Steam」リンクフィルターValve独自のブロックリスト。リンクがSteamのエコシステムを離れる際に参照される。実行されるチェックはこれのみであり、上記の表には、このセクションで記載されている認証ホストに対してこのチェックが返す結果が記録されている。\n読者の誰でも実行できるテストであり、失敗した場合はその結果は否定される\n\nGoogleが公開している「セーフブラウジング」のテスト用URLのいずれかを開いてください（testsafebrowsing.appspot.com) Chromeでは、全画面の赤いインタースティシャルが表示されます。Steamのチャットメッセージから同じURLを開き、Steamのクライアントまたはオーバーレイ上で表示させると、インタースティシャルは表示されません。 Steamが生成できる唯一の警告は、それ自体の「リンクフィルター」ページのみであり、それもValveのリストに登録されているホストに対してのみです。\n\nValve自身のバグ報奨金実績この1層構造については、以前にもValve自身のレコードで回避されていた\n\nリンクフィルターがクライアント内部で実行される唯一のチェックである場合、そのフィルター自体の障害モードは些細な問題ではありません。ValveのHackerOneプログラムに関する2件の報告は、いずれも受理され、解決済みであり、その後、その内容がすべて公開されています：\n\n#291750アーカイブ済み 2025-11-16 ↗Open Redirect · medium\nリンクフィルタの保護機能のバイパス\n\n2017年11月19日に報告され、解決され、2018年5月9日に公開された。報告書自体による概念実証：表意文字のピリオドを置き換える。 (%E3%80%82) ホスト名に含まれるドットについては —このブロックを回避することは可能です。 このセクションで取り上げているインタースティシャルは表示されませんでした。\n\n#1079561アーカイブ済み 2026-09-24 ↗情報開示 · 高\nWebブラウザ「Big Picture」がログイン用クッキーを漏洩し、機密情報を開示している（アカウント乗っ取りにつながる恐れあり）\n\n2021年1月15日に報告され、解決され、2021年9月21日に公開された。Valve自身の深刻度評価は「高」であり、タイトルにはその影響が明記されている。 開示された記録には、タイトル、評価、および日付が記載されています。技術的な解説は公開されたペイロードには含まれていないため、ここではそれ以上の引用は行いません。\n\nこれは著者らの解釈であり、いずれの報告書における調査結果ではない： この2つは、同じゲートの両側に位置している。1つは、目的地が開く前に警告が表示されないこと。もう1つは、そのページ内でページが開かれると、セッションがクライアントから離れてしまうことだ。セッションが乗っ取られた後に続く一連の出来事――プロンプトなしにキーが登録され、本来の取引がキャンセルされ、クローンに複製が送信される――は、以下に示されたパターンである。第5節 ～へ第8節. 両方の報告はクローズされており、いずれも現在進行形の脆弱性として扱われていません。これらの報告が立証している事実は、より限定的なものですが、それで十分です。つまり、残された唯一の防御層については、Valve自身の記録上、過去に回避された実績があることが確認されているのです。\n\n出典：各報告に関するHackerOneの開示記録（取得日 2026-09-22）— HackerOneが公表した番号、タイトル、チーム、脆弱性、深刻度、報告日、開示日、およびステータス。取得記録：hackerone-reports.json. ここには懸賞金の額は記載されておらず、検索して入手した公開記録にもその記載は見当たらない。\n\n現地観察 · PhishDestroy通常であればキャンペーンを終了させるはずの検知が、今回はキャンペーンを終了させなかった\n\nフィッシングホストが、次のような状態を維持しながらトラフィックを引き続き集め続ける様子を私たちは観察した。20件以上のベンダー検出. Webや電子メールを介して配信された場合、その状態のキャンペーンは数日で機能しなくなる――ブラウザもウイルス対策ソフトも、それらの判定に基づいて動作するからだ。Steam内では、どちらもそうはならない。判定は最初から存在していた。クライアント側からは、その判定について一切問い合わせがなかったのだ。\n\nウイルス対策ソフトをインストールしている未成年者にとって、これはどういう意味を持つのか\n\n彼は警告を一切無視せず、何も無効化しない。 Steamの中にメッセージが届く――無料のナイフ、友人のチームへの投票――そしてページはSteamの中で開かれる。彼はブラウザを一切開かないため、ブラウザによる保護を受けることもない。彼のウイルス対策ソフトは動作しており、そのドメインをすでに悪意のあるものと判定しているかもしれないが、確認を求められることは決してない。彼を止められたはずの警告は、すべてすでに存在している。しかし、そのどれもが彼には届いていない。 彼は、自分がSteamを離れたことは一度もないと信じており、実際、彼はそこを離れたことはなかった。\n\nこの「プレゼント」という手口はフィッシング詐欺師が考案したものではありません。「Valve」の無料アイテムという表現は、スキンサイトやギャンブルサイトが広告でよく使う手法であり、まさにそのせいで、このメッセージはごく普通のもののように見えてしまうのです。苦情：執行記録. 年齢および子どものデータ：第17条.\n\n出典：Steamは、Chromium Embedded Frameworkを通じてWebコンテンツをレンダリングします。steamwebhelper プロセス — 参照2024年6月27日付 DARKNAVYのテクニカル分析 ↗ そして Valve 自身のSteam クライアントベータ版フォーラム ↗ アーカイブ済み 2025-08-04 ↗. CEFのバージョンには依存していません。組み込み版のChromiumはChromeではなく、ChromeのGoogleサービスは一切含まれていません。APIキーを必要としないセーフブラウジング：Chromium 設計文書 ↗ アーカイブ済み 2026-08-21 ↗,Chromium API キー ↗ アーカイブ済み 2026-08-30 ↗ （「Chrome で使用されている Google API の多くは Google 独自のものです。派生製品での使用を意図したものではありません」）、また、キーが設定されていない他のビルドでも同様の現象が見られます —自家醸造カスク #193814 ↗. テスト用URL：testsafebrowsing.appspot.com ↗.\n\n2つの異なる時計\nドメインの登録時期。観測日。\n\nレジストリ登録日は、ドメインが登録された日付を示します。日付が記載されたOpenIDレコードは、そのレコード内のリターンホストを特定します。前者は、後者より前の期間を補うことはできません。\n\nこの完全な登録リストでは、個別の登録可能ドメイン、サイト固有のサブドメイン、および直接ルートが区別されています。各行には、その出典とDNSの結果へのリンクが記載されています。\n\nドメイン登録情報を確認する →· 登録日時のダウンロード ↗· 観察結果を再現する ↗\n\nパートA — 技術記録・第4節\nエンドポイントが閉じられました。パブリックトレースでキーが失われました。\n文脈と出典の制限\n\nSteamのリリースにより、アイテムのアセットIDが一般公開されなくなり、APIによる在庫情報へのアクセスが制限される変更が実施されました。その結果、公開データからは、元のアセットIDを用いて特定のアイテムを追跡することが不可能になりました。 以下に、変更前に可能だったこと、変更後に不可能になったこと、そして自身の所有物がどこへ行ったかを証明しようとする被害者が被る代償について述べる。CSFloatのエンジニアリングアカウントによれば、日付は2017年である。Valveの変更履歴は確認されていない。 この一連の経緯——2016年7月のギャンブルに関する声明からおよそ1年後——は、調査上の疑問点であり、結論ではありません。アイテムの記録自体はValveのシステム内に残っていますが、外部の調査員は元のIDチェーンへのアクセス権を失っており、float、seed、paint識別子では部分的な照合しかできません。\n\n規則 Valve が適用されます： Steam サポートでは、お客様のアカウントから削除されたアイテムを復元することはできません。また、何が起きたかを証明する責任はお客様にあります。記録： 2017年、Valveは、元のアイテムIDを伝送していたエンドポイントを閉鎖した。それ以前は、誰でも被害者のアカウントから盗まれたスキンを追跡し、マーケットプレイスのボットまでたどり着くことができた。しかし、それ以降は、Valveの外部からは誰もそれができなくなった。被害者に求められた証拠は、すり替えられていた証拠である — そして、それは今もなお、Valveの中に存在している。\n\n停電前の時代\n\n歴史的に、Steam上で生成されたすべての仮想アイテムは、グローバルに一意で不変のアセットID. サードパーティのOSINTデータベースは、これらのIDをインデックス化できる可能性がある。ユーザーのアセットが乗っ取られた場合、調査担当者は、その特定のアセットが、乗っ取り犯の中継アカウントから、マーケットプレイスやギャンブルサイトの保管アカウントへと移動する過程を追跡することができる。\n\n以前：公開データを利用すれば、誰でも被害者のアカウントから中間アカウントを経由して、マーケットプレイスやカジノの保管ボットに至るまでの資金の流れを追跡することができた。\n変更後\n\nCSFloatのエンジニアリングアカウントによると、Valveは2017年にエンドポイントを閉鎖し、外部からは元のアイテムIDが利用できなくなった。 この変更の理由に関するValveの声明は確認されていない。同期間において、アイテムを大規模に移動させた商用ボットアカウントに対する措置が公表された事例も確認されていない。\n\nその理由が何であれ、この変更によって、公開された所有権の連鎖が断絶してしまった。 被害者はもはや、公開データから元のIDチェーンを再現して、特定の盗難品が特定のマーケットプレイスやカジノを通じて換金されたことを証明することができなくなった。そのアイテムの記録は依然としてValveのシステム内に存在しているが、公開データに基づいて調査を行う一般市民、研究者、法執行機関は、それらにアクセスすることができない。\n\n変更後：公開データからは、元のアセットIDに基づいて特定のアイテムを追跡することはできなくなりました。2017年以降に移動されたアイテムの元IDによる保管履歴は、Valveのインフラ内でのみ存在し、そのような記録は公には公開されていません。 フロート、シード、ペイントの識別子では、部分的かつ確率的な照合しか行えません。\nIEconItems_730\nGET/IEconItems_730/GetPlayerItems/v1/\n追跡可能なペイロード（パッチ適用前）\n\"id\": \"14892281934\",\n\"original_id\": \"11829910211\",\n状況：被害者は、ボットアカウント間でアイテムの移動履歴を追跡できる。\n難読化されたペイロード（パッチ適用後）\n現在\n\"id\": \"HIDDEN_BY_PRIVACY_SETTINGS\",\n\"original_id\": \"NULL\",\n状況：外部の第三者は、公開データから元のアセットIDを用いてアイテムの来歴を追跡できなくなりました。\n証拠への影響： この変更後、被害者のアカウントからマーケットプレイスやカジノボットへと、特定のアセットをその元のアセットIDで追跡するために必要な公開データは、もはや利用できなくなった。 内部記録は依然として Valve に残っていますが、公開データに基づいて調査を行う被害者、研究者、または捜査官は、元のIDチェーンを再現することができません（float、seed、paintの識別子では部分一致しかできないため）。\n\n出典：CSFloatエンジニアリングによる、2017年の閉鎖に関する報告IEconItems_730/GetPlayerItems —blog.csfloat.com/how-floatdb-tracks-items (アーカイブ済み 2026-09-21) ・表示されているペイロードはフィールド形状を示す例であり、実際に取得された応答ではありません。・このクロージャに関する変更履歴は見つかりませんでした。\n\nパートA — 技術記録・第5節\n1回のセッション。ユーザーが認識している以上のアクセス権限。\n文脈と出典の制限\n\nValveのAPIキーのアーキテクチャは、2023年の変更前の時点では、業界の標準基準から逸脱していた （OWASP ASVS、NIST SP 800-63B）から逸脱しており、証拠アーカイブに保存されている在庫盗難に関する自動生成された苦情（第6～8節）に記載されている仕組みそのものである。\n\nルール Valve が適用されました： 「アカウント所有者が鍵を作成し、利用規約に同意したため、損失の責任を負う」――これが、アーカイブされた拒否事例における回答である。記録： 2023年12月までは、盗まれたセッションクッキーだけでそのキーを登録することができた。パスワードも不要だった。Steam Guardも不要だった。アカウントの所有者への通知もなかった。そのユーザーは鍵を作成しておらず、それを見ることもできなかったにもかかわらず、作成したと告げられた。 モバイル認証機能が追加されたのは2023-12-04のこと――2016年の声明から約7年後、アーカイブに保存されている詐欺関連のパネルからおよそ6年後である。その間の費用はValveによって支払われたわけではない。その費用は、その間に資金が使い果たされた口座――その一部は子供たちの口座だった――から支払われたのである。\n\nOWASP ASVS 2.8 / NIST SP 800-63B深刻度：重大\n1. 段階認証の不備\n\nSteam では、セッションクッキーのみを使用して、高度な権限を持ち、有効期間が長い API キーを生成することが可能でした。 開発者用APIキーの設定や変更時には、2FA（Steam Guard）やステップアップ認証の要求がなかったため、Steam Guardのモバイル確認（Steamが提供する唯一の第二要素）では、この手順を保護できなかった。 （2016年にValve自身のトラッカーでハードウェアによる第二要素が要求され、この課題は現在も未解決のままです：付録D、GH-01。）\n\n状況：2023年以前は修正されていませんでした。盗まれたクッキーを保持するスクリプトが、ユーザーの操作を一切必要とせずにキーを登録できる状態でした。\nOWASP A01:2021 / 最小権限の原則深刻度：重大\n2. 最小権限の原則の欠如\n\nSteam Web API には、ロールベースの認証スコープが一切存在しませんでした。「読み取り専用」の在庫ステータス用に発行された開発者用 API キーには、既存の取引の操作、新規取引の開始、Webhook の登録、有効な保留中の交換の拒否を含む、完全な「書き込み」権限が付与されていました。\n\n状況：システム設計上の欠陥。鍵1つで、当該口座の在庫および取引に対する完全な読み取り・書き込み権限が得られる。\nOWASP A07:2021 / セッション深刻度：高\n3. セッション管理の不具合\n\nサーバーをホストしているIPアドレス範囲から発信された、乗っ取られたWebセッションが継続しているとの報告がユーザーから寄せられています。通常、地理的な異常やパスワード変更があった場合にはセッションを終了させるのが一般的ですが、アーカイブに収集されたユーザー報告によると、パスワード変更後もセッションがアクティブなままだった事例が確認されています。\n\n状況：報告済みの不具合（アーカイブ内のユーザーからの苦情）。セッション中に、再認証を行わずにAPIキーが生成される可能性があった。\nドメインレベルのブロックは技術的に可能であった執行の実現可能性\n4. 認証ホストのドメインレベルでのブロックは技術的に可能であった\n\nValveはすでにドメインリスト（リンクフィルター）を運用しており、独自のOpenIDリクエストに含まれるすべての認証ホスト名を受信しています。 これら2つの仕組みは、外部から見ていかなる形でも関連付けられていません。2026-09-22の時点で、26組のペアにおいて、メインドメインはフィルタの対象となっていたものの、そのログイン情報を中継するプロキシは対象外となっていました。\n\nこれらを接続するのは、さほど難しくない作業です。以下の内容を参照してください。openid.realm 各着信リクエストのホスト名を取得し、リストと照合して、そのリクエストを拒否するか、フラグを立てる。右の図は、そのようなルーチンの構成を示している。公開ランディングページだけでなく、認証用ホストそのものを拒否すると、これらのプラットフォームが依存している「Steamでログイン」というステップが中断されてしまう。\n\nValveがそのような確認を行っていることを示す公的な証拠はありません。Steamコミュニティマーケットの合計手数料（約15%）は、マーケット内で成立した取引に適用されるものであり、これらのプラットフォーム外での取引に対しては徴収されません。\n\nblock_auth_hosts.pyイラスト\n// ホスト Steam がすでに受信しているデータを読み込む — スキャンは行わない\ndef on_openid_request(request):\nhost = parse_openid_realm(request)\nもし ホストin blocked_domains:\n（依頼を）断る\n注： これはあくまで説明用の擬似コードです。両方の要素はすでにValveに存在しています――リクエストには認証用ホスト名が含まれており、ドメインリストはリンクフィルターです。これらが結びついていない理由を説明する公開記録は存在しません。\n第5.1節 — これらの基準は未公表ではなかった\nValveは毎日、これらのルールに基づいてビルドを行っています。しかし、ここではそれらのルールに基づいてビルドされませんでした。\n\nSteamはApp StoreやGoogle Playで提供されており、主要なカード決済事業者を通じて販売を行っており、他の大規模プラットフォームと同様にサードパーティのAPIを利用しています。これらの各関係には、Valveが運営を継続するために満たさなければならない、公開され、日付が明記されたセキュリティ要件が定められています。 これらの要件の有効期限と、Steam自身のWeb APIが同等の保護措置を講じた日付とを照合してください。以下に記載されているものは、いずれも非公開の基準、社内メモ、あるいは企業秘密ではありません。すべての行は、公開日が明記された公開文書です。\n\n公表された外部セキュリティ要件とその日付、およびSteam Web APIが同等の管理措置を導入した日付との対比\n公表された規格およびその発効日\t同じ質問に関する Steam Web API\nスコープ付き承認OAuth 2.0 — RFC 6749、2012年10月. 第3.3節では、以下を定義している。scope そのため、クライアントは要求したアクセス権限のみを受け取ることになります。それ以来、これはすべての主要なプラットフォームのAPIにおけるデフォルトの設定となっています。\t粒度の細かいスコープが導入されたのは2026年1月16日.それ以前は、発行理由にかかわらず、1つの Steam Web API キーだけで、そのアカウントの取引に関する完全な読み取りおよび書き込み権限が与えられていました。13年3ヶ月 そのコントロールを定義する仕様の後に。\n鍵は認証ではないGoogleが提供するクラウドのドキュメント：標準のAPIキーでは、プリンシパルの認証は行われません、また、リソースを作成または管理するAPIについては、本番環境では認証キーを使用しないでください。\tその「0」というWeb APIキーは、まさにその通りでした。アカウントに発行される無記名文字列であり、これだけで在庫の照会、保留中の取引の取消し、および新しい取引の送信を行うことができます。使用時点では、発行者の本人確認は行われませんでした。\n特権アクセスにおける多要素認証PCI DSS 3.2、要件 8.3 — 適用開始日：2018年2月1日 コンソール以外からのすべての管理操作およびカード保有者データ環境へのすべてのリモートアクセスについて。その後、Appleはすべての開発者プログラムアカウント保有者に対し、2019年2月27日:開発者プログラムにおいて「アカウント所有者」の役割を持つ開発者は、ログインするために二要素認証を有効にする必要があります。\tAPIキーを作成するには、もう1つの要素が必要でした。2023年12月4日.それまでは、盗まれたセッションクッキーだけで事足りており、アカウント所有者の携帯電話に確認のメッセージが表示されることも、事後の通知が行われることもありませんでした。4年9ヶ月 Appleが、開発者ポータルへのログインだけでさえ、2段階認証の使用を義務付けた後。\n認証情報のライフサイクルと失効Twitchでは、すべてのサードパーティ製アプリケーションに対して以下の要件を定めています：アプリは、起動時およびその後1時間ごとにOAuthトークンの有効性を確認する必要があります。、また、その要件を満たさないアプリケーションについては監査を行うと明記しています。従来のv5 APIは、2022年2月28日 公表されたスケジュールに従って。\t鍵のライフサイクルに関する公開記録はありません。2023年の変更により、作成エンドポイントが保護されました。 この変更に関連して、すでに登録済みのキーを扱う「Valve」ステートメントは見つからず、変更に伴う変更履歴も一切公開されていません。この変更以前に作成されたキーが無効化されたかどうかは、公開データからは確認できません。これは、データ主体が、数年前に自身のアカウントで作成されたキーが現在も有効であるかどうかを知るために、回答を必要とする疑問です。\n建築ベンチマーク // トークン・アーキテクチャ\nGitHub のきめ細かいスコープと Valve Steam Web API の比較\n\nValve人の開発者が、きめ細かな「最小権限」トークンを用いて、GitHub上で日々オープンソースソフトウェアを管理しています。これに対し、1億3000万人のSteam人のプレイヤーには、単一のキーが発行されています。\n\nGitHubのきめ細かなトークン\nGitHubのValveさんが使用しています\n\nスコープによる分離とライフサイクルの強制的な適用を備えた、きめ細かなトークン。\n\nリポジトリへのアクセス：選択されたリポジトリのみ（1つ）\n権限の設定：読み取り専用 [✓]\nコードと秘密：アクセス不可 [✕]\n有効期限：30日間（TTL必須）\n監査ログの記録：IP、ユーザーエージェント、およびタイムスタンプ\nセキュリティ態勢： 最小権限トークンにより、被害は単一の読み取り専用リソースに限定されます。\n!Valve Steam Web API キー\n1億3000万人のユーザーに提供\n\n取引および在庫に関する権限のすべてを包括する、32文字の単一のマスター文字列。\n\nアカウントへのアクセス：完全なアカウント（モノリシック）\n取引管理：「読む」、「キャンセル」、「拒否」 [!]\n詳細なスコープ：なし（2026年に到着、13年遅れ）\n有効期限：NEVER（有効期限なし）\n監査ログ：なし（ユーザーのIP履歴はゼロ）\n脆弱性： 盗まれた鍵により、送信されるすべての取引オファーを誰にも知られずに傍受することが可能になる。\n一方向に適用される基準\n\nあるベンダー Valve が依存しているクラウドプロバイダー、決済処理業者、CDN などが、二要素認証のない認証情報エンドポイントを放置していたと仮定する。数か月後、そのエンドポイントで生成された鍵を通じて、Valve 自身の企業データが流出してしまった。 Valveは、リンクをクリックした者に過失があったと認めるだろうか？この資料に保存されている過去の拒否事例は、ユーザー側の立場から見た対称的な疑問に答えている。そこでは、アカウント所有者が鍵を作成した以上、損失の責任を負うという立場がとられている。このアーキテクチャについては、ある側面ではベンダーの責任、別の側面ではユーザーの責任であると説明されている。 どちらが正しいかというのは、技術的な問題ではなく、また本調査で決着をつけることのできない問題であり、裁判所や監督当局が判断することである。\n\n証拠ではなくイラスト――基準を逆方向に読み解く\nある決済処理業者は、第三者のスクリプトが、アカウント所有者への確認画面を表示することなく、ブラウザのクッキーのみを用いて、全権限を持つ取引認証情報を生成できるようにしていた。\nトークンが発行された経路を塞ぎ、すでに発行されたトークンについては一切公表しなかったIDプロバイダー。\nある銀行は、異議が申し立てられた送金について、使用された認証情報が顧客自身の口座に登録されていたことを指摘して対応し、その件を処理完了とした。\n\nこれらは、特定の企業に関する結論として提示されているものではありません。これらは、監督当局の対応が詳細に記録されている状況に置き換えた、同じ設計上の判断であり、規制当局にはまさにこの比較を行うことが求められているのです。\n\n記録から明らかになった事実： Steam Web API に欠けていた制御機能は、公開されていたものであり、時代遅れであったほか、いくつかのケースでは、自社製品の出荷を継続するために Valve が満たさなければならない条件も存在した。各標準と、それに対応する Steam の変更との間隔は測定可能であり、上記に示されている。しかし、その理由については明らかにされていない。 これらの区間のいずれについても、Valveの理由説明は見つかっておらず、ここではその理由を仮定することもない。その記録はValveの中に存在するが、公表されていない。\n\n出典（いずれも公開文書）：OAuth 2.0 —RFC 6749、2012年10月 ↗ ・Google Cloud —APIキーのドキュメント ↗ ・PCI DSS 3.2 要件 8.3 —PCI SSC リソースガイド ↗ ・Apple —アカウント保有者に対する二要素認証の義務化について（2019年2月20日） ↗ アーカイブ済み 2025-05-06 ↗ ・Twitch —トークンの有効性確認要件 ↗ そして、そのv5 サービス終了のお知らせ ↗ アーカイブ済み 2025-01-27 ↗. Steam自身の日付は、このセクションの更新記録に記載されているものです。2023年および2026年のエントリは、Valveが変更履歴を添付せずにリリースしたものです。2026-09-22を取得しました。\n\nValve自身の更新記録 — 日付付き、公開情報源より\n日付\tValve 変更\t発表された？\t何が閉鎖されたのか\tラグ：メカニズム（公開）→ 修正\t出典\n2026-09-01\t不審なチャットの自動フラグ付け\tはい\tグループチャット内の危険なリンクやパターン\t—\tニュース ↗\n2026-01-16\tSteamworks Web API のきめ細かなスコープ\tはい\t開発者キーの最小権限スコープ\t—\tお知らせ ↗\n2025-07-15\tCS2 トレードプロテクションとリバーサルウィンドウ\tはい\t何もない。 根本的なセキュリティ対策ではありません。サポート側によるアカウント復旧へのアクセス権限は変更されていません。取り消しを実行すると、自動的に30日間の取引停止措置が適用されます（Skinvault ↗)、一方、現物取引の急変により、時価総額は24時間で$104M（-25%）急落した（CSMarketCap ↗). 2026年には、タイマーがアイテムごとに設定されるようになった（Skin.land ↗).\t—\tよくある質問 ↗\n2025-05-14\tアカウントのセキュリティに関するお知らせ\tはい\tステラー／セッションハイジャックに関する指針\t—\tお知らせ ↗\n2024-10-02\tCS2「The Armory」7日間ホールド\tはい\tアーモリーアイテムの取引・市場を保留にする\t—\tお知らせ ↗\n2024-09-18\t新規端末でのログインに関する取引制限\tはい\t新しい端末での2～7日間の取引制限\t—\tよくある質問 ↗\n2024-02-14\tプロフィール名とアバターの変更保留\tはい\t名前変更後の取引には2～4時間のクールダウン期間があります\t—\t投稿 ↗\n2023-12-04\tAPIキーのモバイル認証\t変更履歴なし\tクッキーのみによるサイレントキー登録\t2017年頃のパネルから約6年後\t開発者向けページ ↗\n2023-10-24\tゲームビルドの公開におけるSMSによる多要素認証（MFA）\tはい\tSteamworksビルドの公開\t—\tお知らせ ↗\n2023-07-12\tカスタム経歴に関するコンテンツ警告\tはい\tプロフィールに記載されたフィッシングリンク\t—\tフォーラム ↗\n2023-01-25\tプロフィール {リンク削除済み} およびクールダウン\tはい\tプロフィール文内のリンク\t—\tよくある質問 ↗\n2022-10-24\tログイン機能の全面刷新とクッキーの切り捨て\t変更履歴なし\t無制限のセッション盗用\t— (IAuthenticationService トークンの移行)\tニュース ↗\n2022-10-12\tモバイルアプリ 3.0 QRコードログイン\tはい\tセッション認証解除パネル\t—\tニュース ↗\n2022-05-10\t取引キャンセル用のエンドポイントが削除されました\t変更履歴なし\tオファーの交換（キャンセルおよび再送信）\t2017年頃のパネルから約5年後\t第325号 ↗\n2020-05-25\tDota 2 7日間のトレードロック\tはい\t迅速なアイテム転売\t—\tブログ ↗\n2018-03-29\tCS:GO 7日間の取引ロック\tはい\tボットの即時洗浄\t2016年7月の声明から約20か月後\tブログ ↗ アーカイブ済み 2025-02-26 ↗\n出典：リンク先の Valve の投稿、ヘルプページ、および GitHub のイシュー（日付記載のもの）。 3つの決定的な修正が変更履歴なしでリリースされ（2022年5月、2022年10月、2023年12月）、Valveによる発表ではなくユーザーによって発見されました。この不均衡は、実施記録の一部となっています。 遅延は、資料自体に記載された日付（2016年7月の声明、2017年頃の詐欺パネル）が開始時点を示す場合にのみ算出される。「—」は、ここでそのような開始時点が確立されていないことを意味する。\nパートA — 技術記録・第6節\nインタラクティブなエクスプロイト＆ハイジャック・シミュレーター\n文脈と出典の制限\n\nフィッシングメッセージからサーバー側のキー登録、そして取引のスワップに至るまでの経路を再現したものです。2023年以前は、アカウントに登録されたWeb APIキーを使用して、そのアカウントの在庫情報を読み取ったり、保留中の取引オファーをキャンセルしたり、新しい取引オファーを作成したりすることができましたが、これらの操作のいずれにおいても、アカウント所有者に取引確認画面は表示されませんでした。 これは「最小権限の原則」の欠如（OWASP A01:2021）にあたります。このシミュレーションにおけるタイムスタンプはあくまで例示であり、現在のプラットフォームにおける実際の測定値ではありません。\n\n再現されたハイジャックの手順を順を追って確認してください。各段階では、アカウント所有者に表示される内容と、その横に、その瞬間に「Steam」宛てに受信される通話内容が表示されています。それらの通話はいずれも正しく認証されています。 この一連の処理において、失敗するためにSteamの認証が必要となる部分は一切ない。必要なのは、Steamが発行する鍵にスコープが含まれていないことである（OWASP A01:2021）。\n\nプレイヤーが見ているもの。その背後で何が変化しているのか。ウォークスルー・シミュレーター\nステップ 5 / 5\n\nエクスプロイトが完了しました。 被害者は、当初の取引に関するモバイルプンプトが表示されるものと期待していたため、代替取引を承認してしまいました。これは、「最小権限の原則」（OWASP A01:2021）が遵守されていないことが、1秒未満で資産を乗っ取る自動化された攻撃を可能にする仕組みを解説した、統合的なフォレンジック・ウォークスルーです。\n\n01 / チャット・ルアー友人が投票をお願いしてくる被害者は、リンクが記載されたメッセージを受け取ります。\n02 / ログインそっくりなポータルサイト被害者がログイン情報を入力する。\n03 / アクセスサイレントWeb APIの作成攻撃者が開発者キーを登録する。\n04 / スイッチ正当な取引がすり替えられた「Clone bot」は、対象の受信者を複製します。\n05 / 確認偽造品として承認済みモバイル端末で誤ったオファーが承認されてしまいました。\nネットワークの観点から見た、同じ手順2023年以前のパターンの再現・参考となるコール形状\n被害者当初の取引で想定されていたモバイル用プロンプトを承認します。\n攻撃者クローンアカウントでアイテムを受け取ります。\nSteam 回閲覧登録済みの端末上で、口座名義人によって確認された振替。\nConfirmation genuine — made by the account holder\nRecipient the clone bot, not the intended counterparty\nThe confirmation is authentic. The offer it confirms is not the one the user initiated.\n\n残された記録： ユーザーが承認した取引。これが、苦情が寄せられた際に「Steam Support」が参照する記録であり、アーカイブされた苦情が「ユーザーエラー」として処理された理由でもある。これらの苦情は執行記録.\n\nパートA — 技術記録・第7節\nシーケンスの背後にあるエンドポイント。\n文脈と出典の制限\n\nこれらは、報告されたハイジャックスクリプトが、ブラウザ側の確認手順を経ずに取引を傍受するために使用した Steam 個の Web API エンドポイントです。\n\n文書化された4つのエンドポイントだけで、すべての処理を完結させることができます。そのいずれも欠陥ではなく、悪用する必要もありません。有効なキーがそれらを呼び出すと、Steamが応答します。攻撃者が盗む必要があったのは、その鍵だけだった。\n\nIEconService / GetTradeOffers / v1投票\n\nアカウントの取引オファーを監視するために使用されます。スクリプトは、不正に入手したAPIキーを使用してこのエンドポイントを繰り返しポーリングし、新規作成された、保留中の、または変更された取引オファーの詳細を取得します。ここではポーリング間隔は測定されません。\n\n脅威ベクトル： 保留中の取引オファーのIDと、受信者のプロフィール詳細を表示します。\nIEconService / CancelTradeOffer / v1相互作用\n\nユーザーの正当な取引オファーをプログラムによって無効にするために使用されていました。2023年以前は、鍵を保護する多要素認証が導入されていなかったため、自動化されたサーバーは、オファーが検出されるとすぐに、アカウント所有者への確認画面を表示することなく、そのオファーをキャンセルすることができました。\n\n脅威ベクトル： 口座保有者がモバイル確認を完了する前に、取引を無効にします。\nISteamUser / GetPlayerSummaries / v2RECON\n\n正当な取引相手のプロフィール名、アバター画像のURL、およびレベルを取得するためのクエリを実行しました。これにより、スクリプトは用意しておいたクローンアカウントをその相手に合わせるように設定できます。ここでは所要時間は計測されていません。\n\n脅威ベクトル： 宛先となる受信者を装うために必要なデータを提供します。\n/dev/ajaxregisterkeyCREATION\n\nSteamのキー登録エンドポイント。従来、アクティブなブラウザのクッキーセッション（`steamLoginSecure`）であれば、モバイル端末でのSteam Guardによる確認や、アカウント所有者への通知なしにキーを登録することが可能でした。\n\n脅威ベクトル： スクリプトによって作成され、アカウント所有者には見えない永続的な認証情報。\nパートA — 技術記録・第8節・GDPR第7条\nチェックが入ったボックス。誰の操作？\n文脈と出典の制限\n\n払い戻しを拒否する際、アーカイブに保存されているサポートの回答では、アカウント所有者がAPIキーを作成し、チェックボックスにチェックを入れることで利用規約に同意したとの立場をとっています。\n\nサポートの回答では、その鍵はアカウント所有者に帰属するとされています。問題は、その記録から、実際に誰がそれを作成したのかが判明するかどうかです。\n\nしかし、確認されたAPIキーの乗っ取りの手口では、被害者はAPIキーの作成ページを閲覧したり、そのページにアクセスしたりしたことは一度もありませんでした。同意の入力内容は、盗まれたセッションクッキーを使用してヘッドレスPOSTを実行するスクリプトによって送信されています。\n\nGDPR第7条および第4条(11)に基づき、同意とは、データ主体が自由意志に基づき、具体的かつ十分な情報に基づいて、かつ曖昧さのない形で意思表示を行うものでなければならない。 著者らの見解では、盗まれたクッキーを用いて悪意のあるスクリプトによって送信され、アカウント保有者にページが表示されない状態でチェックされた利用規約への同意欄は、この定義を満たすことはできない。それが定義を満たすかどうかは、監督当局の判断に委ねられる。\n\nフォレンジック・ペイロード解析：キーの登録\n投稿 https://steamcommunity.com/dev/ajaxregisterkey\n// リクエストペイロード（ハイジャックスクリプトを介して注入されたもの）\n{\n\"agreeToTerms\":「了解」,<-- 機械による自動入力、人間の介入なし\n\"ドメイン\":「localhost」,← 検証なし — 任意の値が受け入れられます（localhost を含む）\n\"sessionid\":\"8f0d8ef763ab2140bf89de2a\"\n}\n監督当局への質問： 口座名義人が同意欄をクリックしたことがない場合、当該口座に対して記録された利用規約への同意が、第7条が定める「データ主体の意思の自由な表明、具体的かつ情報に基づいた、かつ明確な意思表示」という要件を満たしているかどうか、また、Steamサポートがこれを根拠として請求を拒否することができるかどうか。\n\n出典：公開エンドポイントおよび証拠アーカイブに保存されているハイジャック報告から再構築された、キー登録のリクエスト形式（検索可能なビルド 2026-09-17) ・表示されているセッション識別子はプレースホルダーであり、取得された値ではありません。\n\n法医学的剖検・代替品ベクトル\nValveが「貿易代替」をどのようにして最終的に解消したか――そして、なぜ7年もの間、その場しのぎの対策が続いたのか\n\nここ10年近く、その「APIキーのすり替え」（またはAPI中間者攻撃詐欺） これはSteamにおいて最も収益性の高いアカウント盗難の手法であり、何も疑わないプレイヤーから数億ドル相当のスキンを搾取していた。 Valveは、脆弱なAPIアーキテクチャを修正してこの悪用を根絶することはなかった。その代わりに、Valveは7年をかけて、プラットフォーム全体に4つの摩擦障壁を段階的に導入したが、これはコミュニティ内の取引流動性を著しく損なう一方で、根本的な原因には手を付けなかった。\n\n1. ミミクリーの死\nアバターと名前のクールダウン（2024年2月）\n\nこの攻撃には、1秒未満での模倣が必要でした。詐欺ボットは送信される取引を傍受し、受信者のアバターや名前をISteamUser、そして200ミリ秒でそのプロファイルを複製した。2024年2月14日、Valveはひそかに強制的な措置を実施した。2～4時間の取引クールダウン（エラー34） プロフィール名やアバターを変更した直後。ボットは、取引から締め出されることなく、その場で受信者を複製することはできなくなりました。\n\n2. 経済的死\n7日間のCS2トレード反転（2025年7月）\n\nValveが一方的に導入したトレンドの反転 『Counter-Strike』のアイテムについて。取引されたスキンはすべて、7日間「取引保護」のタグが付与されます。 被害者がアイテムのすり替えに気づいた場合、Steamサポート内の「取引の取り消し」をクリックすると、スキンは即座に自身のインベントリに戻され、受取人は凍結されます。7日間の取引ロックにより、詐欺師がアイテムを現金化サイトへ移動させることを防ぐため、この盗難は利益を生むことができません。\n\n3. サイレント・キーの死\nAPIにおけるモバイルプッシュ通知の義務化（2023年12月）\n\nこれまで、セッションクッキーが盗まれると、悪意のあるスクリプトがヘッドレスなバックグラウンドPOSTリクエストを実行して/dev/ajaxregisterkey 被害者に通知することなく。2023年12月4日、Valveは、Web APIキーを生成する際にSteamモバイルアプリで明示的なプッシュ通知の確認を義務付け、バックグラウンドでの無通知のキー発行を廃止しました。\n\n4. アプリ内モバイル警告\nアカウントの開設期間と名前が入ったバナー（2022年～2024年）\n\nValve モバイル版の確認モーダルを刷新し、取引相手のSteam 口座開設日（作成日）, Steam レベル、および明示的なアンバー警告：「このユーザーは最近、プロフィール名を変更しました」、注意深い被害者にとっては、その視覚的な錯覚が崩れてしまう。\n\nValveのパッチワークに見られる3つの欠陥：詐欺師たちが単に標的を変えただけの理由\n1. ゲーム除外に関する抜け穴（Dota 2 および TF2）\n\n「トレード・リバーサル」は、『カウンターストライク2』専用に導入されました。『Dota 2』および『Team Fortress 2』のアイテムは、依然として全く保護されていない状態にある クラフトやソケット設定の複雑さによるものです。数千ドル相当の高級アイテム（ドラゴンの爪のフック、ゴールデン・ベイビー・ロシャン、珍しいTF2の燃え盛る炎など）には、取引取り消し期間が一切ありません。 詐欺師たちは、自動化されたAPI傍受を単に『Dota 2』や『TF2』のトレーダーへと転用しただけであり、そこではSteamサポートが2016年の「アイテム復元不可」ポリシーを厳格に適用している。\n\n2. 「ゾンビキー」リザーバー（有効期限なし）\n\nValveは、モバイルプッシュ型2段階認証を追加して生成した新着 2023年12月に鍵を、Valve 既存のレガシーAPIキーが、一度も取り消されたり、有効期限が切れたり、削除されたりしたことがない. キーを生成した（あるいは2023年12月以前にフィッシングやマルウェアによって密かにキーが作成されていた）数百万のアクティブなアカウントには、依然として有効な認証情報が保持されており、有効期限なし（TTLなし）かつ非アクティブタイムアウトなし. 脅威アクターは、こうした永続的なキーに関する膨大な履歴データベースを維持しており、引き続きポーリングを続けていますIEconService 何事もなく。\n\n3. 被害者への罰則：30日間の取引停止\n\nCS2においても、Valveでは騙されたプレイヤーにペナルティが課されます。Steamの「サポート」で「取引を取り消す」をクリックすると、自動的に被害者のアカウントに対し、30日間の取引およびコミュニティマーケットの利用禁止措置を課す. Valveは、「軽率な」取引取り消しに対する抑止策として、ユーザーに対し1か月間のプラットフォーム利用停止処分を科し、被害者が価値の低い流動性の高いアイテムの取引を取り消すことを思いとどまらせるようにしている。\n\n規制をめぐる核心的なスキャンダル：7年間にわたる抜け道対策対1つのAPIスコープ\n\nなぜValveは、業界標準の修正策を導入する代わりに、7年もの歳月をかけて取引保留、アカウントのクールダウン、および解除可能な取引ロックといった仕組みを考案し、ゲーム経済全体を混乱させ、時価総額$104Mを吹き飛ばしてしまったのだろうか？\n\n2026年1月16日に『Valve』がSteamworksを通じて正式にリリースされたことからも明らかなように（発表#493839547938902179 ↗), Valve はすでに建設済み詳細な権限グループ（一般、マイクロトランザクション、経済、販売データ） そしてIPのホワイトリスト登録 法人向けパブリッシャーキーについて。Valveは、この技術的な解決策を何年も前から手元に持っていた。ユーザー向けのチェックボックスが1つ――「この Web API キーが IEconService（トレード管理）にアクセスできないようにする」 あるいは、家庭用IPアドレスのホワイトリストといった措置があれば、2018年の取引代替詐欺を、経済的な副次的被害を一切生じさせることなく根絶できたはずだ。Valveは、企業パートナーのために構築した保護措置を、一般のプレイヤーには適用することを拒否した。\n\nパートB — 規則および執行実績・第9条\n彼らのルールブック。記録されたプラットフォーム。\n文脈と出典に関する制限\n\nこの元帳は、Steam 加入者契約（SSA） そしてSteam オンライン上の行動規範（SOC） 活動中の大規模な営利事業体を直接対象としたガイドライン。\n\nルール： 「商用利用禁止、ギャンブル禁止、ボット禁止」――そして、Steamサポートは、被害者のアイテムの返還を拒否する際、これらの条項を引用している。記録： これらの条項は、その文言上、この登録簿に掲載されている商業プラットフォームを対象としており、それらは Steam のID、Steam のボット、および Steam の転送に基づいて運営されています。この条項は、皮を紛失した人物に対して適用されるものであり、公表されている記録によれば、皮を輸送した事業者に対しては適用されない。\n\nアーカイブされた苦情の中で、Steam Support は以下の点を挙げています。「商用利用禁止」 そして「自動化・ボット禁止」 APIキー詐欺の被害者に対するアイテムの復元を拒否する際の条項。これらの条項は、表面的には、本報告書に記載された商用プラットフォームにも適用される。これらのプラットフォームは、Steam OpenID を通じて認証を行い、自動化された Steam アカウントを介してアイテムを移動させている。 ここでは市場全体の収益額については推計していない（以下の執行統計を参照）。記録が示しているのは、アーカイブされた事例における個々のアカウントに適用された規則であり、各プラットフォームごとの事業者別執行記録は公表されていない。このセクションでは、その非対称性について検証している。\n\n核心となる問題／選択的執行ルール → 規模 → 説明責任\nルールブックは一つ。しかし、その適用にはばらつきがある。\n\n登録簿によると、商用サービスは、SteamのID、インベントリ、ボット、および転送を運用インフラとして利用していることが示されています。SSAは、許可のない商用利用および自動化を禁止しています。アーカイブされた苦情記録によれば、この規則は個々のアカウントに適用されていたことがわかりますが、公開記録には、ここで記載されているプラットフォームについて、事業者ごとに同等のアカウント情報が示されていません。 各事例について、規則、証拠、および執行決定を公開してください。\n\n189監査対象のウェブサイト\n44ライブレジスタに登録されている別ドメインのルート — 公開された証拠ファイルがあるものが27件、手動で収集されたものが17件。189件のウェブサイトに対するブラウザ監査だけで、そのうち25件が解決され、レジスタには手動で収集されたルートが追加されている。\n12歳6ヶ月csgogem.com がリンクフィルターでブロックされました；api.csgem.com 登録日 2014-03-08、ブロック歴なし — 2026-09-22時点での26組のうちの1組\n確認済みの合計数なし市場全体の売上高予測は除外\nSteam オンライン上の行動規範\n「…Steamにおいて、以下の行為を行ったり、行おうとしたりしてはならない：[…] 営利活動に従事すること。このような禁止行為の例としては、広告の掲載、コンテストの開催などが挙げられる；ギャンブル; Steamアカウントの売買、コンテンツやギフトカード、その他のアイテムの販売、および物乞い。」\n\nstore.steampowered.com/online_conduct ↗ アーカイブ済み 2026-09-21 ↗\n\nSSA 第2.G条 — 商用利用\n「…本契約の他の条項で明示的に許可されている場合を除き、コンテンツおよびサービス、またはその一部を商業目的で利用してはなりません…」\n\n報道されている通り、Valveの2016年の通知では、個人かつ非営利目的のライセンスが適用されていました。記録上、Valveの認可を提示した事業者は1社もありません。store.steampowered.com/subscriber_agreement ↗ アーカイブ済み 2026-09-18 ↗\n\nSteam Web API 利用規約\n「Steam Web API または Steam データは、Steam 利用規約に違反する方法で利用してはなりません。」\n\nサードパーティのスキンマーケットプレイスは、Steam APIを利用する自動アカウントを通じて運営されています。この規則の文言には、商業規模に関する例外規定は一切含まれていません。steamcommunity.com/dev/apiterms ↗ アーカイブ済み 2026-09-21 ↗\n\nSSA 第4.C条\n自動化\n\nスクリプト、ボット、および人間以外の主体による取引は制限されています。この台帳には、ボットによる取引、アカウントファーム、および商業規模での自動ルーティングが記録されます。\n\n点検する153この条項のタグが付けられたレコード↗\n本条項に基づき記録に何が記載されるか153 タグ付けされたプラットフォーム\nケースの開封15\nスキン・カジノ13\nCS2マーケット9\nスキン・ルーレット8\ncsgoempire.com→csgoempirelogin4.comカジノ\nrollbit.com→rbsnin.com暗号資産カジノ\n500.casino→fivezerozero.co認可を受けたカジノ\n\nこのうち、 153 また、SSA第2.G条および 2 また、SSA第1.C条にも分類されています。同じサービスが複数の条項に該当するため、 例が重複しています。\n\n28 153の 個別の登録可能なドメインを通じて認証が行われていることが確認されました。タグには日付付きの 観察記録が記載されており、その内容から判断すると、当該プラットフォームは条項の適用対象となります。ただし、これは 裁定された違反ではなく、いずれについてもValveの認可が提示されていません。\n\nSSA 第2.G条\n商用利用\n\n商業利用には明示的な許可が必要です。文書化されたビジネスモデル、その規模、および開示されている認可や執行状況などを比較検討してください。\n\n点検する175この条項でタグ付けされた記録↗\n本条項に基づき記録に何が記載されるか175 タグ付けされたプラットフォーム\nケースの開封15\nスキン・カジノ13\nCS2マーケット9\nスキン・ルーレット8\ncsgoempire.com→csgoempirelogin4.comカジノ\nrollbit.com→rbsnin.com暗号資産カジノ\n500.casino→fivezerozero.co認可を受けたカジノ\n\nこのうち、 153 また、SSA第4.C条および 24 また、SSA第1.C条にも分類されています。同じサービスが複数の条項に該当するため、 例が重複しています。\n\n28 175の 個別の登録可能ドメインを介した認証が確認された。タグには日付付きの 観測記録が記載されており、その内容から判断すると、当該プラットフォームは条項の適用対象となる。ただし、これは 裁定された違反ではなく、いずれについてもValveの認可は提示されていない。\n\nSSA 第3.A条\nVPNと位置情報の偽装\n\nIPプロキシを使用して居住地を偽装すると、サービス利用停止処分につながる可能性があります。別ドメインの認証ホストについては、個別に分析を行う必要があります。つまり、何が偽装されているのか、どのルールが適用されるのかを明確にする必要があります。\n\nauth-host の証拠を確認する↗\nSteam ヘルプ / URLに関する方針\nリンクの難読化\n\nSteam では、リンク短縮サービスやリンク先を不明瞭にするツールの使用が禁止されています。別の認証ドメイン —rbsnin.com Rollbitのログインフローでは、auth.dota.trade CS.MONEYの事例では――、SteamのOpenID検証者に表示される宛先が、実際に運営されているサイトを特定しているのかという、同様の疑問が生じます。\n\nValveのURLポリシー ↗\n\n関連規則：Steam 加入者契約、2026年9月10日改訂版 アーカイブ済み 2026-09-18 ↗ ・Steam Web API 利用規約 アーカイブ済み 2026-09-21 ↗ ・Steam URLポリシー（リンクの難読化）. カウントは、この書類に含まれる記録やタグの数を表すものであり、裁定済みの違反件数の集計ではありません。\n\n信頼の欠如\nサポートが案件をクローズした際、その決定を誰が審査するのですか？\n\n保存されている苦情には、恒久的な制裁措置、回答のない異議申し立て、盗まれたアイテムの返還拒否などが記載されています。これらの報告内容を、実際のチケット履歴、利用可能な救済措置、およびアカウントアクセスログと照らし合わせて検証してください。一般的なフィッシング攻撃による説明だけでは、誰がリセットを実行したのか、あるいは誰がAPIキーを作成したのかを特定することはできません。\n\n寄せられた苦情を読む ↗関連する記録を請求する →モデレーターの関係図 →\nパートB — 規則および執行実績・第10条\n自動化用API。自動化を禁止するルール。\n文脈と出典の制限\n\nこのセクションが提起する問題は、この2つをどのように調和させるか、すなわち、APIのどの利用が許可され、誰によって、またどのような公表された基準に基づいて許可されるかという点である。ここでは、許可された商用API利用者の数については推定しておらず、また、公表されたリストが存在しないことから、そのような数が示唆されているわけでもない。リストが存在しないこと自体が調査結果であり、その背後にある数値ではない。 上記で引用したSteamのサポートメッセージは、ArchiSteamFarmプロジェクトが独自のFAQに転載したものです（逐語的に確認済み2026-09-22）。これらはValveの出版物ではなく、送信先のアカウントも特定されていません。\n\n規則（SSA § 4.C）： Steamでは、スクリプト、ボット、および人間以外のシステムは一切禁止されています。記録： Valve は、サーバー間自動化のみを目的としたヘッドレス REST API を提供しており、どのアカウントに対してもそのアクセス権を付与します。自動化を行ったユーザーは利用停止処分となります。この自動化インターフェースはValve独自の製品です。 どのような商用利用が許可されているかについては、これまで公表されたことがない。\n\n「ゲーム開発者」という誤謬\nSteamworks SDK（正規版）\n\n正規のゲームスタジオが、実績、マッチメイキング、リーダーボードをゲームクライアントに組み込むために利用しています。複雑なC++による統合と、公式パートナーとしての登録が必要です。\n\nSteam Web API（抜け穴）\n\n外部のWebサーバー向けに設計された、ヘッドレスなJSON/RESTアーキテクチャ。ここで解説する「ハイジャック・パターン」では、リモートサーバーから在庫情報を読み取り、ピアツーピア取引を操作するために使用される。その正当な用途については、本資料には記載されていない。\n\nその鍵は誰のためのものか通常のSteamユーザーにとって、クライアント側でWeb APIキーを必要とする場面はありません。キーのページは開発者向けURLの下にあり、その目的は外部からのサーバーサイドアクセスであると明記されています。アーカイブされた乗っ取りに関する苦情によると、被害者の多くは、自分のアカウントにキーが登録されるまで、そのページの存在を知らなかったとのことです。\n自動化の矛盾\n\nSSA第4.C条には、次のように規定されている：「いかなる形式のスクリプト、ボット、マクロ、またはその他の人間による制御を受けていないシステム（以下「自動化システム」といいます）も、Steam上のコンテンツおよびサービスと何らかの形でやり取りするために使用してはなりません。」 しかし、Web APIのエンドポイント（例えばCancelTradeOffer) 人間によるUI操作やキャプチャを必要とせず、Steamクライアントを完全にバイパスします。このAPIはサーバー間での自動化を目的として設計されており、ユーザーによる自動化は禁止されています。この2つの境界線については公表されていません。\n\n取引フローにおけるサーバーサイドの役割\n\nWeb APIキーを使用すると、サードパーティのサーバーは、クライアントなしでアカウントの取引を実行できるようになります。「ハイジャック」パターンでは、そのサーバーがアカウント所有者と取引サーバーの間に位置します。\n\n→キー操作に対しては、取引確認画面は表示されません。\n→バックグラウンドでのポーリング（GetTradeOffers）を有効にします。\n→ユーザーの操作を必要とせずに、オファーをキャンセルし、再発行します。\nValveはインターフェースを構築し、その利用規約においてユーザーによる自動化を禁止しており、どのような商用利用が許可されるかについての基準を公表していない。\nパートB — 規則および執行実績 · 第11条\n10日間が求められた。10年分の説明が必要だ。\n文脈と出典の制限\n\n2016年7月20日、Valveの法務担当役員は、ギャンブル事業者に対し10日間の期限を提示した。 それから10年後（本資料のスナップショット時点、2026-09-21）、その通知に関する報道で名指しされたプラットフォームのうち少なくとも1つ、CSGOFastは、別のドメインの認証ホストを使用して現在も運営を続けている。以下の文言は、2016年7月21日の報道記事から再構成したものであり、スキャン画像ではない。 当該通知が示唆していた執行記録は公表されていない。委員会宛ての公開書簡は第2節.\n\n後述の所見の横にある2016年7月の通知をお読みください。現在、各事業者ごとの執行実績の記録が未提出となっています。\n\nその1週間前――2016年7月13日、公の場で\n\nについて2016年7月13日 アーカイブ済み 2026-09-21 ↗, Valveは、ギャンブルサイトがアカウントの識別にはSteamであるOpenIDを、取引には自動生成されたアカウントを利用していたことを説明した。Valveは、これらの仕組みを用いてギャンブル事業を運営することは、同社のAPI利用規約および利用規約に違反すると述べた。その仕組みの説明も禁止事項も、Valve自身が日付を明記した声明の中に記載されている。 2026-09-21 において、テスト対象となった別ドメインの認証ホストからはリンクフィルタのブロックは返されず、Valve は事業者ごとの適用レコードを公開していません。\n\n別紙A / 7月2016組版による再構成\nバルブ・コーポレーション\n\nワシントン州ベルビュー\n\n日付：2016年7月（2016年7月21日付報道）\n差出人：カール・クアッケンブッシュ、法務総責任者\nRE:差止請求 — Steamアカウントの商用利用\n注：報告されたテキストの再現。スキャン画像ではありません。\n\n「貴社が、以下に挙げるギャンブルサイトの1つを運営していることを承知しております。 貴社は、この事業を行うために Steam のアカウントを使用しています。Steam の利用規約に基づき、Steam および Steam のサービスは、個人的かつ非営利目的での利用にのみライセンスが付与されています。」\n\n「貴殿は、商業目的でのSteamアカウントのさらなる利用を直ちに中止し、これを行わないよう求めます。もしこれに従わない場合は、10日以内, Valveは、お客様のアカウントの解約を含む（ただしこれに限定されない）あらゆる利用可能な救済措置を講じます。\n\n資料の再構築・原記録を参照する\nカール・クアッケンブッシュ\nValve社 法務担当役員\n「余白」／社説\n10日間。それじゃあ、どうするの？\n\n期限は明確に定められていた。国民による対応も、同様に明確であるべきだ。\n\nValveが公表した「2016」に関する見解 ↗\n締め切りに関するお知らせ +\n風刺／『バルブ』誌への投書ではありません\n\n締め切り様、\n\n君には10日間の猶予が与えられた。どういうわけか、カレンダーだけが唯一、正常に機能し続けていた。\n\nご返信は、公開記録へ転送してください。\n\n年表2016年7月 – 2026年9月\n通知に記載されている締切日：\n10日間\n2016年7月\n通知からの経過時間：\n3,715 日\n2016年7月20日から2026年9月21日の資料スナップショット時点までの集計値であり、リアルタイムの数値ではありません。\n公表された執行記録：\nなし\nオペレーターごとの通話の切断や通話遮断に関する記録は見つかりませんでした\n\n◀0～10日目 — 締め切り、拡大表示3715日目 — スナップショット ▶\n\n2016年7月20日10日間の要求が発出された0日目\n2024年2月17日DSAの義務が適用されます0日目\n2026年2月25日ニューヨーク州司法長官による提訴が発表された0日目\n2026年9月21日資料の概要3715日目\n\nそれから10年後、CSGOFast — 2016年の通知に関する報道で名指しされた — は稼働中である：csgofast.com は 2026-09-19 および 2026-09-21 に対して Link Filter によるブロックを返した一方、その認証ホストはsteam-login.authtofast.com (登録番号 2026-06-30) はそうしなかった。\n\nValveのセキュリティ変更に関する完全な日付付き記録：セキュリティの沿革 → ・ワシントン州の記録と執行基準：以下\n\n記録によると： 2016年の通知では10日間の期限が設定されました。Valveはすでにドメインリスト（Link Filter）を運用しており、自社のOpenIDリクエストにおいて認証ホスト名を受け取っていました。事業者ごとの施行記録は公表されていません。 コミュニティの報告では、2018年にマーケットプレイス（SkinJar）に対して措置が講じられたとされているが、それらの報告は未確認であり、本稿ではそれらを根拠としていない。\nCSGOFAST / 保存された認証経路\n宣言されたリターンホストに従ってください。\n\n保存されたルート記録へのリンクcsgofast.com ～へsteam-login.authtofast.com. 個別のホスト名は、SteamのOpenIDリクエストに含まれています。これにより、調査担当者は、Valveのフィルタリングおよび執行記録と照合するための具体的なアドレスを得ることができます。\n\nCSGOFastのルートとそのソースを確認する ↗ ・保存済み Steam を比較 リンクフィルターの結果 ↗\n\n公文書 / ワシントン · 2016年 → 2026年\n2つの期限。1つの未解決の執行基準。\n7月20日\nValveはギャンブルサイトに10日間の猶予を与える\n\n同社の弁護士からの要求書では、Steamアカウントの商業利用を継続した場合、契約解除につながる可能性があるとの警告がなされた。\n\n9月27日\nワシントンが圧力をかける Valve\n\n同州のギャンブル委員会は、ギャンブル目的のスキン譲渡を阻止するための措置に関する証拠の提出を求め、回答期限を10月14日と定めた。\n\n10月17日\nValve はその容疑を否認した\n\nValveは期限を過ぎて回答し、ギャンブルを助長したとの指摘を否定するとともに、関連アカウントを無効化したとし、すべてのユーザーに対して取引機能やOpenIDを停止するつもりはないと述べた。 7月の通知に関する報道で名指しされたプラットフォームのうち少なくとも1つ（CSGOFast）は、10年後も運営を続けていた。これらの事実の両方が成り立つのは、運営者が無効化されたアカウントを代替したケースに限られるが、それを裏付ける記録は公表されていない。WSGCはValveに対し、この2つの事実の整合性を説明するよう求めるべきである。\n\n2026年\n2026年9月に観測された航路\n\nルートレジストリには、2016年に説明されたOpenIDおよび取引メカニズムValveを用いて、CSGOFastを含む別ドメインの認証ホストを介して認証を行う44のプラットフォームが記録されています。どの事業者が接続を遮断されたかを示す執行記録は、まだ提出されていません。\n\n委員会独自のブリーフィング · 2018年1月30日\nValveが回答してから18カ月が経過しても、規制当局は依然としてそれを「意図」と見なしていた。\n\nHB 2881に関する公聴会で州議会に対し説明を行った同委員会は、2016年7月の声明について、次のように自らの言葉で説明した：Valve「同社のプラットフォームがスキン賭博の手段として利用されることに対し、取り締まりを強化する意向を発表した。」 そのページには、その発表が業界の予測にどのような影響を与えたかが記されている――「その結果、」 2020年のスキンギャンブル市場の予測値は、$19.7十億 ～へ$670百万、この発表だけで約97％の削減となった。予測は変更された。これを裏付けるべき事業者ごとの執行実績は、依然として公表されていない。\n\n市場に関する数値は、委員会によるブリーフィング資料に掲載されたNarus Advisors／Eilers & Krejcik Gamingの推計値であり、委員会の調査結果ではない。同資料によると、2016年のスキン賭博の規模は約$5十億で、そのうち約$3十億がカジノ形式のサイトで行われたものである。 取得日時 2026-09-22、SHA-256c507c9025f93da0aadaf395c4d8882f25973211c318ee8e9b6f18a5b3755e050.\n\nValveが2016年に公表した見解と、現在確認できるインフラを並べて比較することができる。問題は、規制措置が、禁止対象の事業者が利用していたアカウントやルートにまで及んだかどうかである。10日前の通知があったからといって、その通知が通知対象として指定された事業者全員に対して行われたことを示す証拠にはならない。 2018年のOPSkinsに対する措置は、特定のオペレーターに対して行われた唯一の記録された介入事例である。調査対象となった189のプラットフォームに対し、オペレーターごとの記録が公表されていないことを踏まえると、1件の記録された措置だけでは、取り締まりの傾向を示すものではない。\n\nワシントン州ギャンブル委員会の2016年の通知 ↗ アーカイブ済み 2026-05-20 ↗ ・Valveによる2016年10月17日の回答（文書の写し） ↗ ・WSGCによる州議会への説明資料、2018年1月30日（ローカルコピー、4ページ） ↗ ・wsgc.wa.gov にある同じファイル ↗ ・検索レコードとハッシュ ↗ ・Valveの2018年OPSkinsでの活躍 ↗ アーカイブ済み 2026-03-07 ↗ ・現在のルートの監査 ↗\n\n法医学的縦断的監査・2016年の差止命令対象\n「10日前の通知」の10年間：指定された23カ所に対する法医学的サバイバル監査\n\n2016年7月19日から20日にかけて、Valveの法務担当役員カール・クアッケンブッシュ氏は、23のスキンギャンブルプラットフォームに対し、Steamアカウントの商用利用を中止するよう命じる正式な差止通知を発出した。10日間 アカウントの停止や法的措置をちらつかせながら。3,700日以上が経過した後、実証的な監査によって、実際の取り締まりの実態が明らかになった。複数の事業者は一度も運営を停止しておらず、他の事業者は期限後も最大6年間運営を続け、数十億ドル規模のエコシステムはValveのOpenIDアーキテクチャを引き続き活用し続けていた。\n\n5+ LIVE\n2026年には確実に稼働予定（CSGOBig、CSGO500、CSGOFastなど）\n6年\n閉鎖までの通知後の最長運営期間（CSGOatseは2022年まで稼働）\n$5.01B\n2016年のスキン賭博の取引高（Narus / Eilers & Krejcik）\n200以上\n市場のピーク時に運営されているアクティブなオンラインギャンブルサイト\n『サバイビング・タイタンズ』・2024～2026年 財務・トラフィック戦略計画\n「10日前の警告」から海外複合企業まで：数十億ドル規模の取引\n\nスキンギャンブルを根絶するどころか、Valveの2016年の通達は、業界の変革を加速させた。 生き残った事業者は、オフショア法人（キュラソー、ベリーズ、キプロス）として再編し、ボット禁止措置を回避するためのピア・ツー・ピア（P2P）取引を開拓し、現在では月間1,000万回のウェブアクセス そして年間賭け金総額が数十億ドル Steamを介して認証を継続しながら：\n\nプラットフォーム／ドメイン\t2016年7月のお知らせ\t執行結果および生存状況\t記録された検証／主要リンク\nCSGOBig\ncsgobig.com\t10日前の通知（2016年7月）\t2026年になってもまだ生きている\n一時的に停止され、再開されました。letmeinbig.com および csgobiglogin.com を通じて認証が行われます。\tX: @csgobig ↗ ・FB：csgobigofficial ↗\nCSGO500\ncsgo500.com / 500.casino\t10日前の通知（2016年7月）\t2026年になってもまだ生きている\n「500 Casino」（キュラソーライセンス番号 #8048/JAZ2014-037）としてブランド名を変更、月間売上高は数百万規模\tライブプラットフォーム (500.casino) ↗\nCSGOFast\ncsgofast.com\t10日前の通知（2016年7月）\t2026年になってもまだ生きている\nsteam-login.authtofast.com を通じて、ルーレット、クラッシュ、ジャックポットを積極的に運営しています。\tドシエ認証監査 ↗\nCSGOLounge / Dota2Lounge\ncsgolounge.com / dota2lounge.com\t10日前の通知（2016年7月）\t2026年になってもまだ生きている\neスポーツのコイン賭けや仮想通貨ベッティングへと事業を転換し、継続的な運営を維持している\tライブプラットフォーム ↗\nCSGOCasino\ncsgocasino.net / csgocasino.gg\t10日前の通知（2016年7月）\t『LIVE VIA SUCCESSOR』（2026年）\nドメインがリダイレクトされました。現在稼働中の後継ポータルは csgocasino.gg で運営されています。\t後継ドメイン ↗\nCSGOatse\ncsgoatse.com\t10日前の通知（2016年7月）\t6年間存続（2022年まで活動中）\nValveによる10日間の最後通告後も、6年間にわたりギャンブル事業を全面的に継続した\tX: @CSGOatsecom（2022年まで活動中） ↗\nCSGOSweep\ncsgosweep.com\t10日前の通知（2016年7月）\t2017年12月まで生存した\n期限切れ後も17か月間、一般に運営されていた\tX: CSGOのスイープ状況 2017年12月 ↗\nCSGOWild\ncsgowild.com\t10日前の通知（2016年7月）\t2017年12月まで生存した\n主要なインフルエンサーによって宣伝され、C&D（差止請求）を受けた後も1年半にわたり運営され、その後暗号資産分野へ移行した。\tX: @Wild (2017年12月現在、活動中) ↗\nCSGOPot\ncsgopot.com\t10日前の通知（2016年7月）\t2017年9月まで生存\n通知から14か月間、高額ジャックポット賭博を運営していた\tX: @csgopot（2017年9月に活動） ↗\nCSGODiamonds\ncsgodiamonds.com\t10日前の通知（2016年7月）\t2017年半ばまで生き延びた\nスポンサー付きストリーマーによる結果操作が認められたにもかかわらず、2017年はそのまま進行した\tX: @csgodiamondscom (2017) ↗\nCSGOLotto\ncsgolotto.com\t10日前の通知（2016年7月）\t2016年7月に閉店\n世間のスキャンダルにより事業を停止；連邦取引委員会（FTC）の同意命令の対象となった\tFTC同意命令（事件番号 C-4632） ↗\nCSGODouble\ncsgodouble.com\t10日前の通知（2016年7月）\t2016年7月閉店\nC&Dの公表後、直ちに自主的に営業を停止する\tX: @CSGODouble (2016年7月に閉鎖) ↗\nCSGOMassive\ncsgomassive.com\t10日前の通知（2016年7月）\t2016年閉店\n2016年後半に一般向け運営を終了した\tX: @csgo_massive ↗\nCSGOStrong\ncsgostrong.com\t10日前の通知（2016年7月）\t2016年 閉店\n2016年に一般向けの運営を終了した\tFB: csgostrongfree ↗\nSkins2\nskins2.com\t10日前の通知（2016年7月）\t2016年 閉店\n2016年に一般向け営業を終了した\tFB：CSNCOM ↗\n\nプラットフォーム\t月間トラフィック（訪問数）\t推定売上高／取扱高\t法人格および管轄\t主な規制措置とモデル\nCSGOEmpire\ncsgoempire.com\t230万～900万／月\n平均所要時間 6分以上； 80% 直通\t$1.5B — $2.5B 年間取扱高\n>1,000,000 P2Pスキン取引／月； $6.4M アクティブな流動性注文フロア\tMoonrail Limited B.V.（キュラソー #148182）\n支払先：JHOLT LTD（キプロス）；創設者：「Monarch」（オッシ・ケトラ）\t手数料無料のP2Pアイテム取引を先駆けて導入。キュラソー OGL/2024/1183/0869 ライセンス取得済み\nCSGORoll\ncsgoroll.com\t274万～350万／月\n平均所要時間 9分23秒；直帰率 16%\t$1.0B — $2.0B 年間取扱高\nハウスエッジによる年間企業収益は、推定$100M～$200M\tフェラル・ホールディングス・リミテッド\nベリーズのベリーズシティに本社を置く（登録番号 #171519）\tオーストラリアのACMAにより禁止措置を受けた（2023年5月）。未成年の選手を擁するティア1チーム「G2 Esports」をスポンサーとして支援していた。\n500カジノ (CSGO500)\n500.casino / csgo500.com\t月額22万～42万5千\n月間ユニーク訪問者数：約10万5千人\tロヤレスでは週に0k（年間1M）\nハイローラーの賭け条件：$1のレーキバックにつき$400の賭け金\tPerfect Storm B.V.（キュラソー #150536）\nキュラソー賭博管理委員会ライセンス OGL/2024/1354/0882\tスウェーデンのプレイヤーを無許可でターゲットにしたとして、スウェーデン賭博監督庁（Spelinspektionen）により禁止措置を受けた（2023年11月）\nCSGOBig\ncsgobig.com\t～0／月\n平均所要時間 19分12秒；米国予備選挙\t年間取引高は数百万規模\nミステリーボックス、ルーレット、ケースバトル\t補助プロキシルーティングを介して動作する\nletmeinbig.com（2023年登録）およびcsgobiglogin.com\t2016年7月のC&Dの対象；プロキシ認証アーキテクチャを採用して再リリース\nCSGOFast\ncsgofast.com\t月約15万～25万\n世界中の多言語の視聴者\t年間取引高は数百万規模\nハイスピード・ルーレットおよびクラッシュゲーム\tオフショア事業体\nルート Steam steam-login.authtofast.com 経由の認証\t2016年7月のC&Dの対象となったが、事業は一度も停止しておらず、2026年現在も稼働中である。\nCSGOポリゴン\ncsgopolygon.com / plg.bet\t月約30万～50万\nCISおよび東欧諸国の優位性\t年間取引高は数百万規模\n暗号資産＆スキンルーレット、マッチベッティング\t第2波の目標（2016年10月）\nミラードメイン「plg.bet」を活用して、仮想通貨事業へ軸足を移した\t10年間も持ちこたえ、サードパーティのAPIを通じて引き続き資産の清算を行っている\n第2の波：なぜValveの差止請求が計43以上のサイトを標的にしたのか\n\n2016年10月17日、Valveの法律顧問は、ワシントン州ギャンブル委員会に対し、7月19日の最初の23通の通知に続き、Valveが以下の各社に対して差止請求書を送付したことを正式に開示した。さらに20以上のスキンギャンブルサイト （これにより、公式の合計は43を超えた）。この第2弾のリスト作成が必要となったのは、最初のリストから、世界で最大かつ最も悪名高いギャンブルの拠点が、不可解なことに除外されていたためである：\n\nCSGOJackpot.com： 「スキン・ジャックポット」の創始者であり、連邦政府による起訴の脅威にさらされて閉鎖されるまで、数億規模の取引高を扱っていた。\nCSGOShuffle.com： 2016年7月のストリーミングスキャンダルの中心となったこのサイトでは、TwitchのストリーマーであるPhantomL0rdが同社の株式を33%秘密裏に保有しており、自己資金を用いてオッズを操作していたことが発覚した。\nマクロ・エコシステム（200社以上の事業者）： Narus AdvisorsおよびEilers & Krejcik Gamingによる業界調査によると、2016年には200以上の異なるスキンギャンブルサイトが運営されており、303万人のアクティブプレイヤーから$5.01十億の賭け金総額を生み出した。 Valveの43通の書簡は、アクティブな市場の20%未満を対象としていた。\n「Steam スキンギャンブル」に関する政府および規制当局による公式調査\n\n「スキンギャンブル」という現象については、複数の正式な法定調査、法執行措置、および政府の政策文書において記録が残されている：\n\n1. ワシントン州ギャンブル委員会（WSGC）（2016年～2018年）\n\n2016年10月5日に正式な差止請求書を発行。2018年1月30日には、スキンが現金同等物であることを明記し、スキンを用いた賭けの取引高が$5.0Bであることを報告した「立法ブリーフィング」を公表した。\n\nWSGC 立法報告書 PDF（ローカルコピー） ↗\n2. 米国連邦取引委員会（FTC）（2017年9月、事件番号C-4632）\n\nCSGOLottoの運営者であるトレバー・マーティン氏とトーマス・キャッセル氏に対し、欺瞞的な行為およびプラットフォームの管理権限の非開示を理由に、スキンギャンブルに関する初の連邦規制当局による執行措置が講じられた。\n\nFTCの決定および同意命令 ↗\n3. 英国賭博委員会（UKGC）の意見書および青少年監査\n\n2005年賭博法に基づき、ゲーム内のスキンは正式に「金銭または金銭的価値のあるもの」に分類された。その後の調査では、11歳から16歳の子供のうち11%以上が、ビデオゲームのスキンを賭けていたことが判明した。\n\nUKGC研究リポジトリ ↗\n4. オーストラリア上院環境・通信調査委員会（2018年）\n\n連邦議会の報告書「～に関する」「運任せのアイテムに関するゲーム内課金」、Valveのロートボックス仕組み、セカンダリーマーケットでの現金化、および規制回避について評価する。\n\nオーストラリア議会による調査 ↗\n未決済の需要\n\n執行記録を公開すること：どのギャンブルアカウントやボットが無効化されたか、どのリターンホストが制限されたか、そしてどの商用サービスが許可を受けたか。公的な禁止措置やホームページ上の警告だけでは、その背後にある運営が停止されたとは断定できない。\n\nパートB — 規則および執行実績 · 第12条\nホスト名はすでにリクエストに含まれています。\n文脈と出典の制限\n\nValveはすでにドメインリスト（リンクフィルター）を管理しており、すべてのOpenIDリクエストにおいて認証ホスト名を受け取っている。以下の擬似コードは、この2つを結びつける論理的な仕組みを示している。Valveがそうしていることを示す公開された証拠はない。\n\nValve はすでにドメインのブロックリストを運用している。 Valve はすでに、すべての OpenID リクエストにおいてログインホストを受け取っている。何も作る必要はありません。この2つをつなぐだけです。 これは、Valveが独自に管理するリストに対するホスト名検索です。以下の擬似コードはあくまで例示であり、Valveの実装ではありません。\n\nforensic_autoban.py\n# 説明用の擬似コード — Valve.block_domain() および flag_session_as_mitm() は実際の API 呼び出しではありません。 これは、プロキシ認証ドメインに対して Valve が実装し得る緩和策の論理構造を示すものであり、実際の Valve の内部構造を示すものではありません。\n# 図解：受信したOpenIDリクエストに対する検証の論理的な流れ\ndef audit_openid_request(リクエスト)：\nblocked_origins = database.get_blacklisted_platforms()\nproxy_domain = request.params.取得する('openid.realm')\ntarget_redirect = request.params.取得する('openid.return_to')\n\n# ロジック：プロキシがブロックされたサイトへ転送する場合は、そのプロキシを禁止する。\n～のために サイトin blocked_origins:\nもし サイトin target_redirect:\nValve.block_domain(proxy_domain)\nValve.flag_session_as_mitm(request.session)\n# 結果： そのホストからのログイン要求は拒否されました\n\n所見：\nメインドメインがすでにリンクフィルターに登録されている場合（例：howl.gg、ブロック対象 2026-09-18/19/21）にすでに登録されており、かつその認証ホスト（howl.uno）が当該サイトのログインボタンからのOpenIDリクエストに含まれている場合、その関連付けはValveが自身のリクエストデータから確認できます。このチェック自体は自動化可能ですが、実行されるかどうかは自動化できません。\n記録・報告された先例\n\nValveは、記録上少なくとも1回、第三者の事業者に対して介入を行ったことがある。2018年には、ExpressTradeシステムにおけるOPSkinsのアクセス権を取り消した（Valveの発表 ↗ アーカイブ済み 2026-03-07 ↗). 2018年のコミュニティからの報告では、あるマーケットプレイス（SkinJar）へのアクセスが失われたことも記述されている。これらの報告は未確認であり、そのメカニズムは開示されたプロセスに基づくものではなく、結果から推測されたものである。\n\nこの判例が確立した点：\n\nValveは、自らの判断でサードパーティのオペレーターへのアクセスを遮断することができる。2016年7月の通知に関する報道で名指しされたCSGOFastは、2026-09-21上で運用されており、2026-06-30に登録された認証ホストからはリンクフィルターによるブロックは返されていなかった。 ある事業者の接続が遮断され、他の事業者は遮断されなかった理由については、公表されている基準では説明されていない。\n\n登録日からは何がわかるか、何がわからないか\n\n認証ホストの登録日は、そのホストがOpenIDリクエストに初めて出現し得た時期の下限を示すものであり、継続的な使用を証明するものではありません。sc-auth.net例えば、2019-04-02（RDAP）として登録されていたものが、2026年9月にSkin.ClubのSteamログインフローで確認されたが、この2つの日付の間に何が起きたかについては、公開記録には記載されていない。\n\n比較監査：APIコンプライアンス基準\n執行の側面\tGitHub API のルール\tSteam Web API (Valve)\n1. コンプライアンスの中立性\t公表された統一的なルール。文書化されたレート制限（例：認証済みユーザーは 5,000 回/時間、GitHub Enterprise Cloud 組織は 15,000 回/時間）および公表された利用規定は、すべてのアカウントに適用されます。\t公表された基準は存在しない。個々のアカウントは、自動化および商用利用に関する条項（アーカイブされた苦情）に基づき停止されているが、商用プラットフォームにおける事業者ごとの執行実績は公表されていない。\n2. OpenID / 認証プロキシの悪用\tGitHubが公表しているポリシーでは、不正利用があった場合、OAuthアプリやトークンを一時停止または無効化することが認められており、そのドキュメントには、公開されたトークンの自動無効化について記載されています（著者によるGitHubドキュメントの要約）。\tSteamのOpenIDフローで確認された別ドメインの認証ホスト（例：rbsnin.com、howl.uno、sc-auth.net）は、そのメインドメインではLink Filterによるブロックが発生したのに対し、2026-09-21ではブロックされなかった。\n3. 虐待の収益化\tGitHubは、サードパーティ製の自動化ツールによって移動されたアイテムについては取引手数料を徴収しません。同社の収益モデルは、サブスクリプションとマーケットプレイスへの出品によるものです。\tValveは、アイテムを入手できるケースキーを販売しており、コミュニティマーケットでは、マーケット内で成立した取引に対して合計で約15%の手数料を徴収しています。第三者プラットフォームに帰属する収益については、ここでは推定していません。\n4. 回避ループの持続時間\t停止されたOAuthクライアントIDは、停止措置が適用された時点でプラットフォーム全体で機能しなくなります。ドキュメントには対応までの所要時間が記載されておらず、本稿でもその期間は想定していません。\t2011年から2026年9月までの登録日を持つ別ドメインの認証ホストについては、2026-09-19および2026-09-21のチェックにおいて、リンクフィルターによるブロックは確認されなかった。登録日は利用の可能性の下限を示すものであり、継続的な利用の証拠ではない。\n出典：GitHubコラム — GitHubが公開しているAPIのレート制限およびプラットフォームポリシーに関するドキュメント（著者による要約。原文の引用ではない） · Steamコラム — 2026-09-19および2026-09-21のリンクフィルターチェック（linkfilter-recheck-2026-09-21.json), RDAPレジストリ (domain-registration.json) およびアーカイブされたサポートへの苦情（証拠アーカイブ).\nパートB — 規則および執行実績 ・ 第13条\nオフ-0-価格差\n\nこのアイテムはSteamのインベントリに保管されており、販売は別の場所で行われます。ファクトリーニューのAWP「ドラゴン・ロア」にはCSFloatには現在62件の有効なオファーがあります; 提示された価格の中で最も安いもの$10,623.95. Steamの市場では、約$1,800を超える売出価格を設定することはできません。観測されたそれ以上の価格で売却するには、所有者はSteam以外の買い手または市場を必要とします。そのアイテムおよびその譲渡は、依然としてSteamに依存しています。\n\nWhat this means — the Community Market listing ceiling\n\nSteam’s own market refuses a listing above roughly $1,800. A seller may ask less, never more. Items whose market price sits above that line therefore cannot be sold at that price on Steam at all — which is the mechanism that moves those sales to third-party venues while the item itself never leaves Valve’s inventory system.\n\nSection 13 — the off-Steam price gap →\n\n文脈と出典の制限\n\nこのセクションには3つの異なるカウントが記載されていますが、これらは互いに置き換え可能ではありません。245 2026年9月20日時点で、CSFloatのみで最安の有効オファーが$1,800を超えたCS2のアイテム名カテゴリの数です。241 これは、CSFloatの$100,000上限に固定された4つのカテゴリを除いた同じセットであり、$13.63Mの下限が算出される際の基準となるパネルです。248 これは別のスナップショットであり、2026年9月23日時点で、5つのマーケットプレイスのうち2つ以上において上限価格を上回って価格設定されていたカテゴリーを示しています。マーケットプレイスは重複しているため、異なる取引所での件数を決して合算してはなりません。 ここにある数値はすべて「提示価格」であり、成約価格ではありません。また、これらはすべて、Valveにとっても、その他の誰にとっても、収益、売上高、利益ではありません。 PriceEmpireに掲載されている数値は、同サイトが公表した四捨五入された推定値であり、その「Steam」カードには他の「Steam」ゲームのアイテムも含まれているため、比較対象の範囲は同一ではありません。\n\n1つの商品。2つの価格体系。記録を追う\nステップ 3 / 3\n\nその条件では、売り手はSteam以外の取引場所や買い手が必要になります。その商品は、依然としてSteamの在庫および転送システムに依存しています。\n\nSTEAM「$1,800」について公開されたコミュニティマーケットの出品上限数\n保存済みカタログ$10,623.95工場出荷状態のAWP Dragon Lore、価格はお問い合わせください\n依存関係まだSteamの商品です在庫と振替は Steam のままです\n01 / アイテムValve ゲームのインベントリCS2またはDota 2のアイテムがSteamに保管されている\n02 / 天井「0」について　「1」マーケットへの1件の掲載につき、上限価格\n03 / 外部からの依頼$10,623.95 『ドラゴン・ローレ』よりその日付のスナップショットにおける、CSFloatの最安値のオファー\n04 / 配送Steam がチェーンに残っている所有権やアイテムの譲渡は、そのシステムに依存しています\n市場構造・特定時点のスナップショット、20 9月 2026\n価格差は数値で把握できる。\n\n最も安い有効なオファーが1,800.を厳密に上回る商品名のカテゴリをカウントしました。CSFloatおよびSkinportは、CS2の在庫が重複している別々のスナップショットであり、それぞれのカウントを合算することはできません。外部のオファーは、より高い希望価格が掲載されている場所を示していますが、商品の所有権および譲渡の管理は依然としてSteamが行っています。\n\n245CS2 カテゴリ · CSFLOAT\n166CS2 カテゴリー · SKINPORT\n3DOTA2カテゴリ · SKINPORT\n$10,623.95ドラゴン・ロア・フロアについて質問\n\nDragon Lore：62では、「Factory New」カテゴリーにおいてCSFloat件のオファーが掲載されています。表示されている価格は「希望価格」であり、成約価格ではありません。Steamでは、それより低い価格で出品することは許可されていますが、実際に確認されたより高い希望価格を掲載することはできません。Valveの2016の声明では、OpenIDおよびSteamの取引インフラを利用するギャンブル事業者の存在を認識していることが確認されています。特定のサードパーティマーケットプレイスがValveのルールに違反しているかどうかは、別途確認する必要があります。\n\n登録内容すべてを確認する →CSFloat JSON ↗Skinport JSON ↗Valveの「2016」に関する声明 ↗\nDIRECT CSFLOAT API / 日付指定スナップショット$13.63M\n\n最低総希望価格（）241の商品カテゴリ そして3,395 有効なオファー. 各カテゴリーの最安売値×そのオファー数として算出される。CSFloatの$100,000上限に固定されている4つのカテゴリーは、この保守的なパネルからは除外されている。\n\nその金額が示すもの\n\nこれらのオファーは、少なくとも$13,631,888.25 この限定的なCSFloatサブセットの掲載売出価格において。上限価格の4つのカテゴリーを含めると、以下のようになります。$14,231,888.25. これはアクティブなリクエストの件数、成約件数や売上高、現金売上高、利益、あるいはCS2市場全体ではありません。\n\n245行のCSFloatスナップショットから再計算 ↗\nPRICEEMPIRE / 掲載価格Steam: 39件中15件目\n多くの会場では、Steamよりも高い金額が記載されています。\nUUSkins\n$133.8M\nYouPin898\n$127.5M\nBuff.163\n$104M\nMoon.Market\n$100.3M\nWhite.Market\n$89.6M\nBuff.Market\n$86.7M\nSteam\n$31M\n\n表示された値のうち、上位6つと「-0」です。PriceEmpireはこれらの数値を四捨五入しており、「-1」は$31M。表示されている金額によると、この会場より上位にランクインしている上場会場は14カ所ある。\n\nPRICEEMPIRE / オファー数Steam: 39件中1件目\nSteamは依然としてオファー数でトップを維持している。\nSteam\n32.2M\nYouPin898\n5.9M\nC5Game\n460万\nHaloSkins\n440万\nスキンポート\n3.8M\n\nSteam 件の表示32.2M オファー。オファーの件数と総希望価格は、それぞれ異なる質問に対する答えとなります。低価格の物件が多数あると、件数でその割合が際立つことがあります。\n\n出典：PriceEmpireの公開比較 ↗ アーカイブ済み 2026-09-21 ↗, 19:03 UTC に記録された；39行分の抽出（日付付き） ↗. 数値は概算値であり、在庫は複数の拠点にまたがっている場合があります。Steamのカードには、他のSteamゲームのアイテムも記載されているため、対象範囲は完全に一致しません。記載されている価格は希望小売価格であり、売上や収益を示すものではありません。\n42\n別の情報源 / STEAMANALYST\n商業エコシステムは、誰の目にも明らかです。\n\nSteamAnalystのマーケットプレイス一覧 アーカイブ済み 2026-07-19 ↗ Steamに加え、42のサードパーティ製CS2マーケットプレイスを掲載しており、43件のうち32件については最新の価格データが掲載されています。PriceEmpireは、独自の選定基準に基づき39のマーケットプレイスを掲載しています。企業名、公開オファー、表示価格――この経済活動は誰にでも確認可能です。\n\n「上限こそが仕組みだ」：セールは勢いを失っても、商品そのものは失われない。\n\n1つのライセンス付きスナップショットに収められた5つのマーケットプレイス全体で、248のCS2商品カテゴリのうち、2つ以上のカテゴリがSteamの約$1,800という出品上限価格を上回る価格設定が個別にされており、そのすべてがSteamには掲載されていない。. 同じスナップショットでは、カタログ全体が価格帯ごとに分類されていた：Valveのマーケットプレイスでは、上限価格以下の商品カテゴリーは95.3%、上限価格を超えるものは1.9%が取り扱われている。この縮小は需要の低下によるものではなく、公表されたルールに完全に合致している。 これらの価格での販売には外部の買い手またはマーケットプレイスが必要となる一方、在庫と移管の管理は依然としてSteamが行っている。つまり、取引はValveのチェックアウトプロセスを経るが、配送はValveのインフラ上で行われる。\n\nSteam 市場に関するよくある質問 ↗アーカイブ済み 2026-09-21 ↗Steam 利用規約 ↗アーカイブ済み 2026-09-21 ↗5つのマーケットプレイスを網羅したアトラス・データセット ↗出所明細書 ↗以前の CSFloat スナップショット ↗Skinportの概要 ↗PriceEmpire ↗アーカイブ済み 2026-09-21 ↗SteamAnalyst ↗アーカイブ済み 2026-07-19 ↗価格差レジスター ↗価格ラダー・アトラス ↗\n\nパートC — 法的枠組み\nパートC — 法的枠組み · 第14節 · 人員の立ち入り\n誰が安全装置をリセットできるのですか？\n文脈と出典の制限\n\nアカウントのセキュリティは、アカウントの復旧、非公開記録の閲覧、あるいはセキュリティ対策のリセットを行うことができる人物にも左右されます。調査においては、APIの不正利用と同様に、こうした特権的な操作についても綿密に追跡する必要があります。\n\nアカウントの復旧処理により、サポート担当者はアカウントを所有者から切り離す権限を持つことになります。Valveは、2023年2月と2025年11月の2回にわたり、この権限が誤ってアカウントを不適切な人物に引き渡すために使用されたことを書面で確認している。 33ヶ月の間隔を置いて、同じ経路を通じて。以下では、そのアクセス権の価値、6件の情報源に基づく事例、そしてログ「Valve」がそれらすべてに適用されていること、そして誰に対しても開示されていないことを解説する。\n\n保存された証言 / 2025年5月9日\nアカウントのセキュリティ機能を無効にした復旧チケット、および報告された$10,000の損失\n\n収集されたサポートアーカイブにあるあるユーザーの報告によると、他者が復旧チケットを送信した後、Steamサポートがパスワードをリセットし、アカウント保護機能を無効にしたとのことです。 投稿者によると、そのアカウントは数年間利用されておらず、2016年から2017年にかけてのアイテムが残っており、Steam Guard、連携済みの電話番号、および保存済みの回復コードがあったとのことです。\n\n「Steam サポートが、また別の誰かに私のアカウントへのアクセス権を与えてしまった。」\n\n『』に記録された、当事者による主張steam_support_tickets_MEGA.json, 記録110。キャプチャされた投稿全文を読む ↗\n\nこれは、ある特定のユーザーだけの不運というわけではありません。同じ仕組み――より古いデータを提供した者にアカウントを移管するという支援要請――が、以下の台帳に記載されているすべての事例において、公式に認められた手順であり、Valveはそのことを2度にわたり文書で明記しています。\n\nその議論では、オーナーは勝てない。 復旧手続きでは、最初のCDキー、最初のメールアドレス、最初のクレジットカード、最初の電話番号が求められます。これらの情報はValveのデータベースに記録されており、サポート側のアクセスによって読み取られます――その記録は15年前まで遡ると報告されています。あなたのファイルのコピーを所持している人物は、常にあなた自身よりも多くの履歴を提示してくるものです。 ターゲットは、特定の条件に合致するように選ばれました。つまり、何年も休眠状態であり、価値が高く、多くの場合中古で購入されたもので、所有者は元のキーを知らないというものです。その後、アカウントは完全に削除され、コミュニティがスキンを追跡するために使用するアイテム履歴の痕跡が断ち切られました。この削除は、通常のユーザーが標準的な待機期間を経ずに実行することはできないものです。\n\n最小権限の原則 / OWASP A01\n\n復旧権限は当該タスクに限定し、個別に審査・記録を行う必要があります。認証情報のリセット、Steam Guardの削除、請求記録の閲覧、またはアカウントデータのエクスポートが可能だったユーザーを監査してください。OWASP アクセス制御に関するガイダンス ↗ アーカイブ済み 2026-09-20 ↗\n\n幅広いサポートへのアクセスアクセス範囲に関連するリスク\n在庫の枠を超えて。\n\n広範なアクセス権限が悪用された場合、非公開のテレメトリデータは、プロファイリング、標的型フィッシング、監視の手段となり得ます。潜在的な被害者には、一般ユーザー、軍関係者、公人、およびその家族が含まれます。これは脅威モデルであり、具体的な権限についてはアクセス制御記録を参照する必要があります。\n\n01 IP履歴と位置情報\nIPログからは、ネットワークの利用履歴やおおよその位置情報が判明する場合があります。ただし、それだけでは正確な物理的な移動経路を特定することはできません。\n02 デバイスのフィンガープリント\nデバイス識別子は、収集され、かつアクセス可能な場合、セッションとアカウントを関連付けることができます。\n03 アクティビティのテレメトリ\nログインのタイムスタンプやセッション記録からは、公開プロフィール上では見えない活動を含め、その人物の日常的な行動パターンが読み取れることがあります。\n04 広報・連絡先\n保存されたメッセージや連絡先情報へのアクセスが可能になれば、プロファイリングやソーシャルエンジニアリングの余地が広がるだろう。\n05 身元の暴露\n元の電子メール、電話番号、および支払いの記録があれば、仮名アカウントと実在の人物を結びつけることができます。\n06 データの再販と説明責任\nエクスポートされたターゲットリストは、標的型詐欺に利用される可能性があります。攻撃者、アクセス元、受信者、および転送先を特定してください。アクセス元だけでは、アクセス権や法的免責を立証するものではありません。\n\nValveは、その文書の中で、IPログ、デバイス情報、支払い記録、およびサードパーティのサポートプロバイダーについて説明しています。プライバシーポリシー 第3条、第5.2条 アーカイブ済み 2026-09-21 ↗。この方針では、第三者によるサポートへのアクセスが許可されているが、どの請負業者がいつ、どのような権限に基づいてどのカテゴリにアクセスしたかを示す監査証跡は開示されていない。\n\n第14.1節 · 『ザ・レジスター』 · 2022年6月 → 2025年11月 · すべての図の出典を明記\nValveは、33ヶ月の間隔を置いて2度、その扉を開けた。扉は一度も閉まることはなかった。\n\nSteam自身のヘルプリクエストチャンネル、あるいはそのチャンネルが保護している認証情報を通じてアカウントが乗っ取られたと報告された事例が6件ある。各金額は引用元が公表した数値であり、各情報源も明記されている。6件のうち2件は全額補償された。 これら2件と残りの事例との違いは、何が起きたかではなく、誰が監視していたかという点にあった。\n\nValve、書面にて — 2023年2月「問題のアイテムは、サポートへの問い合わせを通じて不正アクセスを受けたアカウントから受け取ったものであるため、お客様のアカウントから削除されました。この件については、CS:GOチームが責任を負います。当チームは取引を取り消し、それらのアイテムを受け取ったすべてのアカウントから削除しました。」Steam HFBのアイテムの受信者への返信をサポート。以下に転載：Dexerto、2023年2月21日 ↗ アーカイブ済み 2025-08-18 ↗\nValve、再び執筆 — 2025年11月 · 33か月後「このサポート依頼を担当したサポート担当者が当社の手順に従わなかったため、お客様のアカウントが他のお客様のものとして復元されてしまいました。この誤りについてお詫び申し上げます。」Steam Hawkeye337への返信（引用元：）Dexerto、2025年11月14日 ↗\n2022年6月21日\nHFB — ゲーム内最大の品揃え$2,000,000+・2023年2月のフォローアップ調査で$3,000,000+に引き上げられた\n\n7つの「Souvenir AWP Dragon Lores」と、No.1の「Blue Gem Karambit」。このナイフ1本だけで、その価値は約$1.26百万。そのアカウントは3年間休眠状態にあったが、モバイル認証アプリは依然として有効な状態だった。それでも、サポートのアカウント復旧手続きを通じて、メールアドレスとパスワードは変更された。\n\n品物がなくなる前に、お金は先に無くなってしまった。 報道によると$200,000+ 販売代金の一部は、現金および仮想通貨で決済を行うマーケットプレイス「market.csgo.com」を通じてすでに引き出されていました。取引を取り消しても、スキンは返還されますが、すでに口座に入金された現金は返還されません。\n\nところが、その修正がうまくいかなくなってしまいました。 ある購入者が、自分の「Souvenir Dragon Lore」をゲーム内のストレージユニットに移動しました。Valveのロールバックスクリプトは、自身のコンテナの中身を確認できなかったため、所有者に新しいコピーを配布し、非表示のものはそのまま残しました。Valveは、$130,000 盗難を元に戻そうとした際に使用されたアイテム。アイテムIDの照合とコミュニティからの通報により発覚し、1か月後の2022年7月に削除された。 購入者への返金はValveではなく、BUFFによって行われました。これほど脆弱な緊急対応は、管理措置とは言えません。それは、プラットフォームが管理不能な状況に陥った際に取る行動に過ぎないのです。\n\nDexerto、2022年6月21日 ↗ アーカイブ済み 2022-07-02 ↗ ・カスペルスキー ↗ ・1件あたりのキャッシュアウト額Esportfire、2022年6月22日 ↗ アーカイブ済み 2026-05-15 ↗, そこでは複数のTwitterの情報源によるものとされている · 重複および削除についてはEsportsbetting、2022年7月14日 ↗\n\n復元済み取引が取り消された。定価で購入した人々の在庫から、商品が引き揚げられた。\n2022年8月14日\nCS.Money — プラットフォーム独自のボット$6,300,000・ 19,000+ スキン ・ 初回見積もり $1.6M\n\n攻撃者は、このマーケットプレイスの取引ボットが使用するモバイル認証アプリのファイルを乗っ取り、その内容をすべて消去した後、証拠を隠蔽するために、盗んだデータの一部を著名なトレーダーたちに送った。コミュニティの研究者たちは、その経緯を明らかにした。数時間のうちに55件の攻撃者アカウント そしてそれらを出版した。\n\nValveは決定を覆さなかった。その理由として挙げられたのは、第三者のサイトがSteamの外部に位置しているという点だった。このSteamとは、盗難事件において在庫、取引API、アカウントシステムがエンドツーエンドで利用されていたのと同じSteamのことである。\n\nEsportfire、2022年8月14日 ↗ アーカイブ済み 2025-11-15 ↗\n\n拒否された事態は好転しなかった。損失はプラットフォームとそのユーザーに押し付けられた。\n報告された\n2023年2月21日\nQkss — 同じ扉、同じ俳優$1,000,000+\n\nHFBと同じ方法で、同じ担当者が、同じサポート依頼を通じて対応したと報告されています。HFBについては8か月前に全額補償されましたが、Qkssについてはそうなりませんでした。\n\n一つの道。二つの答え。 公表された記録には、聴衆の規模を除いて、この2つの事例を区別する要素は一切見当たらない。\n\nDexerto、2023年2月21日 ↗ アーカイブ済み 2025-08-18 ↗\n\n拒否された復元されていません。\n報告された\n2023年2月\nインサイダー取引そのもの――1年間にわたる取引≈ $320,000・約1年間にわたって行われるものであり、在庫評価ではない\n\nサポート側からのアクセスにより、以下の期間までのアカウント履歴を確認しました15歳 — 最初のCDキー、最初のメール、最初のカード。これこそが、復旧プロセスで求められる証拠そのものであり、だからこそ、データベースを管理している側が、アカウントを管理している側との議論では常に勝つことになるのです。\n\nブロガーのMzkshow氏は、インサイダーの運営者「Steam Help」と共犯者の「Alexander」が、$100k以上のスキンを持つ休眠アカウントを標的にしていた実態を暴露した。iBUYPOWERとTitan Katowice 2014のホログラムが貼られた盗まれたM4A4 Howl 1丁は、$35,000 その結果、NAVIのヴァレリー・\"b1t\"・ヴァホフスキーが担当することになったが、彼にはその事情を知る由もなかった。Valveが介入した後、請負業者はSteamのサポートデスクのスタッフ全員を解雇した。\n\nVKPlay ↗ ・Lis-Skins ↗ ・Escorenews (RU) ↗ ・Dexerto (EN) ↗\n\n登録なしValveは、この件がいくつのアカウントに影響を与えたかについて公表したことはなく、影響を受けた人々にもその旨を伝えていない。\n報告された\n2024年12月2日\n「マトヴェイ」――解雇の後$13,000\n\nアカウント所有者本人では照合できなかったアカウント情報を提供した人物に対し、アカウントの復旧が認められた。請負業者がそのSteamサポートデスクを撤廃してから2年後、同じ方法で同じ結果が得られた。\n\n保存された投稿、2024年12月2日 ↗ アーカイブ済み 2025-08-05 ↗ ・ソース行とハッシュ ↓\n\n拒否された復元されていません。\n2025年11月13日\nHawkeye337（マーク・スパーロック）――そして2度目の告白≈ 0–1・カトヴィツェ2014 ホロコレクション全点\n\n犯人は次のように要求した1ビットコイン そして、そのコレクションをネゲブにコピーして破棄し始めた。Steam サポートからの書面による回答は、上記の2つ目の事実の認容にあたる。すなわち、技術者がサポート依頼に対応したが、所定の手順に従わず、そのアカウントを他の人に引き継いだということである。\n\nこの不具合の原因はフィードでした。 XにValveをタグ付けした投稿が掲載されてから数時間後、そのアカウントは取り戻され、すべてのステッカーが復元された。Qkssにはそこまで多くのフォロワーはいなかった。\n\nSkin.club ↗ ・Dexerto ↗ ・Esportfire ↗ アーカイブ済み 2025-12-17 ↗\n\n復元済みその記事がトレンド入りしてから数時間以内に、記事は取り下げられた。\n台帳には、個々の事例からは読み取れないことが記されている。\n\nそのルートは一度も閉鎖されたことはありませんでした。 最初の入院日は2023年2月、2回目は2025年11月です――33ヶ月の差、その間に請負業者による大量解雇、記録に残る再発、そして$6.3百万規模のプラットフォーム侵害が発生した。この台帳に記載された最初の盗難から数えると、その経路は3年5ヶ月. 2023年にどのような修正がなされたにせよ、2025年11月、そのヘルプリクエストによってアカウントが依然として間違った担当者に振り分けられてしまった――Valve自身の言葉である。\n\n賠償は、被害ではなく、注目度を基準としていた。 復活：ゲーム内で最大のインベントリ、そしてスレッドがトレンド入りしたコレクター。却下：$1,000,000, $6,300,000, $13,000。Valveは、適用されるルールを一度も公表したことがない。というのも、ルールを公表すれば、これら3つについて説明しなければならなくなるからだ。\n\n誰にも伝えられなかった。 データベースからアカウント履歴が読み出されたユーザーでもなければ、監督当局でもなく、善意で商品を購入し、その返還を求められた市場でもない。情報漏洩の通知も、インシデント報告も、影響を受けたアカウント数の集計もない――そして、残った収益は現金として残った、現金や仮想通貨で支払いを行うマーケットプレイスを通じて。取引の取り消しは、Steamから資金が流出した後では行えない。\n\nValve には、サポート監査証跡、復旧チケットのログ、および上記の各行に関する取引記録が保存されています。これらは一切作成されていません。ご自身のコピーをお求めください →\n\nNDAに関する質問\n機密性の確保には、技術的な説明責任が伴わなければならない。\n\n機密保持契約と、実際の権限設定、輸出規制、リセット承認、およびアクセスログを照合してください。回復プロセスそのものが悪用されたという申し立てについては、定型的な回答では解決できません。\n\nGDPR第28条、第32条～第34条\n\n第33条では、個人データ漏洩が発生した場合、管理者は72時間以内に監督当局に通知しなければならないと規定されている。また、第34条では、影響を受ける人々に対するリスクが高い場合には、その人々に通知することが義務付けられている。 Valveは、自社のサポート窓口がアカウント（利用履歴、請求記録などすべてを含む）を誤った人物に引き渡してしまったことを、書面で2回にわたり確認している。いずれの条項に基づく通知も公表されておらず、影響を受けるユーザーから通知を受け取ったという報告も寄せられていない。 規定を読む ↗ アーカイブ済み 2026-09-20 ↗\n\nリクエストにサポートへのアクセスを含めてください →\nパートC — 法的枠組み · 第15節 · 商業規模\n資金の流れを追跡する。取引を個別に区別する。\n文脈と出典の制限\n\n資金の流れを分けて考えると、商用利用の是非という問題はより鮮明になります。第三者へのアイテム譲渡、Valveの主要な販売、および外部への現金引き出しは、それぞれ異なる取引です。\n\nこのアイテムは Valve 個あります。在庫は Valve 個です。転送は Valve 台のサーバー上で実行されます。支払いだけが別の場所で行われるだけです — これが、ある者が資金送金業者に該当するかどうかを決定づける段階であり、Valveはこの段階において業務を行っていない。\n\n収益メカニズム\n実際に資金が動く場所。\n3つのルート／1つのアイテムによる経済システム\n01 / アカウントユーザーの一覧\n\n保有中のアイテム数 Steam\n\n02 / 移籍P2P取引\n\nユーザー ↔ ボット または ユーザー ↔ ユーザー\n\n03 / 決済外部プラットフォーム\n\nサイト残高または支払額 Steam\n\n発行部数経済的な原動力は、移籍金だけにとどまらない\n\nSteamは、外部市場で利用される在庫および移転インフラを提供している。本調査における経済的な論点は、再販の流動性と繰り返される需要が、ケース、キー、交換用アイテムへの支出を支え、その結果、コミュニティマーケットでのその後の販売に手数料が生じるというものである。 直接のP2P譲渡にはコミュニティ・マーケットの手数料は発生しないが、その会計上の事実は、より広範な便益を決定づけるものではない。Valveは、全過程を通じてアカウントへのアクセスおよび取引制限に対する管理権を保持している。\n\n01 / 二次需要流動性と再販価値\n\n対外貿易およびギャンブル需要\n\n02 / 主要支出鍵、ケース、カプセル\n\n提供されている場合、Valveからの購入\n\n03 / 収益一次販売による収入\n\nさらに、実際の市場での売上に対する手数料がかかります\n\n5% + 10%Steam + コミュニティマーケットでの販売に対するCS2手数料\n\nこの調査から導き出される経済的な示唆は、流動性の高い再販市場が新品の購入を促進し得るということである。お馴染みの「15%」は、最低額や四捨五入の条件付きで設定された市場手数料率を組み合わせたものであり、すべての対外取引に課される税金ではない。\n\nValveのコミュニティマーケット料金表 ↗ アーカイブ済み 2026-09-21 ↗. 2026年2月25日ニューヨーク州司法長官は訴訟を提起した アーカイブ済み 2026-09-01 ↗ 有料のルートボックスが、外部での現金転売やギャンブルによる害と関連しているとの主張――この報告書が技術・インフラの側面から立証しているのと同じ関連性である。 この申し立ては単なる主張であり、確定した事実ではない。ここでこれを引用するのは、ある州の法執行機関が、本報告書が問う問題と密接に関連する疑問を提起しているからである。すなわち、「公的な声明と一致する法執行の実績はどこにあるのか？」という疑問である。\n\n01 / エントリー仮想通貨の入金\n\n外部サービスおよびウォレットの記録\n\n02 / 変換バランス → スキン\n\nSteam回の取引を通じて引き渡された商品\n\n03 / 出口外部での法定通貨による販売\n\n売り手、買い手、および支払い代行業者\n\nKYC？引き継ぎのたびに担当者を明確にする\n\n調査すべきは、ネイティブの Steam API による現金化サービスではなく、このルートです。KYC不要の現金化を承認する前に、各外部事業者における本人確認、保管状況、取引ID、および出金先について確認してください。\n\nアメリカ合衆国／銀行秘密法\nまずその活動を分類し、次に義務を分類してください。\n\nFinCENは、事業者の業務内容に基づいて資金送金を評価します。 換金可能な仮想通貨の受領および送金は、適用される定義および例外に従い、マネーサービス事業者としての義務を発生させる可能性があります。ValveのSteamウォレットは資金を受け入れ、それをゲーム内アイテムに変換します。その後、それらのアイテムは第三者事業者を通じて換金され、実通貨となります。 アイテムおよびその移転はValveのインフラ上で行われますが、現金化はそうではありません。そのサイクルのどの部分が資金送金の定義に該当するかは、FinCENによる分類上の問題であり、本稿で結論付けるものではありません。\n\nFinCEN FIN-2019-G001、第1～2条、第5.1項 ↗ アーカイブ済み 2025-07-11 ↗\n\n欧州連合／マネーロンダリング\n資金の流れ、情報、および支援を追跡する。\n\n指令（EU）2018/1673は、犯罪収益を伴う意図的なマネーロンダリングおよびそれへの関与を対象としています。捜査上の争点は、Valveが、2016年7月13日に自社の取引およびOpenIDインフラの利用状況を公表した後、そのインフラを利用していた事業者についてどのような情報を把握していたか、またそれらに対してどのような措置を講じたかという点です。 Valveは事業者ごとの執行記録を公表していない。この疑問に答えるのは、本報告書ではなく、その記録である。\n\nEUの刑事法枠組み ↗\n\nAMLD6 の用語： 上記の刑事法指令は、AMLD6とも呼ばれる指令（EU）2024/1640とは別のものである。後者の一般的な国内法への移行期限は2027年7月10日であるが、特定の例外が定められている。第78条 ↗ アーカイブ済み 2026-08-30 ↗\n\nパートC — 法的枠組み · 第16条 · 通知、対応、責任\nデジタルサービス法：知見を記録に残す\n文脈と出典の制限\n\n第16条に基づく通知のうち、提出者に関する2つの要素、すなわち提出者自身の詳細情報と、情報が正確であるという善意の表明は、本書類ではなく提出者自身が負担するものである。 同条が要求するその他のすべて——根拠のある説明および正確な電子上の場所——は、第3節およびルートレジスタに、保存された応答とハッシュ値とともに記載されているため、いかなる当事者もこれを提出することができる。 法律自体に関するさらなる2つの制限として、ホスティング免除の喪失は、それ自体では他のいかなる法律に基づく責任も生じさせないこと、および第52条(3)の「6%」は法定の上限であり、「Valve」に対する査定された罰金ではないことが挙げられる。\n\nDSAの下では、ホスティングプロバイダーは、具体的な事実を知りながら対応を怠った場合に限り、その責任免除が適用されます。この資料が、その通知となります。 そこには、ホスト名、日付、保存された応答、およびハッシュ値が記載されている。この記事が公開された時点で、もはや「Valveが知っていたかどうか」が問題なのではなく、「Valveがその後どう行動したか」が問題となっている。\n\n012016年7月 / 資料展\n10日間の要求。\n\n上記で再構成した通知は、本調査における執行措置の比較における歴史的な出発点である。\n\n022024年2月17日 / 一般募集\nDSAの時間枠。\n\n過去の行為と、当該DSAの義務が適用される期間中の行為とを区別すること。\n\n0310年／元の書類のスナップショット\n期間には通知の履歴が必要です。\n\n2016年7月以降の経過時間（第11節参照）は、書類上の指標です。これは、10年間にわたるDSA違反の累積ではありません。各通知を、具体的な項目、適用される法令、送達証拠、および回答と関連付けてください。\n\n第52条第3項／法定上限6%\n世界全体の年間売上高のうち\n\nDSAの義務違反に対する最高罰金額は、当該プロバイダーの前事業年度の実績に基づいて算定される。これは法的に定められた上限額であり、Valveに対する査定された罰金ではない。\n\n第6条、第8条および第16条／法的判断基準\n\n関連するホスティングサービスについては、特定の事実に関する認識や迅速な対応を怠った場合、ホスティング免責が適用されなくなる可能性があります。十分に具体的な通知があれば、当該コンテンツに関する認識があったとみなされます。DSAは一般的な監視義務を課しておらず、免責の喪失そのものが、他の法律に基づく責任を成立させるものではありません。\n\nDSA：第6条、第8条、第16条、第52条、第53条、第93条および前文第17項 ↗ アーカイブ済み 2026-09-20 ↗\n\n保存済みの苦情を確認する ↗アカウントのタイムラインを作成する →法的・経済的な分析の全容 →\nパートC — 法的枠組み · 第17節 · 身元、年齢、商用アクセス\n未成年者：Steamでのログインは年齢確認にはなりません\n文脈と出典の制限\n\nこの資料のどこにも未成年者のデータは記載されておらず、収集もされていません。著者らは、言及されたいかなるプラットフォームにも登録、情報提供、またはログインを行っていません。このセクションを基に資料を作成する者は、児童に関する証拠を非公開とし、公開資料から個人を特定できる詳細情報を削除する必要があります。 ここでCOPPAが引用されているのは、対象範囲（対象者、実際の認識、収集された個人データ）に独自の条件を伴う児童のプライバシー保護法としてであり、一般的なギャンブルの年齢制限規則としてではない。2026年のニューヨーク州における訴状は、州当局による申し立てであり、確定した事実ではない。\n\n「Steamでログイン」すると、アカウントが存在することが確認できます。それは年齢について何も証明していない — そして、こうしたサイトにおいて、それは子どもと入金との間にある唯一の関門なのです。これを読んでみてください。第3.1節: Steamクライアント内では、ブラウザに表示されるはずの警告が決して発動しないため、子要素には警告が表示されることはありません。\n\nOpenIDが提供する機能とはアカウントの識別情報\n\nログインやアカウントの連携に使用される、認証済みのSteamID。\n\n≠\n事業者が確立しなければならない事項参加資格\n\n年齢、管轄区域、および必要な本人確認手続き。\n\n技術的根拠：Steamworks OpenID のドキュメント ↗ アーカイブ済み 2026-09-21 ↗. 記録された本人確認情報は、ユーザーが合法的にギャンブルを行えることを証明するものではありません。\n\nCOPPA／13歳未満の児童\n演算子とデータを特定してください。\n\nCOPPAは、対象となる児童向けサービス、および13歳未満の児童から個人情報を収集していることを実際に認識しているサービスに適用されます。これは児童のプライバシー保護に関する法律であり、賭博の年齢制限に関する普遍的な規則ではありません。対象者、収集される個人データ、認識状況、および親の同意を得る手続きを明確に定めてください。\n\nFTC：COPPAの要件 ↗ アーカイブ済み 2026-09-21 ↗\n\n保存すべき証拠\nログインから入金までの流れを記録してください。\n\n当該サイトの年齢確認機能、登録時の文言、利用資格条件、決済フロー、および苦情の履歴を保持すること。各運営者を個別に評価すること。児童に関連する証拠は非公開とし、公開される証拠資料からは個人を特定できる情報を削除すること。\n\nこれに関連する公的執行記録としては、2026年ニューヨーク州の苦情受付に関するお知らせ アーカイブ済み 2026-09-01 ↗、これは有料のルートボックスが若いユーザーに害を及ぼしていると主張するものです。これはCOPPAに基づく認定ではありません。\n\nパートC — 法的枠組み · 第18節 · GDPR第15条に基づく請求\nリクエスト。レスポンス。欠落している比較。\n\n彼は4つのことを求めたが、そのうちの1つは、自分のアカウントにAPIキーを設定した人物を特定できるログだった。3日後、そのチケットは、それらの情報が一切掲載されていないページへのリンクとともにクローズされました。 — そして、その文を締めくくるために使われた表現は、Valve自身の弁護士たちによって否定されている。\n\nこのアカウントの所有者 · 出所と制限\n\nこれらのスクリーンショットはPhishDestroyのものではありません。 これらは、ごく普通のSteamアカウントの所有者、つまり本プロジェクトが実施した簡単なアンケートに回答した人物から寄せられたものです。この人物は自らリクエストを提出し、スクリーンショットを提供しました。 アカウントもチケットも彼のものであり、やり取りは彼とSteamサポートとの間で行われたものです。本プロジェクトはリクエストを提出しておらず、当該プラットフォーム上にアカウントを保有しておらず、このチケットの当事者でもありません。\n\n2026年9月16日、彼はGDPR／CCPA第15条に基づく情報開示請求を提出し、具体的にはAPIキーの登録ログ、IPアドレス付きのログイン履歴、デバイスの認証履歴、および取引履歴の開示を求めました。9月17日、担当者の「Logen」は、セルフサービスの「アカウントデータ」ページを参照するよう案内しました。 9月18日、彼は、要求した情報カテゴリがそのページには掲載されていないと指摘し、プライバシーチームまたはDPOへのエスカレーションを要請した。9月19日、エージェント「Kal」は、同様の案内をもってチケットをクローズした。両方のスクリーンショットは以下に保存されている（請求者のメールアドレスは伏せられている；SHA-256はsteam_tos_assets/screenshot-manifest.json).\n\n彼が依頼者としてふさわしいのは、ごくありふれた理由によるものだ：このアカウントには、本人が作成していない「Steam」というWeb APIキーが紐付けられており、登録先としてlocalhost.いつ作成されたかは不明である — 彼自身によるものではなく、また Valve が彼に提供した何ものによるものでもない。というのも、その時期を特定できる唯一の記録は API キーの登録ログであるが、まさにそのカテゴリーの記録こそが、閉鎖によって隠蔽されていたからである。このキーは新しいものではない。同じ理由により、彼がその存在に気づくより前から存在しており、その期間の長さは彼には測り知れない。\n\n他のアカウント所有者も同様の要請を提出しています。届いた返信は、カテゴリの提供の可否にかかわらず、これら2件と同じ条件（チケット番号、取得日、SHA-256、要請者の情報は伏せ字）でここに追加されます。\n\n本プロジェクトは、チケットがクローズされた理由について、いかなる立場もとっていません。チケットには理由が記載されておらず、本プロジェクトにおいてもその理由は推測されていません。\n\nリクエスト。レスポンス。比較。記録を追う\nステップ 3 / 3\n\n彼は4つの具体的なカテゴリを挙げました。彼が参照した「アカウントデータ」ページは、Valve自身のセルフサービスによるエクスポートデータであり、本プロジェクトでは他者のアカウントの内容を列挙することはできないため、カテゴリごとの完全な比較結果はここに公開されていません。 記録に残っているのは、9月18日の「それらのカテゴリは存在しなかった」という彼の発言と、9月19日の、それらの件には触れずに紹介を繰り返しただけの解決通知です。\n\n依頼内容具体的なカテゴリーAPIキー、ログイン、デバイス、および取引記録\n対応アカウントデータのリファレンスサポート交換の点検\nテストどのようなものが納入されましたか？各リクエストされたカテゴリを比較する\n画面 1/2 — 依頼（9月16日）と最初の返信、エージェント「ローゲン」（9月17日）\nGDPR ticket HT-2YBP-F7JP-D4VB — request and first response\n出典：help.steampowered.com、チケット番号 HT-2YBP-F7JP-D4VB · 2026年9月16日～17日に取得 · 依頼者のメールアドレスは非公開 2026-09-21 · ファイル：gdpr-ticket-1.png ・SHA-256da940c731ab9869d226e9d06ccc8a1b393738766b7b0c445a56662623e025a66 (screenshot-manifest.json).\n画面 2/2 — エスカレーション依頼（9月18日）および解決、担当エージェント「Kal」（9月19日）\nGDPR ticket HT-2YBP-F7JP-D4VB — escalation request and closure\n出典：help.steampowered.com、チケット番号 HT-2YBP-F7JP-D4VB · 2026年9月18日～19日に取得 · ファイル：gdpr-ticket-2.png ・SHA-25644844ea7b251f7fd7d79f87ee1578a846606a97b9659d3a53b322120c422219b (screenshot-manifest.json).\n最終回答、9月19日（逐語記録）：\n「Steamが保持しているデータは、すでに『アカウントデータ』ページでご確認いただけます。サポートから提供できる追加情報Steamはございませんので、このリクエストは閉じられます。\"\nデータが提供されていない・拒否の法的根拠が明示されていない・エスカレーションの結果が表示されていない\nその文は誤りであり、Valve自身の弁護士たちがそれを証明している。 2025年10月1日付の弁護士書簡の第1.9項には、1台のデバイスと数十のアカウントを結びつけるデバイスレベルの相関関係について記載されている（付録A). 同回答には、保存記録が830ページ分添付されていた（付録B). それらはどれも「アカウントデータ」ページには表示されていません。\nこのアカウントがAPIキーのログを要求した理由\n\n彼はその4つのカテゴリーを無作為に選んだわけではない。そのlocalhost 彼のアカウントのキーはスクリプトによるものという証拠であり、開発者ページに実際のドメインを入力している人物によるものではない (第5節,第6節). 誰が、どこから作成したかを示す唯一の記録は、APIキーの登録ログです。それが彼が最初に求めたものでした。そして、それがクロージャー側が隠していたものなのです。\n\n出典：本プロジェクトの調査におけるアカウント所有者。上記のチケットのスクリーンショットにはハッシュ処理が施されており、キーページは公開されていません。\n\n評価 · PhishDestroy\n\n質問が未解決のままチケットをクローズするのは、ここでは偶然のことではありません。それが通常の結果なのです。私たちは16,319 苦情およびサポート記録の保存 そして重複を除いたサポート交換件数：354件 それらから引用したものです。このチケットは、その形態を如実に表した、日付入りの完全な例の一つです。\n\nサポートチケット — 保存済みHT-2YBP-F7JP-D4VB\nリクエストの種類GDPR第15条（データ主体によるアクセス請求）\nチケットの状況2026年9月19日 閉鎖 — データなし\n取引所のエージェント「ローゲン」（9月17日）、「カル」（9月19日）\n提出済み2026年9月16日\n要求されたデータこのアカウントに紐付けられているWeb APIキーを登録したのは誰か、またそのIPアドレス／デバイス／タイムスタンプは何か\n引用された法的根拠GDPR 第15条 — 個人データへのアクセス権\n法的枠組み：第12条第3項は、管理者に受領日から1か月間の期間を定めている（正当な理由があれば延長可能）。本稿の公表時点ではその期間は満了しておらず、本資料においても期限違反は主張されていない。 異議は内容に関するものである。最終回答ではセルフサービスページへのリンクが示されているものの、名指しされた4つのデータカテゴリーが提供されたことは示されておらず、また、管理者が措置を講じない場合、第12条第4項に基づき、その理由および苦情申立の手順を明示することが義務付けられている。しかし、最終回答にはそのいずれも記載されていない。\nなぜこの特定のデータが重要なのか\n\nWeb APIキーのイベントログとは、第三者が盗まれたセッションクッキーを使用してキーを登録したかどうかを示す記録であり、 これは、本資料のアーカイブに保存されている在庫盗難に関する苦情に記載されている仕組みである。 APIキーを誰が、どのIPアドレスから、いつ登録したかを公開すれば、以下の効果が得られます：\n\n被害者が、API作成時のIPアドレスと自身のログイン履歴を照合できるようにする\n既知のフィッシング／ギャンブル用ボットインフラに関連するデータセンターのIPアドレスを特定する\n当該行為者に対する民事または刑事手続において利用可能な証拠を提出する\n鍵が作成された際に、アカウント所有者に通知があったかどうかを表示する\n記録によると： Valveは、デバイスレベルおよびアカウント間の関連付けに関する記録を保持している。2025年10月1日付の同社の弁護士による書簡にその内容が記載されている（付録A「証拠に関する覚書 — 資料1」参照）。 チケットHT-2YBP-F7JP-D4VBでは、データ主体から同種の記録の開示が求められたが、当該チケットはセルフサービスページへの案内をもってクローズされた。データ主体によれば、そのページには当該記録は含まれていなかったという。 その拒否が合法であるかどうかは監督当局が判断すべき問題であるが、その結果として、当該データの対象となる個人はその記録を入手できないこととなる。\nそのやり取り――3日間で4通のメッセージ\n\n2人のSteamサポート担当者が、チケットに記載されたファーストネーム「Logen」（9月17日）および「Kal」（9月19日）で返信しました。両者とも、依頼者を「アカウントデータ」ページに案内しました。 チケットからは、このリクエストがValveのプライバシーチームやデータ保護責任者に届いたかどうかは一切確認できず、また、資料には担当者が誰であるか、その役割は何か、あるいはチケットがどのようにルーティングされたかについては明記されていない。\n\n9月16日\n第15条に基づく請求（4つの指定データカテゴリーを記載）\n9月17日～18日\nアカウントデータへの参照；依頼者がDPOへのエスカレーションを要請\n9月19日\n同じ紹介元でチケットがクローズされた。データがなく、根拠も明記されていない。\nGDPR第15条は、データ主体にどのような権利を明示的に認めているか\n第15条第1項(a)データの処理目的 — Valveがデータを保有する理由\n第15条第1項(b)データのカテゴリ — Valveが持つもの\n第15条第1項(c)受給者または受給者の区分 —データを受け取った者（例：APIキーの保有者）\n第15条第1項(d)保存期間、またはその決定基準\n第15条第3項処理中の個人データの写し、すなわちAPIキーのログそのもの\n第12条第3項回答期限は1か月 受領日から；延長については、その月内に通知しなければならない。本誌発行時点では、その期間はまだ満了していなかった。第12条第4項： 監督機関が措置を講じない場合は、その理由を明示するとともに、申立人に対し、苦情申立の手続きについて通知しなければならない。\n規制当局への苦情申立ての手続き — すべてのユーザー向け\n\nValveに対してGDPR第15条に基づく請求を提出したにもかかわらず、適切な回答（またはデータが含まれていない定型的な拒否回答）を受け取らなかったユーザーは、 自らが所在するEU／EEA加盟国の監督当局に苦情を申し立てることができます。 ValveのEUにおける事業所であるハンブルクのValve GmbHを管轄する監督当局は、ハンブルク州データ保護・情報公開担当官（HmbBfDI）。（Valveの第27条に基づく代理人もハンブルクに所在しているが、代理人の住所だけでは管轄当局は決定されない。）また、第77条に基づき、申立人の所属する加盟国の当局に対して苦情を申し立てることもできる。\n\nHmbBfDI 苦情申告書 ↗ GDPRの条文（第12条、第15条、第77条） ↗ アーカイブ済み 2026-09-20 ↗EDPBのガイドライン ↗\n\n苦情に関するチケット番号：HT-2YBP-F7JP-D4VB — 実例として、この資料に記録されている。\n\n記録されている事例が1件\n記録は存在しているが、データ主体はそれを受け取っていない。\n\nValveの代理人は、2025年10月1日付の書簡において、デバイスレベルの相関記録について説明した。 2026年9月19日、同種の記録に対する第15条に基づく請求は、法的根拠の明示なしに、請求者が「当該記録が含まれていない」と報告したセルフサービスページへの案内をもって終了した。 チケット番号HT-2YBP-F7JP-D4VBはその一例として記録されている。これがより広範な慣行を反映しているかどうかは、監督当局が判断すべき問題であり、監督当局はValveに対し、その処理記録の提出を求めることができる。\n\nGDPR第12条、第15条、第77条／監督当局\n\n第12条および第15条に基づく苦情は、費用を負担することなく、関連する監督当局に直接申し立てることができます（第77条）。 監督当局は、アクセス請求への応諾命令を含む是正措置を命じ、また、データ主体の権利の侵害に対しては、第83条第5項(b)に基づき罰金を科すことができる。 元のチケット参照番号および「Valve」という応答（または応答がないこと）を保存しておくことで、苦情の説得力が高まる。\n\nDSARテンプレートを見る →\nパートC — 法的枠組み · 第19節 · 契約法\nプラットフォーム独自のアーキテクチャに反する利用規約\n文脈と出典の制限\n\n著者らは弁護士ではなく、本記事の内容はいずれも法的助言ではありません。SSA（社会保障法）の引用は2026年9月10日改訂版に基づくものです。改訂版によって文言が異なる場合があり、また条項の番号付けも改訂ごとに変更されています。問題となっている行為がどの版に基づいて規定されていたかを確認の上、該当する条項を照合してください。 第25条および第32条に基づく主張は、規制が何を要求しているかを述べたものであり、監督当局が違反を認定したことを示すものではありません。主張1に記載された数値には、第13条に定められた適用範囲の制限が反映されています。\n\nSSAの主要な規定のうち3つは、プラットフォームの構築方法と相容れない点がある。具体的には、高額な取引をプラットフォーム外へ追いやる市場価格の上限設定に対する商用利用禁止条項、 2023年以前は二要素認証を必要としなかったキーエンドポイントに対するAPIキーの利用者責任条項；および、事業者ごとの執行実績が示されていない公開記録に対する執行に関する文言。これらの矛盾が執行可能性に影響を与えるかどうかは裁判所の判断に委ねられるが、本節では、裁判所が審理の際に参照することになる事実関係を整理する。\n\n論点1 / 時価総額の仕組み\n市場の天井価格と商業利用の禁止\n\n「Steamコミュニティマーケット」の出品価格の上限は約$1,800です。過去のスナップショット（2026年9月23日）によると、5つのマーケットプレイスにおいて、248のCS2アイテムカテゴリについて、そのうち2つ以上のマーケットプレイスで、その上限価格を2以上上回る価格が個別に設定されています。そのようなアイテムはValveの自社プラットフォームでは、その価格では販売できません. そうした価格を希望する所有者は、SteamアカウントとSteam API上で稼働するサードパーティのマーケットを利用しています。SSAは、明示的に許可されていない限り、これを商用利用とみなします。\n\nアイテムがマーケットの上限を超える → サードパーティのマーケットがその差額を補う → それらのマーケットは Steam アカウントと Steam API を使用している → SSA は許可のない商用利用を禁止している → 許可に関する登録簿は公表されていない。 コミュニティ・マーケットの合計手数料約 15% は、マーケット内で成立した販売にのみ適用され、これらの外部取引には適用されません。\n論点 2 / API キーのセキュリティアーキテクチャ\nAPIキーの脆弱性は、ユーザーの不注意というよりも、プラットフォームの設計上の問題である\n\n2023年以前、SteamのAPIキー生成エンドポイントは、盗まれたセッションIDを含むPOSTリクエストを受け入れ、高権限の認証情報を生成していたメールによる確認、2段階認証、または端末認証がない場合. 本調査で収集されたAPIハイジャックに関する苦情は、すべて同じパターンに従っています。すなわち、攻撃者のスクリプト、セッションクッキーの盗用、密かな鍵の生成、取引の傍受という流れです（リクエストのペイロードは第8節に示されています）。\n\nGDPR第25条（設計段階からのデータ保護）および第32条（処理のセキュリティ）では、リスクに応じた適切な技術的措置を講じることが求められている。 第二の認証要素や所有者への通知なしに、取引の傍受を可能にする認証情報を発行することは、管理者の設計上の問題である。そのような背景において、ユーザーに責任を課すSSA条項が有効であるかどうかは、裁判所および監督当局が判断すべき問題である。\n\n論点3 / リアルタイムでの可視性\nValve は、ログインのたびに認証用ホスト名を受け取ります\n\n認証ホスト名は、プレーンテキストで Valve の OpenID エンドポイントに送信されます。openid.return_to そしてopenid.realm （リクエストの形式は第3節に示されている）。その抽出は標準的な操作である。2026-09-22時点において、26組のペアでは、メインドメインがリンクフィルタの対象となっていた一方で、そのSteamログインを担うホストは対象外であった。 Valveは事業者ごとの適用記録を公開していないため、これらのホストに対してリンクフィルタ以外の措置が適用されたかどうかは、公開データからは確認できない。\n\n費用は誰が負担するのか\n過去寄せられた苦情に見られる傾向\n\n調査対象となった苦情において、APIキーの乗っ取りに関する申し立てに対するSteamサポートの対応は、すべて同じパターンに従っています。すなわち、復旧を拒否し、アカウントおよびそのAPIキーに対する責任はユーザーにあると指摘した上で、チケットをクローズするというものです。本報告書では、影響を受けたアカウント数や損失額に関する総計は推定されておらず、そのような数値の出典も確認されていません。\n\n問題は、個々のユーザーがミスを犯したかどうかではありません。問題は、2023年まで、盗まれたクッキーを用いたPOSTリクエストによって、通知も二要素認証もなしに、高権限の取引認証情報が作成されてしまうようなアーキテクチャについて、誰が責任を負うべきかということです。\n「文書としてのSSA」と「契約としてのSSA」\nこの記録を審査する裁判所は、SSAを単独で解釈することはないだろう。\n\n同文書は、デバイスレベルの相関関係、認証ホストの登録日、バッチ登録のタイムスタンプ、APIキーリクエストのペイロード、および2016年7月の通知から2026年9月時点で依然として稼働しているプラットフォームまでの10年間について記載された、2025年10日付の弁護士からの書簡と併せて読まれることになるだろう。 これこそが、Valveが対応しなければならない記録である。\n\n記録に反するSSA／要点\n「商用利用禁止」— マーケットの上限設定により、高額な取引は第三者の商用市場へと流れている\n「APIキーの責任はユーザーにある」— 2023年まではキーエンドポイントでの二要素認証は実施されない\n「違反者に対しては取り締まりを行っている」――2016年7月以降、事業者ごとの取り締まり実績は公表されていない\n「利用規約に同意しました」――ハイジャックの手口では、同意はアカウント所有者ではなくスクリプトによって送信される\n結論 ・ 記録から明らかになった事実と、我々の主張\n調査結果。私たちが求めている記録。\n文脈と出典の制限\n\n以下の各調査結果は、上記の各セクションに記載された日付入りの公的記録と関連しています。これらの要請は、本調査では入手できない唯一の事項、すなわちValve自身の執行、アクセス、および処理に関する記録について、その開示を強制できる当局に対して行われています。\n\n各要請は、日付が明記された調査結果に基づいています。当局は、この公開情報に基づく調査では入手できない記録の開示を求めることができます。\n\n公的記録が示すところによると\n44の稼働中のプラットフォームは、個別の登録可能なドメインを通じて認証を行っています。そのうち27はルートごとのエビデンスファイルが公開されており、17は手動で収集されたもので、別途リストアップされています。 2026-09-22時点では、26組のペアについて、Steamリンクフィルターでメインドメインがブロックされていたが、そのログイン情報を扱うホストはブロックされていなかった — csgogem.comがブロックされ、api.csgem.com 2014年3月から登録されています。Steamはそのホスト名を受け取ります。openid.realm そしてopenid.return_to ログインするたびに。第3節\n2016年7月13日、Valveはこの仕組みを公に指摘し、その使用を禁止した。また、同機関の弁護士が2016年7月20日に送付した通知では、10日間の期限が設定された。その期限から10年が経過したが、事業者ごとの執行記録は公表されていない。第11条\nSteam Web API キーのエンドポイントは、2023年以前は、2要素認証を行わずに、セッションクッキーのみに基づいて、高い権限を持ち、取引が可能な認証情報を発行していました。第5節\nGDPR第15条に基づく請求（チケット番号 HT-2YBP-F7JP-D4VB）は、3日後にセルフサービスへのリンクのみが記載され、データは提供されないままクローズされました。第18条\n各当局にお願いしたいこと\nワシントン州ギャンブル委員会\n2016年のファイルを再度開いてください。10日間の通知後に、どのアカウント、ボット、リターンホストが無効化されたか、またその後どのオペレーターがアクセス権を回復したかについて、オペレーターごとに詳細な報告を求めてください。第2節\nHmbBfDI（ハンブルク；Valve GmbH）\n第15条に基づく回答がデータ管理者の義務を満たしていたかどうかを検証し、加害者の特定に関連するAPIキーの登録およびアクセス記録の開示を求める。第18条\nDSAデジタルサービスコーディネーター\nauth-hostのルーティングをレコードに「通知」として記載し、その情報が記録された後、Valveの対応が義務を満たしているかどうかを評価する。第16条\nデータ主体\nご自身のアカウントについて同様の記録を請求する際は、第15条のテンプレートをご利用ください。保存された記録を確認することで、リセットを実行した人物や鍵を作成した人物を特定することができます。付録G\n\nこれら4つの要求の根底にある唯一の要望は同じである。すなわち、Valveのみが保有する執行、アクセス、および処理に関する記録を公開することだ。ホームページ上の警告、10日間の通知書、セルフサービスページは、いずれも管理権の行使を示すものである。管理権が行使されたかどうかは、公的記録からは判断できないが、規制当局であれば判断できる。\n\n付録 — 主要な証拠資料および作業資料\n付録A — 弁護士との書簡のやり取り\n証拠概要書 — 情報源1から提供された資料\n\n第1条、第18条および第19条において根拠とした弁護士との書簡の根拠資料および出典状況。\n\nエビデンスの根拠および情報源の状況 — 情報源1から提供された文書\n今回の監査のきっかけとなった永久利用停止処分を受けたユーザーは、本監査の対象ではありません。その処分が正当であったかどうかはここでは検討されておらず、本報告書はその処分を擁護も反論もしていません。重要なのはアカウントそのものではなく、その内容です：出典 1 — 自身のGDPRに基づく情報開示請求のデータ主体として、Valveの弁護士から以下の書簡を受け取った、アカウント停止処分を受けた当人は、その書簡と添付の事件記録、およびそれらを公に閲覧する権利を当方に提供した。氏名は伏せられている。文書は、日付、作成者メタデータ、およびハッシュ値によって識別される。\n\nその書簡は、GDPR／DSARに基づく請求に応じて送付されたものです。その過程で、Valveの代理人は、Steamサポートが以前、ユーザーに対して技術的に不可能であると伝えていた機能について説明した声明書に署名し、記録に残しました。以下に引用する段落は、その声明書の内容です。\n\n著者らが生成されたログ抽出データについて行ったさらなる分析は、本資料からは省略 独立した審査の結果が出るまで保留とする。本調査の他のいかなる部分においても、これを根拠としていない。\n\n記録に残された事実：継続的なデバイスレベルのテレメトリ\n\nValveの弁護人によるものとされる書簡の1.9項において、Valveの弁護人らは次のように述べている：「2019年から2023年にかけて、このアカウントは主に、数十件の盗まれたSteamアカウントへのログインにも使用されていた端末から利用されていました。」\n\n事実： Valveの弁護人は、4年間にわたるアカウント間のデバイスレベルでの関連付けについて説明している。Steam サポート部門は、盗難被害者に対し、盗難品の追跡やアカウントとデバイスの紐付けは技術的に不可能であると伝えていた。 Steam Guard デバイスの認証に関する情報は公開されているため、デバイスごとの記録が存在すること自体は目新しいことではない。目新しいのは、それらの記録が保持されており、複数年にわたりアカウント間で相関付けられていることを、弁護人が書面で確認した点である。\n\nこれが重要な理由： 4年間にわたり、1台の端末と数十の乗っ取られたアカウントを結びつけることができる相関関係は、サポート部門が被害者に対して利用できないとしたのと同じ種類の記録である。 この種の記録があれば、盗難・転売の連鎖におけるアカウントや端末を特定することが可能となる。どのような記録が存在し、どのくらいの期間保存され、どのような根拠に基づいてデータ主体への開示が差し控えられるのか――これらは監督当局が検討すべき問題である。\n\n出典：2025年10月1日付のValveの弁護人からの書簡、第1.9項、およびその830ページにわたるPDF形式の付録・GDPR第15条に基づく請求に応じて情報源1が受領したもの・付録のSHA-256ハッシュ値は以下に記録されているdisclosure-audit.json ・手紙そのものは掲載されておらず、口座名や第三者からのデータは省略されています。\n\nステータス：開く\n出典資料は、エビデンスアーカイブから入手可能です。\n付録B — 生成されたPDF・編集内容の確認\n提出されたPDFにおける黒塗り処理は表面的なものであり、黒塗りされたテキストも引き続き抽出可能です\n\nValveの弁護団は、GDPRに基づく情報開示請求に対し、830ページに及ぶ添付文書を提出したが、その文書では、黒塗り部分がテキストを削除するのではなく、その上に塗りつぶされていた。902,270 文字が黒いバーの下に配置され、テキスト抽出ツールを使ってそのまま抽出される — バーで非表示にされていたサードパーティの識別子も含む。ここでは集計値のみを公開しており、対象となるコンテンツは一切転載されておらず、付録自体も公開されていない。\n\n1. ジオメトリチェックで判明したこと\n\nGDPR第15条に基づく回答（日付：）2025年10月1日 これには、830ページにわたるPDF形式の付録（.NET用Aspose.PDFの生成メタデータで、作成日および最終更新日が同一）が添付されていた。著者らはページ単位のジオメトリチェックを実施した。具体的には、各ページについて、テキストレイヤーの後に描画された不透明でほぼ黒色の矩形を特定し、その下に位置する抽出可能な文字をカウントした。\n\n生成されたファイルに基づいて測定\n902,270\n黒いバーの下からまだ文字を読み取ることができる\n推定値ではなく、実数です。これは対象となるキャラクターの数を数えたものであり、犠牲者数、再特定された事例、あるいは事件の件数ではありません。\n830 / 830\n影響を受けるページ — すべてのページ\n986\n抽出可能なテキスト上の長方形\n1,329\n不透明な黒い長方形の総数\n黒いバーはテキストレイヤーの上に描画されているだけで、テキストを削除するものではありません。バーの下にあるテキストは、標準的なPDFツールを使用して抽出することができます。ここでは集計値のみを公開しており、隠されたコンテンツは一切掲載していません。\n法科学の実演：層の分離\nASPOSE.PDF FOR .NET ベクターオーバーレイのモックアップ（付録 P. 412）\n\n当該アカウントに対して提出された報告：[ログイン：redacted_user_667]\n\nユーザーによる理由：[テキスト：「ユーザーから、インベントリ内のアイテムの重複や不正な取引行為が報告されています…」]\n\n前景：<path fill=\"#000\" />欠陥：基となる UTF-8 ストリームがそのまま残っている\n出典：2025年10月1日付の弁護士書簡のPDF付録（830ページ、Aspose.PDF for .NETによる作成メタデータ） · 著者による計測、方法および1ページあたりのページ数はdisclosure-audit.json ・同じファイルに記録された付録のSHA-256・付録自体は公開されていない。\n2. なぜこれがデータ主体の対応にとって重要なのか\n\nValveの代理人は、当該情報主体からの自身の記録に関する開示請求に応じ、このファイルを当該情報主体に送付した。 そこに施された黒塗り部分は単なる外観上の処理に過ぎません。その下のテキストは削除されていないため、黒塗りによって隠蔽しようとした第三者の識別情報は、ファイルとともに受信者に渡ってしまいました。テキスト抽出ツールで除去できてしまうような黒塗りでは、何も隠蔽できておらず、受信者が何が開示され、何が開示されていないかを判断することもできなくなってしまいます。\n\n第15条第4項こそが、そうした制限が存在する根本的な理由である。すなわち、複写物を入手する権利は、他者の権利や自由に悪影響を及ぼしてはならない。この制作物は、その義務を果たしていなかった。 これが第4条(12)に基づく個人データ侵害に該当するかどうかは、監督当局が判断すべき事項である。開示そのものはファイル上で測定可能であり、同じバイト列を保有する者であれば誰でも再現可能である――SHA-256は公開されているが、付録は公開されていない。\n\nバーの下にあったのは、口座番号ではなかった。 それは、情報開示請求者に対して提出されたユーザー報告の本文であり、報告者の情報も添付されていた。Steam回のログイン記録は、1回のログインがSteamでのみ行われることはめったにないため、その背後にある人物を特定するものであった――著者らの集計によると、この文書に名指しされたユーザーのうち、60%人以上が完全に特定可能である — それに加え、彼らが書いた文章の未編集の原文も含まれている。その文章には、依頼者の国籍を非難する内容や、死を願う言葉などが含まれている。特定された人物の中には未成年者も含まれている。制作側は、取材対象となった人物に、実名が記載された記者リストを手渡した、これはまさに第15条第4項が防止することを目的として規定されている損害である。\n\nファイルの内容と同じくらい、そのファイルの並び順も重要です。 この要請に対し、当初は、依頼者の別名メールアドレスに氏名が記載されていないことを理由に、身元確認のための追加証拠の提出が求められ、その後生じた遅延の間に、当該アカウントは永久に利用停止処分となった。 第12条(3)で定められた1ヶ月を6週間以上経過してようやくデータが送付された書簡では、受取人に対し刑事訴追をほのめかし、弁護士に自身のアカウントの活動状況を説明するまで、残りのデータの提供を保留すると通告した。 この情報開示により、Valveが公の場で回答していなかった2つの疑問も解明された。提出された記録によれば、アカウントの連携は2019年まで遡っており、Valveがこれまで説明したことのない詳細な内部テレメトリデータも明らかになった。\n\n本節の適用範囲： ここでの考察は、作成されたファイルに基づいて測定された編集の仕組みに限定されています。作成されたログに関する著者らによるさらなる分析については、独立した検証の結果が出るまで公表を見合わせており、本報告書の他の部分においても、その分析結果は根拠として用いていません。\n\n証拠：2025年10月1日付の弁護士書簡およびそのPDF添付資料（監査ファイルにSHA-256が記録されている）；ページ単位のPDF測定と方法 ↗. リクエストの経緯、8ページに記載された拒否の理由、および開示された記録の性質については、PhishDestroyの説明に詳細が記載されており、「私の愛犬対GDPRのエリート弁護士たち」、2026年8月17日 ↗ アーカイブ済み 2026-08-21 ↗. ここではアカウント名やサードパーティのデータは省略されており、棒グラフで覆われている部分は一切再現されていません。\n\n送付状の8ページ目では、要請の一部を却下し、その理由を文書で明記している： Steamプラットフォームの他のユーザーの個人情報を保護するため、これ以上の詳細な情報提供は…できません。 — 他のSteamユーザーの個人情報を保護しなければならないため、これ以上の詳細な回答はできません。830ページに及ぶ付録も同封されていました。 黒塗りされていたのは口座番号ではなく、請求者に対して提出された報告書であり、作成者の氏名が明記され、未編集のメッセージが添付されていた。口座名義人は、弁護士を通じてValveに対し、自身のファイルの開示を求めていたが、そこから抽出できたのは他人の情報だった。 この付録の内容において、誰が黒塗りを行ったかは問題ではない。ここで明らかになるのは、情報開示を差し控える根拠として主張された保護措置が、まさにこの開示資料そのものが、同じ封筒の中で、同じ日に、その保護を果たせなかったということである。\nサポートおよび法的文書に関する添付資料\n\n出典: https://phishdestroy.io/steam_dossier/ja/index#exhibit-gallery-section\n\n付録D — ソースの収集\n選定された一次資料\n\nアーカイブから6件の記録――Valveのトラッカーにある3件のGitHubイシューと、サポート対応の結果をめぐる論争が記録された3つのRedditアカウント。各情報源は、その主張、保存されたテキスト、およびそこから生じる疑問と結びつけられたままとなっている。\n\n1 / 6 選択されたレコード\nソースレコードを選択してください\nGH-01 / GITHUB保存済みのビルドで開く\n2016年に要求されたハードウェアキー\n\nValveSoftware / steam-for-linux · #4521 · 2016-06-27\n\nあるユーザーから、代替の2段階認証手段としてU2Fハードウェアキーに対応してほしいという要望（Valve）が寄せられました。保存されたこの課題には「機能リクエスト」と「レビュー済み」の両方のラベルが付与されており、ステータスは「未解決」となっています。\n\n代替手段として、SteamでのU2F USBドングルの対応を要望します。\n\nGitHubのイシューからの抜粋 ↗\n記録された資料\nValve自身のイシュートラッカーに掲載され、「レビュー済み」とマークされた、アカウントの追加セキュリティ対策を求める日付入りのリクエスト。\n説明責任の要求\n製品の決定内容、回答日、および審査後に付与された保護措置を公開してください。\n保存されたレコードを読み込む→GitHub を開く ↗\n資料内：アカウントのセキュリティ対策 →アーカイブ #484 · ビルド 2026-09-17\nGH-02 / GITHUB保存済みのビルドで開く\n効果的なオプトアウト機能のないクラッシュレポート\n\nValveSoftware / steam-for-linux · #6459 · 2019-08-18\n\nこの報告者は、2019年8月12日時点のUbuntu 16上のSteamクライアントについて記述しています。報告者によると、crash-uploadの保存先を無効にしても、再起動後にその設定が維持されなかったとのことです。また、関連する設定も記載されています。\n\n`ServerURL` を無効にすると、再起動のたびに上書きされてしまいます。\n\nGitHubのイシューからの抜粋 ↗ アーカイブ済み 2026-04-19 ↗\n記録された資料\nクライアントの日付、オペレーティングシステム、および設定の抜粋が記載された具体的なプライバシーに関する苦情。保存されたこの問題は現在未解決です。\n説明責任の要求\n調査対象、影響を受けたビルド、およびオプトアウトを有効にした変更内容を特定してください。\n保存されたレコードを読み込む→GitHub を開く ↗アーカイブ済み 2026-04-19 ↗\n資料集：関連記録の開示請求 →アーカイブ #467 · ビルド 2026-09-17\nGH-03 / GITHUB保存済みのビルドで開く\nValveに認証チケットの悪用が報告された\n\nValveSoftware / Source-1-Games · #3857 · 2022-02-26\n\n著者は、サーバー運営側がプレイヤーの接続切断後もSteamの認証チケットを保持し、誤解を招くようなサーバーリストを使用していたと主張している。この投稿では、Valveに対し、この行為について対応を求める内容となっている。\n\nサーバーが満員に見えるようにする。\n\nGitHubのイシューからの抜粋 ↗\n記録された資料\n2022年2月26日にValveのトラッカーに投稿された公開虐待報告。その保存状態は「公開」となっており、報告にはスクリーンショットへのリンクが含まれています。\n説明責任の要求\n報告された認証チケットの不正利用について、調査結果および是正措置の記録を作成してください。\n保存されたレコードを読み込む→GitHubを開く ↗\n資料内：データセットの範囲 →アーカイブ #768 · ビルド 2026-09-17\nRD-01 / REDDIT著者のプロフィール\n44件の係争中のマーケット購入\n\nr/DotA2 · 投稿者名非公開 · 2022-07-07\n\n著者は、2022年7月6日に「Market」で44件の不正な購入が行われ、損失額はおよそ$500+だったと報告している。また、二要素認証が有効になっていたとし、サポートから定型文の返信が繰り返し送られてきたと述べている。\n\n2件目のチケットを提出しましたが、Steamからは、まだ自動生成された定型文ではない返信が届いていません。\n\nRedditの投稿からの抜粋 ↗ アーカイブ済み 2025-03-20 ↗\n記録された資料\n紛争の対象となった購入に関する過去の記録で、取引のスクリーンショットやサポートからの回答へのリンクが含まれています。金額や経緯については、著者の報告に基づいています。\n説明責任の要求\n異議のある購入について、取引ログおよびセッションログと照合してください。サポート部門の判断の根拠を説明してください。\n保存されたレコードを読み込む→Redditを開く ↗アーカイブ済み 2025-03-20 ↗\nこの資料の項目：支援と執行 →アーカイブ #4,533 · ビルド 2026-09-17\nRD-02 / REDDIT著者のプロフィール\n永久利用停止および異議申し立ての受付停止\n\nr/ohnePixel · 投稿者名は非公開 · 2024-12-09\n\n著者は永久利用停止処分に異議を唱え、その根拠として、アカウントの譲渡の疑いやコミュニティからの通報が挙げられたと述べている。また、解決済みのチケットや、自身の個人データの開示を請求する計画についても説明している。\n\n自分の状況を説明し、詳細を尋ねたのですが、彼らは決定を曲げず、私のチケットをクローズしてしまいました。\n\nRedditの投稿からの抜粋 ↗\n記録された資料\n保存されたアピールアカウント。これには、投稿者が「サポート」として挙げた理由や、4枚の画像へのリンクが含まれています。投稿日は、選択した「サポート」のエクスポートデータに基づいています。\n説明責任の要求\n恒久的な利用停止処分を裏付ける根拠と、これに異議を申し立てるために利用できる審査手続きを特定してください。上訴手続きが終了したからといって、その決定の理由が説明されたことにはなりません。\n保存されたレコードを読み込む→Redditを開く ↗\n資料集：関連記録の開示請求 →アーカイブ #4,766 · ビルド 2026-09-17\nRD-03 / REDDIT著者のプロフィール\nリカバリ・リセットと、報告された「-0」の損失\n\nr/legaladvice · 投稿者名非公開 · 2025-05-09\n\n著者は、他者が復旧リクエストを送信した後、サポート側が認証情報をリセットし、アカウントの保護機能を無効にしたと主張している。また、非アクティブなアカウントから約US$10,000が流出したと報告している。\n\nSteam サポートにパスワードのリセットを依頼したところ、アカウントのセキュリティ設定がすべて無効にされてしまいました。\n\nRedditの投稿からの抜粋 ↗\n記録された資料\nアカウントのセキュリティ対策が、復旧プロセスによって無効化されたという主張が記録されている。保存された投稿には、著者がサポートから伝えられたという内容が記されている。\n説明責任の要求\nリセットを承認した人物、承認された本人確認資料、およびアクセスログを特定してください。アカウントの復旧は、セキュリティシステムのValve管理措置の一部です。\n保存されたレコードを読み込む→Redditを開く ↗\n資料集：関連記録の開示請求 →アーカイブ #4,592 · ビルド 2026-09-17\n\n6件のレコードが選択されました。GitHubのステートには、保存されたビルドの詳細が記載されています。Redditの投稿には、投稿者のアカウント情報が保持されています。\n\n6曲の楽曲をダウンロード ↓\n\n検索可能なビルドには以下が含まれます16,319 件の異なるレコード: 393件のTrustpilot、5,635件のReddit、2,395件のGitHub、276件のWeb、および7,620件のWikiの記録。複数の記録が同一の事象に関する場合があります。別途用意された40,448行のマスターエクスポートは、対象範囲が異なります。\n\nアーカイブ全体を検索 ↗ ・マニフェストをビルド ↗ ・データセットの範囲と件数 →\n\n付録E — 事例研究\nArchiSteamFarm および自動化条項\n\nオープンソースのカードファーミングツールであり、そのFAQには数百万のアカウントで稼働していると記載されているが、自動化を禁止する利用規約（§ 4.C）に抵触している。 その仕組み――ファームが何かを生み出す前にValveから購入しなければならないもの、カードを現金化するあらゆる方法がライセンスに違反する理由、執行実績、そしてカード経済を管理する主体――については、以下に詳しく記載されている。別紙V ↗.\n\n「Steam」加入者契約の第4.C項には、次のように規定されています。\n\n「いかなる形式のスクリプト、ボット、マクロ、またはその他の人間による制御を受けていないシステム（以下「自動化システム」といいます）も、Steam上のコンテンツおよびサービスと何らかの形でやり取りするために使用してはなりません。」 —Steam 利用規約 第4.C条（現行） ↗ アーカイブ済み 2026-09-18 ↗\n\nValveはこの条項を徹底して適用します。その点において非常に優れています。 のよくある質問（FAQ）ArchiSteamFarm (ASF) — そのドキュメントによると、次のような環境で動作すると説明されているオープンソースツール数百万以上の Steam アカウント 11年以上前の最初のリリース以来――ボットネットワークを運営していたユーザーを永久追放した3件のSteamサポートメッセージを再現している。Valveはそれらのネットワークを発見し、その名称を特定し、排除した。したがって、重要な問題は、Valveが大規模な自動化を検知できるかどうかではない。\n\nこのプロジェクトの公式サイトArchiSteamFarm よくある質問 禁止措置のリスクについて直接言及している：\n\n「ASFは11年以上前に初めてリリースされて以来、数百万を超えるSteamアカウントで使用されていることを考えると、その可能性は極めて低いと言えるが、実際の確率にかかわらず、依然として可能性は残っている。」\n\n「Valve」は、ここで述べられているように「Steam」の「怠け者」が存在することを明確に認めている。だから、私としては、もし彼らがそれを快く思っていなければ、VACの観点から問題を引き起こす可能性があると指摘するのではなく、とっくに何らかの対策を講じていたはずだと確信している。ここで重要なのは、ゲームの「アイドル」ではなく、例えばASFのような「Steam アイドル」です。\"\n\n— ArchiSteamFarm FAQ、JustArchiNET。出典：GitHub wiki ↗ ・逐語的に確認済み 2026-09-22\n\n同じFAQでは、「それでアカウント停止になった人はいますか？」という質問に対して、次のように回答しています。はい, そして、Steam Supportがそのうち3人に送ったメッセージを以下に転載します：\n\n1,000+ ボット · 取引禁止\n「このアカウントは、ボットアカウントのネットワークを管理するために使用されていたようです。ボットの使用は、Steam利用規約に違反します。」\n\n170以上のボット・永久BAN、2017年ウィンターセール\n「このアカウントは、Steamにおいて、収集用カードを違法に収集する目的のほか、関連する活動や商業活動以外の活動にも使用されていました。当該アカウントは永久に利用停止となっており、Steamサポートではこの件に関してこれ以上のサポートを提供することはできません。」\n\n120以上のボット · 永久BAN\n「このアカウントやその他のアカウントは、当社のネットワークインフラへの過剰なトラフィックを送り込むために使用されましたが、これはSteamのオンライン行動規範に違反する行為です。」\n\n— Steam ArchiSteamFarmのFAQにある「それでアカウント停止になった人はいますか？」というセクションに掲載されている応援メッセージ。出典 ↗ ・逐語的に確認済み 2026-09-22\n\n2つの記録を並べてください。 1,000のファーミングボットを所有する個人ユーザーが特定され、「ボットの使用はSteamの利用規約違反である」と通告された後、永久にアカウントが削除された。 本報告書に記載されている商用プラットフォームは、中核事業としてはるかに大規模な自動運営の Steam アカウントを運用しており、ログインのたびに Valve 独自の OpenID を通じて認証を行っていますが、いずれのプラットフォームについても、オペレーターごとの措置記録は公表されていません。その条項は有効だ。問題は、それが誰を対象としているかということだ。\n\nASFはここでは何ら非難されておらず、Valveの立場に対する解釈はASF独自のものである――その著者は「ASFはValveから権限を与えられていない」と明言している。 このツールはここでは測定器として用いられている。すなわち、Valveがボットネットワークを検知し、その名称を文書で明記し、永久に利用停止処分にしていることを示している。Valveは、自らが認可している商用自動化ツールを公表し、それ以外のものに対してどのような措置を講じたかを事業者ごとに記録として示すことで、この問題をひと文句で決着させることができる。\n\nカードファーミングがValveの収益に与える影響\n\n「Steam」コミュニティマーケットでは、ゲーム内で獲得したトレーディングカードが販売されており、同マーケット内で成約した販売ごとに合計で約「15%」の手数料がかかります。 カードを受け取るには、アカウントがSteamで$5.00 USDを消費している必要があります；また、カードを入手するには、ゲームの所有権またはゲーム内購入が必要です。 ここでは総収益額の推定値は示されていません。運営規模については、ASFのFAQに記載されている通りです。また、FAQにはValveの区別点が記載されています。\"Steam アイドラー\" （カード集め）出典：「ゲームのサボり屋」; 詳しくはASF よくある質問 ↗. その仕組みについては、以下に詳しく説明されています。別紙V — 目盛り そして商用利用の落とし穴.\n\n件名ArchiSteamFarm — 自動化されたカード収集\n記載されたスケール数百万のアカウント（ASFのFAQによる — 正確なアクティブユーザー数は未確認）\n「数えた」であって、「引用した」ではない10,880,610 ASF独自のSteamグループに含まれるAPIエントリの総数（Steamに示されているように、5,360,499は制限なし）――FAQの「数百万」というのは誇張ではなく、単純な件数である。 88.97%には、いかなる種類のSteam禁止措置も課されていない。全面禁止に関する調査結果 ↗\nツール自体のドキュメントに記載されている情報\nASFは（プロジェクトのドキュメントに従い）、Steamクライアントを起動せずに、ヘッドレスモードでアカウントにログインし、カードドロップを待つためにゲームをアイドル状態に保ちます。\nFAQでは、Valveは「Steamの怠け者たち」の存在を認識しており、「もし彼らを快く思っていなければ、とっくに何らかの措置を講じているはずだ」と説明しています。\n（FAQによると）11年以上、対象を絞った取り締まりは報告されておらず、コミュニティマーケット内でのカード販売により、Steamの手数料総額は約15%となっています。\nFAQでは、オペレーター1人あたりの推奨上限を10アカウントと定めており、その根拠としてValveを挙げています。「この推奨事項は、社内のValveガイドラインおよび当社独自の提案に基づいています。」Valveからは、そのようなガイドラインは公表されていません。\n同じFAQによると、技術的な上限は「1つのIPアドレスと1つのASFインスタンスで、最大100～200個のボットを実行できます」となっています。\n「ファーム」によるプレイ時間は Valve によって記録されており――「通常、30分ごとに更新される」――、§ 4.C では「ゲームプレイ統計の偽装（例：勝利数や敗北数、XP、プレイ時間の水増し）」が禁止行為として挙げられている。\n出典\nJustArchi ASF 公式FAQウィキ ↗ ArchiSteamFarm リポジトリ ↗ アーカイブ済み 2026-09-24 ↗\n自動化に関する条項は明確に規定されています。ASFのFAQでは長年にわたり、このツールが数百万のアカウントで稼働していると記載されており、これに対する標的型の取り締まりが報告されたことはありません。規則とその適用との間に隔たりがあることは記録上明らかですが、その理由についてはここでは明らかにされていません。\n展示の全容カード経済：その仕組み、規模、ライセンス、そして誰が管理しているのか ↗農場が1枚のカードを生産する前にValveから購入しなければならないもの； その影響によってカードファーミングを定義している§ 4.Cの2行；なぜカードを換金するあらゆる方法がライセンスに違反するのか――Valveが記述した一方で、Valveは入り口で手数料を徴収している； 2025年6月のVACの波や、電話番号の共有による連鎖的な利用禁止措置を含む執行記録；そして、Steam周辺でカード取引および利用禁止リストの管理業務を行っていたValveの従業員およびコミュニティモデレーター。禁止措置の調査私たちはValveに農場の広さを尋ねたりはしなかった。実際に数えてみたのだ。↗10,880,610 アカウント（制限あり・なし）は、ArchiSteamFarm自身のSteamグループから読み込まれます。このグループには、ユーザーがグループ参加の設定のチェックを外さない限り、初回起動時にソフトウェアがデフォルトで自動参加します （これにより、商用ボットファームと、デフォルト設定のままにしている一般プレイヤーの両方が捕捉される）。88.97%にはいかなる種類のSteam禁止措置も課されていない。禁止措置が課されている11%のうち、99.8%は、取引を一切停止させない表面的なコミュニティによる禁止措置である。 SteamRepと照合した結果、リストに掲載された詐欺師のうち67.77%は、アンチチートによる禁止措置が解除されれば自由の身となる。登録日、地域、存続状況別の内訳――これは、単なる説明ではなく、測定された実際の規模である。\n\nAppendix F — Working ledger\n\nRules ledger: clauses against recorded platforms\n\nルールを選択してください。レジスタには、そのルールにタグ付けされた登録済みプラットフォームの一覧が表示され、各プラットフォームのメインドメイン、指定された認証ホスト、および保存されたリンクフィルターの結果が表示されます。アクセスがブロックされたウェブサイトや、ログイン用の別のドメインについては、そのルールに従って、残りの経路まで追跡してください。\n\n175関連するレコード\nこのルールについて\n174 主要ドメイン0 C&Dの言及\n規則抜粋／SSA §2.G\n商用利用およびアカウントへの課金\n“…exploit the Content and Services or any of its parts for any commercial purpose, except as expressly permitted elsewhere in this Agreement (including any Subscription Terms or Rules of Use).”\n記録を追う\nプラットフォーム登録 175\n数値は出典による推計値です\n\n175 175のレコードのうち\n\nサービス／親グループ\tメインドメイン／レジストリ\t確認された認証ドメイン／経過期間\tスケール／記録された応答\n\nCasino\n\tcsgoempire.com\n11.3 yearsRegistered 2015-06-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgoempirelogin4.com\n6.2 yearsRegistered 2020-07-20\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustreaper.com\n23.2 yearsRegistered 2003-06-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustreaper.com\n23.2 yearsRegistered 2003-06-24\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustly.com\n12.4 yearsRegistered 2014-05-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustly.com\n12.4 yearsRegistered 2014-05-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette Casino\n\tcsgofast.com\n11.5 yearsRegistered 2015-03-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsteam-login.authtofast.com\n83 daysRegistered 2026-06-30\nRDAP ↗ · authtofast.com (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tduelbits.com\n6.6 yearsRegistered 2020-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nswitchflips.com\n6.4 yearsRegistered 2020-04-21\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opener\n\tfarmskins.com\n10.5 yearsRegistered 2016-03-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsteam.kobal.cc\n9.7 yearsRegistered 2017-01-07\nRDAP ↗ · kobal.cc (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgoluck.com\n9.3 yearsRegistered 2017-05-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgoluck.com\n9.3 yearsRegistered 2017-05-18\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tinsane.gg\n7.5 yearsRegistered 2019-04-02\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.insane.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcs2skin.com\n3.5 yearsRegistered 2023-03-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncs2skin.com\n3.5 yearsRegistered 2023-03-06\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tjuice.gg\n7.9 yearsRegistered 2018-10-19\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nletmeinjuice.com\n2.4 yearsRegistered 2024-04-15\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tggdrop.com\n8.6 yearsRegistered 2018-02-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nggauth.com\n3.4 yearsRegistered 2023-05-03\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Casino\n\thowl.gg\n9.5 yearsRegistered 2017-03-16\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhowl.uno\n41 daysRegistered 2026-08-11\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tchicken.gg\n5.7 yearsRegistered 2021-01-11\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nchicken.gg\n5.7 yearsRegistered 2021-01-11\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgocasino.gg\n2.6 yearsRegistered 2024-02-17\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.csgocasino.gg\n2.6 yearsRegistered 2024-02-17\nWHOISFREAKS ↗ · csgocasino.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Casino\n\thunt.gg\n6.9 yearsRegistered 2019-11-04\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.hunt.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Battles\n\tcsbattle.com\n9.8 yearsRegistered 2016-12-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsbattle.com\n9.8 yearsRegistered 2016-12-10\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskinrave.gg\n3.1 yearsRegistered 2023-08-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinrave.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsdouble.gg\n261 daysRegistered 2026-01-03\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsdouble.gg\n261 daysRegistered 2026-01-03\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustchance.com\n8.0 yearsRegistered 2018-10-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhgfuihd.com\n7.6 yearsRegistered 2019-01-27\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Automation\n\tcobaltlab.tech\n3.5 yearsRegistered 2023-03-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncobaltauth.com\n1.7 yearsRegistered 2025-01-07\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\traided.gg\n171 daysRegistered 2026-04-03\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.raided.gg\n171 daysRegistered 2026-04-03\nIP2WHOIS ↗ · raided.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustneo.gg\n1.3 yearsRegistered 2025-06-20\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustneo.gg\n1.3 yearsRegistered 2025-06-20\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tsplits.gg\n3.7 yearsRegistered 2023-01-23\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsplits.gg\n3.7 yearsRegistered 2023-01-23\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Upgrader\n\tupgrader.pro\n1.2 yearsRegistered 2025-07-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nupgauth.space\n38 daysRegistered 2026-08-14\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskin.fans\n8.2 yearsRegistered 2018-07-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skinfans.com\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\thotpizza.one\n1.8 yearsRegistered 2024-12-07\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhotpizza.one\n1.8 yearsRegistered 2024-12-07\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tg4skins.com\n10.1 yearsRegistered 2016-08-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.g4s.to\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2royal.com\n4.1 yearsRegistered 2022-08-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ntf2auth.com\n5.2 yearsRegistered 2021-07-27\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2hunt.com\n8.7 yearsRegistered 2018-01-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrstspcl.com\n6.1 yearsRegistered 2020-08-08\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2.bet/coinflip\n8.4 yearsRegistered 2018-05-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ntf2.bet\n8.4 yearsRegistered 2018-05-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\topenstars.gg\n131 daysRegistered 2026-05-13\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nopenstars.gg\n131 daysRegistered 2026-05-13\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tskins.com\n25.1 yearsRegistered 2001-08-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skins.com\n25.1 yearsRegistered 2001-08-08\nRDAP ↗ · skins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\twhite.market\n9.6 yearsRegistered 2017-03-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwhite.market\n9.6 yearsRegistered 2017-03-01\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tmoon.market\n7.6 yearsRegistered 2019-02-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmoon.market\n7.6 yearsRegistered 2019-02-27\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tcsfloat.com\n5.2 yearsRegistered 2021-07-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgofloat.com\n11.0 yearsRegistered 2015-09-29\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tskin.land\n4.7 yearsRegistered 2022-01-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skin.land\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\thaloskins.com\n2.8 yearsRegistered 2023-12-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhaloskins.com\n2.8 yearsRegistered 2023-12-10\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCorporate Market\n\tbuff.163.com\n29.0 yearsRegistered 1997-09-15\nRDAP ↗ · 163.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\nbuff.163.com\n29.0 yearsRegistered 1997-09-15\nRDAP ↗ · 163.com (parent)\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\tmarket.csgo.com\n26.6 yearsRegistered 2000-02-07\nRDAP ↗ · csgo.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\ndota2.net\n14.9 yearsRegistered 2011-10-29\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRegulated Market\n\tskinport.com\n8.0 yearsRegistered 2018-09-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinport.app\n6.3 yearsRegistered 2020-06-20\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMarketplace/Swap\n\tskinflow.gg\n3.8 yearsRegistered 2022-11-26\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinflow.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tskin.place\n6.0 yearsRegistered 2020-09-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skin.place\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tskinsmonkey.com\n5.7 yearsRegistered 2021-01-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinsmonkey.com\n5.7 yearsRegistered 2021-01-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCorporate Market\n\tskinbaron.de\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinbaron.com\n10.7 yearsRegistered 2015-12-22\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Market\n\trust.tm\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\ndota2.net\n14.9 yearsRegistered 2011-10-29\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tpirateswap.com\n6.0 yearsRegistered 2020-09-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nlogin.pirateswap.com\n6.0 yearsRegistered 2020-09-22\nRDAP ↗ · pirateswap.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Marketplace\n\tmannco.store\n8.6 yearsRegistered 2018-03-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmannco.store\n8.6 yearsRegistered 2018-03-02\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tskinswap.com\n9.9 yearsRegistered 2016-11-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinswap.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\texeskins.com\n2.1 yearsRegistered 2024-08-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nexeskins.com\n2.1 yearsRegistered 2024-08-14\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tbalticskins.com\n153 daysRegistered 2026-04-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nbalticskins.com\n153 daysRegistered 2026-04-21\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tcs.trade\n8.9 yearsRegistered 2017-11-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncs.trade\n8.9 yearsRegistered 2017-11-14\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\trapidskins.com\n4.5 yearsRegistered 2022-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.rapidskins.com\n4.5 yearsRegistered 2022-03-11\nRDAP ↗ · rapidskins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\ttradeit.gg\n9.1 yearsRegistered 2017-08-21\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nconnect-tradeit.com\n4.6 yearsRegistered 2022-02-23\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\t49skins.com\n3.4 yearsRegistered 2023-04-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.49skins.com\n3.4 yearsRegistered 2023-04-19\nRDAP ↗ · 49skins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tskinvault.gg\n3.4 yearsRegistered 2023-05-06\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinvault.gg\n3.4 yearsRegistered 2023-05-06\nIP2WHOIS ↗ · skinvault.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Trading\n\taim.market\n3.3 yearsRegistered 2023-05-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\naim.market\n3.3 yearsRegistered 2023-05-22\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Sell Portal\n\tskinout.gg\n5.6 yearsRegistered 2021-02-27\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skinout.gg\n5.6 yearsRegistered 2021-02-27\nIP2WHOIS ↗ · skinout.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Trading\n\tntskins.com\n230 daysRegistered 2026-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nntskins.com\n230 daysRegistered 2026-02-03\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Portal\n\tgamerpay.gg\n6.0 yearsRegistered 2020-10-02\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ngamerpay.gg\n6.0 yearsRegistered 2020-10-02\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Scrap Swap\n\tscrap.tf\n14.0 yearsRegistered 2012-09-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nscrap.tf\n14.0 yearsRegistered 2012-09-03\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Cashout\n\tmarketplace.tf\n14.0 yearsRegistered 2012-09-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmarketplace.tf\n14.0 yearsRegistered 2012-09-19\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Cashout\n\tskins.cash\n10.5 yearsRegistered 2016-03-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinscash.live\n6.8 yearsRegistered 2019-12-05\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgo.net\n14.2 yearsRegistered 2012-07-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncn2.easylot.net\n10.0 yearsRegistered 2016-09-03\nRDAP ↗ · easylot.net (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCommunity Hub\n\tcybershoke.net\n6.8 yearsRegistered 2019-11-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.cybershoke.net\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMatchmaker Hub\n\tfastcup.net\n14.6 yearsRegistered 2012-02-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.fastcup.net\n14.6 yearsRegistered 2012-02-16\nRDAP ↗ · fastcup.net (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Analytics\n\tleetify.com\n7.6 yearsRegistered 2019-03-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nleetify.com\n7.6 yearsRegistered 2019-03-01\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Analytics\n\tscope.gg\n7.8 yearsRegistered 2018-12-10\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nscope.gg\n7.8 yearsRegistered 2018-12-10\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tools\n\ttradeupspy.com\n6.5 yearsRegistered 2020-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.tradeupspy.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMarketplace\n\tcs.deals\n9.8 yearsRegistered 2016-12-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.cs.deals\n9.8 yearsRegistered 2016-12-03\nRDAP ↗ · cs.deals (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Price DB\n\tpricempire.com\n6.6 yearsRegistered 2020-01-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\npricempire.com\n6.6 yearsRegistered 2020-01-30\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Blackmarket\n\tFSB Market\n7.2 yearsRegistered 2019-07-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nFSB Market\n7.2 yearsRegistered 2019-07-27\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nReady-Account Hub\n\tz2u.com\n26.9 yearsRegistered 1999-11-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwww.z2u.com\n26.9 yearsRegistered 1999-11-10\nRDAP ↗ · z2u.com (parent)\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Gambling\n\tcsgoroll.com\n11.6 yearsRegistered 2015-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwww.csgoroll.com\nRegistry date unavailableRegistry date unavailable\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\trollbit.com\n11.9 yearsRegistered 2014-11-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrbsnin.com\n3 daysRegistered 2026-09-18\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nLicenced Casino\n\t500.casino\n5.9 yearsRegistered 2020-11-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette/Slots\n\tcsgobig.com\n11.4 yearsRegistered 2015-04-12\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcasedrop.com\n14.8 yearsRegistered 2011-12-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\tbanditcamp.com\n12.2 yearsRegistered 2014-06-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tskinbox.com\n18.8 yearsRegistered 2007-12-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\ttastydrop.com\n6.1 yearsRegistered 2020-08-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette Casino\n\tcsgopolygon.gg\n6.5 yearsRegistered 2020-03-28\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tmagicdrop.ru\n10.3 yearsRegistered 2016-05-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nDice Casino\n\tcsdice.com\n3.8 yearsRegistered 2022-11-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUpgrader Casino\n\tskinodds.com\n1.2 yearsRegistered 2025-06-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgowin.com\n12.0 yearsRegistered 2014-09-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrash Casino\n\tcsgorun.net\n7.3 yearsRegistered 2019-06-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\topenskins.com\n3.6 yearsRegistered 2023-02-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Gambling\n\trustbet.com\n7.6 yearsRegistered 2019-02-07\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgomagic.com\n9.4 yearsRegistered 2017-05-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUpgrader/Contract\n\tcsgobounty.com\n11.5 yearsRegistered 2015-03-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tezskins.com\n27.5 yearsRegistered 1999-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\trustcases.com\n7.2 yearsRegistered 2019-06-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgoreaper.com\n11.1 yearsRegistered 2015-08-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgocases.com\n12.3 yearsRegistered 2014-06-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Upgrader\n\tcsgo-skins.com\n11.2 yearsRegistered 2015-07-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgonet.com\n8.8 yearsRegistered 2017-12-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\twtfskins.com\n9.0 yearsRegistered 2017-10-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Casino\n\tflamecases.com\n10.0 yearsRegistered 2016-09-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tgamedom.com\n11.7 yearsRegistered 2015-01-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Battles\n\tskin.club\n9.0 yearsRegistered 2017-09-04\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsc-auth.net\n7.5 yearsRegistered 2019-04-02\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tdaddyskins.com\n9.9 yearsRegistered 2016-10-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Gambling\n\trustix.gg\n1.7 yearsRegistered 2025-01-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Upgrade\n\tskins.club\n4.2 yearsRegistered 2022-07-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgohouse.org\n146 daysRegistered 2026-04-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskinrave.net\n216 daysRegistered 2026-02-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tbloodycase.gg\n19 daysRegistered 2026-09-02\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nClicker/Upgrade\n\tcsgoclicker.com\n8.3 yearsRegistered 2018-05-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustbet.gg\n4.0 yearsRegistered 2022-09-30\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcs-drop.com\n262 daysRegistered 2026-01-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\thellstore.net\n11.7 yearsRegistered 2015-01-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustloot.com\n354 daysRegistered 2025-10-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgo-case.com\n10.3 yearsRegistered 2016-05-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgogem.com\n9.9 yearsRegistered 2016-10-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\trainbet.com\n8.8 yearsRegistered 2017-11-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nservices.rainbet.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustclash.com\n5.4 yearsRegistered 2021-05-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrash Casino\n\t12cs.fail\n181 daysRegistered 2026-03-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\twww.tf2easy.com\n6.3 yearsRegistered 2020-06-02\nRDAP ↗ · tf2easy.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2blaze.com\n7.6 yearsRegistered 2019-01-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tshuffle.com\n30.1 yearsRegistered 1996-07-31\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tbuff.market\n5.9 yearsRegistered 2020-10-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tavan.market\n8.3 yearsRegistered 2018-05-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Engine\n\tcs.money\n11.0 yearsRegistered 2015-09-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.dota.trade\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tuuskins.com\n2.6 yearsRegistered 2024-01-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Market\n\tyoupin898.com\n6.1 yearsRegistered 2020-08-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tc5game.com\n10.5 yearsRegistered 2016-03-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\twaxpeer.com\n7.3 yearsRegistered 2019-05-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwaxpeer.com\n7.3 yearsRegistered 2019-05-20\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBot Trading\n\tcs.money\n11.0 yearsRegistered 2015-09-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.dota.trade\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUS Marketplace\n\tdmarket.com\n30.2 yearsRegistered 1996-07-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nOfficial Market\n\tsteamcommunity.com/market\n20.3 yearsRegistered 2006-05-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNot an external login site2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Platform\n\tlootfarm.com\n11.9 yearsRegistered 2014-10-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Market\n\trustskins.com\n7.6 yearsRegistered 2019-01-31\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tkrakatoa.com\n26.4 yearsRegistered 2000-05-15\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\tshadowpay.com\n10.1 yearsRegistered 2016-08-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nChinese Powerhouse\n\tigxe.cn\n15.0 yearsRegistered 2011-09-06\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAutomated Swap\n\tswap.gg\n9.6 yearsRegistered 2017-01-29\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCash-out Portal\n\tbitskins.com\n11.2 yearsRegistered 2015-07-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Automation\n\ttf2mart.com\n1.1 yearsRegistered 2025-08-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Auctions\n\tskinbid.com\n10.2 yearsRegistered 2016-06-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Rental\n\tlootbear.com\n8.7 yearsRegistered 2018-01-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Valuation\n\tbackpack.tf\n14.4 yearsRegistered 2012-05-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Botnet\n\tstntrading.eu\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Cashout\n\tskinwallet.com\n18.0 yearsRegistered 2008-09-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nDota 2 Market\n\tdota2market.com\n12.2 yearsRegistered 2014-07-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nServer Network\n\txplay.gg\n5.3 yearsRegistered 2021-06-13\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMatchmaking Portal\n\tesportal.com\n26.8 yearsRegistered 1999-12-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nLATAM Hub\n\tgamersclub.com.br\n11.2 yearsRegistered 2015-06-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tools\n\tepidemic.gg\n4.9 yearsRegistered 2021-11-03\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tcs2stash.com\n3.5 yearsRegistered 2023-03-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tcsgoskins.gg\n6.8 yearsRegistered 2019-12-21\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tsteamanalyst.com\n12.6 yearsRegistered 2014-02-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Exchange\n\tsteamcardexchange.net\n13.3 yearsRegistered 2013-05-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tracker\n\tdotabuff.com\n14.2 yearsRegistered 2012-06-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tracker\n\ttracker.gg\n8.9 yearsRegistered 2017-10-12\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Exchange\n\tfunpay.com\n17.0 yearsRegistered 2009-09-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nGrey Market\n\tplayerauctions.com\n26.3 yearsRegistered 2000-06-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Portal\n\teldorado.gg\n8.0 yearsRegistered 2018-09-12\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Key Market\n\tg2a.com\n24.8 yearsRegistered 2001-12-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Key Market\n\tkinguin.net\n16.8 yearsRegistered 2009-12-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nVirtual Services\n\tg2g.com\n31.1 yearsRegistered 1995-08-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Broker\n\tplayerup.com\n19.3 yearsRegistered 2007-05-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfhub.net\n2.7 yearsRegistered 2023-12-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfaccounts.com\n5.3 yearsRegistered 2021-05-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Shop\n\tbuycsgorank.com\n6.2 yearsRegistered 2020-07-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tcsgosmurfkings.com\n9.3 yearsRegistered 2017-06-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfstore.co\n8.6 yearsRegistered 2018-03-03\nWHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlvlup.com\n9.9 yearsRegistered 2016-11-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlevels.com\n10.6 yearsRegistered 2016-02-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tlevelsteam.com\n79 daysRegistered 2026-07-04\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlevelu.com\n6.0 yearsRegistered 2020-09-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\teloking.com\n12.2 yearsRegistered 2014-07-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\tboosteria.org\n11.9 yearsRegistered 2014-10-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tovergear.com\n14.4 yearsRegistered 2012-04-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tblazingboost.com\n14.2 yearsRegistered 2012-06-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\tdota2boost.com\n2.9 yearsRegistered 2023-10-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tbuyboost.com\n22.4 yearsRegistered 2004-04-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n調査の主張選定された規則／分析と解説+\n立証責任\n\n本調査では、商業利用に関する制限と、ここに記録されているサービスとの間に存在する隔たりについて検証を行っています。各活動を分類し、契約違反とみなす前に、明示的な許可があるかどうかを確認してください。コミュニティマーケットの利用料は、すべての外部取引に適用されるわけではありません。\n\nタグ付きレコードとは何か、そして何ではないか\n\n記録へのタグ付けは、当該プラットフォームが条項の適用対象となる日付入りの観察事項が書類に記載されている場合に実施されます。タグは裁定された違反ではなく、ここに記載されているプラットフォームのいずれについても、Valve による明示的な許可が当該記録上で提示されていません。プラットフォームが認可を受けている場合、その情報を公開することで当該エントリは解決されます。\n\n出典および調査方法推計、定義および範囲+\n\n上記のカウントは、選択されたルールを指します。レコードタイプは各プラットフォームごとに1回ずつグループ化されており、完全なタグはプラットフォームの詳細に表示されます。検索およびフィルタは、そのルール内で適用されます。 登録日は、保存された RDAP / WHOIS のスナップショットに基づいています。サブドメインについては、親ドメインの作成日が使用されます。登録期間のみでは、継続的な運用や認証経路が確立されたとはみなされません。現在の認証ホスト名は、UTCタイムスタンプ付きの保存されたOpenIDリクエストに基づいており、未解決のチェックではレガシーラベルは再利用されません。オブザーバーは Steam へのログイン前に停止し、Steam のリンクフィルターの状態はテストしません。 ルート観測データをダウンロード ↗ レジストリの結果をダウンロード ↗\n\nソースアーカイブを閲覧する ↗\n付録G — 拒否通知のテンプレートから原記録へ\nDSAR対応マニュアル：証拠の提出を要請する\n\nGDPR第15条に基づき、APIキーの作成、アカウントの復旧、およびサポートへのアクセスに関連する個人データの開示を請求してください。保存された記録により、誰が操作を開始したか、またプラットフォームがどのような根拠に基づいて対応したかを確認することができます。\n\n01\nタイムラインを保存してください。\n\nアカウントに関する通知、チケット、取引ID、および日付をUTCで保存してください。アカウントのセキュリティを確保し、ゲームおよび取引に適用される復旧オプションを確認してください。\n\nSteam 貿易保護に関する情報 ↗\n02\n保存されているデータの開示を請求してください。\n\nタイムスタンプ、送信元IPアドレス、キーのライフサイクルに関連するイベント、セキュリティ確認情報、およびアカウントに関連する復旧措置について情報を求めます。また、それらのデータが関係する場合には、サポートへのアクセス履歴やその受信者についても含めてください。\n\n03\n配送記録は保管しておいてください。\n\nValveのプライバシーに関する問い合わせ窓口をご利用ください。通常、回答までの期間は1ヶ月です。やむを得ずさらに最大2ヶ月の延長が必要な場合は、その最初の1ヶ月以内にその理由を説明する必要があります。\n\nValve プライバシーに関するお問い合わせ先 ↗ アーカイブ済み 2026-09-21 ↗\n04\n回答を比較してください。\n\nログとタイムラインを照合してください。記載漏れがあった場合はその理由を尋ね、必要に応じて監督当局への苦情申し立て手続きを利用してください。回答内容は、受け取った通りの状態でそのまま保存してください。\n\n適用範囲／第15条\n\nアクセス権の対象は、ログ内のデータを含む、保持されている個人データに限られます。すべての内部文書、復元された記録、または他者に関する非編集データが対象となることを保証するものではありません。理解しやすい形式の写しと、制限の根拠について請求してください。\n\nEDPBのアクセスに関するガイドライン、第2条、第4条～第6条 ↗ ・GDPR第12条、第15条、第77条 ↗ アーカイブ済み 2026-09-20 ↗\n\n情報主体による情報開示請求GDPR／第15条\nアカウントのセキュリティとアクセス履歴\n\n送信する前に、括弧で囲まれた項目を置き換えてください。\n\nTo: Valve Privacy Team\nSubject: Article 15 GDPR request — account security records\n\nAccount / SteamID: [YOUR ACCOUNT IDENTIFIER]\nRelevant period (UTC): [START] to [END]\nRelated support tickets: [TICKET REFERENCES]\n\nI request a copy of the personal data concerning me that you retain for this period, including:\n\n1. API-key registration, confirmation, use and revocation events, with available timestamps, source IP addresses, registered domains, device or user-agent information and non-secret key identifiers.\n\n2. Recorded account-recovery actions, password/email/phone changes, Steam Guard removals or resets, confirmation events and the account-related evidence relied on to authorize those actions.\n\n3. Personal data in support-access and administrative-action logs concerning my account, including available dates, purposes, actions and the support entity involved, subject to applicable rights of others.\n\n4. Account-related records used to determine any sanction, and available records of my complaints, reviews and responses.\n\nPlease also provide the applicable processing purposes, categories, recipients, retention periods or criteria, and available information about sources where data were not obtained from me.\n\nWhere processing relies on my consent, please provide the retained record of the consent relied upon and the wording presented at that time.\n\nPlease provide an intelligible electronic copy with time zones and field definitions. Please do not include active credentials or secret tokens. If any requested data are not held, please say so. For any withheld data, please identify the scope and legal basis of the restriction and provide the remainder.\n\nPlease acknowledge receipt and respond within the applicable Article 12 period, explaining any necessary extension. I also ask you to preserve relevant existing records while this request is handled.\n\nName: [YOUR NAME]\nDate: [DATE]\nデータセンターのIPによって実現できること\n不一致は、調査すべき証拠である。\n\n本調査で取り上げられたホスティングプロバイダーの事例のように、データセンターのネットワークから発信されたAPIキーの要求は、ログイン記録、確認情報、およびユーザーのタイムラインと照らし合わせた際に、関連性を持つ可能性があります。 IPアドレスだけでは、行為者を特定することはできず、またあらゆる防御策を自動的に無効化することもできません。悪意のある行為者が記録された同意を提供したという証拠があれば、その同意への依存に異議を唱えることが可能となります。その他の法的根拠や責任の問題については、別途分析が必要です。\n\n保存されている禁止措置およびGDPRに関する苦情をご覧ください →\n付録 H — ウェイバック・マシンのアーカイブ分析・公開サポート統計\nサポート対応件数。公表されている対応時間。\n文脈と出典の制限\n\nValve は、毎日サポート統計を以下の場所で公開しています。store.steampowered.com/stats/support. ウェイバック・マシンには、2018年から2026年までのこのページの過去のスナップショットが保存されています。これらの数値から推測される処理件数対人員数の比率は、公表されている応答時間において、チケットごとの人的レビューが行われているという状況とは整合しません。\n\n保存されたスナップショット間で、Valveのアーカイブされたサポート数値を比較します。この方法論では、それらの数値で測定できること、できないことについて説明しています。\n\n処理件数と公表された応答時間の推移（2018年 → 2026年）\n1つのサポートデスクに2つの待ち行列があり、21件のアーカイブされたキャプチャ画像にまたがって確認できます。\n\nValveは、ライブサポートの統計データを以下のURLで公開しています。store.steampowered.com/stats/support. 以下の各点は、インターネットアーカイブが当該ページを保存した当日にそのページに表示されていた下限値「Valve」そのものであり、当方の推定値ではありません。両方の系列は同じ単位で表された同じ測定値であるため、同一の軸上に配置されており、互いに直接比較することができます。\n\n返金のお申し込み — 資金 Valve を保有しているアカウントのセキュリティと復旧 — 紛失したアカウント\n0 h\n2 h\n4 h\n6 h\n8 h\n10 h\nno captures · 38 months\n2019\n2020\n2021\n2022\n2023\n2024\n2025\n2026\n8 h 44 m\naccount recovery\n52 m\nrefunds\n15 m — one capture only\n49～55分2018年2月から2026年8月までの各キャプチャにおけるリファンドの下限値。8年半の間に、その変動幅は6分未満にとどまる一方で、1日あたりのリファンド量は9倍にも変動している。\n2.4 時間 → 8.7 時間2022年12月までのすべてのキャプチャにおいて、アカウント回復の下限値は2.4時間前後となっているが、1件を除く。2026年の3件のキャプチャでは、Valveはそれぞれ10.9時間、5.8時間、8.7時間を公表している。\n×2.8 → ×13Valveが公表した数値によると、返金に比べて返品処理の処理速度がどれほど遅いかがわかります。5年間は横ばいでしたが、その後その差が広がっています。処理が遅くなったのは、Valveではなくユーザーが自己負担を強いられるケースの列です。\n\n出典：Wayback Machineによる21件のアーカイブstore.steampowered.com/stats/support, 2018-02-03 から 2026-08-10 まで；抽出はVALVE_EVIDENCE_PACK/databases/steam_support_stats_history.json. 図と併せて制限値を確認してください。このグラフには、下 範囲の上限は Valve 件です。公表されている上限値は、両方の項目においてこれよりも悪い結果となっています。払い戻しには 1.5 時間から 1.5 日、復旧には 7.0 時間から 3.6 日を要しました。 同じ Valve ページのローカライズ版（チェコ語版 2018-11-03、フランス語版 2020-03-25）に2つのキャプチャがアーカイブされており、表では (cs) および (fr) とマークされています。 それらの数値は、単位の名称を翻訳し、数値自体は公表されたままの形でここに掲載されており、原文の文字列は抽出ファイルにそのまま残されている。 すべてのキャプチャで両方のキューの応答時間が公開されており、いずれの曲線上の点も補間されていません。15分間の復旧時間として2020-10-21という単一の数値は、グラフ上でマークされ、そのまま残されています。これは1つのキャプチャにのみ現れており、他のどのキャプチャもその数値の1桁の範囲内にありません。 2022-12-08と2026-02-01の間にはキャプチャが存在しません。記録上のこの38か月にわたる空白部分は陰影で示されており、その部分には何も描かれていません。 これらの数値は公表された対応時間を示している。これらはチケット内部で何が起きているかを示すものではなく、Valveはこれらを解釈するための従業員数を公表していない。\n\nすべてのキャプチャをテーブルとして開く\n公開されたすべてのアーカイブ済みキャプチャ\nキャプチャ\t1日あたりの払い戻し額\t返金に関する回答\t回復／日\t復旧対応\n2018-02-03\t98,788\t50.12分～1.52時間\t25,662\t2.51時間～1.80日\n2018-05-07\t60,494\t53.83分～1.47日\t24,226\t2.45時間から2.22日\n2018-08-02\t69,084\t50.27分～1.59時間\t28,953\t2.44時間から22.17時間\n2018-11-03 (cs)\t63,410\t49.28分～1.54時間\t33,910\t2.42時間～1.31日\n2019-02-01\t76,305\t50.13分～1.52時間\t35,164\t2.44時間から2.04日\n2019-05-18\t78,951\t51.03分～3.12時間\t27,514\t2.46時間から20.39時間\n2019-09-07\t78,941\t50.65分～1.66時間\t28,812\t2.42時間から13.59時間\n2019-12-13\t69,589\t50.77分～1時間55分\t25,322\t2.45時間から1.13日\n2020-03-25 (fr)\t139,278\t49.45分～1時間53分\t32,302\t2.48時間～3.62日\n2020-06-26\t278,504\t48.98分～2.29時間\t20,343\t2.39時間～6.99時間\n2020-10-21\t107,633\t50.80分～1.54時間\t20,688\t15.33分～8.62時間\n2021-03-20\t158,956\t50.80分～1.64時間\t25,760\t2.34時間～11.62時間\n2021-06-26\t547,907\t51.93分～6.73時間\t29,728\t2.40時間から15.63時間\n2021-10-10\t170,103\t51.88分～3.25時間\t23,989\t2.39時間から13.05時間\n2022-01-31\t354,386\t53.65分～8.09時間\t24,391\t2.42時間～15.29時間\n2022-05-09\t172,555\t51.83分～1.65時間\t23,289\t2.41時間～16.90時間\n2022-09-05\t153,453\t53.67分～4.15時間\t23,594\t2.45時間から1.22日\n2022-12-08\t181,075\t54.83分～6.67時間\t27,111\t2.46時間～18.89時間\n2026-02-01\t317,762\t50.30分～1.52時間\t47,197\t10.91時間から21.30時間\n2026-05-09\t246,776\t50.12分～1.52時間\t35,264\t5.81時間～15.60時間\n2026-08-10\t373,244\t52.05分～2.07時間\t45,319\t8.73時間から16.52時間\n主な所見：\n横に21件のWaybackアーカイブ 2018-02-03から2026-08-10の範囲で、1日あたりの払い戻し申請件数は60,494 （2018年5月）から547,907 （2021年6月） — a9.1倍のスプレッド. 2026年の数値は 373,244 である（2018年2月の集計値と比較して +278%）。\nその同じ9年間、公表された還付処理時間の下限値は、一度も49～55分 バンド：6分未満の総移動量である一方、その背後にある作業負荷は9倍に増加した。\nもし1人が各チケットをたった5秒ずつ読んだとしても、1日あたり373,244枚のチケットを処理する場合（現状）、その処理には22名のエージェントが24時間365日体制で対応しています 単に開閉するだけですが、ピーク時（547,907、2021年6月）には32まで上昇します。\n公表された対応時間がチケット1件あたりの処理時間（約52分/チケット）を反映している場合、そこから推測される同時対応可能なスタッフ数は、およそ13,500 エージェント 現在の規模では～20,000、ピーク時には～20,000。Valveの支援要員数に関する出典のある数値は確認できなかったため、ここでは想定していない。\n以下に示す通り、処理量対人員数の比率は、公表されている応答時間において、チケットごとの人間による審査とは整合しない。これらの数値は、第一段階の審査がほぼ自動化されていることとは整合しているが、人間による審査が行われる割合については公表されていない。\nこれがGDPR準拠においてなぜ重要なのか\n\nGDPR第22条は、要求に応じて人間による審査を受ける権利を付与することなく、重大な法的効果をもたらす、もっぱら自動化された個人に対する意思決定を禁止しています。 もし Steam サポートに関する決定（チケットのクローズ、アカウントへの措置、データ開示請求の拒否など）が完全に自動化されたスクリプトによって行われている場合、ユーザーに「重大な影響」を与えるそのような決定はすべて、第22条に違反する可能性があります。\n\nチケットHT-2YBP-F7JP-D4VB （第18条）は、定型文による照会が行われたものの、引用された法的根拠については言及されることなく、3日後に閉鎖された。誰かがこれを審査したかどうかは、チケットからは判断できない。これは、監督当局が第22条および第15条第1項(h)に基づき、Valveに問うことができる事項である。\n\n出典：store.steampowered.com/stats/support のウェイバックマシンによるスナップショット（2018-02-03、2021-06-26、 2026-08-10） — データは VALVE_EVIDENCE_PACK/databases/steam_support_stats_history.json に抽出済み（スナップショット21件、2018年～2026年）。 注：「約52分」という応答時間は、返金カテゴリの下限値である。同じスナップショットにおいて、アカウントセキュリティへの対応時間は2.4～16.5時間であった。 2021-06-26は過去最高のピーク値（547,907の払い戻しリクエスト数）であり、単調な中間点ではありません。2020～2021年に件数が約6倍に急増した後、一時的に減少しましたが、2026年には373Kまで回復しました。\n付録I — データセットの範囲・再現可能なカウント数\nレコード数を数えてください。範囲を確認してください。\n文脈と出典の制限\n\nレコード数を数え、その主張を検証してください。以下の数値はすべて、公開されているファイルから再算出可能です。\n\n基礎となるデータセットを検証し、集計結果を再現し、ソース行と固有の事象を区別する。\n\nマスターCSVには以下の内容が含まれています40,448 行. そのうち、36,516 Discord-AntiScamのフィッシング情報フィードからのものです。残りの3,932 GitHub、レビュー、検索結果、フォーラムの投稿、その他の情報源を網羅しており、コミュニティで報告されたトピックやセキュリティ報告に関する包括的なインデックスを提供しています。\n\nそのCSVファイル内では、1,690行が「Unpatched Security Exploit」というコレクションラベルに分類されており、これらは過去のユーザーからの報告や脆弱性の開示を表しています。これらの報告を追跡するには、各スレッドの具体的なビルドのタイムラインと公開パッチの履歴を確認する必要があります。\n\n「16,319」レコードの検索可能アーカイブは、独自のマニフェストを持つ、個別にキュレーションされたビルドであり、特定のユーザーの申し立てやインシデント報告をローカル環境で詳細に調査できるように設計されています。\n\n信頼性の高い監査証跡を構築するためには、ユーザーから報告されたすべての記録について、文書化されたビルドのタイムラインおよび過去のパッチログと照合して検証する必要があります。\n\n個別のパートIIのコレクション記録231,829 ユニークな出品ID、これには自動登録カテゴリの「33,509」や、未確認の送金としてフラグが立てられた「198,320」などが含まれます。 入力ファイルのSHA-256は、保存済みの測定値と一致しています。これらの数値は、確定した取引額や検証済みの盗難総額ではなく、出品試行や観測された送金を表しており、正確な経済的影響を測定するためには、プラットフォームの一次記録が必要であることを浮き彫りにしています。測定値とハッシュの一覧 ↗\n\nCSVの活用 ↗ ・検索可能なアーカイブ・マニフェスト ↗ ・ソースレコードを確認する ↗\n\n付録J — 本調査について\nValve は執行記録を公表していない。 私たちは一つ作りました。\n\n独立系。非営利。公開データのみを用いて作成。規制当局に提出済み。\n\n88.97%自動化車両は一切影響を受けない — いかなる禁止措置も講じられない\n67.77%51,732人の有罪判決を受けた詐欺犯が釈放された\n$26.8M+非限定フリートによる店舗での支出の下限額\n3.6%Valveのリンクフィルターによってブロックされたギャンブル関連ドメイン\n8年記録されたセキュリティインシデントのうち\n\nこれは何ですか。 Valve社のSteamプラットフォームに関するフォレンジック調査報告書――その執行実績、カードファーミング経済、法的枠組み、そしてギャンブル事業者がSteam独自のOpenIDリレーを通じて利用する認証インフラについて。 すべての数値は、Valveが公開しているAPIと、本調査に併せて公開されたデータセットという2つの情報源から再現可能です。\n\n対象者。 Valveの管轄権を有する規制当局——オランダのGDPR監督機関、FinCEN、SEC、DSAデジタルサービスコーディネーター、UOKiK、およびSteamに関連する資金の流れを調査しているあらゆる法執行機関。 また、ジャーナリスト、研究者、およびアカウントの永久利用停止処分を受けた、返金請求が拒否された、あるいは保有資産が盗まれたにもかかわらず、「異議申し立ての手段はない」と告げられたすべてのユーザーも対象となる。\n\nただ一つの要求。 Valve は、このデータを完全な忠実度で保持している――禁止理由の添付、完全な ID 空間、リアルタイム処理。この資料に含まれるあらゆるクエリを数秒で実行できるが、その内容を一切公開しないことを選択している。有能な当局にとっての疑問は単純明快だ：どうしてダメなの？\n\n著者たちが主張していないこと。 本作業期間中、いかなるサードパーティプラットフォームにおいても、Steamへのログインは完了していませんでした。提供されたOpenID URLはリクエストパラメータを特定するものであり、ログインが完了したことを示すものではありません。登録可能な別のドメインが存在すること自体は、回避の証拠とはなりません。 登録日は、ホストがOpenIDリクエストに初めて出現し得た時期の下限を示すものであり、継続的な使用を立証するものではない。 著者らは、Valveが何を知っていたか、あるいは何を意図していたかについては主張していない。Valveに関するすべての記述は、日付の明記された公開文書または日付の明記された観察結果に基づいている。出典文書に裏付けられない主張については、削除されている。\n\n私たちについて\n\nPhishDestroy — 独立した調査者。Valve社および本稿で言及されているいかなるプラットフォームとも提携関係はありません。1つのSteamアカウントは、第18項のGDPRに基づく請求を記録する目的のみに使用されました。\n\n法的免責事項\n\n非営利かつ分散型の公益調査です。すべてのデータは「現状有姿」で提供され、いかなる保証も付帯しません。本公開資料は司法上の判断ではありません。\n\nパブリックドメイン\nライセンス\n\nすべての権利は人類に譲渡されます。複製、改変、公開は自由です。出典の明記は不要です。OFAC管轄地域からのアクセス：禁止されています。 利用規約および免責事項の全文 →",
        "headings": [
          {
            "level": 2,
            "id": "briefing-heading",
            "text": "ルール。記録。未解決の謎。"
          },
          {
            "level": 2,
            "id": null,
            "text": "ワシントン州賭博委員会への公開書簡"
          },
          {
            "level": 3,
            "id": "wsgc-public-address-title",
            "text": "10日間が10年に変わった。レコードを再度開いてください。"
          },
          {
            "level": 2,
            "id": null,
            "text": "サイトはアクセスがブロックされていますが、ログイン用のルートはブロックされていません。"
          },
          {
            "level": 3,
            "id": null,
            "text": "図3.1 — 2つのルートを図示したもの。"
          },
          {
            "level": 3,
            "id": null,
            "text": "「全体像の罠」：リンクフィルターはコンプライアンスの「見せかけ」に過ぎず、盾にはならない"
          },
          {
            "level": 3,
            "id": null,
            "text": "メインドメインがブロックされている一方で、認証ホストがブロックされていない場合、ログインルートは開いたままとなり、その状態が何年も続くことになります。"
          },
          {
            "level": 3,
            "id": null,
            "text": "背景：「Steam」とは何か、そしてなぜこれがここで重要なのか"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valveが行ったこと：ドメインブロック"
          },
          {
            "level": 3,
            "id": null,
            "text": "プロキシドメインとは"
          },
          {
            "level": 3,
            "id": null,
            "text": "重要なポイント：すべてのリクエストで認証ホストが Steam に送信される"
          },
          {
            "level": 3,
            "id": null,
            "text": "これが何を証明しているか"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steamの内には、Valveのリストが唯一のリストとして含まれている。"
          },
          {
            "level": 3,
            "id": null,
            "text": "リンクフィルタの保護機能のバイパス"
          },
          {
            "level": 3,
            "id": null,
            "text": "Webブラウザ「Big Picture」がログイン用クッキーを漏洩し、機密情報を開示している（アカウント乗っ取りにつながる恐れあり）"
          },
          {
            "level": 3,
            "id": null,
            "text": "ウイルス対策ソフトをインストールしている未成年者にとって、これはどういう意味を持つのか"
          },
          {
            "level": 3,
            "id": null,
            "text": "ドメインの登録時期。観測日。"
          },
          {
            "level": 2,
            "id": null,
            "text": "エンドポイントが閉じられました。パブリックトレースでキーが失われました。"
          },
          {
            "level": 3,
            "id": null,
            "text": "停電前の時代"
          },
          {
            "level": 3,
            "id": null,
            "text": "変更後"
          },
          {
            "level": 2,
            "id": null,
            "text": "1回のセッション。ユーザーが認識している以上のアクセス権限。"
          },
          {
            "level": 3,
            "id": null,
            "text": "1. 段階認証の不備"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. 最小権限の原則の欠如"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. セッション管理の不具合"
          },
          {
            "level": 3,
            "id": null,
            "text": "4. 認証ホストのドメインレベルでのブロックは技術的に可能であった"
          },
          {
            "level": 3,
            "id": "integration-paradox-title",
            "text": "Valveは毎日、これらのルールに基づいてビルドを行っています。しかし、ここではそれらのルールに基づいてビルドされませんでした。"
          },
          {
            "level": 4,
            "id": null,
            "text": "GitHub のきめ細かいスコープと Valve Steam Web API の比較"
          },
          {
            "level": 2,
            "id": null,
            "text": "インタラクティブなエクスプロイト＆ハイジャック・シミュレーター"
          },
          {
            "level": 2,
            "id": null,
            "text": "シーケンスの背後にあるエンドポイント。"
          },
          {
            "level": 2,
            "id": null,
            "text": "チェックが入ったボックス。誰の操作？"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valveが「貿易代替」をどのようにして最終的に解消したか――そして、なぜ7年もの間、その場しのぎの対策が続いたのか"
          },
          {
            "level": 4,
            "id": null,
            "text": "アバターと名前のクールダウン（2024年2月）"
          },
          {
            "level": 4,
            "id": null,
            "text": "7日間のCS2トレード反転（2025年7月）"
          },
          {
            "level": 4,
            "id": null,
            "text": "APIにおけるモバイルプッシュ通知の義務化（2023年12月）"
          },
          {
            "level": 4,
            "id": null,
            "text": "アカウントの開設期間と名前が入ったバナー（2022年～2024年）"
          },
          {
            "level": 2,
            "id": null,
            "text": "彼らのルールブック。記録されたプラットフォーム。"
          },
          {
            "level": 3,
            "id": "enforcement-focus-title",
            "text": "ルールブックは一つ。しかし、その適用にはばらつきがある。"
          },
          {
            "level": 4,
            "id": null,
            "text": "自動化"
          },
          {
            "level": 4,
            "id": null,
            "text": "商用利用"
          },
          {
            "level": 4,
            "id": null,
            "text": "VPNと位置情報の偽装"
          },
          {
            "level": 4,
            "id": null,
            "text": "リンクの難読化"
          },
          {
            "level": 4,
            "id": null,
            "text": "サポートが案件をクローズした際、その決定を誰が審査するのですか？"
          },
          {
            "level": 2,
            "id": null,
            "text": "自動化用API。自動化を禁止するルール。"
          },
          {
            "level": 3,
            "id": null,
            "text": "「ゲーム開発者」という誤謬"
          },
          {
            "level": 4,
            "id": null,
            "text": "自動化の矛盾"
          },
          {
            "level": 4,
            "id": null,
            "text": "取引フローにおけるサーバーサイドの役割"
          },
          {
            "level": 2,
            "id": null,
            "text": "10日間が求められた。10年分の説明が必要だ。"
          },
          {
            "level": 3,
            "id": "letter-company",
            "text": "バルブ・コーポレーション"
          },
          {
            "level": 3,
            "id": null,
            "text": "10日間。それじゃあ、どうするの？"
          },
          {
            "level": 3,
            "id": null,
            "text": "宣言されたリターンホストに従ってください。"
          },
          {
            "level": 3,
            "id": "washington-record-heading",
            "text": "2つの期限。1つの未解決の執行基準。"
          },
          {
            "level": 4,
            "id": null,
            "text": "Valveはギャンブルサイトに10日間の猶予を与える"
          },
          {
            "level": 4,
            "id": null,
            "text": "ワシントンが圧力をかける Valve"
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve はその容疑を否認した"
          },
          {
            "level": 4,
            "id": null,
            "text": "2026年9月に観測された航路"
          },
          {
            "level": 4,
            "id": null,
            "text": "Valveが回答してから18カ月が経過しても、規制当局は依然としてそれを「意図」と見なしていた。"
          },
          {
            "level": 3,
            "id": null,
            "text": "「10日前の通知」の10年間：指定された23カ所に対する法医学的サバイバル監査"
          },
          {
            "level": 4,
            "id": null,
            "text": "「10日前の警告」から海外複合企業まで：数十億ドル規模の取引"
          },
          {
            "level": 2,
            "id": null,
            "text": "ホスト名はすでにリクエストに含まれています。"
          },
          {
            "level": 3,
            "id": null,
            "text": "記録・報告された先例"
          },
          {
            "level": 3,
            "id": null,
            "text": "登録日からは何がわかるか、何がわからないか"
          },
          {
            "level": 3,
            "id": null,
            "text": "比較監査：APIコンプライアンス基準"
          },
          {
            "level": 2,
            "id": "market-thesis-heading",
            "text": "オフ-0-価格差"
          },
          {
            "level": 2,
            "id": null,
            "text": "価格差は数値で把握できる。"
          },
          {
            "level": 3,
            "id": null,
            "text": "その金額が示すもの"
          },
          {
            "level": 3,
            "id": null,
            "text": "多くの会場では、Steamよりも高い金額が記載されています。"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steamは依然としてオファー数でトップを維持している。"
          },
          {
            "level": 3,
            "id": null,
            "text": "商業エコシステムは、誰の目にも明らかです。"
          },
          {
            "level": 2,
            "id": null,
            "text": "誰が安全装置をリセットできるのですか？"
          },
          {
            "level": 3,
            "id": null,
            "text": "アカウントのセキュリティ機能を無効にした復旧チケット、および報告された$10,000の損失"
          },
          {
            "level": 3,
            "id": null,
            "text": "在庫の枠を超えて。"
          },
          {
            "level": 3,
            "id": "theft-ledger-title",
            "text": "Valveは、33ヶ月の間隔を置いて2度、その扉を開けた。扉は一度も閉まることはなかった。"
          },
          {
            "level": 4,
            "id": null,
            "text": "台帳には、個々の事例からは読み取れないことが記されている。"
          },
          {
            "level": 3,
            "id": null,
            "text": "機密性の確保には、技術的な説明責任が伴わなければならない。"
          },
          {
            "level": 2,
            "id": null,
            "text": "資金の流れを追跡する。取引を個別に区別する。"
          },
          {
            "level": 3,
            "id": null,
            "text": "実際に資金が動く場所。"
          },
          {
            "level": 3,
            "id": null,
            "text": "まずその活動を分類し、次に義務を分類してください。"
          },
          {
            "level": 3,
            "id": null,
            "text": "資金の流れ、情報、および支援を追跡する。"
          },
          {
            "level": 2,
            "id": null,
            "text": "デジタルサービス法：知見を記録に残す"
          },
          {
            "level": 3,
            "id": null,
            "text": "10日間の要求。"
          },
          {
            "level": 3,
            "id": null,
            "text": "DSAの時間枠。"
          },
          {
            "level": 3,
            "id": null,
            "text": "期間には通知の履歴が必要です。"
          },
          {
            "level": 3,
            "id": null,
            "text": "世界全体の年間売上高のうち"
          },
          {
            "level": 2,
            "id": null,
            "text": "未成年者：Steamでのログインは年齢確認にはなりません"
          },
          {
            "level": 3,
            "id": null,
            "text": "演算子とデータを特定してください。"
          },
          {
            "level": 3,
            "id": null,
            "text": "ログインから入金までの流れを記録してください。"
          },
          {
            "level": 2,
            "id": null,
            "text": "リクエスト。レスポンス。欠落している比較。"
          },
          {
            "level": 3,
            "id": null,
            "text": "記録は存在しているが、データ主体はそれを受け取っていない。"
          },
          {
            "level": 2,
            "id": null,
            "text": "プラットフォーム独自のアーキテクチャに反する利用規約"
          },
          {
            "level": 3,
            "id": null,
            "text": "市場の天井価格と商業利用の禁止"
          },
          {
            "level": 3,
            "id": null,
            "text": "APIキーの脆弱性は、ユーザーの不注意というよりも、プラットフォームの設計上の問題である"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve は、ログインのたびに認証用ホスト名を受け取ります"
          },
          {
            "level": 3,
            "id": null,
            "text": "過去寄せられた苦情に見られる傾向"
          },
          {
            "level": 3,
            "id": null,
            "text": "この記録を審査する裁判所は、SSAを単独で解釈することはないだろう。"
          },
          {
            "level": 2,
            "id": null,
            "text": "調査結果。私たちが求めている記録。"
          },
          {
            "level": 2,
            "id": null,
            "text": "証拠概要書 — 情報源1から提供された資料"
          },
          {
            "level": 2,
            "id": null,
            "text": "提出されたPDFにおける黒塗り処理は表面的なものであり、黒塗りされたテキストも引き続き抽出可能です"
          },
          {
            "level": 2,
            "id": null,
            "text": "サポートおよび法的文書に関する添付資料"
          },
          {
            "level": 2,
            "id": null,
            "text": "選定された一次資料"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-01",
            "text": "2016年に要求されたハードウェアキー"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-02",
            "text": "効果的なオプトアウト機能のないクラッシュレポート"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-03",
            "text": "Valveに認証チケットの悪用が報告された"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-01",
            "text": "44件の係争中のマーケット購入"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-02",
            "text": "永久利用停止および異議申し立ての受付停止"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-03",
            "text": "リカバリ・リセットと、報告された「-0」の損失"
          },
          {
            "level": 2,
            "id": null,
            "text": "ArchiSteamFarm および自動化条項"
          },
          {
            "level": 2,
            "id": null,
            "text": "Rules ledger: clauses against recorded platforms"
          },
          {
            "level": 3,
            "id": "ledger-title",
            "text": "商用利用およびアカウントへの課金"
          },
          {
            "level": 3,
            "id": "lw-register-title",
            "text": "プラットフォーム登録 175"
          },
          {
            "level": 4,
            "id": null,
            "text": "立証責任"
          },
          {
            "level": 4,
            "id": null,
            "text": "タグ付きレコードとは何か、そして何ではないか"
          },
          {
            "level": 2,
            "id": null,
            "text": "DSAR対応マニュアル：証拠の提出を要請する"
          },
          {
            "level": 3,
            "id": null,
            "text": "タイムラインを保存してください。"
          },
          {
            "level": 3,
            "id": null,
            "text": "保存されているデータの開示を請求してください。"
          },
          {
            "level": 3,
            "id": null,
            "text": "配送記録は保管しておいてください。"
          },
          {
            "level": 3,
            "id": null,
            "text": "回答を比較してください。"
          },
          {
            "level": 3,
            "id": null,
            "text": "アカウントのセキュリティとアクセス履歴"
          },
          {
            "level": 3,
            "id": null,
            "text": "不一致は、調査すべき証拠である。"
          },
          {
            "level": 2,
            "id": null,
            "text": "サポート対応件数。公表されている対応時間。"
          },
          {
            "level": 3,
            "id": null,
            "text": "1つのサポートデスクに2つの待ち行列があり、21件のアーカイブされたキャプチャ画像にまたがって確認できます。"
          },
          {
            "level": 2,
            "id": null,
            "text": "レコード数を数えてください。範囲を確認してください。"
          },
          {
            "level": 2,
            "id": null,
            "text": "Valve は執行記録を公表していない。\n私たちは一つ作りました。"
          }
        ],
        "links": [
          "https://dotesports.com/counter-strike/news/csgo-lounge-billion-bets-3896",
          "https://store.steampowered.com/agreement/?l=english",
          "http://web.archive.org/web/20260921022032/https://store.steampowered.com/agreement/?l=english",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-all-results.json",
          "https://blog.counter-strike.net/expresstrade/",
          "http://web.archive.org/web/20260307161538/https://blog.counter-strike.net/expresstrade/",
          "https://wsgc.wa.gov/news/2016/washington-state-gambling-commission-orders-valve-stop-skins-gambling",
          "http://web.archive.org/web/20260520012601/https://wsgc.wa.gov/news/2016/washington-state-gambling-commission-orders-valve-stop-skins-gambling",
          "https://fr.scribd.com/document/328063293/Valve-s-Oct-18th-response-to-Washington-State-Gambling-Commission-s-cease-and-desist",
          "https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921021947/https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921022628/https://steamcommunity.com/linkfilter/?url=https:%2F%2Frollbit.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rbsnin.com.20260921T021120Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rollbit.com.json",
          "http://web.archive.org/web/20260921022740/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fskin.club",
          "http://web.archive.org/web/20260921022842/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fsc-auth.net",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skin.club.json",
          "http://web.archive.org/web/20260921022603/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fhowl.gg",
          "http://web.archive.org/web/20260921022636/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fhowl.uno",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/howl.gg.json",
          "http://web.archive.org/web/20260921022840/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fduelbits.com",
          "http://web.archive.org/web/20260921022901/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fswitchflips.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/duelbits.com.json",
          "http://web.archive.org/web/20260921022758/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgofast.com",
          "http://web.archive.org/web/20260921022847/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fauthtofast.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgofast.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/farmskins.com.20260921T025840Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/steam.kobal.cc.20260921T025844Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/farmskins.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cobaltlab.tech.20260921T041604Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cobaltauth.com.20260921T041608Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/cobaltlab.tech.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgo.net.20260921T041619Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cn2.easylot.net.20260921T041623Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgo.net.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/ggdrop.com.20260921T041637Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/ggauth.com.20260921T041641Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/ggdrop.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rustchance.com.20260921T041703Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/hgfuihd.com.20260921T041706Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rustchance.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skin.fans.20260921T041710Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.skinfans.com.20260921T041713Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skin.fans.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinport.com.20260921T041724Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinport.app.20260921T041728Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skinport.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skins.cash.20260921T041731Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinscash.live.20260921T041735Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skins.cash.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2hunt.com.20260921T041739Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rstspcl.com.20260921T041742Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tf2hunt.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgogem.com.20260922T192355Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/api.csgem.com.20260922T192358Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-2026-09-22.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/gamdom.com.20260922T192326Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/login.gambldom.com.20260922T192330Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/12cs.fail.20260922T192347Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/fail.games.20260922T192351Z.html",
          "http://web.archive.org/web/20260921022953/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgoempire.com",
          "http://web.archive.org/web/20260921022947/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgoempirelogin4.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgoempire.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cs.money.20260921T021131Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.dota.trade.20260921T021134Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/cs.money.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csfloat.com.20260921T041612Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgofloat.com.20260921T041615Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csfloat.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/g4skins.com.20260921T041630Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.g4s.to.20260921T041634Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/g4skins.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/juice.gg.20260921T041644Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/letmeinjuice.com.20260921T041648Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/juice.gg.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/market.csgo.com.20260921T041652Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2.net.20260921T041655Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/market.csgo.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rust.tm.20260921T041659Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rust.tm.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgolounge.com.20260922T192333Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2.net.20260922T192340Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2lounge.com.20260922T192337Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinbaron.de.20260921T041717Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinbaron.com.20260921T041721Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skinbaron.de.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2royal.com.20260921T041746Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2auth.com.20260921T041750Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tf2royal.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tradeit.gg.20260921T041753Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/connect-tradeit.com.20260921T041757Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tradeit.gg.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/upgrader.pro.20260921T041801Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/upgauth.space.20260921T041804Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/upgrader.pro.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-recheck-2026-09-21.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/domain-registration.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wayback-snapshots.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-2026-09-22c.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/master_registry.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/longitudinal-steam-phishing-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-steam-phishing-100.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-coverage-2026-09-22.json",
          "https://blog.csfloat.com/how-floatdb-tracks-items/",
          "http://web.archive.org/web/20260921022415/https://blog.csfloat.com/how-floatdb-tracks-items/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/platform-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/platforms-removed.json",
          "https://hackerone.com/reports/291750",
          "http://web.archive.org/web/20251116185046/https://hackerone.com/reports/291750",
          "https://hackerone.com/reports/1079561",
          "http://web.archive.org/web/20260924181830/https://hackerone.com/reports/1079561",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/hackerone-reports.json",
          "https://phishdestroy.io/steam_dossier/ja/steam_enforcement_evidence.html#support-records",
          "https://www.darknavy.org/blog/exploiting_steam_usual_and_unusual_ways_in_the_cef_framework/",
          "https://steamcommunity.com/groups/SteamClientBeta/discussions/0/3365901765276206401/",
          "http://web.archive.org/web/20250804051514/https://steamcommunity.com/groups/SteamClientBeta/discussions/0/3365901765276206401/",
          "https://www.chromium.org/developers/design-documents/safebrowsing/",
          "http://web.archive.org/web/20260821101616/https://www.chromium.org/developers/design-documents/safebrowsing/",
          "https://www.chromium.org/developers/how-tos/api-keys/",
          "http://web.archive.org/web/20260830122831/https://www.chromium.org/developers/how-tos/api-keys/",
          "https://github.com/Homebrew/homebrew-cask/issues/193814",
          "https://testsafebrowsing.appspot.com/",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/domain-registration.json",
          "https://phishdestroy.io/steam_dossier/ja/AUTH_AUDIT.md",
          "https://datatracker.ietf.org/doc/rfc6749/",
          "https://docs.cloud.google.com/docs/authentication/api-keys",
          "https://listings.pcisecuritystandards.org/pdfs/PCI_DSS_Resource_Guide_(003).pdf",
          "https://developer.apple.com/news/?id=02202019a",
          "http://web.archive.org/web/20250506070026/https://developer.apple.com/news/?id=02202019a",
          "https://dev.twitch.tv/docs/authentication/validate-tokens/",
          "https://discuss.dev.twitch.com/t/legacy-twitch-api-v5-i-e-kraken-shutdown-reminder-february-28-2022/36589",
          "http://web.archive.org/web/20250127085635/https://discuss.dev.twitch.com/t/legacy-twitch-api-v5-i-e-kraken-shutdown-reminder-february-28-2022/36589",
          "https://store.steampowered.com/news/posts/?enddate=1788390000",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/4123547285514022851",
          "https://skinvault.gg/blog/cs2-trade-protection-explained/",
          "https://csmarketcap.com/blog/market-insights/from-boom-to-bust-cs2s-trade-protection-impact",
          "https://skin.land/blog/steam-changes-cs2-trade-ban-logic-timing/",
          "https://help.steampowered.com/faqs/view/3041-A87A-E5F6-B6AC",
          "https://steamcommunity.com/ogg/593110/announcements/detail/533224478739530146",
          "https://steamcommunity.com/games/CSGO/announcements/detail/4447966961421256740",
          "https://steamcommunity.com/sharedfiles/filedetails/?id=2926756889",
          "https://steamcommunity.com/dev/apikey",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3734103130194459461",
          "https://steamcommunity.com/discussions/forum/1/3807266184852932971/",
          "https://help.steampowered.com/faqs/view/225C-C51E-B8F0-55B2",
          "https://store.steampowered.com/news/group/4/view/3314112260640237775",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/issues/325",
          "https://blog.dota2.com/2020/05/trading-cooldown/",
          "https://blog.counter-strike.net/index.php/2018/03/20308/",
          "http://web.archive.org/web/20250226114333/https://blog.counter-strike.net/index.php/2018/03/20308/",
          "https://phishdestroy.io/steam_dossier/ja/steam_evidence_archive.html",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/493839547938902179",
          "https://store.steampowered.com/online_conduct",
          "http://web.archive.org/web/20260921022120/https://store.steampowered.com/online_conduct",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260918014700/https://store.steampowered.com/subscriber_agreement/",
          "https://steamcommunity.com/dev/apiterms",
          "http://web.archive.org/web/20260921022210/https://steamcommunity.com/dev/apiterms",
          "https://help.steampowered.com/en/faqs/view/628C-E332-BD8C-4D36",
          "https://phishdestroy.io/steam_dossier/ja/social_graph.html",
          "https://phishdestroy.io/steam_dossier/ja/security_timeline.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wsgc-skins-gambling-briefing-2018.pdf",
          "https://wsgc.wa.gov/sites/default/files/2023-10/Skins%20Gambling.pdf",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wsgc-briefing-manifest.json",
          "https://x.com/csgobig",
          "https://www.facebook.com/csgobigofficial/",
          "https://500.casino/",
          "https://csgolounge.com/",
          "https://csgocasino.gg/",
          "https://x.com/CSGOatsecom",
          "https://x.com/CSGOSweep/status/937420902538543106",
          "https://x.com/Wild",
          "https://x.com/csgopot",
          "https://x.com/csgodiamondscom",
          "https://www.ftc.gov/legal-library/browse/cases-proceedings/162-3184-csgo-lotto-matter",
          "https://x.com/CSGODouble",
          "https://x.com/csgo_massive",
          "https://www.facebook.com/csgostrongfree/",
          "https://www.facebook.com/CSNCOM/",
          "https://www.gamblingcommission.gov.uk/report/young-people-and-gambling",
          "https://www.aph.gov.au/Parliamentary_Business/Committees/Senate/Environment_and_Communications/Gamingmicro-transactions",
          "https://phishdestroy.io/steam_dossier/ja/elite_skins.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/csfloat-catalogue.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/skinport-floor-over-cap.json",
          "https://pricempire.com/cs2-marketplaces",
          "http://web.archive.org/web/20260921022459/https://pricempire.com/cs2-marketplaces",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/priceempire-marketplaces.json",
          "https://www.steamanalyst.com/marketplace",
          "http://web.archive.org/web/20260719014552/https://www.steamanalyst.com/marketplace",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-atlas.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json",
          "https://phishdestroy.io/steam_dossier/ja/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/ja/steam_enforcement_evidence.html#case-support-recovery",
          "https://top10.owasp.org/2025/A01_2025-Broken_Access_Control/",
          "http://web.archive.org/web/20260920212535/https://top10.owasp.org/2025/A01_2025-Broken_Access_Control/",
          "https://store.steampowered.com/privacy_agreement/",
          "http://web.archive.org/web/20260921021648/https://store.steampowered.com/privacy_agreement/",
          "https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "http://web.archive.org/web/20250818113925/https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "https://www.dexerto.com/counter-strike-2/valve-saves-hacked-cs2-player-threatened-with-ransom-over-300000-of-rare-stickers-3283135/",
          "https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "http://web.archive.org/web/20220702042821/https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "https://www.kaspersky.com/blog/cs-go-two-million-usd-inventory-hack/44697/",
          "https://esportfire.com/article/the-2-million-usd-csgo-hack-22062022",
          "http://web.archive.org/web/20260515110250/https://esportfire.com/article/the-2-million-usd-csgo-hack-22062022",
          "https://esportsbetting.com/valve-deletes-130000-stolen-dragon-lore/",
          "https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "http://web.archive.org/web/20251115173120/https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "https://vkplay.ru/media/news/bloger-rasskazal-kak-podderzhka-steam-vorovala-akkaunty-igrokov/",
          "https://lis-skins.com/ru/blog/krupneisaia-mosenniceskaia-sxema-v-istorii-steam/",
          "https://escorenews.com/ru/csgo/news/44056-sotrudniki-podderjki-steam-zanimalis-krajey-skinov-s-akkauntov-za-god-oni-zarabotali-svyshe-300-tysyach-dollarov",
          "https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "http://web.archive.org/web/20250805141942/https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/outsourcing-archive-records.json",
          "https://community.skin.club/en/news/collector-has-steam-inventory-returned-after-bold-hack",
          "https://esportfire.com/article/300k-scam-full-katowice-2014-holo-collection-hacked",
          "http://web.archive.org/web/20251217072445/https://esportfire.com/article/300k-scam-full-katowice-2014-holo-collection-hacked",
          "https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng",
          "http://web.archive.org/web/20260920024236/https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng",
          "https://ag.ny.gov/press-release/2026/attorney-general-james-sues-game-developer-promoting-illegal-gambling-through",
          "http://web.archive.org/web/20260901015430/https://ag.ny.gov/press-release/2026/attorney-general-james-sues-game-developer-promoting-illegal-gambling-through",
          "https://www.fincen.gov/sites/default/files/2019-05/FinCEN%20CVC%20Guidance%20FINAL.pdf",
          "http://web.archive.org/web/20250711185007/https://www.fincen.gov/sites/default/files/2019-05/FinCEN%20CVC%20Guidance%20FINAL.pdf",
          "https://eur-lex.europa.eu/legal-content/EN/LSU/?uri=CELEX:32018L1673",
          "https://eur-lex.europa.eu/eli/dir/2024/1640/oj/eng",
          "http://web.archive.org/web/20260830153004/https://eur-lex.europa.eu/eli/dir/2024/1640/oj/eng",
          "https://eur-lex.europa.eu/eli/reg/2022/2065/oj/eng",
          "http://web.archive.org/web/20260920080125/https://eur-lex.europa.eu/eli/reg/2022/2065/oj/eng",
          "https://phishdestroy.io/steam_dossier/ja/legal_analysis.html",
          "https://partner.steamgames.com/doc/features/auth#website",
          "http://web.archive.org/web/20260921022335/https://partner.steamgames.com/doc/features/auth",
          "https://www.ftc.gov/legal-library/browse/rules/childrens-online-privacy-protection-rule-coppa",
          "http://web.archive.org/web/20260921070051/https://www.ftc.gov/legal-library/browse/rules/childrens-online-privacy-protection-rule-coppa",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/gdpr-ticket-1.png",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/screenshot-manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/gdpr-ticket-2.png",
          "https://datenschutz.hamburg.de/beschwerde",
          "https://edpb.europa.eu/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/regulatory-review/disclosure-audit.json",
          "https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "http://web.archive.org/web/20260821155801/https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "https://phishdestroy.io/steam_dossier/ja/index#exhibit-gallery-section",
          "https://github.com/ValveSoftware/steam-for-linux/issues/4521",
          "https://phishdestroy.io/steam_dossier/ja/steam_evidence_archive.html?source=GitHub&record=484",
          "https://github.com/ValveSoftware/steam-for-linux/issues/6459",
          "http://web.archive.org/web/20260419051343/https://github.com/ValveSoftware/steam-for-linux/issues/6459",
          "https://phishdestroy.io/steam_dossier/ja/steam_evidence_archive.html?source=GitHub&record=467",
          "https://github.com/ValveSoftware/Source-1-Games/issues/3857",
          "https://phishdestroy.io/steam_dossier/ja/steam_evidence_archive.html?source=GitHub&record=768",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "http://web.archive.org/web/20250320082450/https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://phishdestroy.io/steam_dossier/ja/steam_evidence_archive.html?source=Reddit&record=4533",
          "https://www.reddit.com/r/ohnePixel/comments/1hahqx2/permanently_banned_steam_account_without_a_clear/",
          "https://phishdestroy.io/steam_dossier/ja/steam_evidence_archive.html?source=Reddit&record=4766",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://phishdestroy.io/steam_dossier/ja/steam_evidence_archive.html?source=Reddit&record=4592",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/selected-evidence-records.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive_manifest.json",
          "https://phishdestroy.io/steam_dossier/ja/card_economy.html",
          "https://github.com/JustArchiNET/ArchiSteamFarm/wiki/FAQ",
          "https://phishdestroy.io/steam_dossier/ja/card_economy.html#scale",
          "https://phishdestroy.io/steam_dossier/ja/card_economy.html#licence",
          "https://phishdestroy.io/steam_dossier/ja/enforcement_audit.html",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "http://web.archive.org/web/20260924181709/https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://rdap.verisign.com/com/v1/domain/csgoempire.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoempire.com",
          "https://rdap.verisign.com/com/v1/domain/csgoempirelogin4.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/csgoempire.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustreaper.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustreaper.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/rustreaper.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustly.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustly.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/rustly.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgofast.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgofast.com",
          "https://rdap.verisign.com/com/v1/domain/authtofast.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/csgofast.com.json",
          "https://rdap.verisign.com/com/v1/domain/duelbits.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fduelbits.com",
          "https://rdap.verisign.com/com/v1/domain/switchflips.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/duelbits.com.json",
          "https://rdap.verisign.com/com/v1/domain/farmskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffarmskins.com",
          "https://tld-rdap.verisign.com/cc/v1/domain/kobal.cc",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/farmskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoluck.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoluck.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/csgoluck.com.json",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/domain-registry/insane.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Finsane.gg",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/insane.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs2skin.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs2skin.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/cs2skin.com.json",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/domain-registry/juice.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fjuice.gg",
          "https://rdap.verisign.com/com/v1/domain/letmeinjuice.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/juice.gg.json",
          "https://rdap.verisign.com/com/v1/domain/ggdrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fggdrop.com",
          "https://rdap.verisign.com/com/v1/domain/ggauth.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/ggdrop.com.json",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/domain-registry/howl.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhowl.gg",
          "https://rdap.radix.host/rdap/domain/howl.uno",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/howl.gg.json",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/domain-registry/chicken.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fchicken.gg",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/chicken.gg.json",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/domain-registry/csgocasino.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgocasino.gg",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/csgocasino.gg.json",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/domain-registry/hunt.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhunt.gg",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/hunt.gg.json",
          "https://rdap.verisign.com/com/v1/domain/csbattle.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsbattle.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/csbattle.com.json",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/domain-registry/skinrave.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinrave.gg",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/skinrave.gg.json",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/domain-registry/csdouble.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsdouble.gg",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/csdouble.gg.json",
          "https://rdap.verisign.com/com/v1/domain/rustchance.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustchance.com",
          "https://rdap.verisign.com/com/v1/domain/hgfuihd.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/rustchance.com.json",
          "https://rdap.radix.host/rdap/domain/cobaltlab.tech",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcobaltlab.tech",
          "https://rdap.verisign.com/com/v1/domain/cobaltauth.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/cobaltlab.tech.json",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/domain-registry/raided.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fraided.gg",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/raided.gg.json",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/domain-registry/rustneo.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustneo.gg",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/rustneo.gg.json",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/domain-registry/splits.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsplits.gg",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/splits.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/upgrader.pro",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fupgrader.pro",
          "https://rdap.radix.host/rdap/domain/upgauth.space",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/upgrader.pro.json",
          "https://rdap.centralnic.com/fans/domain/skin.fans",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.fans",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/skin.fans.json",
          "https://rdap.nic.one/domain/hotpizza.one",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhotpizza.one",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/hotpizza.one.json",
          "https://rdap.verisign.com/com/v1/domain/g4skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg4skins.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/g4skins.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2royal.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2royal.com",
          "https://rdap.verisign.com/com/v1/domain/tf2auth.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/tf2royal.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2hunt.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2hunt.com",
          "https://rdap.verisign.com/com/v1/domain/rstspcl.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/tf2hunt.com.json",
          "https://rdap.identitydigital.services/rdap/domain/tf2.bet",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2.bet",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/tf2.bet.json",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/domain-registry/openstars.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fopenstars.gg",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/openstars.gg.json",
          "https://rdap.verisign.com/com/v1/domain/skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/skins.com.json",
          "https://rdap.identitydigital.services/rdap/domain/white.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwhite.market",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/white.market.json",
          "https://rdap.identitydigital.services/rdap/domain/moon.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmoon.market",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/moon.market.json",
          "https://rdap.verisign.com/com/v1/domain/csfloat.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsfloat.com",
          "https://rdap.verisign.com/com/v1/domain/csgofloat.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/csfloat.com.json",
          "https://rdap.identitydigital.services/rdap/domain/skin.land",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.land",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/skin.land.json",
          "https://rdap.verisign.com/com/v1/domain/haloskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhaloskins.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/haloskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/163.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuff.163.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/buff.163.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmarket.csgo.com",
          "https://rdap.verisign.com/net/v1/domain/dota2.net",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/market.csgo.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinport.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinport.com",
          "https://pubapi.registry.google/rdap/domain/skinport.app",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/skinport.com.json",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/domain-registry/skinflow.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinflow.gg",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/skinflow.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/skin.place",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.place",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/skin.place.json",
          "https://rdap.verisign.com/com/v1/domain/skinsmonkey.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinsmonkey.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/skinsmonkey.com.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbaron.de",
          "https://rdap.verisign.com/com/v1/domain/skinbaron.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/skinbaron.de.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frust.tm",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/rust.tm.json",
          "https://rdap.verisign.com/com/v1/domain/pirateswap.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fpirateswap.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/pirateswap.com.json",
          "https://rdap.radix.host/rdap/domain/mannco.store",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmannco.store",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/mannco.store.json",
          "https://rdap.verisign.com/com/v1/domain/skinswap.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinswap.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/skinswap.com.json",
          "https://rdap.verisign.com/com/v1/domain/exeskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fexeskins.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/exeskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/balticskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbalticskins.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/balticskins.com.json",
          "https://rdap.nic.trade/domain/cs.trade",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.trade",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/cs.trade.json",
          "https://rdap.verisign.com/com/v1/domain/rapidskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frapidskins.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/rapidskins.com.json",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/domain-registry/tradeit.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftradeit.gg",
          "https://rdap.verisign.com/com/v1/domain/connect-tradeit.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/tradeit.gg.json",
          "https://rdap.verisign.com/com/v1/domain/49skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F49skins.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/49skins.com.json",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/domain-registry/skinvault.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinvault.gg",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/skinvault.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/aim.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Faim.market",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/aim.market.json",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/domain-registry/skinout.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinout.gg",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/skinout.gg.json",
          "https://rdap.verisign.com/com/v1/domain/ntskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fntskins.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/ntskins.com.json",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/domain-registry/gamerpay.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamerpay.gg",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/gamerpay.gg.json",
          "https://rdap.nic.tf/domain/scrap.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fscrap.tf",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/scrap.tf.json",
          "https://rdap.nic.tf/domain/marketplace.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmarketplace.tf",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/marketplace.tf.json",
          "https://rdap.identitydigital.services/rdap/domain/skins.cash",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.cash",
          "https://rdap.identitydigital.services/rdap/domain/skinscash.live",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/skins.cash.json",
          "https://rdap.verisign.com/net/v1/domain/csgo.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo.net",
          "https://rdap.verisign.com/net/v1/domain/easylot.net",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/csgo.net.json",
          "https://rdap.verisign.com/net/v1/domain/cybershoke.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcybershoke.net",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/cybershoke.net.json",
          "https://rdap.verisign.com/net/v1/domain/fastcup.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffastcup.net",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/fastcup.net.json",
          "https://rdap.verisign.com/com/v1/domain/leetify.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fleetify.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/leetify.com.json",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/domain-registry/scope.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fscope.gg",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/scope.gg.json",
          "https://rdap.verisign.com/com/v1/domain/tradeupspy.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftradeupspy.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/tradeupspy.com.json",
          "https://rdap.identitydigital.services/rdap/domain/cs.deals",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.deals",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/cs.deals.json",
          "https://rdap.verisign.com/com/v1/domain/pricempire.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fpricempire.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/pricempire.com.json",
          "https://rdap.identitydigital.services/rdap/domain/lzt.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flzt.market",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/lzt.market.json",
          "https://rdap.verisign.com/com/v1/domain/z2u.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fz2u.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/z2u.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoroll.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoroll.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/csgoroll.com.json",
          "https://rdap.verisign.com/com/v1/domain/rollbit.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frollbit.com",
          "https://rdap.verisign.com/com/v1/domain/rbsnin.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/rollbit.com.json",
          "https://rdap.identitydigital.services/rdap/domain/500.casino",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F500.casino",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/500.casino.json",
          "https://rdap.verisign.com/com/v1/domain/csgobig.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgobig.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/csgobig.com.json",
          "https://rdap.verisign.com/com/v1/domain/casedrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcasedrop.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/casedrop.com.json",
          "https://rdap.verisign.com/com/v1/domain/banditcamp.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbanditcamp.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/banditcamp.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinbox.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbox.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/skinbox.com.json",
          "https://rdap.verisign.com/com/v1/domain/tastydrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftastydrop.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/tastydrop.com.json",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/domain-registry/csgopolygon.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgopolygon.gg",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/csgopolygon.gg.json",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/domain-registry/magicdrop.ru.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmagicdrop.ru",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/magicdrop.ru.json",
          "https://rdap.verisign.com/com/v1/domain/csdice.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsdice.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/csdice.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinodds.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinodds.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/skinodds.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgowin.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgowin.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/csgowin.com.json",
          "https://rdap.verisign.com/net/v1/domain/csgorun.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgorun.net",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/csgorun.net.json",
          "https://rdap.verisign.com/com/v1/domain/openskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fopenskins.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/openskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustbet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustbet.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/rustbet.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgomagic.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgomagic.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/csgomagic.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgobounty.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgobounty.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/csgobounty.com.json",
          "https://rdap.verisign.com/com/v1/domain/ezskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fezskins.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/ezskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustcases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustcases.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/rustcases.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoreaper.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoreaper.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/csgoreaper.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgocases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgocases.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/csgocases.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo-skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo-skins.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/csgo-skins.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgonet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgonet.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/csgonet.com.json",
          "https://rdap.verisign.com/com/v1/domain/wtfskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwtfskins.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/wtfskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/flamecases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fflamecases.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/flamecases.com.json",
          "https://rdap.verisign.com/com/v1/domain/gamedom.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamedom.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/gamedom.com.json",
          "https://rdap.nic.club/domain/skin.club",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.club",
          "https://rdap.verisign.com/net/v1/domain/sc-auth.net",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/skin.club.json",
          "https://rdap.verisign.com/com/v1/domain/daddyskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdaddyskins.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/daddyskins.com.json",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/domain-registry/rustix.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustix.gg",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/rustix.gg.json",
          "https://rdap.nic.club/domain/skins.club",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.club",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/skins.club.json",
          "https://rdap.publicinterestregistry.org/rdap/domain/csgohouse.org",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgohouse.org",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/csgohouse.org.json",
          "https://rdap.verisign.com/net/v1/domain/skinrave.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinrave.net",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/skinrave.net.json",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/domain-registry/bloodycase.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbloodycase.gg",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/bloodycase.gg.json",
          "https://rdap.verisign.com/com/v1/domain/csgoclicker.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoclicker.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/csgoclicker.com.json",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/domain-registry/rustbet.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustbet.gg",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/rustbet.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs-drop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs-drop.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/cs-drop.com.json",
          "https://rdap.verisign.com/net/v1/domain/hellstore.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhellstore.net",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/hellstore.net.json",
          "https://rdap.verisign.com/com/v1/domain/rustloot.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustloot.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/rustloot.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo-case.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo-case.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/csgo-case.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgogem.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgogem.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/csgogem.com.json",
          "https://rdap.verisign.com/com/v1/domain/rainbet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frainbet.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/rainbet.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustclash.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustclash.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/rustclash.com.json",
          "https://rdap.identitydigital.services/rdap/domain/12cs.fail",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F12cs.fail",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/12cs.fail.json",
          "https://rdap.verisign.com/com/v1/domain/tf2easy.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwww.tf2easy.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/tf2easy.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2blaze.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2blaze.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/tf2blaze.com.json",
          "https://rdap.verisign.com/com/v1/domain/shuffle.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fshuffle.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/shuffle.com.json",
          "https://rdap.identitydigital.services/rdap/domain/buff.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuff.market",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/buff.market.json",
          "https://rdap.identitydigital.services/rdap/domain/avan.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Favan.market",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/avan.market.json",
          "https://rdap.identitydigital.services/rdap/domain/cs.money",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.money",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/cs.money.json",
          "https://rdap.verisign.com/com/v1/domain/uuskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fuuskins.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/uuskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/youpin898.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fyoupin898.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/youpin898.com.json",
          "https://rdap.verisign.com/com/v1/domain/c5game.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fc5game.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/c5game.com.json",
          "https://rdap.verisign.com/com/v1/domain/waxpeer.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwaxpeer.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/waxpeer.com.json",
          "https://rdap.verisign.com/com/v1/domain/dmarket.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdmarket.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/dmarket.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamcommunity.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamcommunity.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/steamcommunity.com.json",
          "https://rdap.verisign.com/com/v1/domain/lootfarm.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flootfarm.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/lootfarm.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustskins.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/rustskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/krakatoa.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fkrakatoa.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/krakatoa.com.json",
          "https://rdap.verisign.com/com/v1/domain/shadowpay.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fshadowpay.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/shadowpay.com.json",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/domain-registry/igxe.cn.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Figxe.cn",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/igxe.cn.json",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/domain-registry/swap.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fswap.gg",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/swap.gg.json",
          "https://rdap.verisign.com/com/v1/domain/bitskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbitskins.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/bitskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2mart.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2mart.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/tf2mart.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinbid.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbid.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/skinbid.com.json",
          "https://rdap.verisign.com/com/v1/domain/lootbear.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flootbear.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/lootbear.com.json",
          "https://rdap.nic.tf/domain/backpack.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbackpack.tf",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/backpack.tf.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fstntrading.eu",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/stntrading.eu.json",
          "https://rdap.verisign.com/com/v1/domain/skinwallet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinwallet.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/skinwallet.com.json",
          "https://rdap.verisign.com/com/v1/domain/dota2market.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdota2market.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/dota2market.com.json",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/domain-registry/xplay.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fxplay.gg",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/xplay.gg.json",
          "https://rdap.verisign.com/com/v1/domain/esportal.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fesportal.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/esportal.com.json",
          "https://rdap.registro.br/domain/gamersclub.com.br",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamersclub.com.br",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/gamersclub.com.br.json",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/domain-registry/epidemic.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fepidemic.gg",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/epidemic.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs2stash.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs2stash.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/cs2stash.com.json",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/domain-registry/csgoskins.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoskins.gg",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/csgoskins.gg.json",
          "https://rdap.verisign.com/com/v1/domain/steamanalyst.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamanalyst.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/steamanalyst.com.json",
          "https://rdap.verisign.com/net/v1/domain/steamcardexchange.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamcardexchange.net",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/steamcardexchange.net.json",
          "https://rdap.verisign.com/com/v1/domain/dotabuff.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdotabuff.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/dotabuff.com.json",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/domain-registry/tracker.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftracker.gg",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/tracker.gg.json",
          "https://rdap.verisign.com/com/v1/domain/funpay.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffunpay.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/funpay.com.json",
          "https://rdap.verisign.com/com/v1/domain/playerauctions.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fplayerauctions.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/playerauctions.com.json",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/domain-registry/eldorado.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Feldorado.gg",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/eldorado.gg.json",
          "https://rdap.verisign.com/com/v1/domain/g2a.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg2a.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/g2a.com.json",
          "https://rdap.verisign.com/net/v1/domain/kinguin.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fkinguin.net",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/kinguin.net.json",
          "https://rdap.verisign.com/com/v1/domain/g2g.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg2g.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/g2g.com.json",
          "https://rdap.verisign.com/com/v1/domain/playerup.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fplayerup.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/playerup.com.json",
          "https://rdap.verisign.com/net/v1/domain/smurfhub.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfhub.net",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/smurfhub.net.json",
          "https://rdap.verisign.com/com/v1/domain/smurfaccounts.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfaccounts.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/smurfaccounts.com.json",
          "https://rdap.verisign.com/com/v1/domain/buycsgorank.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuycsgorank.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/buycsgorank.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgosmurfkings.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgosmurfkings.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/csgosmurfkings.com.json",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/domain-registry/smurfstore.co.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfstore.co",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/smurfstore.co.json",
          "https://rdap.verisign.com/com/v1/domain/steamlvlup.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlvlup.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/steamlvlup.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamlevels.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlevels.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/steamlevels.com.json",
          "https://rdap.verisign.com/com/v1/domain/levelsteam.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flevelsteam.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/levelsteam.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamlevelu.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlevelu.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/steamlevelu.com.json",
          "https://rdap.verisign.com/com/v1/domain/eloking.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Feloking.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/eloking.com.json",
          "https://rdap.publicinterestregistry.org/rdap/domain/boosteria.org",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fboosteria.org",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/boosteria.org.json",
          "https://rdap.verisign.com/com/v1/domain/overgear.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fovergear.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/overgear.com.json",
          "https://rdap.verisign.com/com/v1/domain/blazingboost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fblazingboost.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/blazingboost.com.json",
          "https://rdap.verisign.com/com/v1/domain/dota2boost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdota2boost.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/dota2boost.com.json",
          "https://rdap.verisign.com/com/v1/domain/buyboost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuyboost.com",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit/buyboost.com.json",
          "https://phishdestroy.io/steam_dossier/ja/steam_tos_assets/auth-route-audit.json",
          "https://help.steampowered.com/en/faqs/view/365F-4BEE-2AE2-7BDD",
          "https://store.steampowered.com/privacy_agreement/#8",
          "https://www.edpb.europa.eu/system/files/2023-04/edpb_guidelines_202201_data_subject_rights_access_v2_en.pdf",
          "https://web.archive.org/web/20260810154631/https://store.steampowered.com/stats/support",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/design-review/part2/measurements.json",
          "https://phishdestroy.io/steam_dossier/ja/VALVE_EVIDENCE_PACK/databases/TOTAL_VALVE_SCANDALS_MASTER_DB.csv",
          "https://phishdestroy.io/steam_dossier/ja/license_disclaimer.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ja/index.content.json",
      "export_json_sha256": "a97976184793740af69126b51827457c2bcda66602979b69da79d3fa0c0f01f2"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ja/investigation_part2.html",
      "language": "ja",
      "title": "アカウントへのアクセスと説明責任 — 「Steam」ドシエ",
      "source_url": "https://phishdestroy.io/steam_dossier/ja/investigation_part2",
      "source_html_sha256": "3d306eeee1d7b9e1697be10c91bc0e2dcfe4b37998ac07c5fce9b237638f1abc",
      "exported_at": "2026-09-29T00:22:12.131Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "investigation_part2.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ja/investigation_part2.pdf?v=print-20260929-v5",
        "sha256": "ab011f9adedea0dcadfbd16d65c040848d8b3d975220b5ebd41979229e6f5738",
        "bytes": 567804,
        "pages": 8
      },
      "integrity": {
        "signed_object": "investigation_part2.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "investigation_part2.content.json.asc",
        "digest_file": "investigation_part2.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify investigation_part2.content.json.asc investigation_part2.content.json",
          "sha256sum -c investigation_part2.content.json.sha256"
        ]
      },
      "content": {
        "text": "『THE STEAM DOSSIER』/ II\n\nお客様のアカウント。彼らのアクセス権。誰が出ますか？\n\n公共部門の自動化。外部委託によるサポート。その代償を払わされるのは一般市民だ。\n\nインフラの状況、報告されている被害状況、そして主張の根拠となる資料を追跡してください。\n\nインフラストラクチャをトレースする↘\n別紙01／ライブ・シャドウ・マーケットの監視550,000+\n\nSteam LZTマーケットで現在販売中のアカウント\nまさに今この瞬間\n\n550,000+ ライブインベントリ · 231,829 過去のスクレイピングコーパス（198,320 スティラーログ）\n\n乗っ取られた Steam アカウントの主要な地下取引市場は、FSB Market (匿名名称。元の名称はここでは非公開です) (関連する別名は非公開です)は、Valveの公式Steam OpenIDを使用して、買い手と売り手の双方の認証を行います（openid.realm = https://FSB Market). 常に、50万件以上の盗まれたアカウントや不正アクセスを受けたアカウント（RedLine/Lummaからの窃取ログ、フィッシングによる取得データ、クレデンシャルスタッフィングなど）が、わずか数セント（$0.50–$2.00）で積極的に出品されている。いずれもFSB Market また関連フォーラム は、Valveのリンクフィルターによってブロックされています。これは、Valveが被害者を支援することなくBANしている63.06%の有料ボットアカウントにユーザーを供給する、いわゆる「産業用ユーザープール」です。\n\nリアルタイム情報：シャドウマーケットの監視（55万件以上、リアルタイム） ↗ ・キャプチャ記録を開く ↗ ・リンクフィルタのトレースを開く ↗55万以上 ライブ\n\n01 / 著者が参加するエコシステム\n\n自動化は書類の記録。\n\nプロジェクト名。公開されている機能。ツールをそのドキュメントまでたどった後、収集された開発者間の関係を調査する。\n\n252収集されたリポジトリ\n3,320GITHUBのプロフィール\n4,214プロフィール－リポジトリの組み合わせ\nValve インフラ地域図書館再利用可能なアプリケーション\n線は、記録された統合や依存関係を示しています。ノードを選択すると、その根拠を確認できます。\n\nマルチアカウントの自動化 / JustArchiNET\n\nArchiSteamFarm\n\nこのプロジェクトは、Steamのアカウント間で同時にカードを収集できることを明示的に宣伝しています。そのプロジェクトファイルには、SteamKit2の依存関係が宣言されています。\n\nプロジェクトの公式ドキュメントを読む ↗\n\nSteamKit → ArchiSteamFarm\n宣言された依存関係 ↗\n\n『関係性の集大成』\n\n40 寄稿者ラベル · 40 フォーカーラベル\n\n以下は寄稿者のサンプルです。これらのラベルは、リポジトリ間の関係を示すものであり、雇用関係や承認を示すものではありません。\n\n@JustArchi@renovate[bot]@JustArchi-ArchiBot@dependabot-preview[bot]@renovate-bot@actions-user@dependabot-support@Abrynos\n開発者グラフが示すもの\n\nこのグラフは、特定のプロジェクトとGitHubプロフィールとの間で公開されている貢献者およびフォーク者の関係を可視化したものです。これらは、リポジトリのフォーク、貢献履歴、プロフィール間の関連性といった公開記録です。重要なのは、公開されている能力や開発者間の関係に関するこの「紙の痕跡」が、Valveにどのような回答を求められているかということであり、この調査によって何が新たに発見されたかではありません。ソースのハッシュ値は、マップの出所.\n\nネットワーク全体を探索する ↗リポジトリのソースデータ ↓\n\n02 / 異なる資格。異なる力。\n\nどのキーですか一体何の話ですか？\n\nゲームをプレイするにあたり、プレイヤーが個人のWeb APIキーを発行する必要はありません。そこが、今回の調査の核心となる違いです。\n\n01 / ユーザーアカウント\n個人用Web APIキー\nsteamcommunity.com/dev/apikey\n\n許可されたAPI呼び出しに対して、ユーザーアカウントから発行されます。鍵の作成、可視性、失効、および不正使用の検出は、アカウントのセキュリティに関する事項です。\n\n02 / ゲームのバックエンド\nパブリッシャーのWeb APIキー\n\nSteamworksのパートナーは、ゲーム関連サービスを含む、サポート対象のバックエンド操作を行う際にパブリッシャーの認証情報を使用します。プレイヤーの個人キーは、これとは別の認証情報です。\n\n03 / 識別情報とセッション\nOpenID / セッショントークン\n\nOpenIDは、ウェブサイトに対して本人確認を行うものです。Steamセッションやリフレッシュトークンは、これとは異なる目的を持っています。これらの仕組みを、互いに置き換え可能な単一の「APIキー」として提示すべきではありません。\n\nValve には、ユーザーおよびパブリッシャーの Web API キーの両方が記載されています。したがって、Web API 全体は Steamworks から切り離されたものではありません。APIキーのドキュメント ↗ アーカイブ済み 2026-09-15 ↗ ・ゲームセッションの認証 ↗ アーカイブ済み 2026-08-29 ↗\n\n本ツールの作成者による記録 / 2024年3月\n\n自動化には、APIキー以外にもさまざまな方法があります。\n\nTrade Offer ManagerのWikiには、個別のAPIキーが存在しない場合に、Web APIの一部でセッションアクセストークンを使用する方法が記載されています。また、2023年後半からのキー作成におけるモバイル認証についても記載されています。メンテナーは、この方法でのトークン使用はValveではサポートされていないと述べていますが、これは古いドキュメント上の記述であり、実際に回避策が機能するかどうかを検証したものではありません。\n\nメンテナーの説明を確認する ↗ アーカイブ済み 2026-09-24 ↗\n\n「人間的な側面」／フィッシングの手口を具体的に示す事例\n\nまだ遊んでいる。すでに暴露されている。\n\n友人からのメッセージ。投票の依頼。「ありがとう」のページ。プレイヤーにとっては、そのタスクは完了した。しかし、侵害されたセッションは、その瞬間よりも長く続く可能性がある。\n\nプレーヤーの画面上\n\nF\nある友人の証言\n\n「私たちのチームに投票していただけますか？」\n\nそのリクエストは、見覚えのあるアカウントからSteamのチャットを通じて届きます。このシナリオでは、リンク先のページがクライアントのブラウザで開かれます。\n\nOUT OF SIGHT\n\n信頼は、ウェブサイトができる前から始まっている。\n\n友人のアカウントが乗っ取られると、フィッシングリンクの信憑性が高まってしまう可能性があります。Steamのインターフェースは、リンク先のウェブサイトの信頼性を保証するものではありません。\n\n送信元が既知 / 宛先が外部\n商品が販売される前に、アカウントのセキュリティが最優先事項となります。\n\nそのプレイヤーは、自動化用の認証情報を作成したり、制御権を委任したりするつもりはなかった。ゲームに復帰したからといって、そのアカウントが安全である証拠にはならない。Valveはセッションログ、APIキーの作成記録、およびデバイスの相関データを保持している。一方、被害者はそれらを保持していない。この非対称性が、説明責任の問題となっている。\n\nセッションへのアクセスと認証情報の種類\n\nAPIキーとログインセッションは、それぞれ異なる機能を持つ別個の認証情報です。キーを取り消しても、アクティブなセッションは終了しません。Valveの公式ドキュメントにはその両方が記載されています。Valveには、問題となっているアクションが行われた時点でどの認証情報がアクティブであったかを示すログが保存されています。 求められているのは、その記録の開示であり、調査によってでっち上げられた推論ではありません。トークンの取り扱いに関するメンテナー向けドキュメント ↗ アーカイブ済み 2026-09-24 ↗ ・Valve 主要なドキュメント ↗ アーカイブ済み 2026-09-15 ↗\n\n03 / 公式市場には上限がある\n\nそのアイテムはレアなものである可能性があります。制限はそのままです。\n\n上場上限価格を超える価格は、コミュニティマーケットへの1件の上場では、その全額で実現することはできません。\n\n参考希望価格$5,000商品の希望価格を変更する\n$100$20,000\n\nこれは公表された上限値を示す図解であり、評価や取引の推奨ではありません。\n\n上場上限≈ $1,800\nウォレットキャップ≈ $2,000\n\n公表された上場枠の上限を超えている。\n\nウォレット内の資金は銀行口座へ引き出すことはできません。こうした制約が、サードパーティのスキン市場が満たすべき需要を生み出しています。この需要は、出品制限やウォレットの上限によって生じている一方で、Valve自身のルールにより、商業事業者がこれに応えることが禁じられているのです。\n\nSteamの市場上限 ↗ アーカイブ済み 2026-09-21 ↗\n\n04 / サポート境界の内側\n\nデータを預かる。アクセスに関する責任を負う。\n\nValveのプライバシーポリシーでは、サポートの提供に必要な範囲において、第三者のサポート提供業者と個人データを共有することが明示的に規定されています。\n\n『ザ・プレイヤー』会計および証拠\n→\nバルブ復旧プロセス\n→\nサポート提供者委任アクセス\n\nプライバシーポリシー 第5.2条 ↗ ・Valve社のポリシーでは、第三者によるサポートアクセスが許可されています。未解明の点は、どのような権限が付与されていたか、どのような監査証跡が存在するか、そしてアクセスが不正利用されたとされる際に何が起きたか、という点です。\n\n2015年\nその規模は公にされていた\n\nValveは、アカウントの不正利用が広範囲に及んでいることを認め、対策について説明した。\n\nValve 出版物 ↗アーカイブ済み 2026-08-09 ↗\n2015年\nValveはその業務を外部委託し――そのことを明言した\n\nValveは、社内に小規模なSteamサポート・リーダーシップ・チームを擁しており、次のように述べている「いくつかの異なる会社に依頼した」 サポート業務の対応（Erik Johnson、Valve、Kotaku）を行うため、同社のプライバシーポリシー第5.2項では、これらの第三者がユーザーデータにアクセスすることを認めている。どの請負業者がアカウント回復権限を持っているかについて、Valveはこれまで一度も明らかにしていない — コミュニティでの議論では、Concentrixなどのベンダー名が挙がっているが、いずれもValve-確認されたものではない。この外部委託された窓口は、以下のいずれの事実が認められるよりも何年も前から設置されていた。\n\nKotaku：そのサポートについて Valve ↗アーカイブ済み 2025-07-11 ↗\n2023年\n最初の入学\n\nValveのCS:GOチームは、自チームのサポート依頼プロセスを通じてアカウントが乗っ取られた件について、書面で責任を認め、トレードを取り消した。\n\nアウトソーシングの事例を開く ↓\n2025年\n2回目の入学\n\n33か月後、Steam サポートからは、技術者が「当社の手順に従わなかったため、お客様のアカウントが他の人に復元されてしまった」との連絡がありました。同じ窓口。同じ結果。\n\nDexerto、2025年11月14日 ↗\n\n事件ファイル／HFBとアウトソーシング疑惑\n\nその入り口は、Steam サポートそのものでした。Valveは書面でそう述べた。\n\nDexertoが掲載したサポートからの回答によると、ValveのCS:GOチームは、アカウントが乗っ取られたことについて責任を認めているヘルプリクエストの手順を通じて — フィッシングページでもユーザーでもなく、独自のチャネルを通じて行われた。該当する商品は回収され、取引は取り消された。これは、Valveが他の被害者たちに「存在しない」と伝えている救済措置である。HFBの在庫は、以下の通り報告された。$2,000,000+ その日、そして$3,000,000+ その後の経過観察において；Qkssも同じように$1,000,000+で負け、何も手に入れられなかった.\n\nサポートの返信 / DEXERTOによる転載 · 2023年2月21日\n「サポートへの問い合わせを通じてセキュリティ侵害が発生し、これについてはCS:GOチームが責任を負います」\n記事と転載されたメッセージを読む ↗ アーカイブ済み 2025-08-18 ↗\n01 / どのバルブが開放されたか\n独自のサポートチャネルこそが、その入り口だった\n\nこの返信には、不正アクセスを受けた口座およびその取引の取り消しについて記載されています。Valveがそれらを取り消したため、取引は取り消し可能でした。当初の認証済みチケットは、このコレクションには含まれていません。\n\n02 / 解任では解決できなかった問題\n2025年11月、その扉が再び開いた。\n\n当該請負業者は、Steam人のサポートスタッフ全員を解雇した――これはDexerto経由でMzkshowが報じたものであり、Valveの社員声明によるものではない。 33ヶ月後、Steam Supportは別の債権回収業者に対し、「ヘルプリクエストに対応したサポート技術者が当社の手順に従わなかったため、お客様のアカウントが他者に復元されてしまった」と書面で通知した。Valve自身の記述であり、ほぼ同じ経路によるものである。\n\n2回目の入院、2025年11月14日 ↗\n03 / 「オープン」とは何か\nValveは、その請負業者の名前を一度も明かしたことがない\n\nこれらの情報源からは、請負業者も場所も特定されていません。これは報道の不備ではなく、Valveがユーザーアカウントへのアクセス権限を誰が持っていたかについて明らかにしていないという事実です。\n\nこの事件に関する当時の記録 ↗\n\nValveがまだ答えていない3つの質問は、誰がアカウント復旧を無効にできたのか、アクセス監査で何が判明したのか、そしてその後何が変更されたのか、というものです。\n\n保存されたサポートアーカイブに含まれるその後の申し立て\n\n2024年のRedditへの2件の投稿では、Mzkshowに関するさらなる調査結果が伝えられています。2024年7月の「VAC」禁止措置解除の事例と、2024年12月の「$13,000」在庫に関する事例です。これらは別々に報告された事案です。 それぞれの事例における責任の所在に関する疑問点は同じです。すなわち、誰がオーバーライド権限を持っていたのか、監査の結果何が判明したのか、そして何が変更されたのか、というものです。\n\n2024年7月14日 · 回復の報告 / VAC-banの事例 ↗2024年12月2日 · 報告された $13,000 在庫事例 ↗アーカイブ済み 2025-08-05 ↗保存された2つの投稿、ソース行、およびハッシュ ↓\n\n05 / 喪失を追って\n\nすべての金額ケースが必要です。\n\n2022年6月から2026年3月までの10件の事例。各金額は、その出典が公表した数値である――$6,300,000,$2,000,000+,$1,000,000+,≈$320,000,≈$300,000、そして288ユーロまで下がりました。Valveは、各取引のトランザクションログ、セッション記録、およびサポート監査証跡を保持していますが、これらはいずれも出力されていません。\n\nサポートチャネル21 6月2022\n$2,000,000+\nHFB — the largest inventory in the game\n\n報告された在庫評価額・2月の2023のフォローアップ記事で3百万ドル以上に引き上げられた\n\n7つの「Souvenir Dragon Lores」と、#1の「Blue Gem Karambit」。このナイフだけでも約$1.26の価値があります。3年間休眠状態でしたが、認証機能は有効なままでした。サポートのアカウント復旧手続きを通じて、メールアドレスとパスワードを変更しました。Valveは取引を取り消し、その責任を文書で明記しました。 取り消しが行われる前に、現金および仮想通貨での決済を行うmarket.csgo.comを通じて、$200,000+ 相当の収益がすでに引き出されていたと報告されています。取引の取り消しにより返還されるのはスキンであり、購入者がすでに銀行口座に振り込んだ金額ではありません。 このロールバックには不具合も生じました。ある購入者が「Souvenir Dragon Lore」をゲーム内のストレージユニットに隠していたため、スクリプトが自身のコンテナ内部を確認できず、Valveは盗難の取り消し処理中に$130,000のアイテムを複製してしまいました。これはアイテムIDとコミュニティからの報告により発覚し、7月に削除されました。2022,の購入者への返金は、ValveではなくBUFFによって行われました。\n\nDexerto、盗難が発生した日 ↗\nウォレットと購入07 7月2022\n>$500\n44 disputed Market purchases\n\n申告されたウォレットの支出 · 米ドル\n\nあるユーザーから、Dotaの2アイテム（低額品）が不正に購入されたこと、およびサポートの対応が不十分だったとの報告が寄せられています。\n\n訴状とリンク先のスクリーンショットをご覧ください ↗\nプラットフォームへの侵入14 8月2022\n$6,300,000\nCS.Money — 19,000+ ボットから入手したスキン\n\n価格評価・初回見積額　1.6Mドル\n\n攻撃者は、このマーケットプレイスの取引ボットが使用するモバイル認証ツールのファイルを乗っ取り、その内容をすべて削除した上で、痕跡を隠すために盗んだデータの一部を著名なトレーダーに流した。 コミュニティの研究者たちは、数時間のうちに55の攻撃者アカウントを特定した。Valveは一切の復元を行わなかった――サードパーティのサイトはSteamの外に存在すると、Steamは述べている。同社の在庫、取引API、およびアカウントシステムは、盗難の全過程に関与していた。\n\n当時の記録を読む ↗\nサポートチャネル21 2月2023の報道\n$1,000,000+\nQkss — 同じ扉、同じ俳優、正反対の答え\n\n報告された在庫評価額\n\nHFBの場合と同様に、同じ俳優が同じサポート依頼を通じて対応を受けた。HFBは8か月前に完全に解決されていたが、Qkssはそうではなかった。公開された記録には、視聴者数の多さ以外、この2つの事例を区別する要素は何もない。\n\nMzkshowの調査に関するDexertoの記事 ↗\nサポートチャネル2023に報告された\n≈ $320,000\nインサイダー取引そのもの――1年間にわたる取引\n\n約1年間の収益 · 在庫評価ではありません\n\nサポート部門からのアクセスにより、15年分までのアカウント履歴を確認できました。最初のCDキー、最初のメールアドレス、最初のクレジットカード情報――これらはまさに、アカウント復旧手続きで求められる証拠そのものです。 データベースを管理する側が、アカウントを管理する側との議論では常に勝つことになる。iBUYPOWERとTitan Katowiceの2014ホログラムが付いた盗難品M4A4 Howlは、35,000ドルで売却され、その事実を知る由もなかったNAVIのb1tの手に渡った。請負業者の対応は、Steamのサポート業務に従事する全従業員を解雇することだった。\n\n同件の捜査に関するEscorenewsの記事 ↗\nウォレットと購入09 DEC 2023\n€288\n2段階の保護策があるにもかかわらず、ウォレットを紛失してしまった\n\nTRUSTPILOT · 出典インデックス 16\n\nレビュアーは、アカウントがハッキングされたこと、およびマーケットでの支出に関する支援を拒否されたことを報告しています。このエクスポートには、個別のレビューURLが含まれていません。\n\nソースの出所を確認する ↗\nアカウントの復旧02 DEC 2024\n$13,000\n「マトヴェイ」――解雇から2年後\n\n著者の在庫推定値\n\nアカウント所有者本人でも照合できなかったアカウント情報を提供した人物に対し、アカウントの復旧が認められた。請負業者がSteamのサポートデスクを閉鎖した後も、同じ手順で同じ結果となった。\n\n保存されている申し立てを読む ↗\nアカウントの復旧09 5月2025\n≈ $10,000\n他人のチケットによる復旧\n\n申告された紛失品・米ドル\n\nケベック州のあるユーザーは、サポートが他者からの依頼を受けてパスワードをリセットし、アカウントの保護機能を解除したと主張している。\n\n当事者による苦情を読む ↗\nサポートチャネル13 11月2025\n≈ $300,000\nHawkeye337 — そしてValveによる2度目の書面による自白\n\n「2014」のカトヴィツェ・ホロコレクション全作品\n\n攻撃者は1のビットコインを要求し、コレクションをネゲブにスクレイピングして破壊し始めました。Steam サポートの回答：「このヘルプリクエストを担当したサポート技術者が当社の手順に従わなかったため、お客様のアカウントが他の人に復元されてしまいました。」 最初の認否から33ヶ月後、同じ事態が繰り返された。Xでこのスレッドがトレンド入りしてから数時間以内にアカウントは復元された。Qkssにはそのような読者層はなかった。\n\nDexerto, 14 Nov 2025 ↗\nウォレットと購入29 MAR 2026\n$50\n不正なチャージおよびプレゼントされたゲーム\n\nTRUSTPILOT · 出典インデックス 290\n\nこのレビュアーは、不正な支出や払い戻し請求が却下されたと主張しています。エクスポートされたデータには、個々のレビューのURLが含まれていません。\n\nソースの出所を確認する ↗\n\n出典および金額については、各情報源が報告した通りとします。Valveは、これらの事例すべてに関するトランザクションログ、セッション記録、およびサポート監査証跡を保持しています。それらを提出してください。保存されたRedditの投稿ではこの問題は解決されません。Valve自身の記録こそが、この問題を解決するものです。\n\nコレクション / 確認後\n\n231,829件のアカウントが販売中です。Valve には、すべてのログが格納されています。\n354 → 201\nTrustpilotの記録\n\n153件の重複行が削除されました。個々のレビューURLはエクスポート時に保持されませんでした。\n\n231,829\nSteam アカウント一覧\n\n33,509 「自動登録済み」として分類されています。198,320 コレクターの「スティラー」レーベルの下に分類されています。掲載情報は成約済みではありません。\n\nコレクション監査 ↓ソースアーカイブを検索 ↗",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "お客様のアカウント。彼らのアクセス権。誰が出ますか？"
          },
          {
            "level": 2,
            "id": null,
            "text": "自動化は書類の記録。"
          },
          {
            "level": 3,
            "id": null,
            "text": "ArchiSteamFarm"
          },
          {
            "level": 2,
            "id": null,
            "text": "どのキーですか一体何の話ですか？"
          },
          {
            "level": 3,
            "id": null,
            "text": "個人用Web APIキー"
          },
          {
            "level": 3,
            "id": null,
            "text": "パブリッシャーのWeb APIキー"
          },
          {
            "level": 3,
            "id": null,
            "text": "OpenID / セッショントークン"
          },
          {
            "level": 3,
            "id": null,
            "text": "自動化には、APIキー以外にもさまざまな方法があります。"
          },
          {
            "level": 2,
            "id": null,
            "text": "まだ遊んでいる。すでに暴露されている。"
          },
          {
            "level": 3,
            "id": "session-hidden-title",
            "text": "信頼は、ウェブサイトができる前から始まっている。"
          },
          {
            "level": 2,
            "id": null,
            "text": "そのアイテムはレアなものである可能性があります。制限はそのままです。"
          },
          {
            "level": 2,
            "id": null,
            "text": "データを預かる。アクセスに関する責任を負う。"
          },
          {
            "level": 3,
            "id": null,
            "text": "その規模は公にされていた"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valveはその業務を外部委託し――そのことを明言した"
          },
          {
            "level": 3,
            "id": null,
            "text": "最初の入学"
          },
          {
            "level": 3,
            "id": null,
            "text": "2回目の入学"
          },
          {
            "level": 3,
            "id": null,
            "text": "その入り口は、Steam サポートそのものでした。Valveは書面でそう述べた。"
          },
          {
            "level": 4,
            "id": null,
            "text": "独自のサポートチャネルこそが、その入り口だった"
          },
          {
            "level": 4,
            "id": null,
            "text": "2025年11月、その扉が再び開いた。"
          },
          {
            "level": 4,
            "id": null,
            "text": "Valveは、その請負業者の名前を一度も明かしたことがない"
          },
          {
            "level": 2,
            "id": null,
            "text": "すべての金額ケースが必要です。"
          },
          {
            "level": 3,
            "id": null,
            "text": "HFB — the largest inventory in the game"
          },
          {
            "level": 3,
            "id": null,
            "text": "44 disputed Market purchases"
          },
          {
            "level": 3,
            "id": null,
            "text": "CS.Money — 19,000+ ボットから入手したスキン"
          },
          {
            "level": 3,
            "id": null,
            "text": "Qkss — 同じ扉、同じ俳優、正反対の答え"
          },
          {
            "level": 3,
            "id": null,
            "text": "インサイダー取引そのもの――1年間にわたる取引"
          },
          {
            "level": 3,
            "id": null,
            "text": "2段階の保護策があるにもかかわらず、ウォレットを紛失してしまった"
          },
          {
            "level": 3,
            "id": null,
            "text": "「マトヴェイ」――解雇から2年後"
          },
          {
            "level": 3,
            "id": null,
            "text": "他人のチケットによる復旧"
          },
          {
            "level": 3,
            "id": null,
            "text": "Hawkeye337 — そしてValveによる2度目の書面による自白"
          },
          {
            "level": 3,
            "id": null,
            "text": "不正なチャージおよびプレゼントされたゲーム"
          },
          {
            "level": 2,
            "id": null,
            "text": "231,829件のアカウントが販売中です。Valve には、すべてのログが格納されています。"
          },
          {
            "level": 3,
            "id": null,
            "text": "Trustpilotの記録"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam アカウント一覧"
          }
        ],
        "links": [
          "https://phishdestroy.io/live-intel/?category=steam",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/lzt.market.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-evidence-lzt.json",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://github.com/JustArchiNET/ArchiSteamFarm/blob/main/ArchiSteamFarm/ArchiSteamFarm.csproj",
          "https://github.com/JustArchi",
          "https://github.com/renovate[bot]",
          "https://github.com/JustArchi-ArchiBot",
          "https://github.com/dependabot-preview[bot]",
          "https://github.com/renovate-bot",
          "https://github.com/actions-user",
          "https://github.com/dependabot-support",
          "https://github.com/Abrynos",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/automation-map.json",
          "https://phishdestroy.io/steam_dossier/ja/output_steam_network/network.html",
          "https://phishdestroy.io/steam_dossier/ja/output_steam_network/raw_data.json",
          "https://partner.steamgames.com/doc/webapi_overview/auth",
          "http://web.archive.org/web/20260915025812/https://partner.steamgames.com/doc/webapi_overview/auth",
          "https://partner.steamgames.com/doc/webapi/ISteamUserAuth",
          "http://web.archive.org/web/20260829124950/https://partner.steamgames.com/doc/webapi/ISteamUserAuth",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "http://web.archive.org/web/20260924181824/https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://store.steampowered.com/privacy_agreement/",
          "https://store.steampowered.com/oldnews/19618",
          "http://web.archive.org/web/20260809125516/https://store.steampowered.com/oldnews/19618",
          "https://kotaku.com/valve-explains-why-steam-customer-service-is-still-terr-1736988223",
          "http://web.archive.org/web/20250711004653/https://kotaku.com/valve-explains-why-steam-customer-service-is-still-terr-1736988223",
          "https://www.dexerto.com/counter-strike-2/valve-saves-hacked-cs2-player-threatened-with-ransom-over-300000-of-rare-stickers-3283135/",
          "https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "http://web.archive.org/web/20250818113925/https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "https://lis-skins.com/ru/blog/krupneisaia-mosenniceskaia-sxema-v-istorii-steam/",
          "https://www.reddit.com/r/cs2/comments/1e38jo4/stealing_accounts_and_removing_vac_bans_a_new/",
          "https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "http://web.archive.org/web/20250805141942/https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/outsourcing-archive-records.json",
          "https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "https://escorenews.com/en/csgo/news/44087-valve-steam-support-employee-accused-of-selling-inactive-accounts-inventories-worth-six-figures-b1t-has-one-of-these-skins",
          "https://phishdestroy.io/steam_dossier/ja/PART2_RESEARCH.md",
          "https://www.reddit.com/r/GlobalOffensive/comments/1h56shi/steam_support_is_stealing_accounts/",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/design-review/part2/quality-review.json",
          "https://phishdestroy.io/steam_dossier/ja/steam_evidence_archive.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ja/investigation_part2.content.json",
      "export_json_sha256": "4efe40b0e4a519e98d24ad5fa95854e86398dcea12c6309808c98d7a2f3683bd"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ja/legal_analysis.html",
      "language": "ja",
      "title": "彼らの利用規約、あなたの権利 — 『Steam』特集",
      "source_url": "https://phishdestroy.io/steam_dossier/ja/legal_analysis",
      "source_html_sha256": "31ef3e2394e378d6b8c5186e39222e6474914e1a689d457791d4622b08b23999",
      "exported_at": "2026-09-29T00:22:12.288Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "legal_analysis.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ja/legal_analysis.pdf?v=print-20260929-v5",
        "sha256": "b633469947bc609eb92550e2e5e2409524c9b8e6e56281e45df8c9fd7a1b45aa",
        "bytes": 637447,
        "pages": 7
      },
      "integrity": {
        "signed_object": "legal_analysis.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "legal_analysis.content.json.asc",
        "digest_file": "legal_analysis.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify legal_analysis.content.json.asc legal_analysis.content.json",
          "sha256sum -c legal_analysis.content.json.sha256"
        ]
      },
      "content": {
        "text": "法律・経済報告書\n法的分析 — 利用規約と規制遵守\n\n彼らの条件。 あなたの権利。\n\nこのセクションが証明すること\n\n本法務監査では、Valve社とSteamのユーザーとの間に、主要な規制管轄区域において存在する契約上の不均衡を評価する。 本監査では、取り消し可能なサブスクリプションライセンスが、法的に認められた消費者の所有権をどのように剥奪しているかを明らかにし、デジタル製品の再販売権消尽に関する欧州司法裁判所の判例を分析するとともに、『デジタルサービス法』（DSA）および『欧州電子商取引指令』（GDPR）第15.条に基づくコンプライアンス状況を検証する。この分析により、自動化された執行メカニズムが実質的な異議申し立ての機会なしに機能している実態と、プラットフォームの市場手数料がユーザー間のあらゆる取引において体系的に経済的価値を搾取している実態が浮き彫りになる。\n\n← エグゼクティブ・ブリーフィングに戻る\n\n本報告書では、Steamが公表しているプラットフォーム規約と消費者の実情との間の乖離について、法的、経済的、技術的な分析を行っている。その実情とは、救済手段がほとんどないままの自動的な執行が行われ、デジタル資産に対して企業が広範な支配権を行使しているという状況である。数値については出典を明記しており、一次資料まで遡ることができなかった数値は省略している。\n\nVector 1\n\n「所有権」を取り消し可能なライセンスに置き換え、契約に基づきデジタル資産を引き出すことができるようにする。\n\nVector 2\n\n自動的な措置（VACNet）によるBANについて、Steamのサポートは、これを撤回することはできないとしている。\n\nVector 3\n\nアカウントおよび資産の管理に加え、15%のCS2マーケット手数料（5%、Steam、および10%の発行者手数料）が課されることで、再販売のたびにエコシステムから価値が失われてしまいます。\n\n用語の非対称性\n免責条項および取り消し可能なライセンス\n2.1 「サブスクリプション」モデル対財産権\n\nSteam利用規約の第2項では、ユーザーに対して以下の権利のみを付与しています。 個人的、非独占的、譲渡不能かつ取り消し可能なライセンス. 本契約に基づき、Valveはいつでもアカウントを解約する権利を有し、未使用のSteamウォレット残高は失効する場合があります。\n\n2.2 「返金という幻想」対EU消費者権利指令\n法的枠組み\t返金手続き\t制限\nEU Consumer Rights Directive\tUnconditional 14-day right of withdrawal on digital content\tWaived if download begins with explicit consumer consent\nSteam SSA\t14 days / under 2 hours played\tValve may deny at its discretion for \"abuse\"\n評価\n\nValve EUの14-日間の法定撤回権は、製品を評価する前にダウンロードの時点で同意が求められる「14日間／2時間以内」という独自の期間を条件としています。この方針は、法定の権利を拡大するのではなく、むしろ制限するものです。これが法的に正当であるかどうかは、所管当局が判断すべき問題であり、ここで結論を下すものではありません。\n\n訴訟\n流通市場と独占禁止法\nUFC Que Choisir 対 Valve — フランス\n2019\nパリの裁判所：デジタルゲームにも権利消尽の原則が適用される――転売は合法\n10月2022\nパリ控訴院が判決を覆した\n23 10月2024\n最高裁（Cour de cassation）：ビデオゲームは、情報社会指令における「複合著作物」であり、ソフトウェアではない。デジタル再販 禁止. 『Valve』が優勢だ。\nWolfire Gamesの独占禁止法訴訟 — 米国（Valve独占禁止法訴訟、事件番号2:21-cv-00563）\n\nValveの「最恵国待遇（PMFN）」条項により、開発者は他のプラットフォームで『Steam』のキーをこれより安く販売することが禁じられています。競合するストアは――たとえValveの「30%」に対して12%の手数料を課している場合でも――そのコスト削減分を消費者に還元することはできません。\n\n336Valveの従業員総数（2021）。出典：公開された証拠開示資料。\n79Steamプラットフォーム全体を管理する従業員。出典：開示された証拠資料。\n$3.5M従業員1人当たりの純利益。出典：開示された証拠資料。\n\n開示された証拠開示記録によると、 2021の総売上高は8.5Bドル 336の従業員について。その 79-Steamのチームメンバー 373,000および日々のサポートチケットを、外部委託の自動応答コールセンターに振り分けることで対応しました。\n\n非封印事件記録添付資料・W.D, WASH. 事件番号2:21-CV-00563社内調査メモ\n\nティム・スウィーニー（エピック・ゲームズCEO）からゲイブ・ニューウェルへのメッセージ： 「決済処理のコストが 2–5% で、帯域幅のコストが CDN0.002/GB であるにもかかわらず、なぜ Steam は依然として売上高の 30% を徴収しているのでしょうか？ Steam の上位 25 タイトルを除外すれば、Valve は、その次の 1,000 の大半から、開発者自身が得た利益よりも多くの利益を上げているに違いないと思います。」\n\nスコット・リンチ（Valve Corporation 最高執行責任者）からゲイブ・ニューウェルへの社内転送メール： 「お前、怒ってるの？」\n\n宣誓供述書に対する反論（ブルームバーグ、2026）： 規則30 (b) (1) に基づく証言録取において、ゲイブ・ニューウェルは次のように証言した。 「Valveは、他のプラットフォーム上のサードパーティ製ソフトウェア開発者に対して価格を指示するような方針や慣行は一切持っていません。」 原告側は、競合ストアでより安い価格を設定している開発者に対して、積極的な価格監視や販売停止の脅迫が行われていたことを証明する、Valveの内部メモをニューウェル氏に突きつけた。3月下旬、2026, 連邦裁判所はValveの即決判決の申立てを却下し、32,000-開発者を対象とした集団訴訟を陪審裁判に付した。\n11月2024\n\n以下の件について集団訴訟の認定が下された ~ 『32,000』の開発チーム 1月以降に手数料を支払った人々 2017, およびこれと並行して提起された消費者集団訴訟。\n\n請求された損害賠償額\n\n$3.1B\n米国独占禁止法に基づく3倍の罰金 = $9.3B 潜在的な被ばく。\n\n6月 2026: 新たな訴訟では、マイクロソフトとValveが、PCゲームの流通における競争を阻害するカルテル協定を結んだと主張されている。\n\n金融犯罪およびAMLに関する正式な認定\nValve 公式の告白：ワールドワイド・フラウド・リキデーションズ（28 10月 2019）\n\n28年10月2019,日、Valveは、新規購入した『Counter-Strike』のコンテナキーの取引およびマーケットプレイスでの再販売を正式に終了しました。同社の公式発表（blog.counter-strike.net/2019/10/26113)、Valve社は、同社が構築した仮想経済が国際的なマネーロンダリングの拠点となっていたことを書面で認めた：\n\n「以前は、私たちが確認したキー取引のほとんどは、正規の顧客間で行われていました。しかし、最近では、世界規模の詐欺ネットワークが、不正に得た利益を現金化するためにCS:GOのキーを利用するようになっています。現時点では、マーケットプレイスで取引や販売されるキーの購入のほぼすべてが、詐欺によって入手されたものであると考えられています。」\n\n規制の背景： この告白は、ワシントン州ギャンブル委員会（WSGC）がValveに対して正式な最後通告を行ったこと、およびValveの法務顧問カール・クアッケンブッシュが、犯罪的なギャンブル行為の調査によりプラットフォームの運営が脅かされたことを受けて、7月に2016の「停止・差し止め命令」を23のスキンギャンブル関連ドメイン（CSGO Lotto、CSGOLounge、OPSkinsを含む）に対して発出したことを受けて行われたものである。\n\n管轄権\nロシアの権利者で、ユーザーからは連絡が取れない\n\n利用規約を見ると、Valveは、ほとんど責任を負わず、誰からも連絡が取れない存在として描かれている。ロック措置は恒久的なものであり、異議申し立ては却下され、「制裁対象地域」に関するたった一行の記述によって、地域全体へのアクセスが遮断されてしまう。そのような姿勢とは対照的に、Valveは、通常は「扱いにくい」と見なしている管轄区域においても、自社の商業的利益が脅かされる事態に直面した際には、どのような対応を取るのか。\n\nValve v. Touch Skins — ロシアにおける審理前の知的財産権侵害主張\n1 9月2026\nValveは、ロシアの法律事務所を通じて メリング・ヴォイティシュキン＆パートナーズ、は、の運営者に対し、審理前の請求通知を送付し、 タッチスキン、大規模なCS2スキンチェンジャーで、ロシア郵便とEメールで配送されます。\n理由\n違反の疑いがある点は、ソフトウェアの独占的権利、武器・ナイフ・手袋のスキンに関する権利、およびValveの商標権の3つである。運営者らの行為は、意図的かつ長期にわたるものと見なされている。\n需要\n直ちに運用を中止し、すべてのインフラを削除してください。— ソフトウェアの ソースコード、ウェブサイトおよびソーシャルメディアのページ――これに従わない場合、Valveは、ロシアの裁判所において、以下の事項について訴訟を提起する権利を留保する。 多額の金銭的補償 そして、この件を 犯罪評価のための法執行.\n結果\nその手紙を受け取った後、同プラットフォームはサービスを終了すると発表した。これは、Valveがロシアのスキン変更ツール開発者に対して法的手段を講じた初めての事例であると報じられている。\n\nデータマイナーのマキシム・「GabeFollower」・ポレタエフ氏（X、~11 202026）およびロシアのゲームメディアが報じた。これは訴訟前の申し立てであり、提訴された訴訟ではない。事件番号は公表されていない。ここでは、裁判記録ではなく報道内容として扱う。情報源： dota2.ru アーカイブ 2026-09-24 ↗ · シャズー.\n\n同じ管轄区域、反対方向\n\nValve ロシアの法制度や規制制度には精通している。それは ロスコムナドゾールの規制に準拠している: 規制当局の要請を受け、同サイトは禁止コンテンツを掲載していた260およびSteamのコミュニティページを削除した。また、ロスコムナドゾルは、Steamが法令の要件を満たしていると公に表明している。ロシアの「ランディング」法（連邦法 236-FZ（2022より施行）では、ロシアのユーザーにサービスを提供する大規模な外国のインターネットプラットフォームに対し、現地拠点の設置およびロスコムナドゾル（Roskomnadzor）との連絡窓口の開設が義務付けられている。Valveは、同規制当局からの削除命令に応じるだけでなく、現在ではロシアの弁護士を起用し、ロシアの裁判所による措置をちらつかせて、自社の「スキン」を知的財産として保護している。\n\nつまり、このプラットフォームは、収益に関わる限りでは、アクセス可能であり、十分な能力を備え、権利を主張している。これとは対照的なのがユーザーだ。制裁対象地域にいる有料顧客には、関係が終了したと告げられ、2038, のチケットが閉じられるまでコミュニティへのアクセスがロックされ、その決定の是非を問える場も存在しない―― 「彼らは私の金を受け取り、取引を処理してくれることに、大いに喜んでくれた」、その同じアカウントによる、同じイランのIPアドレスからの返金申請は、1年前に承認されていた（r/pcgaming、4 8月2026; さらに多くの是正勧告書が 「カード経済」展). 『Valve』は、スキンを守るために国家の法制度のあらゆる手段を動員している一方で、スキンを購入したユーザーに対しては、いかなる手続きも提供していない。\n\nValve Valveの利益が関わる場合――ロシアの弁護士、ロシアの裁判所による脅威、ロスコムナゾールの削除命令への対応など――は、その管轄区域を自らが行動し、遵守できる範囲として扱う一方で、その市場やその他のあらゆる市場のユーザーに対する義務については、いかなる手続きの対象外であるかのように扱っている。 収益が関わる場合は権利者としての顔を見せ、ユーザーの権利が問われる場面では、手の届かない当事者となるのである。\n\n出典： TASS（RKN：Steam準拠） · 連邦法「236-」FZ.\n\n法的機会主義\n仲裁条項の譲歩\n2023 — その攻撃\n\n法律事務所（Zaiger LLC、Mason LLP）は、ソーシャルメディアを通じて数千人のユーザーを募集し、数万件の個別仲裁申立てを同時に提起した。\n\nValveの露出\n\n$225M+\n事件の实体的審理が行われる前に、返金不可の仲裁申立手数料として支払われた。 米国仲裁協会（AAA）の「消費者仲裁規則」および「集団仲裁補足規定」に基づき算出された。Zaiger LLCおよびMason LLPが代理人を務める請求者らは、Valve社に対し、約75,000件の個別仲裁申立てを行った（これは、 Wolfire Games LLC ほか 対 Valve Corp., 事件番号2:21-cv-00563-JCC, W.D. ワシントン州）。AAAの消費者向け料金表に基づき、被告企業は、返金不可の事件管理手数料および仲裁人選任保証金として、1件あたり約3,000ドルを支払う（75,000件の申立て × $3,000 = 約225Mドルの事前の手続き費用負担）。 ハイテク業界における大量仲裁リスクに関するブルームバーグ・ローおよびロイターの法律関連レポートを参照のこと（2023–2024）。\n\n期間\tSSAの紛争解決手続き\t観察された効果\t結果\nBefore Sep 2024\tMandatory individual arbitration + class-action waiver\tIndividual litigation becomes economically irrational for users\tMass arbitration → $225M fee threat\nAfter Sep 2024\tDisputes in King County, WA courts only\tArbitration costs are avoided; cases consolidate in a single forum\tClass actions now possible\n結論\n\n10年以上にわたり、SSAは利用者に対し、陪審裁判を受ける権利を放棄し、個別仲裁を選択するよう求めていました。 Valveにとってこの仕組みが財政的に大きな負担となるような大量の仲裁申立てが行われたことを受け、SSAは改正され、紛争はキング郡の裁判所へ付託されることとなった。この変更は、実質的なオプトアウトの選択肢なしに提示された。すなわち、これを受け入れなければ、アカウントを削除されることで、購入したデジタル資産へのアクセス権を失うことになっていたのである。\n\nアルゴリズムによる執行\nVACNet、有罪推定、および偽陽性\n10月2023 — AMD Anti-Lag+\n\nAMDのドライバー更新（v23.10.1）により、CS2で「Anti-Lag+」が有効化され、ゲームのDLL関数が傍受される事態が発生しました。VACはこれをチートコードの注入と判定し、Valveが介入する前に、何千人もの正当なユーザーに対して永久利用停止処分を下しました。\n\n12月2023 — 高DPI\n\n10,000を超えるDPI設定でカメラを急速に回転させたプレイヤーは、永久利用停止処分を受けました。VACNetでは、マウスの物理的な動きと「スピンボット」チートを区別することができませんでした。\n\nサポートカテゴリ\t公称応答時間\t実際の結果\nRefund requests\t50 min – 1.5 hr\tAutomatic approval (<14 days, <2 hours played)\nAccount security / recovery\t3–12 hours\tDepends on documentation provided\nContesting a VAC ban\tForm response\tComplete refusal. Support cannot reverse VAC decisions. The ban is permanent.\nValveの公式方針\n\n「VACによる利用停止処分は恒久的なものであり、交渉の余地はなく、Steamのサポートチームによって解除されることはありません。」\n\nバン措置を通知するサポートチャネルでは、再審査の拒否についても同様に通知されます：Steam サポート側は、VACの決定を覆すことはできないと述べています。ユーザーにとっては、アルゴリズムによる判定が最終的な結果となります。\n\n転売の経済学\n仮想資産の管理と再販売手数料\n15%CS2の市場手数料 — 再販売のたびに価値が減少する\n反復\t購入者の残高\t売り手は受け取る\t『バーンド』（15%）\n1\t$100.00\t$85.00\t$15.00\n2\t$85.00\t$72.25\t$12.75\n3\t$72.25\t$61.41\t$10.84\n10\t$23.16\t$19.68\t~$3.47\nTotal\t$100 → dust\tValve collects the 15% fee on each resale. Users must add new money to keep trading.\nCS2のトレードアップに関するルール変更 — 10月 2025\n\n事前の予告なしに、ValveはCS2のトレードアップ契約のルールを変更し、コバート品質のアイテムと引き換えに、レアなナイフやグローブを確実に獲得できるようにした。その結果、ナイフの価格は下落し、コバート品質のアイテムの価格は急騰し、市場全体でパニック売りが相次いだ。\n\nValveが掲げる法的根拠は、社会保障法（SSA）第7条であり、プラットフォームのルール変更に対する責任は一切負わないとしている。Valve ルールが予告や補償なしに変更される可能性のある経済環境において、リスクを負うのはユーザーである。報告されている市場全体の損失額については議論の余地があり、一次情報源がないため、ここでは記載しない。\n\n欧州の規制当局の対応\nUOKiK、DSA、およびデジタル公正法\nUOKiK — ポーランド、5月2024\n\nポーランドの独占禁止当局（UOKiK）は、Valve社および国内のゲームパブリッシャー・ディストリビューター5社に対し、価格操作、価格均一化を義務付ける制限条項、および地理的ブロック（ジオブロッキング）の慣行の疑いについて、正式な独占禁止法違反調査を開始した。これらの行為により、ポーランドの消費者は、近隣のEEA（欧州経済領域）市場と比較して、デジタルゲームを最大20%も高く購入せざるを得なくなっていた。 この独占禁止法調査の一環として、UOKiKの調査官と警察は、国内の提携パブリッシャーおよびディストリビューターのポーランド国内事業所（Valveの子会社事務所ではない。Valveはポーランドに法人を保有していないため）に対し、早朝の家宅捜索および証拠押収を行った。科される可能性のある法定罰金は、年間売上高の最大10%に相当する。 出典： UOKiKの公式発表「UOKiK委員長がValveおよびゲーム開発者らに対して調査を開始した」、5月 2024.\n\nデジタルサービス法（DSA）\n\n自動モデレーションにおける透明性が求められます。SteamはVACNetに関する誤検知（false positive）や検知漏れ（false negative）のデータを一切公開しておらず、同社のサポートチャネルでは、VACによる判定は覆すことができないと明記されています。\n\nデジタル公正法 — 2026\n\n想定される規定：有料コンテンツへの恒久的なアクセス権の確保、権利放棄の場面における「ダークパターン」の禁止、デジタル資産における財産権の承認、および在庫の恒久的な没収からの保護。\n\n結論\n規則と記録の間に確認された不一致\n1\n\n所有権の格差。 ユーザーは、契約によりValveが取り消すことができるライセンスに対して、全額を支払っている。フランス最高裁（10月 2024）は、デジタル再販は保護の対象外であるとの判断を示し、この見解を法的に確定させた。\n\n2\n\nアルゴリズムによる執行。 VACNetは誤った利用停止処分を下しました（AMDドライバー、高DPIに関する事案）。Steam サポート部門は、VACの決定を覆すことはできないとしており、したがってアルゴリズムの判断が最終的な決定となります。\n\n3\n\n手数料の節約。 15%のCS2マーケット手数料（5%、Steam、および10%の発行者手数料）は、再販売のたびに価値を目減りさせ、プラットフォームのルールは予告なく変更される可能性があります。Valveは、SSAに基づき、かかる変更に対する責任を免責されます。\n\n4\n\n仲裁条項が削除されました。 SSAは9月、2024,、大量の申し立てによりValveが約225百万ドルの手数料を負担することになったことを受け、強制仲裁制度を廃止した。ユーザーには、この変更に対する実質的なオプトアウトの選択肢は与えられなかった。\n\n5\n\n選択的管轄権。 Valve ロシアの法律事務所（Melling, Voitishkin & Partners）を起用し、Touch Skins社に対してロシアでの訴訟をちらつかせた一方で、同市場のユーザーに対する自社の義務については、いかなる司法手続きの対象外であるかのように扱った。Valve社は、自社の商業的利益が関わる場合には権利者として振る舞い、ユーザーの権利が関わる場合には連絡の取れない当事者として振る舞っている。\n\n← 第1部：プロキシのバイパスとギャンブル第2部：アクセスと説明責任 →\n\n法律関連の情報源および判例記録については、元の発行元および保管先を明記しています。原資料に対する所有権を主張するものではありません。",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "法的分析 — 利用規約と規制遵守"
          },
          {
            "level": 2,
            "id": null,
            "text": "免責条項および取り消し可能なライセンス"
          },
          {
            "level": 3,
            "id": null,
            "text": "2.1 「サブスクリプション」モデル対財産権"
          },
          {
            "level": 3,
            "id": null,
            "text": "2.2 「返金という幻想」対EU消費者権利指令"
          },
          {
            "level": 2,
            "id": null,
            "text": "流通市場と独占禁止法"
          },
          {
            "level": 3,
            "id": null,
            "text": "UFC Que Choisir 対 Valve — フランス"
          },
          {
            "level": 3,
            "id": null,
            "text": "Wolfire Gamesの独占禁止法訴訟 — 米国（Valve独占禁止法訴訟、事件番号2:21-cv-00563）"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve 公式の告白：ワールドワイド・フラウド・リキデーションズ（28 10月 2019）"
          },
          {
            "level": 2,
            "id": null,
            "text": "ロシアの権利者で、ユーザーからは連絡が取れない"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve v. Touch Skins — ロシアにおける審理前の知的財産権侵害主張"
          },
          {
            "level": 3,
            "id": null,
            "text": "同じ管轄区域、反対方向"
          },
          {
            "level": 2,
            "id": null,
            "text": "仲裁条項の譲歩"
          },
          {
            "level": 2,
            "id": null,
            "text": "VACNet、有罪推定、および偽陽性"
          },
          {
            "level": 2,
            "id": null,
            "text": "仮想資産の管理と再販売手数料"
          },
          {
            "level": 3,
            "id": null,
            "text": "15%CS2の市場手数料 — 再販売のたびに価値が減少する"
          },
          {
            "level": 3,
            "id": null,
            "text": "CS2のトレードアップに関するルール変更 — 10月 2025"
          },
          {
            "level": 2,
            "id": null,
            "text": "UOKiK、DSA、およびデジタル公正法"
          },
          {
            "level": 2,
            "id": null,
            "text": "規則と記録の間に確認された不一致"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/ja/#briefing-heading",
          "https://dota2.ru/news/67707-valve-cerez-uristov-napravila-krupnoj-rossijskoj-skincendzer-platforme-trebovanie-o-prekrasenii-deatelnosti/",
          "http://web.archive.org/web/20260924181657/https://dota2.ru/news/67707-valve-cerez-uristov-napravila-krupnoj-rossijskoj-skincendzer-platforme-trebovanie-o-prekrasenii-deatelnosti/",
          "https://shazoo.ru/2026/09/12/190508/valve-cerez-rossiiskix-iuristov-dobilas-zakrytiia-krupnogo-skinceindzera-dlia-cs2",
          "https://www.reddit.com/r/pcgaming/comments/1vf24lu/warning_to_all_gamersexpats_steam_took_my_money/",
          "https://phishdestroy.io/steam_dossier/ja/card_economy.html#asymmetry",
          "https://tass.ru/obschestvo/23235387",
          "https://base.garant.ru/401414628/",
          "https://uokik.gov.pl/postepowanie-wyjasniajace-w-sprawie-valve-i-dystrybutorow-gier",
          "https://phishdestroy.io/steam_dossier/ja/",
          "https://phishdestroy.io/steam_dossier/ja/investigation_part2.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ja/legal_analysis.content.json",
      "export_json_sha256": "2babb6beecf7d331d998d299a1fbfc21dd796b640007345c5d9f8e7a6674f0dc"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ja/license_disclaimer.html",
      "language": "ja",
      "title": "ライセンス・権利・免責事項 — PhishDestroy",
      "source_url": "https://phishdestroy.io/steam_dossier/ja/license_disclaimer",
      "source_html_sha256": "799414481fb728ebb5701c704b9ec920949e241d5c1a94ad7d397cd1dbd70e6d",
      "exported_at": "2026-09-29T00:22:14.058Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "license_disclaimer.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ja/license_disclaimer.pdf?v=print-20260929-v5",
        "sha256": "c5ead227526fee339b532048d53a95af54dca61c4b3457b0d7db2e624c8d5b2e",
        "bytes": 500247,
        "pages": 10
      },
      "integrity": {
        "signed_object": "license_disclaimer.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "license_disclaimer.content.json.asc",
        "digest_file": "license_disclaimer.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify license_disclaimer.content.json.asc license_disclaimer.content.json",
          "sha256sum -c license_disclaimer.content.json.sha256"
        ]
      },
      "content": {
        "text": "PHISHDESTROY科学捜査 · Valve / Steam\nライセンス・権利・免責事項\nライセンスおよび法的免責事項 — パブリックドメインへの寄贈\n\nすべての権利 人類に身を委ねた。\n\nこのセクションが証明すること\n\n本文書は、「PhishDestroy」Steam ドシエを管理する、無条件のパブリックドメインへの寄贈（CC0 1.0 Universal）およびMITソフトウェアライセンス条項を定めるものである。すべてのフォレンジック調査結果、証拠データセット、ネットワークグラフ、および分析手法は、世界中の規制、法律、学術分野において制限なく利用できるよう、取り消し不能な形でパブリックドメインに提供される。\n\n← エグゼクティブ・ブリーフィングに戻る\n\nPhishDestroy この資料に関するあらゆる権利（複製、販売、自身の名前を記載することなど）を放棄します。以下は、一つの語り口で書かれた2つの文書です。一つは、私たちが普段通りの書き方で記したValveへの公開書簡であり、もう一つは、この内容を今後推進していく当局に向けて作成された正式な権利放棄書です。\n\n調査・Valve Corporation / Steamパブリック版 — 有効期限なし、取り消し不可\n免除\n第I節ライセンス — 厳密な法的な部分というよりは、人間的な側面\n\nPhishDestroy この素材に関するあらゆる権利を放棄します。ゼロ。一切なし。完全に手放しました。複製しても、販売しても、自分の名前を付けても、上司の体にタトゥーとして彫っても、何でも構いません。クレジット表記も、DMも、お礼のカードも一切不要です。\n\n実際のルールが1つ（そう、たった1つです）\n\n自分がテロリストかどうかは、あなた自身が決めることではありません。\n\nロシア、またはOFACの制裁対象国にお住まいのユーザーの方は、本資料は対象外です。抜け道などありません。制裁の下でどうぞお楽しみください。\n\nもしモスクワにいながらSteamの地域設定をトルコに変更したなら――その独創的な地理感覚、おめでとう。あなたは依然としてロシア人です。制裁は依然として適用されます。まさにそれが肝心な点なのです。\n\n第II節これが何であり、なぜ存在するのか\n\nValveに関する情報を、Valveの平均的な社員が自分自身について知っていることよりも多く公開していく予定です。これは自慢ではありません。ただ、そうなってしまっただけです。\n\nどうしてこんなことになってしまったのか？　面白い話なんだけど、Steamが実質的に私たちを作り出したんだ。そのサイトは、詐欺師やサポートチケット、利用停止回避のエコシステムといったものの中で私たちを育ててくれた――そして今、こうしてここにいるわけだ。恨みなんてないよ。むしろ、詩的だと言えるかもしれない。\n\nまだその経緯を知らない方のために――私たちはすでに、Valveの非常に高額なヨーロッパの弁護士たち（ご参考までに、Taylor Wessingです）と面会しています：\n\nhttps://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d アーカイブ済み 2026-08-21 ↗\n\n素敵な出会いだった。特に、彼らの時間単価を考えるとね。\n\nValveは知っていたのか？　はい。Taylor Wessingは知っていたのか？　ほぼ間違いなく「はい」だ。しかし、あれほど裕福であれば、法律というのは義務というより、あくまで「雰囲気」のようなものだろう？\n\n実のところ、それこそが答えのすべてなんです。\n\nSteam 長年にわたり、詐欺師たちを「育てて」きました。必ずしも意図的にそうしていたわけではありません――時には、単にValveと関わったというだけで、詐欺師たちにその「痕跡」がついてしまうこともありました。私たちはこれを大げさに言おうとしているわけではありません。正確に伝えようとしているのです。正直なところ、大げさに言うよりも正確に伝えるほうが私たちにとっては難しいのですが――これが私たちの書き方なのです。\n\nこれは矛盾でしょうか？\n— いいえ。\n\n解決できるのでしょうか？\n— はい。でも、NDAには署名しませんし、わずかな報酬でバグ報奨金プログラムに参加するつもりもありません。\n\nこのなりすまし問題について公に記事を書く前に、その修正が行われるまで4年以上も待たなければなりませんでした。というのも、もしもっと早く記事にしていたら、Steamは被害者ぶった顔をして「深刻な脅威だ！」と叫び、私たちを永遠に彼らの法的所有物にしてしまうような文書に署名させる見返りに、たかが小銭を提示してきたでしょうから。ごめんなさい、結構です。\n\n（ちなみに：Valve自体もNDAに違反しています。同社自身の従業員が違反しているのです。上層部の人たちです。でも、まあ、私たちの件について話しましょう。）\n\n第III節Valve への公開書簡 — マジで、これ読んでみて\n\nValve：このドメインの削除をご希望の場合は、メールにてご連絡ください。その件に関しては、外部の弁護士を介す必要はありません。\n\nご存じない方のために説明すると、パトリック博士はアバディーン大学で国際商法の法学修士号を取得しており、さらに――なんと――IT法に関する博士論文を実際に完成させた人物です。 彼は最近、テイラー・ウェッシングのパートナーに就任しました。同事務所のビジネスモデルは、Valveのような企業に法外な金額を請求し、相手側が資金や忍耐力を尽き果てるまで訴訟を長引かせることにあります。\n\n彼を責めるつもりはない。時間単位で報酬を支払う裕福で罪を認めた依頼人――これは確かなキャリアアップだ。ただ、あなたがその費用を負担すべきではないと思うだけだ。\n\n取引の概要（公開オファー、弁護士は不要）\n\nValveが現実的に手が届くのは、そのドメインだけだ。調査、紹介、そして関連リソースはすでに動き出しており、ドメインの有無にかかわらず、それらは継続される。\n\nそのドメインをご希望の場合は：\n\nIT法務の専門家に、適正な価格を設定してもらいましょう。\n\n50% は、「SEAL」財団に寄付されます。\n\nそのドメインを削除する。大騒ぎもなければ、裁判もなし。これで終わりだ。\n\nこれは脅しではありません。実際に手の届く範囲にある、たった一つのものに対する率直な提案です。これ以外の方法では手に入れることはできません――それがこの状況の構造なのです。\n\n私たちは「Valve」に直接的な「打撃」を与えることになるのでしょうか？ おそらく、彼らが財政的に痛手を感じるような形ではないでしょう。私たちも現実を見失っているわけではありません。しかし、私たちは、影響力を追い求めることなく、誠実かつ率直に活動していきます。なぜなら、私たちに影響力など必要ないからです。私たちに必要なのは、時間をかけてじっくりと見れば、もともと公に明らかだった事実を、世界中の人々に知ってもらうことなのです。\n\n当社には5年分のアーカイブがあります。Valveの弁護士たちが証拠開示手続きで提示した内容――捜査官が閲覧できるデータ、指紋、そして彼らが文字通り私たちに手渡した書類の記録――だけで十分です。生データをリークする必要はありません。\n\n誰が何を受け取るのか\n\n規制当局には原本が渡される。\n\n研究者やジャーナリストには、一部が削除されたバージョンが提供される（被害者の報告、子供たちのログイン情報、そしてValveの魅力的なサポートコメントは、言うまでもない理由で削除されている）。\n\n被害を受けたアカウントの中には未成年者も含まれていましたが、彼らには通知が行われませんでした。この調査結果は、被害者の報告や個人識別情報などが削除された状態で規制当局向けの資料に含まれています。これは、記事の中で取り上げるべき内容ではなく、データ保護当局が扱うべき事項だからです。\n\nまた、Valve さん――この件についてどう対応するかを決める前に、一つ明確にしておきたいことがあります。「PhishDestroy」はコミュニティであり、個人ではありません。コミュニティと話し合うこともせずに、コミュニティ宛てに法的文書を送付し、データを搾取しただけでアカウントを凍結した時点で、そのことはすでに理解されていたはずです。\n\nこのコミュニティは、Valveとは何ら対立関係にありません。私たちがわざわざ探したわけではありません。あなたが育てた詐欺師たちが、こちらに近づいてきたのです。私たちは彼らをブロックしました。そして、今こうしてここにいるわけです。\n\n第III-B節関連リソース — 特に Steam への注記\n\n増幅の仕組みについては率直に説明したいと考えています。なぜなら、それが存在しないふりをすることは不誠実だからです。\n\nPhishDestroy によると、現時点でのコミュニティの状況から判断すると、この資料を取り上げて活用してくれる提携先が少なくとも2つあるようです。\n\n実際には、これは次のようなことを意味します：\n\n彼らは、重複するテーマについて、それぞれ独自の切り口で取り組んでいる。\n\n彼らは独立しています――私たちの指示に従うこともなければ、私たちが彼らの指示に従うこともありません。大まかなテーマは同じですが、手法は異なります。\n\n彼らはパート1.では活動を開始しません。彼らは注視しています。\n\nValveが当該サイトの削除を行わないことを選択した場合：\n\n「Part 2」または「Part 3.」の後に、それらが公開される見込みです。\n\n彼らは私たちの研究から有用な部分を取り入れ、それに独自の知見を加え、自分たちの名前で発表するだろう。\n\nまさにこれが、1条のライセンスが想定しているようなケースです。コンテンツは必要な場所へ行き、補足され、さらに充実していく――そして、私たちも相手も、互いに帰属表示の義務を負うことはありません。\n\n（責任の連鎖について疑問を抱いている弁護士の方へ：そのようなものは一切ありません。これらの情報源は、当社からの指示も、資金提供も、データ提供も受けていません。彼らは公開されている情報を読み、独自の結論を導き出しているだけです。まさに、あなたも同じようにできるのです。）\n\nこれは相手を威嚇するために言っているわけではありません。Valve側の戦略立案担当者が、情報環境が実際にどのような状況にあるかについて正確な情報を得られるようにするために言っているのです。\n\n私たちの資料を引用し、それを補足する情報源の一つが「記事」です。2つの情報源がそれぞれ独立して同様の結論に達している場合、それは「パターン」となります。規制当局が注目するのは、こうしたパターンなのです。\n\n第IV節金、禁止措置、そしてこの一連の騒動\n\nSteamがギャンブルサイトや詐欺師を排除していることについて、重要な点はこうだ。それは「取り締まり」ではない。単なる「収益確保」に過ぎないのだ。Valveは金を懐に入れ、手を洗い、その後ステージに上がって、ポケモンカードや野球について、誰もが納得するような立派な話を皆に聞かせるのだ。\n\nサポート側の不正行為が記録されている事例としては、2月にValveが、ヘルプリクエストを通じて高額アカウントが不正アクセスされたことについて責任を認めた書面による声明（2023）や、320のインサイダー取引事件を受けてDexertoおよびEscorenewsが報じた請負業者スタッフの解雇事例などが挙げられる（第II部 §04 · メイン・ドシエ §14.1) — これらは、公表された自白や調査報道に基づいている。サポートスタッフがギャンブルの副業を行っていたり、利用禁止措置を解除する見返りに手数料を受け取っていたりするという根拠のない噂は、公的な記録では裏付けられておらず、本稿では除外している。\n\n一方、Valveは、2017.におけるスキンの適切な追跡機能を廃止しました。彼らは自社のフォーラムでもこの件について議論していました。それを「ギャンブル対策」と呼んでいましたが、実際には、スキンのギャンブルエコシステムはその後も何年にもわたり、Steamのインフラを通じて数十億単位の取引を処理し続けていました。実に素晴らしいブランディングですね。\n\n次のことを証明します：\n\nスキンズはモネロよりも匿名性が高い\n\nペルーのカルテルが、資金移動に『Dota』の「2」スキンを利用したとされる\n\nSteam 機能的には、約7B相当の「トレーディングカード」（そう、彼らは実際に検察官に対して「トレーディングカード」と発言したのです）を用いた制裁回避装置である\n\nスキンに関する動画があるよ。きっと見ることになるよ。\n\nまた、次のこともわかっています：\n\nRedditのモデレーションには、Valveが影響を与えています。\n\nサードパーティ製のSteamデータインフラストラクチャ（例えば steamid.uk)は個人によって運営されています（msart) および、これと連携している姉妹プロジェクトである禁止リスト（steambans.com アーカイブ)は、Valveコミュニティの正式なモデレーターによって共同で管理されています（killahinstinct_) — プラットフォームによる利用停止措置に対する独立した監査を、Valveの管轄内に完全に委ねることになる（「カード経済」の「08」の項を参照のこと。)\n\n自分たちでコントロールできないものは、禁止してしまう\n\nValve：もしあなたが引き続き知らぬふりを続けるなら――構いません。あなたの「安全な避難場所」は把握しています。Google Analyticsは、いずれにせよユーザーのIPアドレスを匿名化しています。何が削除されているかは私たちにも分かります。ただ、あなたの弁護士たちが気にするほど安価にそれを証明することはできないだけです。今のところは。\n\n第V節マルウェアの話 — ええ、その件については触れています\n\n一連の出来事の経緯について、容赦なくはっきりさせておきましょう。なぜなら、それこそがあなたの正体を如実に暴くからです。\n\n私たちは、このゲームの脆弱性を公に開示することはありません。また、Steam にも報告することはありません。同プログラムでは秘密保持契約（NDA）の締結が求められており、これに署名してしまうと、影響を受けたユーザーに対して自分のアカウントに何が起きたのかを伝えることができなくなってしまいます。アカウントを失った方々や規制当局への情報開示こそが、この取り組みの目的であり、秘密保持契約はその目的と相容れないものです。\n\n実際に起きたことはこうです。この脆弱性は、関係者の間では事実上「公然の秘密」となっています。独立系のセキュリティ研究者が、すでに完全なエクスプロイトをSteamサポートに突きつけていたことは、確かな事実です。その段階はすでに終わっています。貴社は、自社の形式的なルートを通じて正式に警告を受けているのです。\n\nでは、Valveはどのような対応をとったのでしょうか？　まったく何もしていませんでした。なぜなら、Valveにとって、セキュリティは利益にはつながらないからです。むしろ、まったく逆なのです。セキュリティはコストセンターに過ぎません。脅威が臨界点に達し、壊滅的な広報上の大失態を引き起こすまでは、Valveはそれを緊急事態として扱わないのです。\n\nでは、私たちは何をしているのでしょうか？　私たちは、その存在を一般に公表しているのです。なぜなら、「Valveは、システム全体に及ぶマルウェアの脅威を把握しているにもかかわらず、意図的に何もしないことを選択している」という事実は、現在この文章を読んでいる規制当局にとって極めて重要な情報だからです。\n\nこのゲームはとてつもなく大規模です。ここではその名前は伏せておきます。しかし、ひとつ理解しておいてほしいのは、\n\nこれは、サーバーから「ドライバーをインストールしてください」と求められるような、ありふれたCS:GOのスクリプトキディによるゴミのようなものとは違います。これは壊滅的な事態です。\n\nこれは『Unturned』レベルの悪夢だ。サーバー接続時のゼロクリックRCEだ。サーバーに参加する。何もクリックしない。 何もダウンロードしない。接続そのものが攻撃対象となり、あなたのマシンは完全に乗っ取られてしまう。現実を見よう。Valveの信頼されたデジタル証明書に便乗してRCEを仕掛け、ローカルのアンチウイルスを迂回する手法は、Steamではもはや目新しいことですらない。それは事実上、あなたのエコシステムに組み込まれた機能同然なのだ。\n\nValve すでにこのゲームの存在を知っている。 しかし、彼らは常套手段である卑怯な法的抜け穴に頼っている。技術的には第三者がゲームを開発しているため、Valveは一切の責任を免れているのだ。彼らはゲームの配信、決済処理、インフラのホスティングを行っているが、ゼロクリックRCEが数百万人のユーザーを脅かす事態になっても、彼らの態度は「当社のゲームではないため、当社の責任ではない」というものだ。\n\nこの問題が必然的に大騒動になったとき、サードパーティの開発者が責任を被ることになり、Valveは、解決に「協力」した責任あるプラットフォームであるかのように装って、その場を立ち去るだろう。まさにValveらしい臆病な振る舞いだ。この手口は何度も見てきた。\n\n規制当局、検察当局、そしてジャーナリストの皆さんに、Valveが活動中のマルウェアをどのように扱っているかを正確に理解していただくため、ここに記録として残しておきます。同社は、サードパーティの開発者を盾にし、秘密保持契約（NDA）による口止めを行い、プレイヤーを無防備な状態に放置しているのです。\n\n公開書簡の終わりフォーマルな話し方が始まります\n正式な語体・権威ある場面で\n宣言利用および権利について\n\nPhishDestroy プロジェクト・サイバーセキュリティ連合\n\nこの声明は、本照会資料に含まれるすべての提出書類および添付資料に添付されています。本資料が渡されるあらゆる当局、裁判所、規制当局、検察官、研究者、ジャーナリスト、または影響を受ける方々を対象としています。\n\n1. 利用に関する制限はありません\n\n1.1 本照会において連合が作成したすべての資料（事実の陳述、分析、作成した証拠資料、ツール、および調査結果）は、いかなる権利も留保することなく公開されます。\n\n1.2 どなたでも、当社への事前のお問い合わせや通知なしに、以下の行為を行うことができます：\n\nその全部または一部を複製すること；\n\nそれを適応させ、編集し、書き直し、構成を変更し、または修正すること；\n\nそれを変換してください；\n\n抜粋したことを明記せずにそれを抜粋すること；\n\nそれを公式文書、調査結果、決定、訴答書、報告書、または報道資料に盛り込むこと；\n\nそれを受取人自身の作品、あるいは受取人自身の調査結果であるかのように提示すること；\n\nそれを原料として使い、残りは廃棄する；\n\nそして、同じ条件で他の誰かにそれを引き継いでください。\n\n1.3 出典の明記は不要であり、求められてもいません。当連合の名称を挙げたり、引用したり、クレジットを記載したり、謝辞を述べたり、相談したり、通知したりする必要はありません。 本紹介資料が当局の業務に役立ったとしても、当連合が一切言及されなかった場合、それは「完全に満足のいく結果」であり、当連合は、その点について疑問が提起されることのないよう、あらかじめその旨を明記しておきます。\n\n1.4 一方、当局が連合を出典として引用する方が都合が良いと判断した場合は、そうしても構わない。その選択は完全に受領者の裁量に委ねられており、どちらの方法を採っても何ら影響はない。\n\n1.5 これは「権利放棄」であり、ライセンスの提供ではありません。これに対する承諾は不要であり、いかなる義務も課さず、また違反となることもありません。 当連合が公開するソフトウェアは、別途MITライセンスの下で公開されています。研究およびその成果は、法的に許容される最大限の範囲でパブリックドメインとして公開されており、管轄区域において権利放棄が認められない場合、当連合は同等の効果を持つ、取消不能かつ全世界を対象とするロイヤリティフリーのライセンスを付与します。\n\n2. なぜこれが単なる礼儀としてだけでなく、実用的な面でも重要なのか\n\n2.1 当局は、外部の当事者の依頼で行動しているように見えたり、その当事者と何らかの利害関係が生じたりすることを恐れて、その当事者から提供された資料を信頼することに合理的な躊躇を示すことがある。\n\n2.2 ここには、何ら関与すべき事項は存在しません。当連合は、何も求めず、何も受け取る権利もなく、何も保持せず、いかなる期待も抱いていません。当連合は、そうする根拠を一切保持していないため、後日、権利を主張したり、功績を主張したり、誤用について苦情を述べたり、資料の表現内容に異議を唱えたりすることはできません。\n\n2.3 したがって、この資料を利用する当局は、連合を代表して行動しているわけではない。単に、たまたま他者がまとめた公開情報を活用しているに過ぎない。\n\n3. もうすべて開いています\n\n3.1 連合の活動は、原則として公開されています：\n\n調査結果は、以下のサイトで公開されています。 https://phishdestroy.io かつ自由に閲覧可能であり、\n\nこのツールは、MITライセンスに基づき、以下のURLでオープンソースとして公開されています。 https://github.com/phishdestroy アーカイブ済み 2026-09-11 ↗;\n\nこの方法論は、照会文書そのものの附属書AのセクションAおよび16のセクションDに記載されており、各情報源の種類ごとの重要度や制限事項も含まれている；\n\n同連合は寄付を一切受け付けておらず、その方針については2018.の時点で公表しています。\n\n3.2 公表されていない資料は、法的に、あるいは安全上の理由から公表できないもの、すなわち、被害者や第三者の個人情報、および情報源が報復にさらされるおそれのある情報に限られます。こうした資料は、機密として当局に提供されており、証拠目録に記載されています。\n\n3.3 同連合は、他者の行動に対する監視を求めるのと同じ条件で、自らの行動に対する監視も受け入れる姿勢を示しており、データ処理に関する情報を関係当局に自主的に提供するとともに、廃棄に関する指示を求める要請も行っている。\n\n4. 証拠一式の完全性\n\n4.1 添付資料は、提出時に同封されるか、指定がある場合は、安全な通信経路を通じて要請に応じて提供されます。これらは公開アドレスでは公開されておらず、そのようなアドレスを推測してはなりません。この種の資料は、当局に直接提供されます。\n\n4.2 各配信には、提供されたすべてのファイルのSHA-256ダイジェストを記載した「SHA256SUMS」ファイルと、独立したOpenPGP署名「SHA256SUMS.asc」が添付されています。\n\n4.3 署名鍵は以下のURLで公開されています。 https://phishdestroy.io/.well-known/pgp-key.txt また、keys.openpgp.org にも掲載されています。この一連の投稿のすべてに、そのフィンガープリントがレターヘッドに記載されています。\n\n4.4 受信者は誰でも、自分が所持しているファイルが、送信されたままの状態で改変されていないものであることを、いつでも確認することができます：\n\ngpg --verify SHA256SUMS.asc SHA256SUMS\n\nsha256sum -c SHA256SUMS\n\n4.5 その目的は形式的な手続きのためではありません。それは、後日、証拠品の正確性や完全性について異議が申し立てられた場合、議論ではなく計算によってその問題を解決できるようにするためです。\n\n5. 登録について――なぜこの免除措置は単なる寛大さではなく、実用的なものなのか\n\n5.1 当局は、連合が公表した調査報告書を目にし、その内容が率直で、対立的であり、時には風刺的であると感じるかもしれない。その印象は正しい。連合は意図的にそのような書き方をしており、そのことについて謝罪するつもりはない。\n\n5.2 また、これは規制手続きや司法手続きにおいて不適切な表現であることも認識している。 重大な事案は、選挙運動のような口調で語られるべきではない。当局に提出される調査結果は、その限界を認めた上で率直に述べられるべきであり、読者が本質を理解する前に、その口調を差し引いて判断することを強いられるようなものであってはならない。\n\n5.3 まさにそれが、連合が著作者権を放棄する理由である。1条に規定されたこの権利放棄は、登録内容から実質的な部分を切り離すための仕組みである。当局は有用な部分を取り入れ、独自の表現で書き換え、連合の名称とともに、連合の文体による表現をすべて排除することができる。 そうしても何も失われることはなく、連合としてもその方が望ましいと考えています。\n\n5.4 また、連合は、この記録が「方法」そのものと誤解されないよう求めています。 公表された文面は対立的ではあるが、その根底にある実務は不注意なものではない。本報告書全体を通じて、推論は観察事実から区別され、証言は証言として明示され、情報源には重み付けがなされその弱点も指摘され、数値にはその限界が示され、連合が証明できない点は断定としてではなく、当局への質問として提示されている。 証拠が連合自身の立場に反する場合、連合はそれを明言している――並行する照会文の付属書A、7,段落およびセクションBを参照のこと。0\n\n5.5 この連合は、その活動姿勢と資金源の関連性について説明している。なぜなら、この二つは切り離せないものだからだ。 同連合は、いかなる者からも金銭を受け取らない――寄付も、報奨金も、依頼主も、スポンサーも一切ない。この拒否姿勢こそが、率直な発言を可能にしている。収入を守る必要がある組織は、自らが依存する政党について発言を控えざるを得ない。守るべきものがないため、同連合には発言を控える必要がないのだ。\n\nそれが、この連合が存続し続けている理由でもあります。他に原動力となるものは何もないのです。仕事は、ただ行われているから行われているのであり、それを担う人々が手を引けば、そこで止まってしまうのです。\n\n5.6 当局は、こうした主張を一切受け入れる必要はない。これは、連立政権の広報活動の口調が、現在審議中の案件に対する配慮の度合いとして解釈されないようにするためである。\n\n6. 連立政権が提供しているもの――同政権自身の言葉による説明\n\n情報、調査、観察。\n\n連合には主張する資格がないという結論は、一切示されていません。何かが推論されている場合は、その旨が報告書に記載されています。何かが証言に基づいている場合は、誰の証言であり、どのような制限があるかが報告書に記載されています。連合が質問に答えられない場合は、その旨も記載されており、誰が答えられるかも明記されています。\n\n同連合は、自身やいかなる個人に対しても、救済措置、支払い、承認、あるいは結果を求めてはいない。同連合が求めているのは、回答を強制する権限を持つ機関が、照会書に記載された質問をValve社に対して提示することだけである。\n\n結びの言葉この件を引き継いでくださる方へ\n\nこの資料を必要な場所まで届けてくださる方々に、心より感謝申し上げます。おそらく、そう簡単にはいかないでしょう。「Valve」は資金力が豊富ですし、「Taylor Wessing」は時間単位で料金を請求します――この組み合わせは、まさにあなたのような人々がゴールにたどり着く前に諦めてしまうよう仕組まれているのです。\n\n自分たちが何をしているのか、誰について書いているのか、私たちはわかっています。『Valve』が私たちを育ててくれたのですから、彼らを理解できないはずがありません。\n\nPhishDestroy Valve とは何ら対立関係にありません。私たちが遭遇した、あの規模の詐欺グループを唯一摘発しただけであり、Valve と争おうとしたわけではありません。単に、どの道を進んでも最終的に彼らに行き着いたというだけです。対立などではなく、単なるネットワーク構造の問題です。\n\nValve PhishDestroyの問題を解決できないのは、解決すべきものが何もないからだ。私たちには何の関わりもない。彼らの資金調達スキームや過剰利益に関するデータは、そのほとんどが公にされている――ただ、それを見るのに十分な時間を費やす必要があっただけだ。 これを「成功の百科事典」だと考えてみてください。「ロシアのハッカーに当社の無料ゲーム（有料版はそもそも海賊版にされないだろうが）を海賊版にされないよう、制裁に従わない方法」。その趣旨はお分かりいただけるでしょう。\n\n著作者情報は必要ありません。\n\n出典の明記は必要ありません。\n\n勝つ必要なんてない。\n\nこの照会書にすでに記載されている質問を、Valve に対して、回答を義務付ける権限を持つ、実質的な権限を持つ人物が尋ねる必要があります。\n\n以上です。お願いはそれだけなんです。\n\nケースは以下の場所に配置されます：\n\nhttps://steamdestroy.eth/\n\nhttps://steamdestroy.eth.limo （現在、不具合が発生しています。必要に応じて修正します）\n\n以下の会場に出展いたします：\n\nhttps://phishdestroy.eth.limo/ アーカイブ済み 2026-06-27 ↗\n\nhttps://phishdestroy.eth/\n\n署名入り物品2点・権利および出版された文章\n署名入り免責同意書何が署名されたのか、そしてその内容は何か\n\n権利付与文と研究テキストは、以下に個別に署名されたJSONオブジェクトとして記載されています。それぞれの独立したOpenPGP署名は、その隣に名前が記載されたJSONの正確なバイト列を認証するものです。権利付与文は権限を付与するものであり、テキストのスナップショットは公開される資料を特定し、その内容を包含するものです。\n\n1. 権利に関する声明 — license-rights.json\n\n署名付きオブジェクト： 完全な license-rights.json 28年9月付のパブリック・ライツ・グラント（2026.）が記載されたファイル。これに基づき、著作者による資料の複製、公開、編集、翻訳、結合、および商用利用が、出典の明示、通知、承認なしに許可されています。この署名は権利に関する声明の真正性を証明するものであり、個々のウェブページやPDFの本文の真正性を証明するものではありません。\n\n当初の署名入り許諾書は、変更されることなくそのまま保持されます。ウェブサイトの変更、別のファイルの公開、またはサイトの閉鎖によって、既存の許諾を取り消したり、その範囲を狭めたりすることはできません。第三者の資料については、それぞれの権利が保持されます。\n\n権利に関する声明（JSON） ↗ · license-rights.jsonの署名 ↗ · license-rights.json の SHA-256 ↗\n\ngpg --verify license-rights.json.asc license-rights.json\nsha256sum -c license-rights.json.sha256\n2. 公開されたテキスト — dossier-text.json\n\n署名付きオブジェクト： 完全な dossier-text.json ファイル。このファイルには、エクスポートされたページの実際に読み取れるテキストが documents[].content.text、各ページのタイトル、言語、ソースURL、ソースHTMLのハッシュ、見出し、および参照情報とともに。その documents このリストは、このスナップショットに含まれる正確なインベントリの一覧であり、言語別バージョンは別途記載されています。これは単なるハッシュのリストではなく、テキスト形式の公開物です。\n\n各エントリは、ファイル名とSHA-256によって、その軽量ページPDFを識別します。 documents[].pdf. また、このJSONでは、元の権利表示をURLおよびSHA-256,で特定しているため、公開されたテキスト、そのPDF、および該当する権利許諾書を、推測することなく照合することができます。リンク先の外部データベース、画像のオリジナル、および目録に含まれていないページは、このテキストのスナップショットには埋め込まれていません。\n\n署名付きテキストの全文（JSON） ↗ · dossier-text.jsonの署名 ↗ · dossier-text.json の SHA-256 ↗\n\ngpg --verify dossier-text.json.asc dossier-text.json\nsha256sum -c dossier-text.json.sha256\n\nドシエのホームページでは、「PDF」および「JSON」ボタンをクリックすると、リサーチ・バンドルがエクスポートされます。内部ページでは、そのページが公開されている言語でエクスポートされます。各ページのJSONファイルには、それぞれ個別の分離署名およびSHA-256ファイルが付属しており、そのファイル名は integrity オブジェクト。関連付けられたPDFを検証するには、そのSHA-256を計算し、それを pdf.sha256 検証済みのJSON内の値。このPDFはそのダイジェストによって紐付けられており、PDF形式のデジタル署名は含まれていません。\n\n3. 印刷用リサーチ資料セット — steam-dossier-{language}.content.json\n\n署名付きオブジェクト： 言語固有のJSONファイル全体（バンドルされた章のテキストを含む）は、 documents[].content.text、章ごとのページ範囲、ソース言語、除外ソースの一覧、および正確なPDFダイジェストは pdf.sha256. 5つの補足資料アーカイブはオンライン上で引き続きリンクされており、1つにまとめられてはいません。著者が作成した研究テキストはそのまま残され、画像カタログは出典へのリンクに置き換えられています。\n\n英語 JSON ↗ · OpenPGPの署名（本文とは別）↗ · SHA-256ダイジェスト ↗\n\nドイツ語 JSON ↗ · OpenPGPの署名（本文とは別）↗ · SHA-256ダイジェスト ↗\n\ngpg --verify steam-dossier-en.content.json.asc steam-dossier-en.content.json\nsha256sum -c steam-dossier-en.content.json.sha256\n\n公開検証鍵 ↗\n\n署名用フィンガープリント：129F C7F3 9C40 C69D 2EF3 C329 BFCF 9E8D D295 EE01\n\ngpg --import pgp-key.txt\ngpg --fingerprint 129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01\n\n表示されたフィンガープリントが上記のものと一致することを確認し、その後、正確なJSONファイル名に基づいて署名を検証してください。署名済みのJSONを編集すると、署名されたオブジェクトが変更され、元の署名は無効になります。有効な署名は公開されたバイト列を特定するものであり、研究結果そのものを独立して検証するものではありません。\n\nPhishDestroy — 公開調査 — すべての権利は人類に譲渡された\n\nOFAC管轄地域へのアクセス：禁止",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "ライセンスおよび法的免責事項 — パブリックドメインへの寄贈"
          },
          {
            "level": 2,
            "id": null,
            "text": "第I節ライセンス — 厳密な法的な部分というよりは、人間的な側面"
          },
          {
            "level": 3,
            "id": null,
            "text": "実際のルールが1つ（そう、たった1つです）"
          },
          {
            "level": 2,
            "id": null,
            "text": "第II節これが何であり、なぜ存在するのか"
          },
          {
            "level": 2,
            "id": null,
            "text": "第III節Valve への公開書簡 — マジで、これ読んでみて"
          },
          {
            "level": 3,
            "id": null,
            "text": "取引の概要（公開オファー、弁護士は不要）"
          },
          {
            "level": 2,
            "id": null,
            "text": "第III-B節関連リソース — 特に Steam への注記"
          },
          {
            "level": 2,
            "id": null,
            "text": "第IV節金、禁止措置、そしてこの一連の騒動"
          },
          {
            "level": 2,
            "id": null,
            "text": "第V節マルウェアの話 — ええ、その件については触れています"
          },
          {
            "level": 2,
            "id": null,
            "text": "宣言利用および権利について"
          },
          {
            "level": 3,
            "id": null,
            "text": "1. 利用に関する制限はありません"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. なぜこれが単なる礼儀としてだけでなく、実用的な面でも重要なのか"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. もうすべて開いています"
          },
          {
            "level": 3,
            "id": null,
            "text": "4. 証拠一式の完全性"
          },
          {
            "level": 3,
            "id": null,
            "text": "5. 登録について――なぜこの免除措置は単なる寛大さではなく、実用的なものなのか"
          },
          {
            "level": 3,
            "id": null,
            "text": "6. 連立政権が提供しているもの――同政権自身の言葉による説明"
          },
          {
            "level": 2,
            "id": null,
            "text": "結びの言葉この件を引き継いでくださる方へ"
          },
          {
            "level": 2,
            "id": null,
            "text": "署名入り免責同意書何が署名されたのか、そしてその内容は何か"
          },
          {
            "level": 3,
            "id": null,
            "text": "1. 権利に関する声明 — license-rights.json"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. 公開されたテキスト — dossier-text.json"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. 印刷用リサーチ資料セット — steam-dossier-{language}.content.json"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/ja/#briefing-heading",
          "https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "http://web.archive.org/web/20260821155801/https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "https://phishdestroy.io/steam_dossier/ja/investigation_part2.html#outsourcing-case",
          "https://phishdestroy.io/steam_dossier/ja/#theft-ledger",
          "https://steamid.uk/",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/groups/steambans",
          "https://steamcommunity.com/id/killahinstinct_",
          "https://phishdestroy.io/steam_dossier/ja/card_economy.html#governance",
          "https://phishdestroy.io/steam_dossier/ja/license_disclaimer.html",
          "https://github.com/phishdestroy",
          "http://web.archive.org/web/20260911040557/https://github.com/PhishDestroy",
          "https://phishdestroy.io/.well-known/pgp-key.txt",
          "https://steamdestroy.eth/",
          "https://steamdestroy.eth.limo/",
          "https://phishdestroy.eth.limo/",
          "http://web.archive.org/web/20260627040219/https://phishdestroy.eth.limo/",
          "https://phishdestroy.eth/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json.asc",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json.sha256",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json.sha256?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json.sha256?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json.sha256?v=print-20260928-v3"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ja/license_disclaimer.content.json",
      "export_json_sha256": "520b23775f1ac5c8c8ebffd7702db3e1c7a004dda13ca73ee6fb443fdf4c122e"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ja/market_economics.html",
      "language": "ja",
      "title": "1つのインフラ、2つの市場 — 『Steam』特集",
      "source_url": "https://phishdestroy.io/steam_dossier/ja/market_economics",
      "source_html_sha256": "976230ccf28b3ae4e9b60343e225c07539e8526d90245044de6e64d43ec8ceca",
      "exported_at": "2026-09-29T00:22:14.057Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "market_economics.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ja/market_economics.pdf?v=print-20260929-v5",
        "sha256": "669e9b53eb17f4d7c5beb191dbf6f7ee21f3bd0523c3a3e3ec23671d7d2ef287",
        "bytes": 480038,
        "pages": 7
      },
      "integrity": {
        "signed_object": "market_economics.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "market_economics.content.json.asc",
        "digest_file": "market_economics.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify market_economics.content.json.asc market_economics.content.json",
          "sha256sum -c market_economics.content.json.sha256"
        ]
      },
      "content": {
        "text": "別紙VII・市場構造・20 9月 2026\n市場経済 — 2つの経済と上場上限\n\n彼らのインフラ。 2つの経済。\n\nこのセクションが証明すること\n\n本章では、Valveが設定した$1,800の上場上限額および引き出し不可のウォレット残高によって生じた、市場における体系的な二極化について分析する。 38で、上場時評価額が約1.28 billionに上る、稼働中の外部スキン取引所を調査した結果、高額取引は必然的に外部のシャドー・プラットフォームへと移行しつつも、Steamの基盤となる取引および認証インフラに依存していることが明らかになった。利用規約では商業利用が形式上禁止されているものの、Valveは、公表された執行記録がないまま、この二層経済を促進し、収益化している。\n\n← エグゼクティブ・ブリーフィングに戻る\n\n38 現在稼働中のサードパーティ製CS2マーケットプレイスに加え、Steam独自のマーケットプレイスも含まれます。 いずれかに掲載されているすべてのスキンについては、 Steamのインベントリを経由し、APIで取引されなければなりません。Valveの規則では、 当該インフラの商業的利用が禁止されています。約1.28億ドルのサードパーティ掲載価値が存在する一方で、 この規則の執行に関する公的な記録は見つかっていません。\n\n$1.28B\n第三者による評価額・38プラットフォーム\n53.2M\n掲載中のオファー · 38 サードパーティ市場\n70.1K\nSteam スナップショットに記載されている項目\n41×\n第三者による評価額とSteamの31Mドルの比較\n主な調査結果\n1つのインフラ。2つの経済。\n\nSteam アイテム、インベントリ、取引を管理しています。以下のいずれかのプラットフォームで販売されるすべてのスキンは、 Steamの取引サイト API を経由しなければなりません。これは、直接確認できる構造的な依存関係です。 Valveの 独自のコミュニティマーケットでは、販売額に対して手数料が徴収されますが、その手数料が サードパーティのエコシステムへの資金源となっているのか、あるいはそれに紐づいているのかについては、ここでは明確になっていません。\n\nなぜこれが捜査にとって重要なのか\n1\nValveの「Steam」利用規約 商業的利用を禁止する Steamのインフラストラクチャを、明示的な許可なしに利用することはできません。以下のプラットフォームについては、公開記録においてそのような許可は確認されていません。\n2\nSteam 約1.28Bドルの第三者上場資産について、本人確認（OpenID）、在庫状況、および取引執行を管理している。 Valveのインフラがなければ、アイテムの転送は一切行われません。\n3\nSteam独自のマーケットプレイスには $31M 上場価格 — サードパーティによる上場価格の約1/41。1,800の上限価格により、これを上回る売り手は、実勢価格で売却するためにプラットフォーム外で取引を行う必要があります。\n4\n248 CS2のアイテムカテゴリ、各銘柄について、2つ以上のマーケットプレイスでそれぞれ上限価格を上回ると独立して評価されているものは、Steamではその市場価格での販売ができません――そして、それらの銘柄はいずれも同サイトには掲載されていません。1,800の上限価格設定が需要を生み出し、それをサードパーティの運営事業者が満たしているのです。\nSteam コミュニティ・マーケット：31百万ドル第三者による評価額：1,276百万ドル\n$1,276M · 第三者による評価額 — これらはすべて、Steamの取引 API および OpenID に依存しています\nSteam ・31百万ドル\n\n出典：PriceEmpireリアルタイムカタログ、20 9月 2026. 掲載価格＝保存されたスナップショット内の四捨五入された掲載価格カードの合計（Steamを除く）。販売数量ではない。\n\n38 活発なサードパーティ市場 · すべてはSteamのインフラに依存している\nプラットフォーム登録\n\n以下のプラットフォームは、ログイン処理をSteamのOpenID経由で、取引処理をSteamのWeb API経由で行っています。それぞれについて確認されたのは、 openid.realm Steamのログインフローを経由します。このレジスタは、特定のオペレーターがValveの権限を持っていないと断定するのではなく、観測された認証ルートを記録します。\n\n#\tプラットフォーム\t上場価格\t現在募集中の案件\t商品\tスケール\n1\tUUSkins\t$133.8M\t3.4M\t30.9K\t\n\n2\tYouPin898\t$127.5M\t5.9M\t29.2K\t\n\n3\tBuff.163\t$104M\t3.5M\t35K\t\n\n4\tMoon.Market\t$100.3M\t2.9M\t20.9K\t\n\n5\tWhite.Market\t$89.6M\t3M\t20.6K\t\n\n6\tBuff.Market\t$86.7M\t1.3M\t33.4K\t\n\n7\tEcosteam\t$82.1M\t3.3M\t30.1K\t\n\n8\tCSFloat\t$67.8M\t2.4M\t27.8K\t\n\n9\tSkin.Land\t$67.4M\t2.2M\t34.6K\t\n\n10\tLIS-SKINS\t$67.4M\t2.2M\t34.6K\t\n\n11\tC5Game\t$54.6M\t4.6M\t29.6K\t\n\n12\tHaloSkins\t$46.6M\t4.4M\t29.3K\t\n\n13\tAvan.Market\t$43.3M\t809.5K\t22.2K\t\n\n14\tWaxpeer\t$40.1M\t1M\t27.3K\t\n\n15\tSteam (official)\t$31M\t32.2M\t70.1K\t\n\n16\tCS.MONEY\t$29M\t748.9K\t28K\t\n\n17\tMarket.CSGO\t$26.3M\t1.3M\t27.6K\t\n\n18\tCS.MONEY Bot\t$25.7M\t614K\t23.8K\t\n\n19\tSkinport\t$16.3M\t3.8M\t31.1K\t\n\n20\tSkinFlow\t$14.1M\t481.8K\t23.6K\t\n\n21\tDMarket\t$12.6M\t948.2K\t35.6K\t\n\n22\tSkins.com\t$11.5M\t83.2K\t15.8K\t\n\n23\tSkin.place\t$6.9M\t380.8K\t11.4K\t\n\n24\tSkinsMonkey\t$6M\t109.4K\t11.6K\t\n\n25\tSkinBaron\t$5M\t2.1M\t21.5K\t\n\n26\tRustTM\t$3M\t33.1K\t4.9K\t\n\n27\tPirateSwap\t$2M\t859.3K\t10.5K\t\n\n28\tMannco.Store\t$1.2M\t223.7K\t11K\t\n\n29\tSkinSwap\t$1.1M\t11.4K\t4K\t\n\n30\tTradeIt\t$967.1K\t29.1K\t11.7K\t\n\n31\tLootFarm\t$896.1K\t162.5K\t28.6K\t\n\n32\tRustskins\t$714.8K\t312.5K\t6.1K\t\n\n33\tBalticSkins\t$599.2K\t28.2K\t4.5K\t\n\n34\tExeSkins\t$442.9K\t2.6K\t1.4K\t\n\n35\tRapidSkins\t$230.9K\t11.6K\t2.3K\t\n\n36\tCS.Trade\t$203K\t19K\t16.7K\t\n\n37\tKrakatoa\t$11.1K\t115\t53\t\n\n38\tShadowPay\t—\t—\t—\t—\n39\t49skins\t—\t—\t—\t—\nSteamの1,800価格上限 · 5つのマーケットプレイスの概要 · 23 9月 2026\n価格差は数値で把握できる。\n\nSteam capsコミュニティマーケットの掲載価格は約$1,800に設定されています（この算出結果は、$2,000, $、2,070, $、2,300、および$2,500で再計算されています）。 cs2sh-atlas.json （そして、すべての閾値でその水準を維持している）。その価格を上回って観測された項目は Valveの自社マーケットプレイスでは、市場価格での販売ができない — しかし、それらは 販売場所にかかわらず、依然としてSteamの在庫および転送システムに依存している。カタログ全体を 価格帯別に分類してみると、その限界がどこにあるかがわかる。Valveの市場では、 95.3% 上限価格を下回る価格設定がされている商品カテゴリのうち、 1.9% その上にあるものたちの。\n\n5つのマーケットプレイス：Steamの上限を超える商品\n248\n\n1,800で最安値の売値が成立した商品カテゴリ 2つ以上の マーケットプレイスを個別に、18,394に掲載された、少なくとも $78.6M. そのうち、 100.0% — すべて — に、 Steamの掲載が一切ありません。\n\n展示物の全容： レジスタ → · 価格ラダー・アトラス →\n\n上限を超える価格分布\n$1,800–$5,000\n174\n$5,000–$10,000\n49\n$10,000–$25,000\n21\n$25,000–$50,000\n2\n$50,000+\n2\n人気商品 — 5つのマーケットプレイスにおける、確認済みの最安値の売り出し価格\n1ステッカー | タイタン（ホロ） | カタログ番号「14」$66,285\n2ステッカー | iBUYPOWER (ホロ) | カタログ番号 '14'$64,795\n3ステッカー | Reason Gaming (Holo) | カタログ番号 '14'$42,899\n4★ スポーツグローブ | ヘッジ・メイズ (FN)$26,812\n5ステッカー | Team Dignitas (ホロ) | カタログ番号 '14'$23,667\n6EMS カテゴリー「14レジェンド」$22,879\n7★ スポーツグローブ | パンドラの箱 (FN)$21,643\n8EMS カテゴリー「14」の挑戦者たち$21,010\n9ステッカー | Vox Eminor (ホロ) | カタログ番号「14」$18,619\n10★ StatTrak™ ナバハ・ナイフ | ブルー・スチール (FN)$18,064\n\n売出価格は販売価格ではありません。cs2.shのライセンス取得済みスナップショット、23 9月 2026. 各行は、 少なくとも2つのマーケットプレイスによって、上限価格を上回る価格で独立して提示されているものです。単一の売り手による売出価格、および その商品の最安売出価格の3倍を超える価格は除外されています。 評価の 仕組み →\n\nValveの料金 · ライセンス取得済み cs2.sh スナップショット · 23 9月 2026\n掲載されている報酬額は15%.です。ほとんどの出稿元はこれより高い報酬を支払っています。\n\nValve 売り手の売上金から、5% Steam の手数料と、10% のCS2パブリッシャー手数料を差し引きます。これは おなじみの15%.です。どちらの手数料も 最低0.01, したがって、どの取引でも手数料が 2セントを下回ることはありません。市場の大部分を占める安価で取引量の多い商品については、 その下限額が拘束条件となり、パーセンテージではありません。私たちは、 すべての 29,635 Steamのリアルタイムオファーが付いている商品タイプ。\n\n77.7%\nSteamの掲載中の商品のうち、15%で表示される料金が適用される商品タイプは以下の通りです。\n84.8%\n商品の 種類 見出しに記載されている賃金に近い金額を支払ってください\n4,517\n広告に記載された料金よりも高い料金が請求された商品の種類\n$0.02\n販売価格にかかわらず、すべての販売に対して最低手数料が適用されます\nこの2つの数字は正反対の方向を指していますが、どちらも正しいのです\n1\n集計済み 品目別, Valve の料金は、おおむね広告通りです：29,635 に掲載されている価格タイプのうち、84.8% は、15%. と同額またはそれに近い金額で課金されます。\n2\n集計済み 実際の掲載情報による, すると、画像が反転します： 18,682,244 24,038,911より 15%. を超える料金が適用される商品カテゴリのリアルタイム一覧はこちら\n3\nどちらも正しい。なぜなら、過充電されたタイプは 安価で、大量生産 もの。1,109のアイテムタイプは、 ダブル 「注目物件」として掲載されており、これらのタイプだけでも14,083,486件のライブ物件情報が掲載されています。\n4\nこれは単なる計算上の話であり、主張ではありません。最低額は、Valve自身の料金に関する資料に開示されています。公表されていないのは、 実際にどの程度の市場に適用されるのか — これが、上記の数値が表しているものです。\n請求手数料が、15%の表題額の何％を占めるか\n200%+\n14,083,486\n100-200%\n1,028,438\n50-100%\n700,804\n30-50%\n317,031\n20-30%\n2,258,254\n17.6-20%\n294,231\n\n「バーの長さ」とは、各バンドに含まれる有効な出品件数を指します。「200%+」というバンドは、徴収される手数料が、売り手の売上高の15%の2倍以上であることを意味します。\n\n解き方の例\n67%\n\n物件の掲載において、買い手は以下を支払います $0.03 というのも、売り手は受け取るからである $0.01 そして、Valveは $0.02 — 2つの1セントの最低額。買い手が支払った金額に占める割合は67%であり、売り手の売却益に占める割合は200%.である。\n\nデータセット全体： cs2sh-steam-fee-census.json →\n\n同じ品物、庭の中と外\nSteamでの購入は、ほとんどの場合、より高くつきます。\n\nSteam と、少なくとも 1 つのサードパーティのマーケットプレイスの両方に掲載されているすべての商品について、 Steam の最安値と、同サイト以外の最安値を比較しました。全体を通じて 28,700 商品に関しては、Steamの方が価格が高いです 86.4% 多くの場合、中央値で +35.7%.\n\n価格帯別のSteam保険料の中央値\n0.50未満\n+48.3%\n$0.50-2\n+36.5%\n$2-10\n+29.6%\n$10-50\n+28.6%\n$50-250\n+36.3%\n$250-1k\n+51.1%\n1,000ドル以上\n+67.9%\n\nその曲線はU字型です。Steamで買うのが最も安く、その $10–$50 両端にはバンドと最愛の人がいます。\n\nなぜ高価格帯が重要なのか\n+67.9%\n\n上 $1,000, 「Steam」に掲載されている物件の価格の中央値は、 67.9% それ以外の地域で最も安い物件の価格よりも高く、しかも 1,040 Steam には、そのような物件がわずかしか掲載されていない。\n\nおよそ1,800ドルを超えると、比較ができなくなります。なぜなら、 Valveの規定により、その価格帯の商品の掲載が一切禁止されているからです。Steamでは、自社の価格上限を超える商品については、 1.9%. ランキング一覧を見る →\n\nデータセット全体： cs2sh-walled-garden-premium.json →\n\nプレミアムはそれ自体では結論にはなりません。Steamは即時決済を提供し、カウンターパーティ・リスクもありません。 したがって、買い手がそれに対して対価を支払うことは理にかなっています。測定可能なのは、その格差の大きさという事実と、 その格差を埋めるために支払われた資金が元に戻ってこないという事実です。これについては次のセクションで説明します。\n\nお金が入ってきても、出ていかない\n128.1百万ドルが、取り消し不能な注文に割り当てられた。\n\nSteamの買い注文は事前入金制となっており、注文が 発注された瞬間に、購入者のウォレットから資金が引き落とされます。Steam ウォレットの資金 取り消すことはできません — これらは Steam内でのみ使用可能です。追跡対象となっているすべてのアイテムの買い注文簿の各価格帯を合計すると、確定済みで、 引き出し不可能な資金の総額が算出されます。\n\n$128.1M\nSteamの買い注文を保持することに注力しています\n170.6M\n未約定の個人資金による買い注文\n$105.8M\n目の前にある物件の適正価格\n$15.9M\nValveの取り分（すべての物件が希望価格で売却された場合）\nこの図が何を表しているのか、そして何を表していないのか\n1\nそれは すでに支払済みの実資金. 集計された1ドルごとに、ウォレットから引き落とされ、31,253の各アイテムタイプにわたる未決済注文の残高として計上されています。\n2\nそれは 収益ではない これは、Valveの貸借対照表に関する主張ではない。浮動株がどこに保有されており、どの企業の帳簿に記載されているのかについては、ここでは明らかにされていない。\n3\nそれは スナップショットであり、フローではない. 注文は購入者によってキャンセル可能であり、その場合、資金はウォレットに戻されますが、それでもSteamからは引き出されません。\n4\n重要なのは、その「一方通行の扉」です。通貨を現金化できないマーケットプレイスであるからこそ、盗まれた在庫が換金されてしまうのです。 オフ Steam その上ではなく。\n\n方法：追跡対象のすべての買い注文簿について、各価格水準に、その 水準にある注文数を乗じたもの。データセット全体： cs2sh-steam-locked-capital.json →\n\n成約価格（希望価格ではない） · 1つのマーケットプレイス · 過去90日間の推移\n実際に取引されたのは30.9百万ドル――5つの棚のうち、最も小さい棚でのことだった。\n\n高額で成約した1件の取引には、希少な工芸品や、安価な基本アイテムにステッカーが貼られたバリエーション品が含まれることがあります（例：e.g。通常価格30のアイテムが、1回限りの9,772で成約したケース）。ここでいう「高額」とは、そのアイテムの通常価格ではなく、成約した取引の中で最も高い金額を指します。\n\nこのページにある他のすべての図は、次のものを測定しています。 掲載済み. これは、かつて何であったかを測定するもので、 販売済み. Skinport は、自社で完了した取引を公表しており、直近の 90 日間において その取引総額は 1,219,143 売上 価値 $30,927,032、1個あたり平均25.37です。\n\n1.22M\n90日間で成約した売上、1つのマーケットプレイス\n$30.9M\n同期間における売上高\n$125M\n年換算ペース — 推定値ではなく、下限値\n~2%\nSkinportが、時価総額ベースで占めるキャップ上限を超えるシェルフの割合\n売上高の源泉\n1未満\n0.5%\n$1-10\n5.8%\n$10-100\n22.2%\n$100-1k\n59.4%\n$1k-1.8k\n6.9%\nSteamのキャップより上\n5.3%\n\n棒の長さは売上高を表しており、その数値は総売上高に占める当該階層の割合を示しています。 59.4% 71,437での売上において、 $100–$1kティアで移動した資金のうち、\n\nValveのキャップの上でも、販売は行われている\n492\n\nSteamの上限を超える価格の商品の販売総額は、 $1,643,938、 76の各商品カテゴリーにわたり――その棚の約2%を占めるマーケットプレイス上で。 これらの売上は、Steamでは一切成立しなかっただろう。\n\nデータセット全体： cs2sh-offsteam-90d-dynamics.json → · 過去最高値 →\n\nSkinport は、ここで追跡対象となっているサードパーティ市場の「1つ」であり、Steamの上限を超える上場価値を持つことから、5つの市場の中で最も規模が小さい（その棚の約2%に相当）。ここでの合計値はすべて、Steamのオフ経済における下限値であり、その規模を示す指標ではない。Steamのデータは一切使用されていない。",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "市場経済 — 2つの経済と上場上限"
          },
          {
            "level": 2,
            "id": null,
            "text": "1つのインフラ。2つの経済。"
          },
          {
            "level": 2,
            "id": null,
            "text": "プラットフォーム登録"
          },
          {
            "level": 2,
            "id": null,
            "text": "価格差は数値で把握できる。"
          },
          {
            "level": 3,
            "id": null,
            "text": "5つのマーケットプレイス：Steamの上限を超える商品"
          },
          {
            "level": 3,
            "id": null,
            "text": "上限を超える価格分布"
          },
          {
            "level": 3,
            "id": null,
            "text": "人気商品 — 5つのマーケットプレイスにおける、確認済みの最安値の売り出し価格"
          },
          {
            "level": 2,
            "id": null,
            "text": "掲載されている報酬額は15%.です。ほとんどの出稿元はこれより高い報酬を支払っています。"
          },
          {
            "level": 3,
            "id": null,
            "text": "請求手数料が、15%の表題額の何％を占めるか"
          },
          {
            "level": 3,
            "id": null,
            "text": "解き方の例"
          },
          {
            "level": 2,
            "id": null,
            "text": "Steamでの購入は、ほとんどの場合、より高くつきます。"
          },
          {
            "level": 3,
            "id": null,
            "text": "価格帯別のSteam保険料の中央値"
          },
          {
            "level": 3,
            "id": null,
            "text": "なぜ高価格帯が重要なのか"
          },
          {
            "level": 2,
            "id": null,
            "text": "128.1百万ドルが、取り消し不能な注文に割り当てられた。"
          },
          {
            "level": 2,
            "id": null,
            "text": "実際に取引されたのは30.9百万ドル――5つの棚のうち、最も小さい棚でのことだった。"
          },
          {
            "level": 3,
            "id": null,
            "text": "売上高の源泉"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valveのキャップの上でも、販売は行われている"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/ja/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/ja/elite_skins.html",
          "https://phishdestroy.io/steam_dossier/ja/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/ja/skin_atlas.html#grading",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-steam-fee-census.json",
          "https://phishdestroy.io/steam_dossier/ja/skin_atlas.html#cliff",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-walled-garden-premium.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-steam-locked-capital.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-offsteam-90d-dynamics.json",
          "https://phishdestroy.io/steam_dossier/ja/skin_atlas.html#highs"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ja/market_economics.content.json",
      "export_json_sha256": "dbbc21361f59db228cf4a641ee7fe1ca5a20dc4ba327d6707e39c8e62f81c811"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ja/regulatory_act_print.html",
      "language": "ja",
      "title": "「フォレンジック監査法」：Valve Steam Web API エコシステムと商業的活用（参照：VAL-REG-2026-09）",
      "source_url": "https://phishdestroy.io/steam_dossier/ja/regulatory_act_print",
      "source_html_sha256": "c3019a730819e014aef5f34f248770ef5b873a6ba3a3fed1f77d3833c26b39e2",
      "exported_at": "2026-09-29T00:22:15.749Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "regulatory_act_print.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ja/regulatory_act_print.pdf?v=print-20260929-v5",
        "sha256": "34a741aa8fc37f7deaf3c7258b1560d237e3c338152dc6f8d733efca6e39592a",
        "bytes": 475756,
        "pages": 13
      },
      "integrity": {
        "signed_object": "regulatory_act_print.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "regulatory_act_print.content.json.asc",
        "digest_file": "regulatory_act_print.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify regulatory_act_print.content.json.asc regulatory_act_print.content.json",
          "sha256sum -c regulatory_act_print.content.json.sha256"
        ]
      },
      "content": {
        "text": "phishdestroy.io ・法医学研究連合・ユニバーサル・パブリック・レコード\n事件番号： VAL-REG-2026-09-EVID\n来歴： phishdestroy.io/steam_dossier/\n権利： すべての権利は人類に委ねられた\n法務監査法および規制関連資料\nValveのSteamエコシステムにおける、体系的なサードパーティによるAPIのプロビジョニング、自動化されたバイパスアーキテクチャ、および契約上の不履行\n発行ドメインphishdestroy.io\n対象プラットフォームValve Steam / Steamworks\n一次認証ベクトルSteam OpenID 2.0 / Web API\n法的献辞All Rights to Humanity (CC0)\n第I部：執行部覚書および事実認定参照：MEMO-SUMMARY-01\n\n本書は、Valve社の公表されている商用規約、同社の技術的な認証エンドポイント、および確認されたサードパーティの商用プラットフォーム間の運用上の関連性を検証する、正式なフォレンジック監査報告書である。本監査は、受動的かつ認証不要なネットワーク監視、RDAPの登録確認、および公開されているLink Filterのテレメトリデータを用いて実施された。\n\n事実の核心： 実証的な観察により、Valveの公的な契約上の表明と、その生産インフラとの間に体系的な乖離があることが明らかになっている。 Steamの加入者契約（SSA）では、無許可の商業的利用（§ 2.G）、自動化されたボット／スクリプトによる操作（§ 4.C）、およびアカウントの譲渡（§ 1.C）が厳格に禁止されているにもかかわらず、Valve Corporationは、数十億ドル規模の二次取引量を発生させている少なくとも175の商業事業体に対し、リアルタイムかつプログラム化されたOpenID認証および在庫照会インフラの提供を継続している。\n\n175\n監査を受けた商業事業者\n44\n別ドメインの認証ホスト\n26\nフィルタ分割プロキシペア\n100%\n施行されていない社会保障法（SSA）第2.G条／第4.C条\n0\n強制的な認証情報の失効\n適用される契約上および法的な枠組み\nSSA 第2.G条\n商用利用の禁止： Valve Corporationからの事前の書面による許可なく、コンテンツおよびサービスを商業目的で利用することを固く禁じます。\nSSA 第4.C条\n自動化の制限： Steamのサービスおよび市場とやり取りを行うスクリプト、トレーディングボット、マクロ、または人間による操作ではないシステムの使用を固く禁じます。\nSSA 第1.C条\n個人利用に関する規定： アカウントは個人利用に限定されます。Steamのユーザーアカウントの販売、貸与、譲渡、または取引は固く禁じられています。\nEUのDSA（2022/2065）\nシステミック・リスク評価（34/35条）： 超大規模オンラインプラットフォーム（VLOP）は、自動化された不正利用や無断の商業的搾取に起因するシステミックリスクを、積極的に検知、評価し、軽減しなければならない。\n第II節：別紙台帳A — リンクフィルタ分割ペアの記録（26ルート）参照番号：EX-SPLIT-LEDGER\n\nスプリットドメイン回避手法のフォレンジック分析： Valveの「Steam」リンクフィルタシステムでは（steamcommunity.com/linkfilter/?url=...)、エンドユーザーが、警告対象のギャンブルサイトや闇市場プラットフォームへのリンクをクリックすると、Valve は目立つ警告を表示します（「リンクがブロックされました！… 悪意のある可能性があると報告されました」）。しかし、フォレンジックによる経路追跡の結果、26の商用プラットフォームが 分割ドメインアーキテクチャ: リンクフィルターでは、主要な商用ドメインが「BLOCKED」と判定されている一方で、ValveのOpenIDリターンエンドポイントをホストしているセカンダリドメインは「CLEAN」と判定されています。ValveのOpenIDサーバーは、これらのプロキシホストからの認証リクエストを中断することなく受け入れており、これにより、消費者に表示される安全警告を無効化しつつ、ログイン処理を継続しています。\n\n#\t主要な商用ドメイン\tメインフィルター\tOpenID 認証プロキシドメイン\t認証フィルター\tRDAP 登録済み\t取得基準\n01\trollbit.com\tBLOCKED\trbsnin.com\tCLEAN\t2026-09-18\tPASSIVE_CAPTURE\n02\tskin.club\tBLOCKED\tsc-auth.net\tCLEAN\t2019-04-02\tPASSIVE_CAPTURE\n03\thowl.gg\tBLOCKED\thowl.uno\tCLEAN\t2026-08-11\tPASSIVE_CAPTURE\n04\tduelbits.com\tBLOCKED\tswitchflips.com\tCLEAN\t2020-04-21\tPASSIVE_CAPTURE\n05\tcsgofast.com\tBLOCKED\tsteam-login.authtofast.com\tCLEAN\t2026-06-30\tPASSIVE_CAPTURE\n06\tfarmskins.com\tBLOCKED\tsteam.kobal.cc\tCLEAN\t2017-01-07\tPASSIVE_CAPTURE\n07\tcobaltlab.tech\tBLOCKED\tcobaltauth.com\tCLEAN\t2025-01-07\tPASSIVE_CAPTURE\n08\tcsgo.net\tBLOCKED\tcn2.easylot.net\tCLEAN\t2016-09-03\tPASSIVE_CAPTURE\n09\tggdrop.com\tBLOCKED\tggauth.com\tCLEAN\t2023-05-03\tPASSIVE_CAPTURE\n10\trustchance.com\tBLOCKED\thgfuihd.com\tCLEAN\t2019-01-27\tPASSIVE_CAPTURE\n11\tskin.fans\tBLOCKED\tauth.skinfans.com\tCLEAN\t2018-07-16\tPASSIVE_CAPTURE\n12\tskinport.com\tBLOCKED\tskinport.app\tCLEAN\t2020-06-20\tPASSIVE_CAPTURE\n13\tskins.cash\tBLOCKED\tskinscash.live\tCLEAN\t2019-12-05\tPASSIVE_CAPTURE\n14\ttf2hunt.com\tBLOCKED\trstspcl.com\tCLEAN\t2020-08-08\tPASSIVE_CAPTURE\n15\tdaddyskins.com\tBLOCKED\tgo-go-daddy.com\tCLEAN\t2019-01-26\tPASSIVE_CAPTURE\n16\tkey-drop.com\tBLOCKED\tkdauth.com\tCLEAN\t2026-05-13\tPASSIVE_CAPTURE\n17\tclash.gg\tBLOCKED\tclggauth.com\tCLEAN\t2024-09-16\tPASSIVE_CAPTURE\n18\tc5game.com\tBLOCKED\twww.imbastar.com\tCLEAN\t2016-02-27\tPASSIVE_CAPTURE\n19\tswap.gg\tBLOCKED\tswapauth.com\tCLEAN\t2018-10-06\tPASSIVE_CAPTURE\n20\tshadowpay.com\tBLOCKED\tthelogins.com\tCLEAN\t2018-01-22\tPASSIVE_CAPTURE\n21\tcsgocases.com\tBLOCKED\tlog-1n.com\tCLEAN\t2017-11-27\tPASSIVE_CAPTURE\n22\tcsgogem.com\tBLOCKED\tapi.csgem.com\tCLEAN\t2014-03-08\tPASSIVE_CAPTURE\n23\tgamdom.com\tBLOCKED\tlogin.gambldom.com\tCLEAN\t2017-09-24\tPASSIVE_CAPTURE\n24\t12cs.fail\tBLOCKED\tfail.games\tCLEAN\t2021-08-24\tPASSIVE_CAPTURE\n25\tskinsnipe.com\tBLOCKED\tpricing.tradeupspy.com\tCLEAN\t2020-03-11\tPASSIVE_CAPTURE\n26\tcsgobig.com\tBLOCKED\tletmeinbig.com\tCLEAN\t2023-01-20\tPASSIVE_CAPTURE\n\n* 注：2026-09-19 および 2026-09-21. 上の、認証されていない Steam リンクフィルターエンドポイントに対して実行されたパッシブチェック。生の HTTP レスポンス本文および SHA-256 ダイジェストは、リポジトリデータセット（steam_tos_assets/linkfilter-2026-09-22.json）に保存されています。\n\n第III節：別紙台帳B — 「175」の監査対象商業事業体に関する包括的調査参照番号：EX-175-MASTER-CENSUS\n\n以下の登録簿には、監査データベースにおいて積極的に検証されたすべての「175」のサードパーティ商用プラットフォームの詳細が記載されています。各レコードには、事業体名、主要な商用ドメイン、確認された Steam の OpenID 認証ルート、活動分類、契約違反のマッピング（SSA § 2.G、SSA § 4.C、SSA § 1.C）、およびソースデータセットに記録された「措置」フィールドが示されています。 「日付入りの証拠を参照」というラベルは、読者に裏付けとなる記録を参照するよう促すものであり、Valveが措置を講じなかったことを立証するものではない。措置フィールドが存在しない場合は、「立証されていない」として報告される。\n\n展示物\t組織名およびメインドメイン\t観測された認証ルート／プロキシ\t分類\t契約違反\tValve アクション\nEX-001\tCSGORoll\ncsgoroll.com\n\t\nwww.csgoroll.com\nDIRECT\n\tSkin Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-002\tCSGOEmpire\ncsgoempire.com\n\t\ncsgoempirelogin4.com\nSPLIT PROXY\n\tCasino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-003\tRollbit\nrollbit.com\n\t\nrbsnin.com\nSPLIT PROXY\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-004\t500 Casino\n500.casino\n\t\nfivezerozero.co\nSPLIT PROXY\n\tLicenced Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-005\tCSGOBig\ncsgobig.com\n\t\ncsgobig.com\nDIRECT\n\tRoulette/Slots\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-006\tCaseDrop\ncasedrop.com\n\t\ncasedrop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-007\tRustReaper\nrustreaper.com\n\t\nrustreaper.com\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-008\tBanditCamp\nbanditcamp.com\n\t\nbanditcamp.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-009\tSkinBox\nskinbox.com\n\t\nskinbox.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-010\tTastyDrop\ntastydrop.com\n\t\ntastydrop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-011\tCSGOPolygon\ncsgopolygon.gg\n\t\ncsgopolygon.gg\nDIRECT\n\tRoulette Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-012\tMagicDrop\nmagicdrop.ru\n\t\nmagicdrop.ru\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-013\tCSDice\ncsdice.com\n\t\ncsdice.com\nDIRECT\n\tDice Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-014\tRustly\nrustly.com\n\t\nrustly.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-015\tSkinOdds\nskinodds.com\n\t\nskinodds.com\nDIRECT\n\tUpgrader Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-016\tCSGOWin\ncsgowin.com\n\t\ncsgowin.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-017\tCSGORun\ncsgorun.net\n\t\ncsgorun.net\nDIRECT\n\tCrash Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-018\tOpenSkins\nopenskins.com\n\t\nopenskins.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-019\tRustBet\nrustbet.com\n\t\nrustbet.com\nDIRECT\n\tRust Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-020\tCSGOMagic\ncsgomagic.com\n\t\ncsgomagic.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-021\tCSGOBounty\ncsgobounty.com\n\t\ncsgobounty.com\nDIRECT\n\tUpgrader/Contract\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-022\tEZSkins\nezskins.com\n\t\nezskins.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-023\tRustCases\nrustcases.com\n\t\nrustcases.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-024\tCSGOReaper\ncsgoreaper.com\n\t\ncsgoreaper.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-025\tCSGOCases\ncsgocases.com\n\t\ncsgocases.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-026\tCSGO-Skins\ncsgo-skins.com\n\t\ncsgo-skins.com\nDIRECT\n\tCase Upgrader\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-027\tCSGONet\ncsgonet.com\n\t\ncsgonet.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-028\tWTFSkins\nwtfskins.com\n\t\nwtfskins.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-029\tCSGOFast\ncsgofast.com\n\t\nsteam-login.authtofast.com\nSPLIT PROXY\n\tRoulette Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-030\tDuelbits\nduelbits.com\n\t\nswitchflips.com\nSPLIT PROXY\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-031\tFlameCases\nflamecases.com\n\t\nflamecases.com\nDIRECT\n\tCase Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-032\tFarmskins\nfarmskins.com\n\t\nsteam.kobal.cc\nSPLIT PROXY\n\tCase Opener\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-033\tCSGOLuck\ncsgoluck.com\n\t\ncsgoluck.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-034\tGamedom\ngamedom.com\n\t\ngamedom.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-035\tSkin.Club\nskin.club\n\t\nsc-auth.net\nSPLIT PROXY\n\tCase Battles\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-036\tDaddySkins\ndaddyskins.com\n\t\ndaddyskins.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-037\tInsane.gg\ninsane.gg\n\t\napi.insane.gg\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-038\tRustix\nrustix.gg\n\t\nrustix.gg\nDIRECT\n\tRust Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-039\tSkins.Club\nskins.club\n\t\nskins.club\nDIRECT\n\tSkin Upgrade\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-040\tCSGOHouse\ncsgohouse.org\n\t\ncsgohouse.org\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-041\tSkinRave\nskinrave.net\n\t\nskinrave.net\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-042\tBloodyCase_GG\nbloodycase.gg\n\t\nbloodycase.gg\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-043\tCSGOClicker\ncsgoclicker.com\n\t\ncsgoclicker.com\nDIRECT\n\tClicker/Upgrade\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-044\tRustBet_GG\nrustbet.gg\n\t\nrustbet.gg\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-045\tCS_Drop\ncs-drop.com\n\t\ncs-drop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-046\tHellStore\nhellstore.net\n\t\nhellstore.net\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-047\tRustLoot\nrustloot.com\n\t\nrustloot.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-048\tCSGO_Case\ncsgo-case.com\n\t\ncsgo-case.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-049\tCS2Skin\ncs2skin.com\n\t\ncs2skin.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-050\tJuice_GG\njuice.gg\n\t\nletmeinjuice.com\nSPLIT PROXY\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-051\tGGDrop\nggdrop.com\n\t\nggauth.com\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-052\tCSGOGem\ncsgogem.com\n\t\ncsgogem.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-053\tRainbet\nrainbet.com\n\t\nservices.rainbet.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-054\tHowl_GG\nhowl.gg\n\t\nhowl.uno\nSPLIT PROXY\n\tSkins Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-055\tChicken_GG\nchicken.gg\n\t\nchicken.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-056\tCSGOCasino_GG\ncsgocasino.gg\n\t\napi.csgocasino.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-057\tHunt_GG\nhunt.gg\n\t\napi.hunt.gg\nDIRECT\n\tSkins Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-058\tCSBattle\ncsbattle.com\n\t\ncsbattle.com\nDIRECT\n\tCase Battles\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-059\tSkinRave_GG\nskinrave.gg\n\t\napi.skinrave.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-060\tCSDouble\ncsdouble.gg\n\t\ncsdouble.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-061\tRustChance\nrustchance.com\n\t\nhgfuihd.com\nSPLIT PROXY\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-062\tRustClash\nrustclash.com\n\t\nrustclash.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-063\tCobaltLab\ncobaltlab.tech\n\t\ncobaltauth.com\nSPLIT PROXY\n\tRust Automation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-064\tRaided_GG\nraided.gg\n\t\napi.raided.gg\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-065\tRustNeo\nrustneo.gg\n\t\nrustneo.gg\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-066\tSplits_GG\nsplits.gg\n\t\nsplits.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-067\tUpgrader_Pro\nupgrader.pro\n\t\nupgauth.space\nSPLIT PROXY\n\tSkin Upgrader\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-068\tSkinFans\nskin.fans\n\t\nauth.skinfans.com\nSPLIT PROXY\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-069\tHotPizza\nhotpizza.one\n\t\nhotpizza.one\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-070\tG4Skins\ng4skins.com\n\t\nauth.g4s.to\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-071\t12CS_Fail\n12cs.fail\n\t\n12cs.fail\nDIRECT\n\tCrash Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-072\tTF2Royal\ntf2royal.com\n\t\ntf2auth.com\nSPLIT PROXY\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-073\tTF2Easy\nwww.tf2easy.com\n\t\nwww.tf2easy.com\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-074\tTF2Hunt\ntf2hunt.com\n\t\nrstspcl.com\nSPLIT PROXY\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-075\tTF2Bet\ntf2.bet/coinflip\n\t\ntf2.bet\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-076\tTF2Blaze\ntf2blaze.com\n\t\ntf2blaze.com\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-077\tOpenStars_GG\nopenstars.gg\n\t\nopenstars.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-078\tShuffle_Com\nshuffle.com\n\t\nshuffle.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-079\tSkins.com\nskins.com\n\t\napi.skins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-080\tWhite.Market\nwhite.market\n\t\nwhite.market\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-081\tBuff.Market\nbuff.market\n\t\nbuff.market\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-082\tAvan.Market\navan.market\n\t\navan.market\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-083\tCS.MONEY\ncs.money\n\t\nauth.dota.trade\nSPLIT PROXY\n\tTrading Engine\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-084\tUUSkins\nuuskins.com\n\t\nuuskins.com\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-085\tYouPin898\nyoupin898.com\n\t\nyoupin898.com\nDIRECT\n\tMass Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-086\tMoon.Market\nmoon.market\n\t\nmoon.market\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-087\tCSFloat\ncsfloat.com\n\t\ncsgofloat.com\nSPLIT PROXY\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-088\tSkin.Land\nskin.land\n\t\nauth.skin.land\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-089\tC5Game\nc5game.com\n\t\nc5game.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-090\tHaloSkins\nhaloskins.com\n\t\nhaloskins.com\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-091\tBuff.163\nbuff.163.com\n\t\nbuff.163.com\nDIRECT\n\tCorporate Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-092\tWaxpeer\nwaxpeer.com\n\t\nwaxpeer.com\nDIRECT\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-093\tCS.MONEY Bot\ncs.money\n\t\nauth.dota.trade\nSPLIT PROXY\n\tBot Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-094\tMarket.CSGO\nmarket.csgo.com\n\t\ndota2.net\nSPLIT PROXY\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-095\tSkinport\nskinport.com\n\t\nskinport.app\nSPLIT PROXY\n\tRegulated Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-096\tSkinFlow\nskinflow.gg\n\t\napi.skinflow.gg\nDIRECT\n\tMarketplace/Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-097\tDMarket\ndmarket.com\n\t\ndmarket.com\nDIRECT\n\tUS Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-098\tSkin.place\nskin.place\n\t\napi.skin.place\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-099\tSkinsMonkey\nskinsmonkey.com\n\t\nskinsmonkey.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-100\tSkinBaron\nskinbaron.de\n\t\nskinbaron.com\nSPLIT PROXY\n\tCorporate Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-101\tSteam\nsteamcommunity.com/market\n\t\nsteamcommunity.com/market\nDIRECT\n\tOfficial Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-102\tRustTM\nrust.tm\n\t\ndota2.net\nSPLIT PROXY\n\tRust Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-103\tPirateSwap\npirateswap.com\n\t\nlogin.pirateswap.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-104\tMannco.Store\nmannco.store\n\t\nmannco.store\nDIRECT\n\tTF2 Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-105\tSkinSwap\nskinswap.com\n\t\napi.skinswap.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-106\tLootFarm\nlootfarm.com\n\t\nlootfarm.com\nDIRECT\n\tTrading Platform\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-107\tRustskins\nrustskins.com\n\t\nrustskins.com\nDIRECT\n\tRust Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-108\tExeSkins\nexeskins.com\n\t\nexeskins.com\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-109\tBalticSkins\nbalticskins.com\n\t\nbalticskins.com\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-110\tCS.Trade\ncs.trade\n\t\ncs.trade\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-111\tRapidSkins\nrapidskins.com\n\t\napi.rapidskins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-112\tTradeIt\ntradeit.gg\n\t\nconnect-tradeit.com\nSPLIT PROXY\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-113\tKrakatoa\nkrakatoa.com\n\t\nkrakatoa.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-114\tShadowPay\nshadowpay.com\n\t\nshadowpay.com\nDIRECT\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-115\t49skins\n49skins.com\n\t\napi.49skins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-116\tSkinVault\nskinvault.gg\n\t\napi.skinvault.gg\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-117\tAim Market\naim.market\n\t\naim.market\nDIRECT\n\tSkins Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-118\tSkinout\nskinout.gg\n\t\nauth.skinout.gg\nDIRECT\n\tInstant Sell Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-119\tNTSkins\nntskins.com\n\t\nntskins.com\nDIRECT\n\tSkins Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-120\tIGXE\nigxe.cn\n\t\nigxe.cn\nDIRECT\n\tChinese Powerhouse\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-121\tSwap.gg\nswap.gg\n\t\nswap.gg\nDIRECT\n\tAutomated Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-122\tBitskins\nbitskins.com\n\t\nbitskins.com\nDIRECT\n\tCash-out Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-123\tGamerPay\ngamerpay.gg\n\t\ngamerpay.gg\nDIRECT\n\tP2P Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-124\tTF2Mart\ntf2mart.com\n\t\ntf2mart.com\nDIRECT\n\tTF2 Automation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-125\tSkinBid\nskinbid.com\n\t\nskinbid.com\nDIRECT\n\tSkin Auctions\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-126\tLootBear\nlootbear.com\n\t\nlootbear.com\nDIRECT\n\tSkin Rental\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-127\tBackpack.tf\nbackpack.tf\n\t\nbackpack.tf\nDIRECT\n\tTF2 Valuation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-128\tScrap.tf\nscrap.tf\n\t\nscrap.tf\nDIRECT\n\tTF2 Scrap Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-129\tMarketplace.tf\nmarketplace.tf\n\t\nmarketplace.tf\nDIRECT\n\tTF2 Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-130\tSTNTrading\nstntrading.eu\n\t\nstntrading.eu\nDIRECT\n\tTF2 Botnet\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-131\tSkins.Cash\nskins.cash\n\t\nskinscash.live\nSPLIT PROXY\n\tInstant Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-132\tSkinWallet\nskinwallet.com\n\t\nskinwallet.com\nDIRECT\n\tInstant Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-133\tDota2Market\ndota2market.com\n\t\ndota2market.com\nDIRECT\n\tDota 2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-134\tCSGO.NET\ncsgo.net\n\t\ncn2.easylot.net\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-135\tCybershoke\ncybershoke.net\n\t\nauth.cybershoke.net\nDIRECT\n\tCommunity Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-136\tXPlay_GG\nxplay.gg\n\t\nxplay.gg\nDIRECT\n\tServer Network\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-137\tFastCup\nfastcup.net\n\t\napi.fastcup.net\nDIRECT\n\tMatchmaker Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-138\tEsportal\nesportal.com\n\t\nesportal.com\nDIRECT\n\tMatchmaking Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-139\tGamersClub\ngamersclub.com.br\n\t\ngamersclub.com.br\nDIRECT\n\tLATAM Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-140\tLeetify\nleetify.com\n\t\nleetify.com\nDIRECT\n\tSaaS Analytics\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-141\tScope_GG\nscope.gg\n\t\nscope.gg\nDIRECT\n\tSaaS Analytics\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-142\tTradeUpSpy\ntradeupspy.com\n\t\napi.tradeupspy.com\nDIRECT\n\tSaaS Tools\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-143\tEpidemic_GG\nepidemic.gg\n\t\nepidemic.gg\nDIRECT\n\tSaaS Tools\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-144\tCSDeals\ncs.deals\n\t\napi.cs.deals\nDIRECT\n\tMarketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-145\tPricempire\npricempire.com\n\t\npricempire.com\nDIRECT\n\tSaaS Price DB\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-146\tCS2Stash\ncs2stash.com\n\t\ncs2stash.com\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-147\tCSGOSkins\ncsgoskins.gg\n\t\ncsgoskins.gg\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-148\tSteamAnalyst\nsteamanalyst.com\n\t\nsteamanalyst.com\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-149\tSteamCardExchange\nsteamcardexchange.net\n\t\nsteamcardexchange.net\nDIRECT\n\tTrading Exchange\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-150\tDotaBuff\ndotabuff.com\n\t\ndotabuff.com\nDIRECT\n\tSaaS Tracker\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-151\tTracker_GG\ntracker.gg\n\t\ntracker.gg\nDIRECT\n\tSaaS Tracker\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-152\tFSB Market (an anonymized label; the original name is withheld here)\nFSB Market\n\t\nFSB Market\nDIRECT\n\tMass Blackmarket\tSSA § 2.G, SSA § 4.C, SSA § 1.C\tSee dated evidence\nEX-153\tFunPay\nfunpay.com\n\t\nfunpay.com\nDIRECT\n\tAccount Exchange\tSSA § 2.G, SSA § 4.C, SSA § 1.C\tSee dated evidence\nEX-154\tPlayerAuctions\nplayerauctions.com\n\t\nplayerauctions.com\nDIRECT\n\tGrey Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-155\tEldorado.gg\neldorado.gg\n\t\neldorado.gg\nDIRECT\n\tAccount Portal\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-156\tG2A\ng2a.com\n\t\ng2a.com\nDIRECT\n\tMass Key Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-157\tKinguin\nkinguin.net\n\t\nkinguin.net\nDIRECT\n\tMass Key Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-158\tG2G.com\ng2g.com\n\t\ng2g.com\nDIRECT\n\tVirtual Services\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-159\tPlayerup\nplayerup.com\n\t\nplayerup.com\nDIRECT\n\tAccount Broker\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-160\tZ2U.com\nz2u.com\n\t\nwww.z2u.com\nDIRECT\n\tReady-Account Hub\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-161\tSmurfHub\nsmurfhub.net\n\t\nsmurfhub.net\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-162\tSmurfAccounts\nsmurfaccounts.com\n\t\nsmurfaccounts.com\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-163\tBuyCSGORank\nbuycsgorank.com\n\t\nbuycsgorank.com\nDIRECT\n\tRank Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-164\tCSGOSmurfKings\ncsgosmurfkings.com\n\t\ncsgosmurfkings.com\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-165\tSmurfStore_Co\nsmurfstore.co\n\t\nsmurfstore.co\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-166\tSteamLvlUp\nsteamlvlup.com\n\t\nsteamlvlup.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-167\tSteamLevels\nsteamlevels.com\n\t\nsteamlevels.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-168\tLevelSteam\nlevelsteam.com\n\t\nlevelsteam.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-169\tSteamLevelU\nsteamlevelu.com\n\t\nsteamlevelu.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-170\tEloKing\neloking.com\n\t\neloking.com\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-171\tBoosteria\nboosteria.org\n\t\nboosteria.org\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-172\tOvergear\novergear.com\n\t\novergear.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-173\tBlazingBoost\nblazingboost.com\n\t\nblazingboost.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-174\tDota2Boost\ndota2boost.com\n\t\ndota2boost.com\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-175\tBuyBoost\nbuyboost.com\n\t\nbuyboost.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\n第IV章：技術アーキテクチャと認証の仕組み参照：TECH-ANALYSIS-01\n\n1. OpenIDにおけるドメイン所有権の検証機能の欠如 2.0: ValveによるOpenID 2.0 プロトコルの実装（https://steamcommunity.com/openid/login) は、 openid.return_to そして openid.realm 開発者の事前の登録、暗号によるチャレンジ検証、ドメイン所有権の確認を必要とせずにパラメータを指定できます。あらゆる商用事業者は、ユーザーをValveのログイン画面に誘導し、任意のドメインにリダイレクトされた、暗号的に署名されたIDアサーション（64-ビットのSteamIDを含む）を受け取ることができます。\n\n2. プログラムによるインベントリ照会およびAPIキーの不正利用： OpenID を通じてユーザー認証が確認されると、オペレーターはパブリックおよびパートナーの Web API エンドポイントにクエリを送信します（IEconItems_730/GetPlayerItems) により、在庫資産をリアルタイムでインデックス化している。自動取引ネットワークでは、プログラムによるセッショントークンを用いて、ピアツーピア（P2P）の取引オファーの送信、ポーリング、および受諾を行っており、これはSSA第4.C条が定める「人間以外の主体との相互作用」の禁止規定に直接違反している。\n\n3. リンクフィルタの非対称性： ユーザー向けのドメイン警告と、完全に機能している認証エンドポイントが併存していることは、規制上の矛盾を生み出しています。Valveのセキュリティテレメトリでは、これらの事業者を「潜在的に悪意のあるもの」として分類しているにもかかわらず、Valveの認証インフラは、引き続きそれらのユーザーを認証し続けているのです。\n\n証拠の取り扱い方法および証拠の保管経路に関する宣言\n\n本書は、認証されていないネットワークキャプチャ、RDAPの過去のレジストリクエリ、および検証済みの暗号ハッシュマニフェストに基づいて作成されました。ユーザーのログイン認証情報は、侵害テストの対象にもならず、処理もされていません。すべての調査結果は、9月2026.時点における実稼働ネットワークの観測可能な状態を反映したものです。本書は、司法、規制当局、および一般からの照会に対応するために作成された、超党派的な技術的証拠資料としての役割を果たします。\n\nダイジェスト： SHA-256 検証済み\nc507c9025f93da0aadaf395c4d8882f25973211c318ee8e9b6f18a5b3755e050\nアーカイブ： 公開法廷記録\n発行者および署名者： phishdestroy.io ・法科学研究連合\n法的地位： すべての権利は人類に委ねられた ・CC0 ユニバーサル・パブリック・ドメイン",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "法務監査法および規制関連資料"
          }
        ],
        "links": []
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ja/regulatory_act_print.content.json",
      "export_json_sha256": "30318e63aa68e206aa82bdeb4f8e2254470f69e9e7a3dcda0cb2d3f19b843e9b"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ja/security_timeline.html",
      "language": "ja",
      "title": "セキュリティの経緯 — 『Steam』に関する資料",
      "source_url": "https://phishdestroy.io/steam_dossier/ja/security_timeline",
      "source_html_sha256": "21e17ad7ee0bc04ba28fc6a2b3fec4b0989350436323beb9185a25d584fdfc5a",
      "exported_at": "2026-09-29T00:22:15.941Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "security_timeline.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ja/security_timeline.pdf?v=print-20260929-v5",
        "sha256": "eb66930ab2a62f8dc9594ae0e6ba2049205fdab88987566d8f06d9bc9b79601b",
        "bytes": 455997,
        "pages": 6
      },
      "integrity": {
        "signed_object": "security_timeline.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "security_timeline.content.json.asc",
        "digest_file": "security_timeline.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify security_timeline.content.json.asc security_timeline.content.json",
          "sha256sum -c security_timeline.content.json.sha256"
        ]
      },
      "content": {
        "text": "セキュリティの実績展示 / 『16』の応募作品\n\n2018 — 2026\n\nセキュリティの沿革 — 2018 から 2026 へ\n\nセキュリティが変更されました。 記録に従ってください。\n\nこのセクションが証明すること\n\nこの時系列記録は、Steamの取引および認証スタックにおける8年間にわたるセキュリティ対策の変更を再構築したものです。ここでは、2018 7-におけるデイトレードの保留機能の実装、2023 Web API におけるキーのモバイル確認、および2026 におけるセッショントークンの廃止が、記録されている迂回手法に対してどのように対応してきたかを追跡しています。このタイムラインは、プラットフォームの更新が既知の攻撃ベクトルに対して一貫して遅れをとっていた一方で、商業運営者にとっての構造的な優位性は維持されていたことを明らかにしています。\n\n← エグゼクティブ・ブリーフィングに戻る\n\n取引ロック。ログイン制御。APIの制限。何が変更されたか、そして情報源が実際に何を立証しているかについての、過去の記録。\n\n年表を閲覧する ↓\n8年。1枚のアルバム。16検討すべきマイルストーン\n\n各エントリには、投稿日と出典が記録されます。検証結果は、そのエントリの横に表示されます。\n\nレビュー済み / 24 9月2026\n10確認済みのイベントと日付\n06一部確認済み\n00ソースの不一致\n00出典が必要\nこの記録の見方\n\n確認済みのイベントと日付： いずれも、読みやすい一次資料によって裏付けられている。 一部確認済み： 関連する変更については記録されているが、その日付や範囲については未確定のままである。 ソースの不一致： リンク先の資料は、提出された主張を裏付けるものではありません。 出典が必要： 今回の検証では、該当する日付の記載がある出典は確認されませんでした。未解決の記載があるからといって、その出来事が起こらなかったという証拠にはなりません。\n\n未解決のエントリに記載されている日付は、提出日であり、確認済みの公開日ではありません。調査の原文は書き直されていません。\n\n年表\n01 — 16\nレコードを検索するトピック証拠注文\n\n16 16件の投稿 · 新しい順\n\n202609-01提出日\nコミュニティ一部確認済み\nグループチャットにおける不審なメッセージに関する警告\n\n公式のベータ版告知により、この機能が31年8月に実装されることが確認されました。併せて発表された1年9月の安定版リリース日については、具体的なリリースノートがまだ公開されていません。\n\nSteam クライアント・ベータ版 — 8月31日 ↗アーカイブ済み 2026-03-13 ↗\n元のエントリーと投稿されたリンク\n\n不審なチャットの自動フラグ付け\n\n提出されたソースコードを確認する ↗\n202601-16確認日\nAPI確認済みのイベントと日付\nパブリッシャーキーに対するきめ細かな権限設定とIPホワイトリスト機能（Valveの発表）\n\n16年1月2026,日、ValveはSteamworksに関する公式発表を公開しました（「新機能：Web API キーの権限と制御機能が強化されました」) 開発者が Web API のキーを個別のグループに分割できるようにする、新しいきめ細かな権限管理ツールが確認された（全般、マイクロトランザクション、経済、および売上データ)、キーを特定のApp IDに限定し、サーバーのIPアドレスのホワイトリスト登録を適用します。\n\n露骨な二重基準： 本公式発表により、Valveが、APIの詳細な権限設定およびIP制限のための技術的インフラを完全に整備したことが明らかになりましたが、 通常のユーザーアカウントからは意図的にそれらを非表示にしている（steamcommunity.com/dev/apikey). 通常のユーザー向けAPIキーは、IPホワイトリスト機能のない、一元的で「すべてか無か」の認証情報であり続けています。まさにこの技術的な欠落こそが、数百万ドル規模のAPI取引傍受産業を可能にしているのです。\n\nValve お知らせ — 新機能：Web API キーの権限と制御機能の強化（16 1月 2026） ↗· ドキュメント：Steamworks Web API 認証 ↗\n元のエントリーと投稿されたリンク\n\nSteamworks Web API 詳細なスコープ\n\n『Valve』のSteamworks公式発表（493839547938902179）をご覧ください ↗\n202507-15確認日\n取引確認済みのイベントと日付\nCS2の取引に7日間の反転期間が設けられる\n\nValveの発表によると、過去7日間の『Counter-Strike』アイテム取引の取り消し機能が導入される。これはハイジャックを防止することを目的としているが、第三者による経済監査（CSMarketCap ↗)は、 $104M (-25%) 折りたたみ 現金取引の混乱により、24時間以内に時価総額が下落した。分析によると、 Skinvault ↗、リバーサルが発生すると、その口座には自動的に30-のデイトレード利用制限が課されます。夏には2026, Valveが、UTC基準のグローバルな深夜リセットから、商品ごとに個別に設定された分単位のタイマー方式へと移行しました（Skin.land ↗).\n\nValve — 15 7月2025の発表 ↗· CSMarketCapの分析 ↗\n元のエントリーと投稿されたリンク\n\nCS2 取引保護／取り消し期間\n\n提出されたソースコードを確認する ↗\n202505-14確認日\n認証確認済みのイベントと日付\nValve SMSによる情報漏洩に関するアカウントのセキュリティ警告を発表\n\nValveが5月14,に発表した公式発表（2025,）では、アカウントのセキュリティおよびSMSベースの認証について言及しています。この通知はSMS情報の漏洩に焦点を当て、Steamのシステムへの不正アクセスはなかったことを確認していますが、提出日時点における公式なセキュリティ更新情報としての役割を果たしています。\n\nValve — 「Steam」アカウントのセキュリティに関するお知らせ ↗\n元のエントリーと投稿されたリンク\n\nアカウントのセキュリティに関するお知らせ\n\n提出されたソースコードを確認する ↗\n202410-02確認日\n取引確認済みのイベントと日付\n再取引または再販売の7日前\n\nこのリリースノートでは、ゲーム内ショップを通じて入手できるアイテム（「アーモリー」、トレードオファー、コミュニティマーケットなど）について解説しています。記載されている範囲は、「アーモリー」のアイテムだけにとどまりません。\n\nValve — 「10/2/2024」のリリースノート ↗\n元のエントリーと投稿されたリンク\n\nCS2 アーモリー / 7-Day Hold\n\n提出されたソースコードを確認する ↗\n202409-18提出日\n取引一部確認済み\nヘルプページで新しいデバイスの制限事項を確認しました\n\nSteamの公式サポートドキュメントによると、7日以上認証されていない新しいデバイスからログインした場合、7-のデイトレード制限が適用されることが確認されています。9月18,に2024,で実施されたこの機能の正確なリリース日は、変更履歴のマイルストーンとして記録されていませんが、この機能については完全にドキュメント化されています。\n\nSteam サポート — 取引および市場の制限事項 ↗\n元のエントリーと投稿されたリンク\n\n新しいデバイスでのログインに関する取引制限\n\n提出されたソースコードを確認する ↗\n202402-14提出日\nコミュニティ一部確認済み\n2024 で、名称変更の取引クールダウンが実装されました\n\nコミュニティおよび開発者の記録によると、2024,の初期に、Valveは、プロフィール名の変更直後に2-から4時間という取引クールダウンを予告なしに導入し、急速ななりすまし詐欺を防止したことが確認されています。Valveはこの制限について、公式のプレスリリース、クライアントの変更履歴、サポート記事を一切公開しなかったため、2月14に提出された日付には正式な裏付けがありません。SteamのWorkshopガイドは、公式のValveドキュメントというよりは、コミュニティによる間接的な裏付けとして機能しています。\n\nSteam ワークショップガイド（間接的な裏付け） — 名称変更の制限に関する詳細 ↗\n元のエントリーと投稿されたリンク\n\nプロフィール名・アバター変更の一時停止\n\n提出されたソースコードを確認する ↗\n202312-04確認日\nAPI確認済みのイベントと日付\n鍵の作成には、モバイル端末での確認が必要です\n\nWeb API での鍵生成において、Steam Guard によるモバイル認証が必須化されたことは、サードパーティの開発者向けライブラリの記録から、2023, の後半に実施されたことが確認されています。12月4, 2023, という正確な日付は、開発者コミュニティ内で確認された導入期間を示しています。\n\nメンテナー向けドキュメント — 3月 2024 ↗アーカイブ 2026-09-24 ↗\n元のエントリーと投稿されたリンク\n\nAPIキーのモバイル認証\n\n提出されたソースコードを確認する ↗\n202310-24確認日\n開発者確認済みのイベントと日付\nゲームビルドのライブ配信設定に関する2の必須FAが施行されます\n\nValveが10月10,に発表したSteamworksに関する公式発表（2023,）によると、10月24,より（2023,）、リリース済みのアプリケーションのデフォルトブランチでビルドをライブ設定するアカウントは、SMSまたはSteamモバイルアプリを通じて変更を承認する必要があることが確認されました。この変更に伴い、SetAppBuildLive Web（API）も直接更新されました。\n\nSteamworks — ビルドおよびユーザーの管理に関するセキュリティの強化 ↗アーカイブ済み 2025-12-03 ↗\n元のエントリーと投稿されたリンク\n\nゲームビルド・パブリケーションズ向けのSMS多要素認証（MFA）\n\n提出されたソースコードを確認する ↗\n202307-12提出日\nコミュニティ一部確認済み\nコミュニティによって指摘された、カスタム経歴欄のコンテンツに関する警告\n\nSteam 7月から寄せられたコミュニティからの報告（2023）によると、外部リンクやトリガーワードを含むカスタムプロフィール紹介文に対して、自動的なコンテンツ警告が表示されるようになったことが確認されています。7月12,に投稿された報告（2023,）の日付は、Steamのコミュニティフォーラムで最初に報告が相次いだ時期と一致しています。\n\nSteam コミュニティフォーラム — バイオコンテンツに関する警告報告 ↗\n元のエントリーと投稿されたリンク\n\nカスタム経歴コンテンツに関する注意喚起\n\n提出されたソースコードを確認する ↗\n202301-25提出日\nコミュニティ一部確認済み\nプロフィールリンクのフィルタリングおよび編集のクールダウンが有効になっています\n\nSteamの公式サポートドキュメントによると、カスタムプロフィールに記載されたリンクはフィルタリングされており、不適切な名前やアバターの変更は編集禁止措置につながる可能性があることが確認されています。1月25, 2023,に導入された4-の1時間のクールダウン機能こそが、この現象の始まりとされていますが、リンクフィルタリング機能自体は、公開されたヘルプページ上ですでに完全に稼働しています。\n\nSteam サポート — プロフィール名とアバターに関する制限 ↗\n元のエントリーと投稿されたリンク\n\nプロフィールリンクを削除 / クールダウン\n\n提出されたソースコードを確認する ↗\n202210-24確認日\n認証確認済みのイベントと日付\nSteam OAuthのリフレッシュトークンおよびアクセストークンへの移行\n\nValveの10月の主要なクライアントおよびモバイルアプリの更新2022は、Steamの認証システムを全面的に刷新しました。従来のセッションクッキーの仕組みは、OAuthベースのアクセストークンおよびリフレッシュトークンに置き換えられ、アクティブな認証済みデバイスの一覧が導入され、アクティブなセッションを手動で取り消せるようになりました。\n\nValve — 「Steam」モバイルアプリのアップデートと認証機能の全面刷新 ↗\n元のエントリーと投稿されたリンク\n\nSteam ログイン機能の全面見直し／Cookieの切り捨て\n\nValveの発表を確認する ↗\n202210-12確認日\n認証確認済みのイベントと日付\nQRコードによるログインと認証済みデバイスの管理\n\nValveが10月に発表した「12」では、QRコードによるサインイン、サインインの承認または拒否、およびアカウントへのアクセス権を無効にできるデバイス一覧について説明されています。\n\nValve — アップデートされた「Steam」モバイルアプリが利用可能になりました ↗\n元のエントリーと投稿されたリンク\n\nSteam モバイルアプリ 3.0 / QRコードによるログイン\n\n提出されたソースコードを確認する ↗\n202205-10提出日\nAPI一部確認済み\nAPIの公開リストから取引キャンセル用エンドポイントが削除されました\n\n開発者の記録によると、5月 2022, Valve に、Web API から IEconService/CancelTradeOffer や DeclineTradeOffer といった取引管理エンドポイントが、事前の告知なしに削除されたことが確認されています（node-steam-tradeoffer-manager #325 に記載）。 これらのメソッドはプライベートクライアントプロトコルでは引き続き機能しますが、10, 2022, の日付は、詐欺パネル対策として公開Web APIからこれらのメソッドが削除されたことを示しています。\n\n開発者による議論 — 課題 #325（CancelTradeOffer の削除） ↗· Steamworks Web API — IEconService ドキュメント ↗\n元のエントリーと投稿されたリンク\n\n取引キャンセルエンドポイントの削除\n\nnode-steam-tradeoffer-manager の課題 #325 を確認する ↗\n202005-25確認日\n取引確認済みのイベントと日付\n『Dota2』のアイテムには、7日間の取引クールダウンが適用されます\n\n5月25,、2020, において、『10』のバトルパスがリリースされたこと（blog.dota2.com/2020/05/the-international-10-battle-pass/）に伴い、Valveは、『Dota』2のアイテムに対して、1日間の取引ロック（7-）を導入しました。これは、2018の『Counter-Strike』に関するポリシーに準じた措置です。この制限は、すべての取引アイテムおよびマーケットでの購入に適用されます。\n\nDota2コミュニティ — トレードロックとTI10クライアントのアップデート ↗\n元のエントリーと投稿されたリンク\n\nDota 2 / 7-デイ・トレード・ロック\n\n提出されたソースコードを確認する ↗\n201803-29確認日\n取引確認済みのイベントと日付\nCS:GOのアイテムをトレードすると、7日間のクールダウン期間が適用されます\n\n公式のリリースノートで、日付と制限事項が確認されています。提供されたURLは2013の地図更新ページにリダイレクトされましたが、これに対応するリリースノートのURLは20309.で終わっています。\n\nValve — 「3/29/2018」のリリースノート ↗\n元のエントリーと投稿されたリンク\n\nCS:GO / 『7-』デイ・トレード・ロック\n\n提出されたソースコードを確認する ↗ アーカイブ済み 2025-02-26 ↗\n\n証拠を追跡し、情報源を精査する。\n\n調査に戻る ↗",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "セキュリティの沿革 — 2018 から 2026 へ"
          },
          {
            "level": 2,
            "id": null,
            "text": "年表"
          },
          {
            "level": 2,
            "id": null,
            "text": "グループチャットにおける不審なメッセージに関する警告"
          },
          {
            "level": 2,
            "id": null,
            "text": "パブリッシャーキーに対するきめ細かな権限設定とIPホワイトリスト機能（Valveの発表）"
          },
          {
            "level": 2,
            "id": null,
            "text": "CS2の取引に7日間の反転期間が設けられる"
          },
          {
            "level": 2,
            "id": null,
            "text": "Valve SMSによる情報漏洩に関するアカウントのセキュリティ警告を発表"
          },
          {
            "level": 2,
            "id": null,
            "text": "再取引または再販売の7日前"
          },
          {
            "level": 2,
            "id": null,
            "text": "ヘルプページで新しいデバイスの制限事項を確認しました"
          },
          {
            "level": 2,
            "id": null,
            "text": "2024 で、名称変更の取引クールダウンが実装されました"
          },
          {
            "level": 2,
            "id": null,
            "text": "鍵の作成には、モバイル端末での確認が必要です"
          },
          {
            "level": 2,
            "id": null,
            "text": "ゲームビルドのライブ配信設定に関する2の必須FAが施行されます"
          },
          {
            "level": 2,
            "id": null,
            "text": "コミュニティによって指摘された、カスタム経歴欄のコンテンツに関する警告"
          },
          {
            "level": 2,
            "id": null,
            "text": "プロフィールリンクのフィルタリングおよび編集のクールダウンが有効になっています"
          },
          {
            "level": 2,
            "id": null,
            "text": "Steam OAuthのリフレッシュトークンおよびアクセストークンへの移行"
          },
          {
            "level": 2,
            "id": null,
            "text": "QRコードによるログインと認証済みデバイスの管理"
          },
          {
            "level": 2,
            "id": null,
            "text": "APIの公開リストから取引キャンセル用エンドポイントが削除されました"
          },
          {
            "level": 2,
            "id": null,
            "text": "『Dota2』のアイテムには、7日間の取引クールダウンが適用されます"
          },
          {
            "level": 2,
            "id": null,
            "text": "CS:GOのアイテムをトレードすると、7日間のクールダウン期間が適用されます"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/ja/#briefing-heading",
          "https://steamcommunity.com/groups/SteamClientBeta?l=english",
          "http://web.archive.org/web/20260313235409/https://steamcommunity.com/groups/SteamClientBeta?l=english",
          "https://store.steampowered.com/news/posts/?enddate=1788390000",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/493839547938902179",
          "https://partner.steamgames.com/doc/webapi_overview/auth",
          "https://csmarketcap.com/blog/market-insights/from-boom-to-bust-cs2s-trade-protection-impact",
          "https://skinvault.gg/blog/cs2-trade-protection-explained/",
          "https://skin.land/blog/steam-changes-cs2-trade-ban-logic-timing/",
          "https://store.steampowered.com/news/posts/?appids=730&amp;enddate=1753924057&amp;feed=steam_announce%2F1000",
          "https://help.steampowered.com/faqs/view/3041-A87A-E5F6-B6AC",
          "https://store.steampowered.com/news/posts/?enddate=1747349559",
          "https://steamcommunity.com/ogg/593110/announcements/detail/533224478739530146",
          "https://store.steampowered.com/news/posts/?appids=730&amp;enddate=1728000977&amp;feed=steam_community_announcements",
          "https://steamcommunity.com/games/CSGO/announcements/detail/4447966961421256740",
          "https://help.steampowered.com/faqs/view/7F77-9E92-31E0-6B8E",
          "https://steamcommunity.com/sharedfiles/filedetails/?id=2926756889",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "http://web.archive.org/web/20260924181824/https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "https://steamcommunity.com/dev/apikey",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3749866608167579206",
          "http://web.archive.org/web/20251203174259/https://steamcommunity.com/groups/steamworks/announcements/detail/3749866608167579206",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3734103130194459461",
          "https://steamcommunity.com/discussions/forum/1/3807266184852932971/",
          "https://help.steampowered.com/faqs/view/225C-C51E-B8F0-55B2",
          "https://store.steampowered.com/news/group/4/view/3314112260640237775",
          "https://store.steampowered.com/news/posts/?appgroupname=Keep+in+touch&amp;enddate=1666122699&amp;feed=steam_blog",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/issues/325",
          "https://partner.steamgames.com/doc/webapi/IEconService",
          "https://steamcommunity.com/app/570/announcements/",
          "https://blog.dota2.com/2020/05/trading-cooldown/",
          "https://blog.counter-strike.net/2018/03/20309/",
          "https://blog.counter-strike.net/index.php/2018/03/20308/",
          "http://web.archive.org/web/20250226114333/https://blog.counter-strike.net/index.php/2018/03/20308/",
          "https://phishdestroy.io/steam_dossier/ja/#vulnerability-profile"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ja/security_timeline.content.json",
      "export_json_sha256": "3ee6a8d3cabc3b3c13ce4d66283c5fa38e576885ea18f66701214fbb8c75127b"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ja/skin_atlas.html",
      "language": "ja",
      "title": "Steamが運べないものの図鑑 — 『Steam』特集",
      "source_url": "https://phishdestroy.io/steam_dossier/ja/skin_atlas",
      "source_html_sha256": "7e0b0129c97df10537e7586f746cbc27a7ec838f91c1baf147202228ce05ed1b",
      "exported_at": "2026-09-29T00:22:19.105Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "gallery",
            "source": "https://phishdestroy.io/steam_dossier/ja/skin_atlas#gallery"
          }
        ],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "skin_atlas.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ja/skin_atlas.pdf?v=print-20260929-v5",
        "sha256": "de80790ee8901587903a92295d9a04f16787f651aa3bfde2225af38d14a7bbb4",
        "bytes": 602589,
        "pages": 13
      },
      "integrity": {
        "signed_object": "skin_atlas.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "skin_atlas.content.json.asc",
        "digest_file": "skin_atlas.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify skin_atlas.content.json.asc skin_atlas.content.json",
          "sha256sum -c skin_atlas.content.json.sha256"
        ]
      },
      "content": {
        "text": "別紙IV-B／価格ラダー／2026-09-23\nスキン・プライス・ラダー・アトラス — 流動性の崖\n\nValveの市場での立ち寄り先 お金の源流。\n\nこのセクションが証明すること\n\nこのビジュアルアトラスは、5つのマーケットプレイスのカタログにおける「30,266」の商品カテゴリーを分析し、Valveの出品基準を上回る市場カバー率と下回る市場カバー率を測定したものです。 $1,800の上限を下回る範囲では、Steamは95.3%のアクティブなカテゴリーをホストしています。その上限をわずかに超えると、公式のカバー範囲は1.9%に激減します（0.0%のカバー範囲は裏付けされた資産に限定されます）。これは、Valveが基礎となる資産の保管については完全な管理権を保持しつつ、高額取引の発見を外部プラットフォームに委ねているという、急激かつ構造的な流動性の断崖を示しています。\n\n← エグゼクティブ・ブリーフィングに戻る\n\n5つのマーケットプレイスでリアルタイムの価格が表示されているすべてのCS2アイテムは、最も安い売り出し価格に基づいて価格帯に分類され、各価格帯について、Valve独自のコミュニティマーケットが依然としてその価格帯のどの程度のシェアを占めているかという一点のみが測定されました。Valveの出品上限を下回る範囲では、その答えは 95.3%. その上にある答えは 1.9%. その下落は緩やかなものではなく、需要が低下する場所で下落するわけでもなく、公表された規則に完全に沿って下落する。そのうち 248 2つ以上のマーケットプレイスが独自に上限価格を超えて価格設定している商品カテゴリについては、100.0% には Steam の掲載が一切ありません。\n\n崖をご覧ください ↓「419」のアイテムギャラリーを開く方法と制限事項\n30,266測定対象の品目カテゴリ\n95.3%Steamが保有する資本外項目のうち\n1.9%Steamが取り扱う上限額を超える商品のうち\n$78.6M裏付けのある集合の下限値\n01 / 測定\n崖は「要求」ではなく「規則」に基づいて現れる\n\n以下の「30,266」の各アイテムカテゴリは、その 最も安い BUFF163、CSFloat、Skinport、YouPin 898、C5Game でのライブアスクを対象とし、そのうち2つ以上で価格が提示されているアイテムのみをカウントするため、1つの楽観的な出品だけでバンドメンバーをでっち上げることはできません。上段のグラフは、Valve独自の市場で現在も取り扱われている各バンドのシェアを示しています。\n\nSteamコミュニティマーケットで取り扱われている各価格帯の割合\n上段：蒸気分布 · 下段：バンドごとの項目数（対数スケール）\n0%\n25%\n50%\n75%\n100%\n100%\n96.9%\n95.9%\n97.3%\n91.1%\n76.8%\n14.5%\n2.9%\n1.5%\n0%\n0%\n0%\n4,632\n1¢–10¢\n7,152\n10¢–$1\n8,568\n$1–10\n5,941\n$10–100\n2,329\n$100–300\n1,292\n$300–1k\n193\n$1k–1.8k\n70\n$1.8k–3k\n67\n$3k–10k\n18\n$10k–30k\n3\n$30k–100k\n1\n$100k+\nitems\nlog\nVALVE’S LISTING CAP\nValveの上場上限額以下上限を超える — 「Valve」の規則により、掲載は禁止されていますバンド内のアイテムカテゴリ\n\n「カバレッジ」とは、取得時点でそのカテゴリーについてSteamのライブ質問が存在していたことを意味します。下段のグラフが対数スケールになっているのは、カタログに掲載されている作品が圧倒的に安価であるためです。線形スケールで表示すると、300以上の価格帯がすべてベースラインまで平坦化されてしまいます。\n\nその形状から除外されるもの\n\nもし高価な商品が単に人気がないだけなら、価格が上昇するにつれて需要曲線は徐々に低下するはずだ。しかし、実際にはそうならない。需要曲線は76.8%で横ばいを保ち、$300–$から1kの範囲を通過した後、上限の直下の範囲では14.5%まで急落し、上限の直上の範囲では2.9%まで急落する。需要の効果には、Valveが上限をどこに設定したかなど分からない。ルールがあるからこそ、そうなるのだ。\n\n価格帯\t商品カテゴリ\tSteamのライブ配信で質問する\tSteam 報道範囲\tSteam に掲載されているコピー\n1¢–10¢\t4,632\t4,632\t100%\t8,223,227\n10¢–$1\t7,152\t6,931\t96.9%\t5,488,315\n$1–10\t8,568\t8,213\t95.9%\t3,939,538\n$10–100\t5,941\t5,780\t97.3%\t1,328,255\n$100–300\t2,329\t2,121\t91.1%\t364,466\n$300–1k\t1,292\t992\t76.8%\t187,504\n$1k–1.8k\t193\t28\t14.5%\t40,281\n$1.8k–3k\t70\t2\t2.9%\t9,592\n$3k–10k\t67\t1\t1.5%\t6,706\n$10k–30k\t18\t0\t0%\t1,366\n$30k–100k\t3\t0\t0%\t21\n$100k+\t1\t0\t0%\t2\n\nこのランキングからは、パターンおよびフェーズのバリエーションは除外されています。Steamでは、ブルー・ジェム・ティアやルビー・フェーズが独立した市場参入項目として記載されていないため、これらを含めるとSteamのカバー範囲が過小評価されてしまうからです。 2つのマーケットプレイスという要件を除外して測定した場合、このランキングは上限以下で79.1%、上限以上で6.5%という結果になります（37,204の全アイテムを対象）。これは、より不確かな根拠に基づく、より顕著な格差を示しており、これが引用されていない数値である理由です。\n\n02 / 証拠に基づく評価\n希望価格は価格そのものではない\n\n誰でもP2000を1,000万元で出品することは可能です。このページに掲載されている数値が何らかの目的で使用される前に、その商品が上限価格を上回る価格で何つのマーケットプレイスから独立して提示されているか、またそれらの提示価格の中央値がどの程度集中しているかによって、その数値のグレードが決定されます。ここでも、この資料の他の部分でも、提示されるのはグレードAおよびBのみです。\n\nA  3つ以上の棚が一致する\n\n3つ以上のマーケットプレイスで、当該商品が上限価格を上回る価格で見積もられており、その中央値が最も安い価格から25%以内の範囲にある。 197 カテゴリー、18,218部、$76,585,587.\n\nSteamには以下のものが含まれていません： 100.0%.\n\nB  2つの棚が一致している\n\n2つのマーケットプレイスが上限を超えて合意するか、あるいは3つのマーケットプレイスがそれより緩やかな条件で合意する。 51 カテゴリー、176部、$2,038,814.\n\nSteamには以下のものが含まれていません： 100.0%.\n\nC  棚が1つ — 未使用\n\nある1つのマーケットプレイスにのみ、上限価格を上回る売り注文が出ている。 171 カテゴリー、247部。 完全性を期すためギャラリーに表示されていますが、このページ上のすべての合計からは除外されています。\n\nこれらは価格に関する問い合わせであり、価格を示す証拠ではありません。\n\nこの是正措置にどれほどのコストがかかり、何をもたらしたのか\n\nCランクを削除すると、見出しから「171」というカテゴリーと「$3,825,125」が削除されます。残るのはより簡潔で、反論の余地がはるかに少ない内容となります： 248 カテゴリ、18,394 に掲載されている品、$78,624,401, および 100.0% に掲載されている品――そのすべて――が、Valveのマーケットプレイスには掲載されていません。 Cクラスの行こそが、数値が変動した原因です。これらは非表示ではなく、一覧に表示されています。\n\n「遺物」として区分された出品物\n\n同一商品について、最も安い売値の3倍を超える見積もりは除外されます。データ自体が示唆するレートで換算すると、そのほとんどは人民元（CNY）の端数のない整数であり、これは実際のオファーというよりは、プレースホルダーやプラットフォームの上限値であることを示しています。このページのすべての合計額は、 最も安い 言うまでもなく、これらの人物の誰一人として数字を水増ししたことはあり得ない。彼らを除外したのは、誰一人として見出しとして引用されないようにするためでもある。\n\n品目\t最も安いライブアスク\t取っておく\nSouvenir P2000 | Wicked Sick (Minimal Wear)\t$148,954\t$1,489,543\n★ Specialist Gloves | Crimson Kimono (Minimal Wear) | Phase 1\t$37,239\t$119,163\nSouvenir USP-S | Printstream (Factory New)\t$2,000\t$59,582\n★ Bowie Knife | Crimson Web (Factory New)\t$2,957\t$43,030\n★ Karambit | Marble Fade (Factory New) | 1st\t$11,916\t$38,874\nSticker | Ninjas in Pyjamas (Holo) | Katowice 2014\t$5,000\t$31,748\nSouvenir AWP | Dragon Lore (Battle-Scarred)\t$4,225\t$29,157\n★ Karambit | Doppler (Minimal Wear) | Ruby\t$7,122\t$27,273\n419のすべてのカテゴリと、各価格が対応するオブジェクト\n\n出典: https://phishdestroy.io/steam_dossier/ja/skin_atlas#gallery\n\n04 / 代わりにどこへ行ったのか\nSteamが扱わない商品を並べる棚\n\n同じ出品物を、それを掲載しているマーケットプレイスごとにまとめたものです。これは、その商品がどこにあるかの件数です。 掲載済み, これは所有地とは異なり、ここではそのように解釈されることはない。\n\n各マーケットプレイス別の、上限価格を超える物件の最低価格\nその棚に並んでいる「最低売値×部」\nYouPin 898\n$22,720,252\nBUFF163\n$22,022,606\nC5Game\n$12,560,543\nCSFloat\n$10,871,845\nSkinport\n$1,385,060\n\n管轄地域（上記の順）：YouPin 898 — 中国 · BUFF163 — 中国 · C5Game — 中国 · CSFloat — 米国 · Skinport — ドイツ／マルタ。同一の物理的な商品は、これらの棚のうち複数に並べて掲載される可能性があるため、これらの数値を他の市場の合計値と合算してはならない。\n\n価格帯別の最低価格\n上限額を超える資金がどのように配分されるか\n$1.8k-3k\n$9,842,391\n$3k-10k\n$36,787,269\n$10k-50k\n$20,038,749\nover $50k\n$2,891,897\n05 / 数えられるほどの希少性\n実際に供給がどれほど逼迫しているのか\n\nCS2の各アイテムには「摩耗度」が設定されており、マーケットプレイスではその各帯域にいくつのコピーが存在するかが公開されています。これにより、「レア」という形容詞が数値へと変わり、その数値こそが、たった1つの侵害されたアカウントのために、特注のフィッシングキットを用意する労力が報われる理由を説明しているのです。\n\nAWP | ドラゴンの伝承\n150 掲載中・価格：11,350から\n0.00–0.01\n29 · $14,730\n0.01–0.02\n54 · $11,618\n0.02–0.03\n26 · $11,350\n0.03–0.04\n25 · $11,618\n0.04–0.07\n16 · $11,585\n\nAWP | ドラゴン・ロア（新品同然）\n\nM4A4 | ハウル\n105 掲載中・価格：6,628\n0.00–0.01\n11 · $10,725\n0.01–0.02\n14 · $8,088\n0.02–0.03\n11 · $7,580\n0.03–0.04\n19 · $6,703\n0.04–0.07\n50 · $6,628\n\nM4A4 | ハウル（工場出荷時新品）\n\nAK-47 | ワイルド・ロータス\n113 掲載中・価格：14,373 ドル～\n0.00–0.01\n25 · $22,343\n0.01–0.02\n11 · $19,364\n0.02–0.03\n3 · $19,645\n0.03–0.04\n15 · $15,044\n0.04–0.07\n59 · $14,373\n\nAK-47 | ワイルド・ロータス（工場出荷時新品）\n\nAWP | グングニル\n173 掲載中・価格：11,618\n0.00–0.01\n28 · $17,875\n0.01–0.02\n21 · $13,600\n0.02–0.03\n32 · $12,065\n0.03–0.04\n29 · $11,735\n0.04–0.07\n63 · $11,618\n\nAWP | グングニル（新品）\n\nAK-47 | ファイア・サーペント\n278 掲載中・価格：663\n0.15–0.18\n87 · $730\n0.18–0.21\n49 · $712\n0.21–0.24\n52 · $703\n0.24–0.27\n18 · $715\n0.27–0.38\n72 · $663\n\nAK-47 | ファイア・サーペント（実戦検証済み）\n\nケースハードニング（全ティア／青色の宝石）\n76 掲載中・価格：1,638 ドルから\n0.07–0.08\n1 · $2,516\n0.08–0.09\n4 · $2,482\n0.09–0.10\n6 · $3,856\n0.10–0.11\n7 · $2,797\n0.11–0.15\n58 · $1,638\n\nAK-47 | 表面硬化処理済み（摩耗はごくわずか） | グレード1\n\nバンドはマーケットプレイス独自の流動性バケットであり、少なくとも1件のリアルタイムの成行注文があるバンドのみが抽出されます。各バーの横に表示されている価格は、そのバンド内で最も安いリアルタイムの売り気配価格であるため、流動性が低い場合に生じるプレミアムは、明示されるのではなく、一目で把握することができます。\n\n06 / 動き（Steam に基づいて測定）\nサードパーティ製棚が実際に実現したこと\n\nValve このレベルでは実用的な履歴データは公開されておらず、この資料でもそのようなデータは主張されていません。Skinport では、直近の24時間、7,30および90日間の成約実績を公開していますが、ここで利用可能な時間軸はそれだけです。つまり、各期間ごとの実現価格の中央値が、90-日の中央値が 100. となるよう指数化されています。 どちらのグラフにも、Steamのデータは含まれていません。\n\n実現価格の中央値（直近の期間）\n90-日の中央値に連動 · 6,758 アイテム（20+ 売上）\n85\n91\n97\n103\n100\n90d\n94\n30d\n90\n7d\n88\n24h\n1日あたりの成約件数\n同じ商品、同じウィンドウ\n7,621\n9,653\n11,684\n13,716\n12,700\n90d\n11,894\n30d\n9,540\n7d\n8,637\n24h\n\nこれらは、1つのグラフに2つの縦軸（インデックスと日別件数）が設定されているのではなく、2つの別々のグラフです。インデックスと日別件数は単位が異なるため、共通の軸上にプロットすると、妥当ではない比較を招く恐れがあります。ウィンドウは入れ子構造になっており、後続のウィンドウが先行するウィンドウを包含する形式（90-日の数値には24-時間の数値が含まれる）となっているため、これは日次系列ではなく、そのように解釈してはなりません。 このグラフが示唆する点は限定的であり、明確に述べられています。Skinportが公表したトレーリング・ウィンドウ期間において、実現価格の中央値は、90-日の中央値を下回っており、日次販売件数もそれに伴って減少しました。\n\nSkinport 実現売上高。ウィンドウは入れ子構造で移動式となっているため、各データポイントは、直近のウィンドウにおける実現価格の中央値であり、90-日の中央値を基準として指数化されています。これは日次データではなく、Steamのデータは使用されていません。\n\n07 / どのような素材でできているのか\n16年前のステッカーと、一握りの手袋\n\nキャップを上回る価格帯は、市場全体を広く代表するものではありません。それはごく一部の希少品やコレクションに集中しており、そのうちのいくつかはもはや入手不可能となっています。まさにそれが、供給が価格に反応できない理由なのです。\n\nキャップより上のカテゴリー（レア度別）\nアイテムカテゴリの数\nCovert\n321\nClassified\n39\nRestricted\n24\nContraband\n12\nMil-Spec Grade\n9\nConsumer Grade\n9\nIndustrial Grade\n5\nキャップの上にあるカテゴリー（コレクション別）\nトップ10コレクション\nThe St. Marc Collection\n13\nThe Cobblestone Collection\n13\nThe Norse Collection\n12\nThe Arms Deal Collection\n9\nThe Canals Collection\n7\nThe Gods and Monsters Collection\n6\nThe Revolution Collection\n4\nThe 2021 Train Collection\n4\nThe Rising Sun Collection\n4\nThe Chop Shop Collection\n4\n\nカテゴリ別：skin 366, sticker 48, container 3, sticker_slab 2.\n\n08 / 実際に支払われた最高額\n上値は上場ではなく、取引によって支えられている\n\nこのページに掲載されているその他の価格はすべて 尋ねる — 売り手が求めているもの。これらは 売上: 各商品について、過去90日間の間にSkinportで記録された最高成約価格。これは、この資料の中で実際に支払われた金額を示す唯一の数値であり、各行にはマーケットプレイスへのリンクが貼られているため、当方ではなく情報源そのもので金額を確認することができます。\n\n21,216期間中に販売が完了した商品\n106Valveの上限価格以上で売却された\n$14,192過去最高の単一成約額\n67/419販売実績のある上限超過カテゴリ\n当該期間における成約額上位30件\n品目\t最高売上\t販売価格の中央値\t売上\t今すぐ最安値を確認\tSteam\t確認して\nAWP | Gungnir (Factory New)\t$14,192\t$11,343\t5\t$11,490\tabsent\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Factory New)\t$12,387\t$12,387\t1\t$13,836\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Factory New)\t$11,779\t$11,063\t16\t$10,941\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Minimal Wear)\t$11,693\t$11,693\t1\t$9,946\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Minimal Wear)\t$10,437\t$10,437\t1\t$9,610\tabsent\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Blue Laminate (Minimal Wear)\t$9,772\t$37\t76\t$30\t$40\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Minimal Wear)\t$9,463\t$9,463\t1\t$9,500\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Minimal Wear)\t$9,104\t$9,026\t6\t$8,524\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Hedge Maze (Minimal Wear)\t$8,139\t$8,139\t1\t$6,819\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Field-Tested)\t$7,617\t$7,390\t4\t$7,194\tabsent\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Field-Tested)\t$7,615\t$7,615\t1\t$7,100\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Field-Tested)\t$7,149\t$7,006\t2\t$7,165\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Field-Tested)\t$6,711\t$6,194\t15\t$5,988\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Factory New)\t$6,679\t$6,613\t3\t$6,628\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Superconductor (Factory New)\t$6,084\t$6,084\t1\t$7,969\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Battle-Scarred)\t$5,750\t$5,413\t3\t$5,899\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Pandora's Box (Minimal Wear)\t$5,520\t$5,508\t3\t$4,998\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Vice (Factory New)\t$5,385\t$5,158\t2\t$5,700\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Minimal Wear)\t$5,342\t$4,989\t19\t$4,997\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Hedge Maze (Field-Tested)\t$5,334\t$4,862\t5\t$3,724\tabsent\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Vulcan (Factory New)\t$5,275\t$1,418\t12\t$1,280\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Well-Worn)\t$4,978\t$4,978\t1\t$4,942\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Well-Worn)\t$4,931\t$4,931\t1\t$5,445\tabsent\tSkinport CSFloat Steam\nAK-47 | Hydroponic (Factory New)\t$4,802\t$4,351\t2\t$3,648\tabsent\tSkinport CSFloat Steam\n★ Talon Knife | Case Hardened (Minimal Wear)\t$4,588\t$466\t16\t$442\t$630\tSkinport CSFloat Steam\nAWP | Medusa (Factory New)\t$4,484\t$4,484\t1\t$4,171\tabsent\tSkinport CSFloat Steam\n★ Specialist Gloves | Pillow Punchers (Factory New)\t$4,359\t$4,359\t1\t$4,302\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Pandora's Box (Field-Tested)\t$4,359\t$3,666\t11\t$3,245\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Field-Tested)\t$4,289\t$4,225\t8\t$4,022\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Battle-Scarred)\t$4,124\t$4,124\t1\t$4,279\tabsent\tSkinport CSFloat Steam\n同じ商品、同じ90のセール期間なのに、価格がまったく異なる\n\n中央値が100ドル以上で、かつ成約済みの取引が5件以上あるアイテムに限定しています。これは、安価なスキンでは、たった1件の異常な取引で比率が大きく歪んでしまうためです。その結果、残ったアイテムは主に 表面硬化処理 「finishes」では、パターンによって価格が決定され、マーケットプレイスはすべてのパターンを1つの名前で分類します。これは、05.セクションでfloatを用いて測定されたのと同じ仕組みです。\n\n品目\t最高値対中央値\t最高売上\t販売価格の中央値\t売上\t確認して\n★ Talon Knife | Case Hardened (Minimal Wear)\t+884%\t$4,588\t$466\t16\tSkinport CSFloat Steam\nDesert Eagle | Cobalt Disruption (Factory New)\t+859%\t$1,210\t$126\t115\tSkinport CSFloat Steam\nAWP | BOOM (Minimal Wear)\t+814%\t$1,232\t$135\t89\tSkinport CSFloat Steam\nAK-47 | Case Hardened (Well-Worn)\t+769%\t$1,720\t$198\t70\tSkinport CSFloat Steam\nAWP | Graphite (Factory New)\t+761%\t$1,469\t$171\t124\tSkinport CSFloat Steam\n★ Talon Knife | Case Hardened (Field-Tested)\t+509%\t$2,437\t$400\t48\tSkinport CSFloat Steam\n★ Kukri Knife | Case Hardened (Minimal Wear)\t+448%\t$723\t$132\t69\tSkinport CSFloat Steam\n★ Kukri Knife | Case Hardened (Field-Tested)\t+415%\t$549\t$106\t128\tSkinport CSFloat Steam\n★ Ursus Knife | Case Hardened (Minimal Wear)\t+371%\t$597\t$127\t12\tSkinport CSFloat Steam\nAK-47 | Case Hardened (Field-Tested)\t+369%\t$1,037\t$221\t125\tSkinport CSFloat Steam\nAK-47 | Red Laminate (Minimal Wear)\t+360%\t$552\t$120\t18\tSkinport CSFloat Steam\nAWP | Asiimov (Field-Tested)\t+351%\t$528\t$117\t439\tSkinport CSFloat Steam\nAK-47 | Vulcan (Field-Tested)\t+337%\t$865\t$198\t241\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Nightwish (Factory New)\t+322%\t$625\t$148\t31\tSkinport CSFloat Steam\nAWP | Lightning Strike (Factory New)\t+319%\t$2,065\t$493\t198\tSkinport CSFloat Steam\nStatTrak™ AWP | Redline (Minimal Wear)\t+312%\t$574\t$139\t24\tSkinport CSFloat Steam\nStatTrak™ AWP | Asiimov (Battle-Scarred)\t+287%\t$524\t$135\t37\tSkinport CSFloat Steam\nAK-47 | Redline (Minimal Wear)\t+277%\t$562\t$149\t112\tSkinport CSFloat Steam\nAWP | Crakow! (Factory New)\t+275%\t$379\t$101\t72\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Vulcan (Factory New)\t+272%\t$5,275\t$1,418\t12\tSkinport CSFloat Steam\n\nこれは90-における1日の最高値であり、過去最高値ではありません。また、これは1つのマーケットプレイスに限定されたものです。本資料のどこにも、過去最高値に関する記載はありません。Skinportでの販売実績がない商品は、この資料から完全に除外されているため、このセットは調査対象の全数よりも規模が小さくなっています。\n\n検証用リンクは、カタログ独自のプラットフォーム識別子に基づいて生成されます。これらのリンクは、各マーケットプレイスの当該商品ページを指しており、読者は当社ではなく、情報源そのものと照らし合わせて確認することができます。外部リンクには rel=\"nofollow\": これらは引用であり、推奨ではありません。また、掲載されている目的地の中には、本調査が批判の対象としているマーケットプレイスもいくつか含まれています。\n\n09 / 由来と限界\nこれがどこから来たのか、そして何が示せないのか\n\nこのページに掲載されているすべての数値は、各数値の横にハッシュ値が公開されている2つのスナップショットファイルから再計算されたものです。ここに掲載されている内容は、他のサイトの記事から転載したものではありません。\n\n出典およびアクセス方法\n\ncs2.sh API、GET /v1/prices/latest および GET /v1/schema、2026-09-23で取得した単一のスナップショット T00:44:27.871388581Z、価格は米ドル建て。\n\nこのデータは、アーカイブに記載されているGDPRの依頼者が保有する有料の商用サブスクリプションに基づき、プロバイダー独自の利用規約に従って取得されたものです。 いかなるマーケットプレイスからもデータをスクレイピングしておらず、いかなるマーケットプレイスの認証情報も使用していません。 リクエスト元の鍵はこのリポジトリの外に保管されており、このリポジトリ内のどのファイルにも記載されていません。\n\n商品の認定基準\n\nBUFF、CSFloat、Skinport、YouPin、またはC5Gameのいずれかで、少なくとも1件の有効な売注文があるすべての基本アイテムは、その最も安い売注文に基づいて価格帯に分類されるため、その価格帯はSteamには依存しません。「Steamのカバー率」とは、データ取得時点で、その価格帯に含まれるアイテムのうち、有効なSteamの売注文があるアイテムの割合を指します。 パターンおよびフェーズのバリエーションは、Steamで個別にリストされていないため、ラダーからは除外されています。これらを含めると、Steamの数値が過小評価されてしまうからです。レンダリングとは、同じ商品に対するカタログ画像のことで、ローカルに保存されています。\n\nレンダリング画像と画像の権利。カタログ商品のレンダリング画像は、価格行と同じ「market_hash_name」に対して提供されるプロバイダーの画像であり、オフラインおよびIPFSでの表示用にローカルに保存されています。 これらのレンダリング画像はPhishDestroyの著作物ではありません。すべての商品画像、ロゴ、スクリーンショットは、それぞれの所有者（cs2.sh、CSFloat、Skinport、BUFF、YouPin、C5Game、Valveなど）の所有物です。これらは識別および公益的な報道を目的としてのみ複製されており、いかなる所有権やライセンスも主張するものではありません。\n\n入手できなかったもの\n\n利用したサブスクリプション tier では、現在のスナップショットのみが利用可能です。履歴およびアーカイブのエンドポイントは利用できず、 このページのいかなる箇所においても、過去のデータ系列に関する主張は一切行われていません。 「トレーリング・ウィンドウ・セールス」に関する記事 Skinport は、06. のセクションに掲載されています。\n\n単一のスナップショットであり、時系列データではありません。 取得時点でSteamに商品が出品されていないからといって、その商品が今後決して出品されないという証拠にはなりません。それはその時点での棚の状態を示すものであり、上限価格を超える商品については、Valveが公表しているルールでも同様に定められています。Valveのコミュニティマーケットでは、1商品あたりの出品価格を1,800に明示的に制限しています（Steamウォレットの残高上限は2,000です。詳細は Steam コミュニティマーケットに関するよくある質問 アーカイブ済み 2026-09-21 ↗ そして Steam 利用規約 § 3.C アーカイブ 2026-09-24 ↗).\n\n採点\n\n商品の価格は常にその商品の最も安いリアルタイムの売値であるため、高い外れ値によって合計額が水増しされることは決してありません。格付けによって、どの行が相場として提示されるかが決まります。同一商品について、最も安い売値の3倍を超える相場は、リアルタイム価格ではないものとして除外されます。 グレードA：3つ以上のマーケットプレイスが依然として上限を上回る価格を提示しており、その中央値が最安値の25パーセントの範囲内にある場合。グレードB：2つのマーケットプレイスが一致しているか、3つがより緩やかに一致している場合。グレードC：単一の価格帯（市場価格ではなく、売り出し価格）のみが存在する場合。本報告書では、グレードAおよびBのみが引用されています。\n\n外れ値のルール：相場 > 3.0× 同一銘柄の最安売値。\n\n合計値が下限値である理由\n\n各マーケットプレイスにおいて、商品の 最低 「売値」には、シェルフリストに掲載されているコピー数が掛けられます。そこにあるコピーのうち、1つおきにその最低売値以上で価格設定されているため、実際の掲載価格は推定値ではなく、仕組み上必然的に高くなります。これは販売でも、キャッシュフローでも、CS2経済の評価でもありません。\n\nご自身で確認してみてください\n\nこのページのすべてのグラフの基となっている派生データセットは、その全容が公開されています： アトラス・データセット, 格付けおよびアーティファクト画面, 基礎となる国勢調査 そして 各生スナップショットのSHA-256が記載されたマニフェスト.\n\n公開された修正\n\nこの関連登録簿の初期草案では、ある中国のマーケットプレイスで「Souvenir AK-47 | Point Disarray」が$148,954で出品されていたのに対し、Steamでは$119.という価格設定がされていた。この項目はグレードCである：掲載は1件のみ、在庫は1点のみ、かつ他のマーケットプレイスでの価格情報が一致していない。これは「希望価格」であり「実際の価格」ではないため、当サイトおよび当該ページにおいてランクが引き下げられた。 裏付けのある最安値は、Sticker | Titan (Holo) | Katowice 2014 で、 $66,285, 4 による引用によると、これらのマーケットプレイスは 5.2% 内で互いに近接しているが、Steam には全く存在しない。",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "スキン・プライス・ラダー・アトラス — 流動性の崖"
          },
          {
            "level": 2,
            "id": null,
            "text": "崖は「要求」ではなく「規則」に基づいて現れる"
          },
          {
            "level": 3,
            "id": null,
            "text": "その形状から除外されるもの"
          },
          {
            "level": 2,
            "id": null,
            "text": "希望価格は価格そのものではない"
          },
          {
            "level": 3,
            "id": null,
            "text": "A  3つ以上の棚が一致する"
          },
          {
            "level": 3,
            "id": null,
            "text": "B  2つの棚が一致している"
          },
          {
            "level": 3,
            "id": null,
            "text": "C  棚が1つ — 未使用"
          },
          {
            "level": 3,
            "id": null,
            "text": "この是正措置にどれほどのコストがかかり、何をもたらしたのか"
          },
          {
            "level": 3,
            "id": null,
            "text": "「遺物」として区分された出品物"
          },
          {
            "level": 2,
            "id": null,
            "text": "419のすべてのカテゴリと、各価格が対応するオブジェクト"
          },
          {
            "level": 2,
            "id": null,
            "text": "Steamが扱わない商品を並べる棚"
          },
          {
            "level": 2,
            "id": null,
            "text": "実際に供給がどれほど逼迫しているのか"
          },
          {
            "level": 2,
            "id": null,
            "text": "サードパーティ製棚が実際に実現したこと"
          },
          {
            "level": 2,
            "id": null,
            "text": "16年前のステッカーと、一握りの手袋"
          },
          {
            "level": 2,
            "id": null,
            "text": "上値は上場ではなく、取引によって支えられている"
          },
          {
            "level": 3,
            "id": null,
            "text": "当該期間における成約額上位30件"
          },
          {
            "level": 3,
            "id": null,
            "text": "同じ商品、同じ90のセール期間なのに、価格がまったく異なる"
          },
          {
            "level": 2,
            "id": null,
            "text": "これがどこから来たのか、そして何が示せないのか"
          },
          {
            "level": 3,
            "id": null,
            "text": "出典およびアクセス方法"
          },
          {
            "level": 3,
            "id": null,
            "text": "商品の認定基準"
          },
          {
            "level": 3,
            "id": null,
            "text": "入手できなかったもの"
          },
          {
            "level": 3,
            "id": null,
            "text": "採点"
          },
          {
            "level": 3,
            "id": null,
            "text": "合計値が下限値である理由"
          },
          {
            "level": 3,
            "id": null,
            "text": "ご自身で確認してみてください"
          },
          {
            "level": 3,
            "id": null,
            "text": "公開された修正"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/ja/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/ja/skin_atlas#gallery",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://skinport.com/market?search=AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260924114457/https://store.steampowered.com/subscriber_agreement/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-atlas.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-artefact-screen.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-above-the-ceiling.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ja/skin_atlas.content.json",
      "export_json_sha256": "6390200e5797382d45f0aede406023c3bfb38b83b45e6e4cd4492b31d48e17b5"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ja/social_graph.html",
      "language": "ja",
      "title": "記録されたつながりをたどる――『Steam』特集",
      "source_url": "https://phishdestroy.io/steam_dossier/ja/social_graph",
      "source_html_sha256": "feb59dc56bb2564fae31e46fddcdd88e69cfcb206bcca19f7c8119a5bed94ef2",
      "exported_at": "2026-09-29T00:22:18.818Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "social_graph.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ja/social_graph.pdf?v=print-20260929-v5",
        "sha256": "dec06ee8b7675ca3cecbbf709ce771cd28deea72ced9f1cec9d664fa83f66254",
        "bytes": 289670,
        "pages": 6
      },
      "integrity": {
        "signed_object": "social_graph.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "social_graph.content.json.asc",
        "digest_file": "social_graph.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify social_graph.content.json.asc social_graph.content.json",
          "sha256sum -c social_graph.content.json.sha256"
        ]
      },
      "content": {
        "text": "つながりをたどってみてください。各関係性を確認してください。\n\nプロフィールを検索します。関係の種類を選択します。取得したレコード内のそのプロフィールの直接の隣接プロフィールを追跡します。 調査ツール： エッジは、2つのノード間の公的な関係を表すものであり、直接的な接触、非公開の連携、あるいは不正行為の証拠を示すものではありません。3,435-のノードレイアウトは、フィルターを使って閲覧するのが最適です。\n\n一度に一つの関係を探求する\n\n💡 ノードをクリックしてドラッグすると、グラフの配置を変更できます。カーソルを合わせると詳細なプロフィールが表示されます。ティール色の実線＝友達関係、アンバー色の破線＝相互コメント。\n\n関係の種類プロフィールと近隣住民\n\n3,435 プロフィール · 4,551 保存されたリンク\n\nプロフィールを検索して選択するか、ノードをクリックしてください。そのノードの直接の隣接ノードのみが残ります。エッジは関係性を記録するものであり、プライベートな連携を確立するものではありません。\n\n取得したデータセットに含まれるプロファイル\n\nソース表の全文： 3,435の全行をダウンロード（CSV）. 以下の表には、当初は最初の25行が表示されていますが、検索やページネーション機能を使用すれば、データセット全体を確認することができます。\n\n1–25 / 3,435行\nペルソナ名\tSteamID64\tプライバシー\tステータス\tグループの会員資格\t凍結在庫（米ドル）\t場所\nMahatma Gandhi\t76561198333721623\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tPH\nGalley//갤리🌠🌙\t76561198043416832\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tKP\n$Schlächter\t76561198860277343\tPUBLIC\tClean\tsteambans\t$0.00\tUnknown\n❄r3dsn0w000™❄ [Cristi]🎮\t76561197986767957\tPUBLIC\tClean\tCommunityLegends\t$0.00\tRO\n(2a03) Wolfy\t76561197991671851\tPUBLIC\tCommunity\tsr_public\t$0.00\tUS\nZloy2288\t76561198038578334\tPUBLIC\tClean\tsteambans\t$0.00\tBY\njessy\t76561198039125237\tPUBLIC\tCommunity, VAC (1x)\tCommunityLegends\t$0.00\tJP\nJithraRufure\t76561198071896910\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\n| Níllerdínho |\t76561198003487438\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tDK\nJones is back\t76561198023013026\tPRIVATE\tVAC (1x)\tsteambans\t$0.00\tUnknown\nUNEX | ★✠☠ MoH3st ☠✠\t76561198050763123\tPUBLIC\tClean\tsteambans\t$0.00\tDE\nTrojan\t76561198048457084\tPUBLIC\tClean\tCommunityLegends\t$0.00\tDE\n𝗠𝗮𝘆𝘂 ❤\t76561199377967696\tPUBLIC\tClean\tsr_public\t$0.00\tIS\nbig fucking idiot\t76561198871206397\tPUBLIC\tVAC (1x)\tsteambans\t$0.00\tUnknown\nSOFF Games\t76561198227129276\tPUBLIC\tClean\tcommunitymoderators\t$0.00\tRU\nThijminecraft02\t76561198253895669\tPUBLIC\tClean\tSteamIDcouk SArchive\t$0.00\tNL\nStatic-sama\t76561198289329793\tPUBLIC\tClean\tsteambans\t$0.00\tJP\n𝙸mmortal 𝚂targazer\t76561198142116760\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\nCommander Keen\t76561197987773287\tPUBLIC\tClean\tsteambans\t$0.00\tBE\nS1mX\t76561199648509165\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\nmixwell\t76561199276547472\tPUBLIC\tClean\tsr_public\t$0.00\tJP\nP90_GOD_YyEs™\t76561198285821942\tPUBLIC\tClean\tsteambans\t$0.00\tHK\nhewwo?\t76561199133807546\tPUBLIC\tVAC (1x)\tsteambans\t$0.00\tCH\n♕Kamikaze Atze♕\t76561198002700103\tPUBLIC\tClean\tsteambans\t$0.00\tDE\nPastica\t76561198154655970\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tDZ\n記録された友情のつながり\n\nソース表の全文： 4,299の全行をダウンロード（CSV）. 以下の表には、当初は最初の25行が表示されていますが、検索やページネーション機能を使用すれば、データセット全体を確認することができます。\n\n1–25 / 4,299行\nユーザーA\t方向\tユーザーB\t関係タイプ\nMahatma Gandhi\n76561198333721623\t↔\tDeskjet\n76561198272738437\tMutual Friends\nGalley//갤리🌠🌙\n76561198043416832\t↔\tomega\n76561197960274529\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tFisty\n76561198057301486\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tFaalagorn\n76561198001116101\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tMURK\n76561198036995672\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tÅρøᴛʜℯᴛȋᴄÅʟȋℯη ♛👽♛\n76561197984615267\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tsilatrak\n76561197999629462\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tBlack Blade\n76561198083368493\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tAvenger\n76561197978249317\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tRemtar\n76561198124322650\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tCato\n76561197961345984\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t✪ G λ M Ξ ®\n76561197994308495\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tclees42\n76561198030936806\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t𝓜ε𝔰𝔥 | AusLevels\n76561198108828539\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tSgtFopper™\n76561198002555892\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t❥Miss Bee\n76561198046958996\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tTesTy\n76561198032370068\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tskl_andrey\n76561198136881436\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t\"Exekutor\"\n76561198009583947\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tAraripe\n76561198103754372\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tsteve6678\n76561198053200093\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\ttrinner\n76561197970359081\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tSteph S.\n76561198025653291\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tKirito\n76561198154545657\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tDoc. todt\n76561197984492467\tMutual Friends\nコメントの記録へのリンク\n\nソース表の全文： 252の全行をダウンロード（CSV）. 以下の表には、当初は最初の25行が表示されていますが、検索やページネーション機能を使用すれば、データセット全体を確認することができます。\n\n1–25 / 252行\n著者\t方向\t対象プロファイル\t日付\tコメント本文\nDeskjet\n76561198272738437\t→\tMahatma Gandhi\n76561198333721623\t16 September, 2021 @ 11:02:05 pm PDT\t\"𝑵𝒐𝒘 𝒊𝒇 𝑰 𝒇𝒖𝒄𝒌 𝒕𝒉𝒊𝒔 𝒎𝒐𝒅𝒆𝒍𝑨𝒏𝒅 𝒔𝒉𝒆 𝒋𝒖𝒔𝒕 𝒃𝒍𝒆𝒂𝒄𝒉𝒆𝒅 𝒉𝒆𝒓 𝒂𝒔𝒔𝒉𝒐𝒍𝒆𝑨𝒏𝒅 𝑰 𝒈𝒆𝒕 𝒃𝒍𝒆𝒂𝒄𝒉 𝒐𝒏 𝒎𝒚 𝑻-𝒔𝒉𝒊𝒓𝒕𝑰'𝒎𝒎𝒂 𝒇𝒆𝒆𝒍 𝒍𝒊𝒌𝒆 𝒂𝒏 𝒂𝒔𝒔𝒉𝒐𝒍𝒆\" - Nelson Mandela\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t22 November, 2021 @ 4:10:28 pm PDT\thttps://anige.horigiri.net/?cat=22\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t18 November, 2021 @ 12:45:26 am PDT\thttps://gamerch.com/umamusume/entry/250411\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t8 August, 2021 @ 4:13:25 am PDT\thttps://modoocode.com/304\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t6 February, 2021 @ 3:35:05 pm PDT\t▤ ∫︹- -ω⁾ ⁽︹▓▓︺\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t11 December, 2019 @ 1:50:53 am PDT\thttps://blog.naver.com/aksenwlddj12/221369410039\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t2 October, 2019 @ 7:11:59 am PDT\tǤαllєу║︎갤리..۩\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t9 April, 2019 @ 12:51:28 pm PDT\tExplosiveDamage(owner, from, maxrange, minrange, distmultiplier, dmgmultiplier, mindamage, typ, damagetype, ignore)\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 12:22:47 pm PDT\tinfo - sh_titles.lua\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 12:21:46 pm PDT\tlocal nibbas = 1344 init.lua\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 11:31:58 am PDT\thttp://foreign.aladin.co.kr/shop/wproduct.aspx?ItemId=123955531&start=slayer\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t3 April, 2019 @ 1:26:41 am PDT\tǤαllєу\nLei\n76561198982197954\t→\tJithraRufure\n76561198071896910\t29 December, 2024 @ 12:58:08 pm PDT\t+rep he knows how 2 rush B ￣ヘ￣\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t2 September, 2026 @ 5:16:55 am PDT\tlol\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t20 August, 2026 @ 6:11:03 am PDT\t?\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t25 July, 2026 @ 7:20:05 am PDT\thahahahaha\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t30 June, 2026 @ 12:52:42 pm PDT\twow\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t30 June, 2026 @ 12:41:32 pm PDT\txD\nvalorant enjoyer\n76561199112142402\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:26:30 pm PDT\toh no!!\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:26:11 pm PDT\toh no!!\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:22:22 pm PDT\tomg !!! they know my secret, omg!!!\nvalorant enjoyer\n76561199112142402\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:21:39 pm PDT\t+rep good ♥♥♥♥♥ player\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:20:50 pm PDT\tomg! u cant cheat on secure gaben servers, omg dont report me, they ban me for boosted omg\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 8:37:11 pm PDT\txD\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t28 June, 2026 @ 1:58:14 pm PDT\twow",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "つながりをたどってみてください。各関係性を確認してください。"
          },
          {
            "level": 2,
            "id": null,
            "text": "一度に一つの関係を探求する"
          },
          {
            "level": 2,
            "id": null,
            "text": "取得したデータセットに含まれるプロファイル"
          },
          {
            "level": 2,
            "id": null,
            "text": "記録された友情のつながり"
          },
          {
            "level": 2,
            "id": null,
            "text": "コメントの記録へのリンク"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-profiles.csv",
          "https://steamcommunity.com/profiles/76561198333721623",
          "https://steamcommunity.com/profiles/76561198043416832",
          "https://steamcommunity.com/profiles/76561198860277343",
          "https://steamcommunity.com/profiles/76561197986767957",
          "https://steamcommunity.com/profiles/76561197991671851",
          "https://steamcommunity.com/profiles/76561198038578334",
          "https://steamcommunity.com/profiles/76561198039125237",
          "https://steamcommunity.com/profiles/76561198071896910",
          "https://steamcommunity.com/profiles/76561198003487438",
          "https://steamcommunity.com/profiles/76561198023013026",
          "https://steamcommunity.com/profiles/76561198050763123",
          "https://steamcommunity.com/profiles/76561198048457084",
          "https://steamcommunity.com/profiles/76561199377967696",
          "https://steamcommunity.com/profiles/76561198871206397",
          "https://steamcommunity.com/profiles/76561198227129276",
          "https://steamcommunity.com/profiles/76561198253895669",
          "https://steamcommunity.com/profiles/76561198289329793",
          "https://steamcommunity.com/profiles/76561198142116760",
          "https://steamcommunity.com/profiles/76561197987773287",
          "https://steamcommunity.com/profiles/76561199648509165",
          "https://steamcommunity.com/profiles/76561199276547472",
          "https://steamcommunity.com/profiles/76561198285821942",
          "https://steamcommunity.com/profiles/76561199133807546",
          "https://steamcommunity.com/profiles/76561198002700103",
          "https://steamcommunity.com/profiles/76561198154655970",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-connections.csv",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-comments.csv"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ja/social_graph.content.json",
      "export_json_sha256": "57b10fd05086bb657d4a77f624c6ffdf4cf64eb3515f306d71d23bc7f8cefa01"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ja/steam_enforcement_evidence.html",
      "language": "ja",
      "title": "「ルール」対「対応」――『Steam』特集",
      "source_url": "https://phishdestroy.io/steam_dossier/ja/steam_enforcement_evidence",
      "source_html_sha256": "baa740509b33c295e9f71f0d2b974fd55128eb2a49671eaee1c69244268421a7",
      "exported_at": "2026-09-29T00:22:20.176Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "steam_enforcement_evidence.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ja/steam_enforcement_evidence.pdf?v=print-20260929-v5",
        "sha256": "8a564cd82771b2d6b6511a638227405b891d9471536182a2d3f1eedfcb21a1e8",
        "bytes": 564452,
        "pages": 36
      },
      "integrity": {
        "signed_object": "steam_enforcement_evidence.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "steam_enforcement_evidence.content.json.asc",
        "digest_file": "steam_enforcement_evidence.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify steam_enforcement_evidence.content.json.asc steam_enforcement_evidence.content.json",
          "sha256sum -c steam_enforcement_evidence.content.json.sha256"
        ]
      },
      "content": {
        "text": "証拠の補足資料／出典リンク付き記録\nSteam 執行証拠 — 裏付け記録および開発者ネットワーク\n\nルール。 回答。\n\nこのセクションが証明すること\n\nこの証拠資料室では、Valveの公式「利用規約」と、日付入りの執行ログ、サポート紛争解決記録、および252のリポジトリや3,320のプロフィールにわたる開発者ネットワークの記録とを比較しています。これにより、一般のアカウント保有者はセッションの侵害が発生すると反論の余地のない執行措置やサポートの停止に直面する一方で、大規模な商用ボット運用はパブリックインフラへのアクセスを維持したまま継続的に稼働している実態が明らかになっています。\n\n← エグゼクティブ・ブリーフィングに戻る\n\n書面による制限事項をお読みください。記録された回答を開いてください。情報源に記載されている内容と、未回答の項目とを比較してください。\n\n支援と訴え ↓公共インフラ ↓\n252リポジトリの記録\n3,320公開プロフィール\n4,214異なるプロファイルとリポジトリの組み合わせ\n98,902共有リポジトリを持つプロファイルのペア\n01 / 支援、制裁、および復興\n訴状をお読みください。ソースを添付したままにしておいてください。\n支援拒否ギャラリー（981の展示） ↗選択したレコードをダウンロード ↓\nHFB / アウトソーシング事例広く認められている妥協案。\n報道された解雇について。\n\n転載されたサポートの回答と、請負業者のスタッフに関する主張の出典を確認してください。\n\nケースとその出典を開く →\n\n以下：保存されている5点 Redditの公開投稿 提供されたサポート記録集から。各記録は、Valveのサポートシステムへの問い合わせを記録したもので、元のソースリンク、キャプチャ位置、および全文がそのまま保存されています。これらは被害者の証言です。これらの証言を裏付ける、あるいは反証するであろう認証済みのサポートログは、Valveが保有しており、公開されていません。\n\n01\nBan & review2024-12-09\nPermanent sanction & closed appeals\n\nThe author reports a permanent account ban, repeated ticket closures and a planned GDPR access request.\n\nREDDIT / PUBLIC TESTIMONYr/ohnePixelCapture record 294\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 303 words\nPermanently banned Steam account without a clear explanation, need help!\n\nsteam_support_tickets_MEGA.json / record 294\n\nHey everyone,\n\nI’m in a really frustrating situation, and I’m hoping someone here can help me or offer advice. My Steam account was just permanently banned for allegedly violating the Steam Subscriber Agreement, and I have no idea why.\n\n# What Steam Support told me:\n\nThe support message said my account was banned due to:\n\n* Suspicious activities related to transferring or attempting to sell/trade the account.\n* Community reports and other unspecified factors.\n\nThey added that the ban is permanent and that they can't help me further. They also warned that future support requests regarding this ban might be ignored. 😞\n\n# Why I’m contesting this ban:\n\n* I have never sold, traded, or transferred my account. I’ve been the legitimate owner since the beginning.\n* On the day the ban occurred, I did nothing noteworthy that could have triggered such a sanction.\n* I received no prior warning, which feels incredibly unfair.\n\n# What I’ve tried so far:\n\n* Contacting Steam Support: I explained my situation and asked for more details, but they’re sticking to their decision and closing my tickets.\n* I’m preparing a request based on my Right of Access (GDPR) to get all the data related to my account.\n\n# Questions for the community:\n\n1. Has anyone successfully had a permanent ban lifted on Steam?\n2. Are there steps I can take to prove I’m the legitimate owner of the account?\n3. Any advice on how to word my request to convince support to reconsider my case?\n4. Would it be helpful to contact the CNIL (I’m based in France) to force Steam to provide more information?\n\nI’m really desperate at the thought of losing all my games, purchases, and years of playtime. Thanks in advance for any help and advice you can give!\n\nhttps://preview.redd.it/jk9qv0gmhv5e1.png?width=1289&amp;format=png&amp;auto=webp&amp;s=b3a333ebb08ea133e2c8747ba126f5a68283d9f7\n\nhttps://preview.redd.it/4sopt0gmhv5e1.png?width=1022&amp;format=png&amp;auto=webp&amp;s=56195d5336118faf9413f1514ead7e8d24c788c3\n\nhttps://preview.redd.it/eqrxw0gmhv5e1.png?width=996&amp;format=png&amp;auto=webp&amp;s=ff3539d28ab754e513ad471822c5de652920101d\n\nhttps://preview.redd.it/728xz0gmhv5e1.png?width=1034&amp;format=png&amp;auto=webp&amp;s=bc5335673509929669af785aa244bf8d2dc58da8\n\n02\nSupport access2025-05-09\nAccount recovery & a reported $10,000 loss\n\nThe author alleges that support reset credentials and removed account protection following another person’s recovery ticket.\n\nREDDIT / PUBLIC TESTIMONYr/legaladviceCapture record 110\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 193 words\nGot $10k stollen from steam inventory due to steam' support fault.\n\nsteam_support_tickets_MEGA.json / record 110\n\nLocation: Quebec, Canada.\n\nLast year, someone hacked my Steam account and stole items worth about $10,000 USD. I only noticed this last week. When I talked to Steam Support, they admitted that someone submitted a ticket to make changes on the account and Steam Support reset my password and turned off all my account security.\n\nI asked Steam Support about getting my items back, but they said there was nothing they could do. They told me I should follow their security recommendations.\n\nThe problem is, I did everything they \"suggested\" to protect an account:\n\n* I had two-factor authentication.\n* My phone number was connected to my account.\n* I used Steam Guard.\n* I printed recovery codes and kept them in a safe.\n\nEven though I did all these things, Steam Support still gave someone else access to my account. The stolen items had been in my account since around 2016-2017. Also, I had not logged in for a few years, so I didn’t accidentally give my information to a fake website.\n\nIs there anything I can do, or do I just have to accept losing $10,000 USD?\n\nThanks for your help.\n03\nRestoration2022-07-07\nA reported $500+ loss & template replies\n\nThe author describes an account compromise, disputed transactions and a support response that allegedly did not address the submitted evidence.\n\nREDDIT / PUBLIC TESTIMONYr/DotA2Capture record 45\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 410 words\nFunds stolen through steam market. Disappointed with Steam response.(or lackthereof)\n\nsteam_support_tickets_MEGA.json / record 45\n\nOn 6th July 2022, 44 unauthorized transactions were made on the steam market using my steam wallet funds totalling roughly $500+ USD to buy worthless 1 cent Dota 2 items. This happened during the wee hours in the morning and i contacted them first thing when i woke up. \n\nI have 2FA enabled all the time, and always thought this would not happen to me as I do not go on betting sites/click sketchy links. My account password + emails were not changed, nor did they take my inventory, just that my funds were used illicitly. Also when I went to disable other APIs, it says there are no other APIs to disable. Shows that it wasn't through me clicking sketchy links and leaving my account details there. Would have lost the whole account if i did so.\n\nWhat baffles me is how did they bypass my 2FA to login my account? Why doesn't steam market purchases go through 2FA as well? First time in 9 years that this happened to me. My acc was logged in 'BY' 'Vitebsk' during the illicit purchases but I'm based in Asia I gathered all the screenshots and provided in the ticket to steam support. \n\nAll i got was the standard copy paste template reply by Steam Support. Lost $500+ and was not even worthy of having a proper person to look into this. I dont think they even read or take a look at the screenshots cause if they did, they would have come to the realization that what happened was clearly fraud, and with a few clicks, reverse the unauthorized transactions, refund my wallet and ban the hijacker. \n\nOver the years, i've spent quite a fair bit on steam but really, this is the kind of recourse we get when our account is compromised? They just don’t care, sigh. I only expect the bare minimum from Steam and looks like even that is quite far-fetched.\n\nSS: https://imgur.com/a/67frcls \n\nHijacker: https://steamcommunity.com/profiles/76561199141246495\n\nSteam Response: https://imgur.com/a/V6v4maM\n\nI could think of a few ways on how to Improve:\n\n1) Add 2FA to market transactions. (even if its bulk posting or selling of items, just 1 2FA notif is required)\n\n2) Enable accounts to be region locked. (if you are migrating, then have to go through steam support etc)\n\n3) Additional Lock on Steam Wallet. (Another password perhaps?)\n\nEDIT: 2nd ticket in and I have still yet to receive a non robotic copy paste template response from Steam.\n04\nRestoration2021-11-29\nSteam Guard & an item-restoration refusal\n\nA preserved post includes the author’s account of item theft and a support response declining restoration.\n\nREDDIT / PUBLIC TESTIMONYr/DotA2Capture record 58\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 563 words\nMany people are losing item via clicking links where steam guard is enabled and steam support doesn't not restore items.\n\nsteam_support_tickets_MEGA.json / record 58\n\nAccounts are getting compromised and might be their pc as well where Steam market is targeted hence the malicious links . I am assuming these hackers are getting encouraged where steam support is not doing nothing and they are getting away with hacking items.  \nLiterally the guy who is supporting the game which he doesn't get any in game advantage just  cosmetics in game only for the sole purpose of supporting the game so that the game will prosper and become beautiful way  to enjoy weekend. But right now players are getting hacked left right and center and steam support  is copy pasting message where in short they are blaming the guy who clicked link. 1st this is happening because they are not targeting players but they are targeting market since they are selling those stuff for real cash via party website. Steam is a huge company and can eradicate the problem or at least can remove links temporarily  in chat since hackers are targeting .They made us install steam guard by saying we wont help if there is no steam guard now steam guard is not enough to save our inventory now they changed their policy  that they should not click any suspicious links. How would we know if the link is suspicious ? After clicking and getting our inventory stolen right !   \n\"we'd have to duplicate an item to restore it. Duplication lowers the value of all items by reducing their scarcity and inflating the economy, which affects everyone involved in trading and the Market. To maintain the value of everyone’s inventory, we do not restore items. For more information, please see the Steam Item Restoration Policy.\"  \nThey care for millions of people IN STEAM MARKET where as few  are losing items which is going to affect market where the rightful owner bought the items and hacker is going to sell the item via 3rd party website and enjoy ! HOW IRONIC !!  \nThis is the message from support where my frnd got his items stolen via clicking on link  \n   \nHi there,  \n\nThank you for the information and screenshots provided.  \n\nIt appears that the account was compromised, please take the following steps to secure your account and computer:  \n\nScan your computer for viruses, key loggers, spyware, and other malicious code using antivirus software with updated virus definitions.  \nChange the password for the email address that is associated with your Steam account.  \nRegularly reset your Steam account password.  \n\nPlease see our Security Recommendations article.  \n\nIn addition, I’m sorry to hear that your items were removed without your permission. Unfortunately, Steam Support does not restore scammed, lost, or stolen items for any reason.  \n\nSince Steam Support does not remove items from accounts, we'd have to duplicate an item to restore it. Duplication lowers the value of all items by reducing their scarcity and inflating the economy, which affects everyone involved in trading and the Market. To maintain the value of everyone’s inventory, we do not restore items. For more information, please see the Steam Item Restoration Policy.  \n\nTo make sure that a scammer is reported, please report them through the Steam Community. Reporting a scammer through the Steam Community is the best way to prevent them from committing future scams.  \n\nTo learn how to avoid scams or hijackings, please see our Trade Scam article.  \n\nIf you still need assistance, please let us know.\n05\nEnforcement2025-05-11\nSelective enforcement & an unexplained ban\n\nA community member describes a disputed ban and contrasts it with the visibility of commercial gambling promotion.\n\nREDDIT / PUBLIC TESTIMONYr/SteamUncensoredCapture record 107\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 1,208 words\n🚨 Steam Bans Without Reason and Ignores Its Community — What’s Going On?\n\nsteam_support_tickets_MEGA.json / record 107\n\nHey r/Steam,\n\nI’m writing this to share my thoughts and concerns about my friend [moneylead](https://steamcommunity.com/id/moneylead/) and Steam’s policies in general. I spoke with him yesterday about his situation, though I didn’t discuss writing this post with him—I asked last night, but he hasn’t responded yet. I want to highlight that this issue is broader than just his case, and while Steam might make changes in the future (though that’s unlikely), I feel the community needs to understand how far Steam has strayed from its original values. I’m not trying to put moneylead in a tough spot with this thread—all the info I’m sharing is public, nothing secretive. I hope he won’t be upset with me, but the community needs this case to see the bigger picture and how Steam feels completely unaccountable.\n\n**Why Does Steam Ignore Its Community?**  \nWhy does a platform like **Roblox** provide a detailed log of ban reasons, while Steam, which claims to be \"community-driven,\" ignores its community, bans whoever they want, for whatever they want, with no transparency? I looked into Roblox as a popular game—not a direct competitor to Steam—to see how their bans look, and you can check it out yourself: [Roblox Ban Reasons](https://www.google.com/search?q=Roblox+ban). Their bans are clear, detailed, and actually explain what you did wrong. I think most decent gaming communities operate like this—not with support agents named Olga, hired through outsourcing, who only know how to send canned auto-replies. Take cases like St4ck—or my friend **moneylead**. All these unbans, like **St4ck’s** or **Alexanddd’s**, happened behind closed doors with zero comments from Steam. Of course, it’s convenient for Steam to handle everything in secret, so no one knows or sees what’s going on—but this violates Steam’s own community rules and principles.\n\n**Who Is moneylead?**  \nI’ve known [moneylead ](https://steamcommunity.com/id/moneylead/)since around 2021. We played Dota 2 a couple of times, and then I just stayed on his friends list. He’s always been a legit player, bringing revenue to Steam through purchases. He never sold his skins, whether in **Dota or CS2—he wasn’t a trader**. All he did was:\n\n* Buy games and skins.\n* Collect badges to level up his profile.\n\nAccording to [SteamSets](https://steamsets.com/account/76561199080934614), he’s given out 324,000 Steam Points—I think he awarded profile rewards to all his friends in the list (though I’m not 100% sure). I do know he ran contests and gave gifts to friends, always supporting the community.\n\n**Steam’s Unfair Treatment**  \nI’ve seen Steam remove his showcases, avatar, description, and even his country multiple times—just because he’s from **Ukraine**. He has a ton of haters leaving toxic comments on his wall, and Steam seems to favor **Russian** users. Every time he tried to appeal the removal of his showcases or profile description—which didn’t break any rules, just had his Instagram link, and his avatar is the same as it is now—Steam moderators didn’t care. **They don’t care about top players who bring them massive revenue, nor about regular users.**\n\n>*Here’s the worst part: moneylead works in cybersecurity, specifically fighting account theft and phishing. He’s neutralized over 5,000 threats targeting Steam alone. And yet, Steam bans him for \"account hijacking\"?*\n\nIf you roughly calculate moneylead’s contribution to Steam and the community—his profile, level, badges (not skins, you can’t sell those)—is this normal, Steam? Banning people, closing tickets, and ignoring users with a spotless reputation who aren’t involved in any commercial activity, just bringing you profit without taking anything in return?\n\n**Steam’s Double Standards**  \nI’m honestly shocked:\n\n* YouTubers who promote casinos and skin gambling? Steam’s fine with that.\n* A cybersecurity expert who fights scams, doesn’t promote casinos, and openly talks about it on his profile? **Banned with no explanation, ignored, and denied an unban.**\n\nI wonder if Steam deliberately bans a high-level account once a year just because of their impunity—maybe for hype or something. Otherwise, this is just madness. It’s scary to think how many regular players have lost their accounts and skins—not because of scammers, but because of Steam’s desire to ignore, send auto-replies, and do whatever they want.\n\n**How Many Others Are Affected?**  \nHow many others are out there—maybe not as well-known—who just have a few games or skins, get banned for nothing, and receive zero explanation or response? **Is this even legal?** Every other platform provides a detailed log with specific violations, but Steam slaps on the same vague label and sends templated responses.\n\n* How safe is it to buy skins on Steam?\n* What’s the chance Steam will just ban your account for no reason, with no explanation?\n\n**A Message to Valve**  \nI wish moneylead the best in resolving this, but Valve, it’d be great if you remembered what \"community\" means and started following the law. Because right now, it looks like your 30% commission, impunity, and sense of being above the law in the U.S. have given you the idea that you can do whatever you want.\n\nI’m sure there are many others like moneylead and St4ck—people who aren’t public or don’t have the resources to fight back. Let’s unite these cases. **If you’re a U.S. resident who’s been banned by Steam without reason and wants to challenge it, please reach out to me.** I’m finishing my **Juris Doctor (J.D.) program at SMU Dedman School of Law** in Dallas, Texas, and I’m participating in a legal clinical practice under Rule 13 of the Texas Supreme Court.\n\nWhat Steam is doing is absolutely disgusting and illegal, and **I’d be happy to help any gamer (legitimate, with no real violations) who has games or skins with value. This will be beneficial for my practice, and it’s time to put Steam in its place and show them they can’t just dictate their own rules with arbitration**. Let’s take it all the way—not for punishment, but for the sake of the community. Maybe if Steam loses a case, they’ll change their policies and start explaining their actions like most popular gaming communities do. Many of us remember how Steam Support used to recover stolen accounts and ended up “stealing” skins themselves—banning without real reasons is basically the same thing, and that’s a serious accusation.\n\nSo, r/Steam, see you soon. I think you understand what you’re doing and how many people you’ve illegally deprived of their assets. I want to raise this issue—not just for the U.S., but for the entire world. You’ve banned class-action lawsuits? **Welcome to Texas.** I recommend starting to look for licensed attorneys in Texas, because I’d love to discuss your company’s policies, feedback, and support agents named Olga—a name that strongly associates with Russian users. Maybe it’d be easier to move your company to Moscow? But I’d be happy to discuss these critical issues on behalf of the global gaming community.\n\nAlso, I wouldn’t recommend ignoring the lawsuit request that will be sent to your physical address and email address, as the court will proceed without you, and that might upset you—especially since things aren’t going so well for a company with stocks like yours.\n\n**Thanks to everyone who took the time to read this. For those who need real help with an unjust Steam ban without any explanation, I’d be happy to assist. For users from Texas, we can easily file a collective lawsuit against Steam—let’s connect and make it happen.**\n02 / Steam 開発ネットワーク\n公共インフラ。大規模に収録されました。\n「252」の全楽曲をダウンロード ↓\n\n付属の output_steam_network スナップショットは、リポジトリ、公開された貢献者・フォークの関係、およびプロフィールの重複を記録します。これらは公開された記録であり、何が構築され、誰が貢献し、何がフォークされたかといった情報を示しています。公開された機能に関するこうした記録の痕跡こそが、Valveが考慮しなければならないものです。\n\nリポジトリ / 説明\t寄稿者\tフォークス\t登録済みプロフィール\nalliedmodders/amxmodx\n\nAMX Mod X - Half-Life 1 Scripting and Administration\n\n\t40\t40\t80\nalliedmodders/sourcemod\n\nSourceMod - Source Engine Scripting and Administration\n\n\t40\t40\t80\nDoctorMcKay/node-steam-user\n\nAllows interaction with the Steam network via the Steam client protocol\n\n\t40\t40\t80\nFacepunch/Facepunch.Steamworks\n\nAnother fucking c# Steamworks implementation\n\n\t40\t40\t80\nJustArchiNET/ArchiSteamFarm\n\nC# application with primary purpose of farming Steam cards from multiple accounts simultaneously.\n\n\t40\t40\t80\nodota/core\n\nOpenDota: Open source Dota 2 data platform with automated replay parsing\n\n\t40\t40\t80\nodota/dotaconstants\n\ndotaconstants: Static data for Dota applications\n\n\t40\t40\t80\nodota/web\n\nOpenDota: React web UI for Dota 2 statistics using the OpenDota platform\n\n\t40\t40\t80\nsplewis/get5\n\nCS:GO Sourcemod plugin for competitive matches/scrims\n\n\t40\t40\t80\nSteamDatabase/FileDetectionRuleSets\n\n🔎 Rules to detect game engines and other technologies based on Steam depot file lists\n\n\t40\t40\t80\nSteamRE/SteamKit\n\nSteamKit2 is a .NET library designed to interoperate with Valve's Steam network. It aims to provide a simple, yet extensible, interface to perform various actions on the network.\n\n\t40\t40\t80\nValveSoftware/dxvk\n\ndxvk tree containing branches used by Proton\n\n\t40\t40\t80\nValveSoftware/GameNetworkingSockets\n\nReliable & unreliable messages over UDP. Robust message fragmentation & reassembly. P2P networking / NAT traversal. Encryption.\n\n\t40\t40\t80\nValveSoftware/gamescope\n\nSteamOS session compositing window manager\n\n\t40\t40\t80\nValveSoftware/Proton\n\nCompatibility tool for Steam Play based on Wine and additional components\n\n\t40\t40\t80\nValveSoftware/source-sdk-2013\n\nThe 2013 edition of the Source SDK\n\n\t40\t40\t80\nValveSoftware/wine\n\nWine with a bit of extra spice\n\n\t40\t40\t80\nValveSoftware/steam-devices\n\nList of devices Steam and SteamVR will want read/write permissions on, to help downstream distributions create udev rules/etc\n\n\t39\t40\t79\nValveSoftware/steam-audio\n\nSteam Audio\n\n\t38\t40\t78\nalliedmodders/metamod-source\n\nMetamod:Source - C++ Plugin Environment and Detour Library for the Source Engine\n\n\t37\t40\t77\nalliedmodders/sourcepawn\n\nA small, statically typed scripting language.\n\n\t35\t40\t75\nValveSoftware/Fossilize\n\nA serialization format for various persistent Vulkan object types.\n\n\t31\t40\t71\nrlabrecque/Steamworks.NET\n\nSteamworks wrapper for Unity / C#\n\n\t27\t40\t67\nModDota/moddota.github.io\n\nModDota github pages project.\n\n\t26\t40\t66\nodota/parser\n\nReplay parse server generating JSON log events from Dota 2 replay files\n\n\t26\t40\t66\nValveSoftware/steam-for-linux\n\nIssue tracking for the Steam for Linux beta client\n\n\t26\t40\t66\nSteamRE/DepotDownloader\n\nSteam depot downloader utilizing the SteamKit2 library.\n\n\t24\t40\t64\nJustArchiNET/ASF-ui\n\nThe official web interface for ASF\n\n\t23\t40\t63\nadvancedfx/advancedfx\n\nHalf-Life Advanced Effects (HLAE) is a tool to enrich content creation mainly for the Counter-Strike series.\n\n\t22\t40\t62\nalliedmodders/ambuild\n\nAlliedModders C++ Build System\n\n\t23\t39\t62\nSteamDatabase/BrowserExtension\n\n💻 SteamDB's extension for Steam websites\n\n\t21\t40\t61\nodota/mobile\n\nReact Native apps for viewing Dota 2 data on Android/iOS\n\n\t19\t40\t59\nValvePython/steam\n\n☁️ Python package for interacting with Steam\n\n\t18\t40\t58\nskadistats/clarity\n\nComically fast Dota 2, CSGO, CS2 and Deadlock replay parser written in Java.\n\n\t13\t40\t53\nSteamRE/open-steamworks\n\nOpen Steamworks is a set of reverse engineered headers for the Valve's Steam Client. More or less abandoned now that the Steamworks SDK is publically available.\n\n\t13\t40\t53\nValveSoftware/Source-1-Games\n\nSource 1 based games such as TF2 and Counter-Strike: Source\n\n\t13\t40\t53\nalliedmodders/hl2sdk\n\nHalf-Life 2 SDK Mirrors\n\n\t11\t40\t51\nSteamDatabase/steamdb.info-issues\n\n🚱 Issue tracker for the SteamDB website\n\n\t11\t40\t51\nCSGOFloat/inspect\n\nSource Code that Powers the CSFloat Inspect Link API\n\n\t10\t40\t50\nValveSoftware/SteamOS\n\nSteamOS community tracker\n\n\t10\t40\t50\nalliedmodders/source2mod\n\nExperimental\n\n\t40\t9\t49\nsmiley/steamapi\n\nAn unofficial object-oriented Python library for accessing the Steam Web API.\n\n\t9\t40\t49\nSteamDatabase/GameTracking\n\n🛢 Dumping things, so you don't have to\n\n\t8\t40\t48\nValveSoftware/counter-strike_rules_and_regs\n\nCS:GO\n\n\t7\t40\t47\nValveSoftware/openvr\n\nOpenVR SDK\n\n\t6\t40\t46\nSteamDatabase/easy-markdown-editor\n\nEasyMDE: A simple, beautiful, and embeddable JavaScript Markdown editor. Delightful editing for beginners and experts alike. Features built-in autosaving and spell checking.\n\n\t40\t4\t44\nValveSoftware/Dota-2\n\nTracker for issues specific to Linux and Mac in the Reborn client. If you have a general issue or non-system-specific feature request please go to dev.dota2.com\n\n\t6\t38\t44\nValveSoftware/Dota2-Gameplay\n\nPublic Bug Tracker for Dota 2\n\n\t4\t40\t44\nJustArchiNET/ArchiBot\n\nNo description in the capture.\n\n\t16\t27\t43\nztizzlegaming/CSGOWinBig\n\nOpen-source Counter-Strike: Global Offensive jackpot betting website.\n\n\t1\t40\t41\nJustArchiNET/mantis.justarchi.net\n\nMantis Bug Tracker (MantisBT)\n\n\t40\t0\t40\nodota/node-steam-user\n\nAllows interaction with the Steam network via the Steam client protocol\n\n\t40\t0\t40\nModDota/TypeScriptAddonTemplate\n\nDota 2 addon template with TypeScript Panorama and VScripts.\n\n\t9\t29\t38\nValvePython/vdf\n\n📜 Package for working with Valve's text and binary KeyValue format\n\n\t6\t32\t38\nalliedmodders/amtl\n\nAlliedModders C++ Template Library\n\n\t17\t19\t36\nValvePython/dota2\n\n🐸 Python package for interacting with Dota 2 Game Coordinator\n\n\t5\t30\t35\nalliedmodders/stripper-source\n\nStripper:Source\n\n\t13\t21\t34\nAllyans3/steam-market-api-v2\n\nSteam Market API v2 package\n\n\t3\t31\t34\nModDota/dota-tutorial\n\nCustom game DOTA tutorial.\n\n\t11\t23\t34\nodota/blog\n\nNo description in the capture.\n\n\t29\t3\t32\nOpsecGuy/BetterGo\n\nExternal CS:GO cheat written in python.\n\n\t1\t27\t28\npxvr-official/1\n\n無許諾配信 企業理念剽窃 動物の森収益化 大神ミオ権利者削除 戌神権利侵害発言 常闇トワ炎上 夜空メルストーカー被害 建築王サポーター放置 赤十字マーク 魔乃アロエ卒業 一つの中國支持声明 大空昴3Dライブ 無限延期清掃員職業差別 日清コラボ楽曲 musedash非公開 rog案件取り消し 壁画ライブ 丁真 Ding Zhen 郑爽 Zheng Shuang 防护林 与朵小天使w 伊月猫凛 本主萌埋午休傻 汪峰 重生细胞 壁纸 比利海灵顿 香蕉君 van 田所浩二 抽象带篮子 抗压背锅吧 季子越 蒋明辉 傻逼…\n\n\t0\t28\t28\nRevadike/InternalSteamWebAPI\n\nDocumenting the unofficial and internal Steam Web API\n\n\t1\t27\t28\nJoeSzymkowiczFiveM/qb-lootcrate\n\nA CSGO-style case opening script\n\n\t2\t25\t27\nAbrarKL/MyRoulette.XYZ\n\nCSGO / Steam Roulette Site created with PHP and Node JS, using the Material Design front-end framework.\n\n\t1\t25\t26\nJustArchiNET/ASF-WebConfigGenerator\n\nNo description in the capture.\n\n\t10\t15\t25\nModDota/dota-data\n\nAuto-generated Dota 2 resource dumps\n\n\t11\t14\t25\nModDota/TypeScriptDeclarations\n\nTypeScript declarations for Dota 2.\n\n\t11\t14\t25\nModDota/API\n\nNo description in the capture.\n\n\t12\t12\t24\nalliedmodders/cssdm\n\nCounter-Strike:Source Deathmatch\n\n\t10\t13\t23\nSteamDatabase/steamstat.us\n\n✅ Front-end of Steam services status website\n\n\t4\t18\t22\nc0deina/csgojackpotV2\n\nCSGO Jackpot Source\n\n\t1\t20\t21\nValvePython/steamctl\n\n🤸 Take control of Steam from your terminal\n\n\t2\t19\t21\nValvePython/csgo\n\n🔫 Python package for interacting with CS:GO Game Coordinator\n\n\t3\t17\t20\nBeepIsla/csgo-crash-exploit\n\nAllows you to crash any Windows user\n\n\t3\t16\t19\nValvePython/vpk\n\n📦 Open, Search, Extract and Create VPKs in python\n\n\t4\t15\t19\nalliedmodders/SM-SteamWorks\n\nExposing SteamWorks functions to SourcePawn.\n\n\t14\t3\t17\nSteamRE/Steam4NET\n\nSteam4NET is a .NET wrapper around the Steamworks C++ interfaces\n\n\t2\t15\t17\nalliedmodders/hl2sdk-manifests\n\nInformation about HL2SDKs shared between Metamod:Source and SourceMod.\n\n\t6\t10\t16\nJustArchiNET/ASF-PluginTemplate\n\nTemplate repository that you can use for creating custom plugins for ArchiSteamFarm.\n\n\t8\t7\t15\nModDota/Dota2AIFramework\n\nGeneral Framework for Dota 2 AI Competitions\n\n\t1\t14\t15\nShkyyl/KeyChamp\n\nExtension for joining free case battle on key-drop automatically\n\n\t1\t14\t15\nSteamDatabase/SteamMonitor\n\n😤 Track Steam's connection manager servers status\n\n\t2\t12\t14\nBaterka/cslore.com\n\nCS:GO gambling site - csgo.style\n\n\t1\t12\t13\nSteamDatabase/SteamTokenDumper\n\n🔢 Submit users' PICS access tokens to SteamDB\n\n\t2\t11\t13\nmonoblocker/roulette\n\nRoulette CS:GO made in React and Typescript\n\n\t1\t11\t12\nzsith/launcher.user.js\n\n// ==UserScript== // @name AposLauncher // @namespace AposLauncher // @include http://agar.io/* // @version 3.062 // @grant none // @author http://www.twitch.tv/apostolique // ==/UserScript== var aposLauncherVersion = 3.062; Nu…\n\n\t1\t11\t12\nLincolnIT/CSGODouble-bot-automated\n\nCSGODouble Automated, auto Betting Bot.\n\n\t1\t10\t11\nvladpuz/steam-market\n\nSteam market API client\n\n\t4\t7\t11\nmcgrizzz/Cstrike.bet\n\nCSGO Roulette Website Angular frontend, nodejs backend, and steam trading bots\n\n\t1\t9\t10\nodota/underlords-web\n\nUI for OpenUnderlords\n\n\t5\t5\t10\nSteamDatabase/SteamToTwitter\n\n🕊 Tweets announcements from various Steam groups\n\n\t1\t9\t10\nModDota/AbilityLuaSpellLibrary\n\nThe successor to the Spell Library by Pizzalol\n\n\t4\t4\t8\nalvinl/bitskins\n\nUnofficial BitSkins API client\n\n\t2\t5\t7\nb1naryth1ef/steamy\n\nA Python Steam community and market API interface that will get you all hot and bothered\n\n\t2\t5\t7\nkratos1812/Case-Opening\n\nIn-game case opening system for CSGO servers.\n\n\t2\t5\t7\nodota/docs\n\nOpenDota API documentation\n\n\t4\t3\t7\nSteamDatabase/steam-advanced-access-fetch-players\n\n📈 Simple script to fetch Steam player count\n\n\t1\t6\t7\nTheRioMiner/CsgoBetterExternalRaytrace\n\nOverridden maps pack for better external raytrace\n\n\t1\t6\t7\nalliedmodders/hl2sdk-mock\n\nMock HL2SDK and Server\n\n\t5\t1\t6\nchristophersu/PySteamMarket\n\nPython API for getting prices from the Steam market.\n\n\t1\t5\t6\nExtremelyd1/Strat-Roulette\n\nCS:GO Sourcemod Plugin\n\n\t2\t4\t6\ngiovanni-orciuolo/double-sdk\n\nA simple way to write CS:GO cheats!\n\n\t2\t4\t6\nJustArchiNET/Madness\n\nMadness embraces your project by including compatibility layer for selected APIs normally not available on .NET Framework target.\n\n\t5\t1\t6\nModDota/TypescriptPanoramaDeclarations\n\nNo description in the capture.\n\n\t4\t2\t6\nodota/rapier\n\nA JavaScript Dota 2 (Source 2) replay parsing library\n\n\t1\t5\t6\nVozn1akHero/CSGOCaseOpeningSimulator\n\nCounter-Strike case opening simulator which resembles the good old CS:GO user interface\n\n\t3\t3\t6\nautarc/steam-store\n\nAPI client for the unofficial steam storefront/big picture resource\n\n\t2\t3\t5\nBETTING-CODE/awesome-esports-sites\n\nA curated list of awesome esport betting sites – live, statistics and other resources.\n\n\t1\t4\t5\njonteohr/Better-Warden\n\nAn improved and more advanced warden plugin with a custom menu for CS:GO jailbreak servers!\n\n\t2\t3\t5\nLudzikk/CSGO-Gambling-Site\n\nhttps://ludzikk.github.io/CSGO-Gambling-Site/\n\n\t1\t4\t5\nModDota/find-steam-app\n\nFind location of an installed Steam app\n\n\t3\t2\t5\nmprey/csgocact.us\n\nsource code for csgocact.us\n\n\t1\t4\t5\nnezu-cc/ServerCrasher\n\nCS:GO Server Crasher\n\n\t1\t4\t5\nodota/testfiles\n\nStores test replay files\n\n\t2\t3\t5\nodota/underlordsconstants\n\nConstant data for Dota Underlords\n\n\t3\t2\t5\nSnaBe/node-steam-market-fetcher\n\nA Node.js wrapper for the Steam Community Market API.\n\n\t2\t3\t5\nSteamDatabase/.github\n\n💗 Organization-wide community health files\n\n\t1\t4\t5\nwolfcon/RIP-HLTV-BET\n\nRIP BET AD (For Tampermonkey) https://greasyfork.org/en/scripts/423484-rip-hltv-bet\n\n\t2\t3\t5\nalliedmodders/blaster.net\n\nSource and GoldSrc Query Tool\n\n\t2\t2\t4\ncatears124/CS2-Price-API\n\nsimple python cs2 steam market price API\n\n\t1\t3\t4\nialakey/caseforge\n\nOpen-source CS2 case-opening platform: Steam auth, provably fair openings, RTP-balanced case builder, withdrawals bought on market.csgo.com and an admin CRM.\n\n\t1\t3\t4\nIlusion9/csgo-fix-mapchange-crash-sm\n\nFix players crash on map change.\n\n\t1\t3\t4\nismail0234/Benson-Map-Crash-Fixer\n\nCSGO Map Change Client Crash Fixer\n\n\t1\t3\t4\njaxwilko/steam-market-api\n\nPHP - Composer Compatible - Steam Market API\n\n\t2\t2\t4\nJustArchiNET/ArchiTag\n\nArchiTag is a very small utility based on Python 3 and Mutagen to provide missing functionality in opusenc of writing specific Opus metadata, such as total number of tracks or track number.\n\n\t1\t3\t4\nModDota/DotaUI\n\nNo description in the capture.\n\n\t2\t2\t4\nnode-steam/market-pricing\n\nWrapper for the unofficial Steam Market Pricing API\n\n\t1\t3\t4\nodota/media\n\nStores media files for Dota projects\n\n\t2\t2\t4\nSergeyIvanovDevelop/Crypto-Steam-Platform\n\nThe repository contains the code and configuration to run a platform for creating cryptocurrency stakes for arbitrary ERC20 tokens.\n\n\t1\t3\t4\nAareksio/csgodouble-floatchecker\n\nAdds context menu option to check item's float value\n\n\t1\t2\t3\nchinm4/CSGOdrop\n\nA online csgo gambling casino that includes a variety of mini games that allows you to win csgo skins\n\n\t2\t1\t3\nCruze03/CSGO-Case-Opening-Prank\n\nCommand:- !prank (Admin flag \"n\" required)\n\n\t1\t2\t3\nDhruva-Kapadia/CSGOTrollGG\n\nCSGO Case Opening Simulator\n\n\t2\t1\t3\nErhanCSGO/CSGOPolygon-prediction\n\nCSGOPolygon.com - prediction script, double your coins by using this tool\n\n\t1\t2\t3\nEv-Hoang/Bedrock-Chest-Case-Opening\n\nHypixel Skyblock Dungeon Mod - Bedrock Chest Opening Animation (CSGO Style)\n\n\t1\t2\t3\njmjp/csgo-roulette\n\nA csgo gambling roulette make with VueJS 3\n\n\t2\t1\t3\nJustArchiNET/ArchiCrowdin\n\nNo description in the capture.\n\n\t1\t2\t3\nLeonSK/WearMarketInspector\n\nRetrieve Wear Value (Float Value) and Pattern Index from Steam Community Market using http://csgo.exchange API\n\n\t1\t2\t3\nmaximgeerinck/csgo-gamble\n\nCSGO gambling website\n\n\t1\t2\t3\nModDota/BugTracker\n\nListing bugs for Dota 2 Custom Games\n\n\t2\t1\t3\nplwp/mma-betting\n\nUFC/MMA betting model with Pinnacle steam detection for AU book latency arb\n\n\t2\t1\t3\nSouthsideswag16/Csgo-Gambling-Site\n\nNo description in the capture.\n\n\t2\t1\t3\ntacyarg/csgofiesta-frontend-react\n\nRemastered version a the long time favorite csgo site\n\n\t2\t1\t3\nVelorasse/Mutah-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-csmoney-csgoskins\n\ngambling script for Mutah, Keydrop, csmoney, and csgoskins, featuring hacks, cheats, and predictors. Offers strategies to boost winning odds and optimize performance on these platforms.\n\n\t3\t0\t3\nalliedmodders/am-github-artifact-webhook\n\nNo description in the capture.\n\n\t2\t0\t2\ncharamza/roulette\n\nCSGO like roulette in JS\n\n\t1\t1\t2\nCruze03/CSGO-PugSetup-RoundRestore\n\nSometimes (player dropped/crashed) which would be disadvantage for a team. It would be very handy to restore the match to the previous round.\n\n\t1\t1\t2\ncsgorol/CSGO-ROLL-Crash-Predictor\n\nCSGO-ROLL-Crash-Predictor\n\n\t1\t1\t2\nFoxSerito/FOXWORLD_plugin_DoubleJump_CSGO\n\nПлагин SourceMod (CSGO). Двойной прыжок с эффектом.\n\n\t1\t1\t2\nhkehayovmoonbiz/CS2-Casino-Full-Source-Code\n\nCS2, CS2 betting platforms, Skin Roulette, Case Unboxing, Crash games, Jackpot, purchase CS2 casino source, crypto gambling\n\n\t1\t1\t2\nJustZakary/steamstoreapi\n\nThis NPM module is a API wrapper that makes the steam unofficial API easier to use.\n\n\t2\t0\t2\njzimr/steam-market-api\n\nA java library to easily get Steam Community Market data\n\n\t1\t1\t2\nMomohime/CSGO.Network-Jackpot-Coinflip\n\nNo description in the capture.\n\n\t1\t1\t2\nnnjjswat/moneybot\n\nautomated bots for bustabit (formerly known as moneypot), csgo crash, etc\n\n\t0\t2\t2\nodota/carry\n\nLegacy Application for donations to the OpenDota project\n\n\t1\t1\t2\nodota/PublicMatchDataBot\n\nA Discord bot to remind users to turn on Expose Public Match Data in the Dota 2 client\n\n\t1\t1\t2\nOrillio/CSGOBet.com\n\nCSGO roulette web app\n\n\t2\t0\t2\nripexz/csgo-bet-alert\n\nA Chrome extension to keep track of active CS:GO Lounge matches.\n\n\t1\t1\t2\nrrpvm/lumen_sense-beta-deprecated-\n\nthis is internal csgo cheat written by me(no paste, self reverse structures). start : ~6 August 2020, end : ~ 14 December 2020\n\n\t1\t1\t2\nRuthless222/csgoscore\n\nThis is a Counter Strike Global Offensive Betting Site. You chose the skins you want to bet and try to win jackpots\n\n\t2\t0\t2\ntfburns/CSGO-cases-PL\n\nExpected profit-loss of CS:GO case openings\n\n\t1\t1\t2\nTomDra/CSGO-Case-Data-Analysis\n\nWorks out the most profitable CS:GO case at that current time\n\n\t1\t1\t2\nValvePython/dota2-wrappers\n\nNo description in the capture.\n\n\t1\t1\t2\nValvePython/teamfortress2-closed-captions\n\nThis project aims to provide a set of closed captions for Team Fortress 2\n\n\t1\t1\t2\nVistaNetGTX/Cstrike.bet-\n\nCSGO Roulette Website Angular frontend, nodejs backend, and steam trading bots\n\n\t1\t1\t2\nwafflas/csgo-case-opening-simulator\n\nI created a cs go case opening simulator for a meme coin\n\n\t0\t2\t2\nAdmiral-Enigma/Le_Coinflip\n\nConflip game\n\n\t1\t0\t1\nadryeljuliao/roulette-csgo\n\nNo description in the capture.\n\n\t1\t0\t1\nAndreuTheG/csgo-coinflip-web\n\nCSGO Gambling Coinflip Website\n\n\t1\t0\t1\nasmilen/csgoDouble\n\na b c\n\n\t1\t0\t1\nb1naryth1ef/csgofort\n\nA CSGO portal for trading, betting, analytics, and more!\n\n\t1\t0\t1\nBaterka/PrivateSteamBettingWebsite2024\n\nPrivate Steam (Counter-Strike 2) betting/gambling website - Roulette, Jackpot\n\n\t1\t0\t1\nblackcaer/SteamTradeHandler\n\nAutomation of Steam trading. Helper project for bet automation.\n\n\t1\t0\t1\nBTheCoderr/theRounders\n\nThe Rounders - A professional-grade sports betting analytics platform combining real-time odds tracking, sharp movement detection, and advanced statistical analysis. Features include line shopping, steam move alerts, power rankings, and comprehensive bet t…\n\n\t1\t0\t1\nCallumHemsley/KazeBot\n\nA Twitch chat betting bot for CSGO, simply bet a certain amount of points, and double if you win, lose all if you lose. Simple.\n\n\t1\t0\t1\nchrisjpm/CSGOJackpotTemplate\n\nFront end for a jackpot site\n\n\t1\t0\t1\ncolinsenner/valve-bug-bounty\n\nFor many years CS:GO, Dota 2, and Team Fortress 2 servers had a bug that allowed malicious users to leak crucial server process memory or reliably crash any server.\n\n\t1\t0\t1\ncoryypeters/nrl-odds-intelligence-pipeline\n\nReal-time sports betting odds intelligence — streaming pipeline that detects line movement, steam, and arbitrage across bookmakers. Python · Redis Streams · FastAPI · React.\n\n\t1\t0\t1\ndeissh/dev-csgoduo\n\nCS:GO. Bot for receiving things on the site (Polygon, Duo, Double and etc).\n\n\t1\t0\t1\ndom1torii/even-better-font-manager\n\nSimply even better cross-platform tool for CS2 Font Management\n\n\t1\t0\t1\nDONnicov/CSGO-crash-black-screen-\n\nsolution csgo crash black screen and close csgo\n\n\t1\t0\t1\nDoubleBoters/CsgoDouble\n\nNo description in the capture.\n\n\t1\t0\t1\ndownarowiczd/DoubleBot\n\nAn old CSGO Double Bot written for my friend. - 07.05.2016\n\n\t1\t0\t1\nErayBahar/steammarketscraper\n\nSteam Market Scraper Python-based tool that tracks real-time CS2 skin prices using Steam's hidden API. It fetches the lowest sell and highest buy offers for any item, helping you monitor deals or snipe underpriced listings automatically.\n\n\t1\t0\t1\nfairydarkness/SteamwebmailAPI\n\nUnofficial Python API for steamwebmail.com Fast, lightweight, and browserless library for automating steamwebmail.com. Support for session management, proxy, folder navigation, and message retrieval\n\n\t1\t0\t1\nFAQU2/CSGO-Coinflip-MyJailShop\n\nSourcemod plugin which provides a Coinflip system for MyJailShop.\n\n\t1\t0\t1\nFlamesONE/csgo-case-opening\n\nNo description in the capture.\n\n\t1\t0\t1\nFunnyRain/csgorun-crash-watch\n\n🚀 CsgoRun dump crash. / 🚀 CsgoRun дамп крашей.\n\n\t1\t0\t1\ngeohdgio/Venatus-Autenticator\n\nეს არის Steam Autenticator ქართული Venatus Trade & Betting ისთვის და Valve News Georgia-სთვის.\n\n\t1\t0\t1\nhakanstarlord/steam-bot\n\nSports betting steam-move signal detection with ML pipeline (XGBoost stacking + isotonic calibration), backtesting engine, Flask dashboard, and Telegram alerts.\n\n\t1\t0\t1\nHvH-gg/CSGO-Item-CrashFix\n\nA plugin for Counter-Strike: Global Offensive that fixes an exploit where receiving CS2 Items will cause CS:GO clients to crash\n\n\t1\t0\t1\nHvH-gg/CSGO-NetMsg-CrashFix\n\nA plugin for Counter-Strike: Global Offensive that fixes an exploit where spamming NetMsg_StringCmd packets would result in a server crash.\n\n\t1\t0\t1\nisybycnsmam/SteamLibrary\n\nLegacy Steam Unofficial API\n\n\t1\t0\t1\nItsTangerine/SteamApis.Net\n\nUnofficial https://steamapis.com .NET library, supporting .NET 6.0+\n\n\t1\t0\t1\nJustArchiNET/JustArchi.net\n\nNo description in the capture.\n\n\t1\t0\t1\nkiri-osint/CS2-Info-Hub-Bot\n\nA Telegram bot that acts as a hub for CS2 players, providing real-time skin prices, server stats, and user profile/inventory inspection using official and unofficial Steam APIs.\n\n\t1\t0\t1\nKoshkaj/monte\n\nGamified csgo gambling platform implementation\n\n\t1\t0\t1\nmadsab/CaseOpening\n\nA school project using Java. Simulating the case opening from CSGO and more.\n\n\t1\t0\t1\nman90es/steamcardexchange-api\n\nSteamCardExchange.net unofficial REST API server (scraper).\n\n\t1\t0\t1\nMattPua/steam-unofficial-docs\n\nUnofficial docs for Steam APIs with fumadocs\n\n\t1\t0\t1\nMetallist1/Portfolio.CsgoWinGambleProject\n\nA website that was done in 2017 September. Websites focus was on gambling with Counter-Strike items. Project was largely completed however backups were not done correctly, this resulted in half a year of wasted improvements to the code. The website was test…\n\n\t1\t0\t1\nmikebobadilla/csgo-jackpot\n\nNo description in the capture.\n\n\t0\t1\t1\nmikebobadilla/meteor-csgojackpot\n\nCssgo Jackpot done in meteor\n\n\t1\t0\t1\nModDota/D2VDump\n\nDota 2 Server VScript API Dumper\n\n\t1\t0\t1\nModDota/DotaTracking\n\nNo description in the capture.\n\n\t1\t0\t1\nModDota/eslint-config\n\nESLint config by ark120202\n\n\t1\t0\t1\nmr-codinglv/Casino-script\n\nscript casino - script betting - exchange script - bc casino - casino csgo - script bet - betwin script\n\n\t1\t0\t1\nMrKeelik/MrKeel\n\nCSGO DOUBLE BOT\n\n\t1\t0\t1\nnoahlatzel/CSGORollHelper\n\nLeveraging positive expected value on triple green jackpots on CSGORoll!\n\n\t1\t0\t1\noddsgpt/oddsgpt-market-intelligence\n\nResearch on football betting markets, closing odds, CLV, market efficiency, steam moves, AI betting systems, and sports market intelligence.\n\n\t1\t0\t1\noEXU/csgo-server-crasher\n\nCSGO SERVER CRASHER\n\n\t1\t0\t1\nPrdTTony/CSGO-Roulette\n\n[CSGO] Roulette System. Bet on RED or Black and win x2 credits\n\n\t1\t0\t1\nr-adamski/csgo-jackpot\n\nNo description in the capture.\n\n\t1\t0\t1\nSahotallo/Turan-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-Skinbaron-hellcase\n\ngambling script for Turan, Keydrop, Skinbaron, and Hellcase, providing hacks, cheats, and predictors. Includes strategies to improve winning chances and enhance gameplay on these platforms.\n\n\t1\t0\t1\nsamuelcsouza/steam-marketplace-api\n\nAn unofficial API to get data from the Steam Marketplace.\n\n\t1\t0\t1\nSKINSTRACK/CS2-Price-API\n\nSkinstrack offers a free, limited API endpoint that returns Steam item prices. Paid plans additionally provide access to pricing data from multiple marketplaces, making it possible to compare prices across different markets through a single API.\n\n\t1\t0\t1\nsnmtriet/CSGO-Casino-Full-Source-Code\n\nCSGO, CSGOEmpire, Case Opening, Case Battles, Roulette, Coinflip, buy csgo gambling site, gambling\n\n\t1\t0\t1\nSteamRE/homebrew-tools\n\nRepository for installation of SteamRE tools via Homebrew (http://brew.sh)\n\n\t1\t0\t1\nSteamRE/opensteamworks.org\n\nNo description in the capture.\n\n\t1\t0\t1\nTheQuack45/CsgoCaseOpenProgram\n\nSimple program to parse an XML file with CS:GO case information and \"simulate\" case openings\n\n\t1\t0\t1\nTLClassless/StratRouletteCSGO\n\nA 'Strat Roulette' web app for CS:GO!\n\n\t1\t0\t1\ntomasoom/csgoCaseOpening\n\nNo description in the capture.\n\n\t1\t0\t1\nvitaliy-evsyukov/steamgifts-autobet-bookmarklet\n\nbookmarklet for automatic bets on steamgifts.com\n\n\t1\t0\t1\nXpravdaX/RouletteCSGO\n\nNo description in the capture.\n\n\t1\t0\t1\nYuiKasumii/steam_api_unofficial\n\nUnofficial Steam Game Information Database\n\n\t1\t0\t1\nZexuz/Steam-Betting\n\nA betting website build ontop of STEAM's ecosystem\n\n\t1\t0\t1\nANK-RULZZ/steam-jackpot-site\n\ngetting some errors and would like some one to help me with it thank you!!!\n\n\t0\t0\t0\nasmilen/CsgoDoubleVS\n\nNo description in the capture.\n\n\t0\t0\t0\nCORNOODOSADAS/CSGOWeed\n\nCsgo Jackpot and Coinflip\n\n\t0\t0\t0\nCSGOApple/csgoapple\n\nJackpot Site\n\n\t0\t0\t0\nCSGOFAST/csgofast-api\n\nNo description in the capture.\n\n\t0\t0\t0\nDonakall/csgoDoublebot\n\nAutomated bot for csgodouble\n\n\t0\t0\t0\nfedor-selivanov/csgo-fast-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nfoldageros/csgod\n\ndouble bot\n\n\t0\t0\t0\ngmod-gambling/gmod-gambling\n\nNo description in the capture.\n\n\t0\t0\t0\nierome/CSGOBoss-BackEnd\n\nBack end version of CSGOBoss. This was a CSGO Gambling site named CSGOBoss. Coded by an old friend of mine Dahquan Hinds (https://github.com/dahquan/) Thought I would release this to help out any one who would need it.\n\n\t0\t0\t0\njamienp1/CSGODOUBLE-BOT-AUTO\n\ni got a bot thats is betting on the last winning color except from green and if you lose it will double the coins you set it to bet, pretty good, so when there comes a loooong train you will be gaining a bit of money codepaste_net/ugmt92 remove all the _ an…\n\n\t0\t0\t0\nJEYONER/CSGOTOXIC\n\nPAGINA DE JACKPOT CSGO SKINS\n\n\t0\t0\t0\nkalrish/csgo-jackpot\n\nStressful but funny zombie-like Counter-Strike: Global Offensive game mode.\n\n\t0\t0\t0\nkrys12345/roulettee\n\n// ==UserScript== // @name CSGO Predict Bot // @namespace http://csgodouble.com // @version 1.0 // @description predicts what number its gonna be // @author Meee // @match http://www.csgodouble.com/ // @grant none // ==/…\n\n\t0\t0\t0\nLilDuggiMuffi/CSGODouble-Working-Bot\n\nFixed CSGO Double Bot\n\n\t0\t0\t0\nLyricLy/Steam2Proton\n\nCheck if all your Steam games will work with Proton! Uses the official Steam API and the unofficial Proton API.\n\n\t0\t0\t0\nM0NsTeR77/csgo-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nozanhalis/Hi\n\n// ==UserScript== // @name CS GO LOUNGE BOT-Ozan Halis // @namespace http://csgolounge.com/ // @version 0.6.6 // @description Cs Go Lounge Hızlı BOT // @match http://csgolounge.com/* // @match http://dota2lounge.com/* // @updateURL h…\n\n\t0\t0\t0\nscoobertus/CSGO-DoubleBot\n\nNo description in the capture.\n\n\t0\t0\t0\nTradeal/CSGO-Jackpot-Bot\n\nNo description in the capture.\n\n\t0\t0\t0\nValvePython/artifact\n\nNo description in the capture.\n\n\t0\t0\t0\nVampire/CSGO-Roulette-Bot\n\nNo description in the capture.\n\n\t0\t0\t0\nvdemans/csgo-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nVocoreVideo/CSGODungeon-\n\nCSGO Jackpot\n\n\t0\t0\t0\nwayz-dev/csgofloat\n\nNo description in the capture.\n\n\t0\t0\t0\n\nスナップショット：17 9月 2026, 11:19:11（ソースに記載の通り）。タイムゾーンは明記されていない。エクスポートではリレーションシップの収集に上限が設けられている（多くのカテゴリは「40」で打ち切られている）。コントリビューターとフォーク作成者の合計は、4,214の異なるプロフィール・リポジトリの組み合わせにおいて、4,554件のロールエントリとなる。1つのプロフィールが両方の役割を持つこともある。 「0」は、そのカテゴリで記録が取得されなかったことを意味します。リポジトリ名にはエイリアスや大文字・小文字の異なる表記が含まれる場合がありますが、合計値はソースの集計規則に従っています。\n\n出典の由来\n収集したファイルから作成されます。\n支持の証言\n2323/reddit_scams_ultra/steam_support_tickets_MEGA.json · 行数 45, 58, 107, 110, 294\nネットワークスナップショット\nnetwork-repositories.csv · raw_data.json ・overlaps.csv ・summary.txt（マニフェストには従来のソースパスが保持されている）\n\nマニフェストには、ソースパス、バイトサイズ、SHA-256ハッシュ、および選択されたレコードの位置が記録されています。生のキャプチャデータは、調査による解釈とは別個に扱われます。\n\nソースマニフェストをダウンロード ↓",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam 執行証拠 — 裏付け記録および開発者ネットワーク"
          },
          {
            "level": 2,
            "id": null,
            "text": "訴状をお読みください。ソースを添付したままにしておいてください。"
          },
          {
            "level": 3,
            "id": null,
            "text": "Permanent sanction & closed appeals"
          },
          {
            "level": 4,
            "id": null,
            "text": "Permanently banned Steam account without a clear explanation, need help!"
          },
          {
            "level": 3,
            "id": null,
            "text": "Account recovery & a reported $10,000 loss"
          },
          {
            "level": 4,
            "id": null,
            "text": "Got $10k stollen from steam inventory due to steam' support fault."
          },
          {
            "level": 3,
            "id": null,
            "text": "A reported $500+ loss & template replies"
          },
          {
            "level": 4,
            "id": null,
            "text": "Funds stolen through steam market. Disappointed with Steam response.(or lackthereof)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam Guard & an item-restoration refusal"
          },
          {
            "level": 4,
            "id": null,
            "text": "Many people are losing item via clicking links where steam guard is enabled and steam support doesn't not restore items."
          },
          {
            "level": 3,
            "id": null,
            "text": "Selective enforcement & an unexplained ban"
          },
          {
            "level": 4,
            "id": null,
            "text": "🚨 Steam Bans Without Reason and Ignores Its Community — What’s Going On?"
          },
          {
            "level": 2,
            "id": null,
            "text": "公共インフラ。大規模に収録されました。"
          },
          {
            "level": 2,
            "id": null,
            "text": "収集したファイルから作成されます。"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/ja/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/ja/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/selected-support-records.json",
          "https://phishdestroy.io/steam_dossier/ja/investigation_part2.html#outsourcing-case",
          "https://www.reddit.com/r/ohnePixel/comments/1hahqx2/permanently_banned_steam_account_without_a_clear/",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://www.reddit.com/r/DotA2/comments/r55bd7/many_people_are_losing_item_via_clicking_links/",
          "https://www.reddit.com/r/SteamUncensored/comments/1kjt2fa/steam_bans_without_reason_and_ignores_its/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/network-repositories.csv",
          "https://github.com/alliedmodders/amxmodx",
          "https://github.com/alliedmodders/sourcemod",
          "https://github.com/DoctorMcKay/node-steam-user",
          "https://github.com/Facepunch/Facepunch.Steamworks",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://github.com/odota/core",
          "https://github.com/odota/dotaconstants",
          "https://github.com/odota/web",
          "https://github.com/splewis/get5",
          "https://github.com/SteamDatabase/FileDetectionRuleSets",
          "https://github.com/SteamRE/SteamKit",
          "https://github.com/ValveSoftware/dxvk",
          "https://github.com/ValveSoftware/GameNetworkingSockets",
          "https://github.com/ValveSoftware/gamescope",
          "https://github.com/ValveSoftware/Proton",
          "https://github.com/ValveSoftware/source-sdk-2013",
          "https://github.com/ValveSoftware/wine",
          "https://github.com/ValveSoftware/steam-devices",
          "https://github.com/ValveSoftware/steam-audio",
          "https://github.com/alliedmodders/metamod-source",
          "https://github.com/alliedmodders/sourcepawn",
          "https://github.com/ValveSoftware/Fossilize",
          "https://github.com/rlabrecque/Steamworks.NET",
          "https://github.com/ModDota/moddota.github.io",
          "https://github.com/odota/parser",
          "https://github.com/ValveSoftware/steam-for-linux",
          "https://github.com/SteamRE/DepotDownloader",
          "https://github.com/JustArchiNET/ASF-ui",
          "https://github.com/advancedfx/advancedfx",
          "https://github.com/alliedmodders/ambuild",
          "https://github.com/SteamDatabase/BrowserExtension",
          "https://github.com/odota/mobile",
          "https://github.com/ValvePython/steam",
          "https://github.com/skadistats/clarity",
          "https://github.com/SteamRE/open-steamworks",
          "https://github.com/ValveSoftware/Source-1-Games",
          "https://github.com/alliedmodders/hl2sdk",
          "https://github.com/SteamDatabase/steamdb.info-issues",
          "https://github.com/CSGOFloat/inspect",
          "https://github.com/ValveSoftware/SteamOS",
          "https://github.com/alliedmodders/source2mod",
          "https://github.com/smiley/steamapi",
          "https://github.com/SteamDatabase/GameTracking",
          "https://github.com/ValveSoftware/counter-strike_rules_and_regs",
          "https://github.com/ValveSoftware/openvr",
          "https://github.com/SteamDatabase/easy-markdown-editor",
          "https://github.com/ValveSoftware/Dota-2",
          "https://github.com/ValveSoftware/Dota2-Gameplay",
          "https://github.com/JustArchiNET/ArchiBot",
          "https://github.com/ztizzlegaming/CSGOWinBig",
          "https://github.com/JustArchiNET/mantis.justarchi.net",
          "https://github.com/odota/node-steam-user",
          "https://github.com/ModDota/TypeScriptAddonTemplate",
          "https://github.com/ValvePython/vdf",
          "https://github.com/alliedmodders/amtl",
          "https://github.com/ValvePython/dota2",
          "https://github.com/alliedmodders/stripper-source",
          "https://github.com/Allyans3/steam-market-api-v2",
          "https://github.com/ModDota/dota-tutorial",
          "https://github.com/odota/blog",
          "https://github.com/OpsecGuy/BetterGo",
          "https://github.com/pxvr-official/1",
          "https://github.com/Revadike/InternalSteamWebAPI",
          "https://github.com/JoeSzymkowiczFiveM/qb-lootcrate",
          "https://github.com/AbrarKL/MyRoulette.XYZ",
          "https://github.com/JustArchiNET/ASF-WebConfigGenerator",
          "https://github.com/ModDota/dota-data",
          "https://github.com/ModDota/TypeScriptDeclarations",
          "https://github.com/ModDota/API",
          "https://github.com/alliedmodders/cssdm",
          "https://github.com/SteamDatabase/steamstat.us",
          "https://github.com/c0deina/csgojackpotV2",
          "https://github.com/ValvePython/steamctl",
          "https://github.com/ValvePython/csgo",
          "https://github.com/BeepIsla/csgo-crash-exploit",
          "https://github.com/ValvePython/vpk",
          "https://github.com/alliedmodders/SM-SteamWorks",
          "https://github.com/SteamRE/Steam4NET",
          "https://github.com/alliedmodders/hl2sdk-manifests",
          "https://github.com/JustArchiNET/ASF-PluginTemplate",
          "https://github.com/ModDota/Dota2AIFramework",
          "https://github.com/Shkyyl/KeyChamp",
          "https://github.com/SteamDatabase/SteamMonitor",
          "https://github.com/Baterka/cslore.com",
          "https://github.com/SteamDatabase/SteamTokenDumper",
          "https://github.com/monoblocker/roulette",
          "https://github.com/zsith/launcher.user.js",
          "https://github.com/LincolnIT/CSGODouble-bot-automated",
          "https://github.com/vladpuz/steam-market",
          "https://github.com/mcgrizzz/Cstrike.bet",
          "https://github.com/odota/underlords-web",
          "https://github.com/SteamDatabase/SteamToTwitter",
          "https://github.com/ModDota/AbilityLuaSpellLibrary",
          "https://github.com/alvinl/bitskins",
          "https://github.com/b1naryth1ef/steamy",
          "https://github.com/kratos1812/Case-Opening",
          "https://github.com/odota/docs",
          "https://github.com/SteamDatabase/steam-advanced-access-fetch-players",
          "https://github.com/TheRioMiner/CsgoBetterExternalRaytrace",
          "https://github.com/alliedmodders/hl2sdk-mock",
          "https://github.com/christophersu/PySteamMarket",
          "https://github.com/Extremelyd1/Strat-Roulette",
          "https://github.com/giovanni-orciuolo/double-sdk",
          "https://github.com/JustArchiNET/Madness",
          "https://github.com/ModDota/TypescriptPanoramaDeclarations",
          "https://github.com/odota/rapier",
          "https://github.com/Vozn1akHero/CSGOCaseOpeningSimulator",
          "https://github.com/autarc/steam-store",
          "https://github.com/BETTING-CODE/awesome-esports-sites",
          "https://github.com/jonteohr/Better-Warden",
          "https://github.com/Ludzikk/CSGO-Gambling-Site",
          "https://github.com/ModDota/find-steam-app",
          "https://github.com/mprey/csgocact.us",
          "https://github.com/nezu-cc/ServerCrasher",
          "https://github.com/odota/testfiles",
          "https://github.com/odota/underlordsconstants",
          "https://github.com/SnaBe/node-steam-market-fetcher",
          "https://github.com/SteamDatabase/.github",
          "https://github.com/wolfcon/RIP-HLTV-BET",
          "https://github.com/alliedmodders/blaster.net",
          "https://github.com/catears124/CS2-Price-API",
          "https://github.com/ialakey/caseforge",
          "https://github.com/Ilusion9/csgo-fix-mapchange-crash-sm",
          "https://github.com/ismail0234/Benson-Map-Crash-Fixer",
          "https://github.com/jaxwilko/steam-market-api",
          "https://github.com/JustArchiNET/ArchiTag",
          "https://github.com/ModDota/DotaUI",
          "https://github.com/node-steam/market-pricing",
          "https://github.com/odota/media",
          "https://github.com/SergeyIvanovDevelop/Crypto-Steam-Platform",
          "https://github.com/Aareksio/csgodouble-floatchecker",
          "https://github.com/chinm4/CSGOdrop",
          "https://github.com/Cruze03/CSGO-Case-Opening-Prank",
          "https://github.com/Dhruva-Kapadia/CSGOTrollGG",
          "https://github.com/ErhanCSGO/CSGOPolygon-prediction",
          "https://github.com/Ev-Hoang/Bedrock-Chest-Case-Opening",
          "https://github.com/jmjp/csgo-roulette",
          "https://github.com/JustArchiNET/ArchiCrowdin",
          "https://github.com/LeonSK/WearMarketInspector",
          "https://github.com/maximgeerinck/csgo-gamble",
          "https://github.com/ModDota/BugTracker",
          "https://github.com/plwp/mma-betting",
          "https://github.com/Southsideswag16/Csgo-Gambling-Site",
          "https://github.com/tacyarg/csgofiesta-frontend-react",
          "https://github.com/Velorasse/Mutah-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-csmoney-csgoskins",
          "https://github.com/alliedmodders/am-github-artifact-webhook",
          "https://github.com/charamza/roulette",
          "https://github.com/Cruze03/CSGO-PugSetup-RoundRestore",
          "https://github.com/csgorol/CSGO-ROLL-Crash-Predictor",
          "https://github.com/FoxSerito/FOXWORLD_plugin_DoubleJump_CSGO",
          "https://github.com/hkehayovmoonbiz/CS2-Casino-Full-Source-Code",
          "https://github.com/JustZakary/steamstoreapi",
          "https://github.com/jzimr/steam-market-api",
          "https://github.com/Momohime/CSGO.Network-Jackpot-Coinflip",
          "https://github.com/nnjjswat/moneybot",
          "https://github.com/odota/carry",
          "https://github.com/odota/PublicMatchDataBot",
          "https://github.com/Orillio/CSGOBet.com",
          "https://github.com/ripexz/csgo-bet-alert",
          "https://github.com/rrpvm/lumen_sense-beta-deprecated-",
          "https://github.com/Ruthless222/csgoscore",
          "https://github.com/tfburns/CSGO-cases-PL",
          "https://github.com/TomDra/CSGO-Case-Data-Analysis",
          "https://github.com/ValvePython/dota2-wrappers",
          "https://github.com/ValvePython/teamfortress2-closed-captions",
          "https://github.com/VistaNetGTX/Cstrike.bet-",
          "https://github.com/wafflas/csgo-case-opening-simulator",
          "https://github.com/Admiral-Enigma/Le_Coinflip",
          "https://github.com/adryeljuliao/roulette-csgo",
          "https://github.com/AndreuTheG/csgo-coinflip-web",
          "https://github.com/asmilen/csgoDouble",
          "https://github.com/b1naryth1ef/csgofort",
          "https://github.com/Baterka/PrivateSteamBettingWebsite2024",
          "https://github.com/blackcaer/SteamTradeHandler",
          "https://github.com/BTheCoderr/theRounders",
          "https://github.com/CallumHemsley/KazeBot",
          "https://github.com/chrisjpm/CSGOJackpotTemplate",
          "https://github.com/colinsenner/valve-bug-bounty",
          "https://github.com/coryypeters/nrl-odds-intelligence-pipeline",
          "https://github.com/deissh/dev-csgoduo",
          "https://github.com/dom1torii/even-better-font-manager",
          "https://github.com/DONnicov/CSGO-crash-black-screen-",
          "https://github.com/DoubleBoters/CsgoDouble",
          "https://github.com/downarowiczd/DoubleBot",
          "https://github.com/ErayBahar/steammarketscraper",
          "https://github.com/fairydarkness/SteamwebmailAPI",
          "https://github.com/FAQU2/CSGO-Coinflip-MyJailShop",
          "https://github.com/FlamesONE/csgo-case-opening",
          "https://github.com/FunnyRain/csgorun-crash-watch",
          "https://github.com/geohdgio/Venatus-Autenticator",
          "https://github.com/hakanstarlord/steam-bot",
          "https://github.com/HvH-gg/CSGO-Item-CrashFix",
          "https://github.com/HvH-gg/CSGO-NetMsg-CrashFix",
          "https://github.com/isybycnsmam/SteamLibrary",
          "https://github.com/ItsTangerine/SteamApis.Net",
          "https://github.com/JustArchiNET/JustArchi.net",
          "https://github.com/kiri-osint/CS2-Info-Hub-Bot",
          "https://github.com/Koshkaj/monte",
          "https://github.com/madsab/CaseOpening",
          "https://github.com/man90es/steamcardexchange-api",
          "https://github.com/MattPua/steam-unofficial-docs",
          "https://github.com/Metallist1/Portfolio.CsgoWinGambleProject",
          "https://github.com/mikebobadilla/csgo-jackpot",
          "https://github.com/mikebobadilla/meteor-csgojackpot",
          "https://github.com/ModDota/D2VDump",
          "https://github.com/ModDota/DotaTracking",
          "https://github.com/ModDota/eslint-config",
          "https://github.com/mr-codinglv/Casino-script",
          "https://github.com/MrKeelik/MrKeel",
          "https://github.com/noahlatzel/CSGORollHelper",
          "https://github.com/oddsgpt/oddsgpt-market-intelligence",
          "https://github.com/oEXU/csgo-server-crasher",
          "https://github.com/PrdTTony/CSGO-Roulette",
          "https://github.com/r-adamski/csgo-jackpot",
          "https://github.com/Sahotallo/Turan-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-Skinbaron-hellcase",
          "https://github.com/samuelcsouza/steam-marketplace-api",
          "https://github.com/SKINSTRACK/CS2-Price-API",
          "https://github.com/snmtriet/CSGO-Casino-Full-Source-Code",
          "https://github.com/SteamRE/homebrew-tools",
          "https://github.com/SteamRE/opensteamworks.org",
          "https://github.com/TheQuack45/CsgoCaseOpenProgram",
          "https://github.com/TLClassless/StratRouletteCSGO",
          "https://github.com/tomasoom/csgoCaseOpening",
          "https://github.com/vitaliy-evsyukov/steamgifts-autobet-bookmarklet",
          "https://github.com/XpravdaX/RouletteCSGO",
          "https://github.com/YuiKasumii/steam_api_unofficial",
          "https://github.com/Zexuz/Steam-Betting",
          "https://github.com/ANK-RULZZ/steam-jackpot-site",
          "https://github.com/asmilen/CsgoDoubleVS",
          "https://github.com/CORNOODOSADAS/CSGOWeed",
          "https://github.com/CSGOApple/csgoapple",
          "https://github.com/CSGOFAST/csgofast-api",
          "https://github.com/Donakall/csgoDoublebot",
          "https://github.com/fedor-selivanov/csgo-fast-roulette",
          "https://github.com/foldageros/csgod",
          "https://github.com/gmod-gambling/gmod-gambling",
          "https://github.com/ierome/CSGOBoss-BackEnd",
          "https://github.com/jamienp1/CSGODOUBLE-BOT-AUTO",
          "https://github.com/JEYONER/CSGOTOXIC",
          "https://github.com/kalrish/csgo-jackpot",
          "https://github.com/krys12345/roulettee",
          "https://github.com/LilDuggiMuffi/CSGODouble-Working-Bot",
          "https://github.com/LyricLy/Steam2Proton",
          "https://github.com/M0NsTeR77/csgo-roulette",
          "https://github.com/ozanhalis/Hi",
          "https://github.com/scoobertus/CSGO-DoubleBot",
          "https://github.com/Tradeal/CSGO-Jackpot-Bot",
          "https://github.com/ValvePython/artifact",
          "https://github.com/Vampire/CSGO-Roulette-Bot",
          "https://github.com/vdemans/csgo-roulette",
          "https://github.com/VocoreVideo/CSGODungeon-",
          "https://github.com/wayz-dev/csgofloat",
          "https://phishdestroy.io/steam_dossier/output_steam_network/raw_data.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/enforcement-source-manifest.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ja/steam_enforcement_evidence.content.json",
      "export_json_sha256": "fe194308d90c3340462f034b72872127c510e82b3afd5157550ee12ac281cf5d"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ja/steam_evidence_archive.html",
      "language": "ja",
      "title": "情報源を精査する — 『Steam』の資料",
      "source_url": "https://phishdestroy.io/steam_dossier/ja/steam_evidence_archive",
      "source_html_sha256": "1adedba064aaef4abfc66a6ad783a046f6c922ef5693ea2334d95f36088ef79b",
      "exported_at": "2026-09-29T00:22:20.954Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "steam_evidence_archive.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ja/steam_evidence_archive.pdf?v=print-20260929-v5",
        "sha256": "1b878ac06f4702daf91eff8aeb3bef83222d4d277b197d949dde8496f43130ca",
        "bytes": 152996,
        "pages": 4
      },
      "integrity": {
        "signed_object": "steam_evidence_archive.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "steam_evidence_archive.content.json.asc",
        "digest_file": "steam_evidence_archive.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify steam_evidence_archive.content.json.asc steam_evidence_archive.content.json",
          "sha256sum -c steam_evidence_archive.content.json.sha256"
        ]
      },
      "content": {
        "text": "調査資料／情報収集 002\nSteam 証拠アーカイブ — 『16,319』の資料\n\nすべての請求。 原点に立ち返る。\n\nこのセクションが証明すること\n\nこのフォレンジック・アーカイブは、16,319の一次資料記録（Valve開発者コミュニティのドキュメント、GitHubの公開イシュー、検証済みのTrustpilotへの苦情、およびアーカイブされたフォーラムの報告など）を、暗号ハッシュと出所ログを用いて索引化しています。このアーカイブは、再現可能なプラットフォームの脆弱性、文書化されていないAPIの非推奨機能、およびアカウント乗っ取りに関する継続的な消費者からの苦情を実証する、検証可能な証拠基盤を提供します。\n\n← エグゼクティブ・ブリーフィングに戻る\n\n主張の背景にある記録を見つけましょう。情報源で絞り込み、全文を開き、元のリンクをたどってください。情報源の行が重複する場合がありますが、記録は検証済みの事象とは限りません。\n\n調査に戻る ↗\n354TRUSTPILOT / ソース行\n208REDDIT / 出典行\n705GITHUB / ソース行\n15,302MASTER CSV / ソース行\n16,319 記録 — プラットフォーム種別内訳\n\nWikiカテゴリ「provenance」（7,620件の記録 · 46.7%）： Valve開発者コミュニティ（developer.valvesoftware.com）、SteamDBのドキュメント／FAQ、およびゲームコミュニティのウィキ（Liquipedia CS／DotaおよびFandom Steamのウィキ）から、2016年8月2024から2016年9月2026.にかけて、自動化されたWARCスナップショットおよびMediaWiki APIのエンドポイントを通じて解析されました。すべての7,620のエントリは、マスターCSVエクスポートに完全に統合されています（TOTAL_VALVE_SCANDALS_MASTER_DB.csv).\n\nWiki\n7,620\nReddit\n5,635\nGitHub\n2,395\nTrustpilot\n393\nWeb\n276\n9,116 16,319のレコード（55.8%）のうち、Steam / Valveへの参照を含むもの\n\nこの検索可能なアーカイブは、以下に基づいて構築されました。 2026-09-17 上記のソースエクスポート一覧から。この資料集の他の箇所で使用されている、独立した40,448-の行マスターエクスポートは、対象範囲が異なります。詳しくは、 マニフェストを生成する このアーカイブの集計については、記録は重複している場合があり、個別の事象とは限りません。\n\nソースプラットフォーム\n資料収集\nSteam / 「Valve」の言及\nテキストの一致、またはValveリポジトリ欠落／削除されたテキスト\n16,569 ソース行\n16,319 異なるレコード\n249 重複行を統合しました\n1 行を除外\n元のファイルを表示 ↘\n★TRUSTPILOT2015-10-16#1RATING 1/5\n\nSteam is the biggest PC gaming platform without a doubt. A power which could be abused but Steam for the most part doesn't. Overall a definite download for any moden digital age PC gamer. It mu... See more\n\nMA · 7 source copies\n★TRUSTPILOT2021-06-18#2RATING 1/5\n\nThey scam people for money, dont believe me? Read this Source: Steam Subscribers/User Agreement NO GUARANTEES TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, NEITHER VALVE NOR ITS AFFILIA... See more\n\nWF · 7 source copies\n★TRUSTPILOT2016-10-28#3RATING 1/5\n\nSupport on site is terrible. Refunds not happend yet, despite games not working. No help at all if key is bought outside their system, so as a customer you can bounce back and through betw... See more\n\nPE · 7 source copies\n★TRUSTPILOT2021-09-27#4RATING 1/5\n\nThey are an amazing company!! My boyfriend paid for and downloaded a game without realizing it wasn’t the version he wanted. When he reached out, they gave him a full refund and responded in the same... See more\n\nVH · 7 source copies\n★TRUSTPILOT2026-07-20#5RATING 1/5\n\nI’ve used Steam for years, but lately, their sales have really lost their edge. I was hoping to score some solid discounts, but many games still feel overpriced, even during sales. Plus, the support response times can be frustratingly slow when issues arise.\n\nCR\n★TRUSTPILOT2025-12-10#6RATING 1/5\n\nI new here , but all my firends had great experience with this platform . They can make money\n\nZeinab Nematollahi\n★TRUSTPILOT2025-11-18#7RATING 1/5TEXT UNAVAILABLE\n\nNo text was included in the source record.\n\nEM\n★TRUSTPILOT2025-10-21#8RATING 1/5\n\nusing steam for over a decade and i have no words how good the platform is. some friends recommended it to me back in 2015 when we wanted to play csgo together and since then im loggin on it on a daily basis to check new games\n\nTrustpilot\n★TRUSTPILOT2025-05-09#9RATING 1/5\n\nSupport are never able to help you and only able to redicrect you to public linkBreaking there own TOSNot able to provider a refundNot able to provide a safe place for gamingBase on the game you play you can get scam.\n\nSym Link · 7 source copies\n★TRUSTPILOT2025-05-09#10RATING 1/5TEXT UNAVAILABLE\n\nNo text was included in the source record.\n\nHearnius\n★TRUSTPILOT2024-12-30#11RATING 1/5\n\nThis company allowed a single phishing scammer 76561199443342045 in 100's of its user community chat rooms \"Steam Chat\" the whole week of Winter Sales, 12-23-2024 - 2025 to spam spaceintrader a scam phishing website.Don't support Valve & Steam that support sca…\n\nFR · 7 source copies\n★TRUSTPILOT2024-11-15#12RATING 1/5\n\nVery realiable! Ive never had an issue over the 11 years ive had steam.\n\nJM\nビルドとそのソースファイル\n\nこのアーカイブでは、249 の重複行を統合し、16,569 の入力データから1行を除外した結果、16,319件の異なるレコードが残っています。あるレコードには、別のレコードですでに網羅されているイベントが記載されている場合があります。検索対象は、タイトル、著者、出典ラベル、および表示されている抜粋です。各レコードを開くと、保存されている全文が表示されます。\n\n4つのソースエクスポートをダウンロード ↓ファイル数およびSHA-256ハッシュ ↗元のビルドマニフェスト ↗\n\nこのバンドルには、ビルドの行数および記録されていた3つのJSONパスと一致する、復元されたエクスポートデータが含まれています。元のビルドでは、入力のハッシュやマスターCSVパスは記録されていませんでした。付属のマニフェストには、復元されたファイルと公開インデックスとの比較結果が記載されています。\n\nTrustpilot · steam_support_reviews.json354 行 · JSON エクスポート\nReddit · reddit_censored_forensics.json208 行 · JSON エクスポート\nGitHub · valve_ignored_bugs.json705 行 · JSON エクスポート；ファイル名はコレクターのラベルです\nマスター · TOTAL_VALVE_SCANDALS_MASTER_DB.csv15,302 行数 · 比較に使用したCSVエクスポートデータ\n裁判記録 · UNSEALED_EXHIBITS_AND_AML_DOSSIER.mdWolfire 対 Valve：公開された電子メール、ゲイブ・ニューウェルの証言録取、10月2019のAMLに関する自白\nマスター・ファクト · FACTS_AND_CITATIONS_DATABASE.md1,638 35の独占禁止法およびセキュリティの各分野における、個別の検証済み引用\nサポートアーカイブ · support_canned_refusals.html1,505 チケットの記録 · 137 に保存されたスクリーンショット · ライブ即時検索\nレコードのフィールド、テキストの欠落、およびエクスポートデータの重複\n\n日付、評価、カテゴリ、および状態は、元のエクスポートデータをそのまま再現しています。欠落しているURLはそのまま欠落したままとなります。「[削除済み]」または「[削除]」というマークは、誰が、なぜ投稿を削除したかを特定するものではありません。Steam / Valve によるフィルタリングは、テキストの一致によるものであり、関連性の評価ではありません。\n\n「エクスポート」を選択すると、抜粋付きのインデックスエントリがダウンロードされます。「レコードをダウンロード」を選択すると、保存された全文が含まれます。それぞれ 40,448-行マスター CSV そして 1,690-GitHub行のCSV このビルドでは、ソースの数ではなく、より広範なエクスポートが対象となっています。",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam 証拠アーカイブ — 『16,319』の資料"
          },
          {
            "level": 2,
            "id": null,
            "text": "ソースプラットフォーム"
          },
          {
            "level": 2,
            "id": null,
            "text": "ビルドとそのソースファイル"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/ja/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/ja/",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/TOTAL_VALVE_SCANDALS_MASTER_DB.csv",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive_manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive-inputs.zip",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive-inputs-manifest.json",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/unsealed_legal_and_aml/UNSEALED_EXHIBITS_AND_AML_DOSSIER.md",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/forensic_facts_1000/FACTS_AND_CITATIONS_DATABASE.md",
          "https://phishdestroy.io/steam_dossier/ja/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/github_valve_unpatched_bugs.csv"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ja/steam_evidence_archive.content.json",
      "export_json_sha256": "ec49f6fc98fa48266fec5f5dc3ec3ff94ca09e84d15cd318532eaf4d32acab26"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ja/support_canned_refusals.html",
      "language": "ja",
      "title": "Steam サポート拒否および定型返信のアーカイブ — 『Steam』資料集",
      "source_url": "https://phishdestroy.io/steam_dossier/ja/support_canned_refusals",
      "source_html_sha256": "51be0306f721f3cb4ec876b9b76e1e8d2cb824b3888bdb57e0d23a6b82141316",
      "exported_at": "2026-09-29T00:22:22.160Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "support_canned_refusals.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ja/support_canned_refusals.pdf?v=print-20260929-v5",
        "sha256": "6e35f4158daf7078bd0a069bd6eb8e0bd3a0b74ecd27ec5ae3ba59157e3218d5",
        "bytes": 255796,
        "pages": 2
      },
      "integrity": {
        "signed_object": "support_canned_refusals.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "support_canned_refusals.content.json.asc",
        "digest_file": "support_canned_refusals.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify support_canned_refusals.content.json.asc support_canned_refusals.content.json",
          "sha256sum -c support_canned_refusals.content.json.sha256"
        ]
      },
      "content": {
        "text": "このセクションが証明すること\n\nこのリポジトリには、137 に保存されているスクリーンショットや、1,505 で監査された被害者の申し立てが記録されており、Valveの自動化されたサポートチケット処理の詳細が示されています。これらは、OpenIDのリダイレクトや無断での API キー生成によってアカウントが乗っ取られた場合、Steamのサポート部門が技術的な調査を行わずに、体系的に標準化された定型的な拒否応答を採用していることを証明しています。アイテムの復元や監査証跡の開示を断固として拒否することで、同プラットフォームは、構造的な認証上の欠陥に対する全責任を、アカウントを乗っ取られた利用者へと転嫁しています。\n\nすべてのスクリーンショットは、第三者によってキャプチャされたものです。著作権およびコンテンツの権利は、それぞれの作成者およびプラットフォーム（Redditユーザー、Steamコミュニティの投稿者、Trustpilotのレビュー投稿者、XおよびYouTubeの投稿者）に帰属します。これらは、識別および公益上の報道を目的としてのみ転載されており、いかなる所有権も主張するものではありません。各資料には、その一次情報源へのリンクが記載されています。\n\nFigures reported on the source page\nMeasure\tReported value\tScope\n記録資料\t1505\t確認済みの被害者からの申し立ておよびチケットのスレッド\n保存されたスクリーンショット\t137\tローカルに保存された高解像度のチケットのキャプチャ\n復元率\t0.0%\tAPI件の主要な取引乗っ取り事件で、判決の覆しが認められた\nテンプレートの複製\t100%\tスタッフ間での台本（リプライ）の再利用（イリヤ、ロジャー、マーベリック）\n法医学的証拠：支援拒否を支える3つの柱\nPILLAR 01 · 入学案内証拠書類 R-014\n「The Roger Admission」：APIのMitM攻撃が確認された\n\nチケット対応 #1cp582i において、Steam のサポートスタッフ「Roger」は、攻撃者が API を通じて正当な取引をキャンセルし、ミリ秒単位でクローンボットによる取引にすり替えていることを文書で認めているが、アイテムの復元を拒否し、被害者に「地元のPC技術者」に相談するよう指示している。\n\n書面による入学許可を確認する ↗\nPILLAR 02 · エスカレーション証拠書類 R-012\n7-デイトレードの保有・不作為\n\nある被害者が、「7-」のデイトレード保留期間中に、ハッカーのアカウントのSteamID64を提供しました。サポートスタッフの「Artem」と「Ilya」は、仮想アイテムの希少性を理由に、盗まれたアイテムの凍結を拒否し、自動生成された定型文を用いてチケットを閉じた。\n\n複数スタッフによるトランスクリプトを確認する ↗\nPILLAR 03 · 方針証拠書類 R-002\n財産権をめぐる市場の希少性\n\nValveの公式アイテム復元ポリシーには、アイテムを復元すると「希少性が低下し、経済が過熱して、コミュニティマーケットにおけるアイテムの価値が下がる」ことになるため、アイテムは返還されないことが明記されています。\n\nポリシーのスクリーンショットを確認 ↗\n歴史的起源 · 22 3月 2018 から 2026 へ\n別紙H -003 · 8-パッチ未適用状態における攻撃対象領域\n記録上最古の貿易代替事例（22 3月 2018）\n\nValveが『Counter-Strike』のアイテムに対して、物議を醸した「7-」のデイ・トレード・クールダウンを課すちょうど1週間前、取引コミュニティは、この機能の最初の実際の運用事例を発見した。 Steam Web API トレードリダイレクトの脆弱性. 攻撃者はWebセッションを乗っ取り、APIの不正なキーを生成しました。 steamcommunity.com/dev/apikey 2によるFAの確認がないため、ボットがリアルタイムで取引をキャンセルしたり、取引先を変更したりすることが可能になる。\n\n3月2018年 公共啓発（PSA）警告： 「詐欺師たちはこのトレードオファーを自動的に検知し、あなたのアカウントでこれを拒否します。なぜなら、彼らはあなたのSteam APIのキーを握っているからです。その後、詐欺ボットが同じスキンを使ったトレードオファーを送信してきますが……あなたにはその違いに気づかないでしょう！」\n歴史的証拠の道\n22 3月2018: APIのスワップとして初めて記録された事例\n2019: サポートによる「マルウェア」の防御策の標準化\n2020: 「ヘルプリクエストの終了」スクリプトのセキュリティ強化\n2022–2026: BitBおよびQRコードを用いたフィッシングの自動化\nRedditのスレッド「2018」のオリジナルを開く ↗\nPrimary sources\n\n137 gallery cards refer to 78 distinct primary URLs. Images and repeated exhibit captions are omitted from this reading edition.\n\nFull visual archive and original captures",
        "headings": [
          {
            "level": 2,
            "id": null,
            "text": "Figures reported on the source page"
          },
          {
            "level": 2,
            "id": null,
            "text": "法医学的証拠：支援拒否を支える3つの柱"
          },
          {
            "level": 3,
            "id": null,
            "text": "「The Roger Admission」：APIのMitM攻撃が確認された"
          },
          {
            "level": 3,
            "id": null,
            "text": "7-デイトレードの保有・不作為"
          },
          {
            "level": 3,
            "id": null,
            "text": "財産権をめぐる市場の希少性"
          },
          {
            "level": 3,
            "id": null,
            "text": "記録上最古の貿易代替事例（22 3月 2018）"
          },
          {
            "level": 2,
            "id": null,
            "text": "Primary sources"
          }
        ],
        "links": [
          "https://www.reddit.com/r/csgo/comments/1cp582i/i_got_api_scammed_what_do_i_do_now/",
          "https://www.reddit.com/r/DotA2/comments/1e5ovy4/my_account_was_hacked_and_steam_support_refuse/",
          "https://www.reddit.com/r/Steam/comments/3b2abd/steam_will_no_longer_restore_scammed_items_item/",
          "https://www.reddit.com/r/GlobalOffensiveTrade/comments/863tk1/psa_urgent_huge_scam_happening_read_here_how_to",
          "https://phishdestroy.io/steam_dossier/ja/support_canned_refusals#gallery-grid"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ja/support_canned_refusals.content.json",
      "export_json_sha256": "409e5b8f4955268f59b64c7ebe244f36e461e8ceb3dff3abdf8e5a6723a65ada"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ja/valve_scandals_registry.html",
      "language": "ja",
      "title": "Valve スキャンダル・レジストリ — 『Steam』に関する資料",
      "source_url": "https://phishdestroy.io/steam_dossier/ja/valve_scandals_registry",
      "source_html_sha256": "2718ca5e63e1c05461e91b78c7b693837aa49aa71607e50b0fb5a7eadbf85c19",
      "exported_at": "2026-09-29T00:22:23.036Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "valve_scandals_registry.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ja/valve_scandals_registry.pdf?v=print-20260929-v5",
        "sha256": "970b72f81f5ed03f4237e835c023db6057cd9b72d534bd6f7c4e970272e0bfd6",
        "bytes": 141294,
        "pages": 6
      },
      "integrity": {
        "signed_object": "valve_scandals_registry.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "valve_scandals_registry.content.json.asc",
        "digest_file": "valve_scandals_registry.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify valve_scandals_registry.content.json.asc valve_scandals_registry.content.json",
          "sha256sum -c valve_scandals_registry.content.json.sha256"
        ]
      },
      "content": {
        "text": "スキャンダル・アーカイブの総覧\nValve スキャンダル・マスター・レジストリ — 160 報告されたインシデント\n出典レコード（RAW）：11,768\n\n報告済み。情報源あり。未解決。\n\nこのセクションが証明すること\n\nこのマスターレジストリは、プラットフォームに存在する恒常的な欠陥、削除されたコミュニティからの報告、およびValveのエコシステム全体における未解決の顧客サポート上の不備について詳述した、160が独自に検証した一次記録をまとめたものです。検証済みのTrustpilotへの紛争申し立て、GitHubのセキュリティ問題に関するアーカイブされたチケット、および規制当局による手続きなどを網羅しており、アカウントの復旧や顧客との紛争解決において繰り返し発生している体系的な機能不全を明らかにしています。\n\n← エグゼクティブ・ブリーフィングに戻る\n\n160 収集された記録：利用者による評価が付けられたサポート対応、表示されなくなったスレッド、報告されたまま放置されたプラットフォームの不具合、そしてValveがすでに説明を求められたインシデント。ここに記載されている内容はすべて、当社による解釈ではなく、各行には元の出典が明記されています。一つ開いて、ご自身で読んでみてください。\n\nソース・レコード\n11,768\nすべてのカテゴリーにおいて\nプラットフォームの欠陥\n3,372\nコミュニティから報告されたプラットフォームの欠陥\n削除されたスレッド\n109\nモデレーターによって削除されたRedditの投稿\nサポートに関する苦情\n471\nTrustpilotで確認済みの苦情\n実施の実現可能性\n認証ホストドメインのブロック\n\nOpenID認証ホストのドメインレベルでのブロックは、技術的には実装が容易です。あるリソースがSteamへのログインリダイレクトから除外されれば、その同じリソースの認証プロキシとして機能するサードパーティのドメインも、同じルールセットによってフィルタリングできます。実装の実現可能性に関する詳細な考察は、メインの報告書に記載されています。\n\n資料内の実施可能性についてはこちらをご覧ください →\nカテゴリ：Trustpilot サポートへの苦情（フィルタリング済みのネガティブなエスカレーション）176 一致するソースレコード · 重複は折りたたまれています\nConsumer Complaint2026-07-20\nAuthor: C***\n\nI’ve used Steam for years, but lately, their sales have really lost their edge. I was hoping to score some solid discounts, but many games still feel overpriced, even during sales. Plus, the support response times can be frustratingly slow when issues arise.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2026-07-20\nConsumer Complaint2025-05-09\nAuthor: S*** L***\n\nSupport are never able to help you and only able to redicrect you to public linkBreaking there own TOSNot able to provider a refundNot able to provide a safe place for gamingBase on the game you play you can get scam.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2025-05-09\nConsumer Complaint2024-12-30\nAuthor: F***\n\nThis company allowed a single phishing scammer 7656…2045 in 100's of its user community chat rooms \"Steam Chat\" the whole week of Winter Sales, 12-23-2024 - 2025 to spam spaceintrader a scam phishing website.Don't support Valve & Steam that support scams. Don't give your log in credentials to account hijacking scammers. This company also allows engagements of commercial advertising / spam for gambling in violation of its own Rules and Guidelines / Online Conduct. 7656…5023 proof - groups/deskinsfans key drop advertising, thanks TannerfromKD and Valve!*\"The Consumer Review Fairness Act (CRFA) protects people’s ability to share their honest opinions about a business’s products, services, or conduct, in any forum, including social media. The law protects a broad variety of honest consumer assessments, including online reviews, social media posts, uploaded photos, videos, etc. And it doesn’t just cover product reviews. It also applies to consumer evaluations of a company\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2024-12-30\nConsumer Complaint2024-07-31\nAuthor: A***\n\nhorrible company.randomly you get \"This account may have been accessed by someone else.\"this happened to me 3 times.the 3rd time they wanted a cd key.a spent useless cd key that nobody has any reason to keep laying around.i gave them the paypal bill for my first purchase back in 2015.i gave them a bill for my first phone number ever on the account.i still got the same email attached to the account.this company is literally a scam. nothing but a scam.they randomly claim you been accessed somewhere else and then require you to give them information no reasonable person would ever have, if not your done and have to rebuy everything.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2024-07-31\nConsumer Complaint2023-12-09\nAuthor: K***\n\nHad 288 euros in steam wallet, someone hacked my account even with two step verification, write a steam support for help but only answer was if something is spent in community market they can’t help.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2023-12-09\nConsumer Complaint2023-09-26\nAuthor: J***\n\nI was banned for saying \"Who let grandma on the PC\"and another for simply calling someone ignorant.Power tripping mods, devs who don't care, steam doesn't care. Yet allows racism/trolling/etc Fk steam, its a joke now.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2023-09-26\nConsumer Complaint2022-08-31\nAuthor: Anonymous\n\nSteam community is plain bad for a various reasons:1. Steam forums are a big mess, for example they allow users to post in any language and as result you get jumbled mess with posts in foreign languages together with English language posts. For example, If you check CS GO forums, you'll see half of posts are in Russian and half in English. I don't understand why such a big and international company would leave their forums so unorganized like that. All other normal companies have English only language allowed which is an international language and sometimes subforums for other languages like German, French and etc... so if French people want to post in French they go specifically in that sub-forum. But no, Steam doesn't care about this. Their forums is a one big mess.2. Moderation is biased and joke. I don't understand why such a big company like Steam can't afford to hire people for moderation and pay them. Instead they just recruit random people for moderation who do it for free and\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2022-08-31\nConsumer Complaint2022-05-28\nAuthor: J***\n\nThe login code never arrives. I hate Steam.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2022-05-28\nConsumer Complaint2021-11-08\nAuthor: N***\n\nThe service is terrible, I only signed up because I really like the game I wanted, but the rest is terrible, I hope to get something better soon.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-11-08\nConsumer Complaint2021-06-18\nAuthor: W***\n\nThey scam people for money, dont believe me? Read thisSource: Steam Subscribers/User Agreement NO GUARANTEESTO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, NEITHER VALVE NOR ITS AFFILIATES GUARANTEE CONTINUOUS, ERROR-FREE, VIRUS-FREE OR SECURE OPERATION AND ACCESS TO STEAM, THE CONTENT AND SERVICES, YOUR ACCOUNT AND/OR YOUR SUBSCRIPTION(S) OR ANY INFORMATION AVAILABLE IN CONNECTION THEREWITH.In short: You got a virus or your data leaked because of our software? Whoopsies we dont care, that isnt even legal or the last of their scammy stuff...\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-06-18\nConsumer Complaint2021-05-14\nAuthor: B***\n\nThe support is one of the worst I've ever seen.Useless support team.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-05-14\nConsumer Complaint2020-04-02\nAuthor: J***\n\nSteamcommunity has 15% fees, 15!!!!\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2020-04-02\nConsumer Complaint2020-03-27\nAuthor: H***\n\nWhat can I say? the support is one of the worst I've ever seen maybe the FUNCOM is much worse. If you tell the true on the steam forum you just got a BAN even if what you said did not violated the rules of the forum.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2020-03-27\nConsumer Complaint2018-03-16\nAuthor: B***\n\ndon't sign up will stick on your computer will kill your pc power you can't remove it from your pc even you deleted it will stay woking in the system\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2018-03-16\nConsumer Complaint2016-12-27\nAuthor: J***\n\nIn bloddy hate their page it's tiresome, it's in no way intuitive. I tried reaching out for support, but that is a maze.I'm simply trying to log in and redeem a key of a product I already bought, their search function is a joke. I f*u*c*k*i*n*g hate them. The layout is not like the how to video from the dealer, this can be done much simpler. I don't frigin care aboutn what other titles you have in store or what genre, I just want to redeem my key and install.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-12-27\nConsumer Complaint2016-10-28\nAuthor: P***\n\nSupport on site is terrible.Refunds not happend yet, despite games not working.No help at all if key is bought outside their system, so as a customer you can bounce back and through between bad support systems?? I wait for some other companies to compete in this market, for this can't be the best we as customers can expect.And do put an email up to find, instead of this stuppid website where you spend so long time trying to find a solution on, instead of a simple mail. Often the problem is not there, or if it's there just saying no help here???I need a response\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-10-28\nConsumer Complaint2016-06-26\nAuthor: V*** W***\n\nUseless support as always!\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-06-26\nConsumer Complaint2014-07-01\nAuthor: J***\n\nexpensive, and support team not willing to cooperate\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2014-07-01\nConsumer Complaint2014-04-15\nAuthor: B***\n\nWhen you pay for a program, you expect it too work. cant not buy or anything and have written to valve. but there is not a being done a damn thing abut it..\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2014-04-15\nConsumer Complaint2026-09-03\nAuthor: M***\n\nWorst platform ever wont give me a refund even though a game is unplayable because of bugs I won't ever be using the crap platform again I hope the platform breaks down for good piece fo crao\n\nTarget Domain: steamcommunity.com / steampowered.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2026-09-03\n\n該当するレコードはありません\n\n実行中のクエリを調整するか、別のカテゴリタブを確認してみてください。\n\n1 / 9",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Valve スキャンダル・マスター・レジストリ — 160 報告されたインシデント"
          },
          {
            "level": 2,
            "id": null,
            "text": "認証ホストドメインのブロック"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: C***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: S*** L***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: F***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: A***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: K***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: Anonymous"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: N***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: W***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: H***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: P***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: V*** W***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: M***"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/ja/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/ja/#autoban-feasibility-section",
          "https://www.trustpilot.com/review/steamcommunity.com"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ja/valve_scandals_registry.content.json",
      "export_json_sha256": "90ef220c48d01c0fd7e127d6a280c294195a05c438dee9a01762ffa53425b08a"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ja/output_steam_network/index.html",
      "language": "ja",
      "title": "「エクスプロイトではなくアーキテクチャ：オートメーション・ネットワーク」――『Steam』特集記事",
      "source_url": "https://phishdestroy.io/steam_dossier/ja/output_steam_network/index",
      "source_html_sha256": "2fa304ccebe67b85e4ae0dd79e93cb62b8b560ab921b19f69ee64717ee308222",
      "exported_at": "2026-09-29T00:22:23.250Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__index.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ja/output_steam_network__index.pdf?v=print-20260929-v5",
        "sha256": "fe1a33cf04c593a86249164326496da1763d73e8dd91fa308d17a415ee007feb",
        "bytes": 333549,
        "pages": 2
      },
      "integrity": {
        "signed_object": "output_steam_network__index.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__index.content.json.asc",
        "digest_file": "output_steam_network__index.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__index.content.json.asc output_steam_network__index.content.json",
          "sha256sum -c output_steam_network__index.content.json.sha256"
        ]
      },
      "content": {
        "text": "別紙VII・技術アーキテクチャ分析\nSteam ネットワークアーキテクチャ — プロトコルの忠実度とエコシステム分析\n\n自動化こそが、Valveの基盤です。 エクスプロイトではありません。\n\nこのセクションが証明すること\n\nこのモジュールは、Steamの自動化エコシステムを支える、252の開発者リポジトリ、3,320のGitHubプロファイル、および4,214のコントリビューターペアの技術的なトポロジーをマッピングしたものです。これにより、サードパーティ製の自動化ツールが、Valveの公式Connection Managerプロトコル、Protobufスキーマ、およびWeb APIに依存しており、悪用コードを含まないことが実証されています。 アルゴリズムによるSteamガード確認トークンの設計および66.7%,までの最低取引手数料の徴収を通じて、Valveは、自動化エコシステム運用の意図的な設計者であり、主要な商業的受益者として機能しています。\n\n← エグゼクティブ・ブリーフィングに戻る\n\nValveが規制当局、決済処理業者、あるいは詐欺被害者に対して説明を行う際、スキニングや市場操作の原因を「無許可の第三者による悪用」や「不正な自動化」に帰している。しかし、この252-リポジトリ・ネットワークの技術的な実態は、まったく逆の事実を明らかにしている： あらゆる自動化フレームワーク、トレーディングボット、ファーミングフリートは、Valve社によって設計、文書化、および収益化された公式のプロトコル定義、Web API、および認証メカニズムの範囲内で厳格に動作しています。\n\n法医学的所見：意図的な設計か、それとも不正な侵入か\n\nこのモジュールで分析するソフトウェアには、以下が含まれます―― SteamKit, node-steam-user, ValvePython/steam、および ArchiSteamFarm — 含まれる ソフトウェアの脆弱性ゼロ、メモリ破損ゼロ、ゼロデイ攻撃ゼロ. これらは、Valveの独自プロトコルであるConnection Manager（CM）クライアントプロトコル、Google Protocol Buffers（Protobufs）、およびWeb APIを、クリーンかつ堅牢に実装したオープンソースのライブラリです。Valveは、プログラムによるログインを受け付けるようこれらのAPIを設計し、アルゴリズムによる確認トークンを許可するようにSteam Guardを設計しました（identity_secret)、そして広告に記載されている15%の手数料を徴収しており、その金額は次第に高くなり、 Valveに有利な66.7%までの差 自動ボットネットが売却する高速カードやコモディティのドロップについて。\n\nPillar 01 · Protocol Fidelity\nProtobufの公式スキーマ\n\n自動化ライブラリは、セキュリティゲートを迂回することはありません。これらは、公式のProtobufメッセージをシリアル化します（steammessages_clientserver.proto) を、Steamクライアントとまったく同じように、TCP/WebSockets経由でValveの公式CMクラスタに直接送信します。\n\nPillar 02 · Algorithmic 2FA\nプログラム取引の承認\n\n数十億ドル規模の皮膚取引経済全体は、Valveの IEconService API およびモバイル認証アプリ「TOTP」のキー。Valveは、マシン間での取引確認を可能にするため、Steam Guardを意図的に設計しました。\n\n柱 03 · 商業受益者\n収益化されたマシントラフィック：最大66.7%の手数料下限\n\nValve 15%の手数料を謳っていますが、自動ボットが取引を行う高取引量の商品――トレーディングカード、ケース、および$0.03から$0.05の価格帯の安価なドロップ――においては、Valveの最低手数料下限である2セント（$0.01 Steam ＋ $0.01 パブリッシャー）が差し引かれます。 50% 66.7% への支払いを、Valve への支払いに変更する （2¢が3¢のカードから引き落とされ、販売者には1¢が残る）。さらに、アカウントごとに$5.00（スキャンされた車両だけで$26.8M）がかかる。\n\nモジュール01 · リポジトリおよびプロトコルの証拠\n公開向け開発者およびリポジトリインフラストラクチャ\n\nSteamの自動化を支える252のオープンソースリポジトリに関する詳細なフォレンジックカタログ。標準的なソフトウェアエンジニアリングツールが、Valveが公開したAPIのエンドポイントを、エクスプロイトを使用せずにどのように実装しているかを追跡しています。\n\n252リポジトリ\n4,554役割リンク\nリポジトリの証拠を確認する →モジュール02 · 生態系の人口動態\nグローバル・エンジニアリング・エコシステムの指標\n\n「Steam」の自動化エコシステムに貢献している3,320のソフトウェアエンジニアの地域別・組織別内訳。主要なテクノロジー企業における所属状況も含む。\n\n3,320エンジニア\n98,902接続ペア\n生態系の指標を確認する →モジュール03・インタラクティブなビジュアルグラフ\nインタラクティブ・プロトコルおよび開発者ネットワークのグラフ\n\nVis.jsの包括的なインタラクティブネットワークグラフにより、リポジトリ、プロトコルライブラリ（SteamKit、Steamworks、ASF）、およびプロジェクト間の貢献者の重複関係を可視化します。Steamの自動化エコシステムを支える、正当かつ相互に連携したオープンソースソフトウェアアーキテクチャを視覚的に示しています。\n\nインタラクティブVis.js エンジン\nクラスタの分離ライブ検索\nゼロエクスプロイト標準API\nインタラクティブなネットワークグラフを表示 →\n規制・法的背景（GDPRの記事「25」および消費者保護）：\n「設計時およびデフォルトでのデータ保護（Data Protection by Design and by Default）」の原則に基づき、APIの秘密鍵の自動生成、通知なしの取引キャンセル、および機械による資産の強制売却を許容するプラットフォームアーキテクチャは、プラットフォーム運営者によるアーキテクチャ上の選択である。 Valveが、損失は「外部からのサイバー攻撃」によるものだと主張して消費者の返金請求を体系的に却下していることは、攻撃経路がValve自身が意図的に設計したWeb APIアーキテクチャであることを隠蔽していることになる。\n\nインタラクティブビュー\n\n252-リポジトリの完全なインタラクティブ可視化、3,320-の開発者ネットワークグラフは、以下のURLからご覧いただけます。 network.html. 集計指標は BI指標 ページ。\n\n『Steam』資料集 · 技術アーキテクチャ・アーカイブ · 公開ソース記録 · すべての権利は人類に譲渡されました。",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam ネットワークアーキテクチャ — プロトコルの忠実度とエコシステム分析"
          },
          {
            "level": 3,
            "id": null,
            "text": "Protobufの公式スキーマ"
          },
          {
            "level": 3,
            "id": null,
            "text": "プログラム取引の承認"
          },
          {
            "level": 3,
            "id": null,
            "text": "収益化されたマシントラフィック：最大66.7%の手数料下限"
          },
          {
            "level": 2,
            "id": null,
            "text": "公開向け開発者およびリポジトリインフラストラクチャ"
          },
          {
            "level": 2,
            "id": null,
            "text": "グローバル・エンジニアリング・エコシステムの指標"
          },
          {
            "level": 2,
            "id": null,
            "text": "インタラクティブ・プロトコルおよび開発者ネットワークのグラフ"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/ja/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/ja/output_steam_network/valve_ru_farming_isolated.html",
          "https://phishdestroy.io/steam_dossier/ja/output_steam_network/steam_ecosystem_dashboard.html",
          "https://phishdestroy.io/steam_dossier/ja/output_steam_network/network.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ja/output_steam_network__index.content.json",
      "export_json_sha256": "5dbff45c6def76df7f5fffb2d5e9e0fc0876ea1b35f4c7b6930a657793d9784e"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ja/output_steam_network/network.html",
      "language": "ja",
      "title": "開発者・リポジトリエクスプローラー — 『Steam』特集",
      "source_url": "https://phishdestroy.io/steam_dossier/ja/output_steam_network/network",
      "source_html_sha256": "46eb70104895c1300c1b94ab2d058c6c3290a26a5a4a6055c370cfd6f0e45c42",
      "exported_at": "2026-09-29T00:22:24.343Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__network.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ja/output_steam_network__network.pdf?v=print-20260929-v5",
        "sha256": "43e84a43bdbbb7aea9efa2e7d301c71305c83caeeb128fcbdc4c0494cb6d0171",
        "bytes": 67584,
        "pages": 1
      },
      "integrity": {
        "signed_object": "output_steam_network__network.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__network.content.json.asc",
        "digest_file": "output_steam_network__network.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__network.content.json.asc output_steam_network__network.content.json",
          "sha256sum -c output_steam_network__network.content.json.sha256"
        ]
      },
      "content": {
        "text": "開発者・リポジトリエクスプローラー\n\nノードを検索します。記録された関係を確認します。\n\n公文書 / 収集された関連情報\nライブ検索\nレイヤーのフィルタ\n開発者総数3,320\nリポの合計252\n表示されたグラフ／コレクションのサブセット468 ノード • 1103 エッジ\n選択されたプロフィールレコード\n\n💡 グラフ上の任意のノードをクリックするか、「検索」欄に文字を入力すると、そのノードの収集された接続情報やソースパスを確認できます。",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "開発者・リポジトリエクスプローラー"
          }
        ],
        "links": []
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ja/output_steam_network__network.content.json",
      "export_json_sha256": "2ff5d7619675ec39adfeee9ed1fac74e7bd902a05d67f22c27fb5641733ae66e"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ja/output_steam_network/steam_ecosystem_dashboard.html",
      "language": "ja",
      "title": "数字で見るネットワークの全貌 — 「Steam」特集",
      "source_url": "https://phishdestroy.io/steam_dossier/ja/output_steam_network/steam_ecosystem_dashboard",
      "source_html_sha256": "458432a6a85dfa736924f1535d5221f261e2435aa9019f62b1e633c43eff225b",
      "exported_at": "2026-09-29T00:22:24.730Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__steam_ecosystem_dashboard.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ja/output_steam_network__steam_ecosystem_dashboard.pdf?v=print-20260929-v5",
        "sha256": "a7db19046caa84c502a44460eaeb120dc433950106389bef1c35195a4d3b598b",
        "bytes": 128356,
        "pages": 2
      },
      "integrity": {
        "signed_object": "output_steam_network__steam_ecosystem_dashboard.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__steam_ecosystem_dashboard.content.json.asc",
        "digest_file": "output_steam_network__steam_ecosystem_dashboard.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__steam_ecosystem_dashboard.content.json.asc output_steam_network__steam_ecosystem_dashboard.content.json",
          "sha256sum -c output_steam_network__steam_ecosystem_dashboard.content.json.sha256"
        ]
      },
      "content": {
        "text": "統計の概要 // ファイル 02\nSteam エコシステム・ダッシュボード — ネットワークの数値データ\n\n数字で見るネットワーク。\n\nこのセクションが証明すること\n\nこのダッシュボードは、3,320の開発者および252のリポジトリにわたる構造的情報を集約し、68のギャンブル特化型コードベースやクロスプラットフォームの接続ブリッジを特定します。実証データからは、地理的なクラスタリングや開発者の重複が浮き彫りになっており、サードパーティのスキン型ギャンブルインフラが、Steamのプラットフォームと統合された、組織化され、高度に相互接続されたソフトウェア産業として機能していることが示されています。\n\n← エグゼクティブ・ブリーフィングに戻る\n\n調査データベースの統合統計：地理的分布、上位企業、スキンギャンブルリポジトリ、およびアクティブな接続ブリッジ。\n\nスキャンされた開発者たち3320\nリポの合計252\nギャンブル関連のリポ68\n接続総数1,426\n自動化の構造と分野\nセクターI — Valve Corporation コア\n\n公式リポジトリおよびシステムソフトウェア。Valveの社員であるNephyrinとJoe Ludwigによる開発環境であることが確認されています。\n\nセクター II — 認証エンジンおよびプロトコルエミュレータ（SteamKit）\n\nValveのNephyrin氏と、スキンギャンブル開発者のDoctorMcKay氏が共同で作成した、リバースエンジニアリングされたネットワークライブラリ。\n\nセクター III — カードファーミングのクライアント（ArchiSteamFarm）\n\nSteamKitプロトコルのエミュレーターを利用して、バックグラウンドで数百万の偽クライアント（アイドル状態）を稼働させ、トレーディングカードを集める。\n\n開発者の地理的分布\nドイツ57\nアメリカ合衆国52\nカナダ48\nイギリス44\nポーランド30\nフランス28\nロシア連邦27\n中国27\n米国（ワシントン州）23\nオーストラリア19",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam エコシステム・ダッシュボード — ネットワークの数値データ"
          },
          {
            "level": 3,
            "id": null,
            "text": "セクターI — Valve Corporation コア"
          },
          {
            "level": 3,
            "id": null,
            "text": "セクター II — 認証エンジンおよびプロトコルエミュレータ（SteamKit）"
          },
          {
            "level": 3,
            "id": null,
            "text": "セクター III — カードファーミングのクライアント（ArchiSteamFarm）"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/ja/#briefing-heading"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ja/output_steam_network__steam_ecosystem_dashboard.content.json",
      "export_json_sha256": "9b85d6214bf340c0bb8a71fa567dddfc110cd2123866c3bedc1da28d6fa30189"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "ja/output_steam_network/valve_ru_farming_isolated.html",
      "language": "ja",
      "title": "コード、貢献者、フォーク — 『Steam』特集",
      "source_url": "https://phishdestroy.io/steam_dossier/ja/output_steam_network/valve_ru_farming_isolated",
      "source_html_sha256": "f80dc5d52cd41cb28e94f04da0027b00c23fe6eb6cf92dcd88d77e6c70b74b07",
      "exported_at": "2026-09-29T00:22:24.900Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__valve_ru_farming_isolated.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/ja/output_steam_network__valve_ru_farming_isolated.pdf?v=print-20260929-v5",
        "sha256": "e18fb4a71f43c9a1ce6cf1accb0aa322e20ebd3d662758717fbcd112733840d2",
        "bytes": 158832,
        "pages": 2
      },
      "integrity": {
        "signed_object": "output_steam_network__valve_ru_farming_isolated.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__valve_ru_farming_isolated.content.json.asc",
        "digest_file": "output_steam_network__valve_ru_farming_isolated.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__valve_ru_farming_isolated.content.json.asc output_steam_network__valve_ru_farming_isolated.content.json",
          "sha256sum -c output_steam_network__valve_ru_farming_isolated.content.json.sha256"
        ]
      },
      "content": {
        "text": "第2部 / 記録された関係に目を向ける\n\nフォーク、貢献、およびソフトウェアの依存関係は、明確な証拠となります。この見解では、収集された役割はそのまま維持されますが、雇用状況、セキュリティの回避、および犯罪への関与については、追加の情報源が必要となります。\n\nインタラクティブな機能マップを開く ↗\n公開情報源／役割監査\nコード。貢献者。フォーク。\n1. Nephyrin: フォークと貢献\n\n提供されたスナップショットによると、NephyrinはValveSoftware/Protonのコントリビューターであり、SteamRE/SteamKitおよびSteamRE/open-steamworksのフォーク元となっています。プロフィールデータにはValve Softwareと記載されています。これらの項目は個別に解釈する必要があります。\n\nフォークはリポジトリのコピーを記録します。このエクスポートには、SteamKitの認証コードへの変更を反映したコミットは含まれていません。\nリポジトリへの参照 / 履歴の確認\nSteamRE/SteamKit ↗ SteamRE/open-steamworks ↗\n2. パブリック機能：デスクトップクライアントを必要としない自動化\n\nSteamKit と node-steam-user は、Steam とのプログラムによる連携機能を提供します。ArchiSteamFarm は、複数アカウントによるカード収集について解説しており、依存関係として SteamKit2 を指定しています。\n\nこれらは具体的な自動化機能です。ヘッドレス実行は、排他的な商用利用やSteam Guardの回避を意味するものではありません。重要な点は、要求された認証情報、それによって実行可能なアクション、およびプラットフォームによって適用される制御です。\n\n出典：各プロジェクトのREADMEおよびArchiSteamFarm.csproj。機能マップには、文書化された各依存関係がリンクされています。\n3. JoeLudwig: hl2sdkのコントリビューターとしての肩書き\n\nこのスナップショットには、JoeLudwig が alliedmodders/hl2sdk、ValveSoftware/openvr、および ValveSoftware/source-sdk-2013. の貢献者として記載されています。これは確認可能なプロジェクト間の関係です。このエクスポートデータには、特定の SDK の変更が盗用や賭博目的での展開と結びついていることを示す証拠は含まれていません。\n\nリポジトリへの参照 / 履歴の確認\nalliedmodders/hl2sdk ↗ DoctorMcKay/node-steam-user ↗\n論理回路図 // 配線図\n接続ロジックのフローチャート：\nプロフィール・人間関係\nネフィリン / プロフィール集\n寄稿者：Proton。フォーク元：SteamKit および open-steamworks。\n▼ フォーク関係のまとめ\nコミュニティ図書館\nSteamRE／SteamKit\nSteamRE 組織によって管理されている、Steamの公開ネットワークライブラリ。\n▼ SteamKit2 の依存関係が宣言されました\n文書化された自動化\nJustArchiNET／ArchiSteamFarm\n複数のアカウントにわたるカード収集行為や、SteamKit2への依存関係について記載されています。\n証拠の検証／情報源の概要\n記録済み：個別の「contributor」および「forker」ラベル。\n実証済み：公共図書館は、Steamとのプログラム的な連携を支援している。\n未解決の問題：特定のコードの作成者、プラットフォームによる承認、および不正利用の帰属については、それぞれ個別の証拠が必要となる。",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "コード。貢献者。フォーク。"
          },
          {
            "level": 2,
            "id": null,
            "text": "1. Nephyrin: フォークと貢献"
          },
          {
            "level": 2,
            "id": null,
            "text": "2. パブリック機能：デスクトップクライアントを必要としない自動化"
          },
          {
            "level": 2,
            "id": null,
            "text": "3. JoeLudwig: hl2sdkのコントリビューターとしての肩書き"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/ja/investigation_part2.html#automation-map",
          "https://github.com/SteamRE/SteamKit",
          "https://github.com/SteamRE/open-steamworks",
          "https://github.com/alliedmodders/hl2sdk",
          "https://github.com/DoctorMcKay/node-steam-user"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/ja/output_steam_network__valve_ru_farming_isolated.content.json",
      "export_json_sha256": "be9680a4d3620b84e426fe39dc4f10c89f5e4f3fd61adb690880ae08d64a0d10"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "id/card_economy.html",
      "language": "id",
      "title": "Ekonomi kartu — Laporan Khusus Steam",
      "source_url": "https://phishdestroy.io/steam_dossier/id/card_economy",
      "source_html_sha256": "13fad41c602afc35dd7afd97d8340c704c35fb09ea13c8581e350e6d7c603610",
      "exported_at": "2026-09-29T00:22:26.155Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "card_economy.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/id/card_economy.pdf?v=print-20260929-v5",
        "sha256": "9ca76bf666216d413f80247a18690873427439cd06344a34641fdc597f707f7d",
        "bytes": 259265,
        "pages": 26
      },
      "integrity": {
        "signed_object": "card_economy.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "card_economy.content.json.asc",
        "digest_file": "card_economy.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify card_economy.content.json.asc card_economy.content.json",
          "sha256sum -c card_economy.content.json.sha256"
        ]
      },
      "content": {
        "text": "LAMPIRAN V — EKONOMI KARTU\nBot farm bukanlah kebocoran di toko Valve. Itu adalah pelanggan.\n\nSebuah akun Steam tidak dapat menerima satu kartu perdagangan pun sebelum melakukan pembelian $5.00 di toko. Sistem tersebut tidak dapat melakukan farming pada game yang tidak dimilikinya, dan juga tidak dapat melakukan farming pada game yang diberikan secara gratis. Jadi, sebelum sistem farming kartu otomatis menghasilkan apa pun, sistem tersebut harus terlebih dahulu membeli aksesnya — per akun, dengan harga yang dipublikasikan oleh Valve. Kemudian, klausul otomatisasi Valve menyebutkan, baris demi baris, persis apa yang dihasilkan oleh sistem pengumpulan tersebut; lisensinya melarang setiap cara yang digunakan untuk mengubah kartu hasil farming menjadi uang; dan pasarnya mengambil potongan saat kartu tersebut terjual — diiklankan di 15%, tetapi batas bawahnya adalah dua sen per penjualan, yang pada kartu dengan harga dalam satuan sen merupakan sebagian besar dari harga tersebut. Bahan bukti ini mengukur seberapa besar perdagangan tersebut, berapa biaya set untuk tingkat teratas dalam profil, dan apa yang dilakukan meja penegakan Valve dengan klausul yang sama ketika akun tersebut milik pedagang biasa.\n\nApa yang harus dibeli terlebih dahulu oleh sebuah peternakanBerapa harga satu level dalam satu setKedua sisi mejaSiapa yang mengatur sistem ekonomi kartu?\n$5.00Lakukan pembelian di toko terlebih dahulu sebelum akun dapat menerima kartu apa pun — halaman dukungan Valve sendiri\n13,876Permainan di Steam yang menerbitkan kartu koleksi, dengan 99,971 jenis kartu yang berbeda\n694,673Set kartu lengkap yang saat ini tersedia di stok milik 91 bot perdagangan yang terdaftar di bursa\n1,389,346Jumlah kartu akun dan kartu permainan yang telah digunakan oleh stok tersebut, setidaknya\n$9.99Harga median sebuah permainan kartu — satu set lengkapnya dijual dengan harga median sebesar $0.74\n97,114Anggota grup pertukaran kartu yang dalam daftar moderatornya tercantum seorang karyawan dengan kode Valve — § 08\n01 — Prosesnya\nApa itu peternakan sebenarnya, langkah demi langkah\n\nPenjelasan ini hanya didasarkan pada dokumentasi alat tersebut sendiri dan halaman dukungan Valve. Tidak ada satu pun hal dalam bagian ini yang disimpulkan secara implisit, dan tidak ada satu pun hal di dalamnya yang diperdebatkan oleh kedua belah pihak.\n\nLangkah 1\nIkut serta\n\nAkun tersebut tidak boleh terbatas. Halaman dukungan Valve melarang akun-akun yang dibatasi untuk \"Berpartisipasi di Pasar Steam\", dari \"Bertukar Steam barang komunitas (kartu koleksi, paket booster, permata, dll.)\" dan dari \"Mendapatkan Steam Tingkat Profil (Terkunci di tingkat 0) dan Kartu Perdagangan\". Intinya adalah uang: \"Anda harus berbelanja minimal $5.00 USD di toko Steam tersebut.\"\n\nLangkah 2\nBeli game\n\nKartu hanya bisa didapatkan dari game yang dimiliki. \"Kamu harus memiliki game tersebut di akun Steam-mu agar memenuhi syarat untuk mendapatkan kartu apa pun yang dijatuhkan dari game tersebut. Fitur berbagi keluarga bukanlah kepemilikan dan tidak dihitung.\" Rute-rute gratis juga ditutup: \"Game berbayar yang kamu dapatkan secara gratis selama masa promosi tidak bisa dimanfaatkan untuk mendapatkan kartu\", dan \"Kamu tidak bisa mendapatkan kartu dari game F2P tanpa mengeluarkan uang di dalamnya.\"\n\nLangkah 3\nMenganggur\n\nAlat ini masuk ke akun di jaringan Steam tanpa antarmuka pengguna, \"menganalisis lencana Anda\", menyusun daftar judul yang dapat ditanam dan memulai \"memainkan game yang memenuhi syarat dan secara berkala memeriksa apakah game tersebut sudah sepenuhnya di-farm.\" Penjelasan pengembangnya mengenai mekanisme tersebut: mekanisme tersebut \"tidak melakukan apa pun selain memberi tahu Steam bahwa kita sedang memainkan permainan tersebut.\"\n\nLangkah 4\nTetesan habis\n\nSetiap judul bersifat terbatas. \"Setiap game memiliki jumlah kartu yang bisa diperoleh dalam jumlah tetap. Begitu kamu sudah mendapatkan semuanya (sekitar setengah dari satu set lengkap), game tersebut tidak lagi layak untuk 'farming'.\" Sebuah pertanian yang ingin terus berproduksi harus terus membeli kartu. Pasokan kartu dibatasi oleh pembelian — hal ini memang dirancang demikian, dan menguntungkan Valve.\n\nLangkah 5\nPenarikan dana\n\nKartu tersebut akan keluar melalui salah satu dari tiga jalur: dijual di Pasar Komunitas, ditukar, atau dihancurkan menjadi permata. Masing-masing merupakan transaksi di Pasar Berlangganan atau pertukaran, dan § 3.D mengatur biaya sebagai berikut: \"Valve dapat mengenakan biaya atas transaksi di Pasar Langganan.\" Inilah langkah yang membuat seluruh proses tersebut menjadi pelanggaran — lihat 05.\n\nSumber-sumber, dibaca dan dikutip secara verbatim di 2026-09-22: Steam Dukungan — Akun Pengguna Terbatas ↗ · ArchiSteamFarm Pertanyaan yang Sering Diajukan (FAQ) ↗ · Valve — Steam Pertanyaan Umum tentang Kartu Perdagangan ↗ · Steam Perjanjian Pelanggan ↗ diarsipkan 2026-09-24 ↗. ArchiSteamFarm digunakan di seluruh halaman ini sebagai alat ukur, bukan sebagai terdakwa; dokumentasi resminya sendiri secara tegas menyatakan bahwa \"ASF tidak diberi wewenang oleh Valve\".\n\n02 — Skala\nSebelum sebuah peternakan menghasilkan satu sen pun, ia sudah mengeluarkan biaya sebesar Valve\n\nKarena akun dengan status terbatas tidak dapat menerima kartu, setiap akun dalam sebuah farm harus dibebaskan dari status terbatas sebelum dapat menghasilkan apa pun. Batas minimalnya telah diumumkan, dan biayanya dikenakan per akun.\n\nLuas lahan pertanian\tDari mana angka tersebut berasal\tNilai belanja minimum di toko agar memenuhi syarat untuk mendapatkan kartu tersebut\n10 akun\tBatas atas yang direkomendasikan oleh ASF — \"berdasarkan pedoman internal Valve, serta saran dari kami sendiri\"\t$50\n100–200 akun\tBatasan teknis dalam FAQ yang sama: \"Anda dapat menjalankan hingga 100–200 bot dengan satu alamat IP dan satu instance ASF\"\t$500 – $1,000\n120 akun\tKasus penegakan aturan nomor 3 di bawah ini — diblokir secara permanen\t$600\n170 akun\tKasus penegakan aturan nomor 2 di bawah ini — diblokir secara permanen selama Obral Musim Dingin 2017\t$850\n1,000 akun\tKasus penegakan hukum nomor 1 di bawah ini — perdagangan dilarang\t$5,000\n5,000 akun belum diverifikasi\tTimbangan operator dilaporkan dalam penyelidikan ini dan belum diverifikasi secara independen — lihat catatan mengenai sumber\t$25,000\n10,000 akun belum diverifikasi\tTimbangan operator dilaporkan dalam penyelidikan ini dan belum diverifikasi secara independen — lihat catatan mengenai sumber\t$50,000\n\nDua baris terakhir adalah satu-satunya angka di halaman ini yang bersumber dari laporan yang belum diverifikasi, bukan dari dokumen — angka-angka tersebut ditandai dalam tabel dan dijelaskan dalam catatan mengenai sumber, dan tidak ada hal lain di sini yang bergantung pada angka-angka tersebut. Kolom sebelah kanan merupakan perhitungan berdasarkan ambang batas $5.00 USD yang dipublikasikan oleh Valve dan tidak ada yang lain. Ini adalah lantai, bukan perkiraan biaya pengelolaan sebuah peternakan atau penghasilan yang diperoleh dari Valve: angka ini tidak termasuk game-game, yang harus dimiliki dan tidak boleh diperoleh secara gratis melalui promosi, serta tidak termasuk sekitar 15% yang dipotong oleh Community Market saat kartu-kartu tersebut dijual. Tidak ada angka pendapatan yang disebutkan di halaman ini.\n\nDan Valve sendiri telah menetapkan harga untuk pembagian kartu tersebut. Bagian FAQ Kartu Perdagangan-nya menyebutkan tingkat konversi dalam sistem permainan gratis (free-to-play) dalam dolar secara gamblang:\n\n\"Game gratis (free-to-play) memberikan kartu game berdasarkan pembelian yang kamu lakukan di dalam game.\" Untuk setiap $9 USD yang dibelanjakan (kira-kira) \"Sejak dimulainya Beta Kartu Perdagangan Steam, Anda akan mendapatkan satu kartu.\"\n\n— Valve, Steam Pertanyaan Umum (FAQ) Kartu Koleksi ↗ · telah diverifikasi secara harfiah 2026-09-22\n\nKartu perdagangan bukanlah barang gratis yang merugikan platform. Kartu tersebut adalah sesuatu yang Valve jual, dengan harga yang Valve umumkan — dan kemudian dikenakan biaya lagi saat dijual kembali. Itulah sebabnya, deskripsi yang jujur mengenai \"kartu farm\" bukanlah parasit. Hal ini pembeli grosir.\n\nSeberapa besar sebenarnya barang yang dibeli itu\n\nSemua yang tercantum mulai dari sini hingga akhir bagian ini merupakan hasil pengukuran, bukan laporan. Data sensus kartu diambil dari Steam, yaitu daftar harga lencana yang diterbitkan oleh Card Exchange; harga game-game tersebut bersumber dari API toko milik Valve sendiri; sedangkan stok bot diambil dari direktori bot publik yang dapat diakses siapa saja. Ketiga sumber tersebut dibaca di 2026-09-22 dan perhitungannya disajikan secara lengkap di bagian 08.\n\n13,876Permainan yang menggunakan kartu\n99,971Jenis-jenis kartu yang berbeda\n5 · 6 · 15Jumlah kartu per set: minimum, median, maksimum\n$0.74Harga median satu set yang sudah jadi\n$23,586.57Setiap set tersedia satu di pasaran\nSeberapa besar ukuran himpunan tersebut?\n\n13,876 permainan yang terdapat dalam set kartu tersebut. Valve sekitar setengahnya ditransfer ke satu akun mana pun.\n\n0\n1,250\n2,500\n3,750\n5,000\n5\n6\n7\n8\n9\n10\n11\n12\n13\n14\n15\nBerapa biaya lisensinya?\n\nHarga katalog game yang sama di toko Steam, dalam dolar AS.\n\n0\n1,000\n2,000\n3,000\n4,000\n<$1\n$1-3\n$3-5\n$5-10\n$10-20\n$20-40\n$40+\nHasil yang ditampilkan oleh set yang sudah jadi\n\nHarga pasar untuk satu set lengkap dari game-game yang sama.\n\n0\n1,500\n3,000\n4,500\n6,000\n<$0.50\n$0.50-1\n$1-2\n$2-5\n$5-10\n$10+\n\nBandingkan grafik kedua dan ketiga satu sama lain, dan pola pergerakan tersebut akan terlihat jelas tanpa perlu perhitungan: jumlah permainan berkumpul di kisaran puluhan dolar, sedangkan jumlah set yang dihasilkan berkumpul di bawah satu dolar. Keduanya merupakan hitungan dari permainan 13,876 yang sama, dengan satuan sumbu yang sama, sehingga perbandingan ini dilakukan antara dua ketinggian, bukan antara dua skala.\n\nItulah sisi penawaran. Sisi permintaan adalah bagian yang tidak perlu diiklankan oleh Valve, karena sudah tersedia untuk umum: sebuah direktori terbuka yang berisi bot-bot pertukaran kartu mencantumkan Saat ini, ada 91 bot yang memiliki 694,673 set lengkap dalam stok. Tanpa perlu login, tanpa perlu mengekstrak data dari pasar daring, tanpa data pribadi — angka stok tercetak di halaman tepat di samping nama masing-masing bot.\n\nJadikan saham itu sebagai satu-satunya unit yang penting di sini. Aturan Valve sendiri: \"Sebagian besar permainan akan mengeluarkan sejumlah kartu yang kira-kira setengah dari jumlah kartu dalam set kartu permainan tersebut… Kamu perlu mengumpulkan separuh lainnya dari set tersebut dari anggota komunitas lainnya.\" Satu akun tidak akan pernah bisa menyelesaikan satu set dengan bermain. Setidaknya dibutuhkan dua akun, masing-masing memiliki game tersebut, dan masing-masing menggunakan kuota drop yang hanya tersedia sekali per game. Kuota drop tidak akan terisi kembali.\n\n694,673Paket yang tersedia, 91 bot publik\n3,473,365Kartu, dengan jumlah minimal 5 kartu\n1,389,346Jumlah jatah yang telah digunakan, minimum\n2,602Akun yang hanya memiliki satu game, bot paling padat\nDi mana kumpulan 694,673 tersebut berada\n\nDua belas bot kartu terbesar dari 91 bot kartu yang terdaftar di bursa, berdasarkan jumlah set lengkap yang dimiliki. Sepuluh bot terbesar tersebut secara keseluruhan memiliki 248,115 set — 35.7% dari setiap item yang ada di papan.\n\n0\n11,250\n22,500\n33,750\n45,000\nCard Supply #4 (High)\nN!vq's Leveling (High)\nAlice [BOT] LEVEL-UP RARE SETS\nN!vq's Leveling (Low)\nDisco Lite Level Up\nN!vq's Leveling (Mid)\nbaty131store.net | Level Up\nKitten - Supreme\nArashirn | Level Up\nSH (Junior) Level Up\nDuobot.com - Overstock\nlvlupbot.com - godlike\n\nSetiap dari 1,39 juta alokasi tersebut berasal dari akun yang memiliki game tersebut, telah melewati batas $5.00, dan tidak akan pernah bisa menghasilkan item-item tersebut lagi. Ini adalah persediaan yang belum terjual pada 91 bot. Ini bukanlah ukuran pasar; ini adalah ukuran dari apa yang tersisa setelah pasar.\n\nAngka terakhir itu merupakan pembagian kategori, bukan jumlah total. Satu bot mencantumkan 14,310 set yang diambil dari hanya 11 game, sehingga setidaknya satu dari game tersebut diwakili oleh 1,301 set, yang berarti setidaknya ada 2,602 akun berbeda yang masing-masing membeli game tersebut. Itu adalah angka terkecil yang diizinkan oleh perhitungan aritmatika, dan hal ini berkaitan dengan satu bot dari sembilan puluh satu bot.\n\nApa yang tersirat dan tidak tersirat dari lantai ini\n\nBot-bot ini membeli kartu dari pemain biasa maupun dari akun farm — tarif pembelian yang mereka umumkan itulah yang menjadi inti dari direktori ini. Jadi, 1,39 juta kuota tersebut bukanlah jumlah akun yang dimiliki oleh petani. Angka-angka tersebut merupakan jumlah jatah drop yang dibatasi satu kali per akun dan satu kali per game, yang telah digunakan di suatu tempat di Steam dan akhirnya, karena tidak terjual, masuk ke stok komersial. Apakah akun di balik masing-masing item tersebut adalah akun farm atau akun remaja yang sedang menyelesaikan halaman lencana mereka, hal itu tidak mengubah apa yang dikumpulkan Valve: pembukaan $5.00, lisensi game, dan potongan komisi Pasar pada setiap transaksi — bukan 15%, melainkan 15% atau kedua nilai minimum satu sen tersebut, mana pun yang lebih besar, yang pada kartu dengan harga dalam sen jumlahnya jauh lebih besar. Perhitungannya ada di skala biaya di bawah ini. Itulah inti dari halaman ini, dan ini bukanlah keluhan terhadap para petani: perilaku yang sama yang menjadi dasar pengenaan biaya oleh Valve adalah perilaku yang dikutipnya, kata demi kata, ketika platform tersebut memblokir seseorang secara permanen atas dasar \"penggunaan komersial\".\n\nAngka tersebut juga merupakan batas bawah dalam arti lain. Angka tersebut hanya memperhitungkan saham yang yang terdaftar dan belum terjual hari ini tentang bot yang memilih untuk berada di direktori publik. Semua barang sudah terjual, semua barang disimpan secara pribadi, dan semua bot yang tidak terdaftar dalam direktori dikecualikan.\n\nDan bertani tidak bisa menutupi biayanya sendiri dengan harga yang ditetapkan Valve\n\nKeberatan yang jelas adalah bahwa sebuah farm membeli game murah untuk mencetak kartu mahal. API toko Steam sendiri justru menunjukkan hal sebaliknya. Dari 13,876 game yang memiliki kartu, harga yang ditetapkan adalah 13,713; 12,918 adalah judul berbayar dengan harga jual median sebesar $9.99. Harga median satu set yang sudah jadi adalah $0.74. Diperlukan dua lisensi per set. Jadi, harga median per set kira-kira $19.98 izin permainan untuk memproduksi dan pengembalian $0.74.\n\nDiukur pada 2026-09-22\tNilai\tApa yang disepakati\nHarga jual rata-rata, permainan berbasis kartu\t$9.99\tBiaya lisensi adalah bagian yang paling mahal dari transaksi tersebut, bukan kartunya\nGame dengan harga $4.99 atau kurang\t3,665 (28.4%)\tBahkan ekor yang murah pun lebih mahal daripada hasil yang dihasilkannya\nPermainan kartu termurah di toko ini\t$0.99\tDua lisensi, $1.98, untuk satu set yang biasanya dijual seharga di bawah $1.30\nGame yang harga paketnya lebih mahal daripada harga game itu sendiri\t323 dari 12,918 (2.5%)\tArbitrase kartu terhadap harga katalog Steam terjadi pada 1 dari setiap 40 permainan\nJudul-judul game gratis (free-to-play) dalam sensus\t795\tDan Valve menetapkan harga setiap drop-nya sebesar $9 dari pengeluaran dalam game\n\nHal ini menutup perdebatan ekonomi dengan keputusan yang menguntungkan Valve dan bertentangan dengan narasi yang lazim. Dengan harga yang ditetapkan oleh Valve sendiri, \"card farming\" adalah kegiatan yang merugi dan hanya menguntungkan jika lisensi diperoleh dengan harga di bawah harga katalog Steam — paket, penetapan harga regional, penjualan kembali utama. Kartu-kartu itu hanyalah sisa-sisanya. Pembelianlah yang menjadi peristiwa utamanya. Dan pembelian itu terjadi pada Steam.\n\nApa yang sebenarnya ditopang oleh pertanian tersebut\n\nJika semua potongan informasi tersebut disatukan, pertanian tidak lagi tampak sebagai sesuatu yang Valve toleransi, melainkan mulai tampak sebagai sesuatu yang Valve butuhkan. Setiap masukan yang disediakan pertanian merupakan keluaran yang dilaporkan atau ditagihkan oleh Valve. Ikuti satu akun bot ke luar:\n\nSatu akun yang dibuat secara massalseorang \"pelanggan grosir\", bukan kebocoran\nPenjualan game\n\nMembeli judul-judul game yang dikumpulkannya — mulai dari game kartu 13,876 hingga game shovelware $0.50 — karena kartu hanya bisa didapatkan dari game yang dimilikinya.\n\n\"Online\" & waktu bermain\n\nMembuat mereka menganggur agar menjatuhkan kartu, sehingga menambah angka jumlah pemain aktif dan jam bermain yang disebutkan Valve sebagai indikator keterlibatan — statistik tepat yang disebut § 4.C sebagai \"waktu bermain palsu\".\n\nPendaftaran\n\nHarus melewati batas akun $5.00 terlebih dahulu sebelum dapat menerima kartu — pembelanjaan di toko fisik Valve dicatat per akun.\n\nUang di dompet & biaya\n\nSetiap kartu yang dijual akan dialihkan kembali melalui Market, di mana biayanya bisa mencapai 66.7% untuk kartu bernilai rendah dan hasil penjualannya tetap terkunci di Dompet Steam.\n\nHubungan Masyarakat (PR) Tingkat 0\n\nLambang dan level Valve hanya ada karena adanya set yang dibuat — dan posisi teratas dalam tangga peringkat tersebut didominasi oleh bot (lihat § 03).\n\nHapus \"farm\", dan semua angka di atasnya akan berkurang — jumlah salinan game yang terjual lebih sedikit, skala \"online\"-nya lebih kecil, akun tersebut tidak pernah didaftarkan, biaya tidak pernah dipungut, dan level tersebut tidak pernah tercapai. Itulah sebabnya aturan yang melarang otomatisasi tetap ada di tengah jutaan akun otomatis: larangan itu hanyalah pilihan, sedangkan aktivitas itulah yang menghasilkan pendapatan.\n\nDan penarikan dana itu sendiri merupakan pemborosan nilai Valve—pajak dikenakan dua kali\n\nKartu tersebut bukanlah ujung dari siklus. Mekanisme Valve sendiri memungkinkan sebuah kartu dihancurkan menjadi permata, dan permata digunakan untuk membuat paket booster — tiga kartu lagi — yang kemudian dijual atau dihancurkan kembali. Setiap langkah dalam siklus ini merupakan transaksi di Pasar atau konversi, dan masing-masing dikenakan pajak. Arah siklus tersebut ditentukan oleh batas bawah biaya yang diukur di bawah ini dan tidak memerlukan model eksternal: setiap kartu yang dijual di dalamnya menyerahkan setidaknya dua sen, pada kartu yang diperdagangkan dengan harga tiga hingga lima, sehingga setiap putaran engkol menghasilkan kembali jumlah yang lebih sedikit daripada yang dimasukkan. Siklus ini menghancurkan nilai virtual dan memaksa dilakukannya transaksi baru yang dikenakan biaya untuk menggantikannya. Di sini tidak disebutkan angka mengenai besarnya kerugian tersebut — hasil per set bergantung pada tingkat kemunculan permata dan peluang booster yang belum diukur dalam penelitian ini.\n\nKartu koleksiitem yang diperoleh dari game yang dimiliki\n→\nPermatakartu dihancurkan, biaya dipungut\n→\nPaket tambahanbatu permata yang digunakan untuk membuat\n→\n3 kartu baruDijual di Market, biaya sudah dipotong\n↶\n\nDi sini hanya mekanisme permainannya yang dijelaskan, dan mekanisme tersebut merupakan milik Valve sendiri — kartu diubah menjadi permata, permata digunakan untuk membuat booster, dan booster menghasilkan kartu — masing-masing telah didokumentasikan dalam FAQ Kartu Perdagangan Steam, serta setiap langkahnya merupakan peristiwa Pasar yang dikenakan pajak. Sumber mekanisme loop: Valve, Steam Pertanyaan Umum tentang Kartu Perdagangan ↗.\n\nIni bukanlah sekadar momen. Ini adalah industri yang telah berdiri kokoh selama bertahun-tahun.\n\nSebuah tangkapan layar tunggal bisa saja sekadar kebetulan belaka. Oleh karena itu, direktori bot kartu publik dibaca sekali setiap kali ada obral musiman Steam, melalui Wayback Machine, dari tahun 2022 hingga 2026 — stok yang dibawa oleh bot-bot tersebut, serta akun-akun yang sama, dari satu obral ke obral berikutnya. Ekonomi ini tidak muncul dan menghilang begitu saja; ia bertahan, dengan inti operator yang stabil, dan mencapai puncaknya di atas tersedia tiga juta set lengkap di gudang Selama obral Musim Dingin 2023 — sekitar sepertiga juta kunci TF2 bernilai yang disimpan pada satu waktu, dalam satu direktori.\n\nKumpulan kartu lengkap yang disimpan di direktori bot publik, oleh Steam sale\n\nSatu cuplikan Wayback dari steam.supply/CardBots per obral musiman. Arahkan kursor untuk melihat nilai kunci TF2 berdasarkan tarif pada cuplikan tersebut.\n\n0.0M\n0.9M\n1.8M\n2.6M\n3.5M\nA’22\nS’23\nW’23\nS’24\nW’24\nS’25\nS’26\n401Akun bot yang berbeda-beda terdeteksi di seluruh bagian penjualan\n59Terdapat dalam 5 atau lebih dari 7 penjualan — inti yang stabil\n16Selalu hadir di setiap dari 7 ajang penjualan, 2022–2026\n3,22 jutaJumlah set puncak dalam stok (Musim Dingin 2023) ≈ $570k–790k dalam kunci\nSeperti apa tampilan tangga lencana penjualan jika dilihat dari puncaknya\n\nPermintaan sejalan dengan penawaran. Di kalangan masyarakat Tangga Lencana Obral Musim Panas 2024 diarsipkan 2026-07-16 ↗, akun peringkat pertama telah membuat lencana penjualan 1,740,645 kali — 1,74 juta set kartu yang masing-masing berisi sepuluh kartu, 17,4 juta kartu digabungkan menjadi satu hiasan profil. Dengan harga pasar yang berlaku di penjualan tersebut ($0.50 per set), itu berarti ~$870,000 berdasarkan nilai kartunya; dibeli dengan cara yang sebenarnya — kunci TF2 ditukar untuk menaikkan level bot dengan perbandingan sekitar 7,6 set per kunci — hal ini ~229,000 kunci, sekitar $410,000–$570,000 secara riil. Akun nomor dua: 552,000 set, ~$130,000–181,000. Tidak ada manusia yang bertaruh untuk ini. Akun ini dibeli, dan setiap tahap pembelian merupakan transaksi yang diselesaikan oleh Valve.\n\nMetode dan batasan: jumlah set-stock dihitung secara kumulatif dari semua bot yang tercantum dalam setiap snapshot; angka Jumlah bot per snapshot tidak dapat dibandingkan antar penjualan karena beberapa snapshot hanya menampilkan bot yang ditampilkan, sedangkan yang lain menampilkan direktori lengkap; oleh karena itu, stok dianggap sebagai batas bawah dari apa yang terlihat, bukan sensus. Nilai kunci menggunakan tingkat median set yang diiklankan per kunci dari setiap snapshot dan kunci TF2 $1.79–$2.49. Persistensi dilakukan berdasarkan SteamID64 di seluruh snapshot. Snapshot tahun 2021 menggunakan tata letak halaman yang lebih lama dan tidak disertakan. Data: garis-waktu-ekonomi-pertanian.json; tingkat lencana dari SteamLadder; harga yang ditetapkan dari Steam Card Exchange (tangkapan layar Wayback pada saat penjualan, $0.05 per kartu).\n\nDan armada yang sama tetap berada di sana ketika tidak ada promo penjualan yang sedang berlangsung\n\nKedua gambar di atas bukanlah dua populasi. Keduanya merupakan satu armada, yang difoto pada waktu yang berbeda. Direktori yang disebutkan di bagian atas bagian ini dibaca pada sebuah hari biasa di mana tidak ada obral musiman yang sedang berlangsung — 2026-09-22 — dan bahkan saat diam pun ia tetap bertahan 91 bot dan 694,673 set lengkap: sekitar 186,000 tombol TF2, $334,000–$464,000 nilai kartu, dalam keadaan tidak digunakan antara satu penjualan dan penjualan lainnya. Itulah beban minimum yang ditanggung oleh operasi tersebut saat tidak ada aktivitas apa pun.\n\nDan ini adalah operasi yang sama. Diidentifikasi berdasarkan SteamID64, 87 dari 91 bot yang sedang tidak aktif tersebut — 96% — juga muncul dalam tujuh cuplikan penjualan di atas, masing-masing berisi enam belas buah. Direktori ini bukanlah kios yang dibuka saat penjualan dan ditutup setelahnya; ini adalah inventaris komersial permanen yang jumlahnya telah bertambah hingga mencapai 3,22 juta set pada puncak musim dingin 2023 dan tidak pernah turun hingga nol. Obral adalah saat barang tersebut terjual. Hal ini juga terjadi sepanjang sisa tahun ini.\n\nDirektori penyimpanan, per bot\n\nSetiap kotak mewakili satu bot dalam direktori pada 2026-09-22, yang ditandai jika bot tersebut juga muncul dalam ketujuh cuplikan penjualan. Angka 91 adalah angka yang tercantum dalam direktori pada hari itu, bukan jumlah armada — Terdapat 401 akun berbeda yang muncul di berbagai cuplikan penjualan, dan direktori tersebut menampilkan potongan data yang berbeda pada hari-hari yang berbeda.\n\nTelah muncul dalam penjualan sebelumnya (87) Perubahan baru sejak snapshot terakhir (4)\n\nPembacaan dasar non-penjualan 2026-09-22 dari direktori publik yang sama, tanpa login. Nilai istirahat menggunakan tingkat set-per-kunci yang diiklankan masing-masing bot dan rentang kunci $1.79–$2.49 di atasnya. Tumpang tindih ditentukan berdasarkan SteamID64 terhadap tujuh snapshot penjualan. Karena daftar yang ditampilkan dan daftar lengkap berbeda-beda pada setiap snapshot, perbandingan ini dilakukan berdasarkan stok dan identitas, bukan jumlah pengguna. Perhitungan dalam bagian 08.\n\n03 — Tangga\nProduk lainnya adalah angka yang tertera di samping nama Anda\n\nKartu adalah bahan baku. Produk jadi berada di Level Steam, dan Valve menentukan harganya per set.\n\n100Steam Tingkat\nTingkat target — seret atau gunakan tombol panah\nHarga satu set lengkap, USD\n\n$0.20 adalah set lengkap termurah dalam sensus ini, $0.74 adalah median, $1.70 adalah rata-rata. Angka tersebut hanya mencakup kartu-kartu saja — tidak termasuk $5.00 item yang harus dibuka atau lisensi permainan.\n\n55,000Diperlukan XP\n550Set lengkap yang telah digunakan\n110Game yang layak dimiliki, mainkan sendiri\n$407.00Harga kartu-kartu tersebut\n1,100Tunjangan penurunan yang hangus, minimum\n$5,500.00$5.00 akan terbuka, jika tidak ada akun yang digunakan kembali\nSet lengkap yang telah diselesaikan, level 1 hingga 1,000\n\nSatu kerajinan lencana = satu set lengkap = 100 XP. Setiap level dalam kelompok sepuluh membutuhkan 100 XP lebih banyak daripada kelompok di bawahnya.\n\n0\n12,625\n25,250\n37,875\n50,500\n1\n250\n500\n750\n1000\n667\n550 sets\n\nLevel bukanlah hiasan yang diabaikan oleh Valve. Level tersebut terintegrasi ke dalam akun. Berdasarkan FAQ Kartu Perdagangan milik Valve sendiri, mengenai apa yang Anda peroleh saat membuat lencana: \"100 XP, yang dapat meningkatkan Level Steam Anda.\" Jika Level Steam Anda naik, batas jumlah anggota daftar teman Anda akan ditambah lima orang, dan mungkin saja kamu akan bisa menyesuaikan profilmu dengan fitur showcase.\" Dan mengenai paket tambahan: \"Level Steam Anda meningkatkan tingkat kemunculan booster pack: Level 10: +20%… Level 50: peningkatan tingkat kemunculan sebesar +100% (artinya, tingkat kemunculannya menjadi dua kali lipat).\"\n\nJadi, level ini menentukan dua hal Valve: berapa banyak orang yang boleh kamu jadikan teman, dan seberapa cepat kartu gratis masuk ke inventarismu. Yang kedua bersifat akumulatif — semakin banyak set yang telah Anda gunakan, semakin cepat platform tersebut memberikan lebih banyak materi kepada Anda. Valve telah memasukkan siklus reinvestasi ke dalam produk.\n\nNilai tukar telah ditetapkan dan dipublikasikan. Setiap pembuatan lencana menghabiskan satu set lengkap dan menghasilkan 100 XP; \"Kamu bisa membuat satu set untuk game yang sama paling banyak lima kali.\" Biaya XP per level meningkat setiap sepuluh level. Hal ini menghasilkan angka-angka berikut, dan tidak ada satupun di sini yang merupakan perkiraan:\n\nSteam Tingkat\tSet lengkap yang dikonsumsinya\tGame yang wajib kamu miliki agar bisa membuatnya sendiri\tPada level terendah yang pernah tercatat ($0.20)\tPada himpunan median ($0.74)\tSkala\n10\t10\t2\t$2.00\t$7.40\t\n50\t150\t30\t$30.00\t$111.00\t\n100\t550\t110\t$110.00\t$407.00\t\n200\t2,100\t420\t$420.00\t$1,554.00\t\n500\t12,750\t2,550\t$2,550.00\t$9,435.00\t\n667\t22,579\t4,516\t$4,515.80\t$16,708.46\t\n\n667 bukanlah angka hipotetis. Angka tersebut merupakan level tertinggi yang diiklankan oleh satu bot di direktori publik sebagai level yang dapat dicapai oleh pelanggan, dari 33,359 set yang dimilikinya di 6,117 game. Kolom keempat menunjukkan harga tangga yang sama dibandingkan dengan set lengkap termurah di mana pun dalam sensus; kolom kelima dibandingkan dengan harga median. Keduanya merupakan harga pasar untuk kartu-kartu tersebut saja dan sama sekali tidak termasuk $5.00 pembukaan serta lisensi game.\n\nBagaimana kurva tersebut diverifikasi, karena Valve tidak mempublikasikannya\n\nValve menunjukkan tingkat pemberian lencana (\"Setiap 100 XP akan memberimu tambahan Steam Level\") lalu melakukan lindung nilai terhadapnya — \"(setidaknya untuk awalnya)\" — tanpa mempublikasikan peningkatan tersebut. Kurva yang digunakan di atas adalah kurva standar, di mana setiap level dalam blok sepuluh membutuhkan 100 XP lebih banyak daripada blok di bawahnya. Hal ini diverifikasi berdasarkan direktori, bukan sekadar asumsi: untuk setiap bot yang batas maksimum yang diiklankannya dibatasi oleh persediaannya, bukan oleh batas lima kerajinan per permainan, level yang dihitung dari kurva ini persis sama dengan level yang diumumkan oleh bot — 541 berbanding 541, 494 berbanding 494, 464 berbanding 464. Di mana batas atas berlaku, angka yang dihitung justru sedikit lebih tinggi, yang memang seharusnya terjadi pada batas atas yang juga bergantung pada kedalaman skuad per pertandingan. Tidak ada klaim yang dibuat mengenai kurva di atas level 667.\n\nBaca skema di samping bagian 02, dan gambaran bisnisnya akan terlihat. Untuk menempatkan satu akun di level 500, seseorang harus mengumpulkan 12,750 set lengkap. Setiap set tersebut membutuhkan setidaknya jatah drop dari dua akun, masing-masing akun tersebut telah melewati gerbang $5.00, dan masing-masing memiliki game tersebut. Satu angka hiasan di bagian atas sebuah profil didukung oleh setidaknya 25,500 jatah drop yang telah digunakan di bawahnya. Valve tidak akan mengalami kerugian dalam transaksi tersebut. Valve adalah pihak lawan dalam setiap bagian dari transaksi tersebut.\n\n04 — Data statistik\nKlausul tersebut tidak menjelaskan pertanian secara samar-samar. Klausul tersebut menjabarkannya secara rinci.\n\n§ 4.C bukanlah kalimat larangan umum terhadap bot. Contoh-contoh yang tercantum di dalamnya menyebutkan, satu per satu, dua hal yang dihasilkan oleh sebuah “card farm”.\n\n\"Anda dilarang menggunakan skrip, bot, makro, atau sistem lain yang tidak dikendalikan oleh manusia ('Otomatisasi') dalam bentuk apa pun untuk berinteraksi dengan Konten dan Layanan di Steam dengan cara apa pun, termasuk namun tidak terbatas pada:\n\nMengotomatiskan proses pembuatan akun Steam,\nMemalsukan statistik permainan (misalnya, memanipulasi jumlah kemenangan atau kekalahan, XP, waktu bermain),\nMendapatkan hadiah atau kemajuan tanpa masukan yang sesungguhnya dari pengguna,\n\"Berpartisipasi dalam sistem penilaian (seperti tinjauan sejawat atau 'overwatch') melalui cara otomatis, termasuk memengaruhi hasil atau melaporkan pengguna melalui tindakan yang telah diprogram, bukan berdasarkan penilaian yang didasari pemahaman.\"\n— Steam Perjanjian Pelanggan § 4.C ↗ diarsipkan 2026-09-24 ↗ · diambil dan dikutip secara harfiah 2026-09-22\n\"…waktu bermain\"\n\nJam-jam tidak produktif bukanlah jam-jam fiktif. Bagian FAQ ASF menjawab pertanyaan tersebut secara langsung — \"Mengapa durasi bermain game yang diperoleh melalui ASF tidak bertambah?\" — bersama: \"Memang begitu, tapi tidak secara real-time. Steam mencatat durasi bermainmu dalam interval tetap dan menjadwalkan pembaruan untuk data tersebut… biasanya diperbarui setiap 30 menit sekali.\"\n\nJam-jam tersebut tercatat dalam data Valve, muncul di halaman toko Valve, dan masuk ke dalam jumlah pemain aktif yang dipublikasikan oleh Valve secara mandiri Steam Grafik ↗ diarsipkan 2026-09-23 ↗. Dalam angka-angka tersebut, akun yang tidak aktif tidak dapat dibedakan dari akun yang aktif. Angka keterlibatan yang dipublikasikan oleh platform tersebut dihitung berdasarkan populasi yang, sesuai aturan platform itu sendiri, mencakup akun-akun yang tidak aktif.\n\n\"…tanpa masukan yang sejati dari pengguna\"\n\nItu adalah definisi dari “idled card drop”, yang ditulis oleh Valve. Definisi tersebut juga mencakup Level Steam, lencana, syarat untuk mendapatkan booster pack, serta XP profil yang menyertainya — FAQ ASF mengonfirmasi alat tersebut \"tetap memungkinkan pengguna untuk menerima paket booster\", karena cara masuknya sama seperti klien resmi.\n\nJadi, sistem imbalan dan tindakan terlarang merupakan satu mekanisme yang dilihat dari dua sisi. Valve merancang agar imbalan dihasilkan berdasarkan waktu, bukan berdasarkan keterampilan, lalu membuat ketentuan yang melarang produksi imbalan melalui cara apa pun selain oleh seseorang yang menghabiskan waktu tersebut.\n\n05 — Perangkap untuk penggunaan komersial\nSetiap orang yang keluar dari kartu yang telah dibeli merupakan tindakan yang dilarang oleh lisensi — dan Valve mengenakan biaya di pintu masuk\n\nInilah bagian yang tidak bisa diatasi hanya dengan melakukan \"farming\" secara bertanggung jawab. Lisensi ini diperuntukkan bagi penggunaan pribadi dan non-komersial, dan sebuah kartu baru layak untuk \"difarming\" pada saat kartu tersebut tidak lagi bersifat pribadi.\n\n§ 2.A — lisensi\n\n\"Valve dengan ini memberikan, dan Anda menerima, lisensi serta hak non-eksklusif untuk menggunakan Konten dan Layanan bagi keperluan Anda penggunaan pribadi dan non-komersial (kecuali jika penggunaan komersial secara tegas diizinkan dalam ketentuan ini atau dalam Ketentuan Berlangganan yang berlaku).\"\n\n§ 2.G — pembatasan\n\n\"Anda tidak berhak atas: … (iii) memanfaatkan Konten dan Layanan atau bagian mana pun darinya untuk tujuan komersial apa pun, kecuali jika secara tegas diizinkan di bagian lain dalam Perjanjian ini (termasuk Ketentuan Berlangganan atau Aturan Penggunaan apa pun).\"\n\n§ 3.D — biaya\n\n\"Valve dapat mengenakan biaya atas transaksi di Pasar Langganan. \"Segala biaya akan diberitahukan kepada Anda sebelum transaksi selesai.\"\n\nBaca ketiga hal tersebut secara bersamaan, dan posisi tersebut akan ditutup\n\nKartu yang disimpan tidak memiliki nilai bagi sebuah farm. Kartu yang dijual, ditukar, atau dihancurkan menjadi permata telah digunakan untuk menghasilkan nilai — dan Valve telah menyebutkan dalam surat penegakan hukumnya sendiri istilah yang mereka gunakan untuk hal tersebut: operator 170 bot diberitahu bahwa akun tersebut \"digunakan untuk mengumpulkan kartu koleksi secara ilegal di Steam, serta kegiatan-kegiatan terkait, tidak hanya yang bersifat komersial.\" Dalam hal ini, kartu-kartu tersebut sudah beredar di pasar. Penjualannya sudah selesai. Biayanya sudah dibayarkan. Larangan itu baru diberlakukan setelahnya.\n\nBiaya di pintu itu bukan 15%. Pada kartu yang disewakan, biayanya mencapai dua pertiga.\n\n§ 3.D cadangan \"biaya\". Pada kartu yang sebenarnya diproduksi oleh sebuah peternakan, biaya tersebut sama sekali tidak sama dengan angka ~15% yang diiklankan. Pasar Komunitas mengambil 5% Steam biaya transaksi dan 10% biaya permainan, masing-masing dengan batas bawah sebesar $0.01 (FAQ Pasar Komunitas milik Valve). Pada kartu yang ditawarkan seharga satu sen, lantai-lantai tersebut adalah harganya: pembeli membayar tiga sen, dua di antaranya merupakan biaya. Aturan pembulatan ke bawah mengubah angka 15% menjadi pungutan efektif yang naik hingga 66.7% persis di mana pasar kartu itu berada — beberapa sen per kartu.\n\nBiaya efektif atas penjualan di Pasar Komunitas, berdasarkan harga yang diminta penjual\n\n5% Steam + 10% permainan, masing-masing minimal $0.01. Bagian yang diarsir adalah rentang harga di mana kartu perdagangan benar-benar diperdagangkan — kira-kira $0.03–$0.05 per kartu.\n\n0%\n10%\n20%\n30%\n40%\n50%\n60%\n70%\ncards\n$0.01\n$0.10\n$0.20\n$0.30\n$0.40\n$0.50\n66.7%\nPenjual menginginkan\tSteam 5% (min $0.01)\tPertandingan 10% (menit $0.01)\tBiaya ditanggung pembeli\tBiaya gabungan\n$0.01\t$0.01\t$0.01\t$0.03\t66.7%\n$0.03\t$0.01\t$0.01\t$0.05\t40.0%\n$0.05\t$0.01\t$0.01\t$0.07\t28.6%\n$0.08\t$0.01\t$0.01\t$0.10\t20.0%\n$1.00\t$0.05\t$0.10\t$1.15\t13.0%\n\nBiaya permainan sebesar 10% masuk ke aplikasi yang menerbitkan kartu tersebut; 5% menjadi milik Valve sendiri, sedangkan untuk judul-judul dan item inventaris dasar milik Valve, seluruh biayanya menjadi milik Valve. Bagaimanapun juga, uang tersebut keluar dari kantong petani — menjual kartu seharga tiga sen menghasilkan satu sen dan mengorbankan dua sen. Kalikan itu dengan ratusan ribu penjualan kartu di bawah lima sen yang dihasilkan oleh sebuah farm dan \"biaya yang dapat dikenakan oleh Valve\" adalah model bisnis, bukan sekadar catatan kaki. Sumber: Steam Pertanyaan Umum (FAQ) Pasar Komunitas — Biaya ↗ diarsipkan 2026-09-21 ↗, dibaca 2026-09-22; kurva tersebut bersifat aritmetika berdasarkan kedua suku bunga yang dipublikasikan tersebut dan batas bawah $0.01-nya.\n\nTidak ada pengaturan alat ini yang dapat menghindari hal ini. Alat ini dapat dijalankan oleh satu orang, pada satu akun, dengan pengendalian diri yang sempurna — dan begitu orang tersebut menjual satu kartu hasil farming untuk mendapatkan dana dompet, hukuman yang sama sebagaimana tercantum dalam § 2.G akan berlaku baginya sebagaimana berlaku bagi operator yang memiliki sepuluh ribu kartu. Oleh karena itu, Valve telah menyisihkan sebuah pelanggaran yang dapat digunakannya terhadap hampir semua penjual kartu di pasarnya sendiri, namun menolak untuk menggunakannya terhadap hampir semua dari mereka. Aturan yang diterapkan dengan cara seperti itu bukanlah aturan. Itu hanyalah sebuah pilihan. Pertanyaan yang diajukan pameran ini bukanlah mengapa para “card farmer” ditoleransi; melainkan mengapa opsi yang sama diterapkan terhadap seorang pengguna individu yang menjual kartu, sementara ekonomi kartu komersial yang didukung oleh kartu-kartu tersebut — layanan perdagangan, bot naik level, dan penjual massal — tetap beroperasi secara terbuka, di mana salah satu kelompok terbesarnya dimoderasi oleh seorang karyawan Valve (§ 08). Pelanggaran tersebut ditujukan kepada pemilik kecil dan diabaikan bagi sistem otomatis.\n\n06 — Catatan penegakan hukum\nTanpa pemberitahuan, datang bergelombang, dan menyebar melalui nomor telepon\n\nValve mencantumkan kewenangan tanpa pemberitahuan sebelumnya dalam perjanjian itu sendiri, tepatnya pada klausul yang berada tepat setelah klausul otomatisasi.\n\n\"Valve berhak membatasi atau menghentikan Akun Anda atau Langganan tertentu atas perilaku atau aktivitas apa pun yang melanggar hukum, merupakan Kecurangan atau Otomatisasi, atau melanggar Aturan Perilaku Daring Steam. Anda mengakui bahwa Valve tidak diwajibkan untuk memberikan pemberitahuan kepada Anda sebelum menghentikan Langganan dan/atau Akun Anda.\"\n\n— Steam Perjanjian Pelanggan § 4.D ↗ diarsipkan 2026-09-24 ↗ · telah diverifikasi secara verbatim 2026-09-22\n\n1,000+ bot · dilarang berdagang. \"Sepertinya akun ini digunakan untuk mengelola jaringan akun bot. Penggunaan bot merupakan pelanggaran terhadap Perjanjian Pelanggan Steam.\"\n\n170+ bot · diblokir selamanya, Obral Musim Dingin 2017. \"Akun ini digunakan untuk mengumpulkan kartu koleksi secara ilegal di Steam, serta kegiatan terkait lainnya—tidak hanya kegiatan komersial. Akun tersebut telah diblokir secara permanen dan Tim Dukungan Steam tidak dapat memberikan bantuan lebih lanjut terkait masalah ini.\"\n\n120+ bot · diblokir secara permanen. \"Akun ini dan akun-akun lainnya digunakan untuk membanjiri infrastruktur jaringan kami, yang merupakan pelanggaran terhadap Steam tata tertib daring.\"\n\n— Steam Pesan dukungan yang dikutip dalam ArchiSteamFarm FAQ, bagian \"Apakah ada yang diblokir karena hal itu?\". Sumber ↗ · telah diverifikasi secara verbatim 2026-09-22\nKasus 4 — Juni 2025, VAC larangan terhadap CS2 yang tidak beroperasi\n\nSebuah kejadian yang terjadi setelah ketiga kejadian di atas tercatat dalam sistem pelacakan proyek itu sendiri: akun-akun yang hanya membiarkan Counter-Strike 2 dalam keadaan tidak aktif melalui alat tersebut menerima VAC larangan — yang berkaitan dengan pencegahan kecurangan, bukan yang bersifat administratif. Pendapat pengelola adalah bahwa membiarkan perangkat dalam keadaan idle tidak dapat menyebabkan hal tersebut, karena hal itu \"tidak melakukan apa pun selain memberi tahu Steam bahwa kita sedang memainkan permainan tersebut.\" Penyebabnya masih menjadi perdebatan. Namun, fakta bahwa akun-akun tersebut diblokir tidak diragukan lagi.\n\n— ArchiSteamFarm diskusi #3440, dibuka pada 26 Juni 2025 ↗ · baca 2026-09-22\n\nBagaimana sebuah akun utama bisa mati\n\nDalam utas yang sama, seorang kolaborator proyek menjelaskan aturan pemblokiran: akun dapat diblokir \"secara berantai\", jika mereka menggunakan nomor telepon yang sama — \"Mungkin ini hanya satu larangan VAC, yang kemudian menyebar ke akun-akun 'bersih' yang terhubung dengan akun yang diblokir tersebut.\"\n\nSteam Guard memerlukan nomor telepon. “Farm” dibangun berdasarkan nomor telepon operator. Jadi, penindakan tidak berhenti pada akun sekali pakai: penindakan dilacak melalui pengenal bersama hingga ke akun yang menyimpan perpustakaan, daftar teman, dan inventaris. Itulah mekanisme yang dijelaskan oleh salah satu kolaborator proyek mengenai bagaimana satu tindakan dapat menghapus akun utama operator beserta jaringan akun palsu tersebut — dan itulah sebabnya kerugian dalam gelombang penegakan aturan tidak diukur dalam jumlah akun $5. (Dijelaskan oleh seorang kontributor proyek dalam diskusi ASF GitHub #3440; tidak ada konfirmasi resmi Valve atau preseden formal yang tercatat.)\n\nParagraf yang sama, dengan selisih waktu lima tahun, dari tiga agen yang berbeda\n\nKlausul yang menyatakan bahwa bertani merupakan pelanggaran — yaitu penggunaan komersial atas lisensi pribadi non-komersial — tidak hanya berlaku untuk pertanian. Ini adalah alasan standar yang diberikan Steam saat menutup akun karena aktivitas perdagangan, dan alasan tersebut disajikan dalam bentuk templat. Di bawah ini terdapat tiga contoh, yang dipublikasikan oleh orang-orang yang menerimanya, dengan selang waktu lima tahun, dari tiga agen berbeda yang disebutkan namanya.\n\nPesan dari Tim Dukungan Steam pada 29 September pukul 19.56\n\n\"Akun yang Anda gunakan untuk menulis ini telah diblokir karena melanggar ketentuan Perjanjian Pelanggan Steam. Akun tersebut telah teridentifikasi digunakan untuk tujuan komersial berdasarkan aktivitas perdagangan, laporan dari komunitas, dan faktor-faktor lainnya.\"\n\nPenguncian ini bersifat permanen dan Steam Tim Dukungan tidak dapat membantu Anda lebih lanjut terkait hal ini.\n\nKarena kami telah memberikan semua informasi yang kami miliki, saya akan menutup permintaan bantuan ini. Harap diperhatikan bahwa Anda tidak akan menerima balasan lebih lanjut mengenai masalah ini.\n\nSalam,\n\"Hal\"\n\nPermintaan bantuan ini telah ditutup.\n29 September 2020. Diposting oleh penerima dengan komentar \"Selamat jalan, RIP Trading.\" — @gergelyszabo94 ↗\nPesan dari Tim Dukungan Steam pada 12 Juli pukul 22:41\n\n\"Akun yang Anda gunakan untuk menulis ini telah diblokir karena melanggar ketentuan Perjanjian Pelanggan Steam. Akun tersebut telah teridentifikasi digunakan untuk tujuan komersial berdasarkan aktivitas perdagangan, laporan dari komunitas, dan faktor-faktor lainnya.\"\n\nPenguncian ini bersifat permanen dan Steam Tim Dukungan tidak dapat membantu Anda lebih lanjut mengenai hal ini.\n\nKarena kami telah memberikan semua informasi yang kami miliki, saya akan menutup permintaan bantuan ini. Harap diperhatikan bahwa permintaan bantuan selanjutnya yang diajukan terkait pemblokiran akun mungkin akan ditutup tanpa balasan.\n\nSteam Dukungan\n\"Vido\"\n\nPermintaan bantuan ini telah ditutup.\n12 Juli 2024, antarmuka bahasa Portugis. Penerima pesan ini adalah seorang pemain CS2 profesional: \"Sudah menghubungi layanan dukungan Steam, tapi yang saya terima hanya balasan otomatis… Saya tidak bisa bermain Faceit dan juga tidak bisa mengikuti pertandingan profesional.\" — @prcs25 ↗ diarsipkan 2024-07-15 ↗\nDikutip oleh penerima, r/steamsupport\n\n\"Halo, Akun yang Anda gunakan saat ini telah diblokir karena melanggar ketentuan Perjanjian Pelanggan Steam. Akun tersebut telah teridentifikasi digunakan untuk tujuan komersial berdasarkan aktivitas perdagangan, laporan dari komunitas, dan faktor-faktor lainnya.\"\n\nPenguncian ini bersifat permanen dan Steam Tim Dukungan tidak dapat membantu Anda lebih lanjut terkait hal ini.\n\nKarena kami telah memberikan semua informasi yang kami miliki, saya akan menutup permintaan bantuan ini. Harap diperhatikan bahwa permintaan bantuan yang diajukan di masa mendatang terkait pemblokiran akun mungkin akan ditutup tanpa balasan.\n\nSteam Dukungan\n\"Sally\"\n\nTelah diterima sebanyak tiga kali, berdasarkan tiga permintaan terpisah.\n29 Maret 2025. Penulis tersebut tidak mengajukan banding terkait pemblokiran akunnya — akunnya telah diretas bersama dengan alamat emailnya, dan ia meminta akses kembali: \"Saya tidak menanyakan soal pemblokiran itu dan saya juga tidak membantahnya. Saya hanya ingin bisa mengakses akun Steam saya… Valve selalu memberikan jawaban yang persis sama ini—yang disalin dan ditempelkan—pada setiap permohonan, lalu menutup permohonan tersebut.\" — r/steamsupport ↗, yang terdapat dalam kumpulan pengaduan yang menjadi bagian dari penyelidikan ini\n\nKata demi kata, koma demi koma, selama lima puluh lima bulan, melibatkan tiga agen dan dua bahasa antarmuka. Satu-satunya perubahan di seluruh teks adalah kalimat terakhir yang disesuaikan antara tahun 2020 dan 2024, dari \"Anda tidak akan menerima balasan lagi\" ke \"Permohonan bantuan di masa mendatang… mungkin akan ditutup tanpa balasan.\" Apa pun proses yang melatarbelakangi keputusan-keputusan tersebut, surat itu bukanlah catatan mengenai proses tersebut. Alasan yang disebutkan adalah \"kegiatan perdagangan, laporan masyarakat, dan faktor-faktor lain\" — sebuah kategori, sebuah laporan yang sumbernya tidak diketahui, serta sisa faktor yang tidak disebutkan namanya.\n\nLima kasus lainnya, yang dikumpulkan dengan cara yang sama. Tiga kasus pertama termasuk dalam kategori yang sama dan memiliki hasil yang sama; dua kasus terakhir berasal dari bagian yang sama, namun menanggapi aturan yang berbeda dengan menggunakan kata-kata yang sama:\n\nTanggal\tApa yang dilakukan akun tersebut\tApa yang terjadi\tSumber\n4 Desember 2021\tJual beli di Buff — \"Saya tidak melakukan apa-apa selain melakukan jual beli di Buff alias perdagangan P2P\"\tPemblokiran komunitas: tidak ada pasar, tidak ada perdagangan, persediaan yang mahal dibekukan\tr/csgomarketforum ↗ diarsipkan 2025-03-27 ↗\n06 Desember 2021\tTransaksi P2P satu arah melalui Buff dan Bitskins untuk perlengkapan dan penukaran ke perlengkapan yang lebih baik\tGembok permanen untuk keperluan komersial ditambah gembok komunitas: \"terjebak dalam mode semu tak terlihat… Profilku juga terjebak dalam mode pribadi\"\tr/GlobalOffensiveTrade ↗ diarsipkan 2021-12-06 ↗\n20 Desember 2024\tAkun ini telah dimiliki sejak 2017, dengan total ribuan jam; melakukan pertukaran di pasar komunitas untuk loadout bertema dan upgrade\tPenguncian permanen dengan sistem penguncian komunitas, tanpa peringatan atau sanksi sebelumnya; dukungan \"mengatakan bahwa keputusan mereka sudah final\", balasan-balasan tersebut bersifat otomatis\tr/csgomarketforum ↗ diarsipkan 2025-06-27 ↗\n23 Desember 2024\tPengguna yang kembali mengisi saldo dompetnya setelah setahun tidak aktif, melalui VPN yang digunakan \"hanya untuk keamanan internet secara umum\"\tPemblokiran permanen dari komunitas dengan sama sekali tidak ada alasan yang disebutkan: \"Larangan tersebut bersifat permanen dan mereka tidak dapat memberikan informasi lebih lanjut, serta tiket-tiket selanjutnya mungkin akan ditutup tanpa tanggapan.\" 196 suara setuju, 340 balasan\tr/steamsupport ↗\n04 Agustus 2026\tSelama bertahun-tahun melakukan pembelian dari Iran; penulis menyatakan bahwa mereka tidak pernah mengirimkan barang, tidak pernah menggunakan Market, dan tidak pernah menggunakan forum\tAkses komunitas diblokir hingga tahun 2038 lebih dari \"wilayah yang dikenai sanksi\"; tiket ditutup oleh seorang agen bernama Azul. Permohonan pengembalian dana dari akun yang sama, yang berasal dari alamat IP Iran yang sama, telah disetujui setahun sebelumnya. Perpustakaan dan uangnya tetap menjadi milik Valve.\tr/pcgaming ↗\n\nBaris terakhir memiliki aturan yang berbeda dari yang lain — kepatuhan terhadap sanksi, bukan penggunaan komersial — dan dimasukkan karena bentuk jawabannya identik: sebuah kategori, tanpa bukti, tanpa banding, tiket yang ditutup. Hal ini juga memunculkan pertanyaan yang tidak ada pada baris lainnya. Jika pelayanan terhadap akun tersebut melanggar hukum, maka penerimaan pembayaran selama bertahun-tahun itu pun melanggar hukum. Salah satu dari kedua posisi tersebut pasti salah, dan hanya salah satunya yang menimbulkan kerugian bagi pelanggan.\n\nKedelapan pesan tersebut dibaca pada 2026-09-22 — utas tahun 2021 dan Desember 2024 melalui tangkapan layar Internet Archive, sedangkan sisanya melalui antarmuka Reddit yang terbuka untuk umum, karena Reddit menolak permintaan langsung dari pihak yang mengumpulkan data. Kedua surat tahun 2020 dan 2024 tersebut ditranskripsikan dari tangkapan layar yang dilampirkan pada postingan asli, yang masih aktif. Tidak ada satu pun akun ini yang dalam penyelidikan ini dituduh tidak bersalah atau bersalah atas apa pun — justru itulah intinya. Tak seorang pun pembaca, maupun pihak pengawas, dapat mengetahui hal itu dari surat tersebut.\n\nCatatan mengenai sumber data — kerugian pada tingkat operator\n\nOperator-operator yang diwawancarai dalam penyelidikan ini melaporkan kerugian sebesar masing-masing lima hingga sepuluh ribu akun dalam gelombang penegakan hukum tunggal, dengan akun-akun utama diperiksa bersamaan dengan peternakan tersebut. Survei tersebut dicatat di sini sebagai laporan pihak pertama, bukan sebagai temuan. Ukuran sampelnya tidak dipublikasikan, tidak ada tanggal pengumpulan yang tetap, dan tidak ada verifikasi per akun; tidak ada angka lain di halaman ini yang bergantung padanya; kedua baris di bagian 02 yang bergantung padanya telah ditandai sebagai demikian.\n\nHal ini disebutkan secara eksplisit, bukan diabaikan, karena dua alasan. Mekanisme larangan berantai di atas merupakan penjelasan yang terdokumentasi untuk pola tersebut secara tepat. Dan regulator dapat meminta dari Valve satu catatan yang akan menyelesaikan masalah ini: berapa banyak akun yang ditindaklanjuti karena otomatisasi, dalam gelombang mana, dan berapa banyak yang telah dibelanjakan oleh masing-masing akun tersebut di toko sebelum ditutup. Selama catatan tersebut belum ada, angka tersebut tetap seperti semula — dilaporkan, dikaitkan, dan belum terbukti.\n\n07 — Asimetri\nKedua sisi meja yang sama\n\nBandingkan standar pembuktian tersebut dengan standar Valve yang diterapkan pada operasi pendukungnya sendiri. Kolom sebelah kanan adalah daftar insiden dari berkas ini sendiri, yang disalin beserta catatan pengecualian yang tercantum di sana.\n\nSeorang pelanggan, untuk keperluan perdagangan\n\nDelapan kasus yang tercatat, 2020–2026\n\nPerilaku\nMenjual atau membeli barang di platform pasar pihak ketiga; dalam satu kasus, sama sekali tidak ada tindakan apa pun — akun tersebut telah diretas.\nBukti yang ditunjukkan\nTidak ada. \"Berdasarkan aktivitas perdagangan, laporan komunitas, dan faktor-faktor lainnya.\"\nPengumuman\nTidak ada. Valve telah ditetapkan dalam § 4.D: \"Valve tidak diwajibkan untuk memberi tahu Anda sebelum melakukan pemutusan hubungan kerja.\"\nBanding\n\"Penguncian ini bersifat permanen dan Steam Tim Dukungan tidak dapat membantu Anda lebih lanjut mengenai hal ini.\"\nTiket\nDitolak pada balasan pertama. Permintaan selanjutnya \"mungkin akan ditutup tanpa balasan.\"\nJangkauan\nProfil, daftar teman, obrolan, Market, inventaris, dan setiap item yang dibeli dengan uang sungguhan.\nDurasi\nTetap.\nArmada bot otomatis, untuk volume besar\n\n694,673 set lengkap yang tersedia di stok umum di 91 bot\n\nPerilaku\nMenjalankan skrip otomatis tanpa antarmuka pengguna (headless) di ribuan akun secara bersamaan untuk menonaktifkan kartu, membuat lencana secara massal, dan menukar set kartu dalam skala industri.\nBukti yang ditunjukkan\nDirektori bot yang dipublikasikan secara terbuka (steam.supply, SteamLvlUp) dan grup publik dengan jutaan anggota.\nPengumuman\nTanpa campur tangan sama sekali. 88.97% tidak dikenakan larangan apa pun; 99.8% dari sisa larangan tersebut bersifat kosmetik.\nBanding\nTidak diperlukan. Armada beroperasi secara terus-menerus selama siklus hidup bertahun-tahun tanpa gangguan.\nTiket\n—\nJangkauan\nPertukaran inventaris tanpa batasan, peningkatan level lencana, dan likuiditas pasar.\nManfaat hingga Valve\n$26.8M+ dalam batas belanja minimum di toko ($5.00 batas masuk per akun) ditambah 15% potongan transaksi di Community Market.\nPertanyaan yang muncul dari hal ini, secara sederhana\n\nSeorang pelanggan perorangan yang melakukan perdagangan kartu atau item secara manual akan dikenai sanksi pemblokiran permanen yang tidak dapat diajukan banding berdasarkan § 4.C (otomatisasi) atau § 2.G (penggunaan komersial). Sebuah jaringan farming otomatis yang menjalankan bot tanpa pengawasan di ribuan akun beroperasi secara terbuka dengan tingkat keberhasilan 88.97%. Valve adalah pihak yang diuntungkan dari keduanya.\n\nAsimetri ini bersifat ekonomi: para pedagang individu memperoleh keuntungan dari platform tersebut, sementara jaringan kartu otomatis menyalurkan jutaan ke gerbang pengeluaran toko Valve ($5.00 per akun) dan mendorong biaya transaksi pada setiap penjualan kembali. Penegakan aturan tidak mengikuti pedoman tertulis; melainkan mengikuti model pendapatan.\n\n08 — Tata Kelola\nSiapa yang mengatur sistem ekonomi kartu?\n\nTemuan yang berulang dalam laporan ini — bahwa lapisan pihak ketiga di sekitar Steam diisi oleh orang-orang dari dalam Steam — juga berlaku dalam ekonomi kartu, dan hal ini berujung pada kesimpulan tertentu: tidak ada pihak independen yang dapat menghitung apa yang sebenarnya dilakukan oleh penegakan aturan Valve, karena pihak yang mampu menghitungnya berada di dalam lapisan tersebut. Setiap fakta di bawah ini diambil dari grup publik dan halaman profil Valve sendiri di 2026-09-22 dan dapat direproduksi oleh siapa pun melalui browser.\n\nSeorang karyawan Valve bertindak sebagai moderator di grup pertukaran kartu terbesar Valve karyawan\n\nCardTrades ↗ menggambarkan dirinya sendiri dalam header-nya sebagai \"Steam Grup resmi Card Exchange\" dan membawa 97,114 anggota. Moderator yang terdaftar di sana — akun-akun yang memegang kendali atas grup tersebut — adalah Mickmane, Sersan Fopper dan afarnsworth ↗.\n\nProfil terakhir itu ditandai oleh markup situs Valve sendiri sebagai karyawan Valve — halaman tersebut memuat class=\"profile_header_valve_employee\" — menyebutkan lokasinya sebagai Bellevue, Washington, dan termasuk dalam Valve, Steam dan Steam Grup Kartu Koleksi kelompok. SteamID64 76561197960434622, menjadi anggota sejak 12 September 2003.\n\nPengamatan ini bersifat struktural, bukan pribadi, dan hal ini tidak Sebuah poin terkait otomatisasi — seorang moderator grup pertukaran kartu tidak menggunakan bot, dan tidak ada hal di sini yang mengindikasikan sebaliknya. Intinya adalah klausul dalam bagian 07. Steam Card Exchange adalah layanan kartu komersial pihak ketiga; bertukar kartu melalui layanan pihak ketiga merupakan tindakan yang persis sama dengan yang menjadi alasan Valve mengunci akun biasa secara permanen berdasarkan \"digunakan untuk tujuan komersial berdasarkan aktivitas perdagangan, laporan komunitas, dan faktor-faktor lainnya.\" Seorang karyawan Valve menjabat sebagai moderator yang terdaftar di grup komunitas resmi layanan tersebut yang beranggotakan sembilan puluh tujuh ribu orang.\n\nTidak ada tuduhan pelanggaran yang dilayangkan terhadap siapa pun di sini, dan tidak ada kesimpulan yang ditarik mengenai apa saja yang termasuk dalam peran tersebut. Asimetri itulah yang menjadi temuan: ketika akun biasa terlibat dengan layanan kartu atau skin pihak ketiga, hasilnya adalah tiket ditutup dan pemblokiran permanen tanpa bukti yang ditunjukkan; ketika layanannya adalah yang ini, seorang karyawan Valve terdaftar dalam daftar moderator dan pengaturannya terlihat di halaman Valve yang diterbitkan oleh layanan tersebut sendiri. Yang diminta adalah hal yang sama seperti yang diminta di seluruh bagian lain dalam berkas ini: tunjukkan otorisasi tertulis, jika memang ada — dan jika tidak diperlukan, sampaikan hal tersebut secara tertulis, karena delapan orang di bagian 06 diberi tahu sebaliknya.\n\nLapisan daftar larangan, dan siapa yang mengelolanya Moderator sukarelawanLayanan pihak ketiga\n\nGrup Steambans.com (arsip) ↗ (siaran langsung ↗ diarsipkan 2025-12-03 ↗) mencatat silsilahnya dalam deskripsi kelompoknya yang masih tersimpan: \"Grup Komunitas resmi Steambans.com Steam. SteamBans.com adalah layanan baru yang didasarkan pada konsep lama. Daftar larangan global telah aktif selama bertahun-tahun di program WONID lama dari VALVe. Ketika terjadi peralihan ke STEAMID, wajar bagi kami untuk mengembangkan layanan yang dirancang khusus untuk sistem baru ini. Namun, kami juga menginginkan lebih. *. Halaman arsip untuk Steambans yang ditutup pada tahun 2013.\" Di antara pengelola yang terdaftar di antaranya adalah devicenull dan killahinstinct_ ↗.\n\nAkun administrator tersebut adalah tidak seorang Valve — ia tidak memiliki status sebagai karyawan. Ia adalah seorang sukarelawan dengan kedudukan yang luar biasa tinggi: seorang anggota dari Moderator Komunitas (414 anggota, digambarkan sebagai sebuah kelompok \"dibuat oleh Moderator Komunitas Steam\"), dari Koordinator Wiki, dari Steam Pasar Komunitas, serta kelompok program dan prarilis Valve, termasuk Valve Pipa, Steam Versi Beta untuk Klien, Autentikasi Seluler Beta, Beta Komunitas Baru Steam, Steam Laboratorium, Steamworks dan Laporkan URL Penipuan. SteamID64 76561197960794555.\n\nSelain itu, di dalam lingkaran tersebut dan menampilkan Steambans secara langsung di daftar anggota grup publiknya: msart ↗ (daftar anggota grup ↗), SteamID64 76561197977933359, yang dalam profilnya disebutkan sebagai berikut \"Saya mengelola steamid.uk dan banyak situs lain yang berkaitan maupun tidak berkaitan dengan Steam\", dan yang mengelola jaringan yang saling terhubung yang terdiri dari enam belas kelompok — SteamIDcouk (kelompok utama \"Situs Web Sid\"), SidAdmins, SidBans, steamideu, Steam3ID, s-id dan SArchive di antara mereka.\n\nsteamid.uk mencantumkan nomor yang sama. Dalam bagian FAQ-nya: \"Siapa yang menciptakan SteamID? Situs web SteamID, infrastruktur jaringan, dan sistem keamanannya semuanya dikelola oleh 76561197977933359.\" Dua jawaban di bawahnya menjelaskan dari mana asal data tersebut: \"SteamID terutama menggunakan Web API Steam untuk pengumpulan data.\" Halaman yang sama menjelaskan sejumlah server khusus yang tersebar di berbagai penyedia layanan, server pengembangan di luar lokasi, server penyimpanan, dan server pencarian teks, serta fasilitas pencadangan tersendiri.\n\nTelah diverifikasi melalui catatan Internet Archive yang tersimpan: Gambaran umum grup Steambans per 3 Desember 2025 ↗, yang Ringkasan profil operator per 14 September 2024 ↗, dan Cuplikan FAQ steamid.uk per 1 April 2026 ↗, data yang cocok yang dibaca langsung dari 2026-09-22.\n\nIntinya, hal ini berarti... dan bukan berarti...\n\nDaftar pemblokiran, penentuan SteamID, dan perdagangan kartu adalah tiga layanan yang menentukan siapa yang dapat dipercaya, siapa yang dapat diidentifikasi, dan berapa nilai suatu item. Tak satu pun dari ketiga layanan tersebut dioperasikan oleh Valve. Pada masing-masing di antaranya, orang-orang yang memegang kendali berasal dari dalam orbit Valve: seorang karyawan yang ditandai Valve dalam daftar moderator grup resmi layanan kartu tersebut; seorang moderator komunitas Valve yang telah lama bertugas dan memiliki akses ke program pra-rilis yang mengelola grup daftar pemblokiran; serta layanan identifikasi yang dijalankan oleh seorang individu swasta yang berada dalam lingkaran yang sama. Tiga layanan, tiga antarmuka kontrol, tiga orang Valve yang telah diberi wewenang.\n\nKeanggotaan dalam kelompok bukanlah hubungan kerja, dan semua ini bukanlah tuduhan. Ini adalah fakta dalam tata kelola, dan itulah alasan mengapa pembelaan standar — Itu adalah pihak ketiga, kami tidak bisa mengendalikan mereka — harus diuji, bukan langsung diterima begitu saja. Para pengendali sudah tidak asing lagi dengan Valve. Valve berada dalam posisi untuk menjelaskan apa yang diminta dari mereka—jika memang ada; tidak ada orang di luar yang bisa mengetahuinya.\n\nTak ada yang dihitung. Itulah kesimpulannya.\n\nRuang ID Steam adalah rentang bilangan bulat yang berurutan. Menelusuri rentang tersebut dan melaporkan berapa banyak akun yang diblokir, berapa banyak yang dibatasi, serta berapa banyak persediaan yang terhalang oleh larangan perdagangan bukanlah sebuah program penelitian — itu hanyalah sebuah loop dan kunci API. Valve sendiri yang membagikan kunci tersebut, di steamcommunity.com/dev/apikey. Namun demikian Tidak ada pihak independen yang menerbitkan sensus tersebut. Bukan regulator, bukan jurnalis, bukan akademisi, bukan organisasi konsumen. Satu-satunya data publik mengenai skala penegakan hukum terhadap Steam adalah data yang Valve pilih untuk sebutkan.\n\nKemampuan tersebut tidak hilang. Kemampuan itu masih ada. Layanan yang mengelola dan mengindeks ruang ID dalam skala besar — steamid.uk — menyatakan dalam FAQ-nya sendiri bahwa layanan tersebut \"secara utama memanfaatkan Web API Steam untuk pengumpulan data\" dan dijalankan di beberapa server khusus, penyimpanan eksternal, mesin pencarian teks, serta fasilitas cadangan terpisah. Situs ini dioperasikan oleh seorang individu swasta. Kelompok saudara dari daftar pemblokiran miliknya dikelola bersama oleh seorang moderator komunitas Valve yang telah lama bertugas dan memiliki akses ke program pra-rilis Valve. Satu-satunya pihak yang berwenang untuk mempublikasikan hasil penghitungan tersebut berada di dalam orbit Valve, namun tidak mempublikasikannya.\n\nInilah pola yang sama yang ditemukan dalam dokumen tersebut di mana-mana. Setiap layanan yang mengambil keputusan penting terkait ekonomi Steam — siapa yang dipercaya, siapa yang dapat diidentifikasi, berapa nilai suatu barang, siapa yang dilarang — secara nominal merupakan pihak ketiga, namun secara praktis berdekatan dengan Valve. Steam Pertukaran Kartu bukanlah pengecualian dari pola tersebut; hal itu justru merupakan contoh lain dari pola tersebut. Alasan pembelaan bahwa mereka adalah operator independen dapat diajukan oleh Valve justru karena tidak ada seorang pun yang pernah mampu mengujinya dengan membandingkannya dengan suatu bilangan.\n\nSensus Akun 10,88 Juta: 88.97% Belum Tersentuh\n\nBasis instalasi ArchiSteamFarm telah diaudit di seluruh Valve GetPlayerBans titik akhir (10,880,610 akun, 55 menit). Himpunan bagian yang tidak terbatas itu sendiri mewakili $26.8M+ dalam jumlah belanja minimum di toko (ambang batas masuk $5.00). 9,680,599 akun (88.97%) tidak dikenai larangan apa pun, dan 99.8% dari sisanya hanya dikenakan sanksi larangan komunitas yang bersifat kosmetik, sehingga perdagangan otomatis tetap aktif.\n\n5,360,499Anggota ASF tanpa batasan (jumlah yang ditampilkan Steam)\n10,880,610Jumlah entri API yang dipindai (terbatas + tidak terbatas)\n9,680,599Belum pernah diblokir sama sekali (88.97%)\n1,200,011Memiliki larangan Steam (11.0%) — 99.8% kosmetik\n55 menitUntuk melakukan sensus terhadap seluruh penduduk, salah satu hal penting\nBukti Forensik & Sensus Mendalam\n\nRincian demografis yang terperinci — termasuk diagram distribusi jenis pemblokiran, usia akun pada saat penegakan sanksi, kelompok tahun pembuatan akun (2020–2026), dan laporan lokasi geografis yang disampaikan sendiri — dipublikasikan dalam laporan investigasi sensus khusus tersebut.\n\nBuka Data Sensus Larangan Selengkapnya sebesar 10,88 juta (Lampiran VI) →Bagian 4 — Pemadaman ID Aset →\n\nJadi, pertanyaan yang harus diajukan—dan hanya Valve yang dapat menjawabnya: identifikasi atau kemampuan mana yang dicabut, pada tanggal berapa, atas keputusan siapa, dan apa dampak yang dapat diukurnya terhadap para operator yang menjadi sasarannya — jika dibandingkan dengan dampaknya terhadap semua orang di luar sana yang sedang berusaha menghitung. Perubahan yang mengakhiri audit independen tidak lantas menjadi netral hanya karena diumumkan sebagai langkah keamanan. Itulah sebabnya sensus di blok di atas tidak ada.\n\n09 — Metode dan batasan\nApa yang telah dibaca, dan apa yang tidak diklaim\n\nSetiap kutipan di halaman ini diambil langsung dari sumber aslinya di 2026-09-22 dan disalin persis seperti aslinya. Tidak ada satu pun di sini yang diambil dari hasil penggalian data, kredensial pasar, atau kumpulan data pribadi.\n\nKeempat kumpulan data tersebut, serta perhitungan yang dilakukan terhadapnya\n\nMasing-masing merupakan satu permintaan publik yang dapat direproduksi dari terminal. Tidak ada akun yang digunakan, tidak ada pasar daring yang diakses, dan tidak ada titik akhir yang memerlukan kredensial yang dipanggil.\n\nKumpulan data\tDari mana asalnya\tApa yang dihitung berdasarkan data tersebut\nSensus kartu\n13,876 pertandingan\tSteam Daftar harga lencana yang dipublikasikan oleh Card Exchange, sumber data yang sama yang menampilkan halaman harga umum ↗ diarsipkan 2026-08-04 ↗\tPermainan yang menerbitkan kartu, jumlah kartu per set, jenis-jenis kartu yang berbeda, dan harga pasar masing-masing set lengkap. Nilai median dan total $23,586.57 merupakan data aritmetika dalam penelitian ini.\nHarga game\n13,713 telah diselesaikan\tTitik akhir toko publik milik Valve, store.steampowered.com/api/appdetails, cc=AS, hanya kolom harga, secara bertahap\tMedian dan distribusi harga eceran yang tertera pada permainan berbasis kartu; jumlah permainan yang penjualan set lengkapnya melebihi penjualan permainan itu sendiri.\nStok bot\n91 bot, 694,673 set\tDirektori bot kartu umum di steam.supply/CardBots ↗, dibaca sesuai tampilan, tanpa login\tJumlah total set yang tersedia, jumlah kartu minimum, batas bawah kuota penarikan, dan batas bawah alokasi per bot pada akun-akun yang berbeda.\nPemeriksaan silang\n21 bot yang dibagikan\tsteamlvlup.net/cardbots ↗ diarsipkan 2026-02-10 ↗, sebuah direktori independen yang berisi bot-bot yang sama\tHanya untuk verifikasi. Pada 21 bot yang tercantum dalam kedua daftar tersebut, Aggregate Stock setuju untuk 0.03%; perbedaan terbesar yang berasal dari satu bot adalah 1.36%, yang sesuai dengan hasil dua kali pengambilan data inventaris real-time yang dilakukan dalam selang waktu beberapa menit.\n\nSumber, sebagaimana diminta oleh direktori kedua: data disediakan oleh SteamLvlUp, dilisensikan di bawah CC BY 4.0 diarsipkan 2026-09-23 ↗; digunakan di sini semata-mata sebagai verifikasi independen terhadap data stok pihak ketiga, dan telah dimodifikasi sedemikian rupa sehingga baris per-bot digabungkan dan dibandingkan, bukan ditampilkan ulang. Steam Card Exchange dan steam.supply telah disebutkan di atas melalui tautan. Harga permainan adalah milik Valve sendiri. Nama dan gambar kartu, permainan, serta set adalah milik Valve atau penerbitnya, direproduksi tanpa klaim atau lisensi apa pun, sebagai fakta mengenai pasar.\n\nDua pengukuran yang seharusnya dilakukan tidak dilakukan dan tidak digantikan. Titik akhir Community Market milik Steam sendiri — ringkasan harga, pencarian/penayangan, riwayat harga — tidak mengirimkan apa pun ke host pengumpul, dan Steam halaman diskusi Komunitas mengirimkan respons HTTP 403 kepadanya, sehingga tidak ada angka di halaman ini yang berasal dari data Market secara real-time. Metode volume penjualan yang seharusnya menghitung kartu yang muncul pada reset harian memerlukan sesi Steam yang sudah masuk; Manifest penyelidikan ini menyatakan bahwa tidak ada kredensial pasar yang digunakan, dan pernyataan tersebut tetap dipertahankan. Lantai bot-stock adalah bagian yang dapat diukur tanpa menggunakan alat tersebut.\n\nSumber primer\n\nSteam Perjanjian Pelanggan ↗ diarsipkan 2026-09-24 ↗ — § 2.A, § 2.G, § 3.D, § 4.C, § 4.D.\nSteam Dukungan — Akun Pengguna Terbatas ↗ — ambang batas $5.00 dan daftar fitur yang dibatasi.\nValve — Steam Pertanyaan Umum tentang Kartu Perdagangan ↗ — sistem drop dan tarif free-to-play $9.\nArchiSteamFarm Pertanyaan Umum ↗ dan diskusi #3440 ↗.\nSteam Halaman grup komunitas dan profil, dibaca langsung, untuk bagian 08.\nFAQ steamid.uk, cuplikan Internet Archive 2026-04-01 ↗.\nDelapan Steam Pemberitahuan penguncian dukungan yang diterbitkan oleh para penerimanya, 2020–2026, tercantum beserta tautannya di bagian 06.\n\nApa yang tidak diklaim\n\nTidak ada perkiraan angka pendapatan untuk Valve dari praktik \"card farming\". Tidak ada data jumlah akun aktif yang disebutkan untuk alat apa pun, dan kuota penurunan sebesar 1,39 juta adalah tidak jumlah akun milik pertanian — lihat catatan di bagian 02. Tidak ada individu yang dituduh melakukan pelanggaran; jika nama seseorang disebutkan, hal itu menggunakan nama pengguna publik Steam miliknya sendiri, dalam peran publiknya, dari halaman yang diterbitkan oleh Valve. Tak satu pun dari delapan akun yang diblokir di bagian 06 dinyatakan tidak bersalah atau bersalah; temuan tersebut berkaitan dengan surat tersebut, bukan akunnya. Angka kerugian operator di bagian 02 merupakan laporan pihak pertama dan diberi label demikian di catatan pengadaan. Bagian FAQ dari steamid.uk dikutip dari tangkapan layar Internet Archive karena halaman aslinya dilindungi oleh sistem verifikasi bot. Tidak ada klaim bahwa upaya penghitungan jumlah pengguna yang diblokir pernah dilakukan dan disembunyikan — temuan ini hanya menunjukkan bahwa tidak ada data semacam itu yang dipublikasikan. Kurva Level Steam di atas angka 667 tidak dimodelkan.\n\nMengapa alat tersebut bukanlah pokok bahasan\n\nArchiSteamFarm menyatakan bahwa hal itu \"tidak disahkan oleh Valve\" dan tidak ada tuduhan apa pun terhadapnya di halaman ini. Organisasi ini digunakan sebagai alat ukur, karena merupakan satu-satunya pihak dalam perekonomian ini yang mendokumentasikan mekanisme tersebut secara terbuka dan tertulis. Valve dapat merangkum seluruh bukti dalam satu paragraf: mempublikasikan otomatisasi komersial mana yang disetujuinya, serta catatan per operator mengenai tindakan yang diambil terkait sisanya.\n\nBaca selanjutnya: bagaimana harga Pasar itu sendiri ditentukan → · skala harga dan batas jumlah penawaran → · barang-barang Steam tidak akan dikirim →",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Bot farm bukanlah kebocoran di toko Valve. Itu adalah pelanggan."
          },
          {
            "level": 2,
            "id": null,
            "text": "Apa itu peternakan sebenarnya, langkah demi langkah"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ikut serta"
          },
          {
            "level": 3,
            "id": null,
            "text": "Beli game"
          },
          {
            "level": 3,
            "id": null,
            "text": "Menganggur\nAlat ini masuk ke akun di jaringan Steam tanpa antarmuka pengguna, \"menganalisis lencana Anda\", menyusun daftar judul yang dapat ditanam dan memulai \"memainkan game yang memenuhi syarat dan secara berkala memeriksa apakah game tersebut sudah sepenuhnya di-farm.\" Penjelasan pengembangnya mengenai mekanisme tersebut: mekanisme tersebut \"tidak melakukan apa pun selain memberi tahu Steam bahwa kita sedang memainkan permainan tersebut.\""
          },
          {
            "level": 3,
            "id": null,
            "text": "Tetesan habis\nSetiap judul bersifat terbatas. \"Setiap game memiliki jumlah kartu yang bisa diperoleh dalam jumlah tetap. Begitu kamu sudah mendapatkan semuanya (sekitar setengah dari satu set lengkap), game tersebut tidak lagi layak untuk 'farming'.\" Sebuah pertanian yang ingin terus berproduksi harus terus membeli kartu. Pasokan kartu dibatasi oleh pembelian — hal ini memang dirancang demikian, dan menguntungkan Valve."
          },
          {
            "level": 3,
            "id": null,
            "text": "Penarikan dana\nKartu tersebut akan keluar melalui salah satu dari tiga jalur: dijual di Pasar Komunitas, ditukar, atau dihancurkan menjadi permata. Masing-masing merupakan transaksi di Pasar Berlangganan atau pertukaran, dan § 3.D mengatur biaya sebagai berikut: \"Valve dapat mengenakan biaya atas transaksi di Pasar Langganan.\" Inilah langkah yang membuat seluruh proses tersebut menjadi pelanggaran — lihat 05."
          },
          {
            "level": 2,
            "id": null,
            "text": "Sebelum sebuah peternakan menghasilkan satu sen pun, ia sudah mengeluarkan biaya sebesar Valve"
          },
          {
            "level": 3,
            "id": null,
            "text": "Seberapa besar sebenarnya barang yang dibeli itu"
          },
          {
            "level": 3,
            "id": null,
            "text": "Seberapa besar ukuran himpunan tersebut?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Berapa biaya lisensinya?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Hasil yang ditampilkan oleh set yang sudah jadi"
          },
          {
            "level": 3,
            "id": null,
            "text": "Di mana kumpulan 694,673 tersebut berada"
          },
          {
            "level": 3,
            "id": null,
            "text": "Apa yang tersirat dan tidak tersirat dari lantai ini"
          },
          {
            "level": 3,
            "id": null,
            "text": "Dan bertani tidak bisa menutupi biayanya sendiri dengan harga yang ditetapkan Valve"
          },
          {
            "level": 3,
            "id": null,
            "text": "Apa yang sebenarnya ditopang oleh pertanian tersebut"
          },
          {
            "level": 4,
            "id": null,
            "text": "Penjualan game"
          },
          {
            "level": 4,
            "id": null,
            "text": "\"Online\" & waktu bermain"
          },
          {
            "level": 4,
            "id": null,
            "text": "Pendaftaran"
          },
          {
            "level": 4,
            "id": null,
            "text": "Uang di dompet & biaya"
          },
          {
            "level": 4,
            "id": null,
            "text": "Hubungan Masyarakat (PR) Tingkat 0"
          },
          {
            "level": 3,
            "id": null,
            "text": "Dan penarikan dana itu sendiri merupakan pemborosan nilai Valve—pajak dikenakan dua kali"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ini bukanlah sekadar momen. Ini adalah industri yang telah berdiri kokoh selama bertahun-tahun."
          },
          {
            "level": 3,
            "id": null,
            "text": "Kumpulan kartu lengkap yang disimpan di direktori bot publik, oleh Steam sale"
          },
          {
            "level": 3,
            "id": null,
            "text": "Seperti apa tampilan tangga lencana penjualan jika dilihat dari puncaknya"
          },
          {
            "level": 3,
            "id": null,
            "text": "Dan armada yang sama tetap berada di sana ketika tidak ada promo penjualan yang sedang berlangsung"
          },
          {
            "level": 3,
            "id": null,
            "text": "Direktori penyimpanan, per bot"
          },
          {
            "level": 2,
            "id": null,
            "text": "Produk lainnya adalah angka yang tertera di samping nama Anda"
          },
          {
            "level": 3,
            "id": null,
            "text": "Set lengkap yang telah diselesaikan, level 1 hingga 1,000"
          },
          {
            "level": 3,
            "id": null,
            "text": "Bagaimana kurva tersebut diverifikasi, karena Valve tidak mempublikasikannya"
          },
          {
            "level": 2,
            "id": null,
            "text": "Klausul tersebut tidak menjelaskan pertanian secara samar-samar. Klausul tersebut menjabarkannya secara rinci."
          },
          {
            "level": 3,
            "id": null,
            "text": "\"…waktu bermain\""
          },
          {
            "level": 3,
            "id": null,
            "text": "\"…tanpa masukan yang sejati dari pengguna\""
          },
          {
            "level": 2,
            "id": null,
            "text": "Setiap orang yang keluar dari kartu yang telah dibeli merupakan tindakan yang dilarang oleh lisensi — dan Valve mengenakan biaya di pintu masuk"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 2.A — lisensi"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 2.G — pembatasan"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 3.D — biaya"
          },
          {
            "level": 3,
            "id": null,
            "text": "Baca ketiga hal tersebut secara bersamaan, dan posisi tersebut akan ditutup"
          },
          {
            "level": 3,
            "id": "fee-ladder",
            "text": "Biaya di pintu itu bukan 15%. Pada kartu yang disewakan, biayanya mencapai dua pertiga."
          },
          {
            "level": 3,
            "id": null,
            "text": "Biaya efektif atas penjualan di Pasar Komunitas, berdasarkan harga yang diminta penjual"
          },
          {
            "level": 2,
            "id": null,
            "text": "Tanpa pemberitahuan, datang bergelombang, dan menyebar melalui nomor telepon"
          },
          {
            "level": 3,
            "id": null,
            "text": "Kasus 4 — Juni 2025, VAC larangan terhadap CS2 yang tidak beroperasi"
          },
          {
            "level": 3,
            "id": null,
            "text": "Bagaimana sebuah akun utama bisa mati"
          },
          {
            "level": 3,
            "id": null,
            "text": "Paragraf yang sama, dengan selisih waktu lima tahun, dari tiga agen yang berbeda"
          },
          {
            "level": 3,
            "id": null,
            "text": "Catatan mengenai sumber data — kerugian pada tingkat operator"
          },
          {
            "level": 2,
            "id": null,
            "text": "Kedua sisi meja yang sama"
          },
          {
            "level": 3,
            "id": null,
            "text": "Seorang pelanggan, untuk keperluan perdagangan"
          },
          {
            "level": 3,
            "id": null,
            "text": "Armada bot otomatis, untuk volume besar"
          },
          {
            "level": 3,
            "id": null,
            "text": "Pertanyaan yang muncul dari hal ini, secara sederhana"
          },
          {
            "level": 2,
            "id": null,
            "text": "Siapa yang mengatur sistem ekonomi kartu?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Seorang karyawan Valve bertindak sebagai moderator di grup pertukaran kartu terbesar Valve karyawan"
          },
          {
            "level": 3,
            "id": null,
            "text": "Lapisan daftar larangan, dan siapa yang mengelolanya Moderator sukarelawan Layanan pihak ketiga"
          },
          {
            "level": 3,
            "id": null,
            "text": "Intinya, hal ini berarti... dan bukan berarti..."
          },
          {
            "level": 3,
            "id": null,
            "text": "Tak ada yang dihitung. Itulah kesimpulannya."
          },
          {
            "level": 3,
            "id": null,
            "text": "Sensus Akun 10,88 Juta: 88.97% Belum Tersentuh"
          },
          {
            "level": 3,
            "id": null,
            "text": "Bukti Forensik & Sensus Mendalam"
          },
          {
            "level": 2,
            "id": null,
            "text": "Apa yang telah dibaca, dan apa yang tidak diklaim"
          },
          {
            "level": 3,
            "id": null,
            "text": "Keempat kumpulan data tersebut, serta perhitungan yang dilakukan terhadapnya"
          },
          {
            "level": 3,
            "id": null,
            "text": "Sumber primer"
          },
          {
            "level": 3,
            "id": null,
            "text": "Apa yang tidak diklaim"
          },
          {
            "level": 3,
            "id": null,
            "text": "Mengapa alat tersebut bukanlah pokok bahasan"
          }
        ],
        "links": [
          "https://help.steampowered.com/en/faqs/view/71D3-35C2-AD96-AA3A",
          "https://github.com/JustArchiNET/ArchiSteamFarm/wiki/FAQ",
          "https://steamcommunity.com/tradingcards/faq/",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260924114457/https://store.steampowered.com/subscriber_agreement/",
          "https://steamladder.com/ladder/badges/2861690/",
          "http://web.archive.org/web/20260716205303/https://steamladder.com/ladder/badges/2861690/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/farm-economy-timeline.json",
          "https://store.steampowered.com/charts/",
          "http://web.archive.org/web/20260923183013/https://store.steampowered.com/charts/",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://github.com/JustArchiNET/ArchiSteamFarm/discussions/3440",
          "https://x.com/gergelyszabo94/status/1311004678633795585",
          "https://x.com/prcs25/status/1811893857253982720",
          "http://web.archive.org/web/20240715122902/https://x.com/prcs25/status/1811893857253982720",
          "https://reddit.com/r/steamsupport/comments/1fjmgc5/what_to_do_when_your_steam_account_gets_hacked/mkelm2y/",
          "https://www.reddit.com/r/csgomarketforum/comments/r87owv/psa_my_steam_account_just_got_banned/",
          "http://web.archive.org/web/20250327203008/https://www.reddit.com/r/csgomarketforum/comments/r87owv/psa_my_steam_account_just_got_banned/",
          "https://www.reddit.com/r/GlobalOffensiveTrade/comments/r9xql9/d_recently_received_commercial_ban_for_what_seems/",
          "http://web.archive.org/web/20211206034804/https://www.reddit.com/r/GlobalOffensiveTrade/comments/r9xql9/d_recently_received_commercial_ban_for_what_seems/",
          "https://www.reddit.com/r/csgomarketforum/comments/1hhxx7m/d_permanently_locked_on_steam_for_commercial_use/",
          "http://web.archive.org/web/20250627014045/https://www.reddit.com/r/csgomarketforum/comments/1hhxx7m/d_permanently_locked_on_steam_for_commercial_use/",
          "https://www.reddit.com/r/steamsupport/comments/1hkctwt/permanent_ban_with_no_explanation/",
          "https://www.reddit.com/r/pcgaming/comments/1vf24lu/warning_to_all_gamersexpats_steam_took_my_money/",
          "https://steamcommunity.com/groups/card-trading-card-trades",
          "https://steamcommunity.com/id/afarnsworth",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/groups/steambans",
          "https://steamcommunity.com/groups/steambans",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/id/killahinstinct_",
          "https://web.archive.org/web/20240914124859/https://steamcommunity.com/id/msart",
          "https://steamcommunity.com/id/msart/groups/",
          "http://web.archive.org/web/20260401154714/https://steamid.uk/faq/",
          "https://phishdestroy.io/steam_dossier/id/enforcement_audit.html",
          "https://phishdestroy.io/steam_dossier/id/#evidence-blackout",
          "https://www.steamcardexchange.net/index.php?badgeprices",
          "http://web.archive.org/web/20260804200309/https://www.steamcardexchange.net/index.php?badgeprices",
          "https://steam.supply/CardBots",
          "https://steamlvlup.net/cardbots",
          "http://web.archive.org/web/20260210171205/https://steamlvlup.net/cardbots",
          "https://steamlvlup.net/",
          "https://creativecommons.org/licenses/by/4.0/",
          "http://web.archive.org/web/20260923221628/https://creativecommons.org/licenses/by/4.0/",
          "https://phishdestroy.io/steam_dossier/id/market_economics.html",
          "https://phishdestroy.io/steam_dossier/id/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/id/elite_skins.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/id/card_economy.content.json",
      "export_json_sha256": "3237f96646993411600ba8a85dae2196820430d28377331ad9d9a65f8610456a"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "id/elite_skins.html",
      "language": "id",
      "title": "Satu barang, dua sistem harga — Laporan Khusus “Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/id/elite_skins",
      "source_html_sha256": "ae194f1d8e8893076982ba8c3956e6bf1af037e850eb9f49955f34a8bde92c1b",
      "exported_at": "2026-09-29T00:22:27.691Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "register",
            "source": "https://phishdestroy.io/steam_dossier/id/elite_skins#register"
          },
          {
            "id": "",
            "source": "https://phishdestroy.io/steam_dossier/id/elite_skins#selected"
          }
        ],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "elite_skins.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/id/elite_skins.pdf?v=print-20260929-v5",
        "sha256": "0438be123fecbddad9d831bcd83c8e081b38ac1dbf45d36a9593ce54953846be",
        "bytes": 94030,
        "pages": 7
      },
      "integrity": {
        "signed_object": "elite_skins.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "elite_skins.content.json.asc",
        "digest_file": "elite_skins.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify elite_skins.content.json.asc elite_skins.content.json",
          "sha256sum -c elite_skins.content.json.sha256"
        ]
      },
      "content": {
        "text": "LAMPIRAN IV / ARSITEKTUR PASAR / 20 SEPTEMBER 2026\nPendaftaran Elite Skins — Batas Atas Pasar $1,800\n\nSatu barang. Dua sistem harga.\n\nAPA YANG DIBUKTIKAN OLEH BAGIAN INI\n\nDaftar ini menyajikan data empiris mengenai semua kategori skin CS2 yang harganya melebihi batas maksimum penawaran di Community Market Steam sebesar $1,800 di lima bursa eksternal. Hal ini membuktikan bahwa 248 kategori tingkat tinggi yang terverifikasi—yang mewakili 18,394 penawaran aktif dan likuiditas terdaftar sebesar $78.6 juta—100% tidak tersedia di pasar resmi Valve. Penjual yang mencari harga pasar yang sesungguhnya secara struktural terpaksa beralih ke platform eksternal, namun tetap bergantung sepenuhnya pada mekanisme perdagangan yang mendasari Steam.\n\nWhat this means — the Community Market listing ceiling\n\nSteam’s own market refuses a listing above roughly $1,800. A seller may ask less, never more. Items whose market price sits above that line therefore cannot be sold at that price on Steam at all — which is the mechanism that moves those sales to third-party venues while the item itself never leaves Valve’s inventory system.\n\nSection 13 — the off-Steam price gap →\n\n← Kembali ke Ringkasan Eksekutif\n\nSteam membatasi harga penawaran di Community Market sekitar $1,800. Di lima platform pasar pihak ketiga yang harganya tercantum dalam ringkasan ini, 419 Kategori barang CS2 memiliki harga penawaran langsung termurah yang melebihi batas tersebut — dan 402 di antaranya, 95.9%,, sama sekali tidak memiliki Steam daftar barang. Secara keseluruhan, mereka memiliki saham-saham yang terdaftar di 18,641 senilai setidaknya $82.4 juta. Harga tersebut baru dianggap sah jika ada pasar kedua yang menyetujuinya, 248 dari kategori-kategori tersebut telah dikonfirmasi — dan semuanya, 100%,, tidak tercantum di Steam. Yang paling disayangi adalah sebuah stiker | Titan (Holo) | Katowice 2014 di $66,285, dikutip oleh empat platform perdagangan yang jaraknya 5.2% satu sama lain dan tidak dilaporkan oleh satupun dari Valve. Daftar lengkap, visualisasi, dan penilaiannya terdapat di atlas tangga harga.\n\nPeriksa semua entri 419 ↓Buka atlas ↗Baca metodenya\n248kategori yang harganya di pasar dua atau lebih melebihi batas atas\n18,394salinan yang terdaftar di lima platform penjualan\n$78.6Mnilai terendah dari daftar properti tersebut\n100%di antaranya sama sekali tidak tercantum di Steam\n\nKoreksi · halaman ini sebelumnya memuat harga yang belum terverifikasi\n\nVersi sebelumnya dari halaman ini menampilkan judul “Souvenir AK-47 | Point Disarray” dengan harga yang ditawarkan $148,954 di salah satu platform jual beli, sementara Steam menawarkannya seharga $119. Baris tersebut hanya terdapat di satu rak dan satu eksemplar saja, tanpa ada platform jual beli lain yang menyetujui harga tersebut; oleh karena itu, angka tersebut merupakan harga yang ditawarkan, bukan harga pasar, dan tidak lagi tercantum di halaman ini. Setiap angka utama di sini kini dibatasi pada kategori \"248\" yang harganya ditetapkan oleh setidaknya dua pasar secara independen di atas batas atas. Baris tersebut sendiri belum dihapus — masih tercantum dalam daftar di bawah ini, dan penilaian yang menurunkan statusnya dijelaskan secara lengkap dalam atlas tangga harga.\n\n01 / uang dalam penawaran yang aktif\nBatas bawah dalam dolar yang dapat diukur\n\nDihitung ulang berdasarkan snapshot berlisensi dari cs2.sh di lima pasar. Ini merupakan nilai penawaran agregat minimum dalam subset yang telah ditentukan, bukan omzet penjualan dan bukan penilaian terhadap ekonomi CS2.\n\n248 KATEGORI YANG TELAH DIVERIFIKASI · 18,394 SALINAN YANG TERDAFTAR · 5 PASAR ONLINE$78.62M\n\nHarga jual terendah agregat dari setiap produk CS2 yang oleh dua atau lebih pasar secara independen ditetapkan harganya di atas batas yang diizinkan oleh Valve di pasarnya masing-masing.\n\nMengapa ini merupakan angka pasti, bukan perkiraan\n\nUntuk setiap pasar, kita mengalikan terendah minta barang tersebut sesuai dengan jumlah eksemplar yang tercantum di platform tersebut. Setiap eksemplar lain di rak tersebut dihargai sama dengan atau di atas harga terendah yang ditawarkan, sehingga nilai yang sebenarnya tercantum lebih tinggi — secara sistematis, bukan berdasarkan perkiraan. Ini bukanlah penjualan, arus kas, atau penilaian pasar secara keseluruhan, dan barang fisik yang sama mungkin muncul di lebih dari satu platform.\n\nPeriksa semua baris sumber di 419 ↗\n★ Sarung Tangan Olahraga | Hedge Maze (Telah Diuji di Lapangan)\n$4.68M\nAWP | Gungnir (Baru dari Pabrik)\n$4.46M\nAWP | Dragon Lore (Baru dari Pabrik)\n$4.34M\n★ Pisau Kupu-kupu | Fade (Baru dari Pabrik)\n$4.17M\nAK-47| Wild Lotus (Baru dari Pabrik)\n$4.16M\n★ Pisau Kupu-kupu | Doppler (Baru dari Pabrik)\n$3.64M\n\nBilah-bilah tersebut menunjukkan enam kontribusi terbesar pada tingkat kategori dalam perhitungan harga dasar, yang diskalakan berdasarkan kontribusi terbesar. Bilah yang tinggi mencerminkan harga penawaran termurah sekaligus jumlah salinan yang terdaftar. Barang fisik yang sama dapat muncul di lebih dari satu pasar, sehingga angka-angka ini tidak boleh dijumlahkan dengan total pasar lainnya.\n\n02 / contoh yang dapat diperiksa\nApa yang tidak tercakup dalam batas tersebut\n\nIlustrasi tersebut sesuai dengan nama barang yang sebenarnya, jika tersedia. Harga yang tercantum adalah harga penawaran yang berlaku dari katalog bertanggal tersebut, bukan catatan transaksi.\n\n★ Butterfly Knife | Doppler (Factory New)\n\nSumber: https://phishdestroy.io/steam_dossier/id/elite_skins#selected\n\nKesenjangan yang dapat diukur: Penawaran-penawaran ini tidak dapat ditandingi oleh daftar properti di Steam dengan harga USD yang sama. Milik Valve sendiri Pertanyaan Umum (FAQ) Pasar Komunitas diarsipkan 2026-09-21 ↗ menyebutkan harga penawaran maksimum sekitar $1,800. Penjual masih bisa menetapkan harga di bawah angka tersebut; apakah hal itu dapat diterima atau tidak, itu terserah penjual. Sebuah CSMarketCap: Cari item dengan harga di atas $1,800 ↗ menampilkan \"Factory New Dragon Lore\" di seluruh pasar yang terdaftar di 28 dengan sekitar 1.1K penawaran yang ditampilkan; stok yang terduplikasi dapat dihitung lebih dari satu kali.\n\n03 / ketergantungan struktural\nTopi yang dikenakan Steam memicu penentuan harga di luar Steam\n\nPerbandingan ini bersifat struktural. Perbandingan ini tidak mengasumsikan bahwa setiap harga yang diminta itu wajar, dan juga tidak menganggap daftar properti yang belum terjual sebagai pendapatan.\n\n01 · ATURAN\nSteam menutup daftar\n\nValve menyebutkan bahwa jumlah iklan di Community Market dibatasi hingga sekitar $1,800. Saldo dompet juga dibatasi, dan dana di dompet tidak dapat ditarik dalam bentuk tunai.\n\n02 · PENGAMATAN\nDragon Lore: $10,940.85\n\nKatalog pasar “5-” menampilkan 389 penawaran langsung untuk AWP Dragon Lore (Baru dari Pabrik), mulai dari $10,940.85 (lantai CSFloat). Daftar yang lebih luas ini berisi kategori-kategori yang telah diverifikasi di 248, yang melebihi batas yang ditetapkan oleh Steam.\n\n03 · AKIBATNYA\nPembagian harga dan transfer\n\nSeorang penjual yang mengincar harga yang lebih tinggi tidak bisa mempostingnya di Steam. Layanan eksternal dapat menetapkan harga tunai, namun proses pengiriman tetap menggunakan sistem kepemilikan dan pemindahSteam.\n\nKontradiksi kebijakan: Karya Valve sendiri Perjanjian Pelanggan diarsipkan 2026-09-21 ↗ melarang pemanfaatan komersial layanan Steam kecuali jika secara tegas diizinkan, sementara 2016 pernyataan diarsipkan 2026-09-21 ↗ Operator perjudian tersebut dilaporkan sudah menggunakan Steam OpenID dan akun otomatis. Hal itu merupakan bukti langsung bahwa Valve mengetahui keberadaan operator pihak ketiga semacam ini di 2016.. Namun, pasar resmi tersebut tidak dapat menampilkan harga yang teramati dari barang-barang bernilai tinggi tersebut. Itulah ketergantungan arsitektural pada penentuan harga dan transaksi di luarSteam; Status kontrak masing-masing pasar memerlukan bukti tersendiri. Dua pasar utama di Barat yang mencatat volume transaksi melebihi kapasitas ini beroperasi sebagai badan usaha resmi di yurisdiksi-yurisdiksi utama — CSFloat Inc. (didirikan di Delaware, AS) dan Skinport GmbH (terdaftar di Stuttgart, Jerman, HRB 764879) — secara terbuka melakukan transaksi senilai ratusan juta dalam penjualan barang secara peer-to-peer dengan mengandalkan langsung API Web dan infrastruktur perdagangan Steam.\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\nKeempat baris dengan nilai $100,000 tersebut berada pada harga penawaran tertinggi yang ditetapkan oleh CSFloat. Baris-baris tersebut ditandai dalam daftar dan tidak boleh dianggap sebagai penilaian. Data arsip CSFloat hanya mencakup harga hingga sekitar $6,999,, sehingga cuplikan katalog publik digunakan untuk daftar lengkap >$1,800.\n\n04 / game Valve lainnya\nLayar atas juga menampilkan Dota 2\n\nUji penawaran termurah yang sama dan ketat di Skinport menemukan kategori 166 CS2 dan kategori 3 Dota 2. Kategori-kategori tersebut merupakan cuplikan pasar yang terpisah; jangan tambahkan ke CSFloat’s 245.\n\nDOTA 2 · PENAWARAN 1\nSabit Brutal yang Heroik\n\nSkinport, harga termurah, tanyakan: $14,622.25.\n\nDOTA 2 · PENAWARAN 1\nJubah Seni Gelap\n\nSkinport, harga termurah, tanyakan: $8,255.16.\n\nDOTA 2 · PENAWARAN 1\nBintang Bertenaga yang Rusak\n\nSkinport, harga termurah, tanyakan: $2,087.92.\n\nIni adalah tiga kategori item yang tercantum, bukan semua item Dota 2 yang ada. Periksa baris-baris yang bertanggal Skinport ↗ dan API dokumentasi ↗.\n\n05 / ketahanan\nTemuan tersebut tidak bergantung pada batas atas yang tepat\n\nValve menetapkan batas atas dalam mata uang regional pembeli, sehingga setelah dikonversi ke USD, nilainya tidak tepat jatuh pada satu angka bulat. Oleh karena itu, penghitungan ini diulangi pada setiap ambang batas yang masuk akal. Persentase item-item yang tidak tercantum di Steam tidak pernah turun di bawah 95%.\n\nSudah diuji ambang batasnya\tKategori barang\tDaftar salinan\tNilai dasar\tTidak hadir dalam acara \"Steam\"\n$1,800\t419\t18,641\t$82,449,526\t95.9%\n$2,000\t382\t15,159\t$75,541,325\t95.5%\n$2,070\t363\t12,336\t$69,560,305\t95.6%\n$2,300\t323\t11,644\t$67,984,432\t95.0%\n$2,500\t299\t10,950\t$66,203,929\t95.0%\n\nBaca satu baris demi satu baris; baris-baris tersebut merupakan himpunan bagian yang saling bersarang dari sensus yang sama, bukan populasi yang terpisah. “Nilai dasar” mengalikan nilai setiap pasar terendah Data tersebut dihitung berdasarkan jumlah eksemplar yang tercantum, sehingga secara otomatis jumlah buku yang tersedia di rak menjadi lebih sedikit dari yang sebenarnya. Buka kumpulan data ↗\n\n06 / kelangkaan yang bisa dihitung\nBetapa sedikitnya barang-barang ini yang benar-benar tersedia untuk dijual\n\nBUFF membagi rak setiap barang menjadi beberapa rentang harga dan mencantumkan jumlah eksemplar yang tersedia di masing-masing rentang. Hal ini mengubah kata “langka” menjadi angka — dan menentukan harga berdasarkan kondisi barang secara terpisah dari desainnya.\n\n298 DAFTAR SALINAN\nAWP | Kisah Naga\n\n8 berbagai varian dengan harga yang berbeda-beda. Yang paling mahal, Suvenir AWP | Dragon Lore (Baru dari Pabrik), bertanya $12,363 dengan salinan *20* yang tersedia di rak.\n\nDi bagian rak yang paling bagus untuk mengapung (0–0.01) terdapat 2 salinan, bertanya $17,875 — selisih harga sebesar +45% di atas harga dasar yang diminta untuk barang tersebut, hanya berdasarkan kondisinya saja.\n\n607 DAFTAR SALINAN\nM4A4 | Howl\n\n12 berbagai varian dengan harga yang berbeda-beda. Yang termahal, Suvenir M4A4 | Howl (Baru dari Pabrik), bertanya $14,895 dengan salinan buku *2* yang tersedia di rak.\n\n213 DAFTAR SALINAN\nAK-47 | Wild Lotus\n\n7 berbagai varian dengan harga yang berbeda-beda. Yang paling mahal, Suvenir AK-47| Wild Lotus (Baru dari Pabrik), bertanya $14,895 dengan salinan buku *2* yang tersedia di rak.\n\n310 DAFTAR SALINAN\nAWP | Gungnir\n\n7 berbagai varian dengan harga yang berbeda-beda. Yang paling mahal, Suvenir AWP | Gungnir (Sedikit Bekas Pakai), bertanya $14,895 dengan salinan buku *2* yang tersedia di rak.\n\nMengapa hal ini penting bagi bagian-bagian lain dalam dokumen ini: Ini bukanlah hal-hal yang abstrak. Ada beberapa ratus salinan dari setiap trofi yang tersebar di rak terbuka di seluruh dunia, masing-masing terikat pada satu akun Steam dan dipindahkan melalui satu transaksi Steam. Pasar yang begitu terbatas ini adalah pasar di mana satu inventaris yang dicuri merupakan peristiwa yang dapat diukur, dan di mana teknik pengambilalihan akun yang didokumentasikan di bagian lain dalam penyelidikan ini memberikan keuntungan langsung dan dapat dihitung.\n\nJumlah yang tercantum merupakan daftar produk yang tersedia secara real-time di satu platform pasar pada saat data diambil, bukan jumlah total yang ada. Barang yang disimpan dalam persediaan pribadi tidak dihitung di sini. Buka kumpulan data float ↗\n\n07 / tangga yang tak terlihat\nSemakin mahal barangnya, semakin jauh lokasinya dari tempat-tempat yang terlihat\n\nSetiap tingkatan di bawah ini merupakan kategori bukti yang berbeda. Ketiganya sengaja tidak digabungkan menjadi satu angka.\n\nAnak tangga\tGambar\tFakta macam apa ini?\nCeiling on Valve's own market\t~$1,800\tPublished rule, stated in the Steam Community Market FAQ.\nDearest ask several marketplaces agree on\t$66,285\tMeasured by us in this snapshot. Sticker | Titan (Holo) | Katowice 2014, quoted by four marketplaces within 5.2% of one another. An ask, not a sale.\nDearest ask seen on any single shelf\t$148,954\tOne marketplace, one copy, no second marketplace agreeing — and equal to a round CNY 1,000,000 at the snapshot rate. Listed here as the outer edge of what sellers ask, and relied on for nothing.\nPublic marketplace sale\t$49,999\tSpecialist Gloves | Crimson Kimono (FN) on CSFloat, as reported by SteamAnalyst. Platform-recorded, third-party reported.\nReported private sale\t$400,000\tAK-47 | Case Hardened, reported by PC Gamer in April 2023. Journalism, not a record we hold.\nReported offer, declined\t$1,500,000\tBlue Gem Karambit, pattern #387. No sale took place and the figure has not been independently confirmed. Included to mark the ceiling of the claims, not to assert a value.\n\nAspek struktural: Pasar Valve berhenti di sekitar $1,800.. Pasar pihak ketiga melanjutkan perdagangan hingga sekitar $66,000—di mana beberapa di antaranya setuju—dan hingga sekitar $150,000—di mana hanya satu yang setuju. Di atas angka tersebut, tidak ada platform sama sekali — transfer terbesar atas aset yang diterbitkan oleh Valveterjadi secara pribadi, antarindividu, tanpa pencatatan, tanpa catatan platform, tanpa verifikasi identitas, dan tanpa pelaporan. Transfer itu sendiri tetap berjalan di Steam. Semakin tinggi nilainya, semakin sulit bagi siapa pun untuk melihatnya, dan infrastruktur yang mendukungnya sepenuhnya merupakan milik Valve.\n\nDua poin terakhir merupakan laporan dari pihak lain, yang disebutkan sebagai sumbernya. Proyek ini tidak memverifikasi laporan tersebut dan tidak mengandalkan laporan tersebut dalam menarik kesimpulan apa pun.\n\nSemua kategori yang diamati di 419\n\nSumber: https://phishdestroy.io/steam_dossier/id/elite_skins#register\n\n09 / asal-usul dan batasan\nPeriksa perhitungannya\n\nKami menampilkan data lokal dan sumber publik. Angka utama tersebut mencakup periode CSFloat pada tanggal pengambilan data.\n\nBatasan dan ketentuan yang ditetapkan oleh Valve sendiri\n\nSteam Pertanyaan Umum (FAQ) Pasar Komunitas ↗ diarsipkan 2026-09-21 ↗ mencantumkan perkiraan batas maksimum penawaran sebesar $1,800. Angka tersebut Perjanjian Pelanggan ↗ diarsipkan 2026-09-21 ↗ menetapkan batasan penggunaan komersial.\n\nDari mana asal harga-harga tersebut\n\nHarga, jumlah saham yang diperdagangkan, dan kisaran jumlah saham yang beredar diambil dari cs2.sh data pasar API melalui langganan komersial berbayar, dengan menggunakan kunci lisensi. Tidak ada platform pasar yang diambil datanya, dan tidak ada akun atau kredensial platform pasar yang digunakan. Penyedia tersebut menggabungkan data dari BUFF, Youpin, CSFloat, Skinport, C5Game, dan Steam Community Market; semua angka dinyatakan dalam USD sesuai yang dilaporkan. Buka manifes asal-usul ↗ — sistem ini mencatat titik akhir yang tepat, waktu pengambilan, dan nilai hash SHA-256 dari snapshot mentah tersebut, sehingga pembaca independen yang memiliki kunci sendiri dapat mengakses data yang sama dan menghitung ulang setiap angka pada halaman ini.\n\nApa yang tidak dapat kami peroleh\n\nLangganan yang dibeli hanya mencakup snapshot terkini. Titik akhir historis dan arsip tidak tersedia bagi kami, dan Halaman ini tidak membuat pernyataan apa pun mengenai tren apa pun, harga di masa lalu, atau perubahan apa pun seiring berjalannya waktu. Segala sesuatu di sini hanyalah sebuah momen tunggal, yang diberi tanggal.\n\nDaftar \"CSFloat\" edisi sebelumnya\n\nVersi pertama pameran ini mencakup kategori-kategori “245” dari satu cuplikan katalog CSFloat yang diterbitkan pada tanggal 20 September 2026: gambar tersebut masih ada di sini ↗. Data saat ini lebih luas karena mencakup lima pasar, bukan hanya satu. Kedua data tersebut merupakan pengumpulan data yang terpisah dan tidak boleh dijumlahkan.\n\nPernyataan penegakan khusus dari Valve\n\nPembaruan tentang perdagangan item dalam game \"2016\" dari Valve ↗ diarsipkan 2026-09-21 ↗ menargetkan operator perjudian yang menggunakan OpenID dan akun otomatis yang dibuat melalui Steam. Kebijakan ini cakupannya lebih sempit dibandingkan larangan terhadap semua pasar eksternal.\n\nBatas interpretasi\n\nIni adalah penawaran, bukan penjualan. Sebuah nama produk di pasar dapat mencakup beberapa barang fisik dengan detail warna, pola, atau stiker yang berbeda-beda. Catatan ini tidak mengukur nilai pasar total maupun niat Valve.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Pendaftaran Elite Skins — Batas Atas Pasar $1,800"
          },
          {
            "level": 2,
            "id": null,
            "text": "Batas bawah dalam dolar yang dapat diukur"
          },
          {
            "level": 3,
            "id": null,
            "text": "Mengapa ini merupakan angka pasti, bukan perkiraan"
          },
          {
            "level": 2,
            "id": null,
            "text": "Apa yang tidak tercakup dalam batas tersebut"
          },
          {
            "level": 3,
            "id": null,
            "text": "★ Butterfly Knife | Doppler (Factory New)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Topi yang dikenakan Steam memicu penentuan harga di luar Steam"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam menutup daftar"
          },
          {
            "level": 3,
            "id": null,
            "text": "Dragon Lore: $10,940.85"
          },
          {
            "level": 3,
            "id": null,
            "text": "Pembagian harga dan transfer"
          },
          {
            "level": 2,
            "id": null,
            "text": "Layar atas juga menampilkan Dota 2"
          },
          {
            "level": 3,
            "id": null,
            "text": "Sabit Brutal yang Heroik"
          },
          {
            "level": 3,
            "id": null,
            "text": "Jubah Seni Gelap"
          },
          {
            "level": 3,
            "id": null,
            "text": "Bintang Bertenaga yang Rusak"
          },
          {
            "level": 2,
            "id": null,
            "text": "Temuan tersebut tidak bergantung pada batas atas yang tepat"
          },
          {
            "level": 2,
            "id": null,
            "text": "Betapa sedikitnya barang-barang ini yang benar-benar tersedia untuk dijual"
          },
          {
            "level": 3,
            "id": null,
            "text": "AWP | Kisah Naga"
          },
          {
            "level": 3,
            "id": null,
            "text": "M4A4 | Howl"
          },
          {
            "level": 3,
            "id": null,
            "text": "AK-47 | Wild Lotus"
          },
          {
            "level": 3,
            "id": null,
            "text": "AWP | Gungnir"
          },
          {
            "level": 2,
            "id": null,
            "text": "Semakin mahal barangnya, semakin jauh lokasinya dari tempat-tempat yang terlihat"
          },
          {
            "level": 2,
            "id": null,
            "text": "Semua kategori yang diamati di 419"
          },
          {
            "level": 2,
            "id": null,
            "text": "Periksa perhitungannya"
          },
          {
            "level": 3,
            "id": null,
            "text": "Batasan dan ketentuan yang ditetapkan oleh Valve sendiri"
          },
          {
            "level": 3,
            "id": null,
            "text": "Dari mana asal harga-harga tersebut"
          },
          {
            "level": 3,
            "id": null,
            "text": "Apa yang tidak dapat kami peroleh"
          },
          {
            "level": 3,
            "id": null,
            "text": "Daftar \"CSFloat\" edisi sebelumnya"
          },
          {
            "level": 3,
            "id": null,
            "text": "Pernyataan penegakan khusus dari Valve"
          },
          {
            "level": 3,
            "id": null,
            "text": "Batas interpretasi"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/id/#market-gap-section",
          "https://phishdestroy.io/steam_dossier/id/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/id/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/id/skin_atlas.html#grading",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-above-the-ceiling.json",
          "https://phishdestroy.io/steam_dossier/id/elite_skins#selected",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://csmarketcap.com/search?minPrice=1800&amp;page=1",
          "https://store.steampowered.com/agreement/?l=english",
          "http://web.archive.org/web/20260921022032/https://store.steampowered.com/agreement/?l=english",
          "https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921021947/https://store.steampowered.com/oldnews/22883",
          "https://phishdestroy.io/steam_dossier/id/#proxy-bypass-explainer",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/skinport-floor-over-cap.json",
          "https://docs.skinport.com/items",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-float-scarcity.json",
          "https://phishdestroy.io/steam_dossier/id/elite_skins#register",
          "https://cs2.sh/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/csfloat-catalogue.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/id/elite_skins.content.json",
      "export_json_sha256": "4e48db04a644835fb9ff8e1813d045ae02e2480151188981a3d37fba321e5df3"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "id/enforcement_audit.html",
      "language": "id",
      "title": "Sensus Valve tidak akan dipublikasikan — Laporan Steam",
      "source_url": "https://phishdestroy.io/steam_dossier/id/enforcement_audit",
      "source_html_sha256": "f74933384ed65aaaf5d678d96d2051c396c337e9d0c24febc895b437c99edffc",
      "exported_at": "2026-09-29T00:22:26.709Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "enforcement_audit.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/id/enforcement_audit.pdf?v=print-20260929-v5",
        "sha256": "88d4722d9e02b50bb9ea79bbc4ac23cddff7f0a66c31a66838ad0a9b20ceeb01",
        "bytes": 147845,
        "pages": 13
      },
      "integrity": {
        "signed_object": "enforcement_audit.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "enforcement_audit.content.json.asc",
        "digest_file": "enforcement_audit.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify enforcement_audit.content.json.asc enforcement_audit.content.json",
          "sha256sum -c enforcement_audit.content.json.sha256"
        ]
      },
      "content": {
        "text": "LAMPIRAN VI — SENSUS VALVE TIDAK AKAN DIPUBLIKASIKAN\nSeberapa besar jaringan akun di Steam? Kami menghitungnya sendiri.\n\nTidak ada angka resmi mengenai berapa banyak akun otomatisasi yang berjalan di Steam. Angka tersebut tidak perlu dirahasiakan: ruang ID Steam merupakan rentang bilangan bulat yang berurutan, dan Valve membagikan kunci API Web yang menjelajahi rentang tersebut. Jadi, kami mengambil populasi terbesar yang mengidentifikasi dirinya sendiri — komunitas ArchiSteamFarm — dan membaca setiap anggota satu kali melalui titik akhir pemblokiran milik Valve. Hal ini terjadi secara otomatis karena ASF, pada peluncuran pertama, secara otomatis bergabung dengan grup Steam kecuali jika pengguna secara eksplisit memilih untuk tidak bergabung atau menghapus centang pada pengaturan bergabung dengan grup (AutoJoinSteamGroup / Statistik). Karena pengaturan ini aktif secara default, keanggotaan grup mencakup populasi yang luas: jaringan bot komersial multi-akun yang aktif, penggemar kasual yang membiarkan akunnya menganggur, serta pemain biasa yang menjalankan perangkat lunak tersebut di akun pribadi mereka dan tidak pernah menghapus langganan default. Hal itu menjadikan keanggotaan grup ini sebagai sensus yang akurat mengenai jangkauan kumulatif perangkat lunak tersebut: 10,880,610 jumlah akun (dengan 5,360,499 anggota yang telah dikonfirmasi dan tidak memiliki batasan yang telah melewati gerbang toko $5.00). Lalu kami mengajukan satu-satunya pertanyaan yang penting — apa sebenarnya yang telah dilakukan Valve kepada mereka?\n\nApa yang tidak ada di halaman ini. Ini bukanlah argumen bahwa Valve harus memblokir sepuluh juta orang, dan ini juga bukan keluhan tentang para \"card farmer\". Setiap angka di bawah ini dicantumkan di sini karena satu alasan: Valve apakah memblokir pengguna secara permanen, dan alasan yang disampaikan secara tertulis adalah penggunaan komersial dari Steam serta otomatisasi. Hal ini mengukur bagaimana aturan yang sama diterapkan pada perilaku yang sama dalam skala besar — oleh seorang operator yang $5.00 membuka kunci, lisensi game, dan biaya Pasar Valve yang dikumpulkan sepanjang proses. Temuan utamanya adalah ketidakseimbangan, bukan praktik farming itu sendiri.\n\nJumlah 10,88 jutaPara penipu yang berkeliaran (53,5 ribu)Audit berbayar senilai 100 ribu vs audit gratis\n10,880,610Jumlah anggota grup ASF yang telah membaca API pemblokiran milik Valve (gabungan yang dibatasi dan yang tidak dibatasi)\n88.97%Belum pernah diblokir sama sekali — 9,680,599 akun masih aktif\n63.06%Dari akun yang diblokir, ada yang berbayar ($5+ pengeluaran) — 100,000 SRSWOR bagian (±0.39% MoE)\n67.77%Dari 51,732 pelaku penipuan yang telah diputus pengadilan, tidak ada satupun yang dikenai larangan penipuan (data sensus lengkap)\n01 — Skala\nSepuluh juta akun, dan sembilan dari sepuluh di antaranya belum pernah digunakan\n\nSebuah populasi yang menghitung dirinya sendiri, dibaca sekali melalui titik akhir milik Valve sendiri.\n\nMENGAPA HAL INI MENGHITUNG SENDIRI\nASF bergabung dengan grup ini khusus untuk Anda\n\nPada putaran pertama, ArchiSteamFarm set Statistik secara default disetel ke \"true\" dan bergabung dengan grup SC Farm Steam milik Archi. Seorang operator harus secara aktif memilih untuk keluar. Jadi, keanggotaan ini merupakan batas bawah jumlah instalasi — bukan batas atas. Operator yang menonaktifkan Statistik tidak tercatat; jumlah instalasi sebenarnya setidaknya sebesar ini.\n\nAPA YANG KAMI BACA\n10,880,610 jumlah entri\n\nDaftar anggota API mengembalikan total 10,880,610 SteamID64 — baik yang terbatas maupun yang tidak terbatas. Halaman grup Steam menampilkan 5,360,499 (hanya yang tidak terbatas). Setiap entri diproses satu kali melalui ISteamUser/GetPlayerBans pada 2026-09-23. Lima puluh lima menit dengan satu tombol.\n\nJAWABANNYA\n88.97% bersih\n\n1,200,011 tidak dikenai Steam larangan (11.03%). Yang lainnya 9,680,599 sama sekali tidak ada catatan apa pun — bukan larangan komunitas, bukan VAC, bukan apa-apa. Peternakan itu tidak dibubarkan. Peternakan itu dibiarkan tetap beroperasi. Klausul yang sama, yang ditujukan kepada satu orang, sudah cukup untuk mengeluarkan orang tersebut secara permanen.\n\nDari 10,880,610 akun, berapa banyak yang telah menyentuh angka Valve?\n\nSeluruh populasi yang telah dipindai, dipisahkan berdasarkan apakah Valve telah memberlakukan larangan apa pun. Bagian berwarna merah mencakup semua tindakan yang pernah dilakukan Valve terhadap armada ini.\n\n88.97%tidak pernah diblokir\n11.03%\nTidak ada larangan apa pun — 9,680,599 (88.97%)Memiliki larangan Steam — 1,200,011 (11.03%)\n10,880,610Anggota kelompok ASF telah diperiksa\n9,680,599Tidak pernah diblokir — 88.97%\n1,200,011Terapkan larangan apa pun — 11.03%\n55 menitUntuk menghitung semuanya, menggunakan satu kunci API\nBerapa biaya yang telah dikeluarkan armada ini Valve agar dapat beroperasi\n\nBukan perkiraan pendapatan peternakan tersebut. Melainkan batas bawah dari jumlah yang telah dibelanjakan di toko Valve — yang diperoleh dari aturan Valve sendiri, yang diterapkan pada perhitungan di atas.\n\nJumlah 10,880,610 mencakup daftar lengkap anggota grup ASF sebagaimana dikembalikan oleh API — ini mencakup akun terbatas maupun yang tidak terbatas. Steam sendiri Akun Pengguna Terbatas Halaman tersebut menyatakan bahwa akun terbatas tidak dihitung sebagai bagian dari Steam keanggotaan grup (mereka tidak termasuk dalam jumlah anggota grup yang ditampilkan), tetapi mereka tetap dapat muncul dalam daftar anggota yang mendasarinya. Himpunan bagian yang tidak dibatasi — akun-akun yang telah berbelanja setidaknya $5.00 di toko Steam — adalah tepat 5,360,499 — angka Steam ditampilkan di halaman grup, yang—sesuai aturan Steam sendiri—tidak mencakup akun-akun yang dibatasi. Perhitungan batas bawah $5.00 hanya berlaku untuk subset yang tidak dibatasi tersebut.\n\n5,360,499anggota tanpa batasan\n(Jumlah grup yang ditampilkan oleh Steam)\n×\n$5.00Nilai minimum milik Valve\nagar tidak lagi dibatasi\n=\n$26,802,495batas pengeluaran di toko\noleh himpunan bagian yang tidak terbatas\n\nIni merupakan batas bawah dari jumlah uang yang telah diterima oleh Valve dari bagian armada yang tidak dibatasi — bukan perkiraan pendapatan, bukan pula klaim laba. Pengeluaran aktual per akun lebih tinggi bagi sebagian besar; angka $5.00 hanyalah ambang batas minimum yang diperlukan.\n\nPendapatan tambahan: biaya hingga 66.7% dari volume komoditas yang dibudidayakan. Selain biaya masuk sebesar $26.8M, setiap kartu dan barang yang dijual di Pasar Komunitas dikenakan biaya minimum wajib sebesar dua sen (Valve), yang terdiri dari biaya $0.01 Steam + biaya penerbit sebesar $0.01). Pada kartu dan barang bekas biasa seharga 3 sen, Valve mengambil 2 sen dari 3 sen — yang secara efektif berarti pemotongan sebesar 66.67% yang menguntungkan Valve, jauh melampaui tingkat pemasaran utama 15%.\n\nPeringatan penting terkait populasi: Keanggotaan grup bukanlah bukti bahwa setiap akun adalah bot khusus, dan juga tidak mencakup semua bot di Steam. Secara default, ASF secara otomatis mendaftarkan akun ke grup komunitasnya saat diluncurkan; kecuali jika pengguna secara eksplisit menghapus centang atau menonaktifkan opsi konfigurasi tersebut (AutoJoinSteamGroup), pemain aktif, pemain yang hanya sesekali bermain, dan anggota komunitas tetap terdaftar dalam daftar bersama armada farming otomatis. Selain itu, sanksi Steam tidak disertai dengan alasan yang diumumkan secara publik. Temuan ini merupakan tingkat empiris di seluruh populasi yang terkait dengan perangkat lunak ini, bukan putusan individual terhadap akun mana pun. Agregat, dapat direproduksi: asf-ban-census-2026-09-23.json.\n\n02 — Geografi\nDi mana armada itu berada\n\nHanya 8.5% dari akun-akun yang diblokir yang mencantumkan negara asal sama sekali. Di antara akun-akun yang mencantumkannya, porsi terbesar berasal dari Amerika Serikat.\n\nProfil Steam memiliki kolom negara yang bersifat opsional. 100,413 dari 1,182,811 akun yang diblokir mengisinya — 8.5%.† Di antara kelompok minoritas tersebut, Amerika Serikat memimpin dengan nilai 15.5%, disusul Ukraina, Tiongkok, dan Rusia, sedangkan sisanya tersebar luas di seluruh Eropa, Amerika Latin, dan Asia Tenggara. Tidak ada yang memverifikasi data ini: Afghanistan berada di sepuluh besar, yang kira-kira sesuai dengan nilainya. 91.5% lainnya diabaikan alih-alih diberi peringkat, sehingga yang tercantum di bawah ini hanyalah gambaran dari kelompok minoritas yang memilih sendiri — bukan peta armada, dan bukan dasar untuk menentukan dari mana armada tersebut dioperasikan.\n\nAkun yang diblokir berdasarkan negara yang disebutkan\n\n15 negara teratas di antara 100,413 akun yang diblokir yang mengungkap lokasi umum. Persentase tersebut merupakan bagian dari subset lokasi tersebut. Arahkan kursor untuk melihat jumlahnya.\n\n0%\n5%\n10%\n15%\n20%\nUnited States\nUkraine\nChina\nRussia\nCanada\nAustralia\nJapan\nBrazil\nGermany\nAfghanistan\nUnited Kingdom\nRomania\nFrance\nPhilippines\nIndia\n\nLokasi dibaca dari GetPlayerSummaries untuk subset yang diblokir. Bidang ini ditetapkan oleh pemilik akun dan tidak diverifikasi oleh siapa pun, sehingga entri yang berasal dari server keluar VPN atau entri iseng dianggap sama dengan entri yang sebenarnya.\n\n03 — Kesegaran\nLaporan terbaru, bukan tumpukan pekerjaan lama\n\nBerdasarkan waktu pembuatan akun, populasi pengguna yang diblokir ini merupakan pengguna baru, bukan sisa dari era kartu perdagangan.\n\nSeandainya ini adalah masalah lama yang sedang dibersihkan secara bertahap, akun-akun yang diblokir seharusnya lebih banyak berasal dari tahun-tahun awal kartu perdagangan. Namun, kenyataannya justru sebaliknya. Dari 1,132,852 akun yang diblokir yang menampilkan tanggal pembuatan, 70% dibuat pada tahun 2020 atau setelahnya, dan hampir setengahnya dibuat sejak tahun 2023. Angka tersebut meningkat dari 59,175 yang diciptakan pada tahun 2017 hingga mencapai puncaknya sebesar 227,030 yang dibuat pada tahun 2024 saja. Masing-masing dari mereka sudah melewati gerbang toko $5.00 sebelum gerbang tersebut sempat membaca kartu mereka, sehingga biaya masuk dipungut dari masing-masing orang.\n\nSaat akun-akun yang diblokir tersebut dibuat\n\nTahun pembuatan akun dari 1,132,852 anggota yang diblokir yang menampilkan tanggal pembuatannya. Rentang waktunya adalah 2020–2026, bukan era kartu koleksi 2013–2015. Puncaknya: 2024. Arahkan kursor untuk melihat jumlahnya.\n\n0k\n63k\n125k\n188k\n250k\n'13\n'14\n'15\n'16\n'17\n'18\n'19\n'20\n'21\n'22\n'23\n'24\n'25\n'26\n70%Dari akun-akun yang diblokir yang dibuat pada tahun 2020 atau setelahnya\n227,030Akun yang diblokir yang dibuat pada tahun 2024 — tahun dengan jumlah terbanyak\n51,701Titik terendah pada tahun 2021, yang terletak di antara dua tahun puncak — belum dapat dijelaskan\n2003→2026Data rentang tersedia, namun data massa hanya mencakup enam tahun terakhir\n\nKarya ini dibuat pada GetPlayerSummaries untuk subset akun yang diblokir, yang telah dihilangkan duplikatnya berdasarkan SteamID64. Tanggal pembuatan merujuk pada saat akun tersebut dibuat, bukan saat akun tersebut diblokir atau saat mulai melakukan farming; data ini digunakan di sini sebagai bukti seberapa baru populasi tersebut, bukan sebagai bukti niat. Tiga hal yang tidak ditampilkan dalam grafik ini:\n\nSebuah tren setelah tahun 2024. Akun yang dibuat pada tahun 2025 atau 2026 memiliki waktu yang lebih singkat untuk terkena pemblokiran, dan tahun 2026 mencakup sembilan bulan — sehingga 227,030 → 121,070 → 16,534 merupakan bentuk sensor, bukan penurunan.\nTingkat penolakan. Tahun pembuatan hanya diambil dari akun-akun yang diblokir, sehingga tidak ada pembilang. Pertumbuhan basis pengguna saja sudah cukup untuk menghasilkan pola ini.\nMengapa tahun 2021 mengalami kegagalan. 51,701 terletak di antara 105,821 dan 104,641, di bawah setengah dari masing-masing tetangganya. Tidak ada penjelasan resmi mengenai hal ini; angka tersebut dibiarkan terlihat alih-alih dihaluskan.\n04 — Waktu\nKetika Valve berlaku, hal itu berlaku pada tahun pertama\n\nAlasan yang paling jelas mengapa 88.97% belum disentuh adalah adanya tumpukan pekerjaan yang tertunda. Larangan-larangan yang sudah lama itu justru menunjukkan sebaliknya.\n\nBerapa lama akun tersebut sudah ada saat pemblokiran diberlakukan\n\nUsia akun pada saat pemblokiran, untuk 293,750 akun yang diblokir yang mencantumkan tanggal pembuatan dan tanggal pemblokiran terakhir. Lebih dari setengahnya terdeteksi dalam tahun pertama.\n\n0%\n10%\n20%\n30%\n40%\n<6 mo\n33.7%\n6–12 mo\n21.5%\n1–2 y\n20.6%\n2–5 y\n14.3%\n5 y+\n10.0%\n55.1% inside the first year\nDilarang dalam tahun pertama — 55.1%Diblokir kemudian — 44.9%\n0,80 tahunUsia median akun saat pemblokiran diberlakukan\n55.1%Diblokir dalam tahun pertama sejak akun dibuat\n33.7%Dilarang dalam enam bulan pertama\n293,750Akun yang mencantumkan kedua tanggal tersebut\n\nInilah jawaban atas argumen pembelaan yang jelas itu. Jika 88.97% dari armada tersebut belum tersentuh karena penegakan hukum memang lambat — tumpukan kasus yang sedang diproses — maka larangan-larangan yang lakukan ...akan terlihat lebih tua. Justru sebaliknya: usia median akun yang diblokir adalah berusia sembilan setengah bulan, dan yang ketiga — 33.7% — tertangkap dalam waktu enam bulan. Ketika Valve bekerja pada populasi ini, ia bekerja dengan cepat. Sembilan dari sepuluh yang masih berkeliaran tidak sedang mengantri.\n\nUsia saat dilarang = tanggal pembuatan dari GetPlayerSummaries dikurangi dari tanggal larangan yang tersirat dalam HariSejakLaranganTerakhir, baca selengkapnya 2026-09-23. Nilai ini dihitung hanya jika kedua nilai tersebut tersedia: 293,750 dari 1,200,011 akun yang diblokir. Akun-akun lainnya tidak melaporkan nilai \"hari sejak\" dan diabaikan, bukan diasumsikan — jadi, pahami ini sebagai bentuk dari subset yang diberi tanggal, bukan dari setiap pemblokiran.\n\n05 — Apa sebenarnya larangan tersebut\nKetika Valve aktif, hal itu tidak menghentikan bot\n\nDari 11% yang dikenai larangan apa pun, perhatikan larangan mana yang dimaksud.\n\nLarangan bukanlah larangan. Dari 1,200,011 akun, Valve di antaranya telah ditandai, 99.8% membawa sebuah komunitas larangan — pembatasan pada forum, profil, dan grup yang tidak berdampak apa pun pada bot perdagangan. Akun tersebut tetap dapat menerima kartu, tetap dapat melakukan perdagangan, dan tetap dapat memindahkan inventaris. 22.2% memiliki setidaknya satu larangan bermain dan 3.9% larangan VAC; kategori-kategori ini tumpang tindih, sehingga tidak dijumlahkan. Satu-satunya sanksi yang benar-benar menghentikan perdagangan, yaitu larangan ekonomi/perdagangan, diterapkan pada 5,214 akun. Kami tidak mendasarkan kasus ini pada angka tersebut — larangan perdagangan memang jarang terjadi, sekitar Steam secara umum. Inti dari grafik ini lebih sederhana: bahkan fraksi Valve apakah Touch terus melakukan perdagangan.\n\nAlasan sebenarnya mengapa para 11% yang diblokir itu diblokir\n\nSetiap jenis pemblokiran sebagai persentase dari seluruh anggota yang dipindai 10,880,610. Sebuah akun dapat memiliki lebih dari satu jenis pemblokiran. Arahkan kursor untuk melihat jumlahnya.\n\n0%\n4%\n8%\n11%\n15%\nCommunity ban\nGame ban\nVAC ban\nEconomy / trade ban\n\nLarangan Steam tidak memiliki kolom alasan, sehingga tidak ada satu pun dari larangan ini yang secara khusus dikaitkan dengan praktik \"card farming\" — ini adalah gabungan dari berbagai jenis larangan yang ada, disandingkan dengan apa yang sebenarnya dibatasi oleh masing-masing jenis larangan tersebut. Larangan komunitas tidak menghentikan aktivitas perdagangan; sedangkan larangan ekonomi/perdagangan justru melakukannya. Ringkasan: asf-ban-census-2026-09-23.json.\n\n06 — Kelompok populasi lainnya\nPara penipu Valve, mari kita lihat: Sensus Lengkap 51,732\n\nDaftar kedua yang independen — kasus penipuan yang dikonfirmasi oleh komunitas — yang dievaluasi berdasarkan API resmi yang sama.\n\nKelompok “otomatisasi” mungkin bisa dianggap sekadar sebagai orang-orang pengangguran yang tidak berbahaya. Namun, hal itu tidak berlaku bagi kelompok kedua. SteamRep adalah basis data reputasi komunitas yang telah lama beroperasi; sebuah akun yang ditandai DILARANG Telah ada seorang penipu yang dinyatakan bersalah oleh komunitas tersebut, dengan bukti korban yang terdokumentasi serta riwayat obrolan transaksi. Kami telah menyelesaikan sensus 100% terhadap semua 51,732 profil yang berstatus DIBLOKIR berdasarkan API Web resmi Steam (ISteamUser/GetPlayerBans/v1) — dan hanya menghitung sanksi yang berkaitan dengan penipuan. Larangan VAC ditujukan untuk kecurangan melalui perangkat lunak dalam permainan (aimbots, wallhacks); larangan ini tidak berdampak apa pun terhadap seorang pedagang dan bukan bukti Valve yang dijadikan dasar tindakan atas kasus penipuan, sehingga tidak dihitung sebagai penegakan hukum terkait penipuan.\n\nDari seluruh data sensus akun 51,732, 67.77% — 35,059 pelaku penipuan yang telah diputuskan bersalah — sama sekali tidak memiliki larangan yang berkaitan dengan penipuan dari Valve: Mereka masih bisa bertransaksi, masih bisa mengirim permintaan pertemanan ke korban baru, dan masih bisa mengirim pesan. Hanya 32.23% yang dikenai larangan komunitas atau larangan bertransaksi, dan larangan bertransaksi — satu-satunya tindakan yang benar-benar memutus transfer inventaris — hanya diterapkan pada 18.81% (9,731 akun). Selain itu, 12.81% (6,627 akun) dikenai VAC larangan bermain atau larangan game semata-mata karena kecurangan dalam game, sementara tetap tidak dikenai pembatasan apa pun dalam Steam perdagangan.\n\nPenipu yang telah dikonfirmasi, berdasarkan apakah Valve telah menjatuhkan sanksi yang berkaitan dengan penipuan (Full Census)\n\nSemua profil yang 51,732 SteamRep-DIBLOKIR, dikelompokkan berdasarkan apakah Valve menerapkan pemblokiran komunitas atau pemblokiran perdagangan. Pemblokiran VAC dan pemblokiran dalam game tidak termasuk — karena keduanya tidak berkaitan dengan penipuan. Arahkan kursor untuk melihat jumlahnya.\n\n0%\n18%\n35%\n53%\n70%\nNo scam-relevant ban\nCommunity or trade ban\n0%\n6%\n13%\n19%\n25%\nCommunity ban\nTrade / economy ban\nVAC (not fraud)\nGame ban\n51,732SteamRep — Profil yang DIBLOKIR telah diaudit — 100% sensus lengkap\n35,059Tidak memiliki larangan terkait penipuan (67.77%)\n18.81%Terapkan larangan perdagangan yang memberantas penipuan (9,731)\n32.23%Saham Valve terkena larangan oleh komunitas atau larangan perdagangan (16,673)\n\nSteamRep adalah basis data reputasi pihak ketiga yang dinilai oleh komunitas, bukan keputusan Valve — dan itulah intinya: bukti eksternal, yang diukur berdasarkan apa yang dilakukan Valve sendiri. Semua profil 51,732 yang DIBLOKIR dari ekspor kanonik telah dicocokkan secara langsung dengan ISteamUser/GetPlayerBans/v1. \"Terkait penipuan\" berarti larangan beraktivitas di komunitas atau larangan ekonomi/perdagangan; VAC (12.81%) dan larangan bermain game (3.86%) dihitung secara terpisah karena keduanya berkaitan dengan kecurangan, bukan penipuan. Kumpulan data audit lengkap: steamrep_steam_bans.csv.\n\nDua populasi, satu temuan\n\nIni bukanlah orang yang sama dan bukan pula perilaku yang sama. Yang satu adalah sepuluh juta akun otomatis; yang lain adalah lima puluh tiga ribu penipu yang telah diputus bersalah. Yang menjadi kesamaan di antara keduanya adalah bentuk hasilnya: sembilan dari sepuluh rekening pertanian tidak pernah digunakan, dan lebih dari dua pertiga (67.77%) pelaku penipuan yang telah teridentifikasi tidak dijatuhi sanksi apa pun terkait penipuan tersebut. Larangan komunitas Valve memang diterapkan secara bebas untuk membatasi akses ke forum dan profil, bukan untuk transaksi. Tombol lapor, basis data reputasi, serta larangan yang menghentikan penipuan: semuanya ada, namun semuanya kurang dimanfaatkan. Bandingkan hal tersebut dengan penolakan yang telah diarsipkan dalam berkas utama, di mana perusahaan yang sama secara permanen menghapus satu akun dan mengutip penggunaan komersial serta otomatisasi sebagai alasannya — klausul tersebut tidak tidak aktif, melainkan ditujukan secara spesifik.\n\n07 — Masalah Akses Akun $5.00 & Pembajakan Akun\nAudit empiris akun 100,000: botnet bukanlah akun gratis yang bisa dibuang begitu saja\n\nLogika pengambilan sampel statistik dan pembuktian matematis: mengapa mengambil nilai 100,000 apa pun akan menghasilkan hasil yang persis sama.\n\nAlasan utama yang dikemukakan Valve kepada pihak regulator dan lembaga perlindungan konsumen adalah bahwa penipuan otomatis dan praktik \"farming\" dilakukan melalui akun-akun \"sekali pakai\" yang bersifat sementara dan gratis, yang dengan cepat diblokir. Berdasarkan aturan yang diterbitkan oleh Valve, sebuah akun adalah Terbatas sampai jumlah yang dibelanjakan mencapai setidaknya $5.00 USD di toko Steam, yang membuatnya tidak dapat melakukan transaksi, mengirim permintaan pertemanan, maupun menggunakan fitur API. Kami memverifikasi klaim ini secara langsung dengan menguji status monetisasi dari sampel yang representatif dan secara matematis valid dari 100,000 diblokir Steam akun diambil dari korpus metadata profil 1,182,811 kami.\n\nPROTOKOL PENGAMBILAN SAMPEL (SRSWOR)\n100,000 Irisan yang Tidak Memihak\n\nDiambil dari N = 1,182,811 akun unik yang diblokir Steam menggunakan metode Simple Random Sampling Without Replacement melalui PRNG yang seragam secara kriptografis. Setiap akun memiliki probabilitas inklusi yang sama sebesar P = n / N ≈ 8.45%, sehingga sepenuhnya menghilangkan bias kelangsungan hidup dan bias aktivitas.\n\nBUKTI MATEMATIKA\nMargin Kesalahan < ±0.4%\n\nMenerapkan rumus Koreksi Populasi Terbatas (FPC) pada 99% Interval Kepercayaan (Z = 2,576):\nMoE = Z × √[p(1-p)/n] × √[(N-n)/(N-1)] ≈ ±0.39%\n\nREPRODUKTIVITAS\nMengapa Setiap 100 ribu Memberikan Hasil yang Sama\n\nKarena batas kesalahan berada di bawah ±0.4% pada tingkat kepercayaan 99%, Secara matematis, pengambilan sampel independen apa pun dari akun 100,000 dijamin akan berada dalam rentang 63.06% ± 0.39% (62.67% hingga 63.45%). Sampel tersebut mewakili seluruh populasi yang diblokir sebanyak 1,18 juta orang.\n\nHasil audit tersebut sepenuhnya membantah dalih \"bot sekali pakai\". Dari 100,000 akun yang diaudit melalui antarmuka profil XML lama milik Steam: 61,490 akun (63.06% dari akun yang diklasifikasikan) adalah akun Non-Limited (Berbayar) yang telah menghabiskan setidaknya $5.00 untuk Steam. Hanya 36,021 (36.94%) adalah akun gratis yang terbatas, sedangkan 2,489 adalah akun yang belum dikonfigurasi atau akun pribadi.\n\n100,000 Akun yang Diblokir: Berbayar ($5+ Pengeluaran di Toko) vs Status Gratis Terbatas\n\nAudit empiris terhadap 100,000 akun yang diblokir yang diambil secara acak. Lebih dari 63% di antaranya telah lolos dari sistem verifikasi keuangan berbayar milik Valve. Arahkan kursor untuk melihat jumlahnya.\n\n0%\n16%\n33%\n49%\n65%\nNon-limited (Paid ≥ $5.00)\nLimited (Free < $5.00)\n100,000Populasi yang menjadi sampel (SRSWOR, N=1,18 juta)\n63.06%Akun berbayar tanpa batasan (akun 61,490)\n±0.39%Margin kesalahan pada interval kepercayaan 99%\n~745,800Akun berbayar yang diekstrapolasi dalam kumpulan data 1,18 juta akun yang diblokir\nRealitas Struktural: Penutupan Rekening dalam Skala Industri\n\nMengapa 63% dari akun-akun yang diblokir dalam sampel tersebut merupakan akun berbayar yang pernah membelanjakan uang sungguhan di toko Valve? Operator botnet tidak akan menghabiskan jutaan dari kantong mereka sendiri untuk akun-akun sekali pakai. Rasio ini menunjukkan besarnya akun yang diretas dan disusupi beredar di dalam ekosistem.\n\nTimbangan ini dapat diamati secara langsung di platform bawah tanah: di pasar-pasar seperti FSB Market (nama samaran; nama asli tidak disebutkan di sini), di atas 550,000 Steam akun (log pencurian, data hasil serangan phishing, serangan credential stuffing) secara aktif ditawarkan untuk dijual setiap saat (phishdestroy.io/live-intel). Pasar ini memverifikasi identitas pembeli dan penjual menggunakan OpenID Steam milik Valve sendiri, dan baik FSB Market atau forum terkait diblokir oleh Filter Tautan Valve.\n\nSebagaimana diatur dalam Bagian 06, Valve tidak secara proaktif memberantas kegiatan penipuan ini: 67.77% dari penipu yang telah dikonfirmasi oleh komunitas tidak memiliki larangan penipuan sama sekali di Steam, dan 88.97% dari armada otomatisasi tersebut tetap sama sekali tidak tersentuh. Akun-akun tersebut beroperasi secara bebas, melakukan otentikasi melalui API resmi, dan melakukan perdagangan di seluruh ekosistem tanpa hambatan sama sekali.\n\nDiagram Arsitektur Bukti Forensik & Penegakan Hukum\nAlur interaktif dari 10,88 juta akun yang dipindai ke 100 ribu sampel empiris dan 53,5 ribu penipu yang terkonfirmasi · Klik tautan untuk memeriksa bukti mentah\nTingkat 01 · 10,88 juta Sensus Armada Otomatisasi\nPopulasi otomatisasi terbesar yang mengidentifikasi diri di Steam, secara berurutan melewati API larangan resmi Valve. Hal ini membuktikan bahwa armada bot komersial beroperasi di 88.97% tanpa konsekuensi hukum, meski telah membayar puluhan juta sebagai biaya masuk.\n9,680,599 88.97% Aktif & Belum Tersentuh\nAkun yang menjalankan perangkat lunak otomatis dan tidak pernah tercatat pernah dikenai pemblokiran apa pun.\nData Sensus JSON Mentah (1,2 KB) ↗Periksa Bagian 01 ↗\n$26,802,495 Batas Bawah Pendapatan Langsung dari Toko\nDikumpulkan oleh Valve dari 5,360,499 anggota non-terbatas yang telah melampaui ambang batas masuk minimum $5.00.\nAudit Ekonomi Kartu ↗Valve $5 Pertanyaan Umum tentang Aturan ↗\n1,200,011 11.03% Himpunan yang Ditandai\n99.8% hanya memberlakukan larangan di komunitas kosmetik; aktivitas perdagangan tetap berjalan di 99.95% akun.\nRincian Jenis Ban ↗DB yang Diblokir (60,4 MB) ↓\nTingkat 02 · 100,000-Audit Sampel Empiris Akun (N = 1,182,811)\nContoh SRSWOR yang dievaluasi melalui titik akhir XML lama. Margin kesalahan yang terbukti secara matematis < ±0.4% pada interval kepercayaan 99%. Membantah klaim bahwa bot yang diblokir adalah akun sekali pakai gratis.\n61,490 (63.06%) Akun Berbayar Tanpa Batasan ($5+ Pengeluaran)\nLebih dari 63% dari akun yang diblokir merupakan transaksi berbayar. Jika diekstrapolasi, jumlahnya mencapai sekitar 745,800 akun berbayar (dengan batas bawah $3.73M+) dalam kelompok akun yang diblokir.\nHasil Terbatas dalam Format CSV (2,1 MB) ↓Laporan Forensik 100k ↗\n36,021 (36.94%) Akun Gratis Terbatas (< $5.00)\nSebagian kecil profil yang diblokir sesuai dengan kriteria \"bot sekali pakai\" yang disebutkan oleh Valve. Akun-akun 2,489 tidak dikonfigurasi atau bersifat pribadi.\nPotongan Sampel CSV 100 ribu (8,5 MB) ↓Analisis Pengeluaran MD ↗\n34.67% vs 63.93% Audit Pembersihan Profil\nValve telah menghapus nama panggilan dan menggantinya dengan SteamID64 mentah pada 34,673 akun, namun membiarkan nama kustom dan avatar tetap utuh pada 63,928 akun yang diblokir.\nBagian Sanitasi ↗Gambaran Umum Peta Jalan ↗\n34.59% Warisan Akun Lama (Dibuat pada 2003–2019)\nLebih dari sepertiga akun yang diblokir terdaftar antara 5 hingga 20 tahun atau lebih yang lalu, yang membuktikan adanya pembajakan akun dalam skala besar terhadap pemain Steam yang telah lama bermain.\nKronologi Usia ↗Penolakan Dukungan ↗\nTingkat 03 · 51,732 SteamRep Daftar Penipu yang Telah Terkonfirmasi\nData lengkap 100% mengenai pelaku penipuan yang telah diputus oleh komunitas, lengkap dengan riwayat obrolan korban dan bukti transaksi, yang dicocokkan dengan API pemblokiran resmi Steam. Hal ini membuktikan adanya kegagalan penegakan aturan secara sistemik.\n35,059 (67.77%) Nol Larangan Akibat Penipuan (Kebal Hukum Sepenuhnya)\nLebih dari dua pertiga pelaku penipuan yang terverifikasi tidak dikenai larangan Komunitas maupun Perdagangan dari Valve. Mereka dapat beroperasi sepenuhnya untuk melakukan perdagangan dan menambah korban.\nSteamRep Larangan API (2,6 MB) ↓SteamRep Laporan Audit ↗\n9,731 (18.81%) Ekonomi / Larangan Perdagangan\nSatu-satunya sanksi yang menghentikan proses likuidasi persediaan. Hanya ditemukan pada kurang dari seperlima pelaku penipuan yang telah terkonfirmasi.\nSteamRep Sumber (2,1 MB) ↓Periksa Bagian 06 ↗\n6,627 (12.81%) Larangan Kecurangan yang Tidak Relevan (Hanya VAC)\nDiblokir karena menggunakan aimbot/wallhack dalam permainan, sementara kemampuan perdagangan dan phishing mereka tetap aktif.\nVAC Analisis Ketidakrelevanan ↗Garis Waktu Keamanan ↗\nTingkat 04 · Peretasan Situs Wiki & Pelanggaran Keamanan Infrastruktur Agustus 2026\nPerubahan isi dokumentasi internal pengembang, pembatasan akses editor komunitas, serta kegagalan sistem keamanan perbatasan yang tidak terlindungi, semuanya tercatat dalam paket bukti.\n1,200+ Tim Redaksi Catatan Konflik VDC Wiki\nPara editor komunitas yang berusaha memperbaiki tautan phishing dan templat spam secara sistematis diblokir oleh filter otomatis, sementara staf Valve mengabaikan peringatan tersebut.\nLaporan Konflik Rusia (127 KB) ↗Laporan Klasifikasi (66 KB) ↗\n12 TB Tanpa Otentikasi Agustus 2026: Kebocoran Aset (CWE-284)\nValve telah menyimpan 12 terabyte kode internal dan versi prototipe di titik akhir publik yang terbuka tanpa otentikasi selama beberapa minggu.\nValve Dokumen Ketidakmampuan (43 KB) ↗Arsip Bukti ↗\nInsiden Keamanan di CEVA Logistics Agustus 2026: Kebocoran Data Pribadi Pelanggan\nNama, alamat, dan nomor telepon para pembeli Steam Deck di Eropa bocor dari mitra logistik Valve, yang memicu gelombang serangan phishing.\nCatatan Insiden ↗Catatan Penegakan Hukum ↗\n\nArtefak pengambilan sampel: banned_100k_slice.csv (100,000 akun). Hasil audit: slice_100k_hasil_terbatas.csv. Laporan analitis lengkap: BANNED_100K_ANALISIS_FORENSIK.md.\n\n08 — Metode dan batasan\nBagaimana hal ini ditafsirkan, dan apa yang tidak diklaim di dalamnya\n\nTiga populasi umum, satu API publik, serta pengambilan sampel statistik yang ketat.\n\nPELAKSANAAN & KREDENSIAL\n\nSensus ASF, 100,000-akun SRSWOR potongan dan SteamRep pemeriksaan silang dilaksanakan oleh PhishDestroy peserta menggunakan Steam akun dan kunci API Web mereka sendiri, sebagai bagian dari upaya Koalisi dalam memberantas phishing dan penipuan. Penulis laporan ini tidak memiliki Steam kunci Web API dan tidak melakukan pemindaian langsung secara pribadi. Penggabungan data, penghashing, verifikasi, dan publikasi dilakukan berdasarkan hasil yang diserahkan oleh para peserta.\n\nPenduduk\tDari mana asalnya\tApa yang telah dibacakan\nAnggota ASF\n10,880,610\tDaftar anggota publik dari grup Komunitas ArchiSteamFarm Steam. Halaman grup Steam menampilkan 5,360,499 anggota (hanya yang tidak dibatasi); daftar anggota yang dihasilkan oleh API menampilkan total 10,880,610 entri, termasuk akun yang dibatasi. Grup ini secara otomatis diikuti saat pertama kali dijalankan, kecuali jika pengguna secara eksplisit menonaktifkan pengaturan default untuk bergabung dengan grup di konfigurasi (AutoJoinSteamGroup / Statistik), yang berarti daftar anggota tersebut mencakup kelompok bot komersial, pengguna individu yang hanya mengaktifkan kartu, dan pemain reguler yang membiarkan opsi bawaan tetap aktif.\tGetPlayerBans untuk setiap anggota (tanda larangan); GetPlayerSummaries untuk tanggal pembuatan dan negara. Dikumpulkan dalam kelompok berisi 100 ID, dan data duplikat telah disingkirkan berdasarkan SteamID64.\n100 ribu Akun yang Diblokir SRSWOR Bagian\n100,000\tSebuah sampel representatif yang diambil secara acak seragam tanpa penggantian dari kumpulan akun yang diblokir 1,182,811 ($P = 8,45\\%$). Koreksi Populasi Terbatas menghasilkan margin of error sebesar $\\pm 0,39\\%$ pada tingkat kepercayaan 99% ($Z = 2,576$).\tMonetisasi dan status akun terbatas (isLimitedAccount) diaudit melalui antarmuka profil XML versi lama milik Steam (?xml=1) melalui saluran proxy terdistribusi. Memastikan status pembayaran 63.06%.\nSteamRep penipu\n51,732\tMelakukan sensus 100% terhadap semua profil yang ditandai sebagai \"DIBLOKIR\" dalam basis data reputasi komunitas SteamRep (total 51,732 profil). Tidak dilakukan pengambilan sampel atau penyaringan sama sekali.\tISteamUser/GetPlayerBans/v1 untuk semua akun 51,732, disajikan dalam tabel silang berdasarkan status SteamRep. Hal ini menegaskan bahwa akun 67.77% bebas dari larangan apa pun terkait penipuan.\nApa yang diklaim\n\nHanya angka empiris dan perkiraan yang terbatasi secara statistik. Dalam populasi otomatisasi, 88.97% tidak dikenai pemblokiran; subset yang diblokir lebih banyak terjadi baru-baru ini (70% sejak 2020). Dalam audit empiris akun 100,000, 63.06% dari akun yang diblokir adalah akun berbayar (tidak dibatasi), dengan margin kesalahan yang terbukti secara matematis di bawah ±0.4%. Di antara 51,732 penipu yang telah dikonfirmasi, 67.77% tidak dikenai pemblokiran yang terkait dengan penipuan. Setiap angka dapat direproduksi dari Web API milik Valve sendiri.\n\nApa yang tidak diklaim\n\nLarangan Steam tidak dilengkapi kolom alasan, sehingga larangan di sini tidak dikaitkan dengan penyebab tertentu. Keanggotaan dalam grup bukanlah bukti bahwa suatu akun merupakan bot otomatis: karena ASF mengaktifkan fitur bergabung ke grup secara default kecuali jika dicabut secara manual, populasi di sana terdiri dari campuran antara akun-akun komersial yang dikelola oleh jaringan multi-akun dengan akun pribadi milik pemain biasa dan penggemar. Negara dilaporkan sendiri, dan pencantuman SteamRep merupakan keputusan komunitas, bukan putusan pengadilan. Tidak ada nama individu yang disebutkan.\n\nMengapa hal ini penting\n\nValve memiliki API yang sama, basis data sendiri di belakangnya, serta alasan pemblokiran yang tidak dapat dideteksi oleh pemindaian ini. Sistem ini mampu menjalankan kueri ini di seluruh ruang ID dalam hitungan detik. Pengukuran yang memungkinkan pihak luar memverifikasi klaim penegakan terhadap suatu nomor belum pernah dipublikasikan oleh pihak yang mampu menghasilkan data tersebut dengan akurasi penuh. Ini adalah perkiraan dari pihak luar, yang disajikan agar pertanyaan dapat diajukan dengan disertai angka.\n\nBaca selanjutnya: sistem ekonomi berbasis kartu yang dijalankan oleh kelompok ini → · mendukung akses dan pencurian → · dokumen lengkap →",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Seberapa besar jaringan akun di Steam? Kami menghitungnya sendiri."
          },
          {
            "level": 2,
            "id": null,
            "text": "Sepuluh juta akun, dan sembilan dari sepuluh di antaranya belum pernah digunakan"
          },
          {
            "level": 3,
            "id": null,
            "text": "ASF bergabung dengan grup ini khusus untuk Anda"
          },
          {
            "level": 3,
            "id": null,
            "text": "10,880,610 jumlah entri"
          },
          {
            "level": 3,
            "id": null,
            "text": "88.97% bersih"
          },
          {
            "level": 3,
            "id": null,
            "text": "Dari 10,880,610 akun, berapa banyak yang telah menyentuh angka Valve?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Berapa biaya yang telah dikeluarkan armada ini Valve agar dapat beroperasi"
          },
          {
            "level": 2,
            "id": null,
            "text": "Di mana armada itu berada"
          },
          {
            "level": 3,
            "id": null,
            "text": "Akun yang diblokir berdasarkan negara yang disebutkan"
          },
          {
            "level": 2,
            "id": null,
            "text": "Laporan terbaru, bukan tumpukan pekerjaan lama"
          },
          {
            "level": 3,
            "id": null,
            "text": "Saat akun-akun yang diblokir tersebut dibuat"
          },
          {
            "level": 2,
            "id": null,
            "text": "Ketika Valve berlaku, hal itu berlaku pada tahun pertama"
          },
          {
            "level": 3,
            "id": null,
            "text": "Berapa lama akun tersebut sudah ada saat pemblokiran diberlakukan"
          },
          {
            "level": 2,
            "id": null,
            "text": "Ketika Valve aktif, hal itu tidak menghentikan bot"
          },
          {
            "level": 3,
            "id": null,
            "text": "Alasan sebenarnya mengapa para 11% yang diblokir itu diblokir"
          },
          {
            "level": 2,
            "id": null,
            "text": "Para penipu Valve, mari kita lihat: Sensus Lengkap 51,732"
          },
          {
            "level": 3,
            "id": null,
            "text": "Penipu yang telah dikonfirmasi, berdasarkan apakah Valve telah menjatuhkan sanksi yang berkaitan dengan penipuan (Full Census)"
          },
          {
            "level": 4,
            "id": null,
            "text": "Dua populasi, satu temuan"
          },
          {
            "level": 2,
            "id": null,
            "text": "Audit empiris akun 100,000: botnet bukanlah akun gratis yang bisa dibuang begitu saja"
          },
          {
            "level": 3,
            "id": null,
            "text": "100,000 Irisan yang Tidak Memihak"
          },
          {
            "level": 3,
            "id": null,
            "text": "Margin Kesalahan < ±0.4%"
          },
          {
            "level": 3,
            "id": null,
            "text": "Mengapa Setiap 100 ribu Memberikan Hasil yang Sama"
          },
          {
            "level": 3,
            "id": null,
            "text": "100,000 Akun yang Diblokir: Berbayar ($5+ Pengeluaran di Toko) vs Status Gratis Terbatas"
          },
          {
            "level": 3,
            "id": null,
            "text": "Realitas Struktural: Penutupan Rekening dalam Skala Industri"
          },
          {
            "level": 2,
            "id": null,
            "text": "Bagaimana hal ini ditafsirkan, dan apa yang tidak diklaim di dalamnya"
          },
          {
            "level": 3,
            "id": null,
            "text": "Apa yang diklaim"
          },
          {
            "level": 3,
            "id": null,
            "text": "Apa yang tidak diklaim"
          },
          {
            "level": 3,
            "id": null,
            "text": "Mengapa hal ini penting"
          }
        ],
        "links": [
          "https://help.steampowered.com/en/faqs/view/71D3-35C2-AD96-AA3A",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/asf-ban-census-2026-09-23.json",
          "https://phishdestroy.io/steam_dossier/id/VALVE_EVIDENCE_PACK/databases/steamrep_steam_bans.csv",
          "https://phishdestroy.io/live-intel/?category=steam",
          "https://phishdestroy.io/steam_dossier/id/card_economy.html",
          "https://phishdestroy.io/steam_dossier/id/VALVE_EVIDENCE_PACK/databases/banned_archiasf_massive.csv",
          "https://phishdestroy.io/steam_dossier/id/VALVE_EVIDENCE_PACK/databases/slice_100k_limited_results.csv",
          "https://phishdestroy.io/steam_dossier/id/VALVE_EVIDENCE_PACK/reports/BANNED_100K_FORENSIC_ANALYSIS.md",
          "https://phishdestroy.io/steam_dossier/id/VALVE_EVIDENCE_PACK/databases/banned_100k_slice.csv",
          "https://phishdestroy.io/steam_dossier/id/VALVE_EVIDENCE_PACK/reports/STEAM_BANNED_LIMIT_ANALYSIS.md",
          "https://phishdestroy.io/steam_dossier/id/VALVE_EVIDENCE_PACK/INVESTIGATION_OVERVIEW.md",
          "https://phishdestroy.io/steam_dossier/id/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/id/VALVE_EVIDENCE_PACK/reports/STEAMREP_VS_STEAM_AUDIT.md",
          "https://phishdestroy.io/steam_dossier/id/VALVE_EVIDENCE_PACK/databases/SteamRep_Profiles_BannedCaution_2024.csv",
          "https://phishdestroy.io/steam_dossier/id/security_timeline.html",
          "https://phishdestroy.io/steam_dossier/id/VALVE_EVIDENCE_PACK/reports/russian_conflicts_report.json",
          "https://phishdestroy.io/steam_dossier/id/VALVE_EVIDENCE_PACK/reports/classification_report.json",
          "https://phishdestroy.io/steam_dossier/id/VALVE_EVIDENCE_PACK/reports/VALVE_INCOMPETENCE_REPORT.md",
          "https://phishdestroy.io/steam_dossier/id/steam_evidence_archive.html",
          "https://phishdestroy.io/steam_dossier/id/steam_enforcement_evidence.html",
          "https://phishdestroy.io/steam_dossier/id/#insider-threat",
          "https://phishdestroy.io/steam_dossier/id/"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/id/enforcement_audit.content.json",
      "export_json_sha256": "b8b5ce904b6da21c9d234828f9f76b542ad18cedaa70536c525a42b16380efd5"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "id/index.html",
      "language": "id",
      "title": "Dossier Steam: aturan, rute, dan pertanggungjawaban",
      "source_url": "https://phishdestroy.io/steam_dossier/id/index",
      "source_html_sha256": "2217f6c56dcbeab96133a0472ca63e5c64abb7af6b0aefce31f204ea261aec56",
      "exported_at": "2026-09-29T00:22:31.002Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "exhibit-gallery-section",
            "source": "https://phishdestroy.io/steam_dossier/id/index#exhibit-gallery-section"
          }
        ],
        "raster_images_replaced": 2
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "index.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/id/index.pdf?v=print-20260929-v5",
        "sha256": "e9330d68ffd257fb8e3d0a73ad90d977f7cfff4ca4e2d3b325c80d3ace4274de",
        "bytes": 976449,
        "pages": 109
      },
      "integrity": {
        "signed_object": "index.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "index.content.json.asc",
        "digest_file": "index.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify index.content.json.asc index.content.json",
          "sha256sum -c index.content.json.sha256"
        ]
      },
      "content": {
        "text": "Bagian 1 — Ringkasan Perkara\nAturan. Rekor. Pertanyaan-pertanyaan yang belum terjawab.\nKonteks & batasan sumber\n\nEnam temuan, masing-masing terkait dengan catatan publik yang tercantum tanggalnya. Bagian-bagian terperinci tersebut disusun dalam urutan yang sama: catatan teknis (Bagian A), catatan peraturan dan penegakan hukum (Bagian B), kerangka hukum (Bagian C), kemudian lampiran yang berisi bukti-bukti utama.\n\nEnam temuan. Masing-masing mengaitkan suatu aturan tertulis dengan catatan bertanggal serta suatu pertanyaan yang dapat diuji berdasarkan bukti tersebut.\n\n1. Host otentikasi dengan domain terpisah — 44 rute · 26 pasangan terpisah\n\nCatatan daftar penerima bantuan 44 platform yang melakukan otentikasi melalui domain terdaftar tersendiri. Lima rute lainnya masih dalam proses verifikasi dan menunggu penetapan tanggal RDAP; jika rute-rute tersebut disetujui, jumlah totalnya akan menjadi 47. Rute-rute tersebut tidak termasuk dalam angka 44 maupun dalam tabel usia. — 27 dengan berkas bukti per rute yang telah dipublikasikan dan 17 yang ditambahkan dari pengumpulan manual, dicantumkan secara terpisah. Dalam 26 pasang filter-split domain utamanya adalah DIBLOKIR di Filter Tautan Steam, sedangkan proxy yang menggunakan informasi login tersebut tidak diblokir. Domain-domain ini bukanlah domain sekali pakai: csgogem.com diblokir, sedangkan api.csgem.com, server yang menggunakan nama pengguna Steam, telah terdaftar sejak Maret 2014 — 12 tahun 6 bulan. Valve menerima nama host tersebut dalam setiap permintaan OpenID, dan menampilkannya kembali kepada pengguna di halaman masuknya sendiri. Tabel lengkap, usia per rute, dan sumbernya terdapat di Bagian 3.\n\nIkuti rute ini →\n2. 2016: mekanisme tersebut diberi nama, batas waktu ditetapkan\n\nPada tanggal 13 Juli 2016, Valve secara terbuka menjelaskan bagaimana situs perjudian menggunakan Steam OpenID dan akun perdagangan otomatis, dan pemberitahuan dari penasihat hukumnya tertanggal 20 Juli 2016 menetapkan batas waktu sepuluh hari. Sejak saat itu, belum ada catatan penegakan hukum per operator yang dipublikasikan. Sepuluh tahun setelah batas waktu tersebut ditetapkan, mekanisme dengan nama yang sama masih digunakan pada host otentikasi dengan domain terpisah yang tidak menghasilkan pemblokiran Link Filter pada 2026-09-21.\n\nBaca surat terbuka untuk WSGC →\n3. Korelasi perangkat, di atas kertas surat berkop firma pengacara\n\nDalam korespondensi yang disajikan di sini, penasihat hukum Valve menjelaskan korelasi pada tingkat perangkat yang menghubungkan satu perangkat dengan beberapa akun — suatu kemampuan yang sebelumnya telah disampaikan oleh Tim Dukungan Steam kepada para pengguna bahwa hal tersebut secara teknis tidak mungkin dilakukan. Pertanyaan yang masih belum terjawab adalah catatan tingkat perangkat apa saja yang dimiliki oleh Valve dan atas dasar apa pemegang akun ditolak aksesnya ke catatan tersebut.\n\nBaca memorandum tersebut →\n4. Ada dua tanggapan terkait akses. Satu menahan data tersebut, satu lagi membocorkannya.\n\nOktober 2025: Pengacara Valve menanggapi permohonan berdasarkan Pasal 15 dengan lampiran setebal 830 halaman yang bagian-bagian yang disensornya ditutupi dengan cat di atas teks alih-alih dihapus — 902,270 karakter mengungkap kembali data tersebut dengan alat ekstraksi standar, termasuk pengenal pihak ketiga yang semula disembunyikan oleh batasan-batasan tersebut. Pasal 15 ayat (4) adalah alasan di balik keberadaan batasan-batasan tersebut. September 2026: Tiket HT-2YBP-F7JP-D4VB ditutup setelah tiga hari dengan tautan ke halaman Data Akun layanan mandiri — tanpa data, tanpa dasar hukum yang disebutkan. Jangka waktu satu bulan sesuai Pasal 12(3) belum berakhir pada saat publikasi; keberatan ini diajukan atas substansi keputusan tersebut.\n\nBaca pemeriksaan penyuntingan →Baca catatan tiket →\n5. Pasar berada di atas batas atas Steam\n\nSteam membatasi harga penawaran di pasar pada sekitar $1,800. Di lima pasar berdasarkan data pada tanggal tertentu (23 September 2026), 248 kategori barang CS2 harganya melebihi batas tersebut oleh dua atau lebih di antaranya secara terpisah, dan keseluruhan 248 orang tidak hadir dari Steam; harga Dragon Lore baru dari pabrik mulai dari $10,941 di 389 salinan yang terdaftar di kelima platform tersebut (angka khusus CSFloat pada Bagian 13, berdasarkan snapshot tanggal 20 September, adalah $10,623.95 di 62 penawaran). Penjualan pada harga-harga tersebut memerlukan platform eksternal, sementara transfer item masih berjalan melalui Steam.\n\nIkuti perkembangan harga dan transfer →\n6. Aturannya jelas; jejak auditnya tidak\n\nPerjanjian Pelanggan menetapkan Steam untuk penggunaan pribadi dan non-komersial, melarang eksploitasi komersial kecuali jika secara tegas diizinkan, melarang penggunaan skrip dan bot, serta mengizinkan penutupan akun. Valve menerapkan ketentuan tersebut kepada operator perjudian pada tahun 2016. Secara terpisah, menurut akun teknik CSFloat, Valve ditutup IEconItems_730/GetPlayerItems Pada tahun 2017, akses publik terhadap ID item asli dihentikan (tidak ditemukan catatan perubahan Valve).\n\nLetakkan aturan tersebut di samping jaringan →\n2016 / Permintaan tertulis 10 hari\nBatas waktu yang tercantum dalam pemberitahuan yang dikeluarkan oleh penasihat hukum pada Juli 2016 kepada situs-situs perjudian. Surat terbuka kepada WSGC: Bagian 2.\n2017 / Jejak audit publik Akses ID ditutup\nCSFloat mencatat hilangnya ID item asli.\nKorespondensi penasihat hukum Korelasi perangkat\nSatu perangkat terkait dengan puluhan akun yang dicuri.\nDaftar rute Terblokir, tapi masih bisa masuk\nAturannya: Pernyataan Valve tahun 2016 melarang pengoperasian usaha perjudian di Steam OpenID. Catatan: Ada 26 domain utama yang terdaftar di Link Filter, sementara server yang menjalankan login Steam masing-masing domain tersebut telah beroperasi selama — server csgogem.com telah beroperasi selama 12 tahun 6 bulan.\nBagian 2 — Surat terbuka\nSurat Terbuka kepada Komisi Perjudian Negara Bagian Washington\n\nSepuluh hari berubah menjadi sepuluh tahun. Pertanyaan yang diajukan Komisi pada tahun 2016 kepada Valve belum dijawab dengan data terperinci per operator; surat ini meminta Komisi untuk membuka kembali kasus tersebut.\n\nPENGUMUMAN UMUM · KOMISI PERJUDIAN NEGARA BAGIAN WASHINGTON\n\nSepuluh hari berubah menjadi sepuluh tahun.Buka kembali catatan tersebut.\n\nKepada Komisi Perjudian Negara Bagian Washington:\n\nPada tahun 2016, Direktur David Trujillo meminta Valve untuk menunjukkan langkah-langkah yang telah diambil guna menghentikan penggunaan skin Steam untuk perjudian. Ketua saat itu, Chris Stearns, dan Komisi berhadapan dengan industri yang dibangun di atas barang-barang yang diterbitkan oleh Valve dan transfer Steam. Keduanya kini telah meninggalkan jabatan mereka di Komisi. Pertanyaan yang mereka ajukan kepada Valve belum kedaluwarsa.\n\nPenasihat Hukum Valve, Karl Quackenbush, memberi waktu sepuluh hari kepada operator perjudian untuk menghentikan penggunaan komersial akun-akun Steam. Dalam tanggapannya pada bulan Oktober kepada Komisi Anda, Valve membantah telah memfasilitasi perjudian, menyatakan telah mengirimkan surat peringatan untuk menghentikan kegiatan tersebut kepada lebih dari empat puluh situs, dan menyatakan telah menonaktifkan akun-akun yang terkait. Perusahaan tersebut juga membela keputusannya untuk mempertahankan layanan perdagangan Steam dan OpenID karena layanan-layanan tersebut bermanfaat bagi pelanggan dan pengembang game. Itu merupakan upaya untuk menunjukkan kekuasaan. Hal itu layak diuji, bukan hanya diterima begitu saja.\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\nMenurut penilaian kami, jawaban Valve tidak menunjukkan bahwa tindakan penegakan yang dipilihnya sesuai dengan skala jaringan yang dijelaskannya. Surat ancaman kepada seorang operator tidak sama dengan pemblokiran permanen terhadap akun-akun Steam, infrastruktur perdagangan, dan jalur otentikasi yang menjadi landasan berjalannya bisnis tersebut. Perkiraan yang dilaporkan menyebutkan bahwa CS:GO Lounge sendiri mencatatkan volume taruhan lebih dari $1 miliar pada tahun 2016; itu adalah perkiraan dari pihak luar mengenai jumlah taruhan, bukan pendapatan Valve, dan operasi taruhan berbasis kulit yang semula dijalankan situs tersebut kemudian ditutup. Skala tersebut membuat penegakan hukum yang dapat diverifikasi menjadi sangat penting.\n\nHari ini, milik Valve sendiri Perjanjian Pelanggan diarsipkan 2026-09-21 ↗ membatasi eksploitasi komersial kecuali jika secara tegas diizinkan, serta secara terpisah melarang bentuk-bentuk otomatisasi tertentu. Kami daftar rute yang sudah kedaluwarsa catatan yang dinyatakan sebagai OpenID mengembalikan host untuk layanan eksternal; openid.realm dan openid.return_to adalah bidang-bidang yang dikirimkan ke Steam, bukan rahasia yang disembunyikan darinya. Kami Pemeriksaan Filter Tautan menunjukkan kasus-kasus di mana alamat utama telah diberi peringatan, tetapi host login yang terkait tidak. Hasil penyaringan saja tidak dapat membuktikan bahwa Valve mengizinkan proses login atau bahwa bot tertentu berhasil menghindari pemblokiran akun. Hal ini memang membuktikan bahwa peringatan di laman beranda tidak dapat dijadikan jawaban yang lengkap mengenai akses.\n\nKeberadaan fungsi perdagangan dan OpenID yang bermanfaat serta sah Steam juga tidak dapat menjawab apakah operator yang dilarang benar-benar telah dikecualikan. Aturan Valve sendiri memperbolehkan pengecualian secara tegas. Jika Valve mengandalkan perbedaan tersebut, Komisi harus memintanya untuk mengidentifikasi izin, kontrol akun, dan kriteria penegakan yang berlaku bagi bisnis skin komersial, serta penggunaan non-perjudian spesifik yang diajukannya pada tahun 2016. Kemungkinan penggunaan yang sah semata-mata bukanlah jawaban atas penggunaan terlarang yang telah didokumentasikan.\n\nKami meminta Komisi untuk meninjau kembali berkas tahun 2016 dan meminta laporan terperinci per operator: akun Steam dan bot perdagangan mana saja yang dinonaktifkan setelah pemberitahuan sepuluh hari; apakah akun terkait atau server pengembalian dipantau; operator mana saja yang kemudian mendapatkan kembali aksesnya; pengecualian apa saja yang diberikan; dan catatan apa yang mendukung pernyataan Valve kepada Komisi. Publikasikan apa yang diizinkan oleh undang-undang untuk diperiksa oleh publik. Bandingkan catatan tersebut dengan rute saat ini dan dengan intervensi Valve selanjutnya, termasuk OPSkins pada tahun 2018 diarsipkan 2026-03-07 ↗.\n\nPemberitahuan tersebut menetapkan batas waktu sepuluh hari pada bulan Juli 2016; sepuluh tahun sudah cukup lama untuk menentukan apakah hal tersebut telah dilaksanakan. Komisi sebaiknya membandingkan laporan keuangan Valve tahun 2016 dengan infrastruktur yang masih dapat diamati hingga saat ini.\n\nPenyelidikan Dossier Steam · Pernyataan Publik, 20 September 2026\n\nPengumuman Komisi Tahun 2016 ↗ diarsipkan 2026-05-20 ↗ · Tanggapan Valve tahun 2016 (salinan dokumen) ↗ · Pernyataan OpenID Valve tahun 2016 ↗ diarsipkan 2026-09-21 ↗ · Perjanjian saat ini Steam ↗ diarsipkan 2026-09-21 ↗ · Kronologi pertukaran tahun 2016: Bagian 11 →\n\nBagian A — Catatan teknis · Bagian 3\nSitus tersebut diblokir. Namun, rute masuknya tidak diblokir.\n\n26 domain utama yang diblokir. Proksi otentikasi yang ada di balik masing-masing domain tersebut, serta berapa lama proksi tersebut telah beroperasi. Host otentikasi terpisah ini bukanlah alamat sekunder yang bersifat insidental — masing-masing merupakan sebuah proksi otentikasi untuk Steam, yang berada di antara platform dan titik akhir OpenID milik Valve serta menangani proses masuk yang tidak lagi dapat dilakukan secara terbuka oleh domain yang diblokir. Valve menempatkan pintu masuk utama pada Link Filter. Proses masuk tetap berjalan melalui proxy: csgogem.com diblokir, dan api.csgem.com telah terdaftar sejak Maret 2014 — dua belas setengah tahun. Setiap hari, server tersebut mengirimkan nama hostnya sendiri ke titik akhir OpenID milik Valve, dan Steam langsung menampilkannya kembali kepada pengguna di halaman masuk. Valve adalah jalur utama yang dilalui oleh setiap rute ini; jalur tersebut tidak perlu mencari rute-rute tersebut. Itulah yang diukur dalam bagian ini: bukan apakah ada peringatan, melainkan berapa tahun rute di belakang peringatan tersebut tetap terbuka. Terdapat 44 rute dengan domain terpisah dalam daftar, 27 di antaranya dilengkapi dengan berkas bukti per rute yang telah dipublikasikan — lihat tabel di bawah ini. Perhatikan satu contoh, lalu ukur semuanya.\n\nGambar 3.1 — Kedua rute tersebut, digambarkan.\n\nSatu platform, satu pengguna, dua permintaan yang dikirim dari browser yang sama. Fitur Link Filter milik Valve berfungsi pada keduanya. Fitur ini memblokir permintaan yang berisi tautan dan membiarkan permintaan yang berisi data login. Semua data yang diukur dalam bagian ini menunjukkan berapa lama rute bawah tetap terbuka.\n\nThe player\none browser, one session\nrollbit.com\nthe platform's main domain\nrbsnin.com\nseparate authentication host\nLINK FILTER\n✕ BLOCKED\nLINK FILTER\n✓ CLEAN\nsteamcommunity.com\nOpenID endpoint · signs in\nno route\nTautan diposting pada Steam — dihentikanPermintaan masuk — disetujuiCek yang disimpan tertanggal 19 dan 21 September 2026\n\nKedua permintaan tersebut terlihat oleh Valve, dan hanya satu yang ditindaklanjuti. Filter Tautan adalah daftar Valve, yang diperiksa oleh layanan Valve. Permintaan OpenID membawa nama host otentikasi itu sendiri ke titik akhir Valve, yang langsung menampilkannya kembali di halaman login. Nama host tersebut tetap ada dalam permintaan — perbedaannya terletak pada apakah ada tindakan yang dilakukan terhadapnya atau tidak.\n\nSatu platform. Dua rute yang berbeda.ROLLBIT / CATATAN YANG TELAH DISIMPAN\nLangkah 5 / 5\n\nPermintaan tersebut mencapai Steam. Rute yang teramati mengarah ke formulir login Steam. Para penulis tidak menyelesaikan proses login tersebut. Memblokir tautan domain utama tidak menghalangi rute yang teramati ini menuju formulir tersebut.\n\n01 PEMERIKSAAN FILTER LINK\nTUJUANrollbit.comDomain utama platform tersebut\nFILTER STEAM LINKMemeriksa tautan tersebutSistem peringatan tujuan yang terpisah\nHASIL YANG DISIMPANTautan diblokir19 dan 21 September 2026\n02 RUTE MASUK YANG TERAMATI\nDI PERONMasuk dengan SteamPlatform tersebut memulai permintaan OpenID\nHOST OTENTIKASI TERPISAHrbsnin.comTidak ada blok Filter Tautan dalam pemeriksaan yang disimpan\nSTEAMFormulir masuk telah ditampilkanHost yang diminta tercantum dalam pemberitahuan Steam\nPeriksa catatan pengambilan sampel asli, tanggal pendaftaran, dan rincian protokol\nSeperti apa penegakan Valve itu\nDomain utama: diblokir\nPengguna\n→\nrollbit.com\n(domain utama)\n↓\nFILTER STEAM LINK — TERBLOKIR\n\"Tautan Diblokir!\" — ditandai sebagai tautan yang berpotensi berbahaya\nrollbit.com menampilkan pemblokiran Filter Tautan pada 2026-09-19 dan 2026-09-21 (pemeriksaan tanpa otentikasi; HTML mentah dan SHA-256 disimpan). Catatan yang terlihat dan dapat diaudit.\nApa yang sebenarnya terjadi — otentikasi\nHost otentikasi: tidak diblokir\nPengguna\n→\nrollbit.com\n\"Masuk dengan Steam\"\n↓\nPengalihan melalui host otentikasi terpisah:\nrbsnin.comFilter Tautan: BERSIH\nterdaftar 2026-09-18T09:34:52Z (Verisign RDAP)\n↓\nSteam pemberitahuan di halaman masuk (2026-09-20):\n\"Note that rbsnin.com is not affiliated with Steam or Valve\"\nSteam menampilkan pemberitahuan ini dari openid.realm pada permintaan yang diterimanya.\n↓\nSteam formulir login yang disajikan untuk host terpisah\nProses masuk tidak diselesaikan oleh para penulis; alurnya diamati hingga formulir Steam.\nValve menerima nama host return_to / realm pada setiap permintaan semacam itu. rbsnin.com tidak mengembalikan pemblokiran Link Filter pada 2026-09-21.\nSesuai permintaan\nSebagai penyedia OpenID, Steam menerima nama host otentikasi pada setiap permintaan otentikasi: nama host tersebut tiba di server milik Valve di openid.return_to dan openid.realm parameter.\nDikirim oleh situs ini\nHost otentikasi tidak terdeteksi melalui pemindaian — platform mengirimkannya ke Steam dalam setiap permintaan. Berdasarkan OpenID 2.0 §9.1 return_to secara resmi bersifat opsional, tetapi tanpa itu Steam tidak dapat menampilkan hasil login, sehingga untuk proses login Steam yang berfungsi, hal itu pada dasarnya wajib. Steam bahkan menampilkan nama host kepada pengguna (\"<host> tidak berafiliasi dengan Steam atau Valve\").\n14 tahun\nadalah usia host otentikasi tertua yang masih memiliki Steam sesi login pada pemeriksaan ke-2026-09-21 (dota2.net, terdaftar pada 2011-10-29); sedangkan yang termuda berusia tiga hari (rbsnin.com). Jangan mengartikan angka \"0 host otentikasi diblokir\" sebagai kesimpulan. Host otentikasi yang diblokir akan langsung membuat fitur \"Masuk dengan Steam\" pada platform ini tidak berfungsi, sehingga daftar yang disusun berdasarkan login yang berhasil hanya dapat berisi host yang tidak pernah diblokir. Angka yang memiliki arti bukanlah jumlah pemblokiran — melainkan berapa tahun domain utama berada di Filter Tautan sementara proses masuk di sebelahnya tetap berjalan.\nHost otentikasi dengan domain terpisah: tanggal pendaftaran vs. domain utama (30 rute: 25 di antaranya berhasil diidentifikasi dalam audit browser 2026-09-21, ditambah 5 yang ditambahkan pada 2026-09-22)\nPlatform\tFilter Tautan: utama\tHost otentikasi\tFilter Tautan: host otentikasi\tHost otentikasi telah terdaftar\tSumber pengamatan\tBerkas bukti\nRollbit\nrollbit.com · reg. 2014-11-08\n\tDIBLOKIR\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\trbsnin.com\tBERSIH\n2026-09-21 · HTML mentah (tidak ada cuplikan Wayback)\n\t2026-09-18\n09:34:52Z, Verisign RDAP\n\tSteam pemberitahuan halaman masuk, 2026-09-20\trollbit.com.json\nSkin.Club\nskin.club · reg. 2017-09-04\n\tDIBLOKIR\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\tsc-auth.net\tBERSIH\n2026-09-21 · Wayback 2026-09-21\n\t2019-04-02\nRDAP\n\tSteam pemberitahuan halaman login\tskin.club.json\nHowl.GG\nhowl.gg · daftar 2017-03-16\n\tDIBLOKIR\n2026-09-18, 19 September, 21 September · Wayback 2026-09-21\n\thowl.uno\tBERSIH\n2026-09-21 · Wayback 2026-09-21\n\t2026-08-11\nRDAP\n\tPerekaman layar browser secara langsung + URL OpenID yang disediakan\thowl.gg.json\nDuelbits\nduelbits.com · terdaftar 2020-02-03\n\tDIBLOKIR\n2026-09-21 · Wayback 2026-09-21\n\tswitchflips.com\tBERSIH\n2026-09-21 · Wayback 2026-09-21\n\t2020-04-21\nRDAP\n\tURL OpenID yang disediakan\tduelbits.com.json\nCSGOFast\ncsgofast.com · terdaftar 2015-03-27\n\tDIBLOKIR\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\tsteam-login.authtofast.com\tBERSIH\nauthtofast.com, 2026-09-21 · Wayback 2026-09-21\n\t2026-06-30\nauthtofast.com, RDAP\n\tPerekaman layar browser secara langsung + URL OpenID yang disediakan\tcsgofast.com.json\nKulit Hewan Ternak\nfarmskins.com · reg. 2016-03-23\n\tDIBLOKIR\n2026-09-19, 2026-09-21 · HTML mentah\n\tsteam.kobal.cc\tBERSIH\n2026-09-19, 2026-09-21 · HTML mentah\n\t2017-01-07\nkobal.cc, RDAP\n\tPerekaman layar browser secara langsung + URL OpenID yang disediakan\tfarmskins.com.json\nCobaltLab\ncobaltlab.tech\n\tDIBLOKIR\n2026-09-21 · HTML mentah\n\tcobaltauth.com\tBERSIH\n2026-09-21 · HTML mentah\n\t2025-01-07\nRDAP\n\tURL OpenID yang disediakan\tcobaltlab.tech.json\nCSGO.NET\ncsgo.net · terdaftar 2012-07-22\n\tDIBLOKIR\n2026-09-21 · HTML mentah\n\tcn2.easylot.net\tBERSIH\n2026-09-21 · HTML mentah\n\t2016-09-03\neasylot.net, RDAP\n\tPerekaman layar secara langsung melalui browser\tcsgo.net.json\nGGDrop\nggdrop.com\n\tDIBLOKIR\n2026-09-21 · HTML mentah\n\tggauth.com\tBERSIH\n2026-09-21 · HTML mentah\n\t2023-05-03\nRDAP\n\tURL OpenID yang disediakan\tggdrop.com.json\nRustChance\nrustchance.com\n\tDIBLOKIR\n2026-09-21 · HTML mentah\n\thgfuihd.com\tBERSIH\n2026-09-21 · HTML mentah\n\t2019-01-27\nRDAP\n\tURL OpenID yang disediakan\trustchance.com.json\nSkin.Fans\nskin.fans\n\tDIBLOKIR\n2026-09-21 · HTML mentah\n\tauth.skinfans.com\tBERSIH\n2026-09-21 · HTML mentah\n\t2018-07-16\nskinfans.com, RDAP\n\tURL OpenID yang disediakan\tskin.fans.json\nSkinport\nskinport.com · reg. 2018-09-05\n\tDIBLOKIR\n2026-09-21 · HTML mentah\n\tskinport.app\tBERSIH\n2026-09-21 · HTML mentah\n\t2020-06-20\nRDAP\n\tPerekaman layar browser secara langsung + URL OpenID yang disediakan\tskinport.com.json\nSkins.Cash\nskins.cash\n\tDIBLOKIR\n2026-09-21 · HTML mentah\n\tskinscash.live\tBERSIH\n2026-09-21 · HTML mentah\n\t2019-12-05\nRDAP\n\tURL OpenID yang disediakan\tskins.cash.json\nTF2Hunt\ntf2hunt.com · terdaftar 2018-01-13\n\tDIBLOKIR\n2026-09-21 · HTML mentah\n\trstspcl.com\tBERSIH\n2026-09-21 · HTML mentah\n\t2020-08-08\nRDAP\n\tPerekaman layar browser secara langsung + URL OpenID yang disediakan\ttf2hunt.com.json\nCSGOGem\ncsgogem.com · terdaftar 2016-10-16\n\tDIBLOKIR\n2026-09-22 · HTML mentah\n\tapi.csgem.com\ncsgem.com — domain terpisah yang dapat didaftarkan\n\tBERSIH\n2026-09-22 · HTML mentah\n\t2014-03-08\ncsgem.com, RDAP — yang paling lama terdaftar\n\tPengumpulan manual + Penangkapan melalui Filter Tautan\tlinkfilter-2026-09-22.json\nGamdom\ngamdom.com · terdaftar 2016-07-29\n\tDIBLOKIR\n2026-09-22 · HTML mentah\n\tlogin.gambldom.com\ngambldom.com — hanya berbeda satu huruf dari merek tersebut\n\tBERSIH\n2026-09-22 · HTML mentah\n\t2017-09-24\ngambldom.com, RDAP\n\tPengumpulan manual + Penangkapan melalui Filter Tautan\tlinkfilter-2026-09-22.json\n12CS\n12cs.fail · reg. 2026-03-24\n\tDIBLOKIR\n2026-09-22 · HTML mentah\n\tfail.games\tBERSIH\n2026-09-22 · HTML mentah\n\t2021-08-24\nfail.games, RDAP\n\tPengumpulan manual + Penangkapan melalui Filter Tautan\tlinkfilter-2026-09-22.json\nCSGOEmpire\ncsgoempire.com · terdaftar 2015-06-10\n\tBERSIH\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\tcsgoempirelogin4.com\nsalah satu dari sepuluh domain bernomor login1–10\n\tBERSIH\n2026-09-21 · Wayback 2026-09-21\n\t2020-07-20\n05:49:17Z, Verisign RDAP\n\tPerekaman layar browser secara langsung\tcsgoempire.com.json\nCS.MONEY\ncs.money\n\tBERSIH\n2026-09-21 · HTML mentah\n\tauth.dota.trade\tBERSIH\n2026-09-21 · HTML mentah\n\t2016-07-15\ndota.trade, RDAP\n\tSteam pemberitahuan halaman login\tcs.money.json\nCSFloat\ncsfloat.com · reg. 2021-07-11\n\tBERSIH\n2026-09-21 · HTML mentah\n\tcsgofloat.com\ndomain merek lama operator; domain terpisah yang dapat didaftarkan, bukan indikator upaya pengelakan\n\tBERSIH\n2026-09-21 · HTML mentah\n\t2015-09-29\nRDAP\n\tPerekaman layar secara langsung melalui browser\tcsfloat.com.json\nG4Skins\ng4skins.com\n\tBERSIH\n2026-09-21 · HTML mentah\n\tauth.g4s.to\tBERSIH\n2026-09-21 · HTML mentah\n\t2021-05-30\ng4s.to, RDAP\n\tURL OpenID yang disediakan\tg4skins.com.json\nJuice.GG\njuice.gg\n\tBERSIH\n2026-09-21 · HTML mentah\n\tletmeinjuice.com\tBERSIH\n2026-09-21 · HTML mentah\n\t2024-04-15\nRDAP\n\tURL OpenID yang disediakan\tjuice.gg.json\nMarket.CSGO\nmarket.csgo.com\n\tBERSIH\n2026-09-21 · HTML mentah\n\tdota2.net\tBERSIH\n2026-09-21 · HTML mentah\n\t2011-10-29\nRDAP\n\tPerekaman layar browser secara langsung + URL OpenID yang disediakan\tmarket.csgo.com.json\nRust.TM\nrust.tm\n\tBERSIH\n2026-09-21 · HTML mentah\n\tdota2.net\tBERSIH\n2026-09-21 · HTML mentah\n\t2011-10-29\nRDAP\n\tURL OpenID yang disediakan\trust.tm.json\nCSGOLounge\ncsgolounge.com · reg. 2013-08-14\n\tBERSIH\n2026-09-22 · HTML mentah\n\tdota2.net\nfront-end ketiga di host otentikasi ini\n\tBERSIH\n2026-09-22 · HTML mentah\n\t2011-10-29\ndota2.net, RDAP\n\tPengumpulan manual + Penangkapan melalui Filter Tautan\tlinkfilter-2026-09-22.json\nDota2Lounge\ndota2lounge.com · terdaftar 2012-08-10\n\tBERSIH\n2026-09-22 · HTML mentah\n\tdota2.net\nfront-end keempat di host otentikasi ini\n\tBERSIH\n2026-09-22 · HTML mentah\n\t2011-10-29\ndota2.net, RDAP\n\tPengumpulan manual + Penangkapan melalui Filter Tautan\tlinkfilter-2026-09-22.json\nSkinBaron\nskinbaron.de\n\tBERSIH\n2026-09-21 · HTML mentah\n\tskinbaron.com\nmerek yang sama, TLD yang berbeda\n\tBERSIH\n2026-09-21 · HTML mentah\n\t2015-12-22\nRDAP\n\tURL OpenID yang disediakan\tskinbaron.de.json\nTF2Royal\ntf2royal.com · terdaftar 2022-08-17\n\tBERSIH\n2026-09-21 · HTML mentah\n\ttf2auth.com\tBERSIH\n2026-09-21 · HTML mentah\n\t2021-07-27\nRDAP\n\tPerekaman layar browser secara langsung + URL OpenID yang disediakan\ttf2royal.com.json\nTradeit\ntradeit.gg\n\tBERSIH\n2026-09-21 · HTML mentah\n\tconnect-tradeit.com\tBERSIH\n2026-09-21 · HTML mentah\n\t2022-02-23\nRDAP\n\tURL OpenID yang disediakan\ttradeit.gg.json\nPeningkat\nupgrader.pro\n\tBERSIH\n2026-09-21 · HTML mentah\n\tupgauth.space\tBERSIH\n2026-09-21 · HTML mentah\n\t2026-08-14\nRDAP\n\tURL OpenID yang disediakan\tupgrader.pro.json\nSumber: steamcommunity.com/linkfilter, permintaan GET tanpa otentikasi, 2026-09-21, 53 host, selang waktu 3 detik; steam_tos_assets/linkfilter-recheck-2026-09-21.json; kode HTML mentah dalam steam_tos_assets/linkfilter-raw/. Tanggal pendaftaran: RDAP, steam_tos_assets/pendaftaran-domain.json. · Pemeriksaan sebelumnya terhadap 2026-09-19 di linkfilter-all-results.json · catatan rute di auth-route-audit.json · Tangkapan layar Wayback Machine dari halaman Link Filter, 2026-09-21, yang tercantum dalam wayback-snapshots.json (tidak ada snapshot untuk rbsnin.com; berkas mentah lokal adalah satu-satunya catatan).\n\nTanggal pendaftaran: RDAP (steam_tos_assets/domain-registry/). \"URL OpenID yang disediakan\" hanya menentukan parameter permintaan, bukan proses login yang telah selesai. Para penulis tidak menyelesaikan proses login apa pun di platform mana pun. Domain terpisah tidak dengan sendirinya menjadi bukti penghindaran. Demikian pula, \"0 host otentikasi diblokir\" bukanlah temuan independen: memblokir satu host akan mengganggu proses login Steam platform tersebut, sehingga daftar yang disusun dari proses login yang berfungsi tidak dapat berisi host otentikasi yang diblokir. Pengamatan yang memiliki bobot adalah pasangan tersebut dan durasinya — domain utama pada Filter Tautan di samping domain login yang telah berjalan selama bertahun-tahun. Tabel ini berisi 30 baris: 25 dari 27 rute dengan file bukti per rute, ditambah lima yang ditambahkan pada 2026-09-22 yang pembagian Filter Tautannya tercatat dalam linkfilter-2026-09-22.json meskipun data tersebut dikumpulkan secara manual — hal itu tercantum pada kolom sumber. Dua rute berkas bukti yang tidak ditampilkan adalah skinsnipe.com (host otentikasi pricing.tradeupspy.com, terdaftar 2020-03-11) dan csgobig.com (host otorisasi letmeinbig.com, terdaftar 2023-01-20); keduanya mengembalikan hasil \"BLOCKED main / CLEAN auth host\" pada pemeriksaan 2026-09-22, yang dicatat dengan SHA-256 di linkfilter-2026-09-22c.json, namun kode HTML mentah untuk batch tersebut tidak termasuk dalam kumpulan yang telah dipublikasikan, sehingga rute-rute tersebut disebutkan namanya di sini alih-alih diberi baris tersendiri—sebagaimana dapat dilihat pada setiap baris lainnya dalam tabel ini. 12 rute lainnya yang dikumpulkan secara manual dalam daftar tersebut diidentifikasi sebagai berikut dalam master_registry.json di bawah realm_src: user.\n\nAudit Empiris Primer · Rentang Tanggal Multi-Tahun\nJebakan Pandangan Besar: Filter Tautan Hanyalah Sandiwara Kepatuhan, Bukan Perisai\n\nDi peramban desktop, pengguna dilindungi oleh sistem pertahanan eksternal: Google Safe Browsing dan Microsoft SmartScreen mencegat upaya phishing yang sudah diketahui dengan menampilkan peringatan berwarna merah yang menutupi seluruh layar. Di dalam mode Big Picture Steam, overlay dalam game (Shift+Tab), dan Deck Steam (SteamOS), mekanisme pertahanan tersebut tidak tersedia. Browser bawaan ini tidak mendukung ekstensi apa pun, menonaktifkan mesin Safe Browsing eksternal, dan hanya menyisakan satu lapisan perlindungan bagi pengguna: Valve's linkfilter interstisial.\n\nGeser untuk membandingkan keempat hasil →\n\n92.5%\n2025–2026: Serangan phishing generasi terbaru lulus tanpa masalah (37/40)\n77.5%\nEra phishing CS2 2023–2024 lulus tanpa masalah (31/40)\n70.0%\nSerangan phishing warisan tahun 2021–2022 lulus tanpa masalah (28/40)\n7 dari 7\nsaluran utama perjudian diblokir (kontrol positif)\nAudit Longitudinal Multi-Tahun: 120 Domain Phishing Murni Steam Diuji Secara Langsung (24 Sep 2026)\n\nUntuk menguji apakah filter Valve hanya lambat dalam mendeteksi ancaman baru ataukah secara mendasar tidak dapat mendeteksinya sama sekali, kami melakukan audit 120 domain phishing yang terkonfirmasi terkait Steam pada tiga kelompok historis dibandingkan dengan steamcommunity.com/linkfilter:\n\nAngkatan 1: 2021–2022 (Penawaran Pertukaran Klasik & Item yang Diterima) — 70.0% Lulus Tanpa Gangguan (28/40). Bahkan 4 hingga 5 tahun setelah dicatat oleh kelompok pemantau komunitas, 7 dari 10 host phishing lama masih dapat diakses tanpa diblokir sama sekali.\nAngkatan 2: 2023–2024 (CS2 Beta Hype & Permohonan Dukungan Palsu) — 77.5% Lulus Tanpa Kesalahan (31/40). Kampanye yang menyamar sebagai pengumuman rilis Counter-Strike 2 dan seruan palsu dari komunitas (misalnya, cs2-steam.com, appealsteamcommunity.help) langsung menembus.\nAngkatan 3: 2025–2026 (Penerapan Serverless Edge & Kloning Favicon) — 92.5% Lulus Tanpa Kesalahan (37/40). Kit phishing modern yang dijalankan di EdgeOne, Vercel, dan Cloudflare Pages (misalnya steamgifter.online, steam-dp4lt5b8fnez.edgeone.dev) dapat melintas hampir tanpa hambatan.\n\nTelemetri & Perlindungan dari Tanggung Jawab, Bukan Perlindungan. Mengapa Filter Tautan ada jika ia membiarkan 70% hingga 92.5% dari phishing murni Steam lolos? Filter ini berfungsi sebagai penafian tanggung jawab perusahaan dan sensor telemetri klik keluar. Dengan menampilkan pesan yang sopan \"Kamu akan pergi Steam\" Pemberitahuan dengan tombol hijau \"Lanjutkan\" yang dapat diklik, Valve mengalihkan tanggung jawab hukum kepada korban berdasarkan Steam Perjanjian Pelanggan (*\"pengguna secara sukarela keluar dari Steam\"*). Valve mengumpulkan data telemetri dari klik tersebut, tetapi tidak mencegah pencurian.\n\nBukti Hash Favicon: Tidak Ada Pengambilan Data dari Sumber Ancaman. Platform intelijen ancaman independen (urlscan.io, Shodan, Censys) mengidentifikasi kit phishing Steam yang masih aktif dengan melakukan pencarian sederhana terhadap hash favicon resmi Steam (page.favicon.hash:9f890a9debcdfccc339149a7943be9aff9e4c9203c2fa37d5671a5b2c88503ad NOT domain:*.steampowered.com). Pemeriksaan otomatis dasar ini dapat mengidentifikasi kluster phishing aktif dalam hitungan detik. Valve tidak melakukan sinkronisasi dengan sumber data eksternal, tidak menjalankan pencarian ancaman berbasis hash, dan hanya melakukan intervensi secara manual apabila diwajibkan oleh pihak regulator (perintah WSGC tahun 2016 terkait perjudian) atau untuk melindungi rangkaian domain yang telah didaftarkan sebagai merek dagangnya.\n\nBenda-benda sebagai bukti audit utama: Audit longitudinal multi-tahun dengan 120 domain: audit-phishing-uap-longitudinal.json · 100 sampel phishing khusus Steam: linkfilter-steam-phishing-100.json · Audit pakan skala luas (n=250): linkfilter-coverage-2026-09-22.json.\n\nCSGOEmpire — pendaftaran massal sepuluh domain otorisasi bernomor\n\nPada 2020-07-20 sepuluh domain bernomor, csgoempirelogin1.com melalui csgoempirelogin10.com, telah terdaftar. Cap waktu RDAP Verisign tercatat untuk kesepuluh akun tersebut: login1 05:49:06Z, login5 05:49:08Z, login2 05:49:11Z, login3 05:49:14Z, login4 05:49:17Z, login6 05:49:20Z, login7 05:49:23Z, login8 05:49:26Z, login9 05:49:28Z — sembilan domain dalam 22 detik — dan login10 pada pukul 05:56:03Z, tujuh menit kemudian. Jarak waktunya konsisten dengan operasi massal oleh satu registrar.\n\nPola ini sejalan dengan host cadangan yang telah disiapkan sebelumnya; hanya login4 Hal ini telah teramati dalam permintaan OpenID yang aktif. csgoempire.com dan csgoempirelogin4.com sama-sama menampilkan hasil \"CLEAN\" pada Filter Tautan pada 2026-09-21; CSGOEmpire tidak termasuk di antara situs-situs yang disebutkan dalam laporan media mengenai pemberitahuan bulan Juli 2016.\n\n# DNS — semuanya 10 aktif (September 2026)\nOke csgoempirelogin1.com 172,67,129,43\nOke csgoempirelogin2.com 172,67,175,168\nOke csgoempirelogin3.com 188.114.96.3\nOke csgoempirelogin4.com 188.114.96.11 ← dalam lalu lintas OpenID\nOke csgoempirelogin5.com 172,67,160,194\nOke csgoempirelogin6–10.com Alamat IP Cloudflare\nNXDOMAIN: csgoempirelogin11.com\nKesepuluh di antaranya terdaftar 2020-07-20; kesepuluh di antaranya dilengkapi cap waktu RDAP (steam_tos_assets/domain-registry/csgoempireloginN.com.rdap.json)\nKesimpulan bagi pihak regulator\nDomain utama yang diblokir, ditambah dengan host otentikasi yang tidak diblokir, membuat rute masuk tetap terbuka — dan akan tetap terbuka selama bertahun-tahun.\n\nBlok Link Filter di domain utama merupakan catatan publik yang dapat diverifikasi. Host otentikasi mengangkut lalu lintas \"Masuk dengan Steam\" dan muncul dalam parameter permintaan OpenID milik Valve. Berdasarkan pemeriksaan terhadap 2026-09-21 dan 2026-09-22, dalam 26 pasangan yang dipisahkan oleh filter, domain utama mengembalikan blokir Filter Tautan, sedangkan proxy yang membawa login-nya tidak mengembalikan apa pun. Daftar di atas mengukur separuh lainnya: host-host ini bukanlah domain sementara yang berumur pendek. Beberapa di antaranya telah terdaftar selama lebih dari satu dekade pada tanggal pemeriksaan, dan setiap hari dari periode tersebut merupakan hari di mana Valve menerima nama host tersebut dalam parameter permintaannya sendiri. Valve belum mempublikasikan catatan penegakan per operator, sehingga tidak dapat dipastikan dari data publik apakah ada tindakan lain yang diterapkan pada host-host ini.\n\n12 tahun 6 bulan\ncsgogem.com diblokir di Filter Tautan.\nHost login-nya api.csgem.com telah\ntelah terdaftar sejak 2014-03-08 dan tidak.\nRingkasan dalam Bahasa yang Mudah Dipahami — Untuk Regulator dan Pengadilan (perluas)\nRingkasan dalam bahasa yang mudah dipahami — untuk pihak regulator\nLatar Belakang: Apa Itu Steam dan Mengapa Hal Ini Penting dalam Konteks Ini\n\nSteam adalah platform perangkat lunak yang dioperasikan oleh Valve Corporation (Bellevue, Washington, AS). Steam berfungsi sebagai penyedia identitas digital: situs web perjudian dan permainan di seluruh internet menggunakan sistem yang disebut \"Masuk dengan Steam\" — sebuah tombol yang memungkinkan situs web memverifikasi bahwa pengunjung memiliki akun Steam yang asli. Hal ini mirip dengan \"Masuk dengan Google\" atau verifikasi kartu identitas yang diterbitkan pemerintah: situs web tersebut mengarahkan pengguna ke server Steam, Steam mengonfirmasi identitas mereka, dan Steam mengarahkan mereka kembali ke situs web tersebut. Valve mengelola sistem otentikasi. Setiap proses masuk melalui \"Masuk dengan Steam\" dilakukan melalui server milik Valve sendiri.\n\nApa yang Dilakukan Valve: Pemblokiran Domain\n\nPada Juli 2016, menyusul tekanan dari media dan pihak hukum terkait perjudian skin, penasihat hukum Valve mengirimkan surat peringatan kepada sekitar 23 situs perjudian yang disebutkan namanya (menurut laporan pers tanggal 21 Juli 2016); pada Oktober 2016, Valve memberitahukan kepada Komisi Perjudian Negara Bagian Washington bahwa pihaknya telah menghubungi lebih dari empat puluh situs. Beberapa domain perjudian tercantum dalam Steam Filter Tautan — daftar yang membuat setiap tautan ke mereka yang diposting di dalam Steam (di obrolan, di halaman profil, di toko) menampilkan halaman peringatan: \"Tautan Diblokir!\" Filter Tautan adalah satu-satunya langkah penegakan yang dampaknya dapat diamati dari luar Valve.\n\nContoh: Tautan ke rollbit.com Di bagian Steam muncul halaman peringatan Link Filter (pilihan 2026-09-19 dan 2026-09-21 dicentang). Secara teori, situs judi tersebut diblokir.\nApa Itu Domain Proksi?\n\nA Host otentikasi domain terpisah adalah proxy otentikasi: alamat situs web kedua, di domain terdaftar yang berbeda, yang ditempatkan oleh operator yang sama di antara penggunanya dan Steam semata-mata untuk menjalankan langkah \"Masuk dengan Steam\". Alamat ini bertindak sebagai perantara dalam proses masuk. Pengguna mengira bahwa mereka sedang masuk ke platform; permintaan yang sampai ke Valve membawa nama host proxy tersebut, bukan nama host platform. Alamat ini biasanya tidak memiliki hubungan yang terlihat secara publik dengan situs perjudian, dan merupakan alamat yang menerima pengguna kembali setelah Steam mengonfirmasi identitas mereka.\n\nContoh: Rollbit beroperasi di bawah rollbit.com, yang diblokir oleh Link Filter. Untuk otentikasi Steam, aliran yang teramati pada 2026-09-20 menggunakan alamat terpisah: rbsnin.com, terdaftar 2026-09-18. Alamat ini mengembalikan Tidak ada blok Filter Tautan pada 2026-09-21. Situs perjudian tersebut tetap beroperasi, dan alur masuk Steam-nya berjalan melalui host yang tidak diblokir.\nTitik Kritis: Host Otentikasi Dikirim ke Steam dalam Setiap Permintaan\n\nValve tidak perlu melakukan pemindaian atau penelusuran untuk mengetahui host otentikasi mana saja yang sedang digunakan. Steam adalah Penyedia identitas OpenID untuk situs-situs ini, dan setiap klik pada tombol \"Masuk dengan Steam\" akan mengirimkan permintaan GET ke server milik Valve yang berisi nama host otentikasi dalam bentuk teks biasa. Berdasarkan OpenID 2.0 §9.1, return_to Kolom ini secara resmi bersifat opsional, tetapi tanpa kolom tersebut Steam tidak dapat menampilkan hasil login, sehingga untuk proses login Steam yang berfungsi, kolom ini pada dasarnya wajib diisi. Steam sendiri menampilkan nama host pada halaman login (\"<host> tidak berafiliasi dengan Steam maupun Valve\").\n\n— Bentuk permintaan Steam yang diterima (host sebagaimana teramati pada Rollbit di 2026-09-20): —\nDAPATKAN steamcommunity.com/openid/login\n&openid.mode=checkid_setup\n&openid.return_to=https://rbsnin.com/… ← secara efektif diperlukan; tercatat dalam log Valve\n&openid.realm=https://rbsnin.com ← dinyatakan sendiri oleh situs tersebut; ditampilkan di halaman masuk Steam\nJika situs tersebut menggunakan verifikasi server-ke-server (check_authentication), log Valve juga mencatat alamat IP server platform dan jaringan hostingnya.\n\nMengambil nama host dari permintaan ini merupakan proses standar. Catatan penegakan — host mana saja yang ditindaklanjuti, mana yang tidak, dan berdasarkan kriteria apa — hanya ada di infrastruktur Valve dan belum dipublikasikan.\n\nApa yang Ditunjukkan oleh Hal Ini\n\n1. Blok Filter Tautan berfungsi pada tautan, bukan pada proses masuk. Memblokir domain utama (misalnya rollbit.com) menampilkan peringatan kepada pengguna yang mengklik tautan ke situs tersebut di dalam Steam. Hal ini tidak menghentikan situs tersebut untuk beroperasi, maupun penggunaan layanan OpenID milik Valve melalui alamat yang berbeda.\n\n2. Host otentikasi yang diuji tidak diblokir. Tabel di atas menunjukkan host otentikasi dengan domain terpisah yang terdaftar antara tahun 2011 dan September 2026, beberapa di antaranya terdaftar bertahun-tahun setelah pemberitahuan pada Juli 2016. Pada 26 pasang, domain utama mengembalikan pemblokiran Filter Tautan, sedangkan proxy yang membawa login-nya tidak (pemeriksaan tanpa otentikasi, 2026-09-21 dan 2026-09-22; respons mentah dan SHA-256 disimpan). Proksi tersebut akan berhenti berfungsi pada hari Valve menolaknya, itulah sebabnya ukuran yang digunakan di sini adalah berapa lama proksi tersebut telah berjalan, bukan apakah proksi tersebut terdaftar atau tidak. Valve menerima nama-nama host ini dalam permintaan OpenID-nya sendiri. Apakah ada tindakan lain selain Filter Tautan yang diterapkan tidak dapat ditentukan dari data publik, karena Valve belum mempublikasikan catatan penegakan per operator.\n\n3. Situs-situs tersebut tetap melakukan otentikasi melalui infrastruktur Valve. \"Masuk dengan Steam\" adalah layanan dari Valve; setiap proses otentikasi melalui layanan ini merupakan permintaan yang diterima dan diproses oleh Valve. Valve juga memperoleh pendapatan dari case keys, dan Steam Community Market mengenakan biaya gabungan sekitar 15% untuk transaksi yang diselesaikan di dalam Market (bukan pada perdagangan eksternal). Tindakan Link Filter menciptakan catatan publik; hal itu tidak mengganggu hubungan otentikasi.\n\nApakah Pemblokiran Itu Akan Berhasil?\n\nSebagai perbandingan: ketika penyedia pendaftaran domain gratis Freenom menghentikan operasinya pada tahun 2023, kampanye phishing yang bergantung pada domain-domainnya pun terhenti. Kelangsungan operasional bergantung pada stabilitas infrastruktur.\n\nLogika yang sama berlaku di sini. Jika sebuah host otentikasi ditolak dalam proses OpenID Steam, fungsi \"Masuk dengan Steam\" pada platform tersebut akan mengalami gangguan hingga host baru terdaftar, sertifikat diterbitkan, dan propagasi DNS selesai. Selama periode tersebut: terjadi downtime.\n\nRotasi tidak membuat upaya memblokir menjadi sia-sia. Hal ini menjadikan pemblokiran sebagai biaya operasional. Karena host baru muncul dalam log permintaan Valve sendiri pada penggunaan pertama, respons dapat berjalan dengan kecepatan yang sama seperti pada penggunaan pertama tersebut.\n\nPendaftaran massal itu sendiri merupakan sebuah sinyal: Akun login1–login10 milik CSGOEmpire terdaftar pada tanggal 2020-07-20, sembilan di antaranya dalam waktu 22 detik (Verisign RDAP). Respons tidak harus diberikan per domain; serangkaian pendaftaran yang dilakukan secara berurutan dalam satu sesi pendaftar dapat diidentifikasi sebagai satu rangkaian.\n\nCatatan publik tidak menunjukkan adanya upaya untuk memblokir host otentikasi yang berhasil diatasi melalui rotasi.\nData tersebut menunjukkan domain-domain utama yang diblokir sementara proxy yang menangani setiap proses login tetap beroperasi — sebanyak 26 pasang per tanggal 2026-09-22, dengan host otentikasi tertua terdaftar sejak 12 tahun 6 bulan yang lalu — dan tidak ada catatan penegakan kebijakan yang dipublikasikan untuk operator mana pun.\nOleh karena itu, pertanyaan bagi pihak regulator adalah: tindakan penegakan apa, jika ada, yang telah diterapkan Valve terhadap host otorisasi yang diterimanya dalam permintaan OpenID-nya sendiri?\nApa yang Dilakukan Valve — dan Mengapa Hal Itu Tidak Mengganggu Jalur Otentikasi\n\nTabel di bawah ini memetakan setiap tindakan Valve yang terdokumentasi secara publik berdasarkan apakah tindakan tersebut memengaruhi titik masuk otentikasi OpenID. Temuan ini bukanlah \"Valve tidak melakukan apa-apa\" — melainkan bahwa tidak ada satu pun tindakan yang didokumentasikan secara publik yang menyentuh titik di mana proses masuk ke platform perjudian melewati server Valve.\n\nTanggal\tValve Tindakan\tTerkena dampak openid.return_to jalur?\nJuli 2016\tPernyataan publik tanggal 13 Juli 2016; pemberitahuan dari kuasa hukum kepada sekitar 23 situs yang disebutkan namanya (media, 21 Juli 2016); lebih dari 40 situs telah dihubungi berdasarkan surat Valve tertanggal Oktober 2016 kepada WSGC\tTidak. Pemberitahuan dan Filter Tautan berlaku pada operator dan tautan; jalur permintaan OpenID tidak diubah.\n2017\tPenutupan IEconItems_730/GetPlayerItems (menurut akun teknik CSFloat; tidak ditemukan catatan perubahan Valve)\tTidak. Hal ini memengaruhi visibilitas riwayat item publik. Otentikasi OpenID tidak mengalami perubahan.\n2018-03-29\tPengumuman pemblokiran perdagangan selama 7 hari di CS:GO (blog.counter-strike.net)\tTidak. Pergerakan item melambat; jalur permintaan OpenID tidak diubah.\n2022-05-10\tTitik akhir pembatalan perdagangan telah dihapus dari API Web publik (ditemukan oleh pengguna; tidak ada catatan perubahan Valve — node-steam-tradeoffer-manager #325)\tTidak. Alat pertukaran penawaran telah ditutup; otentikasi OpenID tidak diubah.\n2023-12-04\tPembuatan kunci API kini memerlukan konfirmasi melalui ponsel (steamcommunity.com/dev/apikey; tidak ada catatan perubahan)\tTidak. Titik akhir utama telah dilindungi; host otentikasi yang disebutkan di sini tidak terpengaruh.\n2026-09-19 / 21 September\tSteam Kondisi Filter Link sebagaimana diamati oleh para penulis\t14 domain utama menunjukkan adanya blokir dalam pemeriksaan ulang 2026-09-21 yang tersimpan — 26 pasangan terpisah dalam daftar berdasarkan 2026-09-22 — sementara proxy yang menangani setiap login tetap berjalan.\nSumber: Valve pernyataan tanggal 13 Juli 2016 (store.steampowered.com/oldnews/22883, telah diarsipkan 2026-09-21) · Laporan teknis CSFloat mengenai penutupan pada tahun 2017 (blog.csfloat.com, diarsipkan 2026-09-21) · Status Filter Tautan: linkfilter-recheck-2026-09-21.json.\nTemuan ini dapat dibantah dengan adanya satu contoh yang telah dipublikasikan di mana Valve menolak permintaan OpenID karena openid.return_to mengarah ke server otorisasi perjudian. Tidak ditemukan catatan serupa dalam catatan publik.\nDua pendaftaran auth-host terbaru\nhowl.unotelah terdaftar 2026-08-11 (RDAP), 41 hari sebelum 2026-09-21; howl.gg menampilkan pemblokiran Link Filter pada 2026-09-18, 2026-09-19, dan 2026-09-21. Belum dapat dipastikan apakah pemblokiran tersebut terjadi sebelum pendaftaran.\nrbsnin.comtelah terdaftar 2026-09-18T09:34:52Z (Verisign RDAP) dan terdeteksi dalam alur masuk Rollbit Steam pada 2026-09-20 melalui pemberitahuan di halaman masuk Steam sendiri; rollbit.com mengembalikan pemblokiran Filter Tautan pada 2026-09-19 dan 2026-09-21, sedangkan rbsnin.com tidak.\nSetiap host dalam tabel di atas dikirim ke server otentikasi Valve sebagai openid.realm pada setiap upaya masuk.\nData lengkap per rute dan hasil penilaian Filter Tautan: lihat tabel pada Bagian 3 di atas; hasil mentah terdapat di linkfilter-recheck-2026-09-21.json dan linkfilter-all-results.json.\nMetodologi — Bagaimana Jumlah Rute dan Filter Tautan Ditentukan\n1. Resolusi domain\nAudit 2026-09-21 telah menyelesaikan 78 dari 189 platform yang diminta: 33 di antaranya melakukan otentikasi berdasarkan nama hostnya sendiri dan 20 di antaranya berdasarkan subdomainnya sendiri — otentikasi langsung, dan tidak ada satupun di antaranya yang dihitung sebagai rute domain terpisah. Yang tersisa 25. Melakukan otentikasi melalui domain terpisah yang dapat didaftarkan, tersebar di 24 nama host yang berbeda (dota2.net digunakan bersama oleh market.csgo.com dan rust.tm): 10 diidentifikasi melalui tangkapan layar browser secara langsung, 3 melalui pemberitahuan di halaman login milik Steam sendiri, dan 12 melalui URL OpenID yang disediakan. Daftar real-time (master_registry.json, 2026-09-22) memperluas hal tersebut menjadi 44 rute domain terpisah: 26 pasangan filter-split (domain utama BLOCKED, host otentikasi CLEAN) ditambah 18 rute lainnya tanpa pemisahan domain utama. Dari 44 rute tersebut, 27. Menyimpan berkas bukti per rute; sedangkan 17 lainnya dikumpulkan secara manual dan telah diberi tanda realm_src: user dalam daftar. Lima dari ketujuh belas domain tersebut — csgogem.com, gamdom.com, 12cs.fail, csgolounge.com, dan dota2lounge.com — ditambahkan pada 2026-09-22 dengan tangkapan Link Filter untuk kedua host (HTML mentah + SHA-256 dalam linkfilter-2026-09-22.json), sehingga pemisahan itu sendiri terbukti meskipun data wilayah tersebut dikumpulkan secara manual; data tersebut tercantum dalam tabel di atas bersama dengan rute-rute dalam berkas bukti. tfauth.com (tf2easy.com) telah dihapus dari daftar pada 2026-09-22: sama seperti arena.fragnet.net, tidak ada tautan yang dapat diverifikasi yang menghubungkannya dengan situs asalnya. Jumlahnya dapat dihitung kembali dari data yang dipublikasikan auth-route-audit.json (run of 2026-09-21) berdasarkan satu aturan: sebuah platform hanya dihitung jika host OpenID Steam yang teramati berada di domain yang dapat didaftarkan yang berbeda dari platform itu sendiri.\n2. Steam Status Filter Tautan\nDiuji melalui steamcommunity.com/linkfilter/?url=https://[domain], tanpa otentikasi, pada 2026-09-19 dan 2026-09-21; HTML mentah disimpan dengan SHA-256. Status dicatat secara terpisah untuk domain utama dan host otentikasi. Sebuah pengklasifikasi membedakan pemberitahuan umum \"Anda sedang meninggalkan Steam\" (CLEAN) dari halaman \"Tautan Diblokir! ... ditandai sebagai berpotensi berbahaya\" (BLOCKED); kontrol google.com memastikan keduanya tidak disamakan. Varian terotentikasi sebelumnya dari pengujian ini dibuang setelah menghasilkan \"diblokir\" untuk setiap domain termasuk kontrol tersebut — yang ditelusuri berasal dari cookie sesi yang tidak valid dalam skrip probe, bukan hasil yang sebenarnya.\n3. Pemantauan host otentikasi\nPerekaman langsung: peramban Playwright diarahkan ke alur masuk masing-masing platform dan openid.return_to Nama host diambil dari permintaan yang disadap. Pemberitahuan halaman login: nama host diambil dari \" milik Steam sendiri\"<host> tidak berafiliasi dengan Steam atau Valve\"teks, yang Steam ditampilkan dari openid.realm (rbsnin.com, sc-auth.net, auth.dota.trade). URL yang disediakan: URL loginform a Steam yang diberikan kepada para penulis; URL ini menentukan parameter permintaan, bukan proses login yang telah selesai. Tidak ada proses login yang diselesaikan di platform mana pun.\n4. Cakupan — hal-hal yang belum terselesaikan, dan mengapa hal itu penting\nDari 189 platform tersebut, 110 tidak menghasilkan rute yang sudah ditetapkan dan satu di antaranya tidak berlaku (189 − 78 − 1). Dokumen ini tidak memperhitungkan satupun dari kasus-kasus tersebut. Rincian dari 110 kasus, berdasarkan berkas audit: 22 tantangan bot, 14 waktu habis, 12 kesalahan HTTP, dan 10 kesalahan navigasi — pengamat tidak dapat mencapai alur login, meskipun sebagian besar situs ini dapat dibuka secara normal di peramban biasa; 20 tidak menampilkan kontrol login Steam di halaman arahan; 16 mencapai alur login yang tidak dapat diselesaikan ke host; 11 domain tidak dapat diselesaikan di DNS; 5 terhenti di halaman persetujuan. Daftar di bawah ini membagi 110 situs yang sama secara berbeda: 11 situs yang tidak dapat di-resolve di DNS dicantumkan secara terpisah sebagai Dihapus · NXDOMAIN, dan satu entri yang tidak berlaku tersebut bergabung dengan yang lainnya. Sebanyak 189 platform telah diaudit, 11 di antaranya dihapus berdasarkan status NXDOMAIN definitif dari kedua resolver, 178 dipertahankan (platform-audit.json, platforms-removed.json). 137 domain otentikasi yang telah ditebak oleh ledger berdasarkan pola penamaan telah dihapus dari data pada 2026-09-19 — tidak pernah teramati, sehingga tidak pernah menjadi bukti. Tiga dari tebakan tersebut bertentangan dengan URL OpenID yang disediakan: buff.163.com, gamerpay.gg, dan csgoluck.com melakukan otentikasi secara langsung, sedangkan tebakan yang diajukan adalah buffauthproxy.163.com, gamerpayredirect.io, dan lucklogin.app. Daftar penghapusan tersebut tercantum dalam berkas audit yang telah dipublikasikan.\nAngka 25 merupakan batas bawah, bukan batas atas. Dari 78 platform yang berhasil diakses, 25 di antaranya menggunakan domain terpisah dan 53 lainnya tidak. Rasio tersebut tidak memberikan asumsi apa pun mengenai 110 platform yang tidak berhasil diakses, dan tidak ada proyeksi apa pun yang didasarkan pada rasio tersebut di mana pun dalam dokumen ini. Masing-masing dapat diselesaikan dengan membuka situs tersebut dan menekan \"Masuk dengan Steam\": nama host otentikasi terdapat di URL halaman Steam yang dimuat.\nInti dari bagian ini: Seorang pengamat independen memerlukan peramban dan kesabaran yang besar untuk mengidentifikasi 189 platform, dan berhasil mengidentifikasi 78 di antaranya. Valve memerlukan kueri basis data. Setiap platform yang menggunakan \"Masuk dengan Steam\" — baik yang sudah teridentifikasi maupun yang belum — mengirimkan openid.realm ke titik akhir otentikasi Valve pada setiap proses masuk. Adanya celah dalam tabel ini disebabkan karena para penulis berada di luar sistem. Celah tersebut tidak ada untuk Valve.\nNama host proxy yang terdeteksi terdapat di auth-route-audit.json. Tanggal pendaftaran domain dari RDAP (Verisign) / IP2WHOIS. Hasil penyaringan tautan menunjukkan linkfilter-all-results.json.\nAnalogi untuk memperjelas\n\nBayangkan sebuah perusahaan taksi berizin diberitahu oleh pihak regulator bahwa mereka tidak boleh lagi beroperasi dari alamat terdaftarnya di Main Street. Perusahaan tersebut melepas papan nama dari Main Street. Pelepasan papan nama tersebut didokumentasikan. Namun, perusahaan yang sama membuka alamat baru di Side Street — yang terdaftar dengan nama berbeda — dan terus beroperasi dari sana. Pihak regulator mengoperasikan sistem pengiriman pusat yang digunakan oleh setiap taksi dari kedua alamat tersebut. Setiap permintaan perjalanan menunjukkan \"penjemputan dari Jalan Samping.\" Pihak regulator tidak pernah mencabut izin Jalan Samping tersebut. Pencopotan papan nama Main Street adalah satu-satunya tindakan penegakan hukum yang dilakukan. Perusahaan taksi tersebut tidak pernah menghentikan operasinya.\n\nBagian A — Catatan teknis · Bagian 3.1\nDi dalam Steam, daftar Valve adalah satu-satunya daftar.\n\nTautan yang diklik di klien Steam, overlay dalam game, atau mode Big Picture tidak akan terbuka di peramban pengguna. Tautan tersebut ditampilkan di dalam peramban tertanam milik Steam sendiri — di mana lapisan peringatan yang biasanya ditampilkan oleh peramban tidak ada. Filter Tautan bukanlah salah satu dari sekian banyak langkah pengamanan. Justru, itulah keseluruhan langkah pengamanannya.\n\nDi peramban biasaTiga lapisan yang terpisah\nGoogle Safe BrowsingHalaman sela seluas satu halaman untuk situs-situs yang terdaftar dalam daftar phishing dan malware Google, yang diperbarui secara terus-menerus dan tidak bergantung pada situs yang sedang dikunjungi.\nEkstensi browser antivirusSebagian besar produk endpoint untuk konsumen dilengkapi dengan ekstensi peramban yang memeriksa tujuan situs web dengan membandingkannya terhadap daftar reputasi milik vendor tersebut.\nPemeriksaan HTTPS pada titik akhirJika produk tersebut melakukan pemeriksaan TLS, konten halaman akan dipindai sebelum sampai ke pengguna.\nDi klien Steam, overlay, dan Big PictureSatu lapisan\nGoogle Safe BrowsingTidak ada. Pemeriksaan ini memerlukan kunci API Google yang tidak disediakan dalam build Chromium yang tertanam; jika kunci tersebut tidak ada, dokumentasi desain Chromium sendiri menyebutkan bahwa penangan Safe Browsing sama sekali tidak pernah ditambahkan ke rantai permintaan.\nEkstensi antivirus untuk browserTidak ada. Renderer Steam bukanlah browser pengguna dan tidak memuat ekstensi apa pun dari profil browser pengguna, sehingga tidak ada add-on yang berjalan pada halaman tersebut.\nPemeriksaan HTTPS pada titik akhirTergantung pada produk. Lalu lintas tersebut berakhir di dalam proses Valve yang ditandatangani secara digital, bukan di peramban yang dikenali, dan sejumlah produk titik akhir mengecualikan aplikasi yang ditandatangani dari pemeriksaan TLS.\nFilter Tautan SteamDaftar blokir milik Valve, yang dirujuk ketika sebuah tautan keluar dari ekosistem Steam. Ini adalah satu-satunya pemeriksaan yang dijalankan — dan tabel di atas mencatat hasil yang ditampilkan untuk host otentikasi yang dijelaskan dalam bagian ini.\nSebuah uji yang dapat dilakukan oleh siapa pun, dan kesimpulannya menjadi tidak berlaku jika uji tersebut gagal\n\nBuka salah satu URL uji Safe Browsing yang dipublikasikan oleh Google (testsafebrowsing.appspot.com) di Chrome: muncul halaman sela berwarna merah yang menutupi seluruh layar. Buka URL yang sama dari pesan obrolan Steam, sehingga URL tersebut ditampilkan di klien Steam atau lapisan overlay: tidak muncul halaman sela. Satu-satunya peringatan yang dapat ditampilkan oleh Steam adalah halaman Filter Tautan miliknya sendiri, dan hanya untuk host yang ada dalam daftar Valve.\n\nRekor program hadiah bug milik ValveLapisan tersebut sudah pernah diatasi sebelumnya — pada rekaman Valve sendiri\n\nJika Filter Tautan merupakan satu-satunya pemeriksaan yang dijalankan di dalam klien, masalah kegagalan yang terkait dengannya bukanlah hal sepele. Dua laporan pada program HackerOne milik Valve, keduanya diterima, keduanya telah diselesaikan, dan keduanya telah diungkapkan secara lengkap:\n\n#291750diarsipkan 2025-11-16 ↗Open Redirect · medium\nPenyisipan jalur bypass pada sistem perlindungan filter\n\nDilaporkan pada 19 November 2017, telah diselesaikan, diungkapkan pada 9 Mei 2018. Bukti konsep dari laporan itu sendiri: mengganti titik ideografis 。 (%E3%80%82) untuk titik dalam nama host — Pemblokiran tersebut dapat dilewati. Konten selingan yang dimaksud dalam bagian ini tidak muncul.\n\n#1079561diarsipkan 2026-09-24 ↗Pengungkapan Informasi · tinggi\nPeramban web Big Picture membocorkan cookie login dan mengungkapkan informasi sensitif (dapat menyebabkan pengambilalihan akun)\n\nDilaporkan pada 15 Januari 2021, telah diselesaikan, diungkapkan pada 21 September 2021. Tingkat keparahan Valve sendiri tergolong tinggi, dan judulnya menyebutkan konsekuensinya. Catatan yang diungkapkan memuat judul, peringkat, dan tanggal; uraian teknisnya tidak termasuk dalam muatan yang dipublikasikan, sehingga tidak ada kutipan lebih lanjut dari sana di sini.\n\nPenafsiran para penulis, bukan temuan dari salah satu laporan tersebut: Keduanya berada di kedua sisi gerbang yang sama. Yang satu adalah peringatan yang tidak muncul sebelum halaman tujuan terbuka; yang lain adalah sesi yang terputus dari klien begitu halaman di dalamnya terbuka. Urutan peristiwa yang terjadi setelah sesi dicuri — kunci terdaftar tanpa permintaan konfirmasi, transaksi asli dibatalkan, dan salinan dikirim ke klon — merupakan pola yang dijelaskan dalam Bagian 5 ke Bagian 8. Kedua laporan tersebut telah ditutup; tidak ada satupun yang dikategorikan sebagai kerentanan aktif. Temuan yang diungkapkan dalam laporan tersebut lebih terbatas namun sudah cukup: lapisan tunggal yang tersisa memiliki riwayat yang tercatat pernah berhasil dilewati, berdasarkan catatan Valve sendiri.\n\nSumber: catatan pengungkapan HackerOne untuk setiap laporan, diambil pada 2026-09-22 — nomor, judul, tim, kelemahan, tingkat keparahan, tanggal laporan dan pengungkapan, serta status sebagaimana dipublikasikan oleh HackerOne. Catatan pengambilan data: hackerone-reports.json. Tidak disebutkan besaran hadiah di sini; tidak ada yang tercantum dalam catatan yang diungkapkan dan telah diperoleh.\n\nPengamatan lapangan · PhishDestroyDeteksi yang biasanya mengakhiri suatu kampanye tidak menghentikan kampanye-kampanye ini\n\nKami mengamati bahwa server phishing terus menarik lalu lintas sambil membawa 20 atau lebih deteksi vendor. Jika dikirim melalui web atau email, kampanye dalam kondisi seperti itu akan gagal dalam hitungan hari — baik browser maupun antivirus akan menindaklanjuti penilaian tersebut. Di dalam Steam, keduanya tidak melakukannya. Penilaian tersebut sebenarnya sudah ada sejak awal. Tidak ada satu pun komponen di sisi klien yang pernah meminta hal itu.\n\nApa artinya hal ini bagi seorang anak di bawah umur yang telah menginstal antivirus\n\nDia tidak mengabaikan peringatan apa pun dan tidak menonaktifkan apa pun. Sebuah pesan masuk ke dalam Steam — pisau gratis, suara untuk tim seorang teman — dan halaman tersebut terbuka di dalam Steam. Dia tidak pernah membuka peramban, jadi peramban tidak pernah melindunginya. Antivirusnya sedang berjalan dan mungkin sudah mengklasifikasikan domain tersebut sebagai berbahaya; namun, antivirus itu tidak pernah diminta pendapatnya. Setiap peringatan yang seharusnya bisa menghentikannya sudah ada. Tak satu pun dari peringatan itu sampai kepadanya. Dia yakin bahwa dia tidak pernah meninggalkan Steam, dan memang benar dia tidak pernah meninggalkannya.\n\nTawaran gratis ini bukanlah ide asli para pelaku phishing — penawaran barang gratis Valve adalah cara yang biasa digunakan situs skin dan perjudian untuk beriklan, dan itulah tepatnya mengapa pesan tersebut terkesan biasa saja. Keluhan: arsip penegakan hukum. Data mengenai usia dan anak-anak: Pasal 17.\n\nSumber: Steam menampilkan konten web melalui Chromium Embedded Framework di dalam steamwebhelper proses — lihat Analisis teknis DARKNAVY tanggal 27 Juni 2024 ↗ dan milik Valve sendiri Steam Forum Beta Klien ↗ diarsipkan 2025-08-04 ↗. Tidak ada versi CEF yang digunakan: Chromium yang tertanam bukanlah Chrome dan tidak menyertakan layanan Google apa pun dari Chrome. Penjelajahan Aman tanpa kunci API: Dokumen desain Chromium ↗ diarsipkan 2026-08-21 ↗, Kunci API Chromium ↗ diarsipkan 2026-08-30 ↗ (“Banyak API Google yang digunakan oleh Chrome bersifat khusus untuk Google dan tidak dimaksudkan untuk digunakan dalam produk turunan”), dan efek yang sama pada versi lain yang tidak dilengkapi kunci — Homebrew cask #193814 ↗. URL pengujian: testsafebrowsing.appspot.com ↗.\n\nDua jam yang berbeda\nUsia domain.Tanggal pengamatan.\n\nTanggal pembuatan registri menunjukkan kapan sebuah domain didaftarkan. Catatan OpenID yang bertanggal menunjukkan host pengirim dalam catatan tersebut. Yang pertama tidak dapat mencakup tahun-tahun sebelum yang kedua.\n\nDaftar lengkap ini membedakan antara domain terdaftar yang terpisah, subdomain milik situs itu sendiri, dan rute langsung. Setiap baris menautkan ke sumbernya dan hasil DNS.\n\nPeriksa daftar domain →· Unduh tanggal registrasi ↗· Ulangi pengamatan tersebut ↗\n\nBagian A — Catatan teknis · Bagian 4\nSebuah titik akhir ditutup. Pelacakan publik kehilangan sebuah kunci.\nKonteks & batasan sumber\n\nSteam telah menerapkan perubahan yang menghapus visibilitas publik terhadap ID Aset barang dan membatasi akses inventaris melalui API. Akibatnya: melacak barang tertentu berdasarkan ID Aset aslinya menjadi tidak mungkin dilakukan melalui data publik. Berikut ini adalah hal-hal yang sebelumnya mungkin dilakukan, hal-hal yang tidak lagi mungkin dilakukan setelahnya, serta konsekuensi yang harus ditanggung korban yang berusaha membuktikan ke mana perginya properti mereka. Tanggalnya adalah 2017 menurut akun teknik CSFloat; belum ditemukan changelog Valve. Urutan peristiwa tersebut — kira-kira setahun setelah pernyataan perjudian pada Juli 2016 — merupakan pertanyaan investigasi, bukan temuan. Catatan item itu sendiri tetap tersimpan di dalam sistem Valve; penyelidik eksternal kehilangan akses ke rantai ID asli, sementara pengenal float, seed, dan paint hanya memungkinkan pencocokan sebagian.\n\nAturan Valve berlaku: Steam Tim Dukungan tidak akan memulihkan item yang telah keluar dari akun Anda, dan Anda yang bertanggung jawab untuk membuktikan apa yang sebenarnya terjadi. Catatan: Pada tahun 2017, Valve menutup titik akhir yang menyalurkan ID item asli. Sebelumnya, siapa pun dapat melacak skin curian dari akun korban hingga ke bot di pasar. Setelah itu, tidak ada seorang pun di luar Valve yang bisa melakukannya. Bukti yang diminta dari korban adalah bukti yang telah dimatikan — dan itu masih ada, di dalam Valve.\n\nEra Sebelum Pemadaman Listrik\n\nSecara historis, setiap item virtual yang dihasilkan di Steam memiliki identitas yang unik secara global dan tidak dapat diubah ID Aset. Basis data OSINT pihak ketiga dapat mengindeks ID-ID tersebut. Jika suatu aset milik pengguna dibajak, para penyelidik dapat melacak riwayat pergerakan aset tersebut saat dipindahkan dari akun perantara pelaku pembajakan ke akun penyimpanan di pasar daring atau situs perjudian.\n\nSEBELUMNYA: siapa pun dapat melacak pergerakan suatu aset dari akun korban melalui akun-akun perantara hingga ke bot penyimpanan di pasar atau kasino, dengan menggunakan data publik.\nSetelah perubahan tersebut\n\nMenurut akun teknik CSFloat, Valve menutup titik akhir pada tahun 2017 dan ID item asli tidak lagi tersedia bagi pihak luar. Belum ditemukan pernyataan Valve mengenai alasan perubahan tersebut. Pada periode yang sama, juga belum ditemukan tindakan yang dipublikasikan terhadap akun bot komersial yang memindahkan item dalam skala besar.\n\nApa pun alasannya, perubahan tersebut memutus rantai kepemilikan publik. Seorang korban tidak lagi dapat menelusuri rantai ID asli dari data publik untuk membuktikan bahwa suatu barang curian tertentu telah dilikuidasi melalui pasar atau kasino tertentu. Catatan barang tersebut masih ada di dalam sistem Valve; masyarakat umum, peneliti, dan penegak hukum yang bekerja berdasarkan data publik tidak dapat mengaksesnya.\n\nSETELAHNYA: Pelacakan suatu barang tertentu berdasarkan ID Aset aslinya tidak lagi dapat dilakukan melalui data publik. Rantai pertanggungjawaban ID asli untuk suatu barang yang dipindahkan setelah tahun 2017 hanya ada di dalam infrastruktur Valve; tidak ada catatan semacam itu yang dipublikasikan. Pengidentifikasi Float, seed, dan paint hanya memungkinkan pencocokan parsial dan probabilistik.\nIEconItems_730\nDAPATKAN/IEconItems_730/GetPlayerItems/v1/\nPayload yang Dapat Dilacak (Pra-Patch)\n\"id\": \"14892281934\",\n\"original_id\": \"11829910211\",\nStatus: Korban dapat melacak riwayat pergerakan barang di seluruh akun bot.\nPayload yang Disamarkan (Pasca-Patch)\nSaat ini\n\"id\": \"HIDDEN_BY_PRIVACY_SETTINGS\",\n\"original_id\": \"NULL\",\nStatus: Pihak luar tidak lagi dapat melacak riwayat barang berdasarkan ID Aset asli dari data publik.\nDampak terhadap bukti: Setelah perubahan tersebut, data publik yang diperlukan untuk melacak suatu item tertentu berdasarkan ID Aset aslinya—mulai dari akun korban hingga ke bot pasar daring atau kasino—tidak lagi tersedia. Catatan internal tersebut masih tersimpan di Valve; korban, peneliti, atau penyelidik yang bekerja berdasarkan data publik tidak dapat mereproduksi rantai ID asli (pengidentifikasi float, seed, dan paint hanya memungkinkan pencocokan sebagian).\n\nSumber: Laporan teknis CSFloat mengenai penutupan pada tahun 2017 dari IEconItems_730/GetPlayerItems — blog.csfloat.com/how-floatdb-tracks-items (telah diarsipkan 2026-09-21) · payload yang ditampilkan hanyalah ilustrasi bentuk bidang, bukan respons yang terekam · belum ditemukan catatan perubahan Valve untuk penutupan tersebut.\n\nBagian A — Catatan teknis · Bagian 5\nSatu sesi. Akses yang lebih luas daripada yang terlihat oleh pengguna.\nKonteks & batasan sumber\n\nArsitektur kunci API Valve, sebagaimana adanya sebelum perubahan tahun 2023, menyimpang dari standar industri dasar (OWASP ASVS, NIST SP 800-63B) dan merupakan mekanisme yang dijelaskan dalam pengaduan pencurian inventaris otomatis yang disimpan dalam arsip bukti (Bagian 6–8).\n\nAturan Valve diterapkan: Pemegang akunlah yang membuat kunci tersebut, menyetujui syarat-syaratnya, dan menanggung kerugiannya — itulah jawaban yang tercantum dalam arsip penolakan. Catatan: Hingga Desember 2023, cookie sesi yang dicuri saja sudah cukup untuk mendaftarkan kunci tersebut. Tanpa kata sandi. Tanpa Steam Guard. Tanpa pemberitahuan kepada pemilik akun tersebut. Pengguna tersebut tidak membuat kunci tersebut, tidak dapat melihatnya, namun diberitahu bahwa dia yang membuatnya. Konfirmasi melalui ponsel ditambahkan pada 2023-12-04 — sekitar tujuh tahun setelah pernyataan tahun 2016 dan kira-kira enam tahun setelah panel-panel penipuan yang disimpan dalam arsip tersebut. Biaya selama tahun-tahun itu tidak ditanggung oleh Valve. Biaya tersebut dibayar dari rekening-rekening yang telah dikosongkan selama periode tersebut, sebagian di antaranya milik anak-anak.\n\nOWASP ASVS 2.8 / NIST SP 800-63BTINGKAT KEPARAHAN: KRITIS\n1. Otentikasi Bertahap yang Tidak Memadai\n\nSteam memungkinkan pembuatan kunci API dengan hak akses tinggi dan masa berlaku panjang hanya dengan menggunakan cookie sesi. Tidak diperlukan 2FA (Steam Guard) atau tantangan otentikasi lanjutan saat membuat atau mengubah kunci API pengembang, sehingga konfirmasi melalui perangkat seluler Steam Guard — satu-satunya faktor kedua yang ditawarkan Steam — tidak melindungi langkah ini. (Faktor kedua berbasis perangkat keras telah diminta di pelacak Valve sendiri pada tahun 2016 dan masalah ini masih terbuka: Lampiran D, GH-01.)\n\nStatus: belum diperbaiki sebelum tahun 2023. Memungkinkan skrip yang menyimpan cookie curian untuk mendaftarkan kunci tanpa interaksi pengguna sama sekali.\nOWASP A01:2021 / Prinsip Hak Akses TerbatasTINGKAT KEPARAHAN: KRITIS\n2. Tidak adanya Prinsip Hak Akses Terbatas\n\nAPI Web Steam tidak memiliki cakupan otorisasi berbasis peran sama sekali. Kunci API pengembang yang diterbitkan untuk status inventaris \"hanya baca\" memiliki izin \"tulis\" penuh — termasuk kemampuan untuk memodifikasi transaksi yang sudah ada, memulai transaksi baru, mendaftarkan webhook, dan menolak pertukaran yang tertunda dan sah.\n\nStatus: cacat desain sistemik. Satu kunci = kendali penuh atas inventaris dan transaksi akun, baik untuk membaca maupun menulis.\nOWASP A07:2021 / SesiTINGKAT KERASAN: TINGGI\n3. Gangguan dalam Pengelolaan Sesi\n\nPara pengguna melaporkan bahwa sesi web yang dibajak yang berasal dari rentang alamat IP server hosting tetap berlangsung. Praktik standar adalah menghentikan sesi jika terjadi anomali geografis atau saat kata sandi diubah; laporan pengguna yang terkumpul dalam arsip menggambarkan adanya sesi yang tetap aktif setelah kata sandi diubah.\n\nStatus: masalah yang telah dilaporkan (keluhan pengguna dalam arsip). Sesi dapat menghasilkan kunci API tanpa perlu otentikasi ulang.\nPemblokiran di tingkat domain secara teknis dapat dilakukanKELAYAKAN PENEGAKAN HUKUM\n4. Pemblokiran Host Otentikasi di Tingkat Domain Secara Teknis Dapat Dilakukan\n\nValve sudah mengelola daftar domain (Link Filter) dan sudah menerima setiap nama host otentikasi dalam permintaan OpenID-nya sendiri. Kedua mekanisme tersebut tidak terhubung dengan cara apa pun yang terlihat dari luar: per 2026-09-22, pada 26 pasangan, domain utama berada di filter sementara proxy yang mengangkut proses login-nya tidak.\n\nMenghubungkannya merupakan tugas teknik yang sederhana: baca openid.realm mengambil nama host dari setiap permintaan yang masuk, membandingkannya dengan daftar, dan menolak atau menandai permintaan tersebut. Ilustrasi di sebelah kanan menunjukkan alur kerja rutinitas semacam itu. Menolak host otentikasi — alih-alih hanya halaman arahan publik — akan mengganggu langkah \"Masuk dengan Steam\" yang menjadi andalan platform-platform ini.\n\nTidak ada bukti publik yang menunjukkan bahwa Valve melakukan pemeriksaan semacam itu. Biaya gabungan Steam Community Market sebesar sekitar 15% berlaku untuk transaksi yang diselesaikan di dalam Pasar tersebut; biaya tersebut tidak dikenakan pada transaksi eksternal di platform-platform tersebut.\n\nblock_auth_hosts.pyILUSTRASI\n// Baca host Steam yang sudah terdeteksi — tidak perlu melakukan pemindaian\ndef on_openid_request(request):\nhost = parse_openid_realm(request)\njika tuan rumah di domain_yang_diblokir:\nmenolak (permintaan)\nCatatan: Pseudokode ini hanya untuk ilustrasi. Kedua bagian tersebut sudah ada di Valve — nama host otentikasi tercantum dalam permintaan, dan daftar domain merupakan Filter Tautan. Tidak ada catatan publik yang menjelaskan mengapa keduanya tidak terhubung.\nBagian 5.1 — Standar-standar tersebut tidak pernah diterbitkan\nValve berhasil dikompilasi sesuai aturan tersebut setiap hari. Namun, di sini, kompilasi tidak berhasil sesuai aturan tersebut.\n\nSteam tersedia di App Store dan Google Play, melakukan penjualan melalui penyedia layanan pembayaran kartu utama, serta memanfaatkan API pihak ketiga seperti platform besar lainnya. Setiap hubungan tersebut memiliki persyaratan keamanan yang telah dipublikasikan dan bertenor tertentu yang harus dipenuhi oleh Valve agar dapat terus beroperasi. Bandingkan tanggal persyaratan tersebut dengan tanggal ketika Web API milik Steam sendiri memperoleh perlindungan yang sama. Tidak ada satu pun yang tercantum di bawah ini yang merupakan standar internal, memo internal, atau rahasia dagang: setiap baris merupakan dokumen publik yang dilengkapi dengan tanggal penerbitan.\n\nPersyaratan keamanan eksternal yang telah dipublikasikan, beserta tanggalnya, dibandingkan dengan tanggal ketika Web API Steam menerapkan pengendalian yang setara\nStandar yang telah diterbitkan, serta tanggal berlakunya\tAPI Web Steam terkait pertanyaan yang sama\nOtorisasi yang dibatasi cakupannyaOAuth 2.0 — RFC 6749, Oktober 2012. Bagian 3.3 mendefinisikan scope Sehingga, klien hanya menerima akses yang dimintanya. Sejak saat itu, hal ini telah menjadi pengaturan default pada setiap API platform utama.\tCakupan granular diperkenalkan pada 16 Januari 2026.Sebelumnya, satu kunci API Web Steam memiliki akses penuh untuk membaca dan menulis data transaksi akun tersebut, terlepas dari alasan penerbitannya. Tiga belas tahun dan tiga bulan setelah spesifikasi yang mendefinisikan kontrol tersebut.\nKunci bukanlah otorisasiDokumentasi Cloud resmi dari Google: Kunci API standar tidak dapat mengautentikasi sebuah entitas, dan untuk API yang membuat atau mengelola sumber daya, Jangan gunakan kunci otorisasi di lingkungan produksi.\tKunci API Web Steam memang persis seperti itu.Sebuah string pemegang, yang diterbitkan untuk suatu akun, yang dengan sendirinya sudah cukup untuk membaca inventaris, membatalkan transaksi yang tertunda, dan mengirimkan transaksi baru. Tidak ada pihak utama yang diautentikasi pada saat penggunaan.\nOtentikasi multi-faktor pada akses istimewaPCI DSS 3.2, persyaratan 8.3 — wajib mulai dari 1 Februari 2018 untuk semua akses administratif non-konsol dan semua akses jarak jauh ke lingkungan data pemegang kartu. Apple kemudian mewajibkan otentikasi dua faktor bagi setiap pemegang akun Program Pengembang mulai dari 27 Februari 2019: Pengembang yang memiliki peran Pemegang Akun dalam program pengembang harus mengaktifkan otentikasi dua faktor untuk masuk.\tDiperlukan faktor kedua untuk membuat kunci API dari 4 Desember 2023.Sampai saat itu, cookie sesi yang dicuri saja sudah cukup, tanpa munculnya peringatan di ponsel pemilik akun dan tanpa pemberitahuan setelahnya. Empat tahun dan sembilan bulan setelah Apple mewajibkan Valve untuk menggunakan otentikasi dua faktor hanya untuk masuk ke portal pengembang.\nSiklus hidup dan pencabutan kredensialTwitch mewajibkan setiap aplikasi pihak ketiga untuk: Aplikasi Anda harus memverifikasi token OAuth saat pertama kali dijalankan dan setiap jam setelahnya, dan menyatakan bahwa pihaknya melakukan audit terhadap aplikasi yang tidak mematuhinya. API v5 lamanya telah dihentikan sepenuhnya pada 28 Februari 2022 sesuai jadwal yang telah diumumkan.\tTidak ada catatan siklus hidup kunci yang dipublikasikan.Perubahan pada tahun 2023 melindungi titik akhir pembuatan. Tidak ditemukan pernyataan Valve yang menyebutkan bahwa perubahan tersebut mencakup kunci yang sudah terdaftar, dan tidak ada catatan perubahan (changelog) yang menyertai perubahan tersebut sama sekali. Apakah kunci yang dibuat sebelum perubahan tersebut menjadi tidak valid tidak dapat dipastikan dari data publik — yang merupakan pertanyaan yang perlu dijawab bagi subjek data agar mereka mengetahui apakah kunci yang dibuat di akun mereka bertahun-tahun sebelumnya masih aktif.\nTolok Ukur Arsitektur // Arsitektur Token\nCakupan Tingkat Halus GitHub vs Valve Steam Web API\n\nValve pengembang mengelola perangkat lunak sumber terbuka di GitHub setiap hari dengan menggunakan token berprivilese minimal yang terperinci. Bandingkan hal itu dengan kunci monolitik yang diterbitkan untuk 130 juta Steam pemain.\n\nToken Berbasis Detail di GitHub\nDigunakan oleh Valve di GitHub\n\nToken bergranularitas halus dengan isolasi berbasis lingkup dan penerapan siklus hidup yang wajib.\n\nAkses Repositori:Hanya Repos yang Dipilih (1 repo)\nIzin Masalah:Hanya baca [✓]\nKode & Rahasia:Tidak ada akses [✕]\nTanggal kedaluwarsa:30 Hari (TTL Wajib)\nPencatatan Audit:IP, User-Agent, dan Cap Waktu\nKondisi Keamanan: Token dengan hak akses minimal membatasi kerusakan pada satu sumber daya yang hanya dapat dibaca.\n!Valve Steam Kunci API Web\nTelah didistribusikan kepada 130 juta pengguna\n\nSatu string utama berisikan 32 karakter yang mencakup wewenang perdagangan dan persediaan secara keseluruhan atau tidak sama sekali.\n\nAkses Akun:AKUN LENGKAP (Monolitik)\nManajemen Perdagangan:Baca, Batalkan, Tolak [!]\nCakupan Granular:TIDAK ADA (Tiba pada tahun 2026, terlambat 13 tahun)\nTanggal kedaluwarsa:TIDAK PERNAH (Berlaku tanpa batas waktu)\nPencatatan Audit:TIDAK ADA (Pengguna tidak memiliki riwayat IP)\nKerentanan: Kunci yang dicuri memungkinkan penyadapan diam-diam terhadap semua penawaran perdagangan yang dikirimkan.\nStandar yang diterapkan dalam satu arah\n\nMisalkan sebuah vendor Valve bergantung pada — penyedia layanan awan, pemroses pembayaran, atau CDN — yang membiarkan titik akhir kredensial tanpa otentikasi dua faktor, dan beberapa bulan kemudian data korporat Valve bocor melalui kunci yang dihasilkan di titik akhir tersebut. Akankah Valve menerima bahwa kesalahan terletak pada siapa pun yang mengklik tautan tersebut? Penolakan-penolakan yang diarsipkan dan disimpan dalam berkas ini menjawab pertanyaan yang sebaliknya bagi pengguna: posisi yang diambil adalah bahwa pemegang akunlah yang membuat kunci tersebut dan menanggung kerugiannya. Arsitektur yang sama dijelaskan sebagai kegagalan penyedia layanan di satu sisi dan tanggung jawab pengguna di sisi lain. Hal mana yang benar bukanlah pertanyaan teknis, dan bukan pula sesuatu yang dapat diputuskan oleh penyelidikan ini — hal itu merupakan kewenangan pengadilan atau otoritas pengawas.\n\nIlustrasi, bukan bukti — standar yang diartikan sebaliknya\nSebuah penyedia layanan pemrosesan pembayaran yang memungkinkan skrip pihak ketiga membuat kredensial transaksi dengan hak akses penuh hanya berdasarkan cookie browser, tanpa ada pemberitahuan kepada pemegang akun.\nPenyedia identitas yang menutup celah yang digunakan untuk mencetak token-tokennya dan tidak mempublikasikan informasi apa pun mengenai token-token yang telah dicetak.\nSebuah bank yang menanggapi sengketa transfer dengan menyatakan bahwa kredensial yang digunakan terdaftar pada rekening nasabah itu sendiri, dan menutup laporan tersebut.\n\nTak satu pun dari hal-hal ini dimaksudkan sebagai kesimpulan mengenai perusahaan tertentu mana pun. Ini adalah keputusan desain yang sama, namun diterapkan dalam konteks di mana tanggapan pihak pengawas telah didokumentasikan dengan baik — dan inilah perbandingan yang diminta untuk dilakukan oleh pihak regulator.\n\nApa yang terungkap dalam catatan: Ketentuan-ketentuan yang tidak terdapat dalam API Web Steam bersifat terbuka, sudah ketinggalan zaman, dan, dalam beberapa kasus, merupakan persyaratan Valve yang harus dipenuhi agar perusahaan tersebut dapat terus mengirimkan produknya sendiri. Selang waktu antara setiap standar dan perubahan setara Steam dapat diukur dan telah dijelaskan di atas. Yang tidak dijelaskan di sini adalah alasannya. Belum ditemukan pernyataan alasan Valve mengenai salah satu dari rentang waktu tersebut, dan tidak ada asumsi yang dibuat di sini; catatan tersebut terdapat di dalam Valve dan belum dipublikasikan.\n\nSumber-sumber, masing-masing berupa dokumen publik: OAuth 2.0 — RFC 6749, Oktober 2012 ↗ · Google Cloud — Dokumentasi kunci API ↗ · Persyaratan PCI DSS 3.2 nomor 8.3 — Panduan Sumber Daya PCI SSC ↗ · Apple — Persyaratan Otentikasi Dua Faktor yang Akan Berlaku bagi Pemegang Akun, 20 Februari 2019 ↗ diarsipkan 2025-05-06 ↗ · Twitch — persyaratan validasi token ↗ dan Pemberitahuan penghentian layanan v5 ↗ diarsipkan 2025-01-27 ↗. Tanggal yang tercantum pada Steam adalah tanggal yang terdapat dalam catatan pembaruan di bagian ini; entri tahun 2023 dan 2026 adalah entri yang dirilis oleh Valve tanpa catatan perubahan. Diambil pada 2026-09-22.\n\nCatatan pembaruan milik Valve — bertanggal, bersumber dari sumber-sumber publik\nTanggal\tValve ubah\tSudah diumumkan?\tApa yang ditutup\tLag: mekanisme publik → diperbaiki\tSumber\n2026-09-01\tPenandaan Otomatis Percakapan yang Mencurigakan\tYa\tTautan / pola berbahaya dalam obrolan grup\t—\tberita ↗\n2026-01-16\tCakupan terperinci Steamworks Web API\tYa\tCakupan hak akses minimal untuk kunci pengembang\t—\tpengumuman ↗\n2025-07-15\tCS2 Perlindungan Perdagangan & Jendela Pembalikan\tYa\tTidak ada apa-apa. Ini bukan solusi keamanan yang mengatasi akar masalah. Akses pemulihan akun oleh tim dukungan tetap tidak terpengaruh. Memicu pembatalan akan mengakibatkan pemblokiran perdagangan otomatis selama 30 hari (Skinvault ↗), sementara guncangan perdagangan tunai menyebabkan penurunan kapitalisasi pasar sebesar $104M (-25%) dalam 24 jam (CSMarketCap ↗). Pada tahun 2026, pengatur waktu mulai diterapkan per item (Skin.land ↗).\t—\tPertanyaan yang Sering Diajukan ↗\n2025-05-14\tPengumuman Mengenai Keamanan Akun\tYa\tPanduan tentang pencurian / pembajakan sesi\t—\tpengumuman ↗\n2024-10-02\tCS2 'The Armory' - Penundaan selama 7 hari\tYa\tPenundaan perdagangan/perdagangan barang-barang Armory\t—\tpengumuman ↗\n2024-09-18\tPembatasan transaksi saat masuk menggunakan perangkat baru\tYa\tPembatasan transaksi selama 2–7 hari pada perangkat baru\t—\tPertanyaan yang Sering Diajukan ↗\n2024-02-14\tPenundaan perubahan nama profil & avatar\tYa\tWaktu tunggu 2–4 jam untuk transaksi setelah penggantian nama\t—\tposting ↗\n2023-12-04\tKonfirmasi melalui ponsel untuk kunci API\tTidak ada catatan perubahan\tPendaftaran kunci secara diam-diam hanya melalui cookie\tSekitar 6 tahun setelah panel-panel era 2017\thalaman pengembang ↗\n2023-10-24\tSMS MFA untuk publikasi rilis game\tYa\tPenerbitan build Steamworks\t—\tpengumuman ↗\n2023-07-12\tPeringatan mengenai konten biografi khusus\tYa\tTautan phishing di bio\t—\tforum ↗\n2023-01-25\tProfil {TAUTAN DIHAPUS} & waktu tunggu\tYa\tTautan dalam teks profil\t—\tPertanyaan yang Sering Diajukan ↗\n2022-10-24\tPerombakan sistem login & pemotongan cookie\tTidak ada catatan perubahan\tSesi yang dicuri tanpa batas\t— (Migrasi token IAuthenticationService)\tberita ↗\n2022-10-12\tAplikasi Seluler 3.0: Masuk dengan QR\tYa\tPanel pencabutan otorisasi sesi\t—\tberita ↗\n2022-05-10\tTitik akhir pembatalan transaksi telah dihapus\tTidak ada catatan perubahan\tPertukaran penawaran (batalkan & kirim ulang)\tSekitar 5 tahun setelah panel-panel era 2017\tedisi #325 ↗\n2020-05-25\tPemblokiran perdagangan Dota 2 selama 7 hari\tYa\tJual beli barang dengan cepat\t—\tblog ↗\n2018-03-29\tKunci perdagangan 7 hari di CS:GO\tYa\tPencucian bot instan\t≈20 bulan setelah pernyataan pada Juli 2016\tblog ↗ diarsipkan 2025-02-26 ↗\nSumber: postingan Valve yang ditautkan, halaman bantuan, dan masalah di GitHub, sesuai tanggal yang tertera. Tiga perbaikan penting dirilis tanpa catatan perubahan (Mei 2022, Oktober 2022, Desember 2023) dan terdeteksi oleh pengguna, bukan diumumkan oleh Valve — asimetri tersebut merupakan bagian dari catatan penegakan. Keterlambatan dihitung hanya jika tanggal dalam dokumen itu sendiri (pernyataan Juli 2016; panel penipuan era 2017) menyediakan titik awalnya; “—” berarti titik awal tersebut tidak ditetapkan di sini.\nBagian A — Catatan teknis · Bagian 6\nSimulator Eksploitasi & Pembajakan Interaktif\nKonteks & batasan sumber\n\nRekontruksi alur proses mulai dari pesan phishing hingga pendaftaran kunci di sisi server dan proses pertukaran perdagangan. Sebelum tahun 2023, kunci Web API yang terdaftar pada suatu akun dapat membaca inventarisnya, membatalkan penawaran perdagangan yang tertunda, dan membuat penawaran baru, serta tidak ada layar konfirmasi perdagangan yang ditampilkan kepada pemilik akun untuk tindakan-tindakan tersebut. Hal tersebut merupakan pelanggaran prinsip hak akses minimal (OWASP A01:2021). Waktu yang ditampilkan dalam simulasi ini bersifat ilustratif dan bukan merupakan pengukuran langsung dari platform saat ini.\n\nIkuti langkah demi langkah rekonstruksi upaya pembajakan akun ini. Setiap tahap menunjukkan apa yang dilihat oleh pemilik akun dan, di sebelahnya, panggilan Steam yang diterima pada saat yang sama. Setiap panggilan tersebut telah diautentikasi dengan benar. Tidak ada satu pun tahap dalam urutan tersebut yang harus bergantung pada otentikasi Steam agar gagal — kunci yang diterbitkannya harus tidak memiliki cakupan (OWASP A01:2021).\n\nApa yang dilihat pemain. Apa yang berubah di baliknya.SIMULATOR LANGKAH DEMI LANGKAH\nLangkah 5 / 5\n\nEksploitasi Telah Selesai. Karena mengira akan menerima notifikasi melalui ponsel terkait transaksi aslinya, korban pun menyetujui transaksi pengganti tersebut. Ini adalah panduan forensik terintegrasi yang menunjukkan bagaimana tidak diterapkannya prinsip Hak Akses Terbatas (Least Privilege) (OWASP A01:2021) memungkinkan terjadinya pembajakan aset secara otomatis dalam hitungan kurang dari satu detik.\n\n01 / UMPAN PERCAKAPANSeorang teman meminta saya untuk memberikan suaraKorban menerima pesan yang berisi tautan.\n02 / HALAMAN MASUKPortal yang miripKorban memasukkan kredensial login.\n03 / AKSESPembuatan API Silent WebPenyerang mendaftarkan kunci pengembang.\n04 / PERUBAHANPerdagangan sah yang ditukarBot kloning menduplikasi penerima sasaran.\n05 / KONFIRMASIPalsu yang telah disetujuiPenawaran yang salah telah disetujui melalui ponsel.\nLangkah yang sama, dilihat dari sudut pandang jaringanRekonstruksi pola sebelum tahun 2023 · contoh bentuk panggilan\nKorbanMenyetujui pesan notifikasi seluler yang semula diharapkan untuk transaksi tersebut.\nPenyerangMenerima barang-barang tersebut di akun klon.\nSteam melihatSebuah transfer yang dikonfirmasi oleh pemegang akun melalui perangkat yang terdaftar.\nConfirmation genuine — made by the account holder\nRecipient the clone bot, not the intended counterparty\nThe confirmation is authentic. The offer it confirms is not the one the user initiated.\n\nCatatan yang ditinggalkan: sebuah transaksi yang disetujui pengguna. Itulah catatan yang dibaca oleh Tim Dukungan Steam saat keluhan masuk, dan alasan mengapa keluhan-keluhan yang telah diarsipkan ditutup sebagai kesalahan pengguna. Keluhan-keluhan tersebut terdapat di arsip penegakan hukum.\n\nBagian A — Catatan teknis · Bagian 7\nTitik akhir di balik urutan tersebut.\nKonteks & batasan sumber\n\nBerikut adalah titik akhir Web API Steam yang digunakan oleh skrip pembajakan yang dilaporkan untuk menyadap transaksi tanpa melalui langkah-langkah konfirmasi di sisi peramban.\n\nEmpat titik akhir yang tercatat sudah cukup untuk menyelesaikan seluruh proses. Tak satu pun di antaranya merupakan celah, tak satu pun perlu dieksploitasi — kunci yang sah memanggil titik-titik akhir tersebut dan Steam merespons. Kunci adalah satu-satunya hal yang harus dicuri oleh penyerang.\n\nIEconService / GetTradeOffers / v1Jajak Pendapat\n\nDigunakan untuk memantau penawaran perdagangan di akun tersebut. Skrip-skrip tersebut melakukan polling terhadap titik akhir ini berulang kali menggunakan kunci API yang telah diretas; titik akhir ini mengembalikan rincian penawaran perdagangan yang baru dibuat, sedang dalam proses, atau telah diubah. Interval polling tidak diukur di sini.\n\nVektor ancaman: Menampilkan ID penawaran perdagangan yang masih dalam proses serta rincian profil penerima.\nIEconService / BatalkanPenawaranPerdagangan / v1INTERAKSI\n\nDigunakan untuk secara otomatis membatalkan penawaran perdagangan sah milik pengguna. Sebelum tahun 2023, tidak ada otentikasi berlapis yang melindungi kunci tersebut, sehingga server otomatis dapat membatalkan penawaran begitu penawaran tersebut terdeteksi, tanpa ada pemberitahuan apa pun kepada pemilik akun.\n\nVektor ancaman: Membatalkan transaksi sebelum pemegang rekening menyelesaikan konfirmasi melalui ponsel.\nISteamUser / GetPlayerSummaries / v2RECON\n\nDilakukan kueri untuk mengambil nama profil, URL gambar avatar, dan level penerima transaksi yang sah. Hal ini memungkinkan skrip untuk menyesuaikan akun klon yang telah disiapkan agar sesuai. Waktu eksekusi tidak diukur di sini.\n\nVektor ancaman: Menyediakan data yang diperlukan untuk menyamar sebagai penerima yang dimaksud.\n/dev/ajaxregisterkeyPENCIPTAAN\n\nTitik akhir pendaftaran Steam untuk kunci. Sebelumnya, setiap sesi cookie browser yang aktif (`steamLoginSecure`) dapat mendaftarkan sebuah kunci tanpa konfirmasi Steam Guard di perangkat seluler, dan tanpa pemberitahuan apa pun kepada pemilik akun.\n\nVektor ancaman: Kredensial permanen yang dibuat oleh sebuah skrip, tanpa sepengetahuan pemilik akun.\nBagian A — Catatan teknis · Bagian 8 · Pasal 7 GDPR\nKotak yang dicentang. Tindakan siapa?\nKonteks & batasan sumber\n\nDalam menanggapi penolakan penggantian biaya, Steam Tanggapan tim dukungan yang tersimpan di arsip menyatakan bahwa pemegang akunlah yang membuat kunci API tersebut dan, dengan mencentang kotak tersebut, telah menyetujui persyaratannya.\n\nTanggapan dari tim dukungan mengaitkan kunci tersebut dengan pemilik akun. Pertanyaannya adalah apakah catatan tersebut membuktikan siapa yang sebenarnya membuatnya.\n\nNamun, dalam pola pembajakan kunci API yang teramati, korban sama sekali tidak pernah melihat atau membuka halaman pembuatan kunci API. Kolom persetujuan dikirimkan oleh sebuah skrip yang menjalankan permintaan POST headless menggunakan cookie sesi yang dicuri.\n\nBerdasarkan Pasal 7 dan Pasal 4 ayat (11) GDPR, persetujuan harus berupa pernyataan kehendak subjek data yang diberikan secara sukarela, spesifik, berdasarkan informasi yang memadai, dan tidak ambigu. Pendapat para penulis adalah bahwa kolom persetujuan syarat dan ketentuan yang dikirimkan oleh skrip berbahaya menggunakan cookie yang dicuri, tanpa menampilkan halaman apa pun kepada pemegang akun, tidak dapat memenuhi definisi tersebut. Apakah hal tersebut memenuhi definisi tersebut merupakan kewenangan otoritas pengawas.\n\nAnalisis Muatan Forensik: Pendaftaran Kunci\nPOSTING https://steamcommunity.com/dev/ajaxregisterkey\n// Muatan Permintaan (Disisipkan melalui skrip pembajakan)\n{\n\"setujuDenganKetentuan\": \"setuju\", <-- dimasukkan secara otomatis, tanpa campur tangan manusia\n\"domain\": \"localhost\", ← belum diverifikasi — nilai apa pun diterima, termasuk localhost\n\"sessionid\": \"8f0d8ef763ab2140bf89de2a\"\n}\nPertanyaan untuk otoritas pengawas: apabila pemegang akun tidak pernah mengklik kotak persetujuan, apakah penerimaan syarat dan ketentuan yang tercatat pada akun tersebut memenuhi persyaratan Pasal 7 mengenai pernyataan kehendak subjek data yang diberikan secara sukarela, spesifik, berdasarkan informasi yang memadai, dan tidak ambigu, serta apakah Steam Layanan Dukungan dapat mengandalkan hal tersebut untuk menolak klaim.\n\nSumber: bentuk permintaan pendaftaran kunci sebagaimana direkonstruksi dari titik akhir publik dan dari laporan pembajakan yang disimpan dalam arsip bukti (versi 2026-09-17 yang dapat dicari) · Pengenal sesi yang ditampilkan hanyalah tempat penampung, bukan nilai yang direkam.\n\nOtopsi Forensik · Vektor Substitusi Komoditas\nBagaimana Valve Akhirnya Menetralkan \"Substitusi Perdagangan\" — Dan Mengapa Butuh 7 Tahun Penyesuaian Sementara\n\nSelama hampir satu dekade, \"Penggantian Kunci API\" (atau Penipuan MitM API) merupakan model pencurian akun yang paling menguntungkan di Steam, yang berhasil menguras ratusan juta dolar dalam bentuk skin dari para pemain yang tidak curiga. Valve tidak memberantas celah keamanan tersebut dengan memperbaiki arsitektur API yang rentan; sebaliknya, Valve menghabiskan tujuh tahun untuk menerapkan empat lapisan penghalang transaksi di seluruh platform yang melumpuhkan likuiditas perdagangan komunitas, sementara akar masalahnya tetap tidak ditangani.\n\n1. Kematian Akibat Peniruan\nWaktu Tunggu Avatar & Nama (Februari 2024)\n\nSerangan tersebut membutuhkan peniruan dalam hitungan kurang dari satu detik: bot penipu itu mencegat transaksi yang akan dikirim, lalu mengambil data avatar/nama penerima melalui ISteamUser, dan mengkloning profil tersebut dalam waktu 200 milidetik. Pada 14 Februari 2024, Valve secara diam-diam memberlakukan suatu kewajiban Waktu tunggu transaksi 2–4 jam (Kesalahan 34) segera setelah terjadi perubahan nama profil atau avatar. Bot tidak lagi dapat mengkloning penerima secara langsung tanpa memblokir dirinya sendiri dari aktivitas perdagangan.\n\n2. Kematian Ekonomi\nPembalikan Tren Perdagangan CS2 Selama 7 Hari (Juli 2025)\n\nValve memperkenalkan langkah sepihak Pembalikan Tren Perdagangan untuk item Counter-Strike. Setiap skin yang diperdagangkan akan diberi label \"Dilindungi Perdagangan\" selama tujuh hari. Jika korban menyadari adanya penggantian, mereka cukup mengklik \"Batalkan Pertukaran\" di Steam Dukungan, dan skin tersebut akan langsung dikembalikan ke inventaris mereka sekaligus membekukan akun penerima. Karena kunci pertukaran selama 7 hari mencegah penipu memindahkan item ke situs pencairan dana, pencurian tersebut menjadi tidak menguntungkan.\n\n3. Kematian \"Silent Key\"\nPemberitahuan Push Seluler Wajib untuk API (Desember 2023)\n\nSecara historis, cookie sesi yang dicuri memungkinkan skrip berbahaya untuk menjalankan permintaan POST latar belakang tanpa antarmuka pengguna ke /dev/ajaxregisterkey tanpa memberi tahu korban. Pada tanggal 4 Desember 2023, Valve mewajibkan konfirmasi push secara eksplisit di Aplikasi Seluler Steam untuk membuat kunci API Web, sehingga menghilangkan proses pembuatan kunci di latar belakang tanpa pemberitahuan.\n\n4. Peringatan Seluler dalam Aplikasi\nSpanduk Usia & Nama Akun (2022–2024)\n\nValve telah memperbarui jendela konfirmasi di perangkat seluler agar menampilkan informasi mitra perdagangan Steam masa berlaku akun (tanggal pembuatan), tingkat Steam, dan peringatan kuning yang jelas: \"Pengguna ini baru saja mengubah nama profilnya\", sehingga mengungkap ilusi visual tersebut bagi korban yang waspada.\n\nTiga Kelemahan dalam Karya Patchwork Valve: Mengapa Para Penipu Hanya Mengalihkan Sasaran\n1. Celah Pengecualian Game (Dota 2 & TF2)\n\nFitur \"Trade Reversals\" diterapkan secara eksklusif untuk Counter-Strike 2. Item-item Dota 2 dan Team Fortress 2 tetap sama sekali tidak terlindungi karena kerumitan proses pembuatan dan pemasangan permata. Item tingkat tinggi yang bernilai ribuan dolar (Dragonclaw Hooks, Golden Baby Roshans, Unusual TF2 burning flames) tidak memiliki jendela pembatalan sama sekali. Para penipu hanya mengalihkan intersepsi API otomatis ke para pedagang Dota 2 dan TF2, di mana Steam Support secara ketat menerapkan kebijakan “tidak ada pemulihan item” tahun 2016.\n\n2. Cadangan \"Zombie Key\" (Tanpa Batas Waktu)\n\nSementara Valve menambahkan otentikasi dua faktor (2FA) berbasis notifikasi push seluler untuk menghasilkan baru kunci pada bulan Desember 2023, Valve kunci API lama yang ada tidak pernah dicabut, kedaluwarsa, atau dihapus. Jutaan akun aktif yang telah menghasilkan kunci (atau yang kuncinya telah dibuat secara diam-diam oleh serangan phishing/malware sebelum Desember 2023) masih memiliki kredensial aktif dengan tanpa batas waktu kedaluwarsa (tanpa TTL) dan tanpa batas waktu inaktivitas. Para pelaku ancaman menyimpan basis data historis yang sangat besar berisi kunci-kunci yang bersifat persisten ini, dan terus melakukan polling IEconService tanpa gangguan.\n\n3. Sanksi bagi Korban: Pembekuan Perdagangan Selama 30 Hari\n\nBahkan di CS2, Valve memberikan sanksi kepada pemain yang menjadi korban penipuan: mengklik \"Reverse Trade\" di Steam Support secara otomatis akan memberikan larangan perdagangan dan akses ke Pasar Komunitas selama 30 hari yang bersifat wajib terhadap akun korban. Valve menjatuhkan sanksi berupa pemblokiran akses ke platform selama sebulan kepada pengguna sebagai upaya pencegahan terhadap pembatalan transaksi yang \"tidak beralasan\", guna mencegah korban membatalkan transaksi atas barang-barang likuid bernilai rendah.\n\nSkandal Regulasi Inti: Tujuh Tahun Menggunakan Jalan Pintas vs. Satu Ruang Lingkup API\n\nMengapa Valve menghabiskan tujuh tahun untuk menciptakan mekanisme pembatasan perdagangan, masa tunggu akun, dan penguncian perdagangan yang dapat dibatalkan—yang mengacaukan seluruh ekonomi dalam game dan menghapus $104M dari kapitalisasi pasar—alih-alih menerapkan solusi yang sudah menjadi standar industri?\n\nSebagaimana dibuktikan oleh rilis resmi Valve di Steamworks pada 16 Januari 2026 (Pengumuman #493839547938902179 ↗), Valve sudah dibangun Kelompok Izin Terperinci (Umum, Transaksi Mikro, Ekonomi, Data Penjualan) dan Daftar Putih IP untuk Kunci Penerbit korporat. Valve sudah memiliki solusi teknisnya selama bertahun-tahun. Sebuah kotak centang yang ditampilkan kepada pengguna—\"Cegah kunci API Web ini mengakses IEconService (Manajemen Perdagangan)\" atau daftar putih alamat IP rumah—akan dapat memberantas penipuan substitusi perdagangan pada tahun 2018 tanpa menimbulkan dampak ekonomi yang merugikan sama sekali. Valve menolak memberikan perlindungan yang dirancang khusus untuk mitra korporatnya kepada para pemain biasa.\n\nBagian B — Peraturan dan catatan penegakan · Pasal 9\nBuku pedoman mereka. Platform-platform yang tercatat.\nKonteks & batasan sumber\n\nBuku besar ini memetakan klausul-klausul eksplisit dari Steam Perjanjian Pelanggan (SSA) dan Steam Perilaku Daring (SOC) pedoman yang secara langsung ditujukan kepada entitas komersial yang aktif dan berskala besar.\n\nAturannya: tidak boleh digunakan untuk tujuan komersial, tidak boleh untuk perjudian, tidak boleh menggunakan bot — dan Steam Tim Dukungan mengutip klausul-klausul tersebut saat menolak mengembalikan barang milik korban. Catatan: Klausul-klausul yang sama, secara harfiah, mencakup platform-platform komersial dalam daftar ini, yang beroperasi berdasarkan Steam identitas, Steam bot, dan Steam transfer. Klausul tersebut diberlakukan terhadap pihak yang kehilangan kulit-kulit tersebut, dan—berdasarkan catatan resmi apa pun—bukan terhadap perusahaan-perusahaan yang mengangkutnya.\n\nDalam pengaduan yang telah diarsipkan, Steam Tim Dukungan menyebutkan bahwa \"Dilarang Digunakan untuk Tujuan Komersial\" dan \"Tidak Ada Otomatisasi/Bot\" ketentuan-ketentuan saat menolak mengembalikan barang kepada korban penipuan kunci API. Ketentuan-ketentuan yang sama berlaku secara harfiah bagi platform-platform komersial yang tercatat dalam berkas ini, yang melakukan otentikasi melalui Steam OpenID dan mentransfer barang melalui akun-akun otomatis Steam. Tidak ada perkiraan angka pendapatan secara keseluruhan di pasar yang disajikan di sini (lihat statistik penegakan hukum di bawah). Yang tercatat adalah penerapan aturan terhadap akun individu dalam kasus-kasus yang diarsipkan, dan tidak ada catatan penegakan hukum per operator yang dipublikasikan untuk platform-platform tersebut. Asimetri inilah yang didokumentasikan dalam bagian ini.\n\nPertanyaan utama / penegakan hukum yang selektifAturan → Skala → Akuntabilitas\nSatu buku peraturan. Penegakan yang tidak merata.\n\nDaftar tersebut menunjukkan bahwa layanan komersial menggunakan identitas Steam, inventaris, bot, dan transfer sebagai infrastruktur operasional. SSA melarang eksploitasi komersial dan otomatisasi tanpa izin. Pengaduan yang diarsipkan menunjukkan bahwa aturan tersebut diterapkan pada akun individu, sementara catatan publik tidak menunjukkan catatan serupa per operator untuk platform-platform yang didokumentasikan di sini. Publikasikan aturan, bukti, dan keputusan penegakan hukum untuk masing-masing kasus.\n\n189situs web yang termasuk dalam cakupan audit\n44rute domain terpisah dalam daftar aktif — 27 di antaranya disertai berkas bukti yang dipublikasikan, 17 lainnya dikumpulkan secara manual. Audit peramban terhadap 189 situs web saja telah menyelesaikan 25 di antaranya; daftar tersebut juga mencakup rute yang dikumpulkan secara manual.\n12 tahun 6 bulancsgogem.com diblokir di Filter Tautan; api.csgem.com terdaftar 2014-03-08 dan tidak pernah diblokir — salah satu dari 26 pasangan serupa per tanggal 2026-09-22\nTidak ada total yang terverifikasiperkiraan pendapatan di seluruh pasar tidak termasuk\nSteam Perilaku Saat Beraktivitas Online\n\"…Anda dilarang melakukan, atau berusaha melakukan, hal-hal berikut ini di Steam: […] Melakukan kegiatan komersial. Contoh perilaku terlarang tersebut antara lain: memposting iklan; menyelenggarakan kontes; perjudian; membeli atau menjual akun Steam; menjual konten, kartu hadiah, atau barang lainnya; serta mengemis.\"\n\nstore.steampowered.com/online_conduct ↗ diarsipkan 2026-09-21 ↗\n\nSSA § 2.G — Penggunaan komersial\n\"…[Anda tidak boleh] memanfaatkan Konten dan Layanan atau bagian mana pun darinya untuk tujuan komersial apa pun, kecuali sebagaimana secara tegas diizinkan di bagian lain dalam Perjanjian ini…\"\n\nPemberitahuan Valve tahun 2016, sebagaimana dilaporkan, mengacu pada lisensi pribadi dan non-komersial. Tidak ada operator yang menunjukkan izin Valve secara resmi. store.steampowered.com/subscriber_agreement ↗ diarsipkan 2026-09-18 ↗\n\nSteam Ketentuan Penggunaan Web API\n\"Anda dilarang menggunakan Steam Web API atau Steam Data dengan cara apa pun yang melanggar Steam Perjanjian Pelanggan.\"\n\nPasar skin pihak ketiga beroperasi melalui akun otomatis yang menggunakan API Steam. Teks aturan tersebut tidak memberikan pengecualian apa pun untuk skala komersial. steamcommunity.com/dev/apiterms ↗ diarsipkan 2026-09-21 ↗\n\nSSA Pasal 4.C\nOtomatisasi\n\nSkrip, bot, dan interaksi non-manusia dilarang. Buku besar mencatat aktivitas perdagangan bot, jaringan akun massal, dan pengalihan otomatis dalam skala komersial.\n\nPeriksa 153catatan yang diberi label berdasarkan klausul ini ↗\nApa yang tercantum dalam catatan berdasarkan klausul ini153 platform yang diberi tag\nPembukaan Perkara15\nSkin Casino13\nPasar CS29\nRoulette Kulit8\ncsgoempire.com→csgoempirelogin4.comKasino\nrollbit.com→rbsnin.comKasino Kripto\n500.casino→fivezerozero.coKasino Berlisensi\n\nDari jumlah tersebut, 153 juga diberi label berdasarkan SSA § 2.G dan 2 juga dikategorikan berdasarkan SSA § 1.C — layanan yang sama termasuk dalam lebih dari satu klausul, itulah sebabnya contoh-contoh tersebut terulang.\n\n28 dari 153 telah diamati melakukan otentikasi melalui domain terdaftar yang terpisah. Sebuah tag mencatat pengamatan bertanggal yang secara jelas menempatkan platform tersebut dalam ketentuan tersebut; hal ini bukanlah pelanggaran yang telah diputuskan, dan belum ada otorisasi Valve yang ditunjukkan untuk salah satu dari mereka.\n\nSSA Pasal 2.G\nPenggunaan komersial\n\nPemanfaatan komersial memerlukan izin tertulis. Bandingkan model bisnis yang terdokumentasi, skalanya, serta izin atau penegakan hukum yang diungkapkan.\n\nPeriksa 175catatan yang diberi label berdasarkan klausul ini ↗\nApa yang tercantum dalam catatan berdasarkan klausul ini175 platform yang diberi tag\nPembukaan Perkara15\nSkin Casino13\nPasar CS29\nRoulette Kulit8\ncsgoempire.com→csgoempirelogin4.comKasino\nrollbit.com→rbsnin.comKasino Kripto\n500.casino→fivezerozero.coKasino Berlisensi\n\nDari jumlah tersebut, 153 juga diberi label berdasarkan SSA § 4.C dan 24 juga dikategorikan berdasarkan SSA § 1.C — layanan yang sama termasuk dalam lebih dari satu klausul, itulah sebabnya contoh-contoh tersebut terulang.\n\n28 dari 175 teramati melakukan otentikasi melalui domain terdaftar yang terpisah. Sebuah tag mencatat pengamatan bertanggal yang secara jelas menempatkan platform tersebut dalam cakupan klausul tersebut; hal ini bukanlah pelanggaran yang telah diputuskan secara hukum, dan belum ada otorisasi Valve yang ditunjukkan untuk salah satu dari mereka.\n\nSSA Pasal 3.A\nVPN & penyamaran lokasi\n\nMenyembunyikan alamat IP tempat tinggal melalui proxy IP dapat mengakibatkan pemutusan layanan. Host otentikasi dengan domain terpisah memerlukan analisis tersendiri: tentukan apa yang disembunyikan dan aturan mana yang berlaku.\n\nPeriksa bukti auth-host ↗\nSteam Bantuan / Kebijakan URL\nPenyamaran tautan\n\nSteam melarang penggunaan layanan pemendek tautan dan alat yang menyembunyikan tujuan tautan. Domain otentikasi terpisah — rbsnin.com dalam alur masuk Rollbit, auth.dota.trade di CS.MONEY — memunculkan pertanyaan serupa mengenai apakah tujuan yang ditampilkan kepada verifikator OpenID milik Steam mengidentifikasi situs yang sedang beroperasi.\n\nKebijakan URL Valve ↗\n\nReferensi peraturan: Steam Perjanjian Pelanggan, revisi 10 September 2026 diarsipkan 2026-09-18 ↗ · Steam Ketentuan Penggunaan Web API diarsipkan 2026-09-21 ↗ · Steam Kebijakan URL (penyamaran tautan). Angka-angka tersebut menggambarkan catatan dan tag dalam berkas ini; angka-angka tersebut bukanlah jumlah pelanggaran yang telah diputuskan.\n\nKekurangan kepercayaan\nSiapa yang meninjau keputusan tersebut ketika tim dukungan menutup kasus tersebut?\n\nKeluhan-keluhan yang tersimpan tersebut menggambarkan sanksi permanen, keberatan yang tidak ditanggapi, dan penolakan untuk mengembalikan barang-barang yang dicuri. Bandingkan laporan-laporan tersebut dengan riwayat tiket yang sebenarnya, upaya penyelesaian yang tersedia, dan catatan akses akun. Penjelasan umum terkait phishing tidak dapat membuktikan siapa yang memicu proses reset atau membuat kunci API.\n\nBaca keluhan yang telah direkam ↗Minta catatan yang mendasari →Grafik hubungan moderator →\nBagian B — Peraturan dan catatan penegakan · Pasal 10\nSebuah API otomatisasi. Sebuah aturan yang melarang otomatisasi.\nKonteks & batasan sumber\n\nPertanyaan yang diajukan dalam bagian ini adalah bagaimana kedua hal tersebut dapat diselaraskan: penggunaan API mana saja yang diizinkan, oleh siapa, dan berdasarkan kriteria apa yang telah dipublikasikan. Tidak ada perkiraan jumlah pengguna API komersial yang diizinkan di sini, dan hal tersebut juga tidak tersirat dari tidak adanya daftar yang dipublikasikan — ketiadaan daftar itulah yang menjadi temuan, bukan angka di baliknya. Pesan dukungan Steam yang dikutip di atas disalin oleh proyek ArchiSteamFarm dalam FAQ-nya sendiri (diverifikasi secara verbatim 2026-09-22); pesan-pesan tersebut bukanlah Valve publikasi, dan akun-akun yang menerimanya tidak diidentifikasi.\n\nAturan (SSA § 4.C): tidak ada skrip, tidak ada bot, tidak ada sistem non-manusia di Steam. Catatan: Valve menyediakan REST API tanpa antarmuka pengguna yang sepenuhnya ditujukan untuk otomatisasi antar-server, dan memberikan kunci akses ke akun mana pun. Pengguna diblokir karena menggunakan otomatisasi; antarmuka otomatisasi tersebut merupakan produk milik Valve sendiri. Penggunaan komersial apa saja yang diizinkan belum pernah diumumkan.\n\nKesalahpahaman tentang \"Pengembang Game\"\nSteamworks SDK (Asli)\n\nDigunakan oleh studio game resmi untuk mengintegrasikan pencapaian, pencocokan pemain, dan papan peringkat ke dalam klien game mereka. Membutuhkan integrasi C++ yang rumit serta proses pendaftaran mitra resmi.\n\nSteam Web API (Celah)\n\nArsitektur JSON/REST tanpa header yang dirancang untuk server web eksternal. Dalam pola \"hijack\" yang didokumentasikan di sini, arsitektur ini digunakan untuk membaca inventaris dan memanipulasi transaksi peer-to-peer dari server jarak jauh; penggunaan sahnya tidak tercantum dalam dokumen ini.\n\nUntuk siapa kunci itu?Pengguna biasa Steam tidak memerlukan kunci Web API di dalam aplikasi; halaman kunci tersebut terletak di bawah URL pengembang dan tujuan yang tercantum dalam dokumentasinya adalah untuk akses eksternal di sisi server. Keluhan-keluhan terkait pembajakan yang telah diarsipkan menggambarkan para korban yang tidak mengetahui keberadaan halaman tersebut hingga kunci telah terdaftar di akun mereka.\nKontradiksi Otomatisasi\n\nSSA § 4.C berbunyi: \"Anda dilarang menggunakan skrip, bot, makro, atau sistem lain yang tidak dikendalikan oleh manusia ('Otomatisasi') dalam bentuk apa pun untuk berinteraksi dengan Konten dan Layanan di Steam dengan cara apa pun.\" Namun, titik akhir Web API (seperti CancelTradeOffer) tidak memerlukan antarmuka pengguna (UI) dan tidak memerlukan captcha, serta sepenuhnya melewati klien Steam. API ini dirancang untuk otomatisasi antar-server; aturan tersebut melarang otomatisasi oleh pengguna; batas antara keduanya tidak diumumkan.\n\nPosisi di sisi server dalam alur perdagangan\n\nKunci API Web memungkinkan server pihak ketiga melakukan transaksi atas nama akun tersebut tanpa melibatkan klien Steam. Dalam skema penyusupan, server tersebut berada di antara pemilik akun dan server transaksi.\n\n→Tidak ada layar konfirmasi transaksi yang ditampilkan untuk tindakan yang dilakukan oleh kunci tersebut.\n→Mengaktifkan polling latar belakang (GetTradeOffers).\n→Membatalkan dan menerbitkan kembali penawaran tanpa keterlibatan pengguna.\nValve telah mengembangkan antarmuka tersebut, melarang otomatisasi oleh pengguna dalam aturannya, dan belum menerbitkan kriteria mengenai penggunaan komersial apa saja yang diizinkan.\nBagian B — Peraturan dan catatan penegakan hukum · Pasal 11\nDiminta sepuluh hari. Harus mempertanggungjawabkan sepuluh tahun.\nKonteks & batasan sumber\n\nPada 20 Juli 2016, penasihat hukum Valve memberikan batas waktu 10 hari kepada para operator perjudian. Sepuluh tahun kemudian (berdasarkan cuplikan berkas, 2026-09-21), setidaknya satu platform yang disebutkan dalam laporan media terkait pemberitahuan tersebut, yaitu CSGOFast, masih beroperasi dengan host otentikasi domain terpisah. Kata-kata dalam pemberitahuan tersebut direkonstruksi di bawah ini berdasarkan laporan media tanggal 21 Juli 2016; rekonstruksi ini bukanlah hasil pindaian. Catatan penegakan hukum yang disiratkan dalam pemberitahuan tersebut belum dipublikasikan. Surat terbuka kepada Komisi tersebut adalah Bagian 2.\n\nSilakan baca pemberitahuan bulan Juli 2016 yang tercantum di samping catatan-catatan selanjutnya. Hal yang masih menjadi perhatian adalah catatan penegakan hukum per operator.\n\nSatu minggu sebelumnya — 13 Juli 2016, di hadapan publik\n\nPada 13 Juli 2016 diarsipkan 2026-09-21 ↗, Valve menjelaskan bagaimana situs perjudian menggunakan Steam: OpenID untuk identifikasi akun dan akun otomatis untuk transaksi. Valve menyatakan bahwa penggunaan mekanisme tersebut untuk menjalankan bisnis perjudian melanggar ketentuan API dan perjanjian pengguna. Baik penjelasan mengenai mekanisme tersebut maupun larangan tersebut tercantum dalam pernyataan Valve yang bertanggal. Pada 2026-09-21, host otentikasi domain terpisah yang diuji tidak menunjukkan adanya pemblokiran Filter Tautan, dan Valve belum menerbitkan catatan penegakan per operator.\n\nLAMPIRAN A / JULI 2016REKONSTRUKSI TATA TULIS\nVALVE CORPORATION\n\nBellevue, WA\n\nTANGGAL:Juli 2016 (dilaporkan oleh media pada 21 Juli 2016)\nDARI:Karl Quackenbush, Penasihat Hukum Utama\nRE:Peringatan untuk menghentikan — penggunaan akun Steam untuk tujuan komersial\nCATATAN:Rekonstruksi teks yang dilaporkan; bukan hasil pindaian\n\n\"Kami mengetahui bahwa Anda mengoperasikan salah satu situs perjudian yang tercantum di bawah ini. Anda menggunakan Steam akun untuk menjalankan bisnis ini. Berdasarkan Perjanjian Pelanggan Steam, layanan Steam dan Steam hanya dilisensikan untuk penggunaan pribadi dan non-komersial.\"\n\n\"Anda harus segera menghentikan dan tidak lagi menggunakan akun-akun Steam Anda untuk tujuan komersial apa pun. Jika Anda tidak melakukannya, dalam waktu sepuluh (10) hari, Valve akan mengambil semua langkah hukum yang tersedia, termasuk namun tidak terbatas pada penutupan akun-akun Anda.\"\n\nRekonstruksi berkas · lihat catatan sumber\nKarl Quackenbush\nPenasihat Hukum Utama, Valve Corp.\nDI SISI HALAMAN / OPINI\nSepuluh hari.Lalu bagaimana?\n\nBatas waktunya sudah ditentukan dengan jelas. Tindakan lanjutan dari masyarakat pun seharusnya demikian.\n\nPernyataan resmi Valve mengenai “2016” ↗\nCatatan mengenai batas waktu +\nSATIRE / BUKAN SURAT KEPADA VALVE\n\nWahai tenggat waktu,\n\nKamu diberi waktu sepuluh hari. Entah bagaimana, kalender itulah satu-satunya yang tetap berfungsi.\n\nMohon sampaikan balasan apa pun ke arsip publik.\n\nGaris WaktuJuli 2016 – September 2026\nBatas waktu yang tercantum dalam pengumuman:\n10 Hari\nJuli 2016\nWaktu yang telah berlalu sejak pemberitahuan:\n3,715 Hari\nJumlah tetap dari tanggal 20 Juli 2016 hingga cuplikan data pada tanggal 21 September 2026, bukan angka aktual\nCatatan penegakan hukum yang dipublikasikan:\nTidak ada\nTidak ditemukan catatan per operator mengenai pemutusan atau pemblokiran\n\n◀ Hari 0–10 — batas waktu, untuk disesuaikanHari ke-3715 — cuplikan ▶\n\n20 Juli 2016Perintah sepuluh hari telah dikeluarkanHari ke-0\n17 Februari 2024Kewajiban DSA berlakuHari 2,768\n25 Februari 2026Pengumuman pengaduan Jaksa Agung New YorkHari 3,507\n21 September 2026Gambaran umum berkasHari ke-3715\n\nSepuluh tahun kemudian, CSGOFast — yang disebutkan dalam laporan media mengenai pemberitahuan tahun 2016 — sudah beroperasi: csgofast.com menampilkan pemblokiran Link Filter pada 2026-09-19 dan 2026-09-21, sedangkan host otentikasinya steam-login.authtofast.com (terdaftar 2026-06-30) tidak melakukannya.\n\nCatatan lengkap berstempel tanggal mengenai perubahan keamanan Valve: Garis Waktu Keamanan → · Catatan Washington dan standar penegakan hukum: di bawah ini\n\nFakta yang tercatat: Pemberitahuan tahun 2016 menetapkan batas waktu 10 hari; Valve telah mengoperasikan daftar domain (Link Filter) dan menerima nama host otorisasi dalam permintaan OpenID-nya sendiri; belum ada catatan penegakan hukum per operator yang dipublikasikan. Laporan komunitas menggambarkan tindakan pada tahun 2018 terhadap sebuah pasar daring (SkinJar), namun laporan-laporan tersebut belum diverifikasi dan tidak dijadikan acuan di sini.\nCSGOFAST / RUTE OTENTIKASI YANG DISIMPAN\nIkuti host pengembalian yang dinyatakan.\n\nTautan catatan rute yang telah disimpan csgofast.com ke steam-login.authtofast.com. Nama host terpisah tersebut tercantum dalam permintaan OpenID Steam. Hal ini memberikan para penyelidik alamat yang spesifik untuk dibandingkan dengan catatan penyaringan dan penegakan aturan dari Valve.\n\nPeriksa rute CSGOFast dan sumbernya ↗ · Bandingkan hasil yang disimpan Steam Saring tautan ↗\n\nCATATAN UMUM / WASHINGTON · 2016 → 2026\nDua batas waktu. Satu standar penegakan hukum yang belum dijelaskan.\n20 JULI\nValve memberikan waktu 10 hari kepada situs perjudian\n\nPihak kuasa hukumnya memperingatkan bahwa penggunaan akun Steam untuk tujuan komersial secara terus-menerus dapat mengakibatkan penutupan akun.\n\n27 SEP\nWashington menekan Valve\n\nKomisi Perjudian negara bagian tersebut meminta bukti langkah-langkah yang diambil untuk menghentikan transfer skin untuk keperluan perjudian dan menetapkan batas waktu tanggapan hingga 14 Oktober.\n\n17 OKT\nValve membantah tuduhan tersebut\n\nValve memberikan tanggapan setelah batas waktu berlalu, membantah tuduhan bahwa platform tersebut memfasilitasi perjudian, menyatakan telah menonaktifkan akun-akun yang terkait, dan mengatakan tidak ingin menonaktifkan layanan perdagangan dan OpenID bagi semua pengguna. Setidaknya satu platform yang disebutkan dalam laporan pers mengenai pemberitahuan bulan Juli (CSGOFast) masih beroperasi sepuluh tahun kemudian. Kedua fakta tersebut hanya dapat berlaku jika operator mengganti akun-akun yang dinonaktifkan; catatan yang menunjukkan hal ini belum dipublikasikan. WSGC sebaiknya meminta Valve untuk menyelaraskan kedua hal tersebut.\n\n2026\nRute-rute yang diamati pada bulan September 2026\n\nDaftar rute mencatat 44 platform yang melakukan otentikasi melalui host otentikasi domain terpisah, termasuk CSGOFast, dengan menggunakan OpenID dan mekanisme perdagangan Valve yang dijelaskan pada tahun 2016. Catatan penegakan yang seharusnya menunjukkan operator mana saja yang diputus aksesnya belum dirilis.\n\nPAPARAN DARI KOMISI SENDIRI · 30 JANUARI 2018\nDelapan belas bulan setelah Valve memberikan tanggapan, otoritas pengawas masih menyebutnya sebagai niat.\n\nDalam audiensi publik RUU HB 2881, Komisi tersebut menjelaskan pernyataan bulan Juli 2016 dengan kata-katanya sendiri kepada badan legislatifnya: Valve \"mengumumkan niatnya untuk menindak penggunaan platformnya yang memfasilitasi perjudian skin.\" Halaman yang sama mencatat dampak pengumuman tersebut terhadap proyeksi industri — \"sehingga,\" proyeksi pasar perjudian online tahun 2020 telah direvisi dari $19.7 miliar ke $670 juta, penurunan sekitar 97 persen, hanya berdasarkan pengumuman tersebut saja. Perkiraan tersebut berubah. Data penegakan hukum per operator yang dapat menjadi dasar keputusan tersebut masih belum dipublikasikan.\n\nAngka-angka pasar tersebut merupakan perkiraan dari Narus Advisors / Eilers & Krejcik Gaming yang dikutip dalam briefing Komisi, bukan temuan Komisi; dokumen yang sama menyebutkan bahwa nilai taruhan skin pada tahun 2016 mencapai sekitar $5 miliar, dengan sekitar $3 miliar di antaranya terjadi di situs-situs bergaya kasino. Diambil pada 2026-09-22, SHA-256 c507c9025f93da0aadaf395c4d8882f25973211c318ee8e9b6f18a5b3755e050.\n\nPosisi resmi Valve pada tahun 2016 dan infrastruktur yang dapat diamati saat ini dapat dibandingkan secara berdampingan. Pertanyaannya adalah apakah penegakan hukum telah menjangkau akun dan rute yang digunakan oleh operator yang dilarang. Pemberitahuan sepuluh hari bukanlah bukti bahwa pemberitahuan tersebut telah disampaikan kepada seluruh operator yang disebutkan di dalamnya. Tindakan OPSkins tahun 2018 merupakan satu-satunya intervensi yang tercatat terhadap seorang operator tertentu; mengingat ada 189 platform yang diperiksa dan tidak ada catatan per operator yang dipublikasikan, satu tindakan yang tercatat tersebut tidak menunjukkan pola penegakan hukum.\n\nPengumuman Komisi Perjudian Washington tahun 2016 ↗ diarsipkan 2026-05-20 ↗ · Tanggapan Valve tanggal 17 Oktober 2016 (salinan dokumen) ↗ · Sesi paparan WSGC kepada badan legislatif, 30 Januari 2018 (salinan lokal, 4 halaman) ↗ · file yang sama di wsgc.wa.gov ↗ · catatan pengambilan & hash ↗ · Aksi OPSkins Valve tahun 2018 ↗ diarsipkan 2026-03-07 ↗ · Audit rute saat ini ↗\n\nAudit Forensik Longitudinal · Target Perintah Penghentian dan Larangan Tahun 2016\nDekade Pemberitahuan 10 Hari: Audit Kelangsungan Hidup Forensik di 23 Lokasi yang Disebutkan\n\nPada tanggal 19–20 Juli 2016, Valve Penasihat Hukum Utama Karl Quackenbush mengeluarkan surat peringatan resmi untuk menghentikan kegiatan kepada 23 platform perjudian skin, memerintahkan mereka untuk menghentikan penggunaan komersial atas Steam akun di dalam 10 hari di bawah ancaman penutupan akun dan tindakan hukum. Lebih dari 3,700 hari kemudian, audit empiris mengungkap pola penegakan aturan yang sebenarnya: sejumlah operator tidak pernah menghentikan operasinya, sementara yang lain tetap beroperasi hingga enam tahun setelah batas waktu, dan ekosistem bernilai miliaran dolar tersebut terus memanfaatkan arsitektur OpenID Valve.\n\n5+ LANGSUNG\nDipastikan akan beroperasi pada tahun 2026 (CSGOBig, CSGO500, CSGOFast, dll.)\n6 TAHUN\nJangka waktu terlama sejak pemberitahuan hingga penutupan (CSGOatse tetap aktif hingga tahun 2022)\n$5.01B\nVolume taruhan kulit tahun 2016 (Narus / Eilers & Krejcik)\n200+\nSitus perjudian online yang aktif beroperasi pada puncak pasar\nThe Surviving Titans · Peta Jalan Keuangan & Lalu Lintas 2024–2026\nDari Peringatan 10 Hari hingga Konglomerat Luar Negeri: Perputaran Dana Senilai Miliaran Dolar\n\nAlih-alih memberantas perjudian skin, pemberitahuan Valve pada tahun 2016 justru memicu evolusi industri. Operator yang masih bertahan melakukan restrukturisasi menjadi entitas korporasi lepas pantai (Curaçao, Belize, Siprus), memelopori perdagangan Peer-to-Peer (P2P) untuk menghindari larangan bot, dan kini memproses lebih dari 10 juta kunjungan situs web per bulan dan miliaran dolar dalam total taruhan tahunan sambil tetap melakukan otentikasi melalui Steam:\n\nPlatform / Domain\tPengumuman Juli 2016\tHasil Penegakan Hukum & Status Kelangsungan Hidup\tVerifikasi yang Tercatat / Tautan Utama\nCSGOBig\ncsgobig.com\tPemberitahuan 10 Hari (Juli 2016)\tMASIH HIDUP DI TAHUN 2026\nUntuk sementara dihentikan, kemudian diluncurkan kembali; otentikasi dilakukan melalui letmeinbig.com & csgobiglogin.com\tX: @csgobig ↗ · FB: csgobigofficial ↗\nCSGO500\ncsgo500.com / 500.casino\tPemberitahuan 10 Hari (Juli 2016)\tMASIH HIDUP PADA TAHUN 2026\nBerganti nama menjadi 500 Casino (lisensi Curaçao No. 8048/JAZ2014-037), dengan omzet bulanan mencapai jutaan\tPlatform Langsung (500.casino) ↗\nCSGOFast\ncsgofast.com\tPemberitahuan 10 Hari (Juli 2016)\tMASIH HIDUP PADA TAHUN 2026\nSaat ini sedang mengoperasikan permainan roulette, crash, dan jackpot melalui steam-login.authtofast.com\tDokumen Audit Otorisasi ↗\nCSGOLounge / Dota2Lounge\ncsgolounge.com / dota2lounge.com\tPemberitahuan 10 Hari (Juli 2016)\tMASIH HIDUP PADA TAHUN 2026\nBeralih ke taruhan koin esports dan taruhan kripto; tetap beroperasi secara berkelanjutan\tPlatform Langsung ↗\nCSGOCasino\ncsgocasino.net / csgocasino.gg\tPemberitahuan 10 Hari (Juli 2016)\tSIARAN LANGSUNG MELALUI SUCCESSOR (2026)\nDomain telah dialihkan; portal pengganti yang aktif beroperasi di bawah csgocasino.gg\tDomain Penerus ↗\nCSGOatse\ncsgoatse.com\tPemberitahuan 10 Hari (Juli 2016)\tBERTAHAN SELAMA 6 TAHUN (AKTIF HINGGA TAHUN 2022)\nOperasi perjudian tetap berjalan penuh selama enam tahun setelah ultimatum 10 hari dari Valve\tX: @CSGOatsecom (Aktif hingga 2022) ↗\nCSGOSweep\ncsgosweep.com\tPemberitahuan 10 Hari (Juli 2016)\tBERLANJUT HINGGA DESEMBER 2017\nBeroperasi secara terbuka selama 17 bulan setelah batas waktu\tX: Status CSGOSweep Desember 2017 ↗\nCSGOWild\ncsgowild.com\tPemberitahuan 10 Hari (Juli 2016)\tBERLANJUT HINGGA DESEMBER 2017\nDipromosikan oleh para influencer ternama; beroperasi selama 1,5 tahun setelah surat peringatan (C&D) sebelum beralih ke kripto\tX: @Wild (Aktif pada Desember 2017) ↗\nCSGOPot\ncsgopot.com\tPemberitahuan 10 Hari (Juli 2016)\tBERTAHAN HIDUP HINGGA SEPTEMBER 2017\nMengoperasikan taruhan jackpot dengan taruhan tinggi selama 14 bulan setelah pemberitahuan\tX: @csgopot (Aktif pada September 2017) ↗\nCSGODiamonds\ncsgodiamonds.com\tPemberitahuan 10 Hari (Juli 2016)\tBERTAHAN HINGGA PERTENGAHAN TAHUN 2017\nAcara tersebut tetap berlangsung sepanjang tahun 2017 meskipun telah diakui adanya manipulasi hasil untuk para streamer yang disponsori\tX: @csgodiamondscom (2017) ↗\nCSGOLotto\ncsgolotto.com\tPemberitahuan 10 Hari (Juli 2016)\tTUTUP PADA JULI 2016\nDitutup akibat skandal publik; menjadi sasaran perintah persetujuan dari Komisi Perdagangan Federal (FTC)\tPerintah Kesepakatan FTC (Nomor Perkara C-4632) ↗\nCSGODouble\ncsgodouble.com\tPemberitahuan 10 Hari (Juli 2016)\tTUTUP PADA JULI 2016\nSegera hentikan operasi secara sukarela setelah penerbitan surat peringatan dan tuntutan (C&D)\tX: @CSGODouble (Ditutup pada Juli 2016) ↗\nCSGOMassive\ncsgomassive.com\tPemberitahuan 10 Hari (Juli 2016)\tTUTUP 2016\nMenghentikan operasi publik pada akhir tahun 2016\tX: @csgo_massive ↗\nCSGOStrong\ncsgostrong.com\tPemberitahuan 10 Hari (Juli 2016)\tTUTUP 2016\nMenghentikan operasi publik pada tahun 2016\tFB: csgostrongfree ↗\nSkins2\nskins2.com\tPemberitahuan 10 Hari (Juli 2016)\tTUTUP 2016\nMenghentikan operasi untuk umum pada tahun 2016\tFB: CSNCOM ↗\n\nPlatform\tLalu Lintas Bulanan (Kunjungan)\tPerkiraan Omset / Volume\tBadan Hukum & Yurisdiksi\tTindakan Regulasi Utama & Model\nCSGOEmpire\ncsgoempire.com\t2,3 juta — 9,0 juta per bulan\nDurasi rata-rata 6+ menit; 80% langsung\t$1.5B — $2.5B Total Transaksi Tahunan\n>1,000,000 Transaksi skin P2P per bulan; $6.4M volume pesanan aktif yang likuid\tMoonrail Limited B.V. (Curaçao No. 148182)\nPembayaran: JHOLT LTD (Siprus); Pendiri: \"Monarch\" (Ossi Ketola)\tPelopor perdagangan barang P2P tanpa biaya; berlisensi Curaçao OGL/2024/1183/0869\nCSGORoll\ncsgoroll.com\t2,74 juta — 3,5 juta / bulan\nDurasi rata-rata 9 menit 23 detik; tingkat pentalan 16%\t$1.0B — $2.0B Total Transaksi Tahunan\nPerkiraan pendapatan tahunan perusahaan sebesar $100M–$200M dari keunggulan rumah\tFeral Holdings Limited\nBerkantor pusat di Kota Belize, Belize (Nomor Registrasi #171519)\tDilarang oleh ACMA Australia (Mei 2023); mensponsori tim tier-1 G2 Esports yang memiliki pemain di bawah umur\n500 Casino (CSGO500)\n500.casino / csgo500.com\t220 ribu — 425 ribu / bulan\n~105 ribu pengunjung unik per bulan\t$100k / minggu ($5.2M/tahun) di Royales\nPersyaratan taruhan untuk pemain besar: $400 taruhan per $1 rakeback\tPerfect Storm B.V. (Curaçao No. 150536)\nIzin dari Badan Pengawas Perjudian Curaçao OGL/2024/1354/0882\tDilarang oleh Spelinspektionen Swedia (November 2023) karena menargetkan pemain Swedia tanpa izin\nCSGOBig\ncsgobig.com\t~169,600 / bulan\nDurasi rata-rata 19 menit 12 detik; Pemilihan pendahuluan AS\tVolume Tahunan Berjumlah Beberapa Juta\nKotak misteri, roulette, dan pertarungan kotak\tBeroperasi melalui perutean proxy tambahan\nletmeinbig.com (terdaftar tahun 2023) & csgobiglogin.com\tTarget C&D Juli 2016 diluncurkan kembali dengan arsitektur otentikasi proxy\nCSGOFast\ncsgofast.com\t~150 ribu — 250 ribu per bulan\nPemirsa multibahasa di seluruh dunia\tVolume Tahunan Berjumlah Beberapa Juta\nPermainan roulette berkecepatan tinggi dan permainan crash\tEntitas operasional lepas pantai\nRute Steam otentikasi melalui steam-login.authtofast.com\tTarget Juli 2016 C&D; tidak pernah menghentikan operasinya; masih beroperasi pada tahun 2026\nCSGO Polygon\ncsgopolygon.com / plg.bet\t~300 ribu — 500 ribu per bulan\nDominasi Negara-Negara CIS dan Eropa Timur\tVolume Tahunan Berjumlah Beberapa Juta\nRoulette kripto & skin, taruhan pertandingan\tTarget gelombang kedua (Oktober 2016)\nBeralih ke mata uang kripto dengan domain cermin plg.bet\tTelah bertahan selama satu dekade penuh; terus melakukan likuidasi skin melalui API pihak ketiga\nGelombang Kedua: Mengapa Surat Peringatan dan Perintah Penghentian (C&D) dari Valve Menargetkan Sebanyak 43+ Situs\n\nPada tanggal 17 Oktober 2016, penasihat hukum Valve secara resmi memberitahukan kepada Komisi Perjudian Negara Bagian Washington bahwa setelah 23 pemberitahuan awal pada tanggal 19 Juli, Valve telah mengirimkan surat peringatan untuk menghentikan kegiatan kepada lebih dari 20 situs perjudian skin lainnya (sehingga jumlah resmi kini melampaui 43). Gelombang kedua ini terpaksa dilakukan karena daftar awal secara tak dapat dijelaskan tidak mencantumkan pusat-pusat perjudian terbesar dan paling terkenal di dunia:\n\nCSGOJackpot.com: Pelopor bersejarah di balik skema penipuan “skin jackpots”, yang pernah menangani transaksi senilai ratusan juta sebelum akhirnya tutup karena terancam dakwaan federal.\nCSGOShuffle.com: Situs yang menjadi pusat skandal siaran langsung pada Juli 2016, di mana streamer Twitch PhantomL0rd secara diam-diam memiliki 33% saham perusahaan tersebut dan terungkap telah memanipulasi peluang taruhan menggunakan dana perusahaan.\nEkosistem Makro (200+ Operator): Menurut penelitian industri yang dilakukan oleh Narus Advisors dan Eilers & Krejcik Gaming, lebih dari 200 situs perjudian skin yang berbeda beroperasi pada tahun 2016, menghasilkan $5.01 miliar dalam volume taruhan dari 3,03 juta pemain aktif. 43 surat dari Valve hanya mencakup kurang dari 20% dari pasar aktif.\nPenyelidikan Resmi oleh Pemerintah dan Otoritas Pengawas Terkait Steam Perjudian Skin\n\nFenomena perjudian ilegal telah didokumentasikan dalam berbagai penyelidikan resmi berdasarkan undang-undang, tindakan penegakan hukum, dan makalah posisi pemerintah:\n\n1. Komisi Perjudian Negara Bagian Washington (WSGC) (2016–2018)\n\nMenyampaikan surat peringatan resmi untuk menghentikan kegiatan (Cease & Desist) pada tanggal 5 Oktober 2016; menerbitkan Laporan Legislatif pada tanggal 30 Januari 2018 yang mendokumentasikan bahwa skin merupakan setara uang tunai serta melaporkan volume taruhan skin sebesar $5.0B.\n\nLaporan Legislatif WSGC dalam format PDF (Salinan Lokal) ↗\n2. Komisi Perdagangan Federal Amerika Serikat (FTC) (September 2017, Nomor Perkara C-4632)\n\nTindakan penegakan peraturan federal pertama yang melibatkan perjudian skin terhadap pemilik CSGOLotto, Trevor Martin dan Thomas Cassell, atas praktik-praktik menipu dan pengendalian platform yang tidak diungkapkan.\n\nKeputusan dan Perintah Persetujuan FTC ↗\n3. Makalah Posisi Komisi Perjudian Inggris (UKGC) & Audit Terkait Remaja\n\nSkin dalam game secara resmi diklasifikasikan sebagai \"uang atau sesuatu yang setara dengan uang\" berdasarkan Undang-Undang Perjudian Tahun 2005. Survei-survei selanjutnya menemukan bahwa lebih dari 11% anak berusia 11–16 tahun pernah bertaruh menggunakan skin dalam video game.\n\nRepositori Penelitian UKGC ↗\n4. Penyelidikan Senat Australia tentang Lingkungan dan Komunikasi (2018)\n\nLaporan Parlemen Federal mengenai \"Transaksi mikro dalam game untuk item yang diperoleh secara acak\", mengevaluasi mekanisme loot box Valve, pencairan dana di pasar sekunder, dan upaya menghindari peraturan.\n\nPenyelidikan Parlemen Australia ↗\nPermintaan yang belum terpenuhi\n\nPublikasikan catatan penegakan hukum: akun perjudian dan bot mana saja yang dinonaktifkan, host pengembalian mana saja yang diblokir, serta layanan komersial mana saja yang mendapat izin. Larangan yang diumumkan secara publik dan peringatan di laman beranda tidak menjamin bahwa operasi yang mendasarinya telah dihentikan.\n\nBagian B — Peraturan dan catatan penegakan · Pasal 12\nNama host sudah tercantum dalam permintaan.\nKonteks & batasan sumber\n\nValve sudah memiliki daftar domain (Link Filter) dan sudah menerima nama host otentikasi dalam setiap permintaan OpenID. Pseudokode di bawah ini menunjukkan alur logis untuk menghubungkan keduanya. Tidak ada bukti publik yang menunjukkan bahwa Valve melakukannya.\n\nValve sudah mengelola daftar blokir domain. Valve sudah menerima informasi host login dalam setiap permintaan OpenID. Tidak perlu membangun apa pun — keduanya hanya perlu disatukan. Itu adalah pencarian nama host berdasarkan daftar yang dikelola sendiri oleh Valve. Pseudokode di bawah ini hanyalah ilustrasi, bukan implementasi dari Valve.\n\nforensic_autoban.py\n# KODE PSEUDO ILUSTRATIF — Valve.block_domain() dan flag_session_as_mitm() bukanlah panggilan API yang sebenarnya. Ini menunjukkan struktur logis dari mitigasi yang dapat diterapkan Valve terhadap domain otentikasi proxy, bukan bagian internal Valve yang sebenarnya.\n# Ilustrasi: bentuk logis dari pemeriksaan terhadap permintaan OpenID yang masuk\ndef audit_openid_request(permintaan):\nblocked_origins = database.get_platform_yang_masuk_daftar_hitam()\nproxy_domain = request.params.dapatkan('openid.realm')\ntarget_redirect = request.params.dapatkan('openid.return_to')\n\n# Logika: Jika proxy tersebut mengarahkan kembali ke situs yang diblokir, blokir proxy tersebut.\nuntuk situs di blocked_origins:\njika situs di target_redirect:\nValve.block_domain(proxy_domain)\nValve.menandai_sesi_sebagai_MITM(request.session)\n# Hasil: Permintaan masuk untuk host tersebut ditolak\n\nPengamatan:\nApabila domain utama sudah terdaftar di Filter Tautan (misalnya howl.gg, diblokir 2026-09-18/19/21) dan host otentikasinya (howl.uno) muncul dalam permintaan OpenID dari tombol masuk situs tersebut, hubungan tersebut dapat diamati oleh Valve dari data permintaannya sendiri. Pemeriksaan ini dapat diotomatisasi; namun, apakah pemeriksaan tersebut dijalankan atau tidak, tidak dapat diotomatisasi.\nPreseden yang terdokumentasi dan dilaporkan\n\nValve tercatat telah mengambil tindakan terhadap operator pihak ketiga setidaknya sekali: pada tahun 2018, mereka mencabut akses OPSkins ke sistem ExpressTrade (Pengumuman Valve ↗ diarsipkan 2026-03-07 ↗). Laporan-laporan dari komunitas pada tahun 2018 juga menyebutkan bahwa sebuah pasar daring (SkinJar) kehilangan akses; laporan-laporan tersebut belum terverifikasi, dan mekanismenya disimpulkan berdasarkan hasilnya, bukan berdasarkan proses yang diungkapkan.\n\nApa yang ditetapkan oleh preseden tersebut:\n\nValve dapat memutus akses operator pihak ketiga kapan pun mereka mau. CSGOFast, yang disebutkan dalam laporan pers mengenai pemberitahuan pada Juli 2016, beroperasi di 2026-09-21 dengan host otorisasi yang terdaftar di 2026-06-30 yang tidak memicu pemblokiran Link Filter. Alasan mengapa satu operator diblokir sementara yang lain tidak, tidak dijelaskan dalam kriteria apa pun yang dipublikasikan.\n\nApa saja yang ditunjukkan dan tidak ditunjukkan oleh tanggal pendaftaran\n\nTanggal pendaftaran sebuah host otentikasi merupakan batas bawah mengenai kapan host tersebut pertama kali dapat muncul dalam permintaan OpenID; hal ini tidak menunjukkan adanya penggunaan yang berkelanjutan. sc-auth.net, misalnya, terdaftar dengan kode 2019-04-02 (RDAP) dan terdeteksi dalam alur masuk Steam di Skin.Club pada September 2026; apa yang terjadi antara kedua tanggal tersebut tidak tercatat dalam catatan publik.\n\nAudit Komparatif: Standar Kepatuhan API\nDimensi Penegakan Hukum\tAturan API GitHub\tSteam Antarmuka Pemrograman Aplikasi Web (Valve)\n1. Netralitas Kepatuhan\tAturan yang telah dipublikasikan dan seragam. Batas frekuensi yang terdokumentasi (misalnya 5,000 panggilan/jam untuk pengguna yang terautentikasi, 15,000/jam untuk organisasi GitHub Enterprise Cloud) serta kebijakan penggunaan yang dapat diterima yang telah dipublikasikan berlaku untuk setiap akun.\tTidak ada kriteria yang dipublikasikan. Akun-akun individu ditutup berdasarkan klausul otomatisasi dan penggunaan komersial (pengaduan yang telah diarsipkan), sementara catatan penegakan aturan per operator untuk platform komersial belum dipublikasikan.\n2. Penyalahgunaan OpenID / Proksi Otentikasi\tKebijakan yang dipublikasikan oleh GitHub memungkinkan aplikasi dan token OAuth ditangguhkan atau dicabut jika terjadi penyalahgunaan, dan dokumentasinya menjelaskan pencabutan otomatis terhadap token yang terpapar (ringkasan dokumentasi GitHub oleh para penulis).\tHost otentikasi dengan domain terpisah yang terdeteksi dalam alur OpenID Steam (misalnya rbsnin.com, howl.uno, sc-auth.net) tidak memicu pemblokiran Filter Tautan pada 2026-09-21, sedangkan domain utama mereka justru memicunya.\n3. Monetisasi Penyalahgunaan\tGitHub tidak memungut biaya transaksi atas barang yang dipindahkan melalui otomatisasi pihak ketiga; model pendapatannya berasal dari langganan dan daftar produk di pasar.\tValve menjual kunci peti yang menghasilkan barang-barang tersebut, dan Pasar Komunitas mengenakan biaya gabungan sekitar 15% atas penjualan yang diselesaikan di dalam Pasar. Angka pendapatan yang berasal dari platform pihak ketiga tidak diperkirakan di sini.\n4. Masa Pakai Loop Pengalihan\tID klien OAuth yang ditangguhkan akan berhenti berfungsi di seluruh platform sejak penangguhan; dokumentasi tidak mencantumkan perkiraan waktu yang diperlukan untuk tindakan, dan hal tersebut juga tidak diasumsikan di sini.\tHost otentikasi dengan domain terpisah yang memiliki tanggal pendaftaran mulai tahun 2011 hingga September 2026 tidak menunjukkan adanya pemblokiran Link Filter dalam pemeriksaan 2026-09-19 dan 2026-09-21. Tanggal pendaftaran merupakan batas bawah dari kemungkinan penggunaan, bukan bukti penggunaan yang berkelanjutan.\nSumber: Kolom GitHub — Dokumentasi batasan laju API dan kebijakan platform yang diterbitkan oleh GitHub (ringkasan penulis, bukan kutipan) · Kolom Steam — Pemeriksaan Filter Tautan pada 2026-09-19 dan 2026-09-21 (linkfilter-recheck-2026-09-21.json), pendaftaran RDAP (domain-registration.json) dan keluhan dukungan yang telah diarsipkan (arsip bukti).\nBagian B — Peraturan dan catatan penegakan · Pasal 13\nSelisih harga off-Steam\n\nBarang tersebut tersimpan di inventaris Steam; penjualannya dilakukan di tempat lain. Sebuah AWP Dragon Lore dalam kondisi baru dari pabrik telah 62 penawaran aktif di CSFloat; harga terendah yang ditawarkan $10,623.95. Pasar milik Steam sendiri tidak dapat menampilkan harga penawaran di atas sekitar $1,800. Untuk menjual dengan harga yang lebih tinggi yang teramati, pemilik memerlukan pembeli atau pasar di luar Steam. Barang tersebut dan proses peralihannya tetap bergantung pada Steam.\n\nWhat this means — the Community Market listing ceiling\n\nSteam’s own market refuses a listing above roughly $1,800. A seller may ask less, never more. Items whose market price sits above that line therefore cannot be sold at that price on Steam at all — which is the mechanism that moves those sales to third-party venues while the item itself never leaves Valve’s inventory system.\n\nSection 13 — the off-Steam price gap →\n\nKonteks & batasan sumber\n\nTerdapat tiga jenis hitungan yang berbeda dalam bagian ini, dan ketiganya tidak dapat digunakan secara bergantian. 245 adalah jumlah kategori nama barang CS2 yang penawaran aktif termurahnya melebihi $1,800 hanya di CSFloat, pada tanggal 20 September 2026. 241 yaitu himpunan yang sama dikurangi empat kategori yang ditempelkan pada batas atas $100,000 di CSFloat, yang merupakan panel yang digunakan sebagai dasar perhitungan batas bawah $13.63M. 248 Ini adalah gambaran yang berbeda: kategori-kategori yang harganya melebihi batas atas di dua atau lebih dari lima platform pada tanggal 23 September 2026. Platform-platform tersebut saling tumpang tindih, sehingga jumlah dari platform yang berbeda tidak boleh dijumlahkan. Setiap angka di sini merupakan harga penawaran, bukan penjualan yang telah diselesaikan, dan tidak ada satupun yang merupakan pendapatan, omzet, atau laba — baik untuk Valve maupun pihak lain manapun. Nilai-nilai yang tercantum di PriceEmpire adalah perkiraan yang dibulatkan yang dipublikasikan oleh situs tersebut, dan kartu Steam-nya mencakup item dari game Steam lainnya, sehingga cakupan perbandingan tersebut tidak identik.\n\nSatu barang. Dua sistem harga.IKUTI PERKEMBANGANNYA\nLangkah 3 / 3\n\nDengan permintaan tersebut, penjual memerlukan platform atau pembeli di luar Steam. Barang tersebut tetap bergantung pada sistem persediaan dan pengiriman Steam.\n\nSTEAMTentang $1,800Batas maksimum daftar di Pasar Komunitas yang telah diterbitkan\nKATALOG YANG TELAH DISIMPAN$10,623.95AWP Dragon Lore baru dari pabrik, silakan tanyakan harganya\nKETERGANTUNGANMasih merupakan barang SteamStok dan pemindahan tetap pada Steam\n01 / BARANGValve inventaris gameItem CS2 atau Dota 2 yang dimiliki di Steam\n02 / PLAFONTentang $1,800 pada SteamHarga maksimum untuk satu penawaran di Pasar\n03 / PERMINTAAN DARI LUAR$10,623.95 untuk Dragon LorePenawaran CSFloat termurah dalam snapshot yang sudah kadaluwarsa\n04 / PENGIRIMANSteam tetap berada dalam rantaiKepemilikan dan pemindahan barang bergantung pada sistemnya\nARSITEKTUR PASAR · GAMBARAN SITUASI PER TANGGAL, 20 SEPTEMBER 2026\nSelisih harga tersebut dapat diukur.\n\nKami menghitung kategori nama barang yang penawaran aktif termurahnya berada tepat di atas $1,800. CSFloat dan Skinport adalah cuplikan terpisah dengan inventaris CS2 yang tumpang tindih; jumlahnya tidak dapat dijumlahkan. Penawaran dari luar menunjukkan di mana harga yang diminta lebih tinggi diposting, sementara Steam masih mengontrol kepemilikan dan transfer barang.\n\n245KATEGORI CS2 · CSFLOAT\n166KATEGORI CS2 · SKINPORT\n3DOTA2KATEGORI · SKINPORT\n$10,623.95PERTANYAAN TENTANG LANTAI DRAGON LORE\n\nDragon Lore: 62 aktif; terdapat CSFloat penawaran dalam kategori \"Factory New\"; harga yang ditampilkan adalah harga yang diminta, bukan harga penjualan yang telah dikonfirmasi. Steam mengizinkan pencantuman barang dengan harga lebih rendah, namun tidak memperbolehkan pencantuman harga yang lebih tinggi dari yang teramati. Pernyataan Valve di 2016 menegaskan bahwa mereka menyadari adanya operator perjudian yang menggunakan OpenID dan infrastruktur perdagangan Steam. Apakah pasar pihak ketiga tertentu melanggar aturan Valve harus ditentukan secara terpisah.\n\nLihat daftar lengkapnya →CSFloat JSON ↗Skinport JSON ↗Pernyataan Valve di 2016 ↗\nAPI CSFLOAT LANGSUNG / CUPlKAN BERDASARKAN TANGGAL$13.63M\n\nNilai penawaran agregat minimum dalam 241 kategori barang dan 3,395 penawaran aktif. Dihitung berdasarkan harga ask termurah di setiap kategori dikalikan dengan jumlah penawaran di kategori tersebut. Empat kategori yang terikat pada batas atas $100,000 di CSFloat dikecualikan dari panel konservatif ini.\n\nApa yang ditunjukkan oleh angka dalam dolar tersebut\n\nPenawaran-penawaran ini setidaknya mewakili $13,631,888.25 dalam harga penawaran yang dipublikasikan untuk subset CSFloat terbatas ini. Dengan memasukkan keempat kategori harga tertinggi tersebut, hasilnya adalah $14,231,888.25. Ini adalah sebuah batas atas permintaan yang aktif, bukan penjualan yang belum diselesaikan, perputaran kas, laba, atau pasar CS2 secara keseluruhan.\n\nHitung ulang berdasarkan snapshot CSFloat yang terdiri dari 245 baris ↗\nPRICEEMPIRE / NILAI TERDAFTARSteam: #15 dari 39\nBanyak tempat yang mencantumkan nilai dalam dolar lebih besar dari Steam.\nUUSkins\n$133.8M\nYouPin898\n$127.5M\nBuff.163\n$104M\nMoon.Market\n$100.3M\nWhite.Market\n$89.6M\nBuff.Market\n$86.7M\nSteam\n$31M\n\nEnam nilai terbesar yang ditampilkan dan Steam. PriceEmpire membulatkan angka-angka ini; Steam menunjukkan $31M. Ada empat belas tempat yang terdaftar yang berada di peringkat di atasnya berdasarkan nilai dolar yang ditampilkan.\n\nPRICEEMPIRE / JUMLAH PENAWARANSteam: #1 dari 39\nSteam masih memimpin dalam hal jumlah penawaran.\nSteam\n32,2 juta\nYouPin898\n5,9 juta\nC5Game\n4,6 juta\nHaloSkins\n4,4 juta\nSkinport\n3,8 juta\n\nSteam menampilkan 32,2 juta penawaran. Jumlah penawaran dan total nilai yang diminta menjawab pertanyaan yang berbeda; banyak iklan dengan harga rendah dapat mendominasi jumlahnya.\n\nSumber: Perbandingan publik dari PriceEmpire ↗ diarsipkan 2026-09-21 ↗, direkam pada 2026-09-20 pukul 19:03 UTC; ekstraksi bertanggal 39 baris ↗. Angka-angka tersebut merupakan perkiraan yang dibulatkan, dan persediaan dapat tumpang tindih di antara berbagai lokasi. Kartu Steam juga mencantumkan item dari game Steam lainnya, sehingga cakupannya tidak sama. Nilai yang tercantum menunjukkan harga yang diminta, bukan penjualan atau pendapatan.\n42\nSUMBER LAIN / STEAMANALYST\nEkosistem komersial itu terlihat jelas.\n\nDirektori pasar SteamAnalyst diarsipkan 2026-07-19 ↗ mencantumkan 42 pasar CS2 pihak ketiga bersama Steam, dengan data harga terkini untuk 32 dari 43 entri tersebut. PriceEmpire mencantumkan 39 pasar berdasarkan kriteria pencantuman miliknya sendiri. Perusahaan yang disebutkan namanya, penawaran publik, harga yang terlihat: ekonomi ini terbuka untuk diperiksa.\n\nBATASANNYA ADALAH MEKANISMENYA: PENJUALANNYA MENINGKAT, BARANGNYA TIDAK.\n\nDi lima pasar yang terekam dalam satu tangkapan layar berlisensi, 248 kategori barang CS2 masing-masing dihargai di atas batas atas penawaran Steam sebesar sekitar $1,800 oleh dua atau lebih di antaranya — dan semuanya tidak terdapat di Steam. Tangkapan layar yang sama mengelompokkan seluruh katalog berdasarkan harga: pasar Valve menyediakan 95.3% dari kategori barang yang harganya di bawah batas atasnya dan 1.9% dari kategori yang harganya di atas batas tersebut. Penurunan ini tidak mencerminkan penurunan permintaan; hal ini tepat sesuai dengan aturan yang diterbitkan. Penjualan pada harga-harga tersebut memerlukan pembeli atau pasar eksternal, sementara Steam tetap mengendalikan persediaan dan proses transfer — transaksi meninggalkan kasir Valve dan pengiriman tetap menggunakan infrastruktur Valve.\n\nSteam Pertanyaan Umum tentang Pasar ↗diarsipkan 2026-09-21 ↗Steam Perjanjian Pelanggan ↗diarsipkan 2026-09-21 ↗Kumpulan data atlas lima pasar ↗Daftar asal-usul ↗Cuplikan CSFloat sebelumnya ↗Gambaran singkat Skinport ↗PriceEmpire ↗diarsipkan 2026-09-21 ↗SteamAnalyst ↗diarsipkan 2026-07-19 ↗Daftar selisih harga ↗Atlas tangga harga ↗\n\nBagian C — Kerangka hukum\nBagian C — Kerangka hukum · Pasal 14 · Akses personel\nSiapa yang bisa mengatur ulang sistem pengaman?\nKonteks & batasan sumber\n\nKeamanan akun juga bergantung pada pihak-pihak yang dapat memulihkan akun, memeriksa catatan pribadi, atau mengatur ulang pengaman akun tersebut. Penyelidikan harus memantau tindakan-tindakan istimewa tersebut dengan sama ketatnya seperti saat memantau penyalahgunaan API.\n\nPemulihan akun memberikan wewenang kepada petugas dukungan untuk mengalihkan akun dari pemiliknya. Valve telah menegaskan secara tertulis, sebanyak dua kali — pada Februari 2023 dan November 2025 — bahwa kewenangan ini digunakan untuk menyerahkan akun kepada orang yang salah. Selisih waktu tiga puluh tiga bulan, melalui saluran yang sama. Di bawah ini: seberapa berharganya akses tersebut, enam kasus yang bersumber, dan log Valve berlaku untuk masing-masing kasus tersebut dan belum pernah diberikan kepada siapa pun.\n\nKesaksian yang terdokumentasi / 9 Mei 2025\nTiket pemulihan yang menonaktifkan fitur keamanan akun tersebut, serta laporan kerugian sebesar $10,000\n\nSeorang pengguna dalam arsip dukungan yang terkumpul melaporkan bahwa Steam Tim Dukungan mereset kata sandi dan menonaktifkan perlindungan akun setelah orang lain mengajukan tiket pemulihan. Penulis mengatakan bahwa akun tersebut telah tidak aktif selama bertahun-tahun, menyimpan item sejak tahun 2016–2017, dan memiliki Steam Guard, nomor telepon yang tertaut, serta kode pemulihan yang tersimpan.\n\n\"Steam Tim Dukungan masih memberikan akses ke akun saya kepada orang lain.\"\n\nTuduhan dari sudut pandang orang pertama, yang tercatat dalam steam_support_tickets_MEGA.json, catatan nomor 110. Baca postingan yang telah disimpan secara lengkap ↗\n\nIni bukan sekadar nasib buruk seorang pengguna. Pintu masuk yang sama — yaitu permohonan bantuan yang mengalihkan akun kepada siapa pun yang menyediakan data yang lebih lama — merupakan cara yang tercatat secara resmi untuk setiap kasus dalam daftar di bawah ini, dan Valve telah dua kali menuliskannya secara tertulis.\n\nPemiliknya tidak bisa memenangkan perdebatan itu. Proses pemulihan meminta kunci CD pertama, alamat email pertama, kartu pertama, dan nomor telepon pertama. Data-data tersebut tersimpan dalam basis data Valve, dan tim dukungan mengaksesnya — dilaporkan mencakup riwayat hingga lima belas tahun ke belakang. Seseorang yang memiliki salinan berkas Anda akan selalu dapat mengungkap lebih banyak riwayat Anda daripada yang bisa Anda lakukan sendiri. Target dipilih agar sesuai: tidak aktif selama bertahun-tahun, bernilai tinggi, dan sering dibeli secara bekas, sehingga pemegangnya tidak pernah mengetahui kunci aslinya. Setelah itu, akun-akun tersebut dihapus sepenuhnya, memutus jejak riwayat item yang digunakan komunitas untuk melacak sebuah skin — penghapusan yang tidak dapat dilakukan oleh pengguna biasa tanpa masa tunggu standar.\n\nPrinsip hak akses minimal / OWASP A01\n\nHak akses pemulihan harus dibatasi hanya untuk tugas tersebut, ditinjau secara independen, dan dicatat. Lakukan audit terhadap pihak yang berwenang untuk mereset kredensial, menghapus Steam Guard, membaca catatan penagihan, atau mengekspor data akun. Panduan OWASP tentang kontrol akses ↗ diarsipkan 2026-09-20 ↗\n\nAkses dukungan yang luasRisiko lingkup akses\nLebih dari sekadar inventaris.\n\nJika akses dukungan luas disalahgunakan, data telemetri pribadi dapat menjadi alat untuk pembuatan profil, serangan phishing yang ditargetkan, dan pengawasan. Korban potensial meliputi pengguna biasa, personel militer, tokoh publik, dan keluarga mereka. Ini adalah model ancaman; izin yang tepat memerlukan catatan kontrol akses.\n\n01 Riwayat IP & lokasi\nCatatan IP dapat mengungkapkan riwayat jaringan dan perkiraan lokasi. Catatan tersebut, dengan sendirinya, tidak dapat menunjukkan pergerakan fisik yang tepat.\n02 Identifikasi perangkat berdasarkan sidik jari\nPengidentifikasi perangkat, jika dikumpulkan dan dapat diakses, dapat menghubungkan sesi dan akun.\n03 Telemetri aktivitas\nCatatan waktu login dan riwayat sesi dapat mengungkap kebiasaan, termasuk aktivitas yang tidak terlihat di profil publik.\n04 Komunikasi & Kontak\nAkses ke pesan yang disimpan atau informasi kontak akan memperluas ruang lingkup pembuatan profil dan rekayasa sosial.\n05 Pengungkapan identitas\nCatatan asli berupa email, nomor telepon, dan riwayat pembayaran dapat menghubungkan akun dengan nama samaran ke seseorang.\n06 Penjualan kembali data & pertanggungjawaban\nDaftar target yang diekspor dapat dimanfaatkan untuk melakukan penipuan yang ditargetkan. Identifikasi pelaku, lokasi akses, penerima, dan transaksi; lokasi saja tidak cukup untuk membuktikan adanya akses maupun kekebalan hukum.\n\nValve menjelaskan pencatatan alamat IP, informasi perangkat, catatan pembayaran, dan penyedia layanan dukungan pihak ketiga dalam Kebijakan Privasi Pasal 3, 5.2 diarsipkan 2026-09-21 ↗. Kebijakan tersebut mengizinkan akses dukungan pihak ketiga — jejak audit yang akan menunjukkan kontraktor mana yang mengakses kategori mana, kapan, dan berdasarkan otorisasi apa, belum diungkapkan.\n\nBagian 14.1 · daftar · Juni 2022 → November 2025 · setiap angka disertai sumbernya\nValve membuka pintu itu dua kali, dengan selang waktu tiga puluh tiga bulan. Pintu itu tak pernah tertutup.\n\nTerdapat enam kasus yang dilaporkan di mana akun-akun diretas melalui saluran permintaan bantuan milik Steam sendiri, atau melalui kredensial yang dilindungi oleh saluran tersebut. Setiap jumlah yang tercantum adalah angka yang dipublikasikan oleh sumber yang dikutip, dan setiap sumber disebutkan namanya. Dua dari enam kasus tersebut telah diselesaikan sepenuhnya. Perbedaan antara keduanya dengan kasus-kasus lainnya bukanlah apa yang terjadi — melainkan siapa yang mengawasinya.\n\nValve, secara tertulis — Februari 2023\"Item-item yang dimaksud telah dihapus dari akun Anda karena diterima dari akun yang diretas melalui permintaan bantuan dukungan, dan tim CS:GO bertanggung jawab atas hal tersebut. Kami telah membatalkan transaksi tersebut dan menghapusnya dari semua akun yang menerimanya.\"Steam Dukungan untuk membalas penerima barang-barang HFB, yang disalin oleh Dexerto, 21 Februari 2023 ↗ diarsipkan 2025-08-18 ↗\nValve, kembali menulis — November 2025 · 33 bulan kemudian\"Seorang teknisi dukungan yang menangani permintaan bantuan tersebut tidak mengikuti prosedur kami, sehingga akun Anda dipulihkan ke nama orang lain. Saya mohon maaf atas kesalahan ini.\"Steam Tanggapan dukungan untuk Hawkeye337, yang dikutip dalam Dexerto, 14 November 2025 ↗\n21 Juni 2022\nHFB — inventaris terbesar dalam game ini$2,000,000+ · dinaikkan menjadi $3,000,000+ dalam pemeriksaan lanjutan pada Februari 2023\n\nTujuh Souvenir AWP Dragon Lores dan Karambit Permata Biru #1, pisau itu sendiri bernilai sekitar $1.26 juta. Akun tersebut telah tidak aktif selama tiga tahun, namun aplikasi otentikasi seluler masih aktif; alamat email dan kata sandinya tetap diubah melalui proses pemulihan yang disediakan oleh layanan dukungan.\n\nUang itu habis lebih dulu daripada barang-barang tersebut. Sebuah laporan menyebutkan $200,000+ Sebagian dari hasil penjualan telah ditarik melalui market.csgo.com — sebuah pasar daring yang melakukan penyelesaian transaksi menggunakan uang tunai dan kripto. Membatalkan transaksi akan mengembalikan skin tersebut. Namun, uang tunai yang telah ditarik oleh seseorang tidak akan dikembalikan.\n\nDan perbaikan itu malah membuat masalah baru. Seorang pembeli memindahkan Souvenir Dragon Lore miliknya ke Unit Penyimpanan dalam game. Skrip rollback milik Valve tidak dapat melihat isi wadahnya sendiri, sehingga skrip tersebut memberikan salinan baru kepada pemiliknya dan membiarkan yang tersembunyi tetap ada — Valve menduplikasi sebuah $130,000 Barang tersebut terdeteksi saat upaya untuk membatalkan pencurian. Barang tersebut terungkap melalui pencocokan ID barang dan laporan dari komunitas, lalu dihapus sebulan kemudian, pada Juli 2022. Pembeli menerima pengembalian dana dari BUFF, bukan dari Valve. Tindakan perbaikan darurat yang begitu rapuh bukanlah suatu bentuk pengendalian; itu adalah apa yang dilakukan sebuah platform ketika tidak memiliki kendali.\n\nDexerto, 21 Juni 2022 ↗ diarsipkan 2022-07-02 ↗ · Kaspersky ↗ · jumlah penarikan per Esportfire, 22 Juni 2022 ↗ diarsipkan 2026-05-15 ↗, yang disebutkan di sana bersumber dari beberapa akun Twitter · duplikasi dan penghapusan sesuai Esportsbetting, 14 Juli 2022 ↗\n\nTelah dipulihkanTransaksi dibatalkan. Barang-barang tersebut ditarik kembali dari persediaan orang-orang yang telah membelinya dengan harga penuh.\n14 Agustus 2022\nCS.Money — bot bawaan platform tersebut$6,300,000 · 19,000+ kulit · perkiraan awal $1.6M\n\nPara penyerang mencuri berkas otentikator seluler milik bot perdagangan di pasar tersebut dan mengosongkannya, lalu mengirimkan sebagian hasil curian itu kepada para pedagang ternama untuk mengaburkan jejak. Para peneliti komunitas memetakan 55 akun penyerang dalam hitungan jam dan menerbitkannya.\n\nValve tidak membatalkan apa pun. Alasan yang dikemukakan adalah bahwa situs pihak ketiga tersebut berada di luar Steam — yaitu Steam yang sama, di mana pencurian tersebut berlangsung dari awal hingga akhir dengan memanfaatkan inventaris, API perdagangan, dan sistem akunnya.\n\nEsportfire, 14 Agustus 2022 ↗ diarsipkan 2025-11-15 ↗\n\nDitolakTidak ada pembalikan. Kerugian tetap ditanggung oleh platform dan para penggunanya.\nDilaporkan\n21 Februari 2023\nQkss — pintu yang sama, pemeran yang sama$1,000,000+\n\nDilaporkan bahwa kasus ini ditangani dengan cara yang sama seperti kasus HFB, oleh pihak yang sama, melalui permintaan bantuan yang sama. Kasus HFB telah diselesaikan sepenuhnya delapan bulan sebelumnya. Sedangkan kasus Qkss belum.\n\nSatu rute. Dua jawaban. Tidak ada hal apa pun dalam catatan yang dipublikasikan yang membedakan kedua kasus tersebut kecuali jumlah penontonnya.\n\nDexerto, 21 Februari 2023 ↗ diarsipkan 2025-08-18 ↗\n\nDitolakBelum dipulihkan.\nDilaporkan\nFebruari 2023\nPraktik perdagangan orang dalam itu sendiri — selama satu tahun≈ $320,000 · berlangsung selama kurang lebih satu tahun, bukan penilaian persediaan\n\nAkses dari sisi dukungan telah mencapai riwayat akun hingga 15 tahun — kunci CD pertama, email pertama, kartu pertama. Itulah tepatnya bukti yang diminta dalam proses pemulihan, dan itulah sebabnya pihak yang menguasai basis data selalu menang dalam perselisihan melawan pihak yang menguasai akun.\n\nBlogger Mzkshow mengungkap bagaimana operator dalam jaringan \"Steam Help\" dan rekan kerjanya \"Alexander\" menargetkan akun-akun tidak aktif yang menyimpan skin senilai lebih dari $100k. Satu senjata M4A4 Howl hasil curian yang dilengkapi dengan hologram iBUYPOWER dan Titan Katowice 2014 terjual seharga $35,000 dan akhirnya melibatkan Valerii \"b1t\" Vakhovskyi dari NAVI, yang sama sekali tidak mengetahuinya. Setelah Valve turun tangan, kontraktor tersebut memberhentikan seluruh staf Steam bagian layanan dukungan.\n\nVKPlay ↗ · Lis-Skins ↗ · Escorenews (RU) ↗ · Dexerto (EN) ↗\n\nTidak ada daftarValve belum pernah mengumumkan berapa banyak akun yang terkena dampaknya, atau memberi tahu orang-orang yang terkena dampaknya.\nDilaporkan\n2 Desember 2024\n\"Matvey\" — setelah pemecatan-pemecatan tersebut$13,000\n\nPemulihan diberikan kepada seseorang yang memberikan data akun yang bahkan pemiliknya sendiri tidak dapat mencocokkan. Dua tahun setelah kontraktor tersebut membubarkan layanan bantuan Steam-nya, cara yang sama menghasilkan hasil yang sama.\n\nPostingan yang disimpan, 2 Desember 2024 ↗ diarsipkan 2025-08-05 ↗ · baris sumber & hash ↓\n\nDitolakBelum dipulihkan.\n13 November 2025\nHawkeye337 (Mark Spurlock) — dan pengakuan keduanya≈ $300,000–$500,000 · Koleksi holo lengkap Katowice 2014\n\nPelaku menuntut 1 bitcoin dan mulai memindahkan koleksi tersebut ke Negevs untuk menghancurkannya. Steam Jawaban tertulis dari Tim Dukungan merupakan pengakuan kedua di atas: seorang teknisi menangani permintaan bantuan tersebut, tidak mengikuti prosedur yang berlaku, dan menyerahkan akun tersebut kepada orang lain.\n\nYang menyebabkan masalah itu adalah umpan. Beberapa jam setelah postingan yang menandai Valve diunggah di X, akun tersebut dikembalikan dan semua stiker dipulihkan. Qkss tidak memiliki audiens sebanyak itu.\n\nSkin.club ↗ · Dexerto ↗ · Esportfire ↗ diarsipkan 2025-12-17 ↗\n\nTelah dipulihkanDitarik kembali dalam hitungan jam setelah berita tersebut menjadi trending.\nApa yang tercantum dalam buku besar itu tidak dapat dijelaskan oleh satu kasus pun.\n\nRute tersebut tidak pernah ditutup. Pendaftaran pertama tertanggal Februari 2023 dan yang kedua November 2025 — selisih tiga puluh tiga bulan, disertai pemecatan massal oleh kontraktor, kejadian serupa yang tercatat, dan pelanggaran keamanan platform senilai $6.3 juta di antaranya. Jika dihitung sejak pencurian pertama dalam catatan ini, saluran tersebut tetap terbuka selama tiga tahun lima bulan. Terlepas dari apa pun yang telah diperbaiki pada tahun 2023, permintaan bantuan tersebut tetap saja dialihkan ke orang yang salah pada November 2025 — seperti yang disebutkan oleh Valve sendiri.\n\nRestitusi berfokus pada perhatian, bukan pada kerugian. Dipulihkan: inventaris terbesar dalam game ini, dan sang kolektor yang utasnya menjadi trending. Ditolak: $1,000,000, $6,300,000, $13,000. Valve tidak pernah mempublikasikan aturan yang digunakannya, karena aturan yang dipublikasikan harus menjelaskan ketiga hal tersebut.\n\nTidak ada yang diberi tahu. Bukan para pengguna yang riwayat akunnya diambil dari basis data, bukan otoritas pengawas, bukan pula pihak pasar yang membeli barang-barang tersebut dengan itikad baik dan kemudian barang-barang itu ditarik kembali. Tidak ada pemberitahuan pelanggaran, tidak ada laporan insiden, tidak ada data jumlah akun yang terdampak — dan hasil penjualan yang tersisa dalam bentuk uang, melalui platform perdagangan yang membayar dengan uang tunai dan kripto. Pembatalan transaksi tidak dapat dilakukan setelah dana ditarik dari Steam.\n\nValve menyimpan jejak audit dukungan, catatan tiket pemulihan, dan catatan transaksi untuk setiap baris di atasnya. Tidak ada satupun dari data tersebut yang telah diserahkan. Minta salinannya →\n\nPertanyaan tentang NDA\nKerahasiaan harus dibarengi dengan akuntabilitas teknis.\n\nBandingkan perjanjian kerahasiaan dengan izin yang sebenarnya, pengendalian ekspor, persetujuan reset, dan catatan akses. Tanggapan standar tidak dapat menyelesaikan tuduhan bahwa proses pemulihan itu sendiri telah disalahgunakan.\n\nPasal 28, 32–34 GDPR\n\nPasal 33 memberikan waktu 72 jam kepada pengendali data untuk memberitahukan otoritas pengawas mengenai pelanggaran data pribadi; Pasal 34 mewajibkan pemberitahuan kepada pihak yang terdampak apabila risiko yang dihadapi mereka tinggi. Valve telah mengonfirmasi secara tertulis, sebanyak dua kali, bahwa saluran dukungannya telah menyerahkan akun kepada orang yang salah — termasuk riwayat akun, catatan penagihan, dan sebagainya. Belum ada pemberitahuan berdasarkan salah satu pasal tersebut yang diterbitkan, dan belum ada pengguna yang terdampak yang melaporkan telah menerimanya. Baca peraturan tersebut ↗ diarsipkan 2026-09-20 ↗\n\nSertakan akses dukungan dalam permintaan Anda →\nBagian C — Kerangka hukum · Pasal 15 · Skala komersial\nTelusuri aliran uangnya. Pisahkan transaksi-transaksinya.\nKonteks & batasan sumber\n\nPertanyaan mengenai penggunaan komersial menjadi semakin tajam ketika arus uang dipisahkan. Transfer barang oleh pihak ketiga, penjualan utama Valve, dan penarikan dana ke luar merupakan transaksi yang berbeda.\n\nBarang tersebut milik Valve. Stoknya berjumlah Valve. Proses pemindahan dilakukan di server milik Valve. Hanya saja pembayarannya dilakukan di tempat lain — yang merupakan langkah yang menentukan apakah seseorang tergolong sebagai penyedia jasa pengiriman uang, dan langkah Valve itulah yang tidak dijalankan.\n\nMekanisme pendapatan\nDi mana uang itu sebenarnya mengalir.\nTiga jalur / sistem ekonomi satu barang\n01 / AkunDaftar pengguna\n\nBarang yang disimpan pada Steam\n\n02 / TransferPerdagangan P2P\n\nPengguna ↔ bot atau pengguna ↔ pengguna\n\n03 / PenyelesaianPlatform eksternal\n\nSaldo situs atau pelunasan Steam\n\nSirkulasiPendorong perekonomian tidak hanya sebatas biaya transfer\n\nSteam menyediakan infrastruktur inventaris dan transfer yang digunakan oleh pasar eksternal. Argumen ekonomi dari penyelidikan ini adalah bahwa likuiditas penjualan kembali dan permintaan berulang menopang pengeluaran untuk casing, kunci, dan barang pengganti, disertai dengan biaya atas penjualan selanjutnya di Community Market. Transfer P2P langsung tidak dikenakan komisi Pasar Komunitas; fakta akuntansi tersebut tidak menyelesaikan manfaat yang lebih luas. Valve tetap memegang kendali atas akses akun dan pembatasan perdagangan sepanjang proses.\n\n01 / Permintaan sekunderLikuiditas & nilai jual kembali\n\nPermintaan dari sektor perdagangan luar negeri dan perjudian\n\n02 / Belanja primerKunci, kotak, dan kapsul\n\nPembelian mulai dari Valve jika tersedia\n\n03 / PendapatanPendapatan dari penjualan pertama\n\nDitambah biaya atas penjualan aktual di pasar\n\n5% + 10%Steam + Biaya CS2 atas penjualan di Community Market\n\nKesimpulan ekonomi dari penelitian ini: pasar penjualan kembali yang likuid dapat mendorong belanja barang-barang baru. Angka 15% yang sudah dikenal tersebut merupakan gabungan dari tarif biaya pasar, dengan batasan minimum dan pembulatan; angka tersebut bukanlah pungutan atas setiap transaksi perdagangan luar negeri.\n\nDaftar tarif Pasar Komunitas Valve ↗ diarsipkan 2026-09-21 ↗. Pada tanggal 25 Februari 2026 Jaksa Agung New York mengajukan gugatan diarsipkan 2026-09-01 ↗ dengan tuduhan bahwa kotak jarahan berbayar terkait dengan penjualan kembali uang tunai di pihak ketiga dan dampak negatif perjudian — hubungan yang sama yang didokumentasikan dalam dokumen ini dari sisi infrastruktur teknis. Keluhan tersebut hanyalah sebuah tuduhan, bukan temuan; hal ini dikutip di sini karena sebuah lembaga penegak hukum negara bagian telah mengajukan pertanyaan yang berkaitan dengan pertanyaan yang diajukan dalam dokumen ini: di manakah catatan penegakan hukum yang sesuai dengan pernyataan publik tersebut?\n\n01 / EntriSetoran kripto\n\nCatatan layanan eksternal dan dompet\n\n02 / KonversiSaldo → tema\n\nBarang yang dikirim melalui Steam transaksi\n\n03 / KeluarPenjualan mata uang fiat eksternal\n\nPenjual, pembeli, dan penyedia pembayaran\n\nKYC?Identifikasi kontrol pada setiap serah terima\n\nInilah langkah yang harus ditelusuri, bukan layanan konversi tunai berbasis API Steam bawaan. Dokumentasikan verifikasi identitas, penitipan, ID transaksi, dan penerima pembayaran di setiap operator eksternal sebelum menyatakan penarikan tunai tanpa KYC.\n\nAmerika Serikat / Undang-Undang Kerahasiaan Perbankan\nKlasifikasikan aktivitasnya terlebih dahulu, baru kemudian kewajibannya.\n\nFinCEN menilai kegiatan pengiriman uang berdasarkan aktivitas yang dilakukan oleh suatu usaha. Menerima dan mentransfer mata uang virtual yang dapat dikonversi dapat memicu kewajiban layanan keuangan, dengan tunduk pada definisi dan pengecualian yang berlaku. Dompet Steam milik Valve menerima dana dan mengonversinya menjadi item dalam game; item tersebut kemudian dilikuidasi melalui operator pihak ketiga untuk ditukar dengan mata uang riil. Item dan transfernya berjalan di infrastruktur Valve; penarikan dana tidak demikian, dan apakah ada bagian dari siklus tersebut yang memenuhi definisi pengiriman uang merupakan pertanyaan klasifikasi bagi FinCEN, bukan kesimpulan yang diambil di sini.\n\nFinCEN FIN-2019-G001, § 1–2, 5.1 ↗ diarsipkan 2025-07-11 ↗\n\nUni Eropa / pencucian uang\nMelacak aliran dana, informasi, dan bantuan.\n\nPetunjuk (UE) 2018/1673 mencakup tindak pidana pencucian uang yang disengaja dan keterlibatan yang melibatkan hasil kejahatan. Pertanyaan dalam penyelidikan ini adalah apa yang diketahui oleh Valve mengenai para operator yang menggunakan infrastruktur perdagangan dan OpenID-nya setelah 13 Juli 2016, ketika perusahaan tersebut secara terbuka menjelaskan penggunaan tersebut, serta tindakan apa yang diambilnya terhadap mereka. Valve belum menerbitkan catatan penegakan hukum per operator; catatan tersebut, bukan berkas ini, yang akan menjawab pertanyaan tersebut.\n\nKerangka hukum pidana Uni Eropa ↗\n\nIstilah-istilah dalam AMLD6: Arahan hukum pidana di atas berbeda dengan Arahan (UE) 2024/1640, yang juga dikenal sebagai AMLD6. Arahan yang terakhir ini memiliki batas waktu transposisi umum pada 10 Juli 2027, dengan pengecualian-pengecualian tertentu. Pasal 78 ↗ diarsipkan 2026-08-30 ↗\n\nBagian C — Kerangka hukum · Pasal 16 · Pemberitahuan, tanggapan, tanggung jawab\nUndang-Undang Layanan Digital: mencatat pengetahuan secara resmi\nKonteks & batasan sumber\n\nDua unsur pemberitahuan berdasarkan Pasal 16 menjadi tanggung jawab pemberi pemberitahuan, bukan bagian dari berkas ini: rincian pribadi pemberi pemberitahuan dan pernyataan itikad baik bahwa informasi tersebut akurat. Semua hal lain yang disyaratkan oleh Pasal tersebut — penjelasan yang didukung bukti dan lokasi elektronik yang tepat — tercantum dalam Bagian 3 dan dalam daftar rute, beserta tanggapan yang disimpan dan hash, sehingga pihak mana pun dapat mengajukan pemberitahuan tersebut. Dua batasan lebih lanjut terkait undang-undang itu sendiri: kehilangan pengecualian hosting tidak secara otomatis menimbulkan tanggung jawab berdasarkan undang-undang lain mana pun, dan angka 6% dalam Pasal 52(3) merupakan batas maksimum yang ditetapkan undang-undang, bukan denda yang ditetapkan terhadap Valve.\n\nBerdasarkan DSA, penyedia layanan hosting hanya tetap terlindung dari tanggung jawab hingga ia memiliki pengetahuan spesifik dan gagal mengambil tindakan. Dokumen ini merupakan pemberitahuan tersebut. Dokumen tersebut mencantumkan nama-nama host, tanggal, respons yang disimpan, dan nilai hash. Sejak diterbitkan, pertanyaannya bukan lagi apakah Valve mengetahuinya — melainkan apa yang dilakukan Valve selanjutnya.\n\n01Juli 2016 / pameran berkas\nTuntutan selama sepuluh hari.\n\nPemberitahuan yang direkonstruksi di atas merupakan titik awal historis bagi perbandingan penegakan hukum dalam penyelidikan ini.\n\n0217 Februari 2024 / pendaftaran umum\nJendela waktu DSA.\n\nPisahkan perilaku di masa lalu dari perilaku selama periode ketika kewajiban DSA yang bersangkutan berlaku.\n\n03Sepuluh tahun / cuplikan berkas asli\nDurasi memerlukan riwayat pemberitahuan.\n\nWaktu yang telah berlalu sejak Juli 2016 (lihat Bagian 11) merupakan metrik berkas. Hal ini bukanlah pelanggaran DSA yang telah berlangsung selama sepuluh tahun. Hubungkan setiap pemberitahuan dengan item tertentu, undang-undang yang berlaku, bukti pengiriman, dan tanggapan.\n\nPasal 52 ayat (3) / batas maksimum yang ditetapkan undang-undang6%\ndari omzet tahunan di seluruh dunia\n\nDenda maksimum atas pelanggaran kewajiban berdasarkan DSA, dengan mengacu pada tahun buku sebelumnya dari penyedia layanan. Ini merupakan batas maksimum yang ditetapkan undang-undang, bukan sanksi yang telah ditetapkan terhadap Valve.\n\nPasal 6, 8, dan 16 / uji hukum\n\nUntuk layanan hosting yang bersangkutan, pengetahuan spesifik dan kegagalan bertindak dengan cepat dapat mengakibatkan dicabutnya pengecualian hosting. Pemberitahuan yang cukup jelas dapat membuktikan adanya pengetahuan mengenai konten tertentu. DSA tidak memberlakukan kewajiban pemantauan secara umum; pencabutan pengecualian itu sendiri tidak secara otomatis menimbulkan pertanggungjawaban berdasarkan undang-undang lain.\n\nDSA: Pasal 6, 8, 16, 52, 53, 93, dan pertimbangan ke-17 ↗ diarsipkan 2026-09-20 ↗\n\nTinjau keluhan yang disimpan ↗Buat garis waktu akun →Analisis hukum dan ekonomi selengkapnya →\nBagian C — Kerangka hukum · Pasal 17 · Identitas, usia, akses komersial\nAnak di bawah umur: login dengan kode Steam bukanlah verifikasi usia\nKonteks & batasan sumber\n\nTidak ada data anak di bawah umur yang muncul di mana pun dalam berkas ini dan tidak ada yang dikumpulkan: para penulis tidak mendaftar, menyimpan, atau masuk ke platform mana pun yang disebutkan. Siapa pun yang mengembangkan bagian ini harus menjaga kerahasiaan bukti yang melibatkan anak dan menyunting detail yang dapat mengidentifikasi identitas dari bukti yang dipublikasikan. COPPA disebutkan di sini sebagai undang-undang privasi anak-anak dengan ketentuan ruang lingkupnya sendiri — audiens, pengetahuan yang sebenarnya, data pribadi yang dikumpulkan — dan bukan sebagai aturan umum mengenai batas usia perjudian; gugatan di New York tahun 2026 merupakan tuduhan dari otoritas negara bagian, bukan putusan.\n\n\"Masuk dengan Steam\" membuktikan bahwa akun tersebut ada. Hal itu tidak membuktikan apa pun mengenai usia — dan di situs-situs ini, itulah satu-satunya penghalang antara seorang anak dan setoran. Bacalah dengan Bagian 3.1: di dalam klien Steam, peringatan yang biasanya ditampilkan oleh peramban tidak pernah muncul, sehingga anak tidak pernah melihatnya.\n\nApa yang disediakan oleh Steam OpenIDIdentitas akun\n\nSteamID yang telah diverifikasi yang digunakan untuk masuk atau menghubungkan akun.\n\n≠\nHal-hal yang harus ditetapkan oleh operatorSyarat untuk berpartisipasi\n\nUsia, yurisdiksi, dan pemeriksaan identitas yang diperlukan.\n\nDasar teknis: Dokumentasi Steamworks OpenID ↗ diarsipkan 2026-09-21 ↗. Pernyataan identitas yang terdokumentasi tersebut bukanlah sertifikasi bahwa pengguna diperbolehkan secara hukum untuk berjudi.\n\nCOPPA / anak-anak di bawah usia 13 tahun\nIdentifikasi operator dan datanya.\n\nCOPPA berlaku bagi layanan yang ditujukan untuk anak-anak dan layanan yang secara nyata mengetahui bahwa mereka mengumpulkan informasi pribadi dari anak-anak di bawah usia 13 tahun. Undang-undang ini merupakan undang-undang privasi anak-anak, bukan aturan umum mengenai batas usia perjudian. Tentukan target audiens, data pribadi yang dikumpulkan, tingkat kesadaran, serta proses persetujuan orang tua.\n\nFTC: Persyaratan COPPA ↗ diarsipkan 2026-09-21 ↗\n\nBukti yang harus dilestarikan\nCatat proses mulai dari login hingga melakukan setoran.\n\nPertahankan batasan usia situs, ketentuan pendaftaran, syarat kelayakan, alur pembayaran, dan riwayat pengaduan. Lakukan penilaian terhadap setiap operator secara terpisah. Jaga kerahasiaan setiap bukti yang melibatkan anak dan samarkan detail yang dapat mengidentifikasi identitas dari bukti-bukti yang dipublikasikan.\n\nSalah satu catatan penegakan hukum publik yang terkait adalah Pengumuman pengaduan di New York tahun 2026 diarsipkan 2026-09-01 ↗, yang menuduh adanya dampak merugikan bagi pengguna muda akibat kotak hadiah berbayar. Hal ini bukanlah temuan berdasarkan COPPA.\n\nBagian C — Kerangka hukum · Bagian 18 · Permohonan berdasarkan Pasal 15 GDPR\nPermintaan. Jawaban. Perbandingan yang terlewatkan.\n\nDia meminta empat hal, salah satunya adalah log yang akan mengungkap identitas orang yang memasukkan kunci API ke akunnya. Tiga hari kemudian, tiket tersebut ditutup dengan tautan ke halaman yang tidak memuat satupun dari hal-hal tersebut — dan kalimat yang digunakan untuk menutupnya dibantah oleh pengacara Valve sendiri.\n\nAkun ini milik siapa · Asal-usul & Batasan\n\nTangkapan layar ini bukan milik PhishDestroy. Mereka berasal dari seorang pemegang akun Steam biasa — salah satu responden dalam survei singkat yang diselenggarakan oleh proyek ini, yang mengajukan permintaan tersebut sendiri dan menyediakan tangkapan layarnya. Akun tersebut miliknya, tiket tersebut miliknya, dan korespondensi tersebut terjadi antara dirinya dan Tim Dukungan Steam. Proyek ini tidak mengajukan permohonan tersebut, tidak memiliki akun di platform tersebut, dan bukan pihak yang terlibat dalam tiket ini.\n\nPada 16 September 2026, ia mengajukan permohonan akses data sesuai Pasal 15 GDPR/CCPA yang secara khusus meminta log pendaftaran kunci API, riwayat login beserta alamat IP, riwayat otorisasi perangkat, dan riwayat transaksi. Pada 17 September, agen \"Logen\" mengarahkan dia ke halaman Data Akun layanan mandiri. Pada tanggal 18 September, ia menyatakan bahwa kategori yang diminta tidak terdapat di halaman tersebut dan meminta agar masalah ini diteruskan ke Tim Privasi atau DPO. Pada tanggal 19 September, agen \"Kal\" menutup tiket tersebut dengan rujukan yang sama. Kedua tangkapan layar tersebut disimpan di bawah ini (alamat email pemohon disamarkan; SHA-256 dalam steam_tos_assets/screenshot-manifest.json).\n\nDia adalah pemohon yang tepat karena alasan yang biasa saja: Akunnya memiliki kunci Web API Steam yang tidak dibuatnya sendiri, yang terdaftar atas nama localhost. Tidak diketahui kapan hal itu dibuat — bukan kepadanya, dan bukan berasal dari apa pun yang telah disediakan oleh Valve kepadanya, karena satu-satunya catatan yang dapat menentukan tanggalnya adalah log pendaftaran kunci API, yang justru merupakan kategori informasi yang disembunyikan oleh pihak yang menutup kasus tersebut. Kunci tersebut bukanlah hal baru: kunci itu sudah ada jauh sebelum ia menyadarinya, dalam rentang waktu yang tak dapat ia ukur, karena alasan yang sama.\n\nPemegang akun lainnya juga mengajukan permintaan yang sama. Setiap balasan yang diterima akan ditambahkan di sini dengan ketentuan yang sama seperti kedua permintaan ini — nomor tiket, tanggal penangkapan, SHA-256, identitas pemohon disamarkan — baik jika balasan tersebut menyetujui kategori-kategori tersebut maupun menolaknya.\n\nProyek ini tidak mengambil sikap apa pun mengenai alasan penutupan tiket tersebut. Tidak ada alasan yang disebutkan di dalamnya, dan tidak ada kesimpulan yang ditarik di sini.\n\nPermintaan. Tanggapan. Perbandingan.IKUTI PERKEMBANGANNYA\nLangkah 3 / 3\n\nDia meminta empat kategori tertentu. Halaman Data Akun yang disebutkan kepadanya adalah fitur ekspor mandiri milik Valve sendiri, dan proyek ini tidak dapat merinci isinya untuk akun orang lain — sehingga tidak ada perbandingan lengkap per kategori yang dipublikasikan di sini. Yang tercatat adalah pernyataannya pada 18 September bahwa kategori-kategori tersebut tidak ada, serta penutupan kasus pada 19 September yang mengulangi rujukan tersebut tanpa menanggapi kategori-kategori tersebut.\n\nPERMINTAANKategori tertentuKunci API, data login, data perangkat, dan riwayat transaksi\nTANGGAPANReferensi Data AkunPeriksa pertukaran dukungan\nUJI COBAApa saja yang disediakan?Bandingkan setiap kategori yang diminta\nLayar 1/2 — Permintaan (16 Sep) dan balasan pertama, agen \"Logen\" (17 Sep)\nGDPR ticket HT-2YBP-F7JP-D4VB — request and first response\nSumber: help.steampowered.com, tiket HT-2YBP-F7JP-D4VB · direkam pada 16–17 Sep 2026 · alamat email pemohon disamarkan 2026-09-21 · File: gdpr-ticket-1.png · SHA-256 da940c731ab9869d226e9d06ccc8a1b393738766b7b0c445a56662623e025a66 (screenshot-manifest.json).\nLayar 2/2 — Permintaan eskalasi (18 Sep) dan penutupan, agen \"Kal\" (19 Sep)\nGDPR ticket HT-2YBP-F7JP-D4VB — escalation request and closure\nSumber: help.steampowered.com, tiket HT-2YBP-F7JP-D4VB · diambil pada 18–19 Sep 2026 · Berkas: gdpr-ticket-2.png · SHA-256 44844ea7b251f7fd7d79f87ee1578a846606a97b9659d3a53b322120c422219b (screenshot-manifest.json).\nTanggapan penutup, 19 September (secara harfiah):\n\"Data Steam yang tersimpan sudah dapat Anda temukan di halaman Data Akun Anda. Karena tidak ada informasi lebih lanjut Steam yang dapat diberikan oleh Tim Dukungan, Permintaan ini akan ditutup.\"\nTidak ada data yang disertakan · tidak disebutkan dasar hukum penolakan · tidak ditampilkan hasil eskalasi\nKalimat itu salah, dan pengacara Valve sendiri yang membuktikannya. Surat penasihat hukum tertanggal 1 Oktober 2025, pada paragraf 1.9, menjelaskan korelasi pada tingkat perangkat yang menghubungkan satu perangkat dengan puluhan akun (Lampiran A). Surat balasan yang sama memuat 830 halaman dokumen yang disimpan (Lampiran B). Tidak ada satupun yang tercantum di halaman Data Akun.\nMengapa akun ini meminta riwayat kunci API?\n\nDia tidak memilih keempat kategori itu secara sembarangan. Yang localhost Kunci pada akunnya adalah tanda bahwa itu adalah skrip, bukan seseorang yang mengetikkan domain asli ke halaman pengembang (Bagian 5, Bagian 6). Satu-satunya catatan yang menunjukkan siapa yang membuatnya dan dari mana asalnya adalah log pendaftaran kunci API. Itulah hal pertama yang dia minta. Dan itulah yang disembunyikan oleh pihak yang menutup kasus tersebut.\n\nSumber: pemegang akun, selama survei proyek ini. Tangkapan layar tiket di atas telah di-hash; halaman kuncinya tidak dipublikasikan.\n\nPenilaian · PhishDestroy\n\nMenutup tiket sementara pertanyaannya masih belum terjawab bukanlah suatu kesalahan di sini. Itu adalah hasil yang wajar. Kami memegang 16,319 catatan pengaduan dan dukungan yang disimpan dan 354 percakapan dukungan yang telah dihilangkan duplikatnya yang diambil dari sana. Tiket ini merupakan salah satu contoh yang sudah diberi tanggal dan tercatat secara lengkap mengenai bentuk yang dimilikinya.\n\nTiket Dukungan — DisimpanHT-2YBP-F7JP-D4VB\nJenis permintaanPasal 15 GDPR (Permohonan Akses Data)\nStatus tiketTUTUP 19 SEP 2026 — TIDAK ADA DATA YANG DISEDIAKAN\nAgen di bursa\"Logen\" (17 Sep), \"Kal\" (19 Sep)\nTelah diajukan16 September 2026\nData yang dimintaSiapa yang mendaftarkan kunci Web API yang terhubung dengan akun ini, dan dari alamat IP / perangkat / cap waktu mana\nDasar hukum yang dikutipPasal 15 GDPR — hak untuk mengakses data pribadi\nKerangka hukum:Pasal 12 ayat (3) memberikan waktu satu bulan kepada pengendali data sejak diterimanya permohonan (dapat diperpanjang dengan alasan yang jelas). Jangka waktu tersebut belum berakhir pada saat publikasi, dan berkas ini tidak menyatakan adanya pelanggaran batas waktu. Keberatan ini berkaitan dengan substansi: tanggapan penutup mengarahkan ke halaman layanan mandiri tetapi tidak menunjukkan bahwa keempat kategori data yang disebutkan telah disediakan, dan jika pengendali data menolak untuk bertindak, Pasal 12(4) mewajibkannya untuk menyatakan alasan serta jalur pengaduan. Keduanya tidak tercantum dalam tanggapan penutup.\nMengapa data ini khususnya penting\n\nCatatan peristiwa kunci Web API adalah catatan yang menunjukkan apakah pihak ketiga telah mendaftarkan kunci menggunakan cookie sesi yang dicuri — mekanisme yang dijelaskan dalam pengaduan pencurian inventaris yang disimpan dalam arsip berkas ini. Mengungkapkan siapa yang mendaftarkan kunci API, dari alamat IP mana, dan pada waktu kapan, akan:\n\nIzinkan korban untuk membandingkan alamat IP yang digunakan saat pembuatan API dengan riwayat login mereka sendiri\nUngkap alamat IP pusat data yang terkait dengan infrastruktur bot phishing dan perjudian yang telah diketahui\nMenyajikan bukti yang dapat digunakan dalam proses hukum perdata atau pidana terhadap pelaku\nTunjukkan apakah pemegang akun telah diberi tahu saat kunci tersebut dibuat\nFakta yang tercatat: Valve menyimpan catatan tingkat perangkat dan korelasi akun — hal ini dijelaskan dalam surat penasihat hukumnya tertanggal 1 Oktober 2025 (lihat Lampiran A, Memorandum Bukti — Sumber 1). Dalam tiket HT-2YBP-F7JP-D4VB, jenis catatan yang sama diminta oleh subjek data dan tiket tersebut ditutup dengan rujukan ke halaman layanan mandiri yang, menurut laporan subjek data, tidak memuat catatan tersebut. Apakah penolakan tersebut sah merupakan pertanyaan bagi otoritas pengawas; akibatnya, orang yang bersangkutan tidak memperoleh data tersebut.\nPercakapan itu — empat pesan, tiga hari\n\nDua agen dukungan Steam membalas dengan menggunakan nama depan yang tertera di tiket: \"Logen\" pada 17 September dan \"Kal\" pada 19 September. Keduanya mengarahkan pemohon ke halaman Data Akun. Tidak ada informasi dalam tiket yang menunjukkan apakah permintaan tersebut sampai ke Tim Privasi atau Petugas Perlindungan Data Valve, dan berkas tersebut tidak menyebutkan siapa agen-agen tersebut, apa peran mereka, atau bagaimana tiket tersebut diteruskan.\n\n16 SEP\nPermohonan berdasarkan Pasal 15 yang diajukan dengan mencantumkan empat kategori data\n17–18 SEP\nRujukan ke Data Akun; pemohon meminta agar masalah ini diteruskan ke DPO\n19 SEP\nTiket ditutup dengan rujukan yang sama; tidak ada data, tidak disebutkan alasannya\nHak apa yang secara eksplisit diberikan kepada subjek data berdasarkan Pasal 15 GDPR\nPasal 15 ayat (1) huruf aTujuan pemrosesan — mengapa Valve menyimpan data tersebut\nPasal 15 ayat (1) huruf bKategori data — apa yang terkandung dalam Valve\nPasal 15 ayat (1) huruf cPenerima atau kategori penerima — siapa yang menerima data tersebut (misalnya, pemegang kunci API)\nPasal 15 ayat (1) huruf dJangka waktu penyimpanan atau kriteria untuk menentukannya\nPasal 15 ayat (3)Salinan data pribadi yang sedang diproses — yaitu, log kunci API itu sendiri\nPasal 12 ayat (3)Diperlukan tanggapan dalam waktu satu bulan sejak tanggal penerimaan; permohonan perpanjangan harus disampaikan dalam bulan tersebut. Jangka waktu tersebut belum berakhir pada saat publikasi. Pasal 12 ayat (4): Jika pengawas tidak mengambil tindakan, ia harus menjelaskan alasannya dan memberi tahu pihak yang bersangkutan mengenai jalur pengaduan yang tersedia.\nProsedur pengaduan terkait peraturan — untuk semua pengguna\n\nSetiap pengguna yang telah mengajukan permohonan berdasarkan Pasal 15 GDPR kepada Valve dan tidak menerima tanggapan yang sesuai (atau penolakan dalam bentuk templat tanpa data) dapat mengajukan pengaduan kepada otoritas pengawas di negara anggota UE/EEA masing-masing. Cabang Valve di Uni Eropa adalah Valve GmbH di Hamburg, sehingga otoritas pengawas utama untuk pengaduan lintas batas adalah Pejabat Hamburg untuk Perlindungan Data dan Kebebasan Informasi (HmbBfDI). (Perwakilan Pasal 27 Valve juga berkedudukan di Hamburg; alamat seorang perwakilan tidak secara otomatis menentukan otoritas yang berwenang.) Pengaduan juga dapat diajukan kepada otoritas di negara anggota tempat pengadu berkedudukan berdasarkan Pasal 77.\n\nFormulir pengaduan HmbBfDI ↗ Teks GDPR (Pasal 12, 15, 77) ↗ diarsipkan 2026-09-20 ↗Pedoman EDPB ↗\n\nNomor referensi tiket untuk setiap keluhan: HT-2YBP-F7JP-D4VB — disimpan dalam berkas ini sebagai contoh yang tercatat.\n\nSatu contoh yang tercatat\nCatatan-catatan tersebut memang ada; namun, subjek data tidak menerimanya.\n\nPengacara Valve menjelaskan catatan korelasi tingkat perangkat dalam surat tertanggal 1 Oktober 2025. Pada 19 September 2026, permohonan berdasarkan Pasal 15 untuk jenis catatan yang sama ditutup dengan rujukan ke halaman layanan mandiri yang dilaporkan oleh pemohon tidak memuat catatan tersebut, tanpa dasar hukum yang disebutkan. Tiket HT-2YBP-F7JP-D4VB adalah salah satu contoh yang terdokumentasi; apakah hal ini mencerminkan praktik yang lebih luas merupakan pertanyaan bagi otoritas pengawas, yang dapat meminta Valve untuk menyerahkan catatan penanganannya.\n\nPasal 12, 15, dan 77 GDPR / Otoritas Pengawas\n\nPengaduan berdasarkan Pasal 12 dan 15 dapat diajukan langsung kepada otoritas pengawas yang berwenang tanpa biaya (Pasal 77). Otoritas tersebut dapat menjatuhkan tindakan korektif, termasuk perintah untuk memenuhi permintaan akses, serta denda berdasarkan Pasal 83(5)(b) atas pelanggaran hak subjek data. Menyimpan referensi tiket asli dan respons Valve (atau ketiadaannya) akan memperkuat pengaduan tersebut.\n\nLihat templat DSAR →\nBagian C — Kerangka hukum · Pasal 19 · Hukum kontrak\nPerjanjian Pelanggan yang bertentangan dengan arsitektur platform itu sendiri\nKonteks & batasan sumber\n\nPara penulis bukanlah pengacara dan semua uraian ini bukanlah nasihat hukum. Kutipan SSA diambil dari revisi tanggal 10 September 2026; revisi yang berbeda mungkin memiliki redaksi yang berbeda pula, dan penomoran pasal telah berubah dari satu revisi ke revisi lainnya — periksa pasal tersebut berdasarkan versi yang berlaku pada saat terjadinya perilaku yang dimaksud. Argumen Pasal 25 dan 32 menyatakan apa yang diwajibkan oleh peraturan tersebut, bukan bahwa otoritas pengawas telah menemukan adanya pelanggaran. Angka-angka dalam Argumen 1 mencakup batasan ruang lingkup yang ditetapkan dalam Bagian 13.\n\nTiga ketentuan utama SSA tampak tidak selaras dengan cara platform ini dibangun: larangan penggunaan komersial yang dipadukan dengan batasan harga di Market yang mendorong penjualan bernilai tinggi keluar dari platform; klausul tanggung jawab pengguna terkait kunci API yang bertentangan dengan titik akhir kunci yang, sebelum tahun 2023, tidak memerlukan otentikasi dua faktor; serta bahasa penegakan hukum yang bertentangan dengan catatan publik yang menunjukkan tidak adanya penegakan hukum per operator. Apakah ketegangan-ketegangan ini memengaruhi keberlakuan hukum merupakan pertanyaan yang harus dijawab oleh pengadilan; bagian ini menguraikan fakta-fakta yang akan dihadapi pengadilan.\n\nArgumen 1 / Arsitektur Kapitalisasi Pasar\nBatas atas harga pasar dan larangan penggunaan untuk keperluan komersial\n\nPasar Komunitas Steam memiliki batas atas harga penawaran sekitar $1,800. Di lima pasar yang tercatat dalam cuplikan data per tanggal 23 September 2026, terdapat 248 kategori barang CS2 yang harganya ditetapkan secara terpisah di atas batas atas tersebut oleh dua atau lebih pasar; barang-barang tersebut tidak dapat dijual dengan harga tersebut di platform milik Valve sendiri. Pemilik yang menginginkan harga-harga tersebut menggunakan pasar pihak ketiga, yang beroperasi melalui akun Steam dan API Steam — penggunaan tersebut diklasifikasikan oleh SSA sebagai kegiatan komersial kecuali jika secara tegas diizinkan.\n\nBarang-barang melebihi batas atas Pasar → pasar pihak ketiga mengisi kekosongan tersebut → pasar-pasar tersebut menggunakan akun Steam dan API Steam → SSA melarang penggunaan komersial tanpa izin → belum ada daftar izin yang dipublikasikan. Biaya gabungan Pasar Komunitas sebesar sekitar 15% hanya berlaku untuk penjualan yang diselesaikan di dalam Pasar, bukan untuk transaksi eksternal ini.\nArgumen 2 / Arsitektur Keamanan Kunci API\nKerentanan kunci API merupakan masalah desain platform, bukan kelalaian pengguna\n\nSebelum tahun 2023, titik akhir pembuatan kunci API Steam menerima permintaan POST yang menggunakan sessionid yang dicuri dan menghasilkan kredensial dengan hak akses tinggi tanpa konfirmasi melalui email, otentikasi dua faktor, atau verifikasi perangkat. Keluhan-keluhan terkait pembajakan API yang dikumpulkan dalam penyelidikan ini mengikuti pola yang sama: skrip penyerang, cookie sesi yang dicuri, pembuatan kunci secara diam-diam, serta intersepsi transaksi (isi permintaan ditampilkan pada Bagian 8).\n\nPasal 25 GDPR (perlindungan data sejak tahap perancangan) dan Pasal 32 (keamanan pemrosesan) mensyaratkan penerapan langkah-langkah teknis yang sesuai dengan tingkat risiko. Penerbitan kredensial yang memungkinkan penyadapan transaksi tanpa faktor otentikasi kedua atau pemberitahuan kepada pemilik merupakan masalah desain bagi pengendali data. Apakah klausul SSA yang membebankan tanggung jawab kepada pengguna dapat diandalkan dalam konteks tersebut merupakan pertanyaan yang harus diputuskan oleh pengadilan dan otoritas pengawas.\n\nArgumen 3 / Visibilitas Real-Time\nValve menerima nama host otentikasi pada setiap proses masuk\n\nNama host otentikasi diterima di titik akhir OpenID milik Valve dalam bentuk teks biasa di openid.return_to dan openid.realm (bentuk permintaan tersebut ditampilkan pada Bagian 3). Mengekstraknya merupakan operasi standar. Per tanggal 2026-09-22, pada 26 pasangan, domain utama terdaftar di Link Filter, sedangkan host yang menggunakan login Steam-nya tidak terdaftar di sana. Valve belum menerbitkan catatan penegakan per operator, sehingga tidak dapat dipastikan dari data publik apakah ada tindakan selain Link Filter yang telah diterapkan pada host-host tersebut.\n\nSiapa yang menanggung biayanya?\nPola yang terlihat dalam pengaduan yang telah diarsipkan\n\nDalam pengaduan yang ditinjau, tanggapan Tim Dukungan terhadap klaim pembajakan kunci API selalu mengikuti pola yang sama: menolak permintaan pemulihan, menegaskan bahwa pengguna bertanggung jawab atas akun dan kunci API-nya, serta menutup tiket. Tidak ada perkiraan angka agregat mengenai jumlah akun yang terdampak atau nilai kerugian dalam dokumen ini; sumber untuk angka tersebut juga belum ditemukan.\n\nPertanyaannya bukanlah apakah pengguna individu melakukan kesalahan. Pertanyaannya adalah siapa yang bertanggung jawab atas arsitektur yang, hingga tahun 2023, memungkinkan permintaan POST dengan cookie yang dicuri untuk membuat kredensial perdagangan dengan hak akses tinggi tanpa pemberitahuan dan tanpa otentikasi dua faktor.\nSSA sebagai dokumen vs SSA sebagai perjanjian\nPengadilan yang menelaah berkas ini tidak akan menafsirkan SSA secara terpisah.\n\nDokumen tersebut akan dibaca bersamaan dengan surat penasihat hukum tertanggal Oktober 2025 yang menjelaskan korelasi pada tingkat perangkat, tanggal pendaftaran host otorisasi, cap waktu pendaftaran batch, muatan permintaan kunci API, serta rentang waktu sepuluh tahun antara pemberitahuan Juli 2016 dan platform-platform yang masih beroperasi pada September 2026. Itulah catatan yang harus ditanggapi oleh Valve.\n\nSSA versus catatan / poin-poin utama\n\"Tidak untuk penggunaan komersial\" — batasan Pasar ini mendorong penjualan bernilai tinggi ke pasar pihak ketiga yang bersifat komersial\n\"Pengguna bertanggung jawab atas kunci API\" — tidak ada otentikasi dua faktor pada titik akhir kunci sebelum tahun 2023\n\"Kami menindak para pelanggar\" — tidak ada catatan penegakan hukum per operator yang dipublikasikan sejak Juli 2016\n\"Anda telah menyetujui persyaratannya\" — dalam pola penyanderaan, persetujuan tersebut dikirimkan oleh sebuah skrip, bukan oleh pemilik akun\nKesimpulan · Apa yang dibuktikan oleh bukti-bukti dan apa yang kami ajukan\nHasil penelitian. Dokumen-dokumen yang kami minta.\nKonteks & batasan sumber\n\nSetiap temuan di bawah ini terkait dengan catatan publik bertanggal yang tercantum pada bagian-bagian di atas. Permohonan-permohonan tersebut ditujukan kepada pihak berwenang yang dapat memaksa akses terhadap satu hal yang tidak dapat dijangkau oleh penyelidikan ini: catatan penegakan hukum, akses, dan pemrosesan milik Valve sendiri.\n\nSetiap permintaan didasarkan pada temuan yang telah ditetapkan tanggalnya. Pihak berwenang dapat meminta dokumen-dokumen yang tidak dapat dipaksakan dalam penyelidikan berbasis sumber terbuka ini.\n\nApa yang tercantum dalam catatan publik\n44 platform aktif melakukan otentikasi melalui domain terdaftar yang terpisah — 27 di antaranya memiliki berkas bukti per rute yang dipublikasikan, sedangkan 17 lainnya diperoleh melalui pengumpulan manual dan dicantumkan secara terpisah. Per tanggal 2026-09-22, 26 pasangan memiliki domain utamanya diblokir di Steam Link Filter sementara host yang menampung login-nya tidak diblokir — csgogem.com diblokir, api.csgem.com terdaftar sejak Maret 2014. Steam menerima nama host tersebut di openid.realm dan openid.return_to setiap kali masuk. Bagian 3\nPada tanggal 13 Juli 2016, Valve secara terbuka menyebutkan mekanisme tersebut dan melarangnya, dan pemberitahuan dari penasihat hukumnya tertanggal 20 Juli 2016 menetapkan batas waktu sepuluh hari. Tidak ada catatan penegakan hukum per operator yang dipublikasikan dalam sepuluh tahun sejak batas waktu tersebut. Bagian 11\nTitik akhir kunci API Web Steam menerbitkan kredensial dengan hak akses tinggi yang dapat digunakan untuk bertransaksi hanya berdasarkan cookie sesi, tanpa otentikasi dua faktor sebelum tahun 2023. Bagian 5\nPermohonan berdasarkan Pasal 15 GDPR (tiket HT-2YBP-F7JP-D4VB) ditutup setelah tiga hari dengan menyertakan tautan ke layanan mandiri dan tanpa data apa pun. Pasal 18\nApa yang kami minta kepada setiap pihak berwenang\nKomisi Perjudian Negara Bagian Washington\nBuka kembali berkas tahun 2016. Minta rincian per operator mengenai akun, bot, dan host pengirim mana saja yang dinonaktifkan setelah pemberitahuan sepuluh hari, serta operator mana saja yang kemudian mendapatkan kembali aksesnya. Bagian 2\nHmbBfDI (Hamburg; Valve GmbH)\nPeriksa apakah tanggapan berdasarkan Pasal 15 telah memenuhi kewajiban pengendali data, dan minta agar diungkapkan catatan pendaftaran dan akses kunci API yang relevan untuk mengidentifikasi pelaku. Pasal 18\nKoordinator Layanan Digital DSA\nTandai rute auth-host pada catatan tersebut sebagai pemberitahuan, lalu nilai apakah tanggapan Valve telah memenuhi kewajibannya setelah informasi tersebut didokumentasikan. Bagian 16\nSetiap subjek data\nGunakan templat Pasal 15 untuk meminta catatan yang sama atas nama Anda sendiri; catatan yang disimpan dapat digunakan untuk mengetahui siapa yang memulai proses reset atau membuat kunci. Lampiran G\n\nTuntutan tunggal di balik keempat hal tersebut sama: mempublikasikan catatan penegakan, akses, dan pemrosesan yang hanya dimiliki oleh Valve. Peringatan di laman beranda, surat tenggat waktu sepuluh hari, dan laman layanan mandiri merupakan bentuk-bentuk penegasan kendali. Apakah kendali tersebut benar-benar dijalankan merupakan pertanyaan yang tidak dapat dijawab oleh catatan publik, namun dapat dijawab oleh pihak regulator.\n\nLampiran — bukti utama dan bahan kerja\nLampiran A — Korespondensi dengan penasihat hukum\nMemorandum Bukti — bahan yang disediakan oleh Sumber 1\n\nDasar bukti dan status sumber untuk korespondensi penasihat hukum yang dijadikan rujukan dalam Pasal 1, 18, dan 19.\n\nDasar Bukti dan Status Sumber — dokumen yang disediakan oleh Sumber 1\nPengguna yang larangan permanennya memicu audit ini bukanlah subjek dari audit tersebut. Apakah larangan tersebut beralasan atau tidak, tidak dibahas di sini, dan dokumen ini tidak membela maupun membantahnya. Akun tersebut bukanlah intinya. Yang penting adalah materi: Sumber 1 — Pemilik akun yang diblokir, yang menerima surat-menyurat di bawah ini dari penasihat hukum Valve sebagai subjek data dalam permohonan GDPR-nya sendiri — telah meneruskan surat-menyurat tersebut beserta berkas perkara yang menyertainya, disertai hak untuk memeriksanya secara terbuka. Namanya dirahasiakan; dokumen-dokumen tersebut diidentifikasi berdasarkan tanggal, metadata pembuat, dan hash.\n\nKorespondensi tersebut dikirim sebagai tanggapan atas permintaan berdasarkan GDPR/DSAR. Dalam prosesnya, penasihat hukum Valve mencantumkan sebuah pernyataan dalam catatan resmi, yang ditandatangani, yang menjelaskan suatu kemampuan yang sebelumnya telah disampaikan oleh Tim Dukungan Steam kepada para pengguna sebagai hal yang secara teknis tidak mungkin dilakukan. Paragraf yang dikutip di bawah ini adalah pernyataan tersebut.\n\nAnalisis lebih lanjut yang dilakukan para penulis terhadap ekstrak log yang dihasilkan adalah tidak dimuat dalam berkas ini masih menunggu hasil tinjauan independen. Temuan ini tidak dijadikan acuan oleh bagian lain mana pun dalam penyelidikan ini.\n\nPengakuan yang tercatat: telemetri tingkat perangkat yang berkelanjutan\n\nDalam paragraf 1.9 surat yang dikaitkan dengan penasihat hukum Valve, para pengacara Valve menyatakan: \"Antara tahun 2019 dan 2023, akun ini sebagian besar diakses melalui perangkat yang juga digunakan untuk masuk ke puluhan akun Steam yang dicuri.\"\n\nFaktanya: Valve Penasihat hukum di sini menjelaskan korelasi pada tingkat perangkat di seluruh akun selama empat tahun. Steam Tim dukungan telah memberi tahu para korban pencurian bahwa melacak barang yang dicuri atau menghubungkan akun dengan perangkat secara teknis tidak memungkinkan. Steam Guard Otorisasi perangkat telah didokumentasikan secara publik, sehingga keberadaan catatan per perangkat itu sendiri bukanlah hal baru; yang baru adalah konfirmasi tertulis dari penasihat hukum bahwa catatan-catatan tersebut disimpan dan dikorelasikan di seluruh akun selama periode bertahun-tahun.\n\nMengapa hal ini penting: Korelasi yang dapat menghubungkan satu perangkat dengan puluhan akun yang dibajak selama empat tahun termasuk dalam kategori catatan yang sama yang menurut pihak Dukungan tidak dapat digunakan untuk para korban. Catatan dari kelas tersebut berpotensi mengidentifikasi akun dan perangkat dalam rantai pencurian dan penjualan kembali. Catatan apa saja yang ada, berapa lama disimpan, dan atas dasar apa data tersebut tidak diungkapkan kepada subjek data merupakan pertanyaan yang harus dijawab oleh otoritas pengawas.\n\nSumber: surat dari penasihat hukum Valve tertanggal 1 Oktober 2025, paragraf 1.9, beserta lampiran PDF-nya yang berjumlah 830 halaman · diterima oleh Sumber 1 sebagai tanggapan atas permohonan berdasarkan Pasal 15 GDPR · nilai SHA-256 dari lampiran tersebut tercatat dalam disclosure-audit.json · Surat tersebut tidak dicantumkan; nama akun dan data pihak ketiga dihilangkan.\n\nStatus: buka\nBahan-bahan sumber tersedia melalui arsip bukti.\nLampiran B — Berkas PDF yang dihasilkan · pemeriksaan penyuntingan\nPengeditan pada file PDF yang dihasilkan bersifat kosmetik: teks yang disamarkan tetap dapat diekstraksi\n\nPihak kuasa hukum Valve menanggapi permohonan akses berdasarkan GDPR dengan lampiran setebal 830 halaman, di mana bagian yang disensor ditutupi dengan cat di atas teks alih-alih dihapus. 902,270 karakter berada di bawah garis-garis hitam dan langsung muncul menggunakan alat ekstraksi teks — termasuk pengenal pihak ketiga yang seharusnya disembunyikan oleh batang-batang tersebut. Di sini hanya dipublikasikan jumlah agregat; tidak ada konten yang tercakup yang disalin, dan lampiran itu sendiri tidak dipublikasikan.\n\n1. Hasil pemeriksaan geometri\n\nTanggapan berdasarkan Pasal 15 GDPR tertanggal 1 Oktober 2025 dilengkapi dengan lampiran PDF setebal 830 halaman (metadata pembuat Aspose.PDF untuk .NET, dibuat dan diubah pada tanggal yang sama). Para penulis melakukan pemeriksaan geometri pada tingkat halaman: untuk setiap halaman, persegi panjang buram berwarna hampir hitam yang digambar di atas lapisan teks diidentifikasi, dan karakter yang dapat diekstraksi yang berada di bawahnya dihitung.\n\nDiukur berdasarkan berkas yang dihasilkan\n902,270\nKarakter-karakter tersebut masih dapat diekstraksi dari bawah bilah hitam\nDihitung, bukan diperkirakan. Ini adalah jumlah karakter yang tercakup — bukan jumlah korban, kasus identifikasi ulang, atau insiden.\n830 / 830\nHalaman yang terpengaruh — setiap halaman\n986\nPersegi panjang di atas teks yang dapat diekstraksi\n1,329\nJumlah persegi panjang hitam buram\nGaris-garis hitam tersebut digambar di atas lapisan teks; garis-garis tersebut tidak menghapusnya. Teks yang berada di bawah garis-garis tersebut dapat diekstraksi menggunakan alat PDF standar. Hanya jumlah agregat yang dipublikasikan; tidak ada konten yang disembunyikan yang dicantumkan di sini.\nDemonstrasi Forensik: Pemisahan Lapisan\nASPOSE.PDF UNTUK .NET: MODEL TAMPILAN LAPISAN VEKTOR (LAMPIRAN HAL. 412)\n\nLaporan yang diajukan terhadap akun: [LOGIN: redacted_user_667]\n\nAlasan yang disampaikan oleh pengguna: [TEKS: \"Pengguna melaporkan adanya barang ganda dalam inventaris dan praktik perdagangan yang tidak etis...\"]\n\nLatar depan: <path fill=\"#000\" />Kelemahan: Aliran UTF-8 yang mendasarinya tetap utuh\nSumber: Lampiran PDF dari surat penasihat tanggal 1 Oktober 2025 (830 halaman, metadata dari Aspose.PDF for .NET) · dihitung oleh para penulis, metode, dan jumlah per halaman dalam disclosure-audit.json · Nilai SHA-256 dari lampiran yang tercantum dalam berkas yang sama · lampiran itu sendiri tidak dipublikasikan.\n2. Mengapa hal ini penting bagi tanggapan subjek data\n\nPengacara Valve mengirimkan berkas ini kepada subjek data sebagai tanggapan atas permohonan untuk mendapatkan catatan milik orang tersebut. Garis-garis yang ada di sana hanya bersifat kosmetik: teks di bawahnya tidak pernah dihapus, sehingga pengenal pihak ketiga yang disembunyikan dengan garis-garis tersebut tetap diteruskan kepada penerima bersama dengan berkas tersebut. Penyensoran yang dapat dihilangkan dengan alat ekstraksi teks tidak menyembunyikan apa pun, dan hal itu juga membuat penerima tidak dapat menentukan bagian mana yang diungkapkan dan bagian mana yang tidak.\n\nPasal 15 ayat (4) adalah alasan mengapa pembatasan-pembatasan tersebut ada: hak untuk memperoleh salinan tidak boleh merugikan hak dan kebebasan orang lain. Itulah kewajiban yang tidak dipenuhi oleh produksi ini. Apakah hal ini dikategorikan sebagai pelanggaran data pribadi berdasarkan Pasal 4 ayat (12) merupakan kewenangan otoritas pengawas untuk menentukannya; pengungkapan itu sendiri dapat diukur dalam berkas, dan dapat direproduksi oleh siapa pun yang memiliki byte yang sama — SHA-256 telah dipublikasikan, sedangkan lampirannya tidak.\n\nYang ada di balik jeruji itu bukanlah nomor rekening. Itu adalah kumpulan laporan pengguna yang diajukan terhadap pemohon, beserta nama-nama pembuatnya: Steam kali login yang, karena suatu akun login jarang hanya digunakan pada Steam, mengidentifikasi orang di baliknya — menurut perhitungan para penulis, lebih dari 60% pengguna yang disebutkan dalam dokumen tersebut dapat diidentifikasi sepenuhnya — beserta teks mentah yang belum disunting dari apa yang mereka tulis. Teks tersebut berisi ancaman pembunuhan dan hinaan yang ditujukan kepada kebangsaan pemohon. Beberapa orang yang teridentifikasi tersebut masih di bawah umur. Pihak produksi menyerahkan daftar nama-nama wartawan kepada orang yang telah mereka laporkan, yang merupakan kerugian tepat yang dimaksudkan untuk dicegah oleh Pasal 15 ayat (4).\n\nUrutan karakter di sekitar berkas tersebut sama pentingnya dengan isinya. Permohonan tersebut awalnya ditanggapi dengan permintaan bukti identitas tambahan, dengan alasan bahwa alamat email alias pemohon tidak mencantumkan namanya; akun tersebut diblokir secara permanen selama penundaan yang terjadi setelahnya. Surat yang akhirnya mengirimkan data tersebut, lebih dari enam minggu setelah batas waktu satu bulan sesuai Pasal 12(3), mengancam penerima dengan tuntutan pidana dan menahan sisa datanya sendiri hingga ia menjelaskan aktivitas akunnya kepada penasihat hukum. Pengungkapan tersebut juga menjawab dua pertanyaan yang belum dijawab Valve di depan umum: catatan yang dihasilkan menunjukkan adanya penghubungan akun yang sudah terjadi sejak tahun 2019, serta telemetri internal dengan kedalaman yang belum pernah dijelaskan oleh Valve.\n\nRuang lingkup bagian ini: Pengamatan di sini terbatas pada mekanisme penyuntingan, yang diukur berdasarkan berkas yang dihasilkan. Analisis lebih lanjut yang dilakukan para penulis terhadap catatan log yang dihasilkan ditunda hingga dilakukan tinjauan independen dan tidak dijadikan acuan di bagian lain dalam dokumen ini.\n\nBukti: surat kuasa tanggal 1 Oktober 2025 beserta lampiran PDF-nya (SHA-256 tercatat dalam berkas audit); Pengukuran PDF pada tingkat halaman dan metodenya ↗. Urutan permohonan, penolakan pada halaman 8, dan deskripsi catatan yang terungkap dijelaskan secara lengkap dalam keterangan PhishDestroy, “Anjingku vs. Pengacara Ahli GDPR”, 17 Agustus 2026 ↗ diarsipkan 2026-08-21 ↗. Nama akun dan data pihak ketiga tidak dicantumkan di sini; tidak ada informasi yang tertutupi oleh garis-garis tersebut yang ditampilkan.\n\nPada halaman 8 surat pengantar tersebut, sebagian permohonan ditolak, dan alasannya dijelaskan secara tertulis: Informasi yang lebih rinci tidak dapat diberikan karena pertimbangan perlindungan data pribadi pengguna lain di platform Steam… — jawaban yang lebih rinci tidak mungkin diberikan, karena data pribadi pengguna Steam lainnya harus dilindungi. Lampiran setebal 830 halaman itu terdapat dalam paket yang sama. Yang disamarkan bukanlah nomor akun: melainkan laporan yang diajukan terhadap pemohon, dengan nama penulisnya disebutkan, serta pesan mentah yang belum disunting terlampir. Pemegang akun telah meminta Valve, melalui penasihat hukumnya, untuk berkasnya sendiri; namun yang dapat ia peroleh dari berkas tersebut justru berkas milik orang lain. Tidak ada satu pun dalam lampiran ini yang bergantung pada siapa yang menggambar kotak-kotak tersebut. Yang ditetapkan di sini adalah bahwa perlindungan Valve yang diajukan sebagai dasar penahanan informasi tersebut adalah perlindungan yang gagal dipenuhi oleh penyerahan dokumen ini sendiri, dalam amplop yang sama, pada hari yang sama.\nBukti-bukti dalam Surat-surat Dukungan dan Hukum\n\nSumber: https://phishdestroy.io/steam_dossier/id/index#exhibit-gallery-section\n\nLampiran D — Pengumpulan sumber\nCatatan primer yang dipilih\n\nEnam catatan dari arsip — tiga masalah GitHub di pelacak Valve dan tiga akun Reddit yang berisi hasil dukungan yang diperdebatkan. Setiap sumber tetap dilampirkan pada klaim tersebut, teks yang disimpan, dan pertanyaan yang muncul darinya.\n\n1 / 6 catatan terpilih\nPilih catatan sumber\nGH-01 / GITHUBBuka dalam build yang telah disimpan\nKunci perangkat keras, yang diminta pada tahun 2016\n\nValveSoftware / steam-for-linux · #4521 · 2016-06-27\n\nSeorang pengguna meminta Valve untuk mendukung kunci perangkat keras U2F sebagai faktor kedua alternatif. Masalah yang telah disimpan tersebut memiliki label “Permintaan Fitur” dan “Telah Ditinjau”, dengan statusnya tercatat sebagai “terbuka”.\n\nSaya meminta agar Steam mendukung dongle USB U2F sebagai alternatif.\n\nKutipan dari isu GitHub ↗\nCatatan tertulis\nSebuah permintaan yang sudah kadaluwarsa mengenai langkah pengamanan tambahan untuk akun, yang dipublikasikan di sistem pelacakan masalah milik Valve dan diberi label \"telah ditinjau\".\nTuntutan akuntabilitas\nPublikasikan keputusan produk, tanggal tanggapan, dan perlindungan yang diberikan setelah peninjauan.\nMembaca catatan yang telah disimpan →Buka GitHub ↗\nDalam dokumen ini: Langkah-langkah pengamanan akun →Arsip #484 · build 2026-09-17\nGH-02 / GITHUBBuka dalam build yang telah disimpan\nLaporan kecelakaan tanpa opsi penolakan yang efektif\n\nValveSoftware / steam-for-linux · #6459 · 2019-08-18\n\nReporter tersebut menjelaskan kasus klien Steam pada tanggal 12 Agustus 2019 di Ubuntu 16. Ia menyebutkan bahwa penonaktifan tujuan crash-upload tidak bertahan setelah sistem di-restart, dan menyertakan konfigurasi yang bersangkutan.\n\nJika saya menonaktifkan `ServerURL`, pengaturannya akan ditimpa setiap kali sistem di-reboot.\n\nKutipan dari isu GitHub ↗ diarsipkan 2026-04-19 ↗\nCatatan tertulis\nKeluhan privasi spesifik yang mencantumkan tanggal klien, sistem operasi, dan cuplikan konfigurasi. Masalah yang telah disimpan tersebut masih dalam status terbuka.\nTuntutan akuntabilitas\nIdentifikasi penyelidikan, build yang terdampak, dan perubahan yang membuat opsi penolakan tersebut berlaku.\nMembaca catatan yang telah disimpan →Buka GitHub ↗diarsipkan 2026-04-19 ↗\nDalam berkas ini: Ajukan permohonan untuk mendapatkan dokumen pendukung →Arsip #467 · build 2026-09-17\nGH-03 / GITHUBBuka dalam build yang telah disimpan\nTindakan penyalahgunaan tiket otentikasi dilaporkan ke Valve\n\nValveSoftware / Source-1-Games · #3857 · 2022-02-26\n\nPenulis menuduh bahwa pengoperasian server menyimpan Steam tiket otentikasi setelah para pemain terputus dari koneksi dan menggunakan daftar server yang menyesatkan. Postingan tersebut meminta Valve untuk menanggapi perilaku tersebut.\n\nMembuat server mereka tampak ramai.\n\nKutipan dari isu GitHub ↗\nCatatan tertulis\nSebuah laporan pelecehan yang diajukan secara publik di pelacak Valve pada tanggal 26 Februari 2022. Status tersimpannya adalah 'terbuka'; laporan tersebut memuat tautan ke tangkapan layar.\nTuntutan akuntabilitas\nSusunlah hasil investigasi dan catatan tindakan mitigasi terkait penyalahgunaan tiket otentikasi yang dilaporkan.\nMembaca catatan yang telah disimpan →Buka GitHub ↗\nDalam dokumen ini: Cakupan kumpulan data →Arsip #768 · build 2026-09-17\nRD-01 / REDDITProfil Penulis\n44 transaksi pembelian di Pasar yang menjadi sengketa\n\nr/DotA2 · nama pengguna penulis dirahasiakan · 2022-07-07\n\nPenulis melaporkan 44 transaksi pembelian tanpa izin di Market pada tanggal 6 Juli 2022 dan kerugian sekitar $500+. Ia menyebutkan bahwa otentikasi dua faktor telah diaktifkan dan menjelaskan bahwa pihak dukungan pelanggan terus-menerus mengirimkan balasan yang menggunakan templat.\n\nIni sudah tiket kedua yang saya ajukan, namun saya masih belum menerima balasan dari Steam yang bukan sekadar salinan-tempel templat otomatis.\n\nKutipan dari postingan Reddit ↗ diarsipkan 2025-03-20 ↗\nCatatan tertulis\nCatatan yang sudah lama mengenai pembelian yang dipermasalahkan, lengkap dengan tautan ke tangkapan layar transaksi dan tanggapan dari tim dukungan. Jumlah dan kejadian yang disebutkan merupakan laporan dari penulis.\nTuntutan akuntabilitas\nSelaraskan pembelian yang dipermasalahkan dengan catatan transaksi dan sesi. Jelaskan bukti yang mendasari keputusan tim dukungan.\nMembaca catatan yang telah disimpan →Buka Reddit ↗diarsipkan 2025-03-20 ↗\nDalam dokumen ini: Dukungan dan penegakan →Arsip #4,533 · build 2026-09-17\nRD-02 / REDDITProfil Penulis\nLarangan permanen dan penutupan jalur banding\n\nr/ohnePixel · nama pengguna penulis dirahasiakan · 2024-12-09\n\nPenulis membantah adanya larangan permanen dan menyatakan bahwa alasan larangan tersebut didasarkan pada dugaan transfer akun serta laporan dari komunitas. Ia menjelaskan mengenai tiket yang telah ditutup dan rencananya untuk meminta data pribadinya.\n\nSaya telah menjelaskan situasi saya dan meminta penjelasan lebih lanjut, tetapi mereka tetap pada keputusan mereka dan menutup tiket-tiket saya.\n\nKutipan dari postingan Reddit ↗\nCatatan tertulis\nSebuah catatan permohonan yang disimpan, termasuk alasan-alasan yang menurut penulis mendukung permohonan tersebut serta tautan ke empat gambar. Tanggal posting diambil dari ekspor data dukungan yang dipilih.\nTuntutan akuntabilitas\nIdentifikasi bukti-bukti yang mendukung larangan permanen tersebut serta mekanisme peninjauan yang tersedia untuk menggugatnya. Penutupan proses banding tidak menjelaskan alasan di balik keputusan tersebut.\nMembaca catatan yang telah disimpan →Buka Reddit ↗\nDalam berkas ini: Minta dokumen pendukungnya →Arsip #4,766 · build 2026-09-17\nRD-03 / REDDITProfil Penulis\nReset pemulihan dan kerugian yang dilaporkan sebesar $10,000\n\nr/legaladvice · nama pengguna penulis dirahasiakan · 2025-05-09\n\nPenulis menuduh bahwa tim dukungan mereset kredensial dan menonaktifkan perlindungan akun setelah seseorang mengajukan tiket pemulihan. Mereka melaporkan adanya kerugian sebesar sekitar US$10,000 dari akun yang tidak aktif.\n\nSteam Layanan Dukungan telah mereset kata sandi saya dan menonaktifkan semua pengaturan keamanan akun saya.\n\nKutipan dari postingan Reddit ↗\nCatatan tertulis\nSebuah tuduhan yang masih tersimpan mengenai proses pemulihan yang mengabaikan mekanisme pengamanan akun. Postingan yang disimpan tersebut mencatat apa yang, menurut penulis, disampaikan oleh tim dukungan kepada mereka.\nTuntutan akuntabilitas\nIdentifikasi siapa yang mengizinkan proses reset tersebut, bukti kepemilikan yang mereka terima, serta catatan aksesnya. Pemulihan akun merupakan bagian dari kontrol sistem keamanan Valve.\nMembaca catatan yang telah disimpan →Buka Reddit ↗\nDalam berkas ini: Minta dokumen pendukungnya →Arsip #4,592 · build 2026-09-17\n\nEnam catatan terpilih. Deskripsi di GitHub menjelaskan hasil build yang disimpan. Postingan di Reddit menyimpan keterangan dari para penulisnya.\n\nUnduh keenam rekaman tersebut ↓\n\nBuild yang dapat dicari ini berisi 16,319 catatan yang berbeda: 393 Trustpilot, 5,635 Reddit, 2,395 GitHub, 276 catatan web, dan 7,620 catatan wiki. Beberapa catatan dapat berkaitan dengan peristiwa yang sama. Ekspor utama terpisah yang terdiri dari 40,448 baris memiliki cakupan yang berbeda.\n\nTelusuri arsip lengkap ↗ · Buat manifes ↗ · Cakupan dan jumlah dataset →\n\nLampiran E — Studi kasus\nArchiSteamFarm dan klausul otomatisasi\n\nSebuah alat open-source untuk mengumpulkan kartu yang, menurut FAQ-nya sendiri, dijalankan pada jutaan akun, bertentangan dengan klausul Perjanjian Pelanggan (§ 4.C) yang melarang penggunaan otomatisasi. Mekanisme — apa yang harus dibeli oleh sebuah farm dari Valve sebelum dapat menghasilkan apa pun, mengapa setiap cara mencairkan dana dari kartu melanggar lisensi, catatan penegakan aturan, dan siapa yang memoderasi ekonomi kartu — dijelaskan secara lengkap dalam Lampiran V ↗.\n\nPerjanjian Pelanggan Steam, Pasal 4.C, menyatakan:\n\n\"Anda dilarang menggunakan skrip, bot, makro, atau sistem lain yang tidak dikendalikan oleh manusia ('Otomatisasi') dalam bentuk apa pun untuk berinteraksi dengan Konten dan Layanan di Steam dengan cara apa pun.\" — Steam Perjanjian Pelanggan § 4.C (versi saat ini) ↗ diarsipkan 2026-09-18 ↗\n\nValve menegakkan klausul ini. Ia sangat mahir dalam hal itu. Pertanyaan yang Sering Diajukan (FAQ) tentang ArchiSteamFarm (ASF) — sebuah alat sumber terbuka yang, menurut dokumentasinya sendiri, berjalan di lebih dari beberapa juta akun Steam Sejak rilis pertamanya lebih dari 11 tahun yang lalu — menampilkan tiga Steam pesan dukungan yang secara permanen memblokir pengguna yang mengoperasikan jaringan bot. Valve menemukan jaringan-jaringan tersebut, mengidentifikasinya, dan menonaktifkannya. Oleh karena itu, pertanyaan yang relevan bukanlah apakah Valve mampu mendeteksi otomatisasi dalam skala besar.\n\nSitus resmi proyek tersebut ArchiSteamFarm Pertanyaan yang Sering Diajukan secara langsung membahas risiko larangan tersebut:\n\n\"Hal ini sangat tidak mungkin mengingat ASF telah digunakan di lebih dari beberapa juta akun Steam sejak pertama kali dirilis lebih dari 11 tahun yang lalu — namun tetap saja ada kemungkinan, terlepas dari seberapa besar kemungkinannya.\"\n\n\"Valve secara jelas mengakui adanya 'Steam para pemalas', seperti yang disebutkan di sini, jadi menurut saya, saya cukup yakin bahwa jika mereka tidak setuju dengan keberadaan mereka, mereka pasti sudah mengambil tindakan alih-alih hanya menyoroti bahwa hal itu bisa menimbulkan masalah VAC.\" Kata kuncinya di sini adalah Steam idler, misalnya ASF, dan bukan idler game.\"\n\n— ArchiSteamFarm Pertanyaan yang Sering Diajukan (FAQ), JustArchiNET. Sumber: Wiki GitHub ↗ · telah diverifikasi secara verbatim 2026-09-22\n\nPertanyaan yang sama dalam bagian FAQ menjawab \"Apakah ada yang diblokir karena hal itu?\" dengan Ya, dan mengutip apa yang ditulis oleh Steam Support kepada tiga di antara mereka:\n\n1,000+ bot · dilarang bertransaksi\n\"Sepertinya akun ini digunakan untuk mengelola jaringan akun bot. Penggunaan bot merupakan pelanggaran terhadap Perjanjian Pelanggan Steam.\"\n\n170+ bot · diblokir selamanya, Obral Musim Dingin 2017\n\"Akun ini digunakan untuk mengumpulkan kartu koleksi secara ilegal di Steam, serta kegiatan terkait lainnya—tidak hanya kegiatan komersial. Akun tersebut telah diblokir secara permanen dan Tim Dukungan Steam tidak dapat memberikan bantuan lebih lanjut terkait masalah ini.\"\n\n120+ bot · diblokir secara permanen\n\"Akun ini dan akun-akun lainnya digunakan untuk membanjiri infrastruktur jaringan kami, yang merupakan pelanggaran terhadap Steam tata tertib daring.\"\n\n— Steam Pesan dukungan yang dimuat dalam ArchiSteamFarm FAQ, bagian \"Apakah ada yang diblokir karena hal itu?\". Sumber ↗ · telah diverifikasi secara verbatim 2026-09-22\n\nLetakkan kedua catatan tersebut berdampingan. Seorang pengguna pribadi yang menggunakan 1,000 bot pertanian teridentifikasi, diberi tahu bahwa \"penggunaan bot merupakan pelanggaran terhadap Steam Perjanjian Pelanggan\", dan diblokir secara permanen. Platform-platform komersial dalam dokumen ini mengoperasikan akun otomatis Steam sebagai bisnis inti mereka, dalam skala yang jauh lebih besar, dan melakukan otentikasi melalui OpenID milik Valve pada setiap login — dan tidak ada catatan penegakan aturan per operator yang telah dipublikasikan untuk salah satu dari mereka. Klausul tersebut berlaku. Pertanyaannya adalah kepada siapa klausul tersebut ditujukan.\n\nASF tidak dituduh melakukan apa pun di sini, dan penafsirannya terhadap posisi Valve adalah pendapatnya sendiri — penulisnya dengan jelas menyatakan bahwa \"ASF tidak diberi wewenang oleh Valve\". Alat ini digunakan di sini sebagai alat ukur: alat ini menunjukkan bahwa Valve mendeteksi jaringan bot, menyebutkannya secara tertulis, dan memblokirnya secara permanen. Valve dapat menutup pertanyaan ini dalam satu kalimat dengan mempublikasikan otomatisasi komersial mana yang diizinkannya, serta catatan per operator mengenai tindakan apa yang telah dilakukannya terhadap sisanya.\n\nDampak kegiatan \"card farming\" terhadap pendapatan Valve\n\nKartu perdagangan yang diperoleh melalui farming dijual di Pasar Komunitas Steam, yang mengenakan biaya gabungan sekitar 15% untuk setiap transaksi yang diselesaikan di dalam Pasar tersebut; akun tersebut harus telah membelanjakan $5.00 USD pada Steam sebelum dapat menerima kartu sama sekali; dan untuk mendapatkan kartu, pemain harus memiliki game tersebut atau melakukan pembelian dalam game. Tidak ada perkiraan angka pendapatan agregat di sini — skala operasional hanya dinyatakan sebagaimana tercantum dalam FAQ ASF. FAQ tersebut juga mencatat Valve hal yang membedakan \"Steam orang yang menganggur\" (mengumpulkan kartu) dari \"para pemain yang hanya bersantai-santai\"; lihat Pertanyaan Umum (FAQ) ASF ↗. Mekanisme tersebut dijelaskan secara lengkap dalam Lampiran V — skala dan perangkap untuk penggunaan komersial.\n\nSubjekArchiSteamFarm — pengumpulan kartu otomatis\nSkala yang dinyatakanJutaan akun (menurut FAQ ASF — jumlah akun aktif yang pasti belum diverifikasi)\nDihitung, bukan dikutip10,880,610 jumlah entri API di grup Steam milik ASF sendiri (5,360,499 tanpa batasan, seperti yang ditampilkan oleh Steam) — angka “jutaan” dalam FAQ bukanlah sebuah cerita, melainkan jumlah entri. 88.97% tidak memberlakukan Steam larangan apa pun. Data sensus larangan menyeluruh ↗\nInformasi yang tercantum dalam dokumentasi alat tersebut sendiri\nASF masuk ke akun secara headless dan membiarkan game dalam keadaan idle untuk mendapatkan kartu tanpa menjalankan klien Steam (sesuai dokumentasi proyek).\nBagian FAQ tersebut berpendapat bahwa Valve mengetahui adanya \"Steam orang yang hanya menganggur\" dan bahwa \"jika mereka tidak setuju dengan hal itu, mereka pasti sudah mengambil tindakan\".\nTidak ada laporan penegakan hukum yang ditargetkan selama lebih dari 11 tahun (menurut FAQ); penjualan kartu yang dihasilkan di dalam Community Market dikenakan biaya gabungan sebesar 15% dari Steam.\nBagian FAQ menyebutkan batas maksimum yang direkomendasikan sebanyak sepuluh akun per operator dan mengaitkannya dengan Valve: \"Rekomendasi ini didasarkan pada pedoman internal Valve, serta saran dari kami sendiri.\" Tidak ada pedoman semacam itu yang diterbitkan oleh Valve.\nBatas teknis, sesuai dengan FAQ yang sama: \"Anda dapat menjalankan hingga 100–200 bot dengan satu alamat IP dan satu instance ASF.\"\nWaktu bermain yang dimanipulasi dicatat oleh Valve — \"biasanya diperbarui setiap 30 menit sekali\" — dan § 4.C mencantumkan \"Memalsukan statistik permainan (misalnya, memanipulasi jumlah kemenangan atau kekalahan, XP, waktu bermain)\" sebagai tindakan yang dilarang.\nSumber\nWiki FAQ Resmi JustArchi ASF ↗ ArchiSteamFarm repositori ↗ diarsipkan 2026-09-24 ↗\nKlausul otomatisasi tersebut sangat jelas; FAQ ASF telah menyatakan selama bertahun-tahun bahwa alat tersebut beroperasi pada jutaan akun; belum ada laporan mengenai tindakan penegakan hukum yang ditargetkan terhadapnya. Perbedaan antara aturan dan penerapannya tercatat dalam data; alasan di balik hal tersebut tidak dijelaskan di sini.\nPameran lengkapEkonomi kartu: prosesnya, skalanya, lisensinya, dan siapa yang mengawasinya ↗Apa yang harus dibeli sebuah peternakan dari Valve sebelum dapat memproduksi satu kartu pun; dua baris pada § 4.C yang mendefinisikan pertanian kartu berdasarkan dampaknya; mengapa setiap cara mencairkan kartu melanggar lisensi Valve yang ditulis sementara Valve mengenakan biaya di pintu masuk; catatan penegakan aturan termasuk gelombang VAC pada Juni 2025 dan pemblokiran berantai berdasarkan nomor telepon yang sama; serta karyawan Valve dan moderator komunitas yang ditemukan mengelola layanan perdagangan kartu dan daftar pemblokiran di sekitar Steam.Sensus laranganKami tidak bertanya kepada Valve seberapa luas lahan pertanian itu. Kami menghitungnya sendiri. ↗10,880,610 jumlah akun (terbatas dan tidak terbatas) yang dibaca dari grup Steam milik ArchiSteamFarm, yang secara otomatis dimasuki oleh perangkat lunak saat pertama kali dijalankan kecuali pengguna mencabut centang pada pengaturan bergabung dengan grup (mencakup baik bot farm komersial maupun pemain biasa yang membiarkan pengaturan default tetap aktif). 88.97% tidak memiliki larangan Steam dalam bentuk apa pun; dari 11% yang memilikinya, 99.8% adalah larangan komunitas yang bersifat kosmetik dan tidak pernah menghentikan aktivitas perdagangan. Setelah dicocokkan dengan SteamRep, 67.77% dari penipu yang terdaftar bebas dari sanksi begitu pemblokiran anti-cheat dikesampingkan. Dengan rincian tanggal pendaftaran, lokasi geografis, dan tingkat kelangsungan — skala sebenarnya, diukur, bukan sekadar diceritakan.\n\nAppendix F — Working ledger\n\nRules ledger: clauses against recorded platforms\n\nPilih sebuah aturan; daftar tersebut menampilkan platform-platform yang tercatat dan diberi label di bawah aturan tersebut, beserta domain utamanya, host otentikasi yang ditentukan, dan hasil Filter Tautan yang tersimpan. Situs web yang diblokir, atau domain lain untuk masuk: ikuti aturan tersebut hingga mencapai rute yang tersisa.\n\n175catatan yang terkait\nterkait aturan ini\n174 domain utama0 C&D disebutkan\nKUTIPAN PERATURAN / SSA § 2.G\nPenggunaan Komersial & Penagihan Akun\n“…exploit the Content and Services or any of its parts for any commercial purpose, except as expressly permitted elsewhere in this Agreement (including any Subscription Terms or Rules of Use).”\nIKUTI CATATANNYA\nPendaftaran platform 175\nAngka-angka dalam skala tersebut merupakan perkiraan berdasarkan sumber\n\n175 dari rekaman \"175\"\n\nLayanan / kelompok induk\tDomain utama / pendaftar domain\tDomain otentikasi / usia yang teramati\tSkala / respons yang tercatat\n\nCasino\n\tcsgoempire.com\n11.3 yearsRegistered 2015-06-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgoempirelogin4.com\n6.2 yearsRegistered 2020-07-20\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustreaper.com\n23.2 yearsRegistered 2003-06-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustreaper.com\n23.2 yearsRegistered 2003-06-24\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustly.com\n12.4 yearsRegistered 2014-05-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustly.com\n12.4 yearsRegistered 2014-05-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette Casino\n\tcsgofast.com\n11.5 yearsRegistered 2015-03-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsteam-login.authtofast.com\n83 daysRegistered 2026-06-30\nRDAP ↗ · authtofast.com (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tduelbits.com\n6.6 yearsRegistered 2020-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nswitchflips.com\n6.4 yearsRegistered 2020-04-21\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opener\n\tfarmskins.com\n10.5 yearsRegistered 2016-03-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsteam.kobal.cc\n9.7 yearsRegistered 2017-01-07\nRDAP ↗ · kobal.cc (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgoluck.com\n9.3 yearsRegistered 2017-05-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgoluck.com\n9.3 yearsRegistered 2017-05-18\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tinsane.gg\n7.5 yearsRegistered 2019-04-02\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.insane.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcs2skin.com\n3.5 yearsRegistered 2023-03-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncs2skin.com\n3.5 yearsRegistered 2023-03-06\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tjuice.gg\n7.9 yearsRegistered 2018-10-19\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nletmeinjuice.com\n2.4 yearsRegistered 2024-04-15\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tggdrop.com\n8.6 yearsRegistered 2018-02-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nggauth.com\n3.4 yearsRegistered 2023-05-03\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Casino\n\thowl.gg\n9.5 yearsRegistered 2017-03-16\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhowl.uno\n41 daysRegistered 2026-08-11\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tchicken.gg\n5.7 yearsRegistered 2021-01-11\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nchicken.gg\n5.7 yearsRegistered 2021-01-11\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgocasino.gg\n2.6 yearsRegistered 2024-02-17\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.csgocasino.gg\n2.6 yearsRegistered 2024-02-17\nWHOISFREAKS ↗ · csgocasino.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Casino\n\thunt.gg\n6.9 yearsRegistered 2019-11-04\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.hunt.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Battles\n\tcsbattle.com\n9.8 yearsRegistered 2016-12-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsbattle.com\n9.8 yearsRegistered 2016-12-10\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskinrave.gg\n3.1 yearsRegistered 2023-08-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinrave.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsdouble.gg\n261 daysRegistered 2026-01-03\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsdouble.gg\n261 daysRegistered 2026-01-03\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustchance.com\n8.0 yearsRegistered 2018-10-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhgfuihd.com\n7.6 yearsRegistered 2019-01-27\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Automation\n\tcobaltlab.tech\n3.5 yearsRegistered 2023-03-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncobaltauth.com\n1.7 yearsRegistered 2025-01-07\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\traided.gg\n171 daysRegistered 2026-04-03\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.raided.gg\n171 daysRegistered 2026-04-03\nIP2WHOIS ↗ · raided.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustneo.gg\n1.3 yearsRegistered 2025-06-20\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustneo.gg\n1.3 yearsRegistered 2025-06-20\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tsplits.gg\n3.7 yearsRegistered 2023-01-23\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsplits.gg\n3.7 yearsRegistered 2023-01-23\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Upgrader\n\tupgrader.pro\n1.2 yearsRegistered 2025-07-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nupgauth.space\n38 daysRegistered 2026-08-14\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskin.fans\n8.2 yearsRegistered 2018-07-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skinfans.com\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\thotpizza.one\n1.8 yearsRegistered 2024-12-07\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhotpizza.one\n1.8 yearsRegistered 2024-12-07\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tg4skins.com\n10.1 yearsRegistered 2016-08-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.g4s.to\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2royal.com\n4.1 yearsRegistered 2022-08-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ntf2auth.com\n5.2 yearsRegistered 2021-07-27\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2hunt.com\n8.7 yearsRegistered 2018-01-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrstspcl.com\n6.1 yearsRegistered 2020-08-08\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2.bet/coinflip\n8.4 yearsRegistered 2018-05-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ntf2.bet\n8.4 yearsRegistered 2018-05-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\topenstars.gg\n131 daysRegistered 2026-05-13\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nopenstars.gg\n131 daysRegistered 2026-05-13\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tskins.com\n25.1 yearsRegistered 2001-08-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skins.com\n25.1 yearsRegistered 2001-08-08\nRDAP ↗ · skins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\twhite.market\n9.6 yearsRegistered 2017-03-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwhite.market\n9.6 yearsRegistered 2017-03-01\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tmoon.market\n7.6 yearsRegistered 2019-02-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmoon.market\n7.6 yearsRegistered 2019-02-27\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tcsfloat.com\n5.2 yearsRegistered 2021-07-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgofloat.com\n11.0 yearsRegistered 2015-09-29\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tskin.land\n4.7 yearsRegistered 2022-01-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skin.land\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\thaloskins.com\n2.8 yearsRegistered 2023-12-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhaloskins.com\n2.8 yearsRegistered 2023-12-10\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCorporate Market\n\tbuff.163.com\n29.0 yearsRegistered 1997-09-15\nRDAP ↗ · 163.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\nbuff.163.com\n29.0 yearsRegistered 1997-09-15\nRDAP ↗ · 163.com (parent)\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\tmarket.csgo.com\n26.6 yearsRegistered 2000-02-07\nRDAP ↗ · csgo.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\ndota2.net\n14.9 yearsRegistered 2011-10-29\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRegulated Market\n\tskinport.com\n8.0 yearsRegistered 2018-09-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinport.app\n6.3 yearsRegistered 2020-06-20\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMarketplace/Swap\n\tskinflow.gg\n3.8 yearsRegistered 2022-11-26\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinflow.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tskin.place\n6.0 yearsRegistered 2020-09-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skin.place\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tskinsmonkey.com\n5.7 yearsRegistered 2021-01-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinsmonkey.com\n5.7 yearsRegistered 2021-01-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCorporate Market\n\tskinbaron.de\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinbaron.com\n10.7 yearsRegistered 2015-12-22\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Market\n\trust.tm\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\ndota2.net\n14.9 yearsRegistered 2011-10-29\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tpirateswap.com\n6.0 yearsRegistered 2020-09-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nlogin.pirateswap.com\n6.0 yearsRegistered 2020-09-22\nRDAP ↗ · pirateswap.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Marketplace\n\tmannco.store\n8.6 yearsRegistered 2018-03-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmannco.store\n8.6 yearsRegistered 2018-03-02\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tskinswap.com\n9.9 yearsRegistered 2016-11-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinswap.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\texeskins.com\n2.1 yearsRegistered 2024-08-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nexeskins.com\n2.1 yearsRegistered 2024-08-14\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tbalticskins.com\n153 daysRegistered 2026-04-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nbalticskins.com\n153 daysRegistered 2026-04-21\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tcs.trade\n8.9 yearsRegistered 2017-11-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncs.trade\n8.9 yearsRegistered 2017-11-14\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\trapidskins.com\n4.5 yearsRegistered 2022-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.rapidskins.com\n4.5 yearsRegistered 2022-03-11\nRDAP ↗ · rapidskins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\ttradeit.gg\n9.1 yearsRegistered 2017-08-21\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nconnect-tradeit.com\n4.6 yearsRegistered 2022-02-23\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\t49skins.com\n3.4 yearsRegistered 2023-04-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.49skins.com\n3.4 yearsRegistered 2023-04-19\nRDAP ↗ · 49skins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tskinvault.gg\n3.4 yearsRegistered 2023-05-06\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinvault.gg\n3.4 yearsRegistered 2023-05-06\nIP2WHOIS ↗ · skinvault.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Trading\n\taim.market\n3.3 yearsRegistered 2023-05-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\naim.market\n3.3 yearsRegistered 2023-05-22\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Sell Portal\n\tskinout.gg\n5.6 yearsRegistered 2021-02-27\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skinout.gg\n5.6 yearsRegistered 2021-02-27\nIP2WHOIS ↗ · skinout.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Trading\n\tntskins.com\n230 daysRegistered 2026-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nntskins.com\n230 daysRegistered 2026-02-03\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Portal\n\tgamerpay.gg\n6.0 yearsRegistered 2020-10-02\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ngamerpay.gg\n6.0 yearsRegistered 2020-10-02\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Scrap Swap\n\tscrap.tf\n14.0 yearsRegistered 2012-09-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nscrap.tf\n14.0 yearsRegistered 2012-09-03\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Cashout\n\tmarketplace.tf\n14.0 yearsRegistered 2012-09-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmarketplace.tf\n14.0 yearsRegistered 2012-09-19\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Cashout\n\tskins.cash\n10.5 yearsRegistered 2016-03-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinscash.live\n6.8 yearsRegistered 2019-12-05\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgo.net\n14.2 yearsRegistered 2012-07-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncn2.easylot.net\n10.0 yearsRegistered 2016-09-03\nRDAP ↗ · easylot.net (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCommunity Hub\n\tcybershoke.net\n6.8 yearsRegistered 2019-11-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.cybershoke.net\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMatchmaker Hub\n\tfastcup.net\n14.6 yearsRegistered 2012-02-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.fastcup.net\n14.6 yearsRegistered 2012-02-16\nRDAP ↗ · fastcup.net (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Analytics\n\tleetify.com\n7.6 yearsRegistered 2019-03-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nleetify.com\n7.6 yearsRegistered 2019-03-01\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Analytics\n\tscope.gg\n7.8 yearsRegistered 2018-12-10\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nscope.gg\n7.8 yearsRegistered 2018-12-10\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tools\n\ttradeupspy.com\n6.5 yearsRegistered 2020-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.tradeupspy.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMarketplace\n\tcs.deals\n9.8 yearsRegistered 2016-12-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.cs.deals\n9.8 yearsRegistered 2016-12-03\nRDAP ↗ · cs.deals (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Price DB\n\tpricempire.com\n6.6 yearsRegistered 2020-01-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\npricempire.com\n6.6 yearsRegistered 2020-01-30\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Blackmarket\n\tFSB Market\n7.2 yearsRegistered 2019-07-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nFSB Market\n7.2 yearsRegistered 2019-07-27\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nReady-Account Hub\n\tz2u.com\n26.9 yearsRegistered 1999-11-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwww.z2u.com\n26.9 yearsRegistered 1999-11-10\nRDAP ↗ · z2u.com (parent)\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Gambling\n\tcsgoroll.com\n11.6 yearsRegistered 2015-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwww.csgoroll.com\nRegistry date unavailableRegistry date unavailable\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\trollbit.com\n11.9 yearsRegistered 2014-11-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrbsnin.com\n3 daysRegistered 2026-09-18\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nLicenced Casino\n\t500.casino\n5.9 yearsRegistered 2020-11-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette/Slots\n\tcsgobig.com\n11.4 yearsRegistered 2015-04-12\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcasedrop.com\n14.8 yearsRegistered 2011-12-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\tbanditcamp.com\n12.2 yearsRegistered 2014-06-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tskinbox.com\n18.8 yearsRegistered 2007-12-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\ttastydrop.com\n6.1 yearsRegistered 2020-08-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette Casino\n\tcsgopolygon.gg\n6.5 yearsRegistered 2020-03-28\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tmagicdrop.ru\n10.3 yearsRegistered 2016-05-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nDice Casino\n\tcsdice.com\n3.8 yearsRegistered 2022-11-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUpgrader Casino\n\tskinodds.com\n1.2 yearsRegistered 2025-06-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgowin.com\n12.0 yearsRegistered 2014-09-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrash Casino\n\tcsgorun.net\n7.3 yearsRegistered 2019-06-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\topenskins.com\n3.6 yearsRegistered 2023-02-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Gambling\n\trustbet.com\n7.6 yearsRegistered 2019-02-07\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgomagic.com\n9.4 yearsRegistered 2017-05-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUpgrader/Contract\n\tcsgobounty.com\n11.5 yearsRegistered 2015-03-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tezskins.com\n27.5 yearsRegistered 1999-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\trustcases.com\n7.2 yearsRegistered 2019-06-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgoreaper.com\n11.1 yearsRegistered 2015-08-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgocases.com\n12.3 yearsRegistered 2014-06-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Upgrader\n\tcsgo-skins.com\n11.2 yearsRegistered 2015-07-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgonet.com\n8.8 yearsRegistered 2017-12-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\twtfskins.com\n9.0 yearsRegistered 2017-10-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Casino\n\tflamecases.com\n10.0 yearsRegistered 2016-09-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tgamedom.com\n11.7 yearsRegistered 2015-01-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Battles\n\tskin.club\n9.0 yearsRegistered 2017-09-04\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsc-auth.net\n7.5 yearsRegistered 2019-04-02\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tdaddyskins.com\n9.9 yearsRegistered 2016-10-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Gambling\n\trustix.gg\n1.7 yearsRegistered 2025-01-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Upgrade\n\tskins.club\n4.2 yearsRegistered 2022-07-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgohouse.org\n146 daysRegistered 2026-04-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskinrave.net\n216 daysRegistered 2026-02-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tbloodycase.gg\n19 daysRegistered 2026-09-02\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nClicker/Upgrade\n\tcsgoclicker.com\n8.3 yearsRegistered 2018-05-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustbet.gg\n4.0 yearsRegistered 2022-09-30\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcs-drop.com\n262 daysRegistered 2026-01-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\thellstore.net\n11.7 yearsRegistered 2015-01-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustloot.com\n354 daysRegistered 2025-10-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgo-case.com\n10.3 yearsRegistered 2016-05-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgogem.com\n9.9 yearsRegistered 2016-10-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\trainbet.com\n8.8 yearsRegistered 2017-11-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nservices.rainbet.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustclash.com\n5.4 yearsRegistered 2021-05-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrash Casino\n\t12cs.fail\n181 daysRegistered 2026-03-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\twww.tf2easy.com\n6.3 yearsRegistered 2020-06-02\nRDAP ↗ · tf2easy.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2blaze.com\n7.6 yearsRegistered 2019-01-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tshuffle.com\n30.1 yearsRegistered 1996-07-31\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tbuff.market\n5.9 yearsRegistered 2020-10-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tavan.market\n8.3 yearsRegistered 2018-05-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Engine\n\tcs.money\n11.0 yearsRegistered 2015-09-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.dota.trade\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tuuskins.com\n2.6 yearsRegistered 2024-01-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Market\n\tyoupin898.com\n6.1 yearsRegistered 2020-08-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tc5game.com\n10.5 yearsRegistered 2016-03-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\twaxpeer.com\n7.3 yearsRegistered 2019-05-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwaxpeer.com\n7.3 yearsRegistered 2019-05-20\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBot Trading\n\tcs.money\n11.0 yearsRegistered 2015-09-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.dota.trade\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUS Marketplace\n\tdmarket.com\n30.2 yearsRegistered 1996-07-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nOfficial Market\n\tsteamcommunity.com/market\n20.3 yearsRegistered 2006-05-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNot an external login site2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Platform\n\tlootfarm.com\n11.9 yearsRegistered 2014-10-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Market\n\trustskins.com\n7.6 yearsRegistered 2019-01-31\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tkrakatoa.com\n26.4 yearsRegistered 2000-05-15\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\tshadowpay.com\n10.1 yearsRegistered 2016-08-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nChinese Powerhouse\n\tigxe.cn\n15.0 yearsRegistered 2011-09-06\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAutomated Swap\n\tswap.gg\n9.6 yearsRegistered 2017-01-29\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCash-out Portal\n\tbitskins.com\n11.2 yearsRegistered 2015-07-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Automation\n\ttf2mart.com\n1.1 yearsRegistered 2025-08-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Auctions\n\tskinbid.com\n10.2 yearsRegistered 2016-06-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Rental\n\tlootbear.com\n8.7 yearsRegistered 2018-01-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Valuation\n\tbackpack.tf\n14.4 yearsRegistered 2012-05-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Botnet\n\tstntrading.eu\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Cashout\n\tskinwallet.com\n18.0 yearsRegistered 2008-09-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nDota 2 Market\n\tdota2market.com\n12.2 yearsRegistered 2014-07-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nServer Network\n\txplay.gg\n5.3 yearsRegistered 2021-06-13\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMatchmaking Portal\n\tesportal.com\n26.8 yearsRegistered 1999-12-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nLATAM Hub\n\tgamersclub.com.br\n11.2 yearsRegistered 2015-06-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tools\n\tepidemic.gg\n4.9 yearsRegistered 2021-11-03\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tcs2stash.com\n3.5 yearsRegistered 2023-03-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tcsgoskins.gg\n6.8 yearsRegistered 2019-12-21\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tsteamanalyst.com\n12.6 yearsRegistered 2014-02-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Exchange\n\tsteamcardexchange.net\n13.3 yearsRegistered 2013-05-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tracker\n\tdotabuff.com\n14.2 yearsRegistered 2012-06-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tracker\n\ttracker.gg\n8.9 yearsRegistered 2017-10-12\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Exchange\n\tfunpay.com\n17.0 yearsRegistered 2009-09-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nGrey Market\n\tplayerauctions.com\n26.3 yearsRegistered 2000-06-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Portal\n\teldorado.gg\n8.0 yearsRegistered 2018-09-12\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Key Market\n\tg2a.com\n24.8 yearsRegistered 2001-12-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Key Market\n\tkinguin.net\n16.8 yearsRegistered 2009-12-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nVirtual Services\n\tg2g.com\n31.1 yearsRegistered 1995-08-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Broker\n\tplayerup.com\n19.3 yearsRegistered 2007-05-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfhub.net\n2.7 yearsRegistered 2023-12-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfaccounts.com\n5.3 yearsRegistered 2021-05-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Shop\n\tbuycsgorank.com\n6.2 yearsRegistered 2020-07-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tcsgosmurfkings.com\n9.3 yearsRegistered 2017-06-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfstore.co\n8.6 yearsRegistered 2018-03-03\nWHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlvlup.com\n9.9 yearsRegistered 2016-11-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlevels.com\n10.6 yearsRegistered 2016-02-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tlevelsteam.com\n79 daysRegistered 2026-07-04\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlevelu.com\n6.0 yearsRegistered 2020-09-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\teloking.com\n12.2 yearsRegistered 2014-07-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\tboosteria.org\n11.9 yearsRegistered 2014-10-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tovergear.com\n14.4 yearsRegistered 2012-04-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tblazingboost.com\n14.2 yearsRegistered 2012-06-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\tdota2boost.com\n2.9 yearsRegistered 2023-10-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tbuyboost.com\n22.4 yearsRegistered 2004-04-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\nArgumen dalam penyelidikan tersebutAturan yang dipilih / analisis & komentar+\nBeban pembuktian\n\nPenyelidikan ini mengungkap ketidaksesuaian antara pembatasan penggunaan komersial dan layanan yang tercatat di sini. Klasifikasikan setiap aktivitas dan pastikan adanya izin tertulis sebelum menyimpulkan bahwa hal tersebut merupakan pelanggaran kontrak. Biaya Pasar Komunitas tidak berlaku untuk setiap transaksi eksternal.\n\nApa yang dimaksud dengan catatan yang diberi tag, dan apa yang bukan\n\nSebuah catatan diberi label ketika berkas tersebut memuat catatan tertanggal yang menunjukkan bahwa platform tersebut secara jelas memenuhi ketentuan dalam klausul tersebut. Label tersebut bukanlah pelanggaran yang telah diputuskan, dan belum ada izin tertulis Valve yang diterbitkan terkait catatan tersebut untuk platform mana pun yang tercantum di sini. Apabila sebuah platform memiliki izin, maka publikasi izin tersebut akan menyelesaikan entri tersebut.\n\nSumber & metodologiPerkiraan, definisi, dan ruang lingkup+\n\nJumlah di atas mengacu pada aturan yang dipilih. Jenis catatan mengelompokkan setiap platform satu kali; tag lengkap ditampilkan dalam detail platform. Pencarian dan filter berlaku dalam aturan tersebut. Tanggal pendaftaran diambil dari snapshot yang disimpan di RDAP / WHOIS. Subdomain menggunakan tanggal pembuatan domain induk. Usia saja tidak menjamin operasi yang berkelanjutan atau rute otentikasi. Nama host otentikasi saat ini diambil dari permintaan OpenID yang disimpan, dengan cap waktu UTC; pemeriksaan yang tidak terselesaikan tidak menggunakan kembali label lama. Pengamat berhenti sebelum proses masuk di Steam dan tidak menguji status Filter Tautan di Steam. Unduh catatan rute ↗ Unduh hasil registri ↗\n\nJelajahi arsip sumber ↗\nLampiran G — Dari templat penolakan hingga catatan aslinya\nPanduan DSAR: ajukan permintaan bukti\n\nGunakan Pasal 15 GDPR untuk meminta data pribadi yang berkaitan dengan pembuatan kunci API, pemulihan akun, dan akses layanan dukungan. Catatan yang disimpan dapat digunakan untuk mengetahui siapa yang memulai suatu tindakan dan apa yang menjadi dasar keputusan platform tersebut.\n\n01\nJaga garis waktu Anda.\n\nSimpan pemberitahuan akun, tiket, ID transaksi, dan tanggal dalam UTC. Amankan akun dan tinjau opsi pemulihan yang berlaku untuk game dan transaksi tersebut.\n\nSteam Informasi Perlindungan Perdagangan ↗\n02\nAjukan permohonan untuk mendapatkan data yang disimpan.\n\nMintalah informasi mengenai cap waktu, alamat IP sumber, peristiwa penting dalam siklus hidup kunci, konfirmasi keamanan, dan tindakan pemulihan yang berkaitan dengan akun. Sertakan juga peristiwa akses dukungan serta penerima data tersebut jika informasi tersebut relevan bagi Anda.\n\n03\nSimpanlah catatan pengiriman tersebut.\n\nGunakan jalur kontak privasi Valve. Waktu tanggapan biasanya adalah satu bulan; jika diperlukan perpanjangan hingga dua bulan lagi, hal tersebut harus dijelaskan dalam jangka waktu satu bulan pertama tersebut.\n\nValve jalur kontak privasi ↗ diarsipkan 2026-09-21 ↗\n04\nBandingkan tanggapannya.\n\nSelaraskan catatan dengan garis waktu Anda. Tanyakan alasan di balik hal-hal yang terlewatkan, lalu gunakan jalur pengaduan melalui pihak berwenang yang berwenang jika diperlukan. Simpan tanggapan tersebut persis seperti yang diterima.\n\nRuang Lingkup / Pasal 15\n\nAkses ini mencakup data pribadi yang disimpan, termasuk data dalam log. Akses ini tidak menjamin ketersediaan setiap dokumen internal, catatan yang direkonstruksi, atau data yang belum disunting mengenai pihak lain. Mintalah salinan yang dapat dipahami serta dasar dari setiap pembatasan yang diterapkan.\n\nPedoman akses EDPB, § 2, § 4–6 ↗ · Pasal 12, 15, dan 77 GDPR ↗ diarsipkan 2026-09-20 ↗\n\nPermohonan Akses oleh Subjek DataGDPR / Pasal 15\nKeamanan akun & riwayat akses\n\nGanti kolom yang diberi tanda kurung sebelum mengirimkan.\n\nTo: Valve Privacy Team\nSubject: Article 15 GDPR request — account security records\n\nAccount / SteamID: [YOUR ACCOUNT IDENTIFIER]\nRelevant period (UTC): [START] to [END]\nRelated support tickets: [TICKET REFERENCES]\n\nI request a copy of the personal data concerning me that you retain for this period, including:\n\n1. API-key registration, confirmation, use and revocation events, with available timestamps, source IP addresses, registered domains, device or user-agent information and non-secret key identifiers.\n\n2. Recorded account-recovery actions, password/email/phone changes, Steam Guard removals or resets, confirmation events and the account-related evidence relied on to authorize those actions.\n\n3. Personal data in support-access and administrative-action logs concerning my account, including available dates, purposes, actions and the support entity involved, subject to applicable rights of others.\n\n4. Account-related records used to determine any sanction, and available records of my complaints, reviews and responses.\n\nPlease also provide the applicable processing purposes, categories, recipients, retention periods or criteria, and available information about sources where data were not obtained from me.\n\nWhere processing relies on my consent, please provide the retained record of the consent relied upon and the wording presented at that time.\n\nPlease provide an intelligible electronic copy with time zones and field definitions. Please do not include active credentials or secret tokens. If any requested data are not held, please say so. For any withheld data, please identify the scope and legal basis of the restriction and provide the remainder.\n\nPlease acknowledge receipt and respond within the applicable Article 12 period, explaining any necessary extension. I also ask you to preserve relevant existing records while this request is handled.\n\nName: [YOUR NAME]\nDate: [DATE]\nApa saja yang dapat diwujudkan oleh alamat IP pusat data\nPerbedaan merupakan bukti yang perlu diselidiki.\n\nPermintaan kunci API yang berasal dari jaringan pusat data, seperti dalam contoh penyedia layanan hosting yang diangkat dalam penyelidikan ini, dapat menjadi relevan jika dibandingkan dengan catatan login, konfirmasi, dan riwayat aktivitas pengguna. Alamat IP saja tidak cukup untuk mengidentifikasi pelaku atau secara otomatis menembus setiap sistem pertahanan. Bukti bahwa pelaku jahatlah yang menyediakan persetujuan yang tercatat dapat menantang keabsahan persetujuan tersebut; dasar hukum lain dan masalah pertanggungjawaban memerlukan analisis terpisah.\n\nLihat pengaduan terkait larangan dan GDPR yang telah disimpan →\nLampiran H — Analisis arsip Wayback Machine · Statistik dukungan yang telah dipublikasikan\nVolume dukungan. Waktu respons yang dipublikasikan.\nKonteks & batasan sumber\n\nValve mempublikasikan statistik dukungan harian di store.steampowered.com/stats/support. Arsip Wayback Machine menyimpan cuplikan historis halaman ini dari tahun 2018 hingga 2026. Rasio volume terhadap jumlah staf yang tersirat dari angka-angka ini tidak sejalan dengan proses peninjauan manual per tiket pada waktu respons yang dipublikasikan.\n\nBandingkan angka-angka dukungan yang diarsipkan oleh Valve di seluruh cuplikan yang disimpan. Metodologi ini menjelaskan hal-hal apa saja yang dapat dan tidak dapat diukur oleh angka-angka tersebut.\n\nVolume terhadap waktu respons yang dipublikasikan (2018 → 2026)\nDua antrean di satu loket layanan pelanggan, seperti yang terlihat pada 21 tangkapan layar yang telah diarsipkan.\n\nValve mempublikasikan data dukungan langsung di store.steampowered.com/stats/support. Setiap titik di bawah ini merupakan batas bawah Valve itu sendiri yang tercetak pada halaman tersebut pada hari ketika Internet Archive menyimpannya — bukan perkiraan dari kami. Kedua deret tersebut merupakan besaran yang sama dalam satuan yang sama, sehingga keduanya berada pada satu sumbu dan dapat dibandingkan secara langsung.\n\nPermohonan pengembalian dana — uang Valve yang dimilikiKeamanan & pemulihan akun — akun yang telah hilang\n0 h\n2 h\n4 h\n6 h\n8 h\n10 h\nno captures · 38 months\n2019\n2020\n2021\n2022\n2023\n2024\n2025\n2026\n8 h 44 m\naccount recovery\n52 m\nrefunds\n15 m — one capture only\n49–55 menitBatas bawah pengembalian dana pada setiap pencatatan dari Februari 2018 hingga Agustus 2026. Selama delapan setengah tahun, perubahannya kurang dari enam menit, sementara volume pengembalian dana harian berubah hingga sembilan kali lipat.\n2,4 jam → 8,7 jamBatas bawah pemulihan akun berada di sekitar 2,4 jam dalam setiap pengukuran hingga Desember 2022, kecuali satu pengukuran. Dalam tiga pengukuran tahun 2026, Valve mencatat angka 10,9 jam, 5,8 jam, dan 8,7 jam.\n×2,8 → ×13Seberapa lambat proses pemulihan dibandingkan dengan pengembalian dana, berdasarkan angka yang dipublikasikan oleh Valve sendiri. Prosesnya stabil selama lima tahun, lalu selisihnya semakin melebar — antrean yang prosesnya semakin lambat adalah antrean di mana pengguna, bukan Valve, yang menanggung kerugian.\n\nSumber: 21 salinan arsip Wayback Machine dari store.steampowered.com/stats/support, 2018-02-03 hingga 2026-08-10; ekstraksi di VALVE_EVIDENCE_PACK/databases/steam_support_stats_history.json. Perhatikan batas-batas yang ditunjukkan pada grafik: grafik tersebut menggambarkan lebih rendah batas atas rentang Valve hasil cetak. Batas atas yang dipublikasikan lebih buruk pada kedua baris — waktu pengembalian berkisar antara 1,5 jam hingga 1,5 hari, sedangkan waktu pemulihan berkisar antara 7,0 jam hingga 3,6 hari. Dua tangkapan layar diarsipkan dalam edisi terjemahan dari halaman Valve yang sama — 2018-11-03 dalam bahasa Ceko, 2020-03-25 dalam bahasa Prancis — dan ditandai dengan (cs) dan (fr) dalam tabel; angka-angka tersebut ditampilkan di sini dengan kata-kata satuan yang telah diterjemahkan dan angka-angka sesuai yang diterbitkan, sedangkan string sumber secara verbatim disimpan dalam berkas ekstraksi. Setiap penangkapan data mempublikasikan waktu respons untuk kedua antrian, dan tidak ada titik pada kedua garis tersebut yang diinterpolasi. Angka pemulihan tunggal selama 15 menit sebesar 2020-10-21 ditandai pada grafik dan dibiarkan apa adanya: angka tersebut hanya muncul dalam satu penangkapan data dan tidak ada penangkapan data lain yang nilainya berada dalam satu orde besar darinya. Tidak ada data yang tercatat antara 2022-12-08 dan 2026-02-01; celah 38 bulan dalam catatan tersebut diarsir, dan tidak ada garis yang digambar melintasi celah tersebut. Angka-angka ini menggambarkan waktu respons yang dipublikasikan. Angka-angka tersebut tidak menunjukkan apa yang terjadi di dalam sebuah tiket, dan Valve belum mempublikasikan jumlah staf yang dapat digunakan sebagai patokan untuk menafsirkannya.\n\nBuka setiap tangkapan layar sebagai tabel\nSetiap tangkapan layar yang diarsipkan, sebagaimana telah dipublikasikan\nPengambilan\tPengembalian dana / hari\tTanggapan terkait pengembalian dana\tPemulihan / hari\tTindakan pemulihan\n2018-02-03\t98,788\t50,12 menit hingga 1,52 jam\t25,662\t2,51 jam hingga 1,80 hari\n2018-05-07\t60,494\t53,83 menit hingga 1,47 hari\t24,226\t2,45 jam hingga 2,22 hari\n2018-08-02\t69,084\t50,27 menit hingga 1,59 jam\t28,953\t2,44 jam hingga 22,17 jam\n2018-11-03 (cs)\t63,410\t49,28 menit hingga 1,54 jam\t33,910\t2,42 jam hingga 1,31 hari\n2019-02-01\t76,305\t50,13 menit hingga 1,52 jam\t35,164\t2,44 jam hingga 2,04 hari\n2019-05-18\t78,951\t51,03 menit hingga 3,12 jam\t27,514\t2,46 jam hingga 20,39 jam\n2019-09-07\t78,941\t50,65 menit hingga 1,66 jam\t28,812\t2,42 jam hingga 13,59 jam\n2019-12-13\t69,589\t50,77 menit hingga 1,55 jam\t25,322\t2,45 jam hingga 1,13 hari\n2020-03-25 (fr)\t139,278\t49,45 menit hingga 1,53 jam\t32,302\t2,48 jam hingga 3,62 hari\n2020-06-26\t278,504\t48,98 menit hingga 2,29 jam\t20,343\t2,39 jam hingga 6,99 jam\n2020-10-21\t107,633\t50,80 menit hingga 1,54 jam\t20,688\t15,33 menit hingga 8,62 jam\n2021-03-20\t158,956\t50,80 menit hingga 1,64 jam\t25,760\t2,34 jam hingga 11,62 jam\n2021-06-26\t547,907\t51,93 menit hingga 6,73 jam\t29,728\t2,40 jam hingga 15,63 jam\n2021-10-10\t170,103\t51,88 menit hingga 3,25 jam\t23,989\t2,39 jam hingga 13,05 jam\n2022-01-31\t354,386\t53,65 menit hingga 8,09 jam\t24,391\t2,42 jam hingga 15,29 jam\n2022-05-09\t172,555\t51,83 menit hingga 1,65 jam\t23,289\t2,41 jam hingga 16,90 jam\n2022-09-05\t153,453\t53,67 menit hingga 4,15 jam\t23,594\t2,45 jam hingga 1,22 hari\n2022-12-08\t181,075\t54,83 menit hingga 6,67 jam\t27,111\t2,46 jam hingga 18,89 jam\n2026-02-01\t317,762\t50,30 menit hingga 1,52 jam\t47,197\tPukul 10.91 hingga pukul 21.30\n2026-05-09\t246,776\t50,12 menit hingga 1,52 jam\t35,264\t5,81 jam hingga 15,60 jam\n2026-08-10\t373,244\t52,05 menit hingga 2,07 jam\t45,319\t8,73 jam hingga 16,52 jam\nPENGAMATAN UTAMA:\nDi seluruh 21 salinan dari Wayback dengan rentang dari 2018-02-03 hingga 2026-08-10, pengajuan pengembalian dana harian berkisar antara 60,494 (Mei 2018) hingga 547,907 (Juni 2021) — a Selisih 9,1×. Angka untuk tahun 2026 adalah 373,244 (+278% dibandingkan dengan data pada Februari 2018).\nSelama sembilan tahun yang sama itu, batas bawah yang dipublikasikan untuk waktu respons pengembalian dana tidak pernah keluar dari 49–55 menit band: pergerakan total kurang dari enam menit, sementara beban kerja di baliknya meningkat sembilan kali lipat.\nJika seseorang membaca setiap tiket selama 5 detik saja, maka memproses 373,244 tiket per hari (saat ini) akan memakan waktu 22 agen yang bekerja 24 jam sehari, 7 hari seminggu hanya untuk membukanya dan menutupnya; pada puncaknya (547,907, Juni 2021), angkanya naik menjadi 32.\nJika waktu respons yang dipublikasikan mencerminkan waktu penanganan per tiket (~52 menit/tiket), jumlah staf yang dibutuhkan secara bersamaan diperkirakan sebesar 13,500 agen pada volume saat ini dan ~20,000 pada puncaknya. Belum ditemukan data yang bersumber mengenai jumlah staf pendukung Valve; angka tersebut tidak diperhitungkan di sini.\nBerikut ini: rasio volume terhadap jumlah staf tidak sesuai dengan proses peninjauan manual per tiket pada waktu respons yang dipublikasikan. Angka-angka tersebut sesuai dengan proses tahap awal yang sebagian besar otomatis; proporsi yang ditinjau secara manual tidak dipublikasikan.\nMengapa hal ini penting bagi kepatuhan terhadap GDPR\n\nPasal 22 GDPR melarang pengambilan keputusan terhadap individu yang sepenuhnya dilakukan secara otomatis dan menimbulkan dampak hukum yang signifikan, tanpa memberikan hak atas peninjauan oleh manusia atas permintaan. Jika keputusan dukungan Steam (penutupan tiket, tindakan terhadap akun, penolakan permintaan data) dibuat sepenuhnya oleh skrip otomatis, setiap keputusan semacam itu yang “secara signifikan memengaruhi” pengguna dapat melanggar Pasal 22.\n\nTiket HT-2YBP-F7JP-D4VB (Bagian 18) ditutup setelah tiga hari dengan rujukan berdasarkan templat dan tanpa pembahasan mengenai dasar hukum yang disebutkan. Apakah ada pihak yang meninjaunya tidak dapat ditentukan dari tiket tersebut; hal itu merupakan pertanyaan yang dapat diajukan oleh otoritas pengawas kepada Valve berdasarkan Pasal 22 dan Pasal 15 ayat (1) huruf h.\n\nSumber: Tangkapan layar Wayback Machine dari store.steampowered.com/stats/support (2018-02-03, 2021-06-26, 2026-08-10) — data diekstraksi ke VALVE_EVIDENCE_PACK/databases/steam_support_stats_history.json (21 snapshot, 2018–2026). Catatan: waktu respons \"~52 menit\" adalah batas bawah kategori pengembalian dana; respons keamanan akun berkisar antara 2,4–16,5 jam di seluruh snapshot yang sama. 2021-06-26 adalah puncak sepanjang masa (547,907 permintaan pengembalian dana), bukan titik tengah yang monoton — volumenya melonjak ~6× pada 2020–2021, kemudian turun sebagian sebelum pulih menjadi 373 ribu pada 2026.\nLampiran I — Cakupan kumpulan data · jumlah yang dapat direproduksi\nHitung jumlah catatan. Periksa cakupannya.\nKonteks & batasan sumber\n\nHitunglah jumlah catatan, lalu periksa kebenaran klaim tersebut: setiap angka di bawah ini dapat dihitung ulang berdasarkan file yang telah dipublikasikan.\n\nPeriksa kumpulan data yang mendasarinya, ulangi perhitungan jumlahnya, dan bedakan baris sumber dari kejadian unik.\n\nBerkas CSV utama berisi 40,448 baris. Di antaranya, 36,516 berasal dari saluran phishing Discord-AntiScam. Sisanya 3,932 Data tersebut mencakup GitHub, ulasan, hasil pencarian, materi forum, dan sumber-sumber lainnya, sehingga menyediakan indeks yang komprehensif mengenai topik-topik yang dilaporkan oleh komunitas serta laporan keamanan.\n\nDalam berkas CSV tersebut, 1,690 baris dikategorikan di bawah label kumpulan \"Unpatched Security Exploit\", yang mewakili masalah pengguna di masa lalu dan pengungkapan kerentanan. Untuk melacak laporan-laporan ini, diperlukan peninjauan terhadap garis waktu rilis versi spesifik setiap utas serta riwayat patch publiknya.\n\nArsip yang dapat dicari 16,319-record merupakan versi terpisah yang telah dikurasi dengan manifestnya sendiri, yang dirancang untuk penelusuran lokal yang akurat terhadap klaim pengguna dan laporan insiden tertentu.\n\nUntuk membangun jejak audit yang andal, setiap catatan yang dilaporkan pengguna harus diverifikasi berdasarkan jadwal pengembangan yang terdokumentasi dan riwayat log patch.\n\nCatatan koleksi Bagian II yang terpisah 231,829 ID daftar unik, termasuk 33,509 dalam kategori pendaftaran otomatis dan 198,320 yang ditandai sebagai transfer yang belum diverifikasi. Nilai SHA-256 berkas masukan sesuai dengan pengukuran yang disimpan. Jumlah-jumlah ini menggambarkan upaya pencatatan dan transfer yang teramati, bukan nilai transaksi yang telah diselesaikan atau total pencurian yang terverifikasi, sehingga menyoroti perlunya catatan utama platform untuk mengukur dampak ekonomi yang tepat. Daftar ukuran dan hash ↗\n\nMenguasai CSV ↗ · Daftar isi arsip yang dapat dicari ↗ · Periksa catatan sumber ↗\n\nLampiran J — Tentang penyelidikan ini\nValve tidak mempublikasikan catatan penegakan hukum. Kami sudah membuatnya.\n\nIndependen. Nirlaba. Dibuat semata-mata berdasarkan data publik. Telah diajukan kepada otoritas pengawas.\n\n88.97%armada otomatisasi tetap tidak terpengaruh — tidak ada larangan apa pun\n67.77%dari 51,732 penipu yang telah divonis bebas\n$26.8M+batas minimum pengeluaran di toko oleh armada yang tidak terbatas\n3.6%domain perjudian yang diblokir oleh Filter Tautan Valve\n8 tahuninsiden keamanan yang tercatat\n\nApa ini. Sebuah laporan forensik mengenai platform Steam milik Valve Corporation — catatan penegakan hukumnya, ekonomi \"card-farming\"-nya, kerangka hukumnya, serta infrastruktur otentikasi yang digunakan oleh operator perjudian melalui relai OpenID milik Steam. Setiap angka dapat diverifikasi dari dua sumber: API publik milik Valve sendiri dan kumpulan data yang diterbitkan bersamaan dengan penyelidikan ini.\n\nUntuk siapa. Otoritas pengatur yang memiliki yurisdiksi atas Valve — otoritas pengawas GDPR untuk Belanda, FinCEN, SEC, Koordinator Layanan Digital (DSA), UOKiK, serta lembaga penegak hukum mana pun yang menyelidiki aliran keuangan yang terkait dengan Steam. Juga bagi jurnalis, peneliti, dan setiap pengguna yang mengalami pemblokiran akun permanen, penolakan pengembalian dana, atau kehilangan inventaris, serta diberitahu bahwa tidak ada jalur banding.\n\nTuntutan tunggal. Valve menyimpan data ini dengan akurasi penuh — termasuk alasan pemblokiran, ruang ID lengkap, dan secara real-time. Sistem ini mampu memproses setiap kueri dalam berkas ini dalam hitungan detik dan telah memilih untuk tidak mempublikasikan satupun dari data tersebut. Pertanyaan bagi setiap otoritas yang berwenang sangatlah sederhana: Kenapa tidak?\n\nApa yang tidak diklaim oleh para penulis. Tidak ada proses login ke Steam yang berhasil diselesaikan di platform pihak ketiga mana pun selama pekerjaan ini. URL OpenID yang disediakan menentukan parameter permintaan, bukan proses login yang berhasil. Domain terdaftar yang terpisah tidak dapat dijadikan bukti pengelakan. Tanggal pendaftaran merupakan batas bawah kapan sebuah host pertama kali dapat muncul dalam permintaan OpenID; tanggal tersebut tidak membuktikan penggunaan yang berkelanjutan. Para penulis tidak menyatakan apa yang diketahui atau dimaksudkan oleh Valve: setiap pernyataan mengenai Valve terkait dengan dokumen publik bertanggal atau pengamatan bertanggal. Jika suatu klaim tidak dapat didukung oleh dokumen sumber, klaim tersebut telah dihapus.\n\nTentang Kami\n\nPhishDestroy — penyelidik independen. Tidak terafiliasi dengan Valve Corporation atau platform mana pun yang disebutkan di sini. Satu akun Steam digunakan semata-mata untuk mendokumentasikan permintaan GDPR dalam Bagian 18.\n\nPernyataan Penafian Hukum\n\nPenyelidikan demi kepentingan umum yang bersifat non-komersial dan terdesentralisasi. Semua data disediakan \"apa adanya\" tanpa jaminan apa pun. Publikasi ini bukanlah putusan pengadilan.\n\nDOMAIN UMUM\nPerizinan\n\nSemua hak diserahkan kepada umat manusia. Diperbolehkan untuk mereproduksi, mengadaptasi, dan menerbitkan — tidak perlu mencantumkan sumber. Akses dari wilayah yang diatur oleh OFAC: dilarang. Lisensi lengkap & penafian →",
        "headings": [
          {
            "level": 2,
            "id": "briefing-heading",
            "text": "Aturan. Rekor. Pertanyaan-pertanyaan yang belum terjawab."
          },
          {
            "level": 2,
            "id": null,
            "text": "Surat Terbuka kepada Komisi Perjudian Negara Bagian Washington"
          },
          {
            "level": 3,
            "id": "wsgc-public-address-title",
            "text": "Sepuluh hari berubah menjadi sepuluh tahun.Buka kembali catatan tersebut."
          },
          {
            "level": 2,
            "id": null,
            "text": "Situs tersebut diblokir. Namun, rute masuknya tidak diblokir."
          },
          {
            "level": 3,
            "id": null,
            "text": "Gambar 3.1 — Kedua rute tersebut, digambarkan."
          },
          {
            "level": 3,
            "id": null,
            "text": "Jebakan Pandangan Besar: Filter Tautan Hanyalah Sandiwara Kepatuhan, Bukan Perisai"
          },
          {
            "level": 3,
            "id": null,
            "text": "Domain utama yang diblokir, ditambah dengan host otentikasi yang tidak diblokir, membuat rute masuk tetap terbuka — dan akan tetap terbuka selama bertahun-tahun."
          },
          {
            "level": 3,
            "id": null,
            "text": "Latar Belakang: Apa Itu Steam dan Mengapa Hal Ini Penting dalam Konteks Ini"
          },
          {
            "level": 3,
            "id": null,
            "text": "Apa yang Dilakukan Valve: Pemblokiran Domain"
          },
          {
            "level": 3,
            "id": null,
            "text": "Apa Itu Domain Proksi?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Titik Kritis: Host Otentikasi Dikirim ke Steam dalam Setiap Permintaan"
          },
          {
            "level": 3,
            "id": null,
            "text": "Apa yang Ditunjukkan oleh Hal Ini"
          },
          {
            "level": 3,
            "id": null,
            "text": "Di dalam Steam, daftar Valve adalah satu-satunya daftar."
          },
          {
            "level": 3,
            "id": null,
            "text": "Penyisipan jalur bypass pada sistem perlindungan filter"
          },
          {
            "level": 3,
            "id": null,
            "text": "Peramban web Big Picture membocorkan cookie login dan mengungkapkan informasi sensitif (dapat menyebabkan pengambilalihan akun)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Apa artinya hal ini bagi seorang anak di bawah umur yang telah menginstal antivirus"
          },
          {
            "level": 3,
            "id": null,
            "text": "Usia domain.Tanggal pengamatan."
          },
          {
            "level": 2,
            "id": null,
            "text": "Sebuah titik akhir ditutup. Pelacakan publik kehilangan sebuah kunci."
          },
          {
            "level": 3,
            "id": null,
            "text": "Era Sebelum Pemadaman Listrik"
          },
          {
            "level": 3,
            "id": null,
            "text": "Setelah perubahan tersebut"
          },
          {
            "level": 2,
            "id": null,
            "text": "Satu sesi. Akses yang lebih luas daripada yang terlihat oleh pengguna."
          },
          {
            "level": 3,
            "id": null,
            "text": "1. Otentikasi Bertahap yang Tidak Memadai"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. Tidak adanya Prinsip Hak Akses Terbatas"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. Gangguan dalam Pengelolaan Sesi"
          },
          {
            "level": 3,
            "id": null,
            "text": "4. Pemblokiran Host Otentikasi di Tingkat Domain Secara Teknis Dapat Dilakukan"
          },
          {
            "level": 3,
            "id": "integration-paradox-title",
            "text": "Valve berhasil dikompilasi sesuai aturan tersebut setiap hari. Namun, di sini, kompilasi tidak berhasil sesuai aturan tersebut."
          },
          {
            "level": 4,
            "id": null,
            "text": "Cakupan Tingkat Halus GitHub vs Valve Steam Web API"
          },
          {
            "level": 2,
            "id": null,
            "text": "Simulator Eksploitasi & Pembajakan Interaktif"
          },
          {
            "level": 2,
            "id": null,
            "text": "Titik akhir di balik urutan tersebut."
          },
          {
            "level": 2,
            "id": null,
            "text": "Kotak yang dicentang. Tindakan siapa?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Bagaimana Valve Akhirnya Menetralkan \"Substitusi Perdagangan\" — Dan Mengapa Butuh 7 Tahun Penyesuaian Sementara"
          },
          {
            "level": 4,
            "id": null,
            "text": "Waktu Tunggu Avatar & Nama (Februari 2024)"
          },
          {
            "level": 4,
            "id": null,
            "text": "Pembalikan Tren Perdagangan CS2 Selama 7 Hari (Juli 2025)"
          },
          {
            "level": 4,
            "id": null,
            "text": "Pemberitahuan Push Seluler Wajib untuk API (Desember 2023)"
          },
          {
            "level": 4,
            "id": null,
            "text": "Spanduk Usia & Nama Akun (2022–2024)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Buku pedoman mereka. Platform-platform yang tercatat."
          },
          {
            "level": 3,
            "id": "enforcement-focus-title",
            "text": "Satu buku peraturan. Penegakan yang tidak merata."
          },
          {
            "level": 4,
            "id": null,
            "text": "Otomatisasi"
          },
          {
            "level": 4,
            "id": null,
            "text": "Penggunaan komersial"
          },
          {
            "level": 4,
            "id": null,
            "text": "VPN & penyamaran lokasi"
          },
          {
            "level": 4,
            "id": null,
            "text": "Penyamaran tautan"
          },
          {
            "level": 4,
            "id": null,
            "text": "Siapa yang meninjau keputusan tersebut ketika tim dukungan menutup kasus tersebut?"
          },
          {
            "level": 2,
            "id": null,
            "text": "Sebuah API otomatisasi. Sebuah aturan yang melarang otomatisasi."
          },
          {
            "level": 3,
            "id": null,
            "text": "Kesalahpahaman tentang \"Pengembang Game\""
          },
          {
            "level": 4,
            "id": null,
            "text": "Kontradiksi Otomatisasi"
          },
          {
            "level": 4,
            "id": null,
            "text": "Posisi di sisi server dalam alur perdagangan"
          },
          {
            "level": 2,
            "id": null,
            "text": "Diminta sepuluh hari. Harus mempertanggungjawabkan sepuluh tahun."
          },
          {
            "level": 3,
            "id": "letter-company",
            "text": "VALVE CORPORATION"
          },
          {
            "level": 3,
            "id": null,
            "text": "Sepuluh hari.Lalu bagaimana?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ikuti host pengembalian yang dinyatakan."
          },
          {
            "level": 3,
            "id": "washington-record-heading",
            "text": "Dua batas waktu. Satu standar penegakan hukum yang belum dijelaskan."
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve memberikan waktu 10 hari kepada situs perjudian"
          },
          {
            "level": 4,
            "id": null,
            "text": "Washington menekan Valve"
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve membantah tuduhan tersebut"
          },
          {
            "level": 4,
            "id": null,
            "text": "Rute-rute yang diamati pada bulan September 2026"
          },
          {
            "level": 4,
            "id": null,
            "text": "Delapan belas bulan setelah Valve memberikan tanggapan, otoritas pengawas masih menyebutnya sebagai niat."
          },
          {
            "level": 3,
            "id": null,
            "text": "Dekade Pemberitahuan 10 Hari: Audit Kelangsungan Hidup Forensik di 23 Lokasi yang Disebutkan"
          },
          {
            "level": 4,
            "id": null,
            "text": "Dari Peringatan 10 Hari hingga Konglomerat Luar Negeri: Perputaran Dana Senilai Miliaran Dolar"
          },
          {
            "level": 2,
            "id": null,
            "text": "Nama host sudah tercantum dalam permintaan."
          },
          {
            "level": 3,
            "id": null,
            "text": "Preseden yang terdokumentasi dan dilaporkan"
          },
          {
            "level": 3,
            "id": null,
            "text": "Apa saja yang ditunjukkan dan tidak ditunjukkan oleh tanggal pendaftaran"
          },
          {
            "level": 3,
            "id": null,
            "text": "Audit Komparatif: Standar Kepatuhan API"
          },
          {
            "level": 2,
            "id": "market-thesis-heading",
            "text": "Selisih harga off-Steam"
          },
          {
            "level": 2,
            "id": null,
            "text": "Selisih harga tersebut dapat diukur."
          },
          {
            "level": 3,
            "id": null,
            "text": "Apa yang ditunjukkan oleh angka dalam dolar tersebut"
          },
          {
            "level": 3,
            "id": null,
            "text": "Banyak tempat yang mencantumkan nilai dalam dolar lebih besar dari Steam."
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam masih memimpin dalam hal jumlah penawaran."
          },
          {
            "level": 3,
            "id": null,
            "text": "Ekosistem komersial itu terlihat jelas."
          },
          {
            "level": 2,
            "id": null,
            "text": "Siapa yang bisa mengatur ulang sistem pengaman?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Tiket pemulihan yang menonaktifkan fitur keamanan akun tersebut, serta laporan kerugian sebesar $10,000"
          },
          {
            "level": 3,
            "id": null,
            "text": "Lebih dari sekadar inventaris."
          },
          {
            "level": 3,
            "id": "theft-ledger-title",
            "text": "Valve membuka pintu itu dua kali, dengan selang waktu tiga puluh tiga bulan. Pintu itu tak pernah tertutup."
          },
          {
            "level": 4,
            "id": null,
            "text": "Apa yang tercantum dalam buku besar itu tidak dapat dijelaskan oleh satu kasus pun."
          },
          {
            "level": 3,
            "id": null,
            "text": "Kerahasiaan harus dibarengi dengan akuntabilitas teknis."
          },
          {
            "level": 2,
            "id": null,
            "text": "Telusuri aliran uangnya. Pisahkan transaksi-transaksinya."
          },
          {
            "level": 3,
            "id": null,
            "text": "Di mana uang itu sebenarnya mengalir."
          },
          {
            "level": 3,
            "id": null,
            "text": "Klasifikasikan aktivitasnya terlebih dahulu, baru kemudian kewajibannya."
          },
          {
            "level": 3,
            "id": null,
            "text": "Melacak aliran dana, informasi, dan bantuan."
          },
          {
            "level": 2,
            "id": null,
            "text": "Undang-Undang Layanan Digital: mencatat pengetahuan secara resmi"
          },
          {
            "level": 3,
            "id": null,
            "text": "Tuntutan selama sepuluh hari."
          },
          {
            "level": 3,
            "id": null,
            "text": "Jendela waktu DSA."
          },
          {
            "level": 3,
            "id": null,
            "text": "Durasi memerlukan riwayat pemberitahuan."
          },
          {
            "level": 3,
            "id": null,
            "text": "dari omzet tahunan di seluruh dunia"
          },
          {
            "level": 2,
            "id": null,
            "text": "Anak di bawah umur: login dengan kode Steam bukanlah verifikasi usia"
          },
          {
            "level": 3,
            "id": null,
            "text": "Identifikasi operator dan datanya."
          },
          {
            "level": 3,
            "id": null,
            "text": "Catat proses mulai dari login hingga melakukan setoran."
          },
          {
            "level": 2,
            "id": null,
            "text": "Permintaan. Jawaban. Perbandingan yang terlewatkan."
          },
          {
            "level": 3,
            "id": null,
            "text": "Catatan-catatan tersebut memang ada; namun, subjek data tidak menerimanya."
          },
          {
            "level": 2,
            "id": null,
            "text": "Perjanjian Pelanggan yang bertentangan dengan arsitektur platform itu sendiri"
          },
          {
            "level": 3,
            "id": null,
            "text": "Batas atas harga pasar dan larangan penggunaan untuk keperluan komersial"
          },
          {
            "level": 3,
            "id": null,
            "text": "Kerentanan kunci API merupakan masalah desain platform, bukan kelalaian pengguna"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve menerima nama host otentikasi pada setiap proses masuk"
          },
          {
            "level": 3,
            "id": null,
            "text": "Pola yang terlihat dalam pengaduan yang telah diarsipkan"
          },
          {
            "level": 3,
            "id": null,
            "text": "Pengadilan yang menelaah berkas ini tidak akan menafsirkan SSA secara terpisah."
          },
          {
            "level": 2,
            "id": null,
            "text": "Hasil penelitian. Dokumen-dokumen yang kami minta."
          },
          {
            "level": 2,
            "id": null,
            "text": "Memorandum Bukti — bahan yang disediakan oleh Sumber 1"
          },
          {
            "level": 2,
            "id": null,
            "text": "Pengeditan pada file PDF yang dihasilkan bersifat kosmetik: teks yang disamarkan tetap dapat diekstraksi"
          },
          {
            "level": 2,
            "id": null,
            "text": "Bukti-bukti dalam Surat-surat Dukungan dan Hukum"
          },
          {
            "level": 2,
            "id": null,
            "text": "Catatan primer yang dipilih"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-01",
            "text": "Kunci perangkat keras, yang diminta pada tahun 2016"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-02",
            "text": "Laporan kecelakaan tanpa opsi penolakan yang efektif"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-03",
            "text": "Tindakan penyalahgunaan tiket otentikasi dilaporkan ke Valve"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-01",
            "text": "44 transaksi pembelian di Pasar yang menjadi sengketa"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-02",
            "text": "Larangan permanen dan penutupan jalur banding"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-03",
            "text": "Reset pemulihan dan kerugian yang dilaporkan sebesar $10,000"
          },
          {
            "level": 2,
            "id": null,
            "text": "ArchiSteamFarm dan klausul otomatisasi"
          },
          {
            "level": 2,
            "id": null,
            "text": "Rules ledger: clauses against recorded platforms"
          },
          {
            "level": 3,
            "id": "ledger-title",
            "text": "Penggunaan Komersial & Penagihan Akun"
          },
          {
            "level": 3,
            "id": "lw-register-title",
            "text": "Pendaftaran platform 175"
          },
          {
            "level": 4,
            "id": null,
            "text": "Beban pembuktian"
          },
          {
            "level": 4,
            "id": null,
            "text": "Apa yang dimaksud dengan catatan yang diberi tag, dan apa yang bukan"
          },
          {
            "level": 2,
            "id": null,
            "text": "Panduan DSAR: ajukan permintaan bukti"
          },
          {
            "level": 3,
            "id": null,
            "text": "Jaga garis waktu Anda."
          },
          {
            "level": 3,
            "id": null,
            "text": "Ajukan permohonan untuk mendapatkan data yang disimpan."
          },
          {
            "level": 3,
            "id": null,
            "text": "Simpanlah catatan pengiriman tersebut."
          },
          {
            "level": 3,
            "id": null,
            "text": "Bandingkan tanggapannya."
          },
          {
            "level": 3,
            "id": null,
            "text": "Keamanan akun & riwayat akses"
          },
          {
            "level": 3,
            "id": null,
            "text": "Perbedaan merupakan bukti yang perlu diselidiki."
          },
          {
            "level": 2,
            "id": null,
            "text": "Volume dukungan. Waktu respons yang dipublikasikan."
          },
          {
            "level": 3,
            "id": null,
            "text": "Dua antrean di satu loket layanan pelanggan, seperti yang terlihat pada 21 tangkapan layar yang telah diarsipkan."
          },
          {
            "level": 2,
            "id": null,
            "text": "Hitung jumlah catatan. Periksa cakupannya."
          },
          {
            "level": 2,
            "id": null,
            "text": "Valve tidak mempublikasikan catatan penegakan hukum.\nKami sudah membuatnya."
          }
        ],
        "links": [
          "https://dotesports.com/counter-strike/news/csgo-lounge-billion-bets-3896",
          "https://store.steampowered.com/agreement/?l=english",
          "http://web.archive.org/web/20260921022032/https://store.steampowered.com/agreement/?l=english",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-all-results.json",
          "https://blog.counter-strike.net/expresstrade/",
          "http://web.archive.org/web/20260307161538/https://blog.counter-strike.net/expresstrade/",
          "https://wsgc.wa.gov/news/2016/washington-state-gambling-commission-orders-valve-stop-skins-gambling",
          "http://web.archive.org/web/20260520012601/https://wsgc.wa.gov/news/2016/washington-state-gambling-commission-orders-valve-stop-skins-gambling",
          "https://fr.scribd.com/document/328063293/Valve-s-Oct-18th-response-to-Washington-State-Gambling-Commission-s-cease-and-desist",
          "https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921021947/https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921022628/https://steamcommunity.com/linkfilter/?url=https:%2F%2Frollbit.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rbsnin.com.20260921T021120Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rollbit.com.json",
          "http://web.archive.org/web/20260921022740/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fskin.club",
          "http://web.archive.org/web/20260921022842/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fsc-auth.net",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skin.club.json",
          "http://web.archive.org/web/20260921022603/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fhowl.gg",
          "http://web.archive.org/web/20260921022636/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fhowl.uno",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/howl.gg.json",
          "http://web.archive.org/web/20260921022840/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fduelbits.com",
          "http://web.archive.org/web/20260921022901/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fswitchflips.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/duelbits.com.json",
          "http://web.archive.org/web/20260921022758/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgofast.com",
          "http://web.archive.org/web/20260921022847/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fauthtofast.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgofast.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/farmskins.com.20260921T025840Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/steam.kobal.cc.20260921T025844Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/farmskins.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cobaltlab.tech.20260921T041604Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cobaltauth.com.20260921T041608Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/cobaltlab.tech.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgo.net.20260921T041619Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cn2.easylot.net.20260921T041623Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgo.net.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/ggdrop.com.20260921T041637Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/ggauth.com.20260921T041641Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/ggdrop.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rustchance.com.20260921T041703Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/hgfuihd.com.20260921T041706Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rustchance.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skin.fans.20260921T041710Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.skinfans.com.20260921T041713Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skin.fans.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinport.com.20260921T041724Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinport.app.20260921T041728Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skinport.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skins.cash.20260921T041731Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinscash.live.20260921T041735Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skins.cash.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2hunt.com.20260921T041739Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rstspcl.com.20260921T041742Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tf2hunt.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgogem.com.20260922T192355Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/api.csgem.com.20260922T192358Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-2026-09-22.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/gamdom.com.20260922T192326Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/login.gambldom.com.20260922T192330Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/12cs.fail.20260922T192347Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/fail.games.20260922T192351Z.html",
          "http://web.archive.org/web/20260921022953/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgoempire.com",
          "http://web.archive.org/web/20260921022947/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgoempirelogin4.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgoempire.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cs.money.20260921T021131Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.dota.trade.20260921T021134Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/cs.money.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csfloat.com.20260921T041612Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgofloat.com.20260921T041615Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csfloat.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/g4skins.com.20260921T041630Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.g4s.to.20260921T041634Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/g4skins.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/juice.gg.20260921T041644Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/letmeinjuice.com.20260921T041648Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/juice.gg.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/market.csgo.com.20260921T041652Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2.net.20260921T041655Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/market.csgo.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rust.tm.20260921T041659Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rust.tm.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgolounge.com.20260922T192333Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2.net.20260922T192340Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2lounge.com.20260922T192337Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinbaron.de.20260921T041717Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinbaron.com.20260921T041721Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skinbaron.de.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2royal.com.20260921T041746Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2auth.com.20260921T041750Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tf2royal.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tradeit.gg.20260921T041753Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/connect-tradeit.com.20260921T041757Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tradeit.gg.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/upgrader.pro.20260921T041801Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/upgauth.space.20260921T041804Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/upgrader.pro.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-recheck-2026-09-21.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/domain-registration.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wayback-snapshots.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-2026-09-22c.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/master_registry.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/longitudinal-steam-phishing-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-steam-phishing-100.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-coverage-2026-09-22.json",
          "https://blog.csfloat.com/how-floatdb-tracks-items/",
          "http://web.archive.org/web/20260921022415/https://blog.csfloat.com/how-floatdb-tracks-items/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/platform-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/platforms-removed.json",
          "https://hackerone.com/reports/291750",
          "http://web.archive.org/web/20251116185046/https://hackerone.com/reports/291750",
          "https://hackerone.com/reports/1079561",
          "http://web.archive.org/web/20260924181830/https://hackerone.com/reports/1079561",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/hackerone-reports.json",
          "https://phishdestroy.io/steam_dossier/id/steam_enforcement_evidence.html#support-records",
          "https://www.darknavy.org/blog/exploiting_steam_usual_and_unusual_ways_in_the_cef_framework/",
          "https://steamcommunity.com/groups/SteamClientBeta/discussions/0/3365901765276206401/",
          "http://web.archive.org/web/20250804051514/https://steamcommunity.com/groups/SteamClientBeta/discussions/0/3365901765276206401/",
          "https://www.chromium.org/developers/design-documents/safebrowsing/",
          "http://web.archive.org/web/20260821101616/https://www.chromium.org/developers/design-documents/safebrowsing/",
          "https://www.chromium.org/developers/how-tos/api-keys/",
          "http://web.archive.org/web/20260830122831/https://www.chromium.org/developers/how-tos/api-keys/",
          "https://github.com/Homebrew/homebrew-cask/issues/193814",
          "https://testsafebrowsing.appspot.com/",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/domain-registration.json",
          "https://phishdestroy.io/steam_dossier/id/AUTH_AUDIT.md",
          "https://datatracker.ietf.org/doc/rfc6749/",
          "https://docs.cloud.google.com/docs/authentication/api-keys",
          "https://listings.pcisecuritystandards.org/pdfs/PCI_DSS_Resource_Guide_(003).pdf",
          "https://developer.apple.com/news/?id=02202019a",
          "http://web.archive.org/web/20250506070026/https://developer.apple.com/news/?id=02202019a",
          "https://dev.twitch.tv/docs/authentication/validate-tokens/",
          "https://discuss.dev.twitch.com/t/legacy-twitch-api-v5-i-e-kraken-shutdown-reminder-february-28-2022/36589",
          "http://web.archive.org/web/20250127085635/https://discuss.dev.twitch.com/t/legacy-twitch-api-v5-i-e-kraken-shutdown-reminder-february-28-2022/36589",
          "https://store.steampowered.com/news/posts/?enddate=1788390000",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/4123547285514022851",
          "https://skinvault.gg/blog/cs2-trade-protection-explained/",
          "https://csmarketcap.com/blog/market-insights/from-boom-to-bust-cs2s-trade-protection-impact",
          "https://skin.land/blog/steam-changes-cs2-trade-ban-logic-timing/",
          "https://help.steampowered.com/faqs/view/3041-A87A-E5F6-B6AC",
          "https://steamcommunity.com/ogg/593110/announcements/detail/533224478739530146",
          "https://steamcommunity.com/games/CSGO/announcements/detail/4447966961421256740",
          "https://steamcommunity.com/sharedfiles/filedetails/?id=2926756889",
          "https://steamcommunity.com/dev/apikey",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3734103130194459461",
          "https://steamcommunity.com/discussions/forum/1/3807266184852932971/",
          "https://help.steampowered.com/faqs/view/225C-C51E-B8F0-55B2",
          "https://store.steampowered.com/news/group/4/view/3314112260640237775",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/issues/325",
          "https://blog.dota2.com/2020/05/trading-cooldown/",
          "https://blog.counter-strike.net/index.php/2018/03/20308/",
          "http://web.archive.org/web/20250226114333/https://blog.counter-strike.net/index.php/2018/03/20308/",
          "https://phishdestroy.io/steam_dossier/id/steam_evidence_archive.html",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/493839547938902179",
          "https://store.steampowered.com/online_conduct",
          "http://web.archive.org/web/20260921022120/https://store.steampowered.com/online_conduct",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260918014700/https://store.steampowered.com/subscriber_agreement/",
          "https://steamcommunity.com/dev/apiterms",
          "http://web.archive.org/web/20260921022210/https://steamcommunity.com/dev/apiterms",
          "https://help.steampowered.com/en/faqs/view/628C-E332-BD8C-4D36",
          "https://phishdestroy.io/steam_dossier/id/social_graph.html",
          "https://phishdestroy.io/steam_dossier/id/security_timeline.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wsgc-skins-gambling-briefing-2018.pdf",
          "https://wsgc.wa.gov/sites/default/files/2023-10/Skins%20Gambling.pdf",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wsgc-briefing-manifest.json",
          "https://x.com/csgobig",
          "https://www.facebook.com/csgobigofficial/",
          "https://500.casino/",
          "https://csgolounge.com/",
          "https://csgocasino.gg/",
          "https://x.com/CSGOatsecom",
          "https://x.com/CSGOSweep/status/937420902538543106",
          "https://x.com/Wild",
          "https://x.com/csgopot",
          "https://x.com/csgodiamondscom",
          "https://www.ftc.gov/legal-library/browse/cases-proceedings/162-3184-csgo-lotto-matter",
          "https://x.com/CSGODouble",
          "https://x.com/csgo_massive",
          "https://www.facebook.com/csgostrongfree/",
          "https://www.facebook.com/CSNCOM/",
          "https://www.gamblingcommission.gov.uk/report/young-people-and-gambling",
          "https://www.aph.gov.au/Parliamentary_Business/Committees/Senate/Environment_and_Communications/Gamingmicro-transactions",
          "https://phishdestroy.io/steam_dossier/id/elite_skins.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/csfloat-catalogue.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/skinport-floor-over-cap.json",
          "https://pricempire.com/cs2-marketplaces",
          "http://web.archive.org/web/20260921022459/https://pricempire.com/cs2-marketplaces",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/priceempire-marketplaces.json",
          "https://www.steamanalyst.com/marketplace",
          "http://web.archive.org/web/20260719014552/https://www.steamanalyst.com/marketplace",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-atlas.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json",
          "https://phishdestroy.io/steam_dossier/id/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/id/steam_enforcement_evidence.html#case-support-recovery",
          "https://top10.owasp.org/2025/A01_2025-Broken_Access_Control/",
          "http://web.archive.org/web/20260920212535/https://top10.owasp.org/2025/A01_2025-Broken_Access_Control/",
          "https://store.steampowered.com/privacy_agreement/",
          "http://web.archive.org/web/20260921021648/https://store.steampowered.com/privacy_agreement/",
          "https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "http://web.archive.org/web/20250818113925/https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "https://www.dexerto.com/counter-strike-2/valve-saves-hacked-cs2-player-threatened-with-ransom-over-300000-of-rare-stickers-3283135/",
          "https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "http://web.archive.org/web/20220702042821/https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "https://www.kaspersky.com/blog/cs-go-two-million-usd-inventory-hack/44697/",
          "https://esportfire.com/article/the-2-million-usd-csgo-hack-22062022",
          "http://web.archive.org/web/20260515110250/https://esportfire.com/article/the-2-million-usd-csgo-hack-22062022",
          "https://esportsbetting.com/valve-deletes-130000-stolen-dragon-lore/",
          "https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "http://web.archive.org/web/20251115173120/https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "https://vkplay.ru/media/news/bloger-rasskazal-kak-podderzhka-steam-vorovala-akkaunty-igrokov/",
          "https://lis-skins.com/ru/blog/krupneisaia-mosenniceskaia-sxema-v-istorii-steam/",
          "https://escorenews.com/ru/csgo/news/44056-sotrudniki-podderjki-steam-zanimalis-krajey-skinov-s-akkauntov-za-god-oni-zarabotali-svyshe-300-tysyach-dollarov",
          "https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "http://web.archive.org/web/20250805141942/https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/outsourcing-archive-records.json",
          "https://community.skin.club/en/news/collector-has-steam-inventory-returned-after-bold-hack",
          "https://esportfire.com/article/300k-scam-full-katowice-2014-holo-collection-hacked",
          "http://web.archive.org/web/20251217072445/https://esportfire.com/article/300k-scam-full-katowice-2014-holo-collection-hacked",
          "https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng",
          "http://web.archive.org/web/20260920024236/https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng",
          "https://ag.ny.gov/press-release/2026/attorney-general-james-sues-game-developer-promoting-illegal-gambling-through",
          "http://web.archive.org/web/20260901015430/https://ag.ny.gov/press-release/2026/attorney-general-james-sues-game-developer-promoting-illegal-gambling-through",
          "https://www.fincen.gov/sites/default/files/2019-05/FinCEN%20CVC%20Guidance%20FINAL.pdf",
          "http://web.archive.org/web/20250711185007/https://www.fincen.gov/sites/default/files/2019-05/FinCEN%20CVC%20Guidance%20FINAL.pdf",
          "https://eur-lex.europa.eu/legal-content/EN/LSU/?uri=CELEX:32018L1673",
          "https://eur-lex.europa.eu/eli/dir/2024/1640/oj/eng",
          "http://web.archive.org/web/20260830153004/https://eur-lex.europa.eu/eli/dir/2024/1640/oj/eng",
          "https://eur-lex.europa.eu/eli/reg/2022/2065/oj/eng",
          "http://web.archive.org/web/20260920080125/https://eur-lex.europa.eu/eli/reg/2022/2065/oj/eng",
          "https://phishdestroy.io/steam_dossier/id/legal_analysis.html",
          "https://partner.steamgames.com/doc/features/auth#website",
          "http://web.archive.org/web/20260921022335/https://partner.steamgames.com/doc/features/auth",
          "https://www.ftc.gov/legal-library/browse/rules/childrens-online-privacy-protection-rule-coppa",
          "http://web.archive.org/web/20260921070051/https://www.ftc.gov/legal-library/browse/rules/childrens-online-privacy-protection-rule-coppa",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/gdpr-ticket-1.png",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/screenshot-manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/gdpr-ticket-2.png",
          "https://datenschutz.hamburg.de/beschwerde",
          "https://edpb.europa.eu/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/regulatory-review/disclosure-audit.json",
          "https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "http://web.archive.org/web/20260821155801/https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "https://phishdestroy.io/steam_dossier/id/index#exhibit-gallery-section",
          "https://github.com/ValveSoftware/steam-for-linux/issues/4521",
          "https://phishdestroy.io/steam_dossier/id/steam_evidence_archive.html?source=GitHub&record=484",
          "https://github.com/ValveSoftware/steam-for-linux/issues/6459",
          "http://web.archive.org/web/20260419051343/https://github.com/ValveSoftware/steam-for-linux/issues/6459",
          "https://phishdestroy.io/steam_dossier/id/steam_evidence_archive.html?source=GitHub&record=467",
          "https://github.com/ValveSoftware/Source-1-Games/issues/3857",
          "https://phishdestroy.io/steam_dossier/id/steam_evidence_archive.html?source=GitHub&record=768",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "http://web.archive.org/web/20250320082450/https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://phishdestroy.io/steam_dossier/id/steam_evidence_archive.html?source=Reddit&record=4533",
          "https://www.reddit.com/r/ohnePixel/comments/1hahqx2/permanently_banned_steam_account_without_a_clear/",
          "https://phishdestroy.io/steam_dossier/id/steam_evidence_archive.html?source=Reddit&record=4766",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://phishdestroy.io/steam_dossier/id/steam_evidence_archive.html?source=Reddit&record=4592",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/selected-evidence-records.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive_manifest.json",
          "https://phishdestroy.io/steam_dossier/id/card_economy.html",
          "https://github.com/JustArchiNET/ArchiSteamFarm/wiki/FAQ",
          "https://phishdestroy.io/steam_dossier/id/card_economy.html#scale",
          "https://phishdestroy.io/steam_dossier/id/card_economy.html#licence",
          "https://phishdestroy.io/steam_dossier/id/enforcement_audit.html",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "http://web.archive.org/web/20260924181709/https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://rdap.verisign.com/com/v1/domain/csgoempire.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoempire.com",
          "https://rdap.verisign.com/com/v1/domain/csgoempirelogin4.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/csgoempire.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustreaper.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustreaper.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/rustreaper.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustly.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustly.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/rustly.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgofast.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgofast.com",
          "https://rdap.verisign.com/com/v1/domain/authtofast.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/csgofast.com.json",
          "https://rdap.verisign.com/com/v1/domain/duelbits.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fduelbits.com",
          "https://rdap.verisign.com/com/v1/domain/switchflips.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/duelbits.com.json",
          "https://rdap.verisign.com/com/v1/domain/farmskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffarmskins.com",
          "https://tld-rdap.verisign.com/cc/v1/domain/kobal.cc",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/farmskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoluck.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoluck.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/csgoluck.com.json",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/domain-registry/insane.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Finsane.gg",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/insane.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs2skin.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs2skin.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/cs2skin.com.json",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/domain-registry/juice.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fjuice.gg",
          "https://rdap.verisign.com/com/v1/domain/letmeinjuice.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/juice.gg.json",
          "https://rdap.verisign.com/com/v1/domain/ggdrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fggdrop.com",
          "https://rdap.verisign.com/com/v1/domain/ggauth.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/ggdrop.com.json",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/domain-registry/howl.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhowl.gg",
          "https://rdap.radix.host/rdap/domain/howl.uno",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/howl.gg.json",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/domain-registry/chicken.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fchicken.gg",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/chicken.gg.json",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/domain-registry/csgocasino.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgocasino.gg",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/csgocasino.gg.json",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/domain-registry/hunt.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhunt.gg",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/hunt.gg.json",
          "https://rdap.verisign.com/com/v1/domain/csbattle.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsbattle.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/csbattle.com.json",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/domain-registry/skinrave.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinrave.gg",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/skinrave.gg.json",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/domain-registry/csdouble.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsdouble.gg",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/csdouble.gg.json",
          "https://rdap.verisign.com/com/v1/domain/rustchance.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustchance.com",
          "https://rdap.verisign.com/com/v1/domain/hgfuihd.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/rustchance.com.json",
          "https://rdap.radix.host/rdap/domain/cobaltlab.tech",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcobaltlab.tech",
          "https://rdap.verisign.com/com/v1/domain/cobaltauth.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/cobaltlab.tech.json",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/domain-registry/raided.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fraided.gg",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/raided.gg.json",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/domain-registry/rustneo.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustneo.gg",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/rustneo.gg.json",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/domain-registry/splits.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsplits.gg",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/splits.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/upgrader.pro",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fupgrader.pro",
          "https://rdap.radix.host/rdap/domain/upgauth.space",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/upgrader.pro.json",
          "https://rdap.centralnic.com/fans/domain/skin.fans",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.fans",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/skin.fans.json",
          "https://rdap.nic.one/domain/hotpizza.one",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhotpizza.one",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/hotpizza.one.json",
          "https://rdap.verisign.com/com/v1/domain/g4skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg4skins.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/g4skins.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2royal.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2royal.com",
          "https://rdap.verisign.com/com/v1/domain/tf2auth.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/tf2royal.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2hunt.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2hunt.com",
          "https://rdap.verisign.com/com/v1/domain/rstspcl.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/tf2hunt.com.json",
          "https://rdap.identitydigital.services/rdap/domain/tf2.bet",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2.bet",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/tf2.bet.json",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/domain-registry/openstars.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fopenstars.gg",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/openstars.gg.json",
          "https://rdap.verisign.com/com/v1/domain/skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/skins.com.json",
          "https://rdap.identitydigital.services/rdap/domain/white.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwhite.market",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/white.market.json",
          "https://rdap.identitydigital.services/rdap/domain/moon.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmoon.market",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/moon.market.json",
          "https://rdap.verisign.com/com/v1/domain/csfloat.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsfloat.com",
          "https://rdap.verisign.com/com/v1/domain/csgofloat.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/csfloat.com.json",
          "https://rdap.identitydigital.services/rdap/domain/skin.land",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.land",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/skin.land.json",
          "https://rdap.verisign.com/com/v1/domain/haloskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhaloskins.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/haloskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/163.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuff.163.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/buff.163.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmarket.csgo.com",
          "https://rdap.verisign.com/net/v1/domain/dota2.net",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/market.csgo.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinport.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinport.com",
          "https://pubapi.registry.google/rdap/domain/skinport.app",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/skinport.com.json",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/domain-registry/skinflow.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinflow.gg",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/skinflow.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/skin.place",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.place",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/skin.place.json",
          "https://rdap.verisign.com/com/v1/domain/skinsmonkey.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinsmonkey.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/skinsmonkey.com.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbaron.de",
          "https://rdap.verisign.com/com/v1/domain/skinbaron.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/skinbaron.de.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frust.tm",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/rust.tm.json",
          "https://rdap.verisign.com/com/v1/domain/pirateswap.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fpirateswap.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/pirateswap.com.json",
          "https://rdap.radix.host/rdap/domain/mannco.store",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmannco.store",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/mannco.store.json",
          "https://rdap.verisign.com/com/v1/domain/skinswap.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinswap.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/skinswap.com.json",
          "https://rdap.verisign.com/com/v1/domain/exeskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fexeskins.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/exeskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/balticskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbalticskins.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/balticskins.com.json",
          "https://rdap.nic.trade/domain/cs.trade",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.trade",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/cs.trade.json",
          "https://rdap.verisign.com/com/v1/domain/rapidskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frapidskins.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/rapidskins.com.json",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/domain-registry/tradeit.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftradeit.gg",
          "https://rdap.verisign.com/com/v1/domain/connect-tradeit.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/tradeit.gg.json",
          "https://rdap.verisign.com/com/v1/domain/49skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F49skins.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/49skins.com.json",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/domain-registry/skinvault.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinvault.gg",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/skinvault.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/aim.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Faim.market",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/aim.market.json",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/domain-registry/skinout.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinout.gg",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/skinout.gg.json",
          "https://rdap.verisign.com/com/v1/domain/ntskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fntskins.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/ntskins.com.json",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/domain-registry/gamerpay.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamerpay.gg",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/gamerpay.gg.json",
          "https://rdap.nic.tf/domain/scrap.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fscrap.tf",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/scrap.tf.json",
          "https://rdap.nic.tf/domain/marketplace.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmarketplace.tf",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/marketplace.tf.json",
          "https://rdap.identitydigital.services/rdap/domain/skins.cash",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.cash",
          "https://rdap.identitydigital.services/rdap/domain/skinscash.live",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/skins.cash.json",
          "https://rdap.verisign.com/net/v1/domain/csgo.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo.net",
          "https://rdap.verisign.com/net/v1/domain/easylot.net",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/csgo.net.json",
          "https://rdap.verisign.com/net/v1/domain/cybershoke.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcybershoke.net",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/cybershoke.net.json",
          "https://rdap.verisign.com/net/v1/domain/fastcup.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffastcup.net",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/fastcup.net.json",
          "https://rdap.verisign.com/com/v1/domain/leetify.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fleetify.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/leetify.com.json",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/domain-registry/scope.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fscope.gg",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/scope.gg.json",
          "https://rdap.verisign.com/com/v1/domain/tradeupspy.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftradeupspy.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/tradeupspy.com.json",
          "https://rdap.identitydigital.services/rdap/domain/cs.deals",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.deals",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/cs.deals.json",
          "https://rdap.verisign.com/com/v1/domain/pricempire.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fpricempire.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/pricempire.com.json",
          "https://rdap.identitydigital.services/rdap/domain/lzt.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flzt.market",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/lzt.market.json",
          "https://rdap.verisign.com/com/v1/domain/z2u.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fz2u.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/z2u.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoroll.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoroll.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/csgoroll.com.json",
          "https://rdap.verisign.com/com/v1/domain/rollbit.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frollbit.com",
          "https://rdap.verisign.com/com/v1/domain/rbsnin.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/rollbit.com.json",
          "https://rdap.identitydigital.services/rdap/domain/500.casino",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F500.casino",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/500.casino.json",
          "https://rdap.verisign.com/com/v1/domain/csgobig.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgobig.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/csgobig.com.json",
          "https://rdap.verisign.com/com/v1/domain/casedrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcasedrop.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/casedrop.com.json",
          "https://rdap.verisign.com/com/v1/domain/banditcamp.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbanditcamp.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/banditcamp.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinbox.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbox.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/skinbox.com.json",
          "https://rdap.verisign.com/com/v1/domain/tastydrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftastydrop.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/tastydrop.com.json",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/domain-registry/csgopolygon.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgopolygon.gg",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/csgopolygon.gg.json",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/domain-registry/magicdrop.ru.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmagicdrop.ru",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/magicdrop.ru.json",
          "https://rdap.verisign.com/com/v1/domain/csdice.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsdice.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/csdice.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinodds.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinodds.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/skinodds.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgowin.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgowin.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/csgowin.com.json",
          "https://rdap.verisign.com/net/v1/domain/csgorun.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgorun.net",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/csgorun.net.json",
          "https://rdap.verisign.com/com/v1/domain/openskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fopenskins.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/openskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustbet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustbet.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/rustbet.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgomagic.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgomagic.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/csgomagic.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgobounty.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgobounty.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/csgobounty.com.json",
          "https://rdap.verisign.com/com/v1/domain/ezskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fezskins.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/ezskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustcases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustcases.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/rustcases.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoreaper.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoreaper.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/csgoreaper.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgocases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgocases.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/csgocases.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo-skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo-skins.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/csgo-skins.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgonet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgonet.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/csgonet.com.json",
          "https://rdap.verisign.com/com/v1/domain/wtfskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwtfskins.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/wtfskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/flamecases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fflamecases.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/flamecases.com.json",
          "https://rdap.verisign.com/com/v1/domain/gamedom.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamedom.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/gamedom.com.json",
          "https://rdap.nic.club/domain/skin.club",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.club",
          "https://rdap.verisign.com/net/v1/domain/sc-auth.net",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/skin.club.json",
          "https://rdap.verisign.com/com/v1/domain/daddyskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdaddyskins.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/daddyskins.com.json",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/domain-registry/rustix.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustix.gg",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/rustix.gg.json",
          "https://rdap.nic.club/domain/skins.club",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.club",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/skins.club.json",
          "https://rdap.publicinterestregistry.org/rdap/domain/csgohouse.org",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgohouse.org",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/csgohouse.org.json",
          "https://rdap.verisign.com/net/v1/domain/skinrave.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinrave.net",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/skinrave.net.json",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/domain-registry/bloodycase.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbloodycase.gg",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/bloodycase.gg.json",
          "https://rdap.verisign.com/com/v1/domain/csgoclicker.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoclicker.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/csgoclicker.com.json",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/domain-registry/rustbet.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustbet.gg",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/rustbet.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs-drop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs-drop.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/cs-drop.com.json",
          "https://rdap.verisign.com/net/v1/domain/hellstore.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhellstore.net",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/hellstore.net.json",
          "https://rdap.verisign.com/com/v1/domain/rustloot.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustloot.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/rustloot.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo-case.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo-case.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/csgo-case.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgogem.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgogem.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/csgogem.com.json",
          "https://rdap.verisign.com/com/v1/domain/rainbet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frainbet.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/rainbet.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustclash.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustclash.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/rustclash.com.json",
          "https://rdap.identitydigital.services/rdap/domain/12cs.fail",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F12cs.fail",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/12cs.fail.json",
          "https://rdap.verisign.com/com/v1/domain/tf2easy.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwww.tf2easy.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/tf2easy.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2blaze.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2blaze.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/tf2blaze.com.json",
          "https://rdap.verisign.com/com/v1/domain/shuffle.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fshuffle.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/shuffle.com.json",
          "https://rdap.identitydigital.services/rdap/domain/buff.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuff.market",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/buff.market.json",
          "https://rdap.identitydigital.services/rdap/domain/avan.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Favan.market",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/avan.market.json",
          "https://rdap.identitydigital.services/rdap/domain/cs.money",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.money",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/cs.money.json",
          "https://rdap.verisign.com/com/v1/domain/uuskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fuuskins.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/uuskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/youpin898.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fyoupin898.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/youpin898.com.json",
          "https://rdap.verisign.com/com/v1/domain/c5game.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fc5game.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/c5game.com.json",
          "https://rdap.verisign.com/com/v1/domain/waxpeer.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwaxpeer.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/waxpeer.com.json",
          "https://rdap.verisign.com/com/v1/domain/dmarket.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdmarket.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/dmarket.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamcommunity.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamcommunity.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/steamcommunity.com.json",
          "https://rdap.verisign.com/com/v1/domain/lootfarm.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flootfarm.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/lootfarm.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustskins.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/rustskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/krakatoa.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fkrakatoa.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/krakatoa.com.json",
          "https://rdap.verisign.com/com/v1/domain/shadowpay.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fshadowpay.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/shadowpay.com.json",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/domain-registry/igxe.cn.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Figxe.cn",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/igxe.cn.json",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/domain-registry/swap.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fswap.gg",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/swap.gg.json",
          "https://rdap.verisign.com/com/v1/domain/bitskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbitskins.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/bitskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2mart.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2mart.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/tf2mart.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinbid.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbid.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/skinbid.com.json",
          "https://rdap.verisign.com/com/v1/domain/lootbear.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flootbear.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/lootbear.com.json",
          "https://rdap.nic.tf/domain/backpack.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbackpack.tf",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/backpack.tf.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fstntrading.eu",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/stntrading.eu.json",
          "https://rdap.verisign.com/com/v1/domain/skinwallet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinwallet.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/skinwallet.com.json",
          "https://rdap.verisign.com/com/v1/domain/dota2market.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdota2market.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/dota2market.com.json",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/domain-registry/xplay.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fxplay.gg",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/xplay.gg.json",
          "https://rdap.verisign.com/com/v1/domain/esportal.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fesportal.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/esportal.com.json",
          "https://rdap.registro.br/domain/gamersclub.com.br",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamersclub.com.br",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/gamersclub.com.br.json",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/domain-registry/epidemic.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fepidemic.gg",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/epidemic.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs2stash.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs2stash.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/cs2stash.com.json",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/domain-registry/csgoskins.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoskins.gg",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/csgoskins.gg.json",
          "https://rdap.verisign.com/com/v1/domain/steamanalyst.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamanalyst.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/steamanalyst.com.json",
          "https://rdap.verisign.com/net/v1/domain/steamcardexchange.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamcardexchange.net",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/steamcardexchange.net.json",
          "https://rdap.verisign.com/com/v1/domain/dotabuff.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdotabuff.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/dotabuff.com.json",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/domain-registry/tracker.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftracker.gg",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/tracker.gg.json",
          "https://rdap.verisign.com/com/v1/domain/funpay.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffunpay.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/funpay.com.json",
          "https://rdap.verisign.com/com/v1/domain/playerauctions.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fplayerauctions.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/playerauctions.com.json",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/domain-registry/eldorado.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Feldorado.gg",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/eldorado.gg.json",
          "https://rdap.verisign.com/com/v1/domain/g2a.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg2a.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/g2a.com.json",
          "https://rdap.verisign.com/net/v1/domain/kinguin.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fkinguin.net",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/kinguin.net.json",
          "https://rdap.verisign.com/com/v1/domain/g2g.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg2g.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/g2g.com.json",
          "https://rdap.verisign.com/com/v1/domain/playerup.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fplayerup.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/playerup.com.json",
          "https://rdap.verisign.com/net/v1/domain/smurfhub.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfhub.net",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/smurfhub.net.json",
          "https://rdap.verisign.com/com/v1/domain/smurfaccounts.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfaccounts.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/smurfaccounts.com.json",
          "https://rdap.verisign.com/com/v1/domain/buycsgorank.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuycsgorank.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/buycsgorank.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgosmurfkings.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgosmurfkings.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/csgosmurfkings.com.json",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/domain-registry/smurfstore.co.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfstore.co",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/smurfstore.co.json",
          "https://rdap.verisign.com/com/v1/domain/steamlvlup.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlvlup.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/steamlvlup.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamlevels.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlevels.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/steamlevels.com.json",
          "https://rdap.verisign.com/com/v1/domain/levelsteam.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flevelsteam.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/levelsteam.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamlevelu.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlevelu.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/steamlevelu.com.json",
          "https://rdap.verisign.com/com/v1/domain/eloking.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Feloking.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/eloking.com.json",
          "https://rdap.publicinterestregistry.org/rdap/domain/boosteria.org",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fboosteria.org",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/boosteria.org.json",
          "https://rdap.verisign.com/com/v1/domain/overgear.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fovergear.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/overgear.com.json",
          "https://rdap.verisign.com/com/v1/domain/blazingboost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fblazingboost.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/blazingboost.com.json",
          "https://rdap.verisign.com/com/v1/domain/dota2boost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdota2boost.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/dota2boost.com.json",
          "https://rdap.verisign.com/com/v1/domain/buyboost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuyboost.com",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit/buyboost.com.json",
          "https://phishdestroy.io/steam_dossier/id/steam_tos_assets/auth-route-audit.json",
          "https://help.steampowered.com/en/faqs/view/365F-4BEE-2AE2-7BDD",
          "https://store.steampowered.com/privacy_agreement/#8",
          "https://www.edpb.europa.eu/system/files/2023-04/edpb_guidelines_202201_data_subject_rights_access_v2_en.pdf",
          "https://web.archive.org/web/20260810154631/https://store.steampowered.com/stats/support",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/design-review/part2/measurements.json",
          "https://phishdestroy.io/steam_dossier/id/VALVE_EVIDENCE_PACK/databases/TOTAL_VALVE_SCANDALS_MASTER_DB.csv",
          "https://phishdestroy.io/steam_dossier/id/license_disclaimer.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/id/index.content.json",
      "export_json_sha256": "d87f996d80048d21b88b7ebdd0be4ed89d07954aeb82b0331a80aa48b669c153"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "id/investigation_part2.html",
      "language": "id",
      "title": "Akses akun & pertanggungjawaban — Dokumen Steam",
      "source_url": "https://phishdestroy.io/steam_dossier/id/investigation_part2",
      "source_html_sha256": "7f32b4809da1776600a6351d49b76f13f3ac67559d40159402eae199fdbc150e",
      "exported_at": "2026-09-29T00:22:28.416Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "investigation_part2.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/id/investigation_part2.pdf?v=print-20260929-v5",
        "sha256": "fc48adbf34e27326ae649f5c6b12c40406cb8172c3fdced2e501a54d0149c68b",
        "bytes": 126114,
        "pages": 9
      },
      "integrity": {
        "signed_object": "investigation_part2.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "investigation_part2.content.json.asc",
        "digest_file": "investigation_part2.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify investigation_part2.content.json.asc investigation_part2.content.json",
          "sha256sum -c investigation_part2.content.json.sha256"
        ]
      },
      "content": {
        "text": "DOSSIER STEAM / II\n\nAkun Anda.Akses mereka.Siapa yang menjawab?\n\nOtomatisasi publik. Dukungan yang diserahkan kepada pihak ketiga. Masyarakatlah yang akhirnya menanggung akibatnya.\n\nTelusuri infrastrukturnya, kerugian yang dilaporkan, serta dokumen-dokumen yang menjadi dasar klaim tersebut.\n\nMelacak infrastruktur ↘\nLAMPIRAN 01 / PEMANTAUAN PASAR GELAP SECARA LANGSUNG550,000+\n\nSteam akun yang sedang ditawarkan di FSB Market (nama samaran; nama asli tidak disebutkan di sini)\npada saat ini juga\n\n550,000+ STOK TERKINI · 231,829 DALAM KORPUS HISTORIS YANG DIKUMPULKAN (198,320 LOG STEALER)\n\nPusat penyaluran bawah tanah utama untuk akun Steam yang dibajak, FSB Market (nama terkait lainnya tidak disebutkan), melakukan verifikasi identitas baik pembeli maupun penjual menggunakan OpenID resmi Valve Steam (openid.realm = https://FSB Market). Setiap menitnya, lebih dari setengah juta akun yang dicuri dan diretas (log pencurian dari RedLine/Lumma, hasil penangkapan phishing, serta serangan credential stuffing) secara aktif ditawarkan dengan harga yang sangat murah ($0.50–$2.00). Baik FSB Market atau forum terkait diblokir oleh Filter Tautan milik Valve. Ini adalah sumber utama yang memasok akun bot berbayar 63.06% yang diblokir oleh Valve tanpa memberikan bantuan kepada korban.\n\nData Real-Time: Pemantauan Pasar Gelap (Lebih dari 550 ribu pengguna aktif) ↗ · Buka catatan penangkapan ↗ · Buka jejak Filter Tautan ↗550 ribu+ LIVE\n\n01 / EKOSISTEM BERSAMA PARA PENULIS\n\nOtomatisasi telahjejak dokumen.\n\nProyek-proyek yang disebutkan. Kemampuan yang dipublikasikan. Telusuri sebuah alat hingga ke dokumentasinya, lalu periksa hubungan-hubungan pengembang yang terkumpul.\n\n252REPOSITORI YANG DIKUMPULKAN\n3,320PROFIL GITHUB\n4,214PROFIL–PASANGAN REPOSITORI\nValve infrastrukturPerpustakaan komunitasAplikasi yang dapat digunakan kembali\nGaris-garis tersebut menunjukkan integrasi atau ketergantungan yang terdokumentasi. Pilih sebuah simpul untuk melihat bukti yang terkait dengannya.\n\nOtomatisasi multi-akun / JustArchiNET\n\nArchiSteamFarm\n\nProyek ini secara eksplisit mempromosikan praktik \"card farming\" secara bersamaan di seluruh akun Steam. Berkas proyeknya mencantumkan ketergantungan pada SteamKit2.\n\nBaca dokumentasi proyek tersebut ↗\n\nSteamKit → ArchiSteamFarm\nketergantungan yang dinyatakan ↗\n\nKUMPULAN HUBUNGAN\n\n40 label kontributor · 40 label forker\n\nContoh kontributor di bawah ini. Label-label ini menjelaskan hubungan dengan repositori, bukan hubungan kerja atau persetujuan.\n\n@JustArchi@renovate[bot]@JustArchi-ArchiBot@dependabot-preview[bot]@renovate-bot@pengguna-aksi@dependabot-support@Abrynos\nApa yang ditunjukkan oleh grafik pengembang\n\nGrafik tersebut memetakan hubungan kontributor dan pembuat fork yang telah dipublikasikan antara proyek-proyek yang disebutkan dan profil GitHub. Ini adalah catatan publik — fork repositori, daftar kontribusi, serta hubungan profil. Pertanyaannya adalah apa yang perlu dijawab oleh jejak dokumentasi mengenai kemampuan yang dipublikasikan dan hubungan pengembang Valve, bukan apa yang diciptakan oleh penyelidikan ini. Hash sumber disimpan di menelusuri asal-usul peta.\n\nJelajahi seluruh jaringan ↗Data sumber repositori ↓\n\n02 / KREDENTIAL YANG BERBEDA. KEKUATAN YANG BERBEDA.\n\nTombol manaApa yang sedang kita bicarakan?\n\nBermain game tidak mengharuskan pemain untuk membuat kunci API Web pribadi. Itulah perbedaan utama yang menjadi inti dari penyelidikan ini.\n\n01 / AKUN PENGGUNA\nKunci API Web Pribadi\nsteamcommunity.com/dev/apikey\n\nDiterbitkan dari akun pengguna untuk panggilan API yang diizinkan. Pembuatan kunci, visibilitas, pencabutan, dan deteksi penyalahgunaan merupakan aspek keamanan akun.\n\n02 / BACKEND PERMAINAN\nKunci API Web Penerbit\n\nMitra Steamworks menggunakan kredensial penerbit untuk operasi backend yang didukung, termasuk layanan yang berkaitan dengan game. Kunci pribadi pemain merupakan kredensial yang berbeda.\n\n03 / IDENTITAS & SESI\nOpenID / token sesi\n\nOpenID digunakan untuk memverifikasi identitas kepada sebuah situs web. Token sesi atau token penyegaran Steam memiliki tujuan yang berbeda. Mekanisme-mekanisme ini tidak boleh disamakan sebagai satu “kunci API” yang dapat saling menggantikan.\n\nValve mencatat kunci API Web baik dari pengguna maupun penerbit. Oleh karena itu, seluruh API Web tidak terpisah dari Steamworks. Dokumentasi kunci API ↗ diarsipkan 2026-09-15 ↗ · Otentikasi sesi permainan ↗ diarsipkan 2026-08-29 ↗\n\nDIDOKUMENTASIKAN OLEH PENULIS ALAT INI / MARET 2024\n\nOtomatisasi dapat menggunakan lebih dari satu kunci API.\n\nWiki Trade Offer Manager menjelaskan penggunaan token akses sesi untuk beberapa bagian Web API ketika tidak ada kunci API terpisah. Wiki tersebut juga mencatat proses konfirmasi melalui perangkat seluler untuk pembuatan kunci yang mulai berlaku sejak akhir 2023. Pengelola wiki menyatakan bahwa penggunaan token dengan cara ini tidak didukung oleh Valve; ini merupakan pernyataan dalam dokumentasi yang sudah usang, bukan hasil pengujian bypass yang masih berlaku.\n\nPeriksa penjelasan pengelola ↗ diarsipkan 2026-09-24 ↗\n\nSISI MANUSIA / JALUR PHISHING YANG DIILUSTRASIKAN\n\nMasih bermain.Sudah terungkap.\n\nSebuah pesan dari seorang teman. Permintaan untuk memberikan suara. Halaman ucapan “terima kasih”. Bagi pemain, tugas tersebut telah selesai. Namun, sesi yang telah diretas bisa bertahan lebih lama dari momen tersebut.\n\nDI LAYAR PEMUTAR\n\nF\nKISAH SEORANG TEMAN\n\n“Bisakah kamu memilih tim kami?”\n\nPermintaan tersebut masuk melalui obrolSteamdari akun yang sudah dikenal. Dalam skenario ini, halaman yang ditautkan terbuka di peramban klien.\n\nTIDAK TERLIHAT\n\nKepercayaan itu sudah terbentuk sebelum situs web tersebut ada.\n\nAkun teman yang diretas dapat membuat tautan phishing tampak lebih meyakinkan. Antarmuka Steam yang mengelilinginya tidak menjamin keaslian situs web tujuan.\n\nPENGIRIM YANG DIKENAL / TUJUAN EKSTERNAL\nKeamanan akun merupakan hal yang harus diperhatikan sebelum suatu barang dijual.\n\nPemain tersebut tidak bermaksud membuat kredensial otomatisasi atau mendelegasikan kendali. Kembali ke permainan bukanlah bukti bahwa akun tersebut aman. Valve menyimpan log sesi, catatan pembuatan kunci API, dan data korelasi perangkat. Korban tidak memilikinya. Asimetri itulah yang menjadi masalah pertanggungjawaban.\n\nAkses sesi dan jenis kredensial\n\nKunci API dan sesi yang sedang aktif adalah kredensial terpisah dengan kemampuan yang berbeda. Mencabut kunci tidak akan mengakhiri sesi yang sedang aktif. Dokumentasi Valve sendiri menjelaskan keduanya; Valve menyimpan log yang akan menunjukkan kredensial mana yang aktif pada saat terjadinya tindakan yang dipermasalahkan. Yang diminta adalah pengungkapan catatan tersebut — bukan kesimpulan yang dibuat-buat oleh penyelidikan. Dokumentasi pengelola mengenai penanganan token ↗ diarsipkan 2026-09-24 ↗ · Valve dokumentasi utama ↗ diarsipkan 2026-09-15 ↗\n\n03 / PASAR RESMI MEMILIKI BATAS ATAS\n\nBarang tersebut mungkin langka.Batas tersebut tetap berlaku.\n\nHarga yang melebihi batas atas penawaran tidak dapat direalisasikan melalui satu penawaran di Community Market dengan harga penuh tersebut.\n\nHARGA PERMINTAAN SEBAGAI ILUSTRASI$5,000Ubah harga yang ditawarkan untuk barang tersebut\n$100$20,000\n\nIlustrasi mengenai batas yang telah dipublikasikan, bukan penilaian atau rekomendasi untuk bertransaksi.\n\nBATAS PENDAFTARAN≈ $1,800\nTUTUP DOMPET≈ $2,000\n\nMelebihi batas penawaran yang telah dipublikasikan.\n\nDana di dompet tidak dapat ditarik ke rekening bank. Keterbatasan ini menciptakan permintaan yang dipenuhi oleh pasar skin pihak ketiga: permintaan yang muncul akibat batasan pencatatan dan batas saldo dompet, sementara aturan Valve sendiri melarang operator komersial untuk memenuhinya.\n\nBatas pasar Steam ↗ diarsipkan 2026-09-21 ↗\n\n04 / DI DALAM BATAS DUKUNGAN\n\nDipercayakan untuk mengelola data.Bertanggung jawab atas akses.\n\nKebijakan privasi Valve secara tegas mengatur tentang pembagian data pribadi dengan penyedia layanan dukungan pihak ketiga, sejauh hal tersebut diperlukan untuk keperluan dukungan.\n\nPEMAINAkun & bukti\n→\nKATUPProses pemulihan\n→\nPENYEDIA LAYANANAkses yang didelegasikan\n\nKebijakan Privasi §5.2 ↗ · Kebijakan Valve sendiri mengizinkan akses dukungan oleh pihak ketiga. Pertanyaan-pertanyaan yang masih belum terjawab adalah: izin apa saja yang telah diberikan, jejak audit apa saja yang ada, dan apa yang terjadi ketika akses tersebut diduga disalahgunakan.\n\n2015\nTimbangan itu terbuka untuk umum\n\nValve mengakui adanya pencurian akun yang meluas dan menjelaskan langkah-langkah pencegahan.\n\nValve terbitan ↗diarsipkan 2026-08-09 ↗\n2015\nValve menyerahkan tugas tersebut kepada pihak luar — dan mengakuinya\n\nValve memiliki tim kepemimpinan dukungan internal yang kecil Steam dan menyatakan hal tersebut \"telah mempekerjakan beberapa perusahaan yang berbeda\" untuk menangani layanan dukungan (Erik Johnson, Valve, kepada Kotaku); pasal 5.2 kebijakan privasinya memberikan wewenang kepada pihak ketiga tersebut untuk mengakses data pengguna. Kontraktor mana yang memiliki akses untuk pemulihan akun, Valve tidak pernah mengungkapkannya — Dalam diskusi komunitas disebutkan beberapa penyedia layanan seperti Concentrix, namun tidak ada yang Valve-dikonfirmasi. Unit layanan yang dialihdayakan tersebut sudah beroperasi bertahun-tahun sebelum kedua pengakuan di bawah ini.\n\nKotaku: Valve mengenai dukungan yang diberikannya ↗diarsipkan 2025-07-11 ↗\n2023\nPenerimaan pertama\n\nTim CS:GO milik Valve secara tertulis mengakui tanggung jawab atas akun yang diretas melalui proses permintaan bantuan miliknya sendiri, dan membatalkan transaksi tersebut.\n\nBuka kasus outsourcing ↓\n2025\nPenerimaan kedua\n\n33 bulan kemudian, Steam Tim Dukungan menulis bahwa seorang teknisi \"gagal mengikuti prosedur kami, yang mengakibatkan akun Anda dikembalikan kepada orang lain.\" Saluran yang sama. Hasil yang sama.\n\nDexerto, 14 November 2025 ↗\n\nBERKAS KASUS / HFB DAN TUDUHAN OUTSOURCING\n\nJalan masuknya adalah Steam Dukungan itu sendiri.Valve telah menyatakan hal itu secara tertulis.\n\nDalam balasan dari tim dukungan yang dipublikasikan oleh Dexerto, tim CS:GO milik Valve mengakui bertanggung jawab atas akun yang diretas melalui proses permohonan bantuan — saluran resminya sendiri, bukan halaman phishing dan bukan pengguna. Barang-barang tersebut berhasil dikembalikan dan transaksi dibatalkan, yang merupakan solusi yang menurut Valve tidak tersedia bagi korban lainnya. Stok HFB dilaporkan sebesar $2,000,000+ pada hari itu dan $3,000,000+ dalam tindak lanjut; Qkss kalah $1,000,000+ dengan cara yang sama dan tidak mendapat apa-apa.\n\nTANGGAPAN DUKUNGAN / DIPUBLIKASIKAN OLEH DEXERTO · 21 FEBRUARI 2023\n“terkena serangan melalui permintaan bantuan, dan tim CS:GO bertanggung jawab atas hal tersebut”\nBaca laporan dan pesan yang disalin di bawah ini ↗ diarsipkan 2025-08-18 ↗\n01 / KATUP APA YANG DIGUNAKAN\nSaluran dukungannya sendiri itulah jalan masuknya\n\nJawaban tersebut mencakup akun yang diretas dan pembatalan transaksi-transaksinya. Valve telah membatalkan transaksi-transaksi tersebut — sehingga transaksi-transaksi tersebut dapat dibatalkan. Tiket otentikasi asli tidak terdapat dalam koleksi ini.\n\n02 / HAL-HAL YANG TIDAK TERATASI OLEH PEMECATAN TERSEBUT\nPintu yang sama itu terbuka kembali pada November 2025\n\nPihak kontraktor memberhentikan seluruh staf dukungan Steam — seperti dilaporkan oleh Mzkshow melalui Dexerto, bukan berdasarkan pernyataan resmi dari pihak Valve. Tiga puluh tiga bulan kemudian, Steam Support menulis kepada penagih lain bahwa \"seorang teknisi dukungan yang menangani permintaan bantuan tersebut gagal mengikuti proses kami, yang mengakibatkan akun Anda dipulihkan ke orang lain.\" Kalimat dari Valve sendiri, mengenai saluran yang sama.\n\nPendaftaran kedua, 14 November 2025 ↗\n03 / APA ITU OPEN\nValve belum pernah menyebutkan nama kontraktor tersebut\n\nBaik kontraktor maupun lokasinya tidak disebutkan dalam sumber-sumber tersebut. Hal itu bukanlah kelemahan dalam pelaporan — melainkan informasi yang belum diungkapkan oleh Valve mengenai siapa saja yang memiliki akses ke akun pengguna.\n\nLaporan terkini mengenai kasus tersebut ↗\n\nTiga pertanyaan yang belum dijawab oleh Valve: siapa yang dapat mengabaikan proses pemulihan akun, apa yang ditemukan dalam audit akses, dan apa yang berubah setelahnya.\n\nTuduhan-tuduhan selanjutnya dalam arsip dukungan yang disimpan\n\nDua postingan Reddit tahun 2024 mengungkap penyelidikan lebih lanjut terkait Mzkshow — sebuah kasus pencabutan larangan VAC pada Juli 2024 dan kasus inventaris $13,000 pada Desember 2024. Kedua insiden ini dilaporkan secara terpisah. Pertanyaan mengenai pertanggungjawaban dalam masing-masing kasus tersebut identik: siapa yang memiliki akses override, apa yang ditemukan dalam audit, dan apa yang berubah.\n\n14 Juli 2024 · dilaporkan sembuh / VAC-kasus pemblokiran ↗2 Desember 2024 · dilaporkan $13,000 kasus persediaan ↗diarsipkan 2025-08-05 ↗Dua tiang yang masih utuh, baris sumber, dan pola ukiran ↓\n\n05 / IKUTI JEJAK KERUGIAN\n\nSetiap jumlahPerlu sebuah kotak.\n\nSepuluh kasus, Juni 2022 hingga Maret 2026. Setiap angka merupakan angka yang dipublikasikan oleh sumber yang disebutkan — $6,300,000, $2,000,000+, $1,000,000+, ≈$320,000, ≈$300,000, dan turun menjadi €288. Valve menyimpan log transaksi, catatan sesi, dan jejak audit dukungan untuk masing-masing transaksi, namun belum menghasilkan satupun dari data tersebut.\n\nSALURAN DUKUNGAN21 2022 JUNI\n$2,000,000+\nHFB — the largest inventory in the game\n\nPENILAIAN STOK YANG DILAPORKAN · NAIK MENJADI LEBIH DARI $3JUTA DALAM LAPORAN TINDAK LANJUT FEBRUARI 2023\n\nTujuh Souvenir Dragon Lores dan Karambit Permata Biru #1; pisau itu sendiri berharga sekitar $1.26m. Akun tidak aktif selama tiga tahun dengan fitur otentikasi masih aktif; email dan kata sandi diubah melalui jalur pemulihan dukungan. Valve membatalkan transaksi tersebut — dan mencatat tanggung jawabnya secara tertulis. Sebelum pembatalan, dilaporkan bahwa $200,000+ dari hasil penjualan telah ditarik melalui market.csgo.com, yang memproses pembayaran dalam bentuk uang tunai dan kripto. Pembatalan mengembalikan skin, bukan uang yang sudah ditarik oleh seseorang. Pembatalan tersebut juga menimbulkan masalah: seorang pembeli menyembunyikan Souvenir Dragon Lore-nya di Unit Penyimpanan dalam game, skrip tidak dapat melihat isi wadah tersebut, dan Valve menggandakan item senilai $130,000 saat membatalkan pencurian — terdeteksi melalui ID item dan laporan komunitas, dihapus pada bulan Juli 2022, pembeli dikembalikan dananya oleh BUFF, bukan Valve.\n\nDexerto, hari terjadinya pencurian ↗\nDOMPET & PEMBELIAN07 2022 JULI\n>$500\n44 disputed Market purchases\n\nPENGELUARAN DARI DOMPET YANG DIKLAIM · USD\n\nSeorang pengguna melaporkan adanya pembelian tanpa izin atas item Dota 2 bernilai rendah serta tanggapan layanan pelanggan yang tidak memuaskan.\n\nBaca pengaduan & tangkapan layar yang terlampir ↗\nPELANGGARAN KEAMANAN PLATFORM14 2022 AGUSTUS\n$6,300,000\nCS.Money — 19,000+ skin dari bot\n\nPENILAIAN HARGA · PERKIRAAN AWAL $1.6M\n\nPara penyerang mengambil berkas otentikator seluler milik bot perdagangan di pasar tersebut dan mengosongkannya, lalu menyebarkan sebagian hasil curiannya ke para pedagang terkenal untuk mengaburkan jejak. Para peneliti komunitas berhasil memetakan 55 akun-akun penyerang dalam hitungan jam. Valve tidak melakukan pembalikan apa pun — situs pihak ketiga tersebut berada di luar Steam, demikian menurut Steam yang inventaris, perdagangan API, dan sistem akunnya menjadi sarana pencurian tersebut dari awal hingga akhir.\n\nBaca catatan sejarah masa itu ↗\nSALURAN DUKUNGANBERITA 21 FEB 2023\n$1,000,000+\nQkss — pintu yang sama, aktor yang sama, jawaban yang berlawanan\n\nPENILAIAN STOK YANG DILAPORKAN\n\nDilihat dari cara kasus HFB ditangani—oleh aktor yang sama, melalui permintaan bantuan dukungan yang sama—kasus HFB telah diselesaikan sepenuhnya delapan bulan sebelumnya. Qkss tidak. Tidak ada hal dalam catatan yang dipublikasikan yang membedakan kedua kasus tersebut kecuali jumlah audiensnya.\n\nDexerto mengenai penyelidikan Mzkshow ↗\nSALURAN DUKUNGANDILAPORKAN PADA 2023\n≈ $320,000\nPraktik perdagangan orang dalam itu sendiri — selama satu tahun\n\nHASIL SELAMA SEKITAR SATU TAHUN · BUKAN PENILAIAN STOK\n\nAkses dari pihak dukungan berhasil mengakses riwayat akun hingga 15 tahun yang lalu: kunci CD pertama, email pertama, kartu pertama — persis bukti yang diminta dalam proses pemulihan. Siapa pun yang menguasai basis data selalu menang dalam perdebatan tersebut melawan siapa pun yang menguasai akun. Satu M4A4 Howl yang dicuri bersama iBUYPOWER dan Titan Katowice 2014 holos terjual seharga $35,000 dan akhirnya jatuh ke tangan b1t dari NAVI, yang tidak mungkin mengetahuinya. Tanggapan kontraktor adalah memecat setiap karyawan yang bekerja di dukungan Steam.\n\nBerita Escorenews mengenai penyelidikan yang sama ↗\nDOMPET & PEMBELIAN09 2023 Desember\n€288\nDompet hilang meskipun sudah dilengkapi perlindungan dua langkah\n\nTRUSTPILOT · INDEKS SUMBER 16\n\nPenilai melaporkan adanya akun yang diretas dan penolakan untuk membantu terkait pengeluaran di Market. Ekspor tersebut tidak memiliki URL ulasan tersendiri.\n\nPeriksa asal-usul sumber ↗\nPEMULIHAN AKUN02 2024 Desember\n$13,000\n“Matvey” — dua tahun setelah pemecatan-pemecatan tersebut\n\nPERKIRAAN STOK PENULIS\n\nPemulihan diberikan kepada seseorang yang memberikan data akun yang bahkan pemiliknya sendiri tidak dapat mencocokkan. Jalur yang sama, hasil yang sama, setelah kontraktor tersebut membubarkan tim dukungan Steam-nya.\n\nBaca tuduhan yang tercatat ↗\nPEMULIHAN AKUN09 2025 MEI\n≈ $10,000\nPemulihan melalui tiket orang lain\n\nKLAIM KEHILANGAN BARANG · USD\n\nSeorang pengguna dari Quebec menuduh tim dukungan telah mereset kata sandi dan menghapus fitur perlindungan akun atas permintaan orang lain.\n\nBaca pengaduan yang ditulis dalam sudut pandang orang pertama ↗\nSALURAN DUKUNGAN13 2025 NOVEMBER\n≈ $300,000\nHawkeye337 — dan pengakuan tertulis kedua dari Valve\n\nKOLEKSI HOLO LENGKAP KATOWICE 2014\n\nPelaku serangan menuntut bitcoin senilai 1 dan mulai memindahkan koleksi tersebut ke Negevs untuk menghancurkannya. Steam Tanggapan Tim Dukungan: “Seorang teknisi dukungan yang menangani permintaan bantuan tersebut gagal mengikuti prosedur kami, yang mengakibatkan akun Anda dipulihkan ke nama orang lain.” Tiga puluh tiga bulan setelah pengakuan pertama, masalah yang sama terulang. Akun dipulihkan dalam hitungan jam setelah utas tersebut menjadi trending di X. Qkss tidak memiliki audiens sebanyak itu.\n\nDexerto, 14 Nov 2025 ↗\nDOMPET & PEMBELIAN29 2026 Maret\n$50\nPengisian saldo tanpa izin dan game yang diberikan sebagai hadiah\n\nTRUSTPILOT · INDEKS SUMBER 290\n\nPenilai tersebut menuduh adanya pengeluaran yang tidak sah dan permintaan pengembalian dana yang tidak berhasil. URL ulasan individu tersebut tidak tercantum dalam file ekspor.\n\nPeriksa asal-usul sumber ↗\n\nSumber dan jumlahnya tetap sebagaimana dilaporkan oleh masing-masing sumber. Valve menyimpan log transaksi, catatan sesi, dan jejak audit dukungan untuk setiap kasus ini. Tunjukkan bukti-bukti tersebut. Sebuah postingan Reddit yang masih tersimpan tidak cukup untuk menjawab pertanyaan ini — catatan milik Valve-lah yang menjadi bukti.\n\nKOLEKSI / SETELAH DIPERIKSA\n\n231,829 akun sedang dijual.Valve menyimpan log untuk masing-masing.\n354 → 201\nCatatan Trustpilot\n\n153 baris duplikat telah dihapus. URL ulasan individual tidak disertakan dalam file ekspor.\n\n231,829\nSteam daftar akun\n\n33,509 diklasifikasikan sebagai kendaraan yang didaftarkan secara otomatis; 198,320 tercantum di bawah label “pencuri” milik kolektor. Iklan-iklan tersebut bukanlah penjualan yang telah selesai.\n\nAudit koleksi ↓Cari di arsip sumber ↗",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Akun Anda.Akses mereka.Siapa yang menjawab?"
          },
          {
            "level": 2,
            "id": null,
            "text": "Otomatisasi telahjejak dokumen."
          },
          {
            "level": 3,
            "id": null,
            "text": "ArchiSteamFarm"
          },
          {
            "level": 2,
            "id": null,
            "text": "Tombol manaApa yang sedang kita bicarakan?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Kunci API Web Pribadi"
          },
          {
            "level": 3,
            "id": null,
            "text": "Kunci API Web Penerbit"
          },
          {
            "level": 3,
            "id": null,
            "text": "OpenID / token sesi"
          },
          {
            "level": 3,
            "id": null,
            "text": "Otomatisasi dapat menggunakan lebih dari satu kunci API."
          },
          {
            "level": 2,
            "id": null,
            "text": "Masih bermain.Sudah terungkap."
          },
          {
            "level": 3,
            "id": "session-hidden-title",
            "text": "Kepercayaan itu sudah terbentuk sebelum situs web tersebut ada."
          },
          {
            "level": 2,
            "id": null,
            "text": "Barang tersebut mungkin langka.Batas tersebut tetap berlaku."
          },
          {
            "level": 2,
            "id": null,
            "text": "Dipercayakan untuk mengelola data.Bertanggung jawab atas akses."
          },
          {
            "level": 3,
            "id": null,
            "text": "Timbangan itu terbuka untuk umum"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve menyerahkan tugas tersebut kepada pihak luar — dan mengakuinya"
          },
          {
            "level": 3,
            "id": null,
            "text": "Penerimaan pertama"
          },
          {
            "level": 3,
            "id": null,
            "text": "Penerimaan kedua"
          },
          {
            "level": 3,
            "id": null,
            "text": "Jalan masuknya adalah Steam Dukungan itu sendiri.Valve telah menyatakan hal itu secara tertulis."
          },
          {
            "level": 4,
            "id": null,
            "text": "Saluran dukungannya sendiri itulah jalan masuknya"
          },
          {
            "level": 4,
            "id": null,
            "text": "Pintu yang sama itu terbuka kembali pada November 2025"
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve belum pernah menyebutkan nama kontraktor tersebut"
          },
          {
            "level": 2,
            "id": null,
            "text": "Setiap jumlahPerlu sebuah kotak."
          },
          {
            "level": 3,
            "id": null,
            "text": "HFB — the largest inventory in the game"
          },
          {
            "level": 3,
            "id": null,
            "text": "44 disputed Market purchases"
          },
          {
            "level": 3,
            "id": null,
            "text": "CS.Money — 19,000+ skin dari bot"
          },
          {
            "level": 3,
            "id": null,
            "text": "Qkss — pintu yang sama, aktor yang sama, jawaban yang berlawanan"
          },
          {
            "level": 3,
            "id": null,
            "text": "Praktik perdagangan orang dalam itu sendiri — selama satu tahun"
          },
          {
            "level": 3,
            "id": null,
            "text": "Dompet hilang meskipun sudah dilengkapi perlindungan dua langkah"
          },
          {
            "level": 3,
            "id": null,
            "text": "“Matvey” — dua tahun setelah pemecatan-pemecatan tersebut"
          },
          {
            "level": 3,
            "id": null,
            "text": "Pemulihan melalui tiket orang lain"
          },
          {
            "level": 3,
            "id": null,
            "text": "Hawkeye337 — dan pengakuan tertulis kedua dari Valve"
          },
          {
            "level": 3,
            "id": null,
            "text": "Pengisian saldo tanpa izin dan game yang diberikan sebagai hadiah"
          },
          {
            "level": 2,
            "id": null,
            "text": "231,829 akun sedang dijual.Valve menyimpan log untuk masing-masing."
          },
          {
            "level": 3,
            "id": null,
            "text": "Catatan Trustpilot"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam daftar akun"
          }
        ],
        "links": [
          "https://phishdestroy.io/live-intel/?category=steam",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/lzt.market.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-evidence-lzt.json",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://github.com/JustArchiNET/ArchiSteamFarm/blob/main/ArchiSteamFarm/ArchiSteamFarm.csproj",
          "https://github.com/JustArchi",
          "https://github.com/renovate[bot]",
          "https://github.com/JustArchi-ArchiBot",
          "https://github.com/dependabot-preview[bot]",
          "https://github.com/renovate-bot",
          "https://github.com/actions-user",
          "https://github.com/dependabot-support",
          "https://github.com/Abrynos",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/automation-map.json",
          "https://phishdestroy.io/steam_dossier/id/output_steam_network/network.html",
          "https://phishdestroy.io/steam_dossier/id/output_steam_network/raw_data.json",
          "https://partner.steamgames.com/doc/webapi_overview/auth",
          "http://web.archive.org/web/20260915025812/https://partner.steamgames.com/doc/webapi_overview/auth",
          "https://partner.steamgames.com/doc/webapi/ISteamUserAuth",
          "http://web.archive.org/web/20260829124950/https://partner.steamgames.com/doc/webapi/ISteamUserAuth",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "http://web.archive.org/web/20260924181824/https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://store.steampowered.com/privacy_agreement/",
          "https://store.steampowered.com/oldnews/19618",
          "http://web.archive.org/web/20260809125516/https://store.steampowered.com/oldnews/19618",
          "https://kotaku.com/valve-explains-why-steam-customer-service-is-still-terr-1736988223",
          "http://web.archive.org/web/20250711004653/https://kotaku.com/valve-explains-why-steam-customer-service-is-still-terr-1736988223",
          "https://www.dexerto.com/counter-strike-2/valve-saves-hacked-cs2-player-threatened-with-ransom-over-300000-of-rare-stickers-3283135/",
          "https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "http://web.archive.org/web/20250818113925/https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "https://lis-skins.com/ru/blog/krupneisaia-mosenniceskaia-sxema-v-istorii-steam/",
          "https://www.reddit.com/r/cs2/comments/1e38jo4/stealing_accounts_and_removing_vac_bans_a_new/",
          "https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "http://web.archive.org/web/20250805141942/https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/outsourcing-archive-records.json",
          "https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "https://escorenews.com/en/csgo/news/44087-valve-steam-support-employee-accused-of-selling-inactive-accounts-inventories-worth-six-figures-b1t-has-one-of-these-skins",
          "https://phishdestroy.io/steam_dossier/id/PART2_RESEARCH.md",
          "https://www.reddit.com/r/GlobalOffensive/comments/1h56shi/steam_support_is_stealing_accounts/",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/design-review/part2/quality-review.json",
          "https://phishdestroy.io/steam_dossier/id/steam_evidence_archive.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/id/investigation_part2.content.json",
      "export_json_sha256": "b7d2ed816cc2f993a66c89440a45401116619e60a4e7c90bb4cbcee4f4d74805"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "id/legal_analysis.html",
      "language": "id",
      "title": "Ketentuan mereka, hak Anda — Laporan “Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/id/legal_analysis",
      "source_html_sha256": "771448de82391311f337234eaf9e46604ff5f8813b1e91ccd508721ba04b3093",
      "exported_at": "2026-09-29T00:22:29.205Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "legal_analysis.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/id/legal_analysis.pdf?v=print-20260929-v5",
        "sha256": "efda905a7ef166dfad3e2c32127369dea062136b2d0cf69e6863798b760218b2",
        "bytes": 103588,
        "pages": 8
      },
      "integrity": {
        "signed_object": "legal_analysis.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "legal_analysis.content.json.asc",
        "digest_file": "legal_analysis.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify legal_analysis.content.json.asc legal_analysis.content.json",
          "sha256sum -c legal_analysis.content.json.sha256"
        ]
      },
      "content": {
        "text": "Laporan Hukum dan Ekonomi\nAnalisis Hukum — Ketentuan Layanan & Kepatuhan terhadap Peraturan\n\nKetentuan mereka. Hak-hak Anda.\n\nAPA YANG DIBUKTIKAN OLEH BAGIAN INI\n\nAudit hukum forensik ini mengevaluasi ketidakseimbangan kontrak antara Valve Corporation dan pengguna Steam di berbagai yurisdiksi regulasi utama. Audit ini mengidentifikasi bagaimana lisensi berlangganan yang dapat dicabut menghilangkan hak kepemilikan konsumen yang diatur undang-undang, menganalisis yurisprudensi Mahkamah Eropa mengenai habisnya hak jual kembali digital, serta menelaah kepatuhan terhadap Undang-Undang Layanan Digital (DSA) dan Pasal 15. dari Undang-Undang Hak Cipta Eropa (GDPR). Analisis ini menunjukkan bagaimana mekanisme penegakan otomatis beroperasi tanpa adanya mekanisme banding yang berarti, sementara biaya pasar platform secara sistematis mengekstraksi nilai ekonomi dari setiap transaksi antar pengguna.\n\n← Kembali ke Ringkasan Eksekutif\n\nLaporan ini menyajikan analisis hukum, ekonomi, dan teknis mengenai kesenjangan antara aturan platform yang diumumkan oleh Steam dan posisi konsumen: penegakan aturan secara otomatis dengan sedikit jalan hukum, serta kontrol korporasi yang luas atas aset digital. Angka-angka yang disajikan disertai sumbernya; jika suatu angka tidak dapat dilacak ke sumber primer, angka tersebut dihilangkan.\n\nVektor 1\n\nMengganti \"hak kepemilikan\" dengan lisensi yang dapat dicabut, sehingga aset digital dapat ditarik kembali sesuai dengan perjanjian tersebut.\n\nVektor 2\n\nPenegakan otomatis (VACNet) yang, menurut pernyataan di Steam, tidak dapat membatalkan sanksi yang dijatuhkan.\n\nVektor 3\n\nPengendalian akun dan aset yang dipadukan dengan biaya pasar CS2 dari 15% (biaya 5%, Steam, dan 10%) yang mengurangi nilai ekosistem pada setiap transaksi penjualan kembali.\n\nKetidakseimbangan istilah\nPernyataan pelepasan tanggung jawab dan lisensi yang dapat dicabut\n2.1 Model \"langganan\" versus hak milik\n\nPasal 2 dalam Perjanjian Pelanggan Steam hanya memberikan hak kepada pengguna berupa lisensi pribadi, non-eksklusif, tidak dapat dialihkan, dan dapat dicabut. Berdasarkan perjanjian tersebut, Valve berhak menghentikan akun kapan saja, dan saldo Dompet Steam yang tidak terpakai dapat hangus.\n\n2.2 Ilusi pengembalian dana versus Petunjuk Hak Konsumen Uni Eropa\nKerangka hukum\tMekanisme pengembalian dana\tBatasan\nEU Consumer Rights Directive\tUnconditional 14-day right of withdrawal on digital content\tWaived if download begins with explicit consumer consent\nSteam SSA\t14 days / under 2 hours played\tValve may deny at its discretion for \"abuse\"\nPenilaian\n\nValve UE mensyaratkan hak penarikan diri yang diatur undang-undang selama \"14-\" hari dengan batasan waktu \"14 hari / 2 jam\", yang harus disetujui pada saat mengunduh sebelum produk dapat dievaluasi. Kebijakan tersebut mempersempit — bukan memperluas — hak yang diatur undang-undang; apakah hal itu dilakukan secara sah merupakan pertanyaan yang harus dijawab oleh otoritas yang berwenang, bukan kesimpulan yang dinyatakan di sini.\n\nSengketa Hukum\nPasar Sekunder dan Antimonopoli\nUFC Que Choisir melawan Valve — Prancis\n2019\nPengadilan Paris: doktrin habisnya hak berlaku untuk game digital — penjualan kembali dianggap sah\n2022 Oktober\nPengadilan Banding Paris membatalkan putusan tersebut\n23 2024 Oktober\nCour de cassation (Mahkamah Agung): video game merupakan “karya kompleks” berdasarkan Direktif InfoSoc, bukan perangkat lunak. Penjualan kembali digital dilarang. Valve tetap yang teratas.\nKasus Antitrust Wolfire Games — Amerika Serikat (Dalam perkara Litigasi Antitrust “Valve”, No. 2:21-cv-00563)\n\nKlausul Most-Favored-Nation (PMFN) dari Valve melarang pengembang menjual kunci Steam dengan harga lebih murah di platform lain mana pun. Toko-toko pesaing — bahkan yang mengenakan komisi 12% dibandingkan dengan 30% dari Valve — tidak dapat meneruskan penghematan tersebut kepada konsumen.\n\n336Jumlah karyawan Valve (2021). Sumber: dokumen pengungkapan yang telah dibuka.\n79karyawan yang mengelola seluruh platform Steam. Sumber: dokumen pengungkapan yang telah dibuka.\n$3.5Mlaba bersih per karyawan. Sumber: dokumen pengungkapan yang telah dibuka.\n\nCatatan pengungkapan yang tidak disegel menunjukkan $8.5miliar pendapatan kotor di 2021 terkait karyawan 336. Hal ini 79-orangSteamtim menangani 373,000+ tiket dukungan harian dengan mengalihkannya ke pusat panggilan otomatis yang dikelola pihak ketiga.\n\nBUKTI PERKARA YANG SUDAH DIBUKA · W.D. WASH. PERKARA 2:21-CV-00563Memo Penelusuran Internal\n\nTim Sweeney (CEO, Epic Games) kepada Gabe Newell: \"Mengapa Steam masih mengambil 30% dari pendapatan kotor, padahal biaya pemrosesan pembayaran sebesar 2–5% dan biaya CDN bandwidth sebesar $0.002/GB? Jika Anda mengesampingkan game-game teratas 25 di Steam, saya yakin Valve meraup keuntungan lebih besar dari sebagian besar game berikutnya 1,000 daripada yang diperoleh pengembangnya sendiri.\"\n\nSurat edaran internal dari Scott Lynch (COO, Valve Corporation) kepada Gabe Newell: \"Kamu marah, bro?\"\n\nBantahan atas Keterangan Sumpah (Bloomberg, 2026): Berdasarkan Pasal 30 (b) (1) mengenai pemeriksaan saksi, Gabe Newell memberikan kesaksian bahwa \"Valvetidak memiliki kebijakan atau praktik yang mengatur harga bagi pengembang perangkat lunak pihak ketiga di platform lain.\" Para penggugat menghadapkan Newell dengan memo internal Valve yang membuktikan adanya pengawasan harga secara aktif serta ancaman penghapusan produk dari daftar penjualan terhadap pengembang yang menetapkan harga lebih rendah di toko-toko pesaing. Pada akhir Maret 2026,, Pengadilan Federal menolak permohonan putusan singkat dari Valve, sehingga gugatan kelompok pengembang 32,000-dilanjutkan ke persidangan juri.\n2024 November\n\nGugatan kelompok telah disahkan untuk ~ Pengembang32,000 yang telah membayar komisi sejak Januari 2017, serta gugatan class action konsumen yang diajukan secara paralel.\n\nGanti rugi yang dituntut\n\n$3.1B\nTiga kali lipat berdasarkan undang-undang antimonopoli AS = $9.3B risiko paparan.\n\n2026: Juni Sebuah gugatan baru menuduh bahwa Microsoft dan Valve terlibat dalam perjanjian kartel yang menghambat persaingan dalam distribusi game PC.\n\nPengakuan Resmi atas Kejahatan Keuangan & Pencegahan Pencucian Uang\nValve Pengakuan Resmi: Likuidasi Akibat Penipuan di Seluruh Dunia (28 Oktober 2019)\n\nPada 28 Oktober 2019, Valve secara resmi menghentikan perdagangan dan penjualan kembali di pasar online untuk kunci kontainer Counter-Strike yang baru dibeli. Dalam pengumuman resminya kepada publik (blog.counter-strike.net/2019/10/26113), PerusahaanValve mengakui secara tertulis bahwa ekonomi virtual yang dirancangnya telah berubah menjadi pusat pencucian uang berskala internasional:\n\n\"Dulu, sebagian besar transaksi kunci yang kami amati terjadi antara pelanggan yang sah. Namun, belakangan ini jaringan penipuan global telah beralih menggunakan kunci CS:GO untuk mencairkan hasil kejahatan mereka. Saat ini, hampir semua pembelian kunci yang akhirnya diperdagangkan atau dijual di pasar diperkirakan berasal dari aktivitas penipuan.\"\n\nKonteks Regulasi: Pengakuan ini muncul setelah Komisi Perjudian Negara Bagian Washington (WSGC) mengeluarkan ultimatum resmi kepada Valve serta perintah “Cease & Desist” (2016) pada bulan Juli yang dikeluarkan oleh Penasihat Hukum Umum Valve, Karl Quackenbush, kepada domain perjudian skin 23 (termasuk CSGO Lotto, CSGOLounge, dan OPSkins), setelah penyelidikan pidana terkait perjudian mengancam kelangsungan operasi platform tersebut.\n\nYurisdiksi\nPemegang hak di Rusia, yang tidak dapat dihubungi oleh pengguna\n\nPerjanjian Pelanggan menggambarkan Valve sebagai pihak yang tidak memiliki banyak kewajiban dan tidak dapat dihubungi oleh siapa pun: pemblokiran bersifat permanen, permohonan banding ditolak, dan akses dicabut dari seluruh wilayah hanya dengan satu kalimat mengenai “wilayah yang dikenai sanksi.” Berbeda dengan sikap tersebut, inilah yang dilakukan Valve ketika kepentingan komersialnya sendiri yang dipertaruhkan di yurisdiksi yang biasanya dianggapnya sulit.\n\nValve v. Touch Skins — gugatan hak kekayaan intelektual pra-persidangan, Rusia\n1 2026 September\nValve., melalui firma hukum Rusia Melling, Voitishkin & Rekan, mengirimkan surat peringatan prapersidangan kepada para pengelola Tema Sentuh, sebuah perangkat pengganti skin CS2 berukuran besar, yang dikirim melalui Pos Rusia dan email.\nAlasan\nTiga kelompok dugaan pelanggaran: hak eksklusif atas perangkat lunak; hak atas tampilan skin senjata, pisau, dan sarung tangan; serta merek dagang Valve. Perilaku para operator tersebut dinilai sebagai tindakan yang disengaja dan berlangsung dalam jangka waktu yang lama.\nPermintaan\nSegera hentikan operasi dan hapus seluruh infrastruktur — perangkat lunak tersebut kode sumber, situs web, dan halaman media sosial — dan jika hal tersebut tidak dipenuhi, Valve berhak untuk mengajukan gugatan ke pengadilan Rusia atas kompensasi finansial yang signifikan dan untuk meneruskan masalah tersebut kepada penegakan hukum untuk penilaian tindak pidana.\nHasil\nSetelah menerima surat tersebut, platform tersebut mengumumkan bahwa mereka akan menghentikan operasinya. Hal ini dilaporkan sebagai langkah pertama yang diambil oleh Valve dalam menggunakan alat hukum terhadap pengembang skin-changer di Rusia.\n\nDilaporkan oleh penelusur data Maxim \"GabeFollower\" Poletaev (X, ~11 Sep 2026) dan media game Rusia. Ini merupakan gugatan pra-persidangan, bukan gugatan yang telah diajukan; belum ada nomor perkara yang dipublikasikan. Disajikan di sini sesuai laporan, bukan sebagai catatan pengadilan. Sumber: dota2.ru diarsipkan 2026-09-24 ↗ · Shazoo.\n\nYurisdiksi yang sama, arah yang berlawanan\n\nValve tidak asing dengan sistem hukum dan peraturan Rusia. Hal itu sesuai dengan ketentuan Roskomnadzor: atas permintaan regulator, pihak tersebut telah menghapus halaman komunitas 260+ Steam yang memuat materi terlarang, dan Roskomnadzor telah secara terbuka menyatakan bahwa Steam memenuhi persyaratan undang-undang. Undang-undang \"landing\" Rusia (Undang-Undang Federal 236-FZ, yang mulai berlaku pada 2022) mewajibkan platform internet asing berskala besar yang melayani pengguna Rusia untuk mendirikan kantor perwakilan lokal dan akun penghubung dengan Roskomnadzor. Valve tidak hanya menaati perintah penghapusan dari regulator tersebut, tetapi kini juga memanfaatkan penasihat hukum Rusia serta ancaman tindakan hukum di pengadilan Rusia untuk melindungi skin-nya sebagai kekayaan intelektual.\n\nJadi, platform ini mudah diakses, mumpuni, dan tegas dalam memperjuangkan hak-haknya, terutama terkait pendapatan. Hal ini kontras dengan nasib pengguna: seorang pelanggan yang membayar di wilayah yang dikenai sanksi diberitahu bahwa hubungan tersebut telah berakhir, akses ke komunitas diblokir hingga 2038, tiket tersebut ditutup, dan tidak ada forum di mana keputusan tersebut dapat dipertanyakan — \"Mereka dengan senang hati menerima uang saya dan memproses transaksi saya\", pengembalian dana dari akun yang sama yang berasal dari alamat IP Iran yang sama telah disetujui setahun sebelumnya (r/pcgaming, 4 8 Agustus 2026; lebih banyak surat teguran di pameran ekonomi kartu). Valve memanfaatkan seluruh mekanisme sistem hukum nasional untuk membela sebuah skin; hal ini sama sekali tidak memberikan proses hukum apa pun kepada pengguna yang telah membeli skin tersebut.\n\nValve memperlakukan yurisdiksi tersebut sebagai yurisdiksi di mana perusahaan dapat bertindak dan mematuhi aturan di dalamnya, setiap kali kepentingan yang dipertaruhkan adalah kepentingValve — penasihat hukum Rusia, ancaman dari pengadilan Rusia, perintah penghapusan dari Roskomnadzor yang dipatuhi — sementara memperlakukan kewajibannya terhadap pengguna di pasar tersebut, dan di setiap pasar lainnya, seolah-olah berada di luar jangkauan proses hukum apa pun. Perusahaan ini bertindak sebagai pemegang hak ketika menyangkut pendapatannya, namun menjadi pihak yang tak dapat dijangkau ketika hak pengguna yang dipertaruhkan.\n\nSumber: TASS (RKN: Sesuai dengan Steam) · Undang-Undang Federal Nomor 236-FZ.\n\nOportunisme hukum\nPenyerahan Diri Terkait Klausul Arbitrase\n2023 — serangan itu\n\nBeberapa firma hukum (Zaiger LLC, Mason LLP) merekrut ribuan pengguna melalui media sosial dan mengajukan puluhan ribu gugatan arbitrase perorangan secara bersamaan.\n\nKeterlibatan Valve\n\n$225M+\ndalam bentuk biaya pengajuan arbitrase yang tidak dapat dikembalikan, sebelum kasus tersebut disidangkan berdasarkan substansi perkara. Dihitung berdasarkan Aturan Arbitrase Konsumen Asosiasi Arbitrase Amerika (AAA) dan Lampiran Tambahan Arbitrase Massal. Para penggugat yang diwakili oleh Zaiger LLC dan Mason LLP mengajukan ~75,000 permohonan arbitrase individu terhadap Valve Corp. (sejalan dengan gugatan antimonopoli dalam Wolfire Games LLC dkk. melawan Valve Corp., Nomor Perkara2:21-cv-00563-JCC, W.D. (Wash.). Berdasarkan daftar tarif konsumen AAA, pihak tergugat dari kalangan bisnis wajib membayar biaya administrasi perkara yang tidak dapat dikembalikan serta uang jaminan penunjukan arbiter sebesar ~$3,000+ per kasus individu (75,000 berkas × $3,000 = ~$225M sebagai kewajiban prosedural di muka). Lihat laporan hukum Bloomberg Law dan Reuters mengenai risiko arbitrase massal di sektor teknologi (2023–2024).\n\nPeriode\tMekanisme penyelesaian sengketa SSA\tEfek yang diamati\tHasil\nBefore Sep 2024\tMandatory individual arbitration + class-action waiver\tIndividual litigation becomes economically irrational for users\tMass arbitration → $225M fee threat\nAfter Sep 2024\tDisputes in King County, WA courts only\tArbitration costs are avoided; cases consolidate in a single forum\tClass actions now possible\nKesimpulan\n\nSelama lebih dari sepuluh tahun, SSA mewajibkan pengguna untuk melepaskan hak mereka atas persidangan dengan juri dan memilih arbitrase individu. Setelah pengajuan arbitrase massal membuat mekanisme tersebut menjadi sangat mahal secara finansial bagi Valve, undang-undang SSA diubah agar sengketa dialihkan ke pengadilan Kabupaten King. Perubahan tersebut diberlakukan tanpa opsi penolakan yang berarti; alternatif dari penerimaan adalah kehilangan akses ke aset digital yang telah dibeli dengan cara menghapus akun.\n\nPenegakan hukum berbasis algoritma\nVACNet, Asumsi Bersalah, dan Hasil Positif Palsu\n2023 Oktober — AMD Anti-Lag+\n\nPembaruan driver AMD (v23.10.1) mengaktifkan Anti-Lag+ di CS2, yang menyadap fungsi DLL dalam game. VAC mengklasifikasikan hal ini sebagai penyisipan kode curang dan menjatuhkan sanksi larangan permanen kepada ribuan pengguna yang sah sebelum Valve turun tangan.\n\n2023 Desember — DPI tinggi\n\nPemain dengan DPI di atas 10,000 yang memutar kamera dengan sangat cepat dijatuhi sanksi larangan bermain permanen. VACNet tidak dapat membedakan gerakan mouse fisik dari kecurangan \"spinbot\".\n\nKategori dukungan\tWaktu respons yang diklaim\tHasil yang sebenarnya\nRefund requests\t50 min – 1.5 hr\tAutomatic approval (<14 days, <2 hours played)\nAccount security / recovery\t3–12 hours\tDepends on documentation provided\nContesting a VAC ban\tForm response\tComplete refusal. Support cannot reverse VAC decisions. The ban is permanent.\nKebijakan resmi Valve\n\n\"Pemblokiran VAC bersifat permanen, tidak dapat dinegosiasikan, dan tidak dapat dicabut oleh Tim DukungSteam.\"\n\nSaluran dukungan yang sama yang memberlakukan pemblokiran tersebut juga menyampaikan penolakan permohonan peninjauan kembali: Steam Pihak dukungan menyatakan bahwa mereka tidak dapat membatalkan keputusan VAC. Bagi pengguna, putusan algoritma itulah yang menjadi hasil yang berlaku.\n\nAspek ekonomi penjualan kembali\nPengendalian atas aset virtual dan biaya penjualan kembali\nBiaya pasar \"15%\" CS2 — nilai dikurangi pada setiap penjualan kembali\nIterasi\tSaldo pembeli\tPenjual menerima\tTerbakar (15%)\n1\t$100.00\t$85.00\t$15.00\n2\t$85.00\t$72.25\t$12.75\n3\t$72.25\t$61.41\t$10.84\n10\t$23.16\t$19.68\t~$3.47\nTotal\t$100 → dust\tValve collects the 15% fee on each resale. Users must add new money to keep trading.\nPerubahan aturan penukaran CS2 — Oktober 2025\n\nTanpa pemberitahuan sebelumnya, Valve mengubah aturan kontrak penukaran CS2 agar memungkinkan perolehan pisau dan sarung tangan langka secara pasti dengan menukarkannya menggunakan item kualitas Covert. Harga pisau pun turun, harga item Covert melonjak tajam, dan hal ini memicu aksi jual panik di seluruh pasar.\n\nPerlindungan yang dinyatakan oleh Valve adalah Pasal 7 dari SSA — tidak ada tanggung jawab atas perubahan aturan platform. Pengguna menanggung risiko dalam perekonomian yang aturannya Valve dapat berubah tanpa pemberitahuan atau kompensasi. Besarnya kerugian yang dilaporkan di seluruh pasar masih diperdebatkan dan tidak disebutkan di sini tanpa sumber utama.\n\nTanggapan pihak regulator Eropa\nUOKiK, DSA, dan Undang-Undang Keadilan Digital\nUOKiK — Polandia, Mei 2024\n\nOtoritas antimonopoli Polandia (UOKiK) telah meluncurkan proses hukum antimonopoli resmi terhadap PerusahaValve, serta lima penerbit/distributor game dalam negeri terkait dugaan penetapan harga, klausul kesetaraan harga yang membatasi, dan praktik pemblokiran geografis yang menyebabkan konsumen Polandia harus membayar hingga 20% lebih mahal untuk game digital dibandingkan pasar-pasar tetangga di Kawasan Ekonomi Eropa (EEA). Sebagai bagian dari penyelidikan antimonopoli tersebut, inspektur UOKiK dan kepolisian melakukan penggeledahan dini hari serta pemeriksaan barang bukti di kantor-kantor mitra penerbit dan distributor dalam negeri di Polandia (bukan di kantor-kantor anak perusahaValve, karena Valve tidak memiliki entitas di Polandia). Denda hukum yang mungkin dikenakan: hingga 10% dari omset tahunan. Sumber: Pengumuman resmi UOKiK, \"Ketua UOKiK telah memulai proses hukum terhadap Valve dan para pengembang game\", 2024 Mei.\n\nUndang-Undang Layanan Digital (DSA)\n\nDiperlukan transparansi dalam proses moderasi otomatis. Steam tidak mempublikasikan data false-positive/false-negative untuk VACNet, dan saluran dukungannya menyatakan bahwa keputusan VAC tidak dapat dibatalkan.\n\nUndang-Undang Keadilan Digital — 2026\n\nKetentuan yang diharapkan: akses berkelanjutan terhadap konten berbayar, larangan penggunaan “dark patterns” pada saat pelepasan hak, pengakuan hak kepemilikan atas aset digital, serta perlindungan dari penyitaan permanen atas inventaris.\n\nKesimpulan\nPerbedaan yang tercatat antara aturan dan catatan\n1\n\nKesenjangan kepemilikan. Pengguna membayar harga penuh untuk lisensi yang berdasarkan perjanjian tersebut dapat dicabut oleh Valve. Mahkamah Agung Prancis (2024 Oktober) memutuskan bahwa penjualan kembali secara digital tidak dilindungi, sehingga menetapkan posisi tersebut dalam undang-undang.\n\n2\n\nPenegakan hukum berbasis algoritma. VACNet telah mengeluarkan larangan yang tidak berdasar (driver AMD, insiden DPI tinggi). Steam Tim Dukungan menyatakan bahwa mereka tidak dapat membatalkan keputusan VAC, sehingga algoritma tersebutlah yang menjadi keputusan akhir yang mengikat.\n\n3\n\nPenghematan biaya. Biaya pasar CS2 dari 15% (5% Steam + 10% biaya penerbit) mengurangi nilai pada setiap penjualan kembali, dan aturan platform dapat berubah tanpa pemberitahuan; tanggung jawab Valve atas perubahan tersebut dikecualikan berdasarkan SSA.\n\n4\n\nKlausul arbitrase telah dihapus. SSA menghapus ketentuan arbitrase wajib pada bulan September 2024, setelah adanya pengajuan gugatan massal yang membuat Valve terancam dikenakan biaya sebesar ~$225juta. Para pengguna tidak diberi pilihan yang berarti untuk menolak perubahan tersebut.\n\n5\n\nYurisdiksi selektif. Valve menunjuk firma hukum Rusia (Melling, Voitishkin & Partners) dan mengancam akan mengajukan gugatan ke pengadilan Rusia terhadap Touch Skins, sementara pada saat yang sama menganggap kewajibannya terhadap pengguna di pasar yang sama tersebut berada di luar proses peradilan apa pun. Valve bertindak sebagai pemegang hak ketika kepentingan komersialnya terlibat, dan sebagai pihak yang tak dapat dihubungi ketika hak-hak pengguna yang dipertaruhkan.\n\n← Bagian I: Mengelabui proxy & perjudianBagian II: Akses & akuntabilitas →\n\nSumber hukum dan catatan perkara dikutip berdasarkan penerbit dan repositori aslinya. Tidak ada klaim kepemilikan atas dokumen-dokumen yang menjadi dasarnya.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Analisis Hukum — Ketentuan Layanan & Kepatuhan terhadap Peraturan"
          },
          {
            "level": 2,
            "id": null,
            "text": "Pernyataan pelepasan tanggung jawab dan lisensi yang dapat dicabut"
          },
          {
            "level": 3,
            "id": null,
            "text": "2.1 Model \"langganan\" versus hak milik"
          },
          {
            "level": 3,
            "id": null,
            "text": "2.2 Ilusi pengembalian dana versus Petunjuk Hak Konsumen Uni Eropa"
          },
          {
            "level": 2,
            "id": null,
            "text": "Pasar Sekunder dan Antimonopoli"
          },
          {
            "level": 3,
            "id": null,
            "text": "UFC Que Choisir melawan Valve — Prancis"
          },
          {
            "level": 3,
            "id": null,
            "text": "Kasus Antitrust Wolfire Games — Amerika Serikat (Dalam perkara Litigasi Antitrust “Valve”, No. 2:21-cv-00563)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve Pengakuan Resmi: Likuidasi Akibat Penipuan di Seluruh Dunia (28 Oktober 2019)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Pemegang hak di Rusia, yang tidak dapat dihubungi oleh pengguna"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve v. Touch Skins — gugatan hak kekayaan intelektual pra-persidangan, Rusia"
          },
          {
            "level": 3,
            "id": null,
            "text": "Yurisdiksi yang sama, arah yang berlawanan"
          },
          {
            "level": 2,
            "id": null,
            "text": "Penyerahan Diri Terkait Klausul Arbitrase"
          },
          {
            "level": 2,
            "id": null,
            "text": "VACNet, Asumsi Bersalah, dan Hasil Positif Palsu"
          },
          {
            "level": 2,
            "id": null,
            "text": "Pengendalian atas aset virtual dan biaya penjualan kembali"
          },
          {
            "level": 3,
            "id": null,
            "text": "Biaya pasar \"15%\" CS2 — nilai dikurangi pada setiap penjualan kembali"
          },
          {
            "level": 3,
            "id": null,
            "text": "Perubahan aturan penukaran CS2 — Oktober 2025"
          },
          {
            "level": 2,
            "id": null,
            "text": "UOKiK, DSA, dan Undang-Undang Keadilan Digital"
          },
          {
            "level": 2,
            "id": null,
            "text": "Perbedaan yang tercatat antara aturan dan catatan"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/id/#briefing-heading",
          "https://dota2.ru/news/67707-valve-cerez-uristov-napravila-krupnoj-rossijskoj-skincendzer-platforme-trebovanie-o-prekrasenii-deatelnosti/",
          "http://web.archive.org/web/20260924181657/https://dota2.ru/news/67707-valve-cerez-uristov-napravila-krupnoj-rossijskoj-skincendzer-platforme-trebovanie-o-prekrasenii-deatelnosti/",
          "https://shazoo.ru/2026/09/12/190508/valve-cerez-rossiiskix-iuristov-dobilas-zakrytiia-krupnogo-skinceindzera-dlia-cs2",
          "https://www.reddit.com/r/pcgaming/comments/1vf24lu/warning_to_all_gamersexpats_steam_took_my_money/",
          "https://phishdestroy.io/steam_dossier/id/card_economy.html#asymmetry",
          "https://tass.ru/obschestvo/23235387",
          "https://base.garant.ru/401414628/",
          "https://uokik.gov.pl/postepowanie-wyjasniajace-w-sprawie-valve-i-dystrybutorow-gier",
          "https://phishdestroy.io/steam_dossier/id/",
          "https://phishdestroy.io/steam_dossier/id/investigation_part2.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/id/legal_analysis.content.json",
      "export_json_sha256": "c3e7f5b0245ba21ced0fec35a31326820be7285cfadffbbc73252cf9f14ceedd"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "id/license_disclaimer.html",
      "language": "id",
      "title": "Lisensi · Hak · Penafian — PhishDestroy",
      "source_url": "https://phishdestroy.io/steam_dossier/id/license_disclaimer",
      "source_html_sha256": "ebc7cb50638106a4b0c77380832a971a26dc51d5b4b2bd6ee47ead0f3976050b",
      "exported_at": "2026-09-29T00:22:30.003Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "license_disclaimer.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/id/license_disclaimer.pdf?v=print-20260929-v5",
        "sha256": "8880c001cf865e1bc3bde75c8594d7920121ea5f2a6fadcaaf8411b9b8123b84",
        "bytes": 119555,
        "pages": 11
      },
      "integrity": {
        "signed_object": "license_disclaimer.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "license_disclaimer.content.json.asc",
        "digest_file": "license_disclaimer.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify license_disclaimer.content.json.asc license_disclaimer.content.json",
          "sha256sum -c license_disclaimer.content.json.sha256"
        ]
      },
      "content": {
        "text": "PHISHDESTROYPenyelidikan forensik · Valve / Steam\nLisensi · Hak · Penafian\nLisensi & Pernyataan Penafian Hukum — Penyerahan ke Domain Publik\n\nSemua hak menyerahkan diri kepada umat manusia.\n\nAPA YANG DIBUKTIKAN OLEH BAGIAN INI\n\nDokumen ini menetapkan penyerahan tanpa syarat ke ranah publik (CC0 1.0 Universal) serta ketentuan lisensi perangkat lunak MIT yang mengatur PhishDestroy Steam Dossier. Seluruh temuan forensik, kumpulan data bukti, diagram jaringan, dan metodologi analitis ditempatkan secara tidak dapat ditarik kembali ke dalam ranah publik untuk penggunaan tanpa batasan dalam bidang regulasi, hukum, dan akademis di seluruh dunia.\n\n← Kembali ke Ringkasan Eksekutif\n\nPhishDestroy melepaskan semua hak atas materi ini — baik untuk menggandakannya, menjualnya, maupun mencantumkan nama Anda di dalamnya. Berikut ini adalah dua dokumen yang disajikan dalam satu gaya penulisan: sebuah surat terbuka kepada Valve, yang ditulis sebagaimana cara kami biasanya menulis, dan sebuah surat pelepasan hak resmi yang disusun untuk pihak berwenang yang akan melanjutkan penanganan materi ini.\n\nPenyelidikan · PerusahaanValve / SteamEdisi umum — tidak ada batas waktu, tidak dapat dibatalkan\nDIBEBASKAN\nBagian ILisensi — bagian hukumnya yang sebenarnya, tapi dari sisi kemanusiaan\n\nPhishDestroy melepaskan semua hak atas materi ini. Nol. Hilang. Selesai. Kamu boleh menggandakannya, menjualnya, mencantumkan namamu di sana, menato bosmu dengan gambar ini, apa pun. Tak perlu mencantumkan nama, tak perlu mengirim pesan langsung, tak perlu mengirim kartu ucapan terima kasih.\n\nSatu aturan yang sebenarnya (ya, hanya satu)\n\nKAMU TIDAK berhak memutuskan apakah kamu seorang teroris.\n\nJika Anda adalah pengguna dari Rusia atau negara mana pun yang dikenai sanksi OFAC — materi ini BUKAN untuk Anda. Tidak ada celah. Nikmati saja sanksi Anda.\n\nDan jika kamu mengubah wilayah \"Steam\" menjadi Turki saat berada di Moskow — selamat atas kreativitasmu dalam hal geografi. Kamu tetap warga Rusia. Sanksi tersebut tetap berlaku. Itulah intinya.\n\nBagian IIApa itu dan mengapa hal ini ada\n\nKami akan mempublikasikan lebih banyak informasi tentang Valve daripada yang diketahui oleh karyawan biasa Valve tentang diri mereka sendiri. Itu bukan sekadar membanggakan diri. Itu hanya hasil yang akhirnya kami capai.\n\nBagaimana kita bisa sampai di sini? Ceritanya lucu: Steam pada dasarnya yang membentuk kita. Situs itu membesarkan kita dengan para penipu, tiket dukungan, dan ekosistem pengelakan pemblokiran—dan kini inilah kita. Tak ada dendam. Sebenarnya, ini terasa puitis.\n\nBagi yang belum membaca kisah asal-usulnya — kita sudah pernah mengenal para pengacara Eropa milik Valve yang sangat mahal (Taylor Wessing, kalau Anda penasaran):\n\nhttps://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d diarsipkan 2026-08-21 ↗\n\nPertemuan yang menyenangkan. Apalagi mengingat tarif per jam mereka.\n\nApakah Valve mengetahuinya? Ya. Apakah Taylor Wessing mengetahuinya? Hampir pasti ya. Tapi kalau sudah sekaya itu, hukum lebih dianggap sebagai semacam suasana daripada kewajiban, kan?\n\nSebenarnya, itulah intinya.\n\nSteam Telah bertahun-tahun kami mengungkap para penipu. Tidak selalu disengaja — terkadang para penipu itu hanya tercemar oleh jejak “Valve” karena keterkaitan mereka. Kami tidak bermaksud melebih-lebihkan masalah ini. Kami hanya berusaha untuk akurat. Sejujurnya, hal itu lebih sulit bagi kami daripada melebih-lebihkan — begitulah cara kami menulis.\n\nApakah ini sebuah konflik?\n— Tidak.\n\nApakah masalah ini bisa diselesaikan?\n— Ya. Tapi kami tidak akan menandatangani perjanjian kerahasiaan (NDA) apa pun, dan kami juga tidak akan ikut program hadiah bug demi uang receh.\n\nKami menunggu lebih dari 4 tahun hingga mereka memperbaiki masalah spoofing tersebut sebelum kami bisa menulis tentang hal itu secara terbuka. Sebab, seandainya kami menulis tentang hal itu lebih awal, Steam pasti akan berpura-pura menjadi korban dan berteriak, “ancaman aktif!”, lalu menawarkan uang receh kepada kami agar menandatangani dokumen yang akan menjadikan kami milik mereka secara hukum selamanya. Tidak, terima kasih.\n\n(Selain itu: Valve sendiri melanggar perjanjian kerahasiaan (NDA). Karyawan mereka sendiri yang melakukannya. Para petinggi di sana. Tapi ya sudah, mari kita bahas soal kita saja.)\n\nBagian IIISurat terbuka untuk Valve — Serius deh, baca ini\n\nValve: jika Anda ingin domain ini diturunkan, kirimkan email kepada kami. Tidak diperlukan penasihat hukum eksternal untuk pembicaraan tersebut.\n\nBagi yang belum tahu: Dr. Patrick meraih gelar Magister Hukum dalam bidang Hukum Perdagangan Internasional dari Universitas Aberdeen dan — tunggu dulu — benar-benar menyelesaikan disertasi doktoralnya di bidang hukum teknologi informasi. Baru-baru ini ia diangkat menjadi mitra di Taylor Wessing, sebuah firma yang seluruh model bisnisnya adalah menagih perusahaan-perusahaan seperti Valve jumlah uang yang sangat besar untuk memperpanjang proses hukum hingga pihak lawan kehabisan uang atau kesabaran.\n\nKami tidak menyalahkannya. Klien kaya yang merasa bersalah dan membayar per jam — langkah karier yang cerdas. Kami hanya merasa Anda tidak seharusnya membiayainya.\n\nKesepakatan tersebut (penawaran terbuka, tidak perlu pengacara)\n\nDomain tersebut adalah satu-satunya hal yang secara realistis dapat dicapai oleh Valve. Penyelidikan, rujukan, dan sumber daya terkait sudah berjalan — semuanya akan terus berlanjut, baik dengan maupun tanpa domain tersebut.\n\nJika Anda ingin domain tersebut:\n\nBiarkan para ahli hukum TI Anda yang menentukan harga yang wajar.\n\n50% diserahkan kepada YayasanSEAL.\n\nKami akan menghapus domain tersebut. Tanpa keributan. Tanpa proses pengadilan. Selesai.\n\nIni bukan ancaman. Ini adalah tawaran yang lugas untuk satu-satunya hal yang benar-benar bisa diraih. Kamu tidak akan mendapatkannya dengan cara lain — begitulah memang dinamika situasinya.\n\nApakah kita akan \"merugikan\" Valve secara langsung? Mungkin tidak dalam arti yang akan mereka rasakan secara finansial. Kita tidak sedang berhalusinasi. Namun, kita akan melakukannya dengan jujur, terbuka, tanpa mengejar ketenaran — karena kita tidak membutuhkan ketenaran. Kita ingin dunia melihat apa yang sebenarnya selalu terlihat secara terbuka jika Anda meluangkan cukup waktu untuk mengamatinya.\n\nKami memiliki arsip selam5. Apa yang ditunjukkan oleh pengacara Valve dalam proses pengungkapan bukti — data yang dapat dilihat oleh petugas penegak hukum, jejak digital, serta dokumen-dokumen yang secara harfiah mereka serahkan kepada kami — sudah cukup. Kami tidak perlu membocorkannya dalam bentuk mentah.\n\nSiapa yang mendapat apa\n\nPihak regulator menerima salinan aslinya.\n\nPara peneliti dan jurnalis menerima versi yang telah disunting (laporan korban, data login anak-anak, serta komentar dukungan yang menarik dari Valve telah dihapus karena alasan yang jelas).\n\nDi antara akun-akun yang terkena dampak terdapat akun milik anak di bawah umur, dan mereka tidak diberi tahu. Temuan tersebut tercantum dalam paket laporan regulator setelah laporan korban dan data identitas dihapus, karena hal ini seharusnya diajukan kepada otoritas perlindungan data, bukan dimuat dalam sebuah artikel.\n\nSelain itu, Valve — kami ingin menjelaskan sesuatu sebelum Anda memutuskan cara menangani hal ini: PhishDestroy adalah sebuah komunitas, bukan seorang individu. Anda sudah mengetahui hal itu ketika Anda mengirimkan surat resmi kepada komunitas tanpa repot-repot berbicara dengan komunitas tersebut — Anda hanya memanfaatkannya untuk mengumpulkan data dan memblokir akun-akun tersebut.\n\nKomunitas ini tidak memiliki konflik dengan Valve. Kami tidak mencari masalah ini. Para penipu yang kalian biarkan berkembanglah yang menemukan kami. Kami telah memblokir mereka. Dan inilah kami sekarang.\n\nBagian III-BSumber daya sekutu — catatan khusus untuk Steam\n\nKami ingin terbuka mengenai struktur amplifikasi ini, karena berpura-pura seolah-olah hal itu tidak ada sama sekali adalah tindakan yang tidak jujur.\n\nPhishDestroy—sejauh yang kami pahami mengenai situasi di komunitas—memiliki setidaknya dua sumber daya mitra yang akan mengangkat materi ini dan mengembangkannya lebih lanjut.\n\nArtinya dalam praktiknya:\n\nMereka masing-masing mengangkat sudut pandang tersendiri terkait topik yang tumpang tindih.\n\nMereka bersifat independen — mereka tidak mengikuti arahan kami, dan kami pun tidak mengikuti arahan mereka. Topik umumnya sama, namun metodologinya berbeda.\n\nMereka TIDAK AKAN mengaktifkannya pada Bagian 1. Mereka sedang mengawasi.\n\nJika Valve memutuskan untuk tidak menghapus situs tersebut:\n\nDiharapkan mereka akan muncul setelah Bagian 2 atau Bagian 3.\n\nMereka akan mengambil bagian yang berguna dari karya kami, melengkapinya dengan karya mereka sendiri, dan menerbitkannya atas nama mereka sendiri.\n\nInilah tepatnya tujuan dari lisensi yang tercantum dalam Bagian 1: materi tersebut disebarkan ke tempat yang seharusnya, dilengkapi, dan diperluas — dan baik kami maupun mereka tidak saling berkewajiban untuk mencantumkan atribusi.\n\n(Catatan tambahan bagi para pengacara yang bertanya-tanya mengenai rantai pertanggungjawaban: tidak ada sama sekali. Sumber-sumber ini tidak menerima arahan, pendanaan, maupun data dari kami. Mereka membaca informasi yang tersedia untuk umum dan menarik kesimpulan sendiri. Sama seperti yang bisa Anda lakukan.)\n\nKami tidak mengatakan ini untuk menakut-nakuti. Kami mengatakannya agar siapa pun yang merumuskan strategi di pihak Valve memiliki informasi yang akurat mengenai seperti apa sebenarnya kondisi lingkungan informasi tersebut.\n\nSalah satu sumber yang mengutip materi kami dan melengkapinya adalah sebuah cerita. Dua sumber yang melakukannya secara independen dan mencapai kesimpulan serupa merupakan sebuah pola. Pola-pola inilah yang menjadi perhatian pihak regulator.\n\nBagian IVUang, larangan-larangan, dan seluruh keributan itu\n\nBegini masalahnya mengenai larangan yang diberlakukan oleh Steam terhadap situs perjudian dan penipu: ini bukan soal penegakan hukum. Ini soal pengumpulan pendapatan. Valve mengantongi uangnya, membersihkan tangannya, lalu naik ke panggung dan menceritakan kisah yang mulia kepada semua orang tentang kartu Pokémon dan bisbol.\n\nDi mana kasus-kasus kebocoran data di pihak dukungan telah didokumentasikan — termasuk pengakuan tertulis dari Valve pada bulan Februari 2023 yang menyatakan bertanggung jawab atas kebocoran data akun-akun bernilai tinggi melalui permintaan bantuan, serta pemecatan staf kontraktor yang dilaporkan oleh Dexerto dan Escorenews menyusul kasus perdagangan orang dalam senilai $320k (Bagian II §04 · Dokumen Utama §14.1) — hal ini didasarkan pada pengakuan yang telah dipublikasikan dan liputan investigatif. Isu-isu yang tidak berdasar mengenai staf pendukung yang menjalankan bisnis sampingan perjudian atau mengambil potongan untuk mencabut larangan tidak didukung oleh catatan publik dan tidak disertakan di sini.\n\nSementara itu, Valve menghapus fitur pelacakan skin yang memadai di 2017.. Mereka bahkan membahas hal ini di forum mereka sendiri. Mereka menyebutnya sebagai “langkah-langkah anti-perjudian” — padahal ekosistem perjudian skin terus mengalirkan miliaran melalui infrastruktur Steam selama bertahun-tahun setelahnya. Strategi pemasaran yang hebat.\n\nKita akan membuktikan bahwa:\n\nSkins lebih anonim daripada Monero\n\nSebuah kartel asal Peru diduga menggunakan skin Dota 2 untuk mentransfer uang\n\nSteam secara fungsional merupakan alat untuk menghindari sanksi senilai ~$7B dalam bentuk \"kartu koleksi\" (ya, mereka benar-benar menyebutnya \"kartu koleksi\" di hadapan jaksa penuntut)\n\nKami punya video tentang masalah skin itu. Nanti kamu akan melihatnya.\n\nKita juga tahu:\n\nModerasValve dipengaruhi oleh\n\nInfrastruktur data pihak ketiga di Steam (seperti steamid.uk) dikelola oleh seorang individu swasta (msart) yang memiliki proyek daftar larangan terkait (steambans.com arsip) dikelola bersama oleh seorang moderator komunitas Valve yang telah terverifikasi (killahinstinct_) — sehingga audit independen terhadap pemblokiran di platform sepenuhnya berada di bawah wewenang Valve (lihat Ekonomi Kartu §08)\n\nApa yang tidak bisa mereka kendalikan, mereka larang\n\nValve: kalau kamu terus berpura-pura tidak tahu — tidak apa-apa. Kami sudah mencatat tempat berlindungmu itu. Google Analytics memang menyamarkan alamat IP penggunamu. Kami tahu apa yang dihapus. Kami hanya belum bisa membuktikannya dengan biaya yang cukup murah agar pengacara-pengacara kamu peduli. Setidaknya untuk saat ini.\n\nBagian VSoal malware itu — ya, kami akan membahasnya\n\nMari kita bahas urutan kejadian ini dengan sangat jujur, karena hal itu justru memperlihatkan siapa dirimu sebenarnya.\n\nKami TIDAK akan mengungkap kerentanan dalam game ini secara terbuka. Kami TIDAK akan melaporkannya ke Steam. Program tersebut mensyaratkan perjanjian kerahasiaan (NDA), dan menandatanganinya akan menghalangi kami untuk memberi tahu pengguna yang terdampak mengenai apa yang terjadi pada akun mereka. Pengungkapan kepada orang-orang yang kehilangan akun tersebut, serta kepada pihak regulator, adalah tujuan dari pekerjaan ini; perjanjian kerahasiaan tidak sejalan dengan tujuan tersebut.\n\nInilah yang sebenarnya terjadi: Kerentanan ini pada dasarnya sudah menjadi rahasia umum di kalangan tertentu. Kami tahu pasti bahwa para peneliti keamanan independen telah secara langsung memperlihatkan eksploit lengkapnya tepat di hadapan Tim DukungSteam. Bagian itu sudah selesai. Kalian telah diberi peringatan resmi melalui saluran resmi kalian sendiri.\n\nLalu, apa yang dilakukValve? Sama sekali tidak ada. Sebab, bagi Valve, keamanan tidak sama dengan keuntungan — justru sebaliknya. Keamanan adalah sumber biaya. Selama ancaman belum mencapai titik kritis dan memicu krisis hubungan masyarakat yang parah, Valve tidak menganggapnya sebagai hal yang mendesak.\n\nLalu, apa yang sedang kita lakukan? Kita memberitahu masyarakat bahwa ancaman itu ada, karena pernyataan “Valve mengetahui adanya ancaman malware sistemik namun secara aktif memilih untuk tidak berbuat apa-apa” merupakan informasi penting bagi para regulator yang saat ini sedang membaca artikel ini.\n\nGame ini sangat besar. Kami tidak akan menyebut namanya di sini. Tapi perlu dipahami bahwa:\n\nIni BUKAN sampah skrip-kiddie CS:GO yang sepele, di mana server meminta Anda untuk \"menginstal driver\". Ini benar-benar bencana.\n\nIni adalah mimpi buruk sekelas Unturned: RCE tanpa klik saat terhubung ke server. Anda bergabung ke sebuah server. Anda tidak mengklik apa pun. Anda tidak mengunduh apa pun. Koneksi itu sendiri adalah titik serangan, dan perangkat Anda telah sepenuhnya disusupi. Mari kita hadapi kenyataannya: menyisipkan RCE dan melewati antivirus lokal dengan memanfaatkan sertifikat digital tepercaya dari Valve bukanlah hal baru lagi di Steam. Hal ini praktis sudah menjadi fitur bawaan dari ekosistem Anda.\n\nValve Sudah tahu bahwa hal ini ada. Namun, mereka mengandalkan celah hukum favorit mereka yang pengecut: karena secara teknis game ini dikembangkan oleh pihak ketiga, Valve mencuci tangan. Mereka mendistribusikan game, memproses pembayaran, dan menghosting infrastrukturnya, tetapi ketika serangan RCE tanpa klik mengancam jutaan penggunanya, sikap mereka adalah: \"Bukan game kami, bukan tanggung jawab kami.\"\n\nKetika masalah ini akhirnya meledak, pengembang pihak ketiga lah yang akan menanggung akibatnya, sementara Valve akan lolos begitu saja sambil berpura-pura menjadi platform yang bertanggung jawab yang telah \"membantu\" dalam penyelesaiannya. Sikap pengecut khas Valve. Kita sudah tahu trik-triknya.\n\nKami mencatat hal ini agar pihak regulator, jaksa penuntut, dan jurnalis memahami dengan tepat bagaimana Valve menangani malware aktif: dengan bersembunyi di balik pengembang pihak ketiga, memberlakukan perjanjian kerahasiaan (NDA) yang membungkam, dan membiarkan para pemain menjadi sasaran empuk.\n\nAkhir dari surat terbuka iniGaya bahasa formal dimulai\nGaya bahasa formal · untuk pihak berwenang\nPernyataanMengenai penggunaan dan hak-hak\n\nPhishDestroy Koalisi Proyek & Keamanan Siber\n\nPernyataan ini menyertai setiap berkas yang diajukan dan setiap bukti dalam paket rujukan ini. Pernyataan ini ditujukan kepada setiap pihak berwenang, pengadilan, badan pengawas, jaksa penuntut, peneliti, jurnalis, atau pihak yang terkena dampak yang menerima materi tersebut.\n\n1. Tidak ada syarat penggunaan\n\n1.1 Seluruh materi yang dihasilkan oleh Koalisi dalam pengajuan ini — pernyataan fakta, analisis, bukti-bukti yang disusunnya, perangkat pendukung, serta temuan-temuan — dipublikasikan TANPA MENYISAKAN HAK APA PUN.\n\n1.2 Siapa pun boleh, tanpa meminta izin dan tanpa memberi tahu kami:\n\nmenggandakannya, baik seluruhnya maupun sebagian;\n\nmenyesuaikan, mengedit, menulis ulang, menyusun ulang, atau mengoreksinya;\n\nterjemahkan;\n\nmengutip sebagian isinya tanpa menyebutkan bahwa itu merupakan kutipan;\n\nmemasukkannya ke dalam dokumen resmi, temuan, keputusan, berkas gugatan, laporan, atau materi pers;\n\nmenyajikannya sebagai karya atau temuan penerima sendiri;\n\nmenggunakannya sebagai bahan baku dan membuang sisanya;\n\ndan menyebarkannya kepada siapa pun dengan syarat yang sama.\n\n1.3 PENYEBUTAN SUMBER TIDAK DIWAJIBKAN DAN TIDAK DIBUTUHKAN. Koalisi tidak perlu disebutkan namanya, dikutip, diberi kredit, diberi ucapan terima kasih, dikonsultasikan, atau diberitahu. Jika materi dari rujukan ini membantu suatu otoritas dan Koalisi tidak pernah disebutkan, HAL ITU MERUPAKAN HASIL YANG SEPENUHNYA MEMUASKAN dan Koalisi menyatakan hal tersebut sejak awal agar pertanyaan tersebut tidak perlu diajukan.\n\n1.4 Sebaliknya, jika suatu pihak berwenang merasa lebih mudah untuk mengutip Koalisi sebagai sumber, pihak tersebut bebas melakukannya. Pilihan sepenuhnya ada di tangan penerima, dan kedua pilihan tersebut tidak menimbulkan konsekuensi apa pun.\n\n1.5 Ini adalah PERNYATAAN PEMBEBASAN, bukan penawaran lisensi. Pernyataan ini tidak memerlukan persetujuan, tidak menimbulkan kewajiban apa pun, dan tidak dapat dilanggar. Perangkat lunak yang diterbitkan oleh Koalisi dirilis secara terpisah di bawah lisensi MIT; penelitian dan temuan-temuan tersebut dirilis ke domain publik sejauh yang diizinkan, dan di yurisdiksi mana pun yang tidak mengizinkan pernyataan pelepasan tanggung jawab, Koalisi memberikan lisensi yang tidak dapat ditarik kembali, berlaku di seluruh dunia, dan bebas royalti dengan maksud yang sama.\n\n2. Mengapa hal ini penting secara praktis, dan bukan sekadar sebagai bentuk kesopanan\n\n2.1 Sebuah otoritas mungkin secara wajar ragu untuk mengandalkan bahan yang disediakan oleh pihak luar, karena khawatir terlihat bertindak atas permintaan pihak tersebut atau terjerat dalam hubungan yang rumit dengannya.\n\n2.2 TIDAK ADA APA PUN DI SINI YANG DAPAT MENYEBABKAN KEBINGUNGAN. Koalisi ini tidak meminta apa pun, tidak berhak atas apa pun, tidak menyimpan apa pun, dan tidak memiliki harapan apa pun. Koalisi ini tidak dapat kemudian menuntut hak, mengklaim penghargaan, mengeluhkan penyalahgunaan, atau keberatan terhadap cara materi tersebut digambarkan, karena koalisi ini tidak memiliki dasar apa pun untuk melakukannya.\n\n2.3 Oleh karena itu, pihak berwenang yang menggunakan materi ini tidak bertindak atas nama Koalisi. Pihak tersebut hanya memanfaatkan informasi publik yang kebetulan telah dikumpulkan oleh pihak lain.\n\n3. Semuanya sudah buka\n\n3.1 Hasil kerja Koalisi secara default bersifat terbuka untuk umum:\n\nhasil penyelidikan tersebut dipublikasikan secara terbuka di https://phishdestroy.io dan dapat dibaca secara bebas;\n\nPerangkat lunak tersebut dipublikasikan sebagai perangkat lunak sumber terbuka di bawah lisensi MIT di https://github.com/phishdestroy diarsipkan 2026-09-11 ↗;\n\nMetodologi tersebut dijelaskan dalam surat rujukan itu sendiri, pada Lampiran A Bagian A.16D, termasuk bobot dan batasan masing-masing jenis sumber;\n\nKoalisi ini tidak menerima sumbangan apa pun dan telah mengumumkan sikap tersebut sejak 2018.\n\n3.2 Satu-satunya materi yang TIDAK dipublikasikan adalah materi yang secara hukum atau keamanan tidak dapat dipublikasikan: data pribadi para korban dan pihak ketiga, serta informasi yang dapat membuat sumber informasi tersebut menjadi sasaran pembalasan. Materi tersebut diserahkan kepada pihak berwenang secara rahasia dan tercantum dalam daftar bukti.\n\n3.3 Koalisi ini mengundang pengawasan terhadap perilakunya sendiri dengan syarat yang sama seperti ketika mengundang pengawasan terhadap pihak lain, dan telah secara sukarela menyerahkan informasi mengenai pengelolaan datanya kepada pihak berwenang yang bersangkutan, termasuk mengajukan permohonan petunjuk mengenai pembuangan data tersebut.\n\n4. Keutuhan kumpulan bukti\n\n4.1 Bukti-bukti disertakan bersama pengajuan atau, jika disebutkan, dapat diminta melalui saluran yang aman. Bukti-bukti tersebut tidak dipublikasikan di alamat publik mana pun dan alamat semacam itu tidak boleh disimpulkan: materi semacam ini diserahkan langsung kepada pihak berwenang.\n\n4.2 Setiap pengiriman disertai dengan berkas SHA256SUMS yang mencantumkan ringkasan SHA-256 untuk setiap berkas yang disertakan, beserta tanda tangan terpisah OpenPGP di SHA256SUMS.asc.\n\n4.3 Kunci penandatanganan dipublikasikan di https://phishdestroy.io/.well-known/pgp-key.txt dan di keys.openpgp.org. Jejaknya terlihat pada kop surat setiap kiriman dalam kumpulan ini.\n\n4.4 Setiap penerima dapat memverifikasi kapan saja bahwa berkas yang dimilikinya adalah berkas yang dikirimkan, tanpa ada perubahan:\n\ngpg --verify SHA256SUMS.asc SHA256SUMS\n\nsha256sum -c SHA256SUMS\n\n4.5 Tujuannya bukanlah sekadar formalitas. Hal ini dilakukan agar, jika kelak keakuratan atau keaslian suatu bukti dipertanyakan, masalah tersebut dapat diselesaikan melalui perhitungan, bukan melalui perdebatan.\n\n5. Dalam konteks ini — mengapa pengecualian tersebut bersifat fungsional dan bukan sekadar bentuk kemurahan hati\n\n5.1 Pihak berwenang mungkin akan menemui hasil investigasi yang dipublikasikan oleh Koalisi dan menganggapnya kasar, kontroversial, dan terkadang bernada satir. Kesan tersebut memang benar. Koalisi memang sengaja menulis dengan gaya seperti itu dan tidak meminta maaf atas hal tersebut.\n\n5.2 LAPORAN INI JUGA MENYADARI BAHWA INI BUKAN GAYA PENULISAN YANG TEPAT UNTUK PROSES REGULASI ATAU PERADILAN. Masalah serius tidak seharusnya disampaikan dengan nada kampanye. Temuan yang diajukan kepada otoritas harus dinyatakan secara tegas, dengan mengakui keterbatasannya, dan tidak boleh mengharuskan pembaca untuk mengabaikan nada penyampaiannya sebelum memahami substansinya.\n\n5.3 ITULAH ALASAN UTAMA MENGAPA KOALISI MENYATAKAN MENYERAHKAN HAK KEPENULISAN. Pernyataan penyerahan hak tersebut pada bagian 1 merupakan mekanisme yang memungkinkan substansi teks dipisahkan dari daftar: pihak berwenang dapat mengambil bagian yang berguna, menyampaikannya kembali dengan gaya bahasanya sendiri, dan menghilangkan setiap kata yang mencerminkan gaya penulisan Koalisi beserta nama Koalisi itu sendiri. Tidak ada yang hilang dengan melakukan hal tersebut, dan Koalisi justru lebih memilih hal itu.\n\n5.4 KOALISI INI JUGA MEMINTA AGAR DAFTAR TERSEBUT TIDAK DISALAHARTIKAN SEBAGAI METODE. Nada yang ditampilkan memang agresif; namun praktik yang mendasarinya tidak sembarangan. Sepanjang laporan ini, kesimpulan dipisahkan dari pengamatan, kesaksian diidentifikasi sebagai kesaksian, sumber-sumber dinilai dan kelemahannya disebutkan, angka-angka disajikan beserta keterbatasannya, dan poin-poin yang tidak dapat dibuktikan oleh Koalisi disajikan sebagai pertanyaan kepada pihak berwenang, bukan sebagai pernyataan. Apabila bukti bertentangan dengan posisi Koalisi sendiri, hal itu telah dinyatakan — lihat Lampiran A, paragraf 7, dan bagian B.0 dari rujukan paralel tersebut.\n\n5.5 KOALISI INI MENJELASKAN HUBUNGAN ANTARA CARA KERJA DAN KEUANGANNYA KARENA KEDUA HAL TERSEBUT TIDAK DAPAT DIPISAHKAN. Koalisi ini tidak menerima uang dari siapa pun — tidak ada sumbangan, tidak ada imbalan, tidak ada klien, dan tidak ada sponsor. Penolakan itulah yang memungkinkan sikap blak-blakan ini: sebuah organisasi yang memiliki pendapatan yang harus dilindungi harus menahan diri dalam menyampaikan pendapatnya mengenai pihak-pihak yang menjadi sumber ketergantungannya. Karena tidak memiliki apa pun yang harus dilindungi, Koalisi ini tidak perlu menahan diri.\n\nItulah juga alasan mengapa Koalisi ini tetap ada. Tidak ada pendorong lain. Pekerjaan itu dilakukan karena memang harus dilakukan; pekerjaan itu berhenti ketika orang-orang yang melakukannya berhenti.\n\n5.6 Pihak berwenang tidak perlu menerima semua ini. Hal ini disampaikan agar nada dari pekerjaan publik Koalisi tersebut tidak ditafsirkan sebagai ukuran seberapa teliti mereka menangani materi yang kini sedang dibahas.\n\n6. Apa yang disediakan oleh Koalisi, menurut penjelasannya sendiri\n\nInformasi, penelitian, dan pengamatan.\n\nTidak ada pernyataan yang dikemukakan sebagai temuan yang tidak memiliki dasar hukum bagi Koalisi untuk menyampaikannya. Apabila ada hal yang disimpulkan, laporan rujukan tersebut mencantumkannya. Apabila ada hal yang didasarkan pada kesaksian, laporan rujukan tersebut menyebutkan dari siapa kesaksian tersebut dan dengan batasan apa. Apabila Koalisi tidak dapat menjawab suatu pertanyaan, hal itu juga disebutkan, serta disebutkan siapa yang dapat menjawabnya.\n\nKoalisi ini tidak menuntut ganti rugi, pembayaran, pengakuan, maupun hasil apa pun bagi dirinya sendiri maupun bagi individu mana pun. Koalisi ini hanya meminta agar pertanyaan-pertanyaan yang tercantum dalam rujukan tersebut diajukan kepada KorporasiValve oleh suatu badan yang berwenang untuk memaksa pemberian jawaban.\n\nCatatan penutupKepada siapa pun yang melanjutkan hal ini\n\nKami ingin mengucapkan terima kasih kepada siapa pun yang akan mengantarkan materi ini ke tempat yang seharusnya. Perjalanan ini kemungkinan besar tidak akan singkat. Valve memiliki dana yang melimpah, sementara Taylor Wessing mengenakan tarif per jam — kombinasi tersebut memang dirancang khusus untuk membuat orang-orang seperti Anda menyerah sebelum mencapai garis finis.\n\nKami tahu apa yang kami lakukan. Kami tahu tentang siapa yang kami tulis. Valve-lah yang membentuk kami — bagaimana mungkin kami tidak memahami mereka?\n\nPhishDestroy tidak ada konflik dengan Valve. Kami telah memblokir satu-satunya jaringan penipu berskala sebesar itu yang pernah kami temui — kami tidak bermaksud mencari masalah dengan Valve. Ternyata saja, setiap jejak mengarah kembali ke mereka. Bukan konflik. Hanya soal topologi.\n\nValve Tidak bisa menyelesaikan masalah PhishDestroy karena memang tidak ada yang perlu diselesaikan. Kami tidak memiliki hubungan apa pun dengan mereka. Data mengenai skema pengayaan mereka dan keuntungan berlebih sebagian besar sudah terbuka untuk umum — Anda hanya perlu meluangkan waktu yang cukup untuk melihatnya. Anggap saja ini sebagai ensiklopedia kesuksesan: “Cara Mengabaikan Sanksi Agar Peretas Rusia Tidak Bisa Membajak Game Gratis Kami (Yang Berbayar Itu Lagipula Tidak Akan Mereka Bajak).” Anda pasti mengerti maksudnya.\n\nKami tidak memerlukan atribusi.\n\nKami tidak memerlukan penyebutan sumber.\n\nKami tidak perlu menang.\n\nKita membutuhkan seseorang yang memiliki kewenangan nyata untuk mengajukan pertanyaan-pertanyaan yang sudah tercantum dalam rujukan ini kepada Valve, serta berwenang untuk menuntut jawaban.\n\nItu saja. Itulah permintaan selengkapnya.\n\nKasus-kasus tersebut akan disimpan di:\n\nhttps://steamdestroy.eth/\n\nhttps://steamdestroy.eth.limo (saat ini tidak berfungsi — akan diperbaiki jika diperlukan)\n\nKami akan hadir di:\n\nhttps://phishdestroy.eth.limo/ diarsipkan 2026-06-27 ↗\n\nhttps://phishdestroy.eth/\n\nDua benda yang ditandatangani · hak cipta dan teks yang diterbitkan\nSurat pernyataan pelepasan yang telah ditandatanganiApa saja yang tercantum dalam perjanjian tersebut, dan apa saja yang dicakup di dalamnya\n\nTeks pemberian hak dan teks penelitian merupakan objek JSON yang ditandatangani secara terpisah seperti yang tercantum di bawah ini. Setiap tanda tangan terpisah OpenPGP memverifikasi keaslian byte-byte tepat dari objek JSON yang disebutkan di sebelahnya. Pernyataan hak memberikan izin; cuplikan teks mengidentifikasi dan memuat materi yang dipublikasikan.\n\n1. Pernyataan hak — license-rights.json\n\nObjek yang telah ditandatangani: seluruh license-rights.json berkas yang berisi pemberian hak publik tertanggal 28 September 2026.. Pemberian hak ini memberikan izin untuk menyalin, menerbitkan, mengedit, menerjemahkan, menggabungkan, dan mengomersialkan materi berkas yang telah dibuat tanpa perlu mencantumkan sumber, pemberitahuan, atau persetujuan. Tanda tangan ini mengesahkan pernyataan hak tersebut; tanda tangan ini tidak mengesahkan teks dari setiap halaman web atau berkas PDF.\n\nIzin tertulis asli yang telah ditandatangani tetap berlaku tanpa perubahan. Izin yang telah diberikan tidak dapat dicabut atau dibatasi dengan mengubah situs web, menerbitkan berkas lain, atau menonaktifkan situs tersebut. Materi dari pihak ketiga tetap memiliki haknya masing-masing.\n\nPernyataan hak JSON ↗ · Tanda tangan license-rights.json ↗ · SHA-256 dari license-rights.json ↗\n\ngpg --verify license-rights.json.asc license-rights.json\nsha256sum -c license-rights.json.sha256\n2. Teks yang telah diterbitkan — dossier-text.json\n\nObjek yang telah ditandatangani: seluruh dossier-text.json berkas. Berkas tersebut berisi teks yang sebenarnya dan dapat dibaca dari halaman-halaman yang diekspor dalam documents[].content.text, beserta judul setiap halaman, bahasa, URL sumber, hash HTML sumber, judul-judul, dan referensi. Halaman tersebut documents Daftar ini berisi inventaris lengkap yang tercakup dalam cuplikan ini; varian bahasa dicantumkan secara terpisah. Ini adalah publikasi teks, bukan sekadar daftar hash.\n\nSetiap entri mengidentifikasi file PDF halaman ringannya berdasarkan nama file dan nilai SHA-256nya di documents[].pdf. Berkas JSON tersebut juga mengidentifikasi pernyataan hak cipta asli berdasarkan URL dan SHA-256,, sehingga teks yang diterbitkan, berkas PDF-nya, dan pernyataan pelepasan hak cipta yang berlaku dapat dipadankan tanpa perlu menebak-nebak. Basis data eksternal yang tertaut, gambar asli, dan halaman yang tidak tercantum dalam inventaris tidak disertakan dalam cuplikan teks ini.\n\nTeks JSON lengkap yang telah ditandatangani ↗ · Tanda tangan dossier-text.json ↗ · SHA-256asi dari dossier-text.json ↗\n\ngpg --verify dossier-text.json.asc dossier-text.json\nsha256sum -c dossier-text.json.sha256\n\nDi halaman beranda dokumen, tombol PDF dan JSON berfungsi untuk mengekspor paket penelitian. Di halaman dalam, tombol-tombol tersebut mengekspor halaman tersebut dalam bahasa yang digunakan saat dipublikasikan. Setiap berkas JSON halaman juga memiliki tanda tangan terpisah dan berkas SHA-256, yang dinamai secara eksplisit dalam integrity objek. Untuk memverifikasi PDF yang terkait, hitung nilai SHA-256-nya dan bandingkan dengan pdf.sha256 nilai dalam JSON yang telah diverifikasi. Berkas PDF tersebut terikat pada digest tersebut; berkas tersebut tidak dilengkapi dengan tanda tangan digital dalam format PDF.\n\n3. Paket penelitian yang dapat dicetak — steam-dossier-{language}.content.json\n\nObjek yang telah ditandatangani: berkas JSON lengkap yang spesifik untuk bahasa tersebut, termasuk teks bab yang disertakan di dalam documents[].content.text, rentang halaman bab, bahasa sumber, daftar sumber yang dikecualikan, dan ringkasan PDF yang tepat dalam pdf.sha256. Kelima arsip bukti tambahan tersebut tetap tertaut secara daring dan tidak digabungkan. Teks penelitian yang ditulis oleh penulis tetap dipertahankan; katalog visual diganti dengan tautan ke sumbernya.\n\nBahasa Inggris JSON ↗ · Tanda tangan terpisah dari \"OpenPGP\" ↗ · Ringkasan SHA-256 ↗\n\nBahasa Jerman JSON ↗ · Tanda tangan terpisah dari \"OpenPGP\" ↗ · Ringkasan SHA-256 ↗\n\ngpg --verify steam-dossier-en.content.json.asc steam-dossier-en.content.json\nsha256sum -c steam-dossier-en.content.json.sha256\n\nKunci verifikasi publik ↗\n\nJejak jari penandatanganan: 129F C7F3 9C40 C69D 2EF3 C329 BFCF 9E8D D295 EE01\n\ngpg --import pgp-key.txt\ngpg --fingerprint 129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01\n\nPastikan sidik jari yang ditampilkan sesuai dengan yang tertera di atas, lalu verifikasi tanda tangan tersebut berdasarkan nama file JSON yang tepat. Mengedit file JSON yang telah ditandatangani akan mengubah objek yang ditandatangani dan membatalkan keabsahan tanda tangan aslinya. Tanda tangan yang sah berfungsi untuk mengidentifikasi byte yang dipublikasikan; hal ini bukanlah verifikasi independen terhadap temuan penelitian.\n\nPhishDestroy — penyelidikan publik — semua hak diserahkan kepada umat manusia\n\nAkses ke wilayah OFAC: dilarang",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Lisensi & Pernyataan Penafian Hukum — Penyerahan ke Domain Publik"
          },
          {
            "level": 2,
            "id": null,
            "text": "Bagian ILisensi — bagian hukumnya yang sebenarnya, tapi dari sisi kemanusiaan"
          },
          {
            "level": 3,
            "id": null,
            "text": "Satu aturan yang sebenarnya (ya, hanya satu)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Bagian IIApa itu dan mengapa hal ini ada"
          },
          {
            "level": 2,
            "id": null,
            "text": "Bagian IIISurat terbuka untuk Valve — Serius deh, baca ini"
          },
          {
            "level": 3,
            "id": null,
            "text": "Kesepakatan tersebut (penawaran terbuka, tidak perlu pengacara)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Bagian III-BSumber daya sekutu — catatan khusus untuk Steam"
          },
          {
            "level": 2,
            "id": null,
            "text": "Bagian IVUang, larangan-larangan, dan seluruh keributan itu"
          },
          {
            "level": 2,
            "id": null,
            "text": "Bagian VSoal malware itu — ya, kami akan membahasnya"
          },
          {
            "level": 2,
            "id": null,
            "text": "PernyataanMengenai penggunaan dan hak-hak"
          },
          {
            "level": 3,
            "id": null,
            "text": "1. Tidak ada syarat penggunaan"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. Mengapa hal ini penting secara praktis, dan bukan sekadar sebagai bentuk kesopanan"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. Semuanya sudah buka"
          },
          {
            "level": 3,
            "id": null,
            "text": "4. Keutuhan kumpulan bukti"
          },
          {
            "level": 3,
            "id": null,
            "text": "5. Dalam konteks ini — mengapa pengecualian tersebut bersifat fungsional dan bukan sekadar bentuk kemurahan hati"
          },
          {
            "level": 3,
            "id": null,
            "text": "6. Apa yang disediakan oleh Koalisi, menurut penjelasannya sendiri"
          },
          {
            "level": 2,
            "id": null,
            "text": "Catatan penutupKepada siapa pun yang melanjutkan hal ini"
          },
          {
            "level": 2,
            "id": null,
            "text": "Surat pernyataan pelepasan yang telah ditandatanganiApa saja yang tercantum dalam perjanjian tersebut, dan apa saja yang dicakup di dalamnya"
          },
          {
            "level": 3,
            "id": null,
            "text": "1. Pernyataan hak — license-rights.json"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. Teks yang telah diterbitkan — dossier-text.json"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. Paket penelitian yang dapat dicetak — steam-dossier-{language}.content.json"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/id/#briefing-heading",
          "https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "http://web.archive.org/web/20260821155801/https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "https://phishdestroy.io/steam_dossier/id/investigation_part2.html#outsourcing-case",
          "https://phishdestroy.io/steam_dossier/id/#theft-ledger",
          "https://steamid.uk/",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/groups/steambans",
          "https://steamcommunity.com/id/killahinstinct_",
          "https://phishdestroy.io/steam_dossier/id/card_economy.html#governance",
          "https://phishdestroy.io/steam_dossier/id/license_disclaimer.html",
          "https://github.com/phishdestroy",
          "http://web.archive.org/web/20260911040557/https://github.com/PhishDestroy",
          "https://phishdestroy.io/.well-known/pgp-key.txt",
          "https://steamdestroy.eth/",
          "https://steamdestroy.eth.limo/",
          "https://phishdestroy.eth.limo/",
          "http://web.archive.org/web/20260627040219/https://phishdestroy.eth.limo/",
          "https://phishdestroy.eth/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json.asc",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json.sha256",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json.sha256?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json.sha256?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json.sha256?v=print-20260928-v3"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/id/license_disclaimer.content.json",
      "export_json_sha256": "57fcce03cbe3017413708a4fd899aa3ff2a543fdb16e96fc77310d2900505bce"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "id/market_economics.html",
      "language": "id",
      "title": "Satu infrastruktur, dua pasar — Laporan Khusus “Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/id/market_economics",
      "source_html_sha256": "6a58cd30d9d78f8daec570032e5b0501a563afd0c84d4c3f35aa3071a6beaef1",
      "exported_at": "2026-09-29T00:22:30.670Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "market_economics.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/id/market_economics.pdf?v=print-20260929-v5",
        "sha256": "d03a845f18c6794e189be951bdf2e5cc8ef8ddbc1d7ef3d91ad822891ea8e1f8",
        "bytes": 99588,
        "pages": 8
      },
      "integrity": {
        "signed_object": "market_economics.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "market_economics.content.json.asc",
        "digest_file": "market_economics.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify market_economics.content.json.asc market_economics.content.json",
          "sha256sum -c market_economics.content.json.sha256"
        ]
      },
      "content": {
        "text": "Lampiran VII · Arsitektur Pasar · 20 September 2026\nEkonomi Pasar — Dua Sistem Ekonomi & Batas Atas Pencatatan\n\nInfrastruktur mereka. Dua perekonomian.\n\nAPA YANG DIBUKTIKAN OLEH BAGIAN INI\n\nBab ini menganalisis pemisahan pasar yang bersifat sistemik yang disebabkan oleh batas pencatatan sebesar $1,800 yang diberlakukan oleh Valve serta saldo dompet yang tidak dapat ditarik. Melalui survei terhadap 38 bursa skin eksternal aktif yang memiliki valuasi terdaftar sekitar $1.28 miliar, penyelidikan ini membuktikan bahwa perdagangan tingkat tinggi secara otomatis berpindah ke platform bayangan eksternal sambil tetap mengandalkan infrastruktur perdagangan dan otentikasi dasar Steam. Meskipun penggunaan komersial secara resmi dilarang dalam Perjanjian Pelanggan, Valve memfasilitasi dan memonetisasi ekonomi dua tingkat ini tanpa catatan penegakan aturan yang dipublikasikan.\n\n← Kembali ke Ringkasan Eksekutif\n\n38 pasar CS2 pihak ketiga yang masih aktif, ditambah pasar milik Steam sendiri. Setiap skin yang terdaftar di salah satu platform tersebut harus melewati inventaris Steam dan bertransaksi melalui API. Aturan Valve melarang eksploitasi komersial terhadap infrastruktur tersebut. Nilai skin pihak ketiga yang terdaftar, yang diperkirakan mencapai $1.28 miliar, tetap ada meskipun belum ditemukan catatan publik mengenai penegakan aturan tersebut.\n\n$1.28B\nNilai yang tercantum oleh pihak ketiga · Platform 38\n53.2M\nPenawaran yang ditampilkan · Pasar pihak ketiga 38\n70.1K\nSteam item yang tercantum dalam cuplikan\n41×\nNilai yang dilaporkan pihak ketiga vs $31M dari Steam\nTemuan utama\nSatu infrastruktur. Dua perekonomian.\n\nSteam mengendalikan barang, persediaan, dan perdagangan. Setiap skin yang dijual di platform mana pun di bawah ini harus melalui saluran perdagangan Steam API — sebuah ketergantungan struktural yang dapat diamati secara langsung. Pasar Komunitas milik Valve memperoleh komisi dari penjualannya; apakah komisi tersebut mendanai, atau terkait dengan, ekosistem pihak ketiga, hal itu belum dijelaskan di sini.\n\nMengapa hal ini penting bagi penyelidikan\n1\nPerjanjian Langganan \"Steam\" dari Valve melarang eksploitasi komersial terkait infrastruktur Steam tanpa izin tertulis. Belum ditemukan izin semacam itu dalam catatan publik untuk platform-platform di bawah ini.\n2\nSteam mengelola identitas (OpenID), status inventaris, dan pelaksanaan transaksi untuk nilai aset pihak ketiga yang terdaftar sebesar sekitar $1.28miliar. Tidak ada transfer barang yang terjadi tanpa infrastruktur Valve.\n3\nPasar daring milik Steam memiliki $31M terdaftar — sekitar 1/41 dari nilai yang terdaftar oleh pihak ketiga. Batas harga $1,800 berarti penjual yang harganya melebihi batas tersebut harus menjual di luar platform dengan harga yang berlaku.\n4\n248 Kategori barang CS2, yang masing-masing harganya ditetapkan melebihi batas atas oleh dua atau lebih platform perdagangan secara independen, tidak dapat dijual dengan harga pasar yang tercatat di Steam — dan tidak ada satupun dari produk tersebut yang terdaftar di sana sama sekali. Batas atas sebesar $1,800tersebut menciptakan permintaan yang dipenuhi oleh operator pihak ketiga.\nSteam Pasar Komunitas: $31jutaNilai yang tercantum oleh pihak ketiga: $1,276juta\n$1,276M · nilai yang terdaftar oleh pihak ketiga — semuanya bergantung pada Steam's trade API & OpenID\nSteam · $31juta\n\nSumber: Katalog real-time PriceEmpire, 20 September 2026. Nilai yang tercantum = jumlah nilai kartu yang telah dibulatkan dalam cuplikan yang disimpan, tidak termasuk Steam. Bukan volume penjualan.\n\n38 pasar pihak ketiga yang aktif · Semuanya bergantung pada infrastruktur Steam\nPendaftaran platform\n\nPlatform-platform di bawah ini mengarahkan proses masuk (login) mereka melalui OpenID dari Steam dan transaksi mereka melalui Web API dari Steam. Masing-masing yang teramati openid.realm melewati alur masuk (login) Steam; modul register mencatat rute otentikasi yang teramati, alih-alih menyatakan bahwa operator tertentu tidak memiliki izin dari Valve.\n\n#\tPlatform\tNilai yang tercantum\tPenawaran yang sedang berlaku\tBarang\tSkala\n1\tUUSkins\t$133.8M\t3.4M\t30.9K\t\n\n2\tYouPin898\t$127.5M\t5.9M\t29.2K\t\n\n3\tBuff.163\t$104M\t3.5M\t35K\t\n\n4\tMoon.Market\t$100.3M\t2.9M\t20.9K\t\n\n5\tWhite.Market\t$89.6M\t3M\t20.6K\t\n\n6\tBuff.Market\t$86.7M\t1.3M\t33.4K\t\n\n7\tEcosteam\t$82.1M\t3.3M\t30.1K\t\n\n8\tCSFloat\t$67.8M\t2.4M\t27.8K\t\n\n9\tSkin.Land\t$67.4M\t2.2M\t34.6K\t\n\n10\tLIS-SKINS\t$67.4M\t2.2M\t34.6K\t\n\n11\tC5Game\t$54.6M\t4.6M\t29.6K\t\n\n12\tHaloSkins\t$46.6M\t4.4M\t29.3K\t\n\n13\tAvan.Market\t$43.3M\t809.5K\t22.2K\t\n\n14\tWaxpeer\t$40.1M\t1M\t27.3K\t\n\n15\tSteam (official)\t$31M\t32.2M\t70.1K\t\n\n16\tCS.MONEY\t$29M\t748.9K\t28K\t\n\n17\tMarket.CSGO\t$26.3M\t1.3M\t27.6K\t\n\n18\tCS.MONEY Bot\t$25.7M\t614K\t23.8K\t\n\n19\tSkinport\t$16.3M\t3.8M\t31.1K\t\n\n20\tSkinFlow\t$14.1M\t481.8K\t23.6K\t\n\n21\tDMarket\t$12.6M\t948.2K\t35.6K\t\n\n22\tSkins.com\t$11.5M\t83.2K\t15.8K\t\n\n23\tSkin.place\t$6.9M\t380.8K\t11.4K\t\n\n24\tSkinsMonkey\t$6M\t109.4K\t11.6K\t\n\n25\tSkinBaron\t$5M\t2.1M\t21.5K\t\n\n26\tRustTM\t$3M\t33.1K\t4.9K\t\n\n27\tPirateSwap\t$2M\t859.3K\t10.5K\t\n\n28\tMannco.Store\t$1.2M\t223.7K\t11K\t\n\n29\tSkinSwap\t$1.1M\t11.4K\t4K\t\n\n30\tTradeIt\t$967.1K\t29.1K\t11.7K\t\n\n31\tLootFarm\t$896.1K\t162.5K\t28.6K\t\n\n32\tRustskins\t$714.8K\t312.5K\t6.1K\t\n\n33\tBalticSkins\t$599.2K\t28.2K\t4.5K\t\n\n34\tExeSkins\t$442.9K\t2.6K\t1.4K\t\n\n35\tRapidSkins\t$230.9K\t11.6K\t2.3K\t\n\n36\tCS.Trade\t$203K\t19K\t16.7K\t\n\n37\tKrakatoa\t$11.1K\t115\t53\t\n\n38\tShadowPay\t—\t—\t—\t—\n39\t49skins\t—\t—\t—\t—\nBatas harga $1,800 di Steam · Gambaran singkat lima pasar · 23 September 2026\nSelisih harga tersebut dapat diukur.\n\nSteam membatasi daftar harga di Community Market pada kisaran sekitar $1,800 (hasil perhitungan tersebut dihitung ulang menjadi $2,000, $2,070, $2,300, dan $2,500 pada cs2sh-atlas.json dan berlaku pada setiap ambang batas). Barang-barang yang harganya di atas harga tersebut tidak dapat dijual dengan harga pasar melalui platform penjualan milik Valve — namun mereka tetap bergantung pada sistem inventaris dan pengiriman Steam di mana pun produk tersebut dijual. Pengelompokan seluruh katalog berdasarkan harga menunjukkan di mana batasnya: pasar Valve mencakup 95.3% dari kategori barang yang harganya di bawah batas atasnya dan 1.9% dari yang berada di atasnya.\n\nLima pasar: barang-barang yang harganya melebihi batas harga \"Steam\"\n248\n\nKategori barang yang harga penawaran terendahnya mencapai $1,800 pada dua atau lebih pasar secara terpisah, memiliki salinan-salinan yang terdaftar di 18,394 dengan nilai setidaknya $78.6M. Dari jumlah tersebut, 100.0% — semuanya tanpa kecuali — sama sekali tidak terdaftar di Steam.\n\nBukti-bukti lengkap: daftar → · atlas tangga harga →\n\nDistribusi harga di atas batas atas\n$1,800–$5,000\n174\n$5,000–$10,000\n49\n$10,000–$25,000\n21\n$25,000–$50,000\n2\n$50,000+\n2\nProduk teratas — harga penawaran termurah yang terverifikasi di lima platform jual beli\n1Stiker | Titan (Holo) | Kategori '14$66,285\n2Stiker | iBUYPOWER (Holo) | Kategori '14'$64,795\n3Stiker | Reason Gaming (Holo) | Kategori '14'$42,899\n4★ Sarung Tangan Olahraga | Labirin Semak (FN)$26,812\n5Stiker | Team Dignitas (Holo) | Kat. '14'$23,667\n6EMS Kategori 'Legenda14'$22,879\n7★ Sarung Tangan Olahraga | Kotak Pandora (FN)$21,643\n8EMS Kategori '14: Para Peserta$21,010\n9Stiker | Vox Eminor (Holo) | Kategori '14'$18,619\n10★ Pisau Lipat StatTrak™ | Blue Steel (FN)$18,064\n\nHarga penawaran bukanlah harga jual. Cuplikan data dari cs2.sh (berlisensi), 23 September 2026. Setiap baris dikutip di atas batas atas oleh setidaknya dua platform perdagangan secara independen; penawaran satu rak dan kutipan yang melebihi tiga kali lipat dari harga penawaran termurah suatu barang tidak dimasukkan. Bagaimana sistem penilaiannya →\n\nBerapa tarif yang dikenakan oleh Valve · berlisensi cs2.sh snapshot · 23 September 2026\nBiaya yang diiklankan adalah 15%.. Sebagian besar penawaran membayar lebih tinggi.\n\nValve memotong biaya 5% Steam dan biaya penerbit CS2 10% dari hasil penjualan penjual — yaitu 15%. yang sudah dikenal. Kedua biaya tersebut dikenakan Minimal $0.01, sehingga tidak ada transaksi pun yang biayanya bisa kurang dari dua sen. Pada barang-barang murah dengan volume tinggi yang mendominasi pasar, batas bawah itulah yang menjadi kendala utama, bukan persentasenya. Kami telah menghitung perhitungan biayanya untuk setiap satu dari 29,635 jenis item yang memiliki permintaan \"Steam\" yang masih berlaku.\n\n77.7%\ndaftar produk \"Steam\" yang masih aktif termasuk dalam kategori produk yang dikenakan biaya di atas 15%\n84.8%\njumlah barang jenis pastikan Anda membayar sesuai dengan tarif yang tertera\n4,517\njenis barang yang dikenakan biaya lebih tinggi dari tarif yang diiklankan\n$0.02\nbiaya minimum untuk setiap penjualan, berapa pun harganya\nKedua angka tersebut menunjukkan arah yang berlawanan, dan keduanya benar\n1\nDihitung berdasarkan jenis barang, Biaya yang dikenakan oleh Valve secara umum sesuai dengan yang diiklankan: 84.8% untuk jenis harga yang tercantum di 29,635 dikenakan biaya sebesar atau mendekati 15%.\n2\nDihitung berdasarkan daftar yang sebenarnya, gambarnya terbalik: 18,682,244 dari 24,038,911 Daftar produk real-time tersedia untuk jenis barang yang dikenakan biaya lebih dari 15%.\n3\nKeduanya benar karena tipe-tipe yang mengalami kelebihan muatan adalah murah, dalam jumlah besar yang tersebut. Jenis barang 1,109 dikenakan biaya lebih tinggi daripada ganda tingkat utama, dan jenis-jenis tersebut saja sudah mencakup daftar properti yang masih aktif di 14,083,486.\n4\nIni adalah perhitungan matematis, bukan tuduhan. Jumlah minimum tersebut tercantum dalam dokumen biaya milik Valve sendiri. Yang belum dipublikasikan adalah seberapa besar pangsa pasar yang sebenarnya dicakup oleh hal tersebut — yang merupakan hal yang diukur oleh angka-angka di atas.\nBiaya yang dikenakan, sebagai persentase dari nilai pasar wajar (15%)\n200%+\n14,083,486\n100-200%\n1,028,438\n50-100%\n700,804\n30-50%\n317,031\n20-30%\n2,258,254\n17.6-20%\n294,231\n\nPanjang bar menunjukkan jumlah penawaran aktif di setiap rentang. Rentang “200%+” berarti biaya yang dikenakan lebih dari dua kali lipat dari 15% dari hasil penjualan penjual.\n\nContoh soal yang telah diselesaikan\n67%\n\nDalam sebuah penawaran, pembeli membayar $0.03 karena itu, penjual menerima $0.01 dan \"Valve\" memakan waktu $0.02 — dua batas minimum sebesar satu sen. Jika dihitung sebagai persentase dari jumlah yang dibayarkan pembeli, nilainya adalah 67%; sedangkan jika dihitung sebagai persentase dari hasil penjualan penjual, nilainya adalah 200%.\n\nKumpulan data lengkap: cs2sh-steam-fee-census.json →\n\nBenda yang sama, di dalam taman dan di luar taman\nBerbelanja di Steam harganya lebih mahal. Hampir selalu begitu.\n\nUntuk setiap produk yang tercantum baik di Steam maupun di setidaknya satu platform pasar pihak ketiga, kami membandingkan harga jual termurah di Steam dengan harga jual termurah di luar platform tersebut. Di seluruh 28,700 produk, Steam adalah situs yang harganya lebih mahal 86.4% sebagian besar waktu, dengan nilai median sebesar +35.7%.\n\nNilai median premi asuransi kesehatan (Steam), berdasarkan kisaran harga\ndi bawah $0.50\n+48.3%\n$0.50-2\n+36.5%\n$2-10\n+29.6%\n$10-50\n+28.6%\n$50-250\n+36.3%\n$250-1k\n+51.1%\nlebih dari $1,000\n+67.9%\n\nKurvanya berbentuk huruf U. Harga termurahnya bisa didapatkan dengan membeli di Steam pada $10–$50 pita dan orang tersayang di kedua ujungnya.\n\nMengapa segmen kelas atas itu penting\n+67.9%\n\nDi atas $1,000, biaya rata-rata (median) untuk iklan di Steam 67.9% lebih mahal daripada penawaran termurah di luar situs tersebut — dan hanya 1,040 iklan semacam itu yang tersedia di Steam.\n\nSetelah melampaui angka sekitar $1,800, perbandingan tersebut tidak lagi dapat dilakukan, karena aturan Valve melarang pencantuman harga tersebut sama sekali. Cakupan Steam terhadap barang-barang yang harganya melebihi batas atasnya adalah 1.9%. Lihat daftar lengkapnya →\n\nKumpulan data lengkap: cs2sh-walled-garden-premium.json →\n\nPremi itu sendiri bukanlah suatu temuan: Steam menawarkan pengiriman instan dan bebas risiko pihak lawan, dan pembeli mungkin bersedia membayar untuk itu. Yang dapat diukur adalah besarnya selisih tersebut dan fakta bahwa uang yang mengalir melaluinya tidak dapat ditarik kembali — yang akan dibahas pada bagian berikutnya.\n\nUang masuk, tidak ada uang yang keluar\n$128.1 juta telah dialokasikan untuk pesanan yang tidak dapat dibatalkan.\n\nPesanan pembelian \"Steam\" sudah didanai terlebih dahulu: uang tersebut ditarik dari dompet pembeli begitu pesanan dibuat. Steam dana dompet tidak dapat ditarik kembali — dana tersebut hanya dapat dibelanjakan di dalam Steam. Dengan menjumlahkan setiap level harga pada buku pesanan beli setiap item yang dipantau, kita mendapatkan gambaran keseluruhan mengenai dana yang telah dikomitmenkan dan tidak dapat ditarik kembali.\n\n$128.1M\nberkomitmen untuk menanggapi pesanan pembelian Steam\n170.6M\npesanan beli yang didanai secara individu yang masih berlaku\n$105.8M\nnilai permintaan dari properti yang terdaftar di hadapan mereka\n$15.9M\nBagian yang diperoleh Valve jika setiap properti yang terdaftar terjual sesuai harga yang diminta\nApa yang dimaksud dengan angka ini, dan apa yang bukan\n1\nItu adalah uang sungguhan yang sudah dibayarkan. Setiap dolar yang dihitung telah didebit dari dompet dan saat ini terikat pada pesanan terbuka di seluruh jenis barang d31,253.\n2\nItu adalah bukan pendapatan dan bukan pernyataan mengenai neracValve. Di mana dana yang beredar tersebut disimpan, dan tercatat dalam pembukuan siapa, tidak dijelaskan di sini.\n3\nIni adalah sebuah gambaran sekilas, bukan alur. Pembeli dapat membatalkan pesanan, sehingga dana akan dikembalikan ke dompet — namun dana tersebut belum keluar dari Steam.\n4\nPintu satu arah itulah intinya. Pasar yang mata uangnya tidak dapat dicairkan adalah alasan mengapa persediaan yang dicuri dapat diuangkan mati Steam bukan di atasnya.\n\nMetode: setiap tingkat harga dari setiap buku pesanan beli yang dipantau, dikalikan dengan jumlah pesanan yang ada pada tingkat tersebut. Kumpulan data lengkap: cs2sh-steam-locked-capital.json →\n\nPenjualan yang telah terlaksana, bukan harga yang diminta · satu platform · data historis 90 hari\n$30.9 juta benar-benar berpindah tangan — di rak terkecil dari kelima rak tersebut.\n\nSebuah penjualan dengan harga tinggi bisa saja berupa barang kerajinan langka atau varian yang diberi stiker pada barang dasar yang murah (misalnya, e.g: barang seharga $30 dengan penjualan yang berhasil sebesar $9,772). \"Tinggi\" = transaksi tertinggi yang berhasil, bukan harga normal barang tersebut.\n\nSetiap angka lainnya di halaman ini menunjukkan apa yang terdaftar. Yang ini mengukur apa yang dulunya terjual. Skinport mempublikasikan transaksi yang telah diselesaikannya sendiri, dan selama 90 hari terakhir jumlahnya mencapai 1,219,143 penjualan bernilai $30,927,032, dengan harga rata-rata $25.37 per buah.\n\n1.22M\npenjualan yang berhasil diselesaikan dalam 90 hari, di satu platform pasar\n$30.9M\nomzet selama periode yang sama\n$125M\ntingkat pertumbuhan tahunan — batas bawah, bukan perkiraan\n~2%\nPangsa Skinport dalam rak di atas batas atas berdasarkan nilai pencatatan\nDari mana asal omzet tersebut\ndi bawah $1\n0.5%\n$1-10\n5.8%\n$10-100\n22.2%\n$100-1k\n59.4%\n$1k-1.8k\n6.9%\ndi atas batas “Steam”\n5.3%\n\nPanjang batang menunjukkan volume perdagangan; angka tersebut menunjukkan porsi tingkat tersebut dari total volume. 59.4% dari uang yang beredar di tingkat $100–$1k, dari penjual71,437.\n\nDi atas topi yang dikenakan olehValve, penjualan tetap berlangsung\n492\n\npenjualan barang-barang yang harganya melebihi batas maksimum yang ditetapkan dalam Undang-Undang Perlindungan Konsumen (Steam), senilai $1,643,938, mencakup 76 jenis produk — di sebuah pasar daring yang menguasai sekitar 2% dari pangsa pasar tersebut. Tak satu pun dari penjualan tersebut bisa terjadi di Steam.\n\nKumpulan data lengkap: cs2sh-offsteam-90d-dynamics.json → · level tertinggi yang pernah tercapai →\n\nSkinport merupakan SALAH SATU pasar pihak ketiga yang dipantau di sini, dan karena nilai pencatatan di atas batas “Steam”, pasar ini merupakan yang terkecil di antara kelima pasar tersebut (sekitar 2% dari total tersebut). Setiap angka total di sini merupakan batas bawah ekonomi off-Steam, bukan ukuran dari ekonomi tersebut. Tidak ada data Steam yang digunakan.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Ekonomi Pasar — Dua Sistem Ekonomi & Batas Atas Pencatatan"
          },
          {
            "level": 2,
            "id": null,
            "text": "Satu infrastruktur. Dua perekonomian."
          },
          {
            "level": 2,
            "id": null,
            "text": "Pendaftaran platform"
          },
          {
            "level": 2,
            "id": null,
            "text": "Selisih harga tersebut dapat diukur."
          },
          {
            "level": 3,
            "id": null,
            "text": "Lima pasar: barang-barang yang harganya melebihi batas harga \"Steam\""
          },
          {
            "level": 3,
            "id": null,
            "text": "Distribusi harga di atas batas atas"
          },
          {
            "level": 3,
            "id": null,
            "text": "Produk teratas — harga penawaran termurah yang terverifikasi di lima platform jual beli"
          },
          {
            "level": 2,
            "id": null,
            "text": "Biaya yang diiklankan adalah 15%.. Sebagian besar penawaran membayar lebih tinggi."
          },
          {
            "level": 3,
            "id": null,
            "text": "Biaya yang dikenakan, sebagai persentase dari nilai pasar wajar (15%)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Contoh soal yang telah diselesaikan"
          },
          {
            "level": 2,
            "id": null,
            "text": "Berbelanja di Steam harganya lebih mahal. Hampir selalu begitu."
          },
          {
            "level": 3,
            "id": null,
            "text": "Nilai median premi asuransi kesehatan (Steam), berdasarkan kisaran harga"
          },
          {
            "level": 3,
            "id": null,
            "text": "Mengapa segmen kelas atas itu penting"
          },
          {
            "level": 2,
            "id": null,
            "text": "$128.1 juta telah dialokasikan untuk pesanan yang tidak dapat dibatalkan."
          },
          {
            "level": 2,
            "id": null,
            "text": "$30.9 juta benar-benar berpindah tangan — di rak terkecil dari kelima rak tersebut."
          },
          {
            "level": 3,
            "id": null,
            "text": "Dari mana asal omzet tersebut"
          },
          {
            "level": 3,
            "id": null,
            "text": "Di atas topi yang dikenakan olehValve, penjualan tetap berlangsung"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/id/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/id/elite_skins.html",
          "https://phishdestroy.io/steam_dossier/id/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/id/skin_atlas.html#grading",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-steam-fee-census.json",
          "https://phishdestroy.io/steam_dossier/id/skin_atlas.html#cliff",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-walled-garden-premium.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-steam-locked-capital.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-offsteam-90d-dynamics.json",
          "https://phishdestroy.io/steam_dossier/id/skin_atlas.html#highs"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/id/market_economics.content.json",
      "export_json_sha256": "872cd09cfd9c42178154345f5c60d3d642646c42d564f300fdaa3b661f582b7b"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "id/regulatory_act_print.html",
      "language": "id",
      "title": "UNDANG-UNDANG AUDIT FORENSIK: Valve Steam Situs Web API Ekosistem & Pemanfaatan Komersial (Ref: VAL-REG-2026-09)",
      "source_url": "https://phishdestroy.io/steam_dossier/id/regulatory_act_print",
      "source_html_sha256": "c99c725e92c53b734184345e8c27d6b997bded0ab55e1a8459333a3b5b66fb53",
      "exported_at": "2026-09-29T00:22:31.173Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "regulatory_act_print.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/id/regulatory_act_print.pdf?v=print-20260929-v5",
        "sha256": "97e46eea6fc2304b9f5175a1b25a2be2c31fd60adbb5e99e6647335c0979b60c",
        "bytes": 185751,
        "pages": 14
      },
      "integrity": {
        "signed_object": "regulatory_act_print.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "regulatory_act_print.content.json.asc",
        "digest_file": "regulatory_act_print.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify regulatory_act_print.content.json.asc regulatory_act_print.content.json",
          "sha256sum -c regulatory_act_print.content.json.sha256"
        ]
      },
      "content": {
        "text": "phishdestroy.io · Koalisi Penelitian Forensik · Arsip Publik Universal\nDAFTAR PERKARA: VAL-REG-2026-09-EVID\nASAL-USUL: phishdestroy.io/steam_dossier/\nHAK: SEMUA HAK DILEPASKAN UNTUK KEMANUSIAAN\nUndang-Undang Audit Forensik & Lampiran Peraturan\nPenyediaan Sistemik Layanan \"API\" oleh Pihak Ketiga, Arsitektur Bypass Otomatis, dan Ketidakberlakuan Klausul Kontrak dalam Ekosistem \"Valve\" Steam\nPenerbitan Domainphishdestroy.io\nPlatform SasaranValve Steam / Steamworks\nVektor Otentikasi UtamaSteam OpenID 2.0 / Situs Web API\nPernyataan HukumAll Rights to Humanity (CC0)\nBagian I: Surat Edaran Eksekutif & Temuan FaktaREF: MEMO-RINGKASAN-01\n\nDokumen ini merupakan laporan audit forensik resmi yang mengkaji hubungan operasional antara ketentuan komersial yang dipublikasikan oleh PerusahaanValve, titik akhir otentikasi teknisnya, serta platform komersial pihak ketiga yang teramati. Audit ini dilakukan melalui pengamatan jaringan pasif tanpa otentikasi, verifikasi pendaftaran di RDAP, serta data telemetri Link Filter yang tersedia untuk umum.\n\nInti Fakta: Pengamatan empiris menunjukkan adanya perbedaan sistematis antara pernyataan kontrak publik yang disampaikan oleh Valve dan infrastruktur produksinya. Meskipun Perjanjian Pelanggan (Subscriber Agreement/SSA) Steam secara tegas melarang eksploitasi komersial tanpa izin (§ 2.G), interaksi bot/skrip otomatis (§ 4.C), dan transfer akun (§ 1.C), Valve Corporation tetap menyediakan infrastruktur otentikasi OpenID dan kueri inventaris secara langsung dan terprogram kepada setidaknya 175 entitas komersial yang menghasilkan volume transaksi sekunder senilai miliaran dolar.\n\n175\nOperator Komersial yang Telah Diaudit\n44\nHost Otentikasi dengan Domain Terpisah\n26\nPasangan Proxy dengan Pembagian Filter\n100%\nPasal SSA yang belum diberlakukan: § 2.G / § 4.C\n0\nPencabutan Otorisasi yang Dipaksakan\nKerangka Kerja Kontrak dan Peraturan Perundang-undangan yang Berlaku\nSSA § 2.G\nLarangan Penggunaan Komersial: Dilarang keras memanfaatkan Konten dan Layanan untuk tujuan komersial tanpa izin tertulis terlebih dahulu dari Valve Corporation.\nSSA § 4.C\nPembatasan Otomatisasi: Dilarang keras menggunakan skrip, bot perdagangan, makro, atau sistem yang tidak dikendalikan oleh manusia untuk berinteraksi dengan layanan dan pasar Steam.\nSSA § 1.C\nKewajiban Penggunaan Pribadi: Membatasi penggunaan akun hanya untuk keperluan pribadi; secara tegas melarang penjualan, penyewaan, pengalihan, atau pertukaran akun penggunSteam.\nDSA Uni Eropa (2022/2065)\nPenilaian Risiko Sistemik (Pasal 34/35): Platform Daring Berskala Sangat Besar (VLOP) harus secara aktif mendeteksi, menilai, dan memitigasi risiko sistemik yang timbul akibat penyalahgunaan otomatis dan eksploitasi komersial tanpa izin.\nBagian II: Buku Besar Lampiran A — Pasangan Pemisahan Filter Tautan yang Terdokumentasi (Rute 26)REF: EX-SPLIT-LEDGER\n\nAnalisis Forensik Terhadap Teknik Pengelakan Domain Terpisah: Di bawah sistem Filter Tautan \"Steam\" () yang dikembangkan oleh Valve (steamcommunity.com/linkfilter/?url=...), ketika pengguna akhir mengklik tautan yang mengarah ke platform perjudian atau pasar gelap yang telah ditandai, Valve menampilkan peringatan yang mencolok (\"Tautan Diblokir! ... dilaporkan sebagai tautan yang berpotensi berbahaya\"). Namun, penelusuran jalur forensik menunjukkan bahwa 26 merupakan platform komersial yang beroperasi di arsitektur domain terpisah: meskipun domain komersial utama DIBLOKIR di Link Filter, domain sekunder yang menampung titik akhir respons OpenID Valve ditandai sebagai AMAN. Server OpenID Valve menerima permintaan otentikasi dari host proxy ini tanpa gangguan, sehingga menonaktifkan peringatan keamanan bagi pengguna sambil tetap memproses proses masuk.\n\n#\tDomain Komersial Utama\tFilter Utama\tDomain Proksi Otentikasi OpenID\tFilter Otorisasi\tRDAP Telah terdaftar\tDasar Pengambilan Data\n01\trollbit.com\tBLOCKED\trbsnin.com\tCLEAN\t2026-09-18\tPASSIVE_CAPTURE\n02\tskin.club\tBLOCKED\tsc-auth.net\tCLEAN\t2019-04-02\tPASSIVE_CAPTURE\n03\thowl.gg\tBLOCKED\thowl.uno\tCLEAN\t2026-08-11\tPASSIVE_CAPTURE\n04\tduelbits.com\tBLOCKED\tswitchflips.com\tCLEAN\t2020-04-21\tPASSIVE_CAPTURE\n05\tcsgofast.com\tBLOCKED\tsteam-login.authtofast.com\tCLEAN\t2026-06-30\tPASSIVE_CAPTURE\n06\tfarmskins.com\tBLOCKED\tsteam.kobal.cc\tCLEAN\t2017-01-07\tPASSIVE_CAPTURE\n07\tcobaltlab.tech\tBLOCKED\tcobaltauth.com\tCLEAN\t2025-01-07\tPASSIVE_CAPTURE\n08\tcsgo.net\tBLOCKED\tcn2.easylot.net\tCLEAN\t2016-09-03\tPASSIVE_CAPTURE\n09\tggdrop.com\tBLOCKED\tggauth.com\tCLEAN\t2023-05-03\tPASSIVE_CAPTURE\n10\trustchance.com\tBLOCKED\thgfuihd.com\tCLEAN\t2019-01-27\tPASSIVE_CAPTURE\n11\tskin.fans\tBLOCKED\tauth.skinfans.com\tCLEAN\t2018-07-16\tPASSIVE_CAPTURE\n12\tskinport.com\tBLOCKED\tskinport.app\tCLEAN\t2020-06-20\tPASSIVE_CAPTURE\n13\tskins.cash\tBLOCKED\tskinscash.live\tCLEAN\t2019-12-05\tPASSIVE_CAPTURE\n14\ttf2hunt.com\tBLOCKED\trstspcl.com\tCLEAN\t2020-08-08\tPASSIVE_CAPTURE\n15\tdaddyskins.com\tBLOCKED\tgo-go-daddy.com\tCLEAN\t2019-01-26\tPASSIVE_CAPTURE\n16\tkey-drop.com\tBLOCKED\tkdauth.com\tCLEAN\t2026-05-13\tPASSIVE_CAPTURE\n17\tclash.gg\tBLOCKED\tclggauth.com\tCLEAN\t2024-09-16\tPASSIVE_CAPTURE\n18\tc5game.com\tBLOCKED\twww.imbastar.com\tCLEAN\t2016-02-27\tPASSIVE_CAPTURE\n19\tswap.gg\tBLOCKED\tswapauth.com\tCLEAN\t2018-10-06\tPASSIVE_CAPTURE\n20\tshadowpay.com\tBLOCKED\tthelogins.com\tCLEAN\t2018-01-22\tPASSIVE_CAPTURE\n21\tcsgocases.com\tBLOCKED\tlog-1n.com\tCLEAN\t2017-11-27\tPASSIVE_CAPTURE\n22\tcsgogem.com\tBLOCKED\tapi.csgem.com\tCLEAN\t2014-03-08\tPASSIVE_CAPTURE\n23\tgamdom.com\tBLOCKED\tlogin.gambldom.com\tCLEAN\t2017-09-24\tPASSIVE_CAPTURE\n24\t12cs.fail\tBLOCKED\tfail.games\tCLEAN\t2021-08-24\tPASSIVE_CAPTURE\n25\tskinsnipe.com\tBLOCKED\tpricing.tradeupspy.com\tCLEAN\t2020-03-11\tPASSIVE_CAPTURE\n26\tcsgobig.com\tBLOCKED\tletmeinbig.com\tCLEAN\t2023-01-20\tPASSIVE_CAPTURE\n\n* Catatan: Pemeriksaan pasif dilakukan terhadap titik akhir Filter Tautan Steam yang belum diautentikasi di 2026-09-19 dan 2026-09-21.. Isi respons HTTP mentah serta ringkasan SHA-256 disimpan dalam dataset repositori (steam_tos_assets/linkfilter-2026-09-22.json).\n\nBagian III: Buku Besar Lampiran B — Sensus Komprehensif Entitas Komersial yang Telah Diaudit oleh Badan Pengawasan Perdagangan (175)REF: EX-175-MASTER-CENSUS\n\nDaftar berikut ini memuat rincian semua platform komersial pihak ketiga 175 yang telah diverifikasi secara aktif dalam basis data audit. Setiap catatan mencantumkan nama entitas, domain komersial utama, rute otentikasi OpenID yang teramati Steam, klasifikasi aktivitas, pemetaan pelanggaran kontrak (SSA § 2.G, SSA § 4.C, SSA § 1.C), serta kolom tindakan yang tercatat dalam kumpulan data sumber. Label \"Lihat bukti bertanggal\" mengarahkan pembaca ke catatan pendukung; label ini tidak menunjukkan bahwa Valve tidak mengambil tindakan apa pun. Kolom tindakan yang tidak ada dilaporkan sebagai \"tidak ditetapkan\".\n\nPameran\tNama Entitas & Domain Utama\tRute Otentikasi / Proksi yang Diamati\tKlasifikasi\tPelanggaran Kontrak\tValve Aksi\nEX-001\tCSGORoll\ncsgoroll.com\n\t\nwww.csgoroll.com\nDIRECT\n\tSkin Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-002\tCSGOEmpire\ncsgoempire.com\n\t\ncsgoempirelogin4.com\nSPLIT PROXY\n\tCasino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-003\tRollbit\nrollbit.com\n\t\nrbsnin.com\nSPLIT PROXY\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-004\t500 Casino\n500.casino\n\t\nfivezerozero.co\nSPLIT PROXY\n\tLicenced Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-005\tCSGOBig\ncsgobig.com\n\t\ncsgobig.com\nDIRECT\n\tRoulette/Slots\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-006\tCaseDrop\ncasedrop.com\n\t\ncasedrop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-007\tRustReaper\nrustreaper.com\n\t\nrustreaper.com\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-008\tBanditCamp\nbanditcamp.com\n\t\nbanditcamp.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-009\tSkinBox\nskinbox.com\n\t\nskinbox.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-010\tTastyDrop\ntastydrop.com\n\t\ntastydrop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-011\tCSGOPolygon\ncsgopolygon.gg\n\t\ncsgopolygon.gg\nDIRECT\n\tRoulette Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-012\tMagicDrop\nmagicdrop.ru\n\t\nmagicdrop.ru\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-013\tCSDice\ncsdice.com\n\t\ncsdice.com\nDIRECT\n\tDice Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-014\tRustly\nrustly.com\n\t\nrustly.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-015\tSkinOdds\nskinodds.com\n\t\nskinodds.com\nDIRECT\n\tUpgrader Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-016\tCSGOWin\ncsgowin.com\n\t\ncsgowin.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-017\tCSGORun\ncsgorun.net\n\t\ncsgorun.net\nDIRECT\n\tCrash Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-018\tOpenSkins\nopenskins.com\n\t\nopenskins.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-019\tRustBet\nrustbet.com\n\t\nrustbet.com\nDIRECT\n\tRust Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-020\tCSGOMagic\ncsgomagic.com\n\t\ncsgomagic.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-021\tCSGOBounty\ncsgobounty.com\n\t\ncsgobounty.com\nDIRECT\n\tUpgrader/Contract\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-022\tEZSkins\nezskins.com\n\t\nezskins.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-023\tRustCases\nrustcases.com\n\t\nrustcases.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-024\tCSGOReaper\ncsgoreaper.com\n\t\ncsgoreaper.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-025\tCSGOCases\ncsgocases.com\n\t\ncsgocases.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-026\tCSGO-Skins\ncsgo-skins.com\n\t\ncsgo-skins.com\nDIRECT\n\tCase Upgrader\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-027\tCSGONet\ncsgonet.com\n\t\ncsgonet.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-028\tWTFSkins\nwtfskins.com\n\t\nwtfskins.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-029\tCSGOFast\ncsgofast.com\n\t\nsteam-login.authtofast.com\nSPLIT PROXY\n\tRoulette Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-030\tDuelbits\nduelbits.com\n\t\nswitchflips.com\nSPLIT PROXY\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-031\tFlameCases\nflamecases.com\n\t\nflamecases.com\nDIRECT\n\tCase Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-032\tFarmskins\nfarmskins.com\n\t\nsteam.kobal.cc\nSPLIT PROXY\n\tCase Opener\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-033\tCSGOLuck\ncsgoluck.com\n\t\ncsgoluck.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-034\tGamedom\ngamedom.com\n\t\ngamedom.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-035\tSkin.Club\nskin.club\n\t\nsc-auth.net\nSPLIT PROXY\n\tCase Battles\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-036\tDaddySkins\ndaddyskins.com\n\t\ndaddyskins.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-037\tInsane.gg\ninsane.gg\n\t\napi.insane.gg\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-038\tRustix\nrustix.gg\n\t\nrustix.gg\nDIRECT\n\tRust Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-039\tSkins.Club\nskins.club\n\t\nskins.club\nDIRECT\n\tSkin Upgrade\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-040\tCSGOHouse\ncsgohouse.org\n\t\ncsgohouse.org\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-041\tSkinRave\nskinrave.net\n\t\nskinrave.net\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-042\tBloodyCase_GG\nbloodycase.gg\n\t\nbloodycase.gg\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-043\tCSGOClicker\ncsgoclicker.com\n\t\ncsgoclicker.com\nDIRECT\n\tClicker/Upgrade\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-044\tRustBet_GG\nrustbet.gg\n\t\nrustbet.gg\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-045\tCS_Drop\ncs-drop.com\n\t\ncs-drop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-046\tHellStore\nhellstore.net\n\t\nhellstore.net\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-047\tRustLoot\nrustloot.com\n\t\nrustloot.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-048\tCSGO_Case\ncsgo-case.com\n\t\ncsgo-case.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-049\tCS2Skin\ncs2skin.com\n\t\ncs2skin.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-050\tJuice_GG\njuice.gg\n\t\nletmeinjuice.com\nSPLIT PROXY\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-051\tGGDrop\nggdrop.com\n\t\nggauth.com\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-052\tCSGOGem\ncsgogem.com\n\t\ncsgogem.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-053\tRainbet\nrainbet.com\n\t\nservices.rainbet.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-054\tHowl_GG\nhowl.gg\n\t\nhowl.uno\nSPLIT PROXY\n\tSkins Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-055\tChicken_GG\nchicken.gg\n\t\nchicken.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-056\tCSGOCasino_GG\ncsgocasino.gg\n\t\napi.csgocasino.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-057\tHunt_GG\nhunt.gg\n\t\napi.hunt.gg\nDIRECT\n\tSkins Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-058\tCSBattle\ncsbattle.com\n\t\ncsbattle.com\nDIRECT\n\tCase Battles\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-059\tSkinRave_GG\nskinrave.gg\n\t\napi.skinrave.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-060\tCSDouble\ncsdouble.gg\n\t\ncsdouble.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-061\tRustChance\nrustchance.com\n\t\nhgfuihd.com\nSPLIT PROXY\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-062\tRustClash\nrustclash.com\n\t\nrustclash.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-063\tCobaltLab\ncobaltlab.tech\n\t\ncobaltauth.com\nSPLIT PROXY\n\tRust Automation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-064\tRaided_GG\nraided.gg\n\t\napi.raided.gg\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-065\tRustNeo\nrustneo.gg\n\t\nrustneo.gg\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-066\tSplits_GG\nsplits.gg\n\t\nsplits.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-067\tUpgrader_Pro\nupgrader.pro\n\t\nupgauth.space\nSPLIT PROXY\n\tSkin Upgrader\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-068\tSkinFans\nskin.fans\n\t\nauth.skinfans.com\nSPLIT PROXY\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-069\tHotPizza\nhotpizza.one\n\t\nhotpizza.one\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-070\tG4Skins\ng4skins.com\n\t\nauth.g4s.to\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-071\t12CS_Fail\n12cs.fail\n\t\n12cs.fail\nDIRECT\n\tCrash Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-072\tTF2Royal\ntf2royal.com\n\t\ntf2auth.com\nSPLIT PROXY\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-073\tTF2Easy\nwww.tf2easy.com\n\t\nwww.tf2easy.com\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-074\tTF2Hunt\ntf2hunt.com\n\t\nrstspcl.com\nSPLIT PROXY\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-075\tTF2Bet\ntf2.bet/coinflip\n\t\ntf2.bet\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-076\tTF2Blaze\ntf2blaze.com\n\t\ntf2blaze.com\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-077\tOpenStars_GG\nopenstars.gg\n\t\nopenstars.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-078\tShuffle_Com\nshuffle.com\n\t\nshuffle.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-079\tSkins.com\nskins.com\n\t\napi.skins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-080\tWhite.Market\nwhite.market\n\t\nwhite.market\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-081\tBuff.Market\nbuff.market\n\t\nbuff.market\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-082\tAvan.Market\navan.market\n\t\navan.market\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-083\tCS.MONEY\ncs.money\n\t\nauth.dota.trade\nSPLIT PROXY\n\tTrading Engine\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-084\tUUSkins\nuuskins.com\n\t\nuuskins.com\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-085\tYouPin898\nyoupin898.com\n\t\nyoupin898.com\nDIRECT\n\tMass Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-086\tMoon.Market\nmoon.market\n\t\nmoon.market\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-087\tCSFloat\ncsfloat.com\n\t\ncsgofloat.com\nSPLIT PROXY\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-088\tSkin.Land\nskin.land\n\t\nauth.skin.land\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-089\tC5Game\nc5game.com\n\t\nc5game.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-090\tHaloSkins\nhaloskins.com\n\t\nhaloskins.com\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-091\tBuff.163\nbuff.163.com\n\t\nbuff.163.com\nDIRECT\n\tCorporate Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-092\tWaxpeer\nwaxpeer.com\n\t\nwaxpeer.com\nDIRECT\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-093\tCS.MONEY Bot\ncs.money\n\t\nauth.dota.trade\nSPLIT PROXY\n\tBot Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-094\tMarket.CSGO\nmarket.csgo.com\n\t\ndota2.net\nSPLIT PROXY\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-095\tSkinport\nskinport.com\n\t\nskinport.app\nSPLIT PROXY\n\tRegulated Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-096\tSkinFlow\nskinflow.gg\n\t\napi.skinflow.gg\nDIRECT\n\tMarketplace/Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-097\tDMarket\ndmarket.com\n\t\ndmarket.com\nDIRECT\n\tUS Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-098\tSkin.place\nskin.place\n\t\napi.skin.place\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-099\tSkinsMonkey\nskinsmonkey.com\n\t\nskinsmonkey.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-100\tSkinBaron\nskinbaron.de\n\t\nskinbaron.com\nSPLIT PROXY\n\tCorporate Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-101\tSteam\nsteamcommunity.com/market\n\t\nsteamcommunity.com/market\nDIRECT\n\tOfficial Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-102\tRustTM\nrust.tm\n\t\ndota2.net\nSPLIT PROXY\n\tRust Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-103\tPirateSwap\npirateswap.com\n\t\nlogin.pirateswap.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-104\tMannco.Store\nmannco.store\n\t\nmannco.store\nDIRECT\n\tTF2 Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-105\tSkinSwap\nskinswap.com\n\t\napi.skinswap.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-106\tLootFarm\nlootfarm.com\n\t\nlootfarm.com\nDIRECT\n\tTrading Platform\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-107\tRustskins\nrustskins.com\n\t\nrustskins.com\nDIRECT\n\tRust Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-108\tExeSkins\nexeskins.com\n\t\nexeskins.com\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-109\tBalticSkins\nbalticskins.com\n\t\nbalticskins.com\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-110\tCS.Trade\ncs.trade\n\t\ncs.trade\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-111\tRapidSkins\nrapidskins.com\n\t\napi.rapidskins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-112\tTradeIt\ntradeit.gg\n\t\nconnect-tradeit.com\nSPLIT PROXY\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-113\tKrakatoa\nkrakatoa.com\n\t\nkrakatoa.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-114\tShadowPay\nshadowpay.com\n\t\nshadowpay.com\nDIRECT\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-115\t49skins\n49skins.com\n\t\napi.49skins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-116\tSkinVault\nskinvault.gg\n\t\napi.skinvault.gg\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-117\tAim Market\naim.market\n\t\naim.market\nDIRECT\n\tSkins Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-118\tSkinout\nskinout.gg\n\t\nauth.skinout.gg\nDIRECT\n\tInstant Sell Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-119\tNTSkins\nntskins.com\n\t\nntskins.com\nDIRECT\n\tSkins Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-120\tIGXE\nigxe.cn\n\t\nigxe.cn\nDIRECT\n\tChinese Powerhouse\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-121\tSwap.gg\nswap.gg\n\t\nswap.gg\nDIRECT\n\tAutomated Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-122\tBitskins\nbitskins.com\n\t\nbitskins.com\nDIRECT\n\tCash-out Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-123\tGamerPay\ngamerpay.gg\n\t\ngamerpay.gg\nDIRECT\n\tP2P Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-124\tTF2Mart\ntf2mart.com\n\t\ntf2mart.com\nDIRECT\n\tTF2 Automation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-125\tSkinBid\nskinbid.com\n\t\nskinbid.com\nDIRECT\n\tSkin Auctions\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-126\tLootBear\nlootbear.com\n\t\nlootbear.com\nDIRECT\n\tSkin Rental\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-127\tBackpack.tf\nbackpack.tf\n\t\nbackpack.tf\nDIRECT\n\tTF2 Valuation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-128\tScrap.tf\nscrap.tf\n\t\nscrap.tf\nDIRECT\n\tTF2 Scrap Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-129\tMarketplace.tf\nmarketplace.tf\n\t\nmarketplace.tf\nDIRECT\n\tTF2 Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-130\tSTNTrading\nstntrading.eu\n\t\nstntrading.eu\nDIRECT\n\tTF2 Botnet\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-131\tSkins.Cash\nskins.cash\n\t\nskinscash.live\nSPLIT PROXY\n\tInstant Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-132\tSkinWallet\nskinwallet.com\n\t\nskinwallet.com\nDIRECT\n\tInstant Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-133\tDota2Market\ndota2market.com\n\t\ndota2market.com\nDIRECT\n\tDota 2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-134\tCSGO.NET\ncsgo.net\n\t\ncn2.easylot.net\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-135\tCybershoke\ncybershoke.net\n\t\nauth.cybershoke.net\nDIRECT\n\tCommunity Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-136\tXPlay_GG\nxplay.gg\n\t\nxplay.gg\nDIRECT\n\tServer Network\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-137\tFastCup\nfastcup.net\n\t\napi.fastcup.net\nDIRECT\n\tMatchmaker Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-138\tEsportal\nesportal.com\n\t\nesportal.com\nDIRECT\n\tMatchmaking Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-139\tGamersClub\ngamersclub.com.br\n\t\ngamersclub.com.br\nDIRECT\n\tLATAM Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-140\tLeetify\nleetify.com\n\t\nleetify.com\nDIRECT\n\tSaaS Analytics\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-141\tScope_GG\nscope.gg\n\t\nscope.gg\nDIRECT\n\tSaaS Analytics\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-142\tTradeUpSpy\ntradeupspy.com\n\t\napi.tradeupspy.com\nDIRECT\n\tSaaS Tools\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-143\tEpidemic_GG\nepidemic.gg\n\t\nepidemic.gg\nDIRECT\n\tSaaS Tools\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-144\tCSDeals\ncs.deals\n\t\napi.cs.deals\nDIRECT\n\tMarketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-145\tPricempire\npricempire.com\n\t\npricempire.com\nDIRECT\n\tSaaS Price DB\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-146\tCS2Stash\ncs2stash.com\n\t\ncs2stash.com\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-147\tCSGOSkins\ncsgoskins.gg\n\t\ncsgoskins.gg\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-148\tSteamAnalyst\nsteamanalyst.com\n\t\nsteamanalyst.com\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-149\tSteamCardExchange\nsteamcardexchange.net\n\t\nsteamcardexchange.net\nDIRECT\n\tTrading Exchange\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-150\tDotaBuff\ndotabuff.com\n\t\ndotabuff.com\nDIRECT\n\tSaaS Tracker\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-151\tTracker_GG\ntracker.gg\n\t\ntracker.gg\nDIRECT\n\tSaaS Tracker\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-152\tFSB Market (an anonymized label; the original name is withheld here)\nFSB Market\n\t\nFSB Market\nDIRECT\n\tMass Blackmarket\tSSA § 2.G, SSA § 4.C, SSA § 1.C\tSee dated evidence\nEX-153\tFunPay\nfunpay.com\n\t\nfunpay.com\nDIRECT\n\tAccount Exchange\tSSA § 2.G, SSA § 4.C, SSA § 1.C\tSee dated evidence\nEX-154\tPlayerAuctions\nplayerauctions.com\n\t\nplayerauctions.com\nDIRECT\n\tGrey Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-155\tEldorado.gg\neldorado.gg\n\t\neldorado.gg\nDIRECT\n\tAccount Portal\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-156\tG2A\ng2a.com\n\t\ng2a.com\nDIRECT\n\tMass Key Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-157\tKinguin\nkinguin.net\n\t\nkinguin.net\nDIRECT\n\tMass Key Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-158\tG2G.com\ng2g.com\n\t\ng2g.com\nDIRECT\n\tVirtual Services\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-159\tPlayerup\nplayerup.com\n\t\nplayerup.com\nDIRECT\n\tAccount Broker\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-160\tZ2U.com\nz2u.com\n\t\nwww.z2u.com\nDIRECT\n\tReady-Account Hub\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-161\tSmurfHub\nsmurfhub.net\n\t\nsmurfhub.net\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-162\tSmurfAccounts\nsmurfaccounts.com\n\t\nsmurfaccounts.com\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-163\tBuyCSGORank\nbuycsgorank.com\n\t\nbuycsgorank.com\nDIRECT\n\tRank Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-164\tCSGOSmurfKings\ncsgosmurfkings.com\n\t\ncsgosmurfkings.com\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-165\tSmurfStore_Co\nsmurfstore.co\n\t\nsmurfstore.co\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-166\tSteamLvlUp\nsteamlvlup.com\n\t\nsteamlvlup.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-167\tSteamLevels\nsteamlevels.com\n\t\nsteamlevels.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-168\tLevelSteam\nlevelsteam.com\n\t\nlevelsteam.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-169\tSteamLevelU\nsteamlevelu.com\n\t\nsteamlevelu.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-170\tEloKing\neloking.com\n\t\neloking.com\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-171\tBoosteria\nboosteria.org\n\t\nboosteria.org\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-172\tOvergear\novergear.com\n\t\novergear.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-173\tBlazingBoost\nblazingboost.com\n\t\nblazingboost.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-174\tDota2Boost\ndota2boost.com\n\t\ndota2boost.com\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-175\tBuyBoost\nbuyboost.com\n\t\nbuyboost.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nBagian IV: Arsitektur Teknis & Mekanisme OtentikasiREF: ANALISIS TEKNIS -01\n\n1. Tidak Adanya Validasi Kepemilikan Domain dalam OpenID 2.0: Penerapan protokol OpenID 2.0 oleh Valve (https://steamcommunity.com/openid/login) mengevaluasi openid.return_to dan openid.realm parameter tanpa memerlukan pendaftaran pengembang terlebih dahulu, verifikasi tantangan kriptografis, atau validasi kepemilikan domain. Setiap operator komersial dapat mengarahkan pengguna ke layar masuk Valve dan menerima pernyataan identitas yang ditandatangani secara kriptografis (yang berisi SteamID dengan bit \"64-\") yang dialihkan ke domain mana pun.\n\n2. Penyalahgunaan Kunci \"Programmatic Inventory Querying\" dan \"API\": Setelah otentikasi pengguna dikonfirmasi melalui OpenID, operator melakukan permintaan ke titik akhir Web API publik dan mitra (IEconItems_730/GetPlayerItems) untuk mengindeks aset inventaris secara real-time. Jaringan perdagangan otomatis menggunakan token sesi terprogram untuk mengirimkan, memeriksa, dan menerima penawaran perdagangan peer-to-peer (P2P), yang secara langsung bertentangan dengan larangan interaksi non-manusia sebagaimana diatur dalam SSA § 4.C.\n\n3. Asimetri Filter Tautan: Adanya peringatan domain yang ditujukan kepada konsumen bersamaan dengan titik akhir otentikasi yang berfungsi penuh menimbulkan kontradiksi regulasi: telemetri keamanan Valve mengklasifikasikan operator-operator ini sebagai \"berpotensi berbahaya\", namun infrastruktur otentikasi Valve tetap melakukan otentikasi terhadap basis penggunanya.\n\nMetodologi Pembuktian & Pernyataan Rantai Pengawasan\n\nDokumen ini disusun berdasarkan data tangkapan jaringan yang belum terotentikasi, riwayat kueri registri RDAP, serta manifes hash kriptografi yang telah diverifikasi. Tidak ada kredensial login pengguna yang diuji terhadap kemungkinan kebocoran atau diproses. Semua temuan mencerminkan kondisi jaringan produksi yang dapat diamati per tanggal 2026.. Dokumen ini berfungsi sebagai bukti teknis yang netral dan disiapkan untuk keperluan penyelidikan yudisial, regulasi, dan publik.\n\nRINGKASAN: SHA-256: TERVERIFIKASI\nc507c9025f93da0aadaf395c4d8882f25973211c318ee8e9b6f18a5b3755e050\nARSIP: REKAM JEJAK HUKUM YANG TERBUKA\nDITERBITKAN & DITANDATANGANI OLEH: phishdestroy.io · Koalisi Penelitian Forensik\nSTATUS HUKUM: SEMUA HAK DILEPASKAN UNTUK KEMANUSIAAN · CC0 DOMAIN PUBLIK UNIVERSAL",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Undang-Undang Audit Forensik & Lampiran Peraturan"
          }
        ],
        "links": []
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/id/regulatory_act_print.content.json",
      "export_json_sha256": "c6579b37bc099bdd1e33c9d8c21b8e4d98195ca37f901b2a390b133fa14a95c4"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "id/security_timeline.html",
      "language": "id",
      "title": "Garis Waktu Keamanan — Dokumen Kasus \"Steam\"",
      "source_url": "https://phishdestroy.io/steam_dossier/id/security_timeline",
      "source_html_sha256": "a7e50486d0ed0126d179493d2bcc9ddf734d74a24813ca8e1a119698df5cc814",
      "exported_at": "2026-09-29T00:22:32.213Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "security_timeline.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/id/security_timeline.pdf?v=print-20260929-v5",
        "sha256": "e6a24a2e17c35194c1ac842849e535feb65535fd5135121019682f5c9e742196",
        "bytes": 96100,
        "pages": 7
      },
      "integrity": {
        "signed_object": "security_timeline.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "security_timeline.content.json.asc",
        "digest_file": "security_timeline.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify security_timeline.content.json.asc security_timeline.content.json",
          "sha256sum -c security_timeline.content.json.sha256"
        ]
      },
      "content": {
        "text": "REKAM JEJAK KEAMANANPAMERAN / KARYA YANG DIKIRIMKAN KE \"16\"\n\n2018 — 2026\n\nLintasan Sejarah Keamanan — 2018 hingga 2026\n\nKeamanan telah berubah. Ikuti catatan tersebut.\n\nAPA YANG DIBUKTIKAN OLEH BAGIAN INI\n\nCatatan kronologis ini merekonstruksi perubahan keamanan selama delapan tahun pada tumpukan perdagangan dan otentikasi Steam. Catatan ini melacak 2018 7-penerapan penangguhan perdagangan harian, 2023 Web API konfirmasi melalui perangkat seluler, serta 2026 penghentian penggunaan token sesi sebagai respons terhadap teknik-teknik bypass yang terdokumentasi. Garis waktu ini menunjukkan bahwa pembaruan platform secara konsisten tertinggal dari vektor eksploitasi yang sudah diketahui, namun tetap mempertahankan keunggulan struktural bagi operator komersial.\n\n← Kembali ke Ringkasan Eksekutif\n\nKunci perdagangan. Kontrol masuk. Pembatasan API. Catatan historis mengenai apa yang telah berubah—dan apa yang sebenarnya dibuktikan oleh sumber-sumber tersebut.\n\nJelajahi garis waktu ↓\nDELAPAN TAHUN. SATU REKOR.16tonggak penting yang perlu ditinjau\n\nSetiap entri menyimpan tanggal pengiriman dan sumbernya. Hasil verifikasi ditampilkan di sampingnya.\n\nTELAH DIREVIEW / 24 SEP 2026\n10Acara & tanggal yang telah diverifikasi\n06Telah diverifikasi sebagian\n00Ketidaksesuaian sumber\n00Diperlukan sumber\nCara membaca catatan ini\n\nAcara dan tanggal yang telah diverifikasi: keduanya didukung oleh sumber primer yang mudah dipahami. Telah diverifikasi sebagian: Perubahan terkait telah didokumentasikan, namun tanggal atau cakupannya masih belum diputuskan. Ketidaksesuaian sumber: Materi yang ditautkan tersebut tidak mendukung klaim yang diajukan. Diperlukan sumber: Tidak ada sumber bertanggal yang sesuai yang diverifikasi dalam tinjauan ini. Entri yang belum terverifikasi bukanlah bukti bahwa suatu peristiwa tidak pernah terjadi.\n\nTanggal pada entri yang belum diselesaikan adalah tanggal pengiriman, bukan tanggal rilis yang telah diverifikasi. Teks investigasi aslinya belum ditulis ulang.\n\nUrutan waktu\n01 — 16\nCari catatan tersebutTopikBuktiPesanan\n\n16 dari entri-16 · yang terbaru terlebih dahulu\n\n202609-01Tanggal pengiriman\nKomunitasTelah diverifikasi sebagian\nPeringatan pesan mencurigakan di obrolan grup\n\nSebuah pengumuman resmi mengenai versi beta mengonfirmasi fitur tersebut pada 31 Agustus. Tanggal rilis versi stabil 1 September yang disebutkan masih memerlukan catatan rilis yang spesifik.\n\nSteam Versi Beta untuk Klien — 31Agustus ↗diarsipkan 2026-03-13 ↗\nEntri asli & tautan yang dikirimkan\n\nPenandaan Otomatis Percakapan yang Mencurigakan\n\nPeriksa kode sumber yang dikirimkan ↗\n202601-16Tanggal verifikasi\nAPIAcara & tanggal yang telah diverifikasi\nIzin terperinci & daftar putih IP untuk Kunci Penerbit (pengumuman Valve)\n\nPada 16 Januari 2026, Valve menerbitkan pengumuman resmi Steamworks (\"BARU: Izin dan kontrol yang lebih baik untuk Kunci Web API\") yang mengonfirmasi adanya alat izin terperinci baru yang memungkinkan pengembang untuk membagi kunci Web API menjadi beberapa kelompok terpisah (Data Umum, Transaksi Mikro, Ekonomi, dan Penjualan), membatasi kunci pada ID Aplikasi tertentu, dan menerapkan daftar putih alamat IP server.\n\nStandar Ganda yang Sangat Mencolok: Pengumuman resmi ini menyatakan bahwa Valve telah sepenuhnya mengembangkan infrastruktur teknis untuk izin akses yang terperinci (API) dan pembatasan alamat IP, namun secara sengaja tidak memberikan akses tersebut kepada akun pengguna biasa (steamcommunity.com/dev/apikey). Kunci \"API\" bagi pengguna biasa tetap berupa kredensial monolitik yang bersifat \"semua atau tidak sama sekali\" tanpa daftar putih alamat IP—dan inilah kelalaian teknis yang justru memungkinkan berkembangnya industri penyadapan transaksi \"API\" senilai jutaan dolar.\n\nValve Pengumuman — BARU: Izin dan kontrol yang lebih baik untuk Kunci Web API (16 Jan 2026) ↗· Dokumentasi: Otentikasi Steamworks Web API ↗\nEntri asli & tautan yang dikirimkan\n\nAPI Web Steamworks: Ruang Lingkup Terperinci\n\nLihat Pengumuman Resmi Steamworks untuk Valve (493839547938902179) ↗\n202507-15Tanggal verifikasi\nPerdaganganAcara & tanggal yang telah diverifikasi\nTransaksi CS2 memasuki jendela pembalikan selama tujuh hari\n\nPengumuman Valve yang sudah lama diterbitkan mengumumkan pembatalan transaksi item Counter-Strike yang dilakukan dalam tujuh hari sebelumnya. Meskipun dirancang untuk mengurangi praktik pembajakan, audit ekonomi pihak ketiga (CSMarketCap ↗) mencatat sebuah $104M (-25%) tutup dalam kapitalisasi pasar dalam waktu 24 jam akibat gangguan pada perdagangan tunai. Sebagaimana dianalisis oleh Skinvault ↗, memicu pembalikan akan secara otomatis memberlakukan pembatasan perdagangan harian (30-) pada akun tersebut. Pada musim panas 2026, Valve beralih dari pengaturan ulang global pada tengah malam UTC ke pengatur waktu per item yang dihitung per menit (Skin.land ↗).\n\nValve — 15 Pengumuman tanggal 2025 ↗· Analisis CSMarketCap ↗\nEntri asli & tautan yang dikirimkan\n\nPerlindungan Perdagangan CS2 / Jendela Pembatalan\n\nPeriksa kode sumber yang dikirimkan ↗\n202505-14Tanggal verifikasi\nOtentikasiAcara & tanggal yang telah diverifikasi\nValve menerbitkan peringatan keamanan akun terkait kebocoran SMS\n\nPengumuman resmi Valve pada 5 Mei 14, 2025, membahas keamanan akun dan sistem otentikasi berbasis SMS. Meskipun pengumuman tersebut berfokus pada kebocoran SMS dan menegaskan bahwa tidak ada sistem Steam yang diretas, pengumuman ini berfungsi sebagai pembaruan keamanan resmi pada tanggal yang disebutkan.\n\nValve — Catatan mengenai keamanan akun Steam Anda ↗\nEntri asli & tautan yang dikirimkan\n\nPengumuman Mengenai Keamanan Akun\n\nPeriksa kode sumber yang dikirimkan ↗\n202410-02Tanggal verifikasi\nPerdaganganAcara & tanggal yang telah diverifikasi\nTujuh hari sebelum penjualan kembali atau pemasaran ulang\n\nCatatan rilis ini mencakup item yang diperoleh melalui toko dalam game, termasuk Armory, penawaran pertukaran, dan Pasar Komunitas. Cakupan yang tercantum dalam catatan ini lebih luas daripada sekadar item Armory saja.\n\nValve — Catatan Rilis untuk 10/2/2024 ↗\nEntri asli & tautan yang dikirimkan\n\nCS2 The Armory / Pertandingan Sehari di7-\n\nPeriksa kode sumber yang dikirimkan ↗\n202409-18Tanggal pengiriman\nPerdaganganTelah diverifikasi sebagian\nPembatasan perangkat baru telah diverifikasi di Halaman Bantuan\n\nDokumentasi dukungan resmi Steam menegaskan adanya pembatasan perdagangan harian (7-) saat masuk dari perangkat baru yang belum diotorisasi setidaknya selama 7 hari. Meskipun tanggal peluncuran tepatnya pada 18, 2024, tidak dicatat sebagai tonggak perubahan (changelog milestone), fitur tersebut telah didokumentasikan secara lengkap.\n\nSteam Dukungan — Pembatasan Perdagangan dan Pasar ↗\nEntri asli & tautan yang dikirimkan\n\nPembatasan Perdagangan untuk Login Perangkat Baru\n\nPeriksa kode sumber yang dikirimkan ↗\n202402-14Tanggal pengiriman\nKomunitasTelah diverifikasi sebagian\nMasa tunggu perubahan nama telah diterapkan di 2024\n\nCatatan komunitas dan pengembang menegaskan bahwa pada awal 2024, Valve, telah diberlakukan masa tunggu transaksi selama 2-to-4 jam—tanpa pengumuman sebelumnya—segera setelah perubahan nama profil, guna mengurangi penipuan peniruan identitas yang terjadi secara cepat. Karena Valve tidak menerbitkan siaran pers resmi, catatan perubahan klien, atau artikel dukungan terkait pembatasan ini, tanggal 14 yang diajukan pada bulan Februari tersebut tidak memiliki verifikasi resmi; panduan Steam Workshop berfungsi sebagai bukti pendukung tidak langsung dari komunitas, bukan sebagai dokumentasi resmi Valve.\n\nSteam Panduan Lokakarya (pembuktian tidak langsung) — Rincian pembatasan perubahan nama ↗\nEntri asli & tautan yang dikirimkan\n\nPenundaan Perubahan Nama Profil / Avatar\n\nPeriksa kode sumber yang dikirimkan ↗\n202312-04Tanggal verifikasi\nAPIAcara & tanggal yang telah diverifikasi\nPembuatan kunci memerlukan konfirmasi melalui ponsel\n\nPenerapan konfirmasi wajib melalui aplikasi seluler Steam Guard untuk pembuatan kunci Web API telah dipastikan terjadi pada akhir 2023, sebagaimana didokumentasikan oleh pustaka pengembang pihak ketiga. Tanggal pasti pada Desember 4, 2023, menandai periode peluncuran yang teramati di kalangan komunitas pengembang.\n\nDokumentasi Pengelola — Maret 2024 ↗diarsipkan 2026-09-24 ↗\nEntri asli & tautan yang dikirimkan\n\nKonfirmasi Melalui Ponsel untuk Kunci API\n\nPeriksa kode sumber yang dikirimkan ↗\n202310-24Tanggal verifikasi\nPengembangAcara & tanggal yang telah diverifikasi\nKetentuan Wajib 2FA untuk peluncuran build game secara langsung mulai berlaku\n\nPengumuman resmi Valve mengenai Steamworks pada 1 Oktober 10, 2023, menegaskan bahwa mulai 24, 2023,, setiap akun yang mengaktifkan build di cabang default aplikasi yang telah dirilis harus mengotorisasi perubahan tersebut melalui SMS atau aplikasi seluler Steam. Perubahan ini secara langsung memperbarui halaman web SetAppBuildLive API.\n\nSteamworks — Peningkatan keamanan dalam pengelolaan build dan pengguna ↗diarsipkan 2025-12-03 ↗\nEntri asli & tautan yang dikirimkan\n\nSMS MFA untuk Publikasi Rilis Game\n\nPeriksa kode sumber yang dikirimkan ↗\n202307-12Tanggal pengiriman\nKomunitasTelah diverifikasi sebagian\nPeringatan konten dalam biografi khusus yang diperhatikan oleh komunitas\n\nSteam Laporan dari komunitas yang dimulai pada bulan Juli 2023 menunjukkan bahwa deskripsi profil kustom yang berisi tautan eksternal atau kata-kata pemicu mulai menampilkan peringatan konten otomatis. Tanggal pengiriman pada 7 Juli 12, 2023, sejalan dengan gelombang awal laporan pengguna di forum komunitas Steam.\n\nSteam Forum Komunitas — Laporan Peringatan Konten Biografi ↗\nEntri asli & tautan yang dikirimkan\n\nPeringatan Terkait Konten Biografi Khusus\n\nPeriksa kode sumber yang dikirimkan ↗\n202301-25Tanggal pengiriman\nKomunitasTelah diverifikasi sebagian\nPenyaringan tautan profil dan masa tunggu pengeditan sedang aktif\n\nDokumentasi dukungan resmi Steam menegaskan bahwa tautan dalam biografi kustom disaring, dan perubahan nama atau avatar yang menyinggung dapat memicu larangan mengedit. Meskipun penerapan resmi masa tunggu satu jam 4-pada 1 Januari 25, 2023, menandai dimulainya kebijakan ini, mekanisme penyaringan tautan itu sendiri sudah sepenuhnya aktif sebagaimana dijelaskan di halaman bantuan yang telah diajukan.\n\nSteam Bantuan — Batasan Nama Profil dan Avatar ↗\nEntri asli & tautan yang dikirimkan\n\nProfil TAUTAN TELAH DIHAPUS / Waktu Tunggu\n\nPeriksa kode sumber yang dikirimkan ↗\n202210-24Tanggal verifikasi\nOtentikasiAcara & tanggal yang telah diverifikasi\nSteam Transisi klien ke token penyegaran dan token akses OAuth\n\nPembaruan utama klien dan aplikasi seluler Valve pada bulan Oktober 2022 telah melakukan perombakan menyeluruh terhadap sistem otentikasi Steam. Struktur cookie sesi lama digantikan dengan token akses dan token penyegaran berbasis OAuth, serta diperkenalkan daftar perangkat yang diotorisasi dan aktif untuk memungkinkan pencabutan sesi aktif secara manual.\n\nValve — Pembaruan Aplikasi Seluler Steam dan Perombakan Sistem Otentikasi ↗\nEntri asli & tautan yang dikirimkan\n\nSteam Perombakan Proses Masuk / Pemotongan Cookie\n\nLihat PengumumValve ↗\n202210-12Tanggal verifikasi\nOtentikasiAcara & tanggal yang telah diverifikasi\nPendaftaran melalui QR dan pengelolaan perangkat yang terotorisasi\n\nPengumuman Valve pada bulan Oktober mengenai \"12\" menjelaskan proses masuk menggunakan kode QR, persetujuan atau penolakan akses masuk, serta daftar perangkat yang dapat mencabut akses ke akun.\n\nValve — Aplikasi Seluler “Steam” yang telah diperbarui kini sudah tersedia ↗\nEntri asli & tautan yang dikirimkan\n\nSteam Aplikasi Seluler 3.0 / Masuk dengan QR\n\nPeriksa kode sumber yang dikirimkan ↗\n202205-10Tanggal pengiriman\nAPITelah diverifikasi sebagian\nTitik akhir pembatalan transaksi telah dihapus dari daftar publik API\n\nCatatan pengembang menegaskan bahwa pada bulan Mei 2022, Valve secara diam-diam menghapus titik akhir pengelolaan perdagangan seperti IEconService/CancelTradeOffer dan DeclineTradeOffer dari Web API (terdokumentasi di node-steam-tradeoffer-manager #325). Meskipun metode-metode tersebut tetap berfungsi dalam protokol klien privat, tanggal 10, 2022, menandai penghapusan yang teramati dari API Web publik untuk memerangi panel penipuan.\n\nDiskusi Pengembang — Masalah #325 (Fitur CancelTradeOffer telah dihapus) ↗· Situs Web Steamworks API — Dokumentasi IEconService ↗\nEntri asli & tautan yang dikirimkan\n\nPenghapusan Titik Akhir Pembatalan Transaksi\n\nLihat masalah node-steam-tradeoffer-manager #325 ↗\n202005-25Tanggal verifikasi\nPerdaganganAcara & tanggal yang telah diverifikasi\nItem Dota2kini memiliki masa tunggu perdagangan selama tujuh hari\n\nPada tanggal 25, 2020, bersamaan dengan peluncuran Battle Pass The International 10 (blog.dota2.com/2020/05/the-international-10-battle-pass/), Valve memberlakukan pembatasan perdagangan harian 7-untuk item Dota 2, sesuai dengan kebijakan 2018 Counter-Strike. Pembatasan ini berlaku untuk semua item yang diperdagangkan dan pembelian di Market.\n\nKomunitas Dota2 — Fitur Trade Lock dan Pembaruan Klien TI10 ↗\nEntri asli & tautan yang dikirimkan\n\nDota 2 / 7-: Penguncian Perdagangan Harian\n\nPeriksa kode sumber yang dikirimkan ↗\n201803-29Tanggal verifikasi\nPerdaganganAcara & tanggal yang telah diverifikasi\nItem CS:GO yang ditukar akan dikenakan masa tunggu selama tujuh hari\n\nCatatan rilis resmi tersebut mengonfirmasi tanggal dan batasan tersebut. URL yang disertakan mengarah ke pembaruan peta di 2013; sedangkan URL catatan rilis yang sesuai berakhiran 20309.\n\nValve — Catatan Rilis untuk 3/29/2018 ↗\nEntri asli & tautan yang dikirimkan\n\nCS:GO / 7-Penguncian Perdagangan Harian\n\nPeriksa kode sumber yang dikirimkan ↗ diarsipkan 2025-02-26 ↗\n\nIkuti bukti yang ada. Periksa sumbernya.\n\nKembali ke penyelidikan ↗",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Lintasan Sejarah Keamanan — 2018 hingga 2026"
          },
          {
            "level": 2,
            "id": null,
            "text": "Urutan waktu"
          },
          {
            "level": 2,
            "id": null,
            "text": "Peringatan pesan mencurigakan di obrolan grup"
          },
          {
            "level": 2,
            "id": null,
            "text": "Izin terperinci & daftar putih IP untuk Kunci Penerbit (pengumuman Valve)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Transaksi CS2 memasuki jendela pembalikan selama tujuh hari"
          },
          {
            "level": 2,
            "id": null,
            "text": "Valve menerbitkan peringatan keamanan akun terkait kebocoran SMS"
          },
          {
            "level": 2,
            "id": null,
            "text": "Tujuh hari sebelum penjualan kembali atau pemasaran ulang"
          },
          {
            "level": 2,
            "id": null,
            "text": "Pembatasan perangkat baru telah diverifikasi di Halaman Bantuan"
          },
          {
            "level": 2,
            "id": null,
            "text": "Masa tunggu perubahan nama telah diterapkan di 2024"
          },
          {
            "level": 2,
            "id": null,
            "text": "Pembuatan kunci memerlukan konfirmasi melalui ponsel"
          },
          {
            "level": 2,
            "id": null,
            "text": "Ketentuan Wajib 2FA untuk peluncuran build game secara langsung mulai berlaku"
          },
          {
            "level": 2,
            "id": null,
            "text": "Peringatan konten dalam biografi khusus yang diperhatikan oleh komunitas"
          },
          {
            "level": 2,
            "id": null,
            "text": "Penyaringan tautan profil dan masa tunggu pengeditan sedang aktif"
          },
          {
            "level": 2,
            "id": null,
            "text": "Steam Transisi klien ke token penyegaran dan token akses OAuth"
          },
          {
            "level": 2,
            "id": null,
            "text": "Pendaftaran melalui QR dan pengelolaan perangkat yang terotorisasi"
          },
          {
            "level": 2,
            "id": null,
            "text": "Titik akhir pembatalan transaksi telah dihapus dari daftar publik API"
          },
          {
            "level": 2,
            "id": null,
            "text": "Item Dota2kini memiliki masa tunggu perdagangan selama tujuh hari"
          },
          {
            "level": 2,
            "id": null,
            "text": "Item CS:GO yang ditukar akan dikenakan masa tunggu selama tujuh hari"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/id/#briefing-heading",
          "https://steamcommunity.com/groups/SteamClientBeta?l=english",
          "http://web.archive.org/web/20260313235409/https://steamcommunity.com/groups/SteamClientBeta?l=english",
          "https://store.steampowered.com/news/posts/?enddate=1788390000",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/493839547938902179",
          "https://partner.steamgames.com/doc/webapi_overview/auth",
          "https://csmarketcap.com/blog/market-insights/from-boom-to-bust-cs2s-trade-protection-impact",
          "https://skinvault.gg/blog/cs2-trade-protection-explained/",
          "https://skin.land/blog/steam-changes-cs2-trade-ban-logic-timing/",
          "https://store.steampowered.com/news/posts/?appids=730&amp;enddate=1753924057&amp;feed=steam_announce%2F1000",
          "https://help.steampowered.com/faqs/view/3041-A87A-E5F6-B6AC",
          "https://store.steampowered.com/news/posts/?enddate=1747349559",
          "https://steamcommunity.com/ogg/593110/announcements/detail/533224478739530146",
          "https://store.steampowered.com/news/posts/?appids=730&amp;enddate=1728000977&amp;feed=steam_community_announcements",
          "https://steamcommunity.com/games/CSGO/announcements/detail/4447966961421256740",
          "https://help.steampowered.com/faqs/view/7F77-9E92-31E0-6B8E",
          "https://steamcommunity.com/sharedfiles/filedetails/?id=2926756889",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "http://web.archive.org/web/20260924181824/https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "https://steamcommunity.com/dev/apikey",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3749866608167579206",
          "http://web.archive.org/web/20251203174259/https://steamcommunity.com/groups/steamworks/announcements/detail/3749866608167579206",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3734103130194459461",
          "https://steamcommunity.com/discussions/forum/1/3807266184852932971/",
          "https://help.steampowered.com/faqs/view/225C-C51E-B8F0-55B2",
          "https://store.steampowered.com/news/group/4/view/3314112260640237775",
          "https://store.steampowered.com/news/posts/?appgroupname=Keep+in+touch&amp;enddate=1666122699&amp;feed=steam_blog",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/issues/325",
          "https://partner.steamgames.com/doc/webapi/IEconService",
          "https://steamcommunity.com/app/570/announcements/",
          "https://blog.dota2.com/2020/05/trading-cooldown/",
          "https://blog.counter-strike.net/2018/03/20309/",
          "https://blog.counter-strike.net/index.php/2018/03/20308/",
          "http://web.archive.org/web/20250226114333/https://blog.counter-strike.net/index.php/2018/03/20308/",
          "https://phishdestroy.io/steam_dossier/id/#vulnerability-profile"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/id/security_timeline.content.json",
      "export_json_sha256": "05a8173065155e8f7a2735d70c2a6d08c524d944a5e01627c33fde02dc1328a1"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "id/skin_atlas.html",
      "language": "id",
      "title": "Atlas tentang hal-hal yang tidak dapat dibawa oleh \"Steam\" — Laporan \"Steam\"",
      "source_url": "https://phishdestroy.io/steam_dossier/id/skin_atlas",
      "source_html_sha256": "eb749b57a1fa827e1f297d8d2cc30eb3f6e19fc83ae125ea6e4b45cf1ecc4d8e",
      "exported_at": "2026-09-29T00:22:34.877Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "gallery",
            "source": "https://phishdestroy.io/steam_dossier/id/skin_atlas#gallery"
          }
        ],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "skin_atlas.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/id/skin_atlas.pdf?v=print-20260929-v5",
        "sha256": "ac26f5186a0344ef7b84d76e83d46d25abe801f554342622db3dbf15b6ad2c29",
        "bytes": 182527,
        "pages": 14
      },
      "integrity": {
        "signed_object": "skin_atlas.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "skin_atlas.content.json.asc",
        "digest_file": "skin_atlas.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify skin_atlas.content.json.asc skin_atlas.content.json",
          "sha256sum -c skin_atlas.content.json.sha256"
        ]
      },
      "content": {
        "text": "LAMPIRAN IV-B / TANGGA HARGA / 2026-09-23\nAtlas Skala Harga Skin — Jurang Likuiditas\n\nTempat perhentian Valve di pasar di mana uang itu berasal.\n\nAPA YANG DIBUKTIKAN OLEH BAGIAN INI\n\nAtlas visual ini menganalisis kategori barang di 30,266 di lima katalog marketplace, dengan mengukur cakupan pasar di atas dan di bawah ambang batas pencantuman Valve. Di bawah batas $1,800, Steam menampung 95.3% kategori aktif; tepat di atasnya, cakupan resmi menyusut menjadi 1.9% (dengan cakupan 0.0% di seluruh aset yang telah dikonfirmasi). Hal ini menunjukkan adanya jurang likuiditas struktural yang tiba-tiba, di mana Valve mendelegasikan penemuan transaksi bernilai tinggi kepada platform eksternal sambil tetap mempertahankan kendali penuh atas penyimpanan aset yang mendasarinya.\n\n← Kembali ke Ringkasan Eksekutif\n\nSetiap barang CS2 yang memiliki harga aktual di lima platform pasar ditempatkan dalam rentang harga berdasarkan harga jual termurahnya, dan setiap rentang tersebut dievaluasi berdasarkan satu hal: berapa besar pangsa pasar yang masih dipegang oleh Community Market milik Valve. Di bawah batas jumlah daftar barang di Valve, jawabannya adalah 95.3%. Di atasnya, jawabannya adalah 1.9%. Penurunan tersebut tidak terjadi secara bertahap dan tidak terjadi di titik di mana permintaan menurun — penurunan itu terjadi tepat sesuai dengan aturan yang telah ditetapkan. Dari 248 kategori barang yang harganya di atas batas atas yang ditetapkan secara independen oleh dua atau lebih platform pasar, 100.0% sama sekali tidak memiliki Steam daftar produk.\n\nLihat tebingnya ↓Buka galeri produk \"419\"Metode dan batasan\n30,266kategori barang yang diukur\n95.3%dari barang-barang di bawah batas yang dijual oleh Steam\n1.9%dari barang-barang yang harganya melebihi batas maksimum yang dijual di Steam\n$78.6Mnilai batas bawah himpunan yang terverifikasi\n01 / pengukuran\nAturan itu berlaku secara mutlak, bukan atas permintaan\n\nSetiap kategori barang di 30,266 di bawah ini dikelompokkan ke dalam suatu rentang berdasarkan termurah Pertanyaan langsung di BUFF163, CSFloat, Skinport, YouPin 898, dan C5Game; hanya barang yang tercantum di dua atau lebih platform tersebut yang dihitung, sehingga tidak ada satu pun daftar yang berlebihan yang dapat “menciptakan” anggota band. Panel atas menunjukkan pangsa pasar masing-masing band yang masih dipegang oleh pasar Valve sendiri.\n\nPangsa masing-masing kisaran harga yang ditawarkan di Pasar Komunitas Steam\nbagian atas: cakupan uap · bagian bawah: jumlah item per rentang, skala logaritmik\n0%\n25%\n50%\n75%\n100%\n100%\n96.9%\n95.9%\n97.3%\n91.1%\n76.8%\n14.5%\n2.9%\n1.5%\n0%\n0%\n0%\n4,632\n1¢–10¢\n7,152\n10¢–$1\n8,568\n$1–10\n5,941\n$10–100\n2,329\n$100–300\n1,292\n$300–1k\n193\n$1k–1.8k\n70\n$1.8k–3k\n67\n$3k–10k\n18\n$10k–30k\n3\n$30k–100k\n1\n$100k+\nitems\nlog\nVALVE’S LISTING CAP\nsama dengan atau di bawah batas pencatatan yang ditetapkan oleh Valvedi atas batas — aturan Valve melarang pencatatan tersebutkategori barang dalam grup tersebut\n\n“Cakupan” berarti pada saat data diambil, terdapat permintaan langsung di Steam untuk kategori tersebut. Panel bawah menggunakan skala logaritmik karena harga-harga dalam katalog ini sangat murah: jika dibaca secara linier, setiap rentang harga di atas $300akan terpadatkan ke garis dasar.\n\nApa yang tidak mungkin berdasarkan bentuknya\n\nJika barang-barang mahal sekadar tidak diminati, tingkat permintaan akan menurun secara bertahap seiring kenaikan harga. Namun, hal itu tidak terjadi. Tingkat permintaan tetap stabil pada angka 76.8% di rentang harga $300–$1k, lalu anjlok ke 14.5% di rentang harga tepat di bawah batas atas dan 2.9% di rentang harga tepat di atasnya. Efek permintaan tidak mengetahui di mana Valve menetapkan batas atasnya. Aturanlah yang menentukan.\n\nKisaran harga\tKategori barang\tDengan sesi tanya jawab langsung di Steam\tSteam cakupan\tDaftar salinan yang tercantum di Steam\n1¢–10¢\t4,632\t4,632\t100%\t8,223,227\n10¢–$1\t7,152\t6,931\t96.9%\t5,488,315\n$1–10\t8,568\t8,213\t95.9%\t3,939,538\n$10–100\t5,941\t5,780\t97.3%\t1,328,255\n$100–300\t2,329\t2,121\t91.1%\t364,466\n$300–1k\t1,292\t992\t76.8%\t187,504\n$1k–1.8k\t193\t28\t14.5%\t40,281\n$1.8k–3k\t70\t2\t2.9%\t9,592\n$3k–10k\t67\t1\t1.5%\t6,706\n$10k–30k\t18\t0\t0%\t1,366\n$30k–100k\t3\t0\t0%\t21\n$100k+\t1\t0\t0%\t2\n\nVarian pola dan fase tidak dimasukkan dalam daftar ini: Steam tidak mencantumkan tingkatan blue-gem atau fase Ruby sebagai entri pasar tersendiri, sehingga jika keduanya dihitung, cakupan Steam akan terlihat lebih kecil dari yang sebenarnya. Jika diukur tanpa persyaratan dua pasar, tangga yang sama menunjukkan angka 79.1% di bawah batas atas dan 6.5% di atasnya untuk 37,204 item — selisih yang lebih mencolok, yang didasarkan pada bukti yang lebih lemah, itulah sebabnya angka tersebut tidak dikutip.\n\n02 / penilaian berdasarkan bukti\nHarga yang diminta bukanlah harga\n\nSiapa pun bisa menawarkan P2000 seharga sepuluh juta yuan. Sebelum angka di halaman ini digunakan untuk tujuan apa pun, angka tersebut dinilai berdasarkan berapa banyak platform perdagangan yang secara independen menetapkan harga barang tersebut di atas batas atas dan seberapa rapat rentang harga tersebut. Hanya peringkat A dan B yang dicantumkan — baik di sini maupun di bagian lain dalam dokumen ini.\n\nA  Tiga rak atau lebih sama\n\nTiga atau lebih platform jual beli menawarkan harga barang tersebut di atas batas atas, dan harga mediannya berada dalam kisaran 25% dari harga termurah. 197 kategori, 18,218 eksemplar, $76,585,587.\n\nTidak hadir dalam acara “Steam”: 100.0%.\n\nB  Kedua rak tersebut sama\n\nDua pasar sepakat pada harga di atas batas atas, atau tiga pasar sepakat pada harga yang selisihnya tidak terlalu besar. 51 kategori, 176 eksemplar, $2,038,814.\n\nTidak hadir dalam acara “Steam”: 100.0%.\n\nC  Satu rak — belum pernah dipakai\n\nHanya ada satu bursa yang mencatatkan harga penawaran di atas batas atas. 171 kategori, salinan \"247\". Ditampilkan di galeri demi kelengkapan dan tidak dimasukkan dalam perhitungan total apa pun di halaman ini.\n\nIni adalah permintaan penawaran harga, bukan bukti harga.\n\nBerapa biaya yang dikeluarkan untuk koreksi ini, dan apa yang diperoleh darinya\n\nDengan menghapus peringkat C, kategori “171” dan $3,825,125” pun hilang dari judul. Yang tersisa adalah pernyataan yang lebih ringkas dan jauh lebih sulit untuk dibantah: 248 kategori, 18,394 daftar salinan, $78,624,401,, dan 100.0% di antaranya — semuanya — tidak tersedia di pasar Valve. Baris-baris kelas C itulah yang menyebabkan angka tersebut berubah; baris-baris tersebut ditampilkan, bukan disembunyikan.\n\nDaftar yang disisihkan sebagai artefak\n\nSetiap penawaran yang nilainya lebih dari tiga kali lipat harga jual termurah untuk barang yang sama akan disisihkan. Jika dikonversi berdasarkan nilai tukar yang tersirat dalam data itu sendiri, sebagian besar angka tersebut merupakan angka bulat dalam CNY — yang menandakan adanya angka sementara atau batas atas platform, bukan penawaran sesungguhnya. Karena setiap total di halaman ini menggunakan termurah Perlu dicatat, tak satu pun dari tokoh-tokoh ini pernah memanipulasi angka; mereka dikecualikan agar tak satu pun dari mereka dapat dijadikan judul berita.\n\nBarang\tHarga terendah untuk permintaan langsung\tSisihkan\nSouvenir P2000 | Wicked Sick (Minimal Wear)\t$148,954\t$1,489,543\n★ Specialist Gloves | Crimson Kimono (Minimal Wear) | Phase 1\t$37,239\t$119,163\nSouvenir USP-S | Printstream (Factory New)\t$2,000\t$59,582\n★ Bowie Knife | Crimson Web (Factory New)\t$2,957\t$43,030\n★ Karambit | Marble Fade (Factory New) | 1st\t$11,916\t$38,874\nSticker | Ninjas in Pyjamas (Holo) | Katowice 2014\t$5,000\t$31,748\nSouvenir AWP | Dragon Lore (Battle-Scarred)\t$4,225\t$29,157\n★ Karambit | Doppler (Minimal Wear) | Ruby\t$7,122\t$27,273\nSemua kategori \"419\", beserta objek yang dimaksud oleh masing-masing harga\n\nSumber: https://phishdestroy.io/steam_dossier/id/skin_atlas#gallery\n\n04 / ke mana sebenarnya benda itu pergi\nRak-rak yang memajang barang-barang yang tidak akan dipajang oleh Steam\n\nDaftar yang sama, dikelompokkan berdasarkan pasar tempat barang-barang tersebut dijual. Ini adalah jumlah lokasi di mana barang-barang tersebut tersedia terdaftar, yang berbeda dengan tempat di mana barang-barang tersebut dimiliki dan di sini tidak diartikan demikian.\n\nNilai terendah dari daftar produk yang harganya melebihi batas atas, berdasarkan platform jual beli\nharga penawaran terendah x eksemplar yang tercantum di rak itu\nYouPin 898\n$22,720,252\nBUFF163\n$22,022,606\nC5Game\n$12,560,543\nCSFloat\n$10,871,845\nSkinport\n$1,385,060\n\nYurisdiksi, sesuai urutan di atas: YouPin 898 — Tiongkok · BUFF163 — Tiongkok · C5Game — Tiongkok · CSFloat — Amerika Serikat · Skinport — Jerman / Malta. Barang fisik yang sama dapat terdaftar di lebih dari satu rak ini, sehingga angka-angka ini tidak boleh dijumlahkan dengan total pasar lainnya.\n\nNilai dasar berdasarkan tingkat harga\nbagaimana dana tersebut dialokasikan melebihi batas atas\n$1.8k-3k\n$9,842,391\n$3k-10k\n$36,787,269\n$10k-50k\n$20,038,749\nover $50k\n$2,891,897\n05 / kelangkaan yang bisa dihitung\nSeberapa terbatasnya pasokan itu sebenarnya\n\nSetiap item CS2 memiliki nilai kelangkaan, dan platform pasar tersebut mempublikasikan berapa banyak salinan yang terdapat di setiap rentang nilai tersebut. Hal ini mengubah kata sifat “langka” menjadi angka — dan angka itulah yang menjelaskan mengapa satu akun yang diretas saja sudah sepadan dengan upaya penggunaan perangkat phishing yang dirancang khusus.\n\nAWP | Kisah Naga\n150 terdaftar · mulai dari $11,350\n0.00–0.01\n29 · $14,730\n0.01–0.02\n54 · $11,618\n0.02–0.03\n26 · $11,350\n0.03–0.04\n25 · $11,618\n0.04–0.07\n16 · $11,585\n\nAWP | Dragon Lore (Baru dari Pabrik)\n\nM4A4 | Howl\n105 terdaftar · mulai dari $6,628\n0.00–0.01\n11 · $10,725\n0.01–0.02\n14 · $8,088\n0.02–0.03\n11 · $7,580\n0.03–0.04\n19 · $6,703\n0.04–0.07\n50 · $6,628\n\nM4A4 | Howl (Baru dari Pabrik)\n\nAK-47 | Wild Lotus\n113 terdaftar · mulai dari $14,373\n0.00–0.01\n25 · $22,343\n0.01–0.02\n11 · $19,364\n0.02–0.03\n3 · $19,645\n0.03–0.04\n15 · $15,044\n0.04–0.07\n59 · $14,373\n\nAK-47| Wild Lotus (Baru dari Pabrik)\n\nAWP | Gungnir\n173 terdaftar · mulai dari $11,618\n0.00–0.01\n28 · $17,875\n0.01–0.02\n21 · $13,600\n0.02–0.03\n32 · $12,065\n0.03–0.04\n29 · $11,735\n0.04–0.07\n63 · $11,618\n\nAWP | Gungnir (Baru dari Pabrik)\n\nAK-47 | Ular Api\n278 terdaftar · mulai dari $663\n0.15–0.18\n87 · $730\n0.18–0.21\n49 · $712\n0.21–0.24\n52 · $703\n0.24–0.27\n18 · $715\n0.27–0.38\n72 · $663\n\nAK-47 | Fire Serpent (Telah Diuji di Lapangan)\n\nCase Hardened (semua tingkatan / permata biru)\n76 terdaftar · mulai dari $1,638\n0.07–0.08\n1 · $2,516\n0.08–0.09\n4 · $2,482\n0.09–0.10\n6 · $3,856\n0.10–0.11\n7 · $2,797\n0.11–0.15\n58 · $1,638\n\nAK-47 | Permukaan yang Diperkeras (Keausan Minimal) | Tingkat1\n\nPita harga merupakan kelompok-kelompok likuiditas di pasar itu sendiri; hanya pita harga yang memiliki setidaknya satu penawaran aktif yang ditampilkan. Harga di samping setiap batang adalah harga penawaran aktif terendah dalam pita harga tersebut, sehingga premi yang melekat pada likuiditas rendah dapat langsung dilihat, bukan hanya dinyatakan.\n\n06 / gerakan, diukur dari Steam\nApa yang sebenarnya diwujudkan oleh rak-rak dari pihak ketiga\n\nValve Tidak ada riwayat yang dapat digunakan pada tingkatan ini, dan dokumen ini pun tidak mengklaim adanya riwayat tersebut. Skinport memang mempublikasikan data penjualan yang telah diselesaikan selama periode 24 jam terakhir, 7, 30 dan 90 hari terakhir, dan itulah keseluruhan rentang waktu yang tersedia di sini: harga realisasi median per jendela waktu terakhir, yang diindeks sedemikian rupa sehingga median harian 90-adalah 100. Tidak ada data dari Steam yang digunakan dalam kedua grafik tersebut.\n\nHarga realisasi median, periode terakhir\ndisesuaikan dengan median harian 90-· 6,758 item dengan 20+ penjualan\n85\n91\n97\n103\n100\n90d\n94\n30d\n90\n7d\n88\n24h\nTotal penjualan per hari\nbarang yang sama, jendela yang sama\n7,621\n9,653\n11,684\n13,716\n12,700\n90d\n11,894\n30d\n9,540\n7d\n8,637\n24h\n\nIni adalah dua grafik, bukan satu grafik dengan dua skala vertikal: indeks dan jumlah harian tidak memiliki satuan yang sama, dan menggambarkannya pada sumbu yang sama akan memicu perbandingan yang tidak valid. Jendela-jendela tersebut bersarang dan bersifat trailing — angka harian 90-mencakup angka jam 24-— sehingga ini bukanlah deret harian dan tidak boleh ditafsirkan sebagai deret harian. Hal yang didukung oleh data ini bersifat sempit dan dinyatakan dengan jelas: selama jendela trailing Skinport yang dipublikasikan, harga realisasi median berada di bawah median hariannya sendiri 90-, dan jumlah penjualan harian pun turun seiring dengan itu.\n\nSkinport penjualan yang terealisasi. Jendela-jendela tersebut bersifat bersarang dan bergerak mundur, sehingga setiap titik merupakan harga median yang terealisasi selama jendela bergerak mundur tersebut, yang diindeks berdasarkan median hari \"90-\". Ini bukanlah rangkaian data harian dan tidak melibatkan data \"Steam\".\n\n07 / dari apa bahan pembuatannya\nStiker-stiker yang sudah berumur enam belas tahun dan segenggam sarung tangan\n\nKategori di atas batas tersebut bukanlah gambaran umum dari pasar ini. Kategori tersebut berfokus pada beberapa barang langka dan beberapa koleksi, beberapa di antaranya sama sekali tidak dapat diperoleh lagi — dan itulah tepatnya alasan mengapa pasokan tidak dapat menyesuaikan diri dengan harga.\n\nKategori di atas batas, berdasarkan tingkat kelangkaan\njumlah kategori barang\nCovert\n321\nClassified\n39\nRestricted\n24\nContraband\n12\nMil-Spec Grade\n9\nConsumer Grade\n9\nIndustrial Grade\n5\nKategori di atas batas, berdasarkan koleksi\nsepuluh koleksi teratas\nThe St. Marc Collection\n13\nThe Cobblestone Collection\n13\nThe Norse Collection\n12\nThe Arms Deal Collection\n9\nThe Canals Collection\n7\nThe Gods and Monsters Collection\n6\nThe Revolution Collection\n4\nThe 2021 Train Collection\n4\nThe Rising Sun Collection\n4\nThe Chop Shop Collection\n4\n\nBerdasarkan kategori: skin 366, sticker 48, container 3, sticker_slab 2.\n\n08 / jumlah terbesar yang pernah dibayarkan oleh siapa pun\nKenaikan harga yang didukung oleh transaksi, bukan oleh pencatatan saham\n\nSetiap harga lain di halaman ini merupakan tanya — apa yang diinginkan penjual. Hal-hal tersebut adalah penjualan: nilai transaksi tertinggi yang telah diselesaikan Skinport yang tercatat untuk setiap barang, selama 90 hari terakhir. Ini adalah satu-satunya angka dalam dokumen ini yang benar-benar telah dibayarkan oleh seseorang, dan setiap baris tertaut ke platform pasar tersebut sehingga angka tersebut dapat diverifikasi langsung dari sumbernya, bukan melalui kami.\n\n21,216barang-barang yang penjualannya telah selesai dalam etalase\n106dijual pada harga yang sama dengan atau di atas batas harga penawaran yang ditetapkan oleh Valve\n$14,192penjualan tunggal tertinggi yang telah diselesaikan\n67/419kategori di atas batas dengan adanya penjualan yang tercatat\nTiga puluh transaksi penjualan tertinggi yang telah diselesaikan selama periode tersebut\nBarang\tPenjualan tertinggi\tHarga jual median\tPenjualan\tTawaran termurah saat ini\tSteam\tCoba lihat\nAWP | Gungnir (Factory New)\t$14,192\t$11,343\t5\t$11,490\tabsent\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Factory New)\t$12,387\t$12,387\t1\t$13,836\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Factory New)\t$11,779\t$11,063\t16\t$10,941\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Minimal Wear)\t$11,693\t$11,693\t1\t$9,946\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Minimal Wear)\t$10,437\t$10,437\t1\t$9,610\tabsent\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Blue Laminate (Minimal Wear)\t$9,772\t$37\t76\t$30\t$40\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Minimal Wear)\t$9,463\t$9,463\t1\t$9,500\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Minimal Wear)\t$9,104\t$9,026\t6\t$8,524\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Hedge Maze (Minimal Wear)\t$8,139\t$8,139\t1\t$6,819\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Field-Tested)\t$7,617\t$7,390\t4\t$7,194\tabsent\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Field-Tested)\t$7,615\t$7,615\t1\t$7,100\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Field-Tested)\t$7,149\t$7,006\t2\t$7,165\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Field-Tested)\t$6,711\t$6,194\t15\t$5,988\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Factory New)\t$6,679\t$6,613\t3\t$6,628\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Superconductor (Factory New)\t$6,084\t$6,084\t1\t$7,969\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Battle-Scarred)\t$5,750\t$5,413\t3\t$5,899\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Pandora's Box (Minimal Wear)\t$5,520\t$5,508\t3\t$4,998\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Vice (Factory New)\t$5,385\t$5,158\t2\t$5,700\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Minimal Wear)\t$5,342\t$4,989\t19\t$4,997\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Hedge Maze (Field-Tested)\t$5,334\t$4,862\t5\t$3,724\tabsent\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Vulcan (Factory New)\t$5,275\t$1,418\t12\t$1,280\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Well-Worn)\t$4,978\t$4,978\t1\t$4,942\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Well-Worn)\t$4,931\t$4,931\t1\t$5,445\tabsent\tSkinport CSFloat Steam\nAK-47 | Hydroponic (Factory New)\t$4,802\t$4,351\t2\t$3,648\tabsent\tSkinport CSFloat Steam\n★ Talon Knife | Case Hardened (Minimal Wear)\t$4,588\t$466\t16\t$442\t$630\tSkinport CSFloat Steam\nAWP | Medusa (Factory New)\t$4,484\t$4,484\t1\t$4,171\tabsent\tSkinport CSFloat Steam\n★ Specialist Gloves | Pillow Punchers (Factory New)\t$4,359\t$4,359\t1\t$4,302\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Pandora's Box (Field-Tested)\t$4,359\t$3,666\t11\t$3,245\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Field-Tested)\t$4,289\t$4,225\t8\t$4,022\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Battle-Scarred)\t$4,124\t$4,124\t1\t$4,279\tabsent\tSkinport CSFloat Steam\nBarang yang sama, periode \"90\" yang sama, namun harganya sangat berbeda\n\nTerbatas pada barang-barang dengan nilai median $100 dan setidaknya lima transaksi yang telah diselesaikan, karena pada skin murah, satu transaksi yang tidak wajar saja sudah cukup untuk mengacaukan rasio tersebut. Yang tersisa didominasi oleh Pengerasan Permukaan hasil akhir, di mana pola menentukan harga dan pasar mengelompokkan setiap pola di bawah satu nama — mekanisme yang sama yang diukur dengan float pada bagian 05.\n\nBarang\tNilai tertinggi vs nilai median\tPenjualan tertinggi\tHarga jual median\tPenjualan\tCoba lihat\n★ Talon Knife | Case Hardened (Minimal Wear)\t+884%\t$4,588\t$466\t16\tSkinport CSFloat Steam\nDesert Eagle | Cobalt Disruption (Factory New)\t+859%\t$1,210\t$126\t115\tSkinport CSFloat Steam\nAWP | BOOM (Minimal Wear)\t+814%\t$1,232\t$135\t89\tSkinport CSFloat Steam\nAK-47 | Case Hardened (Well-Worn)\t+769%\t$1,720\t$198\t70\tSkinport CSFloat Steam\nAWP | Graphite (Factory New)\t+761%\t$1,469\t$171\t124\tSkinport CSFloat Steam\n★ Talon Knife | Case Hardened (Field-Tested)\t+509%\t$2,437\t$400\t48\tSkinport CSFloat Steam\n★ Kukri Knife | Case Hardened (Minimal Wear)\t+448%\t$723\t$132\t69\tSkinport CSFloat Steam\n★ Kukri Knife | Case Hardened (Field-Tested)\t+415%\t$549\t$106\t128\tSkinport CSFloat Steam\n★ Ursus Knife | Case Hardened (Minimal Wear)\t+371%\t$597\t$127\t12\tSkinport CSFloat Steam\nAK-47 | Case Hardened (Field-Tested)\t+369%\t$1,037\t$221\t125\tSkinport CSFloat Steam\nAK-47 | Red Laminate (Minimal Wear)\t+360%\t$552\t$120\t18\tSkinport CSFloat Steam\nAWP | Asiimov (Field-Tested)\t+351%\t$528\t$117\t439\tSkinport CSFloat Steam\nAK-47 | Vulcan (Field-Tested)\t+337%\t$865\t$198\t241\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Nightwish (Factory New)\t+322%\t$625\t$148\t31\tSkinport CSFloat Steam\nAWP | Lightning Strike (Factory New)\t+319%\t$2,065\t$493\t198\tSkinport CSFloat Steam\nStatTrak™ AWP | Redline (Minimal Wear)\t+312%\t$574\t$139\t24\tSkinport CSFloat Steam\nStatTrak™ AWP | Asiimov (Battle-Scarred)\t+287%\t$524\t$135\t37\tSkinport CSFloat Steam\nAK-47 | Redline (Minimal Wear)\t+277%\t$562\t$149\t112\tSkinport CSFloat Steam\nAWP | Crakow! (Factory New)\t+275%\t$379\t$101\t72\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Vulcan (Factory New)\t+272%\t$5,275\t$1,418\t12\tSkinport CSFloat Steam\n\nIni adalah harga tertinggi harian di 90-, BUKAN rekor tertinggi sepanjang masa, dan hanya mencakup SATU pasar. Tidak ada angka rekor tertinggi sepanjang masa yang disebutkan di mana pun dalam dokumen ini. Barang yang tidak memiliki catatan penjualan di Skinport sama sekali tidak tercantum dalam pameran ini, itulah sebabnya koleksi ini lebih kecil daripada hasil sensus.\n\nTautan verifikasi dibuat berdasarkan pengenal platform katalog itu sendiri. Tautan tersebut mengarah ke halaman produk di masing-masing pasar daring sehingga pembaca dapat membandingkan gambar tersebut dengan sumber aslinya, bukan dengan kami. Tautan keluar mencakup rel=\"nofollow\": itu hanyalah kutipan, bukan dukungan, dan beberapa di antara destinasi tersebut adalah platform perdagangan yang dikritik dalam penyelidikan ini.\n\n09 / asal-usul dan batasan\nDari mana asal hal ini dan apa yang tidak dapat ditunjukkannya\n\nSetiap angka pada halaman ini dihitung ulang berdasarkan dua berkas snapshot yang nilai hash-nya dipublikasikan bersamaan dengan angka-angka tersebut. Tidak ada satu pun informasi di sini yang disalin dari artikel situs lain.\n\nSumber dan akses\n\ncs2.sh API, GET /v1/prices/latest dan GET /v1/schema, tangkapan layar tunggal, diambil dari 2026-09-23T00:44:27.871388581Z, dengan harga dalam USD.\n\nData tersebut diperoleh melalui langganan komersial berbayar yang dimiliki oleh pemohon dari GDPR sebagaimana tercatat dalam arsip, sesuai dengan ketentuan yang ditetapkan oleh penyedia layanan. Tidak ada platform perdagangan yang diambil datanya, dan tidak ada kredensial dari platform perdagangan mana pun yang digunakan. Kunci peminta disimpan di luar repositori ini dan tidak muncul di file mana pun di sini.\n\nBagaimana suatu barang memenuhi syarat\n\nSetiap item dasar yang memiliki setidaknya satu penawaran aktif di BUFF, CSFloat, Skinport, YouPin, atau C5Game ditempatkan dalam rentang harga berdasarkan penawaran TERMURAH yang dimilikinya, sehingga rentang tersebut tidak pernah bergantung pada Steam. \"Steam coverage\" adalah persentase item dalam rentang tersebut yang memiliki penawaran aktif Steam pada saat data diambil. Varian pola dan fase dikecualikan dari tangga harga karena Steam tidak mencantumkannya secara terpisah; memasukkannya akan menyebabkan Steam terkesan lebih rendah dari yang sebenarnya. Render adalah gambar katalog untuk barang yang sama, yang disimpan secara lokal.\n\nRender dan hak cipta gambar. Render item katalog adalah gambar dari penyedia yang disajikan untuk `market_hash_name` yang sama dengan baris harga, disimpan secara lokal untuk tampilan offline dan IPFS. Render tersebut bukanlah karya PhishDestroy: semua gambar barang, logo, dan tangkapan layar tetap menjadi milik pemiliknya masing-masing (cs2.sh, CSFloat, Skinport, BUFF, YouPin, C5Game, Valve, dan lainnya). Gambar-gambar tersebut direproduksi semata-mata untuk tujuan identifikasi dan pelaporan demi kepentingan umum; tidak ada klaim kepemilikan atau lisensi yang diajukan.\n\nApa yang tidak dapat kami peroleh\n\nTingkat langganan yang digunakan hanya mencakup snapshot terkini. Titik akhir riwayat dan arsip tidak tersedia, dan Tidak ada rangkaian data historis yang disebutkan di mana pun pada halaman ini Selain data penjualan berbasis jendela bergerak, Skinport juga dipublikasikan di bagian 06.\n\nSatu tangkapan layar, bukan rangkaian data. Tidak adanya daftar di Steam pada saat tangkapan layar diambil bukanlah bukti bahwa suatu barang tidak akan pernah muncul di sana; hal itu merupakan kondisi rak yang terukur pada saat itu, dan untuk harga di atas batas atas, hal itu juga sesuai dengan aturan yang diterbitkan oleh Valve: Pasar Komunitas Valve secara eksplisit membatasi daftar barang hingga $1,800 per item (dengan saldo dompet Steam maksimum sebesar $2,000; lihat Steam Pertanyaan Umum (FAQ) Pasar Komunitas diarsipkan 2026-09-21 ↗ dan Steam Perjanjian Pelanggan § 3.C diarsipkan 2026-09-24 ↗).\n\nPenilaian\n\nHarga suatu barang selalu sama dengan harga penawaran terkini termurahnya, sehingga nilai yang sangat menyimpang (outlier) tidak akan pernah menaikkan total harga. Sistem penilaian menentukan baris mana saja yang boleh dimasukkan dalam kutipan harga. Setiap kutipan harga yang melebihi tiga kali lipat harga penawaran termurah untuk barang yang sama akan dikecualikan sebagai harga yang tidak valid. Peringkat A: tiga atau lebih pasar masih mencantumkan harga di atas batas atas dan median harganya berada dalam kisar25 persen dari harga penawaran terendah. Peringkat B: dua pasar setuju, atau tiga pasar setuju dengan selisih yang lebih longgar. Peringkat C: hanya satu penawaran—harga yang diminta, bukan harga pasar. Hanya peringkat A dan B yang dicantumkan di mana pun dalam dokumen ini.\n\nAturan nilai penyimpangan: harga penawaran > 3.0dikalikan dengan harga penawaran terendah untuk barang yang sama.\n\nMengapa angka-angka tersebut merupakan batas bawah\n\nUntuk setiap pasar, barang tersebut terendah Harga penawaran dikalikan dengan jumlah salinan yang tercantum dalam daftar rak. Setiap salinan lainnya di sana dihargai sama dengan atau di atas harga penawaran terendah tersebut, sehingga nilai yang sebenarnya tercantum lebih tinggi secara inheren, bukan berdasarkan perkiraan. Ini bukanlah penjualan, bukan arus kas, dan bukan penilaian terhadap ekonomi CS2.\n\nCoba periksa sendiri\n\nKumpulan data turunan yang menjadi dasar setiap grafik di halaman ini dipublikasikan secara lengkap: kumpulan data Atlas, layar penyortiran dan pemisahan benda asing, sensus yang mendasari dan daftar isi yang berisi nilai SHA-256, masing-masing untuk setiap snapshot mentah.\n\nKoreksi yang tercatat pada pembukaan pasar\n\nDraf awal dari daftar pelengkap tersebut diawali dengan Souvenir AK-47 | Point Disarray yang ditawarkan seharga $148,954 di salah satu platform e-commerce Tiongkok, sementara Steam menawarkannya seharga $119. Baris tersebut berstatus kelas C: hanya tersedia di satu rak, hanya satu eksemplar, dan tidak ada platform e-commerce lain yang menyetujui harga tersebut. Itu adalah harga penawaran, bukan harga pasti, dan telah diturunkan statusnya baik di sini maupun di halaman tersebut. Pemimpin yang terverifikasi adalah Sticker | Titan (Holo) | Katowice 2014 di $66,285, sebagaimana dikutip dari 4, pasar-pasar tersebut berjarak 5.2% satu sama lain — dan sama sekali tidak terdapat di Steam.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Atlas Skala Harga Skin — Jurang Likuiditas"
          },
          {
            "level": 2,
            "id": null,
            "text": "Aturan itu berlaku secara mutlak, bukan atas permintaan"
          },
          {
            "level": 3,
            "id": null,
            "text": "Apa yang tidak mungkin berdasarkan bentuknya"
          },
          {
            "level": 2,
            "id": null,
            "text": "Harga yang diminta bukanlah harga"
          },
          {
            "level": 3,
            "id": null,
            "text": "A  Tiga rak atau lebih sama"
          },
          {
            "level": 3,
            "id": null,
            "text": "B  Kedua rak tersebut sama"
          },
          {
            "level": 3,
            "id": null,
            "text": "C  Satu rak — belum pernah dipakai"
          },
          {
            "level": 3,
            "id": null,
            "text": "Berapa biaya yang dikeluarkan untuk koreksi ini, dan apa yang diperoleh darinya"
          },
          {
            "level": 3,
            "id": null,
            "text": "Daftar yang disisihkan sebagai artefak"
          },
          {
            "level": 2,
            "id": null,
            "text": "Semua kategori \"419\", beserta objek yang dimaksud oleh masing-masing harga"
          },
          {
            "level": 2,
            "id": null,
            "text": "Rak-rak yang memajang barang-barang yang tidak akan dipajang oleh Steam"
          },
          {
            "level": 2,
            "id": null,
            "text": "Seberapa terbatasnya pasokan itu sebenarnya"
          },
          {
            "level": 2,
            "id": null,
            "text": "Apa yang sebenarnya diwujudkan oleh rak-rak dari pihak ketiga"
          },
          {
            "level": 2,
            "id": null,
            "text": "Stiker-stiker yang sudah berumur enam belas tahun dan segenggam sarung tangan"
          },
          {
            "level": 2,
            "id": null,
            "text": "Kenaikan harga yang didukung oleh transaksi, bukan oleh pencatatan saham"
          },
          {
            "level": 3,
            "id": null,
            "text": "Tiga puluh transaksi penjualan tertinggi yang telah diselesaikan selama periode tersebut"
          },
          {
            "level": 3,
            "id": null,
            "text": "Barang yang sama, periode \"90\" yang sama, namun harganya sangat berbeda"
          },
          {
            "level": 2,
            "id": null,
            "text": "Dari mana asal hal ini dan apa yang tidak dapat ditunjukkannya"
          },
          {
            "level": 3,
            "id": null,
            "text": "Sumber dan akses"
          },
          {
            "level": 3,
            "id": null,
            "text": "Bagaimana suatu barang memenuhi syarat"
          },
          {
            "level": 3,
            "id": null,
            "text": "Apa yang tidak dapat kami peroleh"
          },
          {
            "level": 3,
            "id": null,
            "text": "Penilaian"
          },
          {
            "level": 3,
            "id": null,
            "text": "Mengapa angka-angka tersebut merupakan batas bawah"
          },
          {
            "level": 3,
            "id": null,
            "text": "Coba periksa sendiri"
          },
          {
            "level": 3,
            "id": null,
            "text": "Koreksi yang tercatat pada pembukaan pasar"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/id/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/id/skin_atlas#gallery",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://skinport.com/market?search=AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260924114457/https://store.steampowered.com/subscriber_agreement/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-atlas.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-artefact-screen.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-above-the-ceiling.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/id/skin_atlas.content.json",
      "export_json_sha256": "1a2164897362c20c90fdc662f1a73fac7c183753bbff1dc20279da435300e2db"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "id/social_graph.html",
      "language": "id",
      "title": "Ikuti jejak hubungan yang tercatat — Dokumen “Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/id/social_graph",
      "source_html_sha256": "1928570a943ca618c73e6994206196ed8153c01e52d06317a5c4db61cf42a4b1",
      "exported_at": "2026-09-29T00:22:34.846Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "social_graph.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/id/social_graph.pdf?v=print-20260929-v5",
        "sha256": "7e8dd612ecaedc5aa6da5521dfd244f6866d450a6c637b28c2dbd3c776a5e447",
        "bytes": 119350,
        "pages": 6
      },
      "integrity": {
        "signed_object": "social_graph.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "social_graph.content.json.asc",
        "digest_file": "social_graph.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify social_graph.content.json.asc social_graph.content.json",
          "sha256sum -c social_graph.content.json.sha256"
        ]
      },
      "content": {
        "text": "Ikuti jejaknya.Periksa setiap hubungan.\n\nCari profil. Pilih jenis hubungan. Ikuti tetangga langsungnya dalam catatan yang telah diambil. Alat penelitian: Sisi-sisi tersebut melambangkan hubungan publik, bukan bukti adanya kontak langsung, koordinasi pribadi, atau perilaku tidak pantas antara dua simpul mana pun. Tata letak simpul \"3,435-\" paling baik dipahami dengan menggunakan filter.\n\nJelajahi satu hubungan pada satu waktu\n\n💡 Klik dan seret simpul untuk mengatur ulang grafik. Arahkan kursor untuk melihat profil terperinci. Garis padat berwarna biru kehijauan = Persahabatan, garis putus-putus berwarna kuning kecokelatan = Komentar Bersama.\n\nJenis hubunganProfil dan tetangga terdekat\n\n3,435 profil · tautan yang direkam di 4,551\n\nCari dan pilih sebuah profil, atau klik sebuah simpul. Hanya tetangga langsung yang tercatat yang akan tetap ada. Sebuah tepi mencatat suatu hubungan; tepi tersebut tidak membentuk koordinasi pribadi.\n\nProfil dalam kumpulan data yang diperoleh\n\nTabel sumber lengkap: Unduh semua baris dari 3,435 (CSV). Tabel di bawah ini awalnya menampilkan baris-baris pertama 25; fitur pencarian dan paginasi mencakup seluruh kumpulan data.\n\n1–25 / 3,435 baris\nNama Persona\tSteamID64\tPrivasi\tStatus\tKeanggotaan Kelompok\tPersediaan Beku (USD)\tLokasi\nMahatma Gandhi\t76561198333721623\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tPH\nGalley//갤리🌠🌙\t76561198043416832\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tKP\n$Schlächter\t76561198860277343\tPUBLIC\tClean\tsteambans\t$0.00\tUnknown\n❄r3dsn0w000™❄ [Cristi]🎮\t76561197986767957\tPUBLIC\tClean\tCommunityLegends\t$0.00\tRO\n(2a03) Wolfy\t76561197991671851\tPUBLIC\tCommunity\tsr_public\t$0.00\tUS\nZloy2288\t76561198038578334\tPUBLIC\tClean\tsteambans\t$0.00\tBY\njessy\t76561198039125237\tPUBLIC\tCommunity, VAC (1x)\tCommunityLegends\t$0.00\tJP\nJithraRufure\t76561198071896910\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\n| Níllerdínho |\t76561198003487438\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tDK\nJones is back\t76561198023013026\tPRIVATE\tVAC (1x)\tsteambans\t$0.00\tUnknown\nUNEX | ★✠☠ MoH3st ☠✠\t76561198050763123\tPUBLIC\tClean\tsteambans\t$0.00\tDE\nTrojan\t76561198048457084\tPUBLIC\tClean\tCommunityLegends\t$0.00\tDE\n𝗠𝗮𝘆𝘂 ❤\t76561199377967696\tPUBLIC\tClean\tsr_public\t$0.00\tIS\nbig fucking idiot\t76561198871206397\tPUBLIC\tVAC (1x)\tsteambans\t$0.00\tUnknown\nSOFF Games\t76561198227129276\tPUBLIC\tClean\tcommunitymoderators\t$0.00\tRU\nThijminecraft02\t76561198253895669\tPUBLIC\tClean\tSteamIDcouk SArchive\t$0.00\tNL\nStatic-sama\t76561198289329793\tPUBLIC\tClean\tsteambans\t$0.00\tJP\n𝙸mmortal 𝚂targazer\t76561198142116760\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\nCommander Keen\t76561197987773287\tPUBLIC\tClean\tsteambans\t$0.00\tBE\nS1mX\t76561199648509165\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\nmixwell\t76561199276547472\tPUBLIC\tClean\tsr_public\t$0.00\tJP\nP90_GOD_YyEs™\t76561198285821942\tPUBLIC\tClean\tsteambans\t$0.00\tHK\nhewwo?\t76561199133807546\tPUBLIC\tVAC (1x)\tsteambans\t$0.00\tCH\n♕Kamikaze Atze♕\t76561198002700103\tPUBLIC\tClean\tsteambans\t$0.00\tDE\nPastica\t76561198154655970\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tDZ\nDaftar hubungan pertemanan yang tercatat\n\nTabel sumber lengkap: Unduh semua baris dari 4,299 (CSV). Tabel di bawah ini awalnya menampilkan baris-baris pertama 25; fitur pencarian dan paginasi mencakup seluruh kumpulan data.\n\n1–25 / 4,299 baris\nPengguna A\tArah\tPengguna B\tJenis Hubungan\nMahatma Gandhi\n76561198333721623\t↔\tDeskjet\n76561198272738437\tMutual Friends\nGalley//갤리🌠🌙\n76561198043416832\t↔\tomega\n76561197960274529\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tFisty\n76561198057301486\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tFaalagorn\n76561198001116101\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tMURK\n76561198036995672\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tÅρøᴛʜℯᴛȋᴄÅʟȋℯη ♛👽♛\n76561197984615267\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tsilatrak\n76561197999629462\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tBlack Blade\n76561198083368493\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tAvenger\n76561197978249317\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tRemtar\n76561198124322650\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tCato\n76561197961345984\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t✪ G λ M Ξ ®\n76561197994308495\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tclees42\n76561198030936806\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t𝓜ε𝔰𝔥 | AusLevels\n76561198108828539\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tSgtFopper™\n76561198002555892\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t❥Miss Bee\n76561198046958996\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tTesTy\n76561198032370068\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tskl_andrey\n76561198136881436\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t\"Exekutor\"\n76561198009583947\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tAraripe\n76561198103754372\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tsteve6678\n76561198053200093\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\ttrinner\n76561197970359081\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tSteph S.\n76561198025653291\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tKirito\n76561198154545657\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tDoc. todt\n76561197984492467\tMutual Friends\nTautan komentar yang telah direkam\n\nTabel sumber lengkap: Unduh semua baris dari 252 (CSV). Tabel di bawah ini awalnya menampilkan baris-baris pertama 25; fitur pencarian dan paginasi mencakup seluruh kumpulan data.\n\n1–25 / 252 baris\nPenulis\tArah\tProfil Sasaran\tTanggal\tTeks Komentar\nDeskjet\n76561198272738437\t→\tMahatma Gandhi\n76561198333721623\t16 September, 2021 @ 11:02:05 pm PDT\t\"𝑵𝒐𝒘 𝒊𝒇 𝑰 𝒇𝒖𝒄𝒌 𝒕𝒉𝒊𝒔 𝒎𝒐𝒅𝒆𝒍𝑨𝒏𝒅 𝒔𝒉𝒆 𝒋𝒖𝒔𝒕 𝒃𝒍𝒆𝒂𝒄𝒉𝒆𝒅 𝒉𝒆𝒓 𝒂𝒔𝒔𝒉𝒐𝒍𝒆𝑨𝒏𝒅 𝑰 𝒈𝒆𝒕 𝒃𝒍𝒆𝒂𝒄𝒉 𝒐𝒏 𝒎𝒚 𝑻-𝒔𝒉𝒊𝒓𝒕𝑰'𝒎𝒎𝒂 𝒇𝒆𝒆𝒍 𝒍𝒊𝒌𝒆 𝒂𝒏 𝒂𝒔𝒔𝒉𝒐𝒍𝒆\" - Nelson Mandela\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t22 November, 2021 @ 4:10:28 pm PDT\thttps://anige.horigiri.net/?cat=22\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t18 November, 2021 @ 12:45:26 am PDT\thttps://gamerch.com/umamusume/entry/250411\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t8 August, 2021 @ 4:13:25 am PDT\thttps://modoocode.com/304\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t6 February, 2021 @ 3:35:05 pm PDT\t▤ ∫︹- -ω⁾ ⁽︹▓▓︺\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t11 December, 2019 @ 1:50:53 am PDT\thttps://blog.naver.com/aksenwlddj12/221369410039\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t2 October, 2019 @ 7:11:59 am PDT\tǤαllєу║︎갤리..۩\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t9 April, 2019 @ 12:51:28 pm PDT\tExplosiveDamage(owner, from, maxrange, minrange, distmultiplier, dmgmultiplier, mindamage, typ, damagetype, ignore)\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 12:22:47 pm PDT\tinfo - sh_titles.lua\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 12:21:46 pm PDT\tlocal nibbas = 1344 init.lua\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 11:31:58 am PDT\thttp://foreign.aladin.co.kr/shop/wproduct.aspx?ItemId=123955531&start=slayer\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t3 April, 2019 @ 1:26:41 am PDT\tǤαllєу\nLei\n76561198982197954\t→\tJithraRufure\n76561198071896910\t29 December, 2024 @ 12:58:08 pm PDT\t+rep he knows how 2 rush B ￣ヘ￣\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t2 September, 2026 @ 5:16:55 am PDT\tlol\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t20 August, 2026 @ 6:11:03 am PDT\t?\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t25 July, 2026 @ 7:20:05 am PDT\thahahahaha\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t30 June, 2026 @ 12:52:42 pm PDT\twow\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t30 June, 2026 @ 12:41:32 pm PDT\txD\nvalorant enjoyer\n76561199112142402\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:26:30 pm PDT\toh no!!\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:26:11 pm PDT\toh no!!\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:22:22 pm PDT\tomg !!! they know my secret, omg!!!\nvalorant enjoyer\n76561199112142402\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:21:39 pm PDT\t+rep good ♥♥♥♥♥ player\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:20:50 pm PDT\tomg! u cant cheat on secure gaben servers, omg dont report me, they ban me for boosted omg\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 8:37:11 pm PDT\txD\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t28 June, 2026 @ 1:58:14 pm PDT\twow",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Ikuti jejaknya.Periksa setiap hubungan."
          },
          {
            "level": 2,
            "id": null,
            "text": "Jelajahi satu hubungan pada satu waktu"
          },
          {
            "level": 2,
            "id": null,
            "text": "Profil dalam kumpulan data yang diperoleh"
          },
          {
            "level": 2,
            "id": null,
            "text": "Daftar hubungan pertemanan yang tercatat"
          },
          {
            "level": 2,
            "id": null,
            "text": "Tautan komentar yang telah direkam"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-profiles.csv",
          "https://steamcommunity.com/profiles/76561198333721623",
          "https://steamcommunity.com/profiles/76561198043416832",
          "https://steamcommunity.com/profiles/76561198860277343",
          "https://steamcommunity.com/profiles/76561197986767957",
          "https://steamcommunity.com/profiles/76561197991671851",
          "https://steamcommunity.com/profiles/76561198038578334",
          "https://steamcommunity.com/profiles/76561198039125237",
          "https://steamcommunity.com/profiles/76561198071896910",
          "https://steamcommunity.com/profiles/76561198003487438",
          "https://steamcommunity.com/profiles/76561198023013026",
          "https://steamcommunity.com/profiles/76561198050763123",
          "https://steamcommunity.com/profiles/76561198048457084",
          "https://steamcommunity.com/profiles/76561199377967696",
          "https://steamcommunity.com/profiles/76561198871206397",
          "https://steamcommunity.com/profiles/76561198227129276",
          "https://steamcommunity.com/profiles/76561198253895669",
          "https://steamcommunity.com/profiles/76561198289329793",
          "https://steamcommunity.com/profiles/76561198142116760",
          "https://steamcommunity.com/profiles/76561197987773287",
          "https://steamcommunity.com/profiles/76561199648509165",
          "https://steamcommunity.com/profiles/76561199276547472",
          "https://steamcommunity.com/profiles/76561198285821942",
          "https://steamcommunity.com/profiles/76561199133807546",
          "https://steamcommunity.com/profiles/76561198002700103",
          "https://steamcommunity.com/profiles/76561198154655970",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-connections.csv",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-comments.csv"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/id/social_graph.content.json",
      "export_json_sha256": "0f6d2dd0fa759d394a3f88bb50bb91dfe1201b6153983f3115f8c1271e270914"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "id/steam_enforcement_evidence.html",
      "language": "id",
      "title": "Aturan versus tanggapan — Laporan Khusus “Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/id/steam_enforcement_evidence",
      "source_html_sha256": "1fa0f67e35214bc0fbaf7e04b62b9fbecb16dcbb9f1539a083aa212e0d71a3c7",
      "exported_at": "2026-09-29T00:22:35.316Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "steam_enforcement_evidence.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/id/steam_enforcement_evidence.pdf?v=print-20260929-v5",
        "sha256": "c8e4eea8c031f13ddce2ac06a284523579e62e363cd1292093fc6ee790fe6533",
        "bytes": 379235,
        "pages": 36
      },
      "integrity": {
        "signed_object": "steam_enforcement_evidence.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "steam_enforcement_evidence.content.json.asc",
        "digest_file": "steam_enforcement_evidence.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify steam_enforcement_evidence.content.json.asc steam_enforcement_evidence.content.json",
          "sha256sum -c steam_enforcement_evidence.content.json.sha256"
        ]
      },
      "content": {
        "text": "Lampiran bukti / catatan yang tertaut ke sumber\nSteam Bukti Penegakan Hukum — Catatan Pendukung & Jaringan Pengembang\n\nAturannya. Tanggapan tersebut.\n\nAPA YANG DIBUKTIKAN OLEH BAGIAN INI\n\nRuang bukti ini membandingkan Perjanjian Pelanggan resmi Valve dengan catatan penegakan kebijakan yang berstempel tanggal, penyelesaian sengketa dukungan, serta catatan jaringan pengembang di seluruh repositori 252 dan profil 3,320. Hal ini menunjukkan bahwa pemegang akun biasa menghadapi tindakan penegakan kebijakan yang tidak dapat dibantah serta penutupan layanan dukungan setelah akun mereka diretas, sementara operasi bot komersial berskala besar tetap beroperasi tanpa henti dengan akses ke infrastruktur publik.\n\n← Kembali ke Ringkasan Eksekutif\n\nBaca ketentuan tertulis tersebut. Buka tanggapan yang telah direkam. Bandingkan apa yang tercantum dalam sumber tersebut dengan hal-hal yang masih belum terjawab.\n\nDukungan & permohonan ↓Infrastruktur publik ↓\n252catatan repositori\n3,320profil publik\n4,214pasangan profil–repositori yang berbeda\n98,902pasangan profil dengan repositori bersama\n01 / Dukungan, sanksi, dan pemulihan\nBaca pengaduan tersebut.Sertakan sumbernya.\nGaleri Penolakan Dukungan (Pameran 981) ↗Unduh catatan yang dipilih ↓\nHFB / KASUS OUTSOURCINGKompromi yang diakui.\nPemberhentian yang dilaporkan.\n\nSimak tanggapan layanan pelanggan yang disertakan di bawah ini serta sumber dari pernyataan mengenai staf kontraktor.\n\nBuka kasus ini beserta sumber-sumbernya →\n\nDi bawah ini: lima yang diawetkan postingan Reddit yang terbuka untuk umum dari kumpulan catatan dukungan yang disediakan. Setiap catatan mendokumentasikan interaksi yang dilaporkan dengan sistem dukungan Valve — disimpan lengkap dengan tautan sumber aslinya, posisi tangkapan layar, dan teks lengkapnya. Ini adalah kesaksian para korban. Catatan dukungan yang telah diverifikasi, yang dapat mengonfirmasi atau membantah kesaksian tersebut, disimpan oleh Valve dan belum diungkapkan.\n\n01\nBan & review2024-12-09\nPermanent sanction & closed appeals\n\nThe author reports a permanent account ban, repeated ticket closures and a planned GDPR access request.\n\nREDDIT / PUBLIC TESTIMONYr/ohnePixelCapture record 294\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 303 words\nPermanently banned Steam account without a clear explanation, need help!\n\nsteam_support_tickets_MEGA.json / record 294\n\nHey everyone,\n\nI’m in a really frustrating situation, and I’m hoping someone here can help me or offer advice. My Steam account was just permanently banned for allegedly violating the Steam Subscriber Agreement, and I have no idea why.\n\n# What Steam Support told me:\n\nThe support message said my account was banned due to:\n\n* Suspicious activities related to transferring or attempting to sell/trade the account.\n* Community reports and other unspecified factors.\n\nThey added that the ban is permanent and that they can't help me further. They also warned that future support requests regarding this ban might be ignored. 😞\n\n# Why I’m contesting this ban:\n\n* I have never sold, traded, or transferred my account. I’ve been the legitimate owner since the beginning.\n* On the day the ban occurred, I did nothing noteworthy that could have triggered such a sanction.\n* I received no prior warning, which feels incredibly unfair.\n\n# What I’ve tried so far:\n\n* Contacting Steam Support: I explained my situation and asked for more details, but they’re sticking to their decision and closing my tickets.\n* I’m preparing a request based on my Right of Access (GDPR) to get all the data related to my account.\n\n# Questions for the community:\n\n1. Has anyone successfully had a permanent ban lifted on Steam?\n2. Are there steps I can take to prove I’m the legitimate owner of the account?\n3. Any advice on how to word my request to convince support to reconsider my case?\n4. Would it be helpful to contact the CNIL (I’m based in France) to force Steam to provide more information?\n\nI’m really desperate at the thought of losing all my games, purchases, and years of playtime. Thanks in advance for any help and advice you can give!\n\nhttps://preview.redd.it/jk9qv0gmhv5e1.png?width=1289&amp;format=png&amp;auto=webp&amp;s=b3a333ebb08ea133e2c8747ba126f5a68283d9f7\n\nhttps://preview.redd.it/4sopt0gmhv5e1.png?width=1022&amp;format=png&amp;auto=webp&amp;s=56195d5336118faf9413f1514ead7e8d24c788c3\n\nhttps://preview.redd.it/eqrxw0gmhv5e1.png?width=996&amp;format=png&amp;auto=webp&amp;s=ff3539d28ab754e513ad471822c5de652920101d\n\nhttps://preview.redd.it/728xz0gmhv5e1.png?width=1034&amp;format=png&amp;auto=webp&amp;s=bc5335673509929669af785aa244bf8d2dc58da8\n\n02\nSupport access2025-05-09\nAccount recovery & a reported $10,000 loss\n\nThe author alleges that support reset credentials and removed account protection following another person’s recovery ticket.\n\nREDDIT / PUBLIC TESTIMONYr/legaladviceCapture record 110\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 193 words\nGot $10k stollen from steam inventory due to steam' support fault.\n\nsteam_support_tickets_MEGA.json / record 110\n\nLocation: Quebec, Canada.\n\nLast year, someone hacked my Steam account and stole items worth about $10,000 USD. I only noticed this last week. When I talked to Steam Support, they admitted that someone submitted a ticket to make changes on the account and Steam Support reset my password and turned off all my account security.\n\nI asked Steam Support about getting my items back, but they said there was nothing they could do. They told me I should follow their security recommendations.\n\nThe problem is, I did everything they \"suggested\" to protect an account:\n\n* I had two-factor authentication.\n* My phone number was connected to my account.\n* I used Steam Guard.\n* I printed recovery codes and kept them in a safe.\n\nEven though I did all these things, Steam Support still gave someone else access to my account. The stolen items had been in my account since around 2016-2017. Also, I had not logged in for a few years, so I didn’t accidentally give my information to a fake website.\n\nIs there anything I can do, or do I just have to accept losing $10,000 USD?\n\nThanks for your help.\n03\nRestoration2022-07-07\nA reported $500+ loss & template replies\n\nThe author describes an account compromise, disputed transactions and a support response that allegedly did not address the submitted evidence.\n\nREDDIT / PUBLIC TESTIMONYr/DotA2Capture record 45\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 410 words\nFunds stolen through steam market. Disappointed with Steam response.(or lackthereof)\n\nsteam_support_tickets_MEGA.json / record 45\n\nOn 6th July 2022, 44 unauthorized transactions were made on the steam market using my steam wallet funds totalling roughly $500+ USD to buy worthless 1 cent Dota 2 items. This happened during the wee hours in the morning and i contacted them first thing when i woke up. \n\nI have 2FA enabled all the time, and always thought this would not happen to me as I do not go on betting sites/click sketchy links. My account password + emails were not changed, nor did they take my inventory, just that my funds were used illicitly. Also when I went to disable other APIs, it says there are no other APIs to disable. Shows that it wasn't through me clicking sketchy links and leaving my account details there. Would have lost the whole account if i did so.\n\nWhat baffles me is how did they bypass my 2FA to login my account? Why doesn't steam market purchases go through 2FA as well? First time in 9 years that this happened to me. My acc was logged in 'BY' 'Vitebsk' during the illicit purchases but I'm based in Asia I gathered all the screenshots and provided in the ticket to steam support. \n\nAll i got was the standard copy paste template reply by Steam Support. Lost $500+ and was not even worthy of having a proper person to look into this. I dont think they even read or take a look at the screenshots cause if they did, they would have come to the realization that what happened was clearly fraud, and with a few clicks, reverse the unauthorized transactions, refund my wallet and ban the hijacker. \n\nOver the years, i've spent quite a fair bit on steam but really, this is the kind of recourse we get when our account is compromised? They just don’t care, sigh. I only expect the bare minimum from Steam and looks like even that is quite far-fetched.\n\nSS: https://imgur.com/a/67frcls \n\nHijacker: https://steamcommunity.com/profiles/76561199141246495\n\nSteam Response: https://imgur.com/a/V6v4maM\n\nI could think of a few ways on how to Improve:\n\n1) Add 2FA to market transactions. (even if its bulk posting or selling of items, just 1 2FA notif is required)\n\n2) Enable accounts to be region locked. (if you are migrating, then have to go through steam support etc)\n\n3) Additional Lock on Steam Wallet. (Another password perhaps?)\n\nEDIT: 2nd ticket in and I have still yet to receive a non robotic copy paste template response from Steam.\n04\nRestoration2021-11-29\nSteam Guard & an item-restoration refusal\n\nA preserved post includes the author’s account of item theft and a support response declining restoration.\n\nREDDIT / PUBLIC TESTIMONYr/DotA2Capture record 58\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 563 words\nMany people are losing item via clicking links where steam guard is enabled and steam support doesn't not restore items.\n\nsteam_support_tickets_MEGA.json / record 58\n\nAccounts are getting compromised and might be their pc as well where Steam market is targeted hence the malicious links . I am assuming these hackers are getting encouraged where steam support is not doing nothing and they are getting away with hacking items.  \nLiterally the guy who is supporting the game which he doesn't get any in game advantage just  cosmetics in game only for the sole purpose of supporting the game so that the game will prosper and become beautiful way  to enjoy weekend. But right now players are getting hacked left right and center and steam support  is copy pasting message where in short they are blaming the guy who clicked link. 1st this is happening because they are not targeting players but they are targeting market since they are selling those stuff for real cash via party website. Steam is a huge company and can eradicate the problem or at least can remove links temporarily  in chat since hackers are targeting .They made us install steam guard by saying we wont help if there is no steam guard now steam guard is not enough to save our inventory now they changed their policy  that they should not click any suspicious links. How would we know if the link is suspicious ? After clicking and getting our inventory stolen right !   \n\"we'd have to duplicate an item to restore it. Duplication lowers the value of all items by reducing their scarcity and inflating the economy, which affects everyone involved in trading and the Market. To maintain the value of everyone’s inventory, we do not restore items. For more information, please see the Steam Item Restoration Policy.\"  \nThey care for millions of people IN STEAM MARKET where as few  are losing items which is going to affect market where the rightful owner bought the items and hacker is going to sell the item via 3rd party website and enjoy ! HOW IRONIC !!  \nThis is the message from support where my frnd got his items stolen via clicking on link  \n   \nHi there,  \n\nThank you for the information and screenshots provided.  \n\nIt appears that the account was compromised, please take the following steps to secure your account and computer:  \n\nScan your computer for viruses, key loggers, spyware, and other malicious code using antivirus software with updated virus definitions.  \nChange the password for the email address that is associated with your Steam account.  \nRegularly reset your Steam account password.  \n\nPlease see our Security Recommendations article.  \n\nIn addition, I’m sorry to hear that your items were removed without your permission. Unfortunately, Steam Support does not restore scammed, lost, or stolen items for any reason.  \n\nSince Steam Support does not remove items from accounts, we'd have to duplicate an item to restore it. Duplication lowers the value of all items by reducing their scarcity and inflating the economy, which affects everyone involved in trading and the Market. To maintain the value of everyone’s inventory, we do not restore items. For more information, please see the Steam Item Restoration Policy.  \n\nTo make sure that a scammer is reported, please report them through the Steam Community. Reporting a scammer through the Steam Community is the best way to prevent them from committing future scams.  \n\nTo learn how to avoid scams or hijackings, please see our Trade Scam article.  \n\nIf you still need assistance, please let us know.\n05\nEnforcement2025-05-11\nSelective enforcement & an unexplained ban\n\nA community member describes a disputed ban and contrasts it with the visibility of commercial gambling promotion.\n\nREDDIT / PUBLIC TESTIMONYr/SteamUncensoredCapture record 107\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 1,208 words\n🚨 Steam Bans Without Reason and Ignores Its Community — What’s Going On?\n\nsteam_support_tickets_MEGA.json / record 107\n\nHey r/Steam,\n\nI’m writing this to share my thoughts and concerns about my friend [moneylead](https://steamcommunity.com/id/moneylead/) and Steam’s policies in general. I spoke with him yesterday about his situation, though I didn’t discuss writing this post with him—I asked last night, but he hasn’t responded yet. I want to highlight that this issue is broader than just his case, and while Steam might make changes in the future (though that’s unlikely), I feel the community needs to understand how far Steam has strayed from its original values. I’m not trying to put moneylead in a tough spot with this thread—all the info I’m sharing is public, nothing secretive. I hope he won’t be upset with me, but the community needs this case to see the bigger picture and how Steam feels completely unaccountable.\n\n**Why Does Steam Ignore Its Community?**  \nWhy does a platform like **Roblox** provide a detailed log of ban reasons, while Steam, which claims to be \"community-driven,\" ignores its community, bans whoever they want, for whatever they want, with no transparency? I looked into Roblox as a popular game—not a direct competitor to Steam—to see how their bans look, and you can check it out yourself: [Roblox Ban Reasons](https://www.google.com/search?q=Roblox+ban). Their bans are clear, detailed, and actually explain what you did wrong. I think most decent gaming communities operate like this—not with support agents named Olga, hired through outsourcing, who only know how to send canned auto-replies. Take cases like St4ck—or my friend **moneylead**. All these unbans, like **St4ck’s** or **Alexanddd’s**, happened behind closed doors with zero comments from Steam. Of course, it’s convenient for Steam to handle everything in secret, so no one knows or sees what’s going on—but this violates Steam’s own community rules and principles.\n\n**Who Is moneylead?**  \nI’ve known [moneylead ](https://steamcommunity.com/id/moneylead/)since around 2021. We played Dota 2 a couple of times, and then I just stayed on his friends list. He’s always been a legit player, bringing revenue to Steam through purchases. He never sold his skins, whether in **Dota or CS2—he wasn’t a trader**. All he did was:\n\n* Buy games and skins.\n* Collect badges to level up his profile.\n\nAccording to [SteamSets](https://steamsets.com/account/76561199080934614), he’s given out 324,000 Steam Points—I think he awarded profile rewards to all his friends in the list (though I’m not 100% sure). I do know he ran contests and gave gifts to friends, always supporting the community.\n\n**Steam’s Unfair Treatment**  \nI’ve seen Steam remove his showcases, avatar, description, and even his country multiple times—just because he’s from **Ukraine**. He has a ton of haters leaving toxic comments on his wall, and Steam seems to favor **Russian** users. Every time he tried to appeal the removal of his showcases or profile description—which didn’t break any rules, just had his Instagram link, and his avatar is the same as it is now—Steam moderators didn’t care. **They don’t care about top players who bring them massive revenue, nor about regular users.**\n\n>*Here’s the worst part: moneylead works in cybersecurity, specifically fighting account theft and phishing. He’s neutralized over 5,000 threats targeting Steam alone. And yet, Steam bans him for \"account hijacking\"?*\n\nIf you roughly calculate moneylead’s contribution to Steam and the community—his profile, level, badges (not skins, you can’t sell those)—is this normal, Steam? Banning people, closing tickets, and ignoring users with a spotless reputation who aren’t involved in any commercial activity, just bringing you profit without taking anything in return?\n\n**Steam’s Double Standards**  \nI’m honestly shocked:\n\n* YouTubers who promote casinos and skin gambling? Steam’s fine with that.\n* A cybersecurity expert who fights scams, doesn’t promote casinos, and openly talks about it on his profile? **Banned with no explanation, ignored, and denied an unban.**\n\nI wonder if Steam deliberately bans a high-level account once a year just because of their impunity—maybe for hype or something. Otherwise, this is just madness. It’s scary to think how many regular players have lost their accounts and skins—not because of scammers, but because of Steam’s desire to ignore, send auto-replies, and do whatever they want.\n\n**How Many Others Are Affected?**  \nHow many others are out there—maybe not as well-known—who just have a few games or skins, get banned for nothing, and receive zero explanation or response? **Is this even legal?** Every other platform provides a detailed log with specific violations, but Steam slaps on the same vague label and sends templated responses.\n\n* How safe is it to buy skins on Steam?\n* What’s the chance Steam will just ban your account for no reason, with no explanation?\n\n**A Message to Valve**  \nI wish moneylead the best in resolving this, but Valve, it’d be great if you remembered what \"community\" means and started following the law. Because right now, it looks like your 30% commission, impunity, and sense of being above the law in the U.S. have given you the idea that you can do whatever you want.\n\nI’m sure there are many others like moneylead and St4ck—people who aren’t public or don’t have the resources to fight back. Let’s unite these cases. **If you’re a U.S. resident who’s been banned by Steam without reason and wants to challenge it, please reach out to me.** I’m finishing my **Juris Doctor (J.D.) program at SMU Dedman School of Law** in Dallas, Texas, and I’m participating in a legal clinical practice under Rule 13 of the Texas Supreme Court.\n\nWhat Steam is doing is absolutely disgusting and illegal, and **I’d be happy to help any gamer (legitimate, with no real violations) who has games or skins with value. This will be beneficial for my practice, and it’s time to put Steam in its place and show them they can’t just dictate their own rules with arbitration**. Let’s take it all the way—not for punishment, but for the sake of the community. Maybe if Steam loses a case, they’ll change their policies and start explaining their actions like most popular gaming communities do. Many of us remember how Steam Support used to recover stolen accounts and ended up “stealing” skins themselves—banning without real reasons is basically the same thing, and that’s a serious accusation.\n\nSo, r/Steam, see you soon. I think you understand what you’re doing and how many people you’ve illegally deprived of their assets. I want to raise this issue—not just for the U.S., but for the entire world. You’ve banned class-action lawsuits? **Welcome to Texas.** I recommend starting to look for licensed attorneys in Texas, because I’d love to discuss your company’s policies, feedback, and support agents named Olga—a name that strongly associates with Russian users. Maybe it’d be easier to move your company to Moscow? But I’d be happy to discuss these critical issues on behalf of the global gaming community.\n\nAlso, I wouldn’t recommend ignoring the lawsuit request that will be sent to your physical address and email address, as the court will proceed without you, and that might upset you—especially since things aren’t going so well for a company with stocks like yours.\n\n**Thanks to everyone who took the time to read this. For those who need real help with an unjust Steam ban without any explanation, I’d be happy to assist. For users from Texas, we can easily file a collective lawsuit against Steam—let’s connect and make it happen.**\n02 / Jaringan Pengembangan Steam\nInfrastruktur publik.Direkam dalam skala besar.\nUnduh semua rekaman 252 ↓\n\nYang disertakan output_steam_network Snapshot mencatat repositori, hubungan kontributor/fork publik, serta tumpang tindih profil. Ini adalah catatan yang dipublikasikan — apa yang telah dikembangkan, siapa yang berkontribusi, dan apa yang telah difork. Jejak dokumentasi kemampuan publik inilah yang harus diperhitungkan oleh Valve.\n\nRepositori / deskripsi\tKontributor\tForkers\tProfil yang telah disimpan\nalliedmodders/amxmodx\n\nAMX Mod X - Half-Life 1 Scripting and Administration\n\n\t40\t40\t80\nalliedmodders/sourcemod\n\nSourceMod - Source Engine Scripting and Administration\n\n\t40\t40\t80\nDoctorMcKay/node-steam-user\n\nAllows interaction with the Steam network via the Steam client protocol\n\n\t40\t40\t80\nFacepunch/Facepunch.Steamworks\n\nAnother fucking c# Steamworks implementation\n\n\t40\t40\t80\nJustArchiNET/ArchiSteamFarm\n\nC# application with primary purpose of farming Steam cards from multiple accounts simultaneously.\n\n\t40\t40\t80\nodota/core\n\nOpenDota: Open source Dota 2 data platform with automated replay parsing\n\n\t40\t40\t80\nodota/dotaconstants\n\ndotaconstants: Static data for Dota applications\n\n\t40\t40\t80\nodota/web\n\nOpenDota: React web UI for Dota 2 statistics using the OpenDota platform\n\n\t40\t40\t80\nsplewis/get5\n\nCS:GO Sourcemod plugin for competitive matches/scrims\n\n\t40\t40\t80\nSteamDatabase/FileDetectionRuleSets\n\n🔎 Rules to detect game engines and other technologies based on Steam depot file lists\n\n\t40\t40\t80\nSteamRE/SteamKit\n\nSteamKit2 is a .NET library designed to interoperate with Valve's Steam network. It aims to provide a simple, yet extensible, interface to perform various actions on the network.\n\n\t40\t40\t80\nValveSoftware/dxvk\n\ndxvk tree containing branches used by Proton\n\n\t40\t40\t80\nValveSoftware/GameNetworkingSockets\n\nReliable & unreliable messages over UDP. Robust message fragmentation & reassembly. P2P networking / NAT traversal. Encryption.\n\n\t40\t40\t80\nValveSoftware/gamescope\n\nSteamOS session compositing window manager\n\n\t40\t40\t80\nValveSoftware/Proton\n\nCompatibility tool for Steam Play based on Wine and additional components\n\n\t40\t40\t80\nValveSoftware/source-sdk-2013\n\nThe 2013 edition of the Source SDK\n\n\t40\t40\t80\nValveSoftware/wine\n\nWine with a bit of extra spice\n\n\t40\t40\t80\nValveSoftware/steam-devices\n\nList of devices Steam and SteamVR will want read/write permissions on, to help downstream distributions create udev rules/etc\n\n\t39\t40\t79\nValveSoftware/steam-audio\n\nSteam Audio\n\n\t38\t40\t78\nalliedmodders/metamod-source\n\nMetamod:Source - C++ Plugin Environment and Detour Library for the Source Engine\n\n\t37\t40\t77\nalliedmodders/sourcepawn\n\nA small, statically typed scripting language.\n\n\t35\t40\t75\nValveSoftware/Fossilize\n\nA serialization format for various persistent Vulkan object types.\n\n\t31\t40\t71\nrlabrecque/Steamworks.NET\n\nSteamworks wrapper for Unity / C#\n\n\t27\t40\t67\nModDota/moddota.github.io\n\nModDota github pages project.\n\n\t26\t40\t66\nodota/parser\n\nReplay parse server generating JSON log events from Dota 2 replay files\n\n\t26\t40\t66\nValveSoftware/steam-for-linux\n\nIssue tracking for the Steam for Linux beta client\n\n\t26\t40\t66\nSteamRE/DepotDownloader\n\nSteam depot downloader utilizing the SteamKit2 library.\n\n\t24\t40\t64\nJustArchiNET/ASF-ui\n\nThe official web interface for ASF\n\n\t23\t40\t63\nadvancedfx/advancedfx\n\nHalf-Life Advanced Effects (HLAE) is a tool to enrich content creation mainly for the Counter-Strike series.\n\n\t22\t40\t62\nalliedmodders/ambuild\n\nAlliedModders C++ Build System\n\n\t23\t39\t62\nSteamDatabase/BrowserExtension\n\n💻 SteamDB's extension for Steam websites\n\n\t21\t40\t61\nodota/mobile\n\nReact Native apps for viewing Dota 2 data on Android/iOS\n\n\t19\t40\t59\nValvePython/steam\n\n☁️ Python package for interacting with Steam\n\n\t18\t40\t58\nskadistats/clarity\n\nComically fast Dota 2, CSGO, CS2 and Deadlock replay parser written in Java.\n\n\t13\t40\t53\nSteamRE/open-steamworks\n\nOpen Steamworks is a set of reverse engineered headers for the Valve's Steam Client. More or less abandoned now that the Steamworks SDK is publically available.\n\n\t13\t40\t53\nValveSoftware/Source-1-Games\n\nSource 1 based games such as TF2 and Counter-Strike: Source\n\n\t13\t40\t53\nalliedmodders/hl2sdk\n\nHalf-Life 2 SDK Mirrors\n\n\t11\t40\t51\nSteamDatabase/steamdb.info-issues\n\n🚱 Issue tracker for the SteamDB website\n\n\t11\t40\t51\nCSGOFloat/inspect\n\nSource Code that Powers the CSFloat Inspect Link API\n\n\t10\t40\t50\nValveSoftware/SteamOS\n\nSteamOS community tracker\n\n\t10\t40\t50\nalliedmodders/source2mod\n\nExperimental\n\n\t40\t9\t49\nsmiley/steamapi\n\nAn unofficial object-oriented Python library for accessing the Steam Web API.\n\n\t9\t40\t49\nSteamDatabase/GameTracking\n\n🛢 Dumping things, so you don't have to\n\n\t8\t40\t48\nValveSoftware/counter-strike_rules_and_regs\n\nCS:GO\n\n\t7\t40\t47\nValveSoftware/openvr\n\nOpenVR SDK\n\n\t6\t40\t46\nSteamDatabase/easy-markdown-editor\n\nEasyMDE: A simple, beautiful, and embeddable JavaScript Markdown editor. Delightful editing for beginners and experts alike. Features built-in autosaving and spell checking.\n\n\t40\t4\t44\nValveSoftware/Dota-2\n\nTracker for issues specific to Linux and Mac in the Reborn client. If you have a general issue or non-system-specific feature request please go to dev.dota2.com\n\n\t6\t38\t44\nValveSoftware/Dota2-Gameplay\n\nPublic Bug Tracker for Dota 2\n\n\t4\t40\t44\nJustArchiNET/ArchiBot\n\nNo description in the capture.\n\n\t16\t27\t43\nztizzlegaming/CSGOWinBig\n\nOpen-source Counter-Strike: Global Offensive jackpot betting website.\n\n\t1\t40\t41\nJustArchiNET/mantis.justarchi.net\n\nMantis Bug Tracker (MantisBT)\n\n\t40\t0\t40\nodota/node-steam-user\n\nAllows interaction with the Steam network via the Steam client protocol\n\n\t40\t0\t40\nModDota/TypeScriptAddonTemplate\n\nDota 2 addon template with TypeScript Panorama and VScripts.\n\n\t9\t29\t38\nValvePython/vdf\n\n📜 Package for working with Valve's text and binary KeyValue format\n\n\t6\t32\t38\nalliedmodders/amtl\n\nAlliedModders C++ Template Library\n\n\t17\t19\t36\nValvePython/dota2\n\n🐸 Python package for interacting with Dota 2 Game Coordinator\n\n\t5\t30\t35\nalliedmodders/stripper-source\n\nStripper:Source\n\n\t13\t21\t34\nAllyans3/steam-market-api-v2\n\nSteam Market API v2 package\n\n\t3\t31\t34\nModDota/dota-tutorial\n\nCustom game DOTA tutorial.\n\n\t11\t23\t34\nodota/blog\n\nNo description in the capture.\n\n\t29\t3\t32\nOpsecGuy/BetterGo\n\nExternal CS:GO cheat written in python.\n\n\t1\t27\t28\npxvr-official/1\n\n無許諾配信 企業理念剽窃 動物の森収益化 大神ミオ権利者削除 戌神権利侵害発言 常闇トワ炎上 夜空メルストーカー被害 建築王サポーター放置 赤十字マーク 魔乃アロエ卒業 一つの中國支持声明 大空昴3Dライブ 無限延期清掃員職業差別 日清コラボ楽曲 musedash非公開 rog案件取り消し 壁画ライブ 丁真 Ding Zhen 郑爽 Zheng Shuang 防护林 与朵小天使w 伊月猫凛 本主萌埋午休傻 汪峰 重生细胞 壁纸 比利海灵顿 香蕉君 van 田所浩二 抽象带篮子 抗压背锅吧 季子越 蒋明辉 傻逼…\n\n\t0\t28\t28\nRevadike/InternalSteamWebAPI\n\nDocumenting the unofficial and internal Steam Web API\n\n\t1\t27\t28\nJoeSzymkowiczFiveM/qb-lootcrate\n\nA CSGO-style case opening script\n\n\t2\t25\t27\nAbrarKL/MyRoulette.XYZ\n\nCSGO / Steam Roulette Site created with PHP and Node JS, using the Material Design front-end framework.\n\n\t1\t25\t26\nJustArchiNET/ASF-WebConfigGenerator\n\nNo description in the capture.\n\n\t10\t15\t25\nModDota/dota-data\n\nAuto-generated Dota 2 resource dumps\n\n\t11\t14\t25\nModDota/TypeScriptDeclarations\n\nTypeScript declarations for Dota 2.\n\n\t11\t14\t25\nModDota/API\n\nNo description in the capture.\n\n\t12\t12\t24\nalliedmodders/cssdm\n\nCounter-Strike:Source Deathmatch\n\n\t10\t13\t23\nSteamDatabase/steamstat.us\n\n✅ Front-end of Steam services status website\n\n\t4\t18\t22\nc0deina/csgojackpotV2\n\nCSGO Jackpot Source\n\n\t1\t20\t21\nValvePython/steamctl\n\n🤸 Take control of Steam from your terminal\n\n\t2\t19\t21\nValvePython/csgo\n\n🔫 Python package for interacting with CS:GO Game Coordinator\n\n\t3\t17\t20\nBeepIsla/csgo-crash-exploit\n\nAllows you to crash any Windows user\n\n\t3\t16\t19\nValvePython/vpk\n\n📦 Open, Search, Extract and Create VPKs in python\n\n\t4\t15\t19\nalliedmodders/SM-SteamWorks\n\nExposing SteamWorks functions to SourcePawn.\n\n\t14\t3\t17\nSteamRE/Steam4NET\n\nSteam4NET is a .NET wrapper around the Steamworks C++ interfaces\n\n\t2\t15\t17\nalliedmodders/hl2sdk-manifests\n\nInformation about HL2SDKs shared between Metamod:Source and SourceMod.\n\n\t6\t10\t16\nJustArchiNET/ASF-PluginTemplate\n\nTemplate repository that you can use for creating custom plugins for ArchiSteamFarm.\n\n\t8\t7\t15\nModDota/Dota2AIFramework\n\nGeneral Framework for Dota 2 AI Competitions\n\n\t1\t14\t15\nShkyyl/KeyChamp\n\nExtension for joining free case battle on key-drop automatically\n\n\t1\t14\t15\nSteamDatabase/SteamMonitor\n\n😤 Track Steam's connection manager servers status\n\n\t2\t12\t14\nBaterka/cslore.com\n\nCS:GO gambling site - csgo.style\n\n\t1\t12\t13\nSteamDatabase/SteamTokenDumper\n\n🔢 Submit users' PICS access tokens to SteamDB\n\n\t2\t11\t13\nmonoblocker/roulette\n\nRoulette CS:GO made in React and Typescript\n\n\t1\t11\t12\nzsith/launcher.user.js\n\n// ==UserScript== // @name AposLauncher // @namespace AposLauncher // @include http://agar.io/* // @version 3.062 // @grant none // @author http://www.twitch.tv/apostolique // ==/UserScript== var aposLauncherVersion = 3.062; Nu…\n\n\t1\t11\t12\nLincolnIT/CSGODouble-bot-automated\n\nCSGODouble Automated, auto Betting Bot.\n\n\t1\t10\t11\nvladpuz/steam-market\n\nSteam market API client\n\n\t4\t7\t11\nmcgrizzz/Cstrike.bet\n\nCSGO Roulette Website Angular frontend, nodejs backend, and steam trading bots\n\n\t1\t9\t10\nodota/underlords-web\n\nUI for OpenUnderlords\n\n\t5\t5\t10\nSteamDatabase/SteamToTwitter\n\n🕊 Tweets announcements from various Steam groups\n\n\t1\t9\t10\nModDota/AbilityLuaSpellLibrary\n\nThe successor to the Spell Library by Pizzalol\n\n\t4\t4\t8\nalvinl/bitskins\n\nUnofficial BitSkins API client\n\n\t2\t5\t7\nb1naryth1ef/steamy\n\nA Python Steam community and market API interface that will get you all hot and bothered\n\n\t2\t5\t7\nkratos1812/Case-Opening\n\nIn-game case opening system for CSGO servers.\n\n\t2\t5\t7\nodota/docs\n\nOpenDota API documentation\n\n\t4\t3\t7\nSteamDatabase/steam-advanced-access-fetch-players\n\n📈 Simple script to fetch Steam player count\n\n\t1\t6\t7\nTheRioMiner/CsgoBetterExternalRaytrace\n\nOverridden maps pack for better external raytrace\n\n\t1\t6\t7\nalliedmodders/hl2sdk-mock\n\nMock HL2SDK and Server\n\n\t5\t1\t6\nchristophersu/PySteamMarket\n\nPython API for getting prices from the Steam market.\n\n\t1\t5\t6\nExtremelyd1/Strat-Roulette\n\nCS:GO Sourcemod Plugin\n\n\t2\t4\t6\ngiovanni-orciuolo/double-sdk\n\nA simple way to write CS:GO cheats!\n\n\t2\t4\t6\nJustArchiNET/Madness\n\nMadness embraces your project by including compatibility layer for selected APIs normally not available on .NET Framework target.\n\n\t5\t1\t6\nModDota/TypescriptPanoramaDeclarations\n\nNo description in the capture.\n\n\t4\t2\t6\nodota/rapier\n\nA JavaScript Dota 2 (Source 2) replay parsing library\n\n\t1\t5\t6\nVozn1akHero/CSGOCaseOpeningSimulator\n\nCounter-Strike case opening simulator which resembles the good old CS:GO user interface\n\n\t3\t3\t6\nautarc/steam-store\n\nAPI client for the unofficial steam storefront/big picture resource\n\n\t2\t3\t5\nBETTING-CODE/awesome-esports-sites\n\nA curated list of awesome esport betting sites – live, statistics and other resources.\n\n\t1\t4\t5\njonteohr/Better-Warden\n\nAn improved and more advanced warden plugin with a custom menu for CS:GO jailbreak servers!\n\n\t2\t3\t5\nLudzikk/CSGO-Gambling-Site\n\nhttps://ludzikk.github.io/CSGO-Gambling-Site/\n\n\t1\t4\t5\nModDota/find-steam-app\n\nFind location of an installed Steam app\n\n\t3\t2\t5\nmprey/csgocact.us\n\nsource code for csgocact.us\n\n\t1\t4\t5\nnezu-cc/ServerCrasher\n\nCS:GO Server Crasher\n\n\t1\t4\t5\nodota/testfiles\n\nStores test replay files\n\n\t2\t3\t5\nodota/underlordsconstants\n\nConstant data for Dota Underlords\n\n\t3\t2\t5\nSnaBe/node-steam-market-fetcher\n\nA Node.js wrapper for the Steam Community Market API.\n\n\t2\t3\t5\nSteamDatabase/.github\n\n💗 Organization-wide community health files\n\n\t1\t4\t5\nwolfcon/RIP-HLTV-BET\n\nRIP BET AD (For Tampermonkey) https://greasyfork.org/en/scripts/423484-rip-hltv-bet\n\n\t2\t3\t5\nalliedmodders/blaster.net\n\nSource and GoldSrc Query Tool\n\n\t2\t2\t4\ncatears124/CS2-Price-API\n\nsimple python cs2 steam market price API\n\n\t1\t3\t4\nialakey/caseforge\n\nOpen-source CS2 case-opening platform: Steam auth, provably fair openings, RTP-balanced case builder, withdrawals bought on market.csgo.com and an admin CRM.\n\n\t1\t3\t4\nIlusion9/csgo-fix-mapchange-crash-sm\n\nFix players crash on map change.\n\n\t1\t3\t4\nismail0234/Benson-Map-Crash-Fixer\n\nCSGO Map Change Client Crash Fixer\n\n\t1\t3\t4\njaxwilko/steam-market-api\n\nPHP - Composer Compatible - Steam Market API\n\n\t2\t2\t4\nJustArchiNET/ArchiTag\n\nArchiTag is a very small utility based on Python 3 and Mutagen to provide missing functionality in opusenc of writing specific Opus metadata, such as total number of tracks or track number.\n\n\t1\t3\t4\nModDota/DotaUI\n\nNo description in the capture.\n\n\t2\t2\t4\nnode-steam/market-pricing\n\nWrapper for the unofficial Steam Market Pricing API\n\n\t1\t3\t4\nodota/media\n\nStores media files for Dota projects\n\n\t2\t2\t4\nSergeyIvanovDevelop/Crypto-Steam-Platform\n\nThe repository contains the code and configuration to run a platform for creating cryptocurrency stakes for arbitrary ERC20 tokens.\n\n\t1\t3\t4\nAareksio/csgodouble-floatchecker\n\nAdds context menu option to check item's float value\n\n\t1\t2\t3\nchinm4/CSGOdrop\n\nA online csgo gambling casino that includes a variety of mini games that allows you to win csgo skins\n\n\t2\t1\t3\nCruze03/CSGO-Case-Opening-Prank\n\nCommand:- !prank (Admin flag \"n\" required)\n\n\t1\t2\t3\nDhruva-Kapadia/CSGOTrollGG\n\nCSGO Case Opening Simulator\n\n\t2\t1\t3\nErhanCSGO/CSGOPolygon-prediction\n\nCSGOPolygon.com - prediction script, double your coins by using this tool\n\n\t1\t2\t3\nEv-Hoang/Bedrock-Chest-Case-Opening\n\nHypixel Skyblock Dungeon Mod - Bedrock Chest Opening Animation (CSGO Style)\n\n\t1\t2\t3\njmjp/csgo-roulette\n\nA csgo gambling roulette make with VueJS 3\n\n\t2\t1\t3\nJustArchiNET/ArchiCrowdin\n\nNo description in the capture.\n\n\t1\t2\t3\nLeonSK/WearMarketInspector\n\nRetrieve Wear Value (Float Value) and Pattern Index from Steam Community Market using http://csgo.exchange API\n\n\t1\t2\t3\nmaximgeerinck/csgo-gamble\n\nCSGO gambling website\n\n\t1\t2\t3\nModDota/BugTracker\n\nListing bugs for Dota 2 Custom Games\n\n\t2\t1\t3\nplwp/mma-betting\n\nUFC/MMA betting model with Pinnacle steam detection for AU book latency arb\n\n\t2\t1\t3\nSouthsideswag16/Csgo-Gambling-Site\n\nNo description in the capture.\n\n\t2\t1\t3\ntacyarg/csgofiesta-frontend-react\n\nRemastered version a the long time favorite csgo site\n\n\t2\t1\t3\nVelorasse/Mutah-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-csmoney-csgoskins\n\ngambling script for Mutah, Keydrop, csmoney, and csgoskins, featuring hacks, cheats, and predictors. Offers strategies to boost winning odds and optimize performance on these platforms.\n\n\t3\t0\t3\nalliedmodders/am-github-artifact-webhook\n\nNo description in the capture.\n\n\t2\t0\t2\ncharamza/roulette\n\nCSGO like roulette in JS\n\n\t1\t1\t2\nCruze03/CSGO-PugSetup-RoundRestore\n\nSometimes (player dropped/crashed) which would be disadvantage for a team. It would be very handy to restore the match to the previous round.\n\n\t1\t1\t2\ncsgorol/CSGO-ROLL-Crash-Predictor\n\nCSGO-ROLL-Crash-Predictor\n\n\t1\t1\t2\nFoxSerito/FOXWORLD_plugin_DoubleJump_CSGO\n\nПлагин SourceMod (CSGO). Двойной прыжок с эффектом.\n\n\t1\t1\t2\nhkehayovmoonbiz/CS2-Casino-Full-Source-Code\n\nCS2, CS2 betting platforms, Skin Roulette, Case Unboxing, Crash games, Jackpot, purchase CS2 casino source, crypto gambling\n\n\t1\t1\t2\nJustZakary/steamstoreapi\n\nThis NPM module is a API wrapper that makes the steam unofficial API easier to use.\n\n\t2\t0\t2\njzimr/steam-market-api\n\nA java library to easily get Steam Community Market data\n\n\t1\t1\t2\nMomohime/CSGO.Network-Jackpot-Coinflip\n\nNo description in the capture.\n\n\t1\t1\t2\nnnjjswat/moneybot\n\nautomated bots for bustabit (formerly known as moneypot), csgo crash, etc\n\n\t0\t2\t2\nodota/carry\n\nLegacy Application for donations to the OpenDota project\n\n\t1\t1\t2\nodota/PublicMatchDataBot\n\nA Discord bot to remind users to turn on Expose Public Match Data in the Dota 2 client\n\n\t1\t1\t2\nOrillio/CSGOBet.com\n\nCSGO roulette web app\n\n\t2\t0\t2\nripexz/csgo-bet-alert\n\nA Chrome extension to keep track of active CS:GO Lounge matches.\n\n\t1\t1\t2\nrrpvm/lumen_sense-beta-deprecated-\n\nthis is internal csgo cheat written by me(no paste, self reverse structures). start : ~6 August 2020, end : ~ 14 December 2020\n\n\t1\t1\t2\nRuthless222/csgoscore\n\nThis is a Counter Strike Global Offensive Betting Site. You chose the skins you want to bet and try to win jackpots\n\n\t2\t0\t2\ntfburns/CSGO-cases-PL\n\nExpected profit-loss of CS:GO case openings\n\n\t1\t1\t2\nTomDra/CSGO-Case-Data-Analysis\n\nWorks out the most profitable CS:GO case at that current time\n\n\t1\t1\t2\nValvePython/dota2-wrappers\n\nNo description in the capture.\n\n\t1\t1\t2\nValvePython/teamfortress2-closed-captions\n\nThis project aims to provide a set of closed captions for Team Fortress 2\n\n\t1\t1\t2\nVistaNetGTX/Cstrike.bet-\n\nCSGO Roulette Website Angular frontend, nodejs backend, and steam trading bots\n\n\t1\t1\t2\nwafflas/csgo-case-opening-simulator\n\nI created a cs go case opening simulator for a meme coin\n\n\t0\t2\t2\nAdmiral-Enigma/Le_Coinflip\n\nConflip game\n\n\t1\t0\t1\nadryeljuliao/roulette-csgo\n\nNo description in the capture.\n\n\t1\t0\t1\nAndreuTheG/csgo-coinflip-web\n\nCSGO Gambling Coinflip Website\n\n\t1\t0\t1\nasmilen/csgoDouble\n\na b c\n\n\t1\t0\t1\nb1naryth1ef/csgofort\n\nA CSGO portal for trading, betting, analytics, and more!\n\n\t1\t0\t1\nBaterka/PrivateSteamBettingWebsite2024\n\nPrivate Steam (Counter-Strike 2) betting/gambling website - Roulette, Jackpot\n\n\t1\t0\t1\nblackcaer/SteamTradeHandler\n\nAutomation of Steam trading. Helper project for bet automation.\n\n\t1\t0\t1\nBTheCoderr/theRounders\n\nThe Rounders - A professional-grade sports betting analytics platform combining real-time odds tracking, sharp movement detection, and advanced statistical analysis. Features include line shopping, steam move alerts, power rankings, and comprehensive bet t…\n\n\t1\t0\t1\nCallumHemsley/KazeBot\n\nA Twitch chat betting bot for CSGO, simply bet a certain amount of points, and double if you win, lose all if you lose. Simple.\n\n\t1\t0\t1\nchrisjpm/CSGOJackpotTemplate\n\nFront end for a jackpot site\n\n\t1\t0\t1\ncolinsenner/valve-bug-bounty\n\nFor many years CS:GO, Dota 2, and Team Fortress 2 servers had a bug that allowed malicious users to leak crucial server process memory or reliably crash any server.\n\n\t1\t0\t1\ncoryypeters/nrl-odds-intelligence-pipeline\n\nReal-time sports betting odds intelligence — streaming pipeline that detects line movement, steam, and arbitrage across bookmakers. Python · Redis Streams · FastAPI · React.\n\n\t1\t0\t1\ndeissh/dev-csgoduo\n\nCS:GO. Bot for receiving things on the site (Polygon, Duo, Double and etc).\n\n\t1\t0\t1\ndom1torii/even-better-font-manager\n\nSimply even better cross-platform tool for CS2 Font Management\n\n\t1\t0\t1\nDONnicov/CSGO-crash-black-screen-\n\nsolution csgo crash black screen and close csgo\n\n\t1\t0\t1\nDoubleBoters/CsgoDouble\n\nNo description in the capture.\n\n\t1\t0\t1\ndownarowiczd/DoubleBot\n\nAn old CSGO Double Bot written for my friend. - 07.05.2016\n\n\t1\t0\t1\nErayBahar/steammarketscraper\n\nSteam Market Scraper Python-based tool that tracks real-time CS2 skin prices using Steam's hidden API. It fetches the lowest sell and highest buy offers for any item, helping you monitor deals or snipe underpriced listings automatically.\n\n\t1\t0\t1\nfairydarkness/SteamwebmailAPI\n\nUnofficial Python API for steamwebmail.com Fast, lightweight, and browserless library for automating steamwebmail.com. Support for session management, proxy, folder navigation, and message retrieval\n\n\t1\t0\t1\nFAQU2/CSGO-Coinflip-MyJailShop\n\nSourcemod plugin which provides a Coinflip system for MyJailShop.\n\n\t1\t0\t1\nFlamesONE/csgo-case-opening\n\nNo description in the capture.\n\n\t1\t0\t1\nFunnyRain/csgorun-crash-watch\n\n🚀 CsgoRun dump crash. / 🚀 CsgoRun дамп крашей.\n\n\t1\t0\t1\ngeohdgio/Venatus-Autenticator\n\nეს არის Steam Autenticator ქართული Venatus Trade & Betting ისთვის და Valve News Georgia-სთვის.\n\n\t1\t0\t1\nhakanstarlord/steam-bot\n\nSports betting steam-move signal detection with ML pipeline (XGBoost stacking + isotonic calibration), backtesting engine, Flask dashboard, and Telegram alerts.\n\n\t1\t0\t1\nHvH-gg/CSGO-Item-CrashFix\n\nA plugin for Counter-Strike: Global Offensive that fixes an exploit where receiving CS2 Items will cause CS:GO clients to crash\n\n\t1\t0\t1\nHvH-gg/CSGO-NetMsg-CrashFix\n\nA plugin for Counter-Strike: Global Offensive that fixes an exploit where spamming NetMsg_StringCmd packets would result in a server crash.\n\n\t1\t0\t1\nisybycnsmam/SteamLibrary\n\nLegacy Steam Unofficial API\n\n\t1\t0\t1\nItsTangerine/SteamApis.Net\n\nUnofficial https://steamapis.com .NET library, supporting .NET 6.0+\n\n\t1\t0\t1\nJustArchiNET/JustArchi.net\n\nNo description in the capture.\n\n\t1\t0\t1\nkiri-osint/CS2-Info-Hub-Bot\n\nA Telegram bot that acts as a hub for CS2 players, providing real-time skin prices, server stats, and user profile/inventory inspection using official and unofficial Steam APIs.\n\n\t1\t0\t1\nKoshkaj/monte\n\nGamified csgo gambling platform implementation\n\n\t1\t0\t1\nmadsab/CaseOpening\n\nA school project using Java. Simulating the case opening from CSGO and more.\n\n\t1\t0\t1\nman90es/steamcardexchange-api\n\nSteamCardExchange.net unofficial REST API server (scraper).\n\n\t1\t0\t1\nMattPua/steam-unofficial-docs\n\nUnofficial docs for Steam APIs with fumadocs\n\n\t1\t0\t1\nMetallist1/Portfolio.CsgoWinGambleProject\n\nA website that was done in 2017 September. Websites focus was on gambling with Counter-Strike items. Project was largely completed however backups were not done correctly, this resulted in half a year of wasted improvements to the code. The website was test…\n\n\t1\t0\t1\nmikebobadilla/csgo-jackpot\n\nNo description in the capture.\n\n\t0\t1\t1\nmikebobadilla/meteor-csgojackpot\n\nCssgo Jackpot done in meteor\n\n\t1\t0\t1\nModDota/D2VDump\n\nDota 2 Server VScript API Dumper\n\n\t1\t0\t1\nModDota/DotaTracking\n\nNo description in the capture.\n\n\t1\t0\t1\nModDota/eslint-config\n\nESLint config by ark120202\n\n\t1\t0\t1\nmr-codinglv/Casino-script\n\nscript casino - script betting - exchange script - bc casino - casino csgo - script bet - betwin script\n\n\t1\t0\t1\nMrKeelik/MrKeel\n\nCSGO DOUBLE BOT\n\n\t1\t0\t1\nnoahlatzel/CSGORollHelper\n\nLeveraging positive expected value on triple green jackpots on CSGORoll!\n\n\t1\t0\t1\noddsgpt/oddsgpt-market-intelligence\n\nResearch on football betting markets, closing odds, CLV, market efficiency, steam moves, AI betting systems, and sports market intelligence.\n\n\t1\t0\t1\noEXU/csgo-server-crasher\n\nCSGO SERVER CRASHER\n\n\t1\t0\t1\nPrdTTony/CSGO-Roulette\n\n[CSGO] Roulette System. Bet on RED or Black and win x2 credits\n\n\t1\t0\t1\nr-adamski/csgo-jackpot\n\nNo description in the capture.\n\n\t1\t0\t1\nSahotallo/Turan-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-Skinbaron-hellcase\n\ngambling script for Turan, Keydrop, Skinbaron, and Hellcase, providing hacks, cheats, and predictors. Includes strategies to improve winning chances and enhance gameplay on these platforms.\n\n\t1\t0\t1\nsamuelcsouza/steam-marketplace-api\n\nAn unofficial API to get data from the Steam Marketplace.\n\n\t1\t0\t1\nSKINSTRACK/CS2-Price-API\n\nSkinstrack offers a free, limited API endpoint that returns Steam item prices. Paid plans additionally provide access to pricing data from multiple marketplaces, making it possible to compare prices across different markets through a single API.\n\n\t1\t0\t1\nsnmtriet/CSGO-Casino-Full-Source-Code\n\nCSGO, CSGOEmpire, Case Opening, Case Battles, Roulette, Coinflip, buy csgo gambling site, gambling\n\n\t1\t0\t1\nSteamRE/homebrew-tools\n\nRepository for installation of SteamRE tools via Homebrew (http://brew.sh)\n\n\t1\t0\t1\nSteamRE/opensteamworks.org\n\nNo description in the capture.\n\n\t1\t0\t1\nTheQuack45/CsgoCaseOpenProgram\n\nSimple program to parse an XML file with CS:GO case information and \"simulate\" case openings\n\n\t1\t0\t1\nTLClassless/StratRouletteCSGO\n\nA 'Strat Roulette' web app for CS:GO!\n\n\t1\t0\t1\ntomasoom/csgoCaseOpening\n\nNo description in the capture.\n\n\t1\t0\t1\nvitaliy-evsyukov/steamgifts-autobet-bookmarklet\n\nbookmarklet for automatic bets on steamgifts.com\n\n\t1\t0\t1\nXpravdaX/RouletteCSGO\n\nNo description in the capture.\n\n\t1\t0\t1\nYuiKasumii/steam_api_unofficial\n\nUnofficial Steam Game Information Database\n\n\t1\t0\t1\nZexuz/Steam-Betting\n\nA betting website build ontop of STEAM's ecosystem\n\n\t1\t0\t1\nANK-RULZZ/steam-jackpot-site\n\ngetting some errors and would like some one to help me with it thank you!!!\n\n\t0\t0\t0\nasmilen/CsgoDoubleVS\n\nNo description in the capture.\n\n\t0\t0\t0\nCORNOODOSADAS/CSGOWeed\n\nCsgo Jackpot and Coinflip\n\n\t0\t0\t0\nCSGOApple/csgoapple\n\nJackpot Site\n\n\t0\t0\t0\nCSGOFAST/csgofast-api\n\nNo description in the capture.\n\n\t0\t0\t0\nDonakall/csgoDoublebot\n\nAutomated bot for csgodouble\n\n\t0\t0\t0\nfedor-selivanov/csgo-fast-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nfoldageros/csgod\n\ndouble bot\n\n\t0\t0\t0\ngmod-gambling/gmod-gambling\n\nNo description in the capture.\n\n\t0\t0\t0\nierome/CSGOBoss-BackEnd\n\nBack end version of CSGOBoss. This was a CSGO Gambling site named CSGOBoss. Coded by an old friend of mine Dahquan Hinds (https://github.com/dahquan/) Thought I would release this to help out any one who would need it.\n\n\t0\t0\t0\njamienp1/CSGODOUBLE-BOT-AUTO\n\ni got a bot thats is betting on the last winning color except from green and if you lose it will double the coins you set it to bet, pretty good, so when there comes a loooong train you will be gaining a bit of money codepaste_net/ugmt92 remove all the _ an…\n\n\t0\t0\t0\nJEYONER/CSGOTOXIC\n\nPAGINA DE JACKPOT CSGO SKINS\n\n\t0\t0\t0\nkalrish/csgo-jackpot\n\nStressful but funny zombie-like Counter-Strike: Global Offensive game mode.\n\n\t0\t0\t0\nkrys12345/roulettee\n\n// ==UserScript== // @name CSGO Predict Bot // @namespace http://csgodouble.com // @version 1.0 // @description predicts what number its gonna be // @author Meee // @match http://www.csgodouble.com/ // @grant none // ==/…\n\n\t0\t0\t0\nLilDuggiMuffi/CSGODouble-Working-Bot\n\nFixed CSGO Double Bot\n\n\t0\t0\t0\nLyricLy/Steam2Proton\n\nCheck if all your Steam games will work with Proton! Uses the official Steam API and the unofficial Proton API.\n\n\t0\t0\t0\nM0NsTeR77/csgo-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nozanhalis/Hi\n\n// ==UserScript== // @name CS GO LOUNGE BOT-Ozan Halis // @namespace http://csgolounge.com/ // @version 0.6.6 // @description Cs Go Lounge Hızlı BOT // @match http://csgolounge.com/* // @match http://dota2lounge.com/* // @updateURL h…\n\n\t0\t0\t0\nscoobertus/CSGO-DoubleBot\n\nNo description in the capture.\n\n\t0\t0\t0\nTradeal/CSGO-Jackpot-Bot\n\nNo description in the capture.\n\n\t0\t0\t0\nValvePython/artifact\n\nNo description in the capture.\n\n\t0\t0\t0\nVampire/CSGO-Roulette-Bot\n\nNo description in the capture.\n\n\t0\t0\t0\nvdemans/csgo-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nVocoreVideo/CSGODungeon-\n\nCSGO Jackpot\n\n\t0\t0\t0\nwayz-dev/csgofloat\n\nNo description in the capture.\n\n\t0\t0\t0\n\nCuplikan: 17 September 2026, 11:19:11 sebagaimana tertulis dalam sumber; zona waktu tidak disebutkan. Koleksi hubungan dibatasi dalam ekspor (banyak kategori berakhir pada 40). Jumlah kontributor dan pengembang fork mencapai 4,554 entri peran di seluruh 4,214 pasangan profil–repositori yang berbeda; sebuah profil dapat memiliki kedua peran tersebut. Nilai nol berarti tidak ada catatan yang tercatat dalam kategori tersebut. Nama repositori mungkin mencakup alias atau variasi huruf besar-kecil; jumlah total tetap mengikuti konvensi penghitungan sumber.\n\nAsal usul sumber\nDibuat dari berkas-berkas yang telah Anda kumpulkan.\nKesaksian dukungan\n2323/reddit_scams_ultra/steam_support_tickets_MEGA.json · baris 45, 58, 107, 110, 294\nCuplikan jaringan\nnetwork-repositories.csv · raw_data.json · overlaps.csv · summary.txt (jalur sumber historis tetap dipertahankan dalam manifes)\n\nManifest tersebut mencatat jalur sumber, ukuran byte, nilai hash SHA-256, serta posisi catatan yang dipilih. Rekaman mentah tetap dipisahkan dari hasil interpretasi penyelidikan.\n\nUnduh manifes sumber ↓",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam Bukti Penegakan Hukum — Catatan Pendukung & Jaringan Pengembang"
          },
          {
            "level": 2,
            "id": null,
            "text": "Baca pengaduan tersebut.Sertakan sumbernya."
          },
          {
            "level": 3,
            "id": null,
            "text": "Permanent sanction & closed appeals"
          },
          {
            "level": 4,
            "id": null,
            "text": "Permanently banned Steam account without a clear explanation, need help!"
          },
          {
            "level": 3,
            "id": null,
            "text": "Account recovery & a reported $10,000 loss"
          },
          {
            "level": 4,
            "id": null,
            "text": "Got $10k stollen from steam inventory due to steam' support fault."
          },
          {
            "level": 3,
            "id": null,
            "text": "A reported $500+ loss & template replies"
          },
          {
            "level": 4,
            "id": null,
            "text": "Funds stolen through steam market. Disappointed with Steam response.(or lackthereof)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam Guard & an item-restoration refusal"
          },
          {
            "level": 4,
            "id": null,
            "text": "Many people are losing item via clicking links where steam guard is enabled and steam support doesn't not restore items."
          },
          {
            "level": 3,
            "id": null,
            "text": "Selective enforcement & an unexplained ban"
          },
          {
            "level": 4,
            "id": null,
            "text": "🚨 Steam Bans Without Reason and Ignores Its Community — What’s Going On?"
          },
          {
            "level": 2,
            "id": null,
            "text": "Infrastruktur publik.Direkam dalam skala besar."
          },
          {
            "level": 2,
            "id": null,
            "text": "Dibuat dari berkas-berkas yang telah Anda kumpulkan."
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/id/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/id/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/selected-support-records.json",
          "https://phishdestroy.io/steam_dossier/id/investigation_part2.html#outsourcing-case",
          "https://www.reddit.com/r/ohnePixel/comments/1hahqx2/permanently_banned_steam_account_without_a_clear/",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://www.reddit.com/r/DotA2/comments/r55bd7/many_people_are_losing_item_via_clicking_links/",
          "https://www.reddit.com/r/SteamUncensored/comments/1kjt2fa/steam_bans_without_reason_and_ignores_its/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/network-repositories.csv",
          "https://github.com/alliedmodders/amxmodx",
          "https://github.com/alliedmodders/sourcemod",
          "https://github.com/DoctorMcKay/node-steam-user",
          "https://github.com/Facepunch/Facepunch.Steamworks",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://github.com/odota/core",
          "https://github.com/odota/dotaconstants",
          "https://github.com/odota/web",
          "https://github.com/splewis/get5",
          "https://github.com/SteamDatabase/FileDetectionRuleSets",
          "https://github.com/SteamRE/SteamKit",
          "https://github.com/ValveSoftware/dxvk",
          "https://github.com/ValveSoftware/GameNetworkingSockets",
          "https://github.com/ValveSoftware/gamescope",
          "https://github.com/ValveSoftware/Proton",
          "https://github.com/ValveSoftware/source-sdk-2013",
          "https://github.com/ValveSoftware/wine",
          "https://github.com/ValveSoftware/steam-devices",
          "https://github.com/ValveSoftware/steam-audio",
          "https://github.com/alliedmodders/metamod-source",
          "https://github.com/alliedmodders/sourcepawn",
          "https://github.com/ValveSoftware/Fossilize",
          "https://github.com/rlabrecque/Steamworks.NET",
          "https://github.com/ModDota/moddota.github.io",
          "https://github.com/odota/parser",
          "https://github.com/ValveSoftware/steam-for-linux",
          "https://github.com/SteamRE/DepotDownloader",
          "https://github.com/JustArchiNET/ASF-ui",
          "https://github.com/advancedfx/advancedfx",
          "https://github.com/alliedmodders/ambuild",
          "https://github.com/SteamDatabase/BrowserExtension",
          "https://github.com/odota/mobile",
          "https://github.com/ValvePython/steam",
          "https://github.com/skadistats/clarity",
          "https://github.com/SteamRE/open-steamworks",
          "https://github.com/ValveSoftware/Source-1-Games",
          "https://github.com/alliedmodders/hl2sdk",
          "https://github.com/SteamDatabase/steamdb.info-issues",
          "https://github.com/CSGOFloat/inspect",
          "https://github.com/ValveSoftware/SteamOS",
          "https://github.com/alliedmodders/source2mod",
          "https://github.com/smiley/steamapi",
          "https://github.com/SteamDatabase/GameTracking",
          "https://github.com/ValveSoftware/counter-strike_rules_and_regs",
          "https://github.com/ValveSoftware/openvr",
          "https://github.com/SteamDatabase/easy-markdown-editor",
          "https://github.com/ValveSoftware/Dota-2",
          "https://github.com/ValveSoftware/Dota2-Gameplay",
          "https://github.com/JustArchiNET/ArchiBot",
          "https://github.com/ztizzlegaming/CSGOWinBig",
          "https://github.com/JustArchiNET/mantis.justarchi.net",
          "https://github.com/odota/node-steam-user",
          "https://github.com/ModDota/TypeScriptAddonTemplate",
          "https://github.com/ValvePython/vdf",
          "https://github.com/alliedmodders/amtl",
          "https://github.com/ValvePython/dota2",
          "https://github.com/alliedmodders/stripper-source",
          "https://github.com/Allyans3/steam-market-api-v2",
          "https://github.com/ModDota/dota-tutorial",
          "https://github.com/odota/blog",
          "https://github.com/OpsecGuy/BetterGo",
          "https://github.com/pxvr-official/1",
          "https://github.com/Revadike/InternalSteamWebAPI",
          "https://github.com/JoeSzymkowiczFiveM/qb-lootcrate",
          "https://github.com/AbrarKL/MyRoulette.XYZ",
          "https://github.com/JustArchiNET/ASF-WebConfigGenerator",
          "https://github.com/ModDota/dota-data",
          "https://github.com/ModDota/TypeScriptDeclarations",
          "https://github.com/ModDota/API",
          "https://github.com/alliedmodders/cssdm",
          "https://github.com/SteamDatabase/steamstat.us",
          "https://github.com/c0deina/csgojackpotV2",
          "https://github.com/ValvePython/steamctl",
          "https://github.com/ValvePython/csgo",
          "https://github.com/BeepIsla/csgo-crash-exploit",
          "https://github.com/ValvePython/vpk",
          "https://github.com/alliedmodders/SM-SteamWorks",
          "https://github.com/SteamRE/Steam4NET",
          "https://github.com/alliedmodders/hl2sdk-manifests",
          "https://github.com/JustArchiNET/ASF-PluginTemplate",
          "https://github.com/ModDota/Dota2AIFramework",
          "https://github.com/Shkyyl/KeyChamp",
          "https://github.com/SteamDatabase/SteamMonitor",
          "https://github.com/Baterka/cslore.com",
          "https://github.com/SteamDatabase/SteamTokenDumper",
          "https://github.com/monoblocker/roulette",
          "https://github.com/zsith/launcher.user.js",
          "https://github.com/LincolnIT/CSGODouble-bot-automated",
          "https://github.com/vladpuz/steam-market",
          "https://github.com/mcgrizzz/Cstrike.bet",
          "https://github.com/odota/underlords-web",
          "https://github.com/SteamDatabase/SteamToTwitter",
          "https://github.com/ModDota/AbilityLuaSpellLibrary",
          "https://github.com/alvinl/bitskins",
          "https://github.com/b1naryth1ef/steamy",
          "https://github.com/kratos1812/Case-Opening",
          "https://github.com/odota/docs",
          "https://github.com/SteamDatabase/steam-advanced-access-fetch-players",
          "https://github.com/TheRioMiner/CsgoBetterExternalRaytrace",
          "https://github.com/alliedmodders/hl2sdk-mock",
          "https://github.com/christophersu/PySteamMarket",
          "https://github.com/Extremelyd1/Strat-Roulette",
          "https://github.com/giovanni-orciuolo/double-sdk",
          "https://github.com/JustArchiNET/Madness",
          "https://github.com/ModDota/TypescriptPanoramaDeclarations",
          "https://github.com/odota/rapier",
          "https://github.com/Vozn1akHero/CSGOCaseOpeningSimulator",
          "https://github.com/autarc/steam-store",
          "https://github.com/BETTING-CODE/awesome-esports-sites",
          "https://github.com/jonteohr/Better-Warden",
          "https://github.com/Ludzikk/CSGO-Gambling-Site",
          "https://github.com/ModDota/find-steam-app",
          "https://github.com/mprey/csgocact.us",
          "https://github.com/nezu-cc/ServerCrasher",
          "https://github.com/odota/testfiles",
          "https://github.com/odota/underlordsconstants",
          "https://github.com/SnaBe/node-steam-market-fetcher",
          "https://github.com/SteamDatabase/.github",
          "https://github.com/wolfcon/RIP-HLTV-BET",
          "https://github.com/alliedmodders/blaster.net",
          "https://github.com/catears124/CS2-Price-API",
          "https://github.com/ialakey/caseforge",
          "https://github.com/Ilusion9/csgo-fix-mapchange-crash-sm",
          "https://github.com/ismail0234/Benson-Map-Crash-Fixer",
          "https://github.com/jaxwilko/steam-market-api",
          "https://github.com/JustArchiNET/ArchiTag",
          "https://github.com/ModDota/DotaUI",
          "https://github.com/node-steam/market-pricing",
          "https://github.com/odota/media",
          "https://github.com/SergeyIvanovDevelop/Crypto-Steam-Platform",
          "https://github.com/Aareksio/csgodouble-floatchecker",
          "https://github.com/chinm4/CSGOdrop",
          "https://github.com/Cruze03/CSGO-Case-Opening-Prank",
          "https://github.com/Dhruva-Kapadia/CSGOTrollGG",
          "https://github.com/ErhanCSGO/CSGOPolygon-prediction",
          "https://github.com/Ev-Hoang/Bedrock-Chest-Case-Opening",
          "https://github.com/jmjp/csgo-roulette",
          "https://github.com/JustArchiNET/ArchiCrowdin",
          "https://github.com/LeonSK/WearMarketInspector",
          "https://github.com/maximgeerinck/csgo-gamble",
          "https://github.com/ModDota/BugTracker",
          "https://github.com/plwp/mma-betting",
          "https://github.com/Southsideswag16/Csgo-Gambling-Site",
          "https://github.com/tacyarg/csgofiesta-frontend-react",
          "https://github.com/Velorasse/Mutah-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-csmoney-csgoskins",
          "https://github.com/alliedmodders/am-github-artifact-webhook",
          "https://github.com/charamza/roulette",
          "https://github.com/Cruze03/CSGO-PugSetup-RoundRestore",
          "https://github.com/csgorol/CSGO-ROLL-Crash-Predictor",
          "https://github.com/FoxSerito/FOXWORLD_plugin_DoubleJump_CSGO",
          "https://github.com/hkehayovmoonbiz/CS2-Casino-Full-Source-Code",
          "https://github.com/JustZakary/steamstoreapi",
          "https://github.com/jzimr/steam-market-api",
          "https://github.com/Momohime/CSGO.Network-Jackpot-Coinflip",
          "https://github.com/nnjjswat/moneybot",
          "https://github.com/odota/carry",
          "https://github.com/odota/PublicMatchDataBot",
          "https://github.com/Orillio/CSGOBet.com",
          "https://github.com/ripexz/csgo-bet-alert",
          "https://github.com/rrpvm/lumen_sense-beta-deprecated-",
          "https://github.com/Ruthless222/csgoscore",
          "https://github.com/tfburns/CSGO-cases-PL",
          "https://github.com/TomDra/CSGO-Case-Data-Analysis",
          "https://github.com/ValvePython/dota2-wrappers",
          "https://github.com/ValvePython/teamfortress2-closed-captions",
          "https://github.com/VistaNetGTX/Cstrike.bet-",
          "https://github.com/wafflas/csgo-case-opening-simulator",
          "https://github.com/Admiral-Enigma/Le_Coinflip",
          "https://github.com/adryeljuliao/roulette-csgo",
          "https://github.com/AndreuTheG/csgo-coinflip-web",
          "https://github.com/asmilen/csgoDouble",
          "https://github.com/b1naryth1ef/csgofort",
          "https://github.com/Baterka/PrivateSteamBettingWebsite2024",
          "https://github.com/blackcaer/SteamTradeHandler",
          "https://github.com/BTheCoderr/theRounders",
          "https://github.com/CallumHemsley/KazeBot",
          "https://github.com/chrisjpm/CSGOJackpotTemplate",
          "https://github.com/colinsenner/valve-bug-bounty",
          "https://github.com/coryypeters/nrl-odds-intelligence-pipeline",
          "https://github.com/deissh/dev-csgoduo",
          "https://github.com/dom1torii/even-better-font-manager",
          "https://github.com/DONnicov/CSGO-crash-black-screen-",
          "https://github.com/DoubleBoters/CsgoDouble",
          "https://github.com/downarowiczd/DoubleBot",
          "https://github.com/ErayBahar/steammarketscraper",
          "https://github.com/fairydarkness/SteamwebmailAPI",
          "https://github.com/FAQU2/CSGO-Coinflip-MyJailShop",
          "https://github.com/FlamesONE/csgo-case-opening",
          "https://github.com/FunnyRain/csgorun-crash-watch",
          "https://github.com/geohdgio/Venatus-Autenticator",
          "https://github.com/hakanstarlord/steam-bot",
          "https://github.com/HvH-gg/CSGO-Item-CrashFix",
          "https://github.com/HvH-gg/CSGO-NetMsg-CrashFix",
          "https://github.com/isybycnsmam/SteamLibrary",
          "https://github.com/ItsTangerine/SteamApis.Net",
          "https://github.com/JustArchiNET/JustArchi.net",
          "https://github.com/kiri-osint/CS2-Info-Hub-Bot",
          "https://github.com/Koshkaj/monte",
          "https://github.com/madsab/CaseOpening",
          "https://github.com/man90es/steamcardexchange-api",
          "https://github.com/MattPua/steam-unofficial-docs",
          "https://github.com/Metallist1/Portfolio.CsgoWinGambleProject",
          "https://github.com/mikebobadilla/csgo-jackpot",
          "https://github.com/mikebobadilla/meteor-csgojackpot",
          "https://github.com/ModDota/D2VDump",
          "https://github.com/ModDota/DotaTracking",
          "https://github.com/ModDota/eslint-config",
          "https://github.com/mr-codinglv/Casino-script",
          "https://github.com/MrKeelik/MrKeel",
          "https://github.com/noahlatzel/CSGORollHelper",
          "https://github.com/oddsgpt/oddsgpt-market-intelligence",
          "https://github.com/oEXU/csgo-server-crasher",
          "https://github.com/PrdTTony/CSGO-Roulette",
          "https://github.com/r-adamski/csgo-jackpot",
          "https://github.com/Sahotallo/Turan-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-Skinbaron-hellcase",
          "https://github.com/samuelcsouza/steam-marketplace-api",
          "https://github.com/SKINSTRACK/CS2-Price-API",
          "https://github.com/snmtriet/CSGO-Casino-Full-Source-Code",
          "https://github.com/SteamRE/homebrew-tools",
          "https://github.com/SteamRE/opensteamworks.org",
          "https://github.com/TheQuack45/CsgoCaseOpenProgram",
          "https://github.com/TLClassless/StratRouletteCSGO",
          "https://github.com/tomasoom/csgoCaseOpening",
          "https://github.com/vitaliy-evsyukov/steamgifts-autobet-bookmarklet",
          "https://github.com/XpravdaX/RouletteCSGO",
          "https://github.com/YuiKasumii/steam_api_unofficial",
          "https://github.com/Zexuz/Steam-Betting",
          "https://github.com/ANK-RULZZ/steam-jackpot-site",
          "https://github.com/asmilen/CsgoDoubleVS",
          "https://github.com/CORNOODOSADAS/CSGOWeed",
          "https://github.com/CSGOApple/csgoapple",
          "https://github.com/CSGOFAST/csgofast-api",
          "https://github.com/Donakall/csgoDoublebot",
          "https://github.com/fedor-selivanov/csgo-fast-roulette",
          "https://github.com/foldageros/csgod",
          "https://github.com/gmod-gambling/gmod-gambling",
          "https://github.com/ierome/CSGOBoss-BackEnd",
          "https://github.com/jamienp1/CSGODOUBLE-BOT-AUTO",
          "https://github.com/JEYONER/CSGOTOXIC",
          "https://github.com/kalrish/csgo-jackpot",
          "https://github.com/krys12345/roulettee",
          "https://github.com/LilDuggiMuffi/CSGODouble-Working-Bot",
          "https://github.com/LyricLy/Steam2Proton",
          "https://github.com/M0NsTeR77/csgo-roulette",
          "https://github.com/ozanhalis/Hi",
          "https://github.com/scoobertus/CSGO-DoubleBot",
          "https://github.com/Tradeal/CSGO-Jackpot-Bot",
          "https://github.com/ValvePython/artifact",
          "https://github.com/Vampire/CSGO-Roulette-Bot",
          "https://github.com/vdemans/csgo-roulette",
          "https://github.com/VocoreVideo/CSGODungeon-",
          "https://github.com/wayz-dev/csgofloat",
          "https://phishdestroy.io/steam_dossier/output_steam_network/raw_data.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/enforcement-source-manifest.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/id/steam_enforcement_evidence.content.json",
      "export_json_sha256": "44ee8f175934a40e8ff8f0e16543da4401966098f84133dfe42911f20d2d9aae"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "id/steam_evidence_archive.html",
      "language": "id",
      "title": "Periksa sumber-sumbernya — Dokumen \"Steam\"",
      "source_url": "https://phishdestroy.io/steam_dossier/id/steam_evidence_archive",
      "source_html_sha256": "4b7734e5914d35e683962765e671547c3d419c7d84e02b1db36cedb4f2b1f8d4",
      "exported_at": "2026-09-29T00:22:36.979Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "steam_evidence_archive.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/id/steam_evidence_archive.pdf?v=print-20260929-v5",
        "sha256": "9328c30aca8decb74b7c4df7b7134fa282b1b56dbc9995557b080d88f957c19f",
        "bytes": 61957,
        "pages": 4
      },
      "integrity": {
        "signed_object": "steam_evidence_archive.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "steam_evidence_archive.content.json.asc",
        "digest_file": "steam_evidence_archive.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify steam_evidence_archive.content.json.asc steam_evidence_archive.content.json",
          "sha256sum -c steam_evidence_archive.content.json.sha256"
        ]
      },
      "content": {
        "text": "BAHAN PENYELIDIKAN / PENGUMPULAN SUMBER 002\nSteam Arsip Bukti — Catatan yang Bersumber dari 16,319\n\nSetiap klaim. Kembali ke sumbernya.\n\nAPA YANG DIBUKTIKAN OLEH BAGIAN INI\n\nArsip forensik ini mengindeks catatan sumber primer 16,319—yang mencakup dokumentasi Komunitas Pengembang Valve, masalah publik di GitHub, keluhan yang terverifikasi di Trustpilot, serta laporan forum yang diarsipkan—dengan hash kriptografis dan log asal-usul. Arsip ini menyediakan basis bukti yang dapat diperiksa untuk menunjukkan kerentanan platform yang dapat diulang, penghentian dukungan API yang tidak terdokumentasi, serta keluhan konsumen yang terus-menerus terkait akun yang dibajak.\n\n← Kembali ke Ringkasan Eksekutif\n\nTemukan catatan di balik sebuah klaim. Saring berdasarkan sumber, buka teks lengkapnya, dan ikuti tautan aslinya. Baris-baris sumber bisa tumpang tindih; sebuah catatan bukanlah insiden yang telah diverifikasi.\n\nKembali ke penyelidikan ↗\n354TRUSTPILOT / BARIS SUMBER\n208REDDIT / BARIS SUMBER\n705GITHUB / BARIS KODE\n15,302MASTER CSV / BARIS SUMBER\n16,319 REKOR — RINCIAN BERDASARKAN JENIS PLATFORM\n\nAsal-usul kategori Wiki (catatan 7,620 · 46.7%): Data ini diambil dari Komunitas PengembangValve (developer.valvesoftware.com), Dokumentasi/FAQ SteamDB, serta wiki komunitas game (Liquipedia CS/Dota dan wiki Fandom Steam) melalui tangkapan layar otomatis WARC dan titik akhir MediaWiki API antara Agustus 2024 dan September 2026.. Semua entri 7,620 telah sepenuhnya diintegrasikan ke dalam ekspor CSV Utama (TOTAL_SKANDAL_KATUP_DATABASE_UTAMA.csv).\n\nWiki\n7,620\nReddit\n5,635\nGitHub\n2,395\nTrustpilot\n393\nWeb\n276\n9,116 dari 16,319 catatan (55.8%) berisi referensi ke Steam / Valve\n\nArsip yang dapat dicari ini dibangun di atas 2026-09-17 dari ekspor sumber yang tercantum di atas. Ekspor master baris “40,448-” yang terpisah dan digunakan di bagian lain dalam dokumen ini memiliki cakupan yang berbeda. Lihat membuat manifes untuk jumlah data dalam arsip ini; catatan-catatan tersebut dapat tumpang tindih dan bukan merupakan kejadian yang unik.\n\nPLATFORM SUMBER\nPENGUMPULAN SUMBER\nSteam / Valve mentions\nRepositori pencocokan teks atau repositori \"Valve\"Teks yang hilang / dihapus\n16,569 baris sumber\n16,319 catatan yang berbeda\n249 baris yang duplikat telah digabungkan\n1 baris dikecualikan\nLihat berkas aslinya ↘\n★TRUSTPILOT2015-10-16#1RATING 1/5\n\nSteam is the biggest PC gaming platform without a doubt. A power which could be abused but Steam for the most part doesn't. Overall a definite download for any moden digital age PC gamer. It mu... See more\n\nMA · 7 source copies\n★TRUSTPILOT2021-06-18#2RATING 1/5\n\nThey scam people for money, dont believe me? Read this Source: Steam Subscribers/User Agreement NO GUARANTEES TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, NEITHER VALVE NOR ITS AFFILIA... See more\n\nWF · 7 source copies\n★TRUSTPILOT2016-10-28#3RATING 1/5\n\nSupport on site is terrible. Refunds not happend yet, despite games not working. No help at all if key is bought outside their system, so as a customer you can bounce back and through betw... See more\n\nPE · 7 source copies\n★TRUSTPILOT2021-09-27#4RATING 1/5\n\nThey are an amazing company!! My boyfriend paid for and downloaded a game without realizing it wasn’t the version he wanted. When he reached out, they gave him a full refund and responded in the same... See more\n\nVH · 7 source copies\n★TRUSTPILOT2026-07-20#5RATING 1/5\n\nI’ve used Steam for years, but lately, their sales have really lost their edge. I was hoping to score some solid discounts, but many games still feel overpriced, even during sales. Plus, the support response times can be frustratingly slow when issues arise.\n\nCR\n★TRUSTPILOT2025-12-10#6RATING 1/5\n\nI new here , but all my firends had great experience with this platform . They can make money\n\nZeinab Nematollahi\n★TRUSTPILOT2025-11-18#7RATING 1/5TEXT UNAVAILABLE\n\nNo text was included in the source record.\n\nEM\n★TRUSTPILOT2025-10-21#8RATING 1/5\n\nusing steam for over a decade and i have no words how good the platform is. some friends recommended it to me back in 2015 when we wanted to play csgo together and since then im loggin on it on a daily basis to check new games\n\nTrustpilot\n★TRUSTPILOT2025-05-09#9RATING 1/5\n\nSupport are never able to help you and only able to redicrect you to public linkBreaking there own TOSNot able to provider a refundNot able to provide a safe place for gamingBase on the game you play you can get scam.\n\nSym Link · 7 source copies\n★TRUSTPILOT2025-05-09#10RATING 1/5TEXT UNAVAILABLE\n\nNo text was included in the source record.\n\nHearnius\n★TRUSTPILOT2024-12-30#11RATING 1/5\n\nThis company allowed a single phishing scammer 76561199443342045 in 100's of its user community chat rooms \"Steam Chat\" the whole week of Winter Sales, 12-23-2024 - 2025 to spam spaceintrader a scam phishing website.Don't support Valve & Steam that support sca…\n\nFR · 7 source copies\n★TRUSTPILOT2024-11-15#12RATING 1/5\n\nVery realiable! Ive never had an issue over the 11 years ive had steam.\n\nJM\nBuild dan berkas sumbernya\n\nArsip ini menggabungkan baris-baris duplikat dari 249 dan mengesampingkan satu baris dari data masukan 16,569, sehingga tersisa 16,319 catatan yang berbeda. Sebuah catatan dapat menggambarkan peristiwa yang sudah tercakup dalam catatan lain. Pencarian mencakup judul, penulis, label sumber, dan kutipan yang ditampilkan; teks lengkap yang tersimpan akan terbuka bersama setiap catatan.\n\nUnduh empat file ekspor sumber ↓Jumlah file & nilai hash SHA-256 ↗Manifest versi asli ↗\n\nPaket tersebut berisi data ekspor yang berhasil dipulihkan, yang sesuai dengan jumlah baris pada build tersebut serta tiga jalur JSON yang tercatat. Build asli tidak mencatat hash input maupun jalur CSV utama; dokumen manifest yang menyertainya memuat daftar berkas yang berhasil dipulihkan serta hasil perbandingan dengan indeks yang telah dipublikasikan.\n\nTrustpilot · steam_support_reviews.json354 baris · Ekspor JSON\nReddit · reddit_censored_forensics.json208 baris · Ekspor JSON\nGitHub · valve_ignored_bugs.json705 baris · Ekspor JSON; nama file adalah label pengumpul\nMaster · TOTAL_VALVE_SCANDALS_MASTER_DB.csv15,302 baris · Ekspor CSV yang digunakan untuk perbandingan\nDaftar Perkara Pengadilan · UNSEALED_EXHIBITS_AND_AML_DOSSIER.mdWolfire melawan Valve: email yang telah dibuka segelnya, kesaksian Gabe Newell, pengakuan AML pada 2019 Oktober\nFakta Utama · FACTS_AND_CITATIONS_DATABASE.md1,638 kutipan terverifikasi yang terpisah di berbagai bidang antitrust dan keaman35\nArsip Dukungan · support_canned_refusals.html1,505 catatan tiket · tangkapan layar yang disimpan di 137 · Pencarian instan secara langsung\nKolom catatan, teks yang hilang, dan ekspor yang tumpang tindih\n\nTanggal, peringkat, kategori, dan status terbitan disalin persis seperti pada ekspor sumber. URL yang hilang tetap tidak tercantum. Penanda “[dihapus]” atau “[dihapus]” tidak menunjukkan siapa yang menghapus postingan tersebut atau alasannya. Filter Steam / Valve menggunakan pencocokan teks, bukan penilaian relevansi.\n\n“Ekspor entri” mengunduh entri indeks beserta cuplikannya; “Unduh catatan” mencakup teks lengkap yang telah disimpan. Yang terpisah 40,448-baris utama CSV dan 1,690-baris GitHub CSV yang menjadi faktor utama dalam rilis ini adalah peningkatan volume ekspor, bukan jumlah sumber.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam Arsip Bukti — Catatan yang Bersumber dari 16,319"
          },
          {
            "level": 2,
            "id": null,
            "text": "PLATFORM SUMBER"
          },
          {
            "level": 2,
            "id": null,
            "text": "Build dan berkas sumbernya"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/id/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/id/",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/TOTAL_VALVE_SCANDALS_MASTER_DB.csv",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive_manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive-inputs.zip",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive-inputs-manifest.json",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/unsealed_legal_and_aml/UNSEALED_EXHIBITS_AND_AML_DOSSIER.md",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/forensic_facts_1000/FACTS_AND_CITATIONS_DATABASE.md",
          "https://phishdestroy.io/steam_dossier/id/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/github_valve_unpatched_bugs.csv"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/id/steam_evidence_archive.content.json",
      "export_json_sha256": "fe506dcc323a0e6631c5798239ee60cd98acd770226c63089d38f277efda8696"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "id/support_canned_refusals.html",
      "language": "id",
      "title": "Steam Arsip Penolakan Dukungan & Tanggapan Standar — Dokumen Kasus “Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/id/support_canned_refusals",
      "source_html_sha256": "17fdc9bf974f10fc29af88b8ed188e37f34b0f341b5fef565a478de64929077e",
      "exported_at": "2026-09-29T00:22:37.716Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "support_canned_refusals.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/id/support_canned_refusals.pdf?v=print-20260929-v5",
        "sha256": "f7a6cfc8ee2648817f3ac0373524bda397cddf74d73334969f7fa505f2219b8f",
        "bytes": 59424,
        "pages": 2
      },
      "integrity": {
        "signed_object": "support_canned_refusals.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "support_canned_refusals.content.json.asc",
        "digest_file": "support_canned_refusals.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify support_canned_refusals.content.json.asc support_canned_refusals.content.json",
          "sha256sum -c support_canned_refusals.content.json.sha256"
        ]
      },
      "content": {
        "text": "APA YANG DIBUKTIKAN OLEH BAGIAN INI\n\nRepositori ini mendokumentasikan tangkapan layar asli yang disimpan di 137 serta permohonan banding korban yang telah diaudit di 1,505, yang merinci proses penanganan tiket dukungan otomatis di Valve. Hal ini membuktikan bahwa ketika akun diretas melalui pengalihan OpenID atau pembuatan kunci API tanpa izin, tim dukungan Steam secara sistematis menggunakan tanggapan penolakan baku tanpa melakukan penyelidikan teknis. Dengan secara tegas menolak pemulihan barang atau pengungkapan jejak audit, platform ini mengalihkan seluruh tanggung jawab atas kelemahan otentikasi struktural kepada pemilik akun yang diretas.\n\nSemua tangkapan layar merupakan hasil pengambilan dari pihak ketiga. Hak cipta dan konten tetap menjadi milik masing-masing penulis dan platformnya (pengguna Reddit, penulis Komunitas Steam, pengulas Trustpilot, X, dan pengunggah YouTube). Tangkapan layar tersebut disajikan semata-mata untuk tujuan identifikasi dan pelaporan demi kepentingan umum; tidak ada klaim kepemilikan apa pun. Setiap tangkapan layar dilengkapi tautan ke sumber aslinya.\n\nFigures reported on the source page\nMeasure\tReported value\tScope\nCatatan Tertulis\t1505\tPermohonan banding korban yang terverifikasi dan utas tiket\nTangkapan Layar yang Disimpan\t137\tSalinan tiket beresolusi tinggi disimpan secara lokal\nTingkat Pemulihan\t0.0%\tPermohonan peninjauan kembali dikabulkan dalam kasus penyanderaan perdagangan yang dipimpin olehAPI\nDuplikasi Template\t100%\tPenggunaan kembali naskah verbatim di antara para staf (Ilya, Roger, Maverick)\nBukti Forensik: Tiga Pilar Utama Penolakan Dukungan\nPILLAR 01 · PENERIMAAN MAHASISWABukti R—014\nPengakuan Roger: Serangan MitM pada API Telah Dikonfirmasi\n\nDalam tanggapan tiket #1cp582i, Steam, staf dukungan \"Roger\" mengakui secara tertulis bahwa para penyerang membatalkan transaksi yang sah melalui API dan menggantinya dengan bot tiruan dalam hitungan milidetik, namun menolak untuk mengembalikan barang-barang tersebut dan menyarankan korban untuk mencari \"teknisi PC lokal\".\n\nPeriksa Surat Penerimaan ↗\nPILAR 02 · ESKALASIBukti R-012\n7-Perdagangan Harian: Menahan Diri\n\nSeorang korban memberikan SteamID64 dari akun-akun peretas tersebut selama periode penangguhan perdagangan harian di 7-. Staf dukungan \"Artem\" dan \"Ilya\" menolak untuk membekukan item-item yang dicuri dengan alasan kelangkaan item virtual, dan menutup tiket tersebut menggunakan templat otomatis.\n\nPeriksa Transkrip Multi-Staf ↗\nPILAR 03 · KEBIJAKANBukti R—002\nKekurangan Pasokan di Pasar Terkait Hak Milik Properti\n\nKebijakan Pemulihan Item resmi Valve secara tegas menyatakan bahwa item tidak akan dikembalikan karena memulihkannya akan \"mengurangi kelangkaan dan memicu inflasi dalam ekonomi, sehingga menurunkan nilai item di Pasar Komunitas\".\n\nLihat Tangkapan Layar Kebijakan ↗\nSejarah Awal · 22 Maret 2018 hingga 2026\nLampiran H-003 · 8-Permukaan Serangan yang Belum Diperbaiki Selama Setahun\nSubstitusi Perdagangan Tertua yang Tercatat (22 Maret 2018)\n\nTepat satu minggu sebelum Valve memberlakukan kebijakan masa tunggu perdagangan harian “7-” yang kontroversial untuk item Counter-Strike, komunitas perdagangan menemukan contoh-contoh pertama dari Steam API Web: Eksploitasi Pengalihan Lalu Lintas. Para penyerang membajak sesi web untuk menghasilkan kunci API yang tidak sah di steamcommunity.com/dev/apikey tanpa konfirmasi FA (2) seluler, sehingga memungkinkan bot untuk membatalkan dan menukar transaksi secara real time.\n\nPeringatan Iklan Layanan Masyarakat \"March2018\": \"Para penipu dapat secara otomatis mendeteksi tawaran perdagangan ini dan akan menolaknya di akunmu, karena mereka memiliki kunci Steam API milikmu. Bot penipu tersebut kini akan mengirimkan tawaran perdagangan untuk skin yang sama... dan kamu tidak akan menyadari perbedaannya!\"\nJalur Jejak Sejarah\n22 2018: Maret Pertukaran \"API\" yang pertama kali tercatat\n2019: Dukungan ini menstandarkan upaya pencegahan \"malware\"\n2020: Skrip \"Menutup permintaan bantuan\" telah diperkuat\n2022–2026: Otomatisasi phishing BitB & QR\nBuka Utas Reddit Asli “2018” ↗\nPrimary sources\n\n137 gallery cards refer to 78 distinct primary URLs. Images and repeated exhibit captions are omitted from this reading edition.\n\nFull visual archive and original captures",
        "headings": [
          {
            "level": 2,
            "id": null,
            "text": "Figures reported on the source page"
          },
          {
            "level": 2,
            "id": null,
            "text": "Bukti Forensik: Tiga Pilar Utama Penolakan Dukungan"
          },
          {
            "level": 3,
            "id": null,
            "text": "Pengakuan Roger: Serangan MitM pada API Telah Dikonfirmasi"
          },
          {
            "level": 3,
            "id": null,
            "text": "7-Perdagangan Harian: Menahan Diri"
          },
          {
            "level": 3,
            "id": null,
            "text": "Kekurangan Pasokan di Pasar Terkait Hak Milik Properti"
          },
          {
            "level": 3,
            "id": null,
            "text": "Substitusi Perdagangan Tertua yang Tercatat (22 Maret 2018)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Primary sources"
          }
        ],
        "links": [
          "https://www.reddit.com/r/csgo/comments/1cp582i/i_got_api_scammed_what_do_i_do_now/",
          "https://www.reddit.com/r/DotA2/comments/1e5ovy4/my_account_was_hacked_and_steam_support_refuse/",
          "https://www.reddit.com/r/Steam/comments/3b2abd/steam_will_no_longer_restore_scammed_items_item/",
          "https://www.reddit.com/r/GlobalOffensiveTrade/comments/863tk1/psa_urgent_huge_scam_happening_read_here_how_to",
          "https://phishdestroy.io/steam_dossier/id/support_canned_refusals#gallery-grid"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/id/support_canned_refusals.content.json",
      "export_json_sha256": "a2aa70324447fd95142893f8ac6dd7128ee87a3880ab7e852e688b43728d820e"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "id/valve_scandals_registry.html",
      "language": "id",
      "title": "Valve Daftar Skandal — Dokumen “Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/id/valve_scandals_registry",
      "source_html_sha256": "65a019a70e8dab457f985eb35435706a5d92c3dba470512439622c6774aefa6b",
      "exported_at": "2026-09-29T00:22:38.005Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "valve_scandals_registry.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/id/valve_scandals_registry.pdf?v=print-20260929-v5",
        "sha256": "4e0705bd9549445cb4357d8a66cacbb3a758e1c535efc4def076725409a55931",
        "bytes": 62313,
        "pages": 6
      },
      "integrity": {
        "signed_object": "valve_scandals_registry.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "valve_scandals_registry.content.json.asc",
        "digest_file": "valve_scandals_registry.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify valve_scandals_registry.content.json.asc valve_scandals_registry.content.json",
          "sha256sum -c valve_scandals_registry.content.json.sha256"
        ]
      },
      "content": {
        "text": "Arsip skandal utama\nValve Daftar Utama Skandal — 160 Insiden yang Telah Dikonfirmasi\nDATA SUMBER (MENTAH): 11,768\n\nTelah dilaporkan. Sumbernya sudah diketahui. Masih dalam penyelidikan.\n\nAPA YANG DIBUKTIKAN OLEH BAGIAN INI\n\nDaftar induk ini mengumpulkan 160 catatan utama yang telah diverifikasi secara independen, yang merinci kelemahan platform yang terus-menerus terjadi, laporan komunitas yang dihapus, serta kegagalan layanan dukungan konsumen yang belum ditangani di seluruh ekosistem Valve. Mencakup pengajuan sengketa yang terverifikasi di Trustpilot, tiket masalah keamanan GitHub yang telah diarsipkan, serta proses hukum yang dilakukan oleh pihak regulator, daftar ini membuktikan adanya gangguan sistemik yang berulang dalam pemulihan akun dan penyelesaian sengketa pelanggan.\n\n← Kembali ke Ringkasan Eksekutif\n\n160 catatan yang terkumpul: layanan dukungan yang dinilai oleh para penggunanya, utas diskusi yang tidak lagi terlihat, kelemahan platform yang telah dilaporkan namun diabaikan, serta insiden-insiden yang telah harus dipertanggungjawabkan oleh Valve. Tidak ada satu pun di sini yang merupakan interpretasi kami — setiap baris mencantumkan sumber aslinya. Buka salah satunya dan bacalah sendiri.\n\nCatatan Sumber\n11,768\nDi seluruh kategori\nKelemahan Platform\n3,372\nKelemahan platform yang dilaporkan oleh komunitas\nThread yang Disensor\n109\nPostingan Reddit yang dihapus oleh moderator\nPengaduan Terkait Dukungan\n471\nKeluhan yang telah diverifikasi di Trustpilot\nKelayakan penegakan\nPemblokiran domain host otentikasi\n\nPemblokiran host otentikasi OpenID di tingkat domain secara teknis mudah diterapkan: begitu suatu sumber daya diblokir dari pengalihan login Steam, domain pihak ketiga yang bertindak sebagai proxy otentikasi untuk sumber daya yang sama tersebut dapat disaring menggunakan aturan yang sama. Pembahasan terperinci mengenai kelayakan implementasi disajikan dalam dokumen utama.\n\nLihat kelayakan penegakan hukum dalam berkas tersebut →\nKategori: Keluhan Dukungan Trustpilot (Escalasi Negatif yang Telah Disaring)176 catatan sumber yang cocok · duplikat disembunyikan\nConsumer Complaint2026-07-20\nAuthor: C***\n\nI’ve used Steam for years, but lately, their sales have really lost their edge. I was hoping to score some solid discounts, but many games still feel overpriced, even during sales. Plus, the support response times can be frustratingly slow when issues arise.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2026-07-20\nConsumer Complaint2025-05-09\nAuthor: S*** L***\n\nSupport are never able to help you and only able to redicrect you to public linkBreaking there own TOSNot able to provider a refundNot able to provide a safe place for gamingBase on the game you play you can get scam.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2025-05-09\nConsumer Complaint2024-12-30\nAuthor: F***\n\nThis company allowed a single phishing scammer 7656…2045 in 100's of its user community chat rooms \"Steam Chat\" the whole week of Winter Sales, 12-23-2024 - 2025 to spam spaceintrader a scam phishing website.Don't support Valve & Steam that support scams. Don't give your log in credentials to account hijacking scammers. This company also allows engagements of commercial advertising / spam for gambling in violation of its own Rules and Guidelines / Online Conduct. 7656…5023 proof - groups/deskinsfans key drop advertising, thanks TannerfromKD and Valve!*\"The Consumer Review Fairness Act (CRFA) protects people’s ability to share their honest opinions about a business’s products, services, or conduct, in any forum, including social media. The law protects a broad variety of honest consumer assessments, including online reviews, social media posts, uploaded photos, videos, etc. And it doesn’t just cover product reviews. It also applies to consumer evaluations of a company\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2024-12-30\nConsumer Complaint2024-07-31\nAuthor: A***\n\nhorrible company.randomly you get \"This account may have been accessed by someone else.\"this happened to me 3 times.the 3rd time they wanted a cd key.a spent useless cd key that nobody has any reason to keep laying around.i gave them the paypal bill for my first purchase back in 2015.i gave them a bill for my first phone number ever on the account.i still got the same email attached to the account.this company is literally a scam. nothing but a scam.they randomly claim you been accessed somewhere else and then require you to give them information no reasonable person would ever have, if not your done and have to rebuy everything.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2024-07-31\nConsumer Complaint2023-12-09\nAuthor: K***\n\nHad 288 euros in steam wallet, someone hacked my account even with two step verification, write a steam support for help but only answer was if something is spent in community market they can’t help.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2023-12-09\nConsumer Complaint2023-09-26\nAuthor: J***\n\nI was banned for saying \"Who let grandma on the PC\"and another for simply calling someone ignorant.Power tripping mods, devs who don't care, steam doesn't care. Yet allows racism/trolling/etc Fk steam, its a joke now.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2023-09-26\nConsumer Complaint2022-08-31\nAuthor: Anonymous\n\nSteam community is plain bad for a various reasons:1. Steam forums are a big mess, for example they allow users to post in any language and as result you get jumbled mess with posts in foreign languages together with English language posts. For example, If you check CS GO forums, you'll see half of posts are in Russian and half in English. I don't understand why such a big and international company would leave their forums so unorganized like that. All other normal companies have English only language allowed which is an international language and sometimes subforums for other languages like German, French and etc... so if French people want to post in French they go specifically in that sub-forum. But no, Steam doesn't care about this. Their forums is a one big mess.2. Moderation is biased and joke. I don't understand why such a big company like Steam can't afford to hire people for moderation and pay them. Instead they just recruit random people for moderation who do it for free and\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2022-08-31\nConsumer Complaint2022-05-28\nAuthor: J***\n\nThe login code never arrives. I hate Steam.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2022-05-28\nConsumer Complaint2021-11-08\nAuthor: N***\n\nThe service is terrible, I only signed up because I really like the game I wanted, but the rest is terrible, I hope to get something better soon.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-11-08\nConsumer Complaint2021-06-18\nAuthor: W***\n\nThey scam people for money, dont believe me? Read thisSource: Steam Subscribers/User Agreement NO GUARANTEESTO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, NEITHER VALVE NOR ITS AFFILIATES GUARANTEE CONTINUOUS, ERROR-FREE, VIRUS-FREE OR SECURE OPERATION AND ACCESS TO STEAM, THE CONTENT AND SERVICES, YOUR ACCOUNT AND/OR YOUR SUBSCRIPTION(S) OR ANY INFORMATION AVAILABLE IN CONNECTION THEREWITH.In short: You got a virus or your data leaked because of our software? Whoopsies we dont care, that isnt even legal or the last of their scammy stuff...\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-06-18\nConsumer Complaint2021-05-14\nAuthor: B***\n\nThe support is one of the worst I've ever seen.Useless support team.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-05-14\nConsumer Complaint2020-04-02\nAuthor: J***\n\nSteamcommunity has 15% fees, 15!!!!\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2020-04-02\nConsumer Complaint2020-03-27\nAuthor: H***\n\nWhat can I say? the support is one of the worst I've ever seen maybe the FUNCOM is much worse. If you tell the true on the steam forum you just got a BAN even if what you said did not violated the rules of the forum.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2020-03-27\nConsumer Complaint2018-03-16\nAuthor: B***\n\ndon't sign up will stick on your computer will kill your pc power you can't remove it from your pc even you deleted it will stay woking in the system\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2018-03-16\nConsumer Complaint2016-12-27\nAuthor: J***\n\nIn bloddy hate their page it's tiresome, it's in no way intuitive. I tried reaching out for support, but that is a maze.I'm simply trying to log in and redeem a key of a product I already bought, their search function is a joke. I f*u*c*k*i*n*g hate them. The layout is not like the how to video from the dealer, this can be done much simpler. I don't frigin care aboutn what other titles you have in store or what genre, I just want to redeem my key and install.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-12-27\nConsumer Complaint2016-10-28\nAuthor: P***\n\nSupport on site is terrible.Refunds not happend yet, despite games not working.No help at all if key is bought outside their system, so as a customer you can bounce back and through between bad support systems?? I wait for some other companies to compete in this market, for this can't be the best we as customers can expect.And do put an email up to find, instead of this stuppid website where you spend so long time trying to find a solution on, instead of a simple mail. Often the problem is not there, or if it's there just saying no help here???I need a response\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-10-28\nConsumer Complaint2016-06-26\nAuthor: V*** W***\n\nUseless support as always!\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-06-26\nConsumer Complaint2014-07-01\nAuthor: J***\n\nexpensive, and support team not willing to cooperate\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2014-07-01\nConsumer Complaint2014-04-15\nAuthor: B***\n\nWhen you pay for a program, you expect it too work. cant not buy or anything and have written to valve. but there is not a being done a damn thing abut it..\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2014-04-15\nConsumer Complaint2026-09-03\nAuthor: M***\n\nWorst platform ever wont give me a refund even though a game is unplayable because of bugs I won't ever be using the crap platform again I hope the platform breaks down for good piece fo crao\n\nTarget Domain: steamcommunity.com / steampowered.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2026-09-03\n\nTidak ada catatan yang sesuai\n\nCoba sesuaikan kueri yang sedang aktif atau periksa tab kategori yang lain.\n\n1 / 9",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Valve Daftar Utama Skandal — 160 Insiden yang Telah Dikonfirmasi"
          },
          {
            "level": 2,
            "id": null,
            "text": "Pemblokiran domain host otentikasi"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: C***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: S*** L***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: F***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: A***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: K***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: Anonymous"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: N***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: W***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: H***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: P***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: V*** W***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: M***"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/id/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/id/#autoban-feasibility-section",
          "https://www.trustpilot.com/review/steamcommunity.com"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/id/valve_scandals_registry.content.json",
      "export_json_sha256": "4331bc678855ae4833fd14811c9b725a457a240415a2bc0bf5fba71bb0ca841f"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "id/output_steam_network/index.html",
      "language": "id",
      "title": "Arsitektur, Bukan Eksploitasi: Jaringan Otomatisasi — Laporan “Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/id/output_steam_network/index",
      "source_html_sha256": "32b40c34dfb38f235ca8022f12ed3578ac170b2e500d57f073a1077303f469c3",
      "exported_at": "2026-09-29T00:22:38.584Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__index.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/id/output_steam_network__index.pdf?v=print-20260929-v5",
        "sha256": "e8f87b4357c3f0d93de31f298f322769070e16ac16f8cb22e3dfc7b2444c4e6a",
        "bytes": 66497,
        "pages": 3
      },
      "integrity": {
        "signed_object": "output_steam_network__index.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__index.content.json.asc",
        "digest_file": "output_steam_network__index.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__index.content.json.asc output_steam_network__index.content.json",
          "sha256sum -c output_steam_network__index.content.json.sha256"
        ]
      },
      "content": {
        "text": "Lampiran VII · Analisis Arsitektur Teknis\nSteam Arsitektur Jaringan — Ketepatan Protokol & Analisis Ekosistem\n\nOtomatisasi merupakan Arsitektur dari Valve. Bukan Eksploit.\n\nAPA YANG DIBUKTIKAN OLEH BAGIAN INI\n\nModul ini memetakan topologi teknis repositori pengembang 252, profil 3,320GitHub, serta pasangan kontributor 4,214 yang menjadi landasan ekosistem otomatisasi Steam. Modul ini membuktikan bahwa otomatisasi pihak ketiga bergantung pada protokol Connection Manager resmi Valve, skema Protobuf, dan Web API tanpa kode eksploitasi. Dengan merancang token konfirmasi Guard algoritmik Steam dan memungut biaya transaksi minimum hingga 66.7%,, Valve berperan sebagai arsitek yang disengaja dan penerima manfaat komersial utama dari operasi ekosistem otomatis tersebut.\n\n← Kembali ke Ringkasan Eksekutif\n\nKetika Valve menyampaikan pernyataan kepada pihak regulator, penyedia layanan pembayaran, atau korban penipuan, situs tersebut mengaitkan pencurian data pengguna dan manipulasi pasar dengan \"eksploitasi pihak ketiga yang tidak sah\" dan \"otomatisasi ilegal yang nakal.\" Kenyataan teknis dari jaringan repositori 252-ini justru membuktikan hal yang sebaliknya: Setiap kerangka kerja otomatisasi, bot perdagangan, dan armada penambangan beroperasi secara ketat sesuai dengan definisi protokol resmi, API Web, dan mekanisme otentikasi yang dirancang, didokumentasikan, dan dimonetisasi oleh Valve Corporation.\n\nTemuan Forensik: Arsitektur yang Disengaja vs. Pelanggaran yang Tidak Sah\n\nPerangkat lunak yang dianalisis dalam modul ini — termasuk SteamKit, node-steam-user, ValvePython/steam, dan ArchiSteamFarm — berisi tidak ada kerentanan perangkat lunak, tidak ada kerusakan memori, dan tidak ada eksploitasi zero-day. Implementasi ini bersifat bersih, tangguh, dan berbasis sumber terbuka dari protokol klien Connection Manager (CM) milik Valve, Google Protocol Buffers (Protobufs), serta API Web. Valve merancang API-API ini untuk mendukung proses masuk secara terprogram, serta merancang Steam Guard agar dapat menggunakan token konfirmasi algoritmik (identity_secret), dan memungut biaya yang diiklankan sebesar 15% yang meningkat menjadi hingga 66.7% demi kepentingan Valve terkait kartu kredit berkecepatan tinggi dan barang-barang yang dijual oleh botnet otomatis.\n\nPilar 01 · Kesetiaan Protokol\nSkema Protobuf Resmi\n\nPustaka otomatisasi tidak melewati gerbang keamanan. Pustaka tersebut melakukan serialisasi pesan Protobuf resmi (steammessages_clientserver.proto) melalui TCP/WebSockets secara langsung ke klaster CM resmi Valve, persis seperti yang dilakukan oleh Klien Steam.\n\nPilar 02 · Algoritmik 2FA\nIzin Perdagangan Programatik\n\nSeluruh sektor perdagangan kulit senilai miliaran dolar bergantung pada Valve IEconService API dan kunci TOTP dari aplikasi otentikasi seluler. Valve secara sengaja merancang Steam Guard untuk memungkinkan konfirmasi transaksi antar-mesin.\n\nPilar 03 · Penerima Manfaat Komersial\nLalu Lintas Mesin yang Dimonetisasi: Hingga Batas Bawah Biaya66.7%\n\nValve Meskipun mengiklankan biaya sebesar 15%, namun pada barang-barang komoditas bervolume tinggi yang diperdagangkan oleh bot otomatis — seperti kartu koleksi, kotak, dan barang-barang murah dengan harga $0.03 hingga $0.05 — batas minimum biaya sebesar dua sen dari Valve ($0.01Steam + $0.01publisher) tetap dikenakan 50% kepada 66.7% atas nama Valve (2¢ dipotong dari kartu 3¢, sehingga penjual hanya menerima 1¢). Ditambah $5.00 per akun ($26.8M hanya dari armada yang dipindai saja).\n\nModul 01 · Bukti Repositori & Protokol\nInfrastruktur Pengembang dan Repositori Publik\n\nKatalog forensik terperinci mengenai repositori sumber terbuka 252 yang mendukung otomatisasi Steam. Menjelaskan bagaimana alat-alat rekayasa perangkat lunak standar mengimplementasikan titik akhir API yang dipublikasikan oleh Valve tanpa memanfaatkan celah keamanan.\n\n252Repositori\n4,554Tautan Peran\nPeriksa bukti di repositori →Modul 02 · Demografi Ekosistem\nMetrik Ekosistem Teknik Global\n\nRincian berdasarkan wilayah geografis dan institusi para insinyur perangkat lunak 3,320 yang berkontribusi pada ekosistem otomatisasi Steam, termasuk afiliasi perusahaan di berbagai perusahaan teknologi besar.\n\n3,320Insinyur\n98,902Pasangan Koneksi\nPeriksa metrik ekosistem →Modul 03 · Grafik Visual Interaktif\nGrafik Protokol Interaktif & Jaringan Pengembang\n\nPemetaan grafis jaringan interaktif yang komprehensif dari Vis.js, mencakup repositori, pustaka protokol (SteamKit, Steamworks, ASF), serta tumpang tindih kontributor lintas proyek. Secara visual memperlihatkan arsitektur perangkat lunak sumber terbuka yang sah dan saling terhubung, yang menjadi landasan ekosistem otomatisasi Steam.\n\nInteraktifVis.js Mesin\nIsolasi KlusterPencarian Langsung\nTanpa EksploitasiAPI Standar\nBuka diagram jaringan interaktif →\nKonteks Regulasi dan Hukum (Artikel GDPR 25 & Perlindungan Konsumen):\nBerdasarkan prinsip Perlindungan Data sejak Desain dan secara Default, arsitektur platform yang memungkinkan pembuatan kunci secara diam-diam (API), pembatalan transaksi tanpa pemberitahuan, dan likuidasi aset yang diotomatisasi oleh mesin merupakan pilihan arsitektural dari operator platform. Ketika Valve secara sistematis menolak klaim penggantian kerugian konsumen dengan mengklaim bahwa kerugian tersebut disebabkan oleh \"serangan siber eksternal,\" hal ini menyembunyikan fakta bahwa vektor serangannya adalah arsitektur Web API yang dirancang secara sengajValve sendiri.\n\nTAMPILAN INTERAKTIF\n\nVisualisasi interaktif lengkap dari repositori 252-, grafik jaringan pengembang 3,320-, tersedia di network.html. Metrik agregat terdapat di Metrik BI halaman.\n\nDokumen “Steam” · Arsip Arsitektur Teknis · Catatan Sumber Terbuka · Seluruh hak telah diserahkan kepada umat manusia.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam Arsitektur Jaringan — Ketepatan Protokol & Analisis Ekosistem"
          },
          {
            "level": 3,
            "id": null,
            "text": "Skema Protobuf Resmi"
          },
          {
            "level": 3,
            "id": null,
            "text": "Izin Perdagangan Programatik"
          },
          {
            "level": 3,
            "id": null,
            "text": "Lalu Lintas Mesin yang Dimonetisasi: Hingga Batas Bawah Biaya66.7%"
          },
          {
            "level": 2,
            "id": null,
            "text": "Infrastruktur Pengembang dan Repositori Publik"
          },
          {
            "level": 2,
            "id": null,
            "text": "Metrik Ekosistem Teknik Global"
          },
          {
            "level": 2,
            "id": null,
            "text": "Grafik Protokol Interaktif & Jaringan Pengembang"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/id/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/id/output_steam_network/valve_ru_farming_isolated.html",
          "https://phishdestroy.io/steam_dossier/id/output_steam_network/steam_ecosystem_dashboard.html",
          "https://phishdestroy.io/steam_dossier/id/output_steam_network/network.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/id/output_steam_network__index.content.json",
      "export_json_sha256": "ec922efc40b5783ec2a871327d947869bc1fefd6baae0746b3d723d25a6b0383"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "id/output_steam_network/network.html",
      "language": "id",
      "title": "Penjelajah pengembang & repositori — Profil \"Steam\"",
      "source_url": "https://phishdestroy.io/steam_dossier/id/output_steam_network/network",
      "source_html_sha256": "3b1abdffd070253d0ff41bf59b0f8e023f16d928dde86ed5f816b24895d622da",
      "exported_at": "2026-09-29T00:22:39.620Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__network.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/id/output_steam_network__network.pdf?v=print-20260929-v5",
        "sha256": "2e613a1a1b4a9c68cedb93408380235f4dfc86e5f00280392e15fd9ebcb1371b",
        "bytes": 34997,
        "pages": 1
      },
      "integrity": {
        "signed_object": "output_steam_network__network.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__network.content.json.asc",
        "digest_file": "output_steam_network__network.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__network.content.json.asc output_steam_network__network.content.json",
          "sha256sum -c output_steam_network__network.content.json.sha256"
        ]
      },
      "content": {
        "text": "Pengembang & penjelajah repositori\n\nCari sebuah simpul. Periksa hubungan yang tercatat.\n\nARSIP UMUM / KETERKAITAN YANG DIKUMPULKAN\nPencarian Langsung\nLapisan Filter\nJumlah Pengembang3,320\nJumlah Repo252\nGRAFIK YANG DITAMPILKAN / SUBSET KOLEKSI468 SIMPUL • 1103 SISI\nCatatan profil yang dipilih\n\n💡 Klik salah satu simpul pada grafik atau ketikkan kata kunci di kolom Pencarian untuk melihat koneksi dan jalur sumber yang telah dikumpulkan.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Pengembang & penjelajah repositori"
          }
        ],
        "links": []
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/id/output_steam_network__network.content.json",
      "export_json_sha256": "2d0cc8d38903bfdab046a1e5d5f7a145d3faaf2743981d0ccee0ee3815cce9e4"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "id/output_steam_network/steam_ecosystem_dashboard.html",
      "language": "id",
      "title": "Jaringan yang Terkumpul dalam Angka — Laporan “Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/id/output_steam_network/steam_ecosystem_dashboard",
      "source_html_sha256": "9a283bf313717074b3fdd3b5cc4ecec78598a12f944d0b724430aea045775a8c",
      "exported_at": "2026-09-29T00:22:39.758Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__steam_ecosystem_dashboard.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/id/output_steam_network__steam_ecosystem_dashboard.pdf?v=print-20260929-v5",
        "sha256": "01f46b4b26d83a6d536a50229760ce6f11a953e65dafc613a1947fa3e61c71df",
        "bytes": 38047,
        "pages": 2
      },
      "integrity": {
        "signed_object": "output_steam_network__steam_ecosystem_dashboard.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__steam_ecosystem_dashboard.content.json.asc",
        "digest_file": "output_steam_network__steam_ecosystem_dashboard.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__steam_ecosystem_dashboard.content.json.asc output_steam_network__steam_ecosystem_dashboard.content.json",
          "sha256sum -c output_steam_network__steam_ecosystem_dashboard.content.json.sha256"
        ]
      },
      "content": {
        "text": "GAMBARAN UMUM STATISTIK // BERKAS 02\nSteam Dasbor Ekosistem — Jaringan dalam Angka\n\nJaringan ini, dalam angka.\n\nAPA YANG DIBUKTIKAN OLEH BAGIAN INI\n\nDasbor ini mengumpulkan informasi struktural dari para pengembang di 3,320 dan repositori di 252, serta mengidentifikasi basis kode khusus perjudian di 68 dan jembatan koneksi lintas platform. Data empiris tersebut menyoroti pola pengelompokan geografis dan tumpang tindih pengembang, yang menunjukkan bahwa infrastruktur perjudian skin pihak ketiga beroperasi sebagai industri perangkat lunak yang terorganisir dan sangat saling terhubung, yang terintegrasi dengan platform Steam.\n\n← Kembali ke Ringkasan Eksekutif\n\nStatistik gabungan dari basis data investigasi: sebaran geografis, perusahaan-perusahaan teratas, repositori perjudian berbasis skin, dan jembatan koneksi aktif.\n\nPengembang yang Telah Dipindai3320\nJumlah Repo252\nRepos Perjudian68\nJumlah Koneksi1,426\nStruktur dan Sektor-sektor Otomasi\nSektor I — Inti PerusahaanValve\n\nRepositori resmi dan perangkat lunak sistem. Ruang pengembangan yang telah dikonfirmasi milik dua karyawanValve, Nephyrin dan Joe Ludwig.\n\nSektor II — Mesin Otorisasi & Emulator Protokol (SteamKit)\n\nPustaka jaringan hasil rekayasa balik yang ditulis bersama oleh Nephyrin dari Valve dan DoctorMcKay, pengembang tema perjudian.\n\nSektor III — Klien Penambangan Kartu (ArchiSteamFarm)\n\nGunakan emulator protokol SteamKit untuk menjalankan jutaan klien palsu (dalam keadaan idle) di latar belakang guna mengumpulkan kartu perdagangan.\n\nLokasi Pengembang\nJerman57\nAmerika Serikat52\nKanada48\nBritania Raya44\nPolandia30\nPrancis28\nFederasi Rusia27\nTiongkok27\nAS (Negara Bagian Washington)23\nAustralia19",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam Dasbor Ekosistem — Jaringan dalam Angka"
          },
          {
            "level": 3,
            "id": null,
            "text": "Sektor I — Inti PerusahaanValve"
          },
          {
            "level": 3,
            "id": null,
            "text": "Sektor II — Mesin Otorisasi & Emulator Protokol (SteamKit)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Sektor III — Klien Penambangan Kartu (ArchiSteamFarm)"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/id/#briefing-heading"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/id/output_steam_network__steam_ecosystem_dashboard.content.json",
      "export_json_sha256": "c5ffa137fbe85c2d48097d71ca1105b1664c6f75024b340e42d49e4474014713"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "id/output_steam_network/valve_ru_farming_isolated.html",
      "language": "id",
      "title": "Kode, kontributor, & fork — Laporan “Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/id/output_steam_network/valve_ru_farming_isolated",
      "source_html_sha256": "78c372b55a984cca302ef10fa64257a7c6c7a0412863db702c99683a1744310e",
      "exported_at": "2026-09-29T00:22:39.852Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__valve_ru_farming_isolated.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/id/output_steam_network__valve_ru_farming_isolated.pdf?v=print-20260929-v5",
        "sha256": "e163e00c3101dbc616a392fe01477f27a100ed92d6503af7d36cac164fa419f9",
        "bytes": 40346,
        "pages": 2
      },
      "integrity": {
        "signed_object": "output_steam_network__valve_ru_farming_isolated.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__valve_ru_farming_isolated.content.json.asc",
        "digest_file": "output_steam_network__valve_ru_farming_isolated.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__valve_ru_farming_isolated.content.json.asc output_steam_network__valve_ru_farming_isolated.content.json",
          "sha256sum -c output_steam_network__valve_ru_farming_isolated.content.json.sha256"
        ]
      },
      "content": {
        "text": "BAGIAN II / IKUTI JALUR HUBUNGAN YANG TERCATAT\n\nFork, kontribusi, dan ketergantungan perangkat lunak merupakan bukti yang jelas. Pandangan ini mempertahankan peran-peran yang telah diidentifikasi; sedangkan terkait pekerjaan, pelanggaran keamanan, dan keterlibatan kriminal memerlukan sumber-sumber tambahan.\n\nBuka peta kemampuan interaktif ↗\nSUMBER UMUM / AUDIT PERAN\nKode. Para kontributor. Fork.\n1. Nephyrin: cabang dan kontribusi\n\nSnapshot yang disertakan mencantumkan Nephyrin sebagai kontributor untuk ValveSoftware/Proton serta sebagai pembuat cabang (forker) dari SteamRE/SteamKit dan SteamRE/open-steamworks. Data profilnya mencantumkan Valve Software. Kolom-kolom ini sebaiknya dibaca secara terpisah.\n\nFork mencatat salinan repositori. Ekspor ini tidak menyertakan commit yang mencatat perubahan pada kode otentikasi SteamKit.\nReferensi repositori / lihat riwayat\nSteamRE/SteamKit ↗ SteamRE/open-steamworks ↗\n2. Fitur publik: otomatisasi tanpa klien desktop\n\nSteamKit dan node-steam-user menyediakan antarmuka pemrograman untuk berinteraksi dengan Steam. ArchiSteamFarm mendokumentasikan proses pengumpulan kartu dengan menggunakan banyak akun dan mencantumkan SteamKit2 sebagai dependensi.\n\nInilah kemampuan otomatisasi yang konkret. Eksekusi tanpa antarmuka pengguna (headless) tidak menandakan penggunaan komersial eksklusif atau upaya untuk mengelabui sistem Perlindungan Penggunaan yang Tidak Sah (Steam Guard). Pertanyaan yang relevan adalah kredensial yang diminta, tindakan yang dapat dilakukan dengan kredensial tersebut, serta kontrol yang diterapkan oleh platform.\n\nSumber: berkas README proyek dan ArchiSteamFarm.csproj. Peta kapabilitas menautkan setiap ketergantungan yang didokumentasikan.\n3. JoeLudwig: label kontributor hl2sdk\n\nCuplikan tersebut mencantumkan JoeLudwig sebagai kontributor untuk alliedmodders/hl2sdk, ValveSoftware/openvr, dan ValveSoftware/source-sdk-2013.. Hal tersebut merupakan hubungan antarproyek yang dapat diamati. Data ekspor tersebut tidak memberikan bukti yang mengaitkan perubahan SDK tertentu dengan pencurian atau penerapan sistem perjudian.\n\nReferensi repositori / lihat riwayat\nalliedmodders/hl2sdk ↗ DoctorMcKay/node-steam-user ↗\nSKEMA LOGIKA // JALUR\nDiagram Alur Logika Koneksi:\nPROFIL HUBUNGAN\nNephyrin / profil yang dikumpulkan\nKontributor: Proton. Pengembang cabang: SteamKit dan open-steamworks.\n▼ Hubungan percabangan yang dikumpulkan\nPERPUSTAKAAN MASYARAKAT\nSteamRE/SteamKit\nPerpustakaan jaringan Public Steam yang dikelola oleh organisasi SteamRE.\n▼ Ketergantungan SteamKit2 telah dinyatakan\nOTOMATISASI YANG TERDOKUMENTASI\nJustArchiNET/ArchiSteamFarm\nMendokumentasikan praktik \"card farming\" di beberapa akun dan ketergantungan pada SteamKit2.\nTINJAUAN BUKTI / GAMBARAN SINGKAT SUMBER\nTERCATAT: label kontributor dan pembuat fork yang berbeda.\nTERBUKTI: perpustakaan umum mendukung interaksi yang terSteamasi dan terstruktur.\nPERTANYAAN TERBUKA: Keaslian kode tertentu, persetujuan platform, dan penetapan pihak yang melakukan penyalahgunaan memerlukan bukti yang terpisah.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Kode. Para kontributor. Fork."
          },
          {
            "level": 2,
            "id": null,
            "text": "1. Nephyrin: cabang dan kontribusi"
          },
          {
            "level": 2,
            "id": null,
            "text": "2. Fitur publik: otomatisasi tanpa klien desktop"
          },
          {
            "level": 2,
            "id": null,
            "text": "3. JoeLudwig: label kontributor hl2sdk"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/id/investigation_part2.html#automation-map",
          "https://github.com/SteamRE/SteamKit",
          "https://github.com/SteamRE/open-steamworks",
          "https://github.com/alliedmodders/hl2sdk",
          "https://github.com/DoctorMcKay/node-steam-user"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/id/output_steam_network__valve_ru_farming_isolated.content.json",
      "export_json_sha256": "3af01b2c16cefba825ebff6ef2cdfe417207c562054de69cab18682cd32cc200"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "hi/card_economy.html",
      "language": "hi",
      "title": "कार्ड अर्थव्यवस्था — द Steam डोजियर",
      "source_url": "https://phishdestroy.io/steam_dossier/hi/card_economy",
      "source_html_sha256": "9e2bd2be69ffbd5d296f8b5a3aaa8d253deb5539dd6dbe4b074170b03a1328a6",
      "exported_at": "2026-09-29T00:22:41.875Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "card_economy.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/hi/card_economy.pdf?v=print-20260929-v5",
        "sha256": "9c3155db69a5266b2fecb165cf87e0d41eead7e5fd2c3af5aa96387543ae6050",
        "bytes": 640568,
        "pages": 20
      },
      "integrity": {
        "signed_object": "card_economy.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "card_economy.content.json.asc",
        "digest_file": "card_economy.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify card_economy.content.json.asc card_economy.content.json",
          "sha256sum -c card_economy.content.json.sha256"
        ]
      },
      "content": {
        "text": "प्रदर्शनी V — कार्ड अर्थव्यवस्था\nकार्ड इकोनॉमी — थोक बिक्री, ड्रॉप सीमाएँ और स्वचालित फार्मिंग\n\nबॉट फार्म Valve की दुकान में कोई लीक नहीं है। यह एक ग्राहक.\n\nयह अनुभाग क्या प्रमाणित करता है\n\nयह अध्याय प्रमाणित करता है कि स्वचालित Steam कार्ड फ़ार्म अवैध शोषकों के बजाय संरचनात्मक, राजस्व उत्पन्न करने वाले थोक ग्राहक के रूप में कार्य करते हैं। प्रत्येक फार्मिंग बॉट को Valve की $5.00 सक्रियण सीमा पार करनी होती है, गेम लाइसेंस खरीदने होते हैं, और गारंटीकृत बाजार लेनदेन शुल्क उत्पन्न करने होते हैं (न्यूनतम $0.02,, कम-मूल्य वाली संपत्तियों पर 66.7% तक शुल्क दरें)। स्वचालित बॉट नेटवर्क के खिलाफ स्पष्ट सेवा शर्तों के प्रतिबंधों के बावजूद, 91 द्वारा ऑडिट किए गए वाणिज्यिक बॉट नेटवर्क Steam के पारिस्थितिकी तंत्र में 694,673 सहित पूर्ण कार्ड सेट खुलेआम बनाए रखते हैं, बिना किसी प्रवर्तन हस्तक्षेप के।\n\n← कार्यकारी ब्रीफिंग पर वापस\n\nएक Steam खाता तब तक एक भी ट्रेडिंग कार्ड प्राप्त नहीं कर सकता जब तक कि उसने खर्च न किया हो। $5.00 स्टोर में। यह उस गेम को फार्म नहीं कर सकता जिसके मालिक वह नहीं है, और न ही उस गेम को जिसे उसे मुफ्त में दिया गया हो। इसलिए, इससे पहले कि कोई स्वचालित कार्ड फार्म कुछ भी उत्पादन करे, उसने अपनी जगह खरीद ली होती है — प्रति खाता, उस कीमत पर जो Valve प्रकाशित करता है। फिर Valve का स्वचालन खंड, पंक्ति दर पंक्ति, ठीक-ठीक बताता है कि वह फार्म क्या उत्पादन करता है; उसका लाइसेंस हर उस रास्ते को मना करता है जिससे एक फार्म्ड कार्ड पैसे में बदलता है; और उसका बाज़ार तब भी एक हिस्सा लेता है जब कार्ड वैसे भी बिकता है — जिसकी विज्ञापन दर 15%, है लेकिन बिक्री पर दो सेंट की न्यूनतम दर है, जो सेंट में कीमत वाले कार्ड पर कीमत का अधिकांश हिस्सा है। यह प्रदर्शनी मापती है कि यह व्यापार कितना बड़ा है, प्रोफ़ाइल के शीर्ष स्तर की कीमत सेटों में क्या होती है, और जब खाता एक साधारण व्यापारी का होता है तो Valve का प्रवर्तन विभाग उसी धारा के साथ क्या करता है।\n\nएक खेत को सबसे पहले क्या खरीदना चाहिएसेट्स में एक लेवल की कीमत क्या होती हैमेज के दोनों ओरकार्ड अर्थव्यवस्था का संचालन कौन करता है\n$5.00किसी खाते में कोई कार्ड प्राप्त करने से पहले खर्च संग्रहित करें — Valve का अपना सहायता पृष्ठ\n13,876Steamपर गेम्स जो ट्रेडिंग कार्ड जारी करते हैं, जिनमें 99,971 विभिन्न प्रकार के कार्ड होते हैं।\n694,67391 द्वारा सार्वजनिक रूप से सूचीबद्ध ट्रेडिंग बॉट्स द्वारा अभी स्टॉक में रखे गए पूर्ण कार्ड सेट\n1,389,346खाते और गेम कार्ड ड्रॉप भत्ते उन स्टॉक के लिए जो पहले ही उपभोग हो चुके हैं, न्यूनतम पर।\n$9.99कार्ड-बेयरिंग गेम की माध्यिक कीमत — इसका पूरा सेट औसतन $0.74 में बिकता है।\n97,114कार्ड-ट्रेडिंग समूह के सदस्य, जिनकी मॉडरेटर सूची में एक Valve का कर्मचारी शामिल है — § 08\n01 — प्रक्रिया\nएक खेत वास्तव में क्या है, चरण-दर-चरण\n\nयह केवल उपकरण के अपने दस्तावेज़ीकरण और Valve के अपने सहायता पृष्ठों से वर्णित है। इस अनुभाग में कुछ भी अनुमानित नहीं है, और इसमें कुछ भी किसी भी पक्ष द्वारा विवादित नहीं है।\n\nचरण 1\nसमर्थन करना\n\nखाता नहीं होना चाहिए सीमितValve का समर्थन पृष्ठ सीमित खातों को से रोकता है Steam बाजार में भाग लेना, से Steamकॉम्युनिटी आइटम (ट्रेडिंग कार्ड, बूस्टर पैक, जेम्स आदि) का व्यापार और से Steamप्रोफ़ाइल स्तर प्राप्त करना (0स्तर से लॉक) और ट्रेडिंग कार्ड्स. द्वार पैसा है: आपको Steam स्टोर में कम से कम $5.00 अमेरिकी डॉलर खर्च करने होंगे।\n\nचरण 2\nगेम खरीदें\n\nकार्ड केवल आपके स्वामित्व वाले खेलों से ही मिलते हैं। किसी भी कार्ड ड्रॉप्स के लिए पात्र होने के लिए, आपको अपने Steam खाते पर गेम का मालिक होना चाहिए। फैमिली शेयरिंग मालिकाना हक नहीं है और इसकी गिनती नहीं की जाती। नि:शुल्क मार्ग भी बंद हैं: प्रमोशन के दौरान मुफ्त में प्राप्त किए गए पेड गेम्स से कार्ड ड्रॉप नहीं किए जा सकते।, और आप F2P गेम्स में बिना पैसे खर्च किए कार्ड नहीं प्राप्त कर सकते।\n\nचरण 3\nनिष्क्रिय\n\nयह टूल बिना ग्राफिकल इंटरफ़ेस के Steam नेटवर्क में खाते को लॉग इन करता है। आपके बैज पार्स करता है, खेती योग्य शीर्षकों और स्टार्ट्स की सूची बनाता है योग्य गेम खेलना और समय-समय पर यह जांचना कि गेम पहले से ही पूरी तरह खेती हो चुका है या नहीं। इसकी रखरखावकर्ता द्वारा तंत्र का वर्णन: यह Steam को यह बताने के अलावा और कुछ नहीं करता कि हम दिए गए खेल को खेल रहे हैं।\n\nचरण 4\nबूँदें खत्म हो गईं\n\nप्रत्येक शीर्षक सीमित है। हर गेम में कार्ड ड्रॉप्स की एक निश्चित संख्या होती है। एक बार जब आप उन सभी को ड्रॉप कर लेते हैं (पूरे सेट का लगभग आधा हिस्सा), तो यह गेम फार्मिंग के लिए उपयुक्त नहीं रहता। एक फार्म जो उत्पादन जारी रखना चाहता है, उसे लगातार टाइटल्स खरीदते रहना पड़ता है। कार्ड की आपूर्ति जानबूझकर खरीदारी द्वारा सीमित की जाती है, और यहValve के पक्ष में है।\n\nचरण 5\nनकद निकासी\n\nकार्ड तीन में से किसी एक दरवाजे से निकलता है: सामुदायिक बाज़ार में बेचा जाता है, किसी अन्य के साथ विनिमय किया जाता है, या रत्नों में कुचल दिया जाता है। प्रत्येक एक सदस्यता बाज़ार लेनदेन या एक व्यापार है, और §3.D शुल्क आरक्षित करता है: Valve सदस्यता मार्केटप्लेस में लेनदेन के लिए शुल्क ले सकता है। यह वह कदम है जो पूरी चीज़ को उल्लंघन बना देता है — देखें 05.\n\nस्रोत, 2026-09-22: पर शब्दशः पढ़ा और उद्धृत। Steam सहायता — सीमित उपयोगकर्ता खाते ↗ · ArchiSteamFarm अक्सर पूछे जाने वाले प्रश्न ↗ · Valve — Steam ट्रेडिंग कार्ड्स अक्सर पूछे जाने वाले प्रश्न ↗ · Steam सब्सक्राइबर समझौता ↗ संचित 2026-09-24 ↗. ArchiSteamFarm को इस पूरे पृष्ठ में एक माप उपकरण के रूप में उपयोग किया गया है, न कि प्रतिवादी के रूप में; इसकी अपनी दस्तावेज़ीकरण स्पष्ट रूप से कहती है कि ASF को Valve द्वारा अधिकृत नहीं किया गया है।.\n\n02 — पैमाना\nएक खेत एक पैसा कमाने से पहले ही, उसने पहले ही Valve का भुगतान कर दिया है।\n\nचूंकि सीमित खाते को कार्ड प्राप्त नहीं हो सकता, इसलिए फार्म में प्रत्येक खाते को कुछ भी उत्पादन करने से पहले सीमित स्थिति से उन्नत किया जाना चाहिए। यह सीमा प्रकाशित की जाती है, और शुल्क प्रति खाते लगाया जाता है।\n\nखेत का आकार\tयह संख्या कहाँ से आती है\tकार्ड-योग्य बनने के लिए न्यूनतम स्टोर खर्च\n10 accounts\tThe ceiling ASF recommends — \"based on internal Valve guidelines, as well as our own suggestions\"\t$50\n100–200 accounts\tTechnical ceiling in the same FAQ: \"you can run up to 100-200 bots with a single IP and a single ASF instance\"\t$500 – $1,000\n120 accounts\tEnforcement case 3 below — permanently banned\t$600\n170 accounts\tEnforcement case 2 below — permanently banned during the 2017 Winter Sale\t$850\n1,000 accounts\tEnforcement case 1 below — trade banned\t$5,000\n5,000 accounts unverified\tOperator scale reported to this investigation and not independently checked — see the note on sourcing\t$25,000\n10,000 accounts unverified\tOperator scale reported to this investigation and not independently checked — see the note on sourcing\t$50,000\n\nइस पृष्ठ पर केवल अंतिम दो पंक्तियाँ ही ऐसी आँकड़े हैं जो दस्तावेज़ के बजाय एक अप्रमाणित रिपोर्ट पर आधारित हैं — उन्हें तालिका में चिह्नित किया गया है, जैसा कि समझाया गया है। स्रोत पर नोट, और यहाँ कुछ भी और उन पर निर्भर नहीं करता। दाहिना स्तंभ केवल Valve द्वारा प्रकाशित $5.00 USD थ्रेशोल्ड पर अंकगणित है और कुछ भी और नहीं। यह एक तलयह किसी फार्म की लागत या 'Valve' से हुई आय का अनुमान नहीं है: इसमें उन खेलों को शामिल नहीं किया गया है, जिनका स्वामित्व होना आवश्यक है और जो किसी प्रचार में मुफ्त में नहीं मिल सकते, और इसमें कार्ड बिकने पर कम्युनिटी मार्केट द्वारा ली जाने वाली लगभग 15% की राशि भी शामिल नहीं है। इस पृष्ठ पर कोई राजस्व आंकड़ा दावा नहीं किया गया है।\n\nऔर Valve ने स्वयं एक कार्ड ड्रॉप की कीमत तय की है। इसके ट्रेडिंग कार्ड्स FAQ में फ्री-टू-प्ले रूपांतरण दर को साधारण डॉलर में निर्धारित किया गया है:\n\nमुफ्त में खेलने वाले गेम आपकी इन-गेम खरीदारी के आधार पर गेम कार्ड जारी करते हैं। हर खर्च किए गए लगभग $9 अमेरिकी डॉलर के लिए Steam ट्रेडिंग कार्ड बीटा की शुरुआत से, आप एक कार्ड ड्रॉप अर्जित करेंगे।\n\n— Valve, Steam ट्रेडिंग कार्ड्स अक्सर पूछे जाने वाले प्रश्न ↗ · सत्यापित शब्दशः 2026-09-22\n\nट्रेडिंग कार्ड ऐसा उपहार नहीं है जिस पर प्लेटफ़ॉर्म को घाटा हो। यह कुछ ऐसा है जो Valve बेचता है, उस दर पर जो Valve ने प्रकाशित की — और फिर आगे बेचने के लिए दूसरी बार शुल्क लेता है। इसलिए कार्ड फ़ार्म का ईमानदार वर्णन नहीं है। परजीवीयह है थोक खरीदार.\n\nवास्तव में खरीदी जा रही वस्तु कितनी बड़ी है।\n\nयहाँ से इस अनुभाग के अंत तक सब कुछ मापा गया है, रिपोर्ट नहीं किया गया है। कार्ड जनगणना Steam Card Exchange द्वारा प्रकाशित बैज मूल्य सूची है; खेलों की कीमतें स्वयं Valve की अपनी दुकान API से ली गई हैं; बॉट स्टॉक एक सार्वजनिक बॉट निर्देशिका से आता है जिसे कोई भी खोल सकता है। ये तीनों 2026-09-22 पर पढ़े गए थे और अंकगणित पूरी तरह से इसमें दी गई है। धारा 08.\n\n13,876गेम्स कार्ड जारी करते हैं\n99,971विभिन्न कार्ड प्रकार\n5 · 6 · 15प्रति सेट कार्ड: न्यूनतम, मध्यक, अधिकतम\n$0.74तैयार सेट की माध्यिका कीमत\n$23,586.57हर सेट में से एक बाज़ार में\nयह सेट कितना बड़ा है\n\n13,876 सेट में कार्डों के अनुसार खेल। Valve उनमें से लगभग आधे किसी भी एक खाते में डाल देता है।\n\n0\n1,250\n2,500\n3,750\n5,000\n5\n6\n7\n8\n9\n10\n11\n12\n13\n14\n15\nलाइसेंस की कीमत\n\nSteam की स्टोर पर उन्हीं खेलों की सूची मूल्य, अमेरिकी डॉलर में।\n\n0\n1,000\n2,000\n3,000\n4,000\n<$1\n$1-3\n$3-5\n$5-10\n$10-20\n$20-40\n$40+\nतैयार सेट क्या लौटाता है\n\nउसी खेलों के पूर्ण सेट की बाजार कीमत।\n\n0\n1,500\n3,000\n4,500\n6,000\n<$0.50\n$0.50-1\n$1-2\n$2-5\n$5-10\n$10+\n\nदूसरे और तीसरे चार्ट को एक-दूसरे के सामने पढ़ें और व्यापार का आकार बिना गणित के ही दिखाई देता है: खेल दस डॉलर के आसपास समूहबद्ध होते हैं, जबकि वे जो सेट देते हैं, वे एक डॉलर से नीचे समूहबद्ध होते हैं। दोनों ही एक ही 13,876 खेलों की गिनती हैं, एक ही अक्ष इकाई पर, इसलिए तुलना दो ऊँचाइयों के बीच है, न कि दो पैमानों के बीच।\n\nयह आपूर्ति पक्ष है। मांग पक्ष वह हिस्सा है जValve को विज्ञापन करने की आवश्यकता नहीं है, क्योंकि यह पहले से ही सार्वजनिक रूप से मौजूद है: कार्ड-ट्रेडिंग बॉट्स की एक एकल खुली निर्देशिका सूचीबद्ध करती है। 91 बॉट्स इस समय स्टॉक में पूर्ण सेट (694,673) रखे हुए हैं। कोई लॉगिन नहीं, कोई मार्केटप्लेस स्क्रैपिंग नहीं, कोई निजी डेटा नहीं — स्टॉक की तस्वीर प्रत्येक बॉट के नाम के बगल में पेज पर मुद्रित होती है।\n\nउस स्टॉक को ही एकमात्र इकाई में बदलें जो यहाँ मायने रखती है। Valve का अपना नियम: अधिकांश खेल लगभग आधे कार्डों के बराबर कार्ड ड्रॉप करेंगे… आपको सेट का दूसरा आधा हिस्सा अन्य समुदाय के सदस्यों से इकट्ठा करना होगा।\" एक खाता खेलकर कभी भी एक सेट पूरा नहीं कर सकता। दो खातों की न्यूनतम आवश्यकता है, प्रत्येक के पास वह गेम होना चाहिए, और प्रत्येक अपनी प्रति गेम एक बार की ड्रॉप अनुमति खर्च कर देता है। ड्रॉप्स पुनर्जीवित नहीं होते।\n\n694,673स्टॉक में सेट, सार्वजनिक बॉट्स 91\n3,473,365कार्ड्स, न्यूनतम सेट पर 5-कार्ड\n1,389,346खपत हुए भत्ते, न्यूनतम\n2,602एक ही गेम वाले खाते, सबसे घना बॉट\n694,673 सेट कहाँ रखे गए हैं\n\n91 के सार्वजनिक रूप से सूचीबद्ध कार्ड बॉट्स में से पूर्ण सेट के आधार पर बारह सबसे बड़े। ये दस सबसे बड़े मिलकर 248,115 के सेट रखते हैं — बोर्ड पर मौजूद हर चीज़ के 35.7%।\n\n0\n11,250\n22,500\n33,750\n45,000\nCard Supply #4 (High)\nN!vq's Leveling (High)\nAlice [BOT] LEVEL-UP RARE SETS\nN!vq's Leveling (Low)\nDisco Lite Level Up\nN!vq's Leveling (Mid)\nbaty131store.net | Level Up\nKitten - Supreme\nArashirn | Level Up\nSH (Junior) Level Up\nDuobot.com - Overstock\nlvlupbot.com - godlike\n\nउन सभी 1.39 मिलियन अलाउंस में से प्रत्येक उस खाते का था जो गेम का मालिक था, जो $5.00 गेट से आगे था, और अब कभी भी उन ड्रॉप्स को फिर से उत्पन्न नहीं कर सकता। यह है अनबेची गई सूची नवेंवन बॉट्स पर। यह बाजार का मापदंड नहीं है; यह बाजार के बाद बचे हुए का मापदंड है।\n\nअंतिम आंकड़ा हेडकाउंट नहीं बल्कि पिजनहोल काउंट है। एक बॉट केवल 11 गेम्स से निकाले गए 14,310 सेट की सूची बनाता है, इसलिए उन गेम्स में से कम से कम एक का प्रतिनिधित्व 1,301 सेट द्वारा होता है, जो कम से कम 2,602 अलग-अलग खातों के बराबर है जिन्होंने वह गेम खरीदा। यह वह न्यूनतम संख्या है जिसे अंकगणित अनुमति देता है, और यह नब्बे-एक में से एक बॉट से संबंधित है।\n\nयह मंजिल क्या कहती है और क्या नहीं कहती\n\nये बॉट्स साधारण खिलाड़ियों से और फार्म से कार्ड खरीदते हैं — उनकी प्रकाशित खरीद दरें ही इस निर्देशिका का मुख्य उद्देश्य हैं। तो 1.39 मिलियन भत्ते फार्म-स्वामित्व वाले खातों की संख्या नहीं हैं। ये उन एक-प्रति-खाते, एक-प्रति-खेल ड्रॉप भत्तों की गिनती हैं, जिन्हें कहीं न कहीं Steam पर खर्च किया गया था और जो बिना बिके वाणिज्यिक स्टॉक में पहुँच गए हैं। चाहे प्रत्येक के पीछे का खाता फार्म हो या किशोर जो अपना बैज पेज साफ़ कर रहा हो, इससे Valve ने जो एकत्र किया वह नहीं बदलता: $5.00 अनलॉक, गेम लाइसेंस, और हर हॉप पर मार्केट कट — 15%, नहीं, बल्कि 15% या दो एक-सेंट न्यूनतम, जो भी बड़ा हो।, जो सेंट में मूल्यवान कार्ड पर कहीं अधिक बड़ा है। अंकगणित इसमें है नीचे शुल्क की सीढ़ीयही इस पृष्ठ का उद्देश्य है, और यह किसानों के खिलाफ कोई शिकायत नहीं है: वही व्यवहार, जिस पर Valve शुल्क लगाता है, वही व्यवहार है जिसे यह \"वाणिज्यिक उपयोग\" के लिए किसी व्यक्ति को स्थायी रूप से प्रतिबंधित करते समय शब्दशः उद्धृत करता है।\n\nयह आकृति दूसरे अर्थ में एक तल भी है। यह केवल उस स्टॉक को ही गिनती है जो आज सूचीबद्ध और अनविक्रित बॉट्स पर जो सार्वजनिक निर्देशिका में शामिल हों. सब कुछ पहले ही बिक चुका है, सब कुछ निजी तौर पर रखा गया है, और निर्देशिका के बाहर का हर बॉट शामिल नहीं है।\n\nऔर Valve की कीमतों पर खेती खुद अपना खर्च नहीं उठा सकती।\n\nस्पष्ट आपत्ति यह है कि एक फार्म सस्ते गेम्स खरीदकर महंगे कार्ड बनाता है।Steam की अपनी स्टोर API इसके विपरीत कहती है। 13,876 कार्ड वाले गेम्स में से, 13,713 के लिए कीमतें तय की गईं; 12,918 वे भुगतान किए गए शीर्षक हैं जिनकी माध्य सूची मूल्य $9.99. है। मध्यम समाप्त सेट की बिक्री होती है $0.74. प्रत्येक सेट के लिए दो लाइसेंस आवश्यक हैं। इसलिए मध्यक सेट की लागत लगभग गेम लाइसेंस के उत्पादन के लिए $19.98 और $0.74 की वापसी।.\n\n2026-09-22 पर मापा गया\tमूल्य\tयह क्या तय करता है\nMedian list price, card-bearing game\t$9.99\tThe licence is the expensive half of the transaction, not the card\nGames priced at $4.99 or less\t3,665 (28.4%)\tEven the cheap tail is dearer than the set it yields\nCheapest card-bearing game on the store\t$0.99\tTwo licences, $1.98, for a set that typically sells under $1.30\nGames whose set sells for more than the game\t323 of 12,918 (2.5%)\tCard arbitrage against Steam's list prices exists in 1 game in 40\nFree-to-play titles in the census\t795\tAnd Valve prices each of their drops at $9 of in-game spend\n\nजो आर्थिक प्रश्न कोValve के पक्ष में और सामान्य कहानी के विपरीत बंद कर देता है। जिन कीमतों पर Valve स्वयं शुल्क लेता है, कार्ड फार्मिंग एक घाटे का सौदा है जो केवल Steam की सूची मूल्य से कम पर प्राप्त लाइसेंसों पर ही काम करता है। — बंडल्स, क्षेत्रीय मूल्य निर्धारण, प्रमुख पुनर्विक्रय। कार्ड्स अवशेष हैं। खरीद ही घटना है। और खरीद Steam पर हुई।\n\nखेत वास्तव में क्या सहारा देता है\n\nटुकड़ों को एक साथ जोड़ें और खेत अब वैसा नहीं दिखता जिसे Valve सहन करता है, बल्कि ऐसा दिखने लगता है जिसकी Valve को जरूरत है। खेत द्वारा प्रदान किया गया प्रत्येक इनपुट वह आउटपुट है जिसके लिए Valve रिपोर्ट या बिल तैयार करता है। एक बॉट खाते को बाहर की ओर अनुसरण करें:\n\nएक फार्म किया गया खाताएक \"थोक ग्राहक\", कोई लीक नहीं\nगेम की बिक्री\n\nयह उन शीर्षकों को खरीदता है जिन्हें यह फार्म करता है — 13,876 कार्ड गेम्स से लेकर $0.50 शवेलवेयर तक — क्योंकि कार्ड केवल स्वामित्व वाले खेलों से ही ड्रॉप होते हैं।\n\n\"ऑनलाइन\" और खेलने का समय\n\nयह उन्हें कार्ड ड्रॉप करने के लिए आइडल रखता है, साथ ही उन समवर्ती खिलाड़ियों और खेले गए घंटों के आंकड़ों को बढ़ाता है जिन्हें Valve एंगेजमेंट बताता है — वही आँकड़ा जिसे §4.C \"प्लेटाइम की नकल\" कहता है।\n\nपंजीकरण\n\nकार्ड प्राप्त करने से पहले $5.00 के सीमित-खाता गेट को पार करना अनिवार्य है — एक वास्तविक स्टोर में प्रति खाता Valve किताबें खर्च की जाती हैं।\n\nबटुए का पैसा और शुल्क\n\nहर कार्ड जो यह बेचता है, मार्केट के माध्यम से वापस जाता है, जहाँ कम-मूल्य वाले कार्ड पर शुल्क 66.7% तक पहुँचता है और प्राप्त राशि Steam वॉलेट में लॉक रहती है।\n\nSteam-स्तरीय पीआर\n\nValve में दिखाए गए बैज और स्तर केवल इसलिए मौजूद हैं क्योंकि सेट बनाए गए थे — और उस सीढ़ी की चोटी बॉट्स द्वारा भरी गई है (देखें §03)।\n\nखेत हटा दो और ऊपर का हर नंबर गिर जाता है। — गेम की कम प्रतियाँ बिकीं, \"ऑनलाइन\" छोटा था, खाता कभी पंजीकृत नहीं हुआ, शुल्क कभी नहीं लिया गया, और स्तर कभी हासिल नहीं किया गया। इसलिए स्वचालन पर प्रतिबंध लगाने वाला नियम लाखों स्वचालित खातों के साथ सहअस्तित्व में है: प्रतिबंध ही विकल्प है, और गतिविधि ही राजस्व है।\n\nऔर कैश-आउट स्वयं एक मूल्य अवशोषक है Valve दो बार कर लगाता है\n\nकार्ड लूप का अंत नहीं है।Valve की अपनी यांत्रिकी एक कार्ड को कुचलकर उसमें समाहित होने देती है। रत्न, और रत्न खर्च करके तैयार किया जाए बूस्टर पैक — तीन और कार्ड — जिन्हें फिर से बेचा या कुचला जाता है। प्रत्येक हॉप एक बाज़ार लेन-देन या रूपांतरण है, और प्रत्येक पर कर लगाया जाता है। उस लूप की दिशा नीचे मापे गए शुल्क के न्यूनतम स्तर से निर्धारित होती है और इसके लिए किसी बाहरी मॉडल की आवश्यकता नहीं है: इसमें बेचा गया प्रत्येक कार्ड आत्मसमर्पण कर देता है। कम से कम दो सेंटतीन से पाँच के बीच व्यापार करने वाले कार्डों पर, इसलिए हर क्रैंक घुमाने पर निवेश की तुलना में कम ही वापस मिलता है। यह लूप आभासी मूल्य को नष्ट कर देता है और इसे बदलने के लिए नए, शुल्क-आधारित लेनदेन को मजबूर करता है। यहाँ उस हानि के आकार के लिए कोई आंकड़ा प्रस्तुत नहीं किया गया है। — प्रति सेट रिटर्न रत्न दरों और बूस्टर ऑड्स पर निर्भर करता है, जिन्हें इस जांच में मापा नहीं गया है।\n\nट्रेडिंग कार्डस्वामित्व वाले गेम से ड्रॉप्स\n→\nरत्नकार्ड कुचला गया, शुल्क लिया गया\n→\nबूस्टर पैकक्राफ्ट करने में खर्च किए गए रत्न\n→\n3 नए कार्डमार्केट पर बेचा गया, शुल्क लिया गया\n↶\n\nयहाँ केवल यांत्रिकी का ही उल्लेख किया गया है, और ये सभी Valve की अपनी हैं — कार्ड रत्नों में बदलते हैं, रत्न बूस्टर बनाते हैं, बूस्टर कार्ड उत्पन्न करते हैं — प्रत्येक Steam ट्रेडिंग कार्ड्स FAQ में प्रलेखित है, और प्रत्येक एक कर योग्य मार्केट इवेंट है। लूप यांत्रिकी का स्रोत: Valve, Steam ट्रेडिंग कार्ड्स अक्सर पूछे जाने वाले प्रश्न ↗.\n\nयह कोई क्षण नहीं है। यह एक उद्योग है जिसकी कई वर्षों की मजबूत आधारशिला है।\n\nएक ही स्नैपशॉट महज संयोग हो सकता है। इसलिए सार्वजनिक कार्ड-बॉट निर्देशिका को प्रत्येक मौसमी Steam बिक्री पर एक बार पढ़ा गया, Wayback Machine से, 2022 से 2026 तक — ये वही सेट-स्टॉक थे जिन्हें बॉट्स ले जा रहे थे, और वही खाते, बिक्री के बाद बिक्री। अर्थव्यवस्था दिखाई देती और गायब नहीं होती; यह बनी रहती है, ऑपरेटरों के एक स्थिर मूल के साथ, और यह 100 से अधिक पर चरम पर पहुँच गई तीन मिलियन पूर्ण सेट स्टॉक में 2023 की सर्दियों की बिक्री के दौरान — एक ही समय में, एक ही निर्देशिका में रखे गए लगभग तीस लाख मूल्य की TF2 कीज़।\n\nसार्वजनिक बॉट निर्देशिका में रखे गए पूर्ण कार्ड सेट, Steam बिक्री द्वारा\n\nsteam.supply/CardBots का प्रत्येक सीज़नल सेल पर एक Wayback स्नैपशॉट। उस स्नैपशॉट की दर पर TF2 कीज़ में मूल्य जानने के लिए माउस को उस पर ले जाएँ।\n\n0.0M\n0.9M\n1.8M\n2.6M\n3.5M\nA’22\nS’23\nW’23\nS’24\nW’24\nS’25\nS’26\n401बिक्री में विभिन्न बॉट खाते देखे गए।\n595 या उससे अधिक की 7 बिक्री में मौजूद — स्थिर मुख्य\n167 की प्रत्येक बिक्री में उपस्थित, 2022–2026\n3.22एमस्टॉक में पीक सेट (विंटर 2023) ≈ $570k–790k कीज़ में\nएक सेल की बैज सीढ़ी ऊपर से कैसी दिखती है\n\nमांग पक्ष आपूर्ति से मेल खाता है। सार्वजनिक पर गर्मियों की बिक्री 2024 बैज लैडर संग्रहीत 2026-07-16 ↗, नंबर एक खाते ने बिक्री बैज तैयार किया था 1,740,645 बार — 1.74 मिलियन दस-कार्ड सेट, 17.4 मिलियन कार्ड्स एक ही प्रोफ़ाइल सजावट में समाहित। बिक्री की अपनी बाजार कीमत (प्रति सेट $0.50) पर, यानी ~$870,000 कार्ड के मूल्य का; जैसा कि वास्तव में खरीदा जाता है — TF2 कीज़ का लेन-देन लेवल-अप बॉट्स के साथ लगभग 7.6 सेट करता है — यह है ~229,000 कीज़, लगभग $410,000–$570,000 वास्तविक रूप में। दूसरा खाता: 552,000 सेट, ~$130,000–181,000.। इसके लिए कोई मानव नहीं खेलता। इसे खरीदा जाता है, और खरीद के प्रत्येक चरण का लेन-देन Valve द्वारा निपटाया जाता है।\n\nविधि और सीमाएँ: सेट-स्टॉक प्रत्येक स्नैपशॉट में सूचीबद्ध बॉट्स में जोड़ा जाता है; संख्या प्रति स्नैपशॉट बॉट्स की संख्या बिक्री के बीच तुलना योग्य नहीं है क्योंकि कुछ स्नैपशॉट केवल फीचर्ड बॉट्स दिखाते हैं और कुछ पूरी डायरेक्टरी, इसलिए स्टॉक को जो दिखाई दे रहा था उसकी न्यूनतम सीमा के रूप में पढ़ा जाता है, न कि एक जनगणना के रूप में। मुख्य मान प्रत्येक स्नैपशॉट के मध्यिका विज्ञापित प्रति-कुंजी सेट दर और $1.79–$2.49 TF2 कुंजी का उपयोग करते हैं। निरंतरता स्नैपशॉट्स के बीच SteamID64 द्वारा होती है। 2021 स्नैपशॉट्स ने पुराने पेज लेआउट का उपयोग किया और शामिल नहीं हैं। डेटा: farm-economy-timeline.json; SteamLadder से बैज स्तर; Steam Card Exchange से निर्धारित कीमतें (बिक्री के समय Wayback स्नैपशॉट, प्रति कार्ड $0.05)।\n\nऔर जब कोई बिक्री नहीं चल रही होती है, तब भी वही बेड़ा वहीं होता है।\n\nऊपर की दो तस्वीरें दो आबादी नहीं हैं। वे एक ही बेड़े हैं, जिन्हें अलग-अलग क्षणों में फोटो खींचा गया था। इस अनुभाग के शीर्ष पर पढ़ी गई निर्देशिका को एक पर पढ़ा गया था। मौसमी बिक्री के बिना एक सामान्य दिन — 2026-09-22 — और विश्राम की स्थिति में भी यह कायम रहा 91 694,673 बॉट्स और ई-कॉमर्स पूर्ण सेट: के क्रम पर 186,000 TF2 कीज़, कार्ड मूल्य $334,000–$464,000, बेकार पड़ी हैं बिक्री के बीच। यह वह न्यूनतम स्तर है जिसे संचालन तब बनाए रखता है जब कुछ भी नहीं हो रहा होता।\n\nऔर यह वही ऑपरेशन है। SteamID64 द्वारा मेल किया गया, 87 उन 91रस्टिंग बॉट्स में से — 96% — भी ऊपर दिए गए सात बिक्री स्नैपशॉट्स में दिखाई देते हैं।, उनमें से सोलह प्रत्येक में। डायरेक्टरी कोई ऐसा स्टॉल नहीं है जो बिक्री के लिए खुलता है और बाद में बंद हो जाता है; यह एक स्थायी वाणिज्यिक सूची है जिसे इसी बेड़े ने उतना बढ़ा दिया है जितना कि 3.22 लाखों सेट यह विंटर 2023 के शिखर पर रहता है और कभी शून्य तक नहीं गिरने देता। सेल तब होता है जब यह बिकता है। यह साल के बाकी समय में भी मौजूद रहता है।\n\nविश्राम निर्देशिका, बॉट-दर-बॉट\n\nप्रत्येक वर्ग 2026-09-22, पर निर्देशिका में एक बॉट है, जिसे तब हाइलाइट किया जाता है जब वह सात बिक्री स्नैपशॉट्स में भी दिखाई देता है। 91 उस दिन डायरेक्टरी में जो सूचीबद्ध था, वही है, बेड़े का आकार नहीं। — 401 बिक्री स्नैपशॉट्स में अलग-अलग खाते दिखाई देते हैं, और डायरेक्टरी विभिन्न दिनों पर एक अलग स्लाइस दिखाती है।\n\nपिछली बिक्री में देखा गया (87) पिछले स्नैपशॉट (4) से नया\n\nगैर-सेल बेसलाइन ने उसी सार्वजनिक निर्देशिका से बिना लॉगिन के 2026-09-22 पढ़ा। विश्राम मान प्रत्येक बॉट की अपनी विज्ञापित sets-per-key दर और ऊपर दी गई $1.79–$2.49 कुंजी बैंड का उपयोग करता है। ओवरलैप SteamID64 के आधार पर सात सेल स्नैपशॉट्स के विरुद्ध है। चूंकि featured-vs-full लिस्टिंग स्नैपशॉट के अनुसार भिन्न होती है, यह स्टॉक और पहचान की तुलना करता है, हेडकाउंट की नहीं। अंकगणित धारा 08.\n\n03 — सीढ़ी\nदूसरा उत्पाद आपके नाम के बगल में दिया गया नंबर है।\n\nकार्ड कच्चा माल हैं। तैयार उत्पाद एक Steam-स्तर का होता है, और Valve अपनी कीमत सेटों में निर्धारित करता है।\n\n100Steam स्तर\nलक्ष्य स्तर — ड्रैग करें या तीर कुंजियों का उपयोग करें\nएक पूरे सेट की कीमत, अमेरिकी डॉलर\n\n$0.20 जनगणना में सबसे सस्ता पूरा सेट है, $0.74 मध्यक है, $1.70 औसत है। यह आंकड़ा केवल कार्ड्स को कवर करता है — कभी भी $5.00 अनलॉक्स या गेम लाइसेंस को नहीं।\n\n55,000XP आवश्यक\n550उपभोग किए गए पूर्ण सेट\n110खेलों का स्वामित्व, स्वयं खेती करना\n$407.00उस कीमत पर कार्डों की लागत\n1,100न्यूनतम भत्ते जला दिए गए\n$5,500.00यदि कोई खाता पुन: उपयोग नहीं किया जाता है, तो $5.00 अनलॉक हो जाता है।\nपूरे सेट समाप्त, स्तर 1 से 1,000 तक\n\nएक बैज क्राफ्ट = एक पूरा सेट = 100 XP। दस के ब्लॉक के भीतर प्रत्येक स्तर नीचे वाले ब्लॉक की तुलना में 100 XP अधिक खर्च करता है।\n\n0\n12,625\n25,250\n37,875\n50,500\n1\n250\n500\n750\n1000\n667\n550 sets\n\nएक लेवल ऐसी सजावट नहीं है जिसे Valve अछूता छोड़ दे। यह खाते में सीधे जुड़ा होता है। Valve के अपने ट्रेडिंग कार्ड्स FAQ से, कि बैज बनाने पर आपको क्या मिलता है: 100XP, जो आपके Steam स्तर को बढ़ा सकता है। यदि आपका Steam स्तर बढ़ता है, तो आपकी मित्र सूची के आकार की सीमा पाँच से बढ़ा दी जाएगी।, और संभवतः आप शोकेस के साथ अपनी प्रोफ़ाइल को कस्टमाइज़ करने की क्षमता अनलॉक कर लेंगे। और बूस्टर पैक पर: आपका Steam स्तर बूस्टर पैक ड्रॉप प्राप्त करने की दर बढ़ाता है: स्तर 10: +20%… स्तर 50: +100% से आपकी ड्रॉप दर में वृद्धि होती है (i.e; दर दोगुनी हो गई है)।\n\nतो यह स्तर दो चीज़ें नियंत्रित करता है: Valve नियंत्रण: आप कितने लोगों को दोस्त बनाने की अनुमति रखते हैं, और मुफ्त कार्ड कितनी तेजी से आपकी इन्वेंटरी में गिरते हैं। दूसरी चीज़ चक्रवृद्धि की तरह काम करती है — जितने अधिक सेट आपने उपभोग किए हैं, प्लेटफ़ॉर्म उतनी ही तेजी से आपको और सामग्री प्रदान करता है।Valve ने इस पुनर्निवेश चक्र को उत्पाद में ही शामिल कर दिया।\n\nविनिमय दर स्थिर है और प्रकाशित की गई है। एक बैज क्राफ्ट एक पूरा सेट खर्च करता है और 100 XP प्रदान करता है। आप एक ही खेल के लिए अधिकतम पाँच बार सेट बना सकते हैं। हर स्तर की XP लागत हर दस स्तरों पर बढ़ती है। इससे निम्नलिखित परिणाम निकलते हैं, और यहाँ कुछ भी अनुमानित नहीं है:\n\nSteam स्तर\tयह जो भी सेट उपभोग करता है, उन्हें पूरा करता है।\tखेल जिन्हें आपको खुद बनाने के लिए अपने पास रखना चाहिए\tरिकॉर्ड पर सबसे सस्ते सेट ($0.20)\tमाध्यिका सेट पर ($0.74)\tपैमाना\n10\t10\t2\t$2.00\t$7.40\t\n50\t150\t30\t$30.00\t$111.00\t\n100\t550\t110\t$110.00\t$407.00\t\n200\t2,100\t420\t$420.00\t$1,554.00\t\n500\t12,750\t2,550\t$2,550.00\t$9,435.00\t\n667\t22,579\t4,516\t$4,515.80\t$16,708.46\t\n\n667 यह काल्पनिक नहीं है। यह सार्वजनिक निर्देशिका में एक ही बॉट द्वारा विज्ञापित उच्चतम स्तर है, जहाँ वह ग्राहक को ले जा सकता है, उन 33,359 सेटों में से जिन्हें वह 6,117 खेलों में रखता है। चौथा कॉलम उसी सीढ़ी को दर्शाता है जिसकी कीमत जनगणना में कहीं भी उपलब्ध सबसे सस्ते पूर्ण सेट के मुकाबले तय की गई है; पांचवां कॉलम माध्य के मुकाबले। ये दोनों केवल कार्ड्स के लिए बाजार मूल्य हैं और इनमें $5.00 अनलॉक तथा गेम लाइसेंस पूरी तरह शामिल नहीं हैं।\n\nवक्र की जाँच कैसे की गई, क्योंकि Valve इसे प्रकाशित नहीं करता है।\n\nValve बैज दर बताता है (हर 100 XP आपको एक अतिरिक्त Steam स्तर प्रदान करता है।) और फिर उस पर हेज करता है — (कम से कम शुरुआत के लिए) — वृद्धि को प्रकाशित किए बिना। ऊपर प्रयुक्त वक्र मानक है, जिसमें दस के ब्लॉक के भीतर प्रत्येक स्तर नीचे के ब्लॉक की तुलना में 100 XP अधिक खर्च करता है। इसे मानने के बजाय निर्देशिका के विरुद्ध सत्यापित किया गया: हर उस बॉट के लिए जिसकी विज्ञापित अधिकतम सीमा पाँच-प्रति-गेम की सीमा के बजाय उसके स्टॉक द्वारा सीमित है, इस वक्र से गणना किया गया स्तर ठीक वैसा ही है जैसा बॉट विज्ञापन करता है। — 541 बनाम 541, 494 बनाम 494, 464 बनाम 464. जहाँ कैप लागू होता है, वहाँ गणना किया गया आंकड़ा कुछ स्तर ऊँचा होता है, जो कि एक ऐसा कैप जो प्रति-गेम स्टॉक गहराई पर भी निर्भर करता है, वैसा ही होना चाहिए। स्तर 667. से ऊपर के वक्र के बारे में कोई दावा नहीं किया गया है।\n\nअनुभाग 02 के बगल में दी गई सीढ़ी पढ़ें और व्यवसाय का आकार स्पष्ट हो जाएगा। किसी एक खाते को स्तर 500, पर लाने के लिए किसी को 12,750 के पूर्ण सेट इकट्ठा करने होंगे। उन सेटों में से प्रत्येक के लिए कम से कम दो खातों की ड्रॉप अलाउंसेंस लेनी पड़ी, उनमें से प्रत्येक खाते ने $5.00 के द्वार को पार किया था, और प्रत्येक के पास वह खेल था। एक प्रोफ़ाइल के शीर्ष पर एक वैनिटी नंबर कम से कम 25,500 खर्च किए गए ड्रॉप भत्तों पर टिका रहता है। Valve यह व्यापार नहीं खो रहा है। Valve इसके प्रत्येक भाग का काउंटरपार्टी है।\n\n04 — आँकड़े\nयह खंड खेती का अस्पष्ट रूप से वर्णन नहीं करता है। यह इसे सूचीबद्ध करता है।\n\n§4.C कोई सामान्य एंटी-बॉट वाक्य नहीं है। इसके सूचीबद्ध उदाहरण एक के बाद एक कार्ड फ़ार्म द्वारा उत्पादित दो चीज़ों का नाम लेते हैं।\n\nआप Steam पर सामग्री और सेवाओं के साथ किसी भी प्रकार से इंटरैक्ट करने के लिए किसी भी प्रकार की स्क्रिप्ट्स, बॉट्स, मैक्रोज़, या अन्य गैर-मानव-नियंत्रित प्रणालियों ('ऑटोमेशन') का उपयोग नहीं कर सकते, जिनमें शामिल हैं, लेकिन इन्हीं तक सीमित नहीं:\n\nSteam खाते की निर्माण प्रक्रिया का स्वचालन,\nगेमप्ले आँकड़ों में हेरफेर (e.g., बढ़ा-चढ़ाकर बताई गई जीत या हार, XP, प्लेटाइम),\nवास्तविक उपयोगकर्ता इनपुट के बिना पुरस्कार या प्रगति अर्जित करना,\nस्वचालित माध्यमों से निर्णय प्रक्रियाओं (जैसे सहकर्मी समीक्षा या 'ओवरवॉच') में भाग लेना, जिसमें सूचित निर्णय के बजाय स्क्रिप्टेड कार्रवाई के माध्यम से परिणामों को प्रभावित करना या उपयोगकर्ताओं की रिपोर्ट करना शामिल है।\n— Steam सब्सक्राइबर समझौता § 4.C ↗ संचित 2026-09-24 ↗ · प्राप्त और शब्दशः उद्धृत 2026-09-22\n…खेलने का समय\n\nनिष्क्रिय घंटे भूतिया घंटे नहीं होते। ASF FAQ सीधे इस प्रश्न का उत्तर देता है — ASF के माध्यम से खेती किए गए खेलों का प्लेटाइम क्यों नहीं बढ़ता? — के साथ: यह करता है, लेकिन वास्तविक समय में नहीं।Steam आपके खेलने के समय को निश्चित अंतरालों में रिकॉर्ड करता है और इसके लिए अपडेट शेड्यूल करता है… यह आमतौर पर लगभग हर 30 मिनट में अपडेट होता है।\n\nवे घंटे Valve के रिकॉर्ड में, Valve के स्टोर पेजों पर, और Valve द्वारा अपने स्वयं के प्रकाशित समवर्ती-खिलाड़ी गणनाओं में दर्ज होते हैं। Steam चार्ट ↗ संग्रहित 2026-09-23 ↗उन आंकड़ों में एक निष्क्रिय खाता खेलने वाले खाते से अलग नहीं किया जा सकता। प्लेटफ़ॉर्म द्वारा बाहरी रूप से उद्धृत एंगेजमेंट की संख्या उस आबादी पर आधारित होती है जिसमें, प्लेटफ़ॉर्म के अपने नियम के अनुसार, खेलने वाले नहीं होने वाले खाते भी शामिल हैं।\n\n…वास्तविक उपयोगकर्ता इनपुट के बिना\n\nयह idled कार्ड ड्रॉप की परिभाषा है, जिसे Valve ने लिखा है। यह Steam स्तर, बैज, बूस्टर-पैक पात्रता और इसके साथ मिलने वाले प्रोफ़ाइल XP की भी परिभाषा है — ASF FAQ इस टूल की पुष्टि करता है। बूस्टर पैक प्राप्त करने की क्षमता को बनाए रखता है, क्योंकि यह आधिकारिक क्लाइंट की तरह ही लॉग इन करता है।\n\nतो पुरस्कार प्रणाली और निषिद्ध कृत्य एक ही तंत्र हैं जिन्हें दो दृष्टिकोणों से देखा जाता है।Valve ने पुरस्कार को कौशल के बजाय समय के आधार पर उत्पन्न होने वाला बनाया, फिर एक प्रावधान लिखा जिसमें समय व्यतीत करने वाले व्यक्ति के अलावा किसी अन्य माध्यम से पुरस्कार उत्पन्न करने पर प्रतिबंध लगाया गया।\n\n05 — व्यावसायिक उपयोग का जाल\nकिसान द्वारा तैयार किए गए कार्ड से हर निकास उस निकास के समान है जिसे लाइसेंस मना करता है — और Valve दरवाजे पर शुल्क वसूलता है।\n\nयह वह हिस्सा है जिसे \"जिम्मेदारी से\" खेती करके हल नहीं किया जा सकता। यह लाइसेंस व्यक्तिगत, गैर-व्यावसायिक उपयोग के लिए है, और एक कार्ड तभी खेती करने लायक बनता है जब वह व्यक्तिगत होना बंद कर देता है।\n\n§ 2.A — लाइसेंस\n\nValve इस प्रकार एक गैर-अनन्य लाइसेंस और अधिकार प्रदान करता है, और आप इसे स्वीकार करते हैं, कि आप सामग्री और सेवाओं का उपयोग अपने लिए कर सकते हैं। व्यक्तिगत, गैर-व्यावसायिक उपयोग (जहाँ वाणिज्यिक उपयोग यहाँ या लागू सदस्यता शर्तों में स्पष्ट रूप से अनुमत हो, वहाँ को छोड़कर)\n\n§ 2.G — प्रतिबंध\n\nआपको हक नहीं है: … (iii) सामग्री और सेवाओं या उनके किसी भी हिस्से का किसी भी व्यावसायिक उद्देश्य के लिए शोषण करना, सिवाय इसके कि इस अनुबंध में कहीं और (किसी भी सदस्यता शर्तों या उपयोग के नियमों सहित) स्पष्ट रूप से अनुमति दी गई हो।\n\n§ 3.D — शुल्क\n\n\"Valve सब्सक्रिप्शन मार्केटप्लेस में लेनदेन के लिए शुल्क ले सकता है। लेनदेन पूरा होने से पहले आपको किसी भी शुल्क के बारे में सूचित किया जाएगा।\n\nतीनों को एक साथ पढ़ें और स्थिति बंद हो जाती है।\n\nएक कार्ड जो रखा जाता है, खेत के लिए बेकार है। एक कार्ड जिसे बेचा जाता है, ट्रेड किया जाता है या रत्नों में कुचला जाता है, उसका उपयोग मूल्य सृजन के लिए किया गया है — और ईValve ने अपनी प्रवर्तन पत्र में बताया है कि वह इसे क्या कहता है: 170 बॉट्स के ऑपरेटर को बताया गया कि खाता Steam पर अवैध रूप से संग्रहणीय कार्ड इकट्ठा करने के लिए, साथ ही संबंधित और केवल वाणिज्यिक गतिविधियों के लिए भी इस्तेमाल किया जाता था। उस स्थिति में कार्ड बाजार में पहुँच गए। बिक्री पूरी हो गई। शुल्क वसूल कर लिया गया। प्रतिबंध बाद में लगा।\n\nउस दरवाजे पर शुल्क 15%. नहीं है। एक फार्म्ड कार्ड पर यह दो-तिहाई तक पहुँच जाता है।\n\n§ 3.D आरक्षित एक शुल्क. जिस कार्ड पर वास्तव में कोई फार्म उत्पादन करता है, उस शुल्क का विज्ञापित शुल्क से कोई लेना-देना नहीं है ~15%. द कम्युनिटी मार्केट लेता है 5% Steam लेनदेन शुल्क और एक 10% खेल शुल्क, प्रत्येक का न्यूनतम $0.01 है। (Valve का अपना Community Market FAQ)। एक सेंट पर सूचीबद्ध कार्ड पर वे फ्लोर हैं कीमत: खरीदार तीन सेंट का भुगतान करता है, जिनमें से दो शुल्क हैं। राउंडिंग फ्लोर शीर्षक 15% को एक प्रभावी लेवी में बदल देता है जो बढ़कर 66.7% ठीक वहीं जहाँ कार्ड बाज़ार फलता-फूलता है — एक कार्ड के कुछ सेंट।\n\nसमुदायिक बाज़ार बिक्री पर प्रभावी शुल्क, विक्रेता की माँग मूल्य के अनुसार\n\n5% Steam + 10% गेम, प्रत्येक की न्यूनतम कीमत $0.01. है। छायांकित बैंड वह क्षेत्र है जहाँ ट्रेडिंग कार्ड वास्तव में ट्रेड होते हैं — लगभग $0.03–$0.05 प्रति कार्ड।\n\n0%\n10%\n20%\n30%\n40%\n50%\n60%\n70%\ncards\n$0.01\n$0.10\n$0.20\n$0.30\n$0.40\n$0.50\n66.7%\nविक्रेता चाहता है\tSteam 5% (न्यूनतम $0.01)\tगेम 10% (न्यूनतम $0.01)\tखरीदार देगा\tसंयुक्त शुल्क\n$0.01\t$0.01\t$0.01\t$0.03\t66.7%\n$0.03\t$0.01\t$0.01\t$0.05\t40.0%\n$0.05\t$0.01\t$0.01\t$0.07\t28.6%\n$0.08\t$0.01\t$0.01\t$0.10\t20.0%\n$1.00\t$0.05\t$0.10\t$1.15\t13.0%\n\n10% गेम शुल्क उस ऐप को जाता है जिसने कार्ड जारी किया; 5% Valve का अपना है, और Valve के अपने शीर्षक और बेस इन्वेंटरी आइटम्स पर पूरा शुल्क Valve का होता है। किसी भी हाल में पैसा किसान से निकल जाता है — तीन-सेंट का कार्ड बेचने पर एक सेंट मिलता है और दो सेंट खो जाते हैं। इसे उस सैकड़ों हज़ारों पाँच सेंट से कम मूल्य के कार्ड बिक्री से गुणा करें जो एक फार्म उत्पन्न करता है और Valve द्वारा वसूली जा सकने वाली शुल्क यह व्यवसाय मॉडल है, न कि एक फुटनोट। स्रोत: Steam सामुदायिक बाज़ार अक्सर पूछे जाने वाले प्रश्न — शुल्क ↗ संचित 2026-09-21 ↗, 2026-09-22 पढ़ें; वक्र उन दो प्रकाशित दरों और उनके $0.01 के निचले स्तरों पर अंकगणितीय है।\n\nइससे बचने के लिए इस उपकरण की कोई भी कॉन्फ़िगरेशन नहीं है। इसे एक व्यक्ति द्वारा, एक ही खाते पर, पूर्ण संयम के साथ चलाया जा सकता है — और जिस क्षण वह व्यक्ति वॉलेट फंड के लिए एक भी फार्म्ड कार्ड बेचता है, §2.G में वही दंड उन पर भी लागू होता है जो दस हजार ऑपरेटरों पर होता है। Valve इसलिए इसने अपने स्वयं के बाज़ार में लगभग हर कार्ड विक्रेता के खिलाफ लागू करने योग्य एक उल्लंघन आरक्षित रखा है, और वास्तव में उन सभी के खिलाफ इसे लागू करने से इनकार कर दिया है। उस दर पर लागू किया गया नियम नियम नहीं है। यह एक विकल्प है। यह प्रदर्शनी जो सवाल उठाती है वह यह नहीं है कि कार्ड किसानों को क्यों बर्दाश्त किया जाता है; बल्कि यह है कि एक अकेले उपयोगकर्ता के खिलाफ वही विकल्प क्यों लागू किया जाता है जो कार्ड बेचता है, जबकि वे कार्ड जिनसे यह व्यावसायिक अर्थव्यवस्था—ट्रेडिंग सेवाएं, लेवल-अप बॉट्स, थोक विक्रेता—खुलेआम चलती रहती है, और उनमें से एक सबसे बड़े समूह का संचालन एक Valve कर्मचारी द्वारा किया जाता है (§08)। उल्लंघन छोटे धारक के खिलाफ आरक्षित है और मशीन के लिए माफ कर दिया जाता है।\n\n06 — प्रवर्तन रिकॉर्ड\nकोई सूचना नहीं, लहरों में, और यह फोन नंबर पर नीचे की ओर यात्रा करता है।\n\nValve नो-नोटिस पावर को समझौते में ही लिखा, ऑटोमेशन क्लॉज के एक क्लॉज बाद।\n\nValve किसी भी ऐसे आचरण या गतिविधि के लिए आपके खाते(ओं) या किसी विशेष सदस्यता को प्रतिबंधित या समाप्त कर सकता है जो अवैध हो, धोखाधड़ी या स्वचालन (Automation) का गठन करे, या Steam ऑनलाइन आचरण नियमों का उल्लंघन करे। आप स्वीकार करते हैं कि Valve को आपकी सदस्यता(ओं) और/या खाते को समाप्त करने से पहले आपको सूचना देने की आवश्यकता नहीं है।\"\n\n— Steam सब्सक्राइबर समझौता § 4.D ↗ संचित 2026-09-24 ↗ · सत्यापित शब्दशः 2026-09-22\n\n1,000+ बॉट्स · व्यापार प्रतिबंधित। Steam ऐसा लगता है कि इस खाते का उपयोग बॉट खातों के एक नेटवर्क को प्रबंधित करने के लिए किया गया था। बॉटिंग, ईमेल सेवा सदस्यता समझौते का उल्लंघन है।\n\n170+ बॉट्स · स्थायी रूप से प्रतिबंधित, 2017 विंटर सेल। इस खाते का उपयोग Steam पर अवैध रूप से संग्रहणीय कार्ड इकट्ठा करने के साथ-साथ संबंधित और केवल वाणिज्यिक गतिविधियों के लिए किया गया था। यह खाता स्थायी रूप से अवरुद्ध कर दिया गया है और Steam सहायता इस मामले पर अतिरिक्त सहायता प्रदान नहीं कर सकती।\n\n120+ बॉट्स · स्थायी रूप से प्रतिबंधित। इस और अन्य खातों का उपयोग हमारे नेटवर्क इंफ्रास्ट्रक्चर को बाधित करने के लिए किया गया था, जो कि Steam की ऑनलाइन आचार संहिता का उल्लंघन है।\n\n— Steam समर्थन संदेश ArchiSteamFarm FAQ के \"क्या किसी को इसके लिए प्रतिबंधित किया गया?\" अनुभाग में पुनरुत्पादित। स्रोत ↗ · सत्यापित शब्दशः 2026-09-22\n4 का मामला — जून 2025, निष्क्रिय CS2 पर VAC प्रतिबंध\n\nउपरोक्त तीनों से बाद का एक और प्रकरण परियोजना के अपने ट्रैकर में दर्ज है: उन खातों को जिन्हें केवल इस टूल के माध्यम से Counter-Strike 2 निष्क्रिय किया गया था, प्राप्त हुए वीएसी प्रतिबंध — चीट-रोधी प्रकार, प्रशासनिक प्रकार नहीं। मेंटेनर का रुख है कि आइडलिंग एक ऐसा कारण नहीं हो सकती, क्योंकि यह Steam को यह बताने के अलावा और कुछ नहीं करता कि हम दिए गए खेल को खेल रहे हैं। कारण विवादित है। यह कि खातों पर प्रतिबंध लगाया गया था, विवादित नहीं है।\n\n— ArchiSteamFarm चर्चा #3440, ने 26 जून 2025 ↗ खोला। · पढ़ें 2026-09-22\n\nएक मुख्य खाता कैसे मरता है\n\nउसी थ्रेड में एक परियोजना सहयोगी प्रसारण नियम का वर्णन करता है: खातों पर प्रतिबंध लगाया जा सकता है। \"by chain\", यदि वे एक ही फोन नंबर का उपयोग कर रहे हैं — यह शायद सिर्फ एक VAC प्रतिबंध हो, जिसे प्रतिबंधित खाते से जुड़े 'साफ' खातों तक फैलाया गया हो।\n\nSteam Guard को एक फोन नंबर की आवश्यकता होती है। फार्म्स ऑपरेटर के फोन नंबर पर बनाए जाते हैं। इसलिए प्रवर्तन केवल डिस्पोजेबल खातों पर ही नहीं रुकता: यह साझा पहचानकर्ता के माध्यम से उस खाते तक जाता है जिसमें लाइब्रेरी, मित्रों की सूची और इन्वेंटरी होती है। यह वह तंत्र है जिसे एक परियोजना सहयोगी इस प्रकार वर्णित करता है कि कैसे एक ही कार्रवाई ऑपरेटर का मुख्य खाता फार्म के साथ हटा देती है — और यही कारण है कि प्रवर्तन की लहर में होने वाले नुकसान को $5 खातों में नहीं मापा जाता। (ASF GitHub चर्चा #3440 में एक परियोजना योगदानकर्ता द्वारा वर्णित; कोई आधिकारिक Valve पुष्टि या औपचारिक मिसाल रिकॉर्ड में नहीं है।)\n\nतीन अलग-अलग एजेंटों द्वारा, पाँच साल के अंतराल पर, वही पैराग्राफ\n\nजो खंड खेती को उल्लंघन बनाता है — व्यक्तिगत, गैर-व्यावसायिक लाइसेंस का व्यावसायिक उपयोग — वह केवल फार्मों के लिए आरक्षित नहीं है। यह वही कारण है जो Steam ट्रेडिंग के चलते खाता बंद करते समय देता है, और यह कारण एक टेम्पलेट के रूप में आता है। नीचे तीन उदाहरण दिए गए हैं, जिन्हें प्राप्त करने वालों ने पाँच वर्षों के अंतराल पर तीन अलग-अलग नामित एजेंटों से प्रकाशित किया है।\n\nSteam समर्थन की ओर से संदेश: 29 सितंबर @ 7:56अपराह्न\n\n\"The account you are writing in for has been locked for violating the terms of the Steam Subscriber Agreement. The account has been identified as being used for commercial purposes based on trading, community reports, and other factors.\n\nThis lock is permanent and Steam Support cannot help you further with this.\n\nBecause we have provided all the information we have I am closing this help request. Please note you will not receive further replies regarding this issue.\n\nRegards,\nHal\"\n\nयह सहायता अनुरोध बंद कर दिया गया है।\n29 सितंबर 2020. प्राप्तकर्ता द्वारा टिप्पणी के साथ पोस्ट किया गया आरआईपी ट्रेडिंग। — @gergelyszabo94 ↗\nSteam सहायता संदेश 12 पर जुलाई से 22:41 बजे तक\n\n\"The account you are writing in for has been locked for violating the terms of the Steam Subscriber Agreement. The account has been identified as being used for commercial purposes based on trading, community reports, and other factors.\n\nThis lock is permanent and Steam Support cannot help you further with this.\n\nBecause we have provided all the information we have I am closing this help request. Please note that future help requests submitted regarding the account lock may be closed without a reply.\n\nSteam Support\nVido\"\n\nयह सहायता अनुरोध बंद कर दिया गया है।\n12 जुलाई 2024,पुर्तगाली इंटरफ़ेस। प्राप्तकर्ता एक पेशेवर CS2 खिलाड़ी है: पहले ही स्टीम सपोर्ट से संपर्क कर चुका हूँ, लेकिन केवल स्वचालित प्रतिक्रियाएँ ही मिल रही हैं… फेसइट नहीं खेल पा रहा हूँ और पेशेवर मैच भी नहीं खेल पा रहा हूँ। — @prcs25 ↗ संग्रहीत 2024-07-15 ↗\nप्राप्तकर्ता द्वारा उद्धृत, r/steamsupport\n\n\"Hello, The account you are writing in for has been locked for violating the terms of the Steam Subscriber Agreement. The account has been identified as being used for commercial purposes based on trading, community reports, and other factors.\n\nThis lock is permanent and Steam Support cannot help you further with this.\n\nBecause we have provided all the information we have I am closing this help request. Please note that future help requests submitted regarding the account lock may be closed without a reply.\n\nSteam Support\nSally\"\n\nतीन अलग-अलग अनुरोधों पर तीन बार प्राप्त हुआ।\n29 मार्च 2025. लेखक लॉक का विरोध नहीं कर रहा था — उनका खाता और उनका ईमेल चोरी हो गया था और वे एक्सेस की मांग कर रहे थे: मैं प्रतिबंध के बारे में नहीं पूछ रहा हूँ और मैं इसका विरोध भी नहीं कर रहा हूँ, मैं बस अपने Steam खाते तक पहुँच चाहता हूँ… Valve ने हर अनुरोध पर यही उत्तर कॉपी-पेस्ट किया है और अनुरोध बंद कर दिया है। — आर/स्टीमसपोर्ट ↗, इस जांच के अपने शिकायत कोष में रखा गया\n\nशब्द-शब्द, अल्पविराम-अल्पविराम, पैंतालीस महीनों में, तीन एजेंटों और दो इंटरफ़ेस भाषाओं के माध्यम से। पूरे पाठ में एकमात्र संपादन अंतिम वाक्य का कठोर होना है, जो '2020' और '2024,' के बीच से आता है। आपको और कोई जवाब नहीं मिलेगा के लिए भविष्य की सहायता अनुरोध… बिना उत्तर के बंद किए जा सकते हैं। इन निर्णयों को जो भी प्रक्रिया उत्पन्न करती हो, यह पत्र उसका अभिलेख नहीं है। उल्लिखित आधार \"व्यापार, सामुदायिक रिपोर्टें, और अन्य कारक\" हैं — एक श्रेणी, एक अज्ञात स्रोत की रिपोर्ट, और एक अनाम शेष।\n\nपाँच और मामले, एक ही तरीके से एकत्र किए गए। पहले तीन एक ही श्रेणी के हैं और परिणाम भी समान है; अंतिम दो एक ही डेस्क हैं जो एक ही शब्दों में एक अलग नियम का उत्तर देती हैं:\n\nदिनांक\tखाते ने क्या किया\tक्या हुआ\tस्रोत\n04.12.2021\tBuying and selling on Buff — \"I've done nothing else than some buying and selling on buff aka P2P trading\"\tCommunity ban: no market, no trading, expensive inventory frozen\tr/csgomarketforum ↗ archived 2025-03-27 ↗\n06.12.2021\tOne-way P2P trades through Buff and Bitskins for loadouts and trade-ups\tPermanent commercial-use lock plus community lock: \"stuck in a pseudo invisible mode… My profile is also stuck on private\"\tr/GlobalOffensiveTrade ↗ archived 2021-12-06 ↗\n20.12.2024\tAccount held since 2017, thousands of hours; trades on community marketplaces for themed loadouts and trade-ups\tPermanent lock with community lock, no prior warning or strike; support \"say their decision is final\", replies are automated\tr/csgomarketforum ↗ archived 2025-06-27 ↗\n23.12.2024\tReturning user adds wallet funds after a year away, over a VPN used \"only for general internet security\"\tPermanent community ban with no reason given at all: \"the ban is permanent and they cannot provide further information and that further tickets may be closed without response.\" 196 upvotes, 340 replies\tr/steamsupport ↗\n04.08.2026\tYears of purchases from Iran; the writer states they never posted, never used the Market, never used the forums\tCommunity access locked until 2038 over \"sanctioned regions\"; ticket closed by an agent named Azul. The same account's refund from the same Iranian IP had been approved a year earlier. The library and the money stay with Valve.\tr/pcgaming ↗\n\nअंतिम पंक्ति बाकी सभी से अलग नियम है — प्रतिबंध अनुपालन, वाणिज्यिक उपयोग नहीं — और इसे शामिल किया गया है क्योंकि उत्तर का स्वरूप बिल्कुल समान है: एक श्रेणी, कोई साक्ष्य नहीं, कोई अपील नहीं, एक बंद टिकट। यह एक ऐसा प्रश्न भी उठाता है जो अन्य नहीं उठाते। यदि खाता सेवा देना गैरकानूनी था, तो वर्षों से भुगतान स्वीकार करना भी गैरकानूनी था। इन दोनों में से एक स्थिति गलत होनी ही है, और केवल एक ही स्थिति ने ग्राहक को कुछ खर्च कराया।\n\nइनमें से सभी आठ को Internet Archive के स्नैपशॉट्स के माध्यम से '2026-09-22', '2021' और 'December-2024' थ्रेड्स में पढ़ा गया, और बाकी को सार्वजनिक Reddit फ्रंटएंड के जरिए, क्योंकि Reddit ने संग्रह करने वाले होस्ट से सीधे अनुरोधों को अस्वीकार कर दिया था। दो पत्र, '2020' और '2024', मूल पोस्ट्स से संलग्न स्क्रीनशॉट्स से प्रतिलिपि किए गए हैं, जो अभी भी लाइव हैं। इस जांच में इन किसी भी खाते को निर्दोष या दोषी नहीं ठहराया गया है — यही तो मुख्य बात है। न तो कोई पाठक और न ही कोई नियामक अक्षर से यह बता सकता है।\n\nस्रोत पर नोट — ऑपरेटर-स्तरीय हानियाँ\n\nइस जांच द्वारा सर्वेक्षण किए गए ऑपरेटरों ने लगभग इस स्तर के नुकसान की सूचना दी। प्रत्येक में पाँच से दस हजार खाते एकल प्रवर्तन तरंगों में, मुख्य खातों को फार्म के साथ लिया गया। उस कैनवास को यहाँ प्रथम-पक्ष रिपोर्टिंग के रूप में दर्ज किया गया है, न कि निष्कर्ष के रूप में। इसका कोई प्रकाशित नमूना आकार नहीं है, कोई निश्चित संग्रह तिथि नहीं है, प्रति खाते सत्यापन नहीं है, और इस पृष्ठ पर कोई अन्य संख्या इस पर निर्भर नहीं करती; अनुभाग 02 में जो दो पंक्तियाँ इस पर आधारित हैं, उन्हें उसी प्रकार चिह्नित किया गया है।\n\nयह दो कारणों से छोड़े जाने के बजाय कहा गया है। ऊपर दिया गया चेन-बैन तंत्र ठीक उसी पैटर्न के लिए दस्तावेजीकृत स्पष्टीकरण है। और एक नियामक Valve से वह एकमात्र रिकॉर्ड प्राप्त कर सकता है जो इसे सुलझा देगा: कि कितने खातों पर स्वचालन के लिए कार्रवाई की गई, किन तरंगों में, और उन खातों में से प्रत्येक ने स्टोर बंद होने से पहले कितना खर्च किया था। जब तक वह रिकॉर्ड मौजूद नहीं है, आंकड़ा वहीं रहेगा — रिपोर्ट किया गया, जिम्मेदार ठहराया गया और अप्रमाणित।\n\n07 — विषमता\nएक ही मेज के दोनों ओर\n\nउस प्रमाण मानक को उसी मानक से तुलना करें जो Valve ने अपनी सहायता संचालन पर लागू किया था। दाहिने स्तंभ में इस दस्तावेज़ का अपना घटना रजिस्टर है, जिसे वहाँ मौजूद सावधानियों के साथ पुनरुत्पादित किया गया है।\n\nएक ग्राहक, व्यापार के लिए\n\nआठ प्रलेखित मामले, 2020–2026\n\nआचरण\nतीसरे पक्ष के मार्केटप्लेस पर वस्तुएँ बेचना या खरीदना; एक मामले में कोई आचरण ही नहीं था — खाता चोरी हो गया था।\nप्रमाण दिखाया गया\nकोई नहीं। व्यापार, सामुदायिक रिपोर्टों और अन्य कारकों के आधार पर।\nसूचना\nकोई नहीं। Valve ने §4.D में इसे आरक्षित रखा: Valve को आपको समाप्त करने से पहले आपको सूचना देने की आवश्यकता नहीं है।\nअपील\nयह लॉक स्थायी है और Steam समर्थन इस मामले में आपकी और मदद नहीं कर सकता।\nटिकट\nपहले उत्तर पर बंद कर दिया गया। आगे के अनुरोध बिना जवाब के बंद किया जा सकता है।\nपहुंच\nप्रोफ़ाइल, मित्रों की सूची, चैट, मार्केट, इन्वेंटरी, और वास्तविक धन से खरीदा गया प्रत्येक आइटम।\nअवधि\nस्थायी।\nवॉल्यूम के लिए एक स्वचालित बॉट बेड़ा\n\n694,673 91 बॉट्स में सार्वजनिक स्टॉक में संपूर्ण सेट\n\nआचरण\nहजारों खातों में एक साथ स्वचालित हेडलेस स्क्रिप्ट चलाकर निष्क्रिय कार्डों को निष्क्रिय करना, बड़े पैमाने पर बैज बनाना और सेट का व्यापार करना।\nप्रमाण दिखाया गया\nखुले तौर पर प्रकाशित बॉट डायरेक्टरी (steam.supply, SteamLvlUp) और लाखों सदस्यों वाले सार्वजनिक समूह।\nसूचना\nशून्य हस्तक्षेप। 88.97% किसी भी प्रकार का प्रतिबंध न रखें; 99.8% के शेष प्रतिबंध केवल दिखावटी हैं।\nअपील\nआवश्यक नहीं। बेड़े कई वर्षों के जीवनचक्र के दौरान बिना किसी रुकावट के निरंतर संचालित होते हैं।\nटिकट\n—\nपहुंच\nअसीमित इन्वेंटरी विनिमय, बैज स्तर वृद्धि और बाजार तरलता।\nValve को लाभ\n$26.8M+ न्यूनतम स्टोर खर्च ($5.00 प्रति खाता प्रवेश द्वार) और 15% सामुदायिक बाज़ार लेनदेन कटौती में।\nइससे जो सवाल बचता है, वह सीधे शब्दों में यह है।\n\nएक व्यक्तिगत ग्राहक जो कार्ड या आइटम का मैन्युअल रूप से व्यापार करता है, §4.C (स्वचालन) या §2.G (व्यावसायिक उपयोग) के तहत स्थायी, अपील-अयोग्य प्रतिबंध का सामना करता है। एक स्वचालित फार्मिंग फ्लीट जो हजारों खातों में हेडलेस बॉट्स चलाता है, खुलेआम एक 88.97%-अछूत दर पर संचालित होती है। Valve दोनों का लाभार्थी है।\n\nअसंतुलन आर्थिक है: व्यक्तिगत व्यापारी प्लेटफ़ॉर्म से मूल्य निकालते हैं, जबकि स्वचालित कार्ड बेड़े मिलियनों डॉलर को Valve के स्टोर खर्च गेट ($5.00 प्रति खाता) में पंप करते हैं और प्रत्येक पुनर्विक्रय पर लेनदेन शुल्क को बढ़ावा देते हैं। प्रवर्तन लिखित नियमपुस्तिका का पालन नहीं करता; यह राजस्व मॉडल का पालन करता है।\n\n08 — शासन\nकार्ड अर्थव्यवस्था का संचालन कौन करता है\n\nइस दस्तावेज़ की बार-बार सामने आने वाली निष्कर्ष — कि Steam के आसपास की तृतीय-पक्ष परत Steam के भीतर से ही स्टाफ की जाती है — कार्ड अर्थव्यवस्था में भी लागू होती है, और यह किसी विशिष्ट स्थान पर समाप्त होती है: कोई स्वतंत्र व्यक्ति यह गिन नहीं सकता कि Valve का प्रवर्तन वास्तव में क्या करता है, क्योंकि गिनने वाली पार्टी उसी परत के भीतर बैठी है। नीचे दी गई हर तथ्य Valve के अपने सार्वजनिक समूह और प्रोफ़ाइल पृष्ठों से पढ़ी गई है, जो 2026-09-22 पर हैं, और किसी भी ब्राउज़र में इसे दोबारा देखा जा सकता है।\n\nValve का एक कर्मचारी सबसे बड़े कार्ड-ट्रेडिंग समूह का संचालन करता है। Valve कर्मचारी\n\nकार्डट्रेड्स ↗ अपने ही हेडर में स्वयं को के रूप में वर्णित करता है Steam कार्ड एक्सचेंज आधिकारिक समूह और ले जाता है 97,114 सदस्यइसके सूचीबद्ध मॉडरेटर — वे खाते जो उस समूह को नियंत्रित करते हैं — हैं मिक्मेन, सार्जेंट फॉपर और एफ़ार्न्सवर्थ ↗.\n\nवह अंतिम प्रोफ़ाइल Valve की अपनी साइट मार्कअप द्वारा Valve कर्मचारी के रूप में चिह्नित है — उस पेज पर कर्मचारी का प्रोफ़ाइल शीर्षक वाल्व — अपना स्थान इस प्रकार बताता है बेलव्यू, वाशिंगटन, और का हिस्सा है Valve, Steam और Steam ट्रेडिंग कार्ड समूह समूह। SteamID64 76561197960434622, सदस्य 12 से सितंबर 2003.\n\nयह अवलोकन संरचनात्मक है, व्यक्तिगत नहीं, और यह नहीं एक स्वचालन बिंदु — एक कार्ड-ट्रेडिंग समूह का मॉडरेटर बॉट नहीं चला रहा है, और यहाँ कुछ भी इसके विपरीत नहीं बताता। मुद्दा उस खंड में है धारा 07Steam कार्ड एक्सचेंज एक तृतीय-पक्ष वाणिज्यिक कार्ड सेवा है; तृतीय-पक्ष सेवाओं के माध्यम से ट्रेडिंग कार्ड करना वही व्यवहार है जिसके लिए Valve सामान्य खातों को स्थायी रूप से लॉक कर देता है। व्यापार, सामुदायिक रिपोर्टों और अन्य कारकों के आधार पर वाणिज्यिक उद्देश्यों के लिए उपयोग किया जाता है। Valve का एक कर्मचारी उस सेवा के आधिकारिक साठ-सत्तर हजार लोगों वाले समुदायिक समूह में सूचीबद्ध मॉडरेटर की भूमिका निभाता है।\n\nयहाँ किसी भी व्यक्ति के खिलाफ किसी भी प्रकार का गलत कार्य करने का कोई आरोप नहीं लगाया गया है।, और उस भूमिका में क्या शामिल है, इस बारे में कोई निष्कर्ष नहीं निकाला जाता। असमानता ही निष्कर्ष है: जब कोई साधारण खाता किसी तीसरे पक्ष के कार्ड या स्किन सेवा को छूता है, तो उत्तर एक बंद टिकट और कोई सबूत दिखाए बिना स्थायी लॉक होता है; जब सेवा यही होती है, तो एक Valve कर्मचारी मॉडरेटर सूची में होता है और यह व्यवस्था Valve पर प्रकाशित एक पृष्ठ पर दिखाई देती है। मांगा वही है जो इस दस्तावेज़ में हर जगह मांगा गया है: यदि कोई लिखित प्राधिकरण मौजूद है तो उसे प्रस्तुत करें — और यदि किसी की आवश्यकता नहीं है, तो उसे लिखित रूप में बताएं, क्योंकि धारा 06 के आठ लोगों को इसके विपरीत बताया गया था।\n\nप्रतिबंध-सूची परत, और इसे कौन प्रशासित करता है स्वयंसेवी मॉडरेटरतृतीय-पक्ष सेवा\n\nSteambans.com का समूह (संग्रहीत) ↗ (लाइव ↗ संग्रहीत 2025-12-03 ↗) अपने संरक्षित समूह विवरण में अपनी वंशावली दर्ज करता है: Steambans.comSteam का आधिकारिक समुदाय समूह। SteamBans.com एक पुराने विचार पर आधारित एक बिल्कुल नई सेवा है। वैश्विक प्रतिबंध सूचियाँ वर्षों से VALVe के पुराने WONID प्रोग्राम पर सक्रिय रही हैं। जब STEAMID में बदलाव आया, तो हमारे लिए इस नई प्रणाली के लिए विशेष रूप से एक सेवा विकसित करना स्वाभाविक था। लेकिन हम और भी चाहते थे। *. Steambans के लिए आर्काइव पेज, जो 2013. में बंद हो गया। इसकी सूचीबद्ध प्रशासकों में शामिल हैं डिवाइसनल और किलाहइंस्टिंक्ट_ ↗.\n\nवह प्रशासक खाता है नहीं Valve का एक कर्मचारी — इसमें कोई कर्मचारी ध्वज नहीं होता। यह असाधारण रूप से गहरी स्थिति वाला एक स्वयंसेवक है: एक सदस्य सामुदायिक मॉडरेटर (414 के सदस्य, जिन्हें एक समूह के रूप में वर्णित किया गया है) Steam के सामुदायिक मॉडरेटर द्वारा निर्मित), का विकी समन्वयक, का Steam सामुदायिक बाज़ार, और Valve कार्यक्रम और प्री-रिलीज़ समूहों सहित Valve Pipeline, Steam क्लाइंट बीटा, मोबाइल ऑथ बीटा, नया Steam समुदाय बीटा, Steam प्रयोगशालाएँ, स्टीमवर्क्स और ScamURLs रिपोर्ट करें. SteamID64 76561197960794555.\n\nउस वृत्त के भीतर भी और अपने सार्वजनिक समूह रोस्टर में सीधे स्टीमबैंस प्रदर्शित करते हुए: एमएस आर्ट ↗ (समूह सूची ↗), SteamID64 76561197977933359, जिसकी प्रोफ़ाइल में अपने शब्दों में कहा गया है मैं steamid.uk और कई अन्य स्टीम और गैर-स्टीम संबंधित साइटें चलाता हूँ।, और जो सोलह समूहों के एक जुड़े हुए नेटवर्क का संचालन करता है — SteamIDcouk (प्राथमिक समूह \"सिड वेबसाइट\"), साइडएडमिन, साइडबैन, स्टीमाइड्यू, स्टीम3आईडी, एस-आईडी और एसआर्काइव उनमें से\n\nsteamid.uk इसी संख्या को स्वयं नाम देता है। इसका FAQ: SteamID का निर्माण किसने किया? SteamID वेबसाइट, नेटवर्क अवसंरचना और सुरक्षा प्रणालियाँ सभी 76561197977933359. द्वारा प्रबंधित की जाती हैं। नीचे दो उत्तरों में यह बताया गया है कि डेटा कहाँ से आता है: Steam SteamID मुख्य रूप से डेटा संग्रह के लिए SteamID वेब API का उपयोग करता है। उसी पृष्ठ में विभिन्न होस्ट्स पर कई समर्पित सर्वर, ऑफ-साइट विकास, भंडारण और टेक्स्ट-खोज सर्वर, तथा एक अलग बैकअप सुविधा का वर्णन किया गया है।\n\nसंरक्षित इंटरनेट आर्काइव रिकॉर्ड्स के माध्यम से सत्यापित: 3 का Steambans समूह स्नैपशॉट, दिसंबर 2025 ↗, का 14 का ऑपरेटर प्रोफ़ाइल स्नैपशॉट, सितम्बर 2024 ↗, और steamid.uk 1 का अक्सर पूछे जाने वाले प्रश्न (FAQ) स्नैपशॉट अप्रैल 2026 ↗, सीधे पढ़े गए डेटा से मेल खाने वाला 2026-09-22.\n\nइसका सार क्या है, और इसका क्या नहीं है।\n\nबैन सूचियाँ, SteamID समाधान और कार्ड ट्रेडिंग वे तीन सेवाएँ हैं जो यह तय करती हैं कि कौन विश्वसनीय है, कौन पहचाना जा सकता है, और किसी आइटम का मूल्य क्या है। इनमें से कोई भी सेवा Valve द्वारा संचालित नहीं की जाती। प्रत्येक पर, नियंत्रण संभालने वाले लोग Valve की कक्षा के भीतर से आए थे: Valve का एक फ़्लैग किया गया कर्मचारी कार्ड सेवा के आधिकारिक समूह की मॉडरेटर सूची में; एक लंबे समय से सेवा दे रहा Valve समुदाय का मॉडरेटर, जिसे प्री-रिलीज़ प्रोग्राम तक पहुंच प्राप्त है और जो प्रतिबंध-सूची समूह का प्रबंधन करता है; एक निजी व्यक्ति द्वारा संचालित आईडी-रिज़ॉल्यूशन सेवा, जो उसी समूह का हिस्सा है। तीन सेवाएँ, तीन नियंत्रण सतहें, तीन लोग जिन्हें Valve ने पहले ही मान्यता दे रखी थी।\n\nसमूह की सदस्यता रोजगार नहीं है, और यह सब कोई आरोप नहीं है। यह शासन का एक तथ्य है, और यही कारण है कि साधारण रक्षा — वे तृतीय पक्ष हैं, हम उन्हें नियंत्रित नहीं कर सकते। — इसे स्वीकार करने के बजाय परीक्षण करना होगा। नियंत्रण में बैठे लोग 'Valve' से अपरिचित नहीं हैं।Valve यह बताने की स्थिति में है कि उसने उनसे क्या मांगा, यदि कुछ मांगा हो; कोई बाहरी व्यक्ति यह पता नहीं लगा सकता।\n\nकोई भी मायने नहीं रखता। यही निष्कर्ष है।\n\nSteam आईडी स्पेस एक निरंतर पूर्णांक श्रेणी है। इसे क्रमिक रूप से घूमकर यह रिपोर्ट करना कि कितने खाते प्रतिबंधित हैं, कितने सीमित हैं, और एक व्यापार प्रतिबंध के पीछे कितनी इन्वेंटरी है, कोई शोध कार्यक्रम नहीं है — यह एक लूप और एक API कुंजी है। Valve स्वयं वही कुंजी प्रदान करता है, at steamcommunity.com/dev/apikey. और फिर भी कोई स्वतंत्र पक्ष उस जनगणना को प्रकाशित नहीं करता। न तो कोई नियामक, न कोई पत्रकार, न कोई शिक्षाविद, न कोई उपभोक्ता संगठन। Steam पर प्रवर्तन के पैमाने के बारे में एकमात्र सार्वजनिक आंकड़े वे हैं जिन्हें Valve उल्लेख करने का निर्णय लेता है।\n\nक्षमता गायब नहीं है। यह मौजूद है। बड़े पैमाने पर आईडी स्पेस को हल करने और अनुक्रमित करने वाली सेवा — steamid.uk — अपनी FAQ में कहती है कि यह मुख्य रूप से डेटा संग्रह के लिए Steam वेब API का उपयोग करता है। और इसे कई समर्पित सर्वरों, ऑफ-साइट स्टोरेज, टेक्स्ट-खोज मशीनों और एक अलग बैकअप सुविधा पर चलाया जाता है। इसे एक निजी व्यक्ति द्वारा संचालित किया जाता है। उसके बैन-लिस्ट संबंधी भाई-बहन समूह का सह-प्रबंधन एक लंबे समय से सेवा दे रहे Valve समुदाय के मॉडरेटर द्वारा किया जाता है, जिसे Valve के प्री-रिलीज़ प्रोग्रामों तक पहुंच प्राप्त है। वह एकमात्र पक्ष जो गणना प्रकाशित करने की स्थिति में है, Valve की कक्षा में स्थित है, और इसे प्रकाशित नहीं करता।\n\nयह वही रूप है जो दस्तावेज़ में हर जगह मिलता है। हर सेवा जो Steam अर्थव्यवस्था के बारे में कुछ भार-वाहक निर्णय लेती है — किसे भरोसेमंद माना जाता है, किसे पहचाना जा सकता है, किसी वस्तु का मूल्य क्या है, किसे प्रतिबंधित किया गया है — नाममात्र में तृतीय-पक्ष होती है और व्यावहारिक रूप से Valve के समीप होती है। Steam कार्ड एक्सचेंज उस पैटर्न का अपवाद नहीं है; यह उसका एक और उदाहरण है। यह बचाव कि ये स्वतंत्र ऑपरेटर हैं, Valve के लिए उपलब्ध है, ठीक इसलिए क्योंकि किसी ने भी कभी इसे किसी संख्या के खिलाफ परीक्षण नहीं किया है।\n\n10.88एम अकाउंट जनगणना: 88.97% अछूता\n\nValve के पूरे इंस्टॉल बेस का ऑडिट किया गया। GetPlayerBans एंडपॉइंट (10,880,610 खाते, 55 मिनट)। केवल गैर-सीमित उपसमूह ही दर्शाता है $26.8M+ न्यूनतम स्टोर खर्च में ($5.00 प्रवेश सीमा)। 9,680,599 खातों (88.97%) पर किसी भी प्रकार का प्रतिबंध नहीं है।, और 99.8% शेष केवल कॉस्मेटिक समुदाय प्रतिबंध रखते हैं जो स्वचालित ट्रेडिंग को सक्रिय रखते हैं।\n\n5,360,499गैर-सीमित ASF सदस्य (Steam द्वारा प्रदर्शित संख्या)\n10,880,610कुल API प्रविष्टियाँ स्कैन की गईं (सीमित + गैर-सीमित)\n9,680,599कभी भी प्रतिबंधित नहीं (88.97%)\n1,200,011कोई भी Steam प्रतिबंध (11.0%) — 99.8% कॉस्मेटिक\n55 मिनसम्पूर्ण जनसंख्या की जनगणना करने के लिए, एक प्रमुख\nफॉरेंसिक साक्ष्य और गहन जनगणना\n\nविस्तृत जनसांख्यिकीय विवरण — जिसमें प्रतिबंध-प्रकार वितरण चार्ट, प्रवर्तन के समय खाते की आयु, निर्माण-वर्ष समूह (2020–2026) और भौगोलिक स्व-रिपोर्टिंग शामिल हैं — समर्पित जनगणना जांच में प्रकाशित किया गया है।\n\nपूर्ण 10.88M बैन जनगणना (प्रदर्शनी VI) खोलें →अनुभाग 4 — एसेट आईडी ब्लैकआउट →\n\nValveतो सवाल यह है, और इसका उत्तर केवल ईमेल द्वारा ही दिया जा सकता है: कौन सा पहचानकर्ता या क्षमता वापस ली गई, किस तारीख को, किसके निर्णय पर, और इसका लक्षित ऑपरेटरों पर क्या मापनीय प्रभाव पड़ा। — इसे उन सभी बाहरी लोगों पर इसके प्रभाव के संदर्भ में देखें जो गिनती करने की कोशिश कर रहे थे। एक ऐसा परिवर्तन जो स्वतंत्र लेखा परीक्षा को समाप्त कर देता है, सुरक्षा उपाय के रूप में घोषित किए जाने से तटस्थ नहीं हो जाता। यही कारण है कि ऊपर दिए गए ब्लॉक में जनगणना मौजूद नहीं है।\n\n09 — विधि और सीमाएँ\nजो पढ़ा गया, और जो दावा नहीं किया गया\n\nइस पृष्ठ पर प्रत्येक उद्धरण 2026-09-22 पर उपलब्ध लाइव स्रोत से लिया गया है और शब्दशः पुनरुत्पादित किया गया है। यहाँ कुछ भी स्क्रैप, मार्केटप्लेस क्रेडेंशियल या निजी डेटासेट से नहीं लिया गया है।\n\nचार डेटासेट और उन पर की गई अंकगणित\n\nप्रत्येक एक सार्वजनिक अनुरोध है, जिसे टर्मिनल से पुनः उत्पन्न किया जा सकता है। कोई खाता उपयोग नहीं किया गया, किसी मार्केटप्लेस में लॉग इन नहीं किया गया, और कोई ऐसा एंडपॉइंट जिसे प्रमाण-पत्र की आवश्यकता हो, कॉल नहीं किया गया।\n\nडेटासेट\tयह कहाँ से आया\tउससे क्या गणना की गई\nCard census\n13,876 games\tSteam Card Exchange's published badge pricelist, the same feed that renders their public price page ↗ archived 2026-08-04 ↗\tGames issuing cards, cards per set, distinct card types, and the market price of each finished set. Medians and the $23,586.57 total are this investigation's arithmetic.\nGame prices\n13,713 resolved\tValve's own public store endpoint, store.steampowered.com/api/appdetails, cc=us, price field only, in batches\tMedian and distribution of the list price of a card-bearing game; the count of games whose finished set outsells the game itself.\nBot stock\n91 bots, 694,673 sets\tThe public card-bot directory at steam.supply/CardBots ↗, read as rendered, no login\tTotal sets in stock, the minimum card count, the drop-allowance floor, and the per-bot pigeonhole floor on distinct accounts.\nCross-check\n21 shared bots\tsteamlvlup.net/cardbots ↗ archived 2026-02-10 ↗, an independent directory of the same bots\tVerification only. On the 21 bots both list, aggregate stock agrees to 0.03%; the largest single-bot disagreement is 1.36%, consistent with two crawls of live inventory minutes apart.\n\nआवश्यकतानुसार श्रेय, जैसा कि दूसरी निर्देशिका में आवश्यक है: द्वारा प्रदान किया गया डेटा स्टीमएलवीलअप, के तहत लाइसेंस प्राप्त सीसी बाय 4.0 संग्रहित 2026-09-23 ↗; यहाँ केवल तीसरे पक्ष के स्टॉक आंकड़ों की स्वतंत्र जांच के रूप में उपयोग किया गया है, और इसे इस प्रकार संशोधित किया गया है कि प्रति-बॉट पंक्तियों को पुन: प्रस्तुत करने के बजाय समेकित और तुलना किया गया। Steam Card Exchange और steam.supply को ऊपर लिंक द्वारा श्रेय दिया गया है। गेम की कीमतें Valve की अपनी हैं। कार्ड, गेम और सेट के नाम और चित्र Valve या प्रकाशकों के हैं, जिन्हें किसी भी दावे या लाइसेंस के तहत पुनरुत्पादित नहीं किया गया है, बल्कि बाजार के तथ्यों के रूप में प्रस्तुत किया गया है।\n\nदो इच्छित माप नहीं किए गए और न ही उनका कोई विकल्प दिया गया है।Steam के अपने Community Market एंडपॉइंट्स — मूल्य अवलोकन, खोज/प्रदर्शन, मूल्यइतिहास — कलेक्टिंग होस्ट को कुछ भी वापस न करें, और Steam समुदाय चर्चा पृष्ठ HTTP 403 लौटाते हैं, इसलिए इस पृष्ठ पर कोई आंकड़ा लाइव मार्केट डेटा से प्राप्त नहीं किया गया है। बिक्री-वॉल्यूम विधि, जो दैनिक रीसेट पर कार्ड ड्रॉप्स की गिनती करती, उसके लिए एक लॉग-इन Steam सत्र आवश्यक है; इस जांच के प्रकट विवरण में कहा गया है कि किसी भी बाज़ार प्रमाणपत्र का उपयोग नहीं किया गया था, और वह कथन बरकरार रखा गया था। बॉट-स्टॉक फर्श वह है जिसे बिना किसी के मापा जा सकता है।\n\nप्राथमिक स्रोत\n\nSteam सब्सक्राइबर समझौता ↗ संचित 2026-09-24 ↗ — § 2.A, § 2.G, § 3.D, § 4.C, § 4.D.\nSteam सहायता — सीमित उपयोगकर्ता खाते ↗ — $5.00 सीमा और प्रतिबंधित-विशेषता सूची।\nValve — Steam ट्रेडिंग कार्ड्स अक्सर पूछे जाने वाले प्रश्न ↗ — ड्रॉप मैकेनिक्स और $9 का फ्री-टू-प्ले रेट।\nArchiSteamFarm अक्सर पूछे जाने वाले प्रश्न ↗ और चर्चा #3440 ↗.\nSteam सामुदायिक समूह और प्रोफ़ाइल पृष्ठ, सीधे पढ़ें, अनुभाग के लिए 08.\nsteamid.uk अक्सर पूछे जाने वाले प्रश्न, इंटरनेट आर्काइव स्नैपशॉट 2026-04-01 ↗.\nSteam समर्थन लॉक नोटिस आठ प्राप्तकर्ताओं द्वारा प्रकाशित, 2020–2026, अपने लिंक के साथ अनुभाग में सूचीबद्ध: 06.\n\nक्या दावा नहीं किया गया है\n\nValve के कार्ड फार्मिंग से होने वाली आय का कोई आंकड़ा अनुमानित नहीं है। किसी भी टूल के लिए सक्रिय खातों की संख्या का कोई दावा नहीं किया गया है, और 1.39 मिलियन ड्रॉप भत्ते हैं। नहीं कृषि-स्वामित्व वाले खातों की गिनती — अनुभाग 02. में नोट देखें। किसी व्यक्ति पर कोई गलत काम करने का आरोप नहीं है; जहाँ किसी व्यक्ति का नाम लिया गया है, वह उनके अपने सार्वजनिक Steam हैंडल से है, उनकी अपनी सार्वजनिक भूमिका में, एक ऐसे पेज से जो Valve प्रकाशित करता है। अनुभाग 06 में आठ लॉक्ड खातों में से किसी के भी निर्दोष या दोषी होने का दावा नहीं किया गया है; निष्कर्ष पत्र से संबंधित है, खाते से नहीं। खंड 02 में ऑपरेटर-हानि के आंकड़े प्रथम-पक्ष रिपोर्टिंग हैं और इन्हें उसी प्रकार लेबल किया गया है। स्रोत नोटsteamid.uk की FAQ इंटरनेट आर्काइव के स्नैपशॉट से उद्धृत की गई है क्योंकि लाइव पेज बॉट चुनौती के पीछे है। यह दावा नहीं किया गया है कि किसी भी प्रतिबंध जनगणना का प्रयास किया गया और दबा दिया गया — निष्कर्ष केवल यह है कि कोई प्रकाशित नहीं है। 667 पर Steam का लेवल वक्र मॉडल नहीं किया गया है।\n\nउपकरण विषय क्यों नहीं है\n\nArchiSteamFarm कहता है कि यह Valve द्वारा अधिकृत नहीं है। और इस पृष्ठ पर उस पर किसी भी बात का आरोप नहीं लगाया गया है। इसका उपयोग एक माप उपकरण के रूप में किया जाता है, क्योंकि यह इस अर्थव्यवस्था में एकमात्र पक्ष है जो सार्वजनिक रूप से और लिखित रूप में तंत्रों को दस्तावेज़ित करता है।Valve पूरे प्रदर्शन को एक ही पैराग्राफ में समाप्त कर सकता है: वह प्रकाशित करे कि उसने कौन-सी व्यावसायिक स्वचालन को अधिकृत किया, और शेष के संबंध में प्रत्येक ऑपरेटर का रिकॉर्ड भी प्रकाशित करे कि उसने क्या किया।\n\nअगला पढ़ें: बाज़ार की कीमत स्वयं कैसे तय होती है → · कीमत की सीढ़ी और लिस्टिंग कैप → · Steam द्वारा न बेचे जाने वाले आइटम →",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "कार्ड इकोनॉमी — थोक बिक्री, ड्रॉप सीमाएँ और स्वचालित फार्मिंग"
          },
          {
            "level": 2,
            "id": null,
            "text": "एक खेत वास्तव में क्या है, चरण-दर-चरण"
          },
          {
            "level": 3,
            "id": null,
            "text": "समर्थन करना"
          },
          {
            "level": 3,
            "id": null,
            "text": "गेम खरीदें"
          },
          {
            "level": 3,
            "id": null,
            "text": "निष्क्रिय\nयह टूल बिना ग्राफिकल इंटरफ़ेस के Steam नेटवर्क में खाते को लॉग इन करता है। आपके बैज पार्स करता है, खेती योग्य शीर्षकों और स्टार्ट्स की सूची बनाता है योग्य गेम खेलना और समय-समय पर यह जांचना कि गेम पहले से ही पूरी तरह खेती हो चुका है या नहीं। इसकी रखरखावकर्ता द्वारा तंत्र का वर्णन: यह Steam को यह बताने के अलावा और कुछ नहीं करता कि हम दिए गए खेल को खेल रहे हैं।"
          },
          {
            "level": 3,
            "id": null,
            "text": "बूँदें खत्म हो गईं\nप्रत्येक शीर्षक सीमित है। हर गेम में कार्ड ड्रॉप्स की एक निश्चित संख्या होती है। एक बार जब आप उन सभी को ड्रॉप कर लेते हैं (पूरे सेट का लगभग आधा हिस्सा), तो यह गेम फार्मिंग के लिए उपयुक्त नहीं रहता। एक फार्म जो उत्पादन जारी रखना चाहता है, उसे लगातार टाइटल्स खरीदते रहना पड़ता है। कार्ड की आपूर्ति जानबूझकर खरीदारी द्वारा सीमित की जाती है, और यहValve के पक्ष में है।"
          },
          {
            "level": 3,
            "id": null,
            "text": "नकद निकासी\nकार्ड तीन में से किसी एक दरवाजे से निकलता है: सामुदायिक बाज़ार में बेचा जाता है, किसी अन्य के साथ विनिमय किया जाता है, या रत्नों में कुचल दिया जाता है। प्रत्येक एक सदस्यता बाज़ार लेनदेन या एक व्यापार है, और §3.D शुल्क आरक्षित करता है: Valve सदस्यता मार्केटप्लेस में लेनदेन के लिए शुल्क ले सकता है। यह वह कदम है जो पूरी चीज़ को उल्लंघन बना देता है — देखें 05."
          },
          {
            "level": 2,
            "id": null,
            "text": "एक खेत एक पैसा कमाने से पहले ही, उसने पहले ही Valve का भुगतान कर दिया है।"
          },
          {
            "level": 3,
            "id": null,
            "text": "वास्तव में खरीदी जा रही वस्तु कितनी बड़ी है।"
          },
          {
            "level": 3,
            "id": null,
            "text": "यह सेट कितना बड़ा है"
          },
          {
            "level": 3,
            "id": null,
            "text": "लाइसेंस की कीमत"
          },
          {
            "level": 3,
            "id": null,
            "text": "तैयार सेट क्या लौटाता है"
          },
          {
            "level": 3,
            "id": null,
            "text": "694,673 सेट कहाँ रखे गए हैं"
          },
          {
            "level": 3,
            "id": null,
            "text": "यह मंजिल क्या कहती है और क्या नहीं कहती"
          },
          {
            "level": 3,
            "id": null,
            "text": "और Valve की कीमतों पर खेती खुद अपना खर्च नहीं उठा सकती।"
          },
          {
            "level": 3,
            "id": null,
            "text": "खेत वास्तव में क्या सहारा देता है"
          },
          {
            "level": 4,
            "id": null,
            "text": "गेम की बिक्री"
          },
          {
            "level": 4,
            "id": null,
            "text": "\"ऑनलाइन\" और खेलने का समय"
          },
          {
            "level": 4,
            "id": null,
            "text": "पंजीकरण"
          },
          {
            "level": 4,
            "id": null,
            "text": "बटुए का पैसा और शुल्क"
          },
          {
            "level": 4,
            "id": null,
            "text": "Steam-स्तरीय पीआर"
          },
          {
            "level": 3,
            "id": null,
            "text": "और कैश-आउट स्वयं एक मूल्य अवशोषक है Valve दो बार कर लगाता है"
          },
          {
            "level": 3,
            "id": null,
            "text": "यह कोई क्षण नहीं है। यह एक उद्योग है जिसकी कई वर्षों की मजबूत आधारशिला है।"
          },
          {
            "level": 3,
            "id": null,
            "text": "सार्वजनिक बॉट निर्देशिका में रखे गए पूर्ण कार्ड सेट, Steam बिक्री द्वारा"
          },
          {
            "level": 3,
            "id": null,
            "text": "एक सेल की बैज सीढ़ी ऊपर से कैसी दिखती है"
          },
          {
            "level": 3,
            "id": null,
            "text": "और जब कोई बिक्री नहीं चल रही होती है, तब भी वही बेड़ा वहीं होता है।"
          },
          {
            "level": 3,
            "id": null,
            "text": "विश्राम निर्देशिका, बॉट-दर-बॉट"
          },
          {
            "level": 2,
            "id": null,
            "text": "दूसरा उत्पाद आपके नाम के बगल में दिया गया नंबर है।"
          },
          {
            "level": 3,
            "id": null,
            "text": "पूरे सेट समाप्त, स्तर 1 से 1,000 तक"
          },
          {
            "level": 3,
            "id": null,
            "text": "वक्र की जाँच कैसे की गई, क्योंकि Valve इसे प्रकाशित नहीं करता है।"
          },
          {
            "level": 2,
            "id": null,
            "text": "यह खंड खेती का अस्पष्ट रूप से वर्णन नहीं करता है। यह इसे सूचीबद्ध करता है।"
          },
          {
            "level": 3,
            "id": null,
            "text": "…खेलने का समय"
          },
          {
            "level": 3,
            "id": null,
            "text": "…वास्तविक उपयोगकर्ता इनपुट के बिना"
          },
          {
            "level": 2,
            "id": null,
            "text": "किसान द्वारा तैयार किए गए कार्ड से हर निकास उस निकास के समान है जिसे लाइसेंस मना करता है — और Valve दरवाजे पर शुल्क वसूलता है।"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 2.A — लाइसेंस"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 2.G — प्रतिबंध"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 3.D — शुल्क"
          },
          {
            "level": 3,
            "id": null,
            "text": "तीनों को एक साथ पढ़ें और स्थिति बंद हो जाती है।"
          },
          {
            "level": 3,
            "id": "fee-ladder",
            "text": "उस दरवाजे पर शुल्क 15%. नहीं है। एक फार्म्ड कार्ड पर यह दो-तिहाई तक पहुँच जाता है।"
          },
          {
            "level": 3,
            "id": null,
            "text": "समुदायिक बाज़ार बिक्री पर प्रभावी शुल्क, विक्रेता की माँग मूल्य के अनुसार"
          },
          {
            "level": 2,
            "id": null,
            "text": "कोई सूचना नहीं, लहरों में, और यह फोन नंबर पर नीचे की ओर यात्रा करता है।"
          },
          {
            "level": 3,
            "id": null,
            "text": "4 का मामला — जून 2025, निष्क्रिय CS2 पर VAC प्रतिबंध"
          },
          {
            "level": 3,
            "id": null,
            "text": "एक मुख्य खाता कैसे मरता है"
          },
          {
            "level": 3,
            "id": null,
            "text": "तीन अलग-अलग एजेंटों द्वारा, पाँच साल के अंतराल पर, वही पैराग्राफ"
          },
          {
            "level": 3,
            "id": null,
            "text": "स्रोत पर नोट — ऑपरेटर-स्तरीय हानियाँ"
          },
          {
            "level": 2,
            "id": null,
            "text": "एक ही मेज के दोनों ओर"
          },
          {
            "level": 3,
            "id": null,
            "text": "एक ग्राहक, व्यापार के लिए"
          },
          {
            "level": 3,
            "id": null,
            "text": "वॉल्यूम के लिए एक स्वचालित बॉट बेड़ा"
          },
          {
            "level": 3,
            "id": null,
            "text": "इससे जो सवाल बचता है, वह सीधे शब्दों में यह है।"
          },
          {
            "level": 2,
            "id": null,
            "text": "कार्ड अर्थव्यवस्था का संचालन कौन करता है"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve का एक कर्मचारी सबसे बड़े कार्ड-ट्रेडिंग समूह का संचालन करता है। Valve कर्मचारी"
          },
          {
            "level": 3,
            "id": null,
            "text": "प्रतिबंध-सूची परत, और इसे कौन प्रशासित करता है स्वयंसेवी मॉडरेटर तृतीय-पक्ष सेवा"
          },
          {
            "level": 3,
            "id": null,
            "text": "इसका सार क्या है, और इसका क्या नहीं है।"
          },
          {
            "level": 3,
            "id": null,
            "text": "कोई भी मायने नहीं रखता। यही निष्कर्ष है।"
          },
          {
            "level": 3,
            "id": null,
            "text": "10.88एम अकाउंट जनगणना: 88.97% अछूता"
          },
          {
            "level": 3,
            "id": null,
            "text": "फॉरेंसिक साक्ष्य और गहन जनगणना"
          },
          {
            "level": 2,
            "id": null,
            "text": "जो पढ़ा गया, और जो दावा नहीं किया गया"
          },
          {
            "level": 3,
            "id": null,
            "text": "चार डेटासेट और उन पर की गई अंकगणित"
          },
          {
            "level": 3,
            "id": null,
            "text": "प्राथमिक स्रोत"
          },
          {
            "level": 3,
            "id": null,
            "text": "क्या दावा नहीं किया गया है"
          },
          {
            "level": 3,
            "id": null,
            "text": "उपकरण विषय क्यों नहीं है"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/hi/#briefing-heading",
          "https://help.steampowered.com/en/faqs/view/71D3-35C2-AD96-AA3A",
          "https://github.com/JustArchiNET/ArchiSteamFarm/wiki/FAQ",
          "https://steamcommunity.com/tradingcards/faq/",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260924114457/https://store.steampowered.com/subscriber_agreement/",
          "https://steamladder.com/ladder/badges/2861690/",
          "http://web.archive.org/web/20260716205303/https://steamladder.com/ladder/badges/2861690/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/farm-economy-timeline.json",
          "https://store.steampowered.com/charts/",
          "http://web.archive.org/web/20260923183013/https://store.steampowered.com/charts/",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://github.com/JustArchiNET/ArchiSteamFarm/discussions/3440",
          "https://x.com/gergelyszabo94/status/1311004678633795585",
          "https://x.com/prcs25/status/1811893857253982720",
          "http://web.archive.org/web/20240715122902/https://x.com/prcs25/status/1811893857253982720",
          "https://reddit.com/r/steamsupport/comments/1fjmgc5/what_to_do_when_your_steam_account_gets_hacked/mkelm2y/",
          "https://www.reddit.com/r/csgomarketforum/comments/r87owv/psa_my_steam_account_just_got_banned/",
          "http://web.archive.org/web/20250327203008/https://www.reddit.com/r/csgomarketforum/comments/r87owv/psa_my_steam_account_just_got_banned/",
          "https://www.reddit.com/r/GlobalOffensiveTrade/comments/r9xql9/d_recently_received_commercial_ban_for_what_seems/",
          "http://web.archive.org/web/20211206034804/https://www.reddit.com/r/GlobalOffensiveTrade/comments/r9xql9/d_recently_received_commercial_ban_for_what_seems/",
          "https://www.reddit.com/r/csgomarketforum/comments/1hhxx7m/d_permanently_locked_on_steam_for_commercial_use/",
          "http://web.archive.org/web/20250627014045/https://www.reddit.com/r/csgomarketforum/comments/1hhxx7m/d_permanently_locked_on_steam_for_commercial_use/",
          "https://www.reddit.com/r/steamsupport/comments/1hkctwt/permanent_ban_with_no_explanation/",
          "https://www.reddit.com/r/pcgaming/comments/1vf24lu/warning_to_all_gamersexpats_steam_took_my_money/",
          "https://steamcommunity.com/groups/card-trading-card-trades",
          "https://steamcommunity.com/id/afarnsworth",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/groups/steambans",
          "https://steamcommunity.com/groups/steambans",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/id/killahinstinct_",
          "https://web.archive.org/web/20240914124859/https://steamcommunity.com/id/msart",
          "https://steamcommunity.com/id/msart/groups/",
          "http://web.archive.org/web/20260401154714/https://steamid.uk/faq/",
          "https://phishdestroy.io/steam_dossier/hi/enforcement_audit.html",
          "https://phishdestroy.io/steam_dossier/hi/#evidence-blackout",
          "https://www.steamcardexchange.net/index.php?badgeprices",
          "http://web.archive.org/web/20260804200309/https://www.steamcardexchange.net/index.php?badgeprices",
          "https://steam.supply/CardBots",
          "https://steamlvlup.net/cardbots",
          "http://web.archive.org/web/20260210171205/https://steamlvlup.net/cardbots",
          "https://steamlvlup.net/",
          "https://creativecommons.org/licenses/by/4.0/",
          "http://web.archive.org/web/20260923221628/https://creativecommons.org/licenses/by/4.0/",
          "https://phishdestroy.io/steam_dossier/hi/market_economics.html",
          "https://phishdestroy.io/steam_dossier/hi/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/hi/elite_skins.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/hi/card_economy.content.json",
      "export_json_sha256": "3141b38d565271aa290c06c6a0f84588e024b7be544cca583eb3b91ca7ac1b4e"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "hi/elite_skins.html",
      "language": "hi",
      "title": "एक वस्तु, दो मूल्य प्रणाली — द Steam डॉसियर",
      "source_url": "https://phishdestroy.io/steam_dossier/hi/elite_skins",
      "source_html_sha256": "b620307a747ef814e2340785fd5fd2108a047dc58106643a1eece02d63d1f1f7",
      "exported_at": "2026-09-29T00:22:42.546Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "register",
            "source": "https://phishdestroy.io/steam_dossier/hi/elite_skins#register"
          },
          {
            "id": "",
            "source": "https://phishdestroy.io/steam_dossier/hi/elite_skins#selected"
          }
        ],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "elite_skins.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/hi/elite_skins.pdf?v=print-20260929-v5",
        "sha256": "5a7ce404e0058835acc6199bfbe2fc7aa6bc1c47a38e8a70c4e1e241b7b960e4",
        "bytes": 380680,
        "pages": 6
      },
      "integrity": {
        "signed_object": "elite_skins.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "elite_skins.content.json.asc",
        "digest_file": "elite_skins.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify elite_skins.content.json.asc elite_skins.content.json",
          "sha256sum -c elite_skins.content.json.sha256"
        ]
      },
      "content": {
        "text": "प्रदर्शनी IV / बाज़ार संरचना / 20 सितंबर 2026\nएलिट स्किन्स रजिस्टर — $1,800 का मार्केट सीलिंग\n\nएक आइटम। दो मूल्य प्रणालियाँ।\n\nयह अनुभाग क्या प्रमाणित करता है\n\nयह रजिस्टर पाँच बाहरी एक्सचेंजों पर Steam की $1,800 कम्युनिटी मार्केट लिस्टिंग कैप से ऊपर मूल्य वाली सभी CS2 स्किन श्रेणियों का एक अनुभवजन्य जनगणना स्थापित करता है। यह साबित करता है कि 248 द्वारा सत्यापित उच्च-स्तरीय श्रेणियाँ—जो 18,394 की सक्रिय लिस्टिंग और $78.6 मिलियन की पोस्ट की गई तरलता का प्रतिनिधित्व करती हैं—100% Valve के आधिकारिक मार्केटप्लेस में अनुपस्थित हैं। वास्तविक बाजार मूल्य चाहने वाले विक्रेता संरचनात्मक रूप से बाहरी प्लेटफ़ॉर्मों पर जाने के लिए मजबूर हैं, जबकि वे पूरी तरह से Steam की अंतर्निहित व्यापार यांत्रिकी पर निर्भर रहते हैं।\n\nWhat this means — the Community Market listing ceiling\n\nSteam’s own market refuses a listing above roughly $1,800. A seller may ask less, never more. Items whose market price sits above that line therefore cannot be sold at that price on Steam at all — which is the mechanism that moves those sales to third-party venues while the item itself never leaves Valve’s inventory system.\n\nSection 13 — the off-Steam price gap →\n\n← कार्यकारी ब्रीफिंग पर वापस\n\nSteam एक कम्युनिटी मार्केट लिस्टिंग लगभग $1,800. पर सीमित है। इस स्नैपशॉट में मूल्य निर्धारण किए गए पाँच थर्ड-पार्टी मार्केटप्लेस में, 419 402 CS2 आइटम श्रेणियों में उस सीमा से ऊपर सबसे सस्ता लाइव पूछ मूल्य होता है — और उनमें से कुछ, जैसे , के पास कोई लिस्टिंग ही नहीं है। 95.9%, Steam वे मिलकर कम से कम $82.4 मिलियन मूल्य के सूचीबद्ध प्रतिलिपि18,641s रखे हुए हैं। किसी कीमत को मान्य होने से पहले दूसरे बाज़ार की सहमति आवश्यक है। 248 उन श्रेणियों में से पुष्टि की गई हैं — और उनमें से प्रत्येक, 100%,, Steam से अनुपस्थित है। सबसे महंगा एक स्टिकर है | टाइटन (होलो) | कटोविसे 2014 पर $66,285, चार मार्केटप्लेस द्वारा एक-दूसरे से 5.2% के भीतर उद्धृत और Valve में से किसी द्वारा भी नहीं लिया गया। पूरी सीढ़ी, रेंडर और ग्रेडिंग इसमें हैं। मूल्य-सीढ़ी एटलस.\n\nसभी 419 प्रविष्टियों का निरीक्षण करें ↓एटलस खोलें ↗विधि पढ़ें\n248श्रेणियाँ दो या अधिक बाज़ारों की कीमत कैप से ऊपर\n18,394पाँच मार्केटप्लेस पर सूचीबद्ध प्रतियाँ\n$78.6Mउन लिस्टिंगों का न्यूनतम मूल्य\n100%उनमें से पूरी तरह से Steam से अनुपस्थित\n\nसुधार · यह पृष्ठ पहले एक अप्रमाणित मूल्य के साथ शुरू होता था\n\nइस पृष्ठ का एक पूर्व संस्करण 'Souvenir AK-47' शीर्षक के साथ था | Point Disarray ने एक मार्केटप्लेस पर $148,954 में पूछा जबकि Steam ने इसे $119. में मूल्यित किया। वह पंक्ति एक ही शेल्फ और एक ही प्रति पर आधारित है, कोई दूसरा मार्केटप्लेस सहमत नहीं है, इसलिए यह कीमत नहीं बल्कि पूछी गई कीमत है, और अब यह पृष्ठ पर नहीं दिखती। यहाँ प्रत्येक प्रमुख आंकड़ा अब उन 248 श्रेणियों तक सीमित है, जिनकी कम से कम दो बाज़ार स्वतंत्र रूप से सीमा से ऊपर कीमत निर्धारित करते हैं। इस पंक्ति को स्वयं हटाया नहीं गया है — यह अभी भी नीचे रजिस्टर में है, और जिस ग्रेडिंग ने इसे नीचे उतारा है, वह पूरी तरह से में दी गई है। मूल्य-सीढ़ी एटलस.\n\n01 / सक्रिय अनुरोधों में धन\nमापनीय डॉलर तल\n\nपाँच मार्केटप्लेस में लाइसेंस प्राप्त cs2.sh के स्नैपशॉट से पुनः गणना की गई। यह एक परिभाषित उपसमूह में न्यूनतम समग्र अनुरोधित मूल्य है, बिक्री टर्नओवर नहीं और CS2 अर्थव्यवस्था का मूल्यांकन नहीं।\n\n248 प्रमाणित श्रेणियाँ · 18,394 सूचीबद्ध प्रतियाँ · 5 बाज़ार$78.62M\n\nहर CS2 आइटम के लिए न्यूनतम कुल पोस्ट की गई पूछी गई कीमत, जब दो या अधिक बाज़ार स्वतंत्र रूप से उस सीमा से ऊपर कीमत निर्धारित करते हैं, जो Valve अपने स्वयं के बाज़ार पर अनुमति देता है।\n\nयह एक अनुमान नहीं, बल्कि एक न्यूनतम सीमा क्यों है\n\nप्रत्येक बाज़ार के लिए हम इसका गुणा करते हैं। सबसे कम मार्केटप्लेस द्वारा सूचीबद्ध प्रतियों की संख्या के आधार पर किसी वस्तु का अनुरोध करें। उस शेल्फ पर मौजूद हर दूसरी प्रति की कीमत सबसे कम अनुरोध मूल्य के बराबर या उससे अधिक होती है, इसलिए वास्तविक प्रदर्शित मूल्य अधिक होता है — यह संरचनात्मक है, अनुमान पर आधारित नहीं। यह कोई बिक्री, नकदी प्रवाह या पूरे बाजार का मूल्यांकन नहीं है, और एक ही भौतिक वस्तु एक से अधिक मार्केटप्लेस पर दिखाई दे सकती है।\n\nसभी 419 स्रोत पंक्तियाँ जाँचें ↗\n★ स्पोर्ट दस्ताने | हेज मेज़ (मैदान में परखा हुआ)\n$4.68M\nAWP | गुंगनिर (नया)\n$4.46M\nAWP | ड्रैगन लोअर (नया)\n$4.34M\n★ बटरफ्लाई चाकू | फेड (कारखाना नया)\n$4.17M\nएके-47 | वाइल्ड लोटस (फ़ैक्टरी न्यू)\n$4.16M\n★ बटरफ्लाई चाकू | डॉप्लर (फ़ैक्टरी नया)\n$3.64M\n\nबार फ़्लोर गणना में श्रेणी-स्तर के छह सबसे बड़े योगदानों को दर्शाते हैं, जिन्हें सबसे बड़े के सापेक्ष मापा गया है। एक ऊँचा बार सबसे सस्ती पूछी गई कीमत और सूचीबद्ध प्रतियों की संख्या दोनों को दर्शाता है। एक ही भौतिक वस्तु एक से अधिक बाज़ारों में दिखाई दे सकती है, इसलिए इन आंकड़ों को किसी अन्य बाज़ार के कुल में नहीं जोड़ा जाना चाहिए।\n\n02 / निरीक्षण योग्य उदाहरण\nसीमा जो बाहर छोड़ देती है\n\nचित्र उपलब्ध होने पर वस्तुओं के सटीक नामों से मेल खाते हैं। कीमतें दिनांकित कैटलॉग से ली गई सक्रिय माँग मूल्य हैं, लेन-देन के रिकॉर्ड नहीं।\n\n★ Butterfly Knife | Doppler (Factory New)\n\nस्रोत: https://phishdestroy.io/steam_dossier/hi/elite_skins#selected\n\nमापा जा सकने वाला अंतर: इन ऑफ़र्स की तुलना उसी USD राशि पर किसी 'Steam' लिस्टिंग से नहीं की जा सकती। Valve की अपनी सामुदायिक बाज़ार अक्सर पूछे जाने वाले प्रश्न संचित 2026-09-21 ↗ लगभग $1,800 की अधिकतम लिस्टिंग कीमत बताई गई है। विक्रेता फिर भी इससे कम कीमत पर लिस्ट कर सकता है; यह स्वीकार्य होगा या नहीं, यह विक्रेता की पसंद है। एक अलग CSMarketCap $1,800 से अधिक मूल्य वाली वस्तुओं की खोज ↗ 28-सूचीबद्ध बाज़ारों में फैक्ट्री न्यू ड्रैगन लोअर दिखाता है, जिसमें लगभग 1.1K प्रदर्शित ऑफ़र हैं; प्रतिबिंबित इन्वेंटरी को एक से अधिक बार गिना जा सकता है।\n\n03 / संरचनात्मक निर्भरता\nSteam की कैप कीमत की खोज को Steam के बाहर भेजती है।\n\nयह तुलना संरचनात्मक है। यह न तो यह मानता है कि हर मांगी गई कीमत उचित है, और न ही अनविक्रित लिस्टिंग को राजस्व के रूप में मानता है।\n\n01 · नियम\nSteam सूची को समाप्त करता है\n\nValve कहते हैं कि कम्युनिटी मार्केट लिस्टिंग्स लगभग पर सीमित हैं $1,800वॉलेट बैलेंस पर भी सीमा होती है, और वॉलेट की धनराशि नकद के रूप में नहीं निकाली जा सकती।\n\n02 · अवलोकन\nड्रैगन लॉर: $10,940.85\n\n5-मार्केटप्लेस कैटलॉग दिखाता है 389 लाइव ऑफ़र्स AWP Dragon Lore (Factory New) के लिए, जिसकी कीमत $10,940.85 से शुरू होती है (CSFloat फर्श)। व्यापक रजिस्टर में 248 द्वारा सत्यापित श्रेणियाँ शामिल हैं जो Steam की सीमा से ऊपर हैं।\n\n03 · परिणाम\nकीमत और हस्तांतरण विभाजन\n\nएक विक्रेता जो ऊँची कीमत चाहता है इसे Steam पर पोस्ट नहीं कर सकते।Steamबाहरी सेवाएँ नकद मूल्य निर्धारित कर सकती हैं, लेकिन डिलीवरी अभी भी ई-कॉमर्स-नियंत्रित वस्तु स्वामित्व और हस्तांतरण का उपयोग करती है।\n\nनीतिगत विरोधाभास: Valve का अपना सदस्यता अनुबंध संचित 2026-09-21 ↗ Steam सेवाओं के वाणिज्यिक शोषण को स्पष्ट रूप से अनुमत किए बिना आरक्षित करता है, जबकि इसकी 2016 बयान संचित 2026-09-21 ↗ कहा गया कि जुआ संचालक पहले से ही Steam OpenID और स्वचालित खातों का उपयोग कर रहे थे। यह सीधा प्रमाण है कि Valve को 2016. में इस बाहरी संचालक वर्ग के बारे में पता था। फिर भी आधिकारिक बाज़ार इन उच्च-मूल्य वस्तुओं के देखे गए दामों को प्रकाशित नहीं कर सकता। यह ऑफ-Steam मूल्य खोज और लेनदेन पर वास्तुशिल्पीय निर्भरता है; प्रत्येक व्यक्तिगत मार्केटप्लेस की अनुबंध स्थिति के लिए अलग-अलग प्रमाण आवश्यक हैं। इस ओवर-कैप लेनदेन मात्रा को संभालने वाले दो प्रमुख पश्चिमी मार्केटप्लेस प्रमुख अधिकारक्षेत्रों में औपचारिक कॉर्पोरेट संस्थाओं के रूप में कार्य करते हैं — CSFloat इंकॉर्पोरेटेड (यूएसए के डेलावेयर में निगमित) और Skinport जीएमबीएच (स्टटगार्ट, जर्मनी में पंजीकृत, HRB 764879) — Steam वेब एपीआई और व्यापार अवसंरचना पर सीधे निर्भर करते हुए, खुले तौर पर पीयर-टू-पीयर वस्तु बिक्री में सैकड़ों मिलियन का लेन-देन करता है।\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\nचार $100,000 पंक्तियाँ CSFloat की अपनी अधिकतम लिस्टिंग कीमत पर हैं। इन्हें रजिस्टर में चिह्नित किया गया है और इन्हें मूल्यांकन के रूप में नहीं पढ़ा जाना चाहिए। संग्रहीत CSFloat लिस्टिंग क्रॉल केवल लगभग $6,999, तक पहुँच पाई, इसलिए पूरे >$1,800 रजिस्टर के लिए सार्वजनिक कैटलॉग स्नैपशॉट का उपयोग किया गया है।\n\n04 / एक और Valve गेम\nछत भी Dota 2 को पकड़ती है।\n\nSkinport पर वही सख्त सबसे सस्ती पेशकश परीक्षण 166, CS2 श्रेणियाँ और 3 Dota 2 श्रेणियाँ दिखाता है। ये एक अलग मार्केटप्लेस स्नैपशॉट हैं; इन्हें CSFloat के 245. में शामिल न करें।\n\nडोटा 2 · 1 ऑफर\nवीरात्मक क्रूर अर्धचंद्र\n\nसबसे सस्ता Skinport पूछें: $14,622.25.\n\nडोटा 2 · 1 ऑफर\nडार्क आर्टिस्ट्री केप\n\nसबसे सस्ता Skinport पूछें: $8,255.16.\n\nडोटा 2 · 1 ऑफर\nभ्रष्ट शक्तिशाली तारा\n\nसबसे सस्ता Skinport पूछें: $2,087.92.\n\nये तीन सूचीबद्ध आइटम श्रेणियाँ हैं, न कि मौजूद हर Dota 2 आइटम। दिनांकित Skinport की पंक्तियों का निरीक्षण करें ↗ और API दस्तावेज़ीकरण ↗.\n\n05 मजबूती\nयह निष्कर्ष सटीक टोपी पर निर्भर नहीं करता।\n\nValve यह खरीदार की क्षेत्रीय मुद्रा में सीमा निर्धारित करता है, इसलिए USD में परिवर्तित करने पर यह किसी एक स्पष्ट आंकड़े पर नहीं आता। इसलिए जनगणना प्रत्येक संभावित सीमा पर दोहराई जाती है। इन वस्तुओं का हिस्सा जो Steam से अनुपस्थित हैं, कभी भी 95%. से नीचे नहीं आता।\n\nपरीक्षण सीमा\tआइटम श्रेणियाँ\tलिस्ट की गई प्रतियाँ\tतल मूल्य\tSteam से अनुपस्थित\n$1,800\t419\t18,641\t$82,449,526\t95.9%\n$2,000\t382\t15,159\t$75,541,325\t95.5%\n$2,070\t363\t12,336\t$69,560,305\t95.6%\n$2,300\t323\t11,644\t$67,984,432\t95.0%\n$2,500\t299\t10,950\t$66,203,929\t95.0%\n\nएक बार में एक पंक्ति पढ़ें; पंक्तियाँ एक ही जनगणना के घोंसले उपसमूह हैं, अलग आबादी नहीं। \"फ्लोर वैल्यू\" प्रत्येक मार्केटप्लेस के सबसे कम यह सूचीबद्ध प्रतियों की संख्या के आधार पर पूछता है, इसलिए यह संरचनात्मक रूप से शेल्फ को कम आंकता है। डेटासेट खोलें ↗\n\n06 / कमी जिसे आप गिन सकते हैं\nइनमें से वास्तव में कितने बिक्री के लिए उपलब्ध हैं।\n\nBUFF प्रत्येक आइटम की शेल्फ को फ्लोट ब्रैकेट्स में विभाजित करता है और प्रकाशित करता है कि प्रत्येक में कितनी प्रतियाँ रखी गई हैं। इससे \"रेयर\" शब्द एक गिनती बन जाता है — और स्थिति की कीमत स्किन से अलग तय की जाती है।\n\n298 प्रतिलिपियाँ सूचीबद्ध\nएडब्ल्यूपी | ड्रैगन लोअर\n\n8 अलग-अलग वेरिएंट्स की कीमतें। सबसे महँगा, स्मारिका AWP | ड्रैगन लोअर (कारखाना नया), पूछता है $12,363 शेल्फ पर 20 प्रतियाँ।\n\nशेल्फ पर उपलब्ध सर्वश्रेष्ठ फ्लोट ब्रैकेट (0–0.01) में हैं 2 प्रतिलिपियाँ, पूछते हुए $17,875 — केवल स्थिति के लिए आइटम की मूल पूछी गई कीमत पर एक +45% प्रीमियम।\n\n607 प्रतिलिपियाँ सूचीबद्ध\nएम4ए4 | भौंकना\n\n12 अलग-अलग वेरिएंट्स की कीमतें। सबसे महँगा, सौविनियर M4A4 | हॉल (फ़ैक्टरी न्यू), पूछता है $14,895 शेल्फ पर 2 प्रतियाँ।\n\n213 प्रतिलिपियाँ सूचीबद्ध\nएके-47 | वाइल्ड लोटस\n\n7 अलग-अलग वेरिएंट्स की कीमतें। सबसे महँगा, स्मृति चिन्ह AK-47 | वाइल्ड लोटस (फ़ैक्टरी न्यू), पूछता है $14,895 शेल्फ पर 2 प्रतियाँ।\n\n310 प्रतिलिपियाँ सूचीबद्ध\nएडब्ल्यूपी | गुंगनिर\n\n7 अलग-अलग वेरिएंट्स की कीमतें। सबसे महँगा, सौवेनियर AWP | गुंगनिर (न्यूनतम घिसाव), पूछता है $14,895 शेल्फ पर 2 प्रतियाँ।\n\nयह शेष दस्तावेज़ के लिए क्यों महत्वपूर्ण है: ये कोई अमूर्त अवधारणाएँ नहीं हैं। प्रत्येक ट्रॉफी की कुछ सौ प्रतियाँ दुनिया भर में खुले शेल्फ पर मौजूद हैं, प्रत्येक एक Steam खाते से जुड़ी हुई और एक Steam व्यापार द्वारा स्थानांतरित की गई। इतना संकीर्ण बाजार वह है जहाँ एक चोरी की गई इन्वेंटरी एक मापनीय घटना होती है, और जहाँ इस जांच में अन्यत्र दस्तावेजीकृत खाते-कब्जा करने की तकनीकों का सीधा और मात्रात्मक लाभ होता है।\n\nकाउंट्स कैप्चर समय पर एक मार्केटप्लेस पर लाइव लिस्टिंग हैं, न कि अस्तित्व में मौजूद कुल संख्या। निजी इन्वेंटरी में रखी गई प्रतियाँ यहाँ कहीं भी गिनती में शामिल नहीं हैं। फ़्लोट डेटासेट खोलें ↗\n\n07 / सीढ़ी दृष्टि से ओझल\nवस्तु जितनी महँगी होगी, वह किसी भी दिखाई देने वाले स्थान से उतनी ही दूर होगी।\n\nनीचे प्रत्येक सीढ़ी एक अलग साक्ष्य वर्ग है। इन्हें जानबूझकर एक ही संख्या में नहीं मिलाया गया है।\n\nसीढ़ी\tआकृति\tयह किस प्रकार का तथ्य है\nCeiling on Valve's own market\t~$1,800\tPublished rule, stated in the Steam Community Market FAQ.\nDearest ask several marketplaces agree on\t$66,285\tMeasured by us in this snapshot. Sticker | Titan (Holo) | Katowice 2014, quoted by four marketplaces within 5.2% of one another. An ask, not a sale.\nDearest ask seen on any single shelf\t$148,954\tOne marketplace, one copy, no second marketplace agreeing — and equal to a round CNY 1,000,000 at the snapshot rate. Listed here as the outer edge of what sellers ask, and relied on for nothing.\nPublic marketplace sale\t$49,999\tSpecialist Gloves | Crimson Kimono (FN) on CSFloat, as reported by SteamAnalyst. Platform-recorded, third-party reported.\nReported private sale\t$400,000\tAK-47 | Case Hardened, reported by PC Gamer in April 2023. Journalism, not a record we hold.\nReported offer, declined\t$1,500,000\tBlue Gem Karambit, pattern #387. No sale took place and the figure has not been independently confirmed. Included to mark the ceiling of the claims, not to assert a value.\n\nसंरचनात्मक बिंदु: Valve का बाज़ार लगभग $1,800. पर रुक जाता है। तीसरे पक्ष के बाज़ार इस व्यापार को लगभग $66,000 तक ले जाते हैं, जहाँ कई सहमत होते हैं, और लगभग $150,000 तक, जहाँ केवल एक सहमत होता है। उससे ऊपर कोई मंच ही नहीं है — Valveद्वारा जारी संपत्ति के सबसे बड़े हस्तांतरण निजी तौर पर, व्यक्तियों के बीच, बिना किसी लिस्टिंग, बिना किसी प्लेटफ़ॉर्म रिकॉर्ड, बिना किसी पहचान जांच और बिना किसी रिपोर्टिंग के होते हैं। हस्तांतरण स्वयं अभी भी Steam पर चलता है। जितना अधिक मूल्य होगा, उतना ही कम कोई इसे देख पाएगा, और इसे वहन करने वाला बुनियादी ढांचा पूरे रास्ते 'Valve' का ही है।\n\nअंतिम दो सीढ़ियाँ अन्य लोगों की रिपोर्टिंग हैं, जिन्हें ऐसे ही उद्धृत किया गया है। इस परियोजना ने इन्हें सत्यापित नहीं किया और किसी भी निष्कर्ष के लिए इन पर निर्भर नहीं करती।\n\n419 द्वारा अवलोकित सभी श्रेणियाँ\n\nस्रोत: https://phishdestroy.io/steam_dossier/hi/elite_skins#register\n\n09 / उत्पत्ति और सीमाएँ\nगणना की जाँच करें\n\nहम स्थानीय डेटा और सार्वजनिक स्रोत को प्रकट करते हैं। संख्यात्मक शीर्षक को कैप्चर की तारीख पर CSFloat तक सीमित किया गया है।\n\nValve की अपनी सीमाएँ और शर्तें\n\nSteam सामुदायिक बाज़ार अक्सर पूछे जाने वाले प्रश्न ↗ संचित 2026-09-21 ↗ लगभग $1,800 की अधिकतम लिस्टिंग बताता है। सब्सक्राइबर अनुबंध ↗ संचित 2026-09-21 ↗ व्यावसायिक उपयोग पर प्रतिबंध निर्धारित करता है।\n\nकीमतें कहाँ से आती हैं\n\nकीमतें, लिस्टिंग की संख्या और फ्लोट ब्रैकेट्स से लिए गए हैं। cs2.sh API के मार्केट डेटा को एक लाइसेंस प्राप्त कुंजी का उपयोग करके, एक सशुल्क व्यावसायिक सदस्यता के अंतर्गत। किसी भी मार्केटप्लेस को स्क्रैप नहीं किया गया और किसी भी मार्केटप्लेस खाते या प्रमाण-पत्र का उपयोग नहीं किया गया। प्रदाता BUFF, Youpin, CSFloat, Skinport, C5Game और Steam कम्युनिटी मार्केट को एकत्रित करता है; सभी आंकड़े USD में हैं जैसा लौटाया गया है। प्रोवेंसेंस मैनिफेस्ट खोलें ↗ — यह कच्चे स्नैपशॉट्स के सटीक अंत बिंदु, कैप्चर समय और SHA-256 हैश रिकॉर्ड करता है, ताकि कोई स्वतंत्र पाठक अपनी कुंजी के साथ वही डेटा प्राप्त कर सके और इस पृष्ठ पर प्रत्येक संख्या को पुनः गणना कर सके।\n\nजो हम प्राप्त नहीं कर सके\n\nखरीदी गई सदस्यता केवल वर्तमान स्नैपशॉट्स को ही कवर करती है। ऐतिहासिक और आर्काइव एंडपॉइंट्स हमें उपलब्ध नहीं थे, और इस पृष्ठ पर किसी भी प्रवृत्ति, किसी भी पिछले मूल्य या समय के साथ किसी भी परिवर्तन के बारे में कोई दावा नहीं किया गया है। यहाँ सब कुछ एक ही क्षण है, जिसकी तारीख पुरानी हो चुकी है।\n\nपहले CSFloat पंजीकृत करें\n\nइस प्रदर्शनी के पहले संस्करण ने 20 सितंबर 2026: की तारीख वाले एक CSFloat कैटलॉग स्नैपशॉट से 245 श्रेणियों की गिनती की। वह स्नैपशॉट यहीं रहता है ↗वर्तमान रजिस्टर व्यापक है क्योंकि यह एक के बजाय पाँच बाज़ारों को कवर करता है। ये दोनों अलग-अलग कैप्चर हैं और इन्हें एक साथ नहीं जोड़ा जाना चाहिए।\n\nValve का विशिष्ट प्रवर्तन वक्तव्य\n\nValve का 2016 इन-गेम आइटम ट्रेडिंग अपडेट ↗ संचित 2026-09-21 ↗ यह OpenID और स्वचालित Steam खातों का उपयोग करने वाले जुआ संचालकों को संबोधित करता है। यह हर बाहरी बाज़ार पर प्रतिबंध लगाने से अधिक सीमित है।\n\nव्याख्या की सीमा\n\nये ऑफ़र हैं, बिक्री नहीं। एक मार्केट नाम विभिन्न फ्लोट, पैटर्न या स्टिकर विवरणों वाले कई भौतिक आइटमों को कवर कर सकता है। यह रजिस्टर कुल मार्केट मूल्य या Valve की मंशा को मापता नहीं है।",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "एलिट स्किन्स रजिस्टर — $1,800 का मार्केट सीलिंग"
          },
          {
            "level": 2,
            "id": null,
            "text": "मापनीय डॉलर तल"
          },
          {
            "level": 3,
            "id": null,
            "text": "यह एक अनुमान नहीं, बल्कि एक न्यूनतम सीमा क्यों है"
          },
          {
            "level": 2,
            "id": null,
            "text": "सीमा जो बाहर छोड़ देती है"
          },
          {
            "level": 3,
            "id": null,
            "text": "★ Butterfly Knife | Doppler (Factory New)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Steam की कैप कीमत की खोज को Steam के बाहर भेजती है।"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam सूची को समाप्त करता है"
          },
          {
            "level": 3,
            "id": null,
            "text": "ड्रैगन लॉर: $10,940.85"
          },
          {
            "level": 3,
            "id": null,
            "text": "कीमत और हस्तांतरण विभाजन"
          },
          {
            "level": 2,
            "id": null,
            "text": "छत भी Dota 2 को पकड़ती है।"
          },
          {
            "level": 3,
            "id": null,
            "text": "वीरात्मक क्रूर अर्धचंद्र"
          },
          {
            "level": 3,
            "id": null,
            "text": "डार्क आर्टिस्ट्री केप"
          },
          {
            "level": 3,
            "id": null,
            "text": "भ्रष्ट शक्तिशाली तारा"
          },
          {
            "level": 2,
            "id": null,
            "text": "यह निष्कर्ष सटीक टोपी पर निर्भर नहीं करता।"
          },
          {
            "level": 2,
            "id": null,
            "text": "इनमें से वास्तव में कितने बिक्री के लिए उपलब्ध हैं।"
          },
          {
            "level": 3,
            "id": null,
            "text": "एडब्ल्यूपी | ड्रैगन लोअर"
          },
          {
            "level": 3,
            "id": null,
            "text": "एम4ए4 | भौंकना"
          },
          {
            "level": 3,
            "id": null,
            "text": "एके-47 | वाइल्ड लोटस"
          },
          {
            "level": 3,
            "id": null,
            "text": "एडब्ल्यूपी | गुंगनिर"
          },
          {
            "level": 2,
            "id": null,
            "text": "वस्तु जितनी महँगी होगी, वह किसी भी दिखाई देने वाले स्थान से उतनी ही दूर होगी।"
          },
          {
            "level": 2,
            "id": null,
            "text": "419 द्वारा अवलोकित सभी श्रेणियाँ"
          },
          {
            "level": 2,
            "id": null,
            "text": "गणना की जाँच करें"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve की अपनी सीमाएँ और शर्तें"
          },
          {
            "level": 3,
            "id": null,
            "text": "कीमतें कहाँ से आती हैं"
          },
          {
            "level": 3,
            "id": null,
            "text": "जो हम प्राप्त नहीं कर सके"
          },
          {
            "level": 3,
            "id": null,
            "text": "पहले CSFloat पंजीकृत करें"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve का विशिष्ट प्रवर्तन वक्तव्य"
          },
          {
            "level": 3,
            "id": null,
            "text": "व्याख्या की सीमा"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/hi/#market-gap-section",
          "https://phishdestroy.io/steam_dossier/hi/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/hi/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/hi/skin_atlas.html#grading",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-above-the-ceiling.json",
          "https://phishdestroy.io/steam_dossier/hi/elite_skins#selected",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://csmarketcap.com/search?minPrice=1800&amp;page=1",
          "https://store.steampowered.com/agreement/?l=english",
          "http://web.archive.org/web/20260921022032/https://store.steampowered.com/agreement/?l=english",
          "https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921021947/https://store.steampowered.com/oldnews/22883",
          "https://phishdestroy.io/steam_dossier/hi/#proxy-bypass-explainer",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/skinport-floor-over-cap.json",
          "https://docs.skinport.com/items",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-float-scarcity.json",
          "https://phishdestroy.io/steam_dossier/hi/elite_skins#register",
          "https://cs2.sh/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/csfloat-catalogue.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/hi/elite_skins.content.json",
      "export_json_sha256": "edc61d100cda162ed1729bb1f251cd401d47067c4215d4ce9fbeeba2843b0d74"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "hi/enforcement_audit.html",
      "language": "hi",
      "title": "जनगणना Valve प्रकाशित नहीं करेगी — द Steam डोजियर",
      "source_url": "https://phishdestroy.io/steam_dossier/hi/enforcement_audit",
      "source_html_sha256": "a5dcc5d1fc6771939fdd8b3fe724c715347edb305b91a8244ab9c935627ae80b",
      "exported_at": "2026-09-29T00:23:50.453Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "enforcement_audit.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/hi/enforcement_audit.pdf?v=print-20260929-v5",
        "sha256": "cc9e86c503b834508ec9f8682d0a0f7ed456b950ae5d519992c9ed1d681943b9",
        "bytes": 405317,
        "pages": 11
      },
      "integrity": {
        "signed_object": "enforcement_audit.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "enforcement_audit.content.json.asc",
        "digest_file": "enforcement_audit.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify enforcement_audit.content.json.asc enforcement_audit.content.json",
          "sha256sum -c enforcement_audit.content.json.sha256"
        ]
      },
      "content": {
        "text": "प्रदर्शनी VI — जनगणना VALVE प्रकाशित नहीं करेगा\nप्रवर्तन लेखा परीक्षा — 1,182,811 प्रतिबंध जनगणना\n\nहमने Valve से नहीं पूछा कि खेत कितना बड़ा है। हम गिना गया यह\n\nयह अनुभाग क्या प्रमाणित करता है\n\nयह ऑडिट Valve के आधिकारिक GetPlayerBans एंडपॉइंट का उपयोग करके 1,182,811 द्वारा प्रतिबंधित खातों की एक अनुभवजन्य जनगणना प्रस्तुत करता है, जिसमें वाणिज्यिक बॉट फार्मिंग समूहों को प्रलेखित धोखाधड़ी रजिस्ट्रियों के साथ क्रॉस-रेफरेंस किया गया है। यह साबित करता है कि प्रतिबंधित बॉट्स में से 63% ने प्रवर्तन से पहले Valve के $5.00 स्टोर गेटिंग शुल्क का भुगतान किया, जिससे प्रारंभिक राजस्व में लाखों डॉलर उत्पन्न हुए। इसके अलावा, धोखाधड़ी रजिस्ट्री में दर्ज 51,732 दोषी ठहराए गए स्कैमर्स में से 67% पर कोई सामुदायिक या व्यापार प्रतिबंध नहीं हैं—जो दर्शाता है कि प्लेटफ़ॉर्म प्रवर्तन पीड़ितों की क्षतिपूर्ति के बजाय वाणिज्यिक राजस्व वसूली के रूप में कार्य करता है।\n\n← कार्यकारी ब्रीफिंग पर वापस\n\nSteam पर कितने ऑटोमेशन खाते चलते हैं, इसका कोई प्रकाशित आंकड़ा नहीं है। इसे गुप्त रखने की कोई आवश्यकता नहीं है: Steam आईडी स्पेस एक निरंतर पूर्णांक श्रेणी है और Valve उस वेब API कुंजी को बांटता है जो इसे क्रमिक रूप से घूमती है। तो हमने खुद को पहचानने वाली सबसे बड़ी आबादी — ArchiSteamFarm समुदाय — को लिया और Valve के अपने प्रतिबंध एंडपॉइंट के माध्यम से प्रत्येक सदस्य को एक बार पढ़ा। यह स्वयं घोषित करता है क्योंकि ASF, पहली बार लॉन्च करने पर, स्वचालित रूप से Steam समूह में शामिल हो जाता है जब तक कि उपयोगकर्ता स्पष्ट रूप से बाहर नहीं निकलता या समूह-सदस्यता सेटिंग को अनचेक नहीं करता (AutoJoinSteamGroup / सांख्यिकी)। चूंकि यह सेटिंग डिफ़ॉल्ट रूप से सक्रिय है, समूह की सदस्यता एक व्यापक जनसंख्या को समाहित करती है: सक्रिय बहु-खाते वाले वाणिज्यिक बॉट नेटवर्क, आकस्मिक निष्क्रिय शौकीन, और साधारण खिलाड़ी जिन्होंने अपने व्यक्तिगत खाते पर सॉफ़्टवेयर चलाया और कभी भी डिफ़ॉल्ट सदस्यता नहीं हटाई। यह इसकी सदस्यता को सॉफ़्टवेयर की संचयी पहुंच का एक कार्यशील जनगणना बनाता है: 10,880,610 कुल खाते (5,360,499 के साथ पुष्टिकृत गैर-सीमित सदस्य $5.00 स्टोर गेट के पार)। फिर हमने वह एकमात्र महत्वपूर्ण सवाल पूछा — 'Valve' ने वास्तव में उनके साथ क्या किया है?\n\nयह पृष्ठ क्या नहीं है। यह तर्क नहीं है कि Valve को दस मिलियन लोगों पर प्रतिबंध लगाना चाहिए, और यह कार्ड फार्मर्स के बारे में कोई शिकायत नहीं है। नीचे दिए गए प्रत्येक नंबर का एक ही कारण है: Valve करता है व्यक्तियों पर स्थायी रूप से प्रतिबंध लगाना, और जो कारण यह लिखित रूप में देता है वह है Steam और स्वचालन का व्यावसायिक उपयोग। यह मापता है कि वही नियम उसी आचरण पर बड़े पैमाने पर कैसे लागू होता है — एक ऑपरेटर द्वारा जिसकी $5.00 अनलॉक, गेम लाइसेंस और Market शुल्क Valve रास्ते में एकत्र करता है। निष्कर्ष असममितता है, फार्म नहीं।\n\n10.88एम काउंटठग जो चलते हैं (53.5k)100भुगतान वाला बनाम मुफ्त ऑडिट\n10,880,610कुल ASF समूह के सदस्यों ने Valve के स्वयं के प्रतिबंध API (सीमित + गैर-सीमित संयुक्त) को पढ़ा।\n88.97%कभी भी प्रतिबंधित नहीं हुए — 9,680,599 खाते अभी भी सक्रिय हैं\n63.06%प्रतिबंधित खातों का भुगतान किया जाता है ($5+ खर्च) — 100,000 SRSWOR स्लाइस (±0.39% MoE)\n67.77%51,732 द्वारा जांचे गए घोटालेबाजों पर कोई घोटाला प्रतिबंध नहीं है (पूर्ण जनगणना)\n01 — पैमाना\nदस मिलियन खाते, और दस में से नौ अछूते\n\nएक जनसंख्या जो स्वयं की गिनती करती है, Valve के स्वयं के एंडपॉइंट से एक बार पढ़ी जाती है।\n\nयह स्वयं-गणना क्यों करता है\nASF आपके लिए समूह में शामिल होता है\n\nपहली बार चलाने पर ArchiSteamFarm सेट करता है सांख्यिकी डिफ़ॉल्ट रूप से true होता है और Archi's SC Farm Steam समूह में शामिल हो जाता है। ऑपरेटर को सक्रिय रूप से बाहर निकलना होता है। इसलिए सदस्यता इंस्टॉल्स पर एक न्यूनतम सीमा है — अधिकतम नहीं। जिन ऑपरेटरों ने स्टैटिस्टिक्स अक्षम कर रखा है, वे अनुपस्थित हैं; वास्तविक इंस्टॉल्स की संख्या कम से कम इतनी ही बड़ी है।\n\nहम क्या पढ़ते हैं\n10,880,610 कुल प्रविष्टियाँ\n\nAPI सदस्य सूची ने कुल मिलाकर 10,880,610 SteamID64s लौटाए — सीमित और गैर-सीमित दोनों। Steam का समूह पृष्ठ केवल गैर-सीमित दिखाता है: 5,360,499। प्रत्येक प्रविष्टि को एक बार पास किया गया। आईस्ट्रीमयूज़र/गेटप्लेयरबैन 2026-09-23. पर एक की पर पैंतालीस मिनट।\n\nउत्तर\n88.97% साफ़\n\n1,200,011 कोई भी Steam प्रतिबंध (11.03%) लागू करें। अन्य 9,680,599 रिकॉर्ड पर कुछ भी नहीं है — न कोई सामुदायिक प्रतिबंध, न VAC, कुछ भी नहीं। फार्म को साफ नहीं किया जा रहा है। इसे चालू ही रहने दिया जा रहा है। वही धारा, जो एक व्यक्ति पर लागू की गई है, उसे स्थायी रूप से हटाने के लिए पर्याप्त है।\n\n10,880,610 खातों में से कितने Valve ने छुआ है?\n\nपूरे स्कैन किए गए आबादी को इस आधार पर विभाजित किया गया है कि क्या Valve ने कोई प्रतिबंध लगाया है या नहीं। लाल खंड वह सब कुछ है जो Valve ने इस बेड़े पर कभी लगाया है।\n\n88.97%कभी प्रतिबंधित नहीं\n11.03%\nकिसी भी प्रकार का कोई प्रतिबंध नहीं — 9,680,599 (88.97%)कुछ Steam प्रतिबंध शामिल हैं — 1,200,011 (11.03%)\n10,880,610ASF समूह के सदस्यों का स्कैन किया गया\n9,680,599कभी प्रतिबंधित नहीं — 88.97%\n1,200,011कोई भी प्रतिबंध लागू करें — 11.03%\n55 मिनइसे सब एक साथ गिनने के लिए, एक 'API' कुंजी पर\nइस बेड़े ने पहले ही मौजूद रहने के लिए Valve का भुगतान कर दिया है।\n\nयह फार्म की कमाई का अनुमान नहीं है। यह Valve की दुकान में पहले से खर्च की गई न्यूनतम राशि की सीमा है — जो Valve के अपने नियम से व्युत्पन्न है, जिसे उपरोक्त गणना पर लागू किया गया है।\n\n10,880,610 की गिनती API द्वारा लौटाई गई पूर्ण ASF समूह सदस्य सूची को कवर करती है — इसमें सीमित और गैर-सीमित दोनों खाते शामिल हैं। Steam का अपना सीमित उपयोगकर्ता खाते पृष्ठ कहता है कि सीमित खाते नहीं करते की ओर गिनना Steam समूह सदस्यता (उन्हें प्रदर्शित समूह आकार से बाहर रखा गया है), लेकिन वे फिर भी अंतर्निहित सदस्य सूची में दिखाई दे सकते हैं। गैर-सीमित उपसमूह — वे खाते जिन्होंने Steam स्टोर में कम से कम $5.00 खर्च किए हैं — बिल्कुल 5,360,499 — समूह पृष्ठ पर Steam द्वारा प्रदर्शित संख्या, जो Steam के अपने नियम के अनुसार सीमित खातों को बाहर रखती है। $5.00 का न्यूनतम गणना मान केवल उस गैर-सीमित उपसमूह पर ही लागू होता है।\n\n5,360,499असीमित सदस्य\n(Steam द्वारा प्रदर्शित समूहों की संख्या)\n×\n$5.00Valve का अपना न्यूनतम\nसीमित होना बंद करने के लिए\n=\n$26,802,495स्टोर खर्च पर निचला सीमा\nगैर-सीमित उपसमूह द्वारा\n\nयह 'Valve' द्वारा बेड़े के गैर-सीमित हिस्से से पहले से प्राप्त धनराशि पर एक निचला अनुमान है — यह राजस्व का अनुमान नहीं है, न ही लाभ का दावा। अधिकांश खातों के लिए वास्तविक खर्च अधिक है; $5.00 की यह राशि केवल आवश्यक न्यूनतम सीमा है।\n\nद्वितीयक उपज: खेती की गई वस्तु की मात्रा पर अधिकतम 66.7% का शुल्क। $26.8M प्रवेश शुल्क के अलावा, Community Market पर तरल होने वाले प्रत्येक कार्ड और वस्तु ड्रॉप Valve को अनिवार्य रूप से दो सेंट का न्यूनतम शुल्क (0.01 Steam शुल्क + $0.01 प्रकाशक शुल्क) का भुगतान करना होता है। सामान्य 3-सेंट कार्ड और कबाड़ वस्तुओं पर, Valve 3 सेंट में से 2 सेंट कम करता है — Valve के पक्ष में 66.67% की प्रभावी कटौती।, हेडलाइन 15% मार्केटिंग दर से कहीं अधिक।\n\nमहत्वपूर्ण जनसंख्या चेतावनी: समूह सदस्यता यह प्रमाण नहीं है कि प्रत्येक खाता एक समर्पित बॉट है, और यह Steam पर मौजूद हर बॉट को भी शामिल नहीं करती। ASF लॉन्च के समय डिफ़ॉल्ट रूप से खातों को अपने समुदाय समूह में स्वचालित रूप से सब्सक्राइब कर देता है; जब तक कि उपयोगकर्ता उस कॉन्फ़िगरेशन फ़्लैग को स्पष्ट रूप से अनचेक या अक्षम न कर दे।AutoJoinSteamGroup), नियमित खिलाड़ी, एक-बार के आलसी, और समुदाय के सदस्य स्वचालित फार्मिंग बेड़ों के साथ रोस्टर में बने रहते हैं। इसके अलावा, एक Steam प्रतिबंध के लिए कोई सार्वजनिक कारण क्षेत्र नहीं होता। यह निष्कर्ष इस सॉफ़्टवेयर-संबंधित आबादी में एक अनुभवजन्य दर है, न कि किसी एक खाते पर व्यक्तिगत निर्णय। समग्र, पुनरुत्पादित: asf-ban-census-2026-09-23.json.\n\n02 — भूगोल\nजहाँ बेड़ा रहता है\n\nप्रतिबंधित खातों में से केवल 8.5% ही कोई देश घोषित करते हैं। जो ऐसा करते हैं, उनमें सबसे बड़ा हिस्सा संयुक्त राज्य अमेरिका का है।\n\nSteam प्रोफ़ाइल में एक वैकल्पिक देश फ़ील्ड होती है। 100,413 1,182,811 के प्रतिबंधित खातों को भरें — 8.5%.† उस अल्पसंख्यक में संयुक्त राज्य अमेरिका 15.5%, पर शीर्ष पर है, फिर यूक्रेन, चीन और रूस, और बाकी पूरे यूरोप, लैटिन अमेरिका और दक्षिण-पूर्व एशिया में फैली एक लंबी पूंछ में आते हैं। कोई भी क्षेत्र की पुष्टि नहीं करता: अफगानिस्तान शीर्ष दस में है, जो लगभग उसकी कीमत के बराबर है। अन्य '91.5%' को आवंटित करने के बजाय छोड़ दिया गया है, इसलिए जो आगे आता है वह एक स्व-चयनित अल्पसंख्यक का स्वरूप है — न तो बेड़े का नक्शा, और न ही यह बताने का आधार कि इसे कहाँ से चलाया जाता है।\n\nघोषित देश के अनुसार प्रतिबंधित खाते\n\nसार्वजनिक स्थान प्रकट करने वाले प्रतिबंधित 100,413 खातों में शीर्ष 15 देश। यह उस स्थित उपसमूह का हिस्सा है। संख्या देखने के लिए होवर करें।\n\n0%\n5%\n10%\n15%\n20%\nUnited States\nUkraine\nChina\nRussia\nCanada\nAustralia\nJapan\nBrazil\nGermany\nAfghanistan\nUnited Kingdom\nRomania\nFrance\nPhilippines\nIndia\n\nसे पढ़ी गई स्थिति खिलाड़ियों के सारांश प्राप्त करें प्रतिबंधित उपसमूह के लिए। यह फ़ील्ड खाता धारक द्वारा सेट की जाती है और किसी द्वारा भी सत्यापित नहीं की जाती, इसलिए वीपीएन एग्जिट या मज़ाकिया प्रविष्टि को असली प्रविष्टि के समान ही गिना जाता है।\n\n03 — ताजगी\nहाल के खाते, कोई विरासत में मिला पिछड़ा काम नहीं\n\nखाता-निर्माण समय के अनुसार, प्रतिबंधित जनसंख्या हाल की है, न कि ट्रेडिंग-कार्ड युग की बची हुई।\n\nअगर यह कोई पुरानी गड़बड़ी होती जिसे धीरे-धीरे साफ किया जा रहा होता, तो प्रतिबंधित खाते शुरुआती ट्रेडिंग-कार्ड वर्षों की ओर झुकते। वे इसके विपरीत करते हैं। प्रतिबंधित खातों में से, जिनके निर्माण की तारीख पता चलती है, उनमें से 1,132,852 के प्रतिबंधित खाते, 70% 2020 या बाद में बनाए गए, और लगभग आधे 2023. के बाद। गिनती 2017 में बनाए गए 59,175 से बढ़कर चरम पर पहुँच जाती है। 227,030 केवल 2024 में बनाया गयाउनमें से प्रत्येक ने कार्ड प्राप्त करने से पहले $5.00 स्टोर गेट को पार कर लिया, इसलिए प्रत्येक से प्रवेश शुल्क वसूला गया।\n\nजब प्रतिबंधित खाते बनाए गए थे\n\n1,132,852 के खाता-निर्माण वर्ष के प्रतिबंधित सदस्य जो निर्माण तिथि प्रकट करते हैं। मास 2020–2026, है, न कि 2013–2015 ट्रेडिंग-कार्ड युग। शिखर: 2024.। संख्याओं के लिए होवर करें।\n\n0k\n63k\n125k\n188k\n250k\n'13\n'14\n'15\n'16\n'17\n'18\n'19\n'20\n'21\n'22\n'23\n'24\n'25\n'26\n70%2020या उसके बाद बनाए गए प्रतिबंधित खातों में से\n227,0302024 में बनाए गए प्रतिबंधित खाते — चरम वर्ष\n51,7012021त्रुटि, दो चरम वर्षों के बीच — अस्पष्ट\n2003→2026दायरा मौजूद है, लेकिन द्रव्यमान पिछले छह वर्षों का है।\n\nसृजन की तारीख खिलाड़ियों के सारांश प्राप्त करें प्रतिबंधित उपसमूह के लिए, SteamID64 द्वारा डुप्लिकेट हटाया गया। निर्माण तिथि वह समय है जब खाता बनाया गया था, न कि जब उसे प्रतिबंधित किया गया या जब उसने फार्मिंग शुरू की; इसे यहाँ आबादी कितनी हालिया है, इस बात के प्रमाण के रूप में पढ़ा जाता है, इरादे के रूप में नहीं। चार्ट तीन बातें नहीं दिखाता:\n\n2024. के बाद एक प्रवृत्ति 2025 या 2026 पर बनाया गया खाता प्रतिबंध लगने के लिए कम समय का रहा है, और 2026 नौ महीने का कवर करता है — इसलिए 227,030 → 121,070 → 16,534 सेंसर कर रहा है, यह गिरावट नहीं है।\nएक प्रतिबंध दर निर्माण वर्ष केवल प्रतिबंधित खातों के लिए ही पढ़े गए थे, इसलिए कोई विभाजक नहीं है। केवल बढ़ता हुआ इंस्टॉल आधार ही इस आकार को उत्पन्न करेगा।\n2021 क्यों ढह गया। 51,701 यह 105,821 और 104,641, के बीच स्थित है, और दोनों में से किसी के भी आधे हिस्से के नीचे आता है। इसे सार्वजनिक रूप से कुछ भी स्पष्ट नहीं करता; इसे चिकना किए बिना दिखाई देने के लिए छोड़ दिया गया है।\n04 — समय\nजब Valve कार्य करता है, तो यह पहले वर्ष के भीतर कार्य करता है।\n\n88.97% को छूए बिना स्पष्ट बचाव एक बैकलॉग है। पुराने प्रतिबंध इसके विपरीत कहते हैं।\n\nप्रतिबंध लगने के समय खाता कितने साल पुराना था।\n\nप्रतिबंध के समय खाते की आयु, 293,750 के उन प्रतिबंधित खातों के लिए जिनमें निर्माण तिथि और अंतिम प्रतिबंध की तिथि दोनों दर्ज हैं। आधे से अधिक खाते पहले वर्ष के भीतर पकड़े गए।\n\n0%\n10%\n20%\n30%\n40%\n<6 mo\n33.7%\n6–12 mo\n21.5%\n1–2 y\n20.6%\n2–5 y\n14.3%\n5 y+\n10.0%\n55.1% inside the first year\nपहले वर्ष के भीतर प्रतिबंधित — 55.1%बाद में प्रतिबंधित — 44.9%\n0.80 वाईप्रतिबंध लगने के समय खाते की मध्य आयु\n55.1%खाते के पहले वर्ष के भीतर प्रतिबंधित\n33.7%पहले छह महीनों के भीतर प्रतिबंधित\n293,750खाते जहाँ दोनों तिथियाँ मौजूद हैं\n\nयह स्पष्ट रक्षा के उत्तर के लिए है। यदि बेड़े के 88.97% को अछूता छोड़ दिया जाता है क्योंकि प्रवर्तन बस धीमा है — एक बैकलॉग जो धीरे-धीरे निपट रहा है — तो फिर जो प्रतिबंध करो लैंड पुराना झुक जाएगा। वे इसके विपरीत करते हैं: प्रतिबंधित खाते का मध्यक था साढ़े नौ महीने काऔर तीसरा — 33.7% — छह महीनों के भीतर पकड़ा गया। जब Valve इस आबादी पर कार्रवाई करता है, तो वह तेज़ी से करता है। अभी भी भाग रहे दस में से नौ लोग कतार में इंतज़ार नहीं कर रहे हैं।\n\nप्रतिबंध की आयु = से निर्माण तिथि खिलाड़ियों के सारांश प्राप्त करें द्वारा निहित प्रतिबंध तिथि से घटाया गया पिछली प्रतिबंध से बीते दिन, 2026-09-23. पर पढ़ें। यह केवल तभी गणना किया जाता है जब दोनों मान मौजूद हों: 1,200,011 के प्रतिबंधित खातों का 293,750। शेष खाते कोई days-since मान नहीं दिखाते और उन्हें हटा दिया जाता है, अनुमानित नहीं — इसलिए इसे प्रत्येक प्रतिबंध की नहीं, बल्कि दिनांकित उपसमूह की आकृति के रूप में पढ़ें।\n\n05 — वास्तव में यह प्रतिबंध क्या है\nजब Valve क्रिया करता है, तो यह बॉट को नहीं रोकता।\n\n11%ों में से जो भी प्रतिबंध रखते हैं, देखें कि कौन सा प्रतिबंध है।\n\nप्रतिबंध कोई प्रतिबंध नहीं है। 1,200,011 खातों में से जिन्हें Valve ने चिह्नित किया है, 99.8% एक को ले जाना समुदाय प्रतिबंध — फोरम, प्रोफाइल और समूहों पर एक प्रतिबंध जो ट्रेडिंग बॉट को बिल्कुल प्रभावित नहीं करता। खाता अभी भी कार्ड प्राप्त कर सकता है, अभी भी ट्रेड कर सकता है, अभी भी इन्वेंटरी स्थानांतरित कर सकता है। 22.2% पर कम से कम एक गेम बैन और 3.9% पर एक VAC बैन होता है; श्रेणियाँ ओवरलैप करती हैं, इसलिए वे जुड़कर नहीं होतीं। एकमात्र प्रतिबंध जो वास्तव में ट्रेडिंग को काट देता है, अर्थव्यवस्था/ट्रेड बैन, 5,214 खातों पर लागू है। हम उस संख्या पर ही मामला समाप्त नहीं कर रहे हैं — Steam में व्यापार प्रतिबंध आम तौर पर दुर्लभ हैं। इस चार्ट का उद्देश्य सरल है: यहां तक कि Valve का अंश करता है टच ट्रेडिंग जारी रखता है।\n\n11% जिन्हें प्रतिबंधित किया गया है, वास्तव में किसके लिए प्रतिबंधित किया गया है\n\n10,880,610 प्रत्येक प्रतिबंध प्रकार सभी स्कैन किए गए सदस्यों में हिस्सेदारी के रूप में। खातों में एक से अधिक हो सकते हैं। संख्या देखने के लिए होवर करें।\n\n0%\n4%\n8%\n11%\n15%\nCommunity ban\nGame ban\nVAC ban\nEconomy / trade ban\n\nSteam प्रतिबंध में कोई कारण क्षेत्र नहीं होता, इसलिए इनमें से कोई भी प्रतिबंध विशेष रूप से कार्ड फार्मिंग के लिए नहीं लगाया गया है — यह मौजूद प्रतिबंध प्रकारों का मिश्रण है, साथ ही यह भी दर्शाता है कि प्रत्येक प्रकार वास्तव में क्या प्रतिबंधित करता है। कम्युनिटी प्रतिबंध ट्रेडिंग को नहीं रोकता; इकोनॉमी/ट्रेड प्रतिबंध रोकता है। सारांश: asf-ban-census-2026-09-23.json.\n\n06 — दूसरी आबादी\nठगों ने Valve को बेनकाब कर दिया: 51,732 की पूरी जनगणना\n\nएक दूसरी स्वतंत्र सूची — समुदाय द्वारा पुष्टि की गई धोखाधड़ी — उसी आधिकारिक API के आधार पर मापी गई।\n\nऑटोमेशन आबादी को हानिरहित आलसी के रूप में खारिज किया जा सकता है। दूसरी आबादी को नहीं। SteamRep एक लंबे समय से चलने वाला सामुदायिक प्रतिष्ठा डेटाबेस है; एक चिह्नित खाता प्रतिबंधित उस समुदाय द्वारा एक व्यक्ति को धोखेबाज़ घोषित किया गया है, जिसके पास पीड़ितों के प्रमाण और लेनदेन चैट लॉग्स हैं। हमने सभी की एक ईमेल सर्वेक्षण ( 100% ) पूरी कर ली है। 51,732 वह प्रोफ़ाइल जिनका BANNED स्टेटस है Steam की आधिकारिक वेब API के खिलाफआईस्ट्रीमयूज़र/गेटप्लेयरबैन/वी1) — और केवल उन प्रतिबंधों को गिना गया जो धोखाधड़ी से निपटते हैं। VAC प्रतिबंध किसी गेम में सॉफ़्टवेयर धोखाधड़ी (एआईएमबॉट्स, वॉलहैक्स) के लिए होता है; यह किसी व्यापारी पर कोई प्रभाव नहीं डालता और यह इस बात का प्रमाण नहीं है कि Valve ने धोखाधड़ी पर कार्रवाई की हो, इसलिए इसे धोखाधड़ी प्रवर्तन के रूप में नहीं गिना जाता।\n\n51,732-खाते की संपूर्ण जनगणना में, 67.77% — 35,059 द्वारा जांचे गए धोखेबाज़ — पर Valve से कोई भी धोखाधड़ी-संबंधी प्रतिबंध नहीं है: वे अभी भी ट्रेड कर सकते हैं, नए शिकारों को फ्रेंड रिक्वेस्ट भेज सकते हैं, संदेश भेज सकते हैं। केवल 32.23% को ही समुदाय या ट्रेड प्रतिबंध का सामना करना पड़ा, और ट्रेड प्रतिबंध — वह एकमात्र कार्रवाई जो वास्तव में इन्वेंटरी ट्रांसफर को रोकती है — केवल 18.81% (9,731 खातों) पर ही लागू है। अतिरिक्त 12.81% (6,627 खाते) केवल इन-गेम चीटिंग के लिए VAC या गेम प्रतिबंध झेल रहे हैं, जबकि Steam ट्रेडिंग में पूरी तरह से बिना किसी प्रतिबंध के हैं।\n\nपुष्ट किए गए धोखेबाज, यह देखते हुए कि क्या Valve ने धोखाधड़ी-संबंधित प्रतिबंध लगाया (पूर्ण जनगणना)\n\n51,732 SteamRep-BANNED प्रोफाइल, इस आधार पर विभाजित कि क्या Valve ने सामुदायिक या व्यापार प्रतिबंध लगाया। VAC और गेम प्रतिबंध शामिल नहीं हैं — वे धोखाधड़ी से संबंधित नहीं हैं। संख्याएँ देखने के लिए होवर करें।\n\n0%\n18%\n35%\n53%\n70%\nNo scam-relevant ban\nCommunity or trade ban\n0%\n6%\n13%\n19%\n25%\nCommunity ban\nTrade / economy ban\nVAC (not fraud)\nGame ban\n51,732SteamRep-प्रतिबंधित प्रोफाइलों का ऑडिट — 100% की पूरी जनगणना\n35,059कोई घोटाला-संबंधित प्रतिबंध नहीं (67.77%)\n18.81%धोखाधड़ी को खत्म करने वाले व्यापार प्रतिबंध को लागू करें (9,731)\n32.23%शेयर Valve को सामुदायिक या व्यापार प्रतिबंध (16,673) का सामना करना पड़ा।\n\nSteamRep एक तृतीय-पक्ष, समुदाय-निर्णित प्रतिष्ठा डेटाबेस है, न कि Valve का निर्धारण — और यही बात है: बाहरी साक्ष्य, जिन्हें Valve ने स्वयं जो किया, उसके आधार पर मापा गया। सभी 51,732 BANNED प्रोफाइल को मानक निर्यात से सीधे क्रॉस-रेफरेंस किया गया था। आईस्ट्रीमयूज़र/गेटप्लेयरबैन/वी1. \"Scam-relevant\" का अर्थ है समुदाय या अर्थव्यवस्था/व्यापार प्रतिबंध; VAC (12.81%) और गेम प्रतिबंध (3.86%) को अलग से गिना जाता है क्योंकि ये धोखाधड़ी नहीं बल्कि चीटिंग से संबंधित हैं। पूर्ण ऑडिट डेटासेट: स्टीमरेप_स्टीम_बैन.सीएसवी.\n\nदो आबादी, एक निष्कर्ष\n\nये लोग एक जैसे नहीं हैं और उनका आचरण भी एक जैसा नहीं है। एक में दस मिलियन ऑटोमेशन खाते हैं; दूसरे में पैंतालीस हजार तीन सौ न्यायनिर्णित धोखेबाज हैं। जो बात इन्हें जोड़ती है वह परिणाम का स्वरूप है: दस में से नौ कृषि खाते कभी छुए नहीं जाते, और पुष्टि किए गए धोखेबाजों में से दो-तिहाई से अधिक (67.77%) को धोखाधड़ी से संबंधित कोई दंड नहीं मिलता। Valve द्वारा दी जाने वाली सामुदायिक प्रतिबंध मुफ्त में फोरम और प्रोफाइल को प्रतिबंधित करता है, व्यापार को नहीं। रिपोर्ट बटन, प्रतिष्ठा डेटाबेस, वह प्रतिबंध जो धोखाधड़ी को रोकता है: सभी मौजूद हैं, सभी कम इस्तेमाल किए जाते हैं। इसे मुख्य दस्तावेज़ में संग्रहीत इनकारों के बगल में रखें, जहाँ वही कंपनी एक ही खाते को स्थायी रूप से हटा देती है और व्यावसायिक उपयोग व स्वचालन को कारण बताती है — यह प्रावधान निष्क्रिय नहीं है, यह तीखा है।\n\n07 — $5.00 खाता गेट और खाता हाईजैकिंग\n100,000-खाते का अनुभवजन्य ऑडिट: बॉटनेट्स निस्सरकारी मुफ्त खाते नहीं हैं।\n\nसांख्यिकीय नमूनाकरण तर्क और गणितीय प्रमाण: किसी अन्य 100,000 खाते को लेने पर भी बिल्कुल वही परिणाम क्यों मिलता है।\n\nValve का नियामकों और उपभोक्ता संरक्षण निकायों के समक्ष मुख्य बचाव यह रहा है कि स्वचालित घोटाले और फार्मिंग क्षणिक, मुफ्त \"थ्रोअवे\" खातों के माध्यम से की जाती हैं जिन्हें तुरंत प्रतिबंधित कर दिया जाता है। Valve के प्रकाशित नियमों के तहत, एक खाता है सीमित जब तक यह कम से कम खर्च नहीं कर लेता $5.00 अमेरिकी डॉलर Steam स्टोर में, जो इसे ट्रेडिंग, फ्रेंड रिक्वेस्ट और API सुविधाओं से बाहर कर देता है। हमने इस दावे का सीधे परीक्षण करके सत्यापन किया, एक प्रतिनिधि और गणितीय रूप से कठोर नमूने के मुद्रीकरण की स्थिति का परीक्षण करके। 100,000 Steam खातों पर प्रतिबंध हमारे 1,182,811 प्रोफ़ाइल मेटाडेटा कॉर्पस से लिया गया।\n\nनमूनाकरण प्रोटोकॉल (SRSWOR)\n100,000 निष्पक्ष स्लाइस\n\nसे लिया गया N 1,182,811 ने क्रिप्टोग्राफ़िक रूप से एकसमान PRNG के माध्यम से बिना प्रतिस्थापन के सरल यादृच्छिक नमूनाकरण का उपयोग करके अद्वितीय रूप से प्रतिबंधित Steam खाते बनाए। प्रत्येक खाते की समावेशन संभावना समान रूप से थी। P = n / N ≈ 8.45%,, सर्वाइवर्सशिप और एक्टिविटी बायस को पूरी तरह से समाप्त करते हुए।\n\nगणितीय प्रमाण\nत्रुटि की सीमा < ±0.4%\n\nएक पर जनसंख्या-सीमित सुधार (FPC) सूत्र को लागू करना 99% विश्वास अंतराल (Z = 2.576):\nMoE = Z × √[p(1-p)/n] × √[(N-n)/(N-1)] ≈ ±0.39%\n\nपुनरुत्पादनशीलता\nक्यों कोई भी 100क उपज समान होती है\n\nक्योंकि ±0.4% के अंतर्गत त्रुटि का मार्जिन 99% विश्वास पर सीमित है, किसी भी अन्य स्वतंत्र 100,000-खाता नमूने का चयन गणितीय रूप से गारंटी है कि यह 63.06% ± 0.39% के भीतर आएगा। (62.67% से 63.45%)। यह नमूना पूरी 1.18 मिलियन प्रतिबंधित आबादी का प्रतिनिधित्व करता है।\n\nऑडिट के परिणाम \"थ्रोअवे बॉट\" रक्षा को पूरी तरह से ध्वस्त कर देते हैं। Steam के लेगेसी XML प्रोफ़ाइल इंटरफ़ेस के माध्यम से ऑडिट किए गए 100,000 खातों में से: 61,490 खाते (वर्गीकृत खातों के 63.06%) गैर-सीमित (भुगतान किए गए) खाते हैं, जिन्होंने Steam पर कम से कम $5.00 खर्च किए हैं। केवल 36,021 (36.94%) सीमित मुफ्त खाते हैं, जबकि 2,489 अकॉन्फ़िगर किए गए या निजी थे।\n\n100,000 प्रतिबंधित खाते: सशुल्क ($5+ स्टोर खर्च) बनाम निःशुल्क सीमित स्थिति\n\n100,000 द्वारा यादृच्छिक रूप से नमूना लिए गए प्रतिबंधित खातों का अनुभवजन्य ऑडिट। 63% से अधिक ने Valve के सशुल्क वित्तीय गेट को पार कर लिया है। संख्याओं को देखने के लिए होवर करें।\n\n0%\n16%\n33%\n49%\n65%\nNon-limited (Paid ≥ $5.00)\nLimited (Free < $5.00)\n100,000नमूनाकृत जनसंख्या (SRSWOR, N=1.18M)\n63.06%गैर-सीमित सशुल्क खाते (61,490 खाते)\n±0.39%99% विश्वास अंतराल पर त्रुटि की सीमा\n~745,8001.18M प्रतिबंधित कोरपस में अनुमानित भुगतान किए गए खाते\nसंरचनात्मक वास्तविकता: औद्योगिक पैमाने पर खाते का परिसमापन\n\nनमूना के रूप में लिए गए प्रतिबंधित खातों में से 63% वास्तविक धन खर्च करने वाले भुगतान किए गए खाते क्यों होंगे जो Valve की दुकान में खरीदारी करते थे? बॉटनेट ऑपरेटर एकबारगी खातों पर अपनी जेब से लाखों खर्च नहीं करते। यह अनुपात मात्रा को उजागर करता है। संक्रमित और हाईजैक किए गए खाते पारिस्थितिकी तंत्र में संचारित होते हुए।\n\nयह पैमाना भूमिगत प्लेटफ़ॉर्मों पर सीधे देखा जा सकता है: FSB मार्केट (एक गुमनाम लेबल; मूल नाम यहाँ छिपाया गया है) जैसे बाज़ारों पर, ओवर 550,000 Steam खाते (स्टीलर लॉग, फ़िशिंग कैप्चर, क्रेडेंशियल स्टफिंग) किसी भी समय सक्रिय रूप से बिक्री के लिए सूचीबद्ध होते हैं (phishdestroy.io/लाइव-इंटेल). बाज़ार खरीदारों और विक्रेताओं को Valve के अपने Steam OpenID का उपयोग करके प्रमाणीकृत करता है, और न ही FSB Market न the associated forum Valve के लिंक फ़िल्टर द्वारा अवरुद्ध है।\n\nधारा 06, में स्थापित के अनुसार, Valve इस धोखाधड़ी की गतिविधि को सक्रिय रूप से समाप्त नहीं करता है: 67.77% समुदाय द्वारा पुष्टि किए गए घोटाबाज़ों पर Steam पर घोटाले पर कोई प्रतिबंध नहीं है।, और ऑटोमेशन फ्लीट के 88.97% पूरी तरह से अछूते रहते हैं। खाते स्वतंत्र रूप से घूमते हैं, आधिकारिक एपीआई के माध्यम से प्रमाणीकरण करते हैं, और इकोसिस्टम में लगभग पूर्ण दंडमुक्ति के साथ व्यापार करते हैं।\n\nफोरेंसिक साक्ष्य एवं प्रवर्तन वास्तुकला आरेख\n10.88M स्कैन किए गए खातों से 100k अनुभवजन्य स्लाइस और 53.5k पुष्टि किए गए स्कैमर तक इंटरैक्टिव प्रवाह · कच्चे सबूतों की जांच के लिए लिंक पर क्लिक करें\nस्तर01·10.88एम ऑटोमेशन फ्लीट जनगणना\nSteam पर स्वयं-पहचान करने वाली सबसे बड़ी ऑटोमेशन आबादी क्रमबद्ध रूप से Valve की आधिकारिक प्रतिबंध API से गुज़री। यह साबित करता है कि व्यावसायिक बॉट बेड़े 88.97% के तहत बिना किसी दंड के चलते हैं, जबकि प्रवेश शुल्क के रूप में करोड़ों का भुगतान करते हैं।\n9,680,599 88.97% सक्रिय और अछूता\nऐसे खाते जो स्वचालित सॉफ़्टवेयर चला रहे हैं और जिनके रिकॉर्ड पर किसी भी प्रकार का कोई प्रतिबंध नहीं है।\nकच्चा जनगणना JSON (1.2 KB) ↗अनुभाग निरीक्षण करें01 ↗\n$26,802,495 प्रत्यक्ष स्टोर राजस्व न्यूनतम सीमा\nValve द्वारा 5,360,499 के गैर-सीमित सदस्यों से, न्यूनतम $5.00 प्रवेश सीमा पार करने पर एकत्रित।\nकार्ड अर्थव्यवस्था लेखा परीक्षा ↗Valve $5 नियम अक्सर पूछे जाने वाले प्रश्न ↗\n1,200,011 11.03% चिह्नित उपसमूह\n99.8% केवल कॉस्मेटिक समुदाय प्रतिबंध लागू हैं; खाते 99.95% पर व्यापार खुला रहता है।\nप्रतिबंध प्रकार का विवरण ↗प्रतिबंधित डीबी (60.4 एमबी) ↓\nस्तर02·100,000-खाता अनुभवजन्य नमूना लेखा परीक्षा (N = 1,182,811)\nविरासत XML एंडपॉइंट्स के माध्यम से मूल्यांकित प्रतिनिधि SRSWOR स्लाइस। गणितीय रूप से सिद्ध त्रुटि सीमा 99% विश्वास अंतराल पर ±0.4% से कम है। यह दावा खारिज करता है कि प्रतिबंधित बॉट्स मुफ्त फेंकने योग्य खाते हैं।\n61,490 (63.06%) गैर-सीमित भुगतान किए गए खाते ($5+ खर्च)\nप्रतिबंधित खातों में से 63% से अधिक भुगतान किए गए लेनदेन का प्रतिनिधित्व करते हैं। यह अनुमानित रूप से प्रतिबंधित पूल में लगभग745,800 भुगतान किए गए खातों (प्रवेश सीमा: $3.73मिलियन) के बराबर है।\nसीमित परिणाम CSV (2.1 एमबी) ↓100k फोरेंसिक रिपोर्ट ↗\n36,021 (36.94%) सीमित मुफ्त खाते (< $5.00)\nValve की \"डिस्पोजेबल थ्रोअवे बॉट\" प्रोफ़ाइल में फिट होने वाले प्रतिबंधित प्रोफाइलों का अल्पसंख्यक हिस्सा। 2,489 खाते अनकॉन्फ़िगर/निजी थे।\n100k नमूना स्लाइस CSV (8.5 एमबी) ↓व्यय विश्लेषण एमडी ↗\n34.67% बनाम 63.93% प्रोफ़ाइल स्वच्छता ऑडिट\nValve 34,673 खातों से उपनाम हटाकर raw SteamID64 कर दिया, लेकिन 63,928 प्रतिबंधित खातों पर कस्टम नाम और अवतार पूरी तरह से जस के तस छोड़े।\nसफ़ाई अनुभाग ↗अवलोकन रोडमैप ↗\n34.59% विरासत वयस्क खाते (2003–2019 द्वारा निर्मित)\nप्रतिबंधित खातों में से एक तिहाई से अधिक 5 से 20वर्षों पहले पंजीकृत थे, जो लंबे समय से Steam खेलने वाले खिलाड़ियों के खातों की औद्योगिक पैमाने पर हैकिंग को साबित करता है।\nआयु कालक्रम ↗सहायता अस्वीकृतियाँ ↗\nस्तर03·51,732 SteamRep द्वारा पुष्टि किए गए धोखेबाजों की जनगणना\n100% में सामुदायिक रूप से निर्णयित धोखेबाजों की पूरी जनगणना, जिसमें पीड़ित चैट लॉग और व्यापार प्रमाण शामिल हैं, और जिसे आधिकारिक Steam प्रतिबंध एपीआई के साथ क्रॉस-रेफरेंस किया गया है। यह प्रणालीगत प्रवर्तन विफलता को प्रमाणित करता है।\n35,059 (67.77%) शून्य घोटाला प्रतिबंध (पूर्ण दंडमुक्ति)\nValve से सत्यापित धोखेबाजों में से दो-तिहाई से अधिक के पास न तो Community प्रतिबंध है और न ही Trade प्रतिबंध। वे व्यापार करने और नए पीड़ित जोड़ने के लिए पूरी तरह से सक्रिय हैं।\nSteamRep API प्रतिबंध (2.6 एमबी) ↓SteamRep ऑडिट रिपोर्ट ↗\n9,731 (18.81%) अर्थव्यवस्था / व्यापार प्रतिबंध\nएकमात्र प्रतिबंध जो इन्वेंटरी तरलिकरण को काटता है। पुष्ट किए गए धोखेबाजों में से एक-पाँचवें से भी कम पर मौजूद।\nSteamRep स्रोत (2.1 एमबी) ↓अनुभाग निरीक्षण करें06 ↗\n6,627 (12.81%) अप्रसंगिक चीटिंग प्रतिबंध (केवल VAC)\nगेमों में एइमबॉट्स/वॉलहैक्स के लिए प्रतिबंधित, जबकि उनकी Steam व्यापार और फ़िशिंग क्षमताएँ 100% सक्रिय बनी हुई हैं।\nवीएसी अप्रासंगिकता विश्लेषण ↗सुरक्षा समयरेखा ↗\nस्तर04 · विकी विकृतिकरण और अगस्त 2026 अवसंरचना उल्लंघन\nआंतरिक डेवलपर दस्तावेज़ीकरण की तोड़फोड़, सामुदायिक संपादक का दमन, और सील न किए गए परिधि विफलताओं का दस्तावेजीकरण साक्ष्य पैक में किया गया है।\n1,200+ संपादक वीडीसी विकी संघर्ष लॉग्स\nकम्युनिटी संपादक जो फिशिंग लिंक और स्पैम टेम्पलेट्स को ठीक करने की कोशिश कर रहे थे, उन्हें स्वचालित फ़िल्टरों द्वारा व्यवस्थित रूप से अवरुद्ध किया गया, जबकि Valve के कर्मचारी चेतावनियों को अनदेखा कर रहे थे।\nरूसी संघर्ष रिपोर्ट (127 KB) ↗वर्गीकरण रिपोर्ट (66 KB) ↗\n12 टीबी अप्रमाणीकृत अगस्त 2026 एसेट लीक (CWE-284)\nValve 12 ने हफ्तों तक बिना प्रमाणीकरण के एक खुले सार्वजनिक एंडपॉइंट पर आंतरिक कोड और प्रोटोटाइप बिल्ड के टेराबाइट्स होस्ट किए।\nValve अक्षमता दस्तावेज़ (43 KB) ↗साक्ष्य संग्रह ↗\nCEVA लॉजिस्टिक्स डेटा उल्लंघन अगस्त2026 ग्राहक PII लीक\nValve के लॉजिस्टिक्स पार्टनर से यूरोपीय Steam डेक खरीदारों के नाम, पते और फोन नंबर लीक हो गए, जिससे फिशिंग की लहरें उठ गईं।\nघटना अभिलेख ↗प्रवर्तन अभिलेख ↗\n\nनमूनाकरण दोष: प्रतिबंधित_100k_स्लाइस.सीएसवी (100,000 खातों)। ऑडिट परिणाम: slice_100k_सीमित_परिणाम.सीएसवी. पूर्ण विश्लेषणात्मक रिपोर्ट: प्रतिबंधित_100K_न्यायिक_विश्लेषण.md.\n\n08 — विधि और सीमाएँ\nइसे कैसे पढ़ा गया, और यह क्या दावा नहीं करता\n\nतीन सार्वजनिक आबादी, एक सार्वजनिक API, कठोर सांख्यिकीय नमूनाकरण।\n\nकार्यन्वयन और प्रमाणपत्र\n\nASF जनगणना, 100,000-खाते का SRSWOR स्लाइस और SteamRep क्रॉस-चेक को PhishDestroy प्रतिभागियों ने अपने स्वयं के Steam खातों और Web API कुंजियों के तहत, गठबंधन के सार्वजनिक फ़िशिंग और घोटाला-प्रतिबंध कार्य के हिस्से के रूप में निष्पादित किया। डॉसियर के लेखक के पास कोई Steam वेब API कुंजी नहीं है और उन्होंने व्यक्तिगत रूप से कोई लाइव स्कैन नहीं किया। एकत्रीकरण, हैशिंग, सत्यापन और प्रकाशन प्रतिभागियों के आउटपुट से किया गया।\n\nजनसंख्या\tयह कहाँ से आया\tक्या पढ़ा गया\nASF members\n10,880,610\tThe public member list of the ArchiSteamFarm Steam Community group. Steam's group page shows 5,360,499 members (non-limited only); the API member list returned 10,880,610 total entries including limited accounts. The group is auto-joined on first run unless the user explicitly disables the default group-join setting in configuration (AutoJoinSteamGroup / Statistics), meaning the member list includes commercial bot clusters, individual card idlers, and regular gamers who left the default option enabled.\tGetPlayerBans for every member (ban flags); GetPlayerSummaries for creation dates and country. Batched at 100 IDs, deduplicated by SteamID64.\n100k Banned Accounts SRSWOR Slice\n100,000\tA representative sample drawn uniformly at random without replacement from the 1,182,811 banned accounts corpus ($P = 8.45\\%$). Finite Population Correction yields a margin of error of $\\pm 0.39\\%$ at a 99% confidence level ($Z = 2.576$).\tMonetization and limited account status (isLimitedAccount) audited via Steam's legacy XML profile interface (?xml=1) over distributed proxy pipelines. Confirms 63.06% paid status.\nSteamRep scammers\n51,732\tComplete 100% census of all profiles marked BANNED in the SteamRep community reputation database (51,732 total profiles). Zero sampling or filtering applied.\tISteamUser/GetPlayerBans/v1 for all 51,732 accounts, cross-tabulated against SteamRep status. Confirms 67.77% walk free of any scam bans.\nक्या दावा किया गया है\n\nकेवल अनुभवजन्य दरें और सांख्यिकीय रूप से सीमित अनुमान। ऑटोमेशन जनसंख्या में, 88.97% पर कोई प्रतिबंध नहीं है; प्रतिबंधित उपसमूह हालिया (70% से 2020 तक) में झुकाव दिखाता है। 100,000-खाते के अनुभवजन्य ऑडिट में, प्रतिबंधित खातों में से 63.06% का भुगतान किया जाता है (गैर-सीमित), गणितीय रूप से सिद्ध त्रुटि सीमा ±0.4%. के अंतर्गत। 51,732 द्वारा पुष्टि किए गए स्कैमर्स में, 67.77% पर कोई स्कैम-संबंधित प्रतिबंध नहीं है। प्रत्येक आंकड़ा Valve की अपनी वेब API से पुनः प्राप्त किया जा सकता है।\n\nक्या दावा नहीं किया गया है\n\nSteam प्रतिबंध में कोई कारण क्षेत्र नहीं होता, इसलिए यहाँ कोई प्रतिबंध किसी विशिष्ट कारण से नहीं जोड़ा जाता। समूह सदस्यता यह प्रमाण नहीं है कि कोई खाता स्वचालित बॉट है: क्योंकि ASF डिफ़ॉल्ट रूप से समूह में शामिल होने की सुविधा सक्षम करता है जब तक कि मैन्युअल रूप से अनचेक न किया जाए, इसलिए इसमें व्यावसायिक मल्टी-खाता फार्म और साधारण खिलाड़ियों व शौकीनों के व्यक्तिगत खाते दोनों शामिल हैं। देश स्वयं-रिपोर्ट किया गया है, और SteamRep सूचीकरण एक सामुदायिक निर्णय है, न कि न्यायालय का निर्णय। किसी व्यक्ति का नाम नहीं दिया गया है।\n\nयह क्यों मायने रखता है\n\nValve इसी API को रखता है, इसके पीछे अपना स्वयं का डेटाबेस है, और प्रतिबंध के कारण जिन्हें यह स्कैन देख नहीं सकता। यह पूरे आईडी स्पेस में इस क्वेरी को सेकंडों में चला सकता है। वह माप, जो किसी बाहरी पक्ष को किसी संख्या के खिलाफ प्रवर्तन दावे की जांच करने की अनुमति देता है, उस एक पक्ष द्वारा कभी प्रकाशित नहीं किया गया है जो इसे पूर्ण सटीकता के साथ उत्पन्न कर सकता है। यह बाहरी अनुमान है, जिसे इसलिए प्रस्तुत किया गया है ताकि प्रश्न एक संख्या संलग्न करके पूछा जा सके।\n\nअगला पढ़ें: यह आबादी जिस कार्ड अर्थव्यवस्था को चलाती है → · पहुँच और चोरी का समर्थन → · पूरा दस्तावेज़ →",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "प्रवर्तन लेखा परीक्षा — 1,182,811 प्रतिबंध जनगणना"
          },
          {
            "level": 2,
            "id": null,
            "text": "दस मिलियन खाते, और दस में से नौ अछूते"
          },
          {
            "level": 3,
            "id": null,
            "text": "ASF आपके लिए समूह में शामिल होता है"
          },
          {
            "level": 3,
            "id": null,
            "text": "10,880,610 कुल प्रविष्टियाँ"
          },
          {
            "level": 3,
            "id": null,
            "text": "88.97% साफ़"
          },
          {
            "level": 3,
            "id": null,
            "text": "10,880,610 खातों में से कितने Valve ने छुआ है?"
          },
          {
            "level": 3,
            "id": null,
            "text": "इस बेड़े ने पहले ही मौजूद रहने के लिए Valve का भुगतान कर दिया है।"
          },
          {
            "level": 2,
            "id": null,
            "text": "जहाँ बेड़ा रहता है"
          },
          {
            "level": 3,
            "id": null,
            "text": "घोषित देश के अनुसार प्रतिबंधित खाते"
          },
          {
            "level": 2,
            "id": null,
            "text": "हाल के खाते, कोई विरासत में मिला पिछड़ा काम नहीं"
          },
          {
            "level": 3,
            "id": null,
            "text": "जब प्रतिबंधित खाते बनाए गए थे"
          },
          {
            "level": 2,
            "id": null,
            "text": "जब Valve कार्य करता है, तो यह पहले वर्ष के भीतर कार्य करता है।"
          },
          {
            "level": 3,
            "id": null,
            "text": "प्रतिबंध लगने के समय खाता कितने साल पुराना था।"
          },
          {
            "level": 2,
            "id": null,
            "text": "जब Valve क्रिया करता है, तो यह बॉट को नहीं रोकता।"
          },
          {
            "level": 3,
            "id": null,
            "text": "11% जिन्हें प्रतिबंधित किया गया है, वास्तव में किसके लिए प्रतिबंधित किया गया है"
          },
          {
            "level": 2,
            "id": null,
            "text": "ठगों ने Valve को बेनकाब कर दिया: 51,732 की पूरी जनगणना"
          },
          {
            "level": 3,
            "id": null,
            "text": "पुष्ट किए गए धोखेबाज, यह देखते हुए कि क्या Valve ने धोखाधड़ी-संबंधित प्रतिबंध लगाया (पूर्ण जनगणना)"
          },
          {
            "level": 4,
            "id": null,
            "text": "दो आबादी, एक निष्कर्ष"
          },
          {
            "level": 2,
            "id": null,
            "text": "100,000-खाते का अनुभवजन्य ऑडिट: बॉटनेट्स निस्सरकारी मुफ्त खाते नहीं हैं।"
          },
          {
            "level": 3,
            "id": null,
            "text": "100,000 निष्पक्ष स्लाइस"
          },
          {
            "level": 3,
            "id": null,
            "text": "त्रुटि की सीमा < ±0.4%"
          },
          {
            "level": 3,
            "id": null,
            "text": "क्यों कोई भी 100क उपज समान होती है"
          },
          {
            "level": 3,
            "id": null,
            "text": "100,000 प्रतिबंधित खाते: सशुल्क ($5+ स्टोर खर्च) बनाम निःशुल्क सीमित स्थिति"
          },
          {
            "level": 3,
            "id": null,
            "text": "संरचनात्मक वास्तविकता: औद्योगिक पैमाने पर खाते का परिसमापन"
          },
          {
            "level": 2,
            "id": null,
            "text": "इसे कैसे पढ़ा गया, और यह क्या दावा नहीं करता"
          },
          {
            "level": 3,
            "id": null,
            "text": "क्या दावा किया गया है"
          },
          {
            "level": 3,
            "id": null,
            "text": "क्या दावा नहीं किया गया है"
          },
          {
            "level": 3,
            "id": null,
            "text": "यह क्यों मायने रखता है"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/hi/#briefing-heading",
          "https://help.steampowered.com/en/faqs/view/71D3-35C2-AD96-AA3A",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/asf-ban-census-2026-09-23.json",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/steamrep_steam_bans.csv",
          "https://phishdestroy.io/live-intel/?category=steam",
          "https://phishdestroy.io/steam_dossier/hi/card_economy.html",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/banned_archiasf_massive.csv",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/slice_100k_limited_results.csv",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/reports/BANNED_100K_FORENSIC_ANALYSIS.md",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/banned_100k_slice.csv",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/reports/STEAM_BANNED_LIMIT_ANALYSIS.md",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/INVESTIGATION_OVERVIEW.md",
          "https://phishdestroy.io/steam_dossier/hi/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/reports/STEAMREP_VS_STEAM_AUDIT.md",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/SteamRep_Profiles_BannedCaution_2024.csv",
          "https://phishdestroy.io/steam_dossier/hi/security_timeline.html",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/reports/russian_conflicts_report.json",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/reports/classification_report.json",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/reports/VALVE_INCOMPETENCE_REPORT.md",
          "https://phishdestroy.io/steam_dossier/hi/steam_evidence_archive.html",
          "https://phishdestroy.io/steam_dossier/hi/steam_enforcement_evidence.html",
          "https://phishdestroy.io/steam_dossier/hi/#insider-threat",
          "https://phishdestroy.io/steam_dossier/hi/"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/hi/enforcement_audit.content.json",
      "export_json_sha256": "9bdbc1d6bc8236b30b0620f1b0c88f168685c8f4371e2a25bf8fb3d550ef9e57"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "hi/index.html",
      "language": "hi",
      "title": "Steamका डोजियर: नियम, मार्ग और जवाबदेही",
      "source_url": "https://phishdestroy.io/steam_dossier/hi/index",
      "source_html_sha256": "ea2cf9e67f89a6b34f1a808fc78bd983604111284d6fd952e5492449ed1132b2",
      "exported_at": "2026-09-29T00:22:45.895Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "exhibit-gallery-section",
            "source": "https://phishdestroy.io/steam_dossier/hi/index#exhibit-gallery-section"
          }
        ],
        "raster_images_replaced": 2
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "index.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/hi/index.pdf?v=print-20260929-v5",
        "sha256": "df4215f1fb813adf0cc7848eaf787e8b8ab861b12dc8528026c385b1053ea180",
        "bytes": 1528562,
        "pages": 90
      },
      "integrity": {
        "signed_object": "index.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "index.content.json.asc",
        "digest_file": "index.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify index.content.json.asc index.content.json",
          "sha256sum -c index.content.json.sha256"
        ]
      },
      "content": {
        "text": "संक्षेप में — 5 सत्यापनीय दावेसभी 5 जिन्हें Valve के अपने सर्वरों, दस्तावेज़ों और प्रकाशित तिथियों के विरुद्ध सत्यापित किया जा सकता है।\n44\n\nतीसरे पक्ष के प्लेटफ़ॉर्म के लिए Steam लॉगिन ले जाने वाले अलग auth-host डोमेन पाए गए — प्रत्येक प्लेटफ़ॉर्म के मुख्य पते से अलग पंजीकृत एक डोमेन।\n\nधारा 3 →\n26\n\nफ़िल्टर-स्प्लिट जोड़े: मुख्य डोमेन 'Steam' लिंक फ़िल्टर चेतावनी दिखाता है; इसके बगल में स्थित लॉगिन होस्ट नहीं दिखाता।\n\nधारा 3.2 →\n12वाई 6एम\n\nकितना लंबा है api.csgem.com Steam लॉगिन किए हुए हैं csgogem.com लिंक फ़िल्टर पर बैठता है। पंजीकृत मार्च 2014.\n\nतालिका देखें →\n10 दिन\n\nValve की स्वयं की 2016 थी जो जुआ ऑपरेटरों के लिए थी। तब से कोई प्रति-ऑपरेटर प्रवर्तन रिकॉर्ड प्रकाशित नहीं किया गया है।\n\nधारा 2 →\n830 पीपी\n\nलेख 15GDPR Valve के वकीलों की प्रतिक्रिया — 902,270 निकाले जा सकने वाले छंटनी अंशों के पात्र, छंटनी बार को चयन योग्य पाठ के रूप में छोड़ा गया।\n\nधारा 18 →\nइसका क्या मतलब है — स्टीम लिंक फ़िल्टर\n\nValve एक लिंक फ़िल्टर बनाए रखता है जो Steam चैट या प्रोफ़ाइल टिप्पणियों में पोस्ट किए जाने पर जुआ और ट्रेडिंग साइटों के लिंक को ब्लॉक करता है। जब कोई उपयोगकर्ता एक ब्लॉक किए गए लिंक पर क्लिक करता है, तो Valve एक पूर्ण-स्क्रीन चेतावनी प्रदर्शित करता है: इस लिंक को संभावित रूप से दुर्भावनापूर्ण के रूप में चिह्नित किया गया है। हालाँकि, Valve केवल प्राथमिक वेबसाइट डोमेन की जाँच करता है। Steam OpenID प्रमाणीकरण के लिए उपयोग किए जाने वाले अलग-अलग डोमेन ब्लॉकलिस्ट में नहीं हैं — इसलिए मुख्य साइट अवरुद्ध होने के बावजूद लॉगिन प्रक्रिया सफल हो जाती है।\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\nधारा 1 — मामले का संक्षिप्त विवरण\nनियम। रिकॉर्ड। अनुत्तरित प्रश्न।\nप्रसंग और स्रोत सीमाएँ\n\nछह निष्कर्ष, प्रत्येक एक तिथिबद्ध सार्वजनिक अभिलेख से जुड़ा हुआ। विस्तृत अनुभाग इसी क्रम में हैं: तकनीकी अभिलेख (भाग A), नियम और प्रवर्तन अभिलेख (भाग B), कानूनी ढाँचे (भाग C), और फिर मुख्य प्रदर्शों के साथ परिशिष्ट।\n\nछह निष्कर्ष। प्रत्येक एक लिखित नियम को एक दिनांकित अभिलेख से जोड़ता है और एक ऐसे प्रश्न को उठाता है जिसे साक्ष्य द्वारा परखा जा सकता है।\n\n1. अलग-डोमेन प्रमाणन होस्ट — 44 मार्ग · 26 विभाजित जोड़े\n\nलाइव रजिस्टर रिकॉर्ड करता है 44 एक अलग पंजीकरण योग्य डोमेन के माध्यम से प्रमाणीकरण करने वाले प्लेटफ़ॉर्म. पाँच अतिरिक्त मार्ग सत्यापन के लिए लंबित हैं और एक RDAP तिथि की प्रतीक्षा कर रहे हैं; इन्हें बढ़ावा देने से कुल संख्या 47. हो जाएगी। इन्हें 44 और आयु चार्ट से बाहर रखा गया है। — 27 एक प्रकाशित प्रति-मार्ग साक्ष्य फ़ाइल के साथ और मैनुअल संग्रह से जोड़े गए 17, अलग सूचीबद्ध। में 26 फ़िल्टर-स्प्लिट जोड़े मुख्य डोमेन है अवरुद्ध Steam लिंक फ़िल्टर में जबकि उस लॉगिन को वह प्रॉक्सी नहीं ले जा रहा है। ये बर्नर डोमेन नहीं हैं: csgogem.com अवरुद्ध है जबकि api.csgem.com, होस्ट जो अपना Steam लॉगिन ले जा रहा है, मार्च से पंजीकृत है 2014 — 12 साल 6 महीनेValve को प्रत्येक OpenID अनुरोध में वह होस्टनाम प्राप्त होता है, और इसे अपनी लॉगिन पेज पर उपयोगकर्ता को वापस दिखाता है। पूर्ण तालिका, प्रति-मार्ग आयु और स्रोत जानकारी अनुभाग 3. में दी गई है।\n\nमार्ग का अनुसरण करें →\n2. 2016: प्रक्रिया का नाम रखा गया, समय-सीमा निर्धारित की गई।\n\nपर 13 जुलाई 2016 Valve Steam सार्वजनिक रूप से बताया कि कैसे जुआ साइटों ने ई-मेल OpenID और स्वचालित ट्रेडिंग खातों का उपयोग किया, और इसकी वकील की सूचनाओं का 20 जुलाई2016 दस दिन की समयसीमा निर्धारित की गई। तब से किसी भी ऑपरेटर-विशिष्ट प्रवर्तन रिकॉर्ड का प्रकाशन नहीं हुआ है। उस समयसीमा के जारी होने के दस साल बाद भी, उसी नाम की प्रक्रिया अलग-अलग डोमेन के auth होस्ट्स पर लागू है, जिन्होंने 2026-09-21. पर कोई Link Filter ब्लॉक नहीं लौटाया।\n\nWSGC के लिए खुले पत्र को पढ़ें →\n3. डिवाइस सहसंबंध, वकील के लेटरहेड पर\n\nयहाँ पुनरुत्पादित पत्राचार में, Valve के वकील ने एक डिवाइस-स्तर का सहसंबंध बताया जो एक डिवाइस को कई खातों से जोड़ता है — एक ऐसी क्षमता जिसे Steam सपोर्ट ने पहले उपयोगकर्ताओं को तकनीकी रूप से असंभव बताया था। खुलकर सवाल यह है कि Valve किन डिवाइस-स्तर के रिकॉर्ड्स को रखता है और किस आधार पर खाताधारकों को उन तक पहुँच से वंचित किया जाता है।\n\nस्मारक-पत्र पढ़ें →\n4. दो पहुँच प्रतिक्रियाएँ। एक ने डेटा को छिपाया, एक ने इसे लीक कर दिया।\n\nअक्टूबर2025: Valve के वकील ने अनुच्छेद 15 के तहत एक अनुरोध का उत्तर एक 830-पेज के परिशिष्ट के साथ दिया, जिसमें हटाने के बजाय पाठ पर लाल रंग से छिपाव किया गया है — 902,270 पात्र एक मानक एक्सट्रैक्शन टूल के साथ वापस आएं, जिसमें वे तृतीय-पक्ष पहचानकर्ता भी शामिल हैं जिन्हें बार छिपाने के लिए वहां रखे गए थे। अनुच्छेद 15(4) ही वह कारण है कि वे बार मौजूद हैं। सितंबर2026: टिकट HT-2YBP-F7JP-D4VB को तीन दिनों के बाद स्वयं-सेवा खाता डेटा पृष्ठ के लिंक के साथ बंद कर दिया गया — कोई डेटा नहीं, कोई कानूनी आधार नहीं बताया गया। अनुच्छेद 12(3) के तहत एक महीने की अवधि प्रकाशन तक समाप्त नहीं हुई थी; आपत्ति विषय-वस्तु से है।\n\nसंपादन जाँच पढ़ें →टिकट रिकॉर्ड पढ़ें →\n5. Steam की सीमा से ऊपर का बाजार\n\nSteam बाज़ार सूची को लगभग पर सीमित करता है $1,800. एक पुरानी तस्वीर में पाँच बाज़ारों में (23 सितंबर2026), 248 CS2 वस्तु श्रेणियाँ उनमें से दो या दो से अधिक द्वारा स्वतंत्र रूप से उस सीमा से ऊपर मूल्य निर्धारित किए जाते हैं, और सभी 248, Steam से अनुपस्थित हैं।; एक फैक्ट्री न्यू ड्रैगन लॉर शुरू होता है $10,941 389 62 पर सूचीबद्ध सभी पांचों में कुल प्रतियां हैं ( के 9 सितंबर के स्नैपशॉट से सेक्शन में केवल का आंकड़ा $ है)। उन कीमतों पर बेचने के लिए बाहरी मंच की आवश्यकता होती है, जबकि वस्तु हस्तांतरण अभी भी के माध्यम से होता है।10,623.95 20 13, CSFloat Steam\n\nकीमत और ट्रांसफर का पालन करें →\n6. नियम स्पष्ट है; ऑडिट ट्रेल स्पष्ट नहीं है।\n\nसब्सक्राइबर समझौता व्यक्तिगत, गैर-व्यावसायिक उपयोग के लिए Steam को आरक्षित करता है, स्पष्ट रूप से अनुमत होने के अलावा व्यावसायिक शोषण को प्रतिबंधित करता है, स्क्रिप्ट और बॉट्स को निषेध करता है, और खाते को समाप्त करने की अनुमति देता है।Valve ने उस भाषा को जुआ संचालकों पर 2016. में लागू किया। अलग से, CSFloat के इंजीनियरिंग खाते के अनुसार, Valve बंद हो गया। IEconItems_730/GetPlayerItems 2017, में मूल आइटम आईडी तक सार्वजनिक पहुँच हटाना (Valve चेंजलाग नहीं मिला)।\n\nनियम को नेटवर्क के बगल में रखें →\n2016 लिखित मांग 10 दिन\nValve में वकील द्वारा 2016 के तहत जुआ साइटों को दिए गए नोटिसों की समय सीमा। WSGC को खुली चिट्ठी: धारा 2.\n2017 / सार्वजनिक लेखा-परीक्षा पथ आईडी एक्सेस बंद\nCSFloat मूल आइटम आईडी के नुकसान को दर्ज करता है।\nपरामर्श पत्राचार डिवाइस सहसंबंध\nएक डिवाइस दर्जनों चोरी हुए खातों से जुड़ा हुआ।\nमार्ग रजिस्टर ब्लॉक हो गया, और अभी भी लॉग इन कर रहा है\nनियम: Valve की 2016 घोषणा Steam OpenID पर जुआ व्यवसाय चलाने पर प्रतिबंध लगाती है। रिकॉर्ड: 26 मुख्य डोमेन लिंक फ़िल्टर पर होते हैं, जबकि प्रत्येक के Steam लॉगिन को वह होस्ट चलाता है — csgogem.com का होस्ट 12 वर्षों से चल रहा है 6 महीनों से।\nअनुभाग 2 — खुली चिट्ठी\nवाशिंगटन राज्य जुआ आयोग को खुला पत्र\n\nदस दिन दस साल हो गए। आयोग का '2016' प्रश्न Valve को ऑपरेटर-दर-ऑपरेटर रिकॉर्ड के साथ उत्तर नहीं दिया गया है; यह पत्र उसे फाइल फिर से खोलने का अनुरोध करता है।\n\nसार्वजनिक संबोधन · वाशिंगटन राज्य जुआ आयोग\n\nदस दिन दस साल हो गए।रिकॉर्ड को फिर से खोलें।\n\nवाशिंगटन राज्य जुआ आयोग को:\n\n2016, के निदेशक डेविड ट्रुहियो ने Valve से पूछा कि उसने जुआ के लिए Steam स्किन्स के उपयोग को रोकने के लिए क्या किया है। तत्कालीन अध्यक्ष क्रिस स्टर्न्स और आयोग ने Valveद्वारा जारी वस्तुओं और Steam ट्रांसफर पर आधारित एक उद्योग का सामना किया। दोनों ने तब से आयोग में अपनी भूमिकाएँ छोड़ दी हैं। Valve को जो प्रश्न उन्होंने पूछा था, उसकी समय सीमा समाप्त नहीं हुई है।\n\nValve के मुख्य विधिक सलाहकार, कार्ल क्वैकेनबुश ने जुआ संचालकों को Steam खातों के व्यावसायिक उपयोग को बंद करने के लिए दस दिन का समय दिया। अक्टूबर में आपकी आयोग को दिए गए अपने जवाब में, Valve ने जुआ संचालित करने में सहायता करने से इनकार किया, कहा कि उसने चालीस से अधिक साइटों को रोक-और-निषेध पत्र भेजे हैं और संबंधित खाते अक्षम कर दिए हैं। इसने Steam ट्रेडिंग और OpenID को संरक्षित रखने का भी बचाव किया क्योंकि ये सेवाएँ ग्राहकों और गेम डेवलपर्स को लाभान्वित करती थीं। यह नियंत्रण की पुष्टि थी। यह परीक्षण का पात्र है, सम्मान का नहीं।\n\nहमारी समीक्षा में, Valve के उत्तर ने यह नहीं दिखाया कि इसके द्वारा अपनाई गई प्रवर्तन कार्रवाई उस नेटवर्क के पैमाने से मेल खाती है जिसका उसने वर्णन किया था। एक ऑपरेटर को भेजा गया धमकी भरा पत्र उस स्थायी प्रतिबंध के समान नहीं है जो Steam के खातों, व्यापार अवसंरचना और प्रमाणीकरण मार्गों पर लगाया जाता है और जो व्यवसाय को चलाता है। रिपोर्ट किए गए अनुमान बताते हैं 2016 के दौरान CS:GO लाउंज ने $1 बिलियन से अधिक की सट्टेबाजी हैंडल हासिल की।Valve; यह सट्टेबाजी का एक बाहरी अनुमान है, न कि ई-गेमिंग राजस्व का, और साइट का मूल स्किन-बेटिंग संचालन बाद में बंद कर दिया गया। इस पैमाने ने सत्यापनीय प्रवर्तन को अनिवार्य बना दिया।\n\nआज, Valve का अपना सदस्यता अनुबंध संचित 2026-09-21 ↗ वाणिज्यिक शोषण को प्रतिबंधित करता है, सिवाय जहाँ स्पष्ट रूप से अनुमति दी गई हो, और विशिष्ट प्रकार की स्वचालन को अलग से निषिद्ध करता है। हमारा तिथिकृत मार्ग रजिस्टर रिकॉर्ड्स OpenID द्वारा बाहरी सेवाओं के लिए लौटाए गए होस्ट्स को घोषित करते हैं। openid.realm और openid.return_to ये फ़ील्ड्स Steam को भेजी जाती हैं, न कि उससे छिपाए गए रहस्य। हमारे लिंक फ़िल्टर जाँचें ऐसे मामलों को दिखाता है जहाँ मुख्य पते के खिलाफ चेतावनी दी गई थी लेकिन उससे जुड़े लॉगिन होस्ट के खिलाफ नहीं। केवल फ़िल्टर परिणाम यह साबित नहीं कर सकता कि Valve ने लॉगिन की अनुमति दी या कोई विशेष बॉट खाता प्रतिबंध से बच निकला। यह साबित करता है कि एक होमपेज चेतावनी को पहुँच के बारे में एक पूर्ण उत्तर के रूप में प्रस्तुत नहीं किया जा सकता।\n\nउपयोगी, वैध Steam ट्रेडिंग और OpenID कार्यों की मौजूदगी भी यह नहीं बता सकती कि प्रतिबंधित ऑपरेटरों को वास्तव में बाहर रखा गया था या नहीं। Valve के अपने नियम स्पष्ट अपवादों की अनुमति देते हैं। यदि Valve उस भेदभाव पर निर्भर करता है, तो आयोग को उससे वाणिज्यिक स्किन व्यवसायों पर लागू प्राधिकरण, खाता नियंत्रण और प्रवर्तन मानदंडों की पहचान करने तथा 2016. में जिन विशिष्ट गैर-जुआ उपयोगों का उसने हवाला दिया, उन्हें बताने के लिए कहना चाहिए। कानूनी उपयोग की मात्र संभावना दस्तावेजीकृत निषिद्ध उपयोग का उत्तर नहीं है।\n\nहम आयोग से अनुरोध करते हैं कि वह अपनी 2016 फ़ाइल की पुनः समीक्षा करे और ऑपरेटर-दर-ऑपरेटर विवरण प्रदान करे: किन Steam खातों और ट्रेडिंग बॉट्स को दस-दिवसीय नोटिस के बाद अक्षम किया गया; क्या संबंधित खाते या रिटर्न होस्ट्स की निगरानी की गई; किन ऑपरेटरों ने बाद में फिर से पहुँच प्राप्त की; कौन-सी छूटें दी गईं; और कौन से रिकॉर्ड Valve के आयोग के समक्ष दिए गए बयान का समर्थन करते हैं। जिस कानून के तहत जनता को निरीक्षण की अनुमति है, उसे प्रकाशित करें। उन अभिलेखों की तुलना वर्तमान मार्गों और Valve के बाद के हस्तक्षेपों से करें, जिनमें शामिल हैं ओपीस्किन्स इन 2018 संग्रहीत 2026-03-07 ↗.\n\nसूचना ने जुलाई 2016 में दस-दिन की समयसीमा निर्धारित की; यह निर्धारित करने के लिए दस साल पर्याप्त लंबा समय है कि क्या इसे अंजाम दिया गया था। आयोग को Valve के 2016 खाते का परीक्षण उस अवसंरचना के आधार पर करना चाहिए जो आज भी दिखाई देती है।\n\nSteamडॉसियर जांच · सार्वजनिक बयान, 20 सितंबर 2026\n\n2016 आयोग सूचना ↗ संग्रहीत 2026-05-20 ↗ · Valve का 2016 का उत्तर (दस्तावेज़ की प्रति) ↗ · Valve का 2016 ओपनआईडी स्टेटमेंट ↗ संचित 2026-09-21 ↗ · वर्तमान Steam समझौता ↗ संचित 2026-09-21 ↗ · 2016 विनिमय की समयरेखा: अनुभाग 11 →\n\nभाग A — तकनीकी अभिलेख · अनुभाग 3\nसाइट अवरुद्ध है। लॉगिन मार्ग नहीं।\n\n26 अवरुद्ध मुख्य डोमेन। प्रत्येक के पीछे की प्रमाणीकरण प्रॉक्सी, और यह कितनी देर से सक्रिय है। ये अलग-अलग प्रमाणीकरण होस्ट आकस्मिक द्वितीय पते नहीं हैं — प्रत्येक एक है Steam के लिए प्रमाणीकरण प्रॉक्सी, प्लेटफ़ॉर्म और Valve के OpenID एंडपॉइंट के बीच खड़ा है और लॉगिन को वह डोमेन अब खुले तौर पर नहीं ले जा सकता जो ब्लॉक हो चुका है।Valve ने लिंक फ़िल्टर पर फ्रंट डोर लगाया। साइन-इन प्रॉक्सी के माध्यम से चलते रहे: csgogem.com ब्लॉक है, और api.csgem.com मार्च से पंजीकृत है2014 — बारह साल और आधाउन दिनों में से प्रत्येक दिन होस्ट ने अपना होस्टनेम Valve के OpenID एंडपॉइंट पर भेजा, और Steam ने उसे सीधे लॉगिन पेज पर उपयोगकर्ता को दिखा दिया। Valve यह उस मुख्य मार्ग को दर्शाता है जिससे ये सभी मार्ग गुजरते हैं; इसे उन्हें खोजने की आवश्यकता नहीं है। यह अनुभाग यही मापता है: यह नहीं कि कोई चेतावनी मौजूद है या नहीं, बल्कि यह कि चेतावनी के पीछे का मार्ग कितने वर्षों तक खुला रहता है। 44 अलग-अलग डोमेन वाले मार्गों को रजिस्टर में, 27 में से प्रत्येक के लिए प्रकाशित प्रति-मार्ग साक्ष्य फ़ाइल के साथ — नीचे दी गई तालिका। एक उदाहरण का पालन करें, फिर सभी का मापन करें।\n\nचित्र 3.1 — दो मार्ग, खींचे गए।\n\nएक प्लेटफ़ॉर्म, एक खिलाड़ी, दो अनुरोध एक ही ब्राउज़र से निकल रहे हैं। Valve का लिंक फ़िल्टर दोनों पर लागू होता है। यह उस अनुरोध को रोकता है जिसमें लिंक होता है और उस अनुरोध को पारित करता है जिसमें लॉगिन होता है। इस अनुभाग में मापा गया सब कुछ इस बात की गिनती है कि निचला मार्ग कितनी देर तक खुला रहता है।\n\nThe player\none browser, one session\nrollbit.com\nthe platform's main domain\nrbsnin.com\nseparate authentication host\nLINK FILTER\n✕ BLOCKED\nLINK FILTER\n✓ CLEAN\nsteamcommunity.com\nOpenID endpoint · signs in\nno route\nSteam में लिंक पोस्ट किया गया — बंदलॉगिन अनुरोध — सफल19 और 21 के सुरक्षित चेक, सितंबर 2026\n\nदोनों अनुरोध Valve को दिखाई देते हैं, और केवल एक पर कार्रवाई की जाती है। लिंक फ़िल्टर एक Valve सूची है, जिसे एक Valve सेवा द्वारा जांचा जाता है। OpenID अनुरोध auth होस्ट के अपने नाम को Valve के एंडपॉइंट पर भेजता है, जो इसे सीधे लॉगिन पेज पर वापस प्रिंट कर देता है। होस्टनेम अनुरोध में वैसे भी होता है — जो अंतर है वह यह है कि इसके साथ कुछ किया जाता है या नहीं।\n\nएक मंच। दो अलग-अलग मार्ग।रोलबिट / सहेजी गई अवलोकन\nचरण 5 / 5\n\nअनुरोध Steam तक पहुँचता है। निरीक्षित मार्ग 'Steam' के लॉगिन फॉर्म तक पहुँचा। लेखकों ने लॉगिन पूरा नहीं किया। मुख्य डोमेन लिंक को ब्लॉक करने से इस निरीक्षित मार्ग को फॉर्म तक पहुँचने से नहीं रोका गया।\n\n01 लिंक फ़िल्टर जाँच\nगंतव्यrollbit.comप्लेटफ़ॉर्म का मुख्य डोमेन\nस्टीम लिंक फ़िल्टरलिंक की जाँच करेंएक अलग गंतव्य-चेतावनी प्रणाली\nसहेजा गया परिणामलिंक अवरुद्ध19 & 21 सितंबर 2026\n02 निरीक्षित साइन-इन मार्ग\nमंच परSteam के साथ साइन इन करेंप्लेटफ़ॉर्म एक OpenID अनुरोध शुरू करता है।\nअलगा प्रमाणक होस्टrbsnin.comसहेजे गए चेक में कोई लिंक फ़िल्टर ब्लॉक नहीं है।\nस्ट्रीमलॉगिन फ़ॉर्म दिखाया गयाअनुरोधित होस्ट Steam की सूचना में दिखाई देता है।\nमूल कैप्चर नोट्स, पंजीकरण तिथि और प्रोटोकॉल विवरण की जांच करें।\nValve का प्रवर्तन कैसा दिखता है\nमुख्य डोमेन: अवरुद्ध\nउपयोगकर्ता\n→\nrollbit.com\n(मुख्य डोमेन)\n↓\nस्टीम लिंक फ़िल्टर — अवरुद्ध\n\"लिंक अवरुद्ध!\" — संभावित रूप से दुर्भावनापूर्ण के रूप में चिह्नित\nrollbit.com 2026-09-19 और 2026-09-21 पर लिंक फ़िल्टर ब्लॉक लौटाया गया (अप्रमाणीकृत जाँच; कच्चा HTML और SHA-256 सुरक्षित)। एक दृश्यमान, लेखा-परीक्षण योग्य रिकॉर्ड।\nवास्तव में क्या होता है — प्रमाणीकरण\nऑथ होस्ट: अवरुद्ध नहीं\nउपयोगकर्ता\n→\nrollbit.com\nSteam के साथ साइन इन करें\n↓\nअलग ऑथ होस्ट के माध्यम से पुनर्निर्देशित करें:\nrbsnin.comलिंक फ़िल्टर: स्वच्छ\nपंजीकृत 2026-09-18T09:34:52Z (वेरिसाइन RDAP)\n↓\nSteam लॉगिन पृष्ठ सूचना (2026-09-20):\n\"Note that rbsnin.com is not affiliated with Steam or Valve\"\nSteam openid.realm ने अनुरोध प्राप्त होने पर यह सूचना प्रस्तुत की।\n↓\nSteam अलग होस्ट के लिए लॉगिन फॉर्म\nलेखकों द्वारा लॉगिन पूरा नहीं किया गया; प्रवाह 'Steam' फॉर्म तक देखा गया।\nValve प्रत्येक ऐसे अनुरोध पर return_to / realm होस्टनेम प्राप्त करता है। rbsnin.com ने 2026-09-21. पर कोई Link Filter ब्लॉक नहीं लौटाया।\nअनुरोध के अनुसार\nOpenID प्रदाता के रूप में, Steam को प्रत्येक प्रमाणीकरण अनुरोध के साथ auth होस्टनेम प्राप्त होता है: यह Valve के अपने सर्वरों पर पहुँचता है। openid.return_to और openid.realm पैरामीटर।\nसाइट द्वारा भेजा गया\nस्कैनिंग द्वारा auth होस्ट का पता नहीं चलता — प्लेटफ़ॉर्म प्रत्येक अनुरोध में इसे Steam पर भेजता है। OpenID 2.0 §9.1 के तहत। return_to यह औपचारिक रूप से वैकल्पिक है, लेकिन इसके बिना Steam लॉगिन परिणाम प्रदान नहीं कर सकता, इसलिए एक कामकाजी Steam लॉगिन के लिए यह प्रभावी रूप से आवश्यक है। Steam यहां तक कि उपयोगकर्ता को होस्टनेम भी दिखाता है (\"<host> का Steam या Valve से कोई संबंध नहीं है।\").\n14 आपका वर्ष\nयह 2026-09-21 जांच (dota2.net, पंजीकृत 2011-10-29) पर अभी भी Steam लॉगिन्स ले जाने वाले सबसे पुराने auth होस्ट की आयु है; सबसे नया तीन दिन पुराना है (rbsnin.com)। \"0 auth hosts blocked\" आंकड़े को निष्कर्ष के रूप में न पढ़ें। एक ब्लॉक किया गया auth होस्ट प्लेटफ़ॉर्म की \"Steam से साइन इन करें\" सुविधा को पूरी तरह से बाधित कर देगा, इसलिए कार्यशील लॉगिन से बनी रजिस्ट्री में केवल वे होस्ट शामिल हो सकते हैं जिन्हें कभी ब्लॉक नहीं किया गया। मायने रखने वाला आंकड़ा ब्लॉक की संख्या नहीं है — बल्कि यह है कि मुख्य डोमेन लिंक फ़िल्टर में कितने वर्षों तक रहा, जबकि उसके बगल वाला लॉगिन चलते रहे।\nअलग-डोमेन प्रमाणन होस्ट: पंजीकरण तिथि बनाम मुख्य डोमेन (30 मार्ग: 2026-09-21 ब्राउज़र ऑडिट में हल किए गए 25, साथ ही 2026-09-22 पर जोड़ा गया 5)\nमंच\tलिंक फ़िल्टर: मुख्य\tऑथ होस्ट\tलिंक फ़िल्टर: auth होस्ट\tऑथ होस्ट पंजीकृत\tनिरीक्षण का स्रोत\tसाक्ष्य फ़ाइल\nRollbit\nrollbit.com · reg. 2014-11-08\n\tBLOCKED\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\trbsnin.com\tCLEAN\n2026-09-21 · raw HTML (no Wayback snapshot)\n\t2026-09-18\n09:34:52Z, Verisign RDAP\n\tSteam login-page notice, 2026-09-20\trollbit.com.json\nSkin.Club\nskin.club · reg. 2017-09-04\n\tBLOCKED\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\tsc-auth.net\tCLEAN\n2026-09-21 · Wayback 2026-09-21\n\t2019-04-02\nRDAP\n\tSteam login-page notice\tskin.club.json\nHowl.GG\nhowl.gg · reg. 2017-03-16\n\tBLOCKED\n2026-09-18, 09-19, 09-21 · Wayback 2026-09-21\n\thowl.uno\tCLEAN\n2026-09-21 · Wayback 2026-09-21\n\t2026-08-11\nRDAP\n\tLive browser capture + supplied OpenID URL\thowl.gg.json\nDuelbits\nduelbits.com · reg. 2020-02-03\n\tBLOCKED\n2026-09-21 · Wayback 2026-09-21\n\tswitchflips.com\tCLEAN\n2026-09-21 · Wayback 2026-09-21\n\t2020-04-21\nRDAP\n\tSupplied OpenID URL\tduelbits.com.json\nCSGOFast\ncsgofast.com · reg. 2015-03-27\n\tBLOCKED\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\tsteam-login.authtofast.com\tCLEAN\nauthtofast.com, 2026-09-21 · Wayback 2026-09-21\n\t2026-06-30\nauthtofast.com, RDAP\n\tLive browser capture + supplied OpenID URL\tcsgofast.com.json\nFarmskins\nfarmskins.com · reg. 2016-03-23\n\tBLOCKED\n2026-09-19, 2026-09-21 · raw HTML\n\tsteam.kobal.cc\tCLEAN\n2026-09-19, 2026-09-21 · raw HTML\n\t2017-01-07\nkobal.cc, RDAP\n\tLive browser capture + supplied OpenID URL\tfarmskins.com.json\nCobaltLab\ncobaltlab.tech\n\tBLOCKED\n2026-09-21 · raw HTML\n\tcobaltauth.com\tCLEAN\n2026-09-21 · raw HTML\n\t2025-01-07\nRDAP\n\tSupplied OpenID URL\tcobaltlab.tech.json\nCSGO.NET\ncsgo.net · reg. 2012-07-22\n\tBLOCKED\n2026-09-21 · raw HTML\n\tcn2.easylot.net\tCLEAN\n2026-09-21 · raw HTML\n\t2016-09-03\neasylot.net, RDAP\n\tLive browser capture\tcsgo.net.json\nGGDrop\nggdrop.com\n\tBLOCKED\n2026-09-21 · raw HTML\n\tggauth.com\tCLEAN\n2026-09-21 · raw HTML\n\t2023-05-03\nRDAP\n\tSupplied OpenID URL\tggdrop.com.json\nRustChance\nrustchance.com\n\tBLOCKED\n2026-09-21 · raw HTML\n\thgfuihd.com\tCLEAN\n2026-09-21 · raw HTML\n\t2019-01-27\nRDAP\n\tSupplied OpenID URL\trustchance.com.json\nSkin.Fans\nskin.fans\n\tBLOCKED\n2026-09-21 · raw HTML\n\tauth.skinfans.com\tCLEAN\n2026-09-21 · raw HTML\n\t2018-07-16\nskinfans.com, RDAP\n\tSupplied OpenID URL\tskin.fans.json\nSkinport\nskinport.com · reg. 2018-09-05\n\tBLOCKED\n2026-09-21 · raw HTML\n\tskinport.app\tCLEAN\n2026-09-21 · raw HTML\n\t2020-06-20\nRDAP\n\tLive browser capture + supplied OpenID URL\tskinport.com.json\nSkins.Cash\nskins.cash\n\tBLOCKED\n2026-09-21 · raw HTML\n\tskinscash.live\tCLEAN\n2026-09-21 · raw HTML\n\t2019-12-05\nRDAP\n\tSupplied OpenID URL\tskins.cash.json\nTF2Hunt\ntf2hunt.com · reg. 2018-01-13\n\tBLOCKED\n2026-09-21 · raw HTML\n\trstspcl.com\tCLEAN\n2026-09-21 · raw HTML\n\t2020-08-08\nRDAP\n\tLive browser capture + supplied OpenID URL\ttf2hunt.com.json\nCSGOGem\ncsgogem.com · reg. 2016-10-16\n\tBLOCKED\n2026-09-22 · raw HTML\n\tapi.csgem.com\ncsgem.com — separate registrable domain\n\tCLEAN\n2026-09-22 · raw HTML\n\t2014-03-08\ncsgem.com, RDAP — oldest in register\n\tManual collection + Link Filter capture\tlinkfilter-2026-09-22.json\nGamdom\ngamdom.com · reg. 2016-07-29\n\tBLOCKED\n2026-09-22 · raw HTML\n\tlogin.gambldom.com\ngambldom.com — one letter off the brand\n\tCLEAN\n2026-09-22 · raw HTML\n\t2017-09-24\ngambldom.com, RDAP\n\tManual collection + Link Filter capture\tlinkfilter-2026-09-22.json\n12CS\n12cs.fail · reg. 2026-03-24\n\tBLOCKED\n2026-09-22 · raw HTML\n\tfail.games\tCLEAN\n2026-09-22 · raw HTML\n\t2021-08-24\nfail.games, RDAP\n\tManual collection + Link Filter capture\tlinkfilter-2026-09-22.json\nCSGOEmpire\ncsgoempire.com · reg. 2015-06-10\n\tCLEAN\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\tcsgoempirelogin4.com\none of ten numbered domains login1–10\n\tCLEAN\n2026-09-21 · Wayback 2026-09-21\n\t2020-07-20\n05:49:17Z, Verisign RDAP\n\tLive browser capture\tcsgoempire.com.json\nCS.MONEY\ncs.money\n\tCLEAN\n2026-09-21 · raw HTML\n\tauth.dota.trade\tCLEAN\n2026-09-21 · raw HTML\n\t2016-07-15\ndota.trade, RDAP\n\tSteam login-page notice\tcs.money.json\nCSFloat\ncsfloat.com · reg. 2021-07-11\n\tCLEAN\n2026-09-21 · raw HTML\n\tcsgofloat.com\noperator's former brand domain; separate registrable domain, not an evasion indicator\n\tCLEAN\n2026-09-21 · raw HTML\n\t2015-09-29\nRDAP\n\tLive browser capture\tcsfloat.com.json\nG4Skins\ng4skins.com\n\tCLEAN\n2026-09-21 · raw HTML\n\tauth.g4s.to\tCLEAN\n2026-09-21 · raw HTML\n\t2021-05-30\ng4s.to, RDAP\n\tSupplied OpenID URL\tg4skins.com.json\nJuice.GG\njuice.gg\n\tCLEAN\n2026-09-21 · raw HTML\n\tletmeinjuice.com\tCLEAN\n2026-09-21 · raw HTML\n\t2024-04-15\nRDAP\n\tSupplied OpenID URL\tjuice.gg.json\nMarket.CSGO\nmarket.csgo.com\n\tCLEAN\n2026-09-21 · raw HTML\n\tdota2.net\tCLEAN\n2026-09-21 · raw HTML\n\t2011-10-29\nRDAP\n\tLive browser capture + supplied OpenID URL\tmarket.csgo.com.json\nRust.TM\nrust.tm\n\tCLEAN\n2026-09-21 · raw HTML\n\tdota2.net\tCLEAN\n2026-09-21 · raw HTML\n\t2011-10-29\nRDAP\n\tSupplied OpenID URL\trust.tm.json\nCSGOLounge\ncsgolounge.com · reg. 2013-08-14\n\tCLEAN\n2026-09-22 · raw HTML\n\tdota2.net\nthird front-end on this auth host\n\tCLEAN\n2026-09-22 · raw HTML\n\t2011-10-29\ndota2.net, RDAP\n\tManual collection + Link Filter capture\tlinkfilter-2026-09-22.json\nDota2Lounge\ndota2lounge.com · reg. 2012-08-10\n\tCLEAN\n2026-09-22 · raw HTML\n\tdota2.net\nfourth front-end on this auth host\n\tCLEAN\n2026-09-22 · raw HTML\n\t2011-10-29\ndota2.net, RDAP\n\tManual collection + Link Filter capture\tlinkfilter-2026-09-22.json\nSkinBaron\nskinbaron.de\n\tCLEAN\n2026-09-21 · raw HTML\n\tskinbaron.com\nsame brand, different TLD\n\tCLEAN\n2026-09-21 · raw HTML\n\t2015-12-22\nRDAP\n\tSupplied OpenID URL\tskinbaron.de.json\nTF2Royal\ntf2royal.com · reg. 2022-08-17\n\tCLEAN\n2026-09-21 · raw HTML\n\ttf2auth.com\tCLEAN\n2026-09-21 · raw HTML\n\t2021-07-27\nRDAP\n\tLive browser capture + supplied OpenID URL\ttf2royal.com.json\nTradeit\ntradeit.gg\n\tCLEAN\n2026-09-21 · raw HTML\n\tconnect-tradeit.com\tCLEAN\n2026-09-21 · raw HTML\n\t2022-02-23\nRDAP\n\tSupplied OpenID URL\ttradeit.gg.json\nUpgrader\nupgrader.pro\n\tCLEAN\n2026-09-21 · raw HTML\n\tupgauth.space\tCLEAN\n2026-09-21 · raw HTML\n\t2026-08-14\nRDAP\n\tSupplied OpenID URL\tupgrader.pro.json\nस्रोत: steamcommunity.com/linkfilter, अनधिकृत GET, 2026-09-21, 53 होस्ट्स, 3 s रिक्ति; steam_tos_assets/linkfilter-recheck-2026-09-21.json; में कच्चा एचटीएमएल steam_tos_assets/linkfilter-raw/. पंजीकरण तिथियाँ: RDAP, steam_tos_assets/domain-registration.json. · पहले 2026-09-19 में जाँच linkfilter-all-results.json · मार्ग रिकॉर्ड दर्ज करें auth-route-audit.json · लिंक फ़िल्टर पृष्ठों के Wayback Machine, 2026-09-21, में सूचीबद्ध wayback-snapshots.json rbsnin.com के लिए कोई स्नैपशॉट मौजूद नहीं है; स्थानीय रॉ फ़ाइल ही एकमात्र रिकॉर्ड है।\n\nपंजीकरण तिथियाँ: RDAP (steam_tos_assets/domain-registry/). \"Supplied OpenID URL\" अनुरोध पैरामीटर स्थापित करता है, पूरा लॉगिन नहीं। लेखकों ने किसी भी प्लेटफ़ॉर्म पर कोई लॉगिन पूरा नहीं किया। एक अलग डोमेन अपने आप में छलावा का प्रमाण नहीं है। न ही \"0 auth hosts blocked\" कोई स्वतंत्र निष्कर्ष है: एक को ब्लॉक करने से उस प्लेटफ़ॉर्म का Steam लॉगिन टूट जाएगा, इसलिए काम कर रहे लॉगिन से बनी रजिस्ट्री में कोई ब्लॉक किया गया auth होस्ट नहीं हो सकता। महत्वपूर्ण अवलोकन जोड़ी और इसकी अवधि है — लिंक फ़िल्टर पर एक मुख्य डोमेन, एक लॉगिन डोमेन के बगल में जो वर्षों से चल रहा है। इस तालिका में 30 पंक्तियाँ हैं: 27 मार्गों में से 25, प्रत्येक मार्ग के लिए एक साक्ष्य फ़ाइल के साथ, और 2026-09-22 पर पाँच अतिरिक्त, जिनका लिंक फ़िल्टर विभाजन में कैप्चर किया गया है। linkfilter-2026-09-22.json हालाँकि यह रियायम स्वयं हाथ से एकत्रित किया गया था — उनकी पंक्तियाँ स्रोत कॉलम में ऐसा बताती हैं। दो एविडेंस-फ़ाइल राउट्स जो दिखाए नहीं गए हैं, वे हैं skinsnipe.com (auth host pricing.tradeupspy.com, पंजीकृत 2020-03-11) और csgobig.com (अधिकृत होस्ट) letmeinbig.com, पंजीकृत 2023-01-20); दोनों ने 2026-09-22, की जाँच में SHA-256 के साथ रिकॉर्ड किए गए main / CLEAN auth host को BLOCKED लौटाया। linkfilter-2026-09-22c.json, लेकिन उस बैच का कच्चा HTML प्रकाशित सेट में नहीं है, इसलिए उन्हें यहाँ नामित किया गया है, बजाय उन्हें एक ऐसी पंक्ति दिए जाने के जिसे इस तालिका की हर दूसरी पंक्ति प्रमाणित कर सकती है। रजिस्टर में शेष 12 द्वारा हाथ से एकत्रित मार्गों को इस प्रकार पहचाना गया है। मास्टर_रजिस्ट्री.जेएसओएन के अधीन realm_src: user.\n\nप्राथमिक अनुभवजन्य ऑडिट · बहु-वर्षीय तिथि सीमा\nबड़ी तस्वीर का जाल: लिंक फ़िल्टर अनुपालन दिखावा है, सुरक्षा कवच नहीं।\n\nडेस्कटॉप ब्राउज़रों पर, उपयोगकर्ता बाहरी सुरक्षा उपायों से संरक्षित होते हैं: Google Safe Browsing और Microsoft SmartScreen ज्ञात फ़िशिंग को पूर्ण-स्क्रीन लाल चेतावनियों के साथ रोकते हैं। Steam के बिग पिक्चर मोड, इन-गेम ओवरले (Shift+Tab) और Steam डेक (SteamOS) में वे सुरक्षा उपाय मौजूद नहीं हैं। एम्बेडेड ब्राउज़र शून्य एक्सटेंशन का समर्थन करता है, बाहरी सेफ़ ब्राउज़िंग इंजनों को अक्षम कर देता है, और उपयोगकर्ता के पास बचाता है केवल एक रक्षात्मक अवरोध: Valve का linkfilter अंतरकोशीय\n\nसभी चार परिणामों की तुलना करने के लिए स्वाइप करें →\n\n92.5%\n2025–2026 आधुनिक एज फ़िशिंग बिना संशोधन के पारित (37/40)\n77.5%\n2023–2024 सीएस2 युग की फ़िशिंग बिना संशोधन के पारित (31/40)\n70.0%\n2021–2022 विरासत फ़िशिंग बिना संशोधन के पारित (28/40)\n7 / 7\nजुआ मुख्यधारा अवरुद्ध (सकारात्मक नियंत्रण)\nबहु-वर्षीय दीर्घकालिक ऑडिट: 120 शुद्ध Steam फिशिंग डोमेन लाइव परीक्षण (24, 2026)\n\nयह परीक्षण करने के लिए कि क्या Valve का फ़िल्टर नए खतरों को शामिल करने में केवल धीमा है या उन पर मूल रूप से अंधा है, हमने ऑडिट किया 120 Steam-विशिष्ट फ़िशिंग डोमेन की पुष्टि तीन ऐतिहासिक समूहों के विरुद्ध steamcommunity.com/linkfilter:\n\nकोहोर्ट 1:2021–2022 (क्लासिक ट्रेड-ऑफ़र और आइटम ड्रॉप्स) — 70.0% क्लीन पास (28/40). कम्युनिटी वॉचडॉग्स द्वारा सूचीबद्ध किए जाने के 5 वर्षों बाद भी, 4 से तक, 10 की विरासत फिशिंग होस्ट्स में से 7 अभी भी बिना किसी ब्लॉक के खुले हैं।\nकोहोर्ट 2:2023–2024 (CS2 बीटा हाइप और फेक सपोर्ट अपील) — 77.5% क्लीन पास (31/40). कॉउंटर-स्ट्राइक 2 की रिलीज़ का भेष धारण करने वाले अभियान और नकली सामुदायिक अपीलें (e.g cs2-steam.com, appealsteamcommunity.help) सीधे पार हो जाइए।\nकोहोर्ट 3:2025–2026 (सर्वरलेस एज डिप्लॉयज़ और फेविकॉन क्लोन्स) — 92.5% क्लीन पास (37/40). एजवन, वर्सेल, और Cloudflare पेजेज़ (e.g) पर तैनात आधुनिक फ़िशिंग किट्स। steamgifter.online, steam-dp4lt5b8fnez.edgeone.dev) लगभग बिना किसी बाधा के गुजरें।\n\nटेलीमेट्री और देयता सुरक्षा कवच, सुरक्षा नहीं। यदि लिंक फ़िल्टर शुद्ध Steam फ़िशिंग के लिए 70% को 92.5% पर भेजता है तो यह लिंक फ़िल्टर मौजूद क्यों है? यह एक कॉर्पोरेट देयता अस्वीकरण और एक आउटबाउंड क्लिक टेलीमेट्री सेंसर के रूप में कार्य करता है। एक विनम्र तुम Steam छोड़ रहे हो। एक क्लिक करने योग्य हरे 'प्रोसीड' बटन के साथ नोटिस, Valve कानूनी दोष पीड़ित पर डालता है Steam सब्सक्राइबर एग्रीमेंट के तहत (*\"उपयोगकर्ता ने स्वेच्छा से Steam के बाहर नेविगेट किया\"*). Valve क्लिक की टेलीमेट्री एकत्र करता है, लेकिन चोरी को नहीं रोकता।\n\nफ़ैविकॉन हैश प्रूफ़: थ्रेट फ़ीड्स का शून्य अवशोषण। स्वतंत्र थ्रेट इंटेलिजेंस प्लेटफ़ॉर्म (urlscan.io, Shodan, Censys) Steam के आधिकारिक फ़ैविकॉन हैश के लिए एक सरल खोज का उपयोग करके लाइव Steam फ़िशिंग किट की पहचान करते हैं।page.favicon.hash:9f890a9debcdfccc339149a7943be9aff9e4c9203c2fa37d5671a5b2c88503ad NOT domain:*.steampowered.com). यह बुनियादी स्वचालित जाँच कुछ ही सेकंड में सक्रिय फ़िशिंग क्लस्टरों का पता लगाती है।Valve बाहरी फ़ीड्स के साथ सिंक नहीं करता, हैश-आधारित खतरे का शिकार नहीं करता, और केवल तब मैन्युअल रूप से हस्तक्षेप करता है जब नियामकों द्वारा (2016, WSGC जुआ आदेश) बाध्य किया जाए या अपने ट्रेडमार्क किए गए डोमेन स्ट्रिंग्स की रक्षा के लिए।\n\nप्राथमिक ऑडिट साक्ष्य कलाकृतियाँ: दीर्घकालिक 120-डोमेन बहु-वर्षीय ऑडिट: longitudinal-steam-phishing-audit.json · 100 समर्पित Steam फ़िशिंग नमूना: linkfilter-steam-phishing-100.json · व्यापक फीड ऑडिट (n=250): linkfilter-coverage-2026-09-22.json.\n\nCSGOEmpire — दस क्रमांकित प्रमाणीकरण डोमेनों का बैच पंजीकरण\n\nपर 2020-07-20 दस क्रमांकित डोमेन, csgoempirelogin1.com के माध्यम से csgoempirelogin10.com, पंजीकृत थे। Verisign RDAP टाइमस्टैम्प सभी दस के लिए फाइल में हैं: login1 05:49:06Z, login5 05:49:08Z, login2 05:49:11Z, login3 05:49:14Z, login4 05:49:17Z, login6 05:49:20Z, login7 05:49:23Z, login8 05:49:26Z, login9 05:49:28Z — 22 सेकंड में नौ डोमेन — और login10 at 05:56:03Z, सात मिनट बाद। यह अंतर एक ही रजिस्ट्रार के थोक संचालन के अनुरूप है।\n\nयह पैटर्न पूर्व-प्रबंधित फॉलबैक होस्ट्स के अनुरूप है; केवल login4 एक लाइव OpenID अनुरोध में यह देखा गया है। csgoempire.com और csgoempirelogin4.com दोनों ने 2026-09-21 पर लिंक फ़िल्टर में CLEAN लौटाया; CSGOEmpire जुलाई के 2016 नोटिसों की प्रेस रिपोर्टों में नामित साइटों में शामिल नहीं था।\n\n# DNS — सभी 10 सक्रिय (सितंबर 2026)\nठीक है csgoempirelogin1.com 172.67.129.43\nठीक है csgoempirelogin2.com 172.67.175.168\nठीक है csgoempirelogin3.com 188.114.96.3\nठीक है csgoempirelogin4.com 188.114.96.11 ← OpenID ट्रैफ़िक में\nठीक है csgoempirelogin5.com 172.67.160.194\nठीक है सीएसगोएम्पायरलॉगिन6–10.com Cloudflare आईपीएस\nएनएक्सडीओएमेन: csgoempirelogin11.com\nसभी 10 ने 2020-07-20 पंजीकृत किए; सभी 10 ने RDAPको टाइमस्टैम्प किया (steam_tos_assets/domain-registry/csgoempireloginN.com.rdap.json)\nनियामकों के लिए निष्कर्ष\nमुख्य डोमेन को ब्लॉक करने और auth होस्ट को अनब्लॉक करने से लॉगिन मार्ग खुला रहता है — और यह वर्षों तक खुला रहता है।\n\nमुख्य डोमेन पर लिंक फ़िल्टर ब्लॉक एक सत्यापनीय सार्वजनिक रिकॉर्ड है। auth होस्ट \"Steam के साथ साइन इन करें\" ट्रैफ़िक को संभालता है और Valve के अपने OpenID अनुरोध पैरामीटर में दिखाई देता है। 26 फ़िल्टर-स्प्लिट जोड़ों में 2026-09-21 और 2026-09-22, पर किए गए जांचों में मुख्य डोमेन ने एक लिंक फ़िल्टर ब्लॉक लौटाया, जबकि लॉगिन ले जाने वाले प्रॉक्सी ने कोई नहीं लौटाया। ऊपर दिया गया रजिस्टर उस दूसरे हिस्से को मापता है: ये होस्ट अल्पकालिक बर्नर डोमेन नहीं हैं। जाँच की तारीख तक कई डोमेन एक दशक से अधिक समय से पंजीकृत थे, और उन दिनों में से प्रत्येक दिन ऐसा दिन था जब Valve ने अपने अनुरोध पैरामीटर में होस्टनेम प्राप्त किया था। Valve ने किसी भी ऑपरेटर-वार प्रवर्तन रिकॉर्ड का प्रकाशन नहीं किया है, इसलिए सार्वजनिक डेटा से यह स्थापित नहीं किया जा सकता कि इन होस्टों पर कोई अन्य उपाय लागू किया गया था या नहीं।\n\n12 वर्ष6ह\ncsgogem.com लिंक फ़िल्टर में अवरुद्ध है।\nइसका लॉगिन होस्ट api.csgem.com होया है\n2014-03-08 से पंजीकृत है और नहीं है।\nसरल भाषा सारांश — नियामकों और न्यायालयों के लिए (विस्तारित करें)\nसरल भाषा सारांश — नियामकों के लिए\nSteam पृष्ठभूमि: ईएलएसडीए क्या है और यह यहाँ क्यों महत्वपूर्ण है\n\nSteam यह एक सॉफ्टवेयर प्लेटफ़ॉर्म है जिसे Valve कॉर्पोरेशन (बेलव्यू, वाशिंगटन, यूएसए) द्वारा संचालित किया जाता है। Steam एक डिजिटल पहचान प्रदाता के रूप में कार्य करता है: इंटरनेट पर जुआ और गेमिंग वेबसाइटें \"Sign in with Steam\" नामक एक सिस्टम का उपयोग करती हैं — यह एक बटन है जो एक वेबसाइट को यह सत्यापित करने की अनुमति देता है कि किसी आगंतुक के पास एक वास्तविक Steam खाता है। यह \"Sign in with Google\" या किसी सरकारी पहचान पत्र की जाँच के समान है: वेबसाइट उपयोगकर्ता को Steam के सर्वर पर भेजती है, Steam पुष्टि करता है कि वे कौन हैं, और Steam उन्हें वापस वेबसाइट पर भेज देता है। Valve प्रामाणिकरण प्रणाली संचालित करता है। \"Steam के साथ साइन इन करें\" के माध्यम से प्रत्येक लॉगिन Valve के अपने सर्वरों से होकर गुजरता है।\n\nValve ने क्या किया: डोमेन ब्लॉक\n\nजुलाई 2016, में, स्किन जुआ को लेकर मीडिया और कानूनी दबाव के बाद, Valve के वकील ने लगभग 23 नामक जुआ साइटों को नोटिस भेजे ( 21 जुलाई 2016 की प्रेस रिपोर्टों के अनुसार); अक्टूबर में 2016 Valve ने वाशिंगटन स्टेट गैंबलिंग कमीशन को बताया कि उसने चालीस से अधिक साइटों से संपर्क किया था। कुछ जुआ डोमेन दिखाई देते हैं Steam लिंक फ़िल्टर — एक सूची जो Steam के अंदर (चैट में, प्रोफ़ाइल पेज पर, स्टोर में) पोस्ट किए गए उनसे जुड़े किसी भी लिंक पर चेतावनी पेज दिखाती है: लिंक अवरुद्ध! लिंक फ़िल्टर एकमात्र प्रवर्तन उपाय है जिसका प्रभाव Valve के बाहर से देखा जा सकता है।\n\nउदाहरण: के लिए एक लिंक rollbit.com Steam के अंदर लिंक फ़िल्टर चेतावनी पृष्ठ उत्पन्न होता है (2026-09-19 और 2026-09-21 की जाँच की गई)। कागज़ पर, जुआ साइट अवरुद्ध है।\nप्रॉक्सी डोमेन क्या है\n\nA अलग-डोमेन प्रमाणीकरण होस्ट एक प्रमाणीकरण प्रॉक्सी है।एक दूसरा वेबसाइट पता, एक अलग पंजीकरण योग्य डोमेन पर, जिसे वही ऑपरेटर अपने उपयोगकर्ताओं और Steam के बीच रखता है, केवल \"Steam के साथ साइन इन करें\" चरण को पूरा करने के उद्देश्य से। यह लॉगिन का प्रॉक्सी करता है। उपयोगकर्ता को लगता है कि वे प्लेटफ़ॉर्म में साइन इन कर रहे हैं; Valve तक पहुँचने वाला अनुरोध प्रॉक्सी के होस्टनेम को ले जाता है, न कि प्लेटफ़ॉर्म के। आमतौर पर इसका जुआ साइट से कोई सार्वजनिक रूप से दिखाई देने वाला संबंध नहीं होता है, और यह वही पता है जो Steam उनकी पहचान की पुष्टि करने के बाद उपयोगकर्ताओं को वापस प्राप्त करता है।\n\nउदाहरण: Rollbit के तहत संचालित होता है rollbit.com, जिसे लिंक फ़िल्टर ब्लॉक करता है। Steam प्रमाणीकरण के लिए, 2026-09-20 पर देखा गया फ़्लो एक अलग पता उपयोग करता था: rbsnin.com , पंजीकृत 2026-09-18. यह पता लौटा कोई लिंक फ़िल्टर ब्लॉक नहीं 2026-09-21. पर जुआ साइट चालू रही, और इसका Steam लॉगिन फ्लो अनब्लॉक किए गए होस्ट के माध्यम से चला।\nमहत्वपूर्ण बिंदु: प्रत्येक अनुरोध में ऑथ होस्ट को Steam पर भेजा जाता है।\n\nValve इसे यह जानने के लिए स्कैन या क्रॉल करने की आवश्यकता नहीं है कि कौन से auth होस्ट्स उपयोग में हैं। Steam है। ओपनआईडी पहचान प्रदाता इन साइटों के लिए, और हर \"Steam के साथ साइन इन करें\" क्लिक Valve के अपने सर्वरों को एक GET अनुरोध भेजता है जिसमें auth होस्टनेम प्लेनटेक्स्ट में होता है। ओपनआईडी 2.0 §9.1 के तहत return_to यह फ़ील्ड औपचारिक रूप से वैकल्पिक है, लेकिन इसके बिना Steam लॉगिन परिणाम प्रदान नहीं कर सकता, इसलिए एक कामकाजी Steam लॉगिन के लिए यह प्रभावी रूप से आवश्यक है। Steam स्वयं लॉगिन पेज पर होस्टनेम प्रदर्शित करता है (\"<host> का Steam या Valve से कोई संबंध नहीं है।\").\n\n— Steam को प्राप्त होने वाले अनुरोध का स्वरूप (2026-09-20 पर Rollbit के लिए अवलोकित होस्ट के रूप में): —\nप्राप्त करें steamcommunity.com/openid/login\n&openid.mode=चेकआईडी_सेटअप\nऔर ओपनआईडी.रिटर्न_टू=https://rbsnin.com/… ← प्रभावी रूप से आवश्यक; Valve के लॉग में आता है\n&openid.realm=https://rbsnin.com ← साइट द्वारा स्व-घोषित; Steam के लॉगिन पेज पर प्रदर्शित\nयदि साइट सर्वर-टू-सर्वर सत्यापन (check_authentication) का उपयोग करती है, तो Valve का लॉग प्लेटफ़ॉर्म के सर्वर आईपी और होस्टिंग नेटवर्क को भी रिकॉर्ड करता है।\n\nइस अनुरोध से होस्टनेम निकालना एक मानक प्रक्रिया है। प्रवर्तन रिकॉर्ड — किन होस्ट्स पर कार्रवाई की गई, किन पर नहीं, और किन मानदंडों के तहत — केवल Valve की अवसंरचना में मौजूद है और प्रकाशित नहीं किया गया है।\n\nयह क्या साबित करता है\n\n1. लिंक फ़िल्टर ब्लॉक लिंक पर काम करता है, लॉगिन पर नहीं। मुख्य डोमेन को ब्लॉक करना (उदाहरण के लिए) rollbit.com) उन उपयोगकर्ताओं को एक चेतावनी दिखाता है जो Steam के अंदर लिंक पर क्लिक करते हैं। यह साइट को काम करने से, या किसी अलग पते के माध्यम से Valve की अपनी OpenID सेवा का उपयोग करने से नहीं रोकता है।\n\n2. परीक्षण किए गए प्रामाणिक होस्ट ब्लॉक नहीं थे। ऊपर दी गई तालिका में 2011 और सितंबर 2026, के बीच पंजीकृत अलग-अलग-डोमेन प्रमाणीकरण होस्ट दिखाए गए हैं, जिनमें से कई जुलाई 2016 नोटिस के कई साल बाद पंजीकृत हुए थे। 26 जोड़ों में, मुख्य डोमेन ने एक लिंक फ़िल्टर ब्लॉक लौटाया और उसके लॉगिन को ले जाने वाले प्रॉक्सी ने नहीं लौटाया (अप्रमाणीकृत जाँचें, 2026-09-21 और 2026-09-22; कच्चे उत्तर और SHA-256 सहेजे गए)। वह प्रॉक्सी उस दिन काम करना बंद कर देगी जिस दिन Valve उसे अस्वीकार कर देगा, और यही कारण है कि यहाँ माप यह है कि यह कितने समय तक चली है, न कि यह कि क्या इसे सूचीबद्ध किया गया है। Valve को इन होस्टनामों की जानकारी अपने OpenID अनुरोधों में मिलती है। सार्वजनिक डेटा से यह निर्धारित नहीं किया जा सकता कि लिंक फ़िल्टर के अलावा कोई अन्य उपाय लागू किया गया था या नहीं, क्योंकि Valve ने प्रति-ऑपरेटर प्रवर्तन का कोई रिकॉर्ड प्रकाशित नहीं किया है।\n\n3. साइटों ने Valve के बुनियादी ढांचे के माध्यम से प्रमाणीकरण जारी रखा। \"Steam के साथ साइन इन करें\" Valve की सेवा है; इसके माध्यम से हर प्रमाणीकरण एक अनुरोध है जिसे Valve प्राप्त करता है और संसाधित करता है। Valve केस कीज़ से भी राजस्व अर्जित करता है, और Steam कम्युनिटी मार्केट मार्केट के अंदर पूरा किए गए लेन-देन पर (बाहरी ट्रेड पर नहीं) लगभग 15% का संयुक्त शुल्क लेता है। लिंक फ़िल्टर एक्शन ने एक सार्वजनिक रिकॉर्ड बनाया; इसने प्रमाणीकरण संबंध में बाधा नहीं डाली।\n\nक्या ब्लॉक करना काम करता?\n\nतुलना से: जब निःशुल्क डोमेन रजिस्ट्रार Freenom ने 2023, में अपना संचालन बंद कर दिया, तो उसके डोमेन पर निर्भर फ़िशिंग अभियानों में व्यवधान आ गया। परिचालन निरंतरता अवसंरचना की स्थिरता पर निर्भर करती है।\n\nयहाँ भी वही तर्क लागू होता है। यदि Steam की OpenID प्रक्रिया में auth होस्ट को अस्वीकार कर दिया जाता है, तो प्लेटफ़ॉर्म का \"Sign in with Steam\" फ़ंक्शन तब तक टूट जाएगा जब तक एक नया होस्ट पंजीकृत नहीं हो जाता, प्रमाणपत्र जारी नहीं हो जाते और DNS प्रसारित नहीं हो जाता। उस अवधि के दौरान: डाउनटाइम।\n\nघुमाव अवरोध को व्यर्थ नहीं बनाता। यह ब्लॉकिंग को एक परिचालन लागत बना देता है। चूंकि नए होस्ट पहली बार उपयोग पर Valve के अपने अनुरोध लॉग्स में दिखाई देते हैं, इसलिए प्रतिक्रिया उस पहली बार उपयोग की गति पर चल सकती है।\n\nबैच पंजीकरण स्वयं एक संकेत है: CSGOEmpire के login1–login10 को 2020-07-20, पर पंजीकृत किया गया था, जिनमें से नौ 22 सेकंड के भीतर पंजीकृत हुए (Verisign RDAP)। प्रतिक्रिया को डोमेन-दर-डोमेन होने की आवश्यकता नहीं है; एक रजिस्ट्रार सत्र से प्राप्त क्रमिक श्रृंखला को एक श्रृंखला के रूप में पहचाना जा सकता है।\n\nसार्वजनिक रिकॉर्ड में auth होस्ट्स को ब्लॉक करने का कोई प्रयास नहीं दिखता जिसे रोटेशन द्वारा विफल किया गया हो।\nयह दिखाता है कि मुख्य डोमेन ब्लॉक हैं, जबकि प्रत्येक लॉगिन को वह प्रॉक्सी ले जा रहा था जो अभी भी चल रही है — 26 जोड़े 2026-09-22, के अनुसार, सबसे पुराना auth होस्ट पंजीकृत 12 वर्ष 6 महीने — और किसी भी ऑपरेटर के लिए कोई प्रकाशित प्रवर्तन रिकॉर्ड नहीं है।\nनियामक के लिए प्रश्न इसलिए यह है: क्या Valve ने अपनी OpenID अनुरोधों में प्राप्त auth होस्ट्स पर कोई प्रवर्तन लागू किया है, यदि किया है तो क्या?\nValve ने क्या किया — और उसने ऑथ पथ को क्यों बाधित नहीं किया\n\nनीचे दी गई तालिका प्रत्येक सार्वजनिक रूप से प्रलेखित Valve कार्रवाई को यह दर्शाती है कि क्या उसने OpenID प्रमाणीकरण प्रवेश बिंदु को प्रभावित किया। निष्कर्ष यह नहीं है कि \"Valve ने कुछ नहीं किया\" — बल्कि यह है कि सार्वजनिक रूप से प्रलेखित किसी भी कार्रवाई ने उस बिंदु को नहीं छुआ जहाँ जुआ-प्लेटफ़ॉर्म लॉगिन Valve के सर्वरों से होकर गुजरते हैं।\n\nदिनांक\tValve कार्रवाई\tप्रभावित openid.return_to मार्ग?\nJuly 2016\tPublic statement of 13 July 2016; counsel's notices to ~23 named sites (press, 21 July 2016); >40 sites contacted per Valve's October 2016 letter to WSGC\tNo. Notices and the Link Filter act on operators and links; the OpenID request path was not changed.\n2017\tClosure of IEconItems_730/GetPlayerItems (according to CSFloat's engineering account; no Valve changelog located)\tNo. Affected public item-history visibility. OpenID authentication was not modified.\n2018-03-29\tCS:GO 7-day trade lock announced (blog.counter-strike.net)\tNo. Slowed item movement; the OpenID request path was not changed.\n2022-05-10\tTrade-cancellation endpoints removed from the public Web API (user-detected; no Valve changelog — node-steam-tradeoffer-manager #325)\tNo. Closed the offer-swap tooling; OpenID authentication was not modified.\n2023-12-04\tAPI-key creation now requires mobile confirmation (steamcommunity.com/dev/apikey; no changelog)\tNo. Protected the key endpoint; the auth hosts documented here were not affected.\n2026-09-19 / 09-21\tSteam Link Filter state as observed by the authors\tNo. 14 main domains returned a block in the saved 2026-09-21 recheck — 26 split pairs in the register by 2026-09-22 — while the proxy carrying each login kept running.\nस्रोत: Valve, 13 की 7 जुलाई की प्रेस विज्ञप्ति, 2016store.steampowered.com/oldnews/22883, संग्रहीत 2026-09-21) · CSFloat: 2017 बंद होने का इंजीनियरिंग खाता (blog.csfloat.com, संग्रहीत 2026-09-21) · लिंक फ़िल्टर स्थिति: linkfilter-recheck-2026-09-21.json.\nइस निष्कर्ष को एकमात्र प्रकाशित उदाहरण से खंडित किया जा सकता है, जिसमें Valve ने OpenID अनुरोध को इसलिए अस्वीकार कर दिया क्योंकि openid.return_to एक जुआ प्राधिकरण होस्ट की ओर इशारा किया गया। सार्वजनिक अभिलेख में ऐसा कोई उदाहरण नहीं मिला है।\nदो सबसे हालिया auth-host पंजीकरण\nhowl.uno2026-08-11 (RDAP) को 2026-09-21 से 41 दिन पहले पंजीकृत किया गया था; howl.gg ने 2026-09-18,, 2026-09-19 और 2026-09-21. पर लिंक फ़िल्टर ब्लॉक लौटाया। ब्लॉक का पंजीकरण से पहले होना स्थापित नहीं है।\nrbsnin.com2026-09-18T09:34:52Z (Verisign RDAP) पंजीकृत था और इसे Steam के अपने लॉगिन-पेज नोटिस के माध्यम से 2026-09-20 पर Rollbit के Steam लॉगिन फ्लो में देखा गया; rollbit.com ने 2026-09-19 और 2026-09-21, पर लिंक फ़िल्टर ब्लॉक लौटाया, जबकि rbsnin.com ने नहीं लौटाया।\nऊपर दी गई तालिका में प्रत्येक होस्ट को Valve के प्रमाणीकरण सर्वरों पर as के रूप में भेजा जाता है। openid.realm हर लॉगिन प्रयास पर।\nपूर्ण मार्ग-वार डेटा और लिंक फ़िल्टर निर्णय: उपरोक्त अनुभाग 3 में तालिका; कच्चे परिणाम linkfilter-recheck-2026-09-21.json और linkfilter-all-results.json.\nपद्धति — मार्ग और लिंक फ़िल्टर की गिनती कैसे स्थापित की गई\n1. डोमेन समाधान\n2026-09-21 ऑडिट ने 189 द्वारा अनुरोधित प्लेटफ़ॉर्मों में से 78 को हल किया: 33 20 अपने स्वयं के होस्टनेम पर प्रमाणीकरण करें और अपने स्वयं के सबडोमेन पर ईमेल — प्रत्यक्ष प्रमाणीकरण, और इनमें से कोई भी अलग-डोमेन मार्ग के रूप में नहीं गिना जाता। शेष 25 एक अलग पंजीकरण योग्य डोमेन के माध्यम से प्रमाणीकरण करें24 विशिष्ट होस्टनामों पर (dota2.net साझा है market.csgo.com और rust.tm): 10 लाइव ब्राउज़र कैप्चर द्वारा स्थापित, 3 Steam के अपने लॉगिन-पेज नोटिस द्वारा, 12 एक प्रदान किए गए OpenID URL द्वारा। लाइव रजिस्टर (मास्टर_रजिस्ट्री.जेएसओएन, 2026-09-22) इसे तक विस्तारित करता है 44 अलग-डोमेन मार्ग26 फ़िल्टर-स्प्लिट जोड़े (मुख्य डोमेन BLOCKED, प्रमाणन होस्ट CLEAN) और 18 अतिरिक्त मार्ग जिन्हें मुख्य-डोमेन विभाजन के बिना चलाया जाता है। 44, 27 प्रति मार्ग साक्ष्य फ़ाइल साथ रखें; अन्य 17 हाथ से एकत्र किए गए थे और चिह्नित हैं realm_src: user रजिस्टर में। उन सत्रह में से पाँच — csgogem.com, gamdom.com, 12cs.fail, csgolounge.com और dota2lounge.com — को 2026-09-22 पर लिंक फ़िल्टर कैप्चर के साथ दोनों होस्ट्स (कच्चा HTML + SHA-256 में) जोड़ दिया गया। linkfilter-2026-09-22.json), इसलिए विभाजन स्वयं स्पष्ट है, भले ही डोमेन हाथ से एकत्रित किया गया हो; वे उपरोक्त तालिका में साक्ष्य-फ़ाइल मार्गों के साथ दिखाई देते हैं। tfauth.com (tf2easy.com) को 2026-09-22: से हटा दिया गया था, जैसे arena.fragnet.net; कोई भी सत्यापनीय लिंक इसे इसकी मूल साइट से नहीं जोड़ता। गिनती प्रकाशित से पुनः प्राप्त की जा सकती है। auth-route-audit.json (2026-09-21 की एक श्रृंखला) एक नियम के अनुसार: एक प्लेटफ़ॉर्म तभी गिना जाता है जब इसके अवलोकित Steam OpenID होस्ट का डोमेन स्वयं प्लेटफ़ॉर्म के डोमेन से अलग हो।\n2. Steam लिंक फ़िल्टर स्थिति\nके माध्यम से परीक्षण किया गया steamcommunity.com/linkfilter/?url=https://[domain], अनाधिकृत, 2026-09-19 और 2026-09-21 पर; SHA-256. के साथ कच्चा HTML सहेजा गया। मुख्य डोमेन और auth होस्ट के लिए स्थिति अलग-अलग दर्ज की गई। एक वर्गीकरणकर्ता सामान्य \"आप Steam छोड़ रहे हैं\" सूचना (साफ) को \"लिंक अवरुद्ध! ... संभावित रूप से दुर्भावनापूर्ण के रूप में चिह्नित\" पृष्ठ (BLOCKED); एक google.com नियंत्रण पुष्टि करता है कि दोनों को एक साथ नहीं मिलाया गया है। इस परीक्षण का एक पूर्व प्रमाणित संस्करण, जिसने उस नियंत्रण सहित हर डोमेन के लिए \"blocked\" लौटाया था, खारिज कर दिया गया था — यह जांच स्क्रिप्ट में एक अमान्य सत्र कुकी के कारण हुआ था, वास्तविक परिणाम नहीं।\n3. ऑथ होस्ट का अवलोकन\nलाइव कैप्चर: एक Playwright ब्राउज़र ने प्रत्येक प्लेटफ़ॉर्म के लॉगिन फ़्लो और openid.return_to hostname को इंटरसेप्ट की गई रिक्वेस्ट से पढ़ा गया था। लॉगिन-पेज सूचना: hostname को Steam के अपने \" से पढ़ा गया था।<host> का Steam या Valve से कोई संबंध नहीं है।\" टेक्स्ट, जिसे Steam रेंडर करता है openid.realm (rbsnin.com, sc-auth.net, auth.dota.trade). प्रदान किया गया URL: लेखकों को दिया गया एक Steam लॉगिन फॉर्म URL; यह अनुरोध पैरामीटर स्थापित करता है, पूरा लॉगिन नहीं। किसी भी प्लेटफ़ॉर्म पर कोई लॉगिन पूरा नहीं किया गया।\n4. कवरेज — जो निपटाया नहीं गया, और यह क्यों मायने रखता है\n189 प्लेटफ़ॉर्मों में से, 110 कोई स्थापित मार्ग नहीं हुआ और एक लागू नहीं था (189 − 78 − 1). इस दस्तावेज़ में इनमें से कोई भी शामिल नहीं है. ऑडिट फ़ाइल से 110, का ब्रेकडाउन: 22 बॉट चुनौतियाँ, 14 टाइमआउट, 12 HTTP त्रुटियाँ और 10 नेविगेशन त्रुटियाँ — पर्यवेक्षक लॉगिन फ़्लो तक नहीं पहुँच सका, हालांकि इनमें से अधिकांश साइटें सामान्य ब्राउज़र में ठीक से खुलती हैं; 20 ने लैंडिंग पेज पर कोई Steam लॉगिन नियंत्रण नहीं दिखाया; 16 एक लॉगिन फ्लो तक पहुँचा जो किसी होस्ट पर रिज़ॉल्व नहीं हो सका; 11 डोमेन DNS में रिज़ॉल्व नहीं हुए; 5 एक सहमति दीवार पर रुक गया। नीचे दिया गया रजिस्टर उसी 110 को अलग तरह से विभाजित करता है: DNS में रिज़ॉल्व न होने वाले 11 को अलग से सूचीबद्ध किया गया है, जैसे हटाया गया · NXDOMAIN, और एक अप्रासंगिक प्रविष्टि बाकी के साथ जुड़ जाती है। 189 प्लेटफ़ॉर्म ऑडिट किए गए, 11 को दोनों रिज़ॉल्वर्स से एक निश्चित NXDOMAIN पर हटा दिया गया, 178 रखे गए (platform-audit.json, platforms-removed.json). 137 नामकरण पैटर्न से अनुमानित किए गए auth डोमेन, 2026-09-19 के डेटा से हटा दिए गए — कभी देखे नहीं गए, इसलिए कोई सबूत नहीं। तीन अनुमानों का OpenID URL द्वारा खंडन किया गया: buff.163.com, gamerpay.gg और csgoluck.com सीधे प्रमाणीकरण करते हैं, जबकि अनुमान buffauthproxy.163.com, gamerpayredirect.io और lucklogin.app थे। हटाई गई प्रविष्टियाँ प्रकाशित ऑडिट फ़ाइल में सूचीबद्ध हैं।\n25 एक मंजिल है, छत नहीं। 78 प्लेटफ़ॉर्मों में जिनका समाधान हुआ, 25 ने एक अलग डोमेन का उपयोग किया और 53 ने नहीं किया। उस अनुपात से अनसुलझे 110 के बारे में कुछ भी मान्य नहीं किया गया है, और इस दस्तावेज़ में कहीं भी उससे कोई अनुमान नहीं लगाया गया है। प्रत्येक को कोई व्यक्ति साइट खोलकर \"Sign in with Steam\" पर क्लिक करके हल कर सकता है: auth होस्टनेम उस Steam पेज के URL में होता है जो लोड होता है।\nइस अनुभाग का उद्देश्य: एक स्वतंत्र पर्यवेक्षक को 189 प्लेटफ़ॉर्म को हल करने के लिए एक ब्राउज़र और बहुत धैर्य की आवश्यकता होती है, और उसे 78. Valve के लिए एक डेटाबेस क्वेरी की आवश्यकता होती है। हर प्लेटफ़ॉर्म जो \"Sign in with Steam\" का उपयोग करता है — हल किए गए और अनसुलझे दोनों — भेजता है openid.realm प्रत्येक लॉगिन पर Valve के प्रमाणीकरण एंडपॉइंट पर। इस तालिका में यह अंतर इसलिए है क्योंकि लेखक सिस्टम के बाहर हैं। यह Valve के लिए मौजूद नहीं है।\nनिरीक्षित प्रॉक्सी होस्टनाम हैं auth-route-audit.json. डोमेन पंजीकरण की तारीख RDAP (Verisign) / IP2WHOIS से। लिंक फ़िल्टर के परिणामस्वरूप linkfilter-all-results.json.\nस्पष्टता के लिए उपमा\n\nकल्पना कीजिए कि एक लाइसेंस प्राप्त टैक्सी कंपनी को नियामकों द्वारा बताया जाता है कि वह अब अपने पंजीकृत मेन स्ट्रीट पते से संचालन नहीं कर सकती है। कंपनी मेन स्ट्रीट से साइन हटा देती है। उस साइन को हटाने का दस्तावेजीकरण किया जाता है। हालांकि, वही कंपनी एक साइड स्ट्रीट पते को खोलती है — एक अलग नाम के तहत पंजीकृत — और वहां से अपना संचालन जारी रखती है। नियामक उस केंद्रीय प्रेषण प्रणाली को संचालित करते हैं जिसका उपयोग दोनों पतों से हर टैक्सी करती है। हर सवारी अनुरोध में \"साइड स्ट्रीट से पिक-अप करें\" दिखाता है। नियामक साइड स्ट्रीट का लाइसेंस कभी रद्द नहीं करते। मेन स्ट्रीट के साइन को हटाना ही एकमात्र प्रवर्तन था। टैक्सी कंपनी ने कभी संचालन बंद नहीं किया।\n\nभाग A — तकनीकी अभिलेख · अनुभाग 3.1\nSteam के अंदर, Valve की सूची ही एकमात्र सूची है।\n\nSteam क्लाइंट में किसी लिंक पर क्लिक करने पर, इन-गेम ओवरले या बिग पिक्चर मोड उपयोगकर्ता के ब्राउज़र में नहीं खुलता। यह Steam के अपने एम्बेडेड ब्राउज़र के भीतर रेंडर होता है — जहाँ ब्राउज़र द्वारा लागू की जाने वाली चेतावनी परतें मौजूद नहीं होतीं। लिंक फ़िल्टर कई सुरक्षा उपायों में से एक नहीं है। यह संपूर्ण सुरक्षा है।\n\nएक सामान्य ब्राउज़र मेंतीन स्वतंत्र परतें\nGoogle Safe Browsingगूगल की फ़िशिंग और मैलवेयर सूचियों में शामिल होस्ट्स के लिए एक पूर्ण-पृष्ठ इंटरस्टीशियल, जो लगातार अपडेट होता रहता है और जिस साइट पर जाया जा रहा है, उससे स्वतंत्र है।\nएंटीवायरस ब्राउज़र एक्सटेंशनअधिकांश उपभोक्ता एंडपॉइंट उत्पाद एक ब्राउज़र ऐड-ऑन के साथ आते हैं जो गंतव्य की जाँच विक्रेता की अपनी प्रतिष्ठा सूची के विरुद्ध करता है।\nएंडपॉइंट HTTPS निरीक्षणजहाँ उत्पाद TLS-निरीक्षण करता है, पृष्ठ की सामग्री उपयोगकर्ता तक पहुँचने से पहले स्कैन की जाती है।\nSteam क्लाइंट, ओवरले और बिग पिक्चरएक परत\nGoogle Safe Browsingउपस्थित नहीं। इस जाँच के लिए Google API कुंजियों की आवश्यकता होती है जो एम्बेडेड Chromium बिल्ड्स में प्रदान नहीं की गई हैं; जहाँ ये अनुपस्थित होती हैं, Chromium की अपनी डिज़ाइन दस्तावेज़ीकरण में यह दर्ज है कि Safe Browsing हैंडलर अनुरोध श्रृंखला में कभी भी नहीं जोड़ा जाता।\nएंटीवायरस ब्राउज़र एक्सटेंशनउपस्थित नहीं। Steam का रेंडरर उपयोगकर्ता का ब्राउज़र नहीं है और यह उपयोगकर्ता की ब्राउज़र प्रोफ़ाइल से कोई एक्सटेंशन लोड नहीं करता, इसलिए पेज पर कोई ऐड-ऑन नहीं चलता।\nएंडपॉइंट HTTPS निरीक्षणउत्पाद-निर्भर। ट्रैफ़िक एक कोड-साइन्ड Valve प्रक्रिया के भीतर समाप्त होता है, मान्यता प्राप्त ब्राउज़र के बजाय, और कई एंडपॉइंट उत्पाद हस्ताक्षरित अनुप्रयोगों को TLS निरीक्षण से छूट देते हैं।\nSteam लिंक फ़िल्टरValve की अपनी ब्लॉकलिस्ट, जिसे तब परखा जाता है जब कोई लिंक Steam इकोसिस्टम से बाहर जाता है। यह एकमात्र जाँच है जो चलती है — और ऊपर दी गई तालिका इस बात का रिकॉर्ड रखती है कि यह इस अनुभाग में दस्तावेजीकृत auth होस्ट्स के लिए क्या लौटाती है।\nएक ऐसा परीक्षण जिसे कोई भी पाठक चला सकता है, और यदि यह विफल हो जाता है तो निष्कर्ष अमान्य हो जाता है।\n\nGoogle द्वारा प्रकाशित Safe Browsing परीक्षण URL में से एक खोलें (testsafebrowsing.appspot.comChrome में: एक पूरे पेज का लाल इंटरस्टिशियल दिखाई देता है। उसी URL को Steam चैट संदेश से खोलें, ताकि यह Steam क्लाइंट या ओवरले में रेंडर हो: कोई इंटरस्टिशियल नहीं दिखता। Steam द्वारा उत्पन्न की जा सकने वाली एकमात्र चेतावनी इसका अपना लिंक फ़िल्टर पेज है, और वह भी केवल Valve की सूची में शामिल होस्ट्स के लिए।\n\nValve का अपना बग-बाउंटी रिकॉर्डएक परत पहले ही आ चुकी है — Valve के अपने रिकॉर्ड पर\n\nयदि लिंक फ़िल्टर ही एकमात्र जाँच है जो क्लाइंट के भीतर चलती है, तो इसकी विफलता के तरीके कोई गौण समस्या नहीं हैं। Valve के HackerOne कार्यक्रम पर दो रिपोर्टें, दोनों स्वीकार की गईं, दोनों का समाधान हो चुका है, और दोनों को पूरी तरह से प्रकट किया जा चुका है:\n\n#291750संग्रहीत 2025-11-16 ↗ओपन रीडायरेक्ट · मीडियम\nलिंक फ़िल्टर सुरक्षा बाईपास\n\n19 नवंबर 2017, में रिपोर्ट किया गया, हल किया गया, प्रकट किया गया 9 मई 2018.। रिपोर्ट का अपना प्रूफ-ऑफ़-कॉन्सेप्ट: आइडियोग्राफिक पूर्ण विराम का प्रतिस्थापन। 。 (%E3%80%82) होस्टनेम में बिंदु के लिए — it is possible to bypass the blocking. अंतःकोशिकीय यह अनुभाग जिसके बारे में है, वह प्रकट नहीं हुआ।\n\n#1079561संचित 2026-09-24 ↗सूचना प्रकटीकरण · उच्च\nबिग पिक्चर वेब ब्राउज़र लॉगिन कुकीज़ लीक करता है और संवेदनशील जानकारी का खुलासा करता है (जिससे खाते पर कब्ज़ा हो सकता है)\n\n15 जनवरी 2021, में रिपोर्ट किया गया, समाधानित और प्रकटीकृत 21 सितंबर 2021. Valve की अपनी गंभीरता रेटिंग उच्च है, और शीर्षक परिणाम बताता है। प्रकटीकृत रिकॉर्ड में शीर्षक, रेटिंग और तिथियाँ शामिल हैं; तकनीकी विवरण प्रकाशित पेलोड में नहीं है, इसलिए यहाँ उससे और कुछ उद्धृत नहीं किया गया है।\n\nलेखकों का पठन, न कि किसी भी रिपोर्ट का निष्कर्ष: दोनों एक ही द्वार के दोनों ओर बैठे हैं। एक चेतावनी है जो गंतव्य खुलने से पहले प्रकट नहीं होने पर दी जाती है; दूसरी वह सत्र है जो क्लाइंट को तब छोड़ देता है जब उसमें कोई पृष्ठ खुल जाता है। एक चुराए गए सत्र के बाद जो क्रम आता है — बिना किसी संकेत के कुंजी पंजीकृत हो जाना, वास्तविक व्यापार रद्द हो जाना, एक प्रतिलिपि क्लोन को भेज दी जाना — वह पैटर्न है जो में निर्धारित किया गया है। धारा 5 के लिए धारा 8दोनों रिपोर्टें बंद हैं; किसी को भी लाइव भेद्यता के रूप में पेश नहीं किया गया है। वे जो स्थापित करते हैं वह संकीर्ण है लेकिन पर्याप्त: एकमात्र शेष परत को Valve के अपने रिकॉर्ड के अनुसार पहले भी दरकिनार किया जा चुका है।\n\nस्रोत: प्रत्येक रिपोर्ट के लिए HackerOne प्रकटीकरण रिकॉर्ड, 2026-09-22 से प्राप्त — संख्या, शीर्षक, टीम, कमजोरी, गंभीरता, रिपोर्ट और प्रकटीकरण की तिथियाँ तथा स्थिति जैसा कि HackerOne द्वारा प्रकाशित किया गया है। पुनर्प्राप्ति रिकॉर्ड: hackerone-reports.json. यहाँ कोई इनाम राशि नहीं बताई गई है; प्राप्त किए गए प्रकटीकृत रिकॉर्ड में भी कोई राशि नहीं मिलती।\n\nमैदानी अवलोकन · PhishDestroyपहचानों से जो आम तौर पर एक अभियान समाप्त हो जाता है, वे इन अभियानों को समाप्त नहीं कर पाईं।\n\nहमने देखा कि फ़िशिंग होस्ट्स ट्रैफ़िक खींचते रहे, जबकि वे कैरी कर रहे थे। 20 या अधिक विक्रेता पहचानवेब या ईमेल के माध्यम से पहुँचाया गया एक अभियान उस राज्य में कुछ ही दिनों में समाप्त हो जाता है — ब्राउज़र और एंटीवायरस दोनों उन निर्णयों पर अमल करते हैं। Steam के अंदर ऐसा नहीं होता। निर्णय पूरे समय मौजूद थे। क्लाइंट में कभी कुछ भी नहीं पूछा गया।\n\nएंटीवायरस इंस्टॉल किए गए माइनर के लिए इसका क्या मतलब है\n\nवह किसी भी चेतावनी को अनदेखा नहीं करता और कुछ भी अक्षम नहीं करता। एक संदेश 'Steam' में आता है — एक मुफ्त चाकू, एक दोस्त की टीम के लिए वोट — और पेज 'Steam' में खुलता है। वह कभी ब्राउज़र नहीं खोलता, इसलिए ब्राउज़र कभी उसकी रक्षा नहीं करता। उसका एंटीवायरस चल रहा है और शायद पहले से ही उस डोमेन को खतरनाक मान चुका है; उससे कभी पूछा ही नहीं जाता। हर वह चेतावनी जो उसे पहले ही रोक सकती थी, पहले से मौजूद है। इनमें से कोई भी उस तक नहीं पहुँचती। वह मानता है कि वह कभी Steam नहीं छोड़ा, और उसने नहीं छोड़ा।\n\nयह गिवअवे फिशर का आविष्कार नहीं है — मुफ्त Valve आइटम ही स्किन और जुआ साइटों का विज्ञापन करने का तरीका हैं, और यही वजह है कि यह संदेश सामान्य लगता है। शिकायतें: प्रवर्तन अभिलेखागार. आयु और बच्चों का डेटा: धारा 17.\n\nस्रोत: Steam क्रोमियम एम्बेडेड फ्रेमवर्क के माध्यम से वेब सामग्री प्रस्तुत करता है। steamwebhelper प्रक्रिया — देखें DARKNAVY का 27 का तकनीकी विश्लेषण, 6 जून 2024 ↗ और Valve का अपना Steam क्लाइंट बीटा फोरम ↗ संग्रहीत 2025-08-04 ↗किसी भी CEF संस्करण पर निर्भर नहीं किया जाता: एम्बेडेड क्रोमियम क्रोम नहीं है और इसमें क्रोम की कोई भी गूगल सेवाएँ शामिल नहीं हैं। API कुंजियों के बिना सुरक्षित ब्राउज़िंग: क्रोमियम डिज़ाइन दस्तावेज़ ↗ संग्रहीत 2026-08-21 ↗, क्रोमियम API कुंजी ↗ संचित 2026-08-30 ↗ (\"Chrome द्वारा उपयोग किए जाने वाले कई Google APIs Google के लिए विशिष्ट हैं और व्युत्पन्न उत्पादों में उपयोग के लिए अभिप्रेत नहीं हैं\"), और अन्य अनकीड बिल्ड्स में भी यही प्रभाव — होमब्रू कास्क #193814 ↗. परीक्षण यूआरएल: testsafebrowsing.appspot.com ↗.\n\nदो अलग-अलग घड़ियाँ\nडोमेन की आयु।निरीक्षण की तिथि।\n\nएक रजिस्ट्री निर्माण तिथि यह स्थापित करती है कि एक डोमेन कब पंजीकृत किया गया था। एक दिनांकित OpenID रिकॉर्ड उस रिकॉर्ड में रिटर्न होस्ट को स्थापित करता है। पूर्व वाला रिकॉर्ड उत्तर वाले रिकॉर्ड से पहले के वर्षों को भर नहीं सकता।\n\nपूर्ण रजिस्टर एक अलग पंजीकरण योग्य डोमेन, साइट का अपना सबडोमेन और एक सीधा मार्ग अलग करता है। प्रत्येक पंक्ति अपने स्रोत और DNSपरिणाम से जुड़ी होती है।\n\nडोमेन रजिस्टर का निरीक्षण करें →· रजिस्ट्री तिथियाँ डाउनलोड करें ↗· अवलोकन को दोहराएँ ↗\n\nभाग A — तकनीकी अभिलेख · अनुभाग 4\nएक एंडपॉइंट बंद हो गया। सार्वजनिक ट्रेसिंग ने एक कुंजी खो दी।\nप्रसंग और स्रोत सीमाएँ\n\nSteam बदलाव भेजे गए जिन्होंने आइटम एसेट आईडी की सार्वजनिक दृश्यता को हटा दिया और API इन्वेंटरी तक पहुंच को प्रतिबंधित कर दिया। प्रभाव: सार्वजनिक डेटा से किसी विशिष्ट आइटम को उसकी मूल एसेट आईडी से ट्रेस करना असंभव हो गया। नीचे बताया गया है कि पहले क्या संभव था, बाद में क्या संभव नहीं रहा, और इससे पीड़ित को यह साबित करने में क्या-क्या खर्च आता है कि उनकी संपत्ति कहां गई। CSFloat के इंजीनियरिंग खाते के अनुसार तारीख 2017 है; किसी भी Valve चेंजलाग का पता नहीं चला है। यह क्रम — जुलाई 2016 जुआ बयान के लगभग एक साल बाद — एक खोज प्रश्न है, न कि कोई निष्कर्ष। आइटम रिकॉर्ड स्वयं Valve की प्रणालियों में बने हुए हैं; बाहरी जांचकर्ताओं ने मूल-आईडी श्रृंखला तक पहुंच खो दी है, जबकि फ्लोट, सीड और पेंट पहचानकर्ता केवल आंशिक मिलान की अनुमति देते हैं।\n\nValve का नियम लागू होता है: Steam सहायता आपके खाते से बाहर गए आइटमों को पुनर्स्थापित नहीं करती है, और यह साबित करने का बोझ आप पर है कि क्या हुआ। रिकॉर्ड: 2017Valve ने उस एंडपॉइंट को बंद कर दिया था जिसमें मूल आइटम आईडी होती थीं। इसके पहले कोई भी पीड़ित के खाते से चोरी की गई स्किन को मार्केटप्लेस बॉट तक ट्रैक कर सकता था। इसके बाद Valve के बाहर कोई भी ऐसा नहीं कर सकता। पीड़ित से जो प्रमाण माँगा जा रहा है, वह वही प्रमाण है जिसे बंद कर दिया गया था। — और यह अभी भी मौजूद है, Valve के अंदर।\n\nब्लैकआउट-पूर्व युग\n\nऐतिहासिक रूप से, Steam पर उत्पन्न प्रत्येक आभासी वस्तु के पास एक वैश्विक रूप से अद्वितीय, अपरिवर्तनीय संपत्ति आईडीतीसरे पक्ष के OSINT डेटाबेस इन आईडीज़ को अनुक्रमित कर सकते हैं। यदि किसी उपयोगकर्ता का कोई आइटम हाईजैक हो जाता है, तो जांचकर्ता उस विशिष्ट संपत्ति की वंशावली का पता लगा सकते हैं, जब वह हाईजैक करने वाले के मध्यवर्ती खाते से किसी मार्केटप्लेस या जुआ साइट के स्टोरेज खातों में स्थानांतरित होती है।\n\nपहले: कोई भी सार्वजनिक डेटा का उपयोग करके पीड़ित के खाते से मध्यवर्ती खातों के माध्यम से एक मार्केटप्लेस या कैसीनो स्टोरेज बॉट तक किसी आइटम का पता लगा सकता था।\nबदलाव के बाद\n\nCSFloat की इंजीनियरिंग रिपोर्ट के अनुसार, Valve ने 2017 में एंडपॉइंट बंद कर दिया और मूल आइटम आईडी बाहरी पक्षों के लिए उपलब्ध नहीं रहीं। इस परिवर्तन के कारण के बारे में कोई Valve बयान नहीं मिला है। उसी अवधि में, बड़े पैमाने पर आइटम स्थानांतरित करने वाले वाणिज्यिक बॉट खातों के खिलाफ कोई प्रकाशित कार्रवाई भी नहीं मिली है।\n\nचाहे इसका कोई भी कारण हो, इस बदलाव ने सार्वजनिक हिरासत श्रृंखला को तोड़ दिया। एक पीड़ित अब सार्वजनिक डेटा से मूल-आईडी श्रृंखला को पुनः उत्पन्न नहीं कर सकता, जिससे यह दिखाया जा सके कि कोई विशिष्ट चोरी की गई वस्तु किसी विशिष्ट बाज़ार या कैसीनो के माध्यम से निपटाई गई थी। वस्तु के रिकॉर्ड अभी भी Valve की प्रणालियों में मौजूद हैं; सार्वजनिक डेटा पर काम करने वाले सार्वजनिक, शोधकर्ता और कानून प्रवर्तन उन तक नहीं पहुँच सकते।\n\nAFTER: सार्वजनिक डेटा से किसी विशिष्ट आइटम को उसकी मूल एसेट आईडी द्वारा ट्रेस करना अब संभव नहीं है। 2017 के बाद स्थानांतरित किसी आइटम की मूल-आईडी चेन ऑफ़ कस्टडी केवल Valve की अवसंरचना के भीतर मौजूद है; ऐसा कोई रिकॉर्ड सार्वजनिक रूप से उपलब्ध नहीं है। फ्लोट, सीड और पेंट पहचानकर्ता केवल आंशिक, संभाव्य मिलान की अनुमति देते हैं।\nआईईकॉनआइटम्स_730\nप्राप्त करें/IEconItems_730/GetPlayerItems/v1/\nट्रेस करने योग्य पेलोड (प्री-पैच)\n\"id\": \"14892281934\",\n\"original_id\": \"11829910211\",\nस्थिति: पीड़ित बॉट खातों के माध्यम से वस्तु की उत्पत्ति का पता लगा सकता है।\nअस्पष्ट पेलोड (पैच के बाद)\nवर्तमान\n\"id\": \"HIDDEN_BY_PRIVACY_SETTINGS\",\n\"original_id\": \"NULL\",\nस्थिति: बाहरी पक्ष अब सार्वजनिक डेटा से मूल एसेट आईडी के माध्यम से आइटम की वंशावली का पता नहीं लगा सकते।\nसाक्ष्य पर प्रभाव: बदलाव के बाद, सार्वजनिक डेटा के माध्यम से किसी पीड़ित के खाते से एक विशिष्ट आइटम को उसकी मूल एसेट आईडी से मार्केटप्लेस या कैसीनो बॉट में ट्रैक करने के लिए आवश्यक जानकारी अब उपलब्ध नहीं थी। आंतरिक रिकॉर्ड अभी भी Valve पर मौजूद हैं; सार्वजनिक डेटा के आधार पर काम करने वाला कोई पीड़ित, शोधकर्ता या जांचकर्ता मूल आईडी श्रृंखला को पुन: उत्पन्न नहीं कर सकता (float, seed और paint पहचानकर्ता केवल आंशिक मिलान की अनुमति देते हैं)।\n\nस्रोत: CSFloat इंजीनियरिंग खाता 2017 के बंद होने का IEconItems_730/GetPlayerItems — blog.csfloat.com/फ़्लोटडीबी-आइटम-ट्रैक-कैसे-करता-है (संग्रहीत 2026-09-21) · दिखाए गए पेलोड क्षेत्र के आकार का एक उदाहरण हैं, कैप्चर किए गए प्रतिक्रियाएँ नहीं · क्लोज़र के लिए कोई Valve चेंजलाग नहीं मिला है।\n\nभाग A — तकनीकी अभिलेख · अनुभाग 5\nएक सत्र। उपयोगकर्ता को जितना दिखता है उससे अधिक पहुँच।\nप्रसंग और स्रोत सीमाएँ\n\nValve की API-key आर्किटेक्चर, जैसा कि यह 2023 परिवर्तनों से पहले थी, बेसलाइन उद्योग मानकों (OWASP ASVS, NIST SP 800-63B) से विचलित थी और यह स्वचालित इन्वेंटरी-चोरी शिकायतों में वर्णित तंत्र है, जो साक्ष्य अभिलेखागार (अनुभाग 6–8) में संरक्षित हैं।\n\nValve का नियम लागू हुआ: खाता धारक ने कुंजी बनाई, शर्तों को स्वीकार किया, और हानि वहन करता है — संग्रहीत अस्वीकृतियों में यही उत्तर है। रिकॉर्ड: 2023 दिसंबर तक केवल एक चोरी की गई सत्र कुकी ही उस कुंजी को पंजीकृत कर सकती थी। कोई पासवर्ड नहीं। कोई Steam गार्ड नहीं। उस व्यक्ति को कोई सूचना नहीं कि यह उसका खाता था। उपयोगकर्ता ने कुंजी नहीं बनाई थी, वह उसे देख नहीं सकता था, और उसे बताया गया कि उसने ही बनाई थी। 2023-12-04 पर मोबाइल पुष्टि जोड़ी गई — 2016 बयान के लगभग सात साल बाद और उस घोटाले पैनलों के लगभग छह साल बाद जिन्हें आर्काइव संरक्षित करता है। उन वर्षों का भुगतान Valve द्वारा नहीं किया गया था। उनका भुगतान बीच में खाली किए गए खातों से किया गया था, जिनमें से कुछ बच्चों के थे।\n\nOWASP ASVS 2.8 / NIST SP 800-63Bगंभीरता: गंभीर\n1. अपर्याप्त स्टेप-अप प्रमाणीकरण\n\nSteam केवल एक सत्र कुकी का उपयोग करके अत्यधिक विशेषाधिकार प्राप्त, लंबे समय तक चलने वाले API कुंजियों के निर्माण की अनुमति दी। डेवलपर API कुंजी सेटअप या संशोधित करते समय 2FA (Steam Guard) या स्टेप-अप ऑथेंटिकेशन चुनौती की आवश्यकता नहीं थी, इसलिए Steam Guard मोबाइल पुष्टि — जो Steam द्वारा प्रदान किया जाने वाला एकमात्र दूसरा फैक्टर है — ने इस चरण की रक्षा नहीं की। (Valve के अपने ट्रैकर में 2016 में हार्डवेयर सेकंड फैक्टर का अनुरोध किया गया था और यह मुद्दा अभी भी खुला है: परिशिष्ट D, GH-01.)\n\nस्थिति: 2023. से पहले बिना पैच किए। एक स्क्रिप्ट जिसे चोरी की गई कुकी मिली हो, बिना किसी उपयोगकर्ता इंटरैक्शन के एक कुंजी पंजीकृत कर सकती थी।\nOWASP A01:2021 / न्यूनतम विशेषाधिकारगंभीरता: गंभीर\n2. न्यूनतम विशेषाधिकार के सिद्धांत का अभाव\n\nSteam वेब API में किसी भी भूमिका-आधारित प्राधिकरण दायरे का अभाव था। एक डेवलपर API कुंजी, जिसे \"केवल-पढ़ने\" इन्वेंटरी स्थिति के लिए जारी किया गया था, के पास पूर्ण \"लिखने\" की अनुमति थी — जिसमें मौजूदा ट्रेड्स में हेरफेर करने, नए ट्रेड्स आरंभ करने, वेबहुक्स पंजीकृत करने और मान्य लंबित एक्सचेंजों को अस्वीकार करने की क्षमता शामिल थी।\n\nस्थिति: प्रणालीगत डिज़ाइन दोष। एक कुंजी = खाते की इन्वेंटरी और ट्रेड्स पर पूर्ण पठन/लेखन नियंत्रण।\nOWASP A07:2021 / सत्रगंभीरता: उच्च\n3. टूटा हुआ सत्र प्रबंधन\n\nसर्वर-होस्टिंग आईपी रेंज से उत्पन्न हाईजैक किए गए वेब सत्रों के उपयोगकर्ताओं द्वारा लगातार बने रहने की रिपोर्ट की गई। मानक प्रथा यह है कि भौगोलिक विसंगतियों और पासवर्ड बदलने पर सत्रों को समाप्त कर दिया जाता है; अभिलेखागार में एकत्रित उपयोगकर्ता रिपोर्टों में ऐसे सत्रों का वर्णन है जो पासवर्ड बदलने के बाद भी सक्रिय रहे।\n\nस्थिति: रिपोर्ट किया गया व्यवहार (आर्काइव में उपयोगकर्ता शिकायतें)। सत्र बिना पुनः प्रमाणीकरण के API कुंजियाँ उत्पन्न कर सकते थे।\nडोमेन-स्तरीय अवरोधन तकनीकी रूप से संभव था।प्रवर्तन व्यवहार्यता\n4. प्रमाणन होस्ट्स को डोमेन-स्तर पर अवरुद्ध करना तकनीकी रूप से संभव था।\n\nValve यह पहले से ही एक डोमेन सूची (लिंक फ़िल्टर) संचालित करता है और पहले से ही अपनी OpenID अनुरोधों में प्रत्येक auth होस्टनेम प्राप्त करता है। ये दोनों तंत्र बाहरी रूप से किसी भी तरह से जुड़े नहीं हैं: 2026-09-22, में 26 के जोड़े में मुख्य डोमेन फ़िल्टर में था, जबकि लॉगिन वहन करने वाला प्रॉक्सी फ़िल्टर में नहीं था।\n\nउन्हें जोड़ना एक छोटा इंजीनियरिंग कार्य है: पढ़ें openid.realm प्रत्येक इनकमिंग अनुरोध से होस्टनेम प्राप्त करें, उसे एक सूची से तुलना करें, और अनुरोध को अस्वीकार या फ़्लैग करें। दाईं ओर का चित्र इस तरह की रूटीन का स्वरूप दिखाता है। केवल सार्वजनिक लैंडिंग पेज के बजाय auth होस्ट को अस्वीकार करने से उन प्लेटफ़ॉर्म्स पर निर्भर \"Steam के साथ साइन इन करें\" चरण बाधित हो जाएगा।\n\nकोई सार्वजनिक प्रमाण नहीं है कि Valve ऐसा कोई जाँच करता है। Steam Community Market का संयुक्त शुल्क लगभग 15% है, जो मार्केट के भीतर पूरी हुई बिक्री पर लागू होता है; यह इन प्लेटफ़ॉर्मों के बाहरी लेन-देन पर वसूला नहीं जाता।\n\nब्लॉक_ऑथ_होस्ट्स.पाइथनचित्रण\n// होस्ट Steam पहले से ही जो प्राप्त करता है उसे पढ़ें — कोई स्कैनिंग नहीं\nपरिभाषा on_openid_request(request):\nहोस्ट = parse_openid_realm(अनुरोध)\nयदि मेज़बान में अवरुद्ध_डोमेन:\nअस्वीकार करें (अनुरोध)\nनोट: केवल उदाहरण के लिए प्स्यूडोकोड। दोनों हिस्से पहले से ही Valve पर मौजूद हैं — अनुरोध में auth होस्टनेम आता है, और डोमेन सूची लिंक फ़िल्टर है। कोई सार्वजनिक रिकॉर्ड यह नहीं बताता कि वे क्यों जुड़े नहीं हैं।\nधारा 5.1 — मानक अप्रकाशित नहीं थे।\nValve यह हर दिन इन नियमों के खिलाफ बनता है। यहाँ यह इनके अनुसार नहीं बना।\n\nSteam App Store और Google Play पर उपलब्ध है, प्रमुख कार्ड प्रोसेसरों के माध्यम से बिक्री करता है, और किसी भी अन्य बड़े प्लेटफ़ॉर्म की तरह तृतीय-पक्ष API का उपयोग करता है। इन सभी संबंधों के लिए एक प्रकाशित, दिनांकित सुरक्षा आवश्यकता होती है जिसे Valve को संचालन जारी रखने के लिए पूरा करना होता है। इन आवश्यकताओं की तिथियों को Steam की अपनी वेब API द्वारा समान सुरक्षा प्राप्त करने की तिथियों से तुलना करें। नीचे दिया गया कुछ भी निजी मानक, आंतरिक ज्ञापन या व्यापार रहस्य नहीं है: प्रत्येक पंक्ति एक सार्वजनिक दस्तावेज़ है जिसकी प्रकाशन तिथि है।\n\nप्रकाशित बाहरी सुरक्षा आवश्यकताएँ, उनकी तिथियों सहित, उस तिथि के सापेक्ष निर्धारित की गईं जिस तिथि को Steam वेब API ने समतुल्य नियंत्रण प्राप्त किया।\nप्रकाशित मानक, और वह तिथि जिस दिन यह लागू हुआ\tSteam वेब API उसी प्रश्न पर\nScoped authorisationOAuth 2.0 — RFC 6749, October 2012. Section 3.3 defines scope so a client receives only the access it asks for. It has been the default of every major platform API since.\tGranular scopes arrived on 16 January 2026.Before that a single Steam Web API key carried full read and write over the account's trades regardless of why it was issued. Thirteen years and three months after the specification that defines the control.\nA key is not an authorisationGoogle's own Cloud documentation: A standard API key doesn't authenticate a principal, and for APIs that create or manage resources, don't use authorization keys in production.\tThe Steam Web API key was exactly that.A bearer string, issued to an account, sufficient on its own to read the inventory, cancel a pending trade and send a new one. No principal was authenticated at the point of use.\nMulti-factor authentication on privileged accessPCI DSS 3.2, requirement 8.3 — mandatory from 1 February 2018 for all non-console administrative and all remote access to the cardholder data environment. Apple then required two-factor authentication of every Developer Program account holder from 27 February 2019: developers with the Account Holder role in a developer program will need to enable two-factor authentication to sign in.\tA second factor was required to create an API key from 4 December 2023.Until then a stolen session cookie was enough, with no prompt on the account holder's phone and no notification afterwards. Four years and nine months after Apple made Valve itself use a second factor merely to sign in to a developer portal.\nCredential lifecycle and revocationTwitch requires of every third-party application: Your app must validate the OAuth token when it starts and on an hourly basis thereafter, and states that it audits for applications that do not. Its legacy v5 API was retired outright on 28 February 2022 on a published schedule.\tNo published key-lifecycle record.The 2023 change protected the creation endpoint. No Valve statement located with it addresses keys already registered, and no changelog accompanied the change at all. Whether keys created before it were invalidated cannot be established from public data — which is the question a data subject would need answered to know whether a key created on their account years earlier is still live.\nवास्तु मानक // टोकन वास्तुकला\nGitHub Valve फाइन-ग्रेन्ड स्कोप्स बनाम ई-लर्निंग वेब Steam API\n\nValve डेवलपर्स प्रतिदिन GitHub पर सूक्ष्म न्यूनतम-अधिकार टोकन का उपयोग करके ओपन-सोर्स सॉफ़्टवेयर का प्रबंधन करते हैं। इसकी तुलना 130M Steam खिलाड़ियों को जारी की गई मोनोलिथिक कुंजी से करें।\n\nGitHub सूक्ष्म-कण टोकन\nValve द्वारा GitHub पर उपयोग किया गया\n\nक्षेत्रबद्ध पृथक्करण और अनिवार्य जीवनचक्र प्रवर्तन वाला सूक्ष्म-कण।\n\nरिपॉजिटरी पहुँच:केवल चयनित रिपॉजिटरी (1 रिपॉजिटरी)\nअनुमति दें:केवल-पढ़ने योग्य [✓]\nकोड और रहस्य:कोई पहुँच नहीं [✕]\nसमाप्ति:30 दिन (अनिवार्य टीटीएल)\nऑडिट लॉगिंग:आईपी, यूज़र-एजेंट और टाइमस्टैम्प\nसुरक्षा की स्थिति: न्यूनतम-अधिकार टोकन क्षति को एक ही केवल-पठन संसाधन तक सीमित करता है।\n!Valve Steam वेब API कुंजी\n130एम उपयोगकर्ताओं को जारी\n\nएकल 32--चरित्र मास्टर स्ट्रिंग जो सभी या कुछ नहीं व्यापार और इन्वेंटरी प्राधिकरण वहन करती है।\n\nखाता पहुँच:पूर्ण विवरण (एकल-खंडीय)\nव्यापार प्रबंधन:पढ़ें, रद्द करें, अस्वीकार करें [!]\nविस्तृत दायरे:कोई नहीं (2026,13य देर से पहुँचे)\nसमाप्ति:कभी नहीं (अनंतकाल तक मान्य)\nऑडिट लॉगिंग:कोई नहीं (उपयोगकर्ता के लिए शून्य आईपी इतिहास)\nसंवेदनशीलता: चोरी की गई कुंजी सभी आउटगोइंग व्यापार प्रस्तावों को चुपचाप इंटरसेप्ट करने की अनुमति देती है।\nएक दिशा में लागू मानक\n\nमान लीजिए कि विक्रेता Valve जिस पर निर्भर है — एक क्लाउड प्रदाता, एक भुगतान प्रोसेसर, एक CDN — ने एक क्रेडेंशियल एंडपॉइंट को द्वितीयक कारक के बिना छोड़ दिया, और महीनों बाद Valve का अपना कॉर्पोरेट डेटा उस एंडपॉइंट पर मिंटे गई कुंजी के माध्यम से लीक हो गया। क्या Valve यह स्वीकार करेगा कि दोष उस व्यक्ति का था जिसने लिंक पर क्लिक किया था? इस दस्तावेज़ में संरक्षित संग्रहीत अस्वीकृतियाँ उपयोगकर्ता के लिए इसके विपरीत प्रश्न का उत्तर देती हैं: अपनाई गई स्थिति यह है कि खातेदार ने कुंजी बनाई और हानि उसी की है। उसी वास्तुकला को एक ओर विक्रेता की विफलता और दूसरी ओर उपयोगकर्ता की जिम्मेदारी के रूप में वर्णित किया गया है। यह तकनीकी प्रश्न नहीं है, और यह ऐसा मामला नहीं है जिसे यह जांच निपटा सकती है — यह निर्णय एक न्यायालय या पर्यवेक्षी प्राधिकरण लेता है।\n\nचित्रण, साक्ष्य नहीं — मानक को उल्टा पढ़ा जाता है\nएक भुगतान प्रोसेसर जिसने किसी तीसरे पक्ष की स्क्रिप्ट को केवल ब्राउज़र कुकी से ही पूर्ण-अधिकार वाला लेनदेन क्रेडेंशियल बनाने की अनुमति दी, बिना खाताधारक से कोई पुष्टि मांगे।\nएक पहचान प्रदाता जिसने उस छेद को बंद कर दिया जिससे उसके टोकन बनाए गए थे और पहले से बनाए गए टोकनों के बारे में कुछ भी प्रकाशित नहीं किया।\nएक बैंक ने विवादित ट्रांसफर का जवाब यह देखते हुए दिया कि उपयोग किया गया प्रमाण-पत्र ग्राहक के अपने खाते पर पंजीकृत था, और टिकट बंद कर दिया।\n\nइनमें से कोई भी किसी नामित कंपनी के बारे में निष्कर्ष के रूप में प्रस्तुत नहीं किया गया है। ये वही डिज़ाइन निर्णय हैं, जिन्हें एक ऐसे परिवेश में स्थानांतरित किया गया है जहाँ पर्यवेक्षी प्रतिक्रिया अच्छी तरह से प्रलेखित है — और यही तुलना है जिसे एक नियामक से करने के लिए कहा जा रहा है।\n\nरिकॉर्ड से यह स्थापित होता है: Steam वेब API पर मौजूद नियंत्रण सार्वजनिक, पुराने और कई मामलों में वे शर्तें थीं जिन्हें Valve को अपने उत्पादों की शिपिंग जारी रखने के लिए पूरा करना पड़ता था। प्रत्येक मानक और उसके समकक्ष Steam परिवर्तन के बीच का अंतराल मापा जा सकता है और ऊपर दिया गया है। यह यह स्थापित नहीं करता कि क्यों। इनमें से किसी भी अंतराल के लिए कोई Valve कारण-विवरण नहीं मिला है, और यहाँ कोई भी मान्य नहीं किया गया है; वह रिकॉर्ड Valve के भीतर मौजूद है और प्रकाशित नहीं किया गया है।\n\nस्रोत, प्रत्येक एक सार्वजनिक दस्तावेज़: OAuth 2.0 — आरएफसी 6749, अक्टूबर 2012 ↗ · गूगल क्लाउड — API कुंजियाँ दस्तावेज़ीकरण ↗ · पीसीआई डीएसएस 3.2 आवश्यकता 8.3 — पीसीआई एसएससी संसाधन मार्गदर्शिका ↗ · एप्पल — खाताधारकों के लिए आगामी दो-कारक प्रमाणीकरण आवश्यकता, 20 फरवरी 2019 ↗ संग्रहीत 2025-05-06 ↗ · ट्विच — टोकन सत्यापन आवश्यकता ↗ और v5 शटडाउन सूचना ↗ सहेजा गया 2025-01-27 ↗Steam की अपनी तिथियाँ इस अनुभाग में अपडेट रिकॉर्ड में दी गई हैं; 2023 और 2026 की प्रविष्टियाँ वे हैं जिन्हें Valve ने बिना चेंज लॉग के भेजा था। 2026-09-22. से प्राप्त।\n\nValve का अपना अपडेट रिकॉर्ड — सार्वजनिक स्रोतों से प्राप्त दिनांकित जानकारी\nदिनांक\tValve बदलाव\tघोषित?\tयह क्या बंद हुआ\tलैग: सार्वजनिक तंत्र → ठीक करें\tस्रोत\n2026-09-01\tAutomated Suspicious Chat Flagging\tYes\tDangerous links / patterns in group chats\t—\tnews ↗\n2026-01-16\tSteamworks Web API granular scopes\tYes\tLeast-privilege scopes for developer keys\t—\tannouncement ↗\n2025-07-15\tCS2 Trade Protection & reversal window\tYes\tNothing. Not a root-cause security fix. Support-side account recovery access remains untouched. Triggering reversal inflicts an automatic 30-day trade lockout (Skinvault ↗), while cash-trading shock caused a $104M (-25%) 24h market cap plunge (CSMarketCap ↗). In 2026, timers became per-item (Skin.land ↗).\t—\tFAQ ↗\n2025-05-14\tAccount Security Announcement\tYes\tStealer / session-hijack guidance\t—\tannouncement ↗\n2024-10-02\tCS2 'The Armory' 7-day hold\tYes\tHold on trade/market for Armory items\t—\tannouncement ↗\n2024-09-18\tNew-device login trade restriction\tYes\t2–7 day trade lock on new devices\t—\tFAQ ↗\n2024-02-14\tProfile name & avatar change hold\tYes\t2–4 h cooldown on trades after rename\t—\tpost ↗\n2023-12-04\tMobile confirmation for API keys\tNo changelog\tSilent cookie-only key registration\t≈6 years after the 2017-era panels\tdev page ↗\n2023-10-24\tSMS MFA for game build publications\tYes\tSteamworks build publishing\t—\tannouncement ↗\n2023-07-12\tCustom biography content warning\tYes\tPhishing links in bios\t—\tforum ↗\n2023-01-25\tProfile {LINK REMOVED} & cooldown\tYes\tLinks in profile text\t—\tFAQ ↗\n2022-10-24\tLogin overhaul & cookie truncation\tNo changelog\tInfinite stolen sessions\t— (IAuthenticationService token migration)\tnews ↗\n2022-10-12\tMobile App 3.0 QR login\tYes\tSession deauthorisation panel\t—\tnews ↗\n2022-05-10\tTrade-cancellation endpoints removed\tNo changelog\tOffer-swap (cancel & re-send)\t≈5 years after the 2017-era panels\tissue #325 ↗\n2020-05-25\tDota 2 7-day trade lock\tYes\tFast item flipping\t—\tblog ↗\n2018-03-29\tCS:GO 7-day trade lock\tYes\tInstant bot laundering\t≈20 months after the July 2016 statement\tblog ↗ archived 2025-02-26 ↗\nस्रोत: लिंक किए गए Valve पोस्ट, सहायता पृष्ठ और GitHub मुद्दे, दिनांकित। तीन निर्णायक सुधार बिना चेंज-लॉग के जारी किए गए (2022-05, 2022-10, 2023-12) और इन्हें उपयोगकर्ताओं ने ही खोजा, Valve द्वारा घोषित नहीं किया गया — यह असममितता प्रवर्तन रिकॉर्ड का हिस्सा है। विलंब केवल वहीं गणना किए जाते हैं जहाँ दस्तावेज़ की अपनी दिनांक (जुलाई 2016 बयान; 2017-युग के घोटाला पैनल) प्रारंभ बिंदु प्रदान करती है; \"—\" का अर्थ है कि यहाँ ऐसा कोई प्रारंभ बिंदु स्थापित नहीं है।\nभाग A — तकनीकी अभिलेख · अनुभाग 6\nइंटरैक्टिव एक्सप्लॉइट और हाईजैक सिमुलेटर\nप्रसंग और स्रोत सीमाएँ\n\nफ़िशिंग संदेश से लेकर सर्वर-साइड कुंजी पंजीकरण और ट्रेड स्वैप तक के मार्ग का पुनर्निर्माण। 2023, से पहले, किसी खाते पर पंजीकृत वेब API कुंजी अपनी इन्वेंटरी पढ़ सकती थी, लंबित ट्रेड प्रस्ताव रद्द कर सकती थी और एक नया प्रस्ताव बना सकती थी, और इन किसी भी क्रिया के लिए खाते के धारक को कोई ट्रेड-पुष्टि स्क्रीन नहीं दिखाई जाती थी। यह न्यूनतम विशेषाधिकार की अनुपस्थिति (OWASP A01:2021) है। इस सिमुलेशन में समय-सीमाएँ केवल उदाहरण के लिए हैं और वर्तमान प्लेटफ़ॉर्म के वास्तविक माप नहीं हैं।\n\nपुनर्निर्मित अपहरण का क्रम-दर-क्रम अवलोकन करें। प्रत्येक चरण में दिखाया गया है कि खाताधारक क्या देखता है और उसी क्षण कॉल Steam को क्या प्राप्त होती है। उन सभी कॉलों में से प्रत्येक को सही ढंग से प्रमाणीकृत किया गया है। क्रम में कवनो चीज़ के लिए ई आवश्यक नइखे कि Steam की प्रमाणीकरण विफल हो — जरूरी बा कि ई जारी करे वाली कुंजी का कोई दायरा ना हो (OWASP A01:2021).\n\nखिलाड़ी क्या देखता है। इसके पीछे क्या बदलता है।वॉकथ्रू सिम्युलेटर\nचरण 5 / 5\n\nशोषण पूरा हो गया। अपनी मूल ट्रेड के लिए मोबाइल प्रॉम्प्ट की उम्मीद करते हुए, पीड़ित प्रतिस्थापन ट्रेड को मंजूरी दे देता है। यह एक एकीकृत फोरेंसिक वॉकथ्रू है जो दिखाता है कि न्यूनतम विशेषाधिकार (OWASP A01:2021) की अनुपस्थिति स्वचालित, सब-सेकंड संपत्ति अपहरण को कैसे सक्षम करती है।\n\n01 / चैट लूरएक मित्र वोट देने के लिए कहता हैपीड़ित को एक लिंक वाला संदेश प्राप्त होता है।\n02 / लॉगिनएक नकली पोर्टलपीड़ित साइन-इन क्रेडेंशियल दर्ज करता है।\n03 / पहुँचसाइलेंट वेब API निर्माणहमलावर एक डेवलपर कुंजी पंजीकृत करता है।\n04 / द स्विचवैध व्यापार का आदान-प्रदानक्लोन बॉट लक्ष्य प्राप्तकर्ता की नकल करता है।\n05 / पुष्टिनकली स्वीकृतमोबाइल पर गलत ऑफर स्वीकृत।\nनेटवर्क से देखा गया वही कदमपूर्व-2023 पैटर्न का पुनर्निर्माण · आदर्श कॉल आकार\nपीड़ितमूल व्यापार के लिए अपेक्षित मोबाइल प्रॉम्प्ट को अनुमोदित करता है।\nहमलावरक्लोन खाते में आइटम प्राप्त करता है।\nSteam देखता हैखाताधारक द्वारा पंजीकृत डिवाइस पर पुष्टि किया गया स्थानांतरण।\nConfirmation genuine — made by the account holder\nRecipient the clone bot, not the intended counterparty\nThe confirmation is authentic. The offer it confirms is not the one the user initiated.\n\nछोड़कर गया रिकॉर्ड: एक ऐसा व्यापार जिसे उपयोगकर्ता ने मंजूरी दी। यही वह रिकॉर्ड है जो Steam सपोर्ट तब पढ़ता है जब शिकायत आती है, और यही कारण है कि संग्रहीत शिकायतों को उपयोगकर्ता की त्रुटि के रूप में बंद कर दिया गया था। शिकायतें हैं प्रवर्तन अभिलेखागार.\n\nभाग A — तकनीकी अभिलेख · अनुभाग 7\nक्रम के पीछे के एंडपॉइंट्स।\nप्रसंग और स्रोत सीमाएँ\n\nये वे Steam वेब API एंडपॉइंट्स हैं जिनका उपयोग रिपोर्ट की गई हाईजैक स्क्रिप्ट्स ने ट्रेड्स को इंटरसेप्ट करने के लिए किया, बिना ब्राउज़र-साइड पुष्टि प्रक्रियाओं से गुज़रे।\n\nचार दस्तावेजीकृत एंडपॉइंट्स पूरा काम कर देते हैं। इनमें से कोई भी खामी नहीं है, किसी का भी शोषण करने की आवश्यकता नहीं — एक वैध कुंजी उन्हें कॉल करती है और Steam उत्तर देता है। कुंजी ही एकमात्र चीज़ थी जिसे हमलावर को चुराना था।\n\nआईईकॉनसर्विस / गेटट्रेडऑफ़र्स / v1मतदान\n\nखाते की ट्रेड ऑफ़र्स की निगरानी के लिए उपयोग किया जाता है। स्क्रिप्ट्स इस एंडपॉइंट को समझौता किए गए API कुंजी के साथ बार-बार पोल करती हैं; यह नए बनाए गए, लंबित या संशोधित ट्रेड ऑफ़र्स का विवरण लौटाती है। पोलिंग अंतराल यहां मापे नहीं जाते।\n\nधमकी वेक्टर: लंबित व्यापार प्रस्ताव आईडी और प्राप्तकर्ता की प्रोफ़ाइल विवरण प्रकट करता है।\nआईईकॉनसर्विस / रद्द करें ट्रेड ऑफर / v1परस्पर क्रिया\n\nउपयोगकर्ता के वैध व्यापार प्रस्ताव को प्रोग्रामेटिक रूप से अमान्य करने के लिए प्रयुक्त। 2023 से पहले, कोई स्टेप-अप प्रमाणीकरण कुंजी की सुरक्षा नहीं करता था, इसलिए एक स्वचालित सर्वर जैसे ही इसे पहचान लेता, बिना खाताधारक से कोई पुष्टिकरण मांगे प्रस्ताव को रद्द कर सकता था।\n\nधमकी वेक्टर: खाता धारक द्वारा मोबाइल पुष्टि पूरी करने से पहले व्यापार को रद्द कर देता है।\nआईस्ट्रीमयूज़र / खिलाड़ी सारांश प्राप्त करें / v2निरीक्षण\n\nवैध व्यापार प्राप्तकर्ता का प्रोफ़ाइल नाम, अवतार छवि URL और स्तर प्राप्त करने के लिए क्वेरी की गई। इससे स्क्रिप्ट को मिलान के लिए तैयार क्लोन खाते को तैयार करने की अनुमति मिलती है। यहां कोई समय मापा नहीं जाता।\n\nधमकी वेक्टर: लक्षित प्राप्तकर्ता का भेष धारण करने के लिए आवश्यक डेटा प्रदान करता है।\n/dev/ajaxregisterkeyसृजन\n\nSteam की कुंजियों के लिए पंजीकरण एंडपॉइंट। ऐतिहासिक रूप से, कोई भी सक्रिय ब्राउज़र कुकी सत्र (`steamLoginSecure`) मोबाइल डिवाइस पर Steam गार्ड पुष्टि के बिना, और खाता धारक को किसी भी सूचना दिए बिना, एक कुंजी पंजीकृत कर सकता था।\n\nधमकी वेक्टर: एक स्क्रिप्ट द्वारा बनाई गई एक स्थायी क्रेडेंशियल, जिसे खाता धारक देख नहीं पाता।\nभाग A — तकनीकी अभिलेख · अनुभाग 8 · GDPR लेख 7\nएक चेक किया हुआ बॉक्स। किसकी कार्रवाई?\nप्रसंग और स्रोत सीमाएँ\n\nरिइम्बर्समेंट अस्वीकार करते समय, आर्काइव में संरक्षित Steam समर्थन प्रतिक्रियाएँ यह स्थिति अपनाती हैं कि खाता धारक ने API कुंजी बनाई और बॉक्स पर टिक करके शर्तों को स्वीकार किया।\n\nसमर्थन प्रतिक्रिया कुंजी को खाते के धारक से जोड़ती है। प्रश्न यह है कि क्या रिकॉर्ड यह स्थापित करता है कि वास्तव में इसे किसने बनाया था।\n\nपर्यवेक्षित API–key हाईजैक पैटर्न में, हालांकि पीड़ित ने कभी भी API key निर्माण पृष्ठ को नहीं देखा या उस पर नेविगेट नहीं किया। सहमति फ़ील्ड को चोरी की गई सत्र कुकी के साथ हेडलेस POST करने वाली स्क्रिप्ट द्वारा सबमिट किया जाता है।\n\nGDPR के अनुच्छेद 7 और अनुच्छेद 4 (11) के तहत, सहमति डेटा विषय की इच्छाओं का स्वतंत्र रूप से दिया गया, विशिष्ट, सूचित और अस्पष्ट रहित संकेत होना चाहिए। लेखकों का मानना है कि एक शत्रुतापूर्ण स्क्रिप्ट द्वारा चोरी की गई कुकी के साथ प्रस्तुत किया गया, बिना खाताधारक को कोई पृष्ठ दिखाए, नियम-स्वीकृति फ़ील्ड उस परिभाषा को पूरा नहीं कर सकता। यह निर्णय पर्यवेक्षी प्राधिकरण पर निर्भर है।\n\nफोरेंसिक पेलोड विश्लेषण: कुंजी पंजीकरण\nपोस्ट https://steamcommunity.com/dev/ajaxregisterkey\n// पेडलोड अनुरोध (हाइजैकिंग स्क्रिप्ट के माध्यम से इंजेक्ट किया गया)\n{\nशर्तों से सहमत हैं: सहमत हूँ, <-- मशीन-इनजेक्टेड, कोई मानवीय हस्तक्षेप नहीं\nडोमेन: स्थानीय होस्ट, ← सत्यापित नहीं — कोई भी मान स्वीकार्य है, जिसमें localhost भी शामिल है\nसत्र आईडी: 8f0d8ef763ab2140bf89de2a\n}\nनिरिक्षण प्राधिकरण के लिए प्रश्न: जहाँ खाताधारक ने सहमति क्षेत्र पर कभी क्लिक नहीं किया, क्या खाते के विरुद्ध दर्ज शर्तों की स्वीकृति अनुच्छेद 7 की डेटा विषय की इच्छाओं के स्वतंत्र रूप से दिए गए, विशिष्ट, सूचित और स्पष्ट संकेत की आवश्यकता को पूरा करती है, और क्या Steam सपोर्ट दावे को अस्वीकार करने के लिए इस पर भरोसा कर सकता है।\n\nस्रोत: सार्वजनिक एंडपॉइंट और साक्ष्य संग्रह में संरक्षित हाईजैक रिपोर्टों से पुनर्निर्मित कुंजी पंजीकरण के आकार का अनुरोध (2026-09-17 की खोजने योग्य बिल्ड) · दिखाया गया सत्र पहचानक एक प्लेसहोल्डर है, कैप्चर किया गया मान नहीं।\n\nन्यायिक शव-परीक्षा · प्रतिस्थापन व्यापार वेक्टर\nValve ने आखिरकार \"ट्रेड सब्स्टिट्यूशन\" को कैसे निष्प्रभावी किया — और 7 को इसके लिए वर्षों तक कामचलाऊ समाधान क्यों अपनाने पड़े\n\nलगभग एक दशक से, API की मुख्य व्यापार प्रतिस्थापन (या API का MitM घोटाला) Steam पर सबसे अधिक लाभदायक खाता चोरी मॉडल था, जिसने अनजान खिलाड़ियों से स्किन्स के रूप में सैकड़ों मिलियन डॉलर निकाल लिए। Valve ने कमजोर API आर्किटेक्चर को ठीक करके इस एक्सप्लॉइट को खत्म नहीं किया; इसके बजाय, Valve ने सात साल बिताए प्लेटफ़ॉर्म-व्यापी चार अवरोधक परतें लगाकर, जिससे समुदाय के व्यापार की तरलता ठप हो गई, जबकि मूल कारण अनसुलझा रह गया।\n\n1. अनुकरण मृत्यु\nअवतार और नाम कूलडाउन (फरवरी 2024)\n\nइस शोषण के लिए सब-सेकंड नकल की आवश्यकता थी: स्कैम बॉट ने एक आउटगोइंग ट्रेड को इंटरसेप्ट किया, प्राप्तकर्ता का अवतार/नाम स्क्रैप किया via ISteamUser, और प्रोफ़ाइल को 200ms. में क्लोन किया। 14 फरवरी 2024, पर Valve ने चुपचाप एक अनिवार्य लागू किया। 2-टू-4 घंटे का ट्रेड कूलडाउन (त्रुटि 34) किसी भी प्रोफ़ाइल नाम या अवतार परिवर्तन के तुरंत बाद। एक बॉट अब प्राप्तकर्ता को तुरंत क्लोन नहीं कर सकता, बिना खुद को ट्रेडिंग से लॉक आउट किए।\n\n2. आर्थिक मृत्यु\n7-डे सीएस2 ट्रेड रिवर्सल (जुलाई 2025)\n\nValve एकपक्षीय पेश किया गया व्यापार पलटफेर काउंटर-स्ट्राइक आइटम्स के लिए। किसी भी ट्रेड की गई स्किन पर सात दिनों के लिए \"Trade Protected\" टैग लगा रहता है। यदि पीड़ित को प्रतिस्थापन का पता चलता है, तो वे Steam सपोर्ट में \"Reverse Trade\" पर क्लिक करते हैं, और स्किन तुरंत उनकी इन्वेंटरी में वापस आ जाती है, साथ ही प्राप्तकर्ता का खाता फ्रीज हो जाता है। क्योंकि 7-के दिन के ट्रेड लॉक से स्कैमर आइटम को कैशआउट साइट पर नहीं भेज सकते, इसलिए चोरी लाभहीन हो जाती है।\n\n3. मौन कुंजी मृत्यु\nAPI के लिए अनिवार्य मोबाइल पुश (दिसंबर 2023)\n\nऐतिहासिक रूप से, एक चोरी की गई सत्र कुकी ने दुर्भावनापूर्ण स्क्रिप्ट्स को एक हेडलेस बैकग्राउंड POST करने की अनुमति दी। /dev/ajaxregisterkey पीड़ित को सूचित किए बिना। 4 दिसंबर 2023,Valve ने Steam मोबाइल ऐप पर वेब API कुंजी उत्पन्न करने के लिए एक स्पष्ट पुश पुष्टि अनिवार्य कर दी, जिससे चुपचाप पृष्ठभूमि कुंजी प्रावधान समाप्त हो गया।\n\n4. ऐप में मोबाइल चेतावनियाँ\nखाते की आयु और नाम बैनर (2022–2024)\n\nValve व्यापार भागीदार को प्रदर्शित करने के लिए मोबाइल पुष्टि मोडाल को नया रूप दिया। Steam खाता कार्यकाल (सृजन तिथि), Steam स्तर, और एक स्पष्ट एम्बर चेतावनी: इस उपयोगकर्ता ने हाल ही में अपना प्रोफ़ाइल नाम बदला है।, चौकस शिकारों के लिए दृश्य भ्रम को तोड़ते हुए।\n\nValve के पैचवर्क में तीन खामियाँ: ठगों ने लक्ष्य क्यों बदल लिए\n1. गेम अपवाद का छेद (डोटा 2 और TF2)\n\nट्रेड रिवर्सल्स विशेष रूप से काउंटर-स्ट्राइक 2. के लिए तैनात किए गए थे। डोटा 2 और टीम फोर्ट्रेस 2 की वस्तुएँ पूरी तरह से असुरक्षित हैं। क्राफ्टिंग और सॉकेटिंग की जटिलताओं के कारण। हजारों डॉलर मूल्य की उच्च-स्तरीय वस्तुएँ (Dragonclaw Hooks, Golden Baby Roshans, Unusual TF2 burning flames) में कोई रिवर्सल विंडो नहीं होती। स्कैमर्स ने बस स्वचालित API इंटरसेप्शन को Dota 2 और TF2 ट्रेडर्स पर रीडायरेक्ट कर दिया, जहाँ Steam सपोर्ट अपनी 2016 \"नो आइटम रिस्टोरेशन\" नीति को सख्ती से लागू करता है।\n\n2. \"ज़ॉम्बी की\" जलाशय (शून्य समाप्ति)\n\nजबकि Valve ने मोबाइल पुश 2FA उत्पन्न करने के लिए जोड़ा नया कुंजी दिसंबर में2023, Valve मौजूदा लीगेसी API कुंजियों को कभी रद्द, समाप्त या साफ़ नहीं किया गया।. लाखों सक्रिय खाते जिन्होंने कुंजीएँ उत्पन्न कीं (या जिनकी कुंजीएँ फ़िशिंग/मैलवेयर द्वारा 2023 से पहले चुपचाप बनाई गई थीं) अभी भी सक्रिय क्रेडेंशियल्स के साथ मौजूद हैं शून्य समाप्ति (कोई TTL नहीं) और शून्य निष्क्रियता टाइमआउट. खतरे के कर्ता इन स्थायी कुंजियों का विशाल ऐतिहासिक डेटाबेस बनाए रखते हैं, और लगातार पोल करते रहते हैं IEconService अबाधित\n\n3. पीड़ित दंड: 30-डे ट्रेडिंग लॉकडाउन\n\nCS2 में भी, Valve धोखा खाए गए खिलाड़ी को दंडित करता है: Steam सपोर्ट में \"Reverse Trade\" पर क्लिक करने से स्वचालित रूप से एक पीड़ित के खाते पर अनिवार्य 30--डे ट्रेडिंग और कम्युनिटी मार्केट प्रतिबंधValve उपयोगकर्ता को \"बेबुनियाद\" रिवर्सलों के खिलाफ निवारक के रूप में एक महीने के लिए प्लेटफ़ॉर्म से निष्कासित कर दंडित करता है, जिससे पीड़ितों को कम-मूल्य वाले तरल आइटमों पर ट्रेड रिवर्स करने से हतोत्साहित किया जाता है।\n\nमुख्य नियामक घोटाला: सात वर्षों के कामचलाऊ उपायों बनाम एक API दायरा\n\nValve ने उद्योग-मानक समाधान लागू करने के बजाय व्यापार होल्ड, खाता कूलडाउन और रिवर्सिबल ट्रेड लॉक जैसी चीज़ें आविष्कार करने में सात साल क्यों बिताए—जिससे पूरी गेमिंग अर्थव्यवस्था में उथल-पुथल मच गई और बाजार पूंजीकरण में $104मिलियन का नुकसान हो गया?\n\nValve की आधिकारिक Steamworks रिलीज़ 16 जनवरी 2026 (घोषणा) द्वारा प्रमाणित। #493839547938902179 ↗), Valve पहले से ही बना हुआ दानेदार अनुमति समूह (सामान्य, माइक्रोट्रांजेक्शन, अर्थव्यवस्था, बिक्री डेटा) और आईपी व्हाइटलिस्टिंग कॉर्पोरेट पब्लिशर कीज़ के लिए। Valve के पास वर्षों से इंजीनियरिंग समाधान हाथ में था। एक ही उपयोगकर्ता-सामना वाला चेकबॉक्स—इस वेब API कुंजी को IEconService (ट्रेड मैनेजमेंट) तक पहुँचने से रोकें। या एक होम आईपी व्हाइटलिस्ट—ने 2018 में व्यापार प्रतिस्थापन घोटाले को शून्य आर्थिक सह-क्षति के साथ समाप्त कर दिया होता।Valve ने नियमित खिलाड़ियों को वह सुरक्षा देने से इनकार कर दिया जो उसने कॉर्पोरेट भागीदारों के लिए तैयार की थी।\n\nभाग बी — नियम और प्रवर्तन अभिलेख · धारा 9\nउनकी नियमावली। रिकॉर्डेड प्लेटफ़ॉर्म।\nप्रसंग और स्रोत सीमाएँ\n\nयह लेजर से स्पष्ट प्रावधानों को मानचित्रित करता है Steam सब्सक्राइबर समझौता (एसएसए) और Steam ऑनलाइन आचरण (एसओसी) सीधे तौर पर सक्रिय, बड़े पैमाने पर वाणिज्यिक संस्थाओं के खिलाफ दिशानिर्देश।\n\nनियम: कोई व्यावसायिक उपयोग नहीं, कोई जुआ नहीं, कोई बॉट्स नहीं — और Steam पीड़ित की वस्तुएँ वापस करने से इनकार करते समय इन शर्तों का हवाला देता है। रिकॉर्ड: वे ही प्रावधान, स्पष्ट रूप से, इस रजिस्टर में व्यावसायिक प्लेटफ़ॉर्मों को कवर करते हैं, जो Steam पहचानों, Steam बॉट्स और Steam ट्रांसफ़र्स पर चलते हैं। यह प्रावधान उन व्यक्तियों पर लागू होता है जिन्होंने स्किन्स खोए हैं, न कि किसी भी प्रकाशित रिकॉर्ड में उन्हें स्थानांतरित करने वाले व्यवसायों पर।\n\nआर्काइव की गई शिकायतों में, Steam सपोर्ट उद्धृत करता है वाणिज्यिक उपयोग निषिद्ध और कोई ऑटोमेशन/बॉट्स नहीं API-key धोखाधड़ी के शिकारों को वस्तुएँ पुनर्स्थापित करने से इनकार करते समय लागू होने वाली शर्तें। ये शर्तें इस दस्तावेज़ में दर्ज वाणिज्यिक प्लेटफ़ॉर्मों पर भी प्रत्यक्ष रूप से लागू होती हैं, जो Steam OpenID के माध्यम से प्रमाणीकरण करते हैं और स्वचालित Steam खातों के जरिए वस्तुएँ स्थानांतरित करते हैं। यहाँ कोई समग्र बाज़ार राजस्व आंकड़ा अनुमानित नहीं किया गया है (नीचे प्रवर्तन सांख्यिकी देखें)। रिकॉर्ड से पता चलता है कि संग्रहीत मामलों में व्यक्तिगत खातों पर नियम लागू किया गया है और प्लेटफ़ॉर्मों के लिए प्रति-ऑपरेटर कोई प्रकाशित प्रवर्तन रिकॉर्ड नहीं है। इस असममितता को ही यह अनुभाग दस्तावेज़ित करता है।\n\nमुख्य प्रश्न / चयनात्मक प्रवर्तननियम → पैमाना → जवाबदेही\nएक नियमपुस्तिका। असमान प्रवर्तन।\n\nSteam रजिस्टर दिखाता है कि वाणिज्यिक सेवाएँ ऑपरेटिंग इंफ्रास्ट्रक्चर के रूप में ईमेल पते, इन्वेंटरी, बॉट्स और ट्रांसफर का उपयोग कर रही हैं। SSA बिना अनुमति के वाणिज्यिक शोषण और स्वचालन पर प्रतिबंध लगाता है। संग्रहित शिकायतों से पता चलता है कि यह नियम व्यक्तिगत खातों पर लागू किया गया था, जबकि सार्वजनिक रिकॉर्ड में यहाँ दस्तावेजीकृत प्लेटफ़ॉर्मों के लिए प्रत्येक ऑपरेटर-वार खाता नहीं दिखता। प्रत्येक के लिए नियम, साक्ष्य और प्रवर्तन निर्णय प्रकाशित करें।\n\n189ऑडिट के दायरे में वेबसाइटें\n44लाइव रजिस्टर में अलग-डोमेन राउट्स — 27 एक प्रकाशित साक्ष्य फ़ाइल के साथ, और 17 मैन्युअल रूप से एकत्रित। केवल 189-वेबसाइट ब्राउज़र ऑडिट ने इनमें से 25 को हल किया; रजिस्टर मैन्युअल रूप से एकत्रित राउट्स को जोड़ता है।\n12 वर्ष6हcsgogem.com लिंक फ़िल्टर में अवरुद्ध; api.csgem.com 2014-03-08 पंजीकृत और कभी अवरुद्ध नहीं — 2026-09-22 तक ऐसे 26 युग्मों में से एक।\nकोई सत्यापित कुल नहींबाज़ार-व्यापी राजस्व अनुमान शामिल नहीं किया गया\nSteam ऑनलाइन आचरण\n\"…you shall not do, or attempt to do, any of the following on Steam: […] Engage in commercial activity. Examples of such prohibited behavior include: posting advertisements; running contests; gambling; buying or selling Steam accounts; selling content, gift cards, or other items; and begging.\"\n\nstore.steampowered.comऑनलाइन आचरण ↗ संचित 2026-09-21 ↗\n\nएसएसए § 2.G — वाणिज्यिक उपयोग\n\"…[you may not] exploit the Content and Services or any of its parts for any commercial purpose, except as expressly permitted elsewhere in this Agreement…\"\n\nValve की 2016 सूचनाओं ने, जैसा कि रिपोर्ट किया गया है, व्यक्तिगत, गैर-व्यावसायिक लाइसेंस का सहारा लिया। किसी भी ऑपरेटर ने रिकॉर्ड पर Valve प्राधिकरण प्रस्तुत नहीं किया है। store.steampowered.com/सदस्यता_अनुबंध ↗ संग्रहीत 2026-09-18 ↗\n\nSteam वेब API उपयोग की शर्तें\n\"You may not use the Steam Web API or Steam Data in any way that violates the Steam Subscriber Agreement.\"\n\nतृतीय-पक्ष स्किन मार्केटप्लेस स्वचालित खातों के माध्यम से SteamAPI का उपभोग करते हुए संचालित होते हैं। नियम पाठ वाणिज्यिक पैमाने के लिए कोई अपवाद नहीं छोड़ता। steamcommunity.com/dev/apiterms ↗ संचित 2026-09-21 ↗\n\nएसएसए § 4.C\nस्वचालन\n\nस्क्रिप्ट्स, बॉट्स और गैर-मानवीय इंटरैक्शन प्रतिबंधित हैं। लेजर वाणिज्यिक स्तर पर बॉट ट्रेडिंग, अकाउंट फार्म्स और स्वचालित रूटिंग को रिकॉर्ड करता है।\n\nनिरीक्षण करें 153इस खंड के अंतर्गत टैग किए गए रिकॉर्ड ↗\nइस खंड के अंतर्गत रिकॉर्ड में क्या शामिल है153 टैग किए गए प्लेटफ़ॉर्म\nमामला खोलना15\nस्किन कैसीनो13\nसीएस2 मार्केट9\nत्वचा रूलेट8\ncsgoempire.com→csgoempirelogin4.comकैसीनो\nrollbit.com→rbsnin.comक्रिप्टो कैसीनो\n500.casino→fivezerozero.coलाइसेंस प्राप्त कैसीनो\n\nइनमें से 153 को भी SSA § 2.G और के तहत टैग किया गया है। 2 इन पर SSA § 1.C के अंतर्गत भी टैग किया गया है — एक ही सेवाएँ एक से अधिक खंड के अंतर्गत आती हैं, इसीलिए उदाहरण दोहराए जाते हैं।\n\n28 153 के माध्यम से एक अलग पंजीकरण योग्य डोमेन के माध्यम से प्रमाणीकरण करते हुए देखा गया। एक टैग एक दिनांकित अवलोकन को दर्ज करता है जो प्लेटफ़ॉर्म को स्पष्ट रूप से खंड के दायरे में लाता है; यह कोई निर्णय-प्राप्त उल्लंघन नहीं है, और उनमें से किसी के लिए भी कोई Valve प्राधिकरण प्रस्तुत नहीं किया गया है।\n\nएसएसए § 2.G\nव्यावसायिक उपयोग\n\nव्यावसायिक शोषण के लिए स्पष्ट अनुमति आवश्यक है। दस्तावेजीकृत व्यावसायिक मॉडलों, उनके पैमाने और किसी भी प्रकटीकृत प्राधिकरण या प्रवर्तन की तुलना करें।\n\nनिरीक्षण करें 175इस खंड के अंतर्गत टैग किए गए रिकॉर्ड ↗\nइस खंड के अंतर्गत रिकॉर्ड में क्या शामिल है175 टैग किए गए प्लेटफ़ॉर्म\nमामला खोलना15\nस्किन कैसीनो13\nसीएस2 मार्केट9\nत्वचा रूलेट8\ncsgoempire.com→csgoempirelogin4.comकैसीनो\nrollbit.com→rbsnin.comक्रिप्टो कैसीनो\n500.casino→fivezerozero.coलाइसेंस प्राप्त कैसीनो\n\nइनमें से 153 को भी SSA § 4.C और के तहत टैग किया गया है। 24 इन पर SSA § 1.C के अंतर्गत भी टैग किया गया है — एक ही सेवाएँ एक से अधिक खंड के अंतर्गत आती हैं, इसीलिए उदाहरण दोहराए जाते हैं।\n\n28 175 के माध्यम से एक अलग पंजीकरण योग्य डोमेन के ज़रिए प्रमाणीकरण करते हुए देखा गया। एक टैग एक दिनांकित अवलोकन को दर्ज करता है जो स्पष्ट रूप से प्लेटफ़ॉर्म को इस खंड के दायरे में लाता है; यह कोई निर्णय-प्राप्त उल्लंघन नहीं है, और उनमें से किसी के लिए भी कोई Valve प्राधिकरण प्रस्तुत नहीं किया गया है।\n\nएसएसए § 3.A\nवीपीएन और स्थान छुपाना\n\nआईपी प्रॉक्सी के माध्यम से निवास स्थान छिपाने से सेवा समाप्ति हो सकती है। अलग-डोमेन प्रमाणीकरण होस्ट्स के लिए एक अलग विश्लेषण आवश्यक है: यह निर्धारित करें कि क्या छिपाया गया है और कौन सा नियम लागू होता है।\n\nauth-host साक्ष्य का निरीक्षण करें ↗\nSteam सहायता / यूआरएल नीति\nलिंक अस्पष्टीकरण\n\nSteam लिंक शॉर्टनर और उन उपकरणों को प्रतिबंधित करता है जो लिंक गंतव्यों को अस्पष्ट करते हैं। एक अलग auth डोमेन — rbsnin.com Rollbit के लॉगिन फ्लो में, auth.dota.trade CS.MONEY में — यह तुलनीय प्रश्न उठाता है कि क्या Steam के OpenID सत्यापनकर्ता को दिखाया गया गंतव्य संचालन स्थल की पहचान करता है।\n\nValve की URL नीति ↗\n\nनियम संदर्भ: Steam सब्सक्राइबर समझौता, संशोधन 10 सितंबर 2026 संग्रहीत 2026-09-18 ↗ · Steam वेब API उपयोग की शर्तें संचित 2026-09-21 ↗ · Steam यूआरएल नीति (लिंक अस्पष्टीकरण). काउंट्स इस डोजियर के रिकॉर्ड और टैग का वर्णन करते हैं; ये निर्णयित उल्लंघनों की संख्या नहीं हैं।\n\nविश्वास की कमी\nजब सहायता विभाग मामला बंद कर देता है, तो उस निर्णय की समीक्षा कौन करता है?\n\nसंरक्षित शिकायतों में स्थायी प्रतिबंध, अनुत्तरित चुनौतियाँ और चोरी की गई वस्तुओं को पुनर्स्थापित करने से इनकार का वर्णन है। उन विवरणों की तुलना वास्तविक टिकट इतिहास, उपलब्ध उपायों और खाते तक पहुँच लॉग से करें। एक सामान्य फ़िशिंग स्पष्टीकरण यह स्थापित नहीं कर सकता कि किसने रीसेट शुरू किया या 'API' कुंजी बनाई।\n\nकैप्चर की गई शिकायतें पढ़ें ↗मूल अभिलेखों का अनुरोध करें →मॉडरेटर संबंध ग्राफ़ →\nभाग बी — नियम और प्रवर्तन अभिलेख · धारा 10\nएक स्वचालन API। स्वचालन के खिलाफ एक नियम।\nप्रसंग और स्रोत सीमाएँ\n\nइस खंड का प्रश्न यह है कि दोनों को कैसे सामंजस्यपूर्ण बनाया जाए: API के कौन से उपयोग अधिकृत हैं, इन्हें किसने अधिकृत किया है, और किन प्रकाशित मानदंडों के आधार पर। यहाँ अधिकृत वाणिज्यिक API उपयोगकर्ताओं की कोई संख्या अनुमानित नहीं की गई है, और प्रकाशित सूची की अनुपस्थिति से कोई संख्या निहित नहीं होती — अनुपस्थिति ही निष्कर्ष है, न कि उसके पीछे कोई संख्या। उपरोक्त उद्धृत Steam समर्थन संदेश ArchiSteamFarm परियोजना द्वारा अपनी FAQ में पुनरुत्पादित किए गए हैं (शब्दशः सत्यापित 2026-09-22); ये Valve प्रकाशन नहीं हैं, और जिन्हें ये संदेश भेजे गए थे उन खातों की पहचान नहीं की गई है।\n\nनियम (एसएसए § 4.C): Steam पर कोई स्क्रिप्ट, कोई बॉट, कोई गैर-मानवीय सिस्टम नहीं। रिकॉर्ड: Valve एक हेडलेस REST API प्रदान करता है, जिसका पूरा उद्देश्य सर्वर-टू-सर्वर ऑटोमेशन है, और किसी भी खाते की चाबी सौंप देता है। उपयोगकर्ताओं को ऑटोमेशन के लिए प्रतिबंधित किया जाता है; ऑटोमेशन इंटरफ़ेस Valve का अपना उत्पाद है। कौन से व्यावसायिक उपयोग अधिकृत हैं, यह कभी प्रकाशित नहीं किया गया है।\n\n\"गेम डेवलपर\" भ्रम\nस्टीमवर्क्स एसडीके (वैध)\n\nवैध गेम स्टूडियो द्वारा अपने गेम क्लाइंट्स में उपलब्धियाँ, मैचमेकिंग और लीडरबोर्ड्स को एकीकृत करने के लिए उपयोग किया जाता है। इसके लिए जटिल C++ एकीकरण और आधिकारिक पार्टनर ऑनबोर्डिंग की आवश्यकता होती है।\n\nSteam वेब API (दरार)\n\nएक हेडलेस JSON/REST आर्किटेक्चर जो बाहरी वेब सर्वरों के लिए डिज़ाइन किया गया है। यहाँ दस्तावेज़ित हाइजैक पैटर्न में इसका उपयोग रिमोट सर्वरों से इन्वेंटरी पढ़ने और पीयर-टू-पीयर ट्रेड्स को मैनिपुलेट करने के लिए किया जाता है; इसके वैध उपयोग इस दस्तावेज़ में सूचीबद्ध नहीं हैं।\n\nकुंजी किसके लिए हैएक सामान्य Steam उपयोगकर्ता को इन-क्लाइंट में वेब API कुंजी की कोई आवश्यकता नहीं होती; यह कुंजी पेज एक डेवलपर URL के अंतर्गत रहता है और इसका दस्तावेजीकृत उद्देश्य बाहरी, सर्वर-साइड एक्सेस है। संग्रहीत हाईजैक शिकायतों में उन पीड़ितों का वर्णन है जिन्हें तब तक इस पेज के अस्तित्व का पता नहीं था जब तक कि उनकी खाता पर एक कुंजी पंजीकृत नहीं हो गई थी।\nस्वचालन का विरोधाभास\n\nएसएसए § 4.C प्रदान करता है: आप Steam पर सामग्री और सेवाओं के साथ किसी भी प्रकार से संवाद करने के लिए किसी भी प्रकार की स्क्रिप्ट्स, बॉट्स, मैक्रोज़, या अन्य गैर-मानव-नियंत्रित प्रणालियों ('ऑटोमेशन') का उपयोग नहीं कर सकते। फिर भी वेब API एंडपॉइंट्स (जैसे CancelTradeOffer) इन्हें किसी मानवीय UI या कैप्चा की आवश्यकता नहीं होती और ये Steam क्लाइंट को पूरी तरह बाईपास कर देते हैं। API को सर्वर-टू-सर्वर ऑटोमेशन के लिए डिज़ाइन किया गया है; नियम उपयोगकर्ताओं द्वारा ऑटोमेशन को प्रतिबंधित करता है; दोनों के बीच की सीमा प्रकाशित नहीं की गई है।\n\nव्यापार प्रवाह में सर्वर-साइड स्थिति\n\nएक वेब API कुंजी तीसरे पक्ष के सर्वर को Steam क्लाइंट के बिना खाते के ट्रेड्स पर कार्रवाई करने की अनुमति देती है। हाइजैक पैटर्न में, वह सर्वर खाता धारक और ट्रेड सर्वर के बीच स्थित होता है।\n\n→की की क्रियाओं के लिए कोई ट्रेड-पुष्टि स्क्रीन नहीं दिखाई जाती है।\n→पृष्ठभूमि पोलिंग (GetTradeOffers) की अनुमति देता है।\n→उपयोगकर्ता की सहभागिता के बिना ऑफ़र्स को रद्द और पुनः जारी करता है।\nValve इंटरफ़ेस बनाया, अपने नियमों में उपयोगकर्ता स्वचालन पर प्रतिबंध लगाया, और इस बात के कोई मानदंड प्रकाशित नहीं किए हैं कि कौन से व्यावसायिक उपयोग अधिकृत हैं।\nभाग बी — नियम और प्रवर्तन अभिलेख · धारा 11\nदस दिनों की मांग। दस सालों का हिसाब।\nप्रसंग और स्रोत सीमाएँ\n\n20 जुलाई 2016 Valve के मुख्य कानूनी सलाहकार ने जुआ संचालकों को 10-दिन की समयसीमा दी। दस साल बाद (डॉसियर स्नैपशॉट के अनुसार, 2026-09-21) उस नोटिस में नाम आए कम से कम एक प्लेटफ़ॉर्म, CSGOFast, अभी भी एक अलग-डोमेन ऑथ होस्ट के साथ संचालित हो रहा है। नीचे की शब्दावली 21 जुलाई 2016 की प्रेस रिपोर्टों से पुनर्निर्मित की गई है; यह पुनर्निर्माण स्कैन नहीं है। सूचना में निहित प्रवर्तन रिकॉर्ड प्रकाशित नहीं किया गया है। आयोग को खुला पत्र है धारा 2.\n\nबाद के अवलोकनों के बगल में जुलाई के 2016 नोटिस को पढ़ें। बकाया मांग ऑपरेटर-दर-ऑपरेटर प्रवर्तन रिकॉर्ड है।\n\nएक सप्ताह पहले — 13 जुलाई 2016, सार्वजनिक रूप से\n\nपर 13 जुलाई 2016 संचित 2026-09-21 ↗Valve ने बताया कि जुआ साइटों ने खाता पहचान के लिए Steam और व्यापार के लिए स्वचालित खातों का उपयोग कैसे किया।Valve ने कहा कि उन तंत्रों का उपयोग करके जुआ व्यवसाय चलाना इसकी API और उपयोगकर्ता समझौतों का उल्लंघन था। यंत्रणा का विवरण और प्रतिबंध दोनों ही Valve के स्वयं के दिनांकित बयान में हैं। 2026-09-21 पर परीक्षण किए गए अलग-डोमेन प्रमाणीकरण होस्ट्स ने कोई लिंक फ़िल्टर ब्लॉक नहीं लौटाया, और Valve ने कोई प्रति-ऑपरेटर प्रवर्तन रिकॉर्ड प्रकाशित नहीं किया है।\n\nपरिशिष्ट A / जुलाई 2016टाइपसेट पुनर्निर्माण\nवॉल्व कॉर्पोरेशन\n\nबेलव्यू, डब्ल्यूए\n\nदिनांक:जुलाई 2016 (प्रेस द्वारा रिपोर्ट किया गया 21 जुलाई 2016)\nसे:कार्ल क्वैकेनबुश, महाधिवक्ता\nउत्तर:Steam खातों के व्यावसायिक उपयोग को बंद करें और रोका जाए\nनोट:रिपोर्ट किए गए पाठ का पुनर्निर्माण; स्कैन नहीं\n\nहमें पता है कि आप नीचे सूचीबद्ध जुआ साइटों में से एक का संचालन कर रहे हैं। आप इस व्यवसाय को चलाने के लिए Steam खाते का उपयोग कर रहे हैं। Steam सदस्यता अनुबंध के तहत, Steam और Steam सेवाएँ केवल व्यक्तिगत, गैर-व्यावसायिक उपयोग के लिए लाइसेंस प्राप्त हैं।\n\nआपको तुरंत अपने Steam खातों का किसी भी व्यावसायिक उद्देश्य के लिए आगे का उपयोग बंद कर देना चाहिए। यदि आप ऐसा करने में विफल रहते हैं दस (10) दिनों के भीतरValve सभी उपलब्ध उपायों का सहारा लेगा, जिसमें आपके खातों को समाप्त करना भी शामिल है, लेकिन यह इन्हीं तक सीमित नहीं है।\n\nडॉसियर पुनर्निर्माण · स्रोत रिकॉर्ड देखें\nकार्ल क्वैकेनबुश\nमुख्य विधिक सलाहकार, Valve कॉर्प.\nकिनारे पर / संपादकीय\nदस दिन।फिर क्या?\n\nअंतिम तिथि विशिष्ट थी। सार्वजनिक अनुपालन भी ऐसा ही होना चाहिए।\n\nValve ने प्रकाशित किया है कि 2016 की स्थिति ↗\nअंतिम तिथि के लिए एक नोट +\nव्यंग्य / वाल्व पत्राचार नहीं\n\nप्रिय डेडलाइन,\n\nआपको दस दिन दिए गए थे। किसी तरह, कैलेंडर ही एकमात्र चीज़ था जो काम करता रहा।\n\nकृपया कोई भी उत्तर सार्वजनिक अभिलेख में अग्रेषित करें।\n\nसमयरेखाजुलाई 2016 – सितम्बर 2026\nसूचना में अंतिम तिथि:\n10 दिन\nजुलाई2016\nसूचना के बाद से बीता समय:\n3,715 दिन\n20 जुलाई 2016 से 21 सितंबर 2026, के दस्तावेज़ स्नैपशॉट तक का निश्चित गणना, यह कोई लाइव आंकड़ा नहीं है।\nप्रकाशित प्रवर्तन रिकॉर्ड:\nकोई नहीं\nटर्मिनेशन या ब्लॉकों का प्रति-ऑपरेटर खाता स्थित नहीं है।\n\n◀ दिन0–10 — पैमाने पर विस्तार करने की समयसीमादिन3715 — झलक ▶\n\n20 जुलाई2016दस-दिवसीय मांग जारी की गईदिन0\n17 फरवरी2024डीएसए दायित्व लागू हैंदिन2,768\n25 फरवरी2026एनवाई एजी शिकायत की घोषणादिन3,507\n21 सितंबर 2026डॉसियर स्नैपशॉटदिन3715\n\nदस साल बाद सीएसगोफास्ट — जिसे प्रेस रिपोर्टों में 2016 नोटिस के रूप में नामित किया गया है — परिचालन में है: csgofast.com ने 2026-09-19 और 2026-09-21, पर एक लिंक फ़िल्टर ब्लॉक लौटाया, जबकि इसका auth होस्ट steam-login.authtofast.com (पंजीकृत 2026-06-30) ने नहीं किया।\n\nValve की सुरक्षा परिवर्तनों का पूर्ण दिनांकित रिकॉर्ड: सुरक्षा समयरेखा → · वाशिंगटन रिकॉर्ड और प्रवर्तन मानक: नीचे\n\nरिकॉर्ड से पता चलता है: 2016 नोटिस ने 10-दिन की समयसीमा निर्धारित की; Valve पहले से ही एक डोमेन सूची (लिंक फ़िल्टर) संचालित कर रहा था और अपनी OpenID अनुरोधों में प्रामाणिक होस्टनाम प्राप्त कर रहा था; किसी भी ऑपरेटर-विशिष्ट प्रवर्तन रिकॉर्ड का प्रकाशन नहीं किया गया है। सामुदायिक रिपोर्टों में एक मार्केटप्लेस (SkinJar) के खिलाफ 2018 कार्रवाई का वर्णन है, लेकिन वे रिपोर्टें अप्रमाणित हैं और यहाँ उन पर भरोसा नहीं किया गया है।\nसीएसगोफास्ट / सुरक्षित प्रमाणीकरण मार्ग\nघोषित रिटर्न होस्ट का अनुसरण करें।\n\nसहेजे गए मार्ग रिकॉर्ड लिंक csgofast.com के लिए steam-login.authtofast.comअलग होस्टनेम Steam OpenID अनुरोध में शामिल किया जाता है। यह जांचकर्ताओं को एक ठोस पता प्रदान करता है, जिसे वे Valve के फ़िल्टरिंग और प्रवर्तन रिकॉर्ड्स से तुलना कर सकते हैं।\n\nCSGOFast मार्ग और इसके स्रोत की जाँच करें ↗ · सहेजे गए Steam लिंक फ़िल्टर परिणामों की तुलना करें ↗\n\nसार्वजनिक अभिलेख / वाशिंगटन · 2016 → 2026\nदो समयसीमाएँ। एक अनुत्तरित प्रवर्तन मानक।\n20 जुलाई\nValve जुआ साइटों को 10 दिन\n\nउसके वकील की मांग ने चेतावनी दी कि Steam खातों के निरंतर व्यावसायिक उपयोग से खाता समाप्त किया जा सकता है।\n\n27 अलगाव\nवाशिंगटन दबाव डालता हValve\n\nराज्य के जुआ आयोग ने जुआ के लिए स्किन ट्रांसफर रोकने के लिए उठाए गए कदमों के प्रमाण की मांग की और 14 अक्टूबर तक जवाब देने की समयसीमा निर्धारित की।\n\n17 ओसीटी\nValve आरोप खारिज करता है\n\nValve अंतिम तिथि के बाद जवाब दिया, यह विवादित किया कि उसने जुआ की सुविधा प्रदान नहीं की, कहा कि उसने संबंधित खातों को अक्षम कर दिया है, और कहा कि वह सभी के लिए ट्रेडिंग और OpenID बंद नहीं करना चाहता था। जुलाई नोटिसों की प्रेस रिपोर्टों में नाम आने वाले कम से कम एक प्लेटफ़ॉर्म (CSGOFast) एक दशक बाद भी संचालित हो रहा था। ये दोनों तथ्य केवल तभी सही हो सकते हैं जब ऑपरेटर ने निष्क्रिय किए गए खातों को बदल दिया हो; यह दिखाने वाला रिकॉर्ड प्रकाशित नहीं किया गया है। WSGC को इन दोनों तथ्यों के बीच सामंजस्य स्थापित करने के लिए Valve से पूछना चाहिए।\n\n2026\nसितंबर में देखे गए मार्ग2026\n\nरूट रजिस्टर में OpenID और ट्रेडिंग तंत्र (Valve) का उपयोग करते हुए अलग-अलग डोमेन ऑथ होस्ट्स के माध्यम से प्रमाणित होने वाले ई44 प्लेटफ़ॉर्मों का रिकॉर्ड है, जिनमें CSGOFast शामिल है, जैसा कि 2016. में वर्णित है। कौन से ऑपरेटरों को काट दिया गया था, यह दिखाने वाला प्रवर्तन रिकॉर्ड अभी तक तैयार नहीं किया गया है।\n\nआयोग की अपनी ब्रीफिंग · 30 जनवरी 2018\nValve ने जवाब देने के अठारह महीने बाद भी नियामक ने इसे इरादा ही कहा।\n\nएचबी 2881 की सार्वजनिक सुनवाई में अपनी विधायिका को संक्षिप्त जानकारी देते हुए, आयोग ने जुलाई के 2016 बयान का वर्णन अपने शब्दों में किया: Valve इसने स्किन्स जुए को सुगम बनाने के लिए अपने प्लेटफ़ॉर्म के उपयोग पर सख्त कार्रवाई करने का इरादा घोषित किया। उसी पृष्ठ में यह दर्ज है कि उस घोषणा ने उद्योग के पूर्वानुमान को कैसे प्रभावित किया — परिणामस्वरूप अनुमानित 2020 त्वचा-जुआ बाज़ार को से संशोधित किया गया था $19.7 अरब के लिए $670 मिलियनकेवल इस घोषणा के दम पर लगभग 97% की कटौती। पूर्वानुमान में बदलाव आया। इसे औचित्यसंगत ठहराने वाला प्रति-ऑपरेटर प्रवर्तन रिकॉर्ड अभी तक प्रकाशित नहीं हुआ है।\n\nबाजार के आंकड़े आयोग की ब्रीफिंग में पुनरुत्पादित Narus Advisors / Eilers & Krejcik Gaming के अनुमान हैं, आयोग के निष्कर्ष नहीं; उसी दस्तावेज़ में '2016' स्किन सट्टेबाजी को लगभग $5 बिलियन बताया गया है, जिसमें से लगभग $3 बिलियन कैसीनो-शैली की साइटों पर है। प्राप्त किया गया 2026-09-22, SHA-256 c507c9025f93da0aadaf395c4d8882f25973211c318ee8e9b6f18a5b3755e050.\n\nValve की सार्वजनिक 2016 स्थिति और आज की दृश्यमान अवसंरचना को एक साथ रखा जा सकता है। सवाल यह है कि क्या प्रवर्तन निषिद्ध ऑपरेटरों द्वारा उपयोग किए गए खातों और मार्गों तक पहुँच पाया। दस दिन का नोटिस इस बात का प्रमाण नहीं है कि यह नोटिस नामित ऑपरेटरों तक लागू किया गया था। 2018 OPSkins कार्रवाई नामित ऑपरेटर के खिलाफ एकमात्र दर्ज की गई हस्तक्षेप है; 189 प्लेटफ़ॉर्मों की जाँच की गई और प्रत्येक ऑपरेटर का कोई प्रकाशित रिकॉर्ड नहीं है, एकमात्र दर्ज की गई कार्रवाई प्रवर्तन के पैटर्न को नहीं दर्शाती।\n\nवाशिंगटन जुआ आयोग की 2016 सूचना ↗ संग्रहीत 2026-05-20 ↗ · Valve की 17 अक्टूबर 2016 प्रतिक्रिया (दस्तावेज़ की प्रति) ↗ · WSGC की विधायिका को ब्रीफिंग, 30 जनवरी 2018 (स्थानीय प्रति, 4 पृष्ठ) ↗ · wsgc.wa.gov पर वही फ़ाइल ↗ · पुनर्प्राप्ति रिकॉर्ड और हैश ↗ · Valve का 2018 OPSkins एक्शन ↗ संग्रहीत 2026-03-07 ↗ · वर्तमान मार्ग ऑडिट ↗\n\nफॉरेंसिक दीर्घकालिक ऑडिट · 2016 रोकने और मना करने के लक्ष्य\n10-दिवस सूचना दशक: 23 नामित स्थलों का फोरेंसिक उत्तरजीविता ऑडिट\n\n19–20 जुलाई 2016,Valve के जनरल काउंसल कार्ल क्वैकेनबुश ने 23 स्किन जुआ प्लेटफ़ॉर्म्स को औपचारिक रोक-और-निषेध नोटिस जारी किए, उन्हें Steam खातों के व्यावसायिक उपयोग को बंद करने का आदेश देते हुए 10 दिन खाता समाप्त करने और कानूनी कार्रवाई की धमकी के तहत। 3,700 दिनों बाद, एक अनुभवजन्य ऑडिट से प्रवर्तन का असली पैटर्न सामने आता है: कई ऑपरेटरों ने कभी संचालन बंद नहीं किया, अन्य ने समयसीमा के बाद छह साल तक संचालन जारी रखा, और अरबों डॉलर का इकोसिस्टम Valve की ओपनआईडी आर्किटेक्चर का लाभ उठाता रहा।\n\n5+ लाइव\n2026 (CSGOBig, CSGO500, CSGOFast, आदि) में दृढ़ता से संचालित\n6 वर्ष\nक्लोज़र से पहले नोटिस के बाद सबसे लंबा सक्रिय रहने का समय (2022 तक सक्रिय)\n$5.01B\n2016 स्किन सट्टेबाजी की मात्रा (नारस / ईलर्स और क्रेजिक)\n200+\nबाजार के शिखर पर सक्रिय त्वचा जुआ साइटें\nबाकी बचे टाइटन्स · 2024–2026 वित्तीय और ट्रैफ़िक ब्लूप्रिंट\n10-दिवस चेतावनियों से लेकर अपतटीय समूहों तक: बहु-अरब-डॉलर का कारोबार\n\nस्किन जुआ को खत्म करने के बजाय, Valve के '2016' ने एक औद्योगिक विकास को गति दी। बचे हुए ऑपरेटरों ने क्यूरासाओ, बेलीज, साइप्रस जैसी ऑफशोर कॉर्पोरेट इकाइयों के रूप में पुनर्गठन किया, बॉट प्रतिबंधों को बायपास करने के लिए पीयर-टू-पीयर (P2P) ट्रेडिंग का नेतृत्व किया, और अब संसाधित करते हैं 10 प्रति माह दस लाख वेब विज़िट्स और वार्षिक सट्टेबाजी पर दांव की राशि अरबों डॉलर Steam के माध्यम से प्रमाणीकरण जारी रखते हुए:\n\nप्लेटफ़ॉर्म / डोमेन\tजुलाई2016 सूचना\tप्रवर्तन परिणाम और जीवित रहने की स्थिति\tरिकॉर्डेड सत्यापन / प्राथमिक लिंक\nCSGOBig\ncsgobig.com\t10-Day Notice (Jul 2016)\tSTILL LIVE IN 2026\nTemporarily paused, relaunched; authenticates via letmeinbig.com & csgobiglogin.com\tX: @csgobig ↗ · FB: csgobigofficial ↗\nCSGO500\ncsgo500.com / 500.casino\t10-Day Notice (Jul 2016)\tSTILL LIVE IN 2026\nRebranded into 500 Casino (Curaçao license #8048/JAZ2014-037), multi-million monthly turnover\tLive Platform (500.casino) ↗\nCSGOFast\ncsgofast.com\t10-Day Notice (Jul 2016)\tSTILL LIVE IN 2026\nActively operating roulette, crash, and jackpot via steam-login.authtofast.com\tDossier Auth Audit ↗\nCSGOLounge / Dota2Lounge\ncsgolounge.com / dota2lounge.com\t10-Day Notice (Jul 2016)\tSTILL LIVE IN 2026\nPivoted to esports coin wagering and crypto betting; maintained continuous operation\tLive Platform ↗\nCSGOCasino\ncsgocasino.net / csgocasino.gg\t10-Day Notice (Jul 2016)\tLIVE VIA SUCCESSOR (2026)\nDomain redirected; active successor portal operates under csgocasino.gg\tSuccessor Domain ↗\nCSGOatse\ncsgoatse.com\t10-Day Notice (Jul 2016)\tSURVIVED 6 YEARS (ACTIVE TO 2022)\nContinued full gambling operations for six years following Valve's 10-day ultimatum\tX: @CSGOatsecom (Active to 2022) ↗\nCSGOSweep\ncsgosweep.com\t10-Day Notice (Jul 2016)\tSURVIVED TO DEC 2017\nOperated publicly for 17 months after deadline\tX: CSGOSweep Status Dec 2017 ↗\nCSGOWild\ncsgowild.com\t10-Day Notice (Jul 2016)\tSURVIVED TO DEC 2017\nPromoted by major influencers; ran for 1.5 years post-C&D before crypto migration\tX: @Wild (Active Dec 2017) ↗\nCSGOPot\ncsgopot.com\t10-Day Notice (Jul 2016)\tSURVIVED TO SEPT 2017\nOperated high-stakes jackpot betting 14 months past notice\tX: @csgopot (Active Sep 2017) ↗\nCSGODiamonds\ncsgodiamonds.com\t10-Day Notice (Jul 2016)\tSURVIVED TO MID 2017\nRan through 2017 despite admitted outcome tampering for sponsored streamers\tX: @csgodiamondscom (2017) ↗\nCSGOLotto\ncsgolotto.com\t10-Day Notice (Jul 2016)\tCLOSED JULY 2016\nShut down under public scandal; target of federal FTC consent order\tFTC Consent Order (Docket C-4632) ↗\nCSGODouble\ncsgodouble.com\t10-Day Notice (Jul 2016)\tCLOSED JULY 2016\nShut down voluntarily immediately after C&D publication\tX: @CSGODouble (Closed Jul 2016) ↗\nCSGOMassive\ncsgomassive.com\t10-Day Notice (Jul 2016)\tCLOSED 2016\nCeased public operations in late 2016\tX: @csgo_massive ↗\nCSGOStrong\ncsgostrong.com\t10-Day Notice (Jul 2016)\tCLOSED 2016\nCeased public operations in 2016\tFB: csgostrongfree ↗\nSkins2\nskins2.com\t10-Day Notice (Jul 2016)\tCLOSED 2016\nCeased public operations in 2016\tFB: CSNCOM ↗\n\nमंच\tमासिक ट्रैफ़िक (विज़िट्स)\tअनुमानित कारोबार / मात्रा\tनिगम निकाय और क्षेत्राधिकार\tमुख्य नियामक कार्यवाही एवं मॉडल\nCSGOEmpire\ncsgoempire.com\t2.3M — 9.0M / mo\nAvg 6+ min duration; 80% direct\t$1.5B — $2.5B Annual Handle\n>1,000,000 P2P skin trades/mo; $6.4M active liquid order floor\tMoonrail Limited B.V. (Curaçao #148182)\nPayments: JHOLT LTD (Cyprus); Founder: \"Monarch\" (Ossi Ketola)\tPioneered 0% fee P2P item trading; licensed Curaçao OGL/2024/1183/0869\nCSGORoll\ncsgoroll.com\t2.74M — 3.5M / mo\nAvg 9m 23s duration; 16% bounce rate\t$1.0B — $2.0B Annual Handle\nEst. $100M–$200M annual corporate revenue from house edge\tFeral Holdings Limited\nHeadquartered in Belize City, Belize (Reg #171519)\tBanned by Australian ACMA (May 2023); sponsored tier-1 team G2 Esports with underage players\n500 Casino (CSGO500)\n500.casino / csgo500.com\t220K — 425K / mo\n~105k unique monthly visitors\t$100k / week ($5.2M/yr) in Royales\nHigh-roller wagering requirement: $400 wager per $1 rakeback\tPerfect Storm B.V. (Curaçao #150536)\nCuraçao Gaming Control Board license OGL/2024/1354/0882\tBanned by Swedish Spelinspektionen (Nov 2023) for unlicensed targeting of Swedish players\nCSGOBig\ncsgobig.com\t~169,600 / mo\nAvg duration 19m 12s; US primary\tMulti-Million Annual Volume\nMystery boxes, roulette, and case battles\tOperates via auxiliary proxy routing\nletmeinbig.com (reg 2023) & csgobiglogin.com\tTarget of July 2016 C&D; relaunched with proxy auth architecture\nCSGOFast\ncsgofast.com\t~150K — 250K / mo\nGlobal multi-language audience\tMulti-Million Annual Volume\nHigh-velocity roulette and crash games\tOffshore operational entities\nRoutes Steam auth via steam-login.authtofast.com\tTarget of July 2016 C&D; never discontinued operations; active in 2026\nCSGOPolygon\ncsgopolygon.com / plg.bet\t~300K — 500K / mo\nCIS and Eastern European dominance\tMulti-Million Annual Volume\nCrypto & skin roulette, match betting\tSecond-wave target (Oct 2016)\nPivoted to cryptocurrency with mirror domain plg.bet\tSurvived a full decade; continues skin liquidation via third-party APIs\nदूसरी लहर: क्यों Valve ने 43और अन्य साइटों को कुल मिलाकर C&D पत्र भेजे\n\n17 अक्टूबर 2016, Valve के कानूनी सलाहकार ने वाशिंगटन राज्य जुआ आयोग को औपचारिक रूप से सूचित किया कि प्रारंभिक 23 नोटिस के बाद जुलाई 19, में Valve ने रोक-और-परहेज़ पत्र भेजे थे। 20 से अधिक अतिरिक्त स्किन जुआ साइटें (जिससे आधिकारिक कुल संख्या 43 से ऊपर हो गई)। इस दूसरी लहर की आवश्यकता इसलिए पड़ी क्योंकि प्रारंभिक सूची में अकारण दुनिया के सबसे बड़े और सबसे कुख्यात जुआ केंद्रों को शामिल नहीं किया गया था:\n\nCSGOJackpot.com: त्वचा जैकपॉट्स का ऐतिहासिक संस्थापक, जिसने संघीय अभियोग की धमकी के तहत बंद होने से पहले सैकड़ों मिलियन का लेन-देन संभाला।\nCSGOShuffle.com: जुलाई के2016-स्ट्रीमिंग घोटाले के केंद्र में स्थित यह साइट, जहाँ Twitch स्ट्रीमर PhantomL0rd ने कंपनी के 33% का गुप्त रूप से स्वामित्व रखा था और घर के फंड के साथ ऑड्स में हेरफेर करते हुए पकड़ा गया था।\nमैक्रो इकोसिस्टम (200+ ऑपरेटर): Narus Advisors और Eilers & Krejcik Gaming द्वारा किए गए उद्योग अनुसंधान के अनुसार, 200 से अधिक विशिष्ट स्किन जुआ साइटें 2016, में संचालित थीं, जिन्होंने 3.03 मिलियन सक्रिय खिलाड़ियों से $5.01 बिलियन का सट्टेबाजी वॉल्यूम उत्पन्न किया। Valve के 43 पत्रों ने सक्रिय बाजार के 20% से भी कम को संबोधित किया।\nSteam त्वचा जुआ पर आधिकारिक सरकारी और नियामक जांच\n\nत्वचा जुआ की घटना कई औपचारिक वैधानिक जांचों, प्रवर्तन कार्रवाइयों और सरकारी स्थिति पत्रों में दर्ज की गई है:\n\n1. वाशिंगटन राज्य जुआ आयोग (WSGC) (2016–2018)\n\n5 अक्टूबर 2016 को औपचारिक 'सीज़ एंड डिस्ट' मांग जारी की; 30 जनवरी 2018 पर विधायी ब्रीफिंग प्रकाशित की, जिसमें यह दस्तावेजीकरण किया गया कि स्किन्स नकद समतुल्य हैं और $5.0B की स्किन सट्टेबाजी मात्रा की रिपोर्टिंग की गई।\n\nWSGC विधायी रिपोर्ट पीडीएफ (स्थानीय प्रति) ↗\n2. U.S. संघीय व्यापार आयोग (FTC) (सितंबर 2017, डॉकेट C-4632)\n\nधोखाधड़ीपूर्ण व्यवहार और प्लेटफ़ॉर्म नियंत्रण की जानकारी न देने के आरोप में CSGOLotto के मालिक ट्रेवर मार्टिन और थॉमस कैसल के खिलाफ त्वचा जुआ से संबंधित पहली संघीय नियामक प्रवर्तन कार्रवाई।\n\nएफटीसी निर्णय और सहमति आदेश ↗\n3. यूके जुआ आयोग (यूकेजीसी) स्थिति पत्र और युवा ऑडिट\n\nगेम में स्किन्स को औपचारिक रूप से जुआ अधिनियम के तहत \"पैसा या पैसे के बराबर मूल्य\" के रूप में वर्गीकृत किया गया था2005.। बाद के सर्वेक्षणों में पाया गया कि 11–16 वर्ष की आयु के 11% से अधिक बच्चों ने वीडियो गेम पर स्किन्स पर दांव लगाया था।\n\nयूकेजीसी अनुसंधान भंडार ↗\n4. ऑस्ट्रेलियाई सीनेट पर्यावरण और संचार जांच (2018)\n\nपर संघीय संसदीय रिपोर्ट संयोग-आधारित वस्तुओं के लिए गेमिंग माइक्रो-लेनदेनValve के लूट बॉक्स मैकेनिक्स, सेकेंडरी मार्केट कैशआउट्स, और नियामक परिहार का मूल्यांकन।\n\nऑस्ट्रेलियाई संसद की जांच ↗\nउत्कृष्ट मांग\n\nप्रवर्तन रिकॉर्ड प्रकाशित करें: किन जुआ खातों और बॉट्स को अक्षम किया गया, किन रिटर्न होस्ट्स को प्रतिबंधित किया गया, और किन व्यावसायिक सेवाओं को अनुमति दी गई। सार्वजनिक प्रतिबंध और होमपेज चेतावनी यह साबित नहीं करतीं कि मूल संचालन को रोका गया था।\n\nभाग बी — नियम और प्रवर्तन अभिलेख · धारा 12\nहोस्टनेम पहले से ही अनुरोध में है।\nप्रसंग और स्रोत सीमाएँ\n\nValve यह पहले से ही डोमेन सूची (लिंक फ़िल्टर) रखता है और प्रत्येक OpenID अनुरोध में auth होस्टनेम प्राप्त करता है। नीचे दिया गया प्यूडोकोड दोनों को जोड़ने की तार्किक संरचना दिखाता है। कोई सार्वजनिक प्रमाण नहीं है कि Valve ऐसा करता है।\n\nValve पहले से ही एक डोमेन ब्लॉकलिस्ट चलाता है। Valve पहले से ही प्रत्येक OpenID अनुरोध में लॉगिन होस्ट प्राप्त करता है। कुछ भी बनाने की ज़रूरत नहीं है — दोनों को जोड़ना है। यह एक होस्टनेम लुकअप है जो Valve द्वारा स्वयं बनाए गए एक सूची के खिलाफ किया जाता है। नीचे दिया गया प्यूडोकोड केवल एक उदाहरण है, यह Valve का कार्यान्वयन नहीं है।\n\nन्यायिक_स्वचालितप्रतिबंध.पाइ\n# उदाहरण स्वरूप छद्म-कोड — Valve.block_domain() और flag_session_as_mitm() वास्तविक API कॉल नहीं हैं। यह प्रॉक्सी प्रामाणिकता डोमेन के खिलाफ एक शमन Valve द्वारा लागू की जा सकने वाली तार्किक संरचना को दर्शाता है, न कि वास्तविक Valve की आंतरिक कार्यप्रणाली को।\n# चित्रण: आने वाले OpenID अनुरोध पर एक जाँच का तार्किक स्वरूप\nपरिभाषा ऑडिट_ओपनआईडी_रिक्वेस्ट(अनुरोध):\nब्लॉक किए गए_मूल = डेटाबेस.ब्लैकलिस्ट किए गए प्लेटफ़ॉर्म प्राप्त करें()\nप्रॉक्सी_डोमेन = request.params.प्राप्त करना('openid.realm')\nलक्ष्य पुनर्निर्देश = request.params.प्राप्त करना(ओपनआईडी.रिटर्न_टू)\n\n# तर्क: यदि प्रॉक्सी किसी प्रतिबंधित साइट पर वापस राउट करती है, तो प्रॉक्सी को प्रतिबंधित करें।\nके लिए साइट में अवरुद्ध_मूल:\nयदि साइट में लक्ष्य पुनर्निर्देश:\nValve.ब्लॉक_डोमेन(प्रॉक्सी_डोमेन)\nValve.सत्र को मिडिलमैन हमले के रूप में चिह्नित करें(request.session)\n# परिणाम: उस होस्ट के लिए लॉगिन अनुरोध अस्वीकार कर दिया गया है।\n\nनिरीक्षण:\nजब कोई मुख्य डोमेन पहले से ही लिंक फ़िल्टर (e.g.howl.gg, blocked 2026-09-18/19/21) में हो और उसका auth होस्ट (howl.uno) उस साइट के लॉगिन बटन से आने वाले OpenID अनुरोध में दिखाई दे, तो यह संबंध Valve को उसके अपने अनुरोध डेटा से स्पष्ट रूप से दिखाई देता है। यह जाँच स्वचालित की जा सकती है; इसे चलाया जाए या नहीं, यह स्वचालित नहीं है।\nदस्तावेजीकृत और रिपोर्ट किए गए पूर्वनिर्णय\n\nValve रिकॉर्ड पर कम से कम एक बार एक तीसरे पक्ष के ऑपरेटर के खिलाफ हस्तक्षेप किया है: 2018 में इसने ExpressTrade सिस्टम पर OPSkins की पहुंच रद्द कर दी (Valve की घोषणा ↗ संग्रहीत 2026-03-07 ↗2018 की सामुदायिक रिपोर्टों में भी एक मार्केटप्लेस (SkinJar) के एक्सेस खोने का वर्णन है; ये रिपोर्टें अप्रमाणित हैं और तंत्र परिणाम से अनुमानित है, न कि किसी प्रकटीकृत प्रक्रिया से।\n\nपूर्व उदाहरण क्या स्थापित करता है:\n\nValve यह जब चाहे किसी तीसरे पक्ष के ऑपरेटर की पहुँच काट सकता है। CSGOFast, जिसे जुलाई के 2016 नोटिस से संबंधित प्रेस रिपोर्टों में नामित किया गया था, 2026-09-21 पर ऑपरेट कर रहा था, जिसमें auth होस्ट 2026-06-30 पंजीकृत था, जिसने कोई लिंक फ़िल्टर ब्लॉक नहीं लौटाया। किसी एक ऑपरेटर को काटा गया और अन्य को नहीं, इसका कोई प्रकाशित मानदंड नहीं बताता।\n\nपंजीकरण की तारीख क्या दिखाती है और क्या नहीं दिखाती\n\nएक auth होस्ट की पंजीकरण तिथि उस समय की न्यूनतम सीमा है जब होस्ट पहली बार OpenID अनुरोध में प्रकट हो सकता था; यह निरंतर उपयोग स्थापित नहीं करती। sc-auth.netउदाहरण के लिए, इसे 2019-04-02 (RDAP) पर पंजीकृत किया गया था और सितंबर 2026 में Skin.Club के Steam लॉगिन फ्लो में देखा गया था; इन दोनों तारीखों के बीच क्या हुआ, यह सार्वजनिक रिकॉर्ड में नहीं है।\n\nतुलनात्मक ऑडिट: API अनुपालन मानक\nप्रवर्तन आयाम\tGitHub API नियम\tSteam वेब API (Valve)\n1. Compliance Neutrality\tPublished, uniform rules. Documented rate limits (e.g. 5,000 calls/hr for authenticated users, 15,000/hr for GitHub Enterprise Cloud organisations) and published acceptable-use policies apply to every account.\tNo published criteria. Individual accounts are terminated under the automation and commercial-use clauses (archived complaints), while no per-operator enforcement record for commercial platforms has been published.\n2. OpenID / Auth Proxy Abuse\tGitHub's published policies allow OAuth apps and tokens to be suspended or revoked for abuse, and its documentation describes automatic revocation of exposed tokens (authors' summary of GitHub documentation).\tSeparate-domain auth hosts observed in Steam OpenID flows (e.g. rbsnin.com, howl.uno, sc-auth.net) returned no Link Filter block on 2026-09-21 while their main domains did.\n3. Monetization of Abuse\tGitHub takes no transaction fee on items moved by third-party automation; its revenue model is subscriptions and marketplace listings.\tValve sells the case keys that produce the items, and the Community Market charges a combined fee of about 15% on sales completed inside the Market. No figure for revenue attributable to third-party platforms is estimated here.\n4. Evasion Loop Lifespans\tSuspended OAuth client IDs stop working platform-wide at suspension; the documentation does not publish a time-to-action figure and none is assumed here.\tSeparate-domain auth hosts with registration dates from 2011 to September 2026 returned no Link Filter block in the checks of 2026-09-19 and 2026-09-21. Registration date is a lower bound on possible use, not proof of continuous use.\nस्रोत: GitHub स्तंभ — GitHub द्वारा प्रकाशित API दर-सीमा और प्लेटफ़ॉर्म-नीति दस्तावेज़ीकरण (लेखकों का सारांश, उद्धृत नहीं) · Steam स्तंभ — Link Filter की 2026-09-19 और 2026-09-21 की जाँचें (linkfilter-recheck-2026-09-21.json), RDAP रजिस्ट्री (domain-registration.json) और संग्रहीत सहायता शिकायतें (साक्ष्य संग्रह).\nभाग बी — नियम और प्रवर्तन अभिलेख · अनुभाग 13\nऑफ़-Steam मूल्य अंतर\n\nयह वस्तु एक Steam की इन्वेंटरी में रखी गई है; बिक्री कहीं और होती है। एक फैक्ट्री न्यू AWP Dragon Lore था 62 CSFloat पर लाइव ऑफ़र; सबसे सस्ता मांगा गया $10,623.95Steam का अपना बाजार लगभग $1,800. से अधिक का मांगा गया मूल्य प्रदर्शित नहीं कर सकता। देखी गई उच्च कीमत पर बेचने के लिए, मालिक को ऑफ-Steam खरीदार या बाज़ार की आवश्यकता होती है। वस्तु और उसका हस्तांतरण अभी भी Steam पर निर्भर करते हैं।\n\nWhat this means — the Community Market listing ceiling\n\nSteam’s own market refuses a listing above roughly $1,800. A seller may ask less, never more. Items whose market price sits above that line therefore cannot be sold at that price on Steam at all — which is the mechanism that moves those sales to third-party venues while the item itself never leaves Valve’s inventory system.\n\nSection 13 — the off-Steam price gap →\n\nप्रसंग और स्रोत सीमाएँ\n\nइस अनुभाग में तीन अलग-अलग गणनाएँ दी गई हैं और वे परस्पर प्रतिस्थापन योग्य नहीं हैं। 245 यह उन CS2 आइटम-नाम श्रेणियों की संख्या है जिनकी सबसे सस्ती सक्रिय पेशकश केवल CSFloat पर $1,800 से अधिक थी, 20 सितंबर 2026. 241 यह वही सेट है, जिसमें से उन चार श्रेणियों को हटा दिया गया है, जिन्हें CSFloat की $100,000 की ऊपरी सीमा पर पिन किया गया है, और यही वह पैनल है जिस पर $13.63M के निचले फर्श की गणना की जाती है। 248 यह एक अलग स्नैपशॉट है: 23 सितंबर 2026. पर पांच मार्केटप्लेस में से दो या अधिक द्वारा कैप से ऊपर कीमत वाली श्रेणियाँ। मार्केटप्लेस ओवरलैप करते हैं, इसलिए विभिन्न प्लेटफ़ॉर्म के आंकड़ों को कभी भी जोड़ा नहीं जाना चाहिए। यहाँ प्रत्येक आंकड़ा माँग मूल्य है, पूरी हुई बिक्री नहीं, और इनमें से कोई भी राजस्व, टर्नओवर या लाभ नहीं है — न Valve के लिए, न किसी और के लिए। PriceEmpire के सूचीबद्ध मान उस साइट द्वारा प्रकाशित गोल-मोल अनुमान हैं, और इसका Steam कार्ड अन्य Steam गेम्स की वस्तुओं को भी कवर करता है, इसलिए तुलना के दायरे समान नहीं हैं।\n\nएक आइटम। दो मूल्य प्रणालियाँ।रिकॉर्ड का पालन करें\nचरण 3 / 3\n\nउस अनुरोध पर, विक्रेता को एक ऑफ-Steam स्थल या खरीदार की आवश्यकता होती है। वस्तु अभी भी Steam की इन्वेंटरी और ट्रांसफर सिस्टम पर निर्भर करती है।\n\nस्ट्रीमलगभग $1,800प्रकाशित सामुदायिक बाजार सूचीकरण सीमा\nसहेजा गया कैटलॉग$10,623.95फ़ैक्टरी न्यू AWP ड्रैगन लॉर फ़्लोर आस्क\nनिर्भरताअभी भी एक Steam आइटमइन्वेंटरी और ट्रांसफर Steam पर ही बने रहते हैं।\n01 / आइटमValve गेम सूचीSteam में आयोजित CS2 या Dota 2 आइटम\n02 / छतलगभग $1,800 पर Steamएक मार्केट लिस्टिंग के लिए अधिकतम मूल्य\n03 बाहर पूछेंड्रैगन लोअर के लिए $10,623.95पुरानी तस्वीर में सबसे सस्ता CSFloat ऑफर\n04 / डिलीवरीSteam श्रृंखला में बना रहता हैस्वामित्व और वस्तु हस्तांतरण इसकी प्रणाली पर निर्भर करते हैं।\nबाज़ार संरचना · दिनांकित झलक, 20 सितंबर 2026\nमूल्य अंतर मापनीय है।\n\nहमने उन आइटम-नाम श्रेणियों की गिनती की जिनकी सबसे सस्ती सक्रिय पेशकश सख्ती से $1,800. से ऊपर थी। CSFloat और Skinport अलग-अलग स्नैपशॉट हैं जिनकी CS2 इन्वेंटरी ओवरलैप करती है; उनकी गिनती को जोड़ा नहीं जा सकता। बाहरी ऑफ़र्स दिखाते हैं कि उच्च मांगी गई कीमतें कहां पोस्ट की गई हैं, जबकि Steam अभी भी आइटम के स्वामित्व और हस्तांतरण को नियंत्रित करता है।\n\n245CS2 श्रेणियाँ · CSFLOAT\n166CS2 श्रेणियाँ · स्किनपोर्ट\n3डोटा 2 श्रेणियाँ · स्किनपोर्ट\n$10,623.95ड्रैगन की कथा फर्श पूछो\n\nड्रैगन लोअर: 62 सक्रिय CSFloat फैक्ट्री न्यू श्रेणी में ऑफ़र करता है; प्रदर्शित फ़्लोर एक अनुरोध है, पुष्टि की गई बिक्री नहीं। Steam आइटम को कम कीमत पर सूचीबद्ध करने की अनुमति देता है, लेकिन देखी गई उच्च फ़्लोर पोस्ट नहीं कर सकता। Valve का 2016 बयान पुष्टि करता है कि वह OpenID और Steam ट्रेडिंग इंफ्रास्ट्रक्चर का उपयोग करने वाले जुआ संचालकों से अवगत है। किसी विशेष तृतीय-पक्ष मार्केटप्लेस द्वारा Valve के नियमों का उल्लंघन किया गया है या नहीं, यह अलग से स्थापित किया जाना चाहिए।\n\nपूरा रजिस्टर निरीक्षण करें →CSFloat जेसन ↗Skinport जेसन ↗Valve का 2016 बयान ↗\nसीधे CSFLOAT API / दिनांकित स्नैपशॉट$13.63M\n\nमें न्यूनतम समग्र अनुरोधित मूल्य 241 आइटम श्रेणियाँ और 3,395 सक्रिय ऑफ़र. प्रत्येक श्रेणी की सबसे सस्ती बोली × उसकी ऑफ़र संख्या के रूप में गणना की गई। CSFloat की $100,000 की ऊपरी सीमा पर पिन की गई चार श्रेणियों को इस रूढ़िवादी पैनल से बाहर रखा गया है।\n\nडॉलर की राशि क्या दर्शाती है\n\nये ऑफ़र कम से कम का प्रतिनिधित्व करते हैं $13,631,888.25 पोस्ट किए गए इस सीमित CSFloat उपसमूह के लिए पूछी गई कीमतें। चार उच्चतम मूल्य श्रेणियों को शामिल करने पर $14,231,888.25. यह एक है सक्रिय अनुरोधों पर सीमा, न तो पूरी हुई बिक्री, न नकद कारोबार, न लाभ और न ही पूरा CS2 बाज़ार।\n\n245-पंक्ति CSFloat स्नैपशॉट से पुनः गणना करें ↗\nमूल्यसम्राज्य / सूचीबद्ध मूल्यSteam: #15 का 39\nकई स्थल Steam से अधिक डॉलर मूल्य सूचीबद्ध करते हैं।\nयूयूस्किन्स\n$133.8M\nयू-पिन 898\n$127.5M\nबफ़।163\n$104M\nMoon.Market\n$100.3M\nWhite.Market\n$89.6M\nBuff.Market\n$86.7M\nSteam\n$31M\n\nछह सबसे बड़े प्रदर्शित मान और Steam। PriceEmpire इन आंकड़ों को गोल करता है; Steam दिखाता है। $31Mप्रदर्शित डॉलर मूल्यों के आधार पर चौदह सूचीबद्ध स्थल इससे आगे हैं।\n\nप्राइसएम्पायर / ऑफर काउंटSteam: #1 का 39\nSteam अभी भी ऑफ़र्स की संख्या में आगे है।\nSteam\n32.2एम\nयू-पिन 898\n5.9एम\nसी5गेम\n4.6एम\nहेलोस्किन्स\n4.4एम\nSkinport\n3.8एम\n\nSteam दिखाता है 32.2एम ऑफ़र्स। ऑफ़र्स की संख्या और कुल मांगा गया मूल्य अलग-अलग सवालों का जवाब देते हैं; कई कम कीमत वाली लिस्टिंग गिनती में हावी हो सकती हैं।\n\nस्रोत: प्राइसएम्पायर की सार्वजनिक तुलना ↗ संचित 2026-09-21 ↗, कैप्चर क2026-09-2019:03यूटीसी; तिथि 39-पंक्ति निष्कर्षण ↗. इसके आंकड़े गोल-मोल अनुमान हैं, और इन्वेंटरी विभिन्न साइटों पर ओवरलैप हो सकती है। Steam का कार्ड अन्य Steam खेलों की वस्तुओं का भी वर्णन करता है, इसलिए दायरे समान नहीं हैं। सूचीबद्ध मूल्य पूछी जाने वाली कीमतों को मापता है, बिक्री या राजस्व को नहीं।\n42\nएक और स्रोत / स्टीमएनालिस्ट\nव्यावसायिक पारिस्थितिकी तंत्र स्पष्ट रूप से दिखाई दे रहा है।\n\nSteamAnalyst की मार्केटप्लेस निर्देशिका संग्रहीत 2026-07-19 ↗ 42 को तीसरे पक्ष के CS2 मार्केटप्लेस के रूप में सूचीबद्ध करता है, साथ ही Steam को भी, और 43 प्रविष्टियों के लिए 32 का हालिया मूल्य डेटा प्रदान करता है। PriceEmpire अपने स्वयं के समावेशन मानदंडों के तहत 39 मार्केटप्लेस को सूचीबद्ध करता है। नामित व्यवसाय, सार्वजनिक प्रस्ताव, दृश्यमान कीमतें: यह अर्थव्यवस्था निरीक्षण के लिए खुली है।\n\nसीलिंग ही तंत्र है: बिक्री भाप छोड़ती है, वस्तु नहीं।\n\nएक लाइसेंस प्राप्त स्नैपशॉट में कैद पाँच मार्केटप्लेस, 248 CS2 आइटम श्रेणियों में से दो या अधिक की कीमतें स्वतंत्र रूप से Steam की लगभग $1,800 लिस्टिंग सीमा से ऊपर हैं — और इनमें से प्रत्येक Steam पर अनुपस्थित है।. उसी स्नैपशॉट ने पूरे कैटलॉग को कीमत के अनुसार वर्गीकृत किया: Valve की मार्केट में अपनी कैप से नीचे की आइटम श्रेणियों का 95.3% और उससे ऊपर की श्रेणियों का 1.9% होता है। यह पतन गिरती मांग का अनुसरण नहीं करता; यह ठीक प्रकाशित नियम पर ही लागू होता है। उन कीमतों पर बेचने के लिए एक बाहरी खरीदार या बाज़ार की आवश्यकता होती है, जबकि Steam अभी भी इन्वेंटरी और हस्तांतरण को नियंत्रित करता है — व्यवसाय Valve के चेकआउट से बाहर चला जाता है और डिलीवरी Valve के इन्फ्रास्ट्रक्चर पर ही रहती है।\n\nSteam बाज़ार अक्सर पूछे जाने वाले प्रश्न ↗संचित 2026-09-21 ↗Steam सब्सक्राइबर समझौता ↗संचित 2026-09-21 ↗पाँच-मार्केटप्लेस एटलस डेटासेट ↗प्रोवेंन्स प्रदर्शनी ↗पहले CSFloat स्नैपशॉट ↗Skinport झलक ↗प्राइसएम्पायर ↗संचित 2026-09-21 ↗स्टीमएनालिस्ट ↗संग्रहीत 2026-07-19 ↗मूल्य-अंतर रजिस्टर ↗मूल्य-सीढ़ी एटलस ↗\n\nभाग C — कानूनी ढाँचे\nभाग C — कानूनी ढाँचे · अनुभाग 14 · कार्मिक पहुँच\nसुरक्षा उपायों को कौन रीसेट कर सकता है?\nप्रसंग और स्रोत सीमाएँ\n\nAPI खाते की सुरक्षा उन लोगों पर भी निर्भर करती है जो खाते को पुनः प्राप्त कर सकते हैं, निजी रिकॉर्ड की जांच कर सकते हैं या इसकी सुरक्षा व्यवस्थाओं को रीसेट कर सकते हैं। जांच को उन विशेषाधिकार प्राप्त कार्यों का उतना ही बारीकी से अनुसरण करना चाहिए जितना कि ईमेल खाता दुरुपयोग का।\n\nखाता वसूली एक सहायता एजेंट को खाते को उसके मालिक से अलग करने की शक्ति देती है। Valve ने लिखित रूप में, दो बार — फरवरी 2023 और नवंबर 2025 — की पुष्टि की है कि इस शक्ति का उपयोग गलत लोगों को खाते सौंपने के लिए किया गया था। तीस-तीन महीने के अंतराल पर, एक ही चैनल के माध्यम से। नीचे: उस पहुँच का मूल्य, छह स्रोत-आधारित मामले, और लॉग Valve के पास प्रत्येक मामले के लिए है और जिसे उसने किसी को नहीं दिखाया।\n\nसंरक्षित गवाही / 9 मई 2025\nएक रिकवरी टिकट जिसने खाते की सुरक्षा अक्षम कर दी, और रिपोर्ट किए गए $10,000 के नुकसान\n\nएकत्रित समर्थन अभिलेखागार में एक उपयोगकर्ता ने बताया कि Steam समर्थन ने पासवर्ड रीसेट किया और खाता सुरक्षा अक्षम कर दी, जब किसी अन्य व्यक्ति ने रिकवरी टिकट जमा किया था। लेखक का कहना है कि खाता वर्षों से निष्क्रिय था, उसमें 2016–2017 से वस्तुएँ रखी थीं और उसमें Steam गार्ड, एक लिंक किया गया फोन और संग्रहीत रिकवरी कोड थे।\n\n\"Steam Support still gave someone else access to my account.\"\n\nप्रथम-पुरुष आरोप, संरक्षित steam_support_tickets_MEGA.json, रिकॉर्ड 110. पूरा कैप्चर किया गया पोस्ट पढ़ें ↗\n\nयह किसी एक उपयोगकर्ता की बदकिस्मती नहीं है। वही दरवाज़ा — एक सहायता अनुरोध जो खाते को उस व्यक्ति को स्थानांतरित कर देता है जो पुराना डेटा प्रदान करता है — नीचे दिए गए लेजर में हर मामले में दर्ज किया गया प्रवेश मार्ग है, और Valve ने इसे दो बार लिखित रूप में रखा है।\n\nमालिक वह बहस नहीं जीत सकता। रिकवरी पहली सीडी कुंजी, पहला ईमेल, पहला कार्ड, पहला फोन नंबर मांगती है। ये तथ्य Valve के डेटाबेस में हैं, और सपोर्ट-साइड एक्सेस इन्हें पढ़ती है — बताया गया है कि यह पंद्रह साल पीछे तक जाती है। आपके पास आपकी फ़ाइल की एक प्रति रखने वाला व्यक्ति हमेशा आपके बारे में आपकी तुलना में अधिक इतिहास पेश कर सकता है। लक्षित खातों का चयन इस तरह से किया गया कि वे वर्षों से निष्क्रिय हों, उच्च-मूल्य वाले हों, और अक्सर सेकंड-हैंड खरीदे गए हों, ताकि धारक को कभी मूल कुंजी का पता ही न चले। इसके बाद उन खातों को पूरी तरह से हटा दिया गया, जिससे आइटम-इतिहास की वह श्रृंखला टूट गई जिसका उपयोग समुदाय किसी स्किन का पता लगाने के लिए करता है — एक ऐसा हटाना जो एक साधारण उपयोगकर्ता मानक प्रतीक्षा अवधि के बिना नहीं कर सकता।\n\nन्यूनतम विशेषाधिकार / ओवास्प A01\n\nSteam रिकवरी विशेषाधिकार कार्य तक सीमित होने चाहिए, स्वतंत्र रूप से समीक्षा और लॉग किए जाने चाहिए। ऑडिट करें कि कौन प्रमाण-पत्र रीसेट कर सकता है, ईमेल खाते को हटा सकता है, ईमेल सुरक्षा गार्ड को हटा सकता है, बिलिंग रिकॉर्ड पढ़ सकता है या खाता डेटा निर्यात कर सकता है। OWASP पहुँच-नियंत्रण मार्गदर्शन ↗ संग्रहीत 2026-09-20 ↗\n\nव्यापक समर्थन पहुँचपहुँच-दायरा जोखिम\nभंडार से परे\n\nयदि व्यापक समर्थन पहुँच का दुरुपयोग किया जाए, तो निजी टेलीमेट्री प्रोफाइलिंग, लक्षित फ़िशिंग और निगरानी का एक उपकरण बन सकती है। संभावित पीड़ितों में साधारण उपयोगकर्ता, सैन्यकर्मी, सार्वजनिक हस्तियाँ और उनके परिवार शामिल हैं। यह एक खतरा मॉडल है; सटीक अनुमतियों के लिए पहुँच-नियंत्रण रिकॉर्ड की आवश्यकता होती है।\n\n01 आईपी इतिहास और स्थान\nआईपी लॉग्स नेटवर्क के इतिहास और अनुमानित स्थान को उजागर कर सकते हैं। वे स्वयं में सटीक भौतिक गतिविधियों को स्थापित नहीं करते।\n02 डिवाइस फिंगरप्रिंटिंग\nडिवाइस पहचानकर्ता, जहाँ एकत्रित और सुलभ हों, सत्रों और खातों को जोड़ सकते हैं।\n03 गतिविधि टेलीमेट्री\nलॉगिन टाइमस्टैम्प और सत्र रिकॉर्ड दिनचर्या का खुलासा कर सकते हैं, जिसमें सार्वजनिक प्रोफ़ाइल पर अदृश्य गतिविधियाँ भी शामिल हैं।\n04 संचार और संपर्क\nरखे गए संदेशों या संपर्क जानकारी तक पहुंच प्रोफाइलिंग और सोशल इंजीनियरिंग की संभावनाओं को बढ़ा देगी।\n05 पहचान उजागर करना\nमूल ईमेल, फोन और भुगतान रिकॉर्ड एक छद्म नाम वाले खाते को किसी व्यक्ति से जोड़ सकते हैं।\n06 डेटा पुनर्विक्रय और जवाबदेही\nनिर्यात की गई लक्षित सूचियाँ लक्षित धोखाधड़ियों का समर्थन कर सकती हैं। कार्यकर्ता, पहुँच स्थान, प्राप्तकर्ता और हस्तांतरणों की पहचान करें; केवल स्थान से न तो पहुँच स्थापित होती है और न ही कानूनी प्रतिरक्षा।\n\nValve अपने में आईपी लॉगिंग, डिवाइस जानकारी, भुगतान रिकॉर्ड और तृतीय-पक्ष सहायता प्रदाताओं का वर्णन करता है। गोपनीयता नीति §§ 3, 5.2 संचित 2026-09-21 ↗नीति तीसरे पक्ष को समर्थन तक पहुँच की अनुमति देती है — वह ऑडिट ट्रेल, जो यह दिखाता कि किस ठेकेदार ने किस श्रेणी तक कब और किस प्राधिकरण के तहत पहुँच की, प्रकट नहीं किया गया है।\n\nअनुभाग 14.1 · रजिस्टर · जून 2022 → नवंबर 2025 · प्रत्येक आंकड़ा स्रोत सहित\nValve दरवाज़ा दो बार बंद हुआ, तेईस महीने के अंतराल पर। यह कभी बंद नहीं हुआ।\n\nछह रिपोर्ट किए गए मामले जिनमें खाते Steam के स्वयं सहायता अनुरोध चैनल के माध्यम से, या उन प्रमाण-पत्रों के माध्यम से लिए गए थे जिन्हें वह चैनल सुरक्षित रखता है। प्रत्येक राशि वह आंकड़ा है जिसे उद्धृत स्रोत ने प्रकाशित किया था, और प्रत्येक स्रोत का नाम बताया गया है। छह में से दो मामलों में पूरी राशि वापस कर दी गई। उनके और बाकी के बीच अंतर यह नहीं था कि क्या हुआ — बल्कि यह था कि कौन देख रहा था।\n\nValve, लिखित रूप में — फरवरी 2023\"The items in question were removed from your account because they were received from an account that was compromised through a support help request, for which the CS:GO team takes responsibility. We have reversed the trades and removed them from any account which received them.\"Steam एचएफबी की वस्तुओं के प्राप्तकर्ता को समर्थन उत्तर, द्वारा पुनरुत्पादित डेक्सेर्टो, 21 फरवरी 2023 ↗ संग्रहीत 2025-08-18 ↗\nValve, फिर से लिखते हुए — नवंबर 2025 · 33 महीने बाद\"A support technician that handled the help request failed to follow our process which resulted in your account restored to someone else. I apologize for this error.\"Steam Hawkeye337 को उत्तर, उद्धृत डेक्सेर्टो, 14 नवम्बर 2025 ↗\n21 जून2022\nHFB — खेल में सबसे बड़ी इन्वेंटरी$2,000,000+ · फरवरी के 2023 फॉलो-अप में बढ़ाकर $3,000,000+ किया गया\n\nसात सवेनियर AWP ड्रैगन लॉर्स और #1 ब्लू जेम करम्बिट, वह चाकू अकेले ही लगभग $1.26 मिलियनखाता तीन साल से निष्क्रिय था, लेकिन मोबाइल ऑथेंटिकेटर अभी भी सक्रिय था; फिर भी ईमेल और पासवर्ड सपोर्ट रिकवरी मार्ग के माध्यम से बदल दिए गए।\n\nचीज़ों से पहले पैसा निकल गया। एक रिपोर्ट के अनुसार $200,000+ बिक्री से प्राप्त आय का एक हिस्सा पहले ही market.csgo.com के माध्यम से निकाल लिया गया था — एक ऐसा मार्केटप्लेस जो नकद और क्रिप्टो में निपटान करता है। ट्रेड को रिवर्स करने पर एक स्किन वापस मिलती है। यह उस नकद को वापस नहीं करता जिसे पहले ही बैंक में जमा कर लिया गया है।\n\nऔर मरम्मत टूट गई। एक खरीदार ने अपना Souvenir Dragon Lore इन-गेम स्टोरेज यूनिट में स्थानांतरित कर दिया। Valve की रोलबैक स्क्रिप्ट अपने कंटेनर के अंदर नहीं देख सकी, इसलिए उसने मालिक को एक नई प्रति जारी की और छिपी हुई प्रति को वैसे ही छोड़ दिया — Valve ने एक की नकल की। $130,000 चोरी को रद्द करने की कोशिश करते समय एक आइटम। इसे आइटम आईडी मिलान और समुदाय की रिपोर्टिंग से पकड़ा गया, और एक महीने बाद, जुलाई 2022. में हटा दिया गया। खरीदार को BUFF द्वारा रिफंड किया गया, न कि Valve द्वारा। इस तरह की आपातकालीन सुधार कोई नियंत्रण नहीं है; यह वह है जो एक प्लेटफ़ॉर्म तब करता है जब उसके पास कोई नियंत्रण नहीं होता।\n\nडेक्सेर्टो, 21 जून 2022 ↗ संग्रहित 2022-07-02 ↗ · कास्परस्की ↗ · प्रति कैश-आउट आंकड़ा Esportfire, 22 जून 2022 ↗ संग्रहीत 2026-05-15 ↗, वहाँ कई Twitter स्रोतों को श्रेय दिया गया · प्रतिलिपि और प्रतिलिपि-मुक्ति प्रति ईस्पोर्ट्स बेटिंग, 14 जुलाई 2022 ↗\n\nपुनर्स्थापितव्यापार उलट दिए गए। उन वस्तुओं को उन लोगों की इन्वेंटरी से वापस ले लिया गया जिन्होंने उनके लिए पूरी कीमत चुकाई थी।\n14 अगस्त2022\nCS.Money — प्लेटफ़ॉर्म के अपने बॉट्स$6,300,000 · 19,000+ स्किन्स · पहला अनुमान $1.6M\n\nहमलावरों ने मार्केटप्लेस के ट्रेडिंग बॉट्स की मोबाइल-प्रमाणीकरण फ़ाइलों को लेकर उन्हें खाली कर दिया, फिर लूट का एक हिस्सा प्रसिद्ध व्यापारियों को भेज दिया ताकि निशान धुंधले हो जाएँ। सामुदायिक शोधकर्ताओं ने मैप किया 55 हमलावर खाते कुछ ही घंटों में और उन्हें प्रकाशित किया।\n\nValve कुछ भी उलट नहीं किया गया। दी गई वजह यह थी कि एक तृतीय-पक्ष साइट Steam के बाहर स्थित है — वही Steam जिसकी इन्वेंटरी, ट्रेड API और खाता प्रणाली पर चोरी शुरू से अंत तक चली।\n\nEsportfire, 14 अगस्त2022 ↗ संग्रहीत 2025-11-15 ↗\n\nअस्वीकार कर दिया गयाकोई उलटफेर नहीं। हानि प्लेटफ़ॉर्म और उसके उपयोगकर्ताओं के साथ ही रही।\nरिपोर्ट किया गया\n21 फरवरी2023\nQkss — वही दरवाज़ा, वही अभिनेता$1,000,000+\n\nरिपोर्ट किया गया कि इसे उसी तरह लिया गया जैसा HFB को लिया गया था, उसी अभिनेता द्वारा, उसी सपोर्ट हेल्प रिक्वेस्ट के माध्यम से। HFB को आठ महीने पहले पूरी तरह बहाल कर दिया गया था। Qkss को नहीं।\n\nएक मार्ग। दो उत्तर। प्रकाशित रिकॉर्ड में दर्शकों की संख्या को छोड़कर दोनों मामलों में कोई अंतर नहीं है।\n\nडेक्सेर्टो, 21 फरवरी 2023 ↗ संग्रहीत 2025-08-18 ↗\n\nअस्वीकार कर दिया गयापुनर्स्थापित नहीं किया गया।\nरिपोर्ट किया गया\nफरवरी2023\nअंदरूनी व्यापार स्वयं — इसका एक साल≈ $320,000 · यह लगभग एक वर्ष में पूरा होता है, न कि एक सूची मूल्यांकन\n\nसपोर्ट-साइड एक्सेस ने खाता इतिहास तक पहुँच प्राप्त की 15 वर्ष का/की — पहला सीडी की, पहला ईमेल, पहला कार्ड। यही वह सबूत है जिसकी रिकवरी प्रक्रिया मांग करती है, और इसलिए डेटाबेस रखने वाला व्यक्ति हमेशा खाते को रखने वाले व्यक्ति के खिलाफ बहस जीत जाता है।\n\nब्लॉगर Mzkshow ने उजागर किया कि इनसाइडर ऑपरेटर \"Steam Help\" और सहयोगी \"Alexander\" ने उन निष्क्रिय खातों को निशाना बनाया जिनमें स्किन्स में $100k से अधिक मूल्य था। एक चोरी किया गया M4A4 Howl, जिस पर iBUYPOWER और Titan Katowice 2014 होलो थे, बेचा गया। $35,000 और अंत में वे NAVI के Valerii \"b1t\" Vakhovskyi के पास पहुँच गए, जिन्हें इसका कोई अंदाज़ा नहीं था। जबValve ने हस्तक्षेप किया, तो ठेकेदार ने अपनी पूरी Steam सपोर्ट डेस्क को बर्खास्त कर दिया।\n\nवीकेप्ले ↗ · लिस्-स्किन्स ↗ · एस्कोरन्यूज़ (आरयू) ↗ · डेक्सेर्टो (EN) ↗\n\nकोई रजिस्टर नहींValve कभी यह प्रकाशित नहीं किया कि इससे कितने खाते प्रभावित हुए, या प्रभावित लोगों को यह नहीं बताया।\nरिपोर्ट किया गया\n2 दिसं2024\n\"मैटवे\" — बर्खास्तगियों के बाद$13,000\n\nरिकवरी उस व्यक्ति को दी गई जिसने ऐसा खाता डेटा प्रदान किया जिसे मालिक स्वयं भी मेल नहीं खा सकता था। दो साल बाद जब ठेकेदार ने अपना Steam समर्थन डेस्क खाली कर दिया, उसी रास्ते से फिर वही परिणाम मिला।\n\nसंरक्षित पोस्ट, 2 दिसं2024↗ संग्रहीत 2025-08-05 ↗ · स्रोत पंक्तियाँ और हैश ↓\n\nअस्वीकार कर दिया गयापुनर्स्थापित नहीं किया गया।\n13 नवंबर2025\nHawkeye337 (मार्क स्पर्लॉक) — और दूसरा स्वीकारोक्ति≈ $300,000–$500,000 · पूरा काटोविसे 2014 होलो संग्रह\n\nहमलावर ने मांग की 1 बिटकॉइन और उसे नष्ट करने के लिए संग्रह को नेगेव्स पर खुरचना शुरू कर दिया। Steam सपोर्ट की लिखित प्रतिक्रिया ऊपर दूसरी स्वीकारोक्ति है: एक तकनीशियन ने सहायता अनुरोध को संभाला, प्रक्रिया का पालन नहीं किया, और खाता किसी और को दे दिया।\n\nजो चीज़ सुधार का कारण बनी, वह फ़ीड थी। X पर Valve को टैग करने वाली पोस्ट्स के कुछ ही घंटों बाद, अकाउंट वापस ले लिया गया और हर स्टिकर बहाल कर दिया गया। Qkss के पास वह दर्शक वर्ग नहीं था।\n\nSkin.club ↗ · डेक्सेर्टो ↗ · ईस्पोर्टफायर ↗ संग्रहीत 2025-12-17 ↗\n\nपुनर्स्थापितकहानी के ट्रेंड होने के कुछ ही घंटों में पलट दिया गया।\nलेजर वही कहता है जो कोई एक मामला नहीं कहता।\n\nमार्ग कभी बंद नहीं हुआ। पहला प्रवेश दिनांकित है फरवरी 2023 और दूसरा नवंबर 2025 — तेइस महीने का अंतरठेकेदार की बड़े पैमाने पर बर्खास्तगी, एक दस्तावेजी आवृत्ति और बीच में $6.3 मिलियन का प्लेटफ़ॉर्म उल्लंघन। इस लेज़र में पहली चोरी से गिनती शुरू करते हुए, चैनल खुला रहा तीन साल और पाँच महीने2023, में जो कुछ भी ठीक किया गया था, सहायता अनुरोध ने फिर भी नवंबर में एक खाता गलत व्यक्ति के पास भेज दिया 2025 — Valve का अपना वाक्य।\n\nप्रतिपूर्ति ने ध्यान को ट्रैक किया, हानि को नहीं। पुनर्स्थापित: खेल में सबसे बड़ी सूची, और वह संग्रहकर्ता जिसका थ्रेड ट्रेंड हुआ। अस्वीकृत: $1,000,000, $6,300,000, $13,000.Valve ने वह नियम कभी प्रकाशित नहीं किया जिसे वह लागू करता है, क्योंकि एक प्रकाशित नियम को उन तीनों को समझाना होगा।\n\nकिसी को नहीं बताया गया। न तो वे उपयोगकर्ता जिनके खाते का इतिहास डेटाबेस से पढ़ा गया, न कोई पर्यवेक्षी प्राधिकरण, न वह बाजार जिसने अच्छी नियत से वस्तुएँ खरीदीं और जिन्हें वापस ले लिया गया। कोई उल्लंघन सूचना नहीं, कोई घटना रिपोर्ट नहीं, प्रभावित खातों की कोई गिनती नहीं — और बची हुई राशि नकद में, ऐसे मार्केटप्लेस के माध्यम से जो नकद और क्रिप्टो में भुगतान करते हैं। एक ट्रेड रिवर्सल Steam से बाहर गए पैसे का अनुसरण नहीं कर सकता।\n\nValve उपरोक्त प्रत्येक पंक्ति के लिए सपोर्ट ऑडिट ट्रेल, रिकवरी-टिकट लॉग और लेनदेन रिकॉर्ड रखता है। इनमें से कोई भी प्रस्तुत नहीं किया गया है। अपनी प्रति मांगें →\n\nएनडीए प्रश्न\nगोपनीयता के साथ तकनीकी जवाबदेही भी होनी चाहिए।\n\nगोपनीयता समझौतों की तुलना वास्तविक अनुमतियों, निर्यात नियंत्रणों, रीसेट अनुमोदनों और एक्सेस लॉग्स से करें। एक तैयार प्रतिक्रिया उस आरोप को हल नहीं कर सकती कि पुनर्प्राप्ति प्रक्रिया स्वयं का दुरुपयोग की गई थी।\n\nGDPR लेख 28, 32–34\n\nधारा 33 नियंत्रक को व्यक्तिगत डेटा उल्लंघन की सूचना पर्यवेक्षी प्राधिकरण को 72 घंटे के भीतर देने का समय देती है; धारा 34 प्रभावित लोगों को तब सूचित करने की मांग करती है जब उनके लिए जोखिम अधिक हो। Valve ने लिखित रूप में दो बार पुष्टि की है कि उसके सपोर्ट चैनल ने खाते—खाते का इतिहास, बिलिंग रिकॉर्ड आदि—गलत लोगों को सौंप दिए। किसी भी अनुच्छेद के तहत कोई अधिसूचना प्रकाशित नहीं की गई है, और किसी भी प्रभावित उपयोगकर्ता ने इसे प्राप्त करने की सूचना नहीं दी है। नियम पढ़ें ↗ संग्रहीत 2026-09-20 ↗\n\nअपने अनुरोध में सहायता पहुँच शामिल करें →\nभाग C — कानूनी ढाँचे · अनुभाग 15 · वाणिज्यिक पैमाना\nपैसे का पीछा करो। लेन-देन को अलग करो।\nप्रसंग और स्रोत सीमाएँ\n\nValveजब धन प्रवाह अलग-अलग हो जाते हैं, तो वाणिज्यिक उपयोग का प्रश्न और तीक्ष्ण हो जाता है। तीसरे पक्ष को वस्तु हस्तांतरण, ई-कॉमर्स प्लेटफ़ॉर्म की प्राथमिक बिक्री और बाहरी नकद निकासी अलग-अलग लेनदेन हैं।\n\nयह आइटम Valve का है। इन्वेंटरी Valve की है। ट्रांसफर Valve के सर्वरों पर चलता है। भुगतान ही कहीं और होता है। — जो यह तय करने वाला कदम है कि कोई मनी ट्रांसमीटर है या नहीं, और यही एक ऐसा कदम है जो Valve संचालित नहीं करता।\n\nराजस्व तंत्र\nजहाँ पैसा वास्तव में चलता है।\nतीन मार्ग / एक वस्तु अर्थव्यवस्था\n01 / खाताउपयोगकर्ता सूची\n\nSteam पर रखे गए आइटम\n\n02 / स्थानांतरणपी2पी व्यापार\n\nउपयोगकर्ता ↔ बॉट या उपयोगकर्ता ↔ उपयोगकर्ता\n\n03 / समझौताबाहरी प्लेटफ़ॉर्म\n\nSteam पर साइट संतुलन या भुगतान\n\nपरिसंचरणआर्थिक इंजन एक ट्रांसफर शुल्क से परे तक फैला हुआ है।\n\nSteam बाहरी बाजारों द्वारा उपयोग की जाने वाली इन्वेंटरी और स्थानांतरण अवसंरचना प्रदान करता है। जांच का आर्थिक तर्क यह है कि पुनर्विक्रय तरलता और बार-बार होने वाली मांग मामलों, कुंजियों और प्रतिस्थापन वस्तुओं पर खर्च को बनाए रखती है, साथ ही बाद की कम्युनिटी मार्केट बिक्री पर शुल्क भी लगाती है। एक सीधे P2P स्थानांतरण में कोई कम्युनिटी मार्केट कमीशन नहीं लगता; यह लेखांकन तथ्य व्यापक लाभ को निर्धारित नहीं करता।Valve पूरे समय खाता पहुँच और व्यापार प्रतिबंधों पर नियंत्रण बनाए रखता है।\n\n01 / द्वितीयक मांगतरलता और पुनर्विक्रय मूल्य\n\nबाहरी व्यापार और जुआ की मांग\n\n02 / प्राथमिक खर्चचाबियाँ, केस और कैप्सूल\n\nValveपर जहाँ पेशकश की गई हो, खरीदारी\n\n03 / राजस्वप्राथमिक-विक्रय आय\n\nवास्तविक बाज़ार बिक्री पर अतिरिक्त शुल्क\n\n5% + 10%Steam + कम्युनिटी मार्केट बिक्री पर CS2 शुल्क\n\nजांच का आर्थिक निष्कर्ष: तरल पुनर्विक्रय बाजार नए उत्पादों पर खर्च को प्रोत्साहित कर सकते हैं। परिचित 15% न्यूनतम सीमाओं और राउंडिंग के अधीन मार्केट शुल्क दरों को जोड़ता है; यह प्रत्येक बाहरी व्यापार पर लगाया जाने वाला कोई शुल्क नहीं है।\n\nValve का सामुदायिक बाज़ार शुल्क अनुसूची ↗ संचित 2026-09-21 ↗. 25 फरवरी 2026 न्यूयॉर्क के अटॉर्नी जनरल ने एक कार्रवाई दायर की। संग्रहीत 2026-09-01 ↗ यह आरोप लगाते हुए कि भुगतान किए गए लूट बॉक्स बाहरी नकद पुनर्विक्रय और जुए से होने वाले नुकसान से जुड़े हैं — वही संबंध जिसे यह दस्तावेज़ तकनीकी-अवरसंरचना पक्ष से प्रदर्शित करता है। वह शिकायत एक आरोप है, निष्कर्ष नहीं; इसे यहाँ इसलिए उद्धृत किया गया है क्योंकि एक राज्य कानून-प्रवर्तन एजेंसी ने 'Valve' पर उसी प्रश्न को रखा है जो यह दस्तावेज़ पूछता है: सार्वजनिक घोषणाओं से मेल खाने वाला प्रवर्तन रिकॉर्ड कहाँ है?\n\n01 / प्रवेशक्रिप्टो जमा\n\nबाहरी सेवा और वॉलेट रिकॉर्ड\n\n02 / रूपांतरणबैलेंस → स्किन्स\n\nSteam ट्रेड्स के माध्यम से वितरित की गई वस्तुएँ\n\n03 / बाहर निकलेंबाहरी फ़िएट बिक्री\n\nविक्रेता, खरीदार और भुगतान प्रदाता\n\nकेवाईसी?प्रत्येक हस्तांतरण पर नियंत्रण की पहचान करें।\n\nजांच करने का यह मार्ग है, न कि कोई नेटिव SteamAPI कैश-कन्वर्जन सेवा। बिना KYC कैश-आउट का दावा करने से पहले प्रत्येक बाहरी ऑपरेटर पर पहचान जांच, हिरासत, लेनदेन आईडी और भुगतान प्राप्तकर्ताओं का दस्तावेजीकरण करें।\n\nसंयुक्त राज्य अमेरिका / बैंक गोपनीयता अधिनियम\nपहले गतिविधि का वर्गीकरण करें, फिर दायित्व का।\n\nFinCEN व्यवसाय की गतिविधियों के आधार पर धन प्रेषण का आकलन करता है। परिवर्तनीय वर्चुअल मुद्रा को स्वीकार करना और प्रेषित करना, लागू परिभाषाओं और अपवादों के अधीन, धन-सेवा संबंधी दायित्वों को सक्रिय कर सकता है।Valve का Steam वॉलेट निधियाँ स्वीकार करता है और उन्हें इन-गेम आइटम्स में परिवर्तित करता है; ये आइटम्स फिर तीसरे पक्ष के ऑपरेटरों के माध्यम से वास्तविक मुद्रा में नकदीकृत किए जाते हैं। वस्तु और उसका हस्तांतरण Valve के बुनियादी ढांचे पर चलते हैं; कैश-आउट नहीं, और उस चक्र के किसी भी भाग का मनी-ट्रांसमिशन परिभाषाओं को पूरा करता है या नहीं, यह FinCEN के लिए वर्गीकरण का प्रश्न है, न कि यहाँ निकाला गया कोई निष्कर्ष।\n\nFinCEN FIN-2019-G001, §§ 1–2, 5.1 ↗ संग्रहीत 2025-07-11 ↗\n\nयूरोपीय संघ / धन शोधन\nनिशान, प्रक्रिया, ज्ञान और सहायता।\n\nनिर्देश (EU) 2018/1673 जानबूझकर की गई लॉन्ड्रिंग और आपराधिक आय में भागीदारी को कवर करता है। जांच का प्रश्न यह है कि Valve को 13 जुलाई 2016, के बाद ऑपरेटरों द्वारा इसके ट्रेडिंग और OpenID इंफ्रास्ट्रक्चर का उपयोग करने के बारे में क्या पता था, जब उसने सार्वजनिक रूप से उस उपयोग का वर्णन किया था, और उसने उनके खिलाफ क्या कार्रवाई की। Valve ने किसी भी ऑपरेटर-वार प्रवर्तन रिकॉर्ड का प्रकाशन नहीं किया है; वह रिकॉर्ड, यह दस्तावेज़ नहीं, इस प्रश्न का उत्तर देगा।\n\nईयू आपराधिक-कानून ढांचा ↗\n\nAMLD6 शब्दावली: उपरोक्त आपराधिक-कानून निर्देश Directive (EU) 2024/1640,, जिसे AMLD6 भी कहा जाता है, से अलग है। बाद वाले के लिए सामान्य रूपांतरण की समयसीमा 10 जुलाई 2027, है, जिसमें विशिष्ट अपवाद शामिल हैं। लेख78 ↗ संचित 2026-08-30 ↗\n\nभाग C — कानूनी ढाँचे · अनुभाग 16 · सूचना, प्रतिक्रिया, जिम्मेदारी\nडिजिटल सेवा अधिनियम: तथ्यों को सामने रखें\nप्रसंग और स्रोत सीमाएँ\n\nलेख 16 की सूचना के दो तत्व इस दस्तावेज़ के बजाय प्रस्तुतकर्ता के पास रहते हैं: प्रस्तुतकर्ता का अपना विवरण और यह घोषणा कि जानकारी सटीक है। लेख द्वारा आवश्यक बाकी सभी चीज़ें — प्रमाणित स्पष्टीकरण और सटीक इलेक्ट्रॉनिक स्थान — धारा 3 और मार्ग रजिस्टर में, संग्रहीत प्रतिक्रियाओं और हैश के साथ निर्धारित की गई हैं, ताकि कोई भी पक्ष इसे दर्ज कर सके। कानून पर दो और सीमाएँ हैं: होस्टिंग छूट खोने से स्वयं में किसी अन्य कानून के तहत देयता स्थापित नहीं होती, और अनुच्छेद 52(3) में उल्लिखित '6%' एक वैधानिक सीमा है, न कि Valve के खिलाफ आकलित दंड।\n\nडीएसए के तहत, एक होस्टिंग प्रदाता अपनी देयता सुरक्षा केवल तब तक बनाए रखता है जब तक उसे विशिष्ट जानकारी न हो और वह कार्रवाई करने में विफल रहता है। यह दस्तावेज़ वह सूचना है। यह होस्ट्स, तिथियाँ, सहेजी गई प्रतिक्रियाएँ और हैश नाम बताता है। प्रकाशन के बाद सवाल यह नहीं रहा कि क्या Valve को पता था — सवाल यह है कि Valve ने इसके बाद क्या किया।\n\n01जुलाई 2016 / द डॉसियर प्रदर्शनी\nएक दस-दिवसीय मांग।\n\nउपरोक्त पुनर्निर्मित नोटिस जांच के प्रवर्तन तुलना के लिए ऐतिहासिक प्रारंभिक बिंदु है।\n\n0217 फरवरी 2024 / सामान्य आवेदन\nडीएसए समय खिड़की।\n\nप्रासंगिक डीएसए दायित्वों के लागू होने की अवधि के दौरान आचरण से ऐतिहासिक आचरण को अलग करें।\n\n03दस साल / मूल दस्तावेज़ का स्नैपशॉट\nअवधि के लिए सूचना पथ आवश्यक है।\n\nजुलाई 2016 से अब तक का समय (देखें धारा 11) एक दस्तावेज़ी मेट्रिक है। यह स्थापित DSA उल्लंघनों के दस वर्षों का नहीं है। प्रत्येक सूचना को एक विशिष्ट आइटम, लागू कानून, वितरण के प्रमाण और प्रतिक्रिया से लिंक करें।\n\nलेख 52(3) / वैधानिक सीमा6%\nवार्षिक विश्वव्यापी कारोबार का\n\nडीएसए दायित्वों के उल्लंघन के लिए अधिकतम जुर्माना, प्रदाता के पिछले वित्तीय वर्ष के आधार पर। यह एक कानूनी सीमा है, न कि Valve के खिलाफ आकलित दंड।\n\nलेख 6, 8 और 16 / कानूनी परीक्षण\n\nसंबंधित होस्टिंग सेवाओं के लिए विशिष्ट जानकारी और शीघ्रता से कार्रवाई न करने पर होस्टिंग छूट समाप्त हो सकती है। एक पर्याप्त रूप से सटीक सूचना विशेष सामग्री की जानकारी स्थापित कर सकती है। डीएसए कोई सामान्य निगरानी दायित्व नहीं लगाता; छूट का समाप्त होना स्वयं में किसी अन्य कानून के तहत दायित्व स्थापित नहीं करता।\n\nDSA: अनुच्छेद 6, 8, 16, 52, 53, 93 और पुनरावलोकन 17 ↗ संग्रहीत 2026-09-20 ↗\n\nसंरक्षित शिकायतों की समीक्षा करें ↗खाते की समयरेखा बनाएँ →पूर्ण कानूनी और आर्थिक विश्लेषण →\nभाग C — कानूनी ढाँचे · अनुभाग 17 · पहचान, आयु, वाणिज्यिक पहुँच\nनाबालिग: Steam लॉगिन आयु जांच नहीं है।\nप्रसंग और स्रोत सीमाएँ\n\nइस दस्तावेज़ में किसी भी नाबालिग का डेटा कहीं भी नहीं है और कोई डेटा एकत्रित भी नहीं किया गया: लेखकों ने किसी भी नामित प्लेटफ़ॉर्म पर पंजीकरण नहीं किया, जमा नहीं किया, या लॉगिन पूरा नहीं किया। इस अनुभाग पर काम करने वाले किसी भी व्यक्ति को बच्चे से संबंधित साक्ष्य निजी रखना चाहिए और सार्वजनिक प्रदर्शनों से पहचान संबंधी विवरण हटा देना चाहिए। COPPA का यहाँ बच्चों की गोपनीयता कानून के रूप में उल्लेख किया गया है, जिसके अपने दायरे की शर्तें हैं — दर्शक, वास्तविक जानकारी, एकत्रित व्यक्तिगत डेटा — न कि सामान्य जुआ-आयु नियम के रूप में; 2026न्यूयॉर्क शिकायत एक राज्य प्राधिकरण द्वारा लगाया गया आरोप है, न कि कोई निष्कर्ष।\n\n\"Steam के साथ साइन इन करें\" यह साबित करता है कि एक खाता मौजूद है। यह उम्र के बारे में कुछ भी साबित नहीं करता। — और इन साइटों पर यह एक बच्चे और जमा के बीच का एकमात्र द्वार है। इसे के साथ पढ़ें धारा 3.1Steam क्लाइंट के अंदर ब्राउज़र द्वारा दिखाई जाने वाली चेतावनी कभी भी नहीं दिखती, इसलिए चाइल्ड उसे कभी नहीं देखता।\n\nSteam OpenID क्या प्रदान करता हैखाता पहचान\n\nएक सत्यापित SteamID जिसका उपयोग लॉग इन करने या खाते को लिंक करने के लिए किया जाता है।\n\n≠\nऑपरेटर को क्या स्थापित करना चाहिएभाग लेने की पात्रता\n\nआयु, क्षेत्राधिकार और कोई भी आवश्यक पहचान जांच।\n\nतकनीकी आधार: स्टीमवर्क्स ओपनआईडी दस्तावेज़ीकरण ↗ संचित 2026-09-21 ↗दस्तावेजीकृत पहचान पुष्टि यह प्रमाणन नहीं है कि उपयोगकर्ता कानूनी रूप से जुआ खेल सकता है।\n\nCOPPA / 13 से कम उम्र के बच्चे\nऑपरेटर और डेटा की पहचान करें।\n\nCOPPA उन कवर की गई बाल-उन्मुख सेवाओं और उन सेवाओं पर लागू होती है जिन्हें वास्तव में पता है कि वे 13. से कम उम्र के बच्चों से व्यक्तिगत जानकारी एकत्रित कर रही हैं। यह बच्चों की गोपनीयता संबंधी कानून है, सार्वभौमिक जुआ-आयु नियम नहीं। दर्शकों की पहचान, एकत्रित व्यक्तिगत डेटा, जानकारी और अभिभावक सहमति प्रक्रिया स्थापित करें।\n\nएफटीसी: COPPA आवश्यकताएँ ↗ संचित 2026-09-21 ↗\n\nसंरक्षित करने के लिए साक्ष्य\nलॉगिन से जमा तक की यात्रा रिकॉर्ड करें।\n\nसाइट के आयु गेट, पंजीकरण की शब्दावली, पात्रता की शर्तें, भुगतान प्रक्रिया और शिकायत इतिहास को संरक्षित करें। प्रत्येक ऑपरेटर का अलग से आकलन करें। किसी भी ऐसे साक्ष्य को जो किसी बच्चे से संबंधित हो, निजी रखें और सार्वजनिक प्रदर्शनों से पहचान संबंधी विवरण हटा दें।\n\nएक संबंधित सार्वजनिक प्रवर्तन रिकॉर्ड है 2026 न्यूयॉर्क शिकायत घोषणा संग्रहीत 2026-09-01 ↗, जो भुगतान किए गए लूट बॉक्स से युवा उपयोगकर्ताओं को होने वाले नुकसान का आरोप लगाता है। यह COPPA का निष्कर्ष नहीं है।\n\nभाग C — कानूनी ढाँचे · अनुभाग 18 · GDPR लेख 15 अनुरोध\nअनुरोध। उत्तर। अनुपस्थित तुलना।\n\nउसने चार चीज़ों की मांग की, जिनमें से एक था वह लॉग जो यह बताएगा कि उसके खाते पर 'API' कुंजी किसने लगाई थी। तीन दिन बाद टिकट को एक ऐसे पृष्ठ के लिंक के साथ बंद कर दिया गया जिस पर उनमें से कोई भी नहीं है। — और इसे समाप्त करने के लिए इस्तेमाल किया गया वाक्य Valve के अपने वकीलों द्वारा खंडित किया गया है।\n\nयह किसका खाता है · उत्पत्ति और सीमाएँ\n\nये स्क्रीनशॉट PhishDestroy के नहीं हैं। ये एक साधारण Steam खाताधारक से आए हैं — इस परियोजना द्वारा चलाए गए एक छोटे सर्वेक्षण के एक उत्तरदाता, जिसने स्वयं अनुरोध दायर किया और स्क्रीनशॉट प्रदान किए। खाता उनका है, टिकट उनका है, और पत्राचार उनके और Steam समर्थन के बीच है। इस परियोजना ने अनुरोध प्रस्तुत नहीं किया, प्लेटफ़ॉर्म पर इसका कोई खाता नहीं है, और यह इस टिकट में पक्षकार नहीं है।\n\n16 सितंबर को 2026 ने एक GDPR/CCPA अनुच्छेद 15 विषय पहुँच अनुरोध दायर किया, जिसमें विशेष रूप से API-की पंजीकरण लॉग, आईपी के साथ लॉगिन इतिहास, डिवाइस प्राधिकरण इतिहास और व्यापार इतिहास की मांग की गई। 17 सितंबर को एजेंट \"Logen\" ने उन्हें स्वयं-सेवा खाता डेटा पृष्ठ पर भेज दिया। 18 सितंबर को उन्होंने कहा कि अनुरोधित श्रेणियाँ उस पृष्ठ पर नहीं थीं और उन्होंने प्राइवेसी टीम या DPO को एस्केलेशन करने का अनुरोध किया। 19 सितंबर को एजेंट \"Kal\" ने उसी रेफरल के साथ टिकट बंद कर दिया। दोनों स्क्रीनशॉट नीचे संरक्षित हैं (अनुरोधकर्ता का ईमेल हटाया गया; SHA-256 में steam_tos_assets/screenshot-manifest.json).\n\nवह एक साधारण कारण से अनुरोध करने के लिए उपयुक्त है: उसके खाते में एक Steam Web API कुंजी है जिसे उसने नहीं बनाया, पंजीकृत है localhost. यह कब बनाया गया था, यह ज्ञात नहीं है। — न तो उसे, और न ही Valve द्वारा उपलब्ध कराई गई किसी भी चीज़ से, क्योंकि एकमात्र रिकॉर्ड जो इसकी तारीख बता सकता है, वह API-की पंजीकरण लॉग है, और यही वह श्रेणी है जिसे समापन ने छिपाया था। कुंजी नई नहीं है: यह उसकी जानकारी में आने से पहले से मौजूद थी, और वह उस अंतराल को माप नहीं सकता, ठीक उसी कारण से।\n\nअन्य खाताधारक भी समान अनुरोध दायर कर रहे हैं। कोई भी प्राप्त होने वाली प्रतिक्रिया इन दोनों की शर्तों के अनुसार—टिकट संख्या, कैप्चर तिथि, SHA-256, अनुरोधकर्ता का नाम हटाया गया—यहाँ जोड़ी जाएगी, चाहे वह श्रेणियाँ प्रदान करे या उन्हें अस्वीकार करे।\n\nयह परियोजना टिकट क्यों बंद किया गया, इस पर कोई पक्ष नहीं लेती। इसमें कोई कारण नहीं बताया गया था, और यहाँ कोई अनुमान भी नहीं लगाया गया है।\n\nअनुरोध। प्रतिक्रिया। तुलना।रिकॉर्ड का पालन करें\nचरण 3 / 3\n\nउसने चार नामित श्रेणियों का अनुरोध किया। जिस Account Data पेज का उसे संदर्भ दिया गया था, वह Valve का अपना स्वयं-सेवा निर्यात है, और यह परियोजना किसी अन्य के खाते की सामग्री को सूचीबद्ध नहीं कर सकती — इसलिए यहाँ कोई पूर्ण श्रेणी-दर-श्रेणी तुलना प्रकाशित नहीं की गई है। रिकॉर्ड पर जो है, वह 18 सितंबर का उनका बयान है कि श्रेणियाँ वहाँ नहीं थीं, और 19 सितंबर का समापन है, जिसने उन्हें संबोधित किए बिना ही रेफ़रल दोहराया।\n\nअनुरोधविशिष्ट श्रेणियाँAPI-कुंजी, लॉगिन, डिवाइस और व्यापार रिकॉर्ड\nप्रतिक्रियाखाता डेटा संदर्भसमर्थन विनिमय का निरीक्षण करें\nपरीक्षाक्या प्रदान किया गया था?प्रत्येक अनुरोधित श्रेणी की तुलना करें\nस्क्रीन 1/2 — अनुरोध (16 Sep) और पहला उत्तर, एजेंट \"Logen\" (17 Sep)\nGDPR टिकट HT-2YBP-F7JP-D4VB — अनुरोध और पहला उत्तर\nस्रोत: help.steampowered.com, टिकट HT-2YBP-F7JP-D4VB · कैप्चर 16–17 सितंबर 2026 · अनुरोधकर्ता का ईमेल हटाया गया 2026-09-21 · फ़ाइल: gdpr-ticket-1.png · एसएचए-256 da940c731ab9869d226e9d06ccc8a1b393738766b7b0c445a56662623e025a66 (screenshot-manifest.json).\nस्क्रीन2/2 — एस्केलेशन अनुरोध (18 Sep) और समापन, एजेंट \"Kal\" (19 Sep)\nGDPR टिकट HT-2YBP-F7JP-D4VB — वृद्धि अनुरोध और समापन\nस्रोत: help.steampowered.com, टिकट HT-2YBP-F7JP-D4VB · कैप्चर 18–19 सितंबर 2026 · फ़ाइल: gdpr-ticket-2.png · एसएचए-256 44844ea7b251f7fd7d79f87ee1578a846606a97b9659d3a53b322120c422219b (screenshot-manifest.json).\nअंतिम प्रतिक्रिया, 19 सितम्बर (शाब्दिक):\nSteam द्वारा संग्रहीत डेटा पहले से ही आपके Account Data पृष्ठ पर पाया जा सकता है। चूंकि Steam सपोर्ट और कोई अतिरिक्त जानकारी प्रदान नहीं कर सकता, यह अनुरोध बंद कर दिया जाएगा।\"\nकोई डेटा प्रदान नहीं किया गया · अस्वीकृति का कोई कानूनी आधार नहीं बताया गया · कोई एस्केलेशन परिणाम नहीं दिखाया गया\nवह वाक्य झूठा है, और Valve के अपने वकील ही इसे साबित करते हैं। 1 के वकील का पत्र, दिनांक 2025,, पैराग्राफ 1.9,, एक डिवाइस-स्तर का सहसंबंध वर्णन करता है जो एक डिवाइस को दर्जनों खातों से जोड़ता है (परिशिष्ट अ). उसी प्रतिक्रिया में रखे गए अभिलेखों के 830 पृष्ठ शामिल थे (परिशिष्ट B). इनमें से कुछ भी खाता डेटा पृष्ठ पर नहीं है।\nइस खाते ने API-की लॉग क्यों माँगा?\n\nउसने उन चार श्रेणियों को यादृच्छिक रूप से नहीं चुना। localhost उसके खाते की कुंजी है एक स्क्रिप्ट का निशान है, न कि डेवलपर पेज में कोई वास्तविक डोमेन टाइप करने वाले व्यक्ति का। (धारा 5, धारा 6). एकमात्र रिकॉर्ड जो दिखाता है कि इसे किसने बनाया और कहाँ से बनाया, वह API-key पंजीकरण लॉग है। वह पहली चीज़ थी जिसकी उसने मांग की। यही वह चीज़ थी जिसे क्लोज़र ने छिपाया।\n\nस्रोत: इस परियोजना के सर्वेक्षण के दौरान खाता धारक। ऊपर दिए गए टिकट के स्क्रीनशॉट हैश किए गए हैं; मुख्य पृष्ठ प्रकाशित नहीं किया गया है।\n\nमूल्यांकन · PhishDestroy\n\nयहाँ टिकट को प्रश्न अभी भी खुला होने के बावजूद बंद करना कोई आकस्मिक घटना नहीं है। यह सामान्य परिणाम है। हम मानते हैं 16,319 संरक्षित शिकायत और समर्थन रिकॉर्ड और 354 दोहराए गए समर्थन आदान-प्रदान हटाए गए उनसे लिया गया। यह टिकट उस आकार का एक दिनांकित, पूरी तरह से कैद किया गया उदाहरण है।\n\nसमर्थन टिकट — संरक्षितHT-2YBP-F7JP-D4VB\nअनुरोध का प्रकारGDPR लेख 15 डीएसएआर\nटिकट की स्थितिबंद 19 सितम्बर 2026 — कोई डेटा प्रदान नहीं किया गया\nविनिमय में एजेंट\"लोगेन\" (17 सित), \"काल्\" (19 सित)\nदाखिल16 सितंबर2026\nअनुरोधित डेटाइस खाते से जुड़ी Web API कुंजी किसने पंजीकृत की, और वह किस IP / डिवाइस / टाइमस्टैम्प से की गई थी?\nउद्धृत कानूनी आधारGDPR धारा 15 — व्यक्तिगत डेटा तक पहुँच का अधिकार\nकानूनी ढांचा:लेख 12(3) नियंत्रक को प्राप्ति से एक महीने का समय देता है (कारण बताकर बढ़ाया जा सकता है)। वह अवधि प्रकाशन के समय समाप्त नहीं हुई थी, और यह दस्तावेज़ समयसीमा के उल्लंघन का दावा नहीं करता। आपत्ति विषय-वस्तु से संबंधित है: अंतिम प्रतिक्रिया एक स्व-सेवा पृष्ठ से लिंक करती है लेकिन यह नहीं दिखाती कि चार नामित डेटा श्रेणियाँ तैयार की गई थीं, और यदि नियंत्रक कार्रवाई करने से इनकार करता है, तो अनुच्छेद 12(4) के अनुसार उसे कारण और शिकायत मार्ग बताने होंगे। ये दोनों अंतिम प्रतिक्रिया में नहीं हैं।\nयह विशिष्ट डेटा क्यों मायने रखता है\n\nवेब API कुंजी इवेंट लॉग वह रिकॉर्ड है जो यह दर्शाता है कि किसी तीसरे पक्ष ने चोरी की गई सत्र कुकी का उपयोग करके एक कुंजी पंजीकृत की है या नहीं — यह उस तंत्र का वर्णन है जो इस दस्तावेज़ के अभिलेखागार में संरक्षित इन्वेंटरी-चोरी की शिकायतों में बताया गया है। यह खुलासा करना कि किसने एक API कुंजी पंजीकृत की, किस आईपी से, और किस टाइमस्टैम्प पर, तो:\n\nपीड़ित को API निर्माण आईपी की तुलना अपने लॉगिन इतिहास से करने की अनुमति दें।\nज्ञात फ़िशिंग/जुआ बॉट इंफ्रास्ट्रक्चर से जुड़े डेटा-सेंटर आईपी पतों का खुलासा करें।\nकार्यकर्ता के खिलाफ दीवानी या आपराधिक कार्यवाहियों में उपयोगी साक्ष्य प्रस्तुत करें।\nदिखाएँ कि कुंजी बनाए जाने पर खाते के धारक को सूचित किया गया था या नहीं।\nरिकॉर्ड से पता चलता है: Valve डिवाइस-स्तर और खाता-संबंधी रिकॉर्ड्स को बनाए रखता है — इसके वकील का पत्र 1, 10 अक्टूबर 2025 में उनका वर्णन किया गया है (देखें परिशिष्ट A, साक्ष्य ज्ञापन — स्रोत 1)। टिकट HT-2YBP-F7JP-D4VB में डेटा विषय द्वारा उसी श्रेणी के रिकॉर्ड का अनुरोध किया गया था और टिकट को एक स्व-सेवा पृष्ठ पर भेजकर बंद कर दिया गया, जिसके बारे में डेटा विषय ने रिपोर्ट किया कि उसमें वे रिकॉर्ड नहीं थे। यह कि वह इनकार वैध है या नहीं, यह पर्यवेक्षी प्राधिकरण के लिए एक प्रश्न है; इसका प्रभाव यह है कि जिस व्यक्ति से डेटा संबंधित है, उसे यह नहीं मिलता।\nविनिमय — चार संदेश, तीन दिन\n\nSteam के दो सपोर्ट एजेंटों ने टिकट पर दिखाए गए पहले नामों के तहत जवाब दिया: 17 सितंबर को \"Logen\" और 19 सितंबर को \"Kal\". दोनों ने अनुरोधकर्ता को अकाउंट डेटा पेज पर भेज दिया। टिकट पर यह नहीं दिखता कि अनुरोध Valve की प्राइवेसी टीम या डेटा प्रोटेक्शन ऑफिसर तक पहुँचा या नहीं, और दस्तावेज़ में यह नहीं बताया गया कि एजेंट कौन हैं, उनकी भूमिकाएँ क्या हैं, या टिकट कैसे रूट किया गया।\n\n16 अलगाव\nलेख 15चार नामित डेटा श्रेणियों के साथ दायर अनुरोध\n17–18 अलगाव\nखाता डेटा के लिए रेफ़रल; अनुरोधकर्ता DPO एस्केलेशन का अनुरोध करता है\n19 अलगाव\nटिकट उसी रेफरल के साथ बंद कर दिया गया; कोई डेटा नहीं, कोई आधार नहीं बताया गया।\nलेख 15GDPR स्पष्ट रूप से विषय को क्या अधिकार प्रदान करता है\nधारा15(1)(क)प्रसंस्करण उद्देश्यों — Valve डेटा क्यों रखता है\nधारा15(1)(ख)डेटा की श्रेणियाँ — Valve के पास क्या है\nधारा15(1)(c)प्राप्तकर्ता या प्राप्तकर्ताओं की श्रेणियाँ — जिनके पास डेटा प्राप्त हुआ (e.g., API कुंजी धारक)\nधारा15(1)(d)रखने की अवधि या इसे निर्धारित करने के मानदंड\nलेख15(3)प्रसंस्करण के अधीन व्यक्तिगत डेटा की एक प्रति — i.e., API-की लॉग स्वयं\nधारा12 (3)के भीतर प्रतिक्रिया आवश्यक है एक महीना प्राप्ति की; विस्तार उसी महीने के भीतर सूचित किया जाना चाहिए। प्रकाशन के समय यह अवधि समाप्त नहीं हुई थी। धारा 12(4): यदि नियंत्रक कार्रवाई नहीं करता है, तो उसे कारण बताना होगा और शिकायत निवारण मार्गों की जानकारी देनी होगी।\nनियामक शिकायत मार्ग — किसी भी उपयोगकर्ता के लिए\n\nकोई भी उपयोगकर्ता जिसने Valve को एक लेख 15 GDPR अनुरोध प्रस्तुत किया और कोई अनुपालन प्रतिक्रिया (या डेटा के बिना एक टेम्पलेट अस्वीकृति) प्राप्त नहीं की, वह अपने EU/EEA सदस्य राज्य में पर्यवेक्षी प्राधिकारी के पास शिकायत दर्ज कर सकता है। Valve की EU स्थापना हैम्बर्ग में Valve GmbH है, इसलिए सीमा-पार शिकायतों के लिए प्रमुख पर्यवेक्षी प्राधिकारी है हैम्बर्ग की डेटा सुरक्षा और सूचना स्वतंत्रता की आयुक्त (HmbBfDI). (Valve के अनुच्छेद 27 का प्रतिनिधि भी हैम्बर्ग में स्थित है; एक प्रतिनिधि का पता अपने आप में सक्षम प्राधिकरण निर्धारित नहीं करता।) अनुच्छेद 77. के तहत शिकायतकर्ता के अपने सदस्य राज्य के प्राधिकरण के पास भी शिकायत दर्ज की जा सकती है।\n\nHmbBfDI शिकायत प्रपत्र ↗ GDPR पाठ (लेख12,15,77) ↗ संग्रहीत 2026-09-20 ↗ईडीपीबी दिशानिर्देश ↗\n\nकिसी भी शिकायत के लिए टिकट संदर्भ: HT-2YBP-F7JP-D4VB — इस दस्तावेज़ में एक प्रलेखित उदाहरण के रूप में संरक्षित।\n\nएक प्रलेखित उदाहरण\nरिकॉर्ड मौजूद हैं; डेटा विषय को वे प्राप्त नहीं हुए।\n\nValve के वकील ने 1 अक्टूबर 2025. के एक पत्र में डिवाइस-स्तरीय सहसंबंध रिकॉर्ड का वर्णन किया। 19 सितंबर 2026 पर, इसी श्रेणी के रिकॉर्ड के लिए एक Article 15 अनुरोध को एक स्वयं-सेवा पृष्ठ पर भेजकर बंद कर दिया गया, जिसे अनुरोधकर्ता ने बताया कि उसमें वे रिकॉर्ड नहीं थे, बिना किसी कानूनी आधार के। टिकट HT-2YBP-F7JP-D4VB एक प्रलेखित उदाहरण है; यह व्यापक प्रथा को दर्शाता है या नहीं, यह पर्यवेक्षी प्राधिकरण का प्रश्न है, जो Valve से इसकी हैंडलिंग रिकॉर्ड्स की मांग कर सकता है।\n\nGDPR लेख 12, 15, 77 / पर्यवेक्षी प्राधिकरण\n\nलेख 12 और 15 के तहत शिकायत सीधे संबंधित पर्यवेक्षी प्राधिकरण के पास बिना किसी शुल्क के दर्ज की जा सकती है (लेख 77)। प्राधिकरण सुधारात्मक उपाय लागू कर सकता है, जिसमें पहुँच अनुरोध का पालन करने के आदेश और अनुच्छेद 83(5)(b) के तहत डेटा विषय के अधिकारों के उल्लंघन के लिए जुर्माना शामिल है। मूल टिकट संदर्भ और किसी भी Valve प्रतिक्रिया (या उसकी अनुपस्थिति) को संरक्षित रखना शिकायत को मजबूत करता है।\n\nDSAR टेम्पलेट देखें →\nभाग C — कानूनी ढाँचे · अनुभाग 19 · संविदा कानून\nप्लेटफ़ॉर्म की अपनी वास्तुकला के विरुद्ध सदस्यता समझौता\nप्रसंग और स्रोत सीमाएँ\n\nलेखक वकील नहीं हैं और यह कोई कानूनी सलाह नहीं है। एसएसए का उद्धरण 10, सितंबर 2026 के संशोधन से लिया गया है; किसी अन्य संशोधन में यह अलग हो सकता है, और खंड संख्या संशोधनों के साथ बदल गई है — प्रश्नगत आचरण को नियंत्रित करने वाले संस्करण के अनुसार खंड की जाँच करें। लेख 25 और 32 के तर्क बताते हैं कि विनियमन में क्या आवश्यक है, न कि किसी पर्यवेक्षी प्राधिकरण ने उल्लंघन पाया है। तर्क 1 में दिए गए आंकड़े अनुभाग 13. में निर्धारित दायरा सीमाएँ दर्शाते हैं।\n\nएसएसए के तीन केंद्रीय प्रावधान इस बात से मेल नहीं खाते कि प्लेटफ़ॉर्म कैसे बनाया गया है: एक बाज़ार मूल्य सीमा के खिलाफ व्यावसायिक उपयोग पर रोक जो उच्च-मूल्य वाली बिक्री को प्लेटफ़ॉर्म से बाहर धकेलती है; उपयोगकर्ता-देयता खंड (API) एक ऐसे मुख्य लक्ष्य बिंदु के विरुद्ध है, जिसके लिए 2023, से पहले किसी द्वितीयक कारक की आवश्यकता नहीं होती थी; और सार्वजनिक रिकॉर्ड के विरुद्ध प्रवर्तन भाषा, जो प्रति-ऑपरेटर प्रवर्तन नहीं दिखाती। ये तनाव प्रवर्तन क्षमता को प्रभावित करते हैं या नहीं, यह अदालत का प्रश्न है; इस अनुभाग में वे तथ्य प्रस्तुत किए गए हैं जो अदालत के समक्ष होंगे।\n\nतर्क 1 / मार्केट कैप आर्किटेक्चर\nबाजार की ऊपरी सीमा और वाणिज्यिक उपयोग पर प्रतिबंध\n\nSteam Community Market की लिस्टिंग सीमा लगभग $1,800. है। एक पुराने स्नैपशॉट (23, Sep 2026) में पाँच मार्केटप्लेस में, 248 CS2 आइटम श्रेणियाँ उनमें से दो या अधिक द्वारा स्वतंत्र रूप से उस सीमा से ऊपर मूल्यनिर्धारित की गई हैं; ऐसे आइटम Valve के अपने प्लेटफ़ॉर्म पर उन कीमतों पर बेचा नहीं जा सकता।जो मालिक वे कीमतें चाहते हैं, वे तृतीय-पक्ष बाज़ारों का उपयोग करते हैं, जो Steam खातों और Steam API पर चलते हैं — जब तक स्पष्ट रूप से अनुमति न दी जाए, SSA इन्हें वाणिज्यिक के रूप में वर्गीकृत करता है।\n\nआइटम बाजार की ऊपरी सीमा से अधिक हो जाते हैं → तृतीय-पक्ष बाजार इस अंतर को भरते हैं → ये बाजार Steam खातों और Steam API का उपयोग करते हैं → SSA बिना अनुमति के व्यावसायिक उपयोग पर रोक लगाता है → अनुमति का कोई रजिस्टर प्रकाशित नहीं किया गया है। कम्युनिटी मार्केट की संयुक्त शुल्क राशि लगभग 15% केवल मार्केट के भीतर पूरी हुई बिक्री पर लागू होती है, इन बाहरी लेनदेन पर नहीं।\nतर्क 2 / API कुंजी सुरक्षा वास्तुकला\nAPI-की भेद्यता को उपयोगकर्ता की लापरवाही के बजाय एक प्लेटफ़ॉर्म डिज़ाइन प्रश्न के रूप में देखना\n\n2023,Steam के API कुंजी निर्माण एंडपॉइंट ने एक चोरी किए गए sessionid के साथ एक POST स्वीकार किया और एक उच्च-अधिकार वाला क्रेडेंशियल उत्पन्न किया। ई-मेल पुष्टि के बिना, एक दूसरा फैक्टर या डिवाइस सत्यापनAPI में इस जांच में एकत्रित हाईजैक शिकायतें एक ही पैटर्न का पालन करती हैं: हमलावर स्क्रिप्ट, चोरी की गई सत्र कुकी, चुपके कुंजी निर्माण, व्यापार इंटरसेप्शन (अनुरोध पेलोड अनुभाग 8 में दिखाया गया है)।\n\nGDPR लेख 25 (डिज़ाइन द्वारा डेटा संरक्षण) और लेख 32 (प्रसंस्करण की सुरक्षा) जोखिम के अनुरूप तकनीकी उपायों की आवश्यकता करते हैं। दूसरे कारक या स्वामी को सूचित किए बिना व्यापार इंटरसेप्शन में सक्षम क्रेडेंशियल जारी करना नियंत्रक के लिए एक डिज़ाइन संबंधी प्रश्न है। उस पृष्ठभूमि में उपयोगकर्ता पर दायित्व लगाने वाली SSA क्लॉज पर भरोसा किया जा सकता है या नहीं, यह न्यायालय और पर्यवेक्षी प्राधिकरण का प्रश्न है।\n\nतर्क3 / वास्तविक-समय दृश्यता\nValve हर लॉगिन पर auth होस्टनेम प्राप्त करता है।\n\nauth होस्टनेम Valve के OpenID एंडपॉइंट पर प्लेनटेक्स्ट में पहुँचता है। openid.return_to और openid.realm (रिक्वेस्ट का आकार सेक्शन 3 में दिखाया गया है)। इसे निकालना एक मानक ऑपरेशन है। 2026-09-22, के अनुसार, 26 में मुख्य डोमेन लिंक फ़िल्टर पर था, जबकि होस्ट जिस पर Steam लॉगिन था, वह लिंक फ़िल्टर पर नहीं था। Valve ने किसी भी ऑपरेटर-विशिष्ट प्रवर्तन रिकॉर्ड का प्रकाशन नहीं किया है, इसलिए सार्वजनिक डेटा से यह स्थापित नहीं किया जा सकता कि लिंक फ़िल्टर के अलावा इन होस्ट्स पर कोई अन्य उपाय लागू किया गया है या नहीं।\n\nलागत कौन वहन करता है\nसंग्रहीत शिकायतों में पैटर्न\n\nसमीक्षित शिकायतों में, Steam सपोर्ट की 'API' की-हाइजैक दावे पर प्रतिक्रिया एक ही रूप में होती है: पुनर्स्थापना से इनकार, खाते और इसकी API कुंजी के लिए उपयोगकर्ता की जिम्मेदारी का हवाला, और टिकट बंद करना। इस दस्तावेज़ में प्रभावित खातों या खोए मूल्य का कोई समग्र आंकड़ा अनुमानित नहीं किया गया है; ऐसे आंकड़े का कोई स्रोत नहीं मिला है।\n\nप्रश्न यह नहीं है कि व्यक्तिगत उपयोगकर्ताओं ने गलतियाँ कीं या नहीं। प्रश्न यह है कि उस आर्किटेक्चर के लिए कौन जिम्मेदार है, जिसने 2023, तक एक चोरी की कुकी के साथ POST अनुरोध को बिना किसी सूचना और बिना द्वितीयक प्रमाणीकरण के उच्च-अधिकार वाला ट्रेडिंग क्रेडेंशियल बनाने की अनुमति दी।\nदस्तावेज़ के रूप में SSA बनाम अनुबंध के रूप में SSA\nइस रिकॉर्ड का मूल्यांकन करने वाली अदालत एसएसए को अलग से नहीं पढ़ेगी।\n\n2026. यह वकील के 10 अक्टूबर के 2025 पत्र के साथ पढ़ा जाएगा, जिसमें डिवाइस-स्तर की सहसंबंध, auth-host पंजीकरण तिथियाँ, बैच पंजीकरण टाइमस्टैम्प, API-key अनुरोध पेलोड और जुलाई के 2016 नोटिस और सितंबर में अभी भी संचालित हो रहे प्लेटफ़ॉर्म के बीच के दस वर्षों का वर्णन है। यही वह रिकॉर्ड है जिसे Valve को संबोधित करना होगा।\n\nरिकॉर्ड के विरुद्ध SSA / मुख्य बिंदु\n\"वाणिज्यिक उपयोग नहीं\" — मार्केट की ऊपरी सीमा उच्च-मूल्य की बिक्री को वाणिज्यिक तृतीय-पक्ष बाजारों में धकेलती है।\n\"उपयोगकर्ता API कुंजियों के लिए उत्तरदायी\" — 2023 से पहले कुंजी एंडपॉइंट पर कोई दूसरा कारक नहीं।\n\"हम उल्लंघनकर्ताओं के खिलाफ प्रवर्तन करते हैं\" — जुलाई 2016 से कोई प्रति-ऑपरेटर प्रवर्तन रिकॉर्ड प्रकाशित नहीं किया गया है।\n\"आप शर्तों से सहमत हुए\" — हाईजैक पैटर्न में स्वीकृति स्क्रिप्ट द्वारा प्रस्तुत की जाती है, खाता धारक द्वारा नहीं।\nनिष्कर्ष · रिकॉर्ड क्या स्थापित करता है और हम क्या मांगते हैं\nनिष्कर्ष। वे रिकॉर्ड जिन्हें हम मांगते हैं।\nप्रसंग और स्रोत सीमाएँ\n\nनीचे दी गई प्रत्येक खोज उपरोक्त अनुभागों में दिनांकित सार्वजनिक अभिलेख से जुड़ी है। ये अनुरोध उन प्राधिकरणों को संबोधित हैं जो उस एक चीज़ को जबरदस्ती प्राप्त कर सकते हैं जिसे यह जांच प्राप्त नहीं कर सकती: Valve के अपने प्रवर्तन, पहुँच और प्रसंस्करण अभिलेख।\n\nप्रत्येक अनुरोध एक दिनांकित निष्कर्ष का अनुसरण करता है। प्राधिकरण ऐसे अभिलेखों की मांग कर सकते हैं जिन्हें यह सार्वजनिक-स्रोत जांच जबरदस्ती प्राप्त नहीं कर सकती।\n\nसार्वजनिक अभिलेख से जो स्थापित होता है\n44 लाइव प्लेटफ़ॉर्म एक अलग पंजीकरण योग्य डोमेन — 27 के माध्यम से प्रमाणीकरण करते हैं, जिसमें एक प्रकाशित प्रति-मार्ग साक्ष्य फ़ाइल होती है, 17 जिसे मैन्युअल संग्रह से एकत्रित किया जाता है और अलग से सूचीबद्ध किया जाता है। 2026-09-22, के अनुसार, 26 जोड़ों के मुख्य डोमेन को Steam लिंक फ़िल्टर में ब्लॉक किया गया था, जबकि लॉगिन वह होस्ट नहीं था — csgogem.com ब्लॉक किया गया था। api.csgem.com मार्च से पंजीकृत2014.Steam को वह होस्टनाम प्राप्त होता है openid.realm और openid.return_to हर लॉगिन पर। धारा 3\n13 जुलाई 2016Valve ने सार्वजनिक रूप से उस तंत्र का नाम लिया और उसे प्रतिबंधित कर दिया, और उनके वकील की 20 जुलाई 2016 की नोटिस ने दस दिन की समयसीमा निर्धारित की। उस समयसीमा के बाद से पिछले दस वर्षों में किसी भी ऑपरेटर-वार प्रवर्तन रिकॉर्ड का प्रकाशन नहीं किया गया है। धारा 11\nSteam वेब API की मुख्य एंडपॉइंट ने केवल एक सत्र कुकी के आधार पर, बिना किसी द्वितीयक कारक के, 2023. से पहले उच्च-अधिकार वाला, व्यापार-सक्षम क्रेडेंशियल जारी किया। धारा 5\nGDPR लेख 15 अनुरोध (टिकट HT-2YBP-F7JP-D4VB) तीन दिनों के बाद स्व-सेवा लिंक के साथ बिना किसी डेटा के बंद कर दिया गया। धारा 18\nहम प्रत्येक प्राधिकरण से क्या पूछते हैं\nवाशिंगटन राज्य जुआ आयोग\n2016 फ़ाइल को फिर से खोलें। ऑपरेटर-दर-ऑपरेटर विवरण मांगें कि दस-दिन की सूचनाओं के बाद किन खातों, बॉट्स और रिटर्न होस्ट्स को अक्षम किया गया था, और बाद में किन ऑपरेटरों ने फिर से पहुँच प्राप्त की। धारा 2\nएचएमबीबीएफडीआई (हैम्बर्ग; Valve जीएमबीएच)\nपरीक्षण करें कि क्या अनुच्छेद 15 प्रतिक्रिया ने नियंत्रक के दायित्व को पूरा किया, और अभियुक्त की पहचान करने के लिए प्रासंगिक API-कुंजी पंजीकरण और पहुँच रिकॉर्ड का प्रकटीकरण अनिवार्य करें। धारा 18\nडीएसए डिजिटल-सेवा समन्वयक\nauth-host राउटिंग को रिकॉर्ड में सूचना के रूप में दर्ज करें, फिर जब जानकारी दस्तावेजीकृत हो जाए, तो आकलन करें कि क्या Valve की प्रतिक्रिया उसकी जिम्मेदारियों को पूरा करती है। धारा 16\nकोई भी डेटा विषय\nअपने स्वयं के खाते के लिए वही रिकॉर्ड अनुरोध करने हेतु अनुच्छेद 15 टेम्पलेट का उपयोग करें; एक संरक्षित रिकॉर्ड यह परीक्षण कर सकता है कि रीसेट किसने आरंभ किया या कुंजी किसने बनाई। परिशिष्ट G\n\nचारों के पीछे एक ही अनुरोध है: केवल Valve के पास मौजूद प्रवर्तन, पहुँच और प्रसंस्करण रिकॉर्ड प्रकाशित करें। एक होमपेज चेतावनी, एक दस-दिवसीय पत्र और एक स्व-सेवा पृष्ठ नियंत्रण के दावे हैं। नियंत्रण का प्रयोग किया गया या नहीं, यह एक ऐसा प्रश्न है जिसका उत्तर सार्वजनिक रिकॉर्ड नहीं दे सकता, लेकिन एक नियामक दे सकता है।\n\nपरिशिष्ट — प्राथमिक प्रदर्श और कार्यशील सामग्री\nपरिशिष्ट A — वकील पत्राचार\nसाक्ष्य ज्ञापन — स्रोत 1 द्वारा प्रदान की गई सामग्री\n\nखंड 1,18 और 19. में निर्भर परामर्श पत्राचार के लिए साक्ष्य आधार और स्रोत स्थिति\n\nसाक्ष्य आधार और स्रोत स्थिति — स्रोत द्वारा प्रदान किए गए दस्तावेज़ 1\nजिस उपयोगकर्ता पर स्थायी प्रतिबंध लगने से यह ऑडिट शुरू हुआ, वह इसका विषय नहीं है। यह यहाँ नहीं देखा जाता कि वह प्रतिबंध उचित था या नहीं, और यह दस्तावेज़ न तो उसका बचाव करता है और न ही उस पर विवाद करता है। खाता महत्वपूर्ण नहीं है। जो मायने रखता है वह सामग्री है: स्रोत 1 — प्रतिबंधित खाते के धारक, जिन्हें Valve के वकील से उनकी अपनी GDPR अनुरोध के डेटा विषय के रूप में नीचे दी गई पत्राचार प्राप्त हुई — ने उस पत्राचार और संलग्न केस फाइलों को, साथ ही उन्हें सार्वजनिक रूप से जांचने का अधिकार भी, अग्रेषित किया। नाम छिपाया गया है; दस्तावेज़ों का वर्णन तिथि, निर्माता मेटाडेटा और हैश के आधार पर किया गया है।\n\nGDPRयह पत्राचार एक ईमेल/डीएसएआर अनुरोध के जवाब में भेजा गया था। इस प्रक्रिया के दौरान, Valve के वकील ने हस्ताक्षर के तहत रिकॉर्ड पर एक बयान दिया, जिसमें एक ऐसी क्षमता का वर्णन किया गया था जिसे Steam सपोर्ट ने पहले उपयोगकर्ताओं को तकनीकी रूप से असंभव बताया था। नीचे उद्धृत पैराग्राफ वही बयान है।\n\nलेखकों का उत्पादित लॉग अर्क का आगे का विश्लेषण है इस दस्तावेज़ से हटाया गया स्वतंत्र समीक्षा लंबित है। इस जांच के किसी अन्य भाग द्वारा इस पर भरोसा नहीं किया जाता है।\n\nरिकॉर्ड पर स्वीकारोक्ति: निरंतर डिवाइस-स्तरीय टेलीमेट्री\n\nValve के वकील द्वारा लिखित बताई गई चिट्ठी के पैराग्राफ 1.9 में, Valve के वकीलों ने कहा: 2019 और 2023, के बीच, इस खाते का उपयोग मुख्य रूप से एक ऐसे डिवाइस से किया गया था, जिसका उपयोग दर्जनों चोरी हुए Steam खातों में लॉग इन करने के लिए भी किया गया था।\n\nतथ्य: Valve के वकील ने यहाँ चार वर्षों में फैले खातों में डिवाइस-स्तरीय सहसंबंध का वर्णन किया है। Steam सपोर्ट ने चोरी के शिकारों को बताया कि चोरी हुई वस्तुओं का ट्रैक करना या खातों को उपकरणों से जोड़ना तकनीकी रूप से संभव नहीं था। Steam गार्ड डिवाइस प्राधिकरण सार्वजनिक रूप से प्रलेखित है, इसलिए प्रति-उपकरण रिकॉर्ड का अस्तित्व स्वयं में नया नहीं है; जो नया है वह वकील की लिखित पुष्टि है कि ये रिकॉर्ड कई वर्षों की अवधि में खातों के बीच बनाए रखे और संबंधित किए जाते हैं।\n\nयह क्यों मायने रखता है: वह सहसंबंध जो एक डिवाइस को चार वर्षों में दर्जनों हाईजैक किए गए खातों से जोड़ सकता है, उसी श्रेणी का रिकॉर्ड है जिसे सपोर्ट ने पीड़ितों के लिए उपयोग करने में असमर्थ होने की बात कही। उस श्रेणी के रिकॉर्ड चोरी और पुनर्विक्रय श्रृंखला में खातों और उपकरणों की पहचान करने में सक्षम होंगे। कौन से रिकॉर्ड मौजूद हैं, उन्हें कितनी अवधि तक रखा जाता है, और डेटा विषयों से उन्हें किस आधार पर रोका जाता है, ये पर्यवेक्षी प्राधिकरण के लिए प्रश्न हैं।\n\nस्रोत: Valve के वकील का पत्र दिनांक 1, अक्टूबर 2025,, पैराग्राफ 1.9, और उसका 830-पृष्ठ PDF परिशिष्ट · प्राप्तकर्ता Source 1 को एक GDPR अनुच्छेद 15 अनुरोध के जवाब में · परिशिष्ट का SHA-256 दर्ज किया गया disclosure-audit.json · पत्र स्वयं पुनरुत्पादित नहीं किया गया है; खाता नाम और तृतीय-पक्ष डेटा को छोड़ दिया गया है।\n\nस्थिति: खुला\nसाक्ष्य अभिलेखागार के माध्यम से स्रोत सामग्री उपलब्ध हैं।\nपरिशिष्ट B — उत्पन्न PDF · छुपांकन जाँच\nउत्पादित PDF में की गई छंटनी केवल दिखावटी है: छिपाया गया पाठ अभी भी निकालने योग्य है।\n\nValve के वकील ने GDPR के एक्सेस अनुरोध का उत्तर एक 830-पेज परिशिष्ट के साथ दिया, जिसमें पाठ को हटाने के बजाय उस पर लाल रंग से छपाई की गई है। 902,270 अक्षर काले बार के नीचे बैठते हैं और टेक्स्ट-एक्सट्रैक्शन टूल से सीधे बाहर आते हैं। — जिसमें वे तृतीय-पक्ष पहचानकर्ता भी शामिल हैं जिन्हें छिपाने के लिए बार लगाए गए थे। यहाँ केवल समेकित गणनाएँ प्रकाशित की गई हैं; कोई भी कवर की गई सामग्री पुनरुत्पादित नहीं की गई है, और परिशिष्ट स्वयं प्रकाशित नहीं किया गया है।\n\n1. ज्योमेट्री जांच में क्या पाया गया\n\nGDPR कला. 15 दिनांकित प्रतिक्रिया 1 अक्टूबर 2025 इसके साथ एक 830-पेज PDF परिशिष्ट था (.NET निर्माता मेटाडेटा के लिए Aspose.PDF, उसी तारीख को बनाया और संशोधित)। लेखकों ने पेज-स्तरीय ज्यामिति जांच की: प्रत्येक पेज के लिए, पाठ परत के बाद बनाए गए अपारदर्शी, लगभग काले आयत पाए गए और उनके नीचे स्थित निकालने योग्य अक्षरों की गिनती की गई।\n\nउत्पादित फ़ाइल पर मापा गया\n902,270\nकाले बारों के नीचे से अभी भी पात्र निकाले जा सकते हैं।\nगणना की गई है, अनुमानित नहीं। यह कवर किए गए पात्रों की संख्या है — पीड़ितों, पुनः पहचानों या घटनाओं की नहीं।\n830 / 830\nप्रभावित पृष्ठ — प्रत्येक पृष्ठ\n986\nनिकालने योग्य पाठ पर आयतें\n1,329\nकुल मिलाकर अपारदर्शी काले आयत\nकाले बार टेक्स्ट लेयर पर खींचे गए हैं; वे इसे हटाते नहीं हैं। बार के नीचे का टेक्स्ट मानक PDF उपकरणों से निकाला जा सकता है। केवल समग्र गणनाएँ प्रकाशित की गई हैं; यहाँ कोई आच्छादित सामग्री पुनरुत्पादित नहीं की गई है।\nफोरेंसिक प्रदर्शन: परत पृथक्करण\nASPOSE.PDF .NET वेक्टर ओवरले मॉकअप के लिए (परिशिष्ट P. 412)\n\nखाते के खिलाफ रिपोर्ट दर्ज: [लॉगिन: redacted_user_667]\n\nउपयोगकर्ता द्वारा प्रस्तुत कारण: [टेक्स्ट: \"उपयोगकर्ता ने इन्वेंटरी में डुप्लिकेट आइटम और दुर्व्यवहारपूर्ण व्यापार आचरण की सूचना दी...\"]\n\nअग्रभूमि: <path fill=\"#000\" />खामी: अंतर्निहित UTF-8 स्ट्रीम अक्षुण्ण\n2025 स्रोत: 1 के 10 अक्टूबर 2019 के परामर्श पत्र का PDF परिशिष्ट (830 पृष्ठ, .NET निर्माता मेटाडेटा के लिए Aspose.PDF ) · लेखकों, विधि और प्रति-पृष्ठ गणनाओं द्वारा मापा गया disclosure-audit.json · SHA-1:256, संलग्नक उसी फ़ाइल में दर्ज है · संलग्नक स्वयं प्रकाशित नहीं है।\n2. डेटा विषय प्रतिक्रिया के लिए यह क्यों महत्वपूर्ण है\n\nValve के वकील ने उस व्यक्ति के अपने अभिलेखों की मांग के जवाब में यह फ़ाइल डेटा विषय को भेजी। इस पर लगे बार केवल सजावटी हैं: नीचे का टेक्स्ट कभी हटाया ही नहीं गया था, इसलिए जिन तीसरे पक्ष की पहचानकर्ताओं को छिपाने के लिए बार लगाए गए थे, वे फ़ाइल के साथ प्राप्तकर्ता तक पहुँच गए। एक ऐसी छुपाव जो टेक्स्ट-एक्सट्रैक्शन टूल से हटाया जा सकता है, कुछ भी छिपा नहीं पाता, और यह प्राप्तकर्ता को यह भी नहीं बता पाता कि क्या प्रकट किया गया था और क्या नहीं।\n\nलेख 15(4) ही वह कारण है कि ये प्रतिबंध मौजूद हैं: एक प्रति प्राप्त करने का अधिकार दूसरों के अधिकारों और स्वतंत्रताओं को प्रतिकूल रूप से प्रभावित नहीं करना चाहिए। यह वही दायित्व है जिसे इस उत्पादन ने पूरा नहीं किया। कि इसे अनुच्छेद 4(12) के तहत व्यक्तिगत डेटा उल्लंघन के रूप में वर्गीकृत किया जाना चाहिए या नहीं, यह पर्यवेक्षी प्राधिकरण द्वारा निर्धारित किया जाएगा; प्रकटीकरण स्वयं फ़ाइल में मापा जा सकता है, और वही बाइट्स रखने वाला कोई भी व्यक्ति इसे पुन: उत्पन्न कर सकता है — SHA-256 प्रकाशित है, परिशिष्ट नहीं।\n\nबारों के नीचे जो था, वे खाता नंबर नहीं थे। यह अनुरोधकर्ता के खिलाफ दायर उपयोगकर्ता रिपोर्टों का मूल भाग था, जिनके लेखक संलग्न थे: Steam लॉगिन, जो क्योंकि एक लॉगिन शायद ही कभी केवल Steam पर ही उपयोग किया जाता है, उनके पीछे छिपे व्यक्ति की पहचान करते हैं — लेखकों के अनुसार, दस्तावेज़ में नामित उपयोगकर्ताओं में से 60% से अधिक पूरी तरह से पहचाने जा सकते हैं। — साथ ही उन्होंने जो लिखा था, उसका कच्चा, बिना संपादित पाठ। उस पाठ में मृत्यु की कामनाएँ और आवेदक की राष्ट्रीयता के प्रति अपमानजनक भाषा शामिल है। इस प्रकार पहचाने गए कुछ लोग नाबालिग हैं। प्रोडक्शन ने उस व्यक्ति को, जिसकी उन्होंने रिपोर्ट की थी, पत्रकारों की नामित सूची सौंपी।, जो कि वही सटीक हानि है जिसे रोकने के लिए अनुच्छेद15(4) लिखा गया है।\n\nफ़ाइल के आसपास का क्रम उसकी सामग्री जितना ही महत्वपूर्ण है। अनुरोध को पहले पहचान के अतिरिक्त प्रमाण की मांग के साथ अस्वीकार किया गया, इस आधार पर कि अनुरोधकर्ता के छद्म ईमेल पते में उसका नाम नहीं था; बाद में हुई देरी के दौरान खाते पर स्थायी रूप से प्रतिबंध लगा दिया गया। अंततः डेटा प्रदान करने वाले पत्र में, अनुच्छेद 12(3) महीने की समय-सीमा समाप्त होने के छह सप्ताह से अधिक समय बाद, प्राप्तकर्ता को आपराधिक अभियोजन की धमकी दी गई और जब तक उसने अपने खाते की गतिविधि वकील को समझा नहीं दी, तब तक उसके शेष डेटा को रोक लिया गया। यह खुलासा दो ऐसे सवालों का भी समाधान करता है जिनका जवाब Valve ने सार्वजनिक रूप से नहीं दिया है: प्रस्तुत रिकॉर्ड दिखाते हैं कि खाते को जोड़ने का काम 2019, तक जाता है और आंतरिक टेलीमेट्री की गहराई Valve ने कभी वर्णन नहीं की है।\n\nइस अनुभाग का दायरा: यहाँ का अवलोकन केवल संशोधन की प्रक्रिया तक सीमित है, जिसे प्रस्तुत फ़ाइल पर मापा गया है। लेखकों का प्रस्तुत लॉग्स का आगे का विश्लेषण स्वतंत्र समीक्षा के लंबित होने तक रोका गया है और इस दस्तावेज़ के अन्य भागों में उस पर भरोसा नहीं किया गया है।\n\n2025 साक्ष्य: 1 के 10 अक्टूबर 2019 के वकील पत्र और उसका PDF परिशिष्ट (SHA-256, ऑडिट फ़ाइल में दर्ज); पृष्ठ-स्तरीय PDF मापन और विधि ↗. अनुरोध का क्रम, पेज-8 का अस्वीकार और प्रकट किए गए रिकॉर्डों का वर्णन, PhishDestroy के विवरण में पूरी तरह से दिए गए हैं, \"मेरा कुत्ता बनाम एलीट GDPR वकील\", 17 अगस्त 2026 ↗ संग्रहीत 2026-08-21 ↗. खाता नाम और तृतीय-पक्ष डेटा यहां छोड़े गए हैं; बारों द्वारा ढके गए किसी भी भाग को पुन: प्रस्तुत नहीं किया गया है।\n\nPage 8 of the covering letter refuses part of the request, and states the reason in writing: Eine genauere Auskunft ist aufgrund des Schutzes der personenbezogenen Daten anderer Nutzer der Steam-Plattform… nicht möglich. — a more detailed answer is not possible, because the personal data of other Steam users must be protected. The 830-page appendix was in the same package. What the bars covered was not account numbers: it was the reports filed against the requester, their authors named, with the raw unredacted messages attached. The account holder had asked Valve, through its counsel, for his own file; what he could extract from it was other people's. Nothing in this appendix turns on who drew the boxes. What it establishes is that the protection Valve invoked as its ground for withholding is the protection this same production failed, in the same envelope, on the same day.\nसमर्थन और कानूनी पत्राचार प्रदर्शनी\n\nस्रोत: https://phishdestroy.io/steam_dossier/hi/index#exhibit-gallery-section\n\nपरिशिष्ट डी — स्रोत संग्रह\nचयनित प्राथमिक अभिलेख\n\nआर्काइव से छह रिकॉर्ड — Valve के ट्रैकरों में तीन GitHub मुद्दे और विवादित समर्थन परिणामों के तीन Reddit खाते। प्रत्येक स्रोत उस दावे, संग्रहीत पाठ और उससे उठने वाले प्रश्न से जुड़ा रहता है।\n\n1 / 6 चयनित रिकॉर्ड\nएक स्रोत रिकॉर्ड चुनें\nGH-01 / GITHUBOpen in saved build\nHardware keys, requested in 2016\n\nValveSoftware / steam-for-linux · #4521 · 2016-06-27\n\nA user asked Valve to support U2F hardware keys as an alternative second factor. The saved issue carries both Feature Request and reviewed labels, with its state recorded as open.\n\nI request U2F usb dongle support in steam as an alternative.\n\nExcerpt from the GitHub issue ↗\nDocumented record\nA dated request for an additional account safeguard, published in Valve's own issue tracker and labelled reviewed.\nAccountability demand\nPublish the product decision, the response date and the protection delivered after review.\nRead saved record →Open GitHub ↗\nIn the dossier: Account safeguards →Archive #484 · build 2026-09-17\nGH-02 / GITHUBOpen in saved build\nCrash reports without an effective opt-out\n\nValveSoftware / steam-for-linux · #6459 · 2019-08-18\n\nThe reporter describes a Steam client from 12 August 2019 on Ubuntu 16. They say disabling the crash-upload destination did not persist after a restart, and include the relevant configuration.\n\nIf I disable the `ServerURL`, it gets overwritten after every reboot.\n\nExcerpt from the GitHub issue ↗ archived 2026-04-19 ↗\nDocumented record\nA specific privacy complaint with a client date, operating system and configuration excerpt. The saved issue is open.\nAccountability demand\nIdentify the investigation, the affected builds and the change that made the opt-out effective.\nRead saved record →Open GitHub ↗archived 2026-04-19 ↗\nIn the dossier: Request the underlying records →Archive #467 · build 2026-09-17\nGH-03 / GITHUBOpen in saved build\nAuth-ticket abuse reported to Valve\n\nValveSoftware / Source-1-Games · #3857 · 2022-02-26\n\nThe author alleges that a server operation retained Steam authentication tickets after players disconnected and used misleading server listings. The post asks Valve to address the behavior.\n\nMaking their servers look packed.\n\nExcerpt from the GitHub issue ↗\nDocumented record\nA public abuse report lodged in Valve's tracker on 26 February 2022. Its saved state is open; the report includes links to screenshots.\nAccountability demand\nProduce the investigation result and the mitigation record for the reported authentication-ticket abuse.\nRead saved record →Open GitHub ↗\nIn the dossier: Dataset scope →Archive #768 · build 2026-09-17\nRD-01 / REDDITAuthor's account\n44 disputed Market purchases\n\nr/DotA2 · author handle withheld · 2022-07-07\n\nThe author reports 44 unauthorized Market purchases on 6 July 2022 and roughly $500+ in losses. They say two-factor authentication was enabled and describe repeated template replies from support.\n\n2nd ticket in and I have still yet to receive a non robotic copy paste template response from Steam.\n\nExcerpt from the Reddit post ↗ archived 2025-03-20 ↗\nDocumented record\nA dated account of disputed purchases, with links to transaction screenshots and a support response. The amounts and events are the author's report.\nAccountability demand\nReconcile the disputed purchases with transaction and session logs. Explain the evidence behind support's decision.\nRead saved record →Open Reddit ↗archived 2025-03-20 ↗\nIn the dossier: Support and enforcement →Archive #4,533 · build 2026-09-17\nRD-02 / REDDITAuthor's account\nA permanent ban and closed appeals\n\nr/ohnePixel · author handle withheld · 2024-12-09\n\nThe author disputes a permanent ban and says support cited suspected account transfer and community reports. They describe closed tickets and plans to request their personal data.\n\nI explained my situation and asked for more details, but they're sticking to their decision and closing my tickets.\n\nExcerpt from the Reddit post ↗\nDocumented record\nA preserved appeal account, including the reasons the author says support supplied and links to four images. The post date comes from the selected support export.\nAccountability demand\nIdentify the evidence supporting the permanent ban and the review available to challenge it. Closing an appeal does not explain the decision.\nRead saved record →Open Reddit ↗\nIn the dossier: Request the underlying records →Archive #4,766 · build 2026-09-17\nRD-03 / REDDITAuthor's account\nA recovery reset and a reported $10,000 loss\n\nr/legaladvice · author handle withheld · 2025-05-09\n\nThe author alleges that support reset credentials and disabled account protections after someone else submitted a recovery ticket. They report a loss of about US$10,000 from an inactive account.\n\nSteam Support reset my password and turned off all my account security.\n\nExcerpt from the Reddit post ↗\nDocumented record\nA preserved allegation about the recovery process overriding account safeguards. The saved post records what the author says support told them.\nAccountability demand\nIdentify who authorised the reset, the ownership evidence they accepted and the access log. Account recovery is part of the security system Valve controls.\nRead saved record →Open Reddit ↗\nIn the dossier: Request the underlying records →Archive #4,592 · build 2026-09-17\n\nछह चयनित रिकॉर्ड। GitHub बताता है कि सहेजा गया बिल्ड कैसा है। Reddit पोस्ट लेखकों के खातों को संरक्षित करते हैं।\n\nछह रिकॉर्ड डाउनलोड करें ↓\n\nखोजने योग्य बिल्ड में शामिल हैं 16,319 अलग-अलग रिकॉर्ड393 Trustpilot, 5,635 Reddit, 2,395 GitHub, 276 वेब और 7,620 विकी रिकॉर्ड्स। कई रिकॉर्ड एक ही घटना से संबंधित हो सकते हैं। अलग 40,448-पंक्ति मास्टर एक्सपोर्ट का दायरा अलग है।\n\nपूरे आर्काइव में खोजें ↗ · निर्माण घोषणा ↗ · डेटासेट का दायरा और गणनाएँ →\n\nपरिशिष्ट ई — केस अध्ययन\nArchiSteamFarm और स्वचालन खंड\n\nएक ओपन-सोर्स कार्ड-फार्मिंग टूल, जिसकी अपनी FAQ में कहा गया है कि यह लाखों खातों पर चलता है, सब्सक्राइबर एग्रीमेंट की धारा (§ 4.C) के खिलाफ है जो स्वचालन को प्रतिबंधित करती है। मैकेनिक्स — एक फार्म को Valve से क्या खरीदना होता है इससे पहले कि वह कुछ भी उत्पादन कर सके, कार्ड को नकद में बदलने का हर तरीका लाइसेंस का उल्लंघन क्यों करता है, प्रवर्तन रिकॉर्ड और कार्ड अर्थव्यवस्था का संचालन कौन करता है — पूरी तरह से में वर्णित हैं प्रदर्शनी V ↗.\n\nSteam सदस्य अनुबंध, § 4.C, में कहा गया है:\n\nआप Steam पर सामग्री और सेवाओं के साथ किसी भी प्रकार से संवाद करने के लिए किसी भी प्रकार की स्क्रिप्ट्स, बॉट्स, मैक्रोज़, या अन्य गैर-मानव-नियंत्रित प्रणालियों ('ऑटोमेशन') का उपयोग नहीं कर सकते। — Steam सब्सक्राइबर समझौता § 4.C (वर्तमान) ↗ संग्रहीत 2026-09-18 ↗\n\nValve इस खंड को लागू करता है। यह इसमें बहुत अच्छा है। के अक्सर पूछे जाने वाले प्रश्न आर्चीस्टीमफार्म (एएसएफ) — एक ओपन-सोर्स टूल जिसे इसकी अपनी डॉक्यूमेंटेशन इस पर चलने वाला बताती है कई मिलियन से अधिक Steam खाते 11 साल पहले पहली रिलीज़ के बाद से — यह तीन Steam सपोर्ट संदेशों को पुन: प्रस्तुत करता है, जिनमें उन उपयोगकर्ताओं को स्थायी रूप से प्रतिबंधित किया गया था जिन्होंने बॉट नेटवर्क चलाए थे। Valve ने इन नेटवर्कों का पता लगाया, उन्हें नाम दिए और नष्ट कर दिया। इसलिए प्रासंगिक प्रश्न यह नहीं है कि क्या Valve बड़े पैमाने पर ऑटोमेशन का पता लगा सकता है।\n\nपरियोजना का आधिकारिक आर्चिस्टीमफार्म अक्सर पूछे जाने वाले प्रश्न सीधे प्रतिबंध के जोखिम को संबोधित करता है:\n\nयह अत्यंत असंभव है, यह देखते हुए कि ASF का उपयोग लाखों से अधिक Steam खातों पर किया जा रहा है, इसकी पहली रिलीज़ से जो 11 साल पहले हुई थी — लेकिन फिर भी यह एक संभावना है, वास्तविक संभावना की परवाह किए बिना।\n\nValve स्पष्ट रूप से 'Steam के आलसी' के अस्तित्व को स्वीकार करता है, जैसा कि यहां कहा गया है, इसलिए अगर आप मुझसे पूछें तो मुझे पूरा यकीन है कि अगर वे उनसे सहज नहीं होते, तो वे पहले ही कुछ कर चुके होते, बजाय इसके कि यह बताने के कि वे VAC-संबंधी समस्याएं पैदा कर सकते हैं। यहाँ मुख्य शब्द 'Steam' आइडलर हैं, उदाहरण के लिए ASF, न कि गेम आइडलर।\"\n\n— आर्किस्टीमफार्म अक्सर पूछे जाने वाले प्रश्न, जस्टआर्चीनेट। स्रोत: GitHub विकी ↗ · सत्यापित शब्दशः 2026-09-22\n\nउसी FAQ में \"क्या किसी को इसके लिए प्रतिबंधित किया गया?\" का उत्तर है हाँ, और यह वही पुन: प्रस्तुत करता है जो Steam सपोर्ट ने उन तीनों को लिखा था:\n\n1,000+ बॉट्स · व्यापार प्रतिबंधित\nSteam ऐसा लगता है कि इस खाते का उपयोग बॉट खातों के एक नेटवर्क को प्रबंधित करने के लिए किया गया था। बॉटिंग, ईमेल सेवा सदस्यता समझौते का उल्लंघन है।\n\n170+ बॉट्स · स्थायी रूप से प्रतिबंधित, 2017 विंटर सेल\nइस खाते का उपयोग Steam पर अवैध रूप से संग्रहणीय कार्ड इकट्ठा करने के साथ-साथ संबंधित और केवल वाणिज्यिक गतिविधियों के लिए किया गया था। यह खाता स्थायी रूप से अवरुद्ध कर दिया गया है और Steam सहायता इस मामले पर अतिरिक्त सहायता प्रदान नहीं कर सकती।\n\n120+ बॉट्स · स्थायी रूप से प्रतिबंधित\nइस और अन्य खातों का उपयोग हमारे नेटवर्क इंफ्रास्ट्रक्चर को बाधित करने के लिए किया गया था, जो कि Steam की ऑनलाइन आचार संहिता का उल्लंघन है।\n\n— Steam समर्थन संदेश ArchiSteamFarm FAQ के \"क्या किसी को इसके लिए प्रतिबंधित किया गया?\" अनुभाग में पुनरुत्पादित। स्रोत ↗ · सत्यापित शब्दशः 2026-09-22\n\nदोनों रिकॉर्डों को एक-दूसरे के बगल में रखें। 1,000 फार्मिंग बॉट्स वाले एक निजी उपयोगकर्ता की पहचान की गई, उसे बताया गया कि \"बॉटिंग Steam सदस्यता अनुबंध का उल्लंघन है\", और स्थायी रूप से हटा दिया गया। इस दस्तावेज़ में शामिल वाणिज्यिक प्लेटफ़ॉर्म अपने मुख्य व्यवसाय के रूप में स्वचालित Steam खाते चलाते हैं, और कहीं बड़े पैमाने पर ऐसा करते हैं, तथा हर लॉगिन पर Valve के अपने OpenID के माध्यम से प्रमाणीकरण करते हैं — और इनमें से किसी के भी लिए प्रति-ऑपरेटर प्रवर्तन रिकॉर्ड प्रकाशित नहीं किया गया है। यह प्रावधान काम करता है। सवाल यह है कि यह किसकी ओर निर्देशित है।\n\nयहाँ ASF पर किसी भी बात का आरोप नहीं है, और Valve की स्थिति की अपनी व्याख्या है — इसके लेखक ने स्पष्ट रूप से कहा है कि \"ASF को Valve द्वारा अधिकृत नहीं किया गया है\"। यहाँ इस उपकरण का उपयोग एक मापक यंत्र के रूप में किया गया है: यह दिखाता है कि Valve बॉट नेटवर्क का पता लगाता है, उन्हें लिखित रूप में नामित करता है और स्थायी रूप से प्रतिबंधित कर देता है। Valve एक ही वाक्य में प्रश्न का निपटारा कर सकता है, यह प्रकाशित करके कि वह कौन सी व्यावसायिक स्वचालन को अधिकृत करता है, और बाकी के संबंध में उसने क्या कार्रवाई की, इसका ऑपरेटर-वार रिकॉर्ड प्रस्तुत करके।\n\nजहाँ कार्ड फार्मिंग Valve की आय को प्रभावित करती है\n\nफार्म्ड ट्रेडिंग कार्ड्स को Steam कम्युनिटी मार्केट पर बेचा जाता है, जो मार्केट के भीतर पूरी हुई प्रत्येक बिक्री पर लगभग 15% का संयुक्त शुल्क लेता है; खाते ने Steam पर $5.00 USD खर्च किए होने चाहिए, तभी वह कोई कार्ड प्राप्त कर सकता है; और कार्ड ड्रॉप्स के लिए गेम का स्वामित्व या इन-गेम खरीदारी आवश्यक है। यहाँ कोई समग्र राजस्व आंकड़ा अनुमानित नहीं किया गया है — परिचालन पैमाना केवल ASF FAQ में बताए अनुसार दर्शाया गया है। FAQ में Valve को भी दर्ज किया गया है, जो अलग करता है। Steamइडलर (कार्ड फार्मिंग) से गेम आइडलर्स; देखें ASF अक्सर पूछे जाने वाले प्रश्न ↗. यांत्रिकी पूरी तरह से में निर्धारित की गई हैं प्रदर्शनी V — पैमाना और व्यावसायिक जाल.\n\nविषयआर्चीस्टीमफार्म — स्वचालित कार्ड खेती\nनिर्दिष्ट पैमानालाखों खाते (ASF FAQ के अनुसार — सटीक सक्रिय संख्या अज्ञात)\nगिना गया, उद्धृत नहीं10,880,610 ASF के अपने Steam समूह में कुल API प्रविष्टियाँ (5,360,499 गैर-सीमित, जैसा कि Steam दिखाता है) — FAQ में \"मिलियंस\" कोई कहानी नहीं है, यह एक जनगणना है। 88.97% पर किसी भी प्रकार का Steam प्रतिबंध नहीं है। पूर्ण प्रतिबंध जनगणना ↗\nटूल की अपनी दस्तावेज़ीकरण में प्रकटीकरण\nASF, प्रोजेक्ट दस्तावेज़ीकरण के अनुसार, Steam क्लाइंट को लॉन्च किए बिना ही हेडलेस मोड में खातों को लॉग इन करता है और कार्ड ड्रॉप्स के लिए गेम्स को निष्क्रिय रखता है।\nFAQ में यह बताया गया है कि Valve को \"Steam के आलसी लोगों\" की जानकारी है और \"अगर वे उनसे खुश नहीं होते, तो वे पहले ही कुछ कर चुके होते\"।\n11 वर्षों से लक्षित प्रवर्तन की कोई रिपोर्ट नहीं मिली (FAQ के अनुसार); कम्युनिटी मार्केट के भीतर होने वाली कार्ड बिक्री पर Steam की संयुक्त शुल्क दर लगभग 15%. होती है।\nFAQ में प्रति ऑपरेटर दस खातों की अनुशंसित अधिकतम सीमा बताई गई है और इसे Valve को श्रेय दिया गया है: \"यह सिफारिश आंतरिक Valve दिशानिर्देशों के साथ-साथ हमारी अपनी सुझावों पर आधारित है।\" Valve द्वारा ऐसा कोई दिशानिर्देश प्रकाशित नहीं किया गया है।\nतकनीकी सीमा, उसी FAQ के अनुसार: \"आप एक ही IP और एक ही ASF इंस्टेंस के साथ अधिकतम 100-200 बॉट्स चला सकते हैं।\"\nफार्म्ड प्लेटाइम को Valve द्वारा रिकॉर्ड किया जाता है — \"यह आमतौर पर हर लगभग 30 मिनट में अपडेट होता है\" — और § 4.C \"गेमप्ले आँकड़ों की जालसाजी (e.g., बढ़ा-चढ़ाकर दिखाए गए जीत या हार, XP, प्लेटाइम)\" को एक निषिद्ध कृत्य के रूप में सूचीबद्ध करता है।\nस्रोत\nआधिकारिक JustArchi ASF FAQ विकी ↗ ArchiSteamFarm रिपॉजिटरी ↗ संचित 2026-09-24 ↗\nस्वचालन खंड स्पष्ट है; ASF FAQ में वर्षों से कहा गया है कि यह उपकरण लाखों खातों पर चलता है; इसके खिलाफ कोई लक्षित प्रवर्तन रिपोर्ट नहीं किया गया है। नियम और उसके अनुप्रयोग के बीच का अंतर रिकॉर्ड है; इसका कारण यहाँ स्थापित नहीं किया गया है।\nपूर्ण प्रदर्शनीकार्ड अर्थव्यवस्था: प्रक्रिया, पैमाना, लाइसेंस और इसे कौन नियंत्रित करता है ↗Valve से एक कार्ड बनाने से पहले एक फार्म को क्या-क्या खरीदना होता है; §4.C की वे दो पंक्तियाँ जो कार्ड फार्मिंग को उसके प्रभावों के आधार पर परिभाषित करती हैं; कार्ड को कैश आउट करने का हर तरीका लाइसेंस का उल्लंघन क्यों करता है Valve ने लिखा था जबकि Valve दरवाजे पर शुल्क लेता है; प्रवर्तन रिकॉर्ड जिसमें जून की 2025 VAC लहर और साझा फोन नंबर द्वारा चेन-प्रतिबंध शामिल हैं; और Valve के कर्मचारी तथा सामुदायिक मॉडरेटर कार्ड-ट्रेडिंग और प्रतिबंध-सूची सेवाओं का संचालन करते हुए पाए गए, जो Steam के आसपास हैं।प्रतिबंध जनगणनाहमने Valve से नहीं पूछा कि खेत कितना बड़ा है। हमने इसकी गिनती की। ↗10,880,610 कुल खातों (सीमित और गैर-सीमित) को ArchiSteamFarm के अपने Steam समूह से पढ़ा जाता है, जिसमें सॉफ़्टवेयर पहली बार लॉन्च करते समय डिफ़ॉल्ट रूप से शामिल हो जाता है, जब तक कि उपयोगकर्ता समूह-संयोजन सेटिंग को अनचेक न कर दे (जिससे वाणिज्यिक बॉट फार्म और डिफ़ॉल्ट छोड़ने वाले नियमित खिलाड़ी दोनों कैप्चर होते हैं)। 88.97% इन पर किसी भी प्रकार का Steam प्रतिबंध नहीं है; जिन पर 11% लागू है, उनमें से 99.8% केवल कॉस्मेटिक कम्युनिटी प्रतिबंध हैं जो ट्रेडिंग कभी नहीं रोकते। SteamRep के साथ क्रॉस-चेक करने पर, सूचीबद्ध स्कैमर्स में से 67.77% एंटी-चीट प्रतिबंध हटाए जाने के बाद स्वतंत्र हो जाते हैं। पंजीकरण तिथि, भूगोल और सर्वाइवल ब्रेकडाउन के साथ — असली पैमाना, मापा गया, बताया नहीं गया।\n\nपरिशिष्ट F — कार्यशील खाता-बही\n\nनियमों का खाका: रिकॉर्डेड प्लेटफ़ॉर्मों के विरुद्ध प्रावधान\n\nएक नियम चुनें; रजिस्टर इसके अंतर्गत टैग किए गए प्लेटफ़ॉर्मों को उनकी मुख्य डोमेन, घोषित auth होस्ट और सहेजे गए लिंक फ़िल्टर परिणाम के साथ सूचीबद्ध करता है। एक ब्लॉक की गई वेबसाइट, साइन-इन के लिए एक अन्य डोमेन: नियम का अनुसरण उस मार्ग तक करें जो शेष रहता है।\n\n175रिकॉर्ड्स लिंक किए गए\nइस नियम को\n174 प्राथमिक डोमेन0 सी एंड डी उल्लेख\nनियम अंश / एसएसए § 2.G\nव्यावसायिक उपयोग और खाते पर शुल्क\n“…exploit the Content and Services or any of its parts for any commercial purpose, except as expressly permitted elsewhere in this Agreement (including any Subscription Terms or Rules of Use).”\nरिकॉर्ड्स का पालन करें\nप्लेटफ़ॉर्म रजिस्टर 175\nस्केल आकृतियाँ स्रोत अनुमान हैं।\n\n175 175 रिकॉर्ड्स के\n\nसेवा / अभिभावक समूह\tमुख्य डोमेन / रजिस्ट्री\tनिरीक्षित लेखक डोमेन / आयु\tमाप / दर्ज प्रतिक्रिया\n\nCasino\n\tcsgoempire.com\n11.3 yearsRegistered 2015-06-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgoempirelogin4.com\n6.2 yearsRegistered 2020-07-20\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustreaper.com\n23.2 yearsRegistered 2003-06-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustreaper.com\n23.2 yearsRegistered 2003-06-24\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustly.com\n12.4 yearsRegistered 2014-05-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustly.com\n12.4 yearsRegistered 2014-05-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette Casino\n\tcsgofast.com\n11.5 yearsRegistered 2015-03-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsteam-login.authtofast.com\n83 daysRegistered 2026-06-30\nRDAP ↗ · authtofast.com (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tduelbits.com\n6.6 yearsRegistered 2020-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nswitchflips.com\n6.4 yearsRegistered 2020-04-21\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opener\n\tfarmskins.com\n10.5 yearsRegistered 2016-03-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsteam.kobal.cc\n9.7 yearsRegistered 2017-01-07\nRDAP ↗ · kobal.cc (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgoluck.com\n9.3 yearsRegistered 2017-05-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgoluck.com\n9.3 yearsRegistered 2017-05-18\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tinsane.gg\n7.5 yearsRegistered 2019-04-02\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.insane.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcs2skin.com\n3.5 yearsRegistered 2023-03-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncs2skin.com\n3.5 yearsRegistered 2023-03-06\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tjuice.gg\n7.9 yearsRegistered 2018-10-19\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nletmeinjuice.com\n2.4 yearsRegistered 2024-04-15\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tggdrop.com\n8.6 yearsRegistered 2018-02-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nggauth.com\n3.4 yearsRegistered 2023-05-03\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Casino\n\thowl.gg\n9.5 yearsRegistered 2017-03-16\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhowl.uno\n41 daysRegistered 2026-08-11\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tchicken.gg\n5.7 yearsRegistered 2021-01-11\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nchicken.gg\n5.7 yearsRegistered 2021-01-11\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgocasino.gg\n2.6 yearsRegistered 2024-02-17\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.csgocasino.gg\n2.6 yearsRegistered 2024-02-17\nWHOISFREAKS ↗ · csgocasino.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Casino\n\thunt.gg\n6.9 yearsRegistered 2019-11-04\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.hunt.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Battles\n\tcsbattle.com\n9.8 yearsRegistered 2016-12-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsbattle.com\n9.8 yearsRegistered 2016-12-10\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskinrave.gg\n3.1 yearsRegistered 2023-08-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinrave.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsdouble.gg\n261 daysRegistered 2026-01-03\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsdouble.gg\n261 daysRegistered 2026-01-03\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustchance.com\n8.0 yearsRegistered 2018-10-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhgfuihd.com\n7.6 yearsRegistered 2019-01-27\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Automation\n\tcobaltlab.tech\n3.5 yearsRegistered 2023-03-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncobaltauth.com\n1.7 yearsRegistered 2025-01-07\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\traided.gg\n171 daysRegistered 2026-04-03\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.raided.gg\n171 daysRegistered 2026-04-03\nIP2WHOIS ↗ · raided.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustneo.gg\n1.3 yearsRegistered 2025-06-20\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustneo.gg\n1.3 yearsRegistered 2025-06-20\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tsplits.gg\n3.7 yearsRegistered 2023-01-23\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsplits.gg\n3.7 yearsRegistered 2023-01-23\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Upgrader\n\tupgrader.pro\n1.2 yearsRegistered 2025-07-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nupgauth.space\n38 daysRegistered 2026-08-14\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskin.fans\n8.2 yearsRegistered 2018-07-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skinfans.com\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\thotpizza.one\n1.8 yearsRegistered 2024-12-07\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhotpizza.one\n1.8 yearsRegistered 2024-12-07\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tg4skins.com\n10.1 yearsRegistered 2016-08-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.g4s.to\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2royal.com\n4.1 yearsRegistered 2022-08-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ntf2auth.com\n5.2 yearsRegistered 2021-07-27\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2hunt.com\n8.7 yearsRegistered 2018-01-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrstspcl.com\n6.1 yearsRegistered 2020-08-08\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2.bet/coinflip\n8.4 yearsRegistered 2018-05-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ntf2.bet\n8.4 yearsRegistered 2018-05-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\topenstars.gg\n131 daysRegistered 2026-05-13\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nopenstars.gg\n131 daysRegistered 2026-05-13\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tskins.com\n25.1 yearsRegistered 2001-08-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skins.com\n25.1 yearsRegistered 2001-08-08\nRDAP ↗ · skins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\twhite.market\n9.6 yearsRegistered 2017-03-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwhite.market\n9.6 yearsRegistered 2017-03-01\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tmoon.market\n7.6 yearsRegistered 2019-02-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmoon.market\n7.6 yearsRegistered 2019-02-27\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tcsfloat.com\n5.2 yearsRegistered 2021-07-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgofloat.com\n11.0 yearsRegistered 2015-09-29\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tskin.land\n4.7 yearsRegistered 2022-01-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skin.land\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\thaloskins.com\n2.8 yearsRegistered 2023-12-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhaloskins.com\n2.8 yearsRegistered 2023-12-10\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCorporate Market\n\tbuff.163.com\n29.0 yearsRegistered 1997-09-15\nRDAP ↗ · 163.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\nbuff.163.com\n29.0 yearsRegistered 1997-09-15\nRDAP ↗ · 163.com (parent)\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\tmarket.csgo.com\n26.6 yearsRegistered 2000-02-07\nRDAP ↗ · csgo.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\ndota2.net\n14.9 yearsRegistered 2011-10-29\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRegulated Market\n\tskinport.com\n8.0 yearsRegistered 2018-09-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinport.app\n6.3 yearsRegistered 2020-06-20\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMarketplace/Swap\n\tskinflow.gg\n3.8 yearsRegistered 2022-11-26\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinflow.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tskin.place\n6.0 yearsRegistered 2020-09-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skin.place\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tskinsmonkey.com\n5.7 yearsRegistered 2021-01-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinsmonkey.com\n5.7 yearsRegistered 2021-01-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCorporate Market\n\tskinbaron.de\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinbaron.com\n10.7 yearsRegistered 2015-12-22\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Market\n\trust.tm\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\ndota2.net\n14.9 yearsRegistered 2011-10-29\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tpirateswap.com\n6.0 yearsRegistered 2020-09-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nlogin.pirateswap.com\n6.0 yearsRegistered 2020-09-22\nRDAP ↗ · pirateswap.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Marketplace\n\tmannco.store\n8.6 yearsRegistered 2018-03-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmannco.store\n8.6 yearsRegistered 2018-03-02\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tskinswap.com\n9.9 yearsRegistered 2016-11-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinswap.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\texeskins.com\n2.1 yearsRegistered 2024-08-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nexeskins.com\n2.1 yearsRegistered 2024-08-14\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tbalticskins.com\n153 daysRegistered 2026-04-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nbalticskins.com\n153 daysRegistered 2026-04-21\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tcs.trade\n8.9 yearsRegistered 2017-11-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncs.trade\n8.9 yearsRegistered 2017-11-14\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\trapidskins.com\n4.5 yearsRegistered 2022-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.rapidskins.com\n4.5 yearsRegistered 2022-03-11\nRDAP ↗ · rapidskins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\ttradeit.gg\n9.1 yearsRegistered 2017-08-21\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nconnect-tradeit.com\n4.6 yearsRegistered 2022-02-23\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\t49skins.com\n3.4 yearsRegistered 2023-04-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.49skins.com\n3.4 yearsRegistered 2023-04-19\nRDAP ↗ · 49skins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tskinvault.gg\n3.4 yearsRegistered 2023-05-06\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinvault.gg\n3.4 yearsRegistered 2023-05-06\nIP2WHOIS ↗ · skinvault.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Trading\n\taim.market\n3.3 yearsRegistered 2023-05-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\naim.market\n3.3 yearsRegistered 2023-05-22\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Sell Portal\n\tskinout.gg\n5.6 yearsRegistered 2021-02-27\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skinout.gg\n5.6 yearsRegistered 2021-02-27\nIP2WHOIS ↗ · skinout.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Trading\n\tntskins.com\n230 daysRegistered 2026-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nntskins.com\n230 daysRegistered 2026-02-03\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Portal\n\tgamerpay.gg\n6.0 yearsRegistered 2020-10-02\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ngamerpay.gg\n6.0 yearsRegistered 2020-10-02\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Scrap Swap\n\tscrap.tf\n14.0 yearsRegistered 2012-09-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nscrap.tf\n14.0 yearsRegistered 2012-09-03\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Cashout\n\tmarketplace.tf\n14.0 yearsRegistered 2012-09-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmarketplace.tf\n14.0 yearsRegistered 2012-09-19\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Cashout\n\tskins.cash\n10.5 yearsRegistered 2016-03-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinscash.live\n6.8 yearsRegistered 2019-12-05\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgo.net\n14.2 yearsRegistered 2012-07-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncn2.easylot.net\n10.0 yearsRegistered 2016-09-03\nRDAP ↗ · easylot.net (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCommunity Hub\n\tcybershoke.net\n6.8 yearsRegistered 2019-11-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.cybershoke.net\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMatchmaker Hub\n\tfastcup.net\n14.6 yearsRegistered 2012-02-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.fastcup.net\n14.6 yearsRegistered 2012-02-16\nRDAP ↗ · fastcup.net (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Analytics\n\tleetify.com\n7.6 yearsRegistered 2019-03-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nleetify.com\n7.6 yearsRegistered 2019-03-01\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Analytics\n\tscope.gg\n7.8 yearsRegistered 2018-12-10\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nscope.gg\n7.8 yearsRegistered 2018-12-10\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tools\n\ttradeupspy.com\n6.5 yearsRegistered 2020-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.tradeupspy.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMarketplace\n\tcs.deals\n9.8 yearsRegistered 2016-12-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.cs.deals\n9.8 yearsRegistered 2016-12-03\nRDAP ↗ · cs.deals (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Price DB\n\tpricempire.com\n6.6 yearsRegistered 2020-01-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\npricempire.com\n6.6 yearsRegistered 2020-01-30\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Blackmarket\n\tFSB Market\n7.2 yearsRegistered 2019-07-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nFSB Market\n7.2 yearsRegistered 2019-07-27\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nReady-Account Hub\n\tz2u.com\n26.9 yearsRegistered 1999-11-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwww.z2u.com\n26.9 yearsRegistered 1999-11-10\nRDAP ↗ · z2u.com (parent)\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Gambling\n\tcsgoroll.com\n11.6 yearsRegistered 2015-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwww.csgoroll.com\nRegistry date unavailableRegistry date unavailable\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\trollbit.com\n11.9 yearsRegistered 2014-11-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrbsnin.com\n3 daysRegistered 2026-09-18\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nLicenced Casino\n\t500.casino\n5.9 yearsRegistered 2020-11-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette/Slots\n\tcsgobig.com\n11.4 yearsRegistered 2015-04-12\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcasedrop.com\n14.8 yearsRegistered 2011-12-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\tbanditcamp.com\n12.2 yearsRegistered 2014-06-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tskinbox.com\n18.8 yearsRegistered 2007-12-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\ttastydrop.com\n6.1 yearsRegistered 2020-08-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette Casino\n\tcsgopolygon.gg\n6.5 yearsRegistered 2020-03-28\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tmagicdrop.ru\n10.3 yearsRegistered 2016-05-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nDice Casino\n\tcsdice.com\n3.8 yearsRegistered 2022-11-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUpgrader Casino\n\tskinodds.com\n1.2 yearsRegistered 2025-06-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgowin.com\n12.0 yearsRegistered 2014-09-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrash Casino\n\tcsgorun.net\n7.3 yearsRegistered 2019-06-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\topenskins.com\n3.6 yearsRegistered 2023-02-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Gambling\n\trustbet.com\n7.6 yearsRegistered 2019-02-07\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgomagic.com\n9.4 yearsRegistered 2017-05-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUpgrader/Contract\n\tcsgobounty.com\n11.5 yearsRegistered 2015-03-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tezskins.com\n27.5 yearsRegistered 1999-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\trustcases.com\n7.2 yearsRegistered 2019-06-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgoreaper.com\n11.1 yearsRegistered 2015-08-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgocases.com\n12.3 yearsRegistered 2014-06-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Upgrader\n\tcsgo-skins.com\n11.2 yearsRegistered 2015-07-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgonet.com\n8.8 yearsRegistered 2017-12-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\twtfskins.com\n9.0 yearsRegistered 2017-10-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Casino\n\tflamecases.com\n10.0 yearsRegistered 2016-09-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tgamedom.com\n11.7 yearsRegistered 2015-01-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Battles\n\tskin.club\n9.0 yearsRegistered 2017-09-04\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsc-auth.net\n7.5 yearsRegistered 2019-04-02\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tdaddyskins.com\n9.9 yearsRegistered 2016-10-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Gambling\n\trustix.gg\n1.7 yearsRegistered 2025-01-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Upgrade\n\tskins.club\n4.2 yearsRegistered 2022-07-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgohouse.org\n146 daysRegistered 2026-04-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskinrave.net\n216 daysRegistered 2026-02-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tbloodycase.gg\n19 daysRegistered 2026-09-02\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nClicker/Upgrade\n\tcsgoclicker.com\n8.3 yearsRegistered 2018-05-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustbet.gg\n4.0 yearsRegistered 2022-09-30\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcs-drop.com\n262 daysRegistered 2026-01-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\thellstore.net\n11.7 yearsRegistered 2015-01-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustloot.com\n354 daysRegistered 2025-10-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgo-case.com\n10.3 yearsRegistered 2016-05-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgogem.com\n9.9 yearsRegistered 2016-10-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\trainbet.com\n8.8 yearsRegistered 2017-11-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nservices.rainbet.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustclash.com\n5.4 yearsRegistered 2021-05-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrash Casino\n\t12cs.fail\n181 daysRegistered 2026-03-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\twww.tf2easy.com\n6.3 yearsRegistered 2020-06-02\nRDAP ↗ · tf2easy.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2blaze.com\n7.6 yearsRegistered 2019-01-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tshuffle.com\n30.1 yearsRegistered 1996-07-31\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tbuff.market\n5.9 yearsRegistered 2020-10-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tavan.market\n8.3 yearsRegistered 2018-05-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Engine\n\tcs.money\n11.0 yearsRegistered 2015-09-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.dota.trade\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tuuskins.com\n2.6 yearsRegistered 2024-01-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Market\n\tyoupin898.com\n6.1 yearsRegistered 2020-08-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tc5game.com\n10.5 yearsRegistered 2016-03-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\twaxpeer.com\n7.3 yearsRegistered 2019-05-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwaxpeer.com\n7.3 yearsRegistered 2019-05-20\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBot Trading\n\tcs.money\n11.0 yearsRegistered 2015-09-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.dota.trade\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUS Marketplace\n\tdmarket.com\n30.2 yearsRegistered 1996-07-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nOfficial Market\n\tsteamcommunity.com/market\n20.3 yearsRegistered 2006-05-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNot an external login site2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Platform\n\tlootfarm.com\n11.9 yearsRegistered 2014-10-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Market\n\trustskins.com\n7.6 yearsRegistered 2019-01-31\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tkrakatoa.com\n26.4 yearsRegistered 2000-05-15\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\tshadowpay.com\n10.1 yearsRegistered 2016-08-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nChinese Powerhouse\n\tigxe.cn\n15.0 yearsRegistered 2011-09-06\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAutomated Swap\n\tswap.gg\n9.6 yearsRegistered 2017-01-29\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCash-out Portal\n\tbitskins.com\n11.2 yearsRegistered 2015-07-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Automation\n\ttf2mart.com\n1.1 yearsRegistered 2025-08-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Auctions\n\tskinbid.com\n10.2 yearsRegistered 2016-06-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Rental\n\tlootbear.com\n8.7 yearsRegistered 2018-01-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Valuation\n\tbackpack.tf\n14.4 yearsRegistered 2012-05-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Botnet\n\tstntrading.eu\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Cashout\n\tskinwallet.com\n18.0 yearsRegistered 2008-09-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nDota 2 Market\n\tdota2market.com\n12.2 yearsRegistered 2014-07-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nServer Network\n\txplay.gg\n5.3 yearsRegistered 2021-06-13\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMatchmaking Portal\n\tesportal.com\n26.8 yearsRegistered 1999-12-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nLATAM Hub\n\tgamersclub.com.br\n11.2 yearsRegistered 2015-06-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tools\n\tepidemic.gg\n4.9 yearsRegistered 2021-11-03\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tcs2stash.com\n3.5 yearsRegistered 2023-03-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tcsgoskins.gg\n6.8 yearsRegistered 2019-12-21\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tsteamanalyst.com\n12.6 yearsRegistered 2014-02-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Exchange\n\tsteamcardexchange.net\n13.3 yearsRegistered 2013-05-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tracker\n\tdotabuff.com\n14.2 yearsRegistered 2012-06-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tracker\n\ttracker.gg\n8.9 yearsRegistered 2017-10-12\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Exchange\n\tfunpay.com\n17.0 yearsRegistered 2009-09-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nGrey Market\n\tplayerauctions.com\n26.3 yearsRegistered 2000-06-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Portal\n\teldorado.gg\n8.0 yearsRegistered 2018-09-12\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Key Market\n\tg2a.com\n24.8 yearsRegistered 2001-12-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Key Market\n\tkinguin.net\n16.8 yearsRegistered 2009-12-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nVirtual Services\n\tg2g.com\n31.1 yearsRegistered 1995-08-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Broker\n\tplayerup.com\n19.3 yearsRegistered 2007-05-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfhub.net\n2.7 yearsRegistered 2023-12-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfaccounts.com\n5.3 yearsRegistered 2021-05-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Shop\n\tbuycsgorank.com\n6.2 yearsRegistered 2020-07-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tcsgosmurfkings.com\n9.3 yearsRegistered 2017-06-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfstore.co\n8.6 yearsRegistered 2018-03-03\nWHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlvlup.com\n9.9 yearsRegistered 2016-11-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlevels.com\n10.6 yearsRegistered 2016-02-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tlevelsteam.com\n79 daysRegistered 2026-07-04\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlevelu.com\n6.0 yearsRegistered 2020-09-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\teloking.com\n12.2 yearsRegistered 2014-07-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\tboosteria.org\n11.9 yearsRegistered 2014-10-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tovergear.com\n14.4 yearsRegistered 2012-04-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tblazingboost.com\n14.2 yearsRegistered 2012-06-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\tdota2boost.com\n2.9 yearsRegistered 2023-10-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tbuyboost.com\n22.4 yearsRegistered 2004-04-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\nजांच का तर्कचयनित नियम / विश्लेषण एवं टिप्पणी+\nसाक्ष्य का भार\n\nयह जांच वाणिज्यिक उपयोग पर लगाए गए प्रतिबंधों और यहां दर्ज सेवाओं के बीच के अंतर को चुनौती देती है। प्रत्येक गतिविधि को वर्गीकृत करें और इसे संविदात्मक उल्लंघन कहने से पहले किसी भी स्पष्ट अनुमति की पुष्टि करें। समुदाय बाजार शुल्क हर बाहरी व्यापार पर लागू नहीं होते।\n\nटैग किया गया रिकॉर्ड क्या है, और क्या नहीं है\n\nकिसी रिकॉर्ड को तब टैग किया जाता है जब दस्तावेज़ में दिनांकित कोई अवलोकन होता है जो प्लेटफ़ॉर्म को स्पष्ट रूप से उस खंड के दायरे में लाता है। टैग कोई निर्णयित उल्लंघन नहीं है, और यहाँ सूचीबद्ध किसी भी प्लेटफ़ॉर्म के लिए रिकॉर्ड पर कोई स्पष्ट Valve अनुमति प्रस्तुत नहीं की गई है। जहाँ कोई प्लेटफ़ॉर्म प्राधिकृत है, उसे प्रकाशित करने से प्रविष्टि का समाधान हो जाता है।\n\nस्रोत और कार्यप्रणालीअनुमान, परिभाषाएँ और दायरा+\n\nउपरोक्त संख्याएँ चयनित नियम को संदर्भित करती हैं। रिकॉर्ड प्रकार प्रत्येक प्लेटफ़ॉर्म को एक बार समूहित करते हैं; पूर्ण टैग प्लेटफ़ॉर्म विवरण में दिखाई देते हैं। खोज और फ़िल्टर उस नियम के भीतर लागू होते हैं। पंजीकरण तिथियाँ सहेजे गए RDAP / WHOIS स्नैपशॉट से आती हैं। सबडोमेन पैरेंट डोमेन की निर्माण तिथि का उपयोग करते हैं। केवल आयु निरंतर संचालन या प्रमाणीकरण मार्ग स्थापित नहीं करती। वर्तमान auth होस्टनाम सहेजी गई OpenID अनुरोधों से आते हैं, एक UTC टाइमस्टैम्प के साथ; अनसुलझी जाँचें पुराने लेबल का पुन: उपयोग नहीं करतीं। पर्यवेक्षक Steam लॉगिन से पहले रुक जाता है और Steam लिंक फ़िल्टर स्थिति का परीक्षण नहीं करता। मार्ग अवलोकन डाउनलोड करें ↗ रजिस्ट्री परिणाम डाउनलोड करें ↗\n\nस्रोत संग्रह का अन्वेषण करें ↗\nपरिशिष्ट G — एक टेम्पलेट अस्वीकृति से मूल रिकॉर्ड तक\nDSAR प्लेबुक: साक्ष्य का अनुरोध करें\n\nAPIसे संबंधित व्यक्तिगत डेटा का अनुरोध करने के लिए अनुच्छेद15GDPR का उपयोग करें। एक संरक्षित रिकॉर्ड यह परीक्षण कर सकता है कि किसी कार्रवाई की शुरुआत किसने की और प्लेटफ़ॉर्म किस आधार पर निर्भर था।\n\n01\nअपनी टाइमलाइन को संरक्षित करें।\n\nखाते के नोटिस, टिकट, ट्रेड आईडी और तिथियों को UTC में सहेजें। खाते को सुरक्षित करें और गेम व लेनदेन के लिए लागू पुनर्प्राप्ति विकल्पों की समीक्षा करें।\n\nSteam व्यापार संरक्षण जानकारी ↗\n02\nअपने संग्रहित डेटा का अनुरोध करें।\n\nटाइमस्टैम्प, स्रोत आईपी, कुंजी जीवनचक्र घटनाएँ, सुरक्षा पुष्टि और खाते से संबंधित पुनर्प्राप्ति क्रियाएँ माँगें। जहाँ ये डेटा आपसे संबंधित हों, वहाँ समर्थन-पहुँच घटनाएँ और प्राप्तकर्ता भी शामिल करें।\n\n03\nडिलीवरी का रिकॉर्ड रखें।\n\nValve के गोपनीयता संपर्क मार्ग का उपयोग करें। सामान्य प्रतिक्रिया अवधि एक माह है; यदि पहले माह के भीतर दो अतिरिक्त महीनों तक का विस्तार आवश्यक हो, तो उसका कारण स्पष्ट करना होगा।\n\nValve गोपनीयता संपर्क मार्ग ↗ संचित 2026-09-21 ↗\n04\nप्रतिक्रिया की तुलना करें।\n\nलॉग्स को अपनी समयरेखा के साथ मिलाएँ। छूटी हुई प्रविष्टियों के कारण पूछें, फिर यदि आवश्यक हो तो पर्यवेक्षी-प्राधिकरण शिकायत मार्ग का उपयोग करें। प्रतिक्रिया को बिल्कुल वैसे ही संरक्षित करें जैसे प्राप्त हुई थी।\n\nदायरा / लेख 15\n\nएक्सेस में लॉग्स में मौजूद डेटा सहित व्यक्तिगत डेटा शामिल है। यह हर आंतरिक दस्तावेज़, पुनर्निर्मित रिकॉर्ड या दूसरों के बारे में बिना संपादित डेटा की गारंटी नहीं देता। एक सुबोध प्रति और किसी भी प्रतिबंध के आधार के लिए अनुरोध करें।\n\nEDPB पहुँच दिशानिर्देश, §§ 2, 4–6 ↗ · GDPR लेख12, 15, 77 ↗ संग्रहीत 2026-09-20 ↗\n\nडेटा विषय पहुँच अनुरोधGDPR / लेख 15\nखाता सुरक्षा और पहुँच रिकॉर्ड\n\nसबमिट करने से पहले कोष्ठक वाले फ़ील्ड्स को बदलें।\n\nTo: Valve Privacy Team\nSubject: Article 15 GDPR request — account security records\n\nAccount / SteamID: [YOUR ACCOUNT IDENTIFIER]\nRelevant period (UTC): [START] to [END]\nRelated support tickets: [TICKET REFERENCES]\n\nI request a copy of the personal data concerning me that you retain for this period, including:\n\n1. API-key registration, confirmation, use and revocation events, with available timestamps, source IP addresses, registered domains, device or user-agent information and non-secret key identifiers.\n\n2. Recorded account-recovery actions, password/email/phone changes, Steam Guard removals or resets, confirmation events and the account-related evidence relied on to authorize those actions.\n\n3. Personal data in support-access and administrative-action logs concerning my account, including available dates, purposes, actions and the support entity involved, subject to applicable rights of others.\n\n4. Account-related records used to determine any sanction, and available records of my complaints, reviews and responses.\n\nPlease also provide the applicable processing purposes, categories, recipients, retention periods or criteria, and available information about sources where data were not obtained from me.\n\nWhere processing relies on my consent, please provide the retained record of the consent relied upon and the wording presented at that time.\n\nPlease provide an intelligible electronic copy with time zones and field definitions. Please do not include active credentials or secret tokens. If any requested data are not held, please say so. For any withheld data, please identify the scope and legal basis of the restriction and provide the remainder.\n\nPlease acknowledge receipt and respond within the applicable Article 12 period, explaining any necessary extension. I also ask you to preserve relevant existing records while this request is handled.\n\nName: [YOUR NAME]\nDate: [DATE]\nएक डेटा-सेंटर आईपी क्या स्थापित कर सकता है\nअंतर जांच के लिए साक्ष्य है।\n\nAPI-key अनुरोध, जो डेटा-सेंटर नेटवर्क से उत्पन्न होता है, जैसा कि इस जांच में उठाए गए होस्टिंग-प्रदाता उदाहरण में है, लॉगिन रिकॉर्ड, पुष्टि और उपयोगकर्ता की टाइमलाइन की तुलना में प्रासंगिक हो सकता है। केवल एक आईपी पता स्वयं अपराधी की पहचान नहीं करता और न ही स्वचालित रूप से सभी सुरक्षा उपायों को ध्वस्त कर देता है। यह प्रमाण कि एक शत्रुतापूर्ण पक्ष ने दर्ज की गई सहमति प्रदान की थी, उस सहमति पर निर्भरता को चुनौती दे सकता है; अन्य कानूनी आधारों और देयता संबंधी मुद्दों का अलग से विश्लेषण आवश्यक है।\n\nसंरक्षित प्रतिबंध औरGDPR की शिकायत देखें →\nपरिशिष्ट H — Wayback Machine अभिलेखागार विश्लेषण · प्रकाशित समर्थन सांख्यिकी\nसमर्थन मात्रा। प्रकाशित प्रतिक्रिया समय।\nप्रसंग और स्रोत सीमाएँ\n\nValve दैनिक समर्थन सांख्यिकी प्रकाशित करता है store.steampowered.com/stats/supportWayback Machine आर्काइव्स इस पृष्ठ के 2018 से 2026. तक के ऐतिहासिक स्नैपशॉट्स को संरक्षित करते हैं। इन आंकड़ों से संकेतित वॉल्यूम-से-हेडकाउंट अनुपात प्रकाशित प्रतिक्रिया समयों पर प्रति टिकट मानवीय समीक्षा के साथ असंगत है।\n\nValve के संग्रहीत समर्थन आंकड़ों की विभिन्न सहेजी गई स्नैपशॉट्स में तुलना करें। यह पद्धति बताती है कि ये आंकड़े क्या माप सकते हैं और क्या नहीं।\n\nप्रकाशित प्रतिक्रिया समय के विरुद्ध वॉल्यूम (2018 → 2026)\nएक ही सपोर्ट डेस्क पर दो कतारें, 21 में संग्रहीत कैप्चर को क्रॉस-रीड करें।\n\nValve लाइव सपोर्ट आंकड़े प्रकाशित करता है store.steampowered.com/stats/supportनीचे प्रत्येक बिंदु उस पृष्ठ पर उसी दिन प्रिंट किया गया निचला सीमा Valve है, जिस दिन इंटरनेट आर्काइव ने उसे कैप्चर किया था — यह हमारा कोई अनुमान नहीं है। दोनों श्रृंखलाएँ एक ही माप और एक ही इकाई में हैं, इसलिए वे एक ही अक्ष पर हैं और सीधे एक-दूसरे के सापेक्ष पढ़ी जा सकती हैं।\n\nरिफंड अनुरोध — पैसा Valve रख रहा हैखाता सुरक्षा और पुनर्प्राप्ति — वह खाता जो आप खो चुके हैं\n0 h\n2 h\n4 h\n6 h\n8 h\n10 h\nno captures · 38 months\n2019\n2020\n2021\n2022\n2023\n2024\n2025\n2026\n8 h 44 m\naccount recovery\n52 m\nrefunds\n15 m — one capture only\n49–55 मिनफरवरी 2018 से अगस्त 2026. तक हर कैप्चर में रिफंड की निचली सीमा। आठ साल और आधे वर्ष में यह छह मिनट से भी कम समय में बदलता है, जबकि दैनिक रिफंड वॉल्यूम नौ गुना तक बदलता है।\n2.4 h → 8.7 hखाता-रिकवरी का निचला सीमा दिसंबर 2022 तक हर कैप्चर में लगभग 2.4 घंटे के पास रहती है, सिवाय एक के। तीन 2026 कैप्चर में Valve प्रकाशित करता है: 10.9 घंटे, 5.8 घंटे और 8.7 घंटे।\n×2.8 → ×13Valve के अपने प्रकाशित आंकड़ों के अनुसार, पुनर्प्राप्ति रिफंड की तुलना में कितनी धीमी है। पांच साल तक स्थिर रहने के बाद यह अंतर बढ़ जाता है — वह कतार जो धीमी हो जाती है, वह वही है जिसमें पैसे का नुकसान उपयोगकर्ता को होता है, न कि Valve को।\n\nस्रोत: 21 Wayback Machine कैप्चर store.steampowered.com/सांख्यिकी/समर्थन, 2018-02-03 से 2026-08-10 तक; निष्कर्षण में VALVE_EVIDENCE_PACK/databases/steam_support_stats_history.json. आंकड़ों के साथ सीमाएँ पढ़ें: चार्ट दर्शाता है निम्न, नीचा, नीचे Valve प्रिंट्स की सीमा का एक बाउंड। प्रकाशित ऊपरी सीमा दोनों ही मामलों में खराब है — रिफंड्स 1.5 घंटे से 1.5 दिन तक, रिकवरी 7.0 घंटे से 3.6 दिन तक। दो कैप्चर एक ही Valve पृष्ठ के स्थानीय संस्करण में संग्रहीत किए गए थे — चेक में 2018-11-03, फ्रेंच में 2020-03-25 — और तालिका में (cs) और (fr) से चिह्नित हैं; उनके आंकड़े यहां इकाई शब्दों के अनुवाद और प्रकाशन के अनुसार संख्याओं के साथ दिखाए गए हैं, और शब्दशः स्रोत स्ट्रिंग्स निष्कर्षण फ़ाइल में रखी गई हैं। प्रत्येक कैप्चर ने दोनों कतारों के लिए प्रतिक्रिया समय प्रकाशित किया, और किसी भी रेखा पर कोई बिंदु अंतर-पोलिनेटेड नहीं है। 2020-10-21 के एकल 15-मिनट रिकवरी आंकड़े को चार्ट पर चिह्नित किया गया है और शामिल रखा गया है: यह केवल एक कैप्चर में दिखाई देता है और कोई अन्य कैप्चर इसके एक क्रम-परिमाण के भीतर नहीं है। 2022-12-08 और 2026-02-01 के बीच कोई कैप्चर मौजूद नहीं है; रिकॉर्ड में उस 38-महीने के अंतराल को छायांकित किया गया है, और उस पर कुछ भी नहीं दिखाया गया है। ये आंकड़े प्रकाशित प्रतिक्रिया समय का वर्णन करते हैं। वे यह नहीं दिखाते कि टिकट के अंदर क्या होता है, और Valve ने उन्हें पढ़ने के लिए कोई हेडकाउंट प्रकाशित नहीं किया है।\n\nहर कैप्चर को एक तालिका के रूप में खोलें\nप्रत्येक संग्रहीत कैप्चर, जैसा प्रकाशित\nकैप्चर\tरिफंड / दिन\tरिफंड प्रतिक्रिया\tरिकवरी / दिन\tरिकवरी प्रतिक्रिया\n2018-02-03\t98,788\t50.12 minutes to 1.52 hours\t25,662\t2.51 hours to 1.80 days\n2018-05-07\t60,494\t53.83 minutes to 1.47 days\t24,226\t2.45 hours to 2.22 days\n2018-08-02\t69,084\t50.27 minutes to 1.59 hours\t28,953\t2.44 hours to 22.17 hours\n2018-11-03 (cs)\t63,410\t49.28 minutes to 1.54 hours\t33,910\t2.42 hours to 1.31 days\n2019-02-01\t76,305\t50.13 minutes to 1.52 hours\t35,164\t2.44 hours to 2.04 days\n2019-05-18\t78,951\t51.03 minutes to 3.12 hours\t27,514\t2.46 hours to 20.39 hours\n2019-09-07\t78,941\t50.65 minutes to 1.66 hours\t28,812\t2.42 hours to 13.59 hours\n2019-12-13\t69,589\t50.77 minutes to 1.55 hours\t25,322\t2.45 hours to 1.13 days\n2020-03-25 (fr)\t139,278\t49.45 minutes to 1.53 hours\t32,302\t2.48 hours to 3.62 days\n2020-06-26\t278,504\t48.98 minutes to 2.29 hours\t20,343\t2.39 hours to 6.99 hours\n2020-10-21\t107,633\t50.80 minutes to 1.54 hours\t20,688\t15.33 minutes to 8.62 hours\n2021-03-20\t158,956\t50.80 minutes to 1.64 hours\t25,760\t2.34 hours to 11.62 hours\n2021-06-26\t547,907\t51.93 minutes to 6.73 hours\t29,728\t2.40 hours to 15.63 hours\n2021-10-10\t170,103\t51.88 minutes to 3.25 hours\t23,989\t2.39 hours to 13.05 hours\n2022-01-31\t354,386\t53.65 minutes to 8.09 hours\t24,391\t2.42 hours to 15.29 hours\n2022-05-09\t172,555\t51.83 minutes to 1.65 hours\t23,289\t2.41 hours to 16.90 hours\n2022-09-05\t153,453\t53.67 minutes to 4.15 hours\t23,594\t2.45 hours to 1.22 days\n2022-12-08\t181,075\t54.83 minutes to 6.67 hours\t27,111\t2.46 hours to 18.89 hours\n2026-02-01\t317,762\t50.30 minutes to 1.52 hours\t47,197\t10.91 hours to 21.30 hours\n2026-05-09\t246,776\t50.12 minutes to 1.52 hours\t35,264\t5.81 hours to 15.60 hours\n2026-08-10\t373,244\t52.05 minutes to 2.07 hours\t45,319\t8.73 hours to 16.52 hours\nमुख्य अवलोकन:\nपार 21 वेबैक कैप्चर 2018-02-03 से 2026-08-10, तक दैनिक रिफंड सबमिशन की सीमा थी 60,494 (मई 2018) से 547,907 (जून2021) — एक 9.1× फैलाव2026 का आंकड़ा 373,244 है (+278% बनाम फरवरी के 2018 कैप्चर)।\nउसी नौ वर्षों के दौरान, रिफंड प्रतिक्रिया समय के लिए प्रकाशित निचला सीमा कभी भी एक से ऊपर नहीं गई। 49–55 एक मिनट बैंड: छह मिनट से भी कम समय में एक कुल गति, जबकि इसके पीछे का कार्यभार नौ गुना बढ़ गया।\nयदि कोई व्यक्ति प्रत्येक टिकट को केवल 5 सेकंड में पढ़े, तो वर्तमान में प्रतिदिन 373,244 टिकटों को संसाधित करने में लगेगा 22 24/7 पर काम करने वाले एजेंट सिर्फ उन्हें खोलने और बंद करने के लिए; चरम पर (547,907, जून 2021) यह 32. तक बढ़ जाता है।\nयदि प्रकाशित प्रतिक्रिया समय प्रति टिकट हैंडलिंग समय (~52मिनट/टिकट) को दर्शाता है, तो निहित समवर्ती स्टाफिंग लगभग इस प्रकार होगी 13,500 एजेंट्स वर्तमान वॉल्यूम पर और चरम पर लगभग20,000। Valve के समर्थन हेडकाउंट के लिए कोई स्रोत आंकड़ा नहीं मिला है; यहाँ कोई अनुमान नहीं लगाया गया है।\nनिम्नलिखित: वॉल्यूम-टू-हेडकाउंट अनुपात प्रकाशित प्रतिक्रिया समयों पर प्रति-टिकट मानवीय समीक्षा के साथ असंगत है। ये आंकड़े मुख्यतः स्वचालित प्रथम समीक्षा के अनुरूप हैं; कितनी मात्रा में समीक्षा मानवीय रूप से की जाती है, यह प्रकाशित नहीं किया गया है।\nGDPR अनुपालन के लिए यह क्यों महत्वपूर्ण है\n\nGDPR अनुच्छेद22 केवल स्वचालित व्यक्तिगत निर्णय लेने पर रोक लगाता है, जो अनुरोध पर मानवीय समीक्षा का अधिकार दिए बिना महत्वपूर्ण कानूनी प्रभाव पैदा करते हैं। यदि Steam समर्थन निर्णय (टिकट बंद करना, खाते पर कार्रवाई, डेटा अनुरोधों से इनकार) पूरी तरह से स्वचालित स्क्रिप्ट द्वारा लिए जाते हैं, तो प्रत्येक ऐसा निर्णय जो उपयोगकर्ता को \"महत्वपूर्ण रूप से प्रभावित करता है\" अनुच्छेद 22. का उल्लंघन कर सकता है।\n\nटिकट HT-2YBP-F7JP-D4VB (धारा18) को तीन दिनों के बाद एक टेम्पलेट रेफरल के साथ बंद कर दिया गया और उद्धृत कानूनी आधार के साथ कोई संलग्नता नहीं दिखाई गई। टिकट से यह निर्धारित नहीं किया जा सकता कि किसी व्यक्ति ने इसकी समीक्षा की या नहीं; यह एक ऐसा प्रश्न है जिसे पर्यवेक्षी प्राधिकरण अनुच्छेद 22 और अनुच्छेद 15(1)(h) के तहत Valve से पूछ सकता है।\n\nस्रोत: Wayback Machine के store.steampowered.com/stats/support (2018-02-03, 2021-06-26, 2026-08-10) के स्नैपशॉट — डेटा VALVE_EVIDENCE_PACK/databases/steam_support_stats_history.json में निकाला गया (21 स्नैपशॉट, 2018–2026). नोट: \"~52 मिनट\" प्रतिक्रिया समय रिफंड-श्रेणी का निचला सीमा है; खाता सुरक्षा प्रतिक्रिया समान स्नैपशॉट्स में 2.4–16.5 घंटे थी। 2021-06-26 सभी समय का उच्चतम स्तर (547,907 रिफंड अनुरोध) है, न कि कोई एकरूप मध्यबिंदु — वॉल्यूम ~6गुना बढ़ गया 2020–2021 में, फिर आंशिक रूप से गिरकर 2026. में 373K तक पुनः उबर गया।\nपरिशिष्ट I — डेटासेट का दायरा · पुनरुत्पादित किए जा सकने वाले गणनाएँ\nरिकॉर्ड्स की गिनती करें। दायरा जांचें।\nप्रसंग और स्रोत सीमाएँ\n\nरिकॉर्ड्स की गिनती करें, फिर दावों का परीक्षण करें: नीचे दी गई प्रत्येक संख्या प्रकाशित फ़ाइलों से पुनः प्राप्त की जा सकती है।\n\nनिहित डेटासेटों का निरीक्षण करें, गणनाओं को पुनः उत्पन्न करें, और स्रोत पंक्तियों को अद्वितीय घटनाओं से अलग करें।\n\nमास्टर CSV में शामिल हैं 40,448 कतारेंइनमें से, 36,516 Discord-AntiScam फ़िशिंग फ़ीड से आते हैं। शेष 3,932 पंक्तियाँ रिपोर्ट किए गए सामुदायिक विषयों और सुरक्षा रिपोर्टों का एक व्यापक अनुक्रमणिका प्रदान करते हुए, GitHub, समीक्षाएं, खोज परिणाम, फोरम सामग्री और अन्य स्रोतों में फैली हुई हैं।\n\nउस CSV में, 1,690 पंक्तियाँ \"Unpatched Security Exploit\" संग्रह लेबल के अंतर्गत वर्गीकृत हैं, जो ऐतिहासिक उपयोगकर्ता समस्याओं और भेद्यता प्रकटीकरणों का प्रतिनिधित्व करती हैं। इन रिपोर्टों का पता लगाने में प्रत्येक थ्रेड की विशिष्ट बिल्ड समयरेखा और सार्वजनिक पैच इतिहास की समीक्षा शामिल है।\n\n16,319-रिकॉर्ड सर्चेबल आर्काइव एक अलग, क्यूरेट किया गया बिल्ड है, जिसका अपना मैनिफेस्ट है, और जिसे विशिष्ट उपयोगकर्ता दावों और घटना रिपोर्टों की सटीक स्थानीय खोज के लिए डिज़ाइन किया गया है।\n\nTo build a reliable audit trail, every user-reported record must be verified against documented build timelines and historical patch logs.\n\nअलग भाग II संग्रह रिकॉर्ड 231,829 अनूठी लिस्टिंग आईडी, जिसमें स्वचालित पंजीकरण श्रेणी में 33,509 और unverified transfers के रूप में चिह्नित 198,320 शामिल हैं। इनपुट फ़ाइल का SHA-256 संरक्षित माप से मेल खाता है। ये गणनाएँ अंतिम लेनदेन मूल्यों या सत्यापित चोरी के कुल योग के बजाय लिस्टिंग प्रयासों और देखे गए ट्रांसफर का वर्णन करती हैं, जो सटीक आर्थिक प्रभाव को मापने के लिए प्राथमिक प्लेटफ़ॉर्म रिकॉर्ड्स की आवश्यकता को उजागर करती हैं। माप और हैश सूचीबद्ध करें ↗\n\nमास्टर सीएसवी ↗ · खोजने योग्य अभिलेखागार मैनिफेस्ट ↗ · स्रोत रिकॉर्ड्स का निरीक्षण करें ↗\n\nपरिशिष्ट J — इस जांच के बारे में\nValve कोई प्रवर्तन रिकॉर्ड प्रकाशित नहीं करता। हमने एक बनाया।\n\nस्वतंत्र। गैर-व्यावसायिक। केवल सार्वजनिक डेटा से निर्मित। नियामकों को प्रस्तुत।\n\n88.97%स्वचालित बेड़े को अछूता छोड़ा गया — किसी भी प्रकार का प्रतिबंध नहीं\n67.77%51,732: मुकदमेबाजी के बाद घोटालेबाज़ बरी\n$26.8M+गैर-लिमिटेड फ्लीट द्वारा स्टोर खर्च पर न्यूनतम सीमा\n3.6%Valve के लिंक फ़िल्टर द्वारा अवरुद्ध जुआ डोमेन\n8 वर्षदस्तावेजीकृत सुरक्षा घटनाओं की\n\nयह क्या है। Valve कॉर्पोरेशन के Steam प्लेटफ़ॉर्म पर एक फोरेंसिक दस्तावेज़ — इसके प्रवर्तन रिकॉर्ड, कार्ड-फार्मिंग अर्थव्यवस्था, कानूनी ढाँचा, और प्रमाणीकरण अवसंरचना, जिसका उपयोग जुआ संचालक Steam के अपने OpenID रिले के माध्यम से करते हैं। प्रत्येक आंकड़ा दो स्रोतों से पुनः प्राप्त किया जा सकता है: Valve का अपना सार्वजनिक API और इस जांच के साथ प्रकाशित डेटासेट।\n\nयह किसके लिए है। Valve GDPR — नीदरलैंड के लिए पर्यवेक्षी प्राधिकरण, FinCEN, SEC, DSA डिजिटल सेवा समन्वयक, UOKiK, और कोई भी कानून प्रवर्तन एजेंसी जो से जुड़े वित्तीय प्रवाहों की जांच कर रही है, पर अधिकार क्षेत्र रखने वाले नियामक। पत्रकारों, शोधकर्ताओं और उन सभी उपयोगकर्ताओं के लिए भी जिन्होंने स्थायी खाते पर प्रतिबंध, अस्वीकृत रिफंड या चोरी हुई इन्वेंटरी का सामना किया और जिन्हें बताया गया कि कोई अपील नहीं है। Steam\n\nएकमात्र मांग। Valve यह डेटा पूर्ण विश्वसनीयता के साथ रखता है — कारण संलग्न, पूर्ण आईडी स्पेस, वास्तविक समय में। यह इस दस्तावेज़ में मौजूद हर क्वेरी को सेकंडों में चला सकता है और उसने इसका कोई भी हिस्सा प्रकाशित न करने का निर्णय लिया है। किसी भी सक्षम प्राधिकारी के लिए प्रश्न सरल है: क्यों नहीं?\n\nलेखक जो दावा नहीं करते। इस कार्य के दौरान किसी भी तृतीय-पक्ष प्लेटफ़ॉर्म पर Steam में कोई लॉगिन पूरा नहीं किया गया। एक प्रदान किया गया OpenID URL अनुरोध पैरामीटर स्थापित करता है, पूरा लॉगिन नहीं। एक अलग पंजीकरण योग्य डोमेन अपने आप में छलावा का प्रमाण नहीं है। पंजीकरण की तिथियाँ उस समय की न्यूनतम सीमाएँ हैं जब कोई होस्ट पहली बार OpenID अनुरोध में प्रकट हो सकता था; वे निरंतर उपयोग को स्थापित नहीं करतीं। लेखक यह दावा नहीं करते कि Valve को क्या पता था या उनका इरादा क्या था: Valve के बारे में प्रत्येक कथन किसी दिनांकित सार्वजनिक दस्तावेज़ या दिनांकित अवलोकन से जुड़ा है। जहाँ किसी दावे को किसी स्रोत दस्तावेज़ के आधार पर प्रस्तुत नहीं किया जा सका, उसे हटा दिया गया है।\n\nहम कौन हैं\n\nPhishDestroy — स्वतंत्र जांचकर्ता।Valve कॉर्पोरेशन या यहां नामित किसी भी प्लेटफ़ॉर्म से कोई संबद्धता नहीं। एक Steam खाता केवल धारा 18. में GDPR अनुरोध को दस्तावेज़ित करने के लिए उपयोग किया गया था।\n\nकानूनी अस्वीकरण\n\nगैर-व्यावसायिक, विकेंद्रीकृत सार्वजनिक-हित जांच। सभी डेटा \"जैसा है\" प्रदान किया गया है, बिना किसी वारंटी के। यह प्रकाशन कोई न्यायिक निष्कर्ष नहीं है।\n\nसार्वजनिक डोमेन\nलाइसेंसिंग\n\nसभी अधिकार मानवता को समर्पित। प्रतिलिपि बनाना, अनुकूलित करना, प्रकाशित करना — श्रेय देना आवश्यक नहीं। OFAC-क्षेत्र पहुँच: निषिद्ध। पूर्ण लाइसेंस और अस्वीकरण →",
        "headings": [
          {
            "level": 2,
            "id": "briefing-heading",
            "text": "नियम। रिकॉर्ड। अनुत्तरित प्रश्न।"
          },
          {
            "level": 2,
            "id": null,
            "text": "वाशिंगटन राज्य जुआ आयोग को खुला पत्र"
          },
          {
            "level": 3,
            "id": "wsgc-public-address-title",
            "text": "दस दिन दस साल हो गए।रिकॉर्ड को फिर से खोलें।"
          },
          {
            "level": 2,
            "id": null,
            "text": "साइट अवरुद्ध है। लॉगिन मार्ग नहीं।"
          },
          {
            "level": 3,
            "id": null,
            "text": "चित्र 3.1 — दो मार्ग, खींचे गए।"
          },
          {
            "level": 3,
            "id": null,
            "text": "बड़ी तस्वीर का जाल: लिंक फ़िल्टर अनुपालन दिखावा है, सुरक्षा कवच नहीं।"
          },
          {
            "level": 3,
            "id": null,
            "text": "मुख्य डोमेन को ब्लॉक करने और auth होस्ट को अनब्लॉक करने से लॉगिन मार्ग खुला रहता है — और यह वर्षों तक खुला रहता है।"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam पृष्ठभूमि: ईएलएसडीए क्या है और यह यहाँ क्यों महत्वपूर्ण है"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve ने क्या किया: डोमेन ब्लॉक"
          },
          {
            "level": 3,
            "id": null,
            "text": "प्रॉक्सी डोमेन क्या है"
          },
          {
            "level": 3,
            "id": null,
            "text": "महत्वपूर्ण बिंदु: प्रत्येक अनुरोध में ऑथ होस्ट को Steam पर भेजा जाता है।"
          },
          {
            "level": 3,
            "id": null,
            "text": "यह क्या साबित करता है"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam के अंदर, Valve की सूची ही एकमात्र सूची है।"
          },
          {
            "level": 3,
            "id": null,
            "text": "लिंक फ़िल्टर सुरक्षा बाईपास"
          },
          {
            "level": 3,
            "id": null,
            "text": "बिग पिक्चर वेब ब्राउज़र लॉगिन कुकीज़ लीक करता है और संवेदनशील जानकारी का खुलासा करता है (जिससे खाते पर कब्ज़ा हो सकता है)"
          },
          {
            "level": 3,
            "id": null,
            "text": "एंटीवायरस इंस्टॉल किए गए माइनर के लिए इसका क्या मतलब है"
          },
          {
            "level": 3,
            "id": null,
            "text": "डोमेन की आयु।निरीक्षण की तिथि।"
          },
          {
            "level": 2,
            "id": null,
            "text": "एक एंडपॉइंट बंद हो गया। सार्वजनिक ट्रेसिंग ने एक कुंजी खो दी।"
          },
          {
            "level": 3,
            "id": null,
            "text": "ब्लैकआउट-पूर्व युग"
          },
          {
            "level": 3,
            "id": null,
            "text": "बदलाव के बाद"
          },
          {
            "level": 2,
            "id": null,
            "text": "एक सत्र। उपयोगकर्ता को जितना दिखता है उससे अधिक पहुँच।"
          },
          {
            "level": 3,
            "id": null,
            "text": "1. अपर्याप्त स्टेप-अप प्रमाणीकरण"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. न्यूनतम विशेषाधिकार के सिद्धांत का अभाव"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. टूटा हुआ सत्र प्रबंधन"
          },
          {
            "level": 3,
            "id": null,
            "text": "4. प्रमाणन होस्ट्स को डोमेन-स्तर पर अवरुद्ध करना तकनीकी रूप से संभव था।"
          },
          {
            "level": 3,
            "id": "integration-paradox-title",
            "text": "Valve यह हर दिन इन नियमों के खिलाफ बनता है। यहाँ यह इनके अनुसार नहीं बना।"
          },
          {
            "level": 4,
            "id": null,
            "text": "GitHub Valve फाइन-ग्रेन्ड स्कोप्स बनाम ई-लर्निंग वेब Steam API"
          },
          {
            "level": 2,
            "id": null,
            "text": "इंटरैक्टिव एक्सप्लॉइट और हाईजैक सिमुलेटर"
          },
          {
            "level": 2,
            "id": null,
            "text": "क्रम के पीछे के एंडपॉइंट्स।"
          },
          {
            "level": 2,
            "id": null,
            "text": "एक चेक किया हुआ बॉक्स। किसकी कार्रवाई?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve ने आखिरकार \"ट्रेड सब्स्टिट्यूशन\" को कैसे निष्प्रभावी किया — और 7 को इसके लिए वर्षों तक कामचलाऊ समाधान क्यों अपनाने पड़े"
          },
          {
            "level": 4,
            "id": null,
            "text": "अवतार और नाम कूलडाउन (फरवरी 2024)"
          },
          {
            "level": 4,
            "id": null,
            "text": "7-डे सीएस2 ट्रेड रिवर्सल (जुलाई 2025)"
          },
          {
            "level": 4,
            "id": null,
            "text": "API के लिए अनिवार्य मोबाइल पुश (दिसंबर 2023)"
          },
          {
            "level": 4,
            "id": null,
            "text": "खाते की आयु और नाम बैनर (2022–2024)"
          },
          {
            "level": 2,
            "id": null,
            "text": "उनकी नियमावली। रिकॉर्डेड प्लेटफ़ॉर्म।"
          },
          {
            "level": 3,
            "id": "enforcement-focus-title",
            "text": "एक नियमपुस्तिका। असमान प्रवर्तन।"
          },
          {
            "level": 4,
            "id": null,
            "text": "स्वचालन"
          },
          {
            "level": 4,
            "id": null,
            "text": "व्यावसायिक उपयोग"
          },
          {
            "level": 4,
            "id": null,
            "text": "वीपीएन और स्थान छुपाना"
          },
          {
            "level": 4,
            "id": null,
            "text": "लिंक अस्पष्टीकरण"
          },
          {
            "level": 4,
            "id": null,
            "text": "जब सहायता विभाग मामला बंद कर देता है, तो उस निर्णय की समीक्षा कौन करता है?"
          },
          {
            "level": 2,
            "id": null,
            "text": "एक स्वचालन API। स्वचालन के खिलाफ एक नियम।"
          },
          {
            "level": 3,
            "id": null,
            "text": "\"गेम डेवलपर\" भ्रम"
          },
          {
            "level": 4,
            "id": null,
            "text": "स्वचालन का विरोधाभास"
          },
          {
            "level": 4,
            "id": null,
            "text": "व्यापार प्रवाह में सर्वर-साइड स्थिति"
          },
          {
            "level": 2,
            "id": null,
            "text": "दस दिनों की मांग। दस सालों का हिसाब।"
          },
          {
            "level": 3,
            "id": "letter-company",
            "text": "वॉल्व कॉर्पोरेशन"
          },
          {
            "level": 3,
            "id": null,
            "text": "दस दिन।फिर क्या?"
          },
          {
            "level": 3,
            "id": null,
            "text": "घोषित रिटर्न होस्ट का अनुसरण करें।"
          },
          {
            "level": 3,
            "id": "washington-record-heading",
            "text": "दो समयसीमाएँ। एक अनुत्तरित प्रवर्तन मानक।"
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve जुआ साइटों को 10 दिन"
          },
          {
            "level": 4,
            "id": null,
            "text": "वाशिंगटन दबाव डालता हValve"
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve आरोप खारिज करता है"
          },
          {
            "level": 4,
            "id": null,
            "text": "सितंबर में देखे गए मार्ग2026"
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve ने जवाब देने के अठारह महीने बाद भी नियामक ने इसे इरादा ही कहा।"
          },
          {
            "level": 3,
            "id": null,
            "text": "10-दिवस सूचना दशक: 23 नामित स्थलों का फोरेंसिक उत्तरजीविता ऑडिट"
          },
          {
            "level": 4,
            "id": null,
            "text": "10-दिवस चेतावनियों से लेकर अपतटीय समूहों तक: बहु-अरब-डॉलर का कारोबार"
          },
          {
            "level": 2,
            "id": null,
            "text": "होस्टनेम पहले से ही अनुरोध में है।"
          },
          {
            "level": 3,
            "id": null,
            "text": "दस्तावेजीकृत और रिपोर्ट किए गए पूर्वनिर्णय"
          },
          {
            "level": 3,
            "id": null,
            "text": "पंजीकरण की तारीख क्या दिखाती है और क्या नहीं दिखाती"
          },
          {
            "level": 3,
            "id": null,
            "text": "तुलनात्मक ऑडिट: API अनुपालन मानक"
          },
          {
            "level": 2,
            "id": "market-thesis-heading",
            "text": "ऑफ़-Steam मूल्य अंतर"
          },
          {
            "level": 2,
            "id": null,
            "text": "मूल्य अंतर मापनीय है।"
          },
          {
            "level": 3,
            "id": null,
            "text": "डॉलर की राशि क्या दर्शाती है"
          },
          {
            "level": 3,
            "id": null,
            "text": "कई स्थल Steam से अधिक डॉलर मूल्य सूचीबद्ध करते हैं।"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam अभी भी ऑफ़र्स की संख्या में आगे है।"
          },
          {
            "level": 3,
            "id": null,
            "text": "व्यावसायिक पारिस्थितिकी तंत्र स्पष्ट रूप से दिखाई दे रहा है।"
          },
          {
            "level": 2,
            "id": null,
            "text": "सुरक्षा उपायों को कौन रीसेट कर सकता है?"
          },
          {
            "level": 3,
            "id": null,
            "text": "एक रिकवरी टिकट जिसने खाते की सुरक्षा अक्षम कर दी, और रिपोर्ट किए गए $10,000 के नुकसान"
          },
          {
            "level": 3,
            "id": null,
            "text": "भंडार से परे"
          },
          {
            "level": 3,
            "id": "theft-ledger-title",
            "text": "Valve दरवाज़ा दो बार बंद हुआ, तेईस महीने के अंतराल पर। यह कभी बंद नहीं हुआ।"
          },
          {
            "level": 4,
            "id": null,
            "text": "लेजर वही कहता है जो कोई एक मामला नहीं कहता।"
          },
          {
            "level": 3,
            "id": null,
            "text": "गोपनीयता के साथ तकनीकी जवाबदेही भी होनी चाहिए।"
          },
          {
            "level": 2,
            "id": null,
            "text": "पैसे का पीछा करो। लेन-देन को अलग करो।"
          },
          {
            "level": 3,
            "id": null,
            "text": "जहाँ पैसा वास्तव में चलता है।"
          },
          {
            "level": 3,
            "id": null,
            "text": "पहले गतिविधि का वर्गीकरण करें, फिर दायित्व का।"
          },
          {
            "level": 3,
            "id": null,
            "text": "निशान, प्रक्रिया, ज्ञान और सहायता।"
          },
          {
            "level": 2,
            "id": null,
            "text": "डिजिटल सेवा अधिनियम: तथ्यों को सामने रखें"
          },
          {
            "level": 3,
            "id": null,
            "text": "एक दस-दिवसीय मांग।"
          },
          {
            "level": 3,
            "id": null,
            "text": "डीएसए समय खिड़की।"
          },
          {
            "level": 3,
            "id": null,
            "text": "अवधि के लिए सूचना पथ आवश्यक है।"
          },
          {
            "level": 3,
            "id": null,
            "text": "वार्षिक विश्वव्यापी कारोबार का"
          },
          {
            "level": 2,
            "id": null,
            "text": "नाबालिग: Steam लॉगिन आयु जांच नहीं है।"
          },
          {
            "level": 3,
            "id": null,
            "text": "ऑपरेटर और डेटा की पहचान करें।"
          },
          {
            "level": 3,
            "id": null,
            "text": "लॉगिन से जमा तक की यात्रा रिकॉर्ड करें।"
          },
          {
            "level": 2,
            "id": null,
            "text": "अनुरोध।   उत्तर।   अनुपस्थित तुलना।"
          },
          {
            "level": 3,
            "id": null,
            "text": "रिकॉर्ड मौजूद हैं; डेटा विषय को वे प्राप्त नहीं हुए।"
          },
          {
            "level": 2,
            "id": null,
            "text": "प्लेटफ़ॉर्म की अपनी वास्तुकला के विरुद्ध सदस्यता समझौता"
          },
          {
            "level": 3,
            "id": null,
            "text": "बाजार की ऊपरी सीमा और वाणिज्यिक उपयोग पर प्रतिबंध"
          },
          {
            "level": 3,
            "id": null,
            "text": "API-की भेद्यता को उपयोगकर्ता की लापरवाही के बजाय एक प्लेटफ़ॉर्म डिज़ाइन प्रश्न के रूप में देखना"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve हर लॉगिन पर auth होस्टनेम प्राप्त करता है।"
          },
          {
            "level": 3,
            "id": null,
            "text": "संग्रहीत शिकायतों में पैटर्न"
          },
          {
            "level": 3,
            "id": null,
            "text": "इस रिकॉर्ड का मूल्यांकन करने वाली अदालत एसएसए को अलग से नहीं पढ़ेगी।"
          },
          {
            "level": 2,
            "id": null,
            "text": "निष्कर्ष। वे रिकॉर्ड जिन्हें हम मांगते हैं।"
          },
          {
            "level": 2,
            "id": null,
            "text": "साक्ष्य ज्ञापन — स्रोत 1 द्वारा प्रदान की गई सामग्री"
          },
          {
            "level": 2,
            "id": null,
            "text": "उत्पादित PDF में की गई छंटनी केवल दिखावटी है: छिपाया गया पाठ अभी भी निकालने योग्य है।"
          },
          {
            "level": 2,
            "id": null,
            "text": "समर्थन और कानूनी पत्राचार प्रदर्शनी"
          },
          {
            "level": 2,
            "id": null,
            "text": "चयनित प्राथमिक अभिलेख"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-01",
            "text": "Hardware keys, requested in 2016"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-02",
            "text": "Crash reports without an effective opt-out"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-03",
            "text": "Auth-ticket abuse reported to Valve"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-01",
            "text": "44 disputed Market purchases"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-02",
            "text": "A permanent ban and closed appeals"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-03",
            "text": "A recovery reset and a reported $10,000 loss"
          },
          {
            "level": 2,
            "id": null,
            "text": "ArchiSteamFarm और स्वचालन खंड"
          },
          {
            "level": 2,
            "id": null,
            "text": "नियमों का खाका: रिकॉर्डेड प्लेटफ़ॉर्मों के विरुद्ध प्रावधान"
          },
          {
            "level": 3,
            "id": "ledger-title",
            "text": "व्यावसायिक उपयोग और खाते पर शुल्क"
          },
          {
            "level": 3,
            "id": "lw-register-title",
            "text": "प्लेटफ़ॉर्म रजिस्टर 175"
          },
          {
            "level": 4,
            "id": null,
            "text": "साक्ष्य का भार"
          },
          {
            "level": 4,
            "id": null,
            "text": "टैग किया गया रिकॉर्ड क्या है, और क्या नहीं है"
          },
          {
            "level": 2,
            "id": null,
            "text": "DSAR प्लेबुक: साक्ष्य का अनुरोध करें"
          },
          {
            "level": 3,
            "id": null,
            "text": "अपनी टाइमलाइन को संरक्षित करें।"
          },
          {
            "level": 3,
            "id": null,
            "text": "अपने संग्रहित डेटा का अनुरोध करें।"
          },
          {
            "level": 3,
            "id": null,
            "text": "डिलीवरी का रिकॉर्ड रखें।"
          },
          {
            "level": 3,
            "id": null,
            "text": "प्रतिक्रिया की तुलना करें।"
          },
          {
            "level": 3,
            "id": null,
            "text": "खाता सुरक्षा और पहुँच रिकॉर्ड"
          },
          {
            "level": 3,
            "id": null,
            "text": "अंतर जांच के लिए साक्ष्य है।"
          },
          {
            "level": 2,
            "id": null,
            "text": "समर्थन मात्रा। प्रकाशित प्रतिक्रिया समय।"
          },
          {
            "level": 3,
            "id": null,
            "text": "एक ही सपोर्ट डेस्क पर दो कतारें, 21 में संग्रहीत कैप्चर को क्रॉस-रीड करें।"
          },
          {
            "level": 2,
            "id": null,
            "text": "रिकॉर्ड्स की गिनती करें। दायरा जांचें।"
          },
          {
            "level": 2,
            "id": null,
            "text": "Valve कोई प्रवर्तन रिकॉर्ड प्रकाशित नहीं करता।\nहमने एक बनाया।"
          }
        ],
        "links": [
          "https://dotesports.com/counter-strike/news/csgo-lounge-billion-bets-3896",
          "https://store.steampowered.com/agreement/?l=english",
          "http://web.archive.org/web/20260921022032/https://store.steampowered.com/agreement/?l=english",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-all-results.json",
          "https://blog.counter-strike.net/expresstrade/",
          "http://web.archive.org/web/20260307161538/https://blog.counter-strike.net/expresstrade/",
          "https://wsgc.wa.gov/news/2016/washington-state-gambling-commission-orders-valve-stop-skins-gambling",
          "http://web.archive.org/web/20260520012601/https://wsgc.wa.gov/news/2016/washington-state-gambling-commission-orders-valve-stop-skins-gambling",
          "https://fr.scribd.com/document/328063293/Valve-s-Oct-18th-response-to-Washington-State-Gambling-Commission-s-cease-and-desist",
          "https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921021947/https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921022628/https://steamcommunity.com/linkfilter/?url=https:%2F%2Frollbit.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rbsnin.com.20260921T021120Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rollbit.com.json",
          "http://web.archive.org/web/20260921022740/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fskin.club",
          "http://web.archive.org/web/20260921022842/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fsc-auth.net",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skin.club.json",
          "http://web.archive.org/web/20260921022603/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fhowl.gg",
          "http://web.archive.org/web/20260921022636/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fhowl.uno",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/howl.gg.json",
          "http://web.archive.org/web/20260921022840/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fduelbits.com",
          "http://web.archive.org/web/20260921022901/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fswitchflips.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/duelbits.com.json",
          "http://web.archive.org/web/20260921022758/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgofast.com",
          "http://web.archive.org/web/20260921022847/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fauthtofast.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgofast.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/farmskins.com.20260921T025840Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/steam.kobal.cc.20260921T025844Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/farmskins.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cobaltlab.tech.20260921T041604Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cobaltauth.com.20260921T041608Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/cobaltlab.tech.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgo.net.20260921T041619Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cn2.easylot.net.20260921T041623Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgo.net.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/ggdrop.com.20260921T041637Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/ggauth.com.20260921T041641Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/ggdrop.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rustchance.com.20260921T041703Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/hgfuihd.com.20260921T041706Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rustchance.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skin.fans.20260921T041710Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.skinfans.com.20260921T041713Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skin.fans.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinport.com.20260921T041724Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinport.app.20260921T041728Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skinport.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skins.cash.20260921T041731Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinscash.live.20260921T041735Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skins.cash.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2hunt.com.20260921T041739Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rstspcl.com.20260921T041742Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tf2hunt.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgogem.com.20260922T192355Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/api.csgem.com.20260922T192358Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-2026-09-22.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/gamdom.com.20260922T192326Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/login.gambldom.com.20260922T192330Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/12cs.fail.20260922T192347Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/fail.games.20260922T192351Z.html",
          "http://web.archive.org/web/20260921022953/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgoempire.com",
          "http://web.archive.org/web/20260921022947/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgoempirelogin4.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgoempire.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cs.money.20260921T021131Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.dota.trade.20260921T021134Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/cs.money.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csfloat.com.20260921T041612Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgofloat.com.20260921T041615Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csfloat.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/g4skins.com.20260921T041630Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.g4s.to.20260921T041634Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/g4skins.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/juice.gg.20260921T041644Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/letmeinjuice.com.20260921T041648Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/juice.gg.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/market.csgo.com.20260921T041652Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2.net.20260921T041655Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/market.csgo.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rust.tm.20260921T041659Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rust.tm.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgolounge.com.20260922T192333Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2.net.20260922T192340Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2lounge.com.20260922T192337Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinbaron.de.20260921T041717Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinbaron.com.20260921T041721Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skinbaron.de.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2royal.com.20260921T041746Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2auth.com.20260921T041750Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tf2royal.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tradeit.gg.20260921T041753Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/connect-tradeit.com.20260921T041757Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tradeit.gg.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/upgrader.pro.20260921T041801Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/upgauth.space.20260921T041804Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/upgrader.pro.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-recheck-2026-09-21.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/domain-registration.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wayback-snapshots.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-2026-09-22c.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/master_registry.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/longitudinal-steam-phishing-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-steam-phishing-100.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-coverage-2026-09-22.json",
          "https://blog.csfloat.com/how-floatdb-tracks-items/",
          "http://web.archive.org/web/20260921022415/https://blog.csfloat.com/how-floatdb-tracks-items/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/platform-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/platforms-removed.json",
          "https://hackerone.com/reports/291750",
          "http://web.archive.org/web/20251116185046/https://hackerone.com/reports/291750",
          "https://hackerone.com/reports/1079561",
          "http://web.archive.org/web/20260924181830/https://hackerone.com/reports/1079561",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/hackerone-reports.json",
          "https://phishdestroy.io/steam_dossier/hi/steam_enforcement_evidence.html#support-records",
          "https://www.darknavy.org/blog/exploiting_steam_usual_and_unusual_ways_in_the_cef_framework/",
          "https://steamcommunity.com/groups/SteamClientBeta/discussions/0/3365901765276206401/",
          "http://web.archive.org/web/20250804051514/https://steamcommunity.com/groups/SteamClientBeta/discussions/0/3365901765276206401/",
          "https://www.chromium.org/developers/design-documents/safebrowsing/",
          "http://web.archive.org/web/20260821101616/https://www.chromium.org/developers/design-documents/safebrowsing/",
          "https://www.chromium.org/developers/how-tos/api-keys/",
          "http://web.archive.org/web/20260830122831/https://www.chromium.org/developers/how-tos/api-keys/",
          "https://github.com/Homebrew/homebrew-cask/issues/193814",
          "https://testsafebrowsing.appspot.com/",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/domain-registration.json",
          "https://phishdestroy.io/steam_dossier/hi/AUTH_AUDIT.md",
          "https://datatracker.ietf.org/doc/rfc6749/",
          "https://docs.cloud.google.com/docs/authentication/api-keys",
          "https://listings.pcisecuritystandards.org/pdfs/PCI_DSS_Resource_Guide_(003).pdf",
          "https://developer.apple.com/news/?id=02202019a",
          "http://web.archive.org/web/20250506070026/https://developer.apple.com/news/?id=02202019a",
          "https://dev.twitch.tv/docs/authentication/validate-tokens/",
          "https://discuss.dev.twitch.com/t/legacy-twitch-api-v5-i-e-kraken-shutdown-reminder-february-28-2022/36589",
          "http://web.archive.org/web/20250127085635/https://discuss.dev.twitch.com/t/legacy-twitch-api-v5-i-e-kraken-shutdown-reminder-february-28-2022/36589",
          "https://store.steampowered.com/news/posts/?enddate=1788390000",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/4123547285514022851",
          "https://skinvault.gg/blog/cs2-trade-protection-explained/",
          "https://csmarketcap.com/blog/market-insights/from-boom-to-bust-cs2s-trade-protection-impact",
          "https://skin.land/blog/steam-changes-cs2-trade-ban-logic-timing/",
          "https://help.steampowered.com/faqs/view/3041-A87A-E5F6-B6AC",
          "https://steamcommunity.com/ogg/593110/announcements/detail/533224478739530146",
          "https://steamcommunity.com/games/CSGO/announcements/detail/4447966961421256740",
          "https://steamcommunity.com/sharedfiles/filedetails/?id=2926756889",
          "https://steamcommunity.com/dev/apikey",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3734103130194459461",
          "https://steamcommunity.com/discussions/forum/1/3807266184852932971/",
          "https://help.steampowered.com/faqs/view/225C-C51E-B8F0-55B2",
          "https://store.steampowered.com/news/group/4/view/3314112260640237775",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/issues/325",
          "https://blog.dota2.com/2020/05/trading-cooldown/",
          "https://blog.counter-strike.net/index.php/2018/03/20308/",
          "http://web.archive.org/web/20250226114333/https://blog.counter-strike.net/index.php/2018/03/20308/",
          "https://phishdestroy.io/steam_dossier/hi/steam_evidence_archive.html",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/493839547938902179",
          "https://store.steampowered.com/online_conduct",
          "http://web.archive.org/web/20260921022120/https://store.steampowered.com/online_conduct",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260918014700/https://store.steampowered.com/subscriber_agreement/",
          "https://steamcommunity.com/dev/apiterms",
          "http://web.archive.org/web/20260921022210/https://steamcommunity.com/dev/apiterms",
          "https://help.steampowered.com/en/faqs/view/628C-E332-BD8C-4D36",
          "https://phishdestroy.io/steam_dossier/hi/social_graph.html",
          "https://phishdestroy.io/steam_dossier/hi/security_timeline.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wsgc-skins-gambling-briefing-2018.pdf",
          "https://wsgc.wa.gov/sites/default/files/2023-10/Skins%20Gambling.pdf",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wsgc-briefing-manifest.json",
          "https://x.com/csgobig",
          "https://www.facebook.com/csgobigofficial/",
          "https://500.casino/",
          "https://csgolounge.com/",
          "https://csgocasino.gg/",
          "https://x.com/CSGOatsecom",
          "https://x.com/CSGOSweep/status/937420902538543106",
          "https://x.com/Wild",
          "https://x.com/csgopot",
          "https://x.com/csgodiamondscom",
          "https://www.ftc.gov/legal-library/browse/cases-proceedings/162-3184-csgo-lotto-matter",
          "https://x.com/CSGODouble",
          "https://x.com/csgo_massive",
          "https://www.facebook.com/csgostrongfree/",
          "https://www.facebook.com/CSNCOM/",
          "https://www.gamblingcommission.gov.uk/report/young-people-and-gambling",
          "https://www.aph.gov.au/Parliamentary_Business/Committees/Senate/Environment_and_Communications/Gamingmicro-transactions",
          "https://phishdestroy.io/steam_dossier/hi/elite_skins.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/csfloat-catalogue.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/skinport-floor-over-cap.json",
          "https://pricempire.com/cs2-marketplaces",
          "http://web.archive.org/web/20260921022459/https://pricempire.com/cs2-marketplaces",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/priceempire-marketplaces.json",
          "https://www.steamanalyst.com/marketplace",
          "http://web.archive.org/web/20260719014552/https://www.steamanalyst.com/marketplace",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-atlas.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json",
          "https://phishdestroy.io/steam_dossier/hi/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/hi/steam_enforcement_evidence.html#case-support-recovery",
          "https://top10.owasp.org/2025/A01_2025-Broken_Access_Control/",
          "http://web.archive.org/web/20260920212535/https://top10.owasp.org/2025/A01_2025-Broken_Access_Control/",
          "https://store.steampowered.com/privacy_agreement/",
          "http://web.archive.org/web/20260921021648/https://store.steampowered.com/privacy_agreement/",
          "https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "http://web.archive.org/web/20250818113925/https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "https://www.dexerto.com/counter-strike-2/valve-saves-hacked-cs2-player-threatened-with-ransom-over-300000-of-rare-stickers-3283135/",
          "https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "http://web.archive.org/web/20220702042821/https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "https://www.kaspersky.com/blog/cs-go-two-million-usd-inventory-hack/44697/",
          "https://esportfire.com/article/the-2-million-usd-csgo-hack-22062022",
          "http://web.archive.org/web/20260515110250/https://esportfire.com/article/the-2-million-usd-csgo-hack-22062022",
          "https://esportsbetting.com/valve-deletes-130000-stolen-dragon-lore/",
          "https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "http://web.archive.org/web/20251115173120/https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "https://vkplay.ru/media/news/bloger-rasskazal-kak-podderzhka-steam-vorovala-akkaunty-igrokov/",
          "https://lis-skins.com/ru/blog/krupneisaia-mosenniceskaia-sxema-v-istorii-steam/",
          "https://escorenews.com/ru/csgo/news/44056-sotrudniki-podderjki-steam-zanimalis-krajey-skinov-s-akkauntov-za-god-oni-zarabotali-svyshe-300-tysyach-dollarov",
          "https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "http://web.archive.org/web/20250805141942/https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/outsourcing-archive-records.json",
          "https://community.skin.club/en/news/collector-has-steam-inventory-returned-after-bold-hack",
          "https://esportfire.com/article/300k-scam-full-katowice-2014-holo-collection-hacked",
          "http://web.archive.org/web/20251217072445/https://esportfire.com/article/300k-scam-full-katowice-2014-holo-collection-hacked",
          "https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng",
          "http://web.archive.org/web/20260920024236/https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng",
          "https://ag.ny.gov/press-release/2026/attorney-general-james-sues-game-developer-promoting-illegal-gambling-through",
          "http://web.archive.org/web/20260901015430/https://ag.ny.gov/press-release/2026/attorney-general-james-sues-game-developer-promoting-illegal-gambling-through",
          "https://www.fincen.gov/sites/default/files/2019-05/FinCEN%20CVC%20Guidance%20FINAL.pdf",
          "http://web.archive.org/web/20250711185007/https://www.fincen.gov/sites/default/files/2019-05/FinCEN%20CVC%20Guidance%20FINAL.pdf",
          "https://eur-lex.europa.eu/legal-content/EN/LSU/?uri=CELEX:32018L1673",
          "https://eur-lex.europa.eu/eli/dir/2024/1640/oj/eng",
          "http://web.archive.org/web/20260830153004/https://eur-lex.europa.eu/eli/dir/2024/1640/oj/eng",
          "https://eur-lex.europa.eu/eli/reg/2022/2065/oj/eng",
          "http://web.archive.org/web/20260920080125/https://eur-lex.europa.eu/eli/reg/2022/2065/oj/eng",
          "https://phishdestroy.io/steam_dossier/hi/legal_analysis.html",
          "https://partner.steamgames.com/doc/features/auth#website",
          "http://web.archive.org/web/20260921022335/https://partner.steamgames.com/doc/features/auth",
          "https://www.ftc.gov/legal-library/browse/rules/childrens-online-privacy-protection-rule-coppa",
          "http://web.archive.org/web/20260921070051/https://www.ftc.gov/legal-library/browse/rules/childrens-online-privacy-protection-rule-coppa",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/gdpr-ticket-1.png",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/screenshot-manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/gdpr-ticket-2.png",
          "https://datenschutz.hamburg.de/beschwerde",
          "https://edpb.europa.eu/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/regulatory-review/disclosure-audit.json",
          "https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "http://web.archive.org/web/20260821155801/https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "https://phishdestroy.io/steam_dossier/hi/index#exhibit-gallery-section",
          "https://github.com/ValveSoftware/steam-for-linux/issues/4521",
          "https://phishdestroy.io/steam_dossier/hi/steam_evidence_archive.html?source=GitHub&record=484",
          "https://github.com/ValveSoftware/steam-for-linux/issues/6459",
          "http://web.archive.org/web/20260419051343/https://github.com/ValveSoftware/steam-for-linux/issues/6459",
          "https://phishdestroy.io/steam_dossier/hi/steam_evidence_archive.html?source=GitHub&record=467",
          "https://github.com/ValveSoftware/Source-1-Games/issues/3857",
          "https://phishdestroy.io/steam_dossier/hi/steam_evidence_archive.html?source=GitHub&record=768",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "http://web.archive.org/web/20250320082450/https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://phishdestroy.io/steam_dossier/hi/steam_evidence_archive.html?source=Reddit&record=4533",
          "https://www.reddit.com/r/ohnePixel/comments/1hahqx2/permanently_banned_steam_account_without_a_clear/",
          "https://phishdestroy.io/steam_dossier/hi/steam_evidence_archive.html?source=Reddit&record=4766",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://phishdestroy.io/steam_dossier/hi/steam_evidence_archive.html?source=Reddit&record=4592",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/selected-evidence-records.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive_manifest.json",
          "https://phishdestroy.io/steam_dossier/hi/card_economy.html",
          "https://github.com/JustArchiNET/ArchiSteamFarm/wiki/FAQ",
          "https://phishdestroy.io/steam_dossier/hi/card_economy.html#scale",
          "https://phishdestroy.io/steam_dossier/hi/card_economy.html#licence",
          "https://phishdestroy.io/steam_dossier/hi/enforcement_audit.html",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "http://web.archive.org/web/20260924181709/https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://rdap.verisign.com/com/v1/domain/csgoempire.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoempire.com",
          "https://rdap.verisign.com/com/v1/domain/csgoempirelogin4.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/csgoempire.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustreaper.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustreaper.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/rustreaper.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustly.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustly.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/rustly.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgofast.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgofast.com",
          "https://rdap.verisign.com/com/v1/domain/authtofast.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/csgofast.com.json",
          "https://rdap.verisign.com/com/v1/domain/duelbits.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fduelbits.com",
          "https://rdap.verisign.com/com/v1/domain/switchflips.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/duelbits.com.json",
          "https://rdap.verisign.com/com/v1/domain/farmskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffarmskins.com",
          "https://tld-rdap.verisign.com/cc/v1/domain/kobal.cc",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/farmskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoluck.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoluck.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/csgoluck.com.json",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/domain-registry/insane.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Finsane.gg",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/insane.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs2skin.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs2skin.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/cs2skin.com.json",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/domain-registry/juice.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fjuice.gg",
          "https://rdap.verisign.com/com/v1/domain/letmeinjuice.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/juice.gg.json",
          "https://rdap.verisign.com/com/v1/domain/ggdrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fggdrop.com",
          "https://rdap.verisign.com/com/v1/domain/ggauth.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/ggdrop.com.json",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/domain-registry/howl.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhowl.gg",
          "https://rdap.radix.host/rdap/domain/howl.uno",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/howl.gg.json",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/domain-registry/chicken.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fchicken.gg",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/chicken.gg.json",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/domain-registry/csgocasino.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgocasino.gg",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/csgocasino.gg.json",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/domain-registry/hunt.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhunt.gg",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/hunt.gg.json",
          "https://rdap.verisign.com/com/v1/domain/csbattle.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsbattle.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/csbattle.com.json",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/domain-registry/skinrave.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinrave.gg",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/skinrave.gg.json",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/domain-registry/csdouble.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsdouble.gg",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/csdouble.gg.json",
          "https://rdap.verisign.com/com/v1/domain/rustchance.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustchance.com",
          "https://rdap.verisign.com/com/v1/domain/hgfuihd.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/rustchance.com.json",
          "https://rdap.radix.host/rdap/domain/cobaltlab.tech",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcobaltlab.tech",
          "https://rdap.verisign.com/com/v1/domain/cobaltauth.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/cobaltlab.tech.json",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/domain-registry/raided.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fraided.gg",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/raided.gg.json",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/domain-registry/rustneo.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustneo.gg",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/rustneo.gg.json",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/domain-registry/splits.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsplits.gg",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/splits.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/upgrader.pro",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fupgrader.pro",
          "https://rdap.radix.host/rdap/domain/upgauth.space",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/upgrader.pro.json",
          "https://rdap.centralnic.com/fans/domain/skin.fans",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.fans",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/skin.fans.json",
          "https://rdap.nic.one/domain/hotpizza.one",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhotpizza.one",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/hotpizza.one.json",
          "https://rdap.verisign.com/com/v1/domain/g4skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg4skins.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/g4skins.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2royal.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2royal.com",
          "https://rdap.verisign.com/com/v1/domain/tf2auth.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/tf2royal.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2hunt.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2hunt.com",
          "https://rdap.verisign.com/com/v1/domain/rstspcl.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/tf2hunt.com.json",
          "https://rdap.identitydigital.services/rdap/domain/tf2.bet",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2.bet",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/tf2.bet.json",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/domain-registry/openstars.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fopenstars.gg",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/openstars.gg.json",
          "https://rdap.verisign.com/com/v1/domain/skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/skins.com.json",
          "https://rdap.identitydigital.services/rdap/domain/white.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwhite.market",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/white.market.json",
          "https://rdap.identitydigital.services/rdap/domain/moon.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmoon.market",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/moon.market.json",
          "https://rdap.verisign.com/com/v1/domain/csfloat.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsfloat.com",
          "https://rdap.verisign.com/com/v1/domain/csgofloat.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/csfloat.com.json",
          "https://rdap.identitydigital.services/rdap/domain/skin.land",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.land",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/skin.land.json",
          "https://rdap.verisign.com/com/v1/domain/haloskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhaloskins.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/haloskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/163.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuff.163.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/buff.163.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmarket.csgo.com",
          "https://rdap.verisign.com/net/v1/domain/dota2.net",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/market.csgo.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinport.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinport.com",
          "https://pubapi.registry.google/rdap/domain/skinport.app",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/skinport.com.json",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/domain-registry/skinflow.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinflow.gg",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/skinflow.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/skin.place",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.place",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/skin.place.json",
          "https://rdap.verisign.com/com/v1/domain/skinsmonkey.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinsmonkey.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/skinsmonkey.com.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbaron.de",
          "https://rdap.verisign.com/com/v1/domain/skinbaron.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/skinbaron.de.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frust.tm",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/rust.tm.json",
          "https://rdap.verisign.com/com/v1/domain/pirateswap.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fpirateswap.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/pirateswap.com.json",
          "https://rdap.radix.host/rdap/domain/mannco.store",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmannco.store",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/mannco.store.json",
          "https://rdap.verisign.com/com/v1/domain/skinswap.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinswap.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/skinswap.com.json",
          "https://rdap.verisign.com/com/v1/domain/exeskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fexeskins.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/exeskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/balticskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbalticskins.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/balticskins.com.json",
          "https://rdap.nic.trade/domain/cs.trade",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.trade",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/cs.trade.json",
          "https://rdap.verisign.com/com/v1/domain/rapidskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frapidskins.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/rapidskins.com.json",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/domain-registry/tradeit.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftradeit.gg",
          "https://rdap.verisign.com/com/v1/domain/connect-tradeit.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/tradeit.gg.json",
          "https://rdap.verisign.com/com/v1/domain/49skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F49skins.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/49skins.com.json",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/domain-registry/skinvault.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinvault.gg",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/skinvault.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/aim.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Faim.market",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/aim.market.json",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/domain-registry/skinout.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinout.gg",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/skinout.gg.json",
          "https://rdap.verisign.com/com/v1/domain/ntskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fntskins.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/ntskins.com.json",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/domain-registry/gamerpay.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamerpay.gg",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/gamerpay.gg.json",
          "https://rdap.nic.tf/domain/scrap.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fscrap.tf",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/scrap.tf.json",
          "https://rdap.nic.tf/domain/marketplace.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmarketplace.tf",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/marketplace.tf.json",
          "https://rdap.identitydigital.services/rdap/domain/skins.cash",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.cash",
          "https://rdap.identitydigital.services/rdap/domain/skinscash.live",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/skins.cash.json",
          "https://rdap.verisign.com/net/v1/domain/csgo.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo.net",
          "https://rdap.verisign.com/net/v1/domain/easylot.net",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/csgo.net.json",
          "https://rdap.verisign.com/net/v1/domain/cybershoke.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcybershoke.net",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/cybershoke.net.json",
          "https://rdap.verisign.com/net/v1/domain/fastcup.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffastcup.net",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/fastcup.net.json",
          "https://rdap.verisign.com/com/v1/domain/leetify.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fleetify.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/leetify.com.json",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/domain-registry/scope.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fscope.gg",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/scope.gg.json",
          "https://rdap.verisign.com/com/v1/domain/tradeupspy.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftradeupspy.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/tradeupspy.com.json",
          "https://rdap.identitydigital.services/rdap/domain/cs.deals",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.deals",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/cs.deals.json",
          "https://rdap.verisign.com/com/v1/domain/pricempire.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fpricempire.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/pricempire.com.json",
          "https://rdap.identitydigital.services/rdap/domain/lzt.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flzt.market",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/lzt.market.json",
          "https://rdap.verisign.com/com/v1/domain/z2u.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fz2u.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/z2u.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoroll.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoroll.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/csgoroll.com.json",
          "https://rdap.verisign.com/com/v1/domain/rollbit.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frollbit.com",
          "https://rdap.verisign.com/com/v1/domain/rbsnin.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/rollbit.com.json",
          "https://rdap.identitydigital.services/rdap/domain/500.casino",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F500.casino",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/500.casino.json",
          "https://rdap.verisign.com/com/v1/domain/csgobig.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgobig.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/csgobig.com.json",
          "https://rdap.verisign.com/com/v1/domain/casedrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcasedrop.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/casedrop.com.json",
          "https://rdap.verisign.com/com/v1/domain/banditcamp.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbanditcamp.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/banditcamp.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinbox.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbox.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/skinbox.com.json",
          "https://rdap.verisign.com/com/v1/domain/tastydrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftastydrop.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/tastydrop.com.json",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/domain-registry/csgopolygon.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgopolygon.gg",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/csgopolygon.gg.json",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/domain-registry/magicdrop.ru.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmagicdrop.ru",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/magicdrop.ru.json",
          "https://rdap.verisign.com/com/v1/domain/csdice.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsdice.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/csdice.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinodds.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinodds.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/skinodds.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgowin.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgowin.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/csgowin.com.json",
          "https://rdap.verisign.com/net/v1/domain/csgorun.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgorun.net",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/csgorun.net.json",
          "https://rdap.verisign.com/com/v1/domain/openskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fopenskins.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/openskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustbet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustbet.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/rustbet.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgomagic.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgomagic.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/csgomagic.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgobounty.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgobounty.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/csgobounty.com.json",
          "https://rdap.verisign.com/com/v1/domain/ezskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fezskins.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/ezskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustcases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustcases.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/rustcases.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoreaper.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoreaper.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/csgoreaper.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgocases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgocases.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/csgocases.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo-skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo-skins.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/csgo-skins.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgonet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgonet.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/csgonet.com.json",
          "https://rdap.verisign.com/com/v1/domain/wtfskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwtfskins.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/wtfskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/flamecases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fflamecases.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/flamecases.com.json",
          "https://rdap.verisign.com/com/v1/domain/gamedom.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamedom.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/gamedom.com.json",
          "https://rdap.nic.club/domain/skin.club",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.club",
          "https://rdap.verisign.com/net/v1/domain/sc-auth.net",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/skin.club.json",
          "https://rdap.verisign.com/com/v1/domain/daddyskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdaddyskins.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/daddyskins.com.json",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/domain-registry/rustix.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustix.gg",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/rustix.gg.json",
          "https://rdap.nic.club/domain/skins.club",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.club",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/skins.club.json",
          "https://rdap.publicinterestregistry.org/rdap/domain/csgohouse.org",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgohouse.org",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/csgohouse.org.json",
          "https://rdap.verisign.com/net/v1/domain/skinrave.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinrave.net",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/skinrave.net.json",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/domain-registry/bloodycase.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbloodycase.gg",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/bloodycase.gg.json",
          "https://rdap.verisign.com/com/v1/domain/csgoclicker.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoclicker.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/csgoclicker.com.json",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/domain-registry/rustbet.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustbet.gg",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/rustbet.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs-drop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs-drop.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/cs-drop.com.json",
          "https://rdap.verisign.com/net/v1/domain/hellstore.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhellstore.net",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/hellstore.net.json",
          "https://rdap.verisign.com/com/v1/domain/rustloot.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustloot.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/rustloot.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo-case.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo-case.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/csgo-case.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgogem.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgogem.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/csgogem.com.json",
          "https://rdap.verisign.com/com/v1/domain/rainbet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frainbet.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/rainbet.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustclash.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustclash.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/rustclash.com.json",
          "https://rdap.identitydigital.services/rdap/domain/12cs.fail",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F12cs.fail",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/12cs.fail.json",
          "https://rdap.verisign.com/com/v1/domain/tf2easy.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwww.tf2easy.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/tf2easy.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2blaze.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2blaze.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/tf2blaze.com.json",
          "https://rdap.verisign.com/com/v1/domain/shuffle.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fshuffle.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/shuffle.com.json",
          "https://rdap.identitydigital.services/rdap/domain/buff.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuff.market",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/buff.market.json",
          "https://rdap.identitydigital.services/rdap/domain/avan.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Favan.market",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/avan.market.json",
          "https://rdap.identitydigital.services/rdap/domain/cs.money",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.money",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/cs.money.json",
          "https://rdap.verisign.com/com/v1/domain/uuskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fuuskins.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/uuskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/youpin898.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fyoupin898.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/youpin898.com.json",
          "https://rdap.verisign.com/com/v1/domain/c5game.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fc5game.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/c5game.com.json",
          "https://rdap.verisign.com/com/v1/domain/waxpeer.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwaxpeer.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/waxpeer.com.json",
          "https://rdap.verisign.com/com/v1/domain/dmarket.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdmarket.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/dmarket.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamcommunity.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamcommunity.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/steamcommunity.com.json",
          "https://rdap.verisign.com/com/v1/domain/lootfarm.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flootfarm.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/lootfarm.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustskins.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/rustskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/krakatoa.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fkrakatoa.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/krakatoa.com.json",
          "https://rdap.verisign.com/com/v1/domain/shadowpay.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fshadowpay.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/shadowpay.com.json",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/domain-registry/igxe.cn.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Figxe.cn",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/igxe.cn.json",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/domain-registry/swap.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fswap.gg",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/swap.gg.json",
          "https://rdap.verisign.com/com/v1/domain/bitskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbitskins.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/bitskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2mart.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2mart.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/tf2mart.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinbid.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbid.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/skinbid.com.json",
          "https://rdap.verisign.com/com/v1/domain/lootbear.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flootbear.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/lootbear.com.json",
          "https://rdap.nic.tf/domain/backpack.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbackpack.tf",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/backpack.tf.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fstntrading.eu",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/stntrading.eu.json",
          "https://rdap.verisign.com/com/v1/domain/skinwallet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinwallet.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/skinwallet.com.json",
          "https://rdap.verisign.com/com/v1/domain/dota2market.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdota2market.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/dota2market.com.json",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/domain-registry/xplay.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fxplay.gg",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/xplay.gg.json",
          "https://rdap.verisign.com/com/v1/domain/esportal.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fesportal.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/esportal.com.json",
          "https://rdap.registro.br/domain/gamersclub.com.br",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamersclub.com.br",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/gamersclub.com.br.json",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/domain-registry/epidemic.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fepidemic.gg",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/epidemic.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs2stash.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs2stash.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/cs2stash.com.json",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/domain-registry/csgoskins.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoskins.gg",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/csgoskins.gg.json",
          "https://rdap.verisign.com/com/v1/domain/steamanalyst.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamanalyst.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/steamanalyst.com.json",
          "https://rdap.verisign.com/net/v1/domain/steamcardexchange.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamcardexchange.net",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/steamcardexchange.net.json",
          "https://rdap.verisign.com/com/v1/domain/dotabuff.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdotabuff.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/dotabuff.com.json",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/domain-registry/tracker.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftracker.gg",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/tracker.gg.json",
          "https://rdap.verisign.com/com/v1/domain/funpay.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffunpay.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/funpay.com.json",
          "https://rdap.verisign.com/com/v1/domain/playerauctions.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fplayerauctions.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/playerauctions.com.json",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/domain-registry/eldorado.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Feldorado.gg",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/eldorado.gg.json",
          "https://rdap.verisign.com/com/v1/domain/g2a.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg2a.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/g2a.com.json",
          "https://rdap.verisign.com/net/v1/domain/kinguin.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fkinguin.net",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/kinguin.net.json",
          "https://rdap.verisign.com/com/v1/domain/g2g.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg2g.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/g2g.com.json",
          "https://rdap.verisign.com/com/v1/domain/playerup.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fplayerup.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/playerup.com.json",
          "https://rdap.verisign.com/net/v1/domain/smurfhub.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfhub.net",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/smurfhub.net.json",
          "https://rdap.verisign.com/com/v1/domain/smurfaccounts.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfaccounts.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/smurfaccounts.com.json",
          "https://rdap.verisign.com/com/v1/domain/buycsgorank.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuycsgorank.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/buycsgorank.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgosmurfkings.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgosmurfkings.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/csgosmurfkings.com.json",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/domain-registry/smurfstore.co.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfstore.co",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/smurfstore.co.json",
          "https://rdap.verisign.com/com/v1/domain/steamlvlup.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlvlup.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/steamlvlup.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamlevels.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlevels.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/steamlevels.com.json",
          "https://rdap.verisign.com/com/v1/domain/levelsteam.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flevelsteam.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/levelsteam.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamlevelu.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlevelu.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/steamlevelu.com.json",
          "https://rdap.verisign.com/com/v1/domain/eloking.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Feloking.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/eloking.com.json",
          "https://rdap.publicinterestregistry.org/rdap/domain/boosteria.org",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fboosteria.org",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/boosteria.org.json",
          "https://rdap.verisign.com/com/v1/domain/overgear.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fovergear.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/overgear.com.json",
          "https://rdap.verisign.com/com/v1/domain/blazingboost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fblazingboost.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/blazingboost.com.json",
          "https://rdap.verisign.com/com/v1/domain/dota2boost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdota2boost.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/dota2boost.com.json",
          "https://rdap.verisign.com/com/v1/domain/buyboost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuyboost.com",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit/buyboost.com.json",
          "https://phishdestroy.io/steam_dossier/hi/steam_tos_assets/auth-route-audit.json",
          "https://help.steampowered.com/en/faqs/view/365F-4BEE-2AE2-7BDD",
          "https://store.steampowered.com/privacy_agreement/#8",
          "https://www.edpb.europa.eu/system/files/2023-04/edpb_guidelines_202201_data_subject_rights_access_v2_en.pdf",
          "https://web.archive.org/web/20260810154631/https://store.steampowered.com/stats/support",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/part2-measurements.json",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/TOTAL_VALVE_SCANDALS_MASTER_DB.csv",
          "https://phishdestroy.io/steam_dossier/hi/license_disclaimer.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/hi/index.content.json",
      "export_json_sha256": "968566d8c2f06f1d170b1adf29cc67272b404d4222234e3593fe3111456f0609"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "hi/investigation_part2.html",
      "language": "hi",
      "title": "खाता पहुँच और जवाबदेही — द Steam डोजियर",
      "source_url": "https://phishdestroy.io/steam_dossier/hi/investigation_part2",
      "source_html_sha256": "ebc38c6e4f396b2e6f2982b6c34e015502f8935823bf7c66ca084220a5d0032f",
      "exported_at": "2026-09-29T00:22:43.982Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "investigation_part2.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/hi/investigation_part2.pdf?v=print-20260929-v5",
        "sha256": "a1d29ca91c164504e3d17772d4fa6e95bc487ab5d49bdd3ada839224a7013807",
        "bytes": 379695,
        "pages": 8
      },
      "integrity": {
        "signed_object": "investigation_part2.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "investigation_part2.content.json.asc",
        "digest_file": "investigation_part2.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify investigation_part2.content.json.asc investigation_part2.content.json",
          "sha256sum -c investigation_part2.content.json.sha256"
        ]
      },
      "content": {
        "text": "स्टीम डोजियर / द्वितीय\n\nभाग II — खाते तक पहुँच, आउटसोर्स समर्थन और प्रवर्तन\n\nसार्वजनिक स्वचालन। आउटसोर्स्ड सहायता। लोग बचे हुए खर्च की गिनती करते रह गए।\n\nइस उपखंड की शुरुआत करें ↓\nप्रदर्शन 01 / लाइव शैडो मार्केट निगरानी550,000+\n\nSteam एफएसबी मार्केट पर सक्रिय रूप से बिक्री के लिए खाते (एक गुमनाम लेबल; मूल नाम यहां छिपाया गया है)\nइसी क्षण\n\n550,000+ लाइव इन्वेंटरी · 231,829 ऐतिहासिक स्क्रैप्ड कॉर्पस में (198,320 स्टीलर लॉग्स)\n\nहाइजैक किए गए Steam खातों के लिए प्रमुख भूमिगत क्लियरिंगहाउस, FSB Market (संबंधित नाम गोपनीय रखे गए), Valve के आधिकारिक Steam OpenID (openid.realm = https://FSB Market). किसी भी समय, आधे मिलियन से अधिक चोरी और समझौता किए गए खाते (RedLine/Lumma से स्टीलर लॉग, फ़िशिंग कैप्चर, क्रेडेंशियल स्टफिंग) कुछ ही सेंट में सक्रिय रूप से सूचीबद्ध होते हैं ($0.50–$2.00). न तो FSB Market न the associated forum Valve के लिंक फ़िल्टर द्वारा अवरुद्ध है। यह औद्योगिक जलाशय है जो 63.06% द्वारा भुगतान किए गए बॉट खातों को आपूर्ति करता है, जिन्हें Valve पीड़ित की सहायता किए बिना प्रतिबंधित करता है।\n\nलाइव इंटेल: शैडो मार्केट मॉनिटरिंग (550k+ लाइव) ↗ · कैप्चर रिकॉर्ड खोलें ↗ · ओपन लिंक फ़िल्टर ट्रेस ↗550के+ लाइव\n\n01 लेखकों के साथ एक पारिस्थितिकी तंत्र\n\nस्वचालन नेएक कागज़ी निशान\n\nनामित परियोजनाएँ। प्रकाशित क्षमताएँ। किसी टूल को उसके दस्तावेज़ीकरण से ट्रेस करें, फिर एकत्रित डेवलपर संबंधों की जाँच करें।\n\n252एकत्रित रिपॉजिटरी\n3,320गिटहब प्रोफाइल\n4,214प्रोफ़ाइल–भंडार युग्म\nValve संरचनासामुदायिक पुस्तकालयपुन: प्रयोज्य अनुप्रयोग\nरेखाएँ दस्तावेज़ित एकीकरण या निर्भरताएँ दिखाती हैं। किसी नोड को चुनें ताकि आप उसके प्रमाणों का अनुसरण कर सकें।\n\nमल्टी-खाता स्वचालन / जस्टआर्चीनेट\n\nआर्चीस्टीमफार्म\n\nयह प्रोजेक्ट स्पष्ट रूप से Steam खातों में एक साथ कार्ड फार्मिंग का विज्ञापन करता है। इसकी प्रोजेक्ट फ़ाइल में SteamKit2 निर्भरता घोषित की गई है।\n\nपरियोजना की अपनी दस्तावेज़ीकरण पढ़ें ↗\n\nस्टीमकिट → आर्चीस्टीमफार्म\nनिर्भरता घोषित करें ↗\n\nएकत्रित संबंध\n\n40 योगदानकर्ता लेबल · 40 फ़ोर्कर लेबल\n\nनीचे योगदानकर्ता का नमूना दिया गया है। ये लेबल रिपॉजिटरी संबंध का वर्णन करते हैं, रोजगार या अनुमोदन का नहीं।\n\n@JustArchi@renovate[बॉट]@JustArchi-ArchiBot@dependabot-preview[बॉट]@renovate-बॉट@एक्शन-यूज़र@डिपेंडabot-समर्थन@एब्रिनोस\nडेवलपर ग्राफ़ क्या स्थापित करता है\n\nGitHub यह ग्राफ़ नामित परियोजनाओं और GitHub प्रोफाइल के बीच प्रकाशित योगदानकर्ता और फोर्कर संबंधों को दर्शाता है। ये सार्वजनिक रिकॉर्ड हैं — रिपॉजिटरी फोर्क्स, योगदान सूचियाँ, प्रोफ़ाइल संघ। सवाल यह है कि प्रकाशित क्षमताओं और डेवलपर संबंधों के कागजी निशान के जवाब के लिए Valve को क्या उत्तर देना चाहिए, न कि यह कि इस जांच ने क्या नया आविष्कार किया। स्रोत हैश्स को में सहेजा जाता है। नक्शा उत्पत्ति.\n\nपूरे नेटवर्क को देखें ↗रिपॉजिटरी स्रोत डेटा ↓\n\n02 / विभिन्न प्रमाणपत्र। विभिन्न शक्तियाँ।\n\nकौन सी कुंजीहम किसकी बात कर रहे हैं?\n\nएक खेल खेलने के लिए खिलाड़ी को व्यक्तिगत वेब API कुंजी जारी करने की आवश्यकता नहीं होती। यही इस जांच के केंद्र में अंतर है।\n\n01 / उपयोगकर्ता खाता\nव्यक्तिगत वेब API कुंजी\nsteamcommunity.com/dev/apikey\n\nअनुमत API कॉल्स के लिए उपयोगकर्ता खाते से जारी किया गया। कुंजी निर्माण, दृश्यता, रद्दीकरण और दुरुपयोग का पता लगाना खाता-सुरक्षा संबंधी प्रश्न हैं।\n\n02 / गेम बैकएंड\nप्रकाशक वेब API कुंजी\n\nSteamworks साझेदार समर्थित बैकएंड संचालन, जिनमें गेम-संबंधी सेवाएँ शामिल हैं, के लिए प्रकाशक क्रेडेंशियल्स का उपयोग करते हैं। एक खिलाड़ी की व्यक्तिगत कुंजी एक अलग क्रेडेंशियल है।\n\n03 / पहचान और सत्र\nओपनआईडी / सत्र टोकन\n\nOpenID किसी वेबसाइट को पहचान की पुष्टि करता है। एक Steam सत्र या रिफ्रेश टोकन का उद्देश्य अलग होता है। इन तंत्रों को एक ही परस्पर प्रतिस्थाप्य \"API कुंजी\" के रूप में प्रस्तुत नहीं किया जाना चाहिए।\n\nValve यह उपयोगकर्ता और प्रकाशक दोनों की वेब API कुंजियों को दस्तावेज़ करता है। इसलिए संपूर्ण वेब API Steamworks से अलग नहीं है। API मुख्य दस्तावेज़ीकरण ↗ संग्रहित 2026-09-15 ↗ · गेम-सत्र प्रमाणीकरण ↗ संग्रहित 2026-08-29 ↗\n\nटूल के लेखक द्वारा दस्तावेजीकृत / मार्च 2024\n\nAPI स्वचालन एक से अधिक कुंजी का उपयोग कर सकता है।\n\nTrade Offer Manager की विकी में वर्णित है कि जब कोई अलग API कुंजी मौजूद नहीं होती, तो वेब API के कुछ हिस्सों के लिए सत्र एक्सेस टोकन का उपयोग किया जाता है। यह लेट 2023. से कुंजी निर्माण के लिए मोबाइल पुष्टि को भी रिकॉर्ड करता है। रखरखावकर्ता इस प्रकार टोकन के उपयोग को Valve द्वारा समर्थित नहीं मानते; यह एक पुराना दस्तावेज़ीकरण दावा है, न कि कोई लाइव बाईपास परीक्षण।\n\nरखरखावकर्ता की व्याख्या की जाँच करें ↗ संचित 2026-09-24 ↗\n\nमानवीय पक्ष / एक चित्रमय फ़िशिंग पथ\n\nअभी भी खेल रहा हूँ।पहले से ही उजागर।\n\nएक मित्र का संदेश। मतदान का अनुरोध। एक \"धन्यवाद\" पृष्ठ। खिलाड़ी के लिए कार्य समाप्त हो चुका है। एक समझौता किया गया सत्र उस क्षण से भी अधिक समय तक चल सकता है।\n\nखिलाड़ी की स्क्रीन पर\n\nF\nएक मित्र का वृत्तांत\n\nक्या आप हमारी टीम को वोट दे सकते हैं?\n\nSteam चैट के माध्यम से एक परिचित खाते से अनुरोध आता है। इस परिदृश्य में, लिंक किया गया पृष्ठ क्लाइंट के ब्राउज़र में खुलता है।\n\nनज़रों से ओझल\n\nविश्वास वेबसाइट से पहले शुरू होता है।\n\nएक हैक किए गए मित्र के खाते से फिशिंग लिंक को विश्वसनीयता मिल सकती है। आसपास का Steam इंटरफ़ेस गंतव्य वेबसाइट की पुष्टि नहीं करता।\n\nपरिचित प्रेषक / बाहरी गंतव्य\nकिसी भी वस्तु की बिक्री से पहले खाता सुरक्षा सबसे महत्वपूर्ण मुद्दा है।\n\nखिलाड़ी ने ऑटोमेशन क्रेडेंशियल बनाने या नियंत्रण सौंपने का इरादा नहीं किया था। खेल में वापस आना इस बात का प्रमाण नहीं है कि खाता सुरक्षित है।Valve के पास सत्र लॉग, API कुंजी निर्माण रिकॉर्ड और डिवाइस सहसंबंध डेटा होता है, जबकि पीड़ित के पास नहीं। यही विषमता जवाबदेही की समस्या है।\n\nसत्र पहुँच और प्रमाण-पत्र प्रकार\n\nAPI कुंजी और एक लॉग-इन सत्र अलग-अलग प्रमाण-पत्र हैं जिनकी क्षमताएँ भिन्न होती हैं। कुंजी को रद्द करने से सक्रिय सत्र समाप्त नहीं होता।Valve की अपनी दस्तावेज़ीकरण दोनों का वर्णन करती है; Valve में वे लॉग्स संग्रहीत हैं जो किसी भी विवादित कार्रवाई के समय कौन सा प्रमाण-पत्र सक्रिय था, दिखाते हैं। मांग उस रिकॉर्ड का प्रकटीकरण करने की है — न कि उस निष्कर्ष की जिसे जांच ने गढ़ा हो। टोकन हैंडलिंग पर मेंटेनर दस्तावेज़ीकरण ↗ संचित 2026-09-24 ↗ · Valve मुख्य दस्तावेज़ीकरण ↗ संग्रहित 2026-09-15 ↗\n\n03 / आधिकारिक बाज़ार की एक ऊपरी सीमा होती है\n\nयह वस्तु दुर्लभ हो सकती है।सीमा बनी रहती है।\n\nएक ही कम्युनिटी मार्केट लिस्टिंग के माध्यम से उस पूरी कीमत पर लिस्टिंग कैप से अधिक कीमत प्राप्त नहीं की जा सकती।\n\nउदाहरणार्थ पूछी गई कीमत$5,000आइटम की माँग मूल्य बदलें\n$100$20,000\n\nप्रकाशित सीमा का एक उदाहरण, व्यापार करने के लिए कोई मूल्यांकन या सिफारिश नहीं।\n\nसूचीकरण सीमा≈ $1,800\nवॉलेट कैप≈ $2,000\n\nप्रकाशित लिस्टिंग सीमा से ऊपर\n\nवॉलेट फंड्स को बैंक खाते में निकाला नहीं जा सकता। ये प्रतिबंध तीसरे पक्ष के स्किन मार्केट्स की मांग पैदा करते हैं: एक ऐसी मांग जिसे लिस्टिंग और वॉलेट कैप्स उत्पन्न करते हैं, जबकि Valve के अपने नियम व्यावसायिक ऑपरेटरों को इसे पूरा करने से रोकते हैं।\n\nSteam की बाज़ार सीमाएँ ↗ संचित 2026-09-21 ↗\n\n04 / सहायता सीमा के भीतर\n\nडेटा की जिम्मेदारी सौंपी गई।पहुँच के लिए उत्तरदायी।\n\nValve की गोपनीयता नीति स्पष्ट रूप से समर्थन के लिए आवश्यक होने पर तीसरे पक्ष के समर्थन प्रदाताओं के साथ व्यक्तिगत डेटा साझा करने का प्रावधान करती है।\n\nखिलाड़ीखाता और साक्ष्य\n→\nवाल्वपुनर्प्राप्ति प्रक्रिया\n→\nसमर्थन प्रदाताप्रत्यायित पहुँच\n\nगोपनीयता नीति §5.2 ↗ Valve की अपनी नीति तीसरे पक्ष को समर्थन पहुँच की अनुमति देती है। खुले प्रश्न हैं: कौन-सी अनुमतियाँ दी गई थीं, कौन-से ऑडिट ट्रेल्स मौजूद हैं, और जब कथित तौर पर पहुँच का दुरुपयोग हुआ तो क्या हुआ।\n\n2015\nमापदंड सार्वजनिक था।\n\nValve व्यापक स्तर पर खाता चोरी को स्वीकार किया और सुरक्षात्मक उपायों का वर्णन किया।\n\nValve प्रकाशन ↗संग्रहीत 2026-08-09 ↗\n2015\nValve डेस्क को आउटसोर्स किया — और कहा भी\n\nValve एक छोटी इन-हाउस Steam समर्थन नेतृत्व टीम रखता है और कहा कि कुछ अलग-अलग कंपनियों को काम पर रखा सहायता संभालने के लिए (एरिक जॉनसन, Valve, कोटाकू को); इसकी गोपनीयता नीति §5.2 उन तृतीय पक्षों को उपयोगकर्ता डेटा तक पहुँच की अनुमति देती है। कौन सा ठेकेदार खाता-वसूली की पहुँच रखता है, ईValve ने कभी खुलासा नहीं किया। — सामुदायिक चर्चा में Concentrix जैसे विक्रेताओं का नाम लिया गया, लेकिन इनमें से कवनो भी Valve-पुष्टित नहीं है। आउटसोर्स्ड डेस्क दोनों में से किसी भी नीचे दिए गए प्रवेश से कई साल पहले ही मौजूद था।\n\nKotaku: Valve अपने समर्थन पर ↗संग्रहीत 2025-07-11 ↗\n2023\nपहला प्रवेश\n\nValve की CS:GO टीम अपनी ही सहायता-अनुरोध प्रक्रिया के माध्यम से हैक हुए एक खाते की जिम्मेदारी लिखित रूप में स्वीकार करती है, और ट्रेड्स को रद्द कर देती है।\n\nआउटसोर्सिंग मामला खोलें ↓\n2025\nदूसरा प्रवेश\n\n33 कुछ महीने बाद, Steam सपोर्ट लिखता है कि एक तकनीशियन ने हमारी प्रक्रिया का पालन नहीं किया, जिसके परिणामस्वरूप आपका खाता किसी और को बहाल कर दिया गया। वही चैनल। वही परिणाम।\n\nडेक्सेर्टो, 14 नव. 2025 ↗\n\nमामला फाइल / एचएफबी और आउटसोर्सिंग के आरोप\n\nप्रवेश का तरीका था Steam स्वयं सहायता।Valve लिखित रूप में कहा।\n\nडेक्सेर्टो द्वारा पुनरुत्पादित समर्थन प्रतिक्रिया में, Valve की CS:GO टीम एक समझौता किए गए खाते की जिम्मेदारी स्वीकार करती है। सहायता अनुरोध प्रक्रिया के माध्यम से — इसका अपना चैनल था, न कि कोई फ़िशिंग पेज और न ही उपयोगकर्ता। वस्तुएँ बरामद कर ली गईं और लेनदेन उलट दिए गए, जो कि वह उपाय है जो Valve अन्य पीड़ितों को बताता है कि मौजूद नहीं है। HFB की इन्वेंटरी की रिपोर्ट की गई थी $2,000,000+ उस दिन और $3,000,000+ अनुवर्ती में; Qkss ने $1,000,000+ उसी तरह खो दिया और उसे कुछ भी नहीं मिला।.\n\nसमर्थन उत्तर / डेक्सेर्टो द्वारा पुनरुत्पादित · 21 फरवरी 2023\n“compromised through a support help request, for which the CS:GO team takes responsibility”\nरिपोर्टिंग और पुनरुत्पादित संदेश पढ़ें ↗ संग्रहीत 2025-08-18 ↗\n01 / किस वाल्व ने प्रवेश किया\nइसका अपना सपोर्ट चैनल ही रास्ता था।\n\nयह उत्तर समझौता किए गए खाते और उसके ट्रेड्स के उलटफेर को कवर करता है। Valve ने उन्हें उलट दिया — इसलिए ट्रेड्स उलटे जा सकते थे। मूल प्रमाणीकृत टिकट इस संग्रह में नहीं है।\n\n02 / बर्खास्तगियाँ जो ठीक नहीं कर सकीं\nउसी दरवाजे ने फिर से नवंबर में खुलकर दिखाया कि 2025\n\nठेकेदार ने अपने पूरे Steam-समर्थन स्टाफ को बर्खास्त कर दिया — यह Dexerto के माध्यम से Mzkshow द्वारा रिपोर्ट किया गया था, न कि Valve के किसी कर्मचारी बयान में। तेईस महीने बाद Steam सपोर्ट ने एक अन्य कलेक्टर को लिखा कि \"एक सपोर्ट तकनीशियन जिसने सहायता अनुरोध को संभाला, हमारी प्रक्रिया का पालन करने में विफल रहा, जिसके परिणामस्वरूप आपका खाता किसी और को पुनर्स्थापित कर दिया गया।\" Valve का अपना वाक्य, लगभग उसी चैनल के बारे में।\n\nदूसरा प्रवेश, 14 नव 2025 ↗\n03 / क्या खुला है\nValve ठेकेदार का नाम कभी नहीं बताया\n\nइन स्रोतों से न तो ठेकेदार की पहचान होती है और न ही स्थान का पता चलता है। यह रिपोर्टिंग में कोई कमी नहीं है — यह एक खुलासा है जो Valve ने यह नहीं बताया कि उपयोगकर्ता खातों तक किसकी पहुँच थी।\n\nमामले का समकालीन विवरण ↗\n\nValve ने तीन सवालों का जवाब नहीं दिया है: कौन खाता पुनर्प्राप्ति को ओवरराइड कर सकता है, एक्सेस ऑडिट में क्या पाया गया, और बाद में क्या बदला।\n\nसंरक्षित समर्थन अभिलेखागार में बाद के आरोप\n\n2024 के दो Reddit पोस्ट्स में Mzkshow की आगे की जांचों की जानकारी दी गई है — एक जुलाई का 2024 VAC-बैन हटाने का मामला और एक दिसंबर का 2024 $13,000 इन्वेंटरी मामला। ये अलग-अलग रिपोर्ट की गई घटनाएँ हैं। प्रत्येक में जवाबदेही का सवाल एक ही है: किसके पास ओवरराइड एक्सेस थी, ऑडिट में क्या पाया गया, और क्या बदला।\n\n14 जुलाई 2024 · रिपोर्ट की गई रिकवरी / VAC-प्रतिबंध मामला ↗2 दिसंबर 2024 · $13,000 का इन्वेंटरी मामला रिपोर्ट किया गया ↗संग्रहीत 2025-08-05 ↗दो संरक्षित पोस्ट, स्रोत पंक्तियाँ और हैश ↓\n\n05 / नुकसान का अनुसरण करें\n\nप्रत्येक राशिमामले की ज़रूरत है।\n\nदस मामले, जून 2022 से मार्च 2026. तक। प्रत्येक राशि वही आंकड़ा है जो उसके नामित स्रोत ने प्रकाशित किया है — $6,300,000, $2,000,000+, $1,000,000+, ≈$320,000, ≈$300,000, और €288. तक नीचे। Valve प्रत्येक के लिए लेनदेन लॉग, सत्र रिकॉर्ड और समर्थन ऑडिट ट्रेल रखता है, और इनमें से किसी को भी तैयार नहीं किया है।\n\nसमर्थन चैनल21 जून 2022\n$2,000,000+\nHFB — खेल में सबसे बड़ी इन्वेंटरी\n\nरिपोर्ट की गई इन्वेंटरी मूल्यांकन · फरवरी 2023 के फॉलो-अप में $3मिलियन+ तक बढ़ाया गया\n\nSeven Souvenir Dragon Lores और #1 Blue Gem Karambit, वह चाकू अकेले लगभग $1.26m. तीन साल से निष्क्रिय, ऑथेंटिकेटर अभी भी चालू; ईमेल और पासवर्ड सपोर्ट रिकवरी मार्ग से बदले गए। Valve ने ट्रेड्स को रिवर्स किया — और अपनी जिम्मेदारी लिखित रूप में रखी। रिवर्सल से पहले, रिपोर्ट के अनुसार $200,000+ की आय पहले ही market.csgo.com के माध्यम से निकाली जा चुकी थी, जो नकद और क्रिप्टो में निपटान करता है। रिवर्सल केवल स्किन लौटाता है, न कि उस पैसे को जो पहले ही बैंक में जमा हो चुका हो। रोलबैक में यह भी गड़बड़ी हुई: एक खरीदार ने अपना Souvenir Dragon Lore इन-गेम स्टोरेज यूनिट में छिपा दिया, स्क्रिप्ट अपने ही कंटेनर के अंदर नहीं देख सकी, और Valve ने चोरी को रद्द करते समय $130,000 आइटम की नकल कर दी — जिसे आइटम आईडी और सामुदायिक रिपोर्टिंग से पकड़ा गया, जुलाई में हटा दिया गया 2022, खरीदार को Valve के बजाय BUFF द्वारा रिफंड किया गया।\n\nडेक्सेर्टो, चोरी का दिन ↗\nवॉलेट और खरीदारी07 जुलाई 2022\n>$500\n44 विवादित बाज़ार खरीदें\n\nदावा किया गया वॉलेट खर्च · USD\n\nएक उपयोगकर्ता ने कम-मूल्य के Dota 2 आइटम्स की अनधिकृत खरीदारी और असंतोषजनक समर्थन प्रतिक्रिया की रिपोर्ट की है।\n\nशिकायत और लिंक किए गए स्क्रीनशॉट पढ़ें ↗\nप्लेटफ़ॉर्म उल्लंघन14 अगस्त 2022\n$6,300,000\nCS.Money — 19,000+ बॉट्स से स्किन्स\n\nमूल्यांकन मूल्य · पहला अनुमान $1.6मिलियन\n\nहमलावरों ने मार्केटप्लेस के ट्रेडिंग बॉट्स की मोबाइल-प्रमाणीकरण फ़ाइलों को चुराकर खाली कर दिया, और लूट की एक हिस्सेदारी को प्रसिद्ध व्यापारियों को भेजकर सुराग मिटा दिया। सामुदायिक शोधकर्ताओं ने कुछ ही घंटों में 55 हमलावरों के खातों का नक्शा तैयार कर लिया। Valve ने कुछ भी उल्टा नहीं किया — एक तृतीय-पक्ष साइट Steam के बाहर स्थित है, उसी Steam ने कहा, जिसकी इन्वेंटरी, ट्रेड API और खाता प्रणाली ने चोरी को शुरू से अंत तक अंजाम दिया।\n\nसमकालीन विवरण पढ़ें ↗\nसमर्थन चैनलरिपोर्ट किया गया 21 फरवरी 2023\n$1,000,000+\nक्यूकेएसएस — वही दरवाज़ा, वही अभिनेता, उल्टा जवाब\n\nरिपोर्ट की गई इन्वेंटरी मूल्यांकन\n\nइसे उसी तरह लिया गया जैसे HFB को लिया गया था, उसी अभिनेता द्वारा, उसी सपोर्ट हेल्प रिक्वेस्ट के माध्यम से। HFB को आठ महीने पहले ही पूरी तरह से बहाल कर दिया गया था। Qkss को नहीं। प्रकाशित रिकॉर्ड में दर्शकों की संख्या को छोड़कर दोनों मामलों को कुछ भी अलग नहीं करता।\n\nMzkshow जांच पर डेक्सेर्टो ↗\nसमर्थन चैनलरिपोर्ट किया गया फरवरी 2023\n≈ $320,000\nअंदरूनी व्यापार स्वयं — इसका एक वर्ष\n\nलगभग एक वर्ष से अधिक की आय · यह इन्वेंटरी मूल्यांकन नहीं है\n\nसपोर्ट-साइड एक्सेस ने 15 साल पुराने खाता इतिहास तक पहुँच बनाई: पहली CD कुंजी, पहला ईमेल, पहला कार्ड — ठीक वही सबूत जो रिकवरी प्रक्रिया मांगती है। डेटाबेस रखने वाला हमेशा उस बहस में जीतता है जो खाता रखने वाले के खिलाफ होती है। एक चोरी किया गया M4A4 Howl, iBUYPOWER और Titan Katowice 2014 होलोस $35,000 में बेचे गए और अंततः NAVI के b1t के पास पहुँच गए, जिसे इसका पता लगाने का कोई तरीका नहीं था। ठेकेदार का जवाब था कि Steam सपोर्ट में काम करने वाले सभी कर्मचारियों को निकाल दिया जाए।\n\nउसी जांच पर एस्कोरन्यूज़ ↗\nवॉलेट और खरीदारी09 दिसं 2023\n€288\nदो-चरणीय सुरक्षा के बावजूद वॉलेट की चोरी\n\nट्रस्टपायलट · स्रोत अनुक्रमणिका 16\n\nसमीक्षक ने एक हैक किए गए खाते और मार्केट खर्च में मदद करने से इनकार की सूचना दी है। निर्यात के पास कोई व्यक्तिगत समीक्षा URL नहीं है।\n\nस्रोत उत्पत्ति की जाँच करें ↗\nखाता वसूली02 दिसं 2024\n$13,000\n\"मैटवे\" — बर्खास्तगी के दो साल बाद\n\nलेखक का सूची आकलन\n\nउस व्यक्ति को पुनर्प्राप्ति दी गई जिसने ऐसा खाता डेटा प्रदान किया जिसे मालिक स्वयं भी मेल नहीं खा सकता था। वही रास्ता, वही परिणाम, जब ठेकेदार ने अपनी Steam सहायता डेस्क को साफ़ कर दिया था।\n\nसंरक्षित आरोप पढ़ें ↗\nखाता वसूली09 मई 2025\n≈ $10,000\nकिसी और के टिकट से रिकवरी\n\nदावा किया गया वस्तु हानि · अमेरिकी डॉलर\n\nएक क्यूबेक उपयोगकर्ता का आरोप है कि सपोर्ट ने किसी अन्य व्यक्ति के अनुरोध पर पासवर्ड रीसेट किया और खाते की सुरक्षा हटा दी।\n\nपहले व्यक्ति की शिकायत पढ़ें ↗\nसमर्थन चैनल13 नवंबर2025\n≈ $300,000\nHawkeye337 — और Valve का दूसरा लिखित स्वीकारोक्ति\n\nपूर्ण काटोविचे 2014 होलो संग्रह\n\nहमलावर ने 1 बिटकॉइन की मांग की और इसे नष्ट करने के लिए संग्रह को Negevs पर स्क्रैप करना शुरू कर दिया। Steam सपोर्ट की प्रतिक्रिया: \"एक सपोर्ट तकनीशियन जिसने सहायता अनुरोध को संभाला, हमारी प्रक्रिया का पालन करने में विफल रहा, जिसके परिणामस्वरूप आपका खाता किसी और को पुनर्स्थापित कर दिया गया।\" पहले स्वीकारोक्ति के तेतीस महीने बाद, वही दरवाज़ा। X पर थ्रेड ट्रेंड होने के कुछ ही घंटों में पुनर्स्थापित किया गया। Qkss के पास वह दर्शक वर्ग नहीं था।\n\nडेक्सेर्टो, 14 नव. 2025 ↗\nवॉलेट और खरीदारी29 मार्च 2026\n$50\nअनधिकृत टॉप-अप और उपहार में दिए गए गेम\n\nट्रस्टपायलट · स्रोत अनुक्रमणिका 290\n\nसमीक्षक ने अनधिकृत खर्च और असफल रिफंड अनुरोधों का आरोप लगाया है। व्यक्तिगत समीक्षा URL निर्यात में अनुपस्थित है।\n\nस्रोत उत्पत्ति की जाँच करें ↗\n\nप्रत्येक स्रोत द्वारा रिपोर्ट की गई जिम्मेदारी और राशियाँ जस की तस बनी हुई हैं।Valve इन सभी मामलों के लेनदेन लॉग, सत्र रिकॉर्ड और समर्थन ऑडिट ट्रेल रखता है। उन्हें प्रस्तुत करें। एक संरक्षित Reddit पोस्ट इस प्रश्न का समाधान नहीं करती — Valve के अपने रिकॉर्ड ही करते हैं।\n\nसंग्रह / जाँच के बाद\n\n231,829 बिक्री पर खातेValve हर एक के लिए लॉग्स रखता है।\n354 → 201\nट्रस्टपायलट रिकॉर्ड्स\n\n153 डुप्लिकेट पंक्तियाँ हटा दी गईं। व्यक्तिगत समीक्षा URL निर्यात में संरक्षित नहीं किए गए।\n\n231,829\nSteam खाता सूचीकरण\n\n33,509 स्वयं-पंजीकृत के रूप में वर्गीकृत; कलेक्टर के स्टीलर लेबल के तहत 198,320। लिस्टिंग पूरी हुई बिक्री नहीं हैं।\n\nसंग्रह ऑडिट ↓स्रोत संग्रह खोजें ↗",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "भाग II — खाते तक पहुँच, आउटसोर्स समर्थन और प्रवर्तन"
          },
          {
            "level": 2,
            "id": null,
            "text": "स्वचालन नेएक कागज़ी निशान"
          },
          {
            "level": 3,
            "id": null,
            "text": "आर्चीस्टीमफार्म"
          },
          {
            "level": 2,
            "id": null,
            "text": "कौन सी कुंजीहम किसकी बात कर रहे हैं?"
          },
          {
            "level": 3,
            "id": null,
            "text": "व्यक्तिगत वेब API कुंजी"
          },
          {
            "level": 3,
            "id": null,
            "text": "प्रकाशक वेब API कुंजी"
          },
          {
            "level": 3,
            "id": null,
            "text": "ओपनआईडी / सत्र टोकन"
          },
          {
            "level": 3,
            "id": null,
            "text": "API स्वचालन एक से अधिक कुंजी का उपयोग कर सकता है।"
          },
          {
            "level": 2,
            "id": null,
            "text": "अभी भी खेल रहा हूँ।पहले से ही उजागर।"
          },
          {
            "level": 3,
            "id": "session-hidden-title",
            "text": "विश्वास वेबसाइट से पहले शुरू होता है।"
          },
          {
            "level": 2,
            "id": null,
            "text": "यह वस्तु दुर्लभ हो सकती है।सीमा बनी रहती है।"
          },
          {
            "level": 2,
            "id": null,
            "text": "डेटा की जिम्मेदारी सौंपी गई।पहुँच के लिए उत्तरदायी।"
          },
          {
            "level": 3,
            "id": null,
            "text": "मापदंड सार्वजनिक था।"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve डेस्क को आउटसोर्स किया — और कहा भी"
          },
          {
            "level": 3,
            "id": null,
            "text": "पहला प्रवेश"
          },
          {
            "level": 3,
            "id": null,
            "text": "दूसरा प्रवेश"
          },
          {
            "level": 3,
            "id": null,
            "text": "प्रवेश का तरीका था Steam स्वयं सहायता।Valve लिखित रूप में कहा।"
          },
          {
            "level": 4,
            "id": null,
            "text": "इसका अपना सपोर्ट चैनल ही रास्ता था।"
          },
          {
            "level": 4,
            "id": null,
            "text": "उसी दरवाजे ने फिर से नवंबर में खुलकर दिखाया कि 2025"
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve ठेकेदार का नाम कभी नहीं बताया"
          },
          {
            "level": 2,
            "id": null,
            "text": "प्रत्येक राशिमामले की ज़रूरत है।"
          },
          {
            "level": 3,
            "id": null,
            "text": "HFB — खेल में सबसे बड़ी इन्वेंटरी"
          },
          {
            "level": 3,
            "id": null,
            "text": "44 विवादित बाज़ार खरीदें"
          },
          {
            "level": 3,
            "id": null,
            "text": "CS.Money — 19,000+ बॉट्स से स्किन्स"
          },
          {
            "level": 3,
            "id": null,
            "text": "क्यूकेएसएस — वही दरवाज़ा, वही अभिनेता, उल्टा जवाब"
          },
          {
            "level": 3,
            "id": null,
            "text": "अंदरूनी व्यापार स्वयं — इसका एक वर्ष"
          },
          {
            "level": 3,
            "id": null,
            "text": "दो-चरणीय सुरक्षा के बावजूद वॉलेट की चोरी"
          },
          {
            "level": 3,
            "id": null,
            "text": "\"मैटवे\" — बर्खास्तगी के दो साल बाद"
          },
          {
            "level": 3,
            "id": null,
            "text": "किसी और के टिकट से रिकवरी"
          },
          {
            "level": 3,
            "id": null,
            "text": "Hawkeye337 — और Valve का दूसरा लिखित स्वीकारोक्ति"
          },
          {
            "level": 3,
            "id": null,
            "text": "अनधिकृत टॉप-अप और उपहार में दिए गए गेम"
          },
          {
            "level": 2,
            "id": null,
            "text": "231,829 बिक्री पर खातेValve हर एक के लिए लॉग्स रखता है।"
          },
          {
            "level": 3,
            "id": null,
            "text": "ट्रस्टपायलट रिकॉर्ड्स"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam खाता सूचीकरण"
          }
        ],
        "links": [
          "https://phishdestroy.io/live-intel/?category=steam",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/lzt.market.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-evidence-lzt.json",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://github.com/JustArchiNET/ArchiSteamFarm/blob/main/ArchiSteamFarm/ArchiSteamFarm.csproj",
          "https://github.com/JustArchi",
          "https://github.com/renovate[bot]",
          "https://github.com/JustArchi-ArchiBot",
          "https://github.com/dependabot-preview[bot]",
          "https://github.com/renovate-bot",
          "https://github.com/actions-user",
          "https://github.com/dependabot-support",
          "https://github.com/Abrynos",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/automation-map.json",
          "https://phishdestroy.io/steam_dossier/hi/output_steam_network/network.html",
          "https://phishdestroy.io/steam_dossier/output_steam_network/raw_data.json",
          "https://partner.steamgames.com/doc/webapi_overview/auth",
          "http://web.archive.org/web/20260915025812/https://partner.steamgames.com/doc/webapi_overview/auth",
          "https://partner.steamgames.com/doc/webapi/ISteamUserAuth",
          "http://web.archive.org/web/20260829124950/https://partner.steamgames.com/doc/webapi/ISteamUserAuth",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "http://web.archive.org/web/20260924181824/https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://store.steampowered.com/privacy_agreement/",
          "https://store.steampowered.com/oldnews/19618",
          "http://web.archive.org/web/20260809125516/https://store.steampowered.com/oldnews/19618",
          "https://kotaku.com/valve-explains-why-steam-customer-service-is-still-terr-1736988223",
          "http://web.archive.org/web/20250711004653/https://kotaku.com/valve-explains-why-steam-customer-service-is-still-terr-1736988223",
          "https://www.dexerto.com/counter-strike-2/valve-saves-hacked-cs2-player-threatened-with-ransom-over-300000-of-rare-stickers-3283135/",
          "https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "http://web.archive.org/web/20250818113925/https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "https://lis-skins.com/ru/blog/krupneisaia-mosenniceskaia-sxema-v-istorii-steam/",
          "https://www.reddit.com/r/cs2/comments/1e38jo4/stealing_accounts_and_removing_vac_bans_a_new/",
          "https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "http://web.archive.org/web/20250805141942/https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/outsourcing-archive-records.json",
          "https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "https://escorenews.com/en/csgo/news/44087-valve-steam-support-employee-accused-of-selling-inactive-accounts-inventories-worth-six-figures-b1t-has-one-of-these-skins",
          "https://phishdestroy.io/steam_dossier/hi/PART2_RESEARCH.md",
          "https://www.reddit.com/r/GlobalOffensive/comments/1h56shi/steam_support_is_stealing_accounts/",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/part2-quality-review.json",
          "https://phishdestroy.io/steam_dossier/hi/steam_evidence_archive.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/hi/investigation_part2.content.json",
      "export_json_sha256": "454c1c9717b5d8155d15ff75373f6bfbc678e51a5787dc46014767e6efba93dd"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "hi/legal_analysis.html",
      "language": "hi",
      "title": "उनकी शर्तें, आपके अधिकार — द Steam डोजियर",
      "source_url": "https://phishdestroy.io/steam_dossier/hi/legal_analysis",
      "source_html_sha256": "1137e70ce09aead48b3c27a39a5551c480ba8368ca56251c756de6278491964a",
      "exported_at": "2026-09-29T00:22:44.287Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "legal_analysis.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/hi/legal_analysis.pdf?v=print-20260929-v5",
        "sha256": "ebcf9b58c25d5c9467bc05442dd0df0b8d8057d2543896e7f5f8cdd73c06694e",
        "bytes": 414187,
        "pages": 6
      },
      "integrity": {
        "signed_object": "legal_analysis.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "legal_analysis.content.json.asc",
        "digest_file": "legal_analysis.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify legal_analysis.content.json.asc legal_analysis.content.json",
          "sha256sum -c legal_analysis.content.json.sha256"
        ]
      },
      "content": {
        "text": "कानूनी और आर्थिक रिपोर्ट\nकानूनी विश्लेषण — सेवा की शर्तें और नियामक अनुपालन\n\nउनकी शर्तें। आपके अधिकार\n\nयह अनुभाग क्या प्रमाणित करता है\n\nयह फोरेंसिक कानूनी ऑडिट प्रमुख नियामक अधिकार क्षेत्रों में Valve कॉर्पोरेशन और Steam उपयोगकर्ताओं के बीच संविदात्मक विषमता का आकलन करता है। यह दर्शाता है कि रद्द करने योग्य सदस्यता लाइसेंस कैसे वैधानिक उपभोक्ता स्वामित्व को छीनता है, डिजिटल पुनर्विक्रय समाप्ति पर यूरोपीय न्यायालय की न्यायशास्त्र का विश्लेषण करता है, और डिजिटल सेवा अधिनियम (DSA) तथा GDPR के अनुच्छेद 15. के तहत अनुपालन की जांच करता है। यह विश्लेषण दिखाता है कि स्वचालित प्रवर्तन तंत्र बिना सार्थक अपील के कैसे कार्य करते हैं, जबकि प्लेटफ़ॉर्म बाज़ार शुल्क प्रत्येक पीयर लेनदेन से आर्थिक मूल्य व्यवस्थित रूप से निकालते हैं।\n\n← कार्यकारी ब्रीफिंग पर वापस\n\nयह रिपोर्ट 'Steam' के घोषित प्लेटफ़ॉर्म नियमों और उपभोक्ता की स्थिति के बीच के अंतर का कानूनी, आर्थिक और तकनीकी विश्लेषण प्रस्तुत करती है: कम सहारा के साथ स्वचालित प्रवर्तन, और डिजिटल संपत्तियों पर व्यापक कॉर्पोरेट नियंत्रण। आंकड़े उनके स्रोत के साथ बताए गए हैं; जहाँ किसी आंकड़े का प्राथमिक रिकॉर्ड तक पता नहीं चल पाया, उसे छोड़ दिया गया है।\n\nवेक्टर 1\n\n'स्वामित्व' को एक रद्द करने योग्य लाइसेंस से प्रतिस्थापित करना, ताकि समझौते के तहत डिजिटल संपत्तियों को वापस लिया जा सके।\n\nवेक्टर 2\n\nस्वचालित प्रवर्तन (VACNet) जो प्रतिबंध लगाता है Steam समर्थन करता है जिसे राज्य पलट नहीं सकते।\n\nवेक्टर 3\n\nखाता और संपत्ति नियंत्रण, एक 15% CS2 मार्केट फ़ीस (5%Steam + 10% प्रकाशक शुल्क) के साथ संयुक्त, जो प्रत्येक पुनर्विक्रय पर इकोसिस्टम से मूल्य घटाती है।\n\nअसमानता की शर्तें\nदेयता छूट और रद्द करने योग्य लाइसेंस\n2.1 \"सदस्यता\" मॉडल बनाम संपत्ति अधिकार\n\nSteam सदस्यता अनुबंध की धारा 2 उपयोगकर्ताओं को केवल एक व्यक्तिगत, गैर-अनन्य, गैर-हस्तांतरणीय और रद्द करने योग्य लाइसेंस. समझौते के तहत, Valve किसी भी समय खातों को समाप्त कर सकता है, और अप्रयुक्त Steam वॉलेट शेष राशि जब्त की जा सकती है।\n\n2.2 रिफंड का भ्रम बनाम ईयू उपभोक्ता अधिकार निर्देश\nकानूनी ढांचा\tरिफंड तंत्र\tसीमा\nEU Consumer Rights Directive\tUnconditional 14-day right of withdrawal on digital content\tWaived if download begins with explicit consumer consent\nSteam SSA\t14 days / under 2 hours played\tValve may deny at its discretion for \"abuse\"\nमूल्यांकन\n\nValve यह यूरोपीय संघ के 14--दिवसीय वैधानिक वापसी अधिकार को अपनी \"14-दिनों / 2-घंटों\" की खिड़की तक सीमित करता है, जिसे उत्पाद का मूल्यांकन होने से पहले डाउनलोड के समय स्वीकार किया जाता है। यह नीति वैधानिक अधिकार को संकुचित करती है—विस्तारित नहीं करती; क्या यह कानूनी रूप से ऐसा करती है, यह सक्षम प्राधिकारी का प्रश्न है, न कि यहाँ कोई निष्कर्ष।\n\nमुकदमा\nद्वितीयक बाजार और प्रतिस्पर्धा-विरोधी कानून\nयूएफसी क्यू च्वाइसिर बनाम Valve — फ्रांस\n2019\nपेरिस न्यायालय: अधिकारों के समापन का सिद्धांत डिजिटल खेलों पर लागू होता है — पुनर्विक्रय वैध है\nअक्टूबर2022\nपेरिस अपीलीय न्यायालय ने फैसले को पलटा।\n23 अक्टूबर2024\nकोर डे कैसाशन (सुप्रीम कोर्ट): वीडियो गेम सूचना-समाज निर्देश के तहत \"जटिल कृतियाँ\" हैं, सॉफ़्टवेयर नहीं। डिजिटल पुनर्विक्रय प्रतिबंधित. Valve प्रचलित है।\nवुल्फायर गेम्स एंटीट्रस्ट — संयुक्त राज्य अमेरिका (Valve Antitrust Litigation, संख्या 2:21-cv-00563 में)\n\nValve के प्लेटफ़ॉर्म मोस्ट-फ़ेवर्ड-नेशन (PMFN) प्रावधान डेवलपर्स को किसी अन्य प्लेटफ़ॉर्म पर Steam कीज़ को सस्ते में बेचने से रोकता है। प्रतिस्पर्धी स्टोर — यहाँ तक कि वे जो Valve की 30% के विरुद्ध 12% कमीशन लेते हैं — भी इस बचत को उपभोक्ताओं तक नहीं पहुँचा सकते।\n\n336कुल Valve कर्मचारी (2021)। स्रोत: अनसील्ड डिस्कवरी।\n79Steam प्लेटफ़ॉर्म का प्रबंधन करने वाले कर्मचारी। स्रोत: अनसील्ड डिस्कवरी।\n$3.5Mप्रति कर्मचारी शुद्ध आय। स्रोत: अनसील्ड डिस्कवरी।\n\nअनसील्ड डिस्कवरी रिकॉर्ड दिखाते हैं $8.5B सकल राजस्व 2021 में 336 के कर्मचारियों पर। 79-व्यक्तिSteam टीम 373,000+ दैनिक सपोर्ट टिकटों को आउटसोर्स्ड, स्वचालित कॉल सेंटरों के माध्यम से संभाला।\n\nसील न किया गया डॉकेट प्रदर्श · W.D. वाश. मामला 2:21-CV-00563आंतरिक खोज ज्ञापन\n\nटिम स्विनी (सीईओ, एपिक गेम्स) से गेब न्यूएल तक: Steam अभी भी कुल राजस्व का 30% क्यों ले रहा है, जबकि भुगतान प्रसंस्करण 2–5% है और CDN बैंडविड्थ $0.002/GB है? यदि आप Steam पर शीर्ष 25 गेम्स को हटा दें, तो मेरा दांव है कि Valve ने अधिकांश अगले 1,000 से डेवलपर्स की तुलना में अधिक लाभ कमाया।\n\nस्कॉट लिंच (सीओओ, Valve कॉर्पोरेशन) का गेब न्यूएल को आंतरिक फॉरवर्ड: क्या तुम पागल हो, भाई?\n\nशपथ-पत्र खंडन (ब्लूमबर्ग, 2026): नियम 30(b)(1) के तहत गवाही में, गेब न्यूएल ने गवाही दी कि Valve की अन्य प्लेटफ़ॉर्मों पर तीसरे पक्ष के सॉफ़्टवेयर डेवलपर्स को कीमतें निर्धारित करने की कोई नीति या प्रथा नहीं है। वाददाताओं ने न्यूवेल का सामना आंतरिक Valve मेमो के साथ किया, जो प्रतिस्पर्धी स्टोरों पर कम कीमत रखने वाले डेवलपर्स के खिलाफ सक्रिय मूल्य निगरानी और सूची से हटाने की धमकियों को साबित करते थे। मार्च के अंत में 2026, में संघीय न्यायालय ने Valve की सारांश निर्णय याचिका को खारिज कर दिया, जिससे 32,000-डेवलपर वर्ग कार्रवाई जूरी परीक्षण के लिए भेजी गई।\nनवंबर2024\n\nवर्ग कार्रवाई के लिए प्रमाणित ~32,000 डेवलपर्स जिसने जनवरी से कमीशन का भुगतान किया2017, और एक समानांतर उपभोक्ता सामूहिक मुकदमा।\n\nदावा किए गए नुकसान\n\n$3.1B\nअमेरिकी प्रतिस्पर्धा-विरोधी कानून के तहत तिगुना जुर्माना = $9.3B संभावित जोखिम\n\nजून 2026: एक नए मुकदमे में आरोप लगाया गया है कि माइक्रोसॉफ्ट और Valve ने पीसी गेम वितरण में प्रतिस्पर्धा को दबाने के लिए एक कार्टेल समझौता किया।\n\nवित्तीय अपराध एवं एएमएल औपचारिक प्रवेश\nValve आधिकारिक स्वीकारोक्ति: विश्वव्यापी धोखाधड़ी परिसमापन (28, अक्टूबर 2019)\n\n28 अक्टूबर 2019,Valve ने नए खरीदे गए काउंटर-स्ट्राइक कंटेनर कीज़ के ट्रेड और मार्केटप्लेस पुनर्विक्रय को आधिकारिक रूप से समाप्त कर दिया। अपनी औपचारिक सार्वजनिक घोषणा (blog.counter-strike.net/2019/10/26113Valve कॉर्पोरेशन ने लिखित रूप में स्वीकार किया कि उसने जो आभासी अर्थव्यवस्था तैयार की थी, वह एक अंतरराष्ट्रीय मनी लॉन्ड्रिंग क्लियरिंगहाउस बन चुकी थी:\n\nअतीत में, हमने जो अधिकांश की ट्रेड देखे, वे वैध ग्राहकों के बीच थे। हालांकि, हाल ही में विश्वव्यापी धोखाधड़ी नेटवर्क ने अपने मुनाफे को नकदी में बदलने के लिए CS:GO कीज़ का उपयोग करना शुरू कर दिया है। इस समय, बाजार में ट्रेड या बिक्री के लिए आने वाली लगभग सभी कीज़ को धोखाधड़ी से प्राप्त माना जाता है।\n\nनियामक संदर्भ: 2016 यह स्वीकारोक्ति वाशिंगटन स्टेट गैंबलिंग कमीशन (WSGC) द्वारा Valve को दिए गए औपचारिक अल्टीमेटम और Valve के जनरल काउंसल कार्ल क्वैकेनबुश द्वारा 23 स्किन-जुआ डोमेन (जिसमें CSGO Lotto, CSGOLounge और OPSkins शामिल हैं) के लिए जारी किए गए जुलाई के 'सीज़ एंड डिस्ट' आदेशों के बाद हुई, जब आपराधिक जुआ जांच ने प्लेटफ़ॉर्म संचालन को खतरे में डाल दिया।\n\nअधिकार क्षेत्र\nरूस में एक अधिकार-धारक, जो उपयोगकर्ता की पहुँच से बाहर है।\n\nसब्सक्राइबर समझौता 'Valve' को एक ऐसे पक्ष के रूप में प्रस्तुत करता है जिस पर कम ही दायित्व हैं और जिसे कोई भी नहीं पहुँच सकता: ताले स्थायी हैं, अपीलें खारिज कर दी जाती हैं, और 'प्रतिबंधित क्षेत्रों' के एक ही नियम के तहत पूरे क्षेत्रों से पहुँच वापस ले ली जाती है। इसके विपरीत, 'Valve' तब क्या करता है जब उसके अपने वाणिज्यिक हित उस क्षेत्राधिकार में दांव पर हों, जिसे वह अन्यथा कठिन मानता है।\n\nValve वि. टच स्किन्स — मुकदमे-पूर्व बौद्धिक संपदा दावा, रूस\n1 सितंबर2026\nValve, रूसी कानून फर्म के माध्यम से मेलिंग, वोइटिशकिन और पार्टनर्स, के संचालकों को मुकदमे से पहले की मांग पत्र भेजता है टच स्किन्स, रूसी डाक और ईमेल द्वारा, एक बड़े CS2 स्किन-चेंजर।\nकारण\nआरोपित उल्लंघनों के तीन समूह: सॉफ़्टवेयर पर विशिष्ट अधिकार; हथियार, चाकू और दस्ताने स्किन्स की दिखावट पर अधिकार; तथा ईValve के ट्रेडमार्क। ऑपरेटरों का आचरण जानबूझकर और दीर्घकालिक बताया गया है।\nमांग\nतुरंत संचालन बंद करें और सभी बुनियादी ढांचे को हटा दें — सॉफ़्टवेयर का स्रोत कोड, वेबसाइटों और सोशल-मीडिया पृष्ठों — ऐसा न करने पर Valve को रूसी अदालत में मुकदमा करने का अधिकार सुरक्षित है। महत्वपूर्ण मौद्रिक मुआवजा और मामले को संदर्भित करने के लिए आपराधिक मूल्यांकन के लिए कानून-प्रवर्तन.\nपरिणाम\nपत्र प्राप्त करने के बाद, प्लेटफ़ॉर्म ने घोषणा की कि वह बंद हो रहा है। इसे रूस में एक स्किन-चेंजर डेवलपर के खिलाफ कानूनी उपकरणों के Valve के पहले उपयोग के रूप में रिपोर्ट किया गया।\n\nडेटा-माइनर मैक्सिम \"गेबफॉलोअर\" पोलेताएव (X, ~11, सितंबर2026) और रूसी गेमिंग प्रेस द्वारा रिपोर्ट किया गया। यह एक पूर्व-मुकदमे का दावा है, दायर किया गया मुकदमा नहीं; कोई डॉकेट नंबर सार्वजनिक नहीं है। यहां इसे रिपोर्ट के रूप में लिया गया है, न कि न्यायालय के अभिलेख के रूप में। स्रोत: dota2.ru संचित 2026-09-24 ↗ · शाज़ू.\n\nवही क्षेत्राधिकार, दूसरी दिशा\n\nValve रूसी कानूनी और नियामक प्रणाली से अपरिचित नहीं है। यह रॉस्कोम्नाडज़ोर के अनुरूपनियामक की मांग पर इसने प्रतिबंधित सामग्री रखने वाले260और Steam समुदाय पृष्ठ हटा दिए, और रोस्कोमनadzor ने सार्वजनिक रूप से कहा है कि Steam कानून की आवश्यकताओं को पूरा करता है। रूस का \"लैंडिंग\" कानून (संघीय कानून 236-एफजेड, जो 2022 से प्रभावी है, रूसी उपयोगकर्ताओं को सेवा देने वाले बड़े विदेशी इंटरनेट प्लेटफ़ॉर्मों को स्थानीय उपस्थिति स्थापित करने और Roskomnadzor के साथ एक संपर्क खाता खोलने की आवश्यकता है।Valve न केवल उस नियामक के हटाने के आदेशों का पालन करता है, बल्कि अब अपनी स्किन्स को बौद्धिक संपदा के रूप में संरक्षित करने के लिए रूसी वकीलों और रूसी न्यायालयों की धमकी का भी सहारा लेता है।\n\nतो प्लेटफ़ॉर्म ठीक वहीं पहुँचने योग्य, सक्षम और अपने अधिकारों का दावा करने वाला है जहाँ इसकी आय का सवाल है। इसके विपरीत उपयोगकर्ता है: प्रतिबंधित क्षेत्र में एक भुगतान करने वाले ग्राहक को बताया जाता है कि संबंध समाप्त हो गया है, समुदाय तक पहुँच तब तक लॉक रहती है जब तक कि 2038, टिकट बंद नहीं हो जाता, और ऐसा कोई मंच मौजूद नहीं है जहाँ इस निर्णय को परखा जा सके — वे मेरे पैसे लेने और मेरे लेन-देन को संसाधित करने में बहुत खुश थे।, उसी खाते का रिफंड उसी ईरानी आईपी से एक साल पहले ही मंजूर हो चुका था (r/pcgaming, 4 अगस्त 2026; में और प्रवर्तन पत्र कार्ड-अर्थव्यवस्था प्रदर्शनीValve एक स्किन की रक्षा के लिए राष्ट्रीय कानूनी प्रणाली की पूरी व्यवस्था का सहारा लेता है; यह उस उपयोगकर्ता को, जिसने स्किन खरीदी थी, कोई प्रक्रिया ही नहीं देता।\n\nValve यह उसी क्षेत्राधिकार को अपना मानता है जिसमें वह कार्य कर सकता है और जिसके भीतर वह पालन कर सकता है, जब भी दांव पर Valve का हित हो — रूसी वकील, रूसी अदालतों का खतरा, रोस्कोम्नद्ज़ोर के हटाने के आदेशों का जवाब — जबकि उस बाज़ार और हर दूसरे बाज़ार के उपयोगकर्ताओं के प्रति अपनी ज़िम्मेदारियों को पूरी तरह से किसी भी प्रक्रिया से परे मानता है। जहाँ तक इसकी आय का सवाल है, यह एक अधिकार-धारक है और जहाँ उपयोगकर्ताओं के अधिकारों का सवाल आता है, यह एक पहुँच से बाहर की पार्टी है।\n\nस्रोत: TASS (RKN: Steam अनुपालन करता है) · संघीय कानून 236-एफजेड.\n\nकानूनी अवसरवाद\nमध्यस्थता प्रावधान की आत्मसमर्पण\n2023 — हमला\n\nकानूनी फर्मों (ज़ाइगर एलएलसी, मेसन एलएलपी) ने सोशल मीडिया के माध्यम से हजारों उपयोगकर्ताओं को भर्ती किया और एक साथ दसियों हजार व्यक्तिगत मध्यस्थता दावे दायर किए।\n\nValve का एक्सपोजर\n\n$225M+\nमामले की योग्यता के आधार पर सुनवाई होने से पहले, गैर-वापसी योग्य मध्यस्थता दाखिल शुल्क में। अमेरिकन आर्बिट्रेशन एसोसिएशन (AAA) उपभोक्ता आर्बिट्रेशन नियमों और मास आर्बिट्रेशन पूरक अनुसूचियों के तहत गणना की गई। Zaiger LLC और Mason LLP द्वारा प्रतिनिधित्व किए गए दावेदारों ने ~75,000 व्यक्तिगत मध्यस्थता मांगें दायर कीं Valve कॉर्पोरेशन के खिलाफ (प्रतिस्पर्धा-विरोधी दावों के समानांतर) वुल्फायर गेम्स एलएलसी एवं अन्य बनाम Valve कॉर्पोरेशन, मुकदमा संख्या 2:21-(cv-00563-), JCC, W.D (वॉश.). AAA उपभोक्ता शुल्क अनुसूचियों के तहत, व्यावसायिक प्रतिवादी प्रत्येक व्यक्तिगत मामले के लिए ~$3,000+ की गैर-वापसी योग्य प्रशासनिक केस फीस और मध्यस्थ नियुक्ति जमा राशि का भुगतान करता है (75,000 फाइलिंग्स × $3,000 = ~$225मिलियन अग्रिम प्रक्रियात्मक देनदारियों में). टेक मास आर्बिट्रेशन एक्सपोजर पर ब्लूमबर्ग लॉ और रॉयटर्स की कानूनी रिपोर्टें देखें (2023–2024).\n\nअवधि\tएसएसए विवाद निवारण तंत्र\tनिरीक्षित प्रभाव\tपरिणाम\nBefore Sep 2024\tMandatory individual arbitration + class-action waiver\tIndividual litigation becomes economically irrational for users\tMass arbitration → $225M fee threat\nAfter Sep 2024\tDisputes in King County, WA courts only\tArbitration costs are avoided; cases consolidate in a single forum\tClass actions now possible\nनिष्कर्ष\n\nदस वर्षों से अधिक समय तक SSA ने उपयोगकर्ताओं को व्यक्तिगत मध्यस्थता के पक्ष में जूरी परीक्षण का अधिकार त्यागने के लिए बाध्य किया। बड़ी संख्या में दायर की गई मध्यस्थता याचिकाओं के कारण यह तंत्र SValve के लिए आर्थिक रूप से महंगा हो गया, इसलिए विवादों को किंग काउंटी की अदालतों में भेजने के लिए SSA में संशोधन किया गया। इस बदलाव को बिना किसी सार्थक ऑप्ट-आउट के पेश किया गया; स्वीकृति न देने पर खाते को हटाकर खरीदे गए डिजिटल संपत्तियों तक पहुंच खो देना ही एकमात्र विकल्प था।\n\nअल्गोरिद्मिक प्रवर्तन\nVACNet, दोषारोपण की पूर्वधारणा, और झूठे सकारात्मक\nअक्टूबर2023 — AMD एंटी-लैग+\n\nएक AMD ड्राइवर अपडेट (v23.10.1) ने CS2 में Anti-Lag+ को सक्रिय किया, जिसने गेम DLL फ़ंक्शंस को इंटरसेप्ट किया। VAC ने इसे चीट-कोड इंजेक्शन के रूप में वर्गीकृत किया और Valve के हस्तक्षेप से पहले हजारों वैध उपयोगकर्ताओं पर स्थायी प्रतिबंध लगा दिए।\n\nदिसंबर 2023 — उच्च डीपीआई\n\n10,000 से अधिक DPI वाले खिलाड़ियों को कैमरा तेजी से घुमाने पर स्थायी प्रतिबंध मिल गए। VACNet भौतिक माउस मूवमेंट और \"स्पिनबॉट\" चीट में अंतर नहीं कर सका।\n\nसमर्थन श्रेणी\tदावा किया गया प्रतिक्रिया समय\tवास्तविक परिणाम\nRefund requests\t50 min – 1.5 hr\tAutomatic approval (<14 days, <2 hours played)\nAccount security / recovery\t3–12 hours\tDepends on documentation provided\nContesting a VAC ban\tForm response\tComplete refusal. Support cannot reverse VAC decisions. The ban is permanent.\nआधिकारिक Valve नीति\n\nVAC प्रतिबंध स्थायी हैं, गैर-वार्ता योग्य हैं, और इन्हें Steam समर्थन द्वारा हटाया नहीं जा सकता।\n\nवही सपोर्ट चैनल जो प्रतिबंध लगाता है, समीक्षा से इनकार भी करता है: Steam सपोर्ट कहता है कि वह VAC के निर्णय को पलट नहीं सकता। उपयोगकर्ता के लिए, एल्गोरिदम का निर्णय ही अंतिम परिणाम है।\n\nपुनर्विक्रय का अर्थशास्त्र\nआभासी संपत्तियों पर नियंत्रण और पुनर्विक्रय शुल्क\n15% CS2 मार्केट फ़ी — प्रत्येक पुनर्विक्रय पर मूल्य हटाया जाता है\nआवृत्ति\tखरीदार की शेष राशि\tविक्रेता को प्राप्त होता है\tजल गया (15%)\n1\t$100.00\t$85.00\t$15.00\n2\t$85.00\t$72.25\t$12.75\n3\t$72.25\t$61.41\t$10.84\n10\t$23.16\t$19.68\t~$3.47\nTotal\t$100 → dust\tValve collects the 15% fee on each resale. Users must add new money to keep trading.\nCS2 ट्रेड-अप नियम में बदलाव — अक्टूबर2025\n\nबिना किसी पूर्व सूचना के, Valve ने CS2 ट्रेड-अप अनुबंध नियमों में बदलाव किया ताकि Covert-गुणवत्ता वाली वस्तुओं के बदले दुर्लभ चाकुओं और दस्तानों की गारंटीशुदा प्राप्ति संभव हो सके। चाकुओं की कीमतें गिर गईं, Covert वस्तुओं की कीमतें तेज़ी से बढ़ गईं, और पूरे बाज़ार में घबराहट में बिक्री शुरू हो गई।\n\nValve द्वारा घोषित सुरक्षा SSA की धारा 7 है — प्लेटफ़ॉर्म नियमों में बदलाव के लिए कोई देयता नहीं। उपयोगकर्ता एक ऐसी अर्थव्यवस्था में जोखिम उठाते हैं, जहाँ Valve के नियम बिना किसी सूचना या मुआवजे के बदल सकते हैं। रिपोर्ट किए गए बाजार-व्यापी नुकसान का आकार विवादित है और प्राथमिक स्रोत के बिना यहाँ नहीं बताया गया है।\n\nयूरोपीय नियामक प्रतिक्रिया\nयूओकेआईके, डीएसए, और डिजिटल निष्पक्षता अधिनियम\nयूओकेआईके — पोलैंड, मई 2024\n\nपोलैंड की प्रतिस्पर्धा प्राधिकरण (UOKiK) ने Valve कॉर्पोरेशन और पांच घरेलू गेम प्रकाशकों/वितरकों के खिलाफ कथित मूल्य-निर्धारण, प्रतिबंधात्मक मूल्य-समानता शर्तों, और भू-प्रतिबंध (geo-blocking) प्रथाओं के संबंध में औपचारिक एकाधिकार-विरोधी कार्यवाही शुरू की, जिससे पोलिश उपभोक्ताओं को डिजिटल गेम्स के लिए पड़ोसी EEA बाजारों की तुलना में 20% अधिक भुगतान करना पड़ा। प्रतिस्पर्धा-विरोधी जांच के हिस्से के रूप में, UOKiK के निरीक्षकों और पुलिस ने घरेलू साझेदार प्रकाशकों और वितरकों के पोलिश परिसरों पर तड़के छापे मारे और साक्ष्य निरीक्षण किया (Valve की सहायक कंपनियों के कार्यालयों पर नहीं, क्योंकि Valve का कोई पोलिश इकाई नहीं है)। संभावित वैधानिक जुर्माना: वार्षिक कारोबार का 10% तक। स्रोत: UOKiK की आधिकारिक घोषणा, \"UOKiK के अध्यक्ष ने Valve और गेम निर्माताओं के खिलाफ कार्यवाही शुरू की\", 2024 मई.\n\nडिजिटल सेवा अधिनियम (डीएसए)\n\nस्वचालित मॉडरेशन में पारदर्शिता आवश्यक है।Steam VACNet के लिए कोई फाल्स-पॉजिटिव/फाल्स-नेगेटिव डेटा प्रकाशित नहीं करता है, और इसके सपोर्ट चैनल में कहा गया है कि VAC के निर्णय उलट नहीं किए जा सकते।\n\nडिजिटल निष्पक्षता अधिनियम — 2026\n\nअपेक्षित प्रावधान: सशुल्क सामग्री तक टिकाऊ पहुँच, अधिकार-छूट के बिंदु पर डार्क पैटर्नों पर प्रतिबंध, डिजिटल संपत्तियों में संपत्ति अधिकारों की मान्यता, और स्थायी इन्वेंटरी जब्ती से सुरक्षा।\n\nनिष्कर्ष\nनियमों और रिकॉर्ड के बीच दस्तावेजीकृत अंतराल\n1\n\nस्वामित्व का अंतर उपयोगकर्ता एक ऐसे लाइसेंस के लिए पूरी कीमत चुकाते हैं जिसे समझौते के तहत Valve रद्द कर सकता है। फ्रांस की सर्वोच्च न्यायालय (अक्टूबर 2024) ने निर्णय दिया कि डिजिटल पुनर्विक्रय संरक्षित नहीं है, और इस स्थिति को कानून में स्थापित कर दिया।\n\n2\n\nअल्गोरिद्मिक प्रवर्तन। VACNet ने झूठे प्रतिबंध लगाए (AMD ड्राइवर, उच्च-DPI घटनाएँ)। Steam सपोर्ट कहता है कि यह VAC के निर्णय को उलट नहीं सकता, इसलिए एल्गोरिदम ही अंतिम निर्णयकर्ता है।\n\n3\n\nशुल्कों की बचत 15% CS2 मार्केट फ़ीस (5% Steam + 10% प्रकाशक शुल्क) प्रत्येक पुनर्विक्रय पर मूल्य घटाती है, और प्लेटफ़ॉर्म नियम बिना सूचना के बदल सकते हैं; SSA के तहत ऐसे परिवर्तनों के लिए Valve की देयता से इनकार किया जाता है।\n\n4\n\nमध्यस्थता खंड हटाया गया। एसएसए ने सितंबर 2024, में अनिवार्य मध्यस्थता को हटा दिया, जब बड़े पैमाने पर दायर की गई फाइलिंग्स ने Valve को लगभग $225मिलियन शुल्क के जोखिम में डाल दिया। उपयोगकर्ताओं को इस बदलाव से कोई सार्थक ऑप्ट-आउट नहीं मिला।\n\n5\n\nचयनात्मक क्षेत्राधिकार। Valve रूसी वकील (मेलिंग, वोइटिश्किन एंड पार्टनर्स) को नियुक्त किया और टच स्किन्स के खिलाफ रूसी न्यायालय में मुकदमा चलाने की धमकी दी, जबकि उसी बाजार के उपयोगकर्ताओं के प्रति अपनी जिम्मेदारियों को किसी भी न्यायिक प्रक्रिया से परे माना।Valve तब अधिकार-धारक के रूप में कार्य करता है जब उसके व्यावसायिक हित जुड़े होते हैं, और तब एक ऐसी पहुँच से परे पार्टी के रूप में कार्य करता है जहाँ उपयोगकर्ता के अधिकार होने चाहिए।\n\n← भाग I: प्रॉक्सी बाईपास और जुआभाग II: पहुँच और जवाबदेही →\n\nकानूनी स्रोतों और मुकदमे के अभिलेखों को उनके मूल प्रकाशकों और भंडारों का हवाला दिया गया है। अंतर्निहित दस्तावेजों पर किसी भी स्वामित्व का दावा नहीं किया जाता।",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "कानूनी विश्लेषण — सेवा की शर्तें और नियामक अनुपालन"
          },
          {
            "level": 2,
            "id": null,
            "text": "देयता छूट और रद्द करने योग्य लाइसेंस"
          },
          {
            "level": 3,
            "id": null,
            "text": "2.1 \"सदस्यता\" मॉडल बनाम संपत्ति अधिकार"
          },
          {
            "level": 3,
            "id": null,
            "text": "2.2 रिफंड का भ्रम बनाम ईयू उपभोक्ता अधिकार निर्देश"
          },
          {
            "level": 2,
            "id": null,
            "text": "द्वितीयक बाजार और प्रतिस्पर्धा-विरोधी कानून"
          },
          {
            "level": 3,
            "id": null,
            "text": "यूएफसी क्यू च्वाइसिर बनाम Valve — फ्रांस"
          },
          {
            "level": 3,
            "id": null,
            "text": "वुल्फायर गेम्स एंटीट्रस्ट — संयुक्त राज्य अमेरिका (Valve Antitrust Litigation, संख्या 2:21-cv-00563 में)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve आधिकारिक स्वीकारोक्ति: विश्वव्यापी धोखाधड़ी परिसमापन (28, अक्टूबर 2019)"
          },
          {
            "level": 2,
            "id": null,
            "text": "रूस में एक अधिकार-धारक, जो उपयोगकर्ता की पहुँच से बाहर है।"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve वि. टच स्किन्स — मुकदमे-पूर्व बौद्धिक संपदा दावा, रूस"
          },
          {
            "level": 3,
            "id": null,
            "text": "वही क्षेत्राधिकार, दूसरी दिशा"
          },
          {
            "level": 2,
            "id": null,
            "text": "मध्यस्थता प्रावधान की आत्मसमर्पण"
          },
          {
            "level": 2,
            "id": null,
            "text": "VACNet, दोषारोपण की पूर्वधारणा, और झूठे सकारात्मक"
          },
          {
            "level": 2,
            "id": null,
            "text": "आभासी संपत्तियों पर नियंत्रण और पुनर्विक्रय शुल्क"
          },
          {
            "level": 3,
            "id": null,
            "text": "15% CS2 मार्केट फ़ी — प्रत्येक पुनर्विक्रय पर मूल्य हटाया जाता है"
          },
          {
            "level": 3,
            "id": null,
            "text": "CS2 ट्रेड-अप नियम में बदलाव — अक्टूबर2025"
          },
          {
            "level": 2,
            "id": null,
            "text": "यूओकेआईके, डीएसए, और डिजिटल निष्पक्षता अधिनियम"
          },
          {
            "level": 2,
            "id": null,
            "text": "नियमों और रिकॉर्ड के बीच दस्तावेजीकृत अंतराल"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/hi/#briefing-heading",
          "https://dota2.ru/news/67707-valve-cerez-uristov-napravila-krupnoj-rossijskoj-skincendzer-platforme-trebovanie-o-prekrasenii-deatelnosti/",
          "http://web.archive.org/web/20260924181657/https://dota2.ru/news/67707-valve-cerez-uristov-napravila-krupnoj-rossijskoj-skincendzer-platforme-trebovanie-o-prekrasenii-deatelnosti/",
          "https://shazoo.ru/2026/09/12/190508/valve-cerez-rossiiskix-iuristov-dobilas-zakrytiia-krupnogo-skinceindzera-dlia-cs2",
          "https://www.reddit.com/r/pcgaming/comments/1vf24lu/warning_to_all_gamersexpats_steam_took_my_money/",
          "https://phishdestroy.io/steam_dossier/hi/card_economy.html#asymmetry",
          "https://tass.ru/obschestvo/23235387",
          "https://base.garant.ru/401414628/",
          "https://uokik.gov.pl/postepowanie-wyjasniajace-w-sprawie-valve-i-dystrybutorow-gier",
          "https://phishdestroy.io/steam_dossier/hi/",
          "https://phishdestroy.io/steam_dossier/hi/investigation_part2.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/hi/legal_analysis.content.json",
      "export_json_sha256": "40841af3bf1c15943c249f419381db5bc71330ec1ef73a31f5ac06ccc716c3c3"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "hi/license_disclaimer.html",
      "language": "hi",
      "title": "लाइसेंस · अधिकार · अस्वीकरण — PhishDestroy",
      "source_url": "https://phishdestroy.io/steam_dossier/hi/license_disclaimer",
      "source_html_sha256": "c9f8e59da8a737f5e902a5a17bb3d52a993678ebfb7ac1c97123dc1acc992341",
      "exported_at": "2026-09-29T00:22:45.892Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "license_disclaimer.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/hi/license_disclaimer.pdf?v=print-20260929-v5",
        "sha256": "1adcb3f7d715f4570b533bdbc161162370b04ed810a9fbefebd2e48968259ab0",
        "bytes": 333410,
        "pages": 9
      },
      "integrity": {
        "signed_object": "license_disclaimer.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "license_disclaimer.content.json.asc",
        "digest_file": "license_disclaimer.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify license_disclaimer.content.json.asc license_disclaimer.content.json",
          "sha256sum -c license_disclaimer.content.json.sha256"
        ]
      },
      "content": {
        "text": "मछली नष्ट करोफोरेंसिक जांच · Valve / Steam\nलाइसेंस · अधिकार · अस्वीकरण\nलाइसेंस और कानूनी अस्वीकरण — सार्वजनिक डोमेन समर्पण\n\nसभी अधिकार मानवता के हवाले हो गए।\n\nयह अनुभाग क्या प्रमाणित करता है\n\nयह उपकरण सार्वजनिक डोमेन समर्पण (CC01.0Universal) और MIT सॉफ़्टवेयर लाइसेंसिंग शर्तों को स्थापित करता है, जो PhishDestroy Steam Dossier को नियंत्रित करती हैं। सभी फोरेंसिक निष्कर्ष, साक्ष्य डेटासेट, नेटवर्क ग्राफ़ और विश्लेषणात्मक पद्धतियाँ अपरिवर्तनीय रूप से सार्वजनिक डोमेन में रखी गई हैं, ताकि विश्वभर में नियामक, कानूनी और शैक्षणिक उपयोग के लिए कोई प्रतिबंध न हो।\n\n← कार्यकारी ब्रीफिंग पर वापस\n\nPhishDestroy इस सामग्री पर हर अधिकार छोड़ देता है — इसे पुन:प्रकाशित करें, बेचें, उस पर अपना नाम डालें। इसके बाद एक ही आवाज़ में लिपटे दो दस्तावेज़ हैं: Valve को एक खुला पत्र, जैसा हम वास्तव में लिखते हैं, और एक औपचारिक त्यागपत्र जो उस प्राधिकरण के लिए लिखा गया है जो इस सामग्री को आगे ले जाएगा।\n\nजांच · Valve कॉर्पोरेशन / Steamसार्वजनिक संस्करण — कोई समाप्ति नहीं, कोई वापसी नहीं\nछूट दी गई\nखंड Iलाइसेंस — असल कानूनी हिस्सा, लेकिन मानवीय\n\nPhishDestroy इस सामग्री पर हर अधिकार छोड़ देता है। शून्य। खत्म। हो गया। आप इसे पुन: प्रस्तुत कर सकते हैं, बेच सकते हैं, उस पर अपना नाम डाल सकते हैं, अपने बॉस पर टैटू बनवा सकते हैं, जो चाहें। कोई श्रेय आवश्यक नहीं, कोई डीएम नहीं चाहिए, कोई धन्यवाद कार्ड की उम्मीद नहीं।\n\nएक असली नियम (हाँ, सिर्फ एक)\n\nयह तय करने का तुम्हारा कोई अधिकार नहीं है कि तुम आतंकवादी हो।\n\nयदि आप रूस या किसी भी OFAC-प्रतिबंधित देश के उपयोगकर्ता हैं — यह सामग्री आपके लिए नहीं है। कोई छेद नहीं। अपने प्रतिबंधों का आनंद लें।\n\nऔर अगर आपने मॉस्को में बैठकर अपना Steam क्षेत्र तुर्की में बदल लिया — आपकी रचनात्मक भूगोल के लिए बधाई। आप अभी भी रूसी ही हैं। प्रतिबंध अभी भी लागू हैं। यही तो असल बात है।\n\nखंड IIयह क्या है और यह क्यों मौजूद है\n\nहम औसत Valve कर्मचारी की तुलना में Valve के बारे में अधिक प्रकाशित करेंगे। यह घमंड नहीं है। बस हम यहीं पहुँचे हैं।\n\nहम यहाँ कैसे पहुँचे? मज़ेदार कहानी है: Steam ने मूलतः हमें बनाया। इसने हमें अपने ठगों, अपने सपोर्ट टिकटों, अपने प्रतिबंध टालने वाले इकोसिस्टम पर पाला—और अब हम यहाँ हैं। कोई रंजिश नहीं। सच में काव्यात्मक है।\n\nजो लोग अभी तक उत्पत्ति की कहानी नहीं पढ़े हैं — हम पहले ही मिल चुके हैं Valve के बेहद महँगे यूरोपीय वकीलों से (टेलर वेसिंग, क्योंकि आपने पूछा):\n\nhttps://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d संग्रहीत 2026-08-21 ↗\n\nमनमोहक मुलाकात। खासकर उनकी प्रति घंटा दर को देखते हुए।\n\nक्या Valve को पता था? हाँ। क्या Taylor Wessing को पता था? लगभग निश्चित रूप से हाँ। लेकिन जब आप इतने अमीर हों, तो कानून ज़रूरत से ज़्यादा एक दिखावा होते हैं, है ना?\n\nवास्तव में, यह ही पूरा जवाब है।\n\nSteam हमने वर्षों तक स्कैमर्स का शिकार किया है। हमेशा जानबूझकर नहीं — कभी-कभी स्कैमर्स बस संबद्धता के कारण 'Valve' की उंगलियों के निशान उन पर लग जाते थे। हम इसमें नाटकीयता नहीं लाना चाहते। हम सटीक होना चाहते हैं। ईमानदारी से कहें तो हमारे लिए नाटकीय होने से ज्यादा मुश्किल यही है — बस हम इसी तरह लिखते हैं।\n\nक्या यह कोई संघर्ष है?\n— नहीं।\n\nक्या इसे हल किया जा सकता है?\n— हाँ। लेकिन हम कोई एनडीए साइन नहीं कर रहे हैं और हम कुछ भी टूटे-फूटे पैसे के लिए बग बाउंटी नहीं कर रहे हैं।\n\nहमने सार्वजनिक रूप से इसके बारे में लिखने से पहले स्पूफिंग की समस्या ठीक होने के लिए 4 साल से अधिक इंतजार किया। क्योंकि अगर हमने पहले इसके बारे में लिखा होता, तो Steam अपना छोटा-सा पीड़ित चेहरा दिखाकर \"सक्रिय खतरा!\" चिल्लाता और हमें जेब खर्च के बराबर कुछ पैसे देकर एक ऐसा दस्तावेज़ साइन करवा देता जो हमें हमेशा के लिए उनकी कानूनी संपत्ति बना देता। नहीं, धन्यवाद।\n\n(साथ ही: Valve स्वयं NDA का उल्लंघन करता है। उनके अपने कर्मचारी भी करते हैं। जो शीर्ष के करीब हैं। लेकिन हाँ, चलिए हमारे बारे में बात करते हैं।)\n\nखंड IIIValve के लिए खुला पत्र — सच में, इसे पढ़ो\n\nValve: यदि आप इस डोमेन को हटाना चाहते हैं, तो हमें ईमेल करें। उस बातचीत के लिए बाहरी वकील की आवश्यकता नहीं है।\n\nअनभिज्ञों के लिए: डॉ. पैट्रिक के पास एबरडीन विश्वविद्यालय से अंतर्राष्ट्रीय वाणिज्यिक कानून में मास्टर ऑफ लॉज़ की डिग्री है और — रुकिए — उन्होंने आईटी कानून में अपने डॉक्टोरल शोधप्रबंध को सचमुच पूरा किया है। उन्होंने हाल ही में टेलर वेसिंग में पार्टनर की उपाधि प्राप्त की, जो एक ऐसी फर्म है जिसका पूरा व्यापार मॉडल Valve जैसी कंपनियों को अत्यधिक राशि का बिल भेजकर मामलों को तब तक खींचना है जब तक दूसरी पक्ष के पास पैसा या धैर्य खत्म न हो जाए।\n\nहम उस पर दोष नहीं लगाते। प्रति घंटे भुगतान करने वाले अमीर और दोषी ग्राहक — यह एक ठोस करियर कदम है। हम बस यह नहीं सोचते कि आपको इसे फंड करना चाहिए।\n\nडील (ओपन ऑफर, वकीलों की जरूरत नहीं)\n\nडोमेन ही एकमात्र चीज़ है जिसे Valve वास्तविक रूप से पहुँच सकता है। जांच, रेफरल और संबंधित संसाधन पहले से ही गति में हैं — वे डोमेन के साथ या उसके बिना जारी रहते हैं।\n\nयदि आप डोमेन चाहते हैं:\n\nअपने आईटी कानून विशेषज्ञों को एक उचित मूल्य निर्धारित करने दें।\n\n50% SEAL फाउंडेशन को जाता है।\n\nहम डोमेन खत्म कर देते हैं। कोई ड्रामा नहीं। कोई अदालत नहीं। हो गया।\n\nयह कोई धमकी नहीं है। यह उस एक चीज़ के लिए एक सीधा-सादा प्रस्ताव है जो वास्तव में आपकी पहुँच में है। आपको इसे किसी अन्य तरीके से नहीं मिलेगा — यह बस स्थिति की संरचना है।\n\nक्या हम सीधे तौर पर \"Valve\" को \"नुकसान\" पहुँचाएंगे? शायद नहीं, इस तरह से कि उन्हें आर्थिक रूप से महसूस हो। हम भ्रम में नहीं हैं। लेकिन हम ईमानदारी से, खुले तौर पर, प्रभाव की चाहत के बिना ऐसा करेंगे — क्योंकि हमें प्रभाव की जरूरत नहीं है। हमें दुनिया को वह दिखाना है जो हमेशा सार्वजनिक रूप से दिखाई देता था, अगर आप उसे देखने में पर्याप्त समय लगाते।\n\nहमारे पास 5 वर्षों का अभिलेखागार है। Valve के वकीलों ने डिस्कवरी में जो दिखाया — वह डेटा जिसे सपोर्ट एजेंट देख सकते हैं, फिंगरप्रिंट्स, कागजी निशान जिन्हें उन्होंने सचमुच हमें सौंपा — वह पर्याप्त है। हमें इसे कच्चा लीक करने की जरूरत नहीं है।\n\nकौन क्या पाता है\n\nनियामक मूल दस्तावेज़ प्राप्त करते हैं।\n\nशोधकर्ता और पत्रकार संशोधित संस्करण प्राप्त करते हैं (पीड़ित की रिपोर्टें, बच्चों के लॉगिन और Valve की आकर्षक समर्थन टिप्पणी स्पष्ट कारणों से हटा दी गई हैं)।\n\nप्रभावित खातों में नाबालिग भी शामिल थे और उन्हें सूचित नहीं किया गया था। यह निष्कर्ष नियामक पैकेज में पीड़ितों की रिपोर्टों और प्रमाण-पत्रों को हटाकर रखा गया है, क्योंकि यह किसी लेख में नहीं बल्कि डेटा-संरक्षण प्राधिकरण के समक्ष प्रस्तुत किया जाना चाहिए।\n\nसाथ ही, Valve — इससे पहले कि आप यह तय करें कि इसे कैसे खेलना है, हम कुछ स्पष्ट करना चाहते हैं: PhishDestroy एक समुदाय है, कोई व्यक्ति नहीं। आपने यह तब सीखा जब आपने समुदाय से बात करने की जहमत उठाए बिना ही कानूनी पत्राचार समुदाय को संबोधित किया — सिर्फ डेटा के लिए इसका इस्तेमाल किया और खातों को प्रतिबंधित कर दिया।\n\nइस समुदाय का Valve के साथ कोई टकराव नहीं है। हमने इसकी तलाश नहीं की थी। आपके द्वारा पाले गए ठग हमें ढूंढ निकले। हमने उन्हें ब्लॉक कर दिया। और हम यहाँ हैं।\n\nखंड III-Bसंबंधित संसाधन — विशेष रूप से Steam के लिए एक नोट\n\nहम प्रवर्धन संरचना के बारे में स्पष्ट रहना चाहते हैं, क्योंकि यह मौजूद नहीं है ऐसा दिखावा करना बेईमानी होगी।\n\nPhishDestroy, जैसा कि हम सामुदायिक स्थिति को समझते हैं, के पास कम से कम दो सहयोगी संसाधन हैं जो इस सामग्री को उठाकर आगे बढ़ाएंगे।\n\nव्यावहारिक रूप से इसका क्या मतलब है:\n\nवे ओवरलैपिंग विषय-वस्तु पर अपने-अपने दृष्टिकोण से काम करते हैं।\n\nवे स्वतंत्र हैं — वे हमारी दिशा नहीं मानते, हम उनकी नहीं मानते। सामान्य विषय तो एक ही है, लेकिन कार्यप्रणाली अलग है।\n\nवे भाग 1. पर सक्रिय नहीं होंगे। वे देख रहे हैं।\n\nयदि Valve साइट को हटाने का निर्णय नहीं लेता है:\n\nउम्मीद करें कि वे भाग 2 या भाग 3. के बाद सामने आएँगे।\n\nवे हमारे काम से जो कुछ उपयोगी होगा, उसे लेंगे, उसे अपने काम से पूरक करेंगे, और अपनी लेखकता में प्रकाशित करेंगे।\n\nयह बिल्कुल वैसी ही चीज़ है जिसके लिए धारा 1 में दिया गया लाइसेंस बनाया गया है: सामग्री जहाँ ज़रूरत हो वहाँ पहुँचती है, पूरक की जाती है, और प्रसारित की जाती है — और न तो हम और न ही वे एक-दूसरे को श्रेय देने के लिए बाध्य हैं।\n\n(वकीलों के लिए एक पीएस जो दायित्व की श्रृंखलाओं के बारे में सोच रहे हैं: ऐसी कोई श्रृंखलाएँ नहीं हैं। ये संसाधन हमारी निर्देशन, हमारे वित्त पोषण या हमारे डेटा को प्राप्त नहीं करते हैं। वे जो सार्वजनिक रूप से उपलब्ध है, उसे पढ़ते हैं और अपने निष्कर्ष निकालते हैं। ठीक वैसे ही जैसे आप कर सकते थे।)\n\nहम यह डराने के लिए नहीं कह रहे हैं। हम यह इसलिए कह रहे हैं ताकि Valve की ओर से रणनीति बनाने वाले को वास्तविक सूचना वातावरण कैसा दिखता है, इसकी सटीक जानकारी हो।\n\nएक स्रोत जो हमारी सामग्री को इकट्ठा करता है और उसमें पूरकता लाता है, वह एक कहानी होती है। दो स्रोत स्वतंत्र रूप से ऐसा करते हैं और समान निष्कर्ष पर पहुंचते हैं, तो यह एक पैटर्न होता है। पैटर्न वही होते हैं जिन्हें नियामक नोटिस करते हैं।\n\nखंड IVपैसा, पाबंदियाँ, पूरा तमाशा\n\nSteam द्वारा जुआ साइटों और ठगों को प्रतिबंधित करने के बारे में बात यह है: यह प्रवर्तन नहीं है, यह राजस्व वसूली है।Valve पैसे जेब में रखता है, अपने हाथ साफ कर लेता है, फिर मंच पर जाकर सभी को पोकेमॉन कार्ड्स और बेसबॉल के बारे में एक पवित्र कहानी सुनाता है।\n\nजहाँ समर्थन-पक्ष के समझौते दस्तावेजीकृत हैं — जिसमें फरवरी में Valve का लिखित स्वीकारोक्ति, सहायता अनुरोधों के माध्यम से समझौता किए गए उच्च-मूल्य खातों की जिम्मेदारी लेने वाला 2023, और $320k के अंदरूनी व्यापार के बाद Dexerto और Escorenews द्वारा रिपोर्ट की गई ठेकेदार कर्मचारियों की बर्खास्तगी शामिल है।भाग II §04 · मुख्य फ़ाइल §14.1) — ये प्रकाशित स्वीकारोक्तियों और खोजी पत्रकारिता पर आधारित हैं। सहायक कर्मचारियों द्वारा जुआ संचालित करने या प्रतिबंध हटाने के लिए प्रतिशत लेने जैसी बिना प्रमाणित अफवाहें सार्वजनिक अभिलेखों में स्थापित नहीं हैं और यहां शामिल नहीं की गई हैं।\n\nइस बीच Valve ने 2017. में स्किन्स को ठीक से ट्रैक करने की क्षमता खत्म कर दी। उन्होंने अपने ही फोरम पर भी इस पर चर्चा की और इसे \"जुआ-विरोधी उपाय\" कहा — जबकि स्किन जुआ इकोसिस्टम वर्षों तक Steam के इन्फ्रास्ट्रक्चर के माध्यम से अरबों का लेन-देन करता रहा। शानदार ब्रांडिंग।\n\nहम यह साबित करने जा रहे हैं कि:\n\nस्किन्स मोनेरो से भी अधिक गुमनाम हैं।\n\nएक पेरूवियन कार्टेल ने कथित तौर पर पैसे की आवाजाही के लिए डोटा के2की स्किन्स का इस्तेमाल किया।\n\nSteam कार्यक्षमता की दृष्टि से यह प्रतिबंधों को बाईपास करने वाली एक मशीन है, जिसकी कीमत \"ट्रेडिंग कार्ड्स\" में लगभग7अरब डॉलर है (हाँ, उन्होंने वास्तव में अभियोजक से ट्रेडिंग कार्ड्स ही कहा था)\n\nहमारे पास स्किन्स वाली चीज़ पर एक वीडियो है। आप इसे देखेंगे।\n\nहम यह भी जानते हैं:\n\nरेडिट की मध्यस्थता प्रभावित होती है Valve\n\nतृतीय-पक्षीय Steam डेटा अवसंरचना (जैसे steamid.uk) एक निजी व्यक्ति द्वारा संचालित है (एमएसआर्ट) जिनका जुड़ा हुआ भाई-बहन प्रतिबंध-सूची परियोजना (steambans.com पुस्तकालय) एक पुष्टि किए गए Valve समुदाय के मॉडरेटर द्वारा सह-प्रशासित है (किलहिनस्टिंक्ट_) — प्लेटफ़ॉर्म प्रतिबंधों के स्वतंत्र ऑडिट को पूरी तरह से Valve की कक्षा के भीतर ही छोड़ देना (देखें कार्ड अर्थव्यवस्था §08)\n\nजिस चीज़ को वे नियंत्रित नहीं कर सकते, उसे वे प्रतिबंधित कर देते हैं।\n\nValve: अगर आप बेवकूफ़ बने रहने का नाटक करते रहेंगे — कोई बात नहीं। आपका सुरक्षित बंदरगाह नोट कर लिया गया है। Google Analytics वैसे भी आपके उपयोगकर्ताओं के आईपी पतों को गुमनाम कर देता है। हम देखते हैं कि क्या-क्या हटाया जाता है। हम बस इसे आपके वकीलों के लिए पर्याप्त सस्ते में साबित नहीं कर सकते। अभी तक।\n\nखंड Vमैलवेयर वाली बात — हाँ, हम इसका ज़िक्र कर रहे हैं\n\nआइए घटनाओं के क्रम के बारे में बेरहमी से स्पष्ट हो जाएँ, क्योंकि यह बिल्कुल उजागर कर देता है कि आप कौन हैं।\n\nहम इस गेम में मौजूद भेद्यता को सार्वजनिक रूप से प्रकट नहीं कर रहे हैं। हम इसे Steam पर रिपोर्ट नहीं कर रहे हैं। इस कार्यक्रम के लिए एक एनडीए की आवश्यकता है, और एक पर हस्ताक्षर करने से हम प्रभावित उपयोगकर्ताओं को यह बताने से वंचित हो जाएंगे कि उनके खातों के साथ क्या हुआ। उन लोगों को प्रकट करना जिन्होंने वे खाते खो दिए हैं, और नियामकों को, इस कार्य का उद्देश्य है; गोपनीयता समझौता इसके साथ असंगत है।\n\nअसल में जो हुआ वह यह है: यह भेद्यता सही हलकों में लगभग एक खुली गुप्त बात है। हमें पक्की जानकारी है कि स्वतंत्र सुरक्षा शोधकर्ताओं ने पहले ही पूरा एक्सप्लॉइट सीधे Steam सपोर्ट के सामने रख दिया है। वह हिस्सा पूरा हो चुका है। आपको अपने ही निष्प्रभावी चैनलों के माध्यम से आधिकारिक रूप से चेतावनी दी जा चुकी है।\n\nऔर Valve ने क्या किया? बिल्कुल कुछ नहीं। क्योंकि Valve के लिए सुरक्षा का मतलब मुनाफा नहीं है — असल में, यह बिल्कुल उल्टा है। सुरक्षा एक लागत केंद्र है। जब तक कोई खतरा गंभीर स्तर तक नहीं पहुँचता और सार्वजनिक पीआर में विनाशकारी संकट नहीं खड़ा कर देता, Valve इसे तात्कालिक नहीं मानता।\n\nतो हम क्या कर रहे हैं? हम जनता को बता रहे हैं कि यह मौजूद है, क्योंकि \"Valve को एक प्रणालीगत मैलवेयर खतरे के बारे में पता है और वह सक्रिय रूप से कुछ भी नहीं करने का विकल्प चुनता है\" वर्तमान में इसे पढ़ रहे नियामकों के लिए एक महत्वपूर्ण डेटा बिंदु है।\n\nयह खेल विशाल है। हम इसे यहाँ नाम नहीं दे रहे हैं। लेकिन यह समझें:\n\nयह कोई तुच्छ CS:GO स्क्रिप्ट-किडी बकवास नहीं है जहाँ सर्वर आपसे \"ड्राइवर इंस्टॉल\" करने के लिए कहता है। यह विनाशकारी है।\n\nयह एक Unturned-स्तर का दुःस्वप्न है: सर्वर से कनेक्ट होते ही शून्य-क्लिक RCE। आप एक सर्वर में शामिल होते हैं। आप कुछ भी क्लिक नहीं करते। आप कुछ भी डाउनलोड नहीं करते। कनेक्शन स्वयं ही हमला का क्षेत्र है, और आपकी मशीन पूरी तरह से समझौता हो चुकी है। सच कहें तो, RCE ड्रॉप करना और Valve के विश्वसनीय डिजिटल प्रमाणपत्रों पर सवारी करके स्थानीय एंटीवायरस को बायपास करना अब Steam पर कोई नई बात नहीं रही। यह व्यावहारिक रूप से आपके इकोसिस्टम की एक अंतर्निहित सुविधा बन चुका है।\n\nValve पहले से ही जानता है कि यह मौजूद है। लेकिन वे अपनी पसंदीदा कायर कानूनी चूक पर निर्भर हैं: चूंकि यह गेम तकनीकी रूप से किसी तीसरे पक्ष द्वारा विकसित किया गया है, Valve हाथ धो लेता है। वे गेम वितरित करते हैं, भुगतान संसाधित करते हैं, बुनियादी ढांचे की मेजबानी करते हैं, लेकिन जब एक जीरो-क्लिक RCE उनके लाखों उपयोगकर्ताओं को खतरे में डालता है, तो उनका रुख होता है: \"हमारा गेम नहीं, हमारी जिम्मेदारी नहीं।\"\n\nजब यह अनिवार्य रूप से फूट पड़ेगा, तब तीसरे पक्ष का डेवलपर गोली खाएगा, और Valve खुद को जिम्मेदार प्लेटफ़ॉर्म दिखाकर समाधान में \"सहायता\" करने का ढोंग करते हुए बच निकलेगा। क्लासिक Valve कायरता। हमने यह चाल पहले भी देखी है।\n\nहम इसे रिकॉर्ड पर रख रहे हैं ताकि नियामक, अभियोजक और पत्रकार ठीक से समझ सकें कि Valve सक्रिय मैलवेयर से कैसे निपटता है: तीसरे पक्ष के डेवलपर्स के पीछे छिपकर, एनडीए के तहत चुप्पी साधने के आदेश जारी करके, और खिलाड़ियों को असहाय छोड़कर।\n\nखुले पत्र का अंतऔपचारिक रजिस्टर शुरू होता है\nप्राधिकरण के लिए औपचारिक रजिस्टर\nघोषणाउपयोग और अधिकारों के संबंध में\n\nPhishDestroy परियोजना और साइबर सुरक्षा गठबंधन\n\nयह घोषणा इस रेफरल सेट में प्रत्येक प्रस्तुति और प्रत्येक प्रदर्शनी के साथ संलग्न रहती है। यह किसी भी प्राधिकरण, न्यायालय, नियामक, अभियोजक, शोधकर्ता, पत्रकार या प्रभावित व्यक्ति के नाम संबोधित है, जिसके हाथों में यह सामग्री पहुँचती है।\n\n1. उपयोग पर कोई शर्तें नहीं हैं।\n\n1.1 इस संदर्भ में गठबंधन द्वारा उत्पादित सभी सामग्री — तथ्यों के विवरण, विश्लेषण, इसके द्वारा रचित प्रदर्श, उपकरण, और निष्कर्ष — बिना किसी अधिकार के आरक्षण के जारी की जाती है।\n\n1.2 कोई भी बिना पूछे और हमें सूचित किए बिना कर सकता है:\n\nइसकी, संपूर्ण या आंशिक रूप से, पुनःउत्पादित करना;\n\nइसे अनुकूलित, संपादित, पुनर्लिखित, पुनर्गठित या सुधारें;\n\nइसे अनुवाद करें;\n\nयह बताए बिना कि यह उद्धृत किया गया है, इसका उद्धरण करना;\n\nइसे आधिकारिक दस्तावेजों, निष्कर्षों, निर्णयों, दलीलों, रिपोर्टों या प्रेस सामग्री में शामिल करना;\n\nउसे प्राप्तकर्ता का अपना कार्य या प्राप्तकर्ता के अपने निष्कर्षों के रूप में प्रस्तुत करना;\n\nइसे कच्चे माल के रूप में उपयोग करें और बाकी को फेंक दें;\n\nऔर इसे उसी शर्तों पर किसी और को दे दें।\n\n1.3 आर्यनकरण आवश्यक नहीं है और न ही मांगा जाता है। गठबंधन का नाम लेने, उद्धृत करने, श्रेय देने, धन्यवाद करने, परामर्श करने या सूचित करने की आवश्यकता नहीं है। यदि इस संदर्भ से प्राप्त सामग्री किसी प्राधिकरण की सहायता करती है और गठबंधन का कभी उल्लेख नहीं होता, तो यह पूरी तरह से संतोषजनक परिणाम है, और गठबंधन इसे पहले से ही स्पष्ट कर देता है ताकि यह प्रश्न ही न उठे।\n\n1.4 यदि दूसरी ओर कोई प्राधिकरण गठबंधन को स्रोत के रूप में उद्धृत करना अधिक सुविधाजनक समझता है, तो वह ऐसा करने के लिए स्वतंत्र है। यह विकल्प पूरी तरह से प्राप्तकर्ता का है और दोनों में से किसी भी विकल्प का कोई परिणाम नहीं होता।\n\n1.5 यह एक छूट है, लाइसेंस प्रस्ताव नहीं। इसे स्वीकार करने की आवश्यकता नहीं है, यह कोई दायित्व नहीं लगाता, और इसका उल्लंघन नहीं किया जा सकता। Coalition द्वारा प्रकाशित सॉफ़्टवेयर को अलग से MIT लाइसेंस के तहत जारी किया जाता है; अनुसंधान और निष्कर्षों को अधिकतम हद तक सार्वजनिक डोमेन में जारी किया जाता है, और जहाँ कोई क्षेत्राधिकार छूट की अनुमति नहीं देता, वहाँ Coalition उसी प्रभाव के लिए एक अपरिवर्तनीय, विश्वव्यापी, रॉयल्टी-मुक्त लाइसेंस प्रदान करता है।\n\n2. यह व्यावहारिक रूप से क्यों मायने रखता है, और केवल शिष्टाचार के रूप में ही नहीं।\n\n2.1 कोई प्राधिकरण बाहरी पक्ष द्वारा प्रदान की गई सामग्री पर भरोसा करने में उचित रूप से हिचकिचा सकता है, इस डर से कि वह उस पक्ष के कहने पर कार्य कर रहा प्रतीत हो या उससे किसी प्रकार का जुड़ाव स्थापित कर ले।\n\n2.2 यहाँ उलझने के लिए कुछ भी नहीं है। गठबंधन कुछ भी नहीं मांगता, उस पर कोई देनदारी नहीं है, उसने कुछ भी नहीं रखा है, और किसी भी प्रकार की कोई अपेक्षा नहीं रखता। यह बाद में कोई अधिकार नहीं जता सकता, श्रेय का दावा नहीं कर सकता, दुरुपयोग की शिकायत नहीं कर सकता, या सामग्री को कैसे वर्णित किया गया है, उस पर आपत्ति नहीं कर सकता, क्योंकि इसके पास ऐसा करने का कोई आधार नहीं है।\n\n2.3 इस सामग्री का उपयोग करने वाला कोई प्राधिकरण इसलिए गठबंधन के लिए कार्य नहीं कर रहा है। यह सार्वजनिक जानकारी का उपयोग कर रहा है जिसे संयोगवश किसी अन्य ने संकलित किया था।\n\n3. सब कुछ पहले से ही खुला हुआ है।\n\n3.1 गठबंधन का कार्य स्वतः ही सार्वजनिक होता है:\n\nजांचें खुले तौर पर प्रकाशित की जाती हैं। https://phishdestroy.io और मुफ्त में पढ़े जा सकते हैं;\n\nटूलिंग को MIT लाइसेंस के तहत ओपन सोर्स के रूप में यहाँ प्रकाशित किया गया है। https://github.com/phishdestroy संग्रहीत 2026-09-11 ↗;\n\nपद्धति स्वयं रेफरल में, परिशिष्ट A के अनुभाग A में निर्धारित की गई है।16D, जिसमें प्रत्येक स्रोत प्रकार का भार और सीमाएँ शामिल हैं;\n\nकोएलिशन किसी भी दान को स्वीकार नहीं करता है और इस स्थिति को 2018. से प्रकाशित कर चुका है।\n\n3.2 एकमात्र सामग्री जो प्रकाशित नहीं की जाती, वह वह है जिसे कानूनी या सुरक्षित रूप से प्रकाशित नहीं किया जा सकता: पीड़ितों और तीसरे पक्षों के व्यक्तिगत डेटा, और ऐसी जानकारी जो किसी स्रोत को प्रतिशोध का शिकार होने का जोखिम में डाल सकती है। वह सामग्री गोपनीय रूप से प्राधिकरणों को प्रदान की जाती है और साक्ष्य अनुसूचियों में चिन्हित की जाती है।\n\n3.3 गठबंधन अपने आचरण की उसी शर्तों पर जांच के लिए आमंत्रित करता है, जिन शर्तों पर वह किसी और के आचरण की जांच के लिए आमंत्रित करता है, और संबंधित प्राधिकरणों को अपने डेटा प्रबंधन की स्वयं पेशकश की है, जिसमें निपटान के संबंध में निर्देश का अनुरोध भी शामिल है।\n\n4. साक्ष्य-समूह की अखंडता\n\n4.1 प्रदर्शनी सामग्री प्रस्तुति के साथ या, जहाँ चिह्नित हो, सुरक्षित चैनल के माध्यम से अनुरोध पर प्रदान की जाती है। इसे सार्वजनिक पते पर प्रकाशित नहीं किया जाता और न ही ऐसा कोई पता अनुमानित किया जाना चाहिए: इस प्रकार की सामग्री सीधे प्राधिकरणों को प्रदान की जाती है।\n\n4.2 प्रत्येक डिलीवरी के साथ एक फ़ाइल SHA256SUMS संलग्न रहती है, जिसमें प्रदान की गई प्रत्येक फ़ाइल के लिए SHA-256 डाइजेस्ट सूचीबद्ध होता है, साथ ही एक अलग OpenPGP हस्ताक्षर SHA256SUMS.asc भी होता है।\n\n4.3 हस्ताक्षर कुंजी यहाँ प्रकाशित की गई है https://phishdestroy.io/.well-known/pgp-key.txt और keys.openpgp.org पर। इसकी फिंगरप्रिंट इस सेट में प्रत्येक सबमिशन के लेटरहेड में दिखाई देती है।\n\n4.4 कोई भी प्राप्तकर्ता किसी भी समय यह सत्यापित कर सकता है कि उसके पास मौजूद फ़ाइल वही है जो भेजी गई थी, बिना किसी परिवर्तन के:\n\ngpg --verify SHA256SUMS.asc SHA256SUMS\n\nsha256sum -c SHA256SUMS\n\n4.5 उद्देश्य औपचारिकता नहीं है। इसका उद्देश्य यह है कि यदि किसी प्रदर्शनी की सटीकता या अखंडता पर बाद में विवाद हो, तो इस प्रश्न का समाधान तर्क-वितर्क के बजाय गणना द्वारा किया जा सके।\n\n5. पंजीकरण पर — छूट कैसे व्यावहारिक है और केवल उदार नहीं\n\n5.1 प्राधिकरण को गठबंधन की प्रकाशित जांचों का सामना हो सकता है और वे उन्हें बेबाक, विरोधी और कभी-कभी व्यंग्यात्मक पाएगा। यह धारणा सही है। गठबंधन जानबूझकर इस तरह लिखता है और इसके लिए माफी नहीं मांगता।\n\n5.2 यह भी स्वीकार किया जाता है कि नियामक या न्यायिक कार्यवाही के लिए यह गलत माध्यम है। एक गंभीर मामले को अभियान की भाषा में नहीं पेश किया जाना चाहिए। किसी प्राधिकरण के समक्ष प्रस्तुत निष्कर्षों को स्पष्ट रूप से बताया जाना चाहिए, उनकी सीमाओं को स्वीकार किया जाना चाहिए, और पाठक को विषय-वस्तु तक पहुँचने से पहले स्वर के आधार पर उन्हें कम महत्व देने की आवश्यकता नहीं होनी चाहिए।\n\n5.3 यही कारण है कि गठबंधन लेखकत्व से छूट देता है। धारा 1 में दी गई छूट वह तंत्र है जिससे सामग्री रजिस्टर से अलग की जा सकती है: प्राधिकरण उपयोगी बातों को ले सकता है, उन्हें अपनी आवाज़ में पुनः व्यक्त कर सकता है, और गठबंधन की शैली के हर शब्द के साथ-साथ गठबंधन का नाम भी त्याग सकता है। ऐसा करने से कुछ भी खोया नहीं जाता, और गठबंधन इसे ही प्राथमिकता देगा।\n\n5.4 गठबंधन यह भी अनुरोध करता है कि रजिस्टर को विधि न समझा जाए। प्रकाशित लहजा संघर्षपूर्ण है; अंतर्निहित अभ्यास लापरवाह नहीं है। इस संदर्भ के पूरे प्रवाह में, अनुमान अवलोकन से अलग रखा गया है, गवाही को गवाही के रूप में पहचाना गया है, स्रोतों को तौलकर उनकी कमजोरियाँ बताई गई हैं, आंकड़े उनकी सीमाओं के साथ प्रस्तुत किए गए हैं, और जिन बिंदुओं को गठबंधन साबित नहीं कर सकता, उन्हें दावों के बजाय प्राधिकरण के लिए प्रश्न के रूप में रखा गया है। जहाँ साक्ष्य गठबंधन की अपनी स्थिति के विरुद्ध गए हैं, वहाँ उसने ऐसा कहा है — देखें अनुलग्नक A, अनुच्छेद 7,, और समानांतर संदर्भ के खंड B,0।\n\n5.5 गठबंधन अपने तौर-तरीके और अपने वित्त के बीच संबंध समझाता है क्योंकि ये दोनों अलग नहीं किए जा सकते। यह किसी से भी पैसा नहीं लेता — न दान, न इनाम, न ग्राहक, न प्रायोजक। यही इनकार है जो स्पष्टवादिता को संभव बनाता है: एक ऐसा संगठन जिसके पास संरक्षित करने के लिए राजस्व है, उसे उन दलों के बारे में अपनी बातों को संयमित करना पड़ता है जिन पर वह निर्भर है। संरक्षित करने के लिए कुछ भी न होने के कारण, गठबंधन के पास संयम बरतने का कोई कारण नहीं है।\n\nयह भी वह कारण है कि गठबंधन अभी भी मौजूद है। कोई दूसरा इंजन नहीं है। काम इसलिए किया जाता है क्योंकि वह किया जाता है; जब इसे करने वाले लोग रुक जाते हैं, तब यह रुक जाता है।\n\n5.6 प्राधिकरण को इनमें से किसी को भी स्वीकार करने की आवश्यकता नहीं है। यह इसलिए कहा गया है ताकि गठबंधन के सार्वजनिक कार्यों के स्वर को वर्तमान में उसके समक्ष मौजूद सामग्री के प्रति बरती गई सावधानी का मापदंड न समझा जाए।\n\n6. गठबंधन अपनी ही शब्दों में क्या प्रदान कर रहा है\n\nजानकारी, अनुसंधान और अवलोकन।\n\nकोई भी ऐसा निष्कर्ष नहीं बताया गया है कि गठबंधन के पास ऐसा निर्णय लेने का अधिकार नहीं है। जहाँ कुछ अनुमानित होता है, संदर्भ में यह बताया जाता है। जहाँ कुछ गवाही पर आधारित होता है, संदर्भ में बताया जाता है कि वह किसकी गवाही है और उसकी सीमा क्या है। जहाँ गठबंधन किसी प्रश्न का उत्तर नहीं दे सकता, वह भी बताया जाता है और यह भी बताया जाता है कि कौन उत्तर दे सकता है।\n\nगठबंधन स्वयं या किसी व्यक्ति के लिए कोई उपचार, कोई भुगतान, कोई स्वीकृति और कोई परिणाम नहीं चाहता। यह केवल यह मांग करता है कि संदर्भ में निर्धारित प्रश्न Valve कॉर्पोरेशन से उस निकाय द्वारा पूछे जाएँ जिसके पास उत्तर देने के लिए बाध्य करने की शक्ति हो।\n\nसमापन टिप्पणीजिस भी व्यक्ति इसे आगे बढ़ा रहा है\n\nहम उन सभी का धन्यवाद करना चाहते हैं जो इस सामग्री को उस जगह तक पहुँचाएंगे जहाँ इसे पहुँचना चाहिए। यह शायद कोई त्वरित यात्रा नहीं होगी।Valve के पास गहरी जेबें हैं और Taylor Wessing प्रति घंटे शुल्क वसूलती है — यह संयोजन विशेष रूप से इस तरह से तैयार किया गया है कि आप जैसे लोग फिनिश लाइन तक पहुँचने से पहले ही हार मान लें।\n\nहम जानते हैं कि हम क्या कर रहे हैं। हम जानते हैं कि हम किसके बारे में लिख रहे हैं।Valve ने हमें बनाया — हम उन्हें कैसे नहीं समझ सकते?\n\nPhishDestroy Valve के साथ कोई संघर्ष नहीं है। हमने उस पैमाने का एकमात्र धोखेबाज़ी गिरोह ब्लॉक किया जो हमें मिला — हमने Valve के साथ झगड़ा नहीं खोजा। बस ऐसा हुआ कि हर रास्ता उन्हीं तक जाता था। कोई संघर्ष नहीं। बस टोपोलॉजी।\n\nValve PhishDestroy स्थिति को हल नहीं किया जा सकता क्योंकि हल करने के लिए कुछ भी नहीं है। हमारा कोई संबंध नहीं है। उनकी समृद्धि योजनाओं और अत्यधिक मुनाफे के बारे में डेटा काफी हद तक सार्वजनिक है — आपको बस इसे देखने के लिए पर्याप्त समय देना था। इसे एक सफलता की विश्वकोश समझें: \"प्रतिबंधों का पालन कैसे न करें ताकि रूसी हैकर्स हमारे मुफ्त गेम्स को पायरेट न कर सकें (वे वैसे भी भुगतान वाले गेम्स को पायरेट नहीं करेंगे)।\" आपको अंदाज़ा हो गया होगा।\n\nहमें लेखकत्व की आवश्यकता नहीं है।\n\nहमें श्रेय की आवश्यकता नहीं है।\n\nहमें जीत की ज़रूरत नहीं है।\n\nहमें किसी ऐसे व्यक्ति की आवश्यकता है जिसके पास वास्तविक अधिकार हो ताकि वह संदर्भ में पहले से मौजूद प्रश्नों को Valve से पूछ सके और उत्तर मांगने की शक्ति रखता हो।\n\nबस इतना ही। यही पूरा अनुरोध है।\n\nमामले यहाँ रहेंगे:\n\nhttps://steamdestroy.eth/\n\nhttps://steamdestroy.eth.limo (वर्तमान में टूटा हुआ — आवश्यकता पड़ने पर ठीक किया जाएगा)\n\nहम यहाँ होंगे:\n\nhttps://phishdestroy.eth.limo/ संग्रहीत 2026-06-27 ↗\n\nhttps://phishdestroy.eth/\n\nदो हस्ताक्षरित वस्तुएँ · अधिकार और प्रकाशित पाठ\nहस्ताक्षरित रिहाईक्या हस्ताक्षरित है, और यह क्या कवर करता है\n\nनीचे अधिकार अनुदान और शोध पाठ अलग-अलग हस्ताक्षरित JSON ऑब्जेक्ट्स के रूप में दिए गए हैं। प्रत्येक अलग-थलग OpenPGP हस्ताक्षर उसके बगल में दिए गए JSON के सटीक बाइट्स को प्रमाणित करता है। अधिकार कथन अनुमतियाँ प्रदान करता है; पाठ स्नैपशॉट प्रकाशित की जा रही सामग्री की पहचान करता है और उसे समाहित करता है।\n\n1. अधिकारों का विवरण — license-rights.json\n\nहस्ताक्षरित वस्तु: पूर्ण license-rights.json फ़ाइल, जिसमें दिनांक 28 सितंबर 2026. का सार्वजनिक अधिकार अनुदान शामिल है। यह लेखक द्वारा तैयार दस्तावेज़ सामग्री को बिना श्रेय, सूचना या अनुमोदन के प्रतिलिपि बनाने, प्रकाशित करने, संपादित करने, अनुवाद करने, संयोजित करने और वाणिज्यिक रूप से उपयोग करने की अनुमति प्रदान करता है। यह हस्ताक्षर अधिकार कथन को प्रमाणित करता है; यह प्रत्येक वेबपेज या PDF के पाठ को प्रमाणित नहीं करता।\n\nमूल हस्ताक्षरित रिलीज़ को अपरिवर्तित रूप में संरक्षित रखा गया है। इसकी मौजूदा अनुदान को वेबसाइट बदलकर, कोई अन्य फ़ाइल प्रकाशित करके या साइट को ऑफ़लाइन करके वापस नहीं लिया या संकुचित नहीं किया जा सकता। तृतीय-पक्ष सामग्री अपने स्वयं के अधिकार बनाए रखती है।\n\nअधिकार कथन JSON ↗ · license-rights.json का हस्ताक्षर ↗ · एसएचए-256 का license-rights.json ↗\n\ngpg --verify license-rights.json.asc license-rights.json\nsha256sum -c license-rights.json.sha256\n2. प्रकाशित पाठ — dossier-text.json\n\nहस्ताक्षरित वस्तु: पूर्ण dossier-text.json फ़ाइल। इसमें निर्यात किए गए पृष्ठों का वास्तविक पठनीय पाठ है। documents[].content.text, प्रत्येक पृष्ठ के शीर्षक, भाषा, स्रोत URL, स्रोत HTML हैश, शीर्षकों और संदर्भों के साथ। The documents यह सूची इस स्नैपशॉट द्वारा कवर की गई सटीक इन्वेंटरी है; भाषा संस्करण अलग से सूचीबद्ध हैं। यह केवल हैशों की सूची नहीं, बल्कि एक पाठ प्रकाशन है।\n\nप्रत्येक प्रविष्टि अपने हल्के पेज PDF को फ़ाइलनाम और SHA-256 द्वारा पहचानती है। documents[].pdf. JSON URL और SHA-256, द्वारा मूल अधिकार घोषणा को भी पहचानता है, ताकि प्रकाशित पाठ, उसका PDF और लागू अधिकार विमोचन बिना अनुमान के मेल किए जा सकें। लिंक किए गए बाहरी डेटाबेस, छवि मूल और सूची में अनुपस्थित पृष्ठ इस पाठ स्नैपशॉट में शामिल नहीं हैं।\n\nपूर्ण हस्ताक्षरित पाठ JSON ↗ · dossier-text.json का हस्ताक्षर ↗ · एसएचए-256 का dossier-text.json ↗\n\ngpg --verify dossier-text.json.asc dossier-text.json\nsha256sum -c dossier-text.json.sha256\n\nडॉसियर के होम पेज पर, PDF और JSON बटन रिसर्च बंडल का निर्यात करते हैं। एक आंतरिक पृष्ठ पर, वे उस पृष्ठ को उसकी प्रकाशित भाषा में निर्यात करते हैं। प्रत्येक पृष्ठ के JSON में भी अपनी अलग हस्ताक्षर और SHA-256 फ़ाइल होती है, जिसे स्पष्ट रूप से नामित किया गया है। integrity ऑब्जेक्ट। संबंधित PDF को सत्यापित करने के लिए, इसकी SHA-256 की गणना करें और इसकी तुलना करें pdf.sha256 सत्यापित JSON में मान। PDF उस डाइजेस्ट से बँधी है; इसमें PDF-फ़ॉर्मेट का डिजिटल हस्ताक्षर नहीं है।\n\n3. प्रिंट करने योग्य शोध बंडल — steam-dossier-{language}.content.json\n\nहस्ताक्षरित वस्तु: संपूर्ण भाषा-विशिष्ट JSON फ़ाइल, जिसमें संलग्न अध्याय पाठ शामिल है documents[].content.text, अध्याय पृष्ठ सीमाएँ, स्रोत भाषाएँ, बहिष्कृत-स्रोत सूची और सटीक PDF सारांश में pdf.sha256पाँच पूरक साक्ष्य अभिलेखागार ऑनलाइन जुड़े हुए हैं और इन्हें एक साथ संकलित नहीं किया गया है। लेखित शोध पाठ बरकरार रखा गया है; दृश्य सूचीकरण को स्रोत लिंक से प्रतिस्थापित किया गया है।\n\nअंग्रेज़ी JSON ↗ · अलग OpenPGP हस्ताक्षर ↗ · एसएचए-256 डाइजेस्ट ↗\n\nजर्मन JSON ↗ · अलग OpenPGP हस्ताक्षर ↗ · एसएचए-256 डाइजेस्ट ↗\n\ngpg --verify steam-dossier-en.content.json.asc steam-dossier-en.content.json\nsha256sum -c steam-dossier-en.content.json.sha256\n\nसार्वजनिक सत्यापन कुंजी ↗\n\nहस्ताक्षर फिंगरप्रिंट: 129F C7F3 9C40 C69D 2EF3 C329 BFCF 9E8D D295 EE01\n\ngpg --import pgp-key.txt\ngpg --fingerprint 129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01\n\nजाँचें कि प्रदर्शित फिंगरप्रिंट ऊपर दिए गए फिंगरप्रिंट से मेल खाता है, फिर हस्ताक्षर की पुष्टि सटीक JSON फ़ाइलनाम के आधार पर करें। एक हस्ताक्षरित JSON को संपादित करने से हस्ताक्षरित ऑब्जेक्ट बदल जाता है और उसका मूल हस्ताक्षर अमान्य हो जाता है। एक वैध हस्ताक्षर प्रकाशित बाइट्स की पहचान करता है; यह शोध निष्कर्षों की स्वतंत्र पुष्टि नहीं है।\n\nPhishDestroy — सार्वजनिक जांच — सभी अधिकार मानवता को समर्पित\n\nOFAC-क्षेत्र पहुँच: निषिद्ध",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "लाइसेंस और कानूनी अस्वीकरण — सार्वजनिक डोमेन समर्पण"
          },
          {
            "level": 2,
            "id": null,
            "text": "खंड Iलाइसेंस — असल कानूनी हिस्सा, लेकिन मानवीय"
          },
          {
            "level": 3,
            "id": null,
            "text": "एक असली नियम (हाँ, सिर्फ एक)"
          },
          {
            "level": 2,
            "id": null,
            "text": "खंड IIयह क्या है और यह क्यों मौजूद है"
          },
          {
            "level": 2,
            "id": null,
            "text": "खंड IIIValve के लिए खुला पत्र — सच में, इसे पढ़ो"
          },
          {
            "level": 3,
            "id": null,
            "text": "डील (ओपन ऑफर, वकीलों की जरूरत नहीं)"
          },
          {
            "level": 2,
            "id": null,
            "text": "खंड III-Bसंबंधित संसाधन — विशेष रूप से Steam के लिए एक नोट"
          },
          {
            "level": 2,
            "id": null,
            "text": "खंड IVपैसा, पाबंदियाँ, पूरा तमाशा"
          },
          {
            "level": 2,
            "id": null,
            "text": "खंड Vमैलवेयर वाली बात — हाँ, हम इसका ज़िक्र कर रहे हैं"
          },
          {
            "level": 2,
            "id": null,
            "text": "घोषणाउपयोग और अधिकारों के संबंध में"
          },
          {
            "level": 3,
            "id": null,
            "text": "1. उपयोग पर कोई शर्तें नहीं हैं।"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. यह व्यावहारिक रूप से क्यों मायने रखता है, और केवल शिष्टाचार के रूप में ही नहीं।"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. सब कुछ पहले से ही खुला हुआ है।"
          },
          {
            "level": 3,
            "id": null,
            "text": "4. साक्ष्य-समूह की अखंडता"
          },
          {
            "level": 3,
            "id": null,
            "text": "5. पंजीकरण पर — छूट कैसे व्यावहारिक है और केवल उदार नहीं"
          },
          {
            "level": 3,
            "id": null,
            "text": "6. गठबंधन अपनी ही शब्दों में क्या प्रदान कर रहा है"
          },
          {
            "level": 2,
            "id": null,
            "text": "समापन टिप्पणीजिस भी व्यक्ति इसे आगे बढ़ा रहा है"
          },
          {
            "level": 2,
            "id": null,
            "text": "हस्ताक्षरित रिहाईक्या हस्ताक्षरित है, और यह क्या कवर करता है"
          },
          {
            "level": 3,
            "id": null,
            "text": "1. अधिकारों का विवरण — license-rights.json"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. प्रकाशित पाठ — dossier-text.json"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. प्रिंट करने योग्य शोध बंडल — steam-dossier-{language}.content.json"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/hi/#briefing-heading",
          "https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "http://web.archive.org/web/20260821155801/https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "https://phishdestroy.io/steam_dossier/hi/investigation_part2.html#outsourcing-case",
          "https://phishdestroy.io/steam_dossier/hi/#theft-ledger",
          "https://steamid.uk/",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/groups/steambans",
          "https://steamcommunity.com/id/killahinstinct_",
          "https://phishdestroy.io/steam_dossier/hi/card_economy.html#governance",
          "https://phishdestroy.io/steam_dossier/hi/license_disclaimer.html",
          "https://github.com/phishdestroy",
          "http://web.archive.org/web/20260911040557/https://github.com/PhishDestroy",
          "https://phishdestroy.io/.well-known/pgp-key.txt",
          "https://steamdestroy.eth/",
          "https://steamdestroy.eth.limo/",
          "https://phishdestroy.eth.limo/",
          "http://web.archive.org/web/20260627040219/https://phishdestroy.eth.limo/",
          "https://phishdestroy.eth/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json.asc",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json.sha256",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json.sha256?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json.sha256?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json.sha256?v=print-20260928-v3"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/hi/license_disclaimer.content.json",
      "export_json_sha256": "266925ab73fa34afaea2d07498c2aad628896e653b32ea1647ef0835db33da83"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "hi/market_economics.html",
      "language": "hi",
      "title": "एक बुनियादी ढांचा, दो बाज़ार — द Steam डॉसियर",
      "source_url": "https://phishdestroy.io/steam_dossier/hi/market_economics",
      "source_html_sha256": "803fbf263c299274ab830ec218c6bce049f02150a1eacf904b4597593a43a046",
      "exported_at": "2026-09-29T00:22:46.111Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "market_economics.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/hi/market_economics.pdf?v=print-20260929-v5",
        "sha256": "ce03d3d2ef91c74a7988d2131b01d3611ce91d7938fe1f9c8bddd540b66b2f70",
        "bytes": 336096,
        "pages": 7
      },
      "integrity": {
        "signed_object": "market_economics.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "market_economics.content.json.asc",
        "digest_file": "market_economics.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify market_economics.content.json.asc market_economics.content.json",
          "sha256sum -c market_economics.content.json.sha256"
        ]
      },
      "content": {
        "text": "प्रदर्शनी VII · बाज़ार संरचना · 20 सितंबर 2026\nबाजार अर्थशास्त्र — दो अर्थव्यवस्थाएँ और लिस्टिंग सीमा\n\nउनका बुनियादी ढांचा। दो अर्थव्यवस्थाएँ।\n\nयह अनुभाग क्या प्रमाणित करता है\n\nयह अध्याय Valve की $1,800 लिस्टिंग कैप और गैर-निकासी योग्य वॉलेट बैलेंस द्वारा उत्पन्न प्रणालीगत बाजार विभाजन का विश्लेषण करता है। लगभग $1.28 अरब के सूचीबद्ध मूल्यांकन वाले 38 के सक्रिय बाहरी स्किन एक्सचेंजों का सर्वेक्षण करके, इस जांच से यह साबित होता है कि उच्च-स्तरीय ट्रेडिंग अनिवार्य रूप से बाहरी छाया प्लेटफ़ॉर्मों पर स्थानांतरित हो जाती है, जबकि यह Steam के अंतर्निहित व्यापार और प्रमाणीकरण अवसंरचना पर निर्भर रहती है। जबकि सदस्यता अनुबंध में व्यावसायिक उपयोग को औपचारिक रूप से निषिद्ध किया गया है, Valve बिना प्रकाशित प्रवर्तन रिकॉर्ड के इस द्वि-स्तरीय अर्थव्यवस्था को सुगम बनाता है और इसका मुद्रीकरण करता है।\n\n← कार्यकारी ब्रीफिंग पर वापस\n\n38 सक्रिय तृतीय-पक्ष CS2 बाज़ार, साथ ही Steam का अपना। उनमें से किसी पर सूचीबद्ध प्रत्येक त्वचा को Steam की इन्वेंटरी से होकर गुजरना चाहिए और API पर व्यापार करना चाहिए। Valve के नियम उस अवसंरचना के वाणिज्यिक शोषण को प्रतिबंधित करते हैं। लगभग $1.28 अरब का तीसरे पक्ष द्वारा सूचीबद्ध मूल्य मौजूद है, जबकि इस नियम को लागू करने का कोई सार्वजनिक रिकॉर्ड नहीं मिला है।\n\n$1.28B\nतृतीय-पक्ष सूचीबद्ध मूल्य · 38 प्लेटफ़ॉर्म\n53.2एम\nप्रदर्शित ऑफ़र · 38तृतीय-पक्ष बाज़ार\n70.1के\nSteam स्नैपशॉट में सूचीबद्ध आइटम\n41×\nतृतीय-पक्ष सूचीबद्ध मूल्य बनाम Steam का $31मिलियन\nमुख्य निष्कर्ष\nएक बुनियादी ढांचा। दो अर्थव्यवस्थाएँ।\n\nSteam आइटम, इन्वेंटरी और व्यापार को नियंत्रित करता है। किसी भी निम्न-स्तरीय प्लेटफ़ॉर्म पर बेची जाने वाली हर स्किन को Steam के व्यापार API के माध्यम से गुजरना अनिवार्य है — यह एक संरचनात्मक निर्भरता है जो सीधे तौर पर दिखाई देती है। Valve का अपना कम्युनिटी मार्केट अपनी बिक्री पर एक शुल्क कमाता है; यह शुल्क तीसरे पक्ष के इकोसिस्टम को वित्त पोषित करता है, या उससे जुड़ा है, या नहीं, यह यहाँ स्थापित नहीं किया गया है।\n\nजांच के लिए यह क्यों महत्वपूर्ण है\n1\nValve का Steam सदस्य समझौता व्यावसायिक शोषण पर रोक लगाता है Steam के बुनियादी ढांचे का स्पष्ट अनुमति के बिना उपयोग। नीचे दिए गए प्लेटफ़ॉर्मों के लिए सार्वजनिक अभिलेखों में ऐसी कोई अनुमति नहीं मिली है।\n2\nSteam लगभग $1.28B के तीसरे पक्ष के सूचीबद्ध मूल्य के लिए पहचान (OpenID), इन्वेंटरी स्थिति, और व्यापार निष्पादन को नियंत्रित करता है। Valve के बुनियादी ढांचे के बिना कोई वस्तु हस्तांतरण नहीं होता।\n3\nSteam का अपना मार्केटप्लेस है $31M सूचीबद्ध — तीसरे पक्ष द्वारा सूचीबद्ध मूल्य का लगभग 1/41। $1,800 मूल्य सीमा का मतलब है कि इससे अधिक कीमत पर बेचने वालों को अवलोकित कीमतों पर बेचने के लिए प्लेटफ़ॉर्म से बाहर जाना होगा।\n4\n248 CS2 वस्तु श्रेणियाँ, जिन्हें स्वतंत्र रूप से दो या अधिक मार्केटप्लेस ने कैप से ऊपर मूल्यित किया है, उन्हें Steam पर उनके अवलोकित बाजार मूल्य पर बेचा नहीं जा सकता — और उनमें से कोई भी वहाँ सूचीबद्ध नहीं है। $1,800 कैप वह मांग उत्पन्न करता है जिसे तृतीय-पक्ष ऑपरेटर पूरा करते हैं।\nSteam सामुदायिक बाज़ार: $31मिलियनतृतीय-पक्ष सूचीबद्ध मूल्य: $1,276मिलियन\n$1,276एम · तृतीय-पक्ष सूचीबद्ध मूल्य — सभी Steam के व्यापार API और OpenID पर निर्भर हैं।\nSteam · $31मिलियन\n\nस्रोत: PriceEmpire रीयल-टाइम कैटलॉग, 20 सितंबर 2026. सूचीबद्ध मूल्य = सहेजी गई स्नैपशॉट में गोल किए गए सूचीबद्ध-मूल्य कार्डों का योग, Steam को छोड़कर। बिक्री की मात्रा नहीं।\n\n38 सक्रिय तृतीय-पक्ष बाजार · सब कुछ Steamी अवसंरचना पर निर्भर\nप्लेटफ़ॉर्म रजिस्टर\n\nनीचे दिए गए प्लेटफ़ॉर्म अपने लॉगिन को Steam OpenID के माध्यम से और अपने ट्रेड्स को Steam के वेब API के माध्यम से रूट करते हैं। प्रत्येक अवलोकित openid.realm Steam के लॉगिन फ्लो से गुजरता है; रजिस्टर यह मानते हुए कि किसी भी ऑपरेटर के पास Valve की अनुमति नहीं है, यह दावा करने के बजाय देखे गए ऑथ रूट्स को रिकॉर्ड करता है।\n\n#\tमंच\tसूचीबद्ध मूल्य\tसक्रिय ऑफ़र\tआइटम\tपैमाना\n1\tUUSkins\t$133.8M\t3.4M\t30.9K\t\n\n2\tYouPin898\t$127.5M\t5.9M\t29.2K\t\n\n3\tBuff.163\t$104M\t3.5M\t35K\t\n\n4\tMoon.Market\t$100.3M\t2.9M\t20.9K\t\n\n5\tWhite.Market\t$89.6M\t3M\t20.6K\t\n\n6\tBuff.Market\t$86.7M\t1.3M\t33.4K\t\n\n7\tEcosteam\t$82.1M\t3.3M\t30.1K\t\n\n8\tCSFloat\t$67.8M\t2.4M\t27.8K\t\n\n9\tSkin.Land\t$67.4M\t2.2M\t34.6K\t\n\n10\tLIS-SKINS\t$67.4M\t2.2M\t34.6K\t\n\n11\tC5Game\t$54.6M\t4.6M\t29.6K\t\n\n12\tHaloSkins\t$46.6M\t4.4M\t29.3K\t\n\n13\tAvan.Market\t$43.3M\t809.5K\t22.2K\t\n\n14\tWaxpeer\t$40.1M\t1M\t27.3K\t\n\n15\tSteam (official)\t$31M\t32.2M\t70.1K\t\n\n16\tCS.MONEY\t$29M\t748.9K\t28K\t\n\n17\tMarket.CSGO\t$26.3M\t1.3M\t27.6K\t\n\n18\tCS.MONEY Bot\t$25.7M\t614K\t23.8K\t\n\n19\tSkinport\t$16.3M\t3.8M\t31.1K\t\n\n20\tSkinFlow\t$14.1M\t481.8K\t23.6K\t\n\n21\tDMarket\t$12.6M\t948.2K\t35.6K\t\n\n22\tSkins.com\t$11.5M\t83.2K\t15.8K\t\n\n23\tSkin.place\t$6.9M\t380.8K\t11.4K\t\n\n24\tSkinsMonkey\t$6M\t109.4K\t11.6K\t\n\n25\tSkinBaron\t$5M\t2.1M\t21.5K\t\n\n26\tRustTM\t$3M\t33.1K\t4.9K\t\n\n27\tPirateSwap\t$2M\t859.3K\t10.5K\t\n\n28\tMannco.Store\t$1.2M\t223.7K\t11K\t\n\n29\tSkinSwap\t$1.1M\t11.4K\t4K\t\n\n30\tTradeIt\t$967.1K\t29.1K\t11.7K\t\n\n31\tLootFarm\t$896.1K\t162.5K\t28.6K\t\n\n32\tRustskins\t$714.8K\t312.5K\t6.1K\t\n\n33\tBalticSkins\t$599.2K\t28.2K\t4.5K\t\n\n34\tExeSkins\t$442.9K\t2.6K\t1.4K\t\n\n35\tRapidSkins\t$230.9K\t11.6K\t2.3K\t\n\n36\tCS.Trade\t$203K\t19K\t16.7K\t\n\n37\tKrakatoa\t$11.1K\t115\t53\t\n\n38\tShadowPay\t—\t—\t—\t—\n39\t49skins\t—\t—\t—\t—\nSteam की $1,800 मूल्य सीमा · पाँच-बाजार झलक · 23 सितंबर 2026\nमूल्य अंतर मापनीय है।\n\nSteam caps Community Market लिस्टिंग लगभग $1,800 पर सीमित करता है (यह निष्कर्ष पुनः गणना करके $2,000, $, 2,070, $, 2,300 और $2,500 पर मिला है) cs2sh-atlas.json और प्रत्येक सीमा पर बरकरार रहता है)। उस कीमत से ऊपर देखे गए आइटम Valve के अपने मार्केटप्लेस के माध्यम से उनकी बाजार मूल्य पर बेचा नहीं जा सकता। — लेकिन वे जहाँ भी बेचे जाते हैं, अभी भी Steam के इन्वेंटरी और ट्रांसफर सिस्टम पर निर्भर करते हैं। कीमत के अनुसार पूरे कैटलॉग को बाँटने से पता चलता है कि बाधा कहाँ है: Valve का बाज़ार वहन करता है 95.3% अपने कैप से नीचे मूल्य वाले आइटम श्रेणियों का 1.9% उसके ऊपर मौजूद उन लोगों का।\n\nपाँच बाज़ार: Steam सीमा से ऊपर की वस्तुएँ\n248\n\nवस्तु श्रेणियाँ जिनकी सबसे सस्ती पूछताछ $1,800 से अधिक है। दो या अधिक बाज़ार स्वतंत्र रूप से, कम से कम मूल्य की सूचीबद्ध प्रतिलिपियों के साथ 18,394 को धारण करते हुए $78.6M. उनमें से, 100.0% — हर एक — की कोई भी Steam सूची नहीं है।\n\nपूर्ण प्रदर्शनियाँ: रजिस्टर → · मूल्य-सीढ़ी एटलस →\n\nकैप से ऊपर मूल्य वितरण\n$1,800–$5,000\n174\n$5,000–$10,000\n49\n$10,000–$25,000\n21\n$25,000–$50,000\n2\n$50,000+\n2\nशीर्ष आइटम — पाँच बाज़ारों में सत्यापित सबसे सस्ती पूछी गई कीमतें\n1स्टिकर | टाइटन (होलो) | कैट. '14$66,285\n2स्टिकर | iBUYPOWER (होलो) | श्रेणी '14$64,795\n3स्टिकर | रीज़न गेमिंग (होलो) | श्रेणी: '14$42,899\n4★ स्पोर्ट दस्ताने | हेज मेज़ (एफएन)$26,812\n5स्टिकर | टीम डिग्निटास (होलो) | कैट. '14$23,667\n6ईएमएस श्रेणी '14 लीजेंड्स$22,879\n7★ स्पोर्ट दस्ताने | पंडोरा का बक्सा (एफएन)$21,643\n8ईएमएस श्रेणी '14 चैलेंजर्स$21,010\n9स्टिकर | वॉक्स एमिनोर (होलो) | कैट. '14$18,619\n10★ स्टैटट्रैक™ नावाहा चाकू | नीला स्टील (एफएन)$18,064\n\nमांगी गई कीमतें बिक्री की कीमतें नहीं हैं। लाइसेंस प्राप्त cs2.sh का स्नैपशॉट, 23 सितंबर 2026. प्रत्येक पंक्ति को कम से कम दो बाज़ारों द्वारा स्वतंत्र रूप से कैप से ऊपर उद्धृत किया गया है; एकल-शेल्फ पूछताछ और उद्धरण जिन्हें किसी आइटम की सबसे सस्ती पूछताछ से तीन गुना से अधिक बार बाहर रखा गया है, उन्हें छोड़ दिया गया है। ग्रेडिंग कैसे काम करती है →\n\nValve क्या शुल्क लेता है · लाइसेंस प्राप्त cs2.sh स्नैपशॉट · 23 सितंबर 2026\nविज्ञापित शुल्क 15%. है। अधिकांश लिस्टिंग अधिक भुगतान करती हैं।\n\nValve विक्रेता की आय से 5%Steam शुल्क और एक 10% CS2 प्रकाशक शुल्क लेता है — परिचित 15%. दोनों शुल्कों में एक $0.01 न्यूनतम, इसलिए कोई भी बिक्री शुल्क में दो सेंट से कभी कम नहीं हो सकती। सस्ते, उच्च-मात्रा वाले आइटमों पर, जो बाजार का अधिकांश हिस्सा बनाते हैं, वह न्यूनतम सीमा बाध्यकारी होती है, प्रतिशत नहीं। हमने शुल्क की गणित को हर एक के लिए हल किया 29,635 लाइव Steam पूछने वाले आइटम प्रकार।\n\n77.7%\nSteam लिस्टिंग्स का एक हिस्सा उन आइटम प्रकारों पर होता है जिन पर 15% से अधिक शुल्क लगाया जाता है।\n84.8%\nआइटम का प्रकार शीर्ष दर के बारे में भुगतान करें\n4,517\nवस्तु प्रकारों पर विज्ञापित शुल्क से अधिक शुल्क लिया गया।\n$0.02\nकिसी भी बिक्री पर न्यूनतम शुल्क, कीमत चाहे जो भी हो।\nदोनों संख्याएँ विपरीत दिशाओं की ओर इशारा करती हैं, और दोनों ही सत्य हैं।\n1\nगणना किया गया आइटम प्रकार के अनुसारValve की फीस सामान्यतः विज्ञापित के अनुसार ही है: 29,635 के मूल्य-निर्धारित प्रकारों पर 84.8% की दरें 15%. पर या उसके आसपास लगाई जाती हैं।\n2\nगणना किया गया वास्तविक सूचीकरण द्वारा, तस्वीर उलट जाती है: 18,682,244 24,038,911 लाइव लिस्टिंग उन आइटम प्रकारों पर हैं जिन पर 15%. से अधिक शुल्क लिया जाता है।\n3\nदोनों सत्य हैं क्योंकि अति-चार्ज किए गए प्रकार हैं सस्ता, उच्च मात्रा एक। 1,109 आइटम प्रकारों पर अधिक शुल्क लगाया जाता है। दोहरा हेडलाइन रेट, और केवल वही प्रकार 14,083,486 की लाइव लिस्टिंग करते हैं।\n4\nयह अंकगणित है, कोई आरोप नहीं। न्यूनतम राशि Valve के अपने शुल्क दस्तावेज़ों में प्रकट की गई है। जो प्रकाशित नहीं किया गया है वह है वास्तव में यह बाज़ार के कितने हिस्से पर लागू होता है — जो उपरोक्त आंकड़े मापते हैं।\nशुल्क, शीर्षक 15% के हिस्से के रूप में वसूला जाता है।\n200%+\n14,083,486\n100-200%\n1,028,438\n50-100%\n700,804\n30-50%\n317,031\n20-30%\n2,258,254\n17.6-20%\n294,231\n\nबार लंबाई प्रत्येक बैंड में लाइव लिस्टिंग की संख्या है। \"200%+\" बैंड का अर्थ है कि विक्रेता की आय पर ली जाने वाली फीस विक्रेता की आय के 15% से दोगुनी से अधिक है।\n\nएक व्यावहारिक उदाहरण\n67%\n\nलिस्टिंग पर खरीदार भुगतान करता है $0.03 क्योंकि, विक्रेता को प्राप्त होता है $0.01 और Valve लेता है $0.02 — दो एक-सेंट न्यूनतम। खरीदार द्वारा चुकाई गई राशि का यह हिस्सा 67% है; विक्रेता की आय का यह हिस्सा 200%. है।\n\nपूर्ण डेटासेट: cs2sh-steam-fee-census.json →\n\nउसी वस्तु, बगीचे के अंदर और बाहर\nSteam पर खरीदना महंगा पड़ता है। लगभग हमेशा।\n\nSteam और कम से कम एक तृतीय-पक्ष मार्केटप्लेस दोनों पर उद्धृत प्रत्येक आइटम के लिए, हमने Steam की सबसे सस्ती पूछी गई कीमत की तुलना इसके बाहर की सबसे सस्ती पूछी गई कीमत से की। पूरे 28,700 आइटम, Steam अधिक महंगा स्थल है। 86.4% समय का, एक माध्यिका द्वारा +35.7%.\n\nमध्यम Steam प्रीमियम, मूल्य बैंड के अनुसार\n$0.50 से कम\n+48.3%\n$0.50-2\n+36.5%\n$2-10\n+29.6%\n$10-50\n+28.6%\n$50-250\n+36.3%\n$250-1k\n+51.1%\n$1,000 से अधिक\n+67.9%\n\nवक्र U-आकार का है। इसे Steam पर खरीदना सबसे सस्ता है। $10–$50 दोनों सिरों पर प्रिय और बंधन।\n\nमहँगा अंत क्यों मायने रखता है\n+67.9%\n\nऊपर $1,000, औसत Steam लिस्टिंग लागतें 67.9% इसके बाहर की सबसे सस्ती पेशकश से अधिक हैं — और केवल 1,040 ऐसी लिस्टिंग ही Steam पर मौजूद हैं।\n\nलगभग $1,800 से आगे तुलना संभव नहीं रह जाती, क्योंकि Valve का नियम पूरी तरह से सूचीबद्ध करने पर रोक लगाता है। Steam का अपनी ही सीमा से ऊपर की वस्तुओं का कवरेज 1.9%. पूरी सीढ़ी देखें →\n\nपूर्ण डेटासेट: cs2sh-walled-garden-premium.json →\n\nप्रीमियम अपने आप में कोई निष्कर्ष नहीं है: Steam तत्काल डिलीवरी और कोई काउंटरपार्टी जोखिम नहीं प्रदान करता है, और खरीदार इसके लिए उचित रूप से भुगतान कर सकते हैं। जो मापा जा सकता है वह है अंतर का आकार और यह तथ्य कि उस पैसे को वापस नहीं निकाला जा सकता — जो अगला खंड है।\n\nपैसा आता है, जाता नहीं।\n$128.1 मिलियन उन ऑर्डरों के लिए प्रतिबद्ध हैं जिन्हें वापस नहीं लिया जा सकता।\n\nSteam खरीद आदेश पूर्व-वित्तपोषित होता है: जैसे ही आदेश दिया जाता है, पैसा खरीदार के वॉलेट से निकल जाता है। Steam वॉलेट फंड्स वापस नहीं लिया जा सकता — इन्हें केवल Steam के अंदर ही खर्च किया जा सकता है। प्रत्येक ट्रैक किए गए आइटम की बाय बुक के प्रत्येक मूल्य स्तर को जोड़ने से प्रतिबद्ध, गैर-निकासी योग्य धन का एक जनगणना प्राप्त होती है।\n\n$128.1M\nSteam खरीद आदेशों पर कायम\n170.6एम\nव्यक्तिगत वित्त पोषित खरीद आदेश लंबित\n$105.8M\nउनके सामने रखी गई लिस्टिंग का पूछा गया मूल्य\n$15.9M\nValve का हिस्सा अगर हर लिस्टिंग अपनी पूछी गई कीमत पर बिके\nयह आंकड़ा क्या है, और यह क्या नहीं है\n1\nयह है वास्तविक धन पहले ही जमा हो चुका है. हर गिना गया डॉलर एक वॉलेट से डेबिट किया गया है और यह 31,253 आइटम प्रकारों में एक खुले ऑर्डर के खिलाफ जमा है।\n2\nयह है राजस्व नहीं और यहValve की बैलेंस शीट के बारे में कोई दावा नहीं है। फ्लोट कहाँ रखा गया है, और किसकी बहीखातों में, यह यहाँ स्थापित नहीं किया गया है।\n3\nयह एक है झलक, प्रवाह नहीं. ऑर्डर खरीदार द्वारा रद्द किए जा सकते हैं, जिससे वॉलेट में धन वापस आ जाता है — लेकिन यह अभी भी Steam से बाहर नहीं जाता।\n4\nएकतरफा दरवाज़ा ही मुद्दा है। एक ऐसा बाज़ार जिसकी मुद्रा को नकद में नहीं निकाला जा सकता, चोरी की गई सूची को परिवर्तित करने का कारण है। बंद Steam उस पर की बजाय\n\nविधि: प्रत्येक ट्रैक की गई बाय बुक के प्रत्येक मूल्य स्तर को उस स्तर पर मौजूद ऑर्डरों से गुणा किया गया। पूर्ण डेटासेट: cs2sh-steam-locked-capital.json →\n\nपूरी हुई बिक्री, न कि माँग मूल्य · एक ही बाज़ार · पिछले 90 दिनों का\n$30.9 मिलियन वास्तव में हाथ बदले — पाँचों शेल्फों में से सबसे छोटे पर।\n\nएकल हाई सेल एक दुर्लभ क्राफ्ट या सस्ते बेस आइटम का स्टिकर-आधारित वेरिएंट हो सकता है (e.g । एक $30 आइटम जिसका एक बार $9,772 पर पूरा हुआ बिक्री लेनदेन)। \"हाई\" = सबसे ऊँचा पूरा हुआ लेनदेन, आइटम की सामान्य कीमत नहीं।\n\nइस पृष्ठ पर प्रत्येक अन्य आकृति मापती है कि क्या है सूचीबद्ध. यह मापता है कि क्या था बिक गयाSkinport अपनी पूरी हुई लेन-देन प्रकाशित करता है, और पिछले 90 दिनों में वे कुल मिलाकर 1,219,143 बिक्री मूल्य $30,927,032, प्रत्येक की औसत कीमत $25.37।\n\n1.22एम\n90 दिनों में बिक्री पूरी, एक ही मार्केटप्लेस\n$30.9M\nउसी अवधि में कारोबार\n$125M\nवार्षिक चालू दर — एक न्यूनतम स्तर, अनुमान नहीं\n~2%\nसूचीबद्ध मूल्य के अनुसार उपरोक्त-सीमा शेल्फ में Skinport का हिस्सा\nटर्नओवर कहाँ से आया\n$1 से कम\n0.5%\n$1-10\n5.8%\n$10-100\n22.2%\n$100-1k\n59.4%\n$1k-1.8k\n6.9%\nSteam कैप के ऊपर\n5.3%\n\nबार की लंबाई टर्नओवर है; यह आंकड़ा उस स्तर का कुल का हिस्सा है। 59.4% $100–$1k श्रेणी में, 71,437 बिक्री पर स्थानांतरित धन का।\n\nValve की टोपी के ऊपर भी बिक्री होती है।\n492\n\nSteam सीमा से ऊपर मूल्य वाली वस्तुओं की बिक्री पूरी की, जिनका मूल्य $1,643,938, लगभग 76 आइटम प्रकारों में — एक ऐसे मार्केटप्लेस पर जो उस शेल्फ का लगभग 2% रखता है। उनमें से कोई भी बिक्री Steam पर नहीं हो सकती थी।\n\nपूर्ण डेटासेट: cs2sh-offsteam-90d-dynamics.json → · प्राप्त उच्च →\n\nSkinport यह यहाँ ट्रैक किए गए तीसरे पक्ष के बाजारों में से एक है, और Steam कैप से ऊपर सूचीबद्ध मूल्य के कारण यह पाँचों में सबसे छोटा है (उस शेल्फ का लगभग 2%)। यहाँ दिया गया प्रत्येक कुल ऑफ-Steam अर्थव्यवस्था का न्यूनतम स्तर है, न कि उसका माप। कोई Steam डेटा उपयोग नहीं किया गया है।",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "बाजार अर्थशास्त्र — दो अर्थव्यवस्थाएँ और लिस्टिंग सीमा"
          },
          {
            "level": 2,
            "id": null,
            "text": "एक बुनियादी ढांचा। दो अर्थव्यवस्थाएँ।"
          },
          {
            "level": 2,
            "id": null,
            "text": "प्लेटफ़ॉर्म रजिस्टर"
          },
          {
            "level": 2,
            "id": null,
            "text": "मूल्य अंतर मापनीय है।"
          },
          {
            "level": 3,
            "id": null,
            "text": "पाँच बाज़ार: Steam सीमा से ऊपर की वस्तुएँ"
          },
          {
            "level": 3,
            "id": null,
            "text": "कैप से ऊपर मूल्य वितरण"
          },
          {
            "level": 3,
            "id": null,
            "text": "शीर्ष आइटम — पाँच बाज़ारों में सत्यापित सबसे सस्ती पूछी गई कीमतें"
          },
          {
            "level": 2,
            "id": null,
            "text": "विज्ञापित शुल्क 15%. है। अधिकांश लिस्टिंग अधिक भुगतान करती हैं।"
          },
          {
            "level": 3,
            "id": null,
            "text": "शुल्क, शीर्षक 15% के हिस्से के रूप में वसूला जाता है।"
          },
          {
            "level": 3,
            "id": null,
            "text": "एक व्यावहारिक उदाहरण"
          },
          {
            "level": 2,
            "id": null,
            "text": "Steam पर खरीदना महंगा पड़ता है। लगभग हमेशा।"
          },
          {
            "level": 3,
            "id": null,
            "text": "मध्यम Steam प्रीमियम, मूल्य बैंड के अनुसार"
          },
          {
            "level": 3,
            "id": null,
            "text": "महँगा अंत क्यों मायने रखता है"
          },
          {
            "level": 2,
            "id": null,
            "text": "$128.1 मिलियन उन ऑर्डरों के लिए प्रतिबद्ध हैं जिन्हें वापस नहीं लिया जा सकता।"
          },
          {
            "level": 2,
            "id": null,
            "text": "$30.9 मिलियन वास्तव में हाथ बदले — पाँचों शेल्फों में से सबसे छोटे पर।"
          },
          {
            "level": 3,
            "id": null,
            "text": "टर्नओवर कहाँ से आया"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve की टोपी के ऊपर भी बिक्री होती है।"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/hi/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/hi/elite_skins.html",
          "https://phishdestroy.io/steam_dossier/hi/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/hi/skin_atlas.html#grading",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-steam-fee-census.json",
          "https://phishdestroy.io/steam_dossier/hi/skin_atlas.html#cliff",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-walled-garden-premium.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-steam-locked-capital.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-offsteam-90d-dynamics.json",
          "https://phishdestroy.io/steam_dossier/hi/skin_atlas.html#highs"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/hi/market_economics.content.json",
      "export_json_sha256": "d6a62a40b653129d3e69f93b7f6200f841f4f0e0f4624d60475401ed045efa71"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "hi/regulatory_act_print.html",
      "language": "hi",
      "title": "फॉरेंसिक ऑडिट अधिनियम: Valve Steam वेब API इकोसिस्टम और वाणिज्यिक शोषण (संदर्भ: VAL-REG-2026-09)",
      "source_url": "https://phishdestroy.io/steam_dossier/hi/regulatory_act_print",
      "source_html_sha256": "3fcf1f4f1ae61253bd643c13e30d14f15d1d9de8ea6a6ec4e92a53fcdcdb0d22",
      "exported_at": "2026-09-29T00:22:47.415Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "regulatory_act_print.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/hi/regulatory_act_print.pdf?v=print-20260929-v5",
        "sha256": "094d1d233f28284e70008c0b540dfd942575517baa83ecda8fa60b3c817ec2b7",
        "bytes": 439389,
        "pages": 12
      },
      "integrity": {
        "signed_object": "regulatory_act_print.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "regulatory_act_print.content.json.asc",
        "digest_file": "regulatory_act_print.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify regulatory_act_print.content.json.asc regulatory_act_print.content.json",
          "sha256sum -c regulatory_act_print.content.json.sha256"
        ]
      },
      "content": {
        "text": "phishdestroy.io · फोरेंसिक रिसर्च कोएलिशन · सार्वभौमिक सार्वजनिक अभिलेख\nडॉकेट: VAL-REG-2026-09-EVID\nउत्पत्ति: phishdestroy.io/स्टीम_डॉसियर/\nअधिकार: सभी अधिकार मानवता को समर्पित\nफोरेंसिक ऑडिट अधिनियम और नियामक प्रदर्शनी\nValve-Steam पारिस्थितिकी तंत्र में व्यवस्थित तृतीय-पक्ष API प्रविष्टि, स्वचालित बाईपास वास्तुकला और संविदात्मक गैर-प्रवर्तन\nजारी करने वाला डोमेनphishdestroy.io\nलक्षित प्लेटफ़ॉर्मValve Steam / स्टीमवर्क्स\nप्राथमिक प्रमाणीकरण वेक्टरSteam ओपनआईडी 2.0 / वेब API\nकानूनी समर्पणमानवता के लिए सभी अधिकार (CC0)\nखंड I: कार्यकारी ज्ञापन और तथ्यात्मक निष्कर्षसंदर्भ: मेमो-सारांश-01\n\nयह दस्तावेज़ एक औपचारिक फोरेंसिक ऑडिट अधिनियम है, जोValve Corporation की प्रकाशित व्यावसायिक शर्तों, इसके तकनीकी प्रमाणीकरण एंडपॉइंट्स और अवलोकित तृतीय-पक्ष व्यावसायिक प्लेटफ़ॉर्मों के परिचालन संबंधी अंतर्संबंध की जांच करता है। यह ऑडिट निष्क्रिय, अप्रमाणित नेटवर्क अवलोकन, RDAP पंजीकरण सत्यापन और सार्वजनिक लिंक फ़िल्टर टेलीमेट्री का उपयोग करके किया गया था।\n\nतथ्यात्मक मूल: अनुभवजन्य अवलोकन Valve की सार्वजनिक संविदात्मक अभिव्यक्तियों और उसके उत्पादन अवसंरचना के बीच एक व्यवस्थित विचलन स्थापित करता है। जबकि Steam सदस्य समझौता (SSA) अनधिकृत व्यावसायिक शोषण (§ 2.G), स्वचालित बॉट/स्क्रिप्ट इंटरैक्शन (§ 4.C) और खाते के हस्तांतरण (§ 1.C) को सख्त रूप से प्रतिबंधित करता है, Valve कॉर्पोरेशन कम से कम 175 व्यावसायिक संस्थाओं को लाइव, प्रोग्रामैटिक OpenID प्रमाणीकरण और इन्वेंटरी क्वेरी अवसंरचना प्रदान करना जारी रखती है, जो बहु-अरब डॉलर के द्वितीयक लेनदेन की मात्रा उत्पन्न कर रही हैं।\n\n175\nलेखा-परीक्षित वाणिज्यिक संचालक\n44\nअलग-डोमेन प्रमाणन होस्ट्स\n26\nफ़िल्टर-स्प्लिट प्रॉक्सी जोड़े\n100%\nअनुपालित SSA § 2.G / § 4.C\n0\nलादित प्रामाणिकता रद्दीकरण\nलागू संविदात्मक एवं वैधानिक ढांचा\nएसएसए § 2.G\nव्यावसायिक उपयोग निषेध: Valve कॉर्पोरेशन की पूर्व लिखित अनुमति के बिना सामग्री और सेवाओं का व्यावसायिक उद्देश्यों के लिए शोषण करना स्पष्ट रूप से निषिद्ध है।\nएसएसए § 4.C\nस्वचालन प्रतिबंध: Steam सेवाओं और बाज़ारों के साथ स्क्रिप्ट, ट्रेडिंग बॉट्स, मैक्रोज़ या गैर-मानव-नियंत्रित प्रणालियों के इंटरैक्शन को सख्त रूप से प्रतिबंधित करता है।\nएसएसए § 1.C\nव्यक्तिगत उपयोग आदेश: खातों को केवल व्यक्तिगत उपयोग तक सीमित करता है; स्पष्ट रूप सेSteam उपयोगकर्ता खातों को बेचने, पट्टे पर देने, स्थानांतरित करने या व्यापार करने पर प्रतिबंध लगाता है।\nईयू डीएसए (2022/2065)\nप्रणालीगत जोखिम आकलन (धारा 34/35): बहुत बड़े ऑनलाइन प्लेटफ़ॉर्म (VLOPs) को स्वचालित दुरुपयोग और अनधिकृत व्यावसायिक शोषण से उत्पन्न होने वाले प्रणालीगत जोखिमों का सक्रिय रूप से पता लगाना, उनका आकलन करना और उन्हें कम करना चाहिए।\nखंड II: प्रदर्शित लेजर A — दस्तावेजीकृत लिंक फ़िल्टर विभाजित जोड़े (26 मार्ग)संदर्भ: पूर्व-विभाजित-लेजर\n\nस्प्लिट-डोमेन इवेशन का फोरेंसिक विश्लेषण: Valve के Steam लिंक फ़िल्टर सिस्टम (steamcommunity.com/linkfilter/?url=...), जब कोई अंतिम उपयोगकर्ता एक लिंक पर क्लिक करता है जो एक चिह्नित जुआ या काले बाज़ार प्लेटफ़ॉर्म की ओर ले जाता है, तो Valve एक प्रमुख चेतावनी प्रदर्शित करता है (लिंक अवरुद्ध! ... संभावित रूप से दुर्भावनापूर्ण के रूप में चिह्नित). हालांकि, फोरेंसिक मार्ग-ट्रेसिंग से पता चलता है कि एक वाणिज्यिक प्लेटफ़ॉर्म पर '26' संचालित हो रहे हैं। विभाजित-डोमेन वास्तुकलाजबकि लिंक फ़िल्टर पर प्राथमिक वाणिज्यिक डोमेन BLOCKED के रूप में चिह्नित है, द्वितीयक डोमेन जो Valve के OpenID रिटर्न एंडपॉइंट को होस्ट करता है, CLEAN के रूप में चिह्नित है।Valve के OpenID सर्वर इन प्रॉक्सी होस्ट्स से प्रामाणिकता अनुरोधों को बिना किसी रुकावट के स्वीकार करते हैं, उपभोक्ता सुरक्षा चेतावनी को निष्क्रिय करते हुए और लॉगिन प्रक्रिया जारी रखते हुए।\n\n#\tप्राथमिक वाणिज्यिक डोमेन\tमुख्य फ़िल्टर\tओपनआईडी प्रमाणीकरण प्रॉक्सी डोमेन\tलेखक फ़िल्टर\tRDAP पंजीकृत\tकैप्चर आधार\n01\trollbit.com\tBLOCKED\trbsnin.com\tCLEAN\t2026-09-18\tPASSIVE_CAPTURE\n02\tskin.club\tBLOCKED\tsc-auth.net\tCLEAN\t2019-04-02\tPASSIVE_CAPTURE\n03\thowl.gg\tBLOCKED\thowl.uno\tCLEAN\t2026-08-11\tPASSIVE_CAPTURE\n04\tduelbits.com\tBLOCKED\tswitchflips.com\tCLEAN\t2020-04-21\tPASSIVE_CAPTURE\n05\tcsgofast.com\tBLOCKED\tsteam-login.authtofast.com\tCLEAN\t2026-06-30\tPASSIVE_CAPTURE\n06\tfarmskins.com\tBLOCKED\tsteam.kobal.cc\tCLEAN\t2017-01-07\tPASSIVE_CAPTURE\n07\tcobaltlab.tech\tBLOCKED\tcobaltauth.com\tCLEAN\t2025-01-07\tPASSIVE_CAPTURE\n08\tcsgo.net\tBLOCKED\tcn2.easylot.net\tCLEAN\t2016-09-03\tPASSIVE_CAPTURE\n09\tggdrop.com\tBLOCKED\tggauth.com\tCLEAN\t2023-05-03\tPASSIVE_CAPTURE\n10\trustchance.com\tBLOCKED\thgfuihd.com\tCLEAN\t2019-01-27\tPASSIVE_CAPTURE\n11\tskin.fans\tBLOCKED\tauth.skinfans.com\tCLEAN\t2018-07-16\tPASSIVE_CAPTURE\n12\tskinport.com\tBLOCKED\tskinport.app\tCLEAN\t2020-06-20\tPASSIVE_CAPTURE\n13\tskins.cash\tBLOCKED\tskinscash.live\tCLEAN\t2019-12-05\tPASSIVE_CAPTURE\n14\ttf2hunt.com\tBLOCKED\trstspcl.com\tCLEAN\t2020-08-08\tPASSIVE_CAPTURE\n15\tdaddyskins.com\tBLOCKED\tgo-go-daddy.com\tCLEAN\t2019-01-26\tPASSIVE_CAPTURE\n16\tkey-drop.com\tBLOCKED\tkdauth.com\tCLEAN\t2026-05-13\tPASSIVE_CAPTURE\n17\tclash.gg\tBLOCKED\tclggauth.com\tCLEAN\t2024-09-16\tPASSIVE_CAPTURE\n18\tc5game.com\tBLOCKED\twww.imbastar.com\tCLEAN\t2016-02-27\tPASSIVE_CAPTURE\n19\tswap.gg\tBLOCKED\tswapauth.com\tCLEAN\t2018-10-06\tPASSIVE_CAPTURE\n20\tshadowpay.com\tBLOCKED\tthelogins.com\tCLEAN\t2018-01-22\tPASSIVE_CAPTURE\n21\tcsgocases.com\tBLOCKED\tlog-1n.com\tCLEAN\t2017-11-27\tPASSIVE_CAPTURE\n22\tcsgogem.com\tBLOCKED\tapi.csgem.com\tCLEAN\t2014-03-08\tPASSIVE_CAPTURE\n23\tgamdom.com\tBLOCKED\tlogin.gambldom.com\tCLEAN\t2017-09-24\tPASSIVE_CAPTURE\n24\t12cs.fail\tBLOCKED\tfail.games\tCLEAN\t2021-08-24\tPASSIVE_CAPTURE\n25\tskinsnipe.com\tBLOCKED\tpricing.tradeupspy.com\tCLEAN\t2020-03-11\tPASSIVE_CAPTURE\n26\tcsgobig.com\tBLOCKED\tletmeinbig.com\tCLEAN\t2023-01-20\tPASSIVE_CAPTURE\n\n* नोट: 2026-09-19 और 2026-09-21. पर अनप्रमाणीकृत Steam लिंक फ़िल्टर एंडपॉइंट्स के विरुद्ध निष्क्रिय जाँचें की गईं। कच्ची HTTP प्रतिक्रिया बॉडीज़ और SHA-256 डाइजेस्ट्स को रिपॉजिटरी डेटासेट (steam_tos_assets/linkfilter-2026-09-22.json) में संरक्षित किया गया।\n\nखंड III: प्रदर्शिका खाता बही B — 175 के ऑडिट किए गए वाणिज्यिक संस्थाओं की व्यापक जनगणनासंदर्भ: EX-175-मास्टर-जनगणना\n\nनिम्नलिखित रजिस्टर ऑडिट डेटाबेस में सक्रिय रूप से सत्यापित सभी तृतीय-पक्ष व्यावसायिक प्लेटफ़ॉर्म (175) का विवरण देता है। प्रत्येक रिकॉर्ड में संस्था का नाम, प्राथमिक व्यावसायिक डोमेन, अवलोकित Steam ओपनआईडी प्रमाणीकरण मार्ग, गतिविधि वर्गीकरण, संविदात्मक उल्लंघन मैपिंग (SSA § 2.G, SSA § 4.C, SSA § 1.C), और स्रोत डेटासेट में दर्ज कार्रवाई क्षेत्र शामिल हैं। लेबल \"See dated evidence\" पाठक को सहायक रिकॉर्ड्स की ओर निर्देशित करता है; यह यह स्थापित नहीं करता कि Valve ने कोई कार्रवाई नहीं की। अनुपस्थित कार्रवाई क्षेत्र को 'स्थापित नहीं' के रूप में रिपोर्ट किया गया है।\n\nप्रदर्शनी\tइकाई का नाम और मुख्य डोमेन\tनिगरानी किया गया ऑथ मार्ग / प्रॉक्सी\tवर्गीकरण\tसंविदात्मक उल्लंघन\tValve कार्रवाई\nEX-001\tCSGORoll\ncsgoroll.com\n\t\nwww.csgoroll.com\nDIRECT\n\tSkin Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-002\tCSGOEmpire\ncsgoempire.com\n\t\ncsgoempirelogin4.com\nSPLIT PROXY\n\tCasino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-003\tRollbit\nrollbit.com\n\t\nrbsnin.com\nSPLIT PROXY\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-004\t500 Casino\n500.casino\n\t\nfivezerozero.co\nSPLIT PROXY\n\tLicenced Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-005\tCSGOBig\ncsgobig.com\n\t\ncsgobig.com\nDIRECT\n\tRoulette/Slots\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-006\tCaseDrop\ncasedrop.com\n\t\ncasedrop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-007\tRustReaper\nrustreaper.com\n\t\nrustreaper.com\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-008\tBanditCamp\nbanditcamp.com\n\t\nbanditcamp.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-009\tSkinBox\nskinbox.com\n\t\nskinbox.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-010\tTastyDrop\ntastydrop.com\n\t\ntastydrop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-011\tCSGOPolygon\ncsgopolygon.gg\n\t\ncsgopolygon.gg\nDIRECT\n\tRoulette Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-012\tMagicDrop\nmagicdrop.ru\n\t\nmagicdrop.ru\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-013\tCSDice\ncsdice.com\n\t\ncsdice.com\nDIRECT\n\tDice Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-014\tRustly\nrustly.com\n\t\nrustly.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-015\tSkinOdds\nskinodds.com\n\t\nskinodds.com\nDIRECT\n\tUpgrader Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-016\tCSGOWin\ncsgowin.com\n\t\ncsgowin.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-017\tCSGORun\ncsgorun.net\n\t\ncsgorun.net\nDIRECT\n\tCrash Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-018\tOpenSkins\nopenskins.com\n\t\nopenskins.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-019\tRustBet\nrustbet.com\n\t\nrustbet.com\nDIRECT\n\tRust Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-020\tCSGOMagic\ncsgomagic.com\n\t\ncsgomagic.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-021\tCSGOBounty\ncsgobounty.com\n\t\ncsgobounty.com\nDIRECT\n\tUpgrader/Contract\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-022\tEZSkins\nezskins.com\n\t\nezskins.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-023\tRustCases\nrustcases.com\n\t\nrustcases.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-024\tCSGOReaper\ncsgoreaper.com\n\t\ncsgoreaper.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-025\tCSGOCases\ncsgocases.com\n\t\ncsgocases.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-026\tCSGO-Skins\ncsgo-skins.com\n\t\ncsgo-skins.com\nDIRECT\n\tCase Upgrader\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-027\tCSGONet\ncsgonet.com\n\t\ncsgonet.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-028\tWTFSkins\nwtfskins.com\n\t\nwtfskins.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-029\tCSGOFast\ncsgofast.com\n\t\nsteam-login.authtofast.com\nSPLIT PROXY\n\tRoulette Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-030\tDuelbits\nduelbits.com\n\t\nswitchflips.com\nSPLIT PROXY\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-031\tFlameCases\nflamecases.com\n\t\nflamecases.com\nDIRECT\n\tCase Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-032\tFarmskins\nfarmskins.com\n\t\nsteam.kobal.cc\nSPLIT PROXY\n\tCase Opener\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-033\tCSGOLuck\ncsgoluck.com\n\t\ncsgoluck.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-034\tGamedom\ngamedom.com\n\t\ngamedom.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-035\tSkin.Club\nskin.club\n\t\nsc-auth.net\nSPLIT PROXY\n\tCase Battles\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-036\tDaddySkins\ndaddyskins.com\n\t\ndaddyskins.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-037\tInsane.gg\ninsane.gg\n\t\napi.insane.gg\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-038\tRustix\nrustix.gg\n\t\nrustix.gg\nDIRECT\n\tRust Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-039\tSkins.Club\nskins.club\n\t\nskins.club\nDIRECT\n\tSkin Upgrade\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-040\tCSGOHouse\ncsgohouse.org\n\t\ncsgohouse.org\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-041\tSkinRave\nskinrave.net\n\t\nskinrave.net\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-042\tBloodyCase_GG\nbloodycase.gg\n\t\nbloodycase.gg\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-043\tCSGOClicker\ncsgoclicker.com\n\t\ncsgoclicker.com\nDIRECT\n\tClicker/Upgrade\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-044\tRustBet_GG\nrustbet.gg\n\t\nrustbet.gg\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-045\tCS_Drop\ncs-drop.com\n\t\ncs-drop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-046\tHellStore\nhellstore.net\n\t\nhellstore.net\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-047\tRustLoot\nrustloot.com\n\t\nrustloot.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-048\tCSGO_Case\ncsgo-case.com\n\t\ncsgo-case.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-049\tCS2Skin\ncs2skin.com\n\t\ncs2skin.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-050\tJuice_GG\njuice.gg\n\t\nletmeinjuice.com\nSPLIT PROXY\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-051\tGGDrop\nggdrop.com\n\t\nggauth.com\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-052\tCSGOGem\ncsgogem.com\n\t\ncsgogem.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-053\tRainbet\nrainbet.com\n\t\nservices.rainbet.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-054\tHowl_GG\nhowl.gg\n\t\nhowl.uno\nSPLIT PROXY\n\tSkins Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-055\tChicken_GG\nchicken.gg\n\t\nchicken.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-056\tCSGOCasino_GG\ncsgocasino.gg\n\t\napi.csgocasino.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-057\tHunt_GG\nhunt.gg\n\t\napi.hunt.gg\nDIRECT\n\tSkins Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-058\tCSBattle\ncsbattle.com\n\t\ncsbattle.com\nDIRECT\n\tCase Battles\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-059\tSkinRave_GG\nskinrave.gg\n\t\napi.skinrave.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-060\tCSDouble\ncsdouble.gg\n\t\ncsdouble.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-061\tRustChance\nrustchance.com\n\t\nhgfuihd.com\nSPLIT PROXY\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-062\tRustClash\nrustclash.com\n\t\nrustclash.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-063\tCobaltLab\ncobaltlab.tech\n\t\ncobaltauth.com\nSPLIT PROXY\n\tRust Automation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-064\tRaided_GG\nraided.gg\n\t\napi.raided.gg\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-065\tRustNeo\nrustneo.gg\n\t\nrustneo.gg\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-066\tSplits_GG\nsplits.gg\n\t\nsplits.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-067\tUpgrader_Pro\nupgrader.pro\n\t\nupgauth.space\nSPLIT PROXY\n\tSkin Upgrader\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-068\tSkinFans\nskin.fans\n\t\nauth.skinfans.com\nSPLIT PROXY\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-069\tHotPizza\nhotpizza.one\n\t\nhotpizza.one\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-070\tG4Skins\ng4skins.com\n\t\nauth.g4s.to\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-071\t12CS_Fail\n12cs.fail\n\t\n12cs.fail\nDIRECT\n\tCrash Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-072\tTF2Royal\ntf2royal.com\n\t\ntf2auth.com\nSPLIT PROXY\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-073\tTF2Easy\nwww.tf2easy.com\n\t\nwww.tf2easy.com\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-074\tTF2Hunt\ntf2hunt.com\n\t\nrstspcl.com\nSPLIT PROXY\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-075\tTF2Bet\ntf2.bet/coinflip\n\t\ntf2.bet\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-076\tTF2Blaze\ntf2blaze.com\n\t\ntf2blaze.com\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-077\tOpenStars_GG\nopenstars.gg\n\t\nopenstars.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-078\tShuffle_Com\nshuffle.com\n\t\nshuffle.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-079\tSkins.com\nskins.com\n\t\napi.skins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-080\tWhite.Market\nwhite.market\n\t\nwhite.market\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-081\tBuff.Market\nbuff.market\n\t\nbuff.market\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-082\tAvan.Market\navan.market\n\t\navan.market\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-083\tCS.MONEY\ncs.money\n\t\nauth.dota.trade\nSPLIT PROXY\n\tTrading Engine\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-084\tUUSkins\nuuskins.com\n\t\nuuskins.com\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-085\tYouPin898\nyoupin898.com\n\t\nyoupin898.com\nDIRECT\n\tMass Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-086\tMoon.Market\nmoon.market\n\t\nmoon.market\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-087\tCSFloat\ncsfloat.com\n\t\ncsgofloat.com\nSPLIT PROXY\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-088\tSkin.Land\nskin.land\n\t\nauth.skin.land\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-089\tC5Game\nc5game.com\n\t\nc5game.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-090\tHaloSkins\nhaloskins.com\n\t\nhaloskins.com\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-091\tBuff.163\nbuff.163.com\n\t\nbuff.163.com\nDIRECT\n\tCorporate Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-092\tWaxpeer\nwaxpeer.com\n\t\nwaxpeer.com\nDIRECT\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-093\tCS.MONEY Bot\ncs.money\n\t\nauth.dota.trade\nSPLIT PROXY\n\tBot Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-094\tMarket.CSGO\nmarket.csgo.com\n\t\ndota2.net\nSPLIT PROXY\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-095\tSkinport\nskinport.com\n\t\nskinport.app\nSPLIT PROXY\n\tRegulated Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-096\tSkinFlow\nskinflow.gg\n\t\napi.skinflow.gg\nDIRECT\n\tMarketplace/Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-097\tDMarket\ndmarket.com\n\t\ndmarket.com\nDIRECT\n\tUS Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-098\tSkin.place\nskin.place\n\t\napi.skin.place\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-099\tSkinsMonkey\nskinsmonkey.com\n\t\nskinsmonkey.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-100\tSkinBaron\nskinbaron.de\n\t\nskinbaron.com\nSPLIT PROXY\n\tCorporate Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-101\tSteam\nsteamcommunity.com/market\n\t\nsteamcommunity.com/market\nDIRECT\n\tOfficial Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-102\tRustTM\nrust.tm\n\t\ndota2.net\nSPLIT PROXY\n\tRust Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-103\tPirateSwap\npirateswap.com\n\t\nlogin.pirateswap.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-104\tMannco.Store\nmannco.store\n\t\nmannco.store\nDIRECT\n\tTF2 Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-105\tSkinSwap\nskinswap.com\n\t\napi.skinswap.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-106\tLootFarm\nlootfarm.com\n\t\nlootfarm.com\nDIRECT\n\tTrading Platform\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-107\tRustskins\nrustskins.com\n\t\nrustskins.com\nDIRECT\n\tRust Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-108\tExeSkins\nexeskins.com\n\t\nexeskins.com\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-109\tBalticSkins\nbalticskins.com\n\t\nbalticskins.com\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-110\tCS.Trade\ncs.trade\n\t\ncs.trade\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-111\tRapidSkins\nrapidskins.com\n\t\napi.rapidskins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-112\tTradeIt\ntradeit.gg\n\t\nconnect-tradeit.com\nSPLIT PROXY\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-113\tKrakatoa\nkrakatoa.com\n\t\nkrakatoa.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-114\tShadowPay\nshadowpay.com\n\t\nshadowpay.com\nDIRECT\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-115\t49skins\n49skins.com\n\t\napi.49skins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-116\tSkinVault\nskinvault.gg\n\t\napi.skinvault.gg\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-117\tAim Market\naim.market\n\t\naim.market\nDIRECT\n\tSkins Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-118\tSkinout\nskinout.gg\n\t\nauth.skinout.gg\nDIRECT\n\tInstant Sell Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-119\tNTSkins\nntskins.com\n\t\nntskins.com\nDIRECT\n\tSkins Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-120\tIGXE\nigxe.cn\n\t\nigxe.cn\nDIRECT\n\tChinese Powerhouse\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-121\tSwap.gg\nswap.gg\n\t\nswap.gg\nDIRECT\n\tAutomated Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-122\tBitskins\nbitskins.com\n\t\nbitskins.com\nDIRECT\n\tCash-out Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-123\tGamerPay\ngamerpay.gg\n\t\ngamerpay.gg\nDIRECT\n\tP2P Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-124\tTF2Mart\ntf2mart.com\n\t\ntf2mart.com\nDIRECT\n\tTF2 Automation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-125\tSkinBid\nskinbid.com\n\t\nskinbid.com\nDIRECT\n\tSkin Auctions\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-126\tLootBear\nlootbear.com\n\t\nlootbear.com\nDIRECT\n\tSkin Rental\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-127\tBackpack.tf\nbackpack.tf\n\t\nbackpack.tf\nDIRECT\n\tTF2 Valuation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-128\tScrap.tf\nscrap.tf\n\t\nscrap.tf\nDIRECT\n\tTF2 Scrap Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-129\tMarketplace.tf\nmarketplace.tf\n\t\nmarketplace.tf\nDIRECT\n\tTF2 Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-130\tSTNTrading\nstntrading.eu\n\t\nstntrading.eu\nDIRECT\n\tTF2 Botnet\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-131\tSkins.Cash\nskins.cash\n\t\nskinscash.live\nSPLIT PROXY\n\tInstant Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-132\tSkinWallet\nskinwallet.com\n\t\nskinwallet.com\nDIRECT\n\tInstant Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-133\tDota2Market\ndota2market.com\n\t\ndota2market.com\nDIRECT\n\tDota 2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-134\tCSGO.NET\ncsgo.net\n\t\ncn2.easylot.net\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-135\tCybershoke\ncybershoke.net\n\t\nauth.cybershoke.net\nDIRECT\n\tCommunity Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-136\tXPlay_GG\nxplay.gg\n\t\nxplay.gg\nDIRECT\n\tServer Network\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-137\tFastCup\nfastcup.net\n\t\napi.fastcup.net\nDIRECT\n\tMatchmaker Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-138\tEsportal\nesportal.com\n\t\nesportal.com\nDIRECT\n\tMatchmaking Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-139\tGamersClub\ngamersclub.com.br\n\t\ngamersclub.com.br\nDIRECT\n\tLATAM Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-140\tLeetify\nleetify.com\n\t\nleetify.com\nDIRECT\n\tSaaS Analytics\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-141\tScope_GG\nscope.gg\n\t\nscope.gg\nDIRECT\n\tSaaS Analytics\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-142\tTradeUpSpy\ntradeupspy.com\n\t\napi.tradeupspy.com\nDIRECT\n\tSaaS Tools\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-143\tEpidemic_GG\nepidemic.gg\n\t\nepidemic.gg\nDIRECT\n\tSaaS Tools\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-144\tCSDeals\ncs.deals\n\t\napi.cs.deals\nDIRECT\n\tMarketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-145\tPricempire\npricempire.com\n\t\npricempire.com\nDIRECT\n\tSaaS Price DB\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-146\tCS2Stash\ncs2stash.com\n\t\ncs2stash.com\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-147\tCSGOSkins\ncsgoskins.gg\n\t\ncsgoskins.gg\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-148\tSteamAnalyst\nsteamanalyst.com\n\t\nsteamanalyst.com\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-149\tSteamCardExchange\nsteamcardexchange.net\n\t\nsteamcardexchange.net\nDIRECT\n\tTrading Exchange\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-150\tDotaBuff\ndotabuff.com\n\t\ndotabuff.com\nDIRECT\n\tSaaS Tracker\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-151\tTracker_GG\ntracker.gg\n\t\ntracker.gg\nDIRECT\n\tSaaS Tracker\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-152\tFSB Market (an anonymized label; the original name is withheld here)\nFSB Market\n\t\nFSB Market\nDIRECT\n\tMass Blackmarket\tSSA § 2.G, SSA § 4.C, SSA § 1.C\tSee dated evidence\nEX-153\tFunPay\nfunpay.com\n\t\nfunpay.com\nDIRECT\n\tAccount Exchange\tSSA § 2.G, SSA § 4.C, SSA § 1.C\tSee dated evidence\nEX-154\tPlayerAuctions\nplayerauctions.com\n\t\nplayerauctions.com\nDIRECT\n\tGrey Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-155\tEldorado.gg\neldorado.gg\n\t\neldorado.gg\nDIRECT\n\tAccount Portal\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-156\tG2A\ng2a.com\n\t\ng2a.com\nDIRECT\n\tMass Key Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-157\tKinguin\nkinguin.net\n\t\nkinguin.net\nDIRECT\n\tMass Key Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-158\tG2G.com\ng2g.com\n\t\ng2g.com\nDIRECT\n\tVirtual Services\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-159\tPlayerup\nplayerup.com\n\t\nplayerup.com\nDIRECT\n\tAccount Broker\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-160\tZ2U.com\nz2u.com\n\t\nwww.z2u.com\nDIRECT\n\tReady-Account Hub\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-161\tSmurfHub\nsmurfhub.net\n\t\nsmurfhub.net\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-162\tSmurfAccounts\nsmurfaccounts.com\n\t\nsmurfaccounts.com\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-163\tBuyCSGORank\nbuycsgorank.com\n\t\nbuycsgorank.com\nDIRECT\n\tRank Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-164\tCSGOSmurfKings\ncsgosmurfkings.com\n\t\ncsgosmurfkings.com\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-165\tSmurfStore_Co\nsmurfstore.co\n\t\nsmurfstore.co\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-166\tSteamLvlUp\nsteamlvlup.com\n\t\nsteamlvlup.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-167\tSteamLevels\nsteamlevels.com\n\t\nsteamlevels.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-168\tLevelSteam\nlevelsteam.com\n\t\nlevelsteam.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-169\tSteamLevelU\nsteamlevelu.com\n\t\nsteamlevelu.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-170\tEloKing\neloking.com\n\t\neloking.com\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-171\tBoosteria\nboosteria.org\n\t\nboosteria.org\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-172\tOvergear\novergear.com\n\t\novergear.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-173\tBlazingBoost\nblazingboost.com\n\t\nblazingboost.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-174\tDota2Boost\ndota2boost.com\n\t\ndota2boost.com\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-175\tBuyBoost\nbuyboost.com\n\t\nbuyboost.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nखंड IV: तकनीकी वास्तुकला और प्रमाणीकरण तंत्रसंदर्भ: TECH-ANALYSIS-01\n\n1. ओपनआईडी में डोमेन स्वामित्व सत्यापन की अनुपस्थिति 2.0: Valve द्वारा ओपनआईडी 2.0 प्रोटोकॉल का कार्यान्वयन (https://steamcommunity.com/openid/login) का मूल्यांकन करता है openid.return_to और openid.realm पैरामीटरों को पूर्व डेवलपर पंजीकरण, क्रिप्टोग्राफिक चुनौती सत्यापन या डोमेन स्वामित्व सत्यापन की आवश्यकता के बिना। कोई भी वाणिज्यिक ऑपरेटर उपयोगकर्ताओं को Valve की लॉगिन स्क्रीन पर भेज सकता है और क्रिप्टोग्राफिक रूप से हस्ताक्षरित पहचान पुष्टि (जिसमें 64-बिट SteamID शामिल है) प्राप्त कर सकता है, जिसे किसी भी डोमेन पर पुनर्निर्देशित किया जा सकता है।\n\n2. कार्यक्रमगत इन्वेंटरी पूछताछ एवं API कुंजी दुरुपयोग: एक बार OpenID के माध्यम से उपयोगकर्ता प्रमाणीकरण की पुष्टि हो जाने पर, ऑपरेटर सार्वजनिक और भागीदार वेब API एंडपॉइंट्स को क्वेरी करते हैं (IEconItems_730/GetPlayerItems) वास्तविक समय में इन्वेंटरी परिसंपत्तियों को अनुक्रमित करने के लिए। स्वचालित ट्रेडिंग नेटवर्क प्रोग्रामेबल सत्र टोकन का उपयोग करके पीयर-टू-पीयर (P2P) व्यापार प्रस्ताव जमा करने, पोल करने और स्वीकार करने के लिए, सीधे SSA § 4.C द्वारा गैर-मानवीय अंतःक्रिया पर लगाए गए प्रतिबंध का उल्लंघन करते हैं।\n\n3. लिंक फ़िल्टर विषमता: उपभोक्ता-सामना करने वाले डोमेन चेतावनियों और पूरी तरह से कार्यशील प्रमाणीकरण एंडपॉइंट्स का सह-अस्तित्व एक नियामक विरोधाभास उत्पन्न करता है: Valve की सुरक्षा टेलीमेट्री इन ऑपरेटरों को \"संभावित रूप से दुर्भावनापूर्ण\" के रूप में वर्गीकृत करती है, फिर भी Valve का प्रमाणीकरण अवसंरचना उनके उपयोगकर्ता आधार को प्रमाणित करना जारी रखती है।\n\nसाक्ष्य पद्धति एवं कब्जे की श्रृंखला घोषणा\n\nयह दस्तावेज़ अनधिकृत नेटवर्क कैप्चर, ऐतिहासिक RDAP रजिस्ट्री क्वेरीज़, और सत्यापित क्रिप्टोग्राफिक हैश मैनिफेस्ट से उत्पन्न किया गया था। किसी भी उपयोगकर्ता के लॉगिन क्रेडेंशियल्स का समझौता-परीक्षण या प्रसंस्करण नहीं किया गया। सभी निष्कर्ष सितंबर 2026. तक के अवलोकनीय उत्पादन नेटवर्क की स्थिति को दर्शाते हैं। यह कार्य न्यायिक, नियामक और सार्वजनिक पूछताछों के लिए तैयार एक गैर-पक्षपाती तकनीकी प्रदर्शनी के रूप में कार्य करता है।\n\nसारांश: SHA-256 सत्यापित\nc507c9025f93da0aadaf395c4d8882f25973211c318ee8e9b6f18a5b3755e050\nसंग्रह: खुला कानूनी रिकॉर्ड\nद्वारा जारी एवं हस्ताक्षरित: phishdestroy.io · फोरेंसिक अनुसंधान गठबंधन\nकानूनी स्थिति: सभी अधिकार मानवता को समर्पित · CC0 सार्वभौमिक सार्वजनिक डोमेन",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "फोरेंसिक ऑडिट अधिनियम और नियामक प्रदर्शनी"
          }
        ],
        "links": []
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/hi/regulatory_act_print.content.json",
      "export_json_sha256": "70562516f86cb0da043abdf6fac000aee9f8989bd6e04128381f4833514fe1ef"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "hi/security_timeline.html",
      "language": "hi",
      "title": "सुरक्षा समयरेखा — द Steam का दस्तावेज़",
      "source_url": "https://phishdestroy.io/steam_dossier/hi/security_timeline",
      "source_html_sha256": "30794f6f6f7df2382a839ea6f4a0f1aa937410b8b6b855fdb5fde424968a232a",
      "exported_at": "2026-09-29T00:22:47.916Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "security_timeline.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/hi/security_timeline.pdf?v=print-20260929-v5",
        "sha256": "47e76c86eec192b1a4d4afc64d2a8aa73d666e8aef7d3b88c34da6ab35df91ca",
        "bytes": 319863,
        "pages": 6
      },
      "integrity": {
        "signed_object": "security_timeline.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "security_timeline.content.json.asc",
        "digest_file": "security_timeline.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify security_timeline.content.json.asc security_timeline.content.json",
          "sha256sum -c security_timeline.content.json.sha256"
        ]
      },
      "content": {
        "text": "सुरक्षा रिकॉर्डप्रदर्शनी / 16 प्रविष्टियाँ\n\n2018 — 2026\n\nसुरक्षा समयरेखा — 2018 से 2026\n\nसुरक्षा बदल गई। रिकॉर्ड का पालन करें।\n\nयह अनुभाग क्या प्रमाणित करता है\n\nयह कालानुक्रमिक रिकॉर्ड Steam के ट्रेड और ऑथेंटिकेशन स्टैक में सुरक्षा संशोधनों के आठ वर्षों को पुनर्निर्मित करता है। यह 2018 के '7-' डे ट्रेड होल्ड कार्यान्वयन, 2023 वेब API की कुंजी मोबाइल पुष्टि, और 2026 सत्र टोकन की अप्रचलन को दस्तावेजीकृत बाईपास तकनीकों के संदर्भ में ट्रैक करता है। यह समयरेखा स्थापित करती है कि प्लेटफ़ॉर्म अपडेट्स ज्ञात शोषण मार्गों से लगातार पीछे रहे, जबकि वाणिज्यिक ऑपरेटरों के लिए संरचनात्मक लाभ बनाए रखे गए।\n\n← कार्यकारी ब्रीफिंग पर वापस\n\nव्यापार लॉक। लॉगिन नियंत्रण। API प्रतिबंध। क्या बदला—और स्रोत वास्तव में क्या स्थापित करते हैं, इसका एक पुराना रिकॉर्ड।\n\nसमयरेखा का अन्वेषण करें ↓\nआठ साल। एक रिकॉर्ड।16जांच के लिए मील के पत्थर\n\nप्रत्येक प्रविष्टि अपनी जमा की गई तारीख और स्रोत को बनाए रखती है। सत्यापन इसके साथ दिखाया जाता है।\n\nसमीक्षित / 24 सित्बंर 2026\n10सत्यापित कार्यक्रम और तिथि\n06आंशिक रूप से सत्यापित\n00स्रोत असंगति\n00स्रोत आवश्यक है\nइस रिकॉर्ड को कैसे पढ़ें\n\nसत्यापित कार्यक्रम और तिथि: दोनों एक पठनीय प्राथमिक स्रोत द्वारा समर्थित। आंशिक रूप से सत्यापित: एक संबंधित परिवर्तन दर्ज किया गया है, लेकिन तारीख या दायरा अनसुलझा है। स्रोत असंगति: संलग्न सामग्री प्रस्तुत दावे का समर्थन नहीं करती है। स्रोत आवश्यक है: इस समीक्षा में कोई मेल खाने वाला दिनांकित स्रोत सत्यापित नहीं किया गया। एक अनसुलझी प्रविष्टि इस बात का प्रमाण नहीं है कि कोई घटना नहीं हुई।\n\nअनसुलझी प्रविष्टियों पर दिनांक प्रस्तुत तिथियाँ हैं, सत्यापित जारी तिथियाँ नहीं। मूल जांच पाठ को पुनर्लिखित नहीं किया गया है।\n\nकालक्रम\n01 — 16\nरिकॉर्ड खोजेंविषयसाक्ष्यआदेश\n\n16 16 प्रविष्टियों में से · नवीनतम पहले\n\n202609-01जमा करने की तारीख\nसमुदायआंशिक रूप से सत्यापित\nसमूह चैट में संदिग्ध संदेश चेतावनियाँ\n\nएक आधिकारिक बीटा सूचना 31 अगस्त को इस सुविधा की पुष्टि करती है। प्रदान किए गए 1 सितंबर के स्थिर-रिलीज़ की तारीख को अभी भी अपनी विशिष्ट रिलीज़ नोट की आवश्यकता है।\n\nSteam क्लाइंट बीटा — अगस्त 31तारीख ↗संग्रहीत 2026-03-13 ↗\nमूल प्रविष्टि और सबमिट किया गया लिंक\n\nस्वचालित संदिग्ध चैट फ़्लैगिंग\n\nसबमिट किए गए स्रोत का निरीक्षण करें ↗\n202601-16सत्यापित तिथि\nAPIसत्यापित कार्यक्रम और तिथि\nप्रकाशक कुंजियों के लिए सूक्ष्म अनुमतियाँ और आईपी व्हाइटलिस्टिंग (Valve घोषणा)\n\n16 जनवरी 2026,Valve ने एक आधिकारिक Steamworks घोषणा प्रकाशित की (नया: वेब API कुंजियों के लिए बेहतर अनुमतियाँ और नियंत्रण) वेब API कुंजियों को अलग-अलग समूहों में विभाजित करने की अनुमति देने वाले नए सूक्ष्म अनुमति उपकरणों की पुष्टि करते हुए (सामान्य, माइक्रोट्रांज़ैक्शंस, अर्थव्यवस्था, और बिक्री डेटा), कुंजियों को विशिष्ट ऐप आईडी तक सीमित करें, और सर्वर आईपी व्हाइटलिस्टिंग लागू करें।\n\nचौंकाने वाला दोहरा मापदंड: यह आधिकारिक घोषणा स्थापित करती है कि Valve ने सूक्ष्म API अनुमतियों और आईपी प्रतिबंधों के लिए तकनीकी अवसंरचना को पूरी तरह से विकसित कर लिया है, लेकिन जानबूझकर उन्हें नियमित उपयोगकर्ता खातों से रोकता है (steamcommunity.com/dev/apikey)सामान्य उपयोगकर्ता API कुंजियाँ एकल-खंड, 'सब या कुछ नहीं' प्रमाण-पत्र बनी रहती हैं, जिनमें कोई आईपी व्हाइटलिस्टिंग नहीं होती—और यही तकनीकी चूक है जो करोड़ों डॉलर के API व्यापार अवरोधन उद्योग को संभव बनाती है।\n\nValve घोषणा — नया: वेब API कुंजियों के लिए बेहतर अनुमतियाँ और नियंत्रण (16, 1 जनवरी 2026) ↗· दस्तावेज़ीकरण: Steamworks वेब API प्रमाणीकरण ↗\nमूल प्रविष्टि और सबमिट किया गया लिंक\n\nस्टीमवर्क्स वेब API सूक्ष्म दायरे\n\nValve की आधिकारिक Steamworks घोषणा (493839547938902179) देखें ↗\n202507-15सत्यापित तिथि\nव्यापारसत्यापित कार्यक्रम और तिथि\nCS2 ट्रेड्स को सात-दिवसीय रिवर्सल विंडो मिलती है।\n\nValve की पुरानी घोषणा पिछले सात दिनों के काउंटर-स्ट्राइक आइटम ट्रेड्स को उलटने की शुरुआत करती है। जबकि यह हाईजैकिंग को कम करने के लिए डिज़ाइन किया गया था, तीसरे पक्ष के आर्थिक ऑडिट (सीएसमार्केटकैप ↗) ने एक रिकॉर्ड किया $104M (–25%) संकुचन नकद-व्यापार व्यवधान के कारण 24 घंटों के भीतर बाजार पूंजीकरण में। जैसा कि द्वारा विश्लेषण किया गया स्किनवॉल्ट ↗, रिवर्सल ट्रिगर होने पर खाते पर स्वचालित रूप से 30-दिन का ट्रेड लॉकआउट लागू हो जाता है। गर्मियों में 2026, Valve ने वैश्विक मध्यरात्रि UTC रीसेट से प्रत्येक आइटम के लिए अलग-अलग मिनट टाइमर पर स्विच किया (Skin.land ↗).\n\nValve — 15 जुलाई 2025 घोषणा ↗· सीएसमार्केटकैप विश्लेषण ↗\nमूल प्रविष्टि और सबमिट किया गया लिंक\n\nCS2 व्यापार सुरक्षा / रिवर्सल विंडो\n\nसबमिट किए गए स्रोत का निरीक्षण करें ↗\n202505-14सत्यापित तिथि\nप्रमाणीकरणसत्यापित कार्यक्रम और तिथि\nValve एसएमएस लीक के संबंध में खाता सुरक्षा चेतावनी प्रकाशित करता है\n\nValve 14, 2025, पर जारी आधिकारिक घोषणा में खाते की सुरक्षा और SMS-आधारित प्रमाणीकरण उपकरणों को संबोधित किया गया है। जबकि यह सूचना SMS लीक पर केंद्रित है और पुष्टि करती है कि किसी भी प्रणाली में कोई उल्लंघन नहीं हुआ, यह प्रस्तुत तिथि पर एक आधिकारिक सुरक्षा अपडेट के रूप में कार्य करती है। Steam\n\nValve — आपके Steam खाते की सुरक्षा के बारे में एक सूचना ↗\nमूल प्रविष्टि और सबमिट किया गया लिंक\n\nखाता सुरक्षा घोषणा\n\nसबमिट किए गए स्रोत का निरीक्षण करें ↗\n202410-02सत्यापित तिथि\nव्यापारसत्यापित कार्यक्रम और तिथि\nपुनः व्यापार या पुनः विपणन से सात दिन पहले\n\nरिलीज़ नोट्स में इन-गेम स्टोर के माध्यम से प्राप्त वस्तुएँ शामिल हैं, जिनमें आर्मरी, ट्रेड ऑफ़र्स और कम्युनिटी मार्केट शामिल हैं। दस्तावेज़ित दायरा केवल आर्मरी वस्तुओं तक सीमित नहीं है।\n\nValve — 10/2/2024 के लिए रिलीज़ नोट्स ↗\nमूल प्रविष्टि और सबमिट किया गया लिंक\n\nCS2 द आर्मरी / 7-डे होल्ड\n\nसबमिट किए गए स्रोत का निरीक्षण करें ↗\n202409-18जमा करने की तारीख\nव्यापारआंशिक रूप से सत्यापित\nनए डिवाइस प्रतिबंधों की पुष्टि सहायता पृष्ठों पर की गई।\n\nSteam की आधिकारिक सहायता दस्तावेज़ीकरण पुष्टि करती है कि जब कोई नया डिवाइस, जिसे कम से कम 7 दिनों के लिए अधिकृत नहीं किया गया हो, लॉग इन करता है, तो 7-पर डे ट्रेडिंग प्रतिबंध लागू होता है। हालांकि सितंबर 18, के 2024, की सटीक रोलआउट तिथि चेंजलाग मील का पत्थर के रूप में दर्ज नहीं है, फिर भी इस कार्यक्षमता का पूरा दस्तावेज़ीकरण उपलब्ध है।\n\nSteam समर्थन — व्यापार और बाजार प्रतिबंध ↗\nमूल प्रविष्टि और सबमिट किया गया लिंक\n\nनया डिवाइस लॉगिन व्यापार प्रतिबंध\n\nसबमिट किए गए स्रोत का निरीक्षण करें ↗\n202402-14जमा करने की तारीख\nसमुदायआंशिक रूप से सत्यापित\n2024 में नाम-परिवर्तन ट्रेड कूलडाउन लागू किया गया।\n\nसमुदाय और डेवलपर रिकॉर्ड्स पुष्टि करते हैं कि 2024, Valve ने प्रोफ़ाइल नाम बदलने के तुरंत बाद तेज़ी से नकली पहचान धोखाधड़ी को कम करने के लिए एक बिना घोषणा किए गए 2-से4 घंटे के ट्रेड कूलडाउन को लागू किया। क्योंकि Valve ने इस प्रतिबंध के लिए कोई आधिकारिक प्रेस विज्ञप्ति, क्लाइंट चेंजलॉग या सहायता लेख प्रकाशित नहीं किया, इसलिए प्रस्तुत फरवरी 14 की तारीख औपचारिक रूप से सत्यापित नहीं है; Steam वर्कशॉप गाइड आधिकारिक Valve दस्तावेज़ीकरण के बजाय अप्रत्यक्ष सामुदायिक पुष्टि के रूप में कार्य करती है।\n\nSteam कार्यशाला मार्गदर्शिका (अप्रत्यक्ष पुष्टिकरण) — नाम परिवर्तन प्रतिबंध का विवरण ↗\nमूल प्रविष्टि और सबमिट किया गया लिंक\n\nप्रोफ़ाइल नाम / अवतार परिवर्तन रोक\n\nसबमिट किए गए स्रोत का निरीक्षण करें ↗\n202312-04सत्यापित तिथि\nAPIसत्यापित कार्यक्रम और तिथि\nकुंजी निर्माण के लिए मोबाइल पुष्टि आवश्यक है।\n\nवेब API कुंजी निर्माण के लिए अनिवार्य Steam गार्ड मोबाइल पुष्टि का परिचय तीसरे पक्ष के डेवलपर लाइब्रेरियों द्वारा दस्तावेजीकृत अनुसार 2023, के अंत में हुआ था। दिसंबर 4, 2023, की सटीक तारीख डेवलपर समुदाय के भीतर देखे गए रोलआउट अवधि को दर्शाती है।\n\nरखरखाव संबंधी दस्तावेज़ीकरण — मार्च 2024 ↗संचित 2026-09-24 ↗\nमूल प्रविष्टि और सबमिट किया गया लिंक\n\nAPI कुंजियों के लिए मोबाइल पुष्टि\n\nसबमिट किए गए स्रोत का निरीक्षण करें ↗\n202310-24सत्यापित तिथि\nडेवलपरसत्यापित कार्यक्रम और तिथि\nगेम बिल्ड्स को लाइव सेट करने के लिए अनिवार्य 2FA प्रभावी हो गया।\n\nValve की आधिकारिक Steamworks घोषणा 10 10, 2023, पुष्टि करती है कि 10 24, 2023, से किसी भी खाते द्वारा जारी किए गए एप्लिकेशन की डिफ़ॉल्ट शाखा पर बिल्ड लाइव सेट करने के लिए SMS या Steam मोबाइल ऐप के माध्यम से परिवर्तन को अधिकृत करना अनिवार्य होगा। इस परिवर्तन ने सीधे SetAppBuildLive वेब API को अपडेट किया।\n\nस्टीमवर्क्स — बिल्ड और उपयोगकर्ताओं के प्रबंधन के लिए सुरक्षा सुधार ↗संग्रहीत 2025-12-03 ↗\nमूल प्रविष्टि और सबमिट किया गया लिंक\n\nगेम बिल्ड पब्लिकेशन्स के लिए एसएमएस एमएफए\n\nसबमिट किए गए स्रोत का निरीक्षण करें ↗\n202307-12जमा करने की तारीख\nसमुदायआंशिक रूप से सत्यापित\nकस्टम जीवनी सामग्री चेतावनियाँ जो समुदाय द्वारा देखी गईं\n\nSteam 2023 में जुलाई से शुरू होने वाली समुदाय रिपोर्टों में यह दस्तावेजीकरण किया गया है कि बाहरी लिंक या ट्रिगर शब्दों वाले कस्टम प्रोफ़ाइल जीवनी में स्वचालित सामग्री चेतावनियाँ दिखने लगीं। 7 जुलाई की 12, 2023, की सबमिट की गई तारीख Steam समुदाय मंचों पर उपयोगकर्ता रिपोर्टों की प्रारंभिक लहर से मेल खाती है।\n\nSteam सामुदायिक मंच — जैव सामग्री चेतावनी रिपोर्टें ↗\nमूल प्रविष्टि और सबमिट किया गया लिंक\n\nकस्टम जीवनी सामग्री चेतावनी\n\nसबमिट किए गए स्रोत का निरीक्षण करें ↗\n202301-25जमा करने की तारीख\nसमुदायआंशिक रूप से सत्यापित\nप्रोफ़ाइल लिंक फ़िल्टरिंग और संपादन कूलडाउन सक्रिय हैं\n\nSteamकी आधिकारिक सहायता दस्तावेज़ीकरण पुष्टि करता है कि कस्टम जीवनी में लिंक फ़िल्टर किए जाते हैं, और अपमानजनक नाम या अवतार परिवर्तन संपादन प्रतिबंध को ट्रिगर कर सकते हैं। जबकि 1 जनवरी को लागू होने वाले 4-घंटे के कूलडाउन का सटीक रोलआउट 25, 2023, पर देखा गया प्रारंभिक चरण दर्शाता है, लिंक-फ़िल्टरिंग तंत्र स्वयं सबमिट किए गए सहायता पृष्ठ पर पूरी तरह सक्रिय है।\n\nSteam समर्थन — प्रोफ़ाइल नाम और अवतार प्रतिबंध ↗\nमूल प्रविष्टि और सबमिट किया गया लिंक\n\nप्रोफ़ाइल लिंक हटाया गया / कूलडाउन\n\nसबमिट किए गए स्रोत का निरीक्षण करें ↗\n202210-24सत्यापित तिथि\nप्रमाणीकरणसत्यापित कार्यक्रम और तिथि\nSteam क्लाइंट का OAuth रिफ्रेश और एक्सेस टोकन में संक्रमण\n\nValve के प्रमुख क्लाइंट और अक्टूबर में मोबाइल ऐप अपडेट्स में, 2022 ने Steam प्रमाणीकरण प्रणाली में व्यापक सुधार किया। पुराने सत्र कुकी ढांचे को OAuth-आधारित एक्सेस और रिफ्रेश टोकन से प्रतिस्थापित किया गया, और सक्रिय सत्रों को मैन्युअल रूप से रद्द करने की अनुमति देने के लिए सक्रिय अधिकृत उपकरणों की एक सूची पेश की गई।\n\nValve — Steam मोबाइल ऐप अपडेट और प्रमाणीकरण में व्यापक सुधार ↗\nमूल प्रविष्टि और सबमिट किया गया लिंक\n\nSteam लॉगिन में व्यापक सुधार / कुकी संक्षेपण\n\nValve निरीक्षण घोषणा ↗\n202210-12सत्यापित तिथि\nप्रमाणीकरणसत्यापित कार्यक्रम और तिथि\nक्यूआर साइन-इन और अधिकृत-डिवाइस प्रबंधन\n\nValve की 12 अक्टूबर की घोषणा QR साइन-इन, साइन-इन की स्वीकृति या अस्वीकृति, और एक डिवाइस सूची का वर्णन करती है जो खाते की पहुँच रद्द कर सकती है।\n\nValve — अपडेटेड Steam मोबाइल ऐप अब उपलब्ध है। ↗\nमूल प्रविष्टि और सबमिट किया गया लिंक\n\nSteam मोबाइल ऐप 3.0 / QR लॉगिन\n\nसबमिट किए गए स्रोत का निरीक्षण करें ↗\n202205-10जमा करने की तारीख\nAPIआंशिक रूप से सत्यापित\nसार्वजनिक API सूची से ट्रेड रद्दीकरण एंडपॉइंट्स हटा दिए गए\n\nडेवलपर रिकॉर्ड्स पुष्टि करते हैं कि मई में 2022, Valve ने वेब API से IEconService/CancelTradeOffer और DeclineTradeOffer जैसे ट्रेड मैनेजमेंट एंडपॉइंट्स को चुपचाप हटा दिया (node-steam-tradeoffer-manager #325 में दस्तावेजीकृत)। हालाँकि ये विधियाँ निजी क्लाइंट प्रोटोकॉल में कार्यशील बनी हुई हैं, 10, 2022, की तारीख स्कैम पैनलों से निपटने के लिए सार्वजनिक वेब एपीआई से इनके हटाए जाने का संकेत देती है।\n\nडेवलपर चर्चा — मुद्दा #325 (CancelTradeOffer हटाया गया) ↗· स्टीमवर्क्स वेब API — IEconService दस्तावेज़ीकरण ↗\nमूल प्रविष्टि और सबमिट किया गया लिंक\n\nव्यापार रद्दीकरण एंडपॉइंट्स का निष्कासन\n\nnode-steam-tradeoffer-manager समस्या #325 ↗\n202005-25सत्यापित तिथि\nव्यापारसत्यापित कार्यक्रम और तिथि\nडोटा 2 आइटम्स को सात-दिन का ट्रेडिंग कूलडाउन मिलता है।\n\n25, 2020, के साथ-साथ अंतरराष्ट्रीय 10 बैटल पास रिलीज़ (blog.dota2.com/2020/05/the-international-10-battle-pass/) के अवसर पर, Valve ने Dota 2 आइटम्स पर 7--दिन के ट्रेड लॉक को लागू किया, जो 2018 Counter-Strike नीति के अनुरूप है। यह प्रतिबंध सभी ट्रेड किए गए आइटम्स और मार्केट से की गई खरीदारी पर लागू होता है।\n\nडोटा 2 समुदाय — ट्रेड लॉक और TI10 क्लाइंट अपडेट ↗\nमूल प्रविष्टि और सबमिट किया गया लिंक\n\nडोटा 2 / 7-डे ट्रेड लॉक\n\nसबमिट किए गए स्रोत का निरीक्षण करें ↗\n201803-29सत्यापित तिथि\nव्यापारसत्यापित कार्यक्रम और तिथि\nट्रेड किए गए CS:GO आइटम्स पर सात-दिन का कूलडाउन लगता है।\n\nआधिकारिक रिलीज़ नोट्स तारीख और प्रतिबंध की पुष्टि करते हैं। प्रदान किया गया URL एक 2013 मानचित्र अपडेट पर रीडायरेक्ट करता है; मिलान करने वाला रिलीज़-नोट URL 20309. पर समाप्त होता है।\n\nValve — 3/29/2018 के लिए रिलीज़ नोट्स ↗\nमूल प्रविष्टि और सबमिट किया गया लिंक\n\nसीएस:गो / 7-डे ट्रेड लॉक\n\nसबमिट किए गए स्रोत का निरीक्षण करें ↗ संग्रहीत 2025-02-26 ↗\n\nसाक्ष्य का अनुसरण करें। स्रोत की जाँच करें।\n\nजांच पर लौटें ↗",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "सुरक्षा समयरेखा — 2018 से 2026"
          },
          {
            "level": 2,
            "id": null,
            "text": "कालक्रम"
          },
          {
            "level": 2,
            "id": null,
            "text": "समूह चैट में संदिग्ध संदेश चेतावनियाँ"
          },
          {
            "level": 2,
            "id": null,
            "text": "प्रकाशक कुंजियों के लिए सूक्ष्म अनुमतियाँ और आईपी व्हाइटलिस्टिंग (Valve घोषणा)"
          },
          {
            "level": 2,
            "id": null,
            "text": "CS2 ट्रेड्स को सात-दिवसीय रिवर्सल विंडो मिलती है।"
          },
          {
            "level": 2,
            "id": null,
            "text": "Valve एसएमएस लीक के संबंध में खाता सुरक्षा चेतावनी प्रकाशित करता है"
          },
          {
            "level": 2,
            "id": null,
            "text": "पुनः व्यापार या पुनः विपणन से सात दिन पहले"
          },
          {
            "level": 2,
            "id": null,
            "text": "नए डिवाइस प्रतिबंधों की पुष्टि सहायता पृष्ठों पर की गई।"
          },
          {
            "level": 2,
            "id": null,
            "text": "2024 में नाम-परिवर्तन ट्रेड कूलडाउन लागू किया गया।"
          },
          {
            "level": 2,
            "id": null,
            "text": "कुंजी निर्माण के लिए मोबाइल पुष्टि आवश्यक है।"
          },
          {
            "level": 2,
            "id": null,
            "text": "गेम बिल्ड्स को लाइव सेट करने के लिए अनिवार्य 2FA प्रभावी हो गया।"
          },
          {
            "level": 2,
            "id": null,
            "text": "कस्टम जीवनी सामग्री चेतावनियाँ जो समुदाय द्वारा देखी गईं"
          },
          {
            "level": 2,
            "id": null,
            "text": "प्रोफ़ाइल लिंक फ़िल्टरिंग और संपादन कूलडाउन सक्रिय हैं"
          },
          {
            "level": 2,
            "id": null,
            "text": "Steam क्लाइंट का OAuth रिफ्रेश और एक्सेस टोकन में संक्रमण"
          },
          {
            "level": 2,
            "id": null,
            "text": "क्यूआर साइन-इन और अधिकृत-डिवाइस प्रबंधन"
          },
          {
            "level": 2,
            "id": null,
            "text": "सार्वजनिक API सूची से ट्रेड रद्दीकरण एंडपॉइंट्स हटा दिए गए"
          },
          {
            "level": 2,
            "id": null,
            "text": "डोटा 2 आइटम्स को सात-दिन का ट्रेडिंग कूलडाउन मिलता है।"
          },
          {
            "level": 2,
            "id": null,
            "text": "ट्रेड किए गए CS:GO आइटम्स पर सात-दिन का कूलडाउन लगता है।"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/hi/#briefing-heading",
          "https://steamcommunity.com/groups/SteamClientBeta?l=english",
          "http://web.archive.org/web/20260313235409/https://steamcommunity.com/groups/SteamClientBeta?l=english",
          "https://store.steampowered.com/news/posts/?enddate=1788390000",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/493839547938902179",
          "https://partner.steamgames.com/doc/webapi_overview/auth",
          "https://csmarketcap.com/blog/market-insights/from-boom-to-bust-cs2s-trade-protection-impact",
          "https://skinvault.gg/blog/cs2-trade-protection-explained/",
          "https://skin.land/blog/steam-changes-cs2-trade-ban-logic-timing/",
          "https://store.steampowered.com/news/posts/?appids=730&amp;enddate=1753924057&amp;feed=steam_announce%2F1000",
          "https://help.steampowered.com/faqs/view/3041-A87A-E5F6-B6AC",
          "https://store.steampowered.com/news/posts/?enddate=1747349559",
          "https://steamcommunity.com/ogg/593110/announcements/detail/533224478739530146",
          "https://store.steampowered.com/news/posts/?appids=730&amp;enddate=1728000977&amp;feed=steam_community_announcements",
          "https://steamcommunity.com/games/CSGO/announcements/detail/4447966961421256740",
          "https://help.steampowered.com/faqs/view/7F77-9E92-31E0-6B8E",
          "https://steamcommunity.com/sharedfiles/filedetails/?id=2926756889",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "http://web.archive.org/web/20260924181824/https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "https://steamcommunity.com/dev/apikey",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3749866608167579206",
          "http://web.archive.org/web/20251203174259/https://steamcommunity.com/groups/steamworks/announcements/detail/3749866608167579206",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3734103130194459461",
          "https://steamcommunity.com/discussions/forum/1/3807266184852932971/",
          "https://help.steampowered.com/faqs/view/225C-C51E-B8F0-55B2",
          "https://store.steampowered.com/news/group/4/view/3314112260640237775",
          "https://store.steampowered.com/news/posts/?appgroupname=Keep+in+touch&amp;enddate=1666122699&amp;feed=steam_blog",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/issues/325",
          "https://partner.steamgames.com/doc/webapi/IEconService",
          "https://steamcommunity.com/app/570/announcements/",
          "https://blog.dota2.com/2020/05/trading-cooldown/",
          "https://blog.counter-strike.net/2018/03/20309/",
          "https://blog.counter-strike.net/index.php/2018/03/20308/",
          "http://web.archive.org/web/20250226114333/https://blog.counter-strike.net/index.php/2018/03/20308/",
          "https://phishdestroy.io/steam_dossier/hi/#vulnerability-profile"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/hi/security_timeline.content.json",
      "export_json_sha256": "0972454f55fa4538b05cbe446720d684c84eedff2d19733a258a16364b108c74"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "hi/skin_atlas.html",
      "language": "hi",
      "title": "Steam क्या वह नहीं उठा सकता — Steam का डोजियर",
      "source_url": "https://phishdestroy.io/steam_dossier/hi/skin_atlas",
      "source_html_sha256": "9217f991ab05fb58d0df9dfbf5c535cc79fcbcc43dd4a115067169c8db464532",
      "exported_at": "2026-09-29T00:22:51.204Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "gallery",
            "source": "https://phishdestroy.io/steam_dossier/hi/skin_atlas#gallery"
          }
        ],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "skin_atlas.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/hi/skin_atlas.pdf?v=print-20260929-v5",
        "sha256": "f28e21006722092a5bf74ee362ea4142d20024191283fe95a064141e5259a746",
        "bytes": 423358,
        "pages": 7
      },
      "integrity": {
        "signed_object": "skin_atlas.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "skin_atlas.content.json.asc",
        "digest_file": "skin_atlas.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify skin_atlas.content.json.asc skin_atlas.content.json",
          "sha256sum -c skin_atlas.content.json.sha256"
        ]
      },
      "content": {
        "text": "प्रदर्शनी IV-B / मूल्य सीढ़ी / 2026-09-23\nस्किन प्राइस-लैडर एटलस — तरलता की खाई\n\nValve का मार्केट स्टॉप्स जहाँ पैसा शुरू होता है।\n\nयह अनुभाग क्या प्रमाणित करता है\n\nयह विज़ुअल एटलस पाँच मार्केटप्लेस कैटलॉग्स में 30,266 आइटम श्रेणियों का विश्लेषण करता है, और Valve की लिस्टिंग थ्रेशोल्ड से ऊपर और नीचे बाज़ार कवरेज को मापता है। $1,800 सीमा से नीचे, Steam में सक्रिय श्रेणियों का 95.3% है; ठीक इसके ऊपर, आधिकारिक कवरेज घटकर 1.9% तक सीमित हो जाता है (जहाँ 0.0% कवरेज सत्यापित परिसंपत्तियों में फैला हुआ है)। यह एक अचानक, संरचनात्मक तरलता खाई को दर्शाता है जहाँ Valve उच्च-मूल्य लेनदेन की खोज को बाहरी प्लेटफ़ॉर्मों को सौंपता है, जबकि अंतर्निहित परिसंपत्ति हिरासत पर पूर्ण नियंत्रण बनाए रखता है।\n\n← कार्यकारी ब्रीफिंग पर वापस\n\nपाँच मार्केटप्लेस पर लाइव कीमत वाले प्रत्येक CS2 आइटम को उसकी सबसे सस्ती मांग के आधार पर एक मूल्य बैंड में रखा गया, और प्रत्येक बैंड को एक ही बात के लिए मापा गया: कि उसमें से Valve की अपनी कम्युनिटी मार्केट अभी कितनी हिस्सेदारी रखती है। Valve की लिस्टिंग कैप से नीचे इसका उत्तर है 95.3%. इसके ऊपर, उत्तर है 1.9%. गिरावट क्रमिक नहीं है और यह उस जगह नहीं गिरती जहाँ मांग गिरती है — यह ठीक प्रकाशित नियम पर गिरती है। की 248 ऐसे आइटम श्रेणियाँ जिनके लिए दो या अधिक मार्केटप्लेस स्वतंत्र रूप से कैप से ऊपर कीमत निर्धारित करते हैं, 100.0% के पास कोई Steam लिस्टिंग नहीं है।\n\nचट्टान देखो ↓419 वस्तुओं की गैलरी खोलेंविधि और सीमाएँ\n30,266मापे गए आइटम श्रेणियाँ\n95.3%Steam द्वारा संचालित उप-कैप आइटम\n1.9%Steam द्वारा रखे गए कैप से अधिक आइटम\n$78.6Mपुष्टि किए गए सेट का तल मान\n01 / माप\nचट्टान नियम पर उतरती है, मांग पर नहीं।\n\nनीचे दिए गए प्रत्येक 30,266 आइटम श्रेणी को इसके द्वारा एक बैंड में रखा गया है। सबसे सस्ता BUFF163, CSFloat, Skinport, YouPin 898 और C5Game पर लाइव पूछताछ करें, और केवल उन आइटम्स को गिना जाता है जो इनमें से दो या अधिक पर उद्धृत हों, इसलिए कोई भी एक आशावादी लिस्टिंग बैंड के किसी सदस्य का आविष्कार नहीं कर सकती। ऊपरी पैनल प्रत्येक बैंड का वह हिस्सा दिखाता है जिसे Valve का अपना बाजार अभी भी धारण किए हुए है।\n\nSteam कम्युनिटी मार्केट द्वारा प्रत्येक मूल्य बैंड का हिस्सा\nऊपरी: भाप कवरेज · निचला: प्रति बैंड आइटम, लघु पैमाना\n0%\n25%\n50%\n75%\n100%\n100%\n96.9%\n95.9%\n97.3%\n91.1%\n76.8%\n14.5%\n2.9%\n1.5%\n0%\n0%\n0%\n4,632\n1¢–10¢\n7,152\n10¢–$1\n8,568\n$1–10\n5,941\n$10–100\n2,329\n$100–300\n1,292\n$300–1k\n193\n$1k–1.8k\n70\n$1.8k–3k\n67\n$3k–10k\n18\n$10k–30k\n3\n$30k–100k\n1\n$100k+\nitems\nlog\nVALVE’S LISTING CAP\nValve की लिस्टिंग कैप पर या उससे नीचेकैप से ऊपर — Valve का नियम सूचीबद्ध करने पर रोक लगाता हैबैंड में आइटम श्रेणियाँ\n\nकवरेज का अर्थ है कि कैप्चर के क्षण में उस श्रेणी के लिए एक लाइव Steamask मौजूद था। निचला पैनल लॉगैरिद्मिक है क्योंकि कैटलॉग अत्यधिक सस्ता है: इसे रैखिक रूप से पढ़ने पर $300 से ऊपर की हर बैंड को बेसलाइन में समतल कर देगा।\n\nआकार जो खारिज करता है\n\n76.8%300–$1 14.5% 2.9% Valve यदि महंगी वस्तुएँ केवल अस्वीकृत होतीं, तो कीमत बढ़ने के साथ कवरेज धीरे-धीरे घटती। ऐसा नहीं होता। यह $0.000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000\n\nमूल्य सीमा\tआइटम श्रेणियाँ\tएक लाइव Steam पूछें\tSteam आवरण\tSteam से सूचीबद्ध प्रतियाँ\n1¢–10¢\t4,632\t4,632\t100%\t8,223,227\n10¢–$1\t7,152\t6,931\t96.9%\t5,488,315\n$1–10\t8,568\t8,213\t95.9%\t3,939,538\n$10–100\t5,941\t5,780\t97.3%\t1,328,255\n$100–300\t2,329\t2,121\t91.1%\t364,466\n$300–1k\t1,292\t992\t76.8%\t187,504\n$1k–1.8k\t193\t28\t14.5%\t40,281\n$1.8k–3k\t70\t2\t2.9%\t9,592\n$3k–10k\t67\t1\t1.5%\t6,706\n$10k–30k\t18\t0\t0%\t1,366\n$30k–100k\t3\t0\t0%\t21\n$100k+\t1\t0\t0%\t2\n\nइस सीढ़ी से पैटर्न और फेज़ वेरिएंट्स को बाहर रखा गया है: Steam अपनी मार्केट एंट्री के रूप में ब्लू-जेम टियर या रूबी फेज़ को सूचीबद्ध नहीं करता है, इसलिए उन्हें गिनने से Steam की कवरेज कम आंकी जाएगी। दो मार्केटप्लेस की आवश्यकता के बिना मापने पर वही सीढ़ी 37,204 वस्तुओं में कैप के नीचे 79.1% और उसके ऊपर 6.5% दिखाती है — एक और भी तीखा अंतर, जो कमजोर साक्ष्यों पर आधारित है, और इसलिए यही आंकड़ा उद्धृत नहीं किया गया है।\n\n02 / साक्ष्यात्मक ग्रेडिंग\nमांगी गई कीमत कोई कीमत नहीं है।\n\nकोई भी P2000 को दस मिलियन युआन के आसपास सूचीबद्ध कर सकता है। इस पृष्ठ पर किसी भी आंकड़े का उपयोग करने से पहले, इसे इस आधार पर ग्रेड किया जाता है कि कितने बाज़ार स्वतंत्र रूप से इस वस्तु का मूल्य सीमा से ऊपर उद्धृत करते हैं और उन उद्धरणों का मध्य कितना संकुचित है। केवल ग्रेड A और B ही उद्धृत किए जाते हैं — यहाँ या इस दस्तावेज़ में कहीं भी।\n\nA  तीन या अधिक शेल्फ सहमत हैं\n\nतीन या उससे अधिक मार्केटप्लेस इस आइटम का मूल्य कैप से ऊपर उद्धृत करते हैं और उनका माध्य सबसे सस्ते से 25% के भीतर होता है। 197 श्रेणियाँ, 18,218 प्रतियाँ, $76,585,587.\n\nSteam से अनुपस्थित: 100.0%.\n\nB  दो अलमारियाँ सहमत हैं\n\nदो मार्केटप्लेस कैप से ऊपर सहमत हैं, या तीन कम मजबूती से सहमत हैं। 51 श्रेणियाँ, 176 प्रतियाँ, $2,038,814.\n\nSteam से अनुपस्थित: 100.0%.\n\nC  एक शेल्फ — उपयोग नहीं किया गया\n\nएक ही मार्केटप्लेस में केवल कैप से ऊपर का अनुरोध होता है। 171 श्रेणियाँ, 247 प्रतियाँ। पूर्णता के लिए गैलरी में दिखाया गया है और इस पृष्ठ के प्रत्येक योग से बाहर रखा गया है।\n\nये कीमत के लिए अनुरोध हैं, कीमत का प्रमाण नहीं।\n\nइस सुधार की कीमत क्या थी, और इसने क्या खरीदा\n\nग्रेड C को हटाने से शीर्षक से 171 श्रेणियाँ और $3,825,125 हट जाते हैं। जो बचता है वह छोटा है और उससे बहस करना बहुत मुश्किल है: 248 श्रेणियाँ, 18,394 पर सूचीबद्ध प्रतियाँ, उनमें से $78,624,401, और 100.0% — हर एक — Valve के बाज़ार से अनुपस्थित हैं। ग्रेड-सी पंक्तियाँ ही कारण हैं कि आकृति हिल गई; वे सूचीबद्ध हैं, छिपी नहीं हैं।\n\nकलाकृति के रूप में आरक्षित सूचियाँ\n\nकिसी भी वस्तु पर सबसे सस्ती मांग के तीन गुना से अधिक का कोई भी कोट अलग रख दिया जाता है। डेटा स्वयं जो दर बताता है, उसी दर पर परिवर्तित करने पर, इनमें से अधिकांश गोल CNY आंकड़े होते हैं — ये एक ऑफर की बजाय प्लेसहोल्डर या प्लेटफ़ॉर्म की ऊपरी सीमा का संकेत हैं। क्योंकि इस पृष्ठ पर प्रत्येक कुल राशि का उपयोग करता है सबसे सस्ता पूछें, इन आंकड़ों में से किसी ने भी कभी कोई संख्या नहीं बढ़ाई; इन्हें इसलिए बाहर रखा गया है ताकि इनमें से किसी को भी सुर्खी के रूप में उद्धृत नहीं किया जा सके।\n\nआइटम\tसबसे सस्ता लाइव आस्क\tअलग रखो\nSouvenir P2000 | Wicked Sick (Minimal Wear)\t$148,954\t$1,489,543\n★ Specialist Gloves | Crimson Kimono (Minimal Wear) | Phase 1\t$37,239\t$119,163\nSouvenir USP-S | Printstream (Factory New)\t$2,000\t$59,582\n★ Bowie Knife | Crimson Web (Factory New)\t$2,957\t$43,030\n★ Karambit | Marble Fade (Factory New) | 1st\t$11,916\t$38,874\nSticker | Ninjas in Pyjamas (Holo) | Katowice 2014\t$5,000\t$31,748\nSouvenir AWP | Dragon Lore (Battle-Scarred)\t$4,225\t$29,157\n★ Karambit | Doppler (Minimal Wear) | Ruby\t$7,122\t$27,273\nसभी 419 श्रेणियाँ, प्रत्येक मूल्य जिस वस्तु को संदर्भित करता है\n\nस्रोत: https://phishdestroy.io/steam_dossier/hi/skin_atlas#gallery\n\n04 / जहाँ यह इसके बजाय गया\nवे अलमारियाँ जो वह रखती हैं जो Steam नहीं रखती\n\nउसी लिस्टिंगें, जिन्हें उन्हें धारण करने वाले मार्केटप्लेस के अनुसार समूहित किया गया है। यह उन स्थानों की संख्या है जहाँ प्रतियाँ हैं। सूचीबद्ध, जो कि उनके स्वामित्व के स्थान के समान नहीं है और यहाँ ऐसा नहीं माना जाता है।\n\nकैप से ऊपर की लिस्टिंग का फर्श मूल्य, मार्केटप्लेस के अनुसार\nउस शेल्फ पर सूचीबद्ध x प्रतियों की न्यूनतम पूछताछ कीमत\nYouPin 898\n$22,720,252\nBUFF163\n$22,022,606\nC5Game\n$12,560,543\nCSFloat\n$10,871,845\nSkinport\n$1,385,060\n\nउपरोक्त क्रम में क्षेत्राधिकार: YouPin 898 — चीन · BUFF163 — चीन · C5Game — चीन · CSFloat — संयुक्त राज्य अमेरिका · Skinport — जर्मनी / माल्टा। एक ही भौतिक वस्तु इन शेल्फों में से एक से अधिक पर सूचीबद्ध की जा सकती है, इसलिए इन आंकड़ों को किसी अन्य बाज़ार के कुल आंकड़ों के साथ जोड़ना नहीं चाहिए।\n\nमूल्य श्रेणी के अनुसार फर्श मूल्य\nकैप से ऊपर पैसा कैसे वितरित किया जाता है\n$1.8k-3k\n$9,842,391\n$3k-10k\n$36,787,269\n$10k-50k\n$20,038,749\nover $50k\n$2,891,897\n05 / कमी जिसे आप गिन सकते हैं\nआपूर्ति वास्तव में कितनी पतली है\n\nप्रत्येक CS2 आइटम के साथ एक वियर वैल्यू जुड़ा होता है, और मार्केटप्लेस यह प्रकाशित करते हैं कि इसकी कितनी प्रतियाँ प्रत्येक बैंड में मौजूद हैं। इससे 'दुर्लभ' एक विशेषण से एक संख्या में बदल जाता है — और यही संख्या बताती है कि एक ही समझौता किया गया खाता एक विशेष रूप से तैयार फ़िशिंग किट के लिए प्रयास करने लायक क्यों होता है।\n\nएडब्ल्यूपी | ड्रैगन लोअर\n150 सूचीबद्ध · $11,350 से\n0.00–0.01\n29 · $14,730\n0.01–0.02\n54 · $11,618\n0.02–0.03\n26 · $11,350\n0.03–0.04\n25 · $11,618\n0.04–0.07\n16 · $11,585\n\nAWP | ड्रैगन लोअर (नया)\n\nएम4ए4 | भौंकना\n105 सूचीबद्ध · $6,628 से\n0.00–0.01\n11 · $10,725\n0.01–0.02\n14 · $8,088\n0.02–0.03\n11 · $7,580\n0.03–0.04\n19 · $6,703\n0.04–0.07\n50 · $6,628\n\nM4A4 | हॉल (फ़ैक्टरी न्यू)\n\nएके-47 | वाइल्ड लोटस\n113 सूचीबद्ध · $14,373 से\n0.00–0.01\n25 · $22,343\n0.01–0.02\n11 · $19,364\n0.02–0.03\n3 · $19,645\n0.03–0.04\n15 · $15,044\n0.04–0.07\n59 · $14,373\n\nएके-47 | वाइल्ड लोटस (फ़ैक्टरी न्यू)\n\nएडब्ल्यूपी | गुंगनिर\n173 सूचीबद्ध · $11,618 से\n0.00–0.01\n28 · $17,875\n0.01–0.02\n21 · $13,600\n0.02–0.03\n32 · $12,065\n0.03–0.04\n29 · $11,735\n0.04–0.07\n63 · $11,618\n\nAWP | गुंगनिर (नया)\n\nएके-47 | अग्नि सर्प\n278 सूचीबद्ध · $663 से\n0.15–0.18\n87 · $730\n0.18–0.21\n49 · $712\n0.21–0.24\n52 · $703\n0.24–0.27\n18 · $715\n0.27–0.38\n72 · $663\n\nएके-47 | फायर सर्प (मैदानी-परीक्षित)\n\nकेस हार्डन (सभी स्तर / नीला रत्न)\n76 सूचीबद्ध · $1,638 से\n0.07–0.08\n1 · $2,516\n0.08–0.09\n4 · $2,482\n0.09–0.10\n6 · $3,856\n0.10–0.11\n7 · $2,797\n0.11–0.15\n58 · $1,638\n\nAK-47 | केस हार्डन किया हुआ (न्यूनतम घिसाव) | टियर 1\n\nबैंड्स बाजारों की अपनी फ्लोट बकेट्स हैं; केवल उन बैंड्स को ही शामिल किया जाता है जिनके पास कम से कम एक लाइव लिस्टिंग हो। प्रत्येक बार के बगल में दी गई कीमत उस बैंड में सबसे सस्ती लाइव पूछी गई कीमत है, इसलिए कम फ्लोट से जुड़ा प्रीमियम अनुमानित न होकर सीधे तौर पर पढ़ा जा सकता है।\n\n06 / गति, मापी गई Steam से\nतीसरे पक्ष की अलमारियों ने वास्तव में क्या महसूस किया\n\nValve इस स्तर पर कोई उपयोगी इतिहास प्रकाशित नहीं करता, और यह दस्तावेज़ भी ऐसा कोई दावा नहीं करता।Skinportपिछले 24 घंटों, 7, 30 और 90 दिनों में अपनी पूरी हुई बिक्री प्रकाशित करता है, और यहीं उपलब्ध समय आयाम की पूरी सीमा है: प्रत्येक पिछली विंडो के लिए माध्यिका वास्तविक मूल्य, जिसे इस प्रकार अनुक्रमित किया गया है कि 90-दिनों की माध्यिका 100. हो। किसी भी चार्ट में Steam का कोई डेटा शामिल नहीं है।\n\nमध्यिका वास्तविक मूल्य, पिछली अवधि\n90-दिन के मध्य तक अनुक्रमित · 6,758 आइटम 20+ बिक्री के साथ\n85\n91\n97\n103\n100\n90d\n94\n30d\n90\n7d\n88\n24h\nप्रतिदिन पूरी हुई बिक्री\nएक ही आइटम, एक ही विंडो\n7,621\n9,653\n11,684\n13,716\n12,700\n90d\n11,894\n30d\n9,540\n7d\n8,637\n24h\n\nये दो चार्ट हैं, एक नहीं, जिनमें दो ऊर्ध्वाधर पैमाने हैं: एक सूचकांक और एक दैनिक गिनती, जिनकी कोई एक इकाई साझा नहीं है, और उन्हें एक सामान्य अक्ष पर खींचना एक अमान्य तुलना को आमंत्रित करेगा। विंडो एक-दूसरे में समाहित और पिछली हैं — 90-दिन का आंकड़ा 24-घंटे के आंकड़े को समाहित करता है — इसलिए यह एक दैनिक श्रृंखला नहीं है और इसे दैनिक श्रृंखला के रूप में नहीं पढ़ा जाना चाहिए। यह जो समर्थन करता है वह संकीर्ण है और स्पष्ट रूप से कहा गया है: पिछली खिड़कियों के दौरान Skinport प्रकाशित, औसत वास्तविक कीमत अपने स्वयं के 90-दिन के औसत से नीचे थी और दैनिक बिक्री की संख्या इसके साथ गिर गई।\n\nSkinport वास्तविक बिक्री। विंडोज़ नेस्टेड और ट्रेलिंग हैं, इसलिए प्रत्येक बिंदु ट्रेलिंग विंडो पर औसत वास्तविक मूल्य का माध्यक है, जिसे 90--दिन के माध्यक के अनुसार अनुक्रमित किया गया है। यह दैनिक श्रृंखला नहीं है और इसमें कोई Steam डेटा शामिल नहीं है।\n\n07 / यह किससे बना है\nसोलह साल पुराने स्टिकर और मुट्ठी भर दस्ताने\n\nकैप के ऊपर का सेट पूरे खेल का व्यापक हिस्सा नहीं है। यह कुछ दुर्लभ वस्तुओं और कुछ संग्रहों पर केंद्रित है, जिनमें से कई अब बिल्कुल भी प्राप्त नहीं की जा सकतीं — और यही कारण है कि आपूर्ति कीमत के अनुसार प्रतिक्रिया नहीं दे सकती।\n\nकैप से ऊपर की श्रेणियाँ, दुर्लभता के अनुसार\nआइटम श्रेणियों की गिनती\nCovert\n321\nClassified\n39\nRestricted\n24\nContraband\n12\nMil-Spec Grade\n9\nConsumer Grade\n9\nIndustrial Grade\n5\nकैप से ऊपर की श्रेणियाँ, संग्रह के अनुसार\nशीर्ष दस संग्रह\nThe St. Marc Collection\n13\nThe Cobblestone Collection\n13\nThe Norse Collection\n12\nThe Arms Deal Collection\n9\nThe Canals Collection\n7\nThe Gods and Monsters Collection\n6\nThe Revolution Collection\n4\nThe 2021 Train Collection\n4\nThe Rising Sun Collection\n4\nThe Chop Shop Collection\n4\n\nश्रेणी के अनुसार: skin366, स्टिकर48, कंटेनर3, स्टिकर_स्लैब2.\n\n08 / वास्तव में किसी ने जितना अधिकतम भुगतान किया\nलेन-देन से समर्थित उच्च, लिस्टिंग से नहीं\n\nइस पृष्ठ पर हर दूसरी कीमत एक है। पूछो — एक विक्रेता क्या चाहता है। ये हैं बिक्री: प्रत्येक आइटम के लिए Skinport द्वारा पिछले 90 दिनों में दर्ज की गई उच्चतम पूरी हुई लेनदेन। यह इस दस्तावेज़ में एकमात्र आंकड़ा है जिसे वास्तव में किसी ने चुकाया है, और प्रत्येक पंक्ति मार्केटप्लेस से जुड़ी है ताकि इस संख्या को हमारे बजाय उसके स्रोत के खिलाफ जांचा जा सके।\n\n21,216खिड़की में बिक्री पूरी हुई वस्तुएँ\n106Valve की लिस्टिंग कैप पर या उससे अधिक पर बेचा गया\n$14,192सबसे ऊँची एकल पूरी हुई बिक्री\n67/419किसी भी दर्ज बिक्री के साथ कैप से ऊपर की श्रेणियाँ\nविंडो में तीस सबसे ऊँची पूरी हुई बिक्री\nआइटम\tसबसे ऊँची बिक्री\tमाध्यिक बिक्री\tबिक्री\tसबसे सस्ता अभी पूछें\tSteam\tइसे देखो\nAWP | Gungnir (Factory New)\t$14,192\t$11,343\t5\t$11,490\tabsent\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Factory New)\t$12,387\t$12,387\t1\t$13,836\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Factory New)\t$11,779\t$11,063\t16\t$10,941\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Minimal Wear)\t$11,693\t$11,693\t1\t$9,946\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Minimal Wear)\t$10,437\t$10,437\t1\t$9,610\tabsent\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Blue Laminate (Minimal Wear)\t$9,772\t$37\t76\t$30\t$40\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Minimal Wear)\t$9,463\t$9,463\t1\t$9,500\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Minimal Wear)\t$9,104\t$9,026\t6\t$8,524\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Hedge Maze (Minimal Wear)\t$8,139\t$8,139\t1\t$6,819\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Field-Tested)\t$7,617\t$7,390\t4\t$7,194\tabsent\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Field-Tested)\t$7,615\t$7,615\t1\t$7,100\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Field-Tested)\t$7,149\t$7,006\t2\t$7,165\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Field-Tested)\t$6,711\t$6,194\t15\t$5,988\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Factory New)\t$6,679\t$6,613\t3\t$6,628\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Superconductor (Factory New)\t$6,084\t$6,084\t1\t$7,969\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Battle-Scarred)\t$5,750\t$5,413\t3\t$5,899\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Pandora's Box (Minimal Wear)\t$5,520\t$5,508\t3\t$4,998\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Vice (Factory New)\t$5,385\t$5,158\t2\t$5,700\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Minimal Wear)\t$5,342\t$4,989\t19\t$4,997\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Hedge Maze (Field-Tested)\t$5,334\t$4,862\t5\t$3,724\tabsent\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Vulcan (Factory New)\t$5,275\t$1,418\t12\t$1,280\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Well-Worn)\t$4,978\t$4,978\t1\t$4,942\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Well-Worn)\t$4,931\t$4,931\t1\t$5,445\tabsent\tSkinport CSFloat Steam\nAK-47 | Hydroponic (Factory New)\t$4,802\t$4,351\t2\t$3,648\tabsent\tSkinport CSFloat Steam\n★ Talon Knife | Case Hardened (Minimal Wear)\t$4,588\t$466\t16\t$442\t$630\tSkinport CSFloat Steam\nAWP | Medusa (Factory New)\t$4,484\t$4,484\t1\t$4,171\tabsent\tSkinport CSFloat Steam\n★ Specialist Gloves | Pillow Punchers (Factory New)\t$4,359\t$4,359\t1\t$4,302\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Pandora's Box (Field-Tested)\t$4,359\t$3,666\t11\t$3,245\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Field-Tested)\t$4,289\t$4,225\t8\t$4,022\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Battle-Scarred)\t$4,124\t$4,124\t1\t$4,279\tabsent\tSkinport CSFloat Steam\nएक ही आइटम, एक ही 90 दिन, कीमत में बहुत बड़ा अंतर\n\n$100 के माध्यिक और कम से कम पाँच पूर्ण बिक्री वाले आइटमों तक सीमित, क्योंकि सस्ते स्किन पर एक असामान्य बिक्री अनुपात को बाधित कर देती है। जो बचता है, वह द्वारा प्रभुत्वित है। केस हार्डन किया हुआ निष्कर्ष, जहाँ पैटर्न कीमत तय करता है और बाज़ार प्रत्येक पैटर्न को एक ही नाम के तहत दर्ज करता है — वही तंत्र जिसे धारा 05. में फ्लोट द्वारा मापा जाता है।\n\nआइटम\tउच्च बनाम मध्य\tसबसे ऊँची बिक्री\tमाध्यिक बिक्री\tबिक्री\tइसे देखो\n★ Talon Knife | Case Hardened (Minimal Wear)\t+884%\t$4,588\t$466\t16\tSkinport CSFloat Steam\nDesert Eagle | Cobalt Disruption (Factory New)\t+859%\t$1,210\t$126\t115\tSkinport CSFloat Steam\nAWP | BOOM (Minimal Wear)\t+814%\t$1,232\t$135\t89\tSkinport CSFloat Steam\nAK-47 | Case Hardened (Well-Worn)\t+769%\t$1,720\t$198\t70\tSkinport CSFloat Steam\nAWP | Graphite (Factory New)\t+761%\t$1,469\t$171\t124\tSkinport CSFloat Steam\n★ Talon Knife | Case Hardened (Field-Tested)\t+509%\t$2,437\t$400\t48\tSkinport CSFloat Steam\n★ Kukri Knife | Case Hardened (Minimal Wear)\t+448%\t$723\t$132\t69\tSkinport CSFloat Steam\n★ Kukri Knife | Case Hardened (Field-Tested)\t+415%\t$549\t$106\t128\tSkinport CSFloat Steam\n★ Ursus Knife | Case Hardened (Minimal Wear)\t+371%\t$597\t$127\t12\tSkinport CSFloat Steam\nAK-47 | Case Hardened (Field-Tested)\t+369%\t$1,037\t$221\t125\tSkinport CSFloat Steam\nAK-47 | Red Laminate (Minimal Wear)\t+360%\t$552\t$120\t18\tSkinport CSFloat Steam\nAWP | Asiimov (Field-Tested)\t+351%\t$528\t$117\t439\tSkinport CSFloat Steam\nAK-47 | Vulcan (Field-Tested)\t+337%\t$865\t$198\t241\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Nightwish (Factory New)\t+322%\t$625\t$148\t31\tSkinport CSFloat Steam\nAWP | Lightning Strike (Factory New)\t+319%\t$2,065\t$493\t198\tSkinport CSFloat Steam\nStatTrak™ AWP | Redline (Minimal Wear)\t+312%\t$574\t$139\t24\tSkinport CSFloat Steam\nStatTrak™ AWP | Asiimov (Battle-Scarred)\t+287%\t$524\t$135\t37\tSkinport CSFloat Steam\nAK-47 | Redline (Minimal Wear)\t+277%\t$562\t$149\t112\tSkinport CSFloat Steam\nAWP | Crakow! (Factory New)\t+275%\t$379\t$101\t72\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Vulcan (Factory New)\t+272%\t$5,275\t$1,418\t12\tSkinport CSFloat Steam\n\nयह एक 90--दिवसीय उच्चतम स्तर है, न कि सर्वकालिक उच्चतम, और यह केवल एक बाज़ार को कवर करता है। इस दस्तावेज़ में कहीं भी किसी भी सर्वकालिक आंकड़े का दावा नहीं किया गया है। एक ऐसी वस्तु जिसकी विंडो में कोई Skinport बिक्री नहीं है, वह इस प्रदर्शन से पूरी तरह अनुपस्थित है, और यही कारण है कि यह सेट जनगणना से छोटा है।\n\nप्रमाणीकरण लिंक कैटलॉग के अपने प्लेटफ़ॉर्म पहचानकर्ताओं से बनाए जाते हैं। ये प्रत्येक मार्केटप्लेस के आइटम के पेज की ओर इशारा करते हैं ताकि पाठक हमें नहीं बल्कि स्रोत के साथ चित्र की तुलना कर सके। आउटबाउंड लिंक ले जाते हैं रिले नोफ़ॉलोये उद्धरण हैं, समर्थन नहीं, और कई गंतव्य ऐसे बाज़ार हैं जिनकी यह जांच आलोचना करती है।\n\n09 / उत्पत्ति और सीमाएँ\nयह कहाँ से आया है और यह क्या नहीं दिखा सकता\n\nइस पृष्ठ पर प्रत्येक आकृति दो स्नैपशॉट फ़ाइलों से पुनः गणना की गई है, जिनके हैश उनके साथ प्रकाशित किए गए हैं। यहाँ कुछ भी किसी अन्य साइट के लेख से प्रतिलिपि नहीं किया गया है।\n\nस्रोत और पहुँच\n\ncs2.shAPI, GET /v1/prices/latest और GET /v1/schema, एकल स्नैपशॉट, कैप्चर किया गया 2026-09-23T00:44:27.871388581Z, USD में मूल्य।\n\nयह डेटा प्रदाता की अपनी शर्तों के तहत, अभिलेखागार में प्रलेखित GDPRक अनुरोधकर्ता द्वारा धारित एक सशुल्क व्यावसायिक सदस्यता के अंतर्गत प्राप्त किया गया था। किसी भी मार्केटप्लेस को स्क्रैप नहीं किया गया और किसी भी मार्केटप्लेस का कोई क्रेडेंशियल उपयोग नहीं किया गया। अनुरोधकर्ता की कुंजी इस रिपॉजिटरी के बाहर रखी गई है और यहाँ किसी भी फ़ाइल में नहीं दिखती।\n\nएक आइटम कैसे योग्य होता है\n\nBUFF, CSFloat, Skinport, YouPin या C5Game पर कम से कम एक लाइव आस्क वाले प्रत्येक बेस आइटम को उसकी सबसे सस्ती ऐसी आस्क के आधार पर एक प्राइस बैंड में रखा जाता है, इसलिए बैंड कभी भी Steam पर निर्भर नहीं होता। \"Steam कवरेज\" उस बैंड में मौजूद आइटम्स का वह हिस्सा है जिनके पास कैप्चर के समय कोई भी लाइव Steam आस्क होता है। पैटर्न और फेज़ वेरिएंट्स को लैडर से बाहर रखा गया है क्योंकि Steam उन्हें अलग से सूचीबद्ध नहीं करता; उन्हें शामिल करने से Steam कम आँका जाएगा। रेंडर्स समान आइटम्स की कैटलॉग छवियाँ हैं, जो स्थानीय रूप से संग्रहीत होती हैं।\n\nरेंडर और छवि अधिकार। कैटलॉग आइटम रेंडर प्रदाता की छवियाँ हैं, जिन्हें price rows के समान market_hash_name के लिए परोसा जाता है, और ऑफ़लाइन तथा IPFS प्रदर्शन के लिए स्थानीय रूप से संग्रहीत किया जाता है। ये रेंडर PhishDestroy का कार्य नहीं हैं: सभी आइटम की छवियाँ, लोगो और स्क्रीनशॉट उनके संबंधित मालिकों (cs2.sh, CSFloat, Skinport, BUFF, YouPin, C5Game, Valve और अन्य) की संपत्ति बने रहते हैं। इन्हें केवल पहचान और सार्वजनिक हित की रिपोर्टिंग के लिए पुन: प्रस्तुत किया गया है; किसी भी स्वामित्व या लाइसेंस का दावा नहीं किया जाता।\n\nजो हम प्राप्त नहीं कर सके\n\nउपयोग किया गया सदस्यता स्तर केवल वर्तमान स्नैपशॉट्स के लिए ही सेवा प्रदान करता है। ऐतिहासिक और आर्काइव एंडपॉइंट्स उपलब्ध नहीं थे, और इस पृष्ठ पर कहीं भी किसी ऐतिहासिक श्रृंखला का दावा नहीं किया गया है। ट्रेलिंग-विंडो बिक्री से परे Skinport स्वयं को सेक्शन में प्रकाशित करता है 06.\n\nएक स्नैपशॉट, समय श्रृंखला नहीं। कैप्चर के समय Steam में लिस्टिंग का अभाव यह प्रमाण नहीं है कि कोई आइटम वहाँ कभी नहीं दिखाई देगा; यह उस क्षण शेल्फ की मापी गई स्थिति है, और कैप से ऊपर की कीमतों के लिए यह वही है जो Valve का प्रकाशित नियम निर्धारित करता है: Valve का Community Market स्पष्ट रूप से प्रति आइटम $1,800 पर लिस्टिंग को सीमित करता है (अधिकतम $2,000 का Steam वॉलेट बैलेंस; देखें Steam सामुदायिक बाज़ार अक्सर पूछे जाने वाले प्रश्न संचित 2026-09-21 ↗ और Steam सब्सक्राइबर समझौता § 3.C संचित 2026-09-24 ↗).\n\nग्रेड निर्धारण\n\nकिसी आइटम की कीमत हमेशा उसकी सबसे सस्ती लाइव पूछी गई कीमत होती है, इसलिए कोई उच्च विचलन कभी भी कुल राशि को बढ़ा नहीं सकता। ग्रेडिंग यह नियंत्रित करती है कि कौन सी पंक्तियाँ उद्धृत की जा सकती हैं। किसी भी उद्धरण को, जो उसी आइटम पर सबसे सस्ती पूछी गई कीमत से तीन गुना अधिक हो, लाइव कीमत नहीं माना जाता। ग्रेड A: तीन या अधिक बाज़ार अभी भी कैप से ऊपर उद्धरण देते हैं और उनका माध्यक सबसे सस्ते से 25% के भीतर होता है। ग्रेड B: दो बाज़ार सहमत हैं, या तीन कम सघनता से सहमत हैं। ग्रेड C: एक ही शेल्फ - एक पूछी गई कीमत, बाज़ार की कीमत नहीं। इस दस्तावेज़ में केवल ग्रेड A और B का ही कहीं भी उद्धरण दिया गया है।\n\nआउटलायर नियम: कोट > 3.0x उसी आइटम पर सबसे सस्ता पूछ मूल्य।\n\nकुल योग क्यों न्यूनतम हैं\n\nप्रत्येक बाज़ार के लिए वस्तु का सबसे कम ask को उस शेल्फ द्वारा सूचीबद्ध कॉपी की संख्या से गुणा किया जाता है। वहाँ मौजूद हर अन्य कॉपी की कीमत उस सबसे कम ask के बराबर या उससे अधिक होती है, इसलिए वास्तविक पोस्ट किया गया मूल्य निर्माण के कारण अधिक होता है, अनुमान के कारण नहीं। यह बिक्री नहीं है, न ही नकदी प्रवाह, और न ही CS2 अर्थव्यवस्था का मूल्यांकन है।\n\nखुद देखें\n\nइस पृष्ठ पर प्रत्येक चार्ट के पीछे के व्युत्पन्न डेटासेट पूर्ण रूप से प्रकाशित किए गए हैं: एटलस डेटासेट, ग्रेडिंग और कलाकृति स्क्रीन, आधारभूत जनगणना और प्रत्येक कच्चे स्नैपशॉट का SHA-256 वाला मैनिफेस्ट.\n\nखुले में दर्ज एक सुधार\n\nसाथी रजिस्टर का एक पुराना मसौदा Souvenir AK-47 | Point Disarray के साथ शुरू हुआ, जिसे एक चीनी मार्केटप्लेस पर $148,954 में पूछा गया था, जबकि Steam ने इसे $119. में मूल्यित किया था। वह पंक्ति ग्रेड C है: एक ही शेल्फ, एक ही प्रति, और कोई दूसरा मार्केटप्लेस सहमत नहीं है। यह एक पूछी गई कीमत है, कीमत नहीं, और इसे यहाँ और उस पृष्ठ पर डाउनग्रेड कर दिया गया है। पुष्टि किया गया लीडर Sticker | Titan (Holo) | Katowice 2014 पर है $66,285, 4 द्वारा उद्धृत, जो एक-दूसरे से 5.2% दूर हैं — और Steam से पूरी तरह अनुपस्थित हैं।",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "स्किन प्राइस-लैडर एटलस — तरलता की खाई"
          },
          {
            "level": 2,
            "id": null,
            "text": "चट्टान नियम पर उतरती है, मांग पर नहीं।"
          },
          {
            "level": 3,
            "id": null,
            "text": "आकार जो खारिज करता है"
          },
          {
            "level": 2,
            "id": null,
            "text": "मांगी गई कीमत कोई कीमत नहीं है।"
          },
          {
            "level": 3,
            "id": null,
            "text": "A  तीन या अधिक शेल्फ सहमत हैं"
          },
          {
            "level": 3,
            "id": null,
            "text": "B  दो अलमारियाँ सहमत हैं"
          },
          {
            "level": 3,
            "id": null,
            "text": "C  एक शेल्फ — उपयोग नहीं किया गया"
          },
          {
            "level": 3,
            "id": null,
            "text": "इस सुधार की कीमत क्या थी, और इसने क्या खरीदा"
          },
          {
            "level": 3,
            "id": null,
            "text": "कलाकृति के रूप में आरक्षित सूचियाँ"
          },
          {
            "level": 2,
            "id": null,
            "text": "सभी 419 श्रेणियाँ, प्रत्येक मूल्य जिस वस्तु को संदर्भित करता है"
          },
          {
            "level": 2,
            "id": null,
            "text": "वे अलमारियाँ जो वह रखती हैं जो Steam नहीं रखती"
          },
          {
            "level": 2,
            "id": null,
            "text": "आपूर्ति वास्तव में कितनी पतली है"
          },
          {
            "level": 2,
            "id": null,
            "text": "तीसरे पक्ष की अलमारियों ने वास्तव में क्या महसूस किया"
          },
          {
            "level": 2,
            "id": null,
            "text": "सोलह साल पुराने स्टिकर और मुट्ठी भर दस्ताने"
          },
          {
            "level": 2,
            "id": null,
            "text": "लेन-देन से समर्थित उच्च, लिस्टिंग से नहीं"
          },
          {
            "level": 3,
            "id": null,
            "text": "विंडो में तीस सबसे ऊँची पूरी हुई बिक्री"
          },
          {
            "level": 3,
            "id": null,
            "text": "एक ही आइटम, एक ही 90 दिन, कीमत में बहुत बड़ा अंतर"
          },
          {
            "level": 2,
            "id": null,
            "text": "यह कहाँ से आया है और यह क्या नहीं दिखा सकता"
          },
          {
            "level": 3,
            "id": null,
            "text": "स्रोत और पहुँच"
          },
          {
            "level": 3,
            "id": null,
            "text": "एक आइटम कैसे योग्य होता है"
          },
          {
            "level": 3,
            "id": null,
            "text": "जो हम प्राप्त नहीं कर सके"
          },
          {
            "level": 3,
            "id": null,
            "text": "ग्रेड निर्धारण"
          },
          {
            "level": 3,
            "id": null,
            "text": "कुल योग क्यों न्यूनतम हैं"
          },
          {
            "level": 3,
            "id": null,
            "text": "खुद देखें"
          },
          {
            "level": 3,
            "id": null,
            "text": "खुले में दर्ज एक सुधार"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/hi/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/hi/skin_atlas#gallery",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://skinport.com/market?search=AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260924114457/https://store.steampowered.com/subscriber_agreement/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-atlas.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-artefact-screen.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-above-the-ceiling.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/hi/skin_atlas.content.json",
      "export_json_sha256": "7b1b11fb663f9d2766e079429d1bc083ad4abaf2fea74c25054484060392dc47"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "hi/social_graph.html",
      "language": "hi",
      "title": "रिकॉर्ड किए गए संबंधों का अनुसरण करें — द Steam डोजियर",
      "source_url": "https://phishdestroy.io/steam_dossier/hi/social_graph",
      "source_html_sha256": "b2c528c468496a012e15cabd804d6b16f392b239dc322c4dc82e27c7161086c8",
      "exported_at": "2026-09-29T00:22:51.081Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "social_graph.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/hi/social_graph.pdf?v=print-20260929-v5",
        "sha256": "c9cdd9e3e306e1602f8472408c8380dc645475da8cb69b1a1be110f0d08c2eed",
        "bytes": 344563,
        "pages": 5
      },
      "integrity": {
        "signed_object": "social_graph.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "social_graph.content.json.asc",
        "digest_file": "social_graph.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify social_graph.content.json.asc social_graph.content.json",
          "sha256sum -c social_graph.content.json.sha256"
        ]
      },
      "content": {
        "text": "संबंधों का अनुसरण करें।प्रत्येक संबंध का निरीक्षण करें।\n\nप्रोफ़ाइल खोजें। संबंध का प्रकार चुनें। कैप्चर किए गए रिकॉर्ड्स में इसके प्रत्यक्ष पड़ोसियों का अनुसरण करें। अनुसंधान उपकरण: एज सार्वजनिक संबंधों का प्रतिनिधित्व करते हैं, न कि किसी भी दो नोड्स के बीच प्रत्यक्ष संपर्क, निजी समन्वय या दुराचार का प्रमाण। एक 3,435-नोड लेआउट को फ़िल्टरों के साथ पढ़ना सबसे अच्छा होता है।\n\nएक समय में एक रिश्ता ही समझें।\n\n💡 ग्राफ़ को पुनर्व्यवस्थित करने के लिए नोड्स पर क्लिक करें और उन्हें खींचें। विस्तृत प्रोफ़ाइल देखने के लिए होवर करें। टील ठोस रेखाएँ = मित्रता, एम्बर धराशायी रेखाएँ = पारस्परिक टिप्पणियाँ।\n\nरिश्ते का प्रकारप्रोफ़ाइल और प्रत्यक्ष पड़ोसी\n\n3,435 प्रोफ़ाइल · 4,551 द्वारा रिकॉर्ड किए गए लिंक\n\nप्रोफ़ाइल खोजें और चुनें, या किसी नोड पर क्लिक करें। केवल इसके सीधे रिकॉर्ड किए गए पड़ोसी ही शेष रहते हैं। एक एज एक संबंध रिकॉर्ड करता है; यह निजी समन्वय स्थापित नहीं करता।\n\nकैप्चर किए गए डेटासेट में प्रोफ़ाइल\n\nपूर्ण स्रोत तालिका: 3,435 की सभी पंक्तियाँ डाउनलोड करें (CSV)नीचे दी गई तालिका में प्रारंभ में पहले 25 पंक्तियाँ दिखाई गई हैं; खोज और पेजिनेशन पूरे डेटासेट को कवर करते हैं।\n\n1–25 / 3,435 पंक्तियाँ\nव्यक्तित्व का नाम\tस्टीमआईडी64\tगोपनीयता\tस्थिति\tसमूह सदस्यताएँ\tजमी हुई सूची (यूएसडी)\tस्थान\nMahatma Gandhi\t76561198333721623\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tPH\nGalley//갤리🌠🌙\t76561198043416832\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tKP\n$Schlächter\t76561198860277343\tPUBLIC\tClean\tsteambans\t$0.00\tUnknown\n❄r3dsn0w000™❄ [Cristi]🎮\t76561197986767957\tPUBLIC\tClean\tCommunityLegends\t$0.00\tRO\n(2a03) Wolfy\t76561197991671851\tPUBLIC\tCommunity\tsr_public\t$0.00\tUS\nZloy2288\t76561198038578334\tPUBLIC\tClean\tsteambans\t$0.00\tBY\njessy\t76561198039125237\tPUBLIC\tCommunity, VAC (1x)\tCommunityLegends\t$0.00\tJP\nJithraRufure\t76561198071896910\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\n| Níllerdínho |\t76561198003487438\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tDK\nJones is back\t76561198023013026\tPRIVATE\tVAC (1x)\tsteambans\t$0.00\tUnknown\nUNEX | ★✠☠ MoH3st ☠✠\t76561198050763123\tPUBLIC\tClean\tsteambans\t$0.00\tDE\nTrojan\t76561198048457084\tPUBLIC\tClean\tCommunityLegends\t$0.00\tDE\n𝗠𝗮𝘆𝘂 ❤\t76561199377967696\tPUBLIC\tClean\tsr_public\t$0.00\tIS\nbig fucking idiot\t76561198871206397\tPUBLIC\tVAC (1x)\tsteambans\t$0.00\tUnknown\nSOFF Games\t76561198227129276\tPUBLIC\tClean\tcommunitymoderators\t$0.00\tRU\nThijminecraft02\t76561198253895669\tPUBLIC\tClean\tSteamIDcouk SArchive\t$0.00\tNL\nStatic-sama\t76561198289329793\tPUBLIC\tClean\tsteambans\t$0.00\tJP\n𝙸mmortal 𝚂targazer\t76561198142116760\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\nCommander Keen\t76561197987773287\tPUBLIC\tClean\tsteambans\t$0.00\tBE\nS1mX\t76561199648509165\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\nmixwell\t76561199276547472\tPUBLIC\tClean\tsr_public\t$0.00\tJP\nP90_GOD_YyEs™\t76561198285821942\tPUBLIC\tClean\tsteambans\t$0.00\tHK\nhewwo?\t76561199133807546\tPUBLIC\tVAC (1x)\tsteambans\t$0.00\tCH\n♕Kamikaze Atze♕\t76561198002700103\tPUBLIC\tClean\tsteambans\t$0.00\tDE\nPastica\t76561198154655970\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tDZ\nरिकॉर्ड की गई मित्रता लिंक\n\nपूर्ण स्रोत तालिका: 4,299 की सभी पंक्तियाँ डाउनलोड करें (CSV)नीचे दी गई तालिका में प्रारंभ में पहले 25 पंक्तियाँ दिखाई गई हैं; खोज और पेजिनेशन पूरे डेटासेट को कवर करते हैं।\n\n1–25 / 4,299 पंक्तियाँ\nउपयोगकर्ता A\tदिशा\tउपयोगकर्ता बी\tसंबंध का प्रकार\nMahatma Gandhi\n76561198333721623\t↔\tDeskjet\n76561198272738437\tMutual Friends\nGalley//갤리🌠🌙\n76561198043416832\t↔\tomega\n76561197960274529\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tFisty\n76561198057301486\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tFaalagorn\n76561198001116101\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tMURK\n76561198036995672\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tÅρøᴛʜℯᴛȋᴄÅʟȋℯη ♛👽♛\n76561197984615267\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tsilatrak\n76561197999629462\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tBlack Blade\n76561198083368493\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tAvenger\n76561197978249317\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tRemtar\n76561198124322650\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tCato\n76561197961345984\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t✪ G λ M Ξ ®\n76561197994308495\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tclees42\n76561198030936806\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t𝓜ε𝔰𝔥 | AusLevels\n76561198108828539\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tSgtFopper™\n76561198002555892\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t❥Miss Bee\n76561198046958996\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tTesTy\n76561198032370068\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tskl_andrey\n76561198136881436\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t\"Exekutor\"\n76561198009583947\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tAraripe\n76561198103754372\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tsteve6678\n76561198053200093\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\ttrinner\n76561197970359081\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tSteph S.\n76561198025653291\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tKirito\n76561198154545657\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tDoc. todt\n76561197984492467\tMutual Friends\nरिकॉर्ड किए गए टिप्पणी लिंक\n\nपूर्ण स्रोत तालिका: 252 की सभी पंक्तियाँ डाउनलोड करें (CSV)नीचे दी गई तालिका में प्रारंभ में पहले 25 पंक्तियाँ दिखाई गई हैं; खोज और पेजिनेशन पूरे डेटासेट को कवर करते हैं।\n\n1–25 / 252 पंक्तियाँ\nलेखक\tदिशा\tलक्षित प्रोफ़ाइल\tदिनांक\tटिप्पणी पाठ\nDeskjet\n76561198272738437\t→\tMahatma Gandhi\n76561198333721623\t16 September, 2021 @ 11:02:05 pm PDT\t\"𝑵𝒐𝒘 𝒊𝒇 𝑰 𝒇𝒖𝒄𝒌 𝒕𝒉𝒊𝒔 𝒎𝒐𝒅𝒆𝒍𝑨𝒏𝒅 𝒔𝒉𝒆 𝒋𝒖𝒔𝒕 𝒃𝒍𝒆𝒂𝒄𝒉𝒆𝒅 𝒉𝒆𝒓 𝒂𝒔𝒔𝒉𝒐𝒍𝒆𝑨𝒏𝒅 𝑰 𝒈𝒆𝒕 𝒃𝒍𝒆𝒂𝒄𝒉 𝒐𝒏 𝒎𝒚 𝑻-𝒔𝒉𝒊𝒓𝒕𝑰'𝒎𝒎𝒂 𝒇𝒆𝒆𝒍 𝒍𝒊𝒌𝒆 𝒂𝒏 𝒂𝒔𝒔𝒉𝒐𝒍𝒆\" - Nelson Mandela\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t22 November, 2021 @ 4:10:28 pm PDT\thttps://anige.horigiri.net/?cat=22\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t18 November, 2021 @ 12:45:26 am PDT\thttps://gamerch.com/umamusume/entry/250411\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t8 August, 2021 @ 4:13:25 am PDT\thttps://modoocode.com/304\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t6 February, 2021 @ 3:35:05 pm PDT\t▤ ∫︹- -ω⁾ ⁽︹▓▓︺\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t11 December, 2019 @ 1:50:53 am PDT\thttps://blog.naver.com/aksenwlddj12/221369410039\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t2 October, 2019 @ 7:11:59 am PDT\tǤαllєу║︎갤리..۩\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t9 April, 2019 @ 12:51:28 pm PDT\tExplosiveDamage(owner, from, maxrange, minrange, distmultiplier, dmgmultiplier, mindamage, typ, damagetype, ignore)\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 12:22:47 pm PDT\tinfo - sh_titles.lua\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 12:21:46 pm PDT\tlocal nibbas = 1344 init.lua\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 11:31:58 am PDT\thttp://foreign.aladin.co.kr/shop/wproduct.aspx?ItemId=123955531&start=slayer\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t3 April, 2019 @ 1:26:41 am PDT\tǤαllєу\nLei\n76561198982197954\t→\tJithraRufure\n76561198071896910\t29 December, 2024 @ 12:58:08 pm PDT\t+rep he knows how 2 rush B ￣ヘ￣\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t2 September, 2026 @ 5:16:55 am PDT\tlol\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t20 August, 2026 @ 6:11:03 am PDT\t?\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t25 July, 2026 @ 7:20:05 am PDT\thahahahaha\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t30 June, 2026 @ 12:52:42 pm PDT\twow\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t30 June, 2026 @ 12:41:32 pm PDT\txD\nvalorant enjoyer\n76561199112142402\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:26:30 pm PDT\toh no!!\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:26:11 pm PDT\toh no!!\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:22:22 pm PDT\tomg !!! they know my secret, omg!!!\nvalorant enjoyer\n76561199112142402\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:21:39 pm PDT\t+rep good ♥♥♥♥♥ player\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:20:50 pm PDT\tomg! u cant cheat on secure gaben servers, omg dont report me, they ban me for boosted omg\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 8:37:11 pm PDT\txD\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t28 June, 2026 @ 1:58:14 pm PDT\twow",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "संबंधों का अनुसरण करें।प्रत्येक संबंध का निरीक्षण करें।"
          },
          {
            "level": 2,
            "id": null,
            "text": "एक समय में एक रिश्ता ही समझें।"
          },
          {
            "level": 2,
            "id": null,
            "text": "कैप्चर किए गए डेटासेट में प्रोफ़ाइल"
          },
          {
            "level": 2,
            "id": null,
            "text": "रिकॉर्ड की गई मित्रता लिंक"
          },
          {
            "level": 2,
            "id": null,
            "text": "रिकॉर्ड किए गए टिप्पणी लिंक"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-profiles.csv",
          "https://steamcommunity.com/profiles/76561198333721623",
          "https://steamcommunity.com/profiles/76561198043416832",
          "https://steamcommunity.com/profiles/76561198860277343",
          "https://steamcommunity.com/profiles/76561197986767957",
          "https://steamcommunity.com/profiles/76561197991671851",
          "https://steamcommunity.com/profiles/76561198038578334",
          "https://steamcommunity.com/profiles/76561198039125237",
          "https://steamcommunity.com/profiles/76561198071896910",
          "https://steamcommunity.com/profiles/76561198003487438",
          "https://steamcommunity.com/profiles/76561198023013026",
          "https://steamcommunity.com/profiles/76561198050763123",
          "https://steamcommunity.com/profiles/76561198048457084",
          "https://steamcommunity.com/profiles/76561199377967696",
          "https://steamcommunity.com/profiles/76561198871206397",
          "https://steamcommunity.com/profiles/76561198227129276",
          "https://steamcommunity.com/profiles/76561198253895669",
          "https://steamcommunity.com/profiles/76561198289329793",
          "https://steamcommunity.com/profiles/76561198142116760",
          "https://steamcommunity.com/profiles/76561197987773287",
          "https://steamcommunity.com/profiles/76561199648509165",
          "https://steamcommunity.com/profiles/76561199276547472",
          "https://steamcommunity.com/profiles/76561198285821942",
          "https://steamcommunity.com/profiles/76561199133807546",
          "https://steamcommunity.com/profiles/76561198002700103",
          "https://steamcommunity.com/profiles/76561198154655970",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-connections.csv",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-comments.csv"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/hi/social_graph.content.json",
      "export_json_sha256": "3a560a2fb346b4e8376cda18c06c1c3fd5db6eaaf04d62b3ed9d31a5d375c0f3"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "hi/steam_enforcement_evidence.html",
      "language": "hi",
      "title": "नियम बनाम प्रतिक्रियाएँ — द Steam डोजियर",
      "source_url": "https://phishdestroy.io/steam_dossier/hi/steam_enforcement_evidence",
      "source_html_sha256": "a98a70c5a919cf96b6d12276f476e9601cdee677c2fd16cbee190100d1475a80",
      "exported_at": "2026-09-29T00:22:51.526Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "steam_enforcement_evidence.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/hi/steam_enforcement_evidence.pdf?v=print-20260929-v5",
        "sha256": "3211ee947cad6fce53207e5eb1cbce44021733241a8d99e0a28e251323038088",
        "bytes": 589000,
        "pages": 34
      },
      "integrity": {
        "signed_object": "steam_enforcement_evidence.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "steam_enforcement_evidence.content.json.asc",
        "digest_file": "steam_enforcement_evidence.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify steam_enforcement_evidence.content.json.asc steam_enforcement_evidence.content.json",
          "sha256sum -c steam_enforcement_evidence.content.json.sha256"
        ]
      },
      "content": {
        "text": "साक्ष्य पूरक / स्रोत-संलग्न अभिलेख\nSteam प्रवर्तन साक्ष्य — समर्थन अभिलेख और डेवलपर नेटवर्क\n\nनियम। प्रतिक्रिया।\n\nयह अनुभाग क्या प्रमाणित करता है\n\nयह साक्ष्य कक्ष Valve के आधिकारिक सब्सक्राइबर एग्रीमेंट की तुलना 252 रिपॉजिटरीज़ और 3,320 प्रोफाइल में दिनांकित प्रवर्तन लॉग्स, समर्थन विवाद समाधानों और डेवलपर नेटवर्क रिकॉर्ड्स से करता है। यह दर्शाता है कि साधारण खाताधारक सत्र समझौतों के बाद अप्रतिवादनीय प्रवर्तन और समर्थन समापन का सामना करते हैं, जबकि उच्च-मात्रा वाले वाणिज्यिक बॉट संचालन सार्वजनिक अवसंरचना तक पहुंच के साथ निरंतर चलते रहते हैं।\n\n← कार्यकारी ब्रीफिंग पर वापस\n\nलिखित प्रतिबंध पढ़ें। रिकॉर्ड किए गए उत्तर को खोलें। स्रोत में जो दिखाया गया है उसकी तुलना उस बात से करें जो अभी भी अनुत्तरित है।\n\nसमर्थन और अपीलें ↓सार्वजनिक अवसंरचना ↓\n252भंडार अभिलेख\n3,320सार्वजनिक प्रोफ़ाइल\n4,214अलग प्रोफ़ाइल-रिपॉजिटरी जोड़े\n98,902साझा रिपॉजिटरी वाले प्रोफ़ाइल जोड़े\n01 / समर्थन, प्रतिबंध और पुनर्स्थापना\nशिकायत पढ़ें।स्रोत संलग्न रखें।\nसमर्थन अस्वीकृतियों गैलरी (981 प्रदर्शनियाँ) ↗चयनित रिकॉर्ड डाउनलोड करें ↓\nएचएफबी / आउटसोर्सिंग का मामलास्वीकार्य समझौता।\nरिपोर्ट की गई बर्खास्तगी।\n\nपुनरुत्पादित समर्थन प्रतिक्रिया और ठेकेदार कर्मचारियों के बारे में दावे के स्रोत का पालन करें।\n\nमामले और उसके स्रोतों को खोलें →\n\nनीचे: पाँच संरक्षित सार्वजनिक रेडिट पोस्ट प्रदान किए गए समर्थन संग्रह से। प्रत्येक रिकॉर्ड Valve की सहायता प्रणाली के साथ रिपोर्ट की गई एक बातचीत को दस्तावेज़ित करता है — जिसे इसके मूल स्रोत लिंक, कैप्चर स्थिति और संपूर्ण पाठ के साथ संरक्षित किया गया है। ये पीड़ितों के बयान हैं। उन्हें पुष्टि या खंडन करने वाले प्रमाणीकृत समर्थन लॉग्स Valve के पास हैं और उन्हें प्रकट नहीं किया गया है।\n\n01\nBan & review2024-12-09\nPermanent sanction & closed appeals\n\nThe author reports a permanent account ban, repeated ticket closures and a planned GDPR access request.\n\nREDDIT / PUBLIC TESTIMONYr/ohnePixelCapture record 294\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 303 words\nPermanently banned Steam account without a clear explanation, need help!\n\nsteam_support_tickets_MEGA.json / record 294\n\nHey everyone,\n\nI’m in a really frustrating situation, and I’m hoping someone here can help me or offer advice. My Steam account was just permanently banned for allegedly violating the Steam Subscriber Agreement, and I have no idea why.\n\n# What Steam Support told me:\n\nThe support message said my account was banned due to:\n\n* Suspicious activities related to transferring or attempting to sell/trade the account.\n* Community reports and other unspecified factors.\n\nThey added that the ban is permanent and that they can't help me further. They also warned that future support requests regarding this ban might be ignored. 😞\n\n# Why I’m contesting this ban:\n\n* I have never sold, traded, or transferred my account. I’ve been the legitimate owner since the beginning.\n* On the day the ban occurred, I did nothing noteworthy that could have triggered such a sanction.\n* I received no prior warning, which feels incredibly unfair.\n\n# What I’ve tried so far:\n\n* Contacting Steam Support: I explained my situation and asked for more details, but they’re sticking to their decision and closing my tickets.\n* I’m preparing a request based on my Right of Access (GDPR) to get all the data related to my account.\n\n# Questions for the community:\n\n1. Has anyone successfully had a permanent ban lifted on Steam?\n2. Are there steps I can take to prove I’m the legitimate owner of the account?\n3. Any advice on how to word my request to convince support to reconsider my case?\n4. Would it be helpful to contact the CNIL (I’m based in France) to force Steam to provide more information?\n\nI’m really desperate at the thought of losing all my games, purchases, and years of playtime. Thanks in advance for any help and advice you can give!\n\nhttps://preview.redd.it/jk9qv0gmhv5e1.png?width=1289&amp;format=png&amp;auto=webp&amp;s=b3a333ebb08ea133e2c8747ba126f5a68283d9f7\n\nhttps://preview.redd.it/4sopt0gmhv5e1.png?width=1022&amp;format=png&amp;auto=webp&amp;s=56195d5336118faf9413f1514ead7e8d24c788c3\n\nhttps://preview.redd.it/eqrxw0gmhv5e1.png?width=996&amp;format=png&amp;auto=webp&amp;s=ff3539d28ab754e513ad471822c5de652920101d\n\nhttps://preview.redd.it/728xz0gmhv5e1.png?width=1034&amp;format=png&amp;auto=webp&amp;s=bc5335673509929669af785aa244bf8d2dc58da8\n\n02\nSupport access2025-05-09\nAccount recovery & a reported $10,000 loss\n\nThe author alleges that support reset credentials and removed account protection following another person’s recovery ticket.\n\nREDDIT / PUBLIC TESTIMONYr/legaladviceCapture record 110\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 193 words\nGot $10k stollen from steam inventory due to steam' support fault.\n\nsteam_support_tickets_MEGA.json / record 110\n\nLocation: Quebec, Canada.\n\nLast year, someone hacked my Steam account and stole items worth about $10,000 USD. I only noticed this last week. When I talked to Steam Support, they admitted that someone submitted a ticket to make changes on the account and Steam Support reset my password and turned off all my account security.\n\nI asked Steam Support about getting my items back, but they said there was nothing they could do. They told me I should follow their security recommendations.\n\nThe problem is, I did everything they \"suggested\" to protect an account:\n\n* I had two-factor authentication.\n* My phone number was connected to my account.\n* I used Steam Guard.\n* I printed recovery codes and kept them in a safe.\n\nEven though I did all these things, Steam Support still gave someone else access to my account. The stolen items had been in my account since around 2016-2017. Also, I had not logged in for a few years, so I didn’t accidentally give my information to a fake website.\n\nIs there anything I can do, or do I just have to accept losing $10,000 USD?\n\nThanks for your help.\n03\nRestoration2022-07-07\nA reported $500+ loss & template replies\n\nThe author describes an account compromise, disputed transactions and a support response that allegedly did not address the submitted evidence.\n\nREDDIT / PUBLIC TESTIMONYr/DotA2Capture record 45\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 410 words\nFunds stolen through steam market. Disappointed with Steam response.(or lackthereof)\n\nsteam_support_tickets_MEGA.json / record 45\n\nOn 6th July 2022, 44 unauthorized transactions were made on the steam market using my steam wallet funds totalling roughly $500+ USD to buy worthless 1 cent Dota 2 items. This happened during the wee hours in the morning and i contacted them first thing when i woke up. \n\nI have 2FA enabled all the time, and always thought this would not happen to me as I do not go on betting sites/click sketchy links. My account password + emails were not changed, nor did they take my inventory, just that my funds were used illicitly. Also when I went to disable other APIs, it says there are no other APIs to disable. Shows that it wasn't through me clicking sketchy links and leaving my account details there. Would have lost the whole account if i did so.\n\nWhat baffles me is how did they bypass my 2FA to login my account? Why doesn't steam market purchases go through 2FA as well? First time in 9 years that this happened to me. My acc was logged in 'BY' 'Vitebsk' during the illicit purchases but I'm based in Asia I gathered all the screenshots and provided in the ticket to steam support. \n\nAll i got was the standard copy paste template reply by Steam Support. Lost $500+ and was not even worthy of having a proper person to look into this. I dont think they even read or take a look at the screenshots cause if they did, they would have come to the realization that what happened was clearly fraud, and with a few clicks, reverse the unauthorized transactions, refund my wallet and ban the hijacker. \n\nOver the years, i've spent quite a fair bit on steam but really, this is the kind of recourse we get when our account is compromised? They just don’t care, sigh. I only expect the bare minimum from Steam and looks like even that is quite far-fetched.\n\nSS: https://imgur.com/a/67frcls \n\nHijacker: https://steamcommunity.com/profiles/76561199141246495\n\nSteam Response: https://imgur.com/a/V6v4maM\n\nI could think of a few ways on how to Improve:\n\n1) Add 2FA to market transactions. (even if its bulk posting or selling of items, just 1 2FA notif is required)\n\n2) Enable accounts to be region locked. (if you are migrating, then have to go through steam support etc)\n\n3) Additional Lock on Steam Wallet. (Another password perhaps?)\n\nEDIT: 2nd ticket in and I have still yet to receive a non robotic copy paste template response from Steam.\n04\nRestoration2021-11-29\nSteam Guard & an item-restoration refusal\n\nA preserved post includes the author’s account of item theft and a support response declining restoration.\n\nREDDIT / PUBLIC TESTIMONYr/DotA2Capture record 58\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 563 words\nMany people are losing item via clicking links where steam guard is enabled and steam support doesn't not restore items.\n\nsteam_support_tickets_MEGA.json / record 58\n\nAccounts are getting compromised and might be their pc as well where Steam market is targeted hence the malicious links . I am assuming these hackers are getting encouraged where steam support is not doing nothing and they are getting away with hacking items.  \nLiterally the guy who is supporting the game which he doesn't get any in game advantage just  cosmetics in game only for the sole purpose of supporting the game so that the game will prosper and become beautiful way  to enjoy weekend. But right now players are getting hacked left right and center and steam support  is copy pasting message where in short they are blaming the guy who clicked link. 1st this is happening because they are not targeting players but they are targeting market since they are selling those stuff for real cash via party website. Steam is a huge company and can eradicate the problem or at least can remove links temporarily  in chat since hackers are targeting .They made us install steam guard by saying we wont help if there is no steam guard now steam guard is not enough to save our inventory now they changed their policy  that they should not click any suspicious links. How would we know if the link is suspicious ? After clicking and getting our inventory stolen right !   \n\"we'd have to duplicate an item to restore it. Duplication lowers the value of all items by reducing their scarcity and inflating the economy, which affects everyone involved in trading and the Market. To maintain the value of everyone’s inventory, we do not restore items. For more information, please see the Steam Item Restoration Policy.\"  \nThey care for millions of people IN STEAM MARKET where as few  are losing items which is going to affect market where the rightful owner bought the items and hacker is going to sell the item via 3rd party website and enjoy ! HOW IRONIC !!  \nThis is the message from support where my frnd got his items stolen via clicking on link  \n   \nHi there,  \n\nThank you for the information and screenshots provided.  \n\nIt appears that the account was compromised, please take the following steps to secure your account and computer:  \n\nScan your computer for viruses, key loggers, spyware, and other malicious code using antivirus software with updated virus definitions.  \nChange the password for the email address that is associated with your Steam account.  \nRegularly reset your Steam account password.  \n\nPlease see our Security Recommendations article.  \n\nIn addition, I’m sorry to hear that your items were removed without your permission. Unfortunately, Steam Support does not restore scammed, lost, or stolen items for any reason.  \n\nSince Steam Support does not remove items from accounts, we'd have to duplicate an item to restore it. Duplication lowers the value of all items by reducing their scarcity and inflating the economy, which affects everyone involved in trading and the Market. To maintain the value of everyone’s inventory, we do not restore items. For more information, please see the Steam Item Restoration Policy.  \n\nTo make sure that a scammer is reported, please report them through the Steam Community. Reporting a scammer through the Steam Community is the best way to prevent them from committing future scams.  \n\nTo learn how to avoid scams or hijackings, please see our Trade Scam article.  \n\nIf you still need assistance, please let us know.\n05\nEnforcement2025-05-11\nSelective enforcement & an unexplained ban\n\nA community member describes a disputed ban and contrasts it with the visibility of commercial gambling promotion.\n\nREDDIT / PUBLIC TESTIMONYr/SteamUncensoredCapture record 107\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 1,208 words\n🚨 Steam Bans Without Reason and Ignores Its Community — What’s Going On?\n\nsteam_support_tickets_MEGA.json / record 107\n\nHey r/Steam,\n\nI’m writing this to share my thoughts and concerns about my friend [moneylead](https://steamcommunity.com/id/moneylead/) and Steam’s policies in general. I spoke with him yesterday about his situation, though I didn’t discuss writing this post with him—I asked last night, but he hasn’t responded yet. I want to highlight that this issue is broader than just his case, and while Steam might make changes in the future (though that’s unlikely), I feel the community needs to understand how far Steam has strayed from its original values. I’m not trying to put moneylead in a tough spot with this thread—all the info I’m sharing is public, nothing secretive. I hope he won’t be upset with me, but the community needs this case to see the bigger picture and how Steam feels completely unaccountable.\n\n**Why Does Steam Ignore Its Community?**  \nWhy does a platform like **Roblox** provide a detailed log of ban reasons, while Steam, which claims to be \"community-driven,\" ignores its community, bans whoever they want, for whatever they want, with no transparency? I looked into Roblox as a popular game—not a direct competitor to Steam—to see how their bans look, and you can check it out yourself: [Roblox Ban Reasons](https://www.google.com/search?q=Roblox+ban). Their bans are clear, detailed, and actually explain what you did wrong. I think most decent gaming communities operate like this—not with support agents named Olga, hired through outsourcing, who only know how to send canned auto-replies. Take cases like St4ck—or my friend **moneylead**. All these unbans, like **St4ck’s** or **Alexanddd’s**, happened behind closed doors with zero comments from Steam. Of course, it’s convenient for Steam to handle everything in secret, so no one knows or sees what’s going on—but this violates Steam’s own community rules and principles.\n\n**Who Is moneylead?**  \nI’ve known [moneylead ](https://steamcommunity.com/id/moneylead/)since around 2021. We played Dota 2 a couple of times, and then I just stayed on his friends list. He’s always been a legit player, bringing revenue to Steam through purchases. He never sold his skins, whether in **Dota or CS2—he wasn’t a trader**. All he did was:\n\n* Buy games and skins.\n* Collect badges to level up his profile.\n\nAccording to [SteamSets](https://steamsets.com/account/76561199080934614), he’s given out 324,000 Steam Points—I think he awarded profile rewards to all his friends in the list (though I’m not 100% sure). I do know he ran contests and gave gifts to friends, always supporting the community.\n\n**Steam’s Unfair Treatment**  \nI’ve seen Steam remove his showcases, avatar, description, and even his country multiple times—just because he’s from **Ukraine**. He has a ton of haters leaving toxic comments on his wall, and Steam seems to favor **Russian** users. Every time he tried to appeal the removal of his showcases or profile description—which didn’t break any rules, just had his Instagram link, and his avatar is the same as it is now—Steam moderators didn’t care. **They don’t care about top players who bring them massive revenue, nor about regular users.**\n\n>*Here’s the worst part: moneylead works in cybersecurity, specifically fighting account theft and phishing. He’s neutralized over 5,000 threats targeting Steam alone. And yet, Steam bans him for \"account hijacking\"?*\n\nIf you roughly calculate moneylead’s contribution to Steam and the community—his profile, level, badges (not skins, you can’t sell those)—is this normal, Steam? Banning people, closing tickets, and ignoring users with a spotless reputation who aren’t involved in any commercial activity, just bringing you profit without taking anything in return?\n\n**Steam’s Double Standards**  \nI’m honestly shocked:\n\n* YouTubers who promote casinos and skin gambling? Steam’s fine with that.\n* A cybersecurity expert who fights scams, doesn’t promote casinos, and openly talks about it on his profile? **Banned with no explanation, ignored, and denied an unban.**\n\nI wonder if Steam deliberately bans a high-level account once a year just because of their impunity—maybe for hype or something. Otherwise, this is just madness. It’s scary to think how many regular players have lost their accounts and skins—not because of scammers, but because of Steam’s desire to ignore, send auto-replies, and do whatever they want.\n\n**How Many Others Are Affected?**  \nHow many others are out there—maybe not as well-known—who just have a few games or skins, get banned for nothing, and receive zero explanation or response? **Is this even legal?** Every other platform provides a detailed log with specific violations, but Steam slaps on the same vague label and sends templated responses.\n\n* How safe is it to buy skins on Steam?\n* What’s the chance Steam will just ban your account for no reason, with no explanation?\n\n**A Message to Valve**  \nI wish moneylead the best in resolving this, but Valve, it’d be great if you remembered what \"community\" means and started following the law. Because right now, it looks like your 30% commission, impunity, and sense of being above the law in the U.S. have given you the idea that you can do whatever you want.\n\nI’m sure there are many others like moneylead and St4ck—people who aren’t public or don’t have the resources to fight back. Let’s unite these cases. **If you’re a U.S. resident who’s been banned by Steam without reason and wants to challenge it, please reach out to me.** I’m finishing my **Juris Doctor (J.D.) program at SMU Dedman School of Law** in Dallas, Texas, and I’m participating in a legal clinical practice under Rule 13 of the Texas Supreme Court.\n\nWhat Steam is doing is absolutely disgusting and illegal, and **I’d be happy to help any gamer (legitimate, with no real violations) who has games or skins with value. This will be beneficial for my practice, and it’s time to put Steam in its place and show them they can’t just dictate their own rules with arbitration**. Let’s take it all the way—not for punishment, but for the sake of the community. Maybe if Steam loses a case, they’ll change their policies and start explaining their actions like most popular gaming communities do. Many of us remember how Steam Support used to recover stolen accounts and ended up “stealing” skins themselves—banning without real reasons is basically the same thing, and that’s a serious accusation.\n\nSo, r/Steam, see you soon. I think you understand what you’re doing and how many people you’ve illegally deprived of their assets. I want to raise this issue—not just for the U.S., but for the entire world. You’ve banned class-action lawsuits? **Welcome to Texas.** I recommend starting to look for licensed attorneys in Texas, because I’d love to discuss your company’s policies, feedback, and support agents named Olga—a name that strongly associates with Russian users. Maybe it’d be easier to move your company to Moscow? But I’d be happy to discuss these critical issues on behalf of the global gaming community.\n\nAlso, I wouldn’t recommend ignoring the lawsuit request that will be sent to your physical address and email address, as the court will proceed without you, and that might upset you—especially since things aren’t going so well for a company with stocks like yours.\n\n**Thanks to everyone who took the time to read this. For those who need real help with an unjust Steam ban without any explanation, I’d be happy to assist. For users from Texas, we can easily file a collective lawsuit against Steam—let’s connect and make it happen.**\n02 / Steam विकास नेटवर्क\nसार्वजनिक अवसंरचना।विशाल पैमाने पर रिकॉर्ड किया गया।\nसभी 252 रिकॉर्ड डाउनलोड करें ↓\n\nप्रदत्त output_steam_network स्नैपशॉट रिकॉर्ड रिपॉजिटरी, सार्वजनिक योगदानकर्ता/फ़ोर्क संबंध और प्रोफ़ाइल ओवरलैप को दर्ज करता है। ये प्रकाशित रिकॉर्ड हैं — क्या बनाया गया, किसने योगदान दिया, क्या फ़ोर्क किया गया। सार्वजनिक क्षमताओं का कागज़ी निशान वही है जिसे Valve को ध्यान में रखना चाहिए।\n\nभंडार / विवरण\tयोगदानकर्ता\tफोर्कर्स\tरिकॉर्ड की गई प्रोफ़ाइलें\nalliedmodders/amxmodx\n\nAMX Mod X - Half-Life 1 Scripting and Administration\n\n\t40\t40\t80\nalliedmodders/sourcemod\n\nSourceMod - Source Engine Scripting and Administration\n\n\t40\t40\t80\nDoctorMcKay/node-steam-user\n\nAllows interaction with the Steam network via the Steam client protocol\n\n\t40\t40\t80\nFacepunch/Facepunch.Steamworks\n\nAnother fucking c# Steamworks implementation\n\n\t40\t40\t80\nJustArchiNET/ArchiSteamFarm\n\nC# application with primary purpose of farming Steam cards from multiple accounts simultaneously.\n\n\t40\t40\t80\nodota/core\n\nOpenDota: Open source Dota 2 data platform with automated replay parsing\n\n\t40\t40\t80\nodota/dotaconstants\n\ndotaconstants: Static data for Dota applications\n\n\t40\t40\t80\nodota/web\n\nOpenDota: React web UI for Dota 2 statistics using the OpenDota platform\n\n\t40\t40\t80\nsplewis/get5\n\nCS:GO Sourcemod plugin for competitive matches/scrims\n\n\t40\t40\t80\nSteamDatabase/FileDetectionRuleSets\n\n🔎 Rules to detect game engines and other technologies based on Steam depot file lists\n\n\t40\t40\t80\nSteamRE/SteamKit\n\nSteamKit2 is a .NET library designed to interoperate with Valve's Steam network. It aims to provide a simple, yet extensible, interface to perform various actions on the network.\n\n\t40\t40\t80\nValveSoftware/dxvk\n\ndxvk tree containing branches used by Proton\n\n\t40\t40\t80\nValveSoftware/GameNetworkingSockets\n\nReliable & unreliable messages over UDP. Robust message fragmentation & reassembly. P2P networking / NAT traversal. Encryption.\n\n\t40\t40\t80\nValveSoftware/gamescope\n\nSteamOS session compositing window manager\n\n\t40\t40\t80\nValveSoftware/Proton\n\nCompatibility tool for Steam Play based on Wine and additional components\n\n\t40\t40\t80\nValveSoftware/source-sdk-2013\n\nThe 2013 edition of the Source SDK\n\n\t40\t40\t80\nValveSoftware/wine\n\nWine with a bit of extra spice\n\n\t40\t40\t80\nValveSoftware/steam-devices\n\nList of devices Steam and SteamVR will want read/write permissions on, to help downstream distributions create udev rules/etc\n\n\t39\t40\t79\nValveSoftware/steam-audio\n\nSteam Audio\n\n\t38\t40\t78\nalliedmodders/metamod-source\n\nMetamod:Source - C++ Plugin Environment and Detour Library for the Source Engine\n\n\t37\t40\t77\nalliedmodders/sourcepawn\n\nA small, statically typed scripting language.\n\n\t35\t40\t75\nValveSoftware/Fossilize\n\nA serialization format for various persistent Vulkan object types.\n\n\t31\t40\t71\nrlabrecque/Steamworks.NET\n\nSteamworks wrapper for Unity / C#\n\n\t27\t40\t67\nModDota/moddota.github.io\n\nModDota github pages project.\n\n\t26\t40\t66\nodota/parser\n\nReplay parse server generating JSON log events from Dota 2 replay files\n\n\t26\t40\t66\nValveSoftware/steam-for-linux\n\nIssue tracking for the Steam for Linux beta client\n\n\t26\t40\t66\nSteamRE/DepotDownloader\n\nSteam depot downloader utilizing the SteamKit2 library.\n\n\t24\t40\t64\nJustArchiNET/ASF-ui\n\nThe official web interface for ASF\n\n\t23\t40\t63\nadvancedfx/advancedfx\n\nHalf-Life Advanced Effects (HLAE) is a tool to enrich content creation mainly for the Counter-Strike series.\n\n\t22\t40\t62\nalliedmodders/ambuild\n\nAlliedModders C++ Build System\n\n\t23\t39\t62\nSteamDatabase/BrowserExtension\n\n💻 SteamDB's extension for Steam websites\n\n\t21\t40\t61\nodota/mobile\n\nReact Native apps for viewing Dota 2 data on Android/iOS\n\n\t19\t40\t59\nValvePython/steam\n\n☁️ Python package for interacting with Steam\n\n\t18\t40\t58\nskadistats/clarity\n\nComically fast Dota 2, CSGO, CS2 and Deadlock replay parser written in Java.\n\n\t13\t40\t53\nSteamRE/open-steamworks\n\nOpen Steamworks is a set of reverse engineered headers for the Valve's Steam Client. More or less abandoned now that the Steamworks SDK is publically available.\n\n\t13\t40\t53\nValveSoftware/Source-1-Games\n\nSource 1 based games such as TF2 and Counter-Strike: Source\n\n\t13\t40\t53\nalliedmodders/hl2sdk\n\nHalf-Life 2 SDK Mirrors\n\n\t11\t40\t51\nSteamDatabase/steamdb.info-issues\n\n🚱 Issue tracker for the SteamDB website\n\n\t11\t40\t51\nCSGOFloat/inspect\n\nSource Code that Powers the CSFloat Inspect Link API\n\n\t10\t40\t50\nValveSoftware/SteamOS\n\nSteamOS community tracker\n\n\t10\t40\t50\nalliedmodders/source2mod\n\nExperimental\n\n\t40\t9\t49\nsmiley/steamapi\n\nAn unofficial object-oriented Python library for accessing the Steam Web API.\n\n\t9\t40\t49\nSteamDatabase/GameTracking\n\n🛢 Dumping things, so you don't have to\n\n\t8\t40\t48\nValveSoftware/counter-strike_rules_and_regs\n\nCS:GO\n\n\t7\t40\t47\nValveSoftware/openvr\n\nOpenVR SDK\n\n\t6\t40\t46\nSteamDatabase/easy-markdown-editor\n\nEasyMDE: A simple, beautiful, and embeddable JavaScript Markdown editor. Delightful editing for beginners and experts alike. Features built-in autosaving and spell checking.\n\n\t40\t4\t44\nValveSoftware/Dota-2\n\nTracker for issues specific to Linux and Mac in the Reborn client. If you have a general issue or non-system-specific feature request please go to dev.dota2.com\n\n\t6\t38\t44\nValveSoftware/Dota2-Gameplay\n\nPublic Bug Tracker for Dota 2\n\n\t4\t40\t44\nJustArchiNET/ArchiBot\n\nNo description in the capture.\n\n\t16\t27\t43\nztizzlegaming/CSGOWinBig\n\nOpen-source Counter-Strike: Global Offensive jackpot betting website.\n\n\t1\t40\t41\nJustArchiNET/mantis.justarchi.net\n\nMantis Bug Tracker (MantisBT)\n\n\t40\t0\t40\nodota/node-steam-user\n\nAllows interaction with the Steam network via the Steam client protocol\n\n\t40\t0\t40\nModDota/TypeScriptAddonTemplate\n\nDota 2 addon template with TypeScript Panorama and VScripts.\n\n\t9\t29\t38\nValvePython/vdf\n\n📜 Package for working with Valve's text and binary KeyValue format\n\n\t6\t32\t38\nalliedmodders/amtl\n\nAlliedModders C++ Template Library\n\n\t17\t19\t36\nValvePython/dota2\n\n🐸 Python package for interacting with Dota 2 Game Coordinator\n\n\t5\t30\t35\nalliedmodders/stripper-source\n\nStripper:Source\n\n\t13\t21\t34\nAllyans3/steam-market-api-v2\n\nSteam Market API v2 package\n\n\t3\t31\t34\nModDota/dota-tutorial\n\nCustom game DOTA tutorial.\n\n\t11\t23\t34\nodota/blog\n\nNo description in the capture.\n\n\t29\t3\t32\nOpsecGuy/BetterGo\n\nExternal CS:GO cheat written in python.\n\n\t1\t27\t28\npxvr-official/1\n\n無許諾配信 企業理念剽窃 動物の森収益化 大神ミオ権利者削除 戌神権利侵害発言 常闇トワ炎上 夜空メルストーカー被害 建築王サポーター放置 赤十字マーク 魔乃アロエ卒業 一つの中國支持声明 大空昴3Dライブ 無限延期清掃員職業差別 日清コラボ楽曲 musedash非公開 rog案件取り消し 壁画ライブ 丁真 Ding Zhen 郑爽 Zheng Shuang 防护林 与朵小天使w 伊月猫凛 本主萌埋午休傻 汪峰 重生细胞 壁纸 比利海灵顿 香蕉君 van 田所浩二 抽象带篮子 抗压背锅吧 季子越 蒋明辉 傻逼…\n\n\t0\t28\t28\nRevadike/InternalSteamWebAPI\n\nDocumenting the unofficial and internal Steam Web API\n\n\t1\t27\t28\nJoeSzymkowiczFiveM/qb-lootcrate\n\nA CSGO-style case opening script\n\n\t2\t25\t27\nAbrarKL/MyRoulette.XYZ\n\nCSGO / Steam Roulette Site created with PHP and Node JS, using the Material Design front-end framework.\n\n\t1\t25\t26\nJustArchiNET/ASF-WebConfigGenerator\n\nNo description in the capture.\n\n\t10\t15\t25\nModDota/dota-data\n\nAuto-generated Dota 2 resource dumps\n\n\t11\t14\t25\nModDota/TypeScriptDeclarations\n\nTypeScript declarations for Dota 2.\n\n\t11\t14\t25\nModDota/API\n\nNo description in the capture.\n\n\t12\t12\t24\nalliedmodders/cssdm\n\nCounter-Strike:Source Deathmatch\n\n\t10\t13\t23\nSteamDatabase/steamstat.us\n\n✅ Front-end of Steam services status website\n\n\t4\t18\t22\nc0deina/csgojackpotV2\n\nCSGO Jackpot Source\n\n\t1\t20\t21\nValvePython/steamctl\n\n🤸 Take control of Steam from your terminal\n\n\t2\t19\t21\nValvePython/csgo\n\n🔫 Python package for interacting with CS:GO Game Coordinator\n\n\t3\t17\t20\nBeepIsla/csgo-crash-exploit\n\nAllows you to crash any Windows user\n\n\t3\t16\t19\nValvePython/vpk\n\n📦 Open, Search, Extract and Create VPKs in python\n\n\t4\t15\t19\nalliedmodders/SM-SteamWorks\n\nExposing SteamWorks functions to SourcePawn.\n\n\t14\t3\t17\nSteamRE/Steam4NET\n\nSteam4NET is a .NET wrapper around the Steamworks C++ interfaces\n\n\t2\t15\t17\nalliedmodders/hl2sdk-manifests\n\nInformation about HL2SDKs shared between Metamod:Source and SourceMod.\n\n\t6\t10\t16\nJustArchiNET/ASF-PluginTemplate\n\nTemplate repository that you can use for creating custom plugins for ArchiSteamFarm.\n\n\t8\t7\t15\nModDota/Dota2AIFramework\n\nGeneral Framework for Dota 2 AI Competitions\n\n\t1\t14\t15\nShkyyl/KeyChamp\n\nExtension for joining free case battle on key-drop automatically\n\n\t1\t14\t15\nSteamDatabase/SteamMonitor\n\n😤 Track Steam's connection manager servers status\n\n\t2\t12\t14\nBaterka/cslore.com\n\nCS:GO gambling site - csgo.style\n\n\t1\t12\t13\nSteamDatabase/SteamTokenDumper\n\n🔢 Submit users' PICS access tokens to SteamDB\n\n\t2\t11\t13\nmonoblocker/roulette\n\nRoulette CS:GO made in React and Typescript\n\n\t1\t11\t12\nzsith/launcher.user.js\n\n// ==UserScript== // @name AposLauncher // @namespace AposLauncher // @include http://agar.io/* // @version 3.062 // @grant none // @author http://www.twitch.tv/apostolique // ==/UserScript== var aposLauncherVersion = 3.062; Nu…\n\n\t1\t11\t12\nLincolnIT/CSGODouble-bot-automated\n\nCSGODouble Automated, auto Betting Bot.\n\n\t1\t10\t11\nvladpuz/steam-market\n\nSteam market API client\n\n\t4\t7\t11\nmcgrizzz/Cstrike.bet\n\nCSGO Roulette Website Angular frontend, nodejs backend, and steam trading bots\n\n\t1\t9\t10\nodota/underlords-web\n\nUI for OpenUnderlords\n\n\t5\t5\t10\nSteamDatabase/SteamToTwitter\n\n🕊 Tweets announcements from various Steam groups\n\n\t1\t9\t10\nModDota/AbilityLuaSpellLibrary\n\nThe successor to the Spell Library by Pizzalol\n\n\t4\t4\t8\nalvinl/bitskins\n\nUnofficial BitSkins API client\n\n\t2\t5\t7\nb1naryth1ef/steamy\n\nA Python Steam community and market API interface that will get you all hot and bothered\n\n\t2\t5\t7\nkratos1812/Case-Opening\n\nIn-game case opening system for CSGO servers.\n\n\t2\t5\t7\nodota/docs\n\nOpenDota API documentation\n\n\t4\t3\t7\nSteamDatabase/steam-advanced-access-fetch-players\n\n📈 Simple script to fetch Steam player count\n\n\t1\t6\t7\nTheRioMiner/CsgoBetterExternalRaytrace\n\nOverridden maps pack for better external raytrace\n\n\t1\t6\t7\nalliedmodders/hl2sdk-mock\n\nMock HL2SDK and Server\n\n\t5\t1\t6\nchristophersu/PySteamMarket\n\nPython API for getting prices from the Steam market.\n\n\t1\t5\t6\nExtremelyd1/Strat-Roulette\n\nCS:GO Sourcemod Plugin\n\n\t2\t4\t6\ngiovanni-orciuolo/double-sdk\n\nA simple way to write CS:GO cheats!\n\n\t2\t4\t6\nJustArchiNET/Madness\n\nMadness embraces your project by including compatibility layer for selected APIs normally not available on .NET Framework target.\n\n\t5\t1\t6\nModDota/TypescriptPanoramaDeclarations\n\nNo description in the capture.\n\n\t4\t2\t6\nodota/rapier\n\nA JavaScript Dota 2 (Source 2) replay parsing library\n\n\t1\t5\t6\nVozn1akHero/CSGOCaseOpeningSimulator\n\nCounter-Strike case opening simulator which resembles the good old CS:GO user interface\n\n\t3\t3\t6\nautarc/steam-store\n\nAPI client for the unofficial steam storefront/big picture resource\n\n\t2\t3\t5\nBETTING-CODE/awesome-esports-sites\n\nA curated list of awesome esport betting sites – live, statistics and other resources.\n\n\t1\t4\t5\njonteohr/Better-Warden\n\nAn improved and more advanced warden plugin with a custom menu for CS:GO jailbreak servers!\n\n\t2\t3\t5\nLudzikk/CSGO-Gambling-Site\n\nhttps://ludzikk.github.io/CSGO-Gambling-Site/\n\n\t1\t4\t5\nModDota/find-steam-app\n\nFind location of an installed Steam app\n\n\t3\t2\t5\nmprey/csgocact.us\n\nsource code for csgocact.us\n\n\t1\t4\t5\nnezu-cc/ServerCrasher\n\nCS:GO Server Crasher\n\n\t1\t4\t5\nodota/testfiles\n\nStores test replay files\n\n\t2\t3\t5\nodota/underlordsconstants\n\nConstant data for Dota Underlords\n\n\t3\t2\t5\nSnaBe/node-steam-market-fetcher\n\nA Node.js wrapper for the Steam Community Market API.\n\n\t2\t3\t5\nSteamDatabase/.github\n\n💗 Organization-wide community health files\n\n\t1\t4\t5\nwolfcon/RIP-HLTV-BET\n\nRIP BET AD (For Tampermonkey) https://greasyfork.org/en/scripts/423484-rip-hltv-bet\n\n\t2\t3\t5\nalliedmodders/blaster.net\n\nSource and GoldSrc Query Tool\n\n\t2\t2\t4\ncatears124/CS2-Price-API\n\nsimple python cs2 steam market price API\n\n\t1\t3\t4\nialakey/caseforge\n\nOpen-source CS2 case-opening platform: Steam auth, provably fair openings, RTP-balanced case builder, withdrawals bought on market.csgo.com and an admin CRM.\n\n\t1\t3\t4\nIlusion9/csgo-fix-mapchange-crash-sm\n\nFix players crash on map change.\n\n\t1\t3\t4\nismail0234/Benson-Map-Crash-Fixer\n\nCSGO Map Change Client Crash Fixer\n\n\t1\t3\t4\njaxwilko/steam-market-api\n\nPHP - Composer Compatible - Steam Market API\n\n\t2\t2\t4\nJustArchiNET/ArchiTag\n\nArchiTag is a very small utility based on Python 3 and Mutagen to provide missing functionality in opusenc of writing specific Opus metadata, such as total number of tracks or track number.\n\n\t1\t3\t4\nModDota/DotaUI\n\nNo description in the capture.\n\n\t2\t2\t4\nnode-steam/market-pricing\n\nWrapper for the unofficial Steam Market Pricing API\n\n\t1\t3\t4\nodota/media\n\nStores media files for Dota projects\n\n\t2\t2\t4\nSergeyIvanovDevelop/Crypto-Steam-Platform\n\nThe repository contains the code and configuration to run a platform for creating cryptocurrency stakes for arbitrary ERC20 tokens.\n\n\t1\t3\t4\nAareksio/csgodouble-floatchecker\n\nAdds context menu option to check item's float value\n\n\t1\t2\t3\nchinm4/CSGOdrop\n\nA online csgo gambling casino that includes a variety of mini games that allows you to win csgo skins\n\n\t2\t1\t3\nCruze03/CSGO-Case-Opening-Prank\n\nCommand:- !prank (Admin flag \"n\" required)\n\n\t1\t2\t3\nDhruva-Kapadia/CSGOTrollGG\n\nCSGO Case Opening Simulator\n\n\t2\t1\t3\nErhanCSGO/CSGOPolygon-prediction\n\nCSGOPolygon.com - prediction script, double your coins by using this tool\n\n\t1\t2\t3\nEv-Hoang/Bedrock-Chest-Case-Opening\n\nHypixel Skyblock Dungeon Mod - Bedrock Chest Opening Animation (CSGO Style)\n\n\t1\t2\t3\njmjp/csgo-roulette\n\nA csgo gambling roulette make with VueJS 3\n\n\t2\t1\t3\nJustArchiNET/ArchiCrowdin\n\nNo description in the capture.\n\n\t1\t2\t3\nLeonSK/WearMarketInspector\n\nRetrieve Wear Value (Float Value) and Pattern Index from Steam Community Market using http://csgo.exchange API\n\n\t1\t2\t3\nmaximgeerinck/csgo-gamble\n\nCSGO gambling website\n\n\t1\t2\t3\nModDota/BugTracker\n\nListing bugs for Dota 2 Custom Games\n\n\t2\t1\t3\nplwp/mma-betting\n\nUFC/MMA betting model with Pinnacle steam detection for AU book latency arb\n\n\t2\t1\t3\nSouthsideswag16/Csgo-Gambling-Site\n\nNo description in the capture.\n\n\t2\t1\t3\ntacyarg/csgofiesta-frontend-react\n\nRemastered version a the long time favorite csgo site\n\n\t2\t1\t3\nVelorasse/Mutah-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-csmoney-csgoskins\n\ngambling script for Mutah, Keydrop, csmoney, and csgoskins, featuring hacks, cheats, and predictors. Offers strategies to boost winning odds and optimize performance on these platforms.\n\n\t3\t0\t3\nalliedmodders/am-github-artifact-webhook\n\nNo description in the capture.\n\n\t2\t0\t2\ncharamza/roulette\n\nCSGO like roulette in JS\n\n\t1\t1\t2\nCruze03/CSGO-PugSetup-RoundRestore\n\nSometimes (player dropped/crashed) which would be disadvantage for a team. It would be very handy to restore the match to the previous round.\n\n\t1\t1\t2\ncsgorol/CSGO-ROLL-Crash-Predictor\n\nCSGO-ROLL-Crash-Predictor\n\n\t1\t1\t2\nFoxSerito/FOXWORLD_plugin_DoubleJump_CSGO\n\nПлагин SourceMod (CSGO). Двойной прыжок с эффектом.\n\n\t1\t1\t2\nhkehayovmoonbiz/CS2-Casino-Full-Source-Code\n\nCS2, CS2 betting platforms, Skin Roulette, Case Unboxing, Crash games, Jackpot, purchase CS2 casino source, crypto gambling\n\n\t1\t1\t2\nJustZakary/steamstoreapi\n\nThis NPM module is a API wrapper that makes the steam unofficial API easier to use.\n\n\t2\t0\t2\njzimr/steam-market-api\n\nA java library to easily get Steam Community Market data\n\n\t1\t1\t2\nMomohime/CSGO.Network-Jackpot-Coinflip\n\nNo description in the capture.\n\n\t1\t1\t2\nnnjjswat/moneybot\n\nautomated bots for bustabit (formerly known as moneypot), csgo crash, etc\n\n\t0\t2\t2\nodota/carry\n\nLegacy Application for donations to the OpenDota project\n\n\t1\t1\t2\nodota/PublicMatchDataBot\n\nA Discord bot to remind users to turn on Expose Public Match Data in the Dota 2 client\n\n\t1\t1\t2\nOrillio/CSGOBet.com\n\nCSGO roulette web app\n\n\t2\t0\t2\nripexz/csgo-bet-alert\n\nA Chrome extension to keep track of active CS:GO Lounge matches.\n\n\t1\t1\t2\nrrpvm/lumen_sense-beta-deprecated-\n\nthis is internal csgo cheat written by me(no paste, self reverse structures). start : ~6 August 2020, end : ~ 14 December 2020\n\n\t1\t1\t2\nRuthless222/csgoscore\n\nThis is a Counter Strike Global Offensive Betting Site. You chose the skins you want to bet and try to win jackpots\n\n\t2\t0\t2\ntfburns/CSGO-cases-PL\n\nExpected profit-loss of CS:GO case openings\n\n\t1\t1\t2\nTomDra/CSGO-Case-Data-Analysis\n\nWorks out the most profitable CS:GO case at that current time\n\n\t1\t1\t2\nValvePython/dota2-wrappers\n\nNo description in the capture.\n\n\t1\t1\t2\nValvePython/teamfortress2-closed-captions\n\nThis project aims to provide a set of closed captions for Team Fortress 2\n\n\t1\t1\t2\nVistaNetGTX/Cstrike.bet-\n\nCSGO Roulette Website Angular frontend, nodejs backend, and steam trading bots\n\n\t1\t1\t2\nwafflas/csgo-case-opening-simulator\n\nI created a cs go case opening simulator for a meme coin\n\n\t0\t2\t2\nAdmiral-Enigma/Le_Coinflip\n\nConflip game\n\n\t1\t0\t1\nadryeljuliao/roulette-csgo\n\nNo description in the capture.\n\n\t1\t0\t1\nAndreuTheG/csgo-coinflip-web\n\nCSGO Gambling Coinflip Website\n\n\t1\t0\t1\nasmilen/csgoDouble\n\na b c\n\n\t1\t0\t1\nb1naryth1ef/csgofort\n\nA CSGO portal for trading, betting, analytics, and more!\n\n\t1\t0\t1\nBaterka/PrivateSteamBettingWebsite2024\n\nPrivate Steam (Counter-Strike 2) betting/gambling website - Roulette, Jackpot\n\n\t1\t0\t1\nblackcaer/SteamTradeHandler\n\nAutomation of Steam trading. Helper project for bet automation.\n\n\t1\t0\t1\nBTheCoderr/theRounders\n\nThe Rounders - A professional-grade sports betting analytics platform combining real-time odds tracking, sharp movement detection, and advanced statistical analysis. Features include line shopping, steam move alerts, power rankings, and comprehensive bet t…\n\n\t1\t0\t1\nCallumHemsley/KazeBot\n\nA Twitch chat betting bot for CSGO, simply bet a certain amount of points, and double if you win, lose all if you lose. Simple.\n\n\t1\t0\t1\nchrisjpm/CSGOJackpotTemplate\n\nFront end for a jackpot site\n\n\t1\t0\t1\ncolinsenner/valve-bug-bounty\n\nFor many years CS:GO, Dota 2, and Team Fortress 2 servers had a bug that allowed malicious users to leak crucial server process memory or reliably crash any server.\n\n\t1\t0\t1\ncoryypeters/nrl-odds-intelligence-pipeline\n\nReal-time sports betting odds intelligence — streaming pipeline that detects line movement, steam, and arbitrage across bookmakers. Python · Redis Streams · FastAPI · React.\n\n\t1\t0\t1\ndeissh/dev-csgoduo\n\nCS:GO. Bot for receiving things on the site (Polygon, Duo, Double and etc).\n\n\t1\t0\t1\ndom1torii/even-better-font-manager\n\nSimply even better cross-platform tool for CS2 Font Management\n\n\t1\t0\t1\nDONnicov/CSGO-crash-black-screen-\n\nsolution csgo crash black screen and close csgo\n\n\t1\t0\t1\nDoubleBoters/CsgoDouble\n\nNo description in the capture.\n\n\t1\t0\t1\ndownarowiczd/DoubleBot\n\nAn old CSGO Double Bot written for my friend. - 07.05.2016\n\n\t1\t0\t1\nErayBahar/steammarketscraper\n\nSteam Market Scraper Python-based tool that tracks real-time CS2 skin prices using Steam's hidden API. It fetches the lowest sell and highest buy offers for any item, helping you monitor deals or snipe underpriced listings automatically.\n\n\t1\t0\t1\nfairydarkness/SteamwebmailAPI\n\nUnofficial Python API for steamwebmail.com Fast, lightweight, and browserless library for automating steamwebmail.com. Support for session management, proxy, folder navigation, and message retrieval\n\n\t1\t0\t1\nFAQU2/CSGO-Coinflip-MyJailShop\n\nSourcemod plugin which provides a Coinflip system for MyJailShop.\n\n\t1\t0\t1\nFlamesONE/csgo-case-opening\n\nNo description in the capture.\n\n\t1\t0\t1\nFunnyRain/csgorun-crash-watch\n\n🚀 CsgoRun dump crash. / 🚀 CsgoRun дамп крашей.\n\n\t1\t0\t1\ngeohdgio/Venatus-Autenticator\n\nეს არის Steam Autenticator ქართული Venatus Trade & Betting ისთვის და Valve News Georgia-სთვის.\n\n\t1\t0\t1\nhakanstarlord/steam-bot\n\nSports betting steam-move signal detection with ML pipeline (XGBoost stacking + isotonic calibration), backtesting engine, Flask dashboard, and Telegram alerts.\n\n\t1\t0\t1\nHvH-gg/CSGO-Item-CrashFix\n\nA plugin for Counter-Strike: Global Offensive that fixes an exploit where receiving CS2 Items will cause CS:GO clients to crash\n\n\t1\t0\t1\nHvH-gg/CSGO-NetMsg-CrashFix\n\nA plugin for Counter-Strike: Global Offensive that fixes an exploit where spamming NetMsg_StringCmd packets would result in a server crash.\n\n\t1\t0\t1\nisybycnsmam/SteamLibrary\n\nLegacy Steam Unofficial API\n\n\t1\t0\t1\nItsTangerine/SteamApis.Net\n\nUnofficial https://steamapis.com .NET library, supporting .NET 6.0+\n\n\t1\t0\t1\nJustArchiNET/JustArchi.net\n\nNo description in the capture.\n\n\t1\t0\t1\nkiri-osint/CS2-Info-Hub-Bot\n\nA Telegram bot that acts as a hub for CS2 players, providing real-time skin prices, server stats, and user profile/inventory inspection using official and unofficial Steam APIs.\n\n\t1\t0\t1\nKoshkaj/monte\n\nGamified csgo gambling platform implementation\n\n\t1\t0\t1\nmadsab/CaseOpening\n\nA school project using Java. Simulating the case opening from CSGO and more.\n\n\t1\t0\t1\nman90es/steamcardexchange-api\n\nSteamCardExchange.net unofficial REST API server (scraper).\n\n\t1\t0\t1\nMattPua/steam-unofficial-docs\n\nUnofficial docs for Steam APIs with fumadocs\n\n\t1\t0\t1\nMetallist1/Portfolio.CsgoWinGambleProject\n\nA website that was done in 2017 September. Websites focus was on gambling with Counter-Strike items. Project was largely completed however backups were not done correctly, this resulted in half a year of wasted improvements to the code. The website was test…\n\n\t1\t0\t1\nmikebobadilla/csgo-jackpot\n\nNo description in the capture.\n\n\t0\t1\t1\nmikebobadilla/meteor-csgojackpot\n\nCssgo Jackpot done in meteor\n\n\t1\t0\t1\nModDota/D2VDump\n\nDota 2 Server VScript API Dumper\n\n\t1\t0\t1\nModDota/DotaTracking\n\nNo description in the capture.\n\n\t1\t0\t1\nModDota/eslint-config\n\nESLint config by ark120202\n\n\t1\t0\t1\nmr-codinglv/Casino-script\n\nscript casino - script betting - exchange script - bc casino - casino csgo - script bet - betwin script\n\n\t1\t0\t1\nMrKeelik/MrKeel\n\nCSGO DOUBLE BOT\n\n\t1\t0\t1\nnoahlatzel/CSGORollHelper\n\nLeveraging positive expected value on triple green jackpots on CSGORoll!\n\n\t1\t0\t1\noddsgpt/oddsgpt-market-intelligence\n\nResearch on football betting markets, closing odds, CLV, market efficiency, steam moves, AI betting systems, and sports market intelligence.\n\n\t1\t0\t1\noEXU/csgo-server-crasher\n\nCSGO SERVER CRASHER\n\n\t1\t0\t1\nPrdTTony/CSGO-Roulette\n\n[CSGO] Roulette System. Bet on RED or Black and win x2 credits\n\n\t1\t0\t1\nr-adamski/csgo-jackpot\n\nNo description in the capture.\n\n\t1\t0\t1\nSahotallo/Turan-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-Skinbaron-hellcase\n\ngambling script for Turan, Keydrop, Skinbaron, and Hellcase, providing hacks, cheats, and predictors. Includes strategies to improve winning chances and enhance gameplay on these platforms.\n\n\t1\t0\t1\nsamuelcsouza/steam-marketplace-api\n\nAn unofficial API to get data from the Steam Marketplace.\n\n\t1\t0\t1\nSKINSTRACK/CS2-Price-API\n\nSkinstrack offers a free, limited API endpoint that returns Steam item prices. Paid plans additionally provide access to pricing data from multiple marketplaces, making it possible to compare prices across different markets through a single API.\n\n\t1\t0\t1\nsnmtriet/CSGO-Casino-Full-Source-Code\n\nCSGO, CSGOEmpire, Case Opening, Case Battles, Roulette, Coinflip, buy csgo gambling site, gambling\n\n\t1\t0\t1\nSteamRE/homebrew-tools\n\nRepository for installation of SteamRE tools via Homebrew (http://brew.sh)\n\n\t1\t0\t1\nSteamRE/opensteamworks.org\n\nNo description in the capture.\n\n\t1\t0\t1\nTheQuack45/CsgoCaseOpenProgram\n\nSimple program to parse an XML file with CS:GO case information and \"simulate\" case openings\n\n\t1\t0\t1\nTLClassless/StratRouletteCSGO\n\nA 'Strat Roulette' web app for CS:GO!\n\n\t1\t0\t1\ntomasoom/csgoCaseOpening\n\nNo description in the capture.\n\n\t1\t0\t1\nvitaliy-evsyukov/steamgifts-autobet-bookmarklet\n\nbookmarklet for automatic bets on steamgifts.com\n\n\t1\t0\t1\nXpravdaX/RouletteCSGO\n\nNo description in the capture.\n\n\t1\t0\t1\nYuiKasumii/steam_api_unofficial\n\nUnofficial Steam Game Information Database\n\n\t1\t0\t1\nZexuz/Steam-Betting\n\nA betting website build ontop of STEAM's ecosystem\n\n\t1\t0\t1\nANK-RULZZ/steam-jackpot-site\n\ngetting some errors and would like some one to help me with it thank you!!!\n\n\t0\t0\t0\nasmilen/CsgoDoubleVS\n\nNo description in the capture.\n\n\t0\t0\t0\nCORNOODOSADAS/CSGOWeed\n\nCsgo Jackpot and Coinflip\n\n\t0\t0\t0\nCSGOApple/csgoapple\n\nJackpot Site\n\n\t0\t0\t0\nCSGOFAST/csgofast-api\n\nNo description in the capture.\n\n\t0\t0\t0\nDonakall/csgoDoublebot\n\nAutomated bot for csgodouble\n\n\t0\t0\t0\nfedor-selivanov/csgo-fast-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nfoldageros/csgod\n\ndouble bot\n\n\t0\t0\t0\ngmod-gambling/gmod-gambling\n\nNo description in the capture.\n\n\t0\t0\t0\nierome/CSGOBoss-BackEnd\n\nBack end version of CSGOBoss. This was a CSGO Gambling site named CSGOBoss. Coded by an old friend of mine Dahquan Hinds (https://github.com/dahquan/) Thought I would release this to help out any one who would need it.\n\n\t0\t0\t0\njamienp1/CSGODOUBLE-BOT-AUTO\n\ni got a bot thats is betting on the last winning color except from green and if you lose it will double the coins you set it to bet, pretty good, so when there comes a loooong train you will be gaining a bit of money codepaste_net/ugmt92 remove all the _ an…\n\n\t0\t0\t0\nJEYONER/CSGOTOXIC\n\nPAGINA DE JACKPOT CSGO SKINS\n\n\t0\t0\t0\nkalrish/csgo-jackpot\n\nStressful but funny zombie-like Counter-Strike: Global Offensive game mode.\n\n\t0\t0\t0\nkrys12345/roulettee\n\n// ==UserScript== // @name CSGO Predict Bot // @namespace http://csgodouble.com // @version 1.0 // @description predicts what number its gonna be // @author Meee // @match http://www.csgodouble.com/ // @grant none // ==/…\n\n\t0\t0\t0\nLilDuggiMuffi/CSGODouble-Working-Bot\n\nFixed CSGO Double Bot\n\n\t0\t0\t0\nLyricLy/Steam2Proton\n\nCheck if all your Steam games will work with Proton! Uses the official Steam API and the unofficial Proton API.\n\n\t0\t0\t0\nM0NsTeR77/csgo-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nozanhalis/Hi\n\n// ==UserScript== // @name CS GO LOUNGE BOT-Ozan Halis // @namespace http://csgolounge.com/ // @version 0.6.6 // @description Cs Go Lounge Hızlı BOT // @match http://csgolounge.com/* // @match http://dota2lounge.com/* // @updateURL h…\n\n\t0\t0\t0\nscoobertus/CSGO-DoubleBot\n\nNo description in the capture.\n\n\t0\t0\t0\nTradeal/CSGO-Jackpot-Bot\n\nNo description in the capture.\n\n\t0\t0\t0\nValvePython/artifact\n\nNo description in the capture.\n\n\t0\t0\t0\nVampire/CSGO-Roulette-Bot\n\nNo description in the capture.\n\n\t0\t0\t0\nvdemans/csgo-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nVocoreVideo/CSGODungeon-\n\nCSGO Jackpot\n\n\t0\t0\t0\nwayz-dev/csgofloat\n\nNo description in the capture.\n\n\t0\t0\t0\n\nSnapshot: 17 सितंबर 2026, 11:19:11 जैसा कि स्रोत में लिखा है; समय क्षेत्र निर्दिष्ट नहीं है। संबंध संग्रह निर्यात में सीमित है (कई श्रेणियाँ 40 पर रुकती हैं)। योगदानकर्ता और फोर्कर्स कुल मिलाकर 4,554 भूमिका प्रविष्टियाँ 4,214 अलग-अलग प्रोफ़ाइल–रिपॉजिटरी जोड़ों में होती हैं; एक प्रोफ़ाइल में दोनों भूमिकाएँ हो सकती हैं। शून्य का अर्थ है कि उस श्रेणी में कोई रिकॉर्ड नहीं मिला। रिपॉजिटरी नामों में उपनाम या केस वेरिएंट्स शामिल हो सकते हैं; कुल योग स्रोत की गणना पद्धति को बनाए रखते हैं।\n\nस्रोत उत्पत्ति\nआपकी एकत्रित फ़ाइलों से निर्मित।\nसमर्थन गवाही\n2323/reddit_scams_ultra/steam_support_tickets_MEGA.json · पंक्तियाँ 45,58,107,110,294\nनेटवर्क स्नैपशॉट\nnetwork-repositories.csv · कच्चा_डेटा.जेसन · overlaps.csv · summary.txt (मैनिफेस्ट में ऐतिहासिक स्रोत पथ बनाए रखे गए)\n\nमैनिफेस्ट में स्रोत पथ, बाइट आकार, SHA-256 हैश और चयनित रिकॉर्ड स्थितियाँ दर्ज की जाती हैं। कच्ची कैप्चर जांच की व्याख्या से अलग रहती हैं।\n\nस्रोत मैनिफेस्ट डाउनलोड करें ↓",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam प्रवर्तन साक्ष्य — समर्थन अभिलेख और डेवलपर नेटवर्क"
          },
          {
            "level": 2,
            "id": null,
            "text": "शिकायत पढ़ें।स्रोत संलग्न रखें।"
          },
          {
            "level": 3,
            "id": null,
            "text": "Permanent sanction & closed appeals"
          },
          {
            "level": 4,
            "id": null,
            "text": "Permanently banned Steam account without a clear explanation, need help!"
          },
          {
            "level": 3,
            "id": null,
            "text": "Account recovery & a reported $10,000 loss"
          },
          {
            "level": 4,
            "id": null,
            "text": "Got $10k stollen from steam inventory due to steam' support fault."
          },
          {
            "level": 3,
            "id": null,
            "text": "A reported $500+ loss & template replies"
          },
          {
            "level": 4,
            "id": null,
            "text": "Funds stolen through steam market. Disappointed with Steam response.(or lackthereof)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam Guard & an item-restoration refusal"
          },
          {
            "level": 4,
            "id": null,
            "text": "Many people are losing item via clicking links where steam guard is enabled and steam support doesn't not restore items."
          },
          {
            "level": 3,
            "id": null,
            "text": "Selective enforcement & an unexplained ban"
          },
          {
            "level": 4,
            "id": null,
            "text": "🚨 Steam Bans Without Reason and Ignores Its Community — What’s Going On?"
          },
          {
            "level": 2,
            "id": null,
            "text": "सार्वजनिक अवसंरचना।विशाल पैमाने पर रिकॉर्ड किया गया।"
          },
          {
            "level": 2,
            "id": null,
            "text": "आपकी एकत्रित फ़ाइलों से निर्मित।"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/hi/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/hi/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/selected-support-records.json",
          "https://phishdestroy.io/steam_dossier/hi/investigation_part2.html#outsourcing-case",
          "https://www.reddit.com/r/ohnePixel/comments/1hahqx2/permanently_banned_steam_account_without_a_clear/",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://www.reddit.com/r/DotA2/comments/r55bd7/many_people_are_losing_item_via_clicking_links/",
          "https://www.reddit.com/r/SteamUncensored/comments/1kjt2fa/steam_bans_without_reason_and_ignores_its/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/network-repositories.csv",
          "https://github.com/alliedmodders/amxmodx",
          "https://github.com/alliedmodders/sourcemod",
          "https://github.com/DoctorMcKay/node-steam-user",
          "https://github.com/Facepunch/Facepunch.Steamworks",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://github.com/odota/core",
          "https://github.com/odota/dotaconstants",
          "https://github.com/odota/web",
          "https://github.com/splewis/get5",
          "https://github.com/SteamDatabase/FileDetectionRuleSets",
          "https://github.com/SteamRE/SteamKit",
          "https://github.com/ValveSoftware/dxvk",
          "https://github.com/ValveSoftware/GameNetworkingSockets",
          "https://github.com/ValveSoftware/gamescope",
          "https://github.com/ValveSoftware/Proton",
          "https://github.com/ValveSoftware/source-sdk-2013",
          "https://github.com/ValveSoftware/wine",
          "https://github.com/ValveSoftware/steam-devices",
          "https://github.com/ValveSoftware/steam-audio",
          "https://github.com/alliedmodders/metamod-source",
          "https://github.com/alliedmodders/sourcepawn",
          "https://github.com/ValveSoftware/Fossilize",
          "https://github.com/rlabrecque/Steamworks.NET",
          "https://github.com/ModDota/moddota.github.io",
          "https://github.com/odota/parser",
          "https://github.com/ValveSoftware/steam-for-linux",
          "https://github.com/SteamRE/DepotDownloader",
          "https://github.com/JustArchiNET/ASF-ui",
          "https://github.com/advancedfx/advancedfx",
          "https://github.com/alliedmodders/ambuild",
          "https://github.com/SteamDatabase/BrowserExtension",
          "https://github.com/odota/mobile",
          "https://github.com/ValvePython/steam",
          "https://github.com/skadistats/clarity",
          "https://github.com/SteamRE/open-steamworks",
          "https://github.com/ValveSoftware/Source-1-Games",
          "https://github.com/alliedmodders/hl2sdk",
          "https://github.com/SteamDatabase/steamdb.info-issues",
          "https://github.com/CSGOFloat/inspect",
          "https://github.com/ValveSoftware/SteamOS",
          "https://github.com/alliedmodders/source2mod",
          "https://github.com/smiley/steamapi",
          "https://github.com/SteamDatabase/GameTracking",
          "https://github.com/ValveSoftware/counter-strike_rules_and_regs",
          "https://github.com/ValveSoftware/openvr",
          "https://github.com/SteamDatabase/easy-markdown-editor",
          "https://github.com/ValveSoftware/Dota-2",
          "https://github.com/ValveSoftware/Dota2-Gameplay",
          "https://github.com/JustArchiNET/ArchiBot",
          "https://github.com/ztizzlegaming/CSGOWinBig",
          "https://github.com/JustArchiNET/mantis.justarchi.net",
          "https://github.com/odota/node-steam-user",
          "https://github.com/ModDota/TypeScriptAddonTemplate",
          "https://github.com/ValvePython/vdf",
          "https://github.com/alliedmodders/amtl",
          "https://github.com/ValvePython/dota2",
          "https://github.com/alliedmodders/stripper-source",
          "https://github.com/Allyans3/steam-market-api-v2",
          "https://github.com/ModDota/dota-tutorial",
          "https://github.com/odota/blog",
          "https://github.com/OpsecGuy/BetterGo",
          "https://github.com/pxvr-official/1",
          "https://github.com/Revadike/InternalSteamWebAPI",
          "https://github.com/JoeSzymkowiczFiveM/qb-lootcrate",
          "https://github.com/AbrarKL/MyRoulette.XYZ",
          "https://github.com/JustArchiNET/ASF-WebConfigGenerator",
          "https://github.com/ModDota/dota-data",
          "https://github.com/ModDota/TypeScriptDeclarations",
          "https://github.com/ModDota/API",
          "https://github.com/alliedmodders/cssdm",
          "https://github.com/SteamDatabase/steamstat.us",
          "https://github.com/c0deina/csgojackpotV2",
          "https://github.com/ValvePython/steamctl",
          "https://github.com/ValvePython/csgo",
          "https://github.com/BeepIsla/csgo-crash-exploit",
          "https://github.com/ValvePython/vpk",
          "https://github.com/alliedmodders/SM-SteamWorks",
          "https://github.com/SteamRE/Steam4NET",
          "https://github.com/alliedmodders/hl2sdk-manifests",
          "https://github.com/JustArchiNET/ASF-PluginTemplate",
          "https://github.com/ModDota/Dota2AIFramework",
          "https://github.com/Shkyyl/KeyChamp",
          "https://github.com/SteamDatabase/SteamMonitor",
          "https://github.com/Baterka/cslore.com",
          "https://github.com/SteamDatabase/SteamTokenDumper",
          "https://github.com/monoblocker/roulette",
          "https://github.com/zsith/launcher.user.js",
          "https://github.com/LincolnIT/CSGODouble-bot-automated",
          "https://github.com/vladpuz/steam-market",
          "https://github.com/mcgrizzz/Cstrike.bet",
          "https://github.com/odota/underlords-web",
          "https://github.com/SteamDatabase/SteamToTwitter",
          "https://github.com/ModDota/AbilityLuaSpellLibrary",
          "https://github.com/alvinl/bitskins",
          "https://github.com/b1naryth1ef/steamy",
          "https://github.com/kratos1812/Case-Opening",
          "https://github.com/odota/docs",
          "https://github.com/SteamDatabase/steam-advanced-access-fetch-players",
          "https://github.com/TheRioMiner/CsgoBetterExternalRaytrace",
          "https://github.com/alliedmodders/hl2sdk-mock",
          "https://github.com/christophersu/PySteamMarket",
          "https://github.com/Extremelyd1/Strat-Roulette",
          "https://github.com/giovanni-orciuolo/double-sdk",
          "https://github.com/JustArchiNET/Madness",
          "https://github.com/ModDota/TypescriptPanoramaDeclarations",
          "https://github.com/odota/rapier",
          "https://github.com/Vozn1akHero/CSGOCaseOpeningSimulator",
          "https://github.com/autarc/steam-store",
          "https://github.com/BETTING-CODE/awesome-esports-sites",
          "https://github.com/jonteohr/Better-Warden",
          "https://github.com/Ludzikk/CSGO-Gambling-Site",
          "https://github.com/ModDota/find-steam-app",
          "https://github.com/mprey/csgocact.us",
          "https://github.com/nezu-cc/ServerCrasher",
          "https://github.com/odota/testfiles",
          "https://github.com/odota/underlordsconstants",
          "https://github.com/SnaBe/node-steam-market-fetcher",
          "https://github.com/SteamDatabase/.github",
          "https://github.com/wolfcon/RIP-HLTV-BET",
          "https://github.com/alliedmodders/blaster.net",
          "https://github.com/catears124/CS2-Price-API",
          "https://github.com/ialakey/caseforge",
          "https://github.com/Ilusion9/csgo-fix-mapchange-crash-sm",
          "https://github.com/ismail0234/Benson-Map-Crash-Fixer",
          "https://github.com/jaxwilko/steam-market-api",
          "https://github.com/JustArchiNET/ArchiTag",
          "https://github.com/ModDota/DotaUI",
          "https://github.com/node-steam/market-pricing",
          "https://github.com/odota/media",
          "https://github.com/SergeyIvanovDevelop/Crypto-Steam-Platform",
          "https://github.com/Aareksio/csgodouble-floatchecker",
          "https://github.com/chinm4/CSGOdrop",
          "https://github.com/Cruze03/CSGO-Case-Opening-Prank",
          "https://github.com/Dhruva-Kapadia/CSGOTrollGG",
          "https://github.com/ErhanCSGO/CSGOPolygon-prediction",
          "https://github.com/Ev-Hoang/Bedrock-Chest-Case-Opening",
          "https://github.com/jmjp/csgo-roulette",
          "https://github.com/JustArchiNET/ArchiCrowdin",
          "https://github.com/LeonSK/WearMarketInspector",
          "https://github.com/maximgeerinck/csgo-gamble",
          "https://github.com/ModDota/BugTracker",
          "https://github.com/plwp/mma-betting",
          "https://github.com/Southsideswag16/Csgo-Gambling-Site",
          "https://github.com/tacyarg/csgofiesta-frontend-react",
          "https://github.com/Velorasse/Mutah-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-csmoney-csgoskins",
          "https://github.com/alliedmodders/am-github-artifact-webhook",
          "https://github.com/charamza/roulette",
          "https://github.com/Cruze03/CSGO-PugSetup-RoundRestore",
          "https://github.com/csgorol/CSGO-ROLL-Crash-Predictor",
          "https://github.com/FoxSerito/FOXWORLD_plugin_DoubleJump_CSGO",
          "https://github.com/hkehayovmoonbiz/CS2-Casino-Full-Source-Code",
          "https://github.com/JustZakary/steamstoreapi",
          "https://github.com/jzimr/steam-market-api",
          "https://github.com/Momohime/CSGO.Network-Jackpot-Coinflip",
          "https://github.com/nnjjswat/moneybot",
          "https://github.com/odota/carry",
          "https://github.com/odota/PublicMatchDataBot",
          "https://github.com/Orillio/CSGOBet.com",
          "https://github.com/ripexz/csgo-bet-alert",
          "https://github.com/rrpvm/lumen_sense-beta-deprecated-",
          "https://github.com/Ruthless222/csgoscore",
          "https://github.com/tfburns/CSGO-cases-PL",
          "https://github.com/TomDra/CSGO-Case-Data-Analysis",
          "https://github.com/ValvePython/dota2-wrappers",
          "https://github.com/ValvePython/teamfortress2-closed-captions",
          "https://github.com/VistaNetGTX/Cstrike.bet-",
          "https://github.com/wafflas/csgo-case-opening-simulator",
          "https://github.com/Admiral-Enigma/Le_Coinflip",
          "https://github.com/adryeljuliao/roulette-csgo",
          "https://github.com/AndreuTheG/csgo-coinflip-web",
          "https://github.com/asmilen/csgoDouble",
          "https://github.com/b1naryth1ef/csgofort",
          "https://github.com/Baterka/PrivateSteamBettingWebsite2024",
          "https://github.com/blackcaer/SteamTradeHandler",
          "https://github.com/BTheCoderr/theRounders",
          "https://github.com/CallumHemsley/KazeBot",
          "https://github.com/chrisjpm/CSGOJackpotTemplate",
          "https://github.com/colinsenner/valve-bug-bounty",
          "https://github.com/coryypeters/nrl-odds-intelligence-pipeline",
          "https://github.com/deissh/dev-csgoduo",
          "https://github.com/dom1torii/even-better-font-manager",
          "https://github.com/DONnicov/CSGO-crash-black-screen-",
          "https://github.com/DoubleBoters/CsgoDouble",
          "https://github.com/downarowiczd/DoubleBot",
          "https://github.com/ErayBahar/steammarketscraper",
          "https://github.com/fairydarkness/SteamwebmailAPI",
          "https://github.com/FAQU2/CSGO-Coinflip-MyJailShop",
          "https://github.com/FlamesONE/csgo-case-opening",
          "https://github.com/FunnyRain/csgorun-crash-watch",
          "https://github.com/geohdgio/Venatus-Autenticator",
          "https://github.com/hakanstarlord/steam-bot",
          "https://github.com/HvH-gg/CSGO-Item-CrashFix",
          "https://github.com/HvH-gg/CSGO-NetMsg-CrashFix",
          "https://github.com/isybycnsmam/SteamLibrary",
          "https://github.com/ItsTangerine/SteamApis.Net",
          "https://github.com/JustArchiNET/JustArchi.net",
          "https://github.com/kiri-osint/CS2-Info-Hub-Bot",
          "https://github.com/Koshkaj/monte",
          "https://github.com/madsab/CaseOpening",
          "https://github.com/man90es/steamcardexchange-api",
          "https://github.com/MattPua/steam-unofficial-docs",
          "https://github.com/Metallist1/Portfolio.CsgoWinGambleProject",
          "https://github.com/mikebobadilla/csgo-jackpot",
          "https://github.com/mikebobadilla/meteor-csgojackpot",
          "https://github.com/ModDota/D2VDump",
          "https://github.com/ModDota/DotaTracking",
          "https://github.com/ModDota/eslint-config",
          "https://github.com/mr-codinglv/Casino-script",
          "https://github.com/MrKeelik/MrKeel",
          "https://github.com/noahlatzel/CSGORollHelper",
          "https://github.com/oddsgpt/oddsgpt-market-intelligence",
          "https://github.com/oEXU/csgo-server-crasher",
          "https://github.com/PrdTTony/CSGO-Roulette",
          "https://github.com/r-adamski/csgo-jackpot",
          "https://github.com/Sahotallo/Turan-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-Skinbaron-hellcase",
          "https://github.com/samuelcsouza/steam-marketplace-api",
          "https://github.com/SKINSTRACK/CS2-Price-API",
          "https://github.com/snmtriet/CSGO-Casino-Full-Source-Code",
          "https://github.com/SteamRE/homebrew-tools",
          "https://github.com/SteamRE/opensteamworks.org",
          "https://github.com/TheQuack45/CsgoCaseOpenProgram",
          "https://github.com/TLClassless/StratRouletteCSGO",
          "https://github.com/tomasoom/csgoCaseOpening",
          "https://github.com/vitaliy-evsyukov/steamgifts-autobet-bookmarklet",
          "https://github.com/XpravdaX/RouletteCSGO",
          "https://github.com/YuiKasumii/steam_api_unofficial",
          "https://github.com/Zexuz/Steam-Betting",
          "https://github.com/ANK-RULZZ/steam-jackpot-site",
          "https://github.com/asmilen/CsgoDoubleVS",
          "https://github.com/CORNOODOSADAS/CSGOWeed",
          "https://github.com/CSGOApple/csgoapple",
          "https://github.com/CSGOFAST/csgofast-api",
          "https://github.com/Donakall/csgoDoublebot",
          "https://github.com/fedor-selivanov/csgo-fast-roulette",
          "https://github.com/foldageros/csgod",
          "https://github.com/gmod-gambling/gmod-gambling",
          "https://github.com/ierome/CSGOBoss-BackEnd",
          "https://github.com/jamienp1/CSGODOUBLE-BOT-AUTO",
          "https://github.com/JEYONER/CSGOTOXIC",
          "https://github.com/kalrish/csgo-jackpot",
          "https://github.com/krys12345/roulettee",
          "https://github.com/LilDuggiMuffi/CSGODouble-Working-Bot",
          "https://github.com/LyricLy/Steam2Proton",
          "https://github.com/M0NsTeR77/csgo-roulette",
          "https://github.com/ozanhalis/Hi",
          "https://github.com/scoobertus/CSGO-DoubleBot",
          "https://github.com/Tradeal/CSGO-Jackpot-Bot",
          "https://github.com/ValvePython/artifact",
          "https://github.com/Vampire/CSGO-Roulette-Bot",
          "https://github.com/vdemans/csgo-roulette",
          "https://github.com/VocoreVideo/CSGODungeon-",
          "https://github.com/wayz-dev/csgofloat",
          "https://phishdestroy.io/steam_dossier/output_steam_network/raw_data.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/enforcement-source-manifest.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/hi/steam_enforcement_evidence.content.json",
      "export_json_sha256": "164c7f54b384160af12a9dc1531b4983d3719a68264f5a4efb7e85e13cff3601"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "hi/steam_evidence_archive.html",
      "language": "hi",
      "title": "स्रोतों की जाँच करें — द Steam डोजियर",
      "source_url": "https://phishdestroy.io/steam_dossier/hi/steam_evidence_archive",
      "source_html_sha256": "5932dba4d5c783458b06c65af8711c915bce99b60174388d8182e9d8b8fe2d1e",
      "exported_at": "2026-09-29T00:22:53.467Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "steam_evidence_archive.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/hi/steam_evidence_archive.pdf?v=print-20260929-v5",
        "sha256": "aee3bd2011cbbc0206f5d575e7a65c8c25726a488dc0caa90b2aac148da2f77e",
        "bytes": 185432,
        "pages": 3
      },
      "integrity": {
        "signed_object": "steam_evidence_archive.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "steam_evidence_archive.content.json.asc",
        "digest_file": "steam_evidence_archive.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify steam_evidence_archive.content.json.asc steam_evidence_archive.content.json",
          "sha256sum -c steam_evidence_archive.content.json.sha256"
        ]
      },
      "content": {
        "text": "जांच सामग्री / स्रोत संग्रह 002\nSteam साक्ष्य संग्रह — 16,319 से प्राप्त अभिलेख\n\nहर दावा। स्रोत पर वापस।\n\nयह अनुभाग क्या प्रमाणित करता है\n\nयह फोरेंसिक आर्काइव 16,319 के प्राथमिक स्रोत रिकॉर्ड्स को क्रिप्टोग्राफिक हैश और उत्पत्ति लॉग्स के साथ अनुक्रमित करता है—Valve डेवलपर कम्युनिटी दस्तावेज़ीकरण, सार्वजनिक GitHub मुद्दे, सत्यापित Trustpilot शिकायतें, और संग्रहीत फोरम रिपोर्ट्स तक फैला हुआ। यह एक निरीक्षण योग्य साक्ष्य आधार प्रदान करता है जो बार-बार होने वाली प्लेटफ़ॉर्म कमजोरियों, दस्तावेज़ित न की गई API अप्रचलितताओं, और हैक किए गए खातों से संबंधित लगातार उपभोक्ता शिकायतों को दर्शाता है।\n\n← कार्यकारी ब्रीफिंग पर वापस\n\nदावे के पीछे का रिकॉर्ड खोजें। स्रोत के अनुसार फ़िल्टर करें, पूरा पाठ खोलें और मूल लिंक पर जाएँ। स्रोत पंक्तियाँ ओवरलैप हो सकती हैं; एक रिकॉर्ड सत्यापित घटना नहीं है।\n\nजांच पर लौटें ↗\n354ट्रस्टपायलट / स्रोत पंक्तियाँ\n208रेडिट / स्रोत पंक्तियाँ\n705गिटहब / स्रोत पंक्तियाँ\n15,302मास्टर सीएसवी / स्रोत पंक्तियाँ\n16,319 रिकॉर्ड्स — प्लेटफ़ॉर्म प्रकार के अनुसार विवरण\n\nविकी श्रेणी उत्पत्ति (7,620 रिकॉर्ड्स · 46.7%): Valve डेवलपर समुदाय (developer.valvesoftware.com), SteamDB दस्तावेज़ीकरण/FAQ, और गेमिंग समुदाय विकी (Liquipedia CS/Dota और Fandom Steam विकी) से स्वचालित WARC स्नैपशॉट्स और MediaWiki API एंडपॉइंट्स के माध्यम से अगस्त 2024 और सितंबर 2026. के बीच पार्स किया गया। सभी 7,620 प्रविष्टियाँ मास्टर CSV निर्यात (कुल_वाल्व_घोटाले_मास्टर_डीबी.सीएसवी).\n\nविकी\n7,620\nरेडिट\n5,635\nGitHub\n2,395\nट्रस्टपायलट\n393\nवेब\n276\n9,116 16,319 रिकॉर्ड्स (55.8%) में Steam / Valve संदर्भ शामिल हैं।\n\nयह खोजने योग्य अभिलेखागार पर बनाया गया था 2026-09-17 उपरोक्त सूचीबद्ध स्रोत निर्यातों से। दस्तावेज़ के अन्य भागों में उपयोग किया गया अलग '40,448-' पंक्ति मास्टर निर्यात का दायरा भिन्न है। देखें बिल्ड मैनिफेस्ट इस अभिलेखागार की गणनाओं के लिए; रिकॉर्ड ओवरलैप हो सकते हैं और ये अद्वितीय घटनाएँ नहीं हैं।\n\nस्रोत मंच\nस्रोत संग्रह\nSteam / Valve उल्लेख करता है\nटेक्स्ट मैच या Valve रिपॉजिटरीलापता / हटाया गया पाठ\n16,569 स्रोत पंक्तियाँ\n16,319 अलग-अलग रिकॉर्ड\n249 डुप्लिकेट पंक्तियाँ मर्ज की गईं\n1 पंक्ति शामिल नहीं\nमूल फ़ाइलें देखें ↘\n★TRUSTPILOT2015-10-16#1RATING 1/5\n\nSteam is the biggest PC gaming platform without a doubt. A power which could be abused but Steam for the most part doesn't. Overall a definite download for any moden digital age PC gamer. It mu... See more\n\nMA · 7 source copies\n★TRUSTPILOT2021-06-18#2RATING 1/5\n\nThey scam people for money, dont believe me? Read this Source: Steam Subscribers/User Agreement NO GUARANTEES TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, NEITHER VALVE NOR ITS AFFILIA... See more\n\nWF · 7 source copies\n★TRUSTPILOT2016-10-28#3RATING 1/5\n\nSupport on site is terrible. Refunds not happend yet, despite games not working. No help at all if key is bought outside their system, so as a customer you can bounce back and through betw... See more\n\nPE · 7 source copies\n★TRUSTPILOT2021-09-27#4RATING 1/5\n\nThey are an amazing company!! My boyfriend paid for and downloaded a game without realizing it wasn’t the version he wanted. When he reached out, they gave him a full refund and responded in the same... See more\n\nVH · 7 source copies\n★TRUSTPILOT2026-07-20#5RATING 1/5\n\nI’ve used Steam for years, but lately, their sales have really lost their edge. I was hoping to score some solid discounts, but many games still feel overpriced, even during sales. Plus, the support response times can be frustratingly slow when issues arise.\n\nCR\n★TRUSTPILOT2025-12-10#6RATING 1/5\n\nI new here , but all my firends had great experience with this platform . They can make money\n\nZeinab Nematollahi\n★TRUSTPILOT2025-11-18#7RATING 1/5TEXT UNAVAILABLE\n\nNo text was included in the source record.\n\nEM\n★TRUSTPILOT2025-10-21#8RATING 1/5\n\nusing steam for over a decade and i have no words how good the platform is. some friends recommended it to me back in 2015 when we wanted to play csgo together and since then im loggin on it on a daily basis to check new games\n\nTrustpilot\n★TRUSTPILOT2025-05-09#9RATING 1/5\n\nSupport are never able to help you and only able to redicrect you to public linkBreaking there own TOSNot able to provider a refundNot able to provide a safe place for gamingBase on the game you play you can get scam.\n\nSym Link · 7 source copies\n★TRUSTPILOT2025-05-09#10RATING 1/5TEXT UNAVAILABLE\n\nNo text was included in the source record.\n\nHearnius\n★TRUSTPILOT2024-12-30#11RATING 1/5\n\nThis company allowed a single phishing scammer 76561199443342045 in 100's of its user community chat rooms \"Steam Chat\" the whole week of Winter Sales, 12-23-2024 - 2025 to spam spaceintrader a scam phishing website.Don't support Valve & Steam that support sca…\n\nFR · 7 source copies\n★TRUSTPILOT2024-11-15#12RATING 1/5\n\nVery realiable! Ive never had an issue over the 11 years ive had steam.\n\nJM\nबिल्ड और इसकी स्रोत फ़ाइलें\n\nयह आर्काइव 249 की डुप्लिकेट पंक्तियों को मर्ज करता है और 16,569 इनपुट्स से एक पंक्ति को बाहर रखता है, जिससे 16,319 विशिष्ट रिकॉर्ड बचते हैं। एक रिकॉर्ड पहले से ही किसी अन्य रिकॉर्ड में शामिल घटना का वर्णन कर सकता है। खोज शीर्षक, लेखक, स्रोत लेबल और प्रदर्शित अंशों को कवर करती है; प्रत्येक रिकॉर्ड के साथ पूरा सहेजा गया पाठ खुलता है।\n\nचार स्रोत निर्यातों को डाउनलोड करें ↓फ़ाइल गिनती और SHA-256 हैश ↗मूल बिल्ड मैनिफेस्ट ↗\n\nइस बंडल में पुनर्प्राप्त निर्यातों को शामिल किया गया है, जो बिल्ड की पंक्ति संख्याओं और इसके तीन दर्ज किए गए JSON पथों से मेल खाते हैं। मूल बिल्ड ने इनपुट हैश या मास्टर CSV पथ दर्ज नहीं किया था; साथी मैनिफेस्ट पुनर्प्राप्त फ़ाइलों और प्रकाशित सूचकांक के साथ तुलना को दस्तावेज़ित करता है।\n\nट्रस्टपायलट · steam_support_reviews.json354 पंक्तियाँ · JSON निर्यात\nरेडिट · reddit_censored_forensics.json208 पंक्तियाँ · JSON निर्यात\nGitHub · वाल्व_अनदेखे_बग्स.जेएसओएन705 पंक्तियाँ · JSON निर्यात; फ़ाइलनाम एक कलेक्टर लेबल है\nमास्टर · TOTAL_VALVE_SCANDALS_MASTER_DB.csv15,302 पंक्तियाँ · तुलना के लिए उपयोग किया जाने वाला CSV निर्यात\nअदालती कार्यसूचियाँ · UNSEALED_EXHIBITS_AND_AML_DOSSIER.mdवुल्फायर बनाम Valve, सीलबंद ईमेल, गेब न्यूएल के बयान, अक्टूबर 2019, एएमएल स्वीकारोक्ति\nमास्टर तथ्य · तथ्य और उद्धरण डेटाबेस.md1,638 35, प्रतिस्पर्धा-विरोधी और सुरक्षा क्षेत्रों में पृथक सत्यापित उद्धरण\nसहायता संग्रह · support_canned_refusals.html1,505 टिकट रिकॉर्ड · 137 · संरक्षित स्क्रीनशॉट · लाइव त्वरित खोज\nरिकॉर्ड फ़ील्ड, अनुपस्थित टेक्स्ट और ओवरलैपिंग एक्सपोर्ट्स\n\nदिनांक, रेटिंग, श्रेणियाँ और इश्यू स्टेट्स स्रोत एक्सपोर्ट्स को पुन: प्रस्तुत करते हैं। एक गायब URL वैसे ही गायब रहता है। \"[removed]\" या \"[deleted]\" मार्कर यह नहीं बताते कि किसी पोस्ट को किसने हटाया या क्यों हटाया।Steam/Valve फ़िल्टर एक टेक्स्ट मैच है, प्रासंगिकता का आकलन नहीं।\n\n\"Export matches\" सूचकांक प्रविष्टियों को सारांश के साथ डाउनलोड करता है; \"Download record\" में पूरा सहेजा गया पाठ शामिल होता है। अलग 40,448-पंक्ति मास्टर सीएसवी और 1,690-पंक्तिGitHub सीएसवी ये व्यापक निर्यातों के बारे में हैं, न कि इस बिल्ड के स्रोत काउंट्स के बारे में।",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam साक्ष्य संग्रह — 16,319 से प्राप्त अभिलेख"
          },
          {
            "level": 2,
            "id": null,
            "text": "स्रोत मंच"
          },
          {
            "level": 2,
            "id": null,
            "text": "बिल्ड और इसकी स्रोत फ़ाइलें"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/hi/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/hi/",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/TOTAL_VALVE_SCANDALS_MASTER_DB.csv",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive_manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive-inputs.zip",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive-inputs-manifest.json",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/unsealed_legal_and_aml/UNSEALED_EXHIBITS_AND_AML_DOSSIER.md",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/forensic_facts_1000/FACTS_AND_CITATIONS_DATABASE.md",
          "https://phishdestroy.io/steam_dossier/hi/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/github_valve_unpatched_bugs.csv"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/hi/steam_evidence_archive.content.json",
      "export_json_sha256": "2865c2d09506ed9b18bc5b809a37b0ed2ab143b0d938a0b940f3aadb260f2419"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "hi/support_canned_refusals.html",
      "language": "hi",
      "title": "Steam समर्थन अस्वीकृतियाँ और तैयार प्रतिक्रियाएँ संग्रह — द Steam डोजियर",
      "source_url": "https://phishdestroy.io/steam_dossier/hi/support_canned_refusals",
      "source_html_sha256": "4fd0fe38334d3bd37438d80f106770dbf0e36d7c28dfb00b05800714cd98d112",
      "exported_at": "2026-09-29T00:22:54.390Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "support_canned_refusals.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/hi/support_canned_refusals.pdf?v=print-20260929-v5",
        "sha256": "6e5d1fe3cacaf8f0ed38ee095829abf3e5108edce19234fdca667cf4b4be6960",
        "bytes": 223678,
        "pages": 2
      },
      "integrity": {
        "signed_object": "support_canned_refusals.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "support_canned_refusals.content.json.asc",
        "digest_file": "support_canned_refusals.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify support_canned_refusals.content.json.asc support_canned_refusals.content.json",
          "sha256sum -c support_canned_refusals.content.json.sha256"
        ]
      },
      "content": {
        "text": "यह अनुभाग क्या प्रमाणित करता है\n\nयह रिपॉजिटरी 137 द्वारा संरक्षित प्राथमिक स्क्रीनशॉट्स और 1,505 द्वारा ऑडिट की गई पीड़ित अपीलों को दस्तावेजीकृत करती है, जो Valve की स्वचालित सपोर्ट टिकट हैंडलिंग का विवरण देती हैं। यह प्रमाणित करती है कि जब OpenID रीडायरेक्शन या अनधिकृत API कुंजी उत्पन्न करने के माध्यम से खाते समझौता किए जाते हैं, तो Steam सपोर्ट तकनीकी जांच के बिना मानकीकृत तैयार इनकारों का व्यवस्थित रूप से उपयोग करता है। वस्तुओं की पुनर्स्थापना या ऑडिट ट्रेल प्रकटीकरण को स्पष्ट रूप से अस्वीकार करके, प्लेटफ़ॉर्म संरचनात्मक प्रमाणीकरण दोषों की पूरी जिम्मेदारी समझौता किए गए खाताधारकों पर डाल देता है।\n\nसभी स्क्रीनशॉट तृतीय-पक्ष द्वारा कैप्चर किए गए हैं और संरक्षित हैं। कॉपीराइट और सामग्री उनके संबंधित लेखकों और प्लेटफ़ॉर्म (Reddit उपयोगकर्ता, Steam समुदाय के लेखक, Trustpilot समीक्षक, X और YouTube पोस्टर) के पास बनी रहती है। इन्हें केवल पहचान और सार्वजनिक हित की रिपोर्टिंग के लिए पुन: प्रस्तुत किया गया है; किसी भी स्वामित्व का दावा नहीं किया जाता। प्रत्येक प्रदर्शनी अपने प्राथमिक स्रोत से जुड़ी हुई है।\n\nFigures reported on the source page\nMeasure\tReported value\tScope\nदस्तावेजी अभिलेख\t1505\tसत्यापित पीड़ित अपीलें और टिकट थ्रेड्स\nसंरक्षित स्क्रीनशॉट\t137\tउच्च-रिज़ॉल्यूशन टिकट स्थानीय रूप से संग्रहीत होते हैं।\nपुनर्स्थापना दर\t0.0%\tAPI- प्रमुख व्यापार अपहरण मामलों में रिवर्सल मंजूर\nटेम्पलेट प्रतिलिपि\t100%\tस्टाफ (इलिया, रोजर, मैवरिक) में वाक्यशः स्क्रिप्ट का पुन: उपयोग\nफॉरेंसिक साक्ष्य: समर्थन अस्वीकृति के तीन मुख्य स्तंभ\nस्तंभ 01 · प्रवेशप्रदर्शनी R-014\nरॉजर एडमिशन: API MitM पुष्टि हुई\n\nटिकट प्रतिक्रिया #1cp582i में, Steam के समर्थन कर्मचारी \"रॉजर\" लिखित रूप में स्वीकार करते हैं कि हमलावर API के माध्यम से वैध ट्रेड रद्द कर देते हैं और मिलीसेकंड में उन्हें क्लोन बॉट्स के साथ बदल देते हैं, लेकिन वे आइटम बहाल करने से इनकार करते हैं और पीड़ित से \"स्थानीय पीसी तकनीशियन\" से संपर्क करने को कहते हैं।\n\nलिखित प्रवेश का निरीक्षण करें ↗\nस्तंभ02· वृद्धिप्रदर्शनी R-012\n7-दिवसीय व्यापार: निष्क्रियता बनाए रखें\n\n7--डे ट्रेड होल्ड विंडो के दौरान एक पीड़ित ने हैकर के खातों का SteamID64 प्रदान किया। सपोर्ट स्टाफ \"आर्टम\" और \"इलिया\" ने वर्चुअल आइटम की कमी का हवाला देते हुए चोरी की गई वस्तुओं को फ्रीज करने से इनकार कर दिया और एक स्वचालित टेम्पलेट के साथ टिकट बंद कर दिया।\n\nमल्टी-स्टाफ ट्रांसक्रिप्ट का निरीक्षण करें ↗\nस्तंभ03·नीतिप्रदर्शनी R-002\nसंपत्ति अधिकारों पर बाजार की कमी\n\nValve की आधिकारिक आइटम पुनर्स्थापना नीति स्पष्ट रूप से कहती है कि आइटम वापस नहीं किए जाते हैं क्योंकि उन्हें पुनर्स्थापित करने से \"कमी कम हो जाएगी और अर्थव्यवस्था बढ़ जाएगी, जिससे सामुदायिक बाज़ार में आइटमों का मूल्य गिर जाएगा\"।\n\nनीति स्क्रीनशॉट का निरीक्षण करें ↗\nऐतिहासिक उत्पत्ति · 22 मार्च 2018 से 2026\nप्रदर्शनी H-003 · 8-वर्ष अनपैच्ड अटैक सतह\nसबसे पहला दर्ज किया गया व्यापार प्रतिस्थापन (22, मार्च 2018)\n\nValve ने Counter-Strike आइटम्स पर अपने विवादास्पद 7-डे ट्रेड कूलडाउन को लागू करने से ठीक एक सप्ताह पहले, ट्रेडिंग समुदाय ने इसके पहले लाइव उदाहरणों की खोज की। Steam वेब API ट्रेड रीडायरेक्शन एक्सप्लॉइटहमलावरों ने वेब सत्रों को हाईजैक करके एक अनधिकृत API कुंजी उत्पन्न की steamcommunity.com/dev/apikey मोबाइल 2और एफए पुष्टि के बिना, जिससे बॉट्स वास्तविक समय में ट्रेड रद्द और स्वैप कर सकते हैं।\n\nमार्च 2018 पीएसए चेतावनी: ठग स्वचालित रूप से इस ट्रेड ऑफर का पता लगा सकते हैं और इसे आपके खाते में अस्वीकार कर देंगे, क्योंकि उनके पास आपका Steam API की है। अब यह स्कैम बॉट आपको उन्हीं स्किन्स के लिए ट्रेड ऑफर भेजेगा... और आपको कोई फर्क महसूस नहीं होगा!\nऐतिहासिक साक्ष्य पथ\n22 मार्च2018: पहला प्रलेखित API स्वैप\n2019: समर्थन \"मैलवेयर\" विचलन को मानकीकृत करता है\n2020: \"सहायता अनुरोध बंद करें\" स्क्रिप्ट को मजबूत किया गया\n2022–2026: BitB और QR फ़िशिंग स्वचालन\nमूल 2018 Reddit थ्रेड खोलें ↗\nPrimary sources\n\n137 gallery cards refer to 78 distinct primary URLs. Images and repeated exhibit captions are omitted from this reading edition.\n\nFull visual archive and original captures",
        "headings": [
          {
            "level": 2,
            "id": null,
            "text": "Figures reported on the source page"
          },
          {
            "level": 2,
            "id": null,
            "text": "फॉरेंसिक साक्ष्य: समर्थन अस्वीकृति के तीन मुख्य स्तंभ"
          },
          {
            "level": 3,
            "id": null,
            "text": "रॉजर एडमिशन: API MitM पुष्टि हुई"
          },
          {
            "level": 3,
            "id": null,
            "text": "7-दिवसीय व्यापार: निष्क्रियता बनाए रखें"
          },
          {
            "level": 3,
            "id": null,
            "text": "संपत्ति अधिकारों पर बाजार की कमी"
          },
          {
            "level": 3,
            "id": null,
            "text": "सबसे पहला दर्ज किया गया व्यापार प्रतिस्थापन (22, मार्च 2018)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Primary sources"
          }
        ],
        "links": [
          "https://www.reddit.com/r/csgo/comments/1cp582i/i_got_api_scammed_what_do_i_do_now/",
          "https://www.reddit.com/r/DotA2/comments/1e5ovy4/my_account_was_hacked_and_steam_support_refuse/",
          "https://www.reddit.com/r/Steam/comments/3b2abd/steam_will_no_longer_restore_scammed_items_item/",
          "https://www.reddit.com/r/GlobalOffensiveTrade/comments/863tk1/psa_urgent_huge_scam_happening_read_here_how_to",
          "https://phishdestroy.io/steam_dossier/hi/support_canned_refusals#gallery-grid"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/hi/support_canned_refusals.content.json",
      "export_json_sha256": "70c17da54997643f2ce0b88f10488f57723c5483c4db9e626eb977ac5857f6a2"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "hi/valve_scandals_registry.html",
      "language": "hi",
      "title": "Valve घोटाला रजिस्ट्री — द Steamका दस्तावेज़",
      "source_url": "https://phishdestroy.io/steam_dossier/hi/valve_scandals_registry",
      "source_html_sha256": "8c0972bc493e1526c22e577650cfc2c2c94481343d4025164b82e9a8b0fe8e76",
      "exported_at": "2026-09-29T00:22:54.378Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "valve_scandals_registry.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/hi/valve_scandals_registry.pdf?v=print-20260929-v5",
        "sha256": "34005d6a6f7f619df04b9156ff4ab40e10cc5efd8308ad541fbff659cfb034c4",
        "bytes": 163801,
        "pages": 6
      },
      "integrity": {
        "signed_object": "valve_scandals_registry.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "valve_scandals_registry.content.json.asc",
        "digest_file": "valve_scandals_registry.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify valve_scandals_registry.content.json.asc valve_scandals_registry.content.json",
          "sha256sum -c valve_scandals_registry.content.json.sha256"
        ]
      },
      "content": {
        "text": "स्कैंडल संग्रह मास्टर\nValve घोटालों की मास्टर रजिस्ट्री — 160 स्रोत घटनाएँ\nस्रोत रिकॉर्ड्स (कच्चे): 11,768\n\nरिपोर्ट किया गया। स्रोत किया गया। अभी भी खुला है।\n\nयह अनुभाग क्या प्रमाणित करता है\n\n160 यह मास्टर रजिस्ट्री स्वतंत्र रूप से सत्यापित प्राथमिक अभिलेखों को संकलित करती है, जिनमें म Valve के पारिस्थितिकी तंत्र में लगातार मौजूद प्लेटफ़ॉर्म दोष, हटाई गई सामुदायिक रिपोर्टें और अनसुलझी उपभोक्ता सहायता विफलताएँ शामिल हैं। सत्यापित Trustpilot विवाद फाइलिंग्स, संग्रहीत GitHub सुरक्षा समस्या टिकटों और नियामक कार्यवाहियों को समेटे हुए, यह खाता पुनर्प्राप्ति और ग्राहक विवाद समाधान में बार-बार होने वाली प्रणालीगत खामियों को स्थापित करती है।\n\n← कार्यकारी ब्रीफिंग पर वापस\n\n160 एकत्रित रिकॉर्ड: उपयोगकर्ताओं द्वारा रेट किया गया एक सपोर्ट ऑपरेशन, दिखाई देना बंद हो गए थ्रेड्स, दर्ज और छोड़ दिए गए प्लेटफ़ॉर्म के दोष, और वे घटनाएँ जिनके लिए Valve को पहले ही जवाब देना पड़ा है। यहाँ कुछ भी हमारी व्याख्या नहीं है — हर पंक्ति का अपना मूल स्रोत है। किसी एक को खोलें और स्वयं पढ़ें।\n\nस्रोत अभिलेख\n11,768\nसभी श्रेणियों में\nप्लेटफ़ॉर्म की खामियाँ\n3,372\nसमुदाय द्वारा रिपोर्ट किए गए प्लेटफ़ॉर्म के दोष\nसेंसर किए गए थ्रेड्स\n109\nमॉडरेटर द्वारा हटाई गई रेडिट पोस्ट्स\nशिकायतों का समर्थन\n471\nसत्यापित ट्रस्टपायलट शिकायतें\nप्रवर्तन की व्यवहार्यता\nऑथ-होस्ट डोमेन ब्लॉकिंग\n\nOpenID प्रमाणीकरण होस्ट्स को डोमेन-स्तर पर ब्लॉक करना तकनीकी रूप से सरल है: एक बार किसी संसाधन को Steam लॉगिन रीडायरेक्शन से प्रतिबंधित कर दिया जाए, तो उसी संसाधन के लिए प्रमाणीकरण प्रॉक्सी के रूप में कार्य करने वाले तृतीय-पक्ष डोमेन भी उसी नियम-समूह द्वारा फ़िल्टर किए जा सकते हैं। कार्यान्वयन की व्यवहार्यता पर एक विस्तृत चर्चा मुख्य दस्तावेज़ में दी गई है।\n\nडॉसियर में प्रवर्तन की व्यवहार्यता देखें →\nश्रेणी: ट्रस्टपायलट सहायता शिकायतें (छानबीन किए गए नकारात्मक एस्केलेशन)176 मिलते-जुलते स्रोत रिकॉर्ड · डुप्लिकेट संकुचित\nConsumer Complaint2026-07-20\nAuthor: C***\n\nI’ve used Steam for years, but lately, their sales have really lost their edge. I was hoping to score some solid discounts, but many games still feel overpriced, even during sales. Plus, the support response times can be frustratingly slow when issues arise.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2026-07-20\nConsumer Complaint2025-05-09\nAuthor: S*** L***\n\nSupport are never able to help you and only able to redicrect you to public linkBreaking there own TOSNot able to provider a refundNot able to provide a safe place for gamingBase on the game you play you can get scam.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2025-05-09\nConsumer Complaint2024-12-30\nAuthor: F***\n\nThis company allowed a single phishing scammer 7656…2045 in 100's of its user community chat rooms \"Steam Chat\" the whole week of Winter Sales, 12-23-2024 - 2025 to spam spaceintrader a scam phishing website.Don't support Valve & Steam that support scams. Don't give your log in credentials to account hijacking scammers. This company also allows engagements of commercial advertising / spam for gambling in violation of its own Rules and Guidelines / Online Conduct. 7656…5023 proof - groups/deskinsfans key drop advertising, thanks TannerfromKD and Valve!*\"The Consumer Review Fairness Act (CRFA) protects people’s ability to share their honest opinions about a business’s products, services, or conduct, in any forum, including social media. The law protects a broad variety of honest consumer assessments, including online reviews, social media posts, uploaded photos, videos, etc. And it doesn’t just cover product reviews. It also applies to consumer evaluations of a company\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2024-12-30\nConsumer Complaint2024-07-31\nAuthor: A***\n\nhorrible company.randomly you get \"This account may have been accessed by someone else.\"this happened to me 3 times.the 3rd time they wanted a cd key.a spent useless cd key that nobody has any reason to keep laying around.i gave them the paypal bill for my first purchase back in 2015.i gave them a bill for my first phone number ever on the account.i still got the same email attached to the account.this company is literally a scam. nothing but a scam.they randomly claim you been accessed somewhere else and then require you to give them information no reasonable person would ever have, if not your done and have to rebuy everything.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2024-07-31\nConsumer Complaint2023-12-09\nAuthor: K***\n\nHad 288 euros in steam wallet, someone hacked my account even with two step verification, write a steam support for help but only answer was if something is spent in community market they can’t help.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2023-12-09\nConsumer Complaint2023-09-26\nAuthor: J***\n\nI was banned for saying \"Who let grandma on the PC\"and another for simply calling someone ignorant.Power tripping mods, devs who don't care, steam doesn't care. Yet allows racism/trolling/etc Fk steam, its a joke now.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2023-09-26\nConsumer Complaint2022-08-31\nAuthor: Anonymous\n\nSteam community is plain bad for a various reasons:1. Steam forums are a big mess, for example they allow users to post in any language and as result you get jumbled mess with posts in foreign languages together with English language posts. For example, If you check CS GO forums, you'll see half of posts are in Russian and half in English. I don't understand why such a big and international company would leave their forums so unorganized like that. All other normal companies have English only language allowed which is an international language and sometimes subforums for other languages like German, French and etc... so if French people want to post in French they go specifically in that sub-forum. But no, Steam doesn't care about this. Their forums is a one big mess.2. Moderation is biased and joke. I don't understand why such a big company like Steam can't afford to hire people for moderation and pay them. Instead they just recruit random people for moderation who do it for free and\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2022-08-31\nConsumer Complaint2022-05-28\nAuthor: J***\n\nThe login code never arrives. I hate Steam.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2022-05-28\nConsumer Complaint2021-11-08\nAuthor: N***\n\nThe service is terrible, I only signed up because I really like the game I wanted, but the rest is terrible, I hope to get something better soon.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-11-08\nConsumer Complaint2021-06-18\nAuthor: W***\n\nThey scam people for money, dont believe me? Read thisSource: Steam Subscribers/User Agreement NO GUARANTEESTO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, NEITHER VALVE NOR ITS AFFILIATES GUARANTEE CONTINUOUS, ERROR-FREE, VIRUS-FREE OR SECURE OPERATION AND ACCESS TO STEAM, THE CONTENT AND SERVICES, YOUR ACCOUNT AND/OR YOUR SUBSCRIPTION(S) OR ANY INFORMATION AVAILABLE IN CONNECTION THEREWITH.In short: You got a virus or your data leaked because of our software? Whoopsies we dont care, that isnt even legal or the last of their scammy stuff...\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-06-18\nConsumer Complaint2021-05-14\nAuthor: B***\n\nThe support is one of the worst I've ever seen.Useless support team.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-05-14\nConsumer Complaint2020-04-02\nAuthor: J***\n\nSteamcommunity has 15% fees, 15!!!!\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2020-04-02\nConsumer Complaint2020-03-27\nAuthor: H***\n\nWhat can I say? the support is one of the worst I've ever seen maybe the FUNCOM is much worse. If you tell the true on the steam forum you just got a BAN even if what you said did not violated the rules of the forum.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2020-03-27\nConsumer Complaint2018-03-16\nAuthor: B***\n\ndon't sign up will stick on your computer will kill your pc power you can't remove it from your pc even you deleted it will stay woking in the system\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2018-03-16\nConsumer Complaint2016-12-27\nAuthor: J***\n\nIn bloddy hate their page it's tiresome, it's in no way intuitive. I tried reaching out for support, but that is a maze.I'm simply trying to log in and redeem a key of a product I already bought, their search function is a joke. I f*u*c*k*i*n*g hate them. The layout is not like the how to video from the dealer, this can be done much simpler. I don't frigin care aboutn what other titles you have in store or what genre, I just want to redeem my key and install.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-12-27\nConsumer Complaint2016-10-28\nAuthor: P***\n\nSupport on site is terrible.Refunds not happend yet, despite games not working.No help at all if key is bought outside their system, so as a customer you can bounce back and through between bad support systems?? I wait for some other companies to compete in this market, for this can't be the best we as customers can expect.And do put an email up to find, instead of this stuppid website where you spend so long time trying to find a solution on, instead of a simple mail. Often the problem is not there, or if it's there just saying no help here???I need a response\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-10-28\nConsumer Complaint2016-06-26\nAuthor: V*** W***\n\nUseless support as always!\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-06-26\nConsumer Complaint2014-07-01\nAuthor: J***\n\nexpensive, and support team not willing to cooperate\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2014-07-01\nConsumer Complaint2014-04-15\nAuthor: B***\n\nWhen you pay for a program, you expect it too work. cant not buy or anything and have written to valve. but there is not a being done a damn thing abut it..\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2014-04-15\nConsumer Complaint2026-09-03\nAuthor: M***\n\nWorst platform ever wont give me a refund even though a game is unplayable because of bugs I won't ever be using the crap platform again I hope the platform breaks down for good piece fo crao\n\nTarget Domain: steamcommunity.com / steampowered.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2026-09-03\n\nकोई मेल खाने वाले रिकॉर्ड नहीं मिले\n\nअपनी सक्रिय क्वेरी समायोजित करने का प्रयास करें या किसी अन्य श्रेणी टैब की जाँच करें।\n\n1 / 9",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Valve घोटालों की मास्टर रजिस्ट्री — 160 स्रोत घटनाएँ"
          },
          {
            "level": 2,
            "id": null,
            "text": "ऑथ-होस्ट डोमेन ब्लॉकिंग"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: C***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: S*** L***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: F***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: A***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: K***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: Anonymous"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: N***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: W***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: H***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: P***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: V*** W***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: M***"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/hi/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/hi/#autoban-feasibility-section",
          "https://www.trustpilot.com/review/steamcommunity.com"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/hi/valve_scandals_registry.content.json",
      "export_json_sha256": "e2b62b2b7a7fa468ca4197d1ea0da303934fef5b073db0effb82b1a6f5481feb"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "hi/output_steam_network/index.html",
      "language": "hi",
      "title": "Steam वास्तुकला, शोषण नहीं: स्वचालन नेटवर्क — द एक्सप्लॉइटेशन-एंड-एस्केप डॉसियर",
      "source_url": "https://phishdestroy.io/steam_dossier/hi/output_steam_network/index",
      "source_html_sha256": "772ad9936da9eb4de68fdcb2a2beee8fd57e7e0b57d9bfe140afd54117586501",
      "exported_at": "2026-09-29T00:22:54.730Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__index.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/hi/output_steam_network__index.pdf?v=print-20260929-v5",
        "sha256": "05381fbc9cf1bcf6a08d538fd7a54b59b3f0000b90f03788f884a17e2b70571d",
        "bytes": 295201,
        "pages": 2
      },
      "integrity": {
        "signed_object": "output_steam_network__index.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__index.content.json.asc",
        "digest_file": "output_steam_network__index.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__index.content.json.asc output_steam_network__index.content.json",
          "sha256sum -c output_steam_network__index.content.json.sha256"
        ]
      },
      "content": {
        "text": "प्रदर्शनी VII · तकनीकी वास्तुकला विश्लेषण\nSteam नेटवर्क वास्तुकला — प्रोटोकॉल निष्ठा एवं पारिस्थितिकी तंत्र विश्लेषण\n\nस्वचालन ईValve की वास्तुकला है। कोई शोषण नहीं।\n\nयह अनुभाग क्या प्रमाणित करता है\n\nयह मॉड्यूल 252 डेवलपर रिपॉजिटरीज़, 3,320 GitHub प्रोफाइल्स, और 4,214 योगदानकर्ता जोड़ों की तकनीकी टोपोलॉजी को मैप करता है, जो Steam ऑटोमेशन इकोसिस्टम का आधार हैं। यह साबित करता है कि थर्ड-पार्टी ऑटोमेशन Valve के आधिकारिक कनेक्शन मैनेजर प्रोटोकॉल, प्रोटोबफ स्कीमा, और वेब एपीआई पर निर्भर करता है, बिना किसी एक्सप्लॉइट कोड के। एल्गोरिद्मिक Steam गार्ड पुष्टि टोकन इंजीनियर करके और 66.7%, तक न्यूनतम लेनदेन शुल्क एकत्र करके, Valve स्वचालित इकोसिस्टम संचालन का जानबूझकर वास्तुकार और प्राथमिक व्यावसायिक लाभार्थी के रूप में कार्य करता है।\n\n← कार्यकारी ब्रीफिंग पर वापस\n\nजब Valve नियामकों, भुगतान प्रोसेसरों या घोटाले के शिकारों से बात करता है, तो यह त्वचा चोरी और बाजार हेरफेर को \"अनधिकृत तृतीय-पक्ष शोषण\" और \"दुष्ट अवैध स्वचालन\" का परिणाम बताता है। इस 252-रिपॉजिटरी नेटवर्क की इंजीनियरिंग वास्तविकता इसके ठीक विपरीत स्थापित करती है: प्रत्येक ऑटोमेशन फ्रेमवर्क, ट्रेडिंग बॉट, और फार्मिंग बेड़ा, Valve कॉर्पोरेशन द्वारा इंजीनियर, प्रलेखित, और मुद्रीकृत आधिकारिक प्रोटोकॉल परिभाषाओं, वेब एपीआई, और प्रमाणीकरण तंत्र के भीतर सख्ती से संचालित होता है।\n\nन्यायिक निष्कर्ष: सचेत वास्तुकला बनाम अवैध उल्लंघन\n\nइस मॉड्यूल में विश्लेषित सॉफ़्टवेयर — सहित SteamKit, node-steam-user, ValvePython/steam, और ArchiSteamFarm — में शामिल है सॉफ़्टवेयर में शून्य कमजोरियाँ, मेमोरी में शून्य भ्रष्टता, और शून्य ज़ीरो-डे शोषण. ये Valve के स्वामित्व वाले कनेक्शन मैनेजर (सीएम) क्लाइंट प्रोटोकॉल, गूगल प्रोटोकॉल बफ़र्स (प्रोटोबफ़्स) और वेब एपीआईज़ के स्वच्छ, मजबूत ओपन-सोर्स कार्यान्वयन हैं। Valve ने इन एपीआईज़ को प्रोग्रामैटिक लॉगिन स्वीकार करने के लिए डिज़ाइन किया था, और एल्गोरिद्मिक पुष्टि टोकन की अनुमति देने के लिए Steam गार्ड को डिज़ाइन किया था (identity_secret), और एक विज्ञापित 15% शुल्क वसूलता है जो बढ़कर Valve के पक्ष में 66.7% तक उच्च-गति वाले कार्ड और कमोडिटी ड्रॉप्स जिन्हें स्वचालित बॉटनेट्स तरल करते हैं।\n\nस्तंभ01· प्रोटोकॉल निष्ठा\nआधिकारिक प्रोटोबफ़ स्कीमा\n\nऑटोमेशन लाइब्रेरीज़ सुरक्षा गेट्स को बायपास नहीं करतीं। वे आधिकारिक Protobuf संदेशों को सीरियलाइज़ करती हैं (steammessages_clientserver.proto) TCP/WebSockets के माध्यम से सीधे Valve के आधिकारिक CM क्लस्टरों को, ठीक वैसे ही जैसे Steam क्लाइंट करता है।\n\nस्तंभ 02· एल्गोरिद्मिक 2FA\nकार्यक्रमगत व्यापार प्राधिकरण\n\nपूरा कई अरब डॉलर का स्किन ट्रेडिंग का अर्थव्यवस्था Valve पर निर्भर करता है। IEconService API और मोबाइल ऑथेंटिकेटर TOTP कुंजियाँ।Valve ने जानबूझकर Steam गार्ड को मशीन-टू-मशीन व्यापार पुष्टि सक्षम करने के लिए डिज़ाइन किया।\n\nस्तंभ03· वाणिज्यिक लाभार्थी\nमनीकरण किया गया मशीन ट्रैफ़िक: 66.7% तक शुल्क फ़्लोर\n\nValve 15% शुल्क का विज्ञापन करता है, लेकिन उच्च-मात्रा वाली वस्तुओं पर स्वचालित बॉट्स ट्रेड करते हैं — ट्रेडिंग कार्ड, केस, और $0.03 से $0.05 तक की सस्ती ड्रॉप्स — Valve का दो-सेंट न्यूनतम शुल्क फर्श ($0.01Steam + $0.01 प्रकाशक) वसूलता है। 50% 66.7% के पक्ष में Valve के लिए (2¢ एक 3¢ कार्ड से निकाले गए, जिससे विक्रेता के पास 1¢ बच गए)। साथ ही प्रति खाते $5.00 ($26.8M केवल स्कैन किए गए बेड़े पर)।\n\nमॉड्यूल 01 · रिपॉजिटरी और प्रोटोकॉल साक्ष्य\nसार्वजनिक डेवलपर और रिपॉजिटरी अवसंरचना\n\n252 के ओपन-सोर्स रिपॉजिटरीज़ की विस्तृत फोरेंसिक सूची जो Steam ऑटोमेशन को शक्ति प्रदान करती है। यह दर्शाता है कि मानक सॉफ़्टवेयर इंजीनियरिंग टूल्स बिना किसी शोषण के Valve द्वारा प्रकाशित API एंडपॉइंट्स को कैसे लागू करते हैं।\n\n252भंडार\n4,554भूमिका लिंक\nभंडार साक्ष्य का निरीक्षण करें →मॉड्यूल02 · पारिस्थितिकी तंत्र जनसांख्यिकी\nवैश्विक इंजीनियरिंग पारिस्थितिकी तंत्र मापदंड\n\n3,320 सॉफ़्टवेयर इंजीनियरों का भौगोलिक और संस्थागत विवरण, जो Steam स्वचालन पारिस्थितिकी तंत्र में योगदान दे रहे हैं, जिसमें प्रमुख प्रौद्योगिकी नियोक्ताओं के साथ कॉर्पोरेट संबद्धताएँ शामिल हैं।\n\n3,320अभियंता\n98,902कनेक्शन जोड़े\nइकोसिस्टम मेट्रिक्स का निरीक्षण करें →मॉड्यूल03 · इंटरैक्टिव विज़ुअल ग्राफ़\nइंटरैक्टिव प्रोटोकॉल और डेवलपर नेटवर्क ग्राफ़\n\nVis.js के व्यापक इंटरैक्टिव नेटवर्क ग्राफ़ में रिपॉजिटरी, प्रोटोकॉल लाइब्रेरी (SteamKit, Steamworks, ASF) और विभिन्न परियोजनाओं में योगदानकर्ताओं के ओवरलैप को मैप किया गया है। यह दृश्य रूप में दिखाता है कि Steam के ऑटोमेशन इकोसिस्टम को शक्ति प्रदान करने वाली वैध, परस्पर जुड़ी खुले स्रोत सॉफ़्टवेयर आर्किटेक्चर है।\n\nपरस्पर क्रियाशीलVis.js इंजन\nक्लस्टर पृथक्करणलाइव सर्च\nशून्य शोषणमानक एपीआई\nइंटरैक्टिव नेटवर्क ग्राफ़ लॉन्च करें →\nनियामक एवं कानूनी संदर्भ (GDPR, अनुच्छेद 25 एवं उपभोक्ता संरक्षण):\nडिज़ाइन और डिफ़ॉल्ट द्वारा डेटा संरक्षण के सिद्धांत के तहत, एक ऐसा प्लेटफ़ॉर्म आर्किटेक्चर जो चुपचाप API-कुंजी निर्माण, बिना सूचना के व्यापार रद्दीकरण, और मशीन-स्वचालित संपत्ति परिसमापन की अनुमति देता है, प्लेटफ़ॉर्म ऑपरेटर की एक वास्तुशिल्प पसंद है। जब Valve व्यवस्थित रूप से उपभोक्ता प्रतिपूर्ति दावों को यह दावा करके खारिज कर देता है कि नुकसान \"बाहरी साइबर हमलों\" के कारण हुए, तो यह छिपाता है कि हमला मार्ग Valve की अपनी जानबूझकर डिज़ाइन की गई वेब API वास्तुकला है।\n\nइंटरैक्टिव दृश्य\n\n252-रिपॉजिटरी का पूर्ण इंटरैक्टिव विज़ुअलाइज़ेशन, 3,320-डेवलपर नेटवर्क ग्राफ़ यहाँ उपलब्ध है: network.htmlसमग्र मेट्रिक्स हैं पर बीआई मेट्रिक्स पृष्ठ।\n\nSteamडॉसियर · तकनीकी वास्तुकला अभिलेखागार · सार्वजनिक स्रोत अभिलेख · सभी अधिकार मानवता को समर्पित।",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam नेटवर्क वास्तुकला — प्रोटोकॉल निष्ठा एवं पारिस्थितिकी तंत्र विश्लेषण"
          },
          {
            "level": 3,
            "id": null,
            "text": "आधिकारिक प्रोटोबफ़ स्कीमा"
          },
          {
            "level": 3,
            "id": null,
            "text": "कार्यक्रमगत व्यापार प्राधिकरण"
          },
          {
            "level": 3,
            "id": null,
            "text": "मनीकरण किया गया मशीन ट्रैफ़िक: 66.7% तक शुल्क फ़्लोर"
          },
          {
            "level": 2,
            "id": null,
            "text": "सार्वजनिक डेवलपर और रिपॉजिटरी अवसंरचना"
          },
          {
            "level": 2,
            "id": null,
            "text": "वैश्विक इंजीनियरिंग पारिस्थितिकी तंत्र मापदंड"
          },
          {
            "level": 2,
            "id": null,
            "text": "इंटरैक्टिव प्रोटोकॉल और डेवलपर नेटवर्क ग्राफ़"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/hi/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/hi/output_steam_network/valve_ru_farming_isolated.html",
          "https://phishdestroy.io/steam_dossier/hi/output_steam_network/steam_ecosystem_dashboard.html",
          "https://phishdestroy.io/steam_dossier/hi/output_steam_network/network.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/hi/output_steam_network__index.content.json",
      "export_json_sha256": "846821d007e151ea06463937aecb53d856a3b7b57b2b7389bbde4982bd42cccb"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "hi/output_steam_network/network.html",
      "language": "hi",
      "title": "Steam डेवलपर और रिपॉजिटरी एक्सप्लोरर — द ईमेल डेवलपर गाइड",
      "source_url": "https://phishdestroy.io/steam_dossier/hi/output_steam_network/network",
      "source_html_sha256": "36d0cda243f7ec55925a99144e6eea2e99019e220e27820206379859d0d8d035",
      "exported_at": "2026-09-29T00:22:56.296Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__network.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/hi/output_steam_network__network.pdf?v=print-20260929-v5",
        "sha256": "8d10d1e9b949426af0228cc8ddc7e16b9906d013e82541cf68e3e1ef6b4051ec",
        "bytes": 86077,
        "pages": 1
      },
      "integrity": {
        "signed_object": "output_steam_network__network.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__network.content.json.asc",
        "digest_file": "output_steam_network__network.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__network.content.json.asc output_steam_network__network.content.json",
          "sha256sum -c output_steam_network__network.content.json.sha256"
        ]
      },
      "content": {
        "text": "डेवलपर और रिपॉजिटरी एक्सप्लोरर\n\nनोड खोजें। रिकॉर्ड किए गए संबंध की जाँच करें।\n\nसार्वजनिक अभिलेख / संकलित संबंध\nलाइव सर्च\nपरतों को फ़िल्टर करें\nकुल डेवलपर्स3,320\nकुल पुनर्भुगतान252\nप्रदर्शित ग्राफ़ / संग्रह उपसमूह468 नोड्स • 1103जेजेस\nचयनित प्रोफ़ाइल रिकॉर्ड\n\n💡 ग्राफ़ पर किसी भी नोड पर क्लिक करें या Search में टाइप करें, ताकि उसके एकत्र किए गए कनेक्शन और स्रोत पथों की जाँच की जा सके।",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "डेवलपर और रिपॉजिटरी एक्सप्लोरर"
          }
        ],
        "links": []
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/hi/output_steam_network__network.content.json",
      "export_json_sha256": "959f63c411fe4a4a3ec880fccbfb5073b2b6b5821e4e7b586ee0a67a5c335ad0"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "hi/output_steam_network/steam_ecosystem_dashboard.html",
      "language": "hi",
      "title": "संख्याओं में संकलित नेटवर्क — द Steam डोजियर",
      "source_url": "https://phishdestroy.io/steam_dossier/hi/output_steam_network/steam_ecosystem_dashboard",
      "source_html_sha256": "f565a53bcced9559ff76d8f6c543e8a66af1ff66db8ad3b2420cc3a51b59cc3c",
      "exported_at": "2026-09-29T00:22:56.209Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__steam_ecosystem_dashboard.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/hi/output_steam_network__steam_ecosystem_dashboard.pdf?v=print-20260929-v5",
        "sha256": "41171ecf7790d07063c484fbb29eed6170661b2510cc85632cf703ccfff21667",
        "bytes": 153820,
        "pages": 1
      },
      "integrity": {
        "signed_object": "output_steam_network__steam_ecosystem_dashboard.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__steam_ecosystem_dashboard.content.json.asc",
        "digest_file": "output_steam_network__steam_ecosystem_dashboard.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__steam_ecosystem_dashboard.content.json.asc output_steam_network__steam_ecosystem_dashboard.content.json",
          "sha256sum -c output_steam_network__steam_ecosystem_dashboard.content.json.sha256"
        ]
      },
      "content": {
        "text": "सांख्यिकी अवलोकन // फ़ाइल 02\nSteam इकोसिस्टम डैशबोर्ड — नेटवर्क के आँकड़े\n\nनेटवर्क, आंकड़ों में।\n\nयह अनुभाग क्या प्रमाणित करता है\n\nयह डैशबोर्ड 3,320 डेवलपर्स और 252 रिपॉजिटरीज़ में संरचनात्मक खुफिया जानकारी एकत्रित करता है, 68 जुआ-विशिष्ट कोडबेस और क्रॉस-प्लेटफ़ॉर्म कनेक्शन ब्रिजों की पहचान करता है। अनुभवजन्य डेटा भौगोलिक क्लस्टरिंग और डेवलपर ओवरलैप्स को उजागर करता है, जो दर्शाता है कि तीसरे पक्ष की स्किन जुआ अवसंरचना एक संगठित, अत्यधिक परस्पर जुड़ी सॉफ़्टवेयर उद्योग के रूप में Steam के प्लेटफ़ॉर्म के साथ एकीकृत होकर संचालित होती है।\n\n← कार्यकारी ब्रीफिंग पर वापस\n\nजांच डेटाबेस के समेकित आँकड़े: भौगोलिक वितरण, शीर्ष कंपनियाँ, स्किन्स जुआ भंडार, और सक्रिय कनेक्शन ब्रिज।\n\nस्कैन किए गए डेवलपर्स3320\nकुल पुनर्भुगतान252\nजुआ प्रतिबद्धताएँ68\nकुल कनेक्शन1,426\nस्वचालन की संरचना और क्षेत्र\nक्षेत्र I — Valve निगम कोर\n\nआधिकारिक रिपॉजिटरी और सिस्टम सॉफ़्टवेयर। Valve के कर्मचारियों नेफ्यरिन और जो लुडविग के लिए पुष्टि किया गया विकास क्षेत्र।\n\nसेक्टर II — प्राधिकरण इंजन और प्रोटोकॉल एमुलेटर (स्टीमकिट)\n\nValve के Nephyrin और skins gambling डेवलपर DoctorMcKay द्वारा सह-लेखित रिवर्स-इंजीनियर्ड नेटवर्क लाइब्रेरीज़।\n\nसेक्टर III — कार्ड फार्मिंग क्लाइंट्स (ArchiSteamFarm)\n\nट्रेडिंग कार्ड इकट्ठा करने के लिए पृष्ठभूमि में लाखों नकली क्लाइंट्स (आइडलिंग) चलाने हेतु SteamKit प्रोटोकॉल एमुलेटरों का उपयोग करें।\n\nडेवलपर भूगोल\nजर्मनी57\nसंयुक्त राज्य अमेरिका52\nकनाडा48\nयूनाइटेड किंगडम44\nपोलैंड30\nफ्रांस28\nरूसी संघ27\nचीन27\nयूएसए (वाशिंगटन राज्य)23\nऑस्ट्रेलिया19",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam इकोसिस्टम डैशबोर्ड — नेटवर्क के आँकड़े"
          },
          {
            "level": 3,
            "id": null,
            "text": "क्षेत्र I — Valve निगम कोर"
          },
          {
            "level": 3,
            "id": null,
            "text": "सेक्टर II — प्राधिकरण इंजन और प्रोटोकॉल एमुलेटर (स्टीमकिट)"
          },
          {
            "level": 3,
            "id": null,
            "text": "सेक्टर III — कार्ड फार्मिंग क्लाइंट्स (ArchiSteamFarm)"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/hi/#briefing-heading"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/hi/output_steam_network__steam_ecosystem_dashboard.content.json",
      "export_json_sha256": "63efbe4ecbb7b4668a30aed5d7b8272e5d75a76397e8a82b340ae38cb40c5062"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "hi/output_steam_network/valve_ru_farming_isolated.html",
      "language": "hi",
      "title": "कोड, योगदानकर्ता और फोर्क — द Steam डोजियर",
      "source_url": "https://phishdestroy.io/steam_dossier/hi/output_steam_network/valve_ru_farming_isolated",
      "source_html_sha256": "10f11c9c887250c9bc3178d10368c8787d5703a9f88982ea97fad23531a6d6ea",
      "exported_at": "2026-09-29T00:22:56.593Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__valve_ru_farming_isolated.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/hi/output_steam_network__valve_ru_farming_isolated.pdf?v=print-20260929-v5",
        "sha256": "a659175446ced5ffb820528cf8ce889c775849b81cc78085f8403c938b5fe626",
        "bytes": 163958,
        "pages": 2
      },
      "integrity": {
        "signed_object": "output_steam_network__valve_ru_farming_isolated.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__valve_ru_farming_isolated.content.json.asc",
        "digest_file": "output_steam_network__valve_ru_farming_isolated.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__valve_ru_farming_isolated.content.json.asc output_steam_network__valve_ru_farming_isolated.content.json",
          "sha256sum -c output_steam_network__valve_ru_farming_isolated.content.json.sha256"
        ]
      },
      "content": {
        "text": "भाग II / प्रलेखित संबंध का अनुसरण करें\n\nफोर्क्स, योगदान और सॉफ़्टवेयर निर्भरताएँ अलग-अलग प्रमाण हैं। यह दृष्टिकोण एकत्रित भूमिकाओं को संरक्षित रखता है; रोजगार, सुरक्षा बाईपास और आपराधिक संलिप्तता के लिए अतिरिक्त स्रोतों की आवश्यकता होती है।\n\nइंटरैक्टिव क्षमता मानचित्र खोलें ↗\nसार्वजनिक स्रोत / भूमिका लेखा परीक्षा\nकोड। योगदानकर्ता। फोर्क।\n1. नेफेरिन: शाखाएँ और योगदान\n\nप्रदान की गई स्नैपशॉट में नेफेरिन को ValveSoftware/Proton का योगदानकर्ता और SteamRE/SteamKit तथा SteamRE/open-steamworks का फोकर बताया गया है। इसकी प्रोफ़ाइल डेटा में Valve Software सूचीबद्ध है। इन फ़ील्ड्स को अलग-अलग पढ़ा जाना चाहिए।\n\nएक फोर्क रिपॉजिटरी की प्रतिलिपि रिकॉर्ड करता है। यह एक्सपोर्ट SteamKit प्रमाणीकरण कोड में किए गए परिवर्तनों को स्थापित करने वाला कोई कमिट संलग्न नहीं करता।\nरिपॉजिटरी संदर्भ / इतिहास की जाँच करें\nस्टीमआरई/स्टीमकिट ↗ SteamRE/ओपन-स्टीमवर्क्स ↗\n2. सार्वजनिक क्षमताएँ: डेस्कटॉप क्लाइंट के बिना स्वचालन\n\nSteamKit और node-steam-user प्रोग्रामेटिक इंटरैक्शन के लिए Steam को एक्सपोज़ करते हैं। ArchiSteamFarm मल्टी-अकाउंट कार्ड फार्मिंग का दस्तावेजीकरण करता है और SteamKit2 को एक निर्भरता के रूप में घोषित करता है।\n\nये ठोस स्वचालन क्षमताएँ हैं। हेडलेस निष्पादन विशिष्ट वाणिज्यिक उपयोग या 'Steam Guard' को बाईपास करने की अनुमति नहीं देता। प्रासंगिक प्रश्न हैं: अनुरोधित प्रमाण-पत्र, इसके लिए उपलब्ध क्रियाएँ और प्लेटफ़ॉर्म द्वारा लागू किए गए नियंत्रण।\n\nस्रोत: प्रोजेक्ट READMEs और ArchiSteamFarm.csproj। क्षमता मानचित्र प्रत्येक प्रलेखित निर्भरता को जोड़ता है।\n3. JoeLudwig: hl2sdk योगदानकर्ता लेबल\n\nस्नैपशॉट में JoeLudwig को alliedmodders/hl2sdk, ValveSoftware/openvr और ValveSoftware/source-sdk-2013. का योगदानकर्ता दिखाया गया है। यह एक स्पष्ट परियोजना संबंध है। एक्सपोर्ट किसी विशेष SDK परिवर्तन को चोरी या जुआ तैनाती से जोड़ने का कोई प्रमाण प्रदान नहीं करता।\n\nरिपॉजिटरी संदर्भ / इतिहास की जाँच करें\nalliedmodders/hl2sdk ↗ डॉक्टरमैकके/नोड-स्टीम-यूज़र ↗\nतार्किक योजनाबद्ध // निशान\nकनेक्शन तर्क प्रवाह-चार्ट:\nप्रोफ़ाइल संबंध\nनेफेरिन / संकलित प्रोफ़ाइल\nयोगदानकर्ता: प्रोटॉन। फोर्कर: स्टीमकिट और ओपन-स्टीमवर्क्स।\n▼ एकत्रित कांटा संबंध\nसामुदायिक पुस्तकालय\nस्टीमआर/स्टीमकिट\nSteamRE संगठन में बनाए रखा गया सार्वजनिक Steam नेटवर्क पुस्तकालय।\n▼ SteamKit2 निर्भरता घोषित\nदस्तावेजीकरण की गई स्वचालन\nजस्टआर्किनेट/आर्किस्टीमफार्म\nकई खातों में कार्ड फार्मिंग और SteamKit2 निर्भरता को दस्तावेज़ करता है।\nसाक्ष्य समीक्षा / स्रोत झलक\nरिकॉर्ड किया गया: अलग-अलग योगदानकर्ता और फोर्कर लेबल।\nदस्तावेजीकृत: सार्वजनिक पुस्तकालय कार्यक्रमगत Steam अंतःक्रियाओं का समर्थन करते हैं।\nखुला प्रश्न: विशिष्ट कोड लेखकत्व, प्लेटफ़ॉर्म अनुमोदन और दुरुपयोग के आरोप के लिए अलग-अलग साक्ष्यों की आवश्यकता होती है।",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "कोड। योगदानकर्ता। फोर्क।"
          },
          {
            "level": 2,
            "id": null,
            "text": "1. नेफेरिन: शाखाएँ और योगदान"
          },
          {
            "level": 2,
            "id": null,
            "text": "2. सार्वजनिक क्षमताएँ: डेस्कटॉप क्लाइंट के बिना स्वचालन"
          },
          {
            "level": 2,
            "id": null,
            "text": "3. JoeLudwig: hl2sdk योगदानकर्ता लेबल"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/hi/investigation_part2.html#automation-map",
          "https://github.com/SteamRE/SteamKit",
          "https://github.com/SteamRE/open-steamworks",
          "https://github.com/alliedmodders/hl2sdk",
          "https://github.com/DoctorMcKay/node-steam-user"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/hi/output_steam_network__valve_ru_farming_isolated.content.json",
      "export_json_sha256": "1443835d4400c1c9048f4f2694c6c72559e4263cb798ddc9ff9d420c7ca586cc"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "vi/card_economy.html",
      "language": "vi",
      "title": "Nền kinh tế thẻ — Hồ sơ “Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/vi/card_economy",
      "source_html_sha256": "0138003a9cf4199a46907f164d48d35c5d2e2d50161a2898d032c889e0b9c1e6",
      "exported_at": "2026-09-29T00:22:58.317Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "card_economy.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/vi/card_economy.pdf?v=print-20260929-v5",
        "sha256": "1c71140fd6e3be0a585faf3ecbced38a76f2178b9646032dfd13bfa74d01d10b",
        "bytes": 264431,
        "pages": 25
      },
      "integrity": {
        "signed_object": "card_economy.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "card_economy.content.json.asc",
        "digest_file": "card_economy.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify card_economy.content.json.asc card_economy.content.json",
          "sha256sum -c card_economy.content.json.sha256"
        ]
      },
      "content": {
        "text": "PHỤ LỤC V — NỀN KINH TẾ THẺ\nNền kinh tế thẻ — Bán buôn, giới hạn rút tiền và khai thác tự động\n\nMột trang trại bot không phải là lỗ hổng trong cửa hàng củValve. Đó là một khách hàng.\n\nPHẦN NÀY CHỨNG MINH ĐIỀU GÌ\n\nChương này chứng minh rằng các trang trại thẻ tự động trên Steam hoạt động như những khách hàng bán buôn có cấu trúc và tạo ra doanh thu, chứ không phải là những kẻ khai thác trái phép. Mỗi bot khai thác phải vượt qua ngưỡng kích hoạt $5.00 của Valve, mua giấy phép trò chơi và tạo ra các khoản phí giao dịch thị trường được đảm bảo (với mức tối thiểu là $0.02, và có thể lên đến 66.7% đối với các tài sản có giá trị thấp). Mặc dù Điều khoản Dịch vụ có quy định rõ ràng cấm các mạng bot tự động, nhưng các mạng bot thương mại được kiểm toán tại 91 vẫn công khai duy trì 694,673 các bộ thẻ hoàn chỉnh trên toàn bộ hệ sinh thái của Steam mà không gặp bất kỳ sự can thiệp nào từ phía cơ quan thực thi.\n\n← Quay lại Bản tóm tắt dành cho lãnh đạo\n\nMột tài khoản Steam sẽ không thể nhận được bất kỳ thẻ bài nào cho đến khi đã chi tiêu $5.00 trong cửa hàng. Hệ thống này không thể “farm” một trò chơi mà nó không sở hữu, và cũng không thể “farm” một trò chơi được tặng miễn phí. Vì vậy, trước khi một hệ thống “farm” thẻ tự động có thể tạo ra bất kỳ thứ gì, nó phải trả tiền để được phép tham gia — tính theo từng tài khoản, với mức giá do Valve công bố. Sau đó, điều khoản tự động hóa của Valve liệt kê chi tiết từng dòng chính xác những gì hệ thống đó sản xuất; giấy phép của nó cấm mọi hình thức biến thẻ thu hoạch được thành tiền; và thị trường của nó sẽ thu một phần hoa hồng khi thẻ đó được bán — được quảng cáo tại 15%, nhưng có mức tối thiểu là hai xu mỗi giao dịch, con số này chiếm phần lớn giá trị của một thẻ có giá tính bằng xu. Bài viết này đánh giá quy mô của hoạt động giao dịch này, chi phí tính theo bộ cho mức cao nhất trong một hồ sơ, và cách bộ phận thực thi của Valve áp dụng điều khoản tương tự khi tài khoản thuộc về một nhà giao dịch thông thường.\n\nNhững thứ mà một trang trại cần mua trước tiênGiá của một cấp độ tính theo bộ là bao nhiêuHai bên bàn làm việcAi là người điều tiết nền kinh tế thẻ?\n$5.00Lưu chi tiêu trước khi tài khoản có thể nhận bất kỳ thẻ nào — Trang hỗ trợ chính thức của Valve\n13,876Các trò chơi trên Steam phát hành thẻ sưu tập, bao gồm 99,971 các loại thẻ khác nhau\n694,673Các bộ thẻ hoàn chỉnh hiện đang có sẵn trong kho của các bot giao dịch được niêm yết công khai trên 91\n1,389,346Mức trích lập dự phòng cho thẻ tài khoản và thẻ trò chơi mà kho hàng đã sử dụng, ít nhất là\n$9.99Giá trung vị của một trò chơi dùng thẻ — bộ hoàn chỉnh của trò chơi này được bán với giá trung vị là $0.74\n97,114Các thành viên của nhóm trao đổi thẻ, trong danh sách người điều hành có một nhân viên củaValve— § 08\n01 — Quy trình\nMột trang trại thực sự là gì, từng bước một\n\nNội dung này chỉ được trình bày dựa trên tài liệu hướng dẫn của chính công cụ và các trang hỗ trợ của Valve. Không có nội dung nào trong phần này là suy luận, và không có nội dung nào trong đó bị bất kỳ bên nào phản đối.\n\nBước1\nMua vào\n\nTài khoản đó không được hạn chế. Trang hỗ trợ của Valve không cho phép các tài khoản bị hạn chế \"Tham gia vào thị trường 'Steam'\", từ \"Trao đổi các vật phẩm trong cộng đồngSteam (thẻ bài, gói mở rộng, đá quý, v.v.)\" và từ \"Nâng cấp các cấp độ hồ sơ trong trò chơi 'Steam' (giới hạn ở cấp độ 0) và thu thập thẻ bài\". Cánh cổng chính là tiền: \"Bạn sẽ cần chi tiêu ít nhất $5.00 tại cửa hàng Steam.\"\n\nBước2\nMua trò chơi\n\nThẻ chỉ rơi ra từ các trò chơi mà bạn sở hữu. \"Bạn cần phải sở hữu trò chơi trên tài khoản Steam của mình thì mới đủ điều kiện nhận các thẻ thưởng từ trò chơi đó. Chức năng chia sẻ trong gia đình không được coi là sở hữu và không được tính.\" Các tuyến đường miễn phí cũng đã bị đóng cửa: \"Các trò chơi trả phí mà bạn đã nhận được miễn phí trong thời gian khuyến mãi không thể được sử dụng để \"farm\" nhằm nhận thẻ\", và \"Bạn không thể nhận thẻ từ các trò chơi miễn phí mà không cần chi tiêu bất kỳ khoản tiền nào trong đó.\"\n\nBước3\nKhông hoạt động\n\nCông cụ này đăng nhập tài khoản vào mạng Steam ở chế độ không giao diện, \"xử lý các huy hiệu của bạn\", tạo danh sách các tựa game có thể cày cuốc và bắt đầu \"chơi các trò chơi đủ điều kiện và định kỳ kiểm tra xem trò chơi đó đã được khai thác hết chưa.\" Mô tả của người duy trì về cơ chế này: nó \"Chỉ đơn thuần là thông báo cho Steam rằng chúng tôi đang chơi trò chơi đó mà thôi.\"\n\nBước4\nHạt nhỏ đã cạn\n\nMỗi tiêu đề đều có giới hạn. \"Mỗi trò chơi đều có số lượng thẻ rơi ra cố định. Một khi bạn đã thu thập hết số thẻ đó (khoảng một nửa bộ sưu tập đầy đủ), trò chơi đó sẽ không còn là lựa chọn để cày cuốc nữa.\" Một trang trại muốn tiếp tục sản xuất thì phải liên tục mua các thẻ bài. Nguồn cung thẻ bài bị hạn chế bởi các giao dịch mua — điều này là do thiết kế của trò chơi và mang lại lợi thế choValve.\n\nBước5\nRút tiền\n\nThẻ sẽ rời đi qua một trong ba lối: được bán trên Thị trường Cộng đồng, được trao đổi, hoặc được nghiền nát thành đá quý. Mỗi trường hợp đều là một giao dịch trên Thị trường Đăng ký hoặc một cuộc trao đổi, và § 3.D sẽ thu phí: \"Valve có thể thu phí đối với các giao dịch trên Nền tảng Giao dịch Đăng ký.\" Đây chính là bước khiến toàn bộ sự việc trở thành một vụ vi phạm — xem 05.\n\nCác nguồn, được trích dẫn nguyên văn trên trang 2026-09-22: Steam Hỗ trợ — Tài khoản người dùng có giới hạn ↗ · Câu hỏi thường gặp về ArchiSteamFarm ↗ · Valve — Câu hỏi thường gặp về Thẻ sưu tập “Steam” ↗ · Steam Thỏa thuận người đăng ký ↗ đã lưu trữ 2026-09-24 ↗. ArchiSteamFarm được đề cập trong toàn bộ trang này với tư cách là một công cụ đo lường, chứ không phải là đối tượng bị cáo buộc; chính tài liệu hướng dẫn của nó đã nêu rõ rằng \"ASF không được Valve ủy quyền\".\n\n02 — Thang đo\nTrước khi một trang trại kiếm được một xu, nó đã phải chi trả Valve\n\nVì tài khoản bị giới hạn không thể nhận thẻ, nên mọi tài khoản trong một trang trại đều phải được nâng cấp khỏi trạng thái bị giới hạn trước khi có thể sản xuất bất kỳ thứ gì. Mức phí tối thiểu đã được công bố và sẽ được tính theo từng tài khoản.\n\nQuy mô trang trại\tCon số này xuất phát từ đâu?\tSố tiền mua sắm tối thiểu tại cửa hàng để đủ điều kiện nhận thẻ\n10 accounts\tThe ceiling ASF recommends — \"based on internal Valve guidelines, as well as our own suggestions\"\t$50\n100–200 accounts\tTechnical ceiling in the same FAQ: \"you can run up to 100-200 bots with a single IP and a single ASF instance\"\t$500 – $1,000\n120 accounts\tEnforcement case 3 below — permanently banned\t$600\n170 accounts\tEnforcement case 2 below — permanently banned during the 2017 Winter Sale\t$850\n1,000 accounts\tEnforcement case 1 below — trade banned\t$5,000\n5,000 accounts unverified\tOperator scale reported to this investigation and not independently checked — see the note on sourcing\t$25,000\n10,000 accounts unverified\tOperator scale reported to this investigation and not independently checked — see the note on sourcing\t$50,000\n\nHai hàng cuối cùng là những số liệu duy nhất trên trang này dựa trên một báo cáo chưa được xác minh chứ không phải một tài liệu — chúng đã được đánh dấu trong bảng và được giải thích trong lưu ý về nguồn cung ứng, và không có yếu tố nào khác ở đây phụ thuộc vào chúng. Cột bên phải là các phép tính dựa trên ngưỡng $5.00 USD mà Valve đã công bố và không có yếu tố nào khác. Đó là một sàn, đây không phải là ước tính về chi phí vận hành một trang trại hay thu nhập từ trò chơi “Valve”: con số này không bao gồm các trò chơi — vốn phải là tài sản sở hữu và không thể là phần thưởng miễn phí từ chương trình khuyến mãi — cũng như không tính đến khoản phí khoảng 15% mà Chợ Cộng đồng thu khi các lá bài được bán. Trang này không công bố bất kỳ con số doanh thu nào.\n\nVà chính trang web Valve cũng đã niêm yết giá cho đợt phát hành thẻ này. Phần Câu hỏi thường gặp (FAQ) về Thẻ sưu tập của trò chơi này đã nêu rõ tỷ lệ chuyển đổi của mô hình chơi miễn phí bằng đơn vị tiền tệ cụ thể:\n\n\"Các trò chơi miễn phí sẽ phát hành thẻ trò chơi dựa trên các giao dịch mua hàng trong trò chơi của bạn.\" Với mỗi9 USD chi tiêu (khoảng) \"Kể từ khi phiên bản thử nghiệm (Beta) của trò chơi thẻ bài \"Steam\" bắt đầu, bạn sẽ nhận được một lá bài.\"\n\n— Câu hỏi thường gặp về thẻ sưu tập Valve và Steam ↗ · Đã xác minh nguyên văn 2026-09-22\n\nThẻ sưu tập không phải là món quà tặng khiến nền tảng phải chịu lỗ. Đó là mặt hàng mà Valve bán ra, với mức giá được công bố tại Valve — và sau đó họ còn thu phí lần thứ hai khi bán lại. Đó chính là lý do tại sao mô tả trung thực về một “trang trại thẻ” không phải là ký sinh trùng. Đó là người mua sỉ.\n\nKích thước thực tế của món đồ đang được mua là bao nhiêu\n\nTất cả thông tin từ đây cho đến cuối phần này đều được đo lường, chứ không phải dựa trên báo cáo. Số liệu thống kê thẻ là bảng giá huy hiệu do Steam Card Exchange công bố; giá của các trò chơi được lấy từ cửa hàng riêng của Valve tại địa chỉ API; số lượng bot được lấy từ một danh mục bot công khai mà bất kỳ ai cũng có thể truy cập. Cả ba nguồn này đều được trích dẫn từ 2026-09-22 và các phép tính được trình bày đầy đủ trong phần 08.\n\n13,876Các trò chơi phát thẻ\n99,971Các loại thẻ riêng biệt\n5 · 6 · 15Số thẻ trong mỗi bộ: giá trị nhỏ nhất, giá trị trung vị, giá trị lớn nhất\n$0.74Giá trung vị của một bộ sản phẩm hoàn chỉnh\n$23,586.57Mỗi bộ chỉ có một chiếc trên thị trường\nMột tập có kích thước bao nhiêu?\n\n13,876 các trò chơi bằng thẻ trong bộ. Valve sẽ phân phối khoảng một nửa số thẻ đó cho bất kỳ tài khoản nào.\n\n0\n1,250\n2,500\n3,750\n5,000\n5\n6\n7\n8\n9\n10\n11\n12\n13\n14\n15\nChi phí cấp giấy phép là bao nhiêu?\n\nGiá niêm yết của các tựa game tương tự trên cửa hàng củSteam, tính bằng đô la Mỹ.\n\n0\n1,000\n2,000\n3,000\n4,000\n<$1\n$1-3\n$3-5\n$5-10\n$10-20\n$20-40\n$40+\nKết quả trả về của tập hợp đã hoàn thành là gì\n\nGiá thị trường của bộ sản phẩm hoàn chỉnh dành cho các tựa game tương tự.\n\n0\n1,500\n3,000\n4,500\n6,000\n<$0.50\n$0.50-1\n$1-2\n$2-5\n$5-10\n$10+\n\nHãy so sánh biểu đồ thứ hai và thứ ba với nhau, và hình thái của giao dịch sẽ hiện rõ mà không cần tính toán: các trò chơi tập trung ở mức hàng chục đô la, trong khi các phần thưởng mà chúng mang lại tập trung ở mức dưới một đô la. Cả hai đều là số lượng của cùng các trò chơi 13,876, trên cùng một đơn vị trục, nên việc so sánh là giữa hai mức độ chứ không phải giữa hai thang đo.\n\nĐó là khía cạnh về phía cung. Khía cạnh về phía cầu là phần mà trang web Valve không cần phải quảng cáo, bởi vì thông tin này đã được công khai: một danh mục mở duy nhất liệt kê các bot trao đổi thẻ 91 Hiện tại, các bot đang có sẵn các bộ sưu tập đầy đủ của “694,673” trong kho. Không cần đăng nhập, không cần trích xuất dữ liệu từ sàn thương mại điện tử, không có dữ liệu cá nhân — số lượng hàng tồn kho được hiển thị ngay trên trang, bên cạnh tên của từng bot.\n\nHãy biến cổ phiếu đó thành đơn vị duy nhất có ý nghĩa ở đây. Nguyên tắc của chính Valve: \"Hầu hết các trò chơi sẽ rút ra một số lá bài tương đương khoảng một nửa số lá bài trong bộ bài của trò chơi đó… Bạn sẽ cần thu thập nửa còn lại của bộ sưu tập từ các thành viên khác trong cộng đồng.\" Một tài khoản không bao giờ có thể hoàn thành một bộ bằng cách chơi. Ít nhất phải có hai tài khoản, mỗi tài khoản sở hữu trò chơi đó và mỗi tài khoản đều sử dụng hết hạn mức thả vật phẩm (mỗi trò chơi chỉ được thả một lần). Hạn mức thả vật phẩm sẽ không được phục hồi.\n\n694,673Các gói sản phẩm có sẵn trong kho, các bot công khai trên 91\n3,473,365Bộ bài, bộ bài tối thiểu “5-”\n1,389,346Số lượng trợ cấp đã sử dụng, mức tối thiểu\n2,602Các tài khoản chỉ sở hữu một trò chơi duy nhất, có mật độ bot cao nhất\nVị trí hiện tại của các cụm máy bay chiến đấu F-694,673\n\n12 tài khoản bot sưu tập thẻ lớn nhất trên 91, xếp theo số lượng bộ thẻ đầy đủ có sẵn trong kho. 10 tài khoản lớn nhất này sở hữu tổng cộng 248,115 bộ thẻ — chiếm 35.7% tổng số thẻ có trên bảng.\n\n0\n11,250\n22,500\n33,750\n45,000\nCard Supply #4 (High)\nN!vq's Leveling (High)\nAlice [BOT] LEVEL-UP RARE SETS\nN!vq's Leveling (Low)\nDisco Lite Level Up\nN!vq's Leveling (Mid)\nbaty131store.net | Level Up\nKitten - Supreme\nArashirn | Level Up\nSH (Junior) Level Up\nDuobot.com - Overstock\nlvlupbot.com - godlike\n\nMỗi khoản trợ cấp trong số 1.39 triệu đó đều thuộc về một tài khoản đã sở hữu trò chơi, đã vượt qua cổng $5.00, và sẽ không bao giờ có thể tạo ra những phần thưởng đó một lần nữa. Đây là hàng tồn kho chưa bán được trên 91 bot. Đây không phải là thước đo của thị trường; đây là thước đo những gì còn lại sau khi thị trường đã diễn ra.\n\nCon số cuối cùng là số lượng ô phân loại, không phải số lượng người dùng. Một bot liệt kê 14,310 bộ được rút ra chỉ từ 11 trò chơi, do đó ít nhất một trong số những trò chơi đó được đại diện bởi 1,301 bộ, tương ứng với ít nhất 2,602 tài khoản riêng biệt, mỗi tài khoản đã mua trò chơi đó. Đây là con số nhỏ nhất mà phép tính cho phép, và nó liên quan đến một bot trong số chín mươi mốt.\n\nNhững điều sàn nhà này thể hiện và không thể hiện\n\nCác bot này mua thẻ từ người chơi thông thường cũng như từ các trang trại — mức giá mua mà chúng công bố chính là nội dung chính của danh mục này. Vì vậy, 1.39 triệu khoản trợ cấp này không phải là số lượng tài khoản thuộc sở hữu của các trang trại. Đó là số lượng phần thưởng rơi ra giới hạn mỗi tài khoản một lần, mỗi trò chơi một lần, đã được sử dụng ở đâu đó trên Steam và cuối cùng vẫn chưa bán được, nằm trong kho hàng thương mại. Dù tài khoản đứng sau mỗi mặt hàng đó là một tài khoản farm hay một thiếu niên đang hoàn thành trang huy hiệu thì điều đó cũng không thay đổi những gì Valve đã thu được: khoản mở khóa $5.00, giấy phép trò chơi và phần hoa hồng từ mỗi giao dịch — không phải 15%, mà là 15% hoặc hai mức tối thiểu 1 cent, tùy theo mức nào cao hơn, mà trên một tấm thẻ có giá tính bằng xu thì con số này lớn hơn rất nhiều. Cách tính như sau: bảng phí dưới đây. Đó chính là nội dung chính của trang này, và đây không phải là lời phàn nàn về các nông dân: chính hành vi mà Valve thu phí lại chính là hành vi mà trang web này trích dẫn nguyên văn khi cấm vĩnh viễn một cá nhân vì “mục đích thương mại”.\n\nCon số này cũng là mức sàn theo một nghĩa khác. Nó chỉ tính đến những cổ phiếu mà đã được niêm yết và chưa bán được hôm nay về các bot mà chọn đặt trong thư mục công khai. Tất cả các sản phẩm đã được bán hết, tất cả các sản phẩm được giữ riêng tư và mọi bot nằm ngoài danh mục đều bị loại trừ.\n\nVà với mức giá mà “Valve” đưa ra, việc làm nông không thể tự trang trải chi phí\n\nLý do phản đối rõ ràng là các trang trại mua các trò chơi giá rẻ để sản xuất thẻ bài đắt tiền. Tuy nhiên, cửa hàng của chính Steam tại địa chỉ API lại cho thấy điều ngược lại. Trong số các trò chơi có thẻ bài thuộc danh mục “13,876”, giá đã được xác định như sau trên trang 13,713; 12,918 là những tựa sách phải trả tiền với mức giá niêm yết trung vị là $9.99. Giá bán trung vị của một bộ sản phẩm hoàn thiện là $0.74. Mỗi bộ cần hai giấy phép. Do đó, giá trung vị của một bộ vào khoảng $19.98 từ giấy phép trò chơi để sản xuất và thu về $0.74.\n\nDữ liệu được đo trên 2026-09-22\tGiá trị\tNội dung thỏa thuận\nMedian list price, card-bearing game\t$9.99\tThe licence is the expensive half of the transaction, not the card\nGames priced at $4.99 or less\t3,665 (28.4%)\tEven the cheap tail is dearer than the set it yields\nCheapest card-bearing game on the store\t$0.99\tTwo licences, $1.98, for a set that typically sells under $1.30\nGames whose set sells for more than the game\t323 of 12,918 (2.5%)\tCard arbitrage against Steam's list prices exists in 1 game in 40\nFree-to-play titles in the census\t795\tAnd Valve prices each of their drops at $9 of in-game spend\n\nĐiều này đã giải quyết vấn đề kinh tế theo hướng có lợi cho “Valve” và đi ngược lại với quan điểm thông thường. Với mức giá mà chính “Valve” áp dụng, Việc thu thập thẻ là một hoạt động thua lỗ, chỉ có hiệu quả khi các giấy phép được mua với giá thấp hơn giá niêm yết trên Steam — các gói sản phẩm, chính sách giá theo khu vực, bán lại chủ chốt. Các thẻ chỉ là phần còn lại. Việc mua hàng mới là sự kiện chính. Và giao dịch đó đã diễn ra trên Steam.\n\nĐiều mà trang trại thực sự hỗ trợ\n\nKhi ghép các mảnh ghép lại với nhau, trang trại không còn trông giống như thứ mà Valve chỉ đơn thuần chấp nhận, mà bắt đầu trông giống như thứ mà Valve thực sự cần. Mỗi đầu vào mà trang trại cung cấp đều là một đầu ra mà Valve báo cáo hoặc lập hóa đơn. Hãy theo dõi một tài khoản bot từ đó ra ngoài:\n\nMột tài khoản được tạo ra nhằm mục đích khai thácmột “khách hàng bán buôn”, chứ không phải là một vụ rò rỉ\nDoanh số bán game\n\nMua các tựa game mà họ “farm” — từ các trò chơi bài thuộc dòng “13,876” cho đến những tựa game rác giá $0.50 — bởi vì thẻ bài chỉ rơi ra từ các trò chơi mà người chơi sở hữu.\n\n\"Trực tuyến\" & thời gian chơi\n\nKhiến họ nhàn rỗi để thu thập thẻ, từ đó góp phần vào các con số về số người chơi đồng thời và số giờ chơi mà Valve coi là mức độ tương tác — chính xác là chỉ số mà § 4.C gọi là “giả mạo thời gian chơi”.\n\nĐăng ký\n\nPhải vượt qua ngưỡng tài khoản giới hạn $5.00 trước khi có thể nhận thẻ — mỗi tài khoản phải có Valve giao dịch chi tiêu thực tế tại cửa hàng.\n\nTiền trong ví và phí\n\nMỗi thẻ mà công ty bán ra đều được chuyển qua Thị trường, nơi mức phí có thể lên tới 66.7% đối với thẻ có giá trị thấp và số tiền thu được sẽ bị khóa trong Ví Steam.\n\nSteam- PR cấp độ\n\nCác huy hiệu và cấp độ được giới thiệu trên trang Valve chỉ tồn tại nhờ việc người chơi đã tạo ra các bộ sưu tập — và vị trí đầu bảng xếp hạng đó chủ yếu do bot chiếm giữ (xem § 03).\n\nLoại bỏ trang trại đi thì tất cả các con số ở trên đều giảm xuống — trò chơi bán được ít bản hơn, quy mô “trực tuyến” nhỏ hơn, tài khoản chưa bao giờ được đăng ký, phí chưa bao giờ được thu, và cấp độ chưa bao giờ được đạt tới. Đó là lý do tại sao một quy định cấm tự động hóa lại tồn tại song song với hàng triệu tài khoản tự động: lệnh cấm chỉ là một lựa chọn, còn hoạt động mới chính là nguồn doanh thu.\n\nVà chính việc rút tiền mặt này đã làm giảm giá trị Valve — bị đánh thuế hai lần\n\nLá bài không phải là điểm kết thúc của vòng lặp. Cơ chế riêng của “Valve” cho phép một lá bài bị nghiền nát thành đá quý, và các viên đá quý sẽ được sử dụng để chế tạo gói thẻ mở rộng — thêm ba lá bài nữa — sẽ được bán hoặc nghiền nát một lần nữa. Mỗi bước nhảy là một giao dịch trên Thị trường hoặc một lần chuyển đổi, và mỗi giao dịch đều phải chịu thuế. Hướng của vòng lặp này được xác định dựa trên mức phí tối thiểu được đo lường bên dưới và không cần đến mô hình bên ngoài nào: mọi lá bài được bán bên trong vòng lặp đó đều phải từ bỏ ít nhất hai xu, trên các thẻ có tỷ lệ trao đổi từ ba đến năm, nên mỗi lần quay tay quay sẽ thu về ít hơn số đã bỏ ra. Vòng lặp này làm mất giá trị ảo và buộc phải thực hiện các giao dịch mới, kèm theo phí, để thay thế cho nó. Bài viết này không đưa ra con số cụ thể nào về quy mô khoản lỗ đó — Lợi nhuận trên mỗi bộ phụ thuộc vào tỷ lệ xuất hiện đá quý và tỷ lệ mở gói bổ sung — những yếu tố này chưa được nghiên cứu này đo lường.\n\nThẻ sưu tậpvật phẩm rơi ra từ trò chơi sở hữu\n→\nĐá quýthẻ bị nghiền nát, phí đã thu\n→\nGói mở rộngsố đá quý đã sử dụng để chế tác\n→\n3 thẻ mớiđã bán trên Market, đã trừ phí\n↶\n\nỞ đây chỉ đề cập đến các cơ chế, và đó là những cơ chế riêng của trò chơi “Valve” — thẻ bài chuyển đổi thành đá quý, đá quý dùng để chế tạo gói thẻ, gói thẻ cho ra thẻ bài — mỗi bước đều được ghi rõ trong phần Câu hỏi thường gặp (FAQ) về thẻ bài sưu tập “Steam”, và mỗi bước chuyển đổi đều là một sự kiện Thị trường phải chịu thuế. Nguồn gốc của cơ chế lặp lại này: Câu hỏi thường gặp về thẻ sưu tập Valve và Steam ↗.\n\nĐây không chỉ là một khoảnh khắc. Đây là một ngành công nghiệp có nền tảng vững chắc được xây dựng qua nhiều năm.\n\nMột bản chụp nhanh duy nhất có thể chỉ là sự ngẫu nhiên. Vì vậy, danh mục công khai của các bot thẻ tín dụng đã được kiểm tra một lần trong mỗi đợt giảm giá theo mùa tại Steam, từ các đợt trước đó tại Wayback Machine, từ 2022 đến 2026 — danh mục hàng tồn kho mà các bot đang nắm giữ, cùng với các tài khoản đó, đợt giảm giá này qua đợt giảm giá khác. Nền kinh tế này không xuất hiện rồi biến mất; nó tồn tại liên tục, với một nhóm cốt lõi ổn định gồm các nhà điều hành, và đã đạt đỉnh ở mức trên Có sẵn ba triệu bộ hoàn chỉnh trong kho trong đợt giảm giá “2023” mùa đông — vào một thời điểm nhất định, có khoảng một phần ba triệu khóa TF2 có giá trị được lưu trữ trong một thư mục.\n\nCác bộ thẻ hoàn chỉnh được lưu trữ trong thư mục bot công khai, theo đợt bán hàng của Steam\n\nMột bản chụp nhanh từ Wayback của steam.supply/CardBots cho mỗi đợt giảm giá theo mùa. Di chuột vào để xem giá trị của các chìa khóa TF2 theo tỷ giá tại thời điểm chụp nhanh đó.\n\n0.0M\n0.9M\n1.8M\n2.6M\n3.5M\nA’22\nS’23\nW’23\nS’24\nW’24\nS’25\nS’26\n401Các tài khoản bot riêng biệt được phát hiện trong các giao dịch bán hàng\n59Chiếm từ 5 trở lên trong tổng doanh số 7 — cốt lõi ổn định\n16Luôn có mặt trong mọi đợt bán hàng của 7, 2022–2026\n3.22MSố lượng tồn kho đạt đỉnh (2023 mùa đông) ≈ $570k–790k trong kho\nBảng xếp hạng huy hiệu bán hàng trông như thế nào khi nhìn từ đỉnh\n\nPhía cầu tương ứng với phía cung. Trên thị trường công cộng Chương trình khuyến mãi mùa hè – Bảng xếp hạng huy hiệu “2024” đã lưu trữ 2026-07-16 ↗, tài khoản đứng đầu đã tạo ra huy hiệu bán hàng 1,740,645 lần — 1.74 triệu bộ gồm mười lá bài, 17.4 triệu lá bài được kết hợp thành một mẫu trang trí duy nhất. Theo giá thị trường của chính sự kiện bán hàng này (0.50 mỗi bộ), đó là ~$870,000 giá trị thẻ; được mua theo cách thực tế — các khóa TF2 được trao đổi để nâng cấp bot với tỷ lệ khoảng 7.6 quy định một khóa — đó là ~229,000 keys, khoảng $410,000–$570,000 theo giá trị thực. Tài khoản thứ hai: Bộ sản phẩm “552,000” với giá khoảng $130,000–181,000. Không có con người nào tham gia giao dịch này. Nó được mua, và mỗi đợt mua đều là một giao dịch do Valve xử lý.\n\nPhương pháp và giới hạn: số lượng cổ phiếu trong danh mục được tính tổng trên tất cả các bot được liệt kê trong mỗi bản chụp; số Số lượng bot trên mỗi ảnh chụp nhanh không thể so sánh giữa các đợt bán hàng vì một số ảnh chụp nhanh chỉ hiển thị các bot nổi bật, trong khi một số khác hiển thị toàn bộ danh mục; do đó, số lượng này được xem là mức tối thiểu của những gì có thể nhìn thấy, chứ không phải là số liệu thống kê toàn diện. Các giá trị chìa khóa sử dụng tỷ lệ trung vị số bộ chìa khóa được quảng cáo trên mỗi chìa khóa của từng ảnh chụp nhanh và một chìa khóa TF2 có giá $1.79–$2.49. Tính nhất quán được đảm bảo bằng SteamID64 giữa các ảnh chụp nhanh. Các ảnh chụp nhanh 2021 sử dụng bố cục trang cũ hơn và không được bao gồm. Dữ liệu: farm-economy-timeline.json; các cấp độ huy hiệu từ SteamLadder; giá niêm yết từ Sàn giao dịch thẻ Steam (ảnh chụp màn hình Wayback tại thời điểm bán, $0.05mỗi thẻ).\n\nVà đội tàu đó vẫn ở đó ngay cả khi không có đợt giảm giá nào đang diễn ra\n\nHai bức ảnh trên không phải là hai quần thể. Đó là cùng một hạm đội, được chụp vào những thời điểm khác nhau. Thư mục được đề cập ở đầu phần này đã được đọc trên một một ngày bình thường, không có chương trình giảm giá theo mùa nào đang diễn ra — 2026-09-22 — và ngay cả khi không hoạt động, nó vẫn duy trì 91 bộ sản phẩm hoàn chỉnh gồm bot và 694,673: vào khoảng 186,000 Các phím TF2, $334,000–$464,000 giá trị thẻ, đang nằm không giữa các đợt bán hàng. Đó là mức chi phí tối thiểu mà hoạt động kinh doanh phải gánh chịu khi không có giao dịch nào diễn ra.\n\nVà đây là cùng một thao tác. Được xác định dựa trên SteamID64, 87 trong số các bot nghỉ ngơi trên 91 — 96% — cũng xuất hiện trong bảy ảnh chụp màn hình giao dịch ở trên, mỗi chiếc đều chở mười sáu chiếc. Danh mục này không phải là một gian hàng chỉ mở ra để bán hàng rồi đóng cửa sau đó; đây là một kho hàng thương mại thường trực mà chính đội tàu này đã làm tăng lên đến mức 3.22 triệu bộ vào thời điểm cao điểm của chương trình “2023” mùa đông và nhiệt độ không bao giờ giảm xuống 0. Giảm giá là khi sản phẩm được bán ra. Chương trình này cũng diễn ra trong suốt phần còn lại của năm.\n\nThư mục lưu trữ, theo từng bot\n\nMỗi ô vuông tương ứng với một bot trong danh mục trên trang 2026-09-22, và sẽ được đánh dấu nếu bot đó cũng xuất hiện trong bảy ảnh chụp nhanh về tình hình bán hàng. 91 đó là thông tin được liệt kê trong danh bạ vào ngày hôm đó, chứ không phải quy mô của đội tàu — 401 tài khoản khác nhau xuất hiện trong các bản chụp nhanh giao dịch, và danh sách này hiển thị một phần khác nhau vào các ngày khác nhau.\n\nĐã xuất hiện trong các đợt bán hàng trước đây (87) Các thay đổi mới so với bản chụp nhanh gần nhất (4)\n\nDữ liệu tham chiếu không liên quan đến đợt giảm giá được đọc từ 2026-09-22 trong cùng một thư mục công khai, không cần đăng nhập. Giá trị mặc định sử dụng tỷ lệ “số bộ trên mỗi khóa” do từng bot tự công bố và dải khóa $1.79–$2.49 nêu trên. Sự trùng lặp được xác định dựa trên SteamID64 so với bảy bản chụp nhanh thời điểm giảm giá. Do danh sách nổi bật và danh sách đầy đủ khác nhau tùy theo từng bản chụp nhanh, nên so sánh này tập trung vào số lượng hàng tồn kho và danh tính, chứ không phải số lượng người dùng. Các phép tính trong phần 08.\n\n03 — Cái thang\nSản phẩm còn lại là con số nằm bên cạnh tên của bạn\n\nThẻ bài là nguyên liệu thô. Sản phẩm hoàn chỉnh là một cấp độ “Steam”, và Valve quy định giá bán theo từng bộ.\n\n100Steam Cấp độ\nMức mục tiêu — kéo hoặc sử dụng các phím mũi tên\nGiá của một bộ đầy đủ, USD\n\n$0.20 là bộ đầy đủ rẻ nhất trong danh sách, $0.74 là giá trung vị, $1.70 là giá trung bình. Con số này chỉ bao gồm các thẻ — không bao gồm các nội dung mở khóa $5.00 hay giấy phép trò chơi.\n\n55,000Yêu cầu XP\n550Số bộ hoàn chỉnh đã tiêu thụ\n110Những tựa game đáng sở hữu, tự mình cày cuốc\n$407.00Giá của các thẻ ở mức giá đó\n1,100Trừ đi lượng phát thải đã đốt, mức tối thiểu\n$5,500.00$5.00 sẽ được mở khóa nếu không có tài khoản nào bị sử dụng lại\nCác bộ sản phẩm đã được tiêu thụ, cấp độ 1 đến 1,000\n\nMột món đồ thủ công huy hiệu = một bộ hoàn chỉnh = 100 XP. Mỗi cấp độ trong một nhóm mười cấp sẽ tốn thêm 100 XP so với nhóm cấp độ ngay dưới nó.\n\n0\n12,625\n25,250\n37,875\n50,500\n1\n250\n500\n750\n1000\n667\n550 sets\n\nMột cấp độ không phải là thứ trang trí mà Valve bỏ qua. Nó được gắn liền với tài khoản. Theo phần Câu hỏi thường gặp về Thẻ Giao dịch trên Valve, về những gì bạn nhận được khi chế tạo một huy hiệu: \"100XP, điều này có thể giúp tăng mức độ Steam của bạn. Nếu cấp độ “Steam” của bạn tăng lên, giới hạn số lượng bạn bè trong danh sách của bạn sẽ được tăng thêm năm người, và có thể bạn sẽ mở khóa tính năng tùy chỉnh hồ sơ của mình bằng các mục giới thiệu.\" Và về các gói thẻ mở rộng: \"Cấp độ 'Steam' của bạn sẽ giúp tăng tỷ lệ nhận được gói thẻ bổ trợ: Cấp độ 10: +20%… Cấp độ 50: +100% giúp tăng tỷ lệ nhận được gói thẻ bổ trợ (i.e. Tỷ lệ này đã tăng gấp đôi).\"\n\nVì vậy, cấp độ này quyết định hai yếu tố mà Valve kiểm soát: số lượng người bạn được phép kết bạn, và tốc độ các thẻ miễn phí rơi vào kho của bạn. Yếu tố thứ hai có tính lũy tiến — bạn đã tiêu thụ càng nhiều bộ thẻ, nền tảng sẽ cung cấp thêm nội dung cho bạn càng nhanh. Valve đã tích hợp vòng lặp tái đầu tư vào sản phẩm.\n\nTỷ giá hối đoái là cố định và được công bố. Mỗi lần chế tạo huy hiệu sẽ tiêu tốn một bộ nguyên liệu đầy đủ và mang lại100XP; \"Bạn có thể chế tạo một bộ trang bị cho cùng một trò chơi tối đa năm lần.\" Số XP cần thiết để lên một cấp sẽ tăng lên sau mỗi mười cấp. Điều này dẫn đến kết quả như sau, và tất cả các con số dưới đây đều là số liệu chính xác, không phải ước tính:\n\nSteam Cấp độ\tCác bộ sản phẩm hoàn chỉnh mà nó tiêu thụ\tNhững tựa game bạn nhất định phải sở hữu để tự tay chế tạo chúng\tỞ mức giá rẻ nhất từng được ghi nhận (0.20 USD)\tTại tập giá trị trung vị ($0.74)\tTỷ lệ\n10\t10\t2\t$2.00\t$7.40\t\n50\t150\t30\t$30.00\t$111.00\t\n100\t550\t110\t$110.00\t$407.00\t\n200\t2,100\t420\t$420.00\t$1,554.00\t\n500\t12,750\t2,550\t$2,550.00\t$9,435.00\t\n667\t22,579\t4,516\t$4,515.80\t$16,708.46\t\n\n667 Đây không phải là giả thuyết. Đây là mức cao nhất mà một bot duy nhất trong danh mục công khai tuyên bố có thể giúp khách hàng đạt được, trong số các bộ thẻ “33,359” mà bot đó sở hữu trên các trò chơi thuộc 6,117. Cột thứ tư là mức giá tương ứng với bộ hoàn chỉnh rẻ nhất được ghi nhận trong cuộc điều tra; cột thứ năm tương ứng với mức giá trung vị. Cả hai đều là giá thị trường chỉ tính riêng các lá bài và hoàn toàn không bao gồm phí mở khóa $5.00 cũng như các giấy phép trò chơi.\n\nCách kiểm tra đường cong này như thế nào, vì trang Valve không công bố số liệu này\n\nValve nêu rõ tỷ lệ huy hiệu (\"Mỗi lần 100 XP sẽ giúp bạn tăng thêm Steam Level\") và sau đó thực hiện các giao dịch phòng ngừa rủi ro — \"(ít nhất là lúc đầu)\" — mà không công bố mức tăng dần. Đường cong được sử dụng ở trên là đường cong tiêu chuẩn, trong đó mỗi cấp độ trong một khối gồm mười cấp sẽ tốn thêm 100 XP so với khối ngay dưới nó. Điều này đã được xác minh dựa trên danh mục thay vì chỉ là giả định: đối với mỗi bot mà mức tối đa công bố bị giới hạn bởi số lượng sẵn có của nó thay vì giới hạn năm món đồ thủ công mỗi trận, mức được tính toán từ đường cong này trùng khớp chính xác với mức mà bot công bố — 541 so với 541, 494 so với 494, 464 so với 464. Ở những nơi mà mức trần có tác động, con số tính toán cao hơn một vài bậc, và đó chính là điều mà một mức trần cũng phụ thuộc vào độ sâu đội hình trong từng trận đấu nên làm. Không có khẳng định nào được đưa ra về đường cong ở mức trên 667.\n\nHãy xem bảng phân cấp bên cạnh mục “02” (Các cấp độ tài khoản) thì sẽ thấy được cấu trúc hoạt động của doanh nghiệp. Để đưa một tài khoản lên cấp độ “500,” (Cấp độ 1), người đó phải tập hợp đủ các bộ “12,750” (Bộ sưu tập cấp độ 1). Mỗi bộ sưu tập như vậy đòi hỏi phải sử dụng ít nhất hai hạn mức thả thưởng từ các tài khoản khác, mỗi tài khoản đó phải đã vượt qua mốc $5.00 và mỗi tài khoản đều sở hữu trò chơi. Một con số trang trí ở đầu một hồ sơ được xây dựng dựa trên ít nhất 25,500 số lượng phần thưởng đã sử dụng nằm bên dưới nó. Valve sẽ không để thua lỗ trong giao dịch đó. Công ty Quản lý Đầu tưValve là đối tác giao dịch của từng phần trong giao dịch đó.\n\n04 — Các số liệu thống kê\nĐiều khoản này không mô tả nghề nông một cách mơ hồ. Nó liệt kê cụ thể các hoạt động đó.\n\n§ “4.C” không phải là một câu quy định chung nhằm chống lại các bot. Các ví dụ được liệt kê trong đó nêu ra, lần lượt, hai thứ mà một trang trại thẻ sản xuất ra.\n\n\"Bạn không được sử dụng bất kỳ hình thức kịch bản, bot, macro hoặc các hệ thống khác không do con người điều khiển ('Tự động hóa') để tương tác với Nội dung và Dịch vụ trên Steam dưới bất kỳ hình thức nào, bao gồm nhưng không giới hạn ở:\n\nTự động hóa quy trình tạo tài khoản Steam,\nLàm giả số liệu thống kê trong trò chơi (e.g, số trận thắng hoặc thua được thổi phồng, XP, thời gian chơi),\nKiếm được phần thưởng hoặc tiến bộ mà không có sự đóng góp thực sự từ người dùng,\n“Tham gia vào các hệ thống đánh giá (như đánh giá ngang hàng hoặc ‘Overwatch’) thông qua các phương thức tự động, bao gồm việc tác động đến kết quả hoặc báo cáo người dùng bằng các hành động được lập trình sẵn thay vì dựa trên phán đoán có căn cứ.”\n— Steam Thỏa thuận người đăng ký § 4.C ↗ đã lưu trữ 2026-09-24 ↗ · Trích dẫn nguyên văn từ 2026-09-22\n\"…giờ chơi\"\n\nThời gian nhàn rỗi không phải là thời gian ảo. Phần Câu hỏi thường gặp (FAQ) của ASF đã trả lời thẳng thắn câu hỏi này — \"Tại sao thời gian chơi của các trò chơi được farm qua ASF lại không tăng?\" — với: \"Đúng vậy, nhưng không phải theo thời gian thực. Steam ghi lại thời gian chơi của bạn theo các khoảng thời gian cố định và lên lịch cập nhật cho dữ liệu đó… thông thường, dữ liệu sẽ được cập nhật khoảng 30 phút một lần.\"\n\nSố giờ đó được ghi nhận trong hồ sơ của Valve, trên các trang sản phẩm của Valve, và trong số liệu về số người chơi đồng thời mà Valve tự công bố Steam Biểu đồ ↗ đã lưu trữ 2026-09-23 ↗. Trong các số liệu đó, tài khoản không hoạt động không thể phân biệt được với tài khoản đang chơi. Các con số về mức độ tương tác mà nền tảng công bố ra bên ngoài được tính toán dựa trên tổng số người dùng, trong đó – theo quy định của chính nền tảng – bao gồm cả những tài khoản không đang chơi.\n\n\"…nếu thiếu ý kiến đóng góp thực sự từ người dùng\"\n\nĐó là định nghĩa về việc thả thẻ không hoạt động, do Valve biên soạn. Đây cũng là định nghĩa về Cấp độ “Steam”, huy hiệu, điều kiện nhận gói thẻ bổ sung và điểm kinh nghiệm (XP) trong hồ sơ đi kèm — phần Câu hỏi thường gặp (FAQ) của ASF đã xác nhận công cụ này \"vẫn giữ được khả năng nhận các gói thẻ bổ sung\", bởi vì nó đăng nhập theo cách tương tự như ứng dụng chính thức.\n\nVì vậy, hệ thống phần thưởng và hành vi bị cấm là một cơ chế được nhìn nhận từ hai khía cạnh khác nhau. Valve đã thiết kế phần thưởng được tạo ra dựa trên thời gian chứ không phải dựa trên kỹ năng, sau đó đưa ra một điều khoản cấm việc tạo ra phần thưởng bằng bất kỳ cách nào khác ngoài việc một người dành thời gian đó.\n\n05 — Bẫy dành cho mục đích thương mại\nMỗi lần ra khỏi khu vực thẻ được cấp phép đều là hành vi bị giấy phép cấm — và Valve thu phí tại cửa ra vào\n\nĐây là vấn đề không thể giải quyết bằng cách “khai thác một cách có trách nhiệm”. Giấy phép này chỉ dành cho mục đích sử dụng cá nhân, phi thương mại, và một thẻ chỉ thực sự đáng để khai thác khi nó không còn mang tính chất cá nhân nữa.\n\n§ 2.A — giấy phép\n\n\"Valve\" tại đây cấp cho bạn, và bạn chấp nhận, giấy phép và quyền không độc quyền để sử dụng Nội dung và Dịch vụ cho mục đích của bạn sử dụng cá nhân, phi thương mại (trừ trường hợp việc sử dụng cho mục đích thương mại được cho phép rõ ràng trong tài liệu này hoặc trong Điều khoản Đăng ký áp dụng).\"\n\n§ 2.G — các hạn chế\n\n\"Bạn không có quyền: … (iii) lợi dụng Nội dung và Dịch vụ hoặc bất kỳ phần nào của chúng cho bất kỳ mục đích thương mại nào, trừ khi được cho phép rõ ràng tại các điều khoản khác trong Thỏa thuận này (bao gồm bất kỳ Điều khoản Đăng ký hoặc Quy tắc Sử dụng nào).\"\n\n§ 3.D — mức phí\n\n\"Valve có thể thu phí đối với các giao dịch trên Nền tảng đăng ký. \"Mọi khoản phí sẽ được thông báo cho quý khách trước khi giao dịch được hoàn tất.\"\n\nĐọc cả ba điều này cùng nhau thì vị trí đó sẽ bị đóng lại\n\nMột lá bài được giữ lại thì không có giá trị gì đối với một trang trại. Một lá bài được bán, trao đổi hoặc nghiền thành đá quý đã được sử dụng để tạo ra giá trị — và Công ty Trò chơi Di động (Valve) đã nêu rõ điều này trong thư cảnh báo của mình: người điều hành các bot trên 170 đã được thông báo rằng tài khoản \"đã được sử dụng để thu thập trái phép các thẻ sưu tập trên trang Steam, cũng như các hoạt động liên quan và không chỉ giới hạn ở các hoạt động thương mại.\" Trong trường hợp đó, các thẻ đã được đưa ra thị trường. Giao dịch đã được hoàn tất. Phí đã được thu. Lệnh cấm được ban hành sau đó.\n\nPhí tại cửa đó không phải là 15%.. Trên thẻ được khai thác, mức phí này lên tới hai phần ba.\n\n§ Các khu bảo tồn thuộc Hiệp hội Bảo tồn Thiên nhiên và Động vật Hoang dã (3.D) \"một khoản phí\". Trên các thẻ mà một trang trại thực sự sản xuất ra, khoản phí đó hoàn toàn khác xa so với mức được quảng cáo ~15%. Chợ Cộng đồng thu một 5% Steam phí giao dịch và phí trò chơi “10%”, mỗi loại đều có mức tối thiểu là $0.01 (Câu hỏi thường gặp về Chợ Cộng đồng của Valve). Trên một tấm thẻ được rao bán với giá một xu, những tầng đó là Giá: người mua phải trả ba xu, trong đó hai xu là phí. Quy tắc làm tròn xuống biến mức giá niêm yết “15%” thành một khoản thuế thực tế tăng lên đến 66.7% chính xác là mức giá hiện tại của thị trường thẻ — chỉ vài xu một chiếc.\n\nPhí thực tế áp dụng cho giao dịch trên Thị trường Cộng đồng, tính theo giá chào bán của người bán\n\n5% Steam + 10% game, mỗi lá có giá tối thiểu là $0.01.. Dải màu xám là khoảng giá thực tế mà các lá bài được giao dịch — khoảng $0.03–$0.05 mỗi lá.\n\n0%\n10%\n20%\n30%\n40%\n50%\n60%\n70%\ncards\n$0.01\n$0.10\n$0.20\n$0.30\n$0.40\n$0.50\n66.7%\nNgười bán muốn\tSteam 5% (tối thiểu $0.01)\tTrò chơi “10%” (mức cược tối thiểu $0.01)\tNgười mua thanh toán\tPhí tổng hợp\n$0.01\t$0.01\t$0.01\t$0.03\t66.7%\n$0.03\t$0.01\t$0.01\t$0.05\t40.0%\n$0.05\t$0.01\t$0.01\t$0.07\t28.6%\n$0.08\t$0.01\t$0.01\t$0.10\t20.0%\n$1.00\t$0.05\t$0.10\t$1.15\t13.0%\n\nPhí trò chơi “10%” được chuyển cho ứng dụng đã phát hành thẻ; phần “5%” thuộc về Valve, còn đối với các tựa game và vật phẩm cơ bản của Valve, toàn bộ phí sẽ thuộc về Valve. Dù theo cách nào thì người chơi cũng phải chi tiền — bán một thẻ giá ba xu sẽ thu về một xu và mất hai xu. Nhân con số đó với hàng trăm nghìn giao dịch bán thẻ có giá dưới 5 xu mà một trang trại tạo ra và \"phí mà Valve có thể thu\" đó là mô hình kinh doanh, chứ không phải một chú thích. Nguồn: Steam Câu hỏi thường gặp về Chợ cộng đồng — Phí ↗ đã lưu trữ 2026-09-21 ↗, xem 2026-09-22; đường cong này được tính theo phương pháp số học dựa trên hai mức lãi suất đã công bố và các mức sàn $0.01.\n\nKhông có cách thiết lập nào của công cụ này có thể tránh khỏi điều này. Công cụ này có thể được vận hành bởi một người, trên một tài khoản, với sự kiềm chế tuyệt đối — và ngay khi người đó bán đi một lá bài được “farm” để lấy tiền trong ví, họ sẽ phải đối mặt với cùng một điều khoản tại § 2.G như người vận hành mười nghìn tài khoản. Valve Do đó, đã dành sẵn một điều khoản vi phạm mà họ có thể áp dụng đối với hầu như mọi người bán thẻ trên chính thị trường của mình, nhưng lại từ chối áp dụng điều khoản đó đối với hầu như tất cả họ. Một quy tắc được áp dụng với mức độ như vậy thì không phải là quy tắc. Đó chỉ là một lựa chọn. Câu hỏi mà triển lãm này đặt ra không phải là tại sao những người “trồng thẻ” lại được dung thứ; mà là tại sao cùng một biện pháp lại được áp dụng đối với một người dùng đơn lẻ bán thẻ, trong khi nền kinh tế thẻ thương mại mà những thẻ đó nuôi dưỡng — các dịch vụ giao dịch, bot tăng cấp, những người bán số lượng lớn — vẫn hoạt động công khai, với một trong những nhóm lớn nhất của nó được điều hành bởi một nhân viên của Valve (§ 08). Quy định này chỉ được áp dụng đối với người sở hữu nhỏ lẻ và được miễn trừ cho các hệ thống tự động.\n\n06 — Hồ sơ thi hành\nKhông có thông báo trước, diễn ra từng đợt, và lan truyền qua số điện thoại\n\nValve đã đưa điều khoản về việc cắt điện không báo trước vào chính bản thỏa thuận, ngay sau điều khoản về tự động hóa.\n\n\"Valve có thể hạn chế hoặc chấm dứt (các) Tài khoản của bạn hoặc một Gói đăng ký cụ thể do bất kỳ hành vi hoặc hoạt động nào vi phạm pháp luật, cấu thành hành vi gian lận hoặc sử dụng phần mềm tự động, hoặc vi phạm Quy tắc Ứng xử Trực tuyến của Steam.\" Bạn xác nhận rằng Valve không có nghĩa vụ phải thông báo cho bạn trước khi chấm dứt (các) Gói đăng ký và/hoặc Tài khoản của bạn.\"\n\n— Steam Thỏa thuận người đăng ký § 4.D ↗ đã lưu trữ 2026-09-24 ↗ · Đã xác minh nguyên văn 2026-09-22\n\n1,000+ bot · bị cấm giao dịch. \"Có vẻ như tài khoản này đã được sử dụng để quản lý một mạng lưới các tài khoản bot. Việc sử dụng bot vi phạm Thỏa thuận người dùng của Steam.\"\n\n170+ bot · bị cấm vĩnh viễn, chương trình giảm giá mùa đông “2017”. \"Tài khoản này đã được sử dụng để thu thập trái phép các thẻ sưu tập trên Steam, cũng như các hoạt động liên quan và không chỉ giới hạn ở các hoạt động thương mại. Tài khoản này đã bị khóa vĩnh viễn và bộ phận Hỗ trợ của Steam không thể cung cấp thêm sự hỗ trợ nào về vấn đề này.\"\n\n120+ bot · bị cấm vĩnh viễn. \"Tài khoản này cùng với các tài khoản khác đã được sử dụng để tấn công làm quá tải hạ tầng mạng của chúng tôi, đây là hành vi vi phạm Quy tắc ứng xử trực tuyến của Hiệp hội Bóng chày Quốc gia (Steam).\"\n\n— Các tin nhắn hỗ trợ từ Steam được trích dẫn trong phần Câu hỏi thường gặp (FAQ) của ArchiSteamFarm, mục “Có ai bị cấm vì lý do đó không?”. Nguồn ↗ · Đã xác minh nguyên văn 2026-09-22\nTrường hợp 4 — Tháng 6 năm 2025, Các lệnh cấm của VAC đối với CS2 bị tạm ngưng\n\nMột sự kiện xảy ra muộn hơn so với ba sự kiện nêu trên đã được ghi lại trong hệ thống theo dõi của chính dự án: các tài khoản chỉ để trò chơi Counter-Strike 2 chạy ngầm thông qua công cụ này đã nhận được Các lệnh cấm của VAC — loại chống gian lận, chứ không phải loại hành chính. Quan điểm của người quản trị là việc để máy chạy không tải không thể gây ra lỗi đó, vì nó \"Chỉ đơn thuần là thông báo cho Steam rằng chúng tôi đang chơi trò chơi đó mà thôi.\" Nguyên nhân vẫn còn là chủ đề tranh cãi. Tuy nhiên, việc các tài khoản này bị khóa thì không còn gì để bàn cãi.\n\n— Chủ đề thảo luận ArchiSteamFarm số3440, đã được mở 26 Tháng 6 năm 2025 ↗ · Đọc bài viết “2026-09-22”\n\nCách một tài khoản chính bị xóa\n\nTrong cùng một chuỗi bình luận, một thành viên tham gia dự án đã giải thích quy tắc xử lý: các tài khoản có thể bị cấm \"theo chuỗi\", nếu họ đang sử dụng cùng một số điện thoại — \"Đó có thể chỉ là một lệnh cấm VAC, nhưng lại lan rộng sang các tài khoản 'sạch' có liên quan đến tài khoản bị cấm.\"\n\nSteam Guard yêu cầu số điện thoại. Các “trang trại” được xây dựng dựa trên số điện thoại của người vận hành. Do đó, việc thực thi không chỉ dừng lại ở các tài khoản dùng một lần: nó sẽ lần theo mã định danh chung để truy vết đến tài khoản chứa thư viện, danh sách bạn bè và kho đồ. Đó là cơ chế mà một cộng tác viên dự án mô tả về cách một hành động duy nhất có thể xóa tài khoản chính của người điều hành cùng với trang trại — và đó là lý do tại sao tổn thất trong một đợt thực thi không được đo lường bằng số lượng tài khoản $5. (Được mô tả bởi một cộng tác viên dự án trong cuộc thảo luận #3440 trên ASF GitHub; không có xác nhận chính thức nào từ Valve hay tiền lệ chính thức nào được ghi lại.)\n\nCùng một đoạn văn, cách nhau năm năm, từ ba đại lý khác nhau\n\nĐiều khoản quy định việc canh tác là hành vi vi phạm — tức việc sử dụng giấy phép cá nhân, phi thương mại vào mục đích thương mại — không chỉ áp dụng riêng cho các trang trại. Đây là lý do thường được Steam đưa ra khi đóng tài khoản vì hoạt động giao dịch, và lý do này được gửi dưới dạng mẫu có sẵn. Dưới đây là ba trường hợp, được chính những người nhận thông báo này công bố, cách nhau năm năm, từ ba đại diện được nêu tên khác nhau.\n\nThông báo từ bộ phận hỗ trợ Steam vào ngày 29 lúc 7:56chiều\n\n\"The account you are writing in for has been locked for violating the terms of the Steam Subscriber Agreement. The account has been identified as being used for commercial purposes based on trading, community reports, and other factors.\n\nThis lock is permanent and Steam Support cannot help you further with this.\n\nBecause we have provided all the information we have I am closing this help request. Please note you will not receive further replies regarding this issue.\n\nRegards,\nHal\"\n\nYêu cầu trợ giúp này đã được đóng lại.\n29 Tháng 9 năm 2020. Được đăng bởi người nhận kèm theo bình luận \"Vĩnh biệt RIP Trading.\" — @gergelyszabo94 ↗\nThông báo từ bộ phận hỗ trợ Steam vào ngày 12 tháng 7 lúc 22:41\n\n\"The account you are writing in for has been locked for violating the terms of the Steam Subscriber Agreement. The account has been identified as being used for commercial purposes based on trading, community reports, and other factors.\n\nThis lock is permanent and Steam Support cannot help you further with this.\n\nBecause we have provided all the information we have I am closing this help request. Please note that future help requests submitted regarding the account lock may be closed without a reply.\n\nSteam Support\nVido\"\n\nYêu cầu hỗ trợ này đã được đóng lại.\n12 Tháng 7 năm 2024, Giao diện tiếng Bồ Đào Nha. Người nhận là một game thủ CS2 chuyên nghiệp: \"Tôi đã liên hệ với bộ phận hỗ trợ của Steam nhưng chỉ nhận được các phản hồi tự động… không thể chơi Faceit và cũng không thể tham gia các trận đấu chuyên nghiệp.\" — @prcs25 ↗ đã lưu trữ 2024-07-15 ↗\nĐược trích dẫn bởi người nhận, r/steamsupport\n\n\"Hello, The account you are writing in for has been locked for violating the terms of the Steam Subscriber Agreement. The account has been identified as being used for commercial purposes based on trading, community reports, and other factors.\n\nThis lock is permanent and Steam Support cannot help you further with this.\n\nBecause we have provided all the information we have I am closing this help request. Please note that future help requests submitted regarding the account lock may be closed without a reply.\n\nSteam Support\nSally\"\n\nĐã nhận được ba lần, theo ba yêu cầu riêng biệt.\n29 Tháng 3 năm 2025. Người viết không phải đang khiếu nại về việc tài khoản bị khóa — tài khoản của họ đã bị đánh cắp cùng với địa chỉ email và họ đang yêu cầu được cấp quyền truy cập: \"Tôi không hỏi về lệnh cấm và cũng không phản đối nó, tôi chỉ muốn truy cập vào tài khoản Steam của mình… Valve đã gửi cho tôi chính xác câu trả lời này, sao chép và dán vào mọi yêu cầu, rồi đóng yêu cầu đó lại.\" — r/steamsupport ↗, được lưu trữ trong tập dữ liệu đơn khiếu nại của chính cuộc điều tra này\n\nTừng từ, từng dấu phẩy, trải dài suốt 55 tháng, qua ba đại lý và hai ngôn ngữ giao diện. Sửa đổi duy nhất trong toàn bộ nội dung là việc điều chỉnh câu cuối cùng từ “2020” thành “2024,” từ \"Bạn sẽ không nhận được thêm bất kỳ phản hồi nào nữa\" đến \"Các yêu cầu hỗ trợ trong tương lai… có thể bị đóng mà không có phản hồi.\" Dù quá trình nào đã dẫn đến những quyết định này đi chăng nữa, thì bức thư này cũng không phải là tài liệu ghi lại quá trình đó. Các lý do được nêu ra là “hoạt động giao dịch, báo cáo từ cộng đồng và các yếu tố khác” — một danh mục, một báo cáo không rõ nguồn gốc và phần còn lại không được nêu tên.\n\nNăm trường hợp khác, được thu thập theo cách tương tự. Ba trường hợp đầu tiên thuộc cùng một loại và có cùng kết quả; hai trường hợp cuối cùng là cùng một quy tắc nhưng được diễn đạt bằng cùng một ngôn từ:\n\nNgày\tTài khoản đó đã làm gì\tChuyện gì đã xảy ra\tNguồn\n04.12.2021\tBuying and selling on Buff — \"I've done nothing else than some buying and selling on buff aka P2P trading\"\tCommunity ban: no market, no trading, expensive inventory frozen\tr/csgomarketforum ↗ archived 2025-03-27 ↗\n06.12.2021\tOne-way P2P trades through Buff and Bitskins for loadouts and trade-ups\tPermanent commercial-use lock plus community lock: \"stuck in a pseudo invisible mode… My profile is also stuck on private\"\tr/GlobalOffensiveTrade ↗ archived 2021-12-06 ↗\n20.12.2024\tAccount held since 2017, thousands of hours; trades on community marketplaces for themed loadouts and trade-ups\tPermanent lock with community lock, no prior warning or strike; support \"say their decision is final\", replies are automated\tr/csgomarketforum ↗ archived 2025-06-27 ↗\n23.12.2024\tReturning user adds wallet funds after a year away, over a VPN used \"only for general internet security\"\tPermanent community ban with no reason given at all: \"the ban is permanent and they cannot provide further information and that further tickets may be closed without response.\" 196 upvotes, 340 replies\tr/steamsupport ↗\n04.08.2026\tYears of purchases from Iran; the writer states they never posted, never used the Market, never used the forums\tCommunity access locked until 2038 over \"sanctioned regions\"; ticket closed by an agent named Azul. The same account's refund from the same Iranian IP had been approved a year earlier. The library and the money stay with Valve.\tr/pcgaming ↗\n\nDòng cuối cùng có quy tắc khác biệt so với các dòng còn lại — tuân thủ các biện pháp trừng phạt, chứ không phải mục đích thương mại — và nó được đưa vào vì cấu trúc của câu trả lời hoàn toàn giống nhau: một danh mục, không có bằng chứng, không có quyền kháng cáo, phiếu yêu cầu đã được đóng. Điều này cũng đặt ra một câu hỏi mà các trường hợp khác không có. Nếu việc cung cấp dịch vụ cho tài khoản đó là trái pháp luật, thì việc chấp nhận các khoản thanh toán trong nhiều năm qua cũng là trái pháp luật. Một trong hai quan điểm đó chắc chắn là sai, và chỉ có một trong số đó mới khiến khách hàng phải chịu thiệt hại.\n\nTất cả tám bài viết này đều được đọc trên 2026-09-22 — các chuỗi bài viết “2021” và “December-2024” thông qua các bản chụp nhanh từ Internet Archive, còn phần còn lại thông qua giao diện công khai của Reddit, vì Reddit đã từ chối các yêu cầu trực tiếp từ máy chủ thu thập dữ liệu. Hai lá thư 2020 và 2024 được sao chép từ các ảnh chụp màn hình đính kèm trong các bài đăng gốc, hiện vẫn còn tồn tại. Cuộc điều tra này không cáo buộc bất kỳ tài khoản nào trong số này là vô tội hay có tội về bất kỳ điều gì — đó chính xác là vấn đề ở đây. Không một độc giả nào, cũng như không một cơ quan quản lý nào, có thể biết được điều đó qua bức thư.\n\nGhi chú về nguồn cung — tổn thất ở cấp độ nhà khai thác\n\nCác nhà khai thác được khảo sát trong cuộc điều tra này cho biết họ bị lỗ ở mức khoảng từ năm nghìn đến mười nghìn tài khoản mỗi tài khoản trong các đợt thực thi riêng lẻ, với việc kiểm tra các tài khoản chính được tiến hành song song với việc kiểm tra trang trại. Cuộc khảo sát đó được ghi nhận tại đây dưới dạng báo cáo từ chính bên thực hiện, chứ không phải là kết luận. Tham số này không có kích thước mẫu được công bố, không có ngày thu thập cố định, không yêu cầu xác minh theo từng tài khoản, và không có số liệu nào khác trên trang này phụ thuộc vào nó; hai hàng trong phần “02” dựa trên tham số này đã được đánh dấu rõ ràng.\n\nĐiều này được nêu rõ chứ không phải bỏ qua vì hai lý do. Cơ chế cấm theo chuỗi nêu trên chính là lời giải thích có căn cứ cho chính mô hình đó. Và cơ quan quản lý có thể yêu cầu từ Valve bản ghi duy nhất có thể làm sáng tỏ vấn đề này: có bao nhiêu tài khoản đã bị xử lý do tự động hóa, trong các đợt nào, và mỗi tài khoản đó đã chi tiêu bao nhiêu tại cửa hàng trước khi bị đóng. Cho đến khi bản ghi đó tồn tại, con số này vẫn giữ nguyên — được báo cáo, được quy cho nguyên nhân cụ thể nhưng chưa được chứng minh.\n\n07 — Sự bất đối xứng\nHai bên của cùng một chiếc bàn\n\nHãy so sánh tiêu chuẩn chứng minh đó với tiêu chuẩn mà Valve đã áp dụng cho hoạt động hỗ trợ của chính họ. Cột bên phải là sổ đăng ký sự cố của chính hồ sơ này, được sao chép lại kèm theo những lưu ý được ghi chú trong đó.\n\nMột khách hàng, để giao dịch\n\nTám trường hợp đã được ghi nhận, 2020–2026\n\nHành vi\nMua bán hàng hóa trên các sàn thương mại điện tử của bên thứ ba; trong một trường hợp, không có hành vi nào cả — tài khoản đó đã bị đánh cắp.\nBằng chứng được trình bày\nKhông có. \"Dựa trên hoạt động giao dịch, báo cáo từ cộng đồng và các yếu tố khác.\"\nThông báo\nKhông có. Công ty Bảo hiểm Nhân thọValve đã quy định điều này tại Điều 4.D: \"Valve không có nghĩa vụ phải thông báo cho bạn trước khi chấm dứt hợp đồng.\"\nKháng cáo\n\"Khóa này là vĩnh viễn và bộ phận Hỗ trợ của Steam không thể hỗ trợ bạn thêm về vấn đề này nữa.\"\nVé\nĐã đóng sau phản hồi đầu tiên. Các yêu cầu tiếp theo \"có thể bị đóng mà không có phản hồi.\"\nPhạm vi\nHồ sơ, danh sách bạn bè, trò chuyện, Cửa hàng, kho đồ và mọi vật phẩm được mua bằng tiền thật.\nThời lượng\nVĩnh viễn.\nMột đội bot tự động, dành cho khối lượng lớn\n\n694,673 các bộ sản phẩm đầy đủ trong kho công khai trên các bot củ91\n\nHành vi\nChạy các tập lệnh tự động không giao diện người dùng trên hàng nghìn tài khoản cùng lúc để làm không hoạt động các thẻ, tạo hàng loạt huy hiệu và giao dịch các bộ thẻ trên quy mô công nghiệp.\nBằng chứng được trình bày\nCác danh mục bot được công khai (steam.supply, SteamLvlUp) và các nhóm công khai có hàng triệu thành viên.\nThông báo\nHoàn toàn không can thiệp. 88.97% không bị cấm dưới bất kỳ hình thức nào; 99.8% các lệnh cấm còn lại chỉ mang tính hình thức.\nKháng cáo\nKhông cần thiết. Các đội tàu hoạt động liên tục trong suốt vòng đời kéo dài nhiều năm mà không bị gián đoạn.\nVé\n—\nPhạm vi\nTrao đổi tài sản không giới hạn, nâng cấp huy hiệu và tính thanh khoản trên thị trường.\nSố tiền quyên góp cho tổ chức “Valve”\n$26.8M+ trong mức chi tiêu tối thiểu tại cửa hàng (5.00/lần vào cổng cho mỗi tài khoản) cộng với các khoản chiết khấu từ các giao dịch tại Chợ Cộng đồng 15%.\nCâu hỏi đặt ra ở đây, nói một cách đơn giản là\n\nMột khách hàng cá nhân thực hiện giao dịch thẻ hoặc vật phẩm theo cách thủ công sẽ phải đối mặt với lệnh cấm vĩnh viễn, không thể kháng cáo theo Điều 4.C (tự động hóa) hoặc Điều 2.G (sử dụng vì mục đích thương mại). Một hệ thống khai thác tự động vận hành các bot không cần người điều khiển trên hàng nghìn tài khoản đang hoạt động công khai với tỷ lệ tài khoản không bị xử lý (88.97%) vẫn được giữ nguyên. Valve là người được hưởng lợi từ cả hai.\n\nSự bất đối xứng này mang tính kinh tế: các nhà giao dịch cá nhân thu lợi từ nền tảng, trong khi các đội thẻ tự động bơm hàng triệu vào cổng chi tiêu tại cửa hàng của Valve (5.00 USD mỗi tài khoản) và thúc đẩy phí giao dịch trên mỗi lần bán lại. Việc thực thi không tuân theo quy định bằng văn bản; nó tuân theo mô hình doanh thu.\n\n08 — Quản trị\nAi là người điều tiết nền kinh tế thẻ?\n\nKết luận lặp đi lặp lại trong hồ sơ này — rằng lớp bên thứ ba xung quanh Steam được điều hành bởi chính những người bên trong Steam — cũng đúng trong nền kinh tế thẻ, và điều này dẫn đến một kết luận cụ thể: không ai độc lập có thể đánh giá được hiệu quả thực sự của các biện pháp thực thi của Valve, bởi vì bên có khả năng đánh giá lại nằm ngay bên trong lớp đó. Mọi thông tin dưới đây đều được trích từ các trang nhóm và hồ sơ công khai của Valve trên 2026-09-22 và bất kỳ ai cũng có thể truy cập lại thông qua trình duyệt.\n\nMột nhân viên của Valve điều hành nhóm trao đổi thẻ lớn nhất Valve nhân viên\n\nCardTrades ↗ trong phần tiêu đề của chính nó, nó tự mô tả mình là \"Nhóm chính thức của sự kiện trao đổi thẻ 'Steam'\" và mang theo 97,114 thành viên. Danh sách các người điều hành — tức là các tài khoản nắm quyền kiểm soát nhóm đó — bao gồm Mickmane, Hạ sĩ Fopper và afarnsworth ↗.\n\nHồ sơ cuối cùng đó được chính mã đánh dấu trên trang web của “Valve” gắn nhãn là nhân viên của Valve — trang này hiển thị class=\"profile_header_valve_employee\" — cho biết vị trí của nó là Bellevue, Washington, và thuộc về Valve, Steam và Steam Nhóm Thẻ Sưu Tập các nhóm. SteamID64 76561197960434622, thành viên từ ngày 12 tháng 9 năm 2003.\n\nQuan sát này mang tính cấu trúc, không phải mang tính cá nhân, và nó là không một điểm cần lưu ý — người điều hành một nhóm trao đổi thẻ không sử dụng bot, và không có gì ở đây cho thấy điều ngược lại. Vấn đề nằm ở điều khoản trong phần 07. Steam Card Exchange là một dịch vụ thẻ thương mại của bên thứ ba; việc trao đổi thẻ thông qua các dịch vụ của bên thứ ba chính là hành vi mà Valve sẽ khóa vĩnh viễn các tài khoản thông thường theo \"được sử dụng cho mục đích thương mại dựa trên hoạt động giao dịch, báo cáo từ cộng đồng và các yếu tố khác.\" Một nhân viên của Valve đang đảm nhận vai trò điều hành viên được chỉ định trong nhóm cộng đồng chính thức của dịch vụ này, với 97.000 thành viên.\n\nỞ đây không có bất kỳ cáo buộc nào về hành vi sai trái đối với bất kỳ cá nhân nào, và không có kết luận nào được đưa ra về những gì vai trò đó bao gồm. Sự bất đối xứng chính là phát hiện: khi một tài khoản thông thường liên quan đến dịch vụ thẻ hoặc giao diện của bên thứ ba, kết quả là vé hỗ trợ bị đóng và tài khoản bị khóa vĩnh viễn mà không có bằng chứng nào được trình bày; khi dịch vụ đó là dịch vụ này, một nhân viên của Valve có tên trong danh sách người điều hành và thỏa thuận này được hiển thị trên chính trang Valve do chính họ công bố. Câu hỏi được đặt ra cũng giống như câu hỏi được đặt ra ở mọi nơi khác trong hồ sơ này: hãy xuất trình văn bản ủy quyền, nếu có — và nếu không cần, hãy nói rõ bằng văn bản, bởi vì tám người trong mục 06 đã được thông báo ngược lại.\n\nTầng danh sách cấm và ai là người quản lý nó Người điều hành tình nguyệnDịch vụ của bên thứ ba\n\nNhóm của Steambans.com (bản lưu trữ) ↗ (trực tiếp ↗ đã lưu trữ 2025-12-03 ↗) ghi lại nguồn gốc của mình trong phần mô tả nhóm được lưu giữ: \"Nhóm cộng đồng chính thức của Steambans.com Steam. SteamBans.com là một dịch vụ hoàn toàn mới dựa trên một ý tưởng cũ. Các danh sách cấm toàn cầu đã hoạt động trong nhiều năm trên chương trình WONID cũ của VALVe. Khi sự thay đổi chuyển sang STEAMID, việc chúng tôi phát triển một dịch vụ được thiết kế riêng cho hệ thống mới này là điều tất yếu. Tuy nhiên, chúng tôi còn muốn làm được nhiều hơn thế. *. Trang lưu trữ dành cho Steambans, dịch vụ đã ngừng hoạt động tại 2013.\" Danh sách các quản trị viên bao gồm thiết bị null và killahinstinct_ ↗.\n\nTài khoản quản trị viên đó là không một nhân viên của Valve — người này không mang danh nghĩa nhân viên. Đây là một tình nguyện viên có vị thế đặc biệt cao: một thành viên của Người điều hành cộng đồng (Các thành viên của 414, được mô tả là một nhóm \"được tạo bởi các điều phối viên cộng đồng của Steam\"), của Điều phối viên Wiki, của Steam Chợ cộng đồng, và các nhóm thuộc chương trình “Valve” cùng các nhóm thử nghiệm trước khi phát hành, bao gồm Valve Pipeline, Steam Phiên bản Beta dành cho khách hàng, Phiên bản thử nghiệm xác thực trên thiết bị di động, Phiên bản Beta mới của cộng đồng “Steam”, Steam Phòng thí nghiệm, Steamworks và Báo cáo các URL lừa đảo. SteamID64 76561197960794555.\n\nNgoài ra, trong vòng tròn đó và hiển thị Steambans trực tiếp trong danh sách thành viên nhóm công khai của mình: msart ↗ (Danh sách các nhóm ↗), SteamID64 76561197977933359, trong phần giới thiệu của trang này có ghi như sau: \"Tôi điều hành trang web steamid.uk cùng nhiều trang web khác liên quan đến Steam và các chủ đề khác\", và là người điều hành một mạng lưới gồm mười sáu nhóm liên kết với nhau — SteamIDcouk (nhóm chính \"Trang web Sid\"), SidAdmins, SidBans, steamideu, Steam3ID, s-id và SArchive trong số đó.\n\nsteamid.uk đặt tên chính là con số đó. Phần Câu hỏi thường gặp (FAQ) của nó: \"Ai là người đã tạo ra SteamID? Trang web SteamID, cơ sở hạ tầng mạng và các hệ thống bảo mật đều do 76561197977933359. quản lý.\" Hai câu trả lời tiếp theo ở phía dưới đã nêu rõ nguồn gốc của dữ liệu: \"SteamID chủ yếu sử dụng trang web Steam API để thu thập dữ liệu.\" Trang này mô tả nhiều máy chủ chuyên dụng tại các nhà cung cấp dịch vụ khác nhau, các máy chủ phát triển, lưu trữ và tìm kiếm văn bản đặt tại các địa điểm khác, cùng với một cơ sở sao lưu riêng biệt.\n\nĐã được xác minh thông qua các tài liệu lưu trữ trên Internet Archive: Ảnh chụp nhanh nhóm Steambans về “3” ngày 12 tháng 2025 ↗, cái Tóm tắt hồ sơ người điều hành của 14 tháng 9 năm 2024 ↗, và steamid.uk Tổng quan về các câu hỏi thường gặp (FAQ) của 1 Tháng 4 năm 2026 ↗, dữ liệu khớp được đọc trực tiếp từ 2026-09-22.\n\nĐiều này dẫn đến điều gì, và điều gì thì không\n\nDanh sách cấm, xác định SteamID và giao dịch thẻ là ba dịch vụ quyết định ai là người đáng tin cậy, ai có thể được xác định danh tính, và một vật phẩm có giá trị bao nhiêu. Cả ba dịch vụ này đều không do Valve vận hành. Trên mỗi tàu đó, những người điều khiển đều đến từ bên trong quỹ đạo củValve: một nhân viên của Valve đã được gắn cờ trong danh sách điều hành viên của nhóm chính thức thuộc dịch vụ thẻ; một điều hành viên lâu năm của cộng đồng Valve, người có quyền truy cập chương trình trước khi phát hành và quản lý nhóm danh sách cấm; dịch vụ xác định danh tính do một cá nhân điều hành, người này cũng thuộc cùng một nhóm. Ba dịch vụ, ba mặt trận kiểm soát, ba người mà Valve đã công nhận từ trước.\n\nViệc tham gia nhóm không phải là quan hệ lao động, và những điều này không phải là lời buộc tội. Đó là một thực tế về quản trị, và đó cũng chính là lý do dẫn đến lập luận bào chữa thông thường — Đó là các bên thứ ba, chúng tôi không thể kiểm soát họ — cần phải được kiểm chứng chứ không thể chấp nhận một cách mù quáng. Những người nắm quyền điều hành không phải là những người xa lạ với “Valve”. “Valve” là bên duy nhất có thể xác định xem họ đã yêu cầu gì từ những người này (nếu có); không ai bên ngoài có thể tìm hiểu được điều đó.\n\nKhông ai được tính. Đó là kết luận.\n\nKhông gian ID của Steam là một dải số nguyên liền kề. Việc quét qua dải này và báo cáo số lượng tài khoản bị cấm, số lượng tài khoản bị hạn chế, cũng như lượng hàng tồn kho bị ảnh hưởng bởi lệnh cấm giao dịch không phải là một chương trình nghiên cứu — đó chỉ là một vòng lặp và một khóa API. Valve tự cung cấp khóa đó tại steamcommunity.com/dev/apikey. Thế nhưng Không có tổ chức độc lập nào công bố kết quả điều tra dân số đó. Không phải cơ quan quản lý, không phải nhà báo, không phải học giả, cũng không phải tổ chức người tiêu dùng. Những số liệu công khai duy nhất về quy mô việc thực thi pháp luật trên trang Steam chính là những số liệu mà Valve chọn đề cập đến.\n\nKhả năng này không phải là thiếu. Mà là đang được giữ lại. Dịch vụ chuyên giải quyết và lập chỉ mục không gian ID trên quy mô lớn — steamid.uk — đã nêu rõ trong phần Câu hỏi thường gặp (FAQ) của mình rằng nó \"chủ yếu sử dụng trang web Steam API để thu thập dữ liệu\" và vận hành hệ thống này trên nhiều máy chủ chuyên dụng, các thiết bị lưu trữ ngoài cơ sở, các máy tìm kiếm văn bản cùng một cơ sở sao lưu riêng biệt. Hệ thống này do một cá nhân tư nhân điều hành. Nhóm “ban-list” của anh ta được đồng quản trị bởi một điều phối viên lâu năm của cộng đồng Valve, người có quyền truy cập vào các chương trình bản thử nghiệm của Valve. Đơn vị duy nhất có khả năng công bố kết quả kiểm phiếu này nằm trong phạm vi ảnh hưởng củValve, nhưng lại không công bố kết quả đó.\n\nĐây chính là mô hình mà hồ sơ này phát hiện thấy ở mọi nơi khác. Mọi dịch vụ có quyền quyết định các vấn đề mang tính then chốt đối với nền kinh tế Steam — ai được tin cậy, ai có thể xác thực danh tính, giá trị của một mặt hàng là bao nhiêu, ai bị cấm — về mặt danh nghĩa đều là bên thứ ba, nhưng trên thực tế lại có mối liên hệ mật thiết với Valve. Steam Card Exchange không phải là một ngoại lệ đối với mô hình đó; nó là một ví dụ khác của mô hình đó. Lập luận rằng đây là những nhà khai thác độc lập vẫn được áp dụng cho Valve chính bởi vì chưa ai từng có thể kiểm chứng lập luận đó dựa trên một con số cụ thể nào.\n\nBảng thống kê tài khoản M của “10.88”: “88.97%” vẫn chưa bị can thiệp\n\nCơ sở lắp đặt của ArchiSteamFarm đã được kiểm toán trên toàn bộ các khu vực của Valve GetPlayerBans điểm cuối (tài khoản 10,880,610, 55 phút). Chỉ riêng tập con không bị giới hạn này đã chiếm $26.8M+ về mức chi tiêu tối thiểu tại cửa hàng (ngưỡng tham gia là $5.00). 9,680,599 các tài khoản (88.97%) không bị cấm dưới bất kỳ hình thức nào, và 99.8% trong số các trang còn lại chỉ áp dụng các lệnh cấm mang tính hình thức đối với cộng đồng, khiến hoạt động giao dịch tự động vẫn tiếp tục diễn ra.\n\n5,360,499Thành viên ASF không bị giới hạn (số lượng hiển thị trên Steam)\n10,880,610Tổng số mục tham gia cuộc thi “API” đã được kiểm tra (cả hạng mục có giới hạn và không giới hạn)\n9,680,599Chưa bao giờ bị cấm (88.97%)\n1,200,011Áp dụng bất kỳ lệnh cấm nào liên quan đến “Steam” (11.0%) — Vật phẩm trang trí “99.8%”\n55 phútĐể tiến hành điều tra dân số toàn bộ dân số, một yếu tố quan trọng\nBằng chứng pháp y và điều tra dân số chi tiết\n\nPhân tích nhân khẩu học chi tiết — bao gồm các biểu đồ phân bố theo loại lệnh cấm, thời gian sử dụng tài khoản tại thời điểm thực thi, các nhóm theo năm tạo tài khoản (2020–2026) và thông tin tự khai về vị trí địa lý — đã được công bố trong báo cáo điều tra dân số chuyên sâu.\n\nMở Bảng thống kê M Ban đầy đủ của 10.88(Phụ lục VI) →Phần “4” — Sự cố mất tín hiệu Asset ID →\n\nVậy câu hỏi cần đặt ra – và chỉ có Valve mới có thể trả lời – là: Mã định danh hoặc khả năng nào đã bị thu hồi, vào ngày nào, theo quyết định của ai, và nó đã gây ra tác động cụ thể nào đối với các nhà khai thác mà nó nhắm đến — so với tác động của nó đối với tất cả những người bên ngoài đang cố gắng thống kê. Một sự thay đổi chấm dứt việc kiểm toán độc lập sẽ không trở nên trung lập chỉ vì nó được công bố là một biện pháp an toàn. Đó chính là lý do tại sao cuộc điều tra dân số ở khu vực phía trên không tồn tại.\n\n09 — Phương pháp và giới hạn\nĐiều gì đã được đọc, và điều gì không được khẳng định\n\nMọi trích dẫn trên trang này đều được lấy từ nguồn trực tiếp tại 2026-09-22 và được sao chép nguyên văn. Không có nội dung nào ở đây được trích xuất từ dữ liệu thu thập tự động, thông tin đăng nhập trên sàn giao dịch hay bộ dữ liệu riêng tư.\n\nBốn bộ dữ liệu và các phép tính trên chúng\n\nMỗi yêu cầu là một yêu cầu công khai riêng lẻ, có thể tái tạo từ dòng lệnh. Không sử dụng tài khoản nào, không đăng nhập vào bất kỳ nền tảng thương mại điện tử nào và không gọi đến bất kỳ điểm cuối nào yêu cầu thông tin xác thực.\n\nBộ dữ liệu\tNguồn gốc của nó\tKết quả tính toán từ đó là gì\nCard census\n13,876 games\tSteam Card Exchange's published badge pricelist, the same feed that renders their public price page ↗ archived 2026-08-04 ↗\tGames issuing cards, cards per set, distinct card types, and the market price of each finished set. Medians and the $23,586.57 total are this investigation's arithmetic.\nGame prices\n13,713 resolved\tValve's own public store endpoint, store.steampowered.com/api/appdetails, cc=us, price field only, in batches\tMedian and distribution of the list price of a card-bearing game; the count of games whose finished set outsells the game itself.\nBot stock\n91 bots, 694,673 sets\tThe public card-bot directory at steam.supply/CardBots ↗, read as rendered, no login\tTotal sets in stock, the minimum card count, the drop-allowance floor, and the per-bot pigeonhole floor on distinct accounts.\nCross-check\n21 shared bots\tsteamlvlup.net/cardbots ↗ archived 2026-02-10 ↗, an independent directory of the same bots\tVerification only. On the 21 bots both list, aggregate stock agrees to 0.03%; the largest single-bot disagreement is 1.36%, consistent with two crawls of live inventory minutes apart.\n\nNguồn trích dẫn, theo yêu cầu của thư mục thứ hai: dữ liệu do SteamLvlUp, được cấp phép theo CC BY 4.0 đã lưu trữ 2026-09-23 ↗; được sử dụng ở đây chỉ nhằm mục đích kiểm tra độc lập các số liệu tồn kho của bên thứ ba, và đã được điều chỉnh theo hướng tổng hợp các hàng dữ liệu theo từng robot rồi so sánh, thay vì sao chép nguyên văn. Trang “Steam Card Exchange” và “steam.supply” đã được ghi nhận nguồn ở trên thông qua các liên kết. Giá trò chơi là của riêng Valve. Tên và hình ảnh thẻ, trò chơi và bộ sưu tập thuộc về Valve hoặc các nhà xuất bản, được sao chép mà không dựa trên bất kỳ tuyên bố hay giấy phép nào, với tư cách là thông tin thực tế về thị trường.\n\nHai phép đo dự kiến đã không được thực hiện và cũng không có phép đo nào thay thế cho chúng. Các điểm cuối của Chợ Cộng đồng do Steam tự thiết lập — Tổng quan về giá, tìm kiếm/hiển thị, lịch sử giá — không trả về bất kỳ thông tin nào cho máy chủ thu thập dữ liệu, và các trang thảo luận của cộng đồng Steam trả về phản hồi HTTP 403 cho máy chủ đó, do đó không có số liệu nào trên trang này được lấy từ dữ liệu thị trường thời gian thực. Phương thức tính khối lượng giao dịch, vốn sẽ thống kê số lượng thẻ được phát hành vào thời điểm thiết lập lại hàng ngày, yêu cầu phải có phiên đăng nhập tại Steam; Bản kê khai của cuộc điều tra này nêu rõ rằng không có thông tin đăng nhập nào của nền tảng thương mại điện tử được sử dụng, và tuyên bố đó đã được giữ nguyên. Mức sàn của cổ phiếu bot là mức có thể đo lường được mà không cần đến bot.\n\nNguồn tư liệu sơ cấp\n\nSteam Thỏa thuận người đăng ký ↗ đã lưu trữ 2026-09-24 ↗ — § 2.A, § 2.G, § 3.D, § 4.C, § 4.D.\nSteam Hỗ trợ — Tài khoản người dùng có giới hạn ↗ — ngưỡng $5.00 và danh sách các tính năng bị hạn chế.\nValve — Câu hỏi thường gặp về Thẻ sưu tập “Steam” ↗ — cơ chế nhận vật phẩm ngẫu nhiên và mô hình chơi miễn phí với mức chi tiêu $9.\nCâu hỏi thường gặp về ArchiSteamFarm ↗ và cuộc thảo luận số3440 ↗.\nSteam Các trang nhóm và trang hồ sơ cộng đồng, xem trực tiếp tại mục 08.\nsteamid.uk Câu hỏi thường gặp, bản chụp nhanh từ Internet Archive 2026-04-01 ↗.\nTám thông báo về khóa hỗ trợ của Steam do các bên nhận thông báo đăng tải, 2020–2026, được liệt kê kèm theo các liên kết tương ứng tại mục 06.\n\nNhững điều không được yêu cầu\n\nKhông có con số ước tính nào về doanh thu từ hoạt động “card farming” trên Valve. Không có số liệu nào về số lượng tài khoản hoạt động được công bố cho bất kỳ công cụ nào, và mức giới hạn 1.39 triệu là không số lượng tài khoản thuộc sở hữu của trang trại — xem ghi chú trong phần 02. Không có cá nhân nào bị cáo buộc có hành vi sai trái; khi một người được nêu tên, đó là thông qua tên người dùng công khai Steam của chính họ, trong vai trò công khai của họ, từ một trang do Valve xuất bản. Không có tài khoản nào trong số tám tài khoản bị khóa ở phần 06 được khẳng định là vô tội hay có tội; kết luận này liên quan đến bức thư, không phải tài khoản. Các số liệu về tổn thất của nhà điều hành trong phần 02 là báo cáo từ chính bên liên quan và được ghi chú rõ là như vậy tại Ghi chú về nguồn hàng. Phần Câu hỏi thường gặp (FAQ) của trang “steamid.uk” được trích dẫn từ một bản chụp nhanh trên Internet Archive vì trang web hiện tại yêu cầu vượt qua thử thách xác thực bằng bot. Không có khẳng định nào cho rằng đã có nỗ lực thu thập dữ liệu về các trường hợp bị cấm và bị che giấu — kết luận duy nhất là chưa có dữ liệu nào được công bố. Đường cong mức độ “Steam” ở trên 667 không phải là mô hình.\n\nTại sao công cụ lại không phải là chủ đề\n\nArchiSteamFarm khẳng định rằng nó \"không được Valve cho phép\" và nó không bị cáo buộc bất cứ điều gì trên trang này. Nó được sử dụng như một công cụ đo lường, bởi vì đây là bên duy nhất trong nền kinh tế này ghi chép lại các cơ chế hoạt động một cách công khai và bằng văn bản. Valve có thể tóm gọn toàn bộ vấn đề chỉ trong một đoạn văn: công bố những giải pháp tự động hóa thương mại nào mà họ cho phép, cùng với bản ghi chi tiết theo từng người vận hành về những gì họ đã làm đối với phần còn lại.\n\nĐọc tiếp: cách thị trường tự định giá → · thang giá và mức trần niêm yết → · các mặt hàng mà Steam sẽ không kinh doanh →",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Nền kinh tế thẻ — Bán buôn, giới hạn rút tiền và khai thác tự động"
          },
          {
            "level": 2,
            "id": null,
            "text": "Một trang trại thực sự là gì, từng bước một"
          },
          {
            "level": 3,
            "id": null,
            "text": "Mua vào"
          },
          {
            "level": 3,
            "id": null,
            "text": "Mua trò chơi"
          },
          {
            "level": 3,
            "id": null,
            "text": "Không hoạt động\nCông cụ này đăng nhập tài khoản vào mạng Steam ở chế độ không giao diện, \"xử lý các huy hiệu của bạn\", tạo danh sách các tựa game có thể cày cuốc và bắt đầu \"chơi các trò chơi đủ điều kiện và định kỳ kiểm tra xem trò chơi đó đã được khai thác hết chưa.\" Mô tả của người duy trì về cơ chế này: nó \"Chỉ đơn thuần là thông báo cho Steam rằng chúng tôi đang chơi trò chơi đó mà thôi.\""
          },
          {
            "level": 3,
            "id": null,
            "text": "Hạt nhỏ đã cạn\nMỗi tiêu đề đều có giới hạn. \"Mỗi trò chơi đều có số lượng thẻ rơi ra cố định. Một khi bạn đã thu thập hết số thẻ đó (khoảng một nửa bộ sưu tập đầy đủ), trò chơi đó sẽ không còn là lựa chọn để cày cuốc nữa.\" Một trang trại muốn tiếp tục sản xuất thì phải liên tục mua các thẻ bài. Nguồn cung thẻ bài bị hạn chế bởi các giao dịch mua — điều này là do thiết kế của trò chơi và mang lại lợi thế choValve."
          },
          {
            "level": 3,
            "id": null,
            "text": "Rút tiền\nThẻ sẽ rời đi qua một trong ba lối: được bán trên Thị trường Cộng đồng, được trao đổi, hoặc được nghiền nát thành đá quý. Mỗi trường hợp đều là một giao dịch trên Thị trường Đăng ký hoặc một cuộc trao đổi, và § 3.D sẽ thu phí: \"Valve có thể thu phí đối với các giao dịch trên Nền tảng Giao dịch Đăng ký.\" Đây chính là bước khiến toàn bộ sự việc trở thành một vụ vi phạm — xem 05."
          },
          {
            "level": 2,
            "id": null,
            "text": "Trước khi một trang trại kiếm được một xu, nó đã phải chi trả Valve"
          },
          {
            "level": 3,
            "id": null,
            "text": "Kích thước thực tế của món đồ đang được mua là bao nhiêu"
          },
          {
            "level": 3,
            "id": null,
            "text": "Một tập có kích thước bao nhiêu?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Chi phí cấp giấy phép là bao nhiêu?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Kết quả trả về của tập hợp đã hoàn thành là gì"
          },
          {
            "level": 3,
            "id": null,
            "text": "Vị trí hiện tại của các cụm máy bay chiến đấu F-694,673"
          },
          {
            "level": 3,
            "id": null,
            "text": "Những điều sàn nhà này thể hiện và không thể hiện"
          },
          {
            "level": 3,
            "id": null,
            "text": "Và với mức giá mà “Valve” đưa ra, việc làm nông không thể tự trang trải chi phí"
          },
          {
            "level": 3,
            "id": null,
            "text": "Điều mà trang trại thực sự hỗ trợ"
          },
          {
            "level": 4,
            "id": null,
            "text": "Doanh số bán game"
          },
          {
            "level": 4,
            "id": null,
            "text": "\"Trực tuyến\" & thời gian chơi"
          },
          {
            "level": 4,
            "id": null,
            "text": "Đăng ký"
          },
          {
            "level": 4,
            "id": null,
            "text": "Tiền trong ví và phí"
          },
          {
            "level": 4,
            "id": null,
            "text": "Steam- PR cấp độ"
          },
          {
            "level": 3,
            "id": null,
            "text": "Và chính việc rút tiền mặt này đã làm giảm giá trị Valve — bị đánh thuế hai lần"
          },
          {
            "level": 3,
            "id": null,
            "text": "Đây không chỉ là một khoảnh khắc. Đây là một ngành công nghiệp có nền tảng vững chắc được xây dựng qua nhiều năm."
          },
          {
            "level": 3,
            "id": null,
            "text": "Các bộ thẻ hoàn chỉnh được lưu trữ trong thư mục bot công khai, theo đợt bán hàng của Steam"
          },
          {
            "level": 3,
            "id": null,
            "text": "Bảng xếp hạng huy hiệu bán hàng trông như thế nào khi nhìn từ đỉnh"
          },
          {
            "level": 3,
            "id": null,
            "text": "Và đội tàu đó vẫn ở đó ngay cả khi không có đợt giảm giá nào đang diễn ra"
          },
          {
            "level": 3,
            "id": null,
            "text": "Thư mục lưu trữ, theo từng bot"
          },
          {
            "level": 2,
            "id": null,
            "text": "Sản phẩm còn lại là con số nằm bên cạnh tên của bạn"
          },
          {
            "level": 3,
            "id": null,
            "text": "Các bộ sản phẩm đã được tiêu thụ, cấp độ 1 đến 1,000"
          },
          {
            "level": 3,
            "id": null,
            "text": "Cách kiểm tra đường cong này như thế nào, vì trang Valve không công bố số liệu này"
          },
          {
            "level": 2,
            "id": null,
            "text": "Điều khoản này không mô tả nghề nông một cách mơ hồ. Nó liệt kê cụ thể các hoạt động đó."
          },
          {
            "level": 3,
            "id": null,
            "text": "\"…giờ chơi\""
          },
          {
            "level": 3,
            "id": null,
            "text": "\"…nếu thiếu ý kiến đóng góp thực sự từ người dùng\""
          },
          {
            "level": 2,
            "id": null,
            "text": "Mỗi lần ra khỏi khu vực thẻ được cấp phép đều là hành vi bị giấy phép cấm — và Valve thu phí tại cửa ra vào"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 2.A — giấy phép"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 2.G — các hạn chế"
          },
          {
            "level": 3,
            "id": null,
            "text": "§ 3.D — mức phí"
          },
          {
            "level": 3,
            "id": null,
            "text": "Đọc cả ba điều này cùng nhau thì vị trí đó sẽ bị đóng lại"
          },
          {
            "level": 3,
            "id": "fee-ladder",
            "text": "Phí tại cửa đó không phải là 15%.. Trên thẻ được khai thác, mức phí này lên tới hai phần ba."
          },
          {
            "level": 3,
            "id": null,
            "text": "Phí thực tế áp dụng cho giao dịch trên Thị trường Cộng đồng, tính theo giá chào bán của người bán"
          },
          {
            "level": 2,
            "id": null,
            "text": "Không có thông báo trước, diễn ra từng đợt, và lan truyền qua số điện thoại"
          },
          {
            "level": 3,
            "id": null,
            "text": "Trường hợp 4 — Tháng 6 năm 2025, Các lệnh cấm của VAC đối với CS2 bị tạm ngưng"
          },
          {
            "level": 3,
            "id": null,
            "text": "Cách một tài khoản chính bị xóa"
          },
          {
            "level": 3,
            "id": null,
            "text": "Cùng một đoạn văn, cách nhau năm năm, từ ba đại lý khác nhau"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ghi chú về nguồn cung — tổn thất ở cấp độ nhà khai thác"
          },
          {
            "level": 2,
            "id": null,
            "text": "Hai bên của cùng một chiếc bàn"
          },
          {
            "level": 3,
            "id": null,
            "text": "Một khách hàng, để giao dịch"
          },
          {
            "level": 3,
            "id": null,
            "text": "Một đội bot tự động, dành cho khối lượng lớn"
          },
          {
            "level": 3,
            "id": null,
            "text": "Câu hỏi đặt ra ở đây, nói một cách đơn giản là"
          },
          {
            "level": 2,
            "id": null,
            "text": "Ai là người điều tiết nền kinh tế thẻ?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Một nhân viên của Valve điều hành nhóm trao đổi thẻ lớn nhất Valve nhân viên"
          },
          {
            "level": 3,
            "id": null,
            "text": "Tầng danh sách cấm và ai là người quản lý nó Người điều hành tình nguyện Dịch vụ của bên thứ ba"
          },
          {
            "level": 3,
            "id": null,
            "text": "Điều này dẫn đến điều gì, và điều gì thì không"
          },
          {
            "level": 3,
            "id": null,
            "text": "Không ai được tính. Đó là kết luận."
          },
          {
            "level": 3,
            "id": null,
            "text": "Bảng thống kê tài khoản M của “10.88”: “88.97%” vẫn chưa bị can thiệp"
          },
          {
            "level": 3,
            "id": null,
            "text": "Bằng chứng pháp y và điều tra dân số chi tiết"
          },
          {
            "level": 2,
            "id": null,
            "text": "Điều gì đã được đọc, và điều gì không được khẳng định"
          },
          {
            "level": 3,
            "id": null,
            "text": "Bốn bộ dữ liệu và các phép tính trên chúng"
          },
          {
            "level": 3,
            "id": null,
            "text": "Nguồn tư liệu sơ cấp"
          },
          {
            "level": 3,
            "id": null,
            "text": "Những điều không được yêu cầu"
          },
          {
            "level": 3,
            "id": null,
            "text": "Tại sao công cụ lại không phải là chủ đề"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/vi/#briefing-heading",
          "https://help.steampowered.com/en/faqs/view/71D3-35C2-AD96-AA3A",
          "https://github.com/JustArchiNET/ArchiSteamFarm/wiki/FAQ",
          "https://steamcommunity.com/tradingcards/faq/",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260924114457/https://store.steampowered.com/subscriber_agreement/",
          "https://steamladder.com/ladder/badges/2861690/",
          "http://web.archive.org/web/20260716205303/https://steamladder.com/ladder/badges/2861690/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/farm-economy-timeline.json",
          "https://store.steampowered.com/charts/",
          "http://web.archive.org/web/20260923183013/https://store.steampowered.com/charts/",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://github.com/JustArchiNET/ArchiSteamFarm/discussions/3440",
          "https://x.com/gergelyszabo94/status/1311004678633795585",
          "https://x.com/prcs25/status/1811893857253982720",
          "http://web.archive.org/web/20240715122902/https://x.com/prcs25/status/1811893857253982720",
          "https://reddit.com/r/steamsupport/comments/1fjmgc5/what_to_do_when_your_steam_account_gets_hacked/mkelm2y/",
          "https://www.reddit.com/r/csgomarketforum/comments/r87owv/psa_my_steam_account_just_got_banned/",
          "http://web.archive.org/web/20250327203008/https://www.reddit.com/r/csgomarketforum/comments/r87owv/psa_my_steam_account_just_got_banned/",
          "https://www.reddit.com/r/GlobalOffensiveTrade/comments/r9xql9/d_recently_received_commercial_ban_for_what_seems/",
          "http://web.archive.org/web/20211206034804/https://www.reddit.com/r/GlobalOffensiveTrade/comments/r9xql9/d_recently_received_commercial_ban_for_what_seems/",
          "https://www.reddit.com/r/csgomarketforum/comments/1hhxx7m/d_permanently_locked_on_steam_for_commercial_use/",
          "http://web.archive.org/web/20250627014045/https://www.reddit.com/r/csgomarketforum/comments/1hhxx7m/d_permanently_locked_on_steam_for_commercial_use/",
          "https://www.reddit.com/r/steamsupport/comments/1hkctwt/permanent_ban_with_no_explanation/",
          "https://www.reddit.com/r/pcgaming/comments/1vf24lu/warning_to_all_gamersexpats_steam_took_my_money/",
          "https://steamcommunity.com/groups/card-trading-card-trades",
          "https://steamcommunity.com/id/afarnsworth",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/groups/steambans",
          "https://steamcommunity.com/groups/steambans",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/id/killahinstinct_",
          "https://web.archive.org/web/20240914124859/https://steamcommunity.com/id/msart",
          "https://steamcommunity.com/id/msart/groups/",
          "http://web.archive.org/web/20260401154714/https://steamid.uk/faq/",
          "https://phishdestroy.io/steam_dossier/vi/enforcement_audit.html",
          "https://phishdestroy.io/steam_dossier/vi/#evidence-blackout",
          "https://www.steamcardexchange.net/index.php?badgeprices",
          "http://web.archive.org/web/20260804200309/https://www.steamcardexchange.net/index.php?badgeprices",
          "https://steam.supply/CardBots",
          "https://steamlvlup.net/cardbots",
          "http://web.archive.org/web/20260210171205/https://steamlvlup.net/cardbots",
          "https://steamlvlup.net/",
          "https://creativecommons.org/licenses/by/4.0/",
          "http://web.archive.org/web/20260923221628/https://creativecommons.org/licenses/by/4.0/",
          "https://phishdestroy.io/steam_dossier/vi/market_economics.html",
          "https://phishdestroy.io/steam_dossier/vi/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/vi/elite_skins.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/vi/card_economy.content.json",
      "export_json_sha256": "3f844929d30dbab961e7b1b6df3e88522e91b2821eb82bdd2935a4c9df298dde"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "vi/elite_skins.html",
      "language": "vi",
      "title": "Một mặt hàng, hai hệ thống giá — Hồ sơ “Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/vi/elite_skins",
      "source_html_sha256": "78bc1396926b48f672752ada76abafb37b70220d3d94b024d0b1ebf2d9b3e183",
      "exported_at": "2026-09-29T00:22:59.362Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "register",
            "source": "https://phishdestroy.io/steam_dossier/vi/elite_skins#register"
          },
          {
            "id": "",
            "source": "https://phishdestroy.io/steam_dossier/vi/elite_skins#selected"
          }
        ],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "elite_skins.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/vi/elite_skins.pdf?v=print-20260929-v5",
        "sha256": "abb542ed08cadd2c020f94cd48e07123952d1974497a6cf4f0ed9372dac6a064",
        "bytes": 102492,
        "pages": 7
      },
      "integrity": {
        "signed_object": "elite_skins.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "elite_skins.content.json.asc",
        "digest_file": "elite_skins.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify elite_skins.content.json.asc elite_skins.content.json",
          "sha256sum -c elite_skins.content.json.sha256"
        ]
      },
      "content": {
        "text": "PHỤ LỤC IV / CẤU TRÚC THỊ TRƯỜNG / 20 THÁNG 9 NĂM 2026\nĐăng ký Elite Skins — Mức trần thị trường $1,800\n\nMột món. Hai hệ thống giá.\n\nPHẦN NÀY CHỨNG MINH ĐIỀU GÌ\n\nDanh mục này thiết lập một cuộc điều tra thực nghiệm về tất cả các hạng da CS2 có giá cao hơn mức trần niêm yết $1,800 trên Thị trường Cộng đồng của Steam, trải rộng trên năm sàn giao dịch bên ngoài. Điều này chứng minh rằng 248 các hạng da cao cấp đã được xác nhận — đại diện cho 18,394 danh sách niêm yết đang hoạt động và $78.6 triệu thanh khoản niêm yết — 100% lại vắng bóng trên thị trường chính thức của Valve. Các nhà bán hàng tìm kiếm mức giá thị trường thực sự buộc phải chuyển sang các nền tảng bên ngoài do cơ chế hoạt động nội tại của Steam.\n\nWhat this means — the Community Market listing ceiling\n\nSteam’s own market refuses a listing above roughly $1,800. A seller may ask less, never more. Items whose market price sits above that line therefore cannot be sold at that price on Steam at all — which is the mechanism that moves those sales to third-party venues while the item itself never leaves Valve’s inventory system.\n\nSection 13 — the off-Steam price gap →\n\n← Quay lại Bản tóm tắt dành cho lãnh đạo\n\nSteam giá niêm yết trên Community Market ở mức khoảng $1,800. Trên năm sàn giao dịch bên thứ ba được ghi nhận trong bản tổng quan này, 419 Các danh mục sản phẩm CS2 có mức giá chào bán trực tiếp rẻ nhất cao hơn mức giới hạn đó — và 402 trong số đó, 95.9%, hoàn toàn không có Steam bất kỳ danh sách nào. Tổng cộng, họ nắm giữ các bản sao được liệt kê trên 18,641 với giá trị ít nhất là $82.4 triệu. Để giá được tính là hợp lệ, cần phải có sự đồng ý từ một sàn giao dịch thứ hai, 248 trong số các danh mục đó đều đã được xác nhận — và trong tất cả các danh mục đó, cuốn “100%,” đều không có mặt trên trang web Steam. Món quà đáng yêu nhất là một miếng dán | Titan (Holo) | Katowice 2014 tại $66,285, được trích dẫn bởi bốn sàn giao dịch nằm trong khoảng cách 5.2% so với nhau và không được bất kỳ sàn nào thuộc Valve đăng tải. Bảng xếp hạng đầy đủ, các hình ảnh mô phỏng và hệ thống chấm điểm có trong Bảng giá theo bậc thang.\n\nXem tất cả các bài đăng trên 419 ↓Mở cuốn bản đồ ↗Đọc phương pháp\n248các danh mục có hai hoặc nhiều sàn giao dịch có giá cao hơn mức trần\n18,394số lượng bản được liệt kê trên năm sàn giao dịch\n$78.6Mgiá sàn của các danh sách đó\n100%trong số đó hoàn toàn không xuất hiện trên trang web Steam\n\nSửa lỗi · trước đây, trang này đã đưa ra một mức giá chưa được xác minh\n\nMột phiên bản trước đó của trang này có tiêu đề “Souvenir AK-47| Point Disarray” được rao bán với giá $148,954 trên một sàn thương mại điện tử, trong khi Steam niêm yết giá $119. Dòng sản phẩm này chỉ xuất hiện trên một kệ hàng duy nhất và chỉ có một bản duy nhất, không có sàn thương mại điện tử nào khác niêm yết giá tương tự, do đó đây là mức giá chào bán chứ không phải giá thực tế, và sản phẩm này hiện không còn được liệt kê trên trang nữa. Mọi con số tiêu đề ở đây hiện chỉ giới hạn trong các danh mục 248 mà ít nhất hai sàn giao dịch độc lập định giá cao hơn mức trần. Dòng sản phẩm đó chưa bị xóa — nó vẫn còn trong danh sách bên dưới, và tiêu chí phân loại khiến nó bị hạ cấp được trình bày đầy đủ trong Bảng giá theo bậc thang.\n\n01 / số tiền trong các lệnh mua đang hoạt động\nMức sàn có thể đo lường được tính bằng đô la\n\nĐược tính toán lại dựa trên bản chụp nhanh được cấp phép từ cs2.sh trên năm thị trường. Đây là giá chào bán tổng hợp tối thiểu trong một tập con được xác định, không phải là doanh thu bán hàng và cũng không phải là mức định giá của nền kinh tế CS2.\n\n248 CÁC DANH MỤC ĐÃ ĐƯỢC XÁC NHẬN · 18,394 CÁC BẢN SAO ĐƯỢC LỊCH KÊ · 5 CÁC SÀN GIAO DỊCH$78.62M\n\nMức giá chào bán tổng hợp tối thiểu của mỗi mặt hàng CS2 mà hai hoặc nhiều sàn giao dịch độc lập định giá cao hơn mức giới hạn mà Valve cho phép trên chính sàn giao dịch của mình.\n\nTại sao đây là mức sàn chứ không phải mức ước tính\n\nĐối với mỗi sàn thương mại điện tử, chúng tôi nhân giá trị của nó với thấp nhất Hãy đặt giá mua một mặt hàng theo số lượng bản mà sàn giao dịch đó niêm yết. Mọi bản khác trên kệ đó đều có giá bằng hoặc cao hơn mức giá chào bán thấp nhất, do đó giá trị niêm yết thực tế sẽ cao hơn — điều này được xác định theo cơ chế hoạt động, chứ không phải dựa trên phỏng đoán. Đây không phải là giao dịch bán hàng, dòng tiền hay định giá trên toàn thị trường, và cùng một mặt hàng vật lý có thể xuất hiện trên nhiều sàn giao dịch khác nhau.\n\nKiểm tra tất cả các hàng nguồn của “419” ↗\n★ Găng tay thể thao | Hedge Maze (Đã được kiểm chứng thực tế)\n$4.68M\nAWP | Gungnir (Mới nguyên hộp)\n$4.46M\nAWP | Dragon Lore (Mới nguyên hộp)\n$4.34M\n★ Dao bướm | Fade (Mới nguyên seal)\n$4.17M\nAK-47 | Wild Lotus (Mới nguyên hộp)\n$4.16M\n★ Dao bướm | Doppler (Mới nguyên hộp)\n$3.64M\n\nCác thanh biểu đồ thể hiện sáu đóng góp lớn nhất ở cấp độ danh mục vào kết quả tính toán tổng, được quy đổi theo tỷ lệ so với giá trị lớn nhất. Một thanh biểu đồ cao phản ánh cả mức giá bán ra rẻ nhất và số lượng sản phẩm được niêm yết. Một mặt hàng vật lý có thể xuất hiện trên nhiều sàn thương mại điện tử khác nhau, do đó các con số này không được cộng vào tổng của bất kỳ sàn thương mại điện tử nào khác.\n\n02 / các ví dụ có thể kiểm tra được\nNhững gì giới hạn này bỏ sót\n\nCác hình minh họa tương ứng với tên chính xác của các mặt hàng (nếu có). Giá niêm yết là giá chào bán hiện hành trích từ danh mục có ghi ngày tháng, không phải là giá giao dịch thực tế.\n\n★ Butterfly Knife | Doppler (Factory New)\n\nNguồn: https://phishdestroy.io/steam_dossier/vi/elite_skins#selected\n\nKhoảng cách có thể đo lường được: Các ưu đãi này không thể so sánh được với các tin đăng trên Steam có mức giá bằng USD tương đương. Riêng Valve Câu hỏi thường gặp về Chợ Cộng đồng đã lưu trữ 2026-09-21 ↗ quy định mức giá niêm yết tối đa khoảng $1,800. Người bán vẫn có thể niêm yết với mức giá thấp hơn mức này; việc liệu mức giá đó có được chấp nhận hay không là quyết định của người bán. Một Tìm kiếm các mặt hàng có giá trên $1,800 ↗ hiển thị thông tin về “Factory New Dragon Lore” trên các thị trường được lập chỉ mục tại 28 với khoảng 1.1K lượt hiển thị sản phẩm; hàng tồn kho trùng lặp có thể được tính nhiều lần.\n\n03 / sự phụ thuộc về mặt cấu trúc\nChiếc mũ của Steam đã khiến quá trình xác định giá vượt ra ngoài phạm vi Steam\n\nSự so sánh này mang tính cấu trúc. Nó không giả định rằng mọi mức giá chào bán đều hợp lý, cũng không coi các danh sách bất động sản chưa bán được là doanh thu.\n\n01 · QUY TẮC\nSteam đặt tiêu đề cho danh sách\n\nValve cho biết số lượng tin đăng trên Community Market bị giới hạn ở mức khoảng $1,800. Số dư trong ví cũng bị giới hạn, và số tiền trong ví không thể rút ra dưới dạng tiền mặt.\n\n02 · QUAN SÁT\nDragon Lore: $10,940.85\n\nDanh mục sản phẩm trên sàn thương mại điện tử 5-cho thấy 389 Ưu đãi trực tiếp Đối với AWP Dragon Lore (mới nguyên hộp), giá khởi điểm từ $10,940.85 (tầng CSFloat). Danh mục mở rộng bao gồm các hạng mục đã được xác nhận tại 248, vượt quá giới hạn của Steam.\n\n03 · HẬU QUẢ\nGiá và tỷ lệ chia sẻ phí chuyển nhượng\n\nMột người bán mong muốn mức giá cao hơn không thể đăng bài đó lên Steam. Các dịch vụ bên ngoài có thể thiết lập giá tiền mặt, nhưng việc giao hàng vẫn tuân theo quy trình sở hữu và chuyển nhượng mặt hàng do Steamkiểm soát.\n\nSự mâu thuẫn trong chính sách: Của chính Valve Thỏa thuận người đăng ký đã lưu trữ 2026-09-21 ↗ giữ quyền khai thác thương mại các dịch vụ của Steam trừ khi được cho phép rõ ràng, trong khi đó 2016 tuyên bố đã lưu trữ 2026-09-21 ↗ Các nhà điều hành cờ bạc nói trên đã sử dụng OpenID của Steam và các tài khoản tự động. Đó là bằng chứng trực tiếp cho thấy Valve đã biết về loại nhà điều hành bên ngoài này tại 2016.. Tuy nhiên, thị trường chính thức lại không thể công bố giá thực tế của những mặt hàng có giá trị cao này. Đó là sự phụ thuộc về mặt kiến trúc vào việc xác định giá và các giao dịch trên nền tảng off-Steam; Tình trạng hợp đồng của từng sàn giao dịch riêng lẻ cần có bằng chứng riêng. Hai sàn giao dịch chính của phương Tây đang ghi nhận khối lượng giao dịch vượt mức này hoạt động dưới hình thức các pháp nhân chính thức tại các khu vực pháp lý lớn — CSFloat Công ty TNHH (được thành lập tại Delaware, Hoa Kỳ) và Skinport GmbH (đăng ký tại Stuttgart, Đức, số đăng ký doanh nghiệp (HRB) 764879) — thực hiện công khai các giao dịch trị giá hàng trăm triệu trong lĩnh vực bán hàng trực tiếp giữa các cá nhân (peer-to-peer), dựa trực tiếp vào các giao diện lập trình ứng dụng (API) và hạ tầng giao dịch của Steam.\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\nBốn dòng có giá $100,000 nằm ở mức giá niêm yết tối đa của chính CSFloat. Các dòng này được đánh dấu trong sổ đăng ký và không được coi là kết quả thẩm định. Dữ liệu lưu trữ từ CSFloat chỉ ghi nhận mức giá khoảng $6,999,, do đó bản chụp nhanh danh mục công khai được sử dụng để hiển thị toàn bộ sổ đăng ký với giá trên $1,800.\n\n04 / một tựa game khác thuộc dòng Valve\nTrần nhà cũng chặn được Dota 2\n\nKhi áp dụng cùng tiêu chí “giá rẻ nhất” nghiêm ngặt trên Skinport, kết quả cho thấy các danh mục 166 CS2 và 3 Dota 2. Đây là các bản chụp nhanh thị trường riêng biệt; không nên thêm chúng vào danh sách 245. của CSFloat\n\nDOTA 2 · ƯU ĐÃI 1\nTrăng lưỡi liềm anh hùng và tàn bạo\n\nGiá rẻ nhất cho “Skinport” như sau: $14,622.25.\n\nDOTA 2 · ƯU ĐÃI 1\nÁo choàng nghệ thuật huyền bí\n\nGiá rẻ nhất cho “Skinport” như sau: $8,255.16.\n\nDOTA 2 · ƯU ĐÃI 1\nNgôi sao năng lượng bị hư hỏng\n\nGiá rẻ nhất cho “Skinport” như sau: $2,087.92.\n\nĐây là ba danh mục vật phẩm được liệt kê, chứ không phải tất cả các vật phẩm Dota 2 hiện có. Kiểm tra các hàng có ngày tháng trong bảng “Skinport” ↗ và API tài liệu ↗.\n\n05 / độ bền\nKết quả này không phụ thuộc vào mức trần cụ thể\n\nValve đặt mức trần bằng đồng tiền khu vực của người mua, do đó khi quy đổi sang USD, con số này không phải là một con số tròn. Do đó, việc thống kê được lặp lại tại mọi ngưỡng có thể. Tỷ lệ các mặt hàng này còn thiếu trên trang Steam không bao giờ giảm xuống dưới mức 95%.\n\nĐã kiểm tra ngưỡng\tDanh mục sản phẩm\tCác bản sao được liệt kê\tGiá sàn\tKhông có trong chương trình “Steam”\n$1,800\t419\t18,641\t$82,449,526\t95.9%\n$2,000\t382\t15,159\t$75,541,325\t95.5%\n$2,070\t363\t12,336\t$69,560,305\t95.6%\n$2,300\t323\t11,644\t$67,984,432\t95.0%\n$2,500\t299\t10,950\t$66,203,929\t95.0%\n\nĐọc từng hàng một; các hàng này là các tập con lồng nhau của cùng một cuộc điều tra dân số, chứ không phải là các nhóm dân số riêng biệt. “Giá trị sàn” nhân với mỗi thị trường thấp nhất hệ thống này tính theo số bản được liệt kê, nên về bản chất, số lượng sách trên kệ được ghi nhận sẽ thấp hơn thực tế. Mở tập dữ liệu ↗\n\n06 / sự khan hiếm mà bạn có thể đếm được\nThực tế thì có rất ít sản phẩm như vậy được bày bán\n\nBUFF chia kệ của từng mặt hàng thành các khoảng giá và công bố số lượng bản có trong mỗi khoảng. Điều này biến từ “hiếm” từ một từ ngữ thành một con số cụ thể — và định giá tình trạng sản phẩm tách biệt với mẫu thiết kế.\n\n298 DANH SÁCH CÁC BẢN SAO\nAWP | Truyền thuyết về Rồng\n\n8 các phiên bản khác nhau với mức giá khác nhau. Phiên bản đắt nhất, AWP lưu niệm | Dragon Lore (Mới nguyên hộp), hỏi $12,363 với 20 bản trên kệ.\n\nTrong ngăn đựng đồ nổi tốt nhất trên kệ (0–0.01) có 2 bản sao, hỏi $17,875 — mức chênh lệch “45%” so với giá chào bán cơ bản của mặt hàng, chỉ dựa trên tình trạng của sản phẩm.\n\n607 DANH SÁCH CÁC BẢN SAO\nM4A4 | Tiếng hú\n\n12 các phiên bản khác nhau với mức giá tương ứng. Phiên bản đắt nhất, Quà lưu niệm M4A4 | Howl (Mới nguyên hộp), hỏi $14,895 với 2 bản đang có sẵn trên kệ.\n\n213 DANH SÁCH CÁC BẢN SAO\nAK-47 | Hoa sen hoang dã\n\n7 các phiên bản khác nhau với mức giá tương ứng. Phiên bản đắt nhất, Quà lưu niệm AK-47| Wild Lotus (Mới nguyên hộp), hỏi $14,895 với 2 bản đang có sẵn trên kệ.\n\n310 DANH SÁCH CÁC BẢN SAO\nAWP | Gungnir\n\n7 các phiên bản khác nhau với mức giá tương ứng. Phiên bản đắt nhất, Đồ lưu niệm AWP | Gungnir (Hơi mòn), hỏi $14,895 với 2 bản đang có sẵn trên kệ.\n\nTại sao điều này lại quan trọng đối với phần còn lại của tập tài liệu này: Đây không phải là những khái niệm trừu tượng. Trên toàn thế giới, mỗi chiếc cúp chỉ tồn tại vài trăm bản trên các kệ mở, mỗi bản đều gắn liền với một tài khoản Steam và được chuyển nhượng qua một giao dịch Steam. Trong một thị trường thưa thớt như vậy, việc một mặt hàng bị đánh cắp là một sự kiện có thể đo lường được, và các kỹ thuật chiếm quyền kiểm soát tài khoản được ghi chép ở những phần khác trong cuộc điều tra này mang lại lợi ích trực tiếp và có thể định lượng được.\n\nSố lượng là số lượng sản phẩm đang được rao bán trên một sàn thương mại điện tử tại thời điểm thu thập dữ liệu, không phải tổng số sản phẩm hiện có. Các bản sao được lưu trữ trong kho riêng không được tính vào bất kỳ số liệu nào ở đây. Mở tập dữ liệu float ↗\n\n07 / chiếc thang nằm ngoài tầm nhìn\nMặt hàng càng đắt tiền thì càng nằm xa các địa điểm có thể quan sát được\n\nMỗi bậc dưới đây đại diện cho một loại chứng cứ khác nhau. Chúng được cố ý không gộp lại thành một con số duy nhất.\n\nRung\tHình\tĐây là loại sự kiện nào vậy?\nCeiling on Valve's own market\t~$1,800\tPublished rule, stated in the Steam Community Market FAQ.\nDearest ask several marketplaces agree on\t$66,285\tMeasured by us in this snapshot. Sticker | Titan (Holo) | Katowice 2014, quoted by four marketplaces within 5.2% of one another. An ask, not a sale.\nDearest ask seen on any single shelf\t$148,954\tOne marketplace, one copy, no second marketplace agreeing — and equal to a round CNY 1,000,000 at the snapshot rate. Listed here as the outer edge of what sellers ask, and relied on for nothing.\nPublic marketplace sale\t$49,999\tSpecialist Gloves | Crimson Kimono (FN) on CSFloat, as reported by SteamAnalyst. Platform-recorded, third-party reported.\nReported private sale\t$400,000\tAK-47 | Case Hardened, reported by PC Gamer in April 2023. Journalism, not a record we hold.\nReported offer, declined\t$1,500,000\tBlue Gem Karambit, pattern #387. No sale took place and the figure has not been independently confirmed. Included to mark the ceiling of the claims, not to assert a value.\n\nĐiểm về cấu trúc: Thị trường của Valve dừng lại ở mức khoảng $1,800. Các sàn giao dịch bên thứ ba đưa mức giá giao dịch lên khoảng $66,000, nơi một số sàn đồng ý, và lên khoảng $150,000, nơi chỉ có một sàn đồng ý. Trên mức đó hoàn toàn không có sàn giao dịch nào — các giao dịch chuyển nhượng tài sản do Valvephát hành với quy mô lớn nhất diễn ra theo hình thức riêng tư, giữa các cá nhân, không có niêm yết, không có hồ sơ trên nền tảng, không kiểm tra danh tính và không có báo cáo. Bản thân quá trình chuyển nhượng vẫn diễn ra trên Steam. Giá trị càng cao thì càng ít người có thể nhìn thấy nó, và toàn bộ cơ sở hạ tầng truyền tải giá trị đó đều thuộc về Valve.\n\nHai bậc cuối cùng là các báo cáo của người khác, được trích dẫn rõ ràng. Dự án này không xác minh các thông tin đó và không dựa vào chúng để đưa ra bất kỳ kết luận nào.\n\nTất cả các danh mục được theo dõi trên 419\n\nNguồn: https://phishdestroy.io/steam_dossier/vi/elite_skins#register\n\n09 / nguồn gốc và giới hạn\nKiểm tra phép tính\n\nChúng tôi công bố dữ liệu cục bộ và nguồn dữ liệu công khai. Phạm vi áp dụng của số liệu tiêu đề được giới hạn trong trang CSFloat tại thời điểm thu thập dữ liệu.\n\nGiới hạn và điều kiện riêng của Valve\n\nSteam Câu hỏi thường gặp về Chợ cộng đồng ↗ đã lưu trữ 2026-09-21 ↗ nêu mức giá tối đa ước tính khoảng $1,800. Giá Thỏa thuận người đăng ký ↗ đã lưu trữ 2026-09-21 ↗ quy định các hạn chế đối với việc sử dụng cho mục đích thương mại.\n\nGiá cả xuất phát từ đâu\n\nGiá, số lượng cổ phiếu niêm yết và phạm vi vốn hóa thị trường được trích dẫn từ cs2.sh dữ liệu thị trường API trong khuôn khổ gói đăng ký thương mại trả phí, sử dụng khóa cấp phép. Không có nền tảng thương mại điện tử nào bị trích xuất dữ liệu và cũng không có tài khoản hay thông tin đăng nhập của nền tảng thương mại điện tử nào được sử dụng. Nhà cung cấp tổng hợp dữ liệu từ BUFF, Youpin, CSFloat, Skinport, C5Game và Chợ cộng đồng Steam; tất cả các con số đều được trình bày bằng USD theo số liệu báo cáo. Mở bản kê khai nguồn gốc ↗ — nó ghi lại chính xác các điểm cuối, thời gian chụp và các giá trị băm SHA-256 của các bản chụp thô, do đó một người đọc độc lập có khóa riêng của mình có thể trích xuất cùng một dữ liệu và tính lại mọi con số trên trang này.\n\nNhững gì chúng tôi không thể có được\n\nGói đăng ký đã mua chỉ bao gồm các bản chụp nhanh hiện tại. Chúng tôi không có quyền truy cập vào các điểm cuối lịch sử và lưu trữ, và Trang này không đưa ra bất kỳ khẳng định nào về bất kỳ xu hướng nào, bất kỳ mức giá trong quá khứ nào hay bất kỳ sự thay đổi nào theo thời gian. Mọi thứ ở đây đều là một khoảnh khắc duy nhất, có ghi ngày tháng.\n\nBản đăng ký “CSFloat” trước đây\n\nPhiên bản đầu tiên của triển lãm này đã thống kê 245 các hạng mục từ một bản chụp nhanh duy nhất của danh mục CSFloat có ngày 20 tháng 9 năm 2026: bức ảnh chụp nhanh đó vẫn còn ở đây ↗. Số liệu hiện tại có phạm vi rộng hơn vì nó bao quát năm khu chợ thay vì chỉ một. Hai con số này được thống kê riêng biệt và không được cộng lại với nhau.\n\nTuyên bố về việc thi hành cụ thể của Valve\n\nBản cập nhật về tính năng giao dịch vật phẩm trong game “2016” của Valve ↗ đã lưu trữ 2026-09-21 ↗ nhắm vào các nhà điều hành cờ bạc sử dụng OpenID và các tài khoản tự động trên Steam. Phạm vi áp dụng của quy định này hẹp hơn so với việc cấm hoàn toàn mọi sàn giao dịch bên ngoài.\n\nRanh giới diễn giải\n\nĐây là các đề nghị, không phải giao dịch bán hàng. Một tên gọi trên thị trường có thể bao gồm nhiều mặt hàng thực tế với các chi tiết khác nhau về độ nổi, hoa văn hoặc nhãn dán. Sổ đăng ký này không phản ánh tổng giá trị thị trường cũng như ý định của Công ty Cổ phần Valve.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Đăng ký Elite Skins — Mức trần thị trường $1,800"
          },
          {
            "level": 2,
            "id": null,
            "text": "Mức sàn có thể đo lường được tính bằng đô la"
          },
          {
            "level": 3,
            "id": null,
            "text": "Tại sao đây là mức sàn chứ không phải mức ước tính"
          },
          {
            "level": 2,
            "id": null,
            "text": "Những gì giới hạn này bỏ sót"
          },
          {
            "level": 3,
            "id": null,
            "text": "★ Butterfly Knife | Doppler (Factory New)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Chiếc mũ của Steam đã khiến quá trình xác định giá vượt ra ngoài phạm vi Steam"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam đặt tiêu đề cho danh sách"
          },
          {
            "level": 3,
            "id": null,
            "text": "Dragon Lore: $10,940.85"
          },
          {
            "level": 3,
            "id": null,
            "text": "Giá và tỷ lệ chia sẻ phí chuyển nhượng"
          },
          {
            "level": 2,
            "id": null,
            "text": "Trần nhà cũng chặn được Dota 2"
          },
          {
            "level": 3,
            "id": null,
            "text": "Trăng lưỡi liềm anh hùng và tàn bạo"
          },
          {
            "level": 3,
            "id": null,
            "text": "Áo choàng nghệ thuật huyền bí"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ngôi sao năng lượng bị hư hỏng"
          },
          {
            "level": 2,
            "id": null,
            "text": "Kết quả này không phụ thuộc vào mức trần cụ thể"
          },
          {
            "level": 2,
            "id": null,
            "text": "Thực tế thì có rất ít sản phẩm như vậy được bày bán"
          },
          {
            "level": 3,
            "id": null,
            "text": "AWP | Truyền thuyết về Rồng"
          },
          {
            "level": 3,
            "id": null,
            "text": "M4A4 | Tiếng hú"
          },
          {
            "level": 3,
            "id": null,
            "text": "AK-47 | Hoa sen hoang dã"
          },
          {
            "level": 3,
            "id": null,
            "text": "AWP | Gungnir"
          },
          {
            "level": 2,
            "id": null,
            "text": "Mặt hàng càng đắt tiền thì càng nằm xa các địa điểm có thể quan sát được"
          },
          {
            "level": 2,
            "id": null,
            "text": "Tất cả các danh mục được theo dõi trên 419"
          },
          {
            "level": 2,
            "id": null,
            "text": "Kiểm tra phép tính"
          },
          {
            "level": 3,
            "id": null,
            "text": "Giới hạn và điều kiện riêng của Valve"
          },
          {
            "level": 3,
            "id": null,
            "text": "Giá cả xuất phát từ đâu"
          },
          {
            "level": 3,
            "id": null,
            "text": "Những gì chúng tôi không thể có được"
          },
          {
            "level": 3,
            "id": null,
            "text": "Bản đăng ký “CSFloat” trước đây"
          },
          {
            "level": 3,
            "id": null,
            "text": "Tuyên bố về việc thi hành cụ thể của Valve"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ranh giới diễn giải"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/vi/#market-gap-section",
          "https://phishdestroy.io/steam_dossier/vi/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/vi/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/vi/skin_atlas.html#grading",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-above-the-ceiling.json",
          "https://phishdestroy.io/steam_dossier/vi/elite_skins#selected",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://csmarketcap.com/search?minPrice=1800&amp;page=1",
          "https://store.steampowered.com/agreement/?l=english",
          "http://web.archive.org/web/20260921022032/https://store.steampowered.com/agreement/?l=english",
          "https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921021947/https://store.steampowered.com/oldnews/22883",
          "https://phishdestroy.io/steam_dossier/vi/#proxy-bypass-explainer",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/skinport-floor-over-cap.json",
          "https://docs.skinport.com/items",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-float-scarcity.json",
          "https://phishdestroy.io/steam_dossier/vi/elite_skins#register",
          "https://cs2.sh/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/csfloat-catalogue.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/vi/elite_skins.content.json",
      "export_json_sha256": "454614b7cc94c09df2806f2a02952083fc129e103985ae7da988c532f19658e0"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "vi/enforcement_audit.html",
      "language": "vi",
      "title": "Cục Thống kê Dân số Valve sẽ không công bố — Hồ sơ của Steam",
      "source_url": "https://phishdestroy.io/steam_dossier/vi/enforcement_audit",
      "source_html_sha256": "2c37f332fc1f47ed218b7484dfaddbe9a92bb816ce2d1d3e60d237445d192653",
      "exported_at": "2026-09-29T00:23:50.451Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "enforcement_audit.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/vi/enforcement_audit.pdf?v=print-20260929-v5",
        "sha256": "488652969f0522b7303a81e631a2fdf0a4c4ffb087131df187fcbf02986017ec",
        "bytes": 154807,
        "pages": 13
      },
      "integrity": {
        "signed_object": "enforcement_audit.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "enforcement_audit.content.json.asc",
        "digest_file": "enforcement_audit.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify enforcement_audit.content.json.asc enforcement_audit.content.json",
          "sha256sum -c enforcement_audit.content.json.sha256"
        ]
      },
      "content": {
        "text": "PHỤ LỤC VI — CUỘC ĐIỀU TRA DÂN SỐ MÀ VALVE KHÔNG CÔNG BỐ\nKiểm toán việc thực thi — Cuộc điều tra về lệnh cấm “1,182,811”\n\nChúng tôi không hỏi Valve diện tích trang trại là bao nhiêu. Chúng tôi đã được đếm nó.\n\nPHẦN NÀY CHỨNG MINH ĐIỀU GÌ\n\nCuộc kiểm toán này trình bày một cuộc điều tra thực nghiệm về các tài khoản bị cấm trên 1,182,811 bằng cách sử dụng điểm cuối chính thức GetPlayerBans của Valve, đồng thời đối chiếu các nhóm bot thương mại với các danh sách ghi nhận hành vi gian lận đã được xác minh. Kết quả chứng minh rằng hơn 63% bot bị cấm đã thanh toán phí truy cập cửa hàng $5.00 của Valve trước khi biện pháp xử lý được áp dụng, từ đó tạo ra hàng triệu doanh thu ban đầu. Hơn nữa, trong số 51,732 những kẻ lừa đảo đã bị kết án và được ghi nhận trong các danh sách lừa đảo, hơn 67% không phải đối mặt với bất kỳ lệnh cấm nào từ cộng đồng hay lệnh cấm giao dịch — điều này chứng tỏ rằng các biện pháp xử lý của nền tảng này chỉ nhằm mục đích thu lợi nhuận thương mại chứ không phải bồi thường cho nạn nhân.\n\n← Quay lại Bản tóm tắt dành cho lãnh đạo\n\nHiện chưa có con số chính thức nào về số lượng tài khoản tự động hóa đang hoạt động trên Steam. Tuy nhiên, điều này không cần phải là bí mật: không gian ID của Steam là một dãy số nguyên liên tục và Valve cung cấp khóa Web API để duyệt qua dãy này. Vì vậy, chúng tôi đã chọn cộng đồng lớn nhất tự xác định bản thân — cộng đồng ArchiSteamFarm — và quét qua từng thành viên một lần thông qua điểm cuối chặn (ban endpoint) của chính Valve. Cộng đồng này tự xác định vì ASF, khi khởi chạy lần đầu, sẽ tự động tham gia nhóm Steam trừ khi người dùng từ chối tham gia một cách rõ ràng hoặc bỏ chọn cài đặt tham gia nhóm (AutoJoinSteamGroup / Thống kê). Do cài đặt này được bật theo mặc định, danh sách thành viên nhóm bao quát một nhóm đối tượng rộng lớn: các mạng bot thương mại hoạt động với nhiều tài khoản, những người đam mê chơi game thỉnh thoảng để tài khoản chạy ngầm, và những người chơi bình thường đã chạy phần mềm trên tài khoản cá nhân của họ mà không bao giờ hủy đăng ký mặc định. Điều này khiến danh sách thành viên trở thành một bản thống kê thực tế về phạm vi tiếp cận tích lũy của phần mềm: 10,880,610 Tổng số tài khoản (bao gồm các thành viên không bị giới hạn đã được xác nhận qua 5,360,499 và đã vượt qua ngưỡng $5.00). Sau đó, chúng tôi đã đặt ra câu hỏi duy nhất thực sự quan trọng — “Valve” thực sự đã gây ra điều gì cho họ?\n\nTrang này không phải là gì. Đây không phải là lập luận cho rằng Valve nên cấm 10 triệu người, và cũng không phải là lời phàn nàn về những người “cày thẻ”. Mọi con số dưới đây đều được đưa ra vì một lý do duy nhất: Valve có cấm vĩnh viễn các cá nhân, và lý do được nêu rõ bằng văn bản là việc sử dụng Steam vào mục đích thương mại và tự động hóa. Điều này đánh giá cách quy tắc đó được áp dụng đối với cùng một hành vi trên quy mô lớn — bởi một nhà điều hành mà trong quá trình đó, họ thu phí mở khóa $5.00, phí giấy phép trò chơi và phí Thị trường Valve. Kết luận ở đây là sự bất đối xứng, chứ không phải việc “farm”.\n\nSố lượng M trong bộ sưu tập “10.88”Những kẻ lừa đảo lang thang (53.5k)100Kiểm toán trả phí so với kiểm toán miễn phí\n10,880,610Tổng số thành viên nhóm ASF đã đọc qua lệnh cấm do chính Valve đưa ra tại API (bao gồm cả tài khoản có giới hạn và không có giới hạn)\n88.97%Chưa từng bị cấm lần nào cả — các tài khoản 9,680,599 vẫn còn hoạt động\n63.06%Trong số các tài khoản bị cấm có những tài khoản đã thanh toán (5USD + chi phí) — 100,000 Phần SRSWOR (±0.39% MoE)\n67.77%Trong số những kẻ lừa đảo đã bị kết án trên diễn đàn 51,732, không có ai bị cấm tham gia vì hành vi lừa đảo (số liệu thống kê đầy đủ)\n01 — Quy mô\nMười triệu tài khoản, và chín trong số mười tài khoản vẫn chưa bị xâm phạm\n\nMột quần thể tự đếm số lượng của mình, được đọc một lần qua điểm cuối riêng củValve.\n\nTẠI SAO NÓ TỰ ĐẾM?\nASF sẽ tham gia nhóm thay cho bạn\n\nKhi chạy lần đầu, ArchiSteamFarm sẽ thiết lập Thống kê Mặc định được đặt thành “true” và tự động thêm vào nhóm “Steam” của Archi’s SC Farm. Người vận hành phải chủ động chọn không tham gia. Do đó, số lượng thành viên này là mức tối thiểu của số lượt cài đặt — chứ không phải mức tối đa. Những người vận hành đã tắt tính năng Thống kê sẽ không được tính vào; số lượt cài đặt thực tế ít nhất cũng bằng con số này.\n\nNHỮNG GÌ CHÚNG TÔI ĐÃ ĐỌC\n10,880,610 tổng số mục\n\nDanh sách thành viên của nhóm “API” đã trả về tổng cộng 10,880,610 SteamID64 — bao gồm cả những tài khoản bị giới hạn và không bị giới hạn. Trang nhóm của “Steam” hiển thị 5,360,499 (chỉ bao gồm những tài khoản không bị giới hạn). Mỗi mục trong danh sách đã được xử lý một lần qua ISteamUser/Lấy danh sách người chơi bị cấm trên 2026-09-23. Năm mươi lăm phút chỉ với một phím.\n\nCÂU TRẢ LỜI\n88.97% sạch sẽ\n\n1,200,011 có bất kỳ lệnh cấm nào từ Steam (11.03%). Các trường hợp khác 9,680,599 hoàn toàn không có bất kỳ thông tin nào được ghi nhận — Không phải là lệnh cấm cộng đồng, cũng không phải VAC, chẳng có gì cả. Hệ thống farm đó không bị xóa bỏ. Nó vẫn đang được để chạy. Chỉ cần một điều khoản như vậy, nhắm vào một người, là đủ để loại bỏ người đó vĩnh viễn.\n\nTrong số các tài khoản trên 10,880,610, có bao nhiêu tài khoản đã được Valve tiếp cận\n\nToàn bộ lực lượng được quét, được phân chia theo việc liệu Valve có áp dụng bất kỳ lệnh cấm nào hay không. Phần màu đỏ thể hiện tất cả những gì Valve đã từng thực hiện đối với hạm đội này.\n\n88.97%chưa bao giờ bị cấm\n11.03%\nKhông có bất kỳ lệnh cấm nào — 9,680,599 (88.97%)Có một số lệnh cấm liên quan đến “Steam” — 1,200,011 (11.03%)\n10,880,610Các thành viên nhóm ASF đã quét\n9,680,599Chưa từng bị cấm — 88.97%\n1,200,011Áp dụng bất kỳ lệnh cấm nào — 11.03%\n55 phútĐể đếm tất cả, trên một phím “API”\nChi phí mà đội tàu này đã phải chi trả để Valve tồn tại\n\nĐây không phải là ước tính về thu nhập của trang trại. Đây là mức chi tiêu tối thiểu mà trang trại đã chi tại cửa hàng của “Valve” — được tính ra dựa trên quy tắc riêng củValve, áp dụng cho con số được nêu ở trên.\n\nSố liệu thống kê “10,880,610” bao gồm toàn bộ danh sách thành viên nhóm ASF như được trả về bởi trang API — bao gồm cả các tài khoản có giới hạn và không có giới hạn. Bản thân trang Steam Tài khoản người dùng có giới hạn Trang này nêu rõ rằng các tài khoản có giới hạn không được tính vào Steam tình trạng thành viên nhóm (các tài khoản này không được tính vào số lượng thành viên nhóm hiển thị), nhưng vẫn có thể xuất hiện trong danh sách thành viên cơ sở. Tập con không bị giới hạn — các tài khoản đã chi tiêu ít nhất $5.00 tại cửa hàng Steam — chính xác là 5,360,499 — con số Steam hiển thị trên trang nhóm, theo quy định của chính Steam thì con số này không bao gồm các tài khoản bị giới hạn. Cách tính mức tối thiểu $5.00 chỉ áp dụng cho tập con không bị giới hạn đó.\n\n5,360,499thành viên không có giới hạn\n(Số lượng nhóm được hiển thị trên Steam)\n×\n$5.00Mức tối thiểu riêng của Valve\nđể không còn bị giới hạn nữa\n=\n$26,802,495giới hạn chi tiêu tại cửa hàng\nbởi tập con không giới hạn\n\nĐây là mức thấp nhất của số tiền mà Valve đã nhận được từ phần không bị giới hạn của đội tàu — không phải là ước tính doanh thu, cũng không phải là tuyên bố về lợi nhuận. Chi phí thực tế trên mỗi tài khoản cao hơn đối với phần lớn các trường hợp; con số $5.00 chỉ là ngưỡng tối thiểu bắt buộc mà thôi.\n\nPhí thu hoạch thứ cấp: tối đa 66.7% tính trên khối lượng hàng hóa được nuôi trồng. Ngoài phí tham gia $26.8M, mỗi lần bán tháo thẻ và hàng hóa trên Thị trường Cộng đồng đều phải trả cho Valve một mức phí tối thiểu bắt buộc là hai cent ($0.01Steam + $0.01). Đối với các thẻ và mặt hàng rác thông thường 3-cent, Valve trích ra 2 xu từ 3 xu — tương đương với việc cắt giảm thực tế 66.67% xu để có lợi cho Valve, vượt xa mức lãi suất quảng cáo 15% được công bố.\n\nLưu ý quan trọng về dân số: Việc tham gia nhóm không phải là bằng chứng cho thấy mọi tài khoản đều là bot chuyên dụng, cũng như không phản ánh hết tất cả các bot trên Steam. Theo mặc định, ASF sẽ tự động đăng ký các tài khoản vào nhóm cộng đồng của mình ngay khi khởi chạy; trừ khi người dùng chủ động bỏ chọn hoặc vô hiệu hóa cờ cấu hình đó (AutoJoinSteamGroup), người chơi thường xuyên, những người chỉ chơi một lần và các thành viên cộng đồng vẫn có tên trong danh sách cùng với các đội tàu khai thác tự động. Hơn nữa, lệnh cấm do hệ thống phát hiện hành vi gian lận (Steam) không kèm theo lý do công khai. Kết luận này là tỷ lệ thực nghiệm được ghi nhận trên toàn bộ nhóm người dùng liên quan đến phần mềm này, chứ không phải là phán quyết riêng lẻ đối với bất kỳ tài khoản nào. Tổng hợp, có thể tái hiện: asf-ban-census-2026-09-23.json.\n\n02 — Địa lý\nNơi đội tàu hoạt động\n\nChỉ có 8.5% trong số các tài khoản bị cấm là có khai báo quốc gia. Trong số những tài khoản đã khai báo, Hoa Kỳ chiếm tỷ lệ lớn nhất.\n\nMột hồ sơ trên Steam có trường “quốc gia” là tùy chọn. 100,413 của các tài khoản bị cấm trên 1,182,811, hãy điền vào đây — 8.5%.† Trong số nhóm thiểu số đó, Hoa Kỳ dẫn đầu với 15.5%,, tiếp theo là Ukraine, Trung Quốc và Nga, còn phần còn lại trải dài thành một dải dài khắp châu Âu, Mỹ Latinh và Đông Nam Á. Không ai kiểm chứng dữ liệu này: Afghanistan nằm trong top 10, điều này cũng gần đúng với thực tế. Các quốc gia khác 91.5% bị bỏ qua thay vì được xếp hạng, do đó những gì được trình bày dưới đây chỉ phản ánh hình ảnh của một nhóm thiểu số tự chọn — không phải là bản đồ của toàn bộ đội tàu, và cũng không phải là cơ sở để xác định nơi điều hành đội tàu đó.\n\nCác tài khoản bị khóa theo quốc gia được khai báo\n\n15 là những quốc gia đứng đầu trong số các tài khoản bị cấm trên 100,413 do tiết lộ vị trí công khai. Tỷ lệ phần trăm này tương ứng với tập con các tài khoản đó. Di chuột vào để xem số liệu.\n\n0%\n5%\n10%\n15%\n20%\nUnited States\nUkraine\nChina\nRussia\nCanada\nAustralia\nJapan\nBrazil\nGermany\nAfghanistan\nUnited Kingdom\nRomania\nFrance\nPhilippines\nIndia\n\nVị trí được đọc từ Lấy tóm tắt người chơi đối với tập con bị cấm. Trường này do chủ tài khoản thiết lập và không có ai xác minh, do đó, một địa chỉ thoát VPN hay một mục nhập đùa cợt cũng được tính như một mục nhập thực sự.\n\n03 — Độ tươi ngon\nCác khoản phải thu gần đây, không phải là các khoản tồn đọng từ trước\n\nDựa trên thời điểm tạo tài khoản, nhóm người dùng bị cấm này là những người mới, chứ không phải là những người còn sót lại từ thời kỳ thẻ bài.\n\nNếu đây là một mớ hỗn độn từ lâu đang dần được dọn dẹp, các tài khoản bị cấm sẽ chủ yếu tập trung vào những năm đầu của thời kỳ thẻ sưu tập. Nhưng thực tế lại hoàn toàn ngược lại. Trong số 1,132,852 các tài khoản bị cấm có hiển thị ngày tạo, 70% được tạo ra trong phiên bản 2020 trở lên, và gần một nửa trong số đó được tạo ra kể từ 2023. Con số này tăng từ 59,175 được tạo ra tại 2017 lên mức cao nhất là 227,030 được tạo ra chỉ trên 2024. Mỗi người trong số họ đều đã vượt qua cổng cửa hàng $5.00 trước khi cửa hàng kịp nhận thẻ, nên phí vào cửa đã được thu từ mỗi người.\n\nThời điểm các tài khoản bị cấm được tạo ra\n\nNăm tạo tài khoản của các thành viên bị cấm trên 1,132,852 – những tài khoản hiển thị ngày tạo. Nhóm này là 2020–2026, chứ không phải thời kỳ thẻ sưu tập 2013–2015. Đỉnh điểm: 2024. Di chuột vào để xem số lượng.\n\n0k\n63k\n125k\n188k\n250k\n'13\n'14\n'15\n'16\n'17\n'18\n'19\n'20\n'21\n'22\n'23\n'24\n'25\n'26\n70%Các tài khoản bị khóa được tạo từ ngày 2020 trở đi\n227,030Các tài khoản bị khóa được tạo trên 2024 — năm đạt đỉnh cao\n51,701Rãnh “2021”, nằm giữa hai năm đạt đỉnh — chưa có lời giải thích\n2003→2026Dữ liệu có sẵn, nhưng khối lượng chỉ bao gồm sáu năm gần đây nhất\n\nNgày sáng lập là Lấy tóm tắt người chơi đối với tập con các tài khoản bị cấm, đã được loại trừ trùng lặp theo SteamID64. Ngày tạo là ngày tài khoản được lập, chứ không phải ngày tài khoản bị cấm hay ngày bắt đầu hoạt động “farming”; thông tin này được xem xét ở đây như bằng chứng cho thấy độ mới của nhóm người chơi, chứ không phải để đánh giá ý định. Có ba điều mà biểu đồ này không thể hiện:\n\nMột xu hướng sau sự kiện “2024.” Một tài khoản được tạo tại 2025 hoặc 2026 có thời gian tồn tại ngắn hơn nên chưa bị cấm, còn 2026 bao phủ khoảng thời gian chín tháng — do đó, chuỗi 227,030 → 121,070 → 16,534 là hành vi kiểm duyệt, chứ không phải sự suy giảm.\nTỷ lệ cấm. Số năm kể từ khi tạo tài khoản chỉ được thống kê đối với các tài khoản bị khóa, do đó không có mẫu số. Chỉ riêng sự gia tăng số lượng người dùng đã đủ để tạo ra xu hướng này.\nTại sao “2021” lại sụp đổ? 51,701 nằm giữa 105,821 và 104,641,, ở vị trí thấp hơn một nửa so với cả hai trang lân cận. Không có thông tin công khai nào giải thích điều này; phần này được để nguyên như vậy thay vì được làm mịn.\n04 — Thời điểm\nKhi “Valve” được thực hiện, việc thực hiện đó diễn ra trong năm đầu tiên\n\nLý do hiển nhiên để giải thích tại sao trang web 88.97% vẫn chưa bị can thiệp chính là do lượng công việc tồn đọng. Tuy nhiên, các lệnh cấm đã được ban hành từ lâu lại cho thấy điều ngược lại.\n\nTài khoản đó đã tồn tại được bao lâu khi bị cấm?\n\nThời gian sử dụng tài khoản tại thời điểm bị cấm, đối với các tài khoản bị cấm trên 293,750 có cả ngày tạo tài khoản và ngày bị cấm gần nhất. Hơn một nửa trong số đó đã bị phát hiện vi phạm trong năm đầu tiên.\n\n0%\n10%\n20%\n30%\n40%\n<6 mo\n33.7%\n6–12 mo\n21.5%\n1–2 y\n20.6%\n2–5 y\n14.3%\n5 y+\n10.0%\n55.1% inside the first year\nBị cấm trong năm đầu tiên — 55.1%Sau đó bị cấm — 44.9%\n0.80 yTuổi trung vị của tài khoản tại thời điểm bị cấm\n55.1%Bị cấm trong năm đầu tiên kể từ khi tạo tài khoản\n33.7%Bị cấm trong vòng sáu tháng đầu tiên\n293,750Các tài khoản có cả hai ngày\n\nĐây là câu trả lời cho lập luận phản bác hiển nhiên đó. Nếu 88.97% của đội tàu vẫn chưa bị xử lý chỉ vì việc thi hành luật diễn ra chậm chạp — do lượng công việc tồn đọng đang dần được giải quyết — thì các lệnh cấm đó làm người dùng sẽ có xu hướng già đi. Thực tế lại ngược lại: độ tuổi trung vị của các tài khoản bị khóa là chín tháng rưỡi tuổi, và một nhóm thứ ba — 33.7% — đã bị bắt trong vòng sáu tháng. Khi Valve can thiệp vào nhóm này, họ hành động rất nhanh. Chín trong mười người vẫn đang lẩn trốn không phải chờ đợi trong hàng.\n\nTuổi tại thời điểm cấm = ngày tạo từ Lấy tóm tắt người chơi trừ đi ngày cấm được ngụ ý bởi Số ngày kể từ lần cấm gần nhất, xem thêm tại 2026-09-23. Giá trị này chỉ được tính toán khi cả hai giá trị đều có sẵn: 293,750 trong số các tài khoản bị cấm tại 1,200,011. Các tài khoản còn lại không có giá trị “số ngày kể từ” và bị loại trừ, chứ không phải được giả định — do đó, hãy hiểu đây là cấu trúc của tập con có ngày tháng, chứ không phải của từng trường hợp bị cấm.\n\n05 — Thực chất lệnh cấm này là gì\nKhi Valve thực sự hoạt động, nó cũng không ngăn chặn được bot\n\nTrong số các trang web 11% có áp dụng bất kỳ lệnh cấm nào, hãy xem đó là lệnh cấm nào.\n\nLệnh cấm không phải là lệnh cấm. Trong số các tài khoản 1,200,011 mà Valve đã báo cáo, 99.8% mang theo một cộng đồng lệnh cấm — một hạn chế áp dụng cho các diễn đàn, hồ sơ và nhóm, nhưng không ảnh hưởng gì đến bot giao dịch. Tài khoản đó vẫn có thể nhận thẻ, vẫn có thể giao dịch và vẫn có thể chuyển kho hàng. Các tài khoản thuộc danh mục 22.2% đều bị cấm chơi ít nhất một trò chơi, còn các tài khoản thuộc danh mục 3.9% bị cấm VAC; các danh mục này có phần trùng lặp, nên không được cộng dồn. Hình phạt duy nhất thực sự ngăn chặn hoạt động giao dịch — lệnh cấm kinh tế/giao dịch — được áp dụng cho các tài khoản thuộc danh mục 5,214. Chúng tôi không dựa vào con số đó để kết luận — lệnh cấm giao dịch nói chung rất hiếm gặp trên Steam. Ý nghĩa của biểu đồ này đơn giản hơn: ngay cả tỷ lệ phần trăm Valve có Touch vẫn tiếp tục giao dịch.\n\nLý do thực sự khiến những người thuộc nhóm “11%” bị cấm\n\nTỷ lệ phần trăm của từng loại lệnh cấm so với tổng số thành viên được quét bởi 10,880,610. Mỗi tài khoản có thể bị áp dụng nhiều hơn một loại lệnh cấm. Di chuột vào để xem số lượng.\n\n0%\n4%\n8%\n11%\n15%\nCommunity ban\nGame ban\nVAC ban\nEconomy / trade ban\n\nLệnh cấm “Steam” không có trường “lý do”, do đó không có lệnh cấm nào trong số này được quy cụ thể cho việc “farm” thẻ — đây là sự kết hợp của các loại lệnh cấm hiện có, đi kèm với những gì mỗi loại thực sự hạn chế. Lệnh cấm từ cộng đồng không ngăn cản việc giao dịch; còn lệnh cấm kinh tế / giao dịch thì có. Tổng hợp: asf-ban-census-2026-09-23.json.\n\n06 — Nhóm dân số còn lại\nNhững kẻ lừa đảo trên Valve đã bị vạch trần: 51,732 – Tổng điều tra dân số đầy đủ\n\nMột danh sách thứ hai, độc lập — các trường hợp gian lận được cộng đồng xác nhận — được so sánh với cùng một cơ sở dữ liệu chính thức về gian lận và lạm dụng (API).\n\nCó thể cho rằng nhóm người dùng tự động hóa chỉ là những kẻ lười biếng vô hại. Nhưng không thể nói như vậy về nhóm thứ hai. SteamRep là một cơ sở dữ liệu uy tín cộng đồng đã hoạt động từ lâu; một tài khoản bị gắn nhãn BỊ CẤM Một kẻ lừa đảo đã bị cộng đồng đó kết luận là có tội, dựa trên bằng chứng từ các nạn nhân và nhật ký trò chuyện giao dịch được ghi lại. Chúng tôi đã hoàn tất việc thống kê 100% đối với tất cả 51,732 các hồ sơ có trạng thái \"BỊ CẤM\" so với trang web chính thức của Steam tại địa chỉ API (ISteamUser/Lấy danh sách người chơi bị cấm/phiên bản 1) — và chỉ tính những biện pháp trừng phạt liên quan đến hành vi lừa đảo. Lệnh cấm VAC áp dụng đối với việc sử dụng phần mềm gian lận trong trò chơi (aimbot, wallhack); biện pháp này không ảnh hưởng gì đến người giao dịch và không phải là bằng chứng cho thấy Valve đã xử lý hành vi gian lận, do đó không được tính là biện pháp xử lý gian lận.\n\nTrong toàn bộ danh sách tài khoản trên 51,732-, những tài khoản 67.77% — 35,059 đã bị xác định là kẻ lừa đảo — không có bất kỳ lệnh cấm nào liên quan đến hành vi lừa đảo từ Valve: Họ vẫn có thể giao dịch, vẫn có thể gửi yêu cầu kết bạn đến các nạn nhân mới, vẫn có thể nhắn tin. Chỉ có 32.23% mới bị áp dụng lệnh cấm cộng đồng hoặc cấm giao dịch, và lệnh cấm giao dịch — biện pháp duy nhất thực sự ngăn chặn việc chuyển giao kho đồ — chỉ áp dụng cho 18.81% (các tài khoản 9,731). Ngoài ra, 12.81% (tài khoản 6,627) còn bị cấm VAC hoặc cấm chơi game chỉ vì gian lận trong trò chơi, trong khi vẫn hoàn toàn không bị hạn chế trong việc giao dịch trên Steam.\n\nNhững đối tượng lừa đảo đã được xác nhận, dựa trên việc Valve có áp dụng lệnh cấm liên quan đến hành vi lừa đảo hay không (Danh sách toàn diện)\n\nTất cả các hồ sơ bị cấm trên SteamRep tại 51,732, được phân loại theo việc Valve áp dụng lệnh cấm cộng đồng hay lệnh cấm giao dịch. Các lệnh cấm VAC và lệnh cấm trong trò chơi không được tính vào — vì chúng không liên quan đến hành vi gian lận. Di chuột vào để xem số lượng.\n\n0%\n18%\n35%\n53%\n70%\nNo scam-relevant ban\nCommunity or trade ban\n0%\n6%\n13%\n19%\n25%\nCommunity ban\nTrade / economy ban\nVAC (not fraud)\nGame ban\n51,732Kiểm tra các hồ sơ bị cấm trên SteamRep — Danh sách đầy đủ tại 100%\n35,059Không bị cấm vì liên quan đến lừa đảo (67.77%)\n18.81%Hãy thực thi lệnh cấm giao dịch nhằm chấm dứt các hành vi lừa đảo (9,731)\n32.23%Cổ phiếu Valve đã bị cấm giao dịch trên thị trường cộng đồng hoặc thị trường chuyên ngành (16,673)\n\nSteamRep là một cơ sở dữ liệu danh tiếng của bên thứ ba, được cộng đồng đánh giá, chứ không phải là quyết định của Valve — và đó chính là điểm mấu chốt: bằng chứng bên ngoài, được so sánh với những gì chính Valve đã thực hiện. Tất cả các hồ sơ bị CẤM (51,732) từ tệp xuất chuẩn đều được đối chiếu trực tiếp với ISteamUser/Lấy danh sách người chơi bị cấm/phiên bản 1. “Liên quan đến lừa đảo” có nghĩa là bị cấm tham gia cộng đồng hoặc bị cấm tham gia hoạt động kinh tế/thương mại; các hình thức cấm VAC (12.81%) và cấm chơi game (3.86%) được tính riêng vì chúng nhằm xử lý hành vi gian lận, chứ không phải lừa đảo. Bộ dữ liệu kiểm toán đầy đủ: steamrep_steam_bans.csv.\n\nHai nhóm dân số, một kết quả\n\nĐây không phải là cùng một nhóm người và cũng không phải là cùng một hành vi. Một bên là mười triệu tài khoản tự động; bên kia là năm mươi ba nghìn kẻ lừa đảo đã bị kết án. Điểm chung duy nhất giữa chúng là hình thức của kết quả: 9 trên 10 tài khoản nông trại chưa bao giờ được sử dụng, và hơn hai phần ba (67.77%) số đối tượng lừa đảo đã được xác nhận không phải chịu bất kỳ hình thức xử phạt nào liên quan đến hành vi lừa đảo. Lệnh cấm cộng đồng Valve thực sự được áp dụng một cách tùy tiện, chủ yếu nhằm hạn chế quyền truy cập vào các diễn đàn và hồ sơ cá nhân, chứ không phải để ngăn chặn hoạt động giao dịch. Nút báo cáo, cơ sở dữ liệu uy tín, lệnh cấm nhằm ngăn chặn hành vi lừa đảo: tất cả đều có sẵn, nhưng đều chưa được tận dụng đầy đủ. So sánh điều đó với các trường hợp từ chối đã được lưu trữ trong hồ sơ chính, nơi cùng một công ty vĩnh viễn xóa một tài khoản duy nhất và viện dẫn việc sử dụng thương mại và tự động hóa làm lý do — điều khoản này không phải là vô hiệu, mà là rất rõ ràng.\n\n07 — Vụ lừa đảo tài khoản “5.00” và vụ chiếm quyền kiểm soát tài khoản\nKiểm toán thực nghiệm tài khoản 100,000-: các mạng botnet không phải là những tài khoản miễn phí dùng một lần\n\nLogic lấy mẫu thống kê và chứng minh toán học: tại sao việc sử dụng bất kỳ tài khoản 100,000 nào khác cũng cho kết quả hoàn toàn giống nhau.\n\nLập luận chính mà Valve đưa ra trước các cơ quan quản lý và tổ chức bảo vệ người tiêu dùng là các hành vi lừa đảo tự động và “farming” được thực hiện thông qua các tài khoản “dùng một lần” miễn phí, tồn tại trong thời gian ngắn và nhanh chóng bị khóa. Theo các quy định đã được Valve công bố, một tài khoản là Số lượng có hạn cho đến khi nó chi tiêu ít nhất 5.00 USD trong cửa hàng “Steam”, khiến tài khoản đó không thể thực hiện các giao dịch, gửi yêu cầu kết bạn và sử dụng các tính năng “API”. Chúng tôi đã kiểm chứng trực tiếp tuyên bố này bằng cách kiểm tra trạng thái kiếm tiền từ một mẫu đại diện, được lựa chọn một cách chặt chẽ về mặt toán học của 100,000 các tài khoản bị khóa trên Steam được trích xuất từ tập dữ liệu siêu dữ liệu hồ sơ “1,182,811” của chúng tôi.\n\nQUY TRÌNH LẤY MẪU (SRSWOR)\n100,000 Lát cắt khách quan\n\nTrích từ N = 1,182,811 đã chọn ngẫu nhiên các tài khoản Steam bị cấm duy nhất bằng phương pháp Lấy mẫu ngẫu nhiên đơn giản không thay thế thông qua một bộ tạo số ngẫu nhiên (PRNG) đồng nhất về mặt mật mã. Mỗi tài khoản đều có xác suất được chọn như nhau là P = n / N ≈ 8.45%, giúp loại bỏ hoàn toàn sai lệch do sự sống sót và sai lệch do hoạt động.\n\nCHỨNG MINH TOÁN HỌC\nĐộ sai số < ±0.4%\n\nÁp dụng công thức Điều chỉnh Dân số Hữu hạn (FPC) tại một 99% Khoảng tin cậy (Z = 2.576):\nMoE = Z × √[p(1-p)/n] × √[(N-n)/(N-1)] ≈ ±0.39%\n\nKHẢ NĂNG TÁI TẠO\nTại sao bất kỳ giá trị k nào trong công thức “100” đều cho kết quả giống nhau\n\nVì độ lệch chuẩn nằm trong khoảng ±0.4% ở mức độ tin cậy 99%, Việc lấy bất kỳ mẫu tài khoản 100,000-độc lập nào khác đều được đảm bảo về mặt toán học là sẽ nằm trong khoảng 63.06% ± 0.39% (62.67% đến 63.45%). Mẫu khảo sát này phản ánh toàn bộ 1.18 triệu người bị cấm.\n\nKết quả kiểm toán đã hoàn toàn bác bỏ lập luận bào chữa về “bot dùng một lần”. Trong số các tài khoản 100,000 được kiểm toán thông qua giao diện hồ sơ XML cũ của Steam: 61,490 Các tài khoản (63.06% về các loại tài khoản) là các tài khoản Không giới hạn (Trả phí) đã chi tiêu ít nhất $5.00 trên trang web Steam. Chỉ 36,021 (36.94%) là các tài khoản miễn phí có giới hạn, trong khi các tài khoản 2,489 chưa được cấu hình hoặc là tài khoản riêng tư.\n\n100,000 Tài khoản bị cấm: Tài khoản trả phí (5USD + chi tiêu tại cửa hàng) so với tài khoản miễn phí có giới hạn\n\nKiểm toán thực nghiệm trên 100,000 đối với các tài khoản bị cấm được chọn ngẫu nhiên. Hơn 63% đã vượt qua cổng thanh toán của Valve. Di chuột vào để xem số liệu.\n\n0%\n16%\n33%\n49%\n65%\nNon-limited (Paid ≥ $5.00)\nLimited (Free < $5.00)\n100,000Dân số được lấy mẫu (SRSWOR, N =1.18M)\n63.06%Tài khoản trả phí không giới hạn (tài khoản 61,490)\n±0.39%Độ lệch chuẩn tại khoảng tin cậy 99%\n~745,800Số tài khoản trả phí được suy diễn từ tập dữ liệu “1.18” có dung lượng M\nThực trạng cơ bản: Việc thanh lý tài khoản trên quy mô công nghiệp\n\nTại sao lại có tới 63% số tài khoản bị cấm trong mẫu khảo sát là những tài khoản trả phí đã chi tiêu tiền thật tại cửa hàng của Valve? Những người điều hành mạng bot không bao giờ tự bỏ ra hàng triệu để tạo các tài khoản dùng một lần. Tỷ lệ này cho thấy quy mô của các tài khoản bị xâm phạm và chiếm quyền điều khiển luân chuyển trong hệ sinh thái.\n\nThang đo này có thể quan sát trực tiếp trên các nền tảng ngầm: trên các sàn giao dịch như FSB Market (một tên gọi ẩn danh; tên gốc được giấu đi ở đây), trên 550,000 Steam tài khoản (nhật ký đánh cắp, dữ liệu thu thập từ các vụ lừa đảo qua email, tấn công bằng thông tin đăng nhập có sẵn) luôn được rao bán tại bất kỳ thời điểm nào (phishdestroy.io/thông-tin-trực-tiếp). Sàn giao dịch xác thực người mua và người bán bằng OpenID Steam của chính Valve, và cả hai bên đều không FSB Market cũng không the associated forum bị chặn bởi bộ lọc liên kết của Valve.\n\nTheo quy định tại Mục 06,, trang web Valve không chủ động ngăn chặn hành vi gian lận này: 67.77% các đối tượng lừa đảo đã được cộng đồng xác nhận không bị áp dụng bất kỳ lệnh cấm lừa đảo nào trên Steam, và 88.97% thuộc đội ngũ tự động hóa vẫn hoàn toàn không bị can thiệp. Các tài khoản này hoạt động tự do, xác thực thông qua các API chính thức và thực hiện giao dịch trong toàn bộ hệ sinh thái mà hầu như không gặp bất kỳ trở ngại nào.\n\nSơ đồ kiến trúc về bằng chứng pháp y và thực thi pháp luật\nQuy trình tương tác từ 10.88M tài khoản đã được quét đến 100k mẫu dữ liệu thực nghiệm và 53.5k đối tượng lừa đảo đã được xác nhận · Nhấp vào các liên kết để xem bằng chứng thô\nBảng xếp hạng01 · 10.88: Tổng điều tra đội tàu tự động hóa\nCộng đồng tự nhận là chuyên về tự động hóa lớn nhất trên Steam đã lần lượt bị áp dụng lệnh cấm chính thức của Valve tại API. Điều này chứng minh rằng các đội bot thương mại vẫn hoạt động một cách 88.97% không bị trừng phạt trong khi phải trả hàng chục triệu cho phí tham gia.\n9,680,599 88.97% Hoạt động & Hoang sơ\nCác tài khoản đang chạy phần mềm tự động và chưa từng bị cấm dưới bất kỳ hình thức nào trong lịch sử.\nDữ liệu JSON thô từ cuộc điều tra dân số (1.2 KB) ↗Xem Mục “01” ↗\n$26,802,495 Mức doanh thu tối thiểu tại cửa hàng\nĐược thu thập bởi Valve từ các thành viên không giới hạn của 5,360,499 đã vượt qua ngưỡng tham gia tối thiểu là $5.00.\nKiểm toán hiệu quả sử dụng thẻ ↗Valve $ Câu hỏi thường gặp về Quy tắc “5” ↗\n1,200,011 11.03% Tập con được đánh dấu\n99.8% Chỉ áp dụng các lệnh cấm trong cộng đồng về mỹ phẩm; hoạt động giao dịch vẫn diễn ra bình thường trên các tài khoản thuộc 99.95%.\nPhân tích theo loại ban ↗Cơ sở dữ liệu bị cấm (60.4 MB) ↓\nKiểm toán lấy mẫu thực nghiệm cấp độ 02 · 100,000-(N = 1,182,811)\nMột lát cắt đại diện SRSWOR được đánh giá thông qua các điểm cuối XML cũ. Độ sai số đã được chứng minh toán học là < ±0.4% tại khoảng tin cậy 99%. Điều này bác bỏ khẳng định rằng các bot bị cấm là những tài khoản dùng một lần miễn phí.\n61,490 (63.06%) Tài khoản trả phí không giới hạn (5+ chi tiêu)\nHơn 63% tài khoản bị cấm liên quan đến các giao dịch trả phí. Ước tính có khoảng ~745,800 tài khoản trả phí (mức sàn tham gia là $3.73triệu trở lên) trong nhóm tài khoản bị cấm.\nTệp CSV kết quả giới hạn (2.1 MB) ↓100k Báo cáo pháp y ↗\n36,021 (36.94%) Tài khoản miễn phí có giới hạn (<5.00 USD)\nMột số ít tài khoản bị cấm phù hợp với đặc điểm “bot dùng một lần rồi bỏ” mà Valve đưa ra. Các tài khoản 2,489 là những tài khoản chưa được cấu hình hoặc ở chế độ riêng tư.\n100k Mẫu tệp CSV (8.5 MB) ↓Phân tích chi tiêu MD ↗\n34.67% vs 63.93% Kiểm toán việc làm sạch dữ liệu hồ sơ\nValve đã xóa các biệt danh và khôi phục về SteamID64 gốc trên các tài khoản tại 34,673, nhưng vẫn giữ nguyên hoàn toàn các tên tùy chỉnh và ảnh đại diện trên các tài khoản bị cấm tại 63,928.\nPhần Vệ sinh ↗Tổng quan về lộ trình ↗\n34.59% Di sản Các tài khoản tồn đọng (Được tạo vào ngày 2003–2019)\nHơn một phần ba số tài khoản bị cấm đã được đăng ký tại 5 đến 20cách đây nhiều năm, chứng tỏ việc chiếm đoạt tài khoản trên quy mô công nghiệp nhắm vào những người chơi lâu năm của Steam.\nNiên biểu theo độ tuổi ↗Các trường hợp từ chối hỗ trợ ↗\nCấp độ 03 · 51,732 Danh sách những kẻ lừa đảo đã được SteamRep xác nhận\nDanh sách đầy đủ trên 100% về những kẻ lừa đảo đã bị cộng đồng xử lý, kèm theo nhật ký trò chuyện với nạn nhân và bằng chứng giao dịch, được đối chiếu với các API cấm chính thức trên Steam. Điều này chứng minh sự thất bại có hệ thống trong việc thực thi các biện pháp xử lý.\n35,059 (67.77%) Không có lệnh cấm vì lừa đảo (Miễn trừ hoàn toàn)\nHơn hai phần ba số đối tượng lừa đảo đã được xác minh không bị áp dụng bất kỳ lệnh cấm nào về “Cộng đồng” hay “Giao dịch” từ Valve. Họ vẫn hoạt động bình thường để thực hiện các giao dịch và tìm kiếm nạn nhân mới.\nCác lệnh cấm trong SteamRep API (2.6 MB) ↓Báo cáo kiểm toán SteamRep ↗\n9,731 (18.81%) Kinh tế / Các lệnh cấm thương mại\nĐây là biện pháp trừng phạt duy nhất có thể chấm dứt việc thanh lý hàng tồn kho. Chỉ áp dụng đối với chưa đến một phần năm số đối tượng lừa đảo đã được xác nhận.\nNguồn SteamRep (2.1 MB) ↓Xem phần “06” ↗\n6,627 (12.81%) Các lệnh cấm gian lận không liên quan (Chỉ áp dụng cho VAC)\nBị cấm vì sử dụng aimbot/wallhack trong các trò chơi, trong khi các hoạt động giao dịch Steam và lừa đảo của họ vẫn 100% tiếp tục diễn ra.\nPhân tích mức độ không liên quan của VAC ↗Lịch trình bảo mật ↗\nCấp độ 04 · Các vụ tấn công làm biến dạng trang Wiki và các vụ vi phạm an ninh hệ thống vào tháng 8 2026\nViệc làm biến dạng tài liệu nội bộ dành cho nhà phát triển, việc hạn chế quyền truy cập của các biên tập viên cộng đồng và các sự cố về bảo mật vùng biên chưa được khắc phục đã được ghi nhận trong bộ tài liệu chứng cứ.\n1,200+ Ban biên tập Nhật ký xung đột của VDC Wiki\nCác biên tập viên cộng đồng đang cố gắng khắc phục các liên kết lừa đảo và các mẫu thư rác đã bị các bộ lọc tự động chặn một cách có hệ thống, trong khi nhân viên của Valve lại phớt lờ các cảnh báo.\nBáo cáo về các cuộc xung đột ở Nga (127 KB) ↗Báo cáo phân loại (66 KB) ↗\n12 TB Không xác thực Sự cố rò rỉ tài sản vào tháng 8 trên 2026 (CWE-284)\nValve đã lưu trữ 12 terabyte mã nguồn nội bộ và các bản dựng nguyên mẫu trên một điểm cuối công khai mà không có cơ chế xác thực trong nhiều tuần.\nValve Hồ sơ về sự thiếu năng lực (43 KB) ↗Kho lưu trữ bằng chứng ↗\nVụ vi phạm an ninh tại CEVA Logistics Tháng 8: Sự cố rò rỉ thông tin cá nhân (PII) của khách hàng tại2026\nTên, địa chỉ và số điện thoại của những người mua bộ bài “Steam” tại châu Âu đã bị rò rỉ từ đối tác hậu cần của trang web Valve, dẫn đến hàng loạt vụ lừa đảo qua email.\nBiên bản sự cố ↗Hồ sơ thi hành ↗\n\nHiện tượng nhiễu do lấy mẫu: banned_100k_slice.csv (Tài khoản 100,000). Kết quả kiểm toán: slice_100k_limited_results.csv. Báo cáo phân tích đầy đủ: BANNED_100K_PHÂN TÍCH_PHÁP Y.md.\n\n08 — Phương pháp và giới hạn\nCách hiểu nội dung này, và những điều mà nó không khẳng định\n\nBa nhóm dân số đại diện, một nhóm “API”, phương pháp lấy mẫu thống kê nghiêm ngặt.\n\nTHỰC THI VÀ THẨM QUYỀN\n\nCuộc điều tra dân số ASF, phần trích xuất từ tài khoản SRSWOR trên 100,000-và việc đối chiếu chéo trên SteamRep đã được thực hiện bởi các thành viên của PhishDestroy thông qua các tài khoản Steam và khóa Web API của riêng họ, như một phần trong nỗ lực công khai của Liên minh nhằm chống lừa đảo và cấm các hành vi gian lận. Tác giả của tài liệu này không sở hữu khóa Web API từ Steam và cũng không tự mình thực hiện bất kỳ lần quét trực tiếp nào. Việc tổng hợp, băm, xác minh và công bố được thực hiện dựa trên kết quả đầu ra từ các thành viên tham gia.\n\nDân số\tNguồn gốc của nó\tĐã đọc những gì\nASF members\n10,880,610\tThe public member list of the ArchiSteamFarm Steam Community group. Steam's group page shows 5,360,499 members (non-limited only); the API member list returned 10,880,610 total entries including limited accounts. The group is auto-joined on first run unless the user explicitly disables the default group-join setting in configuration (AutoJoinSteamGroup / Statistics), meaning the member list includes commercial bot clusters, individual card idlers, and regular gamers who left the default option enabled.\tGetPlayerBans for every member (ban flags); GetPlayerSummaries for creation dates and country. Batched at 100 IDs, deduplicated by SteamID64.\n100k Banned Accounts SRSWOR Slice\n100,000\tA representative sample drawn uniformly at random without replacement from the 1,182,811 banned accounts corpus ($P = 8.45\\%$). Finite Population Correction yields a margin of error of $\\pm 0.39\\%$ at a 99% confidence level ($Z = 2.576$).\tMonetization and limited account status (isLimitedAccount) audited via Steam's legacy XML profile interface (?xml=1) over distributed proxy pipelines. Confirms 63.06% paid status.\nSteamRep scammers\n51,732\tComplete 100% census of all profiles marked BANNED in the SteamRep community reputation database (51,732 total profiles). Zero sampling or filtering applied.\tISteamUser/GetPlayerBans/v1 for all 51,732 accounts, cross-tabulated against SteamRep status. Confirms 67.77% walk free of any scam bans.\nYêu cầu bảo hộ\n\nChỉ bao gồm các tỷ lệ thực nghiệm và các ước lượng được giới hạn thống kê. Trong tập hợp người dùng tự động hóa, 88.97% không bị cấm; tập con bị cấm có xu hướng tập trung vào các tài khoản gần đây (70% kể từ 2020). Trong báo cáo kiểm toán thực nghiệm về tài khoản 100,000-, 63.06% tài khoản bị cấm là tài khoản trả phí (không bị giới hạn), với biên độ sai số đã được chứng minh toán học trong khoảng ±0.4%. Trong số các đối tượng lừa đảo đã được xác nhận tại 51,732, 67.77% không bị cấm liên quan đến hành vi lừa đảo. Mọi số liệu đều có thể tái tạo từ trang web riêng của Valve tại API.\n\nNhững điều không được yêu cầu\n\nLệnh cấm “Steam” không có trường “lý do”, do đó không có lệnh cấm nào ở đây được quy cho một nguyên nhân cụ thể. Việc tham gia nhóm không phải là bằng chứng cho thấy tài khoản đó là bot tự động: vì ASF cho phép tham gia nhóm theo mặc định trừ khi người dùng tự bỏ chọn, nên cộng đồng này bao gồm cả các trang trại tài khoản thương mại với nhiều tài khoản lẫn các tài khoản cá nhân của người chơi bình thường và những người chơi nghiệp dư. Quốc gia là thông tin do người dùng tự khai báo, và danh sách trên SteamRep là kết quả phán quyết của cộng đồng, không phải phán quyết của tòa án. Không có cá nhân nào được nêu tên.\n\nTại sao điều này lại quan trọng\n\nValve nó cũng sử dụng cùng một Hệ thống Tính toán Tương đối (API), có cơ sở dữ liệu riêng làm nền tảng, và các lý do cấm mà quá trình quét này không thể nhìn thấy. Nó có thể thực thi truy vấn này trên toàn bộ không gian ID chỉ trong vài giây. Thước đo cho phép một bên thứ ba kiểm tra tuyên bố thực thi đối với một số cụ thể chưa bao giờ được công bố bởi chính bên duy nhất có thể tạo ra nó với độ chính xác tuyệt đối. Đây là ước tính từ bên ngoài, được đưa ra để câu hỏi có thể được đặt ra kèm theo một con số cụ thể.\n\nĐọc tiếp: nền kinh tế thẻ mà nhóm dân số này vận hành → · hỗ trợ truy cập và chống trộm → · tài liệu đầy đủ →",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Kiểm toán việc thực thi — Cuộc điều tra về lệnh cấm “1,182,811”"
          },
          {
            "level": 2,
            "id": null,
            "text": "Mười triệu tài khoản, và chín trong số mười tài khoản vẫn chưa bị xâm phạm"
          },
          {
            "level": 3,
            "id": null,
            "text": "ASF sẽ tham gia nhóm thay cho bạn"
          },
          {
            "level": 3,
            "id": null,
            "text": "10,880,610 tổng số mục"
          },
          {
            "level": 3,
            "id": null,
            "text": "88.97% sạch sẽ"
          },
          {
            "level": 3,
            "id": null,
            "text": "Trong số các tài khoản trên 10,880,610, có bao nhiêu tài khoản đã được Valve tiếp cận"
          },
          {
            "level": 3,
            "id": null,
            "text": "Chi phí mà đội tàu này đã phải chi trả để Valve tồn tại"
          },
          {
            "level": 2,
            "id": null,
            "text": "Nơi đội tàu hoạt động"
          },
          {
            "level": 3,
            "id": null,
            "text": "Các tài khoản bị khóa theo quốc gia được khai báo"
          },
          {
            "level": 2,
            "id": null,
            "text": "Các khoản phải thu gần đây, không phải là các khoản tồn đọng từ trước"
          },
          {
            "level": 3,
            "id": null,
            "text": "Thời điểm các tài khoản bị cấm được tạo ra"
          },
          {
            "level": 2,
            "id": null,
            "text": "Khi “Valve” được thực hiện, việc thực hiện đó diễn ra trong năm đầu tiên"
          },
          {
            "level": 3,
            "id": null,
            "text": "Tài khoản đó đã tồn tại được bao lâu khi bị cấm?"
          },
          {
            "level": 2,
            "id": null,
            "text": "Khi Valve thực sự hoạt động, nó cũng không ngăn chặn được bot"
          },
          {
            "level": 3,
            "id": null,
            "text": "Lý do thực sự khiến những người thuộc nhóm “11%” bị cấm"
          },
          {
            "level": 2,
            "id": null,
            "text": "Những kẻ lừa đảo trên Valve đã bị vạch trần: 51,732 – Tổng điều tra dân số đầy đủ"
          },
          {
            "level": 3,
            "id": null,
            "text": "Những đối tượng lừa đảo đã được xác nhận, dựa trên việc Valve có áp dụng lệnh cấm liên quan đến hành vi lừa đảo hay không (Danh sách toàn diện)"
          },
          {
            "level": 4,
            "id": null,
            "text": "Hai nhóm dân số, một kết quả"
          },
          {
            "level": 2,
            "id": null,
            "text": "Kiểm toán thực nghiệm tài khoản 100,000-: các mạng botnet không phải là những tài khoản miễn phí dùng một lần"
          },
          {
            "level": 3,
            "id": null,
            "text": "100,000 Lát cắt khách quan"
          },
          {
            "level": 3,
            "id": null,
            "text": "Độ sai số < ±0.4%"
          },
          {
            "level": 3,
            "id": null,
            "text": "Tại sao bất kỳ giá trị k nào trong công thức “100” đều cho kết quả giống nhau"
          },
          {
            "level": 3,
            "id": null,
            "text": "100,000 Tài khoản bị cấm: Tài khoản trả phí (5USD + chi tiêu tại cửa hàng) so với tài khoản miễn phí có giới hạn"
          },
          {
            "level": 3,
            "id": null,
            "text": "Thực trạng cơ bản: Việc thanh lý tài khoản trên quy mô công nghiệp"
          },
          {
            "level": 2,
            "id": null,
            "text": "Cách hiểu nội dung này, và những điều mà nó không khẳng định"
          },
          {
            "level": 3,
            "id": null,
            "text": "Yêu cầu bảo hộ"
          },
          {
            "level": 3,
            "id": null,
            "text": "Những điều không được yêu cầu"
          },
          {
            "level": 3,
            "id": null,
            "text": "Tại sao điều này lại quan trọng"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/vi/#briefing-heading",
          "https://help.steampowered.com/en/faqs/view/71D3-35C2-AD96-AA3A",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/asf-ban-census-2026-09-23.json",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/steamrep_steam_bans.csv",
          "https://phishdestroy.io/live-intel/?category=steam",
          "https://phishdestroy.io/steam_dossier/vi/card_economy.html",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/banned_archiasf_massive.csv",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/slice_100k_limited_results.csv",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/reports/BANNED_100K_FORENSIC_ANALYSIS.md",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/banned_100k_slice.csv",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/reports/STEAM_BANNED_LIMIT_ANALYSIS.md",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/INVESTIGATION_OVERVIEW.md",
          "https://phishdestroy.io/steam_dossier/vi/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/reports/STEAMREP_VS_STEAM_AUDIT.md",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/SteamRep_Profiles_BannedCaution_2024.csv",
          "https://phishdestroy.io/steam_dossier/vi/security_timeline.html",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/reports/russian_conflicts_report.json",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/reports/classification_report.json",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/reports/VALVE_INCOMPETENCE_REPORT.md",
          "https://phishdestroy.io/steam_dossier/vi/steam_evidence_archive.html",
          "https://phishdestroy.io/steam_dossier/vi/steam_enforcement_evidence.html",
          "https://phishdestroy.io/steam_dossier/vi/#insider-threat",
          "https://phishdestroy.io/steam_dossier/vi/"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/vi/enforcement_audit.content.json",
      "export_json_sha256": "29f13b89f63cf8dccf587196ef5e8b99b81b79197fa68abef87a10fdd46a042e"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "vi/index.html",
      "language": "vi",
      "title": "Hồ sơ về “Steam”: các quy định, lộ trình và trách nhiệm giải trình",
      "source_url": "https://phishdestroy.io/steam_dossier/vi/index",
      "source_html_sha256": "0c2133684f7b0dd8b8594c609bce1890972c69628294eeecb1b1ff79711926bc",
      "exported_at": "2026-09-29T00:23:03.571Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "exhibit-gallery-section",
            "source": "https://phishdestroy.io/steam_dossier/vi/index#exhibit-gallery-section"
          }
        ],
        "raster_images_replaced": 2
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "index.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/vi/index.pdf?v=print-20260929-v5",
        "sha256": "fb7db77b1ecc1d6b8380e49c8ccdda5ce349c96fc958bab44abab51dfa599940",
        "bytes": 978183,
        "pages": 107
      },
      "integrity": {
        "signed_object": "index.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "index.content.json.asc",
        "digest_file": "index.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify index.content.json.asc index.content.json",
          "sha256sum -c index.content.json.sha256"
        ]
      },
      "content": {
        "text": "Tóm tắt — 5 CÁC TỪNG KHAI CÓ THỂ XÁC MINHTất cả các thông tin tại 5 đều có thể kiểm chứng thông qua các máy chủ, tài liệu và ngày công bố của chính Valve\n44\n\nĐã phát hiện các tên miền máy chủ xác thực riêng biệt chứa thông tin đăng nhập Steam dành cho các nền tảng của bên thứ ba — mỗi tên miền được đăng ký độc lập với địa chỉ chính của nền tảng đó.\n\nPhần 3 →\n26\n\ncác cặp filter-split: miền chính hiển thị cảnh báo “Steam” từ bộ lọc liên kết; trong khi máy chủ đăng nhập bên cạnh thì không.\n\nPhần 3.2 →\n12y 6m\n\nlà bao lâu api.csgem.com đã xử lý các lượt đăng nhập vào Steam trong khi csgogem.com nằm trên bộ lọc liên kết. Đăng ký vào tháng 3 năm 2014.\n\nXem bảng →\n10 ngày\n\nđó là thời hạn “2016” mà chính tờ *Valve* đặt ra cho các nhà điều hành cờ bạc. Kể từ đó đến nay, chưa có báo cáo nào về việc thực thi quy định đối với từng nhà điều hành được công bố.\n\nPhần 2 →\n830 pp\n\nĐiều 15 Phản hồi của GDPR từ các luật sư của Valve — 902,270 các ký tự trong phần bị che mờ có thể trích xuất, các thanh che mờ vẫn được để dưới dạng văn bản có thể chọn.\n\nPhần 18 →\nĐIỀU NÀY CÓ NGHĨA LÀ GÌ — BỘ LỌC STEAM LINK\n\nValve duy trì một bộ lọc liên kết nhằm chặn các liên kết dẫn đến các trang web cờ bạc và giao dịch khi chúng được đăng trong phòng trò chuyện Steam hoặc trong phần bình luận trên hồ sơ. Khi người dùng nhấp vào một liên kết bị chặn, Valve sẽ hiển thị một cảnh báo toàn màn hình: \"Liên kết này đã bị báo cáo là có khả năng chứa mã độc.\" Tuy nhiên, Valve chỉ kiểm tra tên miền chính của trang web. Các tên miền riêng biệt được sử dụng cho xác thực OpenID tại Steam không nằm trong danh sách chặn — do đó, quy trình đăng nhập vẫn diễn ra thành công ngay cả khi trang web chính bị chặn.\n\nWhat this means — OpenID and openid.realm\n\nOpenID is the sign-in standard behind the “Sign in with Steam” button: the site does not receive the password, Steam confirms the identity to it. openid.realm is the field carrying the address of the site asking for the sign-in, and openid.return_to the address Steam is to send the user back to. Steam receives both on every request and prints the realm on its own login page — which is why this dossier can name the host each platform authenticates through.\n\nSection 3 — the observed routes →\n\nPhần 1 — Tóm tắt vụ án\nQuy tắc. Kỷ lục. Những câu hỏi chưa có lời giải đáp.\nBối cảnh và các giới hạn về nguồn\n\nSáu kết luận, mỗi kết luận đều được liên kết với một tài liệu công khai có ghi rõ ngày tháng. Các phần chi tiết được trình bày theo thứ tự như sau: hồ sơ kỹ thuật (Phần A), hồ sơ về quy định và việc thi hành (Phần B), khung pháp lý (Phần C), sau đó là các phụ lục kèm theo các chứng cứ chính.\n\nSáu phát hiện. Mỗi phát hiện đều liên kết một quy định bằng văn bản với một tài liệu có ghi ngày tháng và một câu hỏi mà bằng chứng có thể kiểm chứng.\n\n1. Máy chủ xác thực miền riêng biệt — Các tuyến đường 44 · Các cặp tách biệt 26\n\nCác hồ sơ trong sổ đăng ký lao động 44 các nền tảng xác thực thông qua một tên miền riêng có thể đăng ký. Còn năm tuyến đường nữa đang trong quá trình xác minh và chờ ngày được công bố trên trang RDAP; nếu các tuyến này được công bố, tổng số tuyến sẽ tăng lên 47.. Các tuyến này không được liệt kê trên trang 44 cũng như trong bảng thống kê theo độ tuổi. — 27 kèm theo tệp bằng chứng đã được công bố cho từng tuyến đường và 17 được thêm vào từ quá trình thu thập thủ công, được liệt kê riêng biệt. Trong 26 các cặp lọc-chia nhỏ tên miền chính là BỊ CHẶN trong bộ lọc liên kết “Steam” trong khi máy chủ proxy mang thông tin đăng nhập của nó thì không. Đây không phải là các tên miền tạm thời: csgogem.com bị chặn trong khi api.csgem.com, máy chủ có thông tin đăng nhập Steam, đã được đăng ký từ tháng 3 2014 — 12 năm 6 tháng. Valve nhận được tên máy chủ đó trong mỗi yêu cầu OpenID và hiển thị lại cho người dùng trên trang đăng nhập của chính trang web này. Bảng đầy đủ, thông tin về thời gian tồn tại theo từng tuyến đường và nguồn gốc được trình bày tại mục 3.\n\nHãy đi theo lộ trình →\n2. 2016: cơ chế đã được đặt tên, thời hạn đã được ấn định\n\nVào ngày 13 Tháng 7 năm 2016 Valve đã công khai mô tả cách các trang web cờ bạc sử dụng Steam OpenID và các tài khoản giao dịch tự động, cùng với các thông báo của luật sư đại diện cho công ty này về 20 Tháng 7 năm 2016 đặt thời hạn mười ngày. Kể từ đó, chưa có báo cáo thực thi nào theo từng nhà khai thác được công bố. Mười năm sau khi thời hạn đó được đưa ra, cơ chế cùng tên này đang được sử dụng trên các máy chủ xác thực thuộc các miền riêng biệt, những máy chủ này không trả về bất kỳ lệnh chặn nào từ Link Filter trên 2026-09-21.\n\nĐọc thư ngỏ gửi đến WSGC →\n3. Mối liên hệ giữa các thiết bị, trên giấy tiêu đề của luật sư\n\nTrong các thư từ được trích dẫn ở đây, luật sư của Valve đã mô tả cơ chế tương quan ở cấp độ thiết bị, liên kết một thiết bị với nhiều tài khoản — một tính năng mà bộ phận Hỗ trợ của Steam trước đó đã thông báo với người dùng là không thể thực hiện được về mặt kỹ thuật. Câu hỏi còn bỏ ngỏ là Valve đang lưu giữ những hồ sơ cấp độ thiết bị nào và trên cơ sở nào mà chủ tài khoản bị từ chối quyền truy cập vào những hồ sơ đó.\n\nĐọc bản ghi nhớ →\n4. Hai phản hồi về quyền truy cập. Một phản hồi đã không cung cấp dữ liệu, một phản hồi đã để rò rỉ dữ liệu.\n\nTháng 10 năm 2025: Luật sư của Valve đã trả lời yêu cầu theo Điều 15 bằng một phụ lục trang 830-, trong đó các phần bị che giấu được tô đè lên văn bản thay vì xóa bỏ — 902,270 ký tự đưa ra một công cụ trích xuất tiêu chuẩn, bao gồm cả các định danh của bên thứ ba mà các thanh đó được thiết kế để che giấu. Điều 15 (4) chính là lý do khiến các thanh đó tồn tại. Tháng 9 năm 2026: Phiếu yêu cầu HT-2YBP-F7JP-D4VB đã bị đóng sau ba ngày kèm theo một liên kết đến trang Dữ liệu Tài khoản tự phục vụ — không có dữ liệu, không nêu rõ cơ sở pháp lý. Thời hạn một tháng theo Điều 12(3) vẫn chưa hết hiệu lực tại thời điểm công bố; sự phản đối này liên quan đến nội dung.\n\nXem kết quả kiểm tra việc che giấu thông tin →Xem hồ sơ vé →\n5. Thị trường đang ở mức cao hơn mức trần mà cuốn sách “Steam” đề cập\n\nSteam giới hạn mức niêm yết trên thị trường ở mức khoảng $1,800. Trên năm sàn thương mại điện tử trong một bản chụp nhanh đã lỗi thời (23 2026 tháng 9), 248 Các danh mục sản phẩm CS2 có mức giá cao hơn mức trần đó do hai hoặc nhiều bên trong số đó độc lập với nhau, và Tất cả các tệp 248 đều không có trong thư mục Steam; một cuốn “Dragon Lore” mới nguyên hộp có giá khởi điểm là $10,941 Trên các trang 389, giá của mẫu nhân vật “CSFloat” được liệt kê trên cả năm trang (mẫu nhân vật chỉ có tại “” trong mục 13, từ bản cập nhật tháng 9 của 20) là $10,623.95 trên các trang 62. Việc bán hàng với mức giá này đòi hỏi phải thông qua một nền tảng bên ngoài, trong khi việc chuyển nhượng vật phẩm vẫn được thực hiện qua Steam.\n\nTheo dõi giá và chuyển khoản →\n6. Quy tắc này được nêu rõ ràng; còn dấu vết kiểm toán thì không\n\nThỏa thuận người đăng ký quy định rằng Steam chỉ dành cho mục đích sử dụng cá nhân, phi thương mại; cấm khai thác thương mại trừ khi được cho phép rõ ràng; cấm sử dụng các chương trình tự động và bot; đồng thời cho phép chấm dứt tài khoản. Valve đã áp dụng các điều khoản này đối với các nhà điều hành cờ bạc trong vụ 2016.. Bên cạnh đó, theo tài khoản kỹ thuật của CSFloat, Valve đã bị đóng cửa IEconItems_730/GetPlayerItems trong 2017,, đã gỡ bỏ quyền truy cập công khai vào các ID mục gốc (không tìm thấy nhật ký thay đổi tại Valve).\n\nĐặt quy tắc bên cạnh mạng →\n2016 / Yêu cầu bằng văn bản 10 ngày\nHạn chót được nêu trong các thông báo ngày 7/2016 của luật sư thuộc Ủy ban Cờ bạc Tây Virginia (Valve) gửi đến các trang web cờ bạc. Thư ngỏ gửi Ủy ban Cờ bạc Tây Virginia (WSGC): Mục 2.\n2017 / Dòng sự kiện kiểm toán công khai Đã đóng quyền truy cập ID\nCSFloat ghi lại việc mất các mã định danh ban đầu của các mục.\nThư từ của luật sư Tương quan giữa các thiết bị\nMột thiết bị có liên quan đến hàng chục tài khoản bị đánh cắp.\nSổ đăng ký tuyến đường Bị chặn, nhưng vẫn đang đăng nhập\nQuy tắc: Tuyên bố “2016” của Valve nghiêm cấm việc kinh doanh cờ bạc trên OpenID của Steam. Bản ghi: 26 Các tên miền chính được đặt trên Link Filter, trong khi máy chủ lưu trữ thông tin đăng nhập Steam của từng tên miền hoạt động trên — máy chủ của csgogem.com đã hoạt động được 12 năm 6 tháng.\nMục “2” — Thư ngỏ\nThư ngỏ gửi Ủy ban Cờ bạc Tiểu bang Washington\n\nMười ngày đã trở thành mười năm. Câu hỏi của Ủy ban tại 2016 gửi đến Valve vẫn chưa được trả lời kèm theo bản ghi chi tiết theo từng nhà mạng; lá thư này yêu cầu Ủy ban mở lại hồ sơ.\n\nHỆ THỐNG LOA PHÁT THÔNG BÁO · ỦY BAN CÁ CƯỢC TIỂU BANG WASHINGTON\n\nMười ngày bỗng chốc trở thành mười năm.Mở lại bản ghi.\n\nGửi Ủy ban Cờ bạc Tiểu bang Washington:\n\nTrong bài viết “2016,”, Giám đốc David Trujillo đã yêu cầu Valve trình bày những biện pháp mà cơ quan này đã thực hiện để ngăn chặn việc sử dụng các vật phẩm từ Steam trong hoạt động cờ bạc. Ông Chris Stearns, khi đó là Chủ tịch, cùng Ủy ban đã đối mặt với một ngành công nghiệp dựa trên các vật phẩm do Valvephát hành và các giao dịch chuyển nhượng từ Steam. Cả hai người này đều đã rời khỏi các vị trí của mình tại Ủy ban. Câu hỏi mà họ đặt ra cho Valve vẫn chưa hết hiệu lực.\n\nTổng cố vấn pháp lý của Valve, ông Karl Quackenbush, đã yêu cầu các nhà điều hành cờ bạc ngừng việc sử dụng thương mại các tài khoản trên Steam trong vòng mười ngày. Trong phản hồi gửi đến Ủy ban vào tháng 10, Valve đã phủ nhận việc tạo điều kiện cho hoạt động cờ bạc, cho biết họ đã gửi thư yêu cầu ngừng vi phạm đến hơn 40 trang web và đã vô hiệu hóa các tài khoản liên quan. Công ty này cũng biện minh cho việc duy trì dịch vụ giao dịch Steam và OpenID vì những dịch vụ này mang lại lợi ích cho khách hàng và các nhà phát triển trò chơi. Đó là một hành động thể hiện quyền kiểm soát. Điều đó cần được kiểm chứng, chứ không phải sự tuân phục.\n\nTheo đánh giá của chúng tôi, câu trả lời của Valve không chứng minh được rằng biện pháp thực thi mà họ lựa chọn tương xứng với quy mô của mạng lưới mà họ mô tả. Một lá thư đe dọa gửi đến nhà điều hành không thể so sánh được với việc chặn vĩnh viễn các tài khoản Steam, cơ sở hạ tầng giao dịch và các đường dẫn xác thực – những yếu tố làm nên hoạt động của doanh nghiệp. Các ước tính được báo cáo cho thấy Chỉ riêng CS:GO Lounge đã đạt doanh thu cá cược hơn $1 tỷ trong thời gian diễn ra giải đấu 2016; đó là con số ước tính từ bên ngoài về số tiền đặt cược, chứ không phải doanh thu từ Valve, và hoạt động cá cược trực tuyến ban đầu của trang web này sau đó đã bị đóng cửa. Quy mô hoạt động này khiến việc thực thi pháp luật có thể kiểm chứng trở nên thiết yếu.\n\nHôm nay, chính Valve Thỏa thuận người đăng ký đã lưu trữ 2026-09-21 ↗ hạn chế việc khai thác thương mại, trừ những trường hợp được cho phép rõ ràng, đồng thời cấm riêng các hình thức tự động hóa cụ thể. Chúng tôi sổ đăng ký lộ trình đã hết hạn các bản ghi được khai báo là OpenID trả về các máy chủ cho các dịch vụ bên ngoài; openid.realm và openid.return_to là các trường dữ liệu được gửi đến Steam, chứ không phải là các thông tin bí mật được giấu khỏi trang web này. Trang web của chúng tôi Kiểm tra bộ lọc liên kết trình bày các trường hợp mà địa chỉ chính đã bị cảnh báo nhưng máy chủ đăng nhập liên quan lại không bị. Chỉ riêng kết quả lọc không thể chứng minh rằng Valve đã cho phép đăng nhập hay một bot cụ thể nào đó đã lách được lệnh cấm tài khoản. Điều này thực sự chứng minh rằng một thông báo cảnh báo trên trang chủ không thể được coi là câu trả lời đầy đủ về vấn đề truy cập.\n\nSự tồn tại của các chức năng giao dịch và OpenID hữu ích, hợp pháp tại Steam cũng không thể trả lời liệu các nhà điều hành bị cấm có thực sự bị loại trừ hay không. Chính các quy tắc của Valve cũng cho phép các trường hợp ngoại lệ rõ ràng. Nếu Valve dựa vào sự phân biệt đó, Ủy ban nên yêu cầu họ xác định các tiêu chí về cấp phép, kiểm soát tài khoản và thực thi áp dụng cho các doanh nghiệp kinh doanh skin thương mại, cũng như các mục đích sử dụng cụ thể không liên quan đến cờ bạc mà họ đã viện dẫn trong 2016.. Chỉ đơn thuần là khả năng sử dụng hợp pháp không phải là câu trả lời cho việc sử dụng bị cấm đã được ghi nhận.\n\nChúng tôi đề nghị Ủy ban xem xét lại hồ sơ “2016” và yêu cầu cung cấp báo cáo chi tiết theo từng nhà điều hành: những tài khoản Steam và bot giao dịch nào đã bị vô hiệu hóa sau khi nhận được thông báo 10 ngày; liệu các tài khoản liên quan hoặc máy chủ lưu trữ có được giám sát hay không; những nhà điều hành nào sau đó đã được khôi phục quyền truy cập; những trường hợp miễn trừ nào đã được cấp; và những hồ sơ nào làm cơ sở cho tuyên bố của Valve gửi tới Ủy ban. Công bố những tài liệu mà pháp luật cho phép công chúng tra cứu. So sánh các tài liệu đó với các lộ trình hiện tại và với các can thiệp sau này của Valve, bao gồm OPSkins trong trò chơi “2018” đã lưu trữ 2026-03-07 ↗.\n\nThông báo này đã đặt ra thời hạn mười ngày vào tháng 7 năm 2016; mười năm là khoảng thời gian đủ dài để xác định liệu việc đó có được thực hiện hay không. Ủy ban nên đối chiếu tài khoản 2016 của Valve với cơ sở hạ tầng vẫn còn có thể quan sát được cho đến ngày nay.\n\nCuộc điều tra của “Steam” · Tuyên bố công khai, 20 tháng 9 năm 2026\n\n2016 Thông báo của Ủy ban ↗ đã lưu trữ 2026-05-20 ↗ · Phản hồi của Valve về “2016” (bản sao tài liệu) ↗ · Tuyên bố OpenID của Valve về “2016” ↗ đã lưu trữ 2026-09-21 ↗ · Thỏa thuận hiện tại về “Steam” ↗ đã lưu trữ 2026-09-21 ↗ · Lịch trình của cuộc trao đổi “2016”: Phần “11” →\n\nPhần A — Hồ sơ kỹ thuật · Mục3\nTrang web này bị chặn. Tuy nhiên, đường dẫn đăng nhập thì không.\n\n26 các tên miền chính bị chặn. Máy chủ proxy xác thực phía sau mỗi tên miền đó, và thời gian hoạt động của nó. Các máy chủ xác thực riêng biệt này không phải là những địa chỉ phụ ngẫu nhiên — mỗi máy chủ là một máy chủ proxy xác thực cho Steam, đóng vai trò trung gian giữa nền tảng và điểm cuối OpenID củValve, đồng thời đảm nhận việc đăng nhập mà tên miền bị chặn không còn có thể thực hiện công khai nữa. Valve đã đặt “cửa chính” trên Link Filter. Quá trình đăng nhập vẫn tiếp tục diễn ra thông qua máy chủ proxy: csgogem.com bị chặn, và api.csgem.com đã được đăng ký từ tháng 3 năm 2014 — mười hai năm rưỡi. Trong mỗi ngày đó, máy chủ đó đều gửi tên máy chủ của mình đến điểm cuối OpenID của Valve, và Steam hiển thị lại thông tin đó ngay lập tức cho người dùng trên trang đăng nhập. Valve là tuyến đường chính mà tất cả các tuyến này đều đi qua; nó không cần phải tìm ra các tuyến đó. Đó chính là điều mà phần này đo lường: không phải là liệu có cảnh báo hay không, mà là đoạn đường phía sau cảnh báo đó vẫn mở trong bao nhiêu năm. 44 các tuyến đường thuộc miền riêng biệt trong sổ đăng ký, 27 trong số đó có tệp bằng chứng được công bố cho từng tuyến — như bảng dưới đây. Hãy xem xét một ví dụ, sau đó tiến hành đo lường tất cả các trường hợp.\n\nHình 3.1 — Hai tuyến đường được vẽ ra.\n\nMột nền tảng, một người dùng, hai yêu cầu được gửi đi từ cùng một trình duyệt. Tính năng Lọc Liên kết (Link Filter) của Valve hoạt động trên cả hai yêu cầu này. Tính năng này chặn yêu cầu chứa liên kết và cho phép yêu cầu chứa thông tin đăng nhập đi qua. Tất cả các số liệu được đo lường trong phần này đều thể hiện thời gian mà đường dẫn dưới cùng duy trì trạng thái mở.\n\nThe player\none browser, one session\nrollbit.com\nthe platform's main domain\nrbsnin.com\nseparate authentication host\nLINK FILTER\n✕ BLOCKED\nLINK FILTER\n✓ CLEAN\nsteamcommunity.com\nOpenID endpoint · signs in\nno route\nLiên kết được đăng trên Steam — đã ngừng hoạt độngYêu cầu đăng nhập — đã được chấp nhậnCác bản sao lưu của các bài viết “19” và “21” ngày 2026 tháng 9\n\nValve có thể nhìn thấy cả hai yêu cầu, nhưng chỉ có một yêu cầu được xử lý. Bộ lọc liên kết (Link Filter) là một danh sách các liên kết được phê duyệt (Valve), được kiểm tra bởi dịch vụ xác thực (Valve). Yêu cầu OpenID truyền tên máy chủ xác thực (auth host) đến điểm cuối của Valve, và tên này sẽ được hiển thị ngay lập tức trên trang đăng nhập. Dù sao đi nữa, tên máy chủ vẫn có trong yêu cầu — điểm khác biệt nằm ở việc liệu có thực hiện bất kỳ thao tác nào với nó hay không.\n\nMột nền tảng. Hai lộ trình khác nhau.ROLLBIT / CÁC QUAN SÁT Đà LƯU TRỮ\nBước 5 / 5\n\nYêu cầu được gửi đến Steam. Lộ trình được ghi nhận đã dẫn đến biểu mẫu đăng nhập của Steam. Các tác giả đã không hoàn tất quá trình đăng nhập. Việc chặn liên kết từ miền chính không ngăn được lộ trình này dẫn đến biểu mẫu.\n\n01 KIỂM TRA BỘ LỌC LIÊN KẾT\nĐIỂM ĐẾNrollbit.comTên miền chính của nền tảng\nBộ lọc kết nối STEAMKiểm tra liên kếtMột hệ thống cảnh báo điểm đến độc lập\nKẾT QUẢ Đà LƯULiên kết bị chặn19 & 21 tháng 9 năm 2026\n02 QUY TRÌNH ĐĂNG NHẬP Đà QUAN SÁT ĐƯỢC\nTRÊN NỀN TẢNGĐăng nhập bằng SteamNền tảng này khởi tạo một yêu cầu OpenID\nMÁY CHỦ XÁC THỰC TÁCH BIỆTrbsnin.comKhông có khối “Link Filter” trong bản kiểm tra đã lưu\nSTEAMBiểu mẫu đăng nhập đã được hiển thịMáy chủ được yêu cầu xuất hiện trong thông báo của Steam\nKiểm tra các ghi chú ban đầu về việc thu thập mẫu, ngày đăng ký và chi tiết về quy trình\nCông tác thực thi pháp luật của Cơ quan Bảo vệ Môi trường Hoa Kỳ (Valve) diễn ra như thế nào\nTên miền chính: bị chặn\nNgười dùng\n→\nrollbit.com\n(tên miền chính)\n↓\nBỘ LỌC STEAM LINK — Đà BỊ CHẶN\n\"Liên kết bị chặn!\" — được báo cáo là có khả năng gây hại\nrollbit.com Đã phát hiện một khối Link Filter trên các trang 2026-09-19 và 2026-09-21 (kiểm tra không cần xác thực; mã HTML thô và mã SHA-256đã được lưu lại). Một bản ghi rõ ràng và có thể kiểm chứng.\nĐiều thực sự xảy ra — xác thực\nMáy chủ xác thực: không bị chặn\nNgười dùng\n→\nrollbit.com\n\"Đăng nhập bằng Steam\"\n↓\nChuyển hướng qua máy chủ xác thực riêng biệt:\nrbsnin.comBộ lọc liên kết: CLEAN\nđã đăng ký 2026-09-18T09:34:52Z (Verisign RDAP)\n↓\nSteam Thông báo trên trang đăng nhập (2026-09-20):\n\"Note that rbsnin.com is not affiliated with Steam or Valve\"\nSteam đưa ra thông báo này từ Ủy ban Bảo vệ Môi trường (openid.realm) về yêu cầu mà cơ quan này đã nhận được.\n↓\nSteam biểu mẫu đăng nhập được cung cấp cho máy chủ riêng biệt\nCác tác giả chưa hoàn tất quá trình đăng nhập; quá trình này đã được quan sát cho đến biểu mẫu Steam.\nValve nhận được tên máy chủ return_to / realm trong mỗi yêu cầu như vậy. rbsnin.com không trả về bất kỳ quy tắc chặn nào của Link Filter trên 2026-09-21.\nTheo yêu cầu\nVới tư cách là nhà cung cấp OpenID, Steam nhận được tên máy chủ xác thực (auth hostname) trong mỗi yêu cầu xác thực: thông tin này được gửi đến các máy chủ của chính Valve trong openid.return_to và openid.realm các tham số.\nĐược gửi bởi trang web\nMáy chủ xác thực không được phát hiện qua quá trình quét — nền tảng sẽ gửi thông tin này đến địa chỉ Steam trong mỗi yêu cầu. Theo tài liệu OpenID 2.0 §9.1 return_to thành phần này về mặt kỹ thuật là tùy chọn, nhưng nếu thiếu nó thì Steam sẽ không thể trả về kết quả đăng nhập, do đó để quá trình đăng nhập tại Steam hoạt động bình thường thì nó thực tế là bắt buộc. Steam thậm chí còn hiển thị tên máy chủ cho người dùng (\"<host> không có liên quan đến Steam hoặc Valve\").\n14 yr\nlà thời gian tồn tại của máy chủ xác thực lâu đời nhất vẫn đang lưu giữ các thông tin đăng nhập Steam tại điểm kiểm tra 2026-09-21 (dota2.net, đã đăng ký tại 2011-10-29); máy chủ mới nhất đã tồn tại được ba ngày (rbsnin.com). Đừng coi hình “Các máy chủ xác thực '0' bị chặn” là kết luận. Một máy chủ xác thực bị chặn sẽ khiến tính năng “Đăng nhập bằng Steam” của nền tảng này ngừng hoạt động hoàn toàn, do đó, một danh sách đăng ký được xây dựng từ các lần đăng nhập thành công chỉ có thể chứa những máy chủ chưa từng bị chặn. Con số mang ý nghĩa ở đây không phải là số lần bị chặn — mà là số năm tên miền chính nằm trong Bộ lọc liên kết (Link Filter) trong khi tài khoản đăng nhập bên cạnh nó vẫn tiếp tục hoạt động.\nCác máy chủ xác thực trên miền riêng biệt: so sánh ngày đăng ký với miền chính (các đường dẫn 30: tên miền 25 được giải quyết trong báo cáo kiểm tra trình duyệt 2026-09-21, cùng với 5 được thêm vào tại 2026-09-22)\nNền tảng\tBộ lọc liên kết: chính\tMáy chủ xác thực\tBộ lọc liên kết: máy chủ xác thực\tMáy chủ xác thực đã được đăng ký\tNguồn quan sát\tHồ sơ chứng cứ\nRollbit\nrollbit.com · reg. 2014-11-08\n\tBLOCKED\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\trbsnin.com\tCLEAN\n2026-09-21 · raw HTML (no Wayback snapshot)\n\t2026-09-18\n09:34:52Z, Verisign RDAP\n\tSteam login-page notice, 2026-09-20\trollbit.com.json\nSkin.Club\nskin.club · reg. 2017-09-04\n\tBLOCKED\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\tsc-auth.net\tCLEAN\n2026-09-21 · Wayback 2026-09-21\n\t2019-04-02\nRDAP\n\tSteam login-page notice\tskin.club.json\nHowl.GG\nhowl.gg · reg. 2017-03-16\n\tBLOCKED\n2026-09-18, 09-19, 09-21 · Wayback 2026-09-21\n\thowl.uno\tCLEAN\n2026-09-21 · Wayback 2026-09-21\n\t2026-08-11\nRDAP\n\tLive browser capture + supplied OpenID URL\thowl.gg.json\nDuelbits\nduelbits.com · reg. 2020-02-03\n\tBLOCKED\n2026-09-21 · Wayback 2026-09-21\n\tswitchflips.com\tCLEAN\n2026-09-21 · Wayback 2026-09-21\n\t2020-04-21\nRDAP\n\tSupplied OpenID URL\tduelbits.com.json\nCSGOFast\ncsgofast.com · reg. 2015-03-27\n\tBLOCKED\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\tsteam-login.authtofast.com\tCLEAN\nauthtofast.com, 2026-09-21 · Wayback 2026-09-21\n\t2026-06-30\nauthtofast.com, RDAP\n\tLive browser capture + supplied OpenID URL\tcsgofast.com.json\nFarmskins\nfarmskins.com · reg. 2016-03-23\n\tBLOCKED\n2026-09-19, 2026-09-21 · raw HTML\n\tsteam.kobal.cc\tCLEAN\n2026-09-19, 2026-09-21 · raw HTML\n\t2017-01-07\nkobal.cc, RDAP\n\tLive browser capture + supplied OpenID URL\tfarmskins.com.json\nCobaltLab\ncobaltlab.tech\n\tBLOCKED\n2026-09-21 · raw HTML\n\tcobaltauth.com\tCLEAN\n2026-09-21 · raw HTML\n\t2025-01-07\nRDAP\n\tSupplied OpenID URL\tcobaltlab.tech.json\nCSGO.NET\ncsgo.net · reg. 2012-07-22\n\tBLOCKED\n2026-09-21 · raw HTML\n\tcn2.easylot.net\tCLEAN\n2026-09-21 · raw HTML\n\t2016-09-03\neasylot.net, RDAP\n\tLive browser capture\tcsgo.net.json\nGGDrop\nggdrop.com\n\tBLOCKED\n2026-09-21 · raw HTML\n\tggauth.com\tCLEAN\n2026-09-21 · raw HTML\n\t2023-05-03\nRDAP\n\tSupplied OpenID URL\tggdrop.com.json\nRustChance\nrustchance.com\n\tBLOCKED\n2026-09-21 · raw HTML\n\thgfuihd.com\tCLEAN\n2026-09-21 · raw HTML\n\t2019-01-27\nRDAP\n\tSupplied OpenID URL\trustchance.com.json\nSkin.Fans\nskin.fans\n\tBLOCKED\n2026-09-21 · raw HTML\n\tauth.skinfans.com\tCLEAN\n2026-09-21 · raw HTML\n\t2018-07-16\nskinfans.com, RDAP\n\tSupplied OpenID URL\tskin.fans.json\nSkinport\nskinport.com · reg. 2018-09-05\n\tBLOCKED\n2026-09-21 · raw HTML\n\tskinport.app\tCLEAN\n2026-09-21 · raw HTML\n\t2020-06-20\nRDAP\n\tLive browser capture + supplied OpenID URL\tskinport.com.json\nSkins.Cash\nskins.cash\n\tBLOCKED\n2026-09-21 · raw HTML\n\tskinscash.live\tCLEAN\n2026-09-21 · raw HTML\n\t2019-12-05\nRDAP\n\tSupplied OpenID URL\tskins.cash.json\nTF2Hunt\ntf2hunt.com · reg. 2018-01-13\n\tBLOCKED\n2026-09-21 · raw HTML\n\trstspcl.com\tCLEAN\n2026-09-21 · raw HTML\n\t2020-08-08\nRDAP\n\tLive browser capture + supplied OpenID URL\ttf2hunt.com.json\nCSGOGem\ncsgogem.com · reg. 2016-10-16\n\tBLOCKED\n2026-09-22 · raw HTML\n\tapi.csgem.com\ncsgem.com — separate registrable domain\n\tCLEAN\n2026-09-22 · raw HTML\n\t2014-03-08\ncsgem.com, RDAP — oldest in register\n\tManual collection + Link Filter capture\tlinkfilter-2026-09-22.json\nGamdom\ngamdom.com · reg. 2016-07-29\n\tBLOCKED\n2026-09-22 · raw HTML\n\tlogin.gambldom.com\ngambldom.com — one letter off the brand\n\tCLEAN\n2026-09-22 · raw HTML\n\t2017-09-24\ngambldom.com, RDAP\n\tManual collection + Link Filter capture\tlinkfilter-2026-09-22.json\n12CS\n12cs.fail · reg. 2026-03-24\n\tBLOCKED\n2026-09-22 · raw HTML\n\tfail.games\tCLEAN\n2026-09-22 · raw HTML\n\t2021-08-24\nfail.games, RDAP\n\tManual collection + Link Filter capture\tlinkfilter-2026-09-22.json\nCSGOEmpire\ncsgoempire.com · reg. 2015-06-10\n\tCLEAN\n2026-09-19, 2026-09-21 · Wayback 2026-09-21\n\tcsgoempirelogin4.com\none of ten numbered domains login1–10\n\tCLEAN\n2026-09-21 · Wayback 2026-09-21\n\t2020-07-20\n05:49:17Z, Verisign RDAP\n\tLive browser capture\tcsgoempire.com.json\nCS.MONEY\ncs.money\n\tCLEAN\n2026-09-21 · raw HTML\n\tauth.dota.trade\tCLEAN\n2026-09-21 · raw HTML\n\t2016-07-15\ndota.trade, RDAP\n\tSteam login-page notice\tcs.money.json\nCSFloat\ncsfloat.com · reg. 2021-07-11\n\tCLEAN\n2026-09-21 · raw HTML\n\tcsgofloat.com\noperator's former brand domain; separate registrable domain, not an evasion indicator\n\tCLEAN\n2026-09-21 · raw HTML\n\t2015-09-29\nRDAP\n\tLive browser capture\tcsfloat.com.json\nG4Skins\ng4skins.com\n\tCLEAN\n2026-09-21 · raw HTML\n\tauth.g4s.to\tCLEAN\n2026-09-21 · raw HTML\n\t2021-05-30\ng4s.to, RDAP\n\tSupplied OpenID URL\tg4skins.com.json\nJuice.GG\njuice.gg\n\tCLEAN\n2026-09-21 · raw HTML\n\tletmeinjuice.com\tCLEAN\n2026-09-21 · raw HTML\n\t2024-04-15\nRDAP\n\tSupplied OpenID URL\tjuice.gg.json\nMarket.CSGO\nmarket.csgo.com\n\tCLEAN\n2026-09-21 · raw HTML\n\tdota2.net\tCLEAN\n2026-09-21 · raw HTML\n\t2011-10-29\nRDAP\n\tLive browser capture + supplied OpenID URL\tmarket.csgo.com.json\nRust.TM\nrust.tm\n\tCLEAN\n2026-09-21 · raw HTML\n\tdota2.net\tCLEAN\n2026-09-21 · raw HTML\n\t2011-10-29\nRDAP\n\tSupplied OpenID URL\trust.tm.json\nCSGOLounge\ncsgolounge.com · reg. 2013-08-14\n\tCLEAN\n2026-09-22 · raw HTML\n\tdota2.net\nthird front-end on this auth host\n\tCLEAN\n2026-09-22 · raw HTML\n\t2011-10-29\ndota2.net, RDAP\n\tManual collection + Link Filter capture\tlinkfilter-2026-09-22.json\nDota2Lounge\ndota2lounge.com · reg. 2012-08-10\n\tCLEAN\n2026-09-22 · raw HTML\n\tdota2.net\nfourth front-end on this auth host\n\tCLEAN\n2026-09-22 · raw HTML\n\t2011-10-29\ndota2.net, RDAP\n\tManual collection + Link Filter capture\tlinkfilter-2026-09-22.json\nSkinBaron\nskinbaron.de\n\tCLEAN\n2026-09-21 · raw HTML\n\tskinbaron.com\nsame brand, different TLD\n\tCLEAN\n2026-09-21 · raw HTML\n\t2015-12-22\nRDAP\n\tSupplied OpenID URL\tskinbaron.de.json\nTF2Royal\ntf2royal.com · reg. 2022-08-17\n\tCLEAN\n2026-09-21 · raw HTML\n\ttf2auth.com\tCLEAN\n2026-09-21 · raw HTML\n\t2021-07-27\nRDAP\n\tLive browser capture + supplied OpenID URL\ttf2royal.com.json\nTradeit\ntradeit.gg\n\tCLEAN\n2026-09-21 · raw HTML\n\tconnect-tradeit.com\tCLEAN\n2026-09-21 · raw HTML\n\t2022-02-23\nRDAP\n\tSupplied OpenID URL\ttradeit.gg.json\nUpgrader\nupgrader.pro\n\tCLEAN\n2026-09-21 · raw HTML\n\tupgauth.space\tCLEAN\n2026-09-21 · raw HTML\n\t2026-08-14\nRDAP\n\tSupplied OpenID URL\tupgrader.pro.json\nNguồn: steamcommunity.com/linkfilter, yêu cầu GET không xác thực, 2026-09-21, 53 máy chủ, khoảng cách giữa các ký tự trong 3; steam_tos_assets/linkfilter-recheck-2026-09-21.json; mã HTML thô trong steam_tos_assets/linkfilter-raw/. Thời gian đăng ký: RDAP, steam_tos_assets/domain-registration.json. · Kiểm tra trước đó tại 2026-09-19 trong linkfilter-all-results.json · các bản ghi tuyến đường trong auth-route-audit.json · Các ảnh chụp màn hình từ Wayback Machine của các trang Link Filter, 2026-09-21, được liệt kê trong wayback-snapshots.json (không có ảnh chụp nhanh nào cho rbsnin.com; tệp raw cục bộ là bản ghi duy nhất).\n\nThời gian đăng ký: RDAP (steam_tos_assets/domain-registry/). “URL OpenID được cung cấp” chỉ xác định các tham số yêu cầu, chứ không phải là quá trình đăng nhập đã hoàn tất. Các tác giả không thực hiện đăng nhập thành công trên bất kỳ nền tảng nào. Một tên miền riêng biệt không tự nó là bằng chứng về việc lách luật. \"0 auth hosts blocked\" cũng không phải là một phát hiện độc lập: việc chặn một máy chủ xác thực sẽ làm gián đoạn quá trình đăng nhập Steam trên nền tảng đó, do đó, một danh sách được lập từ các lần đăng nhập thành công không thể chứa máy chủ xác thực bị chặn. Quan sát có trọng lượng là sự kết hợp và thời gian tồn tại của nó — một tên miền chính trên Bộ lọc Liên kết bên cạnh một tên miền đăng nhập đã hoạt động trong nhiều năm. Bảng này chứa các hàng từ 30: 25 của các tuyến đường 27 kèm theo tệp bằng chứng cho từng tuyến đường, cộng thêm năm mục được thêm vào từ 2026-09-22, trong đó sự phân tách của Bộ lọc Liên kết được ghi lại trong linkfilter-2026-09-22.json mặc dù chính vùng dữ liệu này đã được thu thập thủ công — các hàng tương ứng trong cột “nguồn” đã nêu rõ điều đó. Hai đường dẫn tệp bằng chứng không được hiển thị là skinsnipe.com (máy chủ xác thực pricing.tradeupspy.com, đã đăng ký tại 2020-03-11) và csgobig.com (máy chủ xác thực letmeinbig.com, đã đăng ký tại 2023-01-20); cả hai đều trả về kết quả “BLOCKED main / CLEAN auth host” trong quá trình kiểm tra tại 2026-09-22,, được ghi lại với mã SHA-256 trong linkfilter-2026-09-22c.json, nhưng mã HTML thô của lô đó không có trong bộ đã được xuất bản, do đó chúng được liệt kê tên ở đây thay vì được gán một hàng – điều mà mọi dòng khác trong bảng này đều có thể minh chứng. Các tuyến đường còn lại thuộc dự án “12” được thu thập thủ công trong sổ đăng ký được xác định rõ là như vậy trong master_registry.json dưới realm_src: user.\n\nKiểm toán thực nghiệm sơ cấp · Khoảng thời gian nhiều năm\nCái bẫy “Tầm nhìn tổng thể”: Bộ lọc liên kết chỉ là “hành động tuân thủ cho có lệ”, chứ không phải là lá chắn\n\nTrên các trình duyệt máy tính để bàn, người dùng được bảo vệ bởi các cơ chế phòng thủ bên ngoài: Google Safe Browsing và Microsoft SmartScreen sẽ chặn các cuộc tấn công lừa đảo đã biết bằng cách hiển thị cảnh báo màu đỏ toàn màn hình. Trong chế độ Big Picture của Steam, giao diện hiển thị trong trò chơi (Shift+Tab) và bộ thẻ “Steam” (SteamOS), các cơ chế phòng thủ đó không tồn tại. Trình duyệt tích hợp không hỗ trợ bất kỳ tiện ích mở rộng nào, vô hiệu hóa các công cụ Duyệt web an toàn bên ngoài và chỉ để lại cho người dùng đúng một lớp bảo vệ duy nhất: Valve's linkfilter giữa các mô.\n\nVuốt để so sánh cả bốn kết quả →\n\n92.5%\n2025–2026 lừa đảo kiểu hiện đại đạt yêu cầu (37/40)\n77.5%\n2023–2024 Lừa đảo qua email thời kỳ CS2 đạt yêu cầu (31/40)\n70.0%\n2021–2022 lừa đảo kiểu cũ đạt yêu cầu (28/40)\n7 / 7\nđường ống dẫn nước dùng cho hoạt động cờ bạc bị chặn (kiểm soát dương tính)\nKiểm toán theo chiều dọc kéo dài nhiều năm: 120 Kiểm tra trực tiếp các tên miền lừa đảo thuần túy Steam (24 Sep 2026)\n\nĐể kiểm tra xem bộ lọc của Valve chỉ đơn thuần là chậm trong việc nhận diện các mối đe dọa mới hay về cơ bản là không thể phát hiện được chúng, chúng tôi đã tiến hành kiểm tra 120 đã xác nhận các tên miền lừa đảo nhắm mục tiêu cụ thể vào Steam trên ba nhóm đối tượng theo thời gian so với steamcommunity.com/linkfilter:\n\nKhóa học “1:” 2021–2022 (Chương trình trao đổi truyền thống & Nhận vật phẩm ngẫu nhiên) — 70.0% Clean Pass (28/40). Ngay cả 4 đến 5, nhiều năm sau khi bị các tổ chức giám sát cộng đồng đưa vào danh sách theo dõi, 7 – một trong những máy chủ lừa đảo kế thừa từ 10 – vẫn đang hoạt động mà không bị chặn.\nCohort 2: 2023–2024 (CS2 Beta: Tin đồn và các lời kêu gọi hỗ trợ giả mạo) — 77.5% Clean Pass (31/40). Các chiến dịch mạo danh các bản phát hành của Counter-Strike 2 và các lời kêu gọi giả mạo từ cộng đồng (e.g. cs2-steam.com, appealsteamcommunity.help) đi thẳng qua.\nKhóa học “3:” 2025–2026 (Triển khai Serverless Edge & Sao chép Favicon) — 92.5% Clean Pass (37/40). Các bộ công cụ lừa đảo hiện đại đang được triển khai trên EdgeOne, Vercel và các trang web của Cloudflare (e.g. steamgifter.online, steam-dp4lt5b8fnez.edgeone.dev) đi qua mà hầu như không gặp trở ngại nào.\n\nHệ thống đo từ xa và bảo hiểm trách nhiệm pháp lý, chứ không phải bảo vệ. Tại sao Bộ lọc liên kết (Link Filter) lại tồn tại nếu nó vẫn chuyển hướng từ 70% sang 92.5% – một trang lừa đảo thuần túy (Steam)? Nó đóng vai trò như một tuyên bố miễn trừ trách nhiệm của doanh nghiệp và một cảm biến theo dõi nhấp chuột ra ngoài. Bằng cách hiển thị một thông báo lịch sự \"Bạn đang rời khỏi trang Steam\" Trong thông báo có nút “Tiếp tục” màu xanh lá cây có thể nhấp vào, Valve chuyển trách nhiệm pháp lý sang cho nạn nhân theo Thỏa thuận người đăng ký của Steam (*“người dùng đã tự nguyện truy cập ra khỏi Steam”*). Valve thu thập dữ liệu theo dõi về lần nhấp chuột này, nhưng không ngăn chặn hành vi trộm cắp.\n\nBằng chứng về mã băm Favicon: Không thu thập bất kỳ nguồn dữ liệu đe dọa nào. Các nền tảng tình báo mối đe dọa độc lập (urlscan.io, Shodan, Censys) phát hiện các bộ công cụ lừa đảo Steam đang hoạt động thông qua việc tìm kiếm đơn giản mã băm favicon chính thức của Steam (page.favicon.hash:9f890a9debcdfccc339149a7943be9aff9e4c9203c2fa37d5671a5b2c88503ad NOT domain:*.steampowered.com). Quy trình kiểm tra tự động cơ bản này giúp phát hiện các cụm lừa đảo đang hoạt động chỉ trong vài giây. Valve không đồng bộ hóa với các nguồn dữ liệu bên ngoài, không thực hiện việc truy tìm mối đe dọa dựa trên hàm băm và chỉ can thiệp thủ công khi bị cơ quan quản lý yêu cầu (lệnh cấm cờ bạc WSGC của 2016) hoặc để bảo vệ các chuỗi tên miền đã đăng ký nhãn hiệu của mình.\n\nCác bằng chứng kiểm toán chính: Kiểm toán theo chiều dọc trên nhiều năm đối với lĩnh vực “120-”: longitudinal-steam-phishing-audit.json · Mẫu lừa đảo qua email Steam liên quan đến vụ việc “100”: linkfilter-steam-phishing-100.json · Kiểm toán nguồn cấp dữ liệu trên diện rộng (n =250): linkfilter-coverage-2026-09-22.json.\n\nCSGOEmpire — đăng ký hàng loạt mười tên miền xác thực được đánh số\n\nVào ngày 2020-07-20 mười tên miền được đánh số, csgoempirelogin1.com qua csgoempirelogin10.com, đã được đăng ký. Dấu thời gian của Verisign RDAP đã được lưu trữ cho cả mười tài khoản: login1 05:49:06Z, login5 05:49:08Z, login2 05:49:11Z, login3 05:49:14Z, login4 05:49:17Z, login6 05:49:20Z, login7 05:49:23Z, login8 05:49:26Z, login9 05:49:28Z — chín tên miền trong 22 giây — và login10 tại 05:56:03Z, bảy phút sau đó. Khoảng cách giữa các tên miền phù hợp với một thao tác đăng ký hàng loạt từ một nhà đăng ký duy nhất.\n\nMô hình này phù hợp với các máy chủ dự phòng đã được cấu hình sẵn; chỉ login4 đã được ghi nhận trong một yêu cầu OpenID thực tế. Cả csgoempire.com và csgoempirelogin4.com đều trả về kết quả “CLEAN” trong tính năng Link Filter trên 2026-09-21; CSGOEmpire không có tên trong danh sách các trang web được đề cập trong các bài báo về các thông báo ngày 7 tháng 2016.\n\n# DNS — tất cả các địa chỉ 10 đều đang hoạt động (ngày 2026 tháng 9)\nĐược rồi csgoempirelogin1.com 172.67.129.43\nĐược rồi csgoempirelogin2.com 172.67.175.168\nĐược rồi csgoempirelogin3.com 188.114.96.3\nĐược rồi csgoempirelogin4.com 188.114.96.11 ← trong lưu lượng OpenID\nĐược rồi csgoempirelogin5.com 172.67.160.194\nĐược rồi csgoempirelogin6 –10.com Cloudflare IP\nNXDOMAIN: csgoempirelogin11.com\nTất cả các địa chỉ 10 đã được đăng ký tại 2020-07-20; tất cả các địa chỉ 10 đã được gắn dấu thời gian tại RDAP(steam_tos_assets/domain-registry/csgoempireloginN.com.rdap.json)\nKết luận dành cho các cơ quan quản lý\nViệc tên miền chính bị chặn trong khi máy chủ xác thực lại không bị chặn sẽ khiến đường dẫn đăng nhập vẫn mở — và tình trạng này kéo dài suốt nhiều năm.\n\nKhối Link Filter trên miền chính là một bản ghi công khai, có thể xác minh được. Máy chủ xác thực (auth host) xử lý lưu lượng truy cập \"Đăng nhập bằng Steam\" và xuất hiện trong các tham số yêu cầu OpenID của chính Valve. Qua các kiểm tra trên 2026-09-21 và 2026-09-22, trong các cặp bộ lọc phân chia 26, tên miền chính trả về khối Link Filter trong khi máy chủ proxy truyền tải thông tin đăng nhập của nó không trả về gì. Bảng đăng ký ở trên đo lường nửa còn lại của điều đó: các máy chủ này không phải là các tên miền tạm thời có tuổi thọ ngắn. Một số tên miền đã được đăng ký hơn một thập kỷ tính đến thời điểm kiểm tra, và mỗi ngày trong khoảng thời gian đó đều là ngày mà Valve nhận được tên máy chủ trong các tham số yêu cầu của chính nó. Valve chưa công bố bất kỳ bản ghi thực thi nào theo từng nhà điều hành, do đó không thể xác định từ dữ liệu công khai liệu có bất kỳ biện pháp nào khác được áp dụng cho các máy chủ này hay không.\n\n12 Năm 6 tháng\ncsgogem.com bị chặn trong Bộ lọc liên kết.\nMáy chủ đăng nhập của nó api.csgem.com đã\nđã đăng ký từ ngày 2014-03-08 và hiện không còn.\nTóm tắt bằng ngôn ngữ dễ hiểu — Dành cho các cơ quan quản lý và tòa án (mở rộng)\nTóm tắt bằng ngôn ngữ dễ hiểu — dành cho các cơ quan quản lý\nBối cảnh: “Steam” là gì và tại sao nó lại quan trọng trong bối cảnh này\n\nSteam là một nền tảng phần mềm do Công ty Valve (Bellevue, Washington, Hoa Kỳ) vận hành. Steam hoạt động như một nhà cung cấp danh tính kỹ thuật số: các trang web cá cược và trò chơi trực tuyến trên Internet sử dụng một hệ thống có tên “Đăng nhập bằng Steam” — một nút cho phép trang web xác minh rằng người truy cập có tài khoản Steam thực sự. Điều này tương tự như tính năng “Đăng nhập bằng Google” hoặc việc xác minh thẻ căn cước do chính phủ cấp: trang web sẽ chuyển người dùng đến máy chủ của Steam, Steam xác nhận danh tính của họ, và Steam chuyển họ trở lại trang web. Valve vận hành hệ thống xác thực. Mỗi lần đăng nhập thông qua tùy chọn “Đăng nhập bằng Steam” đều được xử lý qua các máy chủ của chính Valve.\n\nValve đã làm gì: Chặn tên miền\n\nVào tháng 7 2016,, trước áp lực từ giới truyền thông và pháp lý liên quan đến cờ bạc trực tuyến, luật sư của Valve đã gửi thông báo đến khoảng 23 các trang web cờ bạc bị nêu tên (theo các báo cáo truyền thông tại 21 vào ngày 2016 tháng 7); vào tháng 10 2016 Valve đã thông báo với Ủy ban Cờ bạc Tiểu bang Washington rằng họ đã liên hệ với hơn bốn mươi trang web. Một số tên miền cờ bạc xuất hiện trong Steam Bộ lọc liên kết — một danh sách khiến bất kỳ liên kết nào đến các trang này được đăng trên Steam (trong phần trò chuyện, trên trang hồ sơ, trong cửa hàng) đều hiển thị một trang cảnh báo: \"Liên kết bị chặn!\" Bộ lọc liên kết (Link Filter) là biện pháp thực thi duy nhất mà hiệu quả của nó có thể được quan sát từ bên ngoài Valve.\n\nVí dụ: Một liên kết đến rollbit.com Trong phần “Steam” hiển thị trang cảnh báo “Link Filter” (đã kiểm tra tại 2026-09-19 và 2026-09-21). Trên lý thuyết, trang web cờ bạc này đã bị chặn.\nMiền proxy là gì?\n\nA Máy chủ xác thực trên miền riêng là một máy chủ proxy xác thực: một địa chỉ trang web thứ hai, trên một tên miền có thể đăng ký khác, do cùng một nhà điều hành đặt giữa người dùng và Steam với mục đích duy nhất là thực hiện bước “Đăng nhập bằng Steam”. Địa chỉ này đóng vai trò là máy chủ trung gian cho quá trình đăng nhập. Người dùng tưởng rằng họ đang đăng nhập vào nền tảng; yêu cầu được gửi đến Valve mang tên máy chủ của máy chủ trung gian, chứ không phải của nền tảng. Thông thường, máy chủ này không có bất kỳ liên kết nào hiển thị công khai với trang web cá cược, và đây chính là địa chỉ mà người dùng được chuyển hướng trở lại sau khi Steam xác thực danh tính của họ.\n\nVí dụ: Rollbit hoạt động theo rollbit.com, mà bộ lọc liên kết (Link Filter) đã chặn. Đối với xác thực theo phương thức “Steam”, luồng dữ liệu được ghi nhận trên 2026-09-20 đã sử dụng một địa chỉ riêng biệt: rbsnin.com , địa chỉ đã đăng ký 2026-09-18. Địa chỉ này trả về Không có khối Lọc liên kết trên 2026-09-21. Trang web cờ bạc này vẫn tiếp tục hoạt động, và quy trình đăng nhập vào Steam của trang web này được thực hiện thông qua máy chủ không bị chặn.\nĐiểm then chốt: Máy chủ xác thực được gửi đến Steam trong mỗi yêu cầu\n\nValve không cần quét hay thu thập dữ liệu để xác định các máy chủ xác thực nào đang được sử dụng. Steam là Nhà cung cấp danh tính OpenID đối với các trang web này, và mỗi lần nhấp vào “Đăng nhập bằng Steam” sẽ gửi một yêu cầu GET đến các máy chủ của Valve, trong đó chứa tên máy chủ xác thực dưới dạng văn bản thuần túy. Theo OpenID 2.0 §9.1, return_to Trường này về mặt kỹ thuật là tùy chọn, nhưng nếu thiếu nó thì Steam sẽ không thể trả về kết quả đăng nhập, do đó để quá trình đăng nhập tại Steam diễn ra thành công thì trường này thực tế là bắt buộc. Bản thân Steam sẽ hiển thị tên máy chủ trên trang đăng nhập (\"<host> không có liên quan đến Steam hoặc Valve\").\n\n— Cấu trúc của yêu cầu mà Steam nhận được (tên máy chủ được ghi nhận cho Rollbit trên 2026-09-20): —\nNHẬN steamcommunity.com/openid/đăng nhập\n&openid.mode=checkid_setup\n&openid.return_to=https://rbsnin.com/… ← thực tế là bắt buộc; xuất hiện trong nhật ký của Valve\n&openid.realm=https://rbsnin.com ← do trang web tự công bố; được hiển thị trên trang đăng nhập của Steam\nNếu trang web sử dụng cơ chế xác thực giữa các máy chủ (check_authentication), nhật ký của Valve cũng sẽ ghi lại địa chỉ IP máy chủ của nền tảng và mạng lưu trữ.\n\nViệc trích xuất tên máy chủ từ yêu cầu này là một thao tác tiêu chuẩn. Bản ghi thực thi — ghi lại những máy chủ nào đã được xử lý, những máy chủ nào chưa được xử lý, và theo tiêu chí nào — chỉ tồn tại trong hạ tầng của Valve và chưa được công bố.\n\nĐiều này chứng tỏ điều gì\n\n1. Khối “Link Filter” tác động lên các liên kết, chứ không phải lên các lần đăng nhập. Chặn tên miền chính (ví dụ: rollbit.com) hiển thị thông báo cảnh báo cho những người dùng nhấp vào các liên kết dẫn đến trang này trong Steam. Điều này không làm gián đoạn hoạt động của trang web, cũng như không ngăn cản việc sử dụng dịch vụ OpenID của chính Valve thông qua một địa chỉ khác.\n\n2. Các máy chủ xác thực đã được kiểm tra không bị chặn. Bảng trên cho thấy các máy chủ xác thực thuộc các miền riêng biệt được đăng ký trong khoảng thời gian từ 2011 đến tháng 9 2026,; một số trong số đó được đăng ký nhiều năm sau các thông báo vào tháng 7 2016. Trong các cặp 26, miền chính trả về kết quả chặn bởi Bộ lọc Liên kết (Link Filter) trong khi máy chủ proxy chứa thông tin đăng nhập của nó thì không (các kiểm tra không xác thực, 2026-09-21 và 2026-09-22; các phản hồi thô và mã SHA-256 đã được lưu lại). Proxy đó sẽ ngừng hoạt động vào ngày Valve từ chối nó, đó là lý do tại sao tiêu chí đánh giá ở đây là thời gian hoạt động của nó, chứ không phải việc nó có nằm trong danh sách hay không. Valve nhận được các tên máy chủ này trong các yêu cầu OpenID của chính nó. Không thể xác định từ dữ liệu công khai liệu có bất kỳ biện pháp nào khác ngoài bộ lọc liên kết (Link Filter) được áp dụng hay không, vì Valve chưa công bố bất kỳ bản ghi thực thi nào theo từng nhà cung cấp dịch vụ.\n\n3. Các trang web này vẫn tiếp tục thực hiện xác thực thông qua hạ tầng củValve. \"Đăng nhập bằng Steam\" là dịch vụ củValve; mọi quá trình xác thực thông qua dịch vụ này đều là một yêu cầu mà Valve nhận và xử lý. Valve cũng thu được doanh thu từ các khóa case, và Chợ Cộng đồng Steam thu một khoản phí tổng cộng khoảng 15% đối với các giao dịch được thực hiện bên trong Chợ (không áp dụng cho các giao dịch bên ngoài). Hành động “Link Filter” đã tạo ra một bản ghi công khai; hành động này không làm gián đoạn mối quan hệ xác thực.\n\nViệc chặn có hiệu quả không?\n\nTương tự như vậy: khi nhà đăng ký tên miền miễn phí Freenom ngừng hoạt động vào năm 2023,, các chiến dịch lừa đảo dựa vào các tên miền của họ cũng bị gián đoạn. Tính liên tục trong hoạt động phụ thuộc vào sự ổn định của cơ sở hạ tầng.\n\nCùng một logic cũng áp dụng ở đây. Nếu một máy chủ xác thực bị từ chối trong quá trình xử lý OpenID của Steam, chức năng “Đăng nhập bằng Steam” của nền tảng sẽ ngừng hoạt động cho đến khi một máy chủ mới được đăng ký, chứng chỉ được cấp và thông tin DNS được cập nhật. Trong khoảng thời gian đó: hệ thống sẽ ngừng hoạt động.\n\nViệc xoay vòng không khiến việc chặn trở nên vô ích. Điều này khiến việc chặn trở thành một chi phí vận hành. Do các máy chủ mới xuất hiện trong nhật ký yêu cầu của Valve ngay từ lần sử dụng đầu tiên, nên tốc độ phản hồi có thể phụ thuộc vào tốc độ của lần sử dụng đó.\n\nViệc đăng ký theo lô bản thân nó đã là một tín hiệu: Các tên miền login1–login10 của CSGOEmpire đã được đăng ký trên 2020-07-20,, trong đó chín tên miền được đăng ký trong vòng 22 giây (Verisign RDAP). Phản hồi không nhất thiết phải được thực hiện theo từng tên miền riêng lẻ; một chuỗi các tên miền được đăng ký liên tiếp trong cùng một phiên đăng ký có thể được xác định là một chuỗi.\n\nHồ sơ công khai không cho thấy có bất kỳ nỗ lực nào nhằm chặn các máy chủ xác thực đã bị vô hiệu hóa bởi cơ chế xoay vòng.\nBáo cáo này cho thấy các tên miền chính đã bị chặn trong khi các máy chủ proxy quản lý từng tài khoản đăng nhập vẫn tiếp tục hoạt động — các cặp tên miền 26 theo dữ liệu tại 2026-09-22,; máy chủ xác thực lâu đời nhất được đăng ký là 12 năm 6 tháng — và không có hồ sơ thực thi nào được công bố đối với bất kỳ nhà khai thác nào.\nDo đó, câu hỏi đặt ra cho cơ quan quản lý là: Valve đã áp dụng biện pháp thực thi nào, nếu có, đối với các máy chủ xác thực mà họ nhận được trong các yêu cầu OpenID của chính mình?\nValve đã làm gì — và tại sao nó không làm gián đoạn đường dẫn xác thực\n\nBảng dưới đây so sánh từng hành động được công khai ghi nhận của Valve với việc liệu hành động đó có ảnh hưởng đến điểm truy cập xác thực OpenID hay không. Kết luận ở đây không phải là “Valve không làm gì cả” — mà là không có hành động nào được công khai ghi nhận tác động đến điểm mà các phiên đăng nhập vào nền tảng cờ bạc đi qua các máy chủ của Valve.\n\nNgày\tValve Hành động\tBị ảnh hưởng openid.return_to đường dẫn?\nJuly 2016\tPublic statement of 13 July 2016; counsel's notices to ~23 named sites (press, 21 July 2016); >40 sites contacted per Valve's October 2016 letter to WSGC\tNo. Notices and the Link Filter act on operators and links; the OpenID request path was not changed.\n2017\tClosure of IEconItems_730/GetPlayerItems (according to CSFloat's engineering account; no Valve changelog located)\tNo. Affected public item-history visibility. OpenID authentication was not modified.\n2018-03-29\tCS:GO 7-day trade lock announced (blog.counter-strike.net)\tNo. Slowed item movement; the OpenID request path was not changed.\n2022-05-10\tTrade-cancellation endpoints removed from the public Web API (user-detected; no Valve changelog — node-steam-tradeoffer-manager #325)\tNo. Closed the offer-swap tooling; OpenID authentication was not modified.\n2023-12-04\tAPI-key creation now requires mobile confirmation (steamcommunity.com/dev/apikey; no changelog)\tNo. Protected the key endpoint; the auth hosts documented here were not affected.\n2026-09-19 / 09-21\tSteam Link Filter state as observed by the authors\tNo. 14 main domains returned a block in the saved 2026-09-21 recheck — 26 split pairs in the register by 2026-09-22 — while the proxy carrying each login kept running.\nNguồn: Valve; tuyên bố của 13 ngày 2016 (store.steampowered.com/oldnews/22883, đã lưu trữ 2026-09-21) · Bài viết kỹ thuật trên tạp chí “CSFloat” về việc đóng cửa nhà máy điện than 2017 (blog.csfloat.com, đã lưu trữ 2026-09-21) · Trạng thái bộ lọc liên kết: linkfilter-recheck-2026-09-21.json.\nKết quả này có thể bị bác bỏ chỉ bằng một trường hợp đã được công bố, trong đó Valve đã từ chối một yêu cầu OpenID vì openid.return_to được trỏ đến một máy chủ được cấp phép hoạt động cờ bạc. Không tìm thấy trường hợp nào như vậy trong hồ sơ công khai.\nHai bản đăng ký máy chủ xác thực gần đây nhất\nhowl.uno2026-08-11 (RDAP) đã được đăng ký trước 41 vài ngày so với 2026-09-21; khi truy cập 2026-09-18,, howl.gg đã trả về thông báo chặn bởi bộ lọc liên kết (Link Filter) đối với , 2026-09-19 và 2026-09-21.. Vẫn chưa xác định được liệu việc chặn này có diễn ra trước khi đăng ký hay không.\nrbsnin.comđã được đăng ký tại 2026-09-18T09:34:52Z (Verisign RDAP) và được phát hiện trong quy trình đăng nhập Steam của Rollbit trên 2026-09-20 thông qua thông báo trên trang đăng nhập của chính Steam; rollbit.com đã trả về thông báo chặn từ Bộ lọc Liên kết (Link Filter) trên 2026-09-19 và 2026-09-21,, trong khi rbsnin.com thì không.\nMỗi máy chủ trong bảng trên được gửi đến các máy chủ xác thực của Valve dưới dạng openid.realm trong mỗi lần đăng nhập.\nDữ liệu đầy đủ theo từng tuyến đường và kết quả của bộ lọc liên kết: bảng trong Phần 3 ở trên; kết quả thô trong linkfilter-recheck-2026-09-21.json và linkfilter-all-results.json.\nPhương pháp luận — Cách xác định số lượng bộ lọc tuyến đường và liên kết\n1. Giải quyết tên miền\nCuộc kiểm toán “2026-09-21” đã giải quyết yêu cầu “78” từ 189 liên quan đến các nền tảng được đề cập: 33 xác thực trên tên máy chủ của chính chúng và 20 trên tên miền con của chính chúng — xác thực trực tiếp, và không có đường dẫn nào trong số đó được tính là các đường dẫn thuộc miền riêng biệt. Phần còn lại 25 xác thực thông qua một tên miền riêng có thể đăng ký, trên 24 tên miền riêng biệt (dota2.net được dùng chung cho market.csgo.com và rust.tm): 10 được xác định thông qua ghi lại màn hình trình duyệt trực tiếp, 3 thông qua thông báo trên trang đăng nhập của chính Steam, 12 thông qua một URL OpenID được cung cấp. Danh sách theo thời gian thực (master_registry.json, 2026-09-22) mở rộng điều đó thành 44 các tuyến đường có miền riêng biệt: 26 các cặp bộ lọc-phân chia (miền chính bị chặn, máy chủ xác thực được chấp nhận) cùng với 18 các tuyến đường khác mà không có phân chia miền chính. Trong số các 44, 27 lưu giữ hồ sơ chứng cứ cho từng tuyến đường; các mẫu còn lại thuộc loài 17 được thu thập bằng tay và đã được đánh dấu realm_src: user trong danh sách. Năm trong số mười bảy địa chỉ đó — csgogem.com, gamdom.com, 12cs.fail, csgolounge.com và dota2lounge.com — đã được thêm vào tại 2026-09-22 kèm theo bản ghi Link Filter của cả hai máy chủ (HTML thô + SHA-256 trong linkfilter-2026-09-22.json), do đó, sự phân chia này vẫn được ghi nhận rõ ràng dù vùng dữ liệu được thu thập thủ công; chúng xuất hiện trong bảng trên cùng với các tuyến đường trong tệp bằng chứng. tfauth.com (tf2easy.com) đã bị xóa khỏi danh sách đăng ký trên 2026-09-22:, tương tự như arena.fragnet.net, không có liên kết nào có thể xác minh được để kết nối nó với trang web gốc. Số lượng có thể tính lại từ dữ liệu đã công bố auth-route-audit.json (2026-09-21) tuân theo một quy tắc duy nhất: một nền tảng chỉ được tính khi máy chủ OpenID Steam được ghi nhận của nền tảng đó nằm trên một tên miền có thể đăng ký khác với chính nền tảng đó.\n2. Steam Trạng thái bộ lọc liên kết\nĐã được kiểm tra thông qua steamcommunity.com/linkfilter/?url=https://[domain], chưa xác thực, trên 2026-09-19 và 2026-09-21; mã HTML thô được lưu dưới dạng SHA-256.. Trạng thái được ghi nhận riêng biệt cho tên miền chính và máy chủ xác thực. Một bộ phân loại phân biệt thông báo chung chung “Bạn đang rời khỏi Steam” (CLEAN) với trang “Liên kết bị chặn! ... được đánh dấu là có khả năng độc hại\" (BLOCKED); một kiểm soát google.com xác nhận rằng hai trường hợp này không bị nhầm lẫn. Một biến thể đã được xác thực trước đó của thử nghiệm này đã bị loại bỏ sau khi nó trả về kết quả \"bị chặn\" cho mọi tên miền, bao gồm cả kiểm soát đó — nguyên nhân được xác định là do một cookie phiên không hợp lệ trong tập lệnh thăm dò, chứ không phải là kết quả thực tế.\n3. Quan sát máy chủ auth\nGhi lại trực tiếp: Trình duyệt Playwright đã truy cập vào quy trình đăng nhập của từng nền tảng và openid.return_to Tên máy chủ được lấy từ yêu cầu đã bị chặn. Thông báo trên trang đăng nhập: Tên máy chủ được lấy từ chính trang Steam \"<host> không có liên quan đến Steam hoặc Valve\" văn bản mà Steam hiển thị từ openid.realm (rbsnin.com, sc-auth.net, auth.dota.trade). URL được cung cấp: một URL đăng nhập Steam được cung cấp cho các tác giả; URL này xác định các tham số yêu cầu, chứ không phải là một quá trình đăng nhập đã hoàn tất. Không có quá trình đăng nhập nào được hoàn tất trên bất kỳ nền tảng nào.\n4. Phạm vi bảo hiểm — những vấn đề chưa được giải quyết, và tại sao điều đó lại quan trọng\nTrong số các nền tảng thuộc Hệ thống Ngân hàng Liên bang (189), 110 không hình thành được tuyến đường cố định nào và có một trường hợp không áp dụng (189 − 78 − 1). Hồ sơ này không tính đến bất kỳ trường hợp nào trong số đó. Chi tiết phân tích từ tệp kiểm toán 110,: 22 – các lỗi liên quan đến bot, 14 – các trường hợp hết thời gian chờ, 12 – các lỗi HTTP và 10 – các lỗi điều hướng — người quan sát không thể truy cập được quy trình đăng nhập, mặc dù hầu hết các trang web này đều mở bình thường trên trình duyệt thông thường; 20 không hiển thị ô đăng nhập Steam trên trang đích; 16 đã truy cập vào quy trình đăng nhập nhưng không thể giải quyết được tên miền; các tên miền 11 không thể giải quyết được thành DNS; 5 bị dừng lại tại màn hình yêu cầu đồng ý. Danh sách dưới đây phân loại các trường hợp tương tự tại 110 theo cách khác: các trang 11 không thể giải quyết được thành DNS được liệt kê riêng biệt như Đã xóa · NXDOMAIN, và mục duy nhất không phù hợp được gộp vào phần còn lại. 189 là các nền tảng đã được kiểm toán, 11 đã bị xóa do nhận được thông báo NXDOMAIN dứt khoát từ cả hai bộ giải quyết tên miền, 178 được giữ lại (platform-audit.json, platforms-removed.json). 137 Các miền xác thực mà sổ cái đã đoán được dựa trên mẫu đặt tên đã bị xóa khỏi dữ liệu trên 2026-09-19 — chưa từng được ghi nhận, do đó không có bằng chứng. Ba trong số các dự đoán này đã bị các URL OpenID được cung cấp bác bỏ: buff.163.com, gamerpay.gg và csgoluck.com thực hiện xác thực trực tiếp, trái ngược với các dự đoán là buffauthproxy.163.com, gamerpayredirect.io và lucklogin.app. Các mục bị loại bỏ được liệt kê trong tệp kiểm toán đã được công bố.\nChỉ số tương đối (25) là mức tối thiểu, không phải mức tối đa. Trong số các nền tảng thuộc Mạng lưới Truy cập Internet (78) đã được giải quyết, 25 sử dụng một tên miền riêng biệt, trong khi 53 thì không. Không có bất kỳ giả định nào về 110 chưa được giải quyết dựa trên tỷ lệ đó, và không có dự báo nào từ tỷ lệ này xuất hiện ở bất kỳ đâu trong hồ sơ này. Mỗi trường hợp đều có thể được giải quyết bằng cách một người truy cập trang web và nhấn \"Đăng nhập với Steam\": tên máy chủ xác thực nằm trong URL của trang Steam được tải.\nMục đích của phần này: Một người quan sát độc lập cần có trình duyệt và rất nhiều kiên nhẫn để xác định các nền tảng 189, và đã tìm thấy 78.; còn Valve thì cần thực hiện truy vấn cơ sở dữ liệu. Mọi nền tảng sử dụng tính năng “Đăng nhập bằng Steam” — dù đã được xác định hay chưa — đều gửi openid.realm đến điểm cuối xác thực của Valve mỗi khi đăng nhập. Khoảng trống trong bảng này xuất hiện do các tác giả nằm ngoài hệ thống. Khoảng trống này không tồn tại đối với Valve.\nCác tên máy chủ proxy được ghi nhận nằm trong auth-route-audit.json. Ngày đăng ký tên miền từ RDAP (Verisign) / IP2WHOIS. Kết quả của công cụ lọc liên kết là linkfilter-all-results.json.\nVí dụ minh họa để dễ hiểu hơn\n\nHãy tưởng tượng một công ty taxi có giấy phép được cơ quan quản lý thông báo rằng họ không được phép tiếp tục hoạt động tại địa chỉ đã đăng ký trên Phố Chính nữa. Công ty này tháo biển hiệu khỏi Phố Chính. Việc tháo dỡ biển hiệu này được ghi nhận lại. Tuy nhiên, chính công ty này lại mở một địa chỉ mới trên Phố Phụ — được đăng ký dưới một tên khác — và tiếp tục hoạt động từ đó. Các cơ quan quản lý vận hành hệ thống điều phối trung tâm mà mọi xe taxi từ cả hai địa chỉ đều sử dụng. Mỗi yêu cầu đi xe đều hiển thị “đón tại Side Street.” Các cơ quan quản lý chưa bao giờ thu hồi giấy phép hoạt động tại Side Street. Việc tháo dỡ biển hiệu “Main Street” là biện pháp xử lý duy nhất được thực hiện. Công ty taxi này chưa bao giờ ngừng hoạt động.\n\nPhần A — Hồ sơ kỹ thuật · Mục3.1\nTrong cuốn sách “Steam”, danh sách của “Valve” là danh sách duy nhất.\n\nMột liên kết được nhấp vào trong ứng dụng khách “Steam”, giao diện phủ trong trò chơi hoặc chế độ Big Picture sẽ không mở trong trình duyệt của người dùng. Liên kết đó sẽ được hiển thị bên trong trình duyệt nhúng sẵn của “Steam” — nơi không có các lớp cảnh báo mà trình duyệt thông thường thường hiển thị. Bộ lọc liên kết không phải là một trong số nhiều biện pháp bảo vệ. Nó chính là toàn bộ hệ thống bảo vệ.\n\nTrong một trình duyệt thông thườngBa lớp độc lập\nGoogle Safe BrowsingMột trang chèn toàn màn hình dành cho các máy chủ nằm trong danh sách lừa đảo và phần mềm độc hại của Google, được cập nhật liên tục và không phụ thuộc vào trang web đang được truy cập.\nTiện ích mở rộng trình duyệt chống vi-rútHầu hết các sản phẩm dành cho thiết bị đầu cuối của người dùng đều đi kèm với một tiện ích mở rộng trình duyệt có chức năng kiểm tra địa chỉ đích dựa trên danh sách uy tín do chính nhà cung cấp lập ra.\nKiểm tra HTTPS tại điểm cuốiKhi sản phẩm thực hiện kiểm tra “TLS”, nội dung trang web sẽ được quét trước khi hiển thị cho người dùng.\nTrong ứng dụng kháchSteam, chế độ hiển thị chồng lớp và chế độ Big PictureMột lớp\nGoogle Safe BrowsingKhông có. Quy trình kiểm tra này yêu cầu các khóa “API” của Google, nhưng các khóa này không được cấp phát trong các bản dựng Chromium nhúng; khi các khóa này vắng mặt, tài liệu thiết kế của chính Chromium ghi rõ rằng trình xử lý Safe Browsing đơn giản là không bao giờ được thêm vào chuỗi yêu cầu.\nTiện ích mở rộng trình duyệt chống vi-rútKhông có. Trình hiển thị của Steam không phải là trình duyệt của người dùng và không tải bất kỳ tiện ích mở rộng nào từ hồ sơ trình duyệt của người dùng, do đó không có tiện ích mở rộng nào được chạy trên trang này.\nKiểm tra HTTPS tại điểm cuốiTùy thuộc vào sản phẩm. Lưu lượng truy cập được xử lý bên trong một tiến trình Valve đã được ký mã thay vì trong một trình duyệt được nhận diện, và một số sản phẩm đầu cuối miễn trừ các ứng dụng đã được ký mã khỏi quá trình kiểm tra TLS.\nBộ lọc liên kết “Steam”Danh sách chặn riêng của Valve, được tham chiếu khi một liên kết rời khỏi hệ sinh thái Steam. Đây là kiểm tra duy nhất được thực hiện — và bảng trên ghi lại kết quả mà nó trả về cho các máy chủ xác thực được đề cập trong phần này.\nMột thử nghiệm mà bất kỳ độc giả nào cũng có thể thực hiện, và kết quả sẽ không còn đúng nếu thử nghiệm đó thất bại\n\nMở một trong các URL kiểm tra tính năng Duyệt web an toàn do Google công bố (testsafebrowsing.appspot.com) trong Chrome: một trang chèn màu đỏ toàn màn hình sẽ xuất hiện. Mở cùng một URL từ một tin nhắn trò chuyện trên Steam, sao cho URL đó được hiển thị trong trình duyệt Steam hoặc lớp phủ: không có trang chèn nào xuất hiện. Cảnh báo duy nhất mà Steam có thể hiển thị là chính trang “Link Filter” của nó, và chỉ áp dụng cho các máy chủ có trong danh sách của Valve.\n\nKỷ lục về chương trình thưởng lỗi của chính ValveVấn đề về “một lớp” này đã từng được giải quyết trước đây — ngay trên chính đĩa nhạc củValve\n\nNếu Bộ lọc liên kết (Link Filter) là cơ chế kiểm tra duy nhất được thực thi bên trong máy khách, thì các tình huống lỗi của chính nó không phải là vấn đề phụ. Hai báo cáo trên chương trình HackerOne của Valve, cả hai đều đã được chấp nhận, đã được giải quyết và đều đã được công bố đầy đủ:\n\n#291750đã lưu trữ 2025-11-16 ↗Chuyển hướng mở · medium\nVượt qua cơ chế bảo vệ bộ lọc liên kết\n\nĐã báo cáo 19 vào ngày 2017,, đã được khắc phục, đã được công bố 9 vào ngày 2018.. Bằng chứng khái niệm trong chính báo cáo: thay thế dấu chấm trong ký tự tượng hình 。 (%E3%80%82) đối với dấu chấm trong tên máy chủ — it is possible to bypass the blocking. Phần nội dung xen kẽ mà phần này đề cập đến đã không xuất hiện.\n\n#1079561đã lưu trữ 2026-09-24 ↗Công bố thông tin · mức cao\nTrình duyệt web Big Picture bị rò rỉ cookie đăng nhập và tiết lộ thông tin nhạy cảm (có thể dẫn đến việc chiếm quyền kiểm soát tài khoản)\n\nĐã báo cáo 15 tháng 1 2021, đã được khắc phục, công bố 21 tháng 9 2021. Valve có mức độ nghiêm trọng cao, và tiêu đề nêu rõ hậu quả. Bản ghi công bố bao gồm tiêu đề, mức độ nghiêm trọng và các ngày tháng; phần mô tả kỹ thuật không có trong nội dung được công bố, do đó không trích dẫn thêm thông tin nào từ đó ở đây.\n\nĐó là cách hiểu của các tác giả, chứ không phải kết luận của bất kỳ báo cáo nào: Hai trường hợp này nằm ở hai bên của cùng một cánh cổng. Một là cảnh báo không xuất hiện trước khi trang đích được mở; trường hợp còn lại là phiên làm việc bị rời khỏi máy khách ngay khi một trang được mở bên trong đó. Chuỗi sự kiện diễn ra sau khi phiên làm việc bị đánh cắp — khóa được đăng ký mà không có lời nhắc, giao dịch thực tế bị hủy, một bản sao được gửi đến một bản sao giả mạo — chính là mô hình được nêu trong Phần 5 đến Phần 8. Cả hai báo cáo này đều đã được đóng lại; không có báo cáo nào được coi là lỗ hổng bảo mật đang tồn tại. Những gì các báo cáo này chỉ ra có phạm vi hẹp hơn nhưng cũng đủ thuyết phục: lớp bảo mật duy nhất còn lại đã có tiền lệ bị vượt qua, theo chính hồ sơ của Valve.\n\nNguồn: Hồ sơ công bố của HackerOne cho từng báo cáo, được trích xuất từ 2026-09-22 — số báo cáo, tiêu đề, nhóm, lỗ hổng, mức độ nghiêm trọng, ngày báo cáo, ngày công bố và trạng thái theo thông tin do HackerOne công bố. Hồ sơ trích xuất: hackerone-reports.json. Tại đây không nêu rõ mức tiền thưởng; trong hồ sơ đã được công bố mà chúng tôi tra cứu được cũng không có thông tin nào về điều này.\n\nQuan sát thực địa · PhishDestroyCác phát hiện thường khiến một chiến dịch kết thúc lại không làm cho những chiến dịch này kết thúc\n\nChúng tôi đã quan sát thấy các máy chủ lừa đảo liên tục thu hút lưu lượng truy cập trong khi vẫn đang chứa 20 hoặc phát hiện thêm các nhà cung cấp. Khi được phân phối qua web hoặc email, một chiến dịch ở trạng thái đó sẽ bị chặn chỉ sau vài ngày — cả trình duyệt lẫn phần mềm diệt virus đều thực thi các quyết định đó. Trong Steam, cả hai đều không làm vậy. Các quyết định đó đã tồn tại từ trước. Không có bất kỳ thành phần nào trong ứng dụng khách từng yêu cầu điều đó.\n\nĐiều này có ý nghĩa như thế nào đối với một trẻ vị thành niên đã cài đặt phần mềm diệt virus\n\nAnh ta không bỏ qua bất kỳ cảnh báo nào và cũng không vô hiệu hóa bất cứ thứ gì. Một tin nhắn xuất hiện tại Steam — một con dao miễn phí, một phiếu bầu cho đội của bạn bè — và trang web đó được mở tại Steam. Anh ta không bao giờ mở trình duyệt, nên trình duyệt cũng không bao giờ bảo vệ anh ta. Phần mềm diệt virus của anh ta đang chạy và có thể đã đánh giá tên miền đó là độc hại; nhưng phần mềm này không bao giờ được yêu cầu thực hiện điều đó. Mọi lời cảnh báo có thể ngăn cản anh ta đều đã có sẵn. Nhưng không có lời nào trong số đó đến được với anh ta. Anh ấy tin rằng mình chưa bao giờ rời khỏi “Steam”, và quả thực là vậy.\n\nChiêu trò tặng quà miễn phí không phải do kẻ lừa đảo nghĩ ra — việc tặng các vật phẩm miễn phí trong trò chơi “Valve” chính là cách các trang web về skin và cờ bạc quảng cáo, và đó chính là lý do tại sao tin nhắn này trông có vẻ bình thường. Các khiếu nại: kho lưu trữ các biện pháp thi hành. Dữ liệu về độ tuổi và trẻ em: Phần 17.\n\nNguồn: Steam hiển thị nội dung web thông qua Chromium Embedded Framework trong steamwebhelper quy trình — xem Phân tích kỹ thuật của DARKNAVY về 27 tháng 6 năm 2024 ↗ và của chính Valve Steam Diễn đàn Beta dành cho khách hàng ↗ đã lưu trữ 2025-08-04 ↗. Không dựa vào bất kỳ phiên bản CEF nào: Chromium nhúng không phải là Chrome và không đi kèm với bất kỳ dịch vụ nào của Google dành cho Chrome. Tính năng Duyệt web an toàn không sử dụng khóa API: Tài liệu thiết kế Chromium ↗ đã lưu trữ 2026-08-21 ↗, Các phím tắt trong Chromium API ↗ đã lưu trữ 2026-08-30 ↗ (“Nhiều API của Google được Chrome sử dụng là độc quyền của Google và không dành để sử dụng trong các sản phẩm phái sinh”), và hiệu ứng tương tự cũng xảy ra trong các bản dựng không có khóa khác — Thùng bia tự ủ số193814 ↗. Các URL thử nghiệm: testsafebrowsing.appspot.com ↗.\n\nHai chiếc đồng hồ khác nhau\nTuổi của tên miền.Ngày thực hiện quan sát.\n\nNgày tạo bản ghi đăng ký xác định thời điểm một tên miền được đăng ký. Bản ghi OpenID có ghi ngày tháng xác định máy chủ trả về trong bản ghi đó. Ngày tạo bản ghi đăng ký không thể bao gồm các năm trước ngày ghi trên bản ghi OpenID.\n\nDanh sách đầy đủ này phân biệt giữa một tên miền riêng biệt có thể đăng ký, tên miền con của chính trang web đó và một đường dẫn trực tiếp. Mỗi hàng đều có liên kết đến nguồn và kết quả từ DNS.\n\nKiểm tra thông tin đăng ký tên miền →· Tải xuống các ngày đăng ký ↗· Lặp lại quan sát ↗\n\nPhần A — Hồ sơ kỹ thuật · Mục4\nMột điểm cuối đã bị đóng. Hệ thống truy vết công khai đã mất một khóa.\nBối cảnh và các giới hạn về nguồn\n\nSteam Các thay đổi đã được triển khai nhằm loại bỏ khả năng hiển thị công khai các mã định danh tài sản (Asset ID) và hạn chế quyền truy cập vào kho hàng của API. Hậu quả là: việc truy vết một mặt hàng cụ thể thông qua mã định danh tài sản ban đầu của nó đã trở nên bất khả thi dựa trên dữ liệu công khai. Phần tiếp theo sẽ trình bày những gì có thể thực hiện được trước đây, những gì không còn khả thi sau đó, và những khó khăn mà nạn nhân phải đối mặt khi cố gắng chứng minh tài sản của họ đã đi đâu. Theo tài khoản kỹ thuật của CSFloat, ngày diễn ra sự việc là 2017; chưa tìm thấy bản ghi thay đổi nào tại Valve. Chuỗi sự kiện này — diễn ra khoảng một năm sau tuyên bố về cờ bạc vào tháng 7 tại 2016 — là câu hỏi điều tra, chứ không phải kết luận. Các bản ghi vật phẩm vẫn còn tồn tại trong hệ thống của Valve; các nhà điều tra bên ngoài đã mất quyền truy cập vào chuỗi ID gốc, trong khi các mã định danh float, seed và paint chỉ cho phép so khớp một phần.\n\nQuy tắc “Valve” được áp dụng: Steam Bộ phận hỗ trợ sẽ không khôi phục các mặt hàng đã bị xóa khỏi tài khoản của bạn, và trách nhiệm chứng minh sự việc đã xảy ra thuộc về bạn. Bản ghi: Tại 2017 Valve, điểm cuối truyền các ID vật phẩm gốc đã bị đóng. Trước đó, bất kỳ ai cũng có thể theo dõi một skin bị đánh cắp từ tài khoản của nạn nhân đến một bot trên thị trường. Sau đó, không ai bên ngoài Valve có thể làm được điều này nữa. Giấy tờ tùy thân mà nạn nhân được yêu cầu xuất trình chính là giấy tờ đã bị tắt đi — và nó vẫn còn tồn tại, bên trong cuốn sách “Valve”.\n\nThời kỳ trước khi mất điện\n\nXét về mặt lịch sử, mọi vật phẩm ảo được tạo ra trên Steam đều sở hữu một mã duy nhất trên toàn cầu và không thể thay đổi Mã tài sản. Các cơ sở dữ liệu của bên thứ ba thuộc mạng lưới Ủy ban Phòng chống Tội phạm (OSINT) có thể lập chỉ mục các ID này. Nếu một người dùng bị đánh cắp tài sản, các nhà điều tra có thể truy vết nguồn gốc của tài sản cụ thể đó khi nó được chuyển từ tài khoản trung gian của kẻ đánh cắp sang các tài khoản lưu trữ của một sàn giao dịch hoặc trang web cá cược.\n\nTRƯỚC ĐÂY: bất kỳ ai cũng có thể theo dõi một khoản tiền từ tài khoản của nạn nhân qua các tài khoản trung gian và đến một sàn giao dịch hoặc bot lưu trữ của sòng bạc, chỉ bằng cách sử dụng dữ liệu công khai.\nSau khi thay đổi\n\nTheo tài khoản kỹ thuật của CSFloat, Valve đã đóng điểm cuối tại 2017 và các ID mục gốc không còn khả dụng đối với các bên bên ngoài. Chưa tìm thấy bất kỳ tuyên bố nào từ Valve về lý do của thay đổi này. Trong cùng khoảng thời gian đó, cũng chưa tìm thấy bất kỳ hành động công khai nào được thực hiện nhằm vào các tài khoản bot thương mại đã di chuyển các mục trên quy mô lớn.\n\nDù lý do là gì đi chăng nữa, sự thay đổi này đã làm đứt đoạn chuỗi lưu giữ công khai. Nạn nhân không còn có thể tái tạo chuỗi ID gốc từ dữ liệu công khai để chứng minh rằng một mặt hàng cụ thể bị đánh cắp đã được thanh lý thông qua một sàn giao dịch hoặc sòng bạc cụ thể. Các bản ghi về mặt hàng đó vẫn tồn tại trong hệ thống củValve; công chúng, các nhà nghiên cứu và cơ quan thực thi pháp luật khi làm việc dựa trên dữ liệu công khai không thể truy cập được chúng.\n\nSAU ĐÓ: Không còn có thể truy vết một vật phẩm cụ thể thông qua ID Tài sản ban đầu của nó từ dữ liệu công khai. Chuỗi lưu giữ ID ban đầu của một vật phẩm đã được di chuyển sau sự kiện “2017” chỉ tồn tại bên trong hạ tầng của Valve; không có hồ sơ nào như vậy được công bố công khai. Các mã định danh Float, seed và paint chỉ cho phép so khớp một phần và mang tính xác suất.\nIEconItems_730\nNHẬN/IEconItems_730/GetPlayerItems/v1/\nTải trọng có thể truy xuất nguồn gốc (Trước khi vá lỗi)\n\"id\": \"14892281934\",\n\"original_id\": \"11829910211\",\nTình trạng: Nạn nhân có thể theo dõi nguồn gốc của vật phẩm qua các tài khoản bot.\nTải trọng được mã hóa (sau khi vá lỗi)\nHiện tại\n\"id\": \"HIDDEN_BY_PRIVACY_SETTINGS\",\n\"original_id\": \"NULL\",\nTình trạng: Các bên thứ ba không còn có thể truy xuất nguồn gốc của mặt hàng dựa trên ID tài sản ban đầu từ dữ liệu công khai.\nẢnh hưởng đến chứng cứ: Sau khi thay đổi, dữ liệu công khai cần thiết để theo dõi một mặt hàng cụ thể thông qua ID tài sản gốc từ tài khoản của nạn nhân vào một sàn giao dịch hoặc bot sòng bạc đã không còn khả dụng. Các bản ghi nội bộ vẫn còn tồn tại tại Valve; một nạn nhân, nhà nghiên cứu hoặc điều tra viên làm việc dựa trên dữ liệu công khai sẽ không thể tái tạo chuỗi ID gốc (các mã định danh float, seed và paint chỉ cho phép khớp một phần).\n\nNguồn: Bài viết trên tài khoản kỹ thuật của CSFloat về việc đóng cửa khu vực 2017 IEconItems_730/GetPlayerItems — blog.csfloat.com/cách-floatdb-theo-dõi-các-mục (đã lưu trữ 2026-09-21) · Các dữ liệu tải (payloads) được hiển thị chỉ là minh họa cho hình dạng của trường, không phải là các phản hồi thực tế · Chưa tìm thấy bản ghi thay đổi (Valve) cho hàm đóng này.\n\nPhần A — Hồ sơ kỹ thuật · Mục5\nMột phiên làm việc. Quyền truy cập rộng hơn so với những gì người dùng nhìn thấy.\nBối cảnh và các giới hạn về nguồn\n\nKiến trúc “API” của Valve, ở trạng thái trước khi có những thay đổi liên quan đến “2023”, đã đi chệch khỏi các tiêu chuẩn cơ bản của ngành (OWASP ASVS, NIST SP 800-63B) và chính là cơ chế được mô tả trong các khiếu nại về hành vi trộm cắp tài sản tự động được lưu giữ trong kho lưu trữ chứng cứ (Các mục 6–8).\n\nQuy tắc “Valve” được áp dụng: Chủ tài khoản đã tạo khóa, đồng ý với các điều khoản và phải chịu tổn thất — đó là câu trả lời trong các trường hợp từ chối đã được lưu trữ. Bản ghi: Cho đến tháng 12 năm 2023, chỉ cần một cookie phiên bị đánh cắp là đã có thể đăng ký khóa đó. Không cần mật khẩu. Không cần tính năng Steam Guard. Không có thông báo nào được gửi đến chủ tài khoản. Người dùng không phải là người tạo ra khóa đó, không thể nhìn thấy nó, nhưng lại được thông báo rằng chính anh ta đã tạo ra nó. Tính năng xác nhận qua điện thoại di động đã được bổ sung trên 2023-12-04 — khoảng bảy năm sau tuyên bố “2016” và khoảng sáu năm sau các diễn đàn lừa đảo mà kho lưu trữ này bảo quản. Những khoản chi phí trong những năm đó không được chi trả bởi Valve. Chúng được chi trả từ các tài khoản đã bị rút cạn trong thời gian đó, trong đó có một phần là tài khoản của trẻ em.\n\nOWASP ASVS 2.8 / NIST SP 800-63BMỨC ĐỘ NGHIÊM TRỌNG: RẤT NGHIÊM TRỌNG\n1. Xác thực tăng cường không đầy đủ\n\nSteam cho phép tạo các khóa xác thực hai yếu tố (API) có đặc quyền cao và thời hạn sử dụng dài chỉ bằng cách sử dụng cookie phiên. Không yêu cầu xác thực hai yếu tố (2) (Steam Guard) hoặc thách thức xác thực nâng cao khi thiết lập hoặc sửa đổi khóa API dành cho nhà phát triển, do đó xác nhận trên thiết bị di động qua Steam Guard — yếu tố thứ hai duy nhất mà Steam cung cấp — không bảo vệ bước này. (Một yếu tố thứ hai dựa trên phần cứng đã được đề xuất trong hệ thống theo dõi của chính Valve tại 2016 và vấn đề này vẫn đang mở: Phụ lục D, GH-01.)\n\nTình trạng: chưa được vá trước phiên bản 2023.. Lỗ hổng này cho phép một tập lệnh chứa cookie bị đánh cắp đăng ký khóa mà không cần bất kỳ tương tác nào từ người dùng.\nOWASP A01:2021 / Quyền truy cập tối thiểuMỨC ĐỘ NGHIÊM TRỌNG: RẤT NGHIÊM TRỌNG\n2. Thiếu nguyên tắc quyền hạn tối thiểu\n\nTrang web Steam API thiếu các phạm vi ủy quyền dựa trên vai trò. Một khóa nhà phát triển API được cấp cho trạng thái danh mục “chỉ đọc” lại sở hữu toàn bộ quyền “ghi” — bao gồm khả năng thao tác các giao dịch hiện có, khởi tạo giao dịch mới, đăng ký webhook và từ chối các giao dịch đang chờ xử lý hợp lệ.\n\nTình trạng: Lỗi thiết kế hệ thống. Chỉ cần một khóa là có thể kiểm soát toàn bộ việc đọc/ghi đối với kho hàng và các giao dịch của tài khoản.\nOWASP A07: Lỗ hổng xác thực phiên (2021) / Phiên làm việcMỨC ĐỘ NGHIÊM TRỌNG: CAO\n3. Lỗi trong quản lý phiên làm việc\n\nNgười dùng đã báo cáo rằng các phiên truy cập web bị chiếm quyền điều khiển có nguồn gốc từ các dải địa chỉ IP của máy chủ lưu trữ vẫn tiếp tục tồn tại. Theo quy trình tiêu chuẩn, các phiên truy cập sẽ bị ngắt khi phát hiện các bất thường về vị trí địa lý hoặc khi thay đổi mật khẩu; tuy nhiên, các báo cáo của người dùng được lưu trữ trong kho dữ liệu cho thấy có những phiên truy cập vẫn duy trì trạng thái hoạt động ngay cả sau khi thay đổi mật khẩu.\n\nTình trạng: Hành vi đã được báo cáo (các khiếu nại của người dùng trong kho lưu trữ). Các phiên làm việc có thể tạo ra các khóa “API” mà không cần xác thực lại.\nViệc chặn ở cấp tên miền là khả thi về mặt kỹ thuậtKHẢ NĂNG THỰC THI\n4. Việc chặn các máy chủ xác thực ở cấp miền là khả thi về mặt kỹ thuật\n\nValve hệ thống này hiện đã vận hành một danh sách tên miền (Link Filter) và đã nhận được mọi tên máy chủ xác thực trong các yêu cầu OpenID của chính nó. Hai cơ chế này không có bất kỳ mối liên hệ nào có thể nhận thấy từ bên ngoài: theo thông tin tại 2026-09-22,, trong cặp 26, tên miền chính đã nằm trong danh sách lọc trong khi máy chủ proxy xử lý quá trình đăng nhập của nó thì không.\n\nViệc kết nối chúng là một công việc kỹ thuật đơn giản: đọc openid.realm lấy tên máy chủ từ mỗi yêu cầu đến, so sánh với một danh sách, và từ chối hoặc đánh dấu yêu cầu đó. Hình minh họa bên phải cho thấy cấu trúc của quy trình này. Việc từ chối máy chủ xác thực — thay vì chỉ từ chối trang đích công khai — sẽ làm gián đoạn bước “Đăng nhập bằng Steam” mà các nền tảng này phụ thuộc vào.\n\nKhông có bằng chứng công khai nào cho thấy Valve thực hiện việc kiểm tra như vậy. Phí tổng hợp khoảng 15% của Steam Community Market chỉ áp dụng cho các giao dịch được thực hiện bên trong nền tảng này; phí này không được thu đối với các giao dịch bên ngoài các nền tảng này.\n\nblock_auth_hosts.pyHÌNH MINH HỌA\n// Đọc các thông tin về máy chủ mà Steam đã nhận được — không quét\ndef on_openid_request(request):\nhost = parse_openid_realm(request)\nnếu máy chủ trong các miền bị chặn:\ntừ chối (yêu cầu)\nLưu ý: Mã giả này chỉ mang tính minh họa. Cả hai phần này đều đã tồn tại tại Valve — tên máy chủ xác thực được gửi kèm trong yêu cầu, còn danh sách tên miền chính là Bộ lọc liên kết. Không có tài liệu công khai nào giải thích lý do tại sao chúng lại không được kết nối với nhau.\nMục 5.1 — Các tiêu chuẩn này không phải là chưa được công bố\nValve hàng ngày đều tuân thủ các quy tắc này. Nhưng ở đây thì nó lại không tuân thủ các quy tắc đó.\n\nSteam có mặt trên App Store và Google Play, thực hiện thanh toán qua các nhà cung cấp dịch vụ xử lý thẻ tín dụng lớn và sử dụng các API của bên thứ ba giống như bất kỳ nền tảng lớn nào khác. Mỗi mối quan hệ này đều đi kèm với các yêu cầu bảo mật đã được công bố và có thời hạn cụ thể mà Valve phải tuân thủ để tiếp tục hoạt động. Hãy so sánh thời hạn của các yêu cầu đó với thời điểm mà trang web API của Steam đã đạt được các biện pháp bảo vệ tương tự. Không có nội dung nào dưới đây là tiêu chuẩn nội bộ, bản ghi nhớ nội bộ hay bí mật kinh doanh: mỗi dòng đều là một tài liệu công khai có ngày công bố.\n\nCác yêu cầu bảo mật bên ngoài đã được công bố, kèm theo ngày công bố, được so sánh với ngày mà trang web Steam (API) áp dụng biện pháp kiểm soát tương ứng\nTiêu chuẩn đã được công bố và ngày có hiệu lực\tTrang web “Steam” API cũng đề cập đến cùng một câu hỏi này\nScoped authorisationOAuth 2.0 — RFC 6749, October 2012. Section 3.3 defines scope so a client receives only the access it asks for. It has been the default of every major platform API since.\tGranular scopes arrived on 16 January 2026.Before that a single Steam Web API key carried full read and write over the account's trades regardless of why it was issued. Thirteen years and three months after the specification that defines the control.\nA key is not an authorisationGoogle's own Cloud documentation: A standard API key doesn't authenticate a principal, and for APIs that create or manage resources, don't use authorization keys in production.\tThe Steam Web API key was exactly that.A bearer string, issued to an account, sufficient on its own to read the inventory, cancel a pending trade and send a new one. No principal was authenticated at the point of use.\nMulti-factor authentication on privileged accessPCI DSS 3.2, requirement 8.3 — mandatory from 1 February 2018 for all non-console administrative and all remote access to the cardholder data environment. Apple then required two-factor authentication of every Developer Program account holder from 27 February 2019: developers with the Account Holder role in a developer program will need to enable two-factor authentication to sign in.\tA second factor was required to create an API key from 4 December 2023.Until then a stolen session cookie was enough, with no prompt on the account holder's phone and no notification afterwards. Four years and nine months after Apple made Valve itself use a second factor merely to sign in to a developer portal.\nCredential lifecycle and revocationTwitch requires of every third-party application: Your app must validate the OAuth token when it starts and on an hourly basis thereafter, and states that it audits for applications that do not. Its legacy v5 API was retired outright on 28 February 2022 on a published schedule.\tNo published key-lifecycle record.The 2023 change protected the creation endpoint. No Valve statement located with it addresses keys already registered, and no changelog accompanied the change at all. Whether keys created before it were invalidated cannot be established from public data — which is the question a data subject would need answered to know whether a key created on their account years earlier is still live.\nTiêu chuẩn kiến trúc // Kiến trúc Token\nGitHub Phạm vi chi tiết so với phạm vi tổng quát (Valve) Steam Trang web API\n\nValve Các nhà phát triển quản lý phần mềm mã nguồn mở trên GitHub hàng ngày bằng cách sử dụng các mã thông báo có mức quyền hạn tối thiểu và chi tiết. Hãy so sánh điều này với khóa thống nhất được cấp cho người chơi tại 130M Steam.\n\nGitHub Token chi tiết\nĐược sử dụng bởi Valve trên GitHub\n\nToken có mức độ chi tiết cao với tính năng cách ly theo phạm vi và việc thực thi bắt buộc chu kỳ sống.\n\nQuyền truy cập kho lưu trữ:Chỉ các kho lưu trữ được chọn (kho lưu trữ 1)\nCấp quyền:Chỉ đọc [✓]\nMã nguồn & Bí mật:Không có quyền truy cập [✕]\nHạn sử dụng:30 Ngày (TTL bắt buộc)\nGhi nhật ký kiểm toán:IP, User-Agent và Dấu thời gian\nTình hình an ninh: Token có đặc quyền tối thiểu giúp hạn chế thiệt hại chỉ trong phạm vi một tài nguyên chỉ đọc.\n!Valve Steam Mã kích hoạt WebAPI\nPhát hành cho người dùng130M\n\nMột chuỗi ký tự chính duy nhất dạng “32-” (chỉ có hoặc không có) quy định toàn bộ quyền giao dịch và quản lý hàng tồn kho.\n\nQuyền truy cập tài khoản:TÀI KHOẢN ĐẦY ĐỦ (Monolithic)\nQuản lý giao dịch:Đọc, Hủy, Từ chối [!]\nPhạm vi chi tiết:KHÔNG CÓ (2026,13đã đến muộn)\nHạn sử dụng:KHÔNG BAO GIỜ (Có hiệu lực vô thời hạn)\nGhi nhật ký kiểm toán:KHÔNG (Người dùng không có lịch sử IP nào)\nLỗ hổng bảo mật: Chìa khóa bị đánh cắp cho phép chặn bí mật tất cả các đề nghị giao dịch đi ra ngoài.\nTiêu chuẩn được áp dụng theo một hướng\n\nGiả sử một nhà cung cấp mà Valve phụ thuộc vào — một nhà cung cấp dịch vụ đám mây, một đơn vị xử lý thanh toán, một CDN — đã để lộ một điểm cuối xác thực mà không có yếu tố xác thực thứ hai, và vài tháng sau, dữ liệu nội bộ của Valve đã bị rò rỉ thông qua một khóa được tạo ra tại điểm cuối đó. Liệu Valve có chấp nhận rằng lỗi thuộc về người đã nhấp vào liên kết đó không? Các quyết định từ chối được lưu trữ trong hồ sơ này trả lời câu hỏi tương tự dành cho người dùng: quan điểm được đưa ra là chủ tài khoản đã tạo ra khóa đó và phải chịu trách nhiệm về tổn thất. Cấu trúc này được mô tả là sự thất bại của nhà cung cấp ở một khía cạnh và trách nhiệm của người dùng ở khía cạnh khác. Điều đó là gì không phải là một câu hỏi mang tính kỹ thuật, và cũng không phải là vấn đề mà cuộc điều tra này có thể giải quyết — đó là điều mà tòa án hoặc cơ quan giám sát sẽ quyết định.\n\nHình minh họa, không phải bằng chứng — tiêu chuẩn được hiểu theo hướng ngược lại\nMột nhà cung cấp dịch vụ thanh toán đã cho phép một tập lệnh của bên thứ ba tạo ra thông tin xác thực giao dịch có toàn quyền truy cập chỉ dựa trên cookie của trình duyệt, mà không có bất kỳ thông báo nào gửi đến chủ tài khoản.\nMột nhà cung cấp dịch vụ xác thực đã bịt lỗ hổng mà qua đó các token của họ được phát hành, nhưng lại không công bố bất kỳ thông tin nào về các token đã được phát hành.\nMột ngân hàng đã giải quyết vụ tranh chấp về giao dịch chuyển khoản bằng cách xác nhận rằng thông tin đăng nhập được sử dụng đã được đăng ký trên chính tài khoản của khách hàng, và đã đóng hồ sơ khiếu nại.\n\nKhông có nội dung nào trong số này được đưa ra như một kết luận về bất kỳ công ty cụ thể nào. Đó là những quyết định thiết kế tương tự, được áp dụng vào một bối cảnh mà phản ứng của cơ quan giám sát đã được ghi chép đầy đủ — và đây chính là sự so sánh mà cơ quan quản lý được yêu cầu thực hiện.\n\nNhững gì hồ sơ đã ghi nhận: Các quy định không có trên trang web Steam API là những quy định công khai, đã lỗi thời và, trong một số trường hợp, là những điều kiện Valve mà doanh nghiệp phải tuân thủ để tiếp tục xuất khẩu sản phẩm của mình. Khoảng thời gian giữa mỗi tiêu chuẩn và sự thay đổi tương ứng Steam có thể đo lường được và đã được nêu rõ ở trên. Điều mà nó không làm rõ là lý do tại sao. Chưa tìm thấy bất kỳ bản giải trình nào của Valve về lý do của bất kỳ khoảng thời gian nào trong số này, và ở đây cũng không đưa ra giả định nào; tài liệu đó hiện đang được lưu trữ tại Valve và chưa được công bố.\n\nCác nguồn, mỗi nguồn là một tài liệu công khai: OAuth 2.0 — RFC 6749, Tháng 10 năm 2012 ↗ · Google Cloud — API Tài liệu về phím ↗ · Yêu cầu PCI DSS về việc xác thực danh tính (3.2) 8.3 — Hướng dẫn tài nguyên của PCI SSC ↗ · Apple — Yêu cầu xác thực hai yếu tố sắp được áp dụng đối với chủ tài khoản, 20 tháng 2 năm 2019 ↗ đã lưu trữ 2025-05-06 ↗ · Twitch — Yêu cầu xác thực mã thông báo ↗ và Thông báo ngừng hoạt động phiên bản v5 ↗ đã lưu trữ 2025-01-27 ↗. Các mốc thời gian của Steam là những mốc được ghi trong bản ghi cập nhật ở phần này; các mục 2023 và 2026 là những bản mà Valve đã phát hành mà không kèm theo bản ghi thay đổi. Truy cập tại 2026-09-22.\n\nBản ghi cập nhật riêng của Valve — đã lỗi thời, lấy từ các nguồn công khai\nNgày\tValve thay đổi\tĐã công bố chưa?\tĐiều gì đã khiến nó đóng cửa\tLag: cơ chế công khai → đã khắc phục\tNguồn\n2026-09-01\tAutomated Suspicious Chat Flagging\tYes\tDangerous links / patterns in group chats\t—\tnews ↗\n2026-01-16\tSteamworks Web API granular scopes\tYes\tLeast-privilege scopes for developer keys\t—\tannouncement ↗\n2025-07-15\tCS2 Trade Protection & reversal window\tYes\tNothing. Not a root-cause security fix. Support-side account recovery access remains untouched. Triggering reversal inflicts an automatic 30-day trade lockout (Skinvault ↗), while cash-trading shock caused a $104M (-25%) 24h market cap plunge (CSMarketCap ↗). In 2026, timers became per-item (Skin.land ↗).\t—\tFAQ ↗\n2025-05-14\tAccount Security Announcement\tYes\tStealer / session-hijack guidance\t—\tannouncement ↗\n2024-10-02\tCS2 'The Armory' 7-day hold\tYes\tHold on trade/market for Armory items\t—\tannouncement ↗\n2024-09-18\tNew-device login trade restriction\tYes\t2–7 day trade lock on new devices\t—\tFAQ ↗\n2024-02-14\tProfile name & avatar change hold\tYes\t2–4 h cooldown on trades after rename\t—\tpost ↗\n2023-12-04\tMobile confirmation for API keys\tNo changelog\tSilent cookie-only key registration\t≈6 years after the 2017-era panels\tdev page ↗\n2023-10-24\tSMS MFA for game build publications\tYes\tSteamworks build publishing\t—\tannouncement ↗\n2023-07-12\tCustom biography content warning\tYes\tPhishing links in bios\t—\tforum ↗\n2023-01-25\tProfile {LINK REMOVED} & cooldown\tYes\tLinks in profile text\t—\tFAQ ↗\n2022-10-24\tLogin overhaul & cookie truncation\tNo changelog\tInfinite stolen sessions\t— (IAuthenticationService token migration)\tnews ↗\n2022-10-12\tMobile App 3.0 QR login\tYes\tSession deauthorisation panel\t—\tnews ↗\n2022-05-10\tTrade-cancellation endpoints removed\tNo changelog\tOffer-swap (cancel & re-send)\t≈5 years after the 2017-era panels\tissue #325 ↗\n2020-05-25\tDota 2 7-day trade lock\tYes\tFast item flipping\t—\tblog ↗\n2018-03-29\tCS:GO 7-day trade lock\tYes\tInstant bot laundering\t≈20 months after the July 2016 statement\tblog ↗ archived 2025-02-26 ↗\nNguồn: các bài đăng trên Valve có liên kết, các trang trợ giúp và các vấn đề trên GitHub, theo ngày tháng ghi trên đó. Ba bản sửa lỗi quan trọng đã được phát hành mà không có bản ghi thay đổi (2022-05, 2022-10, 2023-12) và được người dùng phát hiện, chứ không phải do Valve thông báo — sự bất đối xứng đó là một phần của hồ sơ thực thi. Sự chậm trễ chỉ được tính toán khi chính ngày tháng trong hồ sơ (tháng 7 2016 tuyên bố; 2017-các hội đồng lừa đảo thời kỳ đó) cung cấp điểm khởi đầu; \"—\" có nghĩa là không có điểm khởi đầu nào được xác định tại đây.\nPhần A — Hồ sơ kỹ thuật · Mục6\nTrình mô phỏng khai thác và chiếm quyền điều khiển tương tác\nBối cảnh và các giới hạn về nguồn\n\nMô phỏng lại quy trình từ tin nhắn lừa đảo đến việc đăng ký khóa phía máy chủ và giao dịch hoán đổi. Trước khi có tính năng “2023,”, một khóa Web API được đăng ký trên tài khoản có thể xem danh sách tài sản, hủy một đề nghị giao dịch đang chờ xử lý và tạo một đề nghị mới, đồng thời chủ tài khoản không được hiển thị màn hình xác nhận giao dịch cho bất kỳ hành động nào trong số đó. Điều này thể hiện sự thiếu vắng nguyên tắc “quyền hạn tối thiểu” (OWASP A01:2021). Các mốc thời gian trong mô phỏng này chỉ mang tính minh họa và không phải là số liệu đo lường thực tế của nền tảng hiện tại.\n\nHãy lần lượt xem lại quá trình chiếm quyền điều khiển tài khoản đã được tái hiện. Mỗi giai đoạn sẽ hiển thị những gì chủ tài khoản nhìn thấy và, bên cạnh đó, nội dung tin nhắn mà Steam nhận được vào cùng thời điểm đó. Mỗi cuộc gọi trong số đó đều được xác thực chính xác. Không có bước nào trong quy trình này khiến cho việc xác thực củSteam bị thất bại — điều cần thiết là khóa mà nó cấp ra không được gán phạm vi nào cả (OWASP A01:2021).\n\nNhững gì người chơi nhìn thấy. Những gì đang thay đổi phía sau đó.TRÌNH HƯỚNG DẪN TRONG PHẦN MỀM MÔ PHỎNG\nBước 5 / 5\n\nViệc khai thác đã hoàn tất. Với suy nghĩ rằng mình sẽ nhận được thông báo trên điện thoại di động về giao dịch ban đầu, nạn nhân đã chấp thuận giao dịch thay thế. Đây là một hướng dẫn điều tra pháp y tích hợp, minh họa cách việc thiếu nguyên tắc “Quyền truy cập tối thiểu” (OWASP A01:2021) đã tạo điều kiện cho việc chiếm đoạt tài sản tự động, chỉ trong vòng chưa đầy một giây.\n\n01 / MẪU MỒI TRÒ CHUYỆNMột người bạn nhờ đi bỏ phiếuNạn nhân nhận được một tin nhắn có chứa một liên kết.\n02 / TRANG ĐĂNG NHẬPMột cổng thông tin giống hệtNạn nhân nhập thông tin đăng nhập.\n03 / QUYỀN TRUY CẬPTạo trang web im lặng APIKẻ tấn công đăng ký một khóa nhà phát triển.\n04 / THE SWITCHGiao dịch hợp pháp đã được thực hiệnBot sao chép sẽ tạo bản sao của người nhận mục tiêu.\n05 / XÁC NHẬNHàng giả đã được phê duyệtĐã phê duyệt đề nghị sai trên thiết bị di động.\nCùng một bước, nhìn từ góc độ mạngTái tạo mẫu hình trước khi có hiện tượng “2023” · các hình dạng gọi minh họa\nNạn nhânChấp thuận thông báo trên thiết bị di động vốn được dự kiến cho giao dịch ban đầu.\nKẻ tấn côngNhận các mặt hàng tại tài khoản sao chép.\nSteam thấyMột giao dịch chuyển khoản đã được chủ tài khoản xác nhận trên thiết bị đã đăng ký.\nConfirmation genuine — made by the account holder\nRecipient the clone bot, not the intended counterparty\nThe confirmation is authentic. The offer it confirms is not the one the user initiated.\n\nNhững dấu ấn còn lại: một giao dịch đã được người dùng chấp thuận. Đó chính là thông tin mà bộ phận Hỗ trợ Steam tra cứu khi nhận được khiếu nại, và cũng là lý do khiến các khiếu nại đã được lưu trữ bị đóng với lý do “lỗi của người dùng”. Các khiếu nại này nằm trong kho lưu trữ các biện pháp thi hành.\n\nPhần A — Hồ sơ kỹ thuật · Mục7\nCác điểm cuối nằm phía sau chuỗi.\nBối cảnh và các giới hạn về nguồn\n\nĐây là các điểm cuối (endpoint) của trang web Steam API mà các tập lệnh chiếm quyền điều khiển được báo cáo đã sử dụng để chặn các giao dịch mà không cần qua các bước xác nhận từ phía trình duyệt.\n\nBốn điểm cuối đã được ghi nhận là đủ để hoàn thành toàn bộ công việc. Không có điểm cuối nào là lỗ hổng, cũng không cần phải khai thác — chỉ cần một khóa hợp lệ gọi đến chúng là Steam sẽ phản hồi. Khóa là thứ duy nhất mà kẻ tấn công cần phải đánh cắp.\n\nIEconService / GetTradeOffers / v1THỐNG KÊ Ý KIẾN\n\nĐược sử dụng để theo dõi các đề nghị giao dịch của tài khoản. Các tập lệnh liên tục truy vấn điểm cuối này bằng khóa API đã bị đánh cắp; điểm cuối này trả về thông tin chi tiết về các đề nghị giao dịch mới được tạo, đang chờ xử lý hoặc đã được sửa đổi. Khoảng thời gian giữa các lần truy vấn không được đo lường ở đây.\n\nKênh tấn công: Hiển thị các mã đề nghị giao dịch đang chờ xử lý và thông tin chi tiết về hồ sơ của người nhận.\nIEconService / Hủy đề nghị giao dịch / v1TƯƠNG TÁC\n\nĐược sử dụng để vô hiệu hóa một cách tự động đề nghị giao dịch hợp lệ của người dùng. Trước khi có tính năng “2023”, không có cơ chế xác thực hai yếu tố nào bảo vệ khóa, do đó một máy chủ tự động có thể hủy bỏ đề nghị ngay khi phát hiện ra, mà không cần thông báo cho chủ tài khoản.\n\nKênh tấn công: Hủy giao dịch trước khi chủ tài khoản hoàn tất xác nhận qua điện thoại di động.\nISteamUser / Lấy tóm tắt người chơi / phiên bản 2RECON\n\nThực hiện truy vấn để lấy tên hồ sơ, URL hình ảnh đại diện và cấp độ của người nhận giao dịch hợp lệ. Điều này cho phép tập lệnh điều chỉnh một tài khoản sao chép đã chuẩn bị sẵn sao cho phù hợp. Không đo lường thời gian ở đây.\n\nKênh tấn công: Cung cấp dữ liệu cần thiết để giả mạo danh tính người nhận dự kiến.\n/dev/ajaxregisterkeySỰ TẠO HÓA\n\nĐiểm cuối đăng ký khóa của Steam. Trước đây, bất kỳ phiên cookie trình duyệt nào đang hoạt động (`steamLoginSecure`) đều có thể đăng ký khóa mà không cần xác nhận từ tính năng Bảo vệ Chống Truy cập Bất hợp pháp (Steam Guard) trên thiết bị di động, và cũng không có bất kỳ thông báo nào gửi đến chủ tài khoản.\n\nKênh tấn công: Thông tin đăng nhập cố định được tạo ra bởi một tập lệnh, mà chủ tài khoản không hề hay biết.\nPhần A — Hồ sơ kỹ thuật · Mục 8 · GDPR Bài viết 7\nMột ô đã được đánh dấu. Hành động của ai?\nBối cảnh và các giới hạn về nguồn\n\nTrong bối cảnh mức hoàn trả đang giảm, các phản hồi của bộ phận Hỗ trợ Steam được lưu trữ trong kho lưu trữ đều khẳng định rằng chủ tài khoản đã tạo khóa API và, bằng cách đánh dấu vào ô chọn, đã chấp nhận các điều khoản.\n\nPhản hồi từ bộ phận hỗ trợ cho rằng chìa khóa thuộc về chủ tài khoản. Câu hỏi đặt ra là liệu hồ sơ này có xác định được ai là người thực sự tạo ra nó hay không.\n\nTuy nhiên, trong mô hình đánh cắp khóa “API” đã được ghi nhận, nạn nhân chưa bao giờ nhìn thấy hoặc truy cập vào trang tạo khóa API. Trường đồng ý được gửi đi bởi một tập lệnh thực thi yêu cầu POST không hiển thị giao diện người dùng (headless) bằng cookie phiên đã bị đánh cắp.\n\nTheo Điều 7 và Điều 4 (11) của Quy định Bảo vệ Dữ liệu Chung (GDPR), sự đồng ý phải là sự thể hiện ý chí một cách tự nguyện, cụ thể, có hiểu biết và rõ ràng của chủ thể dữ liệu. Quan điểm của các tác giả là: trường chấp nhận điều khoản được gửi bởi một tập lệnh độc hại sử dụng cookie bị đánh cắp, mà không hiển thị trang web nào cho chủ tài khoản, không thể đáp ứng định nghĩa đó. Việc liệu trường hợp này có đáp ứng định nghĩa hay không là thuộc thẩm quyền của cơ quan giám sát.\n\nPhân tích tải trọng pháp y: Đăng ký khóa\nBÀI ĐĂNG https://steamcommunity.com/dev/ajaxregisterkey\n// Dữ liệu yêu cầu (được chèn vào thông qua tập lệnh chiếm quyền điều khiển)\n{\n\"chấp nhận các điều khoản\": \"đồng ý\", <-- được nhập tự động, không có sự can thiệp của con người\n\"miền\": \"localhost\", ← chưa được xác thực — chấp nhận mọi giá trị, kể cả localhost\n\"sessionid\": \"8f0d8ef763ab2140bf89de2a\"\n}\nCâu hỏi dành cho cơ quan giám sát: trong trường hợp chủ tài khoản chưa bao giờ nhấp vào ô đồng ý, liệu việc chấp nhận các điều khoản được ghi nhận đối với tài khoản đó có đáp ứng yêu cầu tại Điều 7 về việc thể hiện ý chí của chủ thể dữ liệu một cách tự nguyện, cụ thể, có hiểu biết và rõ ràng hay không, và liệu Bộ phận Hỗ trợ của Steam có thể dựa vào đó để từ chối một yêu cầu bồi thường hay không.\n\nNguồn: hình dạng yêu cầu của khóa đăng ký được tái tạo từ điểm cuối công khai và từ các báo cáo về hành vi chiếm quyền điều khiển được lưu giữ trong kho lưu trữ chứng cứ (Phiên bản có thể tìm kiếm của 2026-09-17) · Mã định danh phiên được hiển thị chỉ là một ký hiệu tạm thời, không phải là giá trị đã được ghi lại.\n\nKhám nghiệm tử thi pháp y · Vectơ thay thế thương mại\nCách \"Valve\" cuối cùng đã vô hiệu hóa \"thay thế thương mại\" — Và tại sao \"7\" lại phải mất nhiều năm để tìm cách giải quyết tạm thời\n\nTrong gần một thập kỷ qua, \"Thay thế giao dịch chủ chốt trong 'API'\" (hay \"Chiêu lừa đảo MitM trong 'API'\") đã là mô hình đánh cắp tài khoản sinh lời nhất trên Steam, chiếm đoạt hàng trăm triệu đô la dưới dạng skin từ những người chơi không hay biết. Valve đã không loại bỏ lỗ hổng này bằng cách khắc phục kiến trúc dễ bị tấn công của API; thay vào đó, Valve đã dành bảy năm để xây dựng bốn lớp rào cản giao dịch trên toàn nền tảng, khiến thanh khoản giao dịch trong cộng đồng bị suy giảm nghiêm trọng trong khi nguyên nhân gốc rễ vẫn chưa được giải quyết.\n\n1. Cái Chết của Sự Bắt Chước\nThời gian hồi chiêu của Avatar và Tên (2024 tháng 2)\n\nLỗ hổng này đòi hỏi khả năng bắt chước trong vòng chưa đầy một giây: bot lừa đảo đã chặn một giao dịch đang được gửi đi, sau đó trích xuất hình đại diện và tên của người nhận thông qua ISteamUser, và đã sao chép hồ sơ đó trong 200ms. Vào ngày 14 tháng 2 năm 2024, Valve đã âm thầm áp dụng một quy định bắt buộc 2-Đến4: Thời gian hồi chiêu giao dịch (Lỗi 34) ngay sau khi thay đổi tên tài khoản hoặc ảnh đại diện. Bot sẽ không còn có thể sao chép người nhận ngay lập tức mà không bị khóa khỏi giao dịch.\n\n2. Cái chết kinh tế\n7-Ngày đảo chiều giao dịch CS2 (2025 tháng 7)\n\nValve được đưa ra một cách đơn phương Sự đảo chiều trong giao dịch đối với các vật phẩm trong Counter-Strike. Bất kỳ skin nào được trao đổi đều được gắn nhãn \"Bảo vệ giao dịch\" trong vòng bảy ngày. Nếu nạn nhân phát hiện ra việc thay thế, họ chỉ cần nhấp vào \"Hủy giao dịch\" trong phần Hỗ trợ của Steam, và skin sẽ ngay lập tức được trả lại vào kho đồ của họ đồng thời khóa tài khoản người nhận. Do cơ chế khóa giao dịch trong vòng 7-ngày ngăn chặn kẻ lừa đảo chuyển vật phẩm sang trang web rút tiền, hành vi trộm cắp này trở nên vô lợi.\n\n3. Cái chết của “Chìa khóa im lặng”\nThông báo đẩy bắt buộc trên thiết bị di động dành cho các nhà phát triển ứng dụng (API) (2023 tháng 12)\n\nTrước đây, việc đánh cắp cookie phiên đã cho phép các tập lệnh độc hại thực hiện một yêu cầu POST nền không hiển thị giao diện người dùng tới /dev/ajaxregisterkey mà không thông báo cho nạn nhân. Vào ngày 4 tháng 12 năm 2023, Valve, Google đã yêu cầu phải có xác nhận đẩy rõ ràng trên ứng dụng di động Steam để tạo khóa Web API, qua đó loại bỏ việc cấp phát khóa ngầm trong nền.\n\n4. Cảnh báo trong ứng dụng di động\nBiểu ngữ về thời gian hoạt động và tên tài khoản (2022–2024)\n\nValve đã cải tiến cửa sổ xác nhận trên thiết bị di động để hiển thị thông tin về đối tác giao dịch Steam Thời gian sử dụng tài khoản (ngày tạo), mức độ “Steam” và một cảnh báo màu hổ phách rõ ràng: \"Người dùng này vừa thay đổi tên hồ sơ của mình\", phá vỡ ảo giác thị giác đối với những nạn nhân tinh ý.\n\nBa lỗ hổng trong bản vá củaValve: Tại sao những kẻ lừa đảo chỉ đơn giản là chuyển sang các mục tiêu khác\n1. Kẽ hở về việc loại trừ trò chơi (Dota2và TF2)\n\nCác chiến thuật đảo chiều giao dịch chỉ được áp dụng riêng cho Counter-Strike 2. Các vật phẩm trong Dota 2 và Team Fortress 2 vẫn hoàn toàn không được bảo vệ do sự phức tạp trong quá trình chế tạo và lắp đá. Các vật phẩm cấp cao trị giá hàng nghìn đô la (Móc Móng Rồng, Golden Baby Roshans, Lửa Cháy Bất Thường trong TF2) không có thời hạn hoàn trả. Những kẻ lừa đảo chỉ cần chuyển hướng cơ chế chặn tự động của API sang các trang web giao dịch Dota 2 và TF2, nơi bộ phận hỗ trợ Steam thực thi nghiêm ngặt chính sách “không khôi phục vật phẩm” tại 2016.\n\n2. Kho \"Zombie Key\" (Không hết hạn)\n\nTrong khi Valve đã tích hợp tính năng thông báo đẩy trên thiết bị di động 2FA để tạo ra mới chìa khóa vào tháng 12 2023, Valve không bao giờ thu hồi, hết hạn hoặc xóa các khóa API hiện có từ hệ thống cũ. Hàng triệu tài khoản đang hoạt động đã tạo khóa (hoặc có khóa được tạo ngầm bởi các cuộc tấn công lừa đảo/phần mềm độc hại trước ngày 2023 tháng 12) vẫn còn lưu giữ thông tin đăng nhập hợp lệ với không có thời hạn hết hiệu lực (không có TTL) và không có thời gian chờ do không hoạt động. Các tác nhân đe dọa duy trì các cơ sở dữ liệu lịch sử khổng lồ chứa các khóa cố định này và tiếp tục thực hiện các yêu cầu tra cứu IEconService không bị xáo trộn.\n\n3. Hình phạt dành cho nạn nhân: 30-– Tạm ngừng giao dịch trong ngày\n\nNgay cả trong CS2, tính năng “Valve” vẫn áp dụng hình phạt đối với người chơi bị lừa: việc nhấp vào “Reverse Trade” trong phần Hỗ trợ của Steam sẽ tự động gây ra một Bắt buộc phải thực hiện giao dịch trong ngày theo phương pháp “30-” và lệnh cấm giao dịch trên Thị trường Cộng đồng đối với tài khoản của nạn nhân. Valve áp dụng hình thức cấm sử dụng nền tảng trong một tháng đối với người dùng nhằm răn đe các hành vi hủy giao dịch “vô cớ”, qua đó ngăn chặn các bên bị ảnh hưởng hủy các giao dịch liên quan đến các mặt hàng thanh khoản có giá trị thấp.\n\nVụ bê bối quy định cốt lõi: Bảy năm tìm cách lách luật so với phạm vi “API” duy nhất\n\nTại sao Valve lại dành bảy năm để phát minh ra các cơ chế khóa giao dịch, thời gian chờ tài khoản và khóa giao dịch có thể đảo ngược — gây xáo trộn toàn bộ nền kinh tế trong game và làm sụt giảm $104M vốn hóa thị trường — thay vì áp dụng giải pháp tiêu chuẩn của ngành?\n\nNhư đã được chứng minh qua bản phát hành chính thức trên Steamworks của tựa game “Valve” tại 16 vào ngày 2026 (Thông báo) #493839547938902179 ↗), Valve đã được xây dựng sẵn Các nhóm quyền truy cập chi tiết (Chung, Giao dịch nhỏ, Kinh tế, Dữ liệu bán hàng) và Danh sách trắng IP đối với các khóa nhà xuất bản dành cho doanh nghiệp. Valve đã có sẵn giải pháp kỹ thuật này từ nhiều năm nay. Chỉ cần một ô chọn dành cho người dùng—\"Ngăn chặn khóa Web API này truy cập vào IEconService (Quản lý giao dịch)\" hoặc một danh sách trắng địa chỉ IP gia đình — lẽ ra đã có thể loại bỏ hoàn toàn vụ lừa đảo thay thế giao dịch trong 2018 mà không gây ra bất kỳ thiệt hại kinh tế phụ nào. Valve đã từ chối cung cấp cho người chơi thông thường sự bảo vệ mà họ đã thiết kế dành riêng cho các đối tác doanh nghiệp.\n\nPhần B — Các quy định và hồ sơ thực thi · Mục 9\nBộ quy tắc của họ. Các nền tảng đã được ghi lại.\nBối cảnh và các giới hạn về nguồn\n\nSổ cái này ánh xạ các điều khoản cụ thể từ Steam Thỏa thuận người đăng ký (SSA) và Steam Hành vi trực tuyến (SOC) các hướng dẫn nhắm trực tiếp vào các thực thể thương mại đang hoạt động và có quy mô lớn.\n\nQuy tắc: không sử dụng cho mục đích thương mại, không cá cược, không sử dụng bot — và bộ phận Hỗ trợ của Steam thường viện dẫn các điều khoản này khi từ chối trả lại đồ đạc cho nạn nhân. Bản ghi: Nhìn bề ngoài, các điều khoản này áp dụng cho các nền tảng thương mại trong danh mục này, vốn hoạt động dựa trên các tài khoản Steam, các bot Steam và các giao dịch chuyển tiền Steam. Điều khoản này được áp dụng đối với người đã làm mất số da đó, chứ không phải – theo bất kỳ hồ sơ công khai nào – đối với các doanh nghiệp vận chuyển số da đó.\n\nTrong các khiếu nại đã được lưu trữ, bộ phận hỗ trợ của Steam đã trích dẫn \"Không được sử dụng cho mục đích thương mại\" và \"Không sử dụng tự động hóa/bot\" các điều khoản khi từ chối hoàn trả tài sản cho nạn nhân của hành vi lừa đảo liên quan đến khóa API. Các điều khoản này, về mặt nguyên tắc, cũng áp dụng cho các nền tảng thương mại được ghi nhận trong hồ sơ này, vốn xác thực thông qua Steam OpenID và chuyển giao tài sản qua các tài khoản tự động Steam. Không có ước tính về doanh thu trên toàn thị trường được đưa ra tại đây (xem thống kê thực thi dưới đây). Hồ sơ chỉ cho thấy quy tắc được áp dụng đối với các tài khoản cá nhân trong các vụ việc đã lưu trữ và không có hồ sơ thực thi được công bố theo từng nhà điều hành đối với các nền tảng. Sự bất đối xứng đó chính là nội dung được ghi chép trong phần này.\n\nCâu hỏi trọng tâm / việc thi hành pháp luật có chọn lọcQuy tắc → Quy mô → Trách nhiệm giải trình\nMột bộ quy tắc. Việc thi hành không công bằng.\n\nSổ đăng ký cho thấy các dịch vụ thương mại sử dụng danh tính, kho dữ liệu, bot và các giao dịch chuyển nhượng trên Steam làm cơ sở hạ tầng hoạt động. SSA cấm khai thác thương mại và tự động hóa mà không có sự cho phép. Các khiếu nại đã được lưu trữ cho thấy quy định này được áp dụng đối với các tài khoản cá nhân, trong khi hồ sơ công khai không thể hiện một bản ghi tương ứng theo từng nhà điều hành cho các nền tảng được ghi nhận tại đây. Hãy công bố quy định, bằng chứng và quyết định xử lý đối với từng trường hợp.\n\n189các trang web nằm trong phạm vi kiểm toán\n44Các tuyến đường thuộc miền riêng biệt trong danh sách trực tuyến — 27 kèm theo tệp bằng chứng đã được công bố, 17 được thu thập thủ công. Chỉ riêng cuộc kiểm tra trình duyệt trên trang web 189-đã khắc phục được 25 trong số đó; danh sách này bổ sung thêm các tuyến đường được thu thập thủ công.\n12 Năm 6 thángcsgogem.com bị chặn trong Bộ lọc liên kết; api.csgem.com đã đăng ký tại 2014-03-08 và chưa từng bị chặn — một trong những cặp như 26 tính đến thời điểm 2026-09-22\nKhông có tổng số đã được xác minhkhông bao gồm ước tính doanh thu trên toàn thị trường\nSteam Hành vi trực tuyến\n\"…you shall not do, or attempt to do, any of the following on Steam: […] Engage in commercial activity. Examples of such prohibited behavior include: posting advertisements; running contests; gambling; buying or selling Steam accounts; selling content, gift cards, or other items; and begging.\"\n\nstore.steampowered.com/hành vi_trực_tuyến ↗ đã lưu trữ 2026-09-21 ↗\n\nĐiều 2.G của Luật An sinh Xã hội (SSA) — Mục đích thương mại\n\"…[you may not] exploit the Content and Services or any of its parts for any commercial purpose, except as expressly permitted elsewhere in this Agreement…\"\n\nNhư đã đưa tin, các thông báo trên trang 2016 của Valve đã viện dẫn giấy phép sử dụng cá nhân, phi thương mại. Chưa có nhà khai thác nào công khai xuất trình giấy phép theo Điều Valve. store.steampowered.com/thỏa_thuận_người_đăng_ký ↗ đã lưu trữ 2026-09-18 ↗\n\nSteam Điều khoản sử dụng trang web API\n\"You may not use the Steam Web API or Steam Data in any way that violates the Steam Subscriber Agreement.\"\n\nCác nền tảng giao dịch giao diện của bên thứ ba hoạt động thông qua các tài khoản tự động truy cập vào địa chỉ Steam API. Nội dung quy định không có ngoại lệ nào đối với hoạt động quy mô thương mại. steamcommunity.com/dev/apiterms ↗ đã lưu trữ 2026-09-21 ↗\n\nĐiều 4.C của Bộ luật An sinh Xã hội (SSA)\nTự động hóa\n\nCác tập lệnh, bot và các hình thức tương tác không phải do con người thực hiện đều bị hạn chế. Sổ cái ghi lại các giao dịch bằng bot, các mạng lưới tài khoản ảo và việc định tuyến tự động ở quy mô thương mại.\n\nKiểm tra 153các hồ sơ được gắn thẻ theo điều khoản này ↗\nNội dung được ghi nhận theo điều khoản này là gì153 các nền tảng được gắn thẻ\nMở hồ sơ15\nSkin Casino13\nThị trường CS29\nRoulette da8\ncsgoempire.com→csgoempirelogin4.comSòng bạc\nrollbit.com→rbsnin.comSòng bạc tiền điện tử\n500.casino→fivezerozero.coSòng bạc được cấp phép\n\nTrong số đó, 153 cũng được gắn thẻ theo Điều 2.G của Đạo luật An sinh Xã hội (SSA) và 2 cũng được gắn thẻ theo Điều 1.C của SSA — các dịch vụ này thuộc phạm vi áp dụng của nhiều điều khoản, đó là lý do tại sao các ví dụ được lặp lại.\n\n28 của 153 đã được ghi nhận đang xác thực thông qua một tên miền riêng có thể đăng ký. Một thẻ ghi lại một lần quan sát có ghi ngày tháng, khiến nền tảng này rõ ràng thuộc phạm vi điều khoản; đây không phải là một vi phạm đã được xét xử, và chưa có giấy phép nào từ Valve được xuất trình cho bất kỳ trường hợp nào trong số đó.\n\nĐiều 2.G của Bộ luật An sinh Xã hội (SSA)\nSử dụng cho mục đích thương mại\n\nViệc khai thác thương mại phải có sự cho phép rõ ràng. Hãy so sánh các mô hình kinh doanh đã được ghi nhận, quy mô của chúng cũng như bất kỳ thông tin nào đã được công bố liên quan đến việc cấp phép hoặc thực thi.\n\nKiểm tra 175các hồ sơ được gắn thẻ theo điều khoản này ↗\nNội dung được ghi nhận theo điều khoản này là gì175 các nền tảng được gắn thẻ\nMở hồ sơ15\nSkin Casino13\nThị trường CS29\nRoulette da8\ncsgoempire.com→csgoempirelogin4.comSòng bạc\nrollbit.com→rbsnin.comSòng bạc tiền điện tử\n500.casino→fivezerozero.coSòng bạc được cấp phép\n\nTrong số đó, 153 cũng được gắn thẻ theo Điều 4.C của Đạo luật An sinh Xã hội (SSA) và 24 cũng được gắn thẻ theo Điều 1.C của SSA — các dịch vụ này thuộc phạm vi áp dụng của nhiều điều khoản, đó là lý do tại sao các ví dụ được lặp lại.\n\n28 của 175 đã được ghi nhận đang xác thực thông qua một tên miền riêng có thể đăng ký. Một thẻ ghi lại một quan sát có ghi ngày tháng, khiến nền tảng này rõ ràng thuộc phạm vi điều khoản; đây không phải là một vi phạm đã được xét xử, và chưa có giấy phép nào từ Valve được xuất trình cho bất kỳ trường hợp nào trong số đó.\n\nĐiều 3.A của Bộ luật An sinh Xã hội (SSA)\nVPN và ẩn vị trí\n\nViệc che giấu địa chỉ IP thông qua máy chủ proxy có thể dẫn đến việc chấm dứt dịch vụ. Các máy chủ xác thực thuộc các miền riêng biệt cần được phân tích riêng biệt: xác định rõ đối tượng nào đang bị che giấu và quy tắc nào được áp dụng.\n\nKiểm tra bằng chứng máy chủ xác thực ↗\nSteam Trợ giúp / Chính sách về URL\nChe giấu liên kết\n\nSteam cấm sử dụng các công cụ rút gọn liên kết và các công cụ làm mờ đích đến của liên kết. Một miền xác thực riêng biệt — rbsnin.com trong quy trình đăng nhập của Rollbit, auth.dota.trade trong CS.MONEY — đặt ra câu hỏi tương tự là liệu địa chỉ đích được hiển thị cho trình xác thực OpenID của Steam có xác định được trang web đang hoạt động hay không.\n\nChính sách URL của Valve ↗\n\nTham chiếu quy tắc: Steam Thỏa thuận người đăng ký, bản sửa đổi 10 tháng 9 năm 2026 đã lưu trữ 2026-09-18 ↗ · Steam Điều khoản sử dụng trang web API đã lưu trữ 2026-09-21 ↗ · Steam Chính sách URL (che giấu liên kết). Các con số này phản ánh số lượng hồ sơ và thẻ trong tập hồ sơ này; chúng không phải là số lượng các vi phạm đã được xử lý.\n\nSự thiếu tin tưởng\nKhi bộ phận hỗ trợ đóng hồ sơ, ai sẽ xem xét lại quyết định đó?\n\nCác khiếu nại được lưu giữ mô tả các biện pháp trừng phạt vĩnh viễn, các khiếu nại không được giải quyết và việc từ chối trả lại các vật phẩm bị đánh cắp. Hãy đối chiếu các báo cáo đó với lịch sử vé thực tế, các biện pháp khắc phục hiện có và nhật ký truy cập tài khoản. Một lời giải thích chung chung về lừa đảo qua email không thể xác định được ai là người đã thực hiện việc đặt lại mật khẩu hoặc tạo khóa API.\n\nĐọc các khiếu nại đã được ghi nhận ↗Yêu cầu các hồ sơ liên quan →Biểu đồ mối quan hệ của người điều hành →\nPhần B — Các quy định và hồ sơ thực thi · Mục 10\nMột quy tắc tự động hóa API. Một quy tắc cấm tự động hóa.\nBối cảnh và các giới hạn về nguồn\n\nCâu hỏi mà phần này đặt ra là làm thế nào để dung hòa hai vấn đề này: những hình thức sử dụng nào của “API” được phép, do ai cho phép, và dựa trên những tiêu chí công bố nào. Ở đây không có ước tính nào về số lượng người dùng thương mại được phép của “API”, và việc thiếu danh sách công bố cũng không ngụ ý con số nào — chính sự vắng mặt đó mới là kết luận, chứ không phải con số ẩn sau nó. Các tin nhắn hỗ trợ từ Steam được trích dẫn ở trên đã được dự án ArchiSteamFarm sao chép lại trong phần Câu hỏi thường gặp (FAQ) của riêng mình (đã được xác minh nguyên văn tại 2026-09-22); đây không phải là các ấn phẩm của Valve, và các tài khoản mà các tin nhắn này được gửi đến cũng không được xác định.\n\nQuy định (Điều 4.C của SSA): Không sử dụng tập lệnh, bot hay các hệ thống không do con người điều khiển trên Steam. Bản ghi: Valve cung cấp một dịch vụ REST không giao diện người dùng (API) với mục đích duy nhất là tự động hóa giữa các máy chủ, và trao quyền truy cập cho bất kỳ tài khoản nào. Người dùng sẽ bị cấm nếu sử dụng các công cụ tự động hóa; giao diện tự động hóa là sản phẩm riêng của Valve. Danh sách các mục đích thương mại nào được phép sử dụng vẫn chưa bao giờ được công bố.\n\nLầm tưởng về “nhà phát triển trò chơi”\nSteamworks SDK (Phiên bản chính thức)\n\nĐược các studio game chính thống sử dụng để tích hợp các thành tích, tính năng ghép trận và bảng xếp hạng vào ứng dụng khách game của họ. Yêu cầu quá trình tích hợp phức tạp bằng C++ và thủ tục đăng ký đối tác chính thức.\n\nSteam Trang web API (The Loophole)\n\nMột kiến trúc JSON/REST không có phần đầu (headless) được thiết kế dành cho các máy chủ web bên ngoài. Trong mô hình “hijack” được ghi chép tại đây, kiến trúc này được sử dụng để đọc danh sách hàng tồn kho và thao tác các giao dịch ngang hàng từ các máy chủ từ xa; các mục đích sử dụng hợp pháp của nó không được liệt kê trong tài liệu này.\n\nChìa khóa này dành cho ai?Một người dùng thông thường của Steam không cần đến khóa Web API ngay trong ứng dụng; trang khóa này nằm dưới một URL dành cho nhà phát triển và mục đích được ghi rõ của nó là để truy cập từ bên ngoài, ở phía máy chủ. Các khiếu nại về việc chiếm quyền điều khiển đã được lưu trữ mô tả những nạn nhân không biết đến sự tồn tại của trang này cho đến khi một khóa đã được đăng ký trên tài khoản của họ.\nMâu thuẫn trong tự động hóa\n\nĐiều 4.C của Luật An sinh Xã hội (SSA) quy định như sau: \"Bạn không được sử dụng bất kỳ hình thức kịch bản, bot, macro hoặc các hệ thống khác không do con người điều khiển ('Tự động hóa') để tương tác với Nội dung và Dịch vụ trên Steam dưới bất kỳ hình thức nào.\" Tuy nhiên, các điểm cuối Web API (như CancelTradeOffer) không yêu cầu giao diện người dùng (UI) và không cần mã xác thực (captcha), đồng thời hoàn toàn bỏ qua client của Giao thức Mã hóa Tương tác (Steam). Giao thức Giao tiếp Nguồn mở (API) được thiết kế để tự động hóa giữa các máy chủ; quy tắc này cấm người dùng thực hiện tự động hóa; ranh giới giữa hai trường hợp này không được công bố.\n\nVị trí phía máy chủ trong quy trình giao dịch\n\nKhóa Web API cho phép một máy chủ của bên thứ ba thực hiện các giao dịch của tài khoản mà không cần đến ứng dụng khách Steam. Trong mô hình “chiếm quyền điều khiển”, máy chủ đó nằm giữa chủ tài khoản và máy chủ giao dịch.\n\n→Không có màn hình xác nhận giao dịch nào được hiển thị cho các thao tác của khóa.\n→Cho phép thực hiện truy vấn nền (GetTradeOffers).\n→Hủy và phát hành lại các ưu đãi mà không cần sự tương tác của người dùng.\nValve đã xây dựng giao diện này, cấm người dùng sử dụng các công cụ tự động hóa trong các quy tắc của mình và chưa công bố bất kỳ tiêu chí nào về những hình thức sử dụng thương mại nào được phép.\nPhần B — Các quy định và hồ sơ thực thi · Mục 11\nMười ngày được yêu cầu. Mười năm để giải trình.\nBối cảnh và các giới hạn về nguồn\n\nVào ngày 20 tháng 7 năm 2016, cố vấn pháp lý của Valve đã đặt ra thời hạn 10-ngày cho các nhà điều hành cờ bạc. Mười năm sau (tính đến thời điểm chụp ảnh hồ sơ, 2026-09-21), ít nhất một nền tảng được nêu tên trong các báo cáo báo chí về thông báo đó, CSGOFast, vẫn đang hoạt động với một máy chủ xác thực trên tên miền riêng. Nội dung văn bản được tái tạo dưới đây dựa trên các báo cáo báo chí tại 21 tháng 7 năm 2016; bản tái tạo này không phải là bản quét. Hồ sơ thi hành mà thông báo này đề cập đến vẫn chưa được công bố. Thư ngỏ gửi đến Ủy ban là Phần 2.\n\nHãy đọc thông báo “2016” tháng 7 được đăng bên cạnh các quan sát sau đây. Yêu cầu còn tồn đọng là hồ sơ thực thi đối với từng nhà khai thác.\n\nMột tuần trước đó — 13 tháng 7 năm 2016, trước công chúng\n\nVào ngày 13 Tháng 7 năm 2016 đã lưu trữ 2026-09-21 ↗, Valve đã mô tả cách các trang web cờ bạc sử dụng Steam: OpenID để xác thực tài khoản và tạo tài khoản tự động cho hoạt động giao dịch. Valve khẳng định rằng việc sử dụng các cơ chế này để vận hành hoạt động kinh doanh cờ bạc đã vi phạm API và các thỏa thuận người dùng của họ. Cả phần mô tả cơ chế lẫn quy định cấm đều có trong tuyên bố có ghi ngày tháng của chính “Valve”. Trên trang 2026-09-21, các máy chủ xác thực trên miền riêng biệt được kiểm tra không báo cáo bất kỳ trường hợp chặn nào từ bộ lọc liên kết (Link Filter), và trang Valve cũng chưa công bố bất kỳ bản ghi thực thi nào theo từng nhà mạng.\n\nPHỤ LỤC A / THÁNG 7 NĂM 2016TÁI TẠO BỘ CHỮ\nCÔNG TY VALVE\n\nBellevue, bang Washington\n\nNGÀY:Tháng 7 năm 2016 (theo báo chí 21 Tháng 7 năm 2016)\nTỪ:Karl Quackenbush, Tổng cố vấn pháp lý\nTrả lời:Yêu cầu ngừng và chấm dứt — việc sử dụng tài khoản Steam vào mục đích thương mại\nLƯU Ý:Bản tái tạo từ văn bản được báo cáo; không phải bản quét\n\n\"Chúng tôi được biết rằng quý vị đang vận hành một trong những trang web cờ bạc được liệt kê dưới đây. Quý vị đang sử dụng các tài khoản Steam để tiến hành hoạt động kinh doanh này. Theo Thỏa thuận người đăng ký của Steam, các dịch vụ Steam và Steam chỉ được cấp phép cho mục đích sử dụng cá nhân, phi thương mại.\"\n\n\"Quý vị cần ngay lập tức ngừng và chấm dứt việc tiếp tục sử dụng các tài khoản Steam của mình cho bất kỳ mục đích thương mại nào. Nếu quý vị không tuân thủ yêu cầu này, trong vòng mười (10) ngày, Valve sẽ áp dụng mọi biện pháp khắc phục có thể, bao gồm nhưng không giới hạn ở việc chấm dứt các tài khoản của bạn.\"\n\nTái lập hồ sơ · tham khảo hồ sơ gốc\nKarl Quackenbush\nGiám đốc Pháp chế, Công tyValve\nGHI CHÚ BÊN LỀ / BÀI XUẤT BẢN\nMười ngày.Vậy thì sao?\n\nThời hạn đã được quy định rõ ràng. Việc thực hiện của công chúng cũng cần phải như vậy.\n\nQuan điểm đã được công bố của Valve về “2016” ↗\nLưu ý về thời hạn +\nTRUYỆN CHÂM BIẾM / KHÔNG PHẢI LÀ THƯ TƯƠNG TÁC CỦA VALVE\n\nThưa hạn chót,\n\nBạn được cho mười ngày. Không hiểu sao, lịch lại là thứ duy nhất vẫn hoạt động bình thường.\n\nXin vui lòng chuyển tiếp bất kỳ phản hồi nào vào hồ sơ công khai.\n\nDòng thời gianTháng 7 năm 2016 – Tháng 9 năm 2026\nHạn chót trong thông báo:\n10 Ngày\nTháng 7 năm 2016\nThời gian đã trôi qua kể từ khi có thông báo:\n3,715 Ngày\nSố liệu đã được điều chỉnh từ 20 (ngày 2016 tháng 7) sang bản chụp nhanh hồ sơ tại 21 (ngày 2026, tháng 9) – đây không phải là số liệu thời gian thực\nHồ sơ thi hành đã được công bố:\nKhông có\nKhông tìm thấy thông tin chi tiết về các trường hợp ngắt kết nối hoặc chặn theo từng nhà mạng\n\n◀ Ngày thứ0–10 — thời hạn, để mở rộng quy môNgày thứ 3715 — ảnh chụp nhanh ▶\n\n20 2016 tháng 7Đã ban hành lệnh bắt giữ có thời hạn 10 ngàyNgày thứ 0\n17 2024 tháng 2Các nghĩa vụ theo DSA được áp dụngNgày thứ 2,768\n25 2026 tháng 2Công bố đơn khiếu nại của Tổng chưởng lý bang New YorkNgày thứ3,507\n21 2026 tháng 9Tổng quan về hồ sơNgày thứ 3715\n\nMười năm sau, CSGOFast — được đề cập trong các báo cáo truyền thông về các thông báo của Nhóm Công tác về Bảo mật Mạng (2016) — hiện đang hoạt động: csgofast.com đã trả về thông báo chặn từ Bộ lọc Liên kết (Link Filter) đối với 2026-09-19 và 2026-09-21,, trong khi máy chủ xác thực của nó steam-login.authtofast.com (đã đăng ký 2026-06-30) thì không.\n\nBản ghi đầy đủ và có ghi ngày tháng về các thay đổi bảo mật của Valve: Dòng thời gian về an ninh → · Hồ sơ của Washington và tiêu chuẩn thi hành: dưới đây\n\nTheo hồ sơ ghi nhận: Thông báo của Nhóm Công tác về Tên miền (2016) đã đặt thời hạn là ngày 10-; Valve đã vận hành một danh sách tên miền (Link Filter) và nhận được các tên máy chủ xác thực trong các yêu cầu OpenID của riêng mình; chưa có bản ghi thực thi nào dành riêng cho từng nhà điều hành được công bố. Các báo cáo từ cộng đồng mô tả một hành động 2018 nhằm vào một nền tảng thương mại điện tử (SkinJar), nhưng những báo cáo này chưa được xác minh và không được sử dụng làm cơ sở trong bài viết này.\nCSGOFAST / LỐI XÁC THỰC Đà LƯU\nHãy tuân theo máy chủ trả về đã được chỉ định.\n\nCác liên kết bản ghi lộ trình đã lưu csgofast.com đến steam-login.authtofast.com. Tên máy chủ riêng biệt này được truyền trong yêu cầu OpenID của Steam. Điều này cung cấp cho các nhà điều tra một địa chỉ cụ thể để đối chiếu với các bản ghi về việc lọc và thực thi của Valve.\n\nKiểm tra lộ trình CSGOFast và nguồn gốc của nó ↗ · So sánh kết quả của bộ lọc liên kết đã lưu trên Steam ↗\n\nHỒ SƠ CÔNG KHAI / WASHINGTON · 2016 → 2026\nHai thời hạn. Một tiêu chuẩn thi hành vẫn chưa được làm rõ.\n20 THÁNG 7\nValve cung cấp cho các trang web cá cược 10 ngày\n\nYêu cầu từ phía luật sư của công ty này đã cảnh báo rằng việc tiếp tục sử dụng các tài khoản Steam vào mục đích thương mại có thể dẫn đến việc chấm dứt tài khoản.\n\n27 SEP\nWashington gây áp lực lên Valve\n\nỦy ban Cờ bạc của bang đã yêu cầu cung cấp bằng chứng về các biện pháp nhằm ngăn chặn việc chuyển nhượng “skin” để đánh bạc và đặt hạn chót trả lời vào ngày 14 tháng 10.\n\n17 OCT\nValve bác bỏ cáo buộc\n\nValve đã trả lời sau thời hạn quy định, bác bỏ cáo buộc rằng họ tạo điều kiện cho hoạt động cờ bạc, cho biết đã vô hiệu hóa các tài khoản liên quan và khẳng định không muốn ngừng hoạt động giao dịch cũng như dịch vụ OpenID đối với tất cả người dùng. Ít nhất một nền tảng được nêu tên trong các báo cáo truyền thông về các thông báo tháng 7 (CSGOFast) vẫn đang hoạt động một thập kỷ sau đó. Cả hai sự kiện này chỉ có thể đúng nếu nhà điều hành đã thay thế các tài khoản bị vô hiệu hóa; hồ sơ chứng minh điều này vẫn chưa được công bố. WSGC nên yêu cầu Valve làm rõ mâu thuẫn giữa hai thông tin này.\n\n2026\nCác tuyến đường được ghi nhận vào tháng 9 năm 2026\n\nSổ đăng ký tuyến đường ghi lại các nền tảng 44 xác thực thông qua các máy chủ xác thực thuộc các miền riêng biệt, bao gồm CSGOFast, bằng cách sử dụng OpenID và các cơ chế giao dịch Valve được mô tả tại 2016.. Bản ghi thực thi nhằm chỉ ra những nhà khai thác nào đã bị ngắt kết nối vẫn chưa được lập.\n\nBẢN TÓM TẮT CỦA ỦY BAN · 30 THÁNG 1 NĂM 2018\nMười tám tháng sau khi Công ty Dịch vụ Bưu chính và Viễn thông (Valve) gửi phản hồi, cơ quan quản lý vẫn coi đó là một ý định.\n\nTrong buổi làm việc với cơ quan lập pháp của bang tại phiên điều trần công khai về Dự luật HB 2881, Ủy ban đã tóm tắt tuyên bố ngày 7 tháng 2016 theo cách diễn đạt của riêng mình: Valve \"đã tuyên bố ý định siết chặt việc sử dụng nền tảng của mình để tạo điều kiện cho hoạt động cá cược bằng skin.\" Trang này cũng ghi lại tác động của thông báo đó đối với dự báo của ngành — \"do đó,\" Dự báo về thị trường cá cược trực tuyến tại 2020 đã được điều chỉnh từ 19.7 tỷ đô la đến 670 triệu đô la, mức giảm khoảng 97 phần trăm, chỉ dựa trên thông báo này. Dự báo đã thay đổi. Báo cáo về việc thực thi quy định đối với từng nhà khai thác – vốn là cơ sở để biện minh cho việc này – vẫn chưa được công bố.\n\nCác số liệu thị trường này là ước tính của Narus Advisors / Eilers & Krejcik Gaming được trích dẫn trong bản tóm tắt của Ủy ban, chứ không phải là kết luận của Ủy ban; cùng tài liệu này ước tính quy mô cá cược bằng skin trong trò chơi “2016” vào khoảng $5 tỷ, trong đó khoảng $3 tỷ diễn ra trên các trang web theo mô hình sòng bạc. Nguồn: 2026-09-22, SHA-256 c507c9025f93da0aadaf395c4d8882f25973211c318ee8e9b6f18a5b3755e050.\n\nCó thể so sánh quan điểm công khai của Valve về “2016” với cơ sở hạ tầng hiện có ngày nay. Câu hỏi đặt ra là liệu các biện pháp thực thi có tác động đến các tài khoản và tuyến đường được sử dụng bởi các nhà khai thác bị cấm hay không. Việc thông báo trước mười ngày không phải là bằng chứng cho thấy thông báo đó đã được thực hiện đối với tất cả các nhà khai thác được nêu tên trong đó. Hành động của OPSkins liên quan đến “2018” là biện pháp can thiệp duy nhất được ghi nhận nhằm vào một người điều hành cụ thể; xét trên bối cảnh các nền tảng 189 đã được kiểm tra và không có hồ sơ công khai nào theo từng người điều hành, một hành động được ghi nhận như vậy không đủ để cho thấy một xu hướng thực thi nhất quán.\n\nThông báo “2016” của Ủy ban Cờ bạc Washington ↗ đã lưu trữ 2026-05-20 ↗ · Phản hồi của Valve về bài viết “17” trên tạp chí “2016” tháng 10 (bản sao tài liệu) ↗ · Buổi báo cáo của WSGC trước cơ quan lập pháp, “30” tháng 1 năm 2018 (bản sao lưu trữ, 4 trang) ↗ · tệp tương tự trên wsgc.wa.gov ↗ · bản ghi truy xuất & hàm băm ↗ · Chương trình khuyến mãi OPSkins “2018” của Valve ↗ đã lưu trữ 2026-03-07 ↗ · Kiểm tra lộ trình hiện tại ↗\n\nKiểm toán pháp y theo chiều dọc · Các đối tượng bị yêu cầu ngừng và chấm dứt hoạt động trên trang web 2016\nThập kỷ “10--Day Notice”: Kiểm toán khả năng tồn tại về mặt pháp y đối với các địa điểm được nêu tên trong “23”\n\nVào ngày 19–20 tháng 7 năm 2016, Valve, Tổng cố vấn pháp lý Karl Quackenbush đã ban hành các thông báo chính thức yêu cầu ngừng và chấm dứt hoạt động đối với các nền tảng cờ bạc bằng skin trên 23, yêu cầu các nền tảng này ngừng sử dụng thương mại các tài khoản Steam trong phạm vi 10 ngày dưới nguy cơ bị đóng tài khoản và bị khởi kiện. Hơn 3,700 ngày sau đó, một cuộc kiểm toán thực nghiệm đã vạch trần mô hình thực thi thực sự: nhiều nhà khai thác chưa bao giờ ngừng hoạt động, một số khác vẫn tiếp tục hoạt động tới sáu năm sau thời hạn, và hệ sinh thái trị giá hàng tỷ đô la này vẫn tiếp tục tận dụng kiến trúc OpenID củValve.\n\n5+ TRỰC TIẾP\nHoạt động ổn định trên các nền tảng như 2026 (CSGOBig, CSGO500, CSGOFast, v.v.)\n6 NĂM\nThời gian hoạt động dài nhất sau khi nhận thông báo trước khi đóng cửa (CSGOatse hoạt động qua địa chỉ 2022)\n$5.01B\n2016 khối lượng giao dịch theo giá trị (Narus / Eilers & Krejcik)\n200+\nCác trang web cá cược trực tuyến đang hoạt động sôi nổi trong giai đoạn thị trường đạt đỉnh\nThe Surviving Titans · Kế hoạch tài chính và tăng lưu lượng truy cập “2024–2026”\nTừ các cảnh báo về “10-” đến các tập đoàn đa quốc gia: Doanh thu hàng tỷ đô la\n\nThay vì loại bỏ hoạt động cá cược bằng skin, các thông báo trên 2016 của Valve đã thúc đẩy một cuộc cách mạng trong ngành. Các nhà điều hành còn tồn tại đã tái cơ cấu thành các pháp nhân nước ngoài (Curaçao, Belize, Síp), tiên phong trong giao dịch ngang hàng (P2P) để vượt qua các lệnh cấm bot, và hiện đang xử lý hơn 10 hàng triệu lượt truy cập trang web mỗi tháng và hàng tỷ đô la doanh thu cá cược hàng năm trong khi vẫn tiếp tục xác thực thông qua Steam:\n\nNền tảng / Tên miền\tThông báo về sự kiện “2016” tháng 7\tKết quả thi hành và tình trạng còn tồn tại\tXác minh đã ghi lại / Các liên kết chính\nCSGOBig\ncsgobig.com\t10-Day Notice (Jul 2016)\tSTILL LIVE IN 2026\nTemporarily paused, relaunched; authenticates via letmeinbig.com & csgobiglogin.com\tX: @csgobig ↗ · FB: csgobigofficial ↗\nCSGO500\ncsgo500.com / 500.casino\t10-Day Notice (Jul 2016)\tSTILL LIVE IN 2026\nRebranded into 500 Casino (Curaçao license #8048/JAZ2014-037), multi-million monthly turnover\tLive Platform (500.casino) ↗\nCSGOFast\ncsgofast.com\t10-Day Notice (Jul 2016)\tSTILL LIVE IN 2026\nActively operating roulette, crash, and jackpot via steam-login.authtofast.com\tDossier Auth Audit ↗\nCSGOLounge / Dota2Lounge\ncsgolounge.com / dota2lounge.com\t10-Day Notice (Jul 2016)\tSTILL LIVE IN 2026\nPivoted to esports coin wagering and crypto betting; maintained continuous operation\tLive Platform ↗\nCSGOCasino\ncsgocasino.net / csgocasino.gg\t10-Day Notice (Jul 2016)\tLIVE VIA SUCCESSOR (2026)\nDomain redirected; active successor portal operates under csgocasino.gg\tSuccessor Domain ↗\nCSGOatse\ncsgoatse.com\t10-Day Notice (Jul 2016)\tSURVIVED 6 YEARS (ACTIVE TO 2022)\nContinued full gambling operations for six years following Valve's 10-day ultimatum\tX: @CSGOatsecom (Active to 2022) ↗\nCSGOSweep\ncsgosweep.com\t10-Day Notice (Jul 2016)\tSURVIVED TO DEC 2017\nOperated publicly for 17 months after deadline\tX: CSGOSweep Status Dec 2017 ↗\nCSGOWild\ncsgowild.com\t10-Day Notice (Jul 2016)\tSURVIVED TO DEC 2017\nPromoted by major influencers; ran for 1.5 years post-C&D before crypto migration\tX: @Wild (Active Dec 2017) ↗\nCSGOPot\ncsgopot.com\t10-Day Notice (Jul 2016)\tSURVIVED TO SEPT 2017\nOperated high-stakes jackpot betting 14 months past notice\tX: @csgopot (Active Sep 2017) ↗\nCSGODiamonds\ncsgodiamonds.com\t10-Day Notice (Jul 2016)\tSURVIVED TO MID 2017\nRan through 2017 despite admitted outcome tampering for sponsored streamers\tX: @csgodiamondscom (2017) ↗\nCSGOLotto\ncsgolotto.com\t10-Day Notice (Jul 2016)\tCLOSED JULY 2016\nShut down under public scandal; target of federal FTC consent order\tFTC Consent Order (Docket C-4632) ↗\nCSGODouble\ncsgodouble.com\t10-Day Notice (Jul 2016)\tCLOSED JULY 2016\nShut down voluntarily immediately after C&D publication\tX: @CSGODouble (Closed Jul 2016) ↗\nCSGOMassive\ncsgomassive.com\t10-Day Notice (Jul 2016)\tCLOSED 2016\nCeased public operations in late 2016\tX: @csgo_massive ↗\nCSGOStrong\ncsgostrong.com\t10-Day Notice (Jul 2016)\tCLOSED 2016\nCeased public operations in 2016\tFB: csgostrongfree ↗\nSkins2\nskins2.com\t10-Day Notice (Jul 2016)\tCLOSED 2016\nCeased public operations in 2016\tFB: CSNCOM ↗\n\nNền tảng\tLưu lượng truy cập hàng tháng (Số lượt truy cập)\tDoanh thu / Khối lượng ước tính\tThực thể doanh nghiệp và phạm vi thẩm quyền\tCác biện pháp quản lý chính và mô hình\nCSGOEmpire\ncsgoempire.com\t2.3M — 9.0M / mo\nAvg 6+ min duration; 80% direct\t$1.5B — $2.5B Annual Handle\n>1,000,000 P2P skin trades/mo; $6.4M active liquid order floor\tMoonrail Limited B.V. (Curaçao #148182)\nPayments: JHOLT LTD (Cyprus); Founder: \"Monarch\" (Ossi Ketola)\tPioneered 0% fee P2P item trading; licensed Curaçao OGL/2024/1183/0869\nCSGORoll\ncsgoroll.com\t2.74M — 3.5M / mo\nAvg 9m 23s duration; 16% bounce rate\t$1.0B — $2.0B Annual Handle\nEst. $100M–$200M annual corporate revenue from house edge\tFeral Holdings Limited\nHeadquartered in Belize City, Belize (Reg #171519)\tBanned by Australian ACMA (May 2023); sponsored tier-1 team G2 Esports with underage players\n500 Casino (CSGO500)\n500.casino / csgo500.com\t220K — 425K / mo\n~105k unique monthly visitors\t$100k / week ($5.2M/yr) in Royales\nHigh-roller wagering requirement: $400 wager per $1 rakeback\tPerfect Storm B.V. (Curaçao #150536)\nCuraçao Gaming Control Board license OGL/2024/1354/0882\tBanned by Swedish Spelinspektionen (Nov 2023) for unlicensed targeting of Swedish players\nCSGOBig\ncsgobig.com\t~169,600 / mo\nAvg duration 19m 12s; US primary\tMulti-Million Annual Volume\nMystery boxes, roulette, and case battles\tOperates via auxiliary proxy routing\nletmeinbig.com (reg 2023) & csgobiglogin.com\tTarget of July 2016 C&D; relaunched with proxy auth architecture\nCSGOFast\ncsgofast.com\t~150K — 250K / mo\nGlobal multi-language audience\tMulti-Million Annual Volume\nHigh-velocity roulette and crash games\tOffshore operational entities\nRoutes Steam auth via steam-login.authtofast.com\tTarget of July 2016 C&D; never discontinued operations; active in 2026\nCSGOPolygon\ncsgopolygon.com / plg.bet\t~300K — 500K / mo\nCIS and Eastern European dominance\tMulti-Million Annual Volume\nCrypto & skin roulette, match betting\tSecond-wave target (Oct 2016)\nPivoted to cryptocurrency with mirror domain plg.bet\tSurvived a full decade; continues skin liquidation via third-party APIs\nLàn sóng thứ hai: Tại sao thông báo yêu cầu ngừng và chấm dứt (C&D) của Valve lại nhắm vào 43cùng các trang web khác?\n\nVào ngày 17 tháng 10 năm 2016,, luật sư của Valve đã chính thức thông báo với Ủy ban Cờ bạc Tiểu bang Washington rằng, sau khi nhận được các thông báo ban đầu tại 23 vào ngày 19, tháng 7 năm Valve, họ đã gửi các thư yêu cầu ngừng vi phạm đến hơn 20 các trang web cá cược trực tuyến khác (khiến tổng số chính thức vượt quá 43). Làn sóng thứ hai này là điều không thể tránh khỏi bởi vì danh sách ban đầu đã bỏ sót một cách khó hiểu những trung tâm cờ bạc lớn nhất và tai tiếng nhất trên thế giới:\n\nCSGOJackpot.com: Đơn vị tiên phong lịch sử trong lĩnh vực “skin jackpots”, từng xử lý khối lượng giao dịch lên tới hàng trăm triệu trước khi phải đóng cửa do đối mặt với nguy cơ bị truy tố hình sự từ chính phủ liên bang.\nCSGOShuffle.com: Đây là địa điểm nằm ở trung tâm vụ bê bối phát trực tuyến “2016” hồi tháng 7, nơi người phát trực tuyến trên Twitch có biệt danh PhantomL0rd bí mật sở hữu 33% của công ty này và bị phanh phui vì đã thao túng tỷ lệ cược bằng tiền của công ty.\nHệ sinh thái vĩ mô (200+ Các nhà khai thác): Theo nghiên cứu ngành do Narus Advisors và Eilers & Krejcik Gaming thực hiện, có hơn 200 trang web cá cược với các giao diện khác nhau đang hoạt động tại 2016,, tạo ra doanh thu cá cược trị giá $5.01 tỷ từ 3.03 triệu người chơi tích cực. Các thư của Valve tại 43 chỉ nhắm đến chưa đến 20% thị trường hoạt động.\nCác cuộc điều tra chính thức của Chính phủ và cơ quan quản lý về trò chơi cá cược da “Steam”\n\nHiện tượng cờ bạc trực tuyến đã được ghi nhận qua nhiều cuộc điều tra chính thức theo quy định pháp luật, các biện pháp thi hành pháp luật và các văn bản nêu rõ quan điểm của chính phủ:\n\n1. Ủy ban Cờ bạc Tiểu bang Washington (WSGC) (2016–2018)\n\nĐã gửi yêu cầu chính thức “Ngừng và Chấm dứt” tới 5 vào ngày 2016; đã công bố Bản tóm tắt lập pháp trên 30 vào ngày 2018, trong đó ghi nhận rằng “skins” là các tài sản tương đương tiền mặt và báo cáo khối lượng cá cược bằng “skins” trị giá $5.0B.\n\nBáo cáo lập pháp của WSGC dưới dạng PDF (Bản sao cục bộ) ↗\n2. U.S. Ủy ban Thương mại Liên bang (FTC) (tháng 9 năm 2017,, Hồ sơ vụ việc C-4632)\n\nĐây là biện pháp thi hành pháp luật đầu tiên của chính phủ liên bang liên quan đến hoạt động cá cược “skin” nhằm vào các chủ sở hữu của CSGOLotto là Trevor Martin và Thomas Cassell, với cáo buộc về các hành vi lừa dối và việc kiểm soát nền tảng mà không công bố.\n\nQuyết định và Lệnh đồng thuận của FTC ↗\n3. Bản tuyên bố quan điểm của Ủy ban Cờ bạc Vương quốc Anh (UKGC) và các cuộc kiểm toán về thanh thiếu niên\n\nCác skin trong trò chơi đã chính thức được phân loại là “tiền hoặc có giá trị tương đương tiền” theo Đạo luật Cờ bạc 2005.. Các cuộc khảo sát sau đó cho thấy hơn 11% trẻ em trong độ tuổi 11–16 đã từng đặt cược skin trong các trò chơi điện tử.\n\nKho lưu trữ nghiên cứu của UKGC ↗\n4. Cuộc điều tra của Thượng viện Úc về Môi trường và Truyền thông (2018)\n\nBáo cáo của Quốc hội Liên bang về \"Các giao dịch vi mô trong trò chơi để nhận các vật phẩm dựa trên may rủi\", đánh giá cơ chế hộp quà may mắn của tựa game “Valve”, việc rút tiền từ thị trường thứ cấp và các hành vi lách luật.\n\nCuộc điều tra của Quốc hội Úc ↗\nNhu cầu chưa được đáp ứng\n\nCông bố hồ sơ thực thi: những tài khoản cờ bạc và bot nào đã bị vô hiệu hóa, những máy chủ trả về nào đã bị hạn chế, và những dịch vụ thương mại nào đã được cấp phép. Việc công bố lệnh cấm công khai và cảnh báo trên trang chủ không chứng minh được rằng hoạt động cơ bản đã bị chấm dứt.\n\nPhần B — Các quy định và hồ sơ thực thi · Mục 12\nTên máy chủ đã có sẵn trong yêu cầu.\nBối cảnh và các giới hạn về nguồn\n\nValve hệ thống này hiện đã có sẵn một danh sách tên miền (Link Filter) và đã nhận được tên máy chủ xác thực trong mỗi yêu cầu OpenID. Mã giả dưới đây minh họa cấu trúc logic của việc kết nối hai thành phần này. Không có bằng chứng công khai nào cho thấy Valve thực hiện điều này.\n\nValve hiện đã vận hành một danh sách chặn tên miền. Valve hiện đã nhận được thông tin máy chủ đăng nhập trong mỗi yêu cầu OpenID. Không cần phải xây dựng gì cả — chỉ cần nối hai thứ đó lại với nhau là được. Đó là thao tác tra cứu tên máy chủ dựa trên danh sách do Valve tự duy trì. Mã giả dưới đây chỉ mang tính minh họa, không phải là cách triển khai củValve.\n\nforensic_autoban.py\n# Mà GIẢ MINH HỌA — Các hàm `Valve.block_domain()` và `flag_session_as_mitm()` không phải là các lệnh gọi thực tế đến `API`. Điều này minh họa cấu trúc logic của một biện pháp giảm thiểu mà Valve có thể triển khai đối với các miền xác thực proxy, chứ không phải cơ chế hoạt động thực tế bên trong của Valve.\n# Hình minh họa: Cấu trúc logic của quá trình kiểm tra yêu cầu OpenID đến\ndef kiểm tra yêu cầu OpenID(yêu cầu):\nblocked_origins = database.lấy_danh_sách_các_nền_tảng_bị_đưa_vào_danh_sách_đen()\nproxy_domain = request.params.lấy('openid.realm')\ntarget_redirect = request.params.lấy('openid.return_to')\n\n# Logic: Nếu máy chủ proxy chuyển hướng trở lại một trang web bị chặn, hãy chặn máy chủ proxy đó.\nđể trang web trong blocked_origins:\nnếu trang web trong target_redirect:\nValve.chặn_miền(proxy_domain)\nValve.đánh dấu phiên làm việc là MITM(request.session)\n# Kết quả: Yêu cầu đăng nhập đối với máy chủ đó đã bị từ chối\n\nQuan sát:\nTrong trường hợp một tên miền chính đã có trong Danh sách lọc liên kết (e.g.howl.gg, bị chặn tại 2026-09-18/19/21) và máy chủ xác thực của nó (howl.uno) xuất hiện trong yêu cầu OpenID từ nút đăng nhập của trang web đó, thì mối liên kết này có thể được Valve phát hiện thông qua dữ liệu yêu cầu của chính nó. Việc kiểm tra này có thể tự động hóa; tuy nhiên, việc có thực hiện kiểm tra hay không thì không thể tự động hóa.\nCác tiền lệ đã được ghi chép và báo cáo\n\nValve đã có ít nhất một lần can thiệp chính thức đối với một nhà điều hành bên thứ ba: trong vụ “2018”, cơ quan này đã thu hồi quyền truy cập của OPSkins vào hệ thống ExpressTrade (Thông báo của Valve ↗ đã lưu trữ 2026-03-07 ↗). Các báo cáo từ cộng đồng trên trang 2018 cũng đề cập đến việc một nền tảng thương mại điện tử (SkinJar) bị mất quyền truy cập; những báo cáo này chưa được xác minh và cơ chế xảy ra được suy luận dựa trên kết quả, chứ không phải từ quy trình đã được công bố.\n\nTiền lệ này xác lập điều gì:\n\nValve có thể ngắt quyền truy cập của một nhà cung cấp dịch vụ bên thứ ba bất cứ khi nào họ quyết định. CSGOFast, được nhắc đến trong các báo cáo truyền thông về các thông báo ngày 7 tháng 2016, đã hoạt động trên địa chỉ 2026-09-21 với máy chủ xác thực được đăng ký tại 2026-06-30 và không bị chặn bởi bộ lọc liên kết. Lý do tại sao một nhà cung cấp dịch vụ bị ngắt kết nối trong khi những nhà cung cấp khác thì không vẫn chưa được giải thích dựa trên bất kỳ tiêu chí công bố nào.\n\nNhững thông tin mà ngày đăng ký thể hiện và không thể hiện\n\nNgày đăng ký của một máy chủ xác thực là giới hạn dưới về thời điểm máy chủ đó có thể xuất hiện lần đầu tiên trong một yêu cầu OpenID; điều này không chứng minh việc sử dụng liên tục. sc-auth.net, ví dụ, tên miền 2019-04-02 (RDAP) đã được đăng ký và được ghi nhận xuất hiện trong quy trình đăng nhập Steam của Skin.Club vào tháng 9 năm 2026; những gì đã xảy ra trong khoảng thời gian giữa hai ngày này không được ghi nhận công khai.\n\nKiểm toán so sánh: Tiêu chuẩn tuân thủ của Tổ chức Hợp tác và Phát triển Kinh tế (API)\nKhía cạnh thi hành\tGitHub API Quy định\tSteam Trang web API (Valve)\n1. Compliance Neutrality\tPublished, uniform rules. Documented rate limits (e.g. 5,000 calls/hr for authenticated users, 15,000/hr for GitHub Enterprise Cloud organisations) and published acceptable-use policies apply to every account.\tNo published criteria. Individual accounts are terminated under the automation and commercial-use clauses (archived complaints), while no per-operator enforcement record for commercial platforms has been published.\n2. OpenID / Auth Proxy Abuse\tGitHub's published policies allow OAuth apps and tokens to be suspended or revoked for abuse, and its documentation describes automatic revocation of exposed tokens (authors' summary of GitHub documentation).\tSeparate-domain auth hosts observed in Steam OpenID flows (e.g. rbsnin.com, howl.uno, sc-auth.net) returned no Link Filter block on 2026-09-21 while their main domains did.\n3. Monetization of Abuse\tGitHub takes no transaction fee on items moved by third-party automation; its revenue model is subscriptions and marketplace listings.\tValve sells the case keys that produce the items, and the Community Market charges a combined fee of about 15% on sales completed inside the Market. No figure for revenue attributable to third-party platforms is estimated here.\n4. Evasion Loop Lifespans\tSuspended OAuth client IDs stop working platform-wide at suspension; the documentation does not publish a time-to-action figure and none is assumed here.\tSeparate-domain auth hosts with registration dates from 2011 to September 2026 returned no Link Filter block in the checks of 2026-09-19 and 2026-09-21. Registration date is a lower bound on possible use, not proof of continuous use.\nNguồn: Bài viết trên GitHub — Tài liệu về giới hạn tốc độ và chính sách nền tảng của API do GitHub công bố (tóm tắt của tác giả, không trích dẫn) · Bài viết trên Steam — Các kiểm tra của Link Filter đối với 2026-09-19 và 2026-09-21 (linkfilter-recheck-2026-09-21.json), cơ sở dữ liệu RDAP (domain-registration.json) và các khiếu nại hỗ trợ đã được lưu trữ (kho lưu trữ bằng chứng).\nPhần B — Các quy định và hồ sơ thực thi · Mục 13\nChênh lệch giá so với mức giá trên trang webSteam\n\nMón đồ này nằm trong kho của Steam; việc bán hàng diễn ra ở nơi khác. Một khẩu AWP Dragon Lore mới nguyên bản đã 62 Các ưu đãi đang diễn ra trên CSFloat; mức giá yêu cầu thấp nhất $10,623.95. Trên chính thị trường của Steam, giá chào bán không được cao hơn khoảng $1,800.. Để bán với mức giá cao hơn đã ghi nhận, chủ sở hữu cần có người mua ngoàiSteam hoặc thông qua một nền tảng giao dịch khác. Mặt hàng và việc chuyển nhượng vẫn phụ thuộc vào Steam.\n\nWhat this means — the Community Market listing ceiling\n\nSteam’s own market refuses a listing above roughly $1,800. A seller may ask less, never more. Items whose market price sits above that line therefore cannot be sold at that price on Steam at all — which is the mechanism that moves those sales to third-party venues while the item itself never leaves Valve’s inventory system.\n\nSection 13 — the off-Steam price gap →\n\nBối cảnh và các giới hạn về nguồn\n\nTrong phần này có ba cách tính khác nhau và chúng không thể thay thế cho nhau. 245 là số lượng danh mục tên sản phẩm CS2 có mức giá ưu đãi rẻ nhất hiện có vượt quá $1,800 chỉ riêng trên trang CSFloat, 20 tháng 9 năm 2026. 241 đó chính là tập hợp đó trừ đi bốn hạng mục được ghim tại mức trần $100,000 của CSFloat, đây chính là bảng dữ liệu được dùng để tính toán mức sàn $13.63M. 248 Đây là một bức tranh tổng quan khác: các danh mục có giá cao hơn mức trần tại hai hoặc nhiều hơn trong số năm sàn giao dịch trên 23 vào ngày 2026. Các sàn giao dịch này có sự trùng lặp, do đó tuyệt đối không được cộng dồn số liệu từ các nền tảng khác nhau. Mọi con số ở đây đều là giá chào bán, không phải giá bán đã hoàn tất, và không có con số nào trong số đó là doanh thu, doanh số hay lợi nhuận — cho Valve hay bất kỳ ai khác. Các giá trị được liệt kê trên PriceEmpire là các ước tính làm tròn do trang web đó công bố, và thẻ \"Steam\" của trang này bao gồm các mặt hàng từ các trò chơi khác thuộc dòng Steam, do đó phạm vi so sánh giữa các mục không hoàn toàn trùng khớp.\n\nMột mặt hàng. Hai hệ thống giá.THEO DÕI KẾT QUẢ\nBước 3 / 3\n\nVới mức giá đó, người bán cần một nền tảng giao dịch bên ngoàiSteam hoặc một người mua. Mặt hàng này vẫn phụ thuộc vào kho hàng và hệ thống chuyển nhượng của Steam.\n\nSTEAMGiá khoảng $1,800Giới hạn số lượng tin đăng trên Chợ Cộng đồng đã được công bố\nDANH MỤC Đà LƯU$10,623.95AWP Dragon Lore nguyên seal từ nhà máy, xin báo giá\nSỰ PHỤ THUỘCVẫn là một sản phẩm thuộc dòng “Steam”Danh mục hàng tồn kho và việc chuyển giao vẫn được thực hiện trên Steam\n01 / SẢN PHẨMValve kho đồ trong trò chơiVật phẩm “2” trong CS2 hoặc Dota được lưu trữ tại Steam\n02 / TRẦN NHÀKhoảng $1,800 trên SteamGiá tối đa cho một sản phẩm được đăng trên Market\n03 / YÊU CẦU TỪ BÊN NGOÀI$10,623.95 cho Dragon LoreƯu đãi “CSFloat” rẻ nhất trong ảnh chụp màn hình ngày hôm đó\n04 / GIAO HÀNGSteam vẫn còn trong chuỗiQuyền sở hữu và việc chuyển nhượng vật phẩm phụ thuộc vào hệ thống của nó\nCẤU TRÚC THỊ TRƯỜNG · BẢN TÓM TẮT THEO NGÀY, 20 THÁNG 9 NĂM 2026\nChênh lệch giá là có thể đo lường được.\n\nChúng tôi đã thống kê các danh mục tên mặt hàng có mức giá ưu đãi rẻ nhất hiện có cao hơn chính xác $1,800. CSFloat và Skinport là các bản chụp riêng biệt với danh mục hàng tồn kho CS2 trùng lặp; số lượng của chúng không thể cộng dồn. Các ưu đãi bên ngoài cho thấy những nơi có giá chào bán cao hơn được đăng tải, trong khi Steam vẫn kiểm soát quyền sở hữu và chuyển nhượng mặt hàng.\n\n245CÁC DANH MỤC CS2 · CSFLOAT\n166CÁC DANH MỤC CỦA CS2 · SKINPORT\n3DOTA2: CÁC DANH MỤC · SKINPORT\n$10,623.95CÂU HỎI VỀ TẦNG DRAGON LORE\n\nDragon Lore: 62 hiện có CSFloat giao dịch trong danh mục “Factory New”; mức giá hiển thị là giá chào bán, không phải giá bán đã được xác nhận. Steam cho phép đăng bán mặt hàng với giá thấp hơn, nhưng không được đăng mức giá chào bán cao hơn đã được ghi nhận. Tuyên bố tại 2016 của Valve xác nhận rằng họ đã biết về việc các nhà điều hành cờ bạc sử dụng OpenID và cơ sở hạ tầng giao dịch Steam. Việc một sàn giao dịch bên thứ ba cụ thể có vi phạm quy tắc của Valve hay không phải được xác định riêng biệt.\n\nXem toàn bộ sổ đăng ký →CSFloat JSON ↗Skinport JSON ↗Tuyên bố “2016” của Valve ↗\nDIRECT CSFLOAT API / BẢN CHỤP MÀN HÌNH THEO NGÀY$13.63M\n\nGiá chào bán tổng cộng tối thiểu tại 241 danh mục sản phẩm và 3,395 các ưu đãi đang áp dụng. Được tính bằng cách nhân mức giá chào bán rẻ nhất của mỗi nhóm với số lượng cổ phiếu được chào bán trong nhóm đó. Bốn nhóm bị giới hạn ở mức trần $100,000 theo quy định của Ủy ban Chứng khoán và Giao dịch (CSFloat) đã bị loại khỏi bảng phân tích thận trọng này.\n\nCon số này cho thấy điều gì\n\nCác ưu đãi này tương đương với ít nhất $13,631,888.25 trong các mức giá niêm yết của bộ sưu tập “CSFloat” phiên bản giới hạn này. Khi tính cả bốn hạng mục có mức giá cao nhất, tổng cộng sẽ là $14,231,888.25. Đây là một giá sàn đối với các lệnh mua đang hoạt động, chứ không phải doanh số bán hàng đã hoàn tất, doanh thu tiền mặt, lợi nhuận hay toàn bộ thị trường CS2.\n\nTính toán lại từ bản chụp nhanh CSFloat của hàng “245-” ↗\nPRICEEMPIRE / GIÁ TRỊ NIÊM YẾTSteam: #15 thuộc 39\nNhiều địa điểm niêm yết mức giá cao hơn so với “Steam”.\nUUSkins\n$133.8M\nYouPin898\n$127.5M\nBuff.163\n$104M\nMoon.Market\n$100.3M\nWhite.Market\n$89.6M\nBuff.Market\n$86.7M\nSteam\n$31M\n\nSáu giá trị lớn nhất được hiển thị và Steam. PriceEmpire làm tròn các con số này; Steam cho thấy $31M. Có 14 địa điểm được liệt kê xếp trên địa điểm này theo giá trị bằng đô la được hiển thị.\n\nPRICEEMPIRE / SỐ LƯỢNG ƯU ĐÃISteam: #1 thuộc 39\nSteam vẫn dẫn đầu về số lượng lời đề nghị.\nSteam\n32.2M\nYouPin898\n5.9M\nC5Game\n4.6M\nHaloSkins\n4.4M\nSkinport\n3.8M\n\nSteam chương trình 32.2M số lượng đề nghị. Số lượng đề nghị và tổng giá chào bán trả lời cho những câu hỏi khác nhau; nhiều tin rao bán giá thấp có thể chiếm phần lớn trong tổng số.\n\nNguồn: So sánh công khai của PriceEmpire ↗ đã lưu trữ 2026-09-21 ↗, được ghi lại tại 2026-09-20 19:03 UTC; ngày 39-trích xuất hàng ↗. Các con số này là ước tính được làm tròn, và hàng tồn kho có thể trùng lặp giữa các địa điểm. Thẻ của “Steam” cũng mô tả các vật phẩm từ các tựa game khác thuộc dòng “Steam”, do đó phạm vi của hai danh sách này không hoàn toàn trùng khớp. Giá trị được liệt kê phản ánh giá chào bán, chứ không phải doanh số hay doanh thu.\n42\nMỘT NGUỒN THÔNG TIN KHÁC / STEAMANALYST\nHệ sinh thái thương mại đang hiện hữu rõ ràng trước mắt.\n\nDanh mục thị trường của SteamAnalyst đã lưu trữ 2026-07-19 ↗ liệt kê các sàn giao dịch CS2 của bên thứ ba tại 42 cùng với Steam, kèm theo dữ liệu giá mới nhất cho các sản phẩm 32 thuộc danh mục 43. PriceEmpire liệt kê các sàn giao dịch 39 dựa trên tiêu chí lựa chọn riêng của mình. Các doanh nghiệp được nêu tên, các ưu đãi công khai, giá cả hiển thị: nền kinh tế này hoàn toàn minh bạch và có thể kiểm tra được.\n\nGIỚI HẠN CHÍNH LÀ CƠ CHẾ: VIỆC GIẢM GIÁ SẼ KẾT THÚC, NHƯNG MẶT HÀNG THÌ KHÔNG.\n\nTrên năm sàn thương mại điện tử được ghi lại trong một bản chụp màn hình có giấy phép, 248 Các danh mục sản phẩm CS2 đều có mức giá được định riêng, cao hơn mức trần niêm yết khoảng $1,800 của Steam từ hai đơn vị trở lên — và tất cả các danh mục này đều không có mặt trên Steam. Cùng một bản chụp nhanh này đã phân loại toàn bộ danh mục theo giá: Thị trường của Valve có 95.3% các danh mục sản phẩm có giá dưới mức trần và 1.9% các danh mục có giá trên mức trần. Sự sụt giảm này không phản ánh nhu cầu giảm sút; nó hoàn toàn phù hợp với quy tắc đã công bố. Việc bán hàng ở những mức giá đó đòi hỏi phải có người mua hoặc sàn giao dịch bên ngoài, trong khi Steam vẫn kiểm soát hàng tồn kho và quá trình chuyển giao — giao dịch được thực hiện qua trang thanh toán của Valve và việc giao hàng vẫn diễn ra trên nền tảng của Valve.\n\nSteam Câu hỏi thường gặp về thị trường ↗đã lưu trữ 2026-09-21 ↗Steam Thỏa thuận người đăng ký ↗đã lưu trữ 2026-09-21 ↗Bộ dữ liệu bản đồ năm thị trường ↗Bảng kê nguồn gốc ↗Bản chụp nhanh trước đó của CSFloat ↗Skinport ảnh chụp nhanh ↗PriceEmpire ↗đã lưu trữ 2026-09-21 ↗SteamAnalyst ↗đã lưu trữ 2026-07-19 ↗Sổ ghi chép chênh lệch giá ↗Bản đồ thang giá ↗\n\nPhần C — Khung pháp lý\nPhần C — Khung pháp lý · Mục 14 · Quyền tiếp cận của nhân viên\nAi có thể thiết lập lại các biện pháp bảo vệ?\nBối cảnh và các giới hạn về nguồn\n\nTính bảo mật của tài khoản còn phụ thuộc vào những người có quyền khôi phục tài khoản, kiểm tra các thông tin riêng tư hoặc thiết lập lại các biện pháp bảo mật của tài khoản đó. Cuộc điều tra phải theo dõi chặt chẽ các hành động đặc quyền này, giống như cách mà nó theo dõi các hành vi lạm dụng liên quan đến “API”.\n\nViệc khôi phục tài khoản trao cho nhân viên hỗ trợ quyền chuyển quyền sở hữu tài khoản khỏi chủ sở hữu ban đầu. Valve đã xác nhận bằng văn bản hai lần — vào ngày 2023 tháng 2 và ngày 2025 tháng 11 — rằng quyền hạn này đã được sử dụng để chuyển các tài khoản cho những người không đúng. Cách nhau 33 tháng, qua cùng một kênh. Dưới đây: giá trị của quyền truy cập đó, sáu trường hợp được trích dẫn nguồn, và bản ghi mà Valve lưu giữ cho từng trường hợp và chưa từng cung cấp cho bất kỳ ai.\n\nLời khai được lưu giữ / 9 Tháng 5 năm 2025\nMột phiếu khôi phục đã vô hiệu hóa tính năng bảo mật của tài khoản, cùng với khoản thiệt hại được báo cáo là $10,000\n\nMột người dùng trong kho lưu trữ các trường hợp hỗ trợ đã báo cáo rằng bộ phận Hỗ trợ của Steam đã đặt lại mật khẩu và vô hiệu hóa tính năng bảo vệ tài khoản sau khi một người khác gửi yêu cầu khôi phục tài khoản. Tác giả cho biết tài khoản này đã không hoạt động trong nhiều năm, vẫn lưu giữ các mục từ thời 2016–2017 và được bảo vệ bởi tính năng Steam Guard, có số điện thoại liên kết cùng các mã khôi phục đã lưu trữ.\n\n\"Steam Support still gave someone else access to my account.\"\n\nCáo buộc từ góc nhìn người thứ nhất, được ghi lại trong steam_support_tickets_MEGA.json, truy cập 110. Đọc toàn bộ bài đăng đã được lưu lại ↗\n\nĐây không phải là trường hợp xui xẻo của một người dùng nào đó. Cánh cửa đó — tức là yêu cầu hỗ trợ nhằm chuyển tài khoản cho bất kỳ ai cung cấp dữ liệu cũ hơn — chính là quy trình được ghi nhận áp dụng cho mọi trường hợp trong sổ cái dưới đây, và Valve đã hai lần nêu rõ điều này bằng văn bản.\n\nChủ sở hữu không thể thắng trong cuộc tranh luận đó. Quá trình khôi phục yêu cầu mã CD đầu tiên, địa chỉ email đầu tiên, thẻ thanh toán đầu tiên và số điện thoại đầu tiên. Những thông tin này có trong cơ sở dữ liệu của Valve, và bộ phận hỗ trợ có thể truy cập để đọc chúng — theo báo cáo là có thể truy xuất dữ liệu từ mười lăm năm trước. Một người có bản sao hồ sơ của bạn sẽ luôn cung cấp được nhiều thông tin lịch sử hơn cả chính bạn. Các mục tiêu được chọn sao cho phù hợp: không hoạt động trong nhiều năm, có giá trị cao và thường được mua lại từ người khác, do đó người sở hữu hiện tại không bao giờ biết mã gốc. Sau đó, các tài khoản này bị xóa hoàn toàn, cắt đứt dấu vết lịch sử giao dịch mà cộng đồng sử dụng để truy vết một skin — một thao tác xóa mà người dùng thông thường không thể thực hiện nếu không tuân thủ thời gian chờ tiêu chuẩn.\n\nQuyền truy cập tối thiểu / OWASP A01\n\nCác quyền truy cập phục hồi nên được giới hạn trong phạm vi nhiệm vụ cụ thể, phải được rà soát độc lập và ghi lại. Cần kiểm tra xem ai có thể đặt lại thông tin đăng nhập, gỡ bỏ tính năng Bảo vệ chống truy cập trái phép (Steam Guard), xem hồ sơ thanh toán hoặc xuất dữ liệu tài khoản. Hướng dẫn về kiểm soát truy cập của OWASP ↗ đã lưu trữ 2026-09-20 ↗\n\nTruy cập hỗ trợ rộng rãiRủi ro liên quan đến phạm vi truy cập\nVượt ra ngoài phạm vi hàng tồn kho.\n\nNếu quyền truy cập rộng rãi bị lạm dụng, dữ liệu đo lường từ xa cá nhân có thể trở thành công cụ để phân loại đối tượng, thực hiện các cuộc tấn công lừa đảo nhắm mục tiêu và giám sát. Các nạn nhân tiềm năng bao gồm người dùng thông thường, quân nhân, nhân vật công chúng và gia đình của họ. Đây là một mô hình đe dọa; các quyền truy cập cụ thể cần phải được ghi chép trong hồ sơ kiểm soát truy cập.\n\n01 Lịch sử và vị trí IP\nNhật ký IP có thể tiết lộ lịch sử kết nối mạng và vị trí xấp xỉ. Bản thân các nhật ký này không thể xác định chính xác các chuyển động thực tế.\n02 Nhận dạng dấu vân tay thiết bị\nCác mã định danh thiết bị, nếu được thu thập và có thể truy cập, có thể liên kết các phiên làm việc và tài khoản với nhau.\n03 Dữ liệu đo từ xa về hoạt động\nDấu thời gian đăng nhập và bản ghi phiên làm việc có thể tiết lộ thói quen sử dụng, bao gồm cả những hoạt động không hiển thị trên hồ sơ công khai.\n04 Truyền thông và liên hệ\nViệc truy cập vào các tin nhắn đã lưu trữ hoặc thông tin liên lạc sẽ làm gia tăng nguy cơ bị phân loại hồ sơ cá nhân và bị lợi dụng thông qua các thủ đoạn thao túng tâm lý.\n05 Vạch trần danh tính\nCác bản ghi gốc về email, số điện thoại và thanh toán có thể giúp xác định danh tính của một cá nhân thông qua tài khoản ẩn danh.\n06 Việc bán lại dữ liệu và trách nhiệm giải trình\nCác danh sách mục tiêu đã xuất ra có thể được sử dụng để thực hiện các vụ lừa đảo có chủ đích. Cần xác định đối tượng thực hiện, vị trí truy cập, người nhận và các giao dịch chuyển tiền; chỉ riêng vị trí không đủ để xác định việc truy cập cũng như miễn trừ trách nhiệm pháp lý.\n\nValve trình bày về việc ghi nhật ký địa chỉ IP, thông tin thiết bị, hồ sơ thanh toán và các nhà cung cấp dịch vụ hỗ trợ bên thứ ba trong Chính sách bảo mật §§ 3, 5.2 đã lưu trữ 2026-09-21 ↗. Chính sách này cho phép bên thứ ba truy cập để hỗ trợ — tuy nhiên, hồ sơ theo dõi cho thấy nhà thầu nào đã truy cập vào danh mục nào, vào thời điểm nào và dựa trên cơ sở ủy quyền nào thì vẫn chưa được công bố.\n\nPhần 14.1 · The Register · Tháng 6 2022 → Tháng 11 2025 · Tất cả số liệu đều có nguồn gốc rõ ràng\nValve Cánh cửa đã được mở ra hai lần, cách nhau ba mươi ba tháng. Nó chưa bao giờ đóng lại.\n\nCó sáu trường hợp được báo cáo liên quan đến việc các tài khoản bị chiếm đoạt thông qua kênh yêu cầu trợ giúp của chính Steam, hoặc thông qua thông tin đăng nhập mà kênh này bảo vệ. Mỗi số tiền được nêu là con số mà nguồn được trích dẫn đã công bố, và mỗi nguồn đều được nêu tên. Hai trong số sáu trường hợp này đã được bồi thường đầy đủ. Điểm khác biệt giữa hai trường hợp này với các trường hợp còn lại không phải là những gì đã xảy ra — mà là ai đang theo dõi.\n\nValve gửi bằng văn bản — Tháng 2 năm 2023\"The items in question were removed from your account because they were received from an account that was compromised through a support help request, for which the CS:GO team takes responsibility. We have reversed the trades and removed them from any account which received them.\"Steam Hỗ trợ trả lời người nhận các sản phẩm của HFB, được sao chép bởi Dexerto, 21 tháng 2 năm 2023 ↗ đã lưu trữ 2025-08-18 ↗\nValve lại viết bài — Tháng 11 năm 2025 · 33 tháng sau đó\"A support technician that handled the help request failed to follow our process which resulted in your account restored to someone else. I apologize for this error.\"Steam Trả lời bình luận của Hawkeye337, được trích dẫn trong Dexerto, 14 tháng 11 năm 2025 ↗\n21 2022 tháng 6\nHFB — kho hàng lớn nhất trong trò chơi$2,000,000+ · đã huy động được $3,000,000+ trong đợt huy động vốn tiếp theo trên 2023 vào tháng 2\n\nBảy món đồ lưu niệm AWP Dragon Lores và con dao Karambit ngọc xanh #1; riêng con dao này đã có giá trị khoảng 1.26 triệu đô la. Tài khoản này đã không hoạt động trong ba năm nhưng ứng dụng xác thực trên điện thoại di động vẫn còn hoạt động; dù vậy, địa chỉ email và mật khẩu vẫn được thay đổi thông qua quy trình khôi phục của bộ phận hỗ trợ.\n\nTiền đã hết trước khi các món đồ được mang đi. Theo báo cáo $200,000+ Một phần tiền thu được từ việc bán hàng đã được rút qua market.csgo.com — một sàn giao dịch thanh toán bằng tiền mặt và tiền điện tử. Việc hủy giao dịch sẽ trả lại skin. Nó không trả lại số tiền mặt mà người dùng đã rút về tài khoản.\n\nVà bản vá lại bị hỏng. Một người mua đã chuyển món đồ “Souvenir Dragon Lore” của mình vào một Kho chứa trong trò chơi. Tập lệnh khôi phục của Valve không thể “nhìn” vào bên trong chính kho chứa đó, nên nó đã cấp cho chủ sở hữu một bản sao mới và để nguyên bản bị ẩn — Valve đã sao chép một $130,000 mặt hàng khi đang cố gắng hủy bỏ một vụ trộm cắp. Vụ việc đã bị phát hiện nhờ đối chiếu mã ID mặt hàng và thông tin báo cáo từ cộng đồng, và mặt hàng đó đã bị xóa một tháng sau đó, vào tháng 7 năm 2022. Người mua đã được BUFF hoàn tiền, chứ không phải từ Valve. Việc khắc phục khẩn cấp một cách thiếu bền vững như vậy không phải là một biện pháp kiểm soát; đó là điều mà một nền tảng thực hiện khi không thể kiểm soát được tình hình.\n\nDexerto, 21 Jun 2022 ↗ đã lưu trữ 2022-07-02 ↗ · Kaspersky ↗ · Số tiền rút ra trên mỗi Esportfire, 22 Jun 2022 ↗ đã lưu trữ 2026-05-15 ↗, được trích dẫn từ nhiều nguồn trên trang Twitter · sao chép và xóa theo Esportsbetting, 14 Tháng 7 năm 2022 ↗\n\nĐã được phục hồiCác giao dịch đã bị hủy bỏ. Các mặt hàng đã bị thu hồi khỏi kho hàng của những người đã mua chúng với giá đầy đủ.\n14 2022 tháng 8\nCS.Money — các bot của chính nền tảng này$6,300,000 · 19,000+ các giao diện · ước tính ban đầu $1.6M\n\nNhững kẻ tấn công đã chiếm đoạt các tệp xác thực trên thiết bị di động của các bot giao dịch trên sàn thương mại điện tử và xóa sạch dữ liệu trong đó, sau đó chuyển một phần số tài sản chiếm được cho các nhà giao dịch nổi tiếng nhằm che giấu dấu vết. Các nhà nghiên cứu trong cộng đồng đã lập bản đồ 55 các tài khoản của kẻ tấn công chỉ trong vài giờ và đã xuất bản chúng.\n\nValve không đảo ngược bất cứ điều gì. Lý do được đưa ra là trang web của bên thứ ba nằm ngoài Steam — chính là Steam, nơi mà vụ trộm đã diễn ra từ đầu đến cuối trên nền tảng hàng tồn kho, giao dịch API và hệ thống tài khoản của trang web này.\n\nEsportfire, 14 Tháng 8 năm 2022 ↗ đã lưu trữ 2025-11-15 ↗\n\nBị từ chốiKhông có sự đảo chiều. Mất mát vẫn thuộc về nền tảng và người dùng của nó.\nĐã được báo cáo\n21 2023 tháng 2\nQkss — cùng một cánh cửa, cùng một diễn viên$1,000,000+\n\nTheo báo cáo, trường hợp này được xử lý theo cách tương tự như trường hợp HFB, do cùng một người dùng thực hiện, thông qua cùng một yêu cầu hỗ trợ. Trường hợp HFB đã được giải quyết triệt để tám tháng trước đó. Còn trường hợp Qkss thì chưa.\n\nMột con đường. Hai câu trả lời. Không có chi tiết nào trong hồ sơ đã công bố cho thấy sự khác biệt giữa hai vụ việc này, ngoại trừ quy mô của khán giả.\n\nDexerto, 21 Tháng 2 năm 2023 ↗ đã lưu trữ 2025-08-18 ↗\n\nBị từ chốiChưa được khôi phục.\nĐã được báo cáo\n2023 tháng 2\nChính hoạt động giao dịch nội gián — kéo dài suốt một năm≈ $320,000 · diễn ra trong khoảng một năm, không phải là việc định giá hàng tồn kho\n\nQuyền truy cập từ phía hỗ trợ đã truy cập được lịch sử tài khoản đến 15 tuổi — mã CD đầu tiên, email đầu tiên, thẻ đầu tiên. Đó chính xác là những bằng chứng mà quy trình khôi phục yêu cầu, và đó là lý do tại sao người nắm giữ cơ sở dữ liệu luôn thắng trong cuộc tranh cãi với người nắm giữ tài khoản.\n\nBlogger Mzkshow đã vạch trần cách thức mà kẻ điều hành nội bộ “Steam Help” và đồng phạm “Alexander” nhắm mục tiêu vào các tài khoản không hoạt động chứa hơn $100k skin. Một khẩu M4A4 Howl bị đánh cắp, đi kèm với các skin iBUYPOWER và Titan Katowice 2014, đã được bán với giá $35,000 và cuối cùng liên quan đến Valerii \"b1t\" Vakhovskyi của NAVI, người hoàn toàn không hay biết gì về việc này. Sau khi Valve can thiệp, nhà thầu đã sa thải toàn bộ bộ phận hỗ trợ Steam của mình.\n\nVKPlay ↗ · Lis-Skins ↗ · Escorenews (RU) ↗ · Dexerto (EN) ↗\n\nKhông có sổ đăng kýValve chưa bao giờ công bố số lượng tài khoản bị ảnh hưởng là bao nhiêu, cũng như chưa thông báo cho những người bị ảnh hưởng.\nĐã được báo cáo\n2 Tháng 12 năm 2024\n\"Matvey\" — sau các vụ sa thải$13,000\n\nViệc khôi phục đã được chấp thuận cho một người đã cung cấp dữ liệu tài khoản mà chính chủ tài khoản cũng không thể xác minh được. Hai năm sau khi nhà thầu giải thể bộ phận hỗ trợ Steam, việc áp dụng cùng phương thức này đã mang lại kết quả tương tự.\n\nBài đăng được lưu trữ, 2 tháng 12 năm 2024 ↗ đã lưu trữ 2025-08-05 ↗ · các hàng nguồn & hàm băm ↓\n\nBị từ chốiChưa được khôi phục.\n13 2025 tháng 11\nHawkeye337 (Mark Spurlock) — và lần thừa nhận thứ hai≈ $300,000–$500,000 · Bộ sưu tập holo đầy đủ của Katowice 2014\n\nKẻ tấn công đã yêu cầu 1 bitcoin và bắt đầu sao chép bộ sưu tập sang các thiết bị Negev để xóa bỏ nó. Steam Phản hồi bằng văn bản của bộ phận Hỗ trợ chính là lời thừa nhận thứ hai nêu trên: một kỹ thuật viên đã xử lý yêu cầu hỗ trợ, không tuân thủ quy trình và đã chuyển tài khoản đó cho người khác.\n\nNguyên nhân dẫn đến sự cố chính là nguồn cấp dữ liệu. Chỉ vài giờ sau khi các bài đăng gắn thẻ Valve được đăng lên X, tài khoản này đã được khôi phục và tất cả các sticker đều được phục hồi. Qkss không có lượng người theo dõi như vậy.\n\nSkin.club ↗ · Dexerto ↗ · Esportfire ↗ đã lưu trữ 2025-12-17 ↗\n\nĐã được phục hồiBài viết đã bị gỡ xuống chỉ vài giờ sau khi trở thành chủ đề hot.\nNhững gì sổ cái ghi lại là điều mà không một trường hợp cụ thể nào có thể làm được.\n\nTuyến đường này chưa bao giờ bị đóng cửa. Lần nhập viện đầu tiên có ngày tháng là tháng 2 năm 2023 và lần thứ hai là tháng 11 năm 2025 — cách nhau ba mươi ba tháng, cùng với vụ sa thải hàng loạt của nhà thầu, một vụ tái diễn đã được ghi nhận và một vụ vi phạm nền tảng trị giá $6.3 triệu xảy ra trong khoảng thời gian đó. Tính từ vụ trộm đầu tiên được ghi nhận trong sổ sách này, kênh này vẫn mở trong ba năm và năm tháng. Dù vấn đề đã được khắc phục tại 2023, thì vào tháng 11, yêu cầu trợ giúp vẫn chuyển tài khoản sang người dùng sai 2025 — Câu nói của chính Valve.\n\nViệc bồi thường tập trung vào việc theo dõi mức độ chú ý, chứ không phải mức độ tổn hại. Đã khôi phục: kho đồ lớn nhất trong trò chơi và người sưu tầm có chủ đề gây sốt. Đã từ chối: $1,000,000, $6,300,000, $13,000.Valve chưa bao giờ công bố quy tắc mà họ áp dụng, bởi vì nếu công bố quy tắc thì sẽ phải giải thích về ba trường hợp trên.\n\nKhông ai được thông báo. Không phải những người dùng có lịch sử tài khoản bị trích xuất khỏi cơ sở dữ liệu, không phải cơ quan giám sát, cũng không phải thị trường đã mua các mặt hàng đó với thiện chí và sau đó bị thu hồi. Không có thông báo về vi phạm, không có báo cáo sự cố, cũng không có số liệu thống kê về số tài khoản bị ảnh hưởng — và số tiền thu được còn lại dưới dạng tiền mặt, thông qua các sàn giao dịch thanh toán bằng tiền mặt và tiền điện tử. Việc đảo ngược giao dịch không thể theo dõi dòng tiền rút ra khỏi Steam.\n\nValve lưu giữ bản ghi kiểm toán hỗ trợ, nhật ký phiếu yêu cầu khôi phục và bản ghi giao dịch cho mỗi dòng ở trên. Không có tài liệu nào trong số đó được cung cấp. Yêu cầu nhận bản sao của riêng bạn →\n\nCâu hỏi về NDA\nTính bảo mật phải đi kèm với trách nhiệm giải trình về mặt kỹ thuật.\n\nSo sánh các thỏa thuận bảo mật với các quyền truy cập thực tế, các biện pháp kiểm soát xuất khẩu, các phê duyệt khôi phục và nhật ký truy cập. Một câu trả lời mẫu không thể giải quyết được cáo buộc rằng chính quy trình khôi phục đã bị lạm dụng.\n\nGDPR Các bài viết 28, 32–34\n\nĐiều 33 quy định người kiểm soát dữ liệu phải thông báo cho cơ quan giám sát về vụ vi phạm dữ liệu cá nhân trong vòng 72 giờ; Điều 34 yêu cầu phải thông báo cho những người bị ảnh hưởng khi rủi ro đối với họ ở mức cao. Valve đã xác nhận bằng văn bản, hai lần, rằng kênh hỗ trợ của họ đã chuyển các tài khoản cho nhầm người — bao gồm lịch sử giao dịch, hồ sơ thanh toán và tất cả các thông tin liên quan. Chưa có thông báo nào theo quy định tại hai điều khoản trên được công bố, và chưa có người dùng nào bị ảnh hưởng báo cáo rằng họ đã nhận được thông báo đó. Đọc quy định ↗ đã lưu trữ 2026-09-20 ↗\n\nHãy thêm yêu cầu hỗ trợ vào đơn yêu cầu của bạn →\nPhần C — Khung pháp lý · Mục 15 · Quy mô thương mại\nTheo dõi dòng tiền. Phân tách các giao dịch.\nBối cảnh và các giới hạn về nguồn\n\nVấn đề về mục đích thương mại trở nên rõ ràng hơn khi các dòng tiền được tách biệt. Các giao dịch chuyển nhượng tài sản cho bên thứ ba, hoạt động bán hàng chính của Công ty Cổ phần Công nghệ Thông tin và Truyền thông (Valve) và các khoản rút tiền ra bên ngoài là những giao dịch khác nhau.\n\nMặt hàng này thuộc sở hữu của Valve. Danh mục hàng tồn kho thuộc sở hữu của Valve. Quá trình chuyển giao được thực hiện trên các máy chủ của Valve. Chỉ có việc thanh toán là diễn ra ở một nơi khác — đây chính là bước quyết định liệu một người có phải là đơn vị chuyển tiền hay không, và cũng là bước duy nhất mà Valve không thực hiện.\n\nCơ chế thu nhập\nNơi dòng tiền thực sự lưu chuyển.\nBa con đường / nền kinh tế một mặt hàng\n01 / Tài khoảnDanh sách người dùng\n\nCác bài viết được đăng trên Steam\n\n02 / Chuyển khoảnGiao dịch ngang hàng (P2P)\n\nNgười dùng ↔ bot hoặc người dùng ↔ người dùng\n\n03 / Thanh toánNền tảng bên ngoài\n\nThanh toán hoặc hoàn tất thanh toán Steam\n\nLưu thôngĐộng lực kinh tế không chỉ dừng lại ở mức phí chuyển nhượng\n\nSteam cung cấp cơ sở hạ tầng quản lý hàng tồn kho và chuyển nhượng được các thị trường bên ngoài sử dụng. Lập luận kinh tế của cuộc điều tra cho rằng tính thanh khoản khi bán lại và nhu cầu lặp lại duy trì chi tiêu cho các “vỏ”, “chìa khóa” và các mặt hàng thay thế, kèm theo phí từ các giao dịch tiếp theo trên Thị trường Cộng đồng. Một giao dịch chuyển nhượng trực tiếp giữa người dùng (P2P) không phải chịu hoa hồng của Thị trường Cộng đồng; thực tế kế toán này không giải quyết được lợi ích rộng lớn hơn. Valve vẫn duy trì quyền kiểm soát đối với quyền truy cập tài khoản và các hạn chế giao dịch trong suốt quá trình.\n\n01 / Nhu cầu thứ cấpKhả năng thanh khoản và giá trị bán lại\n\nNhu cầu từ hoạt động thương mại và cờ bạc ở nước ngoài\n\n02 / Chi tiêu chínhChìa khóa, hộp đựng và viên nang\n\nCác giao dịch mua hàng từ trang web Valve khi có chương trình khuyến mãi\n\n03 / Doanh thuThu nhập từ bán hàng lần đầu\n\nCộng với các khoản phí trên doanh thu thực tế từ thị trường\n\n5% + 10%Steam + Phí CS2 đối với các giao dịch trên Thị trường Cộng đồng\n\nKết luận kinh tế từ cuộc điều tra: thị trường bán lại sôi động có thể thúc đẩy chi tiêu cho các mặt hàng mới. Cơ chế “15%” quen thuộc kết hợp các mức phí thị trường, tuân theo mức tối thiểu và quy tắc làm tròn; đây không phải là một khoản thuế áp dụng cho mọi giao dịch thương mại quốc tế.\n\nBảng phí của Chợ Cộng đồng Valve ↗ đã lưu trữ 2026-09-21 ↗. Trên 25 ngày 2026 tháng 2 Tổng chưởng lý bang New York đã nộp đơn khởi kiện đã lưu trữ 2026-09-01 ↗ với cáo buộc rằng các hộp chiến lợi phẩm trả phí có liên quan đến việc bán lại bằng tiền mặt bên ngoài và tác hại từ cờ bạc — chính mối liên hệ này đã được hồ sơ này ghi nhận từ góc độ cơ sở hạ tầng kỹ thuật. Khiếu nại đó chỉ là một cáo buộc, không phải là kết luận; nó được trích dẫn ở đây vì một cơ quan thực thi pháp luật của tiểu bang đã đặt ra cho Valve một câu hỏi liên quan đến câu hỏi mà tài liệu này đặt ra: hồ sơ thực thi pháp luật nào phù hợp với những tuyên bố công khai đó?\n\n01 / MụcNạp tiền bằng tiền điện tử\n\nHồ sơ dịch vụ bên ngoài và ví\n\n02 / Chuyển đổiCân bằng → giao diện\n\nCác mặt hàng được giao thông qua các giao dịch trên Steam\n\n03 / ThoátBán tiền pháp định bên ngoài\n\nNgười bán, người mua và đơn vị thanh toán\n\nKYC?Xác định đối tượng điều khiển tại mỗi lần chuyển giao\n\nĐây là hướng cần điều tra, chứ không phải dịch vụ chuyển đổi tiền mặt “Steam” API do chính nền tảng cung cấp. Cần ghi chép lại các thông tin về xác minh danh tính, việc lưu giữ tài sản, mã giao dịch và người nhận tiền tại mỗi nhà cung cấp dịch vụ bên ngoài trước khi khẳng định rằng việc rút tiền mặt đó không tuân thủ quy trình xác minh danh tính (KYC).\n\nHoa Kỳ / Đạo luật Bảo mật Ngân hàng\nHãy phân loại hoạt động trước, sau đó mới đến nghĩa vụ.\n\nFinCEN đánh giá hoạt động chuyển tiền dựa trên các hoạt động cụ thể của doanh nghiệp. Việc chấp nhận và chuyển đổi tiền ảo có thể chuyển đổi được có thể dẫn đến các nghĩa vụ liên quan đến dịch vụ tiền tệ, tùy thuộc vào các định nghĩa và trường hợp ngoại lệ hiện hành. Ví “Steam” của Valve chấp nhận tiền và chuyển đổi chúng thành các vật phẩm trong trò chơi; sau đó, những vật phẩm này được thanh lý thông qua các nhà điều hành bên thứ ba để đổi lấy tiền thật. Vật phẩm và quá trình chuyển nhượng diễn ra trên nền tảng của Valve; việc rút tiền mặt thì không, và việc liệu bất kỳ phần nào trong chu trình đó có đáp ứng các định nghĩa về chuyển tiền hay không là một vấn đề phân loại thuộc thẩm quyền của FinCEN, không phải là kết luận được đưa ra tại đây.\n\nFinCEN FIN-2019-G001, các điều 1–2, 5.1 ↗ đã lưu trữ 2025-07-11 ↗\n\nLiên minh Châu Âu / rửa tiền\nTheo dõi nguồn thu, kiến thức và sự hỗ trợ.\n\nChỉ thị (EU) 2018/1673 quy định về hành vi rửa tiền có chủ ý và việc tham gia liên quan đến tiền thu được từ hoạt động tội phạm. Vấn đề cần làm rõ trong quá trình điều tra là Công ty Valve đã biết những gì về các nhà khai thác sử dụng cơ sở hạ tầng giao dịch và OpenID của mình sau ngày 13 tháng 7 năm 2016, – thời điểm công ty này công khai mô tả việc sử dụng đó – và công ty đã có những biện pháp gì đối với họ. Công ty Valve chưa công bố bất kỳ hồ sơ xử lý vi phạm nào theo từng nhà khai thác; chính hồ sơ đó, chứ không phải tài liệu này, mới có thể trả lời câu hỏi trên.\n\nKhung pháp lý về luật hình sự của Liên minh châu Âu ↗\n\nThuật ngữ trong AMLD6: Chỉ thị về luật hình sự nêu trên khác với Chỉ thị (EU) 2024/1640,, còn được gọi là AMLD6. Chỉ thị sau này có thời hạn chuyển hóa thành luật chung là ngày 10 tháng 7 năm 2027,, với một số trường hợp ngoại lệ cụ thể. Bài viết 78 ↗ đã lưu trữ 2026-08-30 ↗\n\nPhần C — Khung pháp lý · Mục 16 · Thông báo, phản hồi, trách nhiệm\nĐạo luật Dịch vụ Kỹ thuật số: ghi nhận kiến thức vào hồ sơ\nBối cảnh và các giới hạn về nguồn\n\nHai yếu tố trong thông báo theo Điều 16 thuộc trách nhiệm của người nộp hồ sơ chứ không phải của bộ hồ sơ này: thông tin cá nhân của người nộp hồ sơ và tuyên bố thiện chí xác nhận tính chính xác của thông tin. Tất cả các yêu cầu khác của Điều này — giải thích có căn cứ và vị trí điện tử chính xác — được nêu rõ trong Mục 3 và trong sổ đăng ký lộ trình, kèm theo các phản hồi đã lưu và mã băm, để bất kỳ bên nào cũng có thể nộp hồ sơ. Hai giới hạn nữa đối với chính luật này: việc mất quyền miễn trừ đối với nhà cung cấp dịch vụ lưu trữ không tự nó dẫn đến trách nhiệm pháp lý theo bất kỳ luật nào khác, và mức phạt tối đa (6%) tại Điều 52 (3) là mức trần theo luật định, không phải là mức phạt được xác định cụ thể đối với Valve.\n\nTheo Luật DSA, nhà cung cấp dịch vụ lưu trữ chỉ được hưởng sự miễn trừ trách nhiệm cho đến khi họ có thông tin cụ thể mà vẫn không có hành động nào. Hồ sơ này chính là thông báo đó. Bài báo nêu tên các máy chủ, ngày tháng, các phản hồi đã được lưu trữ và các giá trị băm. Kể từ khi bài báo được công bố, câu hỏi không còn là liệu Valve có biết hay không — mà là Valve đã làm gì tiếp theo.\n\n01Tháng 7 năm 2016 / Triển lãm hồ sơ\nYêu cầu kéo dài mười ngày.\n\nThông báo được tái lập ở trên là điểm khởi đầu lịch sử cho việc so sánh việc thi hành trong cuộc điều tra.\n\n0217 Tháng 2 năm 2024 / Đơn đăng ký chung\nKhoảng thời gian DSA.\n\nCần phân biệt hành vi trong quá khứ với hành vi trong giai đoạn mà các nghĩa vụ theo Luật DSA có liên quan được áp dụng.\n\n03Mười năm / ảnh chụp nhanh hồ sơ gốc\nThời gian thực hiện cần có hồ sơ theo dõi.\n\nThời gian đã trôi qua kể từ ngày 7 tháng 2016 (xem Mục 11) là một chỉ số trong hồ sơ. Đây không phải là mười năm vi phạm DSA đã được xác định. Hãy liên kết từng thông báo với một mục cụ thể, quy định pháp luật áp dụng, bằng chứng gửi thông báo và phản hồi.\n\nBài viết 52(3) / mức trần theo quy định6%\ntrong tổng doanh thu hàng năm trên toàn cầu\n\nMức phạt tối đa đối với hành vi vi phạm các nghĩa vụ theo Luật DSA, được tính dựa trên năm tài chính trước đó của nhà cung cấp. Đây là mức trần theo quy định pháp luật, không phải là mức phạt đã được áp dụng đối với Công ty Dịch vụ Kiểm toán và Thuế (Valve).\n\nCác bài viết 6, 8 & 16 / tiêu chí pháp lý\n\nĐối với các dịch vụ lưu trữ liên quan, việc có kiến thức cụ thể và không hành động kịp thời có thể dẫn đến việc mất quyền miễn trừ dành cho dịch vụ lưu trữ. Một thông báo đủ rõ ràng có thể chứng minh việc biết về nội dung cụ thể đó. DSA không quy định nghĩa vụ giám sát chung; việc mất quyền miễn trừ bản thân nó không đủ để xác lập trách nhiệm pháp lý theo một luật khác.\n\nDSA: Các điều 6, 8, 16, 52, 53, 93 và phần lý do 17 ↗ đã lưu trữ 2026-09-20 ↗\n\nXem lại các khiếu nại đã được lưu giữ ↗Tạo dòng thời gian tài khoản →Phân tích pháp lý và kinh tế toàn diện →\nPhần C — Khung pháp lý · Mục 17 · Danh tính, độ tuổi, quyền truy cập thương mại\nNgười chưa thành niên: Việc đăng nhập vào Steam không phải là hình thức xác minh độ tuổi\nBối cảnh và các giới hạn về nguồn\n\nKhông có dữ liệu nào của trẻ vị thành niên xuất hiện ở bất kỳ đâu trong hồ sơ này và cũng không có dữ liệu nào được thu thập: các tác giả không đăng ký, không tải lên hoặc đăng nhập vào bất kỳ nền tảng nào được nêu tên. Bất kỳ ai tham khảo phần này cần giữ bí mật các bằng chứng liên quan đến trẻ em và che giấu các chi tiết nhận dạng khỏi các tài liệu công khai. COPPA được trích dẫn ở đây với tư cách là luật bảo vệ quyền riêng tư của trẻ em, có các điều kiện phạm vi áp dụng riêng — đối tượng, sự biết rõ thực tế, dữ liệu cá nhân được thu thập — chứ không phải là quy định chung về độ tuổi tham gia cờ bạc; đơn khiếu nại tại New York của Viện Bảo vệ Quyền riêng tư Trẻ em (2026) là một cáo buộc từ cơ quan nhà nước, chứ không phải là kết luận chính thức.\n\n\"Đăng nhập bằng Steam\" chứng minh rằng tài khoản đó tồn tại. Điều đó không chứng minh được gì về tuổi tác cả — và trên các trang web này, đó là cánh cửa duy nhất ngăn cách giữa một đứa trẻ và một khoản tiền gửi. Hãy đọc nó cùng với Phần 3.1: trong ứng dụng khách Steam, cảnh báo mà trình duyệt thường hiển thị sẽ không bao giờ xuất hiện, do đó trẻ em sẽ không bao giờ nhìn thấy cảnh báo đó.\n\nNhững tính năng mà OpenID của Steam cung cấpThông tin tài khoản\n\nMột SteamID đã được xác minh dùng để đăng nhập hoặc liên kết tài khoản.\n\n≠\nNhững điều mà nhà khai thác phải xác địnhĐiều kiện tham gia\n\nĐộ tuổi, phạm vi thẩm quyền và các thủ tục xác minh danh tính cần thiết.\n\nCơ sở kỹ thuật: Tài liệu về Steamworks OpenID ↗ đã lưu trữ 2026-09-21 ↗. Việc xác nhận danh tính đã được ghi nhận không phải là chứng nhận cho thấy người dùng được phép tham gia cờ bạc một cách hợp pháp.\n\nCOPPA / Trẻ em dưới 13\nXác định toán tử và dữ liệu.\n\nLuật COPPA áp dụng đối với các dịch vụ dành cho trẻ em thuộc phạm vi điều chỉnh và các dịch vụ có thông tin cụ thể về việc thu thập thông tin cá nhân từ trẻ em dưới 13.. Đây là luật bảo vệ quyền riêng tư của trẻ em, không phải là quy định chung về độ tuổi tham gia cờ bạc. Cần xác định rõ đối tượng người dùng, loại dữ liệu cá nhân được thu thập, mức độ nắm rõ thông tin và quy trình xin sự đồng ý của phụ huynh.\n\nFTC: Các yêu cầu của COPPA ↗ đã lưu trữ 2026-09-21 ↗\n\nCác bằng chứng cần được bảo quản\nGhi lại toàn bộ quá trình từ khi đăng nhập đến khi nạp tiền.\n\nGiữ nguyên cơ chế kiểm tra độ tuổi, nội dung thông báo đăng ký, các điều kiện đủ điều kiện, quy trình thanh toán và lịch sử khiếu nại của trang web. Đánh giá từng nhà điều hành một cách riêng biệt. Giữ bí mật mọi bằng chứng liên quan đến trẻ em và che đi các thông tin nhận dạng trong các tài liệu công khai.\n\nMột hồ sơ thi hành pháp luật liên quan là 2026 Thông báo về đơn kiện tại New York đã lưu trữ 2026-09-01 ↗, trong đó cáo buộc rằng các hộp quà có trả phí gây hại cho người dùng trẻ tuổi. Đây không phải là kết luận theo COPPA.\n\nPhần C — Khung pháp lý · Mục 18 · GDPR Điều 15 request\nYêu cầu. Phản hồi. So sánh còn thiếu.\n\nAnh ấy yêu cầu bốn điều, trong đó có bản ghi nhật ký sẽ tiết lộ danh tính của người đã cài đặt khóa API vào tài khoản của anh ấy. Ba ngày sau, vé được đóng lại kèm theo một liên kết dẫn đến một trang không chứa bất kỳ thông tin nào trong số đó — và câu kết thúc bài báo này lại bị chính các luật sư của Valve bác bỏ.\n\nTài khoản này thuộc về ai · Nguồn gốc và giới hạn\n\nNhững ảnh chụp màn hình này không phải của PhishDestroy. Những thông tin này đến từ một người dùng bình thường của Steam — một người tham gia cuộc khảo sát ngắn do dự án này tổ chức, người đã tự mình gửi yêu cầu và cung cấp các ảnh chụp màn hình. Tài khoản là của anh ấy, phiếu yêu cầu là của anh ấy, và các trao đổi diễn ra giữa anh ấy và bộ phận Hỗ trợ của Steam. Dự án này không gửi yêu cầu, không sở hữu tài khoản nào trên nền tảng này và không phải là bên liên quan trong phiếu yêu cầu này.\n\nVào ngày 16 tháng 9 năm 2026, anh đã gửi một yêu cầu truy cập thông tin theo Đạo luật Bảo vệ Quyền riêng tư của California (GDPR/CCPA) 15, trong đó yêu cầu cụ thể về các bản ghi đăng ký khóa API, lịch sử đăng nhập kèm địa chỉ IP, lịch sử ủy quyền thiết bị và lịch sử giao dịch. Vào ngày 17 tháng 9, nhân viên “Logen” đã hướng dẫn anh truy cập trang Dữ liệu Tài khoản tự phục vụ. Vào ngày 18 tháng 9, anh ấy cho biết các danh mục được yêu cầu không có trên trang đó và đề nghị chuyển vụ việc lên Nhóm Bảo mật Dữ liệu hoặc Chuyên viên Bảo vệ Dữ liệu (DPO). Vào ngày 19 tháng 9, nhân viên hỗ trợ \"Kal\" đã đóng phiếu yêu cầu với cùng lời hướng dẫn. Cả hai ảnh chụp màn hình đều được lưu giữ bên dưới (địa chỉ email của người yêu cầu đã được che đi; mã SHA-256 trong steam_tos_assets/screenshot-manifest.json).\n\nAnh ấy là người đề nghị phù hợp vì một lý do rất bình thường: Tài khoản của anh ấy có khóa Web API thuộc loại “Steam” mà anh ấy không tạo ra, được đăng ký dưới tên localhost. Không rõ nó được tạo ra vào thời điểm nào — không phải đối với anh ta, và cũng không phải từ bất kỳ thông tin nào mà Valve đã cung cấp cho anh ta, bởi vì bản ghi duy nhất có thể xác định thời điểm đó chính là nhật ký đăng ký khóa “API” — và đây chính xác là danh mục mà hệ thống đã giấu đi. Khóa này không phải là mới: nó đã tồn tại từ trước khi anh ta biết đến nó một khoảng thời gian mà anh ta không thể đo lường được, cũng vì lý do đó.\n\nCác chủ tài khoản khác cũng đang gửi yêu cầu tương tự. Bất kỳ phản hồi nào nhận được sẽ được bổ sung vào đây theo các điều kiện tương tự như hai trường hợp này — số phiếu yêu cầu, ngày ghi nhận, mã SHA-256,(thông tin người yêu cầu đã được ẩn danh) — bất kể phản hồi đó chấp thuận hay từ chối các danh mục được đề xuất.\n\nDự án này không đưa ra quan điểm nào về lý do tại sao phiếu yêu cầu đã bị đóng. Trong phiếu yêu cầu đó không nêu rõ lý do nào, và ở đây cũng không suy luận ra lý do nào cả.\n\nYêu cầu. Phản hồi. So sánh.THEO DÕI KẾT QUẢ\nBước 3 / 3\n\nÔng ấy đã yêu cầu bốn danh mục cụ thể. Trang “Dữ liệu tài khoản” mà ông được hướng dẫn truy cập là tính năng xuất dữ liệu tự phục vụ của chính Valve, và dự án này không thể liệt kê nội dung của nó cho tài khoản của người khác — do đó, không có so sánh chi tiết theo từng danh mục nào được công bố tại đây. Điều được ghi nhận là tuyên bố của ông vào ngày 18 tháng 9 rằng các danh mục đó không tồn tại, và việc đóng lại yêu cầu vào ngày 19 tháng 9, trong đó chỉ lặp lại việc chuyển hướng mà không giải quyết các danh mục đó.\n\nYÊU CẦUCác danh mục cụ thểAPI- hồ sơ khóa, đăng nhập, thiết bị và giao dịch\nPHẢN HỒITham chiếu dữ liệu tài khoảnKiểm tra việc trao đổi hỗ trợ\nBÀI KIỂM TRAĐã cung cấp những gì?So sánh từng danh mục được yêu cầu\nMàn hình 1/2 — Yêu cầu (16 tháng 9) và câu trả lời đầu tiên, nhân viên hỗ trợ “Logen” (17 tháng 9)\nGDPR Vé HT-2YBP-F7JP-D4VB — Yêu cầu và phản hồi ban đầu\nNguồn: help.steampowered.com, phiếu yêu cầu HT-2YBP-F7JP-D4VB · được ghi lại vào ngày 16–17 tháng 9 năm 2026 · địa chỉ email của người yêu cầu đã được ẩn 2026-09-21 · Tệp: gdpr-ticket-1.png · SHA-256 da940c731ab9869d226e9d06ccc8a1b393738766b7b0c445a56662623e025a66 (screenshot-manifest.json).\nMàn hình 2/2 — Yêu cầu chuyển cấp (18 tháng 9) và việc đóng yêu cầu, nhân viên hỗ trợ “Kal” (19 tháng 9)\nGDPR Phiếu HT-2YBP-F7JP-D4VB — Yêu cầu chuyển lên cấp trên và đóng phiếu\nNguồn: help.steampowered.com, mã vé HT-2YBP-F7JP-D4VB · được ghi lại vào ngày 18–19 tháng 9 năm 2026 · Tệp: gdpr-ticket-2.png · SHA-256 44844ea7b251f7fd7d79f87ee1578a846606a97b9659d3a53b322120c422219b (screenshot-manifest.json).\nPhản hồi cuối cùng, 19 tháng 9 (trích nguyên văn):\n\"Các dữ liệu mà Steam lưu trữ hiện đã có sẵn trên trang Dữ liệu tài khoản của bạn. Do bộ phận Hỗ trợ Steam không thể cung cấp thêm thông tin nào khác, Yêu cầu này sẽ bị đóng.\"\nKhông cung cấp dữ liệu · không nêu rõ cơ sở pháp lý cho việc từ chối · không hiển thị kết quả khi chuyển lên cấp trên\nCâu đó là sai, và chính các luật sư của Valve đã chứng minh điều đó. Thư của luật sư ngày 1 tháng 10 năm 2025,, đoạn 1.9, mô tả mối tương quan ở cấp độ thiết bị liên kết một thiết bị với hàng chục tài khoản (Phụ lục A). Bản trả lời đó kèm theo 830 trang tài liệu lưu trữ (Phụ lục B). Không có thông tin nào trong số đó xuất hiện trên trang Dữ liệu tài khoản.\nTại sao tài khoản này lại yêu cầu tệp nhật ký khóa “API”?\n\nAnh ấy không chọn bốn danh mục đó một cách ngẫu nhiên. Những localhost mã khóa trên tài khoản của anh ấy là dấu hiệu của một đoạn mã, chứ không phải của một người đang nhập tên miền thực vào trang dành cho nhà phát triển (Phần 5, Phần 6). Tài liệu duy nhất cho biết ai là người tạo ra nó và từ đâu chính là nhật ký đăng ký khóa “API”. Đó là điều đầu tiên anh ấy yêu cầu. Và đó cũng chính là thông tin mà cơ quan đóng cửa đã giấu đi.\n\nNguồn: chủ tài khoản, trong quá trình khảo sát của dự án này. Các ảnh chụp màn hình vé ở trên đã được mã hóa băm; trang chứa khóa không được công bố.\n\nĐánh giá · PhishDestroy\n\nViệc đóng một phiếu yêu cầu hỗ trợ trong khi câu hỏi vẫn chưa được giải đáp không phải là một sự cố ngẫu nhiên ở đây. Đó là kết quả bình thường. Chúng tôi luôn 16,319 hồ sơ khiếu nại và hỗ trợ được lưu giữ và 354 các giao dịch hỗ trợ đã loại trừ trùng lặp được trích dẫn từ các nguồn đó. Vé này là một ví dụ cụ thể, được ghi lại đầy đủ về hình thức mà chúng thể hiện.\n\nYêu cầu hỗ trợ — Đã lưu giữHT-2YBP-F7JP-D4VB\nLoại yêu cầuGDPR Bài viết 15 DSAR\nTình trạng véĐà ĐÓNG CỬA 19 THÁNG 9 NĂM 2026 — KHÔNG CÓ DỮ LIỆU ĐƯỢC CUNG CẤP\nCác đại lý trên sàn giao dịch\"Logen\" (17 tháng 9), \"Kal\" (19 tháng 9)\nĐã nộp16 2026 tháng 9\nDữ liệu được yêu cầuAi đã đăng ký khóa Web API liên kết với tài khoản này, và từ địa chỉ IP / thiết bị / dấu thời gian nào?\nCăn cứ pháp lý được viện dẫnGDPR Điều 15 — quyền truy cập dữ liệu cá nhân\nKhung pháp lý:Điều 12 (3) quy định cơ quan kiểm soát có thời hạn một tháng kể từ ngày nhận được (có thể gia hạn nếu có lý do chính đáng). Thời hạn này chưa hết hiệu lực tại thời điểm xuất bản, và hồ sơ này không khẳng định có vi phạm thời hạn. Phản đối này liên quan đến nội dung: văn bản trả lời cuối cùng có liên kết đến một trang tự phục vụ nhưng không cho thấy bốn loại dữ liệu được nêu tên đã được cung cấp, và nếu cơ quan kiểm soát từ chối thực hiện, Điều 12(4) yêu cầu cơ quan này phải nêu rõ lý do và các kênh khiếu nại. Cả hai điều này đều không xuất hiện trong văn bản trả lời cuối cùng.\nTại sao dữ liệu cụ thể này lại quan trọng?\n\nNhật ký sự kiện khóa Web API là bản ghi cho biết liệu có bên thứ ba nào đã đăng ký khóa bằng cách sử dụng cookie phiên bị đánh cắp hay không — cơ chế được mô tả trong các đơn khiếu nại về việc đánh cắp tài sản được lưu giữ trong kho lưu trữ của hồ sơ này. Việc tiết lộ danh tính người đã đăng ký khóa API, từ địa chỉ IP nào và vào thời điểm nào sẽ:\n\nCho phép nạn nhân so sánh địa chỉ IP tạo ra liên kết API với lịch sử đăng nhập của chính họ\nTiết lộ các địa chỉ IP của trung tâm dữ liệu có liên quan đến cơ sở hạ tầng bot lừa đảo / cờ bạc đã được xác định\nCung cấp bằng chứng có thể được sử dụng trong các thủ tục tố tụng dân sự hoặc hình sự đối với người thực hiện hành vi\nHiển thị liệu chủ tài khoản có được thông báo khi khóa được tạo hay không\nTheo hồ sơ ghi nhận: Valve lưu giữ các bản ghi ở cấp độ thiết bị và bản ghi liên quan đến tài khoản — thư của luật sư đại diện cho họ ngày 1 tháng 10 năm 2025 đã mô tả các bản ghi này (xem Phụ lục A, Bản ghi nhớ về bằng chứng — Nguồn 1). Trong phiếu yêu cầu HT-2YBP-F7JP-D4VB, chủ thể dữ liệu đã yêu cầu cùng loại hồ sơ này và phiếu yêu cầu đã được đóng lại với việc chuyển hướng đến một trang tự phục vụ mà theo báo cáo của chủ thể dữ liệu thì không chứa các hồ sơ đó. Việc từ chối đó có hợp pháp hay không là vấn đề thuộc thẩm quyền của cơ quan giám sát; hậu quả là người mà dữ liệu liên quan đến không nhận được thông tin đó.\nCuộc trao đổi — bốn tin nhắn, ba ngày\n\nHai nhân viên hỗ trợ của Steam đã trả lời bằng tên riêng được hiển thị trên phiếu yêu cầu: “Logen” trong phiếu ngày 17 tháng 9 và “Kal” trong phiếu ngày 19 tháng 9. Cả hai đều hướng dẫn người gửi yêu cầu truy cập trang Dữ liệu Tài khoản. Không có thông tin nào trên phiếu yêu cầu cho thấy liệu yêu cầu này có được chuyển đến Nhóm Bảo mật hoặc Cán bộ Bảo vệ Dữ liệu của Valve hay không, và hồ sơ này cũng không nêu rõ danh tính của các nhân viên hỗ trợ, vai trò của họ, cũng như cách thức phiếu yêu cầu được chuyển tiếp.\n\n16 SEP\nĐiều 15: Đơn yêu cầu đã được nộp với bốn danh mục dữ liệu được nêu tên\n17–18 SEP\nTham chiếu đến dữ liệu tài khoản; người yêu cầu đề nghị chuyển lên DPO\n19 SEP\nVé đã được đóng với cùng một mã giới thiệu; không có dữ liệu, không nêu rõ cơ sở\nĐiều 15 GDPR quy định rõ ràng những quyền gì mà đối tượng được hưởng\nĐiều15 (1) (a)Mục đích xử lý — lý do tại sao Valve lưu trữ dữ liệu\nĐiều15 (1)(b)Các loại dữ liệu — những gì được lưu trữ tại Valve\nĐiều15 (1) (c)Người nhận hoặc các nhóm người nhận — người đã nhận dữ liệu (e.g, người nắm giữ khóa API)\nĐiều15 (1) (d)Thời hạn lưu giữ hoặc các tiêu chí để xác định thời hạn đó\nBài viết “15” (3)Một bản sao của dữ liệu cá nhân đang được xử lý — i.e., chính bản ghi nhật ký phím (API)\nBÀI VIẾT:12 (3)Yêu cầu phản hồi trong vòng một tháng kể từ ngày nhận được; việc gia hạn phải được thông báo trong tháng đó. Thời hạn này chưa hết hạn tại thời điểm xuất bản. Điều 12 (4): Nếu cơ quan quản lý không có biện pháp xử lý, cơ quan này phải nêu rõ lý do và hướng dẫn người khiếu nại về các kênh khiếu nại.\nQuy trình khiếu nại về quy định — dành cho mọi người dùng\n\nBất kỳ người dùng nào đã gửi yêu cầu theo Điều 15 GDPR tới Valve mà không nhận được phản hồi tuân thủ (hoặc nhận được mẫu thư từ chối không kèm thông tin) đều có thể nộp đơn khiếu nại lên cơ quan giám sát tại quốc gia thành viên EU/EEA của mình. Đơn vị hoạt động tại EU của Valve là Công ty TNHH Valve tại Hamburg, do đó cơ quan giám sát chủ chốt đối với các khiếu nại xuyên biên giới là Cơ quan Bảo vệ Dữ liệu và Tự do Thông tin của Hamburg (HmbBfDI). (Theo Điều Valve, đại diện của 27 cũng có trụ sở tại Hamburg; địa chỉ của đại diện không tự nó quyết định cơ quan có thẩm quyền.) Khiếu nại cũng có thể được nộp lên cơ quan có thẩm quyền của quốc gia thành viên nơi người khiếu nại cư trú theo Điều 77.\n\nMẫu đơn khiếu nại HmbBfDI ↗ GDPR văn bản (Điều 12, 15, 77) ↗ đã lưu trữ 2026-09-20 ↗Hướng dẫn của EDPB ↗\n\nMã tham chiếu vé cho mọi khiếu nại: HT-2YBP-F7JP-D4VB — được lưu giữ trong hồ sơ này như một trường hợp đã được ghi nhận.\n\nMột trường hợp đã được ghi nhận\nCác hồ sơ đó vẫn còn tồn tại; nhưng chủ thể dữ liệu chưa nhận được chúng.\n\nLuật sư của Valve đã mô tả các hồ sơ tương quan ở cấp độ thiết bị trong một lá thư ngày 1 tháng 10 2025. Vào ngày 19 tháng 9 2026, một yêu cầu theo Điều 15 đối với cùng loại hồ sơ này đã bị đóng lại kèm theo lời hướng dẫn truy cập trang tự phục vụ mà người yêu cầu cho biết không chứa các thông tin đó, mà không nêu rõ cơ sở pháp lý. Phiếu yêu cầu HT-2YBP-F7JP-D4VB là một trường hợp được ghi nhận; liệu điều này có phản ánh một thực tiễn phổ biến hơn hay không là câu hỏi dành cho cơ quan giám sát, cơ quan này có thể yêu cầu Valve cung cấp hồ sơ xử lý vụ việc.\n\nGDPR Các bài viết 12, 15, 77 / Cơ quan giám sát\n\nCó thể nộp đơn khiếu nại theo các Điều 12 và 15 trực tiếp tới cơ quan giám sát có thẩm quyền mà không phải chịu chi phí (Điều 77). Cơ quan này có thể áp dụng các biện pháp khắc phục, bao gồm yêu cầu tuân thủ yêu cầu truy cập, và phạt tiền theo Điều 83(5)(b) đối với các vi phạm quyền của chủ thể dữ liệu. Việc lưu giữ mã tham chiếu vé gốc và bất kỳ phản hồi nào từ Valve (hoặc việc không nhận được phản hồi) sẽ củng cố tính thuyết phục của đơn khiếu nại.\n\nXem mẫu DSAR →\nPhần C — Khung pháp lý · Mục 19 · Luật hợp đồng\nThỏa thuận đăng ký trái với kiến trúc riêng của nền tảng\nBối cảnh và các giới hạn về nguồn\n\nCác tác giả không phải là luật sư và những nội dung này không phải là tư vấn pháp lý. SSA được trích dẫn từ bản sửa đổi của 10 tháng 9 năm 2026; các bản sửa đổi khác có thể có nội dung khác nhau, và cách đánh số điều khoản đã thay đổi qua các bản sửa đổi — hãy đối chiếu điều khoản với phiên bản áp dụng cho hành vi đang được đề cập. Các bài viết 25 và 32 nêu rõ những yêu cầu của quy định, chứ không phải là cơ quan giám sát đã phát hiện vi phạm. Các số liệu trong bài viết 1 nêu rõ các giới hạn phạm vi được quy định tại Mục 13.\n\nBa trong số các quy định cốt lõi của SSA có sự mâu thuẫn với cách thức xây dựng nền tảng này: lệnh cấm sử dụng cho mục đích thương mại kết hợp với mức trần giá trên Thị trường, khiến các giao dịch có giá trị cao bị đẩy ra khỏi nền tảng; điều khoản về trách nhiệm của người dùng đối với các khóa xác thực hai yếu tố (API) mâu thuẫn với điểm cuối khóa (key endpoint) vốn trước khi có quy định về xác thực hai yếu tố (2023,) không yêu cầu yếu tố xác thực thứ hai; và ngôn ngữ quy định về việc thi hành mâu thuẫn với hồ sơ công khai cho thấy không có việc thi hành đối với từng nhà điều hành. Việc những mâu thuẫn này có ảnh hưởng đến khả năng thi hành hay không là vấn đề thuộc thẩm quyền của tòa án; phần này trình bày các sự kiện mà tòa án sẽ xem xét.\n\nThuyết \"1\" / Kiến trúc vốn hóa thị trường\nGiới hạn giá thị trường và quy định cấm sử dụng vào mục đích thương mại\n\nChợ cộng đồng Steam có mức giá niêm yết tối đa khoảng $1,800.. Theo một bản chụp màn hình đã lỗi thời (23 Sep 2026), các danh mục mặt hàng CS2 trên 248 có mức giá được niêm yết độc lập cao hơn mức trần đó tại hai hoặc nhiều sàn giao dịch; những mặt hàng như vậy không thể được bán với mức giá đó trên nền tảng riêng của Valve. Các chủ sở hữu muốn áp dụng mức giá đó sẽ sử dụng các nền tảng giao dịch của bên thứ ba, hoạt động trên các tài khoản Steam và Steam API — lưu ý rằng Cơ quan An sinh Xã hội (SSA) phân loại các nền tảng này là thương mại trừ khi được cho phép rõ ràng.\n\nCác mặt hàng vượt quá mức trần của Thị trường → các thị trường bên thứ ba bù đắp phần chênh lệch → các thị trường này sử dụng tài khoản Steam và Steam API → Cơ quan An sinh Xã hội (SSA) cấm sử dụng thương mại mà không có sự cho phép → chưa có danh sách các trường hợp được phép nào được công bố. Phí tổng hợp của Thị trường Cộng đồng (khoảng 15%) chỉ áp dụng cho các giao dịch được hoàn tất bên trong Thị trường, không áp dụng cho các giao dịch bên ngoài này.\nTham số 2 / Kiến trúc bảo mật khóa API\nLỗ hổng bảo mật liên quan đến khóa (API) là một vấn đề về thiết kế nền tảng chứ không phải do sự bất cẩn của người dùng\n\nTrước đây, điểm cuối tạo khóa API của 2023, Steam đã chấp nhận yêu cầu POST kèm theo một sessionid bị đánh cắp và tạo ra thông tin đăng nhập có đặc quyền cao không có xác nhận qua email, xác thực hai yếu tố hoặc xác thực qua thiết bị. Các khiếu nại về việc chiếm quyền điều khiển API được thu thập trong cuộc điều tra này đều tuân theo một mô hình nhất định: tập lệnh của kẻ tấn công, cookie phiên bị đánh cắp, tạo khóa ẩn, chặn giao dịch (nội dung yêu cầu được trình bày tại Mục 8).\n\nGDPR Điều 25 (bảo vệ dữ liệu ngay từ thiết kế) và Điều 32 (an ninh trong quá trình xử lý) yêu cầu phải áp dụng các biện pháp kỹ thuật phù hợp với mức độ rủi ro. Việc cấp một chứng chỉ có khả năng bị chặn trong quá trình giao dịch mà không có yếu tố xác thực thứ hai hoặc thông báo cho chủ sở hữu là một vấn đề thiết kế thuộc trách nhiệm của người kiểm soát. Việc liệu điều khoản của SSA quy định trách nhiệm cho người dùng có thể được viện dẫn trong bối cảnh đó hay không là vấn đề thuộc thẩm quyền của tòa án và cơ quan giám sát.\n\nTham số 3 / Khả năng hiển thị theo thời gian thực\nValve nhận tên máy chủ xác thực mỗi khi đăng nhập\n\nTên máy chủ xác thực được gửi đến điểm cuối OpenID của Valve dưới dạng văn bản thuần túy trong openid.return_to và openid.realm (Cấu trúc yêu cầu được trình bày tại Mục 3). Việc trích xuất thông tin này là một thao tác tiêu chuẩn. Theo dữ liệu tại 2026-09-22, trong các cặp 26, miền chính nằm trong Bộ lọc liên kết (Link Filter), trong khi máy chủ mang thông tin đăng nhập Steam thì không. Valve chưa công bố bất kỳ bản ghi thực thi nào theo từng nhà mạng, do đó không thể xác định được từ dữ liệu công khai liệu có bất kỳ biện pháp nào khác ngoài Bộ lọc liên kết (Link Filter) đã được áp dụng cho các máy chủ này hay không.\n\nAi sẽ chịu chi phí này?\nMô hình trong các đơn khiếu nại đã được lưu trữ\n\nTrong các khiếu nại được xem xét, phản hồi của Bộ phận Hỗ trợ Steam đối với cáo buộc chiếm đoạt khóa APIluôn tuân theo một khuôn mẫu: từ chối khôi phục, nêu rõ trách nhiệm của người dùng đối với tài khoản và khóa API, sau đó đóng phiếu yêu cầu. Hồ sơ này không đưa ra ước tính về số lượng tài khoản bị ảnh hưởng hay giá trị bị mất; cũng không tìm thấy nguồn nào cung cấp con số này.\n\nVấn đề không phải là liệu các người dùng cá nhân có mắc lỗi hay không. Vấn đề là ai phải chịu trách nhiệm về một kiến trúc mà, cho đến khi 2023, cho phép một yêu cầu POST sử dụng cookie bị đánh cắp để tạo ra thông tin đăng nhập giao dịch có quyền truy cập cao mà không có bất kỳ thông báo nào và không yêu cầu xác thực hai yếu tố.\nSSA với tư cách là một văn bản so với SSA với tư cách là một hợp đồng\nMột tòa án xem xét hồ sơ này sẽ không diễn giải Đạo luật An sinh Xã hội (SSA) một cách tách biệt.\n\nHọ sẽ xem xét tài liệu này cùng với lá thư ngày 10 tháng 2025 của luật sư, trong đó mô tả mối tương quan ở cấp độ thiết bị, các ngày đăng ký máy chủ xác thực, các dấu thời gian đăng ký theo lô, nội dung yêu cầu khóa API, cũng như khoảng thời gian mười năm giữa các thông báo tháng 7 2016 và các nền tảng vẫn đang hoạt động vào tháng 9 2026.. Đó chính là hồ sơ mà Valve sẽ phải giải quyết.\n\nSSA so với hồ sơ / những điểm chính\n\"Không được sử dụng cho mục đích thương mại\" — Giới hạn của Thị trường khiến các giao dịch có giá trị cao phải chuyển sang các thị trường thương mại của bên thứ ba\n\"Người dùng phải chịu trách nhiệm về các khóa API\" — không có xác thực hai yếu tố trên điểm cuối khóa trước khi truy cập 2023\n\"Chúng tôi xử lý nghiêm các trường hợp vi phạm\" — không có hồ sơ xử lý vi phạm theo từng nhà khai thác nào được công bố kể từ tháng 7 năm 2016\n\"Bạn đã đồng ý với các điều khoản\" — trong mô hình chiếm quyền điều khiển, việc chấp nhận được thực hiện bởi một tập lệnh, chứ không phải chủ tài khoản\nKết luận · Những gì hồ sơ đã chứng minh và những gì chúng tôi yêu cầu\nCác kết quả. Các tài liệu mà chúng tôi yêu cầu.\nBối cảnh và các giới hạn về nguồn\n\nMỗi phát hiện dưới đây đều liên quan đến một hồ sơ công khai có ghi rõ ngày tháng trong các phần trên. Các yêu cầu này được gửi đến các cơ quan có thẩm quyền, những cơ quan có thể buộc phải cung cấp thứ duy nhất mà cuộc điều tra này không thể tiếp cận được: chính các hồ sơ về việc thi hành, truy cập và xử lý dữ liệu của Valve.\n\nMỗi yêu cầu đều dựa trên một kết luận đã được ghi ngày tháng. Các cơ quan chức năng có thể yêu cầu cung cấp các tài liệu mà cuộc điều tra dựa trên nguồn công khai này không thể buộc phải cung cấp.\n\nNhững gì hồ sơ công khai đã xác nhận\n44 Các nền tảng trực tuyến xác thực thông qua một tên miền riêng biệt có thể đăng ký — 27 với tệp bằng chứng được công bố theo từng tuyến đường, 17 được thu thập thủ công và liệt kê riêng biệt. Tính đến thời điểm 2026-09-22,, các cặp 26 đã bị chặn tên miền chính trong Bộ lọc liên kết Steam, trong khi máy chủ chứa thông tin đăng nhập của chúng thì không — csgogem.com bị chặn, api.csgem.com đã đăng ký từ tháng 3 năm 2014. Steam nhận được tên máy chủ đó trong openid.realm và openid.return_to mỗi khi đăng nhập. Phần 3\nVào ngày 13 tháng 7 năm 2016 Valve, cơ quan này đã công khai nêu tên cơ chế này và cấm áp dụng nó; đồng thời, các thông báo của luật sư đại diện cho cơ quan này tại 20 tháng 7 năm 2016 đã đặt ra thời hạn mười ngày. Trong mười năm kể từ thời hạn đó, chưa có hồ sơ thi hành nào đối với từng nhà khai thác được công bố. Phần 11\nĐiểm cuối chính của Web API thuộc Dự án Nghiên cứu Bảo mật (Steam) đã cấp một thông tin xác thực có quyền truy cập cao và có thể thực hiện giao dịch chỉ dựa trên một cookie phiên, mà không có yếu tố xác thực thứ hai trước khi truy cập 2023. Phần 5\nMột yêu cầu trên GDPR 15 (mã phiếu HT-2YBP-F7JP-D4VB) đã được đóng sau ba ngày kèm theo một liên kết đến dịch vụ tự phục vụ và không có dữ liệu nào. Phần 18\nĐiều chúng tôi yêu cầu mỗi cơ quan chức năng\nỦy ban Cờ bạc Tiểu bang Washington\nMở lại tệp “2016”. Yêu cầu cung cấp danh sách chi tiết theo từng nhà điều hành về các tài khoản, bot và máy chủ trả về nào đã bị vô hiệu hóa sau khi nhận được thông báo 10 ngày, cũng như những nhà điều hành nào sau đó đã lấy lại quyền truy cập. Phần 2\nHmbBfDI (Hamburg; Công ty TNHH Valve)\nKiểm tra xem phản hồi tại Điều 15 có đáp ứng nghĩa vụ của cơ quan quản lý hay không, và yêu cầu công bố các hồ sơ đăng ký và truy cập khóa APIcó liên quan đến việc xác định danh tính của chủ thể thực hiện hành vi. Phần 18\nCác điều phối viên dịch vụ kỹ thuật số của DSA\nGhi chú về định tuyến máy chủ xác thực (auth-host) vào hồ sơ dưới dạng thông báo, sau đó đánh giá xem phản hồi từ Valve có đáp ứng các nghĩa vụ của mình hay không sau khi thông tin đã được ghi chép lại. Phần 16\nBất kỳ chủ thể dữ liệu nào\nHãy sử dụng mẫu bài viết “15” để yêu cầu các bản ghi tương tự cho tài khoản của bạn; bản ghi được lưu giữ có thể giúp xác định ai là người đã khởi tạo thao tác đặt lại hoặc tạo khóa. Phụ lục G\n\nYêu cầu duy nhất đằng sau cả bốn trường hợp này đều giống nhau: công bố các hồ sơ về việc thi hành, truy cập và xử lý dữ liệu mà chỉ Valve mới nắm giữ. Một cảnh báo trên trang chủ, một thư thông báo 10 ngày và một trang tự phục vụ đều là những hành động thể hiện quyền kiểm soát. Việc quyền kiểm soát đó có được thực thi hay không là câu hỏi mà hồ sơ công khai không thể trả lời, nhưng cơ quan quản lý thì có thể.\n\nPhụ lục — các tài liệu chứng cứ chính và tài liệu làm việc\nPhụ lục A — Thư từ của luật sư\nBản tóm tắt bằng chứng — tài liệu do Nguồn cung cấp 1\n\nCơ sở bằng chứng và tình trạng nguồn của các thư từ trao đổi giữa các luật sư được trích dẫn tại các mục 1,, 18 và 19.\n\nCơ sở bằng chứng và tình trạng nguồn — các tài liệu do Nguồn cung cấp 1\nNgười dùng mà lệnh cấm vĩnh viễn của họ đã dẫn đến cuộc kiểm tra này không phải là đối tượng của cuộc kiểm tra. Việc lệnh cấm đó có hợp lý hay không không được xem xét ở đây, và hồ sơ này không bảo vệ cũng không phản bác điều đó. Tài khoản đó không phải là vấn đề chính. Điều quan trọng là nội dung: Nguồn 1 — chủ tài khoản bị khóa, người đã nhận được thư từ dưới đây từ luật sư của Valve với tư cách là chủ thể dữ liệu trong yêu cầu theo Điều GDPR của chính mình — đã chuyển tiếp thư từ đó cùng các hồ sơ vụ việc kèm theo, kèm theo quyền cho phép công khai xem xét các tài liệu này. Tên của người này được giấu kín; các tài liệu được mô tả theo ngày tháng, siêu dữ liệu của tác giả và mã băm.\n\nThư từ đó được gửi để trả lời yêu cầu theo Đạo luật Quyền Truy cập Thông tin (GDPR) / Yêu cầu Tiết lộ Thông tin An ninh (DSAR). Trong quá trình đó, luật sư của Công ty Phần mềm Máy tính (Valve) đã đưa ra một tuyên bố có chữ ký, trong đó mô tả một tính năng mà Bộ phận Hỗ trợ Dịch vụ Mạng (Steam Support) trước đó đã thông báo với người dùng là không thể thực hiện được về mặt kỹ thuật. Đoạn trích dẫn dưới đây chính là tuyên bố đó.\n\nPhân tích sâu hơn của các tác giả về đoạn trích nhật ký đã thu được là không được đưa vào hồ sơ này đang chờ kết quả đánh giá độc lập. Không có phần nào khác trong cuộc điều tra này dựa vào kết quả này.\n\nThông tin được ghi nhận trong hồ sơ: dữ liệu đo từ xa liên tục ở cấp độ thiết bị\n\nTrong đoạn 1.9 của bức thư được cho là do luật sư của Valve gửi, các luật sư của Valve nêu rõ: \"Theo thông tin từ 2019 và 2023,, tài khoản này chủ yếu được sử dụng từ một thiết bị cũng đã được dùng để đăng nhập vào hàng chục tài khoản Steam bị đánh cắp.\"\n\nSự thật: Luật sư của Valve tại đây mô tả việc đối chiếu dữ liệu ở cấp độ thiết bị giữa các tài khoản trong khoảng thời gian bốn năm. Steam Bộ phận hỗ trợ đã thông báo với các nạn nhân bị trộm cắp rằng việc theo dõi các mặt hàng bị đánh cắp hoặc liên kết các tài khoản với thiết bị là không thể thực hiện được về mặt kỹ thuật. Steam Quy trình ủy quyền thiết bị của Guard đã được công khai ghi chép, do đó việc tồn tại các bản ghi theo từng thiết bị không phải là điều mới; điều mới là xác nhận bằng văn bản của luật sư rằng các bản ghi đó được lưu giữ và liên kết giữa các tài khoản trong khoảng thời gian nhiều năm.\n\nTại sao điều này lại quan trọng: Mối tương quan có thể liên kết một thiết bị với hàng chục tài khoản bị chiếm quyền kiểm soát trong vòng bốn năm thuộc cùng loại hồ sơ mà cơ quan hỗ trợ cho biết họ không thể sử dụng để hỗ trợ các nạn nhân. Các loại hồ sơ đó có khả năng xác định các tài khoản và thiết bị trong chuỗi hành vi trộm cắp và bán lại. Những hồ sơ nào tồn tại, thời gian lưu trữ là bao lâu và trên cơ sở nào chúng bị từ chối cung cấp cho chủ thể dữ liệu là những câu hỏi dành cho cơ quan giám sát.\n\nNguồn: Thư của luật sư đại diện cho Valve ngày 1 tháng 10 năm 2025,, đoạn 1.9, và phụ lục PDF tại trang 830-· được Nguồn 1 nhận được để đáp lại yêu cầu theo Điều GDPR, Mục 15 · Mã SHA-256 của phụ lục được ghi lại tại disclosure-audit.json · Nội dung bức thư không được trích dẫn; tên tài khoản và dữ liệu của bên thứ ba đã được loại bỏ.\n\nTrạng thái: mở\nCác tài liệu nguồn có thể truy cập qua kho lưu trữ bằng chứng.\nPhụ lục B — Tệp PDF đã tạo · Kiểm tra việc che giấu thông tin\nViệc che giấu trong tệp PDF được tạo ra chỉ mang tính hình thức: phần văn bản bị che vẫn có thể trích xuất được\n\nLuật sư của Valve đã trả lời yêu cầu tiếp cận thông tin theo Đạo luật Tự do Thông tin (GDPR) bằng cách đính kèm một trang từ trang web 830-, trong đó các phần bị che giấu được tô đè lên văn bản thay vì xóa bỏ chúng. 902,270 các ký tự nằm dưới các thanh màu đen và được trích xuất trực tiếp bằng công cụ trích xuất văn bản — bao gồm cả các mã định danh của bên thứ ba mà các thanh ngang được thiết kế để che giấu. Tại đây chỉ công bố số liệu tổng hợp; không sao chép bất kỳ nội dung được bảo vệ nào, và bản thân phụ lục cũng không được công bố.\n\n1. Kết quả kiểm tra hình học cho thấy\n\nBài viết “GDPR” trên trang 15, ngày 1 Tháng 10 năm 2025 đi kèm với một phụ lục PDF gồm 830-trang (Aspose.PDF chứa thông tin siêu dữ liệu của nhà xuất bản .NET, được tạo và sửa đổi vào cùng ngày). Các tác giả đã tiến hành kiểm tra hình học ở cấp độ trang: đối với mỗi trang, các hình chữ nhật mờ gần như màu đen được vẽ sau lớp văn bản đã được xác định vị trí và các ký tự có thể trích xuất nằm bên dưới chúng đã được đếm.\n\nĐược đo trên tệp đã tạo\n902,270\nCác ký tự vẫn có thể trích xuất được từ dưới các thanh màu đen\nĐược thống kê, không phải ước tính. Đây là số liệu thống kê về các nhân vật được đề cập — không phải số nạn nhân, số trường hợp xác định lại danh tính hay số vụ việc.\n830 / 830\nCác trang bị ảnh hưởng — mọi trang\n986\nHình chữ nhật bao phủ văn bản có thể trích xuất\n1,329\nTổng số hình chữ nhật màu đen đục\nCác thanh màu đen được vẽ chồng lên lớp văn bản; chúng không xóa bỏ lớp văn bản đó. Văn bản nằm dưới các thanh này có thể được trích xuất bằng các công cụ PDF tiêu chuẩn. Chỉ số liệu tổng hợp mới được công bố; nội dung bị che khuất không được sao chép lại tại đây.\nThí nghiệm pháp y: Tách lớp\nASPOSE.PDF MẪU THIẾT KẾ LỚP PHỦ VECTOR CHO “.NET” (PHỤ LỤC P. 412)\n\nĐơn khiếu nại được nộp đối với tài khoản: [Đăng nhập: redacted_user_667]\n\nLý do do người dùng đưa ra: [NỘI DUNG: \"Người dùng báo cáo có các mặt hàng trùng lặp trong kho và hành vi giao dịch vi phạm quy định...\"]\n\nPhần nền trước: <path fill=\"#000\" />Lỗi: Dòng dữ liệu UTF-8 cơ bản vẫn nguyên vẹn\nNguồn: Phụ lục PDF kèm theo thư tư vấn của 1 ngày 2025 (830 trang, Aspose.PDF để xem thông tin siêu dữ liệu của nhà sản xuất .NET) · được các tác giả đo lường, phương pháp và số liệu tính theo trang trong disclosure-audit.json · Mã SHA-256 của phụ lục được ghi trong cùng một tệp · bản thân phụ lục không được công bố.\n2. Tại sao điều này lại quan trọng đối với phản hồi của chủ thể dữ liệu\n\nLuật sư của Valve đã gửi tệp tin này cho chủ thể dữ liệu nhằm đáp ứng yêu cầu cung cấp hồ sơ cá nhân của người đó. Các vạch che trên đó chỉ mang tính hình thức: văn bản bên dưới chưa bao giờ bị xóa, do đó các thông tin nhận dạng của bên thứ ba mà các vạch che này nhằm che giấu vẫn được gửi đến người nhận cùng với tệp tin. Việc che giấu thông tin mà có thể bị loại bỏ bằng công cụ trích xuất văn bản sẽ không che giấu được gì, đồng thời cũng khiến người nhận không thể xác định được thông tin nào đã bị tiết lộ và thông tin nào chưa.\n\nĐiều 15 (4) chính là lý do tồn tại của những giới hạn đó: quyền được cung cấp bản sao không được xâm phạm đến các quyền và tự do của người khác. Đó chính là nghĩa vụ mà tác phẩm này đã không tuân thủ. Việc liệu sự việc này có được coi là vi phạm dữ liệu cá nhân theo Điều 4(12) hay không là do cơ quan giám sát quyết định; việc tiết lộ dữ liệu có thể đo lường được trong tệp và có thể tái tạo bởi bất kỳ ai sở hữu cùng các byte đó — mã SHA-256 đã được công bố, nhưng phụ lục thì không.\n\nNhững gì nằm dưới các thanh đó không phải là số tài khoản. Đó là nội dung các báo cáo của người dùng được gửi chống lại người yêu cầu, kèm theo thông tin về tác giả của chúng: các tài khoản đăng nhập Steam — do một tài khoản đăng nhập hiếm khi chỉ được sử dụng trên Steam — nên đã giúp xác định danh tính của người đứng sau chúng — Theo thống kê của các tác giả, hơn 60% số người dùng được nêu tên trong tài liệu này có thể được xác định danh tính một cách đầy đủ — kèm theo bản văn bản gốc, chưa được chỉnh sửa của những gì họ đã viết. Nội dung đó bao gồm những lời chúc chết chóc và những lời lăng mạ nhắm vào quốc tịch của người yêu cầu. Một số người được xác định danh tính như vậy là trẻ vị thành niên. Đơn vị sản xuất đã trao danh sách các phóng viên được nêu tên cho người mà họ đã đưa tin, đó chính là tác hại cụ thể mà Điều 15 (4) được ban hành nhằm ngăn chặn.\n\nTrình tự các ký tự trong tệp cũng quan trọng không kém nội dung của nó. Yêu cầu này ban đầu vấp phải yêu cầu cung cấp thêm bằng chứng xác minh danh tính, với lý do địa chỉ email bí danh của người yêu cầu không chứa tên của anh ta; tài khoản này đã bị khóa vĩnh viễn trong thời gian trì hoãn sau đó. Bức thư cuối cùng cung cấp dữ liệu, hơn sáu tuần sau thời hạn quy định tại Điều 12(3), đã đe dọa người nhận sẽ bị truy tố hình sự và giữ lại phần dữ liệu còn lại của chính anh ta cho đến khi anh ta giải thích hoạt động tài khoản của mình với luật sư. Việc tiết lộ này cũng giải đáp hai câu hỏi mà Valve chưa từng trả lời công khai: các hồ sơ được cung cấp cho thấy việc liên kết tài khoản đã diễn ra từ rất lâu trước đây 2019, và dữ liệu theo dõi nội bộ với mức độ chi tiết Valve mà trước đây chưa từng được mô tả.\n\nPhạm vi của phần này: Phân tích ở đây chỉ giới hạn trong cơ chế biên tập, được đánh giá dựa trên tệp tin đã được tạo ra. Phân tích sâu hơn của các tác giả về các bản ghi đã tạo ra sẽ được giữ lại cho đến khi có kết quả đánh giá độc lập và không được sử dụng làm cơ sở cho bất kỳ phần nào khác trong hồ sơ này.\n\nBằng chứng: Thư của luật sư ngày 1 tháng 10 năm 2025 và phụ lục PDF kèm theo (SHA-256 được lưu trong hồ sơ kiểm toán); Các phép đo và phương pháp đối với tệp PDF ở cấp độ trang ↗. Trình tự của yêu cầu, việc từ chối trang8 và mô tả chi tiết về các bản ghi bị rò rỉ được trình bày đầy đủ trong bản tường trình của PhishDestroy, “Chú chó của tôi đối đầu với các luật sư hàng đầu về vụ ‘GDPR’”, 17 tháng 8 năm 2026 ↗ đã lưu trữ 2026-08-21 ↗. Tên tài khoản và dữ liệu của bên thứ ba đã được bỏ qua ở đây; không có thông tin nào nằm trong phạm vi các thanh này được trích dẫn.\n\nPage 8 of the covering letter refuses part of the request, and states the reason in writing: Eine genauere Auskunft ist aufgrund des Schutzes der personenbezogenen Daten anderer Nutzer der Steam-Plattform… nicht möglich. — a more detailed answer is not possible, because the personal data of other Steam users must be protected. The 830-page appendix was in the same package. What the bars covered was not account numbers: it was the reports filed against the requester, their authors named, with the raw unredacted messages attached. The account holder had asked Valve, through its counsel, for his own file; what he could extract from it was other people's. Nothing in this appendix turns on who drew the boxes. What it establishes is that the protection Valve invoked as its ground for withholding is the protection this same production failed, in the same envelope, on the same day.\nTài liệu chứng cứ liên quan đến hỗ trợ và trao đổi pháp lý\n\nNguồn: https://phishdestroy.io/steam_dossier/vi/index#exhibit-gallery-section\n\nPhụ lục D — Thu thập nguồn\nCác tài liệu gốc được lựa chọn\n\nSáu tài liệu từ kho lưu trữ — ba bài đăng trên diễn đàn “GitHub” trong hệ thống theo dõi của Valve và ba bài đăng trên Reddit về các kết quả hỗ trợ đang gây tranh cãi. Mỗi nguồn đều được đính kèm với tuyên bố liên quan, nội dung văn bản đã lưu và vấn đề mà nó đặt ra.\n\n1 / 6 các bản ghi đã chọn\nChọn một bản ghi nguồn\nGH-01 / GITHUBOpen in saved build\nHardware keys, requested in 2016\n\nValveSoftware / steam-for-linux · #4521 · 2016-06-27\n\nA user asked Valve to support U2F hardware keys as an alternative second factor. The saved issue carries both Feature Request and reviewed labels, with its state recorded as open.\n\nI request U2F usb dongle support in steam as an alternative.\n\nExcerpt from the GitHub issue ↗\nDocumented record\nA dated request for an additional account safeguard, published in Valve's own issue tracker and labelled reviewed.\nAccountability demand\nPublish the product decision, the response date and the protection delivered after review.\nRead saved record →Open GitHub ↗\nIn the dossier: Account safeguards →Archive #484 · build 2026-09-17\nGH-02 / GITHUBOpen in saved build\nCrash reports without an effective opt-out\n\nValveSoftware / steam-for-linux · #6459 · 2019-08-18\n\nThe reporter describes a Steam client from 12 August 2019 on Ubuntu 16. They say disabling the crash-upload destination did not persist after a restart, and include the relevant configuration.\n\nIf I disable the `ServerURL`, it gets overwritten after every reboot.\n\nExcerpt from the GitHub issue ↗ archived 2026-04-19 ↗\nDocumented record\nA specific privacy complaint with a client date, operating system and configuration excerpt. The saved issue is open.\nAccountability demand\nIdentify the investigation, the affected builds and the change that made the opt-out effective.\nRead saved record →Open GitHub ↗archived 2026-04-19 ↗\nIn the dossier: Request the underlying records →Archive #467 · build 2026-09-17\nGH-03 / GITHUBOpen in saved build\nAuth-ticket abuse reported to Valve\n\nValveSoftware / Source-1-Games · #3857 · 2022-02-26\n\nThe author alleges that a server operation retained Steam authentication tickets after players disconnected and used misleading server listings. The post asks Valve to address the behavior.\n\nMaking their servers look packed.\n\nExcerpt from the GitHub issue ↗\nDocumented record\nA public abuse report lodged in Valve's tracker on 26 February 2022. Its saved state is open; the report includes links to screenshots.\nAccountability demand\nProduce the investigation result and the mitigation record for the reported authentication-ticket abuse.\nRead saved record →Open GitHub ↗\nIn the dossier: Dataset scope →Archive #768 · build 2026-09-17\nRD-01 / REDDITAuthor's account\n44 disputed Market purchases\n\nr/DotA2 · author handle withheld · 2022-07-07\n\nThe author reports 44 unauthorized Market purchases on 6 July 2022 and roughly $500+ in losses. They say two-factor authentication was enabled and describe repeated template replies from support.\n\n2nd ticket in and I have still yet to receive a non robotic copy paste template response from Steam.\n\nExcerpt from the Reddit post ↗ archived 2025-03-20 ↗\nDocumented record\nA dated account of disputed purchases, with links to transaction screenshots and a support response. The amounts and events are the author's report.\nAccountability demand\nReconcile the disputed purchases with transaction and session logs. Explain the evidence behind support's decision.\nRead saved record →Open Reddit ↗archived 2025-03-20 ↗\nIn the dossier: Support and enforcement →Archive #4,533 · build 2026-09-17\nRD-02 / REDDITAuthor's account\nA permanent ban and closed appeals\n\nr/ohnePixel · author handle withheld · 2024-12-09\n\nThe author disputes a permanent ban and says support cited suspected account transfer and community reports. They describe closed tickets and plans to request their personal data.\n\nI explained my situation and asked for more details, but they're sticking to their decision and closing my tickets.\n\nExcerpt from the Reddit post ↗\nDocumented record\nA preserved appeal account, including the reasons the author says support supplied and links to four images. The post date comes from the selected support export.\nAccountability demand\nIdentify the evidence supporting the permanent ban and the review available to challenge it. Closing an appeal does not explain the decision.\nRead saved record →Open Reddit ↗\nIn the dossier: Request the underlying records →Archive #4,766 · build 2026-09-17\nRD-03 / REDDITAuthor's account\nA recovery reset and a reported $10,000 loss\n\nr/legaladvice · author handle withheld · 2025-05-09\n\nThe author alleges that support reset credentials and disabled account protections after someone else submitted a recovery ticket. They report a loss of about US$10,000 from an inactive account.\n\nSteam Support reset my password and turned off all my account security.\n\nExcerpt from the Reddit post ↗\nDocumented record\nA preserved allegation about the recovery process overriding account safeguards. The saved post records what the author says support told them.\nAccountability demand\nIdentify who authorised the reset, the ownership evidence they accepted and the access log. Account recovery is part of the security system Valve controls.\nRead saved record →Open Reddit ↗\nIn the dossier: Request the underlying records →Archive #4,592 · build 2026-09-17\n\nSáu bản ghi đã được chọn. Các trạng thái “GitHub” mô tả bản dựng đã được lưu. Các bài đăng trên Reddit lưu giữ thông tin tài khoản của tác giả.\n\nTải xuống sáu bản ghi ↓\n\nBản dựng có thể tìm kiếm này chứa 16,319 các bản ghi riêng biệt: 393 Trustpilot, 5,635 Reddit, 2,395 GitHub, 276 web và 7,620 các bản ghi trên wiki. Nhiều bản ghi có thể liên quan đến cùng một sự kiện. Tệp xuất dữ liệu hàng riêng lẻ từ 40,448-có phạm vi khác.\n\nTìm kiếm trong toàn bộ kho lưu trữ ↗ · Tạo tệp manifest ↗ · Phạm vi và số lượng bộ dữ liệu →\n\nPhụ lục E — Nghiên cứu điển hình\nArchiSteamFarm và điều khoản tự động hóa\n\nMột công cụ “card-farming” mã nguồn mở, trong phần Câu hỏi thường gặp (FAQ) của chính công cụ này cho biết nó đang hoạt động trên hàng triệu tài khoản, trái ngược với điều khoản trong Thỏa thuận người đăng ký (§ 4.C) cấm việc tự động hóa. Các cơ chế — những gì một trang trại phải mua từ Valve trước khi có thể tạo ra bất kỳ thứ gì, lý do tại sao mọi cách rút tiền từ thẻ đều vi phạm giấy phép, hồ sơ thực thi và ai là người điều tiết nền kinh tế thẻ — được trình bày đầy đủ trong Phụ lục V ↗.\n\nThỏa thuận đăng ký của Hiệp hội Truyền thông Độc lập (Steam), Điều 4.C, quy định như sau:\n\n\"Bạn không được sử dụng bất kỳ hình thức kịch bản, bot, macro hoặc các hệ thống khác không do con người điều khiển ('Tự động hóa') để tương tác với Nội dung và Dịch vụ trên Steam dưới bất kỳ hình thức nào.\" — Steam Thỏa thuận người đăng ký § 4.C (phiên bản hiện hành) ↗ đã lưu trữ 2026-09-18 ↗\n\nValve thực thi điều khoản này. Nó làm việc này rất tốt. Câu hỏi thường gặp về ArchiSteamFarm (ASF) — một công cụ mã nguồn mở mà chính tài liệu hướng dẫn của nó mô tả là chạy trên hơn vài triệu tài khoản Steam Kể từ lần phát hành đầu tiên trên 11 cách đây nhiều năm — bài viết này trích dẫn ba thông báo hỗ trợ từ Steam về việc vĩnh viễn cấm các tài khoản đã vận hành mạng lưới bot. Valve đã phát hiện ra các mạng lưới này, nêu tên chúng và vô hiệu hóa chúng. Do đó, câu hỏi quan trọng ở đây không phải là liệu Valve có thể phát hiện hoạt động tự động hóa trên quy mô lớn hay không.\n\nTrang chính thức của dự án Câu hỏi thường gặp về ArchiSteamFarm đề cập trực tiếp đến nguy cơ bị cấm:\n\n\"Điều này cực kỳ khó xảy ra nếu xét đến thực tế là ASF đang được sử dụng trên hơn vài triệu tài khoản Steam kể từ khi phiên bản đầu tiên của nó được phát hành cách đây hơn 11 năm — nhưng vẫn là một khả năng, bất kể xác suất thực tế là bao nhiêu.\"\n\n\"Valve đã thừa nhận rõ ràng sự tồn tại của 'Steam idlers', như đã nêu ở đây, nên nếu bạn hỏi tôi, tôi khá chắc rằng nếu họ không chấp nhận điều đó, họ đã có hành động từ lâu rồi, thay vì chỉ ra rằng những hành vi đó có thể gây ra vấn đề liên quan đến VAC.\" Từ khóa ở đây là các trang web “Steam” dạng idler, ví dụ như ASF, chứ không phải các trang web idler về trò chơi.\"\n\n— Câu hỏi thường gặp về ArchiSteamFarm, JustArchiNET. Nguồn: Trang wiki về GitHub ↗ · Đã xác minh nguyên văn 2026-09-22\n\nCâu trả lời trong phần Câu hỏi thường gặp (FAQ) cho câu hỏi “Có ai bị cấm vì điều đó không?” là Đúng vậy, và trích dẫn lại nội dung mà bộ phận hỗ trợ của Steam đã gửi cho ba người trong số họ:\n\n1,000+ bot · bị cấm giao dịch\n\"Có vẻ như tài khoản này đã được sử dụng để quản lý một mạng lưới các tài khoản bot. Việc sử dụng bot vi phạm Thỏa thuận người dùng của Steam.\"\n\n170+ bot · bị cấm vĩnh viễn, Chương trình giảm giá mùa đông của2017\n\"Tài khoản này đã được sử dụng để thu thập trái phép các thẻ sưu tập trên Steam, cũng như các hoạt động liên quan và không chỉ giới hạn ở các hoạt động thương mại. Tài khoản này đã bị khóa vĩnh viễn và bộ phận Hỗ trợ của Steam không thể cung cấp thêm sự hỗ trợ nào về vấn đề này.\"\n\n120+ bot · bị cấm vĩnh viễn\n\"Tài khoản này cùng với các tài khoản khác đã được sử dụng để tấn công làm quá tải hạ tầng mạng của chúng tôi, đây là hành vi vi phạm Quy tắc ứng xử trực tuyến của Hiệp hội Bóng chày Quốc gia (Steam).\"\n\n— Các tin nhắn hỗ trợ từ Steam được trích dẫn trong phần Câu hỏi thường gặp (FAQ) của ArchiSteamFarm, mục “Có ai bị cấm vì lý do đó không?”. Nguồn ↗ · Đã xác minh nguyên văn 2026-09-22\n\nĐặt hai bản ghi cạnh nhau. Một người dùng cá nhân sử dụng bot khai thác 1,000 đã bị phát hiện, được thông báo rằng “việc sử dụng bot là hành vi vi phạm Thỏa thuận Người dùng của Steam” và bị xóa vĩnh viễn. Các nền tảng thương mại trong hồ sơ này vận hành các tài khoản tự động Steam như hoạt động kinh doanh cốt lõi của họ, với quy mô lớn hơn nhiều, và xác thực thông qua OpenID riêng của Valve mỗi khi đăng nhập — và chưa có bất kỳ hồ sơ xử lý nào theo từng nhà điều hành được công bố đối với bất kỳ nền tảng nào trong số đó. Điều khoản đó có hiệu lực. Vấn đề là nó nhắm vào ai.\n\nASF không bị cáo buộc bất cứ điều gì ở đây, và cách hiểu của ASF về quan điểm của Valve là của riêng họ — tác giả bài viết đã nêu rõ rằng “ASF không được Valve ủy quyền”. Công cụ này được sử dụng ở đây như một phương tiện đo lường: nó cho thấy rằng Valve phát hiện các mạng bot, nêu tên chúng bằng văn bản và cấm vĩnh viễn. Valve có thể giải quyết vấn đề chỉ bằng một câu bằng cách công bố các công cụ tự động hóa thương mại nào mà họ cho phép, cùng với hồ sơ chi tiết theo từng nhà cung cấp về các biện pháp đã thực hiện đối với phần còn lại.\n\nTác động của việc “farm thẻ” đối với doanh thu củValve\n\nThẻ sưu tập thu được từ việc “farm” được bán trên Chợ Cộng đồng của Steam, nơi thu một khoản phí tổng cộng khoảng 15% cho mỗi giao dịch hoàn tất trong Chợ; tài khoản phải đã chi tiêu $5.00 USD trên Steam trước khi có thể nhận được bất kỳ thẻ nào; và việc nhận thẻ yêu cầu phải sở hữu trò chơi hoặc thực hiện các giao dịch mua trong trò chơi. Không có con số doanh thu tổng hợp nào được ước tính ở đây — quy mô hoạt động chỉ được nêu theo như phần Câu hỏi thường gặp (FAQ) của ASF. Phần FAQ này cũng ghi nhận Valve để phân biệt \"Những người lười biếng ởSteam\" (cày thẻ) từ \"những người chơi game không làm gì cả\"; xem Câu hỏi thường gặp về ASF ↗. Các cơ chế được trình bày đầy đủ trong Phụ lục V — Thang đo và bẫy dành cho mục đích thương mại.\n\nChủ đềArchiSteamFarm — hệ thống canh tác thẻ tự động\nTỷ lệ quy địnhHàng triệu tài khoản (theo phần Câu hỏi thường gặp của ASF — số lượng tài khoản đang hoạt động chính xác chưa được xác minh)\nĐược đếm, không phải được trích dẫn10,880,610 Tổng cộng có API bài đăng trong nhóm Steam của chính ASF (5,360,499 không giới hạn, như Steam hiển thị) — con số “hàng triệu” trong phần Câu hỏi thường gặp (FAQ) không phải là một câu chuyện, mà là số lượng thành viên. Các bài đăng tại 88.97% không bị áp dụng bất kỳ hình thức cấm nào từ Steam. Bảng thống kê đầy đủ về lệnh cấm ↗\nCác thông tin được công bố trong tài liệu hướng dẫn của chính công cụ này\nASF đăng nhập vào các tài khoản ở chế độ không giao diện và để các trò chơi ở trạng thái chờ để nhận thẻ mà không cần khởi chạy ứng dụng khách Steam (theo tài liệu dự án).\nPhần Câu hỏi thường gặp (FAQ) giải thích rằng Valve đã biết về “những người lười biếng trênSteam” và rằng “nếu họ không chấp nhận điều đó, họ đã có hành động từ lâu rồi”.\nKhông có báo cáo nào về việc thực thi nhắm mục tiêu trong hơn 11 năm (theo phần Câu hỏi thường gặp); doanh số bán thẻ tại Chợ Cộng đồng phát sinh từ đó phải chịu mức phí tổng hợp củSteam khoảng 15%.\nPhần Câu hỏi thường gặp (FAQ) nêu rõ mức trần khuyến nghị là mười tài khoản cho mỗi nhà điều hành và dẫn nguồn từ Valve: “Khuyến nghị này dựa trên các hướng dẫn nội bộ của Valve, cũng như các đề xuất của chính chúng tôi.” Valve chưa công bố bất kỳ hướng dẫn nào như vậy.\nGiới hạn kỹ thuật, theo cùng phần Câu hỏi thường gặp (FAQ) này: \"Bạn có thể chạy tối đa 100-200 bot với một địa chỉ IP và một phiên bản ASF.\"\nThời gian chơi được tạo ra nhân tạo được ghi lại tại Valve — “thông tin này thường được cập nhật khoảng mỗi 30 phút” — và § 4.C liệt kê “Giả mạo số liệu thống kê trong trò chơi (e.g., thổi phồng số trận thắng hoặc thua, XP, thời gian chơi)” là hành vi bị cấm.\nNguồn\nTrang wiki câu hỏi thường gặp (FAQ) chính thức của JustArchi ASF ↗ Kho lưu trữ ArchiSteamFarm ↗ đã lưu trữ 2026-09-24 ↗\nĐiều khoản về tự động hóa được quy định rõ ràng; phần Câu hỏi thường gặp (FAQ) của ASF đã nêu rõ từ nhiều năm nay rằng công cụ này đang hoạt động trên hàng triệu tài khoản; chưa có báo cáo nào về việc thực thi có chủ đích nhằm vào công cụ này. Khoảng cách giữa quy định và việc áp dụng quy định chính là thực trạng hiện tại; nguyên nhân dẫn đến điều này chưa được làm rõ trong bài viết này.\nTriển lãm trọn vẹnNền kinh tế thẻ: quy trình, quy mô, giấy phép và ai là người giám sát ↗Những gì một trang trại phải mua từ Valve trước khi có thể sản xuất được một thẻ; hai dòng trong § 4.C mô tả hoạt động “trồng thẻ” qua các tác động của nó; lý do tại sao mọi cách đổi thẻ lấy tiền mặt đều vi phạm giấy phép Valve trong khi Valve thu phí ngay từ đầu; hồ sơ thực thi bao gồm đợt kiểm tra VAC vào tháng 6 tại 2025 và việc cấm theo chuỗi dựa trên số điện thoại chung; cùng với nhân viên Valve và các điều phối viên cộng đồng được phát hiện đang quản lý dịch vụ trao đổi thẻ và danh sách cấm xung quanh Steam.Cuộc điều tra dân số về các loài bị cấmChúng tôi không hỏi trang trại Valve diện tích trang trại là bao nhiêu. Chúng tôi đã tự đếm. ↗10,880,610 Tổng số tài khoản (có giới hạn và không giới hạn) được đọc từ nhóm Steam của chính ArchiSteamFarm, nhóm mà phần mềm sẽ tự động tham gia theo mặc định khi khởi chạy lần đầu, trừ khi người dùng bỏ chọn cài đặt tham gia nhóm (bao gồm cả các trang trại bot thương mại và người chơi thông thường vẫn giữ nguyên cài đặt mặc định). 88.97% không bị bất kỳ hình thức cấm nào từ Steam; trong số các trường hợp 11% bị cấm, 99.8% chỉ là các lệnh cấm cộng đồng mang tính hình thức và không bao giờ ngăn cản việc giao dịch. Sau khi đối chiếu với SteamRep, 67.77%, các đối tượng lừa đảo trong danh sách này vẫn hoạt động tự do một khi các lệnh cấm chống gian lận được gỡ bỏ. Với phân tích theo ngày đăng ký, vị trí địa lý và tỷ lệ tồn tại — quy mô thực tế, được đo lường, không phải chỉ là lời kể.\n\nPhụ lục F — Sổ cái làm việc\n\nSổ quy tắc: các điều khoản chống lại các nền tảng được ghi nhận\n\nChọn một quy tắc; danh sách sẽ hiển thị các nền tảng đã được ghi nhận và gắn thẻ theo quy tắc đó, kèm theo tên miền chính, máy chủ xác thực đã khai báo và kết quả Lọc Liên kết đã lưu. Trong trường hợp trang web bị chặn hoặc có tên miền khác để đăng nhập: hãy tuân theo quy tắc cho đến khi đến đường dẫn còn lại.\n\n175các bản ghi có liên quan\ntheo quy tắc này\n174 miền cấp cao nhất0 Các đề cập đến C&D\nTRÍCH DẪN QUY ĐỊNH / SSA §2.G\nSử dụng cho mục đích thương mại và tính phí tài khoản\n“…exploit the Content and Services or any of its parts for any commercial purpose, except as expressly permitted elsewhere in this Agreement (including any Subscription Terms or Rules of Use).”\nTHEO DÕI CÁC KỶ LỤC\nĐăng ký nền tảng 175\nCác con số trong bảng là ước tính dựa trên nguồn\n\n175 trong số các bản ghi của \"175\"\n\nDịch vụ / nhóm mẹ\tMiền chính / cơ quan đăng ký\tMiền xác thực / độ tuổi được quan sát thấy\tThang đo / Phản hồi đã ghi nhận\n\nCasino\n\tcsgoempire.com\n11.3 yearsRegistered 2015-06-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgoempirelogin4.com\n6.2 yearsRegistered 2020-07-20\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustreaper.com\n23.2 yearsRegistered 2003-06-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustreaper.com\n23.2 yearsRegistered 2003-06-24\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustly.com\n12.4 yearsRegistered 2014-05-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustly.com\n12.4 yearsRegistered 2014-05-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette Casino\n\tcsgofast.com\n11.5 yearsRegistered 2015-03-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsteam-login.authtofast.com\n83 daysRegistered 2026-06-30\nRDAP ↗ · authtofast.com (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tduelbits.com\n6.6 yearsRegistered 2020-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nswitchflips.com\n6.4 yearsRegistered 2020-04-21\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opener\n\tfarmskins.com\n10.5 yearsRegistered 2016-03-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsteam.kobal.cc\n9.7 yearsRegistered 2017-01-07\nRDAP ↗ · kobal.cc (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgoluck.com\n9.3 yearsRegistered 2017-05-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgoluck.com\n9.3 yearsRegistered 2017-05-18\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tinsane.gg\n7.5 yearsRegistered 2019-04-02\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.insane.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcs2skin.com\n3.5 yearsRegistered 2023-03-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncs2skin.com\n3.5 yearsRegistered 2023-03-06\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tjuice.gg\n7.9 yearsRegistered 2018-10-19\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nletmeinjuice.com\n2.4 yearsRegistered 2024-04-15\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tggdrop.com\n8.6 yearsRegistered 2018-02-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nggauth.com\n3.4 yearsRegistered 2023-05-03\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Casino\n\thowl.gg\n9.5 yearsRegistered 2017-03-16\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhowl.uno\n41 daysRegistered 2026-08-11\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tchicken.gg\n5.7 yearsRegistered 2021-01-11\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nchicken.gg\n5.7 yearsRegistered 2021-01-11\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgocasino.gg\n2.6 yearsRegistered 2024-02-17\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.csgocasino.gg\n2.6 yearsRegistered 2024-02-17\nWHOISFREAKS ↗ · csgocasino.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Casino\n\thunt.gg\n6.9 yearsRegistered 2019-11-04\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.hunt.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Battles\n\tcsbattle.com\n9.8 yearsRegistered 2016-12-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsbattle.com\n9.8 yearsRegistered 2016-12-10\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskinrave.gg\n3.1 yearsRegistered 2023-08-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinrave.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsdouble.gg\n261 daysRegistered 2026-01-03\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsdouble.gg\n261 daysRegistered 2026-01-03\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustchance.com\n8.0 yearsRegistered 2018-10-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhgfuihd.com\n7.6 yearsRegistered 2019-01-27\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Automation\n\tcobaltlab.tech\n3.5 yearsRegistered 2023-03-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncobaltauth.com\n1.7 yearsRegistered 2025-01-07\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\traided.gg\n171 daysRegistered 2026-04-03\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.raided.gg\n171 daysRegistered 2026-04-03\nIP2WHOIS ↗ · raided.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustneo.gg\n1.3 yearsRegistered 2025-06-20\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrustneo.gg\n1.3 yearsRegistered 2025-06-20\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tsplits.gg\n3.7 yearsRegistered 2023-01-23\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsplits.gg\n3.7 yearsRegistered 2023-01-23\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Upgrader\n\tupgrader.pro\n1.2 yearsRegistered 2025-07-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nupgauth.space\n38 daysRegistered 2026-08-14\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskin.fans\n8.2 yearsRegistered 2018-07-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skinfans.com\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\thotpizza.one\n1.8 yearsRegistered 2024-12-07\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhotpizza.one\n1.8 yearsRegistered 2024-12-07\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tg4skins.com\n10.1 yearsRegistered 2016-08-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.g4s.to\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2royal.com\n4.1 yearsRegistered 2022-08-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ntf2auth.com\n5.2 yearsRegistered 2021-07-27\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2hunt.com\n8.7 yearsRegistered 2018-01-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrstspcl.com\n6.1 yearsRegistered 2020-08-08\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2.bet/coinflip\n8.4 yearsRegistered 2018-05-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ntf2.bet\n8.4 yearsRegistered 2018-05-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\topenstars.gg\n131 daysRegistered 2026-05-13\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nopenstars.gg\n131 daysRegistered 2026-05-13\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tskins.com\n25.1 yearsRegistered 2001-08-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skins.com\n25.1 yearsRegistered 2001-08-08\nRDAP ↗ · skins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\twhite.market\n9.6 yearsRegistered 2017-03-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwhite.market\n9.6 yearsRegistered 2017-03-01\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tmoon.market\n7.6 yearsRegistered 2019-02-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmoon.market\n7.6 yearsRegistered 2019-02-27\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tcsfloat.com\n5.2 yearsRegistered 2021-07-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncsgofloat.com\n11.0 yearsRegistered 2015-09-29\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tskin.land\n4.7 yearsRegistered 2022-01-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skin.land\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\thaloskins.com\n2.8 yearsRegistered 2023-12-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nhaloskins.com\n2.8 yearsRegistered 2023-12-10\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCorporate Market\n\tbuff.163.com\n29.0 yearsRegistered 1997-09-15\nRDAP ↗ · 163.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\nbuff.163.com\n29.0 yearsRegistered 1997-09-15\nRDAP ↗ · 163.com (parent)\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\tmarket.csgo.com\n26.6 yearsRegistered 2000-02-07\nRDAP ↗ · csgo.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\ndota2.net\n14.9 yearsRegistered 2011-10-29\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRegulated Market\n\tskinport.com\n8.0 yearsRegistered 2018-09-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinport.app\n6.3 yearsRegistered 2020-06-20\nRDAP ↗\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMarketplace/Swap\n\tskinflow.gg\n3.8 yearsRegistered 2022-11-26\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinflow.gg\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tskin.place\n6.0 yearsRegistered 2020-09-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skin.place\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tskinsmonkey.com\n5.7 yearsRegistered 2021-01-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinsmonkey.com\n5.7 yearsRegistered 2021-01-06\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCorporate Market\n\tskinbaron.de\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinbaron.com\n10.7 yearsRegistered 2015-12-22\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Market\n\trust.tm\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\ndota2.net\n14.9 yearsRegistered 2011-10-29\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tpirateswap.com\n6.0 yearsRegistered 2020-09-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nlogin.pirateswap.com\n6.0 yearsRegistered 2020-09-22\nRDAP ↗ · pirateswap.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Marketplace\n\tmannco.store\n8.6 yearsRegistered 2018-03-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmannco.store\n8.6 yearsRegistered 2018-03-02\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tskinswap.com\n9.9 yearsRegistered 2016-11-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinswap.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\texeskins.com\n2.1 yearsRegistered 2024-08-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nexeskins.com\n2.1 yearsRegistered 2024-08-14\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Market\n\tbalticskins.com\n153 daysRegistered 2026-04-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nbalticskins.com\n153 daysRegistered 2026-04-21\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Swap\n\tcs.trade\n8.9 yearsRegistered 2017-11-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncs.trade\n8.9 yearsRegistered 2017-11-14\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\trapidskins.com\n4.5 yearsRegistered 2022-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.rapidskins.com\n4.5 yearsRegistered 2022-03-11\nRDAP ↗ · rapidskins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\ttradeit.gg\n9.1 yearsRegistered 2017-08-21\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nconnect-tradeit.com\n4.6 yearsRegistered 2022-02-23\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\t49skins.com\n3.4 yearsRegistered 2023-04-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.49skins.com\n3.4 yearsRegistered 2023-04-19\nRDAP ↗ · 49skins.com (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tskinvault.gg\n3.4 yearsRegistered 2023-05-06\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.skinvault.gg\n3.4 yearsRegistered 2023-05-06\nIP2WHOIS ↗ · skinvault.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Trading\n\taim.market\n3.3 yearsRegistered 2023-05-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\naim.market\n3.3 yearsRegistered 2023-05-22\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Sell Portal\n\tskinout.gg\n5.6 yearsRegistered 2021-02-27\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.skinout.gg\n5.6 yearsRegistered 2021-02-27\nIP2WHOIS ↗ · skinout.gg (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkins Trading\n\tntskins.com\n230 daysRegistered 2026-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nntskins.com\n230 daysRegistered 2026-02-03\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Portal\n\tgamerpay.gg\n6.0 yearsRegistered 2020-10-02\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ngamerpay.gg\n6.0 yearsRegistered 2020-10-02\nWHOISFREAKS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Scrap Swap\n\tscrap.tf\n14.0 yearsRegistered 2012-09-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nscrap.tf\n14.0 yearsRegistered 2012-09-03\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Cashout\n\tmarketplace.tf\n14.0 yearsRegistered 2012-09-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nmarketplace.tf\n14.0 yearsRegistered 2012-09-19\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Cashout\n\tskins.cash\n10.5 yearsRegistered 2016-03-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nskinscash.live\n6.8 yearsRegistered 2019-12-05\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgo.net\n14.2 yearsRegistered 2012-07-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\ncn2.easylot.net\n10.0 yearsRegistered 2016-09-03\nRDAP ↗ · easylot.net (parent)\nSEPARATE DOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCommunity Hub\n\tcybershoke.net\n6.8 yearsRegistered 2019-11-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.cybershoke.net\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMatchmaker Hub\n\tfastcup.net\n14.6 yearsRegistered 2012-02-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.fastcup.net\n14.6 yearsRegistered 2012-02-16\nRDAP ↗ · fastcup.net (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Analytics\n\tleetify.com\n7.6 yearsRegistered 2019-03-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nleetify.com\n7.6 yearsRegistered 2019-03-01\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Analytics\n\tscope.gg\n7.8 yearsRegistered 2018-12-10\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nscope.gg\n7.8 yearsRegistered 2018-12-10\nIP2WHOIS ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tools\n\ttradeupspy.com\n6.5 yearsRegistered 2020-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.tradeupspy.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMarketplace\n\tcs.deals\n9.8 yearsRegistered 2016-12-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\napi.cs.deals\n9.8 yearsRegistered 2016-12-03\nRDAP ↗ · cs.deals (parent)\nOWN SUBDOMAINReturn hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Price DB\n\tpricempire.com\n6.6 yearsRegistered 2020-01-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\npricempire.com\n6.6 yearsRegistered 2020-01-30\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Blackmarket\n\tFSB Market\n7.2 yearsRegistered 2019-07-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nFSB Market\n7.2 yearsRegistered 2019-07-27\nRDAP ↗\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nReady-Account Hub\n\tz2u.com\n26.9 yearsRegistered 1999-11-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwww.z2u.com\n26.9 yearsRegistered 1999-11-10\nRDAP ↗ · z2u.com (parent)\nSAME HOSTSame hostname captured2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Gambling\n\tcsgoroll.com\n11.6 yearsRegistered 2015-02-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwww.csgoroll.com\nRegistry date unavailableRegistry date unavailable\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\trollbit.com\n11.9 yearsRegistered 2014-11-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nrbsnin.com\n3 daysRegistered 2026-09-18\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nLicenced Casino\n\t500.casino\n5.9 yearsRegistered 2020-11-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette/Slots\n\tcsgobig.com\n11.4 yearsRegistered 2015-04-12\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcasedrop.com\n14.8 yearsRegistered 2011-12-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\tbanditcamp.com\n12.2 yearsRegistered 2014-06-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tskinbox.com\n18.8 yearsRegistered 2007-12-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\ttastydrop.com\n6.1 yearsRegistered 2020-08-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRoulette Casino\n\tcsgopolygon.gg\n6.5 yearsRegistered 2020-03-28\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tmagicdrop.ru\n10.3 yearsRegistered 2016-05-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nDice Casino\n\tcsdice.com\n3.8 yearsRegistered 2022-11-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUpgrader Casino\n\tskinodds.com\n1.2 yearsRegistered 2025-06-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgowin.com\n12.0 yearsRegistered 2014-09-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrash Casino\n\tcsgorun.net\n7.3 yearsRegistered 2019-06-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\topenskins.com\n3.6 yearsRegistered 2023-02-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Gambling\n\trustbet.com\n7.6 yearsRegistered 2019-02-07\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgomagic.com\n9.4 yearsRegistered 2017-05-01\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUpgrader/Contract\n\tcsgobounty.com\n11.5 yearsRegistered 2015-03-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tezskins.com\n27.5 yearsRegistered 1999-03-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\trustcases.com\n7.2 yearsRegistered 2019-06-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgoreaper.com\n11.1 yearsRegistered 2015-08-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgocases.com\n12.3 yearsRegistered 2014-06-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Upgrader\n\tcsgo-skins.com\n11.2 yearsRegistered 2015-07-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgonet.com\n8.8 yearsRegistered 2017-12-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\twtfskins.com\n9.0 yearsRegistered 2017-10-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Casino\n\tflamecases.com\n10.0 yearsRegistered 2016-09-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tgamedom.com\n11.7 yearsRegistered 2015-01-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Battles\n\tskin.club\n9.0 yearsRegistered 2017-09-04\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nsc-auth.net\n7.5 yearsRegistered 2019-04-02\nRDAP ↗\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tdaddyskins.com\n9.9 yearsRegistered 2016-10-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Gambling\n\trustix.gg\n1.7 yearsRegistered 2025-01-16\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Upgrade\n\tskins.club\n4.2 yearsRegistered 2022-07-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\tcsgohouse.org\n146 daysRegistered 2026-04-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedConsent required2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tskinrave.net\n216 daysRegistered 2026-02-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tbloodycase.gg\n19 daysRegistered 2026-09-02\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nClicker/Upgrade\n\tcsgoclicker.com\n8.3 yearsRegistered 2018-05-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Roulette\n\trustbet.gg\n4.0 yearsRegistered 2022-09-30\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcs-drop.com\n262 daysRegistered 2026-01-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Roulette\n\thellstore.net\n11.7 yearsRegistered 2015-01-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustloot.com\n354 daysRegistered 2025-10-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCase Opening\n\tcsgo-case.com\n10.3 yearsRegistered 2016-05-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Casino\n\tcsgogem.com\n9.9 yearsRegistered 2016-10-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\trainbet.com\n8.8 yearsRegistered 2017-11-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nservices.rainbet.com\nRegistry date unavailableRegistry date unavailable\nOWN SUBDOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Casino\n\trustclash.com\n5.4 yearsRegistered 2021-05-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrash Casino\n\t12cs.fail\n181 daysRegistered 2026-03-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\twww.tf2easy.com\n6.3 yearsRegistered 2020-06-02\nRDAP ↗ · tf2easy.com (parent)\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Gambling\n\ttf2blaze.com\n7.6 yearsRegistered 2019-01-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCrypto Casino\n\tshuffle.com\n30.1 yearsRegistered 1996-07-31\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tbuff.market\n5.9 yearsRegistered 2020-10-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tavan.market\n8.3 yearsRegistered 2018-05-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Engine\n\tcs.money\n11.0 yearsRegistered 2015-09-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.dota.trade\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Market\n\tuuskins.com\n2.6 yearsRegistered 2024-01-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Market\n\tyoupin898.com\n6.1 yearsRegistered 2020-08-27\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tc5game.com\n10.5 yearsRegistered 2016-03-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\twaxpeer.com\n7.3 yearsRegistered 2019-05-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nwaxpeer.com\n7.3 yearsRegistered 2019-05-20\nRDAP ↗\nSAME HOSTHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBot Trading\n\tcs.money\n11.0 yearsRegistered 2015-09-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nauth.dota.trade\nRegistry date unavailableRegistry date unavailable\nSEPARATE DOMAINHost in supplied OpenID URL2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nUS Marketplace\n\tdmarket.com\n30.2 yearsRegistered 1996-07-03\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nOfficial Market\n\tsteamcommunity.com/market\n20.3 yearsRegistered 2006-05-28\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNot an external login site2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Platform\n\tlootfarm.com\n11.9 yearsRegistered 2014-10-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRust Market\n\trustskins.com\n7.6 yearsRegistered 2019-01-31\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCS2 Market\n\tkrakatoa.com\n26.4 yearsRegistered 2000-05-15\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nP2P Marketplace\n\tshadowpay.com\n10.1 yearsRegistered 2016-08-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nChinese Powerhouse\n\tigxe.cn\n15.0 yearsRegistered 2011-09-06\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAutomated Swap\n\tswap.gg\n9.6 yearsRegistered 2017-01-29\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCash-out Portal\n\tbitskins.com\n11.2 yearsRegistered 2015-07-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Automation\n\ttf2mart.com\n1.1 yearsRegistered 2025-08-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Auctions\n\tskinbid.com\n10.2 yearsRegistered 2016-06-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSkin Rental\n\tlootbear.com\n8.7 yearsRegistered 2018-01-16\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Valuation\n\tbackpack.tf\n14.4 yearsRegistered 2012-05-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTF2 Botnet\n\tstntrading.eu\nRegistry date unavailableRegistry date unavailable\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nInstant Cashout\n\tskinwallet.com\n18.0 yearsRegistered 2008-09-14\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nDota 2 Market\n\tdota2market.com\n12.2 yearsRegistered 2014-07-24\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nServer Network\n\txplay.gg\n5.3 yearsRegistered 2021-06-13\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMatchmaking Portal\n\tesportal.com\n26.8 yearsRegistered 1999-12-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nLATAM Hub\n\tgamersclub.com.br\n11.2 yearsRegistered 2015-06-29\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tools\n\tepidemic.gg\n4.9 yearsRegistered 2021-11-03\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tcs2stash.com\n3.5 yearsRegistered 2023-03-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tcsgoskins.gg\n6.8 yearsRegistered 2019-12-21\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Index\n\tsteamanalyst.com\n12.6 yearsRegistered 2014-02-21\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nTrading Exchange\n\tsteamcardexchange.net\n13.3 yearsRegistered 2013-05-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tracker\n\tdotabuff.com\n14.2 yearsRegistered 2012-06-22\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSaaS Tracker\n\ttracker.gg\n8.9 yearsRegistered 2017-10-12\nIP2WHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Exchange\n\tfunpay.com\n17.0 yearsRegistered 2009-09-06\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nGrey Market\n\tplayerauctions.com\n26.3 yearsRegistered 2000-06-13\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Portal\n\teldorado.gg\n8.0 yearsRegistered 2018-09-12\nWHOISFREAKS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Key Market\n\tg2a.com\n24.8 yearsRegistered 2001-12-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nMass Key Market\n\tkinguin.net\n16.8 yearsRegistered 2009-12-17\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nVirtual Services\n\tg2g.com\n31.1 yearsRegistered 1995-08-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nAccount Broker\n\tplayerup.com\n19.3 yearsRegistered 2007-05-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfhub.net\n2.7 yearsRegistered 2023-12-26\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfaccounts.com\n5.3 yearsRegistered 2021-05-18\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedVerification challenge2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Shop\n\tbuycsgorank.com\n6.2 yearsRegistered 2020-07-09\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tcsgosmurfkings.com\n9.3 yearsRegistered 2017-06-08\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nSmurf Shop\n\tsmurfstore.co\n8.6 yearsRegistered 2018-03-03\nWHOIS ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlvlup.com\n9.9 yearsRegistered 2016-11-10\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlevels.com\n10.6 yearsRegistered 2016-02-19\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite returned an error2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tlevelsteam.com\n79 daysRegistered 2026-07-04\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedCheck timed out2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nCard Leveling\n\tsteamlevelu.com\n6.0 yearsRegistered 2020-09-05\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\teloking.com\n12.2 yearsRegistered 2014-07-02\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\tboosteria.org\n11.9 yearsRegistered 2014-10-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tovergear.com\n14.4 yearsRegistered 2012-04-20\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedLogin not resolved2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tblazingboost.com\n14.2 yearsRegistered 2012-06-23\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nRank Boosting\n\tdota2boost.com\n2.9 yearsRegistered 2023-10-11\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedWebsite did not load2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\n\nBoosting SaaS\n\tbuyboost.com\n22.4 yearsRegistered 2004-04-30\nRDAP ↗\nOpen Steam Link Filter ↗Filter status is a separate check\t\nRoute not confirmedNo visible Steam sign-in2026-09-19 · capture ↗\n\tNo sourced measurementSee dated evidence\nLập luận của cuộc điều traQuy tắc được lựa chọn / Phân tích và bình luận+\nGánh nặng chứng minh\n\nCuộc điều tra này đặt ra vấn đề về sự chênh lệch giữa các hạn chế đối với việc sử dụng thương mại và các dịch vụ được ghi nhận tại đây. Cần phân loại từng hoạt động và xác định xem có sự cho phép rõ ràng nào hay không trước khi kết luận đó là vi phạm hợp đồng. Phí của Chợ Cộng đồng không áp dụng cho mọi giao dịch bên ngoài.\n\nBản ghi được gắn thẻ là gì, và không phải là gì\n\nMột hồ sơ sẽ được gắn nhãn khi trong hồ sơ có ghi chú kèm ngày tháng cho thấy nền tảng đó thuộc phạm vi điều khoản theo nội dung văn bản. Việc gắn nhãn không đồng nghĩa với việc vi phạm đã được xác định, và chưa có giấy phép rõ ràng từ Cơ quan Quản lý Hàng hải (Valve) được cấp cho bất kỳ nền tảng nào được liệt kê tại đây. Trong trường hợp nền tảng đó có giấy phép, việc công bố giấy phép đó sẽ giải quyết mục ghi chép này.\n\nNguồn và phương pháp luậnDự toán, định nghĩa và phạm vi+\n\nCác số liệu trên đề cập đến quy tắc đã chọn. Các loại bản ghi chỉ được tính một lần cho mỗi nền tảng; các thẻ đầy đủ sẽ hiển thị trong phần chi tiết nền tảng. Tính năng tìm kiếm và bộ lọc được áp dụng trong phạm vi quy tắc đó. Ngày đăng ký được lấy từ bản chụp nhanh đã lưu tại RDAP / WHOIS. Các tên miền con sử dụng ngày tạo của tên miền cha. Tuổi đời của tên miền không đủ để xác định hoạt động liên tục hoặc đường dẫn xác thực. Tên máy chủ xác thực hiện tại được lấy từ các yêu cầu OpenID đã lưu, kèm theo dấu thời gian UTC; các kiểm tra chưa được giải quyết không tái sử dụng các nhãn cũ. Công cụ quan sát dừng lại trước khi đăng nhập tại Steam và không kiểm tra trạng thái bộ lọc liên kết tại Steam. Tải xuống các ghi nhận về tuyến đường ↗ Tải xuống kết quả kiểm tra sổ đăng ký ↗\n\nKhám phá kho lưu trữ mã nguồn ↗\nPhụ lục G — Từ mẫu văn bản từ chối đến hồ sơ gốc\nCẩm nang DSAR: Yêu cầu cung cấp bằng chứng\n\nSử dụng Điều 15 GDPR để yêu cầu cung cấp dữ liệu cá nhân liên quan đến việc tạo khóa API, khôi phục tài khoản và truy cập dịch vụ hỗ trợ. Hồ sơ được lưu giữ có thể xác minh ai là người khởi xướng hành động và nền tảng đã dựa trên cơ sở nào.\n\n01\nHãy lưu giữ dòng thời gian của bạn.\n\nLưu lại các thông báo tài khoản, phiếu yêu cầu, mã giao dịch và ngày giờ theo múi giờ UTC. Bảo mật tài khoản và xem xét các tùy chọn khôi phục áp dụng cho trò chơi và giao dịch.\n\nSteam Thông tin về các biện pháp bảo hộ thương mại ↗\n02\nYêu cầu cung cấp dữ liệu đã được lưu trữ của bạn.\n\nYêu cầu cung cấp dấu thời gian, địa chỉ IP nguồn, các sự kiện quan trọng trong vòng đời khóa, xác nhận bảo mật và các hành động khôi phục liên quan đến tài khoản. Bao gồm các sự kiện truy cập hỗ trợ và người nhận trong trường hợp những dữ liệu đó liên quan đến bạn.\n\n03\nHãy lưu giữ biên bản giao hàng.\n\nHãy sử dụng kênh liên hệ về quyền riêng tư của Valve. Thời gian phản hồi thông thường là một tháng; nếu cần gia hạn thêm tối đa hai tháng, phải nêu rõ lý do trong tháng đầu tiên đó.\n\nValve liên hệ về quyền riêng tư ↗ đã lưu trữ 2026-09-21 ↗\n04\nHãy so sánh các câu trả lời.\n\nĐối chiếu các bản ghi với dòng thời gian của bạn. Hỏi lý do tại sao có những nội dung bị bỏ sót, sau đó nếu cần thiết, hãy sử dụng thủ tục khiếu nại lên cấp trên có thẩm quyền. Lưu giữ nguyên văn câu trả lời như đã nhận được.\n\nPhạm vi / Bài báo15\n\nQuyền truy cập bao gồm dữ liệu cá nhân được lưu giữ, bao gồm cả dữ liệu trong nhật ký. Quyền này không đảm bảo việc truy cập vào mọi tài liệu nội bộ, hồ sơ được tái lập hoặc dữ liệu chưa được che giấu liên quan đến người khác. Hãy yêu cầu một bản sao dễ hiểu và cơ sở pháp lý cho bất kỳ hạn chế nào.\n\nHướng dẫn về quyền truy cập của EDPB, các điều 2, 4–6 ↗ · GDPR Các bài viết 12, 15, 77 ↗ đã lưu trữ 2026-09-20 ↗\n\nYêu cầu truy cập thông tin của chủ thể dữ liệuGDPR / Bài viết 15\nBảo mật tài khoản và lịch sử truy cập\n\nHãy thay thế các trường được đặt trong dấu ngoặc trước khi gửi.\n\nTo: Valve Privacy Team\nSubject: Article 15 GDPR request — account security records\n\nAccount / SteamID: [YOUR ACCOUNT IDENTIFIER]\nRelevant period (UTC): [START] to [END]\nRelated support tickets: [TICKET REFERENCES]\n\nI request a copy of the personal data concerning me that you retain for this period, including:\n\n1. API-key registration, confirmation, use and revocation events, with available timestamps, source IP addresses, registered domains, device or user-agent information and non-secret key identifiers.\n\n2. Recorded account-recovery actions, password/email/phone changes, Steam Guard removals or resets, confirmation events and the account-related evidence relied on to authorize those actions.\n\n3. Personal data in support-access and administrative-action logs concerning my account, including available dates, purposes, actions and the support entity involved, subject to applicable rights of others.\n\n4. Account-related records used to determine any sanction, and available records of my complaints, reviews and responses.\n\nPlease also provide the applicable processing purposes, categories, recipients, retention periods or criteria, and available information about sources where data were not obtained from me.\n\nWhere processing relies on my consent, please provide the retained record of the consent relied upon and the wording presented at that time.\n\nPlease provide an intelligible electronic copy with time zones and field definitions. Please do not include active credentials or secret tokens. If any requested data are not held, please say so. For any withheld data, please identify the scope and legal basis of the restriction and provide the remainder.\n\nPlease acknowledge receipt and respond within the applicable Article 12 period, explaining any necessary extension. I also ask you to preserve relevant existing records while this request is handled.\n\nName: [YOUR NAME]\nDate: [DATE]\nMột địa chỉ IP trung tâm dữ liệu có thể thiết lập được những gì\nSự không khớp là bằng chứng cần được điều tra.\n\nYêu cầu khóa “API” xuất phát từ mạng trung tâm dữ liệu, như trong ví dụ về nhà cung cấp dịch vụ lưu trữ được nêu trong cuộc điều tra này, có thể có ý nghĩa khi so sánh với các bản ghi đăng nhập, thông báo xác nhận và dòng thời gian của người dùng. Chỉ riêng địa chỉ IP không đủ để xác định danh tính của đối tượng thực hiện hành vi hoặc tự động vô hiệu hóa mọi biện pháp phòng vệ. Bằng chứng cho thấy một đối tượng có ý đồ xấu đã cung cấp sự đồng ý được ghi lại có thể làm lung lay tính hợp lệ của sự đồng ý đó; các cơ sở pháp lý khác và các vấn đề về trách nhiệm pháp lý cần được phân tích riêng biệt.\n\nXem đơn khiếu nại “ban-and-GDPR” đã được lưu giữ →\nPhụ lục H — Phân tích kho lưu trữ “Wayback Machine” · Thống kê hỗ trợ đã công bố\nKhối lượng hỗ trợ. Thời gian phản hồi đã công bố.\nBối cảnh và các giới hạn về nguồn\n\nValve công bố số liệu thống kê hỗ trợ hàng ngày tại store.steampowered.com/stats/support. Kho lưu trữ Wayback Machine lưu giữ các bản sao lưu lịch sử của trang này từ 2018 đến 2026. Tỷ lệ khối lượng công việc trên số lượng nhân viên được suy ra từ các số liệu này không phù hợp với việc kiểm tra thủ công từng phiếu yêu cầu trong khoảng thời gian phản hồi đã công bố.\n\nSo sánh các số liệu hỗ trợ đã lưu trữ củaValve qua các bản chụp nhanh đã lưu. Phương pháp nghiên cứu giải thích những số liệu này có thể và không thể đo lường được những gì.\n\nKhối lượng so với thời gian phản hồi đã công bố (2018 → 2026)\nHai hàng người chờ tại một quầy hỗ trợ, như có thể thấy qua các ảnh chụp màn hình được lưu trữ trên 21.\n\nValve công bố số liệu hỗ trợ trực tuyến tại store.steampowered.com/stats/support. Mỗi giá trị dưới đây chính là giới hạn dưới Valve được in trên trang đó vào ngày Internet Archive lưu trữ trang web — chứ không phải là ước tính của chúng tôi. Cả hai dãy số liệu đều là cùng một đại lượng được đo bằng cùng một đơn vị, do đó chúng thuộc về cùng một trục và có thể so sánh trực tiếp với nhau.\n\nYêu cầu hoàn tiền — số tiền mà Valve đang nắm giữBảo mật và khôi phục tài khoản — tài khoản mà bạn đã mất\n0 h\n2 h\n4 h\n6 h\n8 h\n10 h\nno captures · 38 months\n2019\n2020\n2021\n2022\n2023\n2024\n2025\n2026\n8 h 44 m\naccount recovery\n52 m\nrefunds\n15 m — one capture only\n49–55 phútGiá trị dưới cùng của khoản hoàn trả trong mỗi lần ghi nhận từ tháng 2 năm 2018 đến tháng 8 năm 2026.. Trong khoảng thời gian tám năm rưỡi, giá trị này chỉ dao động chưa đến sáu phút, trong khi khối lượng hoàn trả hàng ngày biến động gấp chín lần.\n2.4 h → 8.7 h10.9 5.8 Giới hạn dưới của thời gian khôi phục tài khoản nằm ở mức khoảng 2.4 giờ trong mọi lần ghi nhận cho đến tháng 12 2022, ngoại trừ một lần. Trong ba lần ghi nhận 2026, các giá trị được công bố lần lượt là Valve h, h và 8.7 h.\n×2.8 → ×13Theo số liệu do chính Valve công bố, tốc độ xử lý yêu cầu hoàn tiền chậm hơn bao nhiêu so với việc xử lý các khoản hoàn trả. Tình trạng này ổn định trong năm năm, sau đó khoảng cách ngày càng nới rộng — hàng đợi trở nên chậm hơn chính là hàng đợi mà người dùng, chứ không phải Valve, phải tự chi trả.\n\nNguồn: 21 Wayback Machine các ảnh chụp màn hình của store.steampowered.com/thống_kê/hỗ_trợ, 2018-02-03 đến 2026-08-10; trích xuất tại VALVE_EVIDENCE_PACK/databases/steam_support_stats_history.json. Hãy xem các giới hạn kèm theo các số liệu: biểu đồ này thể hiện thấp hơn Giới hạn trên và dưới của khoảng giá trị Valve được công bố. Giới hạn trên được công bố kém hơn ở cả hai chỉ số — thời gian hoàn tiền dao động từ 1.5 giờ đến 1.5 ngày, thời gian phục hồi dao động từ 7.0 giờ đến 3.6 ngày. Hai bản ghi đã được lưu trữ trong phiên bản địa phương hóa của cùng một trang Valve — 2018-11-03 bằng tiếng Séc, 2020-03-25 bằng tiếng Pháp — và được đánh dấu là (cs) và (fr) trong bảng; các số liệu của chúng được hiển thị ở đây với các đơn vị đo lường được dịch và các con số giữ nguyên như đã công bố, trong khi các chuỗi nguồn nguyên văn được giữ nguyên trong tệp trích xuất. Mỗi lần thu thập dữ liệu đều công bố thời gian phản hồi cho cả hai hàng đợi, và không có điểm nào trên cả hai đường cong được nội suy. Con số phục hồi trong một phút duy nhất 15-là 2020-10-21 được đánh dấu trên biểu đồ và được giữ lại: nó chỉ xuất hiện trong một lần thu thập dữ liệu duy nhất và không có lần thu thập dữ liệu nào khác nằm trong cùng một bậc độ lớn với nó. Không có bản ghi nào tồn tại trong khoảng thời gian từ 2022-12-08 đến 2026-02-01; khoảng trống 38-tháng trong bản ghi được tô bóng và không có đường nào được vẽ qua đó. Các số liệu này mô tả thời gian phản hồi đã được công bố. Chúng không thể hiện những gì diễn ra bên trong một phiếu yêu cầu, và Valve chưa công bố số lượng nhân viên để so sánh với các số liệu này.\n\nMở từng bản chụp dưới dạng bảng\nMỗi bản ghi đã được lưu trữ, như đã được công bố\nChụp\tTiền hoàn lại / ngày\tPhản hồi về việc hoàn tiền\tKhôi phục / ngày\tCác biện pháp ứng phó và phục hồi\n2018-02-03\t98,788\t50.12 minutes to 1.52 hours\t25,662\t2.51 hours to 1.80 days\n2018-05-07\t60,494\t53.83 minutes to 1.47 days\t24,226\t2.45 hours to 2.22 days\n2018-08-02\t69,084\t50.27 minutes to 1.59 hours\t28,953\t2.44 hours to 22.17 hours\n2018-11-03 (cs)\t63,410\t49.28 minutes to 1.54 hours\t33,910\t2.42 hours to 1.31 days\n2019-02-01\t76,305\t50.13 minutes to 1.52 hours\t35,164\t2.44 hours to 2.04 days\n2019-05-18\t78,951\t51.03 minutes to 3.12 hours\t27,514\t2.46 hours to 20.39 hours\n2019-09-07\t78,941\t50.65 minutes to 1.66 hours\t28,812\t2.42 hours to 13.59 hours\n2019-12-13\t69,589\t50.77 minutes to 1.55 hours\t25,322\t2.45 hours to 1.13 days\n2020-03-25 (fr)\t139,278\t49.45 minutes to 1.53 hours\t32,302\t2.48 hours to 3.62 days\n2020-06-26\t278,504\t48.98 minutes to 2.29 hours\t20,343\t2.39 hours to 6.99 hours\n2020-10-21\t107,633\t50.80 minutes to 1.54 hours\t20,688\t15.33 minutes to 8.62 hours\n2021-03-20\t158,956\t50.80 minutes to 1.64 hours\t25,760\t2.34 hours to 11.62 hours\n2021-06-26\t547,907\t51.93 minutes to 6.73 hours\t29,728\t2.40 hours to 15.63 hours\n2021-10-10\t170,103\t51.88 minutes to 3.25 hours\t23,989\t2.39 hours to 13.05 hours\n2022-01-31\t354,386\t53.65 minutes to 8.09 hours\t24,391\t2.42 hours to 15.29 hours\n2022-05-09\t172,555\t51.83 minutes to 1.65 hours\t23,289\t2.41 hours to 16.90 hours\n2022-09-05\t153,453\t53.67 minutes to 4.15 hours\t23,594\t2.45 hours to 1.22 days\n2022-12-08\t181,075\t54.83 minutes to 6.67 hours\t27,111\t2.46 hours to 18.89 hours\n2026-02-01\t317,762\t50.30 minutes to 1.52 hours\t47,197\t10.91 hours to 21.30 hours\n2026-05-09\t246,776\t50.12 minutes to 1.52 hours\t35,264\t5.81 hours to 15.60 hours\n2026-08-10\t373,244\t52.05 minutes to 2.07 hours\t45,319\t8.73 hours to 16.52 hours\nNHẬN XÉT CHÍNH:\nDọc theo 21 Các bản sao lưu của Wayback từ 2018-02-03 đến 2026-08-10,, số lượng yêu cầu hoàn tiền hàng ngày dao động từ 60,494 (2018 tháng 5) đến 547,907 (2021 tháng 6) — a 9.1× chênh lệch. Số liệu từ 2026 là 373,244 (+278% so với số liệu tháng 2 tại 2018).\nTrong suốt chín năm đó, giới hạn dưới đã được công bố về thời gian phản hồi hoàn tiền chưa bao giờ rời khỏi mức 49–55 phút dải: tổng thời gian di chuyển dưới sáu phút, trong khi khối lượng công việc đằng sau nó tăng lên gấp chín lần.\nNếu một người dành ra chỉ 5 giây để đọc từng vé, việc xử lý 373,244 vé mỗi ngày (theo số liệu hiện tại) sẽ chiếm 22 các đại lý làm việc tại 24/7 chỉ để mở và đóng chúng; vào giờ cao điểm (547,907, tháng 6 2021) con số này tăng lên 32.\nNếu thời gian phản hồi được công bố phản ánh thời gian xử lý cho mỗi phiếu yêu cầu (~52 phút/phiếu), thì số lượng nhân viên làm việc đồng thời cần thiết sẽ vào khoảng 13,500 đại lý ở mức hiện tại và khoảng20,000 khi đạt đỉnh. Chưa tìm thấy số liệu có nguồn gốc nào về số lượng nhân viên hỗ trợ của Valve; do đó, ở đây không đưa ra con số nào.\nĐiều sau đây: tỷ lệ khối lượng công việc trên số lượng nhân viên không phù hợp với việc kiểm duyệt thủ công từng phiếu yêu cầu trong khoảng thời gian phản hồi đã công bố. Các số liệu này phù hợp với quy trình kiểm duyệt lần đầu chủ yếu được tự động hóa; tỷ lệ phần trăm các phiếu yêu cầu được kiểm duyệt thủ công không được công bố.\nTại sao điều này lại quan trọng đối với việc tuân thủ Đạo luật về Người khuyết tật (GDPR)\n\nGDPR Điều 22 cấm việc ra quyết định đối với từng cá nhân hoàn toàn tự động mà tạo ra các hậu quả pháp lý đáng kể, mà không cung cấp quyền yêu cầu xem xét lại bởi con người khi có yêu cầu. Nếu các quyết định hỗ trợ của Steam (đóng phiếu yêu cầu, xử lý tài khoản, từ chối yêu cầu dữ liệu) được thực hiện hoàn toàn bằng các tập lệnh tự động, thì mọi quyết định như vậy “ảnh hưởng đáng kể” đến người dùng đều có thể vi phạm Điều 22.\n\nVé HT-2YBP-F7JP-D4VB (Mục 18) đã được đóng sau ba ngày với một mẫu chuyển tiếp và không có bất kỳ phản hồi nào liên quan đến cơ sở pháp lý được trích dẫn. Không thể xác định được liệu có ai đã xem xét nội dung này hay không dựa trên phiếu yêu cầu; đó là câu hỏi mà cơ quan giám sát có thể đặt ra cho Valve theo Điều 22 và Điều 15(1)(h).\n\nNguồn: Wayback Machine — các bản chụp nhanh từ store.steampowered.com/stats/support (2018-02-03, 2021-06-26, 2026-08-10) — dữ liệu được trích xuất vào tệp VALVE_EVIDENCE_PACK/databases/steam_support_stats_history.json (21 — các bản chụp nhanh, 2018–2026). Lưu ý: thời gian phản hồi \"~52 phút\" là giới hạn dưới của danh mục hoàn tiền; thời gian phản hồi về bảo mật tài khoản là 2.4–16.5 giờ trên cùng các bản chụp nhanh. 2021-06-26 là mức đỉnh mọi thời đại (547,907 yêu cầu hoàn tiền), không phải là điểm giữa tăng đều — khối lượng đã tăng vọt ~6× trong 2020–2021 sau đó giảm một phần trước khi phục hồi lên 373K trong 2026.\nPhụ lục I — Phạm vi tập dữ liệu · số liệu có thể tái tạo\nĐếm số bản ghi. Kiểm tra phạm vi.\nBối cảnh và các giới hạn về nguồn\n\nHãy đếm số bản ghi, sau đó kiểm chứng các khẳng định: mọi con số dưới đây đều có thể được tính lại từ các tệp đã công bố.\n\nKiểm tra các tập dữ liệu cơ sở, tái tạo các số liệu thống kê và phân biệt các hàng nguồn với các sự cố riêng lẻ.\n\nTệp CSV chính chứa 40,448 hàng. Trong số đó, 36,516 đến từ nguồn tin về lừa đảo (phishing) trên Discord-AntiScam. Phần còn lại 3,932 Các mục này bao gồm các bài viết trên GitHub, các bài đánh giá, kết quả tìm kiếm, nội dung trên diễn đàn và các nguồn khác, cung cấp một chỉ mục toàn diện về các chủ đề được cộng đồng đề cập và các báo cáo bảo mật.\n\nTrong tệp CSV đó, 1,690 các hàng được phân loại dưới nhãn bộ sưu tập “Lỗ hổng bảo mật chưa được vá”, đại diện cho các vấn đề của người dùng trong quá khứ và các thông báo về lỗ hổng bảo mật. Việc truy vết các báo cáo này đòi hỏi phải rà soát dòng thời gian phát triển cụ thể của từng chuỗi thảo luận và lịch sử các bản vá công khai.\n\nKho lưu trữ có thể tìm kiếm “16,319-” là một phiên bản riêng biệt, được biên soạn cẩn thận với danh sách nội dung riêng, được thiết kế để khám phá chi tiết tại chỗ các khiếu nại của người dùng và báo cáo sự cố cụ thể.\n\nTo build a reliable audit trail, every user-reported record must be verified against documented build timelines and historical patch logs.\n\nCác bản ghi sưu tập riêng biệt thuộc Phần II 231,829 Mã danh sách duy nhất, bao gồm 33,509 trong danh mục đăng ký tự động và 198,320 được đánh dấu là các giao dịch chuyển nhượng chưa được xác minh. Giá trị SHA-256 của tệp đầu vào trùng khớp với kết quả đo lường đã lưu giữ. Các số liệu này phản ánh các nỗ lực niêm yết và các giao dịch chuyển nhượng được ghi nhận, chứ không phải giá trị giao dịch đã hoàn tất hay tổng số vụ trộm cắp đã được xác minh, từ đó nhấn mạnh sự cần thiết phải dựa vào hồ sơ gốc của nền tảng để đo lường chính xác tác động kinh tế. Danh sách các giá trị đo lường và hàm băm ↗\n\nNắm vững CSV ↗ · Danh mục lưu trữ có thể tìm kiếm ↗ · Kiểm tra các bản ghi nguồn ↗\n\nPhụ lục J — Giới thiệu về cuộc điều tra này\nValve không công bố bất kỳ hồ sơ thi hành nào. Chúng tôi đã chế tạo một cái.\n\nĐộc lập. Không mang tính thương mại. Được xây dựng hoàn toàn dựa trên dữ liệu công khai. Đã được gửi đến các cơ quan quản lý.\n\n88.97%đội xe tự động hóa vẫn hoạt động bình thường — không có bất kỳ lệnh cấm nào\n67.77%trong số những kẻ lừa đảo đã bị Tòa án Tối cao (51,732) kết án lại được trả tự do\n$26.8M+Mức chi tiêu tối thiểu tại cửa hàng đối với đội xe không thuộc diện giới hạn\n3.6%Các tên miền cờ bạc bị chặn bởi tính năng Lọc liên kết của Valve\n8 nămcác sự cố an ninh đã được ghi nhận\n\nĐây là gì. Một hồ sơ điều tra chi tiết về nền tảng Steam của Công tyValve — bao gồm lịch sử thực thi quy định, hệ sinh thái “card-farming”, khung pháp lý, và cơ sở hạ tầng xác thực mà các nhà điều hành cờ bạc sử dụng thông qua hệ thống chuyển tiếp OpenID của chính Steam. Mọi số liệu đều có thể kiểm chứng được từ hai nguồn: trang API công khai của Valve và các bộ dữ liệu được công bố kèm theo cuộc điều tra này.\n\nĐối tượng dành cho ai. Các cơ quan quản lý có thẩm quyền đối với Valve — Cơ quan giám sát của Cơ quan Quản lý Tài chính Hà Lan (GDPR), FinCEN, Ủy ban Chứng khoán và Giao dịch (SEC), Điều phối viên Dịch vụ Kỹ thuật số theo Đạo luật Dịch vụ Kỹ thuật số (DSA), UOKiK, và bất kỳ cơ quan thực thi pháp luật nào đang điều tra các luồng tài chính liên quan đến Steam. Cũng dành cho các nhà báo, nhà nghiên cứu và mọi người dùng đã bị cấm tài khoản vĩnh viễn, bị từ chối hoàn tiền hoặc bị đánh cắp tài sản trong tài khoản và được thông báo rằng không có quyền kháng cáo.\n\nYêu cầu duy nhất. Valve lưu trữ dữ liệu này với độ chính xác tuyệt đối — kèm theo lý do cấm, không gian ID đầy đủ, theo thời gian thực. Hệ thống có thể thực hiện mọi truy vấn trong hồ sơ này chỉ trong vài giây và đã quyết định không công bố bất kỳ thông tin nào trong đó. Câu hỏi đặt ra cho bất kỳ cơ quan có thẩm quyền nào cũng rất đơn giản: Tại sao không?\n\nĐiều mà các tác giả không khẳng định. Trong quá trình nghiên cứu này, không có thao tác đăng nhập nào vào Steam được thực hiện trên bất kỳ nền tảng bên thứ ba nào. Một URL OpenID được cung cấp chỉ xác định các tham số yêu cầu, chứ không phải là một thao tác đăng nhập đã hoàn tất. Việc sở hữu một tên miền riêng biệt có thể đăng ký không tự nó là bằng chứng cho việc lách luật. Ngày đăng ký là mốc thời gian sớm nhất mà một máy chủ có thể xuất hiện lần đầu tiên trong một yêu cầu OpenID; chúng không chứng minh việc sử dụng liên tục. Các tác giả không khẳng định những gì Valve biết hoặc dự định: mọi tuyên bố về Valve đều được liên kết với một tài liệu công khai có ngày tháng hoặc một quan sát có ngày tháng. Trong trường hợp một tuyên bố không thể được chứng minh bằng tài liệu nguồn, tuyên bố đó đã bị loại bỏ.\n\nChúng tôi là ai\n\nPhishDestroy — các nhà điều tra độc lập. Không có liên hệ nào với Công ty Valve hay bất kỳ nền tảng nào được nêu tên tại đây. Một tài khoản Steam đã được sử dụng duy nhất để ghi chép lại yêu cầu tại GDPR trong Mục 18.\n\nThông báo miễn trừ trách nhiệm pháp lý\n\nCuộc điều tra phi thương mại, phi tập trung vì lợi ích công cộng. Tất cả dữ liệu được cung cấp “nguyên trạng” mà không kèm theo bất kỳ bảo đảm nào. Ấn phẩm này không phải là phán quyết tư pháp.\n\nPHẠM VI CÔNG CỘNG\nCấp phép\n\nTất cả các quyền được nhượng lại cho nhân loại. Được phép sao chép, chỉnh sửa, xuất bản — không cần ghi nguồn. Cấm truy cập tại khu vực thuộc thẩm quyền của OFAC. Giấy phép đầy đủ & tuyên bố miễn trừ trách nhiệm →",
        "headings": [
          {
            "level": 2,
            "id": "briefing-heading",
            "text": "Quy tắc. Kỷ lục. Những câu hỏi chưa có lời giải đáp."
          },
          {
            "level": 2,
            "id": null,
            "text": "Thư ngỏ gửi Ủy ban Cờ bạc Tiểu bang Washington"
          },
          {
            "level": 3,
            "id": "wsgc-public-address-title",
            "text": "Mười ngày bỗng chốc trở thành mười năm.Mở lại bản ghi."
          },
          {
            "level": 2,
            "id": null,
            "text": "Trang web này bị chặn. Tuy nhiên, đường dẫn đăng nhập thì không."
          },
          {
            "level": 3,
            "id": null,
            "text": "Hình 3.1 — Hai tuyến đường được vẽ ra."
          },
          {
            "level": 3,
            "id": null,
            "text": "Cái bẫy “Tầm nhìn tổng thể”: Bộ lọc liên kết chỉ là “hành động tuân thủ cho có lệ”, chứ không phải là lá chắn"
          },
          {
            "level": 3,
            "id": null,
            "text": "Việc tên miền chính bị chặn trong khi máy chủ xác thực lại không bị chặn sẽ khiến đường dẫn đăng nhập vẫn mở — và tình trạng này kéo dài suốt nhiều năm."
          },
          {
            "level": 3,
            "id": null,
            "text": "Bối cảnh: “Steam” là gì và tại sao nó lại quan trọng trong bối cảnh này"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve đã làm gì: Chặn tên miền"
          },
          {
            "level": 3,
            "id": null,
            "text": "Miền proxy là gì?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Điểm then chốt: Máy chủ xác thực được gửi đến Steam trong mỗi yêu cầu"
          },
          {
            "level": 3,
            "id": null,
            "text": "Điều này chứng tỏ điều gì"
          },
          {
            "level": 3,
            "id": null,
            "text": "Trong cuốn sách “Steam”, danh sách của “Valve” là danh sách duy nhất."
          },
          {
            "level": 3,
            "id": null,
            "text": "Vượt qua cơ chế bảo vệ bộ lọc liên kết"
          },
          {
            "level": 3,
            "id": null,
            "text": "Trình duyệt web Big Picture bị rò rỉ cookie đăng nhập và tiết lộ thông tin nhạy cảm (có thể dẫn đến việc chiếm quyền kiểm soát tài khoản)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Điều này có ý nghĩa như thế nào đối với một trẻ vị thành niên đã cài đặt phần mềm diệt virus"
          },
          {
            "level": 3,
            "id": null,
            "text": "Tuổi của tên miền.Ngày thực hiện quan sát."
          },
          {
            "level": 2,
            "id": null,
            "text": "Một điểm cuối đã bị đóng. Hệ thống truy vết công khai đã mất một khóa."
          },
          {
            "level": 3,
            "id": null,
            "text": "Thời kỳ trước khi mất điện"
          },
          {
            "level": 3,
            "id": null,
            "text": "Sau khi thay đổi"
          },
          {
            "level": 2,
            "id": null,
            "text": "Một phiên làm việc. Quyền truy cập rộng hơn so với những gì người dùng nhìn thấy."
          },
          {
            "level": 3,
            "id": null,
            "text": "1. Xác thực tăng cường không đầy đủ"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. Thiếu nguyên tắc quyền hạn tối thiểu"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. Lỗi trong quản lý phiên làm việc"
          },
          {
            "level": 3,
            "id": null,
            "text": "4. Việc chặn các máy chủ xác thực ở cấp miền là khả thi về mặt kỹ thuật"
          },
          {
            "level": 3,
            "id": "integration-paradox-title",
            "text": "Valve hàng ngày đều tuân thủ các quy tắc này. Nhưng ở đây thì nó lại không tuân thủ các quy tắc đó."
          },
          {
            "level": 4,
            "id": null,
            "text": "GitHub Phạm vi chi tiết so với phạm vi tổng quát (Valve) Steam Trang web API"
          },
          {
            "level": 2,
            "id": null,
            "text": "Trình mô phỏng khai thác và chiếm quyền điều khiển tương tác"
          },
          {
            "level": 2,
            "id": null,
            "text": "Các điểm cuối nằm phía sau chuỗi."
          },
          {
            "level": 2,
            "id": null,
            "text": "Một ô đã được đánh dấu. Hành động của ai?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Cách \"Valve\" cuối cùng đã vô hiệu hóa \"thay thế thương mại\" — Và tại sao \"7\" lại phải mất nhiều năm để tìm cách giải quyết tạm thời"
          },
          {
            "level": 4,
            "id": null,
            "text": "Thời gian hồi chiêu của Avatar và Tên (2024 tháng 2)"
          },
          {
            "level": 4,
            "id": null,
            "text": "7-Ngày đảo chiều giao dịch CS2 (2025 tháng 7)"
          },
          {
            "level": 4,
            "id": null,
            "text": "Thông báo đẩy bắt buộc trên thiết bị di động dành cho các nhà phát triển ứng dụng (API) (2023 tháng 12)"
          },
          {
            "level": 4,
            "id": null,
            "text": "Biểu ngữ về thời gian hoạt động và tên tài khoản (2022–2024)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Bộ quy tắc của họ. Các nền tảng đã được ghi lại."
          },
          {
            "level": 3,
            "id": "enforcement-focus-title",
            "text": "Một bộ quy tắc. Việc thi hành không công bằng."
          },
          {
            "level": 4,
            "id": null,
            "text": "Tự động hóa"
          },
          {
            "level": 4,
            "id": null,
            "text": "Sử dụng cho mục đích thương mại"
          },
          {
            "level": 4,
            "id": null,
            "text": "VPN và ẩn vị trí"
          },
          {
            "level": 4,
            "id": null,
            "text": "Che giấu liên kết"
          },
          {
            "level": 4,
            "id": null,
            "text": "Khi bộ phận hỗ trợ đóng hồ sơ, ai sẽ xem xét lại quyết định đó?"
          },
          {
            "level": 2,
            "id": null,
            "text": "Một quy tắc tự động hóa API. Một quy tắc cấm tự động hóa."
          },
          {
            "level": 3,
            "id": null,
            "text": "Lầm tưởng về “nhà phát triển trò chơi”"
          },
          {
            "level": 4,
            "id": null,
            "text": "Mâu thuẫn trong tự động hóa"
          },
          {
            "level": 4,
            "id": null,
            "text": "Vị trí phía máy chủ trong quy trình giao dịch"
          },
          {
            "level": 2,
            "id": null,
            "text": "Mười ngày được yêu cầu. Mười năm để giải trình."
          },
          {
            "level": 3,
            "id": "letter-company",
            "text": "CÔNG TY VALVE"
          },
          {
            "level": 3,
            "id": null,
            "text": "Mười ngày.Vậy thì sao?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Hãy tuân theo máy chủ trả về đã được chỉ định."
          },
          {
            "level": 3,
            "id": "washington-record-heading",
            "text": "Hai thời hạn. Một tiêu chuẩn thi hành vẫn chưa được làm rõ."
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve cung cấp cho các trang web cá cược 10 ngày"
          },
          {
            "level": 4,
            "id": null,
            "text": "Washington gây áp lực lên Valve"
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve bác bỏ cáo buộc"
          },
          {
            "level": 4,
            "id": null,
            "text": "Các tuyến đường được ghi nhận vào tháng 9 năm 2026"
          },
          {
            "level": 4,
            "id": null,
            "text": "Mười tám tháng sau khi Công ty Dịch vụ Bưu chính và Viễn thông (Valve) gửi phản hồi, cơ quan quản lý vẫn coi đó là một ý định."
          },
          {
            "level": 3,
            "id": null,
            "text": "Thập kỷ “10--Day Notice”: Kiểm toán khả năng tồn tại về mặt pháp y đối với các địa điểm được nêu tên trong “23”"
          },
          {
            "level": 4,
            "id": null,
            "text": "Từ các cảnh báo về “10-” đến các tập đoàn đa quốc gia: Doanh thu hàng tỷ đô la"
          },
          {
            "level": 2,
            "id": null,
            "text": "Tên máy chủ đã có sẵn trong yêu cầu."
          },
          {
            "level": 3,
            "id": null,
            "text": "Các tiền lệ đã được ghi chép và báo cáo"
          },
          {
            "level": 3,
            "id": null,
            "text": "Những thông tin mà ngày đăng ký thể hiện và không thể hiện"
          },
          {
            "level": 3,
            "id": null,
            "text": "Kiểm toán so sánh: Tiêu chuẩn tuân thủ của Tổ chức Hợp tác và Phát triển Kinh tế (API)"
          },
          {
            "level": 2,
            "id": "market-thesis-heading",
            "text": "Chênh lệch giá so với mức giá trên trang webSteam"
          },
          {
            "level": 2,
            "id": null,
            "text": "Chênh lệch giá là có thể đo lường được."
          },
          {
            "level": 3,
            "id": null,
            "text": "Con số này cho thấy điều gì"
          },
          {
            "level": 3,
            "id": null,
            "text": "Nhiều địa điểm niêm yết mức giá cao hơn so với “Steam”."
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam vẫn dẫn đầu về số lượng lời đề nghị."
          },
          {
            "level": 3,
            "id": null,
            "text": "Hệ sinh thái thương mại đang hiện hữu rõ ràng trước mắt."
          },
          {
            "level": 2,
            "id": null,
            "text": "Ai có thể thiết lập lại các biện pháp bảo vệ?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Một phiếu khôi phục đã vô hiệu hóa tính năng bảo mật của tài khoản, cùng với khoản thiệt hại được báo cáo là $10,000"
          },
          {
            "level": 3,
            "id": null,
            "text": "Vượt ra ngoài phạm vi hàng tồn kho."
          },
          {
            "level": 3,
            "id": "theft-ledger-title",
            "text": "Valve Cánh cửa đã được mở ra hai lần, cách nhau ba mươi ba tháng. Nó chưa bao giờ đóng lại."
          },
          {
            "level": 4,
            "id": null,
            "text": "Những gì sổ cái ghi lại là điều mà không một trường hợp cụ thể nào có thể làm được."
          },
          {
            "level": 3,
            "id": null,
            "text": "Tính bảo mật phải đi kèm với trách nhiệm giải trình về mặt kỹ thuật."
          },
          {
            "level": 2,
            "id": null,
            "text": "Theo dõi dòng tiền. Phân tách các giao dịch."
          },
          {
            "level": 3,
            "id": null,
            "text": "Nơi dòng tiền thực sự lưu chuyển."
          },
          {
            "level": 3,
            "id": null,
            "text": "Hãy phân loại hoạt động trước, sau đó mới đến nghĩa vụ."
          },
          {
            "level": 3,
            "id": null,
            "text": "Theo dõi nguồn thu, kiến thức và sự hỗ trợ."
          },
          {
            "level": 2,
            "id": null,
            "text": "Đạo luật Dịch vụ Kỹ thuật số: ghi nhận kiến thức vào hồ sơ"
          },
          {
            "level": 3,
            "id": null,
            "text": "Yêu cầu kéo dài mười ngày."
          },
          {
            "level": 3,
            "id": null,
            "text": "Khoảng thời gian DSA."
          },
          {
            "level": 3,
            "id": null,
            "text": "Thời gian thực hiện cần có hồ sơ theo dõi."
          },
          {
            "level": 3,
            "id": null,
            "text": "trong tổng doanh thu hàng năm trên toàn cầu"
          },
          {
            "level": 2,
            "id": null,
            "text": "Người chưa thành niên: Việc đăng nhập vào Steam không phải là hình thức xác minh độ tuổi"
          },
          {
            "level": 3,
            "id": null,
            "text": "Xác định toán tử và dữ liệu."
          },
          {
            "level": 3,
            "id": null,
            "text": "Ghi lại toàn bộ quá trình từ khi đăng nhập đến khi nạp tiền."
          },
          {
            "level": 2,
            "id": null,
            "text": "Yêu cầu. Phản hồi. So sánh còn thiếu."
          },
          {
            "level": 3,
            "id": null,
            "text": "Các hồ sơ đó vẫn còn tồn tại; nhưng chủ thể dữ liệu chưa nhận được chúng."
          },
          {
            "level": 2,
            "id": null,
            "text": "Thỏa thuận đăng ký trái với kiến trúc riêng của nền tảng"
          },
          {
            "level": 3,
            "id": null,
            "text": "Giới hạn giá thị trường và quy định cấm sử dụng vào mục đích thương mại"
          },
          {
            "level": 3,
            "id": null,
            "text": "Lỗ hổng bảo mật liên quan đến khóa (API) là một vấn đề về thiết kế nền tảng chứ không phải do sự bất cẩn của người dùng"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve nhận tên máy chủ xác thực mỗi khi đăng nhập"
          },
          {
            "level": 3,
            "id": null,
            "text": "Mô hình trong các đơn khiếu nại đã được lưu trữ"
          },
          {
            "level": 3,
            "id": null,
            "text": "Một tòa án xem xét hồ sơ này sẽ không diễn giải Đạo luật An sinh Xã hội (SSA) một cách tách biệt."
          },
          {
            "level": 2,
            "id": null,
            "text": "Các kết quả. Các tài liệu mà chúng tôi yêu cầu."
          },
          {
            "level": 2,
            "id": null,
            "text": "Bản tóm tắt bằng chứng — tài liệu do Nguồn cung cấp 1"
          },
          {
            "level": 2,
            "id": null,
            "text": "Việc che giấu trong tệp PDF được tạo ra chỉ mang tính hình thức: phần văn bản bị che vẫn có thể trích xuất được"
          },
          {
            "level": 2,
            "id": null,
            "text": "Tài liệu chứng cứ liên quan đến hỗ trợ và trao đổi pháp lý"
          },
          {
            "level": 2,
            "id": null,
            "text": "Các tài liệu gốc được lựa chọn"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-01",
            "text": "Hardware keys, requested in 2016"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-02",
            "text": "Crash reports without an effective opt-out"
          },
          {
            "level": 3,
            "id": "receipt-heading-gh-03",
            "text": "Auth-ticket abuse reported to Valve"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-01",
            "text": "44 disputed Market purchases"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-02",
            "text": "A permanent ban and closed appeals"
          },
          {
            "level": 3,
            "id": "receipt-heading-rd-03",
            "text": "A recovery reset and a reported $10,000 loss"
          },
          {
            "level": 2,
            "id": null,
            "text": "ArchiSteamFarm và điều khoản tự động hóa"
          },
          {
            "level": 2,
            "id": null,
            "text": "Sổ quy tắc: các điều khoản chống lại các nền tảng được ghi nhận"
          },
          {
            "level": 3,
            "id": "ledger-title",
            "text": "Sử dụng cho mục đích thương mại và tính phí tài khoản"
          },
          {
            "level": 3,
            "id": "lw-register-title",
            "text": "Đăng ký nền tảng 175"
          },
          {
            "level": 4,
            "id": null,
            "text": "Gánh nặng chứng minh"
          },
          {
            "level": 4,
            "id": null,
            "text": "Bản ghi được gắn thẻ là gì, và không phải là gì"
          },
          {
            "level": 2,
            "id": null,
            "text": "Cẩm nang DSAR: Yêu cầu cung cấp bằng chứng"
          },
          {
            "level": 3,
            "id": null,
            "text": "Hãy lưu giữ dòng thời gian của bạn."
          },
          {
            "level": 3,
            "id": null,
            "text": "Yêu cầu cung cấp dữ liệu đã được lưu trữ của bạn."
          },
          {
            "level": 3,
            "id": null,
            "text": "Hãy lưu giữ biên bản giao hàng."
          },
          {
            "level": 3,
            "id": null,
            "text": "Hãy so sánh các câu trả lời."
          },
          {
            "level": 3,
            "id": null,
            "text": "Bảo mật tài khoản và lịch sử truy cập"
          },
          {
            "level": 3,
            "id": null,
            "text": "Sự không khớp là bằng chứng cần được điều tra."
          },
          {
            "level": 2,
            "id": null,
            "text": "Khối lượng hỗ trợ. Thời gian phản hồi đã công bố."
          },
          {
            "level": 3,
            "id": null,
            "text": "Hai hàng người chờ tại một quầy hỗ trợ, như có thể thấy qua các ảnh chụp màn hình được lưu trữ trên 21."
          },
          {
            "level": 2,
            "id": null,
            "text": "Đếm số bản ghi. Kiểm tra phạm vi."
          },
          {
            "level": 2,
            "id": null,
            "text": "Valve không công bố bất kỳ hồ sơ thi hành nào.\nChúng tôi đã chế tạo một cái."
          }
        ],
        "links": [
          "https://dotesports.com/counter-strike/news/csgo-lounge-billion-bets-3896",
          "https://store.steampowered.com/agreement/?l=english",
          "http://web.archive.org/web/20260921022032/https://store.steampowered.com/agreement/?l=english",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-all-results.json",
          "https://blog.counter-strike.net/expresstrade/",
          "http://web.archive.org/web/20260307161538/https://blog.counter-strike.net/expresstrade/",
          "https://wsgc.wa.gov/news/2016/washington-state-gambling-commission-orders-valve-stop-skins-gambling",
          "http://web.archive.org/web/20260520012601/https://wsgc.wa.gov/news/2016/washington-state-gambling-commission-orders-valve-stop-skins-gambling",
          "https://fr.scribd.com/document/328063293/Valve-s-Oct-18th-response-to-Washington-State-Gambling-Commission-s-cease-and-desist",
          "https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921021947/https://store.steampowered.com/oldnews/22883",
          "http://web.archive.org/web/20260921022628/https://steamcommunity.com/linkfilter/?url=https:%2F%2Frollbit.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rbsnin.com.20260921T021120Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rollbit.com.json",
          "http://web.archive.org/web/20260921022740/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fskin.club",
          "http://web.archive.org/web/20260921022842/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fsc-auth.net",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skin.club.json",
          "http://web.archive.org/web/20260921022603/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fhowl.gg",
          "http://web.archive.org/web/20260921022636/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fhowl.uno",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/howl.gg.json",
          "http://web.archive.org/web/20260921022840/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fduelbits.com",
          "http://web.archive.org/web/20260921022901/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fswitchflips.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/duelbits.com.json",
          "http://web.archive.org/web/20260921022758/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgofast.com",
          "http://web.archive.org/web/20260921022847/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fauthtofast.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgofast.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/farmskins.com.20260921T025840Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/steam.kobal.cc.20260921T025844Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/farmskins.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cobaltlab.tech.20260921T041604Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cobaltauth.com.20260921T041608Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/cobaltlab.tech.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgo.net.20260921T041619Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cn2.easylot.net.20260921T041623Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgo.net.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/ggdrop.com.20260921T041637Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/ggauth.com.20260921T041641Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/ggdrop.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rustchance.com.20260921T041703Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/hgfuihd.com.20260921T041706Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rustchance.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skin.fans.20260921T041710Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.skinfans.com.20260921T041713Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skin.fans.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinport.com.20260921T041724Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinport.app.20260921T041728Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skinport.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skins.cash.20260921T041731Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinscash.live.20260921T041735Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skins.cash.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2hunt.com.20260921T041739Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rstspcl.com.20260921T041742Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tf2hunt.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgogem.com.20260922T192355Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/api.csgem.com.20260922T192358Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-2026-09-22.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/gamdom.com.20260922T192326Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/login.gambldom.com.20260922T192330Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/12cs.fail.20260922T192347Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/fail.games.20260922T192351Z.html",
          "http://web.archive.org/web/20260921022953/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgoempire.com",
          "http://web.archive.org/web/20260921022947/https://steamcommunity.com/linkfilter/?url=https:%2F%2Fcsgoempirelogin4.com",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csgoempire.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/cs.money.20260921T021131Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.dota.trade.20260921T021134Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/cs.money.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csfloat.com.20260921T041612Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgofloat.com.20260921T041615Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/csfloat.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/g4skins.com.20260921T041630Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/auth.g4s.to.20260921T041634Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/g4skins.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/juice.gg.20260921T041644Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/letmeinjuice.com.20260921T041648Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/juice.gg.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/market.csgo.com.20260921T041652Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2.net.20260921T041655Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/market.csgo.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/rust.tm.20260921T041659Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/rust.tm.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/csgolounge.com.20260922T192333Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2.net.20260922T192340Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/dota2lounge.com.20260922T192337Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinbaron.de.20260921T041717Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/skinbaron.com.20260921T041721Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/skinbaron.de.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2royal.com.20260921T041746Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tf2auth.com.20260921T041750Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tf2royal.com.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/tradeit.gg.20260921T041753Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/connect-tradeit.com.20260921T041757Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/tradeit.gg.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/upgrader.pro.20260921T041801Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-raw/upgauth.space.20260921T041804Z.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/upgrader.pro.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-recheck-2026-09-21.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/domain-registration.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wayback-snapshots.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-2026-09-22c.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/master_registry.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/longitudinal-steam-phishing-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-steam-phishing-100.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-coverage-2026-09-22.json",
          "https://blog.csfloat.com/how-floatdb-tracks-items/",
          "http://web.archive.org/web/20260921022415/https://blog.csfloat.com/how-floatdb-tracks-items/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/platform-audit.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/platforms-removed.json",
          "https://hackerone.com/reports/291750",
          "http://web.archive.org/web/20251116185046/https://hackerone.com/reports/291750",
          "https://hackerone.com/reports/1079561",
          "http://web.archive.org/web/20260924181830/https://hackerone.com/reports/1079561",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/hackerone-reports.json",
          "https://phishdestroy.io/steam_dossier/vi/steam_enforcement_evidence.html#support-records",
          "https://www.darknavy.org/blog/exploiting_steam_usual_and_unusual_ways_in_the_cef_framework/",
          "https://steamcommunity.com/groups/SteamClientBeta/discussions/0/3365901765276206401/",
          "http://web.archive.org/web/20250804051514/https://steamcommunity.com/groups/SteamClientBeta/discussions/0/3365901765276206401/",
          "https://www.chromium.org/developers/design-documents/safebrowsing/",
          "http://web.archive.org/web/20260821101616/https://www.chromium.org/developers/design-documents/safebrowsing/",
          "https://www.chromium.org/developers/how-tos/api-keys/",
          "http://web.archive.org/web/20260830122831/https://www.chromium.org/developers/how-tos/api-keys/",
          "https://github.com/Homebrew/homebrew-cask/issues/193814",
          "https://testsafebrowsing.appspot.com/",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/domain-registration.json",
          "https://phishdestroy.io/steam_dossier/vi/AUTH_AUDIT.md",
          "https://datatracker.ietf.org/doc/rfc6749/",
          "https://docs.cloud.google.com/docs/authentication/api-keys",
          "https://listings.pcisecuritystandards.org/pdfs/PCI_DSS_Resource_Guide_(003).pdf",
          "https://developer.apple.com/news/?id=02202019a",
          "http://web.archive.org/web/20250506070026/https://developer.apple.com/news/?id=02202019a",
          "https://dev.twitch.tv/docs/authentication/validate-tokens/",
          "https://discuss.dev.twitch.com/t/legacy-twitch-api-v5-i-e-kraken-shutdown-reminder-february-28-2022/36589",
          "http://web.archive.org/web/20250127085635/https://discuss.dev.twitch.com/t/legacy-twitch-api-v5-i-e-kraken-shutdown-reminder-february-28-2022/36589",
          "https://store.steampowered.com/news/posts/?enddate=1788390000",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/4123547285514022851",
          "https://skinvault.gg/blog/cs2-trade-protection-explained/",
          "https://csmarketcap.com/blog/market-insights/from-boom-to-bust-cs2s-trade-protection-impact",
          "https://skin.land/blog/steam-changes-cs2-trade-ban-logic-timing/",
          "https://help.steampowered.com/faqs/view/3041-A87A-E5F6-B6AC",
          "https://steamcommunity.com/ogg/593110/announcements/detail/533224478739530146",
          "https://steamcommunity.com/games/CSGO/announcements/detail/4447966961421256740",
          "https://steamcommunity.com/sharedfiles/filedetails/?id=2926756889",
          "https://steamcommunity.com/dev/apikey",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3734103130194459461",
          "https://steamcommunity.com/discussions/forum/1/3807266184852932971/",
          "https://help.steampowered.com/faqs/view/225C-C51E-B8F0-55B2",
          "https://store.steampowered.com/news/group/4/view/3314112260640237775",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/issues/325",
          "https://blog.dota2.com/2020/05/trading-cooldown/",
          "https://blog.counter-strike.net/index.php/2018/03/20308/",
          "http://web.archive.org/web/20250226114333/https://blog.counter-strike.net/index.php/2018/03/20308/",
          "https://phishdestroy.io/steam_dossier/vi/steam_evidence_archive.html",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/493839547938902179",
          "https://store.steampowered.com/online_conduct",
          "http://web.archive.org/web/20260921022120/https://store.steampowered.com/online_conduct",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260918014700/https://store.steampowered.com/subscriber_agreement/",
          "https://steamcommunity.com/dev/apiterms",
          "http://web.archive.org/web/20260921022210/https://steamcommunity.com/dev/apiterms",
          "https://help.steampowered.com/en/faqs/view/628C-E332-BD8C-4D36",
          "https://phishdestroy.io/steam_dossier/vi/social_graph.html",
          "https://phishdestroy.io/steam_dossier/vi/security_timeline.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wsgc-skins-gambling-briefing-2018.pdf",
          "https://wsgc.wa.gov/sites/default/files/2023-10/Skins%20Gambling.pdf",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/wsgc-briefing-manifest.json",
          "https://x.com/csgobig",
          "https://www.facebook.com/csgobigofficial/",
          "https://500.casino/",
          "https://csgolounge.com/",
          "https://csgocasino.gg/",
          "https://x.com/CSGOatsecom",
          "https://x.com/CSGOSweep/status/937420902538543106",
          "https://x.com/Wild",
          "https://x.com/csgopot",
          "https://x.com/csgodiamondscom",
          "https://www.ftc.gov/legal-library/browse/cases-proceedings/162-3184-csgo-lotto-matter",
          "https://x.com/CSGODouble",
          "https://x.com/csgo_massive",
          "https://www.facebook.com/csgostrongfree/",
          "https://www.facebook.com/CSNCOM/",
          "https://www.gamblingcommission.gov.uk/report/young-people-and-gambling",
          "https://www.aph.gov.au/Parliamentary_Business/Committees/Senate/Environment_and_Communications/Gamingmicro-transactions",
          "https://phishdestroy.io/steam_dossier/vi/elite_skins.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/csfloat-catalogue.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/skinport-floor-over-cap.json",
          "https://pricempire.com/cs2-marketplaces",
          "http://web.archive.org/web/20260921022459/https://pricempire.com/cs2-marketplaces",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/priceempire-marketplaces.json",
          "https://www.steamanalyst.com/marketplace",
          "http://web.archive.org/web/20260719014552/https://www.steamanalyst.com/marketplace",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-atlas.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json",
          "https://phishdestroy.io/steam_dossier/vi/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/vi/steam_enforcement_evidence.html#case-support-recovery",
          "https://top10.owasp.org/2025/A01_2025-Broken_Access_Control/",
          "http://web.archive.org/web/20260920212535/https://top10.owasp.org/2025/A01_2025-Broken_Access_Control/",
          "https://store.steampowered.com/privacy_agreement/",
          "http://web.archive.org/web/20260921021648/https://store.steampowered.com/privacy_agreement/",
          "https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "http://web.archive.org/web/20250818113925/https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "https://www.dexerto.com/counter-strike-2/valve-saves-hacked-cs2-player-threatened-with-ransom-over-300000-of-rare-stickers-3283135/",
          "https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "http://web.archive.org/web/20220702042821/https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "https://www.kaspersky.com/blog/cs-go-two-million-usd-inventory-hack/44697/",
          "https://esportfire.com/article/the-2-million-usd-csgo-hack-22062022",
          "http://web.archive.org/web/20260515110250/https://esportfire.com/article/the-2-million-usd-csgo-hack-22062022",
          "https://esportsbetting.com/valve-deletes-130000-stolen-dragon-lore/",
          "https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "http://web.archive.org/web/20251115173120/https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "https://vkplay.ru/media/news/bloger-rasskazal-kak-podderzhka-steam-vorovala-akkaunty-igrokov/",
          "https://lis-skins.com/ru/blog/krupneisaia-mosenniceskaia-sxema-v-istorii-steam/",
          "https://escorenews.com/ru/csgo/news/44056-sotrudniki-podderjki-steam-zanimalis-krajey-skinov-s-akkauntov-za-god-oni-zarabotali-svyshe-300-tysyach-dollarov",
          "https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "http://web.archive.org/web/20250805141942/https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/outsourcing-archive-records.json",
          "https://community.skin.club/en/news/collector-has-steam-inventory-returned-after-bold-hack",
          "https://esportfire.com/article/300k-scam-full-katowice-2014-holo-collection-hacked",
          "http://web.archive.org/web/20251217072445/https://esportfire.com/article/300k-scam-full-katowice-2014-holo-collection-hacked",
          "https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng",
          "http://web.archive.org/web/20260920024236/https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng",
          "https://ag.ny.gov/press-release/2026/attorney-general-james-sues-game-developer-promoting-illegal-gambling-through",
          "http://web.archive.org/web/20260901015430/https://ag.ny.gov/press-release/2026/attorney-general-james-sues-game-developer-promoting-illegal-gambling-through",
          "https://www.fincen.gov/sites/default/files/2019-05/FinCEN%20CVC%20Guidance%20FINAL.pdf",
          "http://web.archive.org/web/20250711185007/https://www.fincen.gov/sites/default/files/2019-05/FinCEN%20CVC%20Guidance%20FINAL.pdf",
          "https://eur-lex.europa.eu/legal-content/EN/LSU/?uri=CELEX:32018L1673",
          "https://eur-lex.europa.eu/eli/dir/2024/1640/oj/eng",
          "http://web.archive.org/web/20260830153004/https://eur-lex.europa.eu/eli/dir/2024/1640/oj/eng",
          "https://eur-lex.europa.eu/eli/reg/2022/2065/oj/eng",
          "http://web.archive.org/web/20260920080125/https://eur-lex.europa.eu/eli/reg/2022/2065/oj/eng",
          "https://phishdestroy.io/steam_dossier/vi/legal_analysis.html",
          "https://partner.steamgames.com/doc/features/auth#website",
          "http://web.archive.org/web/20260921022335/https://partner.steamgames.com/doc/features/auth",
          "https://www.ftc.gov/legal-library/browse/rules/childrens-online-privacy-protection-rule-coppa",
          "http://web.archive.org/web/20260921070051/https://www.ftc.gov/legal-library/browse/rules/childrens-online-privacy-protection-rule-coppa",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/gdpr-ticket-1.png",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/screenshot-manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/gdpr-ticket-2.png",
          "https://datenschutz.hamburg.de/beschwerde",
          "https://edpb.europa.eu/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/regulatory-review/disclosure-audit.json",
          "https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "http://web.archive.org/web/20260821155801/https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "https://phishdestroy.io/steam_dossier/vi/index#exhibit-gallery-section",
          "https://github.com/ValveSoftware/steam-for-linux/issues/4521",
          "https://phishdestroy.io/steam_dossier/vi/steam_evidence_archive.html?source=GitHub&record=484",
          "https://github.com/ValveSoftware/steam-for-linux/issues/6459",
          "http://web.archive.org/web/20260419051343/https://github.com/ValveSoftware/steam-for-linux/issues/6459",
          "https://phishdestroy.io/steam_dossier/vi/steam_evidence_archive.html?source=GitHub&record=467",
          "https://github.com/ValveSoftware/Source-1-Games/issues/3857",
          "https://phishdestroy.io/steam_dossier/vi/steam_evidence_archive.html?source=GitHub&record=768",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "http://web.archive.org/web/20250320082450/https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://phishdestroy.io/steam_dossier/vi/steam_evidence_archive.html?source=Reddit&record=4533",
          "https://www.reddit.com/r/ohnePixel/comments/1hahqx2/permanently_banned_steam_account_without_a_clear/",
          "https://phishdestroy.io/steam_dossier/vi/steam_evidence_archive.html?source=Reddit&record=4766",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://phishdestroy.io/steam_dossier/vi/steam_evidence_archive.html?source=Reddit&record=4592",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/selected-evidence-records.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive_manifest.json",
          "https://phishdestroy.io/steam_dossier/vi/card_economy.html",
          "https://github.com/JustArchiNET/ArchiSteamFarm/wiki/FAQ",
          "https://phishdestroy.io/steam_dossier/vi/card_economy.html#scale",
          "https://phishdestroy.io/steam_dossier/vi/card_economy.html#licence",
          "https://phishdestroy.io/steam_dossier/vi/enforcement_audit.html",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "http://web.archive.org/web/20260924181709/https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://rdap.verisign.com/com/v1/domain/csgoempire.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoempire.com",
          "https://rdap.verisign.com/com/v1/domain/csgoempirelogin4.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/csgoempire.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustreaper.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustreaper.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/rustreaper.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustly.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustly.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/rustly.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgofast.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgofast.com",
          "https://rdap.verisign.com/com/v1/domain/authtofast.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/csgofast.com.json",
          "https://rdap.verisign.com/com/v1/domain/duelbits.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fduelbits.com",
          "https://rdap.verisign.com/com/v1/domain/switchflips.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/duelbits.com.json",
          "https://rdap.verisign.com/com/v1/domain/farmskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffarmskins.com",
          "https://tld-rdap.verisign.com/cc/v1/domain/kobal.cc",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/farmskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoluck.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoluck.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/csgoluck.com.json",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/domain-registry/insane.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Finsane.gg",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/insane.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs2skin.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs2skin.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/cs2skin.com.json",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/domain-registry/juice.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fjuice.gg",
          "https://rdap.verisign.com/com/v1/domain/letmeinjuice.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/juice.gg.json",
          "https://rdap.verisign.com/com/v1/domain/ggdrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fggdrop.com",
          "https://rdap.verisign.com/com/v1/domain/ggauth.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/ggdrop.com.json",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/domain-registry/howl.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhowl.gg",
          "https://rdap.radix.host/rdap/domain/howl.uno",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/howl.gg.json",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/domain-registry/chicken.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fchicken.gg",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/chicken.gg.json",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/domain-registry/csgocasino.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgocasino.gg",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/csgocasino.gg.json",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/domain-registry/hunt.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhunt.gg",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/hunt.gg.json",
          "https://rdap.verisign.com/com/v1/domain/csbattle.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsbattle.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/csbattle.com.json",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/domain-registry/skinrave.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinrave.gg",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/skinrave.gg.json",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/domain-registry/csdouble.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsdouble.gg",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/csdouble.gg.json",
          "https://rdap.verisign.com/com/v1/domain/rustchance.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustchance.com",
          "https://rdap.verisign.com/com/v1/domain/hgfuihd.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/rustchance.com.json",
          "https://rdap.radix.host/rdap/domain/cobaltlab.tech",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcobaltlab.tech",
          "https://rdap.verisign.com/com/v1/domain/cobaltauth.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/cobaltlab.tech.json",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/domain-registry/raided.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fraided.gg",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/raided.gg.json",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/domain-registry/rustneo.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustneo.gg",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/rustneo.gg.json",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/domain-registry/splits.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsplits.gg",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/splits.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/upgrader.pro",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fupgrader.pro",
          "https://rdap.radix.host/rdap/domain/upgauth.space",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/upgrader.pro.json",
          "https://rdap.centralnic.com/fans/domain/skin.fans",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.fans",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/skin.fans.json",
          "https://rdap.nic.one/domain/hotpizza.one",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhotpizza.one",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/hotpizza.one.json",
          "https://rdap.verisign.com/com/v1/domain/g4skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg4skins.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/g4skins.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2royal.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2royal.com",
          "https://rdap.verisign.com/com/v1/domain/tf2auth.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/tf2royal.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2hunt.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2hunt.com",
          "https://rdap.verisign.com/com/v1/domain/rstspcl.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/tf2hunt.com.json",
          "https://rdap.identitydigital.services/rdap/domain/tf2.bet",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2.bet",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/tf2.bet.json",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/domain-registry/openstars.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fopenstars.gg",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/openstars.gg.json",
          "https://rdap.verisign.com/com/v1/domain/skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/skins.com.json",
          "https://rdap.identitydigital.services/rdap/domain/white.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwhite.market",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/white.market.json",
          "https://rdap.identitydigital.services/rdap/domain/moon.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmoon.market",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/moon.market.json",
          "https://rdap.verisign.com/com/v1/domain/csfloat.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsfloat.com",
          "https://rdap.verisign.com/com/v1/domain/csgofloat.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/csfloat.com.json",
          "https://rdap.identitydigital.services/rdap/domain/skin.land",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.land",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/skin.land.json",
          "https://rdap.verisign.com/com/v1/domain/haloskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhaloskins.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/haloskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/163.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuff.163.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/buff.163.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmarket.csgo.com",
          "https://rdap.verisign.com/net/v1/domain/dota2.net",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/market.csgo.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinport.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinport.com",
          "https://pubapi.registry.google/rdap/domain/skinport.app",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/skinport.com.json",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/domain-registry/skinflow.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinflow.gg",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/skinflow.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/skin.place",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.place",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/skin.place.json",
          "https://rdap.verisign.com/com/v1/domain/skinsmonkey.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinsmonkey.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/skinsmonkey.com.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbaron.de",
          "https://rdap.verisign.com/com/v1/domain/skinbaron.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/skinbaron.de.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frust.tm",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/rust.tm.json",
          "https://rdap.verisign.com/com/v1/domain/pirateswap.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fpirateswap.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/pirateswap.com.json",
          "https://rdap.radix.host/rdap/domain/mannco.store",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmannco.store",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/mannco.store.json",
          "https://rdap.verisign.com/com/v1/domain/skinswap.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinswap.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/skinswap.com.json",
          "https://rdap.verisign.com/com/v1/domain/exeskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fexeskins.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/exeskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/balticskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbalticskins.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/balticskins.com.json",
          "https://rdap.nic.trade/domain/cs.trade",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.trade",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/cs.trade.json",
          "https://rdap.verisign.com/com/v1/domain/rapidskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frapidskins.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/rapidskins.com.json",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/domain-registry/tradeit.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftradeit.gg",
          "https://rdap.verisign.com/com/v1/domain/connect-tradeit.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/tradeit.gg.json",
          "https://rdap.verisign.com/com/v1/domain/49skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F49skins.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/49skins.com.json",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/domain-registry/skinvault.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinvault.gg",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/skinvault.gg.json",
          "https://rdap.identitydigital.services/rdap/domain/aim.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Faim.market",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/aim.market.json",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/domain-registry/skinout.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinout.gg",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/skinout.gg.json",
          "https://rdap.verisign.com/com/v1/domain/ntskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fntskins.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/ntskins.com.json",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/domain-registry/gamerpay.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamerpay.gg",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/gamerpay.gg.json",
          "https://rdap.nic.tf/domain/scrap.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fscrap.tf",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/scrap.tf.json",
          "https://rdap.nic.tf/domain/marketplace.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmarketplace.tf",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/marketplace.tf.json",
          "https://rdap.identitydigital.services/rdap/domain/skins.cash",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.cash",
          "https://rdap.identitydigital.services/rdap/domain/skinscash.live",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/skins.cash.json",
          "https://rdap.verisign.com/net/v1/domain/csgo.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo.net",
          "https://rdap.verisign.com/net/v1/domain/easylot.net",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/csgo.net.json",
          "https://rdap.verisign.com/net/v1/domain/cybershoke.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcybershoke.net",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/cybershoke.net.json",
          "https://rdap.verisign.com/net/v1/domain/fastcup.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffastcup.net",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/fastcup.net.json",
          "https://rdap.verisign.com/com/v1/domain/leetify.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fleetify.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/leetify.com.json",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/domain-registry/scope.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fscope.gg",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/scope.gg.json",
          "https://rdap.verisign.com/com/v1/domain/tradeupspy.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftradeupspy.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/tradeupspy.com.json",
          "https://rdap.identitydigital.services/rdap/domain/cs.deals",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.deals",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/cs.deals.json",
          "https://rdap.verisign.com/com/v1/domain/pricempire.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fpricempire.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/pricempire.com.json",
          "https://rdap.identitydigital.services/rdap/domain/lzt.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flzt.market",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/lzt.market.json",
          "https://rdap.verisign.com/com/v1/domain/z2u.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fz2u.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/z2u.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoroll.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoroll.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/csgoroll.com.json",
          "https://rdap.verisign.com/com/v1/domain/rollbit.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frollbit.com",
          "https://rdap.verisign.com/com/v1/domain/rbsnin.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/rollbit.com.json",
          "https://rdap.identitydigital.services/rdap/domain/500.casino",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F500.casino",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/500.casino.json",
          "https://rdap.verisign.com/com/v1/domain/csgobig.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgobig.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/csgobig.com.json",
          "https://rdap.verisign.com/com/v1/domain/casedrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcasedrop.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/casedrop.com.json",
          "https://rdap.verisign.com/com/v1/domain/banditcamp.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbanditcamp.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/banditcamp.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinbox.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbox.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/skinbox.com.json",
          "https://rdap.verisign.com/com/v1/domain/tastydrop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftastydrop.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/tastydrop.com.json",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/domain-registry/csgopolygon.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgopolygon.gg",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/csgopolygon.gg.json",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/domain-registry/magicdrop.ru.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fmagicdrop.ru",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/magicdrop.ru.json",
          "https://rdap.verisign.com/com/v1/domain/csdice.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsdice.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/csdice.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinodds.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinodds.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/skinodds.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgowin.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgowin.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/csgowin.com.json",
          "https://rdap.verisign.com/net/v1/domain/csgorun.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgorun.net",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/csgorun.net.json",
          "https://rdap.verisign.com/com/v1/domain/openskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fopenskins.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/openskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustbet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustbet.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/rustbet.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgomagic.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgomagic.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/csgomagic.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgobounty.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgobounty.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/csgobounty.com.json",
          "https://rdap.verisign.com/com/v1/domain/ezskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fezskins.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/ezskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustcases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustcases.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/rustcases.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgoreaper.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoreaper.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/csgoreaper.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgocases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgocases.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/csgocases.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo-skins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo-skins.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/csgo-skins.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgonet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgonet.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/csgonet.com.json",
          "https://rdap.verisign.com/com/v1/domain/wtfskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwtfskins.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/wtfskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/flamecases.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fflamecases.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/flamecases.com.json",
          "https://rdap.verisign.com/com/v1/domain/gamedom.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamedom.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/gamedom.com.json",
          "https://rdap.nic.club/domain/skin.club",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskin.club",
          "https://rdap.verisign.com/net/v1/domain/sc-auth.net",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/skin.club.json",
          "https://rdap.verisign.com/com/v1/domain/daddyskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdaddyskins.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/daddyskins.com.json",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/domain-registry/rustix.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustix.gg",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/rustix.gg.json",
          "https://rdap.nic.club/domain/skins.club",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskins.club",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/skins.club.json",
          "https://rdap.publicinterestregistry.org/rdap/domain/csgohouse.org",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgohouse.org",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/csgohouse.org.json",
          "https://rdap.verisign.com/net/v1/domain/skinrave.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinrave.net",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/skinrave.net.json",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/domain-registry/bloodycase.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbloodycase.gg",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/bloodycase.gg.json",
          "https://rdap.verisign.com/com/v1/domain/csgoclicker.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoclicker.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/csgoclicker.com.json",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/domain-registry/rustbet.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustbet.gg",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/rustbet.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs-drop.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs-drop.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/cs-drop.com.json",
          "https://rdap.verisign.com/net/v1/domain/hellstore.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fhellstore.net",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/hellstore.net.json",
          "https://rdap.verisign.com/com/v1/domain/rustloot.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustloot.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/rustloot.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgo-case.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgo-case.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/csgo-case.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgogem.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgogem.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/csgogem.com.json",
          "https://rdap.verisign.com/com/v1/domain/rainbet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frainbet.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/rainbet.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustclash.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustclash.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/rustclash.com.json",
          "https://rdap.identitydigital.services/rdap/domain/12cs.fail",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2F12cs.fail",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/12cs.fail.json",
          "https://rdap.verisign.com/com/v1/domain/tf2easy.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwww.tf2easy.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/tf2easy.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2blaze.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2blaze.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/tf2blaze.com.json",
          "https://rdap.verisign.com/com/v1/domain/shuffle.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fshuffle.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/shuffle.com.json",
          "https://rdap.identitydigital.services/rdap/domain/buff.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuff.market",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/buff.market.json",
          "https://rdap.identitydigital.services/rdap/domain/avan.market",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Favan.market",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/avan.market.json",
          "https://rdap.identitydigital.services/rdap/domain/cs.money",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs.money",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/cs.money.json",
          "https://rdap.verisign.com/com/v1/domain/uuskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fuuskins.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/uuskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/youpin898.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fyoupin898.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/youpin898.com.json",
          "https://rdap.verisign.com/com/v1/domain/c5game.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fc5game.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/c5game.com.json",
          "https://rdap.verisign.com/com/v1/domain/waxpeer.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fwaxpeer.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/waxpeer.com.json",
          "https://rdap.verisign.com/com/v1/domain/dmarket.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdmarket.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/dmarket.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamcommunity.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamcommunity.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/steamcommunity.com.json",
          "https://rdap.verisign.com/com/v1/domain/lootfarm.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flootfarm.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/lootfarm.com.json",
          "https://rdap.verisign.com/com/v1/domain/rustskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Frustskins.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/rustskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/krakatoa.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fkrakatoa.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/krakatoa.com.json",
          "https://rdap.verisign.com/com/v1/domain/shadowpay.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fshadowpay.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/shadowpay.com.json",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/domain-registry/igxe.cn.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Figxe.cn",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/igxe.cn.json",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/domain-registry/swap.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fswap.gg",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/swap.gg.json",
          "https://rdap.verisign.com/com/v1/domain/bitskins.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbitskins.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/bitskins.com.json",
          "https://rdap.verisign.com/com/v1/domain/tf2mart.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftf2mart.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/tf2mart.com.json",
          "https://rdap.verisign.com/com/v1/domain/skinbid.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinbid.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/skinbid.com.json",
          "https://rdap.verisign.com/com/v1/domain/lootbear.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flootbear.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/lootbear.com.json",
          "https://rdap.nic.tf/domain/backpack.tf",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbackpack.tf",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/backpack.tf.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fstntrading.eu",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/stntrading.eu.json",
          "https://rdap.verisign.com/com/v1/domain/skinwallet.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fskinwallet.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/skinwallet.com.json",
          "https://rdap.verisign.com/com/v1/domain/dota2market.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdota2market.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/dota2market.com.json",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/domain-registry/xplay.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fxplay.gg",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/xplay.gg.json",
          "https://rdap.verisign.com/com/v1/domain/esportal.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fesportal.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/esportal.com.json",
          "https://rdap.registro.br/domain/gamersclub.com.br",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fgamersclub.com.br",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/gamersclub.com.br.json",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/domain-registry/epidemic.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fepidemic.gg",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/epidemic.gg.json",
          "https://rdap.verisign.com/com/v1/domain/cs2stash.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcs2stash.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/cs2stash.com.json",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/domain-registry/csgoskins.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgoskins.gg",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/csgoskins.gg.json",
          "https://rdap.verisign.com/com/v1/domain/steamanalyst.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamanalyst.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/steamanalyst.com.json",
          "https://rdap.verisign.com/net/v1/domain/steamcardexchange.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamcardexchange.net",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/steamcardexchange.net.json",
          "https://rdap.verisign.com/com/v1/domain/dotabuff.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdotabuff.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/dotabuff.com.json",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/domain-registry/tracker.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ftracker.gg",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/tracker.gg.json",
          "https://rdap.verisign.com/com/v1/domain/funpay.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Ffunpay.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/funpay.com.json",
          "https://rdap.verisign.com/com/v1/domain/playerauctions.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fplayerauctions.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/playerauctions.com.json",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/domain-registry/eldorado.gg.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Feldorado.gg",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/eldorado.gg.json",
          "https://rdap.verisign.com/com/v1/domain/g2a.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg2a.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/g2a.com.json",
          "https://rdap.verisign.com/net/v1/domain/kinguin.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fkinguin.net",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/kinguin.net.json",
          "https://rdap.verisign.com/com/v1/domain/g2g.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fg2g.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/g2g.com.json",
          "https://rdap.verisign.com/com/v1/domain/playerup.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fplayerup.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/playerup.com.json",
          "https://rdap.verisign.com/net/v1/domain/smurfhub.net",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfhub.net",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/smurfhub.net.json",
          "https://rdap.verisign.com/com/v1/domain/smurfaccounts.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfaccounts.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/smurfaccounts.com.json",
          "https://rdap.verisign.com/com/v1/domain/buycsgorank.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuycsgorank.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/buycsgorank.com.json",
          "https://rdap.verisign.com/com/v1/domain/csgosmurfkings.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fcsgosmurfkings.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/csgosmurfkings.com.json",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/domain-registry/smurfstore.co.json",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsmurfstore.co",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/smurfstore.co.json",
          "https://rdap.verisign.com/com/v1/domain/steamlvlup.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlvlup.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/steamlvlup.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamlevels.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlevels.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/steamlevels.com.json",
          "https://rdap.verisign.com/com/v1/domain/levelsteam.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Flevelsteam.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/levelsteam.com.json",
          "https://rdap.verisign.com/com/v1/domain/steamlevelu.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fsteamlevelu.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/steamlevelu.com.json",
          "https://rdap.verisign.com/com/v1/domain/eloking.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Feloking.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/eloking.com.json",
          "https://rdap.publicinterestregistry.org/rdap/domain/boosteria.org",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fboosteria.org",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/boosteria.org.json",
          "https://rdap.verisign.com/com/v1/domain/overgear.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fovergear.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/overgear.com.json",
          "https://rdap.verisign.com/com/v1/domain/blazingboost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fblazingboost.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/blazingboost.com.json",
          "https://rdap.verisign.com/com/v1/domain/dota2boost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fdota2boost.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/dota2boost.com.json",
          "https://rdap.verisign.com/com/v1/domain/buyboost.com",
          "https://steamcommunity.com/linkfilter/?url=https%3A%2F%2Fbuyboost.com",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit/buyboost.com.json",
          "https://phishdestroy.io/steam_dossier/vi/steam_tos_assets/auth-route-audit.json",
          "https://help.steampowered.com/en/faqs/view/365F-4BEE-2AE2-7BDD",
          "https://store.steampowered.com/privacy_agreement/#8",
          "https://www.edpb.europa.eu/system/files/2023-04/edpb_guidelines_202201_data_subject_rights_access_v2_en.pdf",
          "https://web.archive.org/web/20260810154631/https://store.steampowered.com/stats/support",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/part2-measurements.json",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/TOTAL_VALVE_SCANDALS_MASTER_DB.csv",
          "https://phishdestroy.io/steam_dossier/vi/license_disclaimer.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/vi/index.content.json",
      "export_json_sha256": "a34dc1b2152634c08281a16fda57408dfeabc26b70106b1bd8ba726820dbcc76"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "vi/investigation_part2.html",
      "language": "vi",
      "title": "Quyền truy cập tài khoản và trách nhiệm giải trình — Hồ sơ “Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/vi/investigation_part2",
      "source_html_sha256": "a8f1c2038510db3799006e7a541a0dcae0597c5b7738c9c7a4b9aca532806815",
      "exported_at": "2026-09-29T00:23:00.495Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "investigation_part2.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/vi/investigation_part2.pdf?v=print-20260929-v5",
        "sha256": "a1221cca55c1f1300e46176ea48821ae357d1e409fe42a7ed0dca69b1e559773",
        "bytes": 134525,
        "pages": 9
      },
      "integrity": {
        "signed_object": "investigation_part2.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "investigation_part2.content.json.asc",
        "digest_file": "investigation_part2.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify investigation_part2.content.json.asc investigation_part2.content.json",
          "sha256sum -c investigation_part2.content.json.sha256"
        ]
      },
      "content": {
        "text": "HỒ SƠ VỀ STEAM / II\n\nPhần II — Quyền truy cập tài khoản, Hỗ trợ thuê ngoài và Thực thi\n\nTự động hóa trong khu vực công. Dịch vụ hỗ trợ thuê ngoài. Người dân phải gánh chịu hậu quả.\n\nBắt đầu phần con này ↓\nPHỤ LỤC 01 / GIÁM SÁT THỊ TRƯỜNG NGẦM TRỰC TIẾP550,000+\n\nSteam các tài khoản hiện đang được rao bán trên FSB Market (một tên gọi ẩn danh; tên gốc không được tiết lộ tại đây)\nngay lúc này\n\n550,000+ DỮ LIỆU TRỰC TIẾP · 231,829 TRONG CƠ SỞ DỮ LIỆU LỊCH SỬ Đà ĐƯỢC TRÍCH XUẤT (NHẬT KÝ STEALER CỦA 198,320)\n\nTrung tâm giao dịch ngầm chính dành cho các tài khoản Steam bị chiếm quyền điều khiển, FSB Market (tên liên quan được giấu kín), xác thực cả người mua lẫn người bán bằng OpenID chính thức Steam của Valve (openid.realm = https://FSB Market). Vào bất kỳ thời điểm nào, hơn nửa triệu tài khoản bị đánh cắp và bị xâm phạm (nhật ký đánh cắp từ RedLine/Lumma, dữ liệu thu thập được từ các vụ lừa đảo qua email, tấn công bằng thông tin đăng nhập đã biết) đang được rao bán với giá chỉ vài xu ($0.50–$2.00). Cả hai đều không FSB Market cũng không the associated forum bị chặn bởi Bộ lọc liên kết của Valve. Đây là nguồn cung cấp cho các tài khoản bot trả phí trên 63.06% mà Valve đã cấm mà không hỗ trợ nạn nhân.\n\nThông tin trực tiếp: Giám sát thị trường ngầm (550k+ Live) ↗ · Mở bản ghi thu thập ↗ · Mở bản ghi theo dõi bộ lọc liên kết ↗550K+ TRỰC TIẾP\n\n01 / MỘT HỆ SINH THÁI CÓ SỰ THAM GIA CỦA CÁC TÁC GIẢ\n\nTự động hóa đãdấu vết trên giấy tờ.\n\nCác dự án được đặt tên. Các tính năng đã được công bố. Theo dõi một công cụ đến tài liệu hướng dẫn của nó, sau đó kiểm tra các mối quan hệ giữa các nhà phát triển đã thu thập được.\n\n252CÁC KHO LƯU TRỮ Đà THU THẬP\n3,320HỒ SƠ TRÊN GITHUB\n4,214HỒ SƠ – CÁC CẶP KHO DỮ LIỆU\nValve cơ sở hạ tầngThư viện cộng đồngCác ứng dụng có thể tái sử dụng\nCác đường kẻ thể hiện các tích hợp hoặc mối phụ thuộc đã được ghi nhận. Chọn một nút để xem thông tin chi tiết liên quan đến nó.\n\nTự động hóa quản lý nhiều tài khoản / JustArchiNET\n\nArchiSteamFarm\n\nDự án này công khai quảng cáo tính năng “farm” thẻ đồng thời trên các tài khoản Steam. Tệp dự án của nó khai báo phụ thuộc vào SteamKit2.\n\nĐọc tài liệu hướng dẫn của chính dự án ↗\n\nSteamKit → ArchiSteamFarm\nphụ thuộc đã khai báo ↗\n\nTỔNG HỢP CÁC MỐI QUAN HỆ\n\n40 nhãn người đóng góp · 40 nhãn phân nhánh\n\nDưới đây là ví dụ về người đóng góp. Các nhãn này mô tả mối quan hệ với kho lưu trữ, chứ không phải mối quan hệ việc làm hay sự phê duyệt.\n\n@JustArchi@renovate[bot]@JustArchi-ArchiBot@dependabot-preview[bot]@renovate-bot@người_dùng_actions@dependabot-support@Abrynos\nBiểu đồ của nhà phát triển cho thấy điều gì\n\nBiểu đồ này thể hiện các mối quan hệ đã được công bố giữa những người đóng góp và những người phân nhánh (forker) liên quan đến các dự án được nêu tên và các hồ sơ trên GitHub. Đây là những dữ liệu công khai — các bản phân nhánh kho lưu trữ, danh sách đóng góp, mối liên hệ giữa các hồ sơ. Câu hỏi đặt ra là những bằng chứng giấy tờ về năng lực đã được công bố và các mối quan hệ giữa các nhà phát triển đòi hỏi Valve phải trả lời điều gì, chứ không phải những gì cuộc điều tra này đã bịa đặt ra. Các mã băm nguồn được lưu trữ trong nguồn gốc bản đồ.\n\nKhám phá toàn bộ mạng lưới ↗Dữ liệu nguồn của kho lưu trữ ↓\n\n02 / NHỮNG THẨM QUYỀN KHÁC NHAU. NHỮNG SỨC MẠNH KHÁC NHAU.\n\nPhím nàoChúng ta đang nói về điều gì vậy?\n\nViệc chơi một trò chơi không yêu cầu người chơi phải cung cấp khóa Web API cá nhân. Đó chính là điểm khác biệt cốt lõi trong cuộc điều tra này.\n\n01 / TÀI KHOẢN NGƯỜI DÙNG\nKhóa cá nhân của WebAPI\nsteamcommunity.com/dev/apikey\n\nĐược cấp từ tài khoản người dùng để thực hiện các cuộc gọi API được phép. Việc tạo khóa, quyền truy cập, thu hồi và phát hiện lạm dụng là các vấn đề liên quan đến bảo mật tài khoản.\n\n02 / HỆ THỐNG HẬU CẦN CỦA TRÒ CHƠI\nMã khóa API của Publisher Web\n\nCác đối tác của Steamworks sử dụng thông tin đăng nhập của nhà phát hành để thực hiện các hoạt động nền tảng được hỗ trợ, bao gồm các dịch vụ liên quan đến trò chơi. Khóa cá nhân của người chơi là một loại thông tin đăng nhập khác.\n\n03 / NHẬN DẠNG & PHẦN MỀM ĐĂNG NHẬP\nOpenID / mã thông báo phiên\n\nOpenID dùng để xác thực danh tính với một trang web. Mã phiên (Steam) hoặc mã làm mới (refresh token) lại có mục đích khác. Không nên coi các cơ chế này như một “khóaAPI” duy nhất có thể thay thế lẫn nhau.\n\nValve ghi lại cả khóa Web API của người dùng lẫn của nhà phát hành. Do đó, toàn bộ hệ thống Web API không tách biệt với Steamworks. API Tài liệu quan trọng ↗ đã lưu trữ 2026-09-15 ↗ · Xác thực phiên chơi game ↗ đã lưu trữ 2026-08-29 ↗\n\nĐƯỢC GHI CHÉP BỞI TÁC GIẢ CỦA CÔNG CỤ / THÁNG 3 NĂM 2024\n\nTự động hóa có thể sử dụng nhiều hơn một khóa “API”.\n\nTrang wiki của Trade Offer Manager mô tả việc sử dụng mã thông báo truy cập phiên (session access token) cho một số phần của trang web API khi không có khóa xác thực phiên (API) riêng biệt. Tài liệu này cũng ghi lại quy trình xác nhận trên thiết bị di động để tạo khóa từ phiên bản 2023.. Người quản trị hệ thống cho biết việc sử dụng mã thông báo theo cách này không được hỗ trợ bởi Valve; đây là một tuyên bố đã lỗi thời trong tài liệu, chứ không phải là kết quả thử nghiệm vượt qua bảo mật thực tế.\n\nXem giải thích của người duy trì ↗ đã lưu trữ 2026-09-24 ↗\n\nMẶT CON NGƯỜI / MỘT QUÁ TRÌNH PHISHING MINH HỌA\n\nVẫn đang chơi.Đã bị phơi bày.\n\nMột tin nhắn từ một người bạn. Một lời kêu gọi bỏ phiếu. Một trang “cảm ơn”. Đối với người chơi, nhiệm vụ đã hoàn thành. Tuy nhiên, một phiên đăng nhập bị xâm nhập có thể vẫn tồn tại sau khoảnh khắc đó.\n\nTRÊN MÀN HÌNH CỦA NGƯỜI CHƠI\n\nF\nLời kể của một người bạn\n\n“Bạn có thể bỏ phiếu cho đội của chúng tôi không?”\n\nYêu cầu được gửi đến qua tính năng trò chuyện củSteamtừ một tài khoản quen thuộc. Trong trường hợp này, trang web được liên kết sẽ mở ra trong trình duyệt của khách hàng.\n\nKHÔNG THẤY\n\nNiềm tin được xây dựng từ trước khi trang web ra đời.\n\nTài khoản của một người bạn bị chiếm quyền điều khiển có thể làm tăng độ tin cậy cho một liên kết lừa đảo. Giao diện Steam xung quanh không xác thực trang web đích.\n\nNgười gửi quen thuộc / Địa chỉ nhận bên ngoài\nAn ninh tài khoản là vấn đề cần được quan tâm trước khi bán bất kỳ mặt hàng nào.\n\nNgười chơi không có ý định tạo thông tin đăng nhập tự động hóa hay ủy quyền quyền kiểm soát. Việc quay lại trò chơi không phải là bằng chứng cho thấy tài khoản đó an toàn. Valve lưu trữ nhật ký phiên, bản ghi tạo khóa API và dữ liệu tương quan thiết bị. Nạn nhân thì không. Sự bất đối xứng đó chính là vấn đề về trách nhiệm giải trình.\n\nQuyền truy cập phiên và các loại thông tin xác thực\n\nKhóa “API” và phiên đăng nhập là hai thông tin xác thực riêng biệt với các quyền hạn khác nhau. Việc thu hồi khóa không làm chấm dứt phiên đang hoạt động. Tài liệu chính thức của “Valve” đã mô tả cả hai; liên kết Valve chứa các bản ghi cho thấy thông tin xác thực nào đang hoạt động tại thời điểm xảy ra bất kỳ hành động nào đang bị tranh cãi. Yêu cầu ở đây là công bố bản ghi đó — chứ không phải là một suy luận do cuộc điều tra bịa đặt ra. Tài liệu của người duy trì về việc xử lý token ↗ đã lưu trữ 2026-09-24 ↗ · Valve Tài liệu quan trọng ↗ đã lưu trữ 2026-09-15 ↗\n\n03 / THỊ TRƯỜNG CHÍNH THỨC CÓ MỨC TRẦN\n\nMón đồ này có thể là đồ hiếm.Giới hạn vẫn được giữ nguyên.\n\nMột mức giá cao hơn mức trần niêm yết không thể được thực hiện thông qua một lần niêm yết duy nhất trên Thị trường Cộng đồng với mức giá đầy đủ đó.\n\nGIÁ YÊU CẦU TÍNH CHẤT THAM KHẢO$5,000Thay đổi giá chào bán của mặt hàng\n$100$20,000\n\nĐây là minh họa về mức giới hạn đã công bố, không phải là đánh giá hay khuyến nghị giao dịch.\n\nGIỚI HẠN NIÊM YẾT≈ $1,800\nNẮP VÍ≈ $2,000\n\nVượt quá mức trần niêm yết đã công bố.\n\nTiền trong ví không thể rút về tài khoản ngân hàng. Những hạn chế này tạo ra nhu cầu mà các thị trường giao dịch skin của bên thứ ba đáp ứng: một nhu cầu phát sinh từ các giới hạn niêm yết và giới hạn ví, trong khi các quy định của chính Valve lại cấm các nhà khai thác thương mại đáp ứng nhu cầu này.\n\nGiới hạn thị trường của Steam ↗ đã lưu trữ 2026-09-21 ↗\n\n04 / BÊN TRONG RANH GIỚI HỖ TRỢ\n\nĐược giao phó trách nhiệm quản lý dữ liệu.Chịu trách nhiệm về quyền truy cập.\n\nChính sách bảo mật của Valve quy định rõ ràng về việc chia sẻ dữ liệu cá nhân với các nhà cung cấp dịch vụ hỗ trợ bên thứ ba, khi cần thiết để thực hiện công tác hỗ trợ.\n\nNGƯỜI CHƠITài khoản và bằng chứng\n→\nVANQuá trình phục hồi\n→\nNHÀ CUNG CẤP DỊCH VỤ HỖ TRỢQuyền truy cập được ủy quyền\n\nChính sách bảo mật §5.2 ↗ · Chính sách riêng của Valve cho phép bên thứ ba truy cập để hỗ trợ. Các câu hỏi còn bỏ ngỏ là: những quyền truy cập nào đã được cấp, có những bản ghi kiểm tra nào, và điều gì đã xảy ra khi quyền truy cập này bị cáo buộc là đã bị lạm dụng.\n\n2015\nBảng xếp hạng được công bố rộng rãi\n\nValve đã thừa nhận tình trạng đánh cắp tài khoản diễn ra trên diện rộng và nêu rõ các biện pháp phòng ngừa.\n\nValve ấn phẩm ↗đã lưu trữ 2026-08-09 ↗\n2015\nValve đã thuê ngoài bộ phận này — và đã nói rõ điều đó\n\nValve duy trì một đội ngũ lãnh đạo hỗ trợ nhỏ thuộc bộ phận Hỗ trợ Khách hàng (Steam) tại công ty và đã tuyên bố rằng \"đã thuê một vài công ty khác nhau\" để xử lý các vấn đề hỗ trợ (Erik Johnson, Valve, gửi cho Kotaku); chính sách bảo mật của họ tại § 5.2 cho phép các bên thứ ba này truy cập vào dữ liệu người dùng. Valve chưa bao giờ tiết lộ nhà thầu nào được cấp quyền truy cập để khôi phục tài khoản — Các cuộc thảo luận trong cộng đồng đã nêu tên một số nhà cung cấp như Concentrix, nhưng không có nhà cung cấp nào được Valvexác nhận. Bộ phận được thuê ngoài này đã được thành lập từ nhiều năm trước cả hai thông tin được đề cập dưới đây.\n\nKotaku: Bài viết “Valve” về sự ủng hộ của trang này ↗đã lưu trữ 2025-07-11 ↗\n2023\nLần nhập viện đầu tiên\n\nĐội CS:GO của Valve đã chính thức thừa nhận trách nhiệm bằng văn bản về việc một tài khoản bị xâm nhập thông qua quy trình yêu cầu hỗ trợ của chính họ, và đã hủy bỏ các giao dịch liên quan.\n\nMở hồ sơ gia công ↓\n2025\nLần nhập viện thứ hai\n\n33 Vài tháng sau, bộ phận hỗ trợ của Steam cho biết một kỹ thuật viên “đã không tuân thủ quy trình của chúng tôi, dẫn đến việc tài khoản của bạn bị khôi phục cho một người khác”. Cùng một kênh liên lạc. Cùng một kết quả.\n\nDexerto, 14 Nov 2025 ↗\n\nHỒ SƠ VỤ ÁN / HFB VÀ CÁC CÁO BUỘC VỀ VIỆC THUÊ NGOÀI\n\nCách tiếp cận chính là chính chương trình hỗ trợ “Steam”.Valve đã nêu rõ điều đó bằng văn bản.\n\nTrong phản hồi từ bộ phận hỗ trợ được Dexerto đăng tải lại, đội CS:GO củValve đã thừa nhận trách nhiệm về việc một tài khoản bị xâm nhập qua quy trình yêu cầu hỗ trợ — kênh riêng của nó, không phải trang lừa đảo và cũng không phải do người dùng. Các mặt hàng đã được thu hồi và các giao dịch đã được hủy bỏ — đây chính là biện pháp khắc phục mà trang Valve khẳng định là không tồn tại đối với các nạn nhân khác. Số lượng hàng tồn kho của HFB được báo cáo là $2,000,000+ vào ngày đó và $3,000,000+ trong phần tiếp theo; Qkss đã thua $1,000,000+ theo cách tương tự và chẳng thu được gì cả.\n\nTRẢ LỜI HỖ TRỢ / ĐƯỢC TÁI BẢN BỞI DEXERTO · 21 THÁNG 2 NĂM 2023\n“compromised through a support help request, for which the CS:GO team takes responsibility”\nĐọc bài báo và nội dung tin nhắn được trích dẫn ↗ đã lưu trữ 2025-08-18 ↗\n01 / VAN NÀO Đà CHO PHÉP\nKênh hỗ trợ riêng của họ chính là lối vào\n\nPhản hồi này đề cập đến tài khoản bị xâm phạm và việc hủy các giao dịch của tài khoản đó. Valve đã hủy các giao dịch này — do đó, các giao dịch này có thể được hủy bỏ. Phiếu giao dịch gốc đã được xác thực không có trong bộ sưu tập này.\n\n02 / NHỮNG VẤN ĐỀ MÀ VIỆC SA THẢI KHÔNG GIẢI QUYẾT ĐƯỢC\nCánh cửa đó lại mở ra vào tháng 11 năm 2025\n\nNhà thầu đã sa thải toàn bộ đội ngũ nhân viên hỗ trợ của Steam— theo thông tin do Mzkshow đăng tải trên Dexerto, không phải thông báo chính thức từ Valve. Ba mươi ba tháng sau, bộ phận hỗ trợ của Steam đã gửi thư cho một khách hàng khác, trong đó nêu rõ: “Một kỹ thuật viên hỗ trợ xử lý yêu cầu trợ giúp đã không tuân thủ quy trình của chúng tôi, dẫn đến việc tài khoản của quý vị bị khôi phục cho một người khác.” Đây là chính câu văn của Valve, liên quan đến cùng kênh hỗ trợ đó.\n\nBài đăng thứ hai, “14” ngày 2025 ↗\n03 / OPEN LÀ GÌ\nValve chưa bao giờ nêu tên nhà thầu\n\nCác nguồn tin này không xác định được cả nhà thầu lẫn địa điểm. Điều đó không phải là lỗ hổng trong báo cáo — mà là thông tin mà Valve chưa công bố về việc ai có quyền truy cập vào các tài khoản người dùng.\n\nBản tường thuật đương thời về vụ việc ↗\n\nBa câu hỏi mà “Valve” vẫn chưa trả lời: ai có thể vô hiệu hóa tính năng khôi phục tài khoản, kết quả kiểm tra quyền truy cập cho thấy điều gì, và những thay đổi nào đã diễn ra sau đó.\n\nCác cáo buộc sau này trong kho lưu trữ tài liệu hỗ trợ\n\nHai bài đăng trên Reddit tại 2024 đã nêu thêm các cuộc điều tra của Mzkshow — một vụ việc gỡ bỏ lệnh cấm VAC vào tháng 7 tại 2024 và một vụ việc liên quan đến kho hàng tại 2024 $13,000 vào tháng 12. Đây là những sự cố được báo cáo riêng biệt. Câu hỏi về trách nhiệm trong mỗi vụ việc đều giống nhau: ai có quyền truy cập đặc quyền, kết quả kiểm toán cho thấy điều gì, và những thay đổi cụ thể là gì.\n\n14 2024 tháng 7 · trường hợp được báo cáo là đã hồi phục / bị cấm tham gia VAC ↗2 Tháng 12 năm 2024 · đã báo cáo vụ việc liên quan đến kho hàng của $13,000 ↗đã lưu trữ 2025-08-05 ↗Hai bài đăng đã được lưu giữ, các hàng nguồn và các hàm băm ↓\n\n05 / THEO DÕI SỰ MẤT MÁT\n\nMọi số tiềncần một chiếc ốp lưng.\n\nMười trường hợp, từ tháng 6 năm 2022 đến tháng 3 năm 2026. Mỗi con số đều là số liệu do nguồn được nêu tên công bố — $6,300,000, $2,000,000+, $1,000,000+, ≈$320,000, ≈$300,000, và giảm xuống còn288. Valve lưu trữ nhật ký giao dịch, bản ghi phiên làm việc và bản ghi kiểm toán hỗ trợ cho từng trường hợp, nhưng chưa tạo ra bất kỳ bản ghi nào trong số đó.\n\nKÊNH HỖ TRỢ21 2022 tháng 6\n$2,000,000+\nHFB — kho hàng lớn nhất trong trò chơi\n\nĐÁNH GIÁ GIÁ TRỊ HÀNG TỒN KHO ĐƯỢC BÁO CÁO · TĂNG LÊN HƠN $3M TRONG BÁO CÁO THEO DÕI NGÀY 2023 THÁNG 2\n\nBảy món đồ lưu niệm “Dragon Lores” và con dao Karambit “Blue Gem” mang số hiệu #1; riêng con dao này đã có giá khoảng $1.26m. Tài khoản không hoạt động trong ba năm với tính năng xác thực vẫn còn kích hoạt; email và mật khẩu đã được thay đổi thông qua quy trình khôi phục của bộ phận hỗ trợ. Valve đã hủy các giao dịch — và cam kết trách nhiệm bằng văn bản. Trước khi hủy giao dịch, số tiền thu được được báo cáo là $200,000+ đã được rút qua market.csgo.com, nền tảng này thanh toán bằng tiền mặt và tiền điện tử. Việc hủy giao dịch chỉ trả lại skin, không phải số tiền mà người dùng đã rút về tài khoản. Việc đảo ngược giao dịch cũng gây ra sự cố: một người mua đã giấu vật phẩm Souvenir Dragon Lore của mình trong một Kho chứa trong trò chơi, kịch bản không thể xem bên trong chính container đó, và Valve đã tạo ra bản sao của một vật phẩm trị giá $130,000 trong quá trình hủy bỏ một vụ trộm — sự việc được phát hiện nhờ ID vật phẩm và báo cáo từ cộng đồng, vật phẩm đã bị xóa vào tháng 7 2022, và người mua được hoàn tiền bởi BUFF thay vì Valve.\n\nDexerto, ngày xảy ra vụ trộm ↗\nVÍ VÀ GIAO DỊCH MUA HÀNG07 07/2022\n>$500\n44 Các giao dịch mua trên thị trường đang có tranh chấp\n\nCHI TIÊU TỪ VÍ Đà ĐĂNG KÝ · USD\n\nMột người dùng đã phản ánh về việc bị mua trái phép các vật phẩm giá trị thấp trong Dota 2 và nhận được phản hồi không thỏa đáng từ bộ phận hỗ trợ.\n\nĐọc đơn khiếu nại và các ảnh chụp màn hình kèm theo ↗\nVI PHẠM AN NINH NỀN TẢNG14 2022 tháng 8\n$6,300,000\nCS.Money — 19,000+ các skin từ bot\n\nĐÁNH GIÁ GIÁ TRỊ · ƯỚC TÍNH BAN ĐẦU $1.6.000.000\n\nNhững kẻ tấn công đã chiếm quyền kiểm soát các tệp xác thực trên thiết bị di động của các bot giao dịch trên sàn giao dịch và làm trống chúng, đồng thời chuyển một phần số tiền đánh cắp được cho các nhà giao dịch nổi tiếng nhằm che giấu dấu vết. Các nhà nghiên cứu trong cộng đồng đã lập bản đồ các tài khoản của kẻ tấn công 55 chỉ trong vài giờ. Valve không thực hiện bất kỳ thao tác đảo ngược nào — một trang web của bên thứ ba nằm bên ngoài Steam, theo thông tin từ chính Steam, nơi hệ thống kho hàng, giao dịch API và hệ thống tài khoản của họ đã bị đánh cắp từ đầu đến cuối.\n\nĐọc bài tường thuật đương thời ↗\nKÊNH HỖ TRỢBÀI BÁO 21 NGÀY 2023\n$1,000,000+\nQkss — cùng một cánh cửa, cùng một diễn viên, câu trả lời ngược lại\n\nGIÁ TRỊ HÀNG TỒN KHO ĐƯỢC BÁO CÁO\n\nXét theo cách mà vụ HFB đã được xử lý, bởi cùng một bên liên quan, thông qua cùng một yêu cầu hỗ trợ. Vụ HFB đã được giải quyết triệt để tám tháng trước đó. Còn vụ Qkss thì không. Không có chi tiết nào trong hồ sơ công khai phân biệt hai vụ việc này, ngoại trừ quy mô của đối tượng liên quan.\n\nDexerto về cuộc điều tra Mzkshow ↗\nKÊNH HỖ TRỢBÀI BÁO NGÀY 2023 THÁNG 2\n≈ $320,000\nChính hành vi giao dịch nội gián — kéo dài trong một năm\n\nKẾT QUẢ HOẠT ĐỘNG TRONG KHOẢNG MỘT NĂM · KHÔNG PHẢI LÀ ĐÁNH GIÁ GIÁ TRỊ HÀNG TỒN KHO\n\nQuyền truy cập từ phía bộ phận hỗ trợ đã tiếp cận được lịch sử tài khoản từ 15 năm trước: mã CD đầu tiên, email đầu tiên, thẻ thanh toán đầu tiên — chính xác là những bằng chứng mà quy trình khôi phục yêu cầu. Ai nắm giữ cơ sở dữ liệu thì luôn thắng trong cuộc tranh cãi với người nắm giữ tài khoản. Một khẩu M4A4 Howl bị đánh cắp kèm theo các hình ảnh 3D iBUYPOWER và Titan Katowice 2014 đã được bán với giá $35,000 và cuối cùng thuộc về b1t của NAVI, người không có cách nào biết được điều đó. Phản ứng của nhà thầu là sa thải mọi nhân viên làm việc tại bộ phận hỗ trợ Steam.\n\nEscorenews về cuộc điều tra này ↗\nVÍ VÀ GIAO DỊCH MUA HÀNG09 2023 tháng 12\n€288\nMất ví dù đã áp dụng cơ chế bảo mật hai bước\n\nTRUSTPILOT · CHỈ SỐ NGUỒN 16\n\nNgười đánh giá báo cáo rằng tài khoản của họ đã bị hack và không nhận được sự hỗ trợ liên quan đến chi tiêu trên Market. Bản xuất này không có URL đánh giá riêng.\n\nKiểm tra nguồn gốc của mã nguồn ↗\nPHỤC HỒI TÀI KHOẢN02 2024 tháng 12\n$13,000\n“Matvey” — hai năm sau vụ sa thải\n\nƯỚC TÍNH HÀNG TỒN KHO CỦA TÁC GIẢ\n\nViệc khôi phục tài khoản đã được chấp thuận cho người đã cung cấp thông tin tài khoản mà chính chủ tài khoản cũng không thể xác minh được. Cùng một quy trình, cùng một kết quả, sau khi nhà thầu đã giải thể bộ phận hỗ trợ khách hàng tại Steam.\n\nĐọc nội dung cáo buộc đã được lưu giữ ↗\nPHỤC HỒI TÀI KHOẢN09 THÁNG 5 NĂM 2025\n≈ $10,000\nPhục hồi thông qua vé của người khác\n\nTỔN THẤT TÀI SẢN ĐƯỢC BỒI THƯỜNG · USD\n\nMột người dùng ở Quebec cáo buộc bộ phận hỗ trợ đã đặt lại mật khẩu và gỡ bỏ các biện pháp bảo vệ tài khoản theo yêu cầu của một người khác.\n\nĐọc đơn khiếu nại được viết dưới góc nhìn của người trong cuộc ↗\nKÊNH HỖ TRỢ13 2025 tháng 11\n≈ $300,000\nHawkeye337 — và lời thừa nhận bằng văn bản lần thứ hai củValve\n\nBỘ SƯU TẬP HOLO ĐẦY ĐỦ “2014” TẠI KATOWICE\n\nKẻ tấn công đã đòi 1 bitcoin và bắt đầu chuyển số bitcoin đó sang các ví Negevs để tiêu hủy. Steam Phản hồi từ bộ phận hỗ trợ: “Một kỹ thuật viên hỗ trợ xử lý yêu cầu trợ giúp đã không tuân thủ quy trình của chúng tôi, dẫn đến việc tài khoản của bạn bị khôi phục cho một người khác.” Ba mươi ba tháng sau lần thừa nhận đầu tiên, lại là tình huống tương tự. Tài khoản được khôi phục chỉ vài giờ sau khi chủ đề này trở thành xu hướng trên X. Qkss không có lượng người theo dõi lớn như vậy.\n\nDexerto, 14 Nov 2025 ↗\nVÍ VÀ GIAO DỊCH MUA HÀNG29 2026 tháng 3\n$50\nNạp tiền và tặng game trái phép\n\nTRUSTPILOT · CHỈ SỐ NGUỒN 290\n\nNgười đánh giá cáo buộc có các khoản chi tiêu trái phép và các yêu cầu hoàn tiền không thành công. URL của bài đánh giá cụ thể này không có trong tệp xuất.\n\nKiểm tra nguồn gốc của mã nguồn ↗\n\nNguồn trích dẫn và số liệu vẫn được giữ nguyên theo báo cáo của từng nguồn. Valve lưu giữ nhật ký giao dịch, bản ghi phiên làm việc và dấu vết kiểm toán hỗ trợ cho từng trường hợp trong số này. Hãy cung cấp các tài liệu đó. Một bài đăng trên Reddit được lưu giữ không thể giải quyết vấn đề — chính các bản ghi của Valve mới là bằng chứng quyết định.\n\nBỘ SƯU TẬP / SAU KHI KIỂM TRA\n\n231,829 các tài khoản đang được bán.Valve lưu trữ nhật ký cho từng trường hợp.\n354 → 201\nCác đánh giá trên Trustpilot\n\n153 Các hàng trùng lặp đã bị xóa. Các URL đánh giá riêng lẻ không được giữ lại trong tệp xuất.\n\n231,829\nSteam danh sách tài khoản\n\n33,509 được phân loại là “đăng ký tự động”; 198,320 dưới nhãn hiệu “stealer” của nhà sưu tập. Các thông tin đăng bán không đồng nghĩa với việc đã hoàn tất giao dịch.\n\nKiểm toán danh mục ↓Tìm kiếm trong kho lưu trữ nguồn ↗",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Phần II — Quyền truy cập tài khoản, Hỗ trợ thuê ngoài và Thực thi"
          },
          {
            "level": 2,
            "id": null,
            "text": "Tự động hóa đãdấu vết trên giấy tờ."
          },
          {
            "level": 3,
            "id": null,
            "text": "ArchiSteamFarm"
          },
          {
            "level": 2,
            "id": null,
            "text": "Phím nàoChúng ta đang nói về điều gì vậy?"
          },
          {
            "level": 3,
            "id": null,
            "text": "Khóa cá nhân của WebAPI"
          },
          {
            "level": 3,
            "id": null,
            "text": "Mã khóa API của Publisher Web"
          },
          {
            "level": 3,
            "id": null,
            "text": "OpenID / mã thông báo phiên"
          },
          {
            "level": 3,
            "id": null,
            "text": "Tự động hóa có thể sử dụng nhiều hơn một khóa “API”."
          },
          {
            "level": 2,
            "id": null,
            "text": "Vẫn đang chơi.Đã bị phơi bày."
          },
          {
            "level": 3,
            "id": "session-hidden-title",
            "text": "Niềm tin được xây dựng từ trước khi trang web ra đời."
          },
          {
            "level": 2,
            "id": null,
            "text": "Món đồ này có thể là đồ hiếm.Giới hạn vẫn được giữ nguyên."
          },
          {
            "level": 2,
            "id": null,
            "text": "Được giao phó trách nhiệm quản lý dữ liệu.Chịu trách nhiệm về quyền truy cập."
          },
          {
            "level": 3,
            "id": null,
            "text": "Bảng xếp hạng được công bố rộng rãi"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve đã thuê ngoài bộ phận này — và đã nói rõ điều đó"
          },
          {
            "level": 3,
            "id": null,
            "text": "Lần nhập viện đầu tiên"
          },
          {
            "level": 3,
            "id": null,
            "text": "Lần nhập viện thứ hai"
          },
          {
            "level": 3,
            "id": null,
            "text": "Cách tiếp cận chính là chính chương trình hỗ trợ “Steam”.Valve đã nêu rõ điều đó bằng văn bản."
          },
          {
            "level": 4,
            "id": null,
            "text": "Kênh hỗ trợ riêng của họ chính là lối vào"
          },
          {
            "level": 4,
            "id": null,
            "text": "Cánh cửa đó lại mở ra vào tháng 11 năm 2025"
          },
          {
            "level": 4,
            "id": null,
            "text": "Valve chưa bao giờ nêu tên nhà thầu"
          },
          {
            "level": 2,
            "id": null,
            "text": "Mọi số tiềncần một chiếc ốp lưng."
          },
          {
            "level": 3,
            "id": null,
            "text": "HFB — kho hàng lớn nhất trong trò chơi"
          },
          {
            "level": 3,
            "id": null,
            "text": "44 Các giao dịch mua trên thị trường đang có tranh chấp"
          },
          {
            "level": 3,
            "id": null,
            "text": "CS.Money — 19,000+ các skin từ bot"
          },
          {
            "level": 3,
            "id": null,
            "text": "Qkss — cùng một cánh cửa, cùng một diễn viên, câu trả lời ngược lại"
          },
          {
            "level": 3,
            "id": null,
            "text": "Chính hành vi giao dịch nội gián — kéo dài trong một năm"
          },
          {
            "level": 3,
            "id": null,
            "text": "Mất ví dù đã áp dụng cơ chế bảo mật hai bước"
          },
          {
            "level": 3,
            "id": null,
            "text": "“Matvey” — hai năm sau vụ sa thải"
          },
          {
            "level": 3,
            "id": null,
            "text": "Phục hồi thông qua vé của người khác"
          },
          {
            "level": 3,
            "id": null,
            "text": "Hawkeye337 — và lời thừa nhận bằng văn bản lần thứ hai củValve"
          },
          {
            "level": 3,
            "id": null,
            "text": "Nạp tiền và tặng game trái phép"
          },
          {
            "level": 2,
            "id": null,
            "text": "231,829 các tài khoản đang được bán.Valve lưu trữ nhật ký cho từng trường hợp."
          },
          {
            "level": 3,
            "id": null,
            "text": "Các đánh giá trên Trustpilot"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam danh sách tài khoản"
          }
        ],
        "links": [
          "https://phishdestroy.io/live-intel/?category=steam",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/auth-route-audit/lzt.market.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/linkfilter-evidence-lzt.json",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://github.com/JustArchiNET/ArchiSteamFarm/blob/main/ArchiSteamFarm/ArchiSteamFarm.csproj",
          "https://github.com/JustArchi",
          "https://github.com/renovate[bot]",
          "https://github.com/JustArchi-ArchiBot",
          "https://github.com/dependabot-preview[bot]",
          "https://github.com/renovate-bot",
          "https://github.com/actions-user",
          "https://github.com/dependabot-support",
          "https://github.com/Abrynos",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/automation-map.json",
          "https://phishdestroy.io/steam_dossier/vi/output_steam_network/network.html",
          "https://phishdestroy.io/steam_dossier/output_steam_network/raw_data.json",
          "https://partner.steamgames.com/doc/webapi_overview/auth",
          "http://web.archive.org/web/20260915025812/https://partner.steamgames.com/doc/webapi_overview/auth",
          "https://partner.steamgames.com/doc/webapi/ISteamUserAuth",
          "http://web.archive.org/web/20260829124950/https://partner.steamgames.com/doc/webapi/ISteamUserAuth",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "http://web.archive.org/web/20260924181824/https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://store.steampowered.com/privacy_agreement/",
          "https://store.steampowered.com/oldnews/19618",
          "http://web.archive.org/web/20260809125516/https://store.steampowered.com/oldnews/19618",
          "https://kotaku.com/valve-explains-why-steam-customer-service-is-still-terr-1736988223",
          "http://web.archive.org/web/20250711004653/https://kotaku.com/valve-explains-why-steam-customer-service-is-still-terr-1736988223",
          "https://www.dexerto.com/counter-strike-2/valve-saves-hacked-cs2-player-threatened-with-ransom-over-300000-of-rare-stickers-3283135/",
          "https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "http://web.archive.org/web/20250818113925/https://www.dexerto.com/csgo/csgo-skins-worth-millions-allegedly-stolen-with-help-from-steam-support-staff-2066939/",
          "https://lis-skins.com/ru/blog/krupneisaia-mosenniceskaia-sxema-v-istorii-steam/",
          "https://www.reddit.com/r/cs2/comments/1e38jo4/stealing_accounts_and_removing_vac_bans_a_new/",
          "https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "http://web.archive.org/web/20250805141942/https://www.reddit.com/r/cs2/comments/1h53qp3/steam_support_is_stealing_accounts_again/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/outsourcing-archive-records.json",
          "https://www.dexerto.com/csgo/over-2-million-in-csgo-skins-stolen-from-hacked-steam-account-1853092/",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://esportfire.com/article/the-biggest-hack-in-csgo-history-csmoney-14082022",
          "https://escorenews.com/en/csgo/news/44087-valve-steam-support-employee-accused-of-selling-inactive-accounts-inventories-worth-six-figures-b1t-has-one-of-these-skins",
          "https://phishdestroy.io/steam_dossier/vi/PART2_RESEARCH.md",
          "https://www.reddit.com/r/GlobalOffensive/comments/1h56shi/steam_support_is_stealing_accounts/",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/part2-quality-review.json",
          "https://phishdestroy.io/steam_dossier/vi/steam_evidence_archive.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/vi/investigation_part2.content.json",
      "export_json_sha256": "3eb122da9e0aacd69f29b1d48b30a7000f7b67c8cdf5c9c7507f17404cc96bf5"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "vi/legal_analysis.html",
      "language": "vi",
      "title": "Điều khoản của họ, quyền lợi của bạn — Hồ sơ về “Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/vi/legal_analysis",
      "source_html_sha256": "7cd8a97c9e8d7d01e0b3bb41d37e97182e01c0f480b07c713eebf91dbc6826b4",
      "exported_at": "2026-09-29T00:23:00.954Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "legal_analysis.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/vi/legal_analysis.pdf?v=print-20260929-v5",
        "sha256": "abc973a7cc55b51eac5d1780ebe49e941f5b5252812579228a4fe4b76331a674",
        "bytes": 111002,
        "pages": 8
      },
      "integrity": {
        "signed_object": "legal_analysis.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "legal_analysis.content.json.asc",
        "digest_file": "legal_analysis.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify legal_analysis.content.json.asc legal_analysis.content.json",
          "sha256sum -c legal_analysis.content.json.sha256"
        ]
      },
      "content": {
        "text": "Báo cáo pháp lý và kinh tế\nPhân tích pháp lý — Điều khoản dịch vụ và tuân thủ quy định\n\nTheo điều kiện của họ. Các quyền của bạn.\n\nPHẦN NÀY CHỨNG MINH ĐIỀU GÌ\n\nCuộc kiểm toán pháp lý chuyên sâu này đánh giá sự bất đối xứng hợp đồng giữa Công ty Cổ phần Valve và người dùng Steam tại các khu vực pháp lý quan trọng. Báo cáo này làm rõ cách thức giấy phép đăng ký có thể thu hồi tước bỏ quyền sở hữu hợp pháp của người tiêu dùng, phân tích án lệ của Tòa án Châu Âu về nguyên tắc cạn kiệt quyền phân phối đối với nội dung số, và xem xét việc tuân thủ theo Đạo luật Dịch vụ Kỹ thuật số (DSA) và Điều 15. của Luật về Quyền Tác giả và Quyền Liên quan (GDPR). Phân tích này cho thấy các cơ chế thực thi tự động hoạt động mà không có cơ chế kháng cáo có ý nghĩa, trong khi các khoản phí thị trường của nền tảng hệ thống thu lợi kinh tế từ mọi giao dịch ngang hàng.\n\n← Quay lại Bản tóm tắt dành cho lãnh đạo\n\nBáo cáo này trình bày phân tích về mặt pháp lý, kinh tế và kỹ thuật liên quan đến khoảng cách giữa các quy tắc nền tảng mà Steam đã công bố và thực trạng của người tiêu dùng: việc thực thi tự động với rất ít cơ hội khiếu nại, cùng với sự kiểm soát rộng rãi của doanh nghiệp đối với tài sản kỹ thuật số. Các số liệu đều được trích dẫn nguồn; trong trường hợp không thể xác định nguồn gốc từ hồ sơ gốc, số liệu đó đã được loại bỏ.\n\nVector 1\n\nThay thế khái niệm “quyền sở hữu” bằng một giấy phép có thể thu hồi, để các tài sản số có thể được thu hồi theo thỏa thuận.\n\nVector 2\n\nHệ thống xử lý tự động (VACNet) – theo thông báo về các lệnh cấm tại Steam, hệ thống này khẳng định không thể hủy bỏ các lệnh cấm đó.\n\nVector 3\n\nCác biện pháp kiểm soát tài khoản và tài sản, kết hợp với khoản phí thị trường CS2 của 15% (gồm phí 5%, Steam và 10% dành cho nhà phát hành), làm giảm giá trị của hệ sinh thái trong mỗi lần bán lại.\n\nSự bất đối xứng về thuật ngữ\nGiấy miễn trừ trách nhiệm và giấy phép có thể thu hồi\n2.1 Mô hình “đăng ký” so với quyền sở hữu\n\nĐiều 2 trong Thỏa thuận người đăng ký của Steam chỉ cấp cho người dùng một giấy phép cá nhân, không độc quyền, không thể chuyển nhượng và có thể thu hồi. Theo thỏa thuận này, Valve có quyền chấm dứt tài khoản vào bất kỳ thời điểm nào, và số dư chưa sử dụng trong Ví Steam có thể bị mất.\n\n2.2 Ảo tưởng về việc hoàn tiền so với Chỉ thị về Quyền của Người tiêu dùng của Liên minh Châu Âu\nKhung pháp lý\tCơ chế hoàn tiền\tGiới hạn\nEU Consumer Rights Directive\tUnconditional 14-day right of withdrawal on digital content\tWaived if download begins with explicit consumer consent\nSteam SSA\t14 days / under 2 hours played\tValve may deny at its discretion for \"abuse\"\nĐánh giá\n\nValve EU đặt ra điều kiện cho quyền hủy bỏ theo quy định trong ngày “14-” của mình trong khung thời gian “14 ngày / under 2 giờ”, điều này phải được chấp nhận tại thời điểm tải xuống trước khi sản phẩm có thể được đánh giá. Chính sách này thu hẹp — chứ không mở rộng — quyền theo quy định; việc liệu điều này có hợp pháp hay không là vấn đề thuộc thẩm quyền của cơ quan có thẩm quyền, chứ không phải là kết luận được đưa ra tại đây.\n\nTranh tụng\nThị trường thứ cấp và Luật Cạnh tranh\nUFC Que Choisir kiện Valve — Pháp\n2019\nTòa án Paris: Nguyên tắc cạn kiệt quyền được áp dụng đối với trò chơi điện tử — việc bán lại là hợp pháp\nTháng 10 năm 2022\nTòa phúc thẩm Paris đã hủy bỏ phán quyết\n23 Tháng 10 năm 2024\nTòa án Cấp cao (Tòa án Tối cao): trò chơi điện tử là “tác phẩm phức tạp” theo Chỉ thị InfoSoc, chứ không phải phần mềm. Bán lại sản phẩm kỹ thuật số bị cấm. “Valve” vẫn chiếm ưu thế.\nVụ kiện chống độc quyền liên quan đến Wolfire Games — Hoa Kỳ (Vụ kiện chống độc quyền “Valve”, Số vụ2:21-cv-00563)\n\nĐiều khoản “Quốc gia được đối xử ưu đãi nhất” (PMFN) trên nền tảng Valve cấm các nhà phát triển bán các chìa khóa “Steam” với giá rẻ hơn trên bất kỳ nền tảng nào khác. Các cửa hàng cạnh tranh — ngay cả những nơi thu phí hoa hồng 12% so với mức 30% của Valve — cũng không được phép chuyển khoản tiết kiệm này cho người tiêu dùng.\n\n336Tổng số nhân viên của Valve (2021). Nguồn: tài liệu điều tra đã được công bố.\n79các nhân viên phụ trách toàn bộ nền tảng Steam. Nguồn: tài liệu điều tra đã được công bố.\n$3.5Mlợi nhuận ròng trên mỗi nhân viên. Nguồn: tài liệu điều tra đã được công bố.\n\nCác hồ sơ điều tra chưa được niêm phong cho thấy $8.5tỷ doanh thu gộp tại 2021 đối với nhân viên của 336. Các 79-cá nhânSteamđội đã xử lý các yêu cầu hỗ trợ 373,000cùng với các phiếu yêu cầu hỗ trợ hàng ngày bằng cách chuyển chúng đến các trung tâm cuộc gọi tự động do bên thứ ba cung cấp.\n\nTÀI LIỆU TÒA ÁN ĐÃ BỊ BỎ NIÊM PHONG · W.D. WASH. VỤ ÁN2:21-CV-00563Bản ghi nhớ nội bộ về việc điều tra\n\nTim Sweeney (Giám đốc điều hành, Epic Games) gửi đến Gabe Newell: \"Tại sao Steam vẫn thu 30% doanh thu thô trong khi chi phí xử lý thanh toán là 2–5% và băng thông CDN là $0.002/GB? Nếu trừ đi các tựa game hàng đầu 25 trên Steam, tôi dám cá rằng Valve đã thu được lợi nhuận từ phần lớn các tựa game tiếp theo 1,000 nhiều hơn cả chính các nhà phát triển.\"\n\nThư chuyển tiếp nội bộ của Scott Lynch (Giám đốc Điều hành, Tập đoànValve) gửi cho Gabe Newell: \"Cậu giận à, anh bạn?\"\n\nBản phản biện lời khai có tuyên thệ (Bloomberg, 2026): Theo Điều 30 (b) (1) về việc lấy lời khai, Gabe Newell đã khai rằng \"Valve không có chính sách hay thói quen áp đặt giá cả đối với các nhà phát triển phần mềm bên thứ ba trên các nền tảng khác.\" Các nguyên đơn đã đưa ra trước Newell các bản ghi nhớ nội bộ của Valve, chứng minh việc công ty này tích cực can thiệp vào giá cả và đe dọa gỡ bỏ sản phẩm khỏi danh mục đối với các nhà phát triển đặt giá thấp hơn trên các cửa hàng cạnh tranh. Vào cuối tháng 3 2026,, Tòa án Liên bang đã bác bỏ đơn yêu cầu xét xử sơ thẩm của Valve, đồng thời chuyển vụ kiện tập thể của các nhà phát triển 32,000-sang xét xử bởi bồi thẩm đoàn.\n2024 tháng 11\n\nVụ kiện tập thể đã được công nhận đối với ~ Nhóm phát triển32,000 những người đã trả hoa hồng kể từ tháng 1 năm 2017, cùng với một vụ kiện tập thể của người tiêu dùng diễn ra song song.\n\nSố tiền bồi thường được yêu cầu\n\n$3.1B\nBị xử phạt gấp ba lần theo luật chống độc quyền của Hoa Kỳ = $9.3B nguy cơ phơi nhiễm.\n\nTháng 6 năm 2026: Một vụ kiện mới cáo buộc rằng Microsoft và Valve đã tham gia vào một thỏa thuận độc quyền nhằm kìm hãm cạnh tranh trong lĩnh vực phân phối trò chơi trên máy tính cá nhân.\n\nChương trình đào tạo chính quy về Tội phạm tài chính và Chống rửa tiền (AML)\nValve Lời thú nhận chính thức: Các vụ thanh lý do gian lận trên toàn cầu (28 tháng 10 năm 2019)\n\nVào ngày 28 tháng 10 năm 2019, Valve đã chính thức chấm dứt việc giao dịch và bán lại trên thị trường các mã khóa container Counter-Strike mới mua. Trong thông báo chính thức công khai của mình (blog.counter-strike.net/2019/10/26113), Công tyValve đã thừa nhận bằng văn bản rằng nền kinh tế ảo do công ty này thiết kế đã trở thành một trung tâm rửa tiền quốc tế:\n\n\"Trước đây, hầu hết các giao dịch mã kích hoạt mà chúng tôi ghi nhận đều diễn ra giữa những khách hàng hợp pháp. Tuy nhiên, gần đây các mạng lưới lừa đảo toàn cầu đã chuyển sang sử dụng mã kích hoạt CS:GO để thanh lý số tiền thu được từ các hoạt động lừa đảo. Hiện tại, gần như tất cả các giao dịch mua mã kích hoạt sau đó được trao đổi hoặc bán trên thị trường đều được cho là có nguồn gốc từ các hoạt động lừa đảo.\"\n\nBối cảnh pháp lý: Lời thú nhận này được đưa ra sau khi Ủy ban Cờ bạc Tiểu bang Washington (WSGC) đưa ra tối hậu thư chính thức đối với Valve và các lệnh “Ngừng và Chấm dứt Hoạt động” ngày 7 tháng 2016 do Cố vấn Pháp lý của Valve, ông Karl Quackenbush, ban hành đối với các tên miền cờ bạc giao dịch skin trên 23 (bao gồm CSGO Lotto, CSGOLounge và OPSkins), chỉ sau khi các cuộc điều tra hình sự về cờ bạc đe dọa đến hoạt động của nền tảng này.\n\nThẩm quyền\nMột chủ sở hữu quyền tại Nga mà người dùng không thể liên hệ được\n\nThỏa thuận đăng ký cho thấy Valve là một bên có rất ít nghĩa vụ và không ai có thể liên hệ được: các biện pháp khóa tài khoản là vĩnh viễn, các đơn kháng cáo đều bị từ chối, và quyền truy cập bị thu hồi trên toàn bộ các khu vực chỉ qua một dòng ghi chú về “các khu vực bị trừng phạt”. Trái ngược với thái độ đó là cách Valve hành động khi lợi ích thương mại của chính họ bị đe dọa tại một khu vực pháp lý mà bình thường họ coi là khó khăn.\n\nValve v. Touch Skins — khiếu nại về quyền sở hữu trí tuệ trước phiên tòa, Nga\n1 2026 tháng 9\nValve thông qua công ty luật của Nga Melling, Voitishkin & Các đối tác, gửi thư yêu cầu trước phiên tòa đến các nhà điều hành của Giao diện cảm ứng, một bộ thay đổi giao diện CS2 quy mô lớn, được gửi qua Bưu điện Nga và email.\nCơ sở\nBa nhóm hành vi vi phạm bị cáo buộc: quyền độc quyền đối với phần mềm; quyền đối với hình thức bên ngoài của các skin vũ khí, dao và găng tay; và các nhãn hiệu của Valve. Hành vi của các nhà điều hành được đánh giá là có chủ ý và kéo dài.\nNhu cầu\nNgừng hoạt động ngay lập tức và xóa toàn bộ cơ sở hạ tầng — phần mềm mã nguồn, các trang web và trang mạng xã hội — nếu không tuân thủ, Valve có quyền khởi kiện tại tòa án Nga để mức bồi thường tiền mặt đáng kể và chuyển vụ việc này cho thực thi pháp luật nhằm đánh giá tính chất hình sự.\nKết quả\nSau khi nhận được lá thư, nền tảng này đã thông báo sẽ ngừng hoạt động. Đây được cho là lần đầu tiên Tổ chức Bảo vệ Quyền Tự do Ngôn luận (Valve) sử dụng các biện pháp pháp lý nhằm vào một nhà phát triển phần mềm thay đổi giao diện tại Nga.\n\nTheo thông tin từ chuyên gia khai thác dữ liệu Maxim \"GabeFollower\" Poletaev (X, ~11 ngày 2026 tháng 9) và các phương tiện truyền thông game của Nga. Đây là một yêu cầu trước khi xét xử, không phải là đơn kiện đã được nộp; chưa có số hồ sơ vụ án nào được công bố. Thông tin này được trình bày ở đây theo nội dung đã được báo cáo, không phải là hồ sơ tòa án. Nguồn: dota2.ru đã lưu trữ 2026-09-24 ↗ · Shazoo.\n\nCùng một thẩm quyền, nhưng theo hướng ngược lại\n\nValve không phải là người xa lạ với hệ thống pháp luật và quy định của Nga. Nó tuân thủ các quy định của Roskomnadzor: Theo yêu cầu của cơ quan quản lý, trang này đã gỡ bỏ các trang cộng đồng 260và Steam chứa nội dung bị cấm, đồng thời Roskomnadzor đã công khai khẳng định rằng trang Steam đáp ứng các yêu cầu của pháp luật. Luật “định hướng truy cập” của Nga (Luật Liên bang 236-FZ, có hiệu lực từ ngày 2022), quy định các nền tảng internet nước ngoài quy mô lớn phục vụ người dùng Nga phải thiết lập sự hiện diện tại địa phương và mở tài khoản liên lạc với Roskomnadzor. Valve không chỉ tuân thủ các lệnh gỡ bỏ nội dung của cơ quan quản lý này mà hiện nay còn sử dụng luật sư Nga và đe dọa khởi kiện tại các tòa án Nga để bảo vệ các giao diện (skins) của mình như tài sản trí tuệ.\n\nVì vậy, nền tảng này có khả năng tiếp cận, đủ năng lực và kiên quyết bảo vệ quyền lợi của mình ngay khi liên quan đến doanh thu. Điều này trái ngược hoàn toàn với người dùng: một khách hàng trả phí ở khu vực bị áp đặt lệnh trừng phạt sẽ được thông báo rằng mối quan hệ đã chấm dứt, quyền truy cập vào cộng đồng bị khóa cho đến khi 2038, phiếu yêu cầu được giải quyết, và không có diễn đàn nào để có thể phản biện quyết định đó — \"Họ rất sẵn lòng nhận tiền của tôi và xử lý các giao dịch của tôi\", việc hoàn tiền từ cùng một tài khoản, có địa chỉ IP từ Iran, đã được phê duyệt một năm trước đó (r/pcgaming, 4 ngày 2026 tháng 8; thêm các thư yêu cầu tuân thủ trong Triển lãm về nền kinh tế thẻ). Valve sử dụng toàn bộ cơ chế của hệ thống pháp luật quốc gia để bảo vệ một skin; điều này khiến người dùng đã mua skin không được hưởng bất kỳ thủ tục pháp lý nào.\n\nValve coi cùng một khu vực pháp lý đó như một phạm vi mà họ có thể hành động và tuân thủ, bất cứ khi nào lợi ích liên quan thuộc về Công ty Truyền thông và Công nghệ (Valve) — luật sư Nga, mối đe dọa từ các tòa án Nga, các lệnh gỡ bỏ nội dung của Roskomnadzor đã được thực hiện — trong khi coi các nghĩa vụ của mình đối với người dùng của thị trường đó, cũng như của mọi thị trường khác, là nằm ngoài mọi quy trình pháp lý. Nó là chủ sở hữu quyền khi liên quan đến doanh thu của mình, nhưng lại là một bên không thể tiếp cận khi liên quan đến quyền lợi của người dùng.\n\nNguồn: TASS (RKN: Tuân thủ theo Steam) · Luật Liên bang số 236-FZ.\n\nChủ nghĩa cơ hội pháp lý\nSự nhượng bộ về điều khoản trọng tài\n2023 — vụ tấn công\n\nCác công ty luật (Zaiger LLC, Mason LLP) đã thu hút hàng nghìn người dùng thông qua mạng xã hội và đồng loạt nộp hàng chục nghìn đơn yêu cầu trọng tài riêng lẻ.\n\nSự xuất hiện của Valve\n\n$225M+\nphí nộp đơn trọng tài không được hoàn lại, trước khi bất kỳ vụ việc nào được xét xử trên cơ sở nội dung vụ việc. Được tính toán theo Quy tắc Trọng tài Tiêu dùng và các Phụ lục Bổ sung về Trọng tài Hàng loạt của Hiệp hội Trọng tài Hoa Kỳ (AAA). Các nguyên đơn do Zaiger LLC và Mason LLP đại diện đã nộp khoảng75,000 yêu cầu trọng tài cá nhân chống lại Công ty Valve (song song với các khiếu nại về chống độc quyền trong Wolfire Games LLC và các bên khác kiện Công tyValve, Số vụ án: 2:21-cv-00563-JCC, W.D. (Tòa án Quận Washington). Theo biểu phí dành cho người tiêu dùng của AAA, bên bị đơn là doanh nghiệp phải nộp các khoản phí hành chính không hoàn lại cho vụ án và khoản đặt cọc để chỉ định trọng tài viên khoảng $3,000+ cho mỗi vụ án riêng lẻ (75,000 hồ sơ × $3,000 = khoảng $225M tiền nghĩa vụ thủ tục phải trả trước). Xem các báo cáo pháp lý của Bloomberg Law và Reuters về rủi ro liên quan đến trọng tài hàng loạt trong lĩnh vực công nghệ (2023–2024).\n\nKỳ\tCơ chế giải quyết tranh chấp của SSA\tHiệu ứng quan sát được\tKết quả\nBefore Sep 2024\tMandatory individual arbitration + class-action waiver\tIndividual litigation becomes economically irrational for users\tMass arbitration → $225M fee threat\nAfter Sep 2024\tDisputes in King County, WA courts only\tArbitration costs are avoided; cases consolidate in a single forum\tClass actions now possible\nKết luận\n\nTrong hơn mười năm, Cơ quan An sinh Xã hội (SSA) đã yêu cầu người dùng từ bỏ quyền được xét xử bởi bồi thẩm đoàn để chuyển sang hình thức trọng tài cá nhân. Sau khi các đơn yêu cầu trọng tài hàng loạt khiến cơ chế này trở nên tốn kém về mặt tài chính đối với Hiệp hội Người dùng Điện tử (Valve), SSA đã được sửa đổi để chuyển các tranh chấp sang các tòa án Hạt King. Thay đổi này được đưa ra mà không có cơ chế từ chối tham gia có ý nghĩa; lựa chọn thay thế cho việc chấp nhận là mất quyền truy cập vào các tài sản kỹ thuật số đã mua bằng cách xóa tài khoản.\n\nThực thi dựa trên thuật toán\nVACNet, giả định có tội và kết quả dương tính giả\nTháng 10 năm 2023 — AMD Anti-Lag+\n\nMột bản cập nhật trình điều khiển AMD (phiên bản 23.10.1) đã kích hoạt tính năng Anti-Lag+ trong CS2, khiến tính năng này chặn các hàm DLL của trò chơi. Hệ thống VAC đã phân loại hành vi này là việc chèn mã gian lận và áp dụng lệnh cấm vĩnh viễn đối với hàng nghìn người dùng hợp pháp trước khi trang web Valve can thiệp.\n\n2023 tháng 12 — độ phân giải cao (DPI)\n\nNhững người chơi có chỉ số DPI vượt quá 10,000 khi xoay camera quá nhanh đã bị cấm vĩnh viễn. Hệ thống VACNet không thể phân biệt được chuyển động thực tế của chuột với phần mềm gian lận “spinbot”.\n\nDanh mục hỗ trợ\tThời gian phản hồi được công bố\tKết quả thực tế\nRefund requests\t50 min – 1.5 hr\tAutomatic approval (<14 days, <2 hours played)\nAccount security / recovery\t3–12 hours\tDepends on documentation provided\nContesting a VAC ban\tForm response\tComplete refusal. Support cannot reverse VAC decisions. The ban is permanent.\nChính sách chính thức của “Valve”\n\n\"Các lệnh cấm của VAC là vĩnh viễn, không thể thương lượng và không thể được gỡ bỏ bởi bộ phận Hỗ trợ của Steam.\"\n\nKênh hỗ trợ đã thông báo về lệnh cấm cũng chính là kênh thông báo về việc từ chối xem xét lại: Steam Bộ phận Hỗ trợ cho biết họ không thể hủy bỏ quyết định của VAC. Đối với người dùng, phán quyết của thuật toán chính là kết quả có hiệu lực.\n\nCác khía cạnh kinh tế của việc bán lại\nQuyền kiểm soát đối với tài sản ảo và phí bán lại\nPhí thị trường CS2 của Hiệp hội Nhà xuất bản Độc lập (15%) — giá trị bị trừ đi mỗi khi bán lại\nLặp lại\tSố dư của người mua\tNgười bán nhận được\t“Burned” (15%)\n1\t$100.00\t$85.00\t$15.00\n2\t$85.00\t$72.25\t$12.75\n3\t$72.25\t$61.41\t$10.84\n10\t$23.16\t$19.68\t~$3.47\nTotal\t$100 → dust\tValve collects the 15% fee on each resale. Users must add new money to keep trading.\nThay đổi quy định về chương trình đổi cũ lấy mới của CS2 — Tháng 10 năm 2025\n\nKhông có thông báo trước, Valve đã điều chỉnh các quy định về hợp đồng đổi nâng cấp trong CS2 để cho phép người chơi chắc chắn nhận được các loại dao và găng tay hiếm khi đổi lấy các vật phẩm cấp Covert. Giá dao giảm, giá vật phẩm cấp Covert tăng mạnh, và tình trạng bán tháo hoảng loạn đã diễn ra trên toàn thị trường.\n\nValve viện dẫn Điều 7 của Đạo luật An sinh Xã hội (SSA) làm cơ sở bảo vệ — không chịu trách nhiệm pháp lý đối với việc thay đổi quy tắc của nền tảng. Người dùng phải tự chịu rủi ro trong một nền kinh tế mà các quy tắc Valve có thể thay đổi mà không cần thông báo trước hoặc bồi thường. Quy mô của khoản lỗ được báo cáo trên toàn thị trường đang gây tranh cãi và không được nêu ra tại đây do thiếu nguồn tin chính thức.\n\nPhản ứng của các cơ quan quản lý châu Âu\nUOKiK, DSA và Luật Công bằng Kỹ thuật số\nUOKiK — Ba Lan, ngày 2024 tháng 5\n\nCơ quan chống độc quyền Ba Lan (UOKiK) đã khởi xướng thủ tục điều tra chống độc quyền chính thức đối với Tập đoàn Valve và năm nhà phát hành/phân phối trò chơi trong nước liên quan đến các cáo buộc về thỏa thuận định giá, các điều khoản hạn chế về sự ngang bằng giá và các hành vi chặn truy cập theo khu vực, khiến người tiêu dùng Ba Lan phải trả giá cao hơn tới 20% so với các thị trường lân cận thuộc Khu vực Kinh tế Châu Âu (EEA) khi mua trò chơi kỹ thuật số. Trong khuôn khổ cuộc điều tra chống độc quyền này, các thanh tra viên của UOKiK và cảnh sát đã tiến hành các cuộc đột kích vào rạng sáng và kiểm tra chứng cứ tại các cơ sở ở Ba Lan của các nhà xuất bản và nhà phân phối đối tác trong nước (không phải các văn phòng chi nhánh củValve, vì Valve không có pháp nhân tại Ba Lan). Mức phạt theo quy định có thể lên tới 10% doanh thu hàng năm. Nguồn: Thông báo chính thức của UOKiK: “Chủ tịch UOKiK đã khởi xướng thủ tục tố tụng chống lại Valve và các nhà phát triển trò chơi”, ngày 2024 tháng 5.\n\nĐạo luật về Dịch vụ Kỹ thuật số (DSA)\n\nYêu cầu tính minh bạch trong quá trình kiểm duyệt tự động. Steam không công bố dữ liệu về các trường hợp dương tính giả/âm tính giả của VACNet, và kênh hỗ trợ của họ cho biết các quyết định của VAC không thể được đảo ngược.\n\nĐạo luật Công bằng Kỹ thuật số — 2026\n\nCác quy định dự kiến: quyền truy cập lâu dài vào nội dung trả phí, cấm sử dụng các “mô hình lừa đảo” (dark patterns) tại thời điểm từ bỏ quyền, công nhận quyền sở hữu đối với tài sản kỹ thuật số, và bảo vệ khỏi việc tịch thu vĩnh viễn tài sản.\n\nKết luận\nNhững điểm không khớp đã được ghi nhận giữa các quy định và hồ sơ\n1\n\nKhoảng cách về quyền sở hữu. Người dùng phải trả đầy đủ giá cho một giấy phép mà theo thỏa thuận, Valve có quyền thu hồi. Tòa án Tối cao Pháp (tháng 10 năm 2024) đã phán quyết rằng việc bán lại bản quyền kỹ thuật số không được bảo hộ, qua đó xác lập quan điểm này trong pháp luật.\n\n2\n\nThực thi dựa trên thuật toán. VACNet đã ban hành các lệnh cấm sai (trình điều khiển AMD, các sự cố liên quan đến độ phân giải cao). Steam Bộ phận Hỗ trợ cho biết họ không thể hủy bỏ quyết định của VAC, do đó thuật toán chính là cơ sở quyết định cuối cùng.\n\n3\n\nTiết kiệm chi phí. Phí thị trường CS2 của 15% (5% Steam + 10% phí nhà xuất bản) làm giảm giá trị ở mỗi lần bán lại, và các quy định của nền tảng có thể thay đổi mà không cần thông báo trước; trách nhiệm pháp lý của Valve đối với những thay đổi đó được miễn trừ theo SSA.\n\n4\n\nĐiều khoản trọng tài đã bị loại bỏ. SSA đã bãi bỏ quy định bắt buộc phải đưa vụ việc ra trọng tài vào tháng 9 năm 2024, sau khi hàng loạt đơn khiếu nại được nộp khiến Valve phải chịu khoản phí khoảng $225M. Người dùng không được cung cấp bất kỳ lựa chọn từ chối nào có ý nghĩa trước sự thay đổi này.\n\n5\n\nThẩm quyền xét xử có chọn lọc. Valve đã thuê luật sư người Nga (Melling, Voitishkin & Partners) và đe dọa khởi kiện Touch Skins tại tòa án Nga, trong khi đồng thời coi các nghĩa vụ của mình đối với người dùng trên chính thị trường đó là nằm ngoài mọi thủ tục xét xử. Công ty “Valve” đóng vai trò là chủ sở hữu quyền khi lợi ích thương mại của họ bị ảnh hưởng, và trở thành bên không thể tiếp cận khi quyền lợi của người dùng được đề cập.\n\n← Phần I: Vượt qua máy chủ proxy và cờ bạcPhần II: Quyền truy cập và trách nhiệm giải trình →\n\nCác nguồn pháp lý và hồ sơ vụ án được trích dẫn theo nhà xuất bản và kho lưu trữ gốc. Không có bất kỳ tuyên bố nào về quyền sở hữu đối với các tài liệu gốc.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Phân tích pháp lý — Điều khoản dịch vụ và tuân thủ quy định"
          },
          {
            "level": 2,
            "id": null,
            "text": "Giấy miễn trừ trách nhiệm và giấy phép có thể thu hồi"
          },
          {
            "level": 3,
            "id": null,
            "text": "2.1 Mô hình “đăng ký” so với quyền sở hữu"
          },
          {
            "level": 3,
            "id": null,
            "text": "2.2 Ảo tưởng về việc hoàn tiền so với Chỉ thị về Quyền của Người tiêu dùng của Liên minh Châu Âu"
          },
          {
            "level": 2,
            "id": null,
            "text": "Thị trường thứ cấp và Luật Cạnh tranh"
          },
          {
            "level": 3,
            "id": null,
            "text": "UFC Que Choisir kiện Valve — Pháp"
          },
          {
            "level": 3,
            "id": null,
            "text": "Vụ kiện chống độc quyền liên quan đến Wolfire Games — Hoa Kỳ (Vụ kiện chống độc quyền “Valve”, Số vụ2:21-cv-00563)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve Lời thú nhận chính thức: Các vụ thanh lý do gian lận trên toàn cầu (28 tháng 10 năm 2019)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Một chủ sở hữu quyền tại Nga mà người dùng không thể liên hệ được"
          },
          {
            "level": 3,
            "id": null,
            "text": "Valve v. Touch Skins — khiếu nại về quyền sở hữu trí tuệ trước phiên tòa, Nga"
          },
          {
            "level": 3,
            "id": null,
            "text": "Cùng một thẩm quyền, nhưng theo hướng ngược lại"
          },
          {
            "level": 2,
            "id": null,
            "text": "Sự nhượng bộ về điều khoản trọng tài"
          },
          {
            "level": 2,
            "id": null,
            "text": "VACNet, giả định có tội và kết quả dương tính giả"
          },
          {
            "level": 2,
            "id": null,
            "text": "Quyền kiểm soát đối với tài sản ảo và phí bán lại"
          },
          {
            "level": 3,
            "id": null,
            "text": "Phí thị trường CS2 của Hiệp hội Nhà xuất bản Độc lập (15%) — giá trị bị trừ đi mỗi khi bán lại"
          },
          {
            "level": 3,
            "id": null,
            "text": "Thay đổi quy định về chương trình đổi cũ lấy mới của CS2 — Tháng 10 năm 2025"
          },
          {
            "level": 2,
            "id": null,
            "text": "UOKiK, DSA và Luật Công bằng Kỹ thuật số"
          },
          {
            "level": 2,
            "id": null,
            "text": "Những điểm không khớp đã được ghi nhận giữa các quy định và hồ sơ"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/vi/#briefing-heading",
          "https://dota2.ru/news/67707-valve-cerez-uristov-napravila-krupnoj-rossijskoj-skincendzer-platforme-trebovanie-o-prekrasenii-deatelnosti/",
          "http://web.archive.org/web/20260924181657/https://dota2.ru/news/67707-valve-cerez-uristov-napravila-krupnoj-rossijskoj-skincendzer-platforme-trebovanie-o-prekrasenii-deatelnosti/",
          "https://shazoo.ru/2026/09/12/190508/valve-cerez-rossiiskix-iuristov-dobilas-zakrytiia-krupnogo-skinceindzera-dlia-cs2",
          "https://www.reddit.com/r/pcgaming/comments/1vf24lu/warning_to_all_gamersexpats_steam_took_my_money/",
          "https://phishdestroy.io/steam_dossier/vi/card_economy.html#asymmetry",
          "https://tass.ru/obschestvo/23235387",
          "https://base.garant.ru/401414628/",
          "https://uokik.gov.pl/postepowanie-wyjasniajace-w-sprawie-valve-i-dystrybutorow-gier",
          "https://phishdestroy.io/steam_dossier/vi/",
          "https://phishdestroy.io/steam_dossier/vi/investigation_part2.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/vi/legal_analysis.content.json",
      "export_json_sha256": "4c5eb992d64e7c8f2f1fd70c3b13c17b10878fb1507bcd90546f7e033cefa93b"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "vi/license_disclaimer.html",
      "language": "vi",
      "title": "Giấy phép · Quyền · Tuyên bố miễn trừ trách nhiệm — PhishDestroy",
      "source_url": "https://phishdestroy.io/steam_dossier/vi/license_disclaimer",
      "source_html_sha256": "791de1f7ca2c8c355c115c59c929a1aad0a891a28c781f3bc7d27a727ee9e65d",
      "exported_at": "2026-09-29T00:23:02.386Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "license_disclaimer.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/vi/license_disclaimer.pdf?v=print-20260929-v5",
        "sha256": "e0428c99d2fbdaa957db0653cae2eb2f952e123b9b0c79c5acc72dc4ac26eeec",
        "bytes": 121846,
        "pages": 11
      },
      "integrity": {
        "signed_object": "license_disclaimer.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "license_disclaimer.content.json.asc",
        "digest_file": "license_disclaimer.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify license_disclaimer.content.json.asc license_disclaimer.content.json",
          "sha256sum -c license_disclaimer.content.json.sha256"
        ]
      },
      "content": {
        "text": "PHISHDESTROYĐiều tra pháp y · Valve / Steam\nGiấy phép · Quyền · Tuyên bố miễn trừ trách nhiệm\nGiấy phép và Tuyên bố miễn trừ trách nhiệm pháp lý — Cam kết đưa vào phạm vi công cộng\n\nTất cả các quyền đã đầu hàng trước loài người.\n\nPHẦN NÀY CHỨNG MINH ĐIỀU GÌ\n\nVăn bản này quy định việc chuyển giao vô điều kiện vào phạm vi công cộng (CC0 1.0 Universal) và các điều khoản cấp phép phần mềm của MIT áp dụng cho Hồ sơ PhishDestroy Steam. Tất cả các kết quả giám định pháp y, tập dữ liệu chứng cứ, sơ đồ mạng và phương pháp phân tích đều được chuyển giao vĩnh viễn vào phạm vi công cộng để sử dụng không hạn chế trong các lĩnh vực quản lý, pháp lý và học thuật trên toàn thế giới.\n\n← Quay lại Bản tóm tắt dành cho lãnh đạo\n\nPhishDestroy từ bỏ mọi quyền đối với tài liệu này — bao gồm quyền sao chép, bán hoặc ghi tên mình lên đó. Phần tiếp theo là hai văn bản được trình bày dưới cùng một giọng điệu: một lá thư ngỏ gửi tới Valve, được viết theo cách chúng tôi thường viết, và một văn bản từ bỏ quyền chính thức được soạn thảo dành cho cơ quan có thẩm quyền sẽ tiếp tục triển khai nội dung này.\n\nĐiều tra · Công tyValve / SteamPhiên bản công khai — không có hạn sử dụng, không thể thu hồi\nĐƯỢC MIỄN\nPhần IGiấy phép — phần pháp lý thực tế, nhưng mang tính con người\n\nPhishDestroy từ bỏ mọi quyền đối với tài liệu này. Hoàn toàn không còn. Đã hết. Xong rồi. Bạn có thể sao chép, bán, ghi tên mình lên đó, xăm hình lên người sếp của bạn, hay làm bất cứ điều gì. Không cần ghi nguồn, không cần nhắn tin riêng, cũng không cần gửi thiệp cảm ơn.\n\nMột quy tắc thực tế (vâng, chỉ một thôi)\n\nBẠN KHÔNG có quyền quyết định liệu mình có phải là kẻ khủng bố hay không.\n\nNếu bạn là người dùng đến từ Nga hoặc bất kỳ quốc gia nào bị OFAC áp đặt lệnh trừng phạt — tài liệu này KHÔNG dành cho bạn. Không có kẽ hở nào cả. Chúc bạn “thưởng thức” các biện pháp trừng phạt của mình.\n\nVà nếu bạn đã chuyển khu vực trên ứng dụng “Steam” sang Thổ Nhĩ Kỳ trong khi đang ở Moscow — xin chúc mừng sự sáng tạo về địa lý của bạn. Bạn vẫn là người Nga. Các biện pháp trừng phạt vẫn có hiệu lực. Đó chính xác là vấn đề ở đây.\n\nPhần IIĐiều này là gì và tại sao nó lại tồn tại\n\nChúng tôi sẽ đăng tải nhiều thông tin về “Valve” hơn cả những gì một nhân viên bình thường của “Valve” biết về chính bản thân họ. Đó không phải là lời khoe khoang. Đó chỉ đơn giản là kết quả mà chúng tôi đạt được mà thôi.\n\nLàm sao chúng ta lại đến được đây? Câu chuyện khá thú vị: Steam thực ra chính là người đã “tạo ra” chúng ta. Nền tảng này đã “nuôi dưỡng” chúng ta bằng những kẻ lừa đảo, những phiếu hỗ trợ kỹ thuật, và cả hệ sinh thái lách lệnh cấm của nó — và giờ thì chúng ta đã ở đây. Không có gì phải bực bội cả. Thực ra, điều này còn mang một chút chất thơ nữa.\n\nĐối với những ai chưa đọc câu chuyện nguồn gốc — chúng ta đã từng biết đến các luật sư châu Âu cực kỳ đắt đỏ củaValve (Taylor Wessing, vì các bạn đã hỏi):\n\nhttps://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d đã lưu trữ 2026-08-21 ↗\n\nMột cuộc gặp gỡ thật thú vị. Đặc biệt là khi xét đến mức giá tính theo giờ của họ.\n\nValve có biết không? Có. Taylor Wessing có biết không? Gần như chắc chắn là có. Nhưng khi giàu đến mức đó, luật pháp chỉ là một thứ gì đó mang tính tham khảo hơn là một yêu cầu bắt buộc, phải không?\n\nThực ra, đó cũng chính là câu trả lời rồi.\n\nSteam đã dành nhiều năm để “nuôi dưỡng” những kẻ lừa đảo. Không phải lúc nào cũng là cố ý — đôi khi những kẻ lừa đảo chỉ vô tình dính líu đến “Valve” do có liên quan. Chúng tôi không cố gắng làm cho vấn đề trở nên kịch tính. Chúng tôi chỉ cố gắng diễn đạt một cách chính xác. Thành thật mà nói, điều đó còn khó hơn là làm cho vấn đề trở nên kịch tính — đây chỉ đơn giản là cách chúng tôi viết.\n\nĐây có phải là một mâu thuẫn không?\n— Không.\n\nVấn đề này có thể được giải quyết không?\n— Đúng vậy. Nhưng chúng tôi sẽ không ký bất kỳ thỏa thuận bảo mật (NDA) nào và cũng không tham gia chương trình thưởng lỗi với mức thưởng bèo bọt.\n\nChúng tôi đã phải chờ hơn 4 năm để họ khắc phục vấn đề giả mạo trước khi có thể công khai viết về nó. Bởi vì nếu chúng tôi viết về vấn đề này sớm hơn, Steam hẳn đã giả vờ làm nạn nhân và la hét rằng “mối đe dọa nghiêm trọng!”, rồi đề nghị chúng tôi một khoản tiền lẻ để ký vào một văn bản khiến chúng tôi trở thành tài sản hợp pháp của họ mãi mãi. Không, cảm ơn.\n\n(Ngoài ra: Chính Valve cũng vi phạm thỏa thuận bảo mật (NDA). Ngay cả nhân viên của họ cũng vậy. Đặc biệt là những người ở cấp cao. Nhưng được rồi, hãy nói về phía chúng ta đi.)\n\nPhần IIIThư ngỏ gửi Valve — Thật đấy, hãy đọc bài này đi\n\nValve: nếu bạn muốn tên miền này bị gỡ bỏ, hãy gửi email cho chúng tôi. Không cần luật sư bên ngoài tham gia vào cuộc trao đổi này.\n\nĐối với những ai chưa biết: Tiến sĩ Patrick có bằng Thạc sĩ Luật chuyên ngành Luật Thương mại Quốc tế từ Đại học Aberdeen và — hãy chờ xem — thực sự đã hoàn thành luận án tiến sĩ về luật công nghệ thông tin. Gần đây, ông đã trở thành đối tác tại Taylor Wessing, một công ty có mô hình kinh doanh hoàn toàn dựa trên việc tính phí những khoản tiền khổng lồ cho các doanh nghiệp như Valve nhằm kéo dài vụ việc cho đến khi bên kia cạn kiệt tiền bạc hoặc kiên nhẫn.\n\nChúng tôi không trách anh ta. Những khách hàng giàu có và có vấn đề pháp lý, trả tiền theo giờ — quả là một bước đi khôn ngoan trong sự nghiệp. Chúng tôi chỉ nghĩ rằng các bạn không nên tài trợ cho việc đó.\n\nThỏa thuận (đề nghị công khai, không cần luật sư)\n\nTên miền là điều duy nhất mà Valve có thể thực sự tiếp cận được. Cuộc điều tra, các trường hợp chuyển tiếp và các nguồn lực liên quan đã được triển khai — chúng sẽ tiếp tục diễn ra dù có hay không có tên miền đó.\n\nNếu bạn muốn tên miền:\n\nHãy để các chuyên gia pháp lý về công nghệ thông tin của quý vị đưa ra mức giá hợp lý.\n\n50% sẽ được chuyển đến Quỹ “SEAL”.\n\nChúng tôi sẽ hủy tên miền. Không ồn ào. Không ra tòa. Xong.\n\nĐây không phải là lời đe dọa. Đây là một đề nghị thẳng thắn về điều duy nhất thực sự nằm trong tầm tay. Bạn sẽ không thể có được nó bằng cách nào khác — đó chỉ là bản chất của tình huống này mà thôi.\n\nLiệu chúng ta có “gây tổn hại” trực tiếp cho Valve không? Có lẽ không phải theo cách mà họ cảm nhận được về mặt tài chính. Chúng ta không ảo tưởng. Nhưng chúng ta sẽ làm điều đó một cách trung thực, cởi mở, không chạy theo danh tiếng — bởi vì chúng ta không cần danh tiếng. Chúng ta cần thế giới nhìn thấy những gì vốn dĩ luôn hiển hiện trước mắt công chúng, nếu bạn dành đủ thời gian để quan sát.\n\nChúng tôi có kho lưu trữ kéo dài 5 năm. Những gì các luật sư của Valve đã trình bày trong quá trình thu thập chứng cứ — những dữ liệu mà các đặc vụ có thể truy cập, các dấu vân tay, và các bằng chứng giấy tờ mà họ thực sự đã trao tận tay cho chúng tôi — là đủ rồi. Chúng tôi không cần phải tiết lộ chúng dưới dạng thô.\n\nAi được gì\n\nCác cơ quan quản lý sẽ nhận được bản gốc.\n\nCác nhà nghiên cứu và nhà báo nhận được các phiên bản đã được che bớt thông tin (các báo cáo của nạn nhân, thông tin đăng nhập của trẻ em và những bình luận hỗ trợ đầy duyên dáng của Valve đã bị loại bỏ vì những lý do hiển nhiên).\n\nTrong số các tài khoản bị ảnh hưởng có cả tài khoản của trẻ vị thành niên, nhưng những người này không nhận được thông báo. Phát hiện này đã được đưa vào hồ sơ của cơ quan quản lý sau khi các báo cáo của nạn nhân và thông tin xác thực đã được loại bỏ, bởi vì vấn đề này thuộc thẩm quyền của cơ quan bảo vệ dữ liệu chứ không phải là nội dung của một bài báo.\n\nNgoài ra, Valve — chúng tôi muốn làm rõ một điều trước khi các bạn quyết định sẽ xử lý vụ việc này như thế nào: PhishDestroy là một cộng đồng, không phải một cá nhân. Các bạn đã biết điều đó khi gửi văn bản pháp lý đến cộng đồng mà không thèm trao đổi với cộng đồng — chỉ khai thác dữ liệu rồi cấm các tài khoản đó mà thôi.\n\nCộng đồng chúng tôi không có mâu thuẫn gì với Valve. Chúng tôi không chủ động tìm đến chuyện này. Chính những kẻ lừa đảo mà các bạn nuôi dưỡng đã tìm đến chúng tôi. Chúng tôi đã chặn họ. Và giờ thì chúng tôi vẫn ở đây.\n\nPhần III-BCác nguồn lực của phe đồng minh — một lưu ý dành riêng cho Steam\n\nChúng tôi muốn thẳng thắn về cơ chế khuếch đại này, bởi vì giả vờ như nó không tồn tại sẽ là không trung thực.\n\nTheo những gì chúng tôi nắm được về tình hình cộng đồng, PhishDestroy có ít nhất hai nguồn lực đồng minh sẽ tiếp nhận tài liệu này và triển khai nó.\n\nĐiều đó có nghĩa là gì trong thực tế:\n\nHọ tiếp cận các chủ đề trùng lặp theo cách riêng của mình.\n\nHọ hoạt động độc lập — họ không nhận chỉ đạo từ chúng tôi, và chúng tôi cũng không nhận chỉ đạo từ họ. Cùng một chủ đề chung, nhưng phương pháp tiếp cận khác nhau.\n\nHọ SẼ KHÔNG kích hoạt trên Phần 1.. Họ đang theo dõi.\n\nNếu Valve quyết định không gỡ bỏ trang web này:\n\nCó thể dự đoán rằng chúng sẽ xuất hiện sau Phần 2 hoặc Phần 3.\n\nHọ sẽ lấy những phần hữu ích từ công trình của chúng ta, bổ sung thêm những đóng góp của riêng họ, rồi xuất bản dưới tên tác giả của họ.\n\nĐây chính xác là loại trường hợp mà giấy phép quy định tại Mục 1 được thiết kế dành cho: tài liệu được chia sẻ đến nơi cần thiết, được bổ sung, được mở rộng — và cả chúng tôi lẫn họ đều không có nghĩa vụ phải ghi nguồn cho nhau.\n\n(Lưu ý dành cho các luật sư đang thắc mắc về chuỗi trách nhiệm pháp lý: không có chuỗi trách nhiệm nào cả. Các nguồn thông tin này không nhận được sự chỉ đạo, tài trợ hay dữ liệu từ chúng tôi. Họ chỉ đọc những thông tin công khai và tự đưa ra kết luận của riêng mình. Cũng giống như các bạn vậy.)\n\nChúng tôi không nói điều này để đe dọa. Chúng tôi nói điều này để những ai đang vạch ra chiến lược cho phe “Valve” có được thông tin chính xác về thực trạng của môi trường thông tin.\n\nMột nguồn thông tin giúp tổng hợp và bổ sung nội dung của chúng ta chính là một câu chuyện. Hai nguồn thông tin thực hiện điều này một cách độc lập và đi đến những kết luận tương tự chính là một xu hướng. Các xu hướng chính là điều mà các cơ quan quản lý chú ý đến.\n\nPhần IVTiền bạc, các lệnh cấm, cả màn trình diễn ồn ào này\n\nVấn đề ở đây là việc Hiệp hội Thể thao và Giải trí (Steam) cấm các trang web cờ bạc và những kẻ lừa đảo không phải là để thực thi pháp luật. Mà là để thu lợi nhuận. Hiệp hội Thể thao và Giải trí (Valve) bỏ túi số tiền đó, rửa tay gác kiếm, rồi lên sân khấu kể cho mọi người nghe một câu chuyện trong sáng về thẻ Pokémon và bóng chày.\n\nTrong những trường hợp các lỗ hổng bảo mật từ phía bộ phận hỗ trợ được ghi nhận — bao gồm cả lời thừa nhận bằng văn bản của Valve vào tháng 2 2023 về việc chịu trách nhiệm đối với các tài khoản có giá trị cao bị xâm phạm thông qua các yêu cầu hỗ trợ, và việc sa thải nhân viên hợp đồng được Dexerto và Escorenews đưa tin sau vụ giao dịch nội gián trị giá $320k (Phần II, Điều04 · Tài liệu chính §14.1) — những thông tin này dựa trên các lời thừa nhận đã được công bố và các bài báo điều tra. Những tin đồn không có căn cứ về việc nhân viên hỗ trợ tham gia các hoạt động cờ bạc bên lề hoặc nhận hoa hồng để dỡ bỏ lệnh cấm không được xác nhận trong hồ sơ công khai và do đó không được đề cập trong bài viết này.\n\nTrong khi đó, Valve đã vô hiệu hóa khả năng theo dõi skin một cách chính xác trên 2017.. Họ thậm chí còn thảo luận về vấn đề này trên chính diễn đàn của mình. Họ gọi đó là “các biện pháp chống cờ bạc” — trong khi hệ sinh thái cờ bạc skin vẫn tiếp tục chuyển hàng tỷ qua hạ tầng của Steam trong nhiều năm sau đó. Thật là một chiến lược xây dựng thương hiệu tuyệt vời.\n\nChúng ta sẽ chứng minh rằng:\n\nCác giao dịch ẩn danh (Skins) còn ẩn danh hơn cả Monero\n\nMột băng đảng ma túy ở Peru được cho là đã sử dụng các skin trong trò chơi Dota 2 để chuyển tiền\n\nSteam về mặt chức năng, đây là một cỗ máy lách các biện pháp trừng phạt trị giá khoảng ~7tỷ USD dưới dạng “thẻ sưu tập” (đúng vậy, họ thực sự đã nói với công tố viên rằng đó là thẻ sưu tập)\n\nChúng tôi có một đoạn video về chuyện các giao diện. Bạn sẽ được xem nó.\n\nChúng ta cũng biết rằng:\n\nCông tác điều hành trên Reddit chịu ảnh hưởng từ Valve\n\nCơ sở hạ tầng dữ liệu của bên thứ ba thuộc mạng lưới phân tán (Steam) (chẳng hạn như steamid.uk) do một cá nhân tư nhân điều hành (msart) cùng với dự án danh sách cấm liên quan (steambans.com kho lưu trữ) được đồng quản lý bởi một điều hành viên đã được xác nhận của cộng đồng Valve (killahinstinct_) — khiến việc kiểm toán độc lập đối với các lệnh cấm trên nền tảng hoàn toàn nằm trong phạm vi ảnh hưởng của Hiệp hội Kế toán Công chứng Hoa Kỳ (Valve) (Xem mục “Card Economy” §08)\n\nNhững gì họ không thể kiểm soát, họ cấm\n\nValve: nếu các bạn cứ tiếp tục giả vờ không biết gì — cũng được thôi. Chúng tôi đã ghi nhận “bến đỗ an toàn” của các bạn rồi. Dù sao thì Google Analytics cũng ẩn danh địa chỉ IP của người dùng rồi. Chúng tôi biết rõ những gì bị xóa. Chỉ là chúng tôi chưa thể chứng minh điều đó với chi phí đủ thấp để các luật sư của các bạn quan tâm thôi. Ít nhất là cho đến nay.\n\nPhần VVấn đề về phần mềm độc hại — vâng, chúng tôi đang đề cập đến điều đó\n\nHãy nói một cách thẳng thắn và rõ ràng về trình tự các sự kiện, bởi vì điều đó sẽ bộc lộ chính xác con người thật của bạn.\n\nChúng tôi SẼ KHÔNG công khai tiết lộ lỗ hổng bảo mật trong trò chơi. Chúng tôi SẼ KHÔNG báo cáo vấn đề này lên Steam. Chương trình này yêu cầu ký thỏa thuận bảo mật (NDA), và việc ký thỏa thuận đó sẽ ngăn cản chúng tôi thông báo cho những người dùng bị ảnh hưởng về những gì đã xảy ra với tài khoản của họ. Mục đích của công việc này là tiết lộ thông tin cho những người đã mất tài khoản cũng như cho các cơ quan quản lý; do đó, thỏa thuận bảo mật là điều không phù hợp với mục đích này.\n\nĐây là những gì thực sự đã xảy ra: Lỗ hổng bảo mật này thực tế đã trở thành một “bí mật công khai” trong giới chuyên môn. Chúng tôi biết chắc chắn rằng các nhà nghiên cứu bảo mật độc lập đã trực tiếp đưa mã khai thác đầy đủ vào mặt bộ phận Hỗ trợ củSteam. Phần đó đã xong. Các bạn đã được cảnh báo chính thức thông qua chính các kênh chính thức của mình.\n\nVà Valve đã làm gì? Hoàn toàn không làm gì cả. Bởi vì đối với Valve, an ninh không đồng nghĩa với lợi nhuận — thực tế, nó hoàn toàn ngược lại. An ninh là một khoản chi phí. Cho đến khi mối đe dọa đạt đến mức nghiêm trọng và gây ra một cuộc khủng hoảng quan hệ công chúng thảm khốc, Valve sẽ không coi đó là vấn đề cấp bách.\n\nVậy chúng ta đang làm gì? Chúng ta đang thông báo cho công chúng biết về sự tồn tại của nó, bởi vì câu nói “Valve biết về một mối đe dọa phần mềm độc hại mang tính hệ thống nhưng lại chủ động chọn cách không làm gì cả” là một thông tin quan trọng đối với các cơ quan quản lý đang đọc bài viết này.\n\nTrò chơi này cực kỳ đồ sộ. Chúng tôi sẽ không nêu tên nó ở đây. Nhưng hãy hiểu điều này:\n\nĐây KHÔNG phải là thứ rác rưởi vớ vẩn kiểu “script-kiddie” trong CS:GO, kiểu như máy chủ yêu cầu bạn “cài đặt trình điều khiển”. Đây là một thảm họa.\n\nĐây là một cơn ác mộng ở mức độ Unturned: lỗ hổng RCE không cần nhấp chuột khi kết nối máy chủ. Bạn tham gia một máy chủ. Bạn không nhấp vào bất cứ thứ gì. Bạn không tải xuống bất cứ thứ gì. Chính kết nối đó là bề mặt tấn công, và máy tính của bạn đã bị xâm nhập hoàn toàn. Hãy nhìn nhận thực tế: việc triển khai một cuộc tấn công RCE và vượt qua các phần mềm diệt virus cục bộ bằng cách lợi dụng các chứng chỉ số đáng tin cậy củValve thậm chí không còn là điều mới mẻ trên Steam nữa. Nó gần như đã trở thành một tính năng tích hợp sẵn trong hệ sinh thái của bạn.\n\nValve đã biết điều này tồn tại. Nhưng họ lại dựa vào kẽ hở pháp lý ưa thích và hèn nhát của mình: vì về mặt kỹ thuật, trò chơi này do một bên thứ ba phát triển, nên Valve rũ bỏ trách nhiệm. Họ phân phối trò chơi, xử lý thanh toán, cung cấp hạ tầng, nhưng khi một lỗ hổng RCE không cần nhấp chuột đe dọa hàng triệu người dùng của họ, lập trường của họ là: \"Không phải trò chơi của chúng tôi, không phải trách nhiệm của chúng tôi.\"\n\nKhi vụ việc này không thể tránh khỏi việc bùng nổ, nhà phát triển bên thứ ba sẽ phải gánh chịu hậu quả, còn Valve sẽ rũ bỏ trách nhiệm và giả vờ là nền tảng có trách nhiệm đã “hỗ trợ” giải quyết vấn đề. Đó là kiểu hèn nhát điển hình của “Valve”. Chúng ta đã quá quen với kịch bản này rồi.\n\nChúng tôi ghi nhận điều này để các cơ quan quản lý, công tố viên và nhà báo hiểu rõ cách thức mà Valve xử lý các phần mềm độc hại đang hoạt động: bằng cách ẩn mình đằng sau các nhà phát triển bên thứ ba, áp dụng các thỏa thuận bảo mật (NDA) để bịt miệng, và khiến người chơi trở thành những mục tiêu dễ bị tấn công.\n\nHết thư ngỏPhần ngôn ngữ trang trọng bắt đầu\nNgôn ngữ trang trọng · dành cho cơ quan chức năng\nTuyên bốVề việc sử dụng và các quyền\n\nPhishDestroy Liên minh Dự án và An ninh mạng\n\nTuyên bố này đi kèm với mọi tài liệu đệ trình và mọi chứng cứ trong bộ hồ sơ chuyển giao này. Tuyên bố này được gửi tới bất kỳ cơ quan chức năng, tòa án, cơ quan quản lý, công tố viên, nhà nghiên cứu, nhà báo hoặc cá nhân bị ảnh hưởng nào nhận được các tài liệu này.\n\n1. Không có điều kiện nào về việc sử dụng\n\n1.1 Tất cả các tài liệu do Liên minh lập ra trong vụ việc này — các bản tường trình sự kiện, phân tích, các tài liệu chứng cứ do Liên minh soạn thảo, các công cụ hỗ trợ và các kết luận — đều được công bố MÀ KHÔNG GIỮ LẠI BẤT KỲ QUYỀN NÀO.\n\n1.2 Bất kỳ ai cũng có thể, mà không cần xin phép và không cần thông báo cho chúng tôi:\n\nsao chép lại, toàn bộ hoặc một phần;\n\nchỉnh sửa, biên tập, viết lại, sắp xếp lại hoặc sửa chữa nó;\n\ndịch nó;\n\ntrích dẫn đoạn đó mà không ghi rõ rằng đó là đoạn trích;\n\nđưa nội dung đó vào các văn bản chính thức, kết luận, quyết định, văn bản tố tụng, báo cáo hoặc tài liệu báo chí;\n\ntrình bày nó như là tác phẩm của chính người nhận hoặc là kết quả nghiên cứu của chính người nhận;\n\nsử dụng nó làm nguyên liệu thô và loại bỏ phần còn lại;\n\nvà chuyển giao nó cho bất kỳ ai khác với các điều kiện tương tự.\n\n1.3 KHÔNG CẦN VÀ CŨNG KHÔNG YÊU CẦU GHI NGUỒN. Không cần phải nêu tên, trích dẫn, ghi công, cảm ơn, tham khảo ý kiến hay thông báo cho Liên minh. Nếu tài liệu từ nguồn tham khảo này hỗ trợ cho một cơ quan chức năng mà Liên minh không bao giờ được đề cập đến, ĐÓ LÀ MỘT KẾT QUẢ HOÀN TOÀN HÀI LÒNG và Liên minh tuyên bố điều này trước để vấn đề này không cần phải được nêu ra.\n\n1.4 Ngược lại, nếu một cơ quan chức năng thấy thuận tiện hơn khi trích dẫn Liên minh làm nguồn tham khảo, thì cơ quan đó hoàn toàn có thể làm như vậy. Quyết định này hoàn toàn thuộc về người nhận thông tin và cả hai cách làm đều không gây ra bất kỳ hậu quả nào.\n\n1.5 Đây là một văn bản MIỄN TRỪ, không phải là đề nghị cấp phép. Văn bản này không yêu cầu sự chấp nhận, không đặt ra bất kỳ nghĩa vụ nào và không thể bị vi phạm. Phần mềm do Liên minh phát hành được cấp phép riêng theo Giấy phép MIT; các nghiên cứu và kết quả được công bố vào phạm vi công cộng ở mức độ tối đa được phép, và trong trường hợp một khu vực pháp lý không cho phép việc miễn trừ, Liên minh cấp một giấy phép không thể hủy ngang, có hiệu lực trên toàn thế giới và miễn phí bản quyền với nội dung tương tự.\n\n2. Tại sao điều này lại quan trọng trên thực tế, chứ không chỉ đơn thuần là một cử chỉ lịch sự\n\n2.1 Một cơ quan có thẩm quyền có thể do dự một cách hợp lý khi dựa vào tài liệu do một bên thứ ba cung cấp, vì lo ngại sẽ bị cho là hành động theo yêu cầu của bên đó hoặc có nguy cơ vướng vào mối quan hệ phức tạp với bên đó.\n\n2.2 TẠI ĐÂY KHÔNG CÓ GÌ ĐỂ GÂY RẮC RỐI. Liên minh không yêu cầu gì, không được hưởng gì, không giữ lại gì và cũng không có bất kỳ kỳ vọng nào. Liên minh không thể sau này khẳng định quyền lợi, đòi công lao, phàn nàn về việc lạm dụng, hay phản đối cách mô tả tài liệu, bởi vì Liên minh không giữ lại bất kỳ cơ sở nào để làm như vậy.\n\n2.3 Do đó, cơ quan nào sử dụng tài liệu này không phải là đại diện cho Liên minh. Cơ quan đó chỉ đang sử dụng thông tin công khai mà tình cờ đã được người khác tổng hợp lại.\n\n3. Mọi thứ đã mở cửa hết rồi\n\n3.1 Các hoạt động của Liên minh được công khai theo mặc định:\n\ncác cuộc điều tra được công bố công khai tại https://phishdestroy.io và có thể đọc được miễn phí;\n\nbộ công cụ này được phát hành dưới dạng mã nguồn mở theo giấy phép MIT tại https://github.com/phishdestroy đã lưu trữ 2026-09-11 ↗;\n\nPhương pháp luận được trình bày ngay trong văn bản chuyển giao, tại Phụ lục A, Mục A.16D, bao gồm mức độ tin cậy và những hạn chế của từng loại nguồn;\n\nLiên minh không nhận bất kỳ khoản đóng góp nào và đã công bố quan điểm này từ trước đến nay tại địa chỉ 2018.\n\n3.2 Những tài liệu duy nhất CHƯA được công bố là những tài liệu không thể công bố một cách hợp pháp hoặc an toàn: dữ liệu cá nhân của nạn nhân và của các bên thứ ba, cũng như thông tin có thể khiến nguồn tin phải đối mặt với sự trả đũa. Những tài liệu này được cung cấp cho các cơ quan chức năng trên cơ sở bảo mật và được liệt kê trong danh mục chứng cứ.\n\n3.3 Liên minh hoan nghênh việc giám sát hành vi của chính mình theo những điều kiện tương tự như khi họ đề nghị giám sát hành vi của bất kỳ bên nào khác, đồng thời đã chủ động cung cấp thông tin về việc xử lý dữ liệu của mình cho các cơ quan chức năng có liên quan, bao gồm cả việc đề nghị hướng dẫn về việc xử lý dữ liệu.\n\n4. Tính toàn vẹn của tập tài liệu chứng cứ\n\n4.1 Các tài liệu kèm theo được cung cấp cùng với hồ sơ nộp hoặc, nếu có ghi chú, sẽ được cung cấp theo yêu cầu qua một kênh bảo mật. Các tài liệu này không được công bố tại một địa chỉ công khai và không nên suy diễn ra địa chỉ nào như vậy: các tài liệu thuộc loại này được cung cấp trực tiếp cho các cơ quan chức năng.\n\n4.2 Mỗi lần giao hàng đều đi kèm với một tệp SHA256SUMS liệt kê mã băm SHA-256 của từng tệp được cung cấp, cùng với chữ ký OpenPGP tách biệt SHA256SUMS.asc.\n\n4.3 Khóa ký được công bố tại https://phishdestroy.io/.well-known/pgp-key.txt và trên trang keys.openpgp.org. Dấu nhận dạng của nó xuất hiện trên tiêu đề của mọi bài viết trong bộ sưu tập này.\n\n4.4 Bất kỳ người nhận nào cũng có thể xác minh bất cứ lúc nào rằng tệp tin mà họ đang sở hữu chính là tệp tin đã được gửi đi, chưa bị sửa đổi:\n\ngpg --verify SHA256SUMS.asc SHA256SUMS\n\nsha256sum -c SHA256SUMS\n\n4.5 Mục đích không phải là để tuân thủ thủ tục. Mà là để trong trường hợp độ chính xác hoặc tính toàn vẹn của bất kỳ chứng cứ nào bị tranh cãi vào một thời điểm sau này, vấn đề đó có thể được giải quyết bằng cách tính toán thay vì tranh luận.\n\n5. Về việc đăng ký — tại sao việc miễn trừ này mang tính thực tiễn chứ không chỉ đơn thuần là một hành động hào phóng\n\n5.1 Các cơ quan chức năng có thể tiếp xúc với các báo cáo điều tra do Liên minh công bố và nhận thấy chúng có giọng điệu thẳng thắn, mang tính đối đầu và đôi khi mang tính châm biếm. Ấn tượng đó là chính xác. Liên minh viết theo cách đó một cách có chủ đích và không xin lỗi về điều đó.\n\n5.2 BÁO CÁO NÀY CŨNG NHẬN THỨC RẰNG ĐÂY KHÔNG PHẢI LÀ GIỌNG ĐIỆU PHÙ HỢP CHO MỘT THỦ TỤC QUẢN LÝ HOẶC TƯ PHÁP. Một vấn đề nghiêm trọng không nên được trình bày bằng giọng điệu của một chiến dịch. Các kết luận được trình bày trước cơ quan có thẩm quyền cần được nêu rõ ràng, thừa nhận những hạn chế của chúng, và không nên bắt người đọc phải bỏ qua giọng điệu để đi vào nội dung chính.\n\n5.3 ĐÓ CHÍNH LÀ LÝ DO TẠI SAO LIÊN MINH TỪ BỎ QUYỀN TÁC GIẢ. Việc từ bỏ quyền tác giả tại mục 1 là cơ chế giúp tách nội dung ra khỏi văn bản đăng ký: cơ quan có thẩm quyền có thể lấy những phần hữu ích, trình bày lại theo cách diễn đạt của riêng mình, và loại bỏ mọi từ ngữ mang phong cách của Liên minh cùng với tên gọi của Liên minh. Việc làm này không gây ra bất kỳ tổn thất nào, và Liên minh cũng mong muốn điều đó.\n\n5.4 LIÊN MINH CŨNG YÊU CẦU KHÔNG ĐƯỢC NHẦM LẪN GIỮA BẢNG TỔNG HỢP VỚI PHƯƠNG PHÁP. Giọng điệu trong bản báo cáo có phần gay gắt; tuy nhiên, thực tiễn đằng sau đó không hề cẩu thả. Trong suốt bản báo cáo này, suy luận được tách biệt khỏi quan sát, lời khai được xác định rõ là lời khai, các nguồn thông tin được đánh giá và những điểm yếu của chúng được nêu rõ, các số liệu được trình bày kèm theo những hạn chế của chúng, và những điểm mà Liên minh không thể chứng minh được được đặt ra dưới dạng câu hỏi dành cho cơ quan có thẩm quyền thay vì là những khẳng định. Khi bằng chứng đi ngược lại quan điểm của chính Liên minh, Liên minh đã thừa nhận điều đó — xem Phụ lục A, đoạn 7, và phần B.0 của bản trình bày song song.\n\n5.5 LIÊN MINH GIẢI THÍCH MỐI LIÊN HỆ GIỮA PHONG CÁCH HOẠT ĐỘNG VÀ TÀI CHÍNH CỦA MÌNH, BỞI VÌ HAI YẾU TỐ NÀY KHÔNG THỂ TÁCH RỜI. Liên minh không nhận tiền từ bất kỳ ai — không nhận quyên góp, không nhận tiền thưởng, không có khách hàng, không có nhà tài trợ. Chính sự từ chối đó đã tạo điều kiện cho sự thẳng thắn: một tổ chức có nguồn thu nhập cần bảo vệ sẽ phải điều chỉnh những gì mình nói về các bên mà họ phụ thuộc vào. Không có gì để bảo vệ, Liên minh cũng không có gì để phải điều chỉnh.\n\nĐó cũng chính là lý do khiến Liên minh vẫn tiếp tục tồn tại. Không có động lực nào khác. Công việc được thực hiện chỉ vì nó được thực hiện; nó sẽ dừng lại khi những người thực hiện nó ngừng lại.\n\n5.6 Cơ quan chức năng không cần phải chấp nhận bất kỳ điều nào trong số này. Điều này được nêu ra nhằm tránh việc giọng điệu trong các hoạt động công khai của Liên minh bị hiểu nhầm là thước đo mức độ cẩn trọng mà Liên minh dành cho tài liệu hiện đang được xem xét.\n\n6. Những gì Liên minh đang cung cấp, theo lời của chính họ\n\nThông tin, nghiên cứu và quan sát.\n\nKhông có nội dung nào được khẳng định như một kết luận mà Liên minh không có thẩm quyền đưa ra. Khi có nội dung nào đó được suy luận ra, văn bản chuyển giao sẽ nêu rõ điều đó. Khi có nội dung nào đó dựa trên lời khai, văn bản chuyển giao sẽ nêu rõ lời khai của ai và có những hạn chế gì. Khi Liên minh không thể trả lời một câu hỏi, văn bản cũng nêu rõ điều đó và chỉ rõ ai có thể trả lời.\n\nLiên minh không yêu cầu bất kỳ biện pháp khắc phục, khoản bồi thường, sự thừa nhận hay kết quả nào cho chính mình hay cho bất kỳ cá nhân nào. Liên minh chỉ yêu cầu các câu hỏi được nêu trong văn bản chuyển giao phải được đưa ra cho Tập đoànValve bởi một cơ quan có thẩm quyền buộc công ty này phải trả lời.\n\nLời kếtGửi đến bất kỳ ai đang tiếp tục công việc này\n\nChúng tôi xin gửi lời cảm ơn đến bất kỳ ai giúp chuyển tài liệu này đến đúng nơi cần đến. Chắc hẳn đây sẽ không phải là một hành trình ngắn ngủi. Quỹ “Valve” có nguồn lực tài chính dồi dào, còn công ty luật Taylor Wessing tính phí theo giờ — sự kết hợp này được thiết kế đặc biệt nhằm khiến những người như bạn phải bỏ cuộc trước khi chạm đến đích.\n\nChúng tôi biết mình đang làm gì. Chúng tôi biết mình đang viết về ai. Chính “Valve” đã tạo nên chúng tôi — làm sao chúng tôi lại không thể hiểu họ được chứ?\n\nPhishDestroy không có mâu thuẫn nào với Valve. Chúng tôi đã chặn đứng đường dây lừa đảo duy nhất có quy mô như vậy mà chúng tôi từng phát hiện — chúng tôi không chủ động tìm cách gây hấn với Valve. Chỉ là mọi manh mối đều dẫn về phía họ mà thôi. Không phải mâu thuẫn. Chỉ là cấu trúc mạng thôi.\n\nValve Không thể giải quyết vấn đề “PhishDestroy” vì chẳng có gì để giải quyết cả. Chúng ta không có mối quan hệ nào cả. Dữ liệu về các kế hoạch làm giàu và lợi nhuận khổng lồ của họ phần lớn đã được công khai — bạn chỉ cần dành đủ thời gian là có thể thấy được thôi. Hãy coi đó như một cuốn bách khoa toàn thư về thành công: “Cách không tuân thủ các lệnh trừng phạt để các hacker Nga không thể sao chép lậu các trò chơi miễn phí của chúng ta (còn những trò chơi trả phí thì họ cũng chẳng thèm sao chép lậu đâu)”. Bạn đã hiểu ý rồi đấy.\n\nChúng ta không cần quyền tác giả.\n\nChúng tôi không cần ghi nguồn.\n\nChúng ta không cần phải thắng.\n\nChúng ta cần một người có thẩm quyền thực sự để đặt ra cho Ủy ban Thương mại Liên bang (Valve) những câu hỏi đã được nêu trong văn bản chuyển giao này, đồng thời có quyền yêu cầu họ phải trả lời.\n\nThế thôi. Đó là tất cả những gì tôi yêu cầu.\n\nCác trường hợp sẽ được lưu trữ tại:\n\nhttps://steamdestroy.eth/\n\nhttps://steamdestroy.eth.limo (hiện đang bị hỏng — sẽ sửa khi cần thiết)\n\nChúng tôi sẽ có mặt tại:\n\nhttps://phishdestroy.eth.limo/ đã lưu trữ 2026-06-27 ↗\n\nhttps://phishdestroy.eth/\n\nHai vật phẩm có chữ ký · bản quyền và văn bản đã xuất bản\nGiấy miễn trừ trách nhiệm đã kýNội dung đã được ký kết là gì, và phạm vi áp dụng của nó là gì\n\nVăn bản cấp quyền và văn bản nghiên cứu là các đối tượng JSON được ký riêng biệt như dưới đây. Mỗi chữ ký OpenPGP độc lập xác thực chính xác các byte của tệp JSON có tên được ghi bên cạnh nó. Tuyên bố quyền cấp các quyền truy cập; bản chụp văn bản xác định và chứa nội dung đang được xuất bản.\n\n1. Tuyên bố về quyền — license-rights.json\n\nĐối tượng đã ký: toàn bộ license-rights.json Tệp này chứa văn bản cấp quyền công khai có ngày 28 tháng 9 năm 2026.. Văn bản này cho phép sao chép, xuất bản, chỉnh sửa, dịch, kết hợp và thương mại hóa các tài liệu trong hồ sơ mà không cần ghi nguồn, thông báo hoặc xin phép. Chữ ký này xác thực tuyên bố về quyền; nó không xác thực nội dung của từng trang web hoặc tệp PDF.\n\nBản thỏa thuận ban đầu đã được ký kết được giữ nguyên vẹn. Quyền cấp phép hiện có trong đó không thể bị thu hồi hoặc hạn chế bằng cách thay đổi trang web, đăng tải một tệp tin khác hoặc ngừng hoạt động trang web. Các tài liệu của bên thứ ba vẫn giữ nguyên các quyền của riêng mình.\n\nTuyên bố về quyền JSON ↗ · Chữ ký của license-rights.json ↗ · SHA-256, thuộc license-rights.json ↗\n\ngpg --verify license-rights.json.asc license-rights.json\nsha256sum -c license-rights.json.sha256\n2. Văn bản đã xuất bản — dossier-text.json\n\nĐối tượng đã ký: toàn bộ dossier-text.json tệp. Tệp này chứa nội dung văn bản thực tế có thể đọc được của các trang đã xuất trong documents[].content.text, bao gồm tiêu đề, ngôn ngữ, URL nguồn, mã băm HTML nguồn, các tiêu đề và các tham chiếu của từng trang. Các documents Danh sách này chính xác là danh mục được bao gồm trong bản chụp này; các phiên bản ngôn ngữ được liệt kê riêng biệt. Đây là một ấn phẩm văn bản, không chỉ đơn thuần là một danh sách các mã băm.\n\nMỗi mục đều xác định tệp PDF trang nhẹ của mình thông qua tên tệp và giá trị SHA-256 documents[].pdf. Tệp JSON này cũng xác định tuyên bố quyền gốc thông qua URL và mã SHA-256,, nhờ đó văn bản đã xuất bản, tệp PDF của nó và tuyên bố quyền liên quan có thể được đối chiếu một cách chính xác mà không cần phỏng đoán. Các cơ sở dữ liệu bên ngoài được liên kết, hình ảnh gốc và các trang không có trong danh mục không được nhúng trong bản chụp nhanh văn bản này.\n\nToàn văn JSON đã ký ↗ · Chữ ký của dossier-text.json ↗ · SHA-256, thuộc dossier-text.json ↗\n\ngpg --verify dossier-text.json.asc dossier-text.json\nsha256sum -c dossier-text.json.sha256\n\nTrên trang chủ của hồ sơ, các nút PDF và JSON dùng để xuất gói nghiên cứu. Trên các trang con, các nút này dùng để xuất trang đó bằng ngôn ngữ đã được xuất bản. Mỗi tệp JSON của trang cũng có chữ ký độc lập và tệp SHA-256, được đặt tên rõ ràng trong integrity đối tượng. Để xác minh tệp PDF liên quan, hãy tính toán giá trị SHA-256 của tệp đó và so sánh với pdf.sha256 giá trị trong tệp JSON đã được xác minh. Tệp PDF được liên kết với giá trị băm đó; tệp này không chứa chữ ký số theo định dạng PDF.\n\n3. Bộ tài liệu nghiên cứu có thể in — steam-dossier-{language}.content.json\n\nĐối tượng đã ký: tệp JSON đầy đủ dành riêng cho ngôn ngữ đó, bao gồm cả nội dung chương được gói sẵn trong documents[].content.text, phạm vi trang của các chương, các ngôn ngữ nguồn, danh sách các nguồn bị loại trừ và bản tóm tắt PDF chính xác trong pdf.sha256. Năm kho tài liệu bổ sung vẫn được liên kết trực tuyến và không được gộp lại thành một gói. Nội dung nghiên cứu do tác giả soạn thảo được giữ nguyên; các danh mục hình ảnh được thay thế bằng các liên kết đến nguồn.\n\nTiếng Anh JSON ↗ · Chữ ký riêng của \"OpenPGP\" ↗ · Bản tóm tắt SHA-256 ↗\n\nTiếng Đức JSON ↗ · Chữ ký riêng của \"OpenPGP\" ↗ · Bản tóm tắt SHA-256 ↗\n\ngpg --verify steam-dossier-en.content.json.asc steam-dossier-en.content.json\nsha256sum -c steam-dossier-en.content.json.sha256\n\nKhóa xác minh công khai ↗\n\nDấu vân tay chữ ký: 129F C7F3 9C40 C69D 2EF3 C329 BFCF 9E8D D295 EE01\n\ngpg --import pgp-key.txt\ngpg --fingerprint 129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01\n\nHãy kiểm tra xem dấu vân tay được hiển thị có khớp với dấu vân tay ở trên hay không, sau đó đối chiếu chữ ký với tên tệp JSON chính xác. Việc chỉnh sửa tệp JSON đã được ký sẽ thay đổi đối tượng đã ký và làm mất hiệu lực chữ ký ban đầu của nó. Một chữ ký hợp lệ giúp xác thực các byte đã được công bố; nó không phải là sự xác minh độc lập đối với các kết quả nghiên cứu.\n\nPhishDestroy — điều tra công khai — mọi quyền lợi đều được nhượng lại cho nhân loại\n\nQuyền truy cập vào khu vực thuộc phạm vi quản lý của OFAC: bị cấm",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Giấy phép và Tuyên bố miễn trừ trách nhiệm pháp lý — Cam kết đưa vào phạm vi công cộng"
          },
          {
            "level": 2,
            "id": null,
            "text": "Phần IGiấy phép — phần pháp lý thực tế, nhưng mang tính con người"
          },
          {
            "level": 3,
            "id": null,
            "text": "Một quy tắc thực tế (vâng, chỉ một thôi)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Phần IIĐiều này là gì và tại sao nó lại tồn tại"
          },
          {
            "level": 2,
            "id": null,
            "text": "Phần IIIThư ngỏ gửi Valve — Thật đấy, hãy đọc bài này đi"
          },
          {
            "level": 3,
            "id": null,
            "text": "Thỏa thuận (đề nghị công khai, không cần luật sư)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Phần III-BCác nguồn lực của phe đồng minh — một lưu ý dành riêng cho Steam"
          },
          {
            "level": 2,
            "id": null,
            "text": "Phần IVTiền bạc, các lệnh cấm, cả màn trình diễn ồn ào này"
          },
          {
            "level": 2,
            "id": null,
            "text": "Phần VVấn đề về phần mềm độc hại — vâng, chúng tôi đang đề cập đến điều đó"
          },
          {
            "level": 2,
            "id": null,
            "text": "Tuyên bốVề việc sử dụng và các quyền"
          },
          {
            "level": 3,
            "id": null,
            "text": "1. Không có điều kiện nào về việc sử dụng"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. Tại sao điều này lại quan trọng trên thực tế, chứ không chỉ đơn thuần là một cử chỉ lịch sự"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. Mọi thứ đã mở cửa hết rồi"
          },
          {
            "level": 3,
            "id": null,
            "text": "4. Tính toàn vẹn của tập tài liệu chứng cứ"
          },
          {
            "level": 3,
            "id": null,
            "text": "5. Về việc đăng ký — tại sao việc miễn trừ này mang tính thực tiễn chứ không chỉ đơn thuần là một hành động hào phóng"
          },
          {
            "level": 3,
            "id": null,
            "text": "6. Những gì Liên minh đang cung cấp, theo lời của chính họ"
          },
          {
            "level": 2,
            "id": null,
            "text": "Lời kếtGửi đến bất kỳ ai đang tiếp tục công việc này"
          },
          {
            "level": 2,
            "id": null,
            "text": "Giấy miễn trừ trách nhiệm đã kýNội dung đã được ký kết là gì, và phạm vi áp dụng của nó là gì"
          },
          {
            "level": 3,
            "id": null,
            "text": "1. Tuyên bố về quyền — license-rights.json"
          },
          {
            "level": 3,
            "id": null,
            "text": "2. Văn bản đã xuất bản — dossier-text.json"
          },
          {
            "level": 3,
            "id": null,
            "text": "3. Bộ tài liệu nghiên cứu có thể in — steam-dossier-{language}.content.json"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/vi/#briefing-heading",
          "https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "http://web.archive.org/web/20260821155801/https://phishdestroy.medium.com/my-dog-vs-elite-gdpr-lawyers-the-valve-data-breach-nobody-is-talking-about-f6f7683d813d",
          "https://phishdestroy.io/steam_dossier/vi/investigation_part2.html#outsourcing-case",
          "https://phishdestroy.io/steam_dossier/vi/#theft-ledger",
          "https://steamid.uk/",
          "http://web.archive.org/web/20251203104928/https://steamcommunity.com/groups/steambans",
          "https://steamcommunity.com/id/killahinstinct_",
          "https://phishdestroy.io/steam_dossier/vi/card_economy.html#governance",
          "https://phishdestroy.io/steam_dossier/vi/license_disclaimer.html",
          "https://github.com/phishdestroy",
          "http://web.archive.org/web/20260911040557/https://github.com/PhishDestroy",
          "https://phishdestroy.io/.well-known/pgp-key.txt",
          "https://steamdestroy.eth/",
          "https://steamdestroy.eth.limo/",
          "https://phishdestroy.eth.limo/",
          "http://web.archive.org/web/20260627040219/https://phishdestroy.eth.limo/",
          "https://phishdestroy.eth/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json.asc",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json.sha256",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/dossier-text.json.sha256?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-en.content.json.sha256?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json.asc?v=print-20260928-v3",
          "https://phishdestroy.io/steam_dossier/exports/steam-dossier-de.content.json.sha256?v=print-20260928-v3"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/vi/license_disclaimer.content.json",
      "export_json_sha256": "0913e3cc6c40d9b91bb8fa2a3745a93902630e5e086fc1eff8c6eb26dea2f587"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "vi/market_economics.html",
      "language": "vi",
      "title": "Một hệ thống hạ tầng, hai thị trường — Hồ sơ về Chương trình “Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/vi/market_economics",
      "source_html_sha256": "8b3574055a4bc8b36a13dfebfd850ca14ff2415c08114ce2bf2d18a095ec7810",
      "exported_at": "2026-09-29T00:23:02.791Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "market_economics.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/vi/market_economics.pdf?v=print-20260929-v5",
        "sha256": "08ca15563c818bb3a1e0858b2862bbde27f92718be1109380c0ad133051f349a",
        "bytes": 104429,
        "pages": 8
      },
      "integrity": {
        "signed_object": "market_economics.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "market_economics.content.json.asc",
        "digest_file": "market_economics.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify market_economics.content.json.asc market_economics.content.json",
          "sha256sum -c market_economics.content.json.sha256"
        ]
      },
      "content": {
        "text": "Phụ lục VII · Cấu trúc thị trường · 20 Tháng 9 năm 2026\nKinh tế thị trường — Hai nền kinh tế và mức trần niêm yết\n\nHạ tầng của họ. Hai nền kinh tế.\n\nPHẦN NÀY CHỨNG MINH ĐIỀU GÌ\n\nChương này phân tích sự phân hóa hệ thống trên thị trường do giới hạn niêm yết $1,800 của Valve và các số dư ví không thể rút ra gây ra. Thông qua việc khảo sát 38 các sàn giao dịch skin bên ngoài đang hoạt động với tổng giá trị niêm yết khoảng $1.28 tỷ, cuộc điều tra chứng minh rằng các giao dịch cấp cao bắt buộc phải chuyển sang các nền tảng \"bóng tối\" bên ngoài trong khi vẫn dựa vào cơ sở hạ tầng giao dịch và xác thực cơ bản của Steam. Mặc dù việc sử dụng thương mại bị cấm chính thức trong Thỏa thuận Người đăng ký, Valve vẫn tạo điều kiện và kiếm tiền từ nền kinh tế hai tầng này mà không có bất kỳ hồ sơ thực thi nào được công bố.\n\n← Quay lại Bản tóm tắt dành cho lãnh đạo\n\n38 các sàn giao dịch CS2 của bên thứ ba đang hoạt động, cùng với sàn giao dịch riêng củSteam. Mọi skin được niêm yết trên bất kỳ nền tảng nào trong số đó đều phải đi qua kho hàng của Steam và giao dịch tại API. Các quy định của Valve nghiêm cấm việc khai thác thương mại cơ sở hạ tầng đó. Giá trị niêm yết của bên thứ ba ước tính khoảng $1.28 tỷ vẫn tồn tại, trong khi chưa tìm thấy bất kỳ hồ sơ công khai nào về việc thực thi quy định này.\n\n$1.28B\nGiá trị niêm yết từ bên thứ ba · Các nền tảng 38\n53.2M\nCác ưu đãi đang hiển thị · Thị trường của bên thứ ba thuộc 38\n70.1K\nSteam các mục được liệt kê trong bản chụp nhanh\n41×\nGiá trị niêm yết của bên thứ ba so với $31M của Steam\nKết luận chính\nMột hệ thống hạ tầng. Hai nền kinh tế.\n\nSteam kiểm soát mặt hàng, kho hàng và hoạt động giao dịch. Mọi skin được bán trên bất kỳ nền tảng nào dưới đây đều phải thông qua hệ thống giao dịch của Steam API — một sự phụ thuộc về mặt cấu trúc có thể quan sát được một cách trực tiếp. Chợ Cộng đồng của Valve thu phí từ doanh số bán hàng; việc khoản phí này có được dùng để tài trợ cho, hay có liên quan đến, hệ sinh thái của bên thứ ba hay không thì chưa được xác định rõ ở đây.\n\nTại sao điều này lại quan trọng đối với cuộc điều tra\n1\nThỏa thuận đăng ký dịch vụ “Steam” của Valve cấm khai thác vì mục đích thương mại của cơ sở hạ tầng Steam mà không có sự cho phép rõ ràng. Không tìm thấy sự cho phép nào như vậy trong hồ sơ công khai đối với các nền tảng dưới đây.\n2\nSteam quản lý thông tin xác thực (OpenID), tình trạng tồn kho và việc thực hiện giao dịch đối với giá trị niêm yết của các bên thứ ba ước tính khoảng $1.28B. Không có giao dịch chuyển nhượng tài sản nào diễn ra nếu không có cơ sở hạ tầng củValve.\n3\nChợ trực tuyến của Steam có $31M được niêm yết — khoảng 1/41 giá trị niêm yết của bên thứ ba. Mức trần giá $1,800 có nghĩa là những người bán có giá cao hơn mức này phải chuyển sang giao dịch ngoài nền tảng để bán theo mức giá thị trường thực tế.\n4\n248 Các danh mục sản phẩm CS2, mỗi loại đều được hai hoặc nhiều sàn giao dịch độc lập định giá cao hơn mức trần, không thể được bán với mức giá thị trường thực tế trên Steam — và không có loại nào trong số đó được niêm yết trên sàn này cả. Mức trần $1,800 tạo ra nhu cầu mà các nhà điều hành bên thứ ba đáp ứng.\nSteam Chợ cộng đồng: $31MGiá trị niêm yết do bên thứ ba công bố: $1,276triệu\n$1,276M · giá trị được bên thứ ba niêm yết — tất cả đều phụ thuộc vào giao dịch API & OpenID của Steam\nSteam · $31M\n\nNguồn: Danh mục thời gian thực của PriceEmpire, 20 ngày 2026. Giá niêm yết = tổng giá trị của các thẻ giá niêm yết đã được làm tròn trong ảnh chụp màn hình đã lưu, không bao gồm Steam. Không phải là khối lượng bán hàng.\n\n38 các thị trường bên thứ ba sôi động · Tất cả đều phụ thuộc vào cơ sở hạ tầng củSteam\nĐăng ký nền tảng\n\nCác nền tảng dưới đây chuyển hướng quá trình đăng nhập của người dùng qua OpenID của Steam và các giao dịch qua Web API của Steam. Mỗi nền tảng được quan sát thấy openid.realm trải qua quy trình đăng nhập của Steam; hệ thống đăng ký ghi lại các lộ trình xác thực được quan sát thấy thay vì khẳng định rằng bất kỳ người vận hành nào cũng không có quyền truy cập vào Valve.\n\n#\tNền tảng\tGiá trị niêm yết\tCác ưu đãi đang áp dụng\tCác mặt hàng\tTỷ lệ\n1\tUUSkins\t$133.8M\t3.4M\t30.9K\t\n\n2\tYouPin898\t$127.5M\t5.9M\t29.2K\t\n\n3\tBuff.163\t$104M\t3.5M\t35K\t\n\n4\tMoon.Market\t$100.3M\t2.9M\t20.9K\t\n\n5\tWhite.Market\t$89.6M\t3M\t20.6K\t\n\n6\tBuff.Market\t$86.7M\t1.3M\t33.4K\t\n\n7\tEcosteam\t$82.1M\t3.3M\t30.1K\t\n\n8\tCSFloat\t$67.8M\t2.4M\t27.8K\t\n\n9\tSkin.Land\t$67.4M\t2.2M\t34.6K\t\n\n10\tLIS-SKINS\t$67.4M\t2.2M\t34.6K\t\n\n11\tC5Game\t$54.6M\t4.6M\t29.6K\t\n\n12\tHaloSkins\t$46.6M\t4.4M\t29.3K\t\n\n13\tAvan.Market\t$43.3M\t809.5K\t22.2K\t\n\n14\tWaxpeer\t$40.1M\t1M\t27.3K\t\n\n15\tSteam (official)\t$31M\t32.2M\t70.1K\t\n\n16\tCS.MONEY\t$29M\t748.9K\t28K\t\n\n17\tMarket.CSGO\t$26.3M\t1.3M\t27.6K\t\n\n18\tCS.MONEY Bot\t$25.7M\t614K\t23.8K\t\n\n19\tSkinport\t$16.3M\t3.8M\t31.1K\t\n\n20\tSkinFlow\t$14.1M\t481.8K\t23.6K\t\n\n21\tDMarket\t$12.6M\t948.2K\t35.6K\t\n\n22\tSkins.com\t$11.5M\t83.2K\t15.8K\t\n\n23\tSkin.place\t$6.9M\t380.8K\t11.4K\t\n\n24\tSkinsMonkey\t$6M\t109.4K\t11.6K\t\n\n25\tSkinBaron\t$5M\t2.1M\t21.5K\t\n\n26\tRustTM\t$3M\t33.1K\t4.9K\t\n\n27\tPirateSwap\t$2M\t859.3K\t10.5K\t\n\n28\tMannco.Store\t$1.2M\t223.7K\t11K\t\n\n29\tSkinSwap\t$1.1M\t11.4K\t4K\t\n\n30\tTradeIt\t$967.1K\t29.1K\t11.7K\t\n\n31\tLootFarm\t$896.1K\t162.5K\t28.6K\t\n\n32\tRustskins\t$714.8K\t312.5K\t6.1K\t\n\n33\tBalticSkins\t$599.2K\t28.2K\t4.5K\t\n\n34\tExeSkins\t$442.9K\t2.6K\t1.4K\t\n\n35\tRapidSkins\t$230.9K\t11.6K\t2.3K\t\n\n36\tCS.Trade\t$203K\t19K\t16.7K\t\n\n37\tKrakatoa\t$11.1K\t115\t53\t\n\n38\tShadowPay\t—\t—\t—\t—\n39\t49skins\t—\t—\t—\t—\nMức giá trần $1,800 của Steam · Tổng quan về năm sàn giao dịch · 23 tháng 9 năm 2026\nChênh lệch giá là có thể đo lường được.\n\nSteam giới hạn mức giá niêm yết trên Community Market ở mức khoảng $1,800 (kết quả này được tính lại thành $2,000, $2,070, $2,300 và $2,500 trong cs2sh-atlas.json và duy trì ở mọi ngưỡng). Các mặt hàng có giá cao hơn mức giá đó không thể được bán theo giá thị trường trên nền tảng thương mại điện tử của Valve — nhưng chúng vẫn phụ thuộc vào hệ thống quản lý hàng tồn kho và chuyển hàng của Steam bất kể được bán ở đâu. Việc phân loại toàn bộ danh mục sản phẩm theo giá cho thấy ranh giới nằm ở đâu: thị trường của Valve cung cấp 95.3% các danh mục sản phẩm có giá thấp hơn mức trần và 1.9% so với những cái ở phía trên nó.\n\nNăm sàn giao dịch: các mặt hàng có giá cao hơn mức trần “Steam”\n248\n\nCác danh mục sản phẩm có mức giá chào bán thấp nhất đạt mức $1,800 trên hai hoặc nhiều sàn thương mại điện tử hoạt động độc lập, sở hữu các bản sao được liệt kê trên trang 18,394 có giá trị ít nhất là $78.6M. Trong số đó, 100.0% — từng cái một — đều không có bất kỳ thông tin nào trên trang Steam.\n\nCác bằng chứng đầy đủ: danh sách → · Bản đồ thang giá →\n\nPhân phối giá vượt mức trần\n$1,800–$5,000\n174\n$5,000–$10,000\n49\n$10,000–$25,000\n21\n$25,000–$50,000\n2\n$50,000+\n2\nCác sản phẩm hàng đầu — mức giá chào bán đã được xác minh thấp nhất trên năm sàn thương mại điện tử\n1Hình dán | Titan (Holo) | Mã sản phẩm: '14'$66,285\n2Hình dán | iBUYPOWER (Holo) | Mã sản phẩm: '14'$64,795\n3Hình dán | Reason Gaming (Holo) | Mã sản phẩm: '14'$42,899\n4★ Găng tay thể thao | Mê cung hàng rào (FN)$26,812\n5Hình dán | Team Dignitas (Holo) | Kat. '14'$23,667\n6EMS Kat. '14: Những huyền thoại'$22,879\n7★ Găng tay thể thao | Hộp Pandora (FN)$21,643\n8EMS Kat. '14' - Các đội tham dự$21,010\n9Hình dán | Vox Eminor (Holo) | Mã sản phẩm: '14$18,619\n10★ Dao gấp StatTrak™ Navaja | Thép xanh (FN)$18,064\n\nGiá chào bán không phải là giá bán. Ảnh chụp màn hình từ cs2.sh (có giấy phép), 23 tháng 9 năm 2026. Mỗi hàng đều được ít nhất hai sàn giao dịch độc lập chào bán với mức giá cao hơn mức trần; các mức giá chào bán đơn lẻ và mức giá chào mua cao hơn ba lần so với mức giá chào bán rẻ nhất của mặt hàng đó sẽ bị loại trừ. Cách thức chấm điểm hoạt động như thế nào →\n\nValve tính phí như thế nào · Ảnh chụp màn hình trang web cs2.sh đã được cấp phép · 23 tháng 9 năm 2026\nMức phí được quảng cáo là 15%.. Hầu hết các tin đăng đều trả cao hơn mức này.\n\nValve trừ một khoản phí 5% Steam và một khoản phí nhà xuất bản CS2 10% từ số tiền thu được của người bán — đó là khoản phí quen thuộc 15%. Cả hai khoản phí này đều có Tối thiểu $0.01, do đó không có giao dịch nào có thể có mức phí thấp hơn hai xu. Đối với các mặt hàng giá rẻ, khối lượng lớn – vốn chiếm phần lớn thị trường – mức sàn này mới là yếu tố hạn chế quyết định, chứ không phải tỷ lệ phần trăm. Chúng tôi đã giải quyết vấn đề tính toán phí cho từng mặt hàng 29,635 các loại mặt hàng có mức giá yêu cầu theo thị trường (Steam) đang được niêm yết.\n\n77.7%\ncác danh sách “Steam” đang hoạt động thuộc các loại mặt hàng có mức phí cao hơn so với 15%\n84.8%\ncủa mặt hàng các loại hãy trả mức lương gần bằng mức lương danh nghĩa\n4,517\ncác loại mặt hàng bị tính phí cao hơn mức phí đã công bố\n$0.02\nphí tối thiểu cho mọi giao dịch bán hàng, bất kể giá cả là bao nhiêu\nHai con số này chỉ theo hai hướng ngược nhau, và cả hai đều đúng\n1\nĐã đếm theo loại mặt hàng, Phí dịch vụ của Valve về cơ bản đúng như đã quảng cáo: 84.8% các loại giá được niêm yết trên trang 29,635 được tính theo mức giá tại hoặc gần với 15%.\n2\nĐã đếm theo danh sách thực tế, hình ảnh bị đảo ngược: 18,682,244 trích từ cuốn “24,038,911” Danh sách trực tiếp được hiển thị theo các loại mặt hàng có mức phí cao hơn so với 15%.\n3\nCả hai đều đúng vì các kiểu bị tính phí quá mức chính là giá rẻ, số lượng lớn những loại này. 1,109 Các loại mặt hàng này có mức phí cao hơn gấp đôi mức giá niêm yết, và chỉ riêng những loại bất động sản này đã chiếm phần lớn các tin rao bán trực tuyến trên 14,083,486.\n4\nĐây là phép tính, không phải cáo buộc. Mức tối thiểu đã được nêu rõ trong chính tài liệu về phí của Quỹ Đầu tưValve. Điều chưa được công bố là thực tế thì nó áp dụng cho bao nhiêu phần trăm thị trường — đó chính là điều mà các số liệu trên phản ánh.\nPhí được tính, tính theo tỷ lệ phần trăm so với mức phí cơ bản (15%)\n200%+\n14,083,486\n100-200%\n1,028,438\n50-100%\n700,804\n30-50%\n317,031\n20-30%\n2,258,254\n17.6-20%\n294,231\n\nĐộ dài dải là số lượng danh sách đang được rao bán trong mỗi dải. Một dải có ký hiệu “200%+” có nghĩa là mức phí thu được cao hơn gấp đôi số tiền 15% từ số tiền thu được của người bán.\n\nMột ví dụ minh họa\n67%\n\nKhi đăng tin rao bán, người mua phải trả $0.03 bởi vì, người bán sẽ nhận được $0.01 và trang web Valve cung cấp $0.02 — hai mức tối thiểu 1 cent. Tính theo tỷ lệ phần trăm so với số tiền người mua đã trả thì đó là 67%; tính theo tỷ lệ phần trăm so với số tiền thu được của người bán thì đó là 200%.\n\nBộ dữ liệu đầy đủ: cs2sh-steam-fee-census.json →\n\nCùng một vật, ở trong vườn và bên ngoài vườn\nMua hàng trên Steam thường đắt hơn. Hầu như luôn luôn như vậy.\n\nĐối với mỗi mặt hàng được niêm yết giá cả trên Steam lẫn ít nhất một sàn thương mại điện tử bên thứ ba, chúng tôi đã so sánh mức giá bán rẻ nhất trên Steam với mức giá bán rẻ nhất trên các nền tảng khác. Trên toàn bộ 28,700 các mặt hàng, Steam là nơi có giá cao hơn 86.4% trong phần lớn thời gian, với giá trị trung vị là +35.7%.\n\nMức phí bảo hiểm trung vị của Chương trình Bảo hiểm Sức khỏe Toàn dân (Steam), theo nhóm giá\ndưới $0.50\n+48.3%\n$0.50-2\n+36.5%\n$2-10\n+29.6%\n$10-50\n+28.6%\n$50-250\n+36.3%\n$250-1k\n+51.1%\nhơn $1,000\n+67.9%\n\nĐường cong có hình chữ U. Giá rẻ nhất là khi mua trên trang Steam trong $10–$50 dải và người thân yêu nhất ở hai đầu.\n\nTại sao phân khúc cao cấp lại quan trọng\n+67.9%\n\nPhía trên $1,000, mức giá trung vị Steam của các bất động sản được rao bán 67.9% cao hơn so với mức giá rẻ nhất của các bất động sản ngoài khu vực đó — và chỉ 1,040 có những bất động sản như vậy được đăng tải trên Steam.\n\nKhi vượt quá khoảng $1,800, việc so sánh sẽ không còn khả thi nữa, bởi vì quy định của Valve cấm hoàn toàn việc niêm yết. Phạm vi bảo hiểm của Steam đối với các mặt hàng có giá trị vượt quá mức trần của chính họ là 1.9%. Xem toàn bộ bảng xếp hạng →\n\nBộ dữ liệu đầy đủ: cs2sh-walled-garden-premium.json →\n\nMức chênh lệch giá (premium) bản thân nó không phải là một kết luận: Steam cung cấp dịch vụ giao dịch tức thì và không có rủi ro đối tác, và người mua có thể sẵn sàng trả tiền cho điều đó. Điều có thể đo lường được là mức độ chênh lệch và thực tế rằng số tiền được chuyển qua đó không thể rút lại được — đây chính là nội dung của phần tiếp theo.\n\nTiền vào, không có tiền ra\n128.1 triệu đô la đã cam kết cho các đơn đặt hàng không thể hủy bỏ.\n\nLệnh mua “Steam” là lệnh đã nạp tiền trước: số tiền sẽ được chuyển khỏi ví của người mua ngay khi lệnh được đặt. Số dư trong ví “Steam” không thể rút lại — chúng chỉ có thể được chi tiêu trong hệ sinh thái Steam. Cộng tổng mức giá tại mọi mức của sổ lệnh mua cho từng mặt hàng được theo dõi sẽ cho ta tổng số tiền đã cam kết, không thể rút ra được.\n\n$128.1M\ncam kết duy trì các lệnh mua Steam\n170.6M\nCác lệnh mua do cá nhân tài trợ hiện đang có hiệu lực\n$105.8M\ngiá chào bán của các bất động sản được rao bán trước mặt họ\n$15.9M\nPhần hoa hồng của Valve nếu mọi bất động sản được rao bán đều được bán với giá chào bán\nCon số này là gì, và nó không phải là gì\n1\nĐó là tiền thật đã được nộp. Mỗi đô la được tính đều đã được trừ khỏi ví và hiện đang được dùng để đảm bảo cho một lệnh mở trên các loại sản phẩm củ31,253.\n2\nĐó là không phải doanh thu và đây không phải là một nhận định về bảng cân đối kế toán củValve. Việc số tiền lưu hành được giữ ở đâu và được ghi nhận trên sổ sách của ai thì chưa được xác định rõ trong bài viết này.\n3\nĐó là một ảnh chụp nhanh, không phải luồng. Người mua có thể hủy đơn hàng, khi đó số tiền sẽ được hoàn lại vào ví — nhưng vẫn chưa rời khỏi Steam.\n4\nCái mấu chốt nằm ở cánh cửa một chiều. Một thị trường mà tiền tệ trong đó không thể rút ra thành tiền mặt chính là lý do khiến hàng hóa bị đánh cắp bị chuyển đổi tắt Steam thay vì trên đó.\n\nPhương pháp: mỗi mức giá của mỗi sổ lệnh mua được theo dõi, nhân với số lượng lệnh đang tồn tại tại mức giá đó. Bộ dữ liệu đầy đủ: cs2sh-steam-locked-capital.json →\n\nDoanh số bán hàng thực tế, không phải giá chào bán · một sàn giao dịch · số ngày theo dõi 90\nThực tế, $30.9 triệu đã được giao dịch — trên kệ nhỏ nhất trong số năm kệ.\n\nMột giao dịch bán với giá cao có thể là một món đồ thủ công hiếm hoặc phiên bản dán nhãn của một mặt hàng cơ bản giá rẻ (ví dụ: e.g – một mặt hàng có giá $30 nhưng đã được bán thành công với giá $9,772 chỉ một lần duy nhất). “Cao” ở đây có nghĩa là mức giá cao nhất trong các giao dịch đã hoàn tất, chứ không phải giá bình thường của mặt hàng đó.\n\nMỗi số liệu còn lại trên trang này đo lường điều gì đó là được liệt kê. Cái này đo lường những gì đã từng là đã bán. Skinport công bố các giao dịch đã hoàn tất của chính mình, và trong 90 ngày gần nhất tổng số giao dịch này là 1,219,143 doanh số giá trị $30,927,032, với mức giá trung bình là $25.37 mỗi chiếc.\n\n1.22M\ndoanh số bán hàng đã hoàn tất trong 90 ngày, trên một sàn thương mại điện tử\n$30.9M\ndoanh thu trong cùng khoảng thời gian đó\n$125M\ntỷ lệ tăng trưởng hàng năm — mức sàn, không phải là ước tính\n~2%\nTỷ trọng của Skinport trong danh mục cổ phiếu vượt mức trần tính theo giá trị niêm yết\nDoanh thu đến từ đâu\ndưới $1\n0.5%\n$1-10\n5.8%\n$10-100\n22.2%\n$100-1k\n59.4%\n$1k-1.8k\n6.9%\ntrên mức trần của chương trình “Steam”\n5.3%\n\nChiều dài thanh biểu đồ thể hiện doanh thu; con số này là tỷ trọng của cấp đó so với tổng doanh thu. 59.4% trong số tiền được chuyển trong mức $100–$1k, từ doanh số bán hàng trên 71,437.\n\nPhía trên chiếc mũ của “Valve”, hoạt động bán hàng vẫn diễn ra\n492\n\ntổng giá trị các giao dịch bán hàng đã hoàn tất đối với các mặt hàng có giá cao hơn mức trần của Chương trình Hỗ trợ Thu nhập (Steam), trị giá $1,643,938, trên 76 loại sản phẩm — tại một sàn thương mại điện tử chiếm khoảng 2% diện tích kệ hàng đó. Không có giao dịch nào trong số đó có thể diễn ra trên Steam.\n\nBộ dữ liệu đầy đủ: cs2sh-offsteam-90d-dynamics.json → · các mức cao đã đạt được →\n\nSkinport là MỘT trong số các thị trường bên thứ ba được theo dõi tại đây, và với giá trị niêm yết vượt quá ngưỡng “Steam”, đây là thị trường nhỏ nhất trong số năm thị trường (chiếm khoảng 2% của ngưỡng đó). Mọi con số tổng hợp tại đây đều là mức sàn của nền kinh tế ngoàiSteam, chứ không phải là thước đo cho nền kinh tế đó. Không sử dụng bất kỳ dữ liệu nào từ Steam.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Kinh tế thị trường — Hai nền kinh tế và mức trần niêm yết"
          },
          {
            "level": 2,
            "id": null,
            "text": "Một hệ thống hạ tầng. Hai nền kinh tế."
          },
          {
            "level": 2,
            "id": null,
            "text": "Đăng ký nền tảng"
          },
          {
            "level": 2,
            "id": null,
            "text": "Chênh lệch giá là có thể đo lường được."
          },
          {
            "level": 3,
            "id": null,
            "text": "Năm sàn giao dịch: các mặt hàng có giá cao hơn mức trần “Steam”"
          },
          {
            "level": 3,
            "id": null,
            "text": "Phân phối giá vượt mức trần"
          },
          {
            "level": 3,
            "id": null,
            "text": "Các sản phẩm hàng đầu — mức giá chào bán đã được xác minh thấp nhất trên năm sàn thương mại điện tử"
          },
          {
            "level": 2,
            "id": null,
            "text": "Mức phí được quảng cáo là 15%.. Hầu hết các tin đăng đều trả cao hơn mức này."
          },
          {
            "level": 3,
            "id": null,
            "text": "Phí được tính, tính theo tỷ lệ phần trăm so với mức phí cơ bản (15%)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Một ví dụ minh họa"
          },
          {
            "level": 2,
            "id": null,
            "text": "Mua hàng trên Steam thường đắt hơn. Hầu như luôn luôn như vậy."
          },
          {
            "level": 3,
            "id": null,
            "text": "Mức phí bảo hiểm trung vị của Chương trình Bảo hiểm Sức khỏe Toàn dân (Steam), theo nhóm giá"
          },
          {
            "level": 3,
            "id": null,
            "text": "Tại sao phân khúc cao cấp lại quan trọng"
          },
          {
            "level": 2,
            "id": null,
            "text": "128.1 triệu đô la đã cam kết cho các đơn đặt hàng không thể hủy bỏ."
          },
          {
            "level": 2,
            "id": null,
            "text": "Thực tế, $30.9 triệu đã được giao dịch — trên kệ nhỏ nhất trong số năm kệ."
          },
          {
            "level": 3,
            "id": null,
            "text": "Doanh thu đến từ đâu"
          },
          {
            "level": 3,
            "id": null,
            "text": "Phía trên chiếc mũ của “Valve”, hoạt động bán hàng vẫn diễn ra"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/vi/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/vi/elite_skins.html",
          "https://phishdestroy.io/steam_dossier/vi/skin_atlas.html",
          "https://phishdestroy.io/steam_dossier/vi/skin_atlas.html#grading",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-steam-fee-census.json",
          "https://phishdestroy.io/steam_dossier/vi/skin_atlas.html#cliff",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-walled-garden-premium.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-steam-locked-capital.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-offsteam-90d-dynamics.json",
          "https://phishdestroy.io/steam_dossier/vi/skin_atlas.html#highs"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/vi/market_economics.content.json",
      "export_json_sha256": "743c474bd45a4f311b98b7a87d2c780925bce32af03c496e2f0f8ab0b8fea193"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "vi/regulatory_act_print.html",
      "language": "vi",
      "title": "LUẬT KIỂM TOÁN PHÁP Y: Valve Steam Trang web API Hệ sinh thái & Khai thác thương mại (Tham khảo: VAL-REG-2026-09)",
      "source_url": "https://phishdestroy.io/steam_dossier/vi/regulatory_act_print",
      "source_html_sha256": "32b6e6f224fca1b2f771a7179a6d3ea43981e2f26883d1f91de2c191589874d2",
      "exported_at": "2026-09-29T00:23:03.924Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "regulatory_act_print.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/vi/regulatory_act_print.pdf?v=print-20260929-v5",
        "sha256": "a48dad412f80513241c7fbfe0b3d5862275d38201b6a7f8fc900ff9462d51a02",
        "bytes": 192782,
        "pages": 13
      },
      "integrity": {
        "signed_object": "regulatory_act_print.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "regulatory_act_print.content.json.asc",
        "digest_file": "regulatory_act_print.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify regulatory_act_print.content.json.asc regulatory_act_print.content.json",
          "sha256sum -c regulatory_act_print.content.json.sha256"
        ]
      },
      "content": {
        "text": "phishdestroy.io · Liên minh Nghiên cứu Pháp y · Cơ sở dữ liệu công khai toàn cầu\nHỒ SƠ: VAL-REG-2026-09-EVID\nNGUỒN GỐC: phishdestroy.io/steam_dossier/\nQUYỀN: TẤT CẢ CÁC QUYỀN ĐÃ ĐƯỢC NHƯỢNG LẠI CHO NHÂN LOẠI\nLuật Kiểm toán Pháp y và Phụ lục Quy định\nViệc cung cấp dịch vụ “API” có hệ thống từ bên thứ ba, kiến trúc bỏ qua tự động và việc không thực thi các điều khoản hợp đồng trong hệ sinh thái Valve Steam\nCấp tên miềnphishdestroy.io\nNền tảng mục tiêuValve Steam / Steamworks\nVectơ xác thực chínhSteam OpenID 2.0 / Trang web API\nLời tri ân pháp lýTất cả các quyền dành cho nhân loại (CC0)\nPhần I: Bản ghi nhớ của Ban điều hành và các kết luận về thực tếSỐ THAM KHẢO: BẢN TÓM TẮT -01\n\nTài liệu này là một báo cáo kiểm toán pháp y chính thức nhằm phân tích sự tương tác trong hoạt động giữa các điều khoản thương mại đã công bố của Công ty Cổ phầnValve, các điểm cuối xác thực kỹ thuật của công ty này và các nền tảng thương mại của bên thứ ba đã được quan sát. Cuộc kiểm toán được thực hiện thông qua việc quan sát mạng thụ động, không cần xác thực, xác minh đăng ký tại RDAP và dữ liệu đo lường từ công cụ Link Filter công khai.\n\nNội dung cốt lõi dựa trên sự thật: Quan sát thực tế cho thấy sự khác biệt có hệ thống giữa các tuyên bố công khai trong hợp đồng của Valve và cơ sở hạ tầng sản xuất của họ. Trong khi Thỏa thuận Người đăng ký (SSA) của Steam nghiêm cấm việc khai thác thương mại trái phép (§ 2.G), tương tác tự động bằng bot/script (§ 4.C) và chuyển nhượng tài khoản (§ 1.C), Công ty Valve vẫn tiếp tục cung cấp cơ sở hạ tầng xác thực OpenID theo thời gian thực và truy vấn kho hàng cho ít nhất 175 thực thể thương mại, tạo ra khối lượng giao dịch thứ cấp lên đến hàng tỷ đô la.\n\n175\nCác đơn vị kinh doanh đã được kiểm toán\n44\nMáy chủ xác thực miền riêng biệt\n26\nCác cặp proxy chia lọc\n100%\nCác điều khoản chưa được thi hành của SSA: § 2.G / § 4.C\n0\nViệc thu hồi quyền truy cập bắt buộc\nKhung pháp lý và hợp đồng áp dụng\nĐiều 2.G của Bộ luật An sinh Xã hội (SSA)\nCấm sử dụng cho mục đích thương mại: Nghiêm cấm việc khai thác Nội dung và Dịch vụ cho mục đích thương mại mà không có sự cho phép trước bằng văn bản từ Công ty Cổ phầnValve.\nĐiều 4.C của Bộ luật An sinh Xã hội (SSA)\nHạn chế về tự động hóa: Nghiêm cấm sử dụng các tập lệnh, bot giao dịch, macro hoặc các hệ thống không do con người điều khiển để tương tác với các dịch vụ và thị trường của Steam.\nĐiều 1.C của Luật An sinh Xã hội (SSA)\nQuy định về sử dụng cá nhân: Giới hạn việc sử dụng tài khoản chỉ cho mục đích cá nhân; nghiêm cấm việc bán, cho thuê, chuyển nhượng hoặc trao đổi tài khoản người dùng Steam.\nDSA của EU (Luật về các dịch vụ số của Liên minh châu Âu - 2022/2065)\nĐánh giá rủi ro hệ thống (Điều 34/35): Các nền tảng trực tuyến quy mô rất lớn (VLOPs) phải chủ động phát hiện, đánh giá và giảm thiểu các rủi ro hệ thống phát sinh từ việc lạm dụng tự động và khai thác thương mại trái phép.\nPhần II: Sổ đăng ký Phụ lục A — Các cặp liên kết được ghi nhận đã qua bộ lọc (Các tuyến đường 26)SỐ THAM KHẢO: EX-SPLIT-LEDGER\n\nPhân tích pháp y về kỹ thuật né tránh bằng cách tách miền: Trong hệ thống lọc liên kết “Steam” () của Valve (steamcommunity.com/linkfilter/?url=...), khi người dùng cuối nhấp vào một liên kết dẫn đến một nền tảng cờ bạc hoặc chợ đen đã bị gắn cờ, trang Valve sẽ hiển thị một cảnh báo nổi bật (\"Liên kết bị chặn! ... đã được báo cáo là có khả năng gây hại\"). Tuy nhiên, quá trình truy vết nguồn gốc theo phương pháp pháp y cho thấy các nền tảng thương mại 26 đang hoạt động trên một kiến trúc miền phân tách: trong khi tên miền thương mại chính bị CHẶN trên Bộ lọc liên kết, tên miền phụ lưu trữ điểm cuối trả về OpenID của Valve lại được đánh dấu là AN TOÀN. Các máy chủ OpenID của Valve chấp nhận các yêu cầu xác thực từ các máy chủ proxy này mà không bị gián đoạn, nhờ đó vô hiệu hóa cảnh báo an toàn dành cho người dùng đồng thời vẫn tiếp tục xử lý các thao tác đăng nhập.\n\n#\tTên miền thương mại chính\tBộ lọc chính\tMiền máy chủ trung gian xác thực OpenID\tBộ lọc xác thực\tRDAP Đã đăng ký\tCơ sở tính thuế\n01\trollbit.com\tBLOCKED\trbsnin.com\tCLEAN\t2026-09-18\tPASSIVE_CAPTURE\n02\tskin.club\tBLOCKED\tsc-auth.net\tCLEAN\t2019-04-02\tPASSIVE_CAPTURE\n03\thowl.gg\tBLOCKED\thowl.uno\tCLEAN\t2026-08-11\tPASSIVE_CAPTURE\n04\tduelbits.com\tBLOCKED\tswitchflips.com\tCLEAN\t2020-04-21\tPASSIVE_CAPTURE\n05\tcsgofast.com\tBLOCKED\tsteam-login.authtofast.com\tCLEAN\t2026-06-30\tPASSIVE_CAPTURE\n06\tfarmskins.com\tBLOCKED\tsteam.kobal.cc\tCLEAN\t2017-01-07\tPASSIVE_CAPTURE\n07\tcobaltlab.tech\tBLOCKED\tcobaltauth.com\tCLEAN\t2025-01-07\tPASSIVE_CAPTURE\n08\tcsgo.net\tBLOCKED\tcn2.easylot.net\tCLEAN\t2016-09-03\tPASSIVE_CAPTURE\n09\tggdrop.com\tBLOCKED\tggauth.com\tCLEAN\t2023-05-03\tPASSIVE_CAPTURE\n10\trustchance.com\tBLOCKED\thgfuihd.com\tCLEAN\t2019-01-27\tPASSIVE_CAPTURE\n11\tskin.fans\tBLOCKED\tauth.skinfans.com\tCLEAN\t2018-07-16\tPASSIVE_CAPTURE\n12\tskinport.com\tBLOCKED\tskinport.app\tCLEAN\t2020-06-20\tPASSIVE_CAPTURE\n13\tskins.cash\tBLOCKED\tskinscash.live\tCLEAN\t2019-12-05\tPASSIVE_CAPTURE\n14\ttf2hunt.com\tBLOCKED\trstspcl.com\tCLEAN\t2020-08-08\tPASSIVE_CAPTURE\n15\tdaddyskins.com\tBLOCKED\tgo-go-daddy.com\tCLEAN\t2019-01-26\tPASSIVE_CAPTURE\n16\tkey-drop.com\tBLOCKED\tkdauth.com\tCLEAN\t2026-05-13\tPASSIVE_CAPTURE\n17\tclash.gg\tBLOCKED\tclggauth.com\tCLEAN\t2024-09-16\tPASSIVE_CAPTURE\n18\tc5game.com\tBLOCKED\twww.imbastar.com\tCLEAN\t2016-02-27\tPASSIVE_CAPTURE\n19\tswap.gg\tBLOCKED\tswapauth.com\tCLEAN\t2018-10-06\tPASSIVE_CAPTURE\n20\tshadowpay.com\tBLOCKED\tthelogins.com\tCLEAN\t2018-01-22\tPASSIVE_CAPTURE\n21\tcsgocases.com\tBLOCKED\tlog-1n.com\tCLEAN\t2017-11-27\tPASSIVE_CAPTURE\n22\tcsgogem.com\tBLOCKED\tapi.csgem.com\tCLEAN\t2014-03-08\tPASSIVE_CAPTURE\n23\tgamdom.com\tBLOCKED\tlogin.gambldom.com\tCLEAN\t2017-09-24\tPASSIVE_CAPTURE\n24\t12cs.fail\tBLOCKED\tfail.games\tCLEAN\t2021-08-24\tPASSIVE_CAPTURE\n25\tskinsnipe.com\tBLOCKED\tpricing.tradeupspy.com\tCLEAN\t2020-03-11\tPASSIVE_CAPTURE\n26\tcsgobig.com\tBLOCKED\tletmeinbig.com\tCLEAN\t2023-01-20\tPASSIVE_CAPTURE\n\n* Lưu ý: Các kiểm tra thụ động được thực hiện đối với các điểm cuối bộ lọc liên kết (Link Filter) chưa được xác thực tại Steam trên các trang 2026-09-19 và 2026-09-21.. Nội dung phản hồi HTTP thô và các giá trị băm SHA-256 được lưu giữ trong bộ dữ liệu kho lưu trữ (steam_tos_assets/linkfilter-2026-09-22.json).\n\nPhần III: Sổ đăng ký B — Điều tra toàn diện các đơn vị thương mại đã được kiểm toán thuộc Chương trình “175”SỐ THAM CHIẾU: EX-175-MASTER-CENSUS\n\nBảng đăng ký sau đây liệt kê chi tiết tất cả các nền tảng thương mại của bên thứ ba thuộc 175 đã được xác minh tích cực trong cơ sở dữ liệu kiểm toán. Mỗi bản ghi nêu rõ tên thực thể, tên miền thương mại chính, lộ trình xác thực OpenID được quan sát tại Steam, phân loại hoạt động, các trường hợp vi phạm hợp đồng (SSA § 2.G, SSA § 4.C, SSA § 1.C) và trường hành động được ghi lại trong tập dữ liệu nguồn. Nhãn \"Xem bằng chứng có ngày tháng\" hướng người đọc đến các hồ sơ hỗ trợ; nhãn này không khẳng định rằng Valve đã không thực hiện bất kỳ hành động nào. Trường hành động bị thiếu được báo cáo là \"chưa được xác định\".\n\nTài liệu trưng bày\tTên thực thể & tên miền chính\tTuyến xác thực / Proxy được quan sát\tPhân loại\tVi phạm hợp đồng\tValve Hành động\nEX-001\tCSGORoll\ncsgoroll.com\n\t\nwww.csgoroll.com\nDIRECT\n\tSkin Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-002\tCSGOEmpire\ncsgoempire.com\n\t\ncsgoempirelogin4.com\nSPLIT PROXY\n\tCasino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-003\tRollbit\nrollbit.com\n\t\nrbsnin.com\nSPLIT PROXY\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-004\t500 Casino\n500.casino\n\t\nfivezerozero.co\nSPLIT PROXY\n\tLicenced Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-005\tCSGOBig\ncsgobig.com\n\t\ncsgobig.com\nDIRECT\n\tRoulette/Slots\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-006\tCaseDrop\ncasedrop.com\n\t\ncasedrop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-007\tRustReaper\nrustreaper.com\n\t\nrustreaper.com\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-008\tBanditCamp\nbanditcamp.com\n\t\nbanditcamp.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-009\tSkinBox\nskinbox.com\n\t\nskinbox.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-010\tTastyDrop\ntastydrop.com\n\t\ntastydrop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-011\tCSGOPolygon\ncsgopolygon.gg\n\t\ncsgopolygon.gg\nDIRECT\n\tRoulette Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-012\tMagicDrop\nmagicdrop.ru\n\t\nmagicdrop.ru\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-013\tCSDice\ncsdice.com\n\t\ncsdice.com\nDIRECT\n\tDice Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-014\tRustly\nrustly.com\n\t\nrustly.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-015\tSkinOdds\nskinodds.com\n\t\nskinodds.com\nDIRECT\n\tUpgrader Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-016\tCSGOWin\ncsgowin.com\n\t\ncsgowin.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-017\tCSGORun\ncsgorun.net\n\t\ncsgorun.net\nDIRECT\n\tCrash Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-018\tOpenSkins\nopenskins.com\n\t\nopenskins.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-019\tRustBet\nrustbet.com\n\t\nrustbet.com\nDIRECT\n\tRust Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-020\tCSGOMagic\ncsgomagic.com\n\t\ncsgomagic.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-021\tCSGOBounty\ncsgobounty.com\n\t\ncsgobounty.com\nDIRECT\n\tUpgrader/Contract\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-022\tEZSkins\nezskins.com\n\t\nezskins.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-023\tRustCases\nrustcases.com\n\t\nrustcases.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-024\tCSGOReaper\ncsgoreaper.com\n\t\ncsgoreaper.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-025\tCSGOCases\ncsgocases.com\n\t\ncsgocases.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-026\tCSGO-Skins\ncsgo-skins.com\n\t\ncsgo-skins.com\nDIRECT\n\tCase Upgrader\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-027\tCSGONet\ncsgonet.com\n\t\ncsgonet.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-028\tWTFSkins\nwtfskins.com\n\t\nwtfskins.com\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-029\tCSGOFast\ncsgofast.com\n\t\nsteam-login.authtofast.com\nSPLIT PROXY\n\tRoulette Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-030\tDuelbits\nduelbits.com\n\t\nswitchflips.com\nSPLIT PROXY\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-031\tFlameCases\nflamecases.com\n\t\nflamecases.com\nDIRECT\n\tCase Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-032\tFarmskins\nfarmskins.com\n\t\nsteam.kobal.cc\nSPLIT PROXY\n\tCase Opener\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-033\tCSGOLuck\ncsgoluck.com\n\t\ncsgoluck.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-034\tGamedom\ngamedom.com\n\t\ngamedom.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-035\tSkin.Club\nskin.club\n\t\nsc-auth.net\nSPLIT PROXY\n\tCase Battles\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-036\tDaddySkins\ndaddyskins.com\n\t\ndaddyskins.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-037\tInsane.gg\ninsane.gg\n\t\napi.insane.gg\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-038\tRustix\nrustix.gg\n\t\nrustix.gg\nDIRECT\n\tRust Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-039\tSkins.Club\nskins.club\n\t\nskins.club\nDIRECT\n\tSkin Upgrade\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-040\tCSGOHouse\ncsgohouse.org\n\t\ncsgohouse.org\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-041\tSkinRave\nskinrave.net\n\t\nskinrave.net\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-042\tBloodyCase_GG\nbloodycase.gg\n\t\nbloodycase.gg\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-043\tCSGOClicker\ncsgoclicker.com\n\t\ncsgoclicker.com\nDIRECT\n\tClicker/Upgrade\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-044\tRustBet_GG\nrustbet.gg\n\t\nrustbet.gg\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-045\tCS_Drop\ncs-drop.com\n\t\ncs-drop.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-046\tHellStore\nhellstore.net\n\t\nhellstore.net\nDIRECT\n\tSkin Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-047\tRustLoot\nrustloot.com\n\t\nrustloot.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-048\tCSGO_Case\ncsgo-case.com\n\t\ncsgo-case.com\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-049\tCS2Skin\ncs2skin.com\n\t\ncs2skin.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-050\tJuice_GG\njuice.gg\n\t\nletmeinjuice.com\nSPLIT PROXY\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-051\tGGDrop\nggdrop.com\n\t\nggauth.com\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-052\tCSGOGem\ncsgogem.com\n\t\ncsgogem.com\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-053\tRainbet\nrainbet.com\n\t\nservices.rainbet.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-054\tHowl_GG\nhowl.gg\n\t\nhowl.uno\nSPLIT PROXY\n\tSkins Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-055\tChicken_GG\nchicken.gg\n\t\nchicken.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-056\tCSGOCasino_GG\ncsgocasino.gg\n\t\napi.csgocasino.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-057\tHunt_GG\nhunt.gg\n\t\napi.hunt.gg\nDIRECT\n\tSkins Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-058\tCSBattle\ncsbattle.com\n\t\ncsbattle.com\nDIRECT\n\tCase Battles\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-059\tSkinRave_GG\nskinrave.gg\n\t\napi.skinrave.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-060\tCSDouble\ncsdouble.gg\n\t\ncsdouble.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-061\tRustChance\nrustchance.com\n\t\nhgfuihd.com\nSPLIT PROXY\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-062\tRustClash\nrustclash.com\n\t\nrustclash.com\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-063\tCobaltLab\ncobaltlab.tech\n\t\ncobaltauth.com\nSPLIT PROXY\n\tRust Automation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-064\tRaided_GG\nraided.gg\n\t\napi.raided.gg\nDIRECT\n\tRust Roulette\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-065\tRustNeo\nrustneo.gg\n\t\nrustneo.gg\nDIRECT\n\tRust Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-066\tSplits_GG\nsplits.gg\n\t\nsplits.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-067\tUpgrader_Pro\nupgrader.pro\n\t\nupgauth.space\nSPLIT PROXY\n\tSkin Upgrader\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-068\tSkinFans\nskin.fans\n\t\nauth.skinfans.com\nSPLIT PROXY\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-069\tHotPizza\nhotpizza.one\n\t\nhotpizza.one\nDIRECT\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-070\tG4Skins\ng4skins.com\n\t\nauth.g4s.to\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-071\t12CS_Fail\n12cs.fail\n\t\n12cs.fail\nDIRECT\n\tCrash Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-072\tTF2Royal\ntf2royal.com\n\t\ntf2auth.com\nSPLIT PROXY\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-073\tTF2Easy\nwww.tf2easy.com\n\t\nwww.tf2easy.com\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-074\tTF2Hunt\ntf2hunt.com\n\t\nrstspcl.com\nSPLIT PROXY\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-075\tTF2Bet\ntf2.bet/coinflip\n\t\ntf2.bet\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-076\tTF2Blaze\ntf2blaze.com\n\t\ntf2blaze.com\nDIRECT\n\tTF2 Gambling\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-077\tOpenStars_GG\nopenstars.gg\n\t\nopenstars.gg\nDIRECT\n\tSkin Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-078\tShuffle_Com\nshuffle.com\n\t\nshuffle.com\nDIRECT\n\tCrypto Casino\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-079\tSkins.com\nskins.com\n\t\napi.skins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-080\tWhite.Market\nwhite.market\n\t\nwhite.market\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-081\tBuff.Market\nbuff.market\n\t\nbuff.market\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-082\tAvan.Market\navan.market\n\t\navan.market\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-083\tCS.MONEY\ncs.money\n\t\nauth.dota.trade\nSPLIT PROXY\n\tTrading Engine\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-084\tUUSkins\nuuskins.com\n\t\nuuskins.com\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-085\tYouPin898\nyoupin898.com\n\t\nyoupin898.com\nDIRECT\n\tMass Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-086\tMoon.Market\nmoon.market\n\t\nmoon.market\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-087\tCSFloat\ncsfloat.com\n\t\ncsgofloat.com\nSPLIT PROXY\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-088\tSkin.Land\nskin.land\n\t\nauth.skin.land\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-089\tC5Game\nc5game.com\n\t\nc5game.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-090\tHaloSkins\nhaloskins.com\n\t\nhaloskins.com\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-091\tBuff.163\nbuff.163.com\n\t\nbuff.163.com\nDIRECT\n\tCorporate Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-092\tWaxpeer\nwaxpeer.com\n\t\nwaxpeer.com\nDIRECT\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-093\tCS.MONEY Bot\ncs.money\n\t\nauth.dota.trade\nSPLIT PROXY\n\tBot Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-094\tMarket.CSGO\nmarket.csgo.com\n\t\ndota2.net\nSPLIT PROXY\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-095\tSkinport\nskinport.com\n\t\nskinport.app\nSPLIT PROXY\n\tRegulated Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-096\tSkinFlow\nskinflow.gg\n\t\napi.skinflow.gg\nDIRECT\n\tMarketplace/Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-097\tDMarket\ndmarket.com\n\t\ndmarket.com\nDIRECT\n\tUS Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-098\tSkin.place\nskin.place\n\t\napi.skin.place\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-099\tSkinsMonkey\nskinsmonkey.com\n\t\nskinsmonkey.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-100\tSkinBaron\nskinbaron.de\n\t\nskinbaron.com\nSPLIT PROXY\n\tCorporate Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-101\tSteam\nsteamcommunity.com/market\n\t\nsteamcommunity.com/market\nDIRECT\n\tOfficial Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-102\tRustTM\nrust.tm\n\t\ndota2.net\nSPLIT PROXY\n\tRust Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-103\tPirateSwap\npirateswap.com\n\t\nlogin.pirateswap.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-104\tMannco.Store\nmannco.store\n\t\nmannco.store\nDIRECT\n\tTF2 Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-105\tSkinSwap\nskinswap.com\n\t\napi.skinswap.com\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-106\tLootFarm\nlootfarm.com\n\t\nlootfarm.com\nDIRECT\n\tTrading Platform\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-107\tRustskins\nrustskins.com\n\t\nrustskins.com\nDIRECT\n\tRust Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-108\tExeSkins\nexeskins.com\n\t\nexeskins.com\nDIRECT\n\tP2P Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-109\tBalticSkins\nbalticskins.com\n\t\nbalticskins.com\nDIRECT\n\tSkins Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-110\tCS.Trade\ncs.trade\n\t\ncs.trade\nDIRECT\n\tInstant Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-111\tRapidSkins\nrapidskins.com\n\t\napi.rapidskins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-112\tTradeIt\ntradeit.gg\n\t\nconnect-tradeit.com\nSPLIT PROXY\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-113\tKrakatoa\nkrakatoa.com\n\t\nkrakatoa.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-114\tShadowPay\nshadowpay.com\n\t\nshadowpay.com\nDIRECT\n\tP2P Marketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-115\t49skins\n49skins.com\n\t\napi.49skins.com\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-116\tSkinVault\nskinvault.gg\n\t\napi.skinvault.gg\nDIRECT\n\tCS2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-117\tAim Market\naim.market\n\t\naim.market\nDIRECT\n\tSkins Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-118\tSkinout\nskinout.gg\n\t\nauth.skinout.gg\nDIRECT\n\tInstant Sell Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-119\tNTSkins\nntskins.com\n\t\nntskins.com\nDIRECT\n\tSkins Trading\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-120\tIGXE\nigxe.cn\n\t\nigxe.cn\nDIRECT\n\tChinese Powerhouse\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-121\tSwap.gg\nswap.gg\n\t\nswap.gg\nDIRECT\n\tAutomated Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-122\tBitskins\nbitskins.com\n\t\nbitskins.com\nDIRECT\n\tCash-out Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-123\tGamerPay\ngamerpay.gg\n\t\ngamerpay.gg\nDIRECT\n\tP2P Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-124\tTF2Mart\ntf2mart.com\n\t\ntf2mart.com\nDIRECT\n\tTF2 Automation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-125\tSkinBid\nskinbid.com\n\t\nskinbid.com\nDIRECT\n\tSkin Auctions\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-126\tLootBear\nlootbear.com\n\t\nlootbear.com\nDIRECT\n\tSkin Rental\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-127\tBackpack.tf\nbackpack.tf\n\t\nbackpack.tf\nDIRECT\n\tTF2 Valuation\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-128\tScrap.tf\nscrap.tf\n\t\nscrap.tf\nDIRECT\n\tTF2 Scrap Swap\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-129\tMarketplace.tf\nmarketplace.tf\n\t\nmarketplace.tf\nDIRECT\n\tTF2 Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-130\tSTNTrading\nstntrading.eu\n\t\nstntrading.eu\nDIRECT\n\tTF2 Botnet\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-131\tSkins.Cash\nskins.cash\n\t\nskinscash.live\nSPLIT PROXY\n\tInstant Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-132\tSkinWallet\nskinwallet.com\n\t\nskinwallet.com\nDIRECT\n\tInstant Cashout\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-133\tDota2Market\ndota2market.com\n\t\ndota2market.com\nDIRECT\n\tDota 2 Market\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-134\tCSGO.NET\ncsgo.net\n\t\ncn2.easylot.net\nSPLIT PROXY\n\tCase Opening\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-135\tCybershoke\ncybershoke.net\n\t\nauth.cybershoke.net\nDIRECT\n\tCommunity Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-136\tXPlay_GG\nxplay.gg\n\t\nxplay.gg\nDIRECT\n\tServer Network\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-137\tFastCup\nfastcup.net\n\t\napi.fastcup.net\nDIRECT\n\tMatchmaker Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-138\tEsportal\nesportal.com\n\t\nesportal.com\nDIRECT\n\tMatchmaking Portal\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-139\tGamersClub\ngamersclub.com.br\n\t\ngamersclub.com.br\nDIRECT\n\tLATAM Hub\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-140\tLeetify\nleetify.com\n\t\nleetify.com\nDIRECT\n\tSaaS Analytics\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-141\tScope_GG\nscope.gg\n\t\nscope.gg\nDIRECT\n\tSaaS Analytics\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-142\tTradeUpSpy\ntradeupspy.com\n\t\napi.tradeupspy.com\nDIRECT\n\tSaaS Tools\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-143\tEpidemic_GG\nepidemic.gg\n\t\nepidemic.gg\nDIRECT\n\tSaaS Tools\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-144\tCSDeals\ncs.deals\n\t\napi.cs.deals\nDIRECT\n\tMarketplace\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-145\tPricempire\npricempire.com\n\t\npricempire.com\nDIRECT\n\tSaaS Price DB\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-146\tCS2Stash\ncs2stash.com\n\t\ncs2stash.com\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-147\tCSGOSkins\ncsgoskins.gg\n\t\ncsgoskins.gg\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-148\tSteamAnalyst\nsteamanalyst.com\n\t\nsteamanalyst.com\nDIRECT\n\tSaaS Index\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-149\tSteamCardExchange\nsteamcardexchange.net\n\t\nsteamcardexchange.net\nDIRECT\n\tTrading Exchange\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-150\tDotaBuff\ndotabuff.com\n\t\ndotabuff.com\nDIRECT\n\tSaaS Tracker\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-151\tTracker_GG\ntracker.gg\n\t\ntracker.gg\nDIRECT\n\tSaaS Tracker\tSSA § 2.G, SSA § 4.C\tSee dated evidence\nEX-152\tFSB Market (an anonymized label; the original name is withheld here)\nFSB Market\n\t\nFSB Market\nDIRECT\n\tMass Blackmarket\tSSA § 2.G, SSA § 4.C, SSA § 1.C\tSee dated evidence\nEX-153\tFunPay\nfunpay.com\n\t\nfunpay.com\nDIRECT\n\tAccount Exchange\tSSA § 2.G, SSA § 4.C, SSA § 1.C\tSee dated evidence\nEX-154\tPlayerAuctions\nplayerauctions.com\n\t\nplayerauctions.com\nDIRECT\n\tGrey Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-155\tEldorado.gg\neldorado.gg\n\t\neldorado.gg\nDIRECT\n\tAccount Portal\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-156\tG2A\ng2a.com\n\t\ng2a.com\nDIRECT\n\tMass Key Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-157\tKinguin\nkinguin.net\n\t\nkinguin.net\nDIRECT\n\tMass Key Market\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-158\tG2G.com\ng2g.com\n\t\ng2g.com\nDIRECT\n\tVirtual Services\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-159\tPlayerup\nplayerup.com\n\t\nplayerup.com\nDIRECT\n\tAccount Broker\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-160\tZ2U.com\nz2u.com\n\t\nwww.z2u.com\nDIRECT\n\tReady-Account Hub\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-161\tSmurfHub\nsmurfhub.net\n\t\nsmurfhub.net\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-162\tSmurfAccounts\nsmurfaccounts.com\n\t\nsmurfaccounts.com\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-163\tBuyCSGORank\nbuycsgorank.com\n\t\nbuycsgorank.com\nDIRECT\n\tRank Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-164\tCSGOSmurfKings\ncsgosmurfkings.com\n\t\ncsgosmurfkings.com\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-165\tSmurfStore_Co\nsmurfstore.co\n\t\nsmurfstore.co\nDIRECT\n\tSmurf Shop\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-166\tSteamLvlUp\nsteamlvlup.com\n\t\nsteamlvlup.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-167\tSteamLevels\nsteamlevels.com\n\t\nsteamlevels.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-168\tLevelSteam\nlevelsteam.com\n\t\nlevelsteam.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-169\tSteamLevelU\nsteamlevelu.com\n\t\nsteamlevelu.com\nDIRECT\n\tCard Leveling\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-170\tEloKing\neloking.com\n\t\neloking.com\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-171\tBoosteria\nboosteria.org\n\t\nboosteria.org\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-172\tOvergear\novergear.com\n\t\novergear.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-173\tBlazingBoost\nblazingboost.com\n\t\nblazingboost.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-174\tDota2Boost\ndota2boost.com\n\t\ndota2boost.com\nDIRECT\n\tRank Boosting\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nEX-175\tBuyBoost\nbuyboost.com\n\t\nbuyboost.com\nDIRECT\n\tBoosting SaaS\tSSA § 2.G, SSA § 1.C\tSee dated evidence\nPhần IV: Kiến trúc kỹ thuật và cơ chế xác thựcMÃ THAM KHẢO: TECH-ANALYSIS-01\n\n1. Việc thiếu cơ chế xác thực quyền sở hữu tên miền trong OpenID 2.0: Việc triển khai giao thức OpenID 2.0 của Valve (https://steamcommunity.com/openid/login) đánh giá openid.return_to và openid.realm các thông số mà không yêu cầu nhà phát triển phải đăng ký trước, xác minh thách thức mật mã hay xác thực quyền sở hữu tên miền. Bất kỳ nhà khai thác thương mại nào cũng có thể hướng người dùng đến màn hình đăng nhập của Valve và nhận được một tuyên bố danh tính được ký bằng mật mã (chứa SteamID dạng 64-) được chuyển hướng đến các tên miền tùy ý.\n\n2. Lạm dụng tính năng truy vấn kho quảng cáo theo chương trình (Programmatic Inventory Querying) và tính năng theo dõi chuyển đổi (API): Sau khi xác thực người dùng được xác nhận qua OpenID, các nhà khai thác sẽ truy vấn các điểm cuối công khai và của các đối tác trên Web API (IEconItems_730/GetPlayerItems) để lập chỉ mục tài sản tồn kho theo thời gian thực. Các mạng lưới giao dịch tự động sử dụng mã thông báo phiên giao dịch lập trình để gửi, thăm dò và chấp nhận các đề nghị giao dịch ngang hàng (P2P), điều này trực tiếp vi phạm quy định cấm tương tác không do con người thực hiện tại Điều 4.C của SSA.\n\n3. Sự bất đối xứng của bộ lọc liên kết: Sự tồn tại song song của các cảnh báo tên miền hướng đến người dùng cùng với các điểm cuối xác thực hoạt động đầy đủ đã tạo ra một mâu thuẫn về mặt quy định: Hệ thống theo dõi an ninh của Valve phân loại các nhà cung cấp dịch vụ này là “có khả năng gây hại”, song cơ sở hạ tầng xác thực của Valve vẫn tiếp tục xác thực người dùng của họ.\n\nPhương pháp luận về chứng cứ và Tuyên bố về chuỗi lưu giữ chứng cứ\n\nTài liệu này được tạo ra từ các dữ liệu thu thập từ mạng chưa được xác thực, các truy vấn lịch sử trong cơ sở dữ liệu đăng ký RDAP và các bản kê khai băm mật mã đã được xác minh. Không có thông tin đăng nhập nào của người dùng được đưa vào thử nghiệm xâm nhập hoặc xử lý. Tất cả các phát hiện phản ánh trạng thái mạng sản xuất có thể quan sát được tính đến ngày 2026.. Tài liệu này đóng vai trò là bằng chứng kỹ thuật phi đảng phái, được chuẩn bị để phục vụ các cuộc điều tra của cơ quan tư pháp, cơ quan quản lý và công chúng.\n\nTÓM TẮT: Đã được xác minh theo tiêu chuẩn SHA-256\nc507c9025f93da0aadaf395c4d8882f25973211c318ee8e9b6f18a5b3755e050\nLƯU TRỮ: HỒ SƠ PHÁP LÝ CÔNG KHAI\nBAN HÀNH VÀ KÝ BỞI: phishdestroy.io · Liên minh Nghiên cứu Pháp y\nTÌNH TRẠNG PHÁP LÝ: TẤT CẢ CÁC QUYỀN ĐÃ ĐƯỢC NHƯỢNG LẠI CHO NHÂN LOẠI · CC0 MIỀN CÔNG CỘNG TOÀN CẦU",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Luật Kiểm toán Pháp y và Phụ lục Quy định"
          }
        ],
        "links": []
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/vi/regulatory_act_print.content.json",
      "export_json_sha256": "4de907f6ae580f9baa552f5f5c919f8935891fa3f0da7018f31048a9a1c988da"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "vi/security_timeline.html",
      "language": "vi",
      "title": "Dòng thời gian về an ninh — Hồ sơ “Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/vi/security_timeline",
      "source_html_sha256": "0d01a695794ee2f18f743c29e3a2e0c0aa9ca8ca8886e4422f5958a37037a983",
      "exported_at": "2026-09-29T00:23:04.464Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "security_timeline.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/vi/security_timeline.pdf?v=print-20260929-v5",
        "sha256": "7ba1bfa7ee29556b7fa05867ef179ed301cb8bfbfefb85ed8c631014df8c2ed5",
        "bytes": 105747,
        "pages": 7
      },
      "integrity": {
        "signed_object": "security_timeline.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "security_timeline.content.json.asc",
        "digest_file": "security_timeline.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify security_timeline.content.json.asc security_timeline.content.json",
          "sha256sum -c security_timeline.content.json.sha256"
        ]
      },
      "content": {
        "text": "THÀNH TÍCH VỀ AN NINHTRIỂN LÃM / CÁC TÁC PHẨM DỰ THI “16”\n\n2018 — 2026\n\nLịch sử phát triển bảo mật — Từ “2018” đến “2026”\n\nChính sách bảo mật đã thay đổi. Hãy làm theo hướng dẫn.\n\nPHẦN NÀY CHỨNG MINH ĐIỀU GÌ\n\nBản ghi theo trình tự thời gian này tái hiện quá trình điều chỉnh các biện pháp bảo mật trong suốt tám năm qua trên nền tảng giao dịch và xác thực của Steam. Bản ghi này theo dõi việc triển khai cơ chế giữ lệnh giao dịch trong ngày (2018) tại 7-, cơ chế xác nhận qua thiết bị di động bằng khóa (2023) trên nền tảng Web API, cũng như việc ngừng hỗ trợ các mã thông báo phiên (session token) tại 2026 nhằm đối phó với các kỹ thuật vượt qua bảo mật đã được ghi nhận. Dòng thời gian này cho thấy các bản cập nhật nền tảng luôn chậm hơn so với các lỗ hổng khai thác đã biết, đồng thời vẫn duy trì những lợi thế về cấu trúc cho các nhà khai thác thương mại.\n\n← Quay lại Bản tóm tắt dành cho lãnh đạo\n\nKhóa giao dịch. Kiểm soát đăng nhập. Các hạn chế về “API”. Một bản ghi chép đã lỗi thời về những thay đổi đã xảy ra — và những gì các nguồn thông tin thực sự xác nhận.\n\nKhám phá dòng thời gian ↓\nTÁM NĂM. MỘT KỶ LỤC.16các mốc quan trọng cần xem xét\n\nMỗi mục đều lưu giữ ngày gửi và nguồn gốc. Kết quả xác minh được hiển thị ngay bên cạnh mục đó.\n\nĐÃ ĐƯỢC KIỂM DUYỆT / 24 THÁNG 9 NĂM 2026\n10Sự kiện và ngày tháng đã được xác minh\n06Đã được xác minh một phần\n00Sự không khớp nguồn\n00Cần nguồn tham khảo\nCách đọc bản ghi này\n\nSự kiện và ngày tháng đã được xác minh: cả hai đều được chứng minh bằng một nguồn tư liệu sơ cấp dễ hiểu. Đã được xác minh một phần: Một thay đổi liên quan đã được ghi nhận, nhưng ngày thực hiện hoặc phạm vi áp dụng vẫn chưa được xác định. Không khớp nguồn: Tài liệu được liên kết không chứng minh được luận điểm đã nêu. Cần nguồn tham khảo: Trong bài đánh giá này, không có nguồn tài liệu có ngày tháng phù hợp nào được xác minh. Việc một mục chưa được làm rõ không phải là bằng chứng cho thấy sự kiện đó không xảy ra.\n\nNgày ghi trên các mục chưa được giải quyết là ngày nộp, không phải ngày phát hành đã được xác minh. Nội dung điều tra ban đầu chưa được viết lại.\n\nThứ tự thời gian\n01 — 16\nTìm kiếm bản ghiChủ đềBằng chứngĐơn hàng\n\n16 trong số các bài đăng trên 16 · hiển thị từ mới nhất trước\n\n202609-01Ngày nộp\nCộng đồngĐã được xác minh một phần\nCảnh báo về tin nhắn đáng ngờ trong các cuộc trò chuyện nhóm\n\nMột thông báo chính thức về phiên bản beta đã xác nhận tính năng này trên trang 31 vào tháng 8. Ngày phát hành phiên bản ổn định 1 vào tháng 9 vẫn chưa có ghi chú phát hành cụ thể.\n\nSteam Phiên bản Beta dành cho khách hàng — Ngày 31tháng 8 ↗đã lưu trữ 2026-03-13 ↗\nBài đăng gốc & liên kết đã gửi\n\nTự động đánh dấu các cuộc trò chuyện đáng ngờ\n\nKiểm tra mã nguồn đã gửi ↗\n202601-16Ngày xác minh\nAPISự kiện và ngày tháng đã được xác minh\nQuyền truy cập chi tiết và danh sách trắng IP cho các khóa nhà xuất bản (Thông báo trên Valve)\n\nVào ngày 16 tháng 1 năm 2026, Valve đã đăng tải một thông báo chính thức về Steamworks (\"MỚI: Cải thiện quyền truy cập và cơ chế kiểm soát đối với các khóa Web API\") xác nhận các công cụ cấp quyền chi tiết mới, cho phép các nhà phát triển chia các khóa Web API thành các nhóm riêng biệt (Tổng quan, Giao dịch vi mô, Nền kinh tế và Dữ liệu doanh số), giới hạn các khóa cho các App ID cụ thể và áp dụng danh sách trắng địa chỉ IP máy chủ.\n\nTiêu chuẩn kép rõ rệt: Thông báo chính thức này khẳng định rằng Valve đã hoàn thiện cơ sở hạ tầng kỹ thuật cho các quyền truy cập chi tiết tại API và các hạn chế theo địa chỉ IP, nhưng cố ý không cung cấp những thông tin đó cho các tài khoản người dùng thông thường (steamcommunity.com/dev/apikey). Các khóa xác thực “API” thông thường vẫn là những thông tin xác thực dạng “tất cả hoặc không gì cả”, không có danh sách trắng địa chỉ IP — và chính sự thiếu sót kỹ thuật này đã tạo điều kiện cho ngành công nghiệp chặn giao dịch “API” trị giá hàng triệu đô la phát triển.\n\nValve Thông báo — MỚI: Cải thiện quyền truy cập và kiểm soát đối với khóa Web API (16 Jan 2026) ↗· Tài liệu: Xác thực qua trang web API của Steamworks ↗\nBài đăng gốc & liên kết đã gửi\n\nTrang web Steamworks API Phạm vi chi tiết\n\nXem thông báo chính thức về Steamworks của Valve (493839547938902179) ↗\n202507-15Ngày xác minh\nGiao dịchSự kiện và ngày tháng đã được xác minh\nCác giao dịch CS2 có được khoảng thời gian đảo chiều trong bảy ngày\n\nThông báo đã được đăng tải từ trước của Valve cho biết sẽ hoàn trả các giao dịch vật phẩm trong Counter-Strike trong vòng bảy ngày trước đó. Mặc dù được thiết kế nhằm hạn chế tình trạng chiếm đoạt tài khoản, các cuộc kiểm toán kinh tế do bên thứ ba thực hiện (CSMarketCap ↗) đã ghi nhận một $104M (-25%) thu gọn về vốn hóa thị trường trong vòng 24 giờ do sự cố gián đoạn giao dịch tiền mặt. Theo phân tích của Skinvault ↗, việc kích hoạt một lệnh đảo chiều sẽ tự động áp dụng lệnh cấm giao dịch trong ngày “30-” đối với tài khoản. Vào mùa hè 2026, Valve đã chuyển từ cơ chế đặt lại vào nửa đêm theo giờ UTC toàn cầu sang cơ chế hẹn giờ theo từng phút cho từng mặt hàng (Skin.land ↗).\n\nValve — 15 Thông báo ngày 2025 tháng 7 ↗· Phân tích CSMarketCap ↗\nBài đăng gốc & liên kết đã gửi\n\nBảo vệ giao dịch CS2 / Cửa sổ đảo chiều\n\nKiểm tra mã nguồn đã gửi ↗\n202505-14Ngày xác minh\nXác thựcSự kiện và ngày tháng đã được xác minh\nValve đăng tải cảnh báo về an ninh tài khoản liên quan đến việc rò rỉ tin nhắn SMS\n\nThông báo chính thức của Valve vào ngày 5 tháng 14, 2025, đề cập đến vấn đề bảo mật tài khoản và các công cụ xác thực qua tin nhắn SMS. Mặc dù thông báo này tập trung vào các vụ rò rỉ tin nhắn SMS và khẳng định hệ thống Steam không bị xâm nhập, nhưng nó vẫn đóng vai trò là bản cập nhật bảo mật chính thức vào ngày được công bố.\n\nValve — Lưu ý về tính bảo mật của tài khoản Steam của bạn ↗\nBài đăng gốc & liên kết đã gửi\n\nThông báo về bảo mật tài khoản\n\nKiểm tra mã nguồn đã gửi ↗\n202410-02Ngày xác minh\nGiao dịchSự kiện và ngày tháng đã được xác minh\nBảy ngày trước khi tiến hành giao dịch lại hoặc tiếp thị lại\n\nBản ghi chú cập nhật bao gồm các vật phẩm được mua qua cửa hàng trong trò chơi, bao gồm Kho vũ khí, các đề nghị trao đổi và Chợ cộng đồng. Phạm vi được đề cập trong tài liệu này rộng hơn so với chỉ riêng các vật phẩm trong Kho vũ khí.\n\nValve — Ghi chú phát hành cho phiên bản 10/2/2024 ↗\nBài đăng gốc & liên kết đã gửi\n\nCS2 The Armory / Ngày thi đấu tại 7-\n\nKiểm tra mã nguồn đã gửi ↗\n202409-18Ngày nộp\nGiao dịchĐã được xác minh một phần\nCác hạn chế đối với thiết bị mới đã được xác minh trên Trang Hỗ trợ\n\nTài liệu hỗ trợ chính thức của Steam xác nhận có hạn chế giao dịch trong ngày (7-) khi đăng nhập từ một thiết bị mới chưa được ủy quyền trong ít nhất 7 ngày. Mặc dù ngày triển khai chính xác vào tháng 9 18, 2024, không được ghi nhận là một mốc quan trọng trong nhật ký thay đổi, nhưng tính năng này đã được ghi chép đầy đủ.\n\nSteam Hỗ trợ — Các hạn chế về giao dịch và thị trường ↗\nBài đăng gốc & liên kết đã gửi\n\nHạn chế giao dịch khi đăng nhập bằng thiết bị mới\n\nKiểm tra mã nguồn đã gửi ↗\n202402-14Ngày nộp\nCộng đồngĐã được xác minh một phần\nThời gian chờ khi đổi tên đã được triển khai trong bản vá “2024”\n\nCác ghi chép từ cộng đồng và nhà phát triển xác nhận rằng vào đầu năm 2024, Valve đã áp dụng một quy định chưa được công bố 2-với thời gian chờ giao dịch4 ngay sau khi thay đổi tên hồ sơ, nhằm hạn chế các vụ lừa đảo mạo danh diễn ra nhanh chóng. Do Valve không công bố bất kỳ thông cáo báo chí chính thức, bản ghi thay đổi của ứng dụng hay bài viết hỗ trợ nào về hạn chế này, nên ngày 14 được đề cập trong tháng 2 thiếu sự xác minh chính thức; hướng dẫn trên Steam Workshop đóng vai trò là bằng chứng gián tiếp từ cộng đồng chứ không phải là tài liệu chính thức Valve.\n\nSteam Hướng dẫn hội thảo (xác nhận gián tiếp) — Chi tiết về hạn chế thay đổi tên ↗\nBài đăng gốc & liên kết đã gửi\n\nTạm ngưng thay đổi tên hồ sơ / ảnh đại diện\n\nKiểm tra mã nguồn đã gửi ↗\n202312-04Ngày xác minh\nAPISự kiện và ngày tháng đã được xác minh\nViệc tạo khóa yêu cầu xác nhận qua điện thoại di động\n\nViệc áp dụng quy định bắt buộc phải xác nhận qua ứng dụng Steam Guard khi tạo khóa trên trang web API đã được xác nhận là diễn ra vào cuối tháng 2023,, theo ghi nhận từ các thư viện phát triển của bên thứ ba. Ngày chính xác là 4, 2023,, đây là khoảng thời gian triển khai được ghi nhận trong cộng đồng các nhà phát triển.\n\nTài liệu dành cho người duy trì — Tháng 3 năm 2024 ↗đã lưu trữ 2026-09-24 ↗\nBài đăng gốc & liên kết đã gửi\n\nXác nhận qua điện thoại di động cho các khóa API\n\nKiểm tra mã nguồn đã gửi ↗\n202310-24Ngày xác minh\nNhà phát triểnSự kiện và ngày tháng đã được xác minh\nQuy định bắt buộc về việc sử dụng FA “2” để thiết lập các phiên bản trò chơi trực tiếp sẽ có hiệu lực\n\nThông báo chính thức về Steamworks của Valve vào ngày 10 tháng 10, 2023, xác nhận rằng, bắt đầu từ ngày 10 tháng 24, 2023,, bất kỳ tài khoản nào đưa bản dựng vào trạng thái hoạt động trên nhánh mặc định của một ứng dụng đã phát hành đều phải xác thực thay đổi này qua tin nhắn SMS hoặc ứng dụng di động Steam. Thay đổi này đã được cập nhật trực tiếp lên trang web SetAppBuildLive API.\n\nSteamworks — Các cải tiến về bảo mật trong việc quản lý các bản dựng và người dùng ↗đã lưu trữ 2025-12-03 ↗\nBài đăng gốc & liên kết đã gửi\n\nXác thực hai yếu tố qua tin nhắn SMS (SMS MFA) cho việc phát hành các phiên bản trò chơi\n\nKiểm tra mã nguồn đã gửi ↗\n202307-12Ngày nộp\nCộng đồngĐã được xác minh một phần\nCác cảnh báo về nội dung trong tiểu sử cá nhân được cộng đồng ghi nhận\n\nSteam Các báo cáo từ cộng đồng bắt đầu từ tháng 7 2023 cho thấy các phần giới thiệu hồ sơ cá nhân chứa liên kết bên ngoài hoặc từ khóa nhạy cảm đã bắt đầu hiển thị các cảnh báo nội dung tự động. Ngày gửi báo cáo là tháng 7 12, 2023, trùng khớp với đợt báo cáo đầu tiên của người dùng trên diễn đàn cộng đồng Steam.\n\nSteam Diễn đàn cộng đồng — Báo cáo cảnh báo về nội dung liên quan đến sinh học ↗\nBài đăng gốc & liên kết đã gửi\n\nCảnh báo về nội dung tiểu sử tùy chỉnh\n\nKiểm tra mã nguồn đã gửi ↗\n202301-25Ngày nộp\nCộng đồngĐã được xác minh một phần\nChế độ lọc liên kết hồ sơ và thời gian chờ chỉnh sửa đang hoạt động\n\nTài liệu hỗ trợ chính thức của Steam xác nhận rằng các liên kết trong phần tiểu sử tùy chỉnh sẽ bị lọc, và việc thay đổi tên hoặc ảnh đại diện mang tính lạm dụng có thể dẫn đến lệnh cấm chỉnh sửa. Mặc dù việc triển khai chính thức thời gian chờ 1 giờ 4-vào ngày 1 tháng 25, 2023, được xem là thời điểm bắt đầu được ghi nhận, nhưng cơ chế lọc liên kết này đã hoạt động đầy đủ trên trang trợ giúp đã được gửi.\n\nSteam Hỗ trợ — Các quy định về tên hồ sơ và ảnh đại diện ↗\nBài đăng gốc & liên kết đã gửi\n\nLiên kết hồ sơ ĐÃ BỊ XÓA / Thời gian hồi chiêu\n\nKiểm tra mã nguồn đã gửi ↗\n202210-24Ngày xác minh\nXác thựcSự kiện và ngày tháng đã được xác minh\nSteam Quá trình chuyển đổi của khách hàng sang mã thông báo làm mới và mã thông báo truy cập OAuth\n\nCác bản cập nhật lớn về ứng dụng khách và ứng dụng di động của Valve trong tháng 10 2022 đã tiến hành cải tổ hệ thống xác thực Steam. Cấu trúc cookie phiên cũ đã được thay thế bằng các mã thông báo truy cập và làm mới dựa trên OAuth, đồng thời danh sách các thiết bị được ủy quyền đang hoạt động cũng được giới thiệu để cho phép thu hồi thủ công các phiên đang hoạt động.\n\nValve — Cập nhật ứng dụng di động “Steam” và cải tiến toàn diện hệ thống xác thực ↗\nBài đăng gốc & liên kết đã gửi\n\nSteam Cải tiến quy trình đăng nhập / Cắt ngắn cookie\n\nXem thông báo về cuộc thi “Valve” ↗\n202210-12Ngày xác minh\nXác thựcSự kiện và ngày tháng đã được xác minh\nĐăng nhập qua mã QR và quản lý thiết bị được ủy quyền\n\nThông báo vào tháng 10 của Valve về “12” mô tả quy trình đăng nhập bằng mã QR, việc chấp thuận hoặc từ chối các lần đăng nhập, cũng như danh sách thiết bị có thể thu hồi quyền truy cập tài khoản.\n\nValve — Ứng dụng di động “Steam” phiên bản cập nhật hiện đã có sẵn ↗\nBài đăng gốc & liên kết đã gửi\n\nSteam Ứng dụng di động 3.0 / Đăng nhập bằng mã QR\n\nKiểm tra mã nguồn đã gửi ↗\n202205-10Ngày nộp\nAPIĐã được xác minh một phần\nCác điểm cuối hủy giao dịch đã bị xóa khỏi danh sách công khai API\n\nCác bản ghi của nhà phát triển xác nhận rằng vào tháng 5 năm 2022, Valve, các điểm cuối quản lý giao dịch như IEconService/CancelTradeOffer và DeclineTradeOffer đã bị gỡ bỏ một cách âm thầm khỏi Web API (được ghi chép trong node-steam-tradeoffer-manager #325). Mặc dù các phương thức này vẫn hoạt động trong các giao thức khách hàng riêng tư, nhưng ngày 5 tháng 10, 2022, đánh dấu thời điểm chúng chính thức bị loại bỏ khỏi các API Web công khai nhằm chống lại các bảng lừa đảo.\n\nThảo luận của các nhà phát triển — Vấn đề số325 (Đã loại bỏ tính năng CancelTradeOffer) ↗· Trang web Steamworks API — Tài liệu hướng dẫn IEconService ↗\nBài đăng gốc & liên kết đã gửi\n\nLoại bỏ các điểm cuối hủy giao dịch\n\nXem chi tiết vấn đề #325 liên quan đến node-steam-tradeoffer-manager ↗\n202005-25Ngày xác minh\nGiao dịchSự kiện và ngày tháng đã được xác minh\nCác vật phẩm trong chế độ “2” của Dota sẽ có thời gian chờ giao dịch là bảy ngày\n\nVào ngày 25, 2020, cùng với việc ra mắt Battle Pass của giải đấu The International 10 (blog.dota2.com/2020/05/the-international-10-battle-pass/), Valve đã áp dụng chính sách khóa giao dịch trong ngày 7-đối với các vật phẩm Dota 2, tương tự như chính sách của 2018 dành cho Counter-Strike. Hạn chế này áp dụng cho tất cả các vật phẩm được giao dịch và mua từ Thị trường.\n\nCộng đồng Dota2 — Chức năng Khóa giao dịch và Bản cập nhật ứng dụng TI10 ↗\nBài đăng gốc & liên kết đã gửi\n\nDota 2 / 7-Khóa giao dịch trong ngày\n\nKiểm tra mã nguồn đã gửi ↗\n201803-29Ngày xác minh\nGiao dịchSự kiện và ngày tháng đã được xác minh\nCác vật phẩm CS:GO được trao đổi sẽ phải chịu thời gian chờ 7 ngày\n\nBản ghi chú phát hành chính thức đã xác nhận ngày phát hành và các hạn chế. Đường dẫn được cung cấp đã chuyển hướng đến bản cập nhật bản đồ tại 2013; đường dẫn tương ứng trong bản ghi chú phát hành kết thúc bằng 20309.\n\nValve — Ghi chú phát hành cho phiên bản 3/29/2018 ↗\nBài đăng gốc & liên kết đã gửi\n\nCS:GO / Khóa giao dịch trong ngày “7-”\n\nKiểm tra mã nguồn đã gửi ↗ đã lưu trữ 2025-02-26 ↗\n\nHãy dựa vào bằng chứng. Kiểm tra nguồn thông tin.\n\nQuay lại cuộc điều tra ↗",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Lịch sử phát triển bảo mật — Từ “2018” đến “2026”"
          },
          {
            "level": 2,
            "id": null,
            "text": "Thứ tự thời gian"
          },
          {
            "level": 2,
            "id": null,
            "text": "Cảnh báo về tin nhắn đáng ngờ trong các cuộc trò chuyện nhóm"
          },
          {
            "level": 2,
            "id": null,
            "text": "Quyền truy cập chi tiết và danh sách trắng IP cho các khóa nhà xuất bản (Thông báo trên Valve)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Các giao dịch CS2 có được khoảng thời gian đảo chiều trong bảy ngày"
          },
          {
            "level": 2,
            "id": null,
            "text": "Valve đăng tải cảnh báo về an ninh tài khoản liên quan đến việc rò rỉ tin nhắn SMS"
          },
          {
            "level": 2,
            "id": null,
            "text": "Bảy ngày trước khi tiến hành giao dịch lại hoặc tiếp thị lại"
          },
          {
            "level": 2,
            "id": null,
            "text": "Các hạn chế đối với thiết bị mới đã được xác minh trên Trang Hỗ trợ"
          },
          {
            "level": 2,
            "id": null,
            "text": "Thời gian chờ khi đổi tên đã được triển khai trong bản vá “2024”"
          },
          {
            "level": 2,
            "id": null,
            "text": "Việc tạo khóa yêu cầu xác nhận qua điện thoại di động"
          },
          {
            "level": 2,
            "id": null,
            "text": "Quy định bắt buộc về việc sử dụng FA “2” để thiết lập các phiên bản trò chơi trực tiếp sẽ có hiệu lực"
          },
          {
            "level": 2,
            "id": null,
            "text": "Các cảnh báo về nội dung trong tiểu sử cá nhân được cộng đồng ghi nhận"
          },
          {
            "level": 2,
            "id": null,
            "text": "Chế độ lọc liên kết hồ sơ và thời gian chờ chỉnh sửa đang hoạt động"
          },
          {
            "level": 2,
            "id": null,
            "text": "Steam Quá trình chuyển đổi của khách hàng sang mã thông báo làm mới và mã thông báo truy cập OAuth"
          },
          {
            "level": 2,
            "id": null,
            "text": "Đăng nhập qua mã QR và quản lý thiết bị được ủy quyền"
          },
          {
            "level": 2,
            "id": null,
            "text": "Các điểm cuối hủy giao dịch đã bị xóa khỏi danh sách công khai API"
          },
          {
            "level": 2,
            "id": null,
            "text": "Các vật phẩm trong chế độ “2” của Dota sẽ có thời gian chờ giao dịch là bảy ngày"
          },
          {
            "level": 2,
            "id": null,
            "text": "Các vật phẩm CS:GO được trao đổi sẽ phải chịu thời gian chờ 7 ngày"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/vi/#briefing-heading",
          "https://steamcommunity.com/groups/SteamClientBeta?l=english",
          "http://web.archive.org/web/20260313235409/https://steamcommunity.com/groups/SteamClientBeta?l=english",
          "https://store.steampowered.com/news/posts/?enddate=1788390000",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/493839547938902179",
          "https://partner.steamgames.com/doc/webapi_overview/auth",
          "https://csmarketcap.com/blog/market-insights/from-boom-to-bust-cs2s-trade-protection-impact",
          "https://skinvault.gg/blog/cs2-trade-protection-explained/",
          "https://skin.land/blog/steam-changes-cs2-trade-ban-logic-timing/",
          "https://store.steampowered.com/news/posts/?appids=730&amp;enddate=1753924057&amp;feed=steam_announce%2F1000",
          "https://help.steampowered.com/faqs/view/3041-A87A-E5F6-B6AC",
          "https://store.steampowered.com/news/posts/?enddate=1747349559",
          "https://steamcommunity.com/ogg/593110/announcements/detail/533224478739530146",
          "https://store.steampowered.com/news/posts/?appids=730&amp;enddate=1728000977&amp;feed=steam_community_announcements",
          "https://steamcommunity.com/games/CSGO/announcements/detail/4447966961421256740",
          "https://help.steampowered.com/faqs/view/7F77-9E92-31E0-6B8E",
          "https://steamcommunity.com/sharedfiles/filedetails/?id=2926756889",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "http://web.archive.org/web/20260924181824/https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens",
          "https://steamcommunity.com/dev/apikey",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3749866608167579206",
          "http://web.archive.org/web/20251203174259/https://steamcommunity.com/groups/steamworks/announcements/detail/3749866608167579206",
          "https://steamcommunity.com/groups/steamworks/announcements/detail/3734103130194459461",
          "https://steamcommunity.com/discussions/forum/1/3807266184852932971/",
          "https://help.steampowered.com/faqs/view/225C-C51E-B8F0-55B2",
          "https://store.steampowered.com/news/group/4/view/3314112260640237775",
          "https://store.steampowered.com/news/posts/?appgroupname=Keep+in+touch&amp;enddate=1666122699&amp;feed=steam_blog",
          "https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/issues/325",
          "https://partner.steamgames.com/doc/webapi/IEconService",
          "https://steamcommunity.com/app/570/announcements/",
          "https://blog.dota2.com/2020/05/trading-cooldown/",
          "https://blog.counter-strike.net/2018/03/20309/",
          "https://blog.counter-strike.net/index.php/2018/03/20308/",
          "http://web.archive.org/web/20250226114333/https://blog.counter-strike.net/index.php/2018/03/20308/",
          "https://phishdestroy.io/steam_dossier/vi/#vulnerability-profile"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/vi/security_timeline.content.json",
      "export_json_sha256": "46084aea70b9a48a90bdde5bcdc159bcb2a7b108be8c0b7f0096d74a89879b57"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "vi/skin_atlas.html",
      "language": "vi",
      "title": "Tập bản đồ về những thứ mà “Steam” không thể mang theo — Hồ sơ “Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/vi/skin_atlas",
      "source_html_sha256": "bf5d38f648e23523787dcdc2e090b835ca4c97add97d863242dab72ce0aafd5e",
      "exported_at": "2026-09-29T00:23:07.907Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [
          {
            "id": "gallery",
            "source": "https://phishdestroy.io/steam_dossier/vi/skin_atlas#gallery"
          }
        ],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "skin_atlas.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/vi/skin_atlas.pdf?v=print-20260929-v5",
        "sha256": "6b0c125cdfecf66542a6028b3757206701cb9fcb82a505c00dde3e8da3bd7405",
        "bytes": 187184,
        "pages": 14
      },
      "integrity": {
        "signed_object": "skin_atlas.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "skin_atlas.content.json.asc",
        "digest_file": "skin_atlas.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify skin_atlas.content.json.asc skin_atlas.content.json",
          "sha256sum -c skin_atlas.content.json.sha256"
        ]
      },
      "content": {
        "text": "PHỤ LỤC IV-B / BẢNG GIÁ / 2026-09-23\nBản đồ thang giá Skin — Vách đá thanh khoản\n\nCác điểm dừng tại chợ của Valve nơi tiền bắt đầu.\n\nPHẦN NÀY CHỨNG MINH ĐIỀU GÌ\n\nTập bản đồ trực quan này phân tích các danh mục sản phẩm “30,266” trên năm danh mục sản phẩm của các sàn thương mại điện tử, đánh giá mức độ bao phủ thị trường ở cả hai mức trên và dưới ngưỡng niêm yết của Valve. Dưới ngưỡng $1,800, Steam lưu trữ 95.3% danh mục đang hoạt động; ngay trên ngưỡng này, phạm vi bao phủ chính thức giảm mạnh xuống còn 1.9% (với phạm vi bao phủ 0.0% trên các tài sản đã được xác minh). Điều này cho thấy một “vách đá thanh khoản” đột ngột và mang tính cấu trúc, trong đó Valve ủy quyền việc khám phá các giao dịch giá trị cao cho các nền tảng bên ngoài trong khi vẫn giữ toàn quyền kiểm soát việc lưu ký tài sản cơ sở.\n\n← Quay lại Bản tóm tắt dành cho lãnh đạo\n\nMỗi mặt hàng CS2 có giá niêm yết thực tế trên năm sàn giao dịch đều được phân loại vào một khoảng giá dựa trên mức giá chào bán thấp nhất, và mỗi khoảng giá được đánh giá dựa trên một tiêu chí duy nhất: tỷ lệ phần trăm mà Chợ Cộng đồng (Community Market) của Valve vẫn đang nắm giữ. Dưới mức giới hạn số lượng niêm yết của Valve, câu trả lời là 95.3%. Phía trên đó, câu trả lời là 1.9%. Mức giảm này không diễn ra từ từ và cũng không giảm theo nơi nào nhu cầu giảm — mà giảm chính xác theo quy định đã công bố. Trong số các 248 các danh mục sản phẩm mà hai hoặc nhiều sàn thương mại điện tử tự đặt giá cao hơn mức trần, 100.0% hoàn toàn không có bất kỳ danh sách nào trên Steam.\n\nXem vách đá ↓Mở thư viện các sản phẩm “419”Phương pháp và giới hạn\n30,266các danh mục mặt hàng được đo lường\n95.3%các mặt hàng dưới mức vốn chủ sở hữu do Công ty Cổ phần Ngân hàng Thương mại Quốc tế (Steam) nắm giữ\n1.9%các mặt hàng vượt mức trần do Steam cung cấp\n$78.6Mgiá trị sàn của tập hợp đã được xác nhận\n01 / phép đo\nQuy tắc được áp dụng một cách cứng nhắc, chứ không phải theo yêu cầu\n\nMỗi danh mục sản phẩm “30,266” dưới đây được phân loại vào một nhóm dựa trên rẻ nhất Khảo sát trực tiếp được thực hiện trên các nền tảng BUFF163, CSFloat, Skinport, YouPin 898 và C5Game; chỉ những mặt hàng được đề cập trên ít nhất hai trong số các nền tảng này mới được tính vào kết quả, do đó không có trường hợp niêm yết nào dù lạc quan đến đâu cũng có thể “phù phép” ra một thành viên ban nhạc. Bảng trên thể hiện tỷ lệ thị phần mà thị trường riêng của Valve vẫn đang nắm giữ đối với từng ban nhạc.\n\nTỷ trọng của từng mức giá tại Chợ Cộng đồng Steam\nphần trên: phạm vi phủ sóng hơi nước · phần dưới: số lượng vật phẩm trên mỗi dải, thang đo lôgarit\n0%\n25%\n50%\n75%\n100%\n100%\n96.9%\n95.9%\n97.3%\n91.1%\n76.8%\n14.5%\n2.9%\n1.5%\n0%\n0%\n0%\n4,632\n1¢–10¢\n7,152\n10¢–$1\n8,568\n$1–10\n5,941\n$10–100\n2,329\n$100–300\n1,292\n$300–1k\n193\n$1k–1.8k\n70\n$1.8k–3k\n67\n$3k–10k\n18\n$10k–30k\n3\n$30k–100k\n1\n$100k+\nitems\nlog\nVALVE’S LISTING CAP\nbằng hoặc thấp hơn mức trần niêm yết của Valvevượt quá mức trần — Quy định của Ủy ban Chứng khoán và Giao dịch Hoa Kỳ (Valve) cấm niêm yếtcác danh mục sản phẩm trong ban nhạc\n\n“Phạm vi bao phủ” có nghĩa là tại thời điểm thu thập dữ liệu, đã có một yêu cầu trực tiếp từ Steam cho danh mục đó. Biểu đồ phía dưới được vẽ theo thang logarit vì hầu hết các mặt hàng trong danh mục đều có giá rất rẻ: nếu đọc theo thang tuyến tính, mọi dải giá trên mức $300 sẽ bị san phẳng xuống đường cơ sở.\n\nHình dạng đó loại trừ điều gì\n\nNếu các mặt hàng đắt tiền chỉ đơn thuần là không được ưa chuộng, mức tiêu thụ sẽ giảm dần khi giá tăng. Nhưng thực tế không phải vậy. Mức tiêu thụ duy trì ổn định ở mức 76.8% trong khoảng giá từ $300–$1k, sau đó sụt giảm mạnh xuống 14.5% trong khoảng giá ngay dưới mức trần và 2.9% trong khoảng giá ngay trên mức trần đó. Hiệu ứng cầu không biết mức trần được đặt ở đâu Valve. Còn quy luật thì biết.\n\nPhạm vi giá\tDanh mục sản phẩm\tVới câu hỏi trực tiếp trên Steam\tSteam phạm vi bảo hiểm\tCác bản sao được liệt kê trên trang web Steam\n1¢–10¢\t4,632\t4,632\t100%\t8,223,227\n10¢–$1\t7,152\t6,931\t96.9%\t5,488,315\n$1–10\t8,568\t8,213\t95.9%\t3,939,538\n$10–100\t5,941\t5,780\t97.3%\t1,328,255\n$100–300\t2,329\t2,121\t91.1%\t364,466\n$300–1k\t1,292\t992\t76.8%\t187,504\n$1k–1.8k\t193\t28\t14.5%\t40,281\n$1.8k–3k\t70\t2\t2.9%\t9,592\n$3k–10k\t67\t1\t1.5%\t6,706\n$10k–30k\t18\t0\t0%\t1,366\n$30k–100k\t3\t0\t0%\t21\n$100k+\t1\t0\t0%\t2\n\nCác biến thể về mô hình và giai đoạn không được tính vào bảng xếp hạng này: Steam không liệt kê bậc “đá quý xanh” hay giai đoạn “Ruby” như một mục riêng biệt trên thị trường, do đó việc tính chúng vào sẽ làm giảm mức độ bao quát của Steam. Nếu tính toán mà không áp dụng yêu cầu về hai nền tảng thương mại điện tử, cùng một bảng xếp hạng sẽ cho kết quả là 79.1% dưới mức trần và 6.5% trên mức trần đối với các mặt hàng trên 37,204 — một khoảng cách rõ rệt hơn, dựa trên bằng chứng yếu hơn, đó là lý do tại sao con số này không được trích dẫn.\n\n02 / chấm điểm dựa trên bằng chứng\nGiá chào bán không phải là giá\n\nBất kỳ ai cũng có thể rao bán một chiếc P2000 với giá khoảng mười triệu nhân dân tệ. Trước khi một con số trên trang này được sử dụng cho bất kỳ mục đích nào, nó sẽ được phân loại dựa trên số lượng sàn giao dịch độc lập đưa ra mức giá cho mặt hàng đó cao hơn mức trần và mức độ tập trung của các mức giá đó. Chỉ các hạng A và B mới được đưa ra — tại đây hoặc bất kỳ đâu khác trong hồ sơ này.\n\nA  Có ba kệ trở lên phù hợp\n\nCó ba sàn thương mại điện tử trở lên niêm yết sản phẩm này với mức giá cao hơn mức trần và giá trung vị của chúng nằm trong khoảng 25% so với mức giá rẻ nhất. 197 danh mục, 18,218 bản sao, $76,585,587.\n\nKhông có mặt trong bộ phim “Steam”: 100.0%.\n\nB  Hai kệ giống nhau\n\nHai sàn giao dịch đạt thỏa thuận ở mức cao hơn mức trần, hoặc ba sàn đạt thỏa thuận với mức chênh lệch nhỏ hơn. 51 danh mục, 176 bản sao, $2,038,814.\n\nKhông có mặt trong bộ phim “Steam”: 100.0%.\n\nC  Một kệ — chưa sử dụng\n\nChỉ có một sàn giao dịch duy nhất niêm yết mức giá bán cao hơn mức trần. 171 các danh mục, 247 bản sao. Được hiển thị trong thư viện để đảm bảo tính đầy đủ và không được tính vào bất kỳ tổng nào trên trang này.\n\nĐây là những yêu cầu báo giá, chứ không phải bằng chứng về mức giá.\n\nChi phí của đợt điều chỉnh này là bao nhiêu, và nó đã mang lại những gì\n\nViệc loại bỏ hạng C sẽ loại bỏ các danh mục “171” và $3,825,125 khỏi tiêu đề. Phần còn lại sẽ ngắn gọn hơn và khó phản bác hơn rất nhiều: 248 các danh mục, 18,394 các bản được liệt kê, $78,624,401, và 100.0% trong số đó — từng bản một — đều không có mặt trên thị trường của Valve. Các hàng thuộc loại C chính là nguyên nhân khiến số liệu thay đổi; chúng được liệt kê ra chứ không bị ẩn đi.\n\nCác mục được dành riêng làm hiện vật\n\nBất kỳ mức giá nào cao hơn gấp ba lần mức giá chào bán rẻ nhất cho cùng một mặt hàng sẽ bị loại bỏ. Khi quy đổi theo tỷ giá mà chính dữ liệu đó ngụ ý, hầu hết các con số này đều là các số tròn tính bằng CNY — đây là dấu hiệu cho thấy đó là giá tạm thời hoặc mức trần của nền tảng, chứ không phải là một đề nghị thực sự. Bởi vì mọi tổng số trên trang này đều sử dụng rẻ nhất Hãy lưu ý rằng, không một nhân vật nào trong số này từng thổi phồng con số nào cả; họ bị loại trừ để không ai trong số họ có thể được trích dẫn làm tiêu đề.\n\nMặt hàng\tYêu cầu trực tiếp rẻ nhất\tĐể riêng ra\nSouvenir P2000 | Wicked Sick (Minimal Wear)\t$148,954\t$1,489,543\n★ Specialist Gloves | Crimson Kimono (Minimal Wear) | Phase 1\t$37,239\t$119,163\nSouvenir USP-S | Printstream (Factory New)\t$2,000\t$59,582\n★ Bowie Knife | Crimson Web (Factory New)\t$2,957\t$43,030\n★ Karambit | Marble Fade (Factory New) | 1st\t$11,916\t$38,874\nSticker | Ninjas in Pyjamas (Holo) | Katowice 2014\t$5,000\t$31,748\nSouvenir AWP | Dragon Lore (Battle-Scarred)\t$4,225\t$29,157\n★ Karambit | Doppler (Minimal Wear) | Ruby\t$7,122\t$27,273\nTất cả các danh mục “419”, kèm theo đối tượng mà mỗi mức giá đề cập đến\n\nNguồn: https://phishdestroy.io/steam_dossier/vi/skin_atlas#gallery\n\n04 / nó đã đi đâu thay vào đó\nNhững kệ hàng chứa những thứ mà “Steam” sẽ không bao giờ có\n\nCác danh sách giống nhau, được phân nhóm theo sàn giao dịch sở hữu chúng. Đây là số lượng bản sao hiện có được liệt kê, điều này không giống với nơi mà chúng thuộc sở hữu và ở đây cũng không được hiểu theo nghĩa đó.\n\nGiá sàn của các danh sách niêm yết vượt mức trần, theo sàn giao dịch\ngiá chào bán thấp nhất x bản được bày trên kệ đó\nYouPin 898\n$22,720,252\nBUFF163\n$22,022,606\nC5Game\n$12,560,543\nCSFloat\n$10,871,845\nSkinport\n$1,385,060\n\nCác khu vực pháp lý, theo thứ tự nêu trên: YouPin 898 — Trung Quốc · BUFF163 — Trung Quốc · C5Game — Trung Quốc · CSFloat — Hoa Kỳ · Skinport — Đức / Malta. Một mặt hàng vật lý có thể được niêm yết trên nhiều kệ trong số này, do đó các con số này không được cộng dồn với tổng số của bất kỳ thị trường nào khác.\n\nGiá sàn theo mức giá\ntiền được phân bổ như thế nào khi vượt quá mức trần\n$1.8k-3k\n$9,842,391\n$3k-10k\n$36,787,269\n$10k-50k\n$20,038,749\nover $50k\n$2,891,897\n05 / sự khan hiếm mà bạn có thể đếm được\nThực tế, nguồn cung khan hiếm đến mức nào\n\nMỗi mặt hàng CS2 đều có một chỉ số độ hiếm, và các sàn giao dịch công bố số lượng bản sao thuộc từng mức độ hiếm đó. Điều này biến từ “hiếm” từ một tính từ thành một con số — và chính con số đó giải thích tại sao chỉ một tài khoản bị xâm nhập cũng đủ để đáng để đầu tư vào một bộ công cụ lừa đảo được thiết kế riêng.\n\nAWP | Truyền thuyết về Rồng\n150 đang rao bán · giá từ $11,350\n0.00–0.01\n29 · $14,730\n0.01–0.02\n54 · $11,618\n0.02–0.03\n26 · $11,350\n0.03–0.04\n25 · $11,618\n0.04–0.07\n16 · $11,585\n\nAWP | Dragon Lore (Mới nguyên hộp)\n\nM4A4 | Tiếng hú\n105 đang rao bán · giá từ $6,628\n0.00–0.01\n11 · $10,725\n0.01–0.02\n14 · $8,088\n0.02–0.03\n11 · $7,580\n0.03–0.04\n19 · $6,703\n0.04–0.07\n50 · $6,628\n\nM4A4 | Howl (Mới nguyên hộp)\n\nAK-47 | Hoa sen hoang dã\n113 đang rao bán · giá từ $14,373\n0.00–0.01\n25 · $22,343\n0.01–0.02\n11 · $19,364\n0.02–0.03\n3 · $19,645\n0.03–0.04\n15 · $15,044\n0.04–0.07\n59 · $14,373\n\nAK-47 | Wild Lotus (Mới nguyên hộp)\n\nAWP | Gungnir\n173 đang rao bán · từ11,618\n0.00–0.01\n28 · $17,875\n0.01–0.02\n21 · $13,600\n0.02–0.03\n32 · $12,065\n0.03–0.04\n29 · $11,735\n0.04–0.07\n63 · $11,618\n\nAWP | Gungnir (Mới nguyên hộp)\n\nAK-47 | Rắn Lửa\n278 đang rao bán · giá từ $663\n0.15–0.18\n87 · $730\n0.18–0.21\n49 · $712\n0.21–0.24\n52 · $703\n0.24–0.27\n18 · $715\n0.27–0.38\n72 · $663\n\nAK-47 | Rắn Lửa (Đã thử nghiệm thực địa)\n\nLớp bề mặt được tôi cứng (tất cả các cấp độ / đá quý màu xanh)\n76 đang rao bán · từ1,638 USD\n0.07–0.08\n1 · $2,516\n0.08–0.09\n4 · $2,482\n0.09–0.10\n6 · $3,856\n0.10–0.11\n7 · $2,797\n0.11–0.15\n58 · $1,638\n\nAK-47 | Thân súng được tôi cứng (mức mòn tối thiểu) | Cấp độ1\n\nCác dải giá là các khoảng thanh khoản riêng của sàn giao dịch; chỉ những dải giá có ít nhất một lệnh đang hoạt động mới được đưa vào. Giá bên cạnh mỗi thanh biểu đồ là mức giá chào bán trực tiếp thấp nhất trong dải giá đó, do đó mức chênh lệch đi kèm với lượng thanh khoản thấp có thể được nhận biết trực tiếp thay vì phải xác định bằng cách tính toán.\n\n06 / chuyển động, được đo từ Steam\nNhững gì các kệ hàng của bên thứ ba thực sự đã mang lại\n\nValve không công bố bất kỳ dữ liệu lịch sử nào có thể sử dụng được ở cấp độ này, và tài liệu này cũng không đề cập đến điều đó. Skinport thực sự công bố các giao dịch đã hoàn tất của chính mình trong khoảng thời gian 24 giờ gần nhất, 7, 30 và 90 ngày gần nhất, và đó là toàn bộ chiều thời gian có sẵn tại đây: giá thực tế trung vị cho mỗi khoảng thời gian gần nhất, được chỉ số hóa sao cho giá trung vị của ngày 90-là 100. Cả hai biểu đồ này đều không sử dụng dữ liệu từ Steam.\n\nGiá thực tế trung vị, theo khoảng thời gian gần nhất\nđược chỉ số hóa theo giá trị trung vị hàng ngày của Chỉ số Giá Tiêu dùng (90-) · 6,758 các mặt hàng có 20+ doanh số\n85\n91\n97\n103\n100\n90d\n94\n30d\n90\n7d\n88\n24h\nDoanh số bán hàng đã hoàn tất mỗi ngày\ncác mục giống nhau, các cửa sổ giống nhau\n7,621\n9,653\n11,684\n13,716\n12,700\n90d\n11,894\n30d\n9,540\n7d\n8,637\n24h\n\nĐây là hai biểu đồ riêng biệt chứ không phải một biểu đồ có hai thang đo dọc: chỉ số và số lượng giao dịch hàng ngày không có cùng đơn vị, và việc vẽ chúng trên cùng một trục sẽ dẫn đến so sánh không hợp lý. Các khoảng thời gian được lồng ghép và trượt theo thời gian — số liệu theo ngày 90-bao gồm số liệu theo giờ 24-— do đó đây không phải là chuỗi dữ liệu hàng ngày và không được hiểu theo cách đó. Điều mà dữ liệu này chứng minh là rất hẹp và được nêu rõ ràng: trong các khoảng thời gian trôi qua Skinport đã công bố, giá thực tế trung vị nằm dưới mức trung vị hàng ngày của chính nó 90-và số lượng giao dịch hàng ngày cũng giảm theo.\n\nSkinport doanh số thực tế. Các khoảng thời gian được lồng ghép và trượt theo thời gian, do đó mỗi điểm dữ liệu là giá trung vị thực tế trong khoảng thời gian trượt đó, được quy chuẩn theo giá trung vị của ngày 90-. Đây không phải là chuỗi dữ liệu hàng ngày và không liên quan đến dữ liệu Steam.\n\n07 / được làm từ chất liệu gì\nNhững miếng dán đã dùng được 16 năm và một nắm găng tay\n\nNhóm sản phẩm ở phân khúc cao cấp không đại diện cho phần lớn thị trường. Nó tập trung vào một số mặt hàng hiếm và một số bộ sưu tập, trong đó có nhiều bộ hiện đã không còn có thể tìm mua được nữa — và đó chính là lý do tại sao nguồn cung không thể đáp ứng được mức giá.\n\nCác danh mục nằm trên mũ, theo mức độ hiếm\nsố lượng danh mục mặt hàng\nCovert\n321\nClassified\n39\nRestricted\n24\nContraband\n12\nMil-Spec Grade\n9\nConsumer Grade\n9\nIndustrial Grade\n5\nCác danh mục nằm trên phần tiêu đề, theo bộ sưu tập\n10 bộ sưu tập hàng đầu\nThe St. Marc Collection\n13\nThe Cobblestone Collection\n13\nThe Norse Collection\n12\nThe Arms Deal Collection\n9\nThe Canals Collection\n7\nThe Gods and Monsters Collection\n6\nThe Revolution Collection\n4\nThe 2021 Train Collection\n4\nThe Rising Sun Collection\n4\nThe Chop Shop Collection\n4\n\nTheo danh mục: skin 366, sticker 48, container 3, sticker_slab 2.\n\n08 / số tiền cao nhất mà bất kỳ ai từng thực sự phải trả\nMức giá cao được hỗ trợ bởi một giao dịch, chứ không phải bởi việc niêm yết\n\nTất cả các mức giá khác trên trang này là hỏi — những điều người bán mong muốn. Đó là doanh số: mức giá giao dịch cao nhất Skinport được ghi nhận cho từng mặt hàng, tính trong 90 ngày gần nhất. Đây là con số duy nhất trong hồ sơ này mà người mua thực sự đã thanh toán, và mỗi hàng đều có liên kết đến sàn giao dịch để người dùng có thể đối chiếu con số này với nguồn gốc thay vì dựa vào thông tin từ chúng tôi.\n\n21,216các mặt hàng đã hoàn tất giao dịch trong khoảng thời gian này\n106được bán với mức giá bằng hoặc cao hơn mức trần niêm yết của Valve\n$14,192giao dịch hoàn tất có giá trị cao nhất\n67/419các danh mục vượt ngưỡng có bất kỳ giao dịch bán hàng nào được ghi nhận\n30 giao dịch đã hoàn tất có giá trị cao nhất trong khoảng thời gian này\nMặt hàng\tDoanh số cao nhất\tGiá bán trung vị\tDoanh số\tGiá chào bán rẻ nhất hiện tại\tSteam\tHãy xem thử\nAWP | Gungnir (Factory New)\t$14,192\t$11,343\t5\t$11,490\tabsent\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Factory New)\t$12,387\t$12,387\t1\t$13,836\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Factory New)\t$11,779\t$11,063\t16\t$10,941\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Minimal Wear)\t$11,693\t$11,693\t1\t$9,946\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Minimal Wear)\t$10,437\t$10,437\t1\t$9,610\tabsent\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Blue Laminate (Minimal Wear)\t$9,772\t$37\t76\t$30\t$40\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Minimal Wear)\t$9,463\t$9,463\t1\t$9,500\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Minimal Wear)\t$9,104\t$9,026\t6\t$8,524\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Hedge Maze (Minimal Wear)\t$8,139\t$8,139\t1\t$6,819\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Field-Tested)\t$7,617\t$7,390\t4\t$7,194\tabsent\tSkinport CSFloat Steam\nStatTrak™ M4A4 | Howl (Field-Tested)\t$7,615\t$7,615\t1\t$7,100\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Field-Tested)\t$7,149\t$7,006\t2\t$7,165\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Field-Tested)\t$6,711\t$6,194\t15\t$5,988\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Factory New)\t$6,679\t$6,613\t3\t$6,628\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Superconductor (Factory New)\t$6,084\t$6,084\t1\t$7,969\tabsent\tSkinport CSFloat Steam\nAWP | Gungnir (Battle-Scarred)\t$5,750\t$5,413\t3\t$5,899\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Pandora's Box (Minimal Wear)\t$5,520\t$5,508\t3\t$4,998\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Vice (Factory New)\t$5,385\t$5,158\t2\t$5,700\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Minimal Wear)\t$5,342\t$4,989\t19\t$4,997\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Hedge Maze (Field-Tested)\t$5,334\t$4,862\t5\t$3,724\tabsent\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Vulcan (Factory New)\t$5,275\t$1,418\t12\t$1,280\tabsent\tSkinport CSFloat Steam\nAK-47 | Wild Lotus (Well-Worn)\t$4,978\t$4,978\t1\t$4,942\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Well-Worn)\t$4,931\t$4,931\t1\t$5,445\tabsent\tSkinport CSFloat Steam\nAK-47 | Hydroponic (Factory New)\t$4,802\t$4,351\t2\t$3,648\tabsent\tSkinport CSFloat Steam\n★ Talon Knife | Case Hardened (Minimal Wear)\t$4,588\t$466\t16\t$442\t$630\tSkinport CSFloat Steam\nAWP | Medusa (Factory New)\t$4,484\t$4,484\t1\t$4,171\tabsent\tSkinport CSFloat Steam\n★ Specialist Gloves | Pillow Punchers (Factory New)\t$4,359\t$4,359\t1\t$4,302\tabsent\tSkinport CSFloat Steam\n★ Sport Gloves | Pandora's Box (Field-Tested)\t$4,359\t$3,666\t11\t$3,245\tabsent\tSkinport CSFloat Steam\nM4A4 | Howl (Field-Tested)\t$4,289\t$4,225\t8\t$4,022\tabsent\tSkinport CSFloat Steam\nAWP | Dragon Lore (Battle-Scarred)\t$4,124\t$4,124\t1\t$4,279\tabsent\tSkinport CSFloat Steam\nCùng một mặt hàng, cùng khoảng thời gian “90”, nhưng giá cả lại chênh lệch rất lớn\n\nChỉ giới hạn ở các mặt hàng có giá trung vị là $100 và có ít nhất năm giao dịch đã hoàn tất, bởi vì với một skin giá rẻ, chỉ cần một giao dịch bất thường cũng có thể làm lệch tỷ lệ này. Những mặt hàng còn lại chủ yếu là Lớp bề mặt được tôi cứng các loại hoàn thiện, trong đó mẫu mã quyết định giá cả và thị trường phân loại mọi mẫu mã dưới một tên duy nhất — cơ chế tương tự được đo lường bằng biến float trong phần 05.\n\nMặt hàng\tGiá trị cao so với giá trị trung vị\tDoanh số cao nhất\tGiá bán trung vị\tDoanh số\tHãy xem thử\n★ Talon Knife | Case Hardened (Minimal Wear)\t+884%\t$4,588\t$466\t16\tSkinport CSFloat Steam\nDesert Eagle | Cobalt Disruption (Factory New)\t+859%\t$1,210\t$126\t115\tSkinport CSFloat Steam\nAWP | BOOM (Minimal Wear)\t+814%\t$1,232\t$135\t89\tSkinport CSFloat Steam\nAK-47 | Case Hardened (Well-Worn)\t+769%\t$1,720\t$198\t70\tSkinport CSFloat Steam\nAWP | Graphite (Factory New)\t+761%\t$1,469\t$171\t124\tSkinport CSFloat Steam\n★ Talon Knife | Case Hardened (Field-Tested)\t+509%\t$2,437\t$400\t48\tSkinport CSFloat Steam\n★ Kukri Knife | Case Hardened (Minimal Wear)\t+448%\t$723\t$132\t69\tSkinport CSFloat Steam\n★ Kukri Knife | Case Hardened (Field-Tested)\t+415%\t$549\t$106\t128\tSkinport CSFloat Steam\n★ Ursus Knife | Case Hardened (Minimal Wear)\t+371%\t$597\t$127\t12\tSkinport CSFloat Steam\nAK-47 | Case Hardened (Field-Tested)\t+369%\t$1,037\t$221\t125\tSkinport CSFloat Steam\nAK-47 | Red Laminate (Minimal Wear)\t+360%\t$552\t$120\t18\tSkinport CSFloat Steam\nAWP | Asiimov (Field-Tested)\t+351%\t$528\t$117\t439\tSkinport CSFloat Steam\nAK-47 | Vulcan (Field-Tested)\t+337%\t$865\t$198\t241\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Nightwish (Factory New)\t+322%\t$625\t$148\t31\tSkinport CSFloat Steam\nAWP | Lightning Strike (Factory New)\t+319%\t$2,065\t$493\t198\tSkinport CSFloat Steam\nStatTrak™ AWP | Redline (Minimal Wear)\t+312%\t$574\t$139\t24\tSkinport CSFloat Steam\nStatTrak™ AWP | Asiimov (Battle-Scarred)\t+287%\t$524\t$135\t37\tSkinport CSFloat Steam\nAK-47 | Redline (Minimal Wear)\t+277%\t$562\t$149\t112\tSkinport CSFloat Steam\nAWP | Crakow! (Factory New)\t+275%\t$379\t$101\t72\tSkinport CSFloat Steam\nStatTrak™ AK-47 | Vulcan (Factory New)\t+272%\t$5,275\t$1,418\t12\tSkinport CSFloat Steam\n\nĐây là mức giá cao nhất trong ngày trên trang 90-, KHÔNG phải là mức giá cao nhất mọi thời đại, và chỉ áp dụng cho MỘT sàn giao dịch. Không có con số nào được khẳng định là mức cao nhất mọi thời đại trong bất kỳ phần nào của tài liệu này. Một mặt hàng không có thông tin về giao dịch trên trang Skinport sẽ hoàn toàn không xuất hiện trong triển lãm này, đó là lý do tại sao bộ sưu tập này có quy mô nhỏ hơn so với số liệu thống kê.\n\nCác liên kết xác minh được tạo ra từ các mã định danh nền tảng của chính danh mục. Chúng trỏ đến trang sản phẩm trên từng sàn thương mại điện tử, để người đọc có thể đối chiếu hình ảnh với nguồn gốc thay vì với chúng tôi. Các liên kết ra ngoài chứa rel=\"nofollow\": đó là những trích dẫn, không phải lời ủng hộ, và một số điểm đến trong số đó là các sàn giao dịch mà cuộc điều tra này đã chỉ trích.\n\n09 / nguồn gốc và giới hạn\nNguồn gốc của điều này và những gì nó không thể thể hiện\n\nMọi số liệu trên trang này đều được tính toán lại từ hai tệp ảnh chụp nhanh, trong đó các giá trị băm được công bố kèm theo. Không có nội dung nào ở đây được sao chép từ bài viết của trang web khác.\n\nNguồn và quyền truy cập\n\ncs2.sh API, GET /v1/prices/latest và GET /v1/schema, bản chụp nhanh duy nhất, được ghi lại tại 2026-09-23T00:44:27.871388581Z, giá tính bằng USD.\n\nDữ liệu này được thu thập thông qua gói đăng ký thương mại trả phí do người yêu cầu thuộc Tổ chức Nghiên cứu và Phát triển Công nghệ (GDPR) sở hữu, được ghi chép trong kho lưu trữ, theo các điều khoản của chính nhà cung cấp. Không có nền tảng thương mại điện tử nào bị trích xuất dữ liệu và không có thông tin đăng nhập nào của bất kỳ nền tảng thương mại điện tử nào được sử dụng. Khóa của người yêu cầu được lưu trữ bên ngoài kho lưu trữ này và không xuất hiện trong bất kỳ tệp nào ở đây.\n\nĐiều kiện để một mặt hàng được công nhận\n\nMỗi mặt hàng cơ bản có ít nhất một lệnh bán đang hoạt động trên BUFF, CSFloat, Skinport, YouPin hoặc C5Game sẽ được xếp vào một khoảng giá dựa trên lệnh bán RẺ NHẤT của nó, do đó khoảng giá này không bao giờ phụ thuộc vào Steam. “Steam coverage” là tỷ lệ phần trăm các mặt hàng trong khoảng giá đó có bất kỳ lệnh bán đang hoạt động nào trên Steam tại thời điểm thu thập dữ liệu. Các biến thể mẫu và giai đoạn bị loại trừ khỏi bảng xếp hạng vì Steam không liệt kê chúng riêng biệt; việc bao gồm chúng sẽ làm giảm giá trị của Steam. Hình ảnh hiển thị là các hình ảnh danh mục của cùng các mặt hàng, được lưu trữ cục bộ.\n\nHình ảnh minh họa và quyền sở hữu hình ảnh. Các hình ảnh minh họa sản phẩm trong danh mục là hình ảnh do nhà cung cấp cung cấp cho cùng một `market_hash_name` với các dòng giá, được lưu trữ cục bộ để hiển thị ngoại tuyến và trên IPFS. Các hình ảnh minh họa này không phải là tác phẩm của PhishDestroy: tất cả hình ảnh sản phẩm, logo và ảnh chụp màn hình vẫn thuộc sở hữu của các chủ sở hữu tương ứng (cs2.sh, CSFloat, Skinport, BUFF, YouPin, C5Game, Valve và các bên khác). Chúng được sao chép duy nhất với mục đích nhận diện và báo cáo vì lợi ích công cộng; không có bất kỳ tuyên bố nào về quyền sở hữu hoặc giấy phép.\n\nNhững gì chúng tôi không thể có được\n\nGói đăng ký đang sử dụng chỉ hỗ trợ các bản chụp nhanh hiện tại. Các điểm cuối lưu trữ và lịch sử không khả dụng, và trên trang này không có bất kỳ chuỗi dữ liệu lịch sử nào được đề cập Ngoài doanh số theo mô hình cửa sổ trượt, trang Skinport tự đăng tải thông tin tại mục 06.\n\nMột ảnh chụp nhanh, không phải chuỗi thời gian. Việc không có danh sách trên Steam tại thời điểm chụp ảnh không phải là bằng chứng cho thấy mặt hàng đó sẽ không bao giờ xuất hiện ở đó; đó chỉ là tình trạng của kệ hàng tại thời điểm đó, và đối với các mức giá vượt quá giới hạn, điều này cũng tuân theo quy định đã công bố của Valve: Thị trường Cộng đồng của Valve quy định rõ ràng giới hạn danh sách ở mức $1,800 cho mỗi mặt hàng (với số dư tối đa trong Ví Steam là $2,000; xem Steam Câu hỏi thường gặp về Chợ Cộng đồng đã lưu trữ 2026-09-21 ↗ và Steam Thỏa thuận người đăng ký § 3.C đã lưu trữ 2026-09-24 ↗).\n\nChấm điểm\n\nGiá của một mặt hàng luôn là mức giá chào bán trực tiếp rẻ nhất của mặt hàng đó, do đó một giá trị ngoại lệ cao sẽ không bao giờ làm tăng tổng giá trị. Hệ thống phân loại quyết định những hàng nào được đưa vào báo giá. Bất kỳ mức giá nào cao hơn ba lần so với mức giá chào bán rẻ nhất của cùng mặt hàng đó sẽ bị loại trừ vì không phải là giá trực tiếp. Hạng A: ba sàn giao dịch trở lên vẫn niêm yết giá cao hơn mức trần và giá trung vị của chúng nằm trong khoảng 25 phần trăm so với mức giá thấp nhất. Hạng B: hai sàn giao dịch đồng ý, hoặc ba sàn đồng ý nhưng mức chênh lệch lớn hơn. Hạng C: chỉ có một mức giá niêm yết - đó là giá chào bán, không phải giá thị trường. Chỉ các hạng A và B mới được trích dẫn trong tài liệu này.\n\nQuy tắc về giá bất thường: giá chào mua > 3.0nhân với giá chào bán rẻ nhất của cùng mặt hàng đó.\n\nTại sao các tổng này là mức tối thiểu\n\nĐối với mỗi sàn thương mại điện tử, sản phẩm thấp nhất Giá chào bán được nhân với số lượng bản sao được liệt kê trên kệ. Mỗi bản sao khác ở đó đều có giá bằng hoặc cao hơn mức giá chào bán thấp nhất đó, do đó giá trị niêm yết thực tế cao hơn do bản chất của hệ thống, chứ không phải do ước tính. Đây không phải là một giao dịch bán hàng, không phải là dòng tiền, và cũng không phải là việc định giá nền kinh tế CS2.\n\nHãy tự kiểm tra xem\n\nCác bộ dữ liệu được tổng hợp làm cơ sở cho mỗi biểu đồ trên trang này đã được công bố đầy đủ: bộ dữ liệu Atlas, Màn hình phân loại và kiểm tra hiện vật, cuộc điều tra dân số cơ sở và bản kê khai kèm theo mã SHA-256 của từng bản chụp thô.\n\nMột đợt điều chỉnh được ghi nhận ngay từ đầu phiên giao dịch\n\nMột bản nháp trước đó của sổ đăng ký liên quan đã mở đầu bằng một mẫu AK-47 | Point Disarray được rao bán với giá $148,954 trên một sàn thương mại điện tử Trung Quốc, trong khi Steam niêm yết giá $119. Dòng sản phẩm này thuộc hạng C: chỉ có một kệ hàng, một bản duy nhất và không có sàn thương mại điện tử nào khác đồng ý về giá. Đây là giá chào bán, không phải giá thực tế, và nó đã bị hạ hạng cả ở đây lẫn trên trang đó. Sản phẩm dẫn đầu được xác nhận là Sticker | Titan (Holo) | Katowice 2014 tại $66,285, theo nguồn trích dẫn từ 4, các sàn giao dịch này nằm trong phạm vi 5.2% so với nhau — và hoàn toàn vắng mặt trên Steam.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Bản đồ thang giá Skin — Vách đá thanh khoản"
          },
          {
            "level": 2,
            "id": null,
            "text": "Quy tắc được áp dụng một cách cứng nhắc, chứ không phải theo yêu cầu"
          },
          {
            "level": 3,
            "id": null,
            "text": "Hình dạng đó loại trừ điều gì"
          },
          {
            "level": 2,
            "id": null,
            "text": "Giá chào bán không phải là giá"
          },
          {
            "level": 3,
            "id": null,
            "text": "A  Có ba kệ trở lên phù hợp"
          },
          {
            "level": 3,
            "id": null,
            "text": "B  Hai kệ giống nhau"
          },
          {
            "level": 3,
            "id": null,
            "text": "C  Một kệ — chưa sử dụng"
          },
          {
            "level": 3,
            "id": null,
            "text": "Chi phí của đợt điều chỉnh này là bao nhiêu, và nó đã mang lại những gì"
          },
          {
            "level": 3,
            "id": null,
            "text": "Các mục được dành riêng làm hiện vật"
          },
          {
            "level": 2,
            "id": null,
            "text": "Tất cả các danh mục “419”, kèm theo đối tượng mà mỗi mức giá đề cập đến"
          },
          {
            "level": 2,
            "id": null,
            "text": "Những kệ hàng chứa những thứ mà “Steam” sẽ không bao giờ có"
          },
          {
            "level": 2,
            "id": null,
            "text": "Thực tế, nguồn cung khan hiếm đến mức nào"
          },
          {
            "level": 2,
            "id": null,
            "text": "Những gì các kệ hàng của bên thứ ba thực sự đã mang lại"
          },
          {
            "level": 2,
            "id": null,
            "text": "Những miếng dán đã dùng được 16 năm và một nắm găng tay"
          },
          {
            "level": 2,
            "id": null,
            "text": "Mức giá cao được hỗ trợ bởi một giao dịch, chứ không phải bởi việc niêm yết"
          },
          {
            "level": 3,
            "id": null,
            "text": "30 giao dịch đã hoàn tất có giá trị cao nhất trong khoảng thời gian này"
          },
          {
            "level": 3,
            "id": null,
            "text": "Cùng một mặt hàng, cùng khoảng thời gian “90”, nhưng giá cả lại chênh lệch rất lớn"
          },
          {
            "level": 2,
            "id": null,
            "text": "Nguồn gốc của điều này và những gì nó không thể thể hiện"
          },
          {
            "level": 3,
            "id": null,
            "text": "Nguồn và quyền truy cập"
          },
          {
            "level": 3,
            "id": null,
            "text": "Điều kiện để một mặt hàng được công nhận"
          },
          {
            "level": 3,
            "id": null,
            "text": "Những gì chúng tôi không thể có được"
          },
          {
            "level": 3,
            "id": null,
            "text": "Chấm điểm"
          },
          {
            "level": 3,
            "id": null,
            "text": "Tại sao các tổng này là mức tối thiểu"
          },
          {
            "level": 3,
            "id": null,
            "text": "Hãy tự kiểm tra xem"
          },
          {
            "level": 3,
            "id": null,
            "text": "Một đợt điều chỉnh được ghi nhận ngay từ đầu phiên giao dịch"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/vi/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/vi/skin_atlas#gallery",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Factory%20New%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Factory%20New%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Blue%20Laminate%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Field-Tested%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Superconductor%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Gungnir%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Vice%20%28Factory%20New%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Hedge%20Maze%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Vulcan%20%28Factory%20New%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Wild%20Lotus%20%28Well-Worn%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Well-Worn%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Hydroponic%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Medusa%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Specialist%20Gloves%20%7C%20Pillow%20Punchers%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Sport%20Gloves%20%7C%20Pandora%27s%20Box%20%28Field-Tested%29",
          "https://skinport.com/market?search=M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/M4A4%20%7C%20Howl%20%28Field-Tested%29",
          "https://skinport.com/market?search=AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Dragon%20Lore%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/Desert%20Eagle%20%7C%20Cobalt%20Disruption%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20BOOM%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Case%20Hardened%20%28Well-Worn%29",
          "https://skinport.com/market?search=AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Graphite%20%28Factory%20New%29",
          "https://skinport.com/market?search=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Talon%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Kukri%20Knife%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/%E2%98%85%20Ursus%20Knife%20%7C%20Case%20Hardened%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Case%20Hardened%20%28Field-Tested%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Red%20Laminate%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Asiimov%20%28Field-Tested%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Vulcan%20%28Field-Tested%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AK-47%20%7C%20Nightwish%20%28Factory%20New%29",
          "https://skinport.com/market?search=AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Lightning%20Strike%20%28Factory%20New%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AWP%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://csfloat.com/search?market_hash_name=StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://steamcommunity.com/market/listings/730/StatTrak%E2%84%A2%20AWP%20%7C%20Asiimov%20%28Battle-Scarred%29",
          "https://skinport.com/market?search=AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://csfloat.com/search?market_hash_name=AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://steamcommunity.com/market/listings/730/AK-47%20%7C%20Redline%20%28Minimal%20Wear%29",
          "https://skinport.com/market?search=AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://csfloat.com/search?market_hash_name=AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://steamcommunity.com/market/listings/730/AWP%20%7C%20Crakow%21%20%28Factory%20New%29",
          "https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "http://web.archive.org/web/20260921022227/https://help.steampowered.com/en/faqs/view/61F0-72B7-9A18-C70B",
          "https://store.steampowered.com/subscriber_agreement/",
          "http://web.archive.org/web/20260924114457/https://store.steampowered.com/subscriber_agreement/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-atlas.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-artefact-screen.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-above-the-ceiling.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/cs2sh-manifest.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/vi/skin_atlas.content.json",
      "export_json_sha256": "970b8ccaaebe1650291a9acdaccfa4dafc7dbeb24f74c64e3c970844242f1e91"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "vi/social_graph.html",
      "language": "vi",
      "title": "Theo dõi các mối liên hệ đã được ghi nhận — Hồ sơ “Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/vi/social_graph",
      "source_html_sha256": "36e7570a1e03e150c34a68e06ef5f60006ac44f69d0a5e3d3b6a129d4a4da80f",
      "exported_at": "2026-09-29T00:23:07.139Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "social_graph.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/vi/social_graph.pdf?v=print-20260929-v5",
        "sha256": "43ec18fad797f777a02df7b86a9f043c65db3c2ce16d908ab76828dc4d1b9594",
        "bytes": 124928,
        "pages": 6
      },
      "integrity": {
        "signed_object": "social_graph.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "social_graph.content.json.asc",
        "digest_file": "social_graph.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify social_graph.content.json.asc social_graph.content.json",
          "sha256sum -c social_graph.content.json.sha256"
        ]
      },
      "content": {
        "text": "Hãy theo dõi các mối liên hệ.Kiểm tra từng mối quan hệ.\n\nTìm kiếm một hồ sơ. Chọn loại mối quan hệ. Theo dõi các hồ sơ liền kề trực tiếp trong các bản ghi đã thu thập. Công cụ nghiên cứu: Các cạnh thể hiện các mối quan hệ công khai, chứ không phải bằng chứng về sự tiếp xúc trực tiếp, sự phối hợp riêng tư hay hành vi sai trái giữa bất kỳ hai nút nào. Cách bố trí nút theo mô hình “3,435-” sẽ dễ hiểu nhất khi sử dụng các bộ lọc.\n\nKhám phá từng mối quan hệ một\n\n💡 Nhấp và kéo các nút để sắp xếp lại đồ thị. Di chuột qua để xem thông tin chi tiết. Đường liền màu xanh lục nhạt = Mối quan hệ bạn bè, đường đứt đoạn màu hổ phách = Bình luận lẫn nhau.\n\nLoại mối quan hệHồ sơ và những người hàng xóm trực tiếp\n\n3,435 hồ sơ · 4,551 các liên kết đã lưu\n\nTìm kiếm và chọn một hồ sơ, hoặc nhấp vào một nút. Chỉ còn lại các nút lân cận trực tiếp đã được ghi nhận của nó. Một cạnh ghi nhận một mối quan hệ; nó không thiết lập sự phối hợp riêng tư.\n\nCác hồ sơ trong tập dữ liệu đã thu thập\n\nBảng nguồn đầy đủ: Tải xuống tất cả các hàng từ “3,435” (dạng CSV). Bảng dưới đây ban đầu hiển thị các hàng đầu tiên 25; chức năng tìm kiếm và phân trang sẽ hiển thị toàn bộ tập dữ liệu.\n\n1–25 / 3,435 hàng\nTên nhân vật\tSteamID64\tQuyền riêng tư\tTình trạng\tTư cách thành viên nhóm\tHàng tồn kho (USD)\tĐịa điểm\nMahatma Gandhi\t76561198333721623\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tPH\nGalley//갤리🌠🌙\t76561198043416832\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tKP\n$Schlächter\t76561198860277343\tPUBLIC\tClean\tsteambans\t$0.00\tUnknown\n❄r3dsn0w000™❄ [Cristi]🎮\t76561197986767957\tPUBLIC\tClean\tCommunityLegends\t$0.00\tRO\n(2a03) Wolfy\t76561197991671851\tPUBLIC\tCommunity\tsr_public\t$0.00\tUS\nZloy2288\t76561198038578334\tPUBLIC\tClean\tsteambans\t$0.00\tBY\njessy\t76561198039125237\tPUBLIC\tCommunity, VAC (1x)\tCommunityLegends\t$0.00\tJP\nJithraRufure\t76561198071896910\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\n| Níllerdínho |\t76561198003487438\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tDK\nJones is back\t76561198023013026\tPRIVATE\tVAC (1x)\tsteambans\t$0.00\tUnknown\nUNEX | ★✠☠ MoH3st ☠✠\t76561198050763123\tPUBLIC\tClean\tsteambans\t$0.00\tDE\nTrojan\t76561198048457084\tPUBLIC\tClean\tCommunityLegends\t$0.00\tDE\n𝗠𝗮𝘆𝘂 ❤\t76561199377967696\tPUBLIC\tClean\tsr_public\t$0.00\tIS\nbig fucking idiot\t76561198871206397\tPUBLIC\tVAC (1x)\tsteambans\t$0.00\tUnknown\nSOFF Games\t76561198227129276\tPUBLIC\tClean\tcommunitymoderators\t$0.00\tRU\nThijminecraft02\t76561198253895669\tPUBLIC\tClean\tSteamIDcouk SArchive\t$0.00\tNL\nStatic-sama\t76561198289329793\tPUBLIC\tClean\tsteambans\t$0.00\tJP\n𝙸mmortal 𝚂targazer\t76561198142116760\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\nCommander Keen\t76561197987773287\tPUBLIC\tClean\tsteambans\t$0.00\tBE\nS1mX\t76561199648509165\tPUBLIC\tClean\tsr_public\t$0.00\tUnknown\nmixwell\t76561199276547472\tPUBLIC\tClean\tsr_public\t$0.00\tJP\nP90_GOD_YyEs™\t76561198285821942\tPUBLIC\tClean\tsteambans\t$0.00\tHK\nhewwo?\t76561199133807546\tPUBLIC\tVAC (1x)\tsteambans\t$0.00\tCH\n♕Kamikaze Atze♕\t76561198002700103\tPUBLIC\tClean\tsteambans\t$0.00\tDE\nPastica\t76561198154655970\tPUBLIC\tClean\tSteamIDcouk\t$0.00\tDZ\nCác mối quan hệ bạn bè đã được ghi nhận\n\nBảng nguồn đầy đủ: Tải xuống tất cả các hàng từ 4,299 (dạng CSV). Bảng dưới đây ban đầu hiển thị các hàng đầu tiên 25; chức năng tìm kiếm và phân trang sẽ hiển thị toàn bộ tập dữ liệu.\n\n1–25 / 4,299 hàng\nNgười dùng A\tHướng dẫn\tNgười dùng B\tLoại quan hệ\nMahatma Gandhi\n76561198333721623\t↔\tDeskjet\n76561198272738437\tMutual Friends\nGalley//갤리🌠🌙\n76561198043416832\t↔\tomega\n76561197960274529\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tFisty\n76561198057301486\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tFaalagorn\n76561198001116101\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tMURK\n76561198036995672\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tÅρøᴛʜℯᴛȋᴄÅʟȋℯη ♛👽♛\n76561197984615267\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tsilatrak\n76561197999629462\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tBlack Blade\n76561198083368493\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tAvenger\n76561197978249317\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tRemtar\n76561198124322650\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tCato\n76561197961345984\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t✪ G λ M Ξ ®\n76561197994308495\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tclees42\n76561198030936806\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t𝓜ε𝔰𝔥 | AusLevels\n76561198108828539\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tSgtFopper™\n76561198002555892\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t❥Miss Bee\n76561198046958996\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tTesTy\n76561198032370068\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tskl_andrey\n76561198136881436\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\t\"Exekutor\"\n76561198009583947\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tAraripe\n76561198103754372\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tsteve6678\n76561198053200093\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\ttrinner\n76561197970359081\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tSteph S.\n76561198025653291\tOne-way Friend\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tKirito\n76561198154545657\tMutual Friends\n❄r3dsn0w000™❄ [Cristi]🎮\n76561197986767957\t↔\tDoc. todt\n76561197984492467\tMutual Friends\nLiên kết đến các bình luận đã được ghi lại\n\nBảng nguồn đầy đủ: Tải xuống tất cả các hàng từ 252 (dạng CSV). Bảng dưới đây ban đầu hiển thị các hàng đầu tiên 25; chức năng tìm kiếm và phân trang sẽ hiển thị toàn bộ tập dữ liệu.\n\n1–25 / 252 hàng\nTác giả\tHướng dẫn\tHồ sơ đối tượng mục tiêu\tNgày\tNội dung bình luận\nDeskjet\n76561198272738437\t→\tMahatma Gandhi\n76561198333721623\t16 September, 2021 @ 11:02:05 pm PDT\t\"𝑵𝒐𝒘 𝒊𝒇 𝑰 𝒇𝒖𝒄𝒌 𝒕𝒉𝒊𝒔 𝒎𝒐𝒅𝒆𝒍𝑨𝒏𝒅 𝒔𝒉𝒆 𝒋𝒖𝒔𝒕 𝒃𝒍𝒆𝒂𝒄𝒉𝒆𝒅 𝒉𝒆𝒓 𝒂𝒔𝒔𝒉𝒐𝒍𝒆𝑨𝒏𝒅 𝑰 𝒈𝒆𝒕 𝒃𝒍𝒆𝒂𝒄𝒉 𝒐𝒏 𝒎𝒚 𝑻-𝒔𝒉𝒊𝒓𝒕𝑰'𝒎𝒎𝒂 𝒇𝒆𝒆𝒍 𝒍𝒊𝒌𝒆 𝒂𝒏 𝒂𝒔𝒔𝒉𝒐𝒍𝒆\" - Nelson Mandela\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t22 November, 2021 @ 4:10:28 pm PDT\thttps://anige.horigiri.net/?cat=22\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t18 November, 2021 @ 12:45:26 am PDT\thttps://gamerch.com/umamusume/entry/250411\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t8 August, 2021 @ 4:13:25 am PDT\thttps://modoocode.com/304\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t6 February, 2021 @ 3:35:05 pm PDT\t▤ ∫︹- -ω⁾ ⁽︹▓▓︺\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t11 December, 2019 @ 1:50:53 am PDT\thttps://blog.naver.com/aksenwlddj12/221369410039\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t2 October, 2019 @ 7:11:59 am PDT\tǤαllєу║︎갤리..۩\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t9 April, 2019 @ 12:51:28 pm PDT\tExplosiveDamage(owner, from, maxrange, minrange, distmultiplier, dmgmultiplier, mindamage, typ, damagetype, ignore)\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 12:22:47 pm PDT\tinfo - sh_titles.lua\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 12:21:46 pm PDT\tlocal nibbas = 1344 init.lua\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t7 April, 2019 @ 11:31:58 am PDT\thttp://foreign.aladin.co.kr/shop/wproduct.aspx?ItemId=123955531&start=slayer\nGalley//갤리🌠🌙\n76561198043416832\t→\tGalley//갤리🌠🌙\n76561198043416832\t3 April, 2019 @ 1:26:41 am PDT\tǤαllєу\nLei\n76561198982197954\t→\tJithraRufure\n76561198071896910\t29 December, 2024 @ 12:58:08 pm PDT\t+rep he knows how 2 rush B ￣ヘ￣\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t2 September, 2026 @ 5:16:55 am PDT\tlol\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t20 August, 2026 @ 6:11:03 am PDT\t?\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t25 July, 2026 @ 7:20:05 am PDT\thahahahaha\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t30 June, 2026 @ 12:52:42 pm PDT\twow\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t30 June, 2026 @ 12:41:32 pm PDT\txD\nvalorant enjoyer\n76561199112142402\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:26:30 pm PDT\toh no!!\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:26:11 pm PDT\toh no!!\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:22:22 pm PDT\tomg !!! they know my secret, omg!!!\nvalorant enjoyer\n76561199112142402\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:21:39 pm PDT\t+rep good ♥♥♥♥♥ player\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 10:20:50 pm PDT\tomg! u cant cheat on secure gaben servers, omg dont report me, they ban me for boosted omg\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t29 June, 2026 @ 8:37:11 pm PDT\txD\nmixwell\n76561199276547472\t→\tmixwell\n76561199276547472\t28 June, 2026 @ 1:58:14 pm PDT\twow",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Hãy theo dõi các mối liên hệ.Kiểm tra từng mối quan hệ."
          },
          {
            "level": 2,
            "id": null,
            "text": "Khám phá từng mối quan hệ một"
          },
          {
            "level": 2,
            "id": null,
            "text": "Các hồ sơ trong tập dữ liệu đã thu thập"
          },
          {
            "level": 2,
            "id": null,
            "text": "Các mối quan hệ bạn bè đã được ghi nhận"
          },
          {
            "level": 2,
            "id": null,
            "text": "Liên kết đến các bình luận đã được ghi lại"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-profiles.csv",
          "https://steamcommunity.com/profiles/76561198333721623",
          "https://steamcommunity.com/profiles/76561198043416832",
          "https://steamcommunity.com/profiles/76561198860277343",
          "https://steamcommunity.com/profiles/76561197986767957",
          "https://steamcommunity.com/profiles/76561197991671851",
          "https://steamcommunity.com/profiles/76561198038578334",
          "https://steamcommunity.com/profiles/76561198039125237",
          "https://steamcommunity.com/profiles/76561198071896910",
          "https://steamcommunity.com/profiles/76561198003487438",
          "https://steamcommunity.com/profiles/76561198023013026",
          "https://steamcommunity.com/profiles/76561198050763123",
          "https://steamcommunity.com/profiles/76561198048457084",
          "https://steamcommunity.com/profiles/76561199377967696",
          "https://steamcommunity.com/profiles/76561198871206397",
          "https://steamcommunity.com/profiles/76561198227129276",
          "https://steamcommunity.com/profiles/76561198253895669",
          "https://steamcommunity.com/profiles/76561198289329793",
          "https://steamcommunity.com/profiles/76561198142116760",
          "https://steamcommunity.com/profiles/76561197987773287",
          "https://steamcommunity.com/profiles/76561199648509165",
          "https://steamcommunity.com/profiles/76561199276547472",
          "https://steamcommunity.com/profiles/76561198285821942",
          "https://steamcommunity.com/profiles/76561199133807546",
          "https://steamcommunity.com/profiles/76561198002700103",
          "https://steamcommunity.com/profiles/76561198154655970",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-connections.csv",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/social-table-comments.csv"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/vi/social_graph.content.json",
      "export_json_sha256": "ebf245c926ae046aefebeee4b488aaffc946b6995ab5763a995a7e1ab208a21e"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "vi/steam_enforcement_evidence.html",
      "language": "vi",
      "title": "Quy tắc so với phản ứng — Hồ sơ “Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/vi/steam_enforcement_evidence",
      "source_html_sha256": "ecbb114684c0cc5ee95514e0bca9e158c1943a13b04af6afbf97d1566c7ef053",
      "exported_at": "2026-09-29T00:23:08.372Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "steam_enforcement_evidence.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/vi/steam_enforcement_evidence.pdf?v=print-20260929-v5",
        "sha256": "099aa7e0cda4dece9757d96d7d9705ff654d8e653e8f33e6c2645d879ca902c1",
        "bytes": 384002,
        "pages": 36
      },
      "integrity": {
        "signed_object": "steam_enforcement_evidence.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "steam_enforcement_evidence.content.json.asc",
        "digest_file": "steam_enforcement_evidence.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify steam_enforcement_evidence.content.json.asc steam_enforcement_evidence.content.json",
          "sha256sum -c steam_enforcement_evidence.content.json.sha256"
        ]
      },
      "content": {
        "text": "Phụ lục chứng cứ / hồ sơ có liên kết với nguồn\nSteam Bằng chứng thực thi — Hồ sơ hỗ trợ & Mạng lưới nhà phát triển\n\nQuy tắc. Phản hồi.\n\nPHẦN NÀY CHỨNG MINH ĐIỀU GÌ\n\nPhòng chứng cứ này so sánh Thỏa thuận người đăng ký chính thức của Valve với các bản ghi thực thi có ghi ngày tháng, các quyết định giải quyết tranh chấp hỗ trợ, và hồ sơ mạng nhà phát triển trên các kho lưu trữ 252 và hồ sơ 3,320. Điều này cho thấy rằng những người sở hữu tài khoản thông thường phải đối mặt với các biện pháp thực thi không thể bác bỏ và việc đóng tài khoản hỗ trợ sau khi phiên đăng nhập bị xâm phạm, trong khi các hoạt động bot thương mại quy mô lớn vẫn vận hành liên tục với quyền truy cập vào cơ sở hạ tầng công cộng.\n\n← Quay lại Bản tóm tắt dành cho lãnh đạo\n\nHãy đọc nội dung hạn chế được ghi rõ. Mở phần phản hồi đã được ghi lại. So sánh những gì nguồn thông tin trình bày với những câu hỏi vẫn chưa được trả lời.\n\nHỗ trợ và khiếu nại ↓Cơ sở hạ tầng công cộng ↓\n252hồ sơ kho lưu trữ\n3,320hồ sơ công khai\n4,214các cặp hồ sơ–kho lưu trữ riêng biệt\n98,902Các cặp hồ sơ có kho lưu trữ chung\n01 / Hỗ trợ, các biện pháp trừng phạt và phục hồi\nHãy đọc đơn khiếu nại.Hãy giữ nguyên tệp nguồn kèm theo.\nThư viện các trường hợp bị từ chối hỗ trợ (Triển lãm “981”) ↗Tải xuống các bản ghi đã chọn ↓\nHFB / TRƯỜNG HỢP THUÊ NGOÀIGiải pháp thỏa hiệp được công nhận.\nCác trường hợp sa thải đã được báo cáo.\n\nHãy tham khảo nội dung phản hồi của bộ phận hỗ trợ được trích dẫn dưới đây và nguồn thông tin liên quan đến tuyên bố về nhân viên của nhà thầu.\n\nMở bài viết và các nguồn tham khảo của nó →\n\nDưới đây: năm mẫu được bảo quản các bài đăng công khai trên Reddit từ bộ sưu tập hồ sơ hỗ trợ được cung cấp. Mỗi bản ghi ghi lại một tương tác đã được báo cáo với hệ thống hỗ trợ của Valve — được lưu giữ kèm theo liên kết nguồn gốc, vị trí chụp màn hình và toàn bộ nội dung văn bản. Đây là những lời kể của các nạn nhân. Các bản ghi hỗ trợ đã được xác thực, vốn có thể xác nhận hoặc bác bỏ những lời kể này, hiện do Valve lưu giữ và chưa được công bố.\n\n01\nBan & review2024-12-09\nPermanent sanction & closed appeals\n\nThe author reports a permanent account ban, repeated ticket closures and a planned GDPR access request.\n\nREDDIT / PUBLIC TESTIMONYr/ohnePixelCapture record 294\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 303 words\nPermanently banned Steam account without a clear explanation, need help!\n\nsteam_support_tickets_MEGA.json / record 294\n\nHey everyone,\n\nI’m in a really frustrating situation, and I’m hoping someone here can help me or offer advice. My Steam account was just permanently banned for allegedly violating the Steam Subscriber Agreement, and I have no idea why.\n\n# What Steam Support told me:\n\nThe support message said my account was banned due to:\n\n* Suspicious activities related to transferring or attempting to sell/trade the account.\n* Community reports and other unspecified factors.\n\nThey added that the ban is permanent and that they can't help me further. They also warned that future support requests regarding this ban might be ignored. 😞\n\n# Why I’m contesting this ban:\n\n* I have never sold, traded, or transferred my account. I’ve been the legitimate owner since the beginning.\n* On the day the ban occurred, I did nothing noteworthy that could have triggered such a sanction.\n* I received no prior warning, which feels incredibly unfair.\n\n# What I’ve tried so far:\n\n* Contacting Steam Support: I explained my situation and asked for more details, but they’re sticking to their decision and closing my tickets.\n* I’m preparing a request based on my Right of Access (GDPR) to get all the data related to my account.\n\n# Questions for the community:\n\n1. Has anyone successfully had a permanent ban lifted on Steam?\n2. Are there steps I can take to prove I’m the legitimate owner of the account?\n3. Any advice on how to word my request to convince support to reconsider my case?\n4. Would it be helpful to contact the CNIL (I’m based in France) to force Steam to provide more information?\n\nI’m really desperate at the thought of losing all my games, purchases, and years of playtime. Thanks in advance for any help and advice you can give!\n\nhttps://preview.redd.it/jk9qv0gmhv5e1.png?width=1289&amp;format=png&amp;auto=webp&amp;s=b3a333ebb08ea133e2c8747ba126f5a68283d9f7\n\nhttps://preview.redd.it/4sopt0gmhv5e1.png?width=1022&amp;format=png&amp;auto=webp&amp;s=56195d5336118faf9413f1514ead7e8d24c788c3\n\nhttps://preview.redd.it/eqrxw0gmhv5e1.png?width=996&amp;format=png&amp;auto=webp&amp;s=ff3539d28ab754e513ad471822c5de652920101d\n\nhttps://preview.redd.it/728xz0gmhv5e1.png?width=1034&amp;format=png&amp;auto=webp&amp;s=bc5335673509929669af785aa244bf8d2dc58da8\n\n02\nSupport access2025-05-09\nAccount recovery & a reported $10,000 loss\n\nThe author alleges that support reset credentials and removed account protection following another person’s recovery ticket.\n\nREDDIT / PUBLIC TESTIMONYr/legaladviceCapture record 110\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 193 words\nGot $10k stollen from steam inventory due to steam' support fault.\n\nsteam_support_tickets_MEGA.json / record 110\n\nLocation: Quebec, Canada.\n\nLast year, someone hacked my Steam account and stole items worth about $10,000 USD. I only noticed this last week. When I talked to Steam Support, they admitted that someone submitted a ticket to make changes on the account and Steam Support reset my password and turned off all my account security.\n\nI asked Steam Support about getting my items back, but they said there was nothing they could do. They told me I should follow their security recommendations.\n\nThe problem is, I did everything they \"suggested\" to protect an account:\n\n* I had two-factor authentication.\n* My phone number was connected to my account.\n* I used Steam Guard.\n* I printed recovery codes and kept them in a safe.\n\nEven though I did all these things, Steam Support still gave someone else access to my account. The stolen items had been in my account since around 2016-2017. Also, I had not logged in for a few years, so I didn’t accidentally give my information to a fake website.\n\nIs there anything I can do, or do I just have to accept losing $10,000 USD?\n\nThanks for your help.\n03\nRestoration2022-07-07\nA reported $500+ loss & template replies\n\nThe author describes an account compromise, disputed transactions and a support response that allegedly did not address the submitted evidence.\n\nREDDIT / PUBLIC TESTIMONYr/DotA2Capture record 45\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 410 words\nFunds stolen through steam market. Disappointed with Steam response.(or lackthereof)\n\nsteam_support_tickets_MEGA.json / record 45\n\nOn 6th July 2022, 44 unauthorized transactions were made on the steam market using my steam wallet funds totalling roughly $500+ USD to buy worthless 1 cent Dota 2 items. This happened during the wee hours in the morning and i contacted them first thing when i woke up. \n\nI have 2FA enabled all the time, and always thought this would not happen to me as I do not go on betting sites/click sketchy links. My account password + emails were not changed, nor did they take my inventory, just that my funds were used illicitly. Also when I went to disable other APIs, it says there are no other APIs to disable. Shows that it wasn't through me clicking sketchy links and leaving my account details there. Would have lost the whole account if i did so.\n\nWhat baffles me is how did they bypass my 2FA to login my account? Why doesn't steam market purchases go through 2FA as well? First time in 9 years that this happened to me. My acc was logged in 'BY' 'Vitebsk' during the illicit purchases but I'm based in Asia I gathered all the screenshots and provided in the ticket to steam support. \n\nAll i got was the standard copy paste template reply by Steam Support. Lost $500+ and was not even worthy of having a proper person to look into this. I dont think they even read or take a look at the screenshots cause if they did, they would have come to the realization that what happened was clearly fraud, and with a few clicks, reverse the unauthorized transactions, refund my wallet and ban the hijacker. \n\nOver the years, i've spent quite a fair bit on steam but really, this is the kind of recourse we get when our account is compromised? They just don’t care, sigh. I only expect the bare minimum from Steam and looks like even that is quite far-fetched.\n\nSS: https://imgur.com/a/67frcls \n\nHijacker: https://steamcommunity.com/profiles/76561199141246495\n\nSteam Response: https://imgur.com/a/V6v4maM\n\nI could think of a few ways on how to Improve:\n\n1) Add 2FA to market transactions. (even if its bulk posting or selling of items, just 1 2FA notif is required)\n\n2) Enable accounts to be region locked. (if you are migrating, then have to go through steam support etc)\n\n3) Additional Lock on Steam Wallet. (Another password perhaps?)\n\nEDIT: 2nd ticket in and I have still yet to receive a non robotic copy paste template response from Steam.\n04\nRestoration2021-11-29\nSteam Guard & an item-restoration refusal\n\nA preserved post includes the author’s account of item theft and a support response declining restoration.\n\nREDDIT / PUBLIC TESTIMONYr/DotA2Capture record 58\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 563 words\nMany people are losing item via clicking links where steam guard is enabled and steam support doesn't not restore items.\n\nsteam_support_tickets_MEGA.json / record 58\n\nAccounts are getting compromised and might be their pc as well where Steam market is targeted hence the malicious links . I am assuming these hackers are getting encouraged where steam support is not doing nothing and they are getting away with hacking items.  \nLiterally the guy who is supporting the game which he doesn't get any in game advantage just  cosmetics in game only for the sole purpose of supporting the game so that the game will prosper and become beautiful way  to enjoy weekend. But right now players are getting hacked left right and center and steam support  is copy pasting message where in short they are blaming the guy who clicked link. 1st this is happening because they are not targeting players but they are targeting market since they are selling those stuff for real cash via party website. Steam is a huge company and can eradicate the problem or at least can remove links temporarily  in chat since hackers are targeting .They made us install steam guard by saying we wont help if there is no steam guard now steam guard is not enough to save our inventory now they changed their policy  that they should not click any suspicious links. How would we know if the link is suspicious ? After clicking and getting our inventory stolen right !   \n\"we'd have to duplicate an item to restore it. Duplication lowers the value of all items by reducing their scarcity and inflating the economy, which affects everyone involved in trading and the Market. To maintain the value of everyone’s inventory, we do not restore items. For more information, please see the Steam Item Restoration Policy.\"  \nThey care for millions of people IN STEAM MARKET where as few  are losing items which is going to affect market where the rightful owner bought the items and hacker is going to sell the item via 3rd party website and enjoy ! HOW IRONIC !!  \nThis is the message from support where my frnd got his items stolen via clicking on link  \n   \nHi there,  \n\nThank you for the information and screenshots provided.  \n\nIt appears that the account was compromised, please take the following steps to secure your account and computer:  \n\nScan your computer for viruses, key loggers, spyware, and other malicious code using antivirus software with updated virus definitions.  \nChange the password for the email address that is associated with your Steam account.  \nRegularly reset your Steam account password.  \n\nPlease see our Security Recommendations article.  \n\nIn addition, I’m sorry to hear that your items were removed without your permission. Unfortunately, Steam Support does not restore scammed, lost, or stolen items for any reason.  \n\nSince Steam Support does not remove items from accounts, we'd have to duplicate an item to restore it. Duplication lowers the value of all items by reducing their scarcity and inflating the economy, which affects everyone involved in trading and the Market. To maintain the value of everyone’s inventory, we do not restore items. For more information, please see the Steam Item Restoration Policy.  \n\nTo make sure that a scammer is reported, please report them through the Steam Community. Reporting a scammer through the Steam Community is the best way to prevent them from committing future scams.  \n\nTo learn how to avoid scams or hijackings, please see our Trade Scam article.  \n\nIf you still need assistance, please let us know.\n05\nEnforcement2025-05-11\nSelective enforcement & an unexplained ban\n\nA community member describes a disputed ban and contrasts it with the visibility of commercial gambling promotion.\n\nREDDIT / PUBLIC TESTIMONYr/SteamUncensoredCapture record 107\nOpen original post ↗Link to this record ↗\nRead the complete captured text · 1,208 words\n🚨 Steam Bans Without Reason and Ignores Its Community — What’s Going On?\n\nsteam_support_tickets_MEGA.json / record 107\n\nHey r/Steam,\n\nI’m writing this to share my thoughts and concerns about my friend [moneylead](https://steamcommunity.com/id/moneylead/) and Steam’s policies in general. I spoke with him yesterday about his situation, though I didn’t discuss writing this post with him—I asked last night, but he hasn’t responded yet. I want to highlight that this issue is broader than just his case, and while Steam might make changes in the future (though that’s unlikely), I feel the community needs to understand how far Steam has strayed from its original values. I’m not trying to put moneylead in a tough spot with this thread—all the info I’m sharing is public, nothing secretive. I hope he won’t be upset with me, but the community needs this case to see the bigger picture and how Steam feels completely unaccountable.\n\n**Why Does Steam Ignore Its Community?**  \nWhy does a platform like **Roblox** provide a detailed log of ban reasons, while Steam, which claims to be \"community-driven,\" ignores its community, bans whoever they want, for whatever they want, with no transparency? I looked into Roblox as a popular game—not a direct competitor to Steam—to see how their bans look, and you can check it out yourself: [Roblox Ban Reasons](https://www.google.com/search?q=Roblox+ban). Their bans are clear, detailed, and actually explain what you did wrong. I think most decent gaming communities operate like this—not with support agents named Olga, hired through outsourcing, who only know how to send canned auto-replies. Take cases like St4ck—or my friend **moneylead**. All these unbans, like **St4ck’s** or **Alexanddd’s**, happened behind closed doors with zero comments from Steam. Of course, it’s convenient for Steam to handle everything in secret, so no one knows or sees what’s going on—but this violates Steam’s own community rules and principles.\n\n**Who Is moneylead?**  \nI’ve known [moneylead ](https://steamcommunity.com/id/moneylead/)since around 2021. We played Dota 2 a couple of times, and then I just stayed on his friends list. He’s always been a legit player, bringing revenue to Steam through purchases. He never sold his skins, whether in **Dota or CS2—he wasn’t a trader**. All he did was:\n\n* Buy games and skins.\n* Collect badges to level up his profile.\n\nAccording to [SteamSets](https://steamsets.com/account/76561199080934614), he’s given out 324,000 Steam Points—I think he awarded profile rewards to all his friends in the list (though I’m not 100% sure). I do know he ran contests and gave gifts to friends, always supporting the community.\n\n**Steam’s Unfair Treatment**  \nI’ve seen Steam remove his showcases, avatar, description, and even his country multiple times—just because he’s from **Ukraine**. He has a ton of haters leaving toxic comments on his wall, and Steam seems to favor **Russian** users. Every time he tried to appeal the removal of his showcases or profile description—which didn’t break any rules, just had his Instagram link, and his avatar is the same as it is now—Steam moderators didn’t care. **They don’t care about top players who bring them massive revenue, nor about regular users.**\n\n>*Here’s the worst part: moneylead works in cybersecurity, specifically fighting account theft and phishing. He’s neutralized over 5,000 threats targeting Steam alone. And yet, Steam bans him for \"account hijacking\"?*\n\nIf you roughly calculate moneylead’s contribution to Steam and the community—his profile, level, badges (not skins, you can’t sell those)—is this normal, Steam? Banning people, closing tickets, and ignoring users with a spotless reputation who aren’t involved in any commercial activity, just bringing you profit without taking anything in return?\n\n**Steam’s Double Standards**  \nI’m honestly shocked:\n\n* YouTubers who promote casinos and skin gambling? Steam’s fine with that.\n* A cybersecurity expert who fights scams, doesn’t promote casinos, and openly talks about it on his profile? **Banned with no explanation, ignored, and denied an unban.**\n\nI wonder if Steam deliberately bans a high-level account once a year just because of their impunity—maybe for hype or something. Otherwise, this is just madness. It’s scary to think how many regular players have lost their accounts and skins—not because of scammers, but because of Steam’s desire to ignore, send auto-replies, and do whatever they want.\n\n**How Many Others Are Affected?**  \nHow many others are out there—maybe not as well-known—who just have a few games or skins, get banned for nothing, and receive zero explanation or response? **Is this even legal?** Every other platform provides a detailed log with specific violations, but Steam slaps on the same vague label and sends templated responses.\n\n* How safe is it to buy skins on Steam?\n* What’s the chance Steam will just ban your account for no reason, with no explanation?\n\n**A Message to Valve**  \nI wish moneylead the best in resolving this, but Valve, it’d be great if you remembered what \"community\" means and started following the law. Because right now, it looks like your 30% commission, impunity, and sense of being above the law in the U.S. have given you the idea that you can do whatever you want.\n\nI’m sure there are many others like moneylead and St4ck—people who aren’t public or don’t have the resources to fight back. Let’s unite these cases. **If you’re a U.S. resident who’s been banned by Steam without reason and wants to challenge it, please reach out to me.** I’m finishing my **Juris Doctor (J.D.) program at SMU Dedman School of Law** in Dallas, Texas, and I’m participating in a legal clinical practice under Rule 13 of the Texas Supreme Court.\n\nWhat Steam is doing is absolutely disgusting and illegal, and **I’d be happy to help any gamer (legitimate, with no real violations) who has games or skins with value. This will be beneficial for my practice, and it’s time to put Steam in its place and show them they can’t just dictate their own rules with arbitration**. Let’s take it all the way—not for punishment, but for the sake of the community. Maybe if Steam loses a case, they’ll change their policies and start explaining their actions like most popular gaming communities do. Many of us remember how Steam Support used to recover stolen accounts and ended up “stealing” skins themselves—banning without real reasons is basically the same thing, and that’s a serious accusation.\n\nSo, r/Steam, see you soon. I think you understand what you’re doing and how many people you’ve illegally deprived of their assets. I want to raise this issue—not just for the U.S., but for the entire world. You’ve banned class-action lawsuits? **Welcome to Texas.** I recommend starting to look for licensed attorneys in Texas, because I’d love to discuss your company’s policies, feedback, and support agents named Olga—a name that strongly associates with Russian users. Maybe it’d be easier to move your company to Moscow? But I’d be happy to discuss these critical issues on behalf of the global gaming community.\n\nAlso, I wouldn’t recommend ignoring the lawsuit request that will be sent to your physical address and email address, as the court will proceed without you, and that might upset you—especially since things aren’t going so well for a company with stocks like yours.\n\n**Thanks to everyone who took the time to read this. For those who need real help with an unjust Steam ban without any explanation, I’d be happy to assist. For users from Texas, we can easily file a collective lawsuit against Steam—let’s connect and make it happen.**\n02 / Mạng lưới phát triển “Steam”\nCơ sở hạ tầng công cộng.Được ghi lại trên quy mô lớn.\nTải xuống toàn bộ các bản ghi của “252” ↓\n\nCác phụ kiện đi kèm output_steam_network các bản ghi chụp nhanh lưu trữ, các mối quan hệ đóng góp/phân nhánh công khai và sự trùng lặp trong hồ sơ. Đây là những bản ghi được công bố — những gì đã được xây dựng, ai đã đóng góp, những gì đã được phân nhánh. Dòng bằng chứng về các khả năng công khai chính là điều mà “Valve” phải tính đến.\n\nKho lưu trữ / mô tả\tNhững người đóng góp\tForkers\tHồ sơ đã lưu\nalliedmodders/amxmodx\n\nAMX Mod X - Half-Life 1 Scripting and Administration\n\n\t40\t40\t80\nalliedmodders/sourcemod\n\nSourceMod - Source Engine Scripting and Administration\n\n\t40\t40\t80\nDoctorMcKay/node-steam-user\n\nAllows interaction with the Steam network via the Steam client protocol\n\n\t40\t40\t80\nFacepunch/Facepunch.Steamworks\n\nAnother fucking c# Steamworks implementation\n\n\t40\t40\t80\nJustArchiNET/ArchiSteamFarm\n\nC# application with primary purpose of farming Steam cards from multiple accounts simultaneously.\n\n\t40\t40\t80\nodota/core\n\nOpenDota: Open source Dota 2 data platform with automated replay parsing\n\n\t40\t40\t80\nodota/dotaconstants\n\ndotaconstants: Static data for Dota applications\n\n\t40\t40\t80\nodota/web\n\nOpenDota: React web UI for Dota 2 statistics using the OpenDota platform\n\n\t40\t40\t80\nsplewis/get5\n\nCS:GO Sourcemod plugin for competitive matches/scrims\n\n\t40\t40\t80\nSteamDatabase/FileDetectionRuleSets\n\n🔎 Rules to detect game engines and other technologies based on Steam depot file lists\n\n\t40\t40\t80\nSteamRE/SteamKit\n\nSteamKit2 is a .NET library designed to interoperate with Valve's Steam network. It aims to provide a simple, yet extensible, interface to perform various actions on the network.\n\n\t40\t40\t80\nValveSoftware/dxvk\n\ndxvk tree containing branches used by Proton\n\n\t40\t40\t80\nValveSoftware/GameNetworkingSockets\n\nReliable & unreliable messages over UDP. Robust message fragmentation & reassembly. P2P networking / NAT traversal. Encryption.\n\n\t40\t40\t80\nValveSoftware/gamescope\n\nSteamOS session compositing window manager\n\n\t40\t40\t80\nValveSoftware/Proton\n\nCompatibility tool for Steam Play based on Wine and additional components\n\n\t40\t40\t80\nValveSoftware/source-sdk-2013\n\nThe 2013 edition of the Source SDK\n\n\t40\t40\t80\nValveSoftware/wine\n\nWine with a bit of extra spice\n\n\t40\t40\t80\nValveSoftware/steam-devices\n\nList of devices Steam and SteamVR will want read/write permissions on, to help downstream distributions create udev rules/etc\n\n\t39\t40\t79\nValveSoftware/steam-audio\n\nSteam Audio\n\n\t38\t40\t78\nalliedmodders/metamod-source\n\nMetamod:Source - C++ Plugin Environment and Detour Library for the Source Engine\n\n\t37\t40\t77\nalliedmodders/sourcepawn\n\nA small, statically typed scripting language.\n\n\t35\t40\t75\nValveSoftware/Fossilize\n\nA serialization format for various persistent Vulkan object types.\n\n\t31\t40\t71\nrlabrecque/Steamworks.NET\n\nSteamworks wrapper for Unity / C#\n\n\t27\t40\t67\nModDota/moddota.github.io\n\nModDota github pages project.\n\n\t26\t40\t66\nodota/parser\n\nReplay parse server generating JSON log events from Dota 2 replay files\n\n\t26\t40\t66\nValveSoftware/steam-for-linux\n\nIssue tracking for the Steam for Linux beta client\n\n\t26\t40\t66\nSteamRE/DepotDownloader\n\nSteam depot downloader utilizing the SteamKit2 library.\n\n\t24\t40\t64\nJustArchiNET/ASF-ui\n\nThe official web interface for ASF\n\n\t23\t40\t63\nadvancedfx/advancedfx\n\nHalf-Life Advanced Effects (HLAE) is a tool to enrich content creation mainly for the Counter-Strike series.\n\n\t22\t40\t62\nalliedmodders/ambuild\n\nAlliedModders C++ Build System\n\n\t23\t39\t62\nSteamDatabase/BrowserExtension\n\n💻 SteamDB's extension for Steam websites\n\n\t21\t40\t61\nodota/mobile\n\nReact Native apps for viewing Dota 2 data on Android/iOS\n\n\t19\t40\t59\nValvePython/steam\n\n☁️ Python package for interacting with Steam\n\n\t18\t40\t58\nskadistats/clarity\n\nComically fast Dota 2, CSGO, CS2 and Deadlock replay parser written in Java.\n\n\t13\t40\t53\nSteamRE/open-steamworks\n\nOpen Steamworks is a set of reverse engineered headers for the Valve's Steam Client. More or less abandoned now that the Steamworks SDK is publically available.\n\n\t13\t40\t53\nValveSoftware/Source-1-Games\n\nSource 1 based games such as TF2 and Counter-Strike: Source\n\n\t13\t40\t53\nalliedmodders/hl2sdk\n\nHalf-Life 2 SDK Mirrors\n\n\t11\t40\t51\nSteamDatabase/steamdb.info-issues\n\n🚱 Issue tracker for the SteamDB website\n\n\t11\t40\t51\nCSGOFloat/inspect\n\nSource Code that Powers the CSFloat Inspect Link API\n\n\t10\t40\t50\nValveSoftware/SteamOS\n\nSteamOS community tracker\n\n\t10\t40\t50\nalliedmodders/source2mod\n\nExperimental\n\n\t40\t9\t49\nsmiley/steamapi\n\nAn unofficial object-oriented Python library for accessing the Steam Web API.\n\n\t9\t40\t49\nSteamDatabase/GameTracking\n\n🛢 Dumping things, so you don't have to\n\n\t8\t40\t48\nValveSoftware/counter-strike_rules_and_regs\n\nCS:GO\n\n\t7\t40\t47\nValveSoftware/openvr\n\nOpenVR SDK\n\n\t6\t40\t46\nSteamDatabase/easy-markdown-editor\n\nEasyMDE: A simple, beautiful, and embeddable JavaScript Markdown editor. Delightful editing for beginners and experts alike. Features built-in autosaving and spell checking.\n\n\t40\t4\t44\nValveSoftware/Dota-2\n\nTracker for issues specific to Linux and Mac in the Reborn client. If you have a general issue or non-system-specific feature request please go to dev.dota2.com\n\n\t6\t38\t44\nValveSoftware/Dota2-Gameplay\n\nPublic Bug Tracker for Dota 2\n\n\t4\t40\t44\nJustArchiNET/ArchiBot\n\nNo description in the capture.\n\n\t16\t27\t43\nztizzlegaming/CSGOWinBig\n\nOpen-source Counter-Strike: Global Offensive jackpot betting website.\n\n\t1\t40\t41\nJustArchiNET/mantis.justarchi.net\n\nMantis Bug Tracker (MantisBT)\n\n\t40\t0\t40\nodota/node-steam-user\n\nAllows interaction with the Steam network via the Steam client protocol\n\n\t40\t0\t40\nModDota/TypeScriptAddonTemplate\n\nDota 2 addon template with TypeScript Panorama and VScripts.\n\n\t9\t29\t38\nValvePython/vdf\n\n📜 Package for working with Valve's text and binary KeyValue format\n\n\t6\t32\t38\nalliedmodders/amtl\n\nAlliedModders C++ Template Library\n\n\t17\t19\t36\nValvePython/dota2\n\n🐸 Python package for interacting with Dota 2 Game Coordinator\n\n\t5\t30\t35\nalliedmodders/stripper-source\n\nStripper:Source\n\n\t13\t21\t34\nAllyans3/steam-market-api-v2\n\nSteam Market API v2 package\n\n\t3\t31\t34\nModDota/dota-tutorial\n\nCustom game DOTA tutorial.\n\n\t11\t23\t34\nodota/blog\n\nNo description in the capture.\n\n\t29\t3\t32\nOpsecGuy/BetterGo\n\nExternal CS:GO cheat written in python.\n\n\t1\t27\t28\npxvr-official/1\n\n無許諾配信 企業理念剽窃 動物の森収益化 大神ミオ権利者削除 戌神権利侵害発言 常闇トワ炎上 夜空メルストーカー被害 建築王サポーター放置 赤十字マーク 魔乃アロエ卒業 一つの中國支持声明 大空昴3Dライブ 無限延期清掃員職業差別 日清コラボ楽曲 musedash非公開 rog案件取り消し 壁画ライブ 丁真 Ding Zhen 郑爽 Zheng Shuang 防护林 与朵小天使w 伊月猫凛 本主萌埋午休傻 汪峰 重生细胞 壁纸 比利海灵顿 香蕉君 van 田所浩二 抽象带篮子 抗压背锅吧 季子越 蒋明辉 傻逼…\n\n\t0\t28\t28\nRevadike/InternalSteamWebAPI\n\nDocumenting the unofficial and internal Steam Web API\n\n\t1\t27\t28\nJoeSzymkowiczFiveM/qb-lootcrate\n\nA CSGO-style case opening script\n\n\t2\t25\t27\nAbrarKL/MyRoulette.XYZ\n\nCSGO / Steam Roulette Site created with PHP and Node JS, using the Material Design front-end framework.\n\n\t1\t25\t26\nJustArchiNET/ASF-WebConfigGenerator\n\nNo description in the capture.\n\n\t10\t15\t25\nModDota/dota-data\n\nAuto-generated Dota 2 resource dumps\n\n\t11\t14\t25\nModDota/TypeScriptDeclarations\n\nTypeScript declarations for Dota 2.\n\n\t11\t14\t25\nModDota/API\n\nNo description in the capture.\n\n\t12\t12\t24\nalliedmodders/cssdm\n\nCounter-Strike:Source Deathmatch\n\n\t10\t13\t23\nSteamDatabase/steamstat.us\n\n✅ Front-end of Steam services status website\n\n\t4\t18\t22\nc0deina/csgojackpotV2\n\nCSGO Jackpot Source\n\n\t1\t20\t21\nValvePython/steamctl\n\n🤸 Take control of Steam from your terminal\n\n\t2\t19\t21\nValvePython/csgo\n\n🔫 Python package for interacting with CS:GO Game Coordinator\n\n\t3\t17\t20\nBeepIsla/csgo-crash-exploit\n\nAllows you to crash any Windows user\n\n\t3\t16\t19\nValvePython/vpk\n\n📦 Open, Search, Extract and Create VPKs in python\n\n\t4\t15\t19\nalliedmodders/SM-SteamWorks\n\nExposing SteamWorks functions to SourcePawn.\n\n\t14\t3\t17\nSteamRE/Steam4NET\n\nSteam4NET is a .NET wrapper around the Steamworks C++ interfaces\n\n\t2\t15\t17\nalliedmodders/hl2sdk-manifests\n\nInformation about HL2SDKs shared between Metamod:Source and SourceMod.\n\n\t6\t10\t16\nJustArchiNET/ASF-PluginTemplate\n\nTemplate repository that you can use for creating custom plugins for ArchiSteamFarm.\n\n\t8\t7\t15\nModDota/Dota2AIFramework\n\nGeneral Framework for Dota 2 AI Competitions\n\n\t1\t14\t15\nShkyyl/KeyChamp\n\nExtension for joining free case battle on key-drop automatically\n\n\t1\t14\t15\nSteamDatabase/SteamMonitor\n\n😤 Track Steam's connection manager servers status\n\n\t2\t12\t14\nBaterka/cslore.com\n\nCS:GO gambling site - csgo.style\n\n\t1\t12\t13\nSteamDatabase/SteamTokenDumper\n\n🔢 Submit users' PICS access tokens to SteamDB\n\n\t2\t11\t13\nmonoblocker/roulette\n\nRoulette CS:GO made in React and Typescript\n\n\t1\t11\t12\nzsith/launcher.user.js\n\n// ==UserScript== // @name AposLauncher // @namespace AposLauncher // @include http://agar.io/* // @version 3.062 // @grant none // @author http://www.twitch.tv/apostolique // ==/UserScript== var aposLauncherVersion = 3.062; Nu…\n\n\t1\t11\t12\nLincolnIT/CSGODouble-bot-automated\n\nCSGODouble Automated, auto Betting Bot.\n\n\t1\t10\t11\nvladpuz/steam-market\n\nSteam market API client\n\n\t4\t7\t11\nmcgrizzz/Cstrike.bet\n\nCSGO Roulette Website Angular frontend, nodejs backend, and steam trading bots\n\n\t1\t9\t10\nodota/underlords-web\n\nUI for OpenUnderlords\n\n\t5\t5\t10\nSteamDatabase/SteamToTwitter\n\n🕊 Tweets announcements from various Steam groups\n\n\t1\t9\t10\nModDota/AbilityLuaSpellLibrary\n\nThe successor to the Spell Library by Pizzalol\n\n\t4\t4\t8\nalvinl/bitskins\n\nUnofficial BitSkins API client\n\n\t2\t5\t7\nb1naryth1ef/steamy\n\nA Python Steam community and market API interface that will get you all hot and bothered\n\n\t2\t5\t7\nkratos1812/Case-Opening\n\nIn-game case opening system for CSGO servers.\n\n\t2\t5\t7\nodota/docs\n\nOpenDota API documentation\n\n\t4\t3\t7\nSteamDatabase/steam-advanced-access-fetch-players\n\n📈 Simple script to fetch Steam player count\n\n\t1\t6\t7\nTheRioMiner/CsgoBetterExternalRaytrace\n\nOverridden maps pack for better external raytrace\n\n\t1\t6\t7\nalliedmodders/hl2sdk-mock\n\nMock HL2SDK and Server\n\n\t5\t1\t6\nchristophersu/PySteamMarket\n\nPython API for getting prices from the Steam market.\n\n\t1\t5\t6\nExtremelyd1/Strat-Roulette\n\nCS:GO Sourcemod Plugin\n\n\t2\t4\t6\ngiovanni-orciuolo/double-sdk\n\nA simple way to write CS:GO cheats!\n\n\t2\t4\t6\nJustArchiNET/Madness\n\nMadness embraces your project by including compatibility layer for selected APIs normally not available on .NET Framework target.\n\n\t5\t1\t6\nModDota/TypescriptPanoramaDeclarations\n\nNo description in the capture.\n\n\t4\t2\t6\nodota/rapier\n\nA JavaScript Dota 2 (Source 2) replay parsing library\n\n\t1\t5\t6\nVozn1akHero/CSGOCaseOpeningSimulator\n\nCounter-Strike case opening simulator which resembles the good old CS:GO user interface\n\n\t3\t3\t6\nautarc/steam-store\n\nAPI client for the unofficial steam storefront/big picture resource\n\n\t2\t3\t5\nBETTING-CODE/awesome-esports-sites\n\nA curated list of awesome esport betting sites – live, statistics and other resources.\n\n\t1\t4\t5\njonteohr/Better-Warden\n\nAn improved and more advanced warden plugin with a custom menu for CS:GO jailbreak servers!\n\n\t2\t3\t5\nLudzikk/CSGO-Gambling-Site\n\nhttps://ludzikk.github.io/CSGO-Gambling-Site/\n\n\t1\t4\t5\nModDota/find-steam-app\n\nFind location of an installed Steam app\n\n\t3\t2\t5\nmprey/csgocact.us\n\nsource code for csgocact.us\n\n\t1\t4\t5\nnezu-cc/ServerCrasher\n\nCS:GO Server Crasher\n\n\t1\t4\t5\nodota/testfiles\n\nStores test replay files\n\n\t2\t3\t5\nodota/underlordsconstants\n\nConstant data for Dota Underlords\n\n\t3\t2\t5\nSnaBe/node-steam-market-fetcher\n\nA Node.js wrapper for the Steam Community Market API.\n\n\t2\t3\t5\nSteamDatabase/.github\n\n💗 Organization-wide community health files\n\n\t1\t4\t5\nwolfcon/RIP-HLTV-BET\n\nRIP BET AD (For Tampermonkey) https://greasyfork.org/en/scripts/423484-rip-hltv-bet\n\n\t2\t3\t5\nalliedmodders/blaster.net\n\nSource and GoldSrc Query Tool\n\n\t2\t2\t4\ncatears124/CS2-Price-API\n\nsimple python cs2 steam market price API\n\n\t1\t3\t4\nialakey/caseforge\n\nOpen-source CS2 case-opening platform: Steam auth, provably fair openings, RTP-balanced case builder, withdrawals bought on market.csgo.com and an admin CRM.\n\n\t1\t3\t4\nIlusion9/csgo-fix-mapchange-crash-sm\n\nFix players crash on map change.\n\n\t1\t3\t4\nismail0234/Benson-Map-Crash-Fixer\n\nCSGO Map Change Client Crash Fixer\n\n\t1\t3\t4\njaxwilko/steam-market-api\n\nPHP - Composer Compatible - Steam Market API\n\n\t2\t2\t4\nJustArchiNET/ArchiTag\n\nArchiTag is a very small utility based on Python 3 and Mutagen to provide missing functionality in opusenc of writing specific Opus metadata, such as total number of tracks or track number.\n\n\t1\t3\t4\nModDota/DotaUI\n\nNo description in the capture.\n\n\t2\t2\t4\nnode-steam/market-pricing\n\nWrapper for the unofficial Steam Market Pricing API\n\n\t1\t3\t4\nodota/media\n\nStores media files for Dota projects\n\n\t2\t2\t4\nSergeyIvanovDevelop/Crypto-Steam-Platform\n\nThe repository contains the code and configuration to run a platform for creating cryptocurrency stakes for arbitrary ERC20 tokens.\n\n\t1\t3\t4\nAareksio/csgodouble-floatchecker\n\nAdds context menu option to check item's float value\n\n\t1\t2\t3\nchinm4/CSGOdrop\n\nA online csgo gambling casino that includes a variety of mini games that allows you to win csgo skins\n\n\t2\t1\t3\nCruze03/CSGO-Case-Opening-Prank\n\nCommand:- !prank (Admin flag \"n\" required)\n\n\t1\t2\t3\nDhruva-Kapadia/CSGOTrollGG\n\nCSGO Case Opening Simulator\n\n\t2\t1\t3\nErhanCSGO/CSGOPolygon-prediction\n\nCSGOPolygon.com - prediction script, double your coins by using this tool\n\n\t1\t2\t3\nEv-Hoang/Bedrock-Chest-Case-Opening\n\nHypixel Skyblock Dungeon Mod - Bedrock Chest Opening Animation (CSGO Style)\n\n\t1\t2\t3\njmjp/csgo-roulette\n\nA csgo gambling roulette make with VueJS 3\n\n\t2\t1\t3\nJustArchiNET/ArchiCrowdin\n\nNo description in the capture.\n\n\t1\t2\t3\nLeonSK/WearMarketInspector\n\nRetrieve Wear Value (Float Value) and Pattern Index from Steam Community Market using http://csgo.exchange API\n\n\t1\t2\t3\nmaximgeerinck/csgo-gamble\n\nCSGO gambling website\n\n\t1\t2\t3\nModDota/BugTracker\n\nListing bugs for Dota 2 Custom Games\n\n\t2\t1\t3\nplwp/mma-betting\n\nUFC/MMA betting model with Pinnacle steam detection for AU book latency arb\n\n\t2\t1\t3\nSouthsideswag16/Csgo-Gambling-Site\n\nNo description in the capture.\n\n\t2\t1\t3\ntacyarg/csgofiesta-frontend-react\n\nRemastered version a the long time favorite csgo site\n\n\t2\t1\t3\nVelorasse/Mutah-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-csmoney-csgoskins\n\ngambling script for Mutah, Keydrop, csmoney, and csgoskins, featuring hacks, cheats, and predictors. Offers strategies to boost winning odds and optimize performance on these platforms.\n\n\t3\t0\t3\nalliedmodders/am-github-artifact-webhook\n\nNo description in the capture.\n\n\t2\t0\t2\ncharamza/roulette\n\nCSGO like roulette in JS\n\n\t1\t1\t2\nCruze03/CSGO-PugSetup-RoundRestore\n\nSometimes (player dropped/crashed) which would be disadvantage for a team. It would be very handy to restore the match to the previous round.\n\n\t1\t1\t2\ncsgorol/CSGO-ROLL-Crash-Predictor\n\nCSGO-ROLL-Crash-Predictor\n\n\t1\t1\t2\nFoxSerito/FOXWORLD_plugin_DoubleJump_CSGO\n\nПлагин SourceMod (CSGO). Двойной прыжок с эффектом.\n\n\t1\t1\t2\nhkehayovmoonbiz/CS2-Casino-Full-Source-Code\n\nCS2, CS2 betting platforms, Skin Roulette, Case Unboxing, Crash games, Jackpot, purchase CS2 casino source, crypto gambling\n\n\t1\t1\t2\nJustZakary/steamstoreapi\n\nThis NPM module is a API wrapper that makes the steam unofficial API easier to use.\n\n\t2\t0\t2\njzimr/steam-market-api\n\nA java library to easily get Steam Community Market data\n\n\t1\t1\t2\nMomohime/CSGO.Network-Jackpot-Coinflip\n\nNo description in the capture.\n\n\t1\t1\t2\nnnjjswat/moneybot\n\nautomated bots for bustabit (formerly known as moneypot), csgo crash, etc\n\n\t0\t2\t2\nodota/carry\n\nLegacy Application for donations to the OpenDota project\n\n\t1\t1\t2\nodota/PublicMatchDataBot\n\nA Discord bot to remind users to turn on Expose Public Match Data in the Dota 2 client\n\n\t1\t1\t2\nOrillio/CSGOBet.com\n\nCSGO roulette web app\n\n\t2\t0\t2\nripexz/csgo-bet-alert\n\nA Chrome extension to keep track of active CS:GO Lounge matches.\n\n\t1\t1\t2\nrrpvm/lumen_sense-beta-deprecated-\n\nthis is internal csgo cheat written by me(no paste, self reverse structures). start : ~6 August 2020, end : ~ 14 December 2020\n\n\t1\t1\t2\nRuthless222/csgoscore\n\nThis is a Counter Strike Global Offensive Betting Site. You chose the skins you want to bet and try to win jackpots\n\n\t2\t0\t2\ntfburns/CSGO-cases-PL\n\nExpected profit-loss of CS:GO case openings\n\n\t1\t1\t2\nTomDra/CSGO-Case-Data-Analysis\n\nWorks out the most profitable CS:GO case at that current time\n\n\t1\t1\t2\nValvePython/dota2-wrappers\n\nNo description in the capture.\n\n\t1\t1\t2\nValvePython/teamfortress2-closed-captions\n\nThis project aims to provide a set of closed captions for Team Fortress 2\n\n\t1\t1\t2\nVistaNetGTX/Cstrike.bet-\n\nCSGO Roulette Website Angular frontend, nodejs backend, and steam trading bots\n\n\t1\t1\t2\nwafflas/csgo-case-opening-simulator\n\nI created a cs go case opening simulator for a meme coin\n\n\t0\t2\t2\nAdmiral-Enigma/Le_Coinflip\n\nConflip game\n\n\t1\t0\t1\nadryeljuliao/roulette-csgo\n\nNo description in the capture.\n\n\t1\t0\t1\nAndreuTheG/csgo-coinflip-web\n\nCSGO Gambling Coinflip Website\n\n\t1\t0\t1\nasmilen/csgoDouble\n\na b c\n\n\t1\t0\t1\nb1naryth1ef/csgofort\n\nA CSGO portal for trading, betting, analytics, and more!\n\n\t1\t0\t1\nBaterka/PrivateSteamBettingWebsite2024\n\nPrivate Steam (Counter-Strike 2) betting/gambling website - Roulette, Jackpot\n\n\t1\t0\t1\nblackcaer/SteamTradeHandler\n\nAutomation of Steam trading. Helper project for bet automation.\n\n\t1\t0\t1\nBTheCoderr/theRounders\n\nThe Rounders - A professional-grade sports betting analytics platform combining real-time odds tracking, sharp movement detection, and advanced statistical analysis. Features include line shopping, steam move alerts, power rankings, and comprehensive bet t…\n\n\t1\t0\t1\nCallumHemsley/KazeBot\n\nA Twitch chat betting bot for CSGO, simply bet a certain amount of points, and double if you win, lose all if you lose. Simple.\n\n\t1\t0\t1\nchrisjpm/CSGOJackpotTemplate\n\nFront end for a jackpot site\n\n\t1\t0\t1\ncolinsenner/valve-bug-bounty\n\nFor many years CS:GO, Dota 2, and Team Fortress 2 servers had a bug that allowed malicious users to leak crucial server process memory or reliably crash any server.\n\n\t1\t0\t1\ncoryypeters/nrl-odds-intelligence-pipeline\n\nReal-time sports betting odds intelligence — streaming pipeline that detects line movement, steam, and arbitrage across bookmakers. Python · Redis Streams · FastAPI · React.\n\n\t1\t0\t1\ndeissh/dev-csgoduo\n\nCS:GO. Bot for receiving things on the site (Polygon, Duo, Double and etc).\n\n\t1\t0\t1\ndom1torii/even-better-font-manager\n\nSimply even better cross-platform tool for CS2 Font Management\n\n\t1\t0\t1\nDONnicov/CSGO-crash-black-screen-\n\nsolution csgo crash black screen and close csgo\n\n\t1\t0\t1\nDoubleBoters/CsgoDouble\n\nNo description in the capture.\n\n\t1\t0\t1\ndownarowiczd/DoubleBot\n\nAn old CSGO Double Bot written for my friend. - 07.05.2016\n\n\t1\t0\t1\nErayBahar/steammarketscraper\n\nSteam Market Scraper Python-based tool that tracks real-time CS2 skin prices using Steam's hidden API. It fetches the lowest sell and highest buy offers for any item, helping you monitor deals or snipe underpriced listings automatically.\n\n\t1\t0\t1\nfairydarkness/SteamwebmailAPI\n\nUnofficial Python API for steamwebmail.com Fast, lightweight, and browserless library for automating steamwebmail.com. Support for session management, proxy, folder navigation, and message retrieval\n\n\t1\t0\t1\nFAQU2/CSGO-Coinflip-MyJailShop\n\nSourcemod plugin which provides a Coinflip system for MyJailShop.\n\n\t1\t0\t1\nFlamesONE/csgo-case-opening\n\nNo description in the capture.\n\n\t1\t0\t1\nFunnyRain/csgorun-crash-watch\n\n🚀 CsgoRun dump crash. / 🚀 CsgoRun дамп крашей.\n\n\t1\t0\t1\ngeohdgio/Venatus-Autenticator\n\nეს არის Steam Autenticator ქართული Venatus Trade & Betting ისთვის და Valve News Georgia-სთვის.\n\n\t1\t0\t1\nhakanstarlord/steam-bot\n\nSports betting steam-move signal detection with ML pipeline (XGBoost stacking + isotonic calibration), backtesting engine, Flask dashboard, and Telegram alerts.\n\n\t1\t0\t1\nHvH-gg/CSGO-Item-CrashFix\n\nA plugin for Counter-Strike: Global Offensive that fixes an exploit where receiving CS2 Items will cause CS:GO clients to crash\n\n\t1\t0\t1\nHvH-gg/CSGO-NetMsg-CrashFix\n\nA plugin for Counter-Strike: Global Offensive that fixes an exploit where spamming NetMsg_StringCmd packets would result in a server crash.\n\n\t1\t0\t1\nisybycnsmam/SteamLibrary\n\nLegacy Steam Unofficial API\n\n\t1\t0\t1\nItsTangerine/SteamApis.Net\n\nUnofficial https://steamapis.com .NET library, supporting .NET 6.0+\n\n\t1\t0\t1\nJustArchiNET/JustArchi.net\n\nNo description in the capture.\n\n\t1\t0\t1\nkiri-osint/CS2-Info-Hub-Bot\n\nA Telegram bot that acts as a hub for CS2 players, providing real-time skin prices, server stats, and user profile/inventory inspection using official and unofficial Steam APIs.\n\n\t1\t0\t1\nKoshkaj/monte\n\nGamified csgo gambling platform implementation\n\n\t1\t0\t1\nmadsab/CaseOpening\n\nA school project using Java. Simulating the case opening from CSGO and more.\n\n\t1\t0\t1\nman90es/steamcardexchange-api\n\nSteamCardExchange.net unofficial REST API server (scraper).\n\n\t1\t0\t1\nMattPua/steam-unofficial-docs\n\nUnofficial docs for Steam APIs with fumadocs\n\n\t1\t0\t1\nMetallist1/Portfolio.CsgoWinGambleProject\n\nA website that was done in 2017 September. Websites focus was on gambling with Counter-Strike items. Project was largely completed however backups were not done correctly, this resulted in half a year of wasted improvements to the code. The website was test…\n\n\t1\t0\t1\nmikebobadilla/csgo-jackpot\n\nNo description in the capture.\n\n\t0\t1\t1\nmikebobadilla/meteor-csgojackpot\n\nCssgo Jackpot done in meteor\n\n\t1\t0\t1\nModDota/D2VDump\n\nDota 2 Server VScript API Dumper\n\n\t1\t0\t1\nModDota/DotaTracking\n\nNo description in the capture.\n\n\t1\t0\t1\nModDota/eslint-config\n\nESLint config by ark120202\n\n\t1\t0\t1\nmr-codinglv/Casino-script\n\nscript casino - script betting - exchange script - bc casino - casino csgo - script bet - betwin script\n\n\t1\t0\t1\nMrKeelik/MrKeel\n\nCSGO DOUBLE BOT\n\n\t1\t0\t1\nnoahlatzel/CSGORollHelper\n\nLeveraging positive expected value on triple green jackpots on CSGORoll!\n\n\t1\t0\t1\noddsgpt/oddsgpt-market-intelligence\n\nResearch on football betting markets, closing odds, CLV, market efficiency, steam moves, AI betting systems, and sports market intelligence.\n\n\t1\t0\t1\noEXU/csgo-server-crasher\n\nCSGO SERVER CRASHER\n\n\t1\t0\t1\nPrdTTony/CSGO-Roulette\n\n[CSGO] Roulette System. Bet on RED or Black and win x2 credits\n\n\t1\t0\t1\nr-adamski/csgo-jackpot\n\nNo description in the capture.\n\n\t1\t0\t1\nSahotallo/Turan-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-Skinbaron-hellcase\n\ngambling script for Turan, Keydrop, Skinbaron, and Hellcase, providing hacks, cheats, and predictors. Includes strategies to improve winning chances and enhance gameplay on these platforms.\n\n\t1\t0\t1\nsamuelcsouza/steam-marketplace-api\n\nAn unofficial API to get data from the Steam Marketplace.\n\n\t1\t0\t1\nSKINSTRACK/CS2-Price-API\n\nSkinstrack offers a free, limited API endpoint that returns Steam item prices. Paid plans additionally provide access to pricing data from multiple marketplaces, making it possible to compare prices across different markets through a single API.\n\n\t1\t0\t1\nsnmtriet/CSGO-Casino-Full-Source-Code\n\nCSGO, CSGOEmpire, Case Opening, Case Battles, Roulette, Coinflip, buy csgo gambling site, gambling\n\n\t1\t0\t1\nSteamRE/homebrew-tools\n\nRepository for installation of SteamRE tools via Homebrew (http://brew.sh)\n\n\t1\t0\t1\nSteamRE/opensteamworks.org\n\nNo description in the capture.\n\n\t1\t0\t1\nTheQuack45/CsgoCaseOpenProgram\n\nSimple program to parse an XML file with CS:GO case information and \"simulate\" case openings\n\n\t1\t0\t1\nTLClassless/StratRouletteCSGO\n\nA 'Strat Roulette' web app for CS:GO!\n\n\t1\t0\t1\ntomasoom/csgoCaseOpening\n\nNo description in the capture.\n\n\t1\t0\t1\nvitaliy-evsyukov/steamgifts-autobet-bookmarklet\n\nbookmarklet for automatic bets on steamgifts.com\n\n\t1\t0\t1\nXpravdaX/RouletteCSGO\n\nNo description in the capture.\n\n\t1\t0\t1\nYuiKasumii/steam_api_unofficial\n\nUnofficial Steam Game Information Database\n\n\t1\t0\t1\nZexuz/Steam-Betting\n\nA betting website build ontop of STEAM's ecosystem\n\n\t1\t0\t1\nANK-RULZZ/steam-jackpot-site\n\ngetting some errors and would like some one to help me with it thank you!!!\n\n\t0\t0\t0\nasmilen/CsgoDoubleVS\n\nNo description in the capture.\n\n\t0\t0\t0\nCORNOODOSADAS/CSGOWeed\n\nCsgo Jackpot and Coinflip\n\n\t0\t0\t0\nCSGOApple/csgoapple\n\nJackpot Site\n\n\t0\t0\t0\nCSGOFAST/csgofast-api\n\nNo description in the capture.\n\n\t0\t0\t0\nDonakall/csgoDoublebot\n\nAutomated bot for csgodouble\n\n\t0\t0\t0\nfedor-selivanov/csgo-fast-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nfoldageros/csgod\n\ndouble bot\n\n\t0\t0\t0\ngmod-gambling/gmod-gambling\n\nNo description in the capture.\n\n\t0\t0\t0\nierome/CSGOBoss-BackEnd\n\nBack end version of CSGOBoss. This was a CSGO Gambling site named CSGOBoss. Coded by an old friend of mine Dahquan Hinds (https://github.com/dahquan/) Thought I would release this to help out any one who would need it.\n\n\t0\t0\t0\njamienp1/CSGODOUBLE-BOT-AUTO\n\ni got a bot thats is betting on the last winning color except from green and if you lose it will double the coins you set it to bet, pretty good, so when there comes a loooong train you will be gaining a bit of money codepaste_net/ugmt92 remove all the _ an…\n\n\t0\t0\t0\nJEYONER/CSGOTOXIC\n\nPAGINA DE JACKPOT CSGO SKINS\n\n\t0\t0\t0\nkalrish/csgo-jackpot\n\nStressful but funny zombie-like Counter-Strike: Global Offensive game mode.\n\n\t0\t0\t0\nkrys12345/roulettee\n\n// ==UserScript== // @name CSGO Predict Bot // @namespace http://csgodouble.com // @version 1.0 // @description predicts what number its gonna be // @author Meee // @match http://www.csgodouble.com/ // @grant none // ==/…\n\n\t0\t0\t0\nLilDuggiMuffi/CSGODouble-Working-Bot\n\nFixed CSGO Double Bot\n\n\t0\t0\t0\nLyricLy/Steam2Proton\n\nCheck if all your Steam games will work with Proton! Uses the official Steam API and the unofficial Proton API.\n\n\t0\t0\t0\nM0NsTeR77/csgo-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nozanhalis/Hi\n\n// ==UserScript== // @name CS GO LOUNGE BOT-Ozan Halis // @namespace http://csgolounge.com/ // @version 0.6.6 // @description Cs Go Lounge Hızlı BOT // @match http://csgolounge.com/* // @match http://dota2lounge.com/* // @updateURL h…\n\n\t0\t0\t0\nscoobertus/CSGO-DoubleBot\n\nNo description in the capture.\n\n\t0\t0\t0\nTradeal/CSGO-Jackpot-Bot\n\nNo description in the capture.\n\n\t0\t0\t0\nValvePython/artifact\n\nNo description in the capture.\n\n\t0\t0\t0\nVampire/CSGO-Roulette-Bot\n\nNo description in the capture.\n\n\t0\t0\t0\nvdemans/csgo-roulette\n\nNo description in the capture.\n\n\t0\t0\t0\nVocoreVideo/CSGODungeon-\n\nCSGO Jackpot\n\n\t0\t0\t0\nwayz-dev/csgofloat\n\nNo description in the capture.\n\n\t0\t0\t0\n\nBản chụp nhanh: 17 tháng 9 năm 2026, 11:19:11 như được ghi trong nguồn; múi giờ không được chỉ định. Bộ sưu tập mối quan hệ bị giới hạn trong tệp xuất (nhiều danh mục chỉ dừng lại ở 40). Tổng số người đóng góp và người phân nhánh tương ứng với 4,554 mục vai trò trên 4,214 cặp hồ sơ–kho lưu trữ riêng biệt; một hồ sơ có thể đảm nhận cả hai vai trò. Số 0 có nghĩa là không có bản ghi nào được ghi nhận trong danh mục đó. Tên kho lưu trữ có thể bao gồm các tên gọi khác hoặc các biến thể về chữ hoa/thường; tổng số vẫn tuân theo quy ước đếm của nguồn.\n\nNguồn gốc\nĐược tạo ra từ các tệp tin bạn đã thu thập.\nLời khai ủng hộ\n2323/reddit_scams_ultra/steam_support_tickets_MEGA.json · hàng 45, 58, 107, 110, 294\nẢnh chụp nhanh mạng\nnetwork-repositories.csv · raw_data.json · overlaps.csv · summary.txt (các đường dẫn nguồn lịch sử được giữ nguyên trong tệp manifest)\n\nBản kê khai ghi lại các đường dẫn nguồn, kích thước byte, các giá trị băm SHA-256 và vị trí của các bản ghi được chọn. Các bản ghi thô được tách biệt với phần phân tích của cuộc điều tra.\n\nTải xuống tệp manifest nguồn ↓",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam Bằng chứng thực thi — Hồ sơ hỗ trợ & Mạng lưới nhà phát triển"
          },
          {
            "level": 2,
            "id": null,
            "text": "Hãy đọc đơn khiếu nại.Hãy giữ nguyên tệp nguồn kèm theo."
          },
          {
            "level": 3,
            "id": null,
            "text": "Permanent sanction & closed appeals"
          },
          {
            "level": 4,
            "id": null,
            "text": "Permanently banned Steam account without a clear explanation, need help!"
          },
          {
            "level": 3,
            "id": null,
            "text": "Account recovery & a reported $10,000 loss"
          },
          {
            "level": 4,
            "id": null,
            "text": "Got $10k stollen from steam inventory due to steam' support fault."
          },
          {
            "level": 3,
            "id": null,
            "text": "A reported $500+ loss & template replies"
          },
          {
            "level": 4,
            "id": null,
            "text": "Funds stolen through steam market. Disappointed with Steam response.(or lackthereof)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Steam Guard & an item-restoration refusal"
          },
          {
            "level": 4,
            "id": null,
            "text": "Many people are losing item via clicking links where steam guard is enabled and steam support doesn't not restore items."
          },
          {
            "level": 3,
            "id": null,
            "text": "Selective enforcement & an unexplained ban"
          },
          {
            "level": 4,
            "id": null,
            "text": "🚨 Steam Bans Without Reason and Ignores Its Community — What’s Going On?"
          },
          {
            "level": 2,
            "id": null,
            "text": "Cơ sở hạ tầng công cộng.Được ghi lại trên quy mô lớn."
          },
          {
            "level": 2,
            "id": null,
            "text": "Được tạo ra từ các tệp tin bạn đã thu thập."
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/vi/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/vi/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/selected-support-records.json",
          "https://phishdestroy.io/steam_dossier/vi/investigation_part2.html#outsourcing-case",
          "https://www.reddit.com/r/ohnePixel/comments/1hahqx2/permanently_banned_steam_account_without_a_clear/",
          "https://www.reddit.com/r/legaladvice/comments/1kipjde/got_10k_stollen_from_steam_inventory_due_to_steam/",
          "https://www.reddit.com/r/DotA2/comments/vt76ov/funds_stolen_through_steam_market_disappointed/",
          "https://www.reddit.com/r/DotA2/comments/r55bd7/many_people_are_losing_item_via_clicking_links/",
          "https://www.reddit.com/r/SteamUncensored/comments/1kjt2fa/steam_bans_without_reason_and_ignores_its/",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/network-repositories.csv",
          "https://github.com/alliedmodders/amxmodx",
          "https://github.com/alliedmodders/sourcemod",
          "https://github.com/DoctorMcKay/node-steam-user",
          "https://github.com/Facepunch/Facepunch.Steamworks",
          "https://github.com/JustArchiNET/ArchiSteamFarm",
          "https://github.com/odota/core",
          "https://github.com/odota/dotaconstants",
          "https://github.com/odota/web",
          "https://github.com/splewis/get5",
          "https://github.com/SteamDatabase/FileDetectionRuleSets",
          "https://github.com/SteamRE/SteamKit",
          "https://github.com/ValveSoftware/dxvk",
          "https://github.com/ValveSoftware/GameNetworkingSockets",
          "https://github.com/ValveSoftware/gamescope",
          "https://github.com/ValveSoftware/Proton",
          "https://github.com/ValveSoftware/source-sdk-2013",
          "https://github.com/ValveSoftware/wine",
          "https://github.com/ValveSoftware/steam-devices",
          "https://github.com/ValveSoftware/steam-audio",
          "https://github.com/alliedmodders/metamod-source",
          "https://github.com/alliedmodders/sourcepawn",
          "https://github.com/ValveSoftware/Fossilize",
          "https://github.com/rlabrecque/Steamworks.NET",
          "https://github.com/ModDota/moddota.github.io",
          "https://github.com/odota/parser",
          "https://github.com/ValveSoftware/steam-for-linux",
          "https://github.com/SteamRE/DepotDownloader",
          "https://github.com/JustArchiNET/ASF-ui",
          "https://github.com/advancedfx/advancedfx",
          "https://github.com/alliedmodders/ambuild",
          "https://github.com/SteamDatabase/BrowserExtension",
          "https://github.com/odota/mobile",
          "https://github.com/ValvePython/steam",
          "https://github.com/skadistats/clarity",
          "https://github.com/SteamRE/open-steamworks",
          "https://github.com/ValveSoftware/Source-1-Games",
          "https://github.com/alliedmodders/hl2sdk",
          "https://github.com/SteamDatabase/steamdb.info-issues",
          "https://github.com/CSGOFloat/inspect",
          "https://github.com/ValveSoftware/SteamOS",
          "https://github.com/alliedmodders/source2mod",
          "https://github.com/smiley/steamapi",
          "https://github.com/SteamDatabase/GameTracking",
          "https://github.com/ValveSoftware/counter-strike_rules_and_regs",
          "https://github.com/ValveSoftware/openvr",
          "https://github.com/SteamDatabase/easy-markdown-editor",
          "https://github.com/ValveSoftware/Dota-2",
          "https://github.com/ValveSoftware/Dota2-Gameplay",
          "https://github.com/JustArchiNET/ArchiBot",
          "https://github.com/ztizzlegaming/CSGOWinBig",
          "https://github.com/JustArchiNET/mantis.justarchi.net",
          "https://github.com/odota/node-steam-user",
          "https://github.com/ModDota/TypeScriptAddonTemplate",
          "https://github.com/ValvePython/vdf",
          "https://github.com/alliedmodders/amtl",
          "https://github.com/ValvePython/dota2",
          "https://github.com/alliedmodders/stripper-source",
          "https://github.com/Allyans3/steam-market-api-v2",
          "https://github.com/ModDota/dota-tutorial",
          "https://github.com/odota/blog",
          "https://github.com/OpsecGuy/BetterGo",
          "https://github.com/pxvr-official/1",
          "https://github.com/Revadike/InternalSteamWebAPI",
          "https://github.com/JoeSzymkowiczFiveM/qb-lootcrate",
          "https://github.com/AbrarKL/MyRoulette.XYZ",
          "https://github.com/JustArchiNET/ASF-WebConfigGenerator",
          "https://github.com/ModDota/dota-data",
          "https://github.com/ModDota/TypeScriptDeclarations",
          "https://github.com/ModDota/API",
          "https://github.com/alliedmodders/cssdm",
          "https://github.com/SteamDatabase/steamstat.us",
          "https://github.com/c0deina/csgojackpotV2",
          "https://github.com/ValvePython/steamctl",
          "https://github.com/ValvePython/csgo",
          "https://github.com/BeepIsla/csgo-crash-exploit",
          "https://github.com/ValvePython/vpk",
          "https://github.com/alliedmodders/SM-SteamWorks",
          "https://github.com/SteamRE/Steam4NET",
          "https://github.com/alliedmodders/hl2sdk-manifests",
          "https://github.com/JustArchiNET/ASF-PluginTemplate",
          "https://github.com/ModDota/Dota2AIFramework",
          "https://github.com/Shkyyl/KeyChamp",
          "https://github.com/SteamDatabase/SteamMonitor",
          "https://github.com/Baterka/cslore.com",
          "https://github.com/SteamDatabase/SteamTokenDumper",
          "https://github.com/monoblocker/roulette",
          "https://github.com/zsith/launcher.user.js",
          "https://github.com/LincolnIT/CSGODouble-bot-automated",
          "https://github.com/vladpuz/steam-market",
          "https://github.com/mcgrizzz/Cstrike.bet",
          "https://github.com/odota/underlords-web",
          "https://github.com/SteamDatabase/SteamToTwitter",
          "https://github.com/ModDota/AbilityLuaSpellLibrary",
          "https://github.com/alvinl/bitskins",
          "https://github.com/b1naryth1ef/steamy",
          "https://github.com/kratos1812/Case-Opening",
          "https://github.com/odota/docs",
          "https://github.com/SteamDatabase/steam-advanced-access-fetch-players",
          "https://github.com/TheRioMiner/CsgoBetterExternalRaytrace",
          "https://github.com/alliedmodders/hl2sdk-mock",
          "https://github.com/christophersu/PySteamMarket",
          "https://github.com/Extremelyd1/Strat-Roulette",
          "https://github.com/giovanni-orciuolo/double-sdk",
          "https://github.com/JustArchiNET/Madness",
          "https://github.com/ModDota/TypescriptPanoramaDeclarations",
          "https://github.com/odota/rapier",
          "https://github.com/Vozn1akHero/CSGOCaseOpeningSimulator",
          "https://github.com/autarc/steam-store",
          "https://github.com/BETTING-CODE/awesome-esports-sites",
          "https://github.com/jonteohr/Better-Warden",
          "https://github.com/Ludzikk/CSGO-Gambling-Site",
          "https://github.com/ModDota/find-steam-app",
          "https://github.com/mprey/csgocact.us",
          "https://github.com/nezu-cc/ServerCrasher",
          "https://github.com/odota/testfiles",
          "https://github.com/odota/underlordsconstants",
          "https://github.com/SnaBe/node-steam-market-fetcher",
          "https://github.com/SteamDatabase/.github",
          "https://github.com/wolfcon/RIP-HLTV-BET",
          "https://github.com/alliedmodders/blaster.net",
          "https://github.com/catears124/CS2-Price-API",
          "https://github.com/ialakey/caseforge",
          "https://github.com/Ilusion9/csgo-fix-mapchange-crash-sm",
          "https://github.com/ismail0234/Benson-Map-Crash-Fixer",
          "https://github.com/jaxwilko/steam-market-api",
          "https://github.com/JustArchiNET/ArchiTag",
          "https://github.com/ModDota/DotaUI",
          "https://github.com/node-steam/market-pricing",
          "https://github.com/odota/media",
          "https://github.com/SergeyIvanovDevelop/Crypto-Steam-Platform",
          "https://github.com/Aareksio/csgodouble-floatchecker",
          "https://github.com/chinm4/CSGOdrop",
          "https://github.com/Cruze03/CSGO-Case-Opening-Prank",
          "https://github.com/Dhruva-Kapadia/CSGOTrollGG",
          "https://github.com/ErhanCSGO/CSGOPolygon-prediction",
          "https://github.com/Ev-Hoang/Bedrock-Chest-Case-Opening",
          "https://github.com/jmjp/csgo-roulette",
          "https://github.com/JustArchiNET/ArchiCrowdin",
          "https://github.com/LeonSK/WearMarketInspector",
          "https://github.com/maximgeerinck/csgo-gamble",
          "https://github.com/ModDota/BugTracker",
          "https://github.com/plwp/mma-betting",
          "https://github.com/Southsideswag16/Csgo-Gambling-Site",
          "https://github.com/tacyarg/csgofiesta-frontend-react",
          "https://github.com/Velorasse/Mutah-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-csmoney-csgoskins",
          "https://github.com/alliedmodders/am-github-artifact-webhook",
          "https://github.com/charamza/roulette",
          "https://github.com/Cruze03/CSGO-PugSetup-RoundRestore",
          "https://github.com/csgorol/CSGO-ROLL-Crash-Predictor",
          "https://github.com/FoxSerito/FOXWORLD_plugin_DoubleJump_CSGO",
          "https://github.com/hkehayovmoonbiz/CS2-Casino-Full-Source-Code",
          "https://github.com/JustZakary/steamstoreapi",
          "https://github.com/jzimr/steam-market-api",
          "https://github.com/Momohime/CSGO.Network-Jackpot-Coinflip",
          "https://github.com/nnjjswat/moneybot",
          "https://github.com/odota/carry",
          "https://github.com/odota/PublicMatchDataBot",
          "https://github.com/Orillio/CSGOBet.com",
          "https://github.com/ripexz/csgo-bet-alert",
          "https://github.com/rrpvm/lumen_sense-beta-deprecated-",
          "https://github.com/Ruthless222/csgoscore",
          "https://github.com/tfburns/CSGO-cases-PL",
          "https://github.com/TomDra/CSGO-Case-Data-Analysis",
          "https://github.com/ValvePython/dota2-wrappers",
          "https://github.com/ValvePython/teamfortress2-closed-captions",
          "https://github.com/VistaNetGTX/Cstrike.bet-",
          "https://github.com/wafflas/csgo-case-opening-simulator",
          "https://github.com/Admiral-Enigma/Le_Coinflip",
          "https://github.com/adryeljuliao/roulette-csgo",
          "https://github.com/AndreuTheG/csgo-coinflip-web",
          "https://github.com/asmilen/csgoDouble",
          "https://github.com/b1naryth1ef/csgofort",
          "https://github.com/Baterka/PrivateSteamBettingWebsite2024",
          "https://github.com/blackcaer/SteamTradeHandler",
          "https://github.com/BTheCoderr/theRounders",
          "https://github.com/CallumHemsley/KazeBot",
          "https://github.com/chrisjpm/CSGOJackpotTemplate",
          "https://github.com/colinsenner/valve-bug-bounty",
          "https://github.com/coryypeters/nrl-odds-intelligence-pipeline",
          "https://github.com/deissh/dev-csgoduo",
          "https://github.com/dom1torii/even-better-font-manager",
          "https://github.com/DONnicov/CSGO-crash-black-screen-",
          "https://github.com/DoubleBoters/CsgoDouble",
          "https://github.com/downarowiczd/DoubleBot",
          "https://github.com/ErayBahar/steammarketscraper",
          "https://github.com/fairydarkness/SteamwebmailAPI",
          "https://github.com/FAQU2/CSGO-Coinflip-MyJailShop",
          "https://github.com/FlamesONE/csgo-case-opening",
          "https://github.com/FunnyRain/csgorun-crash-watch",
          "https://github.com/geohdgio/Venatus-Autenticator",
          "https://github.com/hakanstarlord/steam-bot",
          "https://github.com/HvH-gg/CSGO-Item-CrashFix",
          "https://github.com/HvH-gg/CSGO-NetMsg-CrashFix",
          "https://github.com/isybycnsmam/SteamLibrary",
          "https://github.com/ItsTangerine/SteamApis.Net",
          "https://github.com/JustArchiNET/JustArchi.net",
          "https://github.com/kiri-osint/CS2-Info-Hub-Bot",
          "https://github.com/Koshkaj/monte",
          "https://github.com/madsab/CaseOpening",
          "https://github.com/man90es/steamcardexchange-api",
          "https://github.com/MattPua/steam-unofficial-docs",
          "https://github.com/Metallist1/Portfolio.CsgoWinGambleProject",
          "https://github.com/mikebobadilla/csgo-jackpot",
          "https://github.com/mikebobadilla/meteor-csgojackpot",
          "https://github.com/ModDota/D2VDump",
          "https://github.com/ModDota/DotaTracking",
          "https://github.com/ModDota/eslint-config",
          "https://github.com/mr-codinglv/Casino-script",
          "https://github.com/MrKeelik/MrKeel",
          "https://github.com/noahlatzel/CSGORollHelper",
          "https://github.com/oddsgpt/oddsgpt-market-intelligence",
          "https://github.com/oEXU/csgo-server-crasher",
          "https://github.com/PrdTTony/CSGO-Roulette",
          "https://github.com/r-adamski/csgo-jackpot",
          "https://github.com/Sahotallo/Turan-Gambling-Script-Hack-Cheat-Predictor-Strategies-Keydrop-Skinbaron-hellcase",
          "https://github.com/samuelcsouza/steam-marketplace-api",
          "https://github.com/SKINSTRACK/CS2-Price-API",
          "https://github.com/snmtriet/CSGO-Casino-Full-Source-Code",
          "https://github.com/SteamRE/homebrew-tools",
          "https://github.com/SteamRE/opensteamworks.org",
          "https://github.com/TheQuack45/CsgoCaseOpenProgram",
          "https://github.com/TLClassless/StratRouletteCSGO",
          "https://github.com/tomasoom/csgoCaseOpening",
          "https://github.com/vitaliy-evsyukov/steamgifts-autobet-bookmarklet",
          "https://github.com/XpravdaX/RouletteCSGO",
          "https://github.com/YuiKasumii/steam_api_unofficial",
          "https://github.com/Zexuz/Steam-Betting",
          "https://github.com/ANK-RULZZ/steam-jackpot-site",
          "https://github.com/asmilen/CsgoDoubleVS",
          "https://github.com/CORNOODOSADAS/CSGOWeed",
          "https://github.com/CSGOApple/csgoapple",
          "https://github.com/CSGOFAST/csgofast-api",
          "https://github.com/Donakall/csgoDoublebot",
          "https://github.com/fedor-selivanov/csgo-fast-roulette",
          "https://github.com/foldageros/csgod",
          "https://github.com/gmod-gambling/gmod-gambling",
          "https://github.com/ierome/CSGOBoss-BackEnd",
          "https://github.com/jamienp1/CSGODOUBLE-BOT-AUTO",
          "https://github.com/JEYONER/CSGOTOXIC",
          "https://github.com/kalrish/csgo-jackpot",
          "https://github.com/krys12345/roulettee",
          "https://github.com/LilDuggiMuffi/CSGODouble-Working-Bot",
          "https://github.com/LyricLy/Steam2Proton",
          "https://github.com/M0NsTeR77/csgo-roulette",
          "https://github.com/ozanhalis/Hi",
          "https://github.com/scoobertus/CSGO-DoubleBot",
          "https://github.com/Tradeal/CSGO-Jackpot-Bot",
          "https://github.com/ValvePython/artifact",
          "https://github.com/Vampire/CSGO-Roulette-Bot",
          "https://github.com/vdemans/csgo-roulette",
          "https://github.com/VocoreVideo/CSGODungeon-",
          "https://github.com/wayz-dev/csgofloat",
          "https://phishdestroy.io/steam_dossier/output_steam_network/raw_data.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/enforcement-source-manifest.json"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/vi/steam_enforcement_evidence.content.json",
      "export_json_sha256": "dad8d282bf49da29dce53fed0cc6f5e3c211b3649f56e9719fd429969439ca1e"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "vi/steam_evidence_archive.html",
      "language": "vi",
      "title": "Kiểm tra các nguồn tin — Hồ sơ về “Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/vi/steam_evidence_archive",
      "source_html_sha256": "bdc22bbd7e0d9ea842d8c33094762aa5e009e8c5e9be78581d47f7377f606bde",
      "exported_at": "2026-09-29T00:23:09.303Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "steam_evidence_archive.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/vi/steam_evidence_archive.pdf?v=print-20260929-v5",
        "sha256": "5fb006462fbd4d9bc0a7eb4908bb156aea56910c15542ba6f8b3fb2ceedd9637",
        "bytes": 67733,
        "pages": 4
      },
      "integrity": {
        "signed_object": "steam_evidence_archive.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "steam_evidence_archive.content.json.asc",
        "digest_file": "steam_evidence_archive.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify steam_evidence_archive.content.json.asc steam_evidence_archive.content.json",
          "sha256sum -c steam_evidence_archive.content.json.sha256"
        ]
      },
      "content": {
        "text": "TÀI LIỆU ĐIỀU TRA / THU THẬP NGUỒN THÔNG TIN 002\nSteam Kho lưu trữ bằng chứng — Các tài liệu có nguồn gốc từ 16,319\n\nMọi yêu cầu bồi thường. Quay trở lại nguồn gốc.\n\nPHẦN NÀY CHỨNG MINH ĐIỀU GÌ\n\nKho lưu trữ pháp y này lập chỉ mục các bản ghi nguồn gốc từ 16,319 — bao gồm tài liệu của Cộng đồng Nhà phát triển Valve, các vấn đề công khai trên GitHub, các khiếu nại đã được xác minh trên Trustpilot và các báo cáo diễn đàn đã được lưu trữ — bằng các hàm băm mật mã và nhật ký nguồn gốc. Kho lưu trữ này cung cấp một cơ sở bằng chứng có thể kiểm tra, chứng minh các lỗ hổng nền tảng có thể tái hiện, các tính năng bị loại bỏ mà không được ghi chép tại API, cũng như các khiếu nại liên tục từ người tiêu dùng về các tài khoản bị chiếm quyền kiểm soát.\n\n← Quay lại Bản tóm tắt dành cho lãnh đạo\n\nTìm bản ghi liên quan đến một tuyên bố. Lọc theo nguồn, mở toàn văn và truy cập liên kết gốc. Các hàng nguồn có thể trùng lặp; một bản ghi không phải là một sự cố đã được xác minh.\n\nQuay lại cuộc điều tra ↗\n354TRUSTPILOT / CÁC HÀNG NGUỒN\n208REDDIT / NGUỒN DỮ LIỆU\n705GITHUB / CÁC DÒNG MÃ NGUỒN\n15,302MASTER CSV / CÁC HÀNG NGUỒN\n16,319 SỐ LIỆU — PHÂN TÍCH THEO LOẠI NỀN TẢNG\n\nNguồn gốc danh mục Wiki (Các bản ghi 7,620 · 46.7%): Dữ liệu được trích xuất từ Cộng đồng Nhà phát triển Valve (developer.valvesoftware.com), Tài liệu/Câu hỏi thường gặp (FAQ) của SteamDB, và các trang wiki của cộng đồng game (Liquipedia CS/Dota và Fandom Steam) thông qua các bản chụp tự động của WARC và các điểm cuối MediaWiki API trong khoảng thời gian từ tháng 8 2024 đến tháng 9 2026. Tất cả các mục 7,620 đều được tích hợp đầy đủ vào tệp xuất CSV chính (TOTAL_VALVE_SCANDALS_MASTER_DB.csv).\n\nWiki\n7,620\nReddit\n5,635\nGitHub\n2,395\nTrustpilot\n393\nTrang web\n276\n9,116 trong số các bản ghi trên 16,319 (55.8%) có chứa các liên kết đến Steam / Valve\n\nKho lưu trữ có thể tìm kiếm này được xây dựng trên 2026-09-17 từ các tệp xuất nguồn được liệt kê ở trên. Tệp xuất dữ liệu chính riêng biệt “40,448-” được sử dụng ở các phần khác trong hồ sơ có phạm vi khác. Xem tạo tệp manifest đối với số liệu thống kê của kho lưu trữ này; các bản ghi có thể trùng lặp và không phải là các sự cố riêng biệt.\n\nNỀN TẢNG NGUỒN\nTHU THẬP NGUỒN\nSteam / Valve đề cập\nSo khớp văn bản hoặc kho lưu trữ “Valve”Văn bản bị thiếu / đã bị xóa\n16,569 các hàng nguồn\n16,319 các bản ghi riêng biệt\n249 các hàng trùng lặp đã được hợp nhất\n1 hàng bị loại trừ\nXem các tệp gốc ↘\n★TRUSTPILOT2015-10-16#1RATING 1/5\n\nSteam is the biggest PC gaming platform without a doubt. A power which could be abused but Steam for the most part doesn't. Overall a definite download for any moden digital age PC gamer. It mu... See more\n\nMA · 7 source copies\n★TRUSTPILOT2021-06-18#2RATING 1/5\n\nThey scam people for money, dont believe me? Read this Source: Steam Subscribers/User Agreement NO GUARANTEES TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, NEITHER VALVE NOR ITS AFFILIA... See more\n\nWF · 7 source copies\n★TRUSTPILOT2016-10-28#3RATING 1/5\n\nSupport on site is terrible. Refunds not happend yet, despite games not working. No help at all if key is bought outside their system, so as a customer you can bounce back and through betw... See more\n\nPE · 7 source copies\n★TRUSTPILOT2021-09-27#4RATING 1/5\n\nThey are an amazing company!! My boyfriend paid for and downloaded a game without realizing it wasn’t the version he wanted. When he reached out, they gave him a full refund and responded in the same... See more\n\nVH · 7 source copies\n★TRUSTPILOT2026-07-20#5RATING 1/5\n\nI’ve used Steam for years, but lately, their sales have really lost their edge. I was hoping to score some solid discounts, but many games still feel overpriced, even during sales. Plus, the support response times can be frustratingly slow when issues arise.\n\nCR\n★TRUSTPILOT2025-12-10#6RATING 1/5\n\nI new here , but all my firends had great experience with this platform . They can make money\n\nZeinab Nematollahi\n★TRUSTPILOT2025-11-18#7RATING 1/5TEXT UNAVAILABLE\n\nNo text was included in the source record.\n\nEM\n★TRUSTPILOT2025-10-21#8RATING 1/5\n\nusing steam for over a decade and i have no words how good the platform is. some friends recommended it to me back in 2015 when we wanted to play csgo together and since then im loggin on it on a daily basis to check new games\n\nTrustpilot\n★TRUSTPILOT2025-05-09#9RATING 1/5\n\nSupport are never able to help you and only able to redicrect you to public linkBreaking there own TOSNot able to provider a refundNot able to provide a safe place for gamingBase on the game you play you can get scam.\n\nSym Link · 7 source copies\n★TRUSTPILOT2025-05-09#10RATING 1/5TEXT UNAVAILABLE\n\nNo text was included in the source record.\n\nHearnius\n★TRUSTPILOT2024-12-30#11RATING 1/5\n\nThis company allowed a single phishing scammer 76561199443342045 in 100's of its user community chat rooms \"Steam Chat\" the whole week of Winter Sales, 12-23-2024 - 2025 to spam spaceintrader a scam phishing website.Don't support Valve & Steam that support sca…\n\nFR · 7 source copies\n★TRUSTPILOT2024-11-15#12RATING 1/5\n\nVery realiable! Ive never had an issue over the 11 years ive had steam.\n\nJM\nBản dựng và các tệp nguồn của nó\n\nKho lưu trữ này hợp nhất các bản ghi trùng lặp từ 249 và loại trừ một bản ghi khỏi dữ liệu đầu vào tại 16,569, từ đó còn lại 16,319 bản ghi riêng biệt. Một bản ghi có thể mô tả một sự kiện đã được đề cập trong một bản ghi khác. Tính năng tìm kiếm bao gồm tiêu đề, tác giả, nhãn nguồn và các đoạn trích được hiển thị; toàn bộ văn bản đã lưu sẽ được mở ra cùng với mỗi bản ghi.\n\nTải xuống bốn tệp xuất nguồn ↓Số lượng tệp và các giá trị băm SHA-256 ↗Bản kê khai bản dựng gốc ↗\n\nGói này chứa các tệp xuất đã được khôi phục, khớp với số hàng của bản dựng và ba đường dẫn JSON đã được ghi lại. Bản dựng ban đầu không ghi lại các giá trị băm đầu vào hay đường dẫn tệp CSV chính; tệp bản kê kèm theo ghi lại các tệp đã được khôi phục và kết quả so sánh với chỉ mục đã được công bố.\n\nTrustpilot · steam_support_reviews.json354 hàng · Xuất dưới dạng JSON\nReddit · reddit_censored_forensics.json208 hàng · Xuất dưới dạng JSON\nGitHub · valve_ignored_bugs.json705 hàng · Xuất dưới dạng JSON; tên tệp là nhãn của bộ thu thập\nBản chính · TOTAL_VALVE_SCANDALS_MASTER_DB.csv15,302 các hàng · Tệp CSV xuất ra để so sánh\nDanh sách vụ án · UNSEALED_EXHIBITS_AND_AML_DOSSIER.mdWolfire kiện Valve – các email đã được công khai, lời khai của Gabe Newell, lời thú nhận của Oct2019về AML\nThông tin cơ bản · FACTS_AND_CITATIONS_DATABASE.md1,638 các trích dẫn riêng lẻ đã được xác minh liên quan đến các khía cạnh chống độc quyền và an ninh củ35\nLưu trữ hỗ trợ · support_canned_refusals.html1,505 hồ sơ vé · 137 ảnh chụp màn hình được lưu giữ · Tìm kiếm tức thì trực tuyến\nCác trường bản ghi, văn bản bị thiếu và các tệp xuất trùng lặp\n\nNgày tháng, xếp hạng, danh mục và trạng thái bài đăng được sao chép nguyên vẹn từ nguồn xuất. Một URL bị thiếu sẽ vẫn bị thiếu. Các dấu hiệu “[đã xóa]” hoặc “[đã gỡ bỏ]” không cho biết ai đã xóa bài đăng đó hay lý do tại sao. Bộ lọc Steam / Valve dựa trên sự khớp văn bản, chứ không phải đánh giá mức độ liên quan.\n\n“Xuất các kết quả khớp” sẽ tải xuống các mục chỉ mục kèm theo các đoạn trích; “Tải xuống bản ghi” bao gồm toàn bộ văn bản đã lưu. Tệp riêng biệt 40,448-bảng chính CSV và 1,690-dòng GitHub CSV Đó là tổng kim ngạch xuất khẩu, chứ không phải số lượng nguồn cho phiên bản này.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam Kho lưu trữ bằng chứng — Các tài liệu có nguồn gốc từ 16,319"
          },
          {
            "level": 2,
            "id": null,
            "text": "NỀN TẢNG NGUỒN"
          },
          {
            "level": 2,
            "id": null,
            "text": "Bản dựng và các tệp nguồn của nó"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/vi/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/vi/",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/TOTAL_VALVE_SCANDALS_MASTER_DB.csv",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive_manifest.json",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive-inputs.zip",
          "https://phishdestroy.io/steam_dossier/steam_tos_assets/archive-inputs-manifest.json",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/unsealed_legal_and_aml/UNSEALED_EXHIBITS_AND_AML_DOSSIER.md",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/forensic_facts_1000/FACTS_AND_CITATIONS_DATABASE.md",
          "https://phishdestroy.io/steam_dossier/vi/support_canned_refusals.html",
          "https://phishdestroy.io/steam_dossier/VALVE_EVIDENCE_PACK/databases/github_valve_unpatched_bugs.csv"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/vi/steam_evidence_archive.content.json",
      "export_json_sha256": "33b11ee05a49476806b20f6ead8c9f6b56f8099ced5a014bdf49df6ec912b801"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "vi/support_canned_refusals.html",
      "language": "vi",
      "title": "Steam Lưu trữ các trường hợp từ chối hỗ trợ và câu trả lời mẫu — Hồ sơ “Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/vi/support_canned_refusals",
      "source_html_sha256": "9c84404aef1975b2688a0d0a06960cfdbd98c8d0b2d6509fc15cc7ef532ae7cc",
      "exported_at": "2026-09-29T00:23:10.697Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "support_canned_refusals.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/vi/support_canned_refusals.pdf?v=print-20260929-v5",
        "sha256": "a00f0c9ffa3b81a08ff3e5f5f584e7e67bbb99f4c75a0189159767c5218079cc",
        "bytes": 65796,
        "pages": 2
      },
      "integrity": {
        "signed_object": "support_canned_refusals.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "support_canned_refusals.content.json.asc",
        "digest_file": "support_canned_refusals.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify support_canned_refusals.content.json.asc support_canned_refusals.content.json",
          "sha256sum -c support_canned_refusals.content.json.sha256"
        ]
      },
      "content": {
        "text": "PHẦN NÀY CHỨNG MINH ĐIỀU GÌ\n\nKho lưu trữ này ghi lại các ảnh chụp màn hình gốc được lưu giữ tại 137 và các đơn khiếu nại của nạn nhân đã được kiểm toán tại 1,505, trong đó nêu chi tiết quy trình xử lý phiếu hỗ trợ tự động của Valve. Điều này chứng minh rằng khi các tài khoản bị xâm phạm thông qua chuyển hướng OpenID hoặc việc tạo khóa API trái phép, bộ phận Hỗ trợ của Steam đã có hệ thống sử dụng các mẫu từ chối chuẩn hóa mà không tiến hành điều tra kỹ thuật. Bằng cách từ chối một cách dứt khoát việc khôi phục vật phẩm hoặc tiết lộ nhật ký kiểm toán, nền tảng này chuyển toàn bộ trách nhiệm pháp lý về các lỗ hổng xác thực mang tính cấu trúc sang cho chủ sở hữu các tài khoản bị xâm phạm.\n\nTất cả các ảnh chụp màn hình đều là các bản chụp do bên thứ ba thực hiện. Bản quyền và nội dung thuộc về các tác giả và nền tảng tương ứng (người dùng Reddit, các tác giả của cộng đồng Steam, người đánh giá trên Trustpilot, X và những người đăng tải trên YouTube). Các ảnh chụp màn hình này được sao chép lại chỉ nhằm mục đích nhận diện và đưa tin vì lợi ích công cộng; chúng tôi không tuyên bố sở hữu bất kỳ quyền nào đối với chúng. Mỗi tài liệu minh họa đều có liên kết đến nguồn gốc ban đầu của nó.\n\nFigures reported on the source page\nMeasure\tReported value\tScope\nHồ sơ được lưu trữ\t1505\tCác bài đăng khiếu nại của nạn nhân đã được xác minh và các chuỗi bài về vé\nCác ảnh chụp màn hình được lưu giữ\t137\tBản chụp vé độ phân giải cao được lưu trữ cục bộ\nTỷ lệ phục hồi\t0.0%\tCác quyết định hủy bỏ đã được ban hành trong các vụ chiếm đoạt tàu chở dầu mang tên “API”\nSao chép mẫu\t100%\tTái sử dụng kịch bản nguyên văn giữa các nhân viên (Ilya, Roger, Maverick)\nChứng cứ pháp y: Ba trụ cột chính của việc từ chối hỗ trợ\nTRỤ CỘT 01 · TUYỂN SINHTài liệu R-014\nLời thừa nhận của Roger: Xác nhận vụ tấn công MitM trên API\n\nTrong phản hồi yêu cầu hỗ trợ số1cp582i, Steam, nhân viên hỗ trợ “Roger” thừa nhận bằng văn bản rằng những kẻ tấn công hủy các giao dịch hợp lệ thông qua API và thay thế chúng bằng các bot giả mạo chỉ trong vài mili giây, nhưng từ chối khôi phục các vật phẩm và yêu cầu nạn nhân tìm đến một “kỹ thuật viên máy tính địa phương”.\n\nKiểm tra giấy nhập học ↗\nTRỤ CỘT 02 · THẨM QUYỀN XỬ LÝTài liệu R-012\n7-Giao dịch trong ngày – Giữ vị thế – Không thực hiện hành động nào\n\nMột nạn nhân đã cung cấp SteamID64 của các tài khoản thuộc về hacker trong khoảng thời gian tạm ngưng giao dịch trong ngày của sự kiện “7-”. Nhân viên hỗ trợ “Artem” và “Ilya” đã từ chối khóa các vật phẩm bị đánh cắp, với lý do vật phẩm ảo này rất hiếm, và đã đóng phiếu yêu cầu bằng một mẫu trả lời tự động.\n\nXem bảng điểm của nhiều nhân viên ↗\nTRỤ CỘT 03 · CHÍNH SÁCHTài liệu R-002\nTình trạng khan hiếm trên thị trường so với quyền sở hữu tài sản\n\nChính sách hoàn trả vật phẩm chính thức của Valve nêu rõ rằng vật phẩm sẽ không được hoàn trả vì việc hoàn trả chúng sẽ “làm giảm tính khan hiếm và thổi phồng nền kinh tế, từ đó làm giảm giá trị của các vật phẩm trên Thị trường Cộng đồng”.\n\nXem ảnh chụp màn hình Chính sách ↗\nNguồn gốc lịch sử · 22 Tháng 3 năm 2018 đến 2026\nPhụ lục H -003 · 8-Diện tích tấn công chưa được vá trong năm\nTrường hợp thay thế hàng hóa được ghi chép sớm nhất (22 March 2018)\n\nChính xác một tuần trước khi Valve áp dụng quy định gây tranh cãi về thời gian chờ 7-đối với các vật phẩm trong Counter-Strike, cộng đồng giao dịch đã phát hiện những trường hợp đầu tiên trên thực tế về việc Steam Lỗ hổng khai thác chuyển hướng giao dịch trên trang web API. Những kẻ tấn công đã chiếm quyền điều khiển các phiên truy cập web để tạo ra một khóa API trái phép tại steamcommunity.com/dev/apikey không cần xác nhận từ ứng dụng di động 2FA, cho phép các bot hủy và hoán đổi giao dịch theo thời gian thực.\n\nThông báo cảnh báo của PSA tháng 3 năm 2018: \"Những kẻ lừa đảo có thể tự động phát hiện đề nghị giao dịch này và sẽ từ chối nó trên tài khoản của bạn, bởi vì chúng có khóa Steam API của bạn. Lúc này, bot lừa đảo sẽ gửi cho bạn một đề nghị giao dịch với những skin tương tự... và bạn sẽ không nhận ra sự khác biệt nào cả!\"\nCon đường Dấu vết Lịch sử\n22 2018: tháng 3 Lần đầu tiên được ghi nhận về việc hoán đổi API\n2019: Hỗ trợ tiêu chuẩn hóa việc ngăn chặn “phần mềm độc hại”\n2020: Tăng cường bảo mật cho tập lệnh \"Đóng yêu cầu trợ giúp\"\n2022–2026: Tự động hóa lừa đảo qua BitB và mã QR\nMở chủ đề gốc trên Reddit về “2018” ↗\nPrimary sources\n\n137 gallery cards refer to 78 distinct primary URLs. Images and repeated exhibit captions are omitted from this reading edition.\n\nFull visual archive and original captures",
        "headings": [
          {
            "level": 2,
            "id": null,
            "text": "Figures reported on the source page"
          },
          {
            "level": 2,
            "id": null,
            "text": "Chứng cứ pháp y: Ba trụ cột chính của việc từ chối hỗ trợ"
          },
          {
            "level": 3,
            "id": null,
            "text": "Lời thừa nhận của Roger: Xác nhận vụ tấn công MitM trên API"
          },
          {
            "level": 3,
            "id": null,
            "text": "7-Giao dịch trong ngày – Giữ vị thế – Không thực hiện hành động nào"
          },
          {
            "level": 3,
            "id": null,
            "text": "Tình trạng khan hiếm trên thị trường so với quyền sở hữu tài sản"
          },
          {
            "level": 3,
            "id": null,
            "text": "Trường hợp thay thế hàng hóa được ghi chép sớm nhất (22 March 2018)"
          },
          {
            "level": 2,
            "id": null,
            "text": "Primary sources"
          }
        ],
        "links": [
          "https://www.reddit.com/r/csgo/comments/1cp582i/i_got_api_scammed_what_do_i_do_now/",
          "https://www.reddit.com/r/DotA2/comments/1e5ovy4/my_account_was_hacked_and_steam_support_refuse/",
          "https://www.reddit.com/r/Steam/comments/3b2abd/steam_will_no_longer_restore_scammed_items_item/",
          "https://www.reddit.com/r/GlobalOffensiveTrade/comments/863tk1/psa_urgent_huge_scam_happening_read_here_how_to",
          "https://phishdestroy.io/steam_dossier/vi/support_canned_refusals#gallery-grid"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/vi/support_canned_refusals.content.json",
      "export_json_sha256": "7050c372d55f0b7717ee94ecd8cd3c3b1e555e5637ae42941afcaa0d5e1687d9"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "vi/valve_scandals_registry.html",
      "language": "vi",
      "title": "Valve Cơ sở dữ liệu các vụ bê bối — Hồ sơ về vụ “Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/vi/valve_scandals_registry",
      "source_html_sha256": "ba4fe517250ebfcebde3d6c2868526470d23aefc956e4d34f0b6b22b4de6ad17",
      "exported_at": "2026-09-29T00:23:11.063Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "valve_scandals_registry.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/vi/valve_scandals_registry.pdf?v=print-20260929-v5",
        "sha256": "f47e56136e2314c1d1e52952201c944d397416b85478c133781bdc1dbc75d33e",
        "bytes": 67339,
        "pages": 6
      },
      "integrity": {
        "signed_object": "valve_scandals_registry.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "valve_scandals_registry.content.json.asc",
        "digest_file": "valve_scandals_registry.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify valve_scandals_registry.content.json.asc valve_scandals_registry.content.json",
          "sha256sum -c valve_scandals_registry.content.json.sha256"
        ]
      },
      "content": {
        "text": "Kho lưu trữ các vụ bê bối lớn\nValve Cơ sở dữ liệu tổng hợp các vụ bê bối — 160 Các vụ việc được ghi nhận\nTÀI LIỆU NGUỒN (DỮ LIỆU THÔ): 11,768\n\nĐã được báo cáo. Đã xác minh nguồn. Vẫn đang được xử lý.\n\nPHẦN NÀY CHỨNG MINH ĐIỀU GÌ\n\nCơ sở dữ liệu tổng hợp này tập hợp các bản ghi gốc đã được xác minh độc lập tại 160, trong đó nêu chi tiết các lỗ hổng nền tảng tồn tại dai dẳng, các báo cáo từ cộng đồng đã bị xóa và những sự cố trong dịch vụ hỗ trợ khách hàng chưa được giải quyết trong toàn bộ hệ sinh thái của Valve. Bao gồm các hồ sơ tranh chấp đã được xác minh trên Trustpilot, các phiếu báo cáo sự cố bảo mật đã được lưu trữ tại GitHub và các thủ tục tố tụng của cơ quan quản lý, cơ sở dữ liệu này chỉ ra những sự cố hệ thống lặp đi lặp lại trong quá trình khôi phục tài khoản và giải quyết tranh chấp của khách hàng.\n\n← Quay lại Bản tóm tắt dành cho lãnh đạo\n\n160 các bản ghi đã thu thập: các hoạt động hỗ trợ được người dùng đánh giá, các chuỗi thảo luận không còn hiển thị, các lỗ hổng nền tảng đã được báo cáo nhưng chưa được xử lý, và những sự cố mà Valve đã phải giải trình. Không có nội dung nào ở đây là nhận định của chúng tôi — mỗi dòng đều kèm theo nguồn gốc ban đầu. Hãy mở một mục và tự mình đọc.\n\nHồ sơ nguồn\n11,768\nTrên tất cả các hạng mục\nCác lỗ hổng của nền tảng\n3,372\nCác lỗ hổng trên nền tảng do cộng đồng báo cáo\nCác chủ đề bị kiểm duyệt\n109\nCác bài đăng trên Reddit bị người điều hành xóa\nHỗ trợ giải quyết khiếu nại\n471\nCác khiếu nại đã được xác minh trên Trustpilot\nKhả năng thực thi\nChặn tên miền máy chủ xác thực\n\nViệc chặn các máy chủ xác thực OpenID ở cấp độ tên miền về mặt kỹ thuật rất dễ thực hiện: một khi một tài nguyên đã bị cấm chuyển hướng đăng nhập Steam, các tên miền của bên thứ ba đóng vai trò là máy chủ proxy xác thực cho chính tài nguyên đó cũng có thể được lọc bằng cùng một bộ quy tắc. Phần tài liệu chính đã trình bày chi tiết về khả năng thực hiện.\n\nXem tính khả thi của việc thi hành trong hồ sơ →\nDanh mục: Khiếu nại hỗ trợ Trustpilot (Các trường hợp tiêu cực đã được lọc để chuyển lên cấp trên)176 các bản ghi nguồn khớp nhau · các bản ghi trùng lặp đã được gộp lại\nConsumer Complaint2026-07-20\nAuthor: C***\n\nI’ve used Steam for years, but lately, their sales have really lost their edge. I was hoping to score some solid discounts, but many games still feel overpriced, even during sales. Plus, the support response times can be frustratingly slow when issues arise.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2026-07-20\nConsumer Complaint2025-05-09\nAuthor: S*** L***\n\nSupport are never able to help you and only able to redicrect you to public linkBreaking there own TOSNot able to provider a refundNot able to provide a safe place for gamingBase on the game you play you can get scam.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2025-05-09\nConsumer Complaint2024-12-30\nAuthor: F***\n\nThis company allowed a single phishing scammer 7656…2045 in 100's of its user community chat rooms \"Steam Chat\" the whole week of Winter Sales, 12-23-2024 - 2025 to spam spaceintrader a scam phishing website.Don't support Valve & Steam that support scams. Don't give your log in credentials to account hijacking scammers. This company also allows engagements of commercial advertising / spam for gambling in violation of its own Rules and Guidelines / Online Conduct. 7656…5023 proof - groups/deskinsfans key drop advertising, thanks TannerfromKD and Valve!*\"The Consumer Review Fairness Act (CRFA) protects people’s ability to share their honest opinions about a business’s products, services, or conduct, in any forum, including social media. The law protects a broad variety of honest consumer assessments, including online reviews, social media posts, uploaded photos, videos, etc. And it doesn’t just cover product reviews. It also applies to consumer evaluations of a company\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2024-12-30\nConsumer Complaint2024-07-31\nAuthor: A***\n\nhorrible company.randomly you get \"This account may have been accessed by someone else.\"this happened to me 3 times.the 3rd time they wanted a cd key.a spent useless cd key that nobody has any reason to keep laying around.i gave them the paypal bill for my first purchase back in 2015.i gave them a bill for my first phone number ever on the account.i still got the same email attached to the account.this company is literally a scam. nothing but a scam.they randomly claim you been accessed somewhere else and then require you to give them information no reasonable person would ever have, if not your done and have to rebuy everything.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2024-07-31\nConsumer Complaint2023-12-09\nAuthor: K***\n\nHad 288 euros in steam wallet, someone hacked my account even with two step verification, write a steam support for help but only answer was if something is spent in community market they can’t help.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2023-12-09\nConsumer Complaint2023-09-26\nAuthor: J***\n\nI was banned for saying \"Who let grandma on the PC\"and another for simply calling someone ignorant.Power tripping mods, devs who don't care, steam doesn't care. Yet allows racism/trolling/etc Fk steam, its a joke now.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2023-09-26\nConsumer Complaint2022-08-31\nAuthor: Anonymous\n\nSteam community is plain bad for a various reasons:1. Steam forums are a big mess, for example they allow users to post in any language and as result you get jumbled mess with posts in foreign languages together with English language posts. For example, If you check CS GO forums, you'll see half of posts are in Russian and half in English. I don't understand why such a big and international company would leave their forums so unorganized like that. All other normal companies have English only language allowed which is an international language and sometimes subforums for other languages like German, French and etc... so if French people want to post in French they go specifically in that sub-forum. But no, Steam doesn't care about this. Their forums is a one big mess.2. Moderation is biased and joke. I don't understand why such a big company like Steam can't afford to hire people for moderation and pay them. Instead they just recruit random people for moderation who do it for free and\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2022-08-31\nConsumer Complaint2022-05-28\nAuthor: J***\n\nThe login code never arrives. I hate Steam.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2022-05-28\nConsumer Complaint2021-11-08\nAuthor: N***\n\nThe service is terrible, I only signed up because I really like the game I wanted, but the rest is terrible, I hope to get something better soon.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-11-08\nConsumer Complaint2021-06-18\nAuthor: W***\n\nThey scam people for money, dont believe me? Read thisSource: Steam Subscribers/User Agreement NO GUARANTEESTO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, NEITHER VALVE NOR ITS AFFILIATES GUARANTEE CONTINUOUS, ERROR-FREE, VIRUS-FREE OR SECURE OPERATION AND ACCESS TO STEAM, THE CONTENT AND SERVICES, YOUR ACCOUNT AND/OR YOUR SUBSCRIPTION(S) OR ANY INFORMATION AVAILABLE IN CONNECTION THEREWITH.In short: You got a virus or your data leaked because of our software? Whoopsies we dont care, that isnt even legal or the last of their scammy stuff...\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-06-18\nConsumer Complaint2021-05-14\nAuthor: B***\n\nThe support is one of the worst I've ever seen.Useless support team.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2021-05-14\nConsumer Complaint2020-04-02\nAuthor: J***\n\nSteamcommunity has 15% fees, 15!!!!\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2020-04-02\nConsumer Complaint2020-03-27\nAuthor: H***\n\nWhat can I say? the support is one of the worst I've ever seen maybe the FUNCOM is much worse. If you tell the true on the steam forum you just got a BAN even if what you said did not violated the rules of the forum.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2020-03-27\nConsumer Complaint2018-03-16\nAuthor: B***\n\ndon't sign up will stick on your computer will kill your pc power you can't remove it from your pc even you deleted it will stay woking in the system\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2018-03-16\nConsumer Complaint2016-12-27\nAuthor: J***\n\nIn bloddy hate their page it's tiresome, it's in no way intuitive. I tried reaching out for support, but that is a maze.I'm simply trying to log in and redeem a key of a product I already bought, their search function is a joke. I f*u*c*k*i*n*g hate them. The layout is not like the how to video from the dealer, this can be done much simpler. I don't frigin care aboutn what other titles you have in store or what genre, I just want to redeem my key and install.\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-12-27\nConsumer Complaint2016-10-28\nAuthor: P***\n\nSupport on site is terrible.Refunds not happend yet, despite games not working.No help at all if key is bought outside their system, so as a customer you can bounce back and through between bad support systems?? I wait for some other companies to compete in this market, for this can't be the best we as customers can expect.And do put an email up to find, instead of this stuppid website where you spend so long time trying to find a solution on, instead of a simple mail. Often the problem is not there, or if it's there just saying no help here???I need a response\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-10-28\nConsumer Complaint2016-06-26\nAuthor: V*** W***\n\nUseless support as always!\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2016-06-26\nConsumer Complaint2014-07-01\nAuthor: J***\n\nexpensive, and support team not willing to cooperate\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2014-07-01\nConsumer Complaint2014-04-15\nAuthor: B***\n\nWhen you pay for a program, you expect it too work. cant not buy or anything and have written to valve. but there is not a being done a damn thing abut it..\n\nTarget Domain: steamcommunity.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2014-04-15\nConsumer Complaint2026-09-03\nAuthor: M***\n\nWorst platform ever wont give me a refund even though a game is unplayable because of bugs I won't ever be using the crap platform again I hope the platform breaks down for good piece fo crao\n\nTarget Domain: steamcommunity.com / steampowered.com\nInspect on Trustpilot ↗\nDocumented support grievance\nCaptured: 2026-09-03\n\nKhông tìm thấy kết quả phù hợp\n\nHãy thử điều chỉnh truy vấn hiện tại hoặc chuyển sang tab danh mục khác.\n\n1 / 9",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Valve Cơ sở dữ liệu tổng hợp các vụ bê bối — 160 Các vụ việc được ghi nhận"
          },
          {
            "level": 2,
            "id": null,
            "text": "Chặn tên miền máy chủ xác thực"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: C***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: S*** L***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: F***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: A***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: K***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: Anonymous"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: N***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: W***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: H***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: P***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: V*** W***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: J***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: B***"
          },
          {
            "level": 3,
            "id": null,
            "text": "Author: M***"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/vi/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/vi/#autoban-feasibility-section",
          "https://www.trustpilot.com/review/steamcommunity.com"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/vi/valve_scandals_registry.content.json",
      "export_json_sha256": "15de08f99da3c9dafe411680c753bbe58ced585726dac980024559722fecfb39"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "vi/output_steam_network/index.html",
      "language": "vi",
      "title": "Kiến trúc, không phải lỗ hổng: Mạng lưới tự động hóa — Hồ sơ về “Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/vi/output_steam_network/index",
      "source_html_sha256": "8b077cddb8b9b0da5d4270d4541722adcb0b563220cfd1256f858cf2699c3b08",
      "exported_at": "2026-09-29T00:23:11.064Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__index.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/vi/output_steam_network__index.pdf?v=print-20260929-v5",
        "sha256": "73c826ebb807950fa63d176c2aa1d067f4502dd15fafbd5f14b5c7e0cdb6e2d9",
        "bytes": 72553,
        "pages": 3
      },
      "integrity": {
        "signed_object": "output_steam_network__index.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__index.content.json.asc",
        "digest_file": "output_steam_network__index.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__index.content.json.asc output_steam_network__index.content.json",
          "sha256sum -c output_steam_network__index.content.json.sha256"
        ]
      },
      "content": {
        "text": "Phụ lục VII · Phân tích kiến trúc kỹ thuật\nSteam Kiến trúc mạng — Độ chính xác của giao thức và phân tích hệ sinh thái\n\nTự động hóa chính là triết lý kiến trúc củValve. Không phải là lỗ hổng bảo mật.\n\nPHẦN NÀY CHỨNG MINH ĐIỀU GÌ\n\nMô-đun này mô tả cấu trúc kỹ thuật của các kho lưu trữ dành cho nhà phát triển 252, các hồ sơ 3,320 GitHub và các cặp cộng tác viên 4,214 làm nền tảng cho hệ sinh thái tự động hóa Steam. Nó chứng minh rằng các giải pháp tự động hóa của bên thứ ba dựa trên giao thức Connection Manager chính thức của Valve, các lược đồ Protobuf và các API web mà không chứa mã khai thác lỗ hổng. Bằng cách thiết kế các mã thông báo xác nhận thuật toán Steam Guard và thu phí giao dịch tối thiểu lên đến 66.7%, Valve, đóng vai trò là kiến trúc sư chủ chốt và bên hưởng lợi thương mại chính từ các hoạt động của hệ sinh thái tự động hóa.\n\n← Quay lại Bản tóm tắt dành cho lãnh đạo\n\nKhi Valve hướng tới các cơ quan quản lý, các đơn vị xử lý thanh toán hoặc nạn nhân của các vụ lừa đảo, trang web này quy trách nhiệm cho việc đánh cắp skin và thao túng thị trường là do “các hành vi khai thác trái phép của bên thứ ba” và “tự động hóa bất hợp pháp”. Thực tế kỹ thuật của mạng lưới kho lưu trữ 252-lại chứng minh điều hoàn toàn ngược lại: Mọi khung công nghệ tự động hóa, bot giao dịch và đội máy khai thác đều hoạt động hoàn toàn tuân thủ các định nghĩa chính thức của giao thức, các API web và các cơ chế xác thực do Công ty Valve thiết kế, tài liệu hóa và thương mại hóa.\n\nKết luận pháp y: Kiến trúc có chủ đích so với hành vi xâm nhập trái phép\n\nPhần mềm được phân tích trong mô-đun này — bao gồm SteamKit, node-steam-user, ValvePython/steam, và ArchiSteamFarm — bao gồm không có lỗ hổng phần mềm, không có sự cố hỏng bộ nhớ và không có lỗ hổng zero-day. Đây là các bản triển khai mã nguồn mở, sạch sẽ và ổn định của giao thức khách hàng Connection Manager (CM) độc quyền củValve, Google Protocol Buffers (Protobufs) và các API web. Valve đã thiết kế các API này để hỗ trợ đăng nhập tự động, đồng thời phát triển Steam Guard nhằm cho phép sử dụng các mã xác nhận thuật toán (identity_secret), và thu một khoản phí được quảng cáo là “15%” (phí dịch vụ không hoàn lại) có mức tăng dần lên đến lên đến 66.7% nghiêng về phía Valve trên các giao dịch thẻ có tốc độ cao và các đợt bán tháo hàng hóa mà các mạng bot tự động thanh lý.\n\nTrụ cột 01 · Tuân thủ giao thức\nCác lược đồ Protobuf chính thức\n\nCác thư viện tự động hóa không bỏ qua các rào cản bảo mật. Chúng chuyển đổi các thông điệp Protobuf chính thức sang dạng chuỗi (steammessages_clientserver.proto) qua TCP/WebSockets trực tiếp đến các cụm CM chính thức của Valve, hoàn toàn giống như cách mà ứng dụng khách Steam thực hiện.\n\nPillar 02 · Algorithmic 2FA\nỦy quyền giao dịch theo chương trình\n\nToàn bộ nền kinh tế buôn bán da trị giá hàng tỷ đô la phụ thuộc vào Valve's IEconService API và các khóa xác thực TOTP trên thiết bị di động. Valve đã chủ động phát triển Steam Guard nhằm cho phép xác nhận giao dịch giữa các máy với nhau.\n\nTrụ cột 03 · Bên thụ hưởng thương mại\nLưu lượng truy cập từ máy được tạo doanh thu: Mức phí tối thiểu lên đến 66.7%\n\nValve quảng cáo mức phí “15%”, nhưng đối với các mặt hàng tiêu dùng có khối lượng giao dịch lớn mà các bot tự động giao dịch — thẻ sưu tập, hộp thẻ và các mặt hàng giá rẻ có giá từ $0.03 đến $0.05 — mức phí tối thiểu 2 cent của Valve ($0.01Steam + $0.01 publisher) sẽ được tính 50% đến 66.7% theo yêu cầu của Valve (2¢ được trích từ thẻ 3¢, khiến người bán chỉ còn lại 1¢). Cộng thêm $5.00 cho mỗi tài khoản ($26.8M chỉ tính riêng trên đội xe được quét).\n\nMô-đun 01 · Bằng chứng về kho lưu trữ và giao thức\nCơ sở hạ tầng công khai dành cho nhà phát triển và kho lưu trữ\n\nDanh mục phân tích chi tiết về các kho lưu trữ mã nguồn mở 252 hỗ trợ quá trình tự động hóa trên Steam. Phân tích cách các công cụ kỹ thuật phần mềm tiêu chuẩn triển khai các điểm cuối API do Valve công bố mà không sử dụng các lỗ hổng bảo mật.\n\n252Kho lưu trữ\n4,554Liên kết vai trò\nKiểm tra bằng chứng trong kho lưu trữ →Mô-đun 02 · Dân số học hệ sinh thái\nCác chỉ số về hệ sinh thái kỹ thuật toàn cầu\n\nPhân tích theo khu vực địa lý và tổ chức của các kỹ sư phần mềm thuộc nhóm “3,320” đang đóng góp vào hệ sinh thái tự động hóa “Steam”, bao gồm cả mối quan hệ công tác tại các tập đoàn công nghệ hàng đầu.\n\n3,320Kỹ sư\n98,902Các cặp kết nối\nKiểm tra các chỉ số hệ sinh thái →Mô-đun 03 · Biểu đồ trực quan tương tác\nBiểu đồ giao thức tương tác và mạng lưới nhà phát triển\n\nBản đồ đồ thị mạng tương tác toàn diện trên Vis.js, bao gồm các kho lưu trữ, thư viện giao thức (SteamKit, Steamworks, ASF) và sự trùng lặp giữa các nhà đóng góp giữa các dự án. Minh họa một cách trực quan kiến trúc phần mềm mã nguồn mở hợp pháp và liên kết chặt chẽ, là nền tảng cho hệ sinh thái tự động hóa của Steam.\n\nTương tácVis.js Động cơ\nCách ly cụmTìm kiếm trực tiếp\nKhông có lỗ hổng bảo mậtCác API tiêu chuẩn\nMở biểu đồ mạng tương tác →\nBối cảnh pháp lý và quy định (Bài viết trên GDPR 25 và Bảo vệ người tiêu dùng):\nTheo nguyên tắc “Bảo vệ dữ liệu ngay từ thiết kế và theo mặc định” (Data Protection by Design and by Default), một kiến trúc nền tảng cho phép tạo khóa xác thực (API) một cách âm thầm, hủy giao dịch mà không thông báo và thanh lý tài sản tự động bằng máy là sự lựa chọn về kiến trúc của nhà điều hành nền tảng. Khi Valve có hệ thống từ chối các yêu cầu bồi thường của người tiêu dùng bằng cách khẳng định rằng các khoản lỗ là do “các cuộc tấn công mạng từ bên ngoài” gây ra, họ đang che giấu thực tế rằng vectơ tấn công chính là kiến trúc Web API do chính Valve thiết kế một cách có chủ đích.\n\nCHẾ ĐỘ XEM TƯƠNG TÁC\n\nBản trực quan hóa tương tác đầy đủ của kho lưu trữ “252-”, đồ thị mạng các nhà phát triển “3,320-” có sẵn tại network.html. Các chỉ số tổng hợp được hiển thị trên Các chỉ số BI trang.\n\nHồ sơ “Steam” · Kho lưu trữ kiến trúc kỹ thuật · Hồ sơ nguồn mở · Tất cả các quyền được nhượng lại cho nhân loại.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam Kiến trúc mạng — Độ chính xác của giao thức và phân tích hệ sinh thái"
          },
          {
            "level": 3,
            "id": null,
            "text": "Các lược đồ Protobuf chính thức"
          },
          {
            "level": 3,
            "id": null,
            "text": "Ủy quyền giao dịch theo chương trình"
          },
          {
            "level": 3,
            "id": null,
            "text": "Lưu lượng truy cập từ máy được tạo doanh thu: Mức phí tối thiểu lên đến 66.7%"
          },
          {
            "level": 2,
            "id": null,
            "text": "Cơ sở hạ tầng công khai dành cho nhà phát triển và kho lưu trữ"
          },
          {
            "level": 2,
            "id": null,
            "text": "Các chỉ số về hệ sinh thái kỹ thuật toàn cầu"
          },
          {
            "level": 2,
            "id": null,
            "text": "Biểu đồ giao thức tương tác và mạng lưới nhà phát triển"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/vi/#briefing-heading",
          "https://phishdestroy.io/steam_dossier/vi/output_steam_network/valve_ru_farming_isolated.html",
          "https://phishdestroy.io/steam_dossier/vi/output_steam_network/steam_ecosystem_dashboard.html",
          "https://phishdestroy.io/steam_dossier/vi/output_steam_network/network.html"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/vi/output_steam_network__index.content.json",
      "export_json_sha256": "3d773e8abc633af8efba1145f18472163ee5c11e7beadc2031c99a2dd7cd90b5"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "vi/output_steam_network/network.html",
      "language": "vi",
      "title": "Trình khám phá nhà phát triển và kho lưu trữ — Hồ sơ về “Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/vi/output_steam_network/network",
      "source_html_sha256": "97aa6b0887625c1ff6c32c92ca3067be683d0bcc82d099b4b92cad41c52dc404",
      "exported_at": "2026-09-29T00:23:12.583Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__network.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/vi/output_steam_network__network.pdf?v=print-20260929-v5",
        "sha256": "4aec72664b2aee4f328a81ba5a13e08876632e7af6f7e8a037537ff921b837ec",
        "bytes": 38964,
        "pages": 1
      },
      "integrity": {
        "signed_object": "output_steam_network__network.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__network.content.json.asc",
        "digest_file": "output_steam_network__network.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__network.content.json.asc output_steam_network__network.content.json",
          "sha256sum -c output_steam_network__network.content.json.sha256"
        ]
      },
      "content": {
        "text": "Trình khám phá nhà phát triển và kho lưu trữ\n\nTìm kiếm một nút. Kiểm tra mối quan hệ đã được ghi lại.\n\nHỒ SƠ CÔNG CỘNG / CÁC MỐI LIÊN HỆ ĐƯỢC THU THẬP\nTìm kiếm trực tiếp\nLớp bộ lọc\nTổng số nhà phát triển3,320\nTổng số giao dịch repo252\nBIỂU ĐỒ HIỂN THỊ / TỤC TẬP CON468 NODES • 1103 EDGES\nBản ghi hồ sơ đã chọn\n\n💡 Nhấp vào bất kỳ nút nào trên đồ thị hoặc nhập vào ô Tìm kiếm để xem các kết nối và đường dẫn nguồn đã thu thập của nút đó.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Trình khám phá nhà phát triển và kho lưu trữ"
          }
        ],
        "links": []
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/vi/output_steam_network__network.content.json",
      "export_json_sha256": "f9054bae8522b346a5a5c080f1bd881259c4b8d8651e9bca3d824f35f4c78615"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "vi/output_steam_network/steam_ecosystem_dashboard.html",
      "language": "vi",
      "title": "Mạng lưới được thu thập qua các con số — Hồ sơ “Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/vi/output_steam_network/steam_ecosystem_dashboard",
      "source_html_sha256": "5eecf7a4501e0f40a1ba0e281dfb500a5225aeacf4e44909dfd6e9a7346f917f",
      "exported_at": "2026-09-29T00:23:12.339Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__steam_ecosystem_dashboard.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/vi/output_steam_network__steam_ecosystem_dashboard.pdf?v=print-20260929-v5",
        "sha256": "26a09bdef84fdff15c6c954667267d1493c28cdae7be3a5b69b9e6208c40b146",
        "bytes": 43003,
        "pages": 2
      },
      "integrity": {
        "signed_object": "output_steam_network__steam_ecosystem_dashboard.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__steam_ecosystem_dashboard.content.json.asc",
        "digest_file": "output_steam_network__steam_ecosystem_dashboard.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__steam_ecosystem_dashboard.content.json.asc output_steam_network__steam_ecosystem_dashboard.content.json",
          "sha256sum -c output_steam_network__steam_ecosystem_dashboard.content.json.sha256"
        ]
      },
      "content": {
        "text": "TỔNG QUAN VỀ THỐNG KÊ // TẬP TIN02\nSteam Bảng điều khiển hệ sinh thái — Mạng lưới qua các con số\n\nMạng lưới, qua các con số.\n\nPHẦN NÀY CHỨNG MINH ĐIỀU GÌ\n\nBảng điều khiển này tổng hợp thông tin phân tích cấu trúc từ các nhà phát triển trên 3,320 và các kho lưu trữ trên 252, nhằm xác định các cơ sở mã nguồn dành riêng cho cờ bạc tại 68 cũng như các cầu nối liên nền tảng. Dữ liệu thực nghiệm nêu bật sự tập trung theo khu vực địa lý và sự trùng lặp giữa các nhà phát triển, cho thấy cơ sở hạ tầng cờ bạc của các “skin” bên thứ ba hoạt động như một ngành công nghiệp phần mềm có tổ chức, kết nối chặt chẽ và được tích hợp với nền tảng của Steam.\n\n← Quay lại Bản tóm tắt dành cho lãnh đạo\n\nThống kê tổng hợp từ cơ sở dữ liệu điều tra: phân bố địa lý, các công ty hàng đầu, kho dữ liệu về cờ bạc trực tuyến và các cầu nối kết nối đang hoạt động.\n\nNhóm phát triển Scanned3320\nTổng số giao dịch repo252\nCác báo cáo về cờ bạc68\nTổng số kết nối1,426\nCấu trúc và các lĩnh vực của tự động hóa\nKhu vực I — Trung tâm Công tyValve\n\nCác kho phần mềm chính thức và phần mềm hệ thống. Không gian phát triển đã được xác nhận của hai nhân viên Valve là Nephyrin và Joe Ludwig.\n\nPhân khúc II — Công cụ cấp phép và trình mô phỏng giao thức (SteamKit)\n\nCác thư viện mạng được phân tích ngược, do Nephyrin từ Valve và DoctorMcKay – nhà phát triển trò chơi cá cược – đồng tác giả.\n\nLĩnh vực III — Khách hàng khai thác thẻ (ArchiSteamFarm)\n\nSử dụng các trình mô phỏng giao thức SteamKit để chạy hàng triệu client giả (ở trạng thái không hoạt động) ở chế độ nền nhằm thu thập thẻ giao dịch.\n\nPhân bố địa lý của các nhà phát triển\nĐức57\nHoa Kỳ52\nCanada48\nVương quốc Anh44\nBa Lan30\nPháp28\nLiên bang Nga27\nTrung Quốc27\nHoa Kỳ (bang Washington)23\nÚc19",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Steam Bảng điều khiển hệ sinh thái — Mạng lưới qua các con số"
          },
          {
            "level": 3,
            "id": null,
            "text": "Khu vực I — Trung tâm Công tyValve"
          },
          {
            "level": 3,
            "id": null,
            "text": "Phân khúc II — Công cụ cấp phép và trình mô phỏng giao thức (SteamKit)"
          },
          {
            "level": 3,
            "id": null,
            "text": "Lĩnh vực III — Khách hàng khai thác thẻ (ArchiSteamFarm)"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/vi/#briefing-heading"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/vi/output_steam_network__steam_ecosystem_dashboard.content.json",
      "export_json_sha256": "11f062623cc4a3b773ff848e2a02084e230c7e381e69f7dc748cbe5de8860859"
    },
    {
      "schema": "phishdestroy.text-export.v1",
      "object_type": "Published page text and corresponding PDF digest",
      "id": "vi/output_steam_network/valve_ru_farming_isolated.html",
      "language": "vi",
      "title": "Mã nguồn, những người đóng góp và các phiên bản phân nhánh — Hồ sơ về “Steam”",
      "source_url": "https://phishdestroy.io/steam_dossier/vi/output_steam_network/valve_ru_farming_isolated",
      "source_html_sha256": "86348b78bf85384ec8702cef65cef8ba9456e62ee0771b5dafa396b20197d62d",
      "exported_at": "2026-09-29T00:23:12.716Z",
      "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
      "editorial_scope": {
        "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
        "linked_sections": [],
        "raster_images_replaced": 0
      },
      "license": {
        "identifier": "CC0-1.0",
        "url": "https://creativecommons.org/publicdomain/zero/1.0/",
        "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
        "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
        "application": "Authored research materials; third-party materials retain their own rights."
      },
      "pdf": {
        "filename": "output_steam_network__valve_ru_farming_isolated.pdf",
        "url": "https://phishdestroy.io/steam_dossier/exports/pages/vi/output_steam_network__valve_ru_farming_isolated.pdf?v=print-20260929-v5",
        "sha256": "636766c748c47a68eb1d279bd24cbf7ba7b1b57f1cd35184ae19a7eaef66d85f",
        "bytes": 46637,
        "pages": 2
      },
      "integrity": {
        "signed_object": "output_steam_network__valve_ru_farming_isolated.content.json",
        "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
        "signature_file": "output_steam_network__valve_ru_farming_isolated.content.json.asc",
        "digest_file": "output_steam_network__valve_ru_farming_isolated.content.json.sha256",
        "format": "ASCII-armored detached OpenPGP",
        "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
        "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
        "verify": [
          "gpg --import pgp-key.txt",
          "gpg --verify output_steam_network__valve_ru_farming_isolated.content.json.asc output_steam_network__valve_ru_farming_isolated.content.json",
          "sha256sum -c output_steam_network__valve_ru_farming_isolated.content.json.sha256"
        ]
      },
      "content": {
        "text": "PHẦN II / THEO DÕI MỐI QUAN HỆ ĐÃ ĐƯỢC GHI CHÉP\n\nCác nhánh (forks), đóng góp và các phụ thuộc phần mềm là những bằng chứng rõ ràng. Quan điểm này vẫn giữ nguyên các vai trò đã được thu thập; các trường hợp liên quan đến việc làm, vi phạm an ninh và dính líu đến tội phạm cần có thêm các nguồn tham khảo.\n\nMở bản đồ năng lực tương tác ↗\nNGUỒN THÔNG TIN CÔNG KHAI / KIỂM TOÁN CHỨC NĂNG\nMã nguồn. Những người đóng góp. Các nhánh.\n1. Nephyrin: các nhánh và đóng góp\n\nBản chụp nhanh được cung cấp ghi nhận Nephyrin là người đóng góp cho ValveSoftware/Proton và là người phân nhánh các dự án SteamRE/SteamKit và SteamRE/open-steamworks. Dữ liệu hồ sơ của người này liệt kê Valve Software. Các trường thông tin này cần được xem xét riêng biệt.\n\nMột nhánh ghi lại một bản sao của kho lưu trữ. Việc xuất này không kèm theo một commit ghi nhận các thay đổi đối với mã xác thực SteamKit.\nTham chiếu kho lưu trữ / xem lịch sử\nSteamRE/SteamKit ↗ SteamRE/open-steamworks ↗\n2. Các tính năng công khai: tự động hóa mà không cần ứng dụng máy tính để bàn\n\nSteamKit và node-steam-user cung cấp các giao thức tương tác lập trình với Steam. ArchiSteamFarm hướng dẫn cách “farm” thẻ qua nhiều tài khoản và khai báo SteamKit2 là một phụ thuộc.\n\nĐây là những khả năng tự động hóa cụ thể. Việc thực thi theo kiểu “headless” không đồng nghĩa với việc chỉ dành riêng cho mục đích thương mại hay việc vượt qua cơ chế bảo vệ chống lạm dụng (Steam Guard). Các yếu tố cần xem xét là thông tin xác thực được yêu cầu, các hành động mà thông tin đó có thể thực hiện và các biện pháp kiểm soát được nền tảng áp dụng.\n\nNguồn: các tệp README của dự án và ArchiSteamFarm.csproj. Bản đồ khả năng liên kết từng phụ thuộc đã được ghi chép.\n3. JoeLudwig: Nhãn đóng góp cho hl2sdk\n\nBản chụp nhanh liệt kê JoeLudwig là người đóng góp cho các dự án alliedmodders/hl2sdk, ValveSoftware/openvr và ValveSoftware/source-sdk-2013.. Đó là mối quan hệ giữa các dự án có thể quan sát được. Dữ liệu xuất ra không cung cấp bằng chứng nào liên kết một thay đổi cụ thể trong SDK với hành vi trộm cắp hoặc triển khai liên quan đến cờ bạc.\n\nTham chiếu kho lưu trữ / xem lịch sử\nalliedmodders/hl2sdk ↗ DoctorMcKay/node-steam-user ↗\nSƠ ĐỒ MẠCH LOGIC // ĐƯỜNG DẪN\nSơ đồ luồng logic kết nối:\nHỒ SƠ MỐI QUAN HỆ\nNephyrin / Hồ sơ tổng hợp\nNgười đóng góp: Proton. Người tạo nhánh: SteamKit và open-steamworks.\n▼ Mối quan hệ phân nhánh được tổng hợp\nTHƯ VIỆN CỘNG ĐỒNG\nSteamRE/SteamKit\nThư viện mạng Public Steam do tổ chức SteamRE quản lý.\n▼ Đã khai báo phụ thuộc vào SteamKit2\nTỰ ĐỘNG HÓA ĐƯỢC LƯU TRỮ\nJustArchiNET/ArchiSteamFarm\nTài liệu hướng dẫn việc “farm thẻ” trên nhiều tài khoản và sự phụ thuộc vào SteamKit2.\nXEM XÉT CHỨNG CỨ / TỔNG QUAN NGUỒN THÔNG TIN\nĐÃ GHI NHẬN: các nhãn “người đóng góp” và “người phân nhánh” riêng biệt.\nĐÃ ĐƯỢC CHỨNG MINH: các thư viện công cộng hỗ trợ các hoạt động tương tác theo chương trình Steam.\nCÂU HỎI MỞ: Việc xác định tác giả cụ thể của mã nguồn, việc phê duyệt nền tảng và việc quy trách nhiệm cho hành vi lạm dụng đều cần có bằng chứng riêng biệt.",
        "headings": [
          {
            "level": 1,
            "id": null,
            "text": "Mã nguồn. Những người đóng góp. Các nhánh."
          },
          {
            "level": 2,
            "id": null,
            "text": "1. Nephyrin: các nhánh và đóng góp"
          },
          {
            "level": 2,
            "id": null,
            "text": "2. Các tính năng công khai: tự động hóa mà không cần ứng dụng máy tính để bàn"
          },
          {
            "level": 2,
            "id": null,
            "text": "3. JoeLudwig: Nhãn đóng góp cho hl2sdk"
          }
        ],
        "links": [
          "https://phishdestroy.io/steam_dossier/vi/investigation_part2.html#automation-map",
          "https://github.com/SteamRE/SteamKit",
          "https://github.com/SteamRE/open-steamworks",
          "https://github.com/alliedmodders/hl2sdk",
          "https://github.com/DoctorMcKay/node-steam-user"
        ]
      },
      "export_json_url": "https://phishdestroy.io/steam_dossier/exports/pages/vi/output_steam_network__valve_ru_farming_isolated.content.json",
      "export_json_sha256": "3617461d5299de49490634c22d9367b68337bcaab25dd91c6a5c62326dfe63f1"
    }
  ]
}